Bay Networks Bay Dial VPN, Руководство по настройке и устранению неисправностей

Страница: 129 / 186

Troubleshooting
115623B Rev. 00 BayStream Multiservice Software Version 7.2 11-9
Getting a Snapshot of the Current Status
You can get a good picture of the current status by following these diagnostic
steps.
1.
Recheck all physical connections.
If you find a loose connection, tighten it and try your test again.
2.
Use the system log to display event messages.
The BayStream processor maintains its own log file in local memory for each
slot. Software entities (such as IP) log messages when various events occur.
You can display the messages from all slots as a single file, with events sorted
by date in descending order (most recent events first). Then you use these
messages to diagnose a problem with a port, slot, platform, or protocol.
If a software entity experiences a fault and fails to recover:
a.
Disable and reenable the port.
Watch the event log. Stop here if the software entity recovers.
b.
Reset the slot.
Watch the event log. Stop here if the software entity recovers.
c.
Press the Reset button on the front panel for no more than one
second.
This initiates a warm-boot procedure, which will keep the log intact.
Watch the event log. Stop here if the software entity recovers.
d.
Save the log to a file and transfer it using FTP or TFTP to the Bay
Networks host, or set the BayStream platform up for modem access
so that Bay Networks can dial in and look at it.
e.
Call the Bay Networks Technical Solutions Center to report the
problem.
If you cannot get the system to recover from the fault, contact the Bay
Networks Technical Response Center for the appropriate action to take.
Caution: Avoid using the
diags
command to boot a BayStream platform after
it has crashed. If you do so, or you remove and reinstall power, the diagnostics
software overwrites the log. This prevents you from accessing it to determine
the cause of the problem.