Scenario 1–simple VNet with Active/standby uplinks–ethernet a

Scenario 1–simple VNet with Active/standby uplinks–ethernet and fcoe–windows

Scenario 1: Simple vnet using Active/standby uplinks-ethernet and FCOE-WINDOWS2008R2

Overview:

This simple configuration scenario uses VC vnet and FCoE to meet SAN requirements. This simple design does not use VLAN mapping,vnet is the simplest way to connect virtual connect to network and server components. In this scenario, the uplink network switch is connected to a port in each of the Flexfabric modules. In addition, the Flexfabric module has a port attached to the existing San FC architecture design to meet storage needs.

An on-the-go switch does not require a special configuration, leaving the factory default settings, usually configured to access or untagged port default VLANs or specific VLANs. In this case, Virtual Connect does not receive a VLAN tag.

When configuring VCs, we can use several methods to deploy fail-over or redundant modes of network components. One option may be to connect two uplinks to a single vnet; the two uplinks can be connected to different VC modules in the same frame, and then connected to two different uplink switches via their respective VC ports, depending on their needs. Another option is to design two different vnets, each configured with one or more uplinks, respectively. Both options have their merits and demerits. For example: a active/standby configured to place redundant tiers at the VC level, and one active/active to place redundancy on the system OS NIC teaming or bonding level. Below, we will focus on the first option.

In addition, different vnets can be configured to support different network communication requirements, which may need to differentiate between different types of network traffic, such as ISCSI, Backup, vMotion, management, and production traffic.

The scenario will use the FCoE feature in the Flexfabric module, and each LOM port has an uplink connected to a flexfabric module.

Demand:

The scenario supports both Ethernet and FC network connectivity requirements. In order to deploy this scenario, we need an HP BladeSystem C7000, at least one BL server, two VC flexfabric modules installed in the C7000 Interconnect module Bay1, Bay2 location. One or more external network switches are also required. The VC module does not have a switch function, but the VC can communicate with the standard switch. FC Uplinks also need to be able to connect to an existing FC SAN architecture. The SAN switch port configuration requires support for the NPIV feature. Each of the Flexfabric modules has a port that is allied to a SAN switch.

Physical topology 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/8/718756_ 1412738182dtna.png "height=" 472 "/>

Logical Topology 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/8/718756_1412738215uPvx.png " height= "389"/>

Installation and configuration:

Switch configuration

The VC module role acts as an edge switch. VC can be connected directly to the distributed switch and core switch

The switch with the VC module needs to be configured to meet the needs of the scene.

The 1:switch port is configured as acess or untagged mode, or the default

The VLAN or the specified VLAN can forward untagged frames.

2: If the switch port is configured for trunk mode forwarding multiple VLANS,VC will go

The host adapter that has the tag frame to the network, if this is the case,

Then you need to configure the VC network as VLAN tunning mode. Connection Host will

will need to be configured to interpret these VLAN tags.

In addition, the switch port is best configured as spanning Tree edge, you can see the VC as an edge access device, rather than a switch, by configuring STE, you can make the port forwarding speed faster, This configuration allows a new access port to forward traffic more quickly.

The port to which the SAN Switch and VC modules are connected must be configured to support NPIV.

Module Name Firmware version location

HP VC flexfabric-20/40 F8 Module 4.30 bay1/bay2

HP ProLiant bl420c Gen8 (404663-b21 hp FlexFabric 20Gb 2-port FLB adapte) Bay1

Configure VC

Configuring expanded VLAN capacity (supports up to 8,192 VLANs per domain, up to 162 per host port)

A VLAN)

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; "title=" vlan-Advanced Settings-extended VLAN compatibility "border=" 0 "alt=" vlan-Advanced Settings-extended VLAN Compatibility "src=" http://img1.51cto.com/attachment/201410/8/718756_ 1412738222vlor.jpg "height=" 303 "/>

Configure Fast MAC Cache Failover

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; "title=" Mac cache disaster recovery enabled "border=" 0 "alt=" Mac cache Disaster recovery enable "src=" Http://img1.51cto.com/attachment/201410/8/718756_1412738231LLXI.jpg "height=" 301 "/>

Define a new vnet (that is, create a new Ethernet Network. Configuration point already marked with red circle)

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "VNET-1" Border= "0" alt= "vNET-1" src= "http://img1.51cto.com/attachment/201410/8/718756_141273823679JU.jpg" height= "276"/ >

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "VNET-2" Border= "0" alt= "vNET-2" src= "http://img1.51cto.com/attachment/201410/8/718756_14127382439KFu.jpg" height= "291"/ >

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "VNET-3" Border= "0" alt= "vNET-3" src= "http://img1.51cto.com/attachment/201410/8/718756_1412738251cGiT.jpg" height= "303"/ >

Definition of two new FCoE San Fabric (for SAN storage)

Define FCOE_A SAN Fabric

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "FCoE_a" Border= "0" alt= "fcoe_a" src= "http://img1.51cto.com/attachment/201410/8/718756_1412738259VY8Q.jpg" height= "296"/ >

Similarly define a second fcoe_b SAN Fabric

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "FCoE_B" Border= "0" alt= "fcoe_b" src= "http://img1.51cto.com/attachment/201410/8/718756_1412738278BvQC.jpg" height= "298"/ >

After configuring two FCoE, summarize as shown (need to focus on modules and ports do not choose the wrong!) ）

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "Fcoe-ab" Border= "0" alt= "fcoe-ab" src= "http://img1.51cto.com/attachment/201410/8/718756_1412738285vj7W.jpg" height= "292"/ >

Define a server profile that contains NIC and FCoE connections, and then assign it to the blade server

The name of the Server profile is best for easy identification {use (APP) +bay bit}

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "Profile1" Border= "0" alt= "profile1" src= "http://img1.51cto.com/attachment/201410/8/718756_14127382958eb2.jpg" height= "263"/ >

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; title= "Profile2" Border= "0" alt= "profile2" src= "http://img1.51cto.com/attachment/201410/8/718756_1412738302NCAH.jpg" height= "305"/ >

In the BL420G8 adapter mapping control relationship, you can see the relationship, if you are not sure you can confirm the MAC address in the OS

650) this.width=650; "style=" border-bottom:0px;border-left:0px;border-top:0px;border-right:0px; "title=" Host-profile-map "border=" 0 "alt=" host-profile-map "src=" http://img1.51cto.com/attachment/201410/8/718756_ 14127383114vmf.jpg "height=" 302 "/>

Review:

1:windows 2008R2 Ethernet Network Instance

(Can be tied to network card, increase the bandwidth, increase the fault redundancy function)

2:windows 2008R2 San Connection instance

(Add SAN storage)

Summarize

1: We design a VC network scenario by creating a simple vnet. At the same time, we have configured the Min/max speed limit for the vnet, a dual path SAN fabric for SAN storage network to meet the network QoS requirements in the real Enterprise network design.

2: When we deploy the VC server profile app-bay-1 to the Bay1 server, and then start the server, each NIC of the server is connected to the same vnet-production through any of the Flexfabric modules. Two link rates are 10Gb, and these NICs can be individually configured with their respective IP addresses, or they can be configured as Team NICs. Each NIC can be active, and the server can be connected to the network or uplink via any one of the network ports. For traffic shaping we set the minimum and maximum link rates to meet the needs of the application.

3: When a new server is deployed to enclosure, simply creating a server profile or directly replicating an existing server profile for modification can speed up deployment and when deploying server profile to a blade server, The server must be in power off state.

4: When creating Ethernet network, VC multiport relationship is Active/standby configuration by default.

5: Specific scenario specific design, enterprise internal network design, should meet the business needs of enterprises on the basis of as close as possible to the best design examples.

This article is from the "Dragon Kiss" blog, make sure to keep this source http://728756.blog.51cto.com/718756/1561165

Scenario 1–simple VNet with Active/standby uplinks–ethernet a