NPIV is Enabled on a Brocade SAN Switch and Two Sets of Virtual Fabric WWPNs have been configured on Microsoft Hyper-VM, But Only One Set of WWPNs is Visible and Other Set is Not Visible.

Asset ID:	1-72-2020015.1
Update Date:	2015-11-23
Keywords:

Solution Type Problem Resolution Sure

Solution 2020015.1 : NPIV is Enabled on a Brocade SAN Switch and Two Sets of Virtual Fabric WWPNs have been configured on Microsoft Hyper-VM, But Only One Set of WWPNs is Visible and Other Set is Not Visible.

Applies to:

Brocade 5300 Switch - Version Not Applicable and later
Information in this document applies to any platform.

Symptoms

NPIV is enabled on a Brocade SAN Switch and two sets of Virtual Fabric WWPNs have been configured on Microsoft Hyper-VM, but only one set of WWPNs is visible and other set is not visible.

Changes

Hyper-V automatically alternates between the Set A and Set B WWN addresses during a live migration. This ensures that all LUNs are available on the destination host before the migration and that no downtime occurs during the migration

Cause

To support live migration of VMs across Hyper-V hosts while maintaining Fibre Channel connectivity, two WWPNs are configured for each virtual Fibre Channel adapter Set A and Set B as shown in the following screen shots.

SAN1

SAN2

Here we can observe these Virtual WWPNs for FC Host Adapters SAN1 and SAN2.

SAN1

Address Set A: WWPN C003FFE7C3D5001E
Address Set B: WWPN C003FFE7C3D5001F

SAN2

Address Set A: WWPN C003FFE7C3D50020
Address Set B: WWPN C003FFE7C3D50021

The WWPNs for Address Set A in the case of both SAN1 and SAN2 are not visible on their respective Brocade Switches.

Reviewing each supportsave capture neither C003FFE7C3D5001E or C003FFE7C3D50020 have logged into their respective Brocade Switch and consequently have not registered with the name server.

For the first Brocade Switch these 4 Ports have NPIV devices connected.

  32 32 052c00 id N8 Online FC F-Port 1 N Port + 3 NPIV public
  33 33 052000 id N8 Online FC F-Port 1 N Port + 7 NPIV public
  36 36 055900 id N8 Online FC F-Port 1 N Port + 2 NPIV public
  37 37 052400 id N8 Online FC F-Port 1 N Port + 6 NPIV public

Inspecting each of these Ports to show the WWPNs of the connected devices shows that C003FFE7C3D50021 is connected to Port Number 37.

portWwn of device(s) connected:
  c0:03:ff:e7:c3:d5:00:0f
  c0:03:ff:49:86:aa:00:03
  50:06:0b:00:00:c2:6e:0a
  20:00:b4:99:ba:28:1d:eb

portWwn of device(s) connected:
  c0:03:ff:e7:c3:d5:00:24
  c0:03:ff:0e:19:1f:00:09
  c0:03:ff:0e:19:1f:00:0d
  50:06:0b:00:00:c2:72:06
  c0:03:ff:8a:89:fa:00:0a
  50:06:0b:00:00:c2:72:0e
  50:06:0b:00:00:c2:72:16
  20:00:b4:99:ba:28:1d:fb

portWwn of device(s) connected:
  c0:03:ff:e7:c3:d5:00:0a
  50:06:0b:00:00:c2:6e:26
  20:11:b4:99:ba:28:1d:eb

portWwn of device(s) connected:
  c0:03:ff:e7:c3:d5:00:21   c0:03:ff:8a:89:fa:00:0f
  c0:03:ff:0e:19:1f:00:02
  50:06:0b:00:00:c2:72:02
  50:06:0b:00:00:c2:72:0a
  50:06:0b:00:00:c2:72:12
  20:11:b4:99:ba:28:1d:fb

portloginshow for this Port confirms the successful login.

portloginshow 37
Type PID World Wide Name credit df_sz cos
=====================================================
  fd 05241b c0:03:ff:e7:c3:d5:00:21 16 2112 c scr=0x3
  ff 05241b c0:03:ff:e7:c3:d5:00:21 0 0 8 d_id=FFFFFA
  ff 05241b c0:03:ff:e7:c3:d5:00:21 0 0 8 d_id=FFFFFC

And the device is registered with the name server.

N 05241b; 2,3;c0:03:ff:e7:c3:d5:00:21;c0:03:ff:00:00:ff:ff:00; 0x00000003
  FC4s: FCP
  PortSymb: [64] "Hyper-V VM Port................................................."
  NodeSymb: [34] "QMH2572 FW:v7.00.02 DVR:v9.1.11.24"
  Fabric Port Name: 20:25:00:05:33:dc:42:4a
  Permanent Port Name: 20:11:b4:99:ba:28:1d:fb
  Port Index: 37
  Share Area: No
  Device Shared in Other AD: No
  Redirect: No
  Partial: No
  LSAN: No

These 4 Ports have NPIV devices connected.

  33 33 042c00 id N8 Online FC F-Port 1 N Port + 3 NPIV public
  37 37 042000 id N8 Online FC F-Port 1 N Port + 7 NPIV public
  40 40 042800 id N8 Online FC F-Port 1 N Port + 3 NPIV public
  44 44 042400 id N8 Online FC F-Port 1 N Port + 5 NPIV public

Inspecting each of these Ports to show the WWPNs of the connected devices shows that C003FFE7C3D5001F is connected to Port Number 44.

portWwn of device(s) connected:
  20:00:b4:99:ba:28:29:02
  50:06:0b:00:00:c2:6e:08
  c0:03:ff:49:86:aa:00:01
  c0:03:ff:e7:c3:d5:00:0d

portWwn of device(s) connected:
  20:00:b4:99:ba:28:1d:e7
  50:06:0b:00:00:c2:72:14
  50:06:0b:00:00:c2:72:00
  50:06:0b:00:00:c2:72:0c
  c0:03:ff:8a:89:fa:00:08
  50:06:0b:00:00:c2:72:04
  c0:03:ff:0e:19:1f:00:0b
  c0:03:ff:0e:19:1f:00:07

portWwn of device(s) connected:
  20:11:b4:99:ba:28:29:02
  50:06:0b:00:00:c2:6e:24
  c0:03:ff:e7:c3:d5:00:08
  c0:03:ff:e7:c3:d5:00:23

portWwn of device(s) connected:
  20:11:b4:99:ba:28:1d:e7
  50:06:0b:00:00:c2:72:10
  50:06:0b:00:00:c2:72:08
  c0:03:ff:0e:19:1f:00:00
  c0:03:ff:8a:89:fa:00:0d
  c0:03:ff:e7:c3:d5:00:1f
portloginshow for this Port confirms the successful login.

portloginshow 44
Type PID World Wide Name credit df_sz cos
=====================================================

  fd 042422 c0:03:ff:e7:c3:d5:00:1f 16 2112 c scr=0x3
  ff 042422 c0:03:ff:e7:c3:d5:00:1f 0 0 8 d_id=FFFFFC
  ff 042422 c0:03:ff:e7:c3:d5:00:1f 0 0 8 d_id=FFFFFA

And the device is registered with the name server.

N 042422; 2,3;c0:03:ff:e7:c3:d5:00:1f;c0:03:ff:00:00:ff:ff:00; 0x00000003
  FC4s: FCP
  PortSymb: [64] "Hyper-V VM Port................................................."
  NodeSymb: [34] "QMH2572 FW:v7.00.02 DVR:v9.1.11.24"
  Fabric Port Name: 20:2c:00:05:33:ec:85:76
  Permanent Port Name: 20:11:b4:99:ba:28:1d:e7
  Port Index: 44
  Share Area: No
  Device Shared in Other AD: No
  Redirect: No
  Partial: No
  LSAN: No

It's a similar situation for the second Brocade Switch.

These 4 Ports have NPIV devices connected.

33 33 042c00 id N8 Online FC F-Port 1 N Port + 3 NPIV public
37 37 042000 id N8 Online FC F-Port 1 N Port + 7 NPIV public
40 40 042800 id N8 Online FC F-Port 1 N Port + 3 NPIV public
44 44 042400 id N8 Online FC F-Port 1 N Port + 5 NPIV public

Inspecting each of these Ports to show the WWPNs of the connected devices shows that C003FFE7C3D5001F is connected to Port Number 44.

<Port Number 33>

portWwn of device(s) connected:
20:00:b4:99:ba:28:29:02
50:06:0b:00:00:c2:6e:08
c0:03:ff:49:86:aa:00:01
c0:03:ff:e7:c3:d5:00:0d

<Port Number 37>

portWwn of device(s) connected:
20:00:b4:99:ba:28:1d:e7
50:06:0b:00:00:c2:72:14
50:06:0b:00:00:c2:72:00
50:06:0b:00:00:c2:72:0c
c0:03:ff:8a:89:fa:00:08
50:06:0b:00:00:c2:72:04
c0:03:ff:0e:19:1f:00:0b
c0:03:ff:0e:19:1f:00:07

<Port Number 40>

portWwn of device(s) connected:
20:11:b4:99:ba:28:29:02
50:06:0b:00:00:c2:6e:24
c0:03:ff:e7:c3:d5:00:08
c0:03:ff:e7:c3:d5:00:23

<Port Number 44>

portWwn of device(s) connected:
20:11:b4:99:ba:28:1d:e7
50:06:0b:00:00:c2:72:10
50:06:0b:00:00:c2:72:08
c0:03:ff:0e:19:1f:00:00
c0:03:ff:8a:89:fa:00:0d
c0:03:ff:e7:c3:d5:00:1f <-------------------------- C003FFE7C3D5001F

portloginshow for this Port confirms the successful login.

portloginshow 44
Type PID World Wide Name credit df_sz cos
=====================================================

fd 042422 c0:03:ff:e7:c3:d5:00:1f 16 2112 c scr=0x3
ff 042422 c0:03:ff:e7:c3:d5:00:1f 0 0 8 d_id=FFFFFC
ff 042422 c0:03:ff:e7:c3:d5:00:1f 0 0 8 d_id=FFFFFA

And the device is registered with the name server.

<snip nsshow>

N 042422; 2,3;c0:03:ff:e7:c3:d5:00:1f;c0:03:ff:00:00:ff:ff:00; 0x00000003
FC4s: FCP
PortSymb: [64] "Hyper-V VM Port................................................."
NodeSymb: [34] "QMH2572 FW:v7.00.02 DVR:v9.1.11.24"
Fabric Port Name: 20:2c:00:05:33:ec:85:76
Permanent Port Name: 20:11:b4:99:ba:28:1d:e7
Port Index: 44
Share Area: No
Device Shared in Other AD: No
Redirect: No
Partial: No
LSAN: No

Solution

This is a feature of the Microsoft Hyper-V Virtual Fibre Channel implementation for Live Migration.

THe Microsoft Hyper-V Virtual Fibre Channel Overview document at the following location:

https://technet.microsoft.com/en-in/library/hh831413.aspx

Describes the following:

<>

Live migration

To support live migration of virtual machines across Hyper-V hosts while maintaining Fibre Channel connectivity, two WWNs are configured for each virtual Fibre Channel adapter, as shown in Figure 1: Set A and Set B. Hyper-V automatically alternates between the Set A and Set B WWN addresses during a live migration. This ensures that all LUNs are available on the destination host before the migration and that no downtime occurs during the migration.

<>

The Brocade Data Center Virtual Fibre Channel for Hyper-V manual also documents this in the Live Migration section - please see page 5 of the attached Brocade manual virtual-fibre-channel-hyperv-tb.pdf.

Furthermore Microsoft Technet article titled "Implement Hyper-V Virtual Fibre Channel " which is available at the following location:

https://technet.microsoft.com/en-in/library/dn551169.aspx

In the graphic associated with the following section it clearly shows that only one Set addresses, Set A or Set B, will be active whilst the other Set will be passive.

Step 1: Review considerations for live migration

Hyper-V in Windows Server 2012 R2 and Windows Server 2012 supports live migration of virtual machines across computers running Hyper-V, while maintaining Fibre Channel connectivity. Live migration is accomplished with failover clusters, and each virtual Fibre Channel adapter is configured with two World Wide Names (WWNs).

As shown in Figure 2, Hyper-V automatically changes between Set A and Set B WWN addresses during a live migration. Hyper-V ensures that all LUNs are available on the destination computer, and then it performs the live migration.

This explains why the WWPNs for Address Set A or Address Set B can be active at any one time, but not both, which would be consistent with what the Brocade Switches are reporting.

References

<NOTE:1502843.1> - SAN Fibre Channel (FC) Storage Connectivity Issues

Attachments

This solution has no attachment