Chapter 19: Emergency Recovery
Procedure
In
the event the Avaya Secure Router 2330/4134 becomes unstable or unresponsive, follow the steps in
this section.
Note:
Avaya strongly recommends that you save the Secure Router 2330/4134 configuration both locally and
to a location on the network in the event it is required for system restoration in the future.
Procedure steps
1. Save the configuration locally and to a network location. See Saving the config file on page
46
2. Verify the unit has power. See Power problem on page 52 and Power supply on page 40
• Check system and power supply LEDs. If LEDs are off, verify there is power to the unit.
• Verify that power cords are attached and secure.
• Verify that the power switch is on.
• Verify that the power source has current.
If LEDs are still off, replace Secure Router 4134 power supply modules.
3. Check interface module LEDs. If any LEDs are red, the module may need to be replaced. See
Interpreting LEDs on page 38
4.
If unit has power, but is unresponsive, try to telnet to the router. If Telnet is successful, show
the running configuration to obtain more information that could be useful for a diagnosis. If
telnet is not successful, verify you can ping the router. If ping is unsuccessful, troubleshoot
ping. See
Ping does not work on page
56
5. Enter the show tech-support command and save the file for use in diagnosis. See
Using the
show tech-support command on page 44
6. If
you feel there is an issue with Secure Router 2330/4134 configuration, restore with a known
good configuration. If still unresponsive, reboot the router. See
Importing a saved
configuration on page 49
7.
If the router remains unresponsive, restore the unit to factory defaults. It is very important to
have a configuration file saved locally and to a network location for backup prior to this step.
Specifically, it is likely you will need to have Telnet and/or SSH enabled for remote access. See
Resetting to factory defaults on page
48 The default settings after a factory restore are:
• Telnet server is disabled
• Telnet client is enabled
Troubleshooting August 2013 393
To Next Page
Loading...
