Avaya G250 Maintenance Manual page 84

Avaya Communication Manager controlled maintenance
The SAT commands list media-gateway and status media-gateway can show those
network elements that are not registered with the primary MGC. If the technician is on site, the
illumination of the YELLOW ACT LED on the LSP is an indication that something has registered
with that LSP, and therefore, that the network is fragmented.
A fragmented network can be made whole automatically by means of Auto Fallback. See
Fallback on page 84. There are also several means of making a fragmented network whole
manually. See
Auto Fallback
The Auto Fallback feature provides for the automatic return of all media gateways in the
network from backup MGCs and LSPs to the primary MGC. Auto Fallback uses a client/server
architecture in which the media gateways act in the role of a client that is requesting service
from the primary MGC, and the MGC acts in a permissive role to determine when an Auto
Fallback registration should be allowed.
There are several reasons for denying an Auto Fallback, which can result from general system
performance requirements, or from administrator-imposed requirements. General system
performance requirements can include denial of registration because:
Processor occupancy is above a threshold to handle a registration
●
Too many simultaneous media gateway registration requests
●
Too many IP phone registrations
●
Administrator-imposed requirements for denial of a registration can include:
Registrations restricted to a windowed time of day
●
Migration restricted to a condition of 0 active contexts, that is, there are no users on calls
●
within the media gateway in question.
The administered minimum time for network stability has not been exceeded.
●
The architectural design limits the exchange of information between client and server, which
helps to reduce signaling complexity. The existing registration mechanism is used to carry the
additional information to the Media Server required by this feature.
Other characteristics of this feature include:
This feature does not preclude an older media gateway firmware release from working
●
with Avaya Communication Manager 3.0 or vice versa. However, the Auto Fallback feature
would not be available.
For this feature to work, the MGC is required to have Avaya Communication Manager 3.0,
while the media gateway is required to have the gateway firmware available at the time of
the Avaya Communication Manager 3.0 release.
Existing H.248 media gateways are the targets.
●
84 Maintenance for the Avaya G250 and Avaya G350 Media Gateways
Manual recovery from a fragmented network on page 86.
Auto