topic Re: Virtual Connect showing wrong WWN in BladeSystem - General

Virtual Connect showing wrong WWN

Jacky Wing — Thu, 12 Jun 2008 09:45:27 GMT

Hi,

I have a BL460 servers with HBA installed. after installing HBAnyware(Emulex HBA) I checked the WWN. These servers are connected to an MSA1000 with Brocade switches. Everything looks fine, I can see the MSA from the servers and everything is fine. However when trying to Zone my fabric, I saw that i have the WWN reported from the servers. In virtual connect I setup my servers to use a predefined WWN, these predefined WWN does not show in my SAN Switch.
- I upgraded the FW of Emulex HBA.
- I reapplied profiles
- I restarted servers and switches

Same result all the time. It is not required to use the predefined WWNs however it will be faster for recovery in case any problem happens.

Do you have any idea?
Another question, is it better to enable HBA Bios? I don't want to boot from SAN.

Another question? My San switches each has a domain ID of 1, they are not interconnected, two different fabrics. should I change domain ID. my virtual connect switches each go to one SAN Switch.

Re: Virtual Connect showing wrong WWN

JKytsi — Thu, 12 Jun 2008 18:13:14 GMT

Is Your SAN switch NPIV capable ? Check from switch specs. You can check with switchshow command the status of the port.

Don't enable BIOS if You are not booting from SAN.

Assign unique domain ID's to switches. It is the best practice.

Re: Virtual Connect showing wrong WWN

Jacky Wing — Thu, 12 Jun 2008 23:50:42 GMT

Will check that tomorrow morning. I have reapplied different profiles with the original WWN. will check the NPIV thing tomorrow.
Thank you.

Re: Virtual Connect showing wrong WWN

Jacky Wing — Thu, 19 Jun 2008 14:29:25 GMT

NPIV is enabled on the switch. I am still with the same problem. The WWN are the one coming from the servers not the VC range.

Re: Virtual Connect showing wrong WWN

Blazhev_1 — Thu, 19 Jun 2008 19:29:16 GMT

Hi,

it seems to me like a firmware problem.
Did you update the server BIOSes and the VC FC modules firmwares also?
In the FC HBA's BIOS is the WWN changed or not - so we will see if the problem is VC or the SAN Switch.

Be sure the blade is powered off when you assign the profile, when it powers on, the VC will assign it WWN.

regards

Re: Virtual Connect showing wrong WWN

kevin leong — Thu, 04 Dec 2008 09:43:54 GMT

HI ,

I have a same problem as well .I ready done all the server , SAN switch , anf VC firmware update to latest firmware .

Somehow , on my EVA does not appear WWN provide from VC .Any idea ? Please help

Thanks
LeongKO

Re: Virtual Connect showing wrong WWN

Terri Harris — Mon, 22 Dec 2008 16:13:31 GMT

Is NPIV really successfully enabled? If it is, in SWITCHSHOW for Brocade the last column must show something like "5 NPIV PUBLIC" and not a single WWN address.

Also, in portshow, the portFlag field must include NPIV.
\
Note: portcfgshow makes it look like NPIV is On/Enabled for every port. Its not. You must use the portcfgnpivport command to manually enable each port. And if this is the first time you've enabled any port on the given Brocade switch, you must reboot the switch.
Example:

portcfgnpivport 3,1 enables NPIV for port #3

Brocade fw must be at least 5.2.1(b) in order for NPIV to work properly with Virtual Connect.