OmniSwitch OS6860/OS6900/OS10K Troubleshooting Guide Part No.032996-00 Rev.A
AOS Release 7.X and 8.X January 2015
Alcatel-Lucent Page 11 of 148
6860-> show health port 1/1/1
Port 1/ 1/ 1 Current 1 Min 1 Hr 1 Day
Resources Avg Avg Avg
----------------------+---------+-------+-------+-------
Receive 0 0 0 0
Receive/Transmit 0 0 0 0
The above commands may help to narrow the problem to a particular NI or to the CMM. For more detail see,
the section “Monitoring Switch Health” in the chapter titled “Diagnosing Switch Problems” in the appropriate
OmniSwitch Network Configuration Guide.
4 Check the switch log.
One of the most important things to check is the switch log. The switch log contains the log events based on
the settings of the log levels and applications configured to generate log events messages. Default settings of
the switch log can be view using the command:
sno-lab-r1-6860> show swlog
Operational Status : Running,
File Size per file : 12500K bytes,
Log Device : console flash socket,
Log Device : ipaddr 192.168.2.131 remote command-log,
Syslog FacilityID : local7(23),
Hash Table entries age limit : 60 seconds,
Switch Log Preamble : Enabled,
Switch Log Debug : Disabled,
Switch Log Duplicate Detection : Disabled,
Console Display Level : info
By default, the chassis is set to log to flash and console. This can be changed and specific SYSLOG servers
can be used to log the messages, please refer to the Switch Management Guide for further details. The default
application trace level is ‘info’. Any error messages or informational messages would be logged in the switch
log.
The switch log should be viewed to see if any error messages were generated by the switch. The command to
use is:
sno-lab-r1-6860> show log swlog
/flash/swlog_chassis1.7 not found!
/flash/swlog_chassis1.6 not found!
/flash/swlog_chassis1.5 not found!
/flash/swlog_chassis1.4 not found!
/flash/swlog_chassis1.3 not found!
/flash/swlog_chassis1.2 not found!
Displaying file contents for '/flash/swlog_chassis1.1'
Jan 1 00:00:32 OS6860 syslogd started: BusyBox v1.19.3
Jan 1 00:00:32 OS6860 kernel: klogd started: BusyBox v1.19.3 (2014-05-14 02:47:33 PDT)
Jan 1 00:00:32 OS6860 kernel: [ 0.000000] Booting Linux on physical CPU 0
Jan 1 00:00:32 OS6860 kernel: [ 0.000000] Linux version 3.6.5
…….
If the log messages do not show enough information then they can be changed for specific applications to a
higher log level or for all the applications running in the switch. For setting up different log levels in switch
log, please refer to the “Using Switch Logging” chapter in the appropriate OmniSwitch Network Configuration
Guide.