Вы находитесь на странице: 1из 294

Alcatel-Lucent

Service Router | Release 13.0.R10


SR OS Software Release Notes | June 2016

3HE09898 0010 TQZZA Edition 01

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.
The information presented is subject to change without notice. Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2016 Alcatel-Lucent
All Rights Reserved.
Table of Contents

Table of Contents

About this Document....................................................................................................................... 1

Release 13.0.R10 Documentation Set ............................................................................................ 2


Release 13.0.R10 Supported Hardware ......................................................................................... 4
Supported Chassis Configurations ...............................................................................................................4
Supported Cards (SFM, CPM, XCM, CCM, CFM, MCM, IOM, IMM, ISM)...................................................5
Supported Adapters (XMA, MDA, ISA, CMA, VSM) ...................................................................................16

New Features ................................................................................................................................. 26


Release 13.0.R10.......................................................................................................................................26
Release 13.0.R9 .........................................................................................................................................26
Release 13.0.R8 .........................................................................................................................................28
Release 13.0.R7 .........................................................................................................................................28
Release 13.0.R6 .........................................................................................................................................29
Release 13.0.R5 .........................................................................................................................................31
Release 13.0.R4 .........................................................................................................................................33
Release 13.0.R3 .........................................................................................................................................51
Release 13.0.R2 .........................................................................................................................................51
Release 13.0.R1 .........................................................................................................................................51

Enhancements ............................................................................................................................... 77
Release 13.0.R10.......................................................................................................................................77
Release 13.0.R9 .........................................................................................................................................77
Release 13.0.R8 .........................................................................................................................................78
Release 13.0.R7 .........................................................................................................................................79
Release 13.0.R6 .........................................................................................................................................80
Release 13.0.R5 .........................................................................................................................................83
Release 13.0.R4 .........................................................................................................................................84
Release 13.0.R3 .........................................................................................................................................93
Release 13.0.R2 .........................................................................................................................................95
Release 13.0.R1 .........................................................................................................................................96

Limited Support Features and Enhancements ......................................................................... 106

Unsupported Features ................................................................................................................ 107


Hardware ..................................................................................................................................................107
System......................................................................................................................................................108
Quality of Service ....................................................................................................................................109
Routing .....................................................................................................................................................109
MPLS ........................................................................................................................................................110
Services ....................................................................................................................................................110
Subscriber Management ..........................................................................................................................111
Application Assurance ..............................................................................................................................112

Deprecated Features ................................................................................................................... 113


Release 13.0.R10.....................................................................................................................................113
Release 13.0.R9 .......................................................................................................................................113
Release 13.0.R8 .......................................................................................................................................113

SR OS 13.0.R10 Software Release Notes


Table of Contents

Release 13.0.R7 .......................................................................................................................................113


Release 13.0.R6 .......................................................................................................................................113
Release 13.0.R5 .......................................................................................................................................113
Release 13.0.R4 .......................................................................................................................................113
Release 13.0.R3 .......................................................................................................................................113
Release 13.0.R2 .......................................................................................................................................114
Release 13.0.R1 .......................................................................................................................................114

Changed or Deprecated Commands.......................................................................................... 115


Release 13.0.R10.....................................................................................................................................115
Release 13.0.R9 .......................................................................................................................................115
Release 13.0.R8 .......................................................................................................................................115
Release 13.0.R7 .......................................................................................................................................115
Release 13.0.R6 .......................................................................................................................................116
Release 13.0.R5 .......................................................................................................................................116
Release 13.0.R4 .......................................................................................................................................116
Release 13.0.R3 .......................................................................................................................................118
Release 13.0.R2 .......................................................................................................................................118
Release 13.0.R1 .......................................................................................................................................118

Usage Notes ................................................................................................................................. 135

Software Upgrade Procedures ................................................................................................... 151


Software Upgrade Notes ..........................................................................................................................151
AA Signatures Upgrade Procedure ..........................................................................................................156
ISSU Upgrade Procedure .........................................................................................................................161
Standard Software Upgrade Procedure ...................................................................................................174

Known Limitations....................................................................................................................... 178


Resolved Issues........................................................................................................................... 231
Release 13.0.R10.....................................................................................................................................231
Release 13.0.R9 .......................................................................................................................................234
Release 13.0.R8 .......................................................................................................................................237
Release 13.0.R7 .......................................................................................................................................241
Release 13.0.R6 .......................................................................................................................................245
Release 13.0.R5 .......................................................................................................................................250
Release 13.0.R4 .......................................................................................................................................255
Release 13.0.R3 .......................................................................................................................................263
Release 13.0.R2 .......................................................................................................................................268
Release 13.0.R1 .......................................................................................................................................271

Known Issues............................................................................................................................... 276

Change History for Release 13.0 Release Notes ...................................................................... 287


Technical Support ....................................................................................................................... 289

SR OS 13.0.R10 Software Release Notes


List of Tables

List of Tables
Table 1. Release 13.0.R10 Documentation Set ................................................................................................2
Table 2. Supported 7950 XRS Chassis Configurations .....................................................................................4
Table 3. Supported 7750 SR and 7450 ESS Chassis .......................................................................................4
Table 4. SFM, CPM, CCM, and XCM Cards Supported in 7950 XRS...............................................................5
Table 5. SFM, CPM, CFM, MCM, CCM, IOM, IMM, and ISM Cards Supported in 7750 SR.............................5
Table 6. SFM, CPM, IOM, IMM, and ISM Cards Supported in 7450 ESS in Non-Mixed Mode.......................10
Table 7. IOM, IMM, and ISM Cards Supported in the 7450 ESS in Mixed Mode ............................................14
Table 8. XMAs and C-XMAs Supported in 7950 XRS .....................................................................................16
Table 9. MDAs, CMAs, and ISAs Supported in 7750 SR ................................................................................17
Table 10. MDAs, ISAs, and VSMs Supported in 7450 ESS in Non-Mixed Mode ...........................................20
Table 11. MDAs, ISAs, and VSMs Supported in the 7450 ESS in Mixed Mode ..............................................23
Table 12. Features Added Earlier than Release 13.0.R10 ..............................................................................26
Table 13. Additional Hardware Assemblies with 1G Port IEEE 1588 Port-Based Timestamping Capability...28
Table 14. Additional Hardware with IEEE 1588 Port-Based Timestamping Capability ...................................30
Table 15. 7750 SR-a4/a8 with IEEE 1588 Port-Based Timestamping Capability............................................32
Table 16. Additional Hardware with IEEE 1588 Port-Based Timestamping Capability ...................................32
Table 17. Additional Hardware with IEEE 1588 Port-Based Timestamping Capability ...................................35
Table 18. New and Updated AA Protocols in Release 13.0.R5.......................................................................84
Table 19. New and Updated AA Protocols in Release 13.0.R4.......................................................................91
Table 20. New and Updated AA Protocols in Release 13.0.R3.......................................................................95
Table 21. New and Updated AA Protocols in Release 13.0.R2.......................................................................96
Table 22. New and Updated AA Protocols in Release 13.0.R1.....................................................................105
Table 23. Unsupported Hardware Features ..................................................................................................107
Table 24. Unsupported System Features ......................................................................................................108
Table 25. Unsupported QoS Features ...........................................................................................................109
Table 26. Unsupported Routing Features......................................................................................................109
Table 27. Unsupported MPLS Features ........................................................................................................110
Table 28. Unsupported Services Features ....................................................................................................110
Table 29. Unsupported Subscriber Management Features...........................................................................111
Table 30. Unsupported AA Features .............................................................................................................112
Table 31. Compatible 7750 SR IOMs and IMMs for MS-ISA/MS-ISA2 Applications ....................................135
Table 32. Compatible 7450 ESS IOMs and IMMs for MS-ISA/MS-ISA2 Applications...................................136
Table 33. Compatible 7450 ESS Mixed Mode IOMs and IMMs for MS-ISA/MS-ISA2 Applications ..............137
Table 34. Compatible Devices for dynamic LAN-to-LAN IPsec Tunnels ......................................................146
Table 35. Compatible IPsec Soft Client ........................................................................................................146
Table 36. BFD VCCV Interoperability with Juniper MX .................................................................................148
Table 37. Nuage VSD and SR OS Node XMPP Compatibility ......................................................................148
Table 38. Nuage VSP and SR OS Node EVPN Compatibility .......................................................................149
Table 39. ATM MDAs that Support Access Mode Only .................................................................................186
Table 40. Issues Resolved Earlier than Release 13.0.R10 ...........................................................................234
Table 41. Change History ..............................................................................................................................287

SR OS 13.0.R10 Software Release Notes


About this Document

About this Document


This document provides an overview of SR OS in Release 13.0.R10 for the 7450 Ethernet
Service Switch (ESS), 7750 Service Router (SR), and 7950 eXtensible Routing System (XRS)
platforms.
In this document, the terms “SR OS node” and “SR OS chassis” refer to the 7450 ESS, 7750
SR, and 7950 XRS platforms.

Note:
Unless otherwise stated, the term “ISA” refers to any of the following hardware assemblies:
• MS-ISA/MS-ISA-E MDAs (for example, the 7750 SR/7450 ESS Multiservice ISA)
• MS-ISM/MS-ISM-E
• any IMMs containing MS-ISA2/MS-ISA2-E cards (for example, 7x50 MS-ISA2 + 1-
port 100GE CFP IMM – L3BQ)
• MS-ISA2 and MS-ISA2-E in IOM4-e

SR OS 13.0.R10 Software Release Notes 1


Release 13.0.R10 Documentation Set

Release 13.0.R10 Documentation Set


The SR OS Release 13.0.R10 documentation set consists of Release Notes and the 7450 ESS,
7750 SR, and 7950 XRS user guides. The components of the Release 13.0.R10 documentation
set are listed in Table 1. New guides are printed in bold.

Table 1. Release 13.0.R10 Documentation Set

Document title Platform Part number


SR OS 13.0.R10 Software Release Notes 7450 ESS 3HE09898 0010 TQZZA 01
7750 SR
7950 XRS
13.0 AA Protocols and Applications for the 7450 ESS 3HE 10507 AAAA TQZZA
7450 ESS and 7750 SR 7750 SR
Advanced Configuration Guide for 7450 ESS, 7450 ESS 3HE 10564 AAAA TQZZA
7750 SR and 7950 XRS for Releases up to 7750 SR
13.0.R6 - Part I
7950 XRS
Advanced Configuration Guide for 7450 ESS, 7450 ESS 3HE 10565 AAAA TQZZA
7750 SR and 7950 XRS for Releases up to 7750 SR
13.0.R6 - Part II
7950 XRS
Basic System Configuration Guide 7450 ESS 3HE09844 AAAB TQZZA
7750 SR 3HE09826 AAAB TQZZA
7950 XRS 3HE09861 AAAB TQZZA
Interface Configuration Guide 7450 ESS 3HE09845 AAAB TQZZA
7750 SR 3HE09827 AAAB TQZZA
7950 XRS 3HE09862 AAAB TQZZA
Gx AVPs Reference Guide 7750 SR 3HE09828 AAAB TQZZA
Layer 2 Services and EVPN Guide: VLL, 7450 ESS 3HE09847 AAAB TQZZA
VPLS, PBB, and EVPN 7750 SR 3HE09829 AAAB TQZZA
7950 XRS 3HE09864 AAAB TQZZA
Layer 3 Services Guide: Internet Enhanced 7450 ESS 3HE09848 AAAB TQZZA
Services and Virtual Private Routed Net- 7750 SR 3HE09830 AAAB TQZZA
work Services
7950 XRS 3HE09865 AAAB TQZZA
MPLS Guide 7450 ESS 3HE09849 AAAB TQZZA
7750 SR 3HE09831 AAAB TQZZA
7950 XRS 3HE09866 AAAB TQZZA
Multiservice Integrated Service Adapter Guide 7450 ESS 3HE09832 AAAB TQZZA
7750 SR
OAM and Diagnostics Guide 7450 ESS 3HE09850 AAAB TQZZA
7750 SR 3HE09833 AAAB TQZZA
7950 XRS 3HE09867 AAAB TQZZA

2 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Documentation Set

Table 1. Release 13.0.R10 Documentation Set (Continued)

Document title Platform Part number


Quality of Service Guide 7450 ESS 3HE09851 AAAB TQZZA
7750 SR 3HE09834 AAAB TQZZA
7950 XRS 3HE09868 AAAB TQZZA
RADIUS Attributes Reference Guide 7750 SR 3HE09835 AAAB TQZZA
Router Configuration Guide 7450 ESS 3HE09853 AAAB TQZZA
7750 SR 3HE09836 AAAB TQZZA
7950 XRS 3HE09870 AAAB TQZZA
Routing Protocols Guide 7450 ESS 3HE09854 AAAB TQZZA
7750 SR 3HE09837 AAAB TQZZA
7950 XRS 3HE09871 AAAB TQZZA
Services Overview Guide 7450 ESS 3HE09855 AAAB TQZZA
7750 SR 3HE09838 AAAB TQZZA
7950 XRS 3HE09872 AAAB TQZZA
System Management Guide 7450 ESS 3HE09856 AAAB TQZZA
7750 SR 3HE09839 AAAB TQZZA
7950 XRS 3HE09873 AAAB TQZZA
Triple Play Service Delivery Architecture 7450 ESS 3HE09857 AAAB TQZZA
Guide 7750 SR 3HE09840 AAAB TQZZA
Versatile Service Module Guide 7750 SR 3HE09841 AAAB TQZZA
Zipped collection of documents 7450 ESS 3HE09860 AAAB TQZZA
7750 SR 3HE09843 AAAB TQZZA
7950 XRS 3HE09876 AAAB TQZZA

SR OS 13.0.R10 Software Release Notes 3


Release 13.0.R10 Supported Hardware

Release 13.0.R10 Supported Hardware


The following tables summarize the hardware supported in SR OS Release 13.0.R10. New
hardware supported since SR OS Release 12.0.R1 is printed in bold.

Supported Chassis Configurations

Table 2. Supported 7950 XRS Chassis Configurations

Alcatel-Lucent
Model # Description
7950 XRS-16c A single 33RU chassis that holds up to 8 XCMs and 16 C-XMAs
7950 XRS-20 A single 48RU chassis that holds up to 10 XCMs and 20 XMAs or C-XMAs
7950 XRS-40 Contains two (2) XRS-20 chassis that hold up to 40 XMAs

Table 3. Supported 7750 SR and 7450 ESS Chassis

Alcatel-Lucent
Model # Description
7750 SR-1e 7750 SR-1e chassis (AC and DC)
7750 SR-2e 7750 SR-2e chassis (AC and DC)
7750 SR-3e 7750 SR-3e chassis (AC and DC)
7750 SR-7 7750 SR-7 chassis (AC and DC)
7750 SR-12 7750 SR-12 chassis (AC and DC)
7750 SR-12e 7750 SR-12e integrated chassis
7750 SR-a4 7750 SR-a4 chassis (AC and DC)
7750 SR-a8 7750 SR-a8 chassis (AC and DC)
7750 SR-c4 7750 SR-c4 chassis (AC and DC)
7750 SR-c12 7750 SR-c12 chassis (AC and DC)
7450 ESS-6 7450 ESS-6 chassis (AC and DC)
7450 ESS-6v 7450 ESS-6v chassis (vertical ESS-6)
7450 ESS-7 7450 ESS-7 chassis (AC and DC)
7450 ESS-12 7450 ESS-12 chassis (AC and DC)

4 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Supported Cards (SFM, CPM, XCM, CCM, CFM, MCM, IOM, IMM,
ISM)
The following tables summarize the Switch Fabric/Control Processor Modules (SF/CPMs,
CPMs, or SFMs), XMA Control Modules (XCMs), Connection and Control Modules (CCMs),
Control and Forwarding Modules (CFMs), MDA Carrier Modules (MCMs), Chassis Control
Modules (CCMs), Input/Output Modules (IOMs), Integrated Media Modules (IMMs), and
Integrated Services Modules (ISMs) supported in SR OS Release 13.0.R10.

Table 4. SFM, CPM, CCM, and XCM Cards Supported in 7950 XRS

Alcatel-Lucent
Part # Description
3HE06936AA 7950 XRS-20 XMA Control Module (XCM-X20)
3HE07115AA 7950 XRS-20 Switch Fabric Module (SFM-X20)
3HE07116AA 7950 XRS-20 Control Processor Module (CPM-X20)
3HE07117AA 7950 XRS-20 Connection and Control Module (CCM-X20)
3HE08021AA 7950 XRS-20 Switch Fabric Module B (SFM-X20-B)
3HE08120AA 7950 XRS-16c Switch Fabric Module (SFM-X16)
3HE08121AA 7950 XRS-16c Control Processor Module (CPM-X16)
3HE08125AA 7950 XRS-16c XMA Control Module (XCM-X16)
3HE08505AA 7950 XRS-20 Standalone Switch Fabric Module B (SFM-X20S-B)
3HE09280AA 7950 XRS-16c XCM with XMA support

Table 5. SFM, CPM, CFM, MCM, CCM, IOM, IMM, and ISM Cards Supported in
7750 SR

SR-1e/2e/3e
SR-a4/a8
SR-c12

SR-12e
SR-12
SR-7
Alcatel-Lucent
Part # Description
3HE00020AB 7750 SR 20G Input Output Module (IOM)
✓ ✓
Baseboard (iom-20g-b)
3HE01170AA 7750 SR 400G SF/CPM2 ✓ ✓
3HE01171AA 7750 SR 200G SF/CPM2 ✓
3HE01473AA 7750 SR 20G Input Output Module (IOM2)
✓ ✓
Baseboard (iom2-20g)
3HE03607AA 7750 SR-c12 CFM-XP ✓
3HE03608AA 7750 SR-c4/c12 MCM-XP 1 ✓
3HE03617AA 7750 SR-12 SF/CPM3 ✓ ✓
3HE03619AA 7750 SR IOM3-XP (iom3-xp) ✓ ✓ ✓
3HE03622AA 7750 SR 4-port 10GE XFP IOM (IMM) ✓ ✓
3HE03623AA 7750 SR 8-port 10GE XFP IOM (IMM) ✓ ✓
3HE03624AA 7750 SR 48-port GE SFP IOM (IMM) ✓ ✓ ✓

SR OS 13.0.R10 Software Release Notes 5


Release 13.0.R10 Supported Hardware

Table 5. SFM, CPM, CFM, MCM, CCM, IOM, IMM, and ISM Cards Supported in
7750 SR (Continued)

SR-1e/2e/3e
SR-a4/a8
SR-c12

SR-12e
SR-12
SR-7
Alcatel-Lucent
Part # Description
3HE03625AA 7750 SR 48-port GE copper/TX IOM (IMM) ✓ ✓ ✓
3HE04164AA 7750 SR-7 SF/CPM3 ✓
3HE04580AA 7750 SR-c12 CCM-XP ✓
3HE04741AA 7750 SR 5-port 10GE XFP IOM (IMM) ✓ ✓ ✓
3HE04743AAAB 7x50 12-port 10G Ethernet SFP+ IMM – L3HQ ✓ ✓
3HE05053AAAB 7x50 1-port 100G Ethernet CFP IMM – L3HQ ✓ ✓
3HE05055AA 7x50 1-port OC-768c/STM-256c OTU3 Long
✓ ✓ ✓
Reach DWDM Tunable IMM – L3HQ
3HE05553AA 7x50 12-port 10G Ethernet SFP+ IMM – L2HQ ✓ ✓
3HE05553BA 7x50 12-port 10G Ethernet SFP+ IMM – L3BQ ✓ ✓
3HE05813AA 7x50 1-port OC-768c/STM-256c OTU3 Long
✓ ✓ ✓
Reach DWDM Tunable IMM – L2HQ
3HE05813BA 7x50 1-port OC-768c/STM-256c OTU3 Long
✓ ✓ ✓
Reach DWDM Tunable IMM – L3BQ
3HE05814AA 7x50 1-port 100G Ethernet CFP IMM – L2HQ ✓ ✓
3HE05814BA 7x50 1-port 100G Ethernet CFP IMM – L3BQ ✓ ✓
3HE05895AA 7x50 48-port GE SFP IOM (IMM) – L2HQ ✓ ✓ ✓
3HE05895BA 7x50 48-port GE SFP IOM (IMM) – L3BQ ✓ ✓ ✓
3HE05896AA 7x50 48-port GE copper/TX IOM (IMM) –
✓ ✓ ✓
L2HQ
3HE05896BA 7x50 48-port GE copper/TX IOM (IMM) –
✓ ✓ ✓
L3BQ
3HE05898AA 7x50 5-port 10GE XFP IOM (IMM) – L2HQ ✓ ✓ ✓
3HE05898BA 7x50 5-port 10GE XFP IOM (IMM) – L3BQ ✓ ✓ ✓
3HE05899AA 7x50 8-port 10GE XFP IOM (IMM) – L2HQ ✓ ✓
3HE05899BA 7x50 8-port 10GE XFP IOM (IMM) – L3BQ ✓ ✓
3HE05948AA 7750 SR-12 SF/CPM4 ✓
3HE05949AA 7750 SR-7 SF/CPM4 ✓
3HE06318AA 7750 Multicore-CPU IOM3-XP-B ✓ ✓ ✓
3HE06320AA 7x50 3-port 40GE QSFP IMM – L3HQ ✓ ✓
3HE06326AA 7x50 48-port GE Multicore-CPU SFP IMM –
✓ ✓ ✓
L3HQ
3HE06326BA 7x50 48-port GE Multicore-CPU SFP IMM –
✓ ✓ ✓
L3BQ
3HE06326CA 7x50 48-port GE Multicore-CPU SFP IMM –
✓ ✓ ✓
L2HQ

6 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 5. SFM, CPM, CFM, MCM, CCM, IOM, IMM, and ISM Cards Supported in
7750 SR (Continued)

SR-1e/2e/3e
SR-a4/a8
SR-c12

SR-12e
SR-12
SR-7
Alcatel-Lucent
Part # Description
3HE06428AA 7x50 48-port GE SFP IOM (IMM) – L3HQ ✓ ✓ ✓
3HE06429AA 7x50 48-port GE copper/TX IOM (IMM) –
✓ ✓ ✓
L3HQ
3HE06430AA 7x50 5-port 10GE XFP IOM (IMM) – L3HQ ✓ ✓ ✓
3HE06431AA 7x50 8-port 10GE XFP IOM (IMM) – L3HQ ✓ ✓
3HE06721AA 7x50 3-port 40GE QSFP IMM – L2HQ ✓ ✓
3HE06721BA 7x50 3-port 40GE QSFP IMM – L3BQ ✓ ✓
3HE06798AA 7750 1-port 40GE DWDM Tunable IMM –
✓ ✓ ✓
L3HQ
3HE06798BA 7750 1-port 40GE DWDM Tunable IMM –
✓ ✓ ✓
L3BQ
3HE06798CA 7750 1-port 40GE DWDM Tunable IMM –
✓ ✓ ✓
L2HQ
3HE07158AA 7x50 12-port 10GE FP3 SFP+ IMM – L3HQ ✓ ✓ ✓
3HE07158BA 7x50 12-port 10GE FP3 SFP+ IMM – L3BQ ✓ ✓ ✓
3HE07158CA 7x50 12-port 10GE FP3 SFP+ IMM – L2HQ ✓ ✓ ✓
3HE07159AA 7x50 1-port 100GE FP3 CFP IMM – L3HQ ✓ ✓ ✓
3HE07159BA 7x50 1-port 100GE FP3 CFP IMM – L3BQ ✓ ✓ ✓
3HE07159CA 7x50 1-port 100GE FP3 CFP IMM – L2HQ ✓ ✓ ✓
3HE07166AA 7750 SR-12e SF/CPM4-12e ✓
3HE07167AA 7750 SR-12e Mini-SFM4-12e ✓
3HE07303AA 7x50 2-port 100GE FP3 CFP IMM – L3HQ ✓ ✓ ✓
3HE07303BA 7x50 2-port 100GE FP3 CFP IMM – L3BQ ✓ ✓ ✓
3HE07303CA 7x50 2-port 100GE FP3 CFP IMM – L2HQ ✓ ✓ ✓
3HE07304AA 7x50 6-port 40GE FP3 QSFP IMM – L3HQ ✓ ✓ ✓
3HE07304BA 7x50 6-port 40GE FP3 QSFP IMM – L3BQ ✓ ✓ ✓
3HE07304CA 7x50 6-port 40GE FP3 QSFP IMM – L2HQ ✓ ✓ ✓
3HE07305AA 7x50 20-port 10GE FP3 SFP+ IMM – L3HQ ✓ ✓ ✓
3HE07305BA 7x50 20-port 10GE FP3 SFP+ IMM – L3BQ ✓ ✓ ✓
3HE07305CA 7x50 20-port 10GE FP3 SFP+ IMM – L2HQ ✓ ✓ ✓
3HE08019AA 7x50 1-port 100GE DWDM Tunable FP3 IMM
✓ ✓ ✓
– L3HQ
3HE08019BA 7x50 1-port 100GE DWDM Tunable FP3 IMM
✓ ✓ ✓
– L3BQ
3HE08019CA 7x50 1-port 100GE DWDM Tunable FP3 IMM
✓ ✓ ✓
– L2HQ

SR OS 13.0.R10 Software Release Notes 7


Release 13.0.R10 Supported Hardware

Table 5. SFM, CPM, CFM, MCM, CCM, IOM, IMM, and ISM Cards Supported in
7750 SR (Continued)

SR-1e/2e/3e
SR-a4/a8
SR-c12

SR-12e
SR-12
SR-7
Alcatel-Lucent
Part # Description
3HE08020AA 7x50 1-port 100GE CFP + 10-port 10GE SFP+
✓ ✓ ✓
FP3 IMM – L3HQ
3HE08020BA 7x50 1-port 100GE CFP + 10-port 10GE SFP+
✓ ✓ ✓
FP3 IMM – L3BQ
3HE08020CA 7x50 1-port 100GE CFP + 10-port 10GE SFP+
✓ ✓ ✓
FP3 IMM – L2HQ
3HE08173AA 7750 SR-c12 CFM-XP-B ✓
3HE08174AA 7x50 10-port 10GE SFP+ + 20-port GE SFP
✓ ✓ ✓
FP3 IMM – L3HQ
3HE08174BA 7x50 10-port 10GE SFP+ + 20-port GE SFP
✓ ✓ ✓
FP3 IMM – L3BQ
3HE08174CA 7x50 10-port 10GE SFP+ + 20-port GE SFP
✓ ✓ ✓
FP3 IMM – L2HQ
3HE08175AA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3
✓ ✓ ✓
IMM – L3HQ
3HE08175BA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3
✓ ✓ ✓
IMM – L3BQ
3HE08175CA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3
✓ ✓ ✓
IMM – L2HQ
3HE08421AA 7750 SR SF/CPM5-12e ✓
3HE08422AA 7750 SR Mini-SFM5-12e ✓
3HE08423AA 7750 SR CPM5 ✓ ✓ ✓
3HE08424AA 7x50 40-port 10GE SFP+ IMM – L3HQ ✓
3HE08424BA 7x50 40-port 10GE SFP+ IMM – L3BQ ✓
3HE08424CA 7x50 40-port 10GE SFP+ IMM – L2HQ ✓
3HE08425AA 7x50 4-port 100GE CXP IMM – L3HQ ✓
3HE08425BA 7x50 4-port 100GE CXP IMM – L3BQ ✓
3HE08425CA 7x50 4-port 100GE CXP IMM – L2HQ ✓
3HE08426AA 7750 SR IOM3-XP-C ✓ ✓ ✓
3HE08428AA 7750 SR SFM5-12 ✓
3HE08429AA 7750 SR SFM5-7 ✓
3HE09117AA 7x50 Multiservice ISM ✓ ✓ ✓
3HE09118AA 7x50 Multiservice ISM-E (no encryption) ✓ ✓ ✓
3HE09192AA 7x50 MS-ISA2 + 1-port 100GE CFP IMM –
✓ ✓ ✓
L3HQ
3HE09192BA 7x50 MS-ISA2 + 1-port 100GE CFP IMM –
✓ ✓ ✓
L3BQ

8 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 5. SFM, CPM, CFM, MCM, CCM, IOM, IMM, and ISM Cards Supported in
7750 SR (Continued)

SR-1e/2e/3e
SR-a4/a8
SR-c12

SR-12e
SR-12
SR-7
Alcatel-Lucent
Part # Description
3HE09192CA 7x50 MS-ISA2 + 1-port 100GE CFP IMM –
✓ ✓ ✓
L2HQ
3HE09193AA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM –
✓ ✓ ✓
L3HQ
3HE09193BA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM –
✓ ✓ ✓
L3BQ
3HE09193CA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM –
✓ ✓ ✓
L2HQ
3HE09201AA 7750 SR-a CPM ✓
3HE09202AA 7750 SR-a IOM – L3HQ ✓
3HE09202BA 7750 SR-a IOM – L3BQ ✓
3HE09202CA 7750 SR-a IOM – L2HQ ✓
3HE09253AA 7x50 MS-ISA2-E + 1-port 100GE CFP IMM
✓ ✓ ✓
– L3HQ
3HE09253BA 7x50 MS-ISA2-E + 1-port 100GE CFP IMM
✓ ✓ ✓
– L3BQ
3HE09253CA 7x50 MS-ISA2-E + 1-port 100GE CFP IMM
✓ ✓ ✓
– L2HQ
3HE09254AA 7x50 MS-ISA2-E + 10-port 10G SFP+ IMM
✓ ✓ ✓
– L3HQ
3HE09254BA 7x50 MS-ISA2-E + 10-port 10G SFP+ IMM
✓ ✓ ✓
– L3BQ
3HE09254CA 7x50 MS-ISA2-E + 10-port 10G SFP+ IMM
✓ ✓ ✓
– L2HQ
3HE09260AA 7750 SR SFM5-12 + CPM5 ✓
3HE09261AA 7750 SR SFM5-7 + CPM5 ✓
3HE09279AA 7x50 48-port GE Multicore SFP IMM –
✓ ✓ ✓
L3HQ
3HE09279BA 7x50 48-port GE Multicore SFP IMM –
✓ ✓ ✓
L3BQ
3HE09279CA 7x50 48-port GE Multicore SFP IMM –
✓ ✓ ✓
L2HQ
3HE09645AA 7x50 4-Port 100GE CFP4 IMM – L3HQ ✓
3HE09645BA 7x50 4-Port 100GE CFP4 IMM – L3BQ ✓
3HE09645CA 7x50 4-Port 100GE CFP4 IMM – L2HQ ✓
3HE09648AA IOM – 7750 SR IOM4-e L3HQ 2 ✓ ✓ ✓
3HE09648BA IOM – 7750 SR IOM4-e L3BQ 2 ✓ ✓ ✓

SR OS 13.0.R10 Software Release Notes 9


Release 13.0.R10 Supported Hardware

Table 5. SFM, CPM, CFM, MCM, CCM, IOM, IMM, and ISM Cards Supported in
7750 SR (Continued)

SR-1e/2e/3e
SR-a4/a8
SR-c12

SR-12e
SR-12
SR-7
Alcatel-Lucent
Part # Description
3HE09648CA IOM – 7750 SR IOM4-e L2HQ2 ✓ ✓ ✓
3HE10014AA IMM – 160-port GE cSFP/80-port GE SFP –
✓ ✓ ✓
L3HQ2
3HE10014BA IMM – 160-port GE cSFP/80-port GE SFP –
✓ ✓ ✓
L3BQ2
3HE10014CA IMM – 160-port GE cSFP/80-port GE SFP –
✓ ✓ ✓
L2HQ2
3HE10309AA CCM – 7750 SR-e CCM-e ✓
3HE10310AA CPM – 7750 SR-e CPM-e ✓
3HE10311AA IOM – 7750 SR IOM-e L3HQ ✓
3HE10311BA IOM – 7750 SR IOM-e L2HQ ✓
3HE10311CA IOM – 7750 SR IOM-e L3BQ ✓
1. The MCM is supported in the 7750 SR-c4.
2. Supported with SFM3/4/5.

Table 6. SFM, CPM, IOM, IMM, and ISM Cards Supported in 7450 ESS in Non-
Mixed Mode

ESS-6/6v

ESS-12
ESS-7
Alcatel-Lucent
Part # Description
3HE00229AA 7450 ESS 2 x 10G MDA IOM Card ✓ ✓ ✓
3HE00229AB 7450 ESS IOM 20G LINE CARD (iom-20g-b) ✓ ✓ ✓
3HE01172AA 7450 ESS SF/CPM2 200G ✓
3HE02032AA 7450 ESS SF/CPM2 400G ✓ ✓
3HE02297AA 7450 ESS SF/CPM2 80G ✓
3HE03618AA 7450 ESS-12 SF/CPM3 ✓ ✓
3HE03619AA 7750 SR IOM3-XP (iom3-xp) ✓ ✓ ✓
3HE03620AA 7450 ESS IOM3-XP (iom3-xp) ✓ ✓ ✓
3HE03622AA 7750 SR 4-port 10GE XFP IOM (IMM) ✓ ✓ ✓
3HE03623AA 7750 SR 8-port 10GE XFP IOM (IMM) ✓ ✓ ✓
3HE03624AA 7750 SR 48-port GE SFP IOM (IMM) ✓ ✓ ✓
3HE03625AA 7750 SR 48-port GE copper/TX IOM (IMM) ✓ ✓ ✓
3HE04166AA 7450 ESS-7 SF/CPM3 ✓
3HE04741AA 7750 SR 5-port 10GE SFP IOM (IMM) ✓ ✓ ✓

10 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 6. SFM, CPM, IOM, IMM, and ISM Cards Supported in 7450 ESS in Non-
Mixed Mode (Continued)

ESS-6/6v

ESS-12
ESS-7
Alcatel-Lucent
Part # Description
3HE04743AAAB 7x50 12-port 10G Ethernet SFP+ IMM – L3HQ ✓ ✓
3HE05053AAAB 7x50 1-port 100G Ethernet CFP IMM- L3HQ ✓ ✓
3HE05055AA 7x50 1-port OC-768c/STM-256c OTU3 Long Reach DWDM
✓ ✓
Tunable IMM – L3HQ
3HE05553AA 7x50 12-port 10G Ethernet SFP+ IMM – L2HQ ✓ ✓
3HE05553BA 7x50 12-port 10G Ethernet SFP+ IMM – L3BQ ✓ ✓
3HE05813AA 7x50 1-port OC-768c/STM-256c OTU3 Long Reach DWDM
✓ ✓
Tunable IMM – L2HQ
3HE05813BA 7x50 1-port OC-768c/STM-256c OTU3 Long Reach DWDM
✓ ✓
Tunable IMM – L3BQ
3HE05814AA 7x50 1-port 100G Ethernet CFP IMM – L2HQ ✓ ✓
3HE05814BA 7x50 1-port 100G Ethernet CFP IMM – L3BQ ✓ ✓
3HE05895AA 7x50 48-port GE SFP IOM (IMM) – L2HQ ✓ ✓
3HE05895BA 7x50 48-port GE SFP IOM (IMM) – L3BQ ✓ ✓
3HE05896AA 7x50 48-port GE copper/TX IOM (IMM) – L2HQ ✓ ✓
3HE05896BA 7x50 48-port GE copper/TX IOM (IMM) – L3BQ ✓ ✓
3HE05898AA 7x50 5-port 10GE XFP IOM (IMM) – L2HQ ✓ ✓
3HE05898BA 7x50 5-port 10GE XFP IOM (IMM) – L3BQ ✓ ✓
3HE05899AA 7x50 8-port 10GE XFP IOM (IMM) – L2HQ ✓ ✓
3HE05899BA 7x50 8-port 10GE XFP IOM (IMM) – L3BQ ✓ ✓
3HE05950AA 7450 ESS-12 SF/CPM4 ✓
3HE05951AA 7450 ESS-7 SF/CPM4 ✓
3HE06318AA 7750 Multicore-CPU IOM3-XP-B ✓ ✓ ✓
3HE06320AA 7x50 3-port 40GE QSFP IMM- L3HQ ✓ ✓
3HE06324AA 7450 Multicore-CPU IOM3-XP-B ✓ ✓ ✓
3HE06326AA 7x50 48-port GE Multicore-CPU SFP IMM – L3HQ ✓ ✓ ✓
3HE06326BA 7x50 48-port GE Multicore-CPU SFP IMM – L3BQ ✓ ✓ ✓
3HE06326CA 7x50 48-port GE Multicore-CPU SFP IMM – L2HQ ✓ ✓ ✓
3HE06428AA 7x50 48-port GE SFP IOM (IMM) – L3HQ ✓ ✓
3HE06429AA 7x50 48-port GE copper/TX IOM (IMM) – L3HQ ✓ ✓
3HE06430AA 7x50 5-port 10GE XFP IOM (IMM) – L3HQ ✓ ✓
3HE06431AA 7x50 8-port 10GE XFP IOM (IMM) – L3HQ ✓ ✓
3HE06721AA 7x50 3-port 40GE QSFP IMM – L2HQ ✓ ✓
3HE06721BA 7x50 3-port 40GE QSFP IMM – L3BQ ✓ ✓
3HE06798AA 7750 1-port 40GE DWDM Tunable IMM – L3HQ ✓ ✓ ✓
3HE06798BA 7750 1-port 40GE DWDM Tunable IMM – L3BQ ✓ ✓ ✓

SR OS 13.0.R10 Software Release Notes 11


Release 13.0.R10 Supported Hardware

Table 6. SFM, CPM, IOM, IMM, and ISM Cards Supported in 7450 ESS in Non-
Mixed Mode (Continued)

ESS-6/6v

ESS-12
ESS-7
Alcatel-Lucent
Part # Description
3HE06798CA 7750 1-port 40GE DWDM Tunable IMM – L2HQ ✓ ✓ ✓
3HE07158AA 7x50 12-port 10GE FP3 SFP+ IMM – L3HQ ✓ ✓
3HE07158BA 7x50 12-port 10GE FP3 SFP+ IMM – L3BQ ✓ ✓
3HE07158CA 7x50 12-port 10GE FP3 SFP+ IMM – L2HQ ✓ ✓
3HE07159AA 7x50 1-port 100GE FP3 CFP IMM – L3HQ ✓ ✓
3HE07159BA 7x50 1-port 100GE FP3 CFP IMM – L3BQ ✓ ✓
3HE07159CA 7x50 1-port 100GE FP3 CFP IMM – L2HQ ✓ ✓
3HE07303AA 7x50 2-port 100GE FP3 CFP IMM – L3HQ ✓ ✓
3HE07303BA 7x50 2-port 100GE FP3 CFP IMM – L3BQ ✓ ✓
3HE07303CA 7x50 2-port 100GE FP3 CFP IMM – L2HQ ✓ ✓
3HE07304AA 7x50 6-port 40GE FP3 QSFP IMM – L3HQ ✓ ✓
3HE07304BA 7x50 6-port 40GE FP3 QSFP IMM – L3BQ ✓ ✓
3HE07304CA 7x50 6-port 40GE FP3 QSFP IMM – L2HQ ✓ ✓
3HE07305AA 7x50 20-port 10GE FP3 SFP+ IMM – L3HQ ✓ ✓
3HE07305BA 7x50 20-port 10GE FP3 SFP+ IMM – L3BQ ✓ ✓
3HE07305CA 7x50 20-port 10GE FP3 SFP+ IMM – L2HQ ✓ ✓
3HE08019AA 7x50 1-port 100GE DWDM Tunable FP3 IMM – L3HQ ✓ ✓
3HE08019BA 7x50 1-port 100GE DWDM Tunable FP3 IMM – L3BQ ✓ ✓
3HE08019CA 7x50 1-port 100GE DWDM Tunable FP3 IMM – L2HQ ✓ ✓
3HE08020AA 7x50 1-port 100GE CFP + 10-port 10GE SFP+ FP3 IMM –
✓ ✓
L3HQ
3HE08020BA 7x50 1-port 100GE CFP + 10-port 10GE SFP+ FP3 IMM –
✓ ✓
L3BQ
3HE08020CA 7x50 1-port 100GE CFP + 10-port 10GE SFP+ FP3 IMM –
✓ ✓
L2HQ
3HE08174AA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM –
✓ ✓
L3HQ
3HE08174BA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM –
✓ ✓
L3BQ
3HE08174CA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM –
✓ ✓
L2HQ
3HE08175AA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM –
✓ ✓
L3HQ
3HE08175BA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM –
✓ ✓
L3BQ
3HE08175CA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM –
✓ ✓
L2HQ

12 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 6. SFM, CPM, IOM, IMM, and ISM Cards Supported in 7450 ESS in Non-
Mixed Mode (Continued)

ESS-6/6v

ESS-12
ESS-7
Alcatel-Lucent
Part # Description
3HE08426AA 7750 SR IOM3-XP-C ✓ ✓ ✓
3HE08427AA 7450 ESS IOM3-XP-C ✓ ✓ ✓
3HE08430AA 7450 ESS SFM5-12 ✓
3HE08431AA 7450 ESS SFM5-7 ✓
3HE08432AA 7450 ESS CPM5 ✓ ✓
3HE09117AA 7x50 Multiservice ISM ✓ ✓
3HE09118AA 7x50 Multiservice ISM-E (no encryption) ✓ ✓
3HE09192AA 7x50 MS-ISA2 + 1-port 100GE CFP IMM – L3HQ ✓ ✓
3HE09192BA 7x50 MS-ISA2 + 1-port 100GE CFP IMM – L3BQ ✓ ✓
3HE09192CA 7x50 MS-ISA2 + 1-port 100GE CFP IMM – L2HQ ✓ ✓
3HE09193AA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM – L3HQ ✓ ✓
3HE09193BA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM – L3BQ ✓ ✓
3HE09193CA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM – L2HQ ✓ ✓
3HE09253AA 7x50 MS-ISA2-E + 1-port 100GE CFP IMM – L3HQ ✓ ✓
3HE09253BA 7x50 MS-ISA2-E + 1-port 100GE CFP IMM – L3BQ ✓ ✓
3HE09253CA 7x50 MS-ISA2-E + 1-port 100GE CFP IMM – L2HQ ✓ ✓
3HE09254AA 7x50 MS-ISA2-E + 10-port 10G SFP+ IMM – L3HQ ✓ ✓
3HE09254BA 7x50 MS-ISA2-E + 10-port 10G SFP+ IMM – L3BQ ✓ ✓
3HE09254CA 7x50 MS-ISA2-E + 10-port 10G SFP+ IMM – L2HQ ✓ ✓
3HE09262AA 7450 ESS SFM5-12 + CPM5 ✓
3HE09263AA 7450 ESS SFM5-7 + CPM5 ✓
3HE09279AA 7x50 48-port GE Multicore SFP IMM – L3HQ ✓ ✓ ✓
3HE09279BA 7x50 48-port GE Multicore SFP IMM – L3BQ ✓ ✓ ✓
3HE09279CA 7x50 48-port GE Multicore SFP IMM – L2HQ ✓ ✓ ✓
3HE09648AA IOM – 7750 SR IOM4-e L3HQ 1 ✓ ✓
3HE09648BA IOM – 7750 SR IOM4-e L3BQ1 ✓ ✓
3HE09648CA IOM – 7750 SR IOM4-e L2HQ1 ✓ ✓
3HE10014AA IMM – 160-port GE cSFP/80-port GE SFP – L3HQ 1 ✓ ✓
3HE10014BA IMM – 160-port GE cSFP/80-port GE SFP – L3BQ1 ✓ ✓
3HE10014CA IMM – 160-port GE cSFP/80-port GE SFP – L2HQ1 ✓ ✓

1. Supported with SFM3/4/5.

Table 7 summarizes the IOMs, IMMs, and ISMs supported in SR OS Release 13.0.R10 for the
7450 ESS in mixed mode.

SR OS 13.0.R10 Software Release Notes 13


Release 13.0.R10 Supported Hardware

Table 7. IOM, IMM, and ISM Cards Supported in the 7450 ESS in Mixed Mode

Alcatel-Lucent
Part # Description
3HE06318AA 7750 Multicore-CPU IOM3-XP-B
3HE03619AA 7750 SR IOM3-XP (iom3-xp)
3HE03622AA 7750 SR 4-port 10GE XFP IOM (IMM)
3HE03623AA 7750 SR 8-port 10GE XFP IOM (IMM)
3HE03624AA 7750 SR 48-port GE SFP IOM (IMM)
3HE03625AA 7750 SR 48-port GE copper/TX IOM (IMM)
3HE04741AA 7750 SR 5-port 10GE XFP IOM (IMM)
3HE04743AAAB 7750 SR 12-port 10G Ethernet SFP+ IMM
3HE05053AAAB 7750 SR 1-port 100G Ethernet CFP IMM
3HE05055AA 7750 SR 1-port OC-768c/STM-256c OTU3 Long Reach DWDM Tunable
IMM
3HE05553AA 7x50 12-port 10G Ethernet SFP+ IMM – L2HQ
3HE05553BA 7x50 12-port 10G Ethernet SFP+ IMM – L3BQ
3HE05813AA 7x50 1-port OC-768c/STM-256c OTU3 Long Reach DWDM Tunable IMM
– L2HQ
3HE05813BA 7x50 1-port OC-768c/STM-256c OTU3 Long Reach DWDM Tunable IMM
– L3BQ
3HE05814AA 7x50 1-port 100G Ethernet CFP IMM – L2HQ
3HE05814BA 7x50 1-port 100G Ethernet CFP IMM – L3BQ
3HE05895AA 7x50 48-port GE SFP IOM (IMM) – L2HQ
3HE05895BA 7x50 48-port GE SFP IOM (IMM) – L3BQ
3HE05896AA 7x50 48-port GE copper/TX IOM (IMM) – L2HQ
3HE05896BA 7x50 48-port GE copper/TX IOM (IMM) – L3BQ
3HE05898AA 7x50 5-port 10GE XFP IOM (IMM) – L2HQ
3HE05898BA 7x50 5-port 10GE XFP IOM (IMM) – L3BQ
3HE05899AA 7x50 8-port 10GE XFP IOM (IMM) – L2HQ
3HE05899BA 7x50 8-port 10GE XFP IOM (IMM) – L3BQ
3HE06318AA 7750 Multicore-CPU IOM3-XP-B
3HE06320AA 7x50 3-port 40GE QSFP IMM- L3HQ
3HE06326AA 7x50 48-port GE Multicore-CPU SFP IMM – L3HQ
3HE06326BA 7x50 48-port GE Multicore-CPU SFP IMM – L3BQ
3HE06326CA 7x50 48-port GE Multicore-CPU SFP IMM – L2HQ
3HE06428AA 7x50 48-port GE SFP IOM (IMM) – L3HQ
3HE06429AA 7x50 48-port GE copper/TX IOM (IMM) – L3HQ
3HE06430AA 7x50 5-port 10GE XFP IOM (IMM) – L3HQ
3HE06431AA 7x50 8-port 10GE XFP IOM (IMM) – L3HQ

14 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 7. IOM, IMM, and ISM Cards Supported in the 7450 ESS in Mixed Mode

Alcatel-Lucent
Part # Description
3HE06721AA 7x50 3-port 40GE QSFP IMM – L2HQ
3HE06721BA 7x50 3-port 40GE QSFP IMM – L3BQ
3HE06798AA 7750 1-port 40GE DWDM Tunable IMM – L3HQ
3HE06798BA 7750 1-port 40GE DWDM Tunable IMM – L3BQ
3HE06798CA 7750 1-port 40GE DWDM Tunable IMM – L2HQ
3HE07158AA 7x50 12-port 10GE FP3 SFP+ IMM – L3HQ
3HE07158BA 7x50 12-port 10GE FP3 SFP+ IMM – L3BQ
3HE07158CA 7x50 12-port 10GE FP3 SFP+ IMM – L2HQ
3HE07159AA 7x50 1-port 100GE FP3 CFP IMM – L3HQ
3HE07159BA 7x50 1-port 100GE FP3 CFP IMM – L3BQ
3HE07159CA 7x50 1-port 100GE FP3 CFP IMM – L2HQ
3HE07303AA 7x50 2-port 100GE FP3 CFP IMM – L3HQ
3HE07303BA 7x50 2-port 100GE FP3 CFP IMM – L3BQ
3HE07303CA 7x50 2-port 100GE FP3 CFP IMM – L2HQ
3HE07304AA 7x50 6-port 40GE FP3 QSFP IMM – L3HQ
3HE07304BA 7x50 6-port 40GE FP3 QSFP IMM – L3BQ
3HE07304CA 7x50 6-port 40GE FP3 QSFP IMM – L2HQ
3HE07305AA 7x50 20-port 10GE FP3 SFP+ IMM – L3HQ
3HE07305BA 7x50 20-port 10GE FP3 SFP+ IMM – L3BQ
3HE07305CA 7x50 20-port 10GE FP3 SFP+ IMM – L2HQ
3HE08019AA 7x50 1-port 100GE DWDM Tunable FP3 IMM – L3HQ
3HE08019BA 7x50 1-port 100GE DWDM Tunable FP3 IMM – L3BQ
3HE08019CA 7x50 1-port 100GE DWDM Tunable FP3 IMM – L2HQ
3HE08020AA 7x50 1-port 100GE CFP + 10-port 10GE SFP+ FP3 IMM – L3HQ
3HE08020BA 7x50 1-port 100GE CFP + 10-port 10GE SFP+ FP3 IMM – L3BQ
3HE08020CA 7x50 1-port 100GE CFP + 10-port 10GE SFP+ FP3 IMM – L2HQ
3HE08174AA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM – L3HQ
3HE08174BA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM – L3BQ
3HE08174CA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM – L2HQ
3HE08175AA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM – L3HQ
3HE08175BA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM – L3BQ
3HE08175CA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM – L2HQ
3HE08426AA 7750 SR IOM3-XP-C
3HE09117AA 7x50 Multiservice ISM1
3HE09192AA 7x50 MS-ISA2 + 1-port 100GE CFP IMM – L3HQ1
3HE09192BA 7x50 MS-ISA2 + 1-port 100GE CFP IMM – L3BQ1

SR OS 13.0.R10 Software Release Notes 15


Release 13.0.R10 Supported Hardware

Table 7. IOM, IMM, and ISM Cards Supported in the 7450 ESS in Mixed Mode

Alcatel-Lucent
Part # Description
3HE09192CA 7x50 MS-ISA2 + 1-port 100GE CFP IMM – L2HQ1
3HE09193AA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM – L3HQ1
3HE09193BA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM – L3BQ1
3HE09193CA 7x50 MS-ISA2 + 10-port 10GE SFP+ IMM – L2HQ1
3HE09279AA 7x50 48-port GE Multicore SFP IMM – L3HQ
3HE09279BA 7x50 48-port GE Multicore SFP IMM – L3BQ
3HE09279CA 7x50 48-port GE Multicore SFP IMM – L2HQ
3HE09648AA IOM – 7750 SR IOM4-e L3HQ2
3HE09648BA IOM – 7750 SR IOM4-e L3BQ2
3HE09648CA IOM – 7750 SR IOM4-e L2HQ2
3HE10014AA IMM – 160-port GE cSFP/80-port GE SFP – L3HQ2
3HE10014BA IMM – 160-port GE cSFP/80-port GE SFP – L3BQ2
3HE10014CA IMM – 160-port GE cSFP/80-port GE SFP – L2HQ2
1. MS-ISM and MS-ISA2 applications using MS-ISA2s are not supported in mixed mode with the
exception of Application Assurance, IPsec, and NAT. IPsec is not supported with MS-ISM-E
and MS-ISA2-E.
2. Supported with SFM3/4/5.

Supported Adapters (XMA, MDA, ISA, CMA, VSM)


The following tables summarize the XRS Media Adapters (XMAs), Media Dependent Adapters
(MDAs), Integrated Service Adapters (ISAs), Compact Media Adapters (CMAs), and Versatile
Services Modules (VSMs) supported in Release 13.0.R10.

Table 8. XMAs and C-XMAs Supported in 7950 XRS

Alcatel-Lucent
Part # Description
3HE06937AA C-XMA – 7950 XRS 20-port 10GE SFP+ – IP Core
3HE06938AA C-XMA – 7950 XRS 2-port 100GE CFP – IP Core
3HE06937BA C-XMA – 7950 XRS 20-port 10GE SFP+ – LSR
3HE06938BA C-XMA – 7950 XRS 2-port 100GE CFP – LSR
3HE07297AA XMA – 7950 XRS 40-port 10GE SFP+ – IP Core
3HE07297BA XMA – 7950 XRS 40-port 10GE SFP+ – LSR
3HE07299AA XMA – 7950 XRS 4-port 100GE CXP – IP Core
3HE07299BA XMA – 7950 XRS 4-port 100GE CXP – LSR

16 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 8. XMAs and C-XMAs Supported in 7950 XRS (Continued)

Alcatel-Lucent
Part # Description
3HE08214AA C-XMA – 7950 XRS 6-port 40GE QSFP+ – IP Core
3HE08214BA C-XMA – 7950 XRS 6-port 40GE QSFP+ – LSR
3HE08631AA C-XMA – 7950 XRS 72-port GE CSFP – IP Core
3HE08631BA C-XMA – 7950 XRS 72-port GE CSFP – LSR
3HE08632AA XMA – 7950 XRS 4-port 100G CFP2 – IP Core
3HE08632BA XMA – 7950 XRS 4-port 100G CFP2 – LSR

Table 9. MDAs, CMAs, and ISAs Supported in 7750 SR

SR-1e/2e/3e (iom-e)

SR-a4/a8 (iom-a)
iom3-xp/-b/-c

iom4-e and
iom-20g-b
SR-c4/c12

iom2-20g
Alcatel-Lucent
Part # Description
3HE00021AA 60-port 10/100TX MDA – mini-RJ21 ✓ ✓ ✓ ✓
3HE00023AA 20-port 100FX MDA – SFP ✓ ✓ ✓ ✓
3HE00025AA 5-port GigE MDA – SFP ✓ ✓
3HE00026AA 10-port GigE MDA – SFP ✓ ✓
3HE00030AA 1-port 10GBASE-LW/LR MDA with optics – ✓ ✓ ✓
Simplex SC
3HE00031AA 1-port 10GBASE-EW/ER MDA with optics – ✓ ✓ ✓
Simplex SC
3HE00032AA 8-port OC-3c/STM-1c MDA – SFP ✓ ✓ ✓ ✓
3HE00033AA 16-port OC-3c/STM-1c MDA – SFP ✓ ✓ ✓
3HE00037AA 8-port OC-12c/STM-4c MDA – SFP ✓ ✓ ✓
3HE00038AA 16-port OC-12c/STM-4c MDA – SFP ✓ ✓ ✓
3HE00043AA 2-port OC-48c/STM-16c MDA – SFP ✓ ✓ ✓ ✓
3HE00044AA 4-port OC-48c/STM-16c MDA – SFP ✓ ✓ ✓
3HE00048AA 1-port OC-192c/STM-64c MDA with SR-1/I- ✓ ✓ ✓
64.1 optic – Simplex SC
3HE00049AA 1-port OC-192c/STM-64c MDA with IR-2/S- ✓ ✓ ✓
64.2 optic – Simplex SC
3HE00071AA 4-port ATM OC-12c/STM-4c MDA – SFP ✓ ✓ ✓ ✓
3HE00074AA 16-port ATM OC-3c/STM-1c MDA – SFP ✓ ✓ ✓
3HE00101AB 20-port 10/100/1000TX MDA – RJ45 ✓ ✓ ✓
3HE00707AA 2-port 10GBASE MDA – XFP ✓ ✓ ✓

SR OS 13.0.R10 Software Release Notes 17


Release 13.0.R10 Supported Hardware

Table 9. MDAs, CMAs, and ISAs Supported in 7750 SR (Continued)

SR-1e/2e/3e (iom-e)

SR-a4/a8 (iom-a)
iom3-xp/-b/-c

iom4-e and
iom-20g-b
SR-c4/c12

iom2-20g
Alcatel-Lucent
Part # Description
3HE00708AA 20-port GigE MDA – SFP ✓ ✓ ✓
3HE00709AA 1-port OC-192c/STM-64c MDA with LR-2/L- ✓ ✓ ✓
64.2 optic – Simplex SC
3HE00710AA 1-port 10GBASE-ZW/ZR MDA with optics – ✓ ✓ ✓
Simplex SC
3HE00714AA 1-port 10GBASE MDA – XFP ✓ ✓ ✓
3HE01020AA 8-port Channelized DS1/E1 CMA – RJ48c ✓
3HE01021AA 4-port DS3/E3 CMA – 1.0/2.3 ✓
3HE01022AA 8-port 10/100TX Ethernet CMA – RJ45 ✓
3HE01023AA 1-port GigE CMA – SFP ✓
3HE01197AA 7750 SR Versatile Services Module (VSM) ✓ ✓ ✓
3HE01364AA 4-port Channelized OC-3/STM-1 (DS0) ASAP ✓ ✓ ✓
MDA – SFP
3HE01615AA 5-port GigE MDA – SFP Rev B ✓ ✓ ✓
3HE01616AA 10-port GigE MDA – SFP Rev B ✓ ✓ ✓
3HE02021AA 1-port 10GBASE + 10-port GIGE MDA ✓ ✓ ✓
3HE02185AA 2-port OC-3c/STM-1c/OC-12c/STM-4c CMA ✓
– SFP
3HE02499AA 1-port Channelized OC-12/STM-4 ASAP ✓ ✓ ✓
MDA
3HE02500AA 12-port Channelized DS3/E3 ASAP MDA ✓ ✓ ✓
3HE02501AA 4-port Channelized DS3/E3 ASAP MDA ✓ ✓ ✓
3HE03077AA 1-port Channelized OC-3/STM-1 CES CMA ✓
3HE03078AA 1-port Channelized OC-3/STM-1 CES MDA ✓ ✓
3HE03079AA 7750 SR 4-port CH OC3-1/STM-1 CES SFP ✓ ✓ ✓
MDA
3HE03609AA 1-port GE CMA-XP SFP ✓
3HE03610AA 5-port GE CMA-XP SFP ✓
3HE03611AA 7750 SR 10-port GE – XP – SFP MDA ✓ ✓ ✓ ✓
3HE03612AA 7750 SR 20-port GE – XP – SFP MDA ✓ ✓ ✓ ✓
3HE03613AA 7750 SR 20-port GE – XP – Copper/TX MDA ✓ ✓ ✓ ✓
3HE03685AA 7750 SR 2-port 10GBASE – XP – XFP MDA ✓ ✓ ✓ ✓
3HE03686AA 7750 SR 4-port 10GBASE – XP – XFP MDA ✓ ✓ ✓
3HE04179AA 7750 SR 10GBASE Tunable ZW/R MDA ✓ ✓ ✓

18 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 9. MDAs, CMAs, and ISAs Supported in 7750 SR (Continued)

SR-1e/2e/3e (iom-e)

SR-a4/a8 (iom-a)
iom3-xp/-b/-c

iom4-e and
iom-20g-b
SR-c4/c12

iom2-20g
Alcatel-Lucent
Part # Description
3HE04272AA 7750 SR 1-port OC-12/STM-4 CES MDA ✓ ✓ ✓
3HE04274AA 7750 SR 1-port 10GBASE – XP – XFP MDA ✓ ✓ ✓ ✓
3HE04922AA 7750 SR / 7450 ESS Multiservice ISA1 ✓ ✓ ✓ ✓
3HE05142AA 7750 SR / 7450 ESS Multiservice ISA-E (no ✓ ✓ ✓ ✓
encryption)1
3HE05160AA 7750 SR 48-port 10/100/1000 – XP MDA – ✓
mini-RJ21
3HE05942AA 7750 SR / 7450 ESS Versatile Services Module ✓ ✓ ✓
XP (VSM-CCA-XP)
3HE05943AA 7750 SR 16-port OC-3/12c STM-1/4c POS ✓ ✓ ✓ ✓
MDA – SFP Rev B
3HE05944AA 7750 SR 16-port ATM OC-3c/STM-1c MDA – ✓ ✓ ✓
SFP Rev B
3HE05945AA 7750 SR 4-port ATM OC-12c/STM-4c MDA – ✓ ✓ ✓ ✓
SFP Rev B
3HE05946AA 7750 SR 4-port OC-48c/STM-16c POS MDA ✓ ✓ ✓ ✓
– SFP Rev B
3HE05947AA 7750 SR 2-port OC-192/STM-64 – XP – XFP ✓ ✓ ✓
MDA
3HE06432AA 7750 SR 10-port GE SFP HS-MDAv2 ✓
3HE06433AA 7750 SR 1-port 10GE HS-MDAv2 ✓
3HE06521AA 2-port OC-3c/STM-1c/OC-12c/STM-4c CMA ✓
– SFP Rev B
3HE07282AA 7750 SR 2-port 10GE XFP + 12-port GE SFP – ✓
XP MDA
3HE07284AA 7750 SR 12-port GigE – XP – SFP MDA ✓ ✓ ✓
3HE08220AA 8-port Channelized DS1/E1 CMA Rev B ✓
3HE09203AA 7750 SR-a 1-port 100GE MDA-a XP – CFP ✓
3HE09204AA 7750 SR-a 10-port 10GE MDA-a XP – SFP+ ✓
3HE09205AA 7750 SR-a 2-port 10GE SFP+ + 12-port GE ✓
SFP MDA-a
3HE09206AA 7750 SR-a 20-port 10/100/1000 TX MDA-a – ✓
RJ45
3HE09207AA 7750 SR-a 22-port GE SFP/44-port GE ✓
MDA-a – CSFP
3HE09240AA 7750 SR-a 4-port 10GE MDA-a – SFP+ ✓

SR OS 13.0.R10 Software Release Notes 19


Release 13.0.R10 Supported Hardware

Table 9. MDAs, CMAs, and ISAs Supported in 7750 SR (Continued)

SR-1e/2e/3e (iom-e)

SR-a4/a8 (iom-a)
iom3-xp/-b/-c

iom4-e and
iom-20g-b
SR-c4/c12

iom2-20g
Alcatel-Lucent
Part # Description
3HE09241AA 7750 SR-a 6-port 10GE SFP+ + 1-port 40GE ✓
QSFP+ MDA-a XP
3HE09649AA MDA-e 10-port 10 GE SFP+ ✓
3HE09881AA MDA-e 1-port 100 GE CFP2 ✓
3HE10421AA MDA–a XP - 7750 SR 1-PT 100G CFP2 ✓
3HE10422AA MDA–a XP - 7750 SR 1-PT 100G CFP4 ✓
3HE10427AA ISA - 7750 SR ISA2-MS1 ✓
3HE10428AA ISA - 7750 SR ISA2-MS-E1 ✓
3HE10429AA MDA-e 6-port 10GE SFP+ ✓

1. See Usage Notes for specifics.

Table 10. MDAs, ISAs, and VSMs Supported in 7450 ESS in Non-Mixed Mode

iom3-xp/-b/-c
iom-20g-b

iom4-e
Alcatel-Lucent
Part # Description
3HE00021AA 7750 SR 60-port 10/100TX MDA – mini-RJ211 ✓
3HE00023AA 7750 SR 20-port 100FX MDA – SFP1 ✓
3HE00030AA 7750 SR 1-port 10GBASE-LW/LR MDA with optics – Simplex ✓
SC1
3HE00031AA 7750 SR 1-port 10GBASE-EW/ER MDA with optics – Sim- ✓
plex SC1
3HE00033AA 7750 SR 16-port OC-3c/STM-1c MDA – SFP1 ✓
3HE00037AA 7750 SR 8-port OC-12c/STM-4c MDA – SFP1 ✓
3HE00038AA 7750 SR 16-port OC-12c/STM-4c MDA – SFP1 ✓
3HE00043AA 7750 SR 2-port OC-48c/STM-16c MDA – SFP1 ✓
3HE00044AA 7750 SR 4-port OC-48c/STM-16c MDA – SFP1 ✓
3HE00048AA 7750 SR 1-port OC-192c/STM-64c MDA with SR-1/I-64.1 ✓
optic – Simplex SC1

20 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 10. MDAs, ISAs, and VSMs Supported in 7450 ESS in Non-Mixed Mode

iom3-xp/-b/-c
iom-20g-b

iom4-e
Alcatel-Lucent
Part # Description
3HE00049AA 7750 SR 1-port OC-192c/STM-64c MDA with IR-2/S-64.2 ✓
optic – Simplex SC1
3HE00101AB 7750 SR 20-port 10/100/1000TX MDA – RJ451 ✓
3HE00230AA 60-port 10/100TX MDA – mini-RJ21 ✓ ✓
3HE00231AA 20-port 100FX MDA – SFP ✓ ✓
3HE00232AA 10-port GigE MDA – SFP ✓
3HE00233AA 20-port GigE MDA – SFP ✓ ✓
3HE00234AB 20-port 10/100/1000TX MDA – RJ45 ✓ ✓
3HE00235AA 1-port 10GBASE-LW/LR MDA with optics – Simplex SC ✓ ✓
3HE00236AA 1-port 10GBASE-EW/ER MDA with optics – Simplex SC ✓ ✓
3HE00237AA 16-port OC-3c/STM-1c MDA – SFP ✓ ✓
3HE00238AA 8-port OC-12c/STM-4c MDA – SFP ✓ ✓
3HE00239AA 2-port OC-48c/STM-16c MDA – SFP ✓ ✓
3HE00243AA 16-port OC-12c/STM-4c MDA – SFP ✓ ✓
3HE00244AA 4-port OC-48c/STM-16c MDA – SFP ✓ ✓
3HE00317AA 2-port 10GBASE MDA – XFP ✓ ✓
3HE00707AA 7750 SR 2-port 10GBASE MDA – XFP1 ✓
3HE00708AA 7750 SR 20-port GigE MDA – SFP1 ✓
3HE00709AA 7750 SR 1-port OC-192c/STM-64c MDA with LR-2/L-64.2 ✓
optic – Simplex SC1
3HE00710AA 7750 SR 1-port 10GBASE-ZW/ZR MDA with optics – ✓
Simplex SC1
3HE00714AA 7750 SR 1-port 10GBASE MDA – XFP1 ✓
3HE01173AA 1-port 10GBASE-ZW/ZR MDA with optics – Simplex SC ✓ ✓
3HE01197AA 7750 SR Versatile Services Module (VSM)1 ✓
3HE01198AA 7450 ESS Versatile Services Module (VSM) ✓ ✓
3HE01532AA 10-port GigE MDA – SFP Rev B ✓ ✓
3HE01616AA 7750 SR 10-port GigE MDA – SFP Rev B1 ✓
3HE01617AA 1-port 10GBASE MDA – XFP ✓ ✓
3HE02021AA 7750 SR 1-port 10GBASE + 10-port GIGE MDA1 ✓
3HE02022AA 7450 ESS 1-port 10GBASE+10-port GigE MDA ✓ ✓
3HE03611AA 7750 SR 10-port GE – XP – SFP MDA1 ✓
3HE03612AA 7750 SR 20-port GE – XP – SFP MDA1 ✓

SR OS 13.0.R10 Software Release Notes 21


Release 13.0.R10 Supported Hardware

Table 10. MDAs, ISAs, and VSMs Supported in 7450 ESS in Non-Mixed Mode

iom3-xp/-b/-c
iom-20g-b

iom4-e
Alcatel-Lucent
Part # Description
3HE03613AA 7750 SR 20-port GE – XP – Copper/TX MDA1 ✓
3HE03614AA 7450 ESS 10-port GE – XP – SFP MDA ✓ ✓
3HE03615AA 7450 ESS 20-port GE – XP – SFP MDA ✓ ✓
3HE03616AA 7450 ESS 20-port GE – XP – Copper/TX MDA ✓ ✓
3HE03685AA 7750 SR 2-port 10GBASE – XP – XFP MDA 1 ✓
3HE03686AA 7750 SR 4-port 10GBASE – XP – XFP MDA1 ✓
3HE03687AA 7450 ESS 2-port 10GBASE – XP – XFP MDA ✓ ✓
3HE03688AA 7450 ESS 4-port 10GBASE – XP – XFP MDA ✓ ✓
3HE04179AA 7750 SR 10GBASE Tunable ZW/R MDA 1 ✓
3HE04181AA 7450 ESS 10GBASE Tunable ZW/R MDA ✓ ✓
3HE04273AA 7450 1-port 10GBASE – XP – XFP MDA ✓ ✓
3HE04274AA 7750 SR 1-port 10GBASE – XP – XFP MDA 1 ✓
3HE04922AA 7750 SR / 7450 ESS Multiservice ISA2 ✓ ✓
3HE05142AA 7750 SR / 7450 ESS Multiservice ISA-E (no encryption)2 ✓ ✓
3HE05159AA 7450 SR 48-port 10/100/1000 – XP MDA – mini-RJ21 ✓
3HE05160AA 7750 SR 48-port 10/100/1000 – XP MDA – mini-RJ211 ✓
3HE05942AA 7750 SR / 7450 ESS Versatile Services Module XP (VSM- ✓ ✓
CCA-XP)
3HE05943AA 7750 SR 16-port OC-3/12c STM-1/4c POS MDA – SFP Rev B1 ✓
3HE05946AA 7750 SR 4-port OC-48c/STM-16c POS MDA – SFP Rev B1 ✓
3HE06382AA 7450 ESS 16-port OC-3/12c STM-1/4c POS MDA – SFP Rev ✓ ✓
B
3HE06383AA 7450 ESS 4-port OC-48c/STM-16c POS MDA – SFP Rev B ✓ ✓
3HE06432AA 7750 SR 10-port GE SFP HS-MDAv21 ✓
3HE06434AA 7450 ESS 10-port GE SFP HS-MDAv2 ✓
3HE06435AA 7450 ESS 1-port 10GE HS-MDAv2 ✓
3HE07282AA 7750 SR 2-port 10GE XFP + 12-port GE SFP –XP MDA1 ✓
3HE07283AA 7450 ESS 2-port 10GE XFP + 12-port GE SFP –XP MDA ✓
3HE07284AA 7750 SR 12-port GigE – XP – SFP MDA1 ✓
3HE07285AA 7450 ESS 12-port GigE – XP – SFP MDA ✓ ✓
3HE09649AA MDA-e 10-port 10 GE SFP+ ✓
3HE09881AA MDA-e 1-port 100 GE CFP2 ✓
3HE10427AA ISA – 7750 SR ISA2-MS ✓

22 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

Table 10. MDAs, ISAs, and VSMs Supported in 7450 ESS in Non-Mixed Mode

iom3-xp/-b/-c
iom-20g-b

iom4-e
Alcatel-Lucent
Part # Description
3HE10428AA ISA – 7750 SR ISA2-MS-E ✓
3HE10429AA MDA-e 6-port 10GE SFP+ ✓
1. Supported only with 7750 SR IOM3-XP in the 7450 ESS chassis.
2. See Usage Notes for specifics.

The following table summarizes the MDAs, ISAs, and VSMs supported in SR OS Release
13.0.R10 for the 7450 ESS in mixed mode. 7750 SR MDAs must be configured in the 7750 SR
IOM3-XP or 7750 SR IOM4-e for mixed mode functionality. .

Table 11. MDAs, ISAs, and VSMs Supported in the 7450 ESS in Mixed Mode

Alcatel-Lucent
Part # Description
3HE00021AA 60-port 10/100TX MDA – mini-RJ21
3HE00023AA 20-port 100FX MDA – SFP
3HE00030AA 1-port 10GBASE-LW/LR MDA with optics – Simplex SC
3HE00031AA 1-port 10GBASE-EW/ER MDA with optics – Simplex SC
3HE00032AA 8-port OC-3c/STM-1c MDA – SFP
3HE00033AA 16-port OC-3c/STM-1c MDA – SFP
3HE00037AA 8-port OC-12c/STM-4c MDA – SFP
3HE00038AA 16-port OC-12c/STM-4c MDA – SFP
3HE00043AA 2-port OC-48c/STM-16c MDA – SFP
3HE00044AA 4-port OC-48c/STM-16c MDA – SFP
3HE00048AA 1-port OC-192c/STM-64c MDA with SR-1/I-64.1 optic – Simplex SC
3HE00049AA 1-port OC-192c/STM-64c MDA with IR-2/S-64.2 optic – Simplex SC
3HE00071AA 4-port ATM OC-12c/STM-4c MDA – SFP
3HE00074AA 16-port ATM OC-3c/STM-1c MDA – SFP
3HE00101AB 20-port 10/100/1000TX MDA – RJ45
3HE00707AA 2-port 10GBASE MDA – XFP
3HE00708AA 20-port GigE MDA – SFP
3HE00709AA 1-port OC-192c/STM-64c MDA with LR-2/L-64.2 optic – Simplex SC
3HE00710AA 1-port 10GBASE-ZW/ZR MDA with optics – Simplex SC
3HE00714AA 1-port 10GBASE MDA – XFP
3HE01197AA 7750 SR Versatile Services Module (VSM)
3HE01364AA 4-port Channelized OC-3/STM-1 (DS0) ASAP MDA – SFP
3HE01616AA 10-port GigE MDA – SFP Rev B

SR OS 13.0.R10 Software Release Notes 23


Release 13.0.R10 Supported Hardware

Table 11. MDAs, ISAs, and VSMs Supported in the 7450 ESS in Mixed Mode

Alcatel-Lucent
Part # Description
3HE02021AA 1-port 10GBASE + 10-port GIGE MDA
3HE02499AA 1-port Channelized OC-12/STM-4 ASAP MDA
3HE02500AA 12-port Channelized DS3/E3 ASAP MDA
3HE02501AA 4-port Channelized DS3/E3 ASAP MDA
3HE03078AA 1-port Channelized OC-3/STM-1 CES MDA
3HE03079AA 7750 SR 4-port CH OC3-1/STM-1 CES SFP MDA
3HE03611AA 7750 SR 10-port GE – XP – SFP MDA
3HE03612AA 7750 SR 20-port GE – XP – SFP MDA
3HE03613AA 7750 SR 20-port GE – XP – Copper/TX MDA
3HE03685AA 7750 SR 2-port 10GBASE – XP – XFP MDA
3HE03686AA 7750 SR 4-port 10GBASE – XP – XFP MDA
3HE04179AA 7750 SR 10GBASE Tunable ZW/R MDA
3HE04272AA 7750 SR 1-port OC-12/STM-4 CES MDA
3HE04274AA 7750 SR 1-port 10GBASE – XP – XFP MDA
3HE04922AA 7750 SR / 7450 ESS Multiservice ISA1,2
3HE05142AA 7750 SR 7450 ESS Multiservice ISA-E (no encryption)1
3HE05160AA 7750 SR 48-port 10/100/1000 – XP MDA – mini-RJ21
3HE05942AA 7750 SR / 7450 ESS Versatile Services Module XP (VSM-CCA-XP)
3HE05943AA 7750 SR 16-port OC-3/12c STM-1/4c POS MDA – SFP Rev B
3HE05944AA 7750 SR 16-port ATM OC-3c/STM-1c MDA-SFP Rev B
3HE05945AA 7750 SR 4-port ATM OC-12c/STM-4c MDA – SFP Rev B
3HE05946AA 7750 SR 4-port OC-48c/STM-16c POS MDA – SFP Rev B
3HE05947AA 7750 SR 2-port OC-192/STM-64 –XP –XFP MDA
3HE06432AA 7750 SR 10-port GE SFP HS-MDAv2
3HE06433AA 7750 SR 1-port 10GE HS-MDAv2
3HE07282AA 7750 SR 2-port 10GE XFP + 12-port GE SFP –XP MDA
3HE07284AA 7750 SR 12-port GigE – XP – SFP MDA
3HE09649AA MDA-e 10-port 10GE SFP+
3HE09881AA MDA-e 1-port 100GE CFP2
3HE10427AA ISA – 7750 SR ISA2-MS
3HE10428AA ISA – 7750 SR ISA2-MS-E
3HE10429AA MDA-e 6-port 10GE SFP+
1. MS-ISAs and ISA applications using MS-ISAs are not supported in mixed mode with the
exception of Application Assurance, IPsec, NAT and FCC/RET. IPsec is not supported with
MS-ISA-E.
2. Starting with Release 8.0.R5, MS-ISA cards (3HE04922AA) replace IPsec-ISA cards
(3HE03080AA).

24 SR OS 13.0.R10 Software Release Notes


Release 13.0.R10 Supported Hardware

SR OS 13.0.R10 Software Release Notes 25


New Features

New Features
The following sections describe the new features added in SR OS releases.

Release 13.0.R10
Release 13.0.R10 has no new major features. See also Enhancements in Release 13.0.R10 and
Resolved Issues in Release 13.0.R10.

Features Added in • The following table summarizes the features that were added in releases prior to Release
Prior Releases 13.0.R10, but which were not documented in the SR OS Release Notes until Release
13.0.R10. Refer to the New Features section of the applicable release for details.

Table 15. Features Added Earlier than Release 13.0.R10

Component New Feature Release


HW/Platform MS-ISA2/MS-ISA2-E on SR-1e/2e/3e 13.0.R9

Release 13.0.R9

HW/Platform

MS-ISA2/ In Release 13.0.R9, the Multi-Service Integrated Service Adapter (MS-ISA2), introduced in
MS-ISA2-E on Release 13.0.R7 for IOM4-e, is now also supported on 7750 SR-1e/2e/3e platforms.
SR-1e/2e/3e

7750 SR-1e/2e/3e Release 13.0.R9 introduces the 7750 SR-e family of routers; the Alcatel-Lucent 7750 SR-e
platform series enables the delivery of advanced residential, business and mobile services. The
7750 SR-e series provides high-performance networking for cloud, data center and branch
office applications.
As a member of the Alcatel-Lucent 7750 SR product portfolio, the 7750 SR-e platform employs
the 7750 SR hardware architecture and the SR OS. The 7750 SR-e is FP3-based, which is
programmable to allow the 7750 SR-e to adapt to new features and protocols.
The 7750 SR-e platform supports a wide range of SR OS features, including a variety of services
and protocols, OAM capabilities, and QoS features, all of which are managed by the
Alcatel-Lucent 5620 Service Aware Manager (SAM).
The 7750 SR-e is available in three hardware configurations:

26 SR OS 13.0.R10 Software Release Notes


New Features

• 7750 SR-1e chassis, which supports:


− a total system capacity of 200 Gb/s (full duplex), 6RU
− up to two (2) CPM-e (1+1 redundancy) cards, one (1) IOM-e card and four (4)
MDA-e cards
− up to four (4) AC or DC Power-Supply Units (PSUs) (universal AC and –48 VDC are
available)
• 7750 SR-2e chassis, which supports:
− a total system capacity of 400 Gb/s (full duplex), 10RU
− up to two (2) CPM-e (1+1 redundancy) cards, two (2) IOM-e cards and eight (8)
MDA-e cards
− up to four (4) AC or DC PSUs (universal AC and –48 VDC are available)
• 7750 SR-3e chassis, which supports:
− a total system capacity of 600 Gb/s (full duplex), 13RU
− up to two (2) CPM-e (1+1 redundancy) cards, three (3) IOM-e cards and twelve (12)
MDA-e cards
− up to four (4) AC or DC PSUs (universal AC and –48 VDC are available)
All three configurations have full system redundancy with common components that are
modular and hot-swappable to provide increased system uptime and future upgradeability.
CPM-e, CCM-e, IOM-e, MDA-e cards, and PSUs are designed for use in all three 7750 SR-e
chassis. MDA-e cards are also compatible with 7750 SR and 7450 ESS IOM4-e.

Control The 7750 SR-e CPM-e provides intelligent control and processing functionality. The CPM-e
Processing offers optional 1+1 redundancy and is hot-swappable. Redundant CPM-e’s operate in a hitless,
Module (CPM-e) stateful, failover mode.

Chassis Control The 7750 SR-e CCM-e provides an interface to the CPM-e and is hot-swappable. The CCM-e
Module (CCM-e) provides one-to-one relationship with its associated CPM-e. For timing and synchronization,
each CCM-e has an RJ45 BITS port and a 1PPS port. The CCM-e supports a 10/100BASE
(RJ45) management interface, RJ45 serial console port (DCE/DTE switch) and an RJ45 OES
port.

Input/Output The 7750 SR-e IOM-e provides up to 200 Gb/s (full duplex) connectivity to MDA-e and
Module (IOM-e) MS-ISA2(-E) modules. Optimized for versatility in Ethernet and IP-based services and
applications, each IOM-e uses a multicore CPU and supports up to four (4) MDA-e and MS-
ISA2(-E) modules. Based on FP3, the IOM-e provides the forwarding and service functions
along with high-end traffic management capabilities.

Media Dependent The MDA-e, usable in both IOM4-e for 7750 SR and 7450 ESS, and 7750 SR-e IOM-e,
Adapter (MDA-e) supports up to 100 Gb/s (full duplex) and provide physical Ethernet interface connectivity. They
are available in a variety of Ethernet-speed and port-density configurations.

SR OS 13.0.R10 Software Release Notes 27


New Features

Release 13.0.R8

HW/Platform

IEEE 1588 IEEE 1588 port-based timestamping capability has been added to the 1G ports (p20-1gb-sfp) of
Port-Based the assemblies in Table 12. To unlock this capability on the ports of these IMMs, the firmware
Timestamping must be upgraded. If SR OS has been upgraded via ISSU, then the firmware may not have been
upgraded automatically. In these cases, the operator must perform a hard reset of the IMM using
the clear card command to upgrade the firmware.
The firmware version can be checked in the detailed show information of the assembly (for
example, show mda 1/1 detail).

Table 12. Additional Hardware Assemblies with 1G Port IEEE 1588 Port-Based
Timestamping Capability
Alcatel-Lucent Part # Description
3HE08174AA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM - L3HQ
3HE08174BA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM - L3BQ
3HE08174CA 7x50 10-port 10GE SFP+ + 20-port GE SFP FP3 IMM - L2HQ
3HE08175AA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM - L3HQ
3HE08175BA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM - L3BQ
3HE08175CA 7x50 3-port 40GE QSFP + 20-port GE SFP FP3 IMM - L2HQ

Release 13.0.R7

HW/Platform

7950 XRS-40 30m Release 13.0.R7 introduces the 30-meter-long interconnect cable support for the 7950 XRS-40
chassis inter- system.
connect cable
support

System Alarm Release 13.0.R7 adds the software support for the input alarm pins on the Alarms Interface Port
Contact Inputs for of the CPM on the 7750 SR-a platform. The alarm inputs allow the operator to monitor and
7750 SR-a report changes in the external environmental conditions. In a remote or outdoor deployment,
alarm inputs typically allow an operator to detect door open/close, air conditioner fault, etc.
There are four (4) separate input pins, each of which can be configured with an associated
severity and normally-open/normally-closed state. There is also a single output power pin that
can be used to supply power for the alarm inputs. When an input pin changes state, the router
can generate log events and raise facility alarms.

28 SR OS 13.0.R10 Software Release Notes


New Features

1-port 100G CFP2 Release 13.0.R7 introduces two new MDA-a XP cards utilized within the 7750 SR-a4/a8
MDA-a XP and platforms:
1-port 100G CFP4 • 1-port 100G CFP2
MDA-a XP
• 1-port 100G CFP4
These cards support Alcatel-Lucent-sourced 100GBase CFP2 and CFP4 optic modules (not
included).

MS-ISA2/ Release 13.0.R7 introduces the Multi-Service Integrated Service Adapter (MS-ISA2) for the
MS-ISA2-E 7750 SR IOM4-e (also supported on 7450 ESS). MS-ISA2-E has been created for exporting to
encryption-restricted countries.
The MS-ISA2-E application support is the same as the MS-ISA2 except for IPsec and IP
Tunnels, similar to the MS-ISM and MS-ISA2 IMMs, the export restricted variants (-E).
To run any of these applications, the hardware and appropriate software RTU licenses must be
purchased.

Release 13.0.R6

HW/Platform

APEQ-DC-2200- In Release 13.0.R6, a new DC 60A/80A software-configurable Advanced Power Equalizer


2800 Power (APEQ) module is supported on 7750 SR-12e and 7950 XRS systems.
Equalizer Module

APEQ-AC-3000 AC In Release 13.0.R6, AC power is supported on 7750 SR-12e and 7950 XRS systems using the
Power Equalizer new single phase AC APEQ module.
Module

6x10GE SFP+ Release 13.0.R6 introduces a new 6-port 10GE SFP+ MDA-e utilized on the IOM4-e. The
MDA-e for IOM4-e 6-port 10GE SFP+ MDA-e supports:
• FEC/G.709
• LAN/WAN, OTN framing OTU1e, OTU2, and OTU2e at line rate for use in a wide range
of optical transport networking (OTN) environments
• ITU-T Synchronous Ethernet (SyncE)

SR OS 13.0.R10 Software Release Notes 29


New Features

IEEE 1588 IEEE 1588 Port-Based Timestamping has been introduced on a new hardware assembly as
Port-Based shown below. For this assembly, no firmware upgrade is required to unlock this feature.
Timestamping on
Additional MDA Table 13. Additional Hardware with IEEE 1588 Port-Based Timestamping Capability

Alcatel-Lucent Part # Description


3HE10429AA 6-port 10GE SFP+ MDA-e

Dual frequency The 7750 SR-a4 permits the assignment of two line reference inputs to the central clock to be
reference on from its single IOM. In normal operating mode, this permits redundant frequency references to
7750 SR-a4 both CPMs.

Routing

Selective FIB Release 13.0.R6 introduces the support for IP FIB selective route install. When this feature is
enabled on an SR OS router, every line card in the chassis decides, for every downloaded IP
route, whether or not it should program the route into its forwarding table. A route is
programmed only if it is relevant to the line card based on the configuration of interfaces and
services. For example, with selective FIB enabled, an IP route belonging to VPRN service A is
not installed on a line card with only access interfaces belonging to VPRN service B. With
careful planning, the use of selective FIB allows the effective FIB capacity of the system to
exceed the FIB limit of the line card with the smallest capacity. Selective FIB requires the
system to have CPM3 or higher.

MPLS

Class-Based Release 13.0.R6 extends the scope of applicability of Class-Based Forwarding. LDP prefixes
Forwarding that are resolved to a set of ECMP tunnel next-hops (IGP shortcuts) can now have forwarding-
class specified packets sent to LSPs configured with the matching forwarding class.

Services

PBF: Nuage Release 13.0.R6 introduces the support for integrated Nuage and SR OS router service chaining
Service Chaining solution for VPLS using IPv4/MAC ESI PBF for EVPN on all SR OS FlexPath-based
for VPLS using platforms. To achieve the steering:
IPv4/MAC Filter • An operator must configure a PBF match/action filter policy entry in an IPv4 or MAC
ESI PBF for EVPN ingress access or network filter deployed on a VPLS interface. The PBF target identifies
the first service function in the chain (Ethernet Segment Identifier (ESI) which defines
where the appliance is connected) and the VPLS service for the egress EVPN VXLAN
interface.

30 SR OS 13.0.R10 Software Release Notes


New Features

• An operator must configure a BGP peering session between the router and the data center
controller. The session is used to convey to the router the MP-BGP EVPN route required to
reach the service chain (Ethernet Auto-Discovery (A-D) route for the specified ESI
identifier). The BGP control plane together with the ESI PBR configuration are used to
forward the matching packets to the next-hop in the EVPN-VXLAN data center chain
(through resolution to a VXLAN Network Identifier and VXLAN Termination Endpoint).
If the BGP control plane information is not available, the packets matching the ESI PBF
entry will be, by default, forwarded using regular forwarding. Optionally, an operator can
select to drop the packets when the ESI PBF target is not reachable. See Known
Limitations for more information.

Subscriber
Management

NAT: Active-Active The “active-active” MS-ISA/MS-ISA2 redundancy model is now supported for Layer 2-Aware
MS-ISA/ NAT, previously only supported for NAT on DS-Lite, LSN and NAT64. When all ISAs are
MS-ISA2 active and up to two ISAs fail, traffic will then be distributed over the remaining active ISAs.
Redundancy [210472]
Model

Release 13.0.R5

Hardware

IMM - 160-port GE Release 13.0.R5 introduces the 160-port GE cSFP/80-port GE SFP MultiCore-CPU-based
cSFP/80-port GE IMMs to the Alcatel-Lucent IMM family. These IMMs are based on the FP3 chipset. Providing
SFP 160G of bandwidth, these IMMs:
• are supported in the 7750 SR-7/12 and 7450 ESS-7/12 with SFM3/4/5 and above, and in
the 7750 SR-12e with SFM4/5 and above
• provide 128K queues flexibly configurable to any/all ports for ingress and/or egress
• can co-exist and are interoperable with all released IOMs/IMM/ISMs (must use a chassis
mode that aligns with the earliest generation of IOMs installed in the chassis)
• support chassis mode D when a chassis is configured entirely with any combination of
IOM3-XP/IMM/ISMs
• support 200 GB for full line rate on the 7750 SR-12e with SFM4 and SFM5 and on the
7750 SR-7/12 with SFM5 and the switch fabric speed set to fabric-speed-b
• support Alcatel-Lucent-sourced GE cSFP/SFP optic modules (not included)
• require an upgrade to PEM-3 and to the latest Enhanced Fan Tray for power and cooling
requirements
• support Soft Reset

SR OS 13.0.R10 Software Release Notes 31


New Features

There are Right-to-Use (RTU) licenses associated with IMM hardware depending on the
features used. Contact your Alcatel-Lucent representative for the appropriate application
licenses.
IMPORTANT NOTE: Impedance panels must be purchased and installed in all systems in
which an IMM is used. These impedance panels provide highly efficient air flow in support of
the higher performing IOM3 and newer IOM/IMM/ISM modules. Note that even when only one
IMM/IOM/ISM is deployed, impedance panels are required.

IEEE 1588 Support The 7750 SR-a4/a8 platforms now support IEEE 1588 for distribution of frequency and time.
on 7750 SR-a4/a8 The support includes all of the features available on other platforms supporting IEEE 1588
including
• Ordinary-Master, Ordinary-Slave, and Boundary clocks
• default, G.8265.1, and G.8275.1 profiles
• Unicast IPv4 and Multicast Ethernet transport

Port-Based IEEE 1588 Port-Based Timestamping has been introduced on hardware assemblies of the 7750
Timestamping on SR-a4/a8 as shown below. The support is available on the 1GE and 10GE ports only and is not
7750 SR-a4/a8 available on 40GE or on Electrical Ethernet ports in 10 Mbps mode.
MDAs
Table 14. 7750 SR-a4/a8 with IEEE 1588 Port-Based Timestamping Capability
Alcatel-Lucent Part # Description
3HE09201AA 7750 SR-a CPM
3HE09202AA 7750 SR-a IOM - L3HQ
3HE09202BA 7750 SR-a IOM - L3BQ
3HE09202CA 7750 SR-a IOM - L2HQ
3HE09204AA 7750 SR-a 10-port 10GE SFP+ MDA-a XP
3HE09205AA 7750 SR-a 2-port 10GE SFP+ + 12-port GE SFP MDA-a
3HE09206AA 7750 SR-a 20-port 10/100/1000 TX MDA-a
3HE09207AA 7750 SR-a 44-port GE cSFP/22-port GE SFP MDA-a
3HE09240AA 7750 SR-a 4-port 10GE SFP+ MDA-a
3HE09241AA 7750 SR-a 6-port 10GE SFP+ + 1-port 40GE QSFP+ MDA-a
XP

1588 Port-Based IEEE 1588 Port-Based Timestamping has been introduced on a new hardware assembly as
Timestamping on shown below. For this assembly, no firmware upgrade is required to unlock this feature.
Additional MDA
Table 15. Additional Hardware with IEEE 1588 Port-Based Timestamping Capability

Alcatel-Lucent Part # Description


3HE09649AA MDA-e 10-port 10 GE SFP+

32 SR OS 13.0.R10 Software Release Notes


New Features

System

In-service ISSU (in-service software update) across minor releases (Minor ISSU) allows in-service
Software Update software updates across maintenance releases (within the same major release) for systems with
(ISSU) Across dual CPMs or CFMs without requiring a reboot of the system. ISSU is comparable to
Minor Releases performing a controlled High-Availability switchover where the new image is loaded onto the
standby CPM or CFM which becomes master, and then upgrading the image on the other CPM
or CFM. Minor ISSU does not apply to 7750 SR-c4. The terms Major ISSU and Minor ISSU
are used to differentiate between ISSU across major releases and maintenance releases within a
major release respectively.

Routing

General Support In Release 13.0.R5, the BGP implementation in SR OS introduces broad support for dynamic
for Dynamic BGP BGP sessions. Previously, dynamic sessions were only supported for ESM subscribers. When
Sessions BGP in the base router or a VPRN is configured to support dynamic sessions, it accepts
incoming BGP connection attempts from source IP addresses that matches specified prefixes;
BGP connection establishment no longer requires a source IP to match a statically-configured
neighbor address. The parameters that apply to a dynamic session are inherited from the BGP
group with the longest matching prefix for the source IP address. The implementation allows
configurable limits on the maximum number of established dynamic sessions per instance
and/or per group. See Enhancements in Release 13.0.R6 for more information.

Subscriber
Management

ESM BGP Prior to Release 13.0.R5, dynamic BGP peering was only supported for ESM hosts. Release
13.0.R5 adds dynamic BGP peering support for non-ESM hosts. To avoid any confusion
between the two, ESM-based dynamic BGP peering has been changed to esm-dynamic-
peering, and consequently, the dynamic-peering parameter has been deprecated. See Changed
or Deprecated Commands for more information.

Release 13.0.R4
The following sections describe the new features added in Release 13.0.R4 of SR OS.
− Hardware
− System
− Quality of Service
− Routing
− MPLS

SR OS 13.0.R10 Software Release Notes 33


New Features

− Services
− Subscriber Management
− Application Assurance
− OAM

Hardware

7750 SR-7/12 and Release 13.0.R4 introduces 200 Gb/s per slot support in the 7750 SR-7/12 and the 7450 ESS-
7450 ESS-7/12 7/12 with SFM5. To achieve this level of throughput, the chassis will require all T3-based
200 Gb/s per Slot IOMs/IMMs. A new tools command is introduced to set the switch fabric speed to fabric-
with SFM5 speed-b which will enable 200 Gb/s per slot after rebooting the system. If Major ISSU is used
to upgrade to Release 13.0.R4 or later, then the system will not automatically change to the
faster fabric speed (the tools command and reboot will be necessary after the ISSU for the faster
performance to be in effect).

IOM4-e Release 13.0.R4 introduces the new IOM4-e (Input/Output Module) for the 7450 ESS-7/12 and
7750 SR-7/12/12e platforms. Each IOM4-e MultiCore-CPU line card accepts up to two (2)
MDA-e cards.
The IOM4-e uses the FP3 chipset, providing the following key benefits:
• supports up to 200 Gb/s (full duplex) in the 7750 SR-7/12 and 7450 ESS-7/12 with SFM5
and in the 7750 SR-12e with SFM4 and SFM5. To achieve this level of throughput on the
7750 SR-7/12 and 7450 ESS-7/12 platforms, the chassis will require all T3-based
IOMs/IMMs and the switch fabric speed set to fabric-speed-b.
• supports 100 Gb/s throughput with SF/CPM4 on the 7750 SR-7/12 and 7450 ESS-7/12
platforms.
• maximum of 128k queues in total for ingress and egress directions, which can be flexibly
assigned to any port
• full range of edge services with deterministic performance
• Soft Reset support
There are Right-to-Use (RTU) licenses associated with IOM4-e hardware depending on the
features used. Contact your Alcatel-Lucent representative for the appropriate application
licenses.
IMPORTANT NOTE: Impedance panels must be purchased and installed in all systems in
which a line card is used. These impedance panels provide highly efficient air flow in support
of the higher performing IOM3-XP/-B/-C, IOM4-e and newer IMM/ISM modules. Note that
even when only one IMM/IOM/ISM is deployed, impedance panels are required. See Limited
Support Features and Enhancements for more information.

10-port 10GE SFP+ Release 13.0.R4 introduces a new family of MDA-e cards utilized on the IOM4-e. There are
MDA-e and 1-port two variants of MDA-e, both supporting FEC/G.709:
100GE CFP2 • 10-port 10GE SFP+
MDA-e

34 SR OS 13.0.R10 Software Release Notes


New Features

− supports LAN/WAN, OTN framing OTU1e, OTU2, and OTU2e at line rate for use in
a wide range of optical transport networking (OTN) environments
− supports ITU-T Synchronous Ethernet (SyncE)
• 1-port 100GE CFP2
− supports 100GE Ethernet and OTN OTU4 framing

System

Enhanced CLI Authorization based on locally-configured profiles has been enhanced to allow more granular
Authorization access control to CLI branches and objects. Release 13.0.R4 supports the matching of
parameters and optional parameters in CLI commands, allowing an operator to permit or deny
different users from accessing objects such as service or policy instances (for example, system
interface in comparison to all other interfaces, or VPRN 5 in comparison to VPRN 6).
SR OS also now allows the operator to give users read-only access to sub-branches of the router
configuration.
Note that some special characters are not usable in the match criteria. Notably, they are:
• characters “<”, “>”
• double quotes “” inside the match string. For example: match “configure router interface
“if name with space”” will not correctly match if an operator tries to enter the context for
that particular interface.

Hierarchical CLI The concept of CLI session management has been introduced to control or limit the number of
Session Limits CLI sessions opened by one user. The sessions are limited using a two-level hierarchy via
profiles and a new concept called a cli-session-group. CLI session groups can be used to create
different Telnet or SSH session limits for different groups of users. Log events indicate when
the user is attempting to exceed the limit.

IEEE 1588 IEEE 1588 Port-Based Timestamping has been introduced on new hardware assemblies as
Port-Based shown below. To unlock this capability on ports of these MDAs, the firmware must be
Timestamping on upgraded. If SR OS has been upgraded via ISSU, then the firmware may not have been
Additional MDAs upgraded automatically. In these cases, the operator must hard reset the IMM or MDA using the
clear card or clear mda commands to upgrade the firmware.
Note: The firmware version can be checked in the detailed show information of the assembly
(for example, show mda 1/1 detail).

Table 16. Additional Hardware with IEEE 1588 Port-Based Timestamping Capability

Alcatel-Lucent Part # Description


3HE07282AA 7750 SR 2-port 10GE XFP + 12-port GE SFP -XP MDA
3HE07283AA 7450 ESS 2-port 10GE XFP + 12-port GE SFP-XP MDA
3HE07284AA 7750 SR 12-port GigE - XP - SFP MDA
3HE07285AA 7450 ESS 12-port GigE - XP - SFP MDA

SR OS 13.0.R10 Software Release Notes 35


New Features

IEEE 1588 Support The IEEE 1588 functionality has been enhanced with the addition of support for the ITU-T
for ITU-T G.8275.1 G.8275.1 profile. This profile specifies how to use IEEE 1588 to distribute a time reference to
meet the requirements of mobile base-stations.

Filter Policies: TTL Release 13.0.R4 introduces TTL match support in IPv4 ingress filter policies for the drop action.
Match Support in Greater-than, less-than, equal to, and range operators are supported with the TTL condition. A
IPv4 Filters packet matching an IPv4 ingress filter policy entry with a conditional TTL drop action
configured is discarded when the TTL value in the IPv4 header matches the condition
configured. If the TTL condition is not met, the packet is forwarded. When the filter entry with
conditional action is used as a mirror source, only packets matching the entry’s match criteria
and the TTL condition are mirrored. When the entry is used in Cflowd, packets are processed
for Cflowd based on the entry’s match criteria, whether or not the TTL action condition is met.
TTL condition is supported on FP2- and higher-based line cards on all platforms. Filter policies
with conditional TTL action are not supported in egress directions and on FP1 line cards.
Deploying a filter policy with TTL conditional action in those scenarios may lead to an
unexpected behavior (for example, packets matching an entry are always dropped) and thus
should be avoided.

Filter Release 13.0.R4 allows operators to configure sticky destination selection in IPv4 and IPv6
Policies/PBR: redirect policies (config>filter>redirect-policy>sticky-dest). Upon start-up, or when the first
Redirect policy redirect-policy destination becomes available, a delay timer is started (configurable). When the
Sticky Destination timer expires, a best destination from all available destinations is selected and programmed as
Selection an active, sticky destination.
The currently active, sticky destination remains active until one of the following occurs:
• the destination goes down
• an operator forces the switch manually (tools>perform>filter>redirect-policy>activate-
best-dest).

PBR: ESM Release 13.0.R4 introduces the support for egress PBR on Layer-3 (L3) IES/VPRN subscriber-
Downstream facing interfaces for subscriber-destined downstream traffic. An operator can control traffic
Traffic Steering steering per ESM subscribers/hosts with an IP flow-level granularity using IPv4 ACL filter
Using Egress IPv4 policies. Upstream traffic is steered using ingress subscriber/host-assigned IPv4 ACLs with
ACLs with PBR ingress PBR rules (existing functionality); downstream traffic is steered using egress
Action subscribers/host-assigned IPv4 ACLs with egress PBR rules (new in Release 13.0.R4). Because
steering is based on ACLs assigned to hosts/subscribers, operators no longer need to use other
techniques to identify subscriber traffic to be redirected to Value Added Services (VAS)—for
example, IP address pools or DSCP remark per ESM service type.
Any egress-supported ACL match condition is supported in egress PBR steering, allowing full
flexibility of selecting not only which subscribers or hosts have to be redirected but also what
flows for those subscribers or hosts are to be redirected. Supported egress PBR actions include:
• action forward esi sf-ip vas-interface router (Nuage integrated service-chaining support)
• action forward redirect-policy (IP-based service-chaining/steering including)
To ensure that downstream traffic is not steered again after VAS processing, the traffic must
return over a dedicated L3 interface configured to indicate post-VAS downstream traffic on
ingress (refer to the vas-if-type command in the user guides for more information).

36 SR OS 13.0.R10 Software Release Notes


New Features

The feature is supported with integrated Application Assurance (AA) for platforms that support
AA. If deployed with AA, both upstream and downstream traffic are subject to AA before
steering to VAS. Configuring egress-PBR as part of ACLs deployed in the context other than
ESM subscriber/host is not blocked but not recommended.

PBR: Nuage Release 13.0.R4 introduces the support for integrated Nuage and SR OS router service chaining
Service Chaining solution for IES/VPRN using IPv4 ESI PBR for EVPN on all SR OS FlexPath-based hardware
for IES/VPRN platforms. To achieve the steering, an operator must configure the following items:
using IPv4 Filter • a PBR match/action filter policy entry in an IPv4 ingress access or network filter deployed
ESI PBR for EVPN on an IES/VPRN interface. The PBR target identifies the first service function in the chain
(the Ethernet Segment Identifier (ESI), which identifies where the appliance is connected,
and the IPv4 address of the appliance) and the EVPN VXLAN egress interface on the PE
(the routing instance and interface name).
• the BGP peering session between the router and the data center controller—The session is
used to convey to the router MP-BGP EVPN routes (route type 1 and 2) required to reach
the service chain. The BGP control plane, together with the ESI PBR configuration, are
used to forward the matching packets to the next-hop in the EVPN-VXLAN data center
chain (through resolution to a VXLAN Network Identifier and VXLAN Termination
Endpoint). If the BGP control plane information is not available, the packets matching the
ESI PBR entry will be, by default, forwarded using regular routing. Optionally, an operator
can select to drop the packets when the ESI PBR target is not reachable using the pbr-
down-action-override command.

LAG • Release 13.0.R4 introduces the following enhancements to mixed-speed member port LAG
support:
− support for a mix of 10GE/40GE/100GE ports in a single LAG
− support for access and hybrid modes
− support for MC-LAG and LAG with multiple sub-groups
− support for service hash, per-link-hash, and LAG link map profiles
− support for MCAC, VRRP, ETH-CFM, micro-BFD
− support for configurable Tier-0 scheduler
See Enhancements in Release 13.0.R7 for more information about Mixed-Speed LAG with
ESM.

LAG/ECMP Hashing distribution has been optimized for link aggregation groups with more than 16 links
Hashing and for ECMP with more than 16 paths.
Optimization

TEID-based Release 12.0 introduced TEID-based hashing for IP interfaces. Release 13.0.R4 enhances this
Hashing for functionality by adding the support for GTP-U- and GTP-C-encapsulated traffic on Layer-2
Layer-2 VPLS VPLS services. This functionality allows a deployed SR OS router (for example, in an LTE
Interfaces mobile backhaul network) to use a TEID value from a GTP v1/v2 packet header in hash inputs
in addition to Layer-3/4 IP input for a better traffic distribution across multiple ECMP

SR OS 13.0.R10 Software Release Notes 37


New Features

paths/LAG links. TEID-based hashing can be enabled per service (VPLS). The hashing
configuration applies to traffic ingressing the system on an FP2- or higher-based line card and
egressing the system over LAG/ECMP.

Inner IP Release 13.0.R4 introduces the ability to use inner IPv4/v6 header inputs for hashing of IPv4
Header-based and IPv6 unicast and multicast traffic encapsulated in an IPv4 tunnel (such as GRE) for traffic
Hashing for IPv4 distribution over LAG links/ECMP. By enabling the inner IP header hash for IPv4 tunnels, the
Tunneled Traffic system replaces outer IP inputs (for example, GRE tunnel IP) with those of inner IP (user data)
in the hash. Inner IP-based IPv4 tunneled traffic hashing can be enabled per interface. The
hashing configuration will apply to traffic ingressing system on FP2- or higher-based line cards
and egressing the system over LAG/ECMP.

In-Service Major ISSU support has been added to the 7950 XRS-40 platform. The first Major ISSU path
Software Upgrade for a 7950 XRS-40 system is from Release 12.0.R6 to Release 13.0.R4.
(ISSU) Across
Major Releases for
7950 XRS-40

In-service Major ISSU (In-Service Software Update) allows in-service updates across a major release for
Software Update systems with dual-CPMs without requiring a reboot of the system. ISSU is comparable to
(ISSU) Across performing a controlled High-Availability switchover where the new image is loaded onto the
Major Releases standby CPM which becomes master, and then upgrading the image on the other CPM. Major
ISSU does not apply to 7750 SR-a4/a8/c4/c12. The first (earliest release) possible Major ISSU
upgrade path to Release 13.0 (R4 onwards only) is from Release 12.0.R4 for the 7450 ESS-7/12,
7750 SR-7/12/12e, from Release 12.0.R5 for the 7950 XRS-16c/20, and from Release 12.0.R6
for the 7950 XRS-40.

OOB Management A resilient out-of-band (OOB) management Ethernet redundancy mode has been added to
Ethernet Port SR OS. When the management Ethernet port is down on the active CPM, the active CPM can
Redundancy now use the management Ethernet port of the standby CPM for system management. OOB
management Ethernet port redundancy is enabled using the configure redundancy mgmt-
ethernet-redundancy command.

FIPS-140-2 Release 13.0.R4 introduces the support for FIPS-140-2 Level 1. FIPS (Federal Information
Processing Standards) from NIST (National Institute of Standards and Technology) is a
cryptographic certification standard that defines the requirements for products to become FIPS-
140-2 certified. The feature introduces a new FIPS-140-2 boot mode through a BOF
configuration command that instructs the software to boot up and operate in FIPS-140-2 mode.
When the node is running in FIPS-140-2 mode, it disables the use of cryptographic algorithms
that are not FIPS approved and ensures any FIPS approved algorithms are functioning properly.

38 SR OS 13.0.R10 Software Release Notes


New Features

Quality of
Service

Egress Port Congestion monitoring under Egress Port Scheduler (EPS) for Ethernet ports and Ethernet
Scheduler (EPS) Vports is now supported. It can be enabled for PIR rates under egress port scheduler, its levels,
Congestion and groups. Offered rates are constantly monitored and compared to the configured threshold.
Monitoring After the offered rate exceeds the monitoring threshold, the exceed counter is increased. The
operator can use operational commands (show and clear) to monitor the state of the exceed
counter and, from that, derive congestion patterns on EPS.

Prefix Lists for Support has been added to allow SAP ingress and egress QoS policies configured with IPv4
QoS Policies prefix lists for IP criteria matching statements to be applied to the ingress and egress of an SLA
profile. See Enhancements in Release 13.0.R6 for more information.

Routing

Route Policy Release 13.0.R4 supports more policy variables that can be expanded in sub-policy action items.
Variable Action Policy variables such as “@localcomm@” or “@peeras@” can be configured to provide smaller
Items and more efficient policies. The following action items support policy variables: aigp-metric,
as-path-prepend, local-preference, metric, next-hop, damping, origin, preference, tag, and
type. Release 12.0.R1 supports policy variables for as-path, community and prefix-list, and
Release 12.0.R4 adds policy variable support to as-path expression and as-path-group
expression.

OSPF and IS-IS Release 13.0.R4 adds a new method to identify and prioritize certain OSPF and IS-IS routes to
RIB Prioritization be updated in the protocol RIB (Route Information Base) ahead of other, lower-priority routes.
This is enabled through the use of the rib-priority command. This command allows specific
routes to be prioritized through the protocol processing so that updates are propagated to the
RIB (and eventually the FIB) as quickly as possible.
In IS-IS, the rib-priority command is configured within the global IS-IS routing context and
the administrator has the option to either specify a prefix-list or an IS-IS tag value. If a prefix
list is specified, then route prefixes matching any of the prefix list criteria will be considered
high-priority. If, instead, an IS-IS tag value is specified, then any IS-IS route with that tag value
will be considered high priority.
In OSPF, the rib-priority command is configured either within the global OSPF or OSPFv3
routing context or under a specific OSPF/OSPFv3 interface context. Under the global OSPF
context, a prefix list can be specified, which identifies which route prefixes should be
considered high priority. If the rib-priority high command is configured under an OSPF
interface context, then all routes resolved through that interface are considered high-priority.

SR OS 13.0.R10 Software Release Notes 39


New Features

The routes that have been designated as high-priority will be the first routes processed and then
passed to the FIB update process so that the forwarding engine can be updated. All known high-
priority routes should be processed before the routing protocol moves on to other standard-
priority routes. This feature will have the most impact when there are a large number of routes
being learned through the routing protocol.

IP MTU on Release 13.0.R4 adds a new command to the network interface (config>router>interface) and
Network and VPRN VPRN network interfaces (config>service>vprn>network-interface) to configure the IP
Network Interfaces maximum transmission unit (MTU) for the associated router IP interface. The command, ip-
mtu mtu-value is the same syntax as previously supported under Layer-3 VPN interfaces.
The configured IP-MTU cannot be larger then the calculated IP-MTU based on the port MTU
configuration.
The MTU that will be used is:
MINIMUM((Port_MTU - EtherHeaderSize), (Configured IP-MTU))
The no form of the command returns the associated IP interfaces MTU to its default value,
which is calculated based on the port MTU setting. (For Ethernet ports this will typically be
1554.)

ECMP Support for In Release 13.0.R4, IP ECMP support has been enhanced to allow up to 64 next-hops per route
64 Next-hops destination. This feature requires chassis mode D and is supported on FP2- and higher-based
line cards on all platforms. This enhancement does not apply to LDP which supports up to 32
ECMP paths.

Enhanced Route Route policies now support more options for matching and manipulating BGP FlowSpec routes.
Policy Support for A new generic extended community syntax allows FlowSpec actions, encoded as BGP extended
BGP FlowSpec communities, to be matched in policy entries and to be added, removed, or replaced by policy
Routes actions. In addition, new flow-spec-source and flow-spec-dest commands allow FlowSpec
routes to be matched on the basis of the IP prefix encoded in the type-1 or type-2 subcomponent
of the FlowSpec NLRI; the matching is applied against a prefix-list.

BGP FlowSpec IPv4 and IPv6 BGP FlowSpec now support an L4 port match encoded in a type-4 subcomponent
Support for L4 of the NLRI. This allows a packet to be matched if either its source TCP/UDP port or its
Port Matching destination TCP/UDP port equals a specific number or falls within one single contiguous range.
Prior to Release 13.0.R4, no filter entry was installed when the FlowSpec route contained a
type-4 port subcomponent.

BGP FlowSpec IPv6 BGP FlowSpec now supports matching IPv6 fragments as encoded in a type 12
Support for IPv6 subcomponent of the NLRI. The implementation complies with draft-ietf-idr-flow-spec-v6-06.
Fragment The following match options are supported: non-first only, first-only, fragment true and
Matching fragment false. Last fragment matching is not supported.

Conditional BGP Release 13.0.R4 introduces the concept of conditional route policy entries to support
Route conditional advertisement of BGP routes. Each conditional policy entry has an expression that
Advertisement tests for the existence or non-existence of certain active IPv4 or IPv6 routes in the route table.

40 SR OS 13.0.R10 Software Release Notes


New Features

If the expression evaluates to “true”, then the matching and action commands of the policy entry
are applied as normal. If the expression evaluates to “false”, then the entire policy entry is
skipped and processing continues with the next entry. Note that conditional expressions are only
parsed when the route policy is used as a BGP export policy or a VRF export policy. This feature
is supported in the base router and in VPRNs.

BGP Show Release 13.0.R4 introduces minor changes to various BGP-related show commands to improve
Command visibility and troubleshooting. The show router bgp routes command now uses specific flag
Enhancements values to identify routes that are currently considered “stale” (due to graceful restart) or subject
to “purge” (due to sending route-refresh messages). In addition, the show router bgp summary
command now includes a group filtering option that allows the output to be scoped to a single
configured group.

Segment Routing • The following enhancements have been added to the segment-routing feature:
− OSPF support
− multi-instance support for IS-IS and OSPF with the ability to create a segment-
routing tunnel to a destination prefix reachable in any IGP instance
− ability to create segment-routing tunnels to the same destination prefix in different
IGP instances and using a different SID index/label. This is supported for a
destination prefix reachable over multiple IS-IS instances or over an OSPF instance
and one or more IS-IS instances.
− segment-routing tunnel for IPv4 BGP shortcut and IPv4 BGP label route
− segment-routing tunnel for IPv4 and IPv6 VPRN prefix resolution in both inter-AS
options B and C

Label per Prefix When BGP advertises an IP-VPN route, it distributes an MPLS label with the route. Prior to
for IP-VPN Routes Release 13.0.R4, the MPLS label allocation used one of two methods: label-per-VRF or label-
per-next-hop. Now, a third label allocation mode is supported: label-per-prefix (LPP). Label-
per-prefix is used when a qualifying IP route is exported by a VRF export policy rule that has
the “advertise-label per-prefix” action. A qualifying route is any IPv4 or IPv6 route that is not
a local route, aggregate route, BGP-VPN route, or GRT-lookup static route. With LPP, every
prefix is associated with its own unique label value that does not change while the route is
present in the route table. When the PE receives a terminating MPLS packet with a per-prefix
label value, the packet is forwarded as if the FIB lookup found only the matching prefix route
and not any of the more-specific prefix routes that would normally be selected. LPP supports
ECMP, QPPB, and policy accounting as part of the egress forwarding decision. Note, however,
that it does not support BGP Fast Reroute or BGP sticky ECMP.

RT Constraint for Release 13.0.R4 extends BGP support for constrained VPN route distribution (RT constraint).
L2 VPN and MVPN In previous releases, received RTC routes from a peer had no filtering effect on Layer-2 VPN
Routes routes (BGP-AD, BGP-VPLS, BGP-VPWS) and MVPN-related routes (MVPN-IPv4, MVPN-
IPv6, MCAST-VPN-IPv4) sent to that peer. Now, these other route types are automatically
handled by the same logic that applies to VPN-IPv4, VPN-IPv6 and EVPN routes.

SR OS 13.0.R10 Software Release Notes 41


New Features

IPv4 Dynamic ARP The IP routing features are extended with a command that configures the maximum number of
Entry Limit dynamic IPv4 ARP entries that can be learned on an IP interface. When the number of dynamic
ARP entries reaches the configured percentage of this limit set with arp-limit, an SNMP trap is
sent.
When the limit is exceeded, no new entries are learned until an entry expires and traffic to these
destinations are dropped. Entries that have already been learned will be refreshed.

IPv6 Dynamic The IP routing features are extended with a command that configures the maximum number of
Neighbor Entry dynamic IPv6 neighbor entries that can be learned on an IP interface. When the number of
Limit dynamic neighbor entries reaches the configured percentage of this limit set with neighbor-
limit, an SNMP trap is sent. When the limit is exceeded, no new entries are learned until an
entry expires and traffic to these destinations are dropped. Entries that have already been learned
will be refreshed.

IPv6 Neighbor Release 13.0.R4 adds a configurable IPv6 Neighbor Discovery (ND) stale timer value that can
Discovery Stale be set globally or per interface with the stale-time CLI command. The stale timer defines how
Timer long an SR OS node will retain a Neighbor Cache Entry (NCE) that is in the stale state before
it is removed from the cache. The configurable values are 60-65536 seconds, with 14400
seconds being the default.

MPLS

GMPLS UNI Release 13.0.R4 adds the following new functionality to the GMPLS UNI:
• 1:N end-to-end protection of GMPLS LSPs (gLSPs)

BFD on LSPs • Bidirectional Forwarding Detection (BFD) is supported on RSVP LSPs, for both auto LSPs
and manually-configured LSPs. Chassis mode D is required on platforms that support
chassis modes.

Services

MVPN: (C-*,C-*) Release 13.0.R1 introduced the wildcard S-PMSI support for RFC 6513/RFC 6514-based
Wildcard S-PMSI MVPNs with IPv4 PIM in the C-instance and enhanced BSR support for wildcard S-PMSI.
Support for Release 13.0.R4 extends (C-*,C-*) wildcard S-PMSI support and enhanced BSR to support
MVPNs with IPv6 IPv6 PIM ASM/SSM in the C-instance.
PIM in C-instance

MVPN: Receiver- Release 13.0.R1 introduced a new trigger for S-PMSI instantiation: receiver-PE-driven S-PMSI
PE Threshold for instantiation for mLDP and RSVP-TE S-PMSIs in RFC 6513/6514-based MVPNs with IPv4
S-PMSI Trigger PIM in the C-instance. As of Release 13.0.R4, a receiver-PE threshold for the S-PMSI trigger
IPv6 Enhancement functionality is also fully supported with IPv6 PIM ASM/SSM in the C-instance. See Release
13.0.R1 for more information.

42 SR OS 13.0.R10 Software Release Notes


New Features

IPv4 PIM ASM Multicast extranet distribution allows multicast traffic to flow across routing instances. The
Mapping for extranet functionality was first introduced in SR OS Release 10.0 for RFC 6037 MVPN and
Multicast Extranet extended in SR OS Release 12.0.R4 to support extranet in RFC 6513/6514 ng-MVPNs, extranet
on Receiver PEs for GRT-source/VRF-receiver, and extranet per multicast group mapping on receiver PE for
RFC 6037 MVPN.
Release 13.0.R4 introduces the support for extranet with IPv4 PIM ASM in a receiver routing
instance in addition to IPv4 PIM SSM. IPv4 PIM ASM extranet is achieved through a local
mapping from the receiver to source routing instances on a receiver PE. The mapping allows
propagation of Anycast RP PIM Register messages between the source and receiver routing
instances. This PIM register propagation allows the receiver routing instance to resolve PIM
ASM joins to multicast sources and to propagate PIM SSM joins over an auto-created extranet
interface to the source routing instance. PIM SSM joins are then propagated towards the
multicast source within the source routing instance.
The following MVPN topologies are supported:
• extranet for RFC 6037 MVPN with MDT SAFI with a local replication on a source PE and
multiple-source/multiple-receiver replication on a receiver PE
• extranet for RFC 6513/6514 ng-MVPN (including RFC 6625 (C-*,C-*) wildcard S-PMSI)
with a local replication on a source PE and a multiple source/multiple receiver replication
on a receiver PE
• extranet for GRT-source/VRF receiver with a local replication on a source PE and a
multiple-receiver replication on a receiver PE
To achieve extranet replication, operator must configure:
• local PIM ASM mapping on a receiver PE from a receiver routing instance to a source
routing instance (config>service>vprn>mvpn>rpf-select>core-mvpn or
config>service>vprn>pim>grt-extranet as applicable)
• Anycast RP mesh between source and receiver PEs in the source routing instance
IMPORTANT NOTES:
• The multicast source must reside in the source routing instance the ASM map points to on a
receiver PE.
• A given multicast group can be mapped in a receiver routing instance using either PIM
SSM mapping or PIM ASM mapping, but not both.
• A given multicast group cannot map to multiple source routing instances.
• Chassis mode D is required on platforms that support chassis modes.

EVPN for MPLS in Release 13.0.R4 introduces the full support for RFC 7432 EVPN. Prior to Release 13.0.R4,
VPLS Services EVPN was only supported for VXLAN tunnels. Now, EVPN can be used in MPLS networks
where PEs are interconnected through any of the following tunnels: RSVP-TE, LDP, RFC 3107
BGP, segment-routing IS-IS or segment-routing OSPF. Similarly to VPRN services, the
selection of the tunnel to be used in a VPLS service (with bgp-evpn mpls enabled) is based on
the auto-bind-tunnel command.
This feature includes the support for:
• the advertisement of MAC/IP advertisement routes as well as Inclusive Multicast Ethernet
Tag routes (for Ingress Replication), according to RFC 7432

SR OS 13.0.R10 Software Release Notes 43


New Features

• the configuration of an evi per VPLS service, from which the route-target and route-
distinguisher for the service can be auto-derived; the evi will also be used in the multi-
homing service-carving function
• the control word on EVPN-MPLS packets—the use of the control word can be enabled or
disable on a per-service basis
• the use of force-vlan-vc-forwarding for the transparent transport of the customer 802.1p
bits over the EVPN network
• the integration of EVPN-MPLS destinations with VPLS SAPs and SDP-bindings by
associating them with the same user-configured split-horizon-group
• feature parity with EVPN-VXLAN services.
− MAC mobility, conditional static-MAC protection and MAC duplication detection
− proxy-ARP and proxy-ND
Chassis mode D is required on platforms that support chassis modes.

EVPN Release 13.0.R4 introduces the support for EVPN multi-homing in VPLS services as per
Multi-homing in RFC 7432, including single-active and all-active modes. EVPN multi-homing relies on a new
VPLS Services for logical structure called Ethernet Segment (ES) that is assigned a 10-byte identifier or Ethernet
MPLS Networks Segment Identifier (ESI) and characterizes the multi-homed connectivity between the Customer
Equipment (CE) and the EVPN network.
ES is now supported in Release 13.0.R4 with the following features:
• all-active mode support for CEs connected to the EVPN network through a LAG—This
includes the DF (Designated Forwarder) election, split-horizon and aliasing functions as
per RFC 7432. All-active ES can only be associated to access LAGs.
• single-active mode, including DF election and backup functions as per RFC 7432—Single-
active ES can be associated to ports, LAGs or SDPs.
• DF election-per-service based on the RFC 7432 service-carving function or manual
assignment of DF per service.
EVPN multi-homing is only supported in VPLS services where bgp-evpn mpls is enabled.
Chassis mode D is required on platforms that support chassis modes. See Enhancements in
Release 13.0.R6 for more information.

PBB-EVPN for PBB-EVPN is supported in Release 13.0.R4 according to draft-ietf-l2vpn-pbb-evpn-10. PBB-


I-VPLS and Epipe EVPN is built upon the existing SR OS PBB-VPLS constructs, thereby requiring enabling bgp-
Services evpn mpls in the b-vpls services. In addition to the support of all bgp-evpn mpls features in
the b-vpls services, this feature includes the support for:
• the advertisement of BMAC routes as well as Inclusive Multicast Ethernet Tag routes (for
Ingress Replication) according to draft-ietf-l2vpn-pbb-evpn-10
• the integration of EVPN-MPLS destinations with B-VPLS SAPs and SDP-bindings by
associating them to the same user-configured split-horizon-group
• per-ISID flooding containment in the b-vpls services based on the advertisement of the
local ISIDs and population of MFIBs with the received ISIDs. The configuration of isid-
policy to control the advertisement of the local ISIDs as well as the use of the default
multicast list (as opposed to the per-ISID MFIBs) is also supported.
Chassis mode D is required on platforms that support chassis modes.

44 SR OS 13.0.R10 Software Release Notes


New Features

PBB-EVPN Release 13.0.R4 introduces the support for PBB-EVPN multi-homing as per draft-ietf-l2vpn-
Multi-homing in pbb-evpn, including single-active and all-active modes. The following features are now
I-VPLS and Epipe supported:
Services • ethernet-segments associated with I-VPLS SAPs/SDP-bindings and PBB Epipe SAPs.
• use of shared BMACs or per-ES (Ethernet Segment) dedicated BMACs for the traffic
coming from an access ethernet-segment, as per the PBB-EVPN draft
• all-active mode support for CEs connected to the I-VPLS (or Epipe in some scenarios)
through a LAG. This includes the DF (Designated Forwarder) election as in EVPN multi-
homing, split-horizon based on source BMAC checks and aliasing functions as per the
draft. All-active ES can only be associated to access LAGs.
• single-active mode, including DF election and CMAC flush mechanisms defined in the
PBB-EVPN draft. Single-active ES can be associated to ports, LAGs and SDPs for I-VPLS
SAPs/SDP-bindings defined on those objects (Epipe SAPs are also possible in certain
scenarios).
PBB-EVPN multi-homing is only supported in I-VPLS/Epipe services linked to a b-vpls where
bgp-evpn mpls is enabled. Chassis mode D is required on platforms that support chassis modes.
See Enhancements in Release 13.0.R6 for more information.

XMPP Support on Release 13.0.R4 completes the integration of the SR OS routers into the Nuage VSD (Virtual
DC PE for Services Directory) architecture by introducing the Fully-Dynamic XMPP provisioning model
VPLS/VPRN (Fully- for VPRN or VPLS services.
Dynamic Model) Prior to Release 13.0.R4, only the Static-Dynamic model was supported, where the
VPLS/VPRN service itself, as well as most of the parameters, needed to be provisioned
statically through usual procedures (such as CLI and SNMP) and the VSD would dynamically
send the parameters required for the attachment of the VPLS/VPRN service to the L2/L3
domain in the Data Center.
In the Fully-Dynamic model, the entire VPLS/VPRN service configuration is dynamically
driven from VSD and no static configuration is required. Through the existing XMPP interface,
the VSD provides the SR OS routers with a handful of parameters that are translated into a
service configuration by a Python script. This Python script provides an intermediate
abstraction layer between VSD and the SR OS routers, translating the VSD data model into the
SR OS CLI data model.
A MultiCore-CPU CPM (CPM3 or higher) is required to enable XMPP Fully-Dynamic
services. Fully-Dynamic services are not persistent.

Routed-VPLS IPv4 IPv4 multicast routing support in a Routed-VPLS service has been extended to allow the
Multicast multicast sources to be located on the VPLS side of the service with receivers on the IP interface
side of the service.
When IGMP is configured on the IP interface, IGMP-snooping is supported in the VPLS.
This new functionality is not supported for Routed-VPLS services in which VXLAN is enabled.
Multicast VLAN Registration (MVR) functions or the configuration of a video interface are not
supported within the associated VPLS service. IPv4 multicast routing is not supported in Routed
I-VPLS. See Known Issues for more information.

SR OS 13.0.R10 Software Release Notes 45


New Features

IPv6 SPI Hashing Release 13.0.R4 introduces SPI hashing for IPv6 traffic over VPLS services for Layer-2 and
for ESP Encrypted Layer-3 VPLS interfaces. The functionality allows a deployed SR OS router (for example, in an
Traffic LTE mobile backhaul network) to use an SPI value from the ESP header of the encrypted tunnel
in hash inputs in addition to Layer-3/4 tunnel IP inputs for better traffic distribution across
multiple ECMP paths/LAG links. SPI hashing can be enabled per service (VPLS) or interface
(Layer-3 services). The hashing configuration applies to traffic ingressing an SR OS router
system on an FP2- or higher-based line card and egressing the system over LAG/ECMP.

IPsec Feature Release 13.0.R4 adds the following feature support on the 7750 SR-c12:
Additions for 7750 • Multi-active tunnel-group
SR-c12
• MC-IPsec
• IPv6 IPsec support
See also Scaling in the Enhancements section.

IPsec: IKEv2 Release 13.0.R4 introduces DHCPv4 based address assignment for IKEv2 remote-access
Internal Address tunnels and allows the user to use an external DHCPv4 server for internal address assignment.
Assignment via SR OS acts as a DHCPv4 client on behalf of the IPsec client and also as a relay agent to relay
DHCP DHCPv4 packet to the server.

IPsec Auto-Update Release 13.0.R4 introduces an automatic mechanism for updating the Certificate Revocation
CRL List (CRL) file. It allows the user to configure up to eight (8) HTTP URLs for a given
ca-profile. The system will try to download the latest CRL from the configured URL based on
a configured schedule. There are two types of schedules:
• periodic—The system will update the CRL periodically at the interval configured using
the command periodic-update-interval. For example, if periodic-update-interval is set
to one (1) day, then the system will update the CRL every one (1) day. The minimum
periodic-update-interval is one (1) hour.
• next-update-based—The system will update the CRL when the time is equal to
Next_Update_time_of_current_CRL minus pre-update-time. For example: if
Next_Update_time_of_current_CRL is 2015-06-30 06:00 and pre-update-time is one (1)
hour, then system will start the update at 2015-06-30, 05:00.
The system will use the URL in configured order, and replace the existing CRL with first-
qualified downloaded CRL. A qualified CRL is a valid CRL and more recent than the existing
CRL.
There following are exceptions to next-update-based scenarios:
• If the current CRL file does not contain a “Next Update” field, system will not schedule
further update.
• If the current CRL file contains a “Next Update” value which is beyond the system limit,
system will not schedule further update.
• At the time when enabling the auto-crl-update, if the configured pre-update-time is
larger than Next_Update_time_of_current_CRL minus system current time, the next
scheduled update time will be set to system current time plus retry-interval.

46 SR OS 13.0.R10 Software Release Notes


New Features

IPsec IPv6 Release 13.0.R4 adds the dual-stack support for static LAN-to-LAN IPsec tunnels and IKEv2
Enhancements remote-access tunnels. With this addition, the system now supports both IPv4 and IPv6 traffic
in the same CHILD_SA. For static LAN-to-LAN tunnels, the user can now configure both IPv4
and IPv6 prefixes in the same security-policy entry; for IKEv2 remote-access tunnels, when the
address source (for example, RADIUS or LAA) returns both IPv4 and IPv6 address, the system
will return both to client via the IKEv2 configuration payload.

Video ISA - Release 13.0.R4 introduces the ability to disable FCC/RET client mode. The 7750 SR or 7450
Disable ESS can act as an FCC/RET server as well as a client. By default, the MS-ISA functions as both
Retransimission FCC/RET server and client. The new command enable-rt-client provides the ability to disable
Client the client mode. Disabling the client mode allows the MS-ISA to process higher number of
FCC/RET messages.

Video ISA - A new command, fcc-session-timeout, allows the adjustment of the RTCP session for
Adjustable FCC/RET. By default, an RTCP session remains open for five (5) minutes. The adjustable timer
FCC/RET Timer allows shorter sessions, thereby allowing a higher connectivity rate. Video interface must
remove the accounting policy when fcc-session-timeout is used. Accounting policy with the
video interface is not supported with fcc-session-timeout.

Subscriber
Management

Data-trigger MAC Release 13.0.R4 offers a new MAC learning mechanism for IP-only static host. An IP-only
Learning for static host’s actual data traffic is used for MAC address learning. The data traffic sent must
Static-host match the host’s configured IP-address or the configured IPv6-prefix range.

ESM Host Creation Starting with Release 13.0.R4, ESM host creation via DHCP-snooping is supported for both
via DHCPv6 IPv4 and IPv6 hosts. This feature mainly benefits service providers that use a Layer-3 network
Snooping to aggregate subscribers’ traffic to the BNG. The BNG snoops DHCPv6 messages exchanged
between the subscribers and the DHCP server. A DHCPv6 solicit message will trigger an
authentication request to the AAA server. If the authentication passes, the DHCPv6 reply
message from the DHCP server will trigger the BNG to create an ESM host on the BNG. The
downstream router must be modeled as an IPv6 static host with MAC.

DHCPv6 Filter Release 13.0.R4 introduces a DHCPv6 filter for ESM hosts. ESM hosts created via DHCPv6-
snooping can also benefit from the DHCPv6 filter action “bypass host creation”, which requires
default hosts entries. For example, during a node failure, hosts temporarily fail over to a backup
node and do not require ESM host creation.The hosts can forward traffic via the configured
default host. Furthermore, the DHCPv6 filter has an option to specifically bypass WAN or PD
host creation. Service providers that prefer to share the same /64 among multiple WAN hosts
can choose to bypass WAN host creation option.

SR OS 13.0.R10 Software Release Notes 47


New Features

DHCPv6 IA-PD as Release 13.0.R4 enhances DHCPv6 IA-PD modeled as a managed route, such that the managed
Managed Route route can now also point to an IPv4 subscriber host as next hop. For IPoE hosts, it is a
with IPv4 Next Hop prerequisite that ipoe-session is enabled on the group-interface.
The CLI is enhanced to include the next hop type: pd-managed-route [next-hop {ipv4|ipv6}.
See Changed or Deprecated Commands for more information.
IPv6 filters, QoS IPv6 criteria and IPv6 multicast are not supported for DHCPv6 IA-PD as
managed route pointing to an IPv4 subscriber host as next hop. See also the Known Limitations
section.

Local DHCPv6 Release 13.0.R4 adds the support for lease query by client-ID (RFC 5007) to the local DHCPv6
Server Lease server. For security reasons, this must be explicitly enabled via the CLI flag allow-lease-query
Query Support under configure (router | service vprn svc-id) dhcp6 local-dhcp-server server-name. User
identification must be set to DUID (the default) for lease query to work. Lease query by address
is not supported. It is not possible to filter out leases with the link address; the server will always
return all addresses for a client. The Relay Data and Client Link options are not supported and
will not be returned.

WLAN-GW DSM Release 13.0.R4 adds SLAAC and DHCPv6 support to Distributed Subscriber Management
IPv6 Support (DSM). Single authentication per UE is triggered by the first incoming message (DHCPv4,
DHCPv6, Router Solicit or v4/v6 data-trigger). DSM supports any combination of DHCPv4,
DHCPv6 and SLAAC. All existing DSM features are supported, including Lawful Intercept,
AA divert, filters, policers, portal redirect and one-time redirect. IPv6 does not use NAT, and
Wholesale/Retail is supported in order to forward IPv6 traffic in the same VRF as the IPv4 NAT
outside traffic. DSM IPv6 and ESM are not supported on the same vlan-range.
The SLAAC implementation supports DNS signaling (RFC 6106), privacy extensions (RFC
4941), and up to three (3) simultaneously active /128 addresses. The DHCPv6 implementation
supports a single IA_NA address (RFC 3315), optional LDRA encapsulation (RFC 6221) and
DNS signaling (RFC 3646). Stateless DHCPv6 Information Request (RFC 3736) is supported
to allow additional configuration of SLAAC hosts. Solicited and unsolicited router
advertisements (RFC 4861) are supported for both SLAAC and DHCPv6.
On the CPM, a pool manager allocates IPv6 pools to each MS-ISA that can be used in DHCPv6
or SLAAC. The pool manager retrieves these pools via DHCPv6 prefix delegation. Per-UE
allocations are kept locally only on the MS-ISA to maximize performance. The pool manager
enables the support for IOM redundancy and Active/Standby redundancy. The new active MS-
ISA will receive which pools were installed to support forwarding of data-triggered UEs, but
will not allocate new leases for this pool because allocation state was lost. A new pool will be
allocated for new leases. Migration of a data-triggered UE to a new lease is done via prefix
deprecation (SLAAC) or by assigning a new address in a Renew message (DHCPv6). In the
case of Active/Standby redundancy, the pool manager retrieves the old pools using a Lease
Query (RFC 5007).

IPoE Session Release 13.0.R4 adds the following additional capabilities to IPoE session:
Enhancements • multi-chassis redundancy for IPoE sessions active on a retail subscriber interface
• a seamless migration to IPoE sessions by enabling IPoE session on a group interface with
active subscriber hosts. At the next renewal of the DHCP subscriber host, it is attached to

48 SR OS 13.0.R10 Software Release Notes


New Features

an IPoE session. Alcatel-Lucent recommends preparing and validating a migration plan in


advance of configuring for this migration.

SHCV policy Release 13.0.R4 introduces policies to control Subscriber Host Connectivity Verification
(SHCV), a mechanism to verify host connectivity to the BNG. There are two types of SHCV
timers: periodic and event-triggered. Prior to Release 13.0.R4, some event-triggered SHCV
relied on the reference timer set by the host-connectivity-verify under the group interface while
others had static values. This so-called “SHCV policy” function in Release 13.0.R4 allows for
the individual configuration of event-triggered SHCV timers and periodic SHCV timers
depending on the application.

Residential Both anti-spoof filters and host-limits can prevent quick Residential Gateway (RG)
Gateway replacement. A BNG anti-spoof filter registers a unique pair of MAC and IP for each SAP. If a
Replacement new replacement RG with a different MAC obtains the same IP address, it will fail the anti-
spoof filter, and all packets from the new RG will be dropped. The BNG has enhanced both
lease-override and SHCV features to allow faster RG replacements. Lease-override
immediately overrides the old DHCP lease with a new one, while an SHCV policy will perform
a connectivity check before removing a host and its lease.

Gx – PCC Rules In addition to existing Gx-based overrides and NAS-filter inserts, Gx functionality on SR OS
routers now supports fully-defined rules that can be constructed on PCRF and applied to the
subscriber host. Fully-defined rules can identify certain type of traffic and apply certain actions
to it. Such fully-defined rules are referred to as Policy and Charging Control (PCC) rules.
Traffic classification (or traffic identification) in the PCC rule is based on the ip-criteria which
includes fields in the IP header such as 5-tuple (any combination of source IP address, source
port, destination IP address, destination port and protocol) and DSCP bits. Multiple actions
associated with such classified traffic within PCC rule are supported:
• ingress or egress rate-limiting
• ingress or egress forwarding-class (FC) change
• ingress next-hop redirect
• ingress service-ID redirect
• ingress HTTP redirect
• ingress or egress gate function
• ingress or egress usage-monitoring
Usage-monitoring for PCC rules is not supported in conjunction with multi-chassis redundancy.
See Limited Support Features and Enhancements for more information.

Gx CCR-t Replays Unanswered CCR-t messages can be periodically replayed during the 24-hour period or until
the response from PCRF is received, whichever comes first. This functionality is enabled via
configuration.
CCR-t replays are used to ensure that the originally-sent CCR-t message eventually reaches
PCRF in case the connectivity between an SR OS node and PCRF was affected at the time when
the subscriber on the SR OS node was terminated.

SR OS 13.0.R10 Software Release Notes 49


New Features

Static 1:1 NAT in In static 1:1 NAT, inside IP addresses are predictably mapped to outside IP addresses in 1:1
Protocol Agnostic fashion. This is performed not only for TCP/UDP/ICMP, but for all IP-based protocols. Hence,
Mode static 1:1 NAT is protocol-agnostic.
Port translations for TCP and UDP protocols are not performed, although the flow states based
on 5-tuple are maintained in order to support ALGs.
Traffic can be initiated from outside towards any outside IP address that is already statically
mapped to the inside IP address.
Static 1:1 NAT can be deployed simultaneously with other types of Network Address and Port
Translation (NAPT) via separate pools.
Static 1:1 NAT is supported for LSN44.

NAT – Active- Active-active MS-ISA/MS-ISA2 redundancy model for NAT is now supported in addition to
Active MS-ISA/ existing active-standby model. In active-active redundancy mode, traffic from a failed MS-
MS-ISA2 ISA/MS-ISA2 is distributed to the remaining active MS-ISAs/MS-ISA2s without the need to
Redundancy set aside MS-ISA/MS-ISA2 specifically designated for redundancy purposes and operate it in
Model idle mode during standby operation.
In active-active redundancy model, memory resources are reserved on each MS-ISA/MS-ISA2
in order to accommodate additional translations from failed MS-ISAs/MS-ISA2s. However,
bandwidth is not reserved, and each MS-ISA/MS-ISA2 in the system can operate at full speed
at any given time.
NAT translations are not preserved across the switchover; consequently, traffic from the failed
MS-ISA/MS-ISA2 will need to be re-established.

Recovery Tunnel Release 13.0.R4 adds a new recovery method, recovery tunnel for multi-chassis L2TP LAC
for L2TP LAC redundancy.
Multi-chassis • L2TP tunnel/session information is synchronized between LNS and LAC using L2TP
Stateful failover extension (RFC 4951) after SRRP switchover.
Redundancy
• Two recovery methods (MCS or recovery tunnel) can be specified by CLI (the recovery-
method command under L2TP configuration per routing instance) or new Alc-Tunnel-
Recovery-Method VSA.
• L2TP LNS supports L2TP failover extensions (RFC4951) when initiated by LAC.

Wholesale/Retail Release 13.0.R4 completes the Wholesale/Retail service model with the following additional
Enhancements features:
• multi-chassis redundancy for IPv6 (IPoE and PPPoE)
• SRRP tracking for IPv4 subscriber subnets and IPv6 subscriber prefixes on a retail
subscriber interface—Via routing policies, downstream subscriber traffic can then be
attracted to the master SRRP node to avoid traffic shunting between multi-chassis
redundant nodes.
• overlapping IPv6 prefixes in the retail service for IPoE and PPPoE (enabled with the
private-retail-subnets command on a VPRN retail subscriber interface)—Note that multi-
chassis redundancy in combination with private-retail-subnets is not supported.

50 SR OS 13.0.R10 Software Release Notes


New Features

Application
Assurance

Captive Redirect The captive redirect HTTP redirect policy is used to redirect flows without sending any traffic
HTTP Redirect to the Internet unless it matches a configurable whitelist by terminating TCP sessions in the
Policy MS-ISA cards, in which case HTTP flows are redirected to a predefined redirect URL while
non-HTTP TCP flows are TCP reset.
Traffic can be whitelisted using IP address, port number or by using a DNS-IP-cache allowing
traffic to a list of configurable domain names.

OAM

OAM-PM 5-mins Release 13.0.R4 adds the support for a short-duration, five-minute (5-mins), measurement
Measurement interval under the OAM-PM Session configuration. The meas-interval parameter now supports
Interval Support 5-mins, 15-mins, 1-hour and 1-day options.

Release 13.0.R3

Hardware

Support for For 7750 SR-7/12/12e and 7450 ESS-7/12 platforms equipped with CPM5, both the input and
2048kHz Signal on output BITS ports now support G.703 T12 signal format (2048 kHz) in addition to G.703 E12
the CPM5 BITS (E1) and G.703 E11 (DS1) formats. This feature is not supported on CPM4 or earlier versions,
Ports and requires a minimum revision of the CPM5.

Release 13.0.R2
Release 13.0.R2 has no new major features. See also Enhancements in Release 13.0.R2 and
Resolved Issues in Release 13.0.R2.

Release 13.0.R1
The following sections describe the new features added in Release 13.0.R1 of SR OS.
− Hardware
− System
− Quality of Service
− Routing

SR OS 13.0.R10 Software Release Notes 51


New Features

− MPLS
− Services
− Subscriber Management
− Application Assurance
− OAM
Release 13.0.R1 includes features available in Release 12.0.R8. Refer to the SR OS 12.0.R8
Release Notes for features available in Release 12.0.R8, added since Release 12.0.R1.

Hardware The following section describes the new hardware supported in Release 13.0.R1.

4-PORT 100GE Release 13.0.R1 introduces the 4-port 100GE CFP4 Multicore-CPU-based IMM to the Alcatel-
CFP4 IMM Lucent IMM family. The 4-port 100GE CFP4 uses the FP3 chipset, providing the following key
benefits:
• Supports up to 400 Gb/s (full duplex) with SF/CPM5-12e and mini-SFM-12e in 7750
SR-12e, but in order to achieve this level of throughput, the chassis will require all T3-
based IOMs/IMMs
• Supports up to 270 Gb/s throughput when two (2) SF/CPM4-12e and two (2) mini SFM-4
are installed/operational
• Maximum of 128K queues for ingress and 128K queues for egress that can be flexibly
assigned to any port
• Full range of edge services with deterministic performance
• Support for Alcatel-Lucent-sourced CFP4 optic modules (not included)
• LAN and WAN mode support
• Soft Reset support
There are Right-to-Use (RTU) licenses associated with IMM hardware depending on the
features used. Contact your Alcatel-Lucent representative for the appropriate application
licenses.
IMPORTANT NOTE: Impedance panels must be purchased and installed in all systems in
which an IMM is used. These impedance panels provide highly efficient air flow in support of
the higher performing IOM3-XP/B/C and newer IOM/IMM modules. Note that even when only
one IMM/IOM is deployed, impedance panels are required.

SF/CPM2 and Release 13.0.R1 introduces the support for the following T3-based IOMs, IMMs and ISMs with
SF/CPM3 Support SF/CPM2 and SF/CPM3 in the 7450 ESS-7/12 and the 7750 SR-7/12.
for T3-based Line • IOM3-XP-C
Cards
• 48-Port GE SFP Rev-C IMM
• 12-port 10GE Multicore SFP+ IMM
• 20-port 10GE Multicore SFP+ IMM
• 3-port 40GE QSFP+ + 20-port GE SFP IMM
• 1-port 100GE CFP + 10-port 10GE SFP+ IMM
• 10-port 10GE SFP+ + 20-port GE SFP IMM

52 SR OS 13.0.R10 Software Release Notes


New Features

• 1-port 100GE Multicore CFP IMM


• 2-port 100GE Multicore CFP IMM
• 6-port 40GE Multicore QSFP+ IMM
• 1-port 100GE DWDM Tunable IMM
• Multiservice ISM
• Multiservice ISM-E
• MS-ISA2 + 10-port 10GE SFP+ IMM
• MS-ISA2-E + 10-port 10GE SFP+ IMM
• MS-ISA2 + 1-port 100GE CFP IMM
• MS-ISA2-E + 1-port 100GE CFP IMM
There are Right-to-Use (RTU) licenses associated with IMM/ISM hardware depending on the
features used. Contact your Alcatel-Lucent representative for the appropriate application
licenses.

System The following section describes the new system features in Release 13.0.R1.

BFD Soft Reset Release 13.0.R1 adds a new option to the BFD-over-LAG links capability so that the BFD
Control over LAG timers are not extended during a Soft Reset operation on an IOM/IMM/XCM. As a result, BFD
session may time out during the Soft Reset operation and the associated LAG links will be
removed from the operational state. This option should only be used if alternate paths exist and
can be resolved faster then the Soft Reset process can complete. This option is controlled by
including the keywords disable-soft-reset-extension to the config>lag>bfd [disable-soft-
reset-extension] command.

IEEE 1588 With IEEE 1588 messaging is now supported using direct encapsulation in Ethernet frames, as per
Ethernet Annex F of the standard. IEEE 1588 with Ethernet encapsulation is supported on all platforms
Encapsulation and CPMs/CFMs that currently support IEEE 1588 with UDP/IPv4 encapsulation. IEEE 1588
with Ethernet encapsulation requires FP2-based IOMs or IMMs, or newer; it is not supported
with IOM1 or IOM2. IEEE 1588 port-based timestamping (PBT) for Ethernet encapsulation is
supported on all hardware assemblies that currently support IEEE 1588 PBT for UDP/IPv4
encapsulation. This encapsulation mechanism is configured on a per-port basis.

Enforce Use of Release 13.0.R1 introduces the ability to block immediate configuration changes in the CLI
Candidates for configure context. The no immediate configuration under the config>system>management
Configuration CLI context can be used to enforce the use of candidate configuration (and the candidate
Changes commit command) instead of immediate mode line-by-line configuration changes.

Event Handling Release 13.0.R1 introduces a tool that allows operator-defined behavior to be configured on the
System (EHS) router. Event Handling System (EHS) adds user-controlled programmatic exception handling
by allowing a CLI script to be executed upon the detection of a log event (the trigger). Regular
expression matching is available on various fields in the log event to give flexibility in the
trigger definition.

SR OS 13.0.R10 Software Release Notes 53


New Features

Filter Policies: Release 13.0.R1 introduces a new type of line card filter policy: ingress IPv4/v6 system policy.
Ingress IPv4/IPv6 Multiple policies can be configured, but only a single active IPv4 system policy and a single
System Line Card active IPv6 system policy can be activated.
Filter Policy The IPv4/IPv6 system filter policy supports the configuration of all IPv4/IPv6 filter policy
match rules and actions, but system policy entries cannot be the sources of mirroring and NAT.
The scale of a system filter policy is identical to a corresponding IPv4 or IPv6 filter policy scale.
A system filter policy cannot be used directly; the active system policy can be deployed by
activating it within any IPv4 or IPv6 exclusive/template filter policy (chaining system policy
and interface policy). When an IPv4 or IPv6 filter policy is chained to the active system filter
policy, system filter rules are evaluated first before any rules of the chaining filter policy are
evaluated (that is, the chaining filter’s rules are only matched against if no system filter match
took place).
Alcatel-Lucent recommends using a system policy with drop/forward actions. Other actions,
such as PBR actions or redirect to ISAs, should not be used unless the system filter policy is
activated only in filters used by services that support such action. Failure to observe this
restriction can lead to undesired behavior as system filter actions are not verified against
services the chaining filters are deployed for.
System filter policies can be populated using CLI/SNMP/NETCONF management interfaces
and OpenFlow policy interface. System filter policy entries cannot be populated using
FlowSpec, RADIUS, or Gx interfaces.
A system filter policy consumes a single set of hardware resources on each line card as soon as
it is activated, regardless of how many IPv4 or IPv6 filter policies chain to that system policy.
System filter policies require chassis mode D.

Filter Policies: Release 13.0.R1 enhances the packet-length support in ingress filter policies by adding support
Packet-length for packet-length condition with drop action for IPv6 filter policies on platforms supporting
Support in IPv6 IPv6 filter policies (the configured packet-length value is matched to Payload Length field in
Filters the IPv6 header).
A filter policy with packet-length condition is not supported in egress directions and on FP1 line
cards. Deploying the filter policy in those scenarios may lead to an unexpected behavior
(packets matching an entry always dropped or always forwarded) and thus should be avoided.

Filter Policies: Release 13.0.R1 introduces the support for IPv4 and IPv6 filter policies on network ports for
VPRN Service- VPRN services. In each VPRN service, an operator can now assign an ingress IPv4 and/or IPv6
aware Network filter policy of scope template that will be applied to unicast traffic arriving on all network
Interface Ingress interfaces for that VPRN (auto-bind-tunnel and explicitly defined spokes). The filter policy is
Filter Policy supported for inter-AS and intra-AS network ports and for any-service label type and any
network transport type. The feature requires network chassis mode D. The feature is not
supported with FlowSpec or Lawful Intercept.

IPv4/IPv6 SPI Release 13.0.R1 introduces SPI hashing for IPv4/IPv6 traffic over VPLS services and Layer-3
Hashing for ESP interfaces. The functionality allows a deployed SR OS router, for example, in an LTE mobile
Encrypted Traffic backhaul network, to use an SPI value from the ESP header of the encrypted tunnel in hash
inputs in addition to Layer-3/4 tunnel IP inputs for better traffic distribution across multiple

54 SR OS 13.0.R10 Software Release Notes


New Features

ECMP paths/LAG links. SPI hashing can be enabled per service (VPLS) or interface (Layer-3
services). The hashing configuration will apply to traffic ingressing an SR OS router on an FP2-
and higher-based line card and egressing the system over LAG/ECMP.

Hybrid OpenFlow Release 13.0.R1 introduces the support for VPLS and VPRN service match in OpenFlow flow
Switch (H-OFS): table rules. An OpenFlow controller can specify a VPRN or VPLS service ID as a match
VPLS/VPRN criterion for H-OFS flow table rules. The functionality is achieved through encoding of the
Service Match in SR OS service ID as part of the flow table entry cookie value. A flow table rule with a
Flow Table Rules VPLS/VPRN service ID match is installed on all ingress interfaces of a matched service that
have an ACL policy that embeds a given H-OFS instance. This allows a single H-OFS instance
to contain rules for Layer-2 VPLS services and Layer-3 VPRN services.
Note that the same H-OFS instance can also contain rules for GRT interfaces and system filters.
The feature requires H-OFS with switch-defined-cookie enabled (a multi-service H-OFS).

Hybrid OpenFlow Release 13.0.R1 introduces the support for control of IPv4 and IPv6 System Filter policies using
Switch (H-OFS): OpenFlow. An OpenFlow controller can specify that a given flow table rule applies to system
System Filter filter policies through the encoding of a system policy scope as part of the flow table entry
Policy Match in cookie value. A flow table rule with a system filter scope is installed in all system policies with
Flow Table Rules this H-OFS instance enabled and will apply to any interface that activates a given system policy.
Note that the same H-OFS instance can also contain rules for VPLS/VPRN and GRT interfaces.
The feature requires H-OFS with switch-defined-cookie enabled (a multi-service H-OFS).

Hybrid OpenFlow Release 13.0 introduces the support for port and VLAN ID match in OpenFlow flow table rules
Switch (H-OFS): that also specify a VPLS service ID match. An OpenFlow controller can program an SR OS
Port and VLAN ID Ethernet physical port or a (MC-)LAG in a port match and one of the following:
Match in Flow • an untagged traffic match using standard OpenFlow v1.3.1 flow table match criteria
Table Rules
• a VLAN ID for single-tagged traffic match using standard OpenFlow v1.3.1 flow table
match criteria
• an inner and outer VLAN IDs for dual-tagged traffic match using standard OpenFlow 1.3.1
flow table match criteria and Alcatel-Lucent experimenter match criteria extensions
Masking of port/VLAN values for a flow table match is supported with the exception of adding
a new flow table rule. A flow table rule with port and VLAN match criteria is installed on all
existing VPLS SAPs that match the specified port and VLAN ID values and have an ACL
policy that embeds the H-OFS instance. The feature requires H-OFS with switch-defined-
cookie enabled (a multi-service H-OFS).

Hybrid OpenFlow Release 13.0.R1 introduces the support for Layer-3 (L3) Policy-Based Routing (PBR) for H-
Switch (H-OFS): OFS flow table actions applicable to GRT and VPRN interfaces. OpenFlow controller can
Layer-3 PBR program:
Support • redirect to an IPv4/IPv6 direct/indirect next-hop using OpenFlow v1.3.1 Alcatel-Lucent
experimenter extension
• redirect to GRT or VRF through encoding of “Base” or VPRN service ID in Logical Output
port

SR OS 13.0.R10 Software Release Notes 55


New Features

The functionality provided for the above L3 PBR actions when programmed through OpenFlow
is equivalent to L3 PBR when programmed using management interfaces. The feature requires
H-OFS with switch-defined-cookie enabled (a multi-service H-OFS).

Hybrid OpenFlow Release 13.0.R1 introduces the support for Layer-2 (L2) Policy-Based Forwarding (PBF) for H-
Switch (H-OFS): OFS flow table actions applicable to VPLS interfaces. OpenFlow controller can program:
Layer-2 PBF • redirect to a VPLS SAP using standard OpenFlow v1.3.1 protocol and Alcatel-Lucent
Support experimenter extension for dual-tagged SAPs.
• redirect to a VPLS SDP using OpenFlow v1.3.1 Alcatel-Lucent experimenter extension
The functionality provided for the above L2 PBF actions when programmed through OpenFlow
is equivalent to L2 PBF when programmed using management interfaces. The feature requires
H-OFS with switch-defined-cookie enabled (a multi-service H-OFS).

PBR: IPv6 Redirect Release 13.0.R1 introduces the support for IPv6 redirect policies for line card filter policies.
Policy Support Operators can define an IPv6 filter policy by specifying the redirect policy destinations to be
IPv6 addresses and then reference that filter policy in the IPv6 line card filter. A single redirect
policy can only contain IPv6 or (exclusive) IPv4 destinations. An IPv6 redirect policy does not
support SNMP and URL destination tests. All new redirect policy enhancements introduced in
Release 13.0 are also supported for IPv6 redirect policy. An IPv6 redirect policy requires
chassis mode D.

PBR: Enhanced Release 13.0.R1 introduces enhanced VPRN support for redirect policies. Operators can now
Redirect Policy for configure a target routing instance (config>filter>redirect-policy>router) as part of the
VPRN redirect policy. When the target routing instance is configured, the following applies:
• Any supported test configured in a redirect policy is now executed in the routing instance
specified by the redirect policy regardless of the routing instance in which a filter using this
redirect policy is deployed.
When packets are routed to a destination configured in a redirect policy with the router instance
specified (as result of filter match), routing is executed in the router instance context configured
in the redirect policy regardless of the routing context for the interface on which the packet
arrived. Note that if all destinations are down, the forward action is still executed in the routing
instance of the incoming interface and not the routing instance of the redirect policy. If the
hardware does not support the “next-hop router” PBR action, action forward is executed.

PBR: Redirect Release 13.0.R1 allows an operator to configure a unicast route reachability test as part of
Policy Unicast destination tests in a redirect policy. When configured, a destination is eligible for the redirect
Route Reachability policy best-destination selection only when the destination has a route in the RTM within the
Test target routing context of the redirect policy. Redirect policy unicast route reachability test is
supported for both IPv4 and IPv6 redirect policies.

LACP Multiplexing LACP RX/TX independent mode is now supported in Release 13.0.R1. When enabled, LACP
– Independent first enables RX on a LAG link and then sends an indication to the far-end node that it is ready
Control to receive traffic. Upon the reception of this indication, the far-end system can enable TX.
Therefore, in independent RX/TX control, LACP adds a link into a LAG only when it detects
that the other end is ready to receive traffic. This minimizes the traffic loss that might occur in

56 SR OS 13.0.R10 Software Release Notes


New Features

coupled mode when a port is added into a LAG before notifying the far-end system or before
the far-end system is ready to receive traffic. Similarly, on link removals from LAG, LACP
turns off the distributing and collecting bit and informs the far-end system about the state
change. This allows the far-end side to stop as soon as possible with sending the traffic.
When adding a port to a LAG in a high-scaled deployment, and that port is the first to be added
to the LAG on that IOM/IMM/XCM, Alcatel-Lucent recommends first shutting down the port,
adding the port to the LAG, then re-enabling the port after a short delay to allow for the
forwarding configurations. This procedure minimizes outages.

RADIUS Challenge In Release 13.0.R1, for enhanced security, SR OS supports RADIUS Access-Challenge
Response authentication method as per RFC 2865.
Authentication

Per-SNMP Release 13.0.R1 introduces the ability to validate SNMPv1 and SNMPv2c requests against per-
Community SNMP-community whitelists (src-access-list) of allowable source IPv4 and IPv6 addresses.
Source IP Address Source IP address lists can be configured then associated with an SNMPv1 or SNMPv2c
Validation community. SNMPv1 or SNMPv2c requests that fail the source IP address or community
validation check are discarded.

Support for On the CPM of the 7750 SR-a4/a8, both the input and output BITS ports now support G.703
2048kHz Signal on T12 signal format (2048 kHz) in addition to G.703 E12 (E1) and G.703 E11 (DS1) formats.
7750 SR-a4/a8
BITS Ports

VMware ESXi The virtualized route reflector (VSR-RR) and virtualized simulator (VSR-SIM) are now
Hypervisor supported on virtual machines created and managed by the VMware ESXi 5.5 hypervisor. This
Support for VSR- adds to the KVM/QEMU hypervisor support introduced in Release 12.0. An Open
RR and VSR-SIM Virtualization Archive (OVA) package containing the SR OS binaries and a starter VSR-RR
configuration is available for download. This OVA package, which contains a VMDK disk
image and OVF file, facilitates the deployment of new VMware virtual machines supporting
VSR-RR or VSR-SIM functionality.

YANG Data Models In Release 13.0.R1, a full YANG data model is provided for all SR OS configuration data (the
for Configuration equivalent of everything under the CLI configure context). The YANG data model is composed
with NETCONF of a set of proprietary Alcatel-Lucent YANG modules that are distributed as part of the SR OS
image file bundle. XML formatted configuration data that conforms to the YANG modules is
supported by the SR OS NETCONF server.

NETCONF XML Release 13.0.R1 introduces the support for XML format content layer requests and responses
Format Content for configuration data. Both <edit-config> and <get-config> NETCONF requests support an
Layer for XML format for the content layer.
Configuration Data

SR OS 13.0.R10 Software Release Notes 57


New Features

Release 13.0.R1 Release 13.0.R1 also adds a number of other NETCONF enhancements including:
NETCONF • <edit-config> operations: merge, create, delete and remove
Enhancements
• <copy-config> (for example, from running to startup to get the equivalent of admin save)
• <delete-config> for startup and URL
• <validate> operation and <test-option>
• Equivalent of rollback save and rollback revert
• NETCONF RFC 6241 base 1.1 capability (primarily chunked framing)

Quality of The following section describes the new Quality of Service features in Release 13.0.R1.
Service

Broadcast, Support has been added to allow ingress QoS control of broadcast, unknown and multicast
Unknown, and (BUM) traffic received on a spoke- or mesh-SDP within a VPLS service. The BUM traffic can
Multicast Ingress be separately redirected to policers within an FP ingress network queue group using the per-
QoS Control on forwarding class fp-redirect-group parameter together with broadcast-policer, unknown-
VPLS or policer and mcast-policer within the ingress section of a network QoS policy. The network
Mesh-SDPs QoS policy can be applied to a specific spoke- or mesh-SDP, or to a network IP interface in
which case the control applies to all BUM traffic received on that interface for that forwarding
class (including that received on EVPN bindings).
Prior to Release 13.0.R1, QoS control of the above traffic was combined using fp-redirect-
group multicast-policer, consequently the multicast-policer parameter has been deprecated in
favor of the mcast-policer parameter. See Changed or Deprecated Commands for more
information.
This is supported on FP2- and higher-based hardware.

Ingress QoS Support has been added for ingress QoS control of unicast traffic into a VPRN (including a
Control of Traffic Carrier-Supporting-Carrier VPRN) over automatically-created (using the auto-bind-tunnel
on VPRN Bindings command) or manually-created (using a spoke-sdp command; but not the spoke-sdp command
under the VPRN IP interface context) bindings in a VPRN service.
Unicast traffic received on all automatic and manual bindings in the VPRN can be redirected
per forwarding class to policers in an ingress FP queue group. The traffic from all such bindings
is treated as a single entity (per forwarding class) with respect to QoS control.
This is supported for all available transport tunnel types and is independent of the label mode
(vrf or next-hop) used within the VPRN. IPv4 and IPv6 criteria statements are not supported in
the applied network QoS policy.
The ingress network interfaces on which the traffic is received must be on FP2- or higher-based
hardware. This is ignored on FP1-based hardware.

Queue-depth Queue-depth monitoring has been added in Release 13.0.R1 to give more visibility to the
Monitoring operator of the queue depths being experienced on a set of queues when the traffic is bursty. An
override can be configured on service SAPs or queue group queues to enable monitoring of their
queue depth. The monitoring uses a polling mechanism. The results are presented in the form

58 SR OS 13.0.R10 Software Release Notes


New Features

of occupancy ranges of 10% of the queue depth for each configured queue with the percentage
of polls seen in each occupancy range. The occupancy results, together with a clear function,
are available both through a CLI command and SNMP MIB. This is supported on FP2- and
higher-based hardware.

Ingress The ingress classification in a network QoS policy has been enhanced to support both ip-
Classification criteria and ipv6-criteria statements. This classification only applies to the outer IP header of
Using IP Criteria non-tunneled traffic, except for traffic received on a RFC 6037 MVPN tunnel for which
and IPv6 Criteria classification on the outer IP header only is supported. The application of network QoS policies
Statements for with IP or IPv6 criteria statements is only supported on network interfaces. QPPB processing
Network Interfaces takes precedence over this feature.
This is supported on FP2- and higher-based hardware.

Routing The following section describes the new routing protocol features in Release 13.0.R1.

Auto-RD A new auto-RD (Route Distinguisher) option has been added to BGP-enabled services. This
feature allows the user to decide whether a manual RD or a system-selected RD is allocated on
a per-service basis. The new option for the RD is available for VPLS, VPRN and Epipe services.
When auto-RD is configured, a type-1 RD will be automatically allocated by the system based
on the configuration of the bgp-auto-rd-range command:
bgp-auto-rd-range ip-addr comm-val 1-65535 to 1-65535

BGP ECMP Release 13.0.R1 enhances the implementation of BGP multipath by introducing the support for
Weighted Load- weighted load-balancing across the ECMP BGP next-hops of an IPv4 or IPv6 route. Weighted
balancing load-balancing allows more traffic to be forwarded to one ECMP next-hop A, compared to a
second ECMP next-hop B, if it is known that the path through A has more available bandwidth
than the path through B. The available bandwidth of a path can be signaled in a BGP route using
a Link Bandwidth extended community.
With the introduction of this feature, SR OS now has the ability to recognize, add, delete, or
replace Link Bandwidth extended communities. A Link Bandwidth extended community can
be added to a BGP route using a BGP export policy, BGP import policy, VRF import policy, or
an EBGP neighbor level command. Weighted load-balancing is performed automatically only
when all the BGP ECMP next-hops of a BGP route carry a Link Bandwidth extended
community.
The use of weighted load-balancing does not change the criteria for different paths to be
considered equal by the BGP decision process for purposes of BGP multipath. Weighted load-
balancing at the BGP next-hop level can be used with weighted load-balancing at the IGP level
if one or more of the BGP ECMP next-hops are resolved by IGP shortcut routes and the LSPs
to a BGP next-hop have different weights. This feature is supported on FP2- and higher-based
hardware.

Route Policy Release 13.0.R1 extends the BGP Fast Reroute functionality to allow route policies to control
Support for BGP whether or not a backup path is calculated and installed for a particular IP prefix. In previous
Fast Reroute releases, the backup path functionality was configurable only per router and per address family.

SR OS 13.0.R10 Software Release Notes 59


New Features

With the new route policy control, the backup path can be installed for an IPv4 or IPv6 prefix
if one of the existing router-level commands is configured, or if the best BGP route for the prefix
was matched by a BGP import policy or a VRF import policy with the new install-backup-path
action. This feature does not change the behavior of route types for which backup paths are
supported.

BGP Prefix Limits Release 13.0 adds new flexibility to BGP prefix limits. In previous releases, only one prefix
per Address limit was configurable per BGP neighbor, and this limit applied only to received IPv4 and IPv6
Family unicast routes, prior to any import policy processing. Each address family can now be
configured with its own independent prefix limit, and each address family limit can be evaluated
either at the pre-import policy stage or the post-import policy stage. (A limit applied post-import
does not count received routes that were rejected by the policy.)

Show Route Table Release 13.0.R1 provides a new, extensive output option for the show router route-table and
and FIB Extensive show router fib commands. The existing, non-extensive outputs prior to Release 13.0.R1 do
Outputs not show BGP next-hop detail. The extensive output displays the BGP next-hops of a BGP route
and shows the resolved next-hops of each BGP next-hop in a structured format. .

Cflowd: Multicast In Release 13.0.R1, the Cflowd feature has been expanded to support the sampling and
Sampling Support processing of multicast IP flows. If enabled, multicast flows will be subject to traffic sampling
based on the sampling rate, just as unicast traffic would be sampled. Multicast flow statistics are
then sent to the Cflowd collector using existing IPv4 and IPv6 templates; however, two new
fields will be added to report the multicast replication factor (field ID 99) and a flag indicating
that the flow was a multicast flow. When multicast sampling is enabled, this feature does not
include the sampling of multicast control plane traffic destined to the CPM/CFM.
See Changed or Deprecated Commands for more information about changed commands.

Cflowd: Addition In Release 13.0.R1, two new fields, MPLS_TOP_LABEL TYPE (field ID 46) and
of FEC Address to MPLS_TOP_LABEL_ADDR (field ID 47), have been added to the MPLS-related templates for
MPLS Templates Cflowd formats v9 and v10. These fields can be used to show the far-end IP address for the top
MPLS label as well as the protocol source of this transport label. SR OS will only report the far-
end IP address for LDP sourced MPLS labels (all other sources will result in a null value in both
fields) and only supported on ingress sampling at the LSR routers.

Empty Prefix Lists In Release 13.0.R1, it is now possible to configure a prefix-list which is empty (containing no
in Router Policy member prefixes) in router policies, which will evaluate as if “no match” was found when
referenced in a policy. When removing member prefixes from a prefix-list, the latter will no
longer be automatically removed when the last member is removed. If required, the empty
prefix-list must be explicitly removed by the operator.

IS-IS ATT Release 13.0.R1 enables the configuration of IS-IS to suppress setting the attached bit (ATT) on
(Attached) Bit originated Level-1 LSPs, to prevent all Level-1 routers in the area from installing a default route
Suppression to the router which the command is configured and which originates the LSPs.

60 SR OS 13.0.R10 Software Release Notes


New Features

IS-IS Single IS-IS interoperability has been extended to enable a non-multi-instance (MI) capable router to
Instance Router in establish an adjacency in its standard instance zero (0) with an SR OS router in a non-zero
a Non-Zero instance. See Enhancements in Release 13.0.R4 for more information.
Instance

IPv6 MCAC Policy Release 13.0.R1 extends the existing MCAC policy support by adding the support for IPv6
with Source MCAC policies, including source awareness. The IPv6 MCAC is supported for PIM and MLD.
Awareness See Enhancements in Release 13.0.R4 for more information.
Support

Multipoint LDP Release 13.0.R1 enhances the support for in-band mLDP signaling for IPv6 multicast. The
In-band Signaling following enhancements are added atop of the existing functionality (IPv4 PIM SSM with in-
Enhancements for band IPv4 P2MP mLDP signaling in the “Base” routing instance).
IP Multicast • Support for IPv6 SSM PIM with in-band IPv4 P2MP mLDP signaling for IP multicast in
in GRT the “Base” routing instance as per RFC 6826: Multipoint LDP In-Band Signaling for Point-
to-Multipoint and Multipoint-to-Multipoint Label Switched Paths.
• Support for OAM p2mp-lsp-ping for all the above in-band mLDP signaling use cases.

Route Policy In Release 13.0.R1, the policy variable expansion functionality is extended with midstring
Midstring Variable variable expansion for global policy objects. Policy variables such as “peer-@asname@” or
Expansion “comm-@peeras@-highpref” can be configured to provide smaller and more efficient policies.
Release 12.0 supports policy variables contained completely in the name, such as
“@localcomm@” or “@peeras@”. The following global policy objects support midstring
variable expansion: as-path, as-path expression, as-path-group, as-path-group expression,
community, and prefix-list.

Route Policy Release 13.0.R1 extends the Add-Path functionality to allow route policies to control the
Support for BGP number of advertised paths per prefix or NLRI. In previous releases, the maximum number of
Add-Path paths to send was controllable only per neighbor and per address family; this could result in
sending more total paths to a peer than necessary if only some prefixes require a higher number
of paths. With the new route policy control, the maximum number of paths to send for an IPv4
or IPv6 prefix is based on the setting applied by a BGP import policy to the best BGP route for
the prefix.

Route Policy Route policies have been extended to support more general matching of extended communities
Support for in BGP routes. In prior releases, only the following types of extended communities could be
Matching Any matched: route target, route origin, and origin-validation state. A new extended community
Type of BGP syntax allows for matching specific hexadecimal values in the type/sub-type and value fields of
Extended an extended community. In Release 13.0.R1, the new matching functionality is supported only
Community with IP and IP-VPN routes.

SR OS 13.0.R10 Software Release Notes 61


New Features

Segment Routing: Segment routing adds to IS-IS routing protocol the ability to perform shortest-path routing and
Single IS-IS source routing using the concept of abstract segment. A segment can represent a local prefix of
Instance, LFA, a node, a specific adjacency of the node (interface or next-hop), a service context, or an explicit
Link-protect path over the network. For each segment, the IGP advertises an identifier referred to as
Remote LFA Segment ID (SID).
When segment routing is used together with MPLS data plane, the SID is a standard MPLS
label. A router forwarding a packet using segment routing will thus push one or more MPLS
labels.
Segment routing using MPLS labels can be used in both shortest-path routing applications and
in traffic-engineering applications. The scope of this feature is the shortest-path forwarding
application.
When a received IPv4 prefix SID is resolved, the Segment Routing module programs the
Incoming Label Map (ILM) table with a swap operation and also the Label to NHLFE (LTN)
table with a push operation both pointing to the primary/LFA NHLFE. An IPv4 segment-
routing tunnel to the prefix destination is also added to the Tunnel-Table Manager (TTM).
The segment-routing tunnel in the TTM is available to be used in the following contexts:
• VLL, LDP VPLS, IES/VPRN spoke-interface, R-VPLS, BGP-EVPN.
• BGP-AD VPLS, BGP-VPLS, BGP VPWS when the use-provisioned-sdp option is
enabled in the binding to the PW template.
• Intra-AS BGP VPRN for VPN-IPv4 and VPN-IPv6 prefixes with both auto-bind-tunnel
and explicit SDP.
• Multicast-over-IES/VPRN spoke interface with the spoke-SDP riding a segment-routing
tunnel.
• OAM: ping and traceroute within VPRN and SDP keepalive.
Segment routing introduces the remote LFA feature which expands the coverage of LFA by
computing and automatically programming segment-routing tunnels which are used as backup
next-hops. The segment-routing shortcut tunnels terminate on a remote alternate node which
provides loop-free forwarding for packets of the resolved prefixes. When the loopfree-
alternate option is enabled in an IS-IS instance, segment-routing tunnels are protected with an
LFA backup next-hop. If the prefix of a given segment-routing tunnel is not protected by the
base LFA, the remote LFA functionality will automatically compute a backup next-hop using a
segment-routing tunnel if the remote-lfa option is also enabled in the IGP instance.

MPLS The following section describes the new MPLS features in Release 13.0.R1.

GMPLS UNI Release 13.0.R1 introduces the Generalized Multiprotocol Label Switching (GMPLS) User-to-
Network Interface (UNI). The GMPLS UNI permits dynamic provisioning of optical transport
connections between IP routers and optical network elements in order to reduce the operational
time and administrative overhead required to provision new connectivity. The
7750 SR-7/12/12e and 7950 XRS support the role of a client side of the GMPLS UNI, with an
optical cross-connect, or photonic switch, such as the Alcatel-Lucent 1830 PSS playing the role
of the network side. Release 13.0.R1 supports the Link Management Protocol (LMP) for
managing gray Ethernet data bearers, and RSVP-TE signaling for GMPLS LSPs, over an out-
of-band IP control channel (IPCC). End-to-end protection of GMPLS LSPs using load

62 SR OS 13.0.R10 Software Release Notes


New Features

balancing and full reroute is supported. The 7750 SR-7/12/12e and 7950 XRS also support the
signaling of GMPLS LSP constraints such as the optical path, bandwidth, optical segment
protection type, and SRLG. SRLG collection is also supported. These GMPLS UNI features
support use cases including dynamic connection setup with constraints and multi-layer
resiliency. See Enhancements in Release 13.0.R4 for more information.

LDP IPv6 Using Release 13.0.R1 introduces the support of IPv6 in LDP control and data planes. The SR OS LDP
128-bit LSR-ID IPv6 implementation uses a 128-bit LSR-ID as defined in draft-pdutta-mpls-ldp-v2. The
following capabilities are supported:
• link- and targeted-LDP adjacency/session using IPv6 128-bit LSR-ID
• concurrent 32-bit LSR-ID IPv4 and 128-bit LSR-ID IPv6 LDP link adjacency and session
over the same link
• support of downstream-unsolicited (DU) label distribution
• ability to advertise and resolve unicast IPv4 FEC, unicast IPv6 FEC, mLDP IPv4 FEC
(opaque types 1, 3, and 250, with IPv4 root LSR address), mLDP IPv6 FEC (opaque types
4 and 251, with IPv4 root LSR address), and service FECs on IPv6 LDP session
• ability to advertise and resolve a unicast IPv6 FEC on a 32-bit LSR-ID IPv4 LDP session
• support of the LDP session capability advertisement TLV along with the Dynamic
Capability Announcement TLV
• global and per-peer FEC filter policies for IPv6 prefixes
• IPv6 FEC prefix origination using the fec-originate option
• configuring the local-lsr-id option for link-LDP (I-LDP) IPv6 interface and targeted-LDP
(T-LDP) IPv6 session
• LDP synchronization with IS-IS, OSPFv3 and with static IPv6 routes
• enabling BFD for T-LDP and LDP sessions
• LDP SDPs with far-end and tunnel-far-end using IPv6 addresses or a mix of IPv4 and
IPv6 addresses
• using an LDP prefix IPv6 FEC as a shortcut for IGP IPv6 prefixes (config>router>ldp-
shortcut)
• using an LDP prefix IPv6 FEC to resolve the indirect next-hop of a static IPv6 route
• Epipe VLL, VPLS, IES/VPRN spoke-interface, R-VPLS
• PW redundancy within Epipe/Ipipe VLL, Epipe spoke termination on VPLS/R-VPLS and
IES/VPRN
• mirroring service and LI
• OAM tools: sdp keep-alive, sdp-ping, sdp-mtu, lsp-ping, lsp-trace, vccv-ping and vccv-
trace for single-hop FEC128 PW
The LDP IPv6 feature is supported on all platforms with FP2- or higher-based hardware in
chassis mode D.

SRLG Weight for Release 13.0.R1 introduces the ability to specify a penalty weight associated with an SRLG. The
Bypass and likelihood of paths with links sharing SRLG values with a primary path being used by a bypass
Detour LSP or detour LSP can be configured if a penalty weight or penalty cost is specified for the link. The

SR OS 13.0.R10 Software Release Notes 63


New Features

higher the penalty weight, the less desirable it is to use the link with a given SRLG. Penalty
weights are configured in CLI using a new penalty-weight option in the config>router>if-
attribute>srlg-group group-name context.

Weighted Load- Release 13.0.R1 introduces the ability to spray flows of IGP, BGP, and static-route prefixes
Balancing over resolved to a set of ECMP tunnel next-hops proportionally to the weights configured for each
MPLS LSP MPLS LSP in the ECMP set.
Weighted load-balancing is supported in the following forwarding contexts.
• IGP prefix resolved to IGP shortcuts in the Route Table Manager (RTM) (rsvp-shortcut or
advertise-tunnel-link enabled in the IGP instance).
• BGP prefix with the BGP next-hop resolved to IGP shortcuts in the RTM (rsvp-shortcut
or advertise-tunnel-link enabled in the IGP instance).
• Static-route prefix resolved to an indirect next-hop which itself is resolved to a set of equal-
metric MPLS LSPs in the Tunnel-Table Manager (TTM).
• Static-route prefix resolved to an indirect next-hop which itself is resolved to IGP shortcuts
in the RTM.
• BGP prefix with a BGP next-hop resolved to a static route which itself resolves to set of
tunnel next-hops towards an indirect next-hop in the RTM or TTM.
• BGP prefix resolving to another BGP prefix which next-hop is resolved to a set of ECMP
tunnel next-hops with a static route in the RTM or TTM or to IGP shortcuts in the RTM.
The weighted load-balancing feature is not supported for a BGP prefix with the BGP next-hop
resolved in the TTM to RSVP LSPs (BGP shortcut).
Note that this feature does not modify the route calculation; thus, the same set of ECMP next-
hops is computed for a prefix. It also does not change the hash routine: only the spraying of the
flows over the tunnel next-hops is modified to reflect the normalized weight of each tunnel next-
hop.
As part of this feature, the static-route implementation has been enhanced to support ECMP
over a set of equal-cost MPLS LSPs. The user can allow automatic selection or specify the
names of the equal-metric MPLS LSPs in the TTM to be used in the ECMP set.
The weighted load-balancing feature is supported on all platforms with FP2- or higher-based
hardware in chassis mode D.

Enhanced Auto- Release 13.0.R1 introduces a new auto-binding framework for selecting tunnels in the Tunnel-
Binding to Tunnels Table Manager (TTM) in the following resolution contexts:
• resolution of a static route prefix using tunnels to an indirect next-hop
• resolution of a BGP prefix using tunnels to a BGP next-hop (BGP shortcut)
• resolution of RFC 3107 BGP label route prefix using tunnels to a BGP next-hop
• resolution of a VPN-IPv4 or VPN-IPv6 prefix to a BGP next-hop
The user configures the resolution option to enable auto-bind resolution to tunnels in the TTM.
If the resolution option is explicitly set to disabled, the auto-binding to tunnel is removed.

64 SR OS 13.0.R10 Software Release Notes


New Features

If resolution is set to any, any supported tunnel type in the resolution context will be selected
following the TTM preference. The following tunnel types are selected in order of preference:
RSVP, LDP, Segment Routing, BGP, and GRE. The user can configure the preference of the
segment-routing tunnel type in TTM for a specific IGP instance.
If one or more explicit tunnel types are specified using the resolution-filter option, then only
these tunnel types will be selected again following the TTM preference.
The user must set resolution to filter to activate the list of tunnel-types configured under
resolution-filter. In the context of a static route, the user can further explicitly configure the
MPLS LSP names to use for the resolution of the indirect next-hop.
The existing auto-binding commands for the above resolution contexts are deprecated; see
Changed or Deprecated Commands for more information. When a router is upgraded to Release
13.0, the commands are automatically converted into the new format.

Services The following section describes the new services features in Release 13.0.R1.

ARP/ND Snooping Release 12.0 introduced support for the proxy-ARP function for VPLS services, where IP-
and Proxy Support >MAC pairs advertised by EVPN can populate a proxy-ARP table per service, so that local ARP
requests can be responded by the SR OS node. In Release 13.0.R1, the following enhancements
have been added:
• In addition to the proxy-ARP function, a proxy Neighbor Discovery (proxy-ND) function
for VPLS services is introduced, so that local IPv6 Neighbor Solicitation (NS) messages
can be replied by the SR OS node.
• The proxy-ARP/ND table per service can be populated not only by EVPN-received IP-
>MAC entries, but also by:
− Dynamic entries, snooped from ARP/GARP/NA messages being sent by the
routers/hosts attached to local SAPs/SDP-bindings.
− Static-entries configured in the proxy-ARP/ND tables.
• If EVPN is enabled, the snooped dynamic entries or configured static entries are advertised
in EVPN MAC routes that contain the IP->MAC pairs.
• New options to enable or disable the flooding of ARP and ND packets in an EVPN network
have been added (ND includes Neighbor Solicitation (NS) and Neighbor Advertisement
(NA) packets). In an EVPN network, where all CEs connected to SAPs/SDP-bindings are
routers and they send unsolicited GARP/NA messages, disabling the flooding of ARP/ND
messages may help reduce the flooded traffic significantly. This assumes proxy-ARP/ND is
enabled in all PEs and remote PEs send unsolicited GARP/NA messages to local CEs when
they receive EVPN IP->MAC advertisements.
• A duplicate-detect mechanism is added so that an ARP/ND spoofing attack or a
misconfigured duplicated IP address can be detected. This feature will warn the user of the
presence of a duplicate IP address, and optionally will advertise an anti-spoofing MAC
address for the duplicate IP. The anti-spoofing MAC address will normally be dropped at
the ingress SAPs/SDP-bindings through user-configured filters that will block any
potential man-in-the-middle attack.
See Known Limitations for restrictions that apply.

SR OS 13.0.R10 Software Release Notes 65


New Features

MVPN: (C-*,C-*) Release 13.0.R1 introduces the support for (C-*,C-*) wildcard S-PMSI for RFC 6513- and RFC
Wildcard S-PMSI 6514-based MVPNs with mLDP or RSVP-TE in the P-instance and IPv4 PIM SSM and ASM
Support for in the C-instance.
MVPNs Wildcard S-PMSI allows the use of a selective tunnel as default tunnel. This ensures that a full
mesh of LSPs is no longer required between MVPN PEs, reducing related signaling states and
BW consumption for multicast distribution (no traffic is sent to the PEs without receivers
active). Wildcard S-PMSI MVPN deployments support existing MVPN functionalities,
including extranet, UMH redundancy, LSP templates, MPLS FRR, Multicast Source Geo-
Redundancy, and receiver-PE threshold for S-PMSI trigger (new in Release 13.0).
The SR OS implementation is compliant with RFC 6625: Wildcards in Multicast VPN Auto-
Discovery Routes. SR OS (C-*,C-*) wildcard implementation uses wildcard S-PMSI instead of
I-PMSI for a given MVPN; thus, the following processing takes place:
• the source PE advertises an I-PMSI Auto-Discovery (A-D) route without the tunnel
information present—encoded as per RFC 6513 and RFC 6514 prior to advertising
wildcard S-PMSI
• the source PE advertises an S-PMSI A-D route whose NLRI contains the (C-*,C-*)
wildcard with the tunnel information encoded as per RFC 6625
• the receiver PE joins the wildcard S-PMSI if there are any receivers present
If the source PE does not encode I-PMSI/S-PMSI A-D routes as per the above, or advertises
both I-PMSI and wildcard S-PMSI with the tunnel information present, no interoperability can
be achieved.

MVPN: Enhanced Release 13.0.R1 introduces enhanced BSR signaling for MVPNs with the wildcard S-PMSI
BSR Support for functionality. To ensure the proper BSR operation between MVPN PEs, the operator can select
Wildcard S-PMSI two BSR modes in the P-instance (config>service>vprn>mvpn>pt>inclusive):
• bsr unicast: the BSR PDUs are sent or forwarded as unicast PDUs when I-PMSI with a
pseudo tunnel interface is installed. BSR PDUs received on the I-PMSI pseudo-tunnel
interface are also processed as unicast packets—thus, no special state needs to be created
for BSR when (C-*,C-*) is enabled. This is the default and recommended mode.
• bsr spmsi: an optional full mesh of S-PMSI tunnels is created between PEs in the MVPN
to exchange BSR PDUs. This mode is optional to allow interoperability with other vendor
equipment.
Enhanced BSR support for wildcard S-PMSI currently only supports IPv4.

MVPN: Multipoint Release 13.0.R1 enhances the support for in-band mLDP signaling for IP multicast in MVPN.
LDP In-band Previously, this functionality was only supported in the Base routing instance.
Signaling • Support for IPv4 and IPv6 SSM PIM with in-band IPv4 P2MP mLDP signaling for IP
Enhancements multicast in a VPRN service as per RFC 7246: Multipoint Label Distribution Protocol In-
Band Signaling in Virtual Routing and Forwarding (VFR) Table Context.
• Support for OAM p2mp-lsp-ping for all the above in-band mLDP signaling use cases.

66 SR OS 13.0.R10 Software Release Notes


New Features

MVPN: Receiver- Release 13.0.R1 introduces a new trigger for S-PMSI instantiation. Operators can optionally
PE Threshold for enable receiver-PE-driven S-PMSI instantiation for mLDP and RSVP-TE S-PMSIs in RFC
S-PMSI Trigger 6513- and RFC 6514-based MVPNs. In addition to the existing bandwidth (BW) threshold, two
new threshold values are defined: S-PMSI receiver PE add threshold and S-PMSI receiver PE
delete threshold (expected to be significantly higher).
When a (C-S,C-G) crosses a BW threshold to create an S-PMSI tunnel, instead of the regular
S-PMSI signaling, the sender PE originates S-PMSI explicit tracking procedures to detect how
many receivers PEs are interested in a given (C-S,C-G). When the receiver PEs receive explicit
tracking request, each responds indicating whether there are multicast receivers present for that
(C-S,C-G) on the given PE (PE is interested in a given (C-S,C-G)). The source PE can thus
determine how many receiver PEs are interested in a given (C-S,C-G) and trigger an S-PMSI
creation if the number of PEs is no larger than the add threshold. The created S-PMSI tunnel is
signaled with explicit tracking, so the source PE can detect when the receiver PE number
increases and move the given (C-S,C-G) multicast flow back on a default PMSI (I-PMSI or
wildcard S-PMSI). The explicit tracking procedures follow RFC 6513 and RFC 6514 with
clarification and wildcard S-PMSI explicit tracking extensions, as described in IETF Draft:
draft-dolganow-l3vpn-expl-track-00.
See New Features in Release 13.0.R4 for more information.

EVPN for IPv6 Release 13.0.R1 brings the support of IPv6 host and IPv6 prefixes in EVPN. The system can
Host and Prefixes now send and receive MAC/IP advertisement routes that can be used along with the proxy-nd
function to optimize the neighbor discovery key functions in the service. In addition, when
ip-route-advertisement is enabled in an R-VPLS, EVPN may now advertise/process IPv6
prefixes encoded in the BGP-EVPN IP-prefix routes.

IGMP-snooping on Release 13.0.R1 adds support for IGMP-snooping in EVPN-VXLAN VPLS services. When
EVPN-VXLAN IGMP-snooping is enabled, IGMP reports will be snooped on SAPs/SDP-bindings and also on
VXLAN bindings. This feature is not supported in EVPN-VXLAN R-VPLS services.

IKEv2 Internal Release 13.0.R1 introduces a local address assignment method for IKEv2 remote-access tunnel.
Address This feature allows the system to request an IPv4 or IPv6 address from an address pool
Assignment via configured in a local DHCPv4 or local DHCPv6s server for a remote-access tunnel client. The
Local Pool address is assigned via an internal API call directly without any actual DHCP exchange. This
feature supports auth-method psk/psk-radius/cert/cert-radius/eap. For auth-method that
involves RADIUS, such as psk-radius and cert-radius, the system will perform RADIUS
authentication before address assignment, and if local address assignment is enabled, the
address information returned in RADIUS access-reply will be ignored.

GRE Tunnels over Release 13.0.R1 extends the ISA-tunnel support of IP/GRE tunneling to allow either IPv4 or
IPv6 Transport IPv6 to be used as the transport/delivery protocol for a tunnel; in previous releases, only IPv4
transport was supported. When IPv6 transport is used, the GRE-encapsulated packets have an
outer IPv6 header and the public endpoints of the tunnel are anchored by IPv6 addresses. A GRE
tunnel using IPv6 transport can carry IPv4 and/or IPv6 packets as payload.

SR OS 13.0.R10 Software Release Notes 67


New Features

IPsec • Release 13.0.R1 introduces a new certificate reload command option:


Enhancements admin>certificate>reload type cert-key-pair, which allows the user to reload a
configured certificate and its corresponding key file at the same time.
• In Release 13.0.R1, the system can optionally generate a warning message before a
certificate or a CRL expires. The amount of time before expiration is configurable via two
system wide CLI commands (certificate-expiration-warning and crl-expiration-
warning). Using the repeat command, the warning message can optionally be configured
to repeat at a specified interval.
• In Release 13.0.R1, the system supports RADIUS interim update message for the IKEv2
remote-access tunnel. The RADIUS attributes in interim-update are the same as acct-start,
except for one attribute Acct-status-type; the value of Acct-status-type in acct-start is 1;
while in interim-update is 3. In Release 13.0.R1, if accept-coa is configured, then the
system will accept the disconnect-request message (RFC 5176) and tear down the specified
IKEv2 remote-access tunnel. The identification of the tunnel could be one of following:
− Acct-Session-Id
− Nas-Port-Id + Framed-Ip-Addr/Framed-Ipv6-Prefix + Alc-IPSec-Serv-Id
− User-Name
• In Release 13.0.R1, for IKEv2 tunnels, IKEv2 IDi values (along with types) are added into
the output of the following show commands:
− show ipsec gateway tunnel
− show ipsec gateway gw-name tunnel
− show ipsec gateway gw-name tunnel ip:port
The user could also filter the output via IDi by specifying a new parameter idi-value with
the following command:
− show ipsec gateway [name name] tunnel idi-value idi-prefix
Note that idi-prefix is used as a prefix; the system will show every tunnel that has the IDi
with that prefix.
The user can also filter the output via private interface’s address type with the following
command:
− show ipsec gateway tunnel [private-address-type {ipv4 | ipv6 | dual-stack}]
This filtering is to display remote-access tunnels that are using IPv4-only, IPv6-only, or
IPv4+IPv6 (dualstack) addresses only. Without the private-address-type filter, the output
will display all tunnels.

IPsec IPv6 Release 13.0.R1 introduces the IPv6 support for IPsec tunnel encapsulation; the system allows
Enhancements IPv4 or IPv6 traffic to be encapsulated in an IPv6 IPsec ESP tunnel. IKEv1 and IKEv2 protocol
could also run over IPv6 UDP. IPv6 fragmentation and reassembly for IPv6 ESP/IKE packets
are also supported.

PW-SAP for Epipe Release 13.0.R1 extends PW-SAPs to Epipe VLL services, so that QoS policies can be managed
VLL Services at a central PE/BNG. PW-SAPs on an Epipe VLL can be mated to an Ethernet SAP or a
spoke-SDP in the same service. This release also adds the support for BGP 3107 tunnels for the
PW port, in addition to the existing RSVP LDP LSP support.

68 SR OS 13.0.R10 Software Release Notes


New Features

SAP The following enhancements have been added on QinQ ports in Release 13.0.R1:
Enhancements on • A new SAP “*.null” may now be defined in a QinQ port. This SAP will function as a
QinQ Ports default SAP for single-tagged frames in a QinQ port. It will accept single tags in the range
0 to 4095 as well as untagged traffic.
• A new SAP “*.*” may be defined in a QinQ port. It will function as a default SAP for
double-tagged frames in a QinQ port. This new SAP will accept untagged, singly-tagged,
and doubly-tagged frames with tags in the range 0 to 4095.
• SAPs type :X.0 and :X.* as well as :0.* and the new SAPs mentioned above can be
supported in the same QinQ port as well as in the same (VPLS) service.
The above three enhancements are enabled at system level by the config system ethernet new-
qinq-untagged-sap command. Note that this behavior is always enabled on the 7950 XRS and
cannot be turned off.
When a new frame arrives at a QinQ port on a system enabled for this new behavior, a SAP
lookup is performed and the frame will be assigned to the highest priority SAP that matches the
tag values encoded in the frame. When 0.*, *.null and *.* are configured on the same port, the
priority order is:
1. 0.*
2. *.null
3. *.*
For example, the SAP lookup for untagged frames will yield 0.* if the three above SAPs are
defined on the same port. If 0.* is not defined on the port, *.null will have higher priority than
*.* and will be selected.
The new *.null and *.* SAPs are supported on Epipe, PBB-Epipe, VPLS, and I-VPLS services
on access and hybrid ports or LAGs. This feature requires chassis mode D.

UP MEP and VPLS By default, an Ethernet SAP configured over a LAG will be removed from the forwarding plane
LAG SAP when the LAG is operationally down. This can affect control protocols extracted on egress,
Interaction specifically CFM UP MEPs. The process-cpm-traffic-on-sap-down command allows the
broadcast, unknown and multicast traffic to reach the egress and applicable control traffic to be
extract to and processed by the CPM/CFM.

IP Interface In previous releases, IP-interface-level statistics were not collected for the IP interface
Statistic Collection associated with an R-VPLS service.
on R-VPLS Beginning with Release 13.0.R1, IP-level statistics will be collected for the IP traffic that is
Services routed through the IP interface associated with the R-VPLS service. Layer-2 traffic that is
bridged as part of the VPLS portion of the service is not counted. The IP-interface-level
statistics are populated in the IF-MIB (IfEntry and IfXEntry tables) and TiMetra-vRtr-MIB
(vRtrIfStatsEntry table).
IP statistics are only accounted on traffic arriving on a service access point (SAP). IP level
statistics are not collected for egress multicast IP traffic that is routed through the associated IP
interface.

VCCV BFD Release 13.0.R1 adds Virtual Circuit Connectivity Verification (VCCV) using BFD (VCCV
BFD) to LDP VPLS mesh SDPs. VCCV BFD was originally introduced in Release 12.0.R4.

SR OS 13.0.R10 Software Release Notes 69


New Features

Subscriber The following section describes the new Subscriber Management features in Release 13.0.R1.
Management

Diameter NASREQ Release 13.0.R1 adds the support for Diameter Network Access Server Requirements
Authentication (NASREQ) application that can be used for subscriber-host authentication and authorization.
The stateless NASREQ implementation supports AA-Request (AAR) and AA-Answer (AAA)
messages only. Subscriber-host authentication and authorization data accepted in an AAA
message include IP configuration (address/prefix, pool names, DNS servers), framed routes,
MSAP details, retail service, subscriber ID and profile strings (such as SLA or subscriber). The
authentication data is included using existing RADIUS attributes carried as Diameter AVPs.
Diameter NASREQ authentication is supported for dual stack IPoE and PPPoE PTA in a routed
CO model.

Python Support Release 13.0.R1 adds the Python support for Diameter NASREQ application messages:
for Diameter AA-Request (AAR) and AA-Answer (AAA). See Enhancements in Release 13.0.R4 for more
NASREQ information.
Application
Messages

Diameter Multi- Diameter multi-chassis redundancy is introduced through the concept of Diameter Proxy.
Chassis Diameter Proxy is instantiated on two 7750 SR nodes; one of the 7750 SR nodes assumes the
Redundancy active state, while the other node assumes the standby state. The active Diameter Proxy
transparently passes messages between the Diameter clients and the DRA/PCRF. Only the
active Diameter proxy allows peering connections – from the Diameter client and towards the
Diameter server (DRA/PCRF). The standby Diameter Proxy does not accept or initiate any
peering connections. This concept allows the redundant pair of 7750 SR nodes to assume a
single Diameter Identity (host-name and diameter realm).
A unique system MAC per chassis is used to break the activity tie in case that both nodes assume
the same activity state (for example, recovery after MCS isolation). The system MAC is
exchanged between multi-chassis peers through Multi-Chassis Synchronization (MCS)
protocol.
Diameter Proxy is configured on both 7750 SR nodes, through a Diameter policy that can now
be configured in a proxy mode. Diameter clients (Gx, NASREQ) on both 7750 SR nodes
connect to the Diameter Proxy via another Diameter policy that is in non-proxy mode. The
connectivity between the Diameter client and the Diameter Proxy is established through IPv4
even in the case where both entities (Diameter Client and Diameter Proxy) reside in the same
7750 SR node.
Diameter multi-chassis redundancy is supported for Gx and NASREQ. Within Gx, only ESM
is supported. See Enhancements in Release 13.0.R4 for more information.

DHCP Relay on Release 13.0.R1 adds support for DHCPv4 relay on network interfaces. Highlights of this
Network Ports feature are:
• support for Python-policy
− Python module alc.dhcpv4 is supported

70 SR OS 13.0.R10 Software Release Notes


New Features

− Python module alc.dtc is supported, except for alc.dtc.setEXM(), which is not


supported
• support for only DHCPv4 packets received natively via network interfaces
• no support for DHCPv4 packets over an MPLS tunnel
• no support for lease-populate

DHCP Relay Proxy Release 13.0.R1 introduces a DHCPv4 relay proxy function enhancing the DHCPv4 relay
functionality with a mechanism to hide the DHCPv4 server infrastructure details for DHCPv4
clients. A DHCPv4 relay proxy can act as a server towards the DHCPv4 client by replacing the
Server Identifier with a local IP address.
The existing functionality to relay unicast DHCPv4 request messages is merged in the new
relay-proxy function. The relay-unicast-msg CLI command is deprecated and during a
software upgrade, automatically migrated to the equivalent relay-proxy CLI command. See
Changed or Deprecated Commands for more information.
Relay proxy can be enabled on group-interfaces and on regular interfaces in IES and VPRN
services.

IPoE Session Release 13.0.R1 introduces the concept of an IPoE session enabling single authentication and
session accounting for dual stack devices. Mid-session changes are applied to the IPoE session.
An IPoE session is a logical grouping of IPoEv4 and IPoEv6 subscriber hosts that represent the
different IP stacks of the same end device and that share all authentication data, such as
subscriber ID, SLA profile instance, or session-timeout.The grouping is based on a configurable
session key per group-interface: {SAP, MAC address} by default and can be extended with
Circuit-ID/Interface-ID or Remote-ID for N:1 deployments.
An IPoE session represents a single end-device and can have following associated IP stacks:
• a single IPv4: one DHCPv4 host
• a maximum of two IPv6 WAN: one DHCPv6 IA-NA host and/or one SLAAC host
• a single IPv6 PD: DHCPv6 IA-PD host or PD as managed route (DHCPv6)
A single authentication is performed for all subscriber hosts in an IPoE session. Re-
authentication is based on a configurable minimum authentication interval and is triggered by a
renewal of any host belonging to the session.
With session accounting, a RADIUS accounting start is generated when the first host of the
session is created and accounting stops when the last host of the session is deleted. Optionally,
triggered interim update messages can be generated when a host is deleted from the session or
an additional host is connected.

IPv6 Support for Release 13.0.R1 adds IPv6 support for IPoE hosts/sessions and PPPoE sessions terminating in
Wholesale / Retail a retail subscriber interface in an IES or VPRN service.

L2TP LAC Multi- Multi-chassis stateful redundancy on BNG is now supported for L2TP LAC to protect access
chassis Stateful and network failures including the following functionalities:
Redundancy • MCS to synchronize L2TP tunnel/session information including sequence number of L2TP
control messages with associated PPPoE sessions

SR OS 13.0.R10 Software Release Notes 71


New Features

• SRRP-aware interface route to advertise L2TP endpoint address via routing protocols
based on SRRP mastership

Tunnel Selection Release 13.0.R1 enhances the tunnel selection capability on L2TP LAC:
Enhancements on • In previous releases, only one tunnel server endpoint was supported per tag in Access-
L2TP LAC Accept RADIUS message for L2TP LAC. Release 13.0.R1 introduces the support of
multiple endpoints with the same tag value.
• Release 13.0.R1 adds a new L2TP tunnel selection algorithm, “weighted-random”, which
enhances the existing weighted-access algorithm. When there are multiple tunnels with an
equal number of sessions (equal weight), LAC randomly selects a tunnel.

NAT Version negotiation (version 1 and version 2) for PCP is now supported.

Multicast: IPv4 PIM Release 13.0.R1 introduces the support for PIM on an IES subscriber group interface for SAP-
Support for level replication. On an IES subscriber-interface, an Ethernet SAP is configured (LAG or
SAP-level physical port) under the group interface. On the SAP, a static-host is configured for connectivity
Replication on IES to a downstream Layer-3 aggregation device including PIM while multiple default-hosts can be
Group Interface configured for subscriber traffic. A single SAP with a single static-host per group interface is
supported. Locally attached receivers cannot be mixed in the list of outgoing interfaces (OIF)
with the PIM OIF on a group interface. Default anti-spoofing must be configured (IP+MAC).
The feature requires FP2- or higher-based hardware.

Local DHCPv4/v6 Release 13.0.R1 introduces the following enhancements to local DHCP server:
Server • Local DHCPv6 server:
Enhancements
− sticky lease for DHCPv6 solicited release from client
− sticky lease for local IPsec client via local address assignment
− increase in the maximum configurable days for lease-hold-time to 7305
− assignment of /128 IA_NA address without reserving the corresponding /64 block if
there is no RESERVED_NA_LEN vendor sub-option in the relay-forward message
− ability to configure multiple thresholds on pool and prefix level based on a specified
prefix length. System sends out a warning if the configured threshold is exceeded.
With threshold configured, the system also collects statistics for the specified prefix
length.
− ability to configure one or more exclude-prefixes, which are excluded from available
prefixes in the pool
• Local DHCPv4 server:
− sticky lease when the lease expires (default)
− ability to optionally enable sticky lease for solicited release and local IPsec client via
local address assignment
− sticky lease support for persistency, HA, and MCS

72 SR OS 13.0.R10 Software Release Notes


New Features

− a configurable option to allow the system to send DHCP NAK when all of the
following conditions are satisfied:
− the local DHCPv4 server receives a DHCP Request with option 50
− the result of the address-allocation algorithm is using a pool scope
− the address in option 50 is not in the result pool

ESM BGPv6 ESM BGP IPv6 peering is now supported in addition to the currently available BGP IPv4
peering. The peering session is automatically set up as the subscriber IPv6 host is instantiated.
The BGP-peering policies contain a list of parameters for the BGP peering and is passed down
from RADIUS. Individual BGP attributes that are unique to each host can also be passed from
RADIUS. If the WAN address of the host is a peering address for the BNG, both SLAAC and
DHCPv6 IA-NA addresses are supported. The peering address for the client is any reachable
loopback address on the BNG.

ESM RIP Listener RIP listener is now supported for both PPP and IPoE IPv4 ESM hosts. RIP messages sent by a
host must either be multicasted or unicasted to the destination IP address. RIP messages sent
using the subnet broadcast will be dropped by the BNG. To enable RIP listener, the host requires
a RIP policy and the group interface to be added as a RIP neighbor. RIP policies can either be
passed from RADIUS or Local User Database (LUDB) during authentication. For static host,
the RIP policy can be associated directly to the host. RIP routes are only learned from hosts and
are never sent to hosts. SRRP setups are also supported. RIP routes are never synchronized via
MCS and require relearning after a failure. MCS will only synchronize the RIP policy.

SLA-profile An SLA profile can now offer a host-limit per host type and per address-family type. Prior to
Host-limit this release, host-limit can only limit the total number of hosts that share the same sla-profile
under the same subscriber. For example, it was not possible to provide a separate limit for PPP
hosts and DHCP hosts.

IPv6 Static Host IPv6 static hosts are now supported in addition to the currently available IPv4 static hosts. For
IP-only type of hosts, there are several MAC learning mechanisms: linking to IPv4 host,
learning via host’s router/neighbor solicit, and triggered SHCV. When the SAP is configured as
a single-MAC SAP, it changes the MAC learning behavior for the IPv6 static host only. It does
not apply to IPv4 static hosts. The single-MAC feature automatically populates the IPv6 host
MAC via host’s router solicits and neighbor discoveries.

UPnP IGD Support Release 13.0.R1 introduces the support of UPnP Internet Gateway Device (IGD) v1.0 which
allows clients to dynamically create port-mapping on MS-ISA/MS-ISA2 via UPnP protocol.
This feature only works with L2-Aware NAT and supports only required actions in
WANIPConnection service. This feature does not support distributed subscriber management.

WLAN-GW/WiFi: Release 13.0.R1 provides steering of traffic received on an access VLAN or spoke-SDP from a
VLAN to WLAN- WiFi AP/AC to a WLAN-GW IOM/IMM via an internal Epipe. The benefit of this internal
GW IOM/IMM steering is that all existing features available with native soft-GRE tunnels on WLAN-GW
Steering via IOM/IMM are now available to pure Layer-2 access via VLANs or spoke-SDPs. The access
Internal Epipe SAP can be null, dot1q, or QinQ. The aggregation network can insert up to two “AP identifying”

SR OS 13.0.R10 Software Release Notes 73


New Features

VLAN tags, and the AP can additionally insert a dot1q tag, typically for identifying the SSID.
The number of AP identifying tags sent on the internal Epipe depends on the encapsulation on
the access SAP (for example, if the aggregation network inserts two AP identifying tags, and
the access SAP is configured with null encaps, then the traffic sent on the internal Epipe will
carry two AP identifying tags). The traffic on an internal Epipe is load-balanced amongst MS-
ISAs in the WLAN-GW group. The load-balancing uses a hash based on AP-identifying tags
that remain on the frame after being received on the access SAP. This ensures all traffic from a
particular AP is Epiped to the same MS-ISA. Ingress/egress QoS and filters can be defined in
an epipe-sap-template and associated with the access SAP or spoke-SDP. Egress QoS is not
applied if a retail tag is present. Both Layer-3 ESM/DSM and Layer-2 wholesale are supported
for steered traffic. In Release 13.0.R1, mobility from an AP that is reached over a VLAN or
spoke-SDP to an AP that is reached over soft-GRE or soft-L2TPv3 tunnels is not supported. See
Enhancements in Release 13.0.R2 for more information.

WLAN-GW/WiFi: Release 13.0.R1 adds the support for soft-L2TPv3 tunnels. L2TPv3 is over UDP and both IPv4
Soft-L2TPv3 and IPv6 transport is supported. The encapsulation with UDP allows NAT traversal. Soft-
Tunnel Support L2TPv3 tunnels are terminated on WLAN-GW IOM/IMM. All features supported with soft-
GRE tunnels are supported identically with soft-L2TPv3 tunnels. L2TPv3 tunnels are stateless,
and there is no support for control channel, dynamic exchange of session ID and cookie, and
L2-specific sub-layer for sequencing. A cookie received in L2TPv3 is reflected back. The AP
can encode its MAC address in an eight-byte cookie. Based on the configuration, the cookie can
be parsed to interpret AP-MAC from the least significant six (6) bytes. The mobilty between
APs reachable via soft-L2TPv3 tunnels and APs reachable via soft-GRE tunnels is supported.
There is feature and scale parity between soft-GRE and soft-L2TPv3 tunnels.

WLAN-GW/WiFi: Release 13.0.R1 adds the support for WLAN-GW features on MS-ISM. MS-ISM provides both
WLAN-GW on higher throughput and session scale compared to an IOM with MS-ISAs. There is feature parity
MS-ISM (Two for WLAN-GW between an IOM with MS-ISAs and an MS-ISM. The MS-ISA2s can be
MS-ISA2s) configured with an isa-bb image or an isa2-bb image. If it is configured with an isa-bb image,
then the session scale of an MS-ISA applies, but the higher throughput of an MS-ISA2 is
provided. This allows mixing of MS-ISAs and MS-ISA2s in the same WLAN-GW group.

WLAN-GW/WiFi: Release 13.0.R1 adds the support for mapping a UE to a VPLS instance based on configuration.
L2-Wholesale The mapping is explicitly created by assigning a Layer-2 (L2) service instance (VPLS only in
Support Release 13.0.R1) to an SSID to which the UE is connected. The SSID is represented by the
dot1q tag in the received L2 frames from the UE. A VPLS instance can be configured per VLAN
range on a WLAN-GW group-interface. This feature therefore enables L2 wholesale, where
traffic from all UEs on a particular SSID is transparently forwarded into the corresponding
VPLS instance associated with the retail ISP. UE authentication, address assignment, Layer-3
(L3) classification and QoS are managed by the retail provider terminating the subscriber. The
WLAN-GW applies split-horizon to prevent local-switching between UEs. L2 wholesale and
L3 termination are possible simultaneously on the same WLAN-GW interface, since L2
wholesale or L3 termination is a per-SSID decision. The UE MAC state in the L2-FDB on the
IOM ages out based on the local-age configured under the VPLS service. The UE state on the
MS-ISA/MS-ISA2 is removed via an idle timeout and re-established via normal MAC learning.
IP filters and QoS can be specified in a VPLS-SAP template associated with the VPLS service.

74 SR OS 13.0.R10 Software Release Notes


New Features

The UE MAC scale is limited by the number of MAC entries supported in the IOM-based L2-
FIB. The number of unique VPLS instances is limited by the maximum number of supported
VLAN ranges.

Application The following section describes the new Application Assurance features in Release 13.0.R1.
Assurance

SeGW AA Firewall ISA-AA Firewall protection feature in Security Gateway (SeGW) deployment is enhanced in
Enhancements Release 13.0.R1 to provide S1-U GTP and S1-MME traffic protection. ISA-AA in Release
13.0.R1 implements added functionality to support: SCTP chunk checking, SCTP PPID
filtering, GTP-U tunnels count and rate limiting, GTP packet sanity check – invalid reserve,
invalid reserved IE, Missing IEs, GTP message type filtering, and GTP length filtering.

Local-List URL Local-list URL filtering policy allows network operators to deploy a solution preventing access
Filtering to illegal content in the context of child protection, court order URL takedown or driven by
specific country regulations.
The list of URLs is stored locally in a file located on the system compact flash providing a cost
effective solution for this type of filtering. The list can be updated automatically and the system
supports both encrypted and non-encrypted files.

SRRP Interface In the context of an ESM SRRP deployment, the operator can define at the app-profile level if
and Suppressible the subscriber will be diverted to MS-ISA/MS-ISA2 on a per-SRRP group interface basis. This
App-Profile can be used to reduce the total number of MS-ISAs/MS-ISA2s required in the event of a High-
Availability switchover from a primary to backup SRRP node when Application Assurance is
used as a value-added service for selected subscribers.

DNS IP Cache Release 13.0.R1 introduces the dns-ip-cache feature for URL content charging strengthening.
Subscribers’ DNS responses matching a list of domain names used for content charging are used
to populate the dns-ip-cache. The system can then be configured to create app-filters matching
HTTP or HTTPS expressions as well as the IP cache, ensuring that traffic is properly classified.

OAM The following section describes the new OAM features in Release 13.0.R1.

ETH-CFM MIP Classic MIP support has been added to mesh-SDP bindings.
Support on MESH-
SDP Bindings

IP Performance Support has been added to allow for the recording of loss and availability metrics under the
Monitoring OAM-PM architecture. The operator must specifically select the appropriate record-stats
(TWAMP-Light) option to record the desired metric. By default, only delay statistics are collected. To change this
recording option an active test must be shutdown and the appropriate configuration modified,

SR OS 13.0.R10 Software Release Notes 75


New Features

then activated with the no shutdown command. It is important to remember that no shutdown
will reallocate the system memory for that test. Any statistics not collected or written to compact
flash will be lost when the memory is reallocated.

Ipipe CFM Fault Ipipe Ethernet to legacy (encap-type PPP, MLPPP and Cisco-HDLC) interworking has been
Propagation to enhanced to allow faults on the Ethernet SAP to be propagated to the legacy connection.
Legacy Activation of the Ethernet to legacy fault propagation requires the eth-legacy-fault-
notification command to be included with the Ipipe service configuration. When using
ce-address-discovery the new keep option, only available when eth-legacy-fault-notification
is enabled, must be used to ensure that the learned address on the Ethernet SAP is not flushed
when the SAP enters a non-operational state.

LLDP Port-Id- LLDP now includes the ability to select the port-id-subtype that will be carried in the port-id
Subtype field. The default remains ifIndex. The ifIndex value is required by some versions of Alcatel-
Lucent 5620 SAM to properly build the Layer-2 topology map using LLDP. Changing this
value to transmit the ifName or ifAlias in place of the ifIndex may affect SAM’s ability to build
the a Layer-2 topology map using LLDP.
LLDP System Management Address now includes support for both IPv4 (Address SubType 1)
and IPv6 (Address Subtype 2).

EFM Link Support has been added for link monitoring of frame errors and symbol errors. Symbol errors
Monitoring require specific hardware versions; contact your Alcatel-Lucent representative for the current
hardware list. Signal degrade, signal failure and the various windowing capabilities have been
included in this support. The operator can configure actions based on signal failure threshold
crossing and a number of peer notification and reception actions.

OAM-PM Event Threshold Crossing Alarms (TCA) can be configured against the various key performance
Monitoring metrics collected as part of the OAM-PM architecture. Both stateful and stateless TCA are
supported for delay, loss and availability metrics.

VXLAN Ping A new VXLAN troubleshooting tool vxlan-ping is available to verify VXLAN VTEP
connectivity. The vxlan-ping command is available from interactive CLI and SNMP.

Y.1731 ETH-LMM ETH-LMM support has been extended to UP Service MEPs and Facility MEPs (port, LAG, and
Enhancements base-router interfaces). Service MEPs and Facility MEPs are not supported over the same
resource. The operator must choose a Facility-MEP approach or a Service-MEP approach when
the underlying resource is shared. If Facility MEPs are chosen to collect the frame loss statistics
then only a single Facility MEP on that resource can collect the frame counters. If more than
one facility MEP is configured on the shared resource, then highest-level MEP must be
configured to collect frame loss statistics to avoid the artificial introduction of gain.

76 SR OS 13.0.R10 Software Release Notes


Enhancements

Enhancements
The following sections describe new enhancements in SR OS releases.

Note:
• For the list of new and updated Application Assurance protocols and applications
supported in Release 13.0.R10 and previous 13.0 releases, see the following spreadsheet
at the Alcatel-Lucent online customer support site:
SR OS 13.0 AA Protocols and Applications
The spreadsheet may also be updated between maintenance releases to reflect recent AA
protocol and application updates. To subscribe to document and spreadsheet notifica-
tions, see the online customer support site.
For a complete list of all AA protocols and applications, contact your regional support
organization.

Release 13.0.R10

Hardware • The 7750 SR-1e/2e/3e now supports the show system switch-fabric command. [215958]
• Release 13.0.R10 reduces the automatic recovery period to less than a second for a rare
condition on an FP3-based forwarding plane that may have resulted in traffic being
impacted for a few seconds. [224433]

OSPF • The OSPF routing feature set is extended so that the lsa-generate timer now governs LSA
generation for self-generated LSAs with MaxAge. Prior to Release 13.0.R10, there was a
rare condition that caused the LSA to be flooded immediately if the router received an LSA
with its own router ID because a duplicate ID had been configured in the network.
[228017]

Routing • The output of the show router interface ipv6 detail and show service id interface ipv6
detail commands now displays ICMPv6 values. [210216]

Release 13.0.R9

HW/Platform • The operational state (for example, tmnxHwOperState in SNMP) of the extension chassis
in a 7950 XRS-40 system and the operational states of equipment contained in the
extension chassis (for example, CCMs) have been changed in CLI and SNMP to return a
value of “pre-extension” when the system is in 7950 XRS-20 mode (chassis topology =
standalone). [190843]
• The CPMs on the nodes can now use the BITS input port from their mate CPM along with
the previously-supported local BITS input port. On 7950 XRS-16c/20 and the Master

SR OS 13.0.R10 Software Release Notes 77


Enhancements

chassis of the 7950 XRS-40, the CPMs can use the BITS input ports on CPM/CCM A and
B. On the extension chassis of the 7950 XRS-40, the CPMs can use the BITS input ports on
CCM C and CCM D. [213779]

BGP • Release 13.0.R9 aligns VPRN BGP out-of-memory handling with the main BGP instance
mechanisms. In prior releases, the entire VPRN instance was always shut down if BGP
running in the VPRN was unable to obtain memory to store new routes. Now, if the new
route comes from a VPRN BGP peer, only that peer is shut down. [227877, 230151]

MSDP • The multicast routing feature set is extended with MSDP routing in a VPRN for Rosen
MVPN and NG-MPVN. [188490]

NAT • SIP Application Layer Gateway (ALG) signaling sessions support up to eight (8) pinholes.
Prior to Release 13.0.R9, after the eight (8) pinholes per SIP session had been allocated, the
new request for additional pinholes would have been rejected.
Starting with Release 13.0.R9, the new requests for pinholes will be honored by deleting
the oldest pinholes in order to accommodate the new ones. The total number of pinholes
per SIP session remains at 8. [227554]

Release 13.0.R8

HW/Platform • Release 13.0.R8 introduces new, optional firmware for p20-1gb-sfp in imm-2pac-fp3 that
adds the support for IEEE 1588 Port-Based Timestamping as well as extra pre-
classification based on IPv6 DSCP markings and some EtherTypes. [199381]
• Release 13.0.R8 adds the reset-on-recoverable-error configuration option in the
config>card context on the 7750 SR-7/12/12e and 7450 ESS-7/12 platforms. When this
option is enabled, and there is a recoverable error in the forwarding path, but that recovery
action can have a traffic forwarding impact of a few seconds, the card will reset instead of
taking the recovery action. [218111]

MPLS • Release 13.0.R8 allows the configuration of a metric for a static LSP. By default, a static
LSP is assigned the maximum metric value of 16777215. [212659]

WLAN-GW • Release 13.0.R8 provides the support for seamlessly updating a UE when it moves from
one AP to another and a control packet is received from the UE with a dot1q tag that is
different than the one that the UE is currently associated with. [222804]

78 SR OS 13.0.R10 Software Release Notes


Enhancements

Release 13.0.R7

HW/Platform • Release 13.0.R7 adds the reset-on-recoverable-error configuration option for the
7950 XRS in the configure card x mda t context. When this option is enabled and there is
a recoverable error in the forwarding path with that recovery action having some traffic
forwarding impact, the XMA/C-XMA will reset immediately instead of taking the
recovery action. [213869]

NTP • The default behavior for event notification for the tmnxNtpServerChange event of the NTP
application has been changed to suppress. [218342]

Cflowd • Release 13.0.R7 introduces the new mpls-transport template-set option for Cflowd v9
and v10 collectors. This new option allows Cflowd to collect flow statistics for MPLS
traffic using only the outer transport label, EXP bit value and ingress interface as the flow
identifier. The intent of this new template is to allow the collection of flow statistics on a
core router to develop LSP usage metrics. This option is enabled by configuring one or
more v9 or v10 collectors to use the mpls-transport template for collected statistics.
Different Cflowd collectors should not be configured to use both mpls-transport and
mpls-ip templates concurrently. Doing so would result in MPLS traffic having to be pro-
cessed twice and would significantly reduce Cflowd processing rates.
This new template is configured through the following template-set command:
config>cflowd>collector>template-set {basic | mpls-ip | l2-ip | mpls-transport}
[183594]

LAG • Mixed-Speed LAG with ESM is now available for the production network. This feature
was introduced in Release 13.0.R4.

LDP • Release 13.0.R7 introduces a new global LDP configuration option legacy-ipv4-lsr-
interop to allow interoperability with third-party legacy IPv4 LSR implementations that do
not comply with RFC 5036 with respect to the processing of Hello TLVs with the U-bit set.
Configuration of this command disables the following Hello TLVs:
− Alcatel-Lucent proprietary Interface Info TLV (0x3E05) in the Hello message sent to
the peer. Disabling this Hello TLV also results in the non-generation of the Alcatel-
Lucent proprietary Hello Adjacency Status TLV (0x3E06) because the Interface Info
TLV is not sent. [214697, 218464]
− The RFC 7552 standard dual-stack capability TLV (0x701) and the Alcatel-Lucent
proprietary Adjacency capability TLV (0x3E07) in SR OS Release 13.0 and higher
releases. [217080]

IPsec • In non-resilient topologies, IPsec tunnels are no longer deleted on the master chassis when
the Multi-chassis IPsec Mastership Protocol (MIMP) session to the standby chassis is re-
established while the MS-ISAs/MS-ISA2s are rebooting on the standby chassis. [208268]

SR OS 13.0.R10 Software Release Notes 79


Enhancements

NAT • The SIP timeout value in NAT is now increased to two (2) hours. [219616, 220146]

Application • url-filter policy action for ICAP and local-filtering now uses the TLS Certificate
Assurance Common Name expression in case the Server Name Indication is not present. Prior to
Release 13.0.R7, url-filter policy would not filter TLS sessions in case the Server Name
Indication was not present. [208082]

WLAN-GW • SR OS now supports seamless “DHCP triggered” mobility. If DHCP DISCOVER or


REQUEST is seen on a different tunnel than what the current UE state points to, based on
configuration, the ESM host corresponding to the UE is seamlessly updated. [219748]

Scaling The scaling numbers have increased for the following areas. Contact your Alcatel-Lucent
representative for details:
• Subscriber Management: ESM-based dynamic BGP peers per system [215614]

Release 13.0.R6

HW/Platform • On the 7950 XRS, when there had been a fail-on-error condition due to a low-level event
on an XMA or C-XMA, the XCM itself was taken out of operation. An XMA or C-XMA
sharing the same XCM would also have become operationally down. Starting with Release
13.0.R6, fail-on-error for any low-level event on the XMA or C-XMA will be limited to
only that XMA or C-XMA instead of the whole XCM being taken out of operation.
Important notes:
− to enable this new behavior, fail-on-error must be configured in the
config>card>mda context
− the fail-on-error function will no longer be active on the 7950 XRS if it is only
configured in the config>card context [199185]
• Release 13.0.R6 introduces a user-configurable enhancement to down-on-internal-error
that allows the user to turn-off the laser on the impacted port. In some scenarios, this speeds
up redundant path switchover, especially when higher-layer OAM functions are not used or
enabled. The behavior to re-enable the laser and clear the error condition has not been
changed, which still requires that the port be toggled operationally (shutdown/no
shutdown). [205316]
• SR OS includes the display of the virtual machine UUID to the output of show system
license on virtualized systems. The virtual machine UUID is also included in the output of
the show card slot number {[1..10] | A | B} detail command. [209653]

System • The configurable, alternative prioritization scheme that has been introduced for extracted
control plane traffic is now available for the production network. This enhancement was
introduced in Release 13.0.R5.

80 SR OS 13.0.R10 Software Release Notes


Enhancements

DHCP • Release 13.0.R6 introduces a new format for circuit-id/remote-id of DHCPv4 snooping on
a VPLS SAP. This new format allows the user to configure a hexadecimal string as the
value of the circuit-id/remote-id. [193399]

IS-IS • The output of the show router isis command has been extended to show the instance name
in the headers. [207574]
• For the IS-IS implementation of the IGP shortcuts feature, as described in RFC 3906, when
IS-IS performs an IP-reachability computation following that of the SPF tree, nodes and
prefixes downstream of a tunnel endpoint node will now inherit only the direct tunnels used
to reach the endpoint node when the latter is a parent node.
Prior to Release 13.0.R6, while IS-IS used only the direct tunnels to reach the endpoint
node and prefixes owned by the endpoint node, it computed all possible ECMP paths to
reach prefixes and nodes downstream of a tunnel endpoint. These ECMP paths included
those using direct tunnels terminating on the endpoint node, tunnels terminating prior to it,
and IP next-hops up to the router ecmp value. [211050]

BGP • General Support for Dynamic BGP Sessions is now supported for the production
environment. This feature was introduced in Release 13.0.R5.

MPLS • Release 13.0.R6 introduces the ability to configure the TTL of GMPLS UNI IPCC packets
(RSVP and LMP). This allows the use of a Layer-3 data communication network with
more than one hop between an SR OS router and an adjacent UNI-N node. [214242]

IP Multicast • The multicast ECMP hashing feature configured with mc-ecmp-hashing-enabled is


enhanced with the rebalance option. When this option is enabled, the router rebalances
flows to newly added links immediately instead of waiting until they are pruned. [150739]
• The multicast routing features for IGMP, MLD, PIM, and MSDP, are extended to accept a
source-address prefix-list-name instead of a single IP address. Using a prefix-list instead
of multiple policy statements simplifies and reduces the number of routing policies.
[166117, 211839]

QoS • Prefix lists for QoS policies applied to the ingress and egress of an SLA profile can now be
used in the production network. This feature was introduced in Release 13.0.R4.

Services • EVPN multi-homing is now available for the production network. This feature was
introduced in Release 13.0.R4.
• PBB-EVPN multi-homing in I-VPLS and Epipe services is now available for the
production network. This feature was introduced in Release 13.0.R4.

IPsec • An optional IPsec-gateway name parameter has been added to the show ipsec gateway
tunnel private-address-type private-address-type command: show ipsec gateway name
name tunnel private-address-type private-address-type. This updated command provides
an output that shows the IPsec tunnels with a specified type of private address that
terminate on a specified IPsec-gateway. [213563]

SR OS 13.0.R10 Software Release Notes 81


Enhancements

Mirroring/Lawful • Routable Lawful Intercept encapsulation (config>mirror>mirror-dest>encap>layer-3-


Intercept encap) is now supported for IPv4 destinations reachable over a spoke interface using a
LDP IPv6 FEC.
• Segment-routing tunnels over IS-IS and OSPF can now be used for remote mirroring.
[214550]

L2TP • Release 13.0.R6 adds the support for sending AVPs for L2TP tunnels in ESM session
accounting. It also allows to send Acct-Tunnel-Connection value in a different format
including local tunnel-ID, local session-ID, remote tunnel-ID, remote session-ID, and
Calling-Number. [208200]

NAT • The NAT-related logger event 2021 is changed so that each 2012 “map” event is matched
with a 2021 “free” event, rather than sending a summarization 2021 log for the last port
block of the subscriber which does not contain the last freed port-block. [196154]
• The outside IP and port allocation algorithm has been enhanced for L2-Aware NAT. Prior
to this change, a just-released outside IP and port for a subscriber that was being deleted
could have been immediately reallocated to a new subscriber. Corresponding RADIUS
logging could have resulted in an Accounting-Stop and Accounting-Start within the same
second, reporting the same outside IP and port for different subscribers. External systems
could have wrongly interpreted this as an outside IP and port overlap condition. [217088]

sFlow • In Release 13.0.R6, sFlow has been enhanced to support the 7750 SR-7/12 systems with
CPM3/CPM4/CPM5 on multi-core line cards. [201089]

Application • The 13.0 AA Protocols and Applications for the 7450 ESS and 7750 SR spreadsheet has
Assurance been added to the SR documentation suite. This spreadsheet may be updated between SR
maintenance releases to reflect recent AA protocol and application updates. A link to the
document is also provided at the beginning of the Enhancements section.

OAM • Log and debug messages relating to G.8032 Ethernet Ring Protection Switching have been
modified to reference paths a/b instead of paths 0/1. [213859]
• Release 13.0.R6 introduces the support for VCCV BFD on the 7450 ESS-6/6v. [214672]

Scaling The scaling numbers have increased for the following areas. Contact your Alcatel-Lucent
representative for details:
• sFlow can now be configured on an increased number of SAPs per port. [201089]
• The number of DHCPv6 (IA-NA, IA-PD) lease-states per regular IES or VPRN interface
(non-subscriber interfaces) with lease-populate enabled. [205939]

82 SR OS 13.0.R10 Software Release Notes


Enhancements

Release 13.0.R5

RADIUS • Authentication Requests are no longer forwarded to a RADIUS server that is in state
“overload” because the “pending-requests-limit” value is exceeded. [212937]

System • A configurable, alternative prioritization scheme has been introduced for extracted control-
plane traffic. The new scheme can be enabled (on a per-FP basis with the CLI init-extract-
prio-mode command) to initialize the drop priority of extracted Layer-3 control traffic
based on the QoS classification of the packets. This is useful in networks where the DSCP
and EXP markings can be trusted as the primary method to distinguish, protect, and isolate
“good” terminating protocol traffic from unknown or potentially harmful protocol traffic,
instead of using the rate-based distributed CPU protection (DCP) and centralized CPU
protection traffic marking/coloring mechanisms (such as out-profile-rate and exceed-
action low-priority). See Enhancements in Release 13.0.R6 for more information.
• Support for APEQ provisioning has been added to the 7750 SR-12e platform to allow
management of the APEQ input power mode through the addition of the following
commands:
− show peq
− configure system power-management peq
− show chassis power-management [206787]

Routing • OSPF with segment routing and multiple areas for the ABR role is now available for
production networks. This feature was introduced in Release 13.0.R4.
• The ICMP/ICMPv6 packet processing rate on transit packets that generate an exception
condition has been increased on 7450 ESS-7/12 and 7750 SR-7/12/12e platforms with
Multicore-CPU and FP3-based IMMs/IOMs, and on 7950 XRS platforms. [207965]

OSPF • Release 13.0.R5 introduces the tools dump router router ospf instance area-range
command, which shows the dynamic parameters and the aggregated routes of an OSPF
area-range. [212766]

MPLS • Release 13.0.R5 adds the support for a new tools dump test-oam command on the tail-end
of an LSP to display statistics related to LSP BFD. A new MIB object is also added that
shows ongoing LSP BFD bootstrap retry counts. [211899]

Application • Release 13.0.R5 supports a new version of the isa-aa.tim file that enables new and updated
Assurance protocol signatures and applications. The new and updated protocols in this release are

SR OS 13.0.R10 Software Release Notes 83


Enhancements

shown in the table below. For a complete list of the Release 13.0 AA identification
capabilities (protocols and applications), contact your regional support organization.

Table 17. New and Updated AA Protocols in Release 13.0.R5


Protocol Status Comments
DNS Tunnel new Provides detection of DNS Tunneling. DNS tun-
neling can be used to bypass WiFi captive portal
access restrictions and allow subscriber access to
Internet. It can also be used to bypass content
charging rules.
Speedtest new Provides detection of the Speedtest.net Internet
access analysis service.
Bittorrent updated Provides improved detection of Bittorrent traffic
over Teredo.
eMule updated Provides improved detection of eMule over UDP
when connected to the Kad network.
Google Talk updated Provides improved detection of Google Talk when
initiated with TCP Fast Open.
LINE updated Provides improved detection of LINE voice and
video calls over UDP.
Lync updated Provides improved detection of Microsoft Lync
over TCP.
Skype updated Provides improved detection of obfuscated Skype
over UDP.
TLS_HTTP2 updated Provides improved detection of TLS_HTTP2 when
initiated with TCP Fast Open. These flows were
previously detected at TLS.
WhatsApp updated Provides improved detection of WhatsApp traffic
over TCP.
YouTube updated Provides improved detection of YouTube live event
streaming over RTMP.

• Release 13.0.R5 includes TCP Fast Open support for DPI high-touch features such as
HTTP-Enrichment, In-Browser Notification, HTTP-Redirect, URL-Filter, URL-List and
Match-all. TCP Fast Open is an extension to TCP used to speed up the opening of
successive sessions between a client and server by sending data during the initial three-way
TCP handshake.

Release 13.0.R4

Hardware • 10 GBase tunable DWDM SFP+ (low-power 1.5 watts MSA-compliant) is now supported
on the SFP+ based cards. [200880]
• Release 13.0.R4 introduces a new firmware for the control path on 7750 SR-a4 and SR-a8
which unlocks scaling and performance improvements at the control-plane layer. The

84 SR OS 13.0.R10 Software Release Notes


Enhancements

firmware upgrade will take place automatically on the first attempt to boot Release
13.0.R4. Note that the firmware upgrade process will take longer than a simple software
upgrade so maintenance window plans may need to be adjusted accordingly. Also note that
care must be taken to avoid any resets or removal/insertion of any assemblies in the system
while the upgrade is taking place or cards may be rendered inoperable.
• In Release 13.0.R4, both ingress and egress XPL error trap counts will be displayed under
show mda detail. [210513]

System • A new configuration item under the config>system>security>source-address hierarchy is


available to allow an operator to specify the source IP address to be used for ICMP and
ICMPv6 error messages sourced from the node. This is supported in the base routing
instance and in VPRN services (under the config>service>vprn>source-address context).
If this item is not configured, the default behavior is that the node will source
ICMP/ICMPv6 error messages from the interface on which the packet that triggered the
message was received. [143038]
• Release 13.0.R4 enhances the load balancing hash algorithm configured with system-ip-
load-balance to also work with pure Layer-2 traffic. Previous releases use this algorithm
for Layer-3 traffic only. [179818]
• The per-SNMP community source IP address validation feature has been enhanced to
operate with VPRN SNMP communities and USM communities. As of Release 13.0.R4, a
src-access-list can be referenced by a VPRN SNMP community or an SNMP USM
community. [204677]
• A new min-delay parameter has been added to the Event Handling System to prevent a
script from running too often.

Hybrid OpenFlow • Release 13.0.R4 introduces interface support enhancements. OpenFlow (OF) is enabled on
Switch (H-OFS) an interface by assigning an IPv4 and/or IPv6 line card filter policy with H-OFS instances
embedded in that policy either directly or via the active system filter policy. The following
new CLI contexts, in addition to those listed for Release 13.0.R1, support an assignment of
IPv4 and/or IPv6 line card filter policies with embedded H-OFS instances:
− access interfaces:
− config>service>ies>if>spoke-sdp>ingress>filter
− network interfaces:
− config>service>vpls>mesh-sdp>ingress>filter (requires H-OFS with switch-
defined-cookie enabled)
− config>service>vpls>spoke-sdp>ingress>filter (requires H-OFS with switch-
defined-cookie enabled)
• Release 13.0.R4 introduces an enhanced statistics processing for an SR OS H-OFS. The
processing allows faster flow table statistics retrieval due to the use of the new CPM-based
ACL statistics cache. An OF controller statistics request that is translated to a bulk request
returns the CPM-cached values. An OF controller statistics request that is translated to a
single flow request returns values read real-time from hardware. The ACL CPM cache is
being refreshed in a background using a non-configurable refresh interval. On a High-
Availability switchover, a CPM cache needs to be rebuilt; as such, some initial bulk
requests may require another hardware read to return the statistics and repopulate the
cache. Note that prior to Release 13.0.R4, the returned statistics values were always read

SR OS 13.0.R10 Software Release Notes 85


Enhancements

real-time from hardware, which could have led to a degraded performance at very large OF
switch scale.
• Release 13.0.R4 adds the ability to program *.NULL and *.*VLAN ID match and
forwarding to VPLS SAPs using the Hybrid OpenFlow Switch (H-OFS). [199457]
• Release 13.0.R4 adds the ability to program a new PBR action forward next-hop ip-
address router router-instance using the OpenFlow protocol (see the Filters: PBR
enhancement in Release 13.0.R4 Enhancements for more information).

NETCONF/YANG • A new revisions.txt file is included in the YANG subdirectory of the SR OS image
distribution to indicate the revision of each Alcatel-Lucent YANG module associated with
the release. [207707]
• An unknown XML namespace or prefix declaration is now ignored in NETCONF requests
instead of generating an error. [209637]

Routing • In Release 13.0.R4, the cpe-check option for static routes is expanded to support an IPv6
target. This option initiates a background IPv6 ping to test the reachability to the associated
IPv6 target. The operational state of the static route will be brought down if the IPv6 ping
fails to the configured target. If the cpe-check option is configured for a static route, the
administrator can also specify a padding-size value up to 16384 bytes. [140022]
• In Release 13.0.R4, the IP interface command delayed-enable functionality has been
extended to the following IP interface types.
− config>router>interface
− config>service>ies>interface
− config>service>ies>redundant-interface
− config>service>ies>subscriber-interface
− config>service>vprn>interface
− config>service>vprn>redundant-interface
− config>service>vprn>network-interface
− config>service>vprn>subscriber-interface
− config>service>vpls>interface
The delayed-enabled function is also supported in association with VPRN and IES IP Tun-
nel, GMPLS loopbacks and Unnumbered MPLS-TP interfaces.
This option allows for a configurable timer which delays the enabling of the associated IP
interface by the specified amount of time. The configurable range is 1-1200 seconds.
[191826]
• Release 13.0.R4 adds a new set of optional parameters to the static-route configuration to
allow an exponential back-off behavior for static routes that are flapping. If configured, a
route that transitions from up to down and then up again before the current back-off
interval has expired would be held down (operationally down) for increasing periods, up to
the maximum hold-down value. This behavior will mitigate the effects of an unstable static
route that is flapping due to either traffic or link instability. [193468]

86 SR OS 13.0.R10 Software Release Notes


Enhancements

DHCP • Logging for DHCP errors has been enhanced. A DHCP server that failed to assign an
address to the subscriber host will log the host's MAC or DUID. A trap will also be sent if
a DHCP offer/advertise expires. [198158]
• A DHCPv4 Python script configured in a group-interface DHCPv4 context will now also
act on DHCPv4 release messages originated by ESM on behalf of a DHCP client attached
via that group-interface. [203170]

IS-IS • Release 13.0.R4 adds a new IS-IS option (config>router>isis>ignore-narrow-metric) to


force IS-IS to ignore links with narrow metrics when wide-metrics support has been
enabled. [163873]
• Release 13.0.R4 adds the support for IS-IS purge originator identification (POI) as
described in RFC 6232 and RFC 6233. A POI TLV, which contains the system ID of the
router that generated the purge, is added to purges. This addition simplifies
troubleshooting, and determining what caused the purge. [165786]
• The IS-IS Single Instance Router in a Non-Zero Instance feature is now available for the
production network. This feature was introduced in Release 13.0.R1.

OSPF • The show router ospf and show router ospf3 commands are extended with an all option
to show all configured OSPF instances. The command output is also extended to show the
instance ID in CLI output headers. [182039]
• The OSPF routing feature set is extended to limit the maximum number of LSAs that OSPF
can learn from another router in order to protect the system from a router that accidentally
advertises a large number of prefixes. When the number of advertised LSAs reaches the
configured percentage of the limit set with rtr-adv-lsa-limit, an SNMP trap is sent. If the
limit is exceeded, OSPF goes into overload. The overload-timeout option allows the
administrator to control how long OSPF is in overload as a result of the LSA limit being
reached. At the end of this duration of time, the system automatically attempts to restart
OSPF, or can be configured to stay in overload until cleared by the administrator.
This feature should be used together with the OSPF export-limit, which will limit the num-
ber of prefixes that can be exported from other protocols into OSPF. [182659]

BGP • Release 13.0.R4 changes the BGP implementation to handle unresolved routes more
consistently. Previously, for some address families, an unresolved “best” route was not
withdrawn when next-hop-self was in effect. Now, it will always be withdrawn under these
circumstances, regardless of the address family (IPv4, IPv6, label-IPv4, label-IPv6, VPN-
IPv4, VPN-IPv6). [172163]
• Release 13.0.R4 adds the ability to configure VPRN to be part of a BGP confederation to
import and export IP-VPN routes with confederation information included in their AS path
attributes. [186635]

BGP-EVPN • The EVPN-VXLAN BGP encoding in Release 13.0.R4 is now compliant with draft-ietf-
bess-evpn-overlay. Prior to Release 13.0.R4, the VXLAN Network Identifier (VNI) was
encoded in the Ethernet Tag field of the EVPN routes type 2, 3 and 5 following an early
version of the draft. In Release 13.0.R4, the VNI is now encoded in the Label field of the
EVPN routes as per the current draft. The sending and receiving behavior is described
below.

SR OS 13.0.R10 Software Release Notes 87


Enhancements

− When sending EVPN-VXLAN routes:


− the Ethernet Tag will now be zero (0)
− the VNI value will be encoded in the 24-bit Label field of the EVPN routes (this
field is called “Label1” in MAC/IP routes)
− When receiving EVPN-VXLAN routes, that is, EVPN routes with VXLAN value in
the RFC 5512 BGP tunnel encapsulation extended community, the VNI is extracted
based on the following rules.
− If the Label field and Ethernet Tag are both zero (0), the VNI selected to send
VXLAN packets will be the locally configured VNI value.
− If the Label field is non-zero and the Ethernet Tag is zero, the VNI will be equal
to the 24-bit value encoded in the Label field.
− If the Label field is zero and Ethernet Tag is non-zero, the VNI will be equal to
the value in the Ethernet Tag.
− If the Label and Ethernet Tag fields are both non-zero, the VNI will be equal to
the 24-bit value in the Label field. [201082]
• A new CLI command has been added so that the user can configure the EVPN
encapsulation for EVPN routes (MAC/IP, Inclusive Multicast Ethernet Tag, IP-prefix
routes and AD per-EVI routes) received without an RFC 5512 BGP tunnel encapsulation
extended community. Based on the configured value in
config>router>bgp>neighbor#def-recv-evpn-encap [mpls|vxlan], BGP will treat the
received EVPN routes without an encapsulation as either mpls or vxlan. The default value
is mpls.

BGP VPWS • The configuration of a GRE tunnel using static MPLS labels is now supported within a
single-homed BGP VPWS service; however, BGP multi-homing using an active and a
standby pseudowire to a pair of remote PEs is not supported. [203685]

MPLS/RSVP • The GMPLS UNI feature was released in Release 13.0.R1 for laboratory environments
only. This feature is now available for the production network.

LDP • In Release 13.0.R4, it is no longer possible for an MPLS label control protocol
(RSVP/LDP/BGP) to be affected when another MPLS label control protocol has MPLS
label resource issues on the IOM/IMM/XCM. [190080]

LDP IPv6 • The following LDP capabilities are now supported with LDP IPv6:
− overriding address advertisement using an address export policy when the LSR peer
did not advertise the dual-stack capability TLV
− LDP Downstream on Demand (DoD) label distribution
− LDP IPv6 session overload capability
− aggregate-prefix-match option
− FRR protection for a LDP IPv6 FEC
− mcast-upstream-frr option
− LDP IPv6 peer authentication using MD5

88 SR OS 13.0.R10 Software Release Notes


Enhancements

− LDP IPv6 prefix FEC limit


− LDP IPv6 Hello reduction
− LDP graceful restart helper

PIM • For IPv6 PIM SSM/ASM in C-instance, the receiver-PE threshold for S-PMSI trigger
feature, introduced in Release 13.0.R1, is now available for the production network.
• IPv6 MCAC for PIM and MLD is now available for the production network. This feature
was introduced in Release 13.0.R1.

QoS • A set of show commands have been added to display the QoS information relating to
aggregate rate-limit configurations (show qos agg-rate). [180781]

Filters • Release 13.0.R4 allows the operator to specify a direct/indirect next-hop IPv4/IPv6 address
and a target VRF instance for a PBR action in an IPv4/IPv6 filter policy. Prior to Release
13.0.R4, only a next-hop or a target VRF could be configured in the filter policy, although
next-hop and target VRF could be used for PBR using redirect policies. The new action is
supported in IPv4 and IPv6 filters.
• Release 13.0.R1 introduced the support for IPv4 and IPv6 filter policies on network ports
for VPRN services. In Release 13.0.R4, the filter functionality is available with the newly-
introduced per-prefix VPRN service label mode feature.

Services General • Release 13.0.R4 adds the ability to link a PW port state to the state of an oper-group, such
that if the oper-group goes down, the SDP binding for the PW port will also go
operationally down. [187673]
• In Release 13.0.R4, a new SDP option has been added which disables the setting of the do-
not-fragment bit in the IP header of GRE encapsulated service traffic.This feature is only
applicable to GRE SDPs and will be applied to all service traffic using the associated GRE
SDP. This option is enabled through the CLI command config>service>sdp>allow-
fragmentation. This option is not enabled by default. This option should only be enabled if
an external device is capable of re-assembiling the fragmented GRE traffic before it is
delivered to the far-end service router. [201894]
• In case of a MAC-move rate exceeded event in an I-VPLS service, the alarm message will
display only the B-VPLS service-ID. With this enhancement, the I-VPLS service-ID will
also be displayed. [210519-MI]

Subscriber • In Release 13.0.R4, the minimum quota for RADIUS-based credit control is reduced from
Management 900 seconds to 1 second for time credit and from 100 Mbytes to 1 byte for volume credit.
These minimum values are not realistic deployment values for multiple reasons, such as
effective statistics sampling period, statistics processing time, RADIUS message load, or
subscriber scale. For typical deployment scenarios, it is not recommended to implement
credit control quota values smaller than 60 seconds for the time quota, and for volume
quota, it is not recommended to use values smaller than the volume that can be consumed
in 60 seconds for that category (this is a function of number of queues and policers
monitored and their respective rates).

SR OS 13.0.R10 Software Release Notes 89


Enhancements

• Python support for Diameter NASREQ application messages (AAR/AAA) is now fully
supported. This feature was introduced in Release 13.0.R1.
• Release 13.0.R4 adds the ability to configure an authentication policy in WPP LUDB,
which is used for Web Portal Protocol (WPP) authentication if returned. The authentication
policy on group-interface is optional when WPP LUDB is configured; it will only be used
by WPP if there is no authentication policy returned from WPP LUDB. [182354]
• Release 13.0.R4 provides the support for subscriber-profile overrides via COA for
parameters of tier-1 scheduler in scheduler-policy referred to from the subscriber-profile.
See Limited Support Features and Enhancements for more information. [192710]
• The Web Portal Protocol (WPP) has been enhanced with following capabilities:
− the number of re-transmission for NTF-LOGOUT packet is configurable via CLI
− the number of re-transmission for ACK-AUTH packet is configurable via CLI
− re-transmission is configurable via CLI
− a clear command is added to remove WPP hosts in logout state [198574]
• Diameter multi-chassis redundancy is now available for the production network. This
feature was introduced in Release 13.0.R1.

VPLS • Release 13.0.R4 adds the ability to configure an IGMP-snooping mrouter port in the VPLS
of a Routed-VPLS service to its IP interface which sends all IGMP joins (and multicast
traffic) to the VPLS-service IP interface. This is useful to achieve a faster failover in
scenarios with redundant routers where multicast traffic is sent to systems on the VPLS
side of their Routed-VPLS services and IGMP-snooping is enabled in the VPLS service.
• When PIM-snooping is enabled within a VPLS service, all IP multicast traffic and PIM
messages will now be sent to any SAP or SDP binding configured with an IGMP-snooping
mrouter port. This will occur even without IGMP-snooping enabled. [184851]

VRRP/SRRP • Release 13.0.R4 adds SRRP/VRRP to the list of protocols that generate a
tmnxEqDataPathFailureProtImpact event when they are impacted by a data-path recovery
action. [208825]

IPsec • Release 13.0.R4 adds the ability to specify a domain name or an IPv4/v6 address as
subjectAltName in certTemplate of CMPv2 initial-registration request or certificate-
request. It also adds IPv6 address support for the admin certificate gen-local-cert-req
command. [185340]
• Release 13.0.R4 introduces the support for IKEv2 remote-access tunnel DHCP-based
address assignment. Prior to Release 13.0.R4, configuration of relay-proxy on private IPsec
tunnel interfaces, although not blocked in CLI, was not supported. [209178]

MC-IPsec • In Release 13.0.R4, upon switchover, the new master chassis will be polling for incoming
IPsec traffic on both public and private sides; only after receiving traffic, it will force a
CHILD_SA rekey, and the tunnels receiving ESP traffic will be rekeyed before other
tunnels.

90 SR OS 13.0.R10 Software Release Notes


Enhancements

• In Release 13.0.R4, the master and standby chassis will now use two different ESP SPI
ranges; Multi-chassis IPsec Mastership Protocol (MIMP) will decide which node uses
which range.

Application • Release 13.0.R4 supports a new version of the isa-aa.tim file that enables new and updated
Assurance protocol signatures and applications. The new and updated protocols in this release are
shown in the table below. For a complete list of the Release 13.0 AA identification
capabilities (protocols and applications), contact your regional support organization.

Table 18. New and Updated AA Protocols in Release 13.0.R4


Protocol Status Comments
Facebook_RTP new Provides detection of Facebook voice traffic over
RTP.
NDMP new Provides detection of Network Data Management
Protocol over TCP.
QUIC new Provides detection of QUIC (Quick UDP Internet
Connections) over UDP. QUIC is a new communi-
cation protocol introduced by Google in Chrome
using UDP instead of TCP to transport
HTTP/HTTPs content.
SPDY new Provides detection of unencrypted SPDY over TCP.
Symantec Backup new Provides detection of Symantec Backup Exec over
TCP.
Taobao new Provides detection of Taobao over HTTP, SPDY
and TLS.
TLS_HTTP2 new Provides detection HTTP2 traffic over TLS. Prior
to the introduction of this new protocol HTTP2
encrypted flows were classified as TLS.
WhatsApp_RTP new Provides detection of WhatsApp voice traffic over
RTP.
Tango updated Provides improved detection of Tango over UDP.

• Release 13.0.R4 introduces QUIC protocol classification and QUIC SNI (Server Name
Indication) expression match capability in app-filter by reusing the existing http-host
match criteria. QUIC SNI expressions are also exported in the Cflowd comprehensive
records hostname field and recorded in the http-host-recorder. QUIC is a new
communication protocol introduced by Google in Chrome using UDP instead of TCP to
transport HTTP/HTTPS content. A significant percentage of the traffic generated by
Chrome browser to Google servers now uses this protocol; therefore, it is recommended to
upgrade the AA software using the AA Signatures Upgrade Procedure to keep the detection
up to date.
• Release 13.0.R4 supports the detection of existing protocols when TCP Fast Open is used
to initiate the TCP session. TCP Fast Open is an extension to TCP used to speed up the
opening of successive sessions between a client and server by avoiding the three-way TCP
initial handshake.
• Support for AA per-subscriber statistics for Distributed Subscriber Management (DSM)
AA subscriber types is now supported in CLI configuration and show commands. This

SR OS 13.0.R10 Software Release Notes 91


Enhancements

provides the support for application-group, Application and Charging Group counters on a
per-DSM subscriber basis. [205980]
• The ICAP url-filter policy now provides the capability to include an optional custom-x-
header field to the ICAP requests sent to the ICAP server. A predefined ASO characteristic
value is used to populate this new field allowing ICAP filtering policies on the server side
based on ASO value rather than subscriber name and effectively allowing traffic filtering
based on predefined packages to simplify the policy applicable to AA subscribers.

Cflowd • Release 13.0.R4 adds a tools command to display the contents of the Cflowd active flow
cache. The new command, tools dump cflowd cache, can display either the complete
contents of the active flow cache or an aggregated view which aggregates the flow entries
based on IP source and destination addresses, protocol and port numbers.
The CLI syntax is: tools>dump>cflowd>cache [all | aggregate] family{ipv4 | ipv6} {src-
dst-proto | src-dst-proto-port}. [199420]

OAM • An OAM-PM TWAMP-Light test session supports the configuration of the UDP source
port with config>oam-pm>session>ip source-udp-port udp-port-number in the range of
[64374–64383] to support Distributed TWAMP models (separation of Control-Client and
Session-Sender).
This command should only be used when deploying a distributed TWAMP model. This
command should not be used if the test functions only include native TWAMP-Light net-
work elements and no TWAMP TCP control channel. TWAMP-Light does not utilize the
use of TWAMP TCP Control channel. [191657]
• Locally-generated ETH-CFM PDUs generated from UP MEPs, vMEPs and MIPs can
utilize the EVPN Terminations as transport for EVPN services. The command cfm-mac-
advertisement is required to ensure that the locally-configured UP MEP, vMEP and MIP
MAC addresses on SAP, spoke-SDP and mesh-SDP are distributed through BGP. Shutting
down the MEP does not trigger a MAC withdrawal advertisement; the MEP’s deletion is
required for that action. [197962]
• The following OAM tools are now supported with a segment-routing tunnel:
− ping and traceroute within GRT
− SDP-level OAM tools: sdp-ping and sdp-mtu

Scaling The scaling numbers have increased for the following areas. Contact your Alcatel-Lucent
representative for details:
• IPsec scale improvements
• IPsec tunnels per 7750 SR-c12 chassis
• Filter policy line card limits
• Redirect policy system limits
• OpenFlow per-service/interface flow table rule limit
• The combined SSH and Telnet session limit
• Subscriber management host scale per:
− system (running CPM5, chassis mode D)
− line card (on FP2- and higher-based line cards)

92 SR OS 13.0.R10 Software Release Notes


Enhancements

See Software Upgrade Notes and Known Limitations for more information.
• Event-Handling System (EHS) scale improvements by increasing the number of CLI
scripts, script policies and log filters
• Video ISA session scale improvements using MS-ISA

Release 13.0.R3

HW/Platform • The 1588 port-based timestamping feature on the p10-10g-sfp and p6-10g-sfp MDAs was
released in Release 12.0.R6 for laboratory environments only. This feature on these MDAs
has been modified to now support deployment in production networks. A hard reset of the
MDA is required to activate the modification. See also 202916 in Resolved Issues.

Routing • The output of show router tunnel-interface command is enhanced with the display of the
P2MP LSP type (RSVP or LDP) with which the interface is associated. [189407]
• Release 12.0.R4 introduced a change in CLI output to display route tags configured in
routing policies in hexadecimal instead of decimal format. In Release 13.0.R3, route tags
are now displayed in decimal format in policy-statement from and action accept
statements, and in the RIP, RIPng and OSPF show command output. Decimal format for
route tags is now used consistently in all CLI input and output. [193831]

BGP Multi-homing • The BGP multi-homing algorithm has been optimized with respect to the operation of the
site-min-down-timer as follows:
− If the site goes down on the designated forwarder but there are no BGP multi-homing
peers with the same site in an UP state, then the site-min-down-timer is not started
and is not used.
− If the site goes down on the designated forwarder but there are no active BGP multi-
homing peers, then the site-min-down-timer is not started and is not used.
− If the site-min-down-timer is active and a BGP multi-homing update is received
from the designated forwarder indicating its site has gone down, the site-min-down-
timer is immediately terminated and this PE becomes designated forwarder if the
BGP multi-homing algorithm determines it should be the designated forwarder.
[195483]
• The internal system timing mechanism related to BGP multi-homing has been enhanced to
use smaller intervals. This change does not affect the user-configurable timers; however, it
will improve the resolution experienced as part of the timing mechanism. [197222]

LDP • A new LDP Hello Adjacency Capability advertisement is introduced to enable or disable
the resolution of a FEC type over a given LDP interface. The following FEC types are
supported: unicast IPv4 FEC, unicast IPv6 FEC, mLDP IPv4 FEC (opaque types 1, 3, and
250, with IPv4 root LSR address), mLDP IPv6 FEC (opaque types 4 and 251, with IPv4
root LSR address).
By default, all FEC types negotiated via the LDP session are resolved on all LDP inter-
faces. If a given FEC type is enabled at the session level, it can be disabled over a given

SR OS 13.0.R10 Software Release Notes 93


Enhancements

LDP interface at the IPv4 or IPv6 adjacency level for all IPv4 or IPv6 peers over that inter-
face. If a given FEC type is disabled at the session level, then FECs will not be advertised
and enabling that FEC type at the adjacency level will not have any effect. The LDP adja-
cency capability can be configured on link Hello adjacency only and does not apply to tar-
geted Hello adjacency.
The LDP adjacency capability TLV is advertised in the Hello message as described in
draft-pdutta-mpls-ldp-adjcapability. It is used to restrict which FECs can be resolved over a
given interface to a peer. This provides the ability to dedicate links and data path resources
to specific FEC types. For IPv4 and IPv6 prefix FECs, a subset of ECMP links to a LSR
peer may each be configured to carry one of the two FEC types. An mLDP P2MP FEC can
exclude specific links to a downstream LSR from being used to resolve this type of FEC.
[206150]

Services General • Release 13.0.R3 adds the support for using an SDP with bgp-tunnel enabled for Epipe
spoke-sdp termination on IES and VPRN interfaces. [194468]

Subscriber • A new CLI flag ignore-df-bit in the PPP Local User Database (LUDB) ignores the do-not-
Management fragment (DF) bit for frames egressing the subscriber interface and fragments the frame
according to the applicable egress MTU. The DF bit is reset for the frames that are
fragmented. The CLI flag applies to PPPoE PTA and L2TP LNS frames only. [195644]

EPIPE/VLL • In Release 13.0.R3, the tools dump epipe-map-to-network command has been replaced
by the new command tools dump epipe-map-access-to-egress-port and enhanced to
support use cases including the use of endpoints for Epipe services. The original command
is deprecated.
This new command displays the egress port that will be used to transmit traffic associated
with the Epipe service. While the original command only supported Epipe services with a
single SAP and single SDP and would display the egress port associated with the SDP, the
new command supports Epipe services with the following combinations:
− SAP to SDP (with no endpoint configuration)
− SAP to SAP (with or without an Inter-Chassis Backup (ICB))
− SAP to SDP using endpoints with 1 or 2 SDPs
This command displays the egress port for traffic from SAP to egress SDP or to egress
SAP. It does not display the egress port for traffic from the SDP to egress SAP. This com-
mand also does not work with services that use policers or shared queues and also does not
support PBB services. [182135]

Cflowd • Release 13.0.R3 adds a new Cflowd option to export flow data using interface indexes
(ifIndex values), which can be used directly as the index into the IF-MIB tables for
retrieving interface statistics. Specifically, if the new config cflowd use-vrtr-if-index
command is enabled, then the ingressInterface (ID=10) and egressInterface (ID= 14) fields
in IP flow templates used to export the flow data to Cflowd v9 and v10 collectors will be
populated with the IF-MIB ifIndex of that interface. In addition, for v10 templates, two
new fields are added to the IP flow templates to present the Virtual Router ID associated
with the ingress and egress interfaces.

94 SR OS 13.0.R10 Software Release Notes


Enhancements

The default behavior remains the same as in prior releases, such that the ingress and egress
interface index will be populated using the SR OS global interface index, which is unique
on a system-wide basis but does require a separate MIB look up to determine the interface
index that is compatible with the IF-MIB tables. [198081]

Application • Release 13.0.R3 supports a new version of the isa-aa.tim file that enables new and updated
Assurance protocol signatures and applications. The new and updated protocols in this release are
shown in the table below. For a complete list of the Release 13.0 AA identification
capabilities (protocols and applications), contact your regional support organization.

Table 19. New and Updated AA Protocols in Release 13.0.R3


Protocol Status Comments
League of Legends new Provides detection of League of Legends over
HTTP and TLS, and gaming over UDP.
LINE updated Provides improved detection of LINE over SPDY.
Viber updated Provides improved detection of Viber audio and
video traffic over UDP.

WLAN-GW • Release 13.0.R3 adds the support for managed routes to WLAN-GW group-interfaces. To
support this, the anti-spoof type of the group-interface has to be changed from the default
ip-mac to nh-mac. This is possible through new CLI: sap-parameters anti-spoof {ip-
mac | nh-mac}. With the new anti-spoof type, framed routes can be added using the
RADIUS attributes Framed-Route and Framed-IPv6-Route. To enhance the security for
MAC-only anti-spoof, uRPF support also has been added to WLAN-GW group interfaces.
[197111]

Release 13.0.R2

ARP/ND Snooping • Proxy-ARP now supports the following features in production networks:
and Proxy Support − Proxy-ND
− Proxy-ARP dynamic-arp-populate (IP->MAC entries learned from snooped
ARP/GARP messages received in SAPs/SDP-bindings).
This feature was introduced as a limited-support feature in Release 13.0.R1.

Application • Release 13.0 R2 supports a new version of the isa-aa.tim file that enables new and updated
Assurance protocol signatures and applications. The new and updated protocols in this release are
shown in the table below. For a complete list of the Release 13.0 AA identification
capabilities (protocols and applications), contact your regional support organization.

SR OS 13.0.R10 Software Release Notes 95


Enhancements

Table 20. New and Updated AA Protocols in Release 13.0.R2


Protocol Status Comments
QQ updated Provides improved detection of QQ traffic over
HTTP and TCP.
Weixin updated Provides improved detection of WeChat traffic over
HTTP and TCP.

WLAN-GW/WiFi: • The VLAN to WLAN-GW IOM/IMM steering via internal Epipe feature is now supported
VLAN to WLAN- for production networks. This feature was introduced as a limited support feature in
GW IOM/IMM Release 13.0.R1.
Steering via
Internal Epipe

Release 13.0.R1
Release 13.0.R1 also includes all enhancements available in Releases 12.0.R2 to 12.0.R8. Refer
to the SR OS 12.0.R8 Release Notes for enhancements available in Releases 12.0.R2 through
12.0.R8.

HW/Platform • The CLI now displays “Transceiver Status” in show port detail. [171306]

RADIUS • A new timer, “down-timeout”, is used to declare a RADIUS server “out-of-service”. A


RADIUS server is declared “out-of-service” if it fails to respond to RADIUS requests
within the “down-timeout” interval. By default, the value of the “down-timeout” is the
number of retries multiplied by the timeout interval. Each host will use the configured
timeout and retry value under the AAA RADIUS server policy; timeout refers to the
waiting period before the next retry attempt and retry refers the number of times the host
will attempt to contact the RADIUS server. If a RADIUS server is declared “out-of-
service”, the host pending retry attempts will move on to the next RADIUS server.
[193009]

System • The NTP time recovery process has been augmented to smoothly incorporate leap second
events into the node timebase. This includes protection against race conditions with NTP
messaging near the UTC midnight on the leap second day.
• The behavior of session logs (logs with to session in their configuration) has been
enhanced in several ways. All of the log configuration is now saved in an admin save
except for the to session configuration. The to session configuration is non-persistent and
will no longer cause a '*' (the unsaved change indicator) to appear at the beginning of the
CLI prompt.
• On systems with APEQs, in conditions where all of the fans have failed or are absent from
the chassis, the system temperature could increase to unacceptable levels. A new
functionality has been added to the APEQs, where they will bring the system down within

96 SR OS 13.0.R10 Software Release Notes


Enhancements

three (3) minutes if the fans have failed or their presence cannot be detected. User
intervention is required to recover the system. [162664]
• In Release 13.0.R1, new internal thresholds and resulting log or SNMP trap messages have
been added to monitor the IOM next-hop resources. The existing error message when the
next-hop resource is exceeded has been updated and two new messages have been added to
signal when the resource reaches 90% utilization and another when it has dropped below
85% utilization. [163875]
• The auto-generated timestamp used in script result filenames (used, for example, by CRON
and EHS) has been enhanced to include microseconds.
• Users executing unauthorized CLI commands will now generate an event that will be
captured in the system log. [171199]
• Release 13.0.R1 has added three new AES-CTR ciphers to SSHv2: AES128-CTR,
AES192-CTR, and AES256-CTR. These new ciphers will help to improve SR OS SSHv2
security. [173803]
• Release 13.0.R1 introduces additional checks on Inter-card Communication messages to
prevent card resets in case of bit corruptions in these messages. [183193]

LAG • Support for mixed port-speed LAG was enhanced to allow mixing of 10GE WAN-PHY
ports with 100GE ports. A small difference between WAN-PHY and LAN-PHY in port
speed is ignored; thus, for example, a 100GE port is considered to be ten times the
bandwidth of 10GE WAN-PHY port for all weight/port-speed based functionality (such as
QoS or hash). [192095]

Routing • Release 13.0.R1 introduces the option to add a description to an aggregate route. [175397]

Route Policies • Release 13.0.R1 enhances the route policy source-address command to accept a prefix-
list instead of just a single IP address. [171519]

IPv6 • It is now possible to remove a manually-configured IPv6 Link-Local Address (LLA) on an


IP interface. Previously, removing manually-configured LLA required the operator to
completely remove IPv6 configuration on the interface using the no ipv6 command.
Operators may now use the ipv6 no link-local-address command to remove a manually-
configured LLA, and the system will regenerate an EUI-64 LLA for that interface.
[175057]

DHCP server • The support for leasequery has been added. When the allow leasequery option is set to
false:
− the server will drop leasequery requests (as before)
− no leasequery counters will be increased even when a leasequery request is received
(as before)
When the allow leasequery option is set to true:
− the server will reply to leasequery by client-ID
− queries with missing options or malformed queries will also get a reply with a
corresponding status code

SR OS 13.0.R10 Software Release Notes 97


Enhancements

The options OPTION_LQ_RELAY_DATA, OPTION_LQ_CLIENT_LINK, are not sup-


ported. [193869]

DHCP • Release 13.0.R1 adds support to insert NAS-Port (containing tunnel source/destination) in
a DHCP option in case of Layer-2 wholesale. The option is then included in access-request
message to AAA. [198441]

Python • Release 13.0.R1 introduces python-policy support for DHCPv4 and DHCPv6 relay on
service SAP (non-ESM) interfaces. The highlights of this enhancement are:
− Python module alc.dhcpv4 and alc.dhcpv6 are supported
− Python module alc.dtc is supported except alc.dtc.setESM() is not supported
[191818]

RIP • In Release 13.0.R1, RIP and RIPng have been enhanced to allow RIP updates to be sent as
unicast messages, instead of multicast or broadcast messages. This is enabled by specifying
a unicast address instead of the interface name when creating the RIP/RIPng neighbor. In
addition, the send unicast command must also be enabled to activate the unicast
advertisements. [168243]

IS-IS • The functionality to set overload state due to an SFM failure that reduces forwarding
capacity has been extended with the support for IS-IS. Setting overload enables a router to
still participate in exchanging routing information, but routes all traffic away from it.
Previous releases starting with Release 8.0.R1 supported OSPF only.
Overload is now set for both OSPF and IS-IS using the config router single-sfm-overload
CLI command for global router protocols, or with the single-sfm-overload CLI command
within a VPRN. The conditions to set overload are as follows:
− 7750 SR-c12/7/12 and 7450 ESS-6/6v/7/12: protocol sets overload if one of the
CPM/CFMs fails.
− 7950 XRS and 7750 SR-12e: protocol sets overload if two or more SFMs fail.
[171604]
• IS-IS now enters the overload state if adding routes to the hardware FIB fails, or the
protocol reaches the configured maximum route limit in a VPRN (set with maximum-
routes or maximum-ipv6-routes). Previous releases would restart IS-IS every 30 seconds.
To clear overload for IS-IS, use the clear router isis overload CLI command. [171714]

OSPF • OSPF now enters the overload state if adding routes to the hardware FIB fails, or the
protocol reaches the configured maximum route limit in a VPRN (set with maximum-
routes or maximum-ipv6-routes). Previous releases would restart OSPF every 30
seconds. To clear overload for OSPF, use the clear router ospf overload CLI command.
To clear overload for OSPFv3, use the clear router ospf3 overload CLI command.
[172076]

BGP • Release 13.0.R1 adds BGP next-hop information to the display of BGP routes in the
routing table and FIB. [141814]

98 SR OS 13.0.R10 Software Release Notes


Enhancements

• Release 13.0.R1 improves third-party next-hop handling in BGP and also makes it
configurable. [165801]
• Release 13.0.R1 allows the policy-based export of the active/installed route to a peer that
has BGP advertise-inactive enabled in its configuration. [167175]
• Release 13.0.R1 extends the show router bgp routes command to allow filtering of
IP-VPN routes based on the combination of community and prefix/route-distinguisher.
[172384]
• Release 13.0.R1 changes the BGP FlowSpec implementation to comply with draft-haas-
idr-flowspec-redirec-rt-bis-00. This is an important draft to ensure interoperability with
other vendors when using the redirect-to-VRF action. The standards that originally defined
this action (RFC 5575) did not specify how the type of the route-target should be inferred.
[174598]

mLDP In-Band • Release 13.0.R1 adds the option to configure ipv4 and ipv6 to the following command:
Signaling config>router>pim>if>p2mp-ldp-tree-join [ipv4][ipv6]
The ipv4 and ipv6 keywords are optional keywords; if no keyword is chosen, then ipv4 is
assumed for backward compatibility.

IMPM • When a 7750 SR or 7450 ESS system is equipped with an SFM5, the default values used in
the mcast-capacity and redundant-mcast-capacity commands (under config>mcast-
mgmt>chassis-level>plane-capacity) are set to 87.5%. [201913]

QoS • A new statistic in the show service id service-id sap sap-id sap-stats output displays the
number of valid packets received on SAP ingress policers and queues (used on that SAP or
subscribers on that SAP), and on any related ingress queue group policers and queues. This
is particularly useful to display SAP-level traffic statistics when forwarding classes in a
SAP ingress policy have been redirected to an ingress queue group.
The statistics do not include any packet-byte-offset that may have been set in the SAP
ingress QoS policy or the ingress queue-group template. This is applicable to all services
and is supported for all hardware.
• The number of policers configurable as a SAP ingress and SAP egress QoS policy has been
increased to 63 for each. This allows a larger number of policers to be used in the IPv4 and
IPv6 criteria action statements ingress. Forwarding-class mapping capabilities have not
changed though forwarding classes can be mapped to any policer identifier.
• SAP egress QoS has been enhanced to allow traffic to be classified directly to an egress
policer. This is supported using the action parameter in the ip-criteria and ipv6-criteria
statements. Policed traffic continues by default to exit through a forwarding-class-mapped
queue in the egress policer-output-queues queue group, or alternatively it can be directed
to a local queue, a queue in a user-defined queue group, or it can exit using the queue
mapped by its forwarding class if the use-fc-mapped-queue is specified.
This is supported on all FP2- and higher-based hardware, excluding on a 7750 SR-a4/a8 or
when HS-MDAv2 is used.
• The ability to override the parent weight and CIR-weight configured on ingress and egress
tier 2 and 3 schedulers, and on a tier-1 egress scheduler with a parent-location vport, has

SR OS 13.0.R10 Software Release Notes 99


Enhancements

been added to SAPs and multi-service sites. This is supported on all hardware but is not
applicable to an HS-MDAv2.
• Support has been added to allow a packet-byte-offset to be applied to SAP, subscriber and
queue group ingress queues. This allows the packet size used for both shaping and
accounting to be either increased or reduced. This is supported on FP2- and higher based
hardware and ignored on FP1-based hardware.
• The maximum value for the substract parameter used in a packet-byte-offset statement is
now 64 for all egress uses of this parameter, including the related overrides. Note that the
minimum resulting packet size used by the system is one (1) byte, or 64 bytes with an
HS-MDAv2, regardless of the setting of the substract parameter.
This is supported on FP2- and higher-based hardware.
• The configuration of SAP ingress and egress QoS policies has been simplified by allowing
IPv4 prefix lists to be used for matching in IP criteria statements. This is supported when
applying these policies to SAPs.
• The maximum rate configurable for queue PIR and CIR rates in a SAP ingress and egress
policy (when used with SAP or subscribers), and in an ingress and egress queue group,
have been increased to 2000 Gb/s.
If the rates at ingress exceed the port capacity, or exceed the FP capacity with per-fp-ing-
queuing configured, the rates are set to max. At egress, if the rates exceed the port capacity
(including the egress-rate setting) they are set to max. As a consequence, the maximum
queue rate used can change and hence the behavior of some existing configurations can
change. This also impacts the use of percent-rates with no parent or a max-rate parent, or
the use of the advanced-config-policy with a percent percent-of-admin-pir.
Rates greater than the above (capped) rates are only relevant when configured on a queue
which is part of a distribute or port-fair mode LAG spanning multiple FPs.
The related queue MBS and CBS maximum values are increased to 1GB, which are con-
strained by the pool size in which the queue exists and for the MBS also by the shared pool
space in the corresponding megapool. Their default values remain at the maximum of 10ms
of the PIR or 64Kbytes for the MBS and the maximum of 10ms of the CIR or 6K bytes on
an FP2 and 7680 bytes on an FP3 for the CBS.
In addition, the following rates have been increased to 3200 Gb/s:
− a scheduler PIR and CIR rates in a scheduler policy
− the maximum rate, a level’s PIR and CIR rates and a group’s PIR and CIR rates in a
port-scheduler policy
− the aggregate rate applied on egress Ethernet port queue groups, Vports, SAPs, multi-
service sites and encap groups (but not on egress subscriber profiles, IGMP/MLD
H-QoS adjustment rates, ANCP rates or WLAN gateway rates)
All queue, scheduler and egress scheduler overrides relating to the above rates have also
been increased to the corresponding value.
Note that due to the changes in this implementation, there may be small differences in the
resulting rates, MBS and CBS compared to the previous implementation.
This is supported on FP2- and higher-based hardware but is not applicable to the
HS-MDAv2.
• The IPv6 matching criteria within a SAP ingress QoS policy has been enhanced to include
matching on fragmented packets, including matching only on the first or non-first
fragments.

100 SR OS 13.0.R10 Software Release Notes


Enhancements

This is supported on FP2- and higher-based hardware.


• The entry for “QoS Internal Schedulers” has been removed from the output of the tools
dump system-resources command as the system ensures that sufficient internal schedulers
are available so this resource no longer needs to be monitored. [184405]
• The show card slot-number cpu command has been enhanced to display the CPU
information of two additional IOM process groups: H-QoS Algorithm and H-QoS
Statistics. As the naming implies, the first is responsible for running the actual algorithm
and executing the result while the second collects the offered statistics from the queues.
Note that on line cards with a Multicore CPU, the capacity usage of the H-QoS statistics
process group will always be seen to be near to 100%; this is expected as it constantly tries
to run as fast as possible when unused processor cycles are available, and it is not detrimen-
tal to the running of other processes on the line card. [188179]

Filter • Release 13.0.R1 introduces enhanced show and debug CLI support for filter policies. The
existing filter commands under show>filter and tools>dump>filter>resources have been
enhanced to provide more detail on how filter policies are allocated, how much resource is
being consumed currently by filter policies, and which filter policies or filter policy entries
consume the most resources. To display the extra information, some pre-Release 13.0.R1
displays have been modified to introduce new or modified headings. Any external tools
parsing through filter show and tools displays must be verified and modified accordingly
prior to an upgrade.
• Release 13.0.R1 introduces the support for PBR redirect action forward {sap | sdp} for
IPv6 filter policies for VPLS services. This action has been supported previously in IPv4
filters only. [166644]
• Release 13.0.R1 adds the support for SCTP source/destination match in IPv4 and IPv6
ingress line card filter policies. SCTP port match supports same inputs as TCP/UDP port
match. To specify SCTP port match, the protocol for filter entry match must explicitly
define SCTP. The SCTP match programming is only supported using CLI/SNMP
management. [182939]

Policy • It is now possible to use regular expressions with the site of origin (SOO) extended
community in community-lists. [120229]
• Release 13.0.R1 extends the policy-test command to accept up to fifteen (15) policy names
so that the result of a chain of policy statements on a selected set of BGP routes can be
evaluated. [184487]

Subscriber • The maximum number of RADIUS servers in a RADIUS server policy has been increased
Management from five (5) to sixteen (16). [131980]
• Release 13.0.R1 adds the support for configurable NSAPI values on WLAN-GW. [166216]
• Release 13.0.R1 adds the support to report the VLAN tag received in GRE-encapsulated
Layer-2 frame to RADIUS in authentication and accounting messages. [173033]
• WLAN-GW now includes an APCO (as per 3GPP Release 11) in session-create-request
message instead of PCO, to request DNS from PGW. [174786]
• The output of the show subscriber-mgmt statistics command has been enhanced with
updated and new counters such as DHCPv6 (PD) managed route, IPv6 static hosts, IPoE

SR OS 13.0.R10 Software Release Notes 101


Enhancements

sessions, Basic Subscriber Management (BSM). New Total Subscriber hosts and Total
System Hosts Scale counters can be used to match against per line card and system scaling
limits. All counters have peak values that can be cleared and are available in a MIB for
SNMP access. [190452]
• Release 13.0.R1 adds multicast as an option for per-host-replication under subscriber-
management igmp-policy. By default, per-host-replication will use unicast to deliver the
mulitcast content directly to the host. Enabling the multicast option will send the multicast
content using a multicast destination address and the multicast statistics will be counted
against the subscriber's queues.

VPLS • Release 11.0.R1 introduced the support for IPv4 multicast routing in a Routed-VPLS
service where the source is located on the IP interface side of the service with receivers on
the VPLS side of the service. When IGMP is configured on the IP interface, it was
mandatory to enable IGMP-snooping in the VPLS. This constraint has been removed so
that IGMP can now be configured on the IP interface without needing IGMP-snooping to
be enabled in the VPLS service.
• The pw-template has been enhanced in Release 13.0.R1 with the Spanning-Tree-Protocol
(STP) and Layer-2 Protocol Tunneling (L2PT) commands already supported under SAPs
and SDP-bindings. STP and L2PT commands may be added to pw-template in VPLS
services when BGP-AD and/or BGP-VPLS are used.
• The monitor-oper-group group-name statement has been added under the
config>service>vpls>bgp>pw-template-binding context. The BGP-AD auto-instantiated
spoke-SDP bindings can now monitor an existing oper-group and drive their status based
on the configured oper-group. [172167]

IPsec • Certificate authentication and Diffie-Hellman computation for IKE protocol has been
further optimized; as a result, the setup performance of IPsec tunnels is increased.
• Release 13.0.R1 introduces the following new algorithms to IPsec:
− PRF_AES128_XCBC as IKEv2 pseudorandom function
− AUTH_AES_XCBC_96 as IKEv2 integrity Algorithm
− AUTH_AES_XCBC_96 as ESP integrity Algorithm [136711]
• Release 13.0.R1 allows the system to send unsolicited IKEv2 configuration attributes to
clients if they are available in RADIUS Access-Accept. [168065]
• Release 13.0.R1 allows the system to support a combination of EAP and one other auth-
method on the same IPsec-GW:
− eap + psk-radius
− eap + cert-radius
− eap + psk-radius or cert-radius
This behavior is enabled by configuring auth-method as auto-eap-radius, along with con-
figuration of auto-eap-method and auto-eap-own-method. [173212]
• Release 13.0.R1 allows the system to print out the content of the notification data field of
IKEv2 Notify payload in the debug IPsec output. [175834]
• Release 13.0.R1 allows the system to return secondary IPv4 and IPv6 DNS server
addresses to IKEv2 remote-access client via IKEv2 configuration payload. [175866]

102 SR OS 13.0.R10 Software Release Notes


Enhancements

• Release 13.0.R1 introduces the following new behavior regarding the user-password
attribute in access-request when authenticating IKEv2 remote-access tunnel:
− if auth-method is psk-radius, then the system will include the user-password with
tunnel's psk as the value
− if auth-method is any other RA tunnel method (eap or cert-radius): then the system
will only include the user-password when password is configured in IPsec radius-
authentication-policy. [175869]
− Release 13.0.R1 extends the VPRN route types that can be used to reach the
destinations of IP tunnels (IP-in-IP or GRE). It is now possible to use VPRN routes
with tunneled next-hops (to remote PEs). [178615]

TMS • Release 13.0 supports the configuration of a filter applied to the ISA-TMS tms-interface
off-ramp ingress CLI context allowing TMS-generated traffic (typically challenge
packets) to be redirected to the Base routing table via a new redirect-to-vrf command.
This feature allows for correct routing of TMS-generated challenges back to source IP
address where VRF is being used to off-ramp traffic (as opposed to base table being used to
off-ramp traffic), and thus does not contain source routes back to the IP source of off-
ramped traffic. [172653]

NAT • The source IP address of an L2-Aware NAT subscriber has been added to the MAP/FREE
event logger.
• Security nonce has been added to the PCP Opcode Map and Get.
• Nonce restriction in PCP GET with NEXT option has been removed. This will allow PCP
clients to query the PCP server’s existing PCP mappings, without having to know the
nonce with which the mapping was initially created in accordance with draft-cheshire-pcp-
unsupp-family-06.
• Returned error code “CANNOT_PROVIDE_EXTERNAL” has been replaced with error
code “MALFORMED_OPTION for MAP opcode with PREFER_FAILURE option and
unspecified Suggested External Port and/or Suggested External Address field”, according
to RFC 6887.
• Release 13.0.R1 introduces debug capability for PCP (debug router pcp pcp-server name
packet).
• Port-forwards, Lawful Intercept (LI) entries and deterministic maps/prefixes have gained
an operational state. In the event that the NAT subscriber resources are temporarily
exhausted, the port-forwards, LI entries and deterministic map/prefixes temporarily
become non-operational. After the resources are freed, the entities in question
automatically transition into an operational state that can be observed via show commands.
Consequently, new traps have been introduced: tmnxNatFwd2OperStateChanged,
tMirrorLiNatLsnSubOperStateCh, tMirrorLiNatL2awSubOperStateCh,
tmnxNatDetMapOperStateChanged and tmnxNatDetPlcyOperStateChanged.
• Output of the show service nat port-forwarding-entries has changed and now includes
the operation state of the port-forwards.
• Output of the show li li-source source-id command has changed and now includes the
operation state of the LI in NAT.

SR OS 13.0.R10 Software Release Notes 103


Enhancements

• Output of the show service nat summary has changed and now includes additional
information about subscriber identification, NAT redundancy and NAT policies. [189366]

Application • App-Service-Options characteristics and values can now be included in the AA-subscriber
Assurance custom accounting records. Once configured, the accounting record will include all app-
service-options characteristics and values applied to each subscriber.
• The system automatically exports the IP-family information in Cflowd Volume IPFIX
records. This provides additional information to the operator for data-mining use cases to
understand traffic distribution between IPv4, IPv6, DS-Lite, 6RD, and Teredo at the
network level or per application.
• The system automatically exports the Operating System version in the Cflowd
Comprehensive IPFIX records. This new capability provides additional information to the
operator for data-mining use cases to understand traffic distribution per major/minor
release of a given Operating System.
• Release 13.0.R1 now automatically monitors success and failure notifications using HTTP
notification. In case the notification is not successfully displayed the system will
automatically attempt to notify the next candidate flow instead of waiting for the next
notification interval. This enhancement requires the operator to update the notification
script and modify the AA Policy in order to enable the http-match-all-req for HTTP
requests sent to the messaging server.
• Release 13.0.R1 adds a minimum-isa-generation command to configure the scale
parameters for the ISA group.
− When minimum-isa-generation is configured as one (1), the Group and per-ISA
limits are the MS-ISA (ISA1) scale.
− If there is a mix of MS-ISA and MS-ISA2, the minimum-isa-generation must be left
as one (1).
− When minimum-isa-generation is configured as two (2), the per-ISA resource limits
(as per show isa application-assurance-group 1 load-balance) will increase to MS-
ISA2 limits.
• Release 13.0.R1 adds network-address as an app-filter match criteria to allow IP prefix
list-based identification of traffic such as for on-net vs. off-net traffic [184415]
• Release 13.0.R1 adds a configurable export method for per-subscriber aggregate statistics.
The options are no-export and export via an XML accounting policy (XML export is only
supported in residential and VPN aa-sub-scale modes). [187025]
• Release 13.0.R1 enhances the Gx Diameter interface to support 3GPP release 12. 3GPP
Release 12.0 does not make use of ADC rules (as per release 3GPP R11) on the Gx
interface and instead integrates some of ADC functionality into PCC rules. AA supports
both models. [189845]
• Release 13.0 R1 supports a new version of the isa-aa.tim file that enables new and updated
protocol signatures and applications. The new and updated protocols in this release are
shown in the table below. For a complete list of the Release 13.0 AA identification
capabilities (protocols and applications), contact your regional support organization.

104 SR OS 13.0.R10 Software Release Notes


Enhancements

Table 21. New and Updated AA Protocols in Release 13.0.R1


Protocol Status Comments
DTLS new Provides detection of DTLS 1.0, DTLS 1.2, DTLS
X.509 certificate subject common and organization
name string matching and DTLS session resump-
tion using session ID.
Flow Export new Provides detection of NetFlow v5/v8/v9, IPFIX
over UDP and sFlow v5.
Snapchat new Provides detection of Snapchat over TLS.
JustinTv updated This protocol has been updated such that it now
detects only Twitch Video Streaming (both Twitch
and JustinTv services belong to the same parent
company, Twitch Interactive).
OpenVPN updated Provides detection of Hotspot Shield over UDP and
TCP.

Cflowd • In Release 13.0.R1, a new option manual-export has been added to the Cflowd collector
configuration options allowing flow exports to be trigger-based. Currently, Cflowd will
automatically export flow data as the traffic flow expires due to flow timeouts. With this
option enabled, these flows will not automatically be sent but instead will be kept in the
Cflowd cache until the manual trigger is issued to generate the flows. At that time all
expired flows will be set to the associated collector as quickly as possible. This new option
does not change the behavior of the system if the cache size is exceeded, in which case the
normal overflow actions will be taken. [172569]

OAM • DMM support for 10-second (10000 ms) probe interval for OAM-PM configured tests has
been added. [182865]

Scaling The scaling numbers have increased for the following areas. Contact your Alcatel-Lucent
representative for details:
• SRRP scaling on CPM3 and above
• IPsec IKEv2 chassis limit
• NAT on MS-ISA2
• LAG scaling on the entire system

SR OS 13.0.R10 Software Release Notes 105


Limited Support Features and Enhancements

Limited Support Features and Enhancements


This section describes the SR OS features that are intended for laboratory use only (not for the
production network environment).
See also Unsupported Features and Known Limitations for more information about features that
may not be fully supported.

HW/Platform

Virtualized The virtualized Simulator (vSim) is a product that taps the potential of network function
Simulator virtualization (NFV). This product is intended to be used as a laboratory tool to fully simulate
the control and management plane of an SR OS node. The vSim is not intended to be used in a
production network environment and the forwarding plane is limited to 250 pps per interface.
This feature was introduced in Release 12.0.R4.

Services

XMPP Support on The provisioning of filter entries from VSD is NOT supported in production networks and can
DC PE for Filters only be used in controlled laboratory environments. If a filter entry is sent from VSD and added
(Fully-Dynamic to the running configuration by a Python script, the laboratory user is advised NOT to admin
Model) save the configuration in order to avoid issues. This feature was introduced in Release 13.0.R4.

Subscriber
Management

Gx – PCC Rules Gx support has been added for fully-defined rules that can be constructed on PCRF and applied
to the subscriber host. This feature should only be used in a laboratory environment and not in
a production network. This feature was introduced in Release 13.0.R4.

Subscriber-profile Subscriber-profile overrides via CoA for parameters of tier-1 scheduler in scheduler-policy
Overrides via CoA referred to or from the subscriber-profile should only be used in a laboratory environment and
not in a production network. This enhancement was introduced in Release 13.0.R4.

106 SR OS 13.0.R10 Software Release Notes


Unsupported Features

Unsupported Features
The following tables summarize the features that are not supported on certain SR OS platforms
(marked by an X where unsupported). All SR OS features are supported on all platforms unless
otherwise listed in the table below.
Some platforms do not support ISA applications using MS-ISAs; see also Release 13.0.R10
Supported Hardware and Usage Notes for more information.

Hardware
Table 22. Unsupported Hardware Features

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS

Feature
Chassis modes X X1 X X X
Channelized and TDM interfaces X X X X
ATM interfaces, MDA, and services X X X X
ASAP MDAs and associated interface types X X X X
CES MDAs and associated interface types X X X X
IEEE 1588 PTP X X2 X
IEEE 1588 port-based timestamping X X X
Sub-second CCM-enabled MEPs X
SONET/SDH interfaces X X X
VSM Cross-Connect Aggregation (CCA) and CCA Group (CCAG) X X X X X3
1. The 7750 SR-12e contains the same feature set as the 7750 SR in chassis mode D. Chassis mode concept is not present on
the 7750 SR-12e.
2. Not supported on 7750 SR-c12 with CFM-XP.
3. VSM/CCA is only supported on 7750 SR VSM MDAs in IOM3-XP when mixed mode is enabled.

SR OS 13.0.R10 Software Release Notes 107


Unsupported Features

System
Table 23. Unsupported System Features

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS
Feature
BITS input port redundancy X1
BITS Out support X1
Centralized (CPM-based) CPU-Protection X2 X2 X2
Ingress Multicast Path Management X X X
Major ISSU X X X
Minor ISSU X X3 X
Soft Reset X X3 X
System Alarm Contact Inputs X X X X X X
OOB Management Ethernet Port Redundancy X X X
1. Supported on the 7750 SR-c4 but not supported on the 7750 SR-c12.
2. Note that Distributed CPU Protection (DCP) is supported.
3. Supported on the 7750 SR-c12 but not supported on the 7750 SR-c4.

108 SR OS 13.0.R10 Software Release Notes


Unsupported Features

Quality of Service
Table 24. Unsupported QoS Features

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS
Feature
Named Pools (QoS) X X X X
Ingress shared queuing (Dual-Pass) X X1
Policers (except for Distributed CPU Protection) X

1. Not supported on 400G FP3 line cards.

Routing
Table 25. Unsupported Routing Features

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS

Feature
BGP for forwarding unicast packets in GRT X
BGP RFC 3107-labeled routes for forwarding unicast packet in GRT1 X

ABR/RR capability for BGP RFC 3107-labeled routes2 X


Cflowd X
IPv6 routing (unicast and multicast, 6PE, 6VPE, QoS criteria matching
X
within a VPLS or Epipe service)
IP Multicast routing and forwarding X
• Protocols: PIM, MSDP, and IGMP X
• MVPN X
• P2MP LSP for forwarding multicast packet in GRT and in MVPN3 X

SR OS 13.0.R10 Software Release Notes 109


Unsupported Features

1. BGP RFC 3107-labeled routes are supported in L2 services only.


2. LDP-BGP stitching is supported.
3. P2MP LSP is supported in VPLS.

MPLS
Table 26. Unsupported MPLS Features

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS
Feature
GMPLS UNI X X X X

Services
Table 27. Unsupported Services Features

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS

Feature
Arbor TMS: Threat Mitigation Services1 X X X X X
Circuit Emulation services (for example, Cpipe SAPs) X X X
new-qinq-untagged-sap configurability for :*.0 and :0.0 SAPs X 2

Full VPRN support X


Frame Relay interfaces and services (for example, Fpipe SAPs) X X X X
IP Mirroring X
Tunnel services (IPsec, GRE tunnel termination)3,4 X X X5 X X

110 SR OS 13.0.R10 Software Release Notes


Unsupported Features

Table 27. Unsupported Services Features (Continued)

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS
Feature
IPv6 tunnel services (IPsec, GRE tunnel termination)3,4 X X X5 X X
G.8031 (Ethernet tunnel support) X
Multi-Chassis features using isa-tunnel with MS-ISA6 X X X X
sFlow X X X X X
Spoke termination on L3 (IES/VPRN) interfaces X
Video services (Retransmission and Fast Channel Change, Video Qual-
X X X X X8 X8
ity Monitoring, Local/Zoned Ad Insertion)1,7
1. Requires an MS-ISA/MS-ISA2/MS-ISM (along with -E variants on the 7750 SR).
2. This feature is always “on” for the 7950 XRS.
3. Requires an MS-ISA/MS-ISA2/MS-ISM.
4. Requires an isa-tunnel/isa2-tunnel application license.
5. Not supported on 7750 SR-c4 only.
6. Requires an MS-ISA/MS-ISA2/MS-ISM (along with -E variants on the 7750 SR).
7. Requires an isa-video application license.
8. Not supported for local or zoned ad insertion video service only.

Subscriber Management
Table 28. Unsupported Subscriber Management Features
7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS

Feature
IPv4 local DHCP Server X
IPv6 local DHCP Server X X

SR OS 13.0.R10 Software Release Notes 111


Unsupported Features

Table 28. Unsupported Subscriber Management Features (Continued)

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS
Feature
L2TP LNS1,2 X X X X

port-policy command1,2 X X
1,2 X X X3 X
NAT
WLAN gateway (WLAN-GW)1,2 X X X X X X
Subscriber Management—Routed CO (VPRN/IES subscriber inter-
X X
faces)
Subscriber Management—Bridged CO (VPLS) X
1. Requires an MS-ISA/MS-ISA2/MS-ISM (along with -E variants on the 7750 SR).
2. Requires an isa-bb/isa2-bb application license.
3. Supported on the 7750 SR-c12 but not on the 7750 SR-c4.

Application Assurance
Table 29. Unsupported AA Features

7450 ESS without mixed mode

7450 ESS with mixed mode


7750 SR-1e/2e/3e
7750 SR-c4/c12
7750 SR-a4/a8
7750 SR-7/12

7750 SR-12e
7950 XRS

Feature
Application Assurance1 X X
AARP X2

1. Requires an MS-ISA/MS-ISA2/MS-ISM (along with -E variants on the 7750 SR) and an isa-aa/isa2-aa application license.
2. Supported on the 7750 SR-c12 but not supported on the 7750 SR-c4.

112 SR OS 13.0.R10 Software Release Notes


Deprecated Features

Deprecated Features

Release 13.0.R10
No features have been deprecated in Release 13.0.R10 since Release 13.0.R9.

Release 13.0.R9
No features have been deprecated in Release 13.0.R9 since Release 13.0.R8.

Release 13.0.R8
No features have been deprecated in Release 13.0.R8 since Release 13.0.R7.

Release 13.0.R7
No features have been deprecated in Release 13.0.R7 since Release 13.0.R6.

Release 13.0.R6
No features have been deprecated in Release 13.0.R6 since Release 13.0.R5.

Release 13.0.R5
No features have been deprecated in Release 13.0.R5 since Release 13.0.R4.

Release 13.0.R4
No features have been deprecated in Release 13.0.R4 since Release 13.0.R3.

Release 13.0.R3
No features have been deprecated in Release 13.0.R3 since Release 13.0.R2.

SR OS 13.0.R10 Software Release Notes 113


Deprecated Features

Release 13.0.R2
No features have been deprecated in Release 13.0.R2 since Release 13.0.R1.

Release 13.0.R1
This section describes the SR OS features that have been deprecated in Release 13.0.R1.

7710 SR • The 7710 SR-c4/c12 is no longer supported in SR OS starting in Release 13.0.R1.

114 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

Changed or Deprecated Commands


This section describes the SR OS commands that have been changed or deprecated. See also
Software Upgrade Procedures for more information about the behavior of commands or
parameters that have been modified or deprecated between releases.

Release 13.0.R10
No commands have been changed or deprecated in Release 13.0.R10 since Release 13.0.R9.

Release 13.0.R9
No commands have been changed or deprecated in Release 13.0.R9 since Release 13.0.R8.

Release 13.0.R8
This section describes the SR OS commands that have been renamed or deprecated in Release
13.0.R8.

ISA
Application
Commands

NAT Commands • The group parameter is renamed to nat-group in the following CLI commands. [210642]

Command Prior to Release 13.0.R8 Command in Release 13.0.R8


show isa nat-system-resources group group- show isa nat-system-resources nat-group
id member [1..255] nat-group-id member [1..255]
tools dump nat isa resources group group- tools dump nat isa resources nat-group
id member [1..255] nat-group-id member [1..255]

Release 13.0.R7
No commands have been changed or deprecated in Release 13.0.R7 since Release 13.0.R6.

SR OS 13.0.R10 Software Release Notes 115


Changed or Deprecated Commands

Release 13.0.R6
No commands have been changed or deprecated in Release 13.0.R6 since Release 13.0.R5.

Release 13.0.R5
This section describes the SR OS commands that have been renamed or deprecated in Release
13.0.R5.

BGP Commands • Release 13.0.R5 supports dynamic BGP peering for both ESM hosts and non-ESM hosts
(such as regular routers). To avoid confusion between the two, the command dynamic-
peer for ESM hosts, configured under BGP group, has been changed to esm-dynamic-
peer.

Command Prior to Release 13.0.R5 Command in Release 13.0.R5


configure configure
service vprn service-id service vprn service-id
bgp bgp
group name [dynamic-peer] group name [esm-dynamic-peer]

Release 13.0.R4
This section describes the SR OS commands that have been renamed or deprecated in Release
13.0.R4.

Filter Commands • Release 13.0.R4 introduces changes to the ACL filter policy commands. The action
command (with all types and related parameters defining), used to define an action to be
performed on a packet matching IPv4/IPv6/MAC ACL policy entry, has been deprecated
and replaced by a new action command that allows the operator to enter a new CLI context
under which individual actions can be configured using drop, forward, gtp-local-
breakout, http-redirect, nat, and reassemble action type commands and their respective
parameters.
The operational impact of the action command restructuring is as follows:
− Because all command and parameter names were preserved, any ACL configuration
prior to Release 13.0.R4 remains valid and results in the same configuration result for
all cases except the following:
Prior to Release 13.0.R4, an operator was able to use CLI, SNMP, or NETCONF to
configure an IP, IPv6, or MAC filter policy entry’s action without explicitly
specifying the action type. The system would interpret such configuration as “action
drop”. This functionality is no longer supported and action type must always be
explicitly specified using new action-type commands under new action context.
Loading an old configuration file that does not explicitly configure action type will
either fail or will result in a different behavior (a filter entry will not be activated as no
action is configured). The operator must ensure that any old configuration file always

116 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

explicitly configures action type drop for every filter policy entry action missing
explicit drop keyword. During an ISSU upgrade to Release 13.0.R4 or newer, the
system automatically converts the “action” command with no type specified to
“action drop” for all ACL filter types.
− Starting with Release 13.0.R4, admin save and info commands will save or display
filter entry action configuration in a multi-line format (as illustrated below).
− CLI configuration continues to accept a single line format to specify an action with its
type and related parameters.

Command Prior to Release 13.0.R4 Command in Release 13.0.R4


configure configure
filter {ip-filter | ipv6-filter | mac- filter {ip-filter | ipv6-filter | mac-
filter} filter}
entry entry
action action
drop
... ...
action drop [optional parameters] action
drop [optional parameters]
... ...
action forward [optional parame- action
ters] forward [optional parameters]
... ...
action http-redirect [optional action
parameters] http-redirect [optional parame-
ters]
... ...
action nat [optional parameters] action
nat [optional parameters]
... ...
action gtp-local-breakout action
gtp-local-breakout
... ...
action reassemble action
reassemble

Subscriber • In Release 13.0.R4, the pd-managed-route command is enhanced with a next-hop


Management {ipv4 | ipv6} parameter. When upgrading to Release 13.0.R4, the configuration will be
Commands converted as follows:
CLI contexts:
− config>service>ies>sub-if>grp-if>ipv6>dhcp6>
− config>service>vprn>sub-if>grp-if>ipv6>dhcp6>
− config>service>ies>sub-if>ipv6>dhcp6>
− config>service>vprn>sub-if>ipv6>dhcp6>

SR OS 13.0.R10 Software Release Notes 117


Changed or Deprecated Commands

Command Prior to Release 13.0.R4 Command in Release 13.0.R4


configure configure
service service
ies service-id ies service-id
subscriber-interface ip-int-name subscriber-interface ip-int-name
group-interface ip-int-name group-interface ip-int-name
ipv6 ipv6
dhcp6 dhcp6
pd-managed-route pd-managed-route next-hop ipv6

OAM Commands • TWAMP Light reflector range [1024–65535] has been restricted to [64364–64373] to
prevent UDP port allocation collisions. A configuration attempting to load with the
twamp-light reflector udp-port udp-port-number create outside of this range will cause
the reflector to fail the no shutdown activation. If the configured range does not subscribe
to the new restricted values, an ISSU function using previously accepted values will be
rejected until the TWAMP-Light reflector is shut down. [191657]

Tools dump • The tools>dump>service>vxlan>usage command has been deprecated. The


commands tools>dump>service>evpn>usage command contains the information that used to be in
the deprecated command, as well as new pieces of information.

Release 13.0.R3
This section describes the SR OS commands that have been renamed or deprecated in Release
13.0.R3.

VLL Services • The following command has been deprecated:


Commands tools>dump>epipe-map-to-network
and is replaced by:
tools>dump>epipe-map-access-to-egress-port
The new command has been enhanced with additional information.

Release 13.0.R2
No commands have been changed or deprecated in Release 13.0.R2 since Release 13.0.R1.

Release 13.0.R1
This section describes the SR OS commands that have been renamed or deprecated in Release
13.0.R1.

118 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

System
Commands

System • The following LAG load balancing commands in the config>system context have been
Commands moved one level deeper in the CLI hierarchy in a new load-balancing CLI context:
− [no] l4-load-balancing
− [no] lsr-load-balancing {lbl-only | lbl-ip | ip-only | eth-encap-ip}
− [no] mc-enh-load-balancing
− [no] system-ip-load-balancing
− [no] service-id-lag-hashing

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
system system
[no] l4-load-balancing load-balancing
[no] lsr-load-balancing {lbl-only|lbl- [no] l4-load-balancing
ip|ip-only|eth-encap-ip} [no] lsr-load-balancing {lbl-
[no] mc-enh-load-balancing only|lbl-ip|ip-only|eth-encap-ip}
[no] system-ip-load-balancing [no] mc-enh-load-balancing
[no] service-id-lag-hashing [no] system-ip-load-balancing
[no] service-id-lag-hashing

• Cron scripts have been generalized in order to share a common script control between cron
and the new Event Handling System (EHS) feature. The cron action CLI context and
commands have been renamed to script-policy and moved into a new
config>system>script-control CLI context along with the cron script CLI context. The
rest of the config>cron CLI context has been moved to the config>system>cron context.
Similar changes have been made for the show>cron and tools>perform>cron commands.
Some cron show routine output and log events have had minor textual adjustments to
generalize them for use with EHS.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
cron system
cron
configure configure
cron system
action script-control
script-policy script-policy-name
configure configure
cron system
schedule cron
action schedule
script-policy script-policy-name
show show
cron system
cron
script-control
script
script-policy

SR OS 13.0.R10 Software Release Notes 119


Changed or Deprecated Commands

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


clear clear
cron system
action script-control
tod script-policy
cron
tod
tools tools
perform perform
cron system
action script-control
script-policy

• The following PTP command has been renamed to align with the terminology used in the
ITU-T profiles:
config>system>ptp>peer>priority
and is changed to:
config>system>ptp>peer>local-priority

SNMP Commands • The following command has been renamed:


show system security communities
and is changed to:
show system security snmp community [community-name]
• The config>service>vprn>snmp-access and config>service>vprn>snmp-community
commands have been renamed as access and community, respectively, and have been
moved one level deeper in the CLI hierarchy in a new snmp CLI context.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
vprn service-id vprn service-id
snmp-access snmp
snmp-community access
community

QoS
Commands

Network QoS • The command multicast-policer used to redirect traffic to an ingress FP queue group
Policy Commands within the ingress section of a network QoS policy has been deprecated and replaced by
mcast-policer. When a system is booted using Release 13.0 and the configuration contains
a multicast-policer statement configured within a FC in the ingress of a network QoS
policy, the command is automatically converted to mcast-policer and expanded to create

120 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

both a broadcast-policer and an unknown-policer referencing the same FP ingress queue


group policer.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
qos qos
network network-policy-id create network network-policy-id create
ingress ingress
fc name fc name
fp-redirect-group multicast- fp-redirect-group mcast-policer
policer policer-id policer-id
fp-redirect-group broadcast-
policer policer-id
fp-redirect-group unknown-policer
policer-id

A warning message is displayed, indicating that multicast-policer command is deprecated


and the new command is mcast-policer.
Note that the naming of the multicast-policer within the SAP ingress QoS policy remains
unchanged.

Router
Config
Commands

IP Router • The following LAG commands in the config>router>interface context have been moved
Commands one level deeper in the CLI hierarchy to include the load-balancing context:
− [no] egr-ip-load-balancing {source | destination}
− [no] lsr-load-balancing {lbl-only | lbl-ip | ip-only | eth-encap-ip}
− [no] teid-load-balancing

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
router router
interface interface-name interface interface-name
[no] egr-ip-load-balancing load-balancing
{source|destination} [no] egr-ip-load-balancing
[no] lsr-load-balancing {lbl- {source|destination}
only|lbl-ip|ip-only|eth-encap-ip} [no] lsr-load-balancing {lbl-
[no] teid-load-balancing only|lbl-ip|ip-only|eth-encap-ip}
[no] teid-load-balancing

• The following command for resolution of a static route prefix using tunnels to an indirect
next-hop has been deprecated:
config>router>static-route {ip-prefix | prefix-length | ip-prefix netmask} indirect ip-
address {ldp| rsvp-te}[disallow-igp]

SR OS 13.0.R10 Software Release Notes 121


Changed or Deprecated Commands

and is replaced by:


config>router>static-route-entry {ip-prefix | prefix-length} indirect {ip-address}
tunnel-next-hop
The new command is an add-on to the existing command to configure the resolution to tun-
nel next-hops. As such, when upgrading to Release 13.0, a static route resolved to an indi-
rect next-hop using the ldp or rsvp-te values will be converted into a couple of
configuration lines as shown in the table below. The existing static-route command under
VPRN will continue to be supported in Release 13.0 and does not allow resolving to tun-
nels.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
router router
static-route {ip-prefix|prefix- static-route {ip-prefic|prefix-
length|ip-prefix netmask} lengthI|Iip-prefix netmask}
indirect {ip-address} {ldp|rsvp- indirect ip-address
te}[disallow-igp] static-route-entry {ip-prefix|prefix-
length|ip-prefix netmask}
indirect {ip-address}
tunnel-next-hop
[no] disallow-igp
resolution {disabled|any|filter}
resolution-filter
[no] ldp
[no] rsvp-te

Cflowd • The command to enable sampling under IP interfaces has been changed to accommodate
Commands options for sampling both unicast and multicast independently. The previous Cflowd
command under the IP interface context:
cflowd {acl | interface} [direction {ingress-only|egress-only|both}]
has been replaced with the following command within a new CLI context named cflowd-
parameters:
sampling {unicast | multicast} type {acl | interface} [direction {ingress-
only|egress-only|both}]
The sampling command can be issued independently to enable and control the sampling of
unicast and multicast traffic. Upon upgrade to Release 13.0, any existing Cflowd configura-
tion commands under IP interfaces in the Base-routing context or IP services (IES or
VPRNs) will be automatically converted to the new CLI syntax for unicast. Administrators
can then add an additional sampling command to enable multicast sampling.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
router router
interface interface-name interface interface-name
cflowd {acl|interface} [direction cflowd-parameters
{ingress-only|egress-only|both}] sampling {unicast|multicast} type
{acl|interface} [direction
{ingress-only|egress-only|both}]

122 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

Routing
Protocols
Commands

IS-IS Commands • In Release 13.0.R1, the suppress-default command is changed to ignore-attached-bit.


The following table displays changes in the config>router context; similar changes the
suppress-default command to also apply to the config>service>vprn context.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
router router
isis isis
suppress-default ignore-attached-bit

BGP Commands • The command for resolution of a BGP prefix using tunnels to a BGP next-hop (BGP
shortcut) has been deprecated:
config>router>bgp>igp-shortcut {ldp|rsvp-te|mpls|mpls-bgp}[disallow-igp]
and is replaced by:
config>router>bgp>next-hop-resolution>shortcut-tunnel
When upgrading to Release 13.0, the following values in the configuration file are con-
verted as follows:

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
router router
bgp bgp
igp-shortcut ldp next-hop-resolution
shortcut tunnel
family ipv4
resolution filter
resolution-filter ldp
... ...
igp-shortcut rsvp-te resolution filter
resolution-filter rsvp
... ...
igp-shortcut mpls resolution filter
resolution-filter ldp rsvp
... ...
igp-shortcut mpls-bgp resolution filter
resolution-filter bgp ldp rsvp

− The command for resolution of RFC 3107 BGP label route prefix using tunnels to a
BGP next-hop has been deprecated:
config>router>bgp>transport-tunnel {ldp|rsvp-te|mpls}
and is replaced by:
config>router>bgp>next-hop-resolution>label-route-transport-tunnel

SR OS 13.0.R10 Software Release Notes 123


Changed or Deprecated Commands

When upgrading to Release 13.0, the following values in the configuration file are con-
verted as follows:

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
router router
bgp bgp
no transport-tunnel next-hop-resolution
label-route-transport-tunnel
family ipv4
resolution filter
resolution-filter ldp
family vpn
resolution filter
resolution-filter ldp
... ...
transport-tunnel ldp family ipv4
resolution filter
resolution-filter ldp
family vpn
resolution filter
resolution-filter ldp
... ...
transport-tunnel rsvp-te family ipv4
resolution filter
resolution-filter rsvp
family vpn
resolution filter
resolution-filter rsvp
... ...
transport-tunnel mpls family ipv4
resolution filter
resolution-filter ldp rsvp
family vpn
resolution filter
resolution-filter ldp rsvp

MPLS
Commands

MPLS Commands • The following command has been deprecated:


config>router>mpls-labels>static-labels max-lsp-labels max-lsp-labels max-svc-
labels max-svc-labels
and is replaced by:
config>router>mpls-labels>static-label-range static-range
The static LSP and service label ranges are now collapsed into a single range usable by all
applications requiring a static label. During the upgrade to Release 13.0, the configuration
file is updated to reflect the new single static-label-range CLI with a range size matching
the value saved previously under the max-svc-labels parameter.

LDP Commands • With the introduction of LDP IPv6 in Release 13.0.R1, the LDP CLI has undergone major
changes. There are new commands, updates to existing commands, and deprecations of

124 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

commands. Changes to the CLI hierarchy also impact the configuration of LDP IPv4 peers
and targeted sessions. The following is a summary of the major changes. Numbered
explanations follow the table.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
router router
1 ldp ldp
peer-parameters session-parameters
peer ip-address peer ip-address
... ...
ldp ldp
2 peer-parameters tcp-session-parameters
peer ip-address peer-transport ip-address
... ...
ldp ldp
3 interface-parameters interface-parameters
ipv4
ipv6
... ...
ldp ldp
interface-parameters interface-parameters
4 interface ip-int-name interface ip-int-name [dual-
stack]
ipv4
ipv6
... ...
ldp ldp
5 interface-parameters interface-parameters
interface ip-int-name interface ip-int-name [dual-
stack]
... ...
ldp ldp
6 interface-parameters interface-parameters
interface ip-int-name interface ip-int-name
bfd-enable bfd-enable [ipv4][ipv6]
... ...
ldp ldp
7 targeted-session targeted-session
ipv4
ipv6
... ...
ldp ldp
interface-parameters interface-parameters
8 interface ip-int-name interface ip-int-name
multicast-traffic {enable|dis- ipv4
able} fec-type-capability
p2mp-ipv4 {enable|disable}
... ...
9 ldp-shortcut ldp-shortcut [ipv4|ipv6]

1. This change is made to better convey the scope of applicability of the commands which
apply to the LDP IPv4 or IPv6 session to a peer discovered over a link or to a targeted
peer. Only commands which apply to the LSR-ID are added to this scope. These com-
mands include per-peer FEC import and export policies and the label distribution mode
(DoD or DU).

SR OS 13.0.R10 Software Release Notes 125


Changed or Deprecated Commands

2. This change is made to better convey the scope of applicability of the commands which
apply to the transport address; that is, the address of the TCP connection, which is not
always the address corresponding to the LDP LSR-ID. These are the authentication,
TTL security and path-MTU discovery commands.
3. The user can now configure different default parameters for IPv4 and IPv6 LDP inter-
faces.
4. The user can now configure different parameters specific to a given IPv4 or IPv6 LDP
interface. Note that there is a single instance of the bfd-enable option under the inter-
face context.
The shutdown command exists under the main interface context and under each of the
interface IPv4 and IPv6 contexts.
− The shutdown command under the interface context brings down both IPv4 and
IPv6 Hello adjacencies and stops Hello transmission in both contexts.
− The shutdown command under the interface IPv4 or IPv6 contexts brings down
the Hello adjacency and stops Hello transmission in that context only.
The user can also delete the entire IPv4 or IPv6 context under the interface with the no
ipv4 or no ipv6 commands, which, in addition to bringing down the Hello adjacency,
will delete the configuration.
5. The dual-stack optional keyword is introduced to distinguish between the configura-
tion file executions of prior releases from that in Release 13.0, as the interface node
implementation has changed in Release 13.0 to include new IPv4 and IPv6 contexts.
The key points of the new implementation are:
− If the keyword is provided, then IPv4 interface context will not be created. If it is
not provided, the IPv4 interface context will be created. This will take care of
executions of prior to Release 13.0 configurations on a router running a Release
13.0 image.
− This new keyword will always show in a Release 13.0 configuration.
− When entering an already configured interface, there is no need to provide the
keyword, but it will be ignored if provided.
When deleting a configured interface, the keyword will not be accepted in the no ver-
sion of the interface command.
6. The ipv4 and ipv6 keywords are optional keywords; if no keyword is chosen, then ipv4
is assumed to be enabled for backward compatibility.
The operation of BFD over an LDP interface is enhanced such that it tracks the next-
hop of prefix IPv4 and prefix IPv6 in addition to its tracking of the LDP peer IPv4/IPv6
address of the Hello adjacency over that link.
7. The user can now configure different default parameters for IPv4 and IPv6 LDP tar-
geted Hello adjacencies.
8. The enabling or disabling of the resolution of mLDP P2MP FEC over an interface is
replaced with the Hello adjacency FEC type capability. The latter improves the original
behavior by adding negotiation of the P2MP FEC type capability with the peer for each
interface and the ability to separately enable or disable mLDP IPv4 FEC and IPv6 FEC
types.
9. The ipv4 and ipv6 keywords are optional keywords; if no keyword is chosen, then ipv4
is assumed to be enabled for backward compatibility.

126 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

The user can now enable LDP shortcuts separately for IGP IPv4 and IPv6 prefixes. This
CLI command has the following behaviors:
− When executing a pre-Release 13.0 configuration file, the existing command is
converted as follows:
config>router>ldp-shortcut changed to config>router>ldp-shortcut ipv4
− If the user enters the command without the optional arguments in the Release
13.0 CLI, it defaults to enabling shortcuts for IPv4 IGP prefixes:
config>router>ldp-shortcut changed to config>router>ldp-shortcut ipv4
− When the user enters both IPv4 and IPv6 arguments in the Release 13.0 CLI,
shortcuts for both IPv4 and IPv6 prefixes are enabled:
config>router>ldp-shortcut ipv4 ipv6
• The following table details the changes to the syntax of the show commands to better
convey the scope of applicability of the command. Numbered explanations follow the
table.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


show show
router router
1 ldp ldp
peer targ-peer
... ...
2 ldp ldp
peer-parameters session-parameters
... ...
3 ldp ldp
peer-template targ-peer-template
... ...
4 ldp ldp
peer-template-map targ-peer-template-map
... ...
ldp ldp
5
auth-keychain tcp-session-parameters [keychain
keychain]
... ...
ldp ldp
bindings bindings
6
prefix ip-prefix/ip-prefix-length prefixes
prefix ip-prefix|ip-prefix-
length
... ...
ldp ldp
bindings bindings
7 active active
prefixes
prefix ip-prefix|ip-prefix-
length
... ...
8 ldp ldp
status statistics
... ...
9 ldp ldp
bindings bindings [ipv4|ipv6]

SR OS 13.0.R10 Software Release Notes 127


Changed or Deprecated Commands

1. Command shows parameters configured under config>router>ldp>targ-session>peer


x.y.z.w.
2. Command shows parameters configured under config>router>ldp>session-parame-
ters>peer x.y.z.w.
3. Command shows parameters configured under config>router>ldp>targ-session peer-
template.
4. Command shows parameters configured under config>router>ldp>targ-ses-
sion>peer-template-map.
5. The output of the show router ldp auth-keychain command can now be displayed
using show router ldp tcp-session-parameters [keychain keychain]
6. The show router ldp bindings prefix command has been moved one level deeper in
the CLI hierarchy in a new prefixes CLI context.
7. A new prefixes level in the CLI hierarchy has been added to the show router ldp
binding context to display the unicast IPv4/IPv6 FECs.
8. Some commands related to statistics, previously displayed under the show router ldp
status context, have now been moved to the new show router ldp statistics context.
9. The ipv4 and ipv6 keywords are a new subcontext to this command, so that the user
can specify the family in this context, rather than for each command in a deeper level in
the CLI hierarchy.
• The following changes to the syntax of the clear and debug commands were made to better
convey the scope of the applicability of the command. Numbered explanations follow the
table.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


clear clear
router router
1 ldp ldp
instance instance family [ipv4|ipv6]
... ...
ldp ldp
2
interface ip-int-name interface ip-int-name [family
[ipv4|ipv6]]
debug debug
router router
3 ldp ldp
interface interface-name interface interface-name {family
{ipv4|ipv6}}

1. The ipv4 and ipv6 keywords are optional keywords; if no keyword is chosen, both ipv4
and ipv6 states are cleared.
2. The ipv4 and ipv6 keywords are optional keywords; if no keyword is chosen, both ipv4
and ipv6 states are cleared.
3. The ipv4 and ipv6 keywords are mandatory.

128 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

Layer-2
Services
Commands

VLL Services • The per-service-hashing command in the config>service>epipe context has been moved
Commands one level deeper in the CLI hierarchy to include the load-balancing context. The old
command will still be accepted if it comes from a configuration file but will not be
available in interactive CLI. There is no change from SNMP/MIB.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
epipe service-id epipe service-id
per-service-hashing load-balancing
per-service-hashing

VPLS Services • The following command has been deprecated:


Commands config>service>vpls>allow-ip-int-binding
and is replaced by:
config>service>vpls>allow-ip-int-bind.
The latter is a CLI node, allowing the future addition of sub-commands below it.
• The per-service-hashing commands in the config>service>vpls and
config>service>template>vpls-template contexts have been moved one level deeper in
the CLI hierarchy to include the load-balancing context. The old command will still be
accepted if it comes from a configuration file but will not be available in interactive CLI.
There is no change from SNMP/MIB.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
vpls service-id vpls service-id
per-service-hashing load-balancing
per-service-hashing
... ...
template template
vpls-template name vpls-template name
per-service-hashing load-balancing
per-service-hashing

SR OS 13.0.R10 Software Release Notes 129


Changed or Deprecated Commands

Layer-3
Services
Commands

IES Commands • The following LAG commands in the config>service>ies>interface context have been
moved one level deeper in the CLI hierarchy to include the load-balancing context:
− [no] egr-ip-load-balancing {source | destination}
− [no] teid-load-balancing

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
ies service-id ies service-id
interface ip-int-name interface ip-int-name
[no] egr-ip-load-balancing load-balancing
{source|destination} [no] egr-ip-load-balancing
[no] teid-load-balancing {source|destination}
[no] teid-load-balancing

VPRN Services • The following LAG commands in the config>service>vprn>interface context have been
Commands moved one level deeper in the CLI hierarchy to include the load-balancing context:
− [no] egr-ip-load-balancing {source | destination}
− [no] teid-load-balancing

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
vprn service-id vprn service-id
interface ip-int-name interface ip-int-name
[no] egr-ip-load-balancing load-balancing
{source|destination} [no] egr-ip-load-balancing
[no] teid-load-balancing {source|destination}
[no] teid-load-balancing

• The following LAG commands in the config>service>vprn>network-interface context


have been moved one level deeper in the CLI hierarchy to include the load-balancing
context:
− [no] egr-ip-load-balancing {source | destination}
− [no] lsr-load-balancing {lbl-only | lbl-ip | ip-only | eth-encap-ip}
− [no] teid-load-balancing

130 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
vprn service-id vprn service-id
network-interface interface-name network-interface interface-name
[no] egr-ip-load-balancing load-balancing
{source|destination} [no] egr-ip-load-balancing
[no] lsr-load-balancing {lbl- {source|destination}
only|lbl-ip|ip-only|eth-encap-ip} [no] lsr-load-balancing {lbl-
[no] teid-load-balancing only|lbl-ip|ip-only|eth-encap-
ip}
[no] teid-load-balancing

• The command for resolution of a VPN-IPv4 or VPN-IPv6 prefix to a BGP next-hop has
been renamed:
config>service>vprn>auto-bind {ldp|gre|rsvp-te|mpls|mpls-gre}
and is changed to
config>service>vprn>auto-bind-tunnel
When upgrading to Release 13.0, the following values in VPRN auto-bind in the configura-
tion file will be converted as follows:

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
vprn service-id vprn service-id
auto-bind gre auto-bind-tunnel
resolution filter
resolution-filter gre
... ...
auto-bind ldp auto-bind-tunnel
resolution filter
resolution-filter ldp
... ...
auto-bind mpls auto-bind-tunnel
resolution filter
resolution-filter ldp rsvp
... ...
auto-bind mpls-gre auto-bind-tunnel
resolution filter
resolution-filter gre ldp rsvp
... ...
auto-bind rsvp-te auto-bind-tunnel
resolution filter
resolution-filter rsvp-te

SR OS 13.0.R10 Software Release Notes 131


Changed or Deprecated Commands

Subscriber
Management
Commands

Subscriber • In Release 13.0.R1, the relay-unicast-msg CLI command has been renamed to relay-
Management proxy. The conversion from relay-unicast-msg to relay-proxy is done transparently so
DHCP Commands configurations saved in releases prior to Release 13.0.R1 can still be executed without
problem. There are no changes to the MIB field names.
A comparison of syntax prior to Release 13.0.R1 and in Release 13.0.R1 is as follows:

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
service service
ies service-id ies service-id
interface ip-int-name interface ip-int-name
dhcp dhcp
relay-unicast-msg [release- relay-proxy [release-update-src-
update-src-ip] ip] [siaddr-override ip-address]
no relay-unicast-msg no relay-proxy
... ...
ies service-id ies service-id
subscriber-interface ip-int-name subscriber-interface ip-int-name
group-interface ip-int-name group-interface ip-int-name
dhcp dhcp
relay-unicast-msg [release- relay-proxy [release-update-src-
update-src-ip] ip] [siaddr-override ip-
no relay-unicast-msg address]
no relay-proxy
configure configure
service service
vprn service-id vprn service-id
interface ip-int-name interface ip-int-name
dhcp dhcp
relay-unicast-msg [release- relay-proxy [release-update-src-
update-src-ip] ip] [siaddr-override ip-address]
no relay-unicast-msg no relay-proxy
... ...
vprn service-id vprn service-id
subscriber-interface ip-int-name subscriber-interface ip-int-name
dhcp dhcp
relay-unicast-msg [release- relay-proxy [release-update-src-
update-src-ip] ip] [siaddr-override ip-address]
no relay-unicast-msg no relay-proxy
... ...
vprn service-id vprn service-id
subscriber-interface ip-int-name subscriber-interface ip-int-name
group-interface ip-int-name group-interface ip-int-name
dhcp dhcp
relay-unicast-msg [release- relay-proxy [release-update-src-
update-src-ip] ip] [siaddr-override ip-
no relay-unicast-msg address]
no relay-proxy

132 SR OS 13.0.R10 Software Release Notes


Changed or Deprecated Commands

Subscriber • In Release 13.0.R1, the host-limit command has been deprecated and replaced with host-
Management limits overall and remove-oldest.
Commands

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
subscriber-mgmt subscriber-mgmt
sla-profile sla-profile-name [create] sla-profile sla-profile-name [create]
host-limit max-number-of-hosts host-limits
[remove-oldest] overall max-nr-of-hosts
[no] remove-oldest

MS-ISA/
MS-ISA2
Application
Commands

Application • The following command has been deprecated:


Assurance mirror-dest isa-aa-group
Commands
• In Release 13.0.R1, the following commands have been changed. Numbered explanations
follow the table.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


configure configure
application-assurance application-assurance
group aa-group id:partition-id group aa-group id:partition-id
url-filter-name url-filter-name
1
icap-http-redirect http-redirect
icap
server
vlan-id
configure configure
application-assurance application-assurance
group aa-group id:partition-id group aa-group id:partition-id
statistics statistics
2
aa-sub aa-sub
aggregate-stats aggregate-stats
export-using accounting-pol-
icy
show tools
application-assurance dump
group aa-group id:partition-id application-assurance
3 aa-sub-list group aa-group id:partition-id
policers-exceeded aa-sub-list [filter-by-type sub-
type] [isa mda-id]
policers-exceeded

1. With the introduction of local-filtering in the url-filter policy, the icap-http-redirect


command is renamed http-redirect, and both server and vlan-id are moved to the icap
context of the url-filter

SR OS 13.0.R10 Software Release Notes 133


Changed or Deprecated Commands

2. The following command:


statistics aa-sub aggregate-stats
is replaced by:
statistics aa-sub aggregate-stats export-using accounting-policy.
3. The following command has been deprecated:
show application-assurance group aa-sub-list policers-exceeded
and is replaced by:
tools dump application-assurance group aa-sub-list [filter-by-type sub-type]
[isa mda-id] policers-exceeded

OAM
Commands

Diagnostics • As of Release 13.0.R1, legacy and Alcatel-Lucent-specific OAM commands no longer


Commands support the send-control option. Operators should stop using the send-control option with
the following OAM functions for both interactive CLI, SNMP and SAA:
− cpe-ping
− mac-ping
− mac-populate
− mac-purge
− mac-trace
With Release 13.0.R1, the send-control option will no longer be available. All SAA tests
that include this option will fail to start as of Release 13.0.R1. This option must be removed
from the SAA tests.

Tools Commands • The SAP and MPLS binding loopback with MAC swap commands in the tools>perform>
service>id>loopback>sap and tools>perform>service>id>loopback>sdp contexts have
been moved one level deeper in the CLI hierarchy under the eth context to more accurately
represent the Ethernet loopback function.

Command Prior to Release 13.0.R1 Command in Release 13.0.R1


tools tools
perform perform
service service
id service-id id service-id
loopback loopback
sap eth
sap
... ...
loopback loopback
sdp eth
sdp

134 SR OS 13.0.R10 Software Release Notes


Usage Notes

Usage Notes
The following information supplements or clarifies information in the manuals for Release
13.0.R10 of SR OS.

XCM and SFM • In a 7950 XRS system, at least one SFM must be fully operational in order for the XCMs,
Recovery XMAs and standby CPM to be in service. If there are no operating SFMs in the system,
Behavior then the XCMs, XMAs and standby CPM will be held in a “booting” operational state.
• In a 7950 XRS system, at least one C-XMA/XMA in an XCM must be fully operational for
the XCM to be in service. If there are no operating C-XMAs/XMAs in an XCM, then the
XCM will be held in a “booting” operational state.

7750 SR-12e • For optimal performance, Alcatel-Lucent recommends that up to four (4) FP2-based
IOMs/IMMs for the 7750 SR-12e are installed in up to four (4) consecutive slots (for
example, slots 1-4 or 2-5).

7450 ESS-7/12 and • Specific engineering rules may apply when mixing FP2- and FP3-based line cards; contact
7750 SR-7/12/12e your Alcatel-Lucent representative for further details.

Multiservice The following tables list IOM and IMM support for MS-ISA/MS-ISA2 applications:
Integrated
Services Adapter Table 30. Compatible 7750 SR IOMs and IMMs for MS-ISA/MS-ISA2 Applications
(MS-ISA/MS-ISA2)
MS-ISM/MS-ISA2 IMM

MS-ISA2-E on IOM4-e

MS-ISA2-E on IOM-e
MS-ISA2 on IOM4-e

MS-ISA2 on IOM-e
IOM3-XP/-b/-c
IOM-20g-b

MS-ISM-E
IOM2-20g

Application Assurance ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓ ✓
(isa-aa/isa2-aa)1,2

Retransmission and Fast Channel ✓ ✓ ✓


Change (isa-video)

Video Quality Monitoring ✓ ✓ ✓


(isa-video)

Video Dual Stream Selection ✓ ✓ ✓


(isa-video)

Local/Zoned Ad Insertion ✓ ✓ ✓
(isa-video)

SR OS 13.0.R10 Software Release Notes 135


Usage Notes

Table 30. Compatible 7750 SR IOMs and IMMs for MS-ISA/MS-ISA2 Applications

MS-ISM/MS-ISA2 IMM

MS-ISA2-E on IOM4-e

MS-ISA2-E on IOM-e
MS-ISA2 on IOM4-e

MS-ISA2 on IOM-e
IOM3-XP/-b/-c
IOM-20g-b

MS-ISM-E
IOM2-20g
Tunnel Services, including IPsec ✓3 ✓3 ✓ ✓
(isa-tunnel/isa2-tunnel)1

Network Address Translation ✓ ✓ ✓ ✓ ✓ ✓ ✓


(isa-bb/isa2-bb)1

L2TP LNS Service ✓ ✓ ✓ ✓ ✓


(isa-bb/isa2-bb)

WLAN-GW (isa-bb/isa2-bb) ✓ ✓4 ✓5 ✓6 ✓6

Arbor TMS (isa-tms) ✓

1. Application Assurance, Tunnel and IPsec services and NAT are also supported on the 7750
SR-c12.
2. Application Assurance is also supported on the 7750 SR-c4.
3. MS-ISA only. Not supported on MS-ISA-E.
4. MS-ISM only. Not supported on IMM.with a single MS-ISA2.
5. MS-ISM-E only. Not supported on IMM with a single MS-ISA2-E.
6. Requires both MDA slots in the IOM4-e to be equipped with MS-ISA2 (-E) cards.

Table 31. Compatible 7450 ESS IOMs and IMMs for MS-ISA/MS-ISA2 Applications
MS-ISM/MS-ISA2 IMM

MS-ISA2-E on IOM4-e
MS-ISA2 on IOM4-e
MS-ISA2-E IMM
IOM3-XP/-b/-c
IOM-20g-b

MS-ISM-E

Application Assurance (isa- ✓ ✓ ✓ ✓ ✓ ✓


aa/isa2-aa)

Retransmission and Fast Channel


Change ✓ ✓
(isa-video)

136 SR OS 13.0.R10 Software Release Notes


Usage Notes

Table 32. Compatible 7450 ESS Mixed Mode IOMs and IMMs for MS-ISA/MS-ISA2
Applications

MS-ISM/MS-ISA2 IMM

MS-ISA2-E on IOM4-e
MS-ISA2 on IOM4-e
MS-ISA2-E IMM
IOM3-XP/-b/-c

MS-ISM-E
Application Assurance ✓ ✓ ✓ ✓ ✓
(isa-aa/isa2-aa)

Retransmission and Fast Channel


Change ✓
(isa-video)

Tunnel Services, including IPsec ✓1 ✓ ✓


(isa-tunnel/isa2-tunnel)

Network Address Translation ✓ ✓ ✓ ✓ ✓


(isa-bb/isa2-bb)

L2TP LNS Service ✓ ✓ ✓


(isa-bb/isa2-bb)

1. MS-ISA only. Not supported on MS-ISA-E.

Compact Flash • Only Alcatel-Lucent-sourced Compact Flash devices for the SR OS are supported.
Devices • In Release 13.0.R1 and higher, Alcatel-Lucent recommends that the compact flash in the
CF3 slot be at least 2 Gbytes. The extra compact flash space is intended to support
customers who may want to keep more than one copy of the software.
• Alcatel-Lucent recommends using cf1: or cf2: for event logs and dynamic data persistency.

HW/Platform • SFPs with bad checksums cause traps and log events. The port will be kept operationally
down with SFPs that fail to read or have invalid checksums. [62458]
• When a dual-rate SFP is connected to a GigE LX SFP, the auto-negotiation parameter must
be turned off in order to get a link. [67690]
• Replacing an MS-ISA with another MDA type (that is, non MS-ISA MDA type) requires
the IOM to be reset after the new MDA is installed and configured. The IOM reset is only
required for types IOM-20g-b and IOM2-20g; IOM3-XPs do not require any action. If the
IOM was not reset after replacing the MS-ISA, the IOM may reset in the future. For more
information, refer to TA 12-0058.
• The SR OS routers support qualified pluggable optic modules only. Refer to the current
Alcatel-Lucent price list for supported modules. Third-party optics are not supported.

SR OS 13.0.R10 Software Release Notes 137


Usage Notes

System • When creating a new log file on a Compact Flash disk card, the system will check the
amount of free disk space and the amount must be greater than or equal to the lesser of
5.2 MB or 10% of the Compact Flash disk capacity.
• SNMPv3 user authentication and privacy keys in the configure system security user user-
name snmp authentication command must be entered as maximum length strings.
[18314]
• Manual editing of SNMP persistent index files can cause errors in loading the
configuration file. Persistent index files should only be created by the system. [24327]
• Downgrading from chassis mode C to chassis mode B may require the removal of IPv6
addresses from the BOF configuration. [133960]
• When nodes are run in FIPS-140-2 mode (where only FIPS-140-2 algorithms are enabled
and allowed), Alcatel-Lucent recommends only enabling the FIPS-140-2 mode on newly
deployed nodes. Changing to FIPS-140-2 mode on live nodes should be avoided as there
may be conflicts with existing configurations that are not consistent when running the node
in FIPS-140-2 mode. Before enabling a pre-configured node to run in FIPS-140-2 mode,
ensure all configurations in the configuration file are devoid of conflicting configurations
that are not allowed in FIPS mode, such as the use of any unapproved cryptographic
algorithms or certificates that are signed with unapproved algorithms. Refer to the Basic
System Configuration Guide for details.

SONET/SDH • The show port command on a SONET/SDH interface will only display the bottom 4 bits of
the S1 byte but will incorrectly display the bits as an entire byte. [17364]

ATM • 7750 SR and 7450 ESS in mixed mode allow configuration of user traffic on reserved ATM
Forum UNI specification VCI values (VCIs from 0 to 31 inclusive). Alcatel-Lucent
recommends not configuring any user traffic on those VCIs on any VP as other equipment
may treat that traffic per the defined usage reserved to a given VCI value. Additionally,
users must not configure VCIs 0, 3, 4, 6, and 7 on any VPI for services on ASAP MDAs, as
those VCIs are exclusively used for their ATM Forum defined and reserved functionality.
[53205]

MLPPP • When a MLPPP bundle is out of service (oos), the Oper MTU and Oper MRRU are derived
from the configured MRRU.
• Currently, LCP echo ids from 0–255 are separated into two ranges:
− 0–127 is used for keepalive function
− 128–255 is used for differential delay detection.
Keepalive statistics only count echo packets with IDs from 0-127.
• In order to interoperate with other vendors’ MLPPP implementations, the MLPPP sub-
layer will accept packets with or without leading zeros in the protocol field even though the
7750 SR and 7450 ESS in mixed mode do not advertise the protocol field compression
(PFC) option during LCP negotiation. [25996, 29923]

APS • Alcatel-Lucent recommends that the lb2er-sd and lb2er-sf alarms be enabled for
SONET/SDH ports belonging to APS groups to better understand some APS group
switchovers between the working and protect circuits.

138 SR OS 13.0.R10 Software Release Notes


Usage Notes

• For SONET/SDH ports belonging to APS groups that have a very large difference in the
transmission delay between the working and protect circuits, Alcatel-Lucent recommends
that the hold down timers be increased from their default values.
• Increased APS group scaling (above 32 MC-APS and 64 SC-APS) requires CPM3 or
higher for optimal switchover performance during failures affecting multiple groups.
Alcatel-Lucent recommends CPM3 or higher for APS group scaling over 64 groups.

TCP • Keychains with no active entries will keep LDP and BGP peerings down. [57917]
Authentication
Extension

Routing • Alcatel-Lucent recommends that the preference value for BGP routes be set to a higher
value than that of the internal (IGP) routes used to resolve the next-hop addresses of iBGP
routes or routing instability can occur while the BGP routes are constantly re-learned.
[31146]

Disallowed IP • The following IP address prefixes are not allowed by the unicast routing protocols and the
Prefixes Route Table Manager and will not be populated within the forwarding table:
− 0.0.0.0/8 or longer
− 127.0.0.0/8 or longer
− 224.0.0.0/4 or longer (used for multicast only)
− 240.0.0.0/4 or longer
Any other prefixes that need to be filtered can be filtered explicitly using route policies.

IS-IS • The granularity of the IS-IS hold timer is accurate only to within +/- 0.5s, so having a
computed holdtime value of less than 2s may result in adjacencies being randomly
dropped. Alcatel-Lucent recommends that hello-intervals and hello-multiplier values be
adjusted accordingly, paying specific attention to the smaller hold-times computed on DIS
systems. [29490]
• IS-IS authentication is not activated at any given level or interface unless both the
authentication key and type are added at that level. For instance, if hello-authentication-
type is set to password for an interface, it is not activated until a key is added at the
interface level. [34256]

IS-IS TE • The protocol sends advertisements with the IS-IS Traffic Engineering (TE) Router ID TLV
when traffic engineering is disabled. [17683]

Auto-derived • In a VPLS service, multiple BGP families and protocols can be enabled at the same time.
Route- When bgp-evpn is enabled, bgp-ad and bgp-mh are also supported. It is important to note
Distinguisher (RD) that a single RD is used per service and not per BGP family/protocol. The following rules
in services with apply.
multiple BGP − The VPLS RD is selected based on the following precedence:
families
− manual-RD or auto-RD always take precedence when configured

SR OS 13.0.R10 Software Release Notes 139


Usage Notes

− if there is no manual-RD/auto-rd configuration, the RD is derived from the bgp-


ad>vpls-id
− if there is no manual-RD/auto-rd/vpls-id configuration, the RD is derived from
the bgp-evpn>evi.
− if there is no manual-RDauto-rd/vpls-id/evi configuration, there is no RD, and
thus the service will fail
− The selected RD (see above rules) will be shown in the “Oper Route Dist” field of the
show service id bgp command.
− The service supports RD changes dynamically; for instance, the CLI allows the vpls-
id to be changed even while it is being used to auto-derive the service RD for bgp-ad,
bgp-vpls or bgp-mh. Note that, when the RD changes, the active routes for that
VPLS will be withdrawn and re-advertised with the new RD.
− If one of the mechanisms to derive the RD for a given service is removed from the
configuration, the system will select a new RD based on the above rules. For
example, if the vpls-id is removed from the configuration, the routes will be
withdrawn, the new RD selected from the evi, and the routes re-advertised with the
new RD.
− Note that this de-configuration will fail if the new RD already exists in a different
VPLS or Epipe.
− Because the vpls-id takes precedence over the evi when deriving the RD
automatically, adding evpn to an existing bgp-ad service will not impact the existing
RD—this is important to support bgp-ad to evpn migration.

BGP • Alcatel-Lucent recommends that the local address be configured when a router has
multiple BGP peers to the same node. [113614]
• The static blackhole route should be created prior to receiving routes or creating the policy
in combination with autobind GRE. [160617]

BGP Auto- • On the 7450 ESS without mixed mode, only the L2-VPN address family is supported by
Discovery BGP. This address family is used for BGP Auto-discovery for VPLS. Any commands or
options for other address families in BGP or in routing policies are not supported on the
7450 ESS except in mixed mode.

BGP VPWS • When a provisioned SDP that is used for a spoke-SDP is shut down, or there is a local LSP
failure (causing the spoke-SDP to go down), a BGP-VPWS update will be sent to the
adjacent PE with the CSV bit set to one (1). This, however, does not cause the spoke-SDP,
site or SAP to go down on the adjacent PE. If the adjacent PE is the designated forwarder
of a pair of dual-homed PEs, no designated forwarder failover occurs. The above situation
can result in the designated forwarder being one of the dual-homed PEs but the remote PE
using its pseudowire to the other dual-homed PE.

MPLS/RSVP • The current bypass binding selection logic for Release 7.0 and higher is the following:
− For non-strict environment
a) Manual CSPF disjoint bypass

140 SR OS 13.0.R10 Software Release Notes


Usage Notes

b) Manual CSPF !disjoint bypass


c) Dynamic CSPF disjoint bypass
d) Dynamic CSPF !disjoint bypass
− For strict environment
a) Manual CSPF disjoint bypass
b) Dynamic CSPF disjoint bypass
The above binding order has two (2) collateral/detrimental effects when the non-strict
option is selected:
1. In presence of a disjoint Dynamic Bypass, a non-disjoint Manual Bypass may be
selected instead.
2. Non-CSPF Manual Bypass will never be selected. [66005]
• The enabling or disabling of Diff-Serv on the system requires that the RSVP and MPLS
protocols be shut down. When first created in Release 7.0 or higher, RSVP and MPLS will
be administratively down. The user must execute the no shutdown command for each
protocol once all parameters under both protocols are defined. When saved in the
configuration file, the no shutdown command is automatically inserted under both
protocols to ensure they come up after a node reboot. In addition, the saved configuration
file is organized so that all LSP-level and LSP path-level configuration parameters are
executed after all MPLS and RSVP global- and interface-level parameters are executed.
• LSP MTU negotiation for P2MP LSP is not supported. End-to-end MTU along the S2L
path needs to be large enough to support data traffic. [74835]

LDP • On LDP interfaces and targeted-session keepalive commands, Alcatel-Lucent


recommends that the factor setting be set to a value greater than 1 or it may lead to
unexpected drops in LDP peerings. [67153]
• When a per-peer import/export policy, which is either non-existing, incorrectly configured
or not committed yet is configured, it may result in the system rejecting any FEC from
being imported/exported. The workaround is to ensure that the configuration files do not
contain policy mis-configurations or mismatches between LDP and the policy manager.

IP Multicast • If an rp static-address is configured, the current PIM implementation will install an


implicit deny-all for 224.0.0.0/4. To re-permit this address range, another static entry for
this range must be installed. [38630]
• MoFRR for PIM interfaces should be enabled on a hop-by-hop basis to ensure optimal
MoFRR recovery.
• If auto-rebalancing is enabled, re-balancing when a new path becomes available is
performed for active joins.
• Optimized IP-multicast replication over RSVP-TE spoke-SDPs using configurable
multicast network domains requires all spoke interfaces to be configured exclusively on
physical ports, LAG ports, or APS-protected ports. If that is not the case, the default
replication will take place.
• To execute mtrace and mstat with protocol-protection enabled (config>security>cpu-
protection), IGMP must be enabled on incoming interfaces. [160402]

SR OS 13.0.R10 Software Release Notes 141


Usage Notes

PIM • To ensure proper GRT/VRF extranet functionality, it is strongly recommend to shut down
PIM inside the VPRN (config>service>vprn>pim>shutdown) when enabling grt-
extranet functionality in this VPRN under the following cases:
− enabling grt-extranet for the first time in the VPRN
− configuring grt-extranet group-prefix any or grt-extranet group-prefix
224.0.0.0/4
− configuring grt-extranet group-prefix for a group that is already present in the
VPRN.
To ensure proper per-group map extranet functionality, it is strongly recommend to shut
down PIM inside the receiver VPRN (config>service>vprn>pim>shutdown) when
enabling the per-group mapping extranet functionality in this VPRN under the following
cases:
− enabling per-group mapping for the first time in the VPRN (that is, configuring the
first map entry)
− configuring group-prefix 224.0.0.0/4 inside the map (that is, mapping all multicast
groups to one core instance). [186280]

QoS • By default, the CBS value of newly-created queues in queue-group policies is zero (0)
percent. Adding queue-groups or other configuration may result in reservation of all
available buffer space (CBS) so that there is no shared buffer space available and queues
with CBS of zero (0) percent will drop traffic. Expedited traffic for newly-created queues
in queue-group policies with default CBS of zero (0) percent may also be lost when there is
congestion of non-expedited traffic. To prevent the loss of traffic, Alcatel-Lucent
recommends that the CBS value be changed to at least one (1) percent for expedited and
non-expedited queues, or for non-expedited queues, to ensure that shared buffer space is
available. Buffer memory can be monitored with the show pools command. [86843]
• On the SR-a4/a8, ingress multipoint traffic is forwarded using shared queuing instead of
the multipoint shared queuing. Specifically, the first pass through the FP uses the regular
service queues and the second pass uses the default shared unicast queues instead of the
default shared multipoint queues. Consequently, any parameter changes (for example, rates
and MBS/CBS) applied to the default shared multipoint queues will not have any effect on
the received multipoint traffic. [184678]
• profile-mode queues in FP3 platforms use two (2) offered statistic counters as opposed to
four (4) in non-FP3 platforms. This means FP3 unicast profile-mode queues provide
offered-uncolored and a combined in-/out- profile offered-colored statistics. FP3 multicast
profile-mode queues provide a combined offered-combined statistics and an offered-
mcast-managed statistics for managed multicast. Starting in Release 10.0.R1, multicast
profile-mode queues on non-FP3 platforms report offered-uncolored and offered-managed
using separate counters. No new MIB object is added as part of these statistics changes.
Since existing MIB objects are used, non-FP3 profile-mode multicast queue offered-
managed and offered-uncolored are accounted using the same MIB object. The show
command output displays offered-managed and offered-uncolored as separate statistics for
profile-mode non-FP3 multicast queues. The show command output also displays
different statistic counters based on platform type.

142 SR OS 13.0.R10 Software Release Notes


Usage Notes

Filter Policies • Starting with Release 11.0.R1, the maximum number of filter policies and filter policy
entries per system is larger than the line card limit. Since filter statistics are maintained on
line cards and aggregated on the CPM/CFM, when an entry is deleted from a given line
card (that is, an entry is deleted, or a given filter policy is no longer used on a given line
card), the CPM/CFM resets that entry’s counters to zero. If the counters are required, they
should be retrieved prior to such a configuration change.
• Alcatel-Lucent recommends against deploying the same filter policy on both ingress and
egress because ingress and egress filter policies support different functionalities (actions
and/or match criteria).
• Using a filter policy on a line card or in a direction that does not support a given match
criterion may result in an unexpected match by the filter entry. It is recommended to avoid
such configurations.
• When a filter policy is used on a line card that does not support a given action or in a
direction that does not support that action, the action is ignored; if the packet matches the
entry, default action is executed.
• Starting from Release 11.0.R1, all newly-introduced filter policy functionality is no longer
supported in combination with ToD functionality. Alcatel-Lucent recommends against
configuring a filter policy that has both ToD and Release 11.0.R1 or newer filter policy
enabled.

Services General • Starting in Release 10.0.R3, a PW port needs to be created first (with encap-type dot1q or
qinq) before it can be bound to the SDP. Configurations containing PW-port entries from
releases prior to Release 10.0.R3 are not compatible. [134086]

Proxy-ARP/ND When enabling Proxy-ARP/ND in a VPLS service, Alcatel-Lucent recommends the following
recommended configuration for the correct network behavior:
settings • Alcatel-Lucent recommends enabling dynamic-arp-populate or dynamic-nd-populate
only in networks with a consistent configuration of this command in all PEs. In EVPN
networks where some nodes do not support this feature, dynamic-arp-populate and
dynamic-nd-populate should only be enabled if the EVPN nodes always advertise IP-
>MAC pairs in MAC routes. For example, when an SR OS router is used as a Data Center
(DC) Gateway for a Nuage DC, the user should enable dynamic-arp-populate only if all
the Nuage Vports in the service are type host or VM (since their IPs will be advertised in
MAC routes).
• When using dynamic-arp-populate/dynamic-nd-populate, the age-time value should be
configured to a value equal to three times the send-refresh value. This will help reduce the
EVPN withdrawals and re-advertisements in the network.
• In case of large age-time values, it would be sufficient to configure the send-refresh value
to half of the proxy-ARP/ND age-time or FDB age-time.
• In scaled environments (with thousands of services) it is not recommended to set the send-
refresh value to less than 300 seconds. In such scenarios, Alcatel-Lucent recommends
using a minimum proxy-ARP/ND age-time and FDB age of 900 seconds.
• The use of the following commands reduces or suppresses the ARP/ND flooding in an
EVPN network, since EVPN MAC routes replace the function of the regular data plane
ARP/ND messages:
− no garp-flood-evpn

SR OS 13.0.R10 Software Release Notes 143


Usage Notes

− no unknown-arp-request-flood-evpn
− no unknown-ns-flood-evpn
− no host-unsolicited-na-flood-evpn
− no router-unsolicited-na-flood-evpn
Alcatel-Lucent recommends using these commands only in EVPN networks where the CEs
are routers directly connected to an SR OS node acting as the PE. Networks using aggrega-
tion switches between the host/routers and the PEs should flood GARP/ND messages in
EVPN to make sure the remote caches are updated and BGP does not miss the advertise-
ment of these entries.
• When the anti-spoof-mac is used with Proxy-ARP/ND, ingress filters (in the access
SAPs/SDP-bindings) should be configured to drop all traffic with destination anti-spoof-
mac. The same MAC should be configured in all PEs where dup-detect is active.
• When Proxy-ND is used, the configuration of the following commands should be
consistent in all the PEs in the network:
− router-unsolicited-na-flood-evpn
− host-unsolicited-na-flood-evpn
− evpn-nd-advertise
Since EVPN does not propagate the “router” flag in IPv6->MAC advertisements, in a
mixed network with hosts and routers, if evpn-nd-advertise router is configured, unsolic-
ited host NA messages should be flooded so that the entire network gets to learn all of the
host and router ND entries. In the same way, evpn-nd-advertise host should be configured
if unsolicited router NA messages are flooded.

Subscriber • Dynamic data persistency (subscriber management, DHCP server, Python-policy cache,
Management NAT port forwarding, Application Assurance or ANCP) usage notes are as follows.
− Alcatel-Lucent recommends discontinuing the use of 256M and 1G compact flash
cards for dynamic data persistency applications; using a 4G or 8G compact flash card
is recommended. From Release 13.0.R1 onwards, Alcatel-Lucent recommends using
an 8G compact flash card when enabling multiple dynamic data persistency
applications.
− Dynamic data persistency should not be configured to use compact flash cards
formatted with the Reliance file system.
− Alcatel-Lucent recommends a maximum of two (2) applications on the same compact
flash card when using multiple dynamic data persistency applications.
− CF3 must not be used as the location for dynamic data persistency.
− XML accounting (stored on compact flash) should not be used in conjunction with
dynamic data persistency. Alcatel-Lucent recommends RADIUS accounting as an
alternative. [50940]
• Starting with Release 11.0.R1, a RADIUS server configured under the routing instance
(base, management or VPRN service) radius-server context can be used for authentication
and accounting applications simultaneously. It is now possible to configure an auth-port
and an acct-port for each server. When upgrading from a release prior to Release 11.0.R1,
the single port configured for the server is automatically migrated to the new configuration.
In this case, both auth-port and acct-port will have the same value. This is not a problem

144 SR OS 13.0.R10 Software Release Notes


Usage Notes

for the active configuration, but needs to be manually updated if the server is used for
multiple applications.
• DHCPv6 server DUID configuration guidelines in multi-chassis redundancy scenarios are
as follows:
− In a redundant DHCPv6 server configuration, each server must have a unique DUID
(configured as server-id in the router | service vprn dhcp6 local-dhcp-server CLI
context). Configuring an identical DUID with failover mode local/remote can result
in unpredictable or multiple prefix allocation.
− In a multi-chassis redundant DHCPv6 proxy-server configuration, both proxy-servers
must share the same DUID (configured as server-id in the group-interface ipv6
dhcp6 proxy-server CLI context). Configuring a different DUID can result in
ignoring the lease renewal and release after an SRRP switchover.

Use of BGP-EVPN, • BGP-EVPN, BGP-AD and BGP-MH (one site) can all be configured in the same VPLS
BGP-AD and BGP- service. If that is the case, the following considerations apply:
MH in the same − The configured BGP route-distinguisher and route-target are used by BGP for the two
VPLS service families (that is, EVPN and L2-VPN). If different import/export route targets are used
per family, vsi-import/export policies must be used.
− The pw-template-binding command under BGP does not have any affect on EVPN
or BGP-MH. It is only used for the instantiation of the BGP-AD spoke-SDPs.
− If the same import/export route-targets are used in two (2) redundant systems for
BGP-EVPN and BGP-AD, a VXLAN binding, as well as a FEC129 spoke-SDP
binding, may be attempted between the two systems, creating a loop. If that is the
case, the SR OS will allow the establishment of an EVPN VXLAN binding and an
SDP-binding to the same far-end, but it will keep the SDP-binding operationally
down. Only the VXLAN binding will be operationally up. [170951]

VPRN/2547 • A route policy statement entry referencing a non-existent prefix list, community list, or AS
path list will be accepted without a warning when committing a route policy configuration.
This kind of missing reference can be seen when executing show router policy-edits.
[60879, 84264, 86129]

IPsec • IKE traffic should be treated as higher priority than any data plane traffic (like ESP) on the
end-to-end path from a remote IPsec peer to a 7750 SR, which means that appropriate
ingress/egress QoS policy should be configured on the corresponding network facing port
(or SAP) and public tunnel-SAP of 7750 SR and any other network forwarding node along
the way.
• CRL NUMBER is a non-critical CRL extension; the CRL file provisioned in ca-profile
should not mark this extension as critical.
• Certificate configured in cert-profile or by the cert command under ipsec-tunnel/ipsec-
gw should be an end-entity certificate; a CA certificate should not be configured in these
places.

SR OS 13.0.R10 Software Release Notes 145


Usage Notes

IPsec • The following tables list software and hardware tested for compatibility with IPsec
Compatibility services:

Table 33. Compatible Devices for dynamic LAN-to-LAN IPsec Tunnels

Device Tested Version


Alcatel-Lucent VPN Firewall Brick 1200 9.1
Bintec Funkwerk R1200WU 7.5 Rev 3

Table 34. Compatible IPsec Soft Client

Soft Client Tested Version(s)


Cisco VPN Client 5.0.03.0560
Racoon NetBSD running ipsec-tools 0.7
SafeNet SoftRemote 10.8.3
Shrewsoft 2.1.2
Strongswan 2.8.x, 4.2.x, 5.0.1

Time-of-Day • In a TOD suite, items can be defined that cannot be applied to all SAP types: for instance,
Suites an IP filter in the TOD suite that is then assigned as the TOD suite to a VPLS SAP. When
the IP filter becomes active, the system will detect that it is not possible to assign the suite
to the SAP and generate a log event.
• When a TOD suite is applied to a SAP, there may be conflicts that make it impossible to
install all of the current TOD suite defined values. The conflicts can be between the TOD
suite defined values or between SAP configured values and TOD suite defined values. A
log event is always generated when a conflict occurs. The possible conflicts are:
− An ingress MAC filter cannot be installed with an ingress IP filter, ingress IPv6 filter
or ingress QoS policy which has IPv6 criteria. The MAC filter will not be installed.
− An egress MAC filters cannot be installed with an egress IP filter or egress IPv6 filter.
The MAC filter will not be installed.
− An ingress IPv6 filter cannot be installed with an ingress QoS policy which has MAC
criteria. The filter will not be applied.
• At system boot, it is possible that the “intended value” (be it from the TOD suite or a
configured value) of a policy assignment cannot be applied due to resource unavailability;
at that time, there is no previous state to which to revert, and the SAP (or multi-service site
(MSS)) ends up with a default policy assignment. In this situation, the SAP (or all of the
MSS's SAPs) is (are) placed in an operationally down state with the appropriate flag set.
− “SapTodResourceUnavail” indicates that the SAP has a TOD suite and could neither
apply it nor revert to the previous state. The SAP will have a default policy
configured.
− “SapTodMssResourceUnavail” indicates that the SAP has a Multi-Service Site that
uses a TOD suite, and the MSS could neither apply the TOD suite nor revert to its
previous state. The SAP will have a default scheduler policies configured, i.e. none.
These flags get cleared whenever a subsequent application of the TOD suite is successful
and the intended policies can be configured.

146 SR OS 13.0.R10 Software Release Notes


Usage Notes

• When the QoS and scheduler policy assignment of a SAP or MSS is changed by action of
its TOD suite, packet loss may occur, just like when the configuration is modified directly
by CLI or SNMP.
• The number of assignments in a given TOD suite is implicitly limited to 100 (10 types of
parameters each with 10 possible priority values).

OpenFlow • H-OFS supports statistics collection per entry for Flow Table and Logical Port Table. Due
to large H-OFS scale, Alcatel-Lucent recommends that a single statistics request message
from the controller does not map (using a wildcard or cookie) to more than 1000 Flow
Table entries per cookie context per message or ten (10) Logical Port Table entries per
message.

Application • Operators using applications maintained by Alcatel-Lucent for analytics, charging, or


Assurance control should update both protocol signatures and the AA policy definition on a regular
basis. New and updated protocols are available in the isa-aa.tim file while the AA policy
update is provided through Alcatel-Lucent technical support. See AA Signatures Upgrade
Procedure for more details.
• The isa-aa.tim image is available in the same directory as other .tim images. The image
contains the Application Assurance software used on MS-ISA and the protocol list loaded
by the CPM. The Application Assurance software can be upgraded independently of the
SR OS software within a major release of the SR OS.
• When an Application-Assurance group dual-bucket-bandwidth policer is configured, the
default configuration will cause all packets to be dropped. Ensure that the dual-bucket-
bandwidth policer is configured appropriately. [86311]
• Only properly negotiated TCP sessions are eligible for TCP performance sampling.
• Changes to the TCP performance sampling rates will only affect new traffic flows.
• The bandwidth capacity for an AA-subscriber is equal to the full capacity of the MS-ISA or
MS-ISA2 card, provided there is a realistic diversity of traffic sessions. The bandwidth
capacity of an individual traffic session is limited by the in-order analysis and the amount
of high-touch processing required by each packet in the session.
• If a Forwarding Path (FP) is configured with one MDA type of ISA-AA and any other
MDA type (except a second ISA-AA) on an IOM3 or on a 7750 SR-c4/c12 system, then
the FP buffer allocation must be modified from the default values; otherwise, there may be
insufficient buffers for the non-ISA-AA MDA, which may lead to packet discards.
[117290]
• The use of AARP on multi-homed, active-active SAPs or spoke-SDPs will force some of
the traffic to use the inter-shelf AARP shunt interfaces. The AA remote divert will override
policy-based routing (such as for NAT forwarding) applied on filters for traffic from the
AARP instance (SAP or spoke-SDP).
• When detect-seen-ip is enabled in a transit-ip-policy, the operator must ensure that a
default app-profile is configured. If there is no default app-profile and an app-profile is
not provided by either RADIUS, Diameter or DHCP, then AA subscriber creation will fail;
however, traffic for that subscriber will continue to traverse the AA on the parent context.

SR OS 13.0.R10 Software Release Notes 147


Usage Notes

BFD • per-fp-egr-queuing for LAG-based SAPs that have BFD sessions should not be enabled.
When per-fp-egr-queuing is configured on a LAG and fast BFD is enabled for any SAP
interface on that LAG, the BFD packets may be dropped on egress during LAG physical or
logical port oversubscription. This condition may lead to the BFD session going down.

BFD on LSPs • Interoperability with non-SR OS implementations of LSP BFD is not supported in Release
13.0.R4.

BFD VCCV • The following table describes BFD VCCV interoperability with JunOS running on Juniper
MX. [185090]

Table 35. BFD VCCV Interoperability with Juniper MX

Service Interoperability
BGP-VPLS BFD VCCV inter-op not supported
LDP-VPLS BFD VCCV inter-op supported
Epipe control-word BFD VCCV inter-op supported
Epipe no-control-word Inter-op not supported
VPWS control-word Inter-op not supported

BGP-EVPN and • In general, the recommended version to be used with Release 13.0.R4 is Nuage 3.2.R1 and
XMPP higher for XMPP interoperability.
interoperability • The use of the “Policy-Based Forwarding/Routing to an EVPN ESI” feature, for the
with Nuage integration of the SR OS nodes in the Nuage Service Chaining architecture, requires
Release 3.2.R1 or higher in the Nuage VSC.
• The use of XMPP for the Fully-Dynamic VSD integration model requires Release 3.2.R1
or higher in the Nuage VSD. If lower VSD release versions are to be used, the following
compatibility matrix provides an indication of the combinations that work or do not work:

Table 36. Nuage VSD and SR OS Node XMPP Compatibility

Nuage VSD Release SR OS Release Compatibility Comments1


3.0.R3 – R5 12.0.R7 – R9 ✓ S-D only
13.0.R1 – R2 ✓ S-D only
12.0.R10 and higher X —
13.0.R3 and higher X —
3.1 Any X Not a DC version
3.0.R6 and higher 12.0.R7 – R9 X —
13.0.R1 – R2 X —
12.0.R10 and higher ✓ S-D only
13.0.R3 and higher ✓ S-D only

148 SR OS 13.0.R10 Software Release Notes


Usage Notes

Table 36. Nuage VSD and SR OS Node XMPP Compatibility (Continued)

Nuage VSD Release SR OS Release Compatibility Comments1


3.2.R1 and higher 12.0.R7 – R9 X S-D only
13.0.R1 – R2 X S-D only
12.0.R10 and higher ✓ S-D only
13.0.R3 ✓ S-D only
13.0.R4 and higher ✓ S-D and F-D
1. S-D = Static-Dynamic model, F-D = Fully-Dynamic model.

• A number of changes have been progressively introduced in the Nuage and SR OS EVPN-
VXLAN implementation in order to align the control plane with the relevant IETF
standards. In general, the use of SR OS Release 13.0.R4 and Nuage Release 3.2.R1 or
higher is recommended. If lower release versions are to be used, the following
compatibility matrix provides an indication of the combinations that work or do not work
for EVPN. Note that if VSD – SR OS node integration is required, the above table must
also be considered.

Table 37. Nuage VSP and SR OS Node EVPN Compatibility

Nuage Release SR OS Release Compatibility Comments


Up to 3.0.R3/3.1.R2 12.0.R7 ✓ —
12.0.R8/13.0.Rx X Incompatible extended
community values: RFC
5512 BGP encapsulation
and Router’s MAC.
3.0R4-R6/3.1.R3 12.0.R7 X Incompatible extended
community values: RFC
5512 BGP encapsulation
and Router’s MAC.
12.0.R8 and higher ✓ —
13.0.R1 and higher ✓ —
3.2.R1/3.0.R8 and higher 12.0.R7-R8 X Different VNI encoding
can create issues
13.0.R1 X Different VNI encoding
can create issues
12.0.R9 and higher ✓ —
13.0.R2 and higher ✓ —

• Notes: the following changes have been implemented along the releases:
− The standard EVPN extended community values were introduced in Nuage Release
3.0.R4/3.1.R3 and SR OS Release 12.0.R8. Before those releases:
− The VXLAN tunnel value in the RFC 5512 BGP encapsulation extended
community was not compliant with draft-ietf-bess-evpn-overlay.

SR OS 13.0.R10 Software Release Notes 149


Usage Notes

− The Router’s MAC extended community type/sub-type was not compliant with
draft-ietf-bess-evpn-prefix-advertisement.
− From SR OS Release 12.0.R9/13.0.R2 and higher, the label field is interpreted as a
24-bit value when the encapsulation is VXLAN and it is ignored. Up to these releases,
the SR OS node was expecting the Bottom of Stack (BoS) bit set in the label field.
− From Nuage Release 3.2.R1 on, Nuage encodes the VNI in both, the Ethernet Tag and
label fields. It can accept VNIs from both fields.
− From SR OS Release 13.0.R4 on, the SR OS node encodes the VNI in the label field.
It can accept VNIs from both fields.
− Note that support for AD routes (EVPN route type 1) on the SR OS node has been
introduced in SR OS Release 13.0.R4. Prior to that release, the SR OS node would
discard any AD route received from VSC.
− Nuage Release 3.0.R7 is not recommended in combined SR OS node and Nuage
EVPN deployments.

150 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

Software Upgrade Procedures


The following sections contain information for upgrading to the Release 13.0.R10 software
version.
− Software Upgrade Notes
Information on upgrading the router from previous versions of SR OS software
including rules for upgrading firmware and any special notes for upgrading from
specific earlier versions.
− AA Signatures Upgrade Procedure
Information on upgrading MS-ISA to a new AA-signature load.
− ISSU Upgrade Procedure
Procedure for performing an ISSU to Release 13.0.R10 including information on
applicability of ISSU for earlier versions.
− Standard Software Upgrade Procedure
Procedure for performing a standard, service-affecting upgrade including updating of
firmware images.

Software Upgrade Notes


The following sections describe notes for upgrading from prior versions of SR OS to 13.0.R10.

Notes:
• An admin reboot upgrade is required for all 7450 ESS-6 and ESS-6v chassis running Release 8.0
or an earlier major release, Release 9.0.R22 or an earlier 9.0 minor release, Release 10.0.R12 or an
earlier 10.0 minor release, or Release 11.0.R3 or an earlier 11.0 minor release.
• Automatic firmware updates may occur for CPM and IOM/IMM/XCM cards running older
firmware after a SR OS upgrade. The clear card command or physical removal of a card must not
be performed until the card is operationally up after an SR OS upgrade. This procedure also
applies when subsequently adding new IOMs/IMMs/XCMs (that may have older firmware) to a
chassis. An event log with “firmware upgraded” message will be issued if a firmware update had
occurred for a card.

The following conventions are used in configuration files:


• Deprecated commands are not flagged as errors upon reading a configuration file with
deprecated commands, but these commands will not be written to a saved configuration
file.
• Modified commands are read using the old format, but they are written out with the new
format in a configuration file; so a configuration file saved with modified commands is not
compatible with earlier releases.
• Modified parameters are supported when they are read, but the modified parameters will be
converted to new minimums or maximums when saved in a configuration file.

SR OS 13.0.R10 Software Release Notes 151


Software Upgrade Procedures

Upgrading to • Release 13.0.R10 changes the way XML Accounting files are formatted. Parsing functions
Release 13.0.R10 in operator OSS layers may need to be adjusted if they had custom logic to work around the
or Higher invalid SR OS XML formatting. Prior to Release 13.0.R10, the XML encoding used in
SR OS accounting files for certain special characters was invalid. As of Release 13.0.R10,
SR OS accounting files correctly encode the special characters as “&lt;”, “&gt;”, “&amp;”,
“&apos;”, and “&quot;” instead of placing characters such as “<” directly into the
accounting files. OSS parsing logic for Release 13.0.R10 and higher XML Accounting
files must be able to handle the standard XML encoding for the special characters.

Upgrading from • When upgrading from Release 13.0.R5 to Release 13.0.R6 or higher, there is a mandatory
Release 13.0.R5 to firmware upgrade for all CPMs and IOMs on the 7750 SR-a4/a8.
13.0.R6 or Higher During the software upgrade, the cards that require new firmware will automatically update
their firmware when they are rebooted as part of the normal software upgrade process. The
firmware update will cause a longer reboot time than usual (approximately 10 minutes
instead of a few minutes). Ensure the cards are not removed while they are reprogramming
the firmware. The Operational State of a card that is reprogramming its firmware will be
displayed as “provisioned” under show card and the Equipped Type will be displayed as
“not equipped”. [208437, 216782, 217615]

Upgrading to • When upgrading to Release 13.0.R5 from a previous release, there is a mandatory firmware
Release 13.0.R5 or upgrade for certain cards and platforms:
Higher − 7750 SR-a4/a8: all CPMs and IOMs (note that ISSU is not supported on the
7750 SR-a platform)
− 7750 SR-7/12/12e: the CPM5 has new mandatory firmware in Release 13.0.R5 (this
does not affect ISSU—CPMs are always rebooted during ISSU)
During the software upgrade, the cards that require new firmware will automatically update
their firmware when they are rebooted as part of the normal software upgrade process
(ISSU or non-ISSU). The firmware update will cause a longer reboot time than usual
(approximately 10 minutes instead of a few minutes). Ensure the cards are not removed
while they are reprogramming the firmware. The Operational State of a card that is repro-
gramming its firmware will be displayed as “provisioned” under show card and the
Equipped Type will be displayed as “not equipped”.

13.0.R4 YANG • In Release 13.0.R4, the following changes were made to the YANG modules without
Modules retaining the old elements and marking them as obsolete or deprecated:
− In the alu-conf-filter-r13.yang file, the child leafs in the dhcp6-filter/default-action
container were reworked in Release 13.0.R4. The default-action-id leaf no longer
exists in the YANG file (no obsolete status).
− In the alu-conf-filter-r13.yang file the modeling of the “action” container for ip-filter
and ipv6-filter entries has changed in Release 13.0.R4. The drop, forward, http-
redirect and nat leafs have been changed to containers (to model a similar change in
CLI) and many leafs that existed at the “action” level are now underneath drop,
forward, http-redirect or nat. These changed drop, forward, http-redirect and nat
nodes have not changed names and the other moved leaves are not marked with
deprecated or obsolete status in the YANG file in their old locations in the tree.

152 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

− The alu-conf-svc-vpls-sap-r13.yang file changed the ascii-tuple and vlan-ascii-tuple


in the circuit-id container from leafs to enum values.

Subscriber • Due to increased memory requirements as a result of new software features, the maximum
Management subscriber-host scale is 128k per system for the 7750 SR-7/12, 7450 ESS-7/12 equipped
with CPM3, and operating in chassis mode D. This limit is not enforced by the system. For
existing deployments that need a higher subscriber-host scale and want to upgrade to
SR OS Release 13.0, it is recommended to install CPM5 to provide more memory capacity.
[199108]

Cflowd • In Release 12.0.R9, the new Cflowd command use-vrtr-if-index was introduced. If
upgrading from Release 12.0.R9 or later to Release 13.0.R1 or 13.0.R2, and this new
command has been enabled, or admin save detail was used to save the system’s
configuration, then all mention of this command must be removed from the saved
configuration file before attempting to upgrade to Release 13.0.R1 or 13.0.R2.

Upgrading to • Upgrading from a release earlier than Release 12.0.R2 to Release 13.0.R1 or higher can
Release 13.0.R1 or incorrectly change the configuration of nat outside pool redundancy to shutdown state.
Higher This configuration must be manually corrected. [215881-MA]
• With the introduction of LDP IPv6 in Release 13.0.R1, a FEC for each of the IPv4 and IPv6
system interface addresses is advertised and resolved automatically by the LDP peers when
the LDP session comes up, regardless of whether the session is IPv4 or IPv6.
To avoid the automatic advertisement and resolution of IPv6 system FEC when the LDP
session is IPv4, the following procedure must be followed before and after the upgrade to
the SR OS version which introduces the support of LDP IPv6.
1. Before the upgrade, implement a global import prefix policy which rejects prefix [::0/0
longer] to prevent IPv6 FECs from being installed after the upgrade.
2. In Major ISSU case:
− If new IPv4 sessions are created on the node, the per-peer FEC-capabilities must
be configured to filter out IPv6 FECs.
− Until an existing IPv4 session is operationally toggled, FEC-capabilities have no
effect on filtering out IPv6 FECs; thus, the global import policy must remain
configured in place until the session toggles. Alternatively, a per-peer-import-
policy [::0/0 longer] can be associated with this peer.
3. In cold upgrade case:
− If new IPv4 sessions are created on the node, the per-peer FEC-capabilities must
be configured to filter out IPv6 FECs.
− On older, pre-existing IPv4 sessions, the per-peer FEC-capabilities must be
configured to filter out IPv6 FECs.
4. When all LDP IPv4 sessions have dynamic capabilities enabled, with per-peer FEC-
capabilities for IPv6 FECs disabled, then the global import policy can be removed.

RMON • RMON entries that referenced deprecated MIB entries are not automatically modified and
re-saved with the MIB variable that may have replaced it. MIB variable changes are often
due to a change in the indexing structure for such tables. Refer to the MIBs distributed with

SR OS 13.0.R10 Software Release Notes 153


Software Upgrade Procedures

your SR OS image set and compare those as needed to MIBs from the prior SR OS release
to identify changes and update the corresponding SNMP object or OID references in the
configuration file.

MLD • The checks for a valid link local address are corrected for some cases.
The checks are stricter starting in Release 12.0.R4. Previously, addresses in the range of
FE80::/10 were accepted (for example, FE81:: was accepted). Now the check is corrected
and only addresses in the range of FE80::/64 are accepted.
This will have an impact when performing an upgrade: configured values not in the
FE80::/64 range will be rejected.
Impacted configuration commands are:
− config>router>mld>group-interface group-interface-name>query-src-ip link-local
address
− config>service>vprn service-id>group-interface group-interface-name>query-src-
ip link-local address
− config>router>mld>grp-if-query-src-ip link-local address
− config>service>vprn service-id>mld grp-if-query-src-ip link-local address
− config>router>interface interface-name>ipv6 link-local-address link-local-address
− config>service>vprn service-id>interface interface-name>ipv6 link-local-address
link-local-address [172857]

MPLS • Since Releases 10.0.R4 or 11.0.R1, when the system starts Major or Minor ISSU
Maintenance Mode procedures, MPLS will automatically be put into a maintenance mode such that existing
during ISSU or LSP paths will continue to operate normally while the node will not issue new LSP paths or
Soft Reset a Make-Before-Break (MBB) path for existing LSPs. It will also reject requests for new
LSP paths or MBB paths of existing LSPs coming from RSVP neighbors. The MPLS
module will automatically exit the new maintenance mode when the Major or Minor ISSU
is completed.

Upgrading to • A configuration with an IPv6 prefix present in the router>router-advertisement interface


Release 12.0.R1 or context on a non-mixed mode 7450 ESS will fail to execute from Release 12.0.R1 onward.
Higher It was possible in releases prior to Release 12.0.R1 to configure, although this was
functionally not supported. If such a configuration exists, it has to be removed prior to
upgrading to Release 12.0.R1 or later.
• The configuration command configure system security user user-name console login-
exec " " (single space URL) will fail to execute from Release 12.0.R1 onwards. Prior to
Release 12.0.R1, it was possible to issue this configuration command, although it contained
an invalid URL. If such a configuration exists, it must be removed/updated prior to
upgrading to Release 12.0.R1 or later.

DHCP • When upgrading from Release 10.0.R10 through 10.0.R15 or from Release 11.0.R1
through 11.0.R7 to Release 12.0.R1 or higher, and DHCPv6 server and/or DHCPv6 relay
on subscriber interfaces is/are enabled to assign IA_NA addresses, it may be required to
add the global configuration parameter adv-noaddrs-global esmrelay server under the
config> system>dhcp6 context for backward compatibility. This parameter will send the

154 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

“NoAddrsAvail” status code in DHCPv6 advertise messages at the global DHCP message
level instead of at the default IA_NA option level.

Routing Policies • From Release 12.0.R1 onwards, the use of a community, as-path, as-path-group or
prefix-list name starting and ending with '@' is no longer allowed. @...@ is used as
identification for parameters being used in policies. Upgrading from a pre-Release 12.0.R1
to Release 12.0.R1 or higher will mean that configuration files containing such names will
fail to execute. [173346]

MPLS/RSVP • The LFA SPF policy feature generalizes the use of admin-group and SRLG to non-MPLS
interfaces. To that end, the definition of admin-groups and SRLGs has been moved from
the config>router>mpls context to the new config>router>if-attribute context. The
binding of MPLS interfaces to admin-group or SRLG remains under
config>router>mpls>interface.

Upgrading to • Starting with Release 11.0.R7, configuration changes are required for TACACS+ servers to
Release 11.0.R7 or authorize global commands. Global commands such as info, exit, and others, except the
Higher logout command, should be explicitly added to the configuration in the TACACS+ server.
There are no changes required in the configuration on the SR OS node for this issue. A list
of all global commands can be found in the SR OS Basic System Configuration Guide, or
by entering help globals at the CLI prompt. [171214]

Upgrading from • The parameter port-forwarding-dyn-block-reservation was introduced in Release


Release 11.0.R1 or 11.0.R1 and was incorrectly allowed to be configured for type L2-Aware NAT pools. From
11.0.R2 Release 11.0.R3 onwards, a check was added to disallow the configuration of the parameter
in combination with type L2-Aware NAT pools. Prior to upgrade, the parameter port-
forwarding-dyn-block-reservation should be removed from the NAT configuration when
having a type L2-Aware NAT-group configured. More details can be found in TA 13-1007.
[163525]

LDP • When upgrading from Release 11.0.R3, 11.0.R4, or 11.0.R5 to Release 11.0.R6 or later, the
default setting for LDP event 2003 changed from generate to suppress. This value must be
manually changed after the upgrade to properly save the newly corrected default setting of
suppress. The default of suppress had been the default in Release 11.0.R2 and all prior
releases. [170911]

Upgrading to • The tmnxPortID mapping has changed for the 7950 XRS-20 platform. Refer to TIMETRA-
Release 11.0.R4 or TC-MIB for specific details.
Higher on XRS-20 • On upgrade, port indices in the SNMP MIB will not be preserved on these platforms.
Management software that expects the old mapping may need to be updated.

R-VPLS • R-VPLS does not support configuration of line card MAC filters. This restriction is now
properly enforced starting with Releases 11.0.R1 or higher. A router using an SR OS
version that enforces the restriction will not load a configuration that includes MAC filters
in the context of R-VPLS. Before loading such a configuration either from a saved file or

SR OS 13.0.R10 Software Release Notes 155


Software Upgrade Procedures

as part of an SR OS router upgrade, MAC filter configuration must be removed from the R-
VPLS context.
• A Routed-VPLS service does not support Multicast-VLAN-Registration (MVR). This
restriction is enforced starting from Release 11.0.R1 onwards. With Release 10.0, it was
possible to configure MVR options below a Routed-VPLS service. Before upgrading from
Release 10.0, those options must be removed from the configuration, or loading the saved
file will fail. [163006]

Filter Policy • Starting with Release 11.0.R1, SR OS enforces the rule that a single CLI filter policy entry
Consideration should not exceed the allowed hardware resources. Operators are advised to verify that a
when Upgrading 10.0 configuration that uses match list in filter policies does not exceed the recommended
from Release limit prior to an upgrade. Failure to do so will result in configuration failure during an
10.0.R4 or Higher upgrade if the entry exceeds the enforced limits. The enforced rule allows 2000 hardware
to Release 11.0.R1 sub-entries per line card filter policy entry and 256 hardware sub-entries per CPM filter
or higher policy entry (approx. 25% margin atop Release 10.0.R4 recommended/supported limits as
outlined by known limitation 142472 in Releases 10.0 and 11.0).
Refer to the Release Notes for Releases 11.0 and 10.0 for information about known limita-
tion 142472.

Upgrading to • Support for the read-only radiusServerTable and read-only tacplusServerTable in the
Release 11.0.R1 or TIMETRA-SYSTEM-MIB has been removed in Release 11.0.R1 onwards. The alternative
Higher readable and writable tables tmnxRadiusServerTable and tmnxTacPlusServerTable in the
TIMETRA-SECURITY-MIB should be used instead. [131834]
• A new support.tim file has been introduced in Release 11.0.R1 as part of the SR OS
software image package of *.tim files. All *.tim files should be copied together as a
package when performing actions such as upgrades or backing up images. The support.tim
file contains SR OS image data that is required for all platforms and configurations, and is
not related to Alcatel-Lucent support services or the admin tech-support functionality.
When upgrading from a release prior to Release 11.0.R1 to Release 11.0.R1 release or later,
the support.tim file must be manually synchronized (copied) across to the standby CPM.
See Step 5 of the Standard Software Upgrade Procedure. Releases prior to Release 11.0.R1
do not know about the support.tim file and hence the synchronize command will not copy
it.

AA Signatures Upgrade Procedure


This section describes the AA Signatures Upgrade Procedure which can be used to upgrade
ISAs in 7750 SR-7/12/12e, 7750 SR-c4/c12 and ESS-6/6v/7/12 to a new AA signature load
without upgrading/impacting the router itself:
− When no firmware update is required

156 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

If the above criterion does not apply, the Standard Software Upgrade Procedure must be
performed.

Notes:
• Although the software upgrade can be performed using a remote terminal session, Alcatel-Lucent
recommends that the software upgrade procedure be performed at the system CONSOLE device
where there is physical access to the 7750 SR or 7450 ESS as remote connectivity may not be
possible in the event there is a problem with the software upgrade. Performing the upgrade at the
CONSOLE with physical access is the best situation for troubleshooting any upgrade problems
with the help of the Alcatel-Lucent Technical Assistance Center.
• This procedure applies to all ISA cards.

STEP 1 Back up existing images and configuration files


New software loads may make modifications to the configuration file which are not compatible
with older versions of the software.

Note:
• Configuration files may become incompatible with prior releases even if no new features are
configured. The way in which a particular feature is represented in the configuration file may be
updated by the latest version of the operating software. The updated configuration file would then
be an unknown format to earlier software versions.

Alcatel-Lucent recommends making backup copies of the software image and configuration
files (including bof.cfg and *.ndx persistency files). These backups will be useful in case
reverting to the old version of the software is required.

STEP 2 Copy Application Assurance ISA-AA.TIM file to cf3:


Application Assurance software and signatures are included in the isa-aa.tim file. This file must
be copied to the same cf3: directory as the current SR OS images running on the router. It is
good practice to place all of the image files for a given release in an appropriately named
subdirectory off the root, for example, “cf3:\13.0.R1”.
As a result of this step, when upgrading the AA software only on an older SR OS software, the
new isa-aa.tim file overwrites the existing software on the flash card.

STEP 3 Synchronize boot environment


Active and standby CPM/CFM boot environments must be synchronized if the router has
redundant CPM/CFMs.
• Use admin redundancy synchronize boot-env to synchronize the boot environments
between the active and standby CPM/CFMs.

STEP 4 Load new image for ISA card


Once the boot environment has been synchronized, the new AA image needs to be loaded on
the CPM/CFM.
• Use admin application-assurance upgrade to load the new isa-aa image on the
CPM/CFM.

SR OS 13.0.R10 Software Release Notes 157


Software Upgrade Procedures

• Use show application-assurance version to verify new isa-aa image version running on
the CPM/CFM.
• Use show mda to verify ISA card status.

A:ALU-ABC>show>app-assure# version
==============================================================================
Versions of isa-aa.tim in use
==============================================================================
CPM : TiMOS-M-13.0.R2
1/2 : TiMOS-M-13.0.R1
3/2 : TiMOS-M-13.0.R1
==============================================================================

A:Cpm-A# show mda


==============================================================================
MDA Summary
==============================================================================
Slot MDA Provisioned Equipped Admin Operational
Mda-type Mda-type State State
------------------------------------------------------------------------------
1 2 isa-aa isa-ms up ISSU/standby
...
3 2 isa-aa isa-ms up ISSU/active
==============================================================================

STEP 5 Reset the ISA cards to load the new image


The ISA cards must now be reset to load the new image.

Note:
• The system does not allow cards to run in an ISSU state indefinitely; the system automatically
resets the ISA cards after 2 hours. The “Comments” field in the show card state output displays
the time until the system resets the ISA card in the ISSU state.

The timing and order of the ISA card resets should be sequenced to maximize the effectiveness
of any redundancy. When redundancy is deployed, protecting (standby) ISA cards should be
reset first, and admin activity switch should be forced first (config card mda m/n shutdown)
before an active ISA card is reset.
• Use shutdown mda m/n to shut down an ISA card
• Use clear mda m/n to reset an ISA card
• Use no shutdown mda m/n to enable an ISA card
• Use show application-assurance version to verify the isa-aa signatures version loaded on
the CPM/CFMs and the ISA cards
The sample output below shows the operational state transitions for a single Application
Assurance group with one (1) active and one (1) protecting (standby) ISA card.
1. Before reset starts:

A:ALU-ABC>show>app-assure# version

158 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

==============================================================================
Versions of isa-aa.tim in use
==============================================================================
CPM : TiMOS-M-13.0.R2
1/2 : TiMOS-M-13.0.R1
3/2 : TiMOS-M-13.0.R1
==============================================================================

A:Cpm-A# show mda


==============================================================================
MDA Summary
==============================================================================
Slot MDA Provisioned Equipped Admin Operational
Mda-type Mda-type State State
------------------------------------------------------------------------------
1 2 isa-aa isa-ms up ISSU/standby
...
3 2 isa-aa isa-ms up ISSU/active
==============================================================================

2. After the standby ISA card is reset and comes back up:

A:ALU-ABC>show>app-assure# version
==============================================================================
Versions of isa-aa.tim in use
==============================================================================
CPM : TiMOS-M-13.0.R2
1/2 : TiMOS-M-13.0.R2
3/2 : TiMOS-M-13.0.R1
==============================================================================

A:Cpm-A# show mda


==============================================================================
MDA Summary
==============================================================================
Slot MDA Provisioned Equipped Admin Operational
Mda-type Mda-type State State
------------------------------------------------------------------------------
1 2 isa-aa isa-ms up up/standby
...
3 2 isa-aa isa-ms up ISSU/active
==============================================================================

3. After the ISA card activity switch (shutdown of active card to force activity switch):

A:ALU-ABC>show>app-assure# version
==============================================================================
Versions of isa-aa.tim in use
==============================================================================
CPM : TiMOS-M-13.0.R2
1/2 : TiMOS-M-13.0.R2
3/2 : TiMOS-M-13.0.R1
==============================================================================

SR OS 13.0.R10 Software Release Notes 159


Software Upgrade Procedures

A:Cpm-A# show mda


==============================================================================
MDA Summary
==============================================================================
Slot MDA Provisioned Equipped Admin Operational
Mda-type Mda-type State State
------------------------------------------------------------------------------
1 2 isa-aa isa-ms up up/active
...
3 2 isa-aa isa-ms down ISSU/standby
==============================================================================

4. After the newly inactive ISA card is reset, comes back up (clear command executed) and is
re-enabled (no shutdown executed):

A:ALU-ABC>show>app-assure# version
==============================================================================
Versions of isa-aa.tim in use
==============================================================================
CPM : TiMOS-M-13.0.R2
1/2 : TiMOS-M-13.0.R2
3/2 : TiMOS-M-13.0.R2
==============================================================================

A:Cpm-A# show mda


==============================================================================
MDA Summary
==============================================================================
Slot MDA Provisioned Equipped Admin Operational
Mda-type Mda-type State State
------------------------------------------------------------------------------
1 2 isa-aa isa-ms up up/active
...
3 2 isa-aa isa-ms up up/standby
==============================================================================

STEP 6 Update the AA policy and enable the new applications and protocol signatures
When the CPM/CFMs and ISA cards are using the latest image, update the AA policy definition
and enable the new protocols available in this release. This process updates existing applications
and corresponding app-filters maintained by Alcatel-Lucent, and creates newly supported
applications.
• The operator must open a standard ticket, priority 3, to Alcatel-Lucent technical support,
and provide a technical support file and the target AA software release deployed in the
network.
• The technical support team will provide the following configuration update file to update
the AA policy, to be executed on the target nodes:
7750# exec ftp://user:pass@ftp-server-ip/path/<aaconfig-delta-update-file-name>

160 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

ISSU Upgrade Procedure


This section describes the ISSU Upgrade Procedure which can be used:
− when no manual firmware update is required (such as “admin reboot upgrade”)—See
the ISSU sub-section of Known Limitations for details.
− on routers running Release 12.0.R4 (12.0.R5 for 7950 XRS-16c/20 and 12.0.R6 for
7950 XRS-40) to 12.0.R16 for Major ISSU with redundant CPMs only (not
applicable to 7750 SR-a4/8 or 7750 SR-c4/12)
− on routers running Release 13.0.R4 to Release 13.0.R9 for Minor ISSU with
redundant CPMs/CFMs only (not applicable to 7750 SR-a4/8 or 7750 SR-c4)
If any of the above criteria do not apply, the Standard Software Upgrade Procedure must be
performed.
ISSU limitations listed under Known Limitations should be taken into account for planning
purposes before the ISSU is performed.

Notes:
• Although the software upgrade can be performed using a remote terminal session, Alcatel-Lucent
recommends that the software upgrade procedure be performed at the system CONSOLE device
where there is physical access as remote connectivity may not be possible in the event there is a
problem with the software upgrade. Performing the upgrade at the CONSOLE with physical
access is the best situation for troubleshooting any upgrade problems with the help of the
Alcatel-Lucent Technical Assistance Center. It is also recommended to connect to the CONSOLE
port on both CPMs/CFMs prior to starting the ISSU.

The ISSU procedure is split into the following two (2) phases:
• Phase A: Preparation and CPM/CFM Upgrade, with one procedure common to Minor and
Major ISSU
• Phase B: Completion of the ISSU, with different procedures for Minor and Major ISSU

Phase A: Phase A of the ISSU procedure is common to both Minor ISSU and Major ISSU. This phase
covers ISSU preparation and the update of the CPM/CFM software.
Preparation
and
CPM/CFM
Upgrade

STEP 1 Backup Existing Images and Configuration Files


New software loads may make modifications to the configuration file which are not compatible
with older versions of the software.

Note:
• Configuration files may become incompatible with prior releases even if no new features are
configured. The way in which a particular feature is represented in the configuration file may be
updated by the latest version of the operating software. The updated configuration file would then
be an unknown format to earlier software versions.

SR OS 13.0.R10 Software Release Notes 161


Software Upgrade Procedures

Alcatel-Lucent recommends performing an admin save and then making backup copies of the
BOOT Loader (boot.ldr), software image and configuration files (including bof.cfg and
*.ndx persistency files). These backups will be useful in case reverting to the old version of the
software is required.
If Lawful Intercept (LI) is being used on the router and bof li-local-save is enabled, then the
operator may want to save the LI configuration via configure li save and then backup the li.cfg
file.

STEP 2 Copy SR OS Images to cf3:


The SR OS image files must be copied to the cf3: device. It is good practice to place all of the
image files for a given release in an appropriately named subdirectory off the root, for example,
“cf3:\13.0.R10”. Copying the boot.ldr and other files in a given release to a separate
subdirectory ensures that all files for the release are available should downgrading the software
version be necessary. Note that as of Release 11.0.R1, the support.tim file must also be copied
for all platforms and configurations.

STEP 3 Copy boot.ldr to the Root Directory on cf3:


The BOOT Loader file is named boot.ldr. This file must be copied to the root directory of
the cf3: device.

STEP 4 Modify the Boot Options File to Point to the New Image
The Boot Options File (bof.cfg) is read by the BOOT Loader and indicates primary,
secondary and tertiary locations for the image file.
• The bof.cfg should be modified as appropriate to point to the image file for the release
to be loaded.
• Use the bof save command to save the Boot Options File modifications.

STEP 5 Synchronize Boot Environment


Once the Boot Options File has been modified, the active and standby CPM or CFM boot
environments must be synchronized.
• Use admin redundancy synchronize boot-env to synchronize the boot environments
between the active and standby CPMs/CFMs.

STEP 6 Reboot the Standby CPM/CFM


In the sample output below, the active CPM/CFM is in Slot A and the standby CPM/CFM is in
Slot B. Before performing ISSU on systems with CPMs, the show card output will display the
information similar to the following:

162 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

A:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up up
3 iom-20g-b iom-20g-b up up
4 iom-20g-b iom-20g-b up up
5 iom-20g-b iom-20g-b up up
A sfm4-12 sfm4-12 up up/active
B sfm4-12 sfm4-12 up up/standby
==============================================================================

Before performing ISSU on systems with CFMs, the show card output will display the
information similar to the following:
A:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
1 iom-xp iom-xp up up
A cfm-xp cfm-xp up up/active
B cfm-xp cfm-xp up up/standby
==============================================================================
• Use admin reboot standby now to reboot the standby CPM/CFM and start the ISSU
process.

After rebooting the standby CPM, the show card output will display information similar to the
following:
A:router1# admin reboot standby now
A:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up up
3 iom-20g-b iom-20g-b up up
4 iom-20g-b iom-20g-b up up
5 iom-20g-b iom-20g-b up up
A sfm4-12 sfm4-12 up up/active
B sfm4-12 up down/standby
==============================================================================

SR OS 13.0.R10 Software Release Notes 163


Software Upgrade Procedures

STEP 7 Wait for Standby CPM/CFM to Synchronize


After the ISSU has been initiated, the card status of the standby CPM/CFM (in Slot B in this
example) will show as “synching”, as in this example for systems with CPMs.
A:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up up
3 iom-20g-b iom-20g-b up up
4 iom-20g-b iom-20g-b up up
5 iom-20g-b iom-20g-b up up
A sfm4-12 sfm4-12 up up/active
B sfm4-12 sfm4-12 up synching/standby
==============================================================================

When the standby CPM/CFM has completely synchronized, the standby CPM/CFM will
indicate a state of “ISSU”, as in the following example for systems with CPMs.
A:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up up
3 iom-20g-b iom-20g-b up up
4 iom-20g-b iom-20g-b up up
5 iom-20g-b iom-20g-b up up
A sfm4-12 sfm4-12 up up/active
B sfm4-12 sfm4-12 up ISSU/standby
==============================================================================

For systems with CFMs:


A:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
1 iom-xp iom-xp up up
A cfm-xp cfm-xp up up/active
B cfm-xp cfm-xp up ISSU/standby
==============================================================================
Phase B - Minor ISSU
Phase B - Major ISSU

164 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

Phase B: Phase B of the ISSU procedure is different for Minor ISSU and Major ISSU. Proceed to the
appropriate procedure.
Completion
• Phase B (Minor ISSU)
of the ISSU
• Phase B (Major ISSU)

Phase B (Minor The following steps describe the rest of the ISSU procedure for Minor ISSU.
ISSU)

STEP 8 (Minor ISSU) Switchover the CPM/CFM


After the standby CPM/CFM has synchronized and indicates a card status of “ISSU”, a
CPM/CFM switchover (from A to B in this example) must be performed in order to force the
CPM/CFM running the new software image to become the active CPM/CFM. The switchover
command will cause the active CPM/CFM to reboot.
• Use admin redundancy force-switchover to make the CPM/CFM with the new software
image become the active CPM.
Note that, when the switchover command is issued, a warning will be printed if any cards are
equipped:
WARNING: After switchover, the following resets will be needed:
For each IOM/IMM that is equipped, regardless of state, a one (1) line summary is displayed to
indicate whether the card will be hard reset or Soft Reset, along with a reason for the hard reset.
See Step 8 of the Major ISSU procedure for more details.

Note:
• The isa-bb ISA cards will be automatically placed into a failed state by SR OS when the
force-switchover command is executed (for minor ISSU) until their host IOM is reset in
Step 11.

STEP 9 (Minor ISSU) If Necessary, Re-establish a Console Session


If the ISSU is performed from the serial port CONSOLE on the CPM/CFM and there is only
one terminal available (that is, one PC with a serial port), the console session must be re-
established on the newly active CPM/CFM.

STEP 10 (Minor ISSU) Wait for Standby CPM/CFM to Synchronize


Before continuing with the ISSU procedure, the standby CPM/CFM must re-synchronize by
transitioning from “down”, to “synchronizing”, and finally to the “up” state. Use the show card
command to monitor the status of the IOMs and IMMs. Note that the IOMs and IMMs now have
an “ISSU” status indicating that the active CPM/CFM is running the new image, as in this
example for systems equipped with CPMs.

B:router1# show card


==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational

SR OS 13.0.R10 Software Release Notes 165


Software Upgrade Procedures

Card-type Card-type State State


------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up ISSU
3 iom-20g-b iom-20g-b up ISSU
4 iom-20g-b iom-20g-b up ISSU
5 iom-20g-b iom-20g-b up ISSU
A sfm4-12 up down/standby
B sfm4-12 sfm4-12 up up/active
==============================================================================

B:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up ISSU
3 iom-20g-b iom-20g-b up ISSU
4 iom-20g-b iom-20g-b up ISSU
5 iom-20g-b iom-20g-b up ISSU
A sfm4-12 sfm4-12 up synching/standby
B sfm4-12 sfm4-12 up up/active
==============================================================================

B:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up ISSU
3 iom-20g-b iom-20g-b up ISSU
4 iom-20g-b iom-20g-b up ISSU
5 iom-20g-b iom-20g-b up ISSU
A sfm4-12 sfm4-12 up up/standby
B sfm4-12 sfm4-12 up up/active
==============================================================================
For systems equipped with CFMs, the CMAs/MDAs will never show an operational state of
“ISSU”. For CMAs/MDAs that require a hard reset, the operator may see “unequipped”,
“booting”, and then “up”

STEP 11 (Minor ISSU) Reset the line cards to Load the New Image
The IOMs, ISMs, and IMMs must now be reset to load the new image. This step is not necessary
for the 7750 SR-c12. If the cards will be Soft Reset (see below), see Soft Reset in the Known
Limitations section for the source/starting release of the upgrade. Soft Reset limitations should
be taken into account for planning purposes before the ISSU is performed.
• Use the clear card n soft hard-reset-unsupported-mdas command to Soft Reset a line
card. The line card data path and MDAs/ISAs are not reset in Soft Reset compatible cases,
resulting in a very brief service interruption.

166 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

• If the Soft Reset is blocked, then use the clear card n command to hard reset the line card.
This will reboot the line card and its MDAs and ISAs, causing an outage for the duration of
the reboot..

Notes:
• The system does not allow cards to run in an ISSU state indefinitely; the system automatically
hard resets the IOMs/IMMs/ISMs after two (2) hours. The “Comments” field in the show card
state output displays the time until the system resets the line cards in the ISSU state.
• It is recommended to Soft Reset no more than one line card at a time to ensure that the line card
download process does not impact control plane protocols. Wait for the operational state to be
“up” before proceeding to the next line card.
• With the Deferred MDA Reset enhancement (introduced in Release 10.0.R1), Soft Reset of a card
is allowed to proceed even when the MDA firmware does not match the MDA firmware in the
new image. The operator is informed of MDAs running below the latest revision of firmware with
CHASSIS log event #2082. The MDA can be upgraded to the latest firmware (after the Soft
Reset) by performing a hard reset of the MDA (clear mda x/y).

The sample output below shows the operational state transition for a single line card.
B:SoftReset1# clear card 4 soft
B:SoftReset1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up ISSU
3 iom-20g-b iom-20g-b up ISSU
4 iom-20g-b up soft reset
5 iom-20g-b iom-20g-b up ISSU
A sfm4-12 sfm4-12 up up/standby
B sfm4-12 sfm4-12 up up/active
========================================================================

When the IOM/IMM/ISM is in the “up” state, it will have the new image so it will no longer
have an “ISSU” operational state as shown in the sample output below.
B:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up ISSU
3 iom-20g-b iom-20g-b up ISSU
4 iom-20g-b iom-20g-b up up
5 iom-20g-b iom-20g-b up ISSU
A sfm4-12 sfm4-12 up up/standby
B sfm4-12 sfm4-12 up up/active
==============================================================================

SR OS 13.0.R10 Software Release Notes 167


Software Upgrade Procedures

The timing and order of the line card resets should be sequenced to maximize the effectiveness
of any redundant interfaces (LAGs, VRRP, etc.) spanning IOM/IMM/ISM, MDA, or any ISA
redundancy deployed slots.

The sample output below shows the operational state transitions for a single IOM in a system
equipped with CPMs.
B:router1# clear card 2
B:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b up provisioned
3 iom-20g-b iom-20g-b up ISSU
4 iom-20g-b iom-20g-b up up
5 iom-20g-b iom-20g-b up ISSU
A sfm4-12 sfm4-12 up up/standby
B sfm4-12 sfm4-12 up up/active
==============================================================================

When the line card is in the “up” state, it will have the new image so it will no longer have an
“ISSU” operational state as shown in the sample output below.
B:router1# show card

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational
Card-type Card-type State State
------------------------------------------------------------------------------
2 iom-20g-b iom-20g-b up up
3 iom-20g-b iom-20g-b up ISSU
4 iom-20g-b iom-20g-b up up
5 iom-20g-b iom-20g-b up ISSU
A sfm4-12 sfm4-12 up up/standby
B sfm4-12 sfm4-12 up up/active
==============================================================================

When all of the line cards have been rebooted, the ISSU is complete. It is recommended to save
the configuration (admin save) after an upgrade has been performed and the system is operating
as expected. This will ensure that all configurations are saved in a format that is fully compatible
with the newly running release.

Phase B (Major The following steps describe Phase B of the ISSU procedure for Major ISSU.
ISSU)

168 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

STEP 8 (Major ISSU) Switchover the CPM


Once the standby CPM has synchronized (Operational State = ISSU/standby), then the operator
can proceed to the next phase of Major ISSU.
Note that if the standby CPM is being held in the “down” operational state, take a look at log 99
for log events that explain the reason. For example, if the system contains deprecated hardware
such as the m4-choc3-sfp:
122 2015/05/30 16:21:03.83 EDT MAJOR: CHASSIS #2001 Base Card B
"Class CPM Module : failed, reason: Issu Unsupported Scenario, No Reload"

121 2015/05/30 16:21:03.84 EDT MAJOR: CHASSIS #2001 Base Card B


"Class CPM Module : failed, reason: Unsupported MDA type m4-choc3-sfp in
slot 1/2"

After the standby CPM has synchronized and indicates a card status of “ISSU/standby”, a CPM
switchover (from A to B in this example) must be performed in order to force the CPM running
the new software image to become the active CPM. The switchover command will cause the
active CPM to reboot.
• Use admin redundancy force-switchover to make the CPM with the new software image
become the active CPM.
Note that if the active CPM reboots for any reason other than the force-switchover command,
then the ISSU will be terminated and a full node reboot will occur.
When the switchover command is issued, a warning will be printed if any cards are equipped:
WARNING: After switchover the following HARD and SOFT resets will occur:

For each line card that is equipped, regardless of its state, a one (1) line summary is displayed
to indicate whether the card will be hard reset or Soft Reset, along with a reason for the hard
reset. The following example shows a particular card and MDA configuration, along with the
resulting ISSU hard reset or Soft Reset reasons.
A:Dut-A# show card
==============================================================================
Card Summary
==============================================================================
Slot Provisioned Equipped Admin Operational Comments
Card-type Card-type State State
------------------------------------------------------------------------------
1 imm1-100gb-cfp imm1-100gb-cfp up up
2 imm12-10gb-sf+ imm12-10gb-sf+ up up
3 imm5-10gb-xfp imm5-10gb-xfp up up
4 iom3-xp-b up unprovisioned
5 iom2-20g iom2-20g up up
7 imm3-40gb-qsfp imm3-40gb-qsfp up up
8 iom2-20g iom2-20g up up
9 iom2-20g iom2-20g up up
10 iom3-xp iom3-xp up up
A sfm4-12 sfm4-12 up up/active
B sfm4-12 sfm4-12 up ISSU/standby
==============================================================================

A:Dut-A# show mda


==============================================================================
MDA Summary

SR OS 13.0.R10 Software Release Notes 169


Software Upgrade Procedures

==============================================================================
Slot Mda Provisioned Equipped Admin Operational
Mda-type Mda-type State State
------------------------------------------------------------------------------
1 1 imm1-100gb-xp-cfp imm1-100gb-xp-cfp up up
2 1 imm12-10gb-xp-sf+ imm12-10gb-xp-sf+ up up
3 1 imm5-10gb-xp-xfp imm5-10gb-xp-xfp up up
5 1 m20-1gb-xp-sfp m20-1gb-xp-sfp up up
2 m4-choc3-as-sfp m4-choc3-as-sfp up up
7 1 imm3-40gb-xp-qsfp imm3-40gb-xp-qsfp up up
8 1 m2-10gb-xp-xfp m2-10gb-xp-xfp up up
2 m1-10gb-dwdm-tun m1-10gb-dwdm-tun up up
9 2 m4-choc3-as-sfp m4-choc3-as-sfp up up
10 1 m10-1gb-xp-sfp m10-1gb-xp-sfp up up
2 m10-1gb-hs-sfp-b m10-1gb-hs-sfp-b up up
==============================================================================

A:Dut-A# admin redundancy force-switchover


WARNING: After switchover the following HARD and SOFT resets will occur:
IOM 1: SOFT (MDAs: 1/1 SOFT)
IOM 2: SOFT (MDAs: 2/1 SOFT)
IOM 3: SOFT (MDAs: 3/1 SOFT)
IOM 4: HARD (offline)
IOM 5: SOFT (MDAs: 5/1 SOFT, 5/2 HARD (unsupported))
IOM 7: HARD (no Soft Reset capable MDAs: 7/1 incompatible)
IOM 8: SOFT (MDAs: 8/1 SOFT, 8/2 SOFT)
IOM 9: HARD (no Soft Reset capable MDAs: 9/1 not present, 9/2 unsupported)
IOM 10: SOFT (MDAs: 10/1 SOFT, 10/2 SOFT)

The reason codes are as follows:


• unsupported: Soft Reset not supported on the assembly
• incompatible: the specific upgrade scenario being attempted (from software image X to
software image Y) is not Soft Reset compatible (for example: mandatory datapath firmware
upgrades on an MDA or IMM)
• offline: the assembly is not currently operational
• not present: the card or MDA is not present
• any MDA hard reset forces IOM hard reset: one of the MDAs cannot be upgraded without
IOM hard reset
No reason codes are given for MDAs that are shut down (a reset of those MDAs will have no
impact on service), or for the second MDA identifier in a slot that contains an IMM.

After the IOM summary, the following prompt is given to the operator:
WARNING: Major in service software upgrade in progress.
Are you sure you want to switchover (y/n)?

The switchover may be blocked in various error scenarios. A warning will explain the problem.
For example, the following message will occur if the standby does not have enough compact
flash space for the configuration to be synchronized:
MINOR: CHMGR #1055 - Major ISSU sync of config to standby failed

170 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

If the switchover is attempted when the standby is not in an “ISSU/standby” state, then normal
High-Availability switchover behavior will apply.

STEP 9 (Major ISSU) If Necessary, Re-establish a Console Session


If the ISSU is performed from the serial port CONSOLE on the CPM, and there is only one
terminal available (i.e., one PC with a serial port), the console session must be re-established on
the newly active CPM.

STEP 10 (Major ISSU) Line Card Update


When the switchover command is used in Major ISSU, the active CPM will prepare the system
for the ISSU and then reboot. The other CPM (previously the standby and running the newer
software load) will take over as the active CPM.
After the switchover, a command prompt will be available on the newly active CPM.
Configuration changes are not allowed at this point, but most show, clear and admin
commands are available. If the operator attempts to use a command that is invalid during this
phase, they will receive the following error:
*B:Dut-A# configure service epipe 3 customer 1 create
MINOR: CLI Command not allowed while becoming active.

Once the Major ISSU is complete, the full CLI functionality will be available.
Shortly after the switchover, all line cards are reset so that they can upgrade to the new image.
The reset will be a Soft Reset for any supported combinations of cards, and hard reset for all
other cases (with reasons displayed for each line card as described in previous steps).

Note:
• The Soft Reset section of the Known Limitations in the Release Notes for the
source/starting release of the upgrade should be taken into account for planning
purposes before the ISSU is performed.

The sample output below shows the operational state transition for the cards in the system.
After the CPM running the new software image first takes over:
TiMOS-C-11.0.B1-106 cpm/hops ALCATEL SR 7750 Copyright (c) 2000-2015 Alcatel-
Lucent.
Login: admin
Password:

*B:Dut-A# show redundancy synchronization


==============================================================================
Synchronization Information
==============================================================================
Standby Status : disabled
Last Standby Failure : N/A
Standby Up Time : N/A
Standby Version : N/A
Failover Time : 05/30/2015 16:00:33
Failover Reason : user forced switchover
Boot/Config Sync Mode : None
Boot/Config Sync Status : No synchronization

SR OS 13.0.R10 Software Release Notes 171


Software Upgrade Procedures

Last Config File Sync Time : Never


Last Boot Env Sync Time : Never
Rollback Sync Mode : None
Rollback Sync Status : No Rollback synchronization
Last Rollback Sync Time : Never
==============================================================================

*B:Dut-A# show card


==============================================================================
Card Summary
==============================================================================
Slot Provisioned Type Admin Operational Comments
Equipped Type (if different) State State
------------------------------------------------------------------------------
1 imm1-100gb-cfp up soft reset
(not equipped)
2 imm12-10gb-sf+ up soft reset
(not equipped)
3 imm5-10gb-xfp up soft reset
(not equipped)
5 iom2-20g up soft reset
(not equipped)
7 imm3-40gb-qsfp up provisioned
(not equipped)
8 iom2-20g up soft reset
(not equipped)
9 iom2-20g up provisioned
(not equipped)
10 iom3-xp up soft reset
(not equipped)
A sfm4-12 up down/standby
(not equipped)
B sfm4-12 up up/active
==============================================================================

A few seconds later, most of the cards have been detected and are in the Soft Reset or booting
state. The standby CPM will remain as “down/standby” until all Soft Resets are completed.

==============================================================================
Card Summary
==============================================================================
Slot Provisioned Type Admin Operational Comments
Equipped Type (if different) State State
------------------------------------------------------------------------------
1 imm1-100gb-cfp up soft reset
2 imm12-10gb-sf+ up soft reset
3 imm5-10gb-xfp up soft reset
4 (not provisioned) up unprovisioned
iom3-xp-b
5 iom2-20g up soft reset
7 imm3-40gb-qsfp up booting
8 iom2-20g up soft reset
9 iom2-20g up booting
10 iom3-xp up soft reset
A sfm4-12 up down/standby
B sfm4-12 up up/active
==============================================================================

172 SR OS 13.0.R10 Software Release Notes


Software Upgrade Procedures

The following output shows the cards having completed their resets and are now running with
the new software image. The standby CPM will synchronize with the active CPM once all Soft
Resets are completed.

==============================================================================
Card Summary
==============================================================================
=
Slot Provisioned Type Admin Operational Comments
Equipped Type (if different) State State
------------------------------------------------------------------------------
1 imm1-100gb-cfp up up
2 imm12-10gb-sf+ up up
3 imm5-10gb-xfp up up
4 (not provisioned) up unprovisioned
iom3-xp-b
5 iom2-20g up up
7 imm3-40gb-qsfp up up
8 iom2-20g up up
9 iom2-20g up up
10 iom3-xp up up
A sfm4-12 up synching/standby
B sfm4-12