HP Integrity NonStop NB50000c HP Virtual Connect Flex-10 technology: Convergen - Page 12

HBA driver support, FlexFabric, Adapter

Page 12 highlights

can disable the FlexFabric adapter storage function and configure the second PF as another FlexNIC function. The first, third, and fourth PFs work only as FlexNIC devices and will always have a NIC personality. The like-numbered PFs (F1, F2, F3, F4) of each port on the same FlexFabric adapter must have the same personality. (You could also disable one or both of the like-numbered PFs.) This means that Fibre Channel FlexHBA and iSCSI FlexHBA cannot exist on the same FlexFabric adapter at the same time. You can configure the FlexFabric adapter profile through the Virtual Connect Manager (VCM). VCM determines the "personality" of each of the PFs on the FlexFabric adapter. The VCM configuration also negotiates with the VC FlexFabric module and assigns a VLAN to each PF. The LAN traffic may also have VLAN tags from the OS. This depends on the use of tunneling and shared uplink sets (SUS). The OS sees each PCI PF on the FlexFabric adapter as a conventional hardware NIC, Fibre Channel HBA, or iSCSI HBA device. Each PF advertises its VLAN assignment designated by the VCM server profile. The advertised device type and VLAN assignment steers individual traffic classes to the appropriate PF (F1, F2, F3, or F4) on the FlexFabric adapter (Figure 9). Figure 9. FlexFabric adapter configured for Fibre Channel and displaying data traffic on one 10 Gb Ethernet port NIC Driver NIC driver NIC Driver HBA Driver Host OS F1 ENET0 VLAN F2 HBA1 FC F3 ENET1 VLAN F4 ENET2 VLAN F1 VLAN F2 VLAN F3 VLAN F4 VLAN MAC PHY 10Gb port 1 FlexFabric Adapter IPFCoEIPIP MAC PHY 10Gb port 2 HBA driver support You can use the same drivers for the FlexHBA function on a FlexFabric adapter as those for a traditional Fibre Channel HBA adapter (as long as the drivers are from the same vendor). You can also use Virtual Connect to manage the FlexHBA option ROM image and boot parameters. FlexHBAs support boot from SAN capabilities just like legacy Fibre Channel or iSCSI HBAs. 12

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19

can disable the FlexFabric adapter storage function and configure the second PF as another FlexNIC
function. The first, third, and fourth PFs work only as FlexNIC devices and will always have a NIC
personality. The like-numbered PFs (F1, F2, F3, F4) of each port on the same FlexFabric adapter must
have the same personality. (You could also disable one or both of the like-numbered PFs.) This means
that Fibre Channel FlexHBA and iSCSI FlexHBA cannot exist on the same FlexFabric adapter at the
same time.
You can configure the FlexFabric adapter profile through the Virtual Connect Manager (VCM). VCM
determines the “personality” of each of the PFs on the FlexFabric adapter. The VCM configuration
also negotiates with the VC FlexFabric module and assigns a VLAN to each PF. The LAN traffic may
also have VLAN tags from the OS. This depends on the use of tunneling and shared uplink sets (SUS).
The OS sees each PCI PF on the FlexFabric adapter as a conventional hardware NIC, Fibre Channel
HBA, or iSCSI HBA device. Each PF advertises its VLAN assignment designated by the VCM server
profile. The advertised device type and VLAN assignment steers individual traffic classes to the
appropriate PF (F1, F2, F3, or F4) on the FlexFabric adapter (Figure 9).
Figure 9.
FlexFabric adapter configured for Fibre Channel and displaying data traffic on one 10 Gb Ethernet
port
FlexFabric
Adapter
FCoE
IP
IP
IP
FCoE
IP
IP
IP
10Gb
port 1
PHY
MAC
F1
ENET0
F2
HBA1
F3
ENET1
Host OS
FC
VLAN
VLAN
F4
ENET2
NIC
Driver
HBA
Driver
NIC
Driver
NIC
driver
10Gb
port 2
PHY
MAC
F1
F2
F3
F4
VLAN
VLAN
VLAN
VLAN
VLAN
HBA driver support
You can use the same drivers for the FlexHBA function on a FlexFabric adapter as those for a
traditional Fibre Channel HBA adapter (as long as the drivers are from the same vendor). You can
also use Virtual Connect to manage the FlexHBA option ROM image and boot parameters. FlexHBAs
support boot from SAN capabilities just like legacy Fibre Channel or iSCSI HBAs.
12