XKL DarkStar DRA, Руководство пользователя

Страница: 63 / 72

53
DarkStar User Guide
4: Troubleshooting
www.xkl.com
Troubleshooting
This chapter provides troubleshooting information related to the operation of DarkStar systems and networks. It covers:
•
Good practices for setting up the system running configuration so that important incident notifications reach the event
log and SNMP.
•
Good crash recovery procedures so that the system returns as quickly as possible to a known good state.
• Console procedures for reviewing and revising the state of the system and its network connections.
•
Hardware procedures for interpreting LED patterns and booting via the hardware reset buttons.
• How the system switches to recovery mode in the face of catastrophic error.
In normal operations, many day-to-day problems are related to configuration changes for either the system and its
management services, or the local IP network it communicates with. Please be aware that this chapter covers issues that you
may experience as you initially set up and learn to operate a DarkStar system or network. If you experience issues beyond the
scope of this guide, especially if you experience a loss of customer traffic, contact an XKL representative for professional
technical support.
4.1 Good Practices
4.1.1 Running Configuration
Saved to boot flash via a write memory command, the configuration file runs automatically at boot time. It includes not only
system and network settings, but also configures management services such as SNMP and event logging that need to be in
place for better troubleshooting. As part of the running configuration, you should:
•
Configure operator consoles and AAA authentication. Use the
tacacs-server
,
aaa authentication
,
line
, and
password
commands.
•
Configure network time and management IP addresses. Use the
clock
,
hostname
,
ip domain-name
,
ip name-
server
,
interface
, and
ip address
commands.
•
Set up Bit Error Rate (BER) testing. Use the
bert logging
commands.
• Configure each client interface and wave interface, using the
interface client
, i
nterface wave
,
no laser
shutdown
, and
encapsulation
commands.
• Connect the interfaces. Use the
connect
command.
•
Set up an APP pathway. Use the
app
command.
• Configure SNMP traps. Use the
snmp-server
command.
•
Set up event logging. Use the
logging
command.
4.1.2 Crash Recovery
In the unlikely event of a system crash, a DarkStar system is designed to notify the operator and to recover automatically with,
as far as possible, no loss of customer traffic through the switch complex.
It is good practice to set up an accurate config file, saved on the DarkStar system (via a
write memory
command). This
restores a good system configuration ready for when the system automatically recovers. Config files contain passwords. Make
sure you have an accurate record of the passwords that will come into force if a saved config file is restored: