Table of Contents
Advertisement
6.12 Troubleshooting Tips
This section covers possible causes of RMC problems and suggested solutions for them.
Table 6–5 RMC Troubleshooting
Symptom
You cannot enter the
RMC from the
modem.
The terminal cannot
communicate with
the RMC correctly.
RMC will not answer
when the modem is
called.
RMC will not answer
when modem is
called.
Possible Cause
The RMC may be in soft bypass or
firm bypass mode.
System and terminal baud rates do
not match.
Modem cables may be incorrectly
installed.
RMC remote access is disabled or
the modem was power cycled
since last being initialized.
The modem is not configured
correctly.
On DC power-up, RMC defers
initializing the modem for 30
seconds to allow the modem to
complete its internal diagnostics
and initializations.
Using the Remote Management Console
Suggested Solution
Issue the show com1_mode
command from SRM and
change the setting if necessary.
Set the baud rate for the
terminal to be the same as for
the system. For first-time
setup, note that the RMC and
system default baud is 9600.
Check modem phone lines and
connections.
From the local serial terminal or
VGA monitor, enter the set
password and set init
commands, and then enter the
enable remote command. (See
Section 6.7.)
Modify the modem
initialization string according to
your modem documentation.
Wait 30 seconds after powering
up the system and RMC before
attempting to dial in.
6-45
Advertisement
Table of Contents
Troubleshooting
