HP Integrity NonStop NB50000c HP Virtual Connect Flex-10 technology: Convergen
HP Integrity NonStop NB50000c - BladeSystem Manual
 |
View all HP Integrity NonStop NB50000c manuals
Add to My Manuals
Save this manual to your list of manuals |
HP Integrity NonStop NB50000c manual content summary:
- HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 1
vNets or vFabrics 13 VC FlexFabric products ...14 HP FlexFabric Converged Network adapters 15 HP Virtual Connect FlexFabric 10 Gb/24-port module 15 Interoperability of Flex-10 and FlexFabric components 15 HP management software support for FlexFabric 16 Transition to FlexFabric technology ...16 - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 2
for converging different network protocols. This technology brief discusses the HP hardware and software technology that make up VC Flex-10 Connect FlexFabric modules and FlexFabric adapters to your existing infrastructure. HP Virtual Connect Flex-10 overview Flex-10 technology lets you configure - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 3
support up to four FlexNICs per port. VC Flex-10 interconnect modules support up to 64 FlexNICs. The modules also support data traffic by using OS or driver generated VLAN tags (Figure 2). Figure 2. FlexNICs share a physical link but isolate the traffic using VLAN tags BladeSystem "service" - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 4
on that SUS. On a SUS, the VLAN tagging is done at the VC/data center boundary. For example, the OS adds VLAN tags when packets leave the Virtual only one vNet. The vNet associated with a dedicated uplink only supports untagged packets from the server NIC ports or FlexNICs associated with the - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 5
Figure 3. Virtual Connect Flex-10 tagging method used in mapped configurations 3a 3b 3c 3d Virtual Connect can also map multiple networks to a single server NIC (non-Flex-10) or FlexNIC port. Figure 4 shows how a single FlexNIC handles packets with multiple OS tags (defined by different "OS TAG" - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 6
port 1 BladeSystem server 1Gb NIC 1Gb NIC vNET vNET vNET vNET adds or translates vLAN ID vNET vNET vNET Uplink Data Center Switch is ignoring the VLANs, there are no limits to the number of VLANs supported by a dedicated uplink in a Virtual Connect Domain operating in VLAN tunneling mode - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 7
center switch. If the OS sends an orange-tagged packet through the Flex-10 NIC device, that packet passes through to the data center switch without examination. The data center switch then sends the OS-tagged packet back into the Virtual Connect Flex-10 interconnect module through the SUS and to the - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 8
6. VLAN tunneling mode: OS tagged packet goes to data center switch. The figure shows only one 10 Gb port for the LOM or mezzanine card, but all FlexNIC devices have two ports. OS TAG OS TAG OS TAG OS TAG VM BladeSystem server BladeSystem server FlexNIC FlexNIC Flex-10 LOM/ FlexNIC FlexNIC Mezz - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 9
networks. In the reverse direction, there is no restriction on upstream ports. Flex-10 supports both VLAN tunneling and VLAN mapping on FlexNICs. SmartLink functionality is identical between standard 1 up to 24 NIC ports (for a single, half height BladeSystem server with two Flex-10 mezz cards). 9 - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 10
bandwidth. The Flex-10 modules support non-FlexNIC 1 Gb server ports, VC FlexFabric modules and FlexFabric adapters HP has launched a suite of products within data center. This is why we are using known technology requirements to converge networks only at the server-network edge in BladeSystem - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 11
VC FlexFabric Interconnect Module HP BladeSystem IP enclosure Hypervisor uses vLAN tags and FlexFabric adapter profiles to steer VM traffic FlexFabric Adapter provides local vLAN tagging and merges traffic classes into 10Gb/s uplink VC interconnect separates data traffic into original traffic - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 12
(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 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 - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 13
attributes that let the second PF on each of the two ports handle different data classes. Using the VC Manager (VCM), you can create a profile that one per port Failover support Support for Multipath I/O2 (MPIO) logic in OS for FlexHBAs CHAP3 and Mutual CHAP support for iSCSI FlexHBA point-to - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 14
FlexFabric components add DCB and FCoE functionality to the existing 10 Gb data stream partitioning and adjustable bandwidth capabilities found in Flex-10. VC on the same physical link. HP is the first vendor to offer an NPIV-based FC interconnect option for HP BladeSystem c-Class architecture. 14 - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 15
either integrated NC551i or NC553i FlexFabric adapters. FlexFabric adapters support all VC Flex-10 and VC FlexFabric functions (this includes FlexNIC and FlexHBA personality functions). You can use mezzanine HP NC551m FlexFabric adapters on currently shipping ProLiant BL G6 BladeSystem servers - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 16
, data center wide, within the converged network. HP Insight Dynamics, Orchestration, and Insight failover and recovery services will also support VC cabling, switches, and required ports at the server edge. HP BladeSystem customers can connect servers to network and storage infrastructure with a - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 17
Integrated FlexFabric adapter Future capabilities The current "one hop" approach carries converged network traffic to the server edge. HP HP BladeSystem customers to connect servers to network and storage infrastructure with a single server connection and a single VC interconnect module supporting - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 18
-9642ENW.pdf www.hp.com/go/bladesystem/virtualconnect http://h18004.www1.hp.com/products/blades/compon ents/vc-compmatrix.html www.hp.com/go/vcem http://h20000.www2.hp.com/bc/docs/support/Support Manual/c01990371/c01990371.pdf http://bizsupport1.austin.hp.com/bc/docs/support/Supp ortManual/c02255342 - HP Integrity NonStop NB50000c | HP Virtual Connect Flex-10 technology: Convergen - Page 19
to change without notice. The only warranties for HP products and services are set forth in the express warranty statements accompanying such products and services. Nothing herein should be construed as constituting an additional warranty. HP shall not be liable for technical or editorial errors
-
1 -
2 -
3 -
4 -
5 -
6 -
7 -
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
 |
 |
HP Virtual Connect Flex-10 technology:
Convergence with FlexFabric components
Technology brief
Introduction
.........................................................................................................................................
2
HP Virtual Connect Flex-10 overview
......................................................................................................
2
Traffic flow in Flex-10 devices and modules
............................................................................................
3
Mapping mode
................................................................................................................................
4
Tunneling mode
...............................................................................................................................
6
Virtual Connect Flex-10 management
.....................................................................................................
8
FlexNIC addressing
..........................................................................................................................
9
Virtual Connect server profiles and Flex-10
.........................................................................................
9
Convergence with VC FlexFabric modules and FlexFabric adapters
.........................................................
10
VC FlexFabric adapters
......................................................................................................................
11
FlexFabric physical function assignments
...........................................................................................
11
Determining FlexFabric adapter “personality”
....................................................................................
13
FlexHBA addressing
.......................................................................................................................
13
Mapping FlexHBAs to vNets or vFabrics
...........................................................................................
13
VC FlexFabric products
......................................................................................................................
14
HP FlexFabric Converged Network adapters
.....................................................................................
15
HP Virtual Connect FlexFabric 10 Gb/24-port module
.......................................................................
15
Interoperability of Flex-10 and FlexFabric components
...........................................................................
15
HP management software support for FlexFabric
...................................................................................
16
Transition to FlexFabric technology
......................................................................................................
16
Future capabilities
..............................................................................................................................
17
Conclusion
........................................................................................................................................
17
For more information
..........................................................................................................................
18
Call to action
....................................................................................................................................
19