and the Alcatel logo are registered trademarks of Alcatel. Xylan®, OmniSwitch®, OmniStack®,
®
are registered trademarks of Alcatel Internetworking, Inc.
OmniAccess™, Omni Switch/Router™, PolicyView™, RouterView™, SwitchManager™, VoiceView™,
WebView™, X-Cell™, X-Vision™, and the Xylan logo are trademarks of Alcatel Internetworking, Inc.
This OmniSwitch product contains components which may be covered by one or more of the following
U.S. Patents:
•U.S. Patent No. 6,339,830
•U.S. Patent No. 6,070,243
•U.S. Patent No. 6,061,368
•U.S. Patent No. 5,394,402
•U.S. Patent No. 6,047,024
•U.S. Patent No. 6,314,106
•U.S. Patent No. 6,542,507
26801 West Agoura Road
Calabasas, CA 91301
(818) 880-3500 FAX (818) 880-3505
info@ind.alcatel.com
US Customer Support—(800) 995-2696
International Customer Support—(818) 878-4507
Internet—http://eservice.ind.alcatel.com
iiOmniSwitch Troubleshooting GuideSeptember 2005
Contents
About This Guide .........................................................................................................xv
Supported Platforms ......................................................................................................... xv
Who Should Read this Manual? ...................................................................................... xvi
When Should I Read this Manual? .................................................................................. xvi
What is in this Manual? ................................................................................................... xvi
What is Not in this Manual? ...........................................................................................xvii
How is the Information Organized? ...............................................................................xvii
Related Documentation ..................................................................................................xvii
Before Calling Alcatel’s Technical Assistance Center .................................................... xx
Chapter 1Troubleshooting the Switch System ......................................................................1-1
In This Chapter ................................................................................................................1-1
This OmniSwitch Troubleshooting Guide describes how to use Command Line Interface (CLI) and Dshell
commands available on the OmniSwitch 6600 Family, OmniSwitch 6800 Series, OmniSwitch 7700/7800,
and the OmniSwitch 8800 to troubleshoot switch and network problems.
Supported Platforms
This information in this guide applies to the following products:
• OmniSwitch 6624 (OmniSwitch 6600-24)
• OmniSwitch 6648 (OmniSwitch 6600-48)
• OmniSwitch 6600-P24
• OmniSwitch 6600-U24
• OmniSwitch 6602-24
• OmniSwitch 6602-48
• OmniSwitch 6800
• OmniSwitch 7700
• OmniSwitch 7800
• OmniSwitch 8800
Note. All references to OmniSwitch 6624 and 6648 switches also apply to the OmniSwitch 6600-P24,
OmniSwitch 6600-U24, OmniSwitch 6602-24, and OmniSwitch 6602-48 unless specified otherwise.
Unsupported Platforms
The information in this guide does not apply to the following products:
• OmniSwitch (original version with no numeric model name)
Note. Troubleshooting documentation for legacy products (e.g., Omni Switch/Router) can be downloaded
at http://support.ind.alcatel.com/releasefiles/indexpage.cfm.
Who Should Read this Manual?
The principal audience for this user guide is Service and Support personnel who need to troubleshoot
switch problems in a live network. In addition, network administrators and IT support personnel who need
to configure and maintain switches and routers can use this guide to troubleshoot a problem upon advice
from Alcatel Service and Support personnel..
However, this guide is not intended for novice or first-time users of Alcatel OmniSwitches. Misuse or failure to follow procedures in this guide correctly can cause lengthy network down time and/or permanent
damage to hardware. Caution must be followed on distribution of this document.
When Should I Read this Manual?
Always read the appropriate section or sections of this guide before you log into a switch to troubleshoot
problems. Once you are familiar with the commands and procedures in the appropriate sections you can
use this document as reference material when you troubleshoot a problem.
What is in this Manual?
The principal sections (i.e., the chapters numbered numerically) use CLI and Dshell commands to analyze
and troubleshoot switch problems. Each section documents a specific switch feature (e.g., hardware, server
load balancing, routing).
Note. Dshell commands should only be used by Alcatel personnel or under the direction of Alcatel.
Misuse or failure to follow procedures that use Dshell commands in this guide correctly can cause lengthy
network down time and/or permanent damage to hardware.
Appendix A provides an architecture overview for the OmniSwitch 6600 Family, OmniSwitch 7700/7800,
and the OmniSwitch 8800.
Appendices B and C provide the following for debug and technical support CLI commands:
• Command description.
• Syntax.
• Description of keywords and variables included in the syntax.
• Default values.
• Usage guidelines, which include tips on when and how to use the command.
• Release history, which indicates the release when the command was introduced.
Appendix D provides a list of useful VI editor commands and a sample VI session that modifies the
boot.params file.
What is Not in this Manual?
This guide is intended for troubleshooting switches in live networks. It does not provide step-by-step
instructions on how to set up particular features on the switch or a comprehensive reference to all CLI
commands available in the OmniSwitch. For detailed syntax on non debug CLI commands and comprehensive information on how to configure particular software features in the switch, consult the user
guides, which are listed in “Related Documentation” on page xvii.
How is the Information Organized?
Each chapter in this guide includes troubleshooting guidelines related to a single software feature, such as
server load balancing or link aggregation.
Related Documentation
The following are the titles and descriptions of all the Release 5.1 and later OmniSwitch user guides:
• OmniSwitch 6600 Family Getting Started Guide
Describes the hardware and software procedures for getting an OmniSwitch 6624 or 6648 up and
running. Also provides information on fundamental aspects of OmniSwitch software and stacking
architecture.
• OmniSwitch 6800 Series Getting Started Guide
Describes the hardware and software procedures for getting an OmniSwitch 6800 up and running. Also
provides information on fundamental aspects of OmniSwitch software and stacking architecture.
• OmniSwitch 7700/7800 Getting Started Guide
Describes the hardware and software procedures for getting an OmniSwitch 7700 or 7800 up and
running. Also provides information on fundamental aspects of OmniSwitch software architecture.
• OmniSwitch 8800 Getting Started Guide
Describes the hardware and software procedures for getting an OmniSwitch 8800 up and running. Also
provides information on fundamental aspects of OmniSwitch software architecture.
• OmniSwitch 6600 Family Hardware Users Guide
Complete technical specifications and procedures for all OmniSwitch 6624 and 6648 chassis, power
supplies, fans, uplink modules, and stacking modules.
Complete technical specifications and procedures for all OmniSwitch 6800 chassis, power supplies,
fans, uplink modules, and stacking modules.
• OmniSwitch 7700/7800 Hardware Users Guide
Complete technical specifications and procedures for all OmniSwitch 7700 and 7800 chassis, power
supplies, fans, and Network Interface (NI) modules.
• OmniSwitch 8800 Hardware Users Guide
Complete technical specifications and procedures for all OmniSwitch 8800 chassis, power supplies,
fans, and Network Interface (NI) modules.
• OmniSwitch CLI Reference Guide
Complete reference to all CLI commands supported on the OmniSwitch 6624/6648, 7700/7800, and
8800. Includes syntax definitions, default values, examples, usage guidelines and CLI-to-MIB variable
mappings.
• OmniSwitch 6600 Family Switch Management Guide
Includes procedures for readying an individual switch for integration into a network. Topics include the
software directory architecture, image rollback protections, authenticated switch access, managing
switch files, system configuration, using SNMP, and using web management software (WebView).
• OmniSwitch 6800 Series Switch Management Guide
Includes procedures for readying an individual switch for integration into a network. Topics include the
software directory architecture, image rollback protections, authenticated switch access, managing
switch files, system configuration, using SNMP, and using web management software (WebView).
Includes procedures for readying an individual switch for integration into a network. Topics include the
software directory architecture, image rollback protections, authenticated switch access, managing
switch files, system configuration, using SNMP, and using web management software (WebView).
• OmniSwitch 6600 Family Network Configuration Guide
Includes network configuration procedures and descriptive information on all the major software
features and protocols included in the base software package. Chapters cover Layer 2 information
(Ethernet and VLAN configuration), Layer 3 information (RIP and static routes), security options
(authenticated VLANs), Quality of Service (QoS), and link aggregation.
• OmniSwitch 6800 Series Network Configuration Guide
Includes network configuration procedures and descriptive information on all the major software
features and protocols included in the base software package. Chapters cover Layer 2 information
(Ethernet and VLAN configuration), Layer 3 information (RIP and static routes), security options
(authenticated VLANs), Quality of Service (QoS), and link aggregation.
Includes network configuration procedures and descriptive information on all the major software
features and protocols included in the base software package. Chapters cover Layer 2 information
(Ethernet and VLAN configuration), Layer 3 information (routing protocols, such as RIP and IPX),
security options (authenticated VLANs), Quality of Service (QoS), link aggregation, and server load
balancing.
• OmniSwitch 6600 Family Advanced Routing Configuration Guide
Includes network configuration procedures and descriptive information on the software features
included in the advanced routing software package (OSPF).
• OmniSwitch 6800 Series Advanced Routing Configuration Guide
Includes network configuration procedures and descriptive information on the software features and
protocols included in the advanced routing software package (OSPF, DVMRP, PIM-SM).
Includes network configuration procedures and descriptive information on all the software features and
protocols included in the advanced routing software package. Chapters cover multicast routing
(DVMRP and PIM-SM) and OSPF.
• Technical Tips, Field Notices
Includes information published by Alcatel’s Service and Support group.
• Release Notes
Includes critical Open Problem Reports, feature exceptions, and other important information on the
features supported in the current release and any limitations to their support.
These user guides are included on the Alcatel Enterprise User Manual CD that ships with every switch.
You can also download these guides at http://www.ind.alcatel.com/library/manuals/index.cfm?cnt=index.
Before Calling Alcatel’s Technical Assistance
Center
Before calling Alcatel’s Technical Assistance Center (TAC), make sure that you have read through the
appropriate section (or sections) and have completed the actions suggested for your system’s problem.
Additionally, do the following and document the results so that the Alcatel TAC can better assist you:
• Have a network diagram ready. Make sure that relevant information is listed, such as all IP addresses
and their associated network masks.
• Have any information that you gathered while troubleshooting the issue to this point available to
provide to the TAC engineer.
• If the problem appears to be with only a few-fewer than four-switches, capture the output from the
show tech-support CLI command on these switches. (See Appendix C, “Technical Support
Commands,” for more information on show tech-support CLI commands.)
When calling Alcatel TAC in order to troubleshoot or report a problem following information can be helpful to get a quick resolution:
• All the dump files that were created, if any
• Output of switch log or the switch log files swlog1.log and swlog2.log
• Configuration file boot.cfg
• A capture of the show microcode command
• A capture of the show module long command
• A capture of the show tech-support command from CLI.
• If a CMM fail over to the redundant CMM happened because of this failure then include this informa-
tion from both of the CMMs.
Dial-in or Telnet access can also helpful for effective problem resolution.
In order to troubleshoot the system, a basic understanding of the operation of Chassis Management
Modules (CMMs) and their interaction with Network Interface (NI) modules is required. Some concepts
are covered in this chapter:
• Understanding of the “Diagnosing Switch Problems” chapter in the appropriate OmniSwitch Switch
Management Guide.
• Understanding of the “Using Switch Logging” from the appropriate OmniSwitch Network Configura-
tion Guide is highly recommended.
In This Chapter
“Introduction” on page 1-2
“Troubleshooting System for OS-6624/6648 and OS-7/8XXX” on page 1-3
“Advanced Troubleshooting” on page 1-9
“Dshell Troubleshooting” on page 1-11
“Using AlcatelDebug.cfg” on page 1-26
“Troubleshooting IPC on OS-6/7/8XXX Series of Switches” on page 1-27
The CMM is the Management Module of the switch. All of the critical operations of the switch including
the monitoring is the responsibility of the CMM. CMM not only provides monitoring but also synchronizes all of the NI for different operations. The operation of the CMM is the same in OS-6/7/8XXX
switches. The only difference is that OS-6/7XXX has the switching fabric inherent to the module whereas
OS-8800 has fabric at the back of the chassis.
NI has a build in CPU. Each NI has its own CPU, which acts independently of the CMM. The CPU of the
NI has to interact with the CPU on the CMM for certain operations. If this operation becomes out of sync
then it can create problems specific to that NI.
In order to troubleshoot the system, an understanding of the CMM and NI operation is essential.
Troubleshooting the Switch SystemTroubleshooting System for OS-6624/6648 and OS-7/8XXX
Troubleshooting System for OS-6624/6648 and
OS-7/8XXX
If the switch is having any problems the first place to look for is the CMM. All the task are supervised by
CMM. Any in coherency between CMM and the NI can cause problems to appear.
1 The first step for troubleshooting problems with the switch is to look at the overall general health of the
switch.
OmniSwitch 7700/7800/8800
Verify that all of the modules in the chassis are up and operational, using the command:
-> show module status
Operational Firmware
Slot Status Admin-Status Rev MAC
------+-------------+------------+---------+----------------CMM-A UP POWER ON 36 00:d0:95:6b:09:40
NI-1 UP POWER ON 5 00:d0:95:6b:22:5c
NI-3 UP POWER ON 5 00:d0:95:6b:23:2e
NI-5 UP POWER ON 5 00:d0:95:6b:3a:20
OmniSwitch 6624/6648
If the switch is having any problems the first place to look for is the CMM. All the task are supervised by
CMM. Any in coherency between CMM and the NI can cause problems to appear. For OS-6600 with 8
units stacked together, the CMM will be:
• Primary
• Secondary
• Idle
The switch with the lowest ID will become the primary CMM.
The first step for troubleshooting problems with the switch is to look at the overall general health of the
switch.
Verify that all of the modules in the chassis are up and operational, using the command:
Troubleshooting System for OS-6624/6648 and OS-7/8XXXTroubleshooting the Switch System
NI-2 UP POWER ON N/A 00:d0:95:84:3d:26
NI-3 UP POWER ON N/A 00:d0:95:86:50:f4
NI-4 UP POWER ON N/A 00:d0:95:84:49:be
NI-5 UP POWER ON N/A 00:d0:95:84:39:be
NI-6 UP POWER ON N/A 00:d0:95:84:4a:90
NI-7 UP POWER ON N/A 00:d0:95:84:39:f4
NI-8 UP POWER ON N/A 00:d0:95:84:3c:44
OmniSwitch 6600 with 8 stackable switches show up. Notice that the switch with ID 1 is the primary
CMM and the switch with ID of 2 is the secondary. All the switch also show up as NI because each switch
has a CPU and is also a NI.
To verify the stacking topology, use the following command:
-> show stack topology
Link A Link A Link A Link B Link B Link B
NI Role State RemoteNI RemoteLink State RemoteNI RemoteLink
The above command shows the stacking topology. Switch 1 is the primary connected to Switch 8 on port
51 and Switch 2 on port 52. The state of CPUs for all the switches in the stack is shown by the output of
this command.
2 Verify the power supply (or supplies).
OmniSwitch 7700/7800/8800
Omni Switch 7/8XXX has build-in mechanism to power off the modules if the power supply is not
enough. Switching off a power supply in a chassis which does not have redundant power supply will result
in power off of the modules. Make sure that there is no power involvement.
Check the power supply status, using the command:
-> show power supply 1
Module in slot PS-1
Model Name: OSR-PS-06,
Description: OSR-PS-06,
Part Number: 901750-10,
Receive800000000
Transmit/Receive8000000000
Memory8043434343
Cpu8002060507
Temperature Cmm5038373737
Temperature Cmm Cpu5032323132
The above command shows the receive, transmit/receive, memory, CPU, temperature CMM and temperature CMM CPU statistics for current, 1 minimum average, 1 hour average and 1 hour maximum. All the
values should be within the threshold. Anything above the threshold depicts that some abnormal behavior.
Normally 1 hour average maximum might be high if the switch was booted up in the last hour but it should
be fairly steady during normal operation.
If none of the above are above the threshold then the next step is to try to isolate the problem to a particular NI. Due to the distributed architecture every NI has it own CPU to perform some operations locally. It
is possible that a particular NI might be at high CPU utilization at a time when other NI as well as the CPU
are within the thresholds.
If none of the above are above the threshold then the next step is to try to isolate the problem to a particular NI (or a switch within an OmniSwitch 6624/6648 stack) with the show health slot_number CLI
command:
-> show health 5
* - current value exceeds threshold
Slot 051 Min 1 Hr 1 Hr
ResourcesLimit CurrAvgAvgMax
Troubleshooting the Switch SystemTroubleshooting System for OS-6624/6648 and OS-7/8XXX
The average on one minute is calculated from the average of 12 samples. Each sample is an average of the
CPU utilization during 5 seconds. Those values are stored in a table. The current minute (1 Min Avg or
“min”) displays the average of the last 12 samples.
Every 60 seconds the average of the 12 samples is recorded into the average value for this minute. Those
values are stored in a form of 60 samples which represent one hour.
Most probably one of the above would help to localize the problem to a particular NI or to CMM. For
more details see, Section “Monitoring Switch Health” in the chapter titled “Diagnosing Switch Problems”
in the appropriate OmniSwitch Network Configuration Guide.
4 Check the switch log.
OmniSwitch 6624/6648 and 7700/7800/8800
Now, one of the most important things to check is the switch log. Switch log would contain the error
messages depending on the settings of the log levels and applications configured to generate error
messages. Default settings of the log switch log can be view using the command:
-> show swlog
Switch Logging is:
- INITIALIZED
- RUNNING
Log Device(s)
----------------
flash
console
Only Applications not at the level ‘info’ (6) are shown
Application IDLevel
----------------------------
CHASSIS (64)debug3 (9)
By default, log devices are set to be flash and console. This can be changed and specific log servers can be
used to log the messages, please refer to the Switch Management Guide for further details. The application trace level is set for ‘info’. Any error messages or informational messages would be logged in the
switch log.
Switch log should be viewed to see if any errors messages were generated by the switch. The command to
use is:
-> show log swlog
Displaying file contents for 'swlog2.log'
FILEID: fileName[swlog2.log], endPtr[32]
MON AUG 21 23:09:57 2023HSM-CHASSISinfo== HSM == GBIC extraction detect
ed on NI slot 1, GBIC port 2
MON AUG 21 23:28:33 2023HSM-CHASSISinfo== HSM == GBIC Insertion detecte
d on NI slot 1, GBIC port 1
MON AUG 21 23:28:33 2023HSM-CHASSISinfo== HSM == GBIC Insertion detecte
Troubleshooting System for OS-6624/6648 and OS-7/8XXXTroubleshooting the Switch System
d on NI slot 1, GBIC port 2
MON AUG 21 23:28:39 2023HSM-CHASSISinfo== HSM == GBIC extraction detect
ed on NI slot 5, GBIC port 2
MON AUG 21 23:30:39 2023HSM-CHASSISinfo== HSM == GBIC Insertion detecte
d on NI slot 5, GBIC port 2
MON AUG 21 23:30:41 2023HSM-CHASSISinfo== HSM == GBIC extraction detect
ed on NI slot 1, GBIC port 1
MON AUG 21 23:30:45 2023HSM-CHASSISinfo== HSM == GBIC extraction detect
ed on NI slot 1, GBIC port 2
TUE AUG 22 00:05:45 2023CSM-CHASSISinfo== CSM == !!!ACTIVATING!!!
TUE AUG 22 00:05:45 2023CSM-CHASSISinfo== CSM == !!! REBOOT !!!
TUE AUG 22 00:05:53 2023SYSTEMalarm System rebooted via ssReboot(),
restart type=0x2 (COLD)
The log message are kept in two log files: swlog1.log and swlog2.log in flash. In the above example, log
messages show that some GBICs were extracted and inserted at a particular time. In addition, the switch
was rebooted. This information helps to relate the time of the problem together with the events happening
at the switch. In addition, it also provides an idea about if the source of the problem was external or internal to the switch.
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.
If the switch is running in redundant configuration make sure that the two CMMs are completely synchronized. This can be done using the command:
-> show running-directory
Running CMM : PRIMARY,
Running configuration : WORKING,
Certify/Restore Status : CERTIFIED,
Synchronization Status : SYNCHRONIZED
If the two CMMs are not synchronized and the problem leads to the failure of Primary CMM then it will
result in re-initialization of all of the modules. If the two CMMs are properly synchronized and primary
CMM failed, the take over mechanism will be transparent to the end user. So, for complete redundancy
keep the two CMMs synchronized.
Look for any post-mortem dump files that may be created due to the problem with the switch. Post
Mortem Dump files have an extension of *.dmp and are created in /flash directory of the CMM (be sure to
check the secondary CMM, if running in redundant mode). System dump files are normally named as
“cs_system.dmp”, Memory related dump files are normally created as “MemMon000.dmp” and NI related
dump files are named as “SloXSliYver1.dmp”, where X is the slot number and Y is the slice number.
The creation of a dump file indicates a problem with the switch. System related dump files can be viewed
through CLI but other dump files cannot. For system related dump files use the command:
-> show log pmd cs_system.pmd
Capture the output of this command. In addition, if there are any dump files created in the switch, they
should be downloaded through FTP to forward them to technical support. Technical Support can have
them analyzed to find the source of the problem.
Troubleshooting the Switch SystemAdvanced Troubleshooting
Advanced Troubleshooting
One level of switch logging is stored in the two log files located in the /flash directory. There is another
low level debug that can be enabled and used for diagnosing the problems. This debug is known as
“systrace”, meaning system trace. The information in this trace is stored in NVRAM on the CMM, so it is
valid until powered off. Soft reboot of the switch will retain the trace information but powering off the
switch will result in loosing all of the information. This is less CMM intensive so can be used to collect all
the background information about the different tasks running in the switch.
The command to look at the default settings for systrace is
-> debug systrace show
sysTrace is:
- INITIALIZED
- RUNNING
- configured to TRACE CALLERS
- configured to NOT WATCH on stdout
All Applications have their trace level set to level ’info’ (6)
Systrace is set for the level of “info” for all the applications. Any application with trace level other than 6
is displayed in the above command output. Notice that it is initialized by default and is running in the
background. By default it is configured not to display messages on the console. The purpose of systrace is
to track all the system processes called and the caller.
Application log levels can be changed and specific applications can also be set for the logging purposes.
The commands are similar to switch log.
The applications and the log levels are the same as switch log applications. Please refer to the “Section
Switch Logging Commands Overview” section in the “Using Switch Logging” chapter in the appropriate
OmniSwitch Network Configuration Guide.
Systrace can be enabled using the command:
-> debug systrace enable
To look at the systrace log file use the following command:
Advanced TroubleshootingTroubleshooting the Switch System
_SM_IPCUP_TIMEOUT
3349118948 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> CS_TIMEOUT
3345200526 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3342928783 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3342928661 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> Event = CS_CSM_HELLO
_SM_IPCUP_TIMEOUT
3342928628 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> CS_TIMEOUT
3336738410 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3336738287 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> Event = CS_CSM_HELLO
_SM_IPCUP_TIMEOUT
3336738256 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> CS_TIMEOUT
3334849145 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3330548020 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3330547902 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> Event = CS_CSM_HELLO
_SM_IPCUP_TIMEOUT
3330547869 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> CS_TIMEOUT
3324495309 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3324357940 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3324357816 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> Event = CS_CSM_HELLO
_SM_IPCUP_TIMEOUT
3324357782 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> CS_TIMEOUT
3318167293 CSM-CH info tCsCSMtask ***HELLO FSM TRACE***
3318167171 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> Event = CS_CSM_HELLO
_SM_IPCUP_TIMEOUT
3318167139 CSM-CH info tCsCSMtask csCsmHelloReceptio - -> CS_TIMEOUT
This information is useful to analyze the different processes taking place in the switch.
Other useful command to use in case of problem is:
-> show tech-support
This command captures all of the information from the chassis, including the hardware information,
configuration, software release active and some other statistics about the number of buffers being used at
the time of the use of command. The output of the command is saved in /flash as “tech_support.log”.
Other variation of this command is: