Collect switch information and configuration. This should be done before and after the issue has been resolved. The following three methods each provide the same information:
a. Select Tools > Show Tech Support in Fabric Manager. Fabric Manager can capture switch configuration information from multiple switches simultaneously. The file can be saved on the local PC.
b. Configure your Telnet or SSH application to log the screen output to a text file. Use the terminal length 0 CLI command and then use the show tech-support details CLI command.
c. Use the tac-pac CLI command to redirect the output of the show tech-support details CLI command to a file, and then gzip the file. switch# tac-pac bootflash://showtech.switch1
If no filename is specified, the file is created as volatile:show_tech_out.gz. The file should then be copied from the switch using the procedure outlined in the “Copying Files to or from the Switch” section on page A-3.
Step 2 If an error occurs in Fabric Manager, take a screen shot of the error. In Windows, press Alt+PrintScreen to capture the active window, or press only PrintScreen to capture the entire desktop. Then paste this into a new Microsoft Paint (or similar program) session and save the file.
Step 3 Capture the exact error codes you see in the message logs from either Fabric Manager or the CLI.
a. Select the Logs tab in the Map pane in Fabric Manager or choose Switches > Events to see the recent list of messages generated.
b. Copy the error from the message log, which can be displayed using either the show logging log CLI command or the show logging last number to view the last lines of the log.
Step 4 Answer the following questions before calling for technical support:
• On which switch, host bus adapter (HBA), or storage port is the problem occurring?
• Which Cisco SAN-OS software, driver versions, operating systems versions and storage device firmware are in your fabric?
• What is the network topology? (In Fabric Manager, go to Tools > Show Tech Support and check the Save Map check box.)
• Were any changes being made to the environment (zoning, adding modules, upgrades) prior to or at the time of this event?
• Are there other similarly configured devices that could have this problem, but do not?
• Where was this problematic device connected (which MDS switch and interface)?
• When did this problem first occur?
• When did this problem last occur?
• How often does this problem occur?
• How many devices have this problem?
• Were any traces or debug output captured during the problem time? What troubleshooting steps have you attempted? Which, if any, of the following tools were used? – FC Analyzer, PAA-2, Ethereal, local or remote SPAN – CLI debug commands – FC traceroute, FC ping – Fabric Manager or Device Manager tools Send documentation comments to mdsfeedback-doc@cisco.com A-3 Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x OL-9285-05 Appendix A Before Contacting Technical Support Steps to Perform Before Calling TAC
Step 5 Is your problem related to a software upgrade attempt?
• What was the original Cisco SAN-OS version?
• What is the new Cisco SAN-OS version?
• Did you use Fabric Manager or the CLI to attempt this upgrade?
• Please collect the output from the following commands and forward them to your customer support representative: – show install all status – show system internal log install – show system internal log install details – show log nvram
Step 6 If your problem is related to zoning, use the show zone tech-support CLI command to gather relevant information.
Java training in chennai | Oracle training in chennai
