Carrier Ethernet Transport...

BRKOPT-2018

Carrier Ethernet Transport Architectures Istvan Kakonyi, Vertical Solutions Architect

Follow us on Twitter for real time updates of the event:

@ciscoliveeurope, #CLEUR

© 2012 Cisco and/or its affiliates. All rights reserved. Cisco Public BRKOPT-2018 2

Housekeeping

We value your feedback- don't forget to complete your online session evaluations after each session & the Overall Conference Evaluation which will be available online from Thursday

Visit the World of Solutions and Meet the Engineer

Visit the Cisco Store to purchase your recommended readings

Please switch off your mobile phones

After the event don‘t forget to visit Cisco Live Virtual: www.ciscolivevirtual.com

Follow us on Twitter for real time updates of the event: @ciscoliveeurope, #CLEUR

http://www.ciscolivevirtual.com/

http://www.ciscolivevirtual.com/


Abstract

„Carrier Ethernet Aggregation Networks today are providing residential,

business, wholesale and mobile RAN transport services over the a single

physical infrastructure. This intermediate session describes the Cisco Carrier

Ethernet System and explains how this architecture can seamlessly operate

in this challenging environment. The session gives an overview of the major

building blocks of the Cisco Carrier Ethernet System, and its connectivity to

the other domains of the IP NGN. The session describes the architecture,

service delivery models, transport protocols used, network management and

the details of the connectivity to different access domains (Ethernet, DSL,

PON, Mobile) via Cisco Flexible Ethernet UNI. Special focus is given to

Unified MPLS, which helps to increase the scalability and simplify the

operation of the whole IP NGN. The session also describes the Cisco Carrier

Packet Transport Architecture, which provides a simple, efficient MPLS-TP-

based aggregation system.‖


Agenda

Cisco Carrier Ethernet Transport Architecture Overview

The Context of Broadband Forum‘s TR-101

Carrier Ethernet Architecture Details

- Building Blocks and Variants

- Service Delivery Models

- MPLS-TP-based Aggregation

- Scaling with Unified MPLS

- Network-based High Availability

- Network Virtualization (nV) Technology

- Network Management

Summary

Q and A

Cisco Carrier Ethernet Transport Architecture Overview


63 EB per mo

20 EB per mo

Entering the Zettabyte EraGlobal IP traffic will increase 4-fold from 2010 to 2015

81 EB

per mo

50 EB

per mo

38 EB

per mo 28 EB

per mo

Source: Cisco Visual Networking Index (VNI) Global IP Traffic Forecast, 2010–2015

2010 2011 2012 2013 2014 2015


Circuit to Packet Migration

Massive change in SP traffic make-up in next 5 years*

SP revenue shifting from circuits to packet services**

- 5 yrs ~80% revenue derived from packet services

- Packet traffic increasing at 34% CAGR***

*ACG Research 2011, ** Cisco Research 2010, ***Cisco VNI 2011

90+% IP Traffic

Private Line TDM/OTN Traffic

Private/Public IP Traffic

2011

~30-50%

~50-70%*

2013 2016



20-30% 0─10%

Private/Public IP Traffic

Private/Public

IP Traffic

70-80% 90+%

Legacy TDM Traffic


Subscriber

Business

Corporate

Residential

ATM Aggregation

Edge Core Access

Policy and Service Control Plane (per subscriber)

SDH

Mobile

Optical

L2SW

L2SW L2SW

L2SW

L2SW

L2SW

L1SW

SW

L1SW

L1SW

L2SE

OLT

DSLAM L2SE

L2SE

L2SE

L2SE L3SE

L3SE

BNG

L2SE

L0SW L0SW L0SW L0 W

Aggregation Edge Boundary

Access Aggregation Boundary

Ethernet Aggregation

MPLS Ethernet Aggregation

ATM/FR networks capped and to be closed

SONET/SDH evolving to MPLS Ethernet and OTN

Access and Edge optimized for

MPLS Ethernet

Service Provider Networks: Evolution to Ethernet and MPLS


Cisco Carrier Ethernet Transport Architecture

IPoDWDM Optical Network

Aggregation Node

Aggregation Network MPLS/IP

Carrier Ethernet Aggregation Access Edge

Aggregation Node

Aggregation Node

Ethernet Node

STB

VoD

Content Network

TV SIP

PON Node

DSLNode

Core Nodes

VoD

Content Network

TV SIP

Multiservice Core

Core Network

IP / MPLS Distribution Node

Corporate

Business

Corporate

Business

Residential

STB

Residential

Aggregation Node

Distribution Node

Mobile

2G/3G/4G Node

RAN Access Network

MPLS/IP

Corporate

Business

BSC/RNC

BSC/RNC

MPLS-based transport with MPLS-TP option

Cisco ASR9000, ASR1000, ASR 903, ASR 901,

Cisco Carrier Packet Transport , CPT50, -200, -600

Flexible Ethernet Edge

Ubiquitous Ethernet UNI across different product lines and OSs

Flexible Options for Subscriber Awareness

Distributed Edge, Centralized Edge, ISG for IPv4/IPv6

Intelligent transport of video

PIM Optimizations, MoFRR, TI-MoFRR, integrated video caching,

Video Quality Monitoring


Two technologies for L2 transport over MPLS:

- Ethernet over MPLS (EoMPLS)

Used for L2 point-to-point link over MPLS cloud

No MAC learning involved

- Virtual Private LAN Services (VPLS)

Used for multipoint L2 connections

Collection of pseudowires tied together by a Virtual Forwarding Interface (VFI)

MAC addresses learned on VFI

Traffic forwarding based on destination MAC addresses

H-VPLS, an extension of VPLS

L2 MPLS Transport


MPLS

MPLS in the aggregation network and core

Targeted LDP session between PEs to exchange VC label

Tunnel label is used to forward packet from PE to P to PE

VC label is used to identify L2VPN circuit

Attachment Circuit (AC) can be port-based or VLAN-based (or Ethernet Flow Point based, see later)

EoMPLS Overview

Pseudowire

Aggregation Node

P Aggregation

Node

Access Node FTTB CPE

Access Node FTTB CPE

LDP LDP

Targeted LDP

Attachment Circuit Attachment Circuit

P

Tunnel label

Ethernet PDU

VC label

Ethernet PDU

Ethernet PDU


Attachment Circuit (AC)—Connection to Aggregation using an Ethernet VLAN

Virtual Circuit (Pseudowire)—EoMPLS tunnel between PEs using a full mesh

Virtual Forwarding Instance (VFI)—A virtual L2 bridge instance that connects ACs to VCs

(PWs); VFI=VLAN=broadcast domain

RFC4761 (BGP-signalled) and RFC4762 (LDP Signalled)

Enhanced with BGP based Autodiscovery (RFC6074)

Scalability issues almost solved via H-VPLS and state-of-the-art NPU technology (2M MAC address/chip)

VPLS (Virtual Private LAN Services)

Aggregation

Node

MPLS

Core

VFI

VFI

VFI

Attachment

Circuit

Ethernet Port

or VLAN

Virtual Forwarding

Instance

Eompls Virtual Circuit

(Pseudowire)

Aggregation

Node

Aggregation

Node

Access Node Access Node

http://tools.ietf.org/html/rfc4761




MPLS Transport Profile - T-MPLS requirements feeding into IETF MPLS-TP enhancements:

MPLS-TP differs technologically from T-MPLS. ITU stopped work on T-MPLS.

- Effort to address Pt-to-Pt ATM-like transport centric networks (like ATM PVCs)

- Focused on connection-oriented (CO-PS) services

Data plane—based on IETF MPLS, with restricted options - No ECMP, no PHP, no LSP merging

Control plane—static and/or dynamic - Static provisioning with NMS, with standardized common functions

- Dynamic control plane based on GMPLS or IP/MPLS

Key OAM enhancements - GE-ACH—Generic Associated Channel to support FCAPS functions alongside transport MPLS

LSP

- GAL—Generic-ACH Label as generic exception mechanism for LSP OAM

IETF MPLS-TP

Provisioning and Management

CE CE

PE2 PE1


Aggregation Network MPLS/IP

Dark Fibre / CWDM / DWDM and ROADM

Carrier Ethernet Aggregation

BNG

Business PE

Access Edge

Aggregation

Node

DSL

Ethernet

Core

VoD

Content Network

TV SIP

Multiservice Core

Core Network

IP / MPLS

Distribution

Node

STB

Corporate

STB

STB

Residential

Corporate

Corporate

Business

Business

Business

Residential

Residential

2G/3G Node

PON

Architecture variants:

Carrier Ethernet Architecture Evolution

IP/MPLS ETHERNET

IP/MPLS

IP/MPLS MPLS-TP

MPLS-TP

Cisco supports the MPLS-TP option now (CPT Product Line)


Cisco’s NGN Transport Direction

Characteristic SONET

/

SDH

Optical OTN

(ROADMs)

Electrical OTN

PBB-TE MPLS-TP IP/MPLS

Ethernet

Eline (10GE)

Eline (sub 10GE)

E-Tree

E-LAN

Legacy

F/R

ATM

TDM

IP

L3VPN

L3 Unicast

L3 Multicast

Content

General

Traffic Engineering

50ms restoration

Multiplexing Technology Time Division

Wave Division Time Division Statistical Statistical Statistical

UNI processing Limited None None Typically rich Typically rich Typically rich

Granularity VC-4 Lambda ODU Variable Variable Variable

Technology Maturity

Cisco focuses on IP/MPLS for the Carrier Ethernet Transport architecture.

Cisco targets MPLS-TP for the POTS and Access Networks while supporting already Ethernet Bridged Access

Cisco also addresses MPLS to the access with Unified MPLS


Flexible Ethernet Services Mapping Enabling Multiservice Aggregation

VLAN -802.1q -QinQ

L3/VRF

L2, Bridged

VPLS

L2, Point to Point

EoMPLS

H-QOS

per

VLAN

Flexible

VLAN

Trans-

lation

1:1

2:2

1:2

Security

Residential

STB

Business

Corporate

Residential

STB

Business

Corporate

ISG Subscriber

Session H-QOS

per

Session

Flexible Mapping of subscriber VLANs to

services (L2, L3, MPLS, ISG)

VLAN translation capabilities for single and doubled tagged

VLANs

Business VPN L2/L3 Bitstream wholesale

services

Residential Subscriber Sessions with RADIUS based

zero-touch provisioning


Hybrid (Centralized) Service Edge MPLS/IP Packet Aggregation for 3play Service Delivery

Video Service Edge

• Implemented on Aggregation Node

• Layer-3 MPLS/IP unicast VoD and multicast IPTV transport for video service distribution

HSI/VoIP Services Edge

• Implemented on Centralized BNG

• IPoE and PPPoE service transport over 802.1Q and QinQ interfaces enabled by per subscriber ISG sessions

DSL Access Node

Access

PON Access Node

Ethernet Access Node

Aggregation Network

MPLS/IP


Distribution Node

Distribution Node

Aggregation Node

Aggregation Node

Aggregation Node

Core Network

IP / MPLS

VoD

Content Network

TV SIP

Multiservice Core

Business

Corporate

Residential

STB

Residential

STB

Business

Corporate

Business

Corporat

e Residential

STB

Business

Corporate

MPLS/IPoDWDM Optical Network

BNG


BNG

Core

Core

Internet Peering

Core

BSC/RNC

BSC/RNC

HSI/VoIP

Service Edge

IP Edge

Video

Service Edge

ASR1000 series:

Up to 64k sessions

H-QoS

FW, DPI,CGN


Video Service Edge

Implemented on Centralized Video-BNG

Layer-2 VPLS transport of unicast VoD and multicast IPTV for video service distribution

HSI/VoIP Services Edge

Implemented on Centralized HSI-BNG

IPoE and PPPoE service transport over 802.1Q and QinQ interfaces enabled by per subscriber ISG sessions

Centralized Service Edge (with L2 Aggr.) MPLS/IP Packet Aggregation for 3play Service Delivery

DSL Access Node

Access

PON Access Node



Distribution Node

Distribution Node

Aggregation Node

Aggregation Node

Aggregation Node

Core Network

IP / MPLS

VoD

Content Network

TV SIP

Multiservice Core


HSI-BNG


Video-BNG

Core

Core

Internet Peering

Core

BSC/RNC

BSC/RNC

VFI

Video

Service Edge

HSI/VoIP

Service Edge

IP Edge

Business

Corporate

Residential

STB

Residential

STB

Business

Corporate

Business

Corporat

e Residential

STB

Business

Corporate

VFI VFI

VFI


Distributed Service Edge MPLS/IP Packet Aggregation for 3play Service Delivery

3Play Service Edge

Implemented on Integrated Edge Node

Unicast services (HSI/VoIP/VoD) enabled by IPoE or PPPoE per subscriber ISG sessions

Multicast services (IPTV) coexist with ISG sessions

Aggregation network implements MPLS/IP for unicast and IP multicast for service transport

DSL Access Node

Access

PON Access Node


Aggregation Network

MPLS/IP

Distribution Node

Distribution Node

Integrated Edge Node



Core Network

IP / MPLS

VoD

Content Network

TV SIP

Optional L3VPN

Edge Multiservice Core



Core

Core

Internet Peering

Core

BSC/RNC

BSC/RNC

Video/HSI/VoIP

Integrated Service Edge

Business

Corporate

Residential

STB

Residential

STB

Business

Corporate

Business

Corporat

e Residential

STB

Business

Corporate


C7600

Based on ES+

Up to 48K sessions

Limited IPv6 roadmap

ASR9000:

Up to 128K+ Sessions

Full IPv6 feature set

Very good scalability in

combined BNG

+MSE+CE apps.

IOS-XR


Architecture Comparisons Which one to choose?

The architectures options can be evaluated against the following criteria

• Capital Expenditures

• Scalability (Bandwidth / Subscriber, Transport, Policy Control)

• Operational Complexity (Troubleshooting, QoS)

• Reuse of existing Operations procedures

• Availability

• Traffic Patterns

• Economically serving areas of differing subscriber density

• Service Flexibility

• Operational Flexibility


L3 IP Mcast

L3-Core IP Mcast

L3 IP Mcast

L3-Core IP Mcast

L3 IP Mcast

L3-Core IP Mcast

IP for Video and IP/TV Service Delivery Key Characteristics and Benefits

Simplified Operations

- IGMP/PIM only required, no snooping necessary in Aggregation network; snooping contained in DSLAM

- Single point of L3 termination for IP/TV (no VRRP required)

- No overlay topology

Optimal and Scalable Forwarding

- SSM multicast distribution model for optimal tree creation under all conditions

- Dynamic load balancing on equal cost paths (!!)

- Optimized ARP and IGMP tables through distribution

- Flexible content injection, including localized content

- Same topology for unicast and multicast (!!)

- Scales in terms of network nodes and subscribers in any topology due to distributed L3

- Allows for on-path CAC

Resiliency

- Consistent convergence in all failure cases: Source-, Node-, Link-Failure.

- Anycast-Source model for enhanced redundancy

- SSM security and address-space efficiency proven architecture in many 3Play production networks today

Future Ready

- Possibility to add/distribute video monitoring and error concealment techniques easily

IP: 1.1.1.1

IP: 1.1.1.1

Optimal Replication

Load-Balancing Efficient Use of Access Bandwidth

Any-Cast Sources


Characteristic Native IP Multicast

p2multipoint MPLS Traffic Engineering

Multicast LDP (mLDP)

Convergence < ~1s (100ms) (link and node failures)

~50ms (link failures only)

< ~1s (~50ms with p2p

MPLS TE FRR LP)

Offload routing

(IGP metric based traffic engineering)

(IGP metric based traffic engineering)

Path separation

(MoFRR or MTR)

(MoFRR or MTR)

Admission control and bw reservation

(RSVP)

Scalable mp2mp MulticastVPN Typical Application

Secondary Distribution (TV)

Contribution (TV) Enterprise VPN

Comparison of Multicast Transport Options

•Note: H-VPLS can be used for Wholesale IPTV

•MoFRR=Multicast Only Fast ReRoute, MTR = Multi Topology Routing

The Context of Broadband Forum TR-101 „Migration to Ethernet-based Broadband Aggregation‖


VLAN architecture

Multicast considerations

Use of a video-optimised Service Router (next to ‗traditional‘ TR-59 type BRAS)

Resilience in the Ethernet Aggregation Network

QoS in the Ethernet Aggregation Network

Ethernet OAM

Support for PPPoA and IPoA (aka interworking between XoA and XoE)

TR-101 Scope and Content

Note: TR-101 introduces the term Broadband Network Gateway (BNG) to differentiate from the

legacy ‗BRAS‘ term

Migration from ATM to Ethernet Broadband Aggregation


The models considered are part of DSL Forum TR-101 section 2.5.1

- Multiple VC DSL UNI

- Trunk UNI—Single VC DSL or Ethernet

- Non-Trunk UNI—Single VC DSL or Ethernet

In the Multiple VC DSL UNI model, the VC is used for both service prioritization and service connectivity

In the Single VC DSL and Ethernet UNI models, these functions are distributed in 802.1p COS and 802.1Q VLANs

Choice of model will be dependent on Access Node and RG capability, number and type of services offered and available bandwidth on local loop

Access Node Connectivity Models


DSL Provider Access Domain

A VLAN per DSLAM port

Local C.O.

DSLAM

CopperLoop

U-PE

DSL

PVC VLAN 19Port 2

VLAN 19

DSL

PVC VLAN 85Port 1

VLAN 85

QinQ

Outer VLAN 102

CPE

VLAN Architecture: VLAN per User (1:1)

VLAN use similar to ATM, i.e. connection-oriented, i.e. configuration intensive

IEEE802.1ad—Inner Tag = Port Identifier, Outer Tag = DSLAM Identifier

Multicast replication inside Single BNG, not inside Ethernet Aggregation Network

Multi-homing to two BNGs is complex

Good for p2p business services; less ideal for Triple-Play Services


Single tagged (802.1Q or 802.1ad) VLANs—double tagging not needed

Connectionless provisioning benefit; Access Node inserts Line ID (DHCP Opt 82 , PPPoE Intermediate Agent)

Network Elements take care of subscriber MAC isolation through ‗split horizon forwarding‘

Multiple injection points per VLAN (BRAS and Video Service Router) possible

Multicast replication within access/aggregation

VLAN Architecture: VLAN per Service/SP (N:1)

DSL Provider Access Domain

Residential Bridging

Local C.O.

DSLAM

CPECopperLoop

DSL

PVC

DSL

PVC

U-PE

DSL

PVC

GE

VLAN 18

ISP 1

VLAN 19ISP 2

VLAN 18

ISP 1

VLAN 19

ISP 2

GE


Per Class scheduling within Access/Aggregation Network

Per Class scheduling is essential for Video as the Access Node is effectively a multicast insertion/replication point (replicating per subscriber line)

Per Class scheduling essential when separate Video BNG is deployed

Ethernet Aggregate QoS Within the Access/Aggregation Network

Video BNG

BNG (BRAS)

IP/TV/VoD CBR or VBR

2 Mbps—3.9 Mbps 100 Kbps

3 Mbps

PQ

Voice (PQ with Policing at 100 Kbps)

Internet (Shaped or Policed at 3 Mbps)

Aggregation Access

Video Traffic Uniquely Marked

and Placed on Aggregation

Network

Work preserving scheduler

Static configuration on user link

120 Kbps

4.5 Mbps

Unspecified

PQ

6 Mbps


Cisco’s TR-101 Architecture From Discrete Elements

Video BNG

BNG BRAS

Aggregation Node:

Carrier Ethernet Switch/

Service Router with

Aggregation Function

Aggregation Node:


Service Router with


BNG/BRAS Extremely Important for PPP Services/Migration/Legacy

ATM Support

Business

Residential

STB

IP/MPLS Core L2 Aggregation

with

IGMP Snooping


Cisco’s TR-101 Architecture Via Video Optimization

Video BNG

IP/MPLS Core

BNG BRAS

Aggregation Node:


Service Router with


Aggregation Node:


Service Router with



ATM Support

Business

Residential

STB

L2 Aggregation

+ L3 IP/PIM-SSM


Cisco’s TR-101 Architecture To Integrated Network Elements

BNG BRAS

Carrier Ethernet Service Router (L1, L2, L3)

Video BNG (L3 IP/PIM-SSM) + L2 Aggregation

Option to Virtualize L2 Aggregation (IP Control Layer, MPLS Techniques)


ATM Support

Business

Residential

STB


+ L3 IP/PIM-SSM SiSi SiSi


Cisco’s TR-101 Architecture With Distributed Edge

Carrier Ethernet Service Router (L1, L2, L3)

Video BNG (L3 IP/PIM-SSM) + L2 Aggregation

Option to Virtualize L2 Aggregation (IP Control Layer, MPLS Techniques)

Business

Residential

STB


+ L3 IP/PIM-SSM SiSi SiSi

ISG

Subscriber Control is integrated into the Carrier Ethernet node for PPP and IP (IPv4/IPv6) sessions

Cisco Carrier Ethernet Transport Architecture Details


Cisco IP NGN Architecture Components & Overview

Access

Ethernet Node

Ethernet Node

DSL Node

PON Node

Access Carrier Ethernet Aggregation

Aggregation Node

Distribution Node

Distribution Node

Aggregation Node

Core Network

IP / MPLS

Content Network

TV SIP

Content Network

TV SIP

IP Edge Multiservice Core


Core Node

Core Node

Business

Corporate

Business

Corporate

2G/3G RBS

Residential

STB

Residential

STB

Residential

STB

Business

Corporate

Aggregation Node

Aggregation Node

MPLS/IP/Ethernet

BSC/RNC

BSC/RNC Cell Site Gateway

MPLS/IP Transport

Transport Deployment: VPWS, VPLS

Service Aware Deployment: VPWS, VPLS, MPLS VPN/IP

HSI Service Edge Node

Optional Video Service Edge Node

Optional Business Service Edge Node

Carrier Ethernet Aggregation Core and Edge

CPE

DSL:

• Residential:

Linksys WAG-

310G

• Business:

ISR x900

Ethernet:

• Residential:

Genexis

• Business:

ISR x900,

ME3400E,

ME3600X

PON:

• Residential,

Business:

Wave 7 ONTs

Access ADSL2+ :

• Alcatel-Lucent

ISAM 7302

Ethernet FTTX:

• ME3400E,

ME3600X, Catalyst

4500/4900 series

PON:

• Wave7 Trident G-

PON OLT

Mobile RAN :

• ASR 901

Aggregation /

Distribution

Cisco ASR9k

• RSP 440

• Typhoon LCs: 24 x 10GE, MOD80,

MOD160, 2 x 100 GE

• ―Legacy‖ LCs: 40xGE, 4x10GE,

8x10GE

• ASR 9001

• Clustering and Satellite

• Distributed BNG Services

Cisco CPT200, -600

Cisco ME3800X, Cisco ASR 903

Multiservice Edge Business SEN:

• ASR9k: 4x10GE, 40xGE,

24x10GE, MOD80, MOD160

HSI-SEN :

• ASR1k: RP2, ESP-20,

ESP-40

Video SEN:

• Cisco 7609S: RSP-720,

ES+

•ONS15454 MSTP with WSON

•Xponders for direct Ethernet connectivity

Optical Integration

Multiservice

Core

•Cisco CRS-1/3

•Cisco Prime 3.8, Activation,Monitoring and Fault Management

systems.

•Cisco Access Registrar, Cisco Network Registrar

•CNS-Config Engine r3.0, BAC 3.5

•3rd Party platforms from BroadHop, InfoVista VIN-ANA.

Network & Service Management, OAM


IP NGN Services All Validated in Release 1.8

Market Services Access

SLA

Type SLA Example

Residential Internet Access

Ethernet, DSL,

PON Transport

Dynamic access bandwidth, session/idle timeout, advertisements, post

paid/prepaid (time and volume)

VoIP Telephony

Ethernet, DSL,

PON Application

The number of VoIP appliances, SIP URLs/PST Phone numbers, active

calls, VoIP call quality

VoD

Ethernet, DSL,

PON Application The number of STBs, stream quality, content flavours, charging models

TV

Ethernet, DSL,

PON Application

The number of STBs, type of TV packages, SD vs HD content and

delivery quality

Business L3 VPN

Ethernet, DSL,

PON Transport

Access bandwidth, differentiated services support, L3 VPN topology,

managed services (unicast and multicast)

E-Line

Ethernet,

DSL*, PON* Transport Access bandwidth, differentiated services support, transparency

E-LAN

Ethernet,

DSL*, PON* Transport

Access bandwidth, differentiated services support, multipoint

transport, transparency

Transport Mobile RAN

2G,

3G R99,

3G R5, R8 Transport

Guaranteed bandwidth, delay and jitter synchronization (frequency and

phase) accuracy inline with Mobile Radio technology

HSI

Wholesale

Ethernet,

DSL, PON Transport

Aggregated bandwidth on ISP level, differentiated services support,

with subscriber management at ISP, with L2TP or MPLS VPN transport

Triple Play

Wholesale

Ethernet,

DSL, PON Transport

Aggregated bandwidth on ISP level, differentiated services support,

transparent P2P Ethernet transport for unicast services, P2MP Ethernet

transport for IPTV

Contribution

Video

Ethernet,

Video HD-SDI Transport Guaranteed bandwidth, delay, jitter , and close to zero or zero loss

* Ethernet Relay Point to Point and Multipoint only


Residential Services Architecture

HSI, VoIP VLAN(s) EoMPLS Pseudowire EoMPLS PW

VoD+IPTV , VoIP VLAN

802.1Q

QinQ

N:1 VLAN

Non/Trunk UNI, N:1 or 1:1 VLAN

MPLS/IP, IP Multicast, IP LFA, MoFRR

MPLS/IP

MPLS/Multicast VPN

ISG Sessions

Enables PPPoE to IPoE migration,

usage based services with service

and session control, DPI and SBC

May include service supporting

functions; Content Cache, FCC, RET,

VoD CAC

Retail 3Play Hybrid Edge Deployment

HSI, VoIP VLAN(s) EoMPLS Pseudowire EoMPLS PW

VoD+IPTV VLAN

802.1Q

QinQ

N:1 VLAN

Trunk UNI, N:1 or 1:1 VLAN

MPLS/IP

MPLS/Multicast VPN

ISG Sessions Retail or Wholesale 3Play Centralized Edge deployment

802.1Q

QinQ H-VPLS, IGMP snooping, CAC IP, PIM

HSI SEN

Video SEN

HSI SEN

Multiservice

Core Network

Aggregation Node

ASR9k, 7600, ME3800X Video SEN, 7600

PPP, IP, MPLS MPLS 802.1ad NNI, MPLS/IP Transport DSL, PON, Ethernet

Access Node

HSI SEN, ASR1k

Distribution Node

ASR9k, 7600

Large Scale

Aggregation Network

Intelligent

Services Edge Efficient

Access Network

Ethernet/MPLS NNI

Core Node

CRS-1/3

Service Aware or Transport

VPWS, VPLS, MPLS/IP


Business Services Architecture

E-LINE

E-LAN H-VPLS or VPLS

EoMPLS

Port, 1q, QinQ

Port, 1Q, QinQ or .1ad

Port, 1Q, QInQ or .1ad

L3 VPN

Ethernet

QinQ

Port, 1Q, QInQ

MPLS VPN

VPLS

MPLS VPN/Multicast VPN (GRE)

H-VPLS or VPLS

MPLS VPN

Centralized Edge Deployment

L3 VPN

L2, L3 VPNs SONET/SDH Access

SONET/SDH Access

STM4

OC12

Ethernet MPLS VPN

VPWS (FR, IP) MSE

E-MSE

Multiservice

Core Network

Aggregation Node

ASR9k, 7600, ME3800X Video SEN, 7600

PPP, IP, MPLS MPLS 802.1ad NNI, MPLS/IP Transport DSL, PON, Ethernet

Access Node

HSI SEN, ASR1k

Distribution Node

ASR9k, 7600

Large Scale

Aggregation Network

Intelligent

Services Edge Efficient

Access Network

Ethernet/MPLS NNI

Core Node

CRS-1/3

Service Aware or Transport

VPWS, VPLS, MPLS/IP

Ch E1/T1 E3/T3,

MLPPP/FR

Distributed Edge Deployment


Cisco MPLS-TP Functionality Overview

Bi-directional, co-

routed LSPs

Static LSP

QoS

CC/RDI

On-demand CV

Route Tracing

AIS/LDI/LKR

CFI (PW Status)

Forwarding Plane OAM

1:1 Linear protection

LOS/OAM/BFD trigger

Lockout

Revertive

Wait-to-restore timer

Protection

Ethernet/VLAN

MS-PW integration

with IP/MPLS

Clients

Working LSP

PE PE Protect LSP

NMS for Network Management

or Dynamic Control Plane

Client node Client node

MPLS-TP LSP (Static or Dynamic)

Pseudowire

Client Signal

with e2e and

segment OAM Section Section

• Connection Oriented,

pre-determined working

path and protect path

• Transport Tunnel 1:1

protection, switching

triggered by in-band

OAM

• Options with NMS for

static provisioning, or

dynamic control plane for

routing and signaling


Static Co-Routed MPLS-TP Label Switched Path

Static

Point-to-point

Bidirectional

Co-routed (same forward and reverse paths)

In-band Generic Associated Channel (G-ACh)

Ultimate hop popping (no explicit/implicit null)

No ECMP

Contained within a tunnel

MPLS-TP

LSP

G-ACh

MPLS-TP

Tunnel


OAM Characteristics

In-band OAM packets (fate sharing)

OAM functions can operate on an MPLS-TP network without a control plane

Extensible framework with current standardization focus on fault and performance management

Independent of underlying technology

Independent of PW emulated service


MPLS Generic Associated Channel

OAM capabilities extended using a generic associated channel (G-ACh) based on RFC 5085 (VCCV)

A G-ACh Label (GAL) acts as exception mechanism to identify maintenance packets

GAL not required for pseudowires (first nibble as exception mechanism)

G-ACh used to implement FCAPS (OAM, automatic protection switching (APS), signaling communication channel, management communication channel, etc)

ACH

OAM Payload

GAL

Label

Associated Channel Header

Generic Associated Channel Label (GAL)

PW Associated

Channel Header

(ACH)

ACH

OAM Payload

Label

PW Label

0 0 0 1 Version

RFC 5586

RFC 5085

13 TC 1 1

Reserved 0 0 0 1 Version Channel Type

LSP

G-ACh

PW G-ACh

Reserved Channel Type


MPLS-TP OAM Components

BFD CC

(Interval x

Multiplier)

BFD CC

(Interval x

Multiplier)

Label

ACH

BFD

GAL

Bi-directional, co-routed

MPLS-TP LSP

BFD (Down)

BFD (Init)

BFD (Up/Poll)

BFD (Up/Final) BFD (Up) BFD (Up) BFD (Up)

BFD (Up)

P1 PE1 PE

2

P2

Continuity Check (CC) /

Remote Defect Indication (RDI)

P1 PE1 PE

2

Label

ACH Fault (LKR)

GAL


MPLS-TP LSP

P2

Oper

Down Admin

Down

Label

ACH Fault (LDI)

GAL

LKR LKR LKR

LKR

LKR

LDI LDI LDI

LDI

LDI

1 per sec

1 per fault

refresh timer

(default 20s)

X

X

Fault OAM

(AIS/LDI, LKR)

Label

ACH LSP Ping

GAL


MPLS-TP LSP

LSP Ping

Echo Request

TTL=255

P1 PE1 PE2 P2

LSP Ping

Echo Reply

TTL=255 LSP Ping

Echo Request

TTL=255 LSP Ping

Echo Reply

TTL=255

On-demand Connectivity

Verification (CV) and Route Tracing


Linear Protection

Relies on a disjoint working and a disjoint protect path between two nodes

Provides 1:1 protection (only one active LSP) in revertive mode

Functionally similar to path protection in IP/MPLS

Protection switching can be triggered by

- Detected defect condition (LDI/AIS, LKR)

- Administrative action (lockout)

- Far end request (lockout)

- Server layer defect indication (LOS)

- Revertive timer (wait-to-restore)

Lockout function for administratively initiated switchover (pre-standard)

Revertive behavior by default, can be made non-revertive

PE1 PE2

P2

P1

Working LSP

(Up, Active)

Protect LSP

(Up, Standby)

PE1 PE2

P2

P1

Working LSP

(Down, Standby)

Protect LSP

(Up, Active)

Working LSP

(Up, Active)

Protect LSP

(Up, Standby)

Working LSP

(Down, Standby)

Protect LSP

(Up, Active)

Before Failure

During Failure


MPLS-TP Aggregation Architecture

Aggregation

IP / MPLS Transport

VoD

Content Network

TV SIP

VoD

Content Network

TV SIP

Core

Core Node

Core Node

Edge

Video Service Edge Node

Business Service Edge Node

HSI Service Edge Node

BSC/RNC

BSC/RNC

MPLS-TP

Aggregation Node

Business

Corporate

Business

Corporate

Residential

STB

Residential

STB

Business

Corporate

Access Business

Corporate

Bridged DSLAM

Bridged OLT

MPLS RAN

Bridged RAN

Bridged FTTX

CPT50

CPT200

CPT600

Scaling Services with Unified MPLS


Problem Statement

1k Nodes / Core

10k Nodes / Aggregation

100k Nodes / Access

Scale - Interconnect 100k Access nodes through an MPLS domain

Resilience - < 50msec convergence as often as possible

Simplicity - Operation of big MPLS networks is often considered difficult

Reference Model

IGP2 IGP1 IGP3

DSLAM1

PE11

PE12

ABR11

ABR12

ABR21

ABR22

PE21

PE22

DSLAM2

Core and Edge Distribution /

Aggregation

Distribution /

Aggregation


Solution

To scale, introduce a layer of hierarchy

RFC 3107-based hierarchical LSPs over IGP

IGP/LDP inter-area summarization

BGP‘s applicability to scale services is clear (Internet)

ABRs are BGP speakers too. They set next-hop-self

ABRs are Route Reflectors too. Further RR hierarchy can also be used to avoid full mesh iBGP connectivity among ABRs

BGP‘s applicability to scale PE‘s reachability with was made possible by two key innovation:

BGP PIC: Simple Scale-Independent BGP FRR which meets the resilience requirement for PE reachability

BGP additional-path: BGPs ability to compute and store more than one paths


Route Distribution

No IS-IS route is propagated from L2 to L1 – or a few summaries covering all the r2r subnets in the L1 region

Only the core ABR‘s addresses are propagated from L2 to L1 – plus potentially a few summaries covering all the r2r subnets in other regions

Static Routes to Access Nodes are redistributed into L1

L1 routes are redistributed into BGP (with filters) on ABRs

ISIS L1 ISIS L2 ISIS L1

D1

PE11

PE12

ABR11

ABR12

ABR21

ABR22

PE21

PE22

D2

Redist ribute core ABR into L1

Redistribute static into L1


BGP Add-Path

– PE11 learns two paths to PE21: via ABR11 and ABR12

BGP 3107 RR with next-hop-self

– ABR21 reflecting the path to D2

– ABR11 reflecting the path to D2

BGP Routing and Features

iBGP3107 PE21 and D2 via ABR21


L1 L2 L1

D1

PE11

PE12

ABR11

ABR12

ABR21

ABR22

PE21

PE22

D2


Each IGP area has routes for that area only plus routes to core ABRs ( ~1k prefixes)

LDP labels are used to traverse each area and reach core ABRs

BGP labels are used by PEs and ABRs to reach PEs in remote areas

Service (e.g. PW) labels are used by PEs

L2

IGP/LDP Label

BGP3107 Label

Service Label

L1 L2



Label Stacks and Label Allocation

L1 L2 L1

D1

PE11

PE12

ABR11

ABR12

ABR21

ABR22

PE21

PE22

D2

NH:

ABR21

Label: L1

NH:

ABR11

Label: L2

L1

Network-based High Availability


Baseline Network Availability Mechanism

Access Mechanisms

- Multiple Spanning Tree (MST) or MST Access Gateway

- Resilient Ethernet Protocol (REP)

- G.8032 Ethernet Ring Protection

- Multi-Chassis LACP

IP Services and MPLS IGP:

- IP Fast Convergence

- LFA / IP FRR

- Multicast Fast Convergence, MoFRR

NEW!

Large Scale Aggregation

Intelligent Edge

Distribution Node

BNG

MPLS PP, IP, MPLS MPLS-TP/MPLS/IP

Aggregation Node

BNG

Access Node

Efficient Access

DSL, Ethernet

Multiservice

Core

MPLS Services:

VPLS mac-address withdrawal; MST/REP and VPLS interworking

Pseudowire redundancy including pseudowire status bit support


Ethernet Access Topologies

Ethernet Access Rings Multiple Spanning Tree

Convergence Dependant on VLANs/MAC-addresses

Often non-deterministic

No support for Per VLAN STP

Hub and Spoke FlexLink or Link Aggregation

Fast Convergence independent of VLANs/MAC-addresses

IP/MPLS IP/MPLS


VFI

VFI

VFI

VFI

I‘m the second-best root

I‘m just in a normal STP ring

I‘m the root

Operation

- Top PE sends ―pre-canned‖ BPDUs (best root) into L2 access network

- Access network runs normal MSTP, MSTP is terminated locally on the PE access ports

- MSTP TCNs trigger VPLS MAC Flush + Withdraw

- MST instances have per port local significance – greatly improves scalability

- Only subset of functionality needed for REP Access Gateway

Benefits

- Seamless integration with any L2 access network or node running MSTP, full standard compliance

- Inherent scalability and faster L2 convergence due to local Rapid STP behaviour

MST Access Gateway Operation and Benefits


Ring Protection Protocols: Another Push Beyond Spanning Tree

A ring topology is a cheap method of achieving redundancy, suitable for access networks

Spanning tree is geared toward loop avoidance in a general topology and does not require configuration, but this comes at the cost of convergence time

If a topology is known to be a ring at the outset, a loop avoidance protocol can be designed and optimized to achieve rapid 50ms convergence (but does require configuration and some hardware support)

G.8032 and Cisco‘s REP are such examples


A new protocol designed to provide a solution for fast and predicable Layer 2 convergence for Carrier Ethernet networks

Fast and predictable convergence

- Convergence time: 50 to 250ms

- Fast failure notification even in large rings

Limit the scope of Spanning Tree

- STP is deactivated on REP interfaces

- STP TCN sent away from the segment if segment fails

Allows VLAN load balancing for optimal bandwidth utilization

Cisco proprietary (future alignment and interworking with ITU-T G.8032)

What Is Resilient Ethernet Protocol (REP) ?


REP guarantees there is no connectivity between two edge ports on a segment

A REP segment is a chain of ports connected to each other and configured with a segment ID

When all interfaces in the segment are UP, the alternate port is blocking

When a link or switch failure occurs on the segment, then blocked port goes forwarding

REP

A Segment Protocol

REP Segment

Blocked Open Alternate Port

Link Failure

Edge Port Edge Port


Enhancement to REP introduced in latest Ethernet Access Node releases

Allows interconnection of REP segments with STP/VPLS domains

REP Edge No Neighbour

REP Segment

Blocked Open Alternate Port

Link Failure

Edge Port Edge Port

Non REP Domain

STP TCN


G.8032 Ethernet Ring Protection (ERP) Objectives and Principles

Protection switching on Ethernet layer

Utilizes conventional Ethernet bridge domains as forwarding plane

Preventing any loops by blocking mechanism

Can protect against any single failure on the ring

Fast convergence (50 ms)

Support of administrative commands (e.g. to force a failure etc)

Relies on Ethernet OAM for fault detection and as its control channel, and Y.1731 Ring-Automatic Protection Switching (R-APS) to signal a failure upstream

Supports Closed and Open (like a REP Segment) Rings

Functionally Equivalent to REP (with open rings)


G.8032 Basic Protection Mechanism: Ring Protection Link (RPL)

Normal condition

- Block RPL (Ring Protection Link)

A B

E D

F C

A B

E D

F C

A B

E D

F C

R-APS(SF)

R-APS(SF)

Failure condition

Block failed link

Send R-APS with Signal Failure (SF) messages

Unblock RPL

Perform Forwarding Database (FDB) flush on all ring node as needed


MC-LAG & ICCP enable a switch/router to use standard Ethernet Link Aggregation for device dual-homing, with active/standby redundancy

Dual-homed Device (DHD) operates as if it is connected to single virtual device and runs IEEE std. 802.1AX-2008 (LACP)

Point of Attachment (PoA) nodes run Inter-chassis Communication Protocol (ICCP) to synchronize state & form a Redundancy Group (RG)

Inter-chassis

Communication

Protocol (ICCP)

Redundancy Group (RG)

DHD

Standby PoA

Active PoA

MC-LAG

LACP

Multi-Chassis LACP


IP FRR: The Principle of Simplicity

―Simplicity is prerequisite for reliability‖ Edsger Dijkstra

"Simplicity is the ultimate sophistication" Leonardo da Vinci

Kiss: Keep It Simple Straighforward

Gains


Theory & Terminology

Path: Outgoing interface and next hop

Backup: an outgoing interface/nhop which is used to replace another

one that went down. It can be:

- another primary ECMP nhop

- a secondary LFA routing path

LFA: Loop-Free Alternate

- N is an LFA for S‘s primary path to D via F if ND < NS + SD

- Node-protecting LFA if: ND < NF + FD

- Downstream LFA if: ND < SD

Computation of LFA occurs after calculating the primary path, therefore

IGP FC performance is not affected

Integrated with LDP

Because LFA is precomputed and installed in the FIB, it provides

deterministic protection(<50ms)


Per-Prefix LFA Algorithm

For IGP route D1, S‘s primary path is link SF.

S checks for each neighbor N (<>F) whether ND1 < NS + SD1 (Eq1)

- ―does the path from the neighbor to D1 avoid me?‖

- If so, it is a loop-free alternate (LFA) to my primary path to D1

- C is an LFA for D1, E is an LFA for D2

S F

C

E

D1

D2


PIM Pre-Signalling of two independent joins

- router is connected to the source via two disjoint branches (requires two plane design)

Upon failure detection, switch-over from primary to backup branch

- IGP detection: order of x00msec

- local detection or passive heartbeat: 50msec

- RTP sequence monitoring: zeroloss

Introducing Multicast Only Fast ReRoute (MoFRR)

IPTV source

Pop1

Pop2 PopN


Network-based HA Example 1/3 Two-Way P2P PW Redundancy with MC-LAG

S S

A A

LACP LACP ICCP ICCP

Both sides must run MC-LAG

Bundle member port state decide PW redundancy state

Active POA send active PW status to remote Router. Standby POA send standby PW status. PW become active ONLY if local and remote Routers are both active. The rest of 3 PWs are in standby mode

Standby POA-2

Active POA-3 Active POA-1

Standby POA-4

Active PW

Standby PW


Network-based HA Example 2/3 H-VPLS Spoke (P2P PW) – coupled & ―one-way‖ mode

The remote VFI Routers don‘t have to run MC-LAG. If it run MC-LAG, it need to be in ―decouple mode‖

Bundle/POA status decide the PW status. On active POA, it will send active PW status on its primary PW and standby status on its backup PW. On the standby POA, it will send standby PW status on both of its primary and backup PW

The spoke PW is P2P PW

S

A

LACP ICCP

Standby POA

Active POA

Active PW

Standby PW

MPLS

VFI

VFI


Network-based HA Example 3/3 L3 Service – IRB/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 L3 service

L3 features like HSRP, VRRP, routing, etc are 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

LACP ICCP

Standby POA

Active POA

MPLS/IP

DHD configuration option 1: DHD

can have default IP gateway pointing

to HSRP/VRRP virtual IP address.

POA need to configure HSRP/VRRP

under BVI interface

Option 2: DHD can also 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

Network Virtualization (nV) Technology


Introduce ASR 9000 Cluster Concept Self-Protected Service Resiliency

Leverage existing IOS-XR

CRS multi-chassis SW

infrastructure

Simplified/Enhanced for

Service Resiliency

Single control plane, single management plane, fully distributed

data plane across two physical chassis one virtual chassis

Eliminate service node failures Towards self-protected

service resiliency

ASR 9000

Cluster/

Virtual Chassis

CRS

Multi-Chassis

Fabric

chassis


Edge

Residential Business

Third-Party Services/ Content

Aggregation

Access

Core

Converged

Cisco

Prime IP NGN

SP Services/ Content

nV

Edge and aggregation

managed as one virtual

system through Cisco Prime

IP NGN.

Single release vehicle

offering feature consistency.

Offers up to 71% reduction

in OPEX over 6 years vs

competitors.

Reduced protocol complexity

between edge and

aggregation

Up to 84,480 GE ports

managed through a single

virtual system

Each device managed

separately.

Inconsistent features

between edge and

aggregation.

Siloed service domains.

Inconsistent service

outages upon device

failure.

Port scale limited to

chassis.

Before: nV Technology After: nV Technology

ASR 9000 nV Technology Overview

nV Cluster

nV Satellite

http://www.vonage.com/lp/US/searchmsn/


ASR 9000 Virtual Chassis Overview

Control Plane EOBC Extension (L1 or L2 connection)

One or two 10G/1G from each RSP

Inter-chassis data link (L1 connection)

10G or 100 G bundle (up to 32 ports)

Single control and management plane, distributed data plane one virtual chassis

Control plane EOBC extension is through special RSP onboard 1G or 10G ports

Data plane extension is through regular LC ports (it can even mix regular data ports and virtual chassis data plane ports on the same LC), not require fabric chassis flexible deployment

Special external EOBC 1G/10G

port s on RSP (new RSP)

Regular 10G or 100G data ports

(Current or future line card)

Active

RSP

Standby

RSP

LC LC LC LC

0

Active

RSP

Standby

RSP

LC LC LC LC

1

Internal

EOBC


Ethernet spoke-and-hub (MC-LAG)

L2 Ethernet Ring (MST/REP-AG, G.8032)

Access dual-homing protocols

MST/REP/G.8032/MST-AG

MC-LAG

MR-APS

L3 IGP/BGP

IP/Service Edge

IP/MPLS

L3 Router dual-homing (L3 ECMP)

Network Dual-Homing Today’s solution: Protocols based approach

Cellsite

Router MLP

Bundle

DACS

L2/L3 service resiliency protocols

HSRP/VRRP, 1-way & 2-way PW redundancy, BGP PIC

CR dual-homing (MR-APS)

Service state sync between two nodes:

DHCP, IGMP, IGMP snooping, ANCP, ARP, etc state sync


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)

Network Dual-Homing Tomorrow’s solution: Self-Protected Service

Cellsite

Router MLP

Bundle

DACS CR dual-homing (MR-APS)

ASR 9000 Cluster

Service state sync between two nodes:

No Need! It’s SINGLE virtual node

All L2 and L3 state are sync’d naturally via control plane extension

L2/L3 service resiliency protocols

NO need! It’s SINGLE virtual node

Access single-homing (greatly simplified)

Regular LAG

Single Router APS

Single routing Adjacency

Replace two nodes with one single virtual node simplify dual-homing to be single-homing

L2/L3 service resiliency protocols:

No need!

It is a single Virtual Node.


L2VPN

– SP 3Play and L2 Business VPN

– DCI (data center inter-connect) (both enterprise and SP DCI)

– Ethernet exchange

Wireline Aggregation

– L3 termination, no IP session

BNG (distributed or centralized)

Wireless Back haul

L3 CPE aggregation

Deployment Scenarios


Deployment Example – L2VPN Service

S S

A A

LACP

Standby

Active

Active PW

Standby PW

Standby

Active

LACP

Solution1: MC-LAG + 2-way PW redundancy

(Currently the best solution in the market)

Solution 2: ASR 9000 Cluster

Active/standby MC-LAG

bandwidth inefficiency

4 PWs with 3 standby

control plane overhead

PW failover time depends on

the number of PWs slow

convergence

Require additional state sync

(for example, IGMP Snooping

table) to speed up service

convergence complex

Active/active regular LAG

Single PW

Link/Node failure is

protected by LAG, PW is even

not aware super fast

convergence

State sync naturally

Simple, fast solution


Deployment Example – L3 Service

Two Routing

Adjacency

CE dual homing to two PE routers. It has 2

separated L3 interface, and run separated

IGP/BGP session with two PE routers

Traffic load balance over the two ECMP paths

When link or node failure, IGP/BGP adjacency

goes down. Protocol re-converge. BGP PIC edge

feature is used for fast BGP convergence

No state sync between two PE routers

Single Routing

Adjacency

CE dual homing to one virtual PE. Single routing

adjacency over the link bundle

Traffic load balance over the link bundle

When link or node failure, bundle remains up, so

upper layer protocol is even not aware super

fast convergence, and simple

State sync naturally


nV Satellite Overview

Satellite

access port

Satellite Discovery and Control Protocol

Install special satellite image on the selected access device to make it ASR 9000 satellite

Running satellite auto discovery and control protocol to make satellite as ―virtual line card‖ of the ASR 9000 Host

From end user point of view, it‘s single virtual system – ASR 9000 nV System. All management, configuration are done on the Host chassis

Satellite and Host could co-locate or in different location. There is no distance limit between satellite and Host

Satellite have zero touch configuration

Satellite

ASR 9000 Host One ASR 9000 nV System

Satellite access port

is represented by

the virtual ―nv‖

interface on the

HOST Fabric links


Power Feeds

• Redundant -48vDC Power Feeds

• Single AC power feed

44x10/100/1000 Mbps Pluggables

• Full Line Rate Packet Processing and Traffic Management

Field Replaceable Fan Tray

• Redundant Fans

• ToD/PSS Output

• Bits Out

4x10G SFP+

• Initially used as Fabric Ports ONLY (could be used as access port in the future)

• Plug-n-Play In-Band Management

• Automatic Discovery and Provisioning

• Co-Located or Remote Distribution

• Environmentally Hardened

1 RU ANSI & ETSI Compliant

LEDs

First Satellite Hardware – ASR 9000v


Satellite – Host Control Plane Satellite discovery and control protocol

Satellite ASR

9000v

ASR 9000

Host

MAC-DA MAC-SA Payload/FCS Control VID CPU CPU

Discovery Phase

• A CDP-like link-level protocol that discovers satellites and maintains a

periodic heartbeat

• Heartbeat sent once every second, used to detect satellite or fabric link

failures. BFD based fast failure detection plan for future release

Control Phase

• Used for Inter-Process Communication between Host and Satellite

• Cisco proprietary protocol over TCP socket for the time being. It could move

to standard in the future

• Get/ Set style messages to provision the satellites and also to retrieve

notifications from the satellite Standardization is considered for future


MAC-DA MAC-SA Payload MAC-DA MAC-SA Payload/FCS nV-tag

VLANs (OPT) VLANs (OPT)

Satellite – Host Data Plane Encapsulation

Satellite ASR

9000v

ASR 9000

Host

MAC-DA MAC-SA Payload VLANs (OPT)

On Satellite

Satellite receive Ethernet frame on its access port

Satellite add special nV-tag, optionally have ingress qos policing, then local xconnect packet to its fabric port

Put packet into fabric port egress queue, transmit packet out On Host

• Host receive the packet on its satellite fabric port

• Check the nV tag, then map the frame to the corresponding satellite virtual

access port

• From there, process packet just as local port, apply potential L2/L3 features,

qos, ACL, etc

• Packet is forwarded out of local port, or satellite fabric port to same or

different satellite

Similar on reverse

direction


Virtualized Transport – Operational Models L1 connection, spoke-and-hub

Satellite

Dual home to cluster (or

two HOSTs)

Satellite

Satellite

Satellite

ASR 9000 Cluster

ASR 9000 Cluster

Dual home to cluster (or two

HOSTs) with uplink bundle

Single home

Single home with uplink

bundle

IN IOS-XR 4.2.1


Operational Savings

Low Cost

High Resiliency

Virtual router is always on

Towards 50msec failure protection

with very high service scale

Simplify network protocol based

resiliency to be internal system control

plane based

Leverage ASR9K HOST

ultra-high MD control plane

scale and feature set, remove

complex feature from satellite

low cost satellite hardware

One network element to manage a network cloud

simple service provisioning, image upgrading,

configuration, etc

Rapid service deployment plug-and-play, self-

managed access

Virtualized Transport – Value Proposition

Network and Services Management


A modular suite of applications

A-to-Z management for next-generation packet and transport networks

Designed for lower Total Cost of Ownership (TCO)

Introducing Cisco Prime™ Experience Lifecycle Management


Domain Managers

Provide core information for devices and technologies

Automated discovery and configuration management

Network visibility

Cisco PrimeIntegrated Suite for Experience Lifecycle Management

Optimized resource management

Design

Intelligent fulfillment

Fulfill

Automated diagnostic workflows

Analyze Automated service assurance

Assure


Optical Switches Video Mobile Routers Gateways Servers/Guests/

Machine Instances

Southbound Mediation

Domain Managers

Common Data Model

Service Bus

Lifecycle Applications

Northbound Mediation

Consistent look and feel

Integrated Framework

Embedded database

Real-Time Discovery

Common HA

Virtual machines (VMs)

Cisco UCS, commodity hardware, Sun

Cisco Prime Architecture


• Centralized user portal, correlation engine, and common data model

• Assurance, change and configuration management of packet networks

• Visualization of physical and virtual RAN topologies

• Flexible, automated network service provisioning including RAN backhaul connections

• Zero-touch deployment

• Scalable, reliable and integrated DNS, DHCP, and IP address

management for IPv4 and IPv6

• Fast, easy, actionable information across devices and services • Metrics gathering and performance reporting for backhaul

connections, per service, per geography

Prime Central

Prime Network

Prime Fulfillment

Prime Network Registrar

Prime Performance Manager

Cisco Prime ModulesMobile RAN Backhaul and Carrier Ethernet Support


Centralized User Portal

Prime portal provides:

Single point of entry into the network for operator access to all information they need

Reduced operational costs using an integrated framework for operators and administrators

Increased efficiency with seamless transition between functional areas

Unified Inventory

Access, Aggregation, Edge and Core

Common Event / Alarm Management


Service Design and Activation

Accelerate service deployment for both Carrier Ethernet and IP-RAN services (EoMPLS, VPLS, Ethernet Access EvC, SAToP, CESoPSN and ATM/IMA over pseudowire emulation) with easy to use point and click service creation wizards

Eliminate manual errors with automation

Resource Pools

Policy

Service Provisioning Lifecycle


Network Discovery

Faster and more cost effective Carrier Ethernet and RAN Backhaul management with automatic discovery of all network components

Complete end-to-end visibility of all network elements, covering a wide variety of Cisco Products (over 50 different platforms) from edge to access, aggregation and core

Physical and Logical Maps

Logical and

Physical

Inventory

Maps include integrated

third-party devices

• Physical and logical topologies

• Multivendor support


In-Depth Visibility into Carrier Ethernet Networks VLAN Topologies

Drastically reduced troubleshooting time to identify device configuration or network errors using virtual connection (e.g., VLAN) graphical representations to quickly identify associated devices and their configuration

Topology to represent:

STP Forwarding decision

Root bridge

REP Topologies

VLAN Topology

Blocked Port

REP ID

Root Bridge


In-Depth Visibility into Carrier Ethernet Networks Ethernet Service Virtualization

Ethernet Service

VPLS Topology

Customer VLANs

SP VLAN

SVI

Pseudowire link

Unique graphical view representation for complex Ethernet services to help users analyse how a service traverses multiple domains and technologies


In-Depth Visibility into Carrier Ethernet Networks Troubleshooting via CFM (802.1ag)

Local and Remote Maintenance end Points (MEPs)

Nested Hierarchies

Easier Carrier Ethernet troubleshooting with CFM leveraging Prime:

• CFM hierarchy configuration discovery and reported in hierarchal views

• CFM ping, CFM trace and other built-in scripts available

Maintenance

Association CFM Levels

Maintenance

Domains


Third-Party Device Support

Out-of-the-Box Support for:

DragonWave (microwave radio)

Alcatel-Lucent

Huawei

Juniper

RAD

NEC iPasolink

Basic logical and physical

discovery for third-party

devices supporting the

standard MIB2

• Multivendor ready

• Easy integration of

other third-party

microwave devices

DragonWave microwave


Summary

Carrier Ethernet Aggregation System with Access Agnostic features

Runs Residential, Business, Wholesale and Mobile services on the same platform

Based on MPLS and MPLS-TP

Supports sub-50 ms restoration for all services

Massively scalable

Carrier-grade Management via Cisco Prime

Carrier Ethernet Transport...

Documents

Transcript of Carrier Ethernet Transport...