B22 Blade Fabric Extender for HP (Cisco Nexus B22HP) provides an extension of the Cisco Nexus switch fabric to the HP server edge. Logically, it behaves like a remote line card to a parent Cisco Nexus 5000 Series Switch. The fabric extender and the parent Cisco Nexus 5000 Series Switch together form a distributed modular system.
Page 4
(VFC) interface is bound to a particular link at the server. This configuration also achieves high availability through redundancy, and it can withstand a failure of a Cisco Nexus 5500 switch platform, a Cisco Nexus B22HP, or any connecting cable. This topology is widely used in FCoE deployments.
The third blade chassis from the left in Figure 1 contains Cisco Nexus B22HP fabric extenders that connect to both Cisco Nexus 5500 switch platforms through vPC for redundancy. In this configuration, active-active load balancing using vPC from the blade server to the Cisco Nexus 5500 switch platform cannot be enabled. However, the servers can still be dual-homed with active-standby or active-active transmit-load-balancing (TLB) teaming.
Fabric Connectivity Options The Cisco Nexus B22HP creates a distributed modular chassis with the Cisco Nexus parent switch after a fabric connection has been made over standard 10-Gbps cabling. This connection can be accomplished using any of the following types of interconnects: ●...
The PortChannel fabric interface provides an alternative method of connection between the parent switch and the Cisco Nexus B22HP fabric extender. In this mode of operation, the physical fabric links are bundled into a single logical channel. This approach prevents a single fabric interconnect link loss from disrupting traffic to any one server.
Page 9
N5548-Bottom(config-if)# interface ethernet 1/2 N5548-Bottom(config-if)# switchport mode fex-fabric N5548-Bottom(config-if)# fex associate 103 N5548-Bottom(config-if)# channel-group 3 Repeat the steps on the second Cisco Nexus 5000 Series Switch connected to the fabric extender in interconnect bay 4. N5548-Top# configure terminal N5548-Top(config)# feature fex...
FOC1515ZZU4 Virtual PortChannel Connection vPCs allow links that are physically connected to two different Cisco Nexus switches to form a PortChannel to a downstream device. The downstream device can be a switch, a server, or any other networking device that supports IEEE 802.3ad PortChannels.
EtherChannel or LACP connections can be created between the blade server and the virtual chassis. Dual Cisco Nexus 5000 Series switches can be used with vPC for additional switch redundancy while providing active-active links to servers, thus enabling aggregate 40-Gbps bandwidth with dual links (Figure 4).
Page 16
Click OK to complete the NIC teaming configuration. It may take a few minutes to complete after you click OK. To verify that the vPC is formed, go to one of the Cisco Nexus 5000 Series Switches to check the status of the server PortChannel interface.
FCoE combines LAN and storage traffic on a single link, eliminating dedicated adapters, cables, and devices for each type of network, resulting in savings that can extend the life of the data center. The Cisco Nexus B22HP is the building block that enables FCoE traffic to travel outside the HP BladeSystem chassis.
Nexus B22 Blade Fabric Extender for HP brings these innovations to the HP BladeSystem c-Class chassis. The Cisco Nexus B22HP supports both 1 and 10 Gigabit Ethernet connectivity, allowing a smooth migration from 1 Gigabit Ethernet to 10 Gigabit Ethernet for blade servers. Unified fabric with FCoE deployment outside the HP BladeSystem chassis is finally achieved.