Scenario 6-HP c7000 virtual connect flexfabric sus with A/A uplinks, 8

Overview: HP c7000 VC flexfabric SUS is configured as active/active, lacp, fcoe, vsphere

First, create two sus named VLAN-Trunk-1 and VLAN-Trunk-2, respectively. VLAN-Trunk-1 has 2 uplink ports (Bay1-VC X5, X6), VLAN-Trunk-2 has 2 uplink ports (Bay2-VC X5, X6), all port States are linked-active; the preceding configuration description is the active/active source of 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, prevent network connection failures caused by a single port and VC module. In addition, VLAN is also divided to prevent network storms and improve LAN security.

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

Physical View:

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

Logical view:

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

Installation and Configuration:

Switch configuration:

The VC needs to configure the VLAN trunk mode (tagging) for the connection switch port to support the passing of communication traffic from multiple VLANs. All frames forwarded to VC must carry VLAN tags. Correspondingly, if a VLAN is configured as (default) without untamed, You need to configure the vnet in SUS to "default"

If sus contains multiple uplinks and multiple uplinks are from the same VC module, you must configure lacp in the external switch to ensure that uplinks are active.

Configure the Spanning Tree Protocol for the switch port. Speed up data forwarding

Configure npiv for SAN Switch Port.

Configure the VC Module

Switch_a_port_1 connects to bay1_x5

Switch_a_port_2 connects to baybench X6

Switch_ B _port_1 connects to bay2_x5

Switch_ B _port_2 connects to bay2_x6

San_switch_a_port_1 connects to baybench X1

San_switch_a_port_2 connects to baybench X2

San_switch_ B _port_1 connects to bay2_x1

San_switch_ B _port_2 connects to bay2_x2

Define SUS (VLAN-Trunk-1)

External uplink Prots (baybench X5; baybench X6)

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

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

VLAN IDs are separated by commas (,). For example, 101-2400,

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

After deploying a VLAN, see Figure

According to the actual operation, if a VLAN in the trunk is configured as native or untagged for communication with Sus, you need to edit the VLAN configuration interface and set native to true for normal communication.

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

Define SUS (VLAN-Trunk-2)

Copy the VLAN-Trunk-1 directly, and then modify

External uplink Prots (bay2_x5; bay2_x6)

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

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

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

Define fcoe San Fabric

Define fcoe-A (baybench port_x1; baybench port_x2 ;)

1: Fabric type is "fabricattach"

2: in advanced settings, select "automaitc login re-distribution"

3: QoS (Min 4 GB; Max 8 GB) for fcoe in Advanced Settings)

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

Define fcoe-B (bay2_port_x1; bay2_port_x2 ;)

1: Fabric type is "fabricattach"

2: in advanced settings, select "automaitc login re-distribution"

3: QoS (Min 4 GB; Max 8 GB) for fcoe in Advanced Settings)

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

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

After fcoe is configured, the list is shown in: the module Bay-port ing control relation is easily incorrect.

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/15/718756_1413350946giAi.jpg "Height =" 295 "/>

Define server profile to assign bay1 host

Ethernet Adapter connection

Port1 access network name VLAN-101-1 (customizable port rate)

Port2 access network name VLAN-101-2 (customizable port rate)

Port3 access network name VLAN-102-1 (customizable port rate)

Port4 access network name VLAN-102-2 (customizable port rate)

Port5 access network name multiple networks (customizable port rate)

Port6 access network name multiple networks (customizable port rate)

Fcoe adapter connection

Port1 connected to FC San/fcoe network connection is fcoe_a

Port2 connected to FC San/fcoe network connection is fcoe_ B

Note: After we assign this server profile to bay1 host, this host will have 6 Nic connections and 2 fcoe connections. Nic1 and nic2 will be connected to the network VLAN-101-x network; nic3 and nic4 will be connected to the network VLAN-102-x; nic5 and nic6 will be connected to the network multiple VLAN network. Two fcoe instances are allocated to fcoe_a and fcoe_ B.

After this server profile is assigned to a bl 460g7 server, you can see similar network connection properties to view information.

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 1 (2) "Border =" 0 "alt =" 1 (2) "src =" http://img1.51cto.com/attachment/201410/15/718756_1413350958CMpi.jpg "Height =" 384 "/>

In this regard, we have completed the VC Configuration Requirements.

The following NIC-mapping plan is not exactly consistent with the logical view design. The purpose of the design plan is to give us a clear concept of the Lom flexfabric technology of the BL server, it can accurately express our core ideas when designing NICs, and also to maximize availability and stability.

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/15/718756_1413350967rLsz.jpg "Height =" 225 "/>

When we create a sus or Ethernet network, for HP flexfabric 10 Gb 2-port 554flb adapter, the order of the selected and added network ports is fixed in the order

Port1 Lom: 1-A flexnic

Port2 Lom: 1-B flexhba (you can also delete the default flexhba port and use it as flexnic)

Port3 Lom: 1-c flexnic

Port4 Lom: 1-D flexnic

Port5 Lom: 2-A flexnic

Port6 Lom: 2-B flexhba (you can also delete the default flexhba port and use it as flexnic)

Port7 Lom: 2-C flexnic

Port8 Lom: 2-D flexnic

Finally, we can configure the NIC-mapping we designed in vsphere esxi5.x to use the team to provide fault redundancy for network components.

Vsphere esxi5.x network configuration options

1: Standard Virtual Switch is used for management, vmotion, and production-VM networks.

2: Management and vmotion use standard virtual switch; production-VM use Distribution

Virtual Switch

First Design Option (similar ),

1: In vmnic, the speed is the max speed customized by VC.

2: Port binding for each two vmnics to provide redundancy

3: When vmotion is grouped

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 3 (3) "Border =" 0 "alt =" 3 (3) "src =" http://img1.51cto.com/attachment/201410/15/718756_1413350976Q9GF.jpg "Height =" 484 "/>

Create vswitch vmkarnel

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 2 (2) "Border =" 0 "alt =" 2 (2) "src =" http://img1.51cto.com/attachment/201410/15/718756_1413350983RoPO.jpg "Height =" 418 "/>

Vmotion network considerations

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 4 (2) "Border =" 0 "alt =" 4 (2) "src =" http://img1.51cto.com/attachment/201410/15/718756_1413350991XXFD.jpg "Height =" 468 "/>

Because this scenario is set to sus active/active mode, to ensure that vmotion can be performed between servers in enclosure, You need to edit the vmotion vswitch attribute, in addition, one member bound to the NIC is active, and the other is standby mode, to ensure that the vmotion traffic in the VC module is normal. (I don't know why)

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/15/718756_1413350997yvuu.jpg "Height =" 484 "/>

Design Option 2 (similar)

Production-vdswitch is used for VM networks. Because of the large number of VMS and frequent change requests, it is suitable for transferring across multiple hosts.

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

The management network and vmotion network do not often change configurations and are more suitable for standard vswitches.

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

Finally, you can install the OS in the VM and view the parameter configurations of the virtual Nic in the system.

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/1564318

Scenario 6-HP c7000 virtual connect flexfabric sus with A/A uplinks, 8