Scenario 3-HP c7000 virtual connect flexfabric sus with active/active

Flexfabric-20 bl420g8

Scenario 3-shared uplink set with active/active uplinks and 802.3ad (lacp)-Ethernet and fcoe boot from San-Windows 2008 r2

SUS witch active/active uplink and lacp-fcoe boot from San

Overview: None

Requirement: None

Content: records configuration process notes to meet design requirements and summarizes precautions.

Physical View

650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" physical view "border =" 0 "alt =" physical view "src =" http://img1.51cto.com/attachment/201410/12/718756_14130823854ZiK.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 "border =" 0 "alt =" logical view "src =" http://img1.51cto.com/attachment/201410/12/718756_1413082413Ltk5.png "Height =" 421 "/>

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/12/718756_1413082419OORx.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/12/718756_1413082427qN1w.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/12/718756_1413082436g8Jv.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/12/718756_1413082444THey.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/12/718756_14130824539MN7.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/12/718756_1413082460mjCz.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/12/718756_1413082467C8cx.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/12/718756_1413082476oD3A.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/12/718756_1413082483RXtz.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/12/718756_1413082491BKdt.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/12/718756_1413082498H2dR.jpg "Height =" 295 "/>

Define server profile to assign bay1 host

Ethernet Adapter connection

Port1 access name VLAN-101-1

Port2 access name VLAN-101-2

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: When we assign this server profile to bay1 host, this host will have 2 Nic connections and 2 fcoe connections. Nic1 and nic2 will be connected to the network VLAN-101-x network; 2 fcoe allocated to fcoe_a and fcoe_ B.

After configuring the Ethernet Adapter connections in the server profile, the view is displayed.

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

Add the fcoe HbA connection View list and assign this server profile to bay1 host.

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

Configure the boot from San check option (one is primary and the other is secondary)

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

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

After configuring the server profile, view the adapter connection information from bay1 to verify that the configuration is correct.

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

Now the configuration is complete:

If the bay1 host is installed with the OS, you can view the network connection at the OS level;

If there is no system, you can set the hba bios at boot, configure boot from San, and install the OS in the remote storage Lun data center.

For detailed settings at the system level, see section 1.

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

Scenario 3-HP c7000 virtual connect flexfabric sus with active/active