Blade Servers - Cisco...Server virtualization and multi-core CPUs are driving more bandwidth from each server and out of the rack. Uplink cost Each Blade Switch needs at least one

© 2006 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialPresentation_ID 1

Blade Servers

July 2008


Key Requirements in Blade ServerEnvironments

Reduce the Proliferation of Blade Switches for Ethernetand Fibrechannel environments

More VMs per Blade Servers, means more need forbandwidth => Provide more uplink bandwidth capacity(less oversubscription)

Being able to swap blades with minimal changes to theEthernet configuration and minimal changes to the LUNmasking and Fibrechannel Zoning

Preserve Granularity of Zoning when using VMWARErunning on top of Blade Servers


Agenda

Problem Statement

Cisco Solution for LAN

Cisco Solution for SAN

Cisco Solution to Server Mobility


Cisco Solution forCable Reduction andmanageability

Catalyst Blade SwitchCBS3120 for LAN


Feedback from Ethernet Blade Server Customers

Switch Proliferation

Increases Network Complexity - Larger L2 and L3 domains where convergenceand stability are concerns

Increases operational Management Headaches

Growing Bandwidth needs

Server virtualization and multi-core CPUs are driving more bandwidth fromeach server and out of the rack.

Uplink cost

Each Blade Switch needs at least one 10GE Uplink or multiple GE Uplinks

Feature Consistency with DC Catalyst Products

2 switches per row

2 switches per rack

8 switches per rack

Ethernet Data Center access architectures


Introducing Cisco Virtual Blade Switch (VBS)Overview of Concept and Benefits

Management Simplification– Operational simplification

• Single switch per rack to manage

• True Plug-n-Play of switches

– Design Simplification:

• Sharing Uplinks helps reduce cables

• Reduction in # of logical nodes in L2/L3 network helpsimprove network convergence

– Operational Consistency

• Familiar IOS CLI, MIBs and management tools likeCiscoWorks

• Consistent End-to-end features and functionality

Performance & Scalability

– Up to 160G configurable bandwidth out of rack

– Rack switch allows server to double bandwidth with noadditional cost

Reduce CAPEX– Mix-n-match of GE & 10G uplink switches

– Sharing of uplinks reduces overall network infrastructurecost

Virtual BladeSwitch

TraditionalBlade Switch


Cisco Catalyst BladeSwitch 3120 for HPProduct Overview

2x10GE X2uplinks

10G Virtual Blade Switch (CBS3120X)

GE Virtual Blade Switch (CBS3120G)

4xRJ45ports

Up to 4 SFP 4xRJ45ports

Key Customer Value Prop

Management Simplification– Operational simplification

• Single switch per rack

• True Plug-n-Play of switches

– Design Simplification:

• Share Uplinks to reduce cables

• Reduce # of nodes for L2/L3

– Operational Consistency

• Familiar IOS CLI, MIBs and tools

• Consistent End-to-end features

Performance & Scalability

– Up to 160G bandwidth out of rack

– Double bandwidth from each server

Reduce CAPEX– Mix-n-match of GE & 10G switches

– Share uplinks to reduce overall cost


With VSL on Cat 6K,all links utilized

Topology showing Benefits of Cisco NG Rack Switch

Distribution Layer

GreaterServer BW –via Active-

Active ServerConnectivity

HigherResiliency

withEtherchannel

Local Traffic doesn’t go todistribution switch

Mix-n-match GE & 10GEswitches

Single Switch / Node (forSpanning Tree or Layer 3)

AccessLayer


“Multiple Deployment Options for Customers”Caters to Different Customer Needs

Common Scenario

Single VirtualBlade switch

Cost Effective

Separate Rings

Separate VBS

More resilient

4 NIC server Scenario

More Server Bandwidth– VMware

Creates smaller Rings


Too many switches?Solution: 3 switches to manage

Cisco director-class -- 336 downlinks

336 servers

1 switch to manage

Cisco 3120 -- 16 downlinks

(336/16)/8

4 switches to manage for the same

number of downlinks!


Cisco Network Assistant (CNA 5.0) on EthernetBlade Switch

Benefit:Manage multiple bladeswitches easily

Cost:Free Tool

What:• Mgmt Tool to allow InteractiveConfiguration, Topology/FrontPanel View, Monitoring,Troubleshooting and NetworkMaintenance• Supports up to 40 switches• Examples:

• Apply multiple port configs onmultiple switches• Health Monitoring• OS upgrades


Agenda

Problem Statement





Domain ID scalability:

Catalyst Blade Switch9124e for SAN


Domain ID ScalabilityCisco Solution

F-Port

MDS Switch orNon-Cisco Switch

NPIV enabled

Server 1

Server 2

Server N

FC BladeSwitch 1…

…

FC BladeSwitch 2…

N-Ports

Blade Chassis

F-Ports

…

…

NP ports

SAN

Fabric

F-Ports

F-Port

Eliminates Domain ID for MDS FC switch in BladeCenter – HBA model.

Server ports automatically assigned to NP ports (load balancingalgorithm).

Need to configure the same VSAN between NP ports and core F-ports

In SANOS 3.2 one VSAN per uplink. When F-trunking will be availablethe limitation will go away.


N-Port ID Virtualization (NPIV)

Mechanism to assign multiple N_Port_IDs to a single N_Port

Allows all the Access control, Zoning, Port Security (PSM)be implemented on application level

Multiple N_Port_IDs are allocated in the same VSAN

Support for NESTED NPIV

Application Server FC Switch

Email

Web

File Services

Email I/O

N_Port_ID 1

Web I/O

N_Port_ID 2

File Services I/O

N_Port_ID 3

F_Port


Agenda

Problem Statement





Cisco Solutions forServer Mobility


SANOS 3.2(2): Flex AttachFlexAttach Port (virtual PWWN)

– Creation of virtual PWWN on NPV switch F-port

– Zone vPWWN to storage

– LUN masking is done on vPWWN

– Can swap Blade Server or replace physical HBA (equivalent to HP VC)

• No need for zoning modification

• No LUN masking change required

– Automatic link to new PWWN

• Unlike SDV, which is manual re-linking to new PWWN

FC1/1

PW

WN

1

Server 1

vPWWN1 FC1/1

PW

WN

2Server 1

vPWWN1

Before After


Cisco VFrame Data Center Support

Cisco VFrame Data CenterNetwork-Driven Service Orchestration

SOI ControlLayer

Storage Pool

SANNAS

Server Pool Network Pool

Data Center Networked Infrastructure

MonitoringIBM Tivoli, HP Openview,

BMC Patrol, CA Unicenter

Business ServiceManagement

Mercury,Tideway, BMC

Management and Monitoring

Element ManagersCisco Fabric Manager, VMS,

CiscoWorks, ANM

Virtualization

ManagersVMware VirtualCenter

Orchestrate acrossinfrastructure resources

Platform for serviceabstraction

Integrate with othermanagement systems

VFrame DC 1.2 (Q1CY08) supports Ethernet/FC Blade Switches


Server Virtualization

July 2008


Virtualization

CPU

mem

ory

Mofied Stripped Down OS with

Hypervisor

Guest OS

App

VM

CPU

mem

ory

Host OS

VM

Hypervisor

VMware Microsoft

CPU

mem

ory

Modified OS

App

VM

Mofied Stripped Down OS with

Hypervisor

XEN akaParavirtualization

Guest OS

App

Guest OS

App

Guest OS

App

Modified OS

App


VMware Virtualization Layer

Migration

VMotion, aka VM Migration allows aVM to be reallocated on a differentHardware without having tointerrupt service.

Downtime in the order of fewmilliseconds to few minutes,not hours or days

Can be used to performMaintenance on a server,

Can be used to shift workloadsmore efficiently

2 types of Migration:

VMotion Migration

Regular Migration

VMware Virtualization LayerOS OS C

on

so

leO

S

OS

App. App. App.

CPUm

emory

CPUm

emory

Co

ns

ole

OS

Hypervisor Hypervisor


VMware Architecture in a Nutshell

ESX Server Host

VirtualMachines

…

ProductionNetwork

MgmtNetwork

VM KernelNetwork

OS OS OS

ConsoleOS

App. App. App.

VM Virtualization Layer

Physical Hardware

CPU

mem

ory


VMware HA Clustering

CPU

mem

ory

ESX Host 2

Hypervisor

CPU

mem

ory

ESX Host 1

Hypervisor

Guest OS

App1

Guest OS

App2

CPU

mem

ory

ESX Host 3

Hypervisor

Guest OS

App3

Guest OS

App4

Guest OS

App5Guest OS

App1

Guest OS

App2


Application-level HA clustering(Provided by MSCS, Veritas etc…)

CPU

mem

ory

ESX Host 2

Hypervisor

CPU

mem

ory

ESX Host 1

Hypervisor

Guest OS

App1

Guest OS

App2

CPU

mem

ory

ESX Host 3

Hypervisor

Guest OS

App3

Guest OS

App4

Guest OS

App5

Guest OS

App1

Guest OS

App2


Agenda

VMware Networking

vSwitch Basics

NIC Teaming

vSwitch vs LAN Switch

Cisco/VMware DC DESIGNS

SAN Designs


VMware Networking ComponentsPer ESX-server configuration

VMNICS = uplinksvSwitchVMs

vmnic0

vmnic1

vNIC

vNIC

Virtual Ports

VM_LUN_0007

VM_LUN_0005

vSwitch0


vNIC MAC Address

VM’s MAC addressautomatically generated

Mechanisms to avoid MACcollision

VM’s MAC address doesn’tchange with migration

VM’s MAC addresses can bemade static by modifying theconfiguration files

ethernetN.address =00:50:56:XX:YY:ZZ

/vmfs/volumes/46b9d79a-2de6e23e-929d-001b78bb5a2c/VM_LUN_0005/VM_LUN_0005.vmx

ethernet0.addressType = "vpx"

ethernet0.generatedAddress ="00:50:56:b0:5f:24„

ethernet0.addressType =„static“

ethernet0.address ="00:50:56:00:00:06„


vSwitch Forwarding Characteristics

Forwarding based on MAC address (No Learning):If traffic doesn’t match a VM MAC is sent out to vmnic

VM-to-VM traffic stays local

Vswitches TAG traffic with 802.1q VLAN ID

vSwitches are 802.1q Capable

vSwitches can create Etherchannels


vSwitch Creation

YOU DON’T HAVE TO SELECT A NIC

This is just a name

vswitch

Select the Port-Group by specifying theNETWORK LABEL

vNICs


VM Port-Group vSwitch


VLAN’s - External Switch Tagging - EST

PhysicalSwitches

VLAN tagging andstripping is done by thephysical switch

No ESX configurationrequired as the server isnot tagging

The number of VLAN’ssupported is limited tothe number of physicalNIC’s in the server

VM1 VM2ServiceConsole

VMkernel

VMkernelNIC

VSwitch AVSwitch B ESX

Server

Virtual NIC’s

VLAN 100 VLAN 200

Physical NIC’s


VLAN’s - Virtual Switch Tagging - VST

PhysicalSwitches

The vSwitch tagsoutgooing frames withthe VLAN Id

The vSwitch strips anydot1Q tags beforedelivering to the VM

Physical NIC’s andswitch port operate as atrunk

Number of VLAN’s arelimited to the number ofvNIC’s

No VTP or DTP. Allstatic config. PruneVLAN’s so ESX doesn’tprocess broadcasts


VMkernel

VMkernelNIC

VSwitch AESXServer

Virtual NIC’s

VLAN 100 VLAN 200

Physical NIC’sdot1Q


VLAN’s - Virtual Guest Tagging - VGT

PhysicalSwitches

Portgroup VLAN Id setto 4095

Tagging and stripping ofVLAN id’s happens inthe guest VM – requiresan 802.1Q driver

Guest can send/receiveany tagged VLAN frame

Number of VLAN’s perguest are not limited tothe number of VNIC’s

VMware does not shipwith the driver:Windows E1000Linux dot1q module


VMkernel

VMkernelNIC VSwitch A ESX

Server

Virtual NIC’s

VLAN 100 VLAN 200

Physical NIC’sdot1Q

dot1QVM applied


Agenda

VMware Networking

vSwitch Basics

NIC Teaming



SAN Designs


Meaning of NIC Teaming in VMware (1)

ESX Server Host

vSwitch Uplinks

vmnic0 vmnic1 vmnic2 vmnic3

vNIC vNICvNIC

vNIC

vNIC

ESX server NIC cards

NIC Teaming NIC Teaming

THIS IS NOT NIC Teaming


Meaning of NIC Teaming in VMware (2)T

his

is

NO

T T

ea

min

g

Teaming is Configured at The vmnic Level


vSwitch0

VM1

vmnic0 vmnic1

Service ConsoleVM2

Port-Group 1

VLAN 2

Port-Group 2

VLAN 1

802.1q

Vlan 1,2

802.1q

Vlan 1,2

ESX Server

Design Example2 NICs, VLAN 1 and 2, Active/Standby


Active/Standby per-Port-Group

VM5

VMNIC0

VM7 VM4 VM6

VMNIC1

.5 .7 .4 .6

CBS-rightCBS-left

Port-Group2Port-Group1

ESX Server

vSwitch0


Port-Group Overrides vSwitch GlobalConfiguration


Active/Active

vmnic0 vmnic1

ESX server NIC cards

vSwitch

ESX server

VM1 VM2 VM3 VM4 VM5

Port-Group


Active/ActiveIP-Based Load Balancing

Works with Channel-Groupmode ON

LACP is not supported(see below):

9w0d: %LINK-3-UPDOWN: InterfaceGigabitEthernet1/0/14, changed stateto up

9w0d: %LINK-3-UPDOWN: InterfaceGigabitEthernet1/0/13, changed stateto up

9w0d: %EC-5-L3DONTBNDL2:Gi1/0/14 suspended: LACP currentlynot enabled on the remote port.

9w0d: %EC-5-L3DONTBNDL2:Gi1/0/13 suspended: LACP currentlynot enabled on the remote port.

vmnic0 vmnic1

vSwitch

ESX server

VM1 VM2 VM3 VM4

Port-Group

Port-channeling


Agenda

VMware Networking

vSwitch Basics

NIC Teaming



SAN Designs


All Links Active, No Spanning-TreeIs There a Loop?

VM5

NIC1 NIC2

VM7 VM4 VM6

vSwitch1

NIC3 NIC4

.5 .7 .4 .6

CBS-rightCBS-left

Port-Group2

Port-Group1

ESX Server


Broadcast/Multicast/Unknown UnicastForwarding in Active/Active (1)

vSwitch0

VM1

vmnic0 vmnic1

VM2

Port-Group 1

VLAN 2

802.1q

Vlan 1,2

802.1q

Vlan 1,2

ESX Server


Broadcast/Multicast/Unknown UnicastForwarding in Active/Active (2)

vSwitch

VM1

NIC1 NIC2

VM2

ESX Host

802.1q

Vlan 1,2

802.1q

Vlan 1,2

VM3


Can the vSwitch Pass Traffic Through?

vSwitch

VM1

NIC1 NIC2

VM2

E.g. HSRP?


Is This Design Possible?

vSwitch

VM5 VM7

802.1q

802.1q

.5 .7

ESX server1

VMNIC1 VMNIC2

12

Catalyst1 Catalyst2


vSwitch Security

Promiscuous mode Rejectprevents a port fromcapturing traffic whoseaddress is not the VM’saddress

MAC Address Change,prevents the VM frommodifying the vNICaddress

Forget Transmits preventsthe VM from sending outtraffic with a different MAC(e.g NLB)



Similarly to a LAN Switch:

Forwarding based on MACaddress

Vswitches TAG traffic with802.1q VLAN ID

vSwitches are 802.1q Capable

vSwitches can createEtherchannels

Preemption Configuration(similar to Flexlinks, but nodelay preemption)

Differently from a LAN Switch

No Learning

No Spanning-Tree protocol

No Dynamic trunk negotiation(DTP)

No 802.3ad LACP

2 Etherchannel backing up eachother is not possible

No SPAN/mirroring capabilities:Port Security different


Agenda

VMware Networking

vSwitch Basics

NIC Teaming



SAN Designs


vSwitch and NIC Teaming Best Practices

Q: Should I use multiple vSwitches ormultiple Port-Groups to isolate traffic?

A: We didn’t see any advantage in usingmultiple vSwitches, multiple Port-Groupswith different VLANs give you enoughflexibility to isolate servers

Q: Should I use EST or VST?

A: Always use VST, i.e. assign the VLANfrom the vSwitch

Q: Can I use native VLAN for VMs?

A: Yes you can, but to make it simple don’t.If you do, do not TAG VMs with the nativeVLAN

Q: Which NIC Teaming configuration shouldI use?

A: Active/Active, Virtual Port-ID based

Q: Do I have to attach all NICs in the teamto the same switch or to differentswitches?

A: with Active/Active Virtual Port-ID based, itdoesn’t matter

Q: Should I use Rolling Failover (i.e. nopreemption)

A: No, default is good, just enabletrunkfast on the Cisco switch


Cisco Switchport Configuration

Make it a Trunk

Enable Trunkfast

Can the Native VLAN be used forVMs?

Yes, but IF you do, you have 2options

Configure VLAN ID = 0 for the VMsthat are going to use the native VLAN(preferred)

Configure “vlan dot1q tag native” onthe 6k (not recommended)

Do not enable Port Security(see next slide)

Make sure that “teamed” NICs are inthe same Layer 2 domain

Provide a Redundant Layer 2 path

interface GigabitEthernetX/X

description <<** VM Port **>>

no ip address

switchport

switchport trunk encapsulation dot1q

switchport trunk native vlan <id>

switchport trunk allowed vlan xx,yy-zz

switchport mode trunk

switchport nonegotiate

no cdp enable

spanning-tree portfast trunk

!

Typically: SC, VMKernel, VM Production


Configuration with 2 NICSuboptimal Configuration

Trunks

VM1

VMNIC1 VMNIC2

VM2

802.1q: Production VLANs,

Service Console, VM Kernel 802.1q

Service

Console VM Kernel

ESX Server

vSwitch 0

Port-Group

2

Port-Group

3Port-Group

1

HBA1 HBA2

NIC teamingActive/Active

VST

Global Active/Active

Active/StandbyVmnic1/vmnic2



Configuration with 2 NICsRecommended Configuration

Trunks

VM1

VMNIC1 VMNIC2

VM2

802.1q: Production VLANs,

Service Console, VM Kernel 802.1q

Service

Console VM Kernel

ESX Server

vSwitch 0

Port-Group

2

Port-Group

3Port-Group

1

HBA1 HBA2

NIC teamingActive/Active

VST

Global Active/StandbyVmnic1/vmnic2




Network Attachment (1)

802.1q

802.1q:

Production,

SC, VMKernel

ESX server1 ESX server 2

VMNIC1 VMNIC2

12 3

4

Catalyst1 Catalyst2

VMNIC1 VMNIC2

No Blocked Port,No Loop

All NICs are usedTraffic distributed

On all links

802.1q:

Production,

SC, VMKernel

root

Secondaryroot

TrunkfastBPDU guard

vSwitch vSwitch

Rapid PVST+



802.1q

802.1q:

Production,

SC, VMKernel


VMNIC1 VMNIC2

12 3

4

VMNIC1 VMNIC2

All NICs are usedTraffic distributed

On all links

Typical Spanning-TreeV-Shape Topology

802.1q:

Production, SC, VMKernelroot

Secondaryroot

TrunkfastBPDU guard

vSwitchvSwitch

Rapid PVST+


Configuration with 4 NICsSuboptimal Configuration

ESX Server

HBA1 HBA2

vswitch

Port-Group 1Service

Console VM Kernel

ProductionVLANs

Active/ActiveVmnic1/vmnic2

VMNIC4

VMNIC3VMNIC2VMNIC1


Configuration with 4 NICsRecommended Configuration

ESX Server

HBA1 HBA2

vswitch

Port-Group 1Service

Console VM Kernel

ProductionVLANs

SC, VMKernelVLANs



Active/ActiveVmnic1/vmnic3

VMNIC4

VMNIC3VMNIC2VMNIC1



vSwitch

802.1q:

Production


1 2 7

Catalyst1 Catalyst2

vSwitch

No Blocked Port,No Loop

802.1q:

Production,

SC, VMKernel

root

Secondaryroot

TrunkfastBPDU guard

802.1q:

SC and VMKernel

3

4 5

68

Rapid PVST+




802.1q:


Secondaryroot

TrunkfastBPDU guard

vSwitch

802.1q:

Production


1 27

Catalyst1 Catalyst2

vSwitch

802.1q:

SC and VMKernel

34 5

6 8

Rapid PVST+


How About?


802.1q:


Secondaryroot

TrunkfastBPDU guard

vSwitch

802.1q:

Production


1 27

Catalyst1 Catalyst2

vSwitch

802.1q:

SC and VMKernel

34 5

6 8


4 NICs with Etherchannel

802.1q:

Production


1

273

4 5

6 8

“Clustered” switches

802.1q:

SC, VMKernel

vSwitch vSwitch


VMotion Migration Requirements


VMKernel Network can be routed

ESX Server Host

VirtualMachines

…

ProductionNetwork

MgmtNetwork

VM KernelNetwork

VM KernelNetwork


VMotion L2 Design

VM4 VM5ESX Host 2 VM6

vSwitch0

vmnic0 vmnic1

vSwitch1 vSwitch2

vmnic2 vmnic3

vmkernel Serviceconsole

Rack10Rack1

ESX Host 1

vSwitch0

vmnic0

vSwitch2

vmnic2

vmkernel


HA clustering (1)

HA Agent runs in every host

Heartbeats Unicast UDP port~8042 (4 UDP ports opened)

Hearbeats run on the ServiceConsole ONLY

When a Failure Occurs, the ESXHost pings the gateway (on theSERVICE CONSOLE ONLY) toverify Network Connectivity

If ESX Host is isolated, it shutsdown the VMs thus releaseinglocks on the SAN

Recommendations:

Have 2 Service Console onredundant paths

Avoid losing SAN access (e.g. viaiSCSI)

Make sure you know before handif DRS is activated too!

Caveats:

Losing Production VLANconnectivity only, ISOLATESVMs (there’s no equivalent ofuplink tracking on the vswitch)

Solution:

NIC TEAMING


HA clustering (2)

COS 10.0.2.0

ESX2 Server Host

vmnic0

10.0.200.0

ESX1 Server Host

vmnic0

Prod 10.0.100.0

VM1 VM2

VM1 VM2

iSCSI access/VMkernel


Agenda

VMware Networking

vSwitch Basics

NIC Teaming



SAN Designs


VMware ESX Storage Options

80%+ of install baseuses FC storage

iSCSI is popular in SMBmarket

DAS is not popularbecause it prohibitsVMotion

SCSIFC

VM VM

FC

iSCSI/NFS

VM VM

DAS

VM VM

FC


Storage

Servers

ESX Server

ESX Server

ESX Server

ESX Server

Virtual Machines

A.vmdk

VMFS VMFS VMFSVMFS

VMFS

Stores the entire virtual machinestate in a central location

Supports heterogeneous storagearrays

Adds more storage to a VMFSvolume dynamically

Allows multiple ESX Servers toaccess the same virtual machinestorage concurrently

Enable virtualization-baseddistributed infrastructure servicessuch as VMotion, DRS, HA

VMFS Is High Performance Cluster File Systemfor Virtual Machines


Raw Device Mapping

RDM allows directread/write accessto disk

Block mapping is stillmaintained within aVMFS file

Rarely used butimportant for clustering(MSCS supported)

Used with NPIVenvironments

FC

VM1 VM2

FC

RDM

VMFS

Mapping

FC


FC

Storage Array

(LUN Mapping and Masking)MDS9000

Zone FC Name Server

pWWN-P

Single Login on a Single Point-to-Point Connection

Virtual Servers Share a Physical HBAA zone includes the physical hba andthe storage array

Access control is demanded to storagearray “LUN masking and mapping”, it isbased on the physical HBA pWWN andit is the same for all VMs

The hypervisor is in charge of themapping, errors may be disastrous

HW

Hyp

erv

iso

r

Vir

tua

l

Serv

ers

pWWN-P

Mapping

FC


NPIV Usage Examples‘Intelligent Pass-thru’Virtual Machine Aggregation

FC FC FC FC

NP_Port

F_PortF_Port

FC FC FC FC

FC

NPIV enabled HBA

Switch becomes an HBAconcentrator


Using Virtual Servers in Blade Chassiswith NPIV Proxy Switch

The individual blade servercan use NPIV to providethe virtual servers withvirtual HBAs

Disk Array

12 LUNs

Individually Mapped

NPIV (12 Virtual N Ports)

3 V

irtu

al N

Po

rt

3 V

irtu

al N

Po

rt

3 V

irtu

al N

Po

rt

3 V

irtu

al N

Po

rt

VM

04

VM

05

VM

06

VM

07

VM

08

VM

09

VM

10

VM

11

VM

12

FC FC FC FC

VM

01

VM

02

VM

03

Bla

de

Serv

ers

MDS9000

FCNPIV Proxy Switch Module

VM 1-12


VM creationincludes portcreation

VMwarecreates aunique node

Four ports formultipathingacross 4HBAs


Fabric Zoning For VMs Using Virtual HBA

1. All physical HBAs andarray ports must be in thesame zone

Physical Zone

2. Create a unique zone foreach VM that has a unique

Vport and array port

VM1 Zone

VM2 Zone

VM3 Zone

Zoning and VMotion:

No zone reconfiguration isrequired since the Vportaddress follows the VMduring migration


Unified I/O ( FCoE):Fewer HBA/NIC’s per Server

CNA

CNA

FC HBA

FC HBA

NIC

NIC

SAN (FC)

SAN (FC)

LAN (Ethernet)

LAN (Ethernet)

SAN (FCoE)

LAN (Ethernet)

CNA = Converged Network Adapter


N_Port Virtualizer

Nexus5000

F_Port F_Port F_Port

NP_PortNP_Port

N_Port Virtualizer in detail

NPIV Proxy captures alllogin associated packetsfrom the HBA and BorderInterfaces (BI)

Hosts pinned toBorder Interfaces

Support NPIV over ServerInterfaces (SI)

Relies on NPIV onBorder interfaces

Retry failed login requestsfrom one Border Interfaceon a different interface

SISI SI

N_Port Virtualizer

Mode

BI BI

MDS #1 MDS #2

HBA #1 (NPIV)

HBA #2(NPIV)

HBA #3


Cisco VFrame Data Center Support

Cisco VFrame Data CenterNetwork-Driven Service Orchestration

SOI ControlLayer

Storage Pool

SANNAS

Server Pool Network Pool

Data Center Networked Infrastructure

MonitoringIBM Tivoli, HP Openview,

BMC Patrol, CA Unicenter

Business ServiceManagement

Mercury,Tideway, BMC

Management and Monitoring

Element ManagersCisco Fabric Manager, VMS,

CiscoWorks, ANM

Virtualization

ManagersVMware VirtualCenter

Orchestrate acrossinfrastructure resources

Platform for serviceabstraction

Integrate with othermanagement systems


Documents

Blade Servers - Cisco...Server virtualization and multi-core CPUs are driving more bandwidth from each server and out of the rack. Uplink cost Each Blade Switch needs at least one