SANnav Disaster Recovery setup complete but standby server not responding
Applies to
- Broadcom SANnav Management Portal v2.3.1b
- Bare Metal Deployment
Issue
- After completing SANnav Disaster Recovery setup on primary and standby node, the primary node shows error:
Source Name sannav-primarySource Address 10.0.0.1Description Disaster Recovery standby server ( 10.0.0.2 ) has not responded for the last 186 hours and 10 minutes. Please ensure the following prerequisites are met: 1. If there is a firewall configured between primary and standby servers, make sure the ports 12030, 12032, 12031 and 5432 are opened in the firewall. 2. If there are iptable rules configured, make sure the ports 12030, 12032, 12031 and 5432 are accessible from the standby server. 3. Verify that the SANnav MP Disaster Recovery Services on the standby server are up and running bin/show-dr-status.sh. If they are not, please restart the disaster recovery using the command bin/dr/restart-dr.sh.Severity CriticalMessage ID SSMP-DR-1002Count 1Category SANnav Application Event- The DR status of primary and standby nodes shows data is syncing:
# /opt/brocade/Portal_2.3.1b_bld037/bin/dr/show-dr-status.sh---------------------------------------------SANnav MP Disaster Recovery Server status---------------------------------------------Disaster recovery setup complete. Waiting for the full data synchronization to finish. Once complete the checkpoint will be updated.sannav-dr-primary.logshows it cannot reach the standby node:
Failed to invoke the rest API https://10.0.0.2:12030/dr/dataSynchronization?uuid={uuid} with exception org.springframework.web.client.ResourceAccessException: I/O error on GET request for "https://10.0.0.2:12030/dr/health/getPeerHealth": No route to host (Host unreachable); nested exception is java.net.NoRouteToHostException: No route to host (Host unreachable)
Remote node not responding for the health check request. Reason: {0}