Release Description for 7670 RSP Release 9 - Nokia … Synchronous Digital Hierarchy ... 3.1.2 Specifications ... This document contains Confidential Information of Alcatel-Lucent

Alcatel-Lucent 31RD0050

Issued Version 4.1 Last Revised: 2014.09.16 Page 1 of 78

This document contains Confidential Information of Alcatel-Lucent.

Release Description for 7670 RSP

Release 9.x

NOTICE

This document contains confidential information which is proprietary to Alcatel-Lucent. No part of its contents may be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from Alcatel-Lucent.

©Copyright 2014. Alcatel-Lucent. All rights reserved.




ABSTRACT

This document specifies the functions and features supported by Release 9.x of the 7670 RSP.




[GLOSSARY]

AC Access Circuit (as per IETF PW concept)

ACL Access Control List

AESA ATM End System Address

AINI ATM Inter-network Interface

APS Automatic Protection Switching

ATM Asynchronous Transport Mode

BISUP Broadband ISDN User Part

CAC Connection Admission Control

CC2G Control Card 2nd Generation

CLI Command Line Interface

CLP Cell Loss Priority

CPSS Control Packet Switching System. A proprietary network protocol for communication between Alcatel equipment. CPSS is a packet-switched system similar to X.25 used to transfer configuration and status information between nodes

CO Central Office

DBR Domain Based Rerouting

DCC Direct Communications Channel

DCS SONET Digital Cross Connect

DCR Design Change Request

DFS Detailed Functional Specification. A document which provides a complete description of the “what” of a function or feature, i.e. a black-box description.

DLCI Data Link Connection Identifier

DTL Designated Transit List

ECC Error Correcting Code

EFCI Explicit Forward Congestion Indication

EPD Early Packet Discard

ER Explicit Rate

ESC Edge Services Card

GCAC Generic Connection Admission Control




HCM Hitless Connection Moves

HKII House Keeper Module Version 2

HSDPA High Speed Downlink Packet Access

IE Information Element

IGMP Internet Group Management Protocol

IMA Inverse Multiplexing over ATM

IOC IO Card

IR Intermediate reach

GigE Gigabit Ethernet

LCR Line Card Redundancy

LGN Logical Group Node

LR Long Reach

MAU Media Access Unit

MBS Maximum Burst Size

MIB Management Information Base

MPLS Multi-protocol Label Switching

MR16 MultiRate 16 Line Card

MSE Multi-Service Edge

MTSO Mobile Telephone Switching Office

NMTI Node Management Terminal Interface: The local user interface for a Alcatel network element.

NCCI Network Call Correlation Identifier

NCI Network Control Interface. A family of Alcatel proprietary protocols used to control network nodes.

NNI Network – Network Interface

NSM Network, Service & Element Management.

OAM Operation, Administration, and Maintenance

ODR Operator Directed Route

OIF Optical Internetworking Forum

P2MP Point to Multi-point

P2P Point to Point

PCR Peak Cell Rate

PIM-SM Protocol Independent Multicast – Sparse Mode




PIM-SSM Protocol Independent Multicast – Source Specific Mode

PNNI Private Network Node Interface

PPD Partial packet Discard

PPP Point to Point Protocol

PVC Permanent Virtual Connection

QoS Quality of Service

RAS Reliability/Availability/Serviceability

RAN Radio Access Node

RBOC Regional Bell Operating Company

SCR Sustained Cell Rate

SDH Synchronous Digital Hierarchy

SER Soft Error Recovery

SNMP Simple Network Management Protocol. A standard for the management of entities in a TCP/IP local area network.

SONET Synchronous Optical Network

SR Short Reach

SPVC Soft Permanent Virtual Connection

SVC Switched Virtual Connection

TAC Test Access Connection

TDM Time Division Multiplexing

TG Trunk Group

TM Traffic management

UMTS Universal Mobile Telecommunications Service

UNI User - Network Interface

VCI Virtual Channel Identifier

VPA Virtual Path Aggregation

VPI Virtual Path Identifier

VPN Virtual Private Network

VSR Very Short Reach

VS/VD Virtual Source/Virtual Destination

W-CDMA Wideband – Code Division Multiple Access




TABLE OF CONTENTS

1. INTRODUCTION .......................................................................................................9 1.1 Purpose .................................................................................................................9 1.2 Release Highlights ...............................................................................................9

1.2.1 Release 9.0 .......................................................................................................9 1.2.2 Release 9.1 .......................................................................................................9

2. OVERVIEW ..............................................................................................................10 2.1 System Overview ...............................................................................................10

2.1.1 7670 RSP .......................................................................................................10 2.2 Operating Environment ......................................................................................10 2.3 Mechanicals and Packaging ...............................................................................11

2.4 Configuration Limits ..........................................................................................11 2.5 Performance .......................................................................................................41 2.6 Reliability, Availability and Serviceability (RAS) ............................................47

2.7 Supported Features Tables .................................................................................47

3. NEW FEATURES AND FUNCTIONALITY IN RELEASE 9.0.............................53 3.1 Any Service Any Port (ASAP) on the ESC .......................................................53

3.1.1 Overview ........................................................................................................53 3.1.2 Specifications .................................................................................................53

3.2 MLPPP with Fragmentation ..............................................................................54


3.3 16 DS1 over MLPPP ..........................................................................................56 3.3.1 Overview ........................................................................................................56 3.3.2 Specifications .................................................................................................56

3.4 IP Interfaces on the ESC ....................................................................................56 3.4.1 Overview ........................................................................................................56 3.4.2 Specifications .................................................................................................56

3.5 Test Access Connections (TAC) on ESC ..........................................................58


4. NEW FEATURES AND FUNCTIONALITY IN RELEASE 9.1.............................60 4.1 Pseudo Wire Redundancy ..................................................................................60


4.2 Pseudo Wire Status Signaling ............................................................................63


4.3 LCR Enhancement .............................................................................................64 4.3.1 Overview ........................................................................................................64 4.3.2 Specifications .................................................................................................64




4.4 L2 Cache/SER Configuration ............................................................................66


4.5 IOC Auto-Reset .................................................................................................66 4.5.1 Overview ........................................................................................................66 4.5.2 Specifications .................................................................................................66

5. PRODUCT COMPLIANCE ......................................................................................70

5.1 Standards That This Release Meets ...................................................................70

5.1.1 IP Standards ...................................................................................................70 5.1.2 ATM Standards ..............................................................................................73 5.1.3 Product Integrity and Type Approval Standards: ..........................................75




LIST OF TABLES

Table 2-1 Operating Environment .....................................................................................11

Table 2-1: ATM Infrastructure Supported Features Table ................................................48

Table 2-2: ATM Routing/Signaling Supported Features Table .........................................49

Table 2-3: IP Infrastructure & OAM Supported Features Table .......................................50

Table 2-4: IP Routing Supported Features Table ..............................................................51

Table 2-5: MPLS Supported Features Table .....................................................................51

Table 2-6: VPN Supported Features Table ........................................................................52

Table 5-1: Release 9.x IP/MPLS Compliance listing ........................................................73

Table 5-2: Release 9.x ATM Compliance listing ..............................................................75

Table 5-3:7670 RSP Release 9.x Type Approval Compliance Summary .........................75




1. INTRODUCTION

1.1 Purpose

This Release Description document provides an overview of the new functionality of Release 9.x of the 7670 RSP.

Release 9.x of the 7670 RSP is derived from Release 8.x 7670 RSP, and therefore Release 9.x includes all functionality specified in 31RD0048 and earlier as well as the functionality specified in this document except where noted.

1.2 Release Highlights

1.2.1 Release 9.0

The major offering in Release 9.0 of the 7670 RSP, includes:

• Any Service Any Port on the ESC

• MLPPP with fragmentation

• IP Interfaces on the ESC

• 16 DS1s per MLPPP bundle

• TACs on ESC

Note:

None of the Release 8.0, or Release 8.2 content is supported in Release 9.0. All of the Release 8.1.x content is supported in Release 9.0.

1.2.2 Release 9.1

The major offering in Release 9.1 of the 7670 RSP, includes:

• Pseudo Wire Redundancy

• Pseudo Wire Status Signaling

• LCR Enhancement

• L2Cache mode/SER Configuration

• IOC Auto-Reset

Note:

None of the Release 8.0, or Release 8.2 content is supported in Release 9.1. All of the Release 8.1.x content is supported in Release 9.1, pending specific restrictions or notables in the Release 9.1 Release Notice.




2. OVERVIEW

2.1 System Overview

2.1.1 7670 RSP

The 7670 RSP is a carrier-grade multi-service IP platform enabling service providers to offer L2 and L3 services in their native mode.

The 7670 RSP is available in either a single shelf or a multi-shelf configuration. The Release 9.x software is supported in either single shelf or multi-shelf configurations.

2.2 Operating Environment

Release 9.x of the 7670 RSP is intended to be installed and deployed in Telecom Central Office Facilities that provide weather protection and a temperature controlled environment. Protection from mold growth, pest incursion, and precipitation are provided by the facilities. Shock and Vibration is limited to Very Low Levels, typical of Modern Office Buildings. Table 2-1 provides general operating environment specifications and is for information purposes only.

Category Specification

Shipping and Storage Temperature

–40 °C to 70 °C (– 40 °F to 158 °F)

Normal Operating Temperature 5 °C to 40 °C (41 °F to 104 °F)

Short-term 1 Operating Temperature

–5 °C to 55 °C (23 °F to 131 °F)

Normal Relative Humidity 5% to 85%

Short-term 1 Relative Humidity 5% to 95%, not to exceed 35 g of water per 1 cubic meter of air (0.024 lb of water per 1 lb of air)

Altitude Between 60 m (197 ft) below sea level and 1800 m (5906 ft) above sea level (70kPa to 106kPa)

Earthquake Suitable for High Risk Areas

Pollution Degree 2 2

1 Short- term is a period of less than 96 consecutive hours and a total of no more than 15 days per year. This refers to a total of 360 hours per year, with short-term periods occurring no more than 15 times per year.

2 Pollution Degree as defined in IEC 60950




Rated Voltage -48VDC/-60VDC

Operating Voltage Range -40Vdc to -75Vdc

Table 2-1 Operating Environment

2.3 Mechanicals and Packaging

Release 9.x utilizes the same shelves developed in 7670 RSP Release 3.0 and 2.2 with integral cable management, power distribution and cooling systems.

2.4 Configuration Limits

The following tables present configuration limits pertaining to 7670 RSP Release 9.x and previous releases. Please note that for some items, the limit differs depending on whether the 7670 RSP is using control card CC2 or control card CC2G.

System Configuration Limits

Criteria/Description R7.x R8.x R9.x

Maximum Number of I/O Peripheral Shelf - Single Shelf

1 1 1

Maximum Number of I/O Peripheral Shelves – Multi-Shelf 3

15 15 15

Maximum Number of I/O Peripheral Shelves at full capacity

8 8 8

Maximum Number of I/O Peripheral Shelves when ESC cards are deployed

3 Rel 8.1 and below- 3

Rel 8.1.1- 6

Rel 8.2: 3

6

Maximum number of HISLs - Multi Shelf

32+32 (redundant) 32+32 (redundant) 32+32 (redundant)

Maximum number of CSLs - Multi Shelf

16 + 16 (redundant) 16 + 16 (redundant) 16 + 16 (redundant)

Maximum HISL Length - Multi Shelf

70m 70m 70m

3 Tested to 8 shelves.





Maximum CSL Length - Multi Shelf

70m 70m 70m

Card Slot and Port Maximums


Maximum Number of PS 3.5G Line Card slots. - Single Shelf

14 14 14

Maximum Number of PS 3.5G Line Card slots. - Multi Shelf 4

208 (1+1 Config) 208 (1+1 Config) 208 (1+1 Config)

Maximum number of ESC Line Cards per Single Shelf (w. CC1G, a.k.a. CC2)

n/a n/a n/a

Maximum number of ESC Line Cards per Single Shelf (w. CC2G)

14

(14 x simplex or 7+7 redundant)

14


14


Maximum number of ESC Line Cards in a Multi Shelf system

24


24


24


Maximum number of OC3c/STM1 interfaces per system - Single Shelf5

224 224 224

Maximum number of OC3c/STM1 interfaces per system - Multi Shelf 6

1760 non-redundant ports, 1664 redundant pairs



4 Tested to 110 slots.

5 Note that for APS or line card redundancy these numbers are reduced by half.

6 Tested to 1760 non-redundant ports or 880 redundant pairs.





Maximum number of OC12c/STM4 interfaces per system - Single Shelf7

56 56 56

Maximum number of OC12c/STM4 interfaces per system - Multi Shelf 8




Maximum number of Gigabit Ethernet interface per system - Single Shelf7

56 56 56

Maximum number of GigE interface per system - Multi Shelf

440 440 440

Maximum number of GigE Link Aggregation Group (802.3ad) per system

64 64 64

Maximum number of GigE Link Aggregation Group (802.3ad) per slot

4 4 4

Maximum number of GigE port in a Link Aggregation Group

2 2 2

Maximum number of OC48c/STM16 interfaces per system in PS - Single Shelf 7

14* 14* 14*

Maximum number of OC48c/STM16 interfaces per system in PS - Multi Shelf 9





8 Tested to 440 non-redundant ports or 220 pairs.

9 Tested to 110 non-redundant ports or 55 redundant pairs.





Maximum number of Channelized OC48/STM16 interfaces per system - Single Shelf 10

14 14 14

Maximum number of Channelized OC48/STM16 interfaces per system - Multi Shelf




Maximum number of DS-1 channels per Channelized OC-3 port on ESC

84 84 84

Maximum number of DS-1 channels per 8p Channelized OC-3 I/O on ESC

672 (8*84) 672 (8*84) 672 (8*84)

Maximum number of E1 channels per Channelized STM1 port on ESC

63 63 63

Maximum number of E1 channels per 8p Channelized STM1 I/O on ESC

504 (8*63) 504 (8*63) 504 (8*63)

Maximum number of DS-1 channels per Channelized OC-12 port on ESC

336 336 336

Maximum number of DS-1 channels per ESC 4-port OC12c/STM4c I/O card (2 active ports only)

672 (2*336) 672 (2*336) 672 (2*336)

Maximum number of E1 channels per Channelized STM4 port on ESC

252 252 252






Maximum number of E1 channels per ESC 4-port OC12c/STM4c I/O card (2 active ports only)

504 (2*252) 504 (2*252) 504 (2*252)




Common ATM and MPLS Connection Limits

Note: the term “connection” applies to ATM VCs and MPLS LSPs, unless otherwise specified.


No. of signaled and configured connections per system 11

Maximum connections per node : 768,000

Minimum ATM connections per node : 200,000





Maximum No. of configured connections per system. 11

256,000 per node 256,000 per node 256,000 per node

No. of VP Connections per system

32,000 per node 32,000 per node 32,000 per node

ATM/IMA/MLPPP Data Plane Limits


No. of ATM endpoints per MR16 ATM card

256,000 256,000 256,000

No. of ATM endpoints per MR16 OC3/STM1 port

64,000 64,000 64,000

No. of ATM endpoints per MR16 OC12/STM4 port

64,000 64,000 64,000

No. of ATM endpoints per MR48 Concatenated (clear channel) OC48c/STM16c port

93,000 93,000 93,000

No. of ATM endpoints per MR48 channelized OC48c/STM16c port

82,000 82,000 82,000

11 Release 2.2 onwards, the 7670 RSP shares connection resources between ATM and

MPLS applications. The maximum number of ATM connections on a node is dependent on the number of connection resources in use by LSPs.





No. of ATM endpoints per MR48 1-port OC48c/STM-16c I/O

Channelized mode: 82,000

Clear channel mode: 93,000





No. of ATM endpoints per MR48 OC12c/STM4c channel or port

20,500 20,500 20,500

No. of ATM endpoints per MR48 per 4-port OC12c/STM4c I/O card

82,000 82,000 82,000

No. of ATM endpoints per MR48 OC3c/STM1c channel or port

20,500 20,500 20,500

No. of ATM endpoints per MR48 8-port OC3/STM-1 I/O card

41,000 41,000 41,000

No. of ATM endpoints per MR48 DS3 channel

20,500 20,500 20,500

No. of ATM endpoints per ESC card

16,000 16,000 16,000

No. of ATM endpoints per ESC 8-port OC3/STM-1 I/O Card

16,000 16,000 16,000

No. of ATM endpoints per Channel on ESC

8,000 8,000 8,000

No. of ATM endpoints per IMA Group on ESC

8,000 8,000 8,000

No. of IMA Groups per Chan. OC-3/STM-1 port on ESC

42 42 42

No. of MLPPP Bundles per Chan. OC-3 port on ESC

42 n/a 42

No. of IMA Groups per 8p Chan. OC-3/STM-1 I/O on ESC

336 (8*42) 336 (8*42) 336 (8*42)





No. of MLPPP Bundles per 8p Chan. OC-3 I/O on ESC

336 (8*42) n/a 336 (8*42)

No. of IMA Groups per Chan OC-12/STM-4 port on ESC

168 (4*42) 168 (4*42) 168 (4*42)

No. of MLPPP Bundles per Chan OC-12 port on ESC

168 (4*42) n/a 168 (4*42)

No. of IMA Groups per 4p Chan. OC12/STM-4 I/O on ESC (2 active ports only)

336 (2*4*42) 336 (2*4*42) 336 (2*4*42)

No. of MLPPP Bundles per 4p Chan. OC12 I/O on ESC (2 active ports only)

336 (2*4*42) 336 (2*4*42) 336 (2*4*42)

No. of member links in an IMA Group on ESC

8 Rel 8.1.2 and above = 16

Below Rel8.1.2 = 8

16

No. of member links in an MLPPP Bungle on ESC

8 n/a 16

Maximum number of spatial multicast endpoints (combined roots and leafs) in the system

13,000 13,000 13,000

Maximum number of ATM multicast root endpoints

6,500 6,500 6,500

Maximum number of ATM multicast (logical and spatial multicast) root endpoints plus leaf endpoints

13,000 13,000 13,000

Maximum number of ATM multicast leaf endpoints per root endpoint

4,000 4,000 4,000





Maximum number of ATM multicast root endpoints per line card

1000 1000 1000

Maximum number of ATM multicast leaf endpoints per I/O port that share a common root endpoint

100 100 100

Maximum number of multicast parties per P2MP SVC or S-SPVC

5000 5000 5000

No. of OAM-PM Sessions per MR16 DS3 port

12 12 12

No. of OAM-PM Sessions per MR48 DS3 port

12 12 12

No. of OAM-PM Sessions per MR16 OC3/STM1 port

30 30 30


30 30 30


120 120 120


120 120 120

No. of OAM-PM Sessions per MR16 OC48c/STM16c port

480 480 480

No. of OAM-PM Sessions per MR48 OC48c/STM16c port (non OC48 clear channel)

480 480 480

No. of OAM-PM Sessions per MR48 OC48c/STM16c port (OC48 clear channel)

240 240 240





No. of OAM-PM Sessions per MR16 card

480 480 480

No. of OAM-PM Sessions per MR48 card (non OC48 clear channel)

480 480 480

No. of OAM-PM Sessions per MR48 card (OC48 clear channel)

240 240 240

No. of OAM-PM Sessions per system

52800 52800 52800

No. of VC-VLAN connections to GigE Port/VLAN interfaces per 7670 RSP node

100,000 100,000 100,000

No. of VC-VLAN connection to GigE Port/VLAN interfaces per GigE line card or port

960 960 960

No. of VC-VLAN connections to GigE VLAN endpoints per 7670 node

128,000 128,000 128,000

No. of VC-VLAN connection to GigE VLAN endpoints per GigE line card

16,376 16,376 16,376

No. of VC-VLAN connection to GigE VLAN endpoints per GigE port

4,094 4,094 4,094




MPLS Data Plane 12


No. of RSVP-TE signaled originating, terminating, or transit LSPs per system**

10,000 10,000 10,000

No. of RSVP-TE signaled LC-ATM originating LSPs per MR48

10,000 10,000 10,000

No. of RSVP-TE signaled LC-ATM transit LSPs per MR48

10,000 10,000 10,000

No. of RSVP-TE signaled LC-ATM destination LSPs per MR48

10,000 10,000 10,000

No. of RSVP-TE signaled Generic originating LSPs per Quad GIGE

10,000 10,000 10,000

No. of RSVP-TE signaled Generic originating LSPs per MR48

10,000 10,000 10,000

No. of RSVP-TE signaled Generic transit LSPs per Quad GIGE

10,000 10,000 10,000

No. of RSVP-TE signaled Generic transit LSPs per MR48

10,000 10,000 10,000

No. of RSVP-TE signaled Generic destination LSPs per

10,000 10,000 10,000

12 In Release 2.2 and above, the 7670 RSP shares connection resources between ATM

and MPLS applications. The maximum number of LSP connections on a node is dependent on the number of connection resources in use by ATM.




Criteria/Description R7.x R8.x R9.x Quad GIGE

No. of RSVP-TE signaled Generic destination LSPs per MR48

10,000 10,000 10,000

No. of CR-LDP signaled LC-ATM originating LSPs per system

10,000 10,000 10,000

No. of CR-LDP signaled LC-ATM originating LSPs per MR48

10,000 10,000 10,000

No. of CR-LDP signaled LC-ATM transit LSPs per system

10,000 10,000 10,000

No. of CR-LDP signaled LC-ATM transit LSPs per MR48

10,000 10,000 10,000

No. of CR-LDP signaled LC-ATM terminating LSPs per system

10,000 10,000 10,000

No. of CR-LDP signaled LC-ATM terminating LSPs per MR48

7095 7095 7095

No of LDP DU signaled labels (originating and terminating) per system

40,000 40,000 40,000

No. of originating or terminating P-LSPs per system

4,000 4,000 4,000

No. of transit P-LSPs per system or per card

64,000 64,000 64,000

No. of P-LSPs per Quad GigE

3,777 3,777 3,777

No. of P-LSPs per MR48

System Limit System Limit System Limit

No. of Ethernet/IP Pseudo-Wire endpoints per 7670 RSP node.

7,000 7,000 7,000





No. of Ethernet/IP Pseudo-Wire endpoints per GigE line card.

964 964 964

No. of Ethernet pseudowire ATM endpoints per MR48 line card.

2000 2000 2000

No. of ATM and TDM Pseudo-Wire endpoints per 7670 RSP node.

10,000 10,000 10,000

No. of TDM Pseudo Wire endpoints per ESC card.

n/a R8.0 – n/a

R8.1 – 1376

1376

No. of TDM Pseudo Wire endpoints per single OC12 or four OC3 ports

n/a R8.0 – n/a

R8.1 - 688

688

MPLS Filter Limits


No. of IP Destination filters per system 84,000 84,000 84,000

No. of CoS filters per system 4,000 4,000 4,000

No. of IGP / BGP Shortcut filters per system

4,000 4,000 4,000

OAM&P Limits


No of MPLS Tunnels with MPLS OAM CV enables

Per card = 256

Per system = 512

Per card = 256

Per system = 512

Per card = 256

Per system = 512




No. of Endpoint Configuration Records13

128,000 128,000 128,000

ATM S-PVC/SVC Limits


Maximum no. of SVC Signaling Channels per switch

3,200 3,200 3,200

Maximum no. of S-PVC path origins per switch

256,000 256,000 256,000

Maximum no. Operator Directed Routes ODR

1,000 1,000 1,000

Maximum no. of SVC subscribers (ILMI registered and customer programmed)

4,000 4,000 4,000

Maximum no. of customer programmed users (not ILMI)

3,200 3,200 3,200

Maximum no. of trunk groups per switch 3,200 3,200 3,200

Maximum no. of trunk groups per port 256 256 256

Maximum no. of calls in Setup Pending State of Add Party Pending state per switch

5,000 5,000 5,000

Maximum no. of users (SSN or MSN) per trunk group

16 16 16

Maximum no. of route lists per switch 200 200 200

Maximum no. of routes per node 200 200 200

Maximum no. of Signaling Link Profiles 20 20 20

Maximum no. of subscriber profiles 50 50 50

13 Connection endpoints have a default configuration based upon the port reference type

configuration. Changing any (or all) endpoint configuration away from these defaults will result in an endpoint configuration record being allocated on the 7670 RSP. The 7670 RSP has a system wide limit of 128,000 endpoint configuration records. For a given endpoint if you can one or all of the defaults for that endpoint it will result in only one endpoint configuration record being allocated. Current endpoint configurations that can be changed are OAM-CC, ALS, Segment configuration of intermediate or termination and VPT





Maximum number of SPVC paths (source plus destination plus transit) simultaneously pending a Modify Request operation

N/A N/A N/A

Maximum no. of SPVC originating endpoints that can simultaneously launch an HCM operation

2000 2000 2000

Maximum no. of SPVC terminating endpoints that can simultaneously terminate an HCM operation

2000 2000 2000

Maximum number of NCCI roots for NCCI configured on S-PVC path endpoints, per node

1000 1000 1000

Maximum number of NCCI roots for transiting S-PVCs

10000 10000 10000

Maximum number of SPVCs transiting an IMA group on the ESC card

n/a 2046 2046

PNNI Limits


Number of PNNI Hierarchical Levels 3 3 3

Number of PNNI Lowest Level or Logical Group Nodes stored in the Topology Database

400 400 400

Number of switches in a PNNI network :

- (3 levels of hierarchy, approx. 66 nodes per level equals 66 to the power of 3, equals approx. 250,000)

- (3 levels, approx. 133 nodes per level = 133 to the power of 3 = 2.3 million)

2.3 Million 2.3 Million 2.3 Million

Number of PNNI PVC based Links per Node

300 300 300

Number of “inside” Neighbors at the lowest level of hierarchy

300 300 300





Number of SVCC based RCC connections for the lowest level node (Asymmetrical SVCC based RCCs connections)

25

25

25

Number of SVCC based RCC connections for each logical group node

25 25 25

Number of Parallel links to the same “inside” Neighbor

16 16 16

Number of Parallel links to the same adjacent Peer Group (“outside” neighbor)

60 60 60

Number of link advertisement “edges” visible by a node in the PNNI network, stored in the Topology Database. Defined as the number of advertised “edges” including horizontal edges and up-link edges from lowest level and logical group nodes. Total # of links in the network could be much larger.

4,000 4,000 4,000

Number of Exterior Reachable Address configurable on the lowest level node

500 500 500

Total number of internal or external summarizing, suppressing or exception addresses configurable on all logical nodes in the hierarchy (the lowest level node allows an additional set of exterior addresses, see the limit for # of exterior addresses configurable on the lowest level node)

1,000 1,000 1,000

Number of simultaneous PNNI Connection Trace requests supported

100 100 100

Maximum data storage available for simultaneous PNNI Connection Traces

50 * 1466 bytes

50 * 1466 bytes 50 * 1466 bytes

Number of PNNI Path Trace Filters supported

50 50 50

Maximum data storage available for PNNI Path Traces

100 * 1466 bytes

100 * 1466 bytes

100 * 1466 bytes

Maximum number of Routing Table Descriptor (RTD)

25 25 25

Maximum number of global policy per system

800 800 800





Maximum number of global policy constraint per system

800 800 800

Maximum number of configurable Rp-NSC ID on each trunk group partition

3 3 3

Maximum number of Ne-NSC ID on a trunk group advertised by P-NNI link

5 5 5

ATM SVC Routing Plane


No. of SVC routing table entries (static and PNNI exterior reachable) per switch

500 500 500

No. of PNNI generated routing table entries per switch

5,000 5,000 5,000

No. of parallel trunk groups (trunk groups per route) per switch

60 60 60

No. of routes per route list 2 2 2

ATM SVC Address Translation Limits


No. of address translation tables per switch 100 100 100

No. of entries per address translation table 5,000 5,000 5,000

ILMI Limits


No. of ILMI sessions per switch 734 734 734




Spooling Data Storage Limits


On-node spooling data storage limits 64 Mbytes 64 Mbytes 64 Mbytes

With respect to on-node spooling storage, the 7670 RSP is able to store:

• up to 2 hours (1.5 hours for R2.2) of PVC usage records up to the limit of PVC connections supported in this Release, where half of the PVC interfaces on the node are UNI interfaces (with billing applied).

• or approximately 3.5 minutes (2.5 minutes for R2.2) of SVC usage records with an SVC call rate of 1000 call/s, where half of the interfaces on the node are UNI, and only a small percentage of calls originate and terminate on a UNI interface."

ATM Traffic Management Limits


No. of service categories 5 5 5

Number of Quality of Service (QoS) 8 8 8

SNMP Limits


No. of SNMP Communities 10 10 10

No. of SNMP Access Views 20 20 20

No. of SNMP Access Groups 10 10 10

No. of SNMP Users 20 20 20

CPSS Limits


No. of node (7470 MSP and 7670 RSP) per 250 250 250




CPSS domain with in-band CPSS

No. of CPSS routing neighbors 15 15 15

No. of CPSS stub neighbors 60 60 60

No. of CPSS leaf nodes 1020 1020 1020

Note that the 5620 Network Manager may impose additional limits on network size, number of nodes, and number of CPSS domains.

IPv4 Routing Plane Limits


FIB size (no. of IP route entries per platform (unique))

1,000,000 1,000,000 1,000,000

BGP4 RIB size (no. of AS path entries per switch (non-unique))

2,000,000 2,000,000 2,000,000

No. IP route entries per line card with IP forwarder

450,000 450,000 450,000

No. of IP static routes 40,000 40,000 40,000

No. of BGP peering sessions per switch

1000 1000 1000

No. of OSPF links to neighboring routers per RSP (includes directly attached, virtual, and parallel links)

250 Rel 8.1 and below- 250

Rel 8.1.1- 600

Rel 8.2: 250

600

No. of OSPF links to neighboring routers per RSP, within a single area (includes directly attached, virtual, and parallel links)

250 Rel 8.1 and below – 250

Rel 8.1.1- 600

Rel 8.2: 250

600

No. OSPF adjacencies per area (for the entire OSPF network, including links to neighbours of the 7670 RSP, and all other

1,000 1,000 1,000




Criteria/Description R7.x R8.x R9.x adjacencies within the area)

No. of OSPF areas per switch

100 100 100

No. of OSPF routers per area

800 800 800

No. of OSPF routes per RSP

50,000 50,000 50,000

No. of IS-IS adjacencies per switch

100 100 100

No. of IS-IS links (directly attached) per switch

100 100 100

No. of IS-IS summary addresses per 7670 RSP

64 64 64

No. of IS-IS routers per area

200 200 200

No. of IS-IS area ID configured per switch

3 3 3

No. of IS-IS routes per RSP

20,000 20,000 20,000

No. of RIP Interfaces 1,000 1,000 1,000

No. of RIP routes 50,000 50,000 50,000

No. of PIM Interfaces 1,000 1,000 1,000

No. of IP multicast group per system

4,000 4,000 4,000

No. of static rendezvous point IP address

4,000 4,000 4,000

No. of static IP multicast groups per line card

500 500 500

No. of dynamic IP multicast groups per line card

300 300 300

Max no. static leaves (static IGMP join) per system

14,000 14,000 14,000





Max no. of leaves (static and dynamic) per multicast group per slot:

GigE: 964 MR48: 500

GigE: 964 MR48: 500

GigE: 964 MR48: 500

Max no. of leaves (static and dynamic) for all multicast groups per slot:

GigE: 20,000 MR48: 20,000

GigE: 20,000 MR48: 20,000

GigE: 20,000 MR48: 20,000

Maximum number of rules per access list used for route filtering

1,000 1,000 1,000

No. of AS-path list 3,000 3,000 3,000

No. of AS-path list entries

150,000 150,000 150,000

Maximum number of AS-path list entries per AS-path list

1,000 1,000 1,000

No. of community lists 3,000 3,000 3,000

No. of community lists entries

150,000 150,000 150,000

Maximum number of community list entries per community list

1,000 1,000 1,000

No. of extended community lists

3,000 3,000 3,000

No. of extended community lists entries

150,000 150,000 150,000

Maximum number of extended community list entries per community list

1,000 1,000 1,000

No. of prefix lists 3,000 3,000 3,000

No. of prefix list entries 150,000 150,000 150,000

Maximum number of prefix list entries per prefix list

1,000 1,000 1,000

No. of route-maps 3,000 3,000 3,000

No. of route-map match- 150,000 150,000 150,000




Criteria/Description R7.x R8.x R9.x set sequences

Maximum number of route-map match-set sequences per route map

1,000 1,000 1,000

No. of OSPF VRF Contexts per Switch

16 16 16

No. of RIP routes per VRF instance (w. CC1G, a.k.a. CC2)

n/a n/a n/a

No. of RIP routes per VRF instance (w. CC2G)

1000 1000 1000

No. of RFC 4364 VRFs per system (in addition to the default routing table and includes all IPv4 or IPv6 based VRFs)

2,000 2,000 2,000

No. of RFC 4364 VRFs per line card (includes both IPv4 and IPv6 based VRFs)

254 254** 254**

No. of RFC 4364 VPN IP Prefix

1,000,000 1,000,000 1,000,000

No. of BFD sessions per GigE card

n/a R8.0 – n/a

R8.1 – 200

R8.2 – n/a

200

Number of ECMP route entries per system

4095 4095 4095

Maximum number of GigE ARP entries in the ARP cache

16,382 16,382* 16,382*

Maximum number of MR48 ARP entries in the ARP cache

16,384 16,384* 16,384*

Maximum number of static ARP entries per slot (GigE or MR48)

1,024 1,024 1,024





Maximum number of static ARP entries per system

16,384 16,384 16,384

* Note that the number of cache entries for ARP and ND are completely separate and are not dependent upon each other.

** Note that the number of VRFs is reduced to 253 per MR48 lineacrd if the card mode is set to IPv6 or Dual-Stack when a Dual-Stack card is inserted.

IPv6 Routing Plane Limits (required CC2G)


FIBv6 size (no. of IPv6 route entries per platform (unique))

100,000 100,000 100,000

No. of IPv6 routes on the MR48 line card 100,000 100,000 100,000

No. of IPv6 routes on the GigE line card 100,000 100,000 100,000

BGP4 RIBv6 Size - Max number of BGP 6PE and 6VPE prefixes

500,000 500,000 500,000

No. of BGP4 Peers for 6PE 2000 2000 2000

Max number of BGP allocated labels n/a 131,072 (128*1024)

131,072 (128*1024)

Max number of BGP+ 6VPE PE/CE and BGP L3VPN PE/CE peers per system

n/a Rel 8.0: 1,000

Rel 8.1: n/a

Rel 8.2: 1,000

n/a

Max number of BGP+ and BGP peer groups per system

n/a Rel 8.0: 200

Rel 8.1: n/a

Rel 8.2: 200

n/a

Max number of non-unique prefixes pf 6PE, 6VPE and/or IPv6 routes in the BGP RIB

n/a Rel 8.0: 500,000

Rel 8.1: n/a

Rel 8.2: 500,000

n/a

No. of IP static routes 10,000 10,000 10,000

No. of routes in the default IPv6 VRF 100,000 100,000 100,000





No. of routes in a VRF other than the default IPv6 VRF

1,000 1,000 1,000

No. of CEs per PE 10,000 10,000 10,000

No. of loopback interfaces 2021 2021 2021

No. of Neighbor Discovery entries in the neighbor cache of the GigE card

16,382 16,382 16,382

No. of Neighbor Discovery entries in the neighbor cache of the MR48 card

16,384 16,384* 16,384*

No. of Ipv6 global addresses assigned to interfaces

n/a R8.0 – 16,000

R8.1 – n/a

R8.2 – 16,000

R8.0 – 16,000

R8.1 – n/a

R8.2 – 16,000

No. of IPv4/IPv6 Dual Stack Interfaces per system

n/a R8.0 – 16,000

R8.1 – n/a

R8.2 – 16,000

R8.0 – 16,000

R8.1 – n/a

R8.2 – 16,000

* Note that the number of cache entries for ARP and ND are completely separate and are not dependent upon each other.

IPv4 Data Plane Limits


No. of IPv4 and Ipv6 interfaces per system

100,000 100,000 100,000

No. of control card loopback interfaces

2,020 2,020 2,020

No. of L3 interfaces per Quad GigE card (includes IPv6)

964 964 964

Max No. of L3 interfaces per MR48 (includes IPv6): standard mode/scaled mode

2,000/16,000 2,000/16,000 2,000/16,000

No. of DSCP profile per switch 16 16 16

IP packet maximum transmission unit

9,192 9,192 9,192





PPP Sessions per MR48 (PPPoSONET + PPPoA)

2,047 2,047 2,047

PPPoSONET Sessions per MR48 48 48 48

PPPoA Sessions per MR48 2,000 2,000 2,000

PPP Sessions per System (PPPoSONET + PPPoA)

14,000 14,000 14,000

Number of interface group per system

300 300 300

Number of interface group per line card

255 255 255

Number of line card in an interface group

1 1 1

Number of port/channel in an interface group

1 1 1

Number of member interface in an interface group

16,000 16,000 16,000

Number of host attached to a member interface

8 8 8

Number of static routes per member interface

0 0 0

System limit of the number of numbered, standard access lists*

100 100 100

System limit of the number of numbered, extended access lists*

100 100 100

System limit of the number of named access lists*

11,800 11,800 11,800

System limit of the number of access rules*

64,000 64,000 64,000

Maximum number of rules per access list used for packet filtering*

250 250 250

Maximum number of rules per access list used for IPv4 MFC

250 250 250

Maximum number of rules per access list used for route filtering*

1,000 1,000 1,000

Control card limit of the total 250 250 250




Criteria/Description R7.x R8.x R9.x number of rules supported for all control card ethernet interfaces (mgmt and spool)*

Control card limit of the total number of rules supported on all VRF and non-VRF loopback interfaces. *

10,000 10,000 10,000

Control card limit of the number of access lists per control card interface (loopback, mgmt and spool)*

1 per i/f 1 per i/f 1 per i/f

GIGE limit: maximum no. of unique access lists per GIGE (within system limits and card datapath rule limit)*

2 per IP i/f for pkt filtering, 1 per IP i/f for MFC



MR48 limit: maximum no. of unique access lists for packet filtering per MR48 (within system limits and card datapath rule limit)*

255 255 255

MR48 limit: maximum no. of unique access lists for MFC per MR48 (within system limits and card datapath rule limit)*

111 111 111

GIGE limit: Maximum no. of ACL line card rules for Quad GigE*

16383 16383 16383

MR48 limit: Maximum no. of ACL line card rules for MR48*

64506 64506 64506

Per-IP-flow rate limiting, minimum rate limit (packets/sec) – GIGE*

1 1 1

Per-IP-flow rate limiting, minimum rate limit (packets/sec) - MR48*

1 1 1

Per-IP-flow rate limiting, maximum rate limit (packets/sec) – GIGE*

8000 8000 8000

Per-IP-flow rate limiting, maximum rate limit (packets/sec) -

8000 8000 8000




Criteria/Description R7.x R8.x R9.x MR48*

Per-IP-flow rate limiting, maximum number of rules – GIGE*

992 minus no. policers used by i/f



Per-IP-flow rate limiting, maximum number of rules - MR48*

1000 1000 1000

* - The ACL limit specified is applicable to either IPv4 or IPv6. The limit specified can be distributed as required between both IPv4 and/or IPv6.

IPv6 Data Plane Limits


No. of IPv6 interfaces per system 16,000 16,000 16,000

No. of Dual-Stack interfaces per system n/a R8.0: 16,000

R8.1: n/a

R8.2: 16,000

n/a

No. of control card IPv6 loopback interfaces

1 1 1

No. of IPv6 interfaces per MR48 card 2,000 2,000 2,000

No. of L3 interfaces per Quad GigE card 964 964 964

No. of DSCP profiles per switch 16 16 16

IP packet maximum transmission unit 9192 9192 9192

No. of Ipv6 global addresses assigned to interfaces

n/a R8.0 – 16,000

R8.1 – n/a

R8.2 – 16,000

R8.1 – n/a

No. of Dual Stack interfaces n/a R8.0 – 16,000

R8.1 – n/a

R8.2 – 16,000

n/a





System limit of the number of numbered, standard IPv6 access lists*

n/a 100 100

System limit of the number of numbered, extended access lists*

n/a 100 100

System limit of the number of named access lists*

n/a 11,800 11,800

System limit of the number of access rules* n/a 64,000 64,000

Maximum number of rules per access list used for IPv6 MFC

n/a 0 0

Maximum number of rules per access list used for packet filtering*

n/a 250 250

Maximum number of rules per access list used for route filtering*

n/a 1,000 1,000

Control card limit of the total number of rules supported for all control card ethernet interfaces (mgmt and spool)*

n/a 250 250

Control card limit of the total number of rules supported on all VRF and non-VRF loopback interfaces. *

n/a 10,000 10,000

Control card limit of the number of access lists per control card interface (loopback, mgmt and spool)*

n/a 1 per i/f 1 per i/f

GIGE limit: maximum no. of unique access lists per GIGE (within system limits and card datapath rule limit)*

n/a 2 per IP i/f for pkt filtering, 1 per IP i/f for MFC


MR48 limit: maximum no. of unique access lists for packet filtering per MR48 (within system limits and card datapath rule limit)*

n/a 255 255

MR48 limit: maximum no. of unique access lists for MFC per MR48 (within system limits and card datapath rule limit)*

n/a 111 111

GIGE limit: Maximum no. of ACL line card rules for Quad GigE*

n/a 16383 16383

MR48 limit: Maximum no. of ACL line card rules for MR48*

n/a 64506 64506





Per-IP-flow rate limiting, minimum rate limit (packets/sec) – GIGE*

n/a 1 1

Per-IP-flow rate limiting, minimum rate limit (packets/sec) - MR48*

n/a 1 1

Per-IP-flow rate limiting, maximum rate limit (packets/sec) – GIGE*

n/a 8000 8000

Per-IP-flow rate limiting, maximum rate limit (packets/sec) - MR48*

n/a 8000 8000

Per-IP-flow rate limiting, maximum number of rules – GIGE*

n/a 992 minus no. policers used by i/f


Per-IP-flow rate limiting, maximum number of rules - MR48*

n/a 1000 1000

* - The ACL limit specified is applicable to either IPv4 or IPv6. The limit specified can be distributed as required between both IPv4 and/or IPv6.

MPLS Signaling Plane Limits


No. of MPLS signaling link per system 200 R8.0- 200

R8.1 – 1000

R8.0- 200

R8.1 – 1000

No. of explicit routed LSPs per system 4,000 4,000 4,000

Maximum number of tunnel interfaces 1400 1400 1400

Alarm Limits


Critical alarm queue size 100 100 100

Major alarm queue size 2000 2000 2000

Minor alarm queue size 2000 2000 2000

Diagnostic alarm queue size 2000 2000 2000





Logging alarm queue size 2000 2000 2000

Software Alarms 2000 2000 2000




2.5 Performance

The following tables present performance targets pertaining to 7670 RSP Release 8.x:

System Performance

Limit Description R7.x R8.x R9.x

System cold start time until data flowing on first connection

< 5 minutes < 5 minutes < 5 minutes

System cold start time until data flowing on last connection

20 minutes 20 minutes 20 minutes

Control activity switch outage time (new connections and management operations unavailable)

3 sec 3 sec 3 sec

Fabric activity switch outage time (including the Fabric Interface Card)

<60msec <60msec <60msec

PNNI routing activity switch outage time (switch trying to rebuild the routing table)

< 90 sec < 90 sec < 90 sec

IP routing activity switch outage time 60 msec 60 msec 60 msec

Data spooling activity switch outage time

< 90 sec < 90 sec < 90 sec

ATM & MPLS call control activity switch time (wait time to process new calls)

< 3 sec < 3 sec < 3 sec

CE call control activity switch time < 3 sec < 3 sec < 3 sec

Control redundancy database reconcile time

< 30 min < 30 min < 30 min

Line card with redundancy activity switch outage time

< 60 ms < 60 ms < 60 ms

1+1 SONET/SDH APS activity switch outage time

< 60 ms < 60 ms < 60 ms

Line card upgrade outage time when switching to a new load (hard reset)

Target < 3 minutes

Target < 3 minutes

Target < 3 minutes

Line card upgrade outage time when switching to a new load (soft reset with minor revision change) - ATM traffic outage time

< 60 msec < 60 msec < 60 msec





Line card upgrade outage time when switching to a new load (soft reset with minor revision change) - IP traffic and LSPs

< 5 seconds < 5 seconds < 5 seconds

Line card upgrade outage time when switching to a new load (soft reset with minor revision change) - CE traffic outage time


Line card upgrade outage time when switching to a new load (soft reset with major revision change) - ATM traffic outage time


Line card upgrade outage time when switching to a new load (soft reset with major revision change) - IP traffic and LSPs (all IP Forwarding cards)

< 30 seconds < 30 seconds < 30 seconds

Line card upgrade outage time when switching to a new load (soft reset with major revision change) - CE traffic outage time


Fabric activity switch multi-fault outage time

< 1 sec < 1 sec < 1 sec

HISL reset recovery time < 30 seconds < 30 seconds < 30 seconds

Connection Performance


PVC connection performance 50 connect/sec 50 connect/sec 50 connect/sec

SVC call setup per switch per second (P2P and P2MP, including setup and tear down of the call)

4500 cps 4500 cps 4500 cps

SVC call setup per switch per ATM line card (P2P and P2MP, including setup and tear down of the call)

1000+ cps 1000+ cps 1000+ cps




SVC P2MP Add Party per switch per second

65% of P2P rate

65% of P2P rate

65% of P2P rate

SVC Connections Setup/Clearing Delay

Mean = 30msec, 95% = 10 msec



S-LSP setup rate 400 cps 400 cps 400 cps

SPVC/SVC reroute rate 2000 endpoints/sec

2000 endpoints/sec

2000 endpoints/sec

PNNI Routing Performance


PNNI synchronization for a 50 node network with 1000 trunk group

< 30 sec

< 30 sec

< 30 sec

SVC Accounting Performance


SVC usage data record generation rate

Equal to call rate

Equal to call rate

Equal to call rate

Management Interface Performance


Aggregate sustained SNMP operation (object access/sec)

200

200

200




1+1 Automatic Protection Switching Performance (includes detection and switching times)


OC3c/STM1 ATM < 50 ms < 50 ms < 50 ms

OC12c/STM4c ATM < 50 ms < 50 ms < 50 ms

OC48c/STM16c ATM < 50 ms < 50 ms < 50 ms

OC48c/STM16c POS < 50 ms < 50 ms < 50 ms

OC3c/STM1 POS < 50 ms < 50 ms < 50 ms

OC12c/STM4c POS < 50 ms < 50 ms < 50 ms

IP Routing Plane Performance


IP Routing database convergence time for a 200 node network

< 3 minutes

< 3 minutes

< 3 minutes

Maximum BGP update rate (prefixes/second)

15,000

15,000

15,000

Maximum OSPF update rate (prefixes/second)

1,000

1,000

1,000

Maximum IS-IS update rate (prefixes/second)

1,000

1,000

1,000

Maximum number of BFD messages a second processed by the GigE line card

n/a R8.0 – n/a

R8.1 – 1200

R8.2 – n/a

1200

IPv6 Routing Plane Performance


Maximum 6PE BGP4 Update Rate 5,000 5,000 5,000




(prefixes/second)

IP Data Plane Performance


Maximum no. of IP packets for one GigE port (40 byte IP packets, padded to 64 byte Ethernet packet)

1,488,095 pps

1,488,095 pps 1,488,095 pps

Maximum no. of IP packets for one GigE line card (40 byte packet, padded to 64 byte Ethernet packet)

2,976,190 pps

2,976,190 pps 2,976,190 pps

Maximum no. of IP packets for OC-48c/STM-16c POS port (40 byte packets) - MR48

6,112,632 pps

6,112,632 pps 6,112,632 pps


1,528,158 pps

1,528,158 pps 1,528,158 pps


382,039 pps 382,039 pps 382,039 pps

Maximum no. of IP packets for OC-48c/STM-16c ATM port (40 byte packets) - MR48

5,651,320 pps

5,651,320 pps 5,651,320 pps


1,412,830 pps

1,412,830 pps 1,412,830 pps


353,207 pps 353,207 pps 353,207 pps

Maximum no. of IP packets forwarded per system per second (40 byte packets) in single-shelf configuration

82,040,000 pps (14 MR48 linecards)



Maximum no. of IP packets forwarded per system per second (40 byte packets) in multi-shelf configuration

644,600,000 pps (110 MR48 linecards)

644,600,000 pps (110 MR48 linecards)

644,600,000 pps (110 MR48 linecards)





Length of ACL List for 2-ports simultaneous wirespeed performance passing Internet Mix traffic (entries) - GIGE

120 120 120

Length of ACL List for wirespeed performance for all traffic types (e.g. IMIX or 40-byte packets) (entries) - MR48

System Limit

System Limit System Limit

IPv6 Data Plane Performance


Maximum no. of IPv6 packets for one OC-3c/STM-1c ATM port (60 byte packets) – MR48

176,603 pps 176,603 pps 176,603 pps

Maximum no. of IP packets per OC-12c/STM-4c ATM port (60 byte packets) – MR48

706,415 pps 706,415 pps 706,415 pps

Maximum no. of IP packets for OC-48c/STM-16c ATM port (60 byte packets) – MR48

2,825,660 pps 2,825,660 pps 2,825,660 pps

Maximum no. of IP packets for one GigE port (40 byte IP packets, padded to 64 byte Ethernet packet)

1,275,510 pps 1,275,510 pps 1,275,510 pps

Maximum no. of IP packets for one GigE line card (40 byte packet, padded to 64 byte Ethernet packet)

2,551,020 pps 2,551,020 pps 2,551,020 pps

Maximum no. of IP packets forwarded per system per second (60 byte packets) in single-shelf configuration




Maximum no. of IP packets forwarded per system per second (40 byte packets) in multi-shelf configuration

310,822,600 pps (110 MR48 linecards)

310,822,600 pps (110 MR48 linecards)

310,822,600 pps (110 MR48 linecards)




2.6 Reliability, Availability and Serviceability (RAS)

The 7670 RSP is designed to provide high reliability, at least 99.999% availability and high serviceability for use in core backbone networks. To this end, only fully redundant control and switch fabric configurations are supported in this release (non-redundant operation of either is not supported).

2.7 Supported Features Tables

In this section the following definitions are used:

A system feature is a feature provided by the switch to line processing cards. Examples of this are CAC and TCA’s.

A system application is a feature that uses line processing cards and system features to provide its service. Examples of this are CPSS, PNNI and Signaling.

The support for each system feature (table row) for a given card (column) is indicated in the table cell for that feature and card. In each cell, one of the following is displayed:

n/a The system feature is not applicable for the given card.

NO The system feature is not supported on the given card, although it is applicable.

P The system feature is partially supported on the given card. A description of the “partial” support is given in the DFS for the card described by the column.

YES The system feature is fully supported on the given card.

ATM Infrastructure

MR48 Channelized M-Protocol

ESC Edge Services

Card

Quad Gigabit Ethern

et

MR16 ATM

OC48/ STM16 ATM

CAC

YES

YES YES YES YES

FEPD

NO NO NO NO NO

TCA

YES YES NO YES YES

ATM Connectivity Verification

YES NO No YES YES

ATM Alarm Surveillance

YES YES No YES YES

ATM Performance Monitoring

NO NO NO NO NO




ATM Infrastructure


ESC Edge Services

Card

Quad Gigabit Ethern

et

MR16 ATM

OC48/ STM16 ATM

Interval Stats

YES YES YES YES YES

Congestion Statistics and Reporting Alarms

YES YES YES YES YES

SNMP Stats YES YES YES YES YES

Line Timed Synchronization

YES YES (excludi

ng VT15s)

NO YES YES

CPSS Link

YES NO NO YES YES

Test Access Connections

YES NO NO YES YES

Automatic Protection Switching

1+1 per port

1+1 per port

NO 1+1 per port

1+1 per port

EAC

YES YES NO YES YES

VPA Shaping

YES YES NO YES NO

FIA Fault Isolation Assistant

YES NO YES YES YES

MFES Fabric Error Statistics

YES YES YES YES YES

Traffic Management

YES YES YES YES YES

LCR Enhancement

P P NO YES NO

L2 Cache/SER Configuration

n/a n/a n/a n/a n/a

IOC Auto-Reset NO NO NO YES NO

Table 2-1: ATM Infrastructure Supported Features Table




ATM Routing / Signaling


ESC Edge

Services Card

Quad Gigabit

Ethernet

MR16 ATM

OC48/ STM16 ATM

PNNI Link

YES NO NO YES YES

SVC Signaling Link

YES NO NO YES YES

SPVC

YES NO YES YES YES

Trunk Groups

YES NO NO YES YES

ILMI Link

YES NO NO YES NO

SVC Accounting

YES NO NO YES YES

PVC/S-PVC Billing (spooling)

YES NO YES NO

Switched Services VBN

YES NO YES YES YES

Table 2-2: ATM Routing/Signaling Supported Features Table

IP Infrastructure & OAM

MR48 Channelize

d M-Protocol

ESC Edge

Services Card

Quad Gigabit

Ethernet

MR16 ATM

OC48/ STM16 ATM

IP Forwarding

YES NO YES n/a n/a

IP Classification: DSCP

YES NO YES n/a n/a

DSCP Remarking Yes Egress only

NO Yes

n/a n/a

IP Classification: MFC

YES NO YES n/a n/a

IP & MPLS Statistics

YES NO YES n/a n/a

ICMP & IP Options

YES NO YES n/a n/a

PPP over Sonet YES NO NO n/a n/a




IP Infrastructure & OAM

MR48 Channelize

d M-Protocol

ESC Edge

Services Card

Quad Gigabit

Ethernet

MR16 ATM

OC48/ STM16 ATM

PPP over ATM

YES NO NO n/a n/a

IP VPN PE

YES NO YES n/a n/a

RED and WRED

YES NO YES n/a n/a

DHCP relay

YES NO YES n/a n/a

Reverse Path Filtering

YES NO YES n/a n/a

ECMP

YES NO YES n/a n/a

ATM mediation/Pseudowire trunking

NO NO YES n/a n/a

Packet Filtering / ACLs

YES NO YES n/a n/a

Per-IP-flow rate limiting

YES NO YES n/a n/a

Routed Bridged Encapsulation (RBE)

YES NO NO n/a n/a

Interface Group YES NO NO n/a n/a

Ethernet Link Aggregation (802.3ad)

NO NO YES n/a n/a

IPv6 Forwarding YES (ATM

channel with R-PDU)

NO YES NO NO

IPv6 Diffserv YES NO YES NO NO

Table 2-3: IP Infrastructure & OAM Supported Features Table




IP Routing MR48 Channelize

d M-protocol

ESC Edge Services

Card

Quad Gigabit

Ethernet

MR16 ATM

OC48/ STM16 ATM

IP Routing

YES NO YES n/a n/a

MP-BGP4/BGP-4 YES NO YES n/a n/a

MP-BGP4 for 6PE

YES NO YES n/a n/a

OSPF

YES NO YES n/a n/a

IS-IS Routing

YES NO YES n/a n/a

TE Extensions

YES NO YES n/a n/a

RIP YES NO YES n/a n/a

PIM-SM YES NO YES n/a n/a

IGMPv2 YES NO YES n/a n/a

Table 2-4: IP Routing Supported Features Table

MPLS MR48 Channelize

d M-Protocol

ESC Edge

Services Card

Quad Gigabit

Ethernet

MR16 ATM

OC48/ STM16 ATM

RSVP-TE YES NO YES n/a n/a

LDP (DU) YES NO YES n/a n/a

L-LSPs YES NO YES n/a n/a

E-LSPs YES NO YES n/a n/a

Path Protection YES NO YES n/a n/a

CR-LDP/LDP DoD

YES NO NO n/a n/a

6PE (MPLS Core facing)

YES with ATM/R-

PDU

NO YES NO NO

Table 2-5: MPLS Supported Features Table




VPNs MR48 Channelize

d M-Protocol

ESC Edge

Services Card

Quad Gigabit

Ethernet

MR16 ATM

OC48/ STM16 ATM

ATM / MPLS

Network Inter-working

YES NO NO YES YES

Ethernet / ATM

Service Inter-working

YES NO YES YES YES

Ethernet / MPLS

Network Inter-working

YES NO YES n/a n/a

L3 VPN ‘P Router’

YES NO YES n/a n/a

L3 VPN ‘PE-P Router’ (RFC4364)

YES NO YES n/a n/a

L3 VPN ‘PE-CE Router’ (RFC4364)

YES NO YES n/a n/a

L2 VPN – MPLS core

YES NO YES n/a n/a

L2 VPN – ATM core

YES NO NO YES YES

ATM Pseudowire - MPLS core

YES NO YES n/a n/a

Table 2-6: VPN Supported Features Table




3. NEW FEATURES AND FUNCTIONALITY IN RELEASE 9.0

3.1 Any Service Any Port (ASAP) on the ESC

3.1.1 Overview

This feature allows the ESC card to support all existing features available on the ESC in a single software load for mobile solutions.

As various mobile solutions begin using various back haul technologies, more features currently existing on the ESC card will need to operate concurrently. This becomes more prominent as mobile solutions migrate from ATM IMA based back haul to Ethernet and IP based back haul. The transition from ATM IMA to technologies such as pseudo wires (ATM and TDM PWs) and MLPPP requires the ESC card to support such a transition, thereby requiring concurrent operation.

3.1.2 Specifications

The detailed specification of Any Service Any Port on the ESC is as follows:

• The 7670 RSP requires that if a TDM PW is configured on an STS-1, that the entire STS-1 must only be used for TDM-PWs. This implies that no other services are allowed on the same STS-1 as a TDM-PW. The other STS-1's in the same STS-3 may be used for other services.

• On OC12 interfaces, IMA must use DS1s or E1s, and MLPPP bundles must use DS1s, that are all part of the same STS-3.

• IP Header Compression over MLPPP is not supported in Release 9.0 for ASAP on the ESC.

• The ESC card supports either DS1 or E1 based services on the card at once, but not both.

• The 7670 RSP supports the following ESC features in a single software load: - ATM IMA - TDM PWs - MLPPP

• The 7670 RSP supports the following ESC features to be configured and enabled concurrently: - ATM IMA - TDM PWs - MLPPP

• The 7670 RSP supports IMA, TDM PWs and MLPPP using DS1s.

• The 7670 RSP supports IMA using E1s. The 7670 RSP does not support TDM-PWs, MLPPP, or TDM CE/UDT using E1s.

• The 7670 RSP supports a total of 672 DS1s on the ESC for IMA, MLPPP, and TDM PWs.




• The 7670 RSP supports 504 E1s for IMA only.

• The 7670 RSP supports 336 IMA bundles or 336 MLPPP bundles on the ESC for DS1 based services.

• The 7670 RSP supports 252 IMA bundles on the ESC for E1 based services.

• The 7670 RSP supports 1376 TDM PWs per ESC line card.

• The ASAP feature on the 7670 RSP supports up to 24 ESC line cards and 6 peripheral shelves in a multi-shelf configuration.

• The ASAP feature on the 7670 RSP supports up to 16 links per IMA group.

• The ASAP feature on the 7670 RSP continues to support the performance levels provided by releases 8.1 and 7.2.

• The 7670 RSP provides less than 50ms recovery time during an APS switchover for all available services.

• The 7670 RSP provides a less than 250ms recovery time during an LCR switchover for all available services.

• The 7670 RSP supports 100% throughput for IMA and MLPPP based service.

• The 7670 RSP interoperates with IMA on the 7705.

• The 7670 RSP interoperates with MLPPP on the 7705.

• The 7670 RSP interoperates with TDM PWs on the 7705.

• The 7670 RSP supports the endpoint discriminator option negotiation in order to interoperate with the 7705. The 7670 RSP requests class 4 (PPP Magic-Number block) addressing and accepts requests with either class 3 (Globally Assigned MAC Address) or class 4 addresses from the peer.

3.2 MLPPP with Fragmentation

3.2.1 Overview

MLPPP was first introduced in Rel7.2.1 of the 7670 RSP. In that release, MLPPP fragmentation was not supported. Release 9.0 now supports full fragmentation support for MLPPP.

Fragmentation allows operators to interoperate with MLPPP solutions that provide fragmentation capabilities. This is required for more efficiently transporting larger IP packets over MLPPP bundles by fragmenting those packets into smaller chunks and transporting them over MLPPP. The 7670 RSP supports a standard 128 byte fragment size for efficiently transmitting IP packets over MLPPP.





The detailed specification of MLPPP with fragmentation is as follows:

• The 7670 RSP does not support IP header compression with MLPPP fragmentation.

• The 7670 RSP supports MLPPP fragmentation of IP packets as defined in RFC 1990.

• The 7670 RSP supports the current mode of non-fragmented packets as existed prior to this release.

• The 7670 RSP provides a configuration option to enable or disable MLPPP fragmentation on a per MLPPP bundle basis. This option is available via CLI and the 5620.

• When MLPPP fragmentation is enabled the MRU is 1506 bytes and is not configurable.

• When MLPPP fragmentation is enabled the MTU and MRRU are 1500 bytes and is not configurable.

• When MLPPP fragmentation is disabled the MRRU and MTU are 674 bytes, and the MRU is equal to 680 bytes.

• The 7670 RSP round robins MLPPP fragments on all DS1s such that IP packets that are larger than 128 bytes utilize multiple DS1s in parallel to optimally transmit packets across the bundle.

• When MLPPP fragmentation is enabled or disabled, the interface will go down and up. IPCP renegotiates the link as the MRU/MRRU is changed during this action.

• The 7670 RSP supports the same IP requirements for MLPPP without fragmentation as defined in 31RD0048.

• The 7670 RSP supports OSPF over MLPPP.

• By default, MLPPP fragmentation is enabled for newly configured MLPPP bundles.

• When upgrading from Release 7.2.x, MLPPP fragmentation will be disabled by default for those MLPPP bundles that were previously configured on the node prior to the upgrade. All newly configured MLPPP bundles default fragmentation to enabled.

• There is no change to scalability when MLPPP fragmentation is used.

• The 7670 RSP supports MLPPP + fragmentation in a multi-shelf system with 24 ESC cards and 6 Peripheral Shelves.

• The 7670 RSP supports 100% throughput of 40byte packets when MLPPP fragmentation is enabled.




• The 7670 RSP supports 100% throughput of 40byte packets when MLPPP fragmentation is disabled.

• The 7670 RSP supports less than 50ms recovery for APS of either OC3 or OC12 ports when MLPPP fragmentation is enabled.

• The 7670 RSP supports less than 250ms recovery during an ESC LCR switchover when 100% of DS1s are configured with MLPPP fragmentation.

• The 7670 RSP MLPPP fragmentation implementation interoperates with the 7705 product family.

3.3 16 DS1 over MLPPP

3.3.1 Overview

With the growth of 3G services from mobile operators there is a need to increase the amount of bandwidth available per cell site. The need to increase the maximum number of DS1s per MLPPP bundle to 16 is identical to that of 16 DS1s per IMA bundle.


The detailed specification of 16 DS1s over MLPP is as follows:

• The 7670 RSP supports up to 16 DS1s per MLPPP bundle on the ESC card for single and multi-shelf systems.

• 16 DS1s per MLPPP bundle is supported on both OC3 and OC12.

• The 7670 RSP supports non-stop MLPPP services across an LCR pair of ESC cards running 16 DS1 MLPPP.

• The 7670 RSP supports less than 250 ms recovery for LCR switches with 16 DS1 MLPPP bundles.

• The 7670 RSP supports less than 50 ms recovery for APS switches with 16 DS1 MLPPP bundles.

3.4 IP Interfaces on the ESC

3.4.1 Overview

IP Interfaces on the ESC allows mobile solutions with IP based OAM traffic to use the IP routing capabilities of the 7670 RSP to forward IP traffic to and from the ESC. IP Interfaces can be configured on ATM VCs within IMA bundles to allow IP packets to be transported over ATM IMA.


The detailed specification of IP Interfaces on the ESC is as follows:




• IP interfaces on the ESC supports IPv4.

• The ESC supports IP interfaces on an ATM VC. Bridged and routed PDUs (B-PDU & R-PDU), LLC / SNAP and VC mux encaps are supported.

• The ESC supports up to 3 IP interfaces per IMA bundle.

• The ESC supports IP static routing over an IP interface.

• The ESC supports DHCP relay agent over an IP interface.

• The 7670 RSP supports adding an IP interface on the ESC to a VRF.

• The 7670 RSP supports IP ping and traceroute over an IP interface on the ESC.

• The 7670 RSP provides support for 5620 management of IP interfaces on the ESC.

• ATM VCs used by IP interfaces support all currently supported ATM OAM capabilities.

• The ESC supports the same MTU values as IP interfaces configured over ATM VCs on the MR48 linecard.

• The 7670 RSP does not support IP options header processing for IP interfaces configured on the ESC.

• The 7670 RSP provides a "CoS unaware" traffic management model for IP interfaces configured on the ESC over IMA bundles.

• On egress (for IP interfaces configured on an ATM VC in an IMA bundle), there is no per CoS treatment for any IP traffic traversing the interface. The IP traffic is treated using the ATM service category associated with the VC where the IP interface is configured. This implies that the traffic over the IP interface VC is scheduled and prioritized amongst all the other ATM VCs on the IMA bundle, depending on the service categories of all VCs.

• On egress over the IMA bundle all IP packets, regardless of CoS, are queued first in first out over the IP interface.

• On ingress, IP packets are forwarded onto the fabric as is. The CoS associated with the default classification and DSCP markings of ingress packets is used to forward packets onto the fabric.

• The 7670 RSP ensures that if a "Time Delay" buffer queue is configured on a VC in an IMA bundle, that the queue size is guaranteed to be at least large enough to fit one packet based on the configure MTU of the interface.

• For IP interfaces configured on the ESC, the 7670 RSP does not support per CoS egress congestion interfaces stats, and instead shall only support the "all Cos" egress congestion interface stats option.

• For IP interfaces configured on the ESC, the 7670 RSP supports only non CoS-aware IP stats, on INGRESS and EGRESS.




3.5 Test Access Connections (TAC) on ESC

3.5.1 Overview

Test Access Connections (TACs) are used by network operators to perform maintenance on existing connections in a network (PVCs, SVCs, S-PVCs). A TAC may be used to verify the performance of a data path, or to isolate a fault along a data path. The purpose of this feature is to provide TAC support for ATM endpoints on the ESC linecard.


The detailed specification of Test Access Connections (TAC) on ESC is as follows:

• A monitor TAC on the ESC directs data traffic from the ingress of the target endpoint to the test endpoint without disrupting the target connection cell stream for a maximum of 10 msec.

• TAC is capable of being applied to any of the following targets: PVC & S-PVC (source & destination endpoints).

• TAC is not applicable to resource connections.

• TAC supports the following service categories: CBR, VBR, & UBR.

• TAC is not supported on ABR connections.

• TAC is not configurable on a port that is also being used by test endpoint connections.

• The TAC associated with each direction of a monitored connection takes on the traffic attributes of the connection in that direction.

• When a TAC is programmed on an existing connection, the 7670 RSP checks that resources are available to support the new cell stream. If resources are not available, then the TAC is rejected. Capacity checking for the TAC is performed against the test access port, but not against the ingress and egress ports of the original P2P connection. A TAC also passes CAC requirements before it is admitted to the system.

• TAC is configurable via either CLI or the 5620.

• When the original connection is removed, the corresponding TAC is removed.

• The CLI menu to configure and display TAC endpoint statistics is identical to that of PVC endpoint statistics. The Creator field displays a TAC endpoint type when applicable to distinguish it from a regular PVC connection.

• 100 TAC endpoints are supported per system.

• When a control activity switch occurs, TACs are unaffected and remain configured.




• TACs remain configured when an activity switch takes place between the active and redundant ESC.




4. NEW FEATURES AND FUNCTIONALITY IN RELEASE 9.1

4.1 Pseudo Wire Redundancy

4.1.1 Overview

The Pseudo-Wire Redundancy feature allows the 7670 RSP to offer Primary and Standby PW service. The intent of this feature is to interoperate with the 7750's PW Redundancy feature at customer locations that require both a 7670 RSP and 7750 SR. Although only ATM PWs are supported by this feature, the basic functional behavior of the PW Redundancy feature is developed in general accordance with draft-ietf-pwe3-redundancy-00.txt, draft-ietf-pwe3-redundancy-bit-00.txt, and similar functionality supported by the 7750 SR.

The 7750 SR notifies the 7670 RSP of a PW failure by either withdrawing the Primary PW label it advertised, or by sending a PW status notification with the code set to indicate there is a defect on the PW. Once the 7670 RSP receives this notification it will immediately switch local traffic to forward over the Standby PW. In order to avoid black-holing in-flight packets during path switching, the 7670 RSP will accept packets received from either the Primary or Standby PW while transmitting over the Standby PW.

When the Primary PW is restored, the 7750 SR will update the status of the PW by sending a new label mapping message for the same PW FEC, or by sending a PW status notification message indicating that the PW is back up. The 7670 RSP then starts a timer and reverts back to the Primary PW upon expiry of the timer. By default, the timer is set to 0, which means the 7670 RSP reverts immediately. If the timer is set to infinity, the 7670 RSP never reverts back to the Primary PW.

The behavior of the PW Redundancy feature is the same if the 7670 RSP detects, or is notified of, a network failure that brings the tunnel/PW status to Down.





The detailed specification of Pseudo Wire Redundancy is as follows:

• The PW Redundancy feature is supported by the MR16 line card for ATM ACs, and by the GigE linecard for MPLS tunnels.

• The 7670 RSP supports PW Redundancy for ATM (VC, VP & VPA) cell mode only.

• The 7670 RSP supports the T-PE functionality associated with PW Redundancy.

• The 7670 RSP supports the ability to configure two PWs per AC.

• For each PW the following are configurable via CLI and the 5620: 1) PW ID, 2) Remote Router ID, 3) Remote Group ID.

• Each PW supports an associated precedence status flag whose value shall be either: 1) Primary, or 2) Standby. The Primary setting indicates which PW is to be the primary PW from an operations point of view.

• The precedence status flag is configurable via CLI and the 5620.

• For an AC with two configured PWs: 1. changing the precedence status flag from Primary to Standby on one PW automatically causes the precedence status flag of the other PW to change from Standby to Primary; 2. changing the precedence status flag of a PW from Standby to Primary automatically causes the precedence status flag of the other PW to change from Primary to Standby. Changing a PW's precedence flag to Primary shall cause the PW to come into operational use as the primary PW if it is up and available, in accordance with the rules governing reversion.

• The 7670 RSP allows each PW to establish independently by issuing one "connect" command per PW. The 7670 RSP uses the first PW established to pass traffic. The 7670 RSP uses the precedence flag setting, along with the Revertive Mode settings, in selecting which PW will be chosen for forwarding.

• Both primary and standby PWs inherit the same traffic parameters.

• Connection Admission Control (CAC) can be applied to both PWs.




• The 7670 RSP switches from the Primary PW to the Standby PW (or vice versa in the case where the Standby PW is active) for the following scenarios: 1) The T-LDP peer (remote PE) node withdraws the PW label 2) The T-LDP peer signals a FEC status indicating a PW failure. The signaled status that cause a switch include "Local PSN-facing PW Fault", "PW Not forwarding", "Local Attachment circuit Fault", or "PW Forwarding Standby" in this order of priority. 3) The T-LDP session to the peer node times out 4) All tunnels containing the active PW go down.

• The 7670 RSP supports the ability to receive packets from either the Primary PW or Standby PW.

• The 7670 RSP supports the ability to signal to the remote peer which PW is "PW Forwarding" using PW Status Signaling similar to the 7750 SR. See the PW status signaling feature for more details.

• The 7670 RSP records the date and time of the last PW switchover and displays this via CLI.

• The 7670 RSP shall include the status of both the Primary and Secondary PW in an SNMP trap.

• The 7670 RSP provides the ability to configure a Reversion Timer by CLI or the 5620.

• The 7670 RSP provides one Reversion Timer per PW attachment circuit.

• The configurable range of values for the Reversion Timer is 0 to 600 seconds in 1 second steps, or infinity. The default value is 0 seconds.

• If the Reversion Timer is set to 0, then the 7670 RSP immediately switches back to the Primary PW from the Standby PW if the Primary PW re-establishes.

• If the Reversion Timer is set to a value between 1 and 600, then, after a delay equal to the configured number of seconds, the 7670 RSP switches back to the Primary PW from the Standby PW if the Primary PW re-establishes. The reversion timer is cancelled on any local or remote status changes to either the Primary or Standby PW, and normal switching resumes.

• If the Reversion Timer is set to infinity, then the 7670 RSP never switches back to the Primary PW from the Standby PW if the Primary PW re-establishes until any local or remote status changes to the Standby PW occur.

• If reversion to the Primary PW occurs, then the status "PW Forwarding" is signaled for the Primary PW.

• The 7670 RSP supports the ability to manually force a switchover from the Primary PW to the Standby PW or vice-versa using either CLI or the 5620. When this command is executed, the PW switches and all configured revertive behaviors do not apply. The operation has to be disabled for normal switching to resume based on the operational status.




• The total number of configurable Primary and Standby PWs shall be 10,000.

• In the event of a traffic switch-over from Primary to Standby PWs, full PW traffic is restored on the Standby PWs within a time interval that does no exceed 1.5 seconds for 1,000 pairs of Primary and Standby PWs.

• The PW Redundancy feature on the 7670 RSP interoperates with the PW Redundancy feature on the 7750 SR as an S-PE.

4.2 Pseudo Wire Status Signaling

4.2.1 Overview

Pseudo-wire Status Signaling provides the ability to signal status about a particular pseudo-wire (PW) over T-LDP. The status message is used for ensuring proper OAM/AIS functions for ATM pseudo-wires, and for providing protocol procedures for the PW Redundancy feature.

The basic functional behavior of the PW Status Signaling feature is developed to be in general accordance with draft-ietf-pwe3-redundancy-bit-00.txt, RFC4447, and similar functionality supported by the 7750.


The detailed specification of Pseudo Wire Status Signaling is as follows:

• The 7670 RSP supports the ability to signal the status of PWs over T-LDP to remote PEs as defined in RFC 4447, Section 5.4.

• PW Status Signaling applies to cell mode PWs (including N:1 cell mode).

• The 7670 RSP supports the following status as defined in RFC 4446, Section 3.5: 0x00000000 - PW Forwarding (clear all failures) 0x00000001 - PW Not Forwarding 0x00000002 - Local Attachment Circuit (ingress) Rx Fault 0x00000004 - Local Attachment Circuit (egress) Tx Fault 0x00000008 - Local PSN-facing PW (ingress) Rx Fault 0x00000010 - Local PSN-facing PW (egress) Tx Fault

• The 7670 RSP signals to the remote PE the status "PW Forwarding" for the Primary PW that is up.

• The 7670 RSP signals to the remote PE the status 0x00000018 "Local PSN-Facing PW Fault" for any PW that is not operationally up due to the PW not being able to find a PSN tunnel to forward traffic over.




• If the Attachment Circuit enters AIS or RDI failure states for an ATM PW, and the PW type is a cell mode PW, then the AIS or RDI is passed through and transmitted over the PW as is. If ATM OAM Alarm Surveillance has been enabled for the Attachment Circuit, a PW Status of "Local Attachment Circuit" (0x6) is sent.

• If the Attachment Circuit fails due to a higher layer failure (VP, Port, Line Card, or Fabric), AIS is generated and transmitted over the PW. If ATM OAM Alarm Surveillance has been enabled for the Attachment Circuit, a PW Status of "Local Attachment Circuit" (0x6) is sent.

• If the 7670 RSP receives a signaled status message from the remote PE with any bits set and there is an available alternate backup pseudo wire (see PW Redundancy feature), then it switches to that PW as the forwarding PW.

• If the OAM Continuity Check is enabled on the Attachment Circuit (AC) endpoint, then any local (non-AC fault) or remote failures generate AIS out of the AC.

• The 7670 RSP displays the last received PW status from the remote PE for both the Primary and Standby PWs in CLI. These values are also retrievable via the 5620.

• The 7670 RSP shall display the last transmitted PW status sent to the remote PE for both the Primary and Standby PWs in CLI. These values are also retrievable via the 5620.

• PW Status Signaling is able to run on up to 10,000 PWs.

• The PW Status Signaling feature on the 7670 RSP interoperates with the PW Redundancy feature on the 7750 SR as an S-PE.

4.3 LCR Enhancement

4.3.1 Overview

This is a modification of the LCR feature designed to protect the system from any device failure on the inactive line card that results in a connection creation error. If the inactive line card propagates a connect error while the active line does not, the connection status on the control card will be okay, but the PG status will be “DOWN”. The appropriate alarms are raised and the inactive line card receives demerits to prevent it from becoming active.


The detailed specification of LCR Enhancement is as follows:




• When the active line card receives a connect message, it processes that message as before, then forwards it to the inactive line card, if the inactive line card is present and ready to handle messages. The inactive line card processes the connect message and sends a reply message to the active line card, as before. Once the active line card receives the response, it processes it in the following manner:

o If both active and inactive cards succeeded to program the connections an Ok status is returned.

o If the active card failed the connection an ERROR status will be returned.

o If the inactive card failed the connections:

� An error status will be returned a maximum of 5 times and after that it will return Ok status.

� Also a "connections out of sync" status message is sent which will take the line cards Protection Group down with a status "Conn Not Synchronized".

� A "Protection Lost" alarm will be raised.

� Note: the PG Down status will prevent a user from performing a "User Switch" command, but it will not prevent the inactive line card from becoming active with the use of a "Force Active" command or an active line card reset.

� Note: if the inactive line card takes activity with "connections out of sync" Protection Group status, some connections that previously failed to be programmed will be missing on the newly active.

• This modification has been fully implemented on the MR16 and MR8 platforms.

• This modification has been partially implemented on the MR48 and ESC platforms to prevent potential silent failures – if the active line card fails the connection an ERROR status is returned regardless of the connection status on the inactive line card.




4.4 L2 Cache/SER Configuration

4.4.1 Overview

The L2Cache memory located on the CC2G’s HKII (House Keeper Module Version 2) processor modules is not protected with ECC (Error Correcting Code). As a result, the L2Cache memory can experience parity errors that might cause unexpected card resets, if no other protection is used. In order to reduce the number of parity error-related control card resets, a mechanism called L2 Cache SER (Soft Error Recovery) was implemented for the HKII modules in release 4.0.2.2. An infrequent side effect of the SER software in combination with the L2Cache device operating in the write-back mode (default) is that some of the bit errors can propagate into the main memory and cause negative impact on the CC2G functioning.


The detailed specification of L2 Cache/SER Configuration is as follows:

• As part of the new functionality, a user now has an ability to completely disable the L2 Cache SER mechanism via CLI. Note that when the SER is disabled, any bit error in the L2Cache memory will cause a control card reset.

• Alternatively, the new feature provides a user with a CLI command to switch the HKII modules’ processor L2Cache to use write-through mode. With the write-through mode active, SER can provide very high level of protection against L2Cache parity errors with no possibility for the bit errors to be propagated into the main memory. Note that activating the write-through mode reduces the HKII module processor’s performance by 5 to 10%.

• The L2Cache mode and SER enable/disable configuration parameters are stored in the database, and therefore, they will survive control card resets and can be saved and restored by the database backup/restore procedure.

4.5 IOC Auto-Reset

4.5.1 Overview

The IOC Auto-Reset feature provides an ability to automatically reset an IO card (IOC) when a diagnostics test failure is detected on that IOC. The purpose of the IOC auto-reset feature is to attempt an automatic recovery in case of an IOC intermittent hardware failure detected by background diagnostics. The IOC auto-reset achieves two goals:

- All APS-protected active ports are forced away from a faulty IOC; - IOC reset may help the IOC to recover from an intermittent hardware failure.


The detailed specification of IOC Auto-Reset is as follows:




• The IOC auto-reset feature relies on the existing mechanism where a line card continuously runs a set of background diagnostics tests to monitor the health of its hardware. An IOC auto-reset can be triggered by a failure of one of the background diagnostics deemed capable of causing a user traffic impact.

• An IOC is reset by the control card immediately upon receiving a diagnostics test failure report. The only condition applied is that the IOC will not be reset, if it is still going through initialization or was not recognized by the system for whatever reason. Besides checking the IOC status, no LCR/APS configuration check and no check for the PG status on each port of the impacted IOC are made. The impact of resetting an IOC is considered quite low; the IOC recovers from a reset within 2 seconds.

• Note that a diagnostics error is processed in the usual way – a diagnostics alarm is raised in the diagnostics alarm queue. In parallel, a major alarm “IOC Auto-Reset” will be raised, when an IOC auto-reset is initiated. After the IOC reset, an existing major alarm “Card Hard Reset” will be raised as well.

• To prevent continuous IOC resets in the case of a hard failure, the number of consecutive IOC auto-resets will be limited to 3. Once this threshold number is reached, the RSP will stop resetting that IOC, even if the IOC is still experiencing a diagnostics failure. A manual IOC reset or an IOC removal will bring the counter value back to 0. Also, resetting a line card in a non-LCR configuration or both line cards in an LCR pair would clear the IOC Auto-Reset counters on IOCs in that slot.

• A new line is added to the “maint slot <IOC>” menu display for the MR16 IO cards. It indicates whether IOC auto-reset is active or not and shows how many auto-resets have been performed on this IO card. Once the maximum number of resets is reached, the number of auto-resets will be shown as “Max”.

Alcatel[RW]> maint slot 1-3-1 Object Card Ser. No. Mktg. Part No. Eng. Part No. OC12_IR2 03010109880 90-7570-02-00-B 87-2254-06-03 Card Status : Port_OOS IOC Firmware : 80-6221-01-04 IOC Auto-Reset : On (2)

• The IOC auto-reset feature can be enabled or disabled at the system level by the “system diagnostics ioc-auto-reset status” CLI command. By default, IOC auto-reset is disabled. Note that at least one trigger must be enabled, when enabling IOC auto-reset.

• Enabling the IOC auto-reset feature does not have a retroactive effect – if the IOC auto-reset gets enabled, any IOC with pre-existing diagnostic failure will not be reset. Only subsequent diagnostics failures will cause an IOC auto-reset.

• This feature is only applicable to the MR16 line cards and not available for the Gige line card.




• Main diagnostics tests, failure of which may cause a negative impact on a user data traffic, are used by the IOC Auto-Reset feature. Note that all diagnostics failures are treated with the same priority to trigger the IOC auto-reset feature. This means that a failure of any one of the diagnostics used by the IOC Auto-Reset feature can cause an IOC reset.

• The following diagnostics tests are included as triggers for an IOC automatic reset:

o Loss Of Clock Detection – this is a line card diagnostics test that monitors the quality of the clock source for different devices on a line card, as well as on the IO cards. If a clock source fails on an IO card, this test identifies the particular IO card that experienced a clock failure. Clock failure on an IOC can have a negative impact on either data or control path, which may cause a user traffic impact. Note that if a clock source fails on a line card device, there will be no IOC auto-reset.

o IOC Scratch Pad Test – this is an IO card diagnostics test that monitors the health of the IOC control path. When this test fails it indicates that the line card is unable to communicate to the IOC, which may cause APS protection to stop working properly on this IOC. This problem may be caused by an IOC clock failure.

o IOC DCHK Error Monitor – this is an IO card diagnostics test that detects D-Check errors on the IOC data path. This test error may be caused by an IOC clock failure.

o IOC Parity Error Monitor – this is an IO card diagnostics test that detects parity errors on the IOC data path. This test error may be caused by an IOC clock failure.

• Each IOC auto-reset trigger can be enabled or disabled independently at the system level by the “system diagnostics ioc-auto-reset trigger” CLI command. When all triggers are disabled, the IOC auto-reset feature status will be automatically set to DISABLED. The feature then will have to be explicitly re-enabled to become active. At least one trigger must be enabled, when enabling IOC auto-reset.

• By default, all of the above listed triggers are enabled. IOC auto-reset triggers configuration remains unchanged, when the IOC auto-reset feature is enabled or disabled.

• Just like enabling the IOC auto-reset feature, enabling any of the IOC auto-reset triggers doesn’t have a retroactive effect. Enabling of an IOC auto-reset trigger does not cause an immediate IOC auto-reset, even if there is an outstanding diagnostics failure of that type on any of the IO cards. Only subsequent diagnostics failures will cause an auto-reset.







5. PRODUCT COMPLIANCE

5.1 Standards That This Release Meets

7670 RSP R9.x meets the standards listed in the tables below.

5.1.1 IP Standards

Standard Description

Routing Protocol

BGP4 RFC1657 BGP4 MIB RFC1771 BGP4 Protocol RFC1772 Application of BGP4 in the Internet RFC1745 BGP-OSPF Interaction RFC1965 BGP Confederation RFC1997 BGP Communities Attribute RFC1998 BGP Community Attribute in Multi-home Routing RFC2385 TCP MD5 Signature Option for BGP Sessions RFC2439 BGP Route Flap Damping RFC2519 Framework for Inter-domain Route Aggregation RFC2796 (obsoletes RFC1966) BGP Route Reflection RFC2842 Capabilities Advertisement with BGP4 RFC2858 Multiprotocol Extensions for BGP4 RFC2918 BGP4 Route Refresh RFC3107 Carrying Label Information in BGP4 RFC4360 BGP Extended Communities Attribute RFC4724 BGP4 Graceful Restart (helper function only)

OSPF RFC1587 OSPF NSSA Option RFC1765 OSPF Database Overflow Handling RFC1850 OSPF MIB RFC2328 OSPFv2 Protocol RFC2370 Opaque LSA Option RFC3037 OSPF Stub Router Advertisement RFC3623 OSPF Graceful Restart RFC3630 TE Extension to OSPF

IS-IS ISO/IEC 10589 IS to IS Interdomain Routing RFC1142 IS-IS Intradomain Routing Protocol RFC1195 Use of IS-IS for Routing in TCP/IP environment RFC2104 HMCA: Keyed-Hashing for Message Authentication RFC2763 Dynamic Hostname Exchange Mechanism for IS-IS RFC3277 IS-IS Transient Blackhole Avoidance Mechanism RFC3567 IS-IS Cryptographic Authentication RFC3784 IS-IS Extension for Traffic Engineering

RIP

RFC1722 RIP Version 2 Protocol Applicability Statement

RFC2082 RIP-2 MD5 Authentication




RFC2543 RIP Version 2

RFC1058 RIP Version 1

IP Multicast

RFC2236 Internet Group Management Protocol, Version 2

RFC2362 PIM-SM

RFC4601 Protocol Independent Multicast – Sparse Mode (PIM-SM): Protocol Specification (Revised) Including PIM-SSM

RFC4607 PIM-SSM Architecture

SNMP RFC1155 Structure and Identification of Management Information

for TCP/IP-based Internets RFC1157 A Simple Network Management Protocol RFC1212 Concise MIB Definitions RFC1215 A Convention for Defining Traps for use with the SNMP RFC1907 MIB for SNMPv2 RFC2570 Introduction to Version 3 of the Internet-standard

Network Management Framework RFC2571 Management Framework RFC2572 Message Processing and Dispatching for SNMP RFC2573 SNMP Applications RFC2574 User-based Security Model for SNMPv3 RFC2575 View-based Access Control Model for SNMP RFC2576 Co-existence between SNMP v1, v2 and v3 RFC2578 (obsoletes RFC1902 and 1442) Structure of Management Information for version 2

(SMIv2) RFC2579 (obsoletes RFC 1903 and 1443) Textual Conventions for SMIv2 RFC2580 (obsoletes 1904 and 1444) Conformance Statement for SMIv2 RFC2863 (obsoletes RFC2233 and 1573) The Interface Group MIB RFC3416 (obsoletes RFC1905 and 1448) Version 2 of the Protocol Operations for the SNMP RFC3417 (obsoletes RFC1906 and 1449) Transport Mappings for SNMP RFC3418 (obsolete RFC1907and 1450) MIB for SNMP

IP General RFC768 UDP RFC791 Internet Protocol RFC792 ICMP RFC793 TCP RFC951 BOOTP (relay agent only) RFC1122 Internet Hosts Requirement RFC1305 NTP RFC1483 Multiprotocol Encapsulation over ATM RFC1518 CIDR Architecture RFC1519 CIDR RFC1812 IP Routers Requirement RFC1858 IP Fragments Filtering RFC2011 IP SNMPv2 MIB RFC2096 IP Forwarding Table and Static Route MIB RFC2113 IP Router Alert Option RFC2131 (DHCP Relay Agent only) DHCP




RFC2233 The I/F Group MIB using SMIv2 RFC2644 Changing the default for Directed Broadcasts in Routers RFC2684 Multiprotocol Encapsulation over ATM (obsoletes 1483) RFC2827 Network Ingress Filtering: Defeating DoS Attacks which

employ IP source address spoofing RFC3021 Using 31-Bit Prefixes on P2P links RFC3128 Protection Against a Variant of the Tiny Fragment Attack RFC3046 DHCP Relay Agent Information Option RFC3527 Link Selection sub-option for the Relay Agent

Information Option for DHCPv4

Diffserv RFC2472 Definition of DS Field in IPv4 and IPv6 Header RFC2474 Definition of DS Field RFC2475 Diffserv Architecture RFC2597 Assured Forwarding PHB RFC2697 Single-rate Three-color Policing RFC3246 Expedited Forwarding PHB IPv6 General RFC2460 IPv6 Specification RFC2463 ICMPv6 RFC2464 IPv6 over Ethernet RFC2492 IPv6 over ATM RFC2710 MLDv1 RFC3513 IPv6 Address Architecture RFC3587 IPv6 Global Unicast Address Format RFC3484 IPv6 Default Address Selection RFC4007 IPv6 Address Scoping RFC4443 ICMPv6 RFC4861 Neighbor Discovery RFC4294 IPv6 Node Requirement RFC4291 IPv6 Address Architecture RFC4862 Stateless Address Autoconfiguration RFC4293 (for IPv6 address table section) MIB for IP

IPv6 Tunneling Mechanism

RFC4798 6PE

RFC4659 6VPE

MPLS RFC 2205 RSVP - Version 1, Functional Specification RFC 3031 MPLS Architecture RFC 3032 MPLS Label Stack Encoding RFC 3035 MPLS using LDP and ATM Switching RFC 3036 LDP Specification RFC 3209 RSVP Extensions for LSP Tunnel RFC3212 Constraint-Based LSP Setup using LDP RFC 3215 LDP State Machines RFC3270 MPLS Support of Differentiated Services RFC3443 Time To Live (TTL) Processing in MPLS Networks RFC3478 Graceful Restart Mechanism for Label Distribution

Protocol RFC4090 Fast Reroute - Extensions to RSVP-TE for LSP Tunnels RFC3813 MPLS Label Switching Routing (LSR) MIB




RFC3812 MPLS Traffic Engineering MIB

PPP RFC1332 IPCP RFC1377 OSINLCP RFC1661 PPP RFC1662 PPP in HDLC-like framing RFC1994 CHAP RFC2165 PPP over SDH/SONET

Ethernet IEEE 802.3-2000 CSMA/CD Access Method and Physical Layer Spec IEEE 802.1Q-1998 Virtual Local Area Networks (VLANs) IEEE 802.1P-1998 Ethernet Traffic Class IEEE 802.3 ad Ethernet Link Aggregation RFC826 An Ethernet Address Resolution Protocol RFC894 A Standard for the Transmission of IP Datagrams over

Ethernet Networks RFC2665 (statistics collection only) Managed Objects for Ethernet-like Interface types

MPLS-based L2 VPN RFC4448 Encapsulation Methods for Transport of Ethernet Frames

Over IP and MPLS Networks RFC4717 Encapsulation Methods for Transport of ATM

cells/frames Over IP and MPLS Networks RFC4447 Pseudowire Setup and Maintenance using LDP RFC4446 IANA Allocations for pseudo Wire Edge to Edge

Emulation draft-ietf-pwe3-pw-mib-03.txt IETF PWE3 MIB for Pseudo-Wires RFC4762 (as PE-r only) Virtual Private LAN Services over MPLS ATMF af-aic-00178.001 (Version 2) ATM-MPLS Network Interworking Ltd-cs-atmmpls-01.00 Signaling and Routing Support of ATM-MPLS Network

Interworking ITU-T Y.1711 MPLS OAM Y.1411 ATM over MPLS Cell Encapsulation Y.1412 ATM over MPLS Frame Encapsulation

BGP4/MPLS IP VPN RFC4364 MPLS/BGP4 VPN (a.k.a. 2547bis) draft-rosen-vpns-ospf-bgp-mpls-05.txt OSPF as the PE/CE Protocol in BGP/MPLS VPNs draft-rosen-ppvpn-ospf2547-area0-01.txt OSPF Area 0 PE/CE Links in BGP/MPLS VPNs RFC4576 Using an LSA Options Bit to Prevent Looping in

BGP/MPLS IP VPN

7670 RSP System RFC854 Telnet RFC2865 RADIUS (for user authentication only) RFC2866 RADIUS accounting RFC3164 The BSD Syslog Protocol

Table 5-1: Release 9.x IP/MPLS Compliance listing

5.1.2 ATM Standards

Standard Description




User-Network Interface (UNI)

af-uni-0010.001 ATM User-Network Interface Specification V3.0

af-uni-0010.002 ATM User-Network Interface Specification V3.1

Traffic Management

af-uni-0010.002 Traffic Management 3.1

af-tm-0056.100 Traffic Management 4.0

af-tm-0121.000 Traffic Management 4.1

Signaling

af-uni-0010.002 UNI Signaling 3.1

af-sig-0061.000 UNI Signaling 4.0

af-sig-0076.100 Signaling ABR Addendum

ILMI (Integrated local mgmt interface)

af-ilmi-0065.000 ILMI 4.0

Control Signaling

af-cs-0107.000 Addressing Addendum for UNI Signaling 4.0

af-cs-0115.000 PNNI Transported Address Stack, Version 1.0

af-cs-0125.000 ATM Inter-Network Interface (AINI) Specification

af-cs-0126.100 PNNI Addendum for Generic Application Transport Version 1.0

af-cs-0127.000 PNNI SPVC Addendum Version 1.0

af-cs-0141.000 PNNI Addendum for Path and Connection Trace, Version 1.0

af-cs-0148.000 Modification of Traffic Descriptor for an Active Connection, Addendum to UNI 4.0

af-cs-0173.000 Domain-based rerouting for active point-to-point calls

Af-cs-0195.000 Policy Routing (also commonly known as Policy-based Routing PBR)

B-ICI (with the exception of B-ISUP)

af-bici-0013.000 B-ICI 1.0

af-bici-0013.001 B-ICI 1.1

af-bici-0013.002 B-ICI 2.0 (delta spec to B-ICI 1.1)

af-bici-0013.003 B-ICI 2.0 (integrated specification)

af-bici-0068.000 B-ICI 2.0 Addendum or 2.1

Routing and Addressing

af-ra-0105.000 ATM Forum Addressing: User Guide Version 1.0

af-ra-0106.100 ATM Forum Addressing: Reference Guide




P-NNI

af-pnni-0026.100 Interim Inter-Switch Signaling Protocol

af-pnni-0055.000 P-NNI V1.0

af-pnni-0075.000 PNNI ABR Addendum

af-pnni-0081.000 PNNI v1.0 Errata and PICs

Physical Layer

af-uni-0010.002 155.52 Mbps SONET STS-3c Physical Layer 155.52 Mbps Physical Layer

af-phy-0046.100 622.08 Mbps Physical Layer

af-phy-0128.000 622 and 2488 Mbit/s Cell-Based

Table 5-2: Release 9.x ATM Compliance listing

5.1.3 Product Integrity and Type Approval Standards:

Release 9.x of 7670 RSP with the appropriate revision of hardware meets the standards listed in the table below.

Unless otherwise indicated, the compliance applies to the system as a whole.

North & South America Europe, Middle-East, Africa Asia, Pacific

Product Safety Approvals UL/CSA 60950-1-03 1st Ed. FDA CDRH 21-CFR 1040 Apr 1996

CENELEC EN 60950-1 1st Ed. IEC 60825-1 Ed 1.2 IEC 60825-2 Ed 2.0

IEC 60950-1 Ed 1.0 IEC 60825-1 Ed 1.2 IEC 60825-2 Ed 2.0

EMC Approvals Telcordia GR-1089-CORE Issue 2 ICES-003 Issue 3 (Class A) FCC Part 15, 2002 (Class A)

EN 300 386 v1.3.2 (Class B)

Network Attachment Approvals N/A N/A N/A

Customer-Specific Environmental Requirements Telcordia GR-63-CORE Issue 2 Telcordia GR-78-CORE Issue 1 Telcordia GR-1089-CORE Issue 2 Telcordia SR-3580 Issue 1 Verizon SIT.NEBS.TE.NPI.2000.010 SBC TP76200MP May 2002

ETSI EN 300 019-2-1 v2.1.2 (Class 1.2) ETSI EN 300 019-2-2 v2.1.2 (Class 2.3) ETSI EN 300 019-2-3 v2.1.2 (Class 3.2) ETSI 300 132-2 v2.1.1

Customer- Specific Telecom Interoperability Requirements Telcordia GR-253-CORE Issue 3 (Section 4: Physical Layer) Telcordia GR-253-CORE Issue 3 (Section 5.4 and 5.6: Network Synchronization and Jitter; ambient temperature only) ITU-T G.703 Nov 2001 (Physical Electrical Interfaces requirements) ITU-T G.707/Y.1322 Sept 2002 (SDH mapping and overhead requirements) ITU-T G.813 March 2003 (Network Synchronization Option 1(E rate) only) ITU-T G.825 Aug 2001 (SDH Jitter/Wander) ITU-T G.957 Jul 1999 (IR/LR/XLR interfaces only) ANSI T1.102-1993 ( STM1e requirements only) ANSI T1.105.06-1996 (SONET Interface for MMF/SR-0 requirements only)

Table 5-3:7670 RSP Release 9.x Type Approval Compliance Summary







REFERENCES

[1] 31RD0046, Release Description for 7670 RSP Release 6.3.

[2] 31RD0048, Release Description for 7670 RSP Release 7.x.

[3] 31RD0049, Release Description for 7670 RSP Release 8.x.




HISTORY

Version Date Person Reason

1.0 2009.11.03 C. Rajsic Created for Rel9.0

2.0 2010.01.07 C. Rajsic Minor update to limits table

3.0 2010.05.10 C. Rajsic Added Rel9.1 content

4.0 2014.09.02 P. Byrne Added further 9.1 content

4.1 2014.09.16 P. Byrne Applied corrections

- END OF DOCUMENT -

Documents

Release Description for 7670 RSP Release 9 - Nokia … Synchronous Digital Hierarchy ... 3.1.2 Specifications ... This document contains Confidential Information of Alcatel-Lucent