A Plesk node is registered with IP address, say, 192.168.0.5. There is an IP Pool of "Plesk Hosting" type with IP range from 192.168.0.1 to 192.168.0.255. However, 192.168.0.5 is not within exclusions of the IP Pool.
As a result, the 192.168.0.5 IP address was considered as free and eventually assigned to a Plesk Client or a Plesk Domain as dedicated causing all Plesk domains on the node that used shared IP address 192.168.0.5 to stop resolving and fall offline.
Each IP Pool has a set of hardware nodes and groups configurable under
Top > Service Director > IP Manager > IP Pools > IP Pool name > Configuration tab > Hardware nodes. Only those nodes' addresses are automatically added to the IP Pool's exclusions.
If the group of the node in question is assigned to the IP Pool but the node address is still not added to the IP Pool's exclusions, it means that the node was added to the group after the IP Pool was configured.
Switch the subscription that auto-gained the IP address 192.168.0.5 to a shared IP address via its Customer Panel:
Top > Account Director > Customer Manager > Customers > The subscription owner > Log in to CP > Select Configuration tab > Click Switch to Shared IP
- Re-save the IP Pool to re-check nodes groups membership and re-read IP addresses:
Top > Service Director > IP Manager > IP Pools > IP Pool in question > Configuration, press
Editand then, without changing a thing,
Update. If after that 192.168.0.5 is not in exclusions, add it there by hand.
Please also note that when a hardware node is removed from OBAS its IP address stays in the corresponding IP Pool exclusions and should be removed manually..