Scenario 2-sus with active/active uplinks and 802.3ad (

Create SUS and 802.3ad (lacp) in the virtual connect a/A module ).

Glossary:

SUS (shared uplink sets): supports multi-VLAN data communication traffic.

Lacp (link aggregation Control Protocol): The Link aggregation control protocol, which implements link dynamic convergence.

Configuration Overview:

Two interconnected flexfabric modules, each of which creates an independent SUS and is configured in active/active mode. lacp is used for Link aggregation.

Because multiple VLANs communicate with each other in traffic, the corresponding port needs to be configured as VLAN Trunking/tagging for the VC peer connection switch.

This scenario supports both Ethernet and FC network connections. To deploy this scenario, we need an HP bladesystem c7000 with at least one BL server. Two VC flexfabric modules are installed in the interconnection modules bay1 and bay2 of c7000. One or more external network switches are required. The VC module does not provide the switch function, but the VC can communicate with the standard switch. The FC uplink can also be connected to an existing fc san architecture. SAN Switch Port Configuration must support npiv

Hardware information

Module name: firmware version location

Hp vc FlexFabric-20/40 F8 module 4.30 bay1/bay2

HP ProLiant bl420c gen8 (HP flexfabric 20 GB 2-port flb adapte) bay1

Physical View

Scenario 2-shared uplink sets with active/active uplinks and 802.3ad (lacp)-Ethernet and fcoe-Windows 2008 r2

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/11/718756_1412988182VEkN.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/11/718756_1412988203S8Yi.png "Height =" 438 "/>

Procedure

Uplink Ethernet switch configuration information (VC external Ethernet switch, not displayed in the view)

1: Switch Port is configured as VLAN trunk/tagging mode to support multi-VLAN Communication

2: If sus contains multiple uplink entries, the switch port is configured as lacp.

3: configure the Spanning Tree Protocol for the switch port. Speed up data forwarding.

Uplink SAN Switch configuration information (VC external SAN Switch, not displayed in the view)

1: San switch port must be configured to support npiv

VC module connection

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/11/718756_14129882082PKJ.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/11/718756_1412988218Xsdk.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/11/718756_1412988226ujr4.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/11/718756_1412988236tk82.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/11/718756_1412988241cEMD.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/11/718756_1412988246zGvD.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/11/718756_14129882514ftO.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/11/718756_1412988257D2MA.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/11/718756_14129882626YhK.jpg "Height =" 295 "/>

Define server profile to assign bay1 host

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

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

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

View the adapter ing in bay1 host

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

Summary:

In the server profile we created, both NICs of the BL 420g8 server are connected to the same external VLAN (101) through the VC network (VLAN-101-1, VLAN-101-2, provides fault redundancy for connecting links and VC modules to external networks. Both VLAN-101-1 and VLAN-101-2 support VLAN-101, data frames will be directly connected to the same VLAN through Nic instead of VLAN tagged, but can access external network communication through different paths.

Fcoe San fabric also provides multi-path routing for San traffic in VC. fcoe_a and fcoe_ B are configured to access redundant communication between San Lun inbound and outbound traffic.

When bl420g8 is powered on, the first Nic in both NICS will be connected to flexfabric module1 (connected to the VLAN-101-1); the other NIC will be connected to flexfabric module2 (VLAN-101-2 ).

If you need to add the number of NIC ports to the server in the future, you can disable the server and increase the number of NICs to six (two flexhbas). We can re-allocate the network bandwidth rate, modify the server profile as needed and enable the configuration file.

If you add a server to enclosure later, you can simply create a server profile or copy an existing server profile, configure Ethernet NIC and San fabric as needed, and then assign the application configuration to the host, power-on is so simple.

This article is complete, To be continued ......

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

Scenario 2-sus with active/active uplinks and 802.3ad (