Troubleshooting Tip: Virtual IP not reachable after network service restart
| Description | This article describes the steps to recover the Shared IP address (Virtual IP address or VIP) in L2 High Availability systems after restarting the network service. The Virtual IP address is associated with the eth0 interface of the appliance in control (Primary Server under normal conditions). The Virtual IP association to eth0 is not persistent through network service restarts. Consequently, if the network service is restarted, the Virtual IP address is removed from eth0 and no longer reachable.
Working example (Primary Server): > ip addr sh dev eth0
Example after running “service network restart” on the Primary Server:
|
| Scope | Version: 8.x and 9.x |
| Solution | There are three options to recover the Virtual IP:
Option 1 (Non-intrusive: Does not require a restart of management services): Login to the CLI as root of the appliance in control and type
Example:
hsIP ADD 192.168.8.25 24 eth0
Login to the appliance CLI as root and type <wait 30 seconds> startupNAC
Option 3: Reboot Appliance via UI
1. In the Administration UI, navigate to System > Settings > System Management > Power Management.
Confirm the Shared IP entry has been re-added to eth0 via the CLI. Type
VIP should now be accessible.
For more details on High Availability, refer to the High Availability reference manual. |