A likely outcome to an H.248 link recovery scenario is that a network of gateways and IP endpoints, initially registered to the primary server, might now be registered to a number of different Survivable Remote Servers in the network. This can be very disruptive in that network capability may be highly compromised. Resources at various points in the network may be available in only limited quantities, or not at all.

The SAT commands list media-gateway and status media-gateway can show those gateways that are not registered with the primary server. If the technician is on site, the illumination of the YELLOW ACT LED on the Survivable Remote Servers is an indication that something has registered with that Survivable Remote Servers, and therefore, that the network is fragmented. Two methods are available to recover from a fragmented network:

• Auto Fallback to Primary describes how this feature reconstructs the server/gateway topology following network fragmentation.
• Execute reset system 4 on each Survivable Remote Servers.
  To force gateways and IP endpoints to re-register with the primary server, execute a reset system 4 command, thus forcing any gateways and IP endpoints registered to the Survivable Remote Servers to search for and re-register with the primary server. The expectation is that these endpoints will correctly perform the search and find the primary server; however, there is no guarantee that this will be the result.
  The only way to be certain that gateways and endpoints re-register with the primary server is to shut down Communication Manager on every Survivable Remote Servers in the network.