Avaya G700 Troubleshooting Manual page 40

Initialization-Recovery-Registr
Symptom Root Cause
Avaya™ G700 Media The MGP cannot
Gateway doesn't communicate with
register with the Media the controller.
Gateway Controller
(MGC).
Avaya™ G700 Media Duplicate G700 IP
Gateway doesn't address or MGC IP
register with the Media address.
Gateway Controller
(MGC).
Avaya™ G700 Media Media Gateway
Gateway doesn't Processor (MGP) is
register with the Media misconfigured
Gateway Controller (possibly from a
(MGC). previous
installation).
Avaya™ G700 Media Media Gateway
Gateway doesn't Processor (MGP)
register with the Media True Flash File
Gateway Controller System is
(MGC). corrupted.
G700 Troubleshooting
1. On the MGP CLI, execute the command ping mgp <controller-ip>.
2. If the ping command is successful, check the administration of the Avaya™ G700 Media Gateway on
the S8300/S8700.
3. If the ping is not successful, and the controller is in the same Avaya™ G700 Media Gateway (Avaya™
S8300 Media Server), verify the physical layer with the command session icc
4. If the controller is external and the ping fails, you need to verify VLANs, gateway addresses (use show
ip route to see if the problem is with the S8300 or the MGP, as in the networking symptom AN-7 "cannot
communicate with the S8300".
1. To verify that the Media Gateway Processor doesn't have a duplicate IP address, physically disconnect
it from the network.
2. Try to ping the MGP from a station in the network.
3. Do the same with the S8300/S8700. Make sure you have valid "IP ADDRESS", "GATEWAY IP
ADDRESS", and "NETWORK MASK" on each of the internal P330 Processor, Media Gateway Processor,
and S8300/S8700.
1. Reset the G700 to factory settings by issuing the command nvram init in the Media Gateway Processor
CLI.
2. Reconfigure the G700 using the Installation and Upgrades documentation.
1. Check to see if setting the "IP ADDRESS", "GATEWAY IP ADDRESS", and "NETWORK MASK"
doesn't properly change the values of those parameters on the G700.
2. If this is the case, then there is an indication that the tffs may be corrupted. Please escalate the
problem and contact Avaya or your Authorized Avaya Business Partner.
Resolution
Page 2
7/5/2002 4:40 PM