l2vpn ios-xr and customer deployments

PE-2 Pleasanthill config – 1 l2vpn xconnect group Customer_A p2p VLAN interface GigabitEthernet0/1/0/1.15 neighbor 5.0.0.5 pw-id 200 pw-static-label local 321 remote 123 transport-mode v

ƒ We value your feedback, don’t forget to complete your online session

evaluations after each session and complete the Overall Conference

Evaluation which will be available online from Friday

ƒ Visit the World of Solutions on Level -01!

ƒ Please remember this is a ‘No Smoking’ venue!

ƒ Please switch off your mobile phones!

ƒ Please remember to wear your badge at all times including the Party!

ƒ Do you have a question? Feel free to ask them during the Q&A section or write your question on the Question form given to you and hand it to the

Room Monitor when you see them holding up the Q&A sign.

HOUSEKEEPING

My Background

ƒ Sami Boutros is the Architect Technical Leader in the IOS-XR

development routing group responsible for L2VPN and MPLS

ƒ In deploying and operating a Next Generation Network (NGN), service providers will expect high-levels of reliability and scale IOS-XR is a modular, scalable router OS and with built-in carrier class availability and scale Providers will first deploy IOS-XR-based elements (e.g

CRS-1) beginning first in the core, proceeding out to the edge with

L3VPN and L2VPN This aligns with provider’s stated strategy of

moving to converged packet network

ƒ This presentation will detail IOS-XR L2VPN design, troubleshooting, customer deployments, and Futures

Objective

1 L2VPN/EoMPLS Overview

2 L2VPN IOS-XR implementation Overview

3 L2VPN IOS-XR Customer Deployments

4 Futures of L2VPN IOS-XR

5 References

Agenda

ƒ Differentiators vis-à-vis IOS and competition:

XR ISSU/HA, enhanced CLI, RFC4447 Compliance, AC scale, futures platform

L2VPN and EoMPLS

Overview

PSN Tunnel

Customer Site

(PE) devices which connects two pseudo-wire end-services

(PWESs) of the same type

Pseudo Wire Reference Model

PE PE

Customer

Site

Customer Site Pseudo Wires

PE PE

to transport PW PDU from PE to PE using tunnel labels

to exchange VC information, such as VC labels and control information

TUNNEL LSP

TUNNEL LSP DIRECTED LDP

Customer

Site

Customer Site

Customer

Site

Customer Site

VC Label Tunnel Label

AToM – Label Distribution & Usage

Customer Site A2

Customer Site B2

Interface GigabitEthernet 0/1/0/0

l2tranport

Interface GigabitEthernet 0/2/0/0 l2transport

Ethernet Frame Formats

Preamble SFD DA SA Ethertype Data

Ethernet II Encapsulation

802.3/802.2/SNAP Encapsulation

OUI 0x00-00-00 Ethertype

<7 octets> <1 octet> <6 octets> <2 octets> <46-1500>

<2 octets> <2 octets>

<2 octets> <2 octets>

AToM - Label Stacking

Eth FR HDLC PPP

AAL5

No Yes Control Word

No

No No Yes

Data Plane

ƒ Rsvd - Must be set to zero (allows P routers to

distinguish AToM traffic from IP traffic for proper load

balancing)

Frame Relay flags, etc)

(e.g < 64 byte PDUs over ethernet)

sequencing is disabled)

AToM Control Word

EoMPLS Transport Formats

Preamble SFD DA SA TPID TCI Ethertype Data FCS

Preamble SFD DA SA TPID TCI Length AA-AA-03 OUI

IOS-XR L2VPN

Implementation

Overview

PWE3 Architectural Model

ƒ Initial L2VPN focus for IOS-XR is point-to-point PWs using LDP

(oMPLS) or L2TPv3 (oIP)

LC PI

Signaling Signaling

IM

Interface Resource - QoS L2FIB PD L3FIB PD

LC PD

LSPV

AIB

AIB PD

ƒ Some of the control plane code was ported from IOS, Xconnect DB, part of the AToM and ACMgr state machine

The ported code runs within the context of one Process L2VPN Mgr

ƒ L2FIB is a new code and is not ported from IOS, different architecture customized for the IOS-XR and the specific platforms that IOS-XR run on

platforms Any new L2VPN feature will require extensions to L2VPN Mgr (Ex: VPLS)

performance story due to the distributed XR architecture and having the L2 AC config processing done on the LC

ƒ L2VPN architecture have better HA because of the ability to SMU fixes and achieve hitless SW upgrade

IOS-XR L2VPN Software Architecture (2)

Implementation Notes

Sample Topology

PE2 Pleasanthill

PE1 Alamo

PSN Tunnel carrying PW’s

Customer A Site-2

Pos 0/0/0/4

Pos 0/2/0/0

IOS-XR EoMPLS (2 stage fwding)

TRAFFIC FLOW

IMPOSITION INGRESS

DISPOSITION EGRESS

CE2 CE1

MPLS PSN

AC1 PW (VC) LSP (PSN Tunnel) AC2

IMPOSITION EGRESS

DISPOSITION INGRESS

(Core facing LC) Existing L3FIB/

MPLS processing.

Swap IGP local Label with outgoing IGP label

Disposition Ingress

(Core facing LC) Existing L3FIB/

MPLS Processing Send MPLS pkt with VC label to corresponding

AC hosting Linecard.

Disposition Egress

(AC2 hosting LC)

New L2VPN/L2FIB egress Processing

to map Mpls(VC label) pkt to

AC interface after removing VC label

& control word if exists

Vlan Rewrite and Output L2 QoS Processing if any

PE-1 (Alamo) config – (1)

l2vpn xconnect group Customer_A p2p VLAN

interface GigabitEthernet0/1/0/1.5 neighbor 20.0.0.5 pw-id 200 pw-static-label local 123 remote 321 transport-mode vlan control-word enable

xconnect group Customer_B p2p PORT

interface GigabitEthernet0/1/0/0 neighbor 20.0.0.5 pw-id 100

interface GigabitEthernet0/1/0/0 l2transport

interface GigabitEthernet0/1/0/1.5 l2transport dot1q vlan 5

Cust A site1 config

Cust B site1 config

PE-1 (Alamo) config – (2)

router ospf 100 log adjacency changes detail area 0

interface Loopback0

! interface POS0/0/0/4

!

mpls ldp router-id Loopback0 log

neighbor

! interface POS0/0/0/4

!

interface Loopback0

IGP config

MPLS config

PE-2 (Pleasanthill) config – (1)

l2vpn xconnect group Customer_A p2p VLAN

interface GigabitEthernet0/1/0/1.15 neighbor 5.0.0.5 pw-id 200 pw-static-label local 321 remote 123 transport-mode vlan control-word enable

xconnect group Customer_B p2p NTT

interface GigabitEthernet0/1/0/0 neighbor 5.0.0.5 pw-id 100

interface GigabitEthernet0/1/0/0 l2transport

interface GigabitEthernet0/1/0/1.15 l2transport dot1q vlan 15

Cust A site2 config

Cust B site2 config

PE-2 (Pleasanthill) config – (2)

router ospf 100 log adjacency changes detail area 0

interface Loopback0

! interface POS0/2/0/0

!

mpls ldp router-id Loopback0 log

neighbor

! interface POS0/2/0/0

!

interface Loopback0

IGP config

MPLS config

RP/0/RP1/CPU0:pleasanthill#debug l2vpn forwarding platform ?

atom Platform L2FIB AToM debugs common Platform L2VPN forwarding common debugs

RP/0/RP1/CPU0:pleasanthill#debug l2vpn forwarding platform atom ?

all Platform L2FIB AToM all debugs errors Platform L2FIB AToM errors debugs events Platform L2FIB AToM events debugs location Specify a location

trace Platform L2FIB AToM trace debugs updates Platform L2FIB AToM updates debugs verbose Platform L2FIB AToM verbose debugs

RP/0/RP1/CPU0:pleasanthill#debug l2vpn forwarding platform common ?

all Platform L2VPN forwarding common all debugs errors Platform L2VPN forwarding common errors debugs events Platform L2VPN forwarding common events debugs location Specify a location

trace Platform L2VPN forwarding common trace debugs updates Platform L2VPN forwarding common updates debugs verbose Platform L2VPN forwarding common verbose debugs

<cr>

L2VPN PD Debug commands

RP/0/RP1/CPU0:pleasanthill#sh l2vpn platform trace ? all Platform specific l2fib trace data

atom Platform AToM trace data common Platform common L2VPN forwarding trace data RP/0/RP1/CPU0:pleasanthill#sh l2vpn platform trace atom ? all All L2FIB trace

errors L2FIB errors trace events L2FIB events trace trace L2FIB execution trace update L2FIB update trace verbose L2FIB verbose trace RP/0/RP1/CPU0:pleasanthill#sh l2vpn platform trace common ? all All L2FIB trace

errors L2FIB errors trace events L2FIB events trace trace L2FIB execution trace update L2FIB update trace verbose L2FIB verbose trace

L2VPN PD Ltrace commands

IOS-XR L2VPN CLI (1)

ƒ Move from interface mode in

IOS to a Global/Protocol Mode

IOS-XR L2VPN CLI (2)

3.4.1 Future

AC Type: QinANY

X future

Local Switching for Ethernet Port

X X

AC Type: Ether port

3.4.1 X

VLAN ID rewrite capability on both RX imposition and TX disposition side

3.4.1 X

Ethernet Interworking: port-to-VLAN

X X

VC mode: type-4 and type-5 ( tagged & raw)

X Future

L2PT

3.4.1 Future

Ethernet Interworking: QinQ-to-VLAN

3.4.1 Future

AC Type: QinQ

3.4.1 X

AC Type: VLAN

3.4.1 future

Local Switching for Ethernet VLAN/QinQ mode

X X

EoMPLS Pseudowire (AC<->PW)

X X

Label distribution: static and targeted LDP

C12k CRS

Features

L2VPN Features for XR 3.4.0 (1)

X X

QOS – 802.1pÆEXP Mapping

X 3.4.1

QOS - 1R2C Color-blind policer, 2R3C color-blind policer

X 3.4.1

QOS - match-vlan support

X X

L2VPN recovery via LDP GR

X X

Control Word Support for VCCV

X 3.4.1

QOS - Multiple conform/exceed/violate actions, random-detect cos

Future 3.4.1

QOS - Random-detect cos

Future 3.4.1

QOS - New match on L2 fields MAC address

X 3.4.1

QOS - per-VC policing/marking/shaping

X 3.4.1

L2VPN Config/Oper/Action XML

X X

MIBS: PW Common/MPLS and Ether AC

X X

Single Segment VCCV LSP ping

C12k CRS

Features

L2VPN Features for XR 3.4.0 (2)

Differences with IOS implementation

ƒ Protocol-based CLI for xconnect l2vpn

ƒ Interface configuration

configure PW label at each end

ƒ High availability

Process restartabilityLDP Graceful restart (RFC3478)Modularity via packaging and SW separation to processesFault tolerance

NSF with Failover or FIB and control plane restartsGraceful shutdown

Distributed processingDistributed States

Competitive Differentiation for IOS-XR

L2VPN

Known Caveats

ƒ Neighbor address of a PW has to be == ldp router-id

ƒ Control word can’t be negotiated back to set if it was already reset, without removing the configuration from both sides of the PW’s and re-adding it

ƒ PW status is not communicated back to the AC side PLIM to

inform the CE

Other Common Questions

Yes, infrastructure is there to support PW status TLV and FEC129

yes, we can map PW’s going to the same neighbor to a TE tunnel different then the one used by IGP autoroute

per-LC: 4Kper-box: 16K

IOS-XR L2VPN

Customer

Deployments

PE-1 core PE-2

ƒ Could be inter-area, inter-domain

core

AS

Network model

802.1ah

PE (ingress)

VC (tagged mode)

VC (tagged mode)

VLAN

VLAN VLAN

PE (egress)

L2 SW

L2 SW

LSP

Connectivity notification

Failure detect

Stop Opt-out Link-aggregation Link-aggregation

Basic Requirements

ƒ Consumer service (D/V/V triple-play) and enterprise service (EoMPLS)

will share the same NGN infrastructure

delay/jitter)

PE

customer customer customer

customer customer

IOS-XR PW Management and Provisioning

IOS-XR L2VPN

Futures

Future XR L2VPN Items

P2MP CLI

L2VPN Mgr

SysDB VFI/VPLS/VSI/Bridge

Xc P2mp config

L2FIB

-Send L2 Bridge table.

- List of interfaces/pw’s attached to L2 Bridge.

-Status of the PW and interfaces attached.

HW/Engine netio

L2vpn Switching DLL

-Program HW with Bridge table And interfaces attached to the Bridge

-Program Mac addresses in the bridge table with the Associated Interface from they were learned

Bridge table + Interfaces attached Mac learning/aging Distribution Logic

Punted pkts For Mac learning Going directly to L2FIB

Or via netio l2vpn Switching logic

STP

IOS-XR L2VPN Implementation Notes for VPLS

ƒ IOS XR Multiprotocol Label Switching Configuration Guide,

Release 3.4: http://www.cisco.com

Contacts

Meet the Experts

IP NGN Architectures and Technologies

Q and A

Q and A

52