Here is a situation:
We been using 2 dual port HBA card, initially using only one port from the host for storage. Started setting up second port to connect to the second storage and found out the one the HBA card is bad. Got that replaced. All the 4 ports are online now. The brocade sees all the WWNs from the FC cards and cards on the hosts shows online as well.
bash-3.00# fcinfo hba-port -l | grep -i state
State: online
State: online
State: online
State: online
Now we run luxadm -e port and only one port is communicating. After replacing the card we updated the Brocade with new WWN of the first port which was already in use. Also, zoned the second port from both the FC to the second storage. So, we were expecting atleast 2 ports communicating as before.
Why luxadm is showing the card is not connect ??
bash-3.00# luxadm -e port
/devices/pci@0/pci@0/pci@8/pci@0/pci@2/SUNW,qlc@0/fp@0,0:devctl NOT CONNECTED
/devices/pci@0/pci@0/pci@8/pci@0/pci@2/SUNW,qlc@0,1/fp@0,0:devctl NOT CONNECTED
/devices/pci@0/pci@0/pci@8/pci@0/pci@8/SUNW,qlc@0,1/fp@0,0:devctl NOT CONNECTED
/devices/pci@0/pci@0/pci@8/pci@0/pci@8/SUNW,qlc@0/fp@0,0:devctl CONNECTED
Before we go into the further troubleshooting mode. I just wanted to understand what is "NOT CONNECTED" means
## “luxadm -e port” command is used to verify HBA has established communication with a node.
# luxadm -e port
/devices/pci@1f,4000/SUNW,qlc@4/fp@0,0:devctl CONNECTED /devices/pci@1f,4000/SUNW,qlc@4,1/fp@0,0:devctl CONNECTED
NOTE:
”CONNECTED” means the HBA has established a communications with some other node (Initiator or Target). ”NOT CONNECTED” means the HBA has not established a communication with some other node or connecting to a switch that has no target (including not zoned to a target).
Now to our understanding we have verified switch and everything looks good.
Findings:
When the HBA went bad, it automatically took the WWN (zone member) out of the zone. That was the reason for second port in "NOT CONNECTED" state
Everything was correct for the second ports configured for the other storage, But unfortunately it was not added to the zone group. If you are familiar with Brocade GUI (sorry never tried the command line with FC zoning), the last part is to add the newly created to the zone group after you create aliases and zones
Bottomline, If the HBAs are online its most likely the switch problem when we see "NOT CONNECTED" state.
