CCNA – DC

Introduction to FabricPath

Ozden Karakok – CCIE SAN, R&S, SNA/IP

© 2013 Cisco and/or its affiliates. All rights reserved. 1

 Data Center Technologies
3.0 Storage networking
Describe the initiator target
1.0 Cisco data center fundamental concepts
Verify SAN switch operations
Describe network architectures for the data center (LAN, SAN) Describe basic SAN connectivity
Describe the modular approach in network design Describe the different types of storage array connectivity
Describe the data center core layer Verify name server login
Describe the data center aggregation layer Describe, configure, and verify zoning
Perform initial setup
Describe the data center access layer Describe, configure, and verify VSAN
Describe the collapse core model 4.0 Data center virtualization
Describe Cisco FabricPath Describe device virtualization
Identify key differentiator between DCI and network interconnectivity Describe server virtualization
Describe the Cisco Nexus 1000V Switch
Describe, configure, and verify vPC Verify initial setup and operation for the Cisco Nexus 1000V Switch
Describe the functionality of and configure port channels 5.0 Unified computing
Describe and configure VDC Describe the Cisco UCS product family
Describe the Cisco UCS Manager
Describe the edge and core layers of the SAN
Describe, configure, and verify cluster configuration
Describe the Cisco Nexus product family Describe and verify discovery operation
Configure and verify network connectivity Describe, configure, and verify connectivity
Identify control and data plane traffic Perform initial setup
Perform initial setup Describe the key features of the Cisco UCS Manager
6.0 Data center network services
2.0 Data center unified fabric Describe standard Cisco ACE features for load balancing
Describe FCoE Describe server load-balancing virtual context and high availability
Describe FCoE multihop Describe server load-balancing management options
Describe VIFs Describe the benefits of the Cisco Global Load Balancing Solution
Describe how the Cisco Global Load Balancing Solution integrates with local
Describe FEX products
Cisco load balancers
Perform initial setup Describe the Cisco WAAS need and advantages in the data center

© 2013 Cisco and/or its affiliates. All rights reserved. 2

• Introduction to FabricPath
• FabricPath Technical Overview
• FabricPath Configuration Example

© 2013 Cisco and/or its affiliates. All rights reserved. 3

© 2013 Cisco and/or its affiliates. All rights reserved. 4
 • Local STP problems have network-wide impact, troubleshooting is difficult
• STP provides limited bandwidth (no load balancing)
• STP convergence is disruptive
• Tree topologies introduce sub-optimal paths
• MAC address tables don’t scale
• Flooding impacts the whole network

© 2013 Cisco and/or its affiliates. All rights reserved. 5

 Switching Routing
§ Easy Configuration § Multi-pathing (ECMP)
§ Plug & Play § Fast Convergence
§ Provisioning Flexibility § Highly Scalable

FabricPath

“FabricPath brings Layer 3 routing benefits to

flexible Layer 2 bridged Ethernet networks”

© 2013 Cisco and/or its affiliates. All rights reserved. 6

 STP -> vPC -> FabricPath
Shipping Inter-POD Connectivity across L3 LISP VM mobility
Nexus 7k OTV Failure Boundary Preservation

IP Cloud

Core
L3

L3 vPC Aggregation
L2
FabricPath
vPC vPC vPC+ Access
L2

Virtual Access

STP+ vPC FabricPath

NIC Teaming 16x ECMP
STP Enhancements Simplified loop-free trees Low Latency / Lossless
Bridge Assurance 2x Multi-pathing MAC Scaling
Shipping Shipping Nexus Shipping
Nexus 7k/5k 7k/5k Nexus 7k/5k

© 2013 Cisco and/or its affiliates. All rights reserved. 7

 Turn the network into a Fabric

FabricPath

• Connect a group of switches using an arbitrary topology

• With a simple CLI, aggregate them into a Fabric:

N7K(config)# interface ethernet 1/1

N7K(config-if)# switchport mode fabricpath

§ No STP inside. An open protocol based on L3 technology

provides Fabric-wide intelligence and ties the elements together.

© 2013 Cisco and/or its affiliates. All rights reserved. 8

© 2013 Cisco and/or its affiliates. All rights reserved. 9
 Plug-n-Play L2 IS-IS Manages Forwarding Topology

• IS-IS assigns addresses to all FabricPath switches automatically

• Compute shortest, pair-wise paths
• Support equal-cost paths between any FabricPath switch pairs

S10 S20 S30 S40

FabricPath
Routing Table
Switch IF

S10 L1

S20
S30
L2
L3
FabricPath
S40 L4 L1 L2
L3
S200 L1, L2, L3, L4 L4

… …
S400 L1, L2, L3, L4

S100 S200 S300 S400

© 2013 Cisco and/or its affiliates. All rights reserved. 10

 S10 S20 S30 S40
Switch ID space:
Routing decisions
are made based on S300: FabricPath
the FabricPath Routing Table
routing table A è B S100 è S300
Switch IF
FabricPath (FP) … …
S100 S200 S300
S100 L1, L2, L3, L4
MAC address space:
Switching based on
MAC address tables
1/1 1/2 S300: CE MAC
Address Table
Classical Ethernet (CE) MAC IF
A B B 1/2
…
A S100
…

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

• Traffic is encapsulated across the Fabric

© 2013 Cisco and/or its affiliates. All rights reserved. 11

 § 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’
FP Core Ports
S10 S20 S30 S40

Spine Switch

FabricPath (FP)
S100 S200 S300

Leaf Switch

1/1 1/2

Classical Ethernet (CE)

A B

CE Edge Ports § 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

© 2013 Cisco and/or its affiliates. All rights reserved. 12

 S10 S20 S30 S40

A è B S100 è M

FabricPath Lookup B: Hit

S100 S200 S300
Learn source A
Lookup B: Miss
Flood Lookup B: Miss
Don’t learn
S100: CE MAC 1/1 S200: CE MAC 1/2 S300: CE MAC
Address Table Address Table Address Table
MAC IF MAC IF MAC IF
A B
…
A …
1/1 … … B 1/2
… … … … …
A S100
…

Classical Ethernet

© 2013 Cisco and/or its affiliates. All rights reserved. 13

 S10 S20 S30 S40

S300: FabricPath
Routing Table
B è A S300 è S100
Lookup A: Hit Lookup A: Hit Switch IF
Learn source B
S100
FabricPath
S200 S300
Send to S100 … …
S100 L1, L2, L3, L4

S100: CE MAC Address 1/1 S200: CE MAC Address 1/2 S300: CE MAC Address
Table Table Table
MAC IF MAC IF MAC IF
A B
…
A …
1/1 … … B 1/2
…
B …
S300 … … A
… S100
…

Classical Ethernet

© 2013 Cisco and/or its affiliates. All rights reserved. 14

 Nexus 7000
Only F-series module support FabricPath:

N7K-­‐F132XP-­‐15   N7K-­‐F248XP-­‐25  
Minimum Software: NX-OS 5.1(1) Minimum Software: NX-OS 6.0(1)

Nexus 5500
N5K-­‐C5548P-­‐FA   N5K-­‐C5596UP-­‐FA  
N5K-­‐C5548UP-­‐FA  
Minimum Software: NX-OS 5.1(3)N1(1)

Nexus 2000
FabricPath supported on Nexus 2000 platforms when connected to NEXUS 5500 chassis or
NEXUS 7000 F2 series I/O Module
FEX Host Interfaces can be configured as CE edge ports
Supported FEX models: 2224TP, 2248TP, 2248TP-E, 2232PP, 2232TM

© 2013 Cisco and/or its affiliates. All rights reserved. 15

• N7000 with N7K-F1* linecard as of 5.1.1
• N7000 with N7K-F2* linecard as of 6.0.1 (F2E 6.1.2)
N7000 + FEX as of 6.1.1 (with N7K-F2) for CE ports
• N5500 as of 5.1.3 (no L3 module required)
N5500 + FEX as of 5.1.3 for CE ports
• Enhanced L2 license is required for FabricPath
• Packaged as feature-set (plugin)

N7K(config)# install feature-set fabricpath

N7K(config)# feature-set fabricpath
N7K(config)# int e4/1
N7K(config-if)# switchport mode fabricpath
...
N7K(config-if)# vlan 42
N7K(config-vlan)# mode fabricpath

© 2013 Cisco and/or its affiliates. All rights reserved. 16

 FabricPath
• 2 types of vlans
§ CE (Classic Ethernet, default)
Classic Ethernet
§ FabricPath (FP)

• FP vlans cannot go on M1,M2 modules

• Only FP vlans will be carried over FP interfaces

• FP vlans can be mixed with CE vlans on edge interfaces

Port Type VLANs allowed to be configured VLANs allowed to be brought up

N7K-M1, N7K-M2 FP, CE CE

N7K-F1, N7K-F2 Edge FP, CE FP, CE
Core == switchport mode fabricpath
N7K-F1, N7K-F2 Core FP, CE FP
N5500, Edge FP, CE FP, CE
Edge == switchport mode access || trunk
N5500, Core FP, CE FP

N7K(config)# vlan 3002

N7K(config-vlan)# mode ?
ce Classical Ethernet VLAN mode
fabricpath
© 2013 Cisco and/or its affiliates. All rights reserved.
Fabricpath VLAN mode 17
 FabricPath
S100 S200 S300

1/1 1/2 E1/2: CE MAC Address Table

To Fabric Modules

MAC IF
B
Fabric ASIC Fabric ASIC B 1/2
…
A …
S100
2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G
SoC SoC SoC SoC SoC SoC SoC SoC

2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G 2 X 10G

SoC SoC SoC SoC SoC SoC SoC SoC

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32

A Front Panel Ports

E1/1-2: CE MAC Address E1/3-4: CE MAC Address E1/31-32: CE MAC Address

Table Table Table
MAC IF MAC IF MAC IF
A 1/1 … … … …
B S300 … … … …

© 2013 Cisco and/or its affiliates. All rights reserved. 18

 Forwarding through distinct ‘Trees’
• Several ‘Trees’ are rooted in key location inside the fabric
• All Switches in L2 Fabric share the same view for each ‘Tree’
• Multicast traffic load-balanced across these ‘Trees’
Root for Tree Root for Tree Root for Tree Root for Tree
#1 #2 #3 #4

Ingress switch for FabricPath

decides which “tree” to be used
and add tree number in the header

L2 Fabric

A C
© 2013 Cisco and/or its affiliates. All rights reserved. 19
 Time To Live (TTL) and Reverse Path Forwarding (RPF) Check
Root
STP Domain S1 S2
Root
TTL=2 TTL=1

L2 Fabric
S10

TTL=3
TTL=0

• Control protocol is the only mechanism § TTL in FabricPath header

preventing loops § Decrement by 1 at each hop
• If STP fails -> infinite loop § Frames with TTL =0 are discarded
•no backup mechanism in the data plane § RPF check for multicast based on “tree” info
•Possible network melt-down as the result of flooding

© 2013 Cisco and/or its affiliates. All rights reserved. 20

 Outer Outer FP
CRC
DA SA Tag DMAC SMAC 802.1Q Etype Payload
(new)
(48) (48) (32)

47 0
Endnode U/L I/G Endnode Switch ID SubSwitch
Local ID
ID[5:0] ID[7:6] ID
6 bits 1 1 2 bits 12 bits 8 bits 16 bits

• Outer SA:
§ SwitchID in ingress FP switch system ID (‘sh fabricpath switch-id’) N7K# sh fab switch-id | i SYS|\*
More on next slide… Legend: '*' - this system
§ SubswitchID is used in some cases of VPC+ (more on this later) SWITCH-ID SYSTEM-ID FLAGS STATE STATIC EMULATED

§ LID is specific to the implementation (for N7K the LID is the port index *2028 b414.89e3.a041 Primary Confirmed No No
of the ingress interface, for N5K LID most of the time will be 0)
§ EndnodeID is not currently used

• Outer DA:
§ For known SA/DA is taken from MAC table for DMAC N7K# sh mac address-table address 0000.1234.5678

§ For broadcast and multicast is the same as DMAC VLAN MAC Address Type age Ports/SWID.SSID.LID
---------+-----------------+--------+---------+------------------
§ For unknown unicast DA is 010f.ffc1.01c0 (flood to vlan)
3000 0000.1234.5678 dynamic 0 2.0.1054
§ For known unicast DA, but unknown SA is 010f.ffc1.02c0 (flood to
fabric)
• Example
Ethernet II, Src: 02:00:64:00:00:00, Dst: 01:00:5e:00:00:02, Type: 0x8903

Switch_ID SubSwitch_ID LID

100 0 0

© 2013 Cisco and/or its affiliates. All rights reserved. 21

 • Each FP switch is identified by unique number (ID), dynamically assigned or static

• Dynamic Resource Allocation Protocol (DRAP) is responsible for allocating switch

IDs and resolving duplicate-ID conflicts. Conflicts are resolved by renumbering
switches with higher systemID
N7K# sh fabricpath switch-id
FABRICPATH SWITCH-ID TABLE
========================================================================= 2 3
SWITCH-ID SYSTEM-ID FLAGS STATE STATIC EMULATED 1
----------+----------------+------------+-----------+--------------------
*3 c062.6bac.e343 Primary Confirmed Yes No
30
40
547f.ee02.ce3c
547f.ee04.5cfc
Primary
Primary
Confirmed
Confirmed
Yes
Yes
No
No +
4 5
• When partitioned FP network is merged (or new switch joins the fabric) 3
connecting interface is not enabled for data before all conflicts are resolved
N7K(config-if-range)# no shut
18:46:04 %FABRICPATH-2-FABRICPATH_LINK_BRINGUP_STALLED_STATIC: Link bringup stalled due to conflicts

N7K# sh fabricpath conflict all

=
====================================================
Port State 2 3
---------------+-------------------------+---------- 1
Ethernet3/31 Suspended due to conflicts
==============================================
Fabricpath Conflicts 4 5
SYSTEM-ID SWITCH-ID STATIC 6
---------------+--------------+---------------
c062.6bac.e343 3 Yes
c062.6bac.e342 3 Yes
© 2013 Cisco and/or its affiliates. All rights reserved. 22
 • Known unicast traffic is load-balanced across equal-cost → FabricPath interface
routes à Tree 1
• FabricPath uses 2 loop-free trees for unknown unicast, à Tree 2
broadcast and multicast traffic
• 2 trees are for load-balancing
• For each packet tree is selected by ingress FP switch and choice is carried S1
SysID 50
in the packet header
R
• Root of tree1 is a switch highest sysID (priority+mac) S2 S3
SysID 10 SysID 20
• Root of tree2 is a switch with 2 highest sysID
nd
Lower SysID wins

• Tree is a least-cost-to-the-root graph, with lower sysID used as tie-breaker*

• In case of Tree1 root failure both roots are reelected
S4
SysID 30

Nexus# show fabricpath isis topology summary

Fabricpath IS-IS domain: default FabricPath IS-IS Topology Summary
MT-0
Configured interfaces: Ethernet4/4
Number of trees: 2 • Root for Tree 1
Tree id: 1, ftag: 1, root system: 001b.54c2.4244, 4
Tree id: 2, ftag: 2, root system: 001b.54c2.4243, 3
© 2013 Cisco and/or its affiliates. All rights reserved.
• Root for Tree 2 23
 Outer Outer FP
CRC
DA SA Tag DMAC SMAC 802.1Q Etype Payload
(new)
(48) (48) (32)

16 bits 10 bits 6 bits

Ethertype
FTAG TTL
0x8903

• Ethertype for FabricPath packets is 0x8903

• TTL set to 32 and is decremented at every hop. Packet is discarded when TTL reaches 0. It
will be possible in the future release to set the initial value of TTL

• FTAG: (Forwarding TAG) For multidestination traffic carries the ID of the tree chosen at the
FabricPath ingress switch. DRAP is responsible to keep FTAGs unique/consistent. For
known unicast carries topology ID
Nexus# show fabricpath isis topology summary
Fabricpath IS-IS domain: default FabricPath IS-IS Topology Summary
• Root for Tree 1, FTAG 1
MT-0
Configured interfaces: Ethernet4/4
Number of trees: 2 • Root for Tree 2, FTAG 2
Tree id: 1, ftag: 1, root system: 001b.54c2.4244, 4
Tree id: 2, ftag: 2, root system: 001b.54c2.4243, 3

• Wireshark decodes FP encapsulation (tested on 1.8.3) : EditàPreferencesàProtocolsàCFPàEnable Dissector

© 2013 Cisco and/or its affiliates. All rights reserved. 24
 1 2 • Accept packets from
1,4
(reverse path forwarding) root

• Accept packets from 3

• RPF: check where the source switch of the packet is
• Accept packets from
and only accept packets from the interface we would 4,1,2
have used if we were to send packet to that source 4 3

• At each FP hop RPF check is performed for frames forwarded along the
trees against source switchID + FTAG
Hokum-f2# sh l2 multicast trees

(ftag/2, topo/0, Switch-id 40), uptime: 1w0d, isis How to read

Outgoing interface list: (count: 1, '*' is the preferred interface) § Packets with FTAG==2 from
* Interface Ethernet3/39, [admin distance/115] uptime: 1d23h, isis
switch 30 will be accepted
(ftag/2, topo/0, Switch-id 30), uptime: 1w0d, isis from interface e3/35
Outgoing interface list: (count: 1, '*' is the preferred interface) § Packets with FTAG==1 from
* Interface Ethernet3/35, [admin distance/115] uptime: 02:56:04, isis switch 30 will be accepted
(ftag/2, topo/0, Switch-id 100), uptime: 1w0d, isis from interface e3/35
Outgoing interface list: (count: 1, '*' is the preferred interface) May also use
* Interface Ethernet3/39, [admin distance/115] uptime: 1d23h, isis § sh fabric isis trees
(ftag/1, topo/0, Switch-id 30), uptime: 02:56:06, isis
Outgoing interface list: (count: 1, '*' is the preferred interface)
* Interface Ethernet3/35, [admin distance/115] uptime: 02:56:06, isis

© 2013 Cisco and/or its affiliates. All rights reserved. 25

 POD 1
Local Vlans 1-500
Global Vlans 501-…

• Routing table & Trees (FTAGs) are per topology

• Switch ID is shared across all topologies

• FP interface may belong to several topologies

FabricPath
• N7000: Single topology is currently supported, multiple topologies support is
expected in 6.2 release
• N5500: As of 5.2.1 default + 1 extra topology is supported – main use is to
permit separate L2 pods to use same local vlan set
POD 2
Local Vlans 1-500
Interface2 Interface1 Global Vlans 501-…

Topolog Topolog
y1 y2
FTAGs FTAGs
1,2 3,4

Vlan1 Vlan2 Vlan3 Vlan4

© 2013 Cisco and/or its affiliates. All rights reserved. 26

 Fabric
Path
S10

• Allows dual-homed connections from edge ports into

FabricPath domain with active/active forwarding
• Classic Ethernet switches, Layer 3 routers, load-balancers,
dual-homed servers, etc. S100 S200

Only requirement is device can form port-channel interface

• Can also provide active/active HSRP

• Configuration virtually identical to standard vPC
- under vPC domain configuration of ‘fabricpath switch-id’ results in vPC+

CE

STP Device Host

Physical view

© 2013 Cisco and/or its affiliates. All rights reserved. 27

 Fabric
Path
S10

• VPC+ peer switches share a “virtual” FabricPath switch ID

• MAC addresses behind VPC+ port-channels appear as
“connected” to the virtual switch, not the VPC+ peer switches
• Allows load-balancing within FabricPath domain toward the S100 S200

VPC+ virtual switch

• Conversion between VPC and VPC+ is disruptive
• VPC+ requires F modules with FabricPath enabled in the VDC
or N55xx
S 1000

Peer-link and all VPC+ connections must be to F ports

CE

STP Device Host

Logical view

© 2013 Cisco and/or its affiliates. All rights reserved. 28

 • A given VDC can be part of VPC domain, or VPC+ domain, but not both
• VPC+ only works on F modules with FabricPath enabled in the VDC

VPC VPC+
Peer-link M ports or F ports F ports
Member ports M ports or F ports F ports
VLANs CE FabricPath VLANs only

Peer-link switchport mode CE trunk port FabricPath core port

• You don’t select vPC+, you select FP and indirectly vPC+

© 2013 Cisco and/or its affiliates. All rights reserved. 29

 Transparent Interconnection of Lots of Links

Don’t mistake
• IETF standard for Layer 2 multipathing with bird seed
• Driven by multiple vendors, including Cisco
• TRILL now officially moved from Draft to Proposed Standard in IETF
• Proposed Standard status means vendors can confidently begin developing
TRILL-compliant software implementations
• Cisco FabricPath capable hardware is also TRILL capable

http://datatracker.ietf.org/wg/trill/

© 2013 Cisco and/or its affiliates. All rights reserved. 30

 FabricPath Simple STP Interaction

Fabric
STP Domain 1 Path STP Domain 2
FabricPath
B B B (no STP) B
P P
CE
P P BID := Prio +c84c.75fa.
D
U
D
U
D
U
D
U
6000

• The Fabric looks like a single bridge:

• It sends the same STP information on all edge ports STP State: Blocking/
Discarding
• It expects to be the root of the STP for now
External to FP in the
(edge ports will block if they receive better information)
Legacy environment
• No BPDUs are forwarded across the fabric
• An optional mechanism allows propagating TCNs if needed

© 2013 Cisco and/or its affiliates. All rights reserved. 31

 FabricPath TRILL
Frame routing Yes Yes
(ECMP, TTL, RPFC etc…)
vPC+ Yes In the works
FHRP active/active Yes No
Multiple topologies Yes In the works
Conversational learning Yes No
Inter-switch links Point-to-point only Point-to-point OR shared

• FabricPath will provide a TRILL mode with a software upgrade (hardware is already TRILL capable)
• Cisco will push FabricPath-specific enhancements to TRILL

© 2013 Cisco and/or its affiliates. All rights reserved. 32

© 2013 Cisco and/or its affiliates. All rights reserved. 33
• FabricPath not enabled by default

• Once FabricPath is enabled, Conversational MAC Learning is enabled on all FP Core interfaces
(cannot be disabled)
• Conversational MAC Learning is not enabled for CE interfaces

• All VLAN’s are in CE mode by default.

© 2013 Cisco and/or its affiliates. All rights reserved. 34

1. Ensure you have Nexus devices that supports FabricPath.
2. System is running minimum NX-OS 5.1.1 (Nexus 7000) / NX-OS 5.1.3 (Nexus 5500) software
release
3. Obtain and install “Enhanced Layer 2” license. You will need to obtain the host id of the switch
“show license host-id”
4. Install the license “ install license <file> ”
5. Install FabricPath feature set – FabricPath depends on several discrete processes and
functions; ensures all required system plugins loaded into memory by issuing “ install
feature-set fabricpath ”

© 2013 Cisco and/or its affiliates. All rights reserved. 35

Once FabricPath feature-set installed:
1. Enable FabricPath feature set
feature-set fabricpath
2. Define FabricPath VLANs
vlan <range>
mode fabricpath
3. Identify FabricPath interfaces
interface <name>
switchport mode fabricpath

• FabricPath devices will form adjacencies, exchange unicast and multicast routing information,
and begin forwarding traffic

© 2013 Cisco and/or its affiliates. All rights reserved. 36

 SW11 SW21
install feature-set fabricpath install feature-set fabricpath
Feature-set fabricpath SW11 SW21 Feature-set fabricpath
Fabricpath switch-id 11 Fabricpath switch-id 21
Interface ethernet 9/1-4 Interface ethernet 9/1-4
switchport mode fabricpath switchport mode fabricpath
Vlan 100 Vlan 100
mode fabricpath mode fabricpath
Vlan 101 Vlan 101
mode fabricpath mode fabricpath

SW12 SW12 SW22 SW13 SW23 SW23

Feature-set fabricpath Feature-set fabricpath
Fabricpath switch-id 12 Fabricpath switch-id 23
Interface ethernet 9/9-10 Interface ethernet 9/17-18
switchport mode fabricpath switchport mode fabricpath
Vlan 100 Vlan 100
mode fabricpath mode fabricpath
Vlan 101 Vlan 101
mode fabricpath mode fabricpath

SW22 SW13
Feature-set fabricpath Feature-set fabricpath
Fabricpath switch-id 22 Fabricpath switch-id 13
Interface ethernet 9/9-10 Interface ethernet 9/17-18
switchport mode fabricpath switchport mode fabricpath
Vlan 100 Vlan 100
mode fabricpath mode fabricpath
Vlan 101 Vlan 101
mode fabricpath mode fabricpath

© 2013 Cisco and/or its affiliates. All rights reserved. 37

 show fabricpath switch-id
NX-1# sh fabricpath switch-id
FABRICPATH SWITCH-ID TABLE
Legend: '*' - this system
=========================================================================
SWITCH-ID SYSTEM-ID FLAGS STATE STATIC EMULATED
----------+----------------+------------+-----------+--------------------
*30 64a0.e740.0443 Primary Confirmed Yes No
40 64a0.e740.0444 Primary Confirmed Yes No
300 547f.ee5f.773c Primary Confirmed Yes No
400 547f.ee5f.7641 Primary Confirmed Yes No

show fabricpath isis adjacency

NX-1# sh fabricpath isis adjacency
Fabricpath IS-IS domain: default Fabricpath IS-IS adjacency database:
System ID SNPA Level State Hold Time Interface
NX-3 N/A 1 UP 00:00:31 Ethernet3/21
NX-3 N/A 1 UP 00:00:32 Ethernet3/22
NX-4 N/A 1 UP 00:00:25 Ethernet3/23
NX-4 N/A 1 UP 00:00:29 Ethernet3/24

show fabricpath isis topology summary

# sh fabricpath isis topology summary
Fabricpath IS-IS domain: default FabricPath IS-IS Topology Summary
MT-0
Configured interfaces: Ethernet3/21 Ethernet3/22 Ethernet3/23 Ethernet3/24
Number of trees: 2
Tree id: 1, ftag: 1, root system: 64a0.e740.0443, 30
Tree id: 2, ftag: 2, root system: 64a0.e740.0444, 40

© 2013 Cisco and/or its affiliates. All rights reserved. 38

 • FabricPath provides design flexibility
New routing and services deployment options
• FabricPath is simple, keeps the attractive aspects of Layer 2 without Spanning Tree
Transparent to L3 protocols
No addressing, simple configuration and deployment
• FabricPath is efficient
High bi-sectional bandwidth (ECMP)
Optimal path between any two nodes
• FabricPath is scalable
Can extend a bridged domain without extending the risks generally associated to Layer 2
(frame routing, TTL, RPFC)

© 2013 Cisco and/or its affiliates. All rights reserved. 39

 Recommended Reading & Links For Your
Reference

Useful Links:
http://www.cisco.com/en/US/products/ps10281/products_installation_and_configuration_guides_list.html
http://www.cisco.com/en/US/netsol/ns944/networking_solutions_white_papers_list.html
https://supportforums.cisco.com/community/netpro/data-center/unified-computing?view=documents
https://supportforums.cisco.com/community/netpro/data-center/unified-computing?view=video

© 2013 Cisco and/or its affiliates. All rights reserved. 40

 • Next Webinar: Thurs. April 11th
Topic Date Presenter
Introduction to SAN Apr 11th Ozden Karakok
Boot from SAN and iSCSI Basics Apr 18th Ganesh Kumar
Introduction to iSCSI Apr 25th Chetan Parik

• Keep checking the Cisco Learning Network site for new sessions
https://learningnetwork.cisco.com/docs/DOC-16438

© 2013 Cisco and/or its affiliates. All rights reserved. 41

• Once you exit the session, your
survey will open in your browser.

• How can we make these Webinars

better?

• What topics do you want to see?

• Complete the quick survey for your

chance to win a free E-book from
Cisco Press.

Congratulations to last weeks

winners!

© 2013 Cisco and/or its affiliates. All rights reserved. 42

Thank you.