unified fabric - ciscosimplified management with scale architectural flexibility active-active...

Unified Fabric Maurizio Portolani

• Introduction

• Spanning Tree and vPC

• Fabric Extender

• vPC and FEX design best practice

• FabricPath

Scale-up and Scale-out a Key Requirement

TOP CAREABOUTS IMPACT FABRIC

General Purpose

High Frequency Trading

and High Performance

Computing

Cloud and Service Provider

Web 2.0 and Big Data

• Large Scale L2/L3 Fabric

• Multi-tenancy

• Simplified Management

• Security

• Convergence

• L2/L3 Fabric Scale

• Operational Continuity

• Simplified Management

• Server Virtualization

• Convergence

• Multicast at Scale

• Low Latency

• East/West traffic

• L3 Fabric at Scale (10,000+)

• Open API

• Auto Provisioning and Monitoring

Need For Architectural Flexibility

CONVERGENCE

INTELLIGENCE

Foundational Technologies

DCB/FCoE

Architecture

FabricPath

Consolidated I/O

Virtualizes the Switch

Simplified Management

with Scale

Architectural Flexibility

Active-Active Uplinks

Workload Mobility

Scalability and Mobility

Deployment Flexibility Unified Ports

IO Accelerator Replication and Back up

SME/DMM Compliance and Workload Mobility

• Wire once and walk away

• Lower complexity

• Does not disrupt existing Infrastructure

• Eliminate parallel networks – no stranded assets, less space, less heat, less cooling

• Simpler cabling – easier installation, better airflow

• Interoperates with existing LAN and SAN

Virtualising the Network Port

LAN LAN

Switch port extended over

Fabric Extender

Switch

Legacy multi-tier architecture FEX architecture

Switch

Collapse network tiers, fewer network management points

Where Is the Edge?

PCI-E Bus

Operating System and

Device Drivers

FC 3/11

Edge of the Network and Fabric

Eth 2/12

PCI-E Bus

Hypervisor provides virtualization of PCI-E

resources

FC 3/11

Eth 2/12

Edge of the

Fabric

Still 2 PCI Addresses

on the BUS

PCI-E Bus

Hypervisor provides virtualization of PCI-

E resources

Edge of the

Fabric

Eth 2/12

Converged Network Adapter provides

virtualization of the

physical Media

PCI-E Bus

Hypervisor provides

virtualization of PCI-E resources

Edge of the Fabric

veth 1

802.1BR

vFC 126

SR-IOV adapter

provides multiple

PCIe resources

Compute and Fabric Edge are Merging

Some classic Layer 2 Limitations

• Local problems have network-wide impact, troubleshooting is difficult

• Tree topology provides limited bandwidth

• Tree topology introduces sub-optimal paths

• Each Network device is another management point

STP convergence is disruptive

MAC address tables don’t scale

Host flooding impacts the whole network

Fabric simplification

With FabricPath:

• Traffic is routed inside the fabric local problems have local impact

• L2 can be extended without risk

FabricPath

VLAN X

VLAN Y

VLAN Z

Larger Distributed Topologies

Server, Storage, Application and Facilities are driving Layer 2 Scalability requirements

Server Virtualization and Clustering driving the need for every / any VLAN everywhere based design

Facilities requirements defining the network topology

• VM requirements along with Data Storage growth mandating a need for more efficient and pervasive network based storage

Technology changes will impact any cabling plant design

Migration to 10GE as the default LoM technology

L2 Domain Elasticity: vPC, FabricPath/TRILL

OTV LAN extensions

Device Virtualization: VDCs,

VRF enhancements

MPLS VPN

Location of compute resources is transparent to the user

VN-link

notifications

VM-awareness: VN-link

Port Profiles

IP Mobility: LISP

Multi-tenancy/segmentation: Segment-ID, VXLAN, FabricPath and OTV

Virtualized Workload Mobility Connecting Virtualized Data Centers

Evolution of Enterprise Environments

L3 Cloud

From STP ----------------------------------------------- to FabricPath

From 2-way redundancy ----------------------------- to N-way redundancy

From Limited L2 paths ------------------------------- to L2 ECMP

From Classic learning --------------------------------- to conversational learning

From rigid topologies --------------------------------- to highly flexible topologies

From hard pod boundaries -------------------------- to segment overlay extensions

From disparate fabrics ------------------------------- to converged fabric

From virtualization unaware fabric ----------------- to virtualization aware fabric

Evolution of SPDC Environments

From Restricted VLAN/L2 Scale ----------- to highly scalable VLAN/MAC Space

From Classic L4-7 Scale/Mobility ---------- Physical/Virtual Scale and Service Mobility

From VLAN-Based Multi-tenancy ---------- Tenant ID Based environments

From GE nodes ------------------------------ to 10G nodes pushing 40G uplink adoption

From limited Hypervisors offerings ------- “open” primarily and other as needed

From Stitch-together Orchestration ------ Integrated Process Flow Driven Orchestration

L3 Cloud

L3 L3 Cloud

• Introduction

• Fabric Extender

• FabricPath

! Enable vpc on the switch

dc11-5020-1(config)# feature vpc

! Check the feature status

dc11-5020-1(config)# show feature | include vpc

vpc 1 enabled

• vPC allows a single device to use a port channel across two neighbour switches (vPC peers)

• Eliminate STP blocked ports

• Layer 2 port channel only

• Provide fast convergence upon link/device failure

• Available on Nexus 3000, 5000/5500 and 7000*

Virtual Port Channel - vPC Multi-chassis Etherchannel (MCEC)

vPC Peers

Aggregati

Access

Core FC

LAN and SAN utilize different High Availability Models

SAN is dual fabric, LAN is fully meshed fabric

vPC enables ‘both’ architectures at the edge (single device models not acceptable to SAN customers)

Why vPC and not VSS or Stackwise Co-existence of LAN and SAN

• Do not disable STP !!

• Configure aggregation vPC peers as root and secondary root

If vPC peer-switch is implemented, both vPC peers will behave a single STP root

• Align STP primary root, HSRP active router and PIM DR with vPC primary peer

• BA is enabled by default on vPC peer-link

• Do not enable Loopguard and BA on vPC (disabled by default)

• Enable STP port type “edge” and port type “edge trunk” on host ports

• Enable STP BPDU-guard globally

• Disable STP channel-misconfig guard if supported by access switches

Spanning Tree Recommendations STP Best Practices

BPDU-guard BPDU-guard

Port Type

Edge / Edge Trunk

routing peer agg1b agg1a

Acc1 Acc2

Disable STP channel-

misconfig guard

vPC primary

VLAN 1-4094 root

MST 0 – 3 root

HSRP Active

PIM DR

vPC primary STP

VLAN 1-4094 sec root

MST 0 – 3 sec root

HSRP Standby

vPC_PL

vPC_PKL

vPC maintains layer 2 synchronization between peers ‘not’ Layer 3

Don’t use L2 port channel to attach routers to a vPC domain

If both routed and bridged traffic is required:

Individual L3 links for routed traffic

L2 port-channel (vPC) for bridged traffic

vPC Interaction with Layer 3 Do not create an L3 peer over a vPC interface

ECMP LInks

• HSRP active process communicates the active MAC to its neighbour

• Only the HSRP active process responds to ARP requests

• HSRP active MAC is populated into the L3 hardware forwarding tables, creating a local forwarding capability on the HSRP standby device

• No need to configure aggressive FHRP hello timers as both switches are active

‘peer-gateway’ command allows a vPC peer to respond both the the HSRP virtual and the real MAC address of both itself and it’s peer

dca-n7k1-vdc2(config-vpc-domain)# peer-gateway

------:: Disable IP redirects on all interface-vlans of this vPC domain

for correct operation of this feature ::------

vPC Interaction with Layer 3 FHRP

N5k(config-vpc-domain)# delay restore ?

<1-3600> Delay in bringing up vPC links (in seconds)

N5k(config-vpc-domain)# delay restore 360 Delay activating vPC interfaces

vPC interaction with Routing convergence on system restart

After a vPC device reloads and comes back up routing protocol needs time to reconverge

vPCs may blackhole routed traffic from access to core until layer 3 connectivity is reestablished

vPC Delay Restore

On system restart delays bringing up the vPC interfaces for ‘n’ seconds

Like HSRP preempt delay it needs to be tuned for your network

vPC and Layer 3 InteractionsvPC Delay Restore

Primary

Secondary

HSRP Active

HSRP Standby

RMAC-A RMAC-B

N5k-1 N5k-2

Some devices, such as NetApp filer, could send packets to interface MAC rather than the virtual MAC of FHRP protocol

Such packets will be forwarded over peer-link

The “peer-gateway” will address this issue

L3-N5548-1(config-vpc-domain)# peer-gateway

vPC and Layer 3 InteractionsPeer-Gateway

Parent Switch vPC Peer-link (10 GE Only) VPC Interfaces

N7K-M132XP-12

✓ ✓

N7K-M132XP-12L

✓ ✓

N7K-M108X2-12L

✓ ✓

N7K-F132XP-15

✓ ✓

F2 – 48 x 10G

✓ ✓

M2 40G & 100G

Future Future

For Your Reference

vPC Supported Hardware Nexus 7000

vPC Supported Hardware VDC Combinations with F1/F2/M1 Module

Mix VDC

M1-F1-F2

Mix VDC

vPC Peer Link

F1 Only VDC – F1 ports used for the peer-link

F2 Only VDC – F2 ports used for the peer-link

M1/F1 Mixed VDC – F1 ports (16K MAC addresses)

M1/F1 Mixed VDC – M1 ports (128K MAC addresses)

Switch vPC Peer Link vPC Interfaces

Nexus 5020

✓ ✓

Nexus 5010

✓ ✓

5548P/UP

✓ ✓

5596UP

✓ ✓

For Your Reference

vPC Supported Hardware Nexus 5000/5500

vPC – Virtual Port Channel Nexus 3000

vPC is supported on the Nexus 3000 as of

5.0(3)U2(1)

The maximum number of vPC configurable on

the Cisco Nexus 3000 Series Switches is 64

For Your Reference

• Introduction

• Fabric Extender

• FabricPath

Distributed High

Density Edge

Switching System

(up to 4096 virtual

Ethernet interfaces)

Cisco Nexus® 2000 FEX

Cisco Nexus® 5500

Cisco Nexus® 2000 FEX

Cisco Nexus® 7000

Cisco FEX-link: Virtualized Access Switch Nexus 2000 Fabric Extender

• De-Coupling of the Layer 1 and Layer 2 Topologies

• Simplified Management Model, plug and play provisioning, centralized configuration

• Line Card Portability (N2K supported with Multiple Parent Switches – N5K, 6100, N7K)

• Unified access for any server (100M1GE10GE FCoE): Scalable Ethernet, HPC, unified fabric or virtualization deployment

Virtualized

Switch

Nexus 2000: Virtualized Access Switch Changing the device paradigm

Parent Switch FEX Supported

# FEX FEX HIF Capabilities

Nexus 5020

N2K-C2148T, N2K-C2248TP

N2K-C2248TP-E, N2K-C2224TP,

N2K-C2232PP, N2K-C2232TM,

B22-HP

12 STP Edge Ports

FCoE VF ports

Nexus 5010

N2K-C2148T, N2K-C2248TP

B22-HP

12 STP Edge Ports

FCoE VF ports

Nexus 5548P/UP

N2K-C2148T, N2K-C2248TP

B22-HP

24 – L2

8 – L3

STP Edge Ports

FCoE VF ports

FabricPath Edge Ports

CTS Edge Ports

Nexus 5596UP

N2K-C2148T, N2K-C2248TP

B22-HP

24 – L2

8 – L3

STP Edge Ports

FCoE VF ports

FabricPath Edge Ports

CTS Edge Ports

For Your Reference

Cisco Nexus 5000 Parent Switch Supported Nexus 2000

Parent Switch FEX Supported # FEX FEX HIF Capabilities

N7K-M132XP-12

N2K-C2248TP, N2K-C2224TP,

N2K-C2232PP, N2K-C2232TM* 32 - L2

32 - L3

STP Edge Ports

CTS Edge Ports

N7K-M132XP-12L

N2K-C2232PP, N2K-C2232TM* 32 - L2

32 - L3

STP Edge Ports

CTS Edge Ports

N7K-M108X2-12L

N.A. (FEX not Supported)

N.A. N.A. (FEX not Supported)

N7K-F132XP-15

N.A. (FEX not Supported) N.A. N.A. (FEX not Supported)

F2 – 48 x 10G

N2K-C2232PP, N2K-C2232TM* 32 - L2

32 - L3

STP Edge Ports, FabricPath Edge Ports

CTS Edge Ports, FCoE VF ports (CY12)

M2 40G & 100G

Future N.A. Future

For Your Reference

Cisco Nexus 7000 Parent Switch Supported Nexus 2000

N2224TP 24 Port 100/1000M Host

Interfaces

2 x 10G Uplinks

N2232TM 32 Port 1/10GBASE-T Host

Interfaces

8 x 10G Uplinks (Module)

N2148T 48 Port 1000M Host

Interfaces

4 x 10G Uplinks

N2248TP 48 Port 100/1000M Host

Interfaces

4 x 10G Uplinks

N2232PP 32 Port 1/10G FCoE Host

Interfaces

8 x 10G Uplinks

FET-10G Cost Effective Fabric

Extender Transceiver

N2248TP-E 48 Port 100/1000M Host

Interfaces

4 x 10G Uplinks

32MB Shared Buffer

B22HP 16 x 1/10G Host Interfaces

8 x 10G Uplinks

Cisco Nexus 2000Series Platform Overview

Virtualized Access Switch Fabric Extender Transceiver (FET)

• Cost-effective transceiver to interconnect Nexus 2000 and Nexus 5000 and 7000 parent switch (only supported on FEX Fabric interfaces)

• SFP+ form-factor

• Multimode fiber (MMF)

• FET with OM3 MMF can operate up to 100m

• FET with OM2 MMF can operate up to 20m

• FET with 62.5/125um MMF can operate up to 10m

• Approximately 1 watt (W) per transceiver

• Incompatible with SR optics

FET supported

only on Fabric

Interfaces

Bridges that support

Interface

Virtualization ports

must support VNTag

and the VIC protocol

NIV uplink ports

must connect to

an NIV capable

bridge or an NIV

Downlink

Hypervisor

NIV downlink

ports may be

connected to an

NIV uplink port,

bridge or NIC

NIV may be

cascaded

extending the

port extension

one additional

NIV downlink ports

are assigned a virtual

identifier (VIF) that

corresponds to a

virtual interface on

the bridge and is

used to forward

frames through NIV’s

VIF NIV capable

adapters may

extending the

port extension

The FEXLink Architecture provides the ability to extend the bridge (switch) interface to downstream devices

FEXLink associates the Logical Interface (LIF) to a Virtual Interface (VIF)

Nexus 2000 Fabric Extender FEX Link Architecture

2248TP-E

N5596-L3-2(config-fex)# hardware N2248TPE queue-limit 4000000 rx

N5596-L3-2(config-fex)# hardware N2248TPE queue-limit 4000000 tx

N5596-L3-2(config)#interface e110/1/1

N5596-L3-2(config-if)# hardware N2348TP queue-limit 4096000 tx

Optimized for BigData, distributed storage, distributed computing, market data, video editing (bursty applications)

Each HIF has 128KB dedicated buffer and each NIF has 64KB dedicated buffer. The remaining 26MB is all shared

Interface allocates buffer from its dedicated pool first and then get more buffer if needed from shared pool until queue limit is reached

Queue limit specify how many buffer can be allocated for each queue.

Tune ingress queue limit when the FEX uplink experience temporary congestion.

Tune egress queue limit for better burst absorption or scenario with many to one traffic pattern

Per FEX buffer tuning

Nexus 2248TP-E Better buffering and counters

Extends FEX connectivity into the partner blade chassis

Cisco Nexus 5000 Switch is a single management point for all the blade chassis I/O modules

End-to-end FCoE support

66% decrease in blade management points*

Blade & Rack networking consistency

Interoperable with Nexus 2000 Fabric Extenders in the same Nexus parent switch

HP provides tier 1-2 support. Additional support via Nexus 5000

Cisco Nexus

B22 Series

Blade FEX

* Assuming 10 HP Blade

Chassis, Includes OA Modules

10G Nexus Fabric Extender

[16x 1GE/10GE KR server facing ports]

[8x10GE SFP+ network facing ports]

Over subscription 2:1 to 16:1 depending on number of uplinks

Cisco Nexus B22 Series Fabric Extender FEX Connectivity for the Blade Server Ecosystem

3+3 C19 cords

interconnect

bays usable

for B22 FEX

– 10/1G &

Hot-plug

redundant

Network and serial

connectors

Enclosure links

Redundant

Onboard

Administrators

Cisco Nexus B22 Series Fabric Extender FEX Connectivity for HPC C7000 & C3000 Chassis

• Introduction

• Fabric Extender

• FabricPath

Redundancy model – Dual Switch with redundant fabric

Provides isolation for Storage topologies (SAN ‘A’ and ‘B’)

Port Channel and Pinning supported for Fabric Link

Redundancy model – Single switch with dual ‘supervisor’ for fabric, data control & management planes

No SAN ‘A’ and ‘B’ isolation

FEX-link & vPC Virtualized Access Switch Nexus 5000/5500 Topologies prior to 5.1(3)N1

vPC Supported with up to 2 x 8

Local Etherchannel with up to 8

FCoE Adapters supported on 10G

N2K interfaces

Straight Through Dual Homed

Redundancy model – Dual Switch (each switch supports redundant supervisors)

vPC Supported with NX-OS 5.2

Fabric links supported on N7K-M132XP-12, N7K-M132XP-12L & N7K-F248XP-25

Port Channel only supported for Fabric Links

FEX-link & vPC Virtualized Access Switch Nexus 7000 Topologies supported as of 5.2

vPC Supported with up to 2 x 8

Local Etherchannel with up to 8

Nexus 7000 – vPC Nexus 7000 – vPC

• How is this achieved?

• Configuration associates FCoE traffic to a specific fabric link

switchA(config)# fex 101

switchA(config-fex)# fcoe

switchB(config)# fex 101

Nexus 2000

Fabric

Extender (FEX)

Nexus 5000

(San B) Nexus 5000

(San A)

Storage

SAN B SAN A

Enhanced vPC Isolating SAN A and SAN B

• Introduction

• Fabric Extender

• FabricPath

“FabricPath brings Layer 3

routing benefits to flexible Layer 2

bridged Ethernet networks”

Configuration

Plug & Play

Provisioning

Flexibility

Multi-pathing

(ECMP)

Convergence

Highly Scalable

Switching Routing

FabricPath

Cisco FabricPath NX-OS Innovation Enhancing L2 with L3

CE Edge

FP Core

Switch

Interface connected to traditional network device

Sends/receives traffic in standard 802.3 Ethernet frame format

Participates in STP domain

Forwarding based on MAC table

Classical Ethernet (CE)

FabricPath (FP)

Interface connected to another FabricPath device

Sends/receives traffic with FabricPath header

Does not run spanning tree

Does not perform MAC learning!

Exchanges topology info through L2 ISIS adjacency

Forwarding based on ‘Switch ID Table’

Cisco FabricPath Terminology

Classical Ethernet

• The association MAC address/Switch ID is maintained at the edge

• Traffic is encapsulated across the Fabric S300: CE MAC

Address Table

MAC IF

… …

MAC IF

A S100

FabricPath

Routing Table

… …

S100 L1, L2, L3,

FabricPath (FP)

Switch ID

space:

Routing

decisions are

made based

on the

FabricPath

routing table

MAC adress

space:

Switching

based on MAC

address tables

S100 S300 A

Cisco FabricPath A New Data Plane

S100: CE MAC

Address Table

0 S300

FabricPath

Classical

Ethernet

S300: CE MAC

Address Table

MAC IF

… …

S200: CE MAC

Address Table

MAC IF

… …

S100 M A

Lookup B: Miss

Don’t learn

Lookup B: Miss

Lookup B: Hit

Learn source A

MAC IF

A S100

MAC IF

… …

MAC IF

… …

FabricPath Key Concept #1 Conversational MAC Learning

Classical

Ethernet Conversational

Learning

S100: CE MAC

Address Table

FabricPath

1 S300: CE MAC

Address Table

MAC IF

… …

S200: CE MAC

Address Table

MAC IF

… …

MAC IF

A S100

MAC IF

… …

MAC IF

… …

FabricPath

Routing Table

… …

S100 L1, L2, L3,

S300 S100 B A

Lookup A: Hit

Send to S100 Lookup A: Hit

Learn source B

MAC IF

B S300

FabricPath Key Concept #1 Conversational MAC Learning

FabricPath

• Describes shortest (best) paths to each Switch ID based on link metrics

• Equal-cost paths supported between FabricPath switches

FabricPath

Routing Table on

S100 Switc

S10 L1

S20 L2

S30 L3

S40 L4

S200 L1, L2, L3,

… …

S300 L1, L2, L3,

One ‘best’ path

to S10 (via L1)

Four equal-cost

paths to S300

FabricPath Key Concept #2 It’s a Routed Network

• Multi-destination traffic constrained to loop-free trees touching all FabricPath switches

• Root switch elected for each multi-destination tree in the FabricPath domain

• Loop-free tree built from each Root assigned a network-wide identifier (Ftag)

• Support for multiple multi-destination trees provides multipathing for multi-destination traffic

Two multi-destination trees supported in NX-OS release 5.1

Root for

Tree 1

S100 S

Root for

Tree 2

10 S200

40 Logical

Tree 1

30 Logical

Tree 2

FabricPath

FabricPath Key Concept #3 Multicast

FabricPath

MAC Table on

S100 MAC IF/SID MAC IF/SID

A e1/13 (local)

Root for

Tree 1

Root for

Tree 2

MAC A MAC B

Multidestinatio

Trees on

Switch 100 Tre

1 po10

2 po10,po20,po30

Broadcast →

DMAC→FF

SMAC→A

Payload

Multidestinatio

Trees on

Switch 10 Tre

1 po100,po200,po

2 po100

po10 po20

Ftag →

DMAC→FF

SMAC→A

Payload

DA→FF Ftag→1

SA→100.0.12

DMAC→FF

SMAC→A

Payload

po20 po30 po40

DMAC→FF

SMAC→A

Payload

DA→FF Ftag→1

SA→100.0.12

Learn MACs of directly-connected

devices unconditionally

Don’t learn MACs from

flood frames

FabricPath

MAC Table on

S200 MAC IF/SID

Multidestinatio

Trees on

Switch 300 Tre

1 po10,po20,po30

2 po40

Putting it all together – Host A to Host B (1) Broadcast ARP Request

Root for

Tree 1

Root for

Tree 2

MAC A MAC B

po10 po20

po20 po30 po40

Multidestinatio

Trees on

Switch 100 Tre

1 po10

2 po10,po20,po30

Ftag →

Multidestinatio

Trees on

Switch 10 Tre

1 po100,po200,po

2 po100

Ftag →

DMAC→A

SMAC→B

Payload

DA→MC1 Ftag→1

SA→300.0.64

DMAC→A

SMAC→B

Payload

7 Unknown →

DMAC→A

SMAC→B

Payload

DA→MC1 Ftag→1

SA→300.0.64

FabricPath

MAC Table on

S300 MAC IF/SID MAC IF/SID

B e2/29 (local)

If DMAC is known, then

learn remote MAC

Multidestinatio

Trees on

Switch 300 Tre

1 po10,po20,po30

2 po40

9 FabricPath

MAC Table on

S100 MAC IF/SID

A e1/13 (local)

MAC IF/SID

A e1/13 (local)

B 300.0.64

(remote)

12 DMAC→A

SMAC→B

Payload

*MC1 = 01:0f:ff:c1:01:c0

Putting it all together – Host A to Host B (2) Broadcast ARP Reply

MAC A MAC B

po10 po20

po20 po30 po40

DMAC→B

SMAC→A

Payload

FabricPath

MAC Table on

DMAC→B

SMAC→A

Payload

C IF/SID

A e1/13 (local)

B 300.0.64

(remote)

S300 →

FabricPath

Routing Table

on S100 Switc

S10 po10

S20 po20

S30 po30

S40 po40

DMAC→B

SMAC→A

Payload

DA→300.0.64 Ftag→1

SA→100.0.12

S300 →

FabricPath

Routing Table

on S30 Switc

… …

S300 po300

S300 →

DMAC→B

SMAC→A

Payload

DA→300.0.64 Ftag→1

SA→100.0.12

FabricPath

MAC Table on

S300 MA

C IF/SID

B e2/29 (local)

C IF/SID

A S100.0.12

(remote)

B e2/29 (local)

FabricPath

Routing Table

on S300 Switc

… …

S300 Use LID

If DMAC is known, then

learn remote MAC

Putting it all together – Host A to Host B Unicast Data - Routed

Switch CE edge port FP core port Routing for

FP VLAN

Nexus 5020

✗ ✗ ✗

Nexus 5010

✗ ✗ ✗

Nexus 5548P/UP

✓ ✓ ✓

Nexus 5596UP *

✓ ✓ ✓

For Your Reference

* L3 daughter card is ‘not’ needed in 5550 to run

FabricPath, only L3 routing for FabricPath VLANs

FabricPath Hardware & Software Nexus 5500

I/O Module CE edge port FP core port Routing for FP

N7K-M132XP-12

✗ ✗ ✓

N7K-M148GT-11

✗ ✗ ✓

N7K-M148GS-11

N7K-M148GS-11L ✗ ✗ ✓

N7K-M108X2-12L

✗ ✗ ✓

N7K-F132XP-15 ✓ ✓ ✗

N7K-F248XP-25 * ✓ ✓ ✓

* F2 module needs to be in its own VDC or system. It is not possible to mix F1 and

F2 LC in the same VDC

For Your Reference

FabricPath Hardware & Software Nexus 7000

The Nexus 7000 features two kinds of IO Modules:

M series and F series.

M I/O Modules cannot switch FabricPath traffic

When running FabricPath,

FP Core and CE Edge ports must be on an F module or 5500

New FabricPath/CE locally significant VLAN mode:

FabricPath VLANs can only be enabled on F modules (FEX+F2 with NX-OS 6.0

release as well) or 5500 (5500 + FEX as well)

S100(config)# vlan 10

S100(config-vlan)# mode ?

ce Classical Ethernet VLAN mode

fabricpath Fabricpath VLAN mode

S100(config-vlan)# mode fabricpath

S100(config-vlan)#

FabricPath

F FabricPath Core

Classical

Ethernet Edge

FabricPath Design – VLAN Mode F1/F2/M1 Interaction

SVI SVI

VLAN 10 = CE VLAN

switchport VLAN 10

VLAN 10 = CE VLAN VLAN 20 = FP VLAN

switchport VLAN 10

switchport VLAN 20

VLAN 10 = FP VLAN

switchport VLAN 10

switchport trunk VLAN 10,20 CE FP

switchport trunk VLAN 10,20

Bridging in CE VLAN from M1 port to F1 port in CE mode

Routing via SVIs from M1 port in CE VLAN to F1 port in FP VLAN

F1 trunk port in CE mode carrying CE VLAN and FP VLAN

F1 port in FP mode carrying CE VLAN and FP VLAN

M1 trunk port carrying CE VLAN and FP VLAN

M1 port in FP VLAN

Note : F2 needs to be on

its own VDC so the FP

and CE VLAN

compatibility mode does

not apply

FabricPath Design F1/F2/M1 Interaction

• Introduction

• Fabric Extender

• FabricPath

• Summary

Leading with Innovation

Nexus 7K

• Industry leading scale and density

• Enabling scalable fabrics: FabricPath

• High-Availability with hitless ISSU

• Workload Mobility: OTV & LISP

• DC Consolidation: VDCs, FCoE

Nexus 2K

• Remote linecard for N5K & N7K

• 1GE & 10GE optimized options with FCoE

• Consistent architecture for blade and rack servers

Nexus 5K

• Low latency Non-blocking

• Unified ports: 1/10GE, FCoE, 2/4/8G FC

• Enabling Scalable Fabrics: FabricPath

• Virtualization: Adapter FEX, VM-FEX

Blade Offerings

• Nexus 4K : 10GE FCoE blade switch for IBM

• B22 HP: Fabric extender for HP blade server chassis

Nexus 1K

• Visibility and security for virtual machines

• Support for multiple hypervisors

• Services integration

Nexus 3K

• Ultra low latency 1/10/40GE Switching

• Optimized for high-performance workloads

• Rich L2/L3 features

Thank you.

unified fabric - ciscosimplified management with scale architectural flexibility active-active...

Documents

max mobility and flexibility - easyrobotics · cobot...

table of contents · v. kettlebell training improves your...

power mobility and a consistent experience with unified

lesson: week 1...flexibility alignment mobility stamina...

simplicity meets flexibility - unified communications

exchange 2007 mobility johann kruse national technology...

vmware airwatch windows 10 unified endpoint … · what is...

cisco unified access cisco mobility vision, strategy, and...

cisco unified mobility

tsf flexibility & mobility

mobility | flexibility | availability

unified communications mobility - zultys...zultys unified...

the new mobility with unified communications

unified mobility ii

why upgrade to cisco unified communications manager (cucm...

unified mobility iii

mobility – flexibility - security product presentation

touch cisco mit cisco uc-mobility- lösungen am ball...

mobility enables true unified communications

enhanced mobility management technique for unified...