Unsolved
This post is more than 5 years old
1 Rookie
•
100 Posts
0
3616
ESXi 5.0 NPIV issue
Hello,
I have problem with my preprod environment.
I have HP blade with emulex 8 gb FC and 8gb brocade switch.
I want to create "virtual WWNs" on one Virtual mashine and zone them with Datadomain.
When i generate WWNs on "options" tab i can't see them on brocade switch.
Here some logs from ESX:
Emulex LightPulse FC SCSI 8.2.2.105.36
HP BLc Emulex LPe1205-HP 8Gb FC on PCI bus 0000:06 device 00 irq 176 port 0
BoardNum: 0
ESX Adapter: vmhba0
Firmware Version: 2.00A4 (US2.00A4)
Portname: 10:00:00:00:c9:b6:aa:a6 Nodename: 20:00:00:00:c9:b6:aa:a6
SLI Rev: 3
MQ: Unavailable
NPIV Supported: VPIs max 255 VPIs used 0
RPIs max 512 RPIs used 6 IOCBs inuse 0 IOCB max 8 txq cnt 0 txq max 0 txcmplq 0
Vport List:
Link Up - Ready:
PortID 0x10c00
Fabric
Current speed 8G
Port Discovered Nodes: Count 2
t0000 DID 011100 WWPN 50:06:01:69:3e:a0:13:71 WWNN 50:06:01:60:be:a0:13:71 qdepth 8192 max 2 active 0 busy 0
t0001 DID 011200 WWPN 50:06:01:61:3e:a0:13:71 WWNN 50:06:01:60:be:a0:13:71 qdepth 8192 max 3 active 0 busy 0
Emulex LightPulse FC SCSI 8.2.2.105.36
HP BLc Emulex LPe1205-HP 8Gb FC on PCI bus 0000:06 device 01 irq 184 port 1
BoardNum: 1
ESX Adapter: vmhba1
Firmware Version: 2.00A4 (US2.00A4)
Portname: 10:00:00:00:c9:b6:aa:a7 Nodename: 20:00:00:00:c9:b6:aa:a7
SLI Rev: 3
MQ: Unavailable
NPIV Supported: VPIs max 255 VPIs used 0
RPIs max 512 RPIs used 6 IOCBs inuse 0 IOCB max 8 txq cnt 0 txq max 0 txcmplq 0
Vport List:
Link Up - Ready:
PortID 0x10c00
Fabric
Current speed 8G
Port Discovered Nodes: Count 2
t0000 DID 011100 WWPN 50:06:01:68:3e:a0:13:71 WWNN 50:06:01:60:be:a0:13:71 qdepth 8192 max 2 active 0 busy 0
t0001 DID 011200 WWPN 50:06:01:60:3e:a0:13:71 WWNN 50:06:01:60:be:a0:13:71 qdepth 8192 max 2 active 0 busy 0
2012-03-28T19:21:28.977Z cpu8:2188)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L1 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:21:28.977Z cpu8:2188)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L2 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:26:28.979Z cpu12:2188)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L1 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:26:28.979Z cpu12:2188)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L2 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:31:28.979Z cpu12:7523970)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L1 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:31:28.979Z cpu12:7523970)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L2 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:36:28.979Z cpu14:2188)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L1 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:36:28.979Z cpu14:2188)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L2 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:41:28.978Z cpu8:7522243)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L1 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
2012-03-28T19:41:28.978Z cpu8:7522243)WARNING: ScsiClaimrule: 1289: Path vmhba2:C0:T0:L2 is claimed by plugin NMP, but current claimrule number 290 indicates that it should be claimed by plugin PowerPath.
felipon1
96 Posts
0
May 22nd, 2012 04:00
Hi,
I think that your missing some steps. Please, take a look at the following doc about it:
http://blogs.vmware.com/vsphere/2011/11/npiv-n-port-id-virtualization.html
Rgds
Richard_Butler
84 Posts
0
June 22nd, 2012 01:00
Hello,
The setup of NPIV is a little unusual, in that the VMware guest needs to be initially powered off. You then configure fabric zoning and array LUN masking using the NPIV WWNs whilst not currently logged in to the fabric. You then power on the guest, and ESX will ‘bring up‘ the NPIV virtual N_Ports/WWNs. These virtual N_Ports will then FLOGI/FDISC and PLOGI, and FC4 will then attempt to inquire about LUNs behind the storage target (PRLI). At this point, if a LUN cannot be seen, the WWNs will log out (it is worth remembering that it is a requirement of the SCSI protocol that every SCSI target should respond to an inquiry against LUN zero).
So, if you are troubleshooting NPIV WWNs that are absent from the fabric nameserver, power-cycle the guest and keep issuing either a 'show flogi database' or an ‘nsshow‘ command - if you see the WWNs for a few seconds only, then LUN provisioning is quite likely your problem. Basically, provision the zoning and LUN masking ahead of time (physical and virtual), and then the WWNs should not log out.
A common error that I have seen is to provision the RDM device to the ESX server, this then ‘toggles on‘ the ability to generate virtual N_Port WWNs, however, administrators can then subsequently LUN mask LUNs that have not been provisioned as RDM devices.
Best regards, Richard.