7705 Service Aggregation Router |

Release 9.0.R11

Software Release Notes

3HE147640011TQZZA

Edition: 01

15 July 2020

Nokia — Proprietary and confidential.

Use pursuant to applicable agreements.
Nokia is a registered trademark of Nokia Corporation. Other products and company
names mentioned herein may be trademarks or tradenames of their respective
owners.

The information presented is subject to change without notice. No responsibility is

assumed for inaccuracies contained herein.

© 2018-2020 Nokia. All rights reserved.

Contains proprietary/trade secret information which is the property of Nokia and

must not be made available to, or copied or used by anyone outside Nokia without
its written authorization. Not to be used or disclosed except in accordance with
applicable agreements.
7705 SAR 9.0.R11 Software Release Notes Contents

Contents
1 Release 9.0.R11 Documentation Set...................................................... 5

2 Release 9.0.R11 Supported Hardware ................................................... 7

3 Supported MPR-e Radios ..................................................................... 13

4 New Features ......................................................................................... 15

5 Unsupported Features on the 7705 SAR ............................................. 32

6 Enhancements ....................................................................................... 33

7 Changed or Deprecated Commands ................................................... 45

8 Usage Notes ........................................................................................... 47

9 Software Upgrade Procedures ............................................................. 54

10 Known Limitations ................................................................................ 74

11 Resolved Issues .................................................................................... 95

12 Known Issues ...................................................................................... 124

13 Release Load History .......................................................................... 131

Edition: 01 3HE147640011TQZZA 3
List of Tables 7705 SAR 9.0.R11 Software Release Notes

List of Tables
Table 1 7705 SAR Documentation Set......................................................................... 5
Table 2 7705 SAR Common Equipment ...................................................................... 7
Table 3 7705 SAR Adapter Cards ................................................................................ 8
Table 4 Accessories ................................................................................................... 11
Table 5 Common Equipment New in this Release ..................................................... 12
Table 6 Adapter Cards New in this Release............................................................... 12
Table 7 Accessories New in this Release .................................................................. 12
Table 8 Supported MPR-e Radio Hardware ............................................................... 13
Table 9 Bundled MPR-e Software .............................................................................. 13
Table 10 Realization Codes no Longer Supported ...................................................... 32
Table 11 7705 SAR Upgrade Capability....................................................................... 55
Table 12 Software Upgrade Notes ............................................................................... 57

4 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Release 9.0.R11 Documentation Set

1 Release 9.0.R11 Documentation Set

The 7705 SAR documentation set for this release consists of the documents listed in Table 1.
Table 1 7705 SAR Documentation Set

Nokia Part Number Guide

3HE14718AAACTQZZA_01 7705 SAR 10-port 1GigE / 1-port 10GigE X-Adapter Card Installation Guide
3HE14719AAACTQZZA_01 7705 SAR 2-port 10GigE (Ethernet) Adapter Card/ Module Installation Guide
3HE14720AAACTQZZA_01 7705 SAR 4-port SAR-H Fast Ethernet Module Installation Guide
3HE14721AAACTQZZA_01 7705 SAR 4-port T1/E1 & RS-232 Combination Module Installation Guide
3HE14722AAACTQZZA_01 7705 SAR 6-port E&M Adapter Card Installation Guide
3HE14723AAACTQZZA_01 7705 SAR 6-port SAR-M Ethernet Module Installation Guide
3HE14724AAACTQZZA_01 7705 SAR 6-port FXS Card Installation Guide
3HE14725AAACTQZZA_01 7705 SAR 8-port FXO Card Installation Guide
3HE15076AAABTQZZA_01 7705 SAR 8-port C37.94 Teleprotection Card Installation Guide
3HE14726AAACTQZZA_01 7705 SAR 8-port Voice & Teleprotection Card Installation Guide
3HE14727AAACTQZZA_01 7705 SAR Auxiliary Alarm Card Installation Guide
3HE14728AAACTQZZA_01 7705 SAR CWDM OADM Adapter Card/Module Installation Guide
3HE14729AAACTQZZA_01 7705 SAR DS3/E3 Adapter Card Installation Guide
3HE14730AAACTQZZA_01 7705 SAR DSL Module Installation Guide
3HE14731AAACTQZZA_01 7705 SAR Ethernet/Gigabit Ethernet Adapter Card Installation Guide
3HE14732AAACTQZZA_01 7705 SAR GNSS Receiver Card Installation Guide
3HE14733AAACTQZZA_01 7705 SAR GPON Module Installation Guide
3HE14734AAACTQZZA_01 7705 SAR GPS Receiver Module Installation Guide
3HE14735AAACTQZZA_01 7705 SAR Integrated Services Card Installation Guide
3HE14736AAACTQZZA_01 7705 SAR SONET/SDH Adapter Card Installation Guide
3HE14737AAACTQZZA_01 7705 SAR Packet Microwave Adapter Card Installation Guide
3HE14738AAACTQZZA_01 7705 SAR Power Injector Card Installation Guide
3HE14739AAACTQZZA_01 7705 SAR Serial Data Interface Card Installation Guide
3HE14740AAACTQZZA_01 7705 SAR T1/E1 ASAP Adapter Card Installation Guide
3HE14741AAACTQZZA_01 7705 SAR-18 Chassis Installation Guide
3HE14742AAACTQZZA_01 7705 SAR-8 Chassis Installation Guide
3HE14743AAACTQZZA_01 7705 SAR-A Chassis Installation Guide
3HE14744AAACTQZZA_01 7705 SAR-Ax Chassis Installation Guide
3HE14745AAACTQZZA_01 7705 SAR-H Chassis Installation Guide
3HE14746AAACTQZZA_01 7705 SAR-Hc Chassis Installation Guide
3HE14747AAACTQZZA_01 7705 SAR-M Chassis Installation Guide
3HE14748AAACTQZZA_01 7705 SAR-O Chassis Installation Guide
3HE14749AAACTQZZA_01 7705 SAR-W Chassis Installation Guide
3HE14750AAACTQZZA_01 7705 SAR-Wx Chassis Installation Guide
3HE14751AAACTQZZA_01 7705 SAR-X Chassis Installation Guide

Edition: 01 3HE147640011TQZZA 5
Release 9.0.R11 Documentation Set 7705 SAR 9.0.R11 Software Release Notes

Nokia Part Number Guide

3HE14752AAACTQZZA_01 7705 SAR Basic System Configuration Guide
3HE14753AAACTQZZA_01 7705 SAR Interface Configuration Guide
3HE14754AAACTQZZA_01 7705 SAR Log Events Guide
3HE14755AAACTQZZA_01 7705 SAR MPLS Guide
3HE14756AAACTQZZA_01 7705 SAR OAM and Diagnostics Guide
3HE14757AAACTQZZA_01 7705 SAR Quality of Service Guide
3HE14758AAACTQZZA_01 7705 SAR Router Configuration Guide
3HE14759AAACTQZZA_01 7705 SAR Routing Protocols Guide

3HE14760AAACTQZZA_01 7705 SAR Services Guide

3HE14761AAACTQZZA_01 7705 SAR System Management Guide

3HE14762AAACTQZZA_01 7705 SAR Zipped Collection

6 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Release 9.0.R11 Supported Hardware

2 Release 9.0.R11 Supported Hardware

The following tables summarize the hardware supported in this release.
Table 2 7705 SAR Common Equipment

Nokia Part Number Description Introduced

3HE02773AA 7705 SAR-8 Shelf R1.0.R1
3HE02778AA 7705 SAR-8 Fan Module R1.0.R1
3HE02778AB SAR-8 Fan Module (-48V) – Extended Temperature R2.0.R1
3HE02778BA SAR-8 Fan Module (+24V) – Extended Temperature R2.0.R1
3HE04991AA SAR-18 Shelf R4.0.R1
3HE04992AA Control Switch Module for SAR-18 R4.0.R1
3HE04993AA Fan Module for SAR-18 R4.0.R1
3HE04994AA Alarm Module for SAR-18 R4.0.R1
3HE05051AB SAR-M with 16 T1/E1, 7 GigE, -48/+24 VDC R5.0.R1
3HE05653AA SAR-M with 7 GigE, -48/+24 VDC R5.0.R1
3HE06791AA SAR-8 Shelf V2 R5.0.R1
3HE06792AA Fan Module for SAR-8 Shelf V2 Ext. Temp (-48VDC) R5.0.R1
3HE06790AA SAR-M Fanless with 16 T1/E1, 7GigE, -48/+24VDC R5.0.R2
3HE06793AA SAR-M Fanless with 7 GigE, -48/+24VDC R5.0.R2
3HE02774AB SAR-8 CSMv2 (-48/+24VDC) R6.0.R1
3HE06792BA Fan Module for the SAR-8 Shelf V2 Ext. Temp (+24VDC) R6.0.R1
3HE06797AA SAR-A with 12 Ethernet Ports, 8 T1/E1 (-48VDC) R6.0.R2
3HE06796AA SAR-A with 12 Ethernet Ports (-48VDC) R6.0.R2
3HE07349AA SAR-W R6.0.R1
3HE07939AA SAR-O 2-Fiber CWDM 4-color 1471-1531 N/A
3HE07939BA SAR-O 2-Fiber CWDM 4-color 1551-1611 N/A
3HE07940AA SAR-O 1-Fiber CWDM 8-color Mux (Up) N/A
3HE07940BA SAR-O 1-Fiber CWDM 8-color Mux (Dn) N/A
3HE07614AA SAR-Wx w/ 5 GigE & AC power R6.1.R2
3HE07616AA SAR-Wx w/ 5 GigE, PoE+ & AC power R6.1.R2
3HE07615AA SAR-Wx w/ 5 GigE, GPS Rx & AC power R6.1.R4
3HE07617AA SAR-Wx w/ 5 GigE, PoE+, GPS Rx & AC power R6.1.R4
3HE07618AA SAR-Wx w/ 4 GigE, 4 xDSL & AC power R6.2.R2
3HE07619AA SAR-Wx w/ 4 GigE, 4 xDSL, GPS Rx & AC power R6.2.R2
3HE06969AA SAR-H High Voltage Shelf R6.1.R1
3HE06969BA SAR-H Low Voltage Shelf R6.1.R1
3HE06969CA SAR-H High Voltage Shelf w/ Conformal Coat R6.1.R2
3HE06969DA SAR-H Low Voltage Shelf w/ Conformal Coat R6.1.R2
3HE07353AA SAR-Hc R6.1.R1
3HE07353BA SAR-Hc w/ Conformal Coat R6.1.R2

Edition: 01 3HE147640011TQZZA 7
Release 9.0.R11 Supported Hardware 7705 SAR 9.0.R11 Software Release Notes

Nokia Part Number Description Introduced

3HE05051BB SAR-M with 16 T1/E1, 7 GigE, -48/+24 VDC w/ Conformal Coat R6.1.R2
3HE05653BA SAR-M with 7 GigE, -48/+24 VDC w/ Conformal Coat R6.1.R2
3HE02774CB SAR-8 CSMv2 (-48/+24VDC) w/Conformal Coat R6.1.R1
3HE06791BA SAR-8 Shelf V2 w/ Conformal Coat R6.1.R1
3HE06792CA Fan Module for SAR-8 Shelf V2 Ext. Temp (-48VDC) w/ Conformal Coat R6.1.R1
3HE06792DA Fan Module for SAR-8 Shelf V2 Ext. Temp (+24VDC) w/ Conformal R6.1.R1
Coat
3HE06972AA 100W HV Power Supply R6.1.R1
3HE06970AA SAR-H 100W 48V DC Power Supply - HV Input R6.1.R1
3HE06970BA SAR-H 100W 48V DC Power Supply - LV Input R6.1.R1
3HE06970CA 100W 48V DC Power Supply - HV Input /Conformal Coated R6.1.R2
3HE06970DA 100W 48V DC Power Supply - LV Input /Conformal Coated R6.1.R2
3HE08703AA SAR-Wx/W 5-ft Console Cable (RJ45 to DB9 adapter) R6.1.R1
3HE08533AA 7705 SAR-X, AC power R7.0.R1
3HE08534AA 7705 SAR-X, DC power R7.0.R1
3HE06792EA Fan Module for SAR-8 Shelf V2 Ext. Temp (-48/+24 VDC) R7.0.R2
3HE06792FA Fan Module for SAR-8 Shelf V2 Ext. Temp (-48/+24 VDC) w/ Conformal R7.0.R2
Coat
3HE10329AA 7705 SAR-Ax R8.0.R1
3HE10328AA SYS - 7210 SAS-Sx SONET/SDH ETR DC R8.0.R4

Table 3 7705 SAR Adapter Cards

Nokia Part Description Introduced

Number
3HE02776AB 8 Port GE/FE Ethernet Card V2 R1.1.R1

3HE03125AA 4 Port OC3c/STM1c POS/ATM Card R2.0.R1

3HE02776BA 8 Port GE/FE Ethernet V2 (+24V) R2.0.R1

3HE03127AA 2P OC3/STM1 CH R2.1.R1

3HE03391AA 12 Port Serial Data Card R2.1.R2

3HE04962AA 4 Port DS3/E3 Card (-48V) R3.0.R1

3HE04962BA 4 Port DS3/E3 Card (+24V) R3.0.R1

3HE03126AA 6 Port E&M Interface Card R3.0.R2

3HE02772AA Auxiliary Alarm Card (-48V/+24 VDC) R3.0.R3

3HE02781AA 32-port T1/E1 ASAP Card V2 (-48/+24 VDC) R4.0.R3

3HE02775AB 16-port T1/E1 ASAP Card V2 (-48/+24 VDC) R4.0.R3

3HE05126AA GPON Module for the SAR-M R5.0.R1

3HE05577AA xDSL Module for the SAR-M R5.0.R1

3HE05914AA DSL Combination Module (DCM) for the SAR-M R5.0.R1

3HE06582BA SAR-M OADM Add/Drop CWDM 1471 R5.0.R1

8 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Release 9.0.R11 Supported Hardware

Nokia Part Description Introduced

Number
3HE06582BB SAR-M OADM Add/Drop CWDM 1491 R5.0.R1

3HE06582BC SAR-M OADM Add/Drop CWDM 1511 R5.0.R1

3HE06582BD SAR-M OADM Add/Drop CWDM 1531 R5.0.R1

3HE06582BE SAR-M OADM Add/Drop CWDM 1551 R5.0.R1

3HE06582BF SAR-M OADM Add/Drop CWDM 1571 R5.0.R1

3HE06582BG SAR-M OADM Add/Drop CWDM 1591 R5.0.R1

3HE06582BH SAR-M OADM Add/Drop CWDM 1611 R5.0.R1

3HE06582AA SAR-8/18 OADM Add/Drop CWDM 1471 R5.0.R1

3HE06582AB SAR-8/18 OADM Add/Drop CWDM 1491 R5.0.R1

3HE06582AC SAR-8/18 OADM Add/Drop CWDM 1511 R5.0.R1

3HE06582AD SAR-8/18 OADM Add/Drop CWDM 1531 R5.0.R1

3HE06582AE SAR-8/18 OADM Add/Drop CWDM 1551 R5.0.R1

3HE06582AF SAR-8/18 OADM Add/Drop CWDM 1571 R5.0.R1

3HE06582AG SAR-8/18 OADM Add/Drop CWDM 1591 R5.0.R1

3HE06582AH SAR-8/18 OADM Add/Drop CWDM 1611 R5.0.R1

3HE06583AA SAR-8/18 OADM Add/Drop 1471/1491 R5.0.R1

3HE06583AB SAR-8/18 OADM Add/Drop 1511/1531 R5.0.R1

3HE06583AC SAR-8/18 OADM Add/Drop 1551/1571 R5.0.R1

3HE06583AD SAR-8/18 OADM Add/Drop 1591/1611 R5.0.R1

3HE06584AA SAR-8/18 OADM 4 color Add/Drop 1471/1491/1511/1531 R5.0.R1

3HE06584AB SAR-8/18 OADM 4 color Add/Drop 1551/1571/1591/1611 R5.0.R1

3HE06585AA SAR-8/18 8 Color Mux/Demux 1471–1611 R5.0.R1

3HE06151AA 8-Port GE SFP Card (-48/+24 VDC) R5.0.R2

3HE06153AA 1 Port 10GE / 10 Port 1GE 10G-Card R5.0.R3

3HE06006AA 8-Port Voice and Teleprotection Card R5.0.R4

3HE02782AA Packet Microwave Card R5.0.R4

3HE07152AA Power Injector Card R5.0.R4

3HE06151AB 8-Port GE SFP Card V2 (-48/+24 VDC) R6.0.R1

3HE06794AA 8-Port FXO Adapter Card (-48/+24 VDC) R6.0.R1

3HE06789AA 2-Port 10GigE (Ethernet) XFP Card (-48/+24 VDC) R6.0.R1

3HE06153AC 1-Port 10GE / 10-Port 1GE 10G Card V2 – IPSec Capable R6.0.R4

3HE06151AC 8-Port GE SFP Card V3 – IPSec-Capable R6.0.R4

3HE02780AA 6-port FXS Adapter Card R6.0.R5

3HE07942AA Integrated Services Card R6.1.R1

3HE06788AA 2-Port 10 GigE (Ring) Module - SAR-M R6.1.R1

3HE06788BA 2-Port 10 GigE (Ring) Module - SAR-M w/ Conformal Coat R6.1.R2

3HE06973AA SAR-H T1/E1 ASAP/Serial Combo Module R6.1.R1

3HE06973BA SAR-H T1/E1 ASAP/Serial Combo Module w/ Conformal Coat R6.1.R2

Edition: 01 3HE147640011TQZZA 9
Release 9.0.R11 Supported Hardware 7705 SAR 9.0.R11 Software Release Notes

Nokia Part Description Introduced

Number
3HE02776CB 8 Port GE/FE Ethernet Card V2 (-48 VDC) w/ Conformal Coat R6.1.R1

3HE02776DA 8 PORT GE/FE Ethernet Card V2 (+24 VDC) w/ Conformal Coat R6.1.R2

3HE03391BA 12 Port Serial Data Card w/ Conformal Coat R6.1.R1

3HE02775CB 16-port T1/E1 ASAP Card V2 (-48/+24 VDC) w/ Conformal Coat R6.1.R1

3HE06151BB 8-Port GE SFP Card V2 (-48/+24 VDC) w/ Conformal Coat R6.1.R1

3HE06151BC 8-Port GE SFP Card V3 – IPSec-Capable w/ Conformal Coat R6.1.R1

3HE06789BA 2-Port 10GigE (Ethernet) XFP Card (-48/+24 VDC) R6.1.R1

w/ Conformal Coat

3HE07938AA 4-Port OC3/STM1 Channelized Card R6.1.R4

3HE03125BA 4 Port OC3c/STM1c POS/ATM Card w/ Conformal Coat R6.1.R2

3HE03126BA 6 Port E&M Interface Card w/ Conformal Coat R6.1.R2

3HE03127BA 2P OC3/STM1 CH w/ Conformal Coat R6.1.R2

3HE07152BA Power Injector Card w/ Conformal Coat R6.1.R2

3HE02782BA Packet Microwave Card w/ Conformal Coat R6.1.R2

3HE02772BA Auxiliary Alarm Card (-48V/+24 VDC) w/ Conformal Coat R6.1.R2

3HE06006BA 8-Port Voice and Teleprotection Card w/ Conformal Coat R6.1.R2

3HE06794BA 8-Port FXO Adapter Card (-48/+24 VDC) w/ Conformal Coat R6.1.R2

3HE02780BA 6-port FXS Adapter Card w/ Conformal Coat R6.1.R2

3HE07955AA SAR-H GPS Receiver Module R6.1.R3

3HE07943AA 6-port Ethernet 10Gbps Adapter Card R6.2.R1

3HE07943BA 6-port Ethernet 10Gbps Adapter Card w/ Conformal Coat R6.2.R1

3HE03391AB 12-port Serial Data Card v2 R6.2.R1

3HE03391BB 12-port Serial Data Card v2 w/ Conformal Coat R6.2.R1

3HE09303AA 4-port SAR-H Fast Ethernet Module R7.0.R1

3HE09303BA 4-port SAR-H Fast Ethernet Module w/ Conformal Coat R7.0.R1

3HE09170AA 6-port SAR-M Ethernet Module R7.0.R2

3HE09170BA 6-port SAR-M Ethernet Module w/ Conformal Coat R7.0.R2

3HE07954AA GNSS Receiver Card R7.0.R4

3HE12433AA 6-port Ethernet 10Gbps Adapter Card-E (no encryption) R8.0.R10

3HE12433BA 6-port Ethernet 10Gbps Adapter Card-E (no encryption) w/ Conformal Coat R8.0.R10

Note: The 7705 SAR hardware supports qualified pluggable optic modules only.
Refer to the current Nokia price list for supported modules. Third-party
optics are not supported.

10 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Release 9.0.R11 Supported Hardware

Table 4 Accessories

Nokia Part Number Description Introduced

3HE01619AA CF – 2G Compact Flash R3.0.R4

3HE04707AA CF – 4G Compact Flash R3.0.R4

3HE04708AA CF – 8G Compact Flash R3.0.R4

3HE04995AA Air Filter for SAR-18 (4 pack) R4.0.R1

3HE03054AA 7705 SAR-8 Blanking Plates (6 PK) N/A

3HE06022AA CSM Blanking Plate for SAR-18 R4.0.R1

3HE05838AA 250W 120/240V AC Power Converter N/A

3HE05837AA 7705 AC Power Converter Pigtail – D-sub N/A

3HE05837BA 7705 AC Power Converter Pigtail – O-ring N/A

3HE07800AA SAR-W Mounting Bracket Kit R6.0.R1

3HE07801AA SAR-W Carrying Handle Kit R6.0.R1

3HE07771AA SAR-8 DC Port Surge Protector Kit N/A

3HE07945AA SAR-Hc Panel Mounting H/W Kit - Rear Mount R6.1.R1

3HE07945AB SAR-Hc Panel Mounting H/W Kit - Side Mount R6.1.R1

3HE07357AA SAR-Hc Din Mounting H/W Kit -Rear Mount R6.1.R1

3HE07357AB SAR-Hc Din Mounting H/W Kit -Side Mount R6.1.R1

3HE07957AA SAR-Wx Pole/Wall Mounting Bracket R6.1.R2

3HE07958AA SAR-Wx Strand Mounting Bracket R6.1.R2

3HE06971AA SAR-H PoE Power Supply mounting tray R6.1.R1

3HE07769AA 7705 SAR-H Wall/reverse rack mounting kit R6.1.R1

3HE07770AA 7705 SAR-H PoE Wall Mount kit R6.1.R1

3HE07961AA SAR-H/8/18 1m GPS Cable (Din/Din) R6.1.R3

3HE07962AA SAR-H/8/18 1m GPS Cable (Din/N) R6.1.R3

3HE07959AA SAR-Wx GPS Antenna Mounting R6.1.R4

3HE07960AA SAR-Wx 0.35m GPS Cable R6.1.R4

3HE09584AA 7705 SAR-W Paintable Wrap R6.2.R1

3HE09389AA 7705 SAR-W Strand Mounting Bracket R6.2.R1

3HE08608AA X.21 to RS-530 Adapter Cable R7.0.R1

3HE09257AA 7705 SAR-X Air Filter Media Replacement Kit (10 filters) R7.0.R1

3HE10040AA AC Power Cable for SAR-X or SAR-H – North America (6 ft) R7.0.R1

3HE10040AA AC Power Cable for SAR-X or SAR-H – Europe (8 ft) R7.0.R1

3HE10338AA Power Surge Protection Kit R7.0.R1

3HE10339AA CPX DC Defender Modules R7.0.R1

3HE09698AA SAR-W/SAR-O Rack/Cabinet Mounting Bracket Kit R7.0.R1

3HE09411AA Ethernet Cable with RJ.5 and RJ45 (6 m) R7.0.R2

3HE09411BA Ethernet Cable with RJ.5 and RJ45 (20 m) R7.0.R2

3HE09411CA Ethernet Cable with RJ.5 and RJ45 (50 m) R7.0.R2

Edition: 01 3HE147640011TQZZA 11
Release 9.0.R11 Supported Hardware 7705 SAR 9.0.R11 Software Release Notes

Note: The 7705 SAR hardware supports Nokia-sourced compact flash devices
only. Third-party compact flash devices are not supported.

The following tables summarize the new hardware supported in this release.
Table 5 Common Equipment New in this Release

Nokia Part Number Description Introduced Minimum

Software
Release

Table 6 Adapter Cards New in this Release

Nokia Part Number Description Introduced Minimum

Software
Release
3HE03391AC 12-port Serial Data Card v3 -48/+24VDC 9.0.R1 9.0.R1

3HE03391BC 12-port Serial Data Card v3 -48/+24VDC w/ Conformal Coat 9.0.R1 9.0.R1

3HE12504AA 8-port C37.94 Teleprotection Card/TPC 9.0.R4 9.0.R4

3HE12504BA 8-port C37.94 Teleprotection Card/TPC CC 9.0.R4 9.0.R4

Table 7 Accessories New in this Release

Nokia Part Number Description Introduced

3HE12409AA DTE Cable for SDIv3 9.0.R1

3HE12410AA DCE Cable for SDIv3 9.0.R1

3HE12442AA 4 -port RS-232 Dist Panel, SDIv3 only 9.0.R1

3HE12443AA 4-port RS-530 Dist Panel, SDIv3 only 9.0.R1

3HE12444AA 4-port X.21 Dist Panel, SDIv3 only 9.0.R1

3HE12445AA 4-port V.35 Dist Panel, SDIv3 only 9.0.R1

3HE12520AA C37.94 Adapter Fiber Cable (5 pack) 9.0.R4

12 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Supported MPR-e Radios

3 Supported MPR-e Radios

The 7705 SAR Release 9.0 OS supports MPR-e radios operating in Single NE mode when
attached to the 7705 SAR. Applicable MPR-e OS licenses may be required.

3.1 Supported MPR-e Radios

Table 8 summarizes the MPR-e radio hardware that is supported in Single NE mode in this release.
Table 8 Supported MPR-e Radio Hardware

Nokia Packet Radio* Description Introduced

MPT-XP MPR-e family R6.0.R1

MPT-HCv2 MPR-e family R6.0.R1

MPT-MC MPR-e family R6.0.R1

9558HC MPR-e family R6.0.R1

MPT-HLC MPR-e family R6.2.R2

MPT-HQAM MPR-e family R6.2.R2

MPT-HLC+ MPR-e family R9.0.R5

• If specific part numbers are required, please contact Nokia or refer to the 9500 MPR or Wavence Release Notes
available on OLCS as listed in Table 9.

3.2 Supported MPR-e Software

MPR-e radios operating in Single NE mode require specific software that is included in the 7705
SAR Release 9.0 OS software bundle. Three bundles of the 7705 SAR Release 9.0 OS software
are available. The bundle named “7705-TiMOS.9.0.R11.MWA.zip” is required when the 7705 SAR
has MPR-e radios operating in Single NE mode. Table 9 summarizes the MPR-e radio software
that is bundled for each 7705 SAR release, as well as a reference to the applicable MPR-e
Software Release Notes.
Table 9 Bundled MPR-e Software

7705 SAR Release MPR-e Software MPR-e Release Notes

Release
All 6.0.Rx and 6.1.Rx loads 4.1.0 3DB 19043 AAAA FMZZA (ETSI)
3DB 19043 AAAA DEZZA (ANSI)
All 6.2.Rx loads beginning with 6.2.R2 and all 7.0.Rx loads 6.0.0 3DB 19257 AAAA VCZZA

All 8.0.Rx loads, as well as 9.0.R2 and 9.0.R3 (9.0.R1 and 7.0.0 3DB 19356 AAAA DEZZA
9.0.R4 do not support MPR-e radios in Single NE mode)

9.0.R5 through 9.0.R7 19 3DB 17600 AAAA DEZZA

9.0.R8 and above 19 ICS02 3DB 17600 AAAA DEZZA 04

Edition: 01 3HE147640011TQZZA 13
Supported MPR-e Radios 7705 SAR 9.0.R11 Software Release Notes

Note: For more details on the 7705 SAR upgrade procedure with the MPR-e,
see Standard Software Upgrade Procedure.

14 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4 New Features
The following sections describe the new features in Release 9.0.

Note: Some features supported on the 7705 SAR product family require a
Right-to-Use (RTU) license. Contact your Nokia representative for the
appropriate application licenses.
BETA: Some features are made available in the current release and are
considered BETA quality. They are not fully tested but are enabled in the
CLI and are suitable for lab trials.
ALPHA: Some features are made available in the current release but are
considered ALPHA quality. They are not fully tested but are enabled in
the CLI and are suitable for customer demonstrations.
BETA and ALPHA features are marked as applicable.

Note: New features that were added in earlier releases, but which were not
documented until the current release, are marked as [NEW] and are
documented in the section for the applicable release.

4.1 Release 9.0.R11

There are no new features in this release.

4.2 Release 9.0.R10

There are no new features in this release.

4.3 Release 9.0.R9

4.3.1 HMAC Strengthening (SHA-224/256/384/512)

Release 9.0.R9 enhances SSH MAC algorithms. In previous releases, the cipher algorithms and
security in SSH were enhanced. MAC algorithms were hard-coded, and their indexes were not
configurable in the SSH negotiation list. The following two capabilities are added in this release:

• stronger SHA-2 HMAC algorithms for HMAC-SHA2-256 and HMAC-SHA2-512

• configurable MAC list for SSHv2 – MAC algorithms can be added to and removed from
this list. Stronger algorithms can also be placed at the top of the list (lower index values)
to be negotiated first.

Edition: 01 3HE147640011TQZZA 15
New Features 7705 SAR 9.0.R11 Software Release Notes

4.3.2 SR-ISIS on 8-port Ethernet Adapter Card v2

The 8-port Ethernet Adapter card v2 now supports Segment Routing (SR) extensions for IS-IS and
IPv4. Support on second- and third-generation Ethernet adapter cards was added in 9.0.R1. Note
that Segment Routing support on the 8-port Ethernet Adapter card v2 is limited to SR-ISIS;
therefore, SR-TE, TI-LFA, entropy label, and SR-ISIS LDP stitching are not supported.

4.4 Release 9.0.R8

4.4.1 MPLS Statistics

This feature introduces RSVP point-to-point LSP egress and ingress statistics at the iLER and
eLER only on a per-FC and per-in/out profile basis with both packet and byte counters and LDP
FEC (unicast) egress statistics at the iLER and transit nodes (LSR/ASBR/ABR) only on a per-FC
and per-in/out profile basis with both packet and byte counters.
These statistics allow operators to monitor traffic being forwarded or received by 7705 SAR routers
when transported over an RSVP LSP or LDP FEC and may be used in network traffic engineering
and capacity planning.

4.4.2 TI-LFA for OSPF

TI-LFA is now supported for OSPF in addition to IS-IS. SR extensions are supported only for
OSPFv2.

4.4.3 MWA: G.826 Performance Monitoring Statistics

This feature provides historical data access in the router and NSP management system of the PM
statistics from each attached microwave radio in MWA mode. Statistics are collected at 15-min. and
24-hr intervals and include G.826 statistics, Radio Power Level statistics, and Adaptive Coding and
Modulation statistics.

4.4.4 IKEv2 Fragmentation for PKI

IKEv2 fragmentation (as per RFC 7383) enables the 7705 SAR to avoid IP fragmentation of large
IKEv2 messages, thus allowing IKEv2 messages to traverse network devices that do not allow IP
fragments to pass through. This is achieved by doing fragmentation at the IKEv2 layer and
generating IP packets that are smaller than the network MTU so that they are not fragmented
throughout the network.

16 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4.4.5 Per-DS0 CAS Support on 2-port OC3/STM1 Channelized Adapter Card and 4-port
DS3/E3 Adapter Card

Support for per-DS0 CAS has been extended to T1/E1 channels on the 2-port OC3/STM1
Channelized Adapter card and the 4-port DS3/E3 Adapter card. In previous releases, a restriction
existed such that all the DS0 channels within a T1/E1 on these adapter cards had to either have
CAS enabled or CAS disabled.

4.5 Release 9.0.R7

4.5.1 Multi-chassis Firewall

Multi-chassis firewall synchronizes firewall and NAT states between two 7705 SAR chassis. Both
chassis can have traffic traversing them, but they create a single firewall/NAT database (on the
master chassis) that will be synchronized and shared between the two chassis. If one firewall in
multi-chassis firewall fails, all the known UDP/TCP sessions and states are present in the second
chassis. The connection can therefore continue transmitting traffic on a 5-tuple session without re-
establishing the state of the session. As an example, if there is a TCP connection on the first
firewall that has gone through the three states of TCP, that information is synchronized to the
second firewall. If there is a failure on the first firewall where the session originally was established
and the traffic gets rerouted to the second firewall in the pair, the second firewall can forward the
traffic on the same TCP connection without any interruption because it knows the state of the
connection. Multi-chassis firewall uses the multi-chassis protocol to synchronize these states. Nokia
recommends that a dedicated port be used for the multi-chassis link for security and resiliency.
All firewall functionality in the GRT and VPRN is supported in multi-chassis mode except for strict
TCP. As well, in order for NAT to work in multi-chassis firewall and to have the same NAT state
between the two firewalls, a loopback interface should be used.
IPSec uplinks in VPRN are not currently supported by multi-chassis firewall.

4.5.2 Stronger Hash/Hash2 Algorithms

This feature adds support of AES encryption protocols for hashing of critical phrases.

4.5.3 CTR Ciphers for SSH

In previous releases, SSH only supported AES-CBC. CTR is another block cipher for AES that
provides stronger block ciphers.

Edition: 01 3HE147640011TQZZA 17
New Features 7705 SAR 9.0.R11 Software Release Notes

4.5.4 Cflowd: Egress Layer 3 and Ingress Layer 2

This feature extends Cflowd sampling to Layer 3 interfaces at egress and Layer 2 SAPs at ingress.
Egress sampling on Layer 3 interfaces can be extremely useful in SDN controller-managed
networks with flow-based information that can help steer traffic in case of congestion and similar
issues. The feature adds NetFlow version 9 and version 10 support for Layer 3 egress and Layer 2
ingress applications.

4.5.5 MPLS Secondary Path Preference

In topologies where there is more than one secondary LSP protecting the primary LSP, this feature
provides the ability to assign preferences to the secondary LSPs for a more deterministic selection
process. The feature also supports skipping a secondary LSP when it is not available in order to
ensure availability.

4.5.6 Entropy Label for SR-ISIS, SR-OSPF, SR-TE

Entropy label is a standard way of load balancing traffic across MPLS networks. Entropy label
support on the 7705 SAR is extended to include segment routing LSPs. Entropy label can now be
pushed for traffic riding over SR-TE LSPs. Load balancing based on EL/ELI in an intermediate
label-switching router is already supported.

4.5.7 BGP Next-Hop Resolution Filter

This feature adds the flexibility to attach a route policy to the BGP next-hop resolution process for a
more deterministic process based on preferences; it also allows a route policy to be associated with
the optional BGP peer-tracking function.

4.5.8 BGP Link State (BGP-LS)

BGP-LS allows BGP to be used to distribute IGP topology information to external servers such as
Path Computation Element (PCE) servers. The external traffic engineering database can then use
this information in calculating optimal paths through the associated network.

4.5.9 EVPN-VPLS over MPLS with RT=5 Unicast (R-VPLS)

The EVPN-VPLS offering on the 7705 SAR is extended to include route type 5 (advertisement of IP
reachability information under EVPN service) with this release. Route type 5 support under EVPN-
VPLS enables EVPN-VPLS to be used not only for Layer 2 point-to-multipoint reachability but also
for Layer 3 VPN services. This provides a unified solution for VPN services with scalable BGP-
based signaling for exchanging reachability and status updates, including multihoming status.

18 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4.5.10 Type I and Type II Signaling for A-Law on E&M Ports

The ports of the 6-port E&M Adapter card have been enhanced to support Type I and Type II
signaling for A-Law companding type, in addition to the already supported Type V signaling.

4.5.11 ATM SAP on Epipe with SDP

ATM SAP support for Epipe services has been added for business services, originating from ATM
interfaces. Interworking of BPDUs is supported between the 4-port OC3/STM1 Clear Channel
Adapter card and the 6-port Ethernet 10Gbps Adapter card with Epipe services over the MPLS
network.

4.5.12 Multicast over Layer 3 Spoke SDP

Multicast over Layer 3 spoke-SDP termination is supported in VPRN and IES services. Only PIM
signaling is supported over the Layer 3 spoke SDP interface. In addition, only IPv4 is supported in
VPRN. IPv4 and IPv6 is supported in IES. (D.291813)

4.5.13 Passive VRRP and Multihoming for R-VPLS EVPN

The 7705 SAR supports the multihoming all-active and active/standby solution under EVPN-VPLS
for IP-based services. Multihoming with EVPN-VPLS route type 5 requires passive VRRP to
facilitate seamless activity switchover among participating SAPs.

4.5.14 IPSec over VPRN Public MP-BGP GRE

For IPSec public service VPRN, transport tunnel GRE is now supported. IPSec packets arriving on
the public interface can now be transported over GRE auto-bind or SDP tunnels signaled via MP-
BGP.

4.5.15 MPLS Statistics (BETA)

This feature introduces RSVP point-to-point LSP egress and ingress statistics at the iLER and
eLER only on a per-FC and per-in/out profile basis with both packet and byte counters and LDP
FEC (unicast) egress statistics at the iLER and transit nodes (LSR/ASBR/ABR) only on a per-FC
and per-in/out profile basis with both packet and byte counters.
These statistics allow operators to monitor traffic being forwarded or received by 7705 SAR routers
when transported over an RSVP LSP or LDP FEC and may be used in network traffic engineering
and capacity planning.

4.5.16 TI-LFA for OSPF (BETA)

TI-LFA is now supported for OSPF in addition to IS-IS. SR extensions are supported only for
OSPFv2.

Edition: 01 3HE147640011TQZZA 19
New Features 7705 SAR 9.0.R11 Software Release Notes

4.6 Release 9.0.R6

4.6.1 Multi-chassis Firewall (BETA)

Multi-chassis firewall synchronizes firewall and NAT states between two 7705 SAR chassis. Both
chassis can have traffic traversing them, but they create a single firewall/NAT database (on the
master chassis) that will be synchronized and shared between the two chassis. If one firewall in
multi-chassis firewall fails, all the known UDP/TCP sessions and states are present in the second
chassis. The connection can therefore continue transmitting traffic on a 5-tuple session without re-
establishing the state of the session. As an example, if there is a TCP connection on the first
firewall that has gone through the three states of TCP, that information is synchronized to the
second firewall. If there is a failure on the first firewall where the session originally was established
and the traffic gets rerouted to the second firewall in the pair, the second firewall can forward the
traffic on the same TCP connection without any interruption because it knows the state of the
connection. Multi-chassis firewall uses the multi-chassis protocol to synchronize these states. Nokia
recommends that a dedicated port be used for the multi-chassis link for security and resiliency.
All firewall functionality in the GRT and VPRN is supported in multi-chassis mode except for strict
TCP. As well, in order for NAT to work in multi-chassis firewall and to have the same NAT state
between the two firewalls, a loopback interface should be used.
IPSec uplinks in VPRN are not currently supported by multi-chassis firewall.

4.6.2 Cflowd on Layer 3 Ingress

Cflowd is widely used to gain insight into the types of applications or flow types serviced via a node.
Cflowd is supported on Layer 3 (IP) interfaces, including network interfaces and IES and VPRN
service interfaces. Ingress IP packets on these interfaces can be sampled and flow information
exported to a Cflowd collector. Version 9 and Version 10 (IPFIX) flow formats are supported.

4.6.3 1588v6

Previously, only IPv4 was supported for 1588/PTP. Applicable PTP profiles are now supported with
IPv6.

20 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4.7 Release 9.0.R5

4.7.1 EVPN-VPLS Multihoming

Ethernet VPN, which is supported from Release 9.0.R4, enhances existing VPLS applications in
many ways. Along with all the other optimizations introduced by EVPN, a significant number of
service providers offering E-LAN services today are requesting EVPN for their multihoming
capabilities. Unlike traditional single-active MC-LAG solutions, EVPN-VPLS supports active/active
multihoming where all the available links (capacity) can be utilized under the normal mode of
operation. Although VPLS already supports single-active multihoming, EVPN single-active
multihoming is also perceived as a superior technology due to its mass-withdrawal capabilities,
which speed up convergence in scaled environments.

4.7.2 EVPN-VPWS Multihoming

EVPN Virtual Private Wire Service (VPWS), which is supported from Release 9.0.R4, is a point-to-
point Layer 2 VPN based on RFC 8214, Virtual Private Wire Service Support in Ethernet VPN, that
allows a virtual leased line to be created between two systems. The EVPN-VPWS offering on the
7705 SAR is enhanced to support multihoming capabilities in this release, including both
active/active and single-active options.

4.7.3 T1/E1 Line Card Redundancy (LCR)

Protection switching for T1/E1 is added to the 7705 SAR and is modeled after APS for
SONET/SDH. The T1/E1 panel is used to connect the Tx/Rx signals to both a working and
protection port in different MDAs in a single 7705 SAR chassis or two 7705 SAR chassis. In
conjunction with PW redundancy, T1/E1 LCR provides protection against MDA, node, and network
path failures.

4.7.4 Wavence 19 Software Support and Y.1731 BN in MWA Mode

The microwave awareness (MWA) capabilities have been updated in this release of the 7705 SAR.
The embedded MPR-e software bundle now includes the new Wavence Release 19 (see
Supported MPR-e Radios for details). The HLC Plus is a new microwave radio added to the
supported list. As well, the Y.1731 bandwidth notification (BN) feature support has been extended
from non-MWA ports to also include MWA ports.

4.7.5 VLLs/VPLS over GRE over IPSec Public

For IPSec with public service VPRN, it is now possible to use GRT leaking techniques to transport
a VLL (with GRE spoke SDPs) over the IPSec tunnel that has a public VPRN service.

Edition: 01 3HE147640011TQZZA 21
New Features 7705 SAR 9.0.R11 Software Release Notes

4.7.6 Multi-chassis Firewall (BETA)

Multi-chassis firewall synchronizes firewall states between two 7705 SAR chassis. Both chassis can
have traffic traversing them, but they create a single firewall database that will be synchronized and
shared between the two chassis. If one firewall in multi-chassis firewall fails, all the known
UDP/TCP sessions and states are present in the second chassis. The connection can therefore
continue transmitting traffic on a 5-tuple session without re-establishing the state of the session. As
an example, if there is a TCP connection on the first firewall that has gone through the three states
of TCP, that information is synchronized to the second firewall. If there is a failure on the first
firewall where the session originally was established and the traffic gets rerouted to the second
firewall in the pair, the second firewall can forward the traffic on the same TCP connection without
any interruption because it knows the state of the connection.
All firewall functionality is supported in multi-chassis mode except for strict TCP. As well, in order
for NAT to work in multi-chassis firewall and to have the same NAT state between the two firewalls,
a loopback interface should be used.

4.7.7 Cflowd on Layer 3 Ingress (BETA)

Cflowd is widely used to gain insight into the types of applications or flow types serviced via a node.
Cflowd is supported on Layer 3 (IP) interfaces, including network interfaces and IES and VPRN
service interfaces. Ingress IP packets on these interfaces can be sampled and flow information
exported to a Cflowd collector. Version 9 and Version 10 (IPFIX) flow formats are supported.

4.8 Release 9.0.R4

4.8.1 EVPN-VPLS (Note: the multihoming component of this feature is ALPHA quality in
9.0.R4)

Ethernet VPN is defined in RFC 7432 as a Layer 2 VPN technology that can fill the gaps existing in
VPLS for E-LAN services. Along with all the other optimizations introduced by EVPN, a significant
number of service providers offering E-LAN services today are requesting EVPN for their
multihoming capabilities. Unlike traditional single-active MC-LAG solutions, EVPN-VPLS supports
active/active multihoming where all the available links (capacity) can be utilized under the normal
mode of operation. Although VPLS already supports single-active multihoming, EVPN single-active
multihoming is also perceived as a superior technology due to its mass-withdrawal capabilities,
which speed up convergence in scaled environments.
In Release 9.0.R4, the 7705 SAR supports route type 2, MAC/IP advertisement and route type 3,
inclusive multicast (without point-to-multipoint) Ethernet tag route for multicast, broadcast, and
unknown unicast traffic options.

22 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4.8.2 EVPN-VPWS

Release 9.0.R4 delivers support for EVPN Virtual Private Wire Service (VPWS), which is a point-to-
point Layer 2 VPN based on RFC 8214, Virtual Private Wire Service Support in Ethernet VPN, that
allows a virtual leased line to be created between two systems. EVPN-VPWS – which is configured
under Epipe service – connects a single SAP to a single BGP signaled spoke SDP/pseudowire,
where the latter can use any available MPLS/SR LSP tunneling protocol. Together with EVPN-
VPLS and IP-VPN (VPRN), EVPN-VPWS can be used for BGP-based signaling of all services for a
unified network-wide operation.

4.8.3 G.8032

The 7705 SAR supports IP/MPLS-based ring topologies with functionality such as fast reaction
times against failures and fast recovery capabilities. Deeper into the network, closer to the end
user, enabling IP/MPLS-based protection in ring topologies may not be feasible or even possible in
some cases. Spanning Tree-based ring topologies are known to reconverge relatively slowly. ITU-T
G.8032 Ethernet Ring Protection Switching (ERPS) offers an Ethernet layer protection that uses
Y.1731 CFM extensions for fast fault detection and loop avoidance. In Release 9.0.R4, the 7705
SAR supports G.8032 ERPS under VPLS service to facilitate migration of ERPS rings to IP/MPLS-
based transport networks.

4.8.4 Ethernet Connectivity Fault Management (ETH-CFM) under VPLS

IEEE 802.1ag Fault Management and ITU-T Y.1731 Fault Management and Performance
Management tools were previously available on the 7705 SAR but have now been extended to
VPLS services. VPLS SAP support is added for Up MEPs and Down MEPs as well as VPLS mesh
SDP and spoke SDP support for Down MEPs.

4.8.5 Bypass Resignal Timer

Bypass resignal timer is an optimization for RSVP-TE bypass tunnels where bypass tunnel options
are re-evaluated based on configurable timer values. With bypass resignal timer, nodes periodically
re-evaluate bypass LSP constraints and ensure that the most optimal path is in place when FRR
activates. Topology changes due to link failures, additions, and so on, that impact the selection
criteria are re-evaluated as per configured timer values. Upon expiry of the configured timer, the
node triggers a CSPF calculation based on the constraints associated with the primary LSP. If a
new LSP with a better cost is available as a result of the computation, it is signaled and is promoted
to be used if FRR bypass protection activates.

Edition: 01 3HE147640011TQZZA 23
New Features 7705 SAR 9.0.R11 Software Release Notes

4.8.6 LDP FRR over SR (including SR-LDP Stitching)

In ring environments where an LFA is needed for LDP FRR, previously only RSVP-TE was
available to allow setup of a remote LFA. In Release 9.0.R4, the 7705 SAR now supports LDP-to-
SR stitching. This is only supported for IPv4 FECs. An SR mapping server is also supported for
IPv4 prefixes in the reverse direction. LDP-to-SR stitching can be used for LDP FRR. Unlike RSVP-
TE that acts as a tunnel-in-tunnel FRR, SR acts as a one-to-one stitching to LDP for LDP FRR. SR
can be used as a remote LFA and TI-LFA backup for LDP IPv4 FECs. This feature currently only
works with IS-IS IPv4.

4.8.7 Multiple (Load-Balancing) LSPs under a Single SDP

The 7705 SAR supports one-to-one mapping between LSPs and SDPs, which requires explicit
mapping of a service to an SDP and, as a result, to an LSP. With multiple LSPs under a single
SDP, binding a service to an SDP results in automatic load distribution of traffic/services among the
LSPs. LSP additions or deletions due to capacity or topology changes result in automatic rehashing
of traffic/services onto the new number of LSPs. A 7705 SAR with multiple LSPs under a single
SDP enables transparent load balancing of traffic/services and eases the burden of load balancing
across multiple LSPs.

4.8.8 8-Port C37.94 Teleprotection Card

The 8-port C37.94 Teleprotection card provides eight SFP-based single-mode or multimode optical
interfaces to connect to electrical teleprotection relays, providing higher density than the current
8-port Voice & Teleprotection card. The card uses SFPs with LC connectors and requires adapter
cables to connect to standard multimode relays.

4.8.9 G.8275.2 P-OPS (BETA)

Partial On-Path Support (P-OPS) for PTP as per ITU-T G.8275.2 has been added in this release.
This unicast, IP-encapsulated PTP profile is designed for cases where full on-path support is not
possible and is within the network limits as per G.8271.2. Partial Timing Support (PTS) is supported
on all 7705 SAR platforms, and Assisted Partial Timing Support (APTS) is only available on the
7705 SAR-8 and 7705 SAR-18.

4.8.10 1511 “137” Signaling Mode Support

The 1511 “137” signaling mode allows interoperability between the legacy Alcatel 1511 AN TDM
multiplexer and the 7705 SAR for FXO and FXS interfaces.

24 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4.8.11 T1/E1 Line Card Redundancy (LCR) (BETA)

Protection switching for T1/E1 is added to the 7705 SAR and is modeled after APS for
SONET/SDH. The T1/E1 panel is used to connect the Tx/Rx signals to both a working and
protection port in different MDAs in a single 7705 SAR chassis or two 7705 SAR chassis. In
conjunction with PW redundancy, T1/E1 LCR provides protection against MDA, node, and network
path failures.

4.8.12 Higher Scale TSoP SFP Support for OC12/STM4 and OC3/STM1

Transparent SONET/SDH over Packet (TSoP) SFPs provide the ability to transport clear channel
SONET/SDH TDM services across a packet network. This is done transparently with no need to
terminate the SONET/SDH frame. Support of these TSoP SFPs was added to the 7705 SAR-8 in a
previous release.
In Release 9.0.R4, the maximum number of TSoP SFPs allowed in a SAR-8 has been increased,
and support has been extended to the SAR-18. The maximum number of TSoP SFPs in a single
SAR-8 or SAR-18 system is 16. The supported adapter cards are the 8-port Gigabit Ethernet
Adapter card (all versions), 6-port Ethernet 10Gbps Adapter card, and 10-port 1GigE/1-port 10GigE
X-Adapter card (v1 and v2). The maximum number of TSoP SFPs is two TSoP SFPs per supported
adapter card. For a SAR-8 with a maximum ambient temperature of 131°F (55°C), the maximum
number of TSoP SFPs increases to eight TSoP SFPs per supported adapter card.

4.8.13 1588v6 (BETA)

Previously, only IPv4 was supported for 1588/PTP. Applicable PTP profiles are now supported with
IPv6.

Edition: 01 3HE147640011TQZZA 25
New Features 7705 SAR 9.0.R11 Software Release Notes

4.9 Release 9.0.R3

4.9.1 DS3 PPP Network Links Over SONET/SDH

On the 2-port OC3/STM1 Channelized Adapter card, DS3 clear channels in an OC3 or STM1 port
can now be configured for PPP as the network uplink. This provides additional flexibility for network
connectivity over SONET/SDH. Previously, DS3 clear channels in this adapter card only supported
TDM service on access.

4.9.2 G.8275.2 P-OPS (BETA)

Partial On-Path Support (P-OPS) for PTP as per ITU-T G.8275.2 has been added in this release.
This unicast, IP-encapsulated PTP profile is designed for cases where full on-path support is not
possible and is within the network limits as per G.8271.2. Partial Timing Support (PTS) is supported
on all 7705 SAR platforms, and Assisted Partial Timing Support (APTS) is only available on the
7705 SAR-8 and 7705 SAR-18.

4.9.3 N x DS0 Loopbacks

Line loopbacks and internal loopbacks are now supported for N x DS0/64 kb/s channel groups on
the 16-port T1/E1 ASAP Adapter card v2 and the 32-port T1/E1 ASAP Adapter card in the 7705
SAR-8 and SAR-18. The number of channels in the selected channel group can be 1 to 24 for T1
and 1 to 31 for E1. Line loopbacks send the received data on the Rx port back out its corresponding
Tx port. Internal loopbacks send the received TDM PW packets back into the network from where
the packets originated. This capability is useful at the service provisioning stage as well as for
problem isolation. (D.305449)

4.9.4 SR TI-LFA for IS-IS

Topology-Independent LFA (TI-LFA) improves the protection coverage of a network topology by

computing and automatically instantiating a repair tunnel to a Q node that is not in the shortest path
from the computing node. The repair tunnel uses the shortest path to the P node and a source-
routed path from the P node to the Q node. In addition, the TI-LFA algorithm selects the backup
path that matches the post-convergence path. This helps with capacity planning in the network
because traffic will always flow on the same path when transitioning to the FRR next hop and then
onto the new primary next hop.

4.9.5 Layer 3 Hashing

This feature extends the entropy label and entropy indication label to VPRN, IES, EVPN, and Ipipes
and Cpipes for RSVP-TE.

26 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4.10 Release 9.0.R2

4.10.1 CAS TDM PW Interoperability Between T1 SF and ESF

TDM PWs with CAS signaling are supported with T1 framing for both superframe (SF) and
extended superframe (ESF) formats. Previously, the T1 framing format had to match at both ends
of the PW in order for the PW to come into service. Support has now been added to allow
interoperability of SF at one end and ESF at the other end of the TDM PW. A simple translation is
employed between the ABCD CAS bits from the ESF port and the AB CAS bits from the SF port.
(D.305451)

4.10.2 N x DS0 Loopbacks (BETA)

Line loopbacks and internal loopbacks are now supported for N x DS0/64 kb/s channel groups on
the 16-port T1/E1 ASAP Adapter card v2 and the 32-port T1/E1 ASAP Adapter card in the 7705
SAR-8 and SAR-18. The number of channels in the selected channel group can be 1 to 24 for T1
and 1 to 31 for E1.

Line loopbacks send the received data on the Rx port back out its corresponding Tx port. Internal
loopbacks send the received TDM PW packets back into the network from where the packets
originated. This capability is useful at the service provisioning stage as well as for problem isolation.
(D.305449)

4.11 Release 9.0.R1

4.11.1 12-port Serial Data Interface Card, Version 3 (SDIv3)

The SDIv3 card is an enhancement of the current SDIv2 card, providing all SDIv2 functionality plus:

• complete RS-530/RS-422 interface (16 Mb/s max rate)

• true DTE/DCE operation
• serial DCR to transport serial timing across IP/MPLS
• SAToP serial for enhanced speeds and extended signaling support
• enhanced physical line monitoring capability
• terminal timing support

4.11.2 SAToP Serial

The SAToP serial feature provides a new Cpipe vc-type encapsulation on the SDIv3 card to
transport serial DCR and support additional line speeds and the transport of more serial signaling
leads (subrate and super-rate) on an end-to-end basis.

Edition: 01 3HE147640011TQZZA 27
New Features 7705 SAR 9.0.R11 Software Release Notes

4.11.3 DCR Serial

The DCR serial feature allows the transport of serial user timing on RS-530 and RS-232 serial links
across the 7705 SAR network.

4.11.4 G.8275.2 P-OPS (ALPHA)

Partial On-Path Support (P-OPS) for PTP as per ITU-T G.8275.2 has been added in this release.
This unicast, IP-encapsulated PTP profile is designed for cases where full on-path support is not
possible and is within the network limits as per G.8271.2. Partial Timing Support (PTS) is supported
on all 7705 SAR platforms, and Assisted Partial Timing Support (APTS) is only available on the
7705 SAR-8 and 7705 SAR-18.

4.11.5 SR with OSPF-TE and IS-IS-TE

The 7705 SAR now supports Segment Routing (SR) extensions for IGP. SR removes the need for
MPLS protocols to build an MPLS transport. This simplifies the network with a single IGP underlay
to build the transform and a BGP overlay to signal services. SR advertises segments via IGP
extensions. A segment can be any object or resource within the network, such as a node or a link
(adjacency), and it is presented by a label. SR can create traffic-engineered tunnels by stacking up
these labels between two PEs. The 7705 SAR supports SR extensions for OSPF and IS-IS
(Including IS-IS IPv6). In addition, LFA or TI-LFA (IS-IS only) can be used for resiliency.

4.11.6 SR TI-LFA for IS-IS (ALPHA)

Topology-Independent LFA (TI-LFA) improves the protection coverage of a network topology by

computing and automatically instantiating a repair tunnel to a Q node that is not in the shortest path
from the computing node. The repair tunnel uses the shortest path to the P node and a source-
routed path from the P node to the Q node. In addition, the TI-LFA algorithm selects the backup
path that matches the post-convergence path. This helps with capacity planning in the network
because traffic will always flow on the same path when transitioning to the FRR next hop and then
onto the new primary next hop.

4.11.7 PCEP-P for SR-TE

Path Computation Element Protocol (PCEP-P) is the protocol running between the PCE and the
PCC. It is used for programming SR paths on the PCC. The 7705 SAR supports:

• PCC-initiated and PCC-controlled tunnels

• PCC-initiated and PCE-computed tunnels
• PCC-initiated and PCE-controlled tunnels

28 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

4.11.8 LDPv6

LDPv6 extends the existing LDPv4 functionality to provide support over an IPv6 network. LDPv6
can be used to signal IPv6 or IPv4 FECs throughout the network to build an MPLS transport over
an IPv6 network. This transport can be used for Layer 2 and PW services. The 7705 SAR does not
support IPv6 BGP next hops; therefore, Layer 3 services cannot use IPv6 MPLS transport.

4.11.9 Ignore ATT Bit under IS-IS

IS-IS can now be configured to ignore the attached bit on received level 1 LSPs, thereby disabling
the installation of default routes.

4.11.10 ADC Support over Redundant Network Paths

Asymmetrical Delay Control (ADC) over redundant network paths is an enhancement of the existing
ADC feature to control link asymmetry for utility current-differential relay teleprotection applications.
It is now possible to operate ADC over redundant network paths and maintain symmetry after a
network path switches to the standby path.

4.11.11 Mixed-mode SDP

Mixed-mode SDP provides the ability to fall back to an alternative tunnel for reachability. As an
example, under normal mode of operation, traffic-engineered tunnels with RSVP-TE can be used
as the primary tunnel for transport. If RSVP-TE LSPs become unavailable, LDP-based transport
can be used instead.

4.11.12 EHS

The Event Handling System (EHS) allows operator-defined behavior to be configured on the router.
The operator can program a script to be dynamically executed when a specific log event is
generated.

4.11.13 AIGP Metric for BGP

To ensure best path selection, the accumulated IGP (AIGP) option is now supported, which takes
into account the cost of local links. The AIGP metric is an optional attribute that can be attached to
selected routes (using route policies) to influence the BGP decision process to prefer BGP paths
with a lower end-to-end IGP cost, even when the compared paths span more than one AS or IGP
instance.

Edition: 01 3HE147640011TQZZA 29
New Features 7705 SAR 9.0.R11 Software Release Notes

4.11.14 VPRN Public IPSec

Currently, only IES is supported on public IP network services. This feature extends the public
service to support VPRN on the 7705 SAR. A public VPRN will provide separation between arriving
IPSec tunnels. Each tunnel can belong to a different customer, represented and separated via the
public VRF. In addition, the public VRF can provide IPSec over MPLS functionality when the public
VPRN is configured as an auto-bind MPLS uplink. GRE uplinks will be available in future software
releases.

4.11.15 MAC ACL-based Mirroring (VPLS)

This feature allows for the configuration of the MAC filter policy so that only desired MAC addresses
(source or destination) from a VPLS or routed VPLS service will be mirrored. The destination of the
mirror service can be on a local SAP or a different remote router.

4.11.16 Layer 3 Hashing (ALPHA)

This feature extends the entropy label and entropy indication label to VPRN, IES, EVPN, and Ipipes
and Cpipes for RSVP-TE.

4.11.17 BGP RIB Separation

BGP RIB is now separated so that unlabeled IPv4, labeled-unicast IPv4, and unlabeled IPv6 types
(AFs) are hosted in different tables. Separation ensures that routes of different types can fail or be
selected independently. Capabilities that were mostly available on a per-peer basis can now be
enabled on a per-type basis without causing contention among different address families.

4.11.18 PIMI-MSDP in VPRN

MSDP interconnects multiple IPv4 PIM Sparse-Mode (PIM-SM) domains, which enables PIM-SM to
have Rendezvous Point (RP) redundancy and inter-domain multicasting. Currently, MSDP is
supported in the GRT. This feature provides the capability to enable MSDP in MVPN.

4.11.19 Egress SAP Drop Statistics

This feature adds support for an egress SAP drop counter. Queue drops and errored packet drops
are combined in a single drop count, consistent with the already existing ingress SAP drop counter.

4.11.20 Increased Number of OSPF Routers in a Single Area

The number of OSPF routers in a single area is now tested to a new limit, allowing more flat
architectures. Very large networks with full mesh or close to full mesh may make the introduction of
areas impractical. An increased number of routers in a single area allows flat topologies.

30 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes New Features

Note that large numbers of OSPF routers in a single area can increase the number of LSA updates
and associated Dijkstra runs for SPF, which might adversely impact the stability of the network.
Great care must be taken when increasing the number of routers in a single area. Contact Nokia for
exact scaling limits.

4.11.21 Increased Number of IS-IS Routers in a Single Level

The number of IS-IS routers in a single level is now tested to a new limit, allowing more flat
architectures. Very large networks with full mesh or close to full mesh may make the introduction of
levels impractical. An increased number of routers in a single level allows flat topologies.
Note that large numbers of IS-IS routers in a single level can increase the number of LSA updates
and associated Dijkstra runs for SPF, which might adversely impact the stability of the network.
Great care must be taken when increasing the number of routers in a single level. Contact Nokia for
exact scaling limits.

Edition: 01 3HE147640011TQZZA 31
Unsupported Features on the 7705 SAR 7705 SAR 9.0.R11 Software Release Notes

5 Unsupported Features on the 7705 SAR

5.1 7705 SAR-H and SAR-Wx GPS Realization Variants

Newer realization variants introduced for the 7705 SAR-H GPS Receiver Module (3HE07955AA)
and GPS-enabled 7705 SAR-Wx variants (3HE07615AA, 3HE07617AA, 3HE07619AA) added
GLONASS support capabilities to the hardware. Starting in Release 8.0.R4, older realization
variants are no longer supported, and an upgrade to newer variants is required.
Table 10 highlights the realization codes that are no longer supported.
Table 10 Realization Codes no Longer Supported

Platform or Card Part Number (Including Realization Variant

that is no Longer Supported)
7705 SAR-Wx chassis (3HE07615AA - Ethernet and GPS) 3HE07615AAAA, 3HE07615AAAB, 3HE07615AAAC

7705 SAR-Wx chassis (3HE07617AA - Ethernet, PoE+, and GPS) 3HE07617AAAA, 3HE07617AAAB, 3HE07617AAAC

7705 SAR-Wx chassis (3HE07619AA - Ethernet, xDSL, and GPS) 3HE07619AAAA, 3HE07619AAAB, 3HE07619AAAC
7705 SAR-H GPS Receiver Module 3HE07955AAAA, 3HE07955AAAB

Realization codes can be viewed in the CLI using the show chassis command.

32 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Enhancements

6 Enhancements
The following sections describe enhancements in Release 9.0.

Note: Enhancements that were added in earlier releases, but which were not
documented until the current release, are marked as [NEW] and are
documented in the section for the applicable release.

6.1 Release 9.0.R11

6.1.1 System

A software enhancement has been implemented to increase system robustness on second-

generation adapter cards and platforms. (D.349255)

6.2 Release 9.0.R10

6.2.1 Routing

IS-IS has been enhanced to keep preferring local RSVP tunnels over local IGP routes when the
7705 SAR goes into an overload state. (D.329916)

6.3 Release 9.0.R9

6.3.1 Adapter Card Diagnostics

A new diagnostic test has been added to the following non-Ethernet adapter cards to detect
hardware failures related to synchronization on the adapter card:

• Integrated Services card

• 6-port E&M Adapter card
If the diagnostic test fails, a log event will be generated with the following text: “Class MDA Module:
background diags fault, reason: Sync Clock Monitoring”. If this log event appears for an adapter
card, contact a Nokia support representative for further investigation. (D.337586)

Edition: 01 3HE147640011TQZZA 33
Enhancements 7705 SAR 9.0.R11 Software Release Notes

6.4 Release 9.0.R8

There are no enhancements added in this release.

6.5 Release 9.0.R7

6.5.1 LAG

The CLI restriction that a SAP can only be created on a static LAG group if standby-signaling is
set to power-off has been removed to align with 7750 SR CLI behavior. (D.313949)

6.5.2 RFC 6232 Purge Originator Identification TLV for IS-IS

This enhancement enables the use of the Purge Originator Identification (POI) TLV for an IS-IS
instance. The POI is added to purges and contains the system ID of the router that generated the
purge, which simplifies troubleshooting and determining what caused the purge. (D.165786)

6.5.3 Enable LDP Implicit Null Support

Implicit null might be required for interoperation purposes where the penultimate hop advertises
implicit null or to conserve the label stack. The ability to send the implicit null label in the label-
mapping message is now supported. (D.318623)

6.5.4 Enable static-route-entry with Indirect Tunnel Next Hop

Indirect static routes require a second lookup and this feature allows an IGP shortcut tunnel to be
used for resolving a next hop for the configured route. Indirect routes enhance reachability by
allowing dynamic selection of the next-hop route. (D.318652)

6.5.5 Enable static-route-entry with Indirect Next Hop for VPRN

Indirect static routes require a second lookup and this feature allows resolution of a non-direct route
with a second lookup in the IP-VPN FIB. Indirect routes enhance reachability by allowing dynamic
selection of the next-hop route. (D.318654)

6.5.6 Allow Configurable MAC for Network Interfaces

A MAC address on a per-network interface basis can now be changed. This is in addition to a per-
port MAC address change. When network interfaces are connected to same next hop over parallel
links, different MAC addresses might be required for better load balancing. (D.318659)

34 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Enhancements

6.5.7 RSVP: Enable Implicit Null Support

Implicit null might be required for interoperation purposes where the penultimate hop advertises
implicit null or to conserve the label stack. The ability to send the implicit null label in the Resv
message is now supported. (D.318729)

6.5.8 Enable OSPF/OSPFv3 Multi-area Adjacency Support

This enhancement allows support of multi-area adjacency under both OSPFv2 and OSPFv3 (IPv6).
(D.321748)

6.5.9 GPS Receiver Power Cycle on clear mda Command

The clear mda all CLI command will now initiate a full power cycle of the GPS receiver device on
the 7705 SAR-Ax, SAR-8, and SAR-18. This functionality was previously available on the SAR-H
and SAR-Wx only. (D.294929)

6.5.10 System

The default login banner has been changed to prevent signaling any information related to the
product or software release prior to a successful authentication. This enhancement is most visible
when using SSH/Telnet to access the CLI to manage a 7705 SAR router. The option to display a
login banner can be controlled using the config>system>login-control>login-banner command.
(D.314675)

6.5.11 IPv6 Support on IES with Layer 3 Spoke SDP

IPv6 is now supported on an IES service with a Layer 3 spoke SDP. (D.317749)

6.5.12 Resolution of RFC 3107 BGP Label Unicast Route over LDPoRSVP Tunnels

Release 9.0.R7 extends the resolution of an RFC 3107 BGP label unicast route over LDP going
over RSVP tunnels (as an RSVP shortcut) when the BGP LSP is used to forward packets of IPv4
prefixes, Layer 2 services, or Layer 3 services. The feature is supported at the LER and LSR
(ABR/ASBR).

6.6 Release 9.0.R6

There are no enhancements added in this release.

Edition: 01 3HE147640011TQZZA 35
Enhancements 7705 SAR 9.0.R11 Software Release Notes

6.7 Release 9.0.R5

6.7.1 10-port 1GigE / 1-port 10GigE X-Adapter Card Robustness

A software enhancement has been implemented to increase system robustness on 10-port 1GigE /
1-port 10GigE X-Adapter cards in 10-port 1GigE mode. (D.316697)

6.7.2 DHCP Client

The minimum lease time that a 7705 SAR DHCP client will accept has decreased from
5 minutes to 1 minute. In cases where a lease timer of less than 5 minutes is used, the maximum
number of DHCP clients that are supported will decrease. Contact your Nokia representative for
details. This parameter is not user-configurable. (D.317366)

6.7.3 MPLS

The vRtrMplsLspActivePathChanged MPLS log event is now also raised whenever the active path
of an LSP changes due to a network event such as a failure or degradation of the currently active
path or the expiration of the revert timer. Prior to this enhancement, this log event was only raised
when the active path of an LSP changed following a manual successful MBB operation using the
tools perform router mpls switch-path or tools perform router mpls force-switch-path
commands. (D.308984)

6.8 Release 9.0.R4

6.8.1 IS-IS

Users can now configure a router ID value in each instance of IS-IS, including the default instance.
By default, the global value of router-id (config>router>router-id) is used when an IS-IS instance
is created. The IS-IS system ID for the instance continues to be derived from the router ID.
(D.150880)

6.9 Release 9.0.R3

There are no enhancements added in this release.

6.10 Release 9.0.R2

There are no enhancements added in this release.

36 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Enhancements

6.11 Release 9.0.R1

There are numerous enhancements in Release 9.0.R1 of the 7705 SAR. These enhancements are
summarized below.

6.11.1 System

• The show port detail CLI display has been enhanced to display “Transceiver Status”.
(D.171306)
• The monitor port x/y/z rate command output has been enhanced to include a bits-per-
second output for Ethernet ports.
• A show router icmp command has been added to show ICMP statistics. This
information is also available via SNMP in the TIMETRA-VRTR-MIB MIB object
vRtrIcmpTable. (D.220123)
• The configure redundancy cert-sync configuration is now configured by default.
(D.180324)
• 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.
• Users executing unauthorized CLI commands will now generate an event that will be
captured in the system log. (D.171199)
• Previously, a password that did not meet the complexity rules for an admin user was
allowed, and a warning was displayed to notify the user. Now, the password for an
admin user must follow the password complexity requirements in order for the password
to be accepted. When performing an upgrade or configuration upload from older
releases, the admin user can use a password that does not meet the password
complexity. Only password changes after the upgrade are affected. (D.215312)
• The environment alias command has been enhanced to allow embedded quotes (using
the “\” escape character). For example, the following can be applied to the output of the
show port detail command:
A:mynode# environment alias my-summary "| match expression \"----
|Description|Interface|Admin State|Oper State|Transceiver Type|Optical
Compliance|Link Length\" | match invert-match expression \"Ethernet Interface|OTU
Interface\" | match invert-match expression \"----\" post-lines 1". (D.274444)
• SSH 2K prime number keys are implemented for non-FIPS mode so that both 2K and
1K keys are permitted in non-FIPS mode instead of just 1K keys. (D.231467)

Edition: 01 3HE147640011TQZZA 37
Enhancements 7705 SAR 9.0.R11 Software Release Notes

• The show port detail command has been enhanced to generate a fully detailed output
for all ports in the system. This is useful for gathering full reports or generating
customized summaries by using show port detail as an input into the | match post-
filtering command to display only certain fields for all ports.
• The show chassis command has been enhanced to display a summary by default and
supports the optional detail keyword to return the fully detailed output for physical
chassis information.
• The CLI command range operator has been expanded. In addition to a simple range or
list of values (for example, [1..5], [2,4,6,8]), the user can now submit a list containing
ranges as elements (for example, configure port 1/1/[1..10,15,16,21..30] no
shutdown). Also, CLI ranges now support hexadecimal values (for example,
[0x0f..0x13], [0x4,0x8,0xc]). (D.274445)
• A specific-throttle-rate option can now be configured per log event. When this is
configured for a log event, it overrides the globally configured throttle rate. (D.280977)

6.11.2 OAM

• The 32-bit vendor-specific information field included in the Local Information TLV sent
with each Information OAMPDU will now include a non-zero hexadecimal value that
represents the platform and chassis type. There is no configuration for this option.
• LLDP now includes the ability to select the port-id-subtype that will be carried in the port-
id field. The default remains ifIndex. The ifIndex value is required by some versions of
the Nokia NSP 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
the ability of NSP to build the Layer 2 topology map using LLDP.
• The LLDP System Management Address now includes support for both IPv4 (Address
Subtype 1) and IPv6 (Address Subtype 2).
• The show system lldp neighbor display output has been updated to allow for a wider
Local Port column. The expansion of the “Lcl Port” column requires realignment of three
other columns. If the returned values exceed the width of the column, the last character
is "*", indicating that the value was wider than the column allowed and was therefore
truncated. (D.222990)

38 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Enhancements

6.11.3 IPSec

• The following CA chain-related enhancements are introduced: (D.183273)

o The no shutdown of a ca-profile will trigger a recomputation of the compute-
chain in related certificate profiles. The system will also generate a new log to
indicate that a new compute chain has been generated; the log includes the ca-
profile names on the new chain. Another log will be generated if the send-chain
in a cert-profile entry is not in the compute-chain due to this ca-profile change.
o If the hash calculation of a certificate within the CA has changed, a log will be
generated.
o When performing a no shutdown of a cert-profile, the system now allows the
CAs in the send-chain not related to the compute-chain. The system will also
generate a log.
o The system now allows changes to the configuration of the send-chain without a
shutdown of cert-profile.
• Certificate authentication and Diffie-Hellman computation for the IKE protocol have been
optimized; as a result, the setup performance of IPSec tunnels is increased.
• The following enhancement has been added to the IPSec debug capability: (D.284817)
o The system allows debug to be enabled for multiple IPSec tunnels at the same
time; up to 16 debug ipsec commands are allowed concurrently.
• Two new log events have been introduced for the IPSec static tunnel to indicate tunnel
operational state changes. These events are currently recorded in tmnxStateChange
and will continue to be included; however, using tmnxStateChange to track the tunnel
operational state is being deprecated and will be removed in a future release.
(D.190978)

6.11.4 LDP

• A new global LDP configuration option, legacy-ipv4-lsr-interop, has been introduced 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:
o Nokia 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 Nokia
proprietary Hello Adjacency Status TLV (0x3E06) because the Interface Info TLV
is not sent. (D.214697, D.218464)
o The RFC 7552 standard dual-stack capability TLV (0x701) and the Nokia
proprietary Adjacency capability TLV (0x3E07) (D.217080)

Edition: 01 3HE147640011TQZZA 39
Enhancements 7705 SAR 9.0.R11 Software Release Notes

6.11.5 MPLS

• Enhanced auto-binding to tunnels: a new auto-binding framework has been

introduced for selecting tunnels in the Tunnel-Table Manager (TTM) in the following
resolution contexts:
o resolution of a static route prefix using tunnels to an indirect next hop
o resolution of a BGP prefix using tunnels to a BGP next hop (BGP shortcut)
o resolution of RFC 3107 BGP label route prefix using tunnels to a BGP next hop
o 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 tunnels
is removed.
If the resolution option 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 the TTM for a specific IGP
instance.
If one or more explicit tunnel types are specified using the resolution-filter option, only
these tunnel types will be selected again following the TTM preference.
The user must set the resolution configuration to filter in order 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.
When a router is upgraded to Release 9.0, the commands are automatically converted
to the new format.
• The show router mpls status command has been enhanced to indicate the next free
LSP ID. (D.217129)

6.11.6 QoS

• The show router sgt-qos command is enhanced to show the default and configured
DSCP and 802.1p QoS values for self-generated traffic. (D.221311, D.273384)

6.11.7 IPv6

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

IP interface. Previously, removing a manually configured LLA required the operator to
completely remove the IPv6 configuration on the interface using the no ipv6 command.

40 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Enhancements

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. (D.175057)

6.11.8 IS-IS

• 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. In earlier
releases, while IS-IS used only the direct tunnels to reach the endpoint node and
prefixes owned by the endpoint node, it used 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 the node, and IP next hops up to the router ecmp
value. (D.211050)
• The show router isis command has been enhanced with an all option to show all
configured IS-IS instances. The command output has also been extended to show the
instance ID. (D.182037)
• Support has been added for partial LFA SPF. In earlier releases, IS-IS performed a
partial main SPF and followed it with full LFA SPFs. In the current release, only prefixes
that were added or changed will have their LFA next hops updated. (D.153351)
• The output of the show router isis command has been enhanced to show the instance
name in the headers. (D.207574)
• The IS-IS LSP (lsp-wait) and SPF (spf-wait) timers are enhanced to support
millisecond granularity, which allows finer configuration control over IS-IS timers. Timers
also have a separate timers hierarchy in the IS-IS configuration for clarity. (D.193242,
D.275155)

6.11.9 OSPF

• A tools dump router router ospf area-range command has been added that shows the
dynamic parameters and the aggregated routes of an OSPF area-range. (D.212766)
• The metric on OSPF external type 2 routes can be set to 0 using a routing policy.
Previous releases set the metric to 1 if a metric of 0 was configured. (D.181293)
• The ospf timers spf-wait command is enhanced with spf-initial-wait and spf-second-
wait parameters for consistency with other commands. (D.216051)

Edition: 01 3HE147640011TQZZA 41
Enhancements 7705 SAR 9.0.R11 Software Release Notes

• The OSPF routing feature set is enhanced so that the lsa-generate timer now governs
LSA generation for self-generated LSAs with MaxAge. In earlier releases, 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.
(D.228017)

6.11.10 Routing

• It is now possible to configure a prefix-list that is empty (containing no member prefixes)

in router policies, which will evaluate as if “no match” was found when referenced in a
policy. When the last member prefix is removed from a prefix-list, the prefix-list will no
longer be automatically removed. If required, the empty prefix-list must be explicitly
removed by the operator. (D.170915)
• The syntax for the static route command has been changed from a single CLI command
with multiple parameters to a hierarchical structure where parameters and options for a
specific static route have become new, individual leaf commands of the associated static
route. This new CLI structure is also used for the configuration of static routes in the
Base routing context as well as when configuring static routes in Layer 3 VPN services.
Existing static routes will be automatically converted to the new format when upgrading.
All new static routes or modifications to existing static routes must be made using the
new hierarchical CLI structure. The new static-route CLI structure is documented in the
7705 SAR Router Configuration Guide and the 7705 SAR Services Guide.
In addition, new static routes will be created in a shutdown state. After all of the
parameters for a static route have been added, the no shutdown command must be
issued to activate the new static route.
• A new, extensive output option for the show router route-table and show router fib
commands has been added. The non-extensive output in previous releases did 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.
• A description can now be added to the configuration of an aggregate route. (D.175397)
• A description can now be added to the configuration of a static route. (D.104825)
• Summary values have been added to the vRtrFibStatEntry table that correspond to
values from the CLI command show router fib summary. (D.213063)
• The CLI output has been enhanced to display route tags configured in routing policies in
hexadecimal instead of decimal format. Route tags are now displayed in decimal format
in policy-statement from and action accept statements, and in the RIP and OSPF
show command output. Decimal format for route tags is now used consistently in all CLI
inputs and outputs. (D.193831)

42 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Enhancements

• The outputs of the show router interface ipv6 detail and show service id interface
ipv6 detail commands now display ICMPv6 values. (D.210216)

6.11.11 BGP

• New flexibility has been added to BGP prefix limits. In previous releases, only one prefix
limit was configurable per BGP neighbor, and this limit applied only to received IPv4 and
IPv6 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.)
(D.275011)
• Minor changes have been introduced for various BGP-related show commands to
improve visibility and troubleshooting. The show router bgp routes command now
uses specific flag 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.
• BGP import policy re-evaluation has been optimized when the only change to the import
policy is a limited number of additions and/or deletions to prefix-lists referenced by the
import policy.
• The policy-based export of the active/installed route to a peer that has BGP advertise-
inactive enabled in its configuration is now allowed. (D.167175)
• The show router bgp routes command has been enhanced to allow filtering of IP-VPN
routes based on the combination of community and prefix/route-distinguisher.
(D.172384)
• The show router bgp next-hop command has been enhanced to support three
additional address families: vpn-ipv4, vpn-ipv6, and evpn. (D.242285)
• The BGP-4 MIB has been updated from version draft-ietf-idr-bgp4-mib-05 to support
RFC 4273. (D.214024)
• The show router bgp routes command has been enhanced to support more consistent
parameter ordering. Now, to apply a family filter to the route output of the command, the
family name must be specified before all other filtering parameters except for the prefix,
which, if present, must be placed before the family name in the command.
• BGP next-hop information has been added to the display of BGP routes in the routing
table and FIB. (D.141814)
• The show router bgp routes command has been enhanced to support IPv4 or IPv6
host route lookups, to enable the operator to easily see the matching BGP routes using
one CLI command. (D.227206)

Edition: 01 3HE147640011TQZZA 43
Enhancements 7705 SAR 9.0.R11 Software Release Notes

• A BGP peer that is administratively shut down is now shown as “Idle (Shutdown)”
instead of “Idle” in the show router bgp CLI output to better indicate the peer’s
administrative state. (D.222527)
• VPRN BGP out-of-memory handling is now aligned with the main BGP instance
mechanisms. In earlier 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. (D.227877,
D.230151)

44 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Changed or Deprecated Commands

7 Changed or Deprecated Commands

7.1 Release 9.0.R11

There are no changed or deprecated commands in this release.

7.2 Release 9.0.R10

There are no changed or deprecated commands in this release.

7.3 Release 9.0.R9

There are no changed or deprecated commands in this release.

7.4 Release 9.0.R8

There are no changed or deprecated commands in this release.

7.5 Release 9.0.R7

There are no changed or deprecated commands in this release.

7.6 Release 9.0.R6

There are no changed or deprecated commands in this release.

7.7 Release 9.0.R5

There are no changed or deprecated commands in this release.

7.8 Release 9.0.R4

There are no changed or deprecated commands in this release.

7.9 Release 9.0.R3

There are no changed or deprecated commands in this release.

7.10 Release 9.0.R2

There are no changed or deprecated commands in this release.

Edition: 01 3HE147640011TQZZA 45
Changed or Deprecated Commands 7705 SAR 9.0.R11 Software Release Notes

7.11 Release 9.0.R1

There have been numerous updates to the 7705 SAR CLI in Release 9.0.R1 relative to 7705 SAR
Release 8.0.R11.
A line-by-line summary of the differences between the CLI trees of Release 8.0.R11 and Release
9.0.R1 is included in the embedded spreadsheet below. Note that a small number of CLI items are
available in Release 9.0.R1 for features that are not actually supported; these will be removed in a
subsequent release.

46 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Usage Notes

8 Usage Notes
The following information supplements or clarifies information in the manuals for Release 9.0.

Note: Usage notes that have been added in this release are marked as [NEW].

8.1 1588 on IES

• If PTP packets are transferred to the PTP clock over an IES service and there is also
VPRN service on that same port, the VPRN service must not use an identical IP
address to the source-interface IP address of the PTP clock. (P.616751)

8.2 1588/ACR

• These features meet both traffic and synchronization masks. Their performance
depends upon many factors that must be taken into consideration before deploying.
Network loading, traffic profile, hop counts, and deployment environment are a few
of the factors affecting ACR/1588 performance. Customers must carefully engineer
their networks to take advantage of these features.

8.3 1588/NTP

• NTP should not be configured as the source of system time on a node if that node is
going to be used as a 1588 grand master. While this configuration is allowed, it is not
a supported configuration. PTP or GNSS should be the source of system time if a
node is to be used as a 1588 grand master.

8.4 6-port SAR-M Ethernet Module

• Half-duplex mode is not supported on the 6-port SAR-M Ethernet module. When
using this module, it is recommended that Ethernet ports be configured for auto-
negotiation; otherwise, Ethernet links may not come up. This can occur because if
auto-negotiation is disabled or fails, ports on most devices default to half-duplex
mode, but ports on the 6-port SAR-M Ethernet module cannot (as this mode is not
supported).

Edition: 01 3HE147640011TQZZA 47
Usage Notes 7705 SAR 9.0.R11 Software Release Notes

8.5 APS

• It is recommended 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 protection circuits.
• For SONET/SDH ports belonging to APS groups that have a very large difference in
the transmission delay between the working and protection circuits, it is
recommended that the hold-down timers be increased from their default values.

8.6 ATM

• The 7705 SAR product family allows configuration of user traffic on reserved ATM
Forum UNI specification VCI values (VCIs from 1 to 31 inclusive). It is recommended
that no user traffic be configured on those VCIs on any VP as other equipment may
treat that traffic per the defined usage reserved to a given VCI value. (D.53205)

8.7 ATM Bonding Support on the DCM and XDSL Modules

• It is recommended that ATM bonding over ADSL2 and/or ADSL2+ be restricted to

demonstration or trial evaluations only. As an alternative to this option, PTM bonding
over ADSL2, ADSL2+ and VDSL2 is fully hardened and supported in conjunction
with the Nokia 73xx ISAM and provides superior throughput capabilities compared to
ATM bonding.

8.8 CLI

• The special characters | and > can no longer be used inside environment alias
strings. Additionally, the special characters / and \ cannot be used as the first
character inside an alias string.
• The pipe/match command in the CLI does not support auto-completion. The user
must ensure that the pipe/match command and any attributes are spelled correctly.
• The attribute of the pipe/match command must follow the match command and must
come before the pattern/expression.
• Below are some examples of the pipe/match command (details can be found in the
CLI Usage section of the Basic System Configuration Guide):
o Example: Capture all lines that include "echo" and redirect the output to a file
on the compact flash:
admin display-config | match "echo" > cf3:\echo_list.txt
o Example: Display all lines that do not include "echo":
admin display-config | match invert-match "echo"

48 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Usage Notes

o Example: Display the first match of "vprn" in the configuration file:

admin display-config | match max-count 1 "vprn"

8.9 Differential Clock Recovery (DCR)

• When a port on the 16-port T1/E1 ASAP Adapter card v2 or 32-port T1/E1 ASAP
Adapter card is configured for differential clock, the port timing will be associated
with the service clock of the Cpipe of channel group 1. In the case of a framed T1
port, there is a restriction on the Cpipe’s payload size of channel group 1:
o for DCR timestamp frequency 77.76 MHz: payload size = 2 x N x (number of
timeslots), where N = 1, 2, 3, …
o for DCR timestamp frequency 19.44 MHz: payload size = 8 x N x (number of
timeslots), where N = 1, 2, 3, …
This restriction does not apply to framed E1 or unframed T1/E1 ports. (P.650950)

8.10 EFM OAM Support on all DSL Ports

• EFM OAM can currently be enabled on any DSL port. The current EFM OAM
implementation on Nokia 73xx ISAM DSL Line Termination cards (LTs) is not
compatible with the 7705 SAR implementation. This incompatibility will not allow for
this feature to become operational across DSL uplinks and, if enabled, will cause
DSL uplinks to go into a down state.

8.11 IP Filters and Non-IP Packets

• IP filters with a default-action of discard will not discard non-IP packets such as ARP
and IS-IS. (D.40976)

8.12 IS-IS

• The protocol sends advertisements with the IS-IS Traffic Engineering (TE) Router ID
TLV when traffic engineering is disabled. (D.17683)
• 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 example, if the hello-
authentication type is set to password for an interface, it is not activated until a key
is added at the interface level. (D.34256)

Edition: 01 3HE147640011TQZZA 49
Usage Notes 7705 SAR 9.0.R11 Software Release Notes

8.13 Jumbo Frames

• The 7705 SAR can support jumbo frames on dot1q Ethernet ports up to 9728 bytes
plus the 4-byte FCS (for a total of 9732 bytes), whereas the MPR-e radio supports
frames up to 9728 including the FCS. Care must be taken when configuring
port/service MTUs on microwave links to ensure that large packets are not dropped.

8.14 LDP

• The user should not configure the loopback attribute on a network interface after it
has been assigned to an ILDP interface local-lsr-id. (P.666765, D.170280)
• On LDP interfaces and targeted-session keepalive commands, it is recommended
that the factor setting be set to a value greater than 1 or it may lead to unexpected
drops in LDP peerings. (D.67153)

8.15 LDP Interface Parameters

• Hello and keepalive parameter modifications do not take effect until a shutdown/no
shutdown command is performed on the LDP session.

8.16 Management

• It is highly recommended that the management ports be on protected and controlled

network segments not directly accessible from the Internet to prevent unwanted
Denial-of-Service attacks. (P.52314)
• When creating a new log file on a Compact Flash disk card, the system will check
the amount of free disk space. The amount must be greater than or equal to the
lesser of 5.2 MB or 10% of the Compact Flash disk capacity; otherwise, the log file
will not be created.

8.17 MC-APS

• MC-APS is non-revertive by default. To make it revertive, a revert-time must be

configured. It is recommended that a revert-time of 1 minute or more be used. It is
also generally recommended that ICBs (inter-chassis backup) be provisioned for
better switch times and better protection with the MC-APS feature.
• If revert-time 0 with an ICB is provisioned, when a fault on the working line
recovers, the MC-APS will immediately revert, but there will be a traffic throughput
impact of 10 seconds or more. If an ICB is not used, or if revert-time is 1 minute or
greater when ICBs are used, there is no traffic impact on line recovery. (P.641963)

50 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Usage Notes

8.18 MLPPP

• When an 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 to 255 are separated into two ranges:
o 0 to 127 is used for the keepalive function
o 128 to 255 is used for differential delay detection
Keepalive statistics only count echo packets with IDs from 0 to 127.
• In order to interoperate with other vendors’ MLPPP implementations, the MLPPP
sublayer will accept packets with or without leading zeros in the protocol field even
though the 7705 SAR does not advertise the protocol field compression (PFC) option
during LCP negotiation. (D.25996, D.29923)

8.19 MPLS/RSVP

• The current bypass binding selection logic is the following:

o For non-Strict environment:
Manual CSPF disjoint bypass
Manual CSPF !disjoint bypass
Dynamic CSPF disjoint bypass
Dynamic CSPF !disjoint bypass
o For Strict environment:
Manual CSPF disjoint bypass
Dynamic CSPF disjoint bypass
The above binding order has two collateral/detrimental effects when the non-Strict
option is selected:
o In the presence of a disjoint Dynamic Bypass, a non-disjoint Manual Bypass
may be selected instead.
o Non-CSPF Manual Bypass will never be selected. (D.66005)
• The enabling or disabling of Diff-Serv on the system requires that the RSVP and
MPLS protocols be shut down. When first created, 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.

Edition: 01 3HE147640011TQZZA 51
Usage Notes 7705 SAR 9.0.R11 Software Release Notes

• The following IP address prefixes are not allowed by the unicast routing protocols
and the Route Table Manager and will not be populated within the forwarding table:
o 0.0.0.0/8 or longer
o 127.0.0.0/8 or longer
o 224.0.0.0/4 or longer (used for multicast only)
o 240.0.0.0/4 or longer
Any other prefixes that need to be filtered can be filtered explicitly using route
policies.
• On LDP interfaces and targeted-session keepalive commands, it is recommended
that the factor setting be set to a value greater than 1 or it may lead to unexpected
drops in LDP peerings. (D.67153)

8.20 NAT

• The allow-directed-broadcasts configuration on the interface is not supported

when NAT is enabled on the router. (D.173293-MI)

8.21 NTP

• In order to receive and process NTP broadcast packets on the Base router, both
ntp-broadcast and allow-directed-broadcast must be enabled on the router
interface that is receiving the NTP broadcast packets. (P.634337)

8.22 Routing

• Reducing the interval/timeout timers much below the default values is not
recommended for OSPF, IS-IS, BGP, LDP, or RSVP to ensure stability under
transitional events such as a CSM switchover. (D.56792, D.58891)

8.23 System

• To minimize the chances of service disruption, only the standby CSM should be
removed from a redundant 7705 SAR system. If the active CSM must be removed,
then a High-Availability switchover should be performed first by using admin
redundancy force-switchover now, making it the standby CSM before removing it.
• When nodes are run in FIPS-140-2 mode, only FIPS-140-2 compliant algorithms are
enabled and allowed. Nokia 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.

52 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Usage Notes

Before enabling a preconfigured node to run in FIPS-140-2 mode, ensure that all
configurations in the configuration file do not include any 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
7705 SAR Basic System Configuration Guide for details.

8.24 VPRN

• Modifying local VPRN policies might have unexpected side effects if there exist one
or more VPRN import polices that refer to a community list name that does not exist.
One side effect is that a route refresh message is sent to all BGP-VPN peers when
this is not required. To prevent this, route policies must never refer to non-existent
objects (prefix lists, community lists, and so on). (D.60879)

Edition: 01 3HE147640011TQZZA 53
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

9 Software Upgrade Procedures

The following sections contain information for upgrading to the 9.0.R11 software version. In
particular, there are sections that describe the following:

• Software Bundles
Information on the software bundles available in this release
• Software Upgrade Notes
Information on upgrading the router from previous versions of 7705 SAR OS software,
including rules for upgrading firmware and any special notes for upgrading from specific
earlier versions
• ISSU Upgrade Procedure
Procedure for performing an ISSU to Release 9.0.R11
• Standard Software Upgrade Procedure
Procedure for performing a standard, service-affecting upgrade including updating of
firmware images

Note: CSMv1 and SAR-F are not supported in this release (support was
dropped in Release 7.0). This release will not boot on these platforms.

Note: A new support.tim file was introduced in Release 7.0. The support.tim file
contains files that are required for the following platforms: SAR-8, SAR-
18, SAR-M, SAR-H and SAR-X. Despite its name (support.tim), this file is
not related to Nokia support services or the admin tech-support
functionality. See Software Bundles for additional information.

Note: Upgrade notes that have been added in this release are marked as
[NEW].

54 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

9.1 Software Bundles

There are three software bundles available:

• 7705-TiMOS.9.0.R11.MWA.zip – 7705 SAR Release 9.0 OS software with the

support.tim file and the MPR-e radio software. Before a microwave link can be
configured in single NE mode, the 7705 SAR Release 9.0 OS software bundle, which
includes the MPR-e radio software, must be downloaded to the 7705 SAR-8 or 7705
SAR-18.
• 7705-TiMOS.9.0.R11.zip – 7705 SAR Release 9.0 OS software, including a support.tim
file. This software bundle must be used for the following 7705 SAR platforms: SAR-8,
SAR-18, SAR-M, SAR-H, and SAR-X. These platforms require the support.tim file;
otherwise, equipment will fail to boot.
• 7705-TiMOS.9.0.R11.small.zip – 7705 SAR Release 9.0 OS software, without a
support.tim file. This software bundle should be used for the following 7705 SAR
platforms: SAR-A, SAR-Ax, SAR-W, SAR-Wx, SAR-Hc, and 7210 SAS-Sx SONET/SDH
Satellite. These platforms do not require the support.tim file, and using the “small”
software bundle will save space on the 7705 SAR compact flash device.

Note: Beginning with Release 7.0.R2, the 7705 SAR software bundles no
longer contain MIB files. These files were previously included for
documentation purposes only. Customers wishing access to MIB files
should contact their Nokia support representative. Also, customers
wishing to delete MIB files from existing compact flash devices to save
space can do so without any impact to product functionality.

Table 11 summarizes the upgrade capability from previous releases to this release. Customers
wishing to upgrade from Release 6.2 or lower to Release 9.0 must first upgrade to any 7.0 or 8.0
release using the Software Upgrade Procedure as described in the Release Notes for that release.
The upgrade to Release 9.0 can then proceed.
Table 11 7705 SAR Upgrade Capability

Release # Supported Upgrade Software Upgrade Notes for Standard Shipped

Upgrade From Upgrade to this Release Firmware
Release 7.0.R1 Standard Notes 1, 2, 3, 7, 8, 9, 10, 11, 13, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R2 Standard Notes 1, 3, 7, 8, 9, 10, 11, 13, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R3 Standard Notes 1, 5, 7 ,8, 9, 10, 11, 13, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R4 Standard Notes 1, 4, 5, 6, 8, 10, 11, 12, 13, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R5 Standard Notes 1, 8, 10, 11, 12, 13, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R6 Standard Notes 1, 8, 10, 11, 12, 13, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R7 Standard Notes 1, 8, 10, 11, 12, 13, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R8 Standard Notes 1, 13, 15, 17, 21, 22, 24 0x2e(v46)

Edition: 01 3HE147640011TQZZA 55
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

Release # Supported Upgrade Software Upgrade Notes for Standard Shipped

Upgrade From Upgrade to this Release Firmware
Release 7.0.R9 Standard Notes 1, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R10 Standard Notes 1, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R11 Standard Notes 1, 15, 17, 21, 22, 24 0x2e(v46)

Release 7.0.R12 Standard Notes 1, 17, 21, 22, 24 0x2e(v46)

Release 8.0.R1 Standard Notes 1, 11, 13, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R2 Standard Notes 1, 13, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R3 Standard Notes 1, 13, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R4 Standard Notes 1, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R5 Standard Notes 1, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R6 Standard Notes 1, 14, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R7 Standard Notes 1, 14, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R8 Standard Notes 1, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R9 Standard Notes 1, 15, 17, 21, 22, 24 0x2f(v47)

Release 8.0.R10 Standard Notes 1, 15, 17, 21, 22, 24 0x30(v48)

Release 8.0.R11 Standard Notes 1, 17, 21, 22, 24 0x30(v48)

Release 8.0.R12 Standard Notes 1, 21, 22, 24 0x30(v48)

Release 8.0.R13 Standard Notes 1, 22, 24 0x30(v48)

Release 8.0.R14 Standard Notes 1, 22, 24 0x30(v48)

Release 8.0.R15 Standard Notes 1, 22, 24 0x30(v48)

Release 9.0.R1 Standard Notes 16, 17, 21, 22, 24 0x35(v53)

Release 9.0.R2 Standard Notes 17, 21, 22, 24 0x35(v53)

Release 9.0.R3 Standard Notes 22, 24 0x35(v53)

Release 9.0.R4 Standard Notes 19, 22, 24 0x35(v53)

Release 9.0.R5 Standard Notes 20, 22, 24 0x35(v53)

Release 9.0.R6 Standard Notes 20, 22, 24 0x35(v53)

Release 9.0.R7 Standard Notes 22, 24 0x35(v53)

Release 9.0.R8 Standard, ISSU Notes 22, 23, 24 0x35(v53)

Release 9.0.R9 Standard, ISSU Notes 22, 24 0x35(v53)

Release 9.0.R10 Standard, ISSU Note 24 0x35(v53)

56 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

9.2 Software Upgrade Notes

This section lists notes for upgrading from prior versions of the 7705 SAR to this release.
Table 12 Software Upgrade Notes

Note Description
Note 1: The 7705 SAR OS Release 9.0.R11 requires a firmware update to version 0x35.
Firmware update Follow the steps in the Standard Software Upgrade Procedure or ISSU Upgrade
Procedure to update the firmware images.

Note 2: An admin save detail command results in a line with “no v6-routed-override-filter”
Perform admin save prior to the upgrade in the configuration file. This command is not supported and will fail to load in this
release. To avoid this issue, perform an admin save prior to the upgrade.

Note 3: In previous releases, adding a second unnumbered interface configured as

One unnumbered interface allowed with system when the dhcp option was configured was not blocked. Prior to the
system when DHCP option configured upgrade, ensure that there is only one unnumbered interface configured as
system with the dhcp option. (D.215412)

Note 4: An admin save detail command results in a “prefix-delegate” option in DHCPv6

Perform admin save prior to the upgrade configurations under both IES and VPRN. This is an unsupported option, and the
config file will fail to load with this release. To avoid this issue, perform an admin
save prior to the upgrade. (D.223270)

Note 5: Prior to this release, the following configuration items allowed erroneously large
Maximum allowed values for IGMP snooping values.
now enforced • config>service>vpls>mesh-sdp>igmp-snooping# max-num-groups
• config>service>vpls>mesh-sdp>igmp-snooping# max-num-grp-
sources
• config>service>vpls>mesh-sdp>igmp-snooping# max-num-sources

The maximum allowed value for all three items should be 512 on all 7705 SAR
platforms except for the 7705 SAR-X. For the SAR-X, the maximum value should
be 1024. Before upgrading, these items must all be configured to a value within the
supported range, or the no version of the configuration must be issued. (D.221023)

Note 6: In previous releases, multiple system time PTP references could be configured to
Only one PTP reference allowed at each have the same priority. Prior to the upgrade, ensure that there is only one system
priority time PTP reference at a given priority. (D.221317)

Note 7: In previous releases, the access LAG port-threshold range allowed was 0 to 7.
Access LAG port threshold now enforces Prior to the upgrade, ensure that the port-threshold value is either 0 or 1.
range of 0 to 1

Note 8: In previous releases, for the VPRN in-band feature, configuring the protocol to
VPRN in-band management: vpn-leak in protocol vpn-leak and from protocol vpn-leak under the router policy statement
router policy statement entry to protocol/from entry was allowed. Prior to the upgrade, ensure that these are not configured.
protocol is now blocked (D236103)

Edition: 01 3HE147640011TQZZA 57
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

Note Description
Note 9: In previous releases, configure system security pki was allowed on systems
Configure security PKI not available on SAR-M that did not support IPSec. Prior to the upgrade, ensure that PKI is not configured
and SAR-A on systems that do not support IPSec. (D.233967)

Note 10: In previous releases, vendor-specific-option was available under the

The vendor-specific-option command has config>router>if>dhcp>option menu. It was not supported; therefore, this menu
been removed from the config>router>if> has been removed. Prior to the upgrade, ensure that nothing is configured under
dhcp>option menu config>router>if>dhcp>option>vendor-specific-option. (D.239054)

Note 11: In previous releases, entering a negative value for rising-threshold and falling-
The cflash-cap-alarm thresholds under the threshold for the cflash-cap-warn or cflash-cap-alarm commands under the
config>system>thresholds context may config>system>thresholds context resulted in large out-of-limit values. Prior to
have out-of-range values the upgrade, ensure that the rising-threshold and falling-threshold values are
less than 2147483647 under config>system>thresholds. (D.241967)

Note 12: In previous releases, adding an access port to a LAG group was allowed on the
Adding a port to LAG group blocked when in SAR-A, SAR-Ax, SAR-H, SAR-Hc, SAR-W, and SAR-Wx. It should not have been
default access mode allowed. Prior to the upgrade, ensure that this configuration is removed.
(D.240354)

Note 13: In previous releases, with a PTP profile of G.8275.1, configuring freq-source ptp
Configuring freq-source ptp (non-default) is (non-default) was permitted. This configuration is now blocked. Prior to the
blocked for PTP profile of G.8275.1 upgrade, ensure that freq-source ptp (non-default) is removed. (D.253591)

Note 14: In previous releases, configuring TCP MSS (v4/v6) on system interfaces and
Configuring TCP MSS (v4/v6) on system loopback interfaces was permitted. This configuration is now blocked. Prior to the
interfaces or loopback interfaces is blocked upgrade, ensure that this configuration is removed. (D.268290)

Note 15: In previous releases, configuring use-node-time under config>system>ptp>

The use-node-time option has been removed clock>clock-type>transparent-e2e was permitted. This configuration is now
from the config>system>ptp>clock>clock- blocked. Prior to the upgrade, ensure that this configuration is removed.
type>transparent-e2e menu (D.218952)

Note 16: In the previous release, configuring evpn-tunnel under config>service>vprn was
The evpn-tunnel option has been removed permitted. This configuration is now blocked. Prior to the upgrade, ensure that this
from the config>service>vprn menu configuration is removed. (D.303080)

Note 17: In previous releases, configuring encap-type atm/ipcp/frame-relay on a DS3

Configuring encap-type atm/ipcp/frame-relay channel in access mode on a 2-port OC3/STM1 Channelized Adapter card was
for a DS3 channel in access mode on the permitted. These configurations are now blocked. Prior to the upgrade, ensure that
2-port OC3/STM1 Channelized Adapter card is these configurations are removed. (D.308244)
now blocked

Note 18: Beginning in 9.0.R4, there is a bug such that an interface cannot be used as a
An interface cannot be used as a PTP source PTP source interface if that interface gets its IP address via DHCP. If this
interface if that interface gets its IP address via configuration is in use in a previous release, an upgrade to this release will fail.
DHCP (D.315552)

58 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

Note Description
Note 19: The config>service>epipe>site option was erroneously available in 9.0.R4. It
The site option has been removed from the has been removed. Prior to upgrading, ensure that this configuration is removed.
config>service>epipe menu (D.316918)

Note 20: In previous releases, security and zone configurations were not blocked on the
Shut down mc-firewall prior to the upgrade slave router. These configurations are now blocked but may cause an upgrade
issue. Prior to upgrading, ensure that mc-firewall is shut down. (D.323275)

Note 21: Step 6 of the Standard Software Upgrade Procedure cannot be performed for
MPR-e software cannot be pre-downloaded to upgrades from these releases. Step 6 is an optional step that allows MPR-e
attached radios software to be pre-downloaded to attached microwave radios that are in Single-NE
mode, as a way to minimize service outage time during an upgrade. When
upgrading from releases with this note, Step 6 must be skipped. (D.310745)

Note 22: In previous releases, VRRP could be configured under

Configuring VRRP under config>router>interface. This configuration is now blocked. Prior to the upgrade,
config>router>interface is blocked ensure that this configuration is removed. (D.349430)

Note 23: SSH access to a 7705 SAR will be lost after an ISSU upgrade from 9.0.R8
SSH access to 7705 SAR lost after ISSU because the expected/default SSH client-mac-list and server-mac-list will be
upgrade missing from the configuration of the newly active CSM. As a workaround, either
use the Standard Software Upgrade Procedure or ensure that Telnet is enabled
before starting an ISSU upgrade and after the upgrade manually configure the
required entries in client-mac-list and server-mac-list. (D.353551)

Note 24: In previous releases, more than one management interface could be configured
Configuring more than one management under config>router>”management”. The configuration of more than one
interface under interface is now blocked. Prior to the upgrade, ensure that no more than one
config>router>”management” is blocked management interface is configured. (D.248238) [NEW]

Edition: 01 3HE147640011TQZZA 59
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

9.3 ISSU Upgrade Procedure

This section describes the ISSU Upgrade Procedure, which can be used:

• on routers with redundant CSMs

• on routers running software that supports upgrades to this release; refer to Table 11
If any of the above criteria do not apply, the Standard Software Upgrade Procedure must be
performed.

Note: Although the software upgrade can be performed using a remote terminal
session, Nokia recommends that the software upgrade procedure be
performed at the system CONSOLE device where there is physical
access to the 7705 SAR. Remote connectivity may not be possible if a
problem occurs during the software upgrade process. Performing the
upgrade at the CONSOLE with physical access to the 7705 SAR allows
the user to troubleshoot any upgrade problems with the help of the Nokia
Technical Assistance Center.
Nokia recommends the following status check before performing an
upgrade: ensure that the standby CSM is synchronized with the active
CSM. The CLI command show redundancy synchronization should
show “standby ready” as the standby status.
Nokia recommends the removal of unnecessary files from the compact
flashes. When the standby CSM synchronizes its boot-env to the active
CSM, it keeps a temporary copy of its own image file on its compact flash
before the new synchronized image file is successfully copied.
If there is not enough space on the compact flash for this temporary
copy, synchronization with the active CSM will fail.

1. Back up Existing Images and Configuration Files

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 of
an unknown format to earlier software versions.
Nokia recommends making backup copies of the BOOT Loader
(boot.ldr), software image and configuration files, in case customers must
revert to the previous version of the software.

60 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

2. Copy 7705 SAR OS Images to cf3:

The 7705 SAR OS image files must be copied to the cf3: device on the 7705 SAR. It
is good practice to place all the image files for a given release in an appropriately
named subdirectory off the root; for example, “cf3:\7705-TiMOS- R9.0.R11”. Copying
the boot.ldr and other files in a given release to a separate subdirectory ensures that
all files for the release are available in case it is necessary to downgrade the software
version. Note that as of Release 7.0, the support.tim file must also be copied for all
platforms that require it (see Software Bundles).
If the 7705 SAR has attached MPR-e radios in Single NE mode, ensure that the 7705
SAR Release 9.0 Software bundle includes MPR-e software, that is,
7705-TiMOS.9.0.R11.MWA.zip.

3. Update the boot.ldr on cf3:

The BOOT Loader file is named boot.ldr. This file must be copied to the root directory
of the cf3: device.
Validate and copy the boot.ldr file to the root directory using the command:
admin update boot-loader cf3:\7705-TiMOS-R9.0.R11\boot.ldr

Warning: Do not power off, reset the system, insert cards or remove cards when
the boot.ldr update is being performed, or the cards/system may become
inoperable and therefore need to be returned to Nokia for repair.

Note: If it becomes necessary to downgrade from R9.0, the older software will
work with the R9.0 boot.ldr file.

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 file 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.

5. Synchronize the Boot Environments

Once the Boot Options File has been modified, the active and standby CSM boot
environments must be synchronized.
Use the admin redundancy synchronize boot-env command to synchronize the
boot environments between the active and standby CSMs.

Edition: 01 3HE147640011TQZZA 61
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

6. Reboot the Standby CSM

Use the admin reboot upgrade standby now command to reboot the inactive CSM.
In the output example below, the active CSM is in Slot A and the standby CSM is in
Slot B.
Before the start of ISSU, the card will look like the following:
A:router1# show card state

===============================================================================
Card State
===============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-------------------------------------------------------------------------------
1 iom-sar up up 6
1/1 a16-chds1v2 up up 16
1/2 a8-1gb-sfp up up 8
1/3 a8-ethv2 up up 8
1/4 a4-oc3 up up 4
1/6 a2-choc3 up up 2
A csmv2-10g up up Active
B csmv2-10g up up Standby
===============================================================================

A:router1# admin reboot upgrade standby now

A:router1# show card state

===============================================================================
Card State
===============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
-------------------------------------------------------------------------------
1 iom-sar up up 6
1/1 a16-chds1v2 up up 16
1/2 a8-1gb-sfp up up 8
1/3 a8-ethv2 up up 8
1/4 a4-oc3 up up 4
1/6 a2-choc3 up up 2
A csmv2-10g up up Active
B csmv2-10g up down Standby
(not equipped)
===============================================================================

7. Wait for the Standby CSM to Synchronize

After the ISSU has been initiated, the card status of the standby CSM (in Slot B in this
example) will show as “synching”.
A:router1# show card state
===============================================================================
Card State
===============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
---------------------------------------------------------------------------------
1 iom-sar up up 6
1/1 a16-chds1v2 up up 16
1/2 a8-1gb-sfp up up 8
1/3 a8-ethv2 up up 8
1/4 a4-oc3 up up 4
1/6 a2-choc3 up up 2
A csmv2-10g up up Active
B csmv2-10g up synching Standby

===============================================================================

62 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

When the standby CSM has completely synchronized, the standby CSM will indicate
a state of “ISSU”.
A:router1# show card state
===============================================================================
Card State
===============================================================================
Slot/ Provisioned Type Admin Operational Num Num Comments
Id Equipped Type (if different) State State Ports MDA
---------------------------------------------------------------------------------
1 iom-sar up up 6
1/1 a16-chds1v2 up up 16
1/2 a8-1gb-sfp up up 8
1/3 a8-ethv2 up up 8
1/4 a4-oc3 up up 4
1/6 a2-choc3 up up 2
A csmv2-10g up up Active
B csmv2-10g up ISSU Standby

===============================================================================

8. Reboot the Active CSM

After the standby CSM has synchronized and indicates a card status of “ISSU”, the
active CSM (in Slot A in this example) must be rebooted. Use the admin reboot
upgrade active now command to reboot the active CSM.

9. If Necessary, Re-establish a Console Session

If the ISSU is performed from the serial port CONSOLE on the CSM, the console
session must be re-established on the newly active CSM.

10. Wait for the Standby CSM to Synchronize

Before continuing with the ISSU procedure, the standby CSM must resynchronize by
transitioning from the “down”, “synchronizing” and finally to the “up” states. Use the
command show mda to monitor the status of the adapter cards.
Note that the adapter cards now have an “ISSU” status, indicating that the active
CSM is running the new image.
B:router1# show mda
===============================================================================
MDA Summary
===============================================================================
Slot Mda Provisioned Type Admin Operational
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 1 a16-chds1v2 up ISSU
2 a8-1gb-sfp up ISSU
3 a8-ethv2 up ISSU
4 a4-oc3 up ISSU
6 a2-choc3 up ISSU
===============================================================================

Edition: 01 3HE147640011TQZZA 63
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

11. Reset the Adapter Cards to Load the New Image

The adapter 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 adapter cards after 2 hours. The
“Comments” field in the show card output displays the time until the
system resets the adapter cards in the ISSU state.

B:router1# show card

===============================================================================
Card State
===============================================================================
Slot Provisioned Type Admin Operational Comments
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 iom-sar up up
1/1 a16-chds1v2 up ISSU 119 min
1/2 a8-1gb-sfp up ISSU 119 min
1/3 a8-ethv2 up ISSU 119 min
1/4 a4-oc3 up ISSU 119 min
1/6 a2-choc3 up ISSU 119 min
A csmv2-10g up down Standby
(not equipped)
B csmv2-10g up up Active
===============================================================================

Use the clear mda 1/n command to reset an adapter card.

The output example below shows the operational state transitions for a single adapter
card.
B:router1# clear mda 1/1
B:router1# show mda

===============================================================================
MDA Summary
===============================================================================
Slot Mda Provisioned Type Admin Operational
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 1 a16-chds1v2 up provisioned
(not equipped)
2 a8-1gb-sfp up ISSU
3 a8-ethv2 up ISSU
4 a4-oc3 up ISSU
6 a2-choc3 up ISSU
===============================================================================

When the adapter card is in the “up” state, it will have the new image so it will no
longer have an “ISSU” operating state.
B:router1# show mda

===============================================================================
MDA Summary
===============================================================================
Slot Mda Provisioned Type Admin Operational
Equipped Type (if different) State State
-------------------------------------------------------------------------------
1 1 a16-chds1v2 up up
2 a8-1gb-sfp up ISSU
3 a8-ethv2 up ISSU

64 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

4 a4-oc3 up ISSU
6 a2-choc3 up ISSU
===============================================================================

When all of the adapter cards have been rebooted, the ISSU is complete.

9.4 Standard Software Upgrade Procedure

This section describes the Standard Software Upgrade Procedure, which is service-affecting and
must be used.
Each software release includes a BOOT Loader (boot.ldr). The BOOT Loader performs two
functions:
1. Initiates the loading of the 7705 SAR OS image based on the Boot Options File
(bof.cfg) settings
2. Reprograms the Boot ROM and firmware code on the CSM cards to the version
appropriate for the 7705 SAR OS image
This section describes the process for upgrading the software, the Boot ROM, and the firmware
images with the BOOT Loader.
The software checks the firmware images on the CSM and reports any mismatch. If the loaded
version is earlier than the expected version, the firmware may need to be upgraded. A console or
log message will indicate if a firmware upgrade is required. If the firmware version loaded is later
than the expected version, no firmware programming is required.
The following steps describe the software upgrade process using the automatic firmware upgrade
procedure.

Note: Although the software upgrade can be performed using a remote terminal
session, Nokia recommends that the software upgrade procedure be
performed at the system CONSOLE device where there is physical
access to the 7705 SAR, as remote connectivity may not be possible if
there is a problem with the software upgrade.
Performing the upgrade at the CONSOLE with physical access to the
7705 SAR allows the user to troubleshoot any upgrade problems with the
help of their regional Nokia Technical Assistance Center.
Nokia recommends the following status check before performing an
upgrade: ensure that the standby CSM is synchronized with the active
CSM. The CLI command show redundancy synchronization should
show standby ready as the standby status.
Nokia recommends the removal of unnecessary files from the compact
flashes. When the standby CSM synchronizes its boot-env to the active
CSM, it keeps a temporary copy of its own image file on its compact flash
before the new synchronized image file is successfully copied.

Edition: 01 3HE147640011TQZZA 65
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

If there is not enough space on the compact flash for this temporary copy,
synchronization with the active CSM will fail.
Before an upgrade is attempted, it is recommended that the compact
flash on the active CSM have free space equivalent to twice the size of
the both.tim and boot.ldr files combined plus 10 MB. If the standby CSM
is present, it will also need free space equivalent to twice the size of the
both.tim and boot.ldr files combined plus 10 MB.
Nokia recommends following the steps outlined below precisely. Failure
to do so could result in a failure of the upgrade process, after which a site
visit could be required in order to recover the node. If the node does not
have a customer-accessible compact flash, failure to follow the upgrade
process may require that the node be returned to Nokia for service.
Additional details are outlined in Technical Alert TA 11-0698.

1. Back up Existing Images and Configuration Files

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 of
an unknown format to earlier software versions.
Nokia recommends making backup copies of the BOOT Loader
(boot.ldr), software image and configuration files, in case customers must
revert to the previous version of the software.

2. Copy 7705 SAR OS Images to cf3:

The 7705 SAR OS image files must be copied to the cf3: device on the
7705 SAR. It is good practice to place all the image files for a given release in an
appropriately named subdirectory off the root; for example, “cf3:\7705-TiMOS-
R9.0.R11”.
Copying the boot.ldr file and other files in a given release to a separate subdirectory
ensures that all files for the release are available in case it is necessary to downgrade
the software version. The support.tim file must also be copied for all platforms that
require it (see Software Bundles).
If the 7705 SAR has attached MPR-e radios in Single NE mode, ensure that the 7705
SAR Release 9.0 Software bundle includes MPR-e software, that is,
7705-TiMOS.9.0.R11.MWA.zip.
Note: On systems without removable flash drives, copying the boot.ldr file
directly to the root directory of cf3: is not permitted. Instead, copy it into a
subdirectory. Nokia recommends for all systems that customers use the
command in the next step to update the boot.ldr file, which also verifies
that the file is valid.

66 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

3. Update the boot.ldr on cf3:

The BOOT Loader file is named boot.ldr. This file must be copied to the root directory
of the cf3: device.
Validate and copy the boot.ldr file to the root directory using the command:
admin update boot-loader cf3:\7705-TiMOS-R9.0.R11\boot.ldr

Warning: Do not power off, reset the system, insert cards or remove cards when
the boot.ldr update is being performed, or the cards/system may become
inoperable and therefore need to be returned to Nokia for repair.

Note: If it becomes necessary to downgrade from R9.0, the older software will
work with the R9.0 boot.ldr file.

4. Modify the Boot Options File to Boot 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 file 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.

5. [Redundant CSMs] Synchronize Boot Environment

On systems with redundant CSMs, copy the image files and Boot Options File to the
redundant CSM with the command:
admin redundancy synchronize boot-env

6. Download MPR-e Software to Attached Radios (7705 SAR + MPR-e Single NE

installations only)
This is an optional step that only applies to installations that have attached MPR-e
radios in Single NE mode. In such cases, the user may optionally pre-download the
MPR-e software to the attached radios before upgrading the chassis in order to
minimize the service outage time during the upgrade. This can be done by issuing the
command tools perform mw software download. Once this command is issued, the
user should wait until the software download is complete before moving on to Step 7.
The status of the software download can be monitored by executing the command
show mw radio software.

Edition: 01 3HE147640011TQZZA 67
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

7. Upgrade the Chassis

The chassis must be rebooted with the admin reboot upgrade command:
admin reboot upgrade active now

[Redundant CSMs]
On systems with redundant CSMs, upgrade the standby CSM first with
admin reboot upgrade standby now
Immediately after issuing this command, and before the inactive CSM has finished
its boot sequence, upgrade the active CSM the same way as a single CSM:
admin reboot upgrade active now
All adapter cards in the chassis will reset.
Warning: Do not power off, reset the system, insert cards or remove cards when
firmware programming is being performed, or the cards/system may
become inoperable and therefore need to be returned to Nokia for repair.

The output example below shows a 7705 SAR running 7.0.R5 software performing an
automatic firmware upgrade with the 9.0.R1 BOOT Loader and software image.
A:7705:Dut-A# admin reboot upgrade active now
***********************************
** ---> W A R N I N G <--- **
** ALL REQUIRED FIRMWARE UPGRADES**
** WILL BE DONE ON THIS CARD **
** REBOOT AND MAY TAKE SEVERAL **
** MINUTES. THE CARD MUST NOT **
** BE RESET OR POWERED DOWN **
** DURING THIS PROCESS AS THIS **
** MAY RESULT IN IT BEING **
** RENDERED INOPERABLE! **
***********************************

A:7705:Dut-A# Switching serial output to sync mode... done

Resetting...OK

Alcatel-Lucent 7705 Boot ROM. Copyright 2000-2015 Alcatel-Lucent.

All rights reserved. All use is subject to applicable license agreements.
Build: X-7.0.R5 on Wed Feb 24 10:45:54 EST 2016 by builder
Version: 0x2E
Starting CPU/Switch card
Performing Data Bus Test... Passed.
Performing Local RAM Test (1st 4MB)... Passed.
COLD boot on processor #1
CPLD revision is 0x13
?Preparing for jump to RAM...
Starting bootrom RAM code...
Bootrom version is v46 (0x2e)
Boot ROM verbose flag is set
Shelf Type: SAR8 (1), Shelf Rev: 1
Resetting cf 3
Performing Power on Diagnostics
BIST check for 6XXX processor family
Skipping PCIe port 0 BIST, in EP mode, can't tell if clocked.
Skipping PCIe port 1 BIST, reset not done. (port not configured)
CPU BIST check passed.
Validating SDRAM from 0x7fbfff80 to 0x80000000

68 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

Testing SDRAM from 0x0000000002400000 to 0x000000007fbfff80

Testing SDRAM from 0xffffffffc0000000 to 0xffffffffc2000000
Resetting cf 3
Testing Compact Flash ... OK (SMART CF)
CPLD revision is v19 (0x13)
Hardware Slot 0
sysCountRate() 800,000,000
Card type in EEPROM is 0xe7, 'rialzi_r1'
Board Serial Number is 'NS131364215'
Chassis type 254 (sar8) found in EEProm
Chassis Serial Number is 'NS115010095'
No upgrade image for BOOT present at BFE00000
No upgrade image for CPLD present at BFF80000
Searching for boot.ldr on local drives:
Resetting cf 3
Searching cf3 for boot.ldr...
*******************************************************************************
**************
Loaded 0x002e1080 bytes from cf3 to 0x02400000
Decompressing to address 0x0a000000
Decompression Succeeded
Starting code...

Total Memory: 2GB Chassis Type: 0xfe Card Type: 0xe7

TiMos-L-9.0.R1 boot/hops Nokia 7705 SAR Copyright (c) 2000-2018 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Thu Sep 20 22:53:52 EDT 2018 by builder in /rel9.0/b1/R1/panos/main

TiMOS BOOT LOADER

Acceptable bootrom version; found 0x2e, expected 0x35

Time from clock is WED SEP 26 15:05:00 2018 UTC
Switching serial output to sync mode... done

Preparing to read ROM files from system image.

Looking for cf3:/bof.cfg ... OK, reading

primary-image ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images
primary-config ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images/dut-a.cfg
address xxx.xxx.xxx.xxx/24 active
address xxx.xxx.xxx.xxx/24 standby
primary-dns xxx.xxx.xxx.xx
dns-domain labs.ca.alcatel-lucent.com
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.x
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.x
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.x
autonegotiate
duplex full
speed 100
wait 4
persist on
no fips-140-2
console-speed 115200

Primary image location: ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images

Initializing management port omii0 using IP addr xxx.xxx.xxx.xxx.
Initial DNS resolving preference is ipv6-first
Loading image ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images/both.tim
images_v1:(405024)
File version B-9.0.R1, Thu Sep 20 23:02:48 EDT 2018 by builder in
/rel9.0/b1/R1/panos/main
5 ROM images loaded from .tim file

Checking for firmware upgrades...

Embedded BOOT ROM: 53/X-9.0.R1 on Thu Sep 20 22:49:20 EDT 2018 by builder

Sl Type Serial # FPGA up? BOOT ROM up?

A iom-sar NS131364215 13 46/X-7.0.R5 on Wed Feb 24 10:45:52 E Y

*********************************

Edition: 01 3HE147640011TQZZA 69
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

** ROM PROGRAMMING IN PROGRESS **

** DO NOT RESET CHASSIS, **
** INSERT OR REMOVE CARDS **
** WHILE IN PROGRESS, OR **
** CARDS MAY BE RENDERED **
** INOPERABLE. **
*********************************

***** Programming Slot A (this slot) *****

PROGRAMMING BOOT ROM UPGRADE SPACE

Erasing 30000 bytes at address 1fe00000: 030000 OK
Programing 2d105 bytes at address 1fe00000: 02D105 OK

*********************************************
** CARD PROGRAMMING COMPLETED SUCCESSFULLY **
*********************************************

Resetting...OK

Alcatel-Lucent 7705 Boot ROM. Copyright 2000-2015 Alcatel-Lucent.

All rights reserved. All use is subject to applicable license agreements.
Build: X-7.0.R5 on Wed Feb 24 10:45:54 EST 2016 by builder
Version: 0x2E
Starting CPU/Switch card
Performing Data Bus Test... Passed.
Performing Local RAM Test (1st 4MB)... Passed.
COLD boot on processor #1
CPLD revision is 0x13
?Preparing for jump to RAM...
Starting bootrom RAM code...
Bootrom version is v46 (0x2e)
Boot ROM verbose flag is set
Shelf Type: SAR8 (1), Shelf Rev: 1
Resetting cf 3
Performing Power on Diagnostics
BIST check for 6XXX processor family
Skipping PCIe port 0 BIST, in EP mode, can't tell if clocked.
Skipping PCIe port 1 BIST, reset not done. (port not configured)
CPU BIST check passed.
Validating SDRAM from 0x7fdfff80 to 0x80000000
Testing SDRAM from 0x0000000002400000 to 0x000000007fdfff80
Testing SDRAM from 0xffffffffc0000000 to 0xffffffffc2000000
Resetting cf 3
Testing Compact Flash ... OK (SMART CF)
CPLD revision is v19 (0x13)
Hardware Slot 0
sysCountRate() 800,000,000
Card type in EEPROM is 0xe7, 'rialzi_r1'
Board Serial Number is 'NS131364215'
Chassis type 254 (sar8) found in EEProm
Chassis Serial Number is 'NS115010095'
Decompressing 0x2cff9 bytes at 0xbfe0010c into 0x80600000...
Upgrading BOOT rom to v53 / X-9.0.R1 on Thu Sep 20 22:49:20 EDT 2018 by buil
Programming 535556 bytes at address 0xbfc00000
!........!........!........!........!........!........!........!........!......
..
No upgrade image for CPLD present at BFF80000

Rebooting...�

Nokia 7705 Boot ROM. Copyright 2000-2016 Nokia.

All rights reserved. All use is subject to applicable license agreements.
Build: X-9.0.R1 on Thu Sep 20 22:49:23 EDT 2018 by builder
Version: 0x35
Starting CPU/Switch card
Performing Data Bus Test... Passed.
Performing Local RAM Test (1st 4MB)... Passed.
COLD boot on processor #1

70 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

CPLD revision is 0x13

?Preparing for jump to RAM...
Starting bootrom RAM code...
Bootrom version is v53 (0x35)
Boot ROM verbose flag is set
Shelf Type: SAR8 (1), Shelf Rev: 1
Card type in EEPROM is 0xe7, 'rialzi_r1'
Board Serial Number is 'NS131364215'
Resetting cf 3
Chassis type 254 (sar8) found in EEProm
Chassis Serial Number is 'NS115010095'
Performing Power on Diagnostics
BIST check for 6XXX processor family
Skipping PCIe port 0 BIST, in EP mode, can't tell if clocked.
Skipping PCIe port 1 BIST, reset not done. (port not configured)
CPU BIST check passed.
Validating SDRAM from 0x7fdfff80 to 0x80000000
Testing SDRAM from 0x0000000002400000 to 0x000000007fdfff80
Testing SDRAM from 0xffffffffc0000000 to 0xffffffffc2000000
Resetting cf 3
Testing Compact Flash ... OK (SMART CF)
CPLD revision is v19 (0x13)
Hardware Slot 0
sysCountRate() 800,000,000
No upgrade image for BOOT present at BFE00000
No upgrade image for CPLD present at BFF80000
Searching for boot.ldr on local drives:
Resetting cf 3
Searching cf3 for boot.ldr...
*******************************************************************************
**************
Loaded 0x002e1080 bytes from cf3 to 0x02400000
Decompressing to address 0x0a000000
Decompression Succeeded
Starting code...

Total Memory: 2GB Chassis Type: 0xfe Card Type: 0xe7

TiMos-L-9.0.R1 boot/hops Nokia 7705 SAR Copyright (c) 2000-2018 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Thu Sep 20 22:53:52 EDT 2018 by builder in /rel9.0/b1/R1/panos/main

TiMOS BOOT LOADER

Time from clock is WED SEP 26 15:07:13 2018 UTC
Switching serial output to sync mode... done

Looking for cf3:/bof.cfg ... OK, reading

Contents of Boot Options File on cf3:

primary-image ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images
primary-config ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images/dut-a.cfg
address xxx.xxx.xxx.xxx/24 active
address xxx.xxx.xxx.xxx/24 standby
primary-dns xxx.xxx.xxx.xx
dns-domain labs.ca.alcatel-lucent.com
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.x
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.x
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.x
autonegotiate
duplex full
speed 100
wait 4
persist on
no fips-140-2
console-speed 115200

Hit a key within 1 second to change boot parameters...

Primary image location: ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images

Initializing management port omii0 using IP addr xxx.xxx.xxx.xxx.
Initial DNS resolving preference is ipv6-first
init mgmt port using fe80::4af7:f1ff:feef:f953/64

Edition: 01 3HE147640011TQZZA 71
Software Upgrade Procedures 7705 SAR 9.0.R11 Software Release Notes

init mgmt port using 3000::8a78:d273/64

Loading image ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images/both.tim
Version B-9.0.R1, Thu Sep 20 23:02:48 EDT 2018 by builder in
/rel9.0/b1/R1/panos/main
text:(66204320-->201098368) + data:(5009504-->38139312)
Executing TiMOS image at 0x2800000

Total Memory: 2GB Chassis Type: 0xe8 Card Type: 0xe7

TiMOS-L.B-9.0.R1 both/hops Nokia 7705 SAR Copyright (c) 2000-2018 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Thu Sep 20 23:02:48 EDT 2018 by builder in /rel9.0/b1/R1/panos/main

___ ___ ___ ___

/\ \ /\__\ /\ \ /\ \
\:\ \ ___ /::| | /::\ \ /::\ \
\:\ \ /\__\ /:|:| | /:/\:\ \ /:/\:\ \
/::\ \ _\/__/ /:/|:|__|__ /:/ \:\ \ _\:\~\:\ \
/:/\:\__\ /\__\ /:/ |::::\__\ /:/__/ \:\__\ /\ \:\ \:\__\
/:/ \/__/ /:/ / \/__/~~/:/ / \:\ \ /:/ / \:\ \:\ \/__/
/:/ / /:/ / /:/ / \:\ /:/ / \:\ \:\__\
\/__/ \/__/ /:/ / \:\/:/ / \:\/:/ /
/:/ / \::/ / \::/ /
\/__/ \/__/ \/__/

Running 32 bit architecture

Time from clock is WED SEP 26 15:08:21 2018 UTC

Initial DNS resolving preference is ipv6-first
SMP: 6 cores available

Attempting to exec primary configuration file:

'ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images/dut-a.cfg' ...
System Configuration
System Security Configuration
Log Configuration
System Sync-If-Timing Configuration
Management Router Configuration
Router (Network Side) Configuration
Service Configuration
Router (Service Side) Configuration
Card Configuration
Port Configuration
Result of 'remove_mda' = 0 = 0x0
Executed 337 lines in 0.2 seconds from file
ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest2/images/dut-a.cfg

Attempting to exec successful configuration extension file:

'ftp://*:*@xxx.xxx.xxx.xxx/./images/env.cfg' ...
Result of 'StartNetLog' = 0 = 0x0
Executed 124 lines in 0.1 seconds from file
ftp://*:*@xxx.xxx.xxx.xxx/./images/env.cfg

Applying Security Policies.... OK

TiMOS-L.B-9.0.R1 both/hops Nokia 7705 SAR Copyright (c) 2000-2018 Nokia.
All rights reserved. All use subject to applicable license agreements.
Built on Thu Sep 20 23:02:48 EDT 2018 by builder in /rel9.0/b1/R1/panos/main

CSAHWTEST2 - 7705:Dut-A
Login:

72 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Software Upgrade Procedures

8. Verify the Software Upgrade

Allow the boot sequence to complete and verify that all cards come online. Verify the
Boot ROM and application software versions with the command show card detail.
If applicable, verify the 7705 MPR-e software with the command show mw radio
software.
Note: If any card fails to come online after the upgrade, contact your regional
Nokia Technical Assistance Center for information on corrective actions.

Edition: 01 3HE147640011TQZZA 73
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

10 Known Limitations
The following are the known limitations for Release 9.0.

Note: • Bracketed ( ) references are internal tracking numbers.

• Known limitations that have been added in this release are marked
as [NEW].

10.1 10-port 1GigE/1-port 10GigE X-Adapter Card

• When performing an Ethernet loopback with the peer-port negotiated flow-control

disabled, the 10-port 1GigE X-Adapter card port will still generate egress pause
packets for network and access ports. (P.633996, D.170276)
• Ingress pause frames are not counted in the general multicast and total packet
counters for the 10-port 1GigE/1-port 10GigE X-Adapter card and ports. The adapter
card only increments RxPause; therefore, only the RxPAUSE counter will be
updated in the CLI. (P.621034)
• The network egress queue PIR/CIR percentage of a 10G port when it is in WAN
mode is based on 10 Gb/s instead of on 9.294 Gb/s. (P.634001)

10.2 1588/PTP

• 1588 over a spoke SDP terminated into an IES service is not supported. 1588 is
supported over IES interface SAPs. (P.657255)
• If an access Ethernet port configured with encapsulation type dot1q is being used to
transport PTP packets, only the default Ethertype of 0x8100 should be used.
(P.616325)
• 1588/PTP messaging sessions are dropped and re-established after a CSM activity
switch occurs on a SAR-8 or SAR-18. It may take up to 30 seconds for sessions to
fully re-establish, during which time PTP slaves will be in holdover. (D.22621)
• A 7705 SAR running PTP may go into unexpected holdover and give poor
synchronization under the following conditions:
o two or more rapid switches occur between two grand masters in the network
a few minutes apart, and
o the two grand masters are frequency-synchronized but not phase-
synchronized (for example, two 7750 SR nodes or 7705 SAR nodes acting as
grand masters), and

74 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

o the 7705 SAR is located downstream from a boundary clock that passes on a
large phase shift to the Reference input of the 7705 SAR when the grand
masters switch.
After the issue occurs, PTP will recover on its own after a few hours and synchronize
to the proper source. (P.645314, D.170836)

10.3 16-port T1/E1 ASAP Upgrade to 32-port T1/E1 ASAP

• When upgrading a 16-port T1/E1 ASAP Adapter card that has network ports to a
32-port T1/E1 ASAP Adapter card, the maximum queue depth and reserved queue
depth for network queues (that is, MBS and CBS) will be larger in absolute terms
after the upgrade. This is because the 32-port T1/E1 ASAP Adapter card has more
buffers than the 16-port T1/E1 ASAP Adapter card and network queues are
configured as percentage of number of buffers. Under congestion, this could cause
the maximum latency through a network queue to be larger than intended. If this is
not desired, the MBS and CBS parameters in the network queue policy should be
reconfigured to smaller values after the upgrade. (P.602283)

10.4 2-port 10GigE (Ethernet) Adapter Card

• IGMP/MLD Group-Specific Query messages are dropped on the add-drop ports and
will affect functionalities between querier and non-querier in the same subnet. It is
not recommended that multiple IGMP/MLD interfaces be deployed in the same
subnet over a ring topology with the 7705 SAR. (P.658416)
• If there is traffic congestion on port 1, port 2, or the add-drop port of the 2-port
10GigE (Ethernet) Adapter card, the corresponding port queue drop counters will be
inaccurate while in the congested state. (P.650451)

10.5 2-port OC3/STM1 Channelized Adapter Card

• When changing the SONET/SDH port framing configuration from SONET to SDH (or
vice versa) on the 2-port OC3/STM1 Channelized Adapter card, some channels may
not come up properly. The affected channels will be in the “oof” (out of frame) alarm
state and their operational status will be down. To recover from this problem, the
adapter card must be reset. (P.621488)

Edition: 01 3HE147640011TQZZA 75
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

10.6 4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card and 7210 SAS-Sx SONET/SDH
Satellite

• If idle-payload-fill is configured to a non-default pattern on a channel group, the

payload will still be filled with the default all-ones pattern (ignoring the configured
pattern) if there is no SAP associated with the channel group or if the channel group
is shut down. The idle-payload-fill configuration will work as expected if the
associated SAP is shut down, the service employing that SAP is shut down, or if
user traffic is otherwise not arriving at the channel group. (D.261368)

10.7 4-port OC3/STM1 Clear Channel Adapter Card

• The 4-port OC3/STM1 Clear Channel Adapter card can only support up to 90% of
OC3 bandwidth in SAP-to-SAP Apipe applications or up to 50% of OC3 bandwidth
per port when all four ports are used in SAP-to-SAP Apipes. Traffic exceeding this
limit will experience random discards. (P.550977)

10.8 6-port SAR-M Ethernet Module

• Egress rate enforcement on the 6-port SAR-M Ethernet module network port or
hybrid port egress can cause unexpected delay and jitter at low rates, which can
adversely affect mission-critical applications.
A workaround is to make use of per-VLAN shapers as opposed to the egress rate. If
it is necessary to match null encapsulation behavior, set the port encapsulation to
dot1q and set the interface binding to VLAN 0, where traffic is always transmitted
without any VLAN tags. (D.210666)

10.9 8-port Voice & Teleprotection Card and 6-port E&M Adapter Card

• If a port is up and operational and the adapter card is then shutdown, the CLI
command show port will continue to show the port as “Oper Status Up” and
“Physical Link Yes”. (P.640803)

10.10 802.1X EAP

• RADIUS servers for accounting can be configured under the 802.1x EAP RADIUS
policy, but it is not supported. (P.599930)

76 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

10.11 ADP

• Automatic Discovery Protocol (ADP) is not supported on the 4-port SAR-H Fast
Ethernet module. Only the Ethernet ports on the main chassis (7705 SAR-H) will be
considered as candidates for ADP. (D.207116)

10.12 APS

• In some cases of RDI-L, the transmitted K1/K2 bytes on the wire may differ from
those maintained by the CSM’s APS controller (as displayed on the CLI). (D.36537)

10.13 ATM/IMA

• ILMI is not supported.

• ATM traffic is dropped if the Apipe service MTU is set below 52. This includes ATM
OAM cells generated from one endpoint towards the network uplink. The dropped
packets are tracked by the SAP statistic — Forwarding Engine Stats/Dropped
counter. (P.529055)
• If a link is administratively removed from the IMA group at the far end, the link defect
reported on the 7705 SAR will be LODS instead of LIF. To determine if a link that
reports LODS is actually experiencing the loss-of-delay defect, verify that the link at
the far end has not been removed. If the link still belongs to the IMA group at the far
end, it is truly experiencing LODS and should be investigated. (P.530743)
• An IMA link will not become active if added to an IMA group while the port scramble
setting is mismatched at the far end. If the port scramble setting on the 7705 SAR
IMA link is then changed to match the far end, an IMA group or adapter card reset
may be required to recover the link. To avoid this, set the port scramble setting to
match the far end prior to adding the link to the IMA group. (P.535052)
• Applying loopbacks on IMA links may lead to inconsistent behavior of the IMA group
and/or individual links. To use loopbacks for troubleshooting purposes, remove the
link from the IMA group before applying the loopback and only add it back to the
group once the loopback is removed. If IMA link loopbacks must be used, it is
recommended that all IMA links in the group have loopbacks applied and then all
loopbacks be removed. An IMA group reset may be necessary to recover the IMA
group once loopbacks have been removed. (P.535526)
• An ATM SAP that is part of an ATM SAP-to-SAP service will not generate AIS
towards the attached circuit if the two SAPs belong to different adapter cards and the
other SAP is down as a result of the adapter card being reset or removed.
(P.540477)

Edition: 01 3HE147640011TQZZA 77
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

• The Out Of Service event is not logged in the event log when an IMA group link goes
down because of an LIF or LODS event. (P.564826)

10.14 BFD

• A BFD session of type np with a transmit/receive/multiplier value of 10/10/3 over an

ASAP PPP link (on an ASAP adapter card) may occasionally bounce on a CSM
activity switch.
As a workaround, increase the multiplier value to 5. (P.667484)
• BFD sessions for multihop BGP PE-CE peers using VPRN SAP interface addresses
will not come up on the 7705 SAR.
As a workaround, configure BFD sessions for multihop BGP PE-CE peers using
VPRN loopback interface addresses. (P.613651)
• When using multihop BFD for BGP peering or BFD over reroutable links (for
example, spoke SDPs), the interval and multiplier values should be set to allow
sufficient time for the underlying network to reconverge before the associated BFD
session expires. A general rule of thumb should be that the expiration time (interval ×
multiplier) is three times the convergence time for the IGP network between the two
endpoints of the BFD session.

10.15 BGP

• The 7705 SAR will advertise a route to an IBGP neighbor with a next-hop value set
to itself instead of withdrawing the route when the 7705 SAR receives a route from
an EBGP peer and also has an import policy under router bgp with the next-hop
value equal to the address of the IBGP neighbor. (P.599285)
• If BGP transitions to the operationally disabled state, the clear router bgp protocol
command will not clear this state. The BGP protocol administrative state must be
shutdown/no shutdown to clear this condition. (D.12074)
• Changing the BGP router-id value in a Base or VPRN configuration will immediately
cause a flap of all BGP neighbors that are part of that instance.
The workaround is to execute a shutdown and no shutdown of the protocol before
the new router-id value is used. This would then be in line with what is documented
in the user guides. (D.121246, P.651274, D.170316)
• The policy-statement entry from interface name currently does not match any local
interface.
A workaround is to combine a prefix-list with from protocol direct. (D.89371)

78 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

10.16 CEM

• Setting the idle-signal-fill for timeslots 1 to 15 to be “pattern 0” can result in ABCD

bits in other timeslots being incorrect.
From ITU-T G.704 section 5.1.3.2.2 Table 14:
======================================================
NOTE 3 - When bits b, c or d are not used they should have the values: b = 1, c = 0,
d = 1.
It is recommended that the combination 0000 of bits a, b, c and d not be used for
signaling purposes for channels 1 to 15. (P.538480)

10.17 CLI

• Special characters (“\s”, “\d”, “\w”) do not work with pipe/match functions. (D.100089)
• Output modifiers (“| match” and “>”) are not supported in configuration files executed
using the exec command (scripts).
• The CLI allows the user to specify a TFTP location for the destination of the admin
save and admin debug-save commands that will overwrite any existing file with the
specified name. (D.18554)
• The system does not prevent the user from using the same IP address of its BGP
peer on one of its router interfaces. (D.57198)
• Non-printable 7-bit ASCII characters and extended ASCII characters (for example,
French letters with accents or special Turkish characters) are not allowed. These
characters were accepted for some description fields prior to Release 7.0; therefore,
while upgrading to Release 7.0.R1 or later, customers must ensure that the config
file does not contain any non-printable 7-bit ASCII characters within any description
field. (D.93998, D.269299)

10.18 Copper SFPs

• When the copper SFPs 3HE00062AA and 3HE00062CB are used for ports that are
configured for a speed of 1000 and no autonegotiation, they still advertise
1000Base-T full/half duplex. (P.628763)

10.19 DCR and MEF 8

• There is no DCR service parameter negotiation over MEF 8. If the nodes at either
end of the MEF 8 Epipes are using different DCR timestamp frequencies, the
error/timestamp frequency mismatch is not detected. While in this mismatch state,
the TDM ends of the MEF 8 Epipes are not synchronized.

Edition: 01 3HE147640011TQZZA 79
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

However, the MEF 8 Epipe services will still be up, the TDM ports will be in a
differential Normal state, and there will be no log 99 events raised to indicate the
mismatch. (P.666202)

10.20 DHCP

• If there are more than 20 DHCP client-enabled network interfaces between two
adjacent nodes, OSPF may fail to reconverge after a port shutdown maintenance
operation. OSPF must be restarted (shutdown/no shutdown) in order for OSPF to
reconverge again. (P.655059, D.170339)
• The following limitations are applicable to the DHCP server persistence feature on
the following 7705 SAR platforms: SAR-A, SAR-H, SAR-Hc, SAR-M, SAR-W and
SAR-Wx.
o Lease remaining time
After a power cycle, DHCP leases that were issued before the power cycle
may have the remaining lease time set to the maximum lease time of the
corresponding DHCP pool.
o Lease start time
After a power cycle, the lease start time will be inaccurate. This will be
automatically corrected when the lease is renewed.
o 7705 SAR performance
It is recommended that a lease time of at least 12 hours be used when DHCP
persistence is enabled. A shorter lease time, particularly when combined with
a large pool of DHCP addresses, can put a large load on the 7705 SAR CPU,
potentially affecting system performance. (D.199504)
• When using the “unnumbered system IP address via DHCP” feature, the system IP
address assigned via DHCP can expire and it is possible that a new system IP
address can be assigned to the node. In this case, if an ICMP ping with a large
packet count is started before the IP address expires, the ping packets will continue
to have their source address set to the old system IP address, even after the new
system IP address is applied to the node. (D.208075)

10.21 Differential Clock Recovery (DCR)

• If the DCR timestamp frequency at each end of the Cpipe does not match, the SDP
flags bounce between “NoEgrVCLabel” and “ServiceParamMismatch”. It should just
be “ServiceParamMismatch”. The log 99 queue also fills up with SDP Bind status
change events, a few every second, and they do not stop until the timestamp
frequency mismatch condition is resolved. (P.634847, D.170448)

80 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

10.22 Ethernet Adapter Cards

• On rare occasions, collision counters on the 8-port Ethernet Adapter card v2 may
increment falsely. The issue can be identified by sudden increments in single,
multiple, and late collision counters. This issue has no traffic impact. Collision
counters can typically be safely ignored in ports that are operating in full-duplex
mode. (D.170430)
• The Ethernet port “Tx Bytes” statistics do not include the padding bytes for slow path
packets (for example, ICMP ping) as opposed to the “Rx Bytes” statistics that
properly count them. (P.613019)
• The minimum inter-frame-gap for a Gigabit Ethernet egress port with a copper SFP
should be 96 bits. It is currently between 96 bits and 116 bits. The throughput at
egress for the Gigabit Ethernet port is decreased accordingly. (P.546358)
• If a high rate of traffic with a significant number of small packets flows through an
Ethernet Adapter card, the adapter card may be adversely affected. This situation
may cause a range of impairments, from traffic loss to flapping of services.
If specific numbers need to be known, please contact Nokia. (P.539628)
• Received Ethernet broadcast or multicast frames greater than 1518 bytes (null
encap) and 1522 bytes (dot1q encap) are counted as RxUnicast packets under
Ethernet port statistics. This issue only applies to the 8-port Ethernet Adapter
card v2. (P.553552)
• Failure of the active network BFD link can lead to an outage of 5 seconds due to the
bouncing of the access Ethernet port, when LLF (Link Loss Forwarding) is enabled
on an Ethernet SAP of an Epipe and parallel network links are configured with BFD.
(P.562751)
• The minimum inter-frame-gap for 10M Ethernet egress ports has been changed from
12 bytes to 24 bytes. The throughput on access egress for 10M Ethernet ports
(Epipe or Ipipe service) has been decreased accordingly. The change is only
applicable to the 8-port Ethernet Adapter card v2. (P.564292)

10.23 IES

• In the saved configuration for IES services, the IES instance and interfaces will
appear twice: once for creation purposes and once with all the configuration details.
This allows configuration items such as DHCP server configuration to reference
another IES interface without errors. (D.56086)

Edition: 01 3HE147640011TQZZA 81
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

• If two IES interfaces are connected back-to-back through a 2-way spoke-SDP

connection with SDPs that have keepalive enabled and IGP enabled on the IES
interface with a lower metric as the network interfaces, the related SDPs will bounce
due to SDP keepalive failure. With this configuration, the GRE-encapsulated SDP
ping reply will be ignored when it is received on an IES interface. (D.68963)

10.24 IP Filters

• If filter logs are used with ingress spoke-SDP filters with Layer 2 to Layer 3 spoke
termination, incorrect source MAC information is populated in the filter log.
(P.624468, D.170830)

10.25 IP/MPLS

• If the ARP timeout for an interface is programmed to a value in the range of 1 to 45

seconds, then protocols such as LDP, using the ARP entry, may occasionally
bounce. (P.529377)
• The 7705 SAR releases starting at R2.1.Rx only support a maximum LSP ping/trace
octet size of 2084. (P.556573)
• If triggered-policy is configured, LDP policies are not dynamically evaluated for
changes in FECs. (D.71830)
• The no rsvp command in the config>router context has no effect as the state of
RSVP is tied to the MPLS instance. The no mpls command deletes both the MPLS
and RSVP protocol instances. (D.8611)

10.26 IP Multicast

• An IP multicast packet that requires fragmentation is silently discarded. Configure

the IP interface MTU and port MTU properly to avoid IP fragmentation. (P.660252,
D.170287)

10.27 IPSec

• If CMPv2 or OCSP are configured to use a VPRN service, the server must use port
80 or 8080. (D.228482)

10.28 IP Statistics

• Network APS IP interface statistics will be inaccurate following an APS switch.

(P.620827)

82 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

10.29 IS-IS

• In some specific IS-IS multi-level topologies, CSPF may, on rare occasions,

calculate an incorrect path through Level-1 if the system interface IP address is the
IS-IS router ID and the system interface is configured as Level-2 only. (D.102537)

10.30 Jumbo Frames

• For IP multicast, the fabric will broadcast a given packet to each adapter card that is
part of that multicast group; however, an issue arises when the ingress adapter card
supports jumbo frames and a jumbo packet for each IP multicast group arrives.
If the IP multicast group has a member that resides on an adapter card that does not
support jumbo frames, the packet is dropped on the egress of that adapter card.
(D.170323)
• Some pings may fail if rapid pings are sent to a 7705 SAR node with a large size
parameter. This is because the PIR of the 7705 SAR ingress control queue for ICMP
packets is set at 2 Mb/s. For example, if pings are sent at a rate of 100 pings/s,
some pings will fail when a size parameter greater than 2500 bytes is used.
The interval option of the ping command can be used to reduce the ping rate for
higher packet sizes. (D.180716)
• On certain Ethernet ports, traffic may be impacted when using copper SFPs at
10 Mb/s with jumbo frame size. Copper SFPs running at 100 Mb/s and 1 Gb/s are
not affected. (D.180934)

10.31 LDP

• Modifying the Hello LDP timers while the Hello adjacency is up does not come into
effect until the adjacency bounces. However, after two High-Availability switchovers,
the active CSM will start using the new timer value. (D.108407, P.604751,
D.170276)

10.32 Management

• Collision events detected on a CSM management Ethernet port are reported as

CRC/Alignment errors. (D.30205)
• Source address configuration applies only to the Base routing instance and, where
applicable, to VPRN services. As such, source address configuration does not apply
to unsolicited packets sent out the management interface.
• The SSHv2 implementation does not support the RC5 cryptographic algorithm.
(D.47122)

Edition: 01 3HE147640011TQZZA 83
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

• Threshold monitoring results for cflash-cap and memory-use might be incorrect if a

negative threshold is used. (P.532095)

10.33 MLPPP

• A shutdown then no shutdown of an MLPPP bundle may cause the bundle to

a) not come up or b) not pass traffic, when there are loopbacks on one or more
member links. (D.143509, P.642217, D.170585)

10.34 MPLS/RSVP/SRLG

• Least-fill behavior is not exhibited when the user does a configuration change MBB
by decreasing the bandwidth on the LSP. (D.74544)
• If a local IP address is configured with the same address as the destination address
of an MPLS LSP, the LSP will no longer be set up and will use the RSVP error code
of “routingError”. (D.73326)
• RSVP LSPs cannot be signaled over a channelized DS1 or E1 interface if the
channel group bandwidth is less than 1 Mb/s. (D.59776)
• Shutting down a port on an OC3/STM1 adapter card may not provide sub-50 ms
failover for an RSVP path signaled over that port. (D.39973)
• If a user configures or changes the SRLG constraint of the outgoing links of both the
primary LSP path and its bypass LSP to the same value when both paths are up,
then an MBB of the primary LSP path may result in the new path being associated
with the older bypass path. This condition will remain until the bypass path is
reoptimized. In such a case, the older bypass LSP path will no longer be SRLG
disjoint with the outgoing link of the primary path even if the user enabled the strict
option with the config>router>mpls>srlgfrr command.
To work around this issue, disable the dynamic bypass LSP setting on the system
and enable it again using the config>router>mpls>dynamic-bypass {enable |
disable} command. This triggers a new bypass to be created.
For a manual bypass tunnel, the user may have to perform a shutdown and no
shutdown of the manual bypass tunnel.
• If a user configures or changes the SRLG constraint of any link of the primary LSP
path and that of any link of its SRLG secondary path to the same value when both
paths are up, then an MBB of the primary LSP path may result in the new primary
path no longer being SRLG disjoint with the secondary path.
To work around this issue, perform a manual resignal of the secondary path, which
will update it with the most recent SRLG information, and the SRLG constraint will be
evaluated correctly.

84 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

• Fast failover times of less than 100 ms cannot be achieved for fast reroute protected
LSPs if the failed link is detected by copper Ethernet SFPs. Sub-second failover
times are achieved, but the failover times with copper Ethernet SFPs are inherently
longer based on how the system communicates with the SFP. (D.49003)
• There are scenarios where the bypass optimization does not ensure that a node-
protect manual bypass will be selected over a node-protect dynamic bypass tunnel.
This is because the manual bypass may be unavailable when the association of a
bypass LSP is made with the primary LSP. The bypass optimization feature only
changes the association for an LSP that requested node protection but is currently
associated with a link-protect bypass.
To ensure this selection when using manual bypass, dynamic bypass must be
explicitly disabled. (D.60261)
• When an LSP with admin-group constraints traverses a node with parallel interfaces
to the next hop, and the LSP avoids one of the interfaces due to an exclude
constraint, the LSP can choose the excluded interface during a resignal after a
failure and recovery of the original interface. This happens when the parallel
interfaces are configured as OSPF point-to-point and both physical links are
connected to the same Layer 2 switch. (P.608181)

10.35 Multi-segment PW Switching

• When configuring a Cpipe VLL service with the VC-switching option enabled at a
Switching PE (S-PE) node, the resulting multi-segment PW must have contiguous
signaled PW segments from the S-PE node all the way to at least one of the Target
PE (T-PE) nodes. In other words, there must not be a static PW segment in between
the nodes. If this is not the case, the interface parameters cannot be signaled to the
S-PE, which then cannot send a label mapping message for the PW FEC in the
reverse direction. (P.582310)

10.36 Network LAG

• BFD type np is not supported on ports that are in an active-active LAG group. This
configuration is not blocked; however, it is unsupported and will not function
correctly. (D.225731)

10.37 NTP

• In-band NTP time recovery without MDA timestamping may have degraded
performance that can negatively impact the accuracy of OAM tests. An alternative is
to turn on MDA timestamping.

Edition: 01 3HE147640011TQZZA 85
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

Another alternative for the 7705 SAR fixed platforms (not the 7705 SAR-8 or 7705
SAR-18) is to use IEEE 1588 as the router’s time source. (D.216154)

10.38 OAM

• Ethernet ports should not be configured with short EFM-OAM timeouts (for example,
transmit-interval 1 multiplier 2); otherwise, they may bounce, affecting services
associated with the port. The configured EFM-OAM timeout value should be at least
300 ms or longer (transmit-interval 1 multiplier 3) (D.221672)
• Even if source-mac is specified when using oam cpe-ping, the resulting ARP
request packet sent to the CPE device will still use the chassis base MAC address.
(D.85034)
• The 7705 SAR may add delay on a CPE ping test; therefore, SAA jitter threshold
and jitter results for CPE ping are not accurate. The results are not a proper
reflection of the actual jitter. (P.599295)
• Delay measurements over multiple VPLS segments may not be accurate and are not
a reflection of the actual delay. Therefore, an SAA MAC ping test over a single VPLS
segment is recommended. (P.599297)
• ATM OAM F4 cells on a VPC Apipe service are always sent with a PTI equal to four
(4) for SEG cells and a PTI equal to five (5) for end-to-end cells. (D.75052)
• If a MAC ping or MAC trace request is sent with a source MAC address over a mesh
SDP to a VPLS instance with multiple SAPs, the user will see duplicate reply
messages. This is the expected behavior. (D.16298)
• An OAM service ping request for a VPRN service is always sent over the data plane
(over the spoke SDP) and not through the control plane. A VPRN ping should be
used to send a ping request using the control plane for a VPRN instance. (D.58479)
• When more than 150 SAA result files exist on CF3, additional SAA tests might fail
when attempting to write results to CF3. When SAA tests are scheduled as CRON
jobs, it is recommended that results be sent to an FTP server instead of being saved
on CF3. (P.528324)
• The behavior of VCCV ping on the 7705 SAR differs slightly from the SR platform
(7710, 7750) in a number of local failure scenarios. In particular, the 7705 SAR will
not respond to a VCCV ping with reply-mode ip-routed if:
o the associated service is “admin down”
o the associated SDP is operationally down or “admin down”
o the associated LSP is operationally down or “admin down”
o the associated access adapter card is not in service
(P.529694)

86 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

• One SAA VCCV ping may have an additional delay when it is launched over a single
pseudowire segment with a send-count set to 100. (P.599299)
• Running concurrent ping tests with a high count of repeats may lead to system
memory exhaustion, resulting in unpredictable behavior such as MPLS/RSVP
shutting down. (P.621272)
• An OAM VPRN ping or VPRN trace will fail if the packet size exceeds
<SDP OprMtu – 44>. (D.208986)

10.39 OSPF

• A router with more than one point-to-point adjacency to another router over links of
equal metrics may compute the shortest-path tree over the incorrect link in the case
of unidirectional link failures on the far-end router. This condition lasts until the dead
timer expires and the adjacency over the broken link is brought down locally (near
end).
A workaround is to change to broadcast interfaces or enable BFD on them.
(D.79495)
• The system may refresh self-originated LSAs shortly after completing a CSM
switchover. This may mean that the entry is refreshed before the expiration of the
age-out period. (D.65195)
• To disable OSPF-TE on a link, both ends of the link should be MPLS/RSVP-disabled
in order for CSPF to work correctly and should be removed from the TE database.
(D.15127)

10.40 PIM-SSM

• The Router Alert IP option is not included in mtrace queries that are unicast to the
last-hop router in the trace as defined by the IETF draft. This causes no known
interoperability issues since this packet is still destined for an IP address on this last-
hop router. (D.37923)
• Third-party routers that incorrectly send mtrace queries to the group multicast
address rather than the ALL-ROUTERS.MCAST.NET address (as defined by the
IETF draft) will be discarded. Additionally, some routers do not fill in the “oif” field in
the response block and some do not accept an mtrace query that comes in on the
“oif” interface.
A workaround in this last case is to use the RPF as the destination address for the
query. (D.39070)

Edition: 01 3HE147640011TQZZA 87
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

10.41 QoS

• For sanitized operation of the datapath, the MBS of any configured queue should be
deep enough to host at least three packets at any time. (P.534118)
• The status of any services may bounce Up and Down when CBS is overbooked, the
SAP and/or network queues are congested, and no shared buffer pool is left.
(P.553157)
• The scheduling accuracy at a hybrid port for jumbo traffic (9000 bytes and larger) at
a low egress rate (15 Mb/s and lower) may not be within a –/+ 1% range; the
scheduling error can be up to –/+ 3%.
As a workaround, the port can be set to network or access mode or the rate can be
increased to above 15 Mb/s. (D.210667)
• Additional jitter may be introduced in the datapath on first- and second-generation
adapter cards and platforms if a SAP uses 4-priority scheduling on ingress or egress
and if the CIR is configured to a very low value, such as a few kb/s. (D.350109)

10.42 RADIUS

• In defining RADIUS Vendor Specific Attributes (VSAs), the TiMetra-Default-Action

parameter is required even if the TiMetra-Cmd VSA is not used. (D.13449)
• If the system IP address is not configured, RADIUS user authentication will not be
attempted for in-band RADIUS servers unless a source-address entry for RADIUS
exists. The NAS IP address selected is that of the management interface for out-of-
band RADIUS servers. For in-band RADIUS servers, if a source-address entry is
configured, the source address is used as the NAS IP address; otherwise, the IP
address of the system interface is used.
• SNMP access cannot be authorized for users by the RADIUS server. RADIUS can
be used to authorize access to a user by FTP, console, or both.
• If the first server in the list cannot find a user, the server will reject the authentication
attempt. In this case, the 7705 SAR router does not query the next server in the
RADIUS server list and denies access. If multiple RADIUS servers are used, the
software assumes they all have the same user database.

10.43 Routing

• Routes exported from one protocol to another are redistributed with only the first
ECMP next hop. Therefore, if BGP routes having multiple next hops are exported to
a VPRN client, only one next hop for the route will be exported. The one chosen is
the lowest IP address of the next-hop address list. (D.40147)

88 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

10.44 RS-232 Asynchronous Cpipe

• A small amount of the payload may be periodically lost when sending a single-
character payload into a serial interface configured for asynchronous mode. This
issue does not exist when sending two or more characters back to back. It applies
only to the 12-port Serial Data Interface card v1. (D.205268)

10.45 RSVP

• An RSVP LSP with an administrative group and hop limit constraints may fail to find
a CSPF path through the TE-enabled network when a valid path meeting all
constraints exists. (P.575297)

10.46 R-VPLS

• 1588 PTP control packets will not be processed by the protocol if the packets are
received via an r-VPLS interface.
As a workaround, ensure that all 1588 PTP control packets are received by
recommended interface types. This can be done via proper IGP configuration.
(P.647006)
• Under an r-VPLS interface, BFD packets will always be multicasted regardless of the
FDB state. BFD control packets will be transmitted to all VPLS egress-leaves even
after the BFD neighbor's MAC address is installed in the FDB. (P.642749)

10.47 SAR-M xDSL Module or DSL Combination Module (DCM)

• In 2p-ADSL2/2+ ATM bonding mode on the xDSL or DCM module, when line 1 is
shut down but line 2 is active on the 7705 SAR-M, the bonding group never comes
up. As a result, the xDSL ports stay down. (P.613542)

10.48 SDH

• The system does not prevent the user from entering more than 15 bytes in a path
trace field for ports that have been configured for SDH framing; however, the system
will only use the first 15 bytes of the entry for the path trace. (D.99733)

Edition: 01 3HE147640011TQZZA 89
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

10.49 Services General

• When the standby spoke SDP of an endpoint becomes active due to a revert-time
expiration or a forced switchover, the SAP may forward duplicated packets (only of
broadcast/multicast/unlearned unicast types) coming from the redundant spoke
SDPs for a few milliseconds. It is recommended that the redundant spoke SDPs be
operated in non-revertive mode. (D.67252)
• A GRE SDP is not supported over an RSVP-TE shortcut. The GRE SDP will go
down if the destination is reachable via an RSVP-TE shortcut route. (D.91257)

10.50 SNMP

• A system that does not have a system IP address or a management IP address

configured may not be able to generate SNMP traps. (D.98479, P.650915,
D.167564)
• Using SNMP to change the admin state of an interface in the VPRN context (that is,
TIMETRA-VRTR-MIB::vRtrIfAdminState) does affect the interface; however, the
state change is not reflected in the CLI configuration of that interface. Consequently,
there will be a mismatch between the actual state of the interface and the CLI
configuration.
This issue does not affect admin state changes using the CLI. Using iesIfAdminState
instead works as expected, and there will be no mismatch between the CLI and
SNMP of the interface admin state. (D.138341, P.634463)
• The SNMP MIB attribute snmpEngineTime is restarted upon a High Availability
switchover or system reboot. Additionally, the snmpEngineBoots attribute is
restarted on a system reboot. (D.46179)
• TIMETRA-PORT-MIB.mib does not include an entry for “Link Length support” as an
attribute of a Gigabit Ethernet port. This prevents the NSP NFM-P (formerly 5620
SAM) from reporting the value even though this attribute is reported on the CLI.
(D.46225)
• After 497 days, system up-time will wrap around due to the standard RFC 1213 MIB-
II 32-bit limit. (D.51129)
• The saved indicator in the prompt (represented by *) does not function properly
under the config>log>snmp-trap-group context. (P.536640)
• The following limitation applies to the SAR-18 platform only. When two trap-targets
with different destination subnets are configured, the ssiRedSwitchover trap may not
get generated to the first trap-target.
As a workaround, create a dummy trap-target that will be placed as the first trap-
target (trap-target is sorted by target name in alphabetical order). (D.182684)

90 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

10.51 Spanning Tree

• The RSTP Spanning Tree Protocol operates within the context of a VPLS or mVPLS
service instance. The software allows for the configuration of an STP instance per
VPLS service instance or mVPLS service instance; however, some traffic loss may
occur as STP convergence is highly dependent on 1) the number of SAPs/SDPs per
VPLS and 2) the number of MAC addresses active within a VPLS.

10.52 Synchronization

• System synchronization references from Ethernet Adapter cards may display the
admin status as “OOF OOPIR” rather than “LOS” during periods of Loss Of Signal
(LOS). (P.557974)
• A port configured for differential clock recovery or adaptive clock recovery has a
master channel group, CG #1. When a Cpipe SAP is the DCR or ACR master
channel group, changing its jitter buffer size can result in short loss-of-frame and
loss-of-signal defects at the far end of an E1 link. The far-end defects are of short
duration, so alarms will clear within 1 second. (P.621784)
• Certain port configurations are blocked when those ports are used as system
synchronization timing references; however, if the operator changes the system
sync-if-timing configuration, but does not execute the commit command, those
previously blocked configurations are allowed. If any of those port configurations are
modified, and the system sync-if-timing configuration session is then aborted or
times out, an invalid configuration occurs. If the configuration is saved to a database
file, it will be corrupt. (P.623151)

10.53 System

• Event logging to the compact flash cf1: or cf2: of the 7705 SAR-18 does not restart
after space becomes available if the compact flash has previously been filled. To
restart the event logging to the compact flash, the user must deconfigure and
reconfigure the log-id. (P.598734)
• Larger compact flashes (2G, 4G, or 8G) may have issues copying files if the
compact flash has been formatted and many wildcard file commands (for example,
“file copy both.tim both.tim[1..45]”) are executed. (P.578278)
• Saved configurations may be corrupted if two admin save operations are performed
simultaneously. (P.530664)

Edition: 01 3HE147640011TQZZA 91
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

• When Adaptive Clock Recovery (ACR) is used to generate the timing of the data out
of an E1 or T1 port, the Cpipe should be configured with an appropriate packet rate
to ensure that the speed at which packets are generated is at least 125 packets per
second. This is equivalent to a packet inter-arrival time of no more than 8 ms. The
recommended packet rate is 1000 packets per second (1 ms inter-arrival time).
(P.531060)
• A Cpipe or SAP that is configured as a synchronization reference using Adaptive
Clock Recovery may be shut down by the user. This could result in the 7705 SAR
losing network synchronization. (P.530823)
• The CSM management port may stop working if cabled to a hub operating in half-
duplex mode or any device having duplex mode mismatch. If the problem occurs, a
CSM reboot may be required to recover. (P.600143, D.268532)
• After a single transient power event, an adapter card may continue to raise—after
every card reboot—an event in log 99 and 100 along these lines: UTC CRITICAL:
LOGGER #2002 Base 1:PLATFORM:UNUSUAL_ERROR "Slot 1:
platformDiagsMdaIsAreaFailed: The last card (MDA 6) reboot was caused by a
power supply transient event (Power Supply Warning)". The alarm should only be
raised once, when the event actually happens. If this issue is encountered, reseating
(not resetting) the adapter card will stop erroneous future occurrences of the alarm.
(D.284825)

10.54 TACACS+

• Inconsistencies can arise depending upon the combinations of the local, RADIUS,
and TACACS+ configurations. For example, if the local profile restricts the user to
only FTP access, the authentication order is TACACS+ before local, the TACACS+
server is Up and the TACACS+ default user template allows console access, an
authenticated TACACS+ user will be able to log in to the console using the default
user template because TACACS+ does not provide granularity in terms of granting
FTP or console access. If the TACACS+ server is Down, the user will be denied
access to the console as the local profile only authorizes FTP access. (D.39392)
• If the TACACS+ start-stop option is enabled for accounting, every command will
result in two commands in the accounting log.
• If TACACS+ is first in the authentication order and a TACACS+ server is reachable,
the user will be authenticated for access. If the user is authenticated, the user can
access the console and any rights assigned to the default TACACS+ authenticated
user template (config>system>security>user-template tacplus_default). Unlike
RADIUS, TACACS+ does not have fine granularity for authorization to define if the
user has only console or FTP access, but the 7705 SAR OS supports a default
template for all TACACS+ authenticated users.

92 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Known Limitations

If TACACS+ is first in the authentication order and the TACACS+ server is not
reachable, authorization for console access for the user is checked against the
user’s local or RADIUS profile if configured. If the user is not authorized in the
local/RADIUS profile, the user is not allowed to access the console.

10.55 TDM

• When a TDM channel is administratively disabled, the alarm statuses from show
port are correct; however, the alarm log “Alarm RAI Set” is only reported when the
condition is cleared. (D.58505)

10.56 VPRN

• MPLS tunnels carrying VPRN data may bounce, causing a brief data outage, when a
CSM switchover is performed. (P.577307)
• When fragmentation occurs at the SAP egress, the SAP egress queue statistics may
not reflect the fragmentation. (P.573185)
• Ingress data flow can be delayed up to 25 ms for each link when an MLPPP link
belonging to a VPRN MLPPP interface goes down. Once the link is taken out of
service, the data bursts at an ingress SAP queue rate (default 200M) towards the
fabric. As a result, if the egress port rate is below 200M, the SAP egress queue may
overflow, causing packet loss. If the SAP egress queue is shared by multiple ingress
SAPs, the packet loss may be experienced by all the SAP data flows.
To avoid the above issue, configure the MLPPP SAP ingress queue rate to a lower
value. (P.573700)
• When the local/static routes of one VRF are imported into another VRF and the
local-preference gets changed by an import policy, when the same routes are
exported/advertised to peers, they are advertised with the local-preference set by the
import policy. (P.576927)
• VPRN service traffic with the DF (Do Not Fragment) flag set received from an SDP
tunnel and requiring fragmentation is correctly discarded, but an ICMP Type 3 Code
4 (fragmentation needed and DF set) message is not issued. (D.18869)
• The use of auto-bind and spoke SDP within a VPRN are mutually exclusive.
(D.21529)
• The service operational state of a VPRN might be displayed incorrectly as Up during
its configuration while some mandatory parameters to bring it up have yet to be set.
(D.31055)

Edition: 01 3HE147640011TQZZA 93
Known Limitations 7705 SAR 9.0.R11 Software Release Notes

• Each MP-BGP route has only one copy in the MP-BGP RIB, even if that route is
used by multiple VRFs. Each MP-BGP route has system-wide BGP attributes and
these attributes (preference) cannot be set to different values in different VRFs by
means of VRF import policies. (D.34205)
• Misconfiguring the network such that two VPRNs are leaking the same prefix from
the VPRN to the GRT results in only one leaked route in the GRT. After correcting
that misconfiguration, an additional VPRN shutdown/no shutdown is required.
(D.179766)
• VPRNs auto-bound to GRE tunnels cannot coexist with IGP shortcuts because the
line cards or CFM cannot forward GRE-encapsulated traffic for tunneled next hops.
(D.91863)

94 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11 Resolved Issues
The following are specific technical issues that have been resolved in Release 9.0.

Note: Bracketed ( ) references are internal tracking numbers.

Issues marked as MI have a minor impact and will not disturb network
traffic.
Issues marked as MA may have a major impact on the network and may
disturb traffic.
Issues marked as CR are critical and will have a significant impact on
the network.

Note: Issues that were resolved in earlier releases, but which were not
documented until the current release, are marked as [NEW] and are
documented in the applicable section for the release.

11.1 Release 9.0.R11

11.1.1 LAG

• If a LAG group has member ports and the mode of the LAG group is changed (for
example, from network to access), the MTU of the member ports is erroneously
changed to the default MTU for that port type. The MTU of each member port
should align itself with the new MTU of the LAG group. If there are different port
types in a LAG group, this may lead to an invalid configuration that will fail to load.
(D.355399-MI)

11.1.2 Multi-chassis Firewall

• An IP packet may be corrupted or an adapter card may reset if a packet is going

through a firewall and is forwarded from a slave to a master node on a multi-chassis
link (MC-link) in a multi-chassis firewall (MCFW) configuration and the port MTU is
256 bytes or smaller. This issue may occur on any 7705 SAR platform except for the
SAR-8 and SAR-18. (D.354603-MA)

11.1.3 NAT

• An IP packet may be corrupted if NAT is applied and the IP packet uses optional
parameters. (D.352616-MA)

Edition: 01 3HE147640011TQZZA 95
Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.1.4 OAM

• During 802.1x authentication, the EAP identifier is incorrect in the EAP Success
message. This may cause interoperability issues with some third-party equipment.
(D.348400, D.356104-MI)

11.1.5 QoS

• Configured sgt-qos values for PTP (under the config>router>sgt-qos>application

ptp dscp context) are not kept following a node restart for a subset of PTP message
types. The affected message types are sync, delay-req, delay-resp, pdelay-req,
pdelay-resp, and follow-up. After a node restart, these PTP message types are sent
with the default DSCP value of nc1 regardless of what is configured. To recover,
toggle the configured value to another value and then back to the desired value.
(D.353387-MI)

11.1.6 System

• Only one management interface is allowed. However, the CLI does not block the
creation of additional management interfaces. (D.248238-MI)
• In rare cases, an SCP file transfer may cause the active CSM to reset.
(D.353301-MA)
• In a system with CSM redundancy, the configuration no power-feed-monitoring
reverts to the default (power-feed-monitoring) after a CSM switch. (D.353736-MI)
• The port LEDs on 8-port FXO Adapter cards (a8-fxo) and 6-port FXS Adapter cards
(a6-fxs) are not illuminated as expected when a port is in a no shutdown state. This
issue was introduced in 9.0.R4. (D.356218-MI)

96 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.2 Release 9.0.R10

11.2.1 4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card

• If a network interface is configured with an egress IP filter, the interface is bound to

an APS port, and one of the adapter cards in that pair is reset, followed by the
removal of the filter while the adapter card is still booting, there is a possibility that
the active CSM may reset. This is seen on the 4-port OC3/STM1 / 1-port
OC12/STM4 Adapter card (a4-choc3/12) only. (D.233616-MA)

11.2.2 Cflowd

• MVPN traffic egressing on a network interface on an iLER node will be reported by

Cflowd using an MPLS flow report template. It should be reported using an IP flow
report template. (D.349669-MI)

11.2.3 Cpipes

• Services on 2-port OC3/STM1 Channelized Adapter cards (a2-choc3) or 4-port

DS3/E3 Adapter cards (a4-chds3) may experience data corruption if the channel
group used for the service is configured for no signal-mode and if the E1 containing
that channel group is configured for signal-mode cas and the far-end DS1 is
configured for no signal-mode. (D.352259-MI)

11.2.4 MC-LAG

• MC-LAG is only supported for Layer 2 services. However, if a LAG group has
already been configured as a VPRN SAP and that LAG group is subsequently
configured for MC-LAG, the configuration is not blocked. (D.347494-MI)

11.2.5 Microwave

• For a managed microwave radio, Adaptive Coding and Modulation (ACM) statistics
displayed in the CLI under show mw radio port-id perfmon acm will show a
maximum value of 256 QAM. These statistics should show values up to 2048 QAM.
(D.348025-MI)

Edition: 01 3HE147640011TQZZA 97
Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.2.6 MPLS/RSVP

• Using the isis advertise-tunnel-link command in conjunction with the mpls

interface srlg-group command results in an invalid IS-IS TE-SRLG TLV being
advertised for advertised tunnels. This can result in failing or incorrect CSPF
calculations. (D.349048-MA) [NEW]

11.2.7 QoS

• When a destination-mode fabric profile is assigned for access ingress shaping on

an adapter card hosting Apipe SAPs, the traffic ingressing on those SAPs is not
shaped according to the configured fabric-profile rate. This issue was introduced in
9.0.R7. (D.348178-MA)

11.2.8 System

• If an SSH session is initiated from a 7705 SAR node to a remote SSH server and the
7705 SAR node has preserve-key enabled, after that 7705 SAR is rebooted, a user
initiating another SSH session to the same SSH server will be prompted again to
confirm that they want to continue connecting and re-add the host to the list of
known hosts. They should not be prompted again as preserve-key is enabled.
(D.350273-MI)

11.2.9 VRRP

• If the use-virtual-mac option is enabled under config>router>router-

advertisement>interface or config>service>vprn>router-advertisement>
interface, the node erroneously sends ICMPv6 router advertisement packets using
the port MAC as the source address in the Layer 2 header (the virtual MAC address
should be used in this case). The impact is that the configured virtual MAC address
will not be learned in an IPv6 VRRP with Layer 2 configuration (VRRP VPLS or
VRRP hub). (D.334376-MA)
• VRRP is not supported in the base router (config>router>interface) context;
however, the configuration is allowed. It should be blocked. (D.349430-MI)

98 3HE147640011TQZZA Edition: 01
7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.3 Release 9.0.R9

11.3.1 1588/PTP

• The CLI show command show system ptp clock 1 unicast is missing the “out”
counters. This issue was introduced in Release 9.0.R4. (D.343870-MI)

11.3.2 BGP-EVPN

• In MAC mobility, a PE attached to an all-active multihoming Ethernet Segment (ES)

does not select a remote MAC route if the MAC was previously learned on the local
ES SAP and on a peer PE on the same ES, even if the remote MAC has a higher
sequence number. (D.316307-MI)

11.3.3 CLI

• CLI rollback may fail if there are configuration changes to a router interface with a
physical port configured and used as a PTP source-interface (this does not affect
system or loopback interfaces). This issue was introduced in Release 9.0.R4.
(D.315563-MI)
• When a new RSVP point-to-point LSP is automatically established by the auto-LSP
feature, the configuration change indicator "*" appears in the CLI prompt even
though no configuration changes were made. (D.344048-MI)

11.3.4 EVPN

• BMU VPLS traffic that ingresses a 7705 SAR-X from an EVPN network will be
wrongfully discarded if it is meant to egress on a different MDA. This is not an issue
on any other 7705 SAR platform. (D.340556-MA)

11.3.5 Filters

• An egress MAC filter on a VPLS SAP in a LAG group will stop working if any link is
removed from the LAG group. (D.308392-MA)

Edition: 01 3HE147640011TQZZA 99
Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.3.6 Microwave

• For a managed microwave radio, the power statistics displayed in the CLI under
show mw radio port-id perfmon power will be erroneously shown as a very large
positive number whenever it should be a negative value. For example, if the
correct/actual value is -50 dBm, it will be displayed in the CLI as 65046 dBm. In
addition, positive values will be off by a factor of 10. For example, 17.0 will be
displayed as 170. (D.344630-MA)

11.3.7 Multicast

• A p2mp-lsp-ping test will fail in an mVPN configuration. This issue was introduced
in Release 9.0.R8. (D.343008)

11.3.8 OAM

• An Up MEP configured on a VPLS SAP with a configured MAC address may

incorrectly send CCMs using the port MAC address as the source MAC address
instead of the configured MAC address. The issue will occur if the MEP is actively
sending CCMs and the CCM interval is changed. As a workaround, shut down all
MEPs in the association before changing the CCM interval. This issue was
introduced in Release 9.0.R4. (D.338689-MI)
• In a VPRN hub and spoke setup where NGE is enabled, VPRN OAM packets are
being encrypted as they pass through the hub node. This encryption causes these
OAM packets to be discarded at the spoke nodes because OAM packets are not
expected to be encrypted. This issue was introduced in Release 9.0.R7.
(D.344747-MA)
• A VPRN ping initiated on a 7705 SAR over the CE will time out if the destination IP
address is not the local interface or network address of the subnet. A VPRN trace
will time out when trying to get the last hop (PE interface SAP) information. Note that
a similar issue was resolved in Release 7.0.R6 (as per D.189082) but it was
reintroduced in Release 9.0.R1. (D.285767-MI)

11.3.9 QoS

• In rare cases, the egress queue PIR/CIR of a network port on a 10-port 1GigE/1-port
10GigE X-Adapter card (in either 10-port 1GigE or 1-port 10GigE mode) may be
programmed incorrectly, which may cause unexpected congestion and traffic loss.
(D.330419-MA)

100 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.3.10 System

• A node reboot may occur if a user configures an invalid management IPv6 address
followed by a valid IPv6 address in the BOF. The workaround is to remove the
invalid management IPv6 address first, before adding the valid IPv6 address. This
issue was introduced in Release 9.0.R1. (D.341591-MA)
• Upgrades to any Release 9.0 load between 9.0.R1 and 9.0.R8 will fail if lsr-load-
balancing is configured on an interface in the pre-9.0 configuration file. To work
around this issue, remove any lsr-load-balancing configurations that exist on an
interface before attempting to upgrade. Note that an lsr-load-balancing
configuration under config>system will upgrade properly. See TA 20-0145 for
additional information. (D.347017-MA)

11.4 Release 9.0.R8

11.4.1 Cflowd

• When Layer 3 Cflowd ingress or egress sampling is enabled on a network interface

that is the termination of a GRE tunnel, the 7705 SAR will generate flow reports that
contain IP information from the outer (tunnel) IP header. The flow reports in this
scenario should contain IP information from the inner (customer) IP header.
(D.336135-MA)
• An adapter card will reset if a fragmented packet arrives at a network interface on
that card and both of the following are true:
o ingress Cflowd sampling is enabled on the network interface and it is used for
a GRE tunnel and GRE reassembly is configured
o ingress Cflowd sampling is also enabled on a Layer 3 spoke SDP interface
that is associated with the same GRE tunnel (D.334914-MA)

11.4.2 EVPN-VPLS

• The inactive CSM will reset continuously if VRRP is used with EVPN-VPLS service
with rt=5 and both VRRP instances are configured with the same MAC address.
(D.335361-MA)

Edition: 01 3HE147640011TQZZA 101

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.4.3 GNSS

• If an over-current condition occurs on a GNSS/GPS port, the operational status will

go down. If the GNSS/GPS port is the only configured source of synchronization, this
may cause the System Quality Level to become stuck in the DUS state with an Rx
Quality Level as failed. The workaround is to clear the MDA. Note that after the fix,
the GNSS/GPS port operational status will remain up if an over-current condition
occurs. (D.333977-MA)

11.4.4 GRE

• Egress packets may be corrupted on a GRE SDP if that SDP is doing fragmentation
and if a SAP using that SDP is mirrored or has Cflowd enabled. This issue can occur
on any 7705 SAR platform except the SAR-8 and SAR-18. (D.340179-MA)

11.4.5 IPSec

• When incoming GRE or MPLS tunneled data packets are to be routed in a private
IPSec VPRN through an operationally down IPSec tunnel, this will not trigger the
IPSec tunnel to get re-established as it should. This only occurs if the incoming
tunneled packets are received on a network interface on a non-Ethernet MDA.
(D.337046-MA)
• When a node is busy and there are frequent IPSec tunnel bounces, the 7705 SAR
may incorrectly detect an error condition and raise an alarm similar to the following:
189 2018/12/16 19:32:39.97 CST CRITICAL: LOGGER #2002 Base
A:IPSEC_MGMT:UNUSUAL_ERROR "Slot A: ipsecMgmtGetSAStats7705: Inbound
SA no longer exist." (D.311406-MI)

11.4.6 MPLS

• PLR nodes originating facility FRR tunnels may forward packets with an incorrect
label stack while FRR is active. This only occurs if the merge point is also the tail-
end of the LSP and the tail-end has implicit null enabled under RSVP.
(D.338590-MA)

11.4.7 Multicast

• Multicast traffic will be dropped on a VPLS SAP if PIM snooping is enabled and if the
VPLS SAP is part of a LAG group and the LAG link that it was riding over is shut
down. Traffic will resume when the link is re-enabled. (D.337429-MA)

102 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

• Multicast traffic may be dropped on an r-VPLS SAP if IGMP snooping is enabled and
the r-VPLS SAP is part of a LAG. (D.337853-MA)

11.4.8 OAM

• An adapter card may reset if a Y.1564 test is started on a SAP and the port
associated with that SAP is an ingress mirror source. (D.335652-MA)

11.4.9 QoS

• In rare cases, if multiple Ethernet port configurations are made in quick succession,
including the Ethernet port ingress rate and CBS, a trace error may be raised similar
to the following: "SetIngrRate ERROR. MDA 3 (type 0x9a) - Invalid parameter
rateInMbps=0". If this trace error occurs, the CLI shows the configuration change but
the adapter card is not programmed as intended. If this issue occurs, reset the
adapter card; the configurations will then be properly downloaded. (D.339851,
D.338042-MA)

11.4.10 Segment Routing

• In specific third-party vendor environments with segment routing enabled, the OSPF
neighbor may remain in the Loading state when no adjacency SIDs are received.
(D.337273-MA)

11.4.11 System

• A 7705 SAR-8 CSM switchover will not happen as expected when a certain
hardware fault occurs. In addition, when this fault occurs, a continuous flood of
errors will be seen in the console output similar to the following: “tmSarDubuHandler
called but nothing processed! Status: 0x00000000, Mask: 0x00007FEF, Result:
0x00000000”. To force a CSM switchover, physically remove the faulty CSM.
(D.308247-MA)

11.4.12 VPRN

• Routes resolved to a tunneled next hop are blocked from leaking between VPRNs.
(D.337310-MA)

Edition: 01 3HE147640011TQZZA 103

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.4.13 VRRP

• An ICMP ping to the non-owner VRRP IPv6 backup address will fail even if ping-
reply is enabled. When this issue occurs, the Inv Mcast Addr B* counter will
increment under interface IPv6 discards. A workaround is to add a static routing
entry to that address. (D.335852-MI)
• In rare cases, in a VRRP VPLS or VRRP hub Layer 2 network configuration, the
passive VRRP gratuitous ARP packet for the VRRP backup IP-virtual MAC update
may be missed when bringing up a VRRP instance. To recover, perform a
shutdown and then a no shutdown on the related VRRP instance or IP interface.
(D.335508-MA)

11.5 Release 9.0.R7

11.5.1 1588/PTP

• The combination of an 8-port Ethernet Adapter card v2 as a PTP clock MDA and a
PTP clock source interface with an IPv6 address is not supported. However, this
configuration is not blocked. (D.313373, D.313376)
• Beginning in Release 9.0.R4, an interface cannot be used as a PTP source interface
if that interface gets its IP address via DHCP. (D.315552-MA)

11.5.2 Cflowd

• Configuring Cflowd under the Layer 3 spoke SDP has no effect. Instead, the Cflowd
configuration on the router interface is used to determine whether Cflowd is enabled.
The expected behavior is that the Cflowd configuration on the Layer 3 spoke SDP is
used to determine whether Cflowd is enabled. (D.318487-MI)

11.5.3 DHCP

• DHCP server persistence may be shut down after a power cycle on the following
platforms: 7705 SAR-A, SAR-H, SAR-Hc, SAR-M, SAR-W, or SAR-Wx. While in this
state, the DHCP server will become operational and assign leases and may reuse
leases that had been assigned prior to the power cycle, possibly causing duplicate
IP addresses. In order to recover DHCP persistence and maintain the existing
leases, the system should be reset using the admin reboot command.
(D.327273-MA)

104 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.5.4 Fabric Profiles

• Per-destination fabric profiles may not work as expected for traffic arriving on a SAP
which is destined for a network interface that is part of a LAG group on a first-
generation adapter card.
In addition, a trace error similar to the following may be observed:
"Slot 1: mda_program_sap_enable_disable_setting: FAILED: To set sap
enable/disable setting, sapIndex=4234 that is ENABLE in the INGRESS direction"
(D.317553-MI)

11.5.5 Firewall

• TCP SYN packets are being erroneously dropped when traversing a firewall zone if
the CE flag (CWR and ECE bits) are set. These bits are used for ECN (Explicit
Congestion Notification) and should not cause the packets to be dropped.
(D.325545-MA)

11.5.6 GNSS

• If a 7705 SAR node has two GNSS ports configured to provide system time and
GNSS lock is lost on the GNSS port being used for system time, the system will not
switch to the other port. (D.321276-MA)

11.5.7 Multi-chassis Firewall

• Within a VPRN service, any new multi-chassis firewall sessions created after a CSM
switch on a slave node will have incorrect VRF IDs, resulting in traffic loss for these
new sessions. (D.323273-MA)
• When deleting a large number of policies (approximately 120 or more) from a multi-
chassis firewall master router, the deletion does not get properly synchronized to the
slave router. (D.326208-MA)
• If multiple security policies are created or modified in rapid succession, the
configuration may not get properly synchronized to the multi-chassis firewall slave.
(D.326590-MA)
• Management-plane traffic for a router in a multi-chassis firewall configuration will be
dropped if it is routed through a firewall zone of its peer router. (D.327536-MA)
• Some active UDP sessions may be erroneously removed from a multi-chassis
firewall master router, causing a loss of traffic. This issue may occur when a large
number of UDP sessions with security logging enabled are being synchronized to a
multi-chassis firewall peer that has just come into service. (D.327706-MA)

Edition: 01 3HE147640011TQZZA 105

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

• When the CLI command clear security session all is issued on a multi-chassis
firewall master, all sessions may not get cleared on the slave. (D.327797-MA)
• A memory buffer leak may occur on an adapter card, leading to unpredictable
behavior if that adapter card has a multi-chassis firewall link configured and
encryption is enabled for multi-chassis firewall. (D.327057-MA)
• Multi-chassis firewall policies may fail to synchronize from the master to the slave
after a no shutdown of the multi-chassis peer relationship if the slave had pre-
existing firewall profiles but not policies. (D.328158-MA)
• In rare cases, after multiple master/slave activity switches, it is possible that the
firewall security configuration will be lost. (D.328137-MA)
• If the first packet arriving on a multi-chassis firewall session is a fragmented packet,
only the first fragment is forwarded and the remaining fragments are dropped.
Subsequent fragmented packets are handled correctly. (D.331544, D.323271-MI)

11.5.8 NGE

• ARP request/reply messages are dropped on NGE-enabled Layer 3 spoke SDPs

when any of the following key groups are used: 4 5 12 13 18 19 20 21 22 23 26 27
28 29 30 31 36 37 44 45 50 51 52 53 54 55 58 59 60 61 62 63 68 69 76 77 82 83 84
85 86 87 90 91 92 93 94 95 100 101 108 109 114 115 116 117 118 119 122 123 124
125 126 127
As a workaround, use a key group not included in this list or configure a static ARP
entry under the VPRN interface. (D.331303-MA)

11.5.9 OAM

• In rare cases, an OAM LSP ping/trace originating on an LER node may not follow
the datapath of the LSP under test on the head-end node. (D.207865-MA)

11.5.10 QoS

• If SGT redirection is enabled for an application, all self-generated traffic for that
application is sent as best effort (be). This will only affect the handling of self-
generated traffic if the switching fabric or encryption engine queues are congested.
(D.325144-MI)

11.5.11 Routing

• An ICMP ping will time out and fail when pinging an IP address that is reachable via
an IGP shortcut and IP fragmentation is required. (D.319747-MI)

106 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.5.12 Services General

• LDP transport that could go over RSVP-TE IGP shortcuts is not supported for BGP
3107 SDPs. Layer 2 and Layer 3 services may show as operationally up, but no
traffic will be forwarded. (D.230794)

11.5.13 System

• In rare cases, an adapter card may continuously raise events in log 99 and 100
similar to the following: WDDICSA:UNUSUAL_ERROR "Slot 1:
winpathTs1OffsetSet: ERROR. Block-Read fail”. There are two issues here: first, the
event should be rate-limited so that it does not fill up the event log and second, the
event should include adapter card slot information. If this log event appears for an
adapter card, contact a Nokia support representative for further investigation.
(D.319307-MI)

11.6 Release 9.0.R6

11.6.1 Cpipes

• If Asymmetrical Delay Control (ADC) is configured on a Cpipe and more than two
packet-times worth of delay must be added to the jitter buffer, the delay adjustment
will fail with two possible results:
o the Cpipe will never come into service, with continual overruns and/or
underruns of the jitter buffer observed
o the Cpipe comes into service with an incorrect amount of delay added to the
jitter buffer (D.321626-MA)
• The CLI display for jitter buffer (packets) and playout threshold (packets) might not
be accurate for SAToP T1 Cpipe services. (D.323340-MI)

11.6.2 DHCP

• A DHCP server running on a 7705 SAR may take longer than expected (up to 6 or 7
minutes) to come into service when the 7705 SAR is restarted. (D.325974-MA)

11.6.3 Ethernet

• Pause frames are never sent on the 10Gb ports of the 7705 SAR-X or 6-port
Ethernet 10Gbps Adapter card. (D.321628-MA)

Edition: 01 3HE147640011TQZZA 107

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.6.4 IGMP Snooping

• The adapter cards listed below may reset if they are in a 7705 SAR chassis and
IGMP snooping is enabled on a VPLS service that also has EVPN enabled. The
resets may also happen on a subsequent shutdown/no shutdown of that IGMP
snooping configuration. The affected adapter cards are:
o 4-port OC3/STM1 Clear Channel Adapter card
o 2-port OC3/STM1 Channelized Adapter card
o 16-port T1/E1 ASAP Adapter card v2
o 32-port T1/E1 ASAP Adapter card
o 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card
o 4-port DS3/E3 Adapter card
Note that these cards do not have to be involved with the VPLS service that is being
configured – they just need to reside in the same chassis. (D.323123-MA)

11.6.5 Multi-chassis APS

• If multi-chassis APS is configured with PW redundancy on the 4-port OC3/STM1 / 1-

port OC12/STM4 Adapter card in OC12/STM4 mode, SAPs on the node with the
active APS link on STS3-2 or higher will drop traffic on most configured channels
whereas SAPs on the node with the inactive APS link on STS3-2 or higher will
forward traffic on the standby spoke SDP. (D.316330-MA)

11.6.6 Multi-chassis Firewall

• Sessions on the master and slave may get out of synchronization if multi-chassis
firewall configuration changes are made when there are active sessions. When the
master and slave are out of synchronization, traffic may be affected. To prevent this
issue, perform a shutdown before making configuration changes. To recover, force
both master and slave to be in standalone mode, clear all the security sessions on
both nodes, and then allow one node to be master and the other to be slave.
(D.321360-MA)

11.6.7 Microwave

• If EFM OAM is configured on an Ethernet port and that port is configured as part of a
microwave link, the microwave link will not become operational at boot-up, after an
MDA clear, or if the microwave link state and the port state are both non-operational
and the port state transitions to operational.

108 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

The ignore-efm-state feature has been implemented to allow EFM OAM to be used
with ports in microwave links. When ignore-efm-state is configured on a port, the
EFM protocol continues as normal. However, any failure in the EFM protocol state
will not impact the state of the port or the microwave link. (D.309626-MA)

11.6.8 OAM

• An adapter card may reset unexpectedly when a CFM two-way-delay-test or one-

way-delay-test is executed for a Down MEP on a VPLS SAP. This issue will only
occur if an egress MAC filter is configured on that VPLS SAP such that the CFM
packets that originate from the MEP match the MAC filter criteria. Other CFM tests
such as loopback and linktrace will fail but will not cause an adapter card reset.
As a workaround to allow the CFM tests to work properly, change the MAC filter
configuration such that CFM packets that originate from the MEP do not meet the
filter criteria. (D.320026-MA)

11.7 Release 9.0.R5

11.7.1 IPSec

• The active CSM may reboot when debug ipsec tunnel name detail is enabled and
IKEv2 identification data is exchanged in an IKEv2 message. (D.315043-MA)

11.7.2 Microwave

• If the port MTU of a microwave link is set back to the default value from a non-
default value by either using an SNMP MTU value of 0 or using the no mtu
command in the CLI, the radio link port MTU will be set back to the default value as
expected but a microwave link SAP or SDP on that microwave link port will have its
admin MTU, which is derived from the microwave link port MTU, set incorrectly. For
both the SAP and SDP, the MTU will be smaller than the default port MTU and will
result in the SAP or SDP information under the service showing
“PathMTUTooSmall”.
To recover from this issue, configure the port MTU to a non-default value and then
reconfigure it to the default value using the explicit value through either SNMP or the
CLI (that is, do not use the 0 value or the no mtu command). (D.271945-MI)

Edition: 01 3HE147640011TQZZA 109

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.7.3 OAM

• In very rare cases, configuring TWAMP servers that are waiting for new connections
may lock out Telnet, SSH, and console sessions. (D.258595, D.316260-MA)
• A CFM server MEP configured to use a 10 ms or 100 ms CCM interval does not
generate AIS packets after detecting an error condition. The workaround is to use a
CCM interval of 1 second or greater. This issue was introduced in Release 9.0.R4.
(D.316812-MA)
• A down MEP on a VPLS spoke/mesh SDP that is associated with a TDM network
port will declare a RemoteCCM defect and stop extracting CCM packets if learning is
disabled on the spoke/mesh SDP. Re-enabling learning will not resolve the issue –
the MEP must be reconfigured or the associated MDA cleared. (D.316929-MA)
• CFM two-way-delay-test, loopback, and single-ended-loss-test will not work for a
Down MEP configured on a SAP (Epipe or VPLS) when the associated port is an
ingress mirror source and the associated port is on a 7705 SAR-X MDA (i7-mix-eth)
or on a 6-port Ethernet 10Gbps Adapter card (a6-eth-10G). This issue was
introduced in Release 9.0.R4. (D.317000-MA)

11.7.4 Routing

• When an OSPF designated router (DR) learns various options advertised by

adjacent routers, the DR correctly performs a logical OR function on those options
and returns the result in its LSA responses. However, when these LSAs are
removed from the OSPF database, the DR keeps sending out the original options
without recalculating the value resulting from the OR operation using the new
options. (D.255986-MI)

11.7.5 System

• In rare cases, a 7705 SAR-X or a 6-port Ethernet 10Gbps Adapter card may reset
unexpectedly. This issue may occur when there are a large number of occurrences
of a physical port going in and out of service. (D.316796-MA)
• If MP-BGP traffic hits a CPM filter that has logging enabled, packets are not logged
and an error message similar to the following will appear in the event log: "Slot 1:
displayStdout: MDA 1: [012 15:40:03.276]
wpAdjustLoggedPacketHeaderForSpokeSdp ERROR. MDA 1 (type 0xc3) - Spoke-
Sdp index 4098 is invalid”. (D.317129-MI)

110 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

• A hardware failure detected on the 2-port OC3/STM1 Channelized Adapter card or

the 4-port DS3/E3 Adapter card while the card is booting up may cause the CSM to
reset (both CSMs will reset in a redundant system). The affected card should be
removed or replaced to avoid continuous CSM resets. (D.317874-MA)

11.7.6 T1/E1 Line Card Redundancy (LCR)

• If the T1/E1 LCR working chassis is active and a working chassis reboot is
performed, the protecting chassis does NOT take activity. (D.315015-MA)
• SAP-to-SAP Cpipe services cannot be configured with multi-chassis T1/E1 LCR if
the SAPs are in different LCR groups. These services should be allowed.
(D.315186-MA)

11.8 Release 9.0.R4

11.8.1 1588/PTP

• PTP over IP will not work on the SAR-A, SAR-Ax, SAR-W, SAR-Wx, or SAR-Hc
platforms if the support.tim file does not exist in the same file location as both.tim.
The support.tim file should not be required for these products. This issue only exists
in Releases 9.0.R1, 9.0.R2, and 9.0.R3.
As a workaround, if space permits, download support.tim to the same file location as
both.tim. Refer to TA 19-0281 for details. (D.315554-MA)

11.8.2 BFD

• The 7705 SAR may continually raise alarms similar to the following if unsupported
BFD configurations are made (for example, NP BFD over a Layer 3 spoke SDP
interface):
CRITICAL: LOGGER #2002 Base A:BFD:UNUSUAL_ERROR "Slot A:
bfd_pchip_setup_tx: [A] 492:pchip createBfdSrc failed if_index=257 isrvpls=0
sessionid=1 txIntvl=200"
(D.312704-MI)
• In rare cases (usually due to an unstable network), BFD may be stuck in the Init state
and multiple events similar to the following may appear in log 99: 13695975
2019/01/09 14:22:17.93 IST CRITICAL: LOGGER #2002 Base
A:BFD:UNUSUAL_ERROR "Slot A: bfd_pchip_setup_tx: [A] 358:pbuf NULL while
programming pchip for tx".
Performing a CSM switchover will recover BFD. (D.311414-MA)

Edition: 01 3HE147640011TQZZA 111

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.8.3 BGP

• When bgp next-hop-resolution is configured in the main routing instance, the

default next-hop-resolution configuration is incorrectly also shown with the info
command under VPRN instances. (D.258295-MI)
• When an MVPN-enabled VPRN is created with BGP-based Auto-Discovery (AD),
and the family mvpn-ipv4 BGP peer has outbound-route-filtering configured, the
intra-AS routes will not be advertised until the BGP peer is bounced.
The workaround is to not enable outbound-route-filtering on a family mvpn-ipv4
BGP peer. (D.263627-MI)

11.8.4 Event Handling System (EHS)

• There are two issues with arithmetic operations (addition, subtraction, multiplication,
division) in EHS scripts:
o integer variable multiplication and division are not working
o string variable arithmetic should be blocked and produce an error. Instead, it
is allowed to execute and can lead to unpredictable behavior. (D.299193-MI)

11.8.5 Filter Policies

• A filter log configuration with a scaled number of destination memory entries may fail
to execute after a node reboot due to the scaling limit being reached. (D.257560-MI)

11.8.6 IGMP

• Unnumbered interfaces used with IGMP querier election may cause issues with
forwarding multicast traffic when a loop in the LAN segment causes the query packet
to be looped back to the querier. In this case, multicast traffic resumes again soon
after the loop in the LAN segment is cleared. (D.287255-MI)

11.8.7 IP/RTM

• The debug router ip packet command has been enhanced to display the MTU of
the next-hop interface for ICMP error “type 3: destination unreachable, code 4:
Fragmentation needed”. The actual ICMP packet does contain the MTU of the next
hop. (D.284662-MI)

112 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.8.8 LDP

• Adding and removing IPv6 addresses on an operationally down interface using the
no ipv6 CLI command may result in an LDP:UNUSUAL_ERROR message in the
event log. (D.266146-MI)

11.8.9 Load Balancing

• When an LSR node receives a stream of packets with 11 labels or more, the packets
are not being sprayed over multiple equal-cost paths in a predictable manner,
because hashing is only based on the topmost 10 labels. For proper load balancing
at LSR nodes, it is recommended that networks be limited to packets with 10 labels
or fewer. (D.302692-MA)

11.8.10 OAM

• When the 7705 SAR is the endpoint for a Y.1731 Delay Measurement Test, the
replies originated by the router will have incorrect timestamps if the data TLV size of
the test packets is greater than 193 bytes. (D.314479-MI)

11.8.11 OSPF

• When segment routing is enabled on an OSPF router and an OSPF neighbor is not
in a Full state during a High-Availability switchover, it is possible that the OSPF
router can become unresponsive following the switchover.
A workaround is to clear the OSPF neighbor. (D.254545-MI)
• If a neighbor router changes its next-hop address, the existing BFD session from the
router to its neighbor may stay down indefinitely and the link will no longer be
protected by LFA until BFD configuration of the interface is toggled for OSPF.
(D.289636-MI)

11.8.12 System

• During a CSM boot sequence, accounting files and log files stored on the compact
flash are deleted if they were created 12 or more hours earlier. (D.269385-MI)
• The LEDs on non-Ethernet adapter cards may not restore to their original state after
a lamp test is executed using the ACO/LT (Alarm Cut Off/Lamp Test) button. This is
only a display issue and does not affect the actual status of the ports. Correct LED
operation can be restored by clearing the affected adapter card. (D.282553-MI)

Edition: 01 3HE147640011TQZZA 113

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

• When a system synchronization timing reference source-port is configured to use

an adaptive T1 port, QL Override is incorrectly blocked for SONET SSM values and
permitted for SDH SSM values. This is not an issue when the reference source-port
is an adaptive E1 port. (D.307882-MI)
• An alarm similar to “Slot 1: csaEthXcmFxWpPortGetLinkStatus: port 1/5/7: PHY
failed to init” may be raised continuously in the event log if a bad copper SFP is
installed in a port. With the fix, the alarm will only be raised once. (D.311765-MI)
• Unstable network synchronization may result in a 7705 SAR’s internal clock being
incorrect. As a result, ICMP ping reply times may be erroneously displayed as zero
or large values. In addition, if PTP is used for system time, it may result in an
incorrect node time.
To recover, reset all adapter cards on the affected node. (D.302254-MA)

11.8.13 VRRP

• The system incorrectly allows users to delete a LAG port associated with a VRRP
policy. If the configuration is saved in that state, it will fail to execute after a node
reboot. (D.277557-MI)

11.9 Release 9.0.R3

11.9.1 1588/PTP

• If a source interface is configured against an IP PTP clock and the clock type is
changed to transparent, the system will continue to associate the interface with the
clock although it should not. As a result, the user will be blocked from deleting that
interface. If this issue occurs, in order to be able to delete the interface, the PTP
clock must be reconfigured as an IP clock with that source interface and then
deconfigured. (D.307233-MI)
• On a 1588 boundary clock, when a peer address is moved to another PTP port,
leaving the first PTP port unused, the new PTP port will be stuck in the initialization
state and will not request any announce packets to the peer.
As a workaround, use the first available PTP port to assign a peer IP address on a
boundary clock. (D.309885-MA)

114 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.9.2 2-port OC3/STM1 Channelized Adapter Card

• In previous releases, the following unsupported encapsulation types could be

configured for clear channel DS3 channels on a 2-port OC3/STM1 Channelized
Adapter card (a2-choc3): atm, ipcp, and frame-relay. These encapsulation types
are now blocked. (D.308244-MI)

11.9.3 CLI

• Adding a static IPv6 route 0::/64 in the BOF removes other static IPv6 routes from
the show bof output display. These routes are actually still present in this case;
therefore, this is only a display issue. (D.273905-MI)

11.9.4 IPSec

• If an SDP is in a no shutdown state and a VLL service is using static VC labels and
IPSec tunnel transport and that IPSec tunnel has not currently resolved a route to
the peer gateway, the SDP operational MTU will remain at 0 even after the IPSec
tunnel has resolved a route to the peer. The VLL service will not become active, and
if IPSec IKE is used, the VLL traffic will not bring up the IPSec tunnel.
A preventive workaround is to explicitly set the SDP path MTU. If IPSec IKE is used,
the issue can also be avoided by using IPSec auto-establish. (D.308488-MA)
• If a dynamically keyed IPSec tunnel is being used for GRE VLL transport and that
IPSec tunnel is using anti-replay and ECMP is being used with multiple IPSec public
side uplink interfaces that are spread across different MDAs, the IPSec tunnel may
continuously rekey, which will result in degraded performance. (D.310512-MI)

11.9.5 MPLS

• An RSVP-TE LSP will not go down as expected if a static route that is used to
resolve a hop defined in the path is no longer active. This only occurs if the LSP is
signaled prior to a high-availability switchover.
A workaround is to resignal LSPs that use static routes to resolved hops after a high-
availability switchover. (D.250639-MI)
• In certain scenarios, after an RSVP-TE interface using IS-IS traffic engineering has
bounced due to a port flap, it may incorrectly not be considered for CSPF
calculation.
A workaround to recover from this condition is to bounce the port or interface again.
(D.280088-MI)

Edition: 01 3HE147640011TQZZA 115

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.9.6 Multicast

• The OIF list may be missing some multicast groups after an MDA reset is performed.
This issue will only occur on LAG interfaces on a 7705 SAR-M or SAR-H.
(D.309136-MA)

11.9.7 NGE

• When NGE is enabled on a VPRN and GRT leaking is configured to provide IP

reachability from the VPRN to the GRT (for remote system management through the
VPRN, for example), packets coming from the GRT to the VPRN are unencrypted
and are therefore discarded at the receiving end of the VPRN. (D.307256-MA).

11.9.8 OAM

• In rare cases, egress port mirroring of packets with SR-TE labels may lead to
corruption of those packets as they egress the port. (D.303553-MA)

11.9.9 PIM

• In rare cases, when the spt-switchover-threshold is set to infinity or to a value

much higher than the actual (S,G) rate, multicast data traffic may be copied to the
CSM indefinitely until the (S,G) record is removed from the PIM database.
The workaround is to clear the whole PIM database. (D.251481-MI)

11.9.10 Routing

• A static neighbor entry may be erroneously deleted from the IPv6 neighbor database
after two or more CSM switches. (D.276583-MA)
• When several hundred ARP entries simultaneously become stale, some entries may
not be refreshed and may age out. This causes the router to broadcast an ARP or
ND request for the IP address. (D.244830-MI)
• Adding an additional next hop to a static route prefix may fail and result in the error
“INFO: PIP #1407 The object already exists” if both of the following have occurred
prior to adding the new next hop:
o deletion of a next hop for that same prefix
o high-availability switchover
A workaround is to completely remove the static route prefix and reconfigure it with
all required next hops. (D.249311-MA)

116 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

• When a prefix is present in the route table, both as an aggregate route and as a local
or IGP route, with the aggregate route being the active route, this prefix is incorrectly
not advertised as a FEC if the aggregate route was present in the route table before
the local or IGP route was present. (D.263376-MI)
• When translating from type 7 to type 5 LSAs with a zero metric value, the OSPF
External Metric Type incorrectly changes from E2 to E1.
A workaround is to not use a zero metric value. (D.274578-MI)
• If an interface is added to IS-IS and is administratively disabled in the same SNMP
set request, the standby CSM resets. Nokia recommends performing these actions
in separate SNMP set requests. (D.283090-MI)
• The OSPFv3 NSSA default route is incorrectly advertised as type 1 instead of type
2. (D.292596-MI)

11.9.11 System

• In very rare cases, a 7705 SAR-A, SAR-Ax, SAR-Hc, SAR-W, SAR-Wx, or SAR-X
may reboot during an FTP download if certain third-party FTP clients are used.
(D.295938-MA)

11.10 Release 9.0.R2

11.10.1 1588/PTP

• When a PTP ordinary slave clock is created with only peer 2 configured, the peer will
not be discovered and the PTP port will stay in the initialized state. There is no
workaround to this issue, although configuring a peer 1 will stop the problem from
occurring. (D.307877-MA)

11.10.2 BFD

• In rare cases, a BFD-associated static route may go operationally down after a CSM
switch. To recover, disable and re-enable BFD on that static route. (D.300979-MA)

11.10.3 BGP

• A BGP 3107 route with an explicit-null label learned from a directly connected EBGP
peer causes CSM-originated traffic destined for that route to not be forwarded
correctly. A workaround is to configure the EBGP peers to not use explicit-null
labels. (D.258972-MA)

Edition: 01 3HE147640011TQZZA 117

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

• A route reflector (RR) may withdraw a route or not reflect an update to a route if the
“invalid” flag is set in the RIB-In. Receiving an update while rapid-withdrawal is
configured will cause a withdrawal when a route was previously invalid and
advertised. Without rapid-withdrawal, an update to an invalid but advertised route
does not regenerate updates to reflect the received update. (D.263409-MA)

11.10.4 CLI

• CLI rollback may fail if there are changes to an IPSec policy with active tunnels.
(D.254625-MA)
• A rollback compare between a rescue configuration and the active-cfg will fail if no
rollback-location is configured. The compare should work; only a rescue-location
should be required. (D.284559-MI)
• An evpn-tunnel configuration is erroneously allowed under the config>service>
vprn context. This configuration is not currently supported. (D.303080-MI)

11.10.5 DHCP

• Directed broadcast DHCP Inform packets are not relayed on a DHCP relay enabled
interface. These packets should be enabled. (D.254196-MA)
• If the local-dhcp-server has a lease populated for a particular DHCP client and
receives a broadcast DHCP Request whereby a different client IP address from
another server address (option 54) is selected, the local-dhcp-server incorrectly
replies with a DHCP NAK. Although the DHCP NAK reply contains the correct option
54, it may conflict with some DHCP client implementations. (D.294904-MI)
• Valid DHCPv6 packets that arrive with extra bytes at the end of the packet that do
not belong to the IP payload are erroneously dropped with a reason of incorrect UDP
checksum calculation. (D.301544-MI)

11.10.6 Ethernet

• To minimize the impact of D.170430 (see Known Limitations), a software change

has been made such that the total Output Error count under show port will no
longer include late collisions for first-generation Ethernet adapter cards only (these
are the only adapter cards affected by D.170430). (D.298724-MI)

118 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.10.7 Filters

• If an ip-filter entry entry-id log log-id is configured while a filter log log-id is in a
shutdown state, matching packets on this entry may still be incorrectly forwarded to
the CSM for logging. (D.286095-MI)

11.10.8 GRE Over IPSec

• The operating MTU of a GRE over IPSec SDP will not take effect when the network
port MTU is changed. In order for the newly configured MTU to take effect, the
operator must perform a shutdown/no shutdown of the IPSec tunnel.
(D.301849-MA)

11.10.9 IPSec

• When using IKEv1 tunnels, the system expects to receive the DPD capability in the
first message from the peer. Some vendors send the DPD in the second message,
which results in DPD functionality being disabled on the 7705 SAR but enabled on
the peer side. In the absence of ESP traffic, DPD may time out on the peer side,
bringing down the tunnel. (D.280966-MI)

11.10.10 Microwave

• The 7705 SAR may erroneously report that an attached microwave radio is in Tx-
mute when the microwave link comes into service. This issue will only occur for
microwave links that are in a LAG group. (D.301994-MA)
• A microwave link on a Packet Microwave Adapter card port in Single NE mode may
remain operationally down after the adapter card comes into service. To recover
from this situation, perform a shutdown/no shutdown of the affected port.
(D.291246-MA)
• MCT sessions via a 7705 SAR to an attached MPR-e radio in Single NE mode are
unreliable. They may fail to establish, or they may time out after being established
and drop. (D.298932-MA)

11.10.11 MPLS

• When BOF persist is enabled, using a space character in the name of a static LSP
may result in a failure to execute the configuration file after a node reset due to an
index file error. (D.273811-MI)
• The show router rsvp interface command displays an incorrect total bandwidth
value when the interface is out of service. (D.286096-MI)

Edition: 01 3HE147640011TQZZA 119

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

• If a 7705 SAR receives an RSVP PATH message with the node-id flag set in the
first sub-object of the route record object (RRO), the node-id flag is incorrectly set to
correspond with its interface IP in the RRO of the corresponding RESV message.
This may cause interoperability issues with other vendors’ routers. (D.304787-MA)

11.10.12 Multicast

• Multicast traffic received on an interface will be forwarded back out the same
interface under the following conditions:
o there is an IGMP group (S,G) on that interface
o that interface is configured as a PIM interface
o traffic for that (S,G) group arrives on that interface, and
o the traffic passes the PIM RPF check
If the interface is on a Layer 2 LAN, duplicate traffic may be seen on other interfaces
attached to that LAN. (D.229473, D.302555-MA)

11.10.13 OAM

• A MEP created on a spoke SDP will not transmit CCMs if the spoke SDP is on a
LAG and the primary link of the LAG is down. This issue only exists in Release
9.0.R1. (D.276824-MA)

11.10.14 Routing

• Removing the last entry in the last policy-statement under the config>router>
policy-options context without executing a commit or abort command will prevent
the standby CSM from synchronizing with the active CSM after a reset of the
standby CSM. The standby CSM will stay in the “syncing/standby” state until a
commit or abort command is executed. (D.275666-MI)
• When segment routing (SR) is enabled on an SR-capable node, “SID not in range”
log events might appear on a different, non-SR node as a result of an LFA, R-LFA,
and/or TI-LFA backup next-hop calculation. (D.289884-MI)
• A system reboot may occur on a 7705 SAR-H, SAR-Hc, SAR-Ax, SAR-X, SAR-W, or
SAR-Wx when using an SR-TE LSP with nine or more labels in the label stack for an
SDP binding that has NGE and control word enabled, and the system sends CFM
OAM self-generated packets on an Epipe service. (D.302213-MA)
• OSPF running in a VPRN instance does not export a BGP-VPN route if an AS
external LSA for the same prefix is received from a CE router and then withdrawn. It
is expected that when the AS external LSA is withdrawn, OSPF will generate a
summary LSA for the exported BGP-VPN route.

120 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

This issue is only observed if the external-preference of OSPF running in the VPRN
is set to a higher value than BGP-VPN. (D.297453-MI)

11.10.15 R-VPLS

• An MDA may reset if a high rate of packets are routed into an r-VPLS interface and
are fragmented but are subsequently discarded due to the egress port going down.
(D.304713-MA)

11.10.16 SDIv3

• The output clock provided to the connected DTE device when a DCE RS-530 port is
configured for speeds ≥ 2M slave clock source may not be accurate at all
temperatures. As a result, bit errors may be seen at extreme temperatures at these
speeds. (D.306174-MA)

11.10.17 System

• SSH clients reporting version 1.99 will open an SSH version 2 connection as
expected. However, the connection will be incorrectly displayed as a version 1
connection in the CLI output of show users and show system security ssh.
(D.267717-MI)
• A false alarm will be raised in the event log if a 0.0.0.0/1 static route is configured.
The false alarm will be similar to: Fatal FIB_STATUS_IPV4_DP_LOOKUP_FAULT
Error Detected. (D.303735-MI)
• A SyncE source on a 7705 SAR-Ax may unexpectedly become unqualified, which
could cause system synchronization to go into the holdover state. This issue will only
occur if either port 1/1/3 or 1/1/4 is used as a SyncE source. The workaround to
avoid this problem is to use any port other than 1/1/3 or 1/1/4 on the SAR-Ax as a
source of synchronization. (D.298018-MA)
• All MDAs may reset on a 7705 SAR-Ax, SAR-H, SAR-Hc, SAR-W, SAR-Wx, or
SAR-X when running mirrored traffic on ports with ETH-CFM packets over a GRE
SDP tunnel that has NGE enabled. (D.334078, D.302213-MA)

11.10.18 VPRN

• For ICMP ping messages originated by the CE that are destined for another VPRN
interface learned from a BGP VPN route leak within the same PE, unexpected ICMP
redirect messages may be generated by the local VPRN. (D.261927-MI)

Edition: 01 3HE147640011TQZZA 121

Resolved Issues 7705 SAR 9.0.R11 Software Release Notes

11.11 Release 9.0.R1

This is the first release of 7705 SAR 9.0.

The following issues have been resolved in 9.0.R1 relative to 8.0.R11.

11.11.1 BGP

• In some cases, when a PE has been configured to send BGP ORF updates for
extended communities, if changes are made to policies that affect route-target
extended communities that are used to import BGP-VPN routes into local VPRNs,
ORF updates may be sent by the PE with the incorrect route-target list. This may
affect how routes are advertised by the receiving PE or a route reflector, and how
the received routes are imported into local VPRNs. (D.276450, D.282326-MA)

11.11.2 CLI

• The admin>rollback>compare command may take a long time to complete or may

fail unexpectedly for a TACACS+ user. (D.308518-MI)

11.11.3 IPSec

• In rare cases, the IPSec SAs in positions 2 to 16 may not establish correctly on
some tunnels when establishing a large number of tunnels with IKE version 1 main
mode and multiple security policies per tunnel. A preventive workaround is to enable
auto-establish on one side. If the problem occurs, it can be resolved by toggling the
administrative state of the affected tunnels, causing them to rekey. (D.239308-MA)

11.11.4 IS-IS

• If an IS-IS node receives new IS-IS LSP fragments and the Link Information TLVs
have moved to a different fragment than earlier sets of LSP fragments, in rare cases,
the Link Information might not be correctly populated in the Traffic Engineering
database. This may cause a routing inconsistency corresponding to that link.
(D.258564-MA)

11.11.5 MPLS

• The default MPLS FRR method is one-to-one. However, if FRR is disabled and re-
enabled, the default will change to facility. (D.300202-MI)

122 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Resolved Issues

11.11.6 VPRN

• A CE route may not be withdrawn through MP-BGP as expected. This will occur
when the CE route is deleted from the VRF route table and there is a less-preferred
route that becomes active but the newly active route is rejected by the VRF export
policy. To withdraw the CE route, the VRF export policy must be removed and then
added back or the VRF export policy must be modified to allow and then deny the
less-preferred route. This condition also exists when there is a static blackhole route
that becomes active in the VRF table. (D.310286-MI)
• When routes are locally leaked between VRFs, some interfaces of the adjacent VRF
become unreachable from a local VRF even though routes are populated in the local
VRF’s routing table. Only the first few interfaces created in order of configuration on
the adjacent VRF will be reachable. (D.314595-MI)

Edition: 01 3HE147640011TQZZA 123

Known Issues 7705 SAR 9.0.R11 Software Release Notes

12 Known Issues
The following are specific technical issues that exist in this release. Please also consult the Known
Limitations section, as some known issues may have been moved to that section.

Note: Bracketed ( ) references are internal tracking numbers.

Issues marked as MI have a minor impact and will not disturb network
traffic.
Issues marked as MA may have a major impact on the network and may
disturb traffic.
Issues marked as CR are critical and will have a significant impact on the
network.

Note: Known issues that have been added in this release are marked as
[NEW].

12.1 1588/PTP

• When using 10M links on BC/TC/Slave, the 1PPS output will give a time error of
500 ns more as compared to using 100/1000M links. This issue applies to the 7705
SAR-A and 7705 SAR-W. (P.657254-MI, D.170630-MI)
• PTP packet loss is seen on the 7705 SAR when it is a slave to a TP5000 acting as a
2-step master clock. The packet loss rate is typically 1 or 2 packets/s at a 64 PPS
rate, but it does not affect the PTP frequency or phase recovery of the node.
(D.194414-MA)
• The 7705 SAR may not properly select the higher-priority reference for system
time. This issue will only occur if PTP is given a higher priority (that is, a lower value
for time-ref-priority) than GPS. This is not an expected configuration.
(D.194853-MA)

12.2 2-port 10GigE (Ethernet) Adapter Card/Module

• On the 2-port 10GigE (Ethernet) Adapter card and 2-port 10GigE (Ethernet) module,
when port 1 or port 2 goes down while sending or receiving large packets (larger
than 2106 bytes) destined for port 3/virtual port, all traffic to and from port 3 may
stop. When the port recovers, traffic will recover as well. (D.181396-MA)

124 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Known Issues

12.3 4-port OC3/STM1 / 1-port OC12/STM4 Adapter Card

• Setting trace-string zeros on an 4-port OC3/STM1 / 1-port OC12/STM4 Adapter

card STS3 or STS1 path results in a string of 62 bytes containing “00” and ending
with “0d0a” to make up a 64-byte string being sent out. A string of 64 bytes of “00” is
expected. The 4-port OC3/STM1 / 1-port OC12/STM4 Adapter card also does not
display a received J1 string of all “00s”. (D.184328-MI)

12.4 Active/Active LAG on Access

• Y.1564 tests may fail when the originating SAP is on an Active/Active LAG with
multiple ports. The test payload is sent on the primary port of the LAG. Depending
on the payload, the packets may return on a different port and not be processed by
the CSM. (D.255974-MA)

12.5 ATM

• A 4-port OC3/STM1 Clear Channel Adapter card may reset due to a bus error if the
ATM-TD profile parameters are modified. This issue will only occur if there are more
than two VPLS ATM SAPs configured on the card and those SAPs are experiencing
congestion on SAP egress when the configuration change is made. (D.329520-MA)

12.6 BGP

• Prior to Release 9.0, forwarding for a /32 label-IPv4 route that was originated by
exporting a static route into BGP would have been successful if there was a tunnel to
the destination of the /32 route. Starting in Release 9.0.R1, the packets will be
dropped. This is not an issue for OSPF or IS-IS routes. (D.235489-MA)

12.7 DHCP

• When a routing interface on the 7705 SAR has been configured and an IP address
has been assigned by a DHCP server, it is expected that if the interface is
deconfigured, a DHCP RELEASE message will be sent to the DHCP server;
however, no RELEASE message is sent. (D.209437-MA)

12.8 DSL

• Occasionally the xDSL port on the SAR-M 8-port xDSL module does not come up.
To recover, perform a shutdown/no shutdown on the port again. (D.178266-MA)

Edition: 01 3HE147640011TQZZA 125

Known Issues 7705 SAR 9.0.R11 Software Release Notes

12.9 Ethernet

• The status LED of an administratively down port may indicate LINK UP (green) if the
far-end port is administratively up. Also, if the SFP Tx is down but Rx is still up, the
port state will report UP. (D.209151-MI)
This issue only occurs at 100M speeds when using the 3HE04117AA, 3HE05164AA,
and 3HE09500AA SFPs.
The port state of UP when the SFP Tx is down occurs on all Ethernet ports.
The LED issue only occurs on the following:
o SAR-H
o SAR-M
o 6-port SAR-M Ethernet module
o 8-port Ethernet Adapter card v2
Note: 3HE09500AA only applies to R7.0. The other two SFPs apply to all releases.

12.10 EVPN

• Broadcast, Multicast, and Unknown (BMU) traffic within an EVPN may be discarded
if router ecmp is enabled and the EVPN ECMP transport tunnel next hops are
reachable via different MDAs. (D.336634-MA)

12.11 Filters

• Packets captured by filters may show an incorrect src-mac value. This issue may
occur for IP filters configured on VPRN/IES spoke-SDP terminated interfaces or for
CPM filters on VPRN/IES spoke-SDP terminated interfaces or VPRN services.
(D.320432-MI)
• Adapter cards that do not support large tables may continuously reset or behave
unpredictably under certain configurations that involve scaled numbers of IPv6 filter
entries. To prevent this issue, these adapter cards should limit the number of filter
entries to 16 or fewer. If more than 16 entries are used for a filter, the above issues
may occur. (D.353484-MA) [NEW]

12.12 Frame Relay

• If the 7705 SAR is configured for rev.1 LMI, when the 7705 SAR sends two back-to-
back LMI messages (for example, LINK_INT_VERIFY, PVC_ASYNC_STATUS), the
next message received back from the far end is discarded as Inv. RxSeqNum
message. (D.208933-MA)

126 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Known Issues

12.13 G.8032

• Traffic outages as a result of Ethernet Ring protection switching may be higher than
the norm if a failure occurs in a link not directly connected to the RPL owner or
neighbor. As a workaround, the RPL neighbor should not be configured.
(D.307225-MI)
• Traffic outages as a result of Ethernet Ring protection switching may be higher than
the norm if the failure is detected by CFM continuity check messages.
(D.317046-MA)

12.14 IPv4 ACL Filter

• Using certain wildcards on four or more IPv4 ACL filters (0.0.0.x as netmask) will
cause critical errors on adapter cards when the filter is applied. Subsequently, any
newly added IPv4 filter will not work. The configuration should be removed and the
adapter card cleared to recover from the problem.
In this release, the following adapter cards and platforms are not affected:
o 10-port 1GigE/1-port 10GigE X-Adapter card v1
o 10-port 1GigE/1-port 10GigE X-Adapter card v2
o 8-port Gigabit Ethernet SFP Adapter card v2
o 8-port Gigabit Ethernet SFP Adapter card v3
o 2-port 10GigE (Ethernet) Adapter card
o 6-port Ethernet 10Gbps Adapter card
o SAR-X
(D.188152-MA)

12.15 Load Balancing

• Traffic received on a network port (with dot1q encapsulation) over a GRE SDP is all
expected to be sent over a single egress LAG member when all the fields in the
received packets (MAC SA/DA, IP Src/Dest address, and so on) are constant.
However, the traffic is actually being sprayed across multiple egress LAG members,
which could potentially cause out-of-order traffic at the service endpoint.
(D.301351-MA)

12.16 LSP Statistics

• If a clear mda command is issued immediately after clearing router MPLS LSP
statistics, LSP statistics counters may be corrupted, showing a very large number.
(D.335239-MA)

Edition: 01 3HE147640011TQZZA 127

Known Issues 7705 SAR 9.0.R11 Software Release Notes

12.17 MPLS

• If the one-to-one option is configured in fast-reroute, when one detour is merged

into another detour, there is currently no check that the avoid node of the merging
detour is not in the path taken by the detour into which it is merging. If a detour is
erroneously merged into another detour that transits through the avoid node of the
merging detour, the result is a loop. If a network event activates a detour along this
loop, the result is stale RSVP sessions on the nodes within the loop but the LSP
itself will go down. (D.287785, D.337810-MI)

12.18 Multicast

• An mtrace will fail if the destination address is more than one hop away.
(D.237228-MA)

12.19 Multi-chassis Firewall

• FTP and TFTP traffic will be dropped by a multi-chassis firewall slave router.
(D.323271-MA)

12.20 OAM

• A Down MEP configured on a spoke/mesh SDP (Epipe/VPLS) does not work when
the SDP is configured to use GRE over IPSec over a public VPRN. An Up MEP
configured on a SAP on the same service can be used as a workaround.
(D.320874-MA)

12.21 OSPF

• Loose-hop LSPs are not resignaled if a new equal-cost path becomes available.
(D.17494-MI)

12.22 Packet Byte Offset

• If packet byte offset is enabled on an ingress queue, the received packet size is
calculated as larger than it should be (typically by 28 bytes) for firewall strict TCP
sessions. (D.220721-MI)

128 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Known Issues

12.23 PIM-SM

• On the 7705 SAR-X, if there are more than 254 multicast sources simultaneously
sending traffic to (*,G), some PIM prune messages to the RP may be ignored. As a
result, some (S,G) tree OIFs on the RP node may not get pruned.
In the GRT case, the lost PIM-prune messages will result in the receipt of the same
(S,G) traffic from both the source and RP.
In the MVPN case, traffic is only received from the source, but the (S,G) OIF shows
otherwise. If the PIM interface MTU is 9724 bytes, there is no problem.
(D.261994-MA)

12.24 QinQ

• CPE pings to a VPLS service will fail if the VPLS SAP is on a port that is configured
as QinQ and with a non-default Ethertype (that is, NOT 0x8100). (D.181586-MA)

12.25 QoS

• An MSS unshaped shaper group may not get its fair share of CIR bandwidth when
competing with an MSS shaped shaper group. This issue will only occur with MSS. It
will also only occur when there are a small number of unshaped Layer 3 queues
(generally fewer than four). (D.221417-MA)
• A VLAN tagged packet egressing a SAP configured with a dot1q encapsulation type
and VLAN 0 will have its dot1p bits re-marked if a re-marking policy is applied to that
SAP. The dot1p re-marking should not be happening when an egress SAP is
configured with dot1q encapsulation and a VLAN of 0. (D.229668-MI)
• Self-generated traffic egressing a 7705 SAR from the management port with the
RST flag set and a window size of zero is not marked as per the SGT-QoS settings
but is instead marked as NC1. This issue only occurs if the default SGT-QoS
configuration is used. (D.220991-MI)

12.26 Routing

• An ICMPv6 type 4 code 1 error message is not generated in response to a packet

with an unrecognized next header type that is received on an interface within a
VPRN service. (D.267676-MI)
• If a node that is in the TI-LFA path reboots or an interface is bounced, TI-LFA
backup paths may not be calculated until a new OSPF event causes the TI-LFA SPF
to be triggered. As a workaround, a manual SPF can be triggered to fix this issue.
(D.342312-MA)

Edition: 01 3HE147640011TQZZA 129

Known Issues 7705 SAR 9.0.R11 Software Release Notes

• The no ipv6 command is blocked in the CLI if there are any static IPv6 neighbors
configured. To work around this issue, remove all static IPv6 neighbors before
issuing the no ipv6 command. (D.349137-MI)

12.27 SAR-Wx DSL Variants

• Upstream traffic on a 7705 SAR-Wx xDSL port is sent over all DSL lines that are in
showtime, even if they are not bonded in a bonding group. The traffic sent over the
unbonded lines is lost. This condition may arise due to bonding misconfiguration at
the CO where some lines could be enabled but not bonded in the group.
(D.183448-MA)

12.28 System

• Memory is consumed and not freed up when there is a failed attempt to collect a TS
file. A failed attempt may occur if the compact flash is full, if the TS file is write-
protected, or if the destination directory is nonexistent. In such cases, an error
similar to “Could not open <file>” is displayed. The CLI command show system
memory-pools can be used to monitor management memory. Lost memory can be
freed up by performing a High Availability switchover. (D.347089-MI) [NEW]

12.29 TWAMP

• From time to time (approximately every 8 hours), the T2 timestamp value is

corrupted for a couple of packets when using PPP or MLPPP links. As a result, the
total network delay becomes a very large negative value. This issue affects all
T1/E1, OC3/STM1, DS3/E3, and channelized OC3/STM1 interfaces on all 7705 SAR
platforms and adapter cards, when they are used to provision routing interfaces.
(P.638922, D.170343-MI)

130 3HE147640011TQZZA Edition: 01

7705 SAR 9.0.R11 Software Release Notes Release Load History

13 Release Load History

Released Load Date Reason for Issue
7705 SAR 9.0.R1 28 September 2018 Release Notes for load R1 of Release 9.0
7705 SAR 9.0.R2 28 November 2018 Release Notes for load R2 of Release 9.0
7705 SAR 9.0.R3 30 January 2019 Release Notes for load R3 of Release 9.0
7705 SAR 9.0.R4 3 April 2019 Release Notes for load R4 of Release 9.0
7705 SAR 9.0.R5 29 May 2019 Release Notes for load R5 of Release 9.0
7705 SAR 9.0.R6 6 August 2019 Release Notes for load R6 of Release 9.0
7705 SAR 9.0.R7 30 October 2019 Release Notes for load R7 of Release 9.0
7705 SAR 9.0.R8 29 January 2020 Release Notes for load R8 of Release 9.0
7705 SAR 9.0.R9 25 March 2020 Release Notes for load R9 of Release 9.0
7705 SAR 9.0.R10 3 June 2020 Release Notes for load R10 of Release 9.0
7705 SAR 9.0.R11 15 July 2020 Release Notes for load R11 of Release 9.0

Edition: 01 3HE147640011TQZZA 131