Cookbook

V

PF

Virtua

Part number c02First edition Nov

l Con

2617100 vember 2010

nect F

FlexFabbric CCookboook

Legal notices Never leverage legal and notice information. For the most current requirements, refer to HP Standard 004-0 Legal Notices for Product Documentation, Promotional Materials, and Software and Media located at http://standards.inet.cpqcorp.net/smc/hpstd/hpstds.htm

Purpose 3

Contents

Purpose ................................................................................................................................................. 5Introduction to Virtual Connect FlexFabric ................................................................................................. 6Tunneled VLAN and Mapped VLANS ..................................................................................................... 10Single Domain/Enclosure Scenarios ....................................................................................................... 13

Overview .............................................................................................................................................. 13Requirements .................................................................................................................................... 13

Scenario 1 Simple vNet with Active/Standby Uplinks and FCoE Windows 2008 R2 .............................. 14Overview .............................................................................................................................................. 14

Requirements .................................................................................................................................... 14Installation and configuration................................................................................................................... 16

Switch configuration .......................................................................................................................... 16Review ................................................................................................................................................. 23

Results Windows 2008 R2 Networking Examples ............................................................................... 24Results Windows 2008 R2 SAN Connectivity..................................................................................... 28

Summary .............................................................................................................................................. 29Scenario 2 Share Uplink Sets with Active/Active uplinks and 802.3ad (LACP) - Windows - Ethernet and FCoE .......................................................................................................................................................... 30


Installation and configuration................................................................................................................... 32Switch configuration .......................................................................................................................... 32

Review ................................................................................................................................................. 42Results Windows 2008 R2 Networking Examples ............................................................................... 43Results Windows 2008 R2 SAN Connectivity..................................................................................... 47

Summary .............................................................................................................................................. 48Scenario 3 Share Uplink Set with Active/Active Uplinks and 802.3ad (LACP) - Windows - Ethernet and FCoE Boot from SAN .................................................................................................................................... 49




Summary .............................................................................................................................................. 68Scenario 4 Share Uplink Set with Active/Active Uplinks and 802.3ad (LACP) - Windows Hyper-V - Ethernet and FCoE SAN .................................................................................................................................... 69




Summary .............................................................................................................................................. 96

Purpose 4

Scenario 5 Share Uplink Set with Active/Active Uplinks and 802.3ad (LACP) - vSphere - Ethernet and FCoE SAN ................................................................................................................................................... 97



Review ............................................................................................................................................... 112Results vSphere Networking Examples ............................................................................................. 112Results vSphere SAN Connectivity .................................................................................................. 115

Summary ............................................................................................................................................ 116Scenario 6 Tunneled VLANs and Share Uplink Set with Active/Active Uplinks - vSphere Ethernet and FCoE SAN ................................................................................................................................................. 117

Overview ............................................................................................................................................ 117Requirements .................................................................................................................................. 117

Installation and configuration................................................................................................................. 119Switch configuration ........................................................................................................................ 119

Review ............................................................................................................................................... 130Results vSphere Networking Examples ............................................................................................. 131Results vSphere SAN Connectivity .................................................................................................. 134

Summary ............................................................................................................................................ 135Appendix A Scenario-based CISCO Command Line Reference ............................................................. 136Appendix B Scenario-based ProCurve Command Line Reference ........................................................... 139Appendix C: Acronyms and abbreviations ............................................................................................ 142Appendix D: Useful VC CLI Command sets ............................................................................................ 144

Purpose 5

Purpose

The purpose of this Virtual Connect FlexFabric Cookbook is to provide users of Virtual Connect with a better understanding of the concepts and steps required when integrating HP BladeSystem and Virtual Connect FlexFabric components into an existing network.

The scenarios in this Cookbook vary from simplistic to more complex while covering a range of typical building blocks to use when designing Virtual Connect FlexFabric solutions. Although these scenarios are shown individually, some scenarios could be combined to create a more complex and versatile Virtual Connect environment, however, keeping in mind the difference between mapped and tunneled VLANs, discussed later in this paper are mutually exclusive.

The scenarios as written are meant to be self-contained configurations and do not build on earlier scenarios, with this you may find some repetition or duplication of configuration across scenarios.

This is not meant to be a complete or detailed guide to Virtual Connect FlexFabric, but is intended to provide the reader with some valid examples of how Virtual Connect FlexFabric could be deployed within their environments. Many additional configurations or scenarios could also be implemented. Please refer to the following section for additional reference material on Virtual Connect, Flex-10 and FlexFabric.

Introduction to Virtual Connect FlexFabric 6

Introduction to Virtual Connect FlexFabric

Virtual Connect is an industry standard-based implementation of server-edge virtualization. It puts an abstraction layer between the servers and the external networks so the LAN and SAN see a pool of servers rather than individual servers (Figure 1). Once the LAN and SAN connections are physically made to the pool of servers, the server administrator uses Virtual Connect management tools (Virtual Connect Enterprise Manager or Virtual Connect Manager) to create an Interconnect modules connection profile for each server.

Virtual Connect FlexFabric is an extension to Virtual Connect Flex-10 which leverages the new Fibre Channel over Ethernet (FCoE) protocols. By leveraging FCoE for connectivity to existing Fibre Channel SAN networks, we can reduce the number of switch modules and HBAs required within the server blade. This in turn further reduces cost, complexity, power and administrative overhead.

It is assumed that the reader has experience with and is familiar with Virtual Connect Flex-10. For additional information on Virtual Connect and Flex-10, please review the documents below. The Chapter on Flex-10 in the Virtual Connect Ethernet Cookbook, listed below, will be an excellent primer for this paper.

Additional Virtual Connect Reference Material Link to HP Virtual Connect technology site, provides a great deal of reference information on Virtual connect, Flex-10 and FlexFabric.

http://h18000.www1.hp.com/products/blades/virtualconnect/

Link to HP Virtual Connect technology for the HP BladeSystem c-Class, 4th edition when available

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00814156/c00814156.pdf

Link to HP Virtual Connect for c-Class BladeSystem Setup and Installation Guide

http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01732252/c01732252.pdf

Link to HP Flex-10 technology

http://bizsupport2.austin.hp.com/bc/docs/support/SupportManual/c01608922/c01608922.pdf

Link to HP BladeSystem Network Reference Architecture - FlexFabric and VMware vSphere 4

http://h20195.www2.hp.com/v2/GetPDF.aspx/c02505638.pdf

Link to Virtual Connect User, Setup and CLI Guides

http://h20000.www2.hp.com/bizsupport/TechSupport/DocumentIndex.jsp?contentType=SupportManual&lang=en&cc=us&docIndexId=64180&taskId=101&prodTypeId=3709945&prodSeriesId=3794423

HP Virtual Connect FlexFabric Solutions Recipe

http://h20000.www2.hp.com/bc/docs/support/SupportManual/c02610285/c02610285.pdf


Virtual Connect Ethernet Cookbook Virtual Connect can be used to support both Ethernet and Fibre Channel connections. The Virtual Connect Ethernet Cookbook is provided with basic Virtual Connect configurations for both 1Gb and 10Gb solutions, whereas the Virtual Connect FlexFabric Cookbook provides additional scenarios that leverage the new FCoE protocols. If you are new to Virtual Connect it is highly recommended that you also review the existing Virtual Connect Ethernet Cookbook

Virtual Connect Ethernet (with Flex-10) Channel Cookbook http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01990371/c01990371.pdf

(www.hp.com/go/blades)

Virtual Connect Fibre Channel Cookbook Virtual Connect can be used to support both Ethernet and Fibre Channel connections; however, this guide is focused completely on the Ethernet configuration.

For Fibre Channel connectivity, please refer to the Virtual Connect Fibre Channel Cookbook http://bizsupport1.austin.hp.com/bc/docs/support/SupportManual/c01702940/c01702940.pdf

(www.hp.com/go/blades)

Virtual Connect 3.15 Firmware Release Virtual Connect firmware version 3.15 is the initial release to provide Fibre Channel over Ethernet (FCoE) support within Virtual connect. FCoE support is provided within the FlexFabric Modules discussed in the document.

Please refer to the Virtual Connect 3.15 Release note for further details on new features and resolved issues.

NOTE: When VC 8Gb 20-port FC module or VC FlexFabric 10Gb/24-port module Fibre Channel uplink ports are configured to operate at 8Gb speed and connecting to HP B-series (Brocade) Fibre Channel SAN switches, the minimum supported version of the Brocade Fabric OS (FOS) is v6.3.1 and v6.4.x. In addition, a fill word on those switch ports must be configured with option Mode 3 to prevent connectivity issues at 8Gb speed.

On HP B-series (Brocade) FC switches use command portCfgFillWord (portCfgFillWord ) to configure this setting:

Although this setting only affects devices logged in at 8G, changing the mode is disruptive regardless of the speed the port is operating at. The setting is retained and applied any time an 8G device logs in. Upgrades to FOS v6.3.1 or v6.4 from prior releases supporting only modes 0 and 1 will not change the existing setting, but a switch or port reset to factory defaults with FOS v6.3.1 or v6.4 will be configured to Mode 0 by default. The default setting on new units may vary by vendor. Please use portcfgshow CLI to view the current portcfgfillword status for that port.

Mode Link Init/Fill WordMode 0 IDLE/IDLEMode 1 ARBF/ARBFMode 2 IDLE/ARBFMode 3 If ARBF/ARBF fails use IDLE/ARBF


Modes 2 and 3 are compliant with FC-FS-3 specifications (standards specify the IDLE/ARBF behavior of Mode 2 which is used by Mode 3 if ARBF/ARBF fails after 3 attempts). For most environments, Brocade recommends using Mode 3, as it provides more flexibility and compatibility with a wide range of devices. In the event that the default setting or Mode 3 does not work with a particular device, contact your switch vendor for further assistance. When connecting to Brocade SAN Switches at 8Gb, portCfgFillWord must be set to Mode 3 If ARBF/ARBF fails use IDLE/ARBF. In order to use Mode 3, FOS v6.3.1 or v6.4.x or better is required. Virtual Connect FlexFabric Hardware Overview

Virtual Connect FlexFabric is the first Data Center Bridging (DCB) and Fibre Channel over Ethernet (FCoE) solution introduced into the HP BladeSystem portfolio. It provides 24 line rate ports, Full-Duplex 240Gbps bridging, single DCB-hop fabric. As shown in Image 1, there are 8 faceplate ports. Ports X1-X4 are SFP+ transceiver slots only; which can accept a 10Gb or 4Gb/8Gb SFP+ transceiver. Ports X5-X8 are SFP and SFP+ capable which can accept 1Gb or 10Gb Ethernet connections, and do not support Fibre Channel transceivers.

Virtual connect FlexFabric Uplink Port Mappings In it is important to note how the external uplink ports on the FlexFabric module are configure. The graphic below outlines the type and speed each port can be configured as. Ports X1 X4; Can be configured as 10Gb Ethernet or Fibre Channel, FC speeds supported =

2Gb, 4Gb or 8Gb using 4Gb or 8Gb FC SFP modules, please refer to the FlexFabric Quick Spec for a list of supported SFP modules

Ports X5 X8: Can be configured as 1Gb or 10Gb Ethernet Ports X7 X8; Are also shared as internal cross connect Uplink ports X1-X4 support 0.55m length DAC as stacking or uplink Uplink Ports X5-X8 support 0.57m length DAC as stacking or uplink Note; 5m DAC cables are supported on all ports with FlexFabric, in addition, 7m DAC cables are also supported on ports X5 through X8.

Note: The CX-4 port provided by the Virtual Connect Flex-10 and legacy modules has been depreciated.

Note: Even though the Virtual Connect FlexFabric module supports Stacking, stacking only applies to Ethernet traffic. FC uplinks cannot be consolidated, as it is not possible to stack the FC ports, nor provide a multi-hop DCB bridging fabric today.

Fig

Noto E Figcon

ure 1 - FlexF

te: Even thouEthernet traffic

ure 2 - FlexNnfigured as Eth

abric Module

ugh the Virtua. FC uplinks

NIC Connectiohernet, FCoE o

e port configu

al Connect Flecannot be co

ons It is impor iSCSI. Phy

ration, speeds

exFabric modunsolidated, as

portant to noteysical Function

Introducti

s and types

ules support Ss it is not poss

e that Physicalns 1, 3 and 4

ion to Virtual C

Stacking, stacsible to stack

l Function two4 are assigned

Connect FlexFab

king only appthe FC ports.

o (pf2) can bed as Ethernet o

bric 9

plies

e only

Tunneled VLAN and Mapped VLANS 10

Tunneled VLAN and Mapped VLANS

Virtual Connect provides two Ethernet networks connection methods. Both of these connection types are discussed within the following scenarios.

Tunnel vs. Map VLAN tags setting It is important to note that the behavior of both vNets and Shared Uplink Sets is dependent on whether VLAN Tunnel or Map VLAN Tags is set. Server VLAN Tagging Support, as configured in the Advanced Ethernet Settings tab of Virtual Connect is a Domain wide configuration.

If Virtual Connect is set to Tunnel Mode, you can do the following; Create a Shared Uplink Set which can support several VLANs up to the publish limits. These VLANs can be presented to a Server NIC, one at a time No multiple VLANS supported,

frames are presented to the NIC untagged Create a vNet which can support both TAGGED and UNTAGGED frames, if tagged the host

system will need to interpret those tags

If Virtual Connect is set to Map VLAN Tags Mode, you can do the following; Create a Shared Uplink Set (the behavior of a SUS changes and now provides the ability to

connect multiple networks to a NIC) which can support several VLANs up to the publish limits. These VLANs can be presented to a Server NIC, as either a single Network (where VC will

remove the tags and present an untagged frame to the NIC), or as multiple Networks, where VC will present all frames with their VLAN tags, in which case the host system will need to interpret the tags (one network could be configured as untagged)

Create a vNet (the behavior of a vNet also changes) a vNet can now only support UNTAGGED frames, which means a vNet could then only support ONE VLAN/network

vNet There are two modes of operation for the vNet. The first is a simple vNet that will pass untagged frames. The second is a vNet tunnel which will pass tagged frames for one or many VLANs.

The vNet is a simple network connection between one or many server NICs to one or many uplink ports

A vNet could be used to connect a single VLAN, no tagging, to one or many server NICs, if this network is part of a VLAN, by configuring the upstream switch port as an access or untagged port, by extension, any server connected to this vNet would reside in that VLAN, but would not need to be configured to interpret the VLAN tags.

A tunneled vNet will pass VLAN tagged frames, without the need to interpret or forward those frames based on the VLAN tag. Within a tunneled vNet the VLAN tag is completely ignored by Virtual Connect and the frame is forwarded to the appropriate connection (server NIC[s] or uplinks) depending on frame direction flow. In this case, the end server would need to be configured to interpret the VLAN tags. This could be a server with a local operating system, in which the network stack would need to be configured to understand which VLAN the server was in, or a virtualization host with a vSwitch supporting multiple VLANs.

The tunneled vNet has no limit to the number of VLANs it can support.


Benefits of a vNet If no VLAN support is required, support for a single specific VLAN being presented as untagged or many VLANs need to be presented to the server a vNet is a very simple network to configure and manage within Virtual Connect.

A vNet can be utilized in one of two ways, a simple vNet, used to pass untagged frames and a tunneled vNet. A tunneled vNet can be used to pass many VLANs without modifying the VLAN tags, functioning as a transparent VLAN Pass-Thru module.

Shared Uplink Set (SUS) The SUS provides the ability to support VLAN tagging and forward frames based on the VLAN tags of those frames. The SUS connects one or many server NICs to one or many uplink ports. A SUS would be configured for the specific VLANs it will support. If support for additional VLANs is required, those VLANs need to be configured within the SUS.

When connecting a server NIC to a network within a SUS, there are two choices provided. The key difference between these two options is the state in which the frame is passed to the server NIC;

1. Select a single network which would be mapped to a specific VLAN.

If a single network is selected, the frames will be presented to the server NIC WITHOUT a VLAN tag. In this case the host operating system does not need to understand which VLAN it resides in. When the server transmits frames back to VC, those frames will not be tagged, however; Virtual Connect will add the VLAN tag and forward the frame onto the correct VLAN.

2. Select multiple networks which would provide connectivity to several VLANs.

The Map VLAN Tags feature provides the ability to use a Shared Uplink Set to present multiple networks to a single NIC. If you select Multiple Networks when assigning a Network to a server NIC, you will have the ability to configure multiple Networks (VLANS) on that server NIC. At this point VC tags ALL the packets presented to the NIC unless the Native check box is selected for one of the networks, in which case packets from this network (VLAN) will be untagged, and any untagged packets leaving the server will be placed on this Network (VLAN).

With Mapped VLAN Tags, you can create a Shared Uplink Set that contains ALL the VLANs you want to present to your servers, then present only ONE network (the one associated with the VLAN we want the server NIC in) to the Windows, LINUX or the ESX Console NIC, then select Multiple Networks for the NIC connected to the ESX vSwitch and select ALL the networks that we want presented to the ESX host vSwitch. The vSwitch will then break out the VLANs and present them to the guests. Using Mapped VLAN Tags minimizes the number of uplinks required.

In order to utilize the Multiple Networks feature of Virtual Connect, the Map VLAN Tags feature, needs to be turned on under the Ethernet Settings/Advanced tab within the Virtual Connect manager or the Virtual Connect CLI.

Benefits of a SUS A Shared Uplink Set can be configure to support both tagged and un-tagged network traffic to a server NIC, which simplifies the overall configuration and minimizes the number of uplink cables required to support the network connections.


Virtual Connect VLAN Support SUS - Restrictions and limitations Shared Uplink Sets provide administrators with the ability to distribute VLANs into discrete and defined Ethernet Networks (vNet.) These vNets can then be mapped logically to a Server Profile Network Connection allowing only the required VLANs to be associated with the specific server NIC port. This also allows the flexibility to have various network connections for different physical Operating System instances (i.e. VMware ESX host and physical Windows host.)

The following Shared Uplink Set rules apply per domain: 320 VLANs per Virtual Connect Ethernet module. Note; Every VLAN on every uplink counts

towards the 320-VLAN limit. If a Shared Uplink Set is comprised of multiple uplinks *from the same module*, each VLAN on that Shared Uplink Set is counted multiple times towards 320 limit.

128 VLANs per Shared Uplink Set (64 VLAN Support is provided in VC firmware older than 2.30)

28 VLANs per Ethernet server profile connection regardless of physical vs. FlexNIC connections. On Flex-10 adapters, this amounts to 28 x 4 = 112 VLANs per physical 10Gb port. Note; only applies when in Mapped VLAN mode.

The above configuration rules apply only to a Shared Uplink set. If support for a larger numbers of VLANs is required, the VC domain can be set to Tunneled VLAN mode and a VLAN Tunnel con be configured to support a large number of VLANs.

Please see the Virtual Connect 3.15 Release Notes for future details.

S

O

R

Single

OverviThisSingBayenclrequthat Win

RequiremThisFlexin se10GChacon

Paircon

It is andexac700Inter

FiguFlex

e Dom

iew Cookbook w

gle HP BladeSs 1 and 2. Vlosures, whichuirements. Ea configurationndows and/o

ments Cookbook w

xFabric modulerver Bay 1. Gb FlexFabricannel over Ethnect to the Fle

r of managed nected to the

assumed that no VC Netwmples are pro00 enclosure wrconnect module

ure 3 - c700xFabric modul

main/E

will provide sevSystem c7000Virtual Connech provides a sach scenario wn and include r VMware vSp

will utilize a sines installed in The server wi adapter porternet (FCoE).

exFabric modu

Ethernet switcFlexFabric mo

t a Virtual Conworks, uplink seovided in Appwith Half Heighte bays 1& 2.

00 enclosure wes in Intercon

Enclos

veral configur0 enclosure wict FlexFabric asingle point ofwill provide a both GUI andphere will also

ngle HP Bladen I/O Bays 1 ill connect to ts. Each Flex Port 1 will cule in Bay 2.

ches, as well odules.

nnect Domainets or Server

pendix C. t G7 BladeSyst

with Half Heignect module b

ure Sc

ration scenariith two Virtualalso supports Mf managemenn overview ofd CLI (scriptedo be provided

eSystem c700and 2 and a the FlexFabric

xFabric Adaptonnect to the

as a pair of B

n has been creProfiles have

em servers and

ght G7 BladeSbays 1& 2

Singl

cenari

ios of Virtual Cl Connect FlexMulti-Enclosur

nt and can furf the configurad) methods. Wd.

00 enclosure w BL460c G7 hc models in Bater port suppo FlexFabric mo

Brocade Fibre

eated either thbeen created

d two Virtual Co

System servers

e Domain/Enc

os

Connect FlexFxFabric modure stacking, forther reduce caation, show hWhere possib

with TWO Virhalf height Blaays 1 and 2, orts Ethernet aodule in Bay

e Channel swi

hrough the GU. Virtual Con

onnect FlexFab

s and two Vir

losure Scenario

Fabric, using ules installed ior up to 4 able connectiow to comple

ble, examples

rtual Connect adeSystem Sethrough with nd iSCSI or F1 and Port 2

tches are

UI or a CLI scnnect scripting

bric modules in

rtual Connect

os 13

a n

vity ete for

rvers two

Fibre will

ript g

Scenario 1 Simple vNet with Active/Standby Uplinks and FCoE Windows 2008 R2 14

Scenario 1 Simple vNet with Active/Standby Uplinks and FCoE Windows 2008 R2

Overview This simple configuration uses the Virtual Connect vNet along with FCoE for SAN connectivity. When VLAN mapping is not required, the vNet is the simplest way to connect Virtual Connect to a network and server. In this scenario, the upstream network switch connects a network to a single port on each FlexFabric module. In addition, Fibre Channel uplinks will also be connected to the FlexFabric modules to connect to the existing Fibre Channel infrastructure.

No special upstream switch configuration is required as the switch is in the factory default configuration, typically configured as an Access or untagged port on either the default VLAN or a specific VLAN, either way, Virtual Connect does not receive VLAN tags.

When configuring Virtual Connect, we can provide several ways to implement network fail-over or redundancy. One option would be to connect TWO uplinks to a single vNet; those two uplinks would connect from different Virtual Connect modules within the enclosure and could then connect to the same or two different upstream switches, depending on your redundancy needs. An alternative would be to configure TWO separate vNets, each with a single, or multiple, uplink configured. Each option has its advantages and disadvantages. We will review the first option in this scenario.

In addition, several vNets can be configured to support the required networks to the servers within the BladeSystem enclosure. These networks could be used to separate the various network traffic types, such as iSCSI, backup, VMotion from production network traffic.

This scenario will also leverage the Fibre Channel over Ethernet (FCoE) capabilities of the FlexFabric modules. Each Fibre channel fabric will have one uplink connected to each of the FlexFabric modules.

Requirements This scenario will support both Ethernet and fibre channel connectivity. In order to implement this scenario, an HP BladeSystem c7000 enclosure with one or more server blades and TWO Virtual Connect FlexFabric modules, installed in I/O Bays 1& 2 are required. In addition, we will require ONE or TWO external Network switches. As Virtual Connect does not appear to the network as a switch and is transparent to the network, any standard managed switch will work with Virtual Connect. The Fibre Channel uplinks will connect to the existing FC SAN fabrics. The SAN switch ports will need to be configured to support NPIV logins. One uplink from each FlexFabric module will be connected the existing SAN fabrics.

Figuthe fswit

TheX1

ure 4 - Physfirst network stch.

SAN fabric ito SAN switc

Scenario 1

sical View; switch, a sing

s also connech/fabric B.

Simple vNet w

Shows a single uplink from

cted as Modu

with Active/Sta

gle Ethernet upm Port X5 on M

le 1 port X1 t

ndby Uplinks a

plink from PorModule 2 to P

o SAN switch

and FCoE Wi

rt X5 on Modort 1 on the s

h/fabric A an

ndows 2008 R

ule 1 to Port 1second netwo

d module 2 p

R2 15

1 on rk

port

I

S

V

FignetwEtheconthe

Installa

Switch cAppCiscapp

ThisConis NThe the sEdgallowThe

VC CLI coIn aa Cthe a

ure 5 - Logwork switch aernet uplinks annects to the e existing SAN

ation a

configurpendices A anco IOS or a Prpendices assum

The switch pVLAN or a sAs an alternVLANS, Virtnetwork, hoand the vNeneed to be c

scenario assnnect domain

NOT configure network switcswitch as an ae, it allows thws a fail-over SAN switch p

mmands ddition to theLI command sactive VCM.

Scenario 1

ical View; Snd a single uare connectedexisting SAN F Fabric B thro

and co

ation nd B provide aroCurve netwmes the followports are confspecific VLANnative, if the swtual Connect wwever; the Viet would needconfigured to umes the swit could be coned for VLAN Tch port shouldaccess device

he switch to pl link or newerports connecti

GUI many ofset. In order t Once logged

Simple vNet w

Shows a singleplink from Pord to the same Fabric A throuough port X1 o

nfigura

a summary of ork infrastruct

wing informatiigured as AC

N and will be fwitch ports wewould forwardrtual Connect

d to be config interpret thosch port is configured for eth

Tunneling andd be configuree and not anolace the port ir connected ping to the Flex

f the configurato connect to Vd in, VC provi

with Active/Sta

e Ethernet uplrt X5 on Mod vNet, vNet-PRugh port X1 oon Module 2

ation

the commandture. The confion: CESS or untaforwarding unere configuredd those tagge domain wouured for VLANe VLAN tags.

nfigured as anher Tunneled the frames aed for Spannither switch. Binto a forwardport to come oxFabric modu

ation settings VC via a CLI, ides a CLI wit

ndby Uplinks a

link from Port ule 2 to the seROD. In add

on Module 1 ( (Bay 2).

ds required tofiguration info

gged ports, entagged framd as TRUNK p

ed frames to thld need to be

N Tunneling. . n Access port or Mapped Vre presented tng Tree EdgeBy configuringding state muconline much qle must be co

within VC ca open an SSHh help menus

and FCoE Wi

X5 on Moduecond networition, SAN FaBay 1) and FC

o configure theormation prov

either presenties ports and forwhe host NICs e configured in The connecte

(not tagging),VLAN mode, hto Virtual Con

e as Virtual Cog the port as Sch quicker thauicker. nfigured to ac

n be also be H connection t. The Virtual

ndows 2008 R

le 1 on the firrk switch. Botabric FCoE_A CoE_B conne

e switch in eitided in the

ng the Defaul

warding multiconfigured fon Tunnel Moed host would

, the Virtual however, the vnnect as untagonnect appeaSpanning Trean otherwise,

ccept NPIV lo

accomplishedto the IP addr Connect CLI g

R2 16

rst th cts to

ther a

lt

ple or this ode then

vNet gged rs to e this

ogins.

d via ress of guide


also provides many useful examples. Throughout this scenario the CLI commands to configure VC for each setting are provided.

Configuring the VC module Physically connect Port 1 of Network switch 1 to Port X5 on the VC module in Bay 1. Physically connect Port 1 of the second Network switch to Port X5 of the VC module in Bay 2, if

you have only one network switch, connect VC port 1 (Bay 2) to an alternate port on the same switch. This will NOT create a network loop and Spanning Tree is not required

Physically connect Port X1 on the FlexFabric module (Bay 1) to switch port in SAN Fabric A Physically connect Port X1 on the FlexFabric module (Bay 2) to switch port in SAN Fabric B

Configuring Fast MAC Cache Failover When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades must now be reached on this newly active connection. Enabling Fast MAC Cache Failover forces Virtual Connect to transmit Ethernet packets on newly

active links, which enables the external Ethernet switches to identify the new connection (and update their MAC caches appropriately). This transmission sequence repeats a few times at the MAC refresh interval (five seconds is the recommended interval) and completes in about one minute.

Configuring the VC Module for VLAN Tunneling and Fast Mac Cache Fail-over via GUI (Ethernet settings)

Virtual Connect tunnel mode can be enabled to provide the ability to tunnel an unlimited number of tagged VLANs through a Virtual Connect vNet. This can be very using in a network environment that utilizes a large number of VLANs. Note; for this imply scenario, the Domain mode could be configure for either Map VLAN tags or Tunnel mode.

Enable Tunnel VLAN Tags within Virtual Connect On the Virtual Connect Manager screen, Left pane, click Ethernet Settings, Advanced Settings Select Tunnel VLAN Tags Select Fast MAC Cache Fail-over with a refresh of 5 Select Apply

Configuring the VC Module for VLAN Tunneling and Fast Mac Cache Fail-over via CLI (Ethernet settings)

The following command can be copied and pasted into an SSH based CLI session with Virtual Connect; # Set Advanced Ethernet Settings to "Tunnel VLAN Tags" and Enable Fast MAC cache fail-over set enet-vlan vlantagcontrol=Tunnel (click apply) Click the Other tab set mac-cache Enabled=True Refresh=5 (click apply)

Figu

Fig

ure 6 - Confi

ure 7 - Set Fa

Scenario 1

gure Tunnel M

ast MAC Cac

Simple vNet w

Mode (under E

che (under Eth

with Active/Sta

Ethernet Settin

hernet Settings

ndby Uplinks a

ngs Advance

s Advanced

and FCoE Wi

ed Settings)

Settings - Oth

ndows 2008 R

her)

R2 18


Defining a new vNet via GUI Create a vNet and name it vNet-PROD Login to Virtual Connect, if a Domain has not been created, create it now, but cancel out of the

configuration wizards after the domain has been created. On the Virtual Connect Manager screen, click Define, Ethernet Network to create a vNet Ether the Network Name of vNet-PROD

Note; Do NOT select any of the options (ie; Smart Link, Private Networks etc.) Select Add Port, then add the following ports;

Enclosure 1, Bay 1, Port X5 Enclosure 1, Bay 2, Port X5

Leave Connection Mode as Auto Select Apply Note: By connecting TWO Uplinks from this vNet we have provided a redundant path to the network. As each uplink originates from a different VC module, one uplink will be Active and the second will be in Standby. This configuration provides the ability to lose an uplink cable, network switch or depending on how the NICs are configured at the server (teamed or un-teamed), even a VC module.

Note: Smart Link In this configuration Smartlink should NOT be enabled. Smartlink is used to turn off downlink ports within Virtual Connect, if ALL available uplinks to a vNet are down. We will use Smartlink in a later scenario.

Defining a new vNet via CLI The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect # Create the vNet "vNet-PROD" and configure uplinks as discussed above add Network vNet-PROD add uplinkport enc0:1:X5 Network=vNet-PROD speed=auto add uplinkport enc0:2:X5 Network=vNet-PROD speed=auto set network vNet-PROD SmartLink=Disabled

D

D

Figinfoas b

Defining aCrea

Crea

Defining S

The Con#CrAddAdd

ure 8 - Definormation. If thbelow

a new (FCate a Fabric a

On the VirtuEther the NeSelect Add P

Select Apply

ate a second On the VirtuEther the NeSelect Add P

Select Apply

SAN Fabri following comnnect reate the SANd fabric FCoE_d fabric FCoE_

Scenario 1

ne Ethernet Nhe connected

oE) SAN and name it ual Connect Metwork Name Port, then add

Enclosure 1, y

Fabric and naual Connect Metwork Name Port, then add

Enclosure 1, y

ics via CLmmand(s) can

N Fabrics FCoE_A Bay=1 Po_B Bay=2 Por

Simple vNet w

etwork (vNet-switch suppor

Fabric viaFCoE_A

Manager scree of FCoE_Ad the following

Bay 1, Port X

ame it FCoE_Manager scree of FCoE_B d the following

Bay 2, Port X

I n be copied a

E_A and FCorts=1 rts=1

with Active/Sta

-PROD). Noterts LLDP, the c

a GUI

en, click Defin g ports;

1

_B en, click Defin g ports;

1

nd pasted into

E_B and conf

ndby Uplinks a

: The Port Staconnected to i

ne, SAN Fabr

ne, SAN Fabr

o an SSH bas

figure uplinks

and FCoE Wi

tus and Connnformation sh

ic to create th

ic to create th

sed CLI sessio

as discussed

ndows 2008 R

nected to hould be displ

he first Fabric

he second Fab

on with Virtual

above

R2 20

layed

bric

l

DE

Figuport

Figuserv

Defining aEach server N

On Prio

NotNIC

ure 9 FCoEt numbers on

ure 10 FCovers powered

a Server PNIC will con

the Virtual CoCreate a serIn the NetwoIn the NetwoExpand the Do not confiIn the Assign

r to applying

te: you shouldCs 1&2 should

Scenario 1

E SAN fabricsthe right

oE SAN Serveon)

rofile withnect to a spe

onnect Managrver profile caork Port 1 droork Port 2 droFCoE Connecigure FC SANn the Profile to the profile, e

d now have ad be connecte

Simple vNet w

s configured w

er Connection

h NIC andecific networ

ger screen, clialled App-1 op down box,op down box,ctions box, fo

N or iSCSI Coo a Server Bansure that the

a server profiled to network

with Active/Sta

with a single 4

ns (After serve

d FCoE Cork.

ick Define, Se select vNet- select vNet-r Bay 1, selecnnection y, select Bay server in Bay

e assigned to vNet_PROD a

ndby Uplinks a

4Gb uplink pe

er profiles hav

onnections

erver Profile to

-PROD -PROD ct FCoE_A for

1 and apply y 1 is currently

Bay 1, with 2and FCoE SAN

and FCoE Wi

er fabric. No

ve been create

s, via GUI

o create a Ser

r Bay 2, select

y OFF

2 Server NIC N fabrics FCo

ndows 2008 R

ote the bay an

ed, assigned

I

rver Profile

t FCoE_B

connections. oE_A and FCo

R2 21

nd

and

oE_B.

DDefining aThe Con# Caddset eset eset fset fassi Figu

Notthe LOM

a Server P following comnnect reate and Ass

d profile App-1enet-connectioenet-connectiofcoe-connectiofcoe-connectiogn profile Ap

ure 11 - Defin

te: The speed FCoE connect

M:2-b.

Scenario 1

rofile withmmand(s) can

sign Server Pr1 on App-1 1 pxon App-1 2 pxon App-1:1 Faon App-1:2 Fap-1 enc0:1

e Server Profile

of the NIC antions are assig

Simple vNet w

h NIC andn be copied a

rofile App-1 to

xe=Enabled Nxe=Disabled Nabric=FCoE_Aabric=FCoE_B

e (App- 1)

nd SAN conngned to the tw

with Active/Sta

d FCoE Cond pasted into

o server bay 1

Network=vNeNetwork=vNeA SpeedType=B SpeedType=

nections, as wwo SAN fabric

ndby Uplinks a

onnectionso an SSH bas

1

et-PROD et-PROD =4Gb =4Gb

well as the MAcs created ea

and FCoE Wi

s, via CLI sed CLI sessio

AC and WWNarlier and use

ndows 2008 R

on with Virtual

N. Also, note ports LOM:1-

R2 22

l

that -b and

R

Figu

Review

In thModoneFab Weto sguaenceac The Addincr

ure 12 - Serve

w his scenario wdule, by doin

e uplink will bebrics, utilizing

e created at seustain a link o

arantees that Alosure. Alternh vNet, provi

FCoE SAN fa

ditional uplinkrease perform

Scenario 1

er Profile View B

we have createg so we provie active and t a single uplin

erver profiles, or module failALL server to snatively, we cding an Activ

abric connect

ks could be adance and/or

Simple vNet w

Bay 1

ed a simple vide redundanthe alternate unk each.

with two NICure and not loserver commuould have cre

ve/Active upli

s to each SAN

dded to either availability.

with Active/Sta

vNet utilizing ut connections uplink will be

Cs connected ose connectionications witheated a two vnk scenario.

N fabric over

r the San fabr

ndby Uplinks a

uplinks origin out of the Vir in standby. W

to the same von to the netwhin the enclosuNet and assig

a single uplin

rics or the Ethe

and FCoE Wi

ating from thertual Connect We create tw

vNet, which pork; this confiure will remaigned uplinks f

nk per module

ernet network

ndows 2008 R

e each FlexFa domain, whe

wo FCoE SAN

rovides the abiguration alsoin inside the from one mod

e.

ks, which coul

R2 23

abric ere

bility o

dule to

d

RResults We haveFCo

AlthG7 they

Figu3 Et

The YouNICwe serv

NotG6

Figu

Notcan

Windo have successe created a se

oE connections

ough both Eth servers; eachy appear in th

ure 13 - Examhernet persona

following grau will also notiCs are currentdid not requir

ver would then

e: the BL465c and BL680c G

ure 14 - Wind

te: The NICs t go into Netw

Scenario 1

ows 200sfully configurerver profile tos created with

hernet and Fib capability (LAe server as in

mple of Emulex'alities and one F

aphics show aice that Windly configured re SAN connen have 8 NIC

c G7 and BL6G7 utilizes an

dows 2008 R2

that are not cowork Connecti

Simple vNet w

08 R2 Ned FlexFabrico connect to thin the profile

bre channel cAN and SANndividual netw

s OneManageFCoE personali

a Windows 2dows believes within FlexFaectivity on this

C ports availab

685c G7 utilizn NC553i chi

Network Conn

onfigured withions for the W

with Active/Sta

Networkc with a simplethe vNet with .

onnectivity is N) is provided work and SAN

r Utility (formerity per port, as

008 R2 serve there are 6 N

abric, the extras server, the Fble to the OS.

ze a NC551i ipset.

nections (2 Con

hin VC will apWindows 2008

ndby Uplinks a

king Exae vNet and re TWO NICs a

provided by by a differen

N adapters.

rly known as H configured in t

er with TWO NICs within tha NICs are ofFCoE connecti.

chipset, wher

nnections Active

ppear with a 8 server and

and FCoE Wi

amples edundant SANand the SAN

the CNA adat component o

BA Anywhere).the server profi

FlexNICs conhis server. Hoffline and couions could be

reas the BL46

e

red x as not cDisable any N

ndows 2008 R

N fabrics. Wfabrics using

apter used theof the adapte

. Note that therle.

figured at 6G

owever, only Tuld be disable deleted and

60c G7, BL62

connected. YoNICs that are

R2 24

We the

e in r,

re are

Gb. TWO d. If the

0c

ou not

currLOMadd

Figu

Figu

Not100200

rently in use. M:1 and threedresses to veri

ure 15 - Wind

ure 16 - Wind

e: In windows0MB incremen03 as a 2Gb N

Scenario 1

Windows asse on LOM:2. fy which NIC

dows 2008 R2

dows 2008 R2

s 2003 the Nnts above 1GbNIC. Window

Simple vNet w

signs the NIC You may nee is which.

Extra Network

Network Conn

NIC speeds mab. IE: if a NICws 2008 doe

with Active/Sta

s as NIC 1-6,ed to refer to t

Connections

nection Status

ay not be showC is configurees not have thi

ndby Uplinks a

, whereas threthe FlexFabric

Disabled

wn accuratelyed for 2.5Gb is limitation.

and FCoE Wi

ee of the NICc server profile

y when speed it will be disp

ndows 2008 R

s will reside oe for the NIC

ds are configuplayed in Win

R2 25

on MAC

red in ndows

Figuconf

The concoulfail,modwas

Figu

ure 17 - Wifigured two o

following granected to the ld be teamed Virtual Conn

dule failure, ths the active N

ure 18 - Both N

Scenario 1

ndows 2008 f the NICs an

aphics providenetwork, initia to provide Nect would fail

he servers NICIC, NIC team

NICs for Profile

Simple vNet w

R2, Device Md two FCoE H

es an exampleally each NICIC fail-over rel-over to the stC teaming soing would fai

e App-1are con

with Active/Sta

Manager, SIX HBAs.

e of a WindoC has its own edundancy. tandby uplinkftware would l-over to the s

nected to the n

ndby Uplinks a

NICs are sho

ows 2008 R2 TCP/IP addreIf an active up

k. In the even see one of thstandby NIC.

network through

and FCoE Wi

own, however,

server with TWess, alternativeplink or netwot of a Virtual

he NICs go of

h vNet-PROD

ndows 2008 R

, we have on

WO NICs ely, both NICork switch weConnect FlexFffline, assumin

R2 26

ly

Cs re to Fabric ng it

NNIC TeamIf hinetwteamquiteYou1 to

The andstanthe s

Figu

Figu

Variyou

ming gher availabi

work configuraming. In this ee simple. Ho will note the

o Bay 2 for ex

following gra connected to

ndby uplinks, standby NIC.

ure 19 Team

ure 20 - Both N

ious modes ca can select the

Scenario 1

lity is desiredations. Simplexample, we wever, if mult BAY#-Port# ixample.

aphics provideo the network.if a VC FlexFa

m both NICs, us

NICs for Profile

an be configue team and ed

Simple vNet w

, NIC teamingy, open the Nhave only TWtiple NICs arendication with

e an example In the event abric module

sing the HP Net

e App-1are team

ured for NIC Tdit its properti

with Active/Sta

g in Virtual CoNIC teaming UWO NICs avaie available, enhin each NIC.

e of a Window of an Uplink were to fail, t

twork Configur

med and conne

Teaming, suchies. Typically

ndby Uplinks a

onnect works Utility and conilable, so selensure that the. You would

ws 2008 R2 s or switch failthe NIC team

ration Utility

ected to the net

h as NFT, TLB y, the default s

and FCoE Wi

the same wanfigure the avecting NICs foe correct pair otypically TEA

server with TWure, VC will faing software w

twork through v

etc. Once thsettings can b

ndows 2008 R

ay as in standavailable NICs or teaming wiof NICs is teaM a NIC from

WO NICs teamail-over to thewould fail-ove

vNet-PROD

he Team is crebe used.

R2 27

ard for ll be

amed. m Bay

med e er to

eated,

R

Figu

Figu

Results Figu

ure 21 - View

ure 22 - Both

Windoure 23 - Durin

Scenario 1

Network Co

NICs are team

ows 200ng server boot,

Simple vNet w

onnections NIC

ed and connec

08 R2 Syou can see th

with Active/Sta

C Team #1 W

ct to the networ

SAN Coat Port 1 of the

ndby Uplinks a

Windows

rk with a comm

onnectivie FlexHBA is co

and FCoE Wi

on IP Address

ity onnected to an

ndows 2008 R

MSA1000 SAN

R2 28

N LUN

S

Figu

SummaWe path

Whconinfratheirservactivconf

Addto aIf adadju

As aprofserv

ure 24 - Wind

ary presented a Vh SAN fabric

en VC profilenected througastructure thror own IP addrver could acceve at the timefigured for 4G

ditional NICs c total of 6 NICdditional or leusted.

additional serfiles, configurever bays.

Scenario 1

dows 2008 R2

Virtual Connefor storage co

App-1 is appgh each FlexFaough the 10Gress or as a paess the networ. Each NIC is

Gb of SAN ba

could be addCs, the NIC s

ess SAN band

vers are addee the NICs fo

Simple vNet w

Disk Administr

ect Network sconnectivity.

plied to the seabric module b uplinks. Theair of TEAMErk through eiths configured fandwidth.

ed within Flexpeed can the

dwidth is requ

ed to the enclor vNet-PROD

with Active/Sta

ator. Note; tha

cenario by cre

erver in bay1 connected to ese NICs coulD NICs. Eitheher NIC or eitfor 6Gb of ne

xFabric, by sin be adjustedired, the spee

osure, simply and the SAN

ndby Uplinks a

at D: is the SAN

eating a simp

and is power vNet-PRODld now be coner NIC could ther uplink caetwork bandw

mply powerind accordingly ed of the SAN

create additio fabrics and a

and FCoE Wi

N attached volu

ple vNet, we i

red up, it has , which connnfigured as in be active. A

able, dependinwidth and eac

ng the server o to suit the ne

N connection c

onal profiles, apply them to

ndows 2008 R

ume

ncluded a du

one NIC nects to the nendividual NICsAs a result, thisng on which ih FCoE port is

off and addineds of each Ncan also be

or copy existo the appropri

R2 29

al

etwork s with s is s

ng up NIC.

ting ate

Scenario 2 Shared Uplink Sets with Active/Active uplinks and 802.3ad (LACP) - Windows - Ethernet and FCoE 30

Scenario 2 Shared Uplink Sets with Active/Active uplinks and 802.3ad (LACP) - Windows - Ethernet and FCoE

Overview This scenario will implement the Shared Uplink Set (SUS) to provide support for multiple VLANs. In this scenario, the upstream network switches connect a shared uplink set to two ports on each FlexFabric modules, LACP will be used to aggregate those links.

As multiple VLANs will be supported in this configuration, the upstream switch ports connecting to the FlexFabric modules will be configured to properly present those VLANs. In this scenario, the upstream switch ports will be configured for VLAN trunking/VLAN tagging.

When configuring Virtual Connect, we can provide several ways to implement network fail-over or redundancy. One option would be to connect TWO uplinks to a single virtual connect network; those two uplinks would connect from different Virtual Connect modules within the enclosure and could then connect to the same upstream switch or two different upstream switches, depending on your redundancy needs. An alternative would be to configure TWO separate Virtual Connect networks, each with a single, or multiple, uplinks configured. Each option has its advantages and disadvantages. We will review the second option in this scenario.

In addition, several Virtual Connect Networks can be configured to support the required networks to the servers within the BladeSystem enclosure. These networks could be used to separate the various network traffic types, such as iSCSI, backup, VMotion from production network traffic.

This scenario will also leverage the Fibre Channel over Ethernet (FCoE) capabilities of the FlexFabric modules. Each Fibre channel fabric will have two uplinks connected to each of the FlexFabric modules.

Requirements This scenario will support both Ethernet and fibre channel connectivity. In order to implement this scenario, an HP BladeSystem c7000 enclosure with one or more server blades and TWO Virtual Connect FlexFabric modules, installed in I/O Bays 1& 2 are required. In addition, we will require ONE or TWO external Network switches. As Virtual Connect does not appear to the network as a switch and is transparent to the network, any standard managed switch will work with Virtual Connect. The Fibre Channel uplinks will connect to the existing FC SAN fabrics. The SAN switch ports will need to be configured to support NPIV logins. Two uplinks from each FlexFabric module will be connected the existing SAN fabrics.

Scenario

Figand1 aupli

o 2 Shared Up

ure 25 - Phyd 2 on the firstnd 2 on the sinks per fabric

plink Sets with A

ysical View; St network switecond networc, from ports X

Active/Active u

hows two Ethetch and two Erk switch. TheX1 and X2 on

uplinks and 80

ernet uplinks Ethernet uplinke SAN fabricsn module 1 to

2.3ad (LACP) -

from Ports X5ks from Ports Xs are also con Fabric A and

- Windows - Eth

5 and X6 on MX5 and X6 onnnected redund ports X1 and

hernet and FCo

Module 1 to Pn Module 2 tondantly, with Td X2 to Fabric

oE 31

orts 1 o Ports TWO c B.

I

S

V

Scenario

FigNICVLAVLAPortconthe

Installa

Switch cAppCiscapp

NotsamportThe the sEdgallowThe con

VC CLI coManordeloggVC

o 2 Shared Up

ure 26 - LogCs 1 and 2 arAN_102-x throAN-Trunk-2 rests X5 and X6

nnects to the e existing SAN

ation a

configurpendices A anco IOS or a Prpendices assum

The switch p105. All fracould be coUplink Set w

e: when addime FlexFabric ts will need to network switcswitch as an ae, it allows thws a fail-over SAN connectnecting to the

mmands ny of the confer to connect ged in, VC profor each settin

plink Sets with A

gical View; there connected tough VLAN_1spectively. Th on each FlexFexisting SAN F Fabric B thro

and co

ation nd B provide aroCurve netwmes the followports are confames will be fnfigured as (D

would be confng additionalmodule to the

o be configurech port shouldaccess device

he switch to pl link or newertion will be m

e FlexFabric m

figuration settito VC via a Covides a CLI wng will also be

Active/Active u

e server bladeto VLAN_10105-x, which a

he VLAN-TrunkFabric ModuleFabric A throuough port X1 o

nfigura

a summary of ork infrastruct

wing informatiigured as VLAorwarding to Default) untagigured and sel uplinks to the

e same switch,ed for LACP wd be configuree and not anolace the port ir connected p

made with redumodule must be

ings within VCCLI, open an Swith help mene provided.

uplinks and 80

e profile is con-x, NICs 3 anare part of theks are connece in Bays 1 augh port X1 oon Module 2

ation

the commandture. The confion: AN TRUNK po Virtual Conneged, if so, theet as Defaulte SUS, if the a, in order to e

within the sameed for Spannither switch. Binto a forwardport to come oundant connee configured t

C can also beSSH connectionus. Through

2.3ad (LACP) -

nfigured with nd 4 are conne Shared Uplicted, at 10Gbnd 2. In add

on Module 1 ( (Bay 2).

ds required tofiguration info

orts (tagging) ect with VLANen a correspo. additional upensure all the e Link Aggregng Tree EdgeBy configuringding state muconline much qections to eachto accept NPI

e accomplisheon to the IP ad this scenario

- Windows - Eth

Four FlexNICnected to multink Sets, VLANb, to a networdition, SAN FaBay 1) and FC

o configure theormation prov

to support VLN tags. Optioonding vNet w

links are connuplinks are ac

gation Group.e as Virtual Cog the port as Sch quicker thauicker. h Fabric. SANIV logins.

ed via a CLI coddress of the a the CLI comm

hernet and FCo

Cs and 2 FlexHtiple networksN-Trunk-1 andrk switch, throabric FCoE_ACoE_B conne

e switch in eitided in the

LANs 101 throonally, one VLwithin the Sha

necting from tctive, the swit. onnect appeaSpanning Trean otherwise,

N switch ports

ommand set. active VCM.

mands to confi

oE 32

HBAs.

d ough A

cts to

ther a

ough LAN red

he tch

rs to e this

s

In Once igure


Configuring the VC module Physically connect Port 1 of Network switch 1 to Port X5 on the VC module in Bay 1 Physically connect Port 1 of Network switch 2 to Port X6 on the VC module in Bay 1 Physically connect Port 1 of the second Network switch to Port X5 of the VC module in Bay 2 Physically connect Port 1 of Network switch 1 to Port X6 on the VC module in Bay 2, if you have only one

network switch, connect VC port 1 (Bay 2) to an alternate port on the same switch. This will NOT create a network loop and Spanning Tree is not required

Physically connect Ports X1 and X2 on the FlexFabric module Bay 1 to switch port in SAN Fabric A Physically connect Ports X1 and X2 on the FlexFabric module Bay 2 to switch port in SAN Fabric B

Configuring Fast MAC Cache Failover When an uplink on a VC Ethernet Module that was previously in standby mode becomes active, it can take several minutes for external Ethernet switches to recognize that the c-Class server blades must now be reached on this newly active connection. Enabling Fast MAC Cache Failover forces Virtual Connect to transmit Ethernet packets on newly

active links, which enables the external Ethernet switches to identify the new connection (and update their MAC caches appropriately). This transmission sequence repeats a few times at the MAC refresh interval (five seconds is the recommended interval) and completes in about one minute.

Configuring the VC Module for Map VLAN Tags and Fast Mac Cache Fail-over via GUI (Ethernet settings)

Note: Flex-10 has also provided additional controls when configuring VC for mapped VLAN tags (Multiple Networks over a single link) support. These features provide the ability to set a Custom or Preferred network speed value for each NIC. These are VC domain settings and when configured will limit the maximum configurable speed of a NIC. In order to enable this capability, Mapped VLAN Tags must be enabled.

Enable Map VLAN Tags within Virtual Connect On the Virtual Connect Manager screen, Left pane, click Ethernet Settings, Advanced Settings Select Map VLAN Tags (click apply) Optionally, select a preferred/Maximum link speed Select apply Select the Other tab Select Fast MAC Cache Fail-over with a refresh of 5 Select Apply

Configuring the VC Module for Map VLAN Tags and Fast Mac Cache Fail-over via CLI (Ethernet settings)

The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect

# Set Advanced Ethernet Settings to "Map VLAN Tags" and set "Force server connections" to disabled set enet-vlan vlantagcontrol=map sharedservervlanid=false set mac-cache Enabled=True Refresh=5

Scenario

Noonlyor M Selefor netw # Seset e

Figu

Fig

o 2 Shared Up

te: Do not sey. For the purMaximum Con

ecting the Set Maximum Linworks to 500M

et Advanced enet-vlan Pref

ure 27 - Ethern

ure 28 - Set

plink Sets with A

t a Preferred orpose of this snnection spee

a Custom valk Connection Mb and maxi

Ethernet SettinSpeedType=C

net Settings - M

t Fast MAC C

Active/Active u

or Max speedscenario, we weds. However

lue for Preferr Speed, Sets tmum connect

ngs to a PrefeCustom PrefSp

Map VLAN Tags

ache (under E

uplinks and 80

d for this scenwill not be cor, the CLI com

red Link Connthe respectiveion speed to 2

erred speed ofpeed=500 Ma

s (under Ether

Ethernet Settin

2.3ad (LACP) -

ario. This exnfiguring the

mmands are pr

ection Speed e speed for all2.5Gb.

f 500Mb andaxSpeedType

rnet Settings

ngs Advance

- Windows - Eth

ample is prov custom valuesrovided below

and/or Set al connections

d a Max Spee=Custom Max

Advanced Se

ed Settings - O

hernet and FCo

vided for refers for Preferred

w for reference

a Customer va using multiple

ed of 2500MbxSpeed=2500

ettings)

Other)

oE 34

rence d Link e.

alue e

b 0


Defining a new Shared Uplink Set (VLAN-Trunk-1) Connect Port 1 of FlexFabric module 1 to Port 1 on switch 1 Create a SUS named VLAN-Trunk-1 and connect it to FlexFabric Port X1 on Module 1 On the Virtual Connect Home page, select Define, Shared Uplink Set Insert Uplink Set Name as VLAN-Trunk-1 Select Add Port, then add the following port;


Add Networks as follows (to add a network, right click on the grey bar under the Associate Networks (VLAN) header, the select ADD;

VLAN101-1 = VLAN ID=101 VLAN102-1 = VLAN ID=102 VLAN103-1 = VLAN ID=103 VLAN104-1 = VLAN ID=104 VLAN105-1 = VLAN ID=105

Enable SmartLink on ALL networks Optionally, if one of the VLANs is configured as Default/untagged, on that VLAN only, set

Native to Enabled Click Apply

Defining a new Shared Uplink Set (VLAN-Trunk-2) Connect Port 1 of FlexFabric module 2 to Port 1 on switch 2 Create a SUS named VLAN-Trunk-2 and connect it to FlexFabric Port X1 on Module 2 On the Virtual Connect Home page, select Define, Shared Uplink Set Insert Uplink Set Name as VLAN-Trunk-2 Select Add Port, then add the following port;


Add Networks as follows (to add a network, right click on the grey bar under the Associate

Networks (VLAN) header, the select ADD;

VLAN101-2 = VLAN ID=101 VLAN102-2 = VLAN ID=102 VLAN103-2 = VLAN ID=103 VLAN104-2 = VLAN ID=104 VLAN105-2 = VLAN ID=105

Enable SmartLink on ALL networks Optionally, if one of the VLANs is configured as Default/untagged, on that VLAN only, set

Native to Enabled Click Apply


Defining a new Shared Uplink Set via CLI The following script can be used to create the first Shared Uplink Set (VLAN-Trunk-1)

The following command(s) can be copied and pasted into an SSH based CLI session with Virtual Connect

# Create Shared Uplink Set "VLAN-Trunk-1" and configure uplinks add uplinkset VLAN-Trunk-1 add uplinkport enc0:1:X5 Uplinkset=VLAN-Trunk-1 speed=auto add uplinkport enc0:1:X6 Uplinkset=VLAN-Trunk-1 speed=auto # Create Networks VLAN101-1 through VLAN104-1 for Shared Uplink Set "VLAN-Trunk-1" add network VLAN101-1 uplinkset=VLAN-Trunk-1 VLanID=101 Set Network VLAN101-1 SmartLink=Enabled add network VLAN102-1 uplinkset=VLAN-Trunk-1 VLanID=102 Set Network VLAN102-1 SmartLink=Enabled add network VLAN103-1 uplinkset=VLAN-Trunk-1 VLanID=103 Set Network VLAN103-1 SmartLink=Enabled add network VLAN104-1 uplinkset=VLAN-Trunk-1 VLanID=104 Set Network VLAN104-1 SmartLink=Enabled add network VLAN105-1 uplinkset=VLAN-Trunk-1 VLanID=105 Set Network VLAN105-1 SmartLink=Enabled

The following script can be used to create the Second Shared Uplink Set (VLAN-Trunk-2) # Create Shared Uplink Set "VLAN-Trunk-2" and configure uplinks add uplinkset VLAN-Trunk-2 add uplinkport enc0:2:X5 Uplinkset=VLAN-Trunk-2 speed=auto add uplinkport enc0:2:X6 Uplinkset=VLAN-Trunk-2 speed=auto # Create Networks VLAN101-2 through VLAN104-2 for Shared Uplink Set "VLAN-Trunk-2" add network VLAN101-2 uplinkset=VLAN-Trunk-2 VLanID=101 Set Network VLAN101-2 SmartLink=Enabled add network VLAN102-2 uplinkset=VLAN-Trunk-2 VLanID=102 Set Network VLAN102-2 SmartLink=Enabled add network VLAN103-2 uplinkset=VLAN-Trunk-2 VLanID=103 Set Network VLAN103-2 SmartLink=Enabled add network VLAN104-2 uplinkset=VLAN-Trunk-2 VLanID=104 Set Network VLAN104-2 SmartLink=Enabled add network VLAN105-2 uplinkset=VLAN-Trunk-2 VLanID=105 Set Network VLAN105-2 SmartLink=Enabled

Scenario

Figu

Notthe savaswit

Figu

o 2 Shared Up

ure 29 - Define

te: The Connswitch this upilable in all swtches and por

ure 30 - Active

plink Sets with A

e a Shared Upl

nected to fielink is connecwitch productsts VC is conne

e / Active Shar

Active/Active u

link Set (VLAN-T

ld in the grapcted to. This is. This informected to.

red Uplink Set

uplinks and 80

Trunk-1) and ad

phic above disnformation is

mation can be

2.3ad (LACP) -

dd VLANs

splays the MA provided thro very helpful w

- Windows - Eth

AC address anough LLDP diswhen determi

hernet and FCo

nd port numbscover and is ning which

oE 37

er of not

D

Scenario

Figu

Sumorigsepprofwhicreawou

Figu

Defining aCrea

o 2 Shared Up

ure 31 - Assoc

mmary Notginating from arate and redfiles, you will ch provides thated a single uld have prov

ure 32 - Exam

a new (FCate a Fabric a

On the VirtuEther the NeSelect Add P

Select the A

Select Apply

plink Sets with A

ciated Network

te: In this scenthe opposite F

dundant conne see how the he ability to cSUS and assi

vided an Activ

mple of an Activ

oE) SAN and name it ual Connect Metwork Name Port, then addEnclosure 1, Enclosure 1, dvanced SettiSelect Automay

Active/Active u

ks tab

nario we haveFlexFabric Moections out of NICs will conreate an Activgned both set

ve/Standby up

ve/Standby Sha

Fabric viaFCoE_A

Manager scree of FCoE_Ad the followingBay 1, Port XBay 1, Port X2ings atic Login Re-

uplinks and 80

e created two odules, by do the Virtual Co

nnect to VLANve / Active upts of these uplplink scenario

ard Uplink Set

a GUI

en, click Defin g ports; 1 2

Distribution

2.3ad (LACP) -

independent oing so we proonnect domai

Ns accessed thplink scenariolink ports to th

o, example be

ne, SAN Fabr

- Windows - Eth

t Share Uplinkovide the abilin. When wehrough the opo. Alternativehe same SUS,elow.

ic to create th

hernet and FCo

k Sets (SUS), eity to create

e create the seposite VC moly, we could h, however, thi

he first Fabric

oE 38

each

erver odule, have s

D

Scenario

Crea

Defining SThe Con#CrAddAdd Figu

o 2 Shared Up

ate a second On the VirtuEther the NeSelect Add P

Select the A

Select Apply

SAN Fabri following comnnect reate the SANd fabric FCoE_d fabric FCoE_

ure 33 - SAN

plink Sets with A

Fabric and naual Connect Metwork Name Port, then addEnclosure 1, Enclosure 1, dvanced SettiSelect Automay

ics via CLmmand(s) can

N Fabrics FCoE_A Bay=1 Po_B Bay=2 Por

N Login Distri

Active/Active u

ame it FCoE_Manager scree of FCoE_B d the followingBay 2, Port XBay 2, Port X2ings atic Login Re-

I n be copied a

E_A and FCorts=1,2 LinkDirts=1,2 LinkDis

ibution Setting

uplinks and 80

_B en, click Defin g ports; 1 2

Distribution

nd pasted into

E_B and confist=Auto st=Auto

g

2.3ad (LACP) -

ne, SAN Fabr

o an SSH bas

figure uplinks

- Windows - Eth

ic to create th

sed CLI sessio

as discussed

hernet and FCo

he second Fab

on with Virtual

above

oE 39

bric

l

D

Scenario

Figunum

Figuserv

Defining aWe wEach Prio

NotNICFCo

o 2 Shared Up

ure 34 FCombers on the ri

ure 35 FCovers powered

a Server Pwill create a seserver NIC wOn the mainCreate a serIn the NetwoIn the NetwoExpand the Do not confiIn the Assignthey apply

r to applying

te: you shouldCs 1&2 shouldoE_A and FCo

plink Sets with A

oE SAN fabriight

oE SAN Serveon)

rofile erver profile will connect to n menu, selectrver profile caork Port 1 droork Port 2 droFCoE Connecigure FC SANn Profile to Se

the profile, e

d now have ad be connecteoE_B.

Active/Active u

cs configured

er Connection

with two servea specific nett Define, thenalled App-1 op down box,op down box,ctions box, fo

N or iSCSI Coerver Bay box

nsure that the

a server profiled to networks

uplinks and 80

d with two 4G

ns (After serve

er NICs. twork. Server Profile select VLAN1 select VLAN1r Bay 1, selecnnection , locate the Se

server in Bay

e assigned to s VLAN101-1

2.3ad (LACP) -

Gb uplinks per

er profiles hav

e

101-1 101-2 ct FCoE_A for

elect Location

y 1 is currently

Bay 1, with 2 and VLAN10

- Windows - Eth

r fabric. Note

ve been create

r Bay 2, select

n drop down a

y OFF

2 Server NIC 01-2 and FCo

hernet and FCo

e the bay and

ed, assigned

t FCoE_B

and select Bay

connections. oE SAN fabric

oE 40

port

and

y 1,

cs

D

Scenario

Defining aThe Con

Figu

Notthe LOM

o 2 Shared Up

a Server P following comnnect

# Create Seadd profile Aset enet-connset enet-connset fcoe-conset fcoe-conpoweroff seassign profi

ure 36 - Defin

te: The speed FCoE connect

M:2-b.

plink Sets with A

rofile via mmand(s) can

erver Profile AApp-1 nection App-1nection App-1nection App-1nection App-1rver 1 le App-1 enc0

e a Server Prof

of the NIC antions are assig

Active/Active u

CLI n be copied a

App-1

1 1 pxe=Enab1 2 pxe=Disab1:1 Fabric=FC1:2 Fabric=FC

0:1

file (App-1)

nd SAN conngned to the tw

uplinks and 80

nd pasted into

bled Network=bled NetworkCoE_A SpeedCoE_B SpeedT

nections, as wwo SAN fabric

2.3ad (LACP) -

o an SSH bas

=VLAN101-1 k=VLAN101-2dType=4Gb Type=4Gb

well as the MAcs created ea

- Windows - Eth

sed CLI sessio

2

AC and WWNarlier and use

hernet and FCo

on with Virtual

N. Also, note ports LOM:1-

oE 41

l

that -b and

R

Scenario

Figu

Review

In thUplreduwe acti WeVLAthe presVLA AddSAN The

o 2 Shared Up

ure 37 - Serve

w his scenario winks originatinundant connehave also levve. We create

e created a seAN_101-2, whnetwork. VLAsented to the

AN, but taking

ditionally, FCoN Fabric FCo

FCoE SAN fa

plink Sets with A

er Profile View

we have createng from the eaections out of teraged LACP e two FCoE S

rver profile, which provides

AN101-1 and NIC(s) withou

g a different p

oE port 1 is coE_B, providin

abric connect

Active/Active u

Bay 1

ed Two Shareach FlexFabrithe Virtual Co to improved

SAN Fabrics.

with two NICs the ability to VLAN101-2 aut VLAN tags path out of the

onnected to Sg a multi-path

s to each SAN

uplinks and 80

ed Uplink Setsc Module con

onnect domainuplink perform

s connected to sustain a linkare configure(untagged), th

e enclosure.

AN fabric FChed connected

N fabric over

2.3ad (LACP) -

s (SUS), provinnect to each n. As multiplemance. In thi

o the same VLAk or module faed to support Vhese two NIC

CoE_A and FCd to the SAN.

a single uplin

- Windows - Eth

ding support SUS, by doine uplinks are us scenario, al

AN, VLAN_1ailure and not VLAN 101, fr

Cs are connect

CoE SAN port

nk per module

hernet and FCo

for 5 VLANs. ng so we provused for eachll uplinks will

01-1 and lose connectirames will be ted to the sam

t is connected

e.

oE 42

vide SUS, be

ion to me

d to

R

Scenario

Results We haveFCo

AlthG7 they

Figu3 Et

The YouNICwe serv

NotG6

Figu

o 2 Shared Up

Windo have successe created a se

oE connections

ough both Eth servers; eachy appear in th

ure 38 - Examhernet persona

following grau will also notiCs are currentdid not requir

ver would then

e: the BL465c and BL680c G

ure 39 - Wind

plink Sets with A

ows 200sfully configurerver profile tos created with

hernet and Fib capability (LAe server as in

mple of Emulex'alities and one F

aphics show aice that Windly configured re SAN connen have 8 NIC

c G7 and BL6G7 utilizes an

dows 2008 R2

Active/Active u

08 R2 Ned FlexFabrico connect to thin the profile

bre channel cAN and SANndividual netw

s OneManageFCoE personali

a Windows 2dows believes within FlexFaectivity on this

C ports availab

685c G7 utilizn NC553i chi

Network Conn

uplinks and 80

Networkc with a simplethe vNet with .

onnectivity is N) is provided work and SAN

er Utility (formerity per port, as

008 R2 serve there are 6 N

abric, the extras server, the Fble to the OS.

ze a NC551i ipset.

nections (2 Con

2.3ad (LACP) -

king Exae vNet and re TWO NICs a

provided by by a differen

N adapters.

rly known as H configured in t

er with TWO NICs within tha NICs are ofFCoE connecti.

chipset, wher

nnections Active

- Windows - Eth

amples edundant SANand the SAN

the CNA adat component o

BA Anywhere)the server profi

FlexNICs conhis server. Hoffline and couions could be

reas the BL46

e)

hernet and FCo

N fabrics. Wfabrics using

apter used theof the adapte

. Note that therle.

figured at 6Gowever, only Tuld be disable deleted and

60c G7, BL62

oE 43

We the

e in r,

re are

Gb. TWO d. If the

0c

Scenario

NotcancurrLOMadd

Figu

Figu

Not100200

o 2 Shared Up

te: The NICs t go into Netwrently in use. M:1 and threedresses to veri

ure 40 - Wind

ure 41 - Wind

e: In windows0MB incremen03 as a 2Gb N

plink Sets with A

that are not cowork Connecti Windows asse on LOM:2. fy which NIC

dows 2008 R2

dows 2008 R2

s 2003 the Nnts above 1GbNIC. Window

Active/Active u

onfigured withions for the Wsigns the NIC You may nee is which.

Extra Network

Network Conn

NIC speeds mab. IE: if a NICws 2008 doe

uplinks and 80

hin VC will apWindows 2008

s as NIC 1-6,ed to refer to t

Connections

nection Status

ay not be showC is configurees not have thi

2.3ad (LACP) -

ppear with a 8 server and , whereas threthe FlexFabric

Disabled

wn accuratelyed for 2.5Gb is limitation.

- Windows - Eth

red x as not cDisable any Nee of the NICc server profile

y when speed it will be disp

hernet and FCo

connected. YoNICs that are s will reside oe for the NIC

ds are configuplayed in Win

oE 44

ou not on MAC

red in ndows

Scenario

Figuconf

The concoulfail,modwas

Figu

o 2 Shared Up

ure 42 - Wifigured two o

following granected to the ld be teamed Virtual Conn

dule failure, ths the active N

ure 43 - Both N

plink Sets with A

ndows 2008 f the NICs an

aphics providenetwork, initia to provide Nect would fail

he servers NICIC, NIC team

NICs for Profile

Active/Active u

R2, Device Md two FCoE H

es an exampleally each NICIC fail-over rel-over to the stC teaming soing would fai

e App-1are con

uplinks and 80

Manager, SIX HBAs.

e of a WindoC has its own edundancy. tandby uplinkftware would l-over to the s

nected to the n

2.3ad (LACP) -

NICs are sho

ows 2008 R2 TCP/IP addreIf an active up

k. In the even see one of thstandby NIC.

network through

- Windows - Eth

own, however,

server with TWess, alternativeplink or netwot of a Virtual

he NICs go of

h vNet-PROD

hernet and FCo

, we have on

WO NICs ely, both NICork switch weConnect FlexFffline, assumin

oE 45

ly

Cs re to Fabric ng it

N

Scenario

NIC TeamIf hinetwteamquiteYou1 to

The andstanthe s

Figu

Figu

Variyou

Figu

o 2 Shared Up

ming gher availabi

work configuraming. In this ee simple. Ho will note the

o Bay 2 for ex

following gra connected to

ndby uplinks, standby NIC.

ure 44 Team

ure 45 - Both N

ious modes ca can select the

ure 46 - View

plink Sets with A

lity is desiredations. Simplexample, we wever, if mult BAY#-Port# ixample.

aphics provideo the network.if a VC FlexFa

m both NICs, us

NICs for Profile

an be configue team and ed

Network Co

Active/Active u

, NIC teamingy, open the Nhave only TWtiple NICs arendication with

e an example In the event abric module

sing the HP Net

e App-1are team

ured for NIC Tdit its properti

onnections NIC

uplinks and 80

g in Virtual CoNIC teaming UWO NICs avaie available, enhin each NIC.

e of a Window of an Uplink were to fail, t

twork Configur

med and conne

Teaming, suchies. Typically

C Team #1 W

2.3ad (LACP) -

onnect works Utility and conilable, so selensure that the. You would

ws 2008 R2 s or switch failthe NIC team

ration Utility

ected to the net

h as NFT, TLB y, the default s

Windows

- Windows - Eth

the same wanfigure the avecting NICs foe correct pair otypically TEA

server with TWure, VC will faing software w

twork through v

etc. Once thsettings can b

hernet and FCo

ay as in standavailable NICs or teaming wiof NICs is teaM a NIC from

WO NICs teamail-over to thewould fail-ove

vNet-PROD

he Team is crebe used.

oE 46

ard for ll be

amed. m Bay

med e er to

eated,

R

Scenario

Figu

Results Figu

o 2 Shared Up

ure 47 - Both

Windoure 48 - Durin

plink Sets with A

NICs are team

ows 200ng server boot,

Active/Active u

ed and connec

08 R2 Syou can see th

uplinks and 80

ct to the networ

SAN Coat Port 1 of the

2.3ad (LACP) -

rk with a comm

onnectivie FlexHBA is co

- Windows - Eth

on IP Address

ity onnected to an

hernet and FCo

MSA1000 SAN

oE 47

N LUN

S

Scenario

Figu

SummaWe SUSpath

WhconthroNICNICNICof n

Addto aIf adadju

As aprofserv

o 2 Shared Up

ure 49 - Wind

ary presented a V

S is connectedh SAN fabric

en VC profilenected througugh FlexFabri

Cs could now Cs. Either NICC or either upletwork bandw

ditional NICs c total of 6 NICdditional or leusted.

additional serfiles, configurever bays.

plink Sets with A

dows 2008 R2

Virtual Conned with TWO afor storage co

App-1 is appgh FlexFabric ic module 2 (cbe configured

C could be actink, dependinwidth and eac

could be addCs, the NIC s

ess SAN band

vers are addee the NICs fo

Active/Active u

Disk Administr

ect Network scactive uplinks, onnectivity.

plied to the semodule 1 (coconnected to d as individuative. As a resng on which Nch FCoE port

ed within Flexpeed can the

dwidth is requ

ed to the enclor vNet-PROD

uplinks and 80

ator. Note; tha

cenario by cre both SUS ca

erver in bay1 nnected to VVLAN_101-2

al NICs with thsult, this serveNIC is active ais configured

xFabric, by sin be adjustedired, the spee

osure, simply and the SAN

2.3ad (LACP) -

at D: is the SAN

eating two shan actively pa

and is powerVLAN_101-1). Each NIC iheir own IP ader could accesat the time. E for 4Gb of S

mply powerind accordingly ed of the SAN

create additio fabrics and a

- Windows - Eth

N attached volu

hared uplink sass traffic. We

red up, it has ), the second s configured ddress or as ass the networkEach NIC is coAN bandwid

ng the server o to suit the ne

N connection c

onal profiles, apply them to

hernet and FCo

ume

ets (SUS), eace included a d

one NIC NIC is conneat 6Gb. Thesa pair of TEAMk through eitheonfigured for th.

off and addineds of each Ncan also be

or copy existo the appropri

oE 48

ch dual

ected se MED er 6Gb

ng up NIC.

ting ate

Scenario 3 Shared Uplink Set with Active/Active Uplinks and 802.3ad (LACP) - Windows - Ethernet and FCoE Boot from SAN 49

Scenario 3 Shared Uplink Set with Active/Active Uplinks and 802.3ad (LACP) - Windows - Ethernet and FCoE Boot from SAN

Overview This scenario will implement the Shared Uplink Set (SUS) to provide support for multiple VLANs. In this scenario, the upstream network switches connect a shared uplink set to two ports on each FlexFabric modules, LACP will be used to aggregate those links. This scenario is identical to Scenario 2, however, scenario 3 also provides the steps to configure a windows 2008 R2 server to Boot to SAN using the FC0E connections provided by FlexFabric. When using Virtual Connect/FlexFabric in a Boot to SAN implementation, no custom or special HB

Cookbook

Documents

Transcript of Cookbook