Table Of Contents
Troubleshooting
Troubleshooting the Console Interface
Troubleshooting the CSS Power Supply
Troubleshooting the CSS 11800 Modules
Troubleshooting the Boot Process
Log File Information
Troubleshooting
This appendix provides general troubleshooting information for the CSS components. It includes the following sections:
•
Troubleshooting the Console Interface
•Troubleshooting the CSS Power Supply
•Troubleshooting the CSS 11800 Modules
•Troubleshooting the Boot Process
•Log File Information
Information in this appendix applies to the CSS 11050, CSS 11150, and CSS 11800 content services switches except where noted.
Troubleshooting the Console Interface
Table C-1 lists common communications problems that may exist between the CSS and a console. Ensure the console settings are configured to:
•Baud Rate - 9600
•Data Bits - 8
•Flow Control - none
•Parity - none
•Stop Bits -1
For information on console cable pinouts, refer to Appendix B, Cable Pinouts.
Table C-1 Troubleshooting the Console Interface
Possible Problem
|
Recommended Action
|
Nothing appears on the screen.
|
Ensure the RS-232 cable is securely connected to the console port.
|
Characters appear on the screen, but are garbled.
|
Verify that the CSS and the console settings match for baud rate, data bits, stop bits, and parity.
|
Abbreviated input is used, but pressing the tab key does not enter the command you want.
|
Ensure that you enter enough characters for the CSS to distinguish between different commands and options.
|
Random characters are lost.
|
Set the flow command on the console to XON/XOFF.
|
Troubleshooting the CSS Power Supply
Power supply status is indicated by the:
•Power LED on the CSS 11050 and CSS 11150
•PS1 and PS2 LEDs on the SCM in the CSS 11800
For information on power supply LEDs, refer to Chapter 2, Cabling the CSS. Table C-2 provides suggestions for correcting problems that may occur with the CSS 11050 or CSS 11150 power supply.
Table C-2 Troubleshooting the CSS 11050 or CSS 11150 CSS Power Supply
LED Name
|
LED Status
|
Possible Problem
|
Recommended Action
|
Power
|
Off
|
No power to power supply.
|
Ensure unit has power. Check power switch, power cord, and power source.
|
Fault in power supply.
|
Replace unit.
|
Table C-3 provides suggestions for correcting problems that may occur with the CSS 1800 power supplies (AC or DC). The power supply status LED is on the SCM.
Table C-3 Troubleshooting the CSS 11800 Power Supply
LED Name
|
LED Status
|
Possible Problem
|
Recommended Action
|
PS 1
PS 2
|
Off
|
No power to primary power supply.
|
Ensure unit has power. Check power switch, power cord, and power source.
|
Fault in power supply.
|
Replace the power supply.
|
The power outputs are out of limits (possibly caused by a low input line).
|
Replace the power supply or rectify the deficient line condition.
|
Note Installing a second CSS 11800 power supply provides power load balancing between the two power supplies. When you install a second power supply, it powers on and begins to share the power load automatically.
Troubleshooting the CSS 11800 Modules
Each CSS 11800 module is equipped with a temperature sensor that detects an over- or under-temperature condition. If the module detects that its temperature is out of range, it generates a log message.
Module status is indicated by the Status LED on the module front panel. For information about the module LEDs, refer to Chapter 2, Cabling the CSS.
Table C-4 provides suggestions for correcting problems that may occur with the modules.
Table C-4 Troubleshooting the CSS 11800 Modules
Symptom
|
Recommended Action
|
System cannot identify module type.
|
Remove the module and re-install it to reseat the module in the backplane connector.
|
Reload the ADI file.
|
System cannot find an image for the module.
|
Reload the ADI file.
|
Module failed diagnostic (according to the information in the Boot.log file).
|
Replace the module.
|
You cannot access log or archive files on the CSS disk but traffic is still passed in and out of the CSS.
|
Replace the Internal Disk Module. Remove the module and re-install it to reseat the module in the backplane connector.
|
Replacement IDM does not initialize.
|
If the replacement IDM does not contain the same version of the software that the CSS is currently running, the SCM will not initialize the IDM for use. You must reboot the CSS and configure a primary boot record. You can select the CSS software currently on the disk or instruct the CSS where to locate the CSS software ADI file to install on the disk. If you archived an offline version of your CSS running-config file, copy it back onto the CSS.
|
Troubleshooting the Boot Process
During the boot process, the SCM downloads software to the SFM or SFM2 and the I/O modules. If the boot process cannot locate the correct files, the CSS logs an error in the Boot.log file. For information about the boot process, refer to Chapter 4, Configuring the CSS.
Table C-5 provides suggestions for correcting problems that may occur during the boot process.
Table C-5 Troubleshooting the Boot Process
Symptom
|
Recommended Action
|
Boot diagnostic failed.
|
Check boot.log for error messages that may specify which component is faulty.
|
Boot process failed.
|
Check boot.log for error messages that may specify where in the process the boot failed. (For information on boot.log, refer to the "Log File Information" section in this appendix.)
|
Boot image is corrupt.
|
Reload the ADI file.
|
Cannot locate boot record.
|
Check boot record configuration in the Offline DM menu. (Refer to the Content Services Switch Basic Configuration Guide, Chapter 1, Logging In and Getting Started, for information on the Offline DM menu.) Reconfigure boot record configuration if necessary.
|
Log File Information
The CSS provides logging capabilities for debug and system monitoring by generating the log files described in Table C-6.
Table C-6 CSS Log File Descriptions
Log File
|
Log File Destination
|
Records
|
Default Location
|
AlternateLocation
|
Boot.log
|
Hard disk and console or flash disk and console
|
None
|
Results of the boot process.
|
Boot.bak
|
Hard disk and console or flash disk and console
|
None
|
Backup of a boot log file. Each time you reboot the CSS, the software renames the current boot log file to boot.log.prev and starts a new boot log file. The CSS overwrites an existing backup boot log file when it renames a boot log file.
|
Sys.log
|
Hard disk or flash disk
|
Console
syslogd
VTY1
VTY2
|
Log information for user-defined subsystem or CLI commands. By default, logging is enabled and logs subsystem all with level warning. The CSS creates sys.log to record this log information.
|
Sys.log.prev
|
Hard disk or flash disk
|
Console
syslogd
VTY1
VTY2
|
Backup of a system log file. When a system log file reaches its maximum size (50 MB, for a hard disk-based CSS; 10 MB, for a flash disk-based CSS), the software renames the system log file to sys.log.prev and starts a new system log file. The CSS overwrites an existing backup system log file when it renames a system log file. Each time you reboot a CSS, the software continues to use the existing system log file until it reaches its maximum size.
|
By default, the CSS has boot logging and system logging enabled and writes the logged information to the log files on the hard disk or flash disk, depending on the type of storage in your CSS. The maximum size of a log file is 50 MB for hard disk-based systems and 10 MB for flash disk-based systems. Log file information is recorded as ASCII text.
Note If the CSS disk fails, log and archive information cannot be saved to files on the disk.
For information on:
•Log messages, refer to Appendix D, Log Messages
•Configuring logging functions, refer to the Content Services Switch Basic Configuration Guide
•Using syslogd, refer to your syslogd daemon reference guide
