Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-75-1020241.1
Update Date:2012-07-10
Keywords:

Solution Type  Troubleshooting Sure

Solution  1020241.1 :   Sun StorageTek[TM] Brocade SAN Switches: Troubleshooting hardware errors external to switch  


Related Items
  • Brocade 200E Switch
  •  
  • Brocade 3850 Fabric Switch
  •  
  • Brocade 3900 Switch
  •  
  • Brocade 5300 Switch
  •  
  • Brocade 5100 Switch
  •  
  • Brocade 48000 Director
  •  
  • Brocade 300 Switch
  •  
  • Brocade 24000 Director
  •  
  • Brocade DCX-4S Backbone
  •  
  • Brocade 12000 Fabric Switch
  •  
  • Brocade 7500 Switch
  •  
  • Brocade 4100 Switch
  •  
  • Brocade 5000 Switch
  •  
  • Brocade DCX Backbone
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Switch>SN-DK: Brocade Switch
  •  
  • _Old GCS Categories>Sun Microsystems>Switches>Brocade
  •  

PreviouslyPublishedAs
254750


Applies to:

Brocade 48000 Director - Version Not Applicable and later
Brocade 12000 Fabric Switch - Version Not Applicable and later
Brocade 200E Switch - Version Not Applicable and later
Brocade 24000 Director - Version Not Applicable and later
Brocade 300 Switch - Version Not Applicable and later
All Platforms

Purpose

 The SAN device (host or storage) is logging HW error messages and/or experiencing connectivity issues.

Symptoms

  • Access fails to LUNs

  • Host log file contains offline/online error messages

  • Host log file contains plogi/flogi error messages

  • Host log file contains disappeared/reappeared error messages

  • errdump contains Fabric Watch link messages

Troubleshooting Steps

Steps to Follow
Sun StorageTek[TM] Brocade Series SAN Switches: Troubleshooting hardware errors external to switch.

1. Verify HW is physically connected.

2. Check for error lights on switch. Refer to HW guide for specific switch and instructions.

3. Check zoning configuration to ensure initiator and target pair are properly zoned together. Refer to Technical Instruction: <Document: 1020237.1 >

4. Run nsshow on switches the devices are attached to and verify PWWNs of the suspect devices show up in the output.

5. Run "porterrshow", "uptime", and "errdump" commands on switch or inspect these command outputs in a supportshow or supportsave and look for link issues on affected port/s. Refer to Technical Instruction: <Document: 1020239.1> 

6. Collect the supportsave (or supportshow for FOS 3.x switches) along with SAN topology per Technical Instruction <Document: 1003754.1> to prepare for a support case or escalation.

7. At this point, if you not been able to resolve the issue with the troubleshooting steps above, further troubleshooting is required. Contact Oracle Support and be prepared to provide the data collected in the above steps.


Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback