McData - What logs are required to troubleshoot a McData switch?

Asset ID:	1-75-1015572.1
Update Date:	2018-01-01
Keywords:

Solution Type Troubleshooting Sure

Solution 1015572.1 : McData - What logs are required to troubleshoot a McData switch?

Related Items


McDATA Eclipse 1620 SAN Router
 McData Sphereon 4500 Fabric Switch
 McData Intrepid 6140 Director
 McData Intrepid 10000 (i10K) Director
 McData Sphereon 4700 Fabric Switch
 McData Sphereon 4300 Fabric Switch
 McData Intrepid 6064 Director
 McData 3232 Switch

Related Categories


PLA-Support>Sun Systems>DISK>Switch>SN-DK: McData Switch
 _Old GCS Categories>Sun Microsystems>Switches>McData

PreviouslyPublishedAs
223989

Applies to:

McData Intrepid 6140 Director - Version Not Applicable to Not Applicable [Release N/A]
McData Intrepid 10000 (i10K) Director - Version Not Applicable to Not Applicable [Release N/A]
McData Intrepid 6064 Director - Version Not Applicable to Not Applicable [Release N/A]
McDATA Eclipse 1620 SAN Router - Version Not Applicable to Not Applicable [Release N/A]
McData 3232 Switch - Version Not Applicable to Not Applicable [Release N/A]
All Platforms

Purpose

What logs are required to troubleshoot a McData switch?

Troubleshooting Steps

The support logs required by support to troubleshoot McData switch problems vary depending on whether the customer has an EFCM server running or not.
If the customer is running an EFCM server, the troubleshooting data required is called a Data Collection and can be gathered from the EFCM server. Please refer to KB Document: 1018352.1 for the detailed procedure on how to gather this file.

If the customer does not have an EFCM server, support will require two different text files from the browser gui (called SAN Pilot.) The two necessary files are called Log_information.txt and product_information.txt and can be gathered by the process detailed in Document 1015627.1

Previously Published As
STKKB57881

Attachments

This solution has no attachment