Scenario 4-shared uplink set with active/active uplinks and 802.3ad (lacp)-Ethernet, fcoe san
Overview: None
Requirement: None
Content: record the configuration process to meet the design requirements.
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" physical view (2) "border =" 0 "alt =" physical view (2) "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163354MAD1.png "Height =" 484 "/>
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" logical view (2) "border =" 0 "alt =" logical view (2) "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163371I8mD.png "Height =" 414 "/>
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/13/718756_1413163375L79f.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/13/718756_1413163381lugq.jpg "Height =" 302 "/>
Add external uplink ports to SUS, add "associated networks" to the bottom, and click multiple secondary connections. When VLAN IDs are input, they 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/13/718756_1413163386Jq2A.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/13/718756_1413163392AuIT.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/13/718756_1413163398BRuB.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/13/718756_1413163404Lia5.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/13/718756_1413163408D8XD.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/13/718756_1413163414OXG3.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/13/718756_1413163784Uwgo.jpg "Height =" 295 "/>
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/13/718756_1413163789b1KL.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
Port3 access network name VLAN-102-1 to VLAN-105-1; VLAN-2100-1 to VLAN-2150-1;
Port4 access network name VLAN-102-2 to VLAN-105-2; VLAN-2100-2 to VLAN-2150-2;
Fcoe San 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 four Nic connections and two fcoe connections. Nic1 and nic2 will be connected to the network VLAN-101-x network; nic3 and nic4 will be connected to the VLAN-102-X, VLAN-105-X to the VLAN-2100-X; 2 fcoe allocated to fcoe_a and fcoe_ B.
Click Add multiple networks to network connection (third Nic, only allow VLAN-x-1 network through)
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 2 (1) "Border =" 0 "alt =" 2 (1) "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163796Rrml.jpg "Height =" 296 "/>
Click Add multiple networks to network connection (fourth Nic, only allow VLAN-x-2 network through)
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 3 (2) "Border =" 0 "alt =" 3 (2) "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163803mHKq.jpg "Height =" 305 "/>
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 =" 4 (1) "Border =" 0 "alt =" 4 (1) "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163810OaJY.jpg "Height =" 286 "/>
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/13/718756_1413163818kQvx.jpg "Height =" 305 "/>
After configuring the server profile, view the adapter connection information from bay1.
Click the "multiple networks" option in the Lom to display information similar to the following: list all VLAN connection information of the port.
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 6 "border =" 0 "alt =" 6 "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163827WFmp.jpg "Height =" 317 "/>
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 7 "border =" 0 "alt =" 7 "src =" http://img1.51cto.com/attachment/201410/13/718756_141316383516F3.jpg "Height =" 466 "/>
As shown in Nic mapping information (multiple network was originally intended to add VLAN2100-VLAN2150, a total of 50 !!! However, because the quantity is indeed too large, the batch operation method is not found for the time being, manual addition is indeed troublesome, so some VLAN dragging is omitted. Sorry, I hope you will understand .)
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" 8 "border =" 0 "alt =" 8 "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163845Uk4F.jpg "Height =" 303 "/>
Teaming allows multiple VLANs to pass through and enables the VLAN hybrid mode.
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" Nic hybrid mode "border =" 0 "alt =" Nic hybrid mode "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163853goio.jpg "Height =" 430 "/>
Connection10 can be used only for a single VLAN to allow the console to pass through;
Connection11 enables traffic passing through multiple VLANs and can be used for communication between multiple VM production networks in virtualization. Therefore, no IP address is configured.
650) This. width = 650; "style =" border-bottom: 0px; border-left: 0px; border-top: 0px; border-Right: 0px; "Title =" one team to the console, one team to the VM "border =" 0 "alt =" one team to the console, A team gives VM "src =" http://img1.51cto.com/attachment/201410/13/718756_1413163860e351.jpg "Height =" 317 "/>
After we grant this server profile to bay1 and install Windows 2008r2 for bay1, the network connection will display four NICs. By default, each Nic can initialize and configure an IP address. In addition, to prevent Nic faults, we will create two Nic teams in this chapter, nic1 and nic2 to form a team1 (vlan101 allowed), nic3 and nic4 to form a Team2 (allow VLAN102-105; VLAN2100-2150 traffic data through ). This configuration, coupled with the dual-Active configuration of VC, enables high availability for VC module and nic faults and link faults at the same time to prevent data communication interruptions caused by any network components.
This series, To be continued ......
This article from the "kiss" blog, please be sure to keep this source http://728756.blog.51cto.com/718756/1563087
Scenario 4-HP c7000 virtual connect flexfabric sus with active/active