Server User Manual

8-30 AlphaServer GS80/160/320 User’s Guide
8.8 Troubleshooting Tips
Table 8–4 lists possible causes and suggested solutions for symptoms
you might see.
Table 8–4 SCM Troubleshooting
Symptom Possible Cause Suggested Solution
You cannot enter the
SCM from the modem.
The SCM may be in
soft bypass or firm
bypass mode.
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.
The console device
cannot communicate
with the SCM
correctly.
System and console
device baud rates do
not match.
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.
SCM will not answer
when the modem is
called.
Modem cables may be
incorrectly installed.
Check modem phone lines
and connections.
SCM remote access is
disabled or the modem
was power cycled since
last being initialized.
From the local console
device, enter the set
password and set init
commands, and then enter
the enable remote
command.
The modem is not
configured correctly.
Modify the modem
initialization string
according to your modem
documentation.