| Asset ID: |
1-72-1276184.1 |
| Update Date: | 2017-05-19 |
| Keywords: | |
Solution Type
Problem Resolution Sure
Solution
1276184.1
:
IBM LTO 5 - Drive Failures When Logging into Brocade as F-Port
| Related Items |
- Brocade 5300 Switch
- Brocade 5100 Switch
- Brocade 300 Switch
- Brocade DCX-4S Backbone
- IBM LTO5 Tape Drive
- Brocade DCX Backbone
|
| Related Categories |
- PLA-Support>Sun Systems>TAPE>Tape Hardware>SN-TP: OEM Drive and Library
|
In this Document
Applies to:
Brocade 5100 Switch - Version Not Applicable and later
IBM LTO5 Tape Drive - Version Not Applicable and later
Brocade 300 Switch - Version Not Applicable and later
Brocade 5300 Switch - Version Not Applicable and later
Brocade DCX Backbone - Version Not Applicable and later
Information in this document applies to any platform.
Checked for relevance on 27-Mar-2013.
Symptoms
IBM LTO5 drive with A5R0 f/w: The drive will log into all switches and blades and will negotiate a F-port login.
"IBM LTO5 drive with code A9Q5 and later will now try to log into the switch port as a "Fabric Loop" or "FL" device and thus will be reported to the host by the switch with a different FCID and thus would be seen by the host as a completely different drive on the host. This could cause the customer to have to reconfigure their backup application for all of the drives. If the drives "FL" log in is rejected by the switch the drive will then try to log into the switch port as a "Fabric" or "F" device.
Any 8G capable Brocade switch will see the issue.
Those include:
Brocade 300
Brocade 5100
Brocade 5300
Brocade DCX-4S
Brocade DCX
Changes
NA
Cause
The issue with this is, if a customer has a host already configured to an IBM LTO5 tape drive prior to upgrading it to A6S0, or later, 2 things might happen:
1.) If connected to the Brocade DCX or DCX-4S director on the 48 or 64 port line card, the device will not log-in to the fabric and will be unusable by the host/application.
2.) If connected to the Brocade 300/5100/5300 edge switches or DCX/DCX-4S blades that permit FL-port log-ins, the devices FCID changes and those hosts that build the OS device file based upon the FCID (HP-UX and Windows based servers are most effected...) will see this tape drive as a new drive. At this point, the drive is useless to the host and application until both are reconfigured.
Solution
Customers should force the ports on their Brocade switches to "G" ports and the drives will be forced to log in as "F" devices and thus the FCID won't change for those drives won't change.
Attachments
This solution has no attachment
