Table of Contents
Advertisement
8.8
Troubleshooting Tips
Table 8–4 lists possible causes and suggested solutions for symptoms
you might see.
Table 8–4 SCM Troubleshooting
Symptom
You cannot enter the
SCM from the modem.
The console device
cannot communicate
with the SCM
correctly.
SCM will not answer
when the modem is
called.
8-30
AlphaServer GS80/160/320 User's Guide
Possible Cause
The SCM may be in
soft bypass or firm
bypass mode.
System and console
device baud rates do
not match.
Modem cables may be
incorrectly installed.
SCM remote access is
disabled or the modem
was power cycled since
last being initialized.
The modem is not
configured correctly.
Suggested Solution
Issue the show
com1_mode command
from SRM and change the
setting if necessary. If in
soft bypass mode, you can
disconnect the modem
session and reconnect it.
Set the baud rate for the
console device to be the
same as for the system.
For first-time setup,
suspect the console device,
since the SCM and system
default baud is 9600.
Check modem phone lines
and connections.
From the local console
device, enter the set
password and set init
commands, and then enter
the enable remote
command.
Modify the modem
initialization string
according to your modem
documentation.
Advertisement
Table of Contents
