2017 Expert Packet Workshop V3 + Exercise

2017 Expert Packet Workshop
Including 6.16/8.5 and 6500 R12.1 Features
Marc Lefebvre
Jean-Luc Dupont
Core Systems and Network engineering
May, 2017
Copyright © Ciena Corporation 2016. All rights reserved. Confidential & Proprietary.
Software Evolution for MPLS and IP
Long-Term View (Multi-Year) vRR
vPCE vPCE
Metro Ethernet MPLS Metro Ethernet

Area-1 Core Area-2
You
Are
MPLS Seamless VPNs & Business VPN
Here Enhancements MPLS
VPNs
Transport SDN Control
Control Plane Netconf / YANG iBGP MP-BGP BGP_LS SDN Control
BGP_LU (RFC 3107) BGP_LS
PCE-P
Service Layer PW VPWS L2 PW Control Word EVPN VPWS EVPN (RFC 7432) IRB EVPN
IRB VPWS TDM PW L3 VPN (RFC 4634) VxLAN 6PE/6VPE
Transport Layer MPLS-TE Uni-Dir RSVP-TE LDP-IGP Sync Segment Routing IPv6
MPLS TP-TE LDP (MPLS)
Gateway
Reminder: Each product carries its own roadmap to adopt the features.
If you have a questions regarding a feature on a particular product,
please
Copyright © Ciena Corporation 2016. All rights reserved. Confidential & Proprietary.review the roadmaps in Salesforce or contact the PLM product owner. 2
Thursday May 11th – Day 1 – Packet Expert Workshop (Host: J-L Dupont)
Topic Content Description Approx Sch
Introduction 08:00 – 08:15
Pseudo-Wire Service Architecture • OAM, Co-Routed/Associated 08:15– 09:30
Service Data Plane • Label Structure
MPLS-TP vs MPLS-TE, MPLS Label Distribution • IGP, RSVP (PATH vs RESV), LDP (T-LDP vs I-LDP)
Transport Tunnel/Label Distribution • Static MPLS-TP, Dynamic MPLS-TP
PW Label Distribution • Dynamic MPLS-TE (IP/MPLS)
Transport Tunnel/Label Distribution • Multi-Segment PW
Break 09:30 – 09:45
Non-Dynamic MPLS-TP Packet Features • Static MPLS-TP (eMOTR, T Series) 09:45 – 11:30
(6500 R12.1, SAOS 6.16 & 8.5) • MPLS Trigger – OTN Signal Degrade Switchover
• SyncE (Packet Fabric, S&T Series)
• LAG & MC-LAG (6500, 8700)
• Y1731 SLM, EOAM 802.3ah
• Egress Shaping
Dynamic CO-Routed MPLS-TP Basic Features (6.16/8.5 Features) • ISIS-TE 11:30 – 12:15
CO-Routed Transport Label Distribution • RSVP-TE
• CSPF
Lunch 12:15 – 13:15
PSB/RSB • CSPF, T-LDP, FEC 129 13:15 – 14:15
PW Label Signaling
Break 14:15 – 14:45
Resiliency • IP-BFD, Auto Backup, Re-Optimization, MBB , Control Plane 14:45 – 17:00
Graceful Restart Resiliency
Copyright © Ciena Corporation 2016. All rights reserved. Confidential & Proprietary. 3
Friday May 12th – Day 2 – Packet Expert Workshop (Host: J-L Dupont)
Topic Content Description Approx Sch
Review Day 4 08:00 – 08:15
Dynamic CO-Routed Advanced MPLS-TP Traffic Engineering • SRLG 08:15– 09:30
Features (Resiliency (Cont’d) • Administrative Groups (Resource Affinity)
Bandwidth Management & Reservation • Auto Bandwidth
CAC vs Utilization • LSP Bandwidth Resizing Triggers
Break 09:30 – 09:45

MPLS QoS DIFFSERV-TE 09:45 – 12:15
• CLASS Type
• Bandwidth Constraints (MAM) (RDM)
• Queues/Queue Groups
Lunch 12:15 – 13:15

Hands-on exercises Exercise 1 : CATP exercises 13:15 – 14:45
Exercise 2 : Preconfigured but explore via show commands)
Break 14:45 – 15:15
Whiteboard engineering exercises Engineer an Access network with Cisco ISIS core and dual gateway 15:15 – 17:00
that supports a Mix of on demand TDM services and IPTV in a
network where some paths are going over possibly flaky and
common physical infrastructure.
MPLS Service Architecture Overview
Service Architecture Layered view
Service View
VPWS VPWS
Customer Ethernet Data

Service
Pseudowire View
PW OAM
Primary Pseudowire
MPLS Tunnels View

GAL/GACH BFD
Primary Tunnel
BackupTunnel GAL/GACH BFD
Physical Layer VIew
1G/10G Ethernet
Layer 2 Service Data Plane
Label Basics
Field Name Size (bits) Purpose

Label MPLS Label 20 The MPLS label Value
EXP* Experimental 3 QoS mapping from TOS/COS bits
S Bottom of Stack 1 Flag to indicate bottom of MPLS stack
TTL Time to Live 8 Packet lifetime in MPLS hops
•
•
•
•
•
L2 Service Options
VPWS vs VPLS
Service View
VPWS VPWS
VPLS VPLS
VPLS
VPWS Service
VPLS Service
VPWS VPLS
 From the customer’s perspective it looks as if a  allows the connection of multiple sites in a single
leased link exists between the two locations. bridged domain over a provider managed MPLS
 No MAC learning required network
 From the customer’s perspective it looks as if all
sites are connected to a single switched VLAN
 MAC Learning
Pseudowires
Pseudowire View
PW OAM
MPLS-TP Pseudowires OAM
Pseudowire Virtual Circuit Connectivity Verification
 VCCV is a control channel between a pseudowire's ingress and egress points over which connectivity verification messages can be sent.
 The goal of VCCV is to verify and further diagnose the pseudowire forwarding path. To this end, VCCV is comprised of different components:
 a means of signaling VCCV capabilities to a peer PE
 an encapsulation for the VCCV control channel messages that allows the receiving PE to intercept, interpret, and process them locally as OAM messages,
and
 specifications for the operation of the various VCCV operational modes transmitted within the VCCV messages.
 When a pseudowire is first signaled using the Label Distribution Protocol (LDP) [RFC4447] a message is sent from the initiating PE to the
receiving PE requesting that a pseudowire be set up. This message has been extended to include VCCV capability information. The VCCV
capability information indicates to the receiving PE which combinations of Control Channel (CC) and Connectivity Verification (CV) Types it is
capable of receiving.
 It should be noted that because of the number of combinations of optional and mandatory data-plane encapsulations for PW data traffic,
VCCV defines a number of Control Channel (CC) and Connectivity Verification (CV) types in order to support as many of these as possible.
CC Types CV Types
Type 1: PWE3 Control Word with 0001b as first nibble Type 1: ICMP Ping
(PW-ACH: [RFC4385])
Type 2: MPLS Router Alert Label Type 2: LSP Ping
Type 3: MPLS PW Label with TTL == 1
Type 4: GACH for MPLS-TP
PW OAM frame breakdown
PW Label
GAL = 13 Generic Alert Label
0001 0x027 PW Ach Channel
Refresh timer Len A Flags PW OAM Header
0x96A Len=4 PW Status TLV

PW status code
Field Size Description

OAM Channel 4-bits Value = 0001b indicates OAM frame
Version 4-bits Set to zero
Reserved 8-bits Set to zero
ACH channel type 16-bits Value = 0x0027 indicates the PW OAM message
Refresh Timer 16-bits Value 1 to 65635 represents time interval between PW status message. Value zero indicates
infinite to mean never refresh
TLV length 8-bits Total length of all TLVs

A (ACK bit) 1-bit When set to 1 means acknowledge for the included PW status. Refresh timer with ACK set means
requested timer value (desired value from the node ACKing)
Flags 7-bits Set to zero on send and ignored on receive

TLVs Variable Only one TLV is defined – PW status TLV
MPLS-TP PW OAM Packet Capture
eg. Status OAM
0x0025 On demand CV
0x0027 PW OAM Message
0x0028 MAC Withdraw
MPLS-TP PW OAM Packet Capture
eg. PW Ping
Pseudowire Options
Static vs Dynamic
Static Pseudowire View

Manually
Configured Manually
configured
PW OAM
Primary Pseudowire
Dynamic Pseudowire View

OSPF/ISIS
PW Signaled via
TLDP PW Signaled via
TLDP
PW OAM
T-LDP
Primary Pseudowire
PW Options
Dynamic PW
Why an IGP?
Dynamic PW uses T-LDP to signal service labels
T-LDP uses TCP and UDP which requires IP routing
IP Routing
T-LDP
TLDP = Targeted LDP
(not to be confused with Topology LDP)
MPLS Transport Tunnels
MPLS Tunnels View

GAL/GACH BFD *
Primary Tunnel
BackupTunnel GAL/GACH BFD *
* GAL/GACH : for MPLS-TP Tunnels
MPLS-TP OAM - Generic Associated Channel
•
•
Tunnel Label (same Label as Data Plane LSP)

GAL (always Label 13)
GACH (covered on later slide)
OAM Packet
MPLS-TP OAM – LSP CC and CV using BFD Packet Format
Standby
Bidirectional
P1 P2
Tunnel
OAM packets can be sent at

50 ms 3.33, 10, 100 or 1000 ms intervals to monitor the
CE-1 PE1 switch data path. PE2 CE-2
P3 P4 Active
Bidirectional
Tunnel
Data Packet CC OAM Packet CV OAM Packet

MAC MAC MAC
1 CV for every 10 CC to verify
Tunnel Label Tunnel Label
connectivity to the intended
Tunnel Label
far end LER.
PW Label GALLabel=13 GALLabel=13
Original Frame Gach Gach

BFD BFD
Source MEP TLV
0 4 8 16 31 0 4 8 16 31
0001
ACH
Reserved 0xHH CC Code Point
ACh Overhead ACH
0001 Reserved 0xHH CV Code Point
Version Version
BFD Control Packet BFD Control Packet
CC/BFD Packet Format Unique MEP-ID of source of the BFD packet
CV/BFD Packet Format

MPLS-TP OAM CC - BFD Packet Capture
0x0022 MPLS-TP CC Message

0x0023 MPLS-TP CV Message
Transport MPLS Tunnels Options
MPLS Static Tunnels View
Primary Tunnel Manually

BackupTunnel configured
Associated MPLS-TP Tunnels

Corouted MPLS-TP
MPLS Dynamic Tunnels View
OSPF/ISIS
Primary Tunnel RSVP

BackupTunnel
Associated MPLS-TP Tunnels 6.16

Associated IP/MPLS Tunnels &
Corouted MPLS-TP Tunnels with ISIS-TE 8.5
Dynamic MPLS Transport Tunnel
Why an IGP?
Dynamic MPLS Tunnels use RSVP to signal Transport labels
RSVP uses messages that are routed over IP.
IP Routing
LSP is configured at the
initiator end only
RSVP PATH
1
2c 2b 2a
RSVP RESV RSVP RESV RSVP RESV
Label z Label y Label x
Step 1 : A uni-directional tunnel is created using RSVP

Step 2 : The same is repeated in the opposite direction.
Step 3 : The two tunnels are manually Associated to create a bidirectional Transport Entity
Co-Routed Dynamic MPLS-TP features 6.16/8.5
Bi-directional LSP setup with single PATH+RESV PDU exchange
PATH message upstream label creates reverse LSP from D to A
PATH
100 200 300
Upstream Label
100 200 300
A B C D
600 500 400
Downstream Label
RESV
600 500 400
RESV message label creates forward LSP from A to D
Control Plane Hops shown but note that actual LSP is setup on
TE links which is not necessarily carrying the PDU
Example 1 – All Dynamic
Service View
VPWS VPWS

Service
Pseudowire View
OSPF/ISIS
PW Signaled via
TLDP
PW OAM
T-LDP
Primary Pseudowire

OSPF/ISIS
Primary Tunnel RSVP

BackupTunnel
Physical Layer VIew
1G/10G Ethernet
Example 2 – All Static
Service View
VPWS VPWS

Service

Manually
Configured Manually
configured
Primary Pseudowire

Physical Layer VIew
1G/10G Ethernet
Example 3 – Dynamic PW with Static MPLS
Service View
VPWS VPWS

Service
Pseudowire View
OSPF/ISIS
PW Signaled via
TLDP
PW OAM
T-LDP
Primary Pseudowire

Physical Layer VIew
1G/10G Ethernet
Example 4 – Static PW with Dynamic MPLS
Service View
VPWS VPWS

Service

Manually
Configured Manually
configured
Primary Pseudowire

OSPF/ISIS
Primary Tunnel RSVP

BackupTunnel
Physical Layer VIew
1G/10G Ethernet
IP Routing - FAQ
Traffic Engineering - FAQ
Multi-Segment Pseudowire
MPLS Enhancements
MS-PW architecture
inter-AS PW service
MPLS Enhancements
Multi-segment pseudo wire: Supporting stitching Static VCs – Operational considerations
6500 T-Series PKT/OTN fabric
6500 T-series PKT/OTN fabric
Summary of packet on T-series PKT/OTN cross-connect
Summary of packet on T-series PKT/OTN cross-connect, cont’d
Summary of packet on T-series PKT/OTN cross-connect, cont’d
Packet hardware requirements
6500 Packet cross-connect SAOS CLI access
6500 Packet cross-connect SNMP access
LAG Port aggregation
Flood containment design considerations
Forwarding Database (FDB)
L2 service scalability
802.1ag/Y.1731 support and scalability
Link conditioning: VLLI
P P P P
1 2 2 1
Node A Node B
LAG*
P P
2 2
P P P P
1 Node A 3 3 Node B 1
P P
2 MPLS-TP 2
P P P P
1 Node A 3 3 Node B 1
MPLS-TP tunnels
6500_0007*> gmpls tp-tunnel create <TAB>

static-ingress-corout static-egress-corout
static-transit-corout
MPLS-TP on eMOTR
MPLS-TP on eMOTR
Summary
MPLS-TP on eMOTR
Summary, cont’d
6500 eMOTR enhancements
Equipment Group Modes
MPLS-TP - IP interfaces
Static ARP
1.1.1.1 2.2.2.2
S1 S2
S3
3.3.3.3
S1
# cpu-interface sub-interface create cpu-subinterface toS3 cpu-egress-l2-transform push-8100.100.5
# sub-port create sub-port toS3 parent-port 3/5 classifier-precedence 100
# sub-port add sub-port toS3 class-element 1 vtag-stack 100
# virtual-switch create toS3
# virtual-switch interface attach sub-port toS3 vs toS3
# # interface create ip-interface toS3 ip 192.18.1.2/30 vs toS3
# arp static add destination 192.18.1.1 mac 00:04:95:09:6c:8d ip-interface toS3
# gmpls tp-tunnel create static-ingress-corout toS3 dest-ip 3.3.3.3 next-hop-ip 192.18.1.1 forward-out-label
3000 reverse-in-label 3000
> arp static show

+----------------+------------------+--------------------+
| DestinationIp | DMAC | ifName (ifIndex) |
+----------------+------------------+--------------------+
|10.1.1.1 |00:04:95:09:6c:8d |toS3 (19)|
+----------------+------------------+--------------------+
MPLS-TP tunnels
6500_0007*> gmpls tp-tunnel create <TAB>

static-ingress-corout static-egress-corout
static-transit-corout
MPLS-TP LSP ping/traceroute
MPLS-TP LSP ping/traceroute
6500-1 6500-2
• MPLS Ping: 10.1.2.0/30 2.2.2.2
• MPLS Echo Request is sent in-band with LSP.
• MPLS Echo Reply can be sent:
1.1.1.1
• In-band with LSP with or without IP/UDP
encapsulation
10.2.4.0/30
10.1.3.0/30
Tunnel Header Tunnel Header Tunnel Header

GAL Header GAL IP Header 4.4.4.4
GAch Header (GAch GAch Header (GAch UDP Header
Type 0x21) Type 0x25) MPLS Echo Payload
IP Header MPLS Echo Payload
IPv4 reply-mode 10.3.4.0/30
UDP Header LSP reply-mode without 6500-3 3.3.3.3 6500-4
MPLS Echo Payload IP/UDP header
Default LSP reply-mode

with IP/UDP header
6500-1> mpls ping tp-tunnel-ingress-corout tunnel_to_S4

MPLS Ping with count (5) ttl (255) timeout (1000 ms) size (118 bytes)
Legend:'!' - Success, 'X' - Error
! Seq: 1 Latency: 7 ms
--------------- Statistics ---------------

5 packets transmitted, 5 packets received
round-trip (ms) min/avg/max = 5/5/7
Same applies for Trace route
MPLS-TP: PW status over static PW
MPLS-TP: VCCV profile overview
MPLS-TP: VCCV profile summary
Releases PW Type VCCV Profile CC-Type selected Tunnel CC-Type

Used
6500 12.1 Static PW Default 3&4 Bidirectional 4
eMOTR
6500 12.1 Static PW Present Profile must have Bidirectional 4
eMOTR ONLY ONE (4);
MPLS-TP: eMOTR MPLS OAM Solution
AIS LSP BFD

Nature of protocol Reactive Proactive
Monitors Previous Hop IP LSP Datapath

adjacency of a
tunnel
Supported Static TP tunnels Static TP tunnels
MPLS-TP: BFD
Passive-10sec
6500 PKT fabric MPLS DEI Transparency
6500 PKT fabric
Legend
UNI
I-NNI
Traffic Flow QiQ
E-NNI
QiQ
802.1q QiQ
MPLS
6500 PKT fabric
Ingress Frame Ingress FCOS to RCOS Egress RCOS to FCOS Configurable

options available
802.1q Frame QiQ Frame Configurable Mapping Configurable QiQ Configurable
for RCOS to
Egress Mapping MPLS
Egress FCOS and FCOS
Pbits DEI Pbits DEI RCOS RCOL Pbits DEI EXP to RCOS
w Color mappings
1 1 1 1 7
7 7 48 7
0 0 0 0 7
1 1 1 1 6
6 6 56 6
0 0 0 0 6
1 1 1 1 5
5 5 40 5 Number of
0 0 0 0 5
Classes is
1 1 1 1 4
4 4 32 4 reduced if color is
0 0 0 0 4 carried in EXP
1 1 1 1 2 bits. Yellow is
3 3
0 0 0 0 3 carried in the
24 3
1 1 1 1 2 lower EXP value.
2 2
0 0 0 0 3
1 1 1 1 0
1 1
0 0 0 0 1
8 1
1 1 1 1 0
0 0
0 0 0 0 1
6500 PKT fabric
eMOTR MPLS DEI Transparency
Legend
UNI
I-NNI
Traffic Flow QiQ
E-NNI
QiQ
802.1q QiQ
MPLS
Ingress Frame Ingress FCOS to RCOS Egress RCOS to FCOS Configurable
options available
802.1q Frame QiQ Frame Configurable Mapping Configurable QiQ Configurable
for RCOS to
Egress Mapping MPLS
Egress FCOS and FCOS
Pbits DEI Pbits DEI RCOS RCOL Pbits DEI EXP to RCOS
w Color mappings
1 1 1 1 7
7 7 48 7
0 0 0 0 7
1 1 1 1 6
6 6 56 6
0 0 0 0 6
1 1 1 1 5
5 5 40 5 Number of
0 0 0 0 5
Classes is
1 1 1 1 4
4 4 32 4 reduced if color is
0 0 0 0 4 carried in EXP
1 1 1 1 2 bits. Yellow is
3 3
0 0 0 0 3 carried in the
24 3
1 1 1 1 2 lower EXP value.
2 2
0 0 0 0 3
1 1 1 1 0
1 1
0 0 0 0 1
8 1
1 1 1 1 0
0 0
0 0 0 0 1
•
Act/Stby LAG on S-Series and T-Series PKT fabric
6500 S-Series and T-Series PKT fabric Active/Standby LAG
Overview
Active/Standby LAG Active/Standby DLAG Active/Standby LAG
PKT I/F PKT I/F D PKT I/F

-
L
D A
- G
L
A
G
VS ctive
L
A
G
VS ctive
1
VS
PKT I/F PKT I/F
Description
Note: Refer to the 6500 Data Application Guide Part 1 for engineering rules on PKT I/F LAG
configuration
Configuration example with Active/Standby LAG
6500 Node A 6500 Node B

Single PKT fabric I/F Distributed PKT fabric I/F
PKT I/F #1 PFT I/F #9/10
1/3 9/2
1/2 9/1
Router Router
D
L L
A VS VS
G
MPLS-TP A
G
1/1 10/1 10/2

1/4
Act/Stby LAG on eMOTR
6500 eMOTR Active/Standby LAG
Overview
Active/Standby LAG Active/Standby DLAG Active/Standby LAG
eMOTR eMOTR D eMOTR

-
L
D A
- G
L
A
G
VS ctive
L
A
G
VS ctive
1
VS
eMOTR eMOTR
Description
Note: Refer to the 6500 Data Application Guide Part 1 for engineering rules on eMOTR LAG
configuration
G.8032 Configuration example with Active/Standby LAG and DLAG
6500 Node A 6500 Node B

Single eMOTR card Mated eMOTR cards
eMOTR #1 eMOTR #101
1/3 9/2
1/2 9/1
Router Router
D
L L
A VS VS
G
G.8032 ring A
G
1/1 10/1 10/2

1/4
MC-LAG on 6500 S-Series PKT fabric
Introduction
802.1ax LAG
802.1ax LAG 6500
DHD PKT
Redundancy
6500
SDS SDS ICL Group (RG)
PKT
6500
(a) Standard Link-aggregation PKT
(b) Multi-chassis Link-aggregation
Feature Description
6500 3rd party switch

6500
PKT PKT
* Supported with
one of the RGs
ICL
SDS ICL being a 3rd party
RG
6500 3rd party switch

6500
PKT PKT
(a) Triangle topology (b) Square topology
G.8032 support
6500
PKT
SDS ICL G.8032
6500
PKT
MPLS support
6500
PKT
SDS ICL VPLS Mesh
6500
PKT
Configuration
Usage
Usage
Operational considerations
OTN SD Enhancements on S-Series PKT fabric
OTN SD Enhancements
MPLS-TP Signal Degrade protection trigger
eMOTR OTN Signal Degrade
OTN signal degrade detection
6500 S-Series PKT fabric Y.1731 enhancements
6500 S-Series PKT fabric Y.1731 Synthetic Loss Measurement (SLM)
Overview
6500 S-Series PKT fabric Y.1731 Synthetic Loss Measurement (SLM)
Example
6500 S-Series PKT fabric Y.1731 enhancements
Engineering rules for PKT/OTN I/F circuit packs
eMOTR SLM Software Solution
Y.1731 Synthetic Loss Measurement (SLM) overview
Y.1731 Synthetic Loss Measurement (SLM) example
Y.1731 Synthetic Loss Measurement (SLM) engineering rules
eMOTR Edge - SLM Hardware Solution
enhancements
•
•
•
•
•
•
•
•
•
•
•
•
•
•
eMOTR – CFM Enhancements – Extended Mode
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
eMOTR eMOTR
MPLS-TP
Up Up
Functionality Frame Periodicity Standalone eMOTR Sessions per Card in Sessions per Mated
Mated Equipment Group Equipment Group
3.3ms, 10ms Not supported Not supported Not supported
FPGA (TBD) CCMs 100 ms 10 10 20
1s, 10s, 1m,10m 100 100 200
Down MEP
3.3 ms, 10ms, 100ms, 1s,
100 100 200
10s, 1m,10m
T3 Based CCMs
UP MEP
(on L2 AC) 100ms, 1s, 10s, 1m,10m 2000 1000 2000
UP MEP
3.3 ms, 10ms 100 100 200
Loopback 1s 2000 2000 2000
100ms 200 200 200

Delay Measurement
1s 2000 2000 2000
Loss Measurement 1s 2000 2000 2000
100ms 200 200 200

SLM
(eMOTR-1/2 & Edge)
1s 2000 2000 2000
Maintenance Intermediate
- 256 256 256
Points
Remote MEP’s - 2400 2400 2400
EOAM (802.3ah) Ethernet in the first mile
802.3ah OAM
Description
802.3ah OAM
Key functions
802.3ah OAM
Key functions, cont’d
802.3ah OAM
Active/passive mode
802.3ah OAM
Active/passive mode, cont’d
Active
DTE
Active
Active DTE
DTE Active
Active
DTE
DTE
Passive
DTE
Passive Active
DTE DTE
Active
DTE Active
DTE
Passive
DTE
Active
DTE Active
DTE
Passive
DTE
802.3ah OAM
Configure EOAM on a port
802.3ah OAM
Configure EOAM on a port, cont’d
802.3ah OAM
Loopbacks
+-------------------------------------------- Oam Loopback Port Statistics ----------------------------------------------+

| Port | Lb |Lb Ignore|PeerLb | LbPduTx | LbPduRx | LbPduRxError | Lb Ctrl | Lb Ctrl |
| | Status | State |Support| | | | Tx | Rx |
+------+--------+---------+-------+---------------------+---------------------+---------------------+----------+---------+
|1/9 | Lb-Rx |Process | Yes | 364 | 364 | 0 | 0 | 3 |
+------+--------+---------+-------+---------------------+---------------------+---------------------+----------+---------+
+-------------------------------------------- Oam Loopback Port Statistics ----------------------------------------------+

| Port | Lb |Lb Ignore|PeerLb | LbPduTx | LbPduRx | LbPduRxError | Lb Ctrl | Lb Ctrl |
| | Status | State |Support| | | | Tx | Rx |
+------+--------+---------+-------+---------------------+---------------------+---------------------+----------+---------+
|1/10 | Lb-Tx |Ignore | Yes | 364 | 364 | 0 | 3 | 0 |
+------+--------+---------+-------+---------------------+---------------------+---------------------+----------+---------+
802.3ah OAM
SNMP
802.3ah OAM
Interoperability
eMOTR Configurable Queue Scheduler
Configurable queue scheduler
eMOTR E-Tree Service Topologies
E-TREE for non-MPLS services UNI
Rooted
UNI Multipoint EVC
UNI
OMESJ-02*> private-forwarding-group show
+----------------- PRIVATE FORWARDING GROUPS ----------------+

| | Forwarding Policies |
| Profile | Group A | Group B |
+---------------------------------+-------------+------------+
| Default_E-TREE | A,B | A |
| Default_E-LAN | A,B | A,B |
+---------------------------------+-------------+------------+
Packet OTR for eMOTR Edge
SAOS 8.5 TOI
Egress Shaping Enhancement
SAOS 8.5 TOI
Hiearchical Shaping for VC Shaping
8.3 Egress Shaping
DEFAULT EGRESS QOS HIERARCHY (PER-PORT)
CIR/CBS
WRED
Q7 EIR/EBS
CIR/CBS
WRED EIR/EBS
Q6
CIR/CBS
WRED EIR/EBS
Q5
Default Port Scheduler
Root Port Scheduler

CIR/CBS
WRED EIR/EBS
Q4 Egress
RCOS 0- RCOS Port
VS SubPort
63 Queue Map
CIR/CBS
WRED EIR/EBS
Q3
CIR/CBS
WRED
Q2 EIR/EBS
CIR/CBS
WRED EIR/EBS
Q1
CIR/CBS
WRED EIR/EBS
Q0
Default
Queue-Group
8.4 Egress BW Shaping Enhancements
CUSTOM HIERARCHY – 3 LEVELS
(EG. PER MEF SUB PORT OR PER TUNNEL) 1
CIR/CBS
RCOS 2
WRED
Q7 EIR/EBS
Queue Map
Scheduler
Default
  
  CIR/CBS 
WRED EIR/EBS
Q0
default
VS1 SubPort Queue-Group A
SubPort
Root Port Scheduler

CIR/CBS
3
WRED
Q3 EIR/EBS
VS2
Scheduler
MPLS VC
Custom
  
MPLS Tunnel   CIR/CBS 
VS3 MPLS VC
RCOS 0- WRED
Q0 EIR/EBS
63
Custom
Queue-Group B
MPLS Tunnel
CIR/CBS
VS4 SubPort WRED
Q3 EIR/EBS
Scheduler
Custom
  
  CIR/CBS 
WRED EIR/EBS
Q0
Custom
Queue-Group C
Copyright © Ciena Corporation 2016. All rights reserved. Confidential & Proprietary. SubPort 126
CUSTOM HIERARCHY – 4 LEVELS
(EG. FOR STATIC VC SHAPING)
MPLS Tunnel
CUSTOM HIERARCHY – 4 LEVELS 1
2
(EG. FOR STATIC VC SHAPING) CIR/CBS 3
1 Tap Scheduler
RCOS WRED
EIR/EBS
Queue Map Q7
Scheduler
Custom
  
VS1 MPLS VC   CIR/CBS 
WRED
Q0 EIR/EBS
RCOS 0-
63 Custom
Queue-Group A
MPLS VC
Root Port Scheduler

MPLS Tunnel
CIR/CBS
4
WRED
Q7 EIR/EBS
Scheduler
Custom
  
VS2 MPLS VC

  CIR/CBS
WRED EIR/EBS
Q0
1 Tap Scheduler
Custom
Queue-Group B
MPLS Tunnel MPLS VC
CIR/CBS
WRED
Q3 EIR/EBS
Scheduler
Custom
  
VS3 MPLS VC   CIR/CBS 
WRED EIR/EBS
Q0
Custom
Queue-Group C
MPLS VC MPLS Tunnel
CIR =10% (.4G)
Example EIR = 0

 CIR/CBS
RCOS
EIR/EBS
Queue Q1
Scheduler
Custom
Map 
(8->Q1)  
VS1 MPLS VC CIR =100% (.4G) 
EIR = 0
RCOS
=8 Custom CIR =10% (.4G) CIR =4G
10G
For Queue-Group A EIR = 0 EIR =0
pbit1 MPLS VC
all

Root Port Scheduler

pbits
 CIR/CBS
1 Tap Scheduler
Q1 EIR/EBS
Scheduler
Custom

 
VS2 MPLS VC
MPLS CIR =100% (.4G) 
Tunnel
EIR = 0
Custom CIR =25% (1 G)
10G Queue-Group B
MPLS VC EIR =0
pbit2 CIR =8G
 EIR =10G
CIR/CBS

Q1 EIR/EBS
Scheduler
Custom


CIR =100% (1G) 
VS3 MPLS VC

EIR = 0
10G Custom
Queue-Group C
pbit3 MPLS VC MPLS
Copyright © Ciena Corporation 2016. All rights reserved. Confidential & Proprietary. Tunnel 129
Example - Configuration
1. Set the CIR of the port to be used
Shaper compensation may
traffic-services queuing egress-port-root-scheduler set scheduler 3/10-Root cir 8000000 cbs 128 need to be created/adjusted
2. Create a custom Queue group profile
traffic-services queuing queue-group-profile create profile ALLQueue1 shaper-compensation -30
3. Create the Queues within the custom Queue Group profile

traffic-services queuing queue-group-profile set queue 1 profile ALLQueue1 cbs 21 eir 0 cir-percent 100
4. Create the Scheduler profiles

traffic-services queuing scheduler-profile create profile CIR10 cbs 21 eir 0 cir-policy cir-as-percent cir-percent 10
Ability to define custom schedulers
traffic-services queuing scheduler-profile create profile CIR25 cbs 21 eir 0 cir-policy cir-as-percent cir-percent 25
traffic-services queuing scheduler-profile create profile CIR50OneTap tap-point-count 1 scheduler-algorithm round-robin cir 4000000
with CIR %.
cbs 21 eir 0 cir-policy no-auto-adjust
One Tap Policy -> No-auto-adjust only
5. Create the Scheduler instances
traffic-services queuing scheduler-profile add profile CIR50OneTap instance 1 port 3/10 parent-scheduler 3/10-Root
traffic-services queuing scheduler-profile add profile CIR10 instance 1 port 3/10 parent-scheduler CIR50OneTap parent-instance 1
MPLS tunnels do not need to be

4. Create the queue Group instances
explicitely assigned a scheduler.
traffic-services queuing queue-group-profile add profile ALLQueue1 instance 1 port 3/10 parent-scheduler CIR10 parent-instance 1
6. Associate the Queue-profile with PW
mpls l2-vpn create static-vc VCShapingTestVC1 pw-id 141 peer 14.14.14.14 in-label 21411 out-label 21141 tp-tunnel-ingr-corout S1S14Static queue-group ALLQueue1 queue-group-instance 1
SAOS 8.5 TOI
CIR % Policies
Advanced CIR Configuration Policies
Summary : if we have a scheduler instance with a % based

policy, then all components downstream from it in the QOS
tree will pick up its % value of the parent CIR.
Not all CIR policies/parameters can be configured at all hierarchy levels.
Components Configurable Configurable CIR

Policies parameters
Root port scheduler no-auto-adjust cir
child-cir-sum
One Tap Scheduler no-auto-adjust cir
child-cir-as-percent cir-percent (unused)
Default Scheduler no-auto-adjust cir
child-cir-as-percent cir-percent
child-cir-sum
Customer Scheduler no-auto-adjust cir
child-cir-as-percent cir-percent
child-cir-sum
cir-percent
Queue - cir
cir-percent
Example
Case 1 : Parent Customer Scheduler policy == no_auto_adjust
Parent Sched’s Effective CIR = Configured Absolute CIR (Configured Sched’s CIR% is ignored)
Q’s Effective CIR = Configured Absolute CIR in Kbps(Configured Q’s CIR% is ignored)
Case 2 : Parent Customer Scheduler policy == child_cir_sum
Parent Sched’s Effective CIR = Sum of All Child Q’s Effective CIR (Configured Sched’s Absolute CIR and CIR% are ignored)
Q’s Effective CIR = Configured Absolute CIR in Kbps(Configured Q’s CIR% is ignored)
Case 3 : Parent Sched policy == child_cir_as_percent
Parent Sched’s Effective CIR = Configured Absolute CIR Value (Configured Sched’s CIR% is ignored)
Q’s effective CIR = Configured Q’s CIR% of its parent’s effective CIR = Configured Q’s CIR% of Parent Sched’s
Configured Absolute CIR Value (Configured Q’s Absolute CIR is ignored)
Case 4 : Parent Sched policy == cir-percent
Parent Sched’s Effective CIR = Configured CIR% of its parent’s effective CIR (Configured Sched’s Absolute CIR is ignored)
Q’s effective CIR = Configured Q’s CIR% of its parent’s effective CIR (Configured Q’s Absolute CIR is ignored)
One Control/MCP Highlights
Contributors:
Tim Wong
Packet Service and Packet Transport Management Comparison
Service Visualization
Service Visualization
Service Provisioning
Discovery
Service Provisioning
Discovery
Service Troubleshooting (API only)
Service Troubleshooting
Transport Management
Transport Management
Service Types Service Types

• E-Line • E-Tree • E-LAN • E-Line, • Multi Segment PW
• TDM(17.10)
2point • (unprotected and
• 3point protected)
Transport Types Transport Types
• G.8032 • Linear QinQ
• MPLS-TP • PBB-TE • MPLS-TP • Linear QinQ
Service Configuration Service Configuration

UNI Mid UNI
UNI Mid UNI
E-NNI point E-NNI
E-NNI point E-NNI
CES CES
Port 6500 eMOTR Port CES CES
6500 eMOTR Port Port Port
Port 6500 L2MOTR 6200 6200
6500 L2MOTR
LAG, MC-LAG 6500 Packet Fabric LAG 6500 Packet Fabric LAG,MC_LAG LAG (17.10) LAG (17.10)
6500 PF 6500 PF
5400 ESLM 5400 ESLM
(transit only) (transit only)
Packet Service and Packet Transport Management Comparison
Service Types: Service Types:

E-LINE, E-LAN, E-Tree E-LINE(2 point, 3 point) Single Segment and
Service Discovery Multi Segment Pseudowire
• OneControl discovers service with an initial network sync and Service Discovery
maintains synchronization using background tasks • MCP discovers service with an initial network sync
• End-to-End Service view is created based on nodal data that is • End-to-End Service view is created based on nodal data that is
stitched together stitched together
Service Visualization Service Visualization
• Services can be queried by ID, Node and Link • Services can be queried by ID, Node
• Services are displayed on the Topology map including detailed • Services are displayed on the Topology map including detailed
service information service information
• View related transport types as an overlay on the map • Alarm to Service Correlation
Service Provisioning Service Provisioning
• Provisioning tasks to create, delete, edit services • Provisioning tasks to create and delete services
• Workflow streamlined for minimal data entry • Workflow streamlined for minimal data entry
• Service Profiles to enable customization • Service Profiles to enable customization (API)
Service Troubleshooting Service and LSP Troubleshooting
• Features to enable user to isolate a fault in the network • Features to enable user to isolate a fault in the network
• Control & Monitor Ethernet OAM (Y.1731) • Test and diagnostics (802.1ag, PW ping, PW Traceroute)
• Test and diagnostics (RFC 2544, 802.1ag) • Showing affected service for a link down alarm (API)
Transport Management Transport Management
• Types: G.8032; MPLS-TP; Linear QinQ ; PBB-TE • Types: Static Co-routed MPLS-TP; Linear QinQ
• Discover & Visualize transport layer • Discover & Visualize transport layer
• Provision transport layer • Provision transport layer
• Troubleshooting tools for transport layer • Troubleshooting tools for transport layer
• Node insertion • Available and Consumed Bandwidth Tracking
Copyright © Ciena Corporation 2016. All rights reserved. Confidential & Proprietary.
• Node insertion 137
Support Matrix Overview for MPLS-TP Transport Type
OneControl Service Management support for MCP Service Management support for MPLS-TP
MPLS-TP transport type as follows: transport type as follows:
• Device Types supported: PN 6.x, 8.x, 6500 PF, 5400 ESLM • Device Types supported: PN 6.x, 8.x, 6500 PF (transit
• Service visualization support for each service type only), 6200
• Service provisioning support • Service visualization support for each service
• ELINE, E-TREE, ELAN Single Segment only • Service provisioning support
• LAG and MC-LAG endpoints • ELINE(2 point, 3 point)
• PW signaling (static/dynamic) • Single Segment and Multi-Segment PW
• Service troubleshooting support • PW signaling (static)
• CFM, RFC2544, PW ping • Service troubleshooting support
• MPLS-TP LSP Tunnel Management (visualization, • CFM, PW ping
Provisioning and troubleshooting) support of LSP tunnel • MPLS-TP LSP Tunnel Management (visualization,
configurations Provisioning and troubleshooting) support of LSP tunnel
• MPLS-TE Associated bi-directional static/dynamic configurations
(CES) • MPLS-TP Co-Routed bi-directional (CES, 6500 PF
• MPLS-TP Associated bi-directional dynamic (transit only), 6200)
• MPLS-TP Co-Routed bi-directional (CES, 6500 PF, • LSP ping and traceroute
5400 ESLM) • Bandwidth available and consumed
• LSP ping and traceroute
Dynamic Co-Routed MPLS-TP
Features
Contributors:
Himanshu Shah
Lee Garrett
Dynamic Co-Routed MPLS-TP Features
CO-Routed Creation & Label Distribution Advanced Traffic Engineering
PW Signalling
Resiliency/Robustness
Co-Routed Label Distribution
RSVP-TE Enhancements
Dynamic MPLS-TP features
IS-IS IGP required for dynamic co-routed MPLS-TP
Co-routed bi-directional
LSP is configured at the
initiator end only
Bi-directional LSP setup with single PATH+RESV PDU exchange
PATH message upstream label creates reverse LSP from D to A
PATH
100 200 300
Upstream Label
100 200 300
A B C D
600 500 400
Downstream Label
RESV
600 500 400
RESV message label creates forward LSP from A to D
Control Plane Hops shown but note that actual LSP is setup on
TE links which is not necessarily carrying the PDU
CLI Configuration of dynamic co-routed









CLI Configuration example at initiator and terminator
configuration @ Initiator:
 gmpls tp-tunnel create rsvp-ingress-corout BetweenBostonAndSJ dest-ip 10.10.10.10
 Mpls l2-vpn create dynamic-vc toSJ pw-id 10 peer 10.10.10.10 tp-tunnel-ingress-corout BetweenBostonAndSJ status-
tlv on
MPLS configuration @ terminator:

 Mpls l2-vpn create dynamic-vc toBoston pw-id 10 peer 20.20.20.20 tp-tunnel-egress-corout-dynamic
BetweenBostonAndSJ status-tlv on
 NOTE the use of same tunnel name at initiator and terminator in L2VPN configuration.
PW Signaling
FEC 129
Overview





LSP
T-LDP is used to signal the labels for the PW-FECs as PW
per RFC 4447bis.
2 PW-FEC options are available:
• Legacy option; FEC128 uses PW-ID as unique ID
value
• New enhanced option; FEC129, meant to facilitate
single sided configuration of the PW
FEC 129 (Generalized ID FEC)











FEC 129 - example








FEC 129 Proposed CLI
@PE1:
PE-1> mpls l2-vpn create dynamic-vc vc-boston peer 2.3.4.1 te-tunnel to-sj status on fec-
129 agi Payroll saii Boston taii San Jose
@PE2> :
PE-2> mpls l2-vpn create dynamic-vc vc-sj 1.2.3.4 te-tunnel to-boston status on fec-129 agi
Payroll saii San Jose taii Boston
FEC 129 - VPLS
@PE1:
PE-1> mpls l2-vpn create dynamic-vc vc-boston peer 2.3.4.1 te-tunnel to-sj status on fec-
129 agi Payroll saii NONE taii NONE
@PE2> :
PE-2> mpls l2-vpn create dynamic-vc vc-sj 1.2.3.4 te-tunnel to-boston status on fec-129 agi
Payroll saii NONE taii NONE
ERROR Handling






ISIS Linkage to BFD
BFD: LSP BFD and IP BFD
IS-IS IGP required for dynamic co-

routed MPLS
• IP BFD for fault detection and

trigger dynamic LSP protection
LSP BFD can be enabled to
• IP BFD linked to IS-IS to
monitor individual LSPs and
update IS-IS topology to find a
trigger LSP protection
new LSP path around the
failure
> isis instance create isis-instance MPLS level L1 area 49.0000

> isis interface attach ip-interface mpls_3-2 isis-instance MPLS level L1
> isis interface set ip-interface mpls_3-2 bfd-monitor enable
> bfd profile set profile IP-IGP-Default receive-interval 10msec transmit-interval 10msec
> rsvp-te enable

> rsvp-te enable ip-interface mpls_9
> rsvp-te enable ip-interface mpls_10
> rsvp-te path create rsvp-path Via_S20
> rsvp-te path set rsvp-path Via_S20 index 1 ip 20.20.20.20 hop-type loose
> gmpls tp-tunnel create rsvp-ingress-corout BetweenBostonAndSJ dest-ip 10.10.10.10 bfd-monitor enable
bfd-profile BFDBostonSJ auto-backup <On / Off>
Auto Backup
Auto Backup
configuration @ Initiator:
 gmpls tp-tunnel create rsvp-ingress-corout BetweenBostonAndSJ dest-ip 10.10.10.10 auto-backup on
If Backup feature is enabled for the

LSP, Backup LSP is automatically
created based on:
• Node diversity
• SRLG (if enabled) (covered later)
• BW availability
MBB
Overview






Make-Before-Break (MBB)







MBB
1. Traffic flows on primary
MBB
2. Event triggers the signaling of new LSP.
MBB
3. Traffic is redirected on new LSP.
MBB
4. Old LSP is torn down.
MBB – Rules of operations







Failure handling












LSP RE-Optimization
LSP re-optimization attempts to find a “better” LSP path, based on

the latest network configuration. LSP re-optimization can be
manually triggered or can run at user set intervals, uses Make-
Before-Break “under the hood” which sets up a new LSP path
before tearing down the original path to minimize traffic impact.
> gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> lsp-reopt-interval <NUMBER: 5..60>

> gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> lsp-reopt enable
> gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> lsp-reopt-trigger
Graceful Restart Helper
Control Plane High Availability
ISIS restart scenario
max-restart-time (T1): 10s

recovery-time (T2): 60s
max-recovery-time (T3): 65535s
IS-IS hello (IIH) packets
Device supporting Graceful restart:

• Keeps on forwarding traffic even in the event of a X X
control plane failure (restart) due to dataplane and
control plane separation X
• Sets restart request (RR) bit in the IIH packets to X
inform its neighbors that its undergoing graceful
Graceful restart helper mode devices:
restart.
• Sets restart acknowledge (RA) bit in the IIH packets to acknowledge
• Waits to receive IIH with RA bit set from its
the receipt of a restart TLV with the RR bit set.
neighbors before performing the graceful restart.
• IS-IS adjacencies are maintained and marked in “Restart mode”
• If IIH with RA bit is not received from the neighbors
• T2 is the maximum time that the system will wait for LSP database
after T1, IIH with RR bit set is sent again to the
synchronization.
neighbors.
• T3 indicates the time after which the system will declare that it has
failed to achieve database synchronization
ISIS recovery scenario
max-restart-time (T1): 10s

recovery-time (T2): 60s
max-recovery-time (T3): 65535s
IS-IS hello (IIH) packets
X X
X
X

Graceful restart helper mode devices:
• After GR is complete, sends IIH with RR bit reset.
• Receipt of a normal IIH with the RR bit reset will clear the
"Restart mode“ state of IS-IS adjacencies.
RSVP restart scenario
RSVP hello timer: 10s

Restart timer: 60s
RSVP hello PDUs
If 4x hello missed (4x10s):

• Comms lost is declared
• Restart timer starts (60s)
X X
X
X
• Keeps on forwarding traffic even in the event of
a control plane failure (restart) due to
dataplane and control plane separation
• Restart timer advertises how long a neighbor Graceful restart helper mode devices:
should wait to receive a Hello from the • Receive restart timer information from GR capable node(s)
restarting router before it declares it failed. • Keep on forwarding LSP traffic to the GR capable restarting
node.
• Restart timer can only be set to 0 on helper mode nodes
RSVP recovery scenario
RSVP hello, destination ID=0

RSVP hello, source ID
RSVP hello, updated destination ID
Recovery timer: 120s
After GR-capable device completes

its restart:
• Sends RSVP hello with destination
ID=0
• Receives from GR helper nodes
RSVP hello with correct source ID
• RSVP hello are updated with correct
destination ID
• Recovery timer specifies how long
the device should hold stale label-
FEC bindings after an RSVP Graceful restart helper mode devices:
session has been reestablished. • Receive hello PDUs from the restarted GR node
with destination 0, indicating that the GR node had
a CP failure and recovered.
• Send back hello with their own source ID
RSVP configuration
> rsvp-te graceful-restart enable

WARNING: RSVP Graceful Restart will be activated only on newly created RSVP tunnels
> rsvp-te set ip-interface mpls121 hello-interval <SECONDS: 0..30>
> rsvp-te show timers

+---------------------RSVP TE PROTOCOL TIMERS------------+
| Name | Value |
+-------------------------------+------------------------+
| Retry Interval (sec) | 3 |
| Restart Time (sec) | 60 (??) |
| Tunnel Recovery Time (sec) | 0 |
| PW Recovery Time (sec) | 0 (??) |
| Retry Max Default | 10 |
| Retry Infinite State | On |
| Activation Interval (sec) | 300 |
| Total Activation Period (sec) | Infinite |
| Pseudowire Capability | On |
| Pseudowire Status | On |
+-------------------------------+------------------------+
T-LDP restart scenario
Reconnect Time: 60s

Max-peer-reconnect: 180s
LDP PDUs
LDP session goes down:

• Reconnect and recovery timers start
• The device retains the label-FEC
bindings received via that session,
but marks them as "stale".
• Stale bindings are deleted if lesser of
reconnect time/max-peer-reconnect X
is expired

• Sends in TLV reconnect and recovery timer
values
Graceful restart helper mode device: • Reconnect Time is the time that the sender of
• Receive reconnect and recovery timers from neighbors the TLV would like the receiver of that TLV to
• Reconnect time & Recovery time are 0 and cannot be wait after the receiver detects the failure of
set. LDP session.
• Recovery Time carries the time the device is
• Max-peer-reconnect and max-peer-recovery local timers willing to retain its MPLS forwarding state
are user configurable. that it preserved across the restart.
• Keeps on forwarding PW traffic during LDP
session restart.
T-LDP restart scenario
Recovery Time: 180s

LDP session comes back up:
• If GR node was not able to preserve
Max-peer-recovery: 240s
its forwarding state, all stale entries
are deleted. LDP PDUs
• If GR node was able to preserve its
forwarding state, stale entries are kept
as the lesser of the Recovery Time
and Max-peer-recovery
T-LDP configuration
> ldp graceful-restart enable

WARNING: LDP Graceful Restart will be activated only on newly created LDP session
> ldp graceful-restart set max-peer-reconnect <NUMBER: 0..600>

> ldp graceful-restart set max-peer-recovery <NUMBER: 0..600>
> ldp show timers

+-------------------------- LDP Timers ---------------------+
| Parameter | Value |
+--------------------------------+--------------------------+
|LDP Hello Hold Time (sec) | 180 |
|LDP Keepalive Hold Time (sec) | 180 |
|LDP GR Reconnect Time (sec) | 0 |
|LDP GR Recovery Time (sec) | 0 |
|LDP GR Max Peer Reconnect (sec) | 180 |
|LDP GR Max Peer Recovery (sec) | 240 |
+--------------------------------+--------------------------+
HW Based IP Forwarding
Hardware Based IP Forwarding
Advanced Traffic Engineering
ISIS TE Extensions
S3*> isis te-tables show te

…
+---------------------TE TLV Table---------------------+
+---------------------------+--------------------------+
|System Instance | 3 |
|Level | L1 |
|LSP Id | 0030.0300.3003.00-02 |
|TLV Num | 4 |
|LSP Seq Num | 53 |
|LSP Checksum | c168 |
|TLV Type | 22 |
|TLV Length | 122 |
|IPv4 Interface Address | 10.3.4.1 |
|TE default metric | 1 |
|Admin Group | 0 |
|Link Protection Type | 0 |
|Maximum Link Bw(kbps) | 10000000 |
|Maximum Reserv Bw(kbps) | 10000000 |
|Max Unreserv Link Bw(kbps) | |
| Priority-0/TE-Class-0 | 10000000 |
+---------------------------+--------------------------+
MPLS TE Extensions – show ip-interfaces
MPLS TE Extensions
Resiliency/Robusness
Resource Affinity
Resiliency/Robustness – Resource Affinity
• Also known as link affinity, link color, administrative group.

• 32 bit mask manually configured on a TE interface (ie. a TE interface can be assigned up to 32 different
colors)
• Grouping can be made on any arbitrary criteria (geography, administrative, hardware, etc…)
• Head-end can calculate a path that go through or avoid links depending on the specified constraint.
Create a LSP to far end

that avoids all RED TE
interfaces
RED
Resiliency/Robustness – Resource Affinity - Configuration
1. Create/Define color-mask mapping

2. Create/Define which color(s) are part of color group
3. Assign the color group to a TE interface
4. When creating the tunnel, specify the constraint
mpls traffic-eng create/delete resource-color <color-name> index <1..32>

1
mpls traffic-eng create/delete/add/remove* resource-color-group <color-group-name> colors <color-name-list>
2 mpls traffic-eng set/unset ip-interface <ip-interface-name> resource-color-group <color-group-name>
3 gmpls tp-tunnel create rsvp-ingress-corout <tunnel-name> dest-ip <ip-addr>

 [resource-include-all <color-group-name>]
4  [resource-include-any <color-group-name>]
 [resource-exclude-any <color-group-name>]
Recommendation : Keep color names and masks consistent across nodes!

IF ANY OF THE LSP is passing through the TE LINK using the AFFINITY VALUE, USER WILL NOT BE ALLOWED TO CHANGE the affinity
Backup LSPs will inherit the same resource affinity constraint as its primary.
Resiliency/Robusness
Shared Risk Link Groups
Resiliency/Robustness – SRLG
• 32 bit mask manually configured on a TE interface (ie. a TE interface can be assigned up to 32 different
SRLGs)
• Allows to create backup LSPs that are disjointed from the primary path for maximum resiliency.
1. Primary LSP is computed

and signaled regardless of
SRLG assigned to TE
interfaces.
2. Auto-backup LSP will

avoid using TE interfaces
that have the same SRLG 2
values used by primary
LSP
Resiliency/Robustness – SRLG - Configuration
1. Assign SRLG values to TE interfaces

2. Create primary LSP with auto-backup on.
Auto-backup uses SRLG disjoint if any of the links of the primary LSP has SRLG configured.
Otherwise, it uses ‘node-diversity’ algorithm.
mpls traffic-eng set ip-interface <ip-interface-name | unnum-ip-interface-name> srlg <32-bit-val1, .., 32-bit-valn> ; up to 16
1
2 gmpls tp-tunnel create rsvp-ingress-corout <tunnel-name> dest-ip <ip-addr> [auto-protect <on | off>
Recommendation : Keep SRLG values consistent across nodes!
Resiliency/Robustness – SRLG – Querying SRLG Used
Bandwidth Management
Auto-Bandwidth
Bandwidth Management - Auto-Bandwidth
400M
300M
Resize Increment
Max
• LSP auto-bandwidth will re-adjust the RSVP- 200M
Reserved
Reserved SVC 4 PW = 50M
TE Tspec BW parameter if there is enough
bandwidth on the line interface. Bandwidth SVC 3 PW = 50M
Utilized Bandwidth 100M
• Bandwidth required for an LSP depends on the SVC 2 PW = 50M
Min
on the auto-size-mode:
SVC 1 PW = 50M LSP 100
• Utilization: uses LSP stats (only on
3942, 5142 and 5160)
• CAC: uses mpls-vc bandwidth
parameter
• If there is not enough bandwidth on the line  gmpls tp-tunnel create rsvp-ingress-corout <tunnel-name> dest-ip <IP_addr> auto-size-mode cac|utilization
interface an alarm can be raised (auto-size-  gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> auto-size enable|disable
failure is set to “alarm”) or a new LSP that has  gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> auto-size-failure alarm|mbb
enough BW can be found, using Make-Before-  gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> auto-size-trigger
Break “under the hood” which sets up a new  gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> min-bandwidth <Kbps: 0..1000000000>
LSP path before tearing down the original path  gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> max-bandwidth <Kbps: 0..1000000000>
to minimize traffic impact.  gmpls tp-tunnel set rsvp-ingress-corout <tunnel-name> increment-bandwidth <Kbps: 0..1000000000>
• LSP auto-bandwidth can be manually
triggered, can run at user set intervals (for BW
decrease) or when BW has exceeded min/max
set thresholds (for BW increase or decrease).
CAC Trigger Mode
Animated Slide
LSP Auto Bandwidth : Example
auto-size mode = CAC
@ Time 1
• Service 1 Creation Request (50M Service) Tunnel Creation Profile
• Tunnel Exists with bandwidth Available? No • MIN = 200M
• Create Tunnel with Profile Parameters • MAX = 400M
• Create Service 1  bandwidth Available = Yes • Increment = 100M
@ Time 2
• Create Additional 50M Services
• Tunnel exists with bandwidth Available
• Service 2  bandwidth Available = Yes
• Service 3  bandwidth Available = Yes 400M
@ Time 3
• Create New Service 5  50M Service 300M
• Service 5  bandwidth Available = No SVC 6 PW = 50M
• Resize Tunnel
• New Reserved SVC 5 PW = 50M
200M
Reserved
Max
= Current Usage + New Service bandwidth + Increment
= 350M SVC 4 PW = 50M
SVC 3 PW = 50M
Reserved
• Create Service 5  bandwidth Available = Yes
100M
Min
@ Time 4 SVC 2 PW = 50M
• Create Additional 50M Services
• Service 6  bandwidth Available = Yes SVC 1 PW = 50M LSP 100
LDP RSVP
Animated Slide
@ Time 5
• NE Interval Time Expires
• Auto BW resize Application analyzes LSPs and sends resize request Tunnel Creation Profile
if required • MIN = 200M
• IF Reserved (350) – Utilized (300) > Increment (100)  • MAX = 400M
No • Increment = 100M
Timer
• Do Not Resize
@ Time 6
• Service Additions
400M
• Create New Service 8  50M Service SVC 7 PW = 50M
• Service 8  bandwidth Available = No 300M
• Resize Tunnel SVC 6 PW = 50M
• New Reserved
Reserved
= Current Usage + New Service bandwidth + Increment SVC 5 PW = 50M
200M
Reserved
Max
= 400M
IF New Reserved > MAX Then SVC 4 PW = 50M
New Reserved = MAX
SVC 3 PW = 50M
100M
Min
SVC 2 PW = 50M
@ Time 8
SVC 1 PW = 50M LSP 100
• Service 9  bandwidth Available = No
• Service creation blocked LSP = MAX
• LSP is not Resized. LDP RSVP
Animated Slide
@ Time 9
• Service Deletions
• Service 6  Service Deleted = Yes Tunnel Creation Profile
• Service 5  Service Deleted = Yes • MIN = 200M
• Service 4  Service Deleted = Yes • MAX = 400M
• Increment = 100M
@ Time 10
• NE Interval Time Expires
• Auto BW resize Application analyzes LSPs and sends resize
request if required
• IF Reserved (400) – Utilized (250) > Increment (100)
400M
• Yes  LSP Resize
SVC 8 PW = 50M
Timer • LSP Reserved
350M
= Utilized (250) + Increment (100) SVC 7 PW = 50M
• LSP is Resized to 350.
300M
SVC 6 PW = 50M
@ Time 11
• Service Deletions SVC 5 PW = 50M
Reserved
• Service 5  Service Deleted = Yes 200M
Reserved
Max
• Service 4  Service Deleted = Yes SVC 4 PW = 50M
• Service 3  Service Deleted = Yes
• Service 2  Service Deleted = Yes SVC 3 PW = 50M
Reserved
100M
Min
• NE Interval Time Expires LSP 100
• Auto BW resize Application analyzes LSPs and sends resize SVC 1 PW = 50M
request if required
• If LSP Reserved BW < MIN
Timer • LSP Reserved = MIN LDP RSVP
Utilization Trigger Mode
Animated Slide
auto-size mode = Utilization
@ Time 1
Tunnel Creation Profile LSP Max
• Service 1 Creation Request
• MIN = 5G
Throughput
• Tunnel Exists with bandwidth Available? No Peak
• MAX = 10G
• Create Tunnel with Profile Parameters LSP Min
• Increment = 100M Peak
Peak
Average
Time Time
Interval
@ Time 2
• Create Additional Services
• Tunnel exists with bandwidth Available
• Service 4 bandwidth Available = Yes 10 G
@ Time 3
• LSP Resize Timer Expires
• Tunnel Utilization > Reserved + INC OR Tunnel Utilization < 7.5G
Reserved – INC OR Peak Tunnel Utilization < MIN Service 10 PW
Timer
…
No action Required
5.0G
Max
@ Time 4 Service 4 PW
•
Reserved
Create Additional Services
• Service 3 PW
Reserved
Tunnel exists with bandwidth Available
• Service 5  bandwidth Available = Yes 2.5G
Min
Service 2 PW
...

Service 1 PW LSP 100
@ Time 5
• Peak Tunnel Utilization > Reserved
ResizeTunnel: Usage
LDP RSVP
Timer
Animated Slide
@ Time 6 Tunnel Creation Profile Peak
LSP
LSP Max
Max
• Create Additional Services • MIN = 5G
LSP
PeakMax
Throughput
Peak
• Tunnel exists with bandwidth Available • MAX = 10G LSP
LSP Min
Min
... • Increment = 100M
• Service 20  bandwidth Available = Yes Time Interval
@ Time 7
Timer ResizeTunnel: Usage + Increment/2
10 G
@ Time 8
• Bandwidth increases on existing services and LSP usage grows Service 20 PW
Service 18 PW
beyond Tunnel Threshold (MAX).
…
7.5G
@ Time 9
Service 10 PW
• Peak Tunnel Utilization > Reserved AND Peak Tunnel Utilization
Reserved
> MAX 5.0G
Max
Reserved
Timer Tunnel Resize Fail: Raise Alarm or MBB Service 4 PW
Reserved
@ Time 10 Service 3 PW
• Service Deletions 2.5G
Min
• Service 20  Service Deleted = Yes Service 2 PW
@ Time 11
Timer ResizeTunnel: Clear Resize Alarm LDP RSVP
RSVP
Animated Slide
@ Time 12 Tunnel Creation Profile LSP Max

• Service Deletions • MIN = 5G Peak
Peak
Throughput
• Service 18  Service Deleted = Yes • MAX = 10G LSP Min
... • Increment = 100M Peak
Average
Time Interval
Time
@ Time 13
• Average Tunnel Utilization > Reserved 10 G
Timer ResizeTunnel: Usage + Increment Service 18 PW
@ Time 14
…
• Service Deletions 7.5G
• Service 10  Service Deleted = Yes Service 10 PW
...
…
5.0G
Max
Service 4 PW
Reserved
@ Time 15
Reserved
Reserved
• Average Tunnel Utilization < MIN Service 3 PW
2.5G
Min
Timer ResizeTunnel: MIN
Service 2 PW
LDP RSVP
Link with Performance Monitoring Mechanism
gmpls tp-tunnel create rsvp-ingress-corout S3-S4_50-100+10 dest-ip 4.4.4.4 auto-backup on min-bandwidth 50000 max-bandwidth
100000 increment-bandwidth 10000 auto-size enable auto-size-mode utilization auto-size-interval 5 auto-size-failure mbb
pm threshold create interval-profile AutoSize sample-interval 5m adjustment-interval 10m adjustment-threshold-percentage 2

overflow-threshold-percentage 2 overflow-count 2 underflow-threshold 2 underflow-count 2 alert-interval 5m
pm create tp-rsvp-ingress-corout S3-S4_50-100+10 pm-instance AutoSizeInstance instance-type proactive profile-type

BasicTxRx bin-duration 5m interval-profile AutoSize
S3*> pm threshold show interval-profile AutoSize

+----------------------- PM THRESHOLD INTERVAL PROFILE ------------------------+
+---------------------------------+--------------------------------------------+
| Interval Profile Name | AutoSize |
| Interval Profile ID | 1 |
| Sample Interval | 5 min |
| Adjustment Interval | 10m |
| Adjustment Threshold | |
| Adjustment Threshold Percentage | 2 |
| Overflow Threshold | |
| Overflow Threshold Percentage | 2 |
| Overflow Count | 2 |
| Underflow Threshold | 2 |
| Underflow Threshold Percentage | |
| Underflow Count | 2 |
| Alert Interval | 5m |
| Alert Threshold Percentage | |
+---------------------------------+--------------------------------------------+
+-------------------- PM THRESHOLD INTERVAL PROFILE USAGE ---------------------+

| PM Instance | Instance Oper State |
+---------------------------------+--------------------------------------------+
| AutoSizeInstance | enabled |
+---------------------------------+--------------------------------------------+
Parameters Explained
Adjustment Interval : Time interval at which determination is made whether to adjust the LSP bandwidth or not
Maximum Average Bandwidth : Maximum Average Bandwidth during the adjustment interval. That is, all the Bandwidth Samples
collected within the adjustment interval, are checked to see which one was the highest.
Adjustment Threshold : This could be a percentage or actual value. The formula is : DIFF (Maximum Average Bandwidth , current
LSP BW) >= Adjustment-Threshold then LSP is resized to Adjusted Bandwidth. The Adjusted Bandwidth would be Maximum
Average Bandwidth which could be down or upsizing value.
Overflow-Threshold : A user configurable value. This threshold is used to check against the DIFF(sampleBw, current-LSP-BW) to
see if b/w usage is rapidly increasing
Overflow-Count : A consecutive count the overflow-threshold was crossed. When this count is reached, LSP autosize is dispatched
immediately without waiting for adjustment interval to expire
Underflow-Threshold: A user configurable value. This threshold is used to check against the DIFF(SampleBw, current-LSP-BW) to
see if b/w usage is rapidly decreasing
Underflow-Count : A consecutive count the Underflow Threshold has crossed. When this count is reached the LSP is downsized
immediately to MaxAvgBw value.
Relevant PM Show Commands
S3> pm show user-created

+--------------------------------------------------- USER CREATED PM INSTANCES ----------------------------------------------------+
| | Admin | Oper | Instance | Attached Interface |Bin |Bin |
| Instance Name | State | State | Type | Type | Name |Count|Duration|
+--------------------------------+---------+---------+-----------+-----------------+--------------------------------+-----+--------+
| AutoSizeInstance | Enabled | Enabled | Proactive | RsInCoLs | S3-S4_50-100+10 | 32 | 5 min |
+--------------------------------+---------+---------+-----------+-----------------+--------------------------------+-----+--------+
S3> pm threshold show pm-instance AutoSizeInstance

S3*> pm threshold show pm-instance AutoSizeInstance Time until next adjustment
+------------------------- PERFORMANCE MONITORING THRESHOLD CROSSING ALERT DATA --------------------------+ (if watermark warrants)
+-----------------------------------------------------+---------------------------------------------------+
| Instance Name | AutoSizeInstance |
| Interval Profile | AutoSize |
| Adjustment TCA Units | bits-per-second |
| Adjustment TCA Scheme | inclusive-or |
| Adjustment TCA Stats | RX Accepted Bytes,TX Forwarded Bytes |
| Adjustment TCA Basis Value
| Adjustment TCA Basis Minimum
| 100,000,000
| 50,000,000
|
|
next watermark update
| Adjustment TCA Basis Maximum
| Adjustment TCA Configuration Status
| 100,000,000
| configured
|
|
(sample collection)
| Adjustment TCA Upper Boundary | 102,000,000 |
| Adjustment TCA Lower Boundary | 98,000,000 |
| Adjustment TCA Interval Start Date/Time | Fri Nov 04 20:20:00 2016 (1m10s ago) |
| Adjustment TCA Interval End Date/Time | Fri Nov 04 20:30:00 2016 (8m50s from now) |
| Adjustment TCA Sample Start Date/Time | Fri Nov 04 20:20:00 2016 (1m10s ago) |
| Adjustment TCA Sample End Date/Time | Fri Nov 04 20:25:00 2016 (3m50s from now) |
MPLS QoS
Diffserv-TE
Differentiated Services (DiffServ)







SUPPORTED Prior to 6.16/8.5
Configurable Per Queue shapers
ensure all queues are guaranteed
Diffserv Queuing Model CIR allocations
Mixing all service types within a single Q Group Configurable Per Queue Scheduling
(Strict/WFQ)
CIR CIR/CBS
High Intended for network Q7 Strict
priority control traffic. Spare
Capacity
Intended for network CIR/CBS
CIR Strict
control traffic or Q6
delay/jitter sensitive
EF
traffic.
CIR/CBS
CIR
Strict
Q5
Intended for delay/jitter
sensitive traffic. CIR CIR/CBS
Q4 Strict
CIR/CBS CIR/CBS
CIR/CBS
CIR/EIR
EIR/EBS EIR/EBS EIR/EBS
Q3 WFQ CT0
Intended for assured
AF
CIR/CBS
traffic.
CIR/EIR CT4 LSPs
Q2 EIR/EBS WFQ
CIR/CBS
CIR/EIR One
Q1 EIR/EBS WFQ
BE
Intended for best effort

Class Type
traffic.
EIR
CIR/CBS
(CT0)
WFQ
Lower Q0 EIR/EBS
priority
EXP (TC) bits determines the per-hop behavior
Per Queue weights for WFQ Queues regulate
service treatment regardless of label
EIR allocation during congestion events
Diffserv Aware Traffic Engineering (Diffserv-TE)



SUPPORTED in 8.5 & 6.16 (for 5142,5160, 3942)
BW per CT is Guaranteed via Queue group Shaper
Diffserv-TE Queuing Model EXP (TC) bits determines service treatment within
class type
and port Scheduler.
Queue Group Configuration
Class Type Configuration Example • CIR = CT BW = x% Port capacity
• EIR = 100% of Port Capacity
• ∑ CTn CIR ≤ Port Rate
EF
Bandwidth constraint
determines the CT7 : 20%
bandwidth allocated SP
AF
per class type. Spare
BE
Local Overbooking
Multiplier:
…
…
Allows overbooking LSP
capacity on this CT. CT7 = 2G
BC7 = 2G
Label Max = 0G
EF
identifies the
CIR/CBS
class type
WFQ
10G
AF
CT4 : 40% , LOM 2 Port
BE
EIR/EBS
CT4 = 4G
BC4 = 4G
…
Weights and shapers per Queue in Max = 8G
conjunction with the Q group
scheduler are provided to provide
…
differentiated service behavior within

the Q group if congestion occurs
EF
CT0 = .5G
BC3 = .5G
WFQ Max = .5G
CT0 : 5% , LOM 1
AF
BE
Port Scheduler is configured with Strict or WFQ as required

for each CT. Traffic treatment within each CT is based on
Queue configuration within the CT Q Group.
DiffServ-TE
Bandwidth Allocation Models
•
Max reservable bandwidth
CT7 CT4 CT0

no preemption
DiffServ-TE CAC Overview: Maximum Allocation Model
Maximum Reserved Bandwidth per Class type LSP Resizing Capabilities can be CTn Capacities can be set to ensure total CAC
The sum of the Class type
is calculated based on the Class type leveraged to minimize frequency of bandwidth never exceeds X% of a port and to
capacities must be less than
bandwidth constraints and the Local resize requests as services are added ensure Bandwidth in each Class type cannot be
or equal to the Port Capacity.
Overbooking Factor to LSPs.(CAC or Utilization Mode) reserved by other class Types
Unreserved
Port Capacity
Class Type (CT7) Unreserved

CTn Capacity
LSP 400 Service 8

Service 7
...
LSP 300 Service 6

Maximum
Port
Class Type (CTn) Reserved Service 5

Bandwidth Unreserved
Example = BCn * LOM LSP Capacity
Committed Rate = 4G = 4G * 2 Service 3
Bandwidth Constraint (BCn) = 4G = 8G LSP 100
Local Overbooking Multiplier = 2 Service 2
Service 1
...
Class Type (CT0)
Bandwidth constraints are calculated based on the Service Bandwidth (PW) are CAC’ed into LSPs based LSP Bandwidth is CAC’ed against the CT
Maximum allocation Model on the requested provisioned CIR bandwidth against the bandwidth (MAM model) in conjunction with LOM
(No Sharing of reserved bandwidth is allowed between LSP BW. There is no overbooking for PW to LSP CAC. (Local Overbooking Multiplier). LOM will be set to 1
CTs. Preemption is not supported in Phase 1. BW is always booked 1 to 1 for CBR based Class Types
DiffServ-TE Events
Per LSP Events based on CAC LSP 100
90%
LSP MAX
90% Unreserved
CT7 = 2G
BC7 = 2G Service 14 Sum PW BW associated with
Max = 2G Service 13 LSP > 90% of LSP MAX= No
LSP 100 Reserved No Event
Service 12
Service 11
10G LSP Event is raised when

CT4 = 4G LSP MAX
Port BC4 = 4G Unreserved Service 8 isLSP
configured
100
Max = 8G
90%
Service 8
Service 7
Service 6 Sum PW BW associated with
LSP 101 Service 5 LSP > 90% of LSP MAX= Yes
Reserved Send Event
Service 4
Service 3
Service 2
Service 1
DiffServ-TE Events
Per Class Type Throughput
Per Class type (Queue Group)

Spare Throughput stats, Thresholds and Peak rate
Capacity
Throughput
CIR
CT7 = 2G % Max Threshold
BC7 = 2G Peak
Max = 2G
Time Interval
10G
Port
Peak
Throughput
CIR
CT4 = 4G % Max Threshold
BC4 = 4G
Max = 8G
Time Interval
…
CT0 = .5G
Throughput
BC3 = .5G CIR

Max = .5G % Max Threshold
Peak
Time Interval
DiffServ-TE Events
Per Queue Throughput
Per Queue
Requirements
Throughput stats, Thresholds and Peak rate
• Throughput is monitored for each Queue.
• A threshold crossing alert is provided when a Q exceeds its CIR
rate.
• The peak rate is provided for a time interval (15 min, etc)
Throughput
• A threshold crossing count is provided and increments each time CIR
% Max Threshold
the throughput exceeds the CIR Rate.
Peak
Time Interval
…
Q7 Strict
Peak
Throughput
Q6 CIR
Strict % Max Threshold
Q5 WFQ CIR/CBS
#G
Q4 WFQ Time Interval
…
Q3 WFQ
Q2 EIR/EBS
Throughput
WFQ
Port Speed
CIR
% Max Threshold
Q1 WFQ
Peak
Q0 WFQ
Time Interval
MPLS QoS
Diffserv-TE
6.16 Example
Diffserv-TE – Configuration Sequence
Must be done for all

MPLS enabled nodes
and interfaces
Diffserv-TE - Simple Example Topology
S3 S4 S13
10G 1G 1G
10G 4G 4G
10G 5G 5G
In the simple example above, 3 tunnel class types with 3 different bandwidth constraints in conjunction
with three queue group schedulers will be used to limit a flow in each service.
The example can be extended to have multiple priority flows(queues) per service.
Example – Class Type Design
EF
CIR/CBS
.99G
In this example, Q1
will be assigned the
AF
Spare
full CIR of CT7’s
EIR/EBS
10G
BE
queue group
…
CT7 = .99G
BC7 = .99G
Max = .99G
EF
CIR/CBS
4G CIR/CBS
In this example, Q1 WDRR
will be assigned the 10G
full CIR of CT4’s AF Port
EIR/EBS
BE 10G
EIR/EBS
queue group CT4 = 4G
… BC4 = 4G
Max = 8G
EF
CIR/CBS CT0 = 5G
5G
BC3 = 5G
In this example, Q1 Max = 5G
will be assigned the
AF
EIR/EBS
full CIR of CT0’s 10G
BE
queue group
Diffserv-TE – Configuration Step 1
resource-manager pool set feature mpls-queuing resource classifier count 1024

resource-manager pool set feature mpls-queuing resource counter count 1024
Repeat for all DIFFSERV-TE Nodes
For multi-segment PW tunnels (switching tunnels), set the following resources:
resource-manager pool set feature mpls-mspw-queuing resource classifier count 1024

resource-manager pool set feature mpls-mspw-queuing resource counter count 1024
traffic-services cos-mapping resolved-cos-map create cos-map DS-TE-RCOS

traffic-services cos-mapping resolved-cos-map set cos-map DS-TE-RCOS mpls-tc 7 r-cos 7
traffic-services cos-mapping resolved-cos-map set cos-map DS-TE-RCOS mpls-tc 5 r-cos 5 NOTE: In this release,
traffic-services cos-mapping resolved-cos-map set cos-map DS-TE-RCOS mpls-tc 3 r-cos 3 only the default ingress to
traffic-services cos-mapping resolved-cos-map set cos-map DS-TE-RCOS mpls-tc 2 r-cos 2 queue mapping is
traffic-services cos-mapping resolved-cos-map set cos-map DS-TE-RCOS mpls-tc 0 r-cos 0 supported.
port set port 24 resolved-cos-map DS-TE-RCOS
Repeat for all MPLS ports
traffic-services cos-mapping frame-cos-map create cos-map DS-TE-FCOS

traffic-services cos-mapping frame-cos-map set cos-map DS-TE-FCOS r-cos 7 r-color green mpls-tc 7
port set port 24 frame-cos-map DS-TE-FCOS
traffic-services queuing egress-port set port 24 scheduler-algorithm weighted-deficit-round-robin
traffic-services queuing egress-queue-group-profile create profile DS-TE-QG-CT0Pro

traffic-services queuing egress-queue-group-profile set queue 0 profile DS-TE-QG-CT0Pro scheduler-weight 10
traffic-services queuing egress-queue-group-profile set queue 1 profile DS-TE-QG-CT0Pro scheduler-weight 10 cir 5000000 cbs 1024
traffic-services queuing egress-queue-group create queue-group DS-TE-QG-CT0 profile DS-TE-QG-CT0Pro
Individual queues
parameters can be defined
here.

Individual queues
here.

Individual queues
here.
traffic-services queuing egress-queue-group add port 24 queue-group DS-TE-QG-CT0 priority 10 scheduler-weight 10 cir 5000000 cbs 1024
mpls traffic-eng class-type-profile create class-profile CT-10G

mpls traffic-eng class-type-profile set class-profile CT-10G class-type 0 queue-group DS-TE-QG-CT0
mpls traffic-eng class-type-profile set class-profile CT-10G class-type 4 queue-group DS-TE-QG-CT4 lom 2
mpls traffic-eng class-type-profile set class-profile CT-10G class-type 7 queue-group DS-TE-QG-CT7
If required, configure alarm threshold before

next step.
mpls traffic-eng class-type-profile

set class-profile CT-10G class-type 4
alarm-threshold-percentage 75 queue-
group DS-TE-QG-CT4
mpls traffic-eng set ip-interface toS4 class-profile CT-10G
Repeat for all appropriate

MPLS IP interfaces
Minimum bandwidth > 0 must be assigned
gmpls tp-tunnel create rsvp-ingress-corout S3S13CT0 dest-ip 13.13.13.13 min-bandwidth 100000 max-bandwidth 5000000 auto-size enable
gmpls tp-tunnel create rsvp-ingress-corout S3S13CT7 dest-ip 13.13.13.13 class-type 7 min-bandwidth 100000 max-bandwidth 4000000 auto-size enable
gmpls tp-tunnel create rsvp-ingress-corout S3S13CT4 dest-ip 13.13.13.13 class-type 4 min-bandwidth 4000000 max-bandwidth 4000000 auto-size enable
S3 S4 S13
1G 1G
4G 4G
5G 5G
S3:
mpls l2-vpn create dynamic-vc PW1-CT0 pw-id 100 peer 13.13.13.13 tp-tunnel-ingr-corout S3S13CT0 bandwidth 5000000
S13:
mpls l2-vpn create dynamic-vc PW1-CT0 pw-id 100 peer 3.3.3.3 tp-tunnel-egrs-corout-dynamic S3S13CT0 bandwidth 5000000
S3 S4 S13
1G 1G
4G 4G
5G 5G
Diffserv-TE – Results
Once the services are created, the 3 flows are capped to the defined bandwidth in the queue group in the
MPLS tunnel…
In this example, the RCOS was assigned to 2 (default vs-inherit value) and mapped to queue 1 (default queue
mapping).
S3 S4 S13
10G 1G 1G 1G less MPLS encapsulation
MPLS QoS
Diffserv-TE
8.5 Example
Diffserv-TE Example : Topology
In the simple example that follows, 3 tunnel class types with 3 different bandwidth constraints in conjunction
with three queue group schedulers will be used to limit a flow in each service. Maximal allowable CIR will be
used with no oversubscription specified on the bandwidth constraint. However EIR won’t be capped which
means a greater bandwidth(10G) than the sum of the CIR (8G) will be allowed through. It might be simpler to
specify EIR of 0 on queue groups schedulers/queues.
The example can be extended to have multiple priority flows(queues) per service.
S1 1.1.1.1 S14 14.14.14.14 S2 2.2.2.2
50% 50% 50% 50%
3/10
3/11
3/12
40% 40%
2/10
40% 40%
10% 10% 10% 10%
2/1
3/11 3/12 3/13
10.1.14.0/30 10.2.14.0/30
vlan200
10G
2.752G
2.568G
.64G
50% 4.0G
cir = 40%
10%
3.2G
0.8G
100% 10G
eir = 100%
100%
10G
10G
DiffServ-TE Example: Class Type Design
10G
CIR
In this example, 10% Port
Q1 will be Class
vlan300
assigned 100% profile

EIR/EBS
of CT7 Queue CT10G
VPWS300 PW300-CT7
S1S2CT7 100%
Group’s CIR
tunnel DS-DQG-CT7Pro
CT7 = 800M
BC7 = 800M
Root scheduler
Max = 800M
ip interface
EF
In this example, CIR
40% CIR=80%
vlan200
Q1 will be WDRR
assigned 100%
AF
VPWS200 PW200-CT4
S1S2CT4 of CT4 Queue EIR/EBS
100%
BE
CT4 = 3.2G
tunnel
Group’s CIR EIR=100%
BC4 = 3.2G
Max = 3.2G
DS-DQG-CT4Pro
vlan100
CT0 = 4G
EF
CIR/CBS BC3 = 4G
VPWS100 PW100-CT0
S1S2CT0 In this example, 50%
Max = 4G
Q1 will be
AF
tunnel assigned 100%

EIR/EBS
of CT0 Queue 100%
BE
Group’s CIR
DS-DQG-CT0Pro
Diffserv-TE Example : Configuration Sequence
Must be done for all

MPLS enabled nodes
and MPLS
ports/interfaces
Diffserv-TE Example –Step 1 – Port Scheduling
traffic-services queuing egress-port-root-scheduler set scheduler 3/10-Root cir 8000000 cbs 128
Diffserv-TE Example –Step 2 – Scheduling Profiles
traffic-services queuing scheduler-profile create profile DS-TE-Sched-CT0 cbs 21 cir-policy cir-as-percent cir-percent 50
Diffserv-TE Example –Step 3 – Queue Group Profiles
traffic-services queuing queue-group-profile create profile DS-TE-QG-CT0Pro

traffic-services queuing queue-group-profile set queue 1 profile DS-TE-QG-CT0Pro cbs 21 cir-percent 100
Individual queues
here.
In this example, Q1 will be

assigned 100% of a class
type Queue Group’s CIR.
EIR was left to 100%
Diffserv-TE Example –Step 4 – Scheduling Instances
traffic-services queuing scheduler-profile add profile DS-TE-Sched-CT0 instance 1 port 3/10 parent-scheduler 3/10-Root
Diffserv-TE Example –Step 5 – Queue Group Instances
traffic-services queuing queue-group-profile add profile DS-TE-QG-CT0Pro instance 1 port 3/10 parent-scheduler DS-TE-Sched-
CT0 parent-instance 1
Diffserv-TE Example –Step 6 -
mpls traffic-eng class-type-profile create class-profile DS-TE-CProf

mpls traffic-eng class-type-profile set class-profile DS-TE-CProf class-type 0 queue-group DS-TE-QG-CT0Pro queue-group-instance 1
Diffserv-TE Example – Step 7 – Assigning MPLS CT to IP Interfaces
mpls traffic-eng set ip-interface toS14 class-profile DS-TE-CProf
Repeat for all appropriate

MPLS IP interfaces
Diffserv-TE Example – Configuration Step 8
gmpls tp-tunnel create rsvp-ingress-corout S1S2CT0 dest-ip 2.2.2.2 min-bandwidth 1000000 max-bandwidth 4000000 increment-bandwidth 1000000 auto-size enable
gmpls tp-tunnel create rsvp-ingress-corout S1S2CT4 dest-ip 2.2.2.2 class-type 4 min-bandwidth 1000000 max-bandwidth 3200000 increment-bandwidth 200000 auto-size enable
gmpls tp-tunnel create rsvp-ingress-corout S1S2CT7 dest-ip 2.2.2.2 class-type 7 min-bandwidth 100000 max-bandwidth 800000 increment-bandwidth 100000 auto-size enable
Diffserv-TE Example – Configuration Step 9
S1:
S2:
Diffserv-TE – Results
Once the services are created, the 3 flows are capped to the defined bandwidth in the queue group in the
MPLS tunnel…
In this example, the flows had a pbit of 1 and were thus mapped to queue 1 (default queue mapping).
S1 1.1.1.1 S14 14.14.14.14 S2 2.2.2.2
50% 50% 50% 50%
3/10
3/11
3/12
40% 40%
2/10
40% 40%
10% 10% 10% 10%
2/1
3/11 3/12 3/13
10.1.14.0/30 10.2.14.0/30
vlan200
10G
2.568G
2.752G
.64G
50% 4.0G
cir = 40%
10%
3.2G
0.8G
100% 10G
eir = 100%
100%
10G
10G
SAOS 8.5 TOI
MC-LAG
Contributors:
MC-LAG – Background
802.1ax LAG
802.1ax LAG
DHD
Redundancy
ICL Group (RG)
MC-LAG – Feature Description
3rd party switch
* Supported with
ICL one of the RGs
ICL being a 3rd party
RG
3rd party switch
MC-LAG – G.8032 support
ICL G.8032
MC-LAG – MPLS support
ICL VPLS Mesh
MC-LAG – Configuration
MC-LAG – Usage
MC-LAG – Usage
MC-LAG – Limitations/Caveats
Hands-On Session
Physical Topology
10.181.34.19 10.181.34.66
2/2 4/2
3/20 2/20
3/10 2/10
10.181.34.42
3/11 3/12
3/13
13
23 24
10.181.33.223
22
22
24 24
23 23
10.181.33.222 10.181.33.221
IP Topology
Team1 Team2
1.1.1.1 2.2.2.2
S1 2/2 10.1.2.0/30 4/2 S2

3/20 2/20
3/10 2/10
14.14.14.14
10.1.14.0/30
10.2.14.0/30
3/11 3/12
S14
10.2.4.0/30
3/13
10.1.3.0/30
10.13.14.0/30
49.0001
13
S13
23 24
13.13.13.13
22
22
24 24
S3 10.3.4.0/30 23
S4
23
4.4.4.4
3.3.3.3
Team3 Team4
PART A - Tunnel Robustness/Resiliency Exercise
1. From your Switch, execute a traceroute to the diagonally opposite Switch (eg. S1 to S4).explain
traceroute 4.4.4.4
2. Create a tunnel with autobackup on to the diagonally opposite switch. Determine the path of the primary and backup
tunnel. Explain. (REF. CATP 2.4.1)
gmpls tp-tunnel create rsvp-ingress-corout S1S4 dest-ip 4.4.4.4 auto-backup on
3. Enable LSP BFD session for your tunnel (REF. CATP 2.4.2)
4. Enable ISIS IP BFD Session for your ISIS interface (REF. CATP 2.4.3)
5. VPWS to diagonally opposite Team with FEC 129 (REF. CATP 2.4.4)
6. LSP Switchover and Restoration ( REF. CATP 2.4.6 – 2.4.9)
PART B - Traffic Engineering Exercise - TE Metric – CATP 3.1.1
1. Assign the following TE Metrics

2. Create tunnel to diagonally opposite team with auto backup on
3. Look at path of primary and secondary LSP. Explain
TE=500
TE=100
TE=100
TE=10
TE=100
PART C - Traffic Engineering Exercise – Resource Affinity CATP 3.1.2
1. Assign the following Resource Affinity to the various links. Keep the TE Metrics from previous exercise.
2. Create tunnel to diagonally opposite team with auto backup with a constraint that INCLUDES Yellow
4. Create tunnel to diagonally opposite team with auto backup with a constraint that INCLUDES Green
6. Create tunnel to diagonally opposite team with auto backup with a constraint that EXCLUDES Yellow
GREEN/YELLOW
GREEN/YELLOW
GREEN/YELLOW
YELLOW
GREEN
PART D - Traffic Engineering Exercise – SRLG - CATP 3.1.3
1. Assign the following SRLG to the various links. Keep the TE Metrics from previous exercise.
2. Create tunnel to diagonally opposite team with auto backup
SRLG=2
SRLG=2
SRLG=2
SRLG=1
SRLG=3,4
Whiteboard Exercise
Part 1: On-Demand Voice&Data Service
Provider X wants to offer on demand pay-per-use voice and data services to multiple business customers at various common site(eg. Shopping Centers, Office
Buildings). Customers will have the ability to order voice circuits and data bandwidth via a portal. Each voice service instance will consume 300kbps.
They intend to offer two levels of data service: Gold is aimed at customers such as hospitals and will provide a guaranteed 400 Mbps high priority high reliable
data access service with an option to dynamically grow the service up to 1Gbps. Silver will provide 100Mbps with an option to grow to 250Mbps. That offer
does not provide any reliability SLA KPIs. It is not expected for each site to exceed 10G in traffic. The provider wants to dynamically provision the service to
maximize the available bandwidth.
Traffic from each customer will be tagged with one of two values. All voice calls for one customer will be tagged with one value. Data traffic for the customer
will be tagged with a different value.
The provider is looking to carry the layer 2 traffic from each site to their central office. To ensure resiliency, they have two routers as their gateways to their
IP/MPLS based IP core network. Their main gateway is located in Montreal but have a backup one in Toronto. They prefer not to invest further in Toronto
and prefer for their traffic to transit via Montreal.
A third of their client base is located within a 300km radius of Montreal is spread around 5 different sites which act as a hub for the other sites. Two of the
hubs are physically connected to the CO where the Montreal Gateway is located. One of the hub is physically connected to the Toronto Location and two
hubs are connected via two fibers to two Ottawa Hubs via an optical amplifier in Hawkesbury.
Another third of the client base is located within a 200km radius Ottawa is spread around 3 different hub sites. Two hubs are connected to Montreal via the
previously mentioned fibers and two are connected to the Toronto location. For some customers, the equipment needs to be weather tempered.
The final third of the client base is located within a 400km radius of Toronto is spread around 7 sites. One hub is connected to the Ottawa location via two
fibers and one hub is physically connected to Montreal.
Provider X’s Operations group insists on having a distinct IP subnet for each city for their management DCN.
Network Risk Analysis
History shows three of the links near Toronto are prone to cuts during spring.
Some customers have sites in two of the cities and require that one site is always connected to the
internet.
Diagram
same
customer DCN
Part 2, Transport Network Extension
Provider X requires to extend the network designed in part 1 into New York city with similar Ethernet services capabilities as in Montreal,
Ottawa and Toronto.
The following additional transport network capabilities are also needed:
• Timing-transparent point-to-point 10GE services

• OC-48 and OC-192 SONET transport capabilities
Diagram
same
customer
DCN
Device/feature Requirements
They are asking the vendors to come up with an efficient design to satisfy their needs including proper
DCN design to manage devices. They have used Ciena products in some of their solutions before but
they don’t feel G8032 is the way to go and would prefer a MPLS based approach for both their services
and their DCN Network.
From You
- You need to propose devices from our portfolio that fit this requirement.
- Number of sites they need to collect traffic is 30 (max).
- You need to come up with the DCN design for the provider to manage the access L2 devices including
an OS proposal.
- Finished design should be presented to the audience in the class (power point). Any value added
propositions should be highlighted

2017 Expert Packet Workshop V3 + Exercise

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

2017 Expert Packet Workshop V3 + Exercise

Caricato da

Copyright:

Formati disponibili

2017 Expert Packet Workshop

Including 6.16/8.5 and 6500 R12.1 Features

Metro Ethernet MPLS Metro Ethernet

Break 09:30 – 09:45

Lunch 12:15 – 13:15

Customer Ethernet Data

MPLS Tunnels View

Physical Layer VIew

Field Name Size (bits) Purpose

0x96A Len=4 PW Status TLV

Field Size Description

TLV length 8-bits Total length of all TLVs

Flags 7-bits Set to zero on send and ignored on receive

Static Pseudowire View

Dynamic Pseudowire View

TLDP = Targeted LDP

(not to be confused with Topology LDP)

MPLS Tunnels View

Tunnel Label (same Label as Data Plane LSP)

OAM packets can be sent at

Data Packet CC OAM Packet CV OAM Packet

Original Frame Gach Gach

BFD Control Packet BFD Control Packet

CC/BFD Packet Format Unique MEP-ID of source of the BFD packet

CV/BFD Packet Format

0x0022 MPLS-TP CC Message

MPLS Static Tunnels View

Primary Tunnel Manually

Associated MPLS-TP Tunnels

Primary Tunnel RSVP

Associated MPLS-TP Tunnels 6.16

Step 1 : A uni-directional tunnel is created using RSVP

PATH message upstream label creates reverse LSP from D to A

100 200 300

RESV message label creates forward LSP from A to D

Customer Ethernet Data

MPLS Dynamic Tunnels View

Primary Tunnel RSVP

Physical Layer VIew

Customer Ethernet Data

Static Pseudowire View

MPLS Static Tunnels View

Primary Tunnel Manually

Physical Layer VIew

Customer Ethernet Data

MPLS Static Tunnels View

Primary Tunnel Manually

Physical Layer VIew

Customer Ethernet Data

Static Pseudowire View

MPLS Dynamic Tunnels View

Primary Tunnel RSVP

Physical Layer VIew

6500_0007*> gmpls tp-tunnel create <TAB>

> arp static show

6500_0007*> gmpls tp-tunnel create <TAB>

Tunnel Header Tunnel Header Tunnel Header

Default LSP reply-mode

6500-1> mpls ping tp-tunnel-ingress-corout tunnel_to_S4

--------------- Statistics ---------------

Same applies for Trace route

Releases PW Type VCCV Profile CC-Type selected Tunnel CC-Type

AIS LSP BFD