A Wan Line Stops Working; Cli Is Not Accessible - Avaya G450 Installing And Upgrading

2. Check the ALM LED on the module to which the trunk connects. If it is lit, see Maintenance
Alarms for Communication Manager 2.1, Media Gateways and Servers, 03-300190 for
testing procedures.

A WAN line stops working

1. Check the connection between the WAN line and the Avaya G450 Media Gateway. If the
physical connection is loose, tighten the connection. If the line still does not work, go on to
the next step.
2. Check the ALM LED on the module to which the WAN line connects. If the ALM LED is lit,
the problem may be the configuration of the module or a lack of T1 signal. You can try the
following:
- For E1/T1 interfaces, use the show controllers command to view the status of the
interface's controller. Make sure the controller is up, and that all error counters do not
increase.
- For all serial interfaces (E1/T1 and USB), use the show interfaces Serial
command to verify that the interface and line protocol are both up.
- For USB interfaces only, use the show interfaces Serial command to verify that
all line signals are up.
- Swap the module with another one.
- Check the CON LED on the module. The CON LED indicates if you have a signal. If
the CON LED is lit, check with your provider that you are receiving a signal.
For information on the various modules and their LEDs, see
description
!
CAUTION:
Hot insertion of a WAN module resets the G450. Therefore, any translation and
CAUTION:
other data that is in the running configuration but has not been saved to the
startup configuration will be lost.
3. Check the ALM LED on the Avaya G450 Media Gateway chassis. If it is lit, there may be a
system-wide problem.

CLI is not accessible

You can perform an NVRAM initialization using a jumper on the G450 main board. You should
only use this procedure if you are unable to access the CLI, for example if the G450 resets
continuously.
on page 131.
A WAN line stops working
Appendix A: Front panel
Issue 2 June 2008 127