Sun System Handbook - ISO 3.4 June 2011 Internal/Partner Edition | |||
|
|
Solution Type Problem Resolution Sure Solution 1002168.1 : Mixing Fibre Channel HBA types on private-loop configurations can cause loop offline/timeouts.
PreviouslyPublishedAs 203073 Symptoms Mixing the following combinations of Fibre Channel Host Bus Adapters (HBA) on private-loop configurations may cause loop offlines/timeouts:
Resolution The resolution is to use the same type of HBA for each initiator/host on the private loop and to ensure that the HBA is qualified with the host/storage combination. For example, if there are SOC+ HBAs then ensure that there are no other types of HBAs on the same private-loop. For example, if there are ISP2100 HBAs then ensure that there are no other types of HBAs on the same private-loop. Additional Information These combinations of HBAs when connected on the same physical private-loop can cause offlines or timeouts: SOC+ with any Sun SAN HBA All of the above HBAs can operate in 'private-loop' mode (Sun SAN HBAs also work in fabric or switch attached) however, certain operating differences can lead to offlines or timeouts if mixed types are connected on the same physical 'private-loop'. Definitions.
HBA identification can be achieved by looking at the driver path within 'format' or using luxadm -e port. SOC+,ISP2100 and Sun SAN HBAs use different kernel drivers. SOC+ will use SUNW,socal This issue affects only private-loop configurations. Product Sun StorageTek A5200 Array Sun StorageTek A5100 Array Sun StorageTek A5000 Array Sun StorageTek T3+ Array Sun StorageTek T3 Array FC100, luxadm, HBA, private-loop Previously Published As 81279 Change History Date: 2005-05-04 User Name: 25440 Action: Approved Comment: Publishing. Version: 3 Date: 2005-05-04 User Name: 25440 Action: Accept Comment: Version: 0 Date: 2005-05-04 User Name: 34660 Action: Approved Comment: reworked. Attachments This solution has no attachment |
||||||||||||
|