Cisco MDS SanOS Troubleshooting Guide -- Troubleshooting Hardware - Revision history

Pravraj at 10:55, 30 November 2010

2010-11-30T10:55:16Z

← Older revision		Revision as of 10:55, 30 November 2010
Line 51:		Line 51:
	: b. The System LED turns green, indicating that all chassis environmental monitors are reporting that the system is operational. If one or more of the environmental monitors reports a problem, the System LED is orange or red.		: b. The System LED turns green, indicating that all chassis environmental monitors are reporting that the system is operational. If one or more of the environmental monitors reports a problem, the System LED is orange or red.
	: c. The Active LED turns green, indicating that the supervisor module is operational and active. If the supervisor module is in standby mode, the Active LED is orange.		: c. The Active LED turns green, indicating that the supervisor module is operational and active. If the supervisor module is in standby mode, the Active LED is orange.
-	: d. Each Link LED flashes orange once and stays orange during diagnostic boot tests, and it turns green when the module is operational (online). If no signal is detected, the Link LED turns off. The ~~link~~ LED blinks orange if the port is bad.	+	: d. Each Link LED flashes orange once and stays orange during diagnostic boot tests, and it turns green when the module is operational (online). If no signal is detected, the Link LED turns off. The Link LED blinks orange if the port is bad.

	If any LEDs on the supervisor module front panel are red or orange after the initialization time, see the "Troubleshooting Supervisor Issues" section. If you have a redundant supervisor module, refer to the following website for the latest Cisco MDS 9000 Family configuration guides for descriptions of the supervisor module LEDS, how the redundant supervisor module comes online, and how the software images are handled:		If any LEDs on the supervisor module front panel are red or orange after the initialization time, see the "Troubleshooting Supervisor Issues" section. If you have a redundant supervisor module, refer to the following website for the latest Cisco MDS 9000 Family configuration guides for descriptions of the supervisor module LEDS, how the redundant supervisor module comes online, and how the software images are handled:
		+
	[http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/index.htm.]		[http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/index.htm.]

Line 102:		Line 103:
	Power supply is shut down.		Power supply is shut down.
	\|		\|
-	Choose<span style="font-style: normal">'''<font color="Black"> Physical > Power Supplies</font>'''</span> and check the OperStatus on Device Manager, or use the <span style="font-style: normal">'''<font color="Black">show environment power</font>'''</span> CLI command to determine if the power supply is shut down. If the status is ~~shutdown~~, then the supervisor has ~~shutdown~~ the power supply. The supervisor shuts down the lower capacity power supply only if it detects a mismatched pair of power supplies and the mode is redundant or if there is a transition from combined to redundant mode. If both power supplies are the same capacity or the mode is combined, Cisco SAN-OS never shuts down a power supply.	+	Choose<span style="font-style: normal">'''<font color="Black"> Physical > Power Supplies</font>'''</span> and check the OperStatus on Device Manager, or use the <span style="font-style: normal">'''<font color="Black">show environment power</font>'''</span> CLI command to determine if the power supply is shut down. If the status is shut down, then the supervisor has shut down the power supply. The supervisor shuts down the lower capacity power supply only if it detects a mismatched pair of power supplies and the mode is redundant or if there is a transition from combined to redundant mode. If both power supplies are the same capacity or the mode is combined, Cisco SAN-OS never shuts down a power supply.
	\|- align="left" valign="top"		\|- align="left" valign="top"
	\|		\|
Line 121:		Line 122:

	{\| id="wp44097table44095" width="80%" border="1" cellpadding="3"		{\| id="wp44097table44095" width="80%" border="1" cellpadding="3"
-	\|+ '''Table 4-2 Power Supply ~~INput~~ Ok LED Is Red'''	+	\|+ '''Table 4-2 Power Supply Input Ok LED is Red'''
	\|- align="left" valign="bottom"		\|- align="left" valign="bottom"
	! scope="col" \|		! scope="col" \|
Line 192:		Line 193:
	: '''Error Message''' PLATFORM-2-PS_FANFAIL: Fan in Power supply [dec] failed.		: '''Error Message''' PLATFORM-2-PS_FANFAIL: Fan in Power supply [dec] failed.
	:: '''Explanation''' Fan module in the power supply has failed.		:: '''Explanation''' Fan module in the power supply has failed.
-	:: '''Recommended Action''' Enter the <span style="font-style: normal">'''<font color="Black">show environment power</font>'''</span> and <span style="font-style: normal">'''<font color="Black">show platform internal info</font>'''</span> CLI command or similar Fabric Manager/Device Manager command to collect more information.	+	:: '''Recommended Action''' Enter the <span style="font-style: normal">'''<font color="Black">show environment power</font>'''</span> and <span style="font-style: normal">'''<font color="Black">show platform internal info</font>'''</span> CLI command or similar Fabric Manager/Device Manager command to collect more information. Introduced in Cisco MDS SAN-OS Release 1.3(1).

-	~~Introduced Cisco MDS SAN-OS Release 1.3(1).~~

	<div align="left">		<div align="left">
Line 374:		Line 374:
	To troubleshoot a fan module problem using the CLI, follow these steps:		To troubleshoot a fan module problem using the CLI, follow these steps:
	----		----
-	1. Use the <span style="font-style: normal">'''<font color="Black">show environment fan</font>'''</span> command ~~and~~ verify the status of each fan type.	+	1. Use the <span style="font-style: normal">'''<font color="Black">show environment fan</font>'''</span> command to verify the status of each fan type.

	'''Example 4-2 show environment fan Output'''		'''Example 4-2 show environment fan Output'''
Line 474:		Line 474:
	</pre>		</pre>

-	On a clock module failure, the system switches over to the redundant clock module automatically. This also results in a hardware reset of the switch. When the switch reboots, it displays the current active clock module. The following syslog message is printed at switch ~~boot-up~~ time, indicating the current active clock module:	+	On a clock module failure, the system switches over to the redundant clock module automatically. This also results in a hardware reset of the switch. When the switch reboots, it displays the current active clock module. The following syslog message is printed at switch bootup time, indicating the current active clock module:

	: '''Error Message''': PLATFORM-0-CHASSIS_CLKSWRESET: Switch reset due to clock switch.		: '''Error Message''': PLATFORM-0-CHASSIS_CLKSWRESET: Switch reset due to clock switch.
Line 480:		Line 480:
	:: '''Recommended Action''': Replace the failed clock module during the next maintenance window.		:: '''Recommended Action''': Replace the failed clock module during the next maintenance window.

-	Typically, clock module A is the active clock. On a failure of clock module A, clock module B becomes the active clock. Refer to the hardware installation guide for your platform at the following website to replace a clock module.	+	Typically, clock module A is the active clock. On a failure of clock module A, clock module B becomes the active clock. Refer to the hardware installation guide for your platform at the following website to replace a clock module:
	''http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_installation_guides_list.html''		''http://www.cisco.com/en/US/products/hw/ps4159/ps4358/prod_installation_guides_list.html''

Line 543:		Line 543:
	== Troubleshooting Supervisor Issues ==		== Troubleshooting Supervisor Issues ==

-	Supervisor initiation varies depending on whether or not you have a redundant supervisor present. When two supervisors are present in the system at ~~poweredup~~, one of the supervisors ~~will become~~ active and the other standby. The active supervisor initialization differs from the standby supervisor.	+	Supervisor initiation varies depending on whether or not you have a redundant supervisor present. When two supervisors are present in the system at powerup, one of the supervisors becomes active and the other standby. The active supervisor initialization differs from the standby supervisor.

	If there is no active supervisor in the system, the supervisor that boots up first will default to the active supervisor. If there is an active supervisor in the system, the supervisor that is booting up will default to the standby supervisor state. The standby supervisor needs to mirror the state of the active supervisor. After all components on the standby are synchronized with those of the active supervisor, the standby supervisor is up.		If there is no active supervisor in the system, the supervisor that boots up first will default to the active supervisor. If there is an active supervisor in the system, the supervisor that is booting up will default to the standby supervisor state. The standby supervisor needs to mirror the state of the active supervisor. After all components on the standby are synchronized with those of the active supervisor, the standby supervisor is up.
Line 595:		Line 595:
	<br />		<br />

-	Example 4-6 displays the reason for ~~the recent~~ when a supervisor module reboots after a process crash.	+	Example 4-6 displays the reason for when a supervisor module reboots after a process crash.

	'''Example 4-6 Reset Reason for Supervisor Reboot Caused by Failed Process'''		'''Example 4-6 Reset Reason for Supervisor Reboot Caused by Failed Process'''
Line 1,779:		Line 1,779:
	1. Choose <span style="font-style: normal">'''<font color="Black">Switches > Copy Configuration</font>'''</span> to save the running configuration to the startup configuration.		1. Choose <span style="font-style: normal">'''<font color="Black">Switches > Copy Configuration</font>'''</span> to save the running configuration to the startup configuration.

-	2. Choose<span style="font-style: normal">'''<font color="Black"> Switches > Hardware</font>'''</span>. ~~Then select~~ the <span style="font-style: normal">'''<font color="Black">Module Status</font>'''</span> tab in the Information pane and check the <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> check box to reload the module. Click the <span style="font-style: normal">'''<font color="Black">Apply Changes</font>'''</span> icon.	+	2. Choose<span style="font-style: normal">'''<font color="Black"> Switches > Hardware</font>'''</span>. Select the <span style="font-style: normal">'''<font color="Black">Module Status</font>'''</span> tab in the Information pane and check the <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> check box to reload the module. Click the <span style="font-style: normal">'''<font color="Black">Apply Changes</font>'''</span> icon.

	3. If the module is not up, choose <span style="font-style: normal">'''<font color="Black">Switches > Hardware </font>'''</span>and check the S/W Rev column to verify the software image on the module.		3. If the module is not up, choose <span style="font-style: normal">'''<font color="Black">Switches > Hardware </font>'''</span>and check the S/W Rev column to verify the software image on the module.
Line 1,785:		Line 1,785:
	4. If the software image on the module is not the latest, choose <span style="font-style: normal">'''<font color="Black">Tools > Other > Software Install</font>'''</span> to download the latest image to supervisor bootflash memory.		4. If the software image on the module is not the latest, choose <span style="font-style: normal">'''<font color="Black">Tools > Other > Software Install</font>'''</span> to download the latest image to supervisor bootflash memory.

-	5. Use the ~~CLI~~ to force-download the software image from the supervisor to the module.	+	5. Use the folowing command to force-download the software image from the supervisor to the module:

	<pre>		<pre>

Pravraj: /* Diagnosing a Module in the Unknown State */

2010-11-08T09:10:50Z

Diagnosing a Module in the Unknown State

← Older revision		Revision as of 09:10, 8 November 2010
Line 1,644:		Line 1,644:
	2. Choose<span style="font-style: normal">'''<font color="Black"> Logs > Switch Resident > Syslog > Sever Events</font>'''</span> on Device Manager or use the <span style="font-style: normal">'''<font color="Black">show logging</font>'''</span> CLI command to search for common problems.		2. Choose<span style="font-style: normal">'''<font color="Black"> Logs > Switch Resident > Syslog > Sever Events</font>'''</span> on Device Manager or use the <span style="font-style: normal">'''<font color="Black">show logging</font>'''</span> CLI command to search for common problems.

-	3. Use the <span style="font-style: normal">'''<font color="Black">show platform internal event-history</font>'''</span> <span style="font-style: normal">'''<font color="Black">errors ~~CLI command~~ </font>'''</span>to view possible causes for the unknown state.	+	3. Use the <span style="font-style: normal">'''<font color="Black">show platform internal event-history</font>'''</span> <span style="font-style: normal">'''<font color="Black">errors </font>'''</span> CLI command to view possible causes for the unknown state.

	<pre>		<pre>

Pravraj: /* Troubleshooting Modules in an Unknown State */

2010-11-08T09:09:59Z

Troubleshooting Modules in an Unknown State

← Older revision		Revision as of 09:09, 8 November 2010
Line 1,607:		Line 1,607:
	=== Troubleshooting Modules in an Unknown State ===		=== Troubleshooting Modules in an Unknown State ===

-	'''Symptom'' Module is in the unknown state.	+	'''Symptom''' Module is in the unknown state.

	<div align="left">		<div align="left">
Line 1,626:		Line 1,626:
	Module experienced SPROM failures.		Module experienced SPROM failures.
	\| rowspan="2" colspan="1" \|		\| rowspan="2" colspan="1" \|
-	Verify the cause of the failure. See the "Diagnosing a Module in the Unknown State" section]. Right-click on the module in Device Manager and select <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> or use the <span style="font-style: normal">'''<font color="Black">reload module </font>'''</span>CLI command to restart the module. See the "Reinitializing a Failed Module Using Fabric Manager" section or the "Reinitializing a Failed Module Using the CLI" section.	+	Verify the cause of the failure. See the "Diagnosing a Module in the Unknown State" section. Right-click on the module in Device Manager and select <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> or use the <span style="font-style: normal">'''<font color="Black">reload module </font>'''</span>CLI command to restart the module. See the "Reinitializing a Failed Module Using Fabric Manager" section or the "Reinitializing a Failed Module Using the CLI" section.
	\|- align="left" valign="top"		\|- align="left" valign="top"
	\|}		\|}

Pravraj: /* Diagnosing a Reloaded Module */

2010-11-08T09:09:11Z

Diagnosing a Reloaded Module

← Older revision		Revision as of 09:09, 8 November 2010
Line 1,555:		Line 1,555:
	----		----

-	1. Right-click the module and select <span style="font-style: normal">'''<font color="Black">Module</font>'''</span> on Device Manager or use the <span style="font-style: normal">'''<font color="Black">show module</font>'''</span> CLI command to verify the status of the module.	+	1. Right-click the module and select <span style="font-style: normal">'''<font color="Black">Module</font>'''</span> in Device Manager or use the <span style="font-style: normal">'''<font color="Black">show module</font>'''</span> CLI command to verify the status of the module.

-	2 .Choose<span style="font-style: normal">'''<font color="Black"> Logs > Switch Resident > Syslog > Sever Events</font>'''</span> on Device Manager or use the <span style="font-style: normal">'''<font color="Black">show logging</font>'''</span> CLI command to search for common reload problems.	+	2 .Choose<span style="font-style: normal">'''<font color="Black"> Logs > Switch Resident > Syslog > Sever Events</font>'''</span> in Device Manager or use the <span style="font-style: normal">'''<font color="Black">show logging</font>'''</span> CLI command to search for common reload problems.

	3 .Use the <span style="font-style: normal">'''<font color="Black">show module internal exception module</font>'''</span> CLI command to view the exception log.		3 .Use the <span style="font-style: normal">'''<font color="Black">show module internal exception module</font>'''</span> CLI command to view the exception log.

Pravraj: /* Troubleshooting Reloaded Modules */

2010-11-08T09:08:19Z

Troubleshooting Reloaded Modules

← Older revision		Revision as of 09:08, 8 November 2010
Line 1,502:		Line 1,502:

	: '''Error Message''' SYSTEMHEALTH-2-OHMS_MOD_PORT_LB_TEST_FAILED: Module [dec] Port [dec] has failed loop back tests.		: '''Error Message''' SYSTEMHEALTH-2-OHMS_MOD_PORT_LB_TEST_FAILED: Module [dec] Port [dec] has failed loop back tests.
-	:: '''Explanation''' Port loop-back test failure.	+	:: '''Explanation''' Port loop back test failure.
	:: '''Recommended Action''' No action is required.		:: '''Recommended Action''' No action is required.

Line 1,542:		Line 1,542:
	Module lost synchronize with the fabric.		Module lost synchronize with the fabric.
	\|		\|
-	Use the <span style="font-style: normal">'''<font color="Black">show system internal xbar internal event-history errors</font>'''</span><span style="font-style: normal">'''<font color="Black"> </font>'''</span>and look for something similar to: Rx MTS_OPC_SSA_LOST_SYNC_SERIAL slot 8 fabric 0 link 0 to verify that the module lost ~~sync~~ with the fabric. Right-click the module in Device Manager and select <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> or use the <span style="font-style: normal">'''<font color="Black">reload module </font>'''</span>CLI command to restart the module. See the "Reinitializing a Failed Module Using Fabric Manager" section or the "Reinitializing a Failed Module Using the CLI" section.	+	Use the <span style="font-style: normal">'''<font color="Black">show system internal xbar internal event-history errors</font>'''</span><span style="font-style: normal">'''<font color="Black"> </font>'''</span>and look for something similar to Rx MTS_OPC_SSA_LOST_SYNC_SERIAL slot 8 fabric 0 link 0 to verify that the module lost synchronization with the fabric. Right-click the module in Device Manager and select <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> or use the <span style="font-style: normal">'''<font color="Black">reload module </font>'''</span>CLI command to restart the module. See the "Reinitializing a Failed Module Using Fabric Manager" section or the "Reinitializing a Failed Module Using the CLI" section.
	\|}		\|}

Pravraj: /* Troubleshooting Powered-Down Modules */

2010-11-08T09:06:08Z

Troubleshooting Powered-Down Modules

← Older revision		Revision as of 09:06, 8 November 2010
Line 1,232:		Line 1,232:
	Module experienced boot-up failures.		Module experienced boot-up failures.
	\|		\|
-	<span style="font-style: normal">'''<font color="Black">~~Choose~~ Logs > Switch Resident > Syslog > Sever Events</font>'''</span> on Device Manager or use the <span style="font-style: normal">'''<font color="Black">show logging</font>'''</span> CLI command to verify bootup problems. Right-click the module in Device Manager and select <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> or use the <span style="font-style: normal">'''<font color="Black">reload module </font>'''</span>CLI command to restart the module. See the "Reinitializing a Failed Module Using Fabric Manager" section or the "Reinitializing a Failed Module Using the CLI" section.	+	Choose <span style="font-style: normal">'''<font color="Black">Logs > Switch Resident > Syslog > Sever Events</font>'''</span> on Device Manager or use the <span style="font-style: normal">'''<font color="Black">show logging</font>'''</span> CLI command to verify bootup problems. Right-click the module in Device Manager and select <span style="font-style: normal">'''<font color="Black">Reset</font>'''</span> or use the <span style="font-style: normal">'''<font color="Black">reload module </font>'''</span>CLI command to restart the module. See the "Reinitializing a Failed Module Using Fabric Manager" section or the "Reinitializing a Failed Module Using the CLI" section.
	\|- align="left" valign="top"		\|- align="left" valign="top"
	\|		\|

Pravraj: /* Troubleshooting Powered-Down Modules */

2010-11-08T09:04:42Z

Troubleshooting Powered-Down Modules

← Older revision		Revision as of 09:04, 8 November 2010
Line 1,203:		Line 1,203:
	: '''Error Message''' PLATFORM-3-MOD_PWRFAIL: Module [dec] failed to power up (Serial No. [chars]).		: '''Error Message''' PLATFORM-3-MOD_PWRFAIL: Module [dec] failed to power up (Serial No. [chars]).
	:: '''Explanation''' The module failed to power up.		:: '''Explanation''' The module failed to power up.
-	:: '''Recommended Action''' Enter the <span style="font-style: normal">'''<font color="Black">show platform internal all module</font>'''</span> <span style="font-style: normal">'''<font color="Black">[</font>'''</span>dec<span style="font-style: normal">'''<font color="Black">]</font>'''</span> CLI command to collect more information.	+	:: '''Recommended Action''' Enter the <span style="font-style: normal">'''<font color="Black">show platform internal all module </font>'''</span> <span style="font-style: normal">'''<font color="Black"></font>'''</span>''dec''<span style="font-style: normal">'''<font color="Black"></font>'''</span> CLI command to collect more information.
	:: Introduced Cisco MDS SAN-OS Release 1.2(2a).		:: Introduced Cisco MDS SAN-OS Release 1.2(2a).

Line 1,213:		Line 1,213:
	:: '''Explanation''' The module is powered down.		:: '''Explanation''' The module is powered down.

-	Enter the <span style="font-style: normal">'''<font color="Black">show module</font>'''</span>, <span style="font-style: normal">'''<font color="Black">show platform internal all module</font>'''</span>''dec''<span style="font-style: normal">'''<font color="Black"></font>'''</span> and <span style="font-style: normal">'''<font color="Black">show module internal all module </font>'''</span>''dec''<span style="font-style: normal">'''<font color="Black"> </font>'''</span>CLI command to collect more information if you suspect module has been powered down due to errors.	+	Enter the <span style="font-style: normal">'''<font color="Black">show module </font>'''</span>, <span style="font-style: normal">'''<font color="Black">show platform internal all module </font>'''</span>''dec''<span style="font-style: normal">'''<font color="Black"></font>'''</span> and <span style="font-style: normal">'''<font color="Black">show module internal all module </font>'''</span>''dec''<span style="font-style: normal">'''<font color="Black"> </font>'''</span>CLI command to collect more information if you suspect module has been powered down due to errors.

	<div align="left">		<div align="left">

Pravraj: /* Troubleshooting Powered-Down Modules */

2010-11-08T09:02:55Z

Troubleshooting Powered-Down Modules

← Older revision		Revision as of 09:02, 8 November 2010
Line 1,208:		Line 1,208:
	: '''Error Message''' PLATFORM-3-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to idprom read error.		: '''Error Message''' PLATFORM-3-MOD_PWRIDPROMFAIL: Module [dec] failed to power up due to idprom read error.
	:: '''Explanation''' The module cannot be powered up because of an IDPROM read error.		:: '''Explanation''' The module cannot be powered up because of an IDPROM read error.
-	:: '''Recommended Action''' Enter the~~<span style="font-style: normal">~~'''~~<font color="Black">~~ show platform internal all module~~</font>~~'''~~</span> <span style="font-style: normal">~~''~~'<font color="Black">[</font>'''</span>~~dec~~<span style="font-style: normal">'''<font color="Black">]</font>'~~''~~</span>~~ and ~~<span style="font-style: normal">~~'''~~<font color="Black">~~show module internal all module~~</font>~~'''~~</span> [~~dec~~] <span style="font-style: normal">~~'''~~<font color="Black">~~show sprom module~~</font>~~'''~~</span> <span style="font-style: normal">~~''~~'<font color="Black">[</font>'''</span>~~dec~~<span style="font-style: normal">~~'''~~<font color="Black">][</font>~~'~~''</span>~~dec~~<span style="font-style: normal">'''<font color="Black">]</font>'~~''~~</span>~~ CLI command to read module IDPROM contents to collect more information.	+	:: '''Recommended Action''' Enter the '''show platform internal all module''' ''dec'' and '''show module internal all module''' ''dec'' '''show sprom module''' ''dec'' ''dec'' CLI command to read module IDPROM contents to collect more information.

	: '''Error Message''' PLATFORM-5-MOD_PWRDN: Module [dec] powered down (Serial No. [chars]).		: '''Error Message''' PLATFORM-5-MOD_PWRDN: Module [dec] powered down (Serial No. [chars]).
	:: '''Explanation''' The module is powered down.		:: '''Explanation''' The module is powered down.

-	Enter the <span style="font-style: normal">'''<font color="Black">show module</font>'''</span>, <span style="font-style: normal">'''<font color="Black">show platform internal all module[</font>'''</span>dec<span style="font-style: normal">'''<font color="Black">]</font>'''</span> and <span style="font-style: normal">'''<font color="Black">show module internal all module [</font>'''</span>dec<span style="font-style: normal">'''<font color="Black">] </font>'''</span>CLI command to collect more information if you suspect module has been powered down due to errors.	+	Enter the <span style="font-style: normal">'''<font color="Black">show module</font>'''</span>, <span style="font-style: normal">'''<font color="Black">show platform internal all module</font>'''</span>''dec''<span style="font-style: normal">'''<font color="Black"></font>'''</span> and <span style="font-style: normal">'''<font color="Black">show module internal all module </font>'''</span>''dec''<span style="font-style: normal">'''<font color="Black"> </font>'''</span>CLI command to collect more information if you suspect module has been powered down due to errors.

	<div align="left">		<div align="left">

Pravraj: /* Troubleshooting Module Issues */

2010-11-08T08:56:32Z

Troubleshooting Module Issues

← Older revision		Revision as of 08:56, 8 November 2010
Line 1,164:		Line 1,164:

	To isolate a module problem, follow these steps:		To isolate a module problem, follow these steps:
-
	----		----
-		+	<p>1. Verify that all Status LEDs are green. If any status LED is red or off, the module might have shifted out of its slot.</p>
-	1. Verify that all Status LEDs are green. If any status LED is red or off, the module might have shifted out of its slot.	+	<p>2. Reseat the module until both ejector levers are at 90 degrees to the rear of the chassis.</p>
-	2 .Reseat the module until both ejector levers are at 90 degrees to the rear of the chassis.	+	<p>3. Tighten the captive screws at the left and right of the module front panel.</p>
-	3 .Tighten the captive screws at the left and right of the module front panel.	+	<p>4. Restart the system.</p>
-	4 .Restart the system.	+

	If the Status LED on a switching module is orange, the module might be busy or disabled. Refer to the following website for<span class="cXRef_Color" style="font-weight: normal"> </span>the latest Cisco MDS 9000 Family configuration guides to configure or enable the interfaces:<br /><span class="cXRef_Color" style="font-weight: normal">[http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/index.htm http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/index.htm.<br />]</span>After the system reinitializes the interfaces, the Status LED on the module should be green.		If the Status LED on a switching module is orange, the module might be busy or disabled. Refer to the following website for<span class="cXRef_Color" style="font-weight: normal"> </span>the latest Cisco MDS 9000 Family configuration guides to configure or enable the interfaces:<br /><span class="cXRef_Color" style="font-weight: normal">[http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/index.htm http://www.cisco.com/univercd/cc/td/doc/product/sn5000/mds9000/index.htm.<br />]</span>After the system reinitializes the interfaces, the Status LED on the module should be green.

-	5 .If the module does not transition into the online state, see the symptoms listed in this section.	+	<p>5. If the module does not transition into the online state, see the symptoms listed in this section.</p>

	If you are unable to resolve a problem with the startup, gather the information listed under Appendix A, "Before Contacting Technical Support" and contact your technical support representative for assistance as directed in the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section.		If you are unable to resolve a problem with the startup, gather the information listed under Appendix A, "Before Contacting Technical Support" and contact your technical support representative for assistance as directed in the "Obtaining Documentation, Obtaining Support, and Security Guidelines" section.
-
	----		----

Pravraj: /* Analyzing The Logs */

2010-11-08T08:54:59Z

Analyzing The Logs

← Older revision		Revision as of 08:54, 8 November 2010
Line 1,135:		Line 1,135:
	* '''show hardware internal errors'''		* '''show hardware internal errors'''

-	=== Analyzing ~~The~~ Logs ===	+	=== Analyzing the Logs ===

	In some instances, you may need to check other internal logs to verify the cause of a problem. You can use the state transition log and the error log in these instances. These logs may hold information not present in the system messages or in the exception log because of interactions between the module and the supervisor. The state transition log is sorted in ascending manner (that is, the latest state is at the end of the log). The error log is sorted in descending manner (that is, the latest error is at the beginning of the log).		In some instances, you may need to check other internal logs to verify the cause of a problem. You can use the state transition log and the error log in these instances. These logs may hold information not present in the system messages or in the exception log because of interactions between the module and the supervisor. The state transition log is sorted in ascending manner (that is, the latest state is at the end of the log). The error log is sorted in descending manner (that is, the latest error is at the beginning of the log).