07-15-2015 08:54 AM
I am new to using Brocade SAN switches so I'm not sure how to troubleshoot an issue that we have.
We have a new HP C7000 with BL460 blades which are all on the very latest HP firmware including the VC's and OA's. We are also using the HP ESXi 5.5 image with the latest reccomended driver for the FC connectivity. Our Brocade SLKWRM 300 SAN switch is running the 7.3.1 firmware version. The issue that we have is that some of the WWN's display the Device Name but some don't. The ones that show up ok show the manufacturer Emulex with other information and the WWN but some of them only display the WWN.
Could anyone assist with this please?
Solved! Go to Solution.
07-16-2015 12:42 AM
general windows servers will add their hostname to the wwn, this is a driver thingy
its looks like this
NodeSymb:  "Emulex LPe1205-HP FV2.01A4 DV10.2.261.4 "serverhostname"
linux or aix servers dont do that
you could try to name the HBA in the bios, if the hba supports that.
otherwise this information is redundant and not necessary to run the SAN
07-16-2015 01:43 AM
Thanks for the posts so far.
I ran the command nodefind followed by the WWN and I got the same information on one of the WWN's show shows the device name but with the following differences.
Device type: NPIV Unknown(initiator/target)
And on the ones that displays all the information it had another paremeter as below.
The WWN that doesn't show the device name doesn't get detected by the SAN. I have manually entered the WWN into the SAN when trying to add the host but it says the paths are disconnected. The strange thing is that all of the hosts are running the same firmware and driver versions but some show the device name and some don't. The ones that do show the device name can be seen by the SAN.
07-22-2015 04:39 AM
I have found when I use one uplink port from our C7000 to the switch it works but not when I use 2. Any ideas? I have disabled one connection and tested and everything worked ok so I disabled the 2nd and enabled the 1st connection again and still fine. When I had both connections enabled that's when I got the issue again.
07-27-2015 08:46 AM
The issue is now fixed. We had to downgrade the firmware as advised by HP.