7705 SAR OS 6.1.R7 Software Release Notice

Alcatel-Lucent 7705
SERVICE AGGREGATION ROUTER | RELEASE 6.1.R7

RELEASE NOTES | MARCH 25, 2015
3HE086790007TQZZA_01
Alcatel-Lucent Proprietary
This document contains proprietary information of Alcatel-Lucent and is not to be disclosed
or used except in accordance with applicable agreements.
Copyright 2014-2015 Alcatel-Lucent. All rights reserved.
7705 SAR OS 6.1.R7 Software Release Notes
TABLE OF CONTENTS
RELEASE 6.1.R7 DOCUMENTATION SET ............................................................ 3
RELEASE 6.1.R7 SUPPORTED HARDWARE .......................................................... 5
SUPPORTED MPR-e RADIOS (7705 SAR + MPR-e SINGLE NE MODE) .......................... 12
SUPPORTED MPR-e RADIOS .............................................................. 12
SUPPORTED MPR-e SOFTWARE .......................................................... 12
NEW FEATURES IN RELEASE 6.1.R7 ............................................................. 13
HARDWARE ................................................................................. 26
SYSTEM ..................................................................................... 28
SERVICES ................................................................................... 31
QUALITY OF SERVICE ..................................................................... 31
ROUTING ................................................................................... 31
MPLS ........................................................................................ 33
OAM ......................................................................................... 34
SYNCHRONIZATION ....................................................................... 34
LICENSES ................................................................................... 34
UNSUPPORTED FEATURES ON THE 7705 SAR ................................................... 37
ENHANCEMENTS ..................................................................................... 38
RELEASE 6.1.R7 ........................................................................... 38
RELEASE 6.1.R6 ........................................................................... 38
RELEASE 6.1.R5 ........................................................................... 38
RELEASE 6.1.R4 ........................................................................... 39
RELEASE 6.1.R3 ........................................................................... 39
RELEASE 6.1.R2 ........................................................................... 39
RELEASE 6.1.R1 ........................................................................... 39
USAGE NOTES ....................................................................................... 41
SOFTWARE UPGRADE PROCEDURES .............................................................. 46
SOFTWARE BUNDLES ..................................................................... 46
SOFTWARE UPGRADE NOTES ............................................................ 48
ISSU UPGRADE PROCEDURE ............................................................. 51
STANDARD SOFTWARE UPGRADE PROCEDURE ........................................ 55
CONTROL AND SWITCHING MODULE: CSMv1 to CSMv2 MIGRATION ......................... 62
KNOWN LIMITATIONS ............................................................................... 63
RESOLVED ISSUES ................................................................................... 79
RESOLVED IN R6.1.R7 .................................................................... 79
RESOLVED IN R6.1.R6 .................................................................... 80
RESOLVED IN R6.1.R5 .................................................................... 83
RESOLVED IN R6.1.R4 .................................................................... 84
RESOLVED IN R6.1.R3 .................................................................... 86
RESOLVED IN R6.1.R2 .................................................................... 88
RESOLVED IN R6.1.R1 .................................................................... 91
RESOLVED IN R6.1.B1-8 .................................................................. 93
KNOWN ISSUES ...................................................................................... 95
RELEASE LOAD HISTORY ........................................................................... 98
CHANGE HISTORY FOR RELEASE 6.1 RELEASE NOTES ......................................... 99
Alcatel-Lucent
3HE086790007TQZZA_01
RELEASE 6.1.R7 DOCUMENTATION SET

The 7705 SAR documentation set for this release consists of the documents listed
in Table 1.
Table 1. 7705 SAR Documentation Set
Alcatel-Lucent Part #
Guide
3HE08639AAACTQZZA_01
7705 SAR 10-port 1GigE / 1-port 10GigE X-Adapter Card

Installation Guide
7705 SAR 2-port 10GigE (Ethernet) Adapter Card/Module

Installation Guide
7705 SAR 4-port T1/E1 & RS-232 Combination Module

Installation Guide
7705 SAR 6-port E&M Adapter Card Installation Guide
7705 SAR 6-port FXS Card Installation Guide
7705 SAR 8-port FXO Card Installation Guide
7705 SAR 8-port Voice & Teleprotection Card Installation

Guide
7705 SAR Auxiliary Alarm Card Installation Guide
7705 SAR CWDM OADM Adapter Card/Module Installation

Guide
7705 SAR DS3/E3 Adapter Card Installation Guide
7705 SAR DSL Module Installation Guide
7705 SAR Ethernet/Gigabit Ethernet Adapter Card

Installation Guide
7705 SAR GPON Module Installation Guide
7705 SAR GPS Receiver Module Installation Guide
7705 SAR Integrated Services Card Installation Guide
7705 SAR OC3/STM1 Adapter Card Installation Guide
7705 SAR Packet Microwave Adapter Card Installation Guide
7705 SAR Power Injector Card Installation Guide
7705 SAR Serial Data Interface Card Installation Guide
7705 SAR T1/E1 ASAP Adapter Card Installation Guide
7705 SAR-18 Chassis Installation Guide
7705 SAR-8 Chassis Installation Guide
7705 SAR-A Chassis Installation Guide
7705 SAR-F Chassis Installation Guide
7705 SAR-H Chassis Installation Guide
7705 SAR-Hc Chassis Installation Guide
7705 SAR-M Chassis Installation Guide
Alcatel-Lucent
3HE086790007TQZZA_01

Alcatel-Lucent Part #
Guide
7705 SAR-O Chassis Installation Guide
7705 SAR-W Chassis Installation Guide
7705 SAR-Wx Chassis Installation Guide
7705 SAR OS Basic System Configuration Guide
7705 SAR OS Interface Configuration Guide
7705 SAR OS MPLS Guide
7705 SAR OS OAM and Diagnostics Guide
7705 SAR OS Quality of Service Guide
7705 SAR OS Router Configuration Guide
7705 SAR OS Routing Protocols Guide
7705 SAR OS Services Guide
7705 SAR OS System Management Guide
3HE09165AAAATQZZA_01
7705 SAR-A Power Supply Tray Installation Instructions
7705 SAR Zipped Collection
Alcatel-Lucent
3HE086790007TQZZA_01
RELEASE 6.1.R7 SUPPORTED HARDWARE

The following tables summarize the hardware supported in this release.
Table 2. 7705 SAR Common Equipment
Alcatel-Lucent
Part #
Description
Introduced
3HE02773AA
7705 SAR-8 Shelf
R1.0.R1
3HE02774AA
Control and Switching Module (CSM)
R1.0.R1
3HE02778AA
7705 SAR-8 Fan Module
R1.0.R1
3HE02777AA
7705 SAR-F (-48V)
R1.1.R1
3HE02777AB
7705 SAR-F (+24V)
R1.1.R1
3HE02778AB
SAR-8 Fan Module (-48V) Extended Temperature
R2.0.R1
3HE02774BA
Control and Switching Module (+24V)
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
Alcatel-Lucent
3HE086790007TQZZA_01

Table 3. 7705 SAR Adapter Cards
Alcatel-Lucent
Part #
Description
Introduced
3HE02775AA
16 Port T1/E1 ASAP Card
R1.0.R1
3HE02776AA
8 Port GE/FE Ethernet Card
R1.0.R1
3HE02776AB
8 Port GE/FE Ethernet Card V2
R1.1.R1
3HE03125AA
4 Port OC3c/STM1c POS/ATM Card
R2.0.R1
3HE02775BA
16 Port T1/E1 ASAP Card (+24V)
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 T3/E3 Card (-48V)
R3.0.R1
3HE04962BA
4 Port T3/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
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
3HE06582BB
R5.0.R1
3HE06582BC
R5.0.R1
3HE06582BD
R5.0.R1
3HE06582BE
R5.0.R1
3HE06582BF
R5.0.R1
3HE06582BG
R5.0.R1
3HE06582BH
R5.0.R1
3HE06582AA
SAR-8/18 OADM Add/Drop CWDM 1471
R5.0.R1
3HE06582AB
R5.0.R1
3HE06582AC
R5.0.R1
3HE06582AD
R5.0.R1
3HE06582AE
R5.0.R1
3HE06582AF
R5.0.R1
3HE06582AG
R5.0.R1
3HE06582AH
R5.0.R1
Alcatel-Lucent
3HE086790007TQZZA_01

Alcatel-Lucent
Part #
Description
Introduced
3HE06583AA
SAR-8/18 OADM Add/Drop 1471/1491
R5.0.R1
3HE06583AB
R5.0.R1
3HE06583AC
R5.0.R1
3HE06583AD
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 14711611
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 IPSecCapable
R6.0.R4
3HE02780AA
6-port FXS Adapter Card
R6.0.R5
Note: The 7705 SAR hardware supports qualified pluggable optic modules only. Refer to
the current Alcatel-Lucent price list for supported modules. Third-party optics are not
supported.
Table 4. Accessories
Alcatel-Lucent
Part #
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
Alcatel-Lucent
3HE086790007TQZZA_01

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
Note: The 7705 SAR hardware supports Alcatel-Lucent-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
Alcatel-Lucent
Part #
Description
Introduced
Minimum
Software
Release
3HE07614AA
SAR-Wx w/ 5 GigE & AC power
R6.1.R2
R6.1.R2
3HE07616AA
SAR-Wx w/ 5 GigE, PoE+ & AC power
R6.1.R2
R6.1.R2
3HE07615AA
SAR-Wx w/ 5 GigE, GPS Rx & AC power
R6.1.R4
R6.1.R4
3HE07617AA
SAR-Wx w/ 5 GigE, PoE+, GPS Rx & AC

power
R6.1.R4
R6.1.R4
3HE06969AA
SAR-H High Voltage Shelf
R6.1.R1
SAR-H R5.0.R1 1
3HE06969BA
SAR-H Low Voltage Shelf
R6.1.R1
SAR-H R5.0.R11
3HE06969CA
SAR-H High Voltage Shelf w/ Conformal

Coat
R6.1.R2
SAR-H R5.0.R11
3HE06969DA
SAR-H Low Voltage Shelf w/ Conformal

Coat
R6.1.R2
SAR-H R5.0.R11
3HE07353AA
SAR-Hc
R6.1.R1
R6.1.R1
3HE07353BA
SAR-Hc w/ Conformal Coat
R6.1.R2
R6.1.R1
3HE05051BB
SAR-M with 16 T1/E1, 7 GigE, -48/+24

VDC w/ Conformal Coat
R6.1.R2
R5.0.R1
3HE05653BA
SAR-M with 7 GigE, -48/+24 VDC w/

Conformal Coat
R6.1.R2
R5.0.R1
3HE02774CB
SAR-8 CSMv2 (-48/+24VDC) w/Conformal

Coat
R6.1.R1
R6.0.R1
3HE06791BA
SAR-8 Shelf V2 w/ Conformal Coat
R6.1.R1
R5.0.R1
3HE06792CA
Fan Module for SAR-8 Shelf V2 Ext. Temp

(-48VDC) w/ Conformal Coat
R6.1.R1
R5.0.R1
3HE06792DA
Fan Module for SAR-8 Shelf V2 Ext. Temp

(+24VDC) w/ Conformal Coat
R6.1.R1
R6.0.R1
SAR-H R5.0 (Release Notice 3HE080840004TQZZA_01) is a separate software stream that will be discontinued
at a future date. The Standard Software Upgrade Procedure is not supported from this release. For assistance in
upgrading from SAR-H R5.0 to SAR R6.1, please contact your Alcatel-Lucent representative.
Alcatel-Lucent
3HE086790007TQZZA_01

Alcatel-Lucent
Part #
Description
Introduced
Minimum
Software
Release
3HE06972AA
100W HV Power Supply
R6.1.R1
N/A
3HE06970AA
SAR-H 100W 48V DC Power Supply - HV

Input
R6.1.R1
N/A
3HE06970BA
SAR-H 100W 48V DC Power Supply - LV

Input
R6.1.R1
N/A
3HE06970CA
100W 48V DC Power Supply - HV Input

/Conformal Coated
R6.1.R2
N/A
3HE06970DA
100W 48V DC Power Supply - LV Input

/Conformal Coated
R6.1.R2
N/A
3HE08703AA
SAR-Wx/W 5-ft Console Cable (RJ45 to

DB9 adapter)
R6.1.R1
N/A
Table 6. Adapter Cards New in this Release

Alcatel-Lucent
Part #
Description
Introduced
Minimum
Software
Release
3HE07942AA
Integrated Services Card
R6.1.R1
R6.1.R1
3HE06788AA
2-Port 10 GigE (Ring) Module - SAR-M
R6.1.R1
R6.1.R1
3HE06788BA
2-Port 10 GigE (Ring) Module - SAR-M w/

Conformal Coat
R6.1.R2
R6.1.R1
3HE06973AA
SAR-H T1/E1 ASAP/Serial Combo Module
R6.1.R1
SAR-H
R5.0.R1 2
3HE06973BA
SAR-H T1/E1 ASAP/Serial Combo Module w/

Conformal Coat
R6.1.R2
SAR-H R5.0.R12
3HE02776CB
8 Port GE/FE Ethernet Card V2 (-48 VDC) w/

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

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

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

Conformal Coat
R6.1.R1
R6.0.R1
3HE06151BC
8-Port GE SFP Card V3 IPSecCapable w/

Conformal Coat
R6.1.R1
R6.0.R4
SAR-H R5.0 (Release Notice 3HE080840004TQZZA_01) is a separate software stream that will be discontinued
at a future date. The Standard Software Upgrade Procedure is not supported from this release. For assistance in
upgrading from SAR-H R5.0 to SAR R6.1, please contact your Alcatel-Lucent representative.
Alcatel-Lucent
3HE086790007TQZZA_01

Alcatel-Lucent
Part #
Description
Introduced
Minimum
Software
Release
3HE06789BA
2-Port 10GigE (Ethernet) XFP Card

(-48/+24 VDC) w/ Conformal Coat
R6.1.R1
R6.0.R1
3HE07938AA
4-Port OC3/STM1 Channelized Card
R6.1.R4
R6.1.R4
3HE03125BA
4 Port OC3c/STM1c POS/ATM Card w/

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

Coat
R6.1.R2
R3.0.R2
3HE03127BA
2P OC3/STM1 CH w/ Conformal Coat
R6.1.R2
R2.1.R1
3HE07152BA
Power Injector Card w/ Conformal Coat
R6.1.R2
R5.0.R4
3HE02782BA
Packet Microwave Card w/ Conformal Coat
R6.1.R2
R5.0.R4
3HE02772BA
Auxiliary Alarm Card (-48V/+24 VDC) w/

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

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

Conformal Coat
R6.1.R2
R6.0.R1
3HE02780BA
6-port FXS Adapter Card w/ Conformal Coat
R6.1.R2
R6.0.R5
3HE07955AA
SAR-H GPS Receiver Module
R6.1.R3
R6.1.R3
Table 7. Accessories New in this Release

Alcatel-Lucent
Part #
Description
Introduced
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
Alcatel-Lucent
3HE086790007TQZZA_01
10

Alcatel-Lucent
Part #
Description
Introduced
3HE07960AA
SAR-Wx 0.35m GPS Cable
R6.1.R4
Alcatel-Lucent
3HE086790007TQZZA_01
11
SUPPORTED MPR-e RADIOS (7705 SAR + MPR-e SINGLE NE MODE)

The 7705 SAR Release 6.1 OS supports MPR-e radios operating in Single NE
mode when attached to the 7705 SAR. Note that applicable MPR-e OS licenses
may be required.
SUPPORTED MPR-e RADIOS

The following table summarizes the MPR-e radio hardware that is supported in
Single NE mode in this release.
Table 8. Supported MPR-e Radio Hardware
Alcatel-Lucent 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
* If specific part numbers need to be known, please contact Alcatel-Lucent or refer to the
9500 MPR Release Notes available on OLCS as listed in Table 9.
SUPPORTED MPR-e SOFTWARE

MPR-e radios operating in Single NE mode require specific software that is
included in the 7705 SAR Release 6.1 OS software bundle. Note that two
versions of the 7705 SAR Release 6.1 OS software bundle are available. The
version named 7705-TiMOS.6.1.R2.MWA.zip is required when the 7705
SAR has MPR-e radios operating in Single NE mode.
The following table 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
Release
MPR-e Release Notes
R6.0.R1 and above
4.1.0
3DB 19043 AAAA FMZZA

(ETSI)
3DB 19043 AAAA DEZZA
(ANSI)
Note: For more details on the 7705 SAR upgrade procedure with the MPR-e, refer to the
SOFTWARE UPGRADE NOTES section of this document.
Alcatel-Lucent
3HE086790007TQZZA_01
12
NEW FEATURES IN RELEASE 6.1.R7

There are no new features in this release.

The following sections describe the new features in this release.
Some features supported on the 7705 SAR product family require a Right-to-Use
(RTU) license. Contact your Alcatel-Lucent representative for the appropriate
application licenses.
BETA: Some features are made available in the current release but are
considered BETA quality. They are not fully tested but are enabled in 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 CLI and
are suitable for customer demonstrations.
BETA and ALPHA features are marked as applicable.
Note: The platform reference to 7705 SAR-8(v1/v2) means that any combination of
SAR-8 shelf v1 or v2 with a CSMv1 or CSMv2 can be used.
8-Port Gigabit Ethernet

SFP Adapter Card v3
(3HE06151AC)
(3HE06151BC)
DCR on 4-Port DS3/E3
Adapter card
Alcatel-Lucent
The 8-port Gigabit Ethernet SFP Adapter card v3, introduced in an

earlier release, is now backwards compatible with 7705 SAR-8 systems
with a CSMv1. Note that although this card is hardware-ready for
IPSec, the IPSec feature is not supported on the CSMv1.
The card is retroactively supported to Release 6.1.R2.
Differential Clock Recovery on DS1/E1 channels on DS3 ports for the
4-port DS3/E3 Adapter card is now supported.
3HE086790007TQZZA_01
13

Cpipes on 4-port
OC3/STM1 Channelized
Adapter Card
Cpipes (TDM VLLs) are supported on access ports of the 4-port

OC3/STM1 Channelized Adapter card.
MLPPP on 4-port
Adapter Card
MLPPP encapsulation is enabled on network ports of the 4-port

1588v2 Scaling
Enhancement
NAT Packet Fragment
Handling
Alcatel-Lucent
The 7705 SAR now supports increased scale for 1588v2. For further
details, contact your Alcatel-Lucent representative.
For fragmented packets, special handling through NAT is required
because non-first-fragments do not include the UDP/TCP header. This
capability is now supported on NAT-capable 7705 SAR platforms. For
more details, refer to the 7705 SAR OS Router Configuration Guide.
3HE086790007TQZZA_01
14

SAR-Wx w/ 5 GigE, GPS

Rx & AC Power
(3HE07615AA)
SAR-Wx w/ 5 GigE,
PoE+, GPS Rx & AC
Power
(3HE07617AA)
4-Port OC3/STM1
Channelized Adapter
Card
(3HE07938AA)
(See Note)
Alcatel-Lucent
The 7705 SAR-Wx is an environmentally hardened platform that

supports five Gigabit Ethernet ports: three 10/100/1000 Base-X with
SFP ports and two 10/100/1000 Base-T RJ45 ports. The 7705 SAR-Wx
supports a 110/220 VAC power feed. The device is passively cooled,
with a -40 to 55C temperature range. It can be mounted to a wall,
pole or strand. The 7705 SAR-Wx supports 5.0 Gb/s of fullduplex
switch capacity. This variant of the 7705 SAR-Wx includes an integrated
GPS receiver. Some features supported on this platform require a
Right-to-Use (RTU) license. The OS licenses for the 7705 SAR-Wx are
sold separately.
SFP ports and two 10/100/1000 Base-T RJ45 ports. This variant
supports PoE+ power output on one of the RJ45 ports. The 7705 SARWx supports a 110/220 VAC power feed. The device is passively cooled,
sold separately.
The 4-port OC3/STM1 Channelized Adapter card, with channelization
down to DS1/E1, is supported on the 7705 SAR-8 with CSMv2 and the
7705 SAR-18. Each port can be independently configured for the
different services on access or network. In access mode, each port
must be configured for TDM. In network mode, each port must be
configured for MLPPP. SFPs are sold separately.
3HE086790007TQZZA_01
15

SSH/SCP over IPv6
IPv6 Management
Access Filters (MAF)
Static Destination NAT
Management client access with SSH/SCP over IPv6 is now supported.

With the introduction of SSH/SCP over IPv6 for 7705 SAR management,
IPv6 MAFs control all traffic in and out of the CSM. They can be used to
restrict management of the 7705 SAR by other nodes outside either
specific (sub)networks or through designated ports.
Static Destination NAT (or port forwarding) allows the mapping of a
public UDP/TCP port to a private IP destination address and port. This
allows an application to be forwarded through the NAT table directly
to a host that can process the incoming packets.
This feature is supported on the same systems and adapter cards as the
dynamic source NAT feature introduced in Release 6.1.R1.
Multi-Instance IS-IS
(RFC 6822)
Routing Information
Protocol (RIP) at PE-CE
Per-VLAN Network
Egress Shapers
Multiple instances of IS-IS can be configured on a single router. Each

instance utilizes separate resources and supports unique adjacencies,
topologies, architectures, etc.
RIP v1/v2 is now supported on PE-CE interfaces for VPRN services.
Per-VLAN network egress shapers add another tier of shaping similar in

functionality to SAP egress shapers. This allows traffic to be fairly
shaped and scheduled on separate VLANs. For example, on a 7705 SAR
in a hub site that is connected to multiple access sites via a single
1-GigE or 10-GigE link, but with multiple VLANs on the Layer 2 network
in between, traffic destined for each individual access site can be
shaped as required.
This feature is supported on 1-GigE and 10-GigE ports on the following
platforms and adapter cards:
7705 SAR-8(v1/v2)/SAR-18: 8-port Ethernet Adapter card v2
7705 SAR-8(v1/v2)/SAR-18: 8-port Gigabit Ethernet SFP
Adapter card
Adapter card v2
Adapter card v3
7705 SAR-8(v1/v2)/SAR-18: 2port 10GigE (Ethernet) XFP
Adapter card
7705 SAR-8(v1/v2)/SAR-18: Packet Microwave Adapter card
7705 SAR-18: 10-port 1GigE/1-port 10GigE X-Adapter card
7705 SAR-18: 10-port 1GigE/1-port 10GigE X-Adapter card v2
7705 SAR-F
7705 SAR-M: all platform variants
7705 SAR-A: all platform variants
7705 SAR-W
7705 SAR-Wx: all platform variants
7705 SAR-H
7705 SAR-Hc
Alcatel-Lucent
3HE086790007TQZZA_01
16

System Time Derived
from 1588v2
This feature allows the 7705 SAR platform to derive its system time by
functioning as a client to a 1588v2 reference clock. Compared with
tradional NTP, 1588v2 can offer much more accurate timing, in some
scenarios down to the microsecond level.
This feature is supported on the following platforms:
7705 SAR-W
7705 SAR-H
7705 SAR-Hc
System Time Derived

from GPS
This feature allows the 7705 SAR platforms that support an integrated
GPS receiver to derive system time from the GPS as the timing source.
This also allows these systems to function as Grand Master for 1588v2
timing distribution to downstream clients.
7705 SAR-Wx: GPS platform variants
7705 SAR-H
OAM Accuracy
Enhancements
With the introduction of more accurate system time derived from

1588v2/GPS, OAM toolsets have been enhanced to utilize this
information in order to provide more accurate latency testing results,
particularly important in one-way tests. In some scenarios, latency
testing results are accurate to the microsecond level.
7705 SAR-W
7705 SAR-H
7705 SAR-Hc
Cpipes on 4-Port
Adapter Card

(See Note)
MLPPP on 4-Port
Adapter Card

(See Note)
Note : Hardened for SDH mode with E1 framing. BETA for SONET mode, or SDH mode with T1 framing.
Alcatel-Lucent
3HE086790007TQZZA_01
17

SAR-H GPS Receiver

Module
The 7705 SAR-H GPS Receiver Module can retrieve time/frequency

information from a GPS Antenna to be used for system synchronization.
(3HE07955AA)
Rx & AC Power
(3HE07615AA)
BETA
SAR-Wx w/ 5 GigE,
PoE+, GPS Rx & AC
Power
(3HE07617AA)
BETA
Alcatel-Lucent

sold separately.
sold separately.
3HE086790007TQZZA_01
18

4-Port OC3/STM1
Channelized Adapter
Card
(3HE07938AA)
BETA
FRR Enhancements

down to DS1/E1, is supported on the 7705 SAR-8 with CSMv2 and the
7705 SAR-18. Each port can be independently configured for the
different services on access or network. In access mode, each port
must be configured for TDM. In network mode, each port must be
configured for MLPPP. SFPs are sold separately.
Fast Re-Route (FRR) in MPLS networks plays a critical role in service
availability and reconvergence times after a node or a link failure. In
this release, the 7705 SAR introduces significant enhancements to FRR
scaling and performance times. The number of LSPs that can be
rerouted in LSR mode and the number of services in LER mode both
benefit from this enhancement. This feature enhancement applies
equally to node-protection or link-protection modes provided by bypass
LSPs. FRR scaling enhancements apply to all service types. For more
Access Egress IP Filters

on IES/VPRN
Access egress IPv4 filters on IES/VPRN services and IPv6 filters on IES
are now supported. (D.168980)
In-Band Management in
VPRN
The 7705 SAR products support in-band management in a virtual

private routed network (VPRN). This feature simplifies the networking
architectures where OAM networks are required to be segregated from
other networking functions.
SSH/SCP over IPv6
Management client access with SSH/SCP over IPv6 is now supported.
BETA
Static Destination NAT
BETA
Static Destination NAT (or port forwarding) allows the mapping of a

public UDP/TCP port to a private IP destination address and port. This
allows an application to be forwarded through the NAT table directly
to a host that can process the incoming packets.
This feature is supported on the same systems and adapter cards as the
dynamic source NAT feature introduced in Release 6.1.R1.
Per-VLAN Network
Egress Shapers
BETA
Per-VLAN network egress shapers add another tier of shaping similar in

functionality to SAP egress shapers. This allows traffic to be fairly
shaped and scheduled on separate VLANs. For example, on a 7705 SAR
in a hub site that is connected to multiple access sites via a single
1-GigE or 10-GigE link, but with multiple VLANs on the Layer 2 network
in between, traffic destined for each individual access site can be
shaped as required.
This feature is supported on 1-GigE and 10-GigE ports on the following
platforms and adapter cards:
Adapter card
Adapter card v2
7705 SAR-8 with CSMv2/SAR-18: 8-port Gigabit Ethernet SFP
Adapter card v3
Alcatel-Lucent
3HE086790007TQZZA_01
19
Cpipes on 4-Port
Adapter Card
7705 SAR-8(v1/v2)/SAR-18: 2port 10GigE (Ethernet) XFP

Adapter card
7705 SAR-W
7705 SAR-H
7705 SAR-Hc

BETA
MLPPP on 4-Port
Adapter Card

BETA
Alcatel-Lucent
3HE086790007TQZZA_01
20

SAR-Wx w/ 5 GigE & AC

Power
(3HE07614AA)
SAR-Wx w/ 5 GigE,
PoE+ & AC Power
(3HE07616AA)

Rx & AC Power
(3HE07615AA)
BETA
GPS functionality will
be supported in a
future release
Alcatel-Lucent

switch capacity. Some features supported on this platform require a
sold separately.
sold separately.
Right-to-Use (RTU) license.
3HE086790007TQZZA_01
21

The OS licenses for the 7705 SAR-Wx are sold separately.
SAR-Wx w/ 5 GigE,
PoE+, GPS Rx & AC
Power
(3HE07617AA)
BETA
GPS functionality will
be supported in a
future release
4-Port OC3/STM1
Channelized Adapter
Card
(3HE07938AA)
ALPHA
Hybrid Ports

sold separately.
down to DS1/E1, is supported on the 7705 SAR-8 and 7705 SAR-18. Each
port can be independently configured for the different services on
access or network. In access mode, each port must be configured for
TDM. In network mode, each port must be configured for MLPPP. SFPs
are sold separately.
Hybrid ports allow a single port to operate in both access and network
modes. The default encapsulation for hybrid port mode is Dot1q; it also
supports QinQ encapsulation on the port level. Null hybrid port mode is
not supported. LAG support is a future enhancement.
Hybrid ports are supported on the following platforms and adapter
cards:
Adapter card
Adapter card v2
Adapter card v3
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
Jumbo Frames
Ethernet jumbo frames are supported. The maximum size depends on

the Ethernet encapsulation in use.
Encapsulation
Null
Dot1q
QinQ
Alcatel-Lucent
Max. MTU (Bytes)

9724
9728
9732
3HE086790007TQZZA_01
22

Jumbo frames are supported on the following platforms and adapter
cards:
7705 SAR-8 with CSMv2: 8-port Ethernet Adapter card v2
7705 SAR-8 with CSMv2: 8-port Gigabit Ethernet SFP Adapter card
7705 SAR-8 with CSMv2: 8-port Gigabit Ethernet SFP Adapter
card v2
card v3
7705 SAR-8 with CSMv2: Packet Microwave Adapter card
7705 SAR-8 with CSMv2: 2-port 10GigE (Ethernet) XFP Adapter
card
7705 SAR-18: 8-port Ethernet Adapter card v2
7705 SAR-18: 8-port Gigabit Ethernet SFP Adapter card
7705 SAR-18: 8-port Gigabit Ethernet SFP Adapter card v2
7705 SAR-18: Packet Microwave Adapter card
7705 SAR-18: 2-port 10GigE (Ethernet) XFP Adapter card
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
Auto-bind
Enhancement
Multi-Field
Classification (MFC)
VPRN services now support automatic binding to RSVP-TE SDPs assigned

to the service. RSVP-TE SDPs can be configured individually to allow or
disallow auto-binding. In addition, an option to use either LDP or RSVPTE SDPs is available, with LDP SDPs preferred. This extends the
previously supported options of LDP and GRE tunnels.
Multi-field classification (MFC) allows a router to classify incoming
traffic based on IP criteria other than the DSCP value. This is
applicable when incoming traffic, and by extension, the traffic
classification markings on the incoming packets, is untrusted.
IP criteria to match on are exactly the same as supported ACL
configuration parameters.
MFC is supported on ingress for Layer 3 network interfaces, VPRN/IES
SAPs, VPRN/IES spoke SDPs, and Epipe/Ipipe SAPs.
IPSec (IPv4)
IPSec enables the encryption and authentication of IP packets. The

7705 SAR supports hardware-accelerated IPSec for optimal
performance and throughput.
The 7705 SAR supports IPSec tunnel mode on VPRNs with the following
options:
Encryption:
AES 256
AES 128
NULL
3DES
Alcatel-Lucent
3HE086790007TQZZA_01
23

Authentication:
HMAC-SHA-512
HMAC-SHA-256
SHA-1-96
HMAC-MD5
NULL
Key Exchange:
IKEv2 with Pre-shared Key (PSK)
IPSec is supported on the following platforms and adapter cards:
card v3
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
Label-BGP
(RFC 3107)
Fixed Mobile Convergence has created the need to offer services over
larger-than-ever geographic areas. This convergence of mobile
backhaul, business-to-business, machine-to-machine, etc., as well as
any-to-any Layer 2 services (that is, VPLS or pseudowires) and/or Layer
3 IP-VPN services, is critical to success, and seamless MPLS
infrastructure with RFC 3107 support can accomplish that. This feature
allows networks and transport infrastructure to be configured once,
and new services can then be turned up without touching/
reconfiguring any intermediate nodes. This simplifies day-to-day
operational procedures and drives down operating expenses.
The 7705 SAR supports Layer 2 point-to-point services (that is, a full
set of pseudowire services including Ethernet, IP, TDM, FR, ATM and
HDLC PWs), Layer 2 multipoint services (that is, VPLS/ELAN), and Layer
3 IP-VPN services over seamless MPLS infrastructure with both Option-B
and Option-C for maximum flexibility.
The 7705 SAR also supports industry-leading label BGP routes on a pernode basis, including the 1RU platforms, to meet and exceed the
scaling requirements of even very large topologies. For more details on
scaling limits, contact your Alcatel-Lucent representative.
1588v2 Support on
SAR-M 2-Port 10GigE
(Ethernet) Module
LDP Export Policy
This feature is hardened in this release.
An LDP export policy can control the set of LDP label bindings
advertised by the router. For example, for security reasons, it may be
advantageous to use a non-system loopback address for LDP label
bindings.
By default, only label bindings for the system address are advertised
and propagate all FECs that are received. (D.172072)
Alcatel-Lucent
3HE086790007TQZZA_01
24

ARP Entries Scaling
The number of ARP entries supported on some platforms of the 7705

SAR has been increased. For more details, contact your Alcatel-Lucent
representative.
FRR Enhancements

equally to node-protection or link-protection modes provided by bypass
LSPs. FRR scaling enhancements apply to all service types. For more
BETA

on IES/VPRN
ALPHA
Alcatel-Lucent
3HE086790007TQZZA_01
25

Hardware on page 26
System on page 28
Services on page 31
Quality of Service on page 31
Routing on page 31
MPLS on page 33
OAM on page 34
Synchronization on page 34
Licenses on page 34
HARDWARE
Conformal Coated
Variants
(Multiple)
The following sections describe the new hardware supported in

Release 6.1.R1.
Many existing and new hardware systems, cards, modules, etc., are
now available in conformal coated variants (See Table 5 and Table 6
for part numbers). Software releases that support conformal coated
variants are the same as the software releases for non-conformal
variants of the same hardware.
Conformal coating provides extra protection to sensitive electronic
components when the 7705 SAR is deployed in harsh environments. For
more details on whether this option is required, contact your AlcatelLucent representative.
Alcatel-Lucent
3HE086790007TQZZA_01
26

SAR-H
(3HE06969AA)
(3HE06969BA)
The 7705 SAR-H is a temperature- and EMC-hardened platform. It is

passively cooled and supports an operating temperature range from
-40 to 65C. It supports eight Gigabit Ethernet ports: four
10/100/1000 Base-X SFP ports and four 10/100/1000 Base-T RJ45
PoE-capable Ethernet ports. It also supports two module positions for
expansion. The 7705 SAR-H supports 4 Gb/s of fullduplex switch
capacity. Some features supported on this platform require a Right-toUse (RTU) license. The OS licenses for the 7705 SAR-H are sold
separately.
The 7705 SAR-H High Voltage Shelf (3HE06969AA) variant supports
110/240 VAC or 110-250 VDC.
The 7705 SAR-H Low Voltage Shelf (3HE06969BA) variant supports
two +24/-48 VDC inputs.
ASAP/Serial Combo
Module SAR-H
(3HE06973AA)
SAR-Hc
(3HE07353AA)
The SAR-H 4-port T1/E1 and RS-232 Combination module supports two
T1/E1 ports and two RS-232/V.24 asynchronous serial ports. The T1/E1
ports support TDM and IP services only. These ports support line
timing, ACR, and DCR. The serial ports support Cpipe functionality
only and are compatible with the 7705 SAR Serial Data Interface card
and 36xx MainStreet products.
The 7705 SAR-Hc is a temperature- and EMC-hardened platform. It is
passively cooled and supports an operating temperature range from
-40 to 65C. The 7705 SAR-Hc has six 10/100/1000 Mb/s Ethernet
ports (2 x SFP, 2 x RJ45, 2 x PoE RJ45) and two RS-232 ports. It
includes redundant 20-75 VDC power feeds, and can be DIN railmounted or panel/wall-mounted as required. The 7705 SAR-Hc
supports 2.5 Gb/s of full-duplex switch capacity. Some features
supported on this platform require a Right-to-Use (RTU) license. The
OS licenses for the 7705 SAR-Hc are sold separately.
The DIN rail or panel/wall mounting hardware is sold separately.
Integrated Services
Card Multidrop Data
Bridging (MDDB)
The Integrated Services card is an application resource card that

requires purchase of an application-specific RTU. This card is
supported in both -48 VDC and +24 VDC systems.
(3HE07942AA)
2-Port 10GigE (Ring)
Module SAR-M
(3HE06788AA)
Alcatel-Lucent
The 2-port 10GigE (Ethernet) module is a 7705 SAR-M expansion

module with 2-port 10GigE (Ethernet) XFPs for network (ring)
connectivity. The module supports 10G FD to both the East and West
paths. It supports a 2.5 Gb/s drop to the fabric. This module supports
network mode port operation only and is supported in both -48 VDC
and +24 VDC systems. XFPs are sold separately.
3HE086790007TQZZA_01
27

SAR-Wx w/ 5 GigE & AC
Power
(3HE07614AA)
BETA
SAR-Wx w/ 5 GigE,
PoE+, & AC Power
(3HE07616AA)
BETA
SYSTEM
QinQ on SAP

sold separately.
supports PoE+ power output on one of the RJ45 ports. The 7705 SARWx supports a 110/220 VAC power feed. The device is passively
cooled, with a -40 to 55C temperature range. It can be mounted to a
wall, pole or strand. The 7705 SAR-Wx supports 5.0 Gb/s of fullduplex
sold separately.
The following sections describe the new system features supported in

Release 6.1.R1.
QinQ encapsulation is now supported on Ethernet interfaces on service
access points (SAPs). Ethernet PW, IP PW, VPRN, IES and VPLS services
are supported, including SAP-to-SAP mode.
QinQ is supported on the following platforms and adapter cards:
7705 SAR-8(v1/v2)/SAR-18: 8-port Ethernet Adapter card v2
7705 SAR-8(v1/v2)/SAR-18: 8-port Gigabit Ethernet SFP Adapter
card
card v2
card v3
7705 SAR-F
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
Default SAP Support
Alcatel-Lucent
Default SAP configuration is supported for Dot1q and QinQ

encapsulation. A default SAP is a SAP that uses a wildcard VLAN ID,
such as 1/1/1:*. It matches all VLAN IDs that are not explicitly
configured on the port, except VLAN 0.
3HE086790007TQZZA_01
28

Static LAG
Static LAG is active/standby without LACP. In cases where the 7705

SAR aggregates nodes that do not support LACP (for example,
microwave nodes), static LAG can be configured to provide link and
card protection when applicable. The standby link will have the port
powered off. When a link/card failure occurs on the active link, the
standby link will be activated.
SAR-W Scaling to
SAR-M Limits
The 7705 SAR-W supports the same scaling numbers as the 7705 SAR-M
platform.
SAR-H Switch Capacity

Enhancement
The switch capacity of all 7705 SAR-H variants has been doubled from
2.0 Gb/s FD to 4.0 Gb/s FD in this software release.
PoE Show Menu

Enhancements
This debugging enhancement provides information on the Power over

Ethernet usage, including details on maximum available power, total
power used, and power in use per device. (D.168970)
PoE is supported on the following platforms:
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
Hybrid Ports
BETA
Hybrid ports allow a single port to operate in both access and network
modes. The default encapsulation for hybrid port mode is Dot1q; it
also supports QinQ encapsulation on the port level. Null hybrid port
mode is not supported. LAG support is a future enhancement.
Hybrid ports are supported on the following platforms and adapter
cards:
Adapter card
Adapter card v2
Adapter card v3
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
Alcatel-Lucent
3HE086790007TQZZA_01
29

Jumbo Frames
Ethernet jumbo frames are supported. The maximum size depends on

the Ethernet encapsulation in use.
BETA
Encapsulation
Null
Dot1q
QinQ
Max. MTU (Bytes)

9724
9728
9732
Jumbo frames are supported on the following platforms and adapter

cards:
7705 SAR-8 with CSMv2: 8-port Ethernet Adapter card v2
card
card v2
card v3
7705 SAR-8 with CSMv2: Packet Microwave Adapter card
7705 SAR-8 with CSMv2: 2-port 10GigE (Ethernet) XFP Adapter
card
7705 SAR-18: 8-port Ethernet Adapter card v2
7705 SAR-18: 8-port Gigabit Ethernet SFP Adapter card
7705 SAR-18: Packet Microwave Adapter card
7705 SAR-18: 2-port 10GigE (Ethernet) XFP Adapter card
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
ACL Limits Scaling
Alcatel-Lucent
The ACL entries limit per IPv4 filter as well as per MAC filter has been
increased for all 7705 SAR platforms and adapter cards. In addition,
some system-wide limits have been increased. For more details,
contact your Alcatel-Lucent representative.
3HE086790007TQZZA_01
30
SERVICES
VPRN/Interface Scaling
Auto-bind
Enhancement
BETA
The following sections describe the new services features supported in

Release 6.1.R1.
The number of VPRN instances and the system-wide number of
interfaces within VPRN/IES services have been increased. This
increase is dependent on which system hardware is installed in the
7705 SAR-8 or 7705 SAR-18. For more details, contact your AlcatelLucent representative.
VPRN services now support automatic binding to RSVP-TE SDPs
assigned to the service. RSVP-TE SDPs can be configured individually
to allow or disallow auto-binding. In addition, an option to use either
LDP or RSVP-TE SDPs is available, with LDP SDPs preferred. This
extends the previously supported options of LDP and GRE tunnels.
QUALITY OF
SERVICE
The following sections describe the new QoS features supported in

Release 6.1.R1.
Multi-Field
Classification (MFC)
Multi-field classification (MFC) allows a router to classify incoming

traffic based on IP criteria other than the DSCP value. This is
applicable when incoming traffic, and by extension, the traffic
classification markings on the incoming packets, is untrusted.
BETA
IP criteria to match on are exactly the same as supported ACL

configuration parameters.
MFC is supported on ingress for Layer 3 network interfaces, VPRN/IES
SAPs, VPRN/IES spoke SDPs, and Epipe/Ipipe SAPs.
ROUTING
IPv4 Source-NAT
The following sections describe the new routing features supported in

Release 6.1.R1.
The 7705 SAR supports dynamic source NAT/PAT for IPv4. Source
NAT/PAT allows scaling of IPv4 networks by separating private IP
addresses from the public network. All private IP addresses can be
reached via a single public IP address or a small range of public IP
addresses. In addition, source NAT/PAT can provide additional security
to a private network by hiding internal private IP addresses.
Source NAT is supported on the following platforms and adapter cards:
7705 SAR-8 with CSMv2 or 7705 SAR-18 configured with any
combination of the following adapter cards only:
o 8-port Gigabit Ethernet SFP Adapter card
o 8-port Gigabit Ethernet SFP Adapter card v2
o 8-port Gigabit Ethernet SFP Adapter card v3
o Packet Microwave Adapter card
o 2-port 10GigE (Ethernet) XFP Adapter card
o (7705 SAR-18 only) 10-port 1GigE/1-port 10GigE
X-Adapter card
Alcatel-Lucent
3HE086790007TQZZA_01
31

o
o
o
o
(7705 SAR-18 only) 10-port 1GigE/1-port 10GigE

X-Adapter card v2
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc
Proxy ARP
The proxy ARP feature allows the 7705 SAR to respond to ARP requests
on behalf of other network elements. This feature allows for network
reachability for proxy ARP client nodes without the need to configure
a default gateway or IP routing. This feature was previously supported
on VPRN services. Support has been added for IES and network
interfaces.
DHCP Server (IPv4)
The local DHCP server provides a mechanism to respond to host

requests for configuration information. For example, access devices
attached to the 7705 SAR can request details such as IP address, DNS
address, hostname, default router, etc., from the server configured on
the 7705 SAR.
The 7705 SAR supports persistent DHCP in case of CSM redundancy and
node reboot, allowing for learned DHCP sessions to be maintained and
recovered. The persistence information is stored on the compact
flash.
Local DHCP servers are supported on all 7705 SAR platforms under the
VPRN or GRT context.
IP ECMP
TEID Hashing
IPv6 Discard Statistics

BGP TTL Security
Alcatel-Lucent
The 7705 SAR supports ECMP on up to eight access or network

interfaces. Hashing is based on source/destination IP address, source/
destination port (optional), and TEID (optional). This feature is
supported for GRT interfaces (IES service, network interfaces) and
VPRN service interfaces. For VPRN service with LDP transport at the
network egress, traffic is hashed once more across multiple LDP ECMP
links.
The 7705 SAR supports TEID hashing on IP ECMP-enabled links. In
mobile backhaul where source/destination IP address and UDP/TCP
ports are consistently the same, the wireless GTP tunnels TEID
provides a granular identifier to improve traffic hashing on loadbalancing IP ECMP links while still avoiding misordering of frames.
The 7705 SAR now captures IPv6 packet discard statistics.
When BGP TTL security is enabled on the 7705 SAR, BGP will accept
incoming IP packets from a peer only if the TTL value in the packet is
greater than or equal to the minimum TTL value configured for that
peer. This feature provides added protection against hacking attacks
between BGP peers. (P.613155)
3HE086790007TQZZA_01
32

IPSec (IPv4)
BETA
IPSec enables the encryption and authentication of IP packets. The

7705 SAR supports hardware-accelerated IPSec for optimal
performance and throughput.
The 7705 SAR supports IPSec tunnel mode on VPRNs with the following
options:
Encryption:
AES 256
AES 128
NULL
3DES
Authentication:
HMAC-SHA-512
HMAC-SHA-256
SHA-1-96
HMAC-MD5
NULL
Key Exchange:
IKEv2 with Pre-shared Key (PSK)
IPSec is supported on the following platforms and adapter cards:
card v3
7705 SAR-W
7705 SAR-Wx
7705 SAR-H
7705 SAR-Hc

on IES/VPRN
ALPHA
MPLS
Label-BGP
(RFC 3107)
BETA
Alcatel-Lucent
The following sections describe the new MPLS features supported in

Release 6.1.R1.
Fixed Mobile Convergence has created the need to offer services over
larger-than-ever geographic areas. This convergence of mobile
backhaul, business-to-business, machine-to-machine, etc., as well as
any-to-any Layer 2 services (that is, VPLS or pseudowires) and/or
Layer 3 IP-VPN services, is critical to success, and seamless MPLS
infrastructure with RFC 3107 support can accomplish that. This
feature allows networks and transport infrastructure to be configured
once, and new services can then be turned up without touching/
reconfiguring any intermediate nodes. This simplifies day-to-day
operational procedures and drives down operating expenses.
3HE086790007TQZZA_01
33

The 7705 SAR supports Layer 2 point-to-point services (that is, a full
set of pseudowire services including Ethernet, IP, TDM, FR, ATM and
HDLC PWs), Layer 2 multipoint services (that is, VPLS/ELAN), and
Layer 3 IP-VPN services over seamless MPLS infrastructure with both
Option-B and Option-C for maximum flexibility.
The 7705 SAR also supports industry-leading label BGP routes on a
per-node basis, including the 1RU platforms, to meet and exceed the
scaling requirements of even very large topologies. For more details
on scaling limits, contact your Alcatel-Lucent representative.
FRR Enhancements
BETA
OAM
Y.1731 Down MEP on
Network Ports
SYNCHRONIZATION
1588v2 Support on
SAR-M 2-Port 10GigE
(Ethernet) Module

equally to node-protection or link-protection modes provided by
bypass LSPs. FRR scaling enhancements apply to all service types. For
more details, contact your Alcatel-Lucent representative.
The following sections describe the new OAM features supported in

Release 6.1.R1.
Y.1731 CFM and PM Down MEP on network ports is now supported (AIS
excluded).
The following sections describe the new synchronization features

supported in Release 6.1.R1.
This feature will be hardened in an upcoming release.
BETA
LICENSES
7705 SAR Release 6.1
Basic OS License
(3HE02784GA)
Alcatel-Lucent
The following sections describe the new licenses introduced with Release
6.1.R1.
One (1) 7705 SAR Release 6.1 OS license is required for each SAR-8,
SAR-F, SAR-M, SAR-A, SAR-H, SAR-Hc, SAR-W or SAR-Wx in the network.
See the optional RTUs available for additional advanced features.
3HE086790007TQZZA_01
34

7705 SAR Release 6.1
Basic OS Upgrade
License
(3HE02785GA)
One (1) 7705 SAR Release 6.1 OS upgrade license is required for each
SAR-8, SAR-F, SAR-M, SAR-A, SAR-H, or SAR-W in the network. See the
optional RTUs available for additional advanced features.
7705 SAR-18 Release

6.1 Basic OS License
(3HE05574DA)
One (1) 7705 SAR Release 6.1 OS license is required for each SAR-18 in
the network. See the optional RTUs available for additional advanced
features.
7705 SAR-18 Release

6.1 Basic OS Upgrade
License
(3HE06681DA)
One (1) 7705 SAR Release 6.1 OS upgrade license is required for each
SAR-18 in the network. See the optional RTUs available for additional
advanced features.
7705 SAR-H Basic IPSec

License
(3HE8607AA)
7705 SAR-H Full IPSec
License
(3HE8607AC)
7705 SAR-H Upgrade
IPSec License
(3HE8607AB)
7705 SAR-Hc Basic
IPSec License
(3HE8607BA)
7705 SAR-Hc Full IPSec
License
(3HE8607BC)
7705 SAR-Hc Upgrade
IPSec License
(3HE8607BB)
7705 SAR-W Basic IPSec
License
(3HE8607CA)
7705 SAR-W Full IPSec
License
(3HE8607CC)
7705 SAR-W Upgrade
IPSec License
(3HE8607CB)
Alcatel-Lucent
This license supports encryption throughput of 150 Mb/s and a maximum

of 25 IPSec tunnels. One (1) OS license is required for each SAR-H in the
network.
This license supports the maximum encryption throughput and tunnels.
One (1) OS license is required for each SAR-H in the network.
This is a basic-to-full IPSec license upgrade. One (1) OS license is

required for each SAR-H in the network.

of 25 IPSec tunnels. One (1) OS license is required for each SAR-Hc in the
network.
One (1) OS license is required for each SAR-Hc in the network.

required for each SAR-Hc in the network.

of 25 IPSec tunnels. One (1) OS license is required for each SAR-W in the
network.
One (1) OS license is required for each SAR-W in the network.

required for each SAR-W in the network.
3HE086790007TQZZA_01
35

7705 SAR-Wx Basic
IPSec License
(3HE8607DA)
7705 SAR-Wx Full IPSec
License
(3HE8607DC)
7705 SAR-Wx Upgrade
IPSec License
(3HE8607DB)
7705 SAR-8 Basic IPSec
License
(3HE8607EA)
7705 SAR-8 Full IPSec
License
(3HE8607EC)
7705 SAR-8 Upgrade
IPSec License
(3HE8607EB)
7705 SAR-18 Basic
IPSec License
(3HE8607FA)
7705 SAR-18 Full IPSec
License
(3HE8607FC)
7705 SAR-18 Upgrade
IPSec License
(3HE8607FB)

of 25 IPSec tunnels. One (1) OS license is required for each SAR-Wx in the
network.
One (1) OS license is required for each SAR-Wx in the network.

required for each SAR-Wx in the network.

of 50 IPSec tunnels. One (1) OS license is required for each SAR-8 in the
network.
One (1) OS license is required for each SAR-8 in the network.

required for each SAR-8 in the network.

of 50 IPSec tunnels. One (1) OS license is required for each SAR-18 in the
network.
One (1) OS license is required for each SAR-18 in the network.

required for each SAR-18 in the network.
Multi-Drop Data
Bridging (MDDB)
License
(3HE07354AF)
The 7705 SAR-8/18 Multi Drop Data Bridging (MDDB) RTU License is for
use on the 3HE07942AA Integrated Services Card (ISC). One (1) MDDB
License is required for up to 25 SAR-8/18 nodes in the network using the
ISC card. An incremental license (3HE07354AH) is required for each node
beyond 25 in the network. It supports a maximum of 16 bridges per card
with each bridge supporting 30 branches
Multi-Drop Data
Bridging (MDDB)
License
(3HE07354AH)
The 7705 SAR-8/18 Multi Drop Data Bridging (MDDB) RTU License is for
additional nodes using the 3HE07942AA Integrated Services Card (ISC).
One (1) MDDB License is required for each SAR-8/18 in the network using
the ISC card beyond the 25 associated with the 3HE07354AF RTU - MDDB
License. It supports a maximum of 16 bridges per card with each bridge
supporting 30 branches.
Alcatel-Lucent
3HE086790007TQZZA_01
36
UNSUPPORTED FEATURES ON THE 7705 SAR

All hardware and features currently available in Release 6.0 remain supported in
this release.
Support for the following systems that was declared available in earlier
Release 6.1 Software Release Notes has been removed. Support will be added in
a future release.
SAR-Wx w/ 4 GigE,
4 xDSL & AC Power
(3HE07618AA)
SAR-Wx w/ 4 GigE,
4 xDSL, GPS Rx & AC
Power
(3HE07619AA)
Alcatel-Lucent

supports four Gigabit Ethernet ports: three 10/100/1000 Base-X with
SFP ports and one 10/100/1000 Base-T RJ45 port. This variant
supports a 4-port bonded xDSL interface. The 7705 SAR-Wx supports a
110/220 VAC power feed. The device is passively cooled, with a -40 to
55C temperature range. It can be mounted to a wall, pole or strand.
The 7705 SAR-Wx supports 5.0 Gb/s of fullduplex switch capacity.
Some features supported on this platform require a Right-to-Use (RTU)
license. The OS licenses for the 7705 SAR-Wx are sold separately.
supports four Gigabit Ethernet ports: three 10/100/1000 Base-X with
SFP ports and one 10/100/1000 Base-T RJ45 port. This variant
supports a 4-port bonded xDSL interface. The 7705 SAR-Wx supports a
110/220 VAC power feed. The device is passively cooled, with a -40 to
55C temperature range. It can be mounted to a wall, pole or strand.
The 7705 SAR-Wx supports 5.0 Gb/s of fullduplex switch capacity.
This variant of the 7705 SAR-Wx includes an integrated GPS receiver.
Some features supported on this platform require a Right-to-Use (RTU)
license. The OS licenses for the 7705 SAR-Wx are sold separately.
3HE086790007TQZZA_01
37
ENHANCEMENTS
RELEASE 6.1.R7
BGP GRACEFUL
RESTART HELPER
The following are enhancements added to Release 6.1.R7 since Release

6.1.R6.
BGP Graceful Restart Helper is now supported in the VPRN context.
(D.198875)
SAR-H GPS
A performance improvement has been implemented that increases the

ability to remain locked to GPS satellites when the signal quality is
degraded. (D.199412)
SNMP ENGINE BOOT

COUNTER
Prior to this enhancement, the value of snmpEngineBoots (in the

SNMP-FRAMEWORK-MIB.mib and described in RFC 3414) was always
reset to a value of 1 after a full system reboot instead of incremented
by 1 as specified in RFC 3414. With this enhancement, the value of
snmpEngineBoots is incremented by 1 after a system reboot, a CSM
switchover or an snmp engineID change. (D.193482)
RELEASE 6.1.R6
SUPPRESS POWER
FEED MONITORING/
ALARMING
RELEASE 6.1.R5
RFC 3107
LABEL-BGP

6.1.R5.
When a 7705 SAR system is powered via a single power input feed, any
other unconnected power inputs will raise an alarm. In situations
where the use of a single power input feed is intended by the
operator, a configurable option has been added to suppress
monitoring/alarming in each specific power feed on the 7705 SAR
system. This suppression is off by default. (D.188053)

6.1.R4.
This enhancement allows a route reflector to reflect, with next-hopself, VPN-IP routes received from a client to which it has only a BGPlabel tunnel.
In other words, this enhancement enables the option-B model for the
VPN-IPv4 address family (rr-vpn-forwarding) on route reflector
nodes where PE reachability information is exchanged via the BGP
label-IPv4 address family. (D.191785)
Alcatel-Lucent
3HE086790007TQZZA_01
38

TWAMP
It is now possible to change the description of a prefix entry used by

the TWAMP server at any time, even when the server is running.
Previously the server had to be shut down before making such changes
(D.182300)
RELEASE 6.1.R4
There are no new enhancements in this release.
RELEASE 6.1.R3

6.1.R2.
COPY DF-BIT FOR

IPSEC TUNNELS
Enabling this setting on an IPSec tunnel copies the inner packet DF-bit
setting to the IPSec tunnel header. (D.181505)
IKEv2 LOCAL-ID
An IKEv2 local-ID value can be configured for a dynamically keyed

IPSec tunnel. The allowed local-id types are a valid IPv4 address or an
FQDN string. (D.183084)
RELEASE 6.1.R2

6.1.R1.
LACP-TUNNEL
SAR-H
RELEASE 6.1.R1
The SAR-H and SAR-Hc RS-232 asynchronous latency has been reduced.
(D.179289)

6.0.
CLI
Alcatel-Lucent
LACP tunnels are supported on DSL ports on the 7705 SAR-M module
and the 7705 SAR-Wx. (D.175860)
The Invalid L2 Packets packet drop counter has been divided into
the following categories: invalid vlanId, invalid Etype, and others. The
packet header for the invalid vlanId and invalid Etype are captured
and displayed using the new tools dump port x/y/z discard
command. (D.169794)
3HE086790007TQZZA_01
39

SYSTEM
Alcatel-Lucent
The 7705 SAR boot process can be interrupted in the boot.ldr by any
key press received on the console port. An enhancement has been
added that continues the boot process automatically after it has been
interrupted unless a specific sequence of characters (sros and
[enter]) is typed by the operator before a 30-second timer expires.
This enhancement ensures that the boot process will automatically
continue if it was unintentionally interrupted by noise,
misconfiguration or operator error. (D.169006)
3HE086790007TQZZA_01
40
USAGE NOTES
The following information supplements or clarifies information in the manuals
for Release 6.1.R7 of the 7705 SAR.
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)
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.
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.
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 holddown timers be
increased from their default values.
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)
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
Alcatel-Lucent 73xx ISAM and provides superior throughput
capabilities compared to ATM bonding.
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 autocompletion. The user must ensure that the pipe/match command
and any attributes are spelled correctly.
Alcatel-Lucent
3HE086790007TQZZA_01
41

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):
Example: Capture all lines that include "echo" and redirect

the output to a file on the compact flash:
o
Example: Display all lines that do not include "echo":

o
admin display-config | match invert-match "echo"
Example: Display the first match of "vprn" in the

configuration file:
o
DIFFERENTIAL CLOCK
RECOVERY (DCR)
admin display-config | match "echo" > cf3:\echo_list.txt
admin display-config | match max-count 1 "vprn"
When a port on the 16-port T1/E1 ASAP Adapter card v2 or 32port

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 Cpipes payload size of channel group 1:
for DCR timestamp frequency 77.76 MHz: payload size = 2 x N x

(number of timeslots), where N = 1, 2, 3,
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)
EFM OAM SUPPORT ON
ALL DSL PORTS
IP FILTERS & NON-IP

PACKETS
IS-IS
EFM OAM can currently be enabled on any DSL port. Note that the
current EFM OAM implementation on Alcatel-Lucent 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.
IP filters with a default-action of discard will not discard non-IP
packets such as ARP and IS-IS. (D.40976)
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)
JUMBO FRAMES
Alcatel-Lucent
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.
3HE086790007TQZZA_01
42

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)
LDP INTERFACE
PARAMETERS
MANAGEMENT
Hello and keepalive parameter modifications do not take effect until

a shutdown/no shutdown command is performed on the LDP
session.
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.
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)
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:
0 to 127 is used for the keepalive function

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)
MPLS/RSVP
The current bypass binding selection logic is the following:

For non-Strict environment:
a) Manual CSPF disjoint bypass
b) Manual CSPF !disjoint bypass
c) Dynamic CSPF disjoint bypass
d) Dynamic CSPF !disjoint bypass
Alcatel-Lucent
3HE086790007TQZZA_01
43

For Strict environment:
a) Manual CSPF disjoint bypass
b) Dynamic CSPF disjoint bypass
The above binding order has two collateral/detrimental effects when
the non-Strict option is selected:
1) In the presence of a disjoint Dynamic Bypass, a non-disjoint
Manual Bypass may be selected instead.
2) 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.
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:
0.0.0.0/8 or longer
127.0.0.0/8 or longer
224.0.0.0/4 or longer (used for multicast only)
240.0.0.0/4 or longer
Any other prefixes that need to be filtered can be filtered explicitly
using route policies.
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)
Alcatel-Lucent
NAT
"Allow-Directed-Broadcast" on the interface is not supported when

NAT is enabled on the router. (D.173293-MI)
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)
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)
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.
3HE086790007TQZZA_01
44

VPRN
Alcatel-Lucent
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 nonexistent objects (prefix lists, community lists, etc). (D.60879)
3HE086790007TQZZA_01
45
SOFTWARE UPGRADE PROCEDURES

The following sections contain information for upgrading to the 6.1.R7 software
version. In particular, there are sections that describe the following:
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 6.1.R7
STANDARD SOFTWARE UPGRADE PROCEDURE

Procedure for performing a standard, service-affecting upgrade including
updating of firmware images
SOFTWARE BUNDLES
There are two software bundles available:
7705-TiMOS.6.1.R7.zip - 7705 SAR Release 6.1 OS software with MIBs
7705-TiMOS.6.1.R7.MWA.zip 7705 SAR Release 6.1 OS software with

MIBs and the MPR-e radio software. Before a microwave link can be
configured in single NE mode, the 7705 SAR Release 6.1 OS software
bundle, which includes the MPR-e radio software, must be downloaded to
the 7705 SAR-8 or 7705 SAR-18.
The following table summarizes the upgrade capability from previous releases to
this release. Customers wishing to upgrade from Release 4.0 or lower to Release
6.1 must first upgrade to any 5.0 Release using the Software Upgrade Procedure
as described in the Release Notes for that release. The upgrade to Release 6.1 can
then proceed.
Note: SAR-H R5.0 (Release Notice 3HE080840004TQZZA_01) is a separate software
stream that will be discontinued at a future date. The Standard Software Upgrade
Procedure is not supported from this release. For assistance in upgrading from SAR-H
R5.0 to SAR R6.1, please contact your Alcatel-Lucent representative.
Alcatel-Lucent
3HE086790007TQZZA_01
46

Table 10. 7705 SAR Upgrade Capability
Release #
Upgrade From
Supported
Upgrade
Software Upgrade Notes For

Standard Upgrade To This Release
Shipped
Firmware
Release 5.0.R1
Standard
Notes 1, 2, 3, 4, 5, 6, 8, 9, 10, 12, 14,

18
0x28(v40)
Release 5.0.R2
Standard
Notes 1, 5, 6, 8, 9, 10, 12, 14, 18
0x2a(v42)
Release 5.0.R3
Standard
Notes 1, 5, 6, 8, 9, 10, 12, 14, 16, 17,

18
0x2a(v42)
Release 5.0.R4
Standard
Notes 1, 5, 6, 8, 9, 10, 12, 14, 16, 17,

18
0x2a(v42)
Release 5.0.R5
Standard
Notes 1, 8, 9, 10, 12, 14, 16, 17, 18
0x2a(v42)
Release 5.0.R6
Standard
Notes 1, 8, 9, 10, 12, 14, 16, 17, 18
0x2a(v42)
Release 5.0.R7
Standard
Notes 1, 7, 8, 9, 10, 12, 14, 16, 17, 18
0x2a(v42)
Release 5.0.R8
Standard
Notes 1, 7, 8, 9, 10, 12, 14, 16, 17, 18
0x2a(v42)
Release 5.0.R9
Standard
Notes 1, 7, 8, 9, 10, 12, 14, 16, 17, 18
0x2a(v42)
Release 5.0.R10
Standard
Notes 1, 7, 8, 9, 10, 12, 14, 16, 17, 18
0x2a(v42)
Release 5.0.R11
Standard
Notes 1, 7, 8, 9, 10, 12, 14, 16, 17, 18
0x2a(v42)
Release 6.0.R1
Standard
Notes 1, 11, 12, 14, 16, 17, 18
0x2b(v43)
Release 6.0.R2
Standard
Notes 1, 11, 12, 14, 16, 17, 18
0x2b(v43)
Release 6.0.R3
Standard
Notes 1, 12, 14, 16, 17, 18
0x2b(v43)
Release 6.0.R4
Standard
Notes 1, 12, 14, 16, 17, 18
0x2b(v43)
Release 6.0.R5
Standard
Notes 1, 12, 13, 14, 16, 17, 18
0x2b(v43)
Release 6.0.R6
Standard
Notes 1, 12, 13, 14, 16, 17, 18
0x2c(v44)
Release 6.0.R7
Standard
Notes 1, 12, 13, 16, 17, 18
0x2c(v44)
Release 6.1.R1
Standard
Notes 13, 14, 15, 16, 17, 18
0x2d(v45)
Release 6.1.R2
Standard
Notes 13, 14, 15, 16, 17, 18
0x2d(v45)
Release 6.1.R3
Standard
Notes 14, 15, 16, 17, 18
0x2d(v45)
Release 6.1.R4
Standard
Notes 14, 15, 16, 17
0x2d(v45)
Release 6.1.R5
Standard
ISSU
Notes 15, 16, 17
0x2d(v45)
Release 6.1.R6
Standard
ISSU
Notes 16, 17
0x2d(v45)
Alcatel-Lucent
3HE086790007TQZZA_01
47
SOFTWARE The following section lists notes for upgrading from prior versions of the
UPGRADE NOTES 7705 SAR to this release.
Note 1:
FIRMWARE UPDATE
Note 2:
IES INTERFACES IN
OSPFv3 PROTOCOL
MUST BE REMOVED
PRIOR TO THE
UPGRADE
Note 3:
SAR-M WITH GPON OR
DSL MODULES MUST
SET DOWN-WHENLOOPED USEBROADCAST-ADDRESS
PRIOR TO THE
UPGRADE
Note 4:
OSPF CONFIGURED IN
VPRN MUST BE
REMOVED PRIOR TO
THE UPGRADE
Note 5:
X.21 PORT SETTINGS
MIGHT HAVE TO BE
UPDATED PRIOR TO
THE UPGRADE
Note 6:
SERIAL DATA CARD
PORTS MUST HAVE
UNSUPPORTED
CONFIGURATIONS
REMOVED PRIOR TO
THE UPGRADE
Alcatel-Lucent
The 7705 SAR OS Release 6.1.R7 requires a firmware update to version

0x2D.
Follow the steps in the STANDARD SOFTWARE UPGRADE PROCEDURE to
update the firmware images.
Configuring an IES interface with the OSPFv3 protocol in R5.0.R1 is not
supported. If a customer configured an IES interface with OSPFv3, the
configuration must be removed prior to performing an upgrade to R6.0 or
R6.1. (P.623389)
When upgrading from R5.0.R1 on a SAR-M with xDSL or GPON modules,

the operator must set the down-when-looped use-broadcast-address
configuration on all the DSL or GPON ports that currently have the downwhen-looped component enabled. The down-when-looped component
enabled is not a supported configuration. (P.621220, P.621226)
Configuring OSPF in VPRN in R5.0.R1 is not supported. If a customer

configured OSPF in VPRN, this access side OSPF instance must be
removed prior to performing an upgrade to R6.0 or R6.1. (P.624239)
If the X.21 speed is configured for subrate (< 64 kb/s) and the signaling is
configured for end-to-end, then prior to the upgrade, the operator must
edit the config file and place the speed setting before the signaling
setting. (P.635029)
Serial Data Interface (SDI) card ports with cHDLC or frame relay
encapsulation are not supported under IES SAPs. If a customer has
configured SDI ports with cHDLC or frame relay encapsulation and bound
them to an IES SAP, this configuration must be removed prior to
performing the upgrade. (P.636362)
3HE086790007TQZZA_01
48

Note 7:
8-PORT VOICE &
TELEPROTECTION
CARD: THE FXS PORT
RING-GENERATION
CONFIGURATION MUST
BE UPDATED PRIOR TO
THE UPGRADE
Note 8:
PERFORM ADMIN SAVE
PRIOR TO THE
UPGRADE WITH DS3
CHANNELIZED
ADAPTER CARD
Note 9:
NEWLY ENFORCED
LIMITS MUST BE
UPDATED BEFORE
UPGRADE
FXS port no ring generation is not supported. If a customer has this

configured, it should be changed to a valid configuration prior to the
upgrade. (P.645298)
When channelized to DS1 or E1, the clock-source adaptive configuration

is not supported. However, an admin save detail command will select
adaptive for the default clock-source. Prior to the upgrade, perform an
admin save to ensure this does not occur. (P.644709)
The following limits are now enforced:
VPLS instances per node
VPLS SAPs per XMDA
Number of unique IP filters per system
Number of BGP_PEERS per node
If these limits have been exceeded, upgrading to this maintenance load

will fail.
Such configurations must be updated before performing an upgrade.
Please contact Alcatel-Lucent for specific limits.
Note 10:
CFLOWD MIGHT HAVE
TO BE UPDATED PRIOR
TO THE UPGRADE
Note 11:
1588 PTP CLOCK AS
TIME REFERENCE
MIGHT HAVE TO BE
REMOVED PRIOR TO
THE UPGRADE
Alcatel-Lucent
The command configure system security source-address application

cflowd system was accepted prior to R6.0. This command is
unsupported and is rejected in the current release.
Prior to the upgrade, the operator must remove the source address for
cflowd if it exists. (P.657233)
In R6.0.R1 and R6.0.R2, the CLI allowed the PTP time reference from TC
(transparent clock) to be configured when the same clock was previously
configured as BC/ordinary clock. If the configuration is saved and
executed or the node is rebooted, the configuration will fail to load
because the time-ref-priority configured is not relevant for TC.
Prior to the upgrade, remove the PTP clock as the time reference after
changing the clock type to transparent e2e. (P.656937)
3HE086790007TQZZA_01
49

Note 12:
FOR ACCESS
INTERFACES WITH
DOT1Q
ENCAPSULATION:
CONFIGURE THE PORT
ETHERTYPE OF THE
CONNECTED NODES
TO 0X8100 PRIOR TO
THE UPGRADE
Note 13:
IPV6 EGRESS FILTER
MIGHT HAVE TO BE
REMOVED PRIOR TO
THE UPGRADE
Note 14:
PERFORM ADMIN SAVE
PRIOR TO THE
UPGRADE WITH
4-PORT OC3/STM1
CLEAR CHANNEL
ADAPTER CARD
Note 15:
EFM TUNNELING FOR
HYBRID PORTS MUST
BE REMOVED PRIOR
TO THE UPGRADE
Note 16:
SAR-Wx UPGRADE
RESULTS IN CHANGED
PORT MAC ADDRESSES
Note 17:
SSM CONFIGURED
WITH UNFRAMED E1
MUST BE REMOVED
PRIOR TO THE
UPGRADE
Note 18:
IS-IS OVERLOAD
TIMEOUT
CONFIGURATION
Alcatel-Lucent
Prior to R6.1.R1, VPRN/IES/IP access interfaces with dot1q encapsulation

always sent ARP requests/responses with Ethertype=0x8100 regardless of
the configured Ethertype of the port. If a 7705 SAR VPRN/IES/IP
access interface is connected to another 7705 SAR VPRN/IES/IP access
interface with a non-default Ethertype configured on the port, before
upgrading to R6.1 the port Ethertypes should be changed to the
default 0x8100. Otherwise, the interface will send and only accept ARP
requests/responses that match the configured dot1q Ethertype of the
port. Once the upgrade is complete, the Ethertypes may be changed
back to non-default values.
In previous releases, IPv6 egress filters could be applied to adapter cards
that do not support IPv6. In the current release, if an IPv6 egress filter is
applied to an adapter card that does not support IPv6, it should be
removed prior to the upgrade. All Ethernet adapter cards and the 4-port
OC3/STM1 Clear Channel Adapter card support IPv6.
For the 4-port OC3/STM1 Clear Channel Adapter card (mda-type
a4-oc3), the clock-mode adaptive configuration is not supported.
However, an admin save detail command will select adaptive for the
default clock mode. Prior to the upgrade, perform an admin save to
ensure this does not occur. (P.696830, D.187528)
In previous releases, EFM tunneling could be enabled on a hybrid port. In

the current release, that is not permitted. Any such configurations must
be removed prior to the upgrade. (D.192115)
Upgrading a SAR-Wx to 6.1.R7 will result in changed port MAC addresses,

which may affect MAC filters that have already been applied. After the
upgrade, update any applicable src-mac and/or dst-mac
configurations under the applied MAC filters. (D.202077)
In previous releases, SSM could be configured with unframed E1. This
unsupported configuration is now blocked. Any such configurations must
be removed prior to the upgrade. (D.197134)
A defect was introduced in 6.1.R4 that requires IS-IS overload to have a

timeout value explicitly configured. Until this defect is fixed, when
upgrading to a release with this defect, ensure that a valid timeout value
is configured for IS-IS overload. If the desired behavior is that IS-IS
remains in the overload state indefinitely, configure isis no overload
and isis overload-on-boot without a timeout value prior to the
upgrade.
3HE086790007TQZZA_01
50

The isis overload-on-boot command will cause IS-IS to go into the
overload state indefinitely. (D.203662-MA)
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 10
If any of the above criteria do not apply, the STANDARD SOFTWARE

UPGRADE PROCEDURE must be performed.
Notes:
Although the software upgrade can be performed using a remote terminal session,
Alcatel-Lucent recommends that the software upgrade procedure be performed at the
system CONSOLE device where there is physical access to the 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
Alcatel-Lucent Technical Assistance Center.
Alcatel-Lucent 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.
Alcatel-Lucent 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.
STEP 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.
Alcatel-Lucent 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.
STEP 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-6.1.R7. 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. If the 7705 SAR has attached MPR-e radios in Single NE mode, ensure that the
7705 SAR Release 6.1 Software bundle includes MPR-e software, that is,
7705-TiMOS.6.1R7.MWA.zip.
Alcatel-Lucent
3HE086790007TQZZA_01
51

STEP 3
Copy boot.ldr to the Root Directory on cf3:

The BOOT Loader file is named boot.ldr. This file must be copied to the root
directory of the cf3: device.
STEP 4
Modify the Boot Options File to Point to the New Image

The Boot Options File (bof.cfg) is read by the BOOT Loader and indicates primary,
secondary and tertiary locations for the image file.
STEP 5
The bof.cfg should be modified as appropriate to point to the image file for the
release to be loaded.
Use the bof save command to save the Boot Options File modifications.
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.
STEP 6
Reboot the Standby CSM

Use the admin reboot upgrade standby now command to reboot the inactive CSM.
In the sample output 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
===============================================================================
Card State
===============================================================================
Slot/ Provisioned
Equipped
Admin Operational
Num
Num Comments
Id
Type
Type
State State
Ports MDA
------------------------------------------------------------------------------1
iom-1g
iom-1g
up
up
6
1/1
a16-chds1
a16-chds1
up
up
16
1/5
a8-eth
a8-eth
up
up
8
A
csm-1g
csm-1g
up
up
Active
B
csm-1g
csm-1g
up
up
Standby
===============================================================================
A:router1# admin reboot standby now
===============================================================================
Card State
===============================================================================
Slot/ Provisioned
Equipped
Admin Operational
Num
Num Comments
Id
Type
Type
State State
Ports MDA
------------------------------------------------------------------------------1
iom-1g
iom-1g
up
up
6
1/1
a16-chds1
a16-chds1
up
up
16
1/5
a8-eth
a8-eth
up
up
8
A
csm-1g
csm-1g
up
up
Active
B
csm-1g
up
down
Standby
Alcatel-Lucent
3HE086790007TQZZA_01
52

STEP 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.
===============================================================================
Card State
===============================================================================
Slot/ Provisioned
Equipped
Admin Operational
Num
Num Comments
Id
Type
Type
State State
Ports MDA
------------------------------------------------------------------------------1
iom-1g
iom-1g
up
up
6
1/1
a16-chds1
a16-chds1
up
up
16
1/5
a8-eth
a8-eth
up
up
8
A
csm-1g
csm-1g
up
up
Active
B
csm-1g
csm-1g
up
synching
Standby
===============================================================================
When the standby CSM has completely synchronized, the standby CSM will indicate a
state of ISSU.
===============================================================================
Slot/ Provisioned
Equipped
Admin Operational
Num
Num Comments
Id
Type
Type
State State
Ports MDA
------------------------------------------------------------------------------1
iom-1g
iom-1g
up
up
6
1/1
a16-chds1
a16-chds1
up
up
16
1/5
a8-eth
a8-eth
up
up
8
A
csm-1g
csm-1g
up
up
Active
B
csm-1g
csm-1g
up
ISSU
Standby
===============================================================================
STEP 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.
STEP 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.
Alcatel-Lucent
3HE086790007TQZZA_01
53

STEP 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
Equipped
Admin
Operational
Mda-type
Mda-type
State
State
------------------------------------------------------------------------------1
1
a16-chds1
a16-chds1
up
ISSU
5
a8-eth
a8-eth
up
ISSU
===============================================================================
STEP 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
Equipped
Admin Operational
Num
Num Comments
Id
Type
Type
State State
Ports MDA
------------------------------------------------------------------------------1
iom-1g
iom-1g
up
up
6
1/1
a16-chds1
a16-chds1
up
ISSU
16
116 min
1/5
a8-eth
a8-eth
up
ISSU
8
116 min
A
csm-1g
up
down
Standby
B
csm-1g
csm-1g
up
up
Active
===============================================================================
Use the clear mda 1/<n> command to reset an adapter card.

The sample output 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
Equipped
Admin
Operational
Mda-type
Mda-type
State
State
------------------------------------------------------------------------------1
1
a16-chds1
up
provisioned
5
a8-eth
a8-eth
up
ISSU
===============================================================================
Alcatel-Lucent
3HE086790007TQZZA_01
54

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
Equipped
Admin
Operational
Mda-type
Mda-type
State
State
------------------------------------------------------------------------------1
1
a16-chds1
a16-chds1
up
up
5
a8-eth
a8-eth
up
ISSU
===============================================================================
When all of the adapter cards have been rebooted, the ISSU is complete.
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.
Notes:
Although the software upgrade can be performed using a remote terminal session,
Alcatel-Lucent recommends that the software upgrade procedure be performed at the
system CONSOLE device where there is physical access to the 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 AlcatelLucent Technical Assistance Center.
Alcatel-Lucent 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.
Alcatel-Lucent recommends the removal of unnecessary files from the compact flashes.
Alcatel-Lucent
3HE086790007TQZZA_01
55

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.
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.
Alcatel-Lucent 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 is a 7705 SAR-F, failure to follow the
upgrade process may require that the node be returned to Alcatel-Lucent for service as
there is no customeraccessible compact flash on the 7705 SAR-F. Additional details
are outlined in Technical Alert TA 11-0698.
STEP 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.
Alcatel-Lucent 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.
STEP 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-TiMOSR6.1.R7. 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.
If the 7705 SAR has attached MPR-e radios in Single NE mode, ensure that the 7705
SAR Release 6.1 Software bundle includes MPR-e software, that is,
7705-TiMOS.6.1R7.MWA.zip.
STEP 3
Copy boot.ldr to the Root Directory on cf3:

The BOOT Loader file is named boot.ldr. This file must be copied to the root
directory of the cf3: device.
STEP 4
Modify the Boot Options File to 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.
Alcatel-Lucent
3HE086790007TQZZA_01
56

STEP 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
STEP 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.
STEP 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 may become inoperable and therefore need to be returned to
Alcatel-Lucent for repair.
The sample output below shows a 7705 SAR running 5.0.R1 software performing an
automatic firmware upgrade with the 6.1.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#
Resetting...OK
Alcatel-Lucent
3HE086790007TQZZA_01
57
Alcatel 7705 Boot ROM. Copyright 2000-2011 Alcatel-Lucent.

All rights reserved. All use is subject to applicable license agreements.
Build: X-5.0.R1 on Tue Oct 18 21:15:48 EDT 2011 by csabuild
Version: 0x28
Starting CPU/Switch card
Performing Data Bus Test... Passed.
Performing Local RAM Test (1st 2MB)... Passed.
COLD boot on processor #1
CPLD revision is 0x0F
?Preparing for jump to RAM...
Starting bootrom RAM code...
Bootrom version is v40 (0x28)
CPU BIST check passed.
Validating SDRAM from 0x41e00000 to 0x42000000
Testing SDRAM from 0x0000000002200000 to 0x0000000041e00000
Testing Compact Flash ... OK (SMART CF)
CPLD revision is v15 (0x0f)
Board Serial Number is 'NS083241197'
Chassis Serial Number is 'NS083940043'
Searching for boot.ldr on local drives:
Searching cf3 for boot.ldr...
******************************************************************************
Total Memory: 1GB Chassis Type: sar8 Card Type: corona_r1
TiMOS-L-6.1.B1-8 boot/hops ALCATEL-LUCENT SAR 7705
Copyright (c) 2000-2014 Alcatel-Lucent.
All rights reserved. All use subject to applicable license agreements.
Built on Thu Jan 16 22:22:31 EST 2014 by csabuild in /rel6.1/b1/B1-8/panos/main
TiMOS BOOT LOADER
** Boot ROM is too old; is v40, should be v45 **
Chassis firmware will be upgraded automatically
Time from clock is FRI JAN 17 16:10:08 2014 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.xx/home/csahwtest8/images/both.tim
primary-config ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest8/images/dut-a.cfg
address
xxx.xxx.xxx.xxx/24 active
address
xxx.xxx.xxx.xxx/24 standby
primary-dns
xxx.xxx.xxx.xxx
dns-domain
ca.alcatel.com
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.1
autonegotiate
duplex
full
speed
100
wait
3
persist
on
console-speed 115200
Primary image location: ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest8/images/both.tim
Initializing management port tme0 using IP addr xxx.xxx.xxx.xxx
Initial DNS resolving preference is ipv6-first
init mgmt port using FE80::221:5FF:FE7E:A2CC/64
init mgmt port using 3000::8A78:AC33/64
Loading image ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest8/images/both.tim
images_v1:(449648)
File version B-6.1.B1-8, Thu Jan 16 22:34:17 EST 2014 by csabuild in /rel6.1/b1/B1-8/panos/main
6 ROM images loaded from .tim file
Checking for firmware upgrades...
Embedded BOOT ROM: 45/X-6.1.B1-8 on Thu Jan 16 22:21:45 EST 2014 by csabuild
Sl Type
A iom-sar
Alcatel-Lucent
Serial # CPLD up? BOOT ROM

up?
NS083241197 0F 40/X-5.0.R1 on Tue Oct 18 21:15:48 E Y
3HE086790007TQZZA_01
58

*********************************
** 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) *****
Not expecting BDB Write Acks from this slot
PROGRAMMING BOOT ROM UPGRADE SPACE
Erasing 0x30000 bytes at address 0x1FC80000: 30000 OK
Programming 0x23D8C bytes at address 0x1FC80000: 23D8C OK
*********************************************
** CARD PROGRAMMING COMPLETED SUCCESSFULLY **
*********************************************
Resetting...OK
Alcatel 7705 Boot ROM. Copyright 2000-2011 Alcatel-Lucent.

Build: X-5.0.R1 on Tue Oct 18 21:15:48 EDT 2011 by csabuild
Version: 0x28
Bootrom version is v40 (0x28)
Upgrading BOOT rom to v45 / X-6.1.B1-8 on Thu Jan 16 22:21:45 EST 2014 by csabu
Programming 427152 bytes at address 0xbfc00000
!........!........!........!........!........!........!........
Rebooting...
Alcatel-Lucent 7705 Boot ROM. Copyright 2000-2014 Alcatel-Lucent.
Build: X-6.1.B1-8 on Thu Jan 16 22:21:37 EST 2014 by csabuild
Version: 0x2D
Bootrom version is v45 (0x2d)
Searching for boot.ldr on local drives:
Searching cf3 for boot.ldr...
******************************************************************************
Alcatel-Lucent
3HE086790007TQZZA_01
59

TiMOS-L-6.1.B1-8 boot/hops ALCATEL-LUCENT SAR 7705
TiMOS BOOT LOADER
Switching serial output to sync mode... done
Contents of Boot Options File on cf3:
primary-image ftp://*:*@xxx.xxx.xxx.xx/home/csahwtest8/images/both.tim
primary-config ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest8/images/dut-a.cfg
address
xxx.xxx.xxx.xxx/24 active
address
xxx.xxx.xxx.xxx/24 standby
primary-dns
xxx.xxx.xxx.xxx
dns-domain
ca.alcatel.com
static-route xxx.xxx.0.0/16 next-hop xxx.xxx.xxx.1
autonegotiate
duplex
full
speed
100
wait
3
persist
on
console-speed 115200
Primary image location: ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest8/images/both.tim
Initializing management port tme0 using IP addr xxx.xxx.xxx.xxx
init mgmt port using FE80::221:5FF:FE7E:A2CC/64
init mgmt port using 3000::8A78:AC33/64
Loading image ftp://*:*@xxx.xxx.xxx.xxx/home/csahwtest8/images/both.tim
Version B-6.1.B1-8, Thu Jan 16 22:34:17 EST 2014 by csabuild in /rel6.1/b1/B1-8/panos/main
text:(79945716-->140361392) + data:(3172836-->18096384)
Executing TiMOS image at 0x2800000
TiMOS-B-6.1.B1-8 both/hops ALCATEL-LUCENT SAR 7705
___
___
/\ \
/\__\
___
___
/\ \
/\ \
\:\ \
___
/::| |
/::\ \
/::\ \
\:\ \
/\__\ /:|:| |
/:/\:\ \
/:/\:\ \
/::\ \ _\/__/ /:/|:|__|__ /:/ \:\ \ _\:\~\:\ \

/:/\:\__\ /\__\ /:/ |::::\__\ /:/__/ \:\__\ /\ \:\ \:\__\
/:/ \/__/ /:/ / \/__/~~/:/ / \:\ \ /:/ / \:\ \:\ \/__/
/:/ /
\/__/
/:/ /
\/__/
/:/ / \:\ /:/ / \:\ \:\__\

/:/ /
/:/ /
\/__/
\:\/:/ /
\::/ /
\/__/
\:\/:/ /
\::/ /
\/__/
Plock checks disabled (no SMP kernel)

Rialto FPGA, version: 0x0000002a
Alcatel-Lucent
3HE086790007TQZZA_01
60

STEP 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
Alcatel-Lucent Technical Assistance Center for information on corrective actions.
Alcatel-Lucent
3HE086790007TQZZA_01
61
CONTROL AND SWITCHING MODULE: CSMv1 to CSMv2 MIGRATION

Using the software release as per this Release Note and following the guidelines
indicated below, a configuration file created on a CSMv1 may be loaded onto a
CSMv2. In this way, an installed 7705 SAR node can be migrated from
CSMv1(s) to CSMv2(s) without needing to rebuild the entire configuration file.
Note: If installing a CSMv2 into a SAR-8 v1 chassis built between 2008 and 2009, the
chassis may contain a hardware type that is not recognized by the CSMv2 as being
compatible. Please refer to TA 14-0143b for steps to take before attempting the migration
from CSMv1 to CSMv2.
Steps for Migrating from CSMv1 to CSMv2

1. Make any necessary configuration changes to ensure that the CSMv1 config
file is compatible with a CSMv2:
a) Remove any configured IP interfaces from 16-port T1/E1 ASAP Adapter
cards (3HE02775AA) OR replace any 16-port T1/E1 ASAP cards
(3HE02775AA) with 16-port T1/E1 ASAP Adapter cards v2
(3HE02775AB) or 32-port T1/E1 ASAP Adapter cards v2
(3HE02781AA).
b) CSMv2 does not support an External Sync Output frequency of 5 MHz.
c) Issue an Admin Save command.
2. Copy config and .bof files from CSMv1 to CSMv2. Alternately, remove the
compact flash device from the CSMv1 and install it in the CSMv2.
3. Install CSMv2 in the node.
Alcatel-Lucent
3HE086790007TQZZA_01
62
KNOWN LIMITATIONS
The following are the known limitations for this release.
Note: bracketed () references are internal tracking numbers.
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)
1588
1588 over a spoke SDP terminated into an IES service is not

supported. 1588 is supported over IES interface SAPs. (P.657255)
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
port(s) 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, then the MBS and CBS
parameters in the network queue policy should be reconfigured to
smaller values after the upgrade. (P.602283)
2PORT 10GIGE
(ETHERNET) XFP
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 adddrop port
of the 2port 10GigE (Ethernet) XFP Adapter card, the corresponding
port queue drop counters will be inaccurate while in the congested
state. (P.650451)
Alcatel-Lucent
3HE086790007TQZZA_01
63

2PORT OC3/STM1
CHANNELIZED
ADAPTER CARD
When changing the SONET/SDH port framing configuration from

SONET to SDH (or vice versa) on the 2port 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)
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)
8-PORT VOICE &

TELEPROTECTION
CARD AND 6-PORT
E&M ADAPTER CARD
802.1X EAP
APS
ATM/IMA
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)
RADIUS servers for accounting can be configured under the 802.1x

EAP RADIUS policy, but it is not supported. (P.599930)
In some cases of RDI-L, the transmitted K1/K2 bytes on the wire may
differ from those maintained by the CSMs APS controller (as
displayed on the CLI). (D.36537)
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.
Alcatel-Lucent
3HE086790007TQZZA_01
64

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)
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)
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 type np is not able to support a BFD configuration that has a
detection time of more than 3000 ms. Currently, in the case where
the remote BFD configuration exceeds this 3000 ms limit, the local
BFD session will be held down in the Down state and a log message
will be issued indicating error of unsupported BFD configuration. The
holding down of the BFD session currently causes the client protocols
(for example, OSPF) to bounce from the adjacency establishment.
The following is an example of a BFD configuration that will have the
issue mentioned above.
Local (SAR): tx/rx/m/type = 500/400/3/np <----> Remote:
tx/rx/m = 600/700/8
Then, the local detection time at the SAR node will be:
localNegTx = max[ localTx, remoteRx] = max[500, 700] = 700
remoteNegTx = max[ remoteTx, localRx] = max[600, 400] = 600
localDetctTime = remoteMult * remoteNegTx = 8 * 600 = 4800 >
3000ms.
As a workaround, use BFD type null instead. (P.646769)
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.
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 the router bgp with the nexthop 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)
Alcatel-Lucent
3HE086790007TQZZA_01
65

Under rare circumstances, multiple BGP peer sessions between the
same two systems may not be successfully established without a
local-address explicitly configured for each peer. (D.77884)
The remove-private command currently causes affected BGP
peerings to be reset and reestablished. (D.16727)
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 prefixlist with from protocol direct. (D.89371)
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
should not be used for signaling purposes for channels 1 to 15.
(P.538480)
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)
When logged in with the Telnet client supplied with Windows and
issuing an SSH to a remote server, an unexpected carriage return
may be sent, causing the SSH connection to fail. (D.50657)
COPPER SFPs
DCR AND MEF 8
Alcatel-Lucent
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)
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.
3HE086790007TQZZA_01
66

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)
DHCP
If there are more than 20 DHCP clientenabled 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.
DIFFERENTIAL CLOCK
RECOVERY (DCR)
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.
Lease start time

After a power cycle, the lease start time will be inaccurate.
This will be automatically corrected when the lease is
renewed.
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)
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)
When a differential DS1 on a CEM adapter card is deleted and
reconfigured as a differential E1, the recovered clock on the E1 may
go into holdover. The clock recovery can be restored on the E1 with
the clear mda command. [D.109738]
ETHERNET ADAPTER
CARDS
On rare occasions, collision counters on the 8-port Ethernet Adapter

card, 8-port Ethernet Adapter card v2, and SAR-F Ethernet ports 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-framegap 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)
Alcatel-Lucent
3HE086790007TQZZA_01
67

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 Alcatel-Lucent. (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. (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 8port
Ethernet Adapter card, 8port Ethernet Adapter card v2, and 7705
SAR-F. (P.564292)
GPON
Autonegotiation must be explicitly disabled on the GPON SFP port in

order for traffic to pass properly. (D.170170)
IEEE 1588V2
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)
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)
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)
IP FILTERS
IP/MPLS
If filter logs are used with ingress spokeSDP filters with Layer 2 to
Layer 3 spoke termination, incorrect source MAC information is
populated in the filter log. (P.624468, D.170830)
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/lsp-trace octet size of 2084. (P.556573)
If triggered-policy is configured, LDP policies are not dynamically
evaluated for changes in FECs. (D.71830)
Alcatel-Lucent
3HE086790007TQZZA_01
68

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)
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)
IP STATISTICS
Network APS IP interface statistics will be inaccurate following an

APS switch. (P.620827)
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)
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
size parameter greater than 2106 bytes. This is due to the 7705 SAR
limitation that the PIR of the ingress control queue for ICMP packets
is set at 1 Mb/s. Rapid pings to 7705 SAR nodes should only be used
with packet sizes no greater than 2106 bytes. (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)
LDP
Modifying the Hello LDP timers while the Hello adjacency is up does
not come into effect until the adjacency bounces. However, after
two HighAvailability switchovers, the active CSM will start using the
new timer value. (D.108407, P.604751, D.170276)
A passive LDP session will remain in GR Reconnect if the TCP
session drops but valid UDP hellos are still received. (D.123019)
If the Hello hold-timer of a T-LDP session is modified, the change
will correctly not take effect until the T-LDP session has bounced. It
will, however, take effect after a double-CSM High-Availability
switchover, which may result in one of the following unexpected
symptoms:
Alcatel-Lucent
The T-LDP session bounces once if there is only a T-LDP session

between the two nodes involved.
The T-LDP keeps bouncing until it is manually cleared if there

is both a T-LDP and ILDP session between the two nodes
involved. (D.112617)
3HE086790007TQZZA_01
69

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)
Threshold monitoring results for cflash-cap and memory-use might
be incorrect if a negative threshold is used. (P.532095)
The management port may not work properly when connected to a
legacy 10 Mb/s halfduplex hub or Ethernet switch that sends frames
with an odd nibble preamble. (P.550709)
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)
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.
Alcatel-Lucent
3HE086790007TQZZA_01
70

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.
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 nodeprotect 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 pointtopoint and both physical links are
connected to the same Layer 2 switch. (P.608181)
MULTISEGMENT 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)
NAT
Security zones may be applied to IES, VPRN and R-VPLS, but the
supported configurations for VPRNs do not include GRE tunnels to
the remote PE; therefore, if a user configures NAT with a VPRN
service, the traffic on the ingress SAP associated with the VPRN will
not be dropped. The normal behavior for unsupported configurations
with NAT is for the traffic to be dropped and for the Unsupported
Svc counter to increment in the interface statistics.
The traffic in the outbound direction will be forwarded without the
IP header translated through the NAT function; however, no NAT
session is created on the 7705 SAR. The traffic in the reverse
direction will be dropped because the NAT session has not been
created, and the No NAT Session counter will be incremented in
the interface statistics. (D.175496)
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)
Alcatel-Lucent
3HE086790007TQZZA_01
71

OAM
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-toend cells. (D.75052)
If a MAC ping or MAC trace request is sent with <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 replymode 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)
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)
When an SDP is configured with a far-end IP address that is not the
system address (for example, a network interface address), an sdpping over that SDP will get a response indicating that the farend
responder ID has changed. (P.663499, D.170349)
OSPF
Alcatel-Lucent
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)
3HE086790007TQZZA_01
72

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/RSVPdisabled in order for CSPF to work correctly and should
be removed from the TE database. (D.15127)
PIM-SSM
Discarded RPF mismatch packets are recorded under Inv IP Packets

for show port <port>, instead of under show router pim group
detail. (P.660454, D.170831)
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. Note that this causes no known interoperability issues since
this packet is still destined for an IP address on this last-hop router.
(D.37923)
Thirdparty 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)
QOS
For sanitized operation of the datapath, the buffers 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)
RADIUS
In defining RADIUS Vendor Specific Attributes (VSAs), the TiMetraDefault-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 inband 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 inband RADIUS servers, if a sourceaddress 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.
When RADIUS or TACACS+ accounting is enabled, it may take longer
than expected to generate a tech-support file using the admin
tech-support command. (D.126499, D.178244)
Alcatel-Lucent
3HE086790007TQZZA_01
73

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)
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)
RVPLS
1588 PTP control packets will not be processed by the protocol if the
packets are received via an RVPLS 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 RVPLS 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)
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)
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)
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)
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)
Alcatel-Lucent
3HE086790007TQZZA_01
74

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 Alcatel-Lucent 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).
This limitation applies to the SAR-18 platform only. When two traptargets 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-MI)
SPANNING TREE
SSH
SYNCHRONIZATION
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.
When using a Telnet or SSH session, redirecting the output of a CLI
command to a file on a compact flash disk with little or no free
space may cause the active session to become unresponsive.
(D.121555, D.178241)
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 lossofframe and lossofsignal defects at the far
end of an E1 link. The farend 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)
Alcatel-Lucent
3HE086790007TQZZA_01
75

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, you must deconfigure and reconfigure the log-id.
(P.598734)
When configuring an IPv6 address in the BOF for the management
port, you must also configure an IPv4 address. (P.593821)
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)
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 when cabled to a hub
operating in halfduplex mode. If the problem occurs, a CSM reboot
is required to recover. (P.600143)
TACACS+
Configuring the system to use the TACACS+ single-connection

option does not force the system to set the single-connection flag
in the TACACS+ packets that are sent to the TACACS+ server.
(D.79797, D.178239)
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).
Alcatel-Lucent
3HE086790007TQZZA_01
76

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.
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 users 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.
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)
T-LDP
The current implementation of the T-LDP local-lsr-id only supports

one targeted LDP peer per local-lsr-id interface. Configuring multiple
targeted LDP peers with the same local-lsr-id interface will have
adverse effects. Some adverse affects are loss of CSM redundancy or
T-LDP session bouncing. To recover from loss of CSM redundancy,
remove the invalid configuration and reset the standby CSM.
(P.671110, D.171911)
VPLS
For VPLS multicast traffic, each packet consumes two buffers at SAP
and network egress. The CBS of SAP and network egress queues must
be configured accordingly. (P.603822)
Servicerelated SNMP requests to the 7705 SAR-8 can time out
(standard 10second timeout) after a 4port OC3/STM1 Clear Channel
Adapter card that has a large number of VPLS ATM SAPs configured
has been reset. (P.598660, D.171155)
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)
An OAM VPRN ping or VPRN trace will fail if the packet size exceeds
the network port MTU. (P.577221)
Alcatel-Lucent
3HE086790007TQZZA_01
77

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)
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)
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)
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
additonal VPRN shutdown/no shutdown is required. (D.179766)
Alcatel-Lucent
3HE086790007TQZZA_01
78
RESOLVED ISSUES
RESOLVED IN
R6.1.R7
The following are specific technical issues that have been resolved in this
release since Release 6.1.R6.
Notes:
Bracketed ( ) references are internal tracking numbers.
Issues marked as MI might have had a minor impact but did not disturb network
traffic.
Issues marked as MA might have had a major impact on the network and might have
disturbed traffic.
Issues marked as CR were critical and might have had a significant amount of impact
on the network.
BFD
An NP BFD session may not come up if continuous physical layer issues

cause it to bounce several thousand times. To recover from this issue,
perform two successive CSM switchovers if redundancy is configured;
otherwise, reset the CSM. To avoid this issue, ensure that there are no
repeated physical layer errors or avoid using NP BFD. (D.202173-MI)
FRR
When an Apipe, Hpipe or a Cisco HDLC Ipipe service is going over a

network that has FRR enabled and that uses SDP with RSVP tunnels/LSPs
and, specifically, static VC labels, any configuration changes to the
control word settings, without shutting down the service or LSP, will
result in traffic loss after a fast reroute switch.
As a workaround, any control word setting changes must be done while
the service or LSP is shut down. Once in the failed state, a
shutdown/no shutdown of the service will restore traffic.
(D.200792-MA, D.200340-MA)
If BFD is enabled, a local failure on a link that is providing FRR
protection for an LSP may cause the traffic over the primary path to
stop. This issue might occur only if all of the following conditions are
met:
the primary LSP path goes over one link and the FRR
protection path goes over another link
BFD under RSVP is enabled on the FRR protecting interface

and an alternate path (for example, a default route) to the
BFD peer is available on the interface that is also used by the
primary LSP path
a local failure occurs on the FRR protecting interface that is

not triggered by BFD (for example, a physical link failure, or
a port or interface shutdown)
(D.201520-MA)
LDP
Alcatel-Lucent
When the security feature vprn-network-exceptions is enabled, link

LDP sessions may unexpectedly bounce. (D.198047-MA)
3HE086790007TQZZA_01
79

MLPPP
An MLPPP bundle may stop passing traffic at ingress if it is connected to

a far-end node through a microwave path and the microwave path is
degraded or has been degraded in the past. A shutdown/no
shutdown of the MLPPP bundle will recover the bundle. (D.198161-MA)
SAR-Wx
Upgrading a SAR-Wx to R6.1.R7 will result in changed port MAC

addresses, which may affect MAC filters that have already been applied.
After the upgrade, update any applicable src-mac and/or dst-mac
configurations under the applied MAC filters. (D.202077-MI)
SNMP
A CSM reboot or dual-CSM reboot (if redundancy is configured) may

occur if a port ID is specified when creating a new router interface using
SNMP (for example, the 5620 SAM) on the 10-port 1GigE/1-port 10GigE
X-Adapter card, the 2-port 10GigE (Ethernet) XFP Adapter card, or the
2-port 10GigE (Ethernet) module (on the 7705 SAR-M). (D.203029-MI)
SSM
TWAMP
RESOLVED IN
R6.1.R6
SSM cannot be supported with unframed E1. This illegal configuration is

now blocked. Before attempting a software upgrade, this configuration
must be turned off; otherwise, the upgrade will fail. (D.197134-MI)
Approximately one time in ten million (10^7), TWAMP delay
measurements will show a value that is off by approximately 1 second.

This is caused by an improper T3 timestamp. (D.200808-MI)
Notes:
traffic.
disturbed traffic.
on the network.
BFD
DHCP
Alcatel-Lucent
A 10-port 1GigE/1-port 10GigE X-Adapter card may reset when checking

the BFD session operational status either during initial establishment or
after a shutdown/no shutdown port operation when there are 127
central BFD sessions configured with type np on a 10-port 1GigE/1port 10GigE X-Adapter card port pair. (D.195084-MA)
A DHCP Server on a 7705 SAR may be configured with an option to keep
the leases persistent. In this configuration, all leases issued by the DHCP
Server are saved in a file and recovered when the router reboots.
3HE086790007TQZZA_01
80

However, when chassis types SAR-A, SAR-H, SAR-Hc, SAR-M, SAR-W or
SAR-Wx lose power, the DHCP leases recovered after the restoration of
power will have an abnormally long lease time. The lease time restores
to an expected value upon receiving a DHCP Renew/Rebind request
from the DHCP Client. However, if the DHCP Client is no longer in the
network, the lease may not be released. In that situation, you can
manually clear the leases using the CLI command clear router dhcp.
Note that all new DHCP requests are supported without any disruption
even when the 7705 SAR has leases with incorrect expiry times.
(D.193370-MI)
GPS
IPSEC
When a SAR-Wx or SAR-H that has a GPS feed and that is configured for
1588 Boundary Clock (Grand Master-capable) slaving to a Grand Master
upstream, regains its lost GPS signal, it will not transmit the correct
clock-class, variance and accuracy to its downstream slave for 3 or 4
minutes. This can cause the downstream slave to go out of
synchronization. (D.191895-MA)
If two or more IPSec tunnels are configured with the same local gateway
address, the alarm smgrRecordTunnelForPip: Can't insert tunnel
localGwIpAddr will be raised in log 99. Traffic might be affected if NAT
is enabled.
The workaround is to use a different local gateway address for each
IPSec tunnel. (D.192864-MA)
If hybrid port mode is used in conjunction with an IES interface for the
IPSec tunnels egress interface, a BFD over IPSec session will not come
up. (D.193507-MI)
MICROWAVE
When an admin save is performed to an FTP location, the operation

may appear to be successful but the MW radio database files may not
get backed up.
As a workaround, create the directory \local\db on a compact flash
for both the active and standby CSMs. (D.194310-MI)
MLPPP
MLPPP bundle statistics will appear to decrement by a large value. After

this occurs, the statistics will increment normally. The issue is not
present on the individual member link statistics. (D.193072-MI)
MULTI-DROP DATA
BRIDGE (MDDB)
It may take longer to squelch an MDDB branch than the configured

timeout. As well, the time to squelch beyond the timeout is related to
the squelch-timeout itself. The issue is more visible for speeds less than
9600 b/s and for longer timeouts. (D.194590-MA)
While operating at speeds less than 2400 b/s, the squelch functionality
of MDDB does not work for certain test patterns. For example, at 1200
b/s and 600 b/s, and for test patterns 511 and 2047, a branch is never
squelched, but it is squelched for a 1:1 test pattern. (D.188337-MI)
Alcatel-Lucent
3HE086790007TQZZA_01
81

NTP
On a 7705 SAR-M, the system date/time may change after a system

reboot. The problem will not occur if SNTP, GPS or PTP are used as the
source of system time. If NTP is used as the source of system time, then
after a reboot the time will be changed to a distant future year (for
example, year 2038), and the date/time will not correct itself even if
the 7705 SAR-M is communicating with an NTP server. If there is no
external source of system time and the user manually configures the
system time using the CLI, then after a system reboot the date/time
will revert to either 1970 or a future year (for example, 2106),
depending on the time zone configured.
This issue only exists in the 6.1.R4 and 6.1.R5 software loads. If this
issue is encountered, the system time can be recovered by manually
changing it via the CLI. (D.199270-MA)
OAM
The EFM tunneling feature is only supported on access ports; however,

the configuration was not being blocked on hybrid ports.
(D.192115-MI)
An MDA reset may occur on a SAR-A, SAR-M, or SAR-W platform if both
of the following conditions are met:
o
a CFM Up MEP is configured on a SAP in an Epipe service that uses

a 4-priority scheduler at SAP ingress with a PIR or CIR configured
as any value except 0 or maximum
a CFM LBM packet larger than 448 bytes is received on a port using
a 16-priority scheduler, destined for that MEP
As a workaround to this issue, use a 16-priority scheduler on SAP ingress

when a CFM Up MEP is used. (D.192661)
PPP
If a protocol reject is received at the LCP level, LCP may incorrectly

stay in the stopped state depending on subsequent protocol messages. A
shutdown/no shutdown of the MLPPP bundle will recover the
bundle. (D.194976-MA, D.187910-MI)
R-VPLS
When an R-VPLS interface is using an RFC 3107 BGP tunnel and a control
word is enabled at that spoke SDP, a ping across the BGP tunnel does
not work. (D.196596-MI)
SYSTEM
TRAFFIC
MANAGEMENT
Alcatel-Lucent
During admin tech-support file collection, an unusual error

"wpSarmGetBootLoadInfo Failed to read Main board EEPROM" might be
raised in log 99. This error can be ignored. The problem can occur on
SAR-A, SAR-H, SAR-Hc , SAR-M, SAR-W, and SAR-Wx platforms.
(D.181420-MI)
In R6.0 and R6.1 on the SAR-A, SAR-M and SAR-W, and in R6.1 on the
additional platforms SAR-H, SAR-Hc and SAR-Wx, the in-profile/out-ofprofile marking on egress for VPLS BMU (broadcast, multicast and
unicast) traffic may be incorrect in the following scenario. If the ingress
queue performing the in-profile/out-of-profile marking has the CIR set
to anything other than 0 or max, then all packets on the egress side will
be seen as in-profile traffic, when only some of the packets should be
seen as in-profile traffic and some should be seen as out-of-profile
traffic.
3HE086790007TQZZA_01
82

In this scenario, the egress in-profile/out-of-profile statistics counts will
be incorrect, the egress queue discard mechanisms (WRED and tail drop)
will drop based on an incorrect in-profile/out-of-profile marking, and
the egress markings (DSCP/EXP/dot1p) will be incorrect since the egress
marking relies on the in-profile/out-of-profile marking for the packet.
(D.191475-MA)
VPLS
RESOLVED IN
R6.1.R5
The VPLS MAC move function does not work properly if the movefrequency value is configured as 2 or above and there is only one SAP
or spoke SDP configured under the VPLS service. (D.193074-MI)
Notes:
traffic.
disturbed traffic.
on the network.
4PORT OC3/STM1
CHANNELIZED
ADAPTER CARD
In previous releases, configuring and inserting an adapter card in a slot

after a 4-port OC3/STM1 Channelized Adapter card has already been up
and running in that slot may result in a CSM crash.
As a workaround, reboot the CSM after the MDA slot with the 4-port
OC3/STM1 Channelized Adapter card (4-choc3) has been deconfigured.
(D.189620-MA)
4PORT OC3/STM1
CLEAR CHANNEL
ADAPTER CARD
When the OC3 SONET port is brought down due to an SF alarm (B2
errors) on the 4-port OC3/STM1 Clear Channel Adapter card, the
underlying STS3 stays up and the router interface associated with the
port also stays up, receiving traffic. An MPLS reroute may take place if a
high number of errors occur. The new behavior matches that of the
2-port OC3/STM1 Channelized Adapter card; that is, the port declaring
SF BER will trigger AIS-P on its STS3, bringing it down, and will send
L-RDI to the far end, in addition to sending L-REI. (D.187948-MI)
If there is an internal loopback on one OC3 port of the 4-port OC3/STM1
Channelized Adapter card and a line loopback on another OC3 port on
the same card, shutting down the OC3 port with the line loopback on it
can cause corruption on the internal loopback.
A workaround is to deconfigure and reconfigure the internal loopback.
(D.187836-MI)
Alcatel-Lucent
3HE086790007TQZZA_01
83

FPIPES AND HPIPES
FILTER POLICIES
IS-IS
MLPPP
OAM
PIM
RESOLVED IN
R6.1.R4
When an Fpipe or Hpipe service is set up with a pseudowire switching

node in the middle, the traffic is discarded by the switching node.
(D.190998-MA)
When a community expression is configured to match on a fixed number
of digits through the { } operator, incorrect matching occurs when the
input community contains digit 0. This digit 0 (as well as the
following digits) are ignored for evaluation, allowing a community
exceeding this fixed number of digits to match. (D.188926-MI)
An MPLS LSP may fail to come back into service on an MLPPP interface
with IS-IS routing after a link failure and recovery. An IS-IS interface
shutdown/no shutdown on an MLPPP interface will clear the
failure. (D.188604-MA)
Under certain conditions, adding or removing a link to an MLPPP bundle
could add a delay to traffic. The fix will limit the delay to 50 ms.
(D.179994, D.182272-MI)
The port on which a persistent loopback is provisioned may stay
operationally down after a node reboot or after a clear mda
command. The port will come up only after executing the
shutdown/no shutdown commands. (D.188537-MA)
There may be traffic loss on multicast groups that are rebalanced across
ECMP interfaces. (D.185953, D.149798-MI)
Notes:
traffic.
disturbed traffic.
on the network.
10-PORT 1GIGE/
1-PORT 10GIGE XADAPTER CARD
Alcatel-Lucent
When using a copper/dual-rate SFP with 10-port 1GigE/1-port 10GigE

X-Adapter card ports 9 and 10, renegotiating from a speed of 1 Gb/s to
10/100 Mb/s would result in traffic loss. (D.187885-MI)
3HE086790007TQZZA_01
84

BOUNDARY CLOCK
A boundary clock with a ptp-port in the master state may not transmit
1588 sync packets. This problem occurs as a result of the following
sequence of events.
1. A ptp-port (ptp-port 1) was in the slave state and another Grand
Master (deemed better) is found in the network.
2. The clock switches to the alternate Grand Master by slaving on
another ptp-port (ptp-port 2).
3. ptp-port 1 transitions to the passive state based on the best
master clock algorithm.
4. The Grand Master accessible via ptp-port 1 degrades such that
the ptp-port transitions to the master state.
This final state transition results in PTP sync packets not being sent by
the master port. This problem is cleared if a shutdown then no
shutdown is performed on the PTP clock. (D.185331-MA)
IP ECMP
IP INTERFACES
MLPPP
If IP ECMP is enabled on the node, the system limit of IP next-hop

groups is 16384 (a next-hop group is created when IP ECMP is enabled
and multiple next hops for the same route are available). If next-hop
groups are continuously created and deleted (either by a configuration
change or a network topology change), traffic will not flow on the
16385th next-hop group even though there may not be 16K existing
next-hop groups at that time. (D.184655-MI)
The limit of 64 network IP interfaces for Ethernet ports on the SAR-H,
SAR-Hc, SAR-W, SAR-Wx, SAR-M, SAR-F, and SAR-A was unenforced.
Exceeding this port limit can cause the Ethernet ports to continuously
reset until the extra interfaces are removed. (D.186132-MI)
For an MLPPP bundle running on the SAR-M, SAR-A, or SAR-H, if the farend equipment does not support MLPPP fragmentation, the MLPPP
bundle will discard all incoming packets with payloads greater than
666 bytes. The defect only impacts Release 6.1. (D.186508-CR)
NAT
Security policy entries did not allow a zero (0) value for an src-port or
dst-port. IETF RFCs do not explicitly restrict this value; therefore, it is
now allowed as a valid value to be entered in a security policy on
CLI/SNMP (D.184202-MI)
PER-VLAN
NETWORK EGRESS
SHAPERS
If network egress per-VLAN shapers are enabled on a microwave 1+1

link, then the microwave adapter cards containing these links, as well
as the inactive CSM, may reset and fail to boot after an adapter card
reset. (D.184529-MA)
SNMP
Alcatel-Lucent
The vRtrPolicyTable can become inaccessible after its mw-management

routing instance (vrtrID 4090) is accessed by snmpgetnext.
(D.184881-MI)
3HE086790007TQZZA_01
85

SYSTEM
A module on a SAR-M or SAR-H may go into the failed state after it is

reset. This may happen if there is a large volume of traffic being sent to
the module while it is attempting to boot up, causing the buffer pool to
become exhausted. (D.183177-MA)
Ports 1 to 4 on an 8-port Gigabit Ethernet SFP Adapter card may stay
operationally down even if the physical port is fine. This issue is rare,
and will only rarely occur when a TS file is collected on a node with
redundant control when CSM-B is active. If the issue is encountered, the
recovery mechanism is to perform a CSM switch making CSM-A active,
followed by clearing all Ethernet ports on the 8-port Gigabit Ethernet
SFP Adapter card. (D-183082-MI)
RESOLVED IN
R6.1.R3
Notes:
traffic.
disturbed traffic.
on the network.
APS
A shutdown of an unframed E1/DS1 port within APS will not result in the
related SAP (for example, aps-1.1.1.1.1) changing state to operationally
down. (D.182727-MI)
DHCP
When DHCP Server and DHCP Relay are configured on the same 7705
SAR, and DHCP Relay is configured over an R-VPLS interface or a Base
Router interface, the Renew requests from the Client are discarded.
The DHCP lease is extended with a subsequent Rebind request from the
Client.
As possible workarounds, if DHCP Relay is configured over an IES
interface, the Renew requests are processed correctly. If both DHCP
Server and DHCP Relay are configured within a VPRN service, the Renew
requests are processed correctly as well. (D.182945-MA)
FABRIC STATISTICS
On the SAR-18 chassis, traffic with a packet size 8983 bytes will not be
counted in the total forwarded packets for both the fabric port and
fabric global statistics. (D.181614-MI)
IP ECMP
Alcatel-Lucent
If IP ECMP is enabled on the node, the system limit of IP next-hop

groups is 16 000 (a next-hop group is created when IP ECMP is enabled
and multiple next hops for the same route are available). However,
when the number of next-hop groups exceeds 4000, traffic will only
flow on the first 4000 next-hop groups. (D.183747-MI)
3HE086790007TQZZA_01
86

IPV6 FILTERS
JUMBO FRAMES
IPv6 egress filters are only supported on Ethernet adapter cards and the
4-port OC3/STM1 Clear Channel Adapter card. The configuration is
allowed on all adapter card types. (D.181406-MI)
Rapid pings originating on a 7705 SAR should be limited to a maximum
size of 2106 bytes. (D.180635-MI)
Jumbo frames ingressing on a SAR-M or SAR-H Ethernet port and
egressing from a T1/E1 port may be erroneously discarded, if the
ingressing packets do_not_fragment bit is not set and the packet size
is larger than the maximum configurable MTU on the T1/E1 port. In such
a case, the packet should be fragmented to match the port MTU of the
ASAP port. Instead, it is being dropped. (D.181759-MI)
NAT
When port ID collisions occur, NAT session packets are dropped. As a

workaround, manually configure the port range in the NAT pool
configuration to solve the port collision issue. (D.181892-MA)
On very rare occasions after a system restart, all NAT packets flowing
through an adapter card may be discarded due to checksum errors. If
this issue occurs, an adapter card reset is required to recover.
(D.181886-MA)
DNS NAT sessions time out almost immediately independent of the UDP
DNS timeout configuration and may result in DNS responses being
dropped. (D.185157-MA)
OAM
CFM two-way-delay and one-way-delay tests do not function correctly

for a down MEP on a SAP with tag format qtag.qtag when the SAP
resides on a 1GigE X-Adapter card port configured with QinQ
encapsulation. (D.181881-MI)
The ETH-CFM hold-mep-up-on-failure feature is not configured
correctly on a QinQ SAP. The configuration is accepted using SNMP or
the CLI, but the configuration does not appear using the CLI info
command or by reading the SNMP object AluSapEthCfmHoldMepU. If a
user enables hold-mep-up-on-failure, it will function correctly, but
after reboot the configuration will be lost. (D.183438-MI)
ETH-CFM two-way-slm-test results are incorrect for interface MEPs;
this includes inbound, outbound and round-trip values. The problem is
due to a corrupt timestamp in the SLR. (D.181871-MI)
On the 8-port Gigabit Ethernet SFP Adapter card, version 3, and the
SAR-Wx, the incorrect maximum MTU value is allowed (9198 instead of
9702) for all OAM tool commands. (D.181322-MA)
SAR-M
Alcatel-Lucent
Only 512 SAPs can be created on a SAR-M with DSL or GPON modules.
The limit on these systems with a module is 640: 512 SAPs on the
Ethernet block and 128 SAPs on the module (DSL or GPON) block.
(D.181410-MI)
3HE086790007TQZZA_01
87

SYSTEM
RESOLVED IN
R6.1.R2
Creating and deleting long filenames (LFN) in a directory can result in

corruption of the directory. Creating new LFN files will fail while the
directory is in this state. A workaround is to create new temporary 8.3
files until LFN files can be created. The 8.3 filename must be all
uppercase and contain only a single dot; for example, ABCD.CFG. The
temporary 8.3 files can be deleted after the LFN files start working
again. (D.177985-MI)
Notes:
traffic.
disturbed traffic.
on the network.
7705 SAR-H
On a 7705 SAR-H, if there is a SAP on an Ethernet port and a network

MLPPP bundle on the T1/E1 ports on the 4-port T1/E1 and RS-232
Combination module, the MLPPP bundle may go operationally down if
you make QoS changes to the QoS policy assigned to the Ethernet SAP.
To recover, perform a shutdown/no shutdown on the network
MLPPP bundle to bring it operationally back up. (D.175482-MA)
7705 SAR-M &

APIPE
If the control-word configuration of an Apipe service on a 7705 SAR-M is

changed while the Apipe is in service and passing traffic, all the ports
may reset, causing data loss. As a workaround, perform a shutdown
on the Apipe service, change the control-word configuration, and then
perform a no shutdown on the Apipe service. (D.176984-MA)
ASAP ADAPTER
CARD
On an ASAP adapter card within a DS1, if a higher-numbered channel

group (for example, cg24) is created and configured such that all
timeslots automatically get assigned (access mode with encap-type atm,
or network mode with encap-type ppp-auto) and then a lowernumbered channel group (for example, cg1) is created, an admin save
and later reboot will result in the config file not loading correctly.
(D.177472-MA)
On a ASAP adapter card within a DS1, if a higher-numbered channel
group (for example, cg24) is created and configured for network mode
(encap-type ppp-auto with fractional DS1/E1) and then a lowernumbered channel group (for example, cg1) is created with fractional
DS1/E1, an admin save and later reboot will result in the config file
not loading correctly. (D.178160-MA)
Alcatel-Lucent
3HE086790007TQZZA_01
88

BFD
If a unidirectional failure occurs in the Layer 2 transportation network

that is connected with a 7705 SAR, BFD may not inform RSVP quickly
enough, which could cause a 2.5 to 8 second outage during Fast
Reroute. (D.179496-MA)
A BFD session could go down if the IP interface port configuration is
changed from one adapter card to another adapter card by a
modification operation from the 5620 SAM (which is not possible via the
CLI). (D.178492-MA)
BGP
A High-Availability switchover will no longer result in VPN-IPv4 routes

becoming unresolved in configurations with a large number of spoke SDP
bindings. (D.178004-MA, D.165386-MA)
DHCP
An R-VPLS interface should not be associated with a local DHCP Server.

If it is inadvertently associated with a local DHCP server, the command
will be denied. However, the system CPU usage will reach 100% and not
recover. (D.178826-MA)
FABRIC STATISTICS
Fabric statistics as per the show mda <mda-num> statistics destmda/source-mda menu may freeze at the last displayed value when a
node has been running for 497 days or longer. A clear mda statistics
command will also not work when this issue occurs. This issue is a
statistics issue only and has no traffic impact. In dual CSM installations,
the statistics can be refreshed by executing the admin redundancy
force-switchover" command. In cases where there is only one CSM, only
a node reboot will fix the issue. (D.178012-MI)
HYBRID PORTS
CPE pings to a VPLS service on a hybrid port will fail. (172063-MI)
LAG
In rare cases, the LAG port states displayed in the show port <portId>
detail menu are out of sync with the actual states. (D.170599-MI)
NAT
When a forward policy/zone is configured by itself on a 7705 SAR, the

ICMP query IDs in the reverse direction are incorrectly changed to 0,
causing ping to fail. (D.178098-MA)
In the show screen for NAT session dump, the PLCY value that is
generated in the NAT session show screen output may not correspond to
the value of the RULE entry in the policy. Therefore, it may not be
possible to correlate the NAT session with a Rule Entry. (D.178331-MI)
OAM
The Y.1731 Down MEP on networks ports feature does not function when
the network port is a port on the 2-port 10GigE (Ethernet) module of
the 7705 SAR-M. All CFM functionality is affected. (D.178260-MA)
If an Ethernet CFM SAP Up MEP is configured on an Epipe service with
SAP format <port-id>:qtag1 or <port-id>:qtag1.qtag2, where qtag1 is 0,
the one-way-delay test and two-way-delay test results will be invalid.
All Ethernet adapter cards are affected by this issue. (D.177714-MA)
If the active CSMv2 is removed from a SAR-8v2 chassis, then it is
possible that EFM-OAM links on adapter cards in slots 2, 4 or 6 may get
stuck in a link-fault state. (D.180820-MA)
Alcatel-Lucent
3HE086790007TQZZA_01
89

During admin tech-support file collection, Ethernet ports configured
with EFM-OAM with a timeout of 500 ms or less (for example, transmitinterval 1 multiplier 5 (or less)) may bounce, due to the Ethernet EFMOAM packets processing being delayed and expiring. Services associated
with the port configured with EFM-OAM could be affected.
The workaround is to increase the EFM-OAM timeout value to be more
than 500 ms. (D.180313-MA)
PW REDUNDANCY
When a Cpipe is configured as standby-signaling-slave under an explicit

endpoint for a pseudowire redundancy application, a SAP port down will
not trigger a pseudowire redundancy switchover if the service has a
partial second explicit endpoint configured. (D.178643-MA)
RFC 3107
Label-BGP
Traffic for Inter-AS Layer 2 services using RFC 3107 may be impacted
when a new labeled BGP route is being installed in the FIB with a new
RFC 3107 label. If the transport MPLS label associated with this RFC
3107 route also changes, there is no impact.
A workaround is to bounce the MPLS interfaces on routers impacted by
network changes. (D.178708-MI)
R-VPLS
When there is more than one route to the destination for an IP address
in an R-VPLS service, the ARP does not get resolved. (D.180383-MA)
When an R-VPLS service is configured with QinQ default SAP (*.*), ARP
requests are incorrectly discarded, resulting in unresolved ARP.
(D.180596-MA)
SYSTEM
The 7705 SAR does not support accounting on network Ethernet port
statistics. Via SNMP, if tmnxPortEtherCollectStats is set to true on an
Ethernet network port, then a message similar to the following will be
observed if an attempt is made to change the port from network to
access:
MINOR: PMGR #1011 Port network stats accounting-policy-id is
configured or stats collection is enabled - 1/1/1.
If this issue is observed, it will not be possible to configure the port
from network to access without first setting tmnxPortEtherCollectStats
to false via SNMP. (D.177793-MI)
On rare occasions during admin tech-support file collection, the fiber
SFP port status could be incorrectly read as down for a brief period,
which may cause brief port status bouncing. The service associated with
the port status could be affected. The problem only occurs with fiber
SFP ports on the SAR-M and SAR-H platforms. (D.178264-MA)
Alcatel-Lucent
VPLS
When the node is configured with VPLS with spoke SDP, the CLI
command tools dump service vpls-fdb-stats causes adapter cards that
do not support VPLS to reboot. (D.181340-MA)
X.21
X.21 SAPs are not supported as part of VPRN services; however, they are
not blocked from being configured in the CLI. If such an unsupported
configuration is made, the Serial Data Interface card may reset
constantly. The fix will now block this invalid configuration.
(D.178787-MI)
3HE086790007TQZZA_01
90
RESOLVED IN
R6.1.R1
release since Release 6.1.B1-8.
Notes:
traffic.
disturbed traffic.
on the network.
1588
7705 SAR-A
If a configuration file is executed in the CLI and the source-interface is

programmed for a PTP clock within this configuration file, the sourceinterface will be lost on a subsequent activity switch. (D.177755-MA)
If a non-default description is added to one or more ports of a 7705
SAR-A, an admin save is performed, and the node is then rebooted,
the descriptions on ports 1/1/1, 1/1/2 and 1/1/4 will not be saved.
Instead, they will revert back to their default port descriptions.
(D.177450-MI)
BFD
If an interface has BFD enabled under RSVP, the node will not block a
user from removing the network interface's BFD configurations as it
should. If the network interface's BFD configurations are removed and
the node is rebooted, the complete configuration will not be executed,
as it will fail when it tries to execute the RSVP configuration.
(D.176124-MI)
BGP
VPN-IPv4 routes that are flagged as invalid may not get reflected to all
route-reflector clients if the routes have flapped. A route reflector will
mark routes as invalid if there is a local VPRN configured with an import
target matching the routes received, but there is no valid tunnel to the
next hop of the route. A workaround is to ensure that all VPN-IPv4
routes are marked as valid by configuring a tunnel in the VPRN to all
next hops. (D.161331, D.175634-MA)
The 7705 SAR CSM may reset while performing robustness operations
(for example, ospf shutdown/no shutdown) in a scaled BGP route
reflector configuration. (D.169843-MA)
Next-hop-self is not supported when enabled in a route policy action in
conjunction with RFC 3107 labeled routes on the route reflector; it will
be set, but the label will not change and forwarding will not work.
(D.82485)
ECMP
Alcatel-Lucent
VPRN or IES services with interfaces that share a common spoke SDP
that has multiple equal-cost tunnels will all incorrectly choose the same
tunnel to forward traffic. In previous releases, each VPRN/IES service
would potentially choose a different tunnel for the same spoke SDP
interface. (D.172971-MA)
3HE086790007TQZZA_01
91

EPIPE SERVICES
FILTERS
IES/IP/VPRN
ACCESS
INTERFACES
In 6.1.R1, the tagged LACP and 802.1X frames will be forwarded through
the Epipe as customer traffic, while in previous releases these frames
would be dropped. (D.174390-MI)
If an IPv4 CPM filter is configured with multiple entries using all the
different entry match criteria, exceeding the supported limit, a trace
error (WP_INVALID_IW_CLASS_FIELDS_COMBINATION in
WPI_IwClassFilterSetFields()) is seen and the filter is rendered useless
until the extra configuration that exceeds the supported limit is
removed. (D.175242-MI)
Prior to 6.1.R1, IES/IP/VPRN access interfaces with dot1q encapsulation
always sent ARP requests/responses with Ethertype=0x8100, regardless
of the configured Ethertype of the port between two 7705 SAR nodes.
(D.174607-MA)
NAT
A TCP session cannot be fully established if egress and ingress traffic

ride on different interfaces. (D.174719-MA)
OAM
Up MEPs on a SAP-to-SAP Epipe cannot exchange CCMs when the SAP

format is <port-id>:qtag1.qtag2 and the ports have a non-default value
for qinq-etype. The default value for port qinq-etype should be used.
(D.174917-MI)
With a SAP ingress QoS policy configured, Y.1731 two-way-delay test
response (DMR), single-ended-loss test response (LMR), and loopback
(with size zero) response (LBR) PDUs received on the SAP do not receive
the correct treatment per the user priority bits. The PDUs are instead
processed through the default queue as best effort. (D.173287-MI)
CCM exchange fails for Up MEPs when the SAP has a QinQ encapsulated
port with different non-default port Ethernet types for inner and outer
tags. (D.174524-MA)
PPP
QOS POLICIES
STP
Alcatel-Lucent
Packets may be discarded on the ingress of PPP links on the following

platforms: 7705 SAR-M or 7705 SAR-H. The issue is related to packet
size; only packets of certain sizes are at risk of being discarded. If the
issue is observed during lab trials, adjust the packet sizes being sent in
order to avoid the issue. (D.175417-MA)
When a QoS SAP ingress/egress policy is applied to more than 48 SAPs
under APS on a 2-port OC3/STM1 Channelized Adapter card, the active
CSM may crash if certain configurations are modified, added, or deleted
in the QoS policy (for example, a new queue creation with FC mapping
to it, or deleting an existing queue). Without APS, or fewer than 48
SAPs, there is no problem. The workaround is to create a new QoS
policy with all necessary changes, and then apply it to all related SAPs.
(D.176912-MA)
Spanning Tree Protocol (STP) does not work on VPLS and R-VPLS SAPs
that are on ports configured as hybrid. A workaround is to configure
the port as access rather than hybrid. (D.174268-MA)
3HE086790007TQZZA_01
92

SYSTEM
CSMv2 cards may not boot successfully in a very old SAR8 v1 chassis.
(D.170269-MI)
TACACS+
Login and logout events are not being recorded in TACACS+ accounting
records. (D.98648, D.178240-MI)
VPLS
A VPLS multicast service may stop passing traffic after an FRR switch.
This issue will occur if there was a routing change to the inactive path
(while it was still inactive) such that the new route uses a different
adapter card than the previous route. In addition, for the problem to
occur, the adapter card with the new route must not have any
configured VPLS SAPs. (D.174483-MA)
VPRN
After a double CSM switchover, VPRN over GRE services may stop
sending traffic for a period of time depending on how fast the standby
CSM reconciles. (D.175139-MA)
XDSL
While interoperating with an ISAM that has support for parallel

initialization of lines in the bonding group (for example, R4502.304),
and is configured for 8-p ADSL2+ bonding, the 7705 SAR-M xDSL lines do
not form the bonding group. As a result of this, the xDSL port will not be
operational. (D.173163-MA)
RESOLVED IN
R6.1.B1-8
Notes:
traffic.
disturbed traffic.
on the network.
1588
Alcatel-Lucent
The correction field (CF) in 1588 event packets may not get updated
when the 7705 SAR-M, 7705 SAR-A, or 7705 SAR-W is acting as a
Transparent Clock (TC), if the packets are going through an IES
interface. This issue occurs when the IES interface is created after
enabling TC on the node.
As a workaround, perform a shutdown/no shutdown on the
transparent clock. (D.170851-MA)
3HE086790007TQZZA_01
93

BFD
When BFD is enabled under a broadcast interface in a large broadcast

domain, it will establish a scaled number of BFD sessions. Under rare
conditions, when the BFD sessions go down (for example, due to router
interface IP address changes), it could cause internal counter issues
that will stop the BFD configuration from being removed from the
router interface. BFD functionality will not be affected. (D.170702-MI)
LAG
After issuing a no shutdown command on a LAG group, it is possible

that the output of the show lag x detail command will erroneously
show the operational state of one of the LAG members as down and the
active/standby state as active, while the other LAG member will appear
to be operationally up, but will have an active/standby state of
standby. Traffic will pass on the LAG group when it is in this state.
(P.625461)
ROUTING
If the IP address mask is changed from /31 to some other value at the
remote end, a ping of the new address/mask fails due to a stale entry
with the older mask value in the route cache. When the cache is full,
the stale route will be deleted. Once the stale route is deleted from the
cache, the new address/mask can be pinged. (D.170591-MA)
RSVP
RSVP tunnels with FRR enabled may not come up when interoperating
with a specific third-party vendor. This has now been resolved.
(D.168738-MA)
SHDSL
SHDSL uplinks on the DCM may under rare circumstances train at rates
less than the maximum rates allowed in G.991.2 Annex B and G.991.2
Annex G. (P.634477, D.170179-MA)
SSH
When an SSH session is initiated to an OmniSwitch from a 7705 SAR

node, there is no prompt displayed to enter a password as from a UNIX
box, only a space. Entering the password initiates the SSH session
normally. (D.169361-MI)
SYNCHRONIZATION
SYSTEM
Loopbacks on DS3/E3 and ENET ports that are a source of

synchronization are now blocked. (D.173185-MI)
During bootup, if there is a constant stream of characters received via
the console port, the boot process may not complete and may be
delayed indefinitely or until the ingress streaming subsides. If this
occurs, the CSM and adapter cards will not come up. The probability of
seeing this issue is higher with lower console port baud rates (for
example, 9600 baud). (D.168838-MI)
If a customer frequently performs routine LED tests by pressing the FAN
module ACO/LT button, or there is a hardware defect with the button,
eventually it could cause memory exhaustion and trigger MPLS to shut
down. If MPLS is shut down, perform a CSM switchover to recover.
(D.170175-MA)
Alcatel-Lucent
3HE086790007TQZZA_01
94
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.
Notes:
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.
1588
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)
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
the two Grand Masters are frequencysynchronized but not phase

synchronized (for example, two 7750 SR nodes or 7705 SAR nodes
acting as Grand Masters), and
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-MA)
2PORT 10GIGE
(ETHERNET) XFP
ADAPTER
CARD/MODULE
4PORT OC3/STM1
CHANNELIZED
ADAPTER CARD
On the 2-port 10GigE (Ethernet) XFP 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)
Setting trace-string zeros on an 4-port OC3/STM1 Channelized
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
Channelized Adapter card also does not display a received J1 string of
all 00s. (D.184328-MI)
With a fully configured 4-port OC3/STM1 Channelized Adapter card,
channelized down to DS1 or E1, when an slof is received by the
adapter card, several of the VT paths do not have an alarm status of
pais. (D.186698-MI)
Alcatel-Lucent
3HE086790007TQZZA_01
95

APS
Individual APS channel group members may be reported as down while

the APS port status is operationally up. This is strictly a display issue.
(D.89341, P.581261, D.170606-MI)
BGP
Turning on BGP AddPath functionality for BGP peers going over the
2-port 10GigE (Ethernet) Adapter card might cause a CSM to reset.
(D.172022-MA)
BOUNDARY CLOCK
DSL
IPv4 ACL FILTER
After configuring an unsupported peer ID 2-10 on a boundary clocks

ptp-port, the system may not accept any configuration commands.
(D.174103-MI)
As a workaround, log out from the node and log in again.
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. (178266-MA)
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. (D.188152-MA)
IPv6
If an IPv6 interface port or link is bouncing, a configuration

netMaskMismatch alarm may be incorrectly raised against OSPFv3 Hello
packets. (D.177010-MI)
IS-IS
The metric for a bundled interface in IS-IS with BFD and reference
bandwidth configured may be incorrect if the interface is assigned a
static metric and then that static metric is removed. Additionally, the
interface must be added to RSVP to see this issue. If this condition
occurs, the interface metric is calculated based on a rounded down
value of the interface bandwidth. Performing a shutdown/no
shutdown on the interface will allow the metric to be recalculated
correctly. (D.172474-MA)
IS-IS overload erroneously requires that a timeout value be explicitly
configured. This means that IS-IS overload cannot be configured to
remain in effect indefinitely by using the isis overload command. If
the desired behavior is that IS-IS remains in the overload state
indefinitely, a workaround is to configure isis no overload and isis
overload-on-boot and then reboot the node. (D.203662-MA)
NAT
Alcatel-Lucent
NAT sessions may not be created under circumstances in which users are
configuring zones and policies at the same time as a high traffic rate is
passing on the zones attached to the interfaces or SAPs in question
going through the NAT/firewall functionality.
A workaround is to use the clear security session all command.
(D.184302-MA)
3HE086790007TQZZA_01
96

OSPF
Loose-hop LSPs are not resignaled if a new equal-cost path becomes

available. (D.17494-MI)
PPP
Access PPP links with encap-type ipcp will be incorrectly in the LINK
UP state when one end is configured with the non-default CRC of 32.
This issue is only seen when using back-to-back ports on the 16-port
T1/E1 ASAP Adapter card v2 and the 32-port T1/E1 ASAP Adapter card.
(D.200801-MI)
PTP
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. Note that this
is not an expected configuration. (D.194853-MA)
QinQ
TWAMP
VPRN
Alcatel-Lucent
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)
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)
OAM VPRN ping from PE to CE will time out if the destination IP address
is not the local interface or network address of the subnet. VPRN trace
will time out when trying to get the last hop (PE interface SAP)
information. (D.189082-MI)
3HE086790007TQZZA_01
97
RELEASE LOAD HISTORY
Alcatel-Lucent
Released Load
Date
7705 SAR 6.1.B1-8
22 January 2014
7705 SAR 6.1.R1
28 February 2014
7705 SAR 6.1.R2
30 April 2014
7705 SAR 6.1.R3
3 July 2014
7705 SAR 6.1.R4
27 August 2014
7705 SAR 6.1.R5
15 October 2014
7705 SAR 6.1.R6
29 January 2015
7705 SAR 6.1.R7
25 March 2015
3HE086790007TQZZA_01
98
CHANGE HISTORY FOR RELEASE 6.1 RELEASE NOTES

Issue Number
Date of Issue
Reason for Issue
1.0
28 February 2014
Release Notes for load R1 of Release 6.1
1.0 Ed02
6 March 2014
Added CSMv1 to CSMv2 migration section

that was missing
2.0
30 April 2014
2.0 Ed02
29 May 2014
SAR-A support changed to R6.0.R2 from

R6.0.R1
Resolved Issue D.177793 description
updated
3.0
3 July 2014
4.0
27 August 2014
5.0
15 October 2014
6.0
29 January 2015
7.0
25 March 2015
APPROVALS
NOTE: This document has been electronically approved. Approval history is stored in the appropriate
DDM Number Log. When printed, this document is uncontrolled.
Document Part Number: 3HE086790007TQZZA_01
No portion of this document may be reproduced in any form or means without prior written permission from
Alcatel-Lucent.
Information in this document is proprietary and confidential to Alcatel-Lucent.
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other
trademarks are the property of their respective owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright 2014-2015 Alcatel-Lucent. All rights reserved.
END OF DOCUMENT
Alcatel-Lucent
3HE086790007TQZZA_01
99

7705 SAR OS 6.1.R7 Software Release Notice

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

7705 SAR OS 6.1.R7 Software Release Notice

Diunggah oleh

Hak Cipta:

Format Tersedia

Alcatel-Lucent 7705

SERVICE AGGREGATION ROUTER | RELEASE 6.1.R7

7705 SAR OS 6.1.R7 Software Release Notes

7705 SAR OS 6.1.R7 Software Release Notes

RELEASE 6.1.R7 DOCUMENTATION SET

7705 SAR 10-port 1GigE / 1-port 10GigE X-Adapter Card

7705 SAR 2-port 10GigE (Ethernet) Adapter Card/Module

7705 SAR 4-port T1/E1 & RS-232 Combination Module

7705 SAR 6-port E&M Adapter Card Installation Guide

7705 SAR 6-port FXS Card Installation Guide

7705 SAR 8-port FXO Card Installation Guide

7705 SAR 8-port Voice & Teleprotection Card Installation

7705 SAR Auxiliary Alarm Card Installation Guide

7705 SAR CWDM OADM Adapter Card/Module Installation

7705 SAR DS3/E3 Adapter Card Installation Guide

7705 SAR DSL Module Installation Guide

7705 SAR Ethernet/Gigabit Ethernet Adapter Card

7705 SAR GPON Module Installation Guide

7705 SAR GPS Receiver Module Installation Guide

7705 SAR Integrated Services Card Installation Guide

7705 SAR OC3/STM1 Adapter Card Installation Guide

7705 SAR Packet Microwave Adapter Card Installation Guide

7705 SAR Power Injector Card Installation Guide

7705 SAR Serial Data Interface Card Installation Guide

7705 SAR T1/E1 ASAP Adapter Card Installation Guide

7705 SAR-18 Chassis Installation Guide

7705 SAR-8 Chassis Installation Guide

7705 SAR-A Chassis Installation Guide

7705 SAR-F Chassis Installation Guide

7705 SAR-H Chassis Installation Guide

7705 SAR-Hc Chassis Installation Guide

7705 SAR-M Chassis Installation Guide

7705 SAR OS 6.1.R7 Software Release Notes

7705 SAR-O Chassis Installation Guide

7705 SAR-W Chassis Installation Guide

7705 SAR-Wx Chassis Installation Guide

7705 SAR OS Basic System Configuration Guide

7705 SAR OS Interface Configuration Guide

7705 SAR OS MPLS Guide

7705 SAR OS OAM and Diagnostics Guide

7705 SAR OS Quality of Service Guide

7705 SAR OS Router Configuration Guide

7705 SAR OS Routing Protocols Guide

7705 SAR OS Services Guide

7705 SAR OS System Management Guide

7705 SAR-A Power Supply Tray Installation Instructions

7705 SAR Zipped Collection

7705 SAR OS 6.1.R7 Software Release Notes

RELEASE 6.1.R7 SUPPORTED HARDWARE

7705 SAR-8 Shelf

Control and Switching Module (CSM)

7705 SAR-8 Fan Module

7705 SAR-F (-48V)

7705 SAR-F (+24V)

SAR-8 Fan Module (-48V) Extended Temperature

Control and Switching Module (+24V)

SAR-8 Fan Module (+24V) Extended Temperature

Control Switch Module for SAR-18

Fan Module for SAR-18

Alarm Module for SAR-18

SAR-M with 16 T1/E1, 7 GigE, -48/+24 VDC

SAR-M with 7 GigE, -48/+24 VDC

Fan Module for SAR-8 Shelf V2 Ext. Temp (-48VDC)

SAR-M Fanless with 16 T1/E1, 7GigE, -48/+24VDC