How to run a basic health check on a Connectrix B-Series switch.
For initial diagnosis, running the supportshow command gathers the output from various commands.
If further investigation is needed, it may become necessary to run a supportsave as it contains the supportshow and additional information for engineering and attach it to the appropriate service request.
To collect the supportshow, see EMC Knowledgebase solution:
489144: Connectrix: How to collect a switch log file with a Putty session step by step.
Connectrix: How to collect a switch log file with a PuTTY session, step by step
Once supportshow has been completed, open the file with any text file editor. Listed below are the most useful commands that are part of the supportshow output.
Enter commands in lowercase only; mixed case is for readability.
- Examples are based on Fabric OS 8.2.x or higher, see the support by Product page (also for older firmware outputs): https://www.dell.com/support/home/en-ie/products search for the product in questions, and check for the command guide in the documentation section.
- For detailed explanation of the commands sees also the command guide for the relevant Fabric OS version.
chassisShow
WWN Unit: 1 ED-8510_4S_001:FID128:admin> chassishow [truncated] WWN Unit: 1 Header Version: 2 [truncated] ID: EMCXXXXXX Part Num: CONTRX0000DCX Serial Num: BRCXXXXXXXXXXX
firmwareShow
ED-8510_4S_fid128:FID128:admin> firmwareshow
Slot Name Appl Primary/Secondary Versions Status
--------------------------------------------------------------------------
4 CP0 FOS v8.2.3c1 ACTIVE *
v8.2.3c1
5 CP1 FOS v8.2.3c1 STANDBY
v8.2.3c1
7 FX8-24 FOS v8.2.3c1
v8.2.3c1
mapsdb --show
ED-8510_4S_fid128:FID128:admin> mapsdb --show
1 Dashboard Information:
=======================
DB start time: Sat Jan 1 00:01:50 2000
Active policy: dflt_moderate_policy
Configured Notifications: RASLOG,SNMP,SW_CRITICAL,SW_MARGINAL,SFP_MARGINAL
Fenced Ports : None
Decommissioned Ports : None
Fenced circuits : None
Quarantined Ports : None
Top Zoned PIDs <pid(it-flows)>:
2 Switch Health Report:
=======================
Current Switch Policy Status: MARGINAL
Contributing Factors:
---------------------
*EXPIRED_CERTS (MARGINAL).
3.1 Summary Report:
===================
Category |Today |Last 7 days |
--------------------------------------------------------------------------------
Port Health |No Errors |In operating range |
BE Port Health |No Errors |No Errors |
Extension GE Port Health |No Errors |No Errors |
Fru Health |In operating range |In operating range |
Security Violations |Out of operating range |Out of operating range |
Fabric State Changes |No Errors |In operating range |
Switch Resource |In operating range |In operating range |
Traffic Performance |In operating range |In operating range |
Extension Health |No Errors |No Errors |
Fabric Performance Impact|In operating range |In operating range |
3.2 Rules Affecting Health:
===========================
Category(Violation Count)|RepeatCount|Rule Name |Execution Time |Object |Triggered Value(Units)|
-----------------------------------------------------------------------------------------------------------------------------
Security Violations(46) |2 |defSWITCHSEC_TELNET_2 |03/28/24 20:35:18|Switch |3 Violations |
| | | |Switch |3 Violations |
|2 |defSWITCHSEC_LV_2 |03/28/24 20:35:18|Switch |3 Violations |
| | | |Switch |3 Violations |
|3 |defSWITCHSEC_TELNET_2 |03/27/24 20:35:06|Switch |4 Violations |
| | | |Switch |4 Violations |
| | | |Switch |3 Violations |
|3 |defSWITCHSEC_LV_2 |03/27/24 20:35:06|Switch |4 Violations |
| | | |Switch |4 Violations |
| | | |Switch |3 Violations |
|4 |defSWITCHSEC_TELNET_2 |03/26/24 20:34:53|Switch |4 Violations |
| | | |Switch |3 Violations |
| | | |Switch |4 Violations |
| | | |Switch |3 Violations |
switchShow
ED_br8510_4S_001:FID128:admin> switchshow switchName: ED_br8510_4S_001 switchType: 121.3 switchState: Online switchMode: Native switchRole: Principal switchDomain: 2 switchId: fffc02 switchWwn: 10:00:00:05:1e:98:ba:00 zoning: ON (cfgExample) switchBeacon: OFF FC Router: OFF HIF Mode: OFF Allow XISL Use: OFF LS Attributes: [FID: 128, Base Switch: No, Default Switch: Yes, Address Mode 0]
porterrshow- Use this command to display an error summary for all ports. The display contains one output line per port and shows error counters in ones, thousands (k), or millions (m) or giga (g)
slotShow -m(Only for use on Enterprise Directors)
errDumpThis command displays external error log messages for all switch instances and the chassis, without any page breaks.
If you are dealing with a dial home service request, this is where you can find the error that caused the dial home.
The errors are logged chronologically from top to bottom (oldest to newest), so if the switch dialed home, chances are the correlating error message is found closer to the bottom of the errdump output.
Each message displays the following:
Timestamp - Timestamp for the message.
Message ID - Message identifier.
External sequence number - Sequence number for the message
Security audit flag - Security audit logged. AUDIT displays in the field.
Severity - Severity of the message. Valid values include INFO, WARNING, ERROR, and CRITICAL.
Switch name - Switch name for the generator of this message, or chassis.
Message - Message body.
haDump hashow haredundancy --showOnly for use on Enterprise Directors. Use this command to display information about the status of the High Availability (HA) feature on the switch or a chassis. This command displays the following information:
Time Stamp
Local CP state (slot number and CP ID)
Remote CP state (slot number and CP ID)
Type of recovery (warm or cold)
High Availability (enabled or disabled)
Heartbeat (up or down)
Health of standby CP (healthy, failed, or unknown), is defined as follows:
Healthy - The standby CP is running and the background health diagnostic has not detected any errors.
Failed - The standby CP is running, but the background health diagnostic has discovered a problem with the blade. The logs should be checked to determine the appropriate repair action. Failover is disabled until the standby CP is repaired. Information about the failing device in the standby CP will be displayed.
Unknown - The standby CP health state is unknown due because the standby CP does not exist, heartbeat is down, or Health Monitor detects a configuration file error.
HA synchronization status:
HA State Synchronized - The system is currently fully synchronized. If a failover became necessary, it would be non-disruptive.
HA State Not In Sync - The system is unable to synchronize the two CPs because the standby CP is faulty, a haSyncStop command was issued, or a system error occurred. If a failover became necessary, currently, the standby CP reboots, and the failover is disruptive.
IP and Fibre Channel addresses configured for the switch.
Other internal HA state information, subject to change.
Example:
ED_br8510_4S_001:FID128:admin> hadump --------------------------------------- TIME_STAMP: Jul 10 09:51:33.769077 --------------------------------------- Local CP (Slot 4, CP0): Active, Warm Recovered Remote CP (Slot 5, CP1): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized [truncated]
"haRedundancy --show" Command.
Use this command to display the switch uptime and the chassis control processor redundancy statistics. For chassis, the command displays the control processor redundancy settings and switch uptime. For switches, the command displays the switch uptime only. See the command guide.
The display includes the following information:
Current active session: Displays the settings for the current session.
- HA synchronization status.
- Active slot state: Displays CP ID, whether CP is local or remote, and recovery type information.
- Standby slot state: Displays CP ID, and whether CP is local or remote.
- Start time: Displays the start time of the services in synchronized state.
Previous active session: Displays the settings for the previous active session.
- Active slot state: Displays CP ID, and recovery type information.
- Standby slot state: Displays CP ID information.
- Start time: Displays the start time of the services synchronized state for the session.
- End time: Displays end time of the session caused by expected or unexpected recovery.
System uptime: Displays the start time of the system services. This changes when there is a power cycle or both CPs are reset together.
If an issue (NOT currently impacting production) appears to be at the port level and it is necessary to gain a fresh set of port errors, clear the stats Or further troubleshooting is needed:
See the following KB articles:
Connectrix: Connection issue or port problems follow the Pre-SFP Replacement Procedure
Connectrix: How to troubleshoot Fibre Channel node to switch port or SFP communication problems by elimination, Self-Help.
To Clear the stats:
Connect to the switch by Putty
If virtual fabrics are in use:
fosexec --fid all -cmd "statsclear";fosexec --fid all -cmd "slotstatsclear"
or if the switch is running FOS 7.3 and above the command is
supportinfoclear --clear
If NO virtual fabrics are in use:
statsclear;slotstatsclear
Let errors accrue for 4 to 8 hours.
Run a fresh
supportshow or supportsave
Review the
porterrshow
(See the above-mentioned Kb articles for the porterrshow outputs and action to take.)
If the issue is not resolved after initial review of the supportshow, run
supportsave
See KB article:
Connectrix: How to collect Brocade Supportsave logs using SANnav, CLI, and Brocade USB
Attach output and your findings to the appropriate Service Request, and re-queue SR accordingly.
Refer to this published video:
You can also view this video on YouTube.