Advance VPLS Technology Atachements Options

8/19/2019 Advance VPLS Technology Atachements Options

1/62

Session BRKRST-2008

Advanced VPLS attachment technology options

Patrice Bellagamba

Distinguished System Engineer

Cisco Europe

https://www.ciscolivelondon.com/content/sessionDetail.do?SESSION_ID=3027https://www.ciscolivelondon.com/content/sessionDetail.do?SESSION_ID=3027https://www.ciscolivelondon.com/content/sessionDetail.do?SESSION_ID=3027https://www.ciscolivelondon.com/content/sessionDetail.do?SESSION_ID=3027


2/62

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

Problem statement

Problem to solve:

“Ethernet service Attachment -Circuit redundancy should not implyend to end Spanning-tree usage”

STP is struggling with

- Topology diameter

- Fault isolation between sites

- Resilience to WAN type connections

Position Architecture: STP domain isolation thru dual homing

- Carrier-Ethernet

- Data-Center Interconnect

- Ethernet Services


3/62


Access Multi-homing Solutions Summary

Highlights

Multi-chassis LAG Simple solution for spoke-and-hub topology, works for both bridging and non-bridging 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

REP /REP accessgateway

Sub 200msec convergence

Good access ring isolation

Now standard based G.8032 (XR4.1 release)

Spoke-and-hub and ring topology, not works well for mesh network

MST/PVST accessgateway

Standard based solution as long as access network support MST/PVST

Works for any access network topology

Good access domain isolationWork with 802.1ah PBB

Convergence time depends on access network STP

Node clustering VSS (Catalyst / Cisco 7600-Sup2T)Nv cluster (ASR9k)

One control-plane for two chassis

Easiness, Active/Active


4/62


L2 node peering solutions

Making usage of an “Inter -Chassis Communication Protocol”

Service TypeL2VPN

TransportEnabler

AccessRedundancy

ICCP basedProtocol / Feature

E-LINE VPWSHub and Spoke

(Active / Backup)mLACP + 2-way PW Red.

(coupled mode)

E-LAN VPLS Hub and Spoke(Active / Backup)

mLACP + 2-way PW Red.(decoupled mode)

E-LAN H-VPLSHub and Spoke

(Active / Backup)mLACP + 2-way PW Red.

(decoupled mode)

DCI VPLS CPE service mLACP or pseudo-mLACP

DCI EVPN PE service mLACP + BGP

Don’t be scared of all acronyms, they will be explained along the presentation


5/62

Inter-Chassis Communication Protocol for L2VPN PERedundancy (ICCP)

draft-martini-pwe3-iccp-06


6/62


Inter-Chassis Communication Protocol

ICCP allows two or more devices to form a„Redundancy Group‟

ICCP provides a control channel forsynchronizing state between devices

ICCP uses TCP/IP as the underlyingtransport

-ICCP rides on targeted LDP session, butMPLS need not be enabled

Various redundancy applications canuse ICCP:

-mLACP

-Pseudowire redundancy

Under standardization in IETF:-draft-ietf-pwe3-iccp-06.txt

RG

ICCP over Dedicated Link

RG

ICCP over Shared Network


7/62© 2011 Cisco and/or its affiliates. All rights reserved. Cisco PublicPresentation_ID 7

7

Inter-Chassis Communication Protocoldraft-ietf-pwe3-iccp-06.txt

• ICC Protocol Transport Requirements

–Reliable Message exchange

–In-order Delivery

–Sequence Numbers

–Timeouts/Retransmissions

use widely deployed LDP protocol.

• Extend LDP with a small set of new messages:

–RG Connect Message

–RG Disconnect Message

–RG Notification Message

–RG Application Data Message

• Use LDP Capability to bootstrap ICCP.

• Application layer specific TLVs.



8

Node Failure Detection

Two mechanisms:

• BFD – Bi-Directional Forward Detection

• Detection upon loss of BFD keepalives

• Requires nodes to be co-located, with a direct link connection

• No split-brain protection, mandates link to be port-channel

dispatched over two different line cards

• /32 IP Route-watch

• Detection upon loss of IP routing adjacency

• Geo localization of nodes

• Split-brain tie-break via MPLS network

• Depends on IGP timersOSPF/ISIS fast convergence tuning is required

• Ensure not to have less specific route for detection to work

• “ip routing protocol purge interface”

This is requiring to avoid route-watch flapping on peer link

failure

Default in IOS-XR & IOS Rls15

RG

ICCP over Dedicated Link

RG

ICCP over Shared Network


9/62

Multi-Chassis Link Aggregation Group(ASR 9K - MC-LAG)

&

Multi-Chassis Link Aggregation control Protocol(Cisco 7600 - mLACP)



Background: Link Aggregation Control Protocol

System attributes:-System MAC address: MAC address that uniquely identifies the switch

-System priority: determines which switch‟s Port Priority values win Aggregator (bundle) attributes:

- Aggregator key: identifies a bundle within a switch (per node significance)

-Maximum links per bundle: maximum number of forwarding links in bundle – usedfor Hot Standby configuration

-Minimum links per bundle: minimum number of forwarding links in bundle, when

threshold is crossed the bundle is disabled

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 thecandidate ports exceed the Maximum Links per Bundle value

-Port number : uniquely identifies a port in the switch (per node significance)

Agg1

Agg2

Agg3

Agg4

Port #: 1, Priority: 10

Port #: 2, Priority: 11

Port #: 3, Priority: 5Port #: 4, Priority: 6

Key: 10

Key: 20

Key: 10

Key: 35

System Priority: 5

System MAC: M1

System Priority: 3

System MAC: M2



Extending LACP Across Multi-Chassis: mLACP

mLACP uses ICCP to synchronize LACP configuration & operational state

between PoAs, to provide DHD the perception of being connected to a singleswitch

All PoAs use the same System MAC Address & System Priority whencommunicating with DHD

-Configurable or automatically synchronized via ICCP

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

ICCP

DHD = Dual-Homed-Device

PoA1

LACPPoA2

Node ID: 1

Node ID: 2

Port #: 0x9001, Port Priority 1

Port #:0xA001, Port Priority 2

System MAC:

aaaa.bbbb.cccc

System Priority: 1

PoA = Point of Aggregation

DHD



Operational Variants

Each PoA is configured to limit themaximum number of links per bundle

-Limit must be set to L, where L is the minimumnumber of links from DHD to any single PoA

DHD max link should be set > L

- In order to insure that it is slave of the POA- This will allow faster convergence

Selection of active/standby links is theresponsibility of the PoAs

Advantages: Faster switchover times

compared to other variants, and MinimumLink policy on PoA can be flexible

Disadvantage: If ICCP transport is lost,Split Brain condition could occur

PoA-Based Control

ICCPDHD

Standby PoA

Active PoALACP

Max Links per

Bundle: L

L = 2

Max Links per

Bundle: L

This is the most used variant



Protected Failure Points

mLACP Offers Protection Against 5 Failure Points:

A: DHD Port Failure

B: DHD Uplink Failure

C: Active PoA Port Failure

D: Active PoA Node Failure

E: Active PoA Isolation from Core Network

A B CD

E

Active PoA

DHD

Standby PoA



Failover Operation

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 2 – Active PoA signals failover to standby PoA over ICCP

Step 3 – Failover is triggered on DHD by one of:Dynamic Port Priority Mechanism: real-time change of LACP Port Priority on active PoA to cause the standbyPoA links to gain precedence

Links are either Hot-Standby or Up

Brute-force Mechanism: change the state of the surviving links on active PoA to admin down

Links are either Err-disabled or Up

Step 4 – Standby PoA and DHD bring up standby links per regular LACP procedures

Port/Link Failures

ICCPDHD

Standby PoA

Active PoA

• Max Links per

Bundle: L (=2)

• Min Links per

Bundle: M (=2)

A B

C

2. Signal failover over

ICCP

3. Dynamic Port Priority

or Brute-force failover

3. LACP Exchanges



Failover Operation

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 perregular LACP procedures

Node Failure ICCPDHD

Standby PoA

Active PoA

1A. IP Route-

Watch or BFD

timeout

D1B. Links Down

2. LACP Exchanges



Failover Operation

Step 1 – Active PoA detects all designated core interfaces are downinterchassis group 21backbone interface TenGigabitEthernet4/1backbone interface TenGigabitEthernet1/4

Really useful if no direct connection between POA or using one onlymodule toward core

Step 2A – Active PoA signals standby PoA over ICCP to trigger failover

Step 2B – Active PoA uses either Dynamic Port Priority or Brute-forceMechanism to signal DHD of failover

Step 3 – Standby PoA and DHD bring up standby links per regularLACP procedures

PoA Isolation from Core ICCPDHD

Standby PoA

Active PoA

E

1. Detect coreisolation

2A. Signal failover

over ICCP

2B. Dynamic Port

Priority or Brute-

force failover

3. LACP Exchanges


17/62

Works similarly with H-VPLS (MPLS Access)

E-LAN Availability ModelsActive/Backup Access Node Redundancy (mLACP)



E-LAN availability model Active / Backup Access Node Redundancy (mLACP)

VFI

VFI

A A

A A

A

A

A

A

LACPICCP ICCP

For VPLS Decoupled Mode, VFI‟s PWs alwaysadvertised in Active state, regardless of AC state

VFI

VFI

Forwarding EoMPLS PW Non-Forwarding EoMPLS PW

FA

FB

FC

LACP

EventsI Initial state

FA-C Port / Link Failures

2 Standby link broughtup per LACP proc.

Port / Link Failures

1B

2

1A1B

Failover triggered onDHD

1A

Active PoA detectsfailure and signalsfailover over ICCP

3

Standby PoA flushes

MAC table andtriggers LDP MACadd. withdrawal toremote peers

4 Remote PEs flushMAC addresses

3

4 4

4

VPLS

PW - PseudoWire

VFI – Virtual Forwarding Instance



E-LAN availability model Active / Backup Access Node Redundancy (mLACP)

VFI

VFI

A A

A A

A

A

A

A

LACPICCP

VFI

VFI


FA

FB

FC

LACP

Events Port / Link Failures (cont.)

E End State

ICCP

VPLS

4 Remote PEs flushMAC addresses


20/62

E-LINE Availability ModelsActive/Backup Access Node Redundancy (mLACP)


21/62


Pseudowire Redundancy with LDP

Designate Pseudowires as either primary or backup-Primary Pseudowire used for traffic forwarding, and backuptakes over in case of failure

Signaling Redundant Pseudowires in targetedLDP session

-Cold Redundancy: Backup PWs were not signaled untilrequired to take over

-Warm Redundancy: Backup PWs were signaled up in thecontrol-plane but held down in the data-plane. Use AC Faultcode-point in LDP Status Message to indicate a backup PW

-Hot Redundancy: Use PW Preferential Forwarding Status Bits

Background

PW 2

PW 1

MPLS

PE1

CE


22/62


Two-Way Pseudowire Redundancy

Allows dual-homing of two local PEs to two remote PEs

Four pseudowires: 1 primary & 3 backup provide redundancyfor a dual-homed device

Overview

PW 1

MPLS

uPE2

uPE4

uPE1

CE

uPE3PW 2 PW 3

PW 4


23/62


Pseudowire Redundancy with LDP

-0x00000000 - Pseudowire forwarding (clear all failures)

-0x00000001 - Pseudowire Not Forwarding-0x00000002 - Local Attachment Circuit (ingress) Receive Fault

-0x00000004 - Local Attachment Circuit (egress) Transmit Fault

-0x00000008 - Local PSN-facing PW (ingress) Receive Fault

-0x00000010 - Local PSN-facing PW (egress) Transmit Fault

-0x00000020 - PW Forwarding Standby

-0x00000040 – PW Request to go Active

PW Status Signaling

RFC 4447

draft-ietf-pwe3-redundancy-bit

Only this bit is required/used (with help of ICCP)

PW

tLDP

PE1

CE

PE2


24/62



Every PE decides the local statusof the PW: Active or Standby

A PW is selected as primary forforwarding if it is active on both local & remote PEs

A PW is considered as backup ifit is declared as Backup by either local or remote PE

Independent Operation Mode

PW

PE1 PE2

PE1 PE2Active Active

Active Standby

MPLS

PE1 PE2Standby Standby

PE1 PE2Standby Active


25/62



VPWS / H-VPLS – two-waycoupled:

-When AC changes state to Active1,both PWs will advertise Active

-When AC changes state to Standby1,both PWs will advertise Standby

H-VPLS – two-way decoupled:

-Regardless from AC state, PrimaryPW and Backup PWs will advertise

Active state

For H-VPLS, all PWs in VFI (at nPE)are Active simultaneously, for bothaccess & core PWs

Determining Pseudowire State

Active ActiveActive

Standby Standby

Standby

pseudowire-class

encapsulation mpls

status peer topology dual-homed

Active Active

Active

Standby Active

Active

pseudowire-class

encapsulation mpls

status peer topology dual-homed

status decoupled(1) Active / Standby AC states determined for example by mLACP


26/62


E-LINE availability model Active / Backup Access Node Redundancy (mLACP)

S S

A A

LACP LACPICCP ICCP

1A

2

1B

S

3

A

4



1A

Active PoA detectsfailure and signals

failover over ICCP

1BFailover triggered onDHD

2Standby link broughtup per LACP proc.

3

Active PoA

advertises “Standby”state on its PWs

4Standby PoAadvertises “Active”state on its PWs

For VPWS Coupled Mode, attachment circuit (AC) state(Active/Standby) drives PW state advertised to remote peers


Port / Link Failures

VPWS

FA

FB

FC


27/62


LACP

E-LINE availability model Active / Backup Access Node Redundancy (mLACP)

S

A

LACPICCP ICCP

S

A

FA

FB

FC



1A

Active PoA detectsfailure and signals

failover over ICCP

1BFailover triggered onDHD

2Standby link broughtup per LACP proc.

3

Active PoA

advertises “Standby”state on its PWs

4Standby PoAadvertises “Active”state on its PWs

E End State Local site access failure does not trigger LACP

failover at remote site (i.e. control-plane

separation between sites)Forwarding EoMPLS PW Non-Forwarding EoMPLS PW

Port / Link Failures (cont.)

VPWS


28/62

Implementing MC-LAG


29/62


Multi-Chassis LACP synchronization:

LACP BPDUs (01:80:C2:00:00:00) are exchanged on each Link

System Attributes: Priority + bundle MAC Address

Port Attributes: Key + Priority + Number + State

MPLS

Terminology:mLACP : Multi-Chassis Link Aggregation Control Protocol

MC-LAG : Multi-Chassis Link Aggregation Group

DHD : Dual Homed Device (Customer Edge)

DHN : Dual Homed Network (Customer Edge)POA : Point of Attachment (Provider Edge)

Attachment Circuit Using mLACP/MC-LAG

redundancy

iccp

group

mlacp node

mlacp system mac

mlacp system priority

member

neighbor

interface

mlacp iccp-group

mlacp port-priority

interface

bundle id mode active

DHD

Active POA

Standby POA

Redundancy

Group

ICCP


30/62


Active/Standby Deployment Options

ICCPVFI VFI

MPLS Core

Cluster node

as a DHD

ICCPVFI VFI

MPLS Core

Cluster node

as a DHD

LACP Hot-Standby

Active

PE

Standby

PE

Traffic may take sub-optimal path

via the DHD inter chassis link

Optimal path by bundling 4 links in vPC

Direct path exist between each N7K

and active PE

ASR9K‟s as

POA‟s ASR9K‟s as POA‟s

Active

PE

Standby

PE


31/62


SiSi

SiSi

MC-LAG to VPLS Testing http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/DCI/vpls/vpls_asr9k.html

MPLS

core

1

23

4

5

6

7

8

Only error 2/3/4 are leading to ICCP convergence

Rem: 2 & 4 are dual errors

• 500 VLAN Unicast: Link error sub-1s & Node error sub-2s

• 1200 VLAN unicast: Link error sub-2s & Node error sub-4s


32/62


MC-LAG Not-Supported Service ExampleLocal Connect

Local connect service between bundle port and bundle port, or between bundle port and regular port areconfigurable. And it works in the normal condition

However, if bundle failover happen, then it won‟t work. For example, for CE2, if it failover to the bottomPOA, 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 itcould cause problem. So it‟s not supported

Local bridging is supported assume there is L2 link between two POA

ICCP

Standby POA

Active POA

CE1

CE2

CE3

ICCP

Standby POA

Active POA

CE1

CE2

CE3

Local BridgingLocal Connect


33/62


VPLS or H-VPLS

AS2

VFI

VFI

VFI

VFI

ASBR2

ASBR3

ASBR4

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 redundancyo 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

MC-LAG on

both pair of

ASBRs

Link bundle

ASBR1

VPLS or H-VPLS

AS1

VFI

VFI

Inter-AS Option A – Resiliency SolutionsUsing MC-LAG


34/62


MC-LAG & L3 ServiceIRB/BVI, decoupled mode

Configure L2 sub-interface on the bundle, and then configure L2 PW between two POA. Both L2 sub-interface and L2 PW are in the same bridge-domain. Configure IRB/BVI for the bridge-domain for the L3service

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 L3convergence

LACP ICCP

Standby POA

Active POA

MPLS/IP

Recommanded Option:

DHD can run IGP with both POA. Routing

session will be up with both POAs

Bundle/POA failover won‟t cause

the L3 topology change

BD

BD

BVI

BVI


35/62


FeatureCisco

Catalyst3750-ME

Cisco ME3600X / 3800X

Cisco ASR901/903

Cisco7600

CiscoASR 9000

One-Way PW Redundancy X X X X X

Two-Way PW Redundancy X X

LDP MAC AddressWithdrawal

X X

LACP X X X X X

mLACP X X

ICCP X X

mLACP Platform Support


36/62

Pseudo mLACP


37/62


Pseudo MLACP (P-mLACP) concept

P-mLACP provides an Active / Active dual homing redundancymechanism with per-VLAN load balancing

- higher bandwidth utilization

Backup time does not require link state changes

- Improve scale and convergence time

Supports today Dual Homed Device (DHD)

- Will support Dual Homed Network (DHN) in future

New extensions to Inter-Chassis Communication Protocol (ICCP) used

for communication to control the failover process

Available in Cisco 7600 with 15.1(3)S release

- ES / ES+ linecards


38/62


39/62


Attachment Circuit options

DHD

ICCP

DHD

ICCP

DHN

Mono-Device Dual Homed Device(DHD)

Multi-Devices Dual Homed Device (DHD)

The one analyzed in this presentation

Dual Homed Network (DHN)• 7600 do support MVRP

• But not officially supported as it would

require DHN to support MVRP to flush

local MAC

• 4K VLAN Scale (no multi-chassis

etherchannel)

Traffic path


40/62


Traffic path

DHD

Per VLAN group balancing over Etherchannel

Traffic path


41/62


Traffic path

DHD

With VPLS, on the ES+ facing edge card

EVC load balancing over lacp bundle is only on per EFP

With one EFP per VLAN, repartition is OK

If one EFP for all VLAN, then no balancing


42/62


EFP static load repartition over bundle

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 ###

encapsulation dot1q 400,1000-1999

bridge-domain 4021

Optional, but useful to control

which link is primary

EFP


43/62


Active path failures

DHD

ICCP

AB

CD E

A = Nexus port failure (shut)

B = Attachment-Circuit failure

C = Dual AC failure

D = 7600 crash

E = MPLS link failureN= DHD member crash

N

F il diti d MAC fl h id ti


44/62


Failure condition and MAC flush considerationMAC learning on nominal mode

Mr

LAG PWForwarding

Ml

Ml

Ml

Mr

Mr

Assuming no VLAN repartition

ICCP

Blocking

Mr

Mr



45/62


Failure condition and MAC flush considerationMAC learning on PE failure

Mr

LAG PWForwarding

Blocking

Ml

Ml

Ml

Mr

Mr

Mr

Mr

Assuming no VLAN repartition

ICCP

Mr

Mr

Mr

Ml

Ml



46/62


Failure condition and MAC flush considerationMAC learning on PE up time

Mr

LAG PWForwarding

Ml

Ml

Ml

Mr

Mr

Due to lack of per VLAN MVRP, second path VLAN may be affected during recovery

Manual trigger is prefered

ICCP

Blocking

Mr

Mr

Mr

Mr

Mr

Ml

Ml

Reversion

trigger

-

Manual

procedure

No MVRP

Requires to flap port-channel,

R i d


47/62


Reversion procedurescripted for easiness

event manager applet Revert_po2

event none

action 1.0 cli command en

action 1.1 cli command conf t

action 2.0 cli command int po2

action 2.1 cli command shut

action 2.2 cli command no shut

action 2.3 cli command end

action 3.0 syslog msg Preemption requested for port-channel “

alias exec Revert_po2 event manager run Revert_po2


48/62

Active path failures measurement

Failure type Traffic

Down Up

Traffic

Down Up

Comment

A DHD link

shut

0.5s-1s 1.5s


49/62


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

Supported on port-channel with service instances (evc-based port-channel)

- EFP with bridge-domain and SVI for VPLS uplinks

- EFP with xconnect (PoA with EoMPLS uplinks – VPWS and H-VPLS spoke)

- EFP with C-MAC bridge-domain (PoA with native 802.1ah Ethernet uplinks)

PBB configurations support only one (1) member link per PoA in mLACP/P-mLACP port-channels

- EFP with C-MAC bridge-domain with SVI for VPLS uplinks

Supported by Cisco 7600 starting with IOS 15.1(3)S

Planned support with ASR9K


50/62


P-mLACP Configuration Guidelines / Restrictions

Only one Port-channel of type „mLACP or pmLACP‟ is supported on a single

RG. There can be one mLACP port-channel and one more pmLACP port-channel on a single RG, but not two Port-channel of same type.

Bridge-domain associated to P-mLACP port-channel should not be part of anyother non P-mLACP interfaces

ICCP ICCP

Working in normal mode Blocking in failure mode !

Not supported

Fo a given Bridge-domain (SVI)


51/62


P-mLACP Configuration Guidelines / Restrictions

DHCP / IGMP snooping state synchronization over ICCP is supported from 15.2S

Routed PW will not be supported in Core

Connectivity Fault Management (CFM) maintenance points (MEP/MIP) notsupported on P-mLACP port-channel

- CFM Port MEP (untagged CFM) can be configured under port-channel member

Link OAM can be configured under port-channel members

Recommended configuration sequence:

- Configure “interchassis group”

- Configure port-channel interface

- Configure port-channel memberlinks

Any Out-Of-Sequence Configuration may need flapping of the Port-Channel to ensureproper pmLACP functionality


52/62


SSO considerations

Pseudo-mLACP is supporting SSO- With LDP graceful

Software crash protected gracefully

But manual command “redundancy force-switchover”

- Is subject to timing constraints and could lead tomedium term blackout

- Under investigation

- Recommendation is to preventively swap traffic toalternate node


53/62


PE1 Configuration

redundancy

interchassis group 100

monitor peer bfd

member ip 2.2.2.2

backbone interface GigabitEthernet2/21

mlacp node-id 1

PE2 Configuration

redundancy

interchassis group 100

monitor peer bfd

member ip 1.1.1.1

backbone interface GigabitEthernet1/12

mlacp node-id 2

Sample Configuration

DHD

PE-1 (POA1)

1.1.1.1

ICCPmLACP-AA

PE-2 (POA2)

2.2.2.2

Redundancy

Group 100

Gig2/20

Gig1/11

Prim: 4041

Sec: 4042

Prim: 4042

Sec: 4041

Gig2/21

Gig1/12


54/62


Sample Configuration (cont.)

PE1 Configurationinterface Port-channel34

no ip address

mlacp interchassis group 100

mlacp mode active-active

mlacp load-balance primary vlan 4041

mlacp load-balance secondary vlan 4042

ethernet vlan color-block all*service instance 888 ethernet

description vpls_coupled

encapsulation dot1q 4041

rewrite ingress tag pop 1 symmetric

bridge-domain 4041

!


description vpls_decoupled



bridge-domain 4042

PE2 Configurationinterface Port-channel34

no ip address

mlacp interchassis group 100

mlacp mode active-active

mlacp load-balance primary vlan 4042

mlacp load-balance secondary vlan 4041

ethernet vlan color-block all*service instance 888 ethernet

description vpls_coupled



bridge-domain 4041

!


description vpls_decoupled



bridge-domain 4042

(*) Configuration required if EVC cross connect or PBB is used on the P-mLACP port-channel


55/62


Debugging/Troubleshooting

Show commands

show lacp multi-chassis group

show lacp multi-chassis port-channel

show lacp multi-chassis load-balance group

show lacp multi-chassis load-balance port-channel show lacp internal

show lacp neighbor

show etherchannel [id] [detail | port | port-channel | summary]

show redundancy interchassis

show mpls ldp iccp


56/62


57/62


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: 4041Secondary 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

Show Commands

Fail flags (bitfield):

MLACP_FAIL_PEER = 0x1, /* Node failure */

MLACP_FAIL_MIN_LINK = 0x2, /* A/B/C failure */MLACP_FAIL_CORE = 0x4, /* Core failure */


58/62


Debugging/Troubleshooting

SP Debugging commands

- debug lacp load-balance- debug lacp load-balance vlan

- debug lacp load-balance database

- debug lacp load-balance redundancy-group

- debug lacp load-balance all

- debug redundancy interchassis [all | application | error | event | monitor]

- debug ethernet service instance error

- debug ethernet service instance xdr- debug ethernet service instance event

- debug mvrp all

- debug mvrp error

- debug mvrp packet

- debug mvrp verbose

RP Debugging commands- debug lacp load-balance vlan

- debug lacp load-balance database

- debug redundancy interchassis [all | application | error | event | monitor]

- debug mpls ldp iccp

- debug ethernet service error

- debug ethernet service api


59/62


Ethernet spoke-and-hub(MC-LAG)

L2 Ethernet Ring

(MST/REP-AG,G.8032)

IP/Service Edge

IP/MPLS

L3 Router dual-homing (L3 ECMP)

Service Multi-Homing

Building blocks

Point to point L2 Service PW redundancy Multi-point L2 Service MC-LAG

Changing the Redundancy Paradigm


60/62


g g y g

Virtual Cluster and Satellite for BNG

Home

Aggregation

(MPLS)

Cluster ASR 9000

Distribution

Home

Cluster & Satellite

Core

BNG

BNG

ASR 9000

VirtualCluster

BNG

BNG

ASR 9000Virtual Cluster

Satellite

Aggregation

(MPLS)

ASR 9000

Distribution

Core

• Geo Redundant Dual Homing

• High Availability

• Single-Chassis-like look&feel and

Management of cluster Members

• Stateful Failover between chassis

• Active/active LAG user facing

+• Huge 1GE Fan-out

• Satellites appear like ASR 9000

Linecards

• Simplified topology, No Spanning

tree or other L2 redundancy

protocols needed


61/62


Complete Your Online Session Evaluation

Give us your feedback andyou could win fabulous prizes. Winnersannounced daily

Receive 20 Cisco Preferred Access pointsfor each session evaluation you complete

Complete your session evaluation onlinenow (open a browser through our wirelessnetwork to access our portal) or visit oneof the Internet stations throughout theConvention Center

Don‟t forget to activate your Cisco Live

and Networkers Virtual account for access

to all session materials, communities, and

on-demand and live activities throughout

the year. Activate your account at any internet station

or visit www.ciscolivevirtual.com.

http://www.ciscolivevirtual.com/http://www.ciscolivevirtual.com/http://www.ciscolivevirtual.com/


62/62

Thank you.

Documents

Advance VPLS Technology Atachements Options