Advance VPLS Technology Atachements Options
Advance VPLS Technology Atachements Options
Advance VPLS Technology Atachements Options
Session BRKRST-2008
Patrice Bellagamba
Distinguished System Engineer
Cisco Europe
Problem statement
Problem to solve:
Ethernet service Attachment-Circuit redundancy should not imply
end to end Spanning-tree usage
STP is struggling with
- Topology diameter
- Ethernet Services
Presentation_ID
Cisco Public
Multi-chassis LAG
Simple solution for spoke-and-hub topology, works for both bridging and nonbridging access device
Standard based solution by using 802.3ad
Sub-second convergence
Phase 1 implement is active/standby mode.
Phase 2 is per VLAN load balancing
Ring topology support is under investigation
MST/PVST access
gateway
Node clustering
Presentation_ID
Cisco Public
L2VPN
Transport
Enabler
Access
Redundancy
ICCP based
Protocol / Feature
E-LINE
VPWS
E-LAN
VPLS
E-LAN
H-VPLS
DCI
VPLS
CPE service
mLACP or pseudo-mLACP
DCI
EVPN
PE service
mLACP + BGP
Dont be scared of all acronyms, they will be explained along the presentation
Presentation_ID
Cisco Public
RG
Presentation_ID
Cisco Public
7
Presentation_ID
Cisco Public
RG
/32 IP Route-watch
RG
Presentation_ID
Cisco Public
Port attributes:
-Port key: defines which ports can be bundled together (per node significance)
-Port priority: specifies which ports have precedence to join a bundle when the
candidate ports exceed the Maximum Links per Bundle value
-Port number: uniquely identifies a port in the switch (per node significance)
Key: 10
System Priority: 3
System MAC: M2
Key: 35
Presentation_ID
Key: 10
Port #: 1, Priority: 10
Port #: 2, Priority: 11
Agg3
Agg1
Agg4
Agg2
Port #: 3, Priority: 5
Port #: 4, Priority:
6
Cisco Public
2011 Cisco and/or its affiliates. All rights reserved.
System Priority: 5
System MAC: M1
Key: 20
11
Every PoA in the RG is configured with a unique Node ID (value 0 to 7). Node
ID + 8 forms the most significant nibble of the Port Number
For a given bundle, all links on the same PoA must have the same Port Priority
PoA = Point of Aggregation
DHD = Dual-Homed-Device
Port #: 0x9001, Port Priority 1
PoA1
Node ID: 1
DHD
System MAC:
aaaa.bbbb.cccc
ICCP
System Priority: 1
Node ID: 2
LACP
Presentation_ID
PoA2
Port #:0xA001, Port Priority 2
Cisco Public
12
Operational Variants
PoA-Based Control
Max Links per
Bundle: L
Standby PoA
L=2
DHD
ICCP
LACP
Active PoA
Cisco Public
14
DHD
D
E
Active PoA
Presentation_ID
Cisco Public
15
Failover Operation
Standby PoA
Port/Link Failures
3. LACP Exchanges
DHD
ICCP
C
Active PoA
Step 1 For port/link failures (A,B,C), active PoA evaluates number of surviving in bundle:
If >= M, then no action
If < M, then trigger failover to standby PoA
Step 4 Standby PoA and DHD bring up standby links per regular LACP procedures
Presentation_ID
Cisco Public
16
2. LACP Exchanges
Standby PoA
Failover Operation
Node Failure
DHD
ICCP
D
Active PoA
Step 1A Standby PoA detects failure of Active PoA via one of:
-IP Route-watch: loss of IP routing adjacency
-BFD: loss of BFD keepalives
Step 1B DHD detects failure of all its uplinks to previously active PoA
Step 2 Both Standby PoA and DHD activate their Standby links per
regular LACP procedures
Presentation_ID
Cisco Public
17
3. LACP Exchanges
Standby PoA
Failover Operation
PoA Isolation from Core
DHD
ICCP
2B. Dynamic Port
Priority or Bruteforce failover
E
Active PoA
Step 1 Active PoA detects all designated core interfaces are down
interchassis group 21
backbone interface TenGigabitEthernet4/1
backbone interface TenGigabitEthernet1/4
Step 2A Active PoA signals standby PoA over ICCP to trigger failover
Step 2B Active PoA uses either Dynamic Port Priority or Brute-force
Mechanism to signal DHD of failover
Step 3 Standby PoA and DHD bring up standby links per regular
LACP procedures
Presentation_ID
Cisco Public
18
VPLS
Events
PW - PseudoWire
VFI Virtual Forwarding Instance
VFI
A
FA
2
1A
ICCP
ICCP
LACP
4
LACP
1A
1B
Failover triggered on
DHD
VFI
VFI
FA-C
A
FB
Initial state
VFI
A
FC
1B
Cisco Public
Forwarding EoMPLS PW
Non-Forwarding EoMPLS
20 PW
VPLS
Events
VFI
A
End State
FB
VFI
A
FC
FA
ICCP
ICCP
LACP
VFI
Presentation_ID
LACP
VFI
Cisco Public
Forwarding EoMPLS PW
Non-Forwarding EoMPLS
21 PW
PW 2
<IP1, VCID1>
PE1
PW 1
<IP2, VCID2>
Cisco Public
23
MPLS
CE
PW 1
uPE1
PW 3
PW 2
uPE2
uPE3
PW 4
uPE4
Presentation_ID
Cisco Public
24
PW
PE1
PE2
RFC 4447
draft-ietf-pwe3-redundancy-bit
Cisco Public
25
PW
PE1
A PW is considered as backup if
it is declared as Backup by either
local or remote PE
PE1
PE1
PE1
Presentation_ID
Cisco Public
Active
Active
Active
PE2
Standby
PE2
Standby
Standby
PE2
Standby
Active
PE2
26
Active
Active
Active
Standby
Standby
Standby
Cisco Public
Active
Active
Active
Standby
Active
Active
VPWS
Events
I
AS
FC
FB
1A
FA
LACP
ICCP
ICCP
1B
2
4
SA
LACP
Initial state
FA-C
1A
1B
Failover triggered on
DHD
Active PoA
advertises Standby
state on its PWs
Standby PoA
advertises Active
state on its PWs
Cisco Public
Forwarding EoMPLS PW
Non-Forwarding EoMPLS
28 PW
VPWS
Events
I
FC
FB
FA
LACP
ICCP
ICCP
LACP
Presentation_ID
FA-C
1A
1B
Failover triggered on
DHD
Active PoA
advertises Standby
state on its PWs
Standby PoA
advertises Active
state on its PWs
End State
Initial state
Forwarding EoMPLS PW
Non-Forwarding EoMPLS
29 PW
Implementing MC-LAG
Redundancy
Group
Active POA
DHD
ICCP
redundancy
iccp
group <ig-id>
mlacp node <node id>
mlacp system mac <system mac>
mlacp system priority <sys_prio>
member
neighbor <mpls device>
interface <bundle>
mlacp iccp-group <ig-id>
mlacp port-priority <port prio>
interface <physical interface>
bundle id <bundle id> mode active
Presentation_ID
MPLS
Standby POA
Terminology:
mLACP :
MC-LAG :
DHD :
DHN :
CiscoPOA
Public :
MPLS Core
Active
PE
VFI
VFI
ICCP
MPLS Core
Active
PE
Standby
PE
ASR9Ks as
POAs
VFI
VFI
ICCP
Standby
PE
ASR9Ks as
POAs
Cluster node
as a DHD
Cluster node
as a DHD
LACP Hot-Standby
32
2
1
4
5
8
Si
MPLS
core
Si
Cisco Public
33
CE1
CE2
Active POA
ICCP
CE3
Local Connect
Standby POA
Active POA
CE2
ICCP
CE3
Local Bridging
Standby POA
Local connect service between bundle port and bundle port, or between bundle port and regular port are
configurable. And it works in the normal condition
However, if bundle failover happen, then it wont work. For example, for CE2, if it failover to the bottom
POA, then there is no local connection to CE 1 or CE3
In summary, although you can configure the local connect service for the MC-LAG bundle port, but it
could cause problem. So its not supported
Local
bridging is supported
there
L2 link between
Presentation_ID
Cisco Public two POA
2011 Ciscoassume
and/or its affiliates.
All rightsis
reserved.
34
ASBR3
ASBR1
VFI
VFI
VFI
AS2
AS1
VFI
VFI
VFI
VPLS or H-VPLS
ASBR2
Link bundle
ASBR4
VPLS or H-VPLS
From each pair of ASBR point of view, the other side is just a single virtual LACP device
Pros:
o Simple configuration which provide both link and node redundancy
o Advantage of option A: Flexible per interface/sub-interface features: QoS, MAC limit, ACL, etc
o Convergence time is fast: sub-second for both link and node failures
Cons:
o Bundle is in active/standby mode, 50% usage of the inter-AS link bandwidth
o Need manual configuration to inter-connect different VPLS VFIs
o limited to be 4K L2 sub-interfaces per bundle port
o ASBR link has to be Ethernet
Presentation_ID
Cisco Public
35
BD
BVI
Active POA
LACP
ICCP
MPLS/IP
Recommanded Option:
DHD can run IGP with both POA. Routing
session will be up with both POAs
Bundle/POA failover wont cause
the L3 topology change
BD
Standby POA
BVI
Configure L2 sub-interface on the bundle, and then configure L2 PW between two POA. Both L2 subinterface and L2 PW are in the same bridge-domain. Configure IRB/BVI for the bridge-domain for the L3
service
L3 features like HSRP, VRRP, routing, etc could be configured under BVI interface
BVI interfaces are up on both POA regardless of the bundle status
Bundle failover only impact the bundle itself. BVI and related L3 topology is not aware fast L3
convergence
Presentation_ID
Cisco Public
2011 Cisco and/or its affiliates. All rights reserved.
36
Feature
Cisco
Catalyst
3750-ME
One-Way PW Redundancy
Cisco
7600
Cisco
ASR 9000
Two-Way PW Redundancy
mLACP
ICCP
LACP
Cisco ME
Cisco ASR
3600X / 3800X 901/903
Presentation_ID
Cisco Public
37
Pseudo mLACP
Presentation_ID
Cisco Public
39
Pseudo-LACP application on PoAs ensure that two port-channels on DHD will get bundled to one
logical port-channel on PoA
DHD
POA1
ICCP
Aggregation / Core
Presentation_ID
Cisco Public
POA2
40
DHD
ICCP
DHN
Presentation_ID
41
Traffic path
DHD
Cisco Public
42
Traffic path
DHD
Cisco Public
43
interface TenGigabitEthernet2/3
channel-group 2 mode active link 1
interface Port-channel2
port-channel load-balance link 1
service-instance 4021
!
service instance 4021 ethernet
description ### VDC-2 VLANs ###
EFP
Presentation_ID
Cisco Public
44
DHD
N
C
A
B
ICCP
D = 7600 crash
E = MPLS link failure
Cisco Public
45
Mr
Ml
Mr
Ml
Mr
Ml
ICCP
Mr
Mr
LAG
PW
Forwarding
Blocking
Presentation_ID
Cisco Public
Mr
Ml
Mr
Mr
Ml
Ml
Mr
ICCP
Mr
Ml
Mr
Mr
Ml
LAG
Mr
PW
Forwarding
Blocking
Presentation_ID
Cisco Public
Ml
Mr
Mr
Ml
Ml
Mr
ICCP
Mr
Ml
Mr
Mr
Ml
LAG
PW
Forwarding
No MVRP
Requires to flap port-channel,
Blocking
Presentation_ID
Mr
Cisco Public
Reversion
trigger
Manual
procedure
48
Reversion procedure
scripted for easiness
event manager applet Revert_po2
event none
action 1.0 cli command "en"
Presentation_ID
Cisco Public
49
Traffic
Down
Up
Traffic
Down
Up
DHD link
shut
0.5s-1s
1.5s
<0.1s
1.8s
7600 link
shut
0.8s
1.8s
<0.1s
1.8s
7600
crash
0.8s
1.7s
0.8s
1.7s
MPLS link
down
0.1s
<0.1s
0.1s
<0.1s
DHD crash
0.3s
<0.1s
0.3s
<0.1s
Comment
HW and SW considerations
Supported today by Cisco 7600 with following HW:
- Access linecard: ES+ and ES-20 (Core linecard: Any)
- SUP-720 and RSP-720
Cisco Public
51
ICCP
ICCP
Presentation_ID
52
Presentation_ID
Cisco Public
53
SSO considerations
Presentation_ID
Cisco Public
54
Sample Configuration
PE1 Configuration
PE2 Configuration
redundancy
redundancy
member ip 2.2.2.2
member ip 1.1.1.1
mlacp node-id 1
mlacp node-id 2
Prim: 4041
Sec: 4042
PE-1 (POA1)
1.1.1.1
Gig2/20
Gig2/21
mLACP-AA
ICCP
Redundancy
Group 100
Gig1/12
DHD
Gig1/11
Prim: 4042
Sec: 4041
Presentation_ID
PE-2 (POA2)
2.2.2.2
Cisco Public
55
PE2 Configuration
interface Port-channel34
interface Port-channel34
no ip address
no ip address
description vpls_coupled
description vpls_coupled
bridge-domain 4041
bridge-domain 4041
description vpls_decoupled
description vpls_decoupled
bridge-domain 4042
bridge-domain 4042
(*) Configuration
required if EVC cross
connect or PBB is used on the P-mLACP Cisco
port-channel
Presentation_ID
Public
2011 Cisco and/or its affiliates. All rights reserved.
56
Debugging/Troubleshooting
Show commands
Presentation_ID
Cisco Public
57
Show Commands
Checking ICCP connectivity
PE1#show redundancy interchassis
Redundancy Group 100 (0x64)
Applications connected: mLACP, Pseudo-mLACP, DHCP Snooping
Monitor mode: BFD
member ip: 2.2.2.2 "PE2", CONNECTED
BFD neighbor: GigabitEthernet2/9, next hop 192.168.41.2, UP
mLACP state: CONNECTED
Pseudo-mLACP state: CONNECTED
Interface
==========
=========
2.2.2.2
UP
GigabitEthernet2/9
Presentation_ID
BFD
192.168.41.2
Cisco Public
58
Show Commands
Checking P-mLACP state
PE1#show lacp multi-chassis load-balance port-channel 34
Interface Port-Channel 34
Local Configuration:
P-mLACP Enabled:
Yes
Redundancy Group:
100
Revertive Mode:
Revertive
Primary VLANs:
4041
Secondary VLANs:
4042
Local Interface State:
Interface ID: 34
Port State:
Up
Primary VLAN State:
Active
Secondary VLAN State: Standby
Peer Interface State:
Interface ID: 34
Primary VLAN State:
Active
Secondary VLAN State: Standby
Presentation_ID
/* Node failure */
/* A/B/C failure */
/* Core failure */ 59
Debugging/Troubleshooting
SP Debugging commands
-
RP Debugging commands
-
Cisco Public
60
Service Multi-Homing
Building blocks
IP/Service Edge
IP/MPLS
L2 Ethernet Ring
(MST/REP-AG,
G.8032)
Ethernet spokeand-hub
(MC-LAG)
Presentation_ID
Cisco Public
61
Home
Cluster
ASR 9000
Distribution
High Availability
BNG
Aggregation
(MPLS)
Core
BNG
ASR 9000
Virtual Cluster
Satellite
Home
BNG
Aggregation
(MPLS)
Core
BNG
Presentation_ID
Cisco Public
62
Presentation_ID
Cisco Public
63
Thank you.
Presentation_ID
Cisco Public
64