Cisco MDS SanOS Troubleshooting Guide -- Troublelshooting Tools and Methodology - Revision history

Pravraj: /* Using Host Diagnostic Tools */

2010-11-08T09:35:50Z

Using Host Diagnostic Tools

← Older revision		Revision as of 09:35, 8 November 2010
Line 1,414:		Line 1,414:
	PostMark generates an initial pool of random text files in a configurable range of sizes. Creation of the pool produces statistics on continuous small file creation performance. Once the pool is created, PostMark generates a specified number of transactions, each of which consists of a pair of smaller transactions:		PostMark generates an initial pool of random text files in a configurable range of sizes. Creation of the pool produces statistics on continuous small file creation performance. Once the pool is created, PostMark generates a specified number of transactions, each of which consists of a pair of smaller transactions:

-	* Create file or ~~Delete~~ file	+	* Create file or delete file
-	* Read file or ~~Append~~ file	+	* Read file or append file

	Benchmarking tools offer a variety of capabilities and you should select the one that provides the best I/O characteristics of your application environment.		Benchmarking tools offer a variety of capabilities and you should select the one that provides the best I/O characteristics of your application environment.

Pravraj: /* Fibre Channel Protocol Analyzers */

2010-11-08T09:35:22Z

Fibre Channel Protocol Analyzers

← Older revision		Revision as of 09:35, 8 November 2010
Line 1,385:		Line 1,385:
	=== Fibre Channel Protocol Analyzers ===		=== Fibre Channel Protocol Analyzers ===

-	An external protocol analyzer (for example from Finisar), ~~is capable of capturing~~ and ~~decoding~~ link level issues and ~~the fibre channel~~ ordered sets ~~which~~ comprise the ~~fibre channel~~ frame. The Cisco MDS 9000 Family Port Analyzer Adapter, does not capture and decode at the ordered set level.	+	An external protocol analyzer (for example, from Finisar), can capture and decode link-level issues and Fibre Channel ordered sets that comprise the Fibre Channel frame. The Cisco MDS 9000 Family Port Analyzer Adapter, does not capture and decode at the ordered set level.

-	A Fibre Channel protocol analyzer captures transmitted information from the physical layer of the Fibre Channel network. Because these devices are physically located on the network instead of at a software ~~re-assembly~~ layer like most Ethernet analyzers, Fibre Channel protocol analyzers can monitor data from the 8b/10b level all the way to the embedded upper-layer protocols.	+	A Fibre Channel protocol analyzer captures transmitted information from the physical layer of the Fibre Channel network. Because these devices are physically located on the network instead of at a software reassembly layer like most Ethernet analyzers, Fibre Channel protocol analyzers can monitor data from the 8b/10b level all the way to the embedded upper-layer protocols.

	Fibre Channel network devices (HBAs, switches, and storage subsystems) are not able to monitor many SAN behavior patterns. Also, management tools that gather data from these devices are not necessarily aware of problems occurring at the Fibre Channel physical, framing, or SCSI upper layers for a number of reasons.		Fibre Channel network devices (HBAs, switches, and storage subsystems) are not able to monitor many SAN behavior patterns. Also, management tools that gather data from these devices are not necessarily aware of problems occurring at the Fibre Channel physical, framing, or SCSI upper layers for a number of reasons.

Pravraj: /* Cisco MDS 9000 Family Port Analyzer Adapter */

2010-11-08T09:33:40Z

Cisco MDS 9000 Family Port Analyzer Adapter

← Older revision		Revision as of 09:33, 8 November 2010
Line 1,236:		Line 1,236:
	=== Cisco MDS 9000 Family Port Analyzer Adapter ===		=== Cisco MDS 9000 Family Port Analyzer Adapter ===

-	The Cisco MDS 9000 Family Port Analyzer Adapter is a stand-alone adapter card that converts Fibre Channel frames to Ethernet frames by encapsulating each Fibre Channel frame into an Ethernet frame. This product is meant to be used for analyzing SPAN traffic from a Fibre channel port on a Cisco MDS 9000 Family switch.	+	The Cisco MDS 9000 Family Port Analyzer Adapter is a stand alone adapter card that converts Fibre Channel frames to Ethernet frames by encapsulating each Fibre Channel frame into an Ethernet frame. This product is meant to be used for analyzing SPAN traffic from a Fibre channel port on a Cisco MDS 9000 Family switch.

	The Cisco MDS 9000 Family Port Analyzer Adapter provides two physical interfaces:		The Cisco MDS 9000 Family Port Analyzer Adapter provides two physical interfaces:
	* A Fiber Channel interface that connects to the SPAN port of a Cisco MDS 9000 Family switch		* A Fiber Channel interface that connects to the SPAN port of a Cisco MDS 9000 Family switch
-	* A 100/1000 Mb/s Ethernet port that forwards the encapsulated Fibre Channel traffic with a broadcast destination MAC ~~Address~~	+	* A 100/1000 Mb/s Ethernet port that forwards the encapsulated Fibre Channel traffic with a broadcast destination MAC address

	----		----

Pravraj: /* Using Fibre Channel SPAN */

2010-11-08T09:32:54Z

Using Fibre Channel SPAN

← Older revision		Revision as of 09:32, 8 November 2010
Line 1,198:		Line 1,198:
	To use a protocol analyzer, you must insert the analyzer in-line with the device under analysis, which disrupts input and output (I/O) to and from the device. This problem is worse when the point of analysis is on an Inter-Switch Link (ISL) link between two switches. In this case, the disruption may be significant depending on what devices are downstream from the severed ISL link.		To use a protocol analyzer, you must insert the analyzer in-line with the device under analysis, which disrupts input and output (I/O) to and from the device. This problem is worse when the point of analysis is on an Inter-Switch Link (ISL) link between two switches. In this case, the disruption may be significant depending on what devices are downstream from the severed ISL link.

-	In Ethernet networks, this problem can be solved using the SPAN utility, which is provided with the Cisco Catalyst Family of Ethernet switches. SPAN has also been implemented with the Cisco MDS 9000 Family switches for use in Fibre Channel networks. SPAN lets you take a <span style="font-weight: normal">''<font color="Black">copy</font>''</span> of all traffic and direct it to another port within the switch. The process is non-disruptive to any connected devices and is facilitated in hardware, which prevents any unnecessary CPU load. Using Fibre Channel SPAN, you can connect a Fibre Channel analyzer, such as a Finisar analyzer, to an unused port on the switch and then SPAN a copy of the traffic from a port under analysis to the analyzer in a non-disruptive fashion.	+	In Ethernet networks, this problem can be solved using the SPAN utility, which is provided with the Cisco Catalyst Family of Ethernet switches. SPAN has also been implemented with the Cisco MDS 9000 Family switches for use in Fibre Channel networks. SPAN lets you take a <span style="font-weight: normal">''<font color="Black">copy</font>''</span> of all traffic and direct it to another port within the switch. The process is non disruptive to any connected devices and is facilitated in hardware, which prevents any unnecessary CPU load. Using Fibre Channel SPAN, you can connect a Fibre Channel analyzer, such as a Finisar analyzer, to an unused port on the switch and then SPAN a copy of the traffic from a port under analysis to the analyzer in a non disruptive fashion.

-	SPAN allows you to create up to 16 independent <span style="font-weight: normal">''<font color="Black">SPAN</font>''</span> sessions within the switch. Each session can have up to four unique sources and one destination port. In addition, you can apply a filter to capture only the traffic received or the traffic transmitted. With Fibre Channel SPAN, you can even capture<span style="font-weight: normal">''<font color="Black"> </font>''</span>traffic from a particular Virtual SAN (VSAN).	+	SPAN allows you to create up to 16 independent <span style="font-weight: normal"><font color="Black">SPAN</font></span> sessions within the switch. Each session can have up to four unique sources and one destination port. In addition, you can apply a filter to capture only the traffic received or the traffic transmitted. With Fibre Channel SPAN, you can even capture<span style="font-weight: normal">''<font color="Black"> </font>''</span>traffic from a particular Virtual SAN (VSAN).

	To start the SPAN utility use the CLI command <span style="font-style: normal">'''<font color="Black">span session </font>'''</span><span style="font-weight: normal">''<font color="Black">session_num</font>''</span>, where <span style="font-weight: normal">''<font color="Black">session_num</font>''</span> identifies a specific SPAN session. When you enter this command, the system displays a submenu, which lets you configure the destination interface and the source VSAN or interfaces.		To start the SPAN utility use the CLI command <span style="font-style: normal">'''<font color="Black">span session </font>'''</span><span style="font-weight: normal">''<font color="Black">session_num</font>''</span>, where <span style="font-weight: normal">''<font color="Black">session_num</font>''</span> identifies a specific SPAN session. When you enter this command, the system displays a submenu, which lets you configure the destination interface and the source VSAN or interfaces.

Pravraj: /* Logging Levels */

2010-11-08T09:31:45Z

Logging Levels

← Older revision		Revision as of 09:31, 8 November 2010
Line 1,148:		Line 1,148:
	=== Logging Levels ===		=== Logging Levels ===

-	~~The~~ MDS supports the following logging levels:	+	MDS supports the following logging levels:
	* 0-emergency		* 0-emergency
	* 1-alert		* 1-alert

Pravraj: /* SNMP and RMON Support */

2010-11-08T09:31:25Z

SNMP and RMON Support

Pravraj: /* Fabric Manager and Device Manager */

2010-11-08T09:29:42Z

Fabric Manager and Device Manager

← Older revision		Revision as of 09:29, 8 November 2010
Line 945:		Line 945:
	[[Image:B-2.jpg]]		[[Image:B-2.jpg]]

-	The Summary View window lets you analyze switch performance issues, diagnose problems, and change parameters to resolve problems or inconsistencies. This view shows aggregated statistics for the active ~~Supervisor Module~~ and all switch ports. Information is presented in tabular or graphical formats, with bar, line, area, and pie chart options. You can also use the Summary View to capture the current state of information for export to a file or output to a printer.	+	The Summary View window lets you analyze switch performance issues, diagnose problems, and change parameters to resolve problems or inconsistencies. This view shows aggregated statistics for the active supervisor module and all switch ports. Information is presented in tabular or graphical formats, with bar, line, area, and pie chart options. You can also use the Summary View to capture the current state of information for export to a file or output to a printer.

	=== Analyzing Switch Device Health ===		=== Analyzing Switch Device Health ===

Pravraj: /* Fabric Manager Tools */

2010-11-08T09:29:09Z

Fabric Manager Tools

← Older revision		Revision as of 09:29, 8 November 2010
Line 926:		Line 926:

	----		----
-	{{Note \| For detailed information about using Cisco Fabric Manager, refer to the Cisco MDS 9000 Family Fabric Manager Configuration Guide.}}	+	{{Note \| For detailed information about using Cisco Fabric Manager, refer to the ''Cisco MDS 9000 Family Fabric Manager Configuration Guide''.}}
	----		----

Pravraj: /* Displaying OBFL Logs */

2010-11-08T09:28:47Z

Displaying OBFL Logs

← Older revision		Revision as of 09:28, 8 November 2010
Line 884:		Line 884:
	\|- align="left" valign="top"		\|- align="left" valign="top"
	\|		\|
-	show logging onboard obfl-history	+	'''show logging onboard obfl-history'''
	\|		\|
	Displays history information.		Displays history information.
Line 904:		Line 904:
	\|- align="left" valign="top"		\|- align="left" valign="top"
	\|		\|
-	show logging onboard system-health	+	'''show logging onboard system-health'''
	\|		\|
	Displays system health information.		Displays system health information.

Pravraj: /* Configuring OBFL for a Module */

2010-11-08T09:27:47Z

Configuring OBFL for a Module

← Older revision		Revision as of 09:27, 8 November 2010
Line 727:		Line 727:
	=== Configuring OBFL for a Module ===		=== Configuring OBFL for a Module ===

-	To configure OBFL for specific modules on the switch, follow these steps	+	To configure OBFL for specific modules on the switch, follow these steps:

	<div align="left">		<div align="left">
Line 798:		Line 798:

	</div>		</div>
-		+	<p></p>
	Use the '''show logging onboard status''' command to display the configuration status of OBFL.		Use the '''show logging onboard status''' command to display the configuration status of OBFL.

← Older revision		Revision as of 09:31, 8 November 2010
Line 1,078:		Line 1,078:

	Cisco MDS 9000 Family switches support over 50 different MIBs, which can be divided into the following six categories:		Cisco MDS 9000 Family switches support over 50 different MIBs, which can be divided into the following six categories:
-	* IETF Standards-based Entity MIBs (for example, RFC273óENTITY-MIB)ó	+	* IETF Standards-based Entity MIBs (for example, RFC273óENTITY-MIB)
	: These MIBs are used to report information on the physical devices themselves in terms of physical attributes etc.		: These MIBs are used to report information on the physical devices themselves in terms of physical attributes etc.
-	* Cisco-Proprietary Entity MIBs (for example, CISCO-ENTITY-FRU-CONTROL-MIB)ó	+	* Cisco-Proprietary Entity MIBs (for example, CISCO-ENTITY-FRU-CONTROL-MIB)
	: These MIBs are used to report additional physical device information about Cisco-only devices such as their configuration.		: These MIBs are used to report additional physical device information about Cisco-only devices such as their configuration.
-	* IETF IP Transport-oriented MIBs (for example, RFC2013óUDP-MIB)ó	+	* IETF IP Transport-oriented MIBs (for example, RFC2013óUDP-MIB)
-	: These MIBs are used to report transport-oriented statistics on such protocols as IP, TCP, and UDP. These transports are used in the management of the Cisco MDS 9000 Family through the OOB Ethernet interface on the ~~Supervisor~~ module.	+	: These MIBs are used to report transport-oriented statistics on such protocols as IP, TCP, and UDP. These transports are used in the management of the Cisco MDS 9000 Family through the OOB Ethernet interface on the supervisor module.
	* Cisco-Proprietary Storage and Storage Network MIBs (for example, NAME-SERVER-MIB)		* Cisco-Proprietary Storage and Storage Network MIBs (for example, NAME-SERVER-MIB)
-	: These MIBs were written by Cisco to help expose information that is discovered within a fabric to management applications not connected to the fabric itself. In addition to exposing configuration details for features like zoning and ~~Virtual~~ SANs (VSANs) via MIBs, discovered information from sources like the FC-GS-3 Name Server can be pulled via a MIB. Additionally, MIBs are provided to configure/enable features within the Cisco MDS 9000 Family. There are over 20 new MIBs provided by Cisco for this information and configuration capability.	+	: These MIBs were written by Cisco to help expose information that is discovered within a fabric to management applications not connected to the fabric itself. In addition to exposing configuration details for features like zoning and virtual SANs (VSANs) via MIBs, discovered information from sources like the FC-GS-3 Name Server can be pulled via a MIB. Additionally, MIBs are provided to configure/enable features within the Cisco MDS 9000 Family. There are over 20 new MIBs provided by Cisco for this information and configuration capability.
	* IETF IP Storage Working Group MIBs (for example, ISCSI-MIB)		* IETF IP Storage Working Group MIBs (for example, ISCSI-MIB)
	: While many of these MIBs are still work-in-progress, Cisco is helping to draft such MIBs for protocols such as iSCSI and Fibre Channel-over-IP (FCIP) to be standardized within the IETF.		: While many of these MIBs are still work-in-progress, Cisco is helping to draft such MIBs for protocols such as iSCSI and Fibre Channel-over-IP (FCIP) to be standardized within the IETF.
	* Miscellaneous MIBs (for example, SNMP-FRAMEWORK-MIB)		* Miscellaneous MIBs (for example, SNMP-FRAMEWORK-MIB)
	: There are several other MIBs provided in the Cisco MDS 9000 Family switches for tasks such as defining the SNMP framework or creating SNMP partitioned views.		: There are several other MIBs provided in the Cisco MDS 9000 Family switches for tasks such as defining the SNMP framework or creating SNMP partitioned views.
-	: These MIBs are used to report transport-oriented statistics on such protocols as IP, TCP, and UDP. These transports are used in the management of the Cisco MDS 9000 Family through the OOB Ethernet interface on the ~~Supervisor~~ module.	+	: These MIBs are used to report transport-oriented statistics on such protocols as IP, TCP, and UDP. These transports are used in the management of the Cisco MDS 9000 Family through the OOB Ethernet interface on the supervisor module.

	You can use SNMPv3 to assign different SNMP capabilities to specific roles.		You can use SNMPv3 to assign different SNMP capabilities to specific roles.
Line 1,099:		Line 1,099:

	----		----
-	{{Note \| To configure events within an RMON group, use the Events > Threshold Manager option from Device Manager. See the "Device Manager: RMON Threshold Manager" section. }}	+	{{Note \| To configure events within an RMON group, use the '''Events''' > '''Threshold Manager''' option from Device Manager. See the "Device Manager: RMON Threshold Manager" section. }}
	----		----