Scenario 5-HP c7000 virtual connect sus A/S uplinks and ladp-fcoe-vsphere

English Name:

Scenario 5-shared uplink set with active/standby uplinks and 802.3ad (lacp)-Ethernet and fcoe San-vsphere

Introduction:

SUS: After the configuration is created, the communication traffic of multiple VLANs can pass through.

Active/active (A/A): this component or path is active-active, spof does not cause faults of the entire network..

Active/standby (A/S): two modules are active and standby. The standby node is activated only when the active node fails.

Lacp: a dynamic connection control protocol that groups several ports to Improve line bandwidth and link redundancy.

Fcoe: San communication traffic is transmitted over the Ethernet network, which reduces costs and is easy to use. The performance is lower than that of FC San.

Vsphere: an integrated solution for enterprise-level server virtualization.

First, create a sus, which has 4 uplink ports (Bay1-VC X5, X6; Bay2-VC X5, X6 ), the Bay1-VC X5, X6 port status is linked-active; Bay2-VC X5, X6 port status is linked-standby; The above configuration description is the active/standby source in this case, all uplink ports are members of lacp, and must be enabled in the Peer switch port.

Second, we also need to create two fcoe-san named fcoe_a and fcoe_ B to provide high-reliability San access functions.

Finally, we create a server profile for the host assigned to us, and allocate 6 flexnics and 2 flexhbas. The network usage functions are as follows: management Network, San network, vmotion network, and production VM access network. To improve high reliability, we create a group for each Nic from each lom1 and lom2, to prevent network connection failures caused by a single port and VC module, VLAN is also divided to prevent network storms and improve LAN security. For details about the vsphere NIC-mapping relationship, see:

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" Nic-mapping "border =" 0 "alt =" Nic-mapping "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250187G8I3.jpg "Height =" 225 "/>

The Network Design of c7000 and VMWare vsphere maximizes the advantages of hp vc flexfabric to improve the availability of the overall vsphere architecture.

Physical View

Scenario 5-shared uplink set with active/standby uplinks and 802.3ad (lacp)-Ethernet and fcoe San-vsphere

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" physical view (1) "border =" 0 "alt =" physical view (1) "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250211AGJt.png "Height =" 484 "/>

Logic View

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" logical view (1) "border =" 0 "alt =" logical view (1) "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250238juHZ.png "Height =" 413 "/>

Configuration process Demonstration:

1: Create SUS. (It is very important to add ports in sequence. If we first add X5 and X6 of bay2 to uplink, and then add X5 and X6 to uplink of bay1, the first two are active, and the last two are standby. )

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" A-S1 "border =" 0 "alt =" A-S1 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250246wbjl.jpg "Height =" 327 "/>

Create vlan101, vlan102, and a multiple VLAN (including multiple VLANs for production-VM access)

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-1 "border =" 0 "alt =" 5-1 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250251zODr.jpg "Height =" 298 "/>

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-3 "border =" 0 "alt =" 5-3 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250257817N.jpg "Height =" 238 "/>

View sus View

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-1 (1) "border =" 0 "alt =" 5-1 (1) "src =" http://img1.51cto.com/attachment/201410/14/718756_141325026076uL.jpg "Height =" 156 "/> 650) this. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-2 "border =" 0 "alt =" 5-2 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250263ZtLC.jpg "Height =" 123 "/>

2: view After configuring fcoe-san as shown in Figure

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 1 "border =" 0 "alt =" 1 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250269ZLCu.jpg "Height =" 295 "/>

3:Configure server profile

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-6 "border =" 0 "alt =" 5-6 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250279UZlT.jpg "Height =" 279 "/>

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-5 "border =" 0 "alt =" 5-5 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250285SL2g.jpg "Height =" 311 "/>

View the connection of the fcoe HbA and assign this server profile to bay11 host and bl460g7. Pay attention to the detailed ing relationship.

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-7 "border =" 0 "alt =" 5-7 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250291XpxA.jpg "Height =" 207 "/>

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-9 "border =" 0 "alt =" 5-9 "src =" http://img1.51cto.com/attachment/201410/14/718756_14132502941GCw.jpg "Height =" 101 "/>

Nic-mapping relationship (network function usage marked in red)

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-8 "border =" 0 "alt =" 5-8 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250303VeQ7.jpg "Height =" 484 "/>

View the complete server profile Interface

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 5-10 "border =" 0 "alt =" 5-10 "src =" http://img1.51cto.com/attachment/201410/14/718756_1413250309Avrj.jpg "Height =" 415 "/>

Now the VC configuration is complete.

At the vsphere esxi level

After esxi5.x is installed on the host, you can view all 6 flexnics in the network connection properties. According to our initial plan, team each two vmnic with the same function to improve bandwidth and fault redundancy.

In the future, an independent chapter will be published to introduce the configuration methods and precautions for HP c7000 VC-flexfabric in the vsphere environment.

This article ends, this series is to be continued ......

This article from the "kiss" blog, please be sure to keep this source http://728756.blog.51cto.com/718756/1563752

Scenario 5-HP c7000 virtual connect sus A/S uplinks and ladp-fcoe-vsphere