alcatel lucent 7670 routing switch platform general information release 7.1

Alcatel-Lucent 7670ROUTING SWITCH PLATFORM | RELEASE 7.1G E N E R A L I N F O R M A T I O N

PRINTED ONRECYCLED PAPER

Alcatel-Lucent assumes no responsibility for the accuracy of the information presented, which is subject to change without notice.

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of Alcatel-Lucent. All other trademarks are the property of their respective owners.

Copyright 2007 Alcatel-Lucent.All rights reserved.

Disclaimers

Alcatel-Lucent products are intended for commercial uses. Without the appropriate network design engineering, they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control, direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal injury, or severe physical or environmental damage. The customer hereby agrees that the use, sale, license or other distribution of the products for any such application without the prior written consent of Alcatel-Lucent, shall be at the customer's sole risk. The customer hereby agrees to defend and hold Alcatel-Lucent harmless from any claims for loss, cost, damage, expense or liability that may arise out of or in connection with the use, sale, license or other distribution of the products in such applications.

This document may contain information regarding the use and installation of non-Alcatel-Lucent products. Please note that this information is provided as a courtesy to assist you. While Alcatel-Lucent tries to ensure that this information accurately reflects information provided by the supplier, please refer to the materials provided with any non-Alcatel-Lucent product and contact the supplier for confirmation. Alcatel-Lucent assumes no responsibility or liability for incorrect or incomplete information provided about non-Alcatel-Lucent products.

However, this does not constitute a representation or warranty. The warranties provided for Alcatel-Lucent products, if any, are set forth in contractual documentation entered into by Alcatel-Lucent and its customers.

This document was originally written in English. If there is any conflict or inconsistency between the English version and any other version of a document, the English version shall prevail.

iii

Preface

Alcatel-Lucent provides end-to-end communications solutions, enabling carriers, service providers, and enterprises to deliver content to any type of user, anywhere in the world. Leveraging its long-term leadership in telecommunications network equipment as well as its expertise in innovative applications and network services, Alcatel-Lucent enables its customers to focus on optimizing their service offerings and revenue streams.

The 7670 Routing Switch Platform (7670 RSP) is a highly scalable and configurable switching and routing platform designed to provide carriers with the utmost flexibility to capitalize on revenue-generating opportunities. Optimized to concurrently and reliably support multiple IP/MPLS and ATM services, the 7670 RSP delivers IP VPN, VoIP, and video services, as well as existing data services, while maintaining stringent service-level agreements. The 7670 RSP is also a key enabler in network architecture migration to the next-generation multiservice network with MPLS. By integrating both IP/MPLS and ATM control planes on a high-availability architecture that can scale without service disruption, Alcatel-Lucent has designed a best-in-class, data networking platform to deliver reliable, carrier-class services.

This general information book describes Release 7.1 of the 7670 RSP in nine chapters:

• Chapter 1 “7670 RSP overview”• Chapter 2 “7670 RSP new features overview”• Chapter 3 “7670 RSP network applications”• Chapter 4 “ATM on the 7670 RSP”• Chapter 5 “IP/MPLS on the 7670 RSP”• Chapter 6 “7670 RSP system architecture”• Chapter 7 “7670 RSP system reliability and redundancy”• Chapter 8 “7670 RSP security features”• Chapter 9 “7670 RSP system management”

Appendix A lists all the standards and specifications with which the 7670 RSP is in compliance.

Preface

iv

Appendix B lists the 7670 RSP physical characteristics and performance parameters.

For information about how to install, use, and maintain the 7670 RSP, see the 7670 Routing Switch Platform Technical Practices, Release 7.1.

v

Contents

1 7670 RSP overview......................................................................... 1

Introduction....................................................................................................................2Key operator benefits and product capabilities..........................................................2

2 7670 RSP new features overview..................................................... 5

New features...................................................................................................................6

3 7670 RSP network applications ....................................................... 7

Mobile transport infrastructure....................................................................................83G mobile aggregation and backhaul...........................................................................8Converged network transport for 2G, 2.5G, and 3G ............................................... 14Alcatel-Lucent’s multiservice IP/MPLS portfolio for mobile networks ................. 16VPNs over the 7670 RSP............................................................................................ 18Layer 2 VPNs with Ethernet and frame relay to ATM access on the 7670 RSP .. 20IP VPNs on the 7670 RSP .......................................................................................... 27Application architectures........................................................................................... 27IPv6 services................................................................................................................ 29MPLS convergence ..................................................................................................... 30Broadband aggregation .............................................................................................. 34High-speed Internet access with the 7670 RSP....................................................... 35Voice over broadband................................................................................................. 36Video services using existing DSL and multiservice IP networks ......................... 38VoP using multiservice IP networks.......................................................................... 45

4 ATM on the 7670 RSP.................................................................... 49

ATM switching architecture....................................................................................... 50Cross-connections....................................................................................................... 50IMA ............................................................................................................................... 52ILMI 4.0 ........................................................................................................................ 53

Contents

vi

PNNI routing ............................................................................................................... 53Standardized AINI support ........................................................................................ 55Connection resource display ..................................................................................... 56OAM PM....................................................................................................................... 56Traffic management capabilities................................................................................ 56

5 IP/MPLS on the 7670 RSP.............................................................. 61

MPLS overview............................................................................................................ 62S-LSPs.......................................................................................................................... 64MPLS signaling protocols........................................................................................... 65S-LSP path modification without break.................................................................... 66S-LSP tunnels.............................................................................................................. 66S-LSP protection......................................................................................................... 67MPLS OAM .................................................................................................................. 68IP data plane................................................................................................................ 68IP routing support....................................................................................................... 73IP multicast.................................................................................................................. 76IPv6............................................................................................................................... 79IP VPNs (Layer 3 VPNs)............................................................................................ 81Pseudowires ................................................................................................................ 83

6 7670 RSP system architecture ........................................................ 85

Architecture principles............................................................................................... 86System configurations................................................................................................ 87Single-shelf system overview..................................................................................... 87Multishelf system overview........................................................................................ 91Switching shelf ............................................................................................................ 95Peripheral shelf ........................................................................................................... 96In-service single-shelf to multishelf upgrade ........................................................... 98Line cards and I/O cards............................................................................................. 99

7 7670 RSP system reliability and redundancy ................................ 105

Introduction............................................................................................................... 106Infrastructure ............................................................................................................ 106Control plane redundancy ....................................................................................... 111Data plane redundancy ............................................................................................ 111

8 7670 RSP security features .......................................................... 115

Introduction............................................................................................................... 116Platform security....................................................................................................... 116Data plane security................................................................................................... 118Routing plane security.............................................................................................. 119Management plane security..................................................................................... 120

Contents

vii

Combatting security threats .................................................................................... 126

9 7670 RSP system management .................................................... 127

Integrated Layer 2 and Layer 3 management........................................................ 128External management.............................................................................................. 128Internal management ............................................................................................... 129

A 7670 RSP standards compliance and specifications....................... 133

B 7670 RSP component features ..................................................... 155

Glossary .............................................................................................. 173

Index ................................................................................................... 215

Contents

viii

1

7670 RSP overview

This chapter provides an overview of the 7670 RSP, including:

• “Introduction”• “Key operator benefits and product capabilities”

1. 7670 RSP overview

2

IntroductionThe 7670 RSP is a highly reliable, scalable, and field-proven routing and switching platform. It enables fixed and mobile operators to leverage their existing multiservice infrastructure to create a next-generation carrier-class infrastructure, capable of delivering premium, guaranteed-QoS services based on Ethernet, IPv4 or IPv6, and MPLS. For 3G mobile operators, the 7670 RSP represents a cornerstone for scalable, cost-optimized and future-proofed mobile Radio Access Network (RAN) aggregation and backhaul. The 7670 RSP integrates IP/MPLS and ATM/PNNI control planes on a high-availability, fully redundant architecture, and can simultaneously support Layer 2 and Layer 3 services, including Layer 2 VPNs and Layer 3 (IP/MPLS) VPNs.

With its ability to deliver existing legacy services, as well as new and reliable IP/MPLS and Ethernet services independently of underlying technologies, the 7670 RSP becomes a bridge to enable evolution to a converged IP/MPLS-based network. In addition, the industry-leading Alcatel-Lucent 5620 network management portfolio delivers innovative tools to manage critical, real-time voice, data and multimedia traffic, including end-to-end service interworking across different networks and technologies.

Key operator benefits and product capabilities The 7670 RSP offers:

• high availability of common platform infrastructure, cards, interfaces, and services

• in-service platform scalability• unmatched flexibility of services and interfaces• future-proof network transformation to IP/MPLS• a common management system for Layer 2 and Layer 3 interfaces

Table 1 lists the key benefits for fixed and mobile operators and the main product capabilities of the 7670 RSP.


3

Table 1: Key operator benefits and product capabilities

Key operator benefit Product capability

High-availability, telecommmunications architecture with no single point of failure

High-availability architecture:• hitless software upgrades• hardware redundancy• control redundancy: 1+1 redundant call

processing, billing, routing, network data collection, and node control

• 1+1 APS protection with no service hit to Layer 2 and Layer 3 services

• fast reroutes for LSPs and VCs• SRRP interface protection• non-stop routing for BGP, OSPF, IS-IS, and RIP• non-stop VRF routing for BGP, OSPF, RIP, and

static routes• non-stop forwarding• non-stop IP multicast• non-stop RSVP-TE signaling• non-stop DHCP relay agent• non-stop IMA• circuit emulation support on the Edge Services

Card (ESC)• hot standby for PNNI routing and signaling• nonstop MPLS signaling, LDP graceful restart• BGP and OSPF graceful restart helper• end-to-end LSP protection (fast reroute)• hitless "make before break" LSP modification• IEEE 802.3ad link aggregation on Gigabit

Ethernet line card with LACP• alarm logs and remote alarm signaling• resiliency equivalent to leased lines for Layer 3

networks

In-service scaling from 50 Gb/s to 450 Gb/s

In-service, flexible system expansion:• scalable switching fabric from 50 Gb/s to

450 Gb/s (full duplex, redundant, APS enabled)

• 100 000 IP interfaces supported per node• unsurpassed IP routing convergence speed• single Peripheral shelf deployable as

standalone (50 Gb/s)• 14 universal, multiprotocol IP/MPLS/ATM slots,

each supporting 2.5 Gb/s (user I/O) per Peripheral shelf

• capacity for up to 14 additional Peripheral shelves for growth

• Switching shelf with switching fabric for high- capacity nodes (scales to full duplex 450 Gb/s providing 32 Gb/s user I/O)

(1 of 2)


4

Delivery of any Layer 2 and Layer 3 service over any access for unmatched flexibility and revenue capture

Flexible multiprotocol capabilities:• IP/MPLS and ATM/PNNI• Ethernet-to-ATM service interworking over ATM

or MPLS• Ethernet-to-frame relay service interworking

over ATM or MPLS• full data plane transparency for frame relay

and/or ATM transport over MPLS• support for any protocol over any access

Controlled, step-by-step transformation to converged, multiservice MPLS infrastructure enabled by a dual control plane

Features that enable evolution to MPLS:• multiprotocol interfaces with simultaneous

support for POS and ATM over one physical interface

• separate control planes for MPLS and ATM signaling

• LER and LSR support• LSP signaling RSVP-TE and LDP-DU with explicit

route reservation• Ethernet, ATM, and IP pseudowire support as

per IETF PWE3• network interworking that enables

IP/MPLS-based services over ATM networks and ATM-based services over IP/MPLS networks

Common management system extends and simplifies existing operational procedures to new services

Common network and service management system for Layer 2 and Layer 3 services:• automated service provisioning• monitoring and enforcement of SLAs• open interfaces that enable simple integration

into any OSS environment• end-to-end provisioning of LSPs and VCs

Key operator benefit Product capability

(2 of 2)

5

7670 RSP new features overview

This chapter provides an overview of new features introduced in 7670 RSP Release 7.1.

2. 7670 RSP new features overview

6

New featuresTable 2 lists the latest features in Release 7.1 of the 7670 RSP.

Table 2: 7670 RSP features

Release 7.1 enhances the Edge Services Card (ESC) by adding support for two OC12/STM4 I/O interface ports as well as the existing support for OC3/STM1 interfaces. These higher speed interfaces offer customers of the 7670 RSP increased flexibility of deployment.

Release 7.1 introduces TDM circuit emulation to the ESC. TDM circuit emulation allows TDM devices with channelized DS1 interfaces to connect to the RSP. In the mobile backhaul application, this capability, when used with the existing implementation of ATM and non-stop IMA, enables the ESC and the 7670 RSP to further optimize the resources and connectivity models within the mobile telephone switching office (MTSO) for further cost improvements and optimization of mobile backhaul.

In Release 7.1, the IPv6 feature set is expanded with 6VPE functionality. The 6VPE feature allows operators to extend IP VPN functionality by enabling IPv6 CE routers to connect to and participate in IPv6 VPNs. With 6VPE, the 7670 RSP can add support for IPv6 VPNs while maintaining existing IPv4 VPNs, Ethernet, Layer 2 ATM VPNs, and other multiservice applications.

Release 7.1 also improves existing ICMP diagnostic tools with the multisession, rapid, and self ping features. Multisession ping enables operators to execute simultaneous ping commands from multiple CLI sessions. Rapid ping allows the operator to send up to 255 ping requests and view the results in a single message on the CLI screen. Self ping works in conjunction with ping or rapid ping to test the connectivity of a physical loop.

Category Feature

ATM TDM circuit emulation on the ESC

IP/MPLS 6VPE functionality

Multisession ping

Self ping and rapid ping

7

7670 RSP network applications

This chapter provides an overview of the 7670 RSP network applications, including:

• “Mobile transport infrastructure”• “3G mobile aggregation and backhaul”• “Converged network transport for 2G, 2.5G, and 3G”• “Alcatel-Lucent’s multiservice IP/MPLS portfolio for mobile networks”

• “VPNs over the 7670 RSP”• “Layer 2 VPNs with Ethernet and frame relay to ATM access on the

7670 RSP”• “IP VPNs on the 7670 RSP”• “IPv6 services”

• “MPLS convergence”• “Broadband aggregation”• “High-speed Internet access with the 7670 RSP”• “Voice over broadband”• “Video services using existing DSL and multiservice IP networks”• “VoP using multiservice IP networks”

• “Class 4: toll office displacement”• “Class 5: end office displacement”

3. 7670 RSP network applications

8

Mobile transport infrastructureMobile networks continue to experience tremendous growth, with operators further evolving their 2.5G networks, migrating from 2G to 3G technology, or simply introducing new 3G networks. Until now, the success of mobile networks has been based primarily on voice services and Short Messaging Service (SMS). However, the enhanced data capabilities introduced with 3G technology (HSDPA, HSUPA) have provided mobile operators with the opportunity to offer new services, such as video, voice, and high-speed Internet access for mobile users. As a result, high-bandwidth data capabilities are being incorporated into mobile networks as a “must-have” for mobile operators who want to stay competitive.

It is widely acknowledged that 3G and 4G services will be multimedia-based and that a highly reliable network infrastructure will be required to deliver a multitude of new, high-QoS, high-bandwidth services. As a result, mobile RANs need to offer scalability to accommodate the increased data requirements.

The 7670 RSP allows for the creation of mobile transport architectures with multimedia capabilities, including multiple concurrent voice and high-speed packet data, with sophisticated QoS management capabilities. The 7670 RSP is the cornerstone of Alcatel-Lucent’s multiservice solution for mobile operators, providing a cost-effective solution to optimize and scale a mobile RAN, while delivering high-value, reliable, and premium services. It also enables mobile operators to evolve to a future-proof, all-IP network architecture, while continuing to support existing networking protocols.

Global market requirements

Mobile operators have been focused on creating efficient 3G network architectures to extend their service offerings from voice and SMS to a wider range of multimedia services based on higher data speeds. In some developing environments and high-growth economies, new mobile infrastructures are seen as partial or full replacements for inadequate fixed network infrastructures. Globally, Alcatel-Lucent plays a leading role in the overall IP network transformation.

The 7670 RSP solution for 3G mobile operators has become widely accepted and deployed by a number of global mobile operators. Operators begin by implementing cost-effective ATM-based mobile UMTS RAN aggregation and gradually evolve to all-IP.

Some typical scenarios for 7670 RSP deployments in mobile networks are shown in the following section.

3G mobile aggregation and backhaulTo meet the needs of high-capacity 3G mobile aggregation and backhaul, the 7670 RSP delivers the Edge Services Card (ESC). This solution is optimized for the needs of 3G mobile operators who are consolidating, enhancing, or improving their 3G RAN aggregation networks. By combining the rich feature


9

set of the 7670 RSP and the scalability and flexibility of the ESC, Alcatel-Lucent delivers superior performance and density, carrier-class reliability and network management, and no-risk evolution to IP/MPLS.

The ESC is fully managed end-to-end by the Alcatel-Lucent 5620 Network Manager, addressing all key operational requirements for mobile operators, including:

• quick and easy configuration and reconfiguration• Node B reparenting• real-time equipment and network management• detailed monitoring and reporting• remote diagnostics and troubleshooting• integration with OSS/BSS

Together with the 7670 ESE, the 7670 RSP allows mobile operators to implement the solution for any level of geographical concentration. For large, centralized concentrations, the 7670 RSP is ideal, with a capacity to terminate more than 12 000 E1 lines or 16 000 DS1 lines per system, using channelized STM1/OC3 interface I/O cards and the ESC. For geographically remote concentrations, the centrally located 7670 RSP nodes can extend to connect to 7670 ESE nodes, all of which are managed by the same 5620 NM. See Figure 1 for an example of mobile aggregation and backhaul using the 7670 RSP.

Both ATM-based and Ethernet-based (IP/MPLS) solutions for 3G mobile aggregation and backhaul are possible. The 7670 RSP delivers industry-leading ATM/IMA performance and scalability. Additionally, the 7670 RSP supports ATM, Ethernet, and, coming in a future release, TDM pseudowires over MPLS. These solutions allow for converged transport of 3G and legacy traffic over new, cost-effective Ethernet-based mobile transport networks.


10

Figure 1: Mobile aggregation and backhaul using the 7670 RSP

Circuit emulation on the ESC

DS1 CE is a multiplexing technique that adapts circuit-switched traffic to and from cell relay traffic at the AAL-1 layer so that DS1 traffic can be passed transparently over an ATM network. To further lower network costs and improve the optimization of mobile backhaul, the 7670 RSP supports unstructured DS1 circuit emulation on the ESC.

Unstructured DS1 CE allows customers to connect DS1 circuits between TDM ports and TDM channelized ports, or TDM channelized ports and ATM ports on the 7670 RSP. This feature is especially ideal for mobile aggregation networks because it allows 2G and 3G traffic to be collapsed on a single platform, thereby reducing the cost and space requirements of maintaining multiple platforms. See Figure 2 for an example of 3G and 2G mobile backhaul using unstructured DS1 CE on the 7670 RSP.

RNC

RNCNodeB

BTS

NodeB

NodeB

NodeB

BTS GE

OC-12/STM-4ch

OC-3/STM-1ch

OC-3/STM-1c

LECSONET/SDH

Ring or Leased Line

LECSONET/SDH

Ring or Leased Line

SGSN

7670 RSP

PSTN

OAM IPBackbone

Internet

IP/MPLSMobile Core

MSC

GMSC

MediaGateway

OAMRouter

GGSN

NOC

IuB (Node B)Aggregation

T1/E1ATM IMA

T1/E1ATM IMA

T1/E1ATM IMA

T1/E1TDM

T1/E1TDM

T1/E1ATM IMA

18875


11

Figure 2: 3G and 2G mobile backhaul using unstructured DS1 CE on the 7670 RSP

ATM-based 3G mobile UTRAN aggregation

ATM-based mobile aggregation and backhaul is the most commonly deployed solution in UMTS networks today. To handle the increased voice and data traffic requirements for Node Bs, the ATM-based solution deploys IMA as a method of bundling a number of E1/T1 lines to provide one high-bandwidth data pipe from Node B to the RNC. Figure 3 displays this solution.

Figure 3: ATM-based mobile UTRAN aggregation using the 7670 RSP

2G trafficChannelized OC12 from LEC Channelized OC3/TDM BSC

OC3c/ATM

OC12c/ATM

IMA group

3G traffic

ATM

7670 RSPESCTDM

switchingESC

TDM

IMA MR48 orESCATM

RNC

MSC

19132

Node BnxE1/T1

nxE1/T1

VPs from Node Bsdelivered over OC3/STM1c

or OC12/STM4cIMA (nxE1/T1 Bundles)

over OC3/STM1ch

RNC

Cell RelayIMA

SONET/SDHADM

7670 RSP

Consolidated Node B TrafficOver a Single VP

NBAP (AAL5)ALCAP (AAL2)OAM (AAL5)Sync (AAL2)

nxUser Data (AAL2)

nxUser Data (AAL2)

Node B

18873


12

Evolution of 3G RAN aggregation to IP

The evolution of the aggregation network to IP requires minimal or no changes on the 7670 RSP. Both the interface and protocols of the 7670 RSP are designed to reliably support the evolution from circuit-switched to packet-switched access technologies. The multiprotocol features of the 7670 RSP enable simultaneous support of ATM, IMA, Ethernet and IPv4/IPv6/MPLS connections to the RAN, as shown in Figure 4. The 7670 RSP also supports full network and service interworking for the transport of pseudowire circuits over MPLS.

Figure 4: Evolution of 3G RAN aggregation to IP using the 7670 RSP

Optimization of mobile telephone switching offices (MTSO)

The 7670 RSP is an ideal solution for the optimization of MTSO and Radio Network Controller (RNC) interfaces. The 7670 RSP can optimize the utilization of interfaces and therefore minimize the number of interfaces required to connect the aggregation network to the RNCs. This can significantly reduce OPEX, since software configuration using the 5620 NM is all that is required for reconfiguration of the interfaces towards the RNC for Node B reparenting and for handling increased cell capacity. This optimization solution is portrayed in Figure 5.

T1/E1ATM IMA

T1/E1ATM IMA

T1/E1ATM IMA

T1/E1TDM

T1/E1TDM

T1/E1MLPPP

IP (MLPPP)Aggregation

IP-MPLSEthernet

ATM/IMAAggregation

7670 RSP withEdge Services Card

OC12/STM4ch

OC3/STM1ch

STM-n/OC-n

GE

RNC

RNC

Node B

BTS

BTS

Node B

Node B

BTS

T1/E1 ATM IMA

Ethernet

MPLSPseudowire

T1/E1 TDM

Node B

Node B

BTS

7705 SAR


13

Figure 5: Optimization of MTSO

Key benefits of using the 7670 RSP for 3G RAN aggregation

Built for carrier-class environments and for deploying high-availability features such as non-stop routing, non-stop forwarding, and non-stop IMA, the 7670 RSP is ideal for use in 3G RAN aggregation. Several key benefits of using the 7670 RSP in the mobile aggregation and backhaul network include:

• cost-effective, flexible, in-service scaling over a range of aggregation requirements, from smaller aggregation points to extreme densities (thousands of Node Bs per site)

• superior performance, with top-in-class MPLS/IP/ATM functionality and features

• provision of services according to strict Service Level Agreements and based on measurable QoS parameters

• carrier-class reliability, enabled by superior product hardware design and robust software implementation

• future-proof growth from proven ATM/IMA infrastructures to multiservice IP/MPLS-based solutions, facilitating a smooth evolution to mobile NGN and IMS deployment

• unified management using the 5620 NM

New services can be provisioned smoothly and quickly, without disruption to existing services, as seen in the deployment of the 7670 RSP in more than 110 mobile and fixed networks worldwide.

Cell Site

7670 ESE

7670 ESE RNC

RNC

RNC

RNC

RNC

RNC

7670RSP

18872

Cell Site

Cell Site

Cell Site

Logical RNC-Node B mapping

MTSO


14

Converged network transport for 2G, 2.5G, and 3GMobile operators frequently have multiple 2G and 3G network overlays. The 7670 RSP multiservice-based transport solution is widely used to create a common, converged transport infrastructure and to assist with migration from circuit-switched 2G to packet-switched 3G, and also with the evolution to IP.

The 7670 RSP and 7670 ESE solution can deploy a mix of transport technologies on a discrete E1/T1 level, thereby successfully lowering the cost of combined operation of the converged network infrastructure. By selectively choosing the aggregation points in a network, the overall number of required leased line or microwave transport facilities can be reduced and the cost of transport lowered. This converged network infrastructure is displayed in Figure 6.

Figure 6: Converged network transport for 2G, 2.5G, and 3G

BTS

LECaccess ring

2G and2.5G

2G and2.5G

3G

3G

Node B

Node B

BTS

Packet domain

Circuit domain

Multiservice IPnetwork

Core network (CN)UMTS terrestrial radio accessnetwork (UTRAN)

Internet

7670 RSP 7670 RSP

BSCRNC MSC

3G MSC GMSC

PSTN

Voicenetwork

Datanetwork

Consolidated access traffic:2G TDM - Voice2.5G TDM - Voice & Data3G ATM or IP - Voice & Data

Consolidated backbone traffic:2G TDM - Voice2.5G TDM - Voice, FR/ATM/IP - Data3G TDM/ATM/IP - Voice, ATM/IP - Dataplus FR/Ethernet/IP - OA&M, IT traffic

18876

SGSN GGSN


15

The main applications for this converged transport infrastructure are:

• ATM aggregation to and from the RNC• frame relay transport for GPRS traffic from the BSC to the SGSN• TDM grooming and aggregation• voice compression for voice transport between MSCs• voice compression for voicemail servers• low-speed aggregation of IP services to a BB router (Ethernet, DS1/E1),

minimizing the number of ports required on the router• PPP termination and aggregation for 3GPP R5 UTRAN• 1+1 bidirectional protection protocol based on ITU-T G.841 Annex B and

optimized for networks using 1+1 bidirectional switching (available in a future release)

Common aggregation network for 2G, 2.5G, and 3G

With the addition of the 7670 ESE, the 7670 RSP can provide a critical part of the solution for 2G and 2.5G grooming and aggregation, as displayed in Figure 7. The 7670 RSP and 7670 ESE nodes enable the transformation from 2G or 2.5G to 3G aggregation and support guaranteed QoS for voice and data traffic. The 5620 NM provides simple point-and-click provisioning to set up connections between nodes, through the use of customized templates.

Figure 7: Using 7670 RSP and 7670 ESE for common aggregation network

RNC

BSC

RNC

BTS T1/E1 TDM

MicrowaveT1/E1 TDM

OC3/STM1 ch

OC12/STM4

IP/MPLS/Ethernet

ATM/IMA (nxT1/E1)

MultipleAccess Services

Grooming andConcentration

EfficientHandoff

MobilePoP

Node B

ATM/IMA (nxT1/E1)Node B

Network andService

Management

BTS

Node B

18871

7670 RSP

7670 ESE

MTSO


16

Key benefits for converged network infrastructure

By deploying both the 7670 RSP and the 7670 ESE, mobile operators gain the following benefits:

• the ability to provide a common environment for the transport of 2G, 2.5G, and 3G services

• a consistent service environment for reliable delivery and transport of a range of Layer 2 and Layer 3 services

• overall transport cost optimization for mobile access networks (RAN/UTRAN), applying optimized aggregation of Node B/BTS traffic through the deployment of either ATM/IMA or MC/ML-PPP over SONET/SDH and Ethernet/MPLS/IP

• consistent management interface and practices, using the 5620 NM

This solution delivers superior performance and a cost-effective evolution to IP/MPLS architecture.

Alcatel-Lucent’s multiservice IP/MPLS portfolio for mobile networksAlcatel-Lucent’s multiservice solution for mobile operators includes the 7670 RSP, the 7670 ESE, the 7470 MSP, the PSAX portfolio of products, and the MainStreet family of narrowband (TDM) multiplexers. These products are field-proven, carrier-grade platforms and are perfectly suited to meeting the QoS requirements of both voice and data services, providing a smooth transition from TDM to ATM and IP/MPLS, and offering the required scalability to support rapid growth.

The Alcatel-Lucent 5620 Network Manager gives operators complete control and visibility of all their network resources and plays an important role in enabling all of the network elements to work together.

The features and benefits of the portfolio for backhaul and transport in mobile networks are summarized in Table 3.

Table 3: Features and benefits of the Alcatel-Lucent portfolio in mobile networks

Feature Benefits

Predictable and consistent voice quality

Cost savings with advanced voice processing

Reduced leased lines costs with voice compression and silence suppression, along with AAL-2 or AAL-5 transport

Reduced leased lines for access backhaul

Cost savings through grooming and aggregationIncreased utilization and reduced number of RNC interfaces

Reduced number of BSC ports

Reduced cost per port on BSC and MSC by moving connectivity from physical E1/T1 to channelized STM1/OC3

(1 of 3)


17

Network convergence of 2G, 2.5G, and 3G

Network optimization with consolidation

Reduced network complexity by consolidating all services onto a single platform

Network evolution supported on same platform• 2G (TDM and voice transport

over AAL-1, AAL-2, or AAL-5)• 2.5G (FR, IP, MPLS)• 3G (IP, MPLS, ATM)

Investment protection of existing infrastructure

Integration of IP, MPLS, and ATM on same platform

Seamless migration to 3G services and risk mitigation

Separate control and data plane for ATM and MPLS

Support for MPLS and native IP forwarding

Real-time service provisioning for rapid service rollout

Simplified and more efficient operation

Faster provisioning times than individual element management systems

Reduced risk of operator error through automation

Flexible billing options

Faster network engineering and growth

Network portioning, which allows mobile virtual network operators to share the same infrastructure

Support for rapid fault detection and problem isolation through extensive OA&M capabilities

Multishelf support, enabling in-service expansion without service impact

Scalability without service impact

Backbone scalability, up to 450 Gb/s (multishelf 7670 RSP)

Support for access network interfaces from n x 64 kb/s T1/E1 to channelized OC3/STM1

Feature Benefits

(2 of 3)


18

As mobile networks grow and evolve from 2G to 3G, mobile operators need to consider the next major challenge: the evolution towards the mobile NGN and IMS, while maintaining profitability at all service levels. To accommodate service growth, operators need to balance the goal of deploying cost-effective 3G RAN transport infrastructure, which can deliver all required services today, with the goal to evolve to a future-proof infrastructure. Alcatel-Lucent’s multiservice-based mobile transport solution provides an evolution path to help operators accomplish both of these goals.

VPNs over the 7670 RSPAlcatel-Lucent provides the industry's most complete, consolidated VPN solution suite, which can be delivered to customers in various locations using many different currently available access technologies (see Figure 8).

Service differentiation based on service categories and QoS

Service level assurance

Support for IP CoS and ATM QoS, including DSCP classification

Support for per-VC traffic shaping and queuing

QoS-based SLAs

Service consolidation support for circuit emulation, FR, ATM, Ethernet, and POS interfaces

Service flexibility with multiservice capabilities

High-density channelized interfaces

2G, 2.5G, and 3G traffic over the same physical links

Reduced number of elements in the access layer with integrated capabilities (DACS multiplexer)

Reduced time to market for new service capabilities with the addition of the ESC

Field-proven reliability with greater than 99.999% availability

Reliability and network resiliency

Non-stop routing, enabling the deployment of high-availability, carrier-class IP networks (7670 RSP)

Supported SPVCs for dynamic reroutes around network failures

Automatic protection switching

IPv6 ready IPv6 readiness

Support for advanced 3G services, such as IMS

Feature Benefits

(3 of 3)


19

Figure 8: Access technologies used to deploy VPNs

VPNs enable multiple end-user locations to be interconnected over a shared infrastructure while providing controlled access, guaranteed bandwidth, and security.

Over the past decade, VPNs have evolved from enterprise-driven VPNs that enable remote users and small offices to connect to the main corporate network over the Internet through secure tunnels, to more sophisticated service provider-driven VPN services that are delivered over high-speed, high-capacity, carrier IP/MPLS core networks.

The 7670 RSP can be used as a PE router, P router, or both, to deliver a full range of service provider-based VPN services including traditional ATM and frame relay services, flexible Ethernet-enabled Layer 2 VPN services, and MPLS-based IP VPN services (see Figure 9).

Manufacturers

Teleworker

Branch officeHead office

Suppliers

PartnersATM Leased

line

DSL

IP

FrameRelay

Ethernet

VPN

18039


20

Figure 9: Typical service provider network

Layer 2 VPNs with Ethernet and frame relay to ATM access on the 7670 RSPLayer 2 VPNs provide Layer 2 connectivity between multiple customer sites using point-to-point connections across a service provider network. Access to a Layer 2 VPN is generally provided over Ethernet, frame relay, or ATM connections. Traditional Layer 2 VPN services, including frame relay and ATM, are supported on ATM networks and provide solid QoS and resiliency. However, when an IP/MPLS core network is present, it is also possible to deliver Layer 2 services in addition to Layer 3 or IP VPN services (see Figure 10).

CE

P

PPE PE

PE

P

CE

18057

CE CE CE

CE

CE


21

Figure 10: Layer 2 VPNs over MPLS or ATM networks

Benefits of Layer 2 VPNs

Layer 2 VPNs offer several benefits to both service providers and end customers.

• Layer 2 VPNs are simple to provision and manage, because the service provider network does not participate in routing or need to learn end-customer Layer 3 routing information.

• With well-defined service and network interworking standards, Layer 2 VPNs can be delivered using a variety of Layer 2 access technologies, which enables flexible services to be designed to better meet the requirements of end customers.

• End customers maintain autonomy over their corporate networks, with a higher level of security against hacker attacks and other security concerns because Layer 3 routing information is retained in-house.

The 7670 RSP supports the deployment of the following Layer 2 VPN solutions that can be customized to meet the most demanding customer requirements:

• ATM and frame relay VPN services• Ethernet VPN services

Gigabit EthernetUNI

Gigabit EthernetUNI

ATM7670 RSP

ATMNNI

ATM UNI

ATM UNI

Ethernet UNI Ethernet UNI

FR UNI FR UNI

ATM UNI

ATM UNI

PE router PE router

7670 RSP

7670 ESE

Gigabit EthernetCE router

ATMCE router

EthernetCE router

ATMCE router

FRCE router

Gigabit EthernetCE router

ATMCE router

EthernetCE router

ATMCE router

FRCE router

MPLS(over ATM, POS,Gigabit Ethernet)

ATMNNI

7670 ESE

18058


22

ATM and frame relay VPNs

Frame relay is still one of the most widely used access technologies for network-based VPNs today. Frame relay networks are simple to operate and highly reliable. Service level agreements can be established, monitored, and delivered with high confidence.

ATM is often associated with frame relay VPNs mainly as the core network infrastructure for frame relay services. However, ATM is often deployed as an enhancement to a frame relay VPN, offering higher bandwidth connectivity to high traffic sites.

The Alcatel-Lucent portfolio of multiservice, multiprotocol products—the 7670 RSP, 7670 ESE, 7470 MSP, and PSAX —enables the deployment of frame relay-to-ATM VPNs. These products provide channelized and unchannelized frame relay and ATM interfaces to customers or can be used as network links.

Figure 11 shows how a frame relay-to-ATM VPN based on the Alcatel-Lucent portfolio uses different access technologies such as ATM and frame relay.

Figure 11: Frame relay-to-ATM VPN using Alcatel-Lucent platforms

Frame relay-to-ATM network interworking

Frame relay VPN services are delivered across an ATM network using frame relay-to-ATM network interworking. A frame relay-to-frame relay connection over an ATM network is created in three stages as illustrated in Figure 12.

Manufacturer B

Branch B

Customer AHQ

Branch A

FR/ATM

7470 MSP

ATM OC3/STM1

ATM T1/E1

Frame relay/DS3/E3

ATM OC3/STM1 Frame relay/DS3/E3

ATM IMAn x T1/E1

Customer BHQ

Manufacturer A

PSAX

PSAX

7670 RSP

7670 ESE

5620 NM

19099


23

Figure 12: Frame relay network interworking

• RFC 2427 encapsulated traffic is received on a 7670 ESE frame relay interface. The 7670 ESE converts the traffic stream to RFC 2684 routed encapsulated traffic over ATM.

• The converted traffic is transmitted to the 7670 RSP through an ATM NNI connection and aggregated for transport across the ATM network.

• At the far end, the ATM cells are converted back to frame relay at the egress 7670 ESE.

Frame relay-to-ATM network interworking connections can be manually configured using the CLI or the 5620 NM, or can be dynamically established using PNNI-signaled SPVCs.

Frame relay-to-ATM service interworking

The addition of ATM access to a frame relay VPN service is delivered using frame relay-to-ATM service interworking. The 7670 RSP supports frame relay-to-ATM service interworking on the 7670 ESE. For more information about frame relay-to-ATM service interworking, see the 7670 Edge Services Extender Technical practices.

Ethernet services on the 7670 RSP

Over the past several years, the use of Ethernet as a service in wide area networks has significantly increased due to its operational simplicity and low transmission cost. Today, with improvements in network availability and resiliency, along with advancements in Ethernet OA&M and service management capabilities, Ethernet is becoming well established as a mainstream alternative for WAN connectivity.

7670 RSP 7670 RSP

FRUNI

FRUNI

ATM

7670 ESE 7670 ESE

CPE Ethernetswitch or router


18062


24

Benefits of Ethernet services

Using a 7670 RSP IP multiservice network to introduce Ethernet services provides the following benefits:

• reduced time to market because incumbent service providers can quickly introduce new Ethernet services by simply adding line cards and updating OSS procedures, as compared to the time and effort required to deploy a new network

• lowered investment risk by deferring capital and reducing upfront costs—Ethernet services can be introduced and market-tested on existing infrastructures across the entire serving area. As service volumes ramp up, complementary new infrastructures can be evaluated and deployed to deliver scaled and enhanced services.

• protection of existing frame relay business revenues and reduced customer churn by using frame relay to ATM or Ethernet “service hybrids” that support nondisruptive migration from traditional ATM and frame relay VPN services to newer Ethernet-based VPN services

7670 RSP Ethernet VPN services

The 7670 RSP enables the deployment of flexible Ethernet services that can be delivered over ATM or IP/MPLS network infrastructures:

• point-to-point Ethernet service• over ATM (transparent LAN service)• over MPLS (Ethernet virtual leased lines)

• Ethernet-to-ATM/frame relay interworking services• Ethernet-to-ATM service interworking over ATM• Frame relay-to-Ethernet service interworking over ATM• Ethernet-to-ATM service interworking over MPLS

Point-to-point Ethernet service

A point-to-point Ethernet service is a point-to-point connection between two customer sites that enables the transfer of Ethernet frames across a service provider network. An Ethernet VPN is created when several customer sites are interconnected through a series of point-to-point Ethernet connections, most commonly in a hub-and-spoke network topology. In many ways, a point-to-point Ethernet service is similar to a frame relay PVC service, except that it offers much higher access bandwidth (10 Mb/s to 1000 Mb/s, instead of 64 kb/s to 45 Mb/s) for customer-attached sites.

Ethernet service over ATM

Ethernet services over ATM are supported on the 7670 RSP using Ethernet network interworking over ATM. To create an Ethernet transparent LAN service, the customer site is attached to the 7670 RSP through an Ethernet VLAN (tagged or untagged) or port-based interface. The incoming traffic is converted into ATM cells using RFC 2684 bridged encapsulation and is then transported across the ATM network. At the far end, the Ethernet frames are extracted and delivered to the destination customer site through the


25

destination 7670 RSP Ethernet interface. Ethernet service connections over ATM can be manually configured using the CLI or the 5620 NM. For PNNI-enabled networks, extensions to PNNI provide the capability for SPVCs to be signaled through the ATM network between the Ethernet interfaces.

Ethernet virtual leased line services

Ethernet VLLs over MPLS are supported on the 7670 RSP using Ethernet network interworking over MPLS. The customer site is attached to the 7670 RSP Ethernet VLAN (tagged or untagged) or port-based interface. Ethernet frames are then converted to MPLS packets with the addition of a two-deep MPLS label stack as defined in draft-Martini. The inner label represents the Layer 2 Ethernet connection, also known as an Ethernet pseudowire. The outer label identifies the LSP tunnel that is used to forward the packet through the MPLS network. The MPLS packets then leave the 7670 RSP on an MPLS-capable interface (POS, Gigabit Ethernet, or ATM) and traverse the MPLS network to the far-end 7670 RSP MPLS interface. The MPLS labels are stripped, and the Ethernet frame egresses the far-end 7670 RSP Ethernet interface to the destination LAN.

Interworking services

By interworking with and extending the installed base of frame relay service, Ethernet can remove bandwidth constraints, reduce costs, and take Layer 2 service offerings to a new level. Enterprise customers can leverage high-speed, cost-effective Ethernet access at major sites or headquarter locations where traffic demands warrant it, while retaining frame relay or ATM access at more remote sites where Ethernet service may not be available or practical. The ability to offer a range of Layer 2 access options enables truly flexible, value-added services to be created for enterprise customers.

Frame relay-to-Ethernet service interworking over ATM

On the 7670 RSP, frame relay-to-Ethernet service interworking functionality is accomplished in two stages. First, frame relay traffic is service-interworked to ATM on a 7670 ESE. Then, ATM traffic is service-interworked to Ethernet on the 7670 RSP.

Frame relay-to-Ethernet service interworking connections can be PVC-based and set up manually using the CLI or 5620 NM, or dynamically established using SPVCs signaled by PNNI (see Figure 13).


26

Figure 13: Frame relay-to-Ethernet service interworking

Ethernet-to-ATM service interworking over ATM

For Ethernet-to-ATM service interworking over an ATM network, Ethernet traffic must be encapsulated in ATM cells. Two types of encapsulation are supported on the 7670 RSP: RFC 2684 bridged Ethernet, which provides interworking at the Ethernet layer, and RFC 2684 routed encapsulation, which provides interworking at the IP layer. The 7670 RSP VC-VLAN cross-connect feature is then used to define the actual connection between the ATM VC or VP endpoint and the Ethernet port or VLAN endpoint.

Ethernet-to-ATM service interworking over MPLS

In order to create an Ethernet-to-ATM interworking connection over MPLS on the 7670 RSP, the CE device that is connected through ATM must support RFC 2684 bridged or routed Ethernet encapsulation. When bridged encapsulation is used, the 7670 RSP performs service interworking at the Ethernet layer—stripping the ATM bridged encapsulation information from the incoming packet, and creating an Ethernet pseudowire based on the Ethernet header information for transport across the MPLS network (see “Ethernet virtual leased line services” in this section). At the far end, MPLS encapsulation is removed, and the native Ethernet frame is presented to the far-end Ethernet port.

When routed encapsulation is used, the 7670 RSP performs interworking at the IP layer—stripping the ATM encapsulation information on ingress and creating an IP pseudowire for transport across the MPLS network. At the far end, the MPLS headers are removed, and an Ethernet frame is created and sent from the destination Ethernet port.

7670 RSP 7670 RSP

ATMUNI

FRUNI

ATM to Ethernet SPVC signaled by PNNI(uses ATM/MPLS mediation over

MPLS core)

GigEATM

7670 ESE



ATM to Ethernet SPVC signaled by LDP(only over MPLS core)

FR to Ethernet SPVC signaled by PNNI(uses ATM/MPLS mediation over MPLS core)

FR toATM PVC

FR toATM PVC

18061


27

IP VPNs on the 7670 RSPIP VPNs have evolved into carrier-grade services. The IP VPN service is not a best-effort-based IP service such as Internet access. Capabilities such as service assurance, reliability, availability, and high performance ensure that Layer 3 networking equipment is up to the challenge posed by real-time traffic and high-priority data with stringent support requirements. The Alcatel-Lucent solution for IP VPNs, based on the 7670 RSP and managed by the 5620 NM, enables service providers to capitalize on this opportunity by leveraging the existing network architecture to offer premium Layer 2 and Layer 3 services.

Benefits

The carrier business challenges are to meet the enterprise SLA demands using the IP VPN architecture while minimizing the costs associated with enabling this service and maximizing potential revenue.

• IP VPNs enable the carrier to provide enterprise services with different connectivity architectures: hub and spoke, full mesh, or partial mesh between enterprise sites in a cost-effective manner.

• IP VPNs give the service provider access to an enterprise’s IP addressing and network topology. This enables value-added services such as Web hosting, data storage, customer IP address allocation, centralized e-mail, and firewall protection to be offered.

• IP VPNs offer unprecedented flexibility in interconnecting different sites with different access technologies.

• IP VPNs enable a reduction in the number of physical and logical ports that the CPE must support in order to interconnect the diverse sites of the enterprise customers.

• IP VPNs also reduce the number of connections the service provider must support in the network.

• IP VPNs can be used by a service provider to ensure proper IP network partitioning through BGP-4/MPLS VPNs. Different applications and services —such as VoIP, management traffic, or operator’s intranet traffic—can be properly partitioned and processed accordingly by assigning them to different VPNs. Through this virtual isolation, the routing and forwarding are controlled on a per-VPN level, the impact of processing different types of traffic is minimized, and the reuse of IP private addresses is enabled.

Application architecturesIn a fundamental network topology for an IP VPN, a CE device typically connects to the provider network through Layer 2 connectivity (frame relay, ATM, Ethernet, or PPP). The Layer 2 identifier (DLCI, VCC, or VLAN port) points to a VRF on the PE device.

The CE router advertises its local VPN routes to the PE router and learns remote VPN routes from the PE router. Routing information between PE and CE can be provisioned statically or by using a dynamic protocol such as OSPF


28

or EBGP. Exchange of VPN route information between PE routers is done through iMBGP. A PE router pushes and pops MPLS labels on the IP datagram, and is referred to as an LER. Nodes that switch the datagram based on the MPLS header are LSRs. Figure 14 illustrates the basic network topology for an IP VPN.

Figure 14: Basic network topology for IP VPN

IP VPNs rely on a control plane to distribute VPN routes and bind them to an MPLS label and a data plane to switch the data through the network. The control plane uses multicast BGP to advertise routes between PE routers and binds routes with an inner and outer label. The inner label identifies a route within the VPN, while the outer label identifies the LSP that the packet will traverse to reach a destination. The control plane also ensures that an outer LSP between adjacent PE routers has been configured. The outer tunnel can be signaled with LDP or RSVP-TE. The data plane oversees the encapsulation of the IP datagram with the MPLS headers on the ingress PE router and the removal of this encapsulation at the egress PE router. Figure 15 shows an example of a network topology of an IP VPN service for a customer with three sites.

VPN 2Site B

VPN 1Site A

7670 RSP 7670 RSP

7670 RSP

FrameRelay

ATMAccess

VPN 2Site B

VPN 1Site A

VPN 2Site B

VPN 1Site A

MetroAccess

VRF

VRF

VRF

18045


29

Figure 15: Sample network topology for IP VPN service with three sites

IPv6 servicesIPv6 implementation on the 7670 RSP extends the high-availability, non-stop routing and forwarding capabilities inherent to the platform and provides the flexibility to use the existing architecture to introduce IPv6 services in an IPv4/MPLS environment. Figure 16 shows how multiprotocol BGP, with the IPv6 address family, exchanges the IPv6 routes between 6PE or 6VPE routers over the IPv4/MPLS core network.

7670 RSP

VPN 1Site C

Data Layer:Ethernet (VLAN)CE-PE DynamicProtocol EBGP

Data Layer:FR (DLCI)CE-PE DynamicProtocol: OSPF

Data Layer:ATM (VCC)CE-PE Static

VPN 1Site B

VPN 1Site A

7670 RSP

VRF

VRF

7670 RSP

VRF

Outer tunnelsinterconnecting

the PE sites

Inner labelsassigned to thecustomer VPN

18046


30

Figure 16: IPv6 Internet access

MPLS convergenceThe 7670 RSP has the power to deliver multiservice IP solutions and enable service providers to maximize the network and customer access lines they have in place, in order to offer multiple services without operating multiple service networks. Figure 17 illustrates the 7670 RSP capabilities to deliver today’s new advanced services over converged IP/MPLS networks while giving service providers the option to support existing ATM-based Layer 2 services over MPLS or in their native mode over ATM/PNNI.

IPv6

IPv6

IPv6

IPv6

MPLS/IPv4network

6PE6PE

6VPE 6VPE

18843


31

Figure 17: Deriving maximum value from the multiservice WANs

The converged network is a unified network infrastructure that supports an MPLS-based network with Layer 3 service capabilities while preserving the existing frame relay and ATM data network and Layer 2 services.

Market drivers

The fundamental drivers behind convergence are based on improved network efficiency: better use of network resources and reduced costs for adding new services and revenue streams on common network assets.

Enterprise customers continue to use leased lines, frame relay, and ATM services for data because of their availability, reliability, security, and interoperability. Therefore, the continued support for traditional Layer 2 services is an essential part of any successful service evolution strategy.

However, enterprises are increasingly moving towards IP-based applications. Since the ultimate function of a network is to support applications, this in turn drives demand for IP services. As it makes little sense to invest in two or more parallel networks—one for Layer 2 services and one for Layer 3 services—carriers are looking for solutions that enable them to introduce new services using their existing infrastructure.

The common business challenge for data network convergence is based on two inter-related requirements: the transformation of existing multiservice networks to MPLS, and the ability to offer new IP services.

7670 RSP

7670 RSP

> Internet security> Content hosting> E-business integration> Disaster recovery> Application management

Ethernet

Ethernet

ATM

GigE

FrameRelay

FrameRelay

Cars'R'Us

HubCaps Int'l

Cars'R'Us

IPNetwork

ASP orData Center

MultiserviceIP Network

IP, MPLS, ATM

MultivendorATM/FR Network

HubCaps Int'l

HubCaps Int'l

Cars'R'Us

Cars'R'Us

7670 RSP

18047


32

7670 RSP solution

Engineered for carrier-grade performance and next-generation service delivery, the 7670 RSP makes the move to IP/MPLS seamless, risk-free, and profitable. The multiprotocol switch router platform has the ability to migrate large-scale multiservice ATM/frame relay networks to a carrier-grade IP/MPLS implementation.

The 7670 RSP supports the following key multiservice edge services as a complete management solution with the Alcatel-Lucent network management portfolio:

• IP VPNs• frame relay-to-ATM VPNs• frame relay-to-ATM-MPLS consolidation• Ethernet-frame relay-to-ATM interworking• Ethernet VLLs• Internet access• IPv6 services

Benefits

The 7670 RSP enables carriers to balance revenue growth with market leadership. With a 7670 RSP converged data network, carriers can:

• enable new services, including interworking between existing services• enable Layer 2 and Layer 3 services to coexist and interwork effectively• scale networks to support a range of customer and network sizes• expand existing service range and competitiveness and improve bottom line

contribution• improve the use of existing assets without building more overlays

The following sections outline two possible approaches to network migration with the 7670 RSP: Ships-in-the-Night, and MPLS core with ATM over MPLS.

Ships-in-the-Night: IP/MPLS core networking with native ATM switching

IP/MPLS networking can coexist with native ATM switching on the 7670 RSP without any network or service interworking yet provide flexibility to offer both services at the same time. As a multiservice IP and ATM switch, the 7670 RSP is capable of delivering the best of both worlds: ATM protocols for providing native ATM services and IP/MPLS protocols for providing IP/MPLS-related services. Carriers can take advantage of the multiservice capabilities of the 7670 RSP to unify their networks while embarking on the road toward IP/MPLS in parallel. The first step can be the adoption of the 7670 RSP as a Ships-in-the-Night platform where ATM and MPLS run concurrently yet separately and the 7670 RSP is able to connect to non-MPLS nodes. The PNNI protocol is still predominantly used to provide ATM switched services, and IP/MPLS protocols are used for IP services.


33

Ships-in-the-Night can be used as a transitioning mechanism as networks migrate their ATM control planes to MPLS. For example, service providers can move their data and non-real-time UBR traffic to MPLS label switched paths, yet keep their CBR and VBR traffic (for example, higher QoS voice and video) on ATM connections. A change in an MPLS label switched path has no impact on an ATM virtual circuit, and vice versa.

MPLS core with ATM over MPLS

MPLS delivers all the benefits of connection-oriented virtual circuits as found in ATM, while reusing a unified MPLS core for new and enhanced services. MPLS provides excellent traffic engineering, including some unique ways to optimize the network. MPLS also provides highly resilient paths using MPLS fast reroute. The benefits of MPLS make it a natural choice for a converged core network, and it is also becoming a popular delivery mechanism for new services at the edge (such as IP VPN).

In order to converge ATM traffic over an MPLS network, the core network must support the ability to encapsulate ATM traffic into MPLS packets. The 7670 RSP enables such encapsulation techniques and provides flexible network interworking to carry ATM traffic over an MPLS core network. The 7670 RSP supports the aggregation of multiple ATM VCCs and VPCs in MPLS LSPs. This mechanism can support all ATM AAL types and the transport of ATM cells in a single MPLS frame.

ATM pseudowires over MPLS

In order to create ATM pseudowires across an MPLS network, the first step is to encapsulate the ATM cells in an appropriate envelope. There are several types of encapsulation, and the choice of encapsulation method is driven by the nature of the traffic being carried (AAL-1 versus AAL-5), and by the priorities of the carrier (bandwidth efficiencies versus retaining granularity on ATM QoS and traffic management). The choices of encapsulation method are:

• cell mode: N:1 and 1:1 encapsulations• frame mode: AAL-5 SDU and AAL-5 PDU encapsulations

Figure 18 shows this type of network convergence with the 7670 RSP.


34

Figure 18: Network convergence with the 7670 RSP

Broadband aggregationThe 7670 RSP complements broadband access solutions by concentrating the traffic coming from the access network. This aggregation enables the efficient trunking of DSLAMs over a high-speed link to the network core. While aggregating last-mile traffic, the 7670 RSP can also deliver IP-based advanced multimedia services.

Interworking with Ethernet solutions (DSLAM aggregation)

In video solutions that include both ATM and Ethernet DSLAMs, the 7670 RSP can be used in the IP backbone to complement Ethernet aggregation devices. The connection to the 7670 RSP is through Gigabit Ethernet interfaces or OC48/STM16 packet over SONET/SDH (POS). Figure 19 illustrates the leveraging of existing architecture for ATM and Ethernet DSLAMs.

IP Enabled Multiservice

Network

Doorlocks Ltd.HQ

Doorlocks Ltd.Data Center

HubCaps Int'lHQ

HubCaps Int'lManufacturing

Cars 'R' UsRegional office

18054

Cars 'R' UsHQ

GigE

Cars 'R' UsManufacturing

L2 VPN overIP-Enabled

Multiservice Network

L3 VPN overIP-Enabled Multiservice

Network

ATM SVCs, SPVCs, PVCs overIP-Enabled

Multiservice Network

IP Network

POS

7670 RSP 7670 RSP

ATM

ATM

7670 RSP 7670 RSP

FrameRelay

7670 RSP

MultivendorATM/FR Network


35

Figure 19: DSLAM aggregation with the 7670 RSP

The 7670 RSP is the ideal platform for extending broadband aggregation to deliver all services (high-speed Internet, video, VoD, VoIP) simultaneously:

• enables smooth migration from the ATM transport network of today to a triple-play network while preserving existing infrastructure investments

• uses separate VCs to maintain QoS for each service and each customer• supports hybrid models (IP model for VoD, ATM/PPP model for high-speed

Internet, and ATM point-to-multipoint for broadcast video), enabling maximum flexibility in the service provider’s migration and deployment strategy

• provides non-stop routing, control, and line card redundancy and advanced CoS features for unparalleled service reliability and flexibility

High-speed Internet access with the 7670 RSPThe 7670 RSP is able to deliver high-speed Internet service concurrently with other services (broadcast video, VoD, VoIP). Figure 20 illustrates the high-speed Internet access application on the 7670 RSP.

7670 RSP(Gateway to Internet)

IP/MPLS/ATMBackbone

7670 RSPATMDSLAMs

EthernetDSLAMs

DSL Modem

DSL Modem

VoD ContentServer

VoD ContentServer

DHCP Server

7450 ESS

VPLS-BasedNetworkBackhaul

(7450)

18051


36

Figure 20: High-speed Internet access with 7670 RSP

Voice over broadbandVoBB is often defined simply as voice services offered over broadband Internet connections. While this is true, the implications of VoBB for residential subscribers, enterprises, and carriers extend far beyond just putting telephony services over data lines. The integration of telephony and the Internet is enhancing the future of communications and blurring the differences between voice and data messaging.

This integration of communications creates a new world of revenue-generating services that are highly advanced as well as easy to use and access. VoBB (see Figure 21) is a critical step in increasing the capabilities, effectiveness, and accessibility of today's communications systems.

Figure 21: Voice over broadband

7670RSP

IP/MPLS/ATM

Backbone

DHCPServer

OSPF or IS-IS

adjacency

DSLModems

DSLAMs

ATMConnection

7670RSP

BGPPeering

18055

Private IP NetworkBB Access

NB Access

PSTN

Softswitch

SIP Phone POTS/ISDN

Modem

AccessGateway

18065


37

New level of service

Service providers began rapidly expanding their data networks worldwide, offering large data pipes even for residential subscribers. This technology opened the door for VoBB by offering service providers another way to access the last mile. Yet while this access to subscribers is critical, even more benefit is gained because VoBB calls are transmitted as data using IP.

There are three types of carriers offering VoBB: MSOs, DSL providers, and alternative VoBB carriers.

• MSOs leverage their vast infrastructure to deploy a wide range of multimedia service offerings.

• Local telephone service providers also compete in the VoBB market using DSL, which supports high-speed Internet over existing copper lines.

• Alternative VoBB carriers offer voice services over cable and DSL networks; as VoBB is based on IP, these voice calls are simply more data running on the network.

VoBB solution

There are two key technologies to enable VoBB in the IP network:

• DHCP-managed IP session for the VoIP subscriber• VoIP over Ethernet over B-PDU in the ADSL copper loop

Routing voice packets over a telco’s private IP network ensures a superior reliability and QoS compared to other providers.

7670 RSP benefits for VoIP

The 7670 RSP VoIP offering guarantees carriers the same reliability and QoS of voice services as PSTN service. Figure 22 illustrates a VoIP architecture using the 7670 RSP.

Figure 22: VoIP using the 7670 RSP

7670RSP

IP/MPLS/ATM

Backbone

DHCPServer

OSPF or IS-IS

adjacency

DSL

DSLAMsSIP

Phone

SIPServer

PSTN

Gateway

18066


38

Table 4 outlines the key features offered with the 7670 RSP VoIP solution.

Table 4: Key features offered with the 7670 RSP VoIP solution

Video services using existing DSL and multiservice IP networksDSL services have achieved a high rate of customer penetration due to demand for broadband services. Service providers who are already using Alcatel-Lucent broadband and multiservice networks to deploy high-speed Internet services can now leverage that infrastructure to offer value-added video services (broadcast video and VoD). By combining video with VoIP and high-speed Internet access, service providers can create a bundled service offering referred to as “triple-play”, a competitive offering that leverages the service providers’ existing investment.

Deployment of the 7670 RSP for video services

The Alcatel-Lucent multiservice IP solution is based on the 7670 RSP and the Alcatel-Lucent network management portfolio. The products provide a flexible platform on which service providers can base their video offering. They support both IP and ATM multicast options for broadcast video and provide an IP-enabled, dedicated virtual connection for VoD in a multiservice environment.

Feature Benefits

Non-stop routing and MPLS signaling Eliminate outage due to control card failure and software upgrade

Zero-second network reconvergence and no service hit to voice services

99.999% reliability of voice services over a carrier-grade IP network

Rapid IP routing convergence Minimize impact due to third-party router and transport network failures

High ratio of prefix/s for BGP routes

High ratio of prefix/s for IGP routes

Rapid LSP recovery Minimize impact due to third-party router and transport network failures

Parallel link, end-to-end protection, FRR

IP interface scalability Supports 100 000 IP interfaces (subscribers)

IP traffic management Hierarchical queuing and shaping capability providing flexible guaranteed QoS for VoIP packets among other service classes

Non-service-affecting software upgrade

No service impact during software upgrade between minor releases


39

The 7670 RSP enables service providers to use existing and new ADSL DSLAMs to offer next-generation, triple-play services.

The 7670 RSP can be used for video backhaul with either Layer 2 or Layer 3 technology. In Layer 2 networks, it supports point-to-multipoint video content replication from a head-end to a regional or local office with a point-to-multipoint ATM VC cross-connect configuration. In Layer 3 networks, it supports IP dynamic multicast streaming with PIM-SM, PIM-SSM, or static multicast and IGMP routing protocols.

The 7670 RSP can support multimedia services as a DSLAM aggregator. The 7670 RSP line cards have the ability to replicate a single stream to create multiple streams.

Broadcast video architecture

Multicasting enables channels to be replicated within the network. Multicasting conserves bandwidth because each DSLAM does not have to be supplied with a unique video stream from the head-end. To optimize bandwidth, the video channel is carried to the furthest replicating point in the network, either a DSLAM or a 7670 RSP.

The 7670 RSP supports both IP and ATM multicast capabilities. The same inherent fabric multicasting capabilities are used, providing similar benefits to both models. Common implementation attributes include:

• efficient mechanism for multicast video streams• platform is designed for efficient (no bandwidth degradation) multicasting,

and logical multicasting is done across the fabric• APS: guaranteed switchover occurs in 50 ms• no need to pair nodes for redundancy: high-reliability design (APS and hot

redundant line cards, I/O card, and control card) ensures 99.999% uptime

IP multicast model

In the IP multicast model for broadcast video, the multicast trees are IP-based using PIM-SM or PIM-SSM for replication. Optionally, static multicast can be used.

A channel is propagated downstream from the head-end once an IGMP request for that channel (multicast group) has been generated by an end user. An IGMP join command generated by an end user propagates upstream along the connecting nodes in the network. Each node along the path independently verifies that the group is already present at its location. If the group exists, a “leaf” is replicated toward the downstream node that has requested the group; otherwise, the IGMP message is propagated upstream. In order to ensure fast zapping, all the groups must be statically provisioned to the furthest element in the network, thus localizing the IGMP message on the 7670 RSP or DSLAM.


40

Multicast traffic can be assigned a specific CoS in the backbone, enabling differentiation from other traffic types and thus ensuring that video quality is maintained. Distinct services (such as high-speed Internet or gaming) can be assigned different CoSs to ensure separation between the services and to meet varying requirements for delay and loss. Figure 23 illustrates the IP multicast model.

Figure 23: IP-based multicasting for broadcast video

The 7670 RSP provides several advantages that are unique to its IP multicast implementation:

• minimized loss and jitter IP multicast video streams carried over the 7670 RSP can be mapped to a CoS that ensures delay and loss ratios comparable to those of ATM.

• service continuity The 7670 RSP enables carriers to continue provisioning high-speed Internet using ATM cross-connects to a BRAS while at the same time offering video and VoIP over other VCs that terminate and are routed on the 7670 RSP. Service isolation is ensured through sophisticated traffic management.

7670 RSP

IP/MPLS Network(PIM-SM or PIM-SSM)

7670 RSP 7670 RSP

Modem

DSLAM DSLAM

IGMPIGMP

IGMP IGMP

DSLAMDSLAM

Modem

18048


41

• versatile MR48 card The 7670 RSP enables carriers to provision both ATM VCs (cross-connects) and IP-terminated VCs on a common line card. Extensive IP functionality, multifield classification, three-color two-rate policing, access lists, reverse path filtering, and IP buffer management are also provided. The card also supports APS and line card redundancy for unprecedented functionality and robustness. See the section “Line cards and I/O cards” in chapter 6 for more details on the MR48 card.

• support for both ATM- and Ethernet-attached DSLAMs The 7670 RSP can be connected to both an ATM aggregation network and Ethernet metro network with the Gigabit Ethernet line card. See the section “Line cards and I/O cards” in chapter 6 for more details on the Gigabit Ethernet card.

ATM multicast model

In the ATM-based model for video broadcast, a point-to-multipoint ATM VC is established for each broadcast channel, connecting the video source to all of the DSLAMs. The set-top box in the end user’s home uses an IGMP message to perform channel selection. The DSLAM terminates the IGMP message, directing a new multicast channel toward the end user’s set-top box. By localizing the IGMP message to the DSLAM, channel switching time (zapping) is minimized.

This solution provides for a robust, scalable architecture that minimizes bandwidth consumption in the backbone through the use of ATM multicast connections. In addition, the solution capitalizes on ATM’s inherent QoS capabilities to ensure that the quality of the video stream is maintained at all times. The platform’s OAM manageability enables operators to detect and diagnose problems in real time. Figure 24 illustrates the ATM multicast model.


42

Figure 24: ATM-based multicasting for broadcast video

The 7670 RSP provides several advantages that are unique to its ATM multicast implementation:

• minimized loss and jitter Loss and jitter are minimized through the use of constant bit rate (CBR) or real-time variable bit rate (rt-VBR). This meets ATM UNI4.1 specification for traffic management for ATM, which assigns delay tolerance and cell loss ratio to these specific service categories.

• pre-provisioning a multicast tree as far as the 7670 RSPIf the DSLAMs do not support IGMP termination, then the 7670 RSP roadmap provides an option to perform IGMP joins. IGMP messages from DSL modems terminate on the 7670 RSP, which replicates the video stream towards the DSLAM on a per-user basis.

• supported VLAN-based leaf in order to interconnect with an Ethernet-based aggregation network

Video on demand architecture

VoD is a high-value service that can command as much as 100 times the price per bit of broadcast video. In this model, individual end users request specific video streams associated with the content they want to view at a particular time. As a result, all video streams are unicast, making the application highly bandwidth-intensive. Assuming that a video stream is 1.5 Mb/s (with MPEG-4 compression), 413 VoD sessions can consume an OC12/STM4 connection. In broadcast video, the video source is centralized and multicasting can be used to efficiently distribute content to customers. With the high bandwidth requirements and unicast nature of VoD, a centralized model does not scale

7670 RSP

ATM Network

7670 RSP 7670 RSP

Modem

DSLAM DSLAM

IGMPIGMP

DSLAMDSLAM

Modem

18049


43

efficiently; connecting all customers to a single video server would cause a bottleneck. Instead, a distributed model in which multiple video content servers are deployed across a service provider infrastructure is viewed as the model moving forward. Figure 25 illustrates the VoD architecture.

Figure 25: VoD

The VoD application typically involves a three-step communication.

• The set-top box IP address is initialized through a DHCP request originated by the set-top box and relayed by a DHCP relay agent to a centralized DHCP server (the 7670 RSP can act as a DHCP relay agent). The DHCP server, which can be used to assign IP addresses for multiple services in a service bundle, responds with the IP address.

• The set-top box downloads middleware software that enables it to view the video content on the VoD server.

• Once a video stream is selected, an IP unicast video session is established between the set-top box and the VoD server. That session carries the movie or other event that the user has chosen to view.

Figure 26 illustrates an application of VoD with the 7670 RSP.

7670RSP

VoDContentServer

IP/MPLS/ATM

Backbone

DHCPServer

DHCPRequest/Response

OSPF or IS-ISPeering

DSL

STB

DSLAMs

Unicast Video Stream

18064


44

Figure 26: VoD application

The 7670 RSP provides several key benefits for the VoD application:

• leverages the 7670 RSP investment In most service provider networks, the 7670 RSP is located close to the DSLAMs, which is the ideal location from which to provide VoD transport. The alternative, deploying large numbers of BRASs next to DSLAMs, is costly and does not leverage existing investments.

• maintains existing service models VoD services can be enabled through the use of MR48 cards connected to the DSLAMs, while other services (high-speed Internet, broadcast video) can remain on the existing ATM architecture, if desired. The VoD service can have a dedicated virtual connection that is IP-enabled on the 7670 RSP. The terminating VC can be configured with all the attributes of a Layer 3 interface.

• supports centralized model for smaller networks In POPs where the number of DSL users does not justify collocation of a VoD server, customer VoD interfaces can be backhauled using ATM cross-connects to an MR48 card at the nearest VoD server site. Many connections can be backhauled from many 7670 RSPs to a single video server.

• supports native IPThe 7670 RSP enables operators to transform their networks into ubiquitous IP networks for value-added services such as VoD. The 7670 RSP also supports extensive MPLS capabilities. LDP-DU, LDP-DoD, CR-LDP, and RSVP-TE are supported, enabling carriers to engineer the traffic on their networks and provide fast restoration using RSVP-TE LSPs as bypass tunnels.

• supports non-stop routing and signaling The 7670 RSP enables operators to provide robust and highly available VoD services with confidence based on enhanced redundancy ensuring 99.999% availability.

7670 RSP

IP/MPLS Network(PIM-SM orPIM-SSM)

7670 RSPDSLAM

Modem

VoD ContentServer

DHCPServer

DHCP Request/Response

DHCPRelay

Unicast Video Stream

18050


45

VoP using multiservice IP networksThe VoP application enables both voice and signaling information to be transported over a packet network. This enables service providers to take advantage of the flexibility and efficiency of packet networks. It also reduces costs for the service providers by consolidating voice and data on one network.

As legacy PSTN switches are in maintenance mode in their life cycle, carriers look for alternate technology to continue to support the high volume and revenues of the PSTN service while they are getting ready for network convergence.

The main challenge t hat the VoP solution must meet in order to gain widespread customer acceptance is to provide the same reliability and QoS as the traditional PSTN service.

There are three types of VoP service:

• Class 4: toll office displacement• Class 5: end office displacement• Voice over broadband (see “Voice over broadband” earlier in this chapter)

Class 4: toll office displacement

Alcatel-Lucent’s Class 4 solution (see Figure 27) enables service providers to deploy new packet-based, long distance voice networks and use these at the same time to offer data services, or to migrate existing long distance voice traffic from the PSTN onto already existing packet-based data networks.

The NGN Class 4 solution applies to different types of service providers:

• established and backbone service providers who are facing the challenge of how to handle the traffic growth at toll level and how to anticipate the future—migrating voice traffic from aging transit/tandem TDM switches onto a common voice and data packet-based infrastructure

• service providers expanding outside their home market who face the challenge of deploying a Class 4 infrastructure fast, with a limited footprint to compete with the local established and backbone service providers


46

Figure 27: Class 4: toll office displacement

The Class 4 over IP backbone solutions apply to the following applications:

• long distance VoIP• voice trunking over IP• Class 4 cap and grow• toll/Class 4/transit bypass• Class 4 replacement• PSTN/ISDN offload

While the NGN solution is based on ITU-T H.248, the core network can be ATM-based or IP/MPLS-based.

ATM network requirements

The NGN Class 4 solution is based on the following ATM network requirements:

• support of ATM SVC — UNI signaling and PNNI• high SVC call setup rate• hot redundant protection for SVC to offer 99.999% reliability• ATM traffic management to support real-time CoS

7670 RSPmultiservice IP network

Class 5

H.248 H.248

MediaGateway

MediaGateway

MediaGateway

Class 5

MGController

PNNI PNNI

T1T1

SS7SS7

18063


47

IP/MPLS network requirements

The NGN Class 4 solution is based on the following IP/MPLS network requirements:

• non-stop routing• non-stop signaling• IP traffic management

Class 5: end office displacement

The NGN Class 5 solution (see Figure 28) offers service providers a valuable alternative to the traditional method of constructing a voice network. Rather than employing TDM technology, the solution uses the service provider's existing packet-oriented transport networks to create a unified next-generation data infrastructure. On this infrastructure, operators can deliver revenue-generating voice services.

The NGN Class 5 solution supports both local and long distance telephony services on a single softswitch platform. This platform uses the standard ITU-T H.248 protocol to control the trunking of access and residential gateways. The NGN Class 5 solution can work in a VoIP or VoATM configuration and can also be deployed in both ETSI and ANSI markets.

Figure 28: Class 5: end office displacement

IP/MPLS network requirements

The NGN class 5 solution is based on the following IP/MPLS network requirements:

• non-stop routing and MPLS to provide non-stop service in order to meet regulatory requirements

• IP VPN to segregate routing of signaling packets and voice packets• first class traffic management to guarantee low network latency and minimal

jitter to simulate PSTN performance

PSTN

TrunkGateway

VoiceoverTDM

7670 RSPIP/MPLSNetwork

AccessGateway

AccessGateway

Softswitch

SS7

18053


48

49

ATM on the 7670 RSP

This chapter addresses the ATM functionality of the 7670 RSP, including:

• “ATM switching architecture”• “Cross-connections”• “IMA”• “ILMI 4.0”• “PNNI routing”• “Standardized AINI support”• “Connection resource display”• “OAM PM”• “Traffic management capabilities”

4. ATM on the 7670 RSP

50

ATM switching architectureIn a single-shelf system, the switching function is performed by two Switch cards: one for switching fabric X and one for switching fabric Y. A single Switch card provides the switching fabric needed for all line cards. The second Switch card provides switching fabric redundancy. Each switching fabric receives cells from all the line cards and sends cells to destination line cards.

In a multishelf system, the switching function is performed by two dedicated Switching shelves: one for switching fabric X and one for switching fabric Y. The use of two Switching shelves guarantees full redundancy in the same manner as the use of two Switch cards in a single-shelf system. Each switching fabric in the Switching shelf receives cells from all the line cards and sends cells to all the line cards.

In both single-shelf and multishelf systems, the redundant fabric provides 100% capacity protection. There is no loss in switched capacity in a core-fabric activity switch.

The egress line cards examine the header of each cell at the egress point of the switching fabric, select cells based on the cross-connection information in the header, remove the header, and send the cells to their I/O cards. The I/O cards transmit the cells over the appropriate interface to the network.

Cross-connectionsAn ATM virtual connection provides the information needed for the 7670 RSP to establish a cross-connection between an ingress point and an egress point on the node. There are three types of VCs:

• PVCs• SVCs• SPVCs

PVCs

A PVC is an ATM virtual connection set up by an operator. The operator sets up the PVC through a network management system or through a CLI session at each device along the PVC. The 7670 RSP supports point-to-point and point-to-multipoint PVCs at the VP and VC levels.


51

Hitless modification of active PVC connections

This feature enables the change of traffic rates on an active connection without interrupting data flow on the line card. The following point-to-point PVC and signaling link traffic parameters can be modified while the connection is in service, without incurring cell loss:

• PIR• SIR• MBS• MIR• CDVT

SVCs

An SVC is an ATM virtual connection, set up automatically by the ATM devices in response to information sent by the originating device over an SVC infrastructure that exists between all the devices. The SVC infrastructure includes path determination (routing) and signaling to establish the connection.

The 7670 RSP supports static and PNNI routing, ILMI links, signaling links, call processing, SVC accounting, and usage records for point-to-point and point-to-multipoint SVCs at the VP and VC levels. The following signaling protocols are supported:

• ATM Forum UNI 3.1 and 4.0• ATM Forum IISP 1.0• ATM Forum PNNI 1.1• AINI• ILMI 4.0

The 7670 RSP supports native ATM addresses and ITU-T E.164 and X.121 addresses encoded in an AESA.

SPVCs

An SPVC is an ATM virtual connection that combines the path’s endpoint characteristics of PVCs with the path’s network characteristics of SVCs. The path endpoints are configured by an operator. The path through the network is set up automatically by the switches in response to information sent over a PNNI infrastructure that exists between the supporting devices. The 7670 RSP supports static routing, PNNI routing, and signaling links for point-to-point and point-to-multipoint SPVCs at the VP and VC levels.

SPVCs provide easily provisioned, scalable, standards-compliant permanent virtual circuits in ATM networks. Because the control plane manages the node-by-node establishment and re-establishment of the connection through the network, interoperability between nodes from different vendors is easier to


52

achieve. Because connection management is performed by the nodes, SPVCs make it easier to initiate reroute and recovery actions in the event of a network failure.

Hitless SPVC moves using DBR

Domain-based rerouting (DBR) is used to move an SPVC without affecting service on the connection. DBR can optimize existing SPVCs and move SPVCs for maintenance.

A move is considered to be hitless when the data flow interruption is less than the Telcordia (formerly Bellcore) standard of 50 ms.

DBR offers the following benefits:

• ability to move SPVCs in the network when a network resource needs to be taken temporarily out of service

• ability to move SPVCs in the network when a particular resource nears its capacity

Network call correlation identifier

The network call correlation identifier (NCCI) is an optional 28-byte, AESA-based identifier that is used to identify a call uniquely within a network. The NCCI correlates SPVC cross-connections with SPVC paths without the use of enhanced signaling.

The NCCI offers the following benefits:

• ability to identify all SPVC and SVC connections on a given resource • ability to hitlessly move SPVC paths from a resource that is to be taken out of

service• ability to provide security similar to CUG security at an SPVC destination point• ability to use a signaled NCCI value for usage-based billing

Point-to-multipoint SPVCs

SPVCs can provide connection scalability and superior reroute performance in a network that requires multicast capabilities. Point-to-multipoint SPVCs behave identically to PVC-based point-to-multipoint connections, and these connections are managed similarly to point-to-point SPVC services.

Point-to-multipoint SPVCs offer the benefit of a seamless and efficient implementation of multicast services.

IMAInverse multiplexing over ATM (IMA) is a technique developed as a cost-effective solution to address the increasing need for bandwidth greater than the DS1/E1 link speed, but less than the high-speed DS3/E3 links. IMA combines the transport bandwidth of multiple DS1/E1 channels in a group to provide scalable bandwidth.


53

A DS1/E1 link that is part of an IMA group is referred to as an IMA link. Multiple IMA links (DS1/E1) form an IMA virtual link that is called an IMA group. The aggregate rate of the IMA group is approximately the sum of the DS1/E1 link rates.

IMA is supported on the ESC and is compliant with the ATM Forum specification, IMA version 1.1.

ILMI 4.0The 7670 RSP supports the mandatory aspects of the ATM Forum ILMI Specification Version 4.0, af-ilmi-0065.000, including virtual UNIs as described in Annex B of the specification. This feature gives customer premises equipment limited access to various management plane functions, such as registration of MAC addresses for LANE and visibility of PVC endpoint status to equipment that does not support OAM.

PNNI routingThe PNNI routing protocol organizes and distributes information about changing network topology and network resources among a group of associated nodes. The 7670 RSP conforms to ATM Forum PNNI version 1.1.

PNNI hierarchy

PNNI hierarchy is vital for network operators who are considering deploying PNNI in their networks. From the hierarchical topology information, network nodes create routing tables that switch SVC and SPVC calls using PNNI signaling. PNNI hierarchy enables the 7670 RSP to interoperate with other Alcatel-Lucent multiservice nodes and in mixed-vendor networks that use PNNI hierarchy.

By using PNNI hierarchy, network operators can scale their PNNI networks up to 2.3 million nodes. The 7670 RSP supports three levels of hierarchy.

PNNI topology database display

With PNNI topology database display, network operators can see a summary of the PNNI topology database information that has been learned by the PNNI protocol. The information in the database is flooded throughout the network to provide each node with details about the network topology so that they can route calls. Information contained in the topology database includes a list of the peer groups and the nodes contained within those peer groups, the PTSE information describing each logical node, the map information that forms the PNNI topology, and the reachable addresses advertised by each logical node.

Topology database display gives network operators a view of the network topology as seen from a single node, making it easier to understand the amount and content of the information being flooded through the network. Having this view makes it easier for network operators to debug and diagnose any


54

problems that may occur. Topology database display also provides in-house or third-party management systems with access to the network topology information needed to build applications to better manage the network.

PNNI restricted transit

PNNI restricted transit gives network operators control over whether calls can transit specific logical nodes in the PNNI network. With PNNI restricted transit, network operators can use a standards-based method of directing calls away from a node that may not have sufficient capacity to transit calls even though it can originate and terminate calls.

PNNI restricted transit reduces the complexity of network planning and improves network resiliency.

PNNI address summarization

PNNI address summarization makes it possible for network operators to deploy SVC or SPVC services with minimal manual configuration of summary addresses. Logical group nodes can automatically advertise reachable addresses to other logical nodes in their peer groups, based on information in their child peer groups. Lowest-level nodes can advertise their default summary addresses, and logical nodes are automatically configured with a summarizing address that is advertised when nodes in their child peer groups advertise their own default summary addresses.

Because PNNI address summarization reduces the configuration process, it enables rapid network expansion and simplifies the deployment of dynamic backbone networks.

PNNI routing support for exterior reachable addresses

Resource bandwidth information can be advertised for PNNI exterior reachable addresses. By advertising the available bandwidth resources, nodes can source calls to exclude destination nodes that cannot forward the call to an exterior reachable address. Exterior reachable address advertisements are withdrawn when the exterior reachable address becomes nonroutable.

PNNI routing support for exterior reachable addresses decreases the call setup delay and increases network efficiency, because PNNI routing directs calls toward exterior reachable addresses that satisfy bandwidth requirements, which reduces call blocking and alternate routing.


55

PNNI policy-based routing

ATM PNNI policy-based routing (PBR) gives network administrators control over the way connections are routed across a PNNI routing domain based on network-specific criteria and resource utilization strategies. Service providers accomplish this in two steps:

• by assigning Ne-NSC tags on trunk groups in the form of Ne-NSC IDs and assigning Rp-NSC tags on trunk group partitions in the form of Rp-NSC IDs. These tags are advertised throughout the PNNI network.

• by configuring policies and policy constraints that are signaled with calls during call establishment. The policy constraints are used by PNNI routing to find paths that support the policy constraints for the call.

PBR is applied to network traffic in three steps:

• network resources are tagged and advertised using PNNI• policies and policy constraints are defined • policy constraints are assigned to SPVC and SPVC subscribers for

differentiated path selection using the policies defined in the network

Policy-based routing on the 7670 RSP enables advanced routing policy with SPVC-based and SVC-based services as well as the following applications:

• routing over untagged resources• VBNs• SPVC versus SVC bandwidth partitioning• link differentiation (for example, require APS, avoid satellite links,

require/avoid ATM/MPLS mediation)• SVCC-based RCC establishment using policy routing

Standardized AINI supportThe 7670 RSP is fully compliant with the ATM internetwork interface (AINI) standard of the ATM Forum, as specified in af-cs-0125.000. This feature makes the 7670 RSP interoperable with AINI-based networks and environments of other vendors.

AINI link loop detection

The AINI protocol acts as a gateway protocol between PNNI and SS7 or B-ISUP networks, and between PNNI networks. AINI is a combination of B-ISUP routing and PNNI signaling.

AINI link loop detection is a modification to the protocol that prevents loops in the setup of SVCCs, SVPCs, SPVCCs, and SPVPCs.

AINI link loop detection offers the benefit of providing broader interoperability with third-party vendor equipment.


56

Connection resource displayConnection resource display is a means of monitoring the use of connection resources in a network. Monitoring the use of the connection resources on the 7670 RSP enables operators to manage high use of resources through network planning or path optimization, and to review call failures that occur due to lack of resources.

OAM PMOAM performance management tracks connectivity and monitors traffic flow on an end-to-end connection or a connection segment. Measurements of connection performance are based on the number of errored or lost cells.

OAM PM offers the benefit of measuring connection performance in a network and monitoring performance degradation with the 7670 RSP.

OAM round-trip delay

Round-trip delay is a test that measures the time it takes for a standard OAM loopback cell to travel from a launch point in the network to a return point in the network and back. The round-trip delay test can be performed while the network is in service. Round-trip delay can be measured on Multi-Rate 8 ATM/IP, Multi-Rate16 ATM, and MR48 line cards.

The OAM round-trip delay test offers the benefit of measuring performance in the network.

Traffic management capabilitiesThe 7670 RSP uses industry-leading traffic management processes to ensure maximum efficiency and bandwidth use. The advanced traffic management capabilities of the 7670 RSP provide absolute QoS for all service categories.

Traffic management is part of the traffic flow architecture of the 7670 RSP. The ingress line cards use traffic management before passing traffic to the switching fabric. The egress line cards use traffic management after receiving traffic from the switching fabric. The ingress line cards effectively manage traffic by using backpressure information from the fabric and the egress line cards.

With virtual queuing, the 7670 RSP can resolve traffic congestion at isolated points within the switch while continuing to process traffic from noncongested points.


57

The major components of traffic management are:

• network congestion management• service categories• QoS parameters• CAC• traffic policing and shaping• congestion control• VP aggregation shaping• ATM call failure diagnostics

Network congestion management

Traffic management processes prevent network congestion on shared network devices and transmission links. Network congestion created by some traffic can cause other traffic to experience unacceptable loss or delays. Traffic management guarantees a QoS level and fairness for all connections. The 7670 RSP uses ATM traffic management for IP over ATM virtual connections and for ATM virtual connections at the ingress and egress points of the node.

ATM traffic management of virtual connections:

• monitors and controls traffic flow• ensures an appropriate and fair allocation of resources• handles traffic that exceeds the configured limits

Service categories

Service categories ensure an appropriate and fair allocation of resources by providing the means to determine the priority that a connection receives when requesting network bandwidth. The 7670 RSP supports the TM 4.0 standard, which identifies five service categories, each optimized for a different type of traffic. The 7670 RSP uses the service category assigned to the connection when it sets up the connection. This process ensures that each connection receives the resources appropriate for its traffic. See Table 37 in Appendix B for a list of the service categories and their characteristics.

QoS parameters

QoS is a set of parameters and their values that determine the performance of a connection. QoS parameters allow further service differentiation in each service category. The QoS parameters supported by the 7670 RSP are:

• CLR• CDV• CTD

The 7670 RSP supports configuration of the PIR, SIR, and MIR traffic descriptors.


58

The 7670 RSP supports a configurable MBS. The larger the MBS value, the less concentrated the SIR traffic policing. MBS is used for CAC and traffic policing functions.

CAC

Connection admission control (CAC) is an algorithm that evaluates whether the 7670 RSP can accept a new connection without affecting the service objectives of existing connections.

CAC examines the shared resources of the 7670 RSP, such as the number of existing virtual connections, available bandwidth, and available buffers. CAC also examines the resource requirements of the proposed connection. The proposed connection is accepted by CAC if the 7670 RSP has the resources to accommodate it and its projected requirements without hindering QoS guarantees for existing connections.

Disabling capacity checking or increasing the booking factor allows CAC to be configured to accept proposed connections that would otherwise not be admitted. The booking factor is a value that determines the degree to which CAC accepts or rejects proposed connections.

Traffic policing and shaping

Traffic policing ensures that the traffic on a virtual connection conforms to its traffic contract. The 7670 RSP accepts conforming cells and discards or tags nonconforming cells. Tagged cells have a lower priority than accepted cells and may be discarded in the event of congestion.

Traffic shaping ensures that traffic exceeding the configured traffic policing rates is shaped so that it conforms to the traffic policing parameters for that connection. Traffic shaping is performed according to the traffic descriptors. At ingress points, shaping can allow the 7670 RSP to accept nearly compliant traffic as compliant instead of discarding it. At egress points, shaping allows strict control of CDV.

Congestion control

Congestion control in the 7670 RSP reduces inefficient throughput caused by traffic congestion. The payload of an IP packet is often segmented into many ATM cells. During periods of congestion, some cells can be discarded, resulting in an incomplete IP packet at the destination and causing the destination to request the source to resend the entire packet.

The 7670 RSP uses PPD or EPD to reduce congestion throughput inefficiency.

VP aggregation shaping

VP aggregation shaping is a commissioning capability that aggregates the traffic of multiple VCs onto the same VP and shapes the aggregated traffic on the egress port of a line card to a particular VP traffic descriptor.


59

With VP aggregation shaping, service providers can aggregate multiple VCs with different QoS onto the same VP while maintaining the QoS requirements for individual VCs. By shaping a single VP rather than many VCs, VP aggregation:

• simplifies cross-connections through the network core• allows scaling of a network• increases network rerouting• allows more stringent SLAs to be offered

The 7670 RSP supports VP aggregation shaping on PVCs, SVCs, and SPVCs. VP aggregation shaping can be performed on point-to-point and point-to-multipoint connections.

ATM call failure diagnostics

The ATM call failure diagnostics include the following capabilities:

• detailed information logging about a failed call, including information to determine the cause of the failure

• creation of a source node failure log in addition to the failure log created on the node where the failure occurred

• duplicate log detection• filters to determine which types of call failures are logged and/or displayed

The ATM call failure diagnostics on the 7670 RSP offer the benefit of improved logging functionality and diagnostics for switched services.


60

61

IP/MPLS on the 7670 RSP

This chapter describes the IP/MPLS features of the 7670 RSP:

• “MPLS overview”• “S-LSPs”• “MPLS signaling protocols”• “S-LSP path modification without break”• “S-LSP tunnels”• “S-LSP protection”• “MPLS OAM”• “IP data plane”• “IP routing support”• “IP multicast”• “IPv6”• “IP VPNs (Layer 3 VPNs)”• “Pseudowires”

5. IP/MPLS on the 7670 RSP

62

The 7670 RSP supports both native IP forwarding and MPLS. The platform is designed to perform simultaneous full line-rate IP forwarding and label switching at all ports, with CoS, access lists, and other features applied. By separating its routing and forwarding functions, the 7670 RSP leverages its data- and control-plane architecture to provide more robust forwarding. By combining its expertise in carrier-grade switching with state-of-the-art IP routing technologies, Alcatel-Lucent has created the ultimate, multiservice-based MPLS solution for next-generation networks.

MPLS overviewMPLS brings much-needed network and traffic engineering capabilities to the connectionless, hop-by-hop routing approach used in large-scale IP networks. These traffic engineering capabilities allow service providers to meet the demand for premium IP services.

MPLS defines labels associated with IP forwarding properties and the signaling mechanisms used to assign them. The protocol results in switched IP paths called LSPs. LSPs can be viewed as the connection through which traffic passes. The 7670 RSP supports P-LSPs (provisioned) and S-LSPs (signaled). P-LSPs are unidirectional, static LSPs established by cross-connections at each end of the node. S-LSPs are dynamic LSPs established by a signaling protocol. Once traffic is mapped onto an LSP, MPLS forwards label-encapsulated IP packets along the predefined path by means of label swapping. The 7670 RSP looks up the packet’s input port and incoming label and swaps them for the outgoing port and outgoing label. The 7670 RSP examines only the label—the MPLS payload is ignored. The granularity of control in the form of a path lends itself to traffic engineering for optimizing network use, enhancing scalability of the IP network, and reducing operational complexity.

7670 RSP as an LER

LERs are deployed at the edge of an MPLS network and are capable of routing and forwarding labeled packets. The 7670 RSP can function as an LER, setting up network paths that follow specific topological routes or defined constraints, such as resource availability and explicit routes.

As an LER, the 7670 RSP participates in Layer 3 routing, communicating with edge routers receiving native IP packets, and labeling and unlabeling packets at the edge of the MPLS domain.

The 7670 RSP supports LER functionality on all IP forwarding-capable line cards. The Multi-Rate 8 ATM/IP, Multi-Rate 16 POS, Gigabit Ethernet, and Multi-Rate 48 Channelized Multi-Protocol line cards support IP forwarding.

7670 RSP as an LSR

LSRs are deployed at the core of an MPLS network and are capable of forwarding labeled packets. The 7670 RSP can function as a high-performance LSR with QoS, across both ATM and IP interfaces.


63

As an LSR, the 7670 RSP participates in the IP routing control plane and becomes a true IP routing peer, transforming the IP network from a transparent overlay into a converged Layer 2 and Layer 3 network.

The 7670 RSP supports LSR functions at OC3/STM1, OC12/STM4, OC48/STM16, and Gigabit Ethernet line rates.

Figure 29 shows the 7670 RSP deployed as both an LER and an LSR.

Figure 29: 7670 RSP as an LER and an LSR

Filters

With MPLS, the 7670 RSP gives service providers rich functionality to fully control and engineer their IP networks. By providing the ability to specify the route that traffic will follow through a network, MPLS allows service providers to use traffic filters to reserve resources for an LSP and define the class of service that traffic is accorded on the LSP. Traffic filters are applied to all packets entering the network.

LSP tunnels

An LSP tunnel gives service providers a flexible way of carrying IP traffic over MPLS. The tunnel is an LSP that is set up without explicit IP destination address information in the signaling protocol. The traffic that flows along the tunnel is selected by the LSP’s ingress node according to network operator specifications. Any LSP can be a tunnel. Service providers can use LSP tunnels to create the following:

• an IGP shortcut, which is a virtual link to a target router• a BGP-4 shortcut, which is a virtual link to a target border router• a CoS-filtered LSP, in which the LSP carries only packets with a certain set of

DSCP values• IP VPN• Layer 2 pseudowires

7670 RSPNode B

LSR

7670 RSPNode A

LER

7670 RSPNode C

LER

Router Router

Label IP packet Label IP packetIP packet IP packet

MPLS network

18056


64

Multiple parallel LSPs

Service providers can use multiple parallel LSPs to meet different service requirements. Multiple parallel LSPs allow IP packets going to the same IP destination prefix to travel on LSPs with different QoS and different routes. These can be a combination of S-LSPs and P-LSPs. Traffic on multiple parallel LSPs is classified based on a preconfigured CoS that is DSCP-based or on VRF policy.

Prefix-based filters

All IP traffic associated with a destination IP address prefix that matches a filter prefix is placed on the LSP carrying the filter. A CoS can be applied to the filter.

S-LSPsS-LSPs are dynamic LSPs that are established using either the RSVP-TE or the LDP signaling protocol. The 7670 RSP implements the following on S-LSPs:

• FEC match criteria for IP address prefixes• generic or explicitly routed LSPs, with either best-effort service or QoS• path rerouting upon link failure

The 7670 RSP supports the creation and transit of RSVP-TE, CR-LDP, LDP-DU, and LDP-DoD S-LSPs, allowing the 7670 RSP to act as an LSR (P router in an IP VPN) or as an LER (PE router in an IP VPN).

While S-LSPs are dynamically routed by default, they can be configured to use static routes. The 7670 RSP supports static primary routes and static alternate source routes. The platform also supports dynamic primary routes and static alternate routes. Primary/alternate route information is part of end-to-end protection.

LER support with CR-LDP/LDP-DoD

S-LSPs can now be explicitly configured to use the CR-LDP or LDP-DoD signaling protocols. LDP-DoD is used to set up an S-LSP with no mechanisms for specifying path and resource constraints for the S-LSP. CR-LDP is an extension of LDP-DoD that supports mechanisms for specifying path and resource constraints for the S-LSP. CR-LDP uses the downstream on demand (DoD) label distribution method and behaves in much the same way as RSVP-TE.

CR-LDP along with RSVP-TE offer the benefit of enabling a IP VPN over an LSP with the ability to specify path and resource constraints for the LSP.


65

MPLS signaling protocolsThe 7670 RSP supports a wide range of signaling protocols:

• RSVP-TE• LDP-DU• LDP-DoD• CR-LDP• static

If RSVP-TE is used as the signaling protocol for an MPLS signaling link, the LSPs used to transport packets between routers must be explicitly configured. Bandwidth can be assigned to the LSP, and QoS and traffic engineering parameters can be applied.

The 7670 RSP implements the following RSVP-TE functionality:

• non-stop MPLS with hot redundant signaling link protection• strict and loose explicit routing• LSP setup with bandwidth reservation, QoS, and best-effort service• support of record route object• CSPF at LER

The 7670 RSP also supports the LDP signaling protocol, which allows two LSRs to agree on the labels to be applied to packets forwarded between them. The LDP protocol supports the downstream unsolicited (LDP-DU) and downstream on demand (LDP-DoD) label advertisement modes.

If LDP-DU is used as the signaling protocol for an MPLS signaling link, the LSPs used for the transport of packets between routers are determined based on the information exchanged over the set of BGP peering sessions configured between routers. Once LDP-DU signaling links are established through the MPLS core of the provider network, no additional configuration is required to create the LDP tunnels.

Signaling link types

The 7670 RSP supports generic label signaling links and LC-ATM signaling links. Cell relay, POS, and Gigabit Ethernet cards support generic label signaling links. Only cell relay cards support LC-ATM signaling links.

Graceful restart for LDP

LDP graceful restart for planned and unplanned outages eliminates loss of MPLS traffic caused by an LSR or LER control plane restart.

The 7670 RSP preserves the MPLS forwarding component across the restart and preserves a requesting neighbor’s forwarding component across a restart if the neighbor also supports graceful restart. The functions are supported for both planned and unplanned outages. Preserving a neighbor’s forwarding component enables the 7670 RSP to help that neighbor recover from an LDP


66

restart. During a control plane restart, the 7670 RSP continues to forward traffic for regular LSPs or for Layer 2 VPNs or IP VPNs using LDP-DU as an outer tunnel.

LDP graceful restart offers the benefit of providing improved MPLS/LSP reliability to IP VPNs and pseudowire-based Layer 2 VPNs.

Parallel links

Parallel links allow labels for generic-label interfaces to be managed on a single signaling link. When multiple adjacencies exist between directly connected peers, traffic may be moved from one to the other if an interface fails.

If a failure is detected, new interfaces are selected to carry the S-LSPs originally carried on the failed interface. The selection is identical to the selection that is performed when the S-LSP is originally established. If the S-LSP cannot be moved to a parallel adjacency, it is resignaled on a parallel signaling link if one exists. If no other path exists, the failure propagates upstream.

S-LSP path modification without breakS-LSPs that use the RSVP-TE signaling protocol support path modification without break functionality, allowing service providers to make changes to an S-LSP’s configuration without interrupting traffic. When an S-LSP’s configuration changes, the original path remains connected until the path with the changed configuration is connected. When the new path is connected, traffic is switched and the old path is deleted.

S-LSP tunnelsThe 7670 RSP supports a hierarchy of labeled traffic by sending MPLS labeled traffic through an outer S-LSP acting as a tunnel. The S-LSP is tunneled inside the outer S-LSP by adding the outer S-LSP label on top of the existing label. S-LSP hierarchy supports Layer 2 VPNs, IP VPNs, and bypass tunnels.

Outer S-LSPs can be unconstrained tunnels or constrained tunnels (TE-tunnels). Any RSVP-TE, CR-LDP, LDP-DoD, or LDP-DU LSP is automatically an unconstrained tunnel when it is created.

An RSVP-TE LSP or CR-LDP LSP can be configured as a Layer 3 interface. This configuration allows reservable bandwidth and an administrative group to be specified for the tunnel. All other Layer 3 interface characteristics are defined by the LSP.

Layer 2 VPNs can select an RSVP-TE, CR-LDP, LDP-DoD, or LDP-DU LSP as an outer tunnel. The tunnel must terminate on the correct router as identified by the router ID, and it must match the CoS configured for the pseudowire.


67

Layer 3 VPNs can select an RSVP-TE, CR-LDP, LDP-DoD, or LDP-DU LSP as an outer tunnel, as long as the tunnel terminates on the correct router as identified by the router ID.

S-LSP protectionPath protection improves the reliability of packet transfers in MPLS-based networks, without requiring complete hardware redundancy. On the 7670 RSP, path protection is applied to each S-LSP individually and is provided through fault detection, end-to-end protection, and fast reroute.

Fault detection

When an S-LSP fails at a lower level (for example, the physical layer), that level attempts to repair the problem. If the problem cannot be handled at the lower level, the failure is propagated to the MPLS layer, and S-LSP protection is activated.

In addition to failures detected by MPLS, LDP detects failures of directly connected adjacent nodes using the Hello protocol. An adjacency is considered down if it does not receive a Hello message within 15 seconds.

The RSVP-TE protocol detects local interface failures when the port fails.

Failures detected at destination and transit nodes are propagated to the original node upstream using the signaling path.

End-to-end protection

End-to-end protection is applied to an entire S-LSP from source to destination. End-to-end protection is implemented when an alternate route is configured for an S-LSP, and it is activated when a failure is detected at or propagated to the S-LSP’s source node.

The 7670 RSP supports end-to-end protection on S-LSPs that use the RSVP-TE or CR-LDP protocol. S-LSPs can be configured for hot standby or cold standby. When an S-LSP is configured for hot standby, an alternate route is pre-established parallel to the primary route.When an S-LSP is configured for cold standby, an alternate route is configured but is not established until the primary route fails.

Reversion

The 7670 RSP supports automatic or manual reversion. With automatic reversion, traffic is automatically restored to the primary route when it has been re-established. With manual reversion, the traffic remains on the alternate route until it is manually restored to the primary route. Manual reversion gives operators the option of keeping traffic on an alternate route until it is certain that the primary route is stable.


68

Fast reroute

Fast reroute allows traffic to be moved onto a different path at a transit node of an S-LSP. Since traffic is being rerouted from a point close to the failure, recovery times are faster. A fast reroute of an S-LSP can be performed using a bypass tunnel or a detour LSP. Bypass tunnels are a 1:N protection mechanism in which many LSPs are protected by a tunnel. Detour LSPs are a 1:1 protection mechanism suited for networks with a small number of LSPs, diverse bandwith reservation, or diverse LSP routing. Fast reroute is supported on S-LSPs that use the RSVP-TE protocol.

MPLS OAMThe following MPLS OAM diagnostic and troubleshooting tools are used to monitor LSPs and isolate faults when an LSP fails to deliver user traffic:

• MPLS LSP ping• MPLS LSP traceroute• pseudowire VCCV (for further information, see the “Pseudowire VCCV”

subsection in this chapter)

MPLS ping tests the integrity of the LSP connection, using MPLS echo requests and echo replies to validate LSP connectivity.

MPLS traceroute provides fault localization and LSP path tracing, leveraging MPLS ping along with manipulation of the time-to-live (TTL) field in the IP packet header, to identify each MPLS router in the path taken by the LSP.

Both of these features provide simple and efficient mechanisms to detect LSP data plane failures and isolate faults in an MPLS network. They also mirror functionality for IP network troubleshooting.

IP data planeThe 7670 RSP IP data plane supports:

• IP forwarding with differentiated service (Diffserv)• ICMP• IP CoS with hierarchical shaping• packet filtering using access lists and rate limiting• reverse path filtering• admission control• DHCP relay

IP forwarding

With IP forwarding, IP packets received at one interface are forwarded to another interface based on the packet’s destination IP address and the IP forwarding table created through routing protocols. The 7670 RSP supports IP forwarding on the Multi-Rate 8 ATM/IP, Multi-Rate 16 POS, Multi-Rate 48 Channelized Multi-Protocol, and Gigabit Ethernet line cards.


69

Routed bridged encapsulation

An RBE interface is a Layer 3 interface on an ATM VC configured to use bridged Ethernet encapsulation.

RBE enables the 7670 RSP to terminate ADSL and SHDSL traffic at a Layer 3 IP forwarding interface and transmit the traffic over the network using IP forwarding.

Ingress packets are stripped of their MAC header and forwarded according to the IP payload in the packet. Egress packets are encapsulated with a MAC address corresponding to an entry in a locally maintained ARP table. Layer 3 interface support conforms to RFC 2684. ARP support conforms to RFC 826.

The MR48 line card currently supports up to 16 000 RBE interfaces when it is configured in scaled mode.

MR48 line card IP interface enhancements

The 7670 RSP supports scheduling and shaping at the CoS level for a Layer 3 ATM interface on an MR48 line card using two scheduling modes: per-CoS shaping and hierarchical shaping.

To enable the 7670 RSP to be used in a single-VC/single-service configuration, the local MAC address can be configured for each RBE interface to be one of six system MAC addresses.

The improvements of the MR48 card offer the following benefits:

• a more cost-effective solution for terminating IP traffic of DSL broadband access customers

• better flexibility for SLA offerings for business IP services• IP termination of broadband access customers in a single-VC/single-service

network configuration• capability to connect DSLAMs that require bridged interfaces

IP interface groups

An interface group is a set of Layer 3 interfaces configured with the same parameters.

IP interface groups allow the bulk configuration of thousands of IP interfaces that share a common set of parameters residing in the same IP subnet on the MR48 line card. As interface parameters are configured for the group, any new interfaces added to the group are automatically configured with those parameters.

Groups also expand the capability of the 7670 RSP DHCP relay functionality by enabling the DHCP server to assign IP subnets per port, per VP, or per VC range.


70

SRRP

SRRP is a suite of protection mechanisms to provide redundancy protection for static IP host access to a default gateway. SRRP makes it possible for service providers to replace two redundant routers configured with VRRP with a single 7670 RSP. SRRP is interoperable with any standard configuration.

SRRP provides interface protection by configuring an interface protection group consisting of a primary and a backup Layer 3 interface. In the event of an ATM link failure (such as SONET or OAM failure) on a primary interface in the protection group, an interface protection switch takes place to the backup interface so that traffic continues to flow.

Interface protection can only be configured on interfaces that are members of an RBE interface group on the MR48 line card. The backup interface is created on a specified channel using the same VPI/VCI as the primary interface and must be in the same slot as the primary interface.

SRRP offers the benefit of providing redundancy at the ATM layer for an IP/ATM Layer 3 interface.

ICMP

ICMP provides a mechanism that IP routers and hosts can use to communicate any control or error information. The 7670 RSP uses ICMP to report problems and test destination reachability.

The 7670 RSP implements the following ICMP functionality:

• IP error handling, such as destination unreachable• traceroute• ping (multisession, directed, VRF-sensitive, rapid, and self)• rate limiting of ICMP messages

IP CoS

With IP CoS, service providers can offer differentiated services to their customers. CoS provides prioritized queuing services for certain types of traffic and prevents any one class of traffic from monopolizing system resources and bandwidth.

The 7670 RSP supports eight configurable IP CoS. CoS parameters define the system-level behavior for any traffic using that CoS. Gigabit Ethernet VLAN interfaces map the eight CoS to one of three different treatments of service—high, medium, or low.

IP traffic can be classified into one of eight CoS by using multifield classification or DSCP remarking.


71

Differentiated services and DSCP to CoS profile

DS profiles can be configured on an interface to support differentiated services. IP packets arriving from an interface are classified according to the DSCP field in the header and are mapped to one of the classes according to the configured DS profile. The 7670 RSP supports 16 DS profiles.

Multifield classification

With multifield classification, service providers can assign a CoS and DP to IP packets based on a set of rules defined in a list.

DSCP remarking

With DSCP remarking, service providers can use the 7670 RSP to change the DSCP field in the header of an IP packet to a new DSCP based on the internal CoS and DP of the packet. The new DSCP is used by a next-hop router and does not affect the CoS and DP of the packet at the current node. Typically, DSCP remarking is performed on an egress interface. Ingress DSCP remarking is used in conjunction with multifield classification, DS metering or policing, and untrusted interfaces.

Packet filtering using access control lists and rate limiting

Service providers can use access lists for packet filtering in order to protect their networks from unwanted traffic or traffic sent maliciously. When an access list has been configured and assigned to an interface, the list checks packets to ensure that they conform to the rules specified in the list.

Access lists can contain permit, deny, or rate limiting rules. When a packet matches a permit rule in an access list, the 7670 RSP forwards incoming or outgoing packets on the interface. When a packet matches a deny rule in an access list, the 7670 RSP drops incoming or outgoing packets against the interface.

With rate limiting, the packet arrival or departure rate at an interface is configured in packets per second. If the specified number of packets or less arrive at or depart from the node within 1 second, they are permitted. Packets that arrive at or depart from the node at a rate that exceeds the configured limit are denied. This rule gives service providers the ability to protect their networks from flooding—packets are permitted, but in a controlled manner.

The 7670 RSP supports both standard and extended access lists. Standard access lists use source addresses for matching operations; extended access lists use source and destination addresses for matching operations as well as parameters such as TCP flags, fragments, protocol type, and port numbers.

In addition to filtering traffic that is forwarded by the node, access lists can be used to filter traffic that terminates on the node regardless of the line card on which the traffic arrived.


72

Reverse path filtering

Reverse path filtering is a security feature that can be used as part of a network strategy to protect against denial of service and distributed denial of service attacks. Many host and router attacks rely on spoofed, or false, IP source addresses. With reverse path filtering enabled, the 7670 RSP performs a lookup in the FIB against the source IP address for each packet it receives. If the source IP address is recognized, the 7670 RSP forwards the packet. If the source IP address is not recognized, the packet fails the reverse path filtering check, and it is not forwarded into the network. Instead, the packet is counted and discarded. Reverse path filtering is typically applied on untrusted interfaces at the edge of a network; it provides security to downstream nodes in the network.

Admission control

Admission control is a mechanism that ensures traffic guarantees by preventing more reservations of bandwidth than the various queuing points can handle. Admission control admits transport interfaces (the link between each IP forwarder to each IP forwarding card), Layer 3 interfaces, and LSPs requiring reserved bandwidth to a port in a hierarchical fashion.

Admission control for Layer 3 interfaces and LSPs

Admission control for Layer 3 interfaces and LSPs is performed hierarchically as follows.

• Interfaces are admitted to the ports and channels of a card.• Tunnel LSPs or other outer label LSPs are admitted into the interfaces.• Inner label LSPs are admitted into tunnel LSPs.

On ATM ports and channels, the interfaces also must coexist with PVCs, SVCs, and SPVCs.

Admission control for transport interfaces

Admission control for transport interfaces is based on the values of the system CoS configuration. If the transport interfaces use the default values of CoS, they are treated as multipoint-to-point connections. The values in the traffic descriptors from each of the congestion points in the fabric are admitted only once based on admission control. The values are used as rates relative to an OC12 rate that IP and MPLS traffic consume through the fabric as a whole. If a transport interface has values for CoS other than the default values, it is treated as a point-to-point connection between two line cards for reserved resources.

Hierarchy of admission control

The 7670 RSP supports two modes for admission control and queuing on an interface: shared bandwidth and reserved bandwidth.

In shared bandwidth mode, all interfaces on a port share the bandwidth on a first-come, first-served basis.


73

In reserved bandwidth mode, resource-reserved LSPs take the bandwidth from the configured MPLS reservable bandwidth. Non-resource-reserved traffic is scheduled to use the difference between the bandwidth of a Layer 3 interface and the bandwidth that is currently used by the resource-reserved LSPs.

DHCP relay

The 7670 RSP provides DHCP/BOOTP Relay agent services for DHCP clients and servers. A DHCP client is an IP-capable device (typically a computer) that uses DHCP to obtain configuration parameters such as a network address. A DHCP server is an Internet host or router that returns configuration parameters to DHCP clients. A DHCP/BOOTP Relay agent is a host or router (for example, the 7670 RSP) that passes DHCP messages between clients and servers.

Home computers in a residential high-speed Internet application typically use the DHCP protocol to have their IP address assigned by their Internet service provider. The DHCP protocol requires the client to transmit a request packet with a destination address of 255.255.255.255 (broadcast) that is processed by the DHCP server. Since most IP routers are not generally configured to forward broadcast packets, the DHCP client and server must reside on the same network segment. However, when the 7670 RSP is acting as a DHCP Relay agent, it processes these DHCP broadcast packets and relays them to a DHCP server, eliminating the need for DHCP clients and servers to reside on the same network segment.

DHCP reforwarding is an option that provides the ability to switch the destination of specified DHCP packets to a DHCP server, offering the flexibility to act as a DHCP Relay agent.

IP routing supportIP routing support is the foundation for the MPLS capability of the 7670 RSP. See Table 29 in Appendix B for a list of IP routing protocols supported on the 7670 RSP.

Non-stop IP routing and forwarding

Routers used in a typical IP network today do not have the ability to continue updating the routing database and forwarding packets when a route processing engine experiences failure. For this reason, most current network implementations rely on a paired-node architecture to provide the required redundancy and network reliability for service providers’ mission-critical IP-based services.

Non-stop IP routing builds on the 7670 RSP system architecture, which separates routing and forwarding functions, therefore improving the reliability of the IP network. Unlike typical second-generation routers, the routing processor of the inactive control card in the control-redundant 7670 RSP is in hot standby for the active routing stack—there is no need for reset of BGP sessions or convergence of OSPF, IS-IS, or RIP. The control card maintains


74

routing adjacencies, calculates the IP forwarding table, and downloads the IP forwarding table to the line cards that support forwarding directly. The line cards forward traffic based on information from the IP forwarding table. Non-stop IP routing means fewer routers, interfaces, and IP addresses and therefore fewer points of failure.

Key features of non-stop IP routing on the 7670 RSP include:

• separation of control plane (routing) and data plane (forwarding)• hot redundancy for BGP, OSPF, IS-IS, RIPv2, and static routing• forwarding table redundancy• redundant and hot concurrent parallel processing router engines• continued adding or changing of routes when a route processing engine is

pulled• control card and line card redundancy

Non-stop IP routing on the 7670 RSP offers service providers the following benefits:

• preservation of SLAs• no route flaps in the network• no traffic oscillation in the network• software upgrades are hitless or non-service-affecting• soft reset of line cards does not interrupt service• fast switch failover – in milliseconds, not minutes• achievement of true 99.999% availability (less than 5 minutes downtime per

year)• non-stop forwarding

Non-stop RSVP-TE

Non-stop RSVP-TE is a major enhancement to the existing RSVP-TE functionality. Non-stop RSVP totally eliminates loss of MPLS traffic caused by an LSR or LER control plane restart, specifically, the restart of the RSVP label distribution protocol component. The 7670 RSP preserves the MPLS forwarding component across the restart. During a control plane restart, the 7670 RSP continues to forward traffic for RSVP-TE LSPs or for Layer 2 or IP VPNs or MPLS pseudowire service using RSVP-TE as an outer tunnel, primary route, alternate route, or bypass tunnel.

Non-stop RSVP is enabled by default and is not configurable. Non-stop RSVP-TE does not require any extension to standard RSVP-TE and is interoperable with any third-party, standards-compliant platform.

Non-stop RSVP-TE offers the following benefits:

• improves MPLS/LSP reliability• brings an IP/MPLS-based converged backbone network up to a 99.999%

reliability


75

CSPF for RSVP-TE and CR-LDP

CSPF enables the configuration of constraints on the routing of RSVP-TE and CR-LDP S-LSPs. The constraints are reservable bandwidth and administrative group. CSPF uses traffic engineering metrics circulated by OSPF and IS-IS to calculate its constrained paths. CSPF provides a means of controlling the path taken by traffic using RSVP-TE and CR-LDP S-LSPs.

The CSPF feature for RSVP-TE and CR-LDP enables the 7670 RSP to compute a path for an LSP from a source node to a destination node subject to various constraints.

CSPF offers the benefit of enabling the 7670 RSP to calculate the LSP route with required constraints.

RIPv2 support

RIP is a routing protocol based on the Bellman-Ford algorithm, which uses distance vector routing. RIP is an older, widely used protocol. It is supported by many CE routers that do not support other dynamic routing protocols. RIP is therefore ideal for use as a PE-CE routing protocol in an IP VPN.

The 7670 RSP supports RIPv2, as defined in RFC 2453. RIPv2 adds authentication and support for subnet masks to RIP. RIP supports route redistribution to and from other protocols such as BGP, OSPF, and IS-IS, and supports non-stop routing. A RIP version compatibility switch is also supported to interoperate with RIPv1-based routers.

RIPv2 offers the following benefits:

• enables high-availability IP and IP VPN services• expands new CE routing options, which is particularly useful with many

ADSL-based routers

Graceful restart helper for BGP

Graceful restart helper for BGP helps to minimize network route flaps when peering sessions, or neighbors, restart. Typically, when a routing processor of a router goes down, before the redundant routing process restarts, all the routes advertised by this router are withdrawn by its neighboring routers, causing route flaps.

The 7670 RSP is fully redundant, which prevents any loss in its BGP peering sessions, so it only implements the receiving side of the graceful restart capability. This enables it to act as a helper to a neighboring restarting router that has advertised the graceful restart capability.

Graceful restart helper for BGP enables the 7670 RSP to preserve BGP routes learned from a neighbor, during a session restart of that neighbor, provided that the restart happens within a certain time limit that was negotiated during session establishment. The 7670 RSP can process restart requests from multiple BGP neighbors and routers.


76

Graceful restart helper for BGP offers the benefit of interoperable routing resiliency with other third-party, standards-compliant P routers and PE routers.

Graceful restart helper for OSPF

Graceful restart helper for OSPF provides a mechanism by which an OSPF router can stay on the forwarding path as its OSPF routing stack restarts. The 7670 RSP supports this functionality.

When the 7670 RSP receives a grace LSA from a neighboring router, indicating that the router is about to restart, the 7670 RSP performs the helper function by continuing to advertise LSAs as if the restarting OSPF router was continuously operational. The 7670 RSP can help multiple restarting routers at the same time.

Graceful restart helper for OSPF offers the benefit of interoperable routing resiliency with other third-party, standards-compliant P routers and PE routers.

ECMP

ECMP is a method of distributing traffic to a single destination over several equivalent paths in order to balance the traffic load. The 7670 RSP can support up to eight equal-cost paths per destination. ECMP is supported by OSPF, BGP, IS-IS, RIP, and static routing.

Routing policies

Service providers can use the 7670 RSP to create routing policies from autonomous system path lists, access lists, prefix lists, community lists, and route maps. Routing policies are used to filter incoming and outgoing routes and can be applied to BGP peers, RIP peers, IS-IS links, OSPF links, redistribution, and aggregation.

IP multicastIP multicast is a bandwidth-conserving technology that reduces traffic by sending a single stream of traffic to multiple recipients.

In a unicast environment, a source host must send a separate data stream for each host wishing to receive the data. In a multicast environment, hosts wishing to receive a particular data stream join a multicast group. The source host only needs to send a single data stream for the multicast group, regardless of how many receiving hosts belong to the group.

The 7670 RSP supports IP multicast routing to deliver traffic to multiple receivers using the IGMP, PIM-SM, and PIM-SSM protocols.

The 7670 RSP supports multicast ping and traceroute to enable insertion into a multicast tree and interception of replies.


77

Based on the IP multicast address, the 7670 RSP classifies a multicast tree into one of the IP CoS, and prioritizes it amongst other IP unicast traffic in the node.

The IP multicast capability of the 7670 RSP offers the following benefits:

• provides an IP-layer solution for broadcast video distribution• brings the right QoS to video distribution• enables the following applications:

• video conferencing and corporate communications• distance learning• software distribution• stock quotes and news feeds• broadcast TV• combination of the above, delivered via one video interface

IGMP

IGMP is a protocol used between hosts and multicast routers on a single physical network to establish membership of the hosts in particular multicast groups. Hosts send IGMP messages to the local multicast router indicating their interest in joining a particular group or their intention to leave the group. The messages are encapsulated in IP packets.

IGMP is also used by the multicast router to check on the status of group membership. The router sends out membership queries periodically to verify that there is at least one host in the attached network (subnetwork) that is interested in receiving messages from a particular group.

As a multicast router, the 7670 RSP maintains a list of multicast groups.

The 7670 RSP supports IGMP v2 as per RFC 2236. The 7670 RSP supports static IGMP, where the interface is manually added or removed, if the receiving host does not support IGMP. The interface is statically added as an outgoing IP interface (OIF) to the multicast tree. The 7670 RSP also supports non-stop IGMP, whereby during a control card switchover or software upgrade, all OIF in the multicast tree are maintained.

Static multicast

With static multicast, the 7670 RSP can add an incoming IP interface (IIF) to the tree without having to run any dynamic PIM protocol.

IGMP proxy

IGMP proxy is a method used to send IGMP request messages between routers. IGMP proxy enables the router to issue IGMP host messages on behalf of hosts that the router discovered through standard IGMP interfaces. The router acts as a proxy for its hosts.

IGMP proxy, as a solution, enables the 7670 RSP to provide each DSLAM with only the specific channels that it has requested, thereby greatly reducing the problem of video bandwidth exhaustion from unnecessary channel replication.


78

This optimized bandwidth between the broadcast server and the end user translates into service providers being able to offer a greater variety of TV and video channels to end customers over limited bandwidth.

PIM-SM

PIM-SM is a multicast routing protocol that uses information in the unicast routing table to perform multicast routing. PIM-SM is protocol-independent. With the PIM-SM protocol, multicast traffic is forwarded only to networks containing hosts that have explicitly requested the data (that is, have joined the multicast group). PIM-SM is known as an any-source protocol because it supports traffic from multiple sources to the same multicast group. Multicast sources transmit data to multicast groups in the range of 224.0.1.0 to 239.255.255.255.

PIM-SM uses a shared tree model to determine the path that the multicast traffic takes through the network. A shared tree is also called an RP tree because it uses a central multicast router as a rendezvous point (RP). There is one shared tree per multicast group. The 7670 RSP can be deployed as a designated router (DR) as well as an RP.

The PIM-SM protocol offers the benefit of simplifying the routing or forwarding of multicast traffic in the network.

PIM-SSM

Protocol independent multicast - source-specific mode (PIM-SSM) is an IP multicast routing protocol, a derivation of PIM-SM, that supports traffic from a single source to many receiving hosts. Although PIM-SSM uses the same join/prune procedure as PIM-SM, it does not need the RP-based, shared-tree infrastructure that is required by PIM-SM. PIM-SSM uses a source-specific tree model (or shortest-path tree) to determine the path that multicast traffic takes through the network.

The default PIM-SSM address range is 232/8 (232.0.0.0 to 232.255.255.255). Addresses in this range are reserved for source-specific applications and therefore cannot be used for SM applications. However, SSM applications are not limited to this range; they can use the entire Class D address range.

PIM-SSM reduces the risk of denial of service attacks because only an exact, specified source can send to a particular IP multicast group.


79

IPv6IP version 6 (IPv6) is a set of protocols designed to replace IP version 4 (IPv4) and to provide the following solutions:

• expand address capabilities for new and advanced applications, to address the eventual exhaustion of IPv4 addresses

• equitably distribute addressing assignment space as needed• enable full peer-to-peer communications between end-user devices• provide inherent support for 3G mobile IP multimedia applications and

real-time services• enable easier autoconfiguration and renumbering for advanced mobility

services• improve security at the IP level, for authentication and data integrity

IPv6 introduces 128-bit addresses—a major increase over IPv4’s 32-bit addresses. As a result, both fixed and mobile service providers are able to future-proof their networks to meet the continued growth in demand for IP-based applications and services.

IPv6 Ready certification

The 7670 RSP is the first multiservice platform to achieve the industry-recognized, IPv6 Forum-sponsored, IPv6 Ready certification. This certification was given by an independent third-party testing house—the Interoperability Laboratory at the University of New Hampshire.

Non-stop IPv6 routing and forwarding

On the 7670 RSP, the IPv6 Routing Information Base (RIBv6) contains routes added by routing protocols and local IPv6-enabled interfaces. Four sources of IPv6 routes are supported: IPv6 static routing, IBGP 6PE, IBGP 6VPE, and local interfaces. Only the best routes, chosen based on the route’s lowest or most direct administrative distance, are downloaded to the Forwarding Information Base on the line cards.

IPv6 implementation on the 7670 RSP extends its functionality to add support for high availability for IPv6 (IPv6 non-stop routing and forwarding). In the case of a control card activity switch or nodal upgrade, the hot standby redundancy mechanism between the active and the standby control cards ensures enhanced reliability and service continuity.

IPv6 QoS

In an MPLS-enabled network, IP traffic is transported in LSPs. These LSPs provide traffic flow segregation and bandwidth reservation, as well as up to eight classes of service, through the use of the EXP bit in the MPLS header. Different classes of IPv6 traffic can be mapped to different EXP bit values. This means that a service provider can not only offer IPv6 services (such as


80

enterprise connectivity, internet, NGN voice networks, and mobile applications), but can offer differentiated and premium IPv6 services with quantifiable and measurable end-to-end QoS.

IPv6 over MPLS

IPv6 is supported on the MR48 and Gigabit Ethernet line cards. The 7670 RSP acts as a dual-stack router, and both IPv4 and IPv6 can run simultaneously.

IPv6 is deployed over an MPLS backbone, enabling isolated IPv6 domains to communicate with each other over an MPLS/IPv4 core network. Using this implementation, forwarding is based on MPLS labels rather than the IPv6 header. This results in fewer infrastructure upgrades and reconfigurations of core routers to support IPv6. Deploying IPv6 on provider edge routers is possible using 6PE or 6VPE.

6PE

The 7670 RSP can be deployed as a 6PE router.

In a typical deployment scenario, the 7670 RSP acts as a 6PE router that is connected to IPv6 CE routers via IPv6 interfaces. IPv6 reachability information is advertised through a multiprotocol BGP session running over IPv4. IPv6 static routers or directly connected IPv6 routers are used to redistribute IPv6 reachability information into multiprotocol BGP.

6VPE

The 7670 RSP can also be deployed as a 6VPE router in an IPv6-capable VPN to support IPv6 traffic over MPLS.

The 6VPE router maintains separate IPv6 VRFs for each VPN. The PE routers use the VRFs to collect information for each IPv6 VPN. In a similar setup to IPv4, IPv6 routing information is exchanged between PEs using BGP with multiprotocol extensions to support carrying routes from VPN-IPv6 address families. IPv6 static routes in a VPN, or directly connected IPv6 VPN routes, are redistributed into multiprotocol BGP.

ICMPv6

ICMPv6 is an updated version of ICMPv4, a diagnostics and troubleshooting tool used by the 7670 RSP. ICMPv6 is used in the operations, administration, maintenance, and provisioning of an IPv6 network. The following functions and message types are supported:

• neighbor discovery• troubleshooting (ping and traceroute)• error handling• Multicast Listener Discovery (MLD)


81

IP VPNs (Layer 3 VPNs)IP VPNs are a standardized and widely deployed method of establishing secure communications networks for enterprise customers or for simplifying carrier IP infrastructure. With IP VPNs, carriers can provide enterprises with the ability to connect a number of different locations and create a “private” network, in a secure and cost-effective manner. This ability can be extended to a number of different IP VPNs.

IP VPNs differ from traditional Layer 1 VPNs (which require a physically separate infrastructure) and Layer 2 VPNs (which connect sites using frame relay, ATM, or Ethernet with a virtual circuit). Instead, IP VPNs can provide equivalent or improved service since multiple VPNs can be delivered from a common infrastructure, where the total cost of the network is lowered and utilization is maximized.

IP VPNs on the 7670 RSP are based on RFC 4364 (formerly 2547bis). Premium IP VPN functionality is available because of the high availability, guaranteed QoS, traffic engineering, simple and quick provisioning, and full management capabilities unique to IP VPN implementation on the 7670 RSP.

7670 RSP solution for IP VPNs

Table 5 lists the features that make the 7670 RSP one of the most versatile and cost-effective solutions for deploying IP VPNs.

Table 5: Features of the 7670 RSP IP VPN solution

Feature Description

High-availability services based on high-availability architecture

The platform provides non-stop routing for the VRFs delivering the IP VPN service. This ensures that if the control complex fails, the IGP or BGP session and MPLS LSPs are not torn down and that the network continues to exchange topology information between peers. Non-stop routing eliminates the reroute convergence time that affects most dual-home router networks.

Proven QoS and traffic management tool, ensuring SLA compliance

The platform integrates QoS and traffic management tools. It supports eight QoS levels per VPN interface, which correlate to DiffServ queues that help to segregate and set priorities for traffic with different delay and loss characteristics. This flexibility enables service providers to support a variety of applications on the same VPN while maintaining a strict SLA for each.

Support for import and export route targets for improved extranet security, and VRF-based routing policy

This feature enables import and export routing policy to determine how customers communicate across VPNs based on how IP addresses are handed off. This is the key building block for a secured extranet offering.

(1 of 3)


82

Dedicated and differentiated tunnels enable multiple service levels and flexible service pricing models

Tunnels are established between service nodes in the core of the network to carry traffic from all VPNs supported in a service provider’s network. The most common mechanism to establish these tunnels is LDP-DU. The 7670 RSP supports a more robust protocol, RSVP-TE, for establishing tunnels. RSVP-TE also guarantees bandwidth reservation between nodes. The 7670 RSP enables service providers to run both protocols (LDP-DU and RSVP-TE) simultaneously between service nodes and to map a customer's VRF or multiple VRFs to an LDP-DU or RSVP-TE tunnel. The benefit is the ability to determine the bandwidth reservation and service SLA level for each customer and tariff the service accordingly.

Bandwidth guarantees per Virtual Routing and Forwarding (VRF)

Bandwidth guarantees per VRF provide enhancements to Layer 3 VPN LSP tunnel management. Specifically, a set of CR-LDP S-LSPs can be configured in an S-LSP list for use as outer tunnels in a VRF for VPN packet flow between the PE devices. Using the configured S-LSP list, the 7670 RSP will preferentially select an S-LSP whose path ends match the BGP source update address of the BGP session. This feature provides an additional QoS mechanism to control L3 VPN traffic between PEs. It also allows customers to make better use of lower speed transport links, guaranteeing that service no longer requires trunks to become over-provisioned.

Virtualized DHCP relay agent per VPN simplifies service delivery, enabling CE-less VPN site

IP addresses are assigned dynamically with DHCP, which is a flexible and easy way of creating IP addresses for simple LAN networks.

Source-based forwarding (SBF) allows packets to be redirected away from an interface’s default route and onto a preferred LSP through the network

SBF allows operators to have greater control over how IP packets are forwarded within the network; for example, based on host IP address, subnet, or specific application. This offers the flexibility to map the traffic to an LSP based on ingress port and destination address. How the packets are directed is based on the source IP interface and on rules defined on Access Control Lists (ACLs). SBF also enables the creation of differentiated, highly secure VPN services. For example, premium subscriber traffic can be redirected to travel along a specific path through the network, supporting CoS treatment end-to-end.

Feature Description

(2 of 3)


83

PseudowiresPseudowires provide a connection-oriented service between Layer 2 endpoints on PE devices over an MPLS network. For Layer 2 connections across an MPLS network, the 7670 RSP supports both Ethernet and ATM pseudowires. Pseudowire LSPs are signaled through a targeted LDP session. The pseudowires traverse the network over RSVP-TE and LDP-DU S-LSP tunnels between the PE devices.

IP pseudowires are also supported on the 7670 RSP. They offer the benefit of being able to be used in a service interworking capacity to encapsulate frame relay or ATM (Layer 2 services) traveling between Ethernet devices. This enables carriers to leverage their legacy transport services.

The 7670 RSP fully adheres to the IETF PWE3 framework for the standardization of pseudowire functionality. For a complete list of pseudowire standards and IP/MPLS standards compliance, see Table 14 in Appendix A.

Pseudowire VCCV

Pseudowire Virtual Circuit Connection Verification (VCCV) is a network fault diagnostic and troubleshooting tool that notifies a remote router of the diagnostic operations that are supported on the local node. VCCV emulates fault detection and enhances the troubleshooting of Layer 2 services, including ATM and Ethernet across an MPLS network. Pseudowire VCCV defines a set of messages that are exchanged between PE devices in order to verify connectivity of the pseudowire. To ensure that pseudowire packets follow the same path as the data flow, they are encapsulated with the same labels.

For further information, see the “MPLS OAM” section in this chapter.

Inter-AS VPN option (b) This feature facilitates deployment of IP VPN services in a variety of situations, allowing multiple Autonomous Systems (AS) under the control of a single organization to be effectively linked. This enables merged service providers to leverage multiple networks and exchange VPN routes with other operators to deliver IP VPN services, while still preserving existing Autonomous Systems and not requiring a dedicated interface per customer.

Concurrent support for Layer 2 and Layer 3 services

The 7670 RSP is optimized to deliver multiple services reliably and concurrently. Its architecture supports IP and new and existing Layer 2 services over IP and MPLS technologies. For new networks, it means one platform solution for both Layer 2 and Layer 3 services. For existing networks, it means additional revenue with incremental investment versus the cost of deploying a new network (customers activate new services through standard software).

Feature Description

(3 of 3)


84

Pseudowire endpoint coordination

Where supported, pseudowire endpoint coordination minimizes the use of network resources when pseudowire establishment fails. If a pseudowire signaling link fails to be established bidirectionally, the 7670 RSP withdraws the pseudowire label to unreserve the associated network resources at both the ingress and egress endpoints.

85

7670 RSP system architecture

This chapter describes the architecture of the 7670 RSP, including:

• “Architecture principles”• “Single-shelf system overview”• “Multishelf system overview”• “Switching shelf”• “Peripheral shelf”• “In-service single-shelf to multishelf upgrade”• “Line cards and I/O cards”

6. 7670 RSP system architecture

86

Architecture principlesThe 7670 RSP system architecture design is based on the following principles:

• scalability, density, and flexibility• high availability• simultaneous IP/MPLS and ATM functionality• high performance

Scalability, density, and flexibility

The 7670 RSP supports a comprehensive range of scalability, capacity, and performance options. A unique attribute of the 7670 RSP is its ability to scale while in service from a 50 Gb/s to a 450 Gb/s switching fabric (redundant, full duplex), supporting 320 Gb/s user I/Os (redundant, full duplex, APS enabled). Its ability to scale up gradually after initial deployment not only defers capital expenditures until traffic levels warrant, but also eliminates the need for hardware upgrades. Service providers can optimize node configurations at each individual site over an extended time and ensure capital is never tied up in underused assets.

The 7670 RSP’s support for 768 000 virtual connections meets the carrier requirement to migrate thousands of Layer 2 frame relay and ATM connections and a high volume of associated state information onto a smaller number of LSPs on an MPLS backbone. A general-purpose router does not usually have the capacity to maintain this amount of Layer 2 state information without a resulting impact on performance, throughput, or QoS. The 7670 RSP LSP connection density has been sized to support the migration of the multiservice networks to MPLS. The 7670 RSP can support up to 100 000 customers simultaneously.

High availability

High availability, a core requirement for highly reliable products, is achieved through the features listed in Table 6.

Table 6: 7670 RSP high-availability features

Feature Description

Midplane The adoption of a midplane architecture enables easy replacement of I/O card optics, in case of failure. Separating I/O cards from line cards reduces service disruption when replacing faulty hardware or performing maintenance.

Diagnostics The ability to quickly diagnose and identify any components within the system that may be experiencing degradation or problems ensures maximum fault isolation and coverage.

LCR/APS (1) To achieve full flexibility, APS and LCR can be deployed independently.

(1 of 2)


87

Note1. LCR is sometimes known as EPS.

IP/MPLS and ATM functionality

The 7670 RSP is an ideal platform for offering Layer 2 and Layer 3 services concurrently.

High performance

The 7670 RSP platform supports high-performance SVC and SPVC call rates and minimal IP routing convergence times. Wire-speed forwarding and switching are supported on all ports at the same time.

System configurationsThe 7670 RSP comes in two configurations: a standalone single-shelf configuration (providing 50 Gb/s of bandwidth) and a multishelf configuration (providing 450 Gb/s of bandwidth). Each shelf is based on a midplane design in which cards may be plugged into the front or the rear. All the cabling is located at the rear.

Single-shelf system overviewThe single-shelf system is the base of the “pay-as-you-grow” solution offered by the 7670 RSP. It can be seamlessly expanded while in service to become the Control shelf (also known as Peripheral shelf 1) in a multishelf system.

The single shelf has a midplane design in which field-replaceable cards and I/O cards are inserted in the front and back of the shelf. The front face of the midplane also provides connection for three fan units, two power modules, and two LED panels.

Hitless upgrade In order to ensure high-availability services, carriers must be able to upgrade the node without interruption of services or breach of SLA commitments.

Control redundancy An internal bus architecture enables full and rapid synchronization between active and inactive control cards.

Infrastructure redundancy

The 7670 RSP provides redundancy protection for the nodal infrastructure.

Safety net In the unlikely event of a double control card failure, line cards stay up and data path traffic continues to pass.

Fabric redundancy The 7670 RSP is designed with a redundant fabric for high availability and 100% capacity protection.

Feature Description

(2 of 2)


88

Single-shelf layout

Figure 30 shows the layout of the single shelf. The shelf is divided into three main areas:

• breaker panel and power termination area• circuit-card area• fan area

Figure 30: Layout of the 7670 RSP single shelf

Breaker panel and power termination area

The breaker panel and power termination area contains connection points for the power feeds and an antistatic wrist strap. It also contains the alarm display LEDs and the alarm cutoff switch.

Circuit-card area

All cards are inserted into the card slots in the circuit-card area. The cards connect to the midplane, which is positioned between the front and the back cards. The midplane design separates the line card and I/O card functionality to enhance redundancy and help the 7670 RSP achieve 99.999% availability. The midplane also holds filler plates for slots that do not contain cards.

Table 30 in Appendix A lists the main components of the circuit-card area.

Figure 31 shows the circuit-card area of the 7670 RSP single shelf.

Breaker panel andpower termination

area

Circuit-cardarea

Fanarea

14766

6-2 5-2 4-2 3-2 2-2 1-2

Status

Active

Status

Active

8-1 Switch Y 7-1 Switch X

16-2 15-2 14-2 13-2 12-2 11-2 10-2 9-2

16-1 15-1 14-1 13-1 12-1 11-1 10-1 9-1

6-1 5-1 4-1 3-1 2-1 1-1

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active Status

ActiveStatus

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Status Status Status StatusStatus Status Status

Status

Front view Back view


89

Figure 31: Circuit-card area of the single-shelf system

Fan area

The 7670 RSP uses forced-air convection cooling through three independently controlled fan units. Each fan unit has two fans. Built-in temperature sensors monitor the exhausted air temperature of the system and adjust the fan speed accordingly. The fan units are located at the front of the fan area, and an exhaust vent is located at the back of the fan area.

Single-shelf system cards

The following system cards provide management and switching capability in a single-shelf system:

• control card• CIC• Facilities card• Switch card

See “Line cards and I/O cards” later in this chapter for information about supported line cards and I/O cards in the single-shelf system.

Switchcards

CIC CIC

14768

6-2 5-2 4-2 3-2 2-2 1-2

Status

Active

Status

Active

8-1 Switch Y 7-1 Switch X

16-2 15-2 14-2 13-2 12-2 11-2 10-2 9-2

16-1 15-1 14-1 13-1 12-1 11-1 10-1 9-1

6-1 5-1 4-1 3-1 2-1 1-1

Critical Alarm

Major Alarm

Minor Alarm

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active Status

Active Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

Status

Active

I/O

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Status Status Status StatusStatus Status Status

Status

I/Ocards

I/Ocards

I/Ocards

I/Ocards

Facilitiescard

Linecards

Controlcards Fan unit

Front view Back view

Cablemanagement

brackets

Cablemanagement

brackets

Linecards


90

Control card

The 7670 RSP system supports two CC2G cards. The CC2G card is a control card that contains high-speed processors, RAM, and flash memory, which enable significant scaling of the IP feature set. Throughout this General Information Book, the terms “control card” and “CC2G card” are used interchangeably.

The 7670 RSP requires two control cards to be installed. One control card is active and the other is the hot redundant backup.

The control cards provide local and remote control of the system. They control all the cards in the system, maintain the configuration and connection database for the node, and collect and report statistics.

Table 7 describes the functions that are performed by the control card.

Table 7: Control card functions

CIC

The CIC provides an Ethernet interface connection to the control card. The 7670 RSP uses two CICs, one for each control card. The CICs are installed in dedicated slots on the back of the 7670 RSP.

Facilities card

The Facilities card provides an interface to the control card for node management and external alarm connections. The 7670 RSP has one Facilities card, which is accessed and used by the active control card. The Facilities card is installed in a dedicated slot on the back of the 7670 RSP.

Function Description

Network management interface support

The control card provides an interface to a network management system through Ethernet connections on the CICs or through ATM connections on I/O cards.

Alarm consolidation The control card consolidates node-wide alarms into alarm queues. Alarms are indicated by LEDs on the front and back of the breaker panel and power termination area. The control card uses connections on the Facilities card to receive alarms from, or send alarms to, external equipment.

Data spooling The control card can use data spooling to provide accounting information to external data collectors through Ethernet connections on the CICs.

Node management support The control card provides statistics collection and reporting, and maintenance and diagnostic support for the node.

Routing and call processing The control card provides the IP and PNNI routing, ATM and MPLS signaling, and general processing functions for the system.


91

The Facilities card has two variants: International and North American.The International variant has two BNC connectors for timing inputs of 2.048 MHz. The North American variant has two sets of three wire-wrap posts for BITS timing inputs.

Switch card

The Switch card provides the core of the switching fabric used by the 7670 RSP for routing and switching. The 7670 RSP uses two Switch cards for redundancy; they are installed in dedicated slots in the back of the 7670 RSP.

Multishelf system overviewThe 7670 RSP multishelf system extends the single-shelf system by moving the fabric out to separate redundant Switching shelves and allowing multiple Peripheral shelves to be attached to it. Instead of clustering multiple single-shelf systems where each one behaves as an individual node, a multishelf system combines multiple single-shelf systems into one node and thus greatly reduces the number of nodes in the network as well as the operating costs. In its most basic configuration, a multishelf system with only one Peripheral shelf resembles a single-shelf system with the Switch cards replaced by FICs connecting the Switching shelf, and two line card slots occupied by ICON cards used for inter-shelf control communications.

The multishelf system supports the following shelves:

• Control shelf (also known as Peripheral shelf 1)• Switching shelf• Peripheral shelf

A multishelf configuration requires a minimum of:

• one Control shelf, which contains the control cards for the whole system; this shelf is known as Peripheral shelf 1

• two Switching shelves, X and Y, which provide the required switching capacity for the whole system

Figure 32 shows a basic multishelf configuration.


92

Figure 32: 7670 RSP multishelf configuration

Control shelf (Peripheral shelf 1)

In a multishelf system, the Control shelf performs all of the control functions. The Control shelf is differentiated from all other Peripheral shelves in that it contains the control cards, CICs, and ICON cards. In addition, it supports line cards in other available slots. See “Peripheral shelf” later in this chapter for information about the functions of other Peripheral shelves used in a 7670 RSP multishelf configuration.

Figure 33 shows the front and back layouts of the 7670 RSP Control shelf.

FIC

Y

FIC

X

FIC

Y

FIC

X

SACs SACs

Switching shelf Y

Control shelf

HISL cables

16137

Peripheral shelf

Switching shelf X


93

Figure 33: Front and back layout of the 7670 RSP Control shelf

Circuit-card area

All Control shelf cards are inserted into the card slots in the circuit-card area. The cards connect to the midplane, which is positioned between the front and the back cards. The midplane design separates the circuit cards and I/O cards to enhance redundancy and help the 7670 RSP achieve 99.999% availability.

Table 31 in Appendix A lists the main components of the circuit-card area on the Control shelf.

Fan area

The Control shelf uses forced-air convection cooling through three independently controlled fan units. Each fan unit has two fans. Built-in temperature sensors monitor the exhausted air temperature of the system and adjust the fan speed accordingly. The fan units are located on the front of the fan area, and an exhaust vent is located at the back of the fan area.

Control shelf cards

The following Control shelf system cards provide management and switching capability:

• control cardThe control card manages the other cards in the 7670 RSP system. The 7670 RSP multishelf system uses the same control card as the single-shelf system. See “Single-shelf system cards” for more information about the control card functions.

• CICThe CIC provides a connection interface to the control card for Ethernet ports. The 7670 RSP uses two CICs, one for each control card. The CICs are installed in dedicated slots on the back of the Control shelf. The multishelf system uses the same CICs as the single-shelf system.

16-2 15-2 14-2 13-2 12-2 11-2 10-2 9-2 6-2 5-2 4-2 3-2 2-2 1-2

16-2 15-2 14-2 13-2 12-2 11-2 10-2 9-2 6-2 5-2 4-2 3-2 2-2 1-2

1

2

3

4

8-2

Status

Active

ClockOut

CIC

Status

ClockA In

ClockB In

Facilities

1

2

3

4

Status

Active

ClockOut

CIC

Ext

erna

l Ala

rms

Ext

erna

l Ala

rms

Critical Alarm

Major Alarm

Minor Alarm

ACO/LT

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

Control Control

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1 2 3 4 5Control Card A Control Card A

6 7 8 9 10 11 12 13 14 15 16

Critical AlarmACO/LTMajor AlarmMinor Alarm

Status Status Status

A PowerA1 A2 A3 A4

StatusStatusStatusStatus

A PowerB1 B2 B3 B4


Fan Unit 1 Fan Unit 2 Fan Unit 3

Active

I/O Fault

Status

Active

I/O Fault

Status

Controlcard A

Controlcard B

ICON 1

Breakerpanelarea

Circuit-cardarea

Fanarea

ICON 2

CIC B CIC A

FICsICONI/O card

ICON I/O expansion

card

Terminationarea

Circuit-cardarea

Facilitiescard

Exhaust

18067


94

• Facilities cardThe Facilities card provides an interface to the control card for node management and external alarm connections. The Facilities card is installed in a dedicated slot on the back of the Control shelf.The Facilities card has two variants: International and North American.The International variant has two BNC connectors for timing inputs of 2.048 MHz. The North American variant has two sets of three wire-wrap posts for BITS timing inputs.

• DFIC and QFICDFICs and QFICs provide the Control shelf and the other Peripheral shelves with connectivity to the Switching shelves through HISL ports. HISL cables allow traffic to flow between shelves. DFICs and QFICs also provide connectivity to the switching fabric for all line cards in the Peripheral shelves. DFICs and QFICs are installed in the fabric slots of the Control shelf and the other Peripheral shelves.The system can be configured to optimize the use of bandwidth according to the configuration of each shelf. The DFIC has two HISL ports that provide up to 28 Gb/s; the QFIC has four HISL ports that provide up to 56 Gb/s, doubling the fabric capacity.

• ICON Management cardThe ICON Management cards are installed in a multishelf system to connect Peripheral shelves and Switching shelves to the Control shelf. The ICON Management cards extend services from the control card to all elements in the system. They communicate control information between the shelves and ensure that system timing is consistent. An active control card must be present and the system must be configured as a multishelf system in order for an ICON Management card to perform its function. A multishelf system uses two ICON Management cards for redundancy. To be fully functional, the ICON infrastructure requires two ICON management cards and two ICON I/O cards on the Control shelf.

• ICON I/O and ICON I/O Expansion cardsICON I/O and ICON I/O Expansion cards provide interface connectivity for the Control shelf. To access all of the shelves in the system, the ICON Management card requires at least two ICON I/O cards. ICON I/O and ICON I/O Expansion cards are located on the back of the shelf. The CSL ports associated with one ICON Management card are distributed to both of the ICON I/O cards. ICON I/O cards and ICON I/O Expansion cards are designated A and B; ICON A and ICON B provide redundancy for each other.

See “Line cards and I/O cards” for information about supported line cards and I/O cards in the multishelf system.


95

Control plane

The control plane includes:

• node management, or methods to manage and monitor the node through CLI, SNMP, or a network management system

• internal management, the mechanism by which the control card manages the line cards and all other cards

• applications and protocols terminated by the 7670 RSP that affect the data plane

Switching shelfThe Switching shelf directs traffic among the Peripheral shelves. A multishelf system requires two Switching shelves.

Figure 34 shows the front and back views of the 7670 RSP Switching shelf.

Figure 34: Front and back layout of the 7670 RSP Switching shelf

Circuit-card area

All switching cards are inserted into the card slots in the circuit-card area. The cards connect to the midplane, which is positioned between the front and the back cards. The midplane design separates the switching circuit cards and SACs to enhance redundancy and help the 7670 RSP achieve 99.999% availability.

Table 32 in Appendix A lists the main components of the circuit-card area on the Switching shelf.

32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

RxCLS B

CLS A

16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx

ActiveActive

Status

Tx

Rx



Fan Unit 1 PowerZone 4 Fan Unit 2 PowerZone 4 Fan Unit 3 PowerZone 4

1 Schuduler 2 Matrix 3 Matrix 4 Matrix 5 Matrix 6 Matrix 8 Controller7 Matrix

OC192

Status

Active

OC192

Status

Active

OC192

Status

Active

OC192

Status

Active

OC192

Status

Active

OC192

Status

Active

OC192

Status

Active

OC192

Status

Active

PowerZone 1 PowerZone 1 PowerZone 1 PowerZone 2 PowerZone 2 PowerZone 2 PowerZone 3 PowerZone 3

A PowerA1 A2 A3 A4

Status Status Status Status

B PowerB1 B2 B3 B4

Status Status Status Status


Circuit-cardarea

ACO/LTswitch

Alarmdisplay

Breakerpanel

Wrist-strapconnection

point

SSCcard

Airintake

SCHcard

Fanunits

SMXcards

Powertermination

area

ACO/LTSwitch

SACs

Wrist-strapconnection

point

CSLs

Cablemanagement

brackets

Back exhaust

Circuit-cardarea

Alarmdisplay

18069


96

Fan area

The Switching shelf uses forced-air convection cooling through three independently controlled fan units. Each fan unit has two fans. Built-in temperature sensors monitor the exhausted air temperature of the system and adjust the fan speed accordingly. The fan units are located on the front of the fan area, and an exhaust vent is located at the back of the fan area.

An optional exhaust deflector tray mounts below the Switching shelf and directs the hot air exhaust from the fan units at the front of the shelf out the back of the shelf.

Switching shelf cards

The following switching cards provide the Switching shelf with switching capability:

• SSC cardThe SSC card monitors all shelf functions and components, and maintains communications with the Control shelf using the two redundant CSL connectors on the back of the shelf. The SSC card controls and monitors the SCH card, SMX card, and SACs, as well as the display panels, fan trays, and power modules on the Switching shelf. The SSC card synchronizes the timing for all devices on the Switching shelf.

• SCH and SMX cardsThe SCH card and SMX cards work together to create the switching core. The switching core checks ingress traffic and directs it to the appropriate egress port. The six SMX cards create the switching fabric. The SCH card analyzes and prioritizes the incoming cells crossing the fabric by communicating with the SACs.

• SACThe SAC provides the Control shelf and the Peripheral shelves with access to the switching core. The SAC communicates with the FIC to avoid congestion in the switching core.The SAC is the connection point for the HISL cables that come from the FICs installed in the Peripheral shelves. Each SAC has one HISL port with an Rx and a Tx SMC connector pair. Two HISL cables make the ingress and egress data-path connections. When both HISL cables are connected, the SAC synchronizes with the FIC.Up to 32 SACs can be installed in the back slots of a Switching shelf. The SAC installed in the first slot is reserved to transmit resource connection information to and from the Control shelf.

Peripheral shelfIn addition to the Control shelf, up to 14 Peripheral shelves equipped with line cards can be added to the multishelf system for a total of 15 Peripheral shelves. This enables service providers to increase their switching capacity up to 450 Gb/s. The basic functions and layout of the Peripheral shelf are similar to


97

those of the single-shelf system, except that the Peripheral shelf has no control function. See “Single-shelf system overview” earlier in this chapter for more information.

Figure 35 shows the front and back views of the 7670 RSP Peripheral shelf.

Figure 35: Front and back layout of the 7670 RSP Peripheral shelf

Circuit-card area

The Peripheral shelf cards are inserted into the card slots in the circuit-card area. The cards connect to the midplane, which is positioned between the front and the back cards. The midplane design separates the circuit cards and I/O cards to enhance redundancy and help the 7670 RSP achieve 99.999% availability.

Table 33 in Appendix A lists the main components of the circuit-card area on Peripheral shelves 2 to 15.

Fan area

The Peripheral shelf uses forced-air convection cooling through three independently controlled fan units. Each fan unit has two fans. Built-in temperature sensors monitor the exhausted air temperature of the system and adjust the fan speed accordingly. The fan units are located at the front of the fan area, and an exhaust vent is located at the back of the fan area.

An optional exhaust deflector tray mounts under a Peripheral shelf and directs the hot air exhaust from the fan units at the front of the shelf out the back of the shelf.

Peripheral shelf cards

The following Peripheral shelf cards provide system management and switching capability:

• PSC card

16-2 15-2 14-2 13-2 12-2 11-2 10-2 9-2 6-2 5-2 4-2 3-2 2-2 1-2

16-2 15-2 14-2 13-2 12-2 11-2 10-2 9-2 6-2 5-2 4-2 3-2 2-2 1-2

1

2

3

4

8-2

Status

Active

ClockOut

CIC

Status

ClockA In

ClockB In

Facilities

1

2

3

4

Status

Active

ClockOut

CIC

Ext

erna

l Ala

rms

Ext

erna

l Ala

rms

Critical Alarm

Major Alarm

Minor Alarm

ACO/LT

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

OC3c-OC12c

STM1-STM4

Active

I/O Fault

Status

Control Control

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

1 2 3 4 5Control Card A Control Card A

6 7 8 9 10 11 12 13 14 15 16



A PowerA1 A2 A3 A4


A PowerB1 B2 B3 B4


Fan Unit 1 Fan Unit 2 Fan Unit 3

Active

I/O Fault

Status

Active

I/O Fault

Status

PSC Acard

PSC Bcard

Circuit-cardarea

CIC B CIC A

FICs

Circuit-cardarea

Facilitiescard

18068


98

The PSC card controls and monitors the Peripheral shelf and all of its components, including the PICs, Facilities cards, DFICs, QFICS, and line cards. It also monitors the display panels, fan trays, and power modules. Two PSC cards are installed on the front of the shelf to maintain communication with the Control shelf through a PIC installed on the back of the shelf.Two PSC cards and two PICs provide shelf controller redundancy. The PIC provides I/O connectivity on the back of the Peripheral shelf for the PSC card.Only one PSC/PIC pair is active at a time. The two PSC cards communicate with each other over the shelf midplane to determine which pair has fewer demerits. The pair with fewer demerits becomes the active pair.

• PICThe 7670 RSP uses two PICs in each Peripheral shelf. The PIC is connected to the Control shelf using a CSL. The CSL port on the PIC connects Peripheral shelves 2 to 15 to the Control shelf. The PIC also provides direct external Ethernet access to the PSC card. The PICs are installed at the back of the Peripheral shelf.

• DFICs and QFICsThe DFICs and QFICs used in a Peripheral shelf are the same as the DFICs and QFICs used on the Control shelf. DFICs and QFICs provide the Peripheral shelves and the Control shelf with connectivity to the Switching shelves through HISL ports. HISL cables enable traffic to flow between shelves. DFICs and QFICs also provide connectivity to the switching fabric for all line cards in the Peripheral shelves. DFICs and QFICs are installed in the fabric slots of the Control shelf and the other Peripheral shelves.The system can be configured to optimize the use of bandwidth according to the configuration of each shelf. The DFIC has two HISL ports that provide up to 28 Gb/s; the QFIC has four HISL ports that provide up to 56 Gb/s, doubling the fabric capacity.

• Facilities cardThe Facilities card used in each Peripheral shelf is the same as the Facilities card used on the Control shelf. The Facilities card provides an interface to the control card for node management and external alarm connections. The Facilities card is installed in a dedicated slot on the back of the shelf.The Facilities card has two variants: International and North American.The International variant has two BNC connectors for timing inputs of 2.048 MHz. The North American variant has two sets of three wire-wrap posts for BITS timing inputs.

See “Line cards and I/O cards” for information about supported line cards and I/O cards in the multishelf system.

In-service single-shelf to multishelf upgradeThe 7670 RSP supports the upgrade from a single-shelf configuration to a multishelf configuration while the node is in service. This upgrade relies on fabric redundancy to switch the 50 Gb/s fabric for a 450 Gb/s fabric. The single-shelf to multishelf configuration upgrade also involves installation of the multishelf control infrastructure.


99

The upgrade starts with two 50 Gb/s fabrics, X and Y. The X fabric is made active while the Y fabric is removed and a 450 Gb/s fabric on the Switching shelf is installed in its place. Then, a fabric switch is performed to make the 450 Gb/s Y fabric active. The 50 Gb/s X fabric is then removed and replaced with a second 450 Gb/s fabric, which completes the upgrade.

Line cards and I/O cardsThis section briefly describes the line cards used with the 7670 RSP.

Line cards

Line cards terminate Layer 2 and Layer 3 connected interfaces. The physical layer is terminated by an associated I/O card. Line cards terminate a variety of traffic types, including ATM, Ethernet, IP, IP over ATM, MPLS, and pseudowires. Traffic can be transported over Gigabit Ethernet, DS3, and SONET/SDH at OC3/STM1, OC12/STM4, and OC48/STM16 speeds.

Both the single-shelf and multishelf configurations of the 7670 RSP use the same line cards to provide the interface between the switching fabric and the I/O cards. Each line card supports one or two I/O cards. At the ingress of the switching fabric, the line cards direct traffic to the switch cards. At the egress of the switching fabric, the line cards select traffic intended for them and send it to the I/O cards.

The 7670 RSP supports the following line cards:

• Edge Services Card (ESC)• Multi-Rate 48 Channelized Multi-Protocol card (MR48)• Multi-Rate 16 ATM• Gigabit Ethernet• Multi-Rate 16 POS• Multi-Rate 8 ATM/IP• OC48c/STM16 ATM

Edge Services Card (ESC)

The ESC provides cell relay service over channelized OC3 or STM1 interfaces and OC12 or STM4 interfaces. Channelization is supported down to the T1 (DS1) or E1 level. In addition, the ESC supports inverse multiplexing over ATM (IMA) groups. Up to eight DS1/E1 circuits can be aggregated in an IMA group to provide scalable bandwidth. For more information on IMA groups, see “IMA” in Chapter 4.

The ESC also provides support for circuit-switched traffic through unstructured DS1 circuit emulation. This feature allows the ESC to adapt circuit-switched traffic to and from cell relay traffic at the AAL-1 layer.

The 4-port OC12/STM4 channelized I/O card uses two available ports to enable a direct connection between an ESC and a DCS. This direct connection eliminates the intermediate DCS, which allows the configuration of a simpler


100

network. The use of the OC12/STM4 channelized card allows operators to better manage 3G traffic volume, provides greater bandwidth between the RBOC PoP and the MTSO, and creates a more cost-effective system.

See Table 39 in Appendix B for details on the ESC line card features.

Multi-Rate 48 Channelized Multi-Protocol card

The MR48 line card provides ATM, IP, and MPLS services over ATM and POS channelized and unchannelized interfaces.

The MR48 line card can support up to 45 Mb/s on one physical port. The MR48 line card is versatile and can be configured to support a number of different I/Os and interface speeds. It also supports ATM (cell relay) and IP/POS (PPP) protocols.

The MR48 line card supports two interface modes: scaled and standard. Table 8 describes the features available for each of the interface modes.

Table 8: Comparison of standard and scaled interface modes

See Table 40 in Appendix B for details on the MR48 line card features.

Multi-Rate 16 ATM line card

The Multi-Rate 16 ATM line card provides cell relay services at the UNI and NNI.

See Table 41 in Appendix B for details on the Multi-Rate 16 ATM line card features.

Gigabit Ethernet line card

The Gigabit Ethernet line card provides a high-speed, packet-based interface that processes Ethernet packets.

Standard mode Scaled mode

Default mode of operation Manually configured or supported through an in-service upgrade

Supports 2000 Layer 3 interfaces of any type

Supports up to16 000 Layer 3 interfaces• supports up to 16 000 scheduled

interfaces (8-CoS-per-CoS RBE)• supports up to 1000 aggregate

or hierarchical interfaces (non-8-CoS-per-CoS RBE)

Supports LSPs Does not support LSPs

Supports a full range of IP statistics for all Layer 3 interfaces

Supports only unicast and multicast IP statistics on ingress and egress, for all Layer 3 interfaces

Supports IPv4 and IPv6 card modes Supports only IPv4 card mode


101

The Gigabit Ethernet line card supports Ethernet link aggregation as defined in IEEE 802.3ad. Link aggregation enables the aggregation of two Ethernet ports to form a LAG that is treated as a single logical Ethernet port. The 7670 RSP supports up to 64 LAGs per system. See “LAG with LACP” in Chapter 7.

See Table 42 in Appendix B for details on the Gigabit Ethernet line card features.

Multi-Rate 16 POS line card

The Multi-Rate16 POS line card provides IP and MPLS functionality over a packet and SONET physical port.

See Table 43 in Appendix B for details on the Multi-Rate 16 POS line card features.

Multi-Rate 8 ATM/IP line card

The Multi-Rate 8 ATM/IP line card provides cell relay service at the UNI and NNI on OC3c/STM1 and OC12c/STM4 I/O card interfaces.

This card also provides IP forwarding. High-performance, wire-speed IP packet classification and forwarding capabilities are available for IP and MPLS functionality.

See Table 44 in Appendix B for details on the Multi-Rate 8 ATM/IP line card features.

OC48c/STM16 SONET/SDH ATM line card

The OC48c/STM16 SONET/SDH ATM line card provides cell relay services at the NNI. It terminates one 1-port OC48c/STM16 ATM I/O card.

See Table 45 in Appendix B for details on the OC48c/STM16 ATM line card features.

I/O cards

The I/O cards provide an interface to the line cards. The 7670 RSP uses I/O cards for connecting to SONET-based and SDH-based network equipment. Depending on the card type, one, two, four, or eight optical or electrical ports are provided on each card. The external connector for the electrical I/O cards is an SMZ connector.

See Tables 46 and 47 in Appendix B for details on I/O and line card compatibility.

8-port DS3 I/O card

The 8-port DS3 I/O card has eight electrical interfaces. Up to two DS3 I/O cards can be associated with a Multi-Rate 16 ATM line card.


102

4-port OC3c/STM1 I/O card

The 4-port OC3c/STM1 I/O card terminates four physical OC3/STM1 interfaces. Up to two 4-port OC3c/STM1 I/O cards can be associated with one Multi-Rate 8 ATM/IP line card.

4-port STM1 Electrical I/O card

The 4-port STM1 Electrical I/O card has four electrical interfaces. Each interface has two coaxial cables: one for transmitting signals and one for receiving signals. This card can only be used with the Multi-Rate 8 ATM/IP line card.


The 8-port OC3c/STM1 I/O card terminates eight physical OC3/STM1 interfaces. Up to two 8-port OC3c/STM1 I/O cards can be associated with one Multi-Rate 16 ATM line card.

8-port OC3/STM1 I/O card

For use with the MR48 line card or with the ESC, the 8-port OC3/STM1 I/O card terminates eight physical OC3/STM1 optical interfaces. The I/O card terminates both ATM and IP/POS (PPP) protocol channels. Up to two I/O cards can be provisioned with an MR48 line card; one I/O card can be provisioned with an ESC.

8-port STM1 Electrical I/O card

The 8-port STM1 Electrical I/O card has eight electrical interfaces. Each interface has two coaxial cables: one for transmitting signals and one for receiving signals. This card can only be used with the Multi-Rate 16 ATM line card.

8-port STM1 Electrical MR48 I/O card

The 8-port STM1 Electrical MR48 I/O card terminates eight physical STM1 electrical interfaces. This card can only be used with the MR48 and ESC line cards. One MR48 line card supports two 8-port STM1 Electrical MR48 I/O cards. One ESC line card supports one 8-port STM1 Electrical MR48 I/O card.


The 1-port OC12c/STM4 I/O card terminates one physical OC12c/STM4 interface. Up to two OC12c/STM4 I/O cards can be associated with one Multi-Rate 8 ATM/IP line card.


The 2-port OC12c/STM4 I/O card terminates two physical OC12c/STM4 interfaces. Up to two OC12c/STM4 I/O cards can be associated with one Multi-Rate 16 ATM line card.


103

4-port OC12/STM4 Channelized I/O card

For use with the Channelized MR48 and ESC line cards, the 4-port OC12/STM4 Channelized I/O card terminates four physical OC12/STM4 interfaces. The 4-port OC12/STM4 Channelized I/O card supports ATM and IP/POS (PPP) protocol channels across 4 ports when used with the MR48 card, and supports ATM and UDT protocol channels across 2 ports when used with the ESC line card.


One OC48c/STM16 I/O card connects to one OC48/STM16 SONET/SDH ATM line card or one Multi-Rate 16 POS line card.

1-port OC48/STM16 Channelized I/O card

For use with the Channelized MR48 line card, the 1-port OC48/STM16 Channelized I/O card terminates one physical OC48/STM16 interface.

2-port Gigabit Ethernet I/O card

The 2-port Gigabit Ethernet I/O card provides two fiber-optic connections for connection to a Gigabit Ethernet line card. Up to two 2-port I/O cards can be associated with one Gigabit Ethernet line card.


104

105

7670 RSP system reliability and redundancy

This chapter provides an overview of the 7670 RSP reliability and redundancy features, including:

• “Infrastructure”• “Switching fabric redundancy”• “Control card redundancy”• “Power redundancy”• “Cooling redundancy”• “System timing redundancy”

• “Control plane redundancy”• “Non-stop PNNI”

• “Data plane redundancy”• “APS/LCR redundancy”• “LAG with LACP”• “Management interface redundancy”

7. 7670 RSP system reliability and redundancy

106

IntroductionThe 7670 RSP single-shelf and multishelf systems are fully redundant, achieving 99.999% platform availability and fulfilling SLAs with true carrier-grade reliability.

Each redundant component can be hot swapped without any impact on service. Mission-critical processes such as PNNI routing, IP routing, MPLS signaling, and ATM call processing are also 1+1 hot redundant.

Maintaining a separate control and data plane further enhances the redundancy of the 7670 RSP by ensuring full line-rate performance across all interfaces, while maintaining robustness of the control plane.

InfrastructureInfrastructure redundancy is ensured by implementing full hot redundancy for all 7670 RSP components: shelves, control cards, power and cooling system, and system timing. A more detailed description of the 7670 RSP components is provided in Chapter 6.

Switching fabric redundancy

The 7670 RSP uses two switching fabrics (X and Y) for switching fabric redundancy to ensure that traffic between line cards is not interrupted if a fabric failure occurs. Unlike some N:1 protection schemes that effectively result in a decrease of the system’s capacity, this feature enhances the reliability, availability, and serviceability of the platform and maintains 100% capacity at all times.

In the single-shelf and multishelf systems, the line card transmits incoming data to both switching fabric X and switching fabric Y. The line card accepts only outgoing traffic from the active switching fabric. The same error checks, diagnostics, monitoring, and statistics are performed on both the active and inactive fabrics.

If a fault occurs on the active fabric, activity automatically switches to the other fabric.

When both switching fabrics are functional, a forced activity switch may be required if the active fabric is in need of maintenance. A network or node management system can be used to force activity to the other fabric, even if it has faults. The fabric that has been forced to be active will remain active, even if it accumulates more demerits than the inactive fabric.

Switching fabric redundancy in a single-shelf system

In a single-shelf system, each Switch card supplies its own switching fabric. One Switch card is the active card, and the other is the inactive card. Both Switch cards receive incoming traffic, but the line cards accept outgoing traffic only from the active Switch card. This provides hot redundancy if the active Switch card fails.


107

The following events cause the 7670 RSP to switch to the inactive Switch card.

• The active Switch card is removed.• The active Switch card is reset through a node management or CLI session.• The active Switch card has more demerits than the inactive Switch card.• Activity is released through a node management or CLI session.• A failure occurs on the active Switch card.

Switching fabric redundancy in a multishelf system

A multishelf system requires two switching shelves, one for switching fabric X and one for switching fabric Y. Each fabric requires the following components:

• FIC• HISL• SAC• SSC card• SMX cards• SCH card

In a multishelf system, fabric redundancy ensures monitoring of all of the components on both the active and inactive switching fabrics. If the system detects a fault, it uses either the FAST or demerit method to select the active fabric. All fabric activity switches raise a diagnostic alarm.

Before evaluating switching fabric X and switching fabric Y for a potential activity switch, the redundancy subsystem checks for a fabric selection grace period. During system startup and commissioning, fabric redundancy allows a period of time in which demerits are counted but no fabric activity switch occurs. Table 9 describes the startup activities and the fabric selection grace period for each activity.

Table 9: Startup activities

Single, severe faults trigger a FAST fabric activity switch. The system can perform a FAST fabric activity switch only if it detects a single fault and both fabrics are fault-free. To minimize cell loss, a FAST fabric activity switch occurs in 60 ms or less. After a FAST fabric activity switch, the system uses demerits for any further fabric activity switches. The FAST fabric activity switch is re-enabled only after all fabric faults are cleared.

Activity Grace period

System startup 5 min

Addition of a Peripheral shelf or Switching shelf

1 min

CSL establishment or re-establishment 1 min

CC2G card or PSC card switchover 15 s

Fabric switchover 30 s


108

When the system detects faults on both fabrics, it uses demerits to select the active fabric. The system assigns demerit points to faults depending on their severity: the more severe the fault, the higher the number of demerits. The system selects the fabric with the least number of demerits as the active fabric. If both fabrics have the same number of demerit points assigned, then no fabric activity switch occurs.

Control card redundancy

The 7670 RSP uses two control cards for redundancy: one card is the active card, and the other is the inactive card. The 7670 RSP maintains the same control information on both cards, which provides hot redundancy if the active card fails. Control card redundancy includes 1+1 redundant call processing, billing, routing, network data collection, and node control.

The following events cause the 7670 RSP to switch to the inactive control card.

• The active control card is removed.• The CIC associated with the active control card is removed, and the other CIC

has fewer demerits.• The ICON card associated with the active control card is removed, and the

other ICON card has fewer demerits.• The active control card is reset through a node management session.• Activity is released through a node management session.• A failure occurs on the active control card.• The active control card has more demerits than the inactive card.

Some control card functions have hot redundancy or warm redundancy. Hot redundancy occurs when the system maintains information on the active and inactive control cards so that an activity switch has no impact on these service functions. During normal operation, the active control card sends the information to the inactive control card in real time to maintain hot redundancy. Warm redundancy occurs when the system maintains information only on the active control card, with inactive processors in hot standby. When an activity switch occurs, the newly active control card either retrieves the required information from the recently inactivated control card or recomputes the required information.

Table 10 describes the redundancy for the different control card functions.

Table 10: Control card function redundancies

Function Redundancy

Control Hot

Call processing Hot

PNNI routing Warm

ATM signaling (UNI 3.1, UNI 4.0, PNNI, IISP, AINI)

Hot

(1 of 2)


109

The active control card uses a demerit point system to monitor its own health and to compare its health to that of the inactive control card. If a fault occurs, the system assigns demerit points to the active card and, if the inactive card is healthier, may switch to the inactive card.

A node management session can be used to determine which control card is active and which is inactive. The status of the communication link between the active and inactive cards and the status of the node database can also be viewed using the CLI. As well, the active LEDs on the control card faceplates indicate status: green on the active control card and unlit on the inactive control card.

Control card redundancy is available only after the reset of the inactive control card is complete. After a control activity switch or reset of the active control card, the newly inactive control card automatically resets and reconciles its database with the active card.

PSC card redundancy

The PSC card controls and monitors the Peripheral shelf and all of its components, including the PICs, Facilities cards, FICs, and line cards. It also monitors the display panels, fan trays, and power modules.

The Peripheral shelf contains two PSC cards and two PICs to provide shelf controller redundancy. Only one PSC/PIC pair is active at a time. The two PSC cards communicate with each other over the shelf midplane to determine which pair has fewer demerits. The pair with fewer demerits becomes the active pair.

The following events cause the active PSC/PIC pair to switch to the inactive PSC/PIC pair:

• removal of the active PSC card or PIC card from the Peripheral shelf• a card reset of the active PSC card or PIC card due to card failure or power loss

or due to a hard reset

SSC card redundancy

The SSC card controls and monitors the Switching shelf and all of its components, including the SACs, SCH card, and SMX cards. It also monitors the display panels, fan trays, and power modules. The SSC card synchronizes timing to all of the devices on the Switching shelf.

MPLS signaling RSVP-TE Warm

MPLS signaling LDP Warm

IP routing Hot

ILMI Warm

Function Redundancy

(2 of 2)


110

The SSC card has two redundant CSLs to the control complex. The SSC ensures that the healthiest CSL is the active CSL. All control traffic between the control complex and the SSC card crosses the active CSL. The inactive CSL passes test traffic to validate the quality of the link.

Power redundancy

Each 7670 RSP shelf provides power redundancy by using two separately filtered power feeds (A and B), each with its own independent power source. Each shelf has discrete power zones, with each zone supplied by both feeds. Circuit breakers allow power from feeds A and B to be switched on or off for each of the four zones. A power zone does not need to be powered up if it is not in use.

Cooling redundancy

In a single-shelf system, the 7670 RSP uses six fan units for cooling redundancy; in a multishelf system, each 7670 RSP shelf uses three fan units for cooling redundancy. During normal conditions, the fans run at reduced speed. If a fan failure occurs or if the air temperature increases significantly, the operational fans speed up. Each fan unit is hot-swappable and can be replaced while the shelf remains in service.

System timing redundancy

The 7670 RSP can be configured to use up to four sources for its system timing. A timing source can be derived from a line rate of the interface or it can be provided externally, via timing inputs located on the Facilities card — two external inputs for BITS source (DS1) or 2.048 MHz clock signal (ITU-T G.703).

The 7670 RSP can be configured to use an automated revertive or a non-revertive mode of switching between programmed sources of system timing. If none of the configured timing values are present or valid, the 7670 RSP enters the holdover mode of operation using the last known timing information. If no timing information is available, the 7670 RSP enters a free-run mode of operation. The performance in free-run/holdover mode conforms to Stratum 3 level, as described in Telcordia (formerly Bellcore) GR-1244-CORE.

The 7670 RSP provides two timing outputs (8KHz, 2.048 MHz), which can be used to provide timing reference to collocated equipment.


111

Control plane redundancyThe 7670 RSP supports unsurpassed control plane redundancy for both IP/MPLS and ATM. Mechanisms supported include:

• non-stop routing• non-stop MPLS • graceful restart helper for BGP and OSPF to facilitate interoperability with

third-party vendors• non-stop PNNI• hitless addition and deletion of IMA links to and from an IMA group

See Chapter 5 for descriptions of non-stop routing, non-stop MPLS, and graceful restart helper functions. See Chapter 4 for information on IMA.

Non-stop PNNI

PNNI activity switches occur when a system performs a control activity switch.

The PNNI application uses 1+1 warm redundancy. Warm redundancy indicates that PNNI routing on the redundant control card must rediscover the links to neighbor nodes and rebuild its link state database on startup.

Existing SVC calls and SPVCs are not affected by a control card activity switch. During an activity switch, new SVCs in the process of being established are routed by the existing PNNI routing tables that were downloaded to the control cards before the activity switch occurred. After an activity switch, the PNNI application suppresses changes to the call processing routing tables on the control cards until a sufficient view of the network has been achieved, or until a threshold time limit has passed. The routing table suppression is performed to cause the least disruption to the existing routing tables on the control cards. The routing table values that the newly active control card calculates may be identical to those of the previously active card.

Data plane redundancyData plane redundancy is ensured by the implementation of line card redundancy, APS (port) redundancy, and link aggregation management with LACP.

APS/LCR redundancy

The 7670 RSP supports APS (port) redundancy through port protection groups. A port protection group consists of a pair of corresponding ports on two I/O cards. One port is configured and operates as the working port; the other port is the protection port. The traffic flowing through the working port is switched to flow through the protection port when required.

The 7670 RSP also supports line card redundancy (LCR) by deploying two line cards of the same type in adjacent slots. One line card is configured and operates as the working card; the other card is the protection card. The traffic


112

flowing through the working card is switched to flow through the protection card when required. Line card redundancy is also known as equipment protection switching (EPS).

The 7670 RSP also supports 1+1 protection with G.841 Annex B port redundancy. G.841Annex B provides a 1+1 bidirectional protection protocol that is optimized for a network using 1+1 bidirectional switching. The Annex B protocol is specified in ITU-T G.841 and configurable for both SONET and SDH networks.

With APS and LCR, Layer 2 and Layer 3 services are protected without an impact on the control plane or on the data plane.

LAG with LACP

Link aggregation or trunking is a method of combining physical network links into a single logical link for increased bandwidth. Two Gigabit Ethernet ports are combined in order to increase the bandwidth capability or to create resilient and redundant links.

In order to interoperate with different protection schemes, LAGs on the 7670 RSP can operate in either load-sharing mode or active/standby mode.

LAGs are fully control-redundant. Because any LAG configuration is immediately propagated to the inactive control card, LAGs operating with or without LACP are unaffected by a control card activity switch.

LACP provides a convenient way to manage and detect link aggregation capabilities between partner systems and to detect a link failure. Link information is exchanged between local and remote nodes in order to reach agreement on the identity of the LAG.

The LACP mode (active or passive) and LACP timeout can be configured on the 7670 RSP against each LAG on a local node. To detect link failures, at least one LAG must be configured with LACP in active mode. If a port is removed from a LAG that is configured in active mode at either end of the link, the partner system detects a periodic transmission failure and the link goes down. If the configured LACP mode on a LAG is changed while the link status is up and in service, there is no traffic interruption.

The LACP timeout is configured as either short or long. The timeout value is used to determine the rate at which the local system must transmit and receive periodic LACP messages before a link is declared down. By default, a LAG on the 7670 RSP is configured for short timeouts so that link failures can be detected quickly. The configured timeout value can be changed without any traffic interruption.

Management interface redundancy

The 7670 RSP provides redundancy for management connections made over Ethernet, ATM, and serial interfaces.


113

Node and network management connections over Ethernet interfaces use the CIC to connect to the 7670 RSP single shelf or to the control shelf in a multishelf system. Two CICs, each with its own Ethernet connection, provide Ethernet interface redundancy.

Network management connections over ATM use I/O card ports and line cards to connect to the 7670 RSP. Line card and port redundancy provide ATM interface redundancy.

Node management connections over serial interfaces use a serial port on the control card or Facilities card. Each control card has a serial port to provide serial interface redundancy.

Soft restart on software upgrades

In systems that use line card redundancy, service providers can upgrade software on any line card without disrupting service to their customers. In systems that use non-redundant line cards, the software is designed in a modular fashion to enable soft-reset functionality.


114

115

7670 RSP security features

This chapter provides an overview of the 7670 RSP security features, including:

• “Platform security”• “Hardened real-time operating system”• “Multiprocessor availability”• “Separate routing and signaling plane”• “DoS resiliency”• “Non-stop services”• “Resource utilization metering”

• “Data plane security”• “Access lists for traffic filtering or rate limiting on TCP flags”

• “Routing plane security”• “Resistance to denial of service attacks”• “Network control plane”• “IP routing and signaling security”• “MD5 authentication between routing peers”• “Per-IP-flow rate limiting and IP CoS differentiation based on multifield

classification”

8. 7670 RSP security features

116

• “Management plane security”• “Improved user login authentication and support for RADIUS”• “Secure protocols for node management”• “CLI security through SSH”• “File transfer security using SFTP”• “Node management security through SNMP v3”• “Encrypted configuration databases”• “Cryptographic algorithms”• “Secured local storage of passwords”• “Event logging”

• “Combatting security threats”

IntroductionService providers require secure networks and information systems that are able to resist, at a given level of confidence, accidental events or malicious actions that compromise the availability, authenticity, and confidentiality of stored or transmitted data, and the related services offered or accessible through their networks.

Security is fundamental to the design of the 7670 RSP. The platform embeds appropriate security technologies at every level: platform level, data plane, routing plane, and management plane.

Platform securityThe 7670 RSP is a platform designed to provide high-availability, reliable, and secure carrier-grade services with guaranteed data integrity. The security features detailed below have been integrated into the 7670 RSP platform to ensure secure data transmission and resiliency to malicious attacks.

Hardened real-time operating system

A hardened real-time OS must have a pre-emptible kernel, low interrupt response latency, and rigorous determinism and be able to prioritize tasks unerringly. It should provide true real-time, built-in, high-availability features as well as advanced support for distributed systems, and make the most efficient use of system resources and CPU capacity.

Multitasking as a general characteristic of a real-time OS is enabled on the 7670 RSP. The ability to run different tasks simultaneously, such as FIB calculation, processing of routing protocols, or log collection, is provided on the platform. Scalability and timely response are guaranteed with the platform’s task-dedicated multiple CPUs. The 7670 RSP real-time OS coordinates the tasks and aggregates the output, as well as prioritizes certain tasks over others as required.


117

Multiprocessor availability

Multiple processors isolate an attack impact and improve denial of service (DoS) survivability. For example, an attack on the management processes does not affect the routing process.

Separate routing and signaling plane

The 7670 RSP offers excellent throughput performance because it separates routing and system functions from the cell and packet forwarding functions. The forwarding functions are distributed on each line card, enabling wire-speed IP forwarding performance on each interface.

DoS resiliency

Reverse path filtering (RPF) is a security feature that can be used as part of a network strategy to protect against various attacks such as DoS and DDoS. As many host and router attacks rely on a spoofed or false IP source address, RPF can be used at the edge of a network to help prevent these spoofed addresses.

RPF operates in the data path by examining the IP source address of each packet. A lookup is performed in the FIB using the IP source address. If the lookup is not successful, the packet fails the RPF check and is not forwarded into the network. The packet is simply counted and then discarded.

Non-stop services

The non-stop services features of the 7670 RSP improve the reliability of IP services. Non-stop services are divided into two categories:

• non-stop routing services: static routing, RIP, OSPF, BGP, static multicast routing, PIM-SM, PIM-SSM, and IS-IS

• non-stop signaling services

With the introduction of the non-stop services features—a combination of hardware and software that is the foundation for delivering reliable carrier grade IP solutions—service providers can improve the quality of IP services by eliminating network disruptions caused by software upgrades. Non-stop services on the 7670 RSP have been independently tested and validated by BTexact Technologies.

Resource utilization metering

The resource utilization meter feature provides statistical metrics for the CPU and memory resources on any of the following cards in the 7670 RSP system:

• line cards• control cards• PSC cards• ICON cards• SSC cards


118

This feature enables the detection of unusual resource consumption that can indicate a card problem.

CPUs are used to run user tasks and operating system tasks and to handle interrupts. Statistics are kept on the CPU usage of each processor, including processors on cards that are in protection status.

Statistics for each processor are recorded and stored in real time. The statistics are recorded in 10-second intervals and are reported for the last complete 10-second interval, 1-minute interval, and 5-minute interval.

Data plane securityThe security of traffic routed through the 7670 RSP is ensured by the application of authorization through access lists and multi-level administration access. Access lists are a powerful method of filtering traffic or blocking traffic access to some resources. On the 7670 RSP, IP routing and signaling security is ensured through access lists for traffic filtering and rate limiting on TCP flags.

Access lists for traffic filtering or rate limiting on TCP flags

For security purposes, access lists can be configured on the 7670 RSP in the following ways:

• access lists for traffic filteringAccess lists based on source/destination address or port, protocol, and TCP flags, can be deployed to block the access of designated traffic to some specific resources on the network or to allow some traffic to access particular resources while blocking all the rest.

• access lists for rate limitingAccess lists can be used for IP traffic rate limiting. IP traffic that matches an access list can be limited to a specified rate. The rate limiting of IP traffic ensures that traffic destined for a particular resource, or traffic coming from a particular resource, or traffic of a particular kind (for example, ICMP traffic) is limited with an upper value for priority purposes.

Access list statistics

When logging is enabled, the number of times an access rule is matched is counted.

If the rate limit action and logging of a rule are enabled, then two statistical counters are activated: one is kept for the number of packets that are allowed to proceed, and another one is kept for the number of packets that are discarded as a result of the traffic rate exceeding the configured packet rate.

Packet filtering and packet copying of traffic

When a rule is matched, and packet copying is enabled, a minimum of 44 bytes starting with the IP header to a maximum of 112 bytes, are copied to an on-card circular buffer to enable further retrieval and examination.


119

Access list statistics logging and packet copying can be enabled or disabled according to preset rules, and applied independently of each other.

Routing plane securityTo effectively deliver IP-based applications and services to users, enterprises need networks that are self-healing from intrusions, such as viruses and DoS attacks. The intrusion threats facing networks today are varied and ever-evolving, making it imperative that the various security systems in an enterprise work together.

Resistance to denial of service attacks

Comprehensive automated subscriber and service-level security features have been added. Service providers are able to establish thousands of anti-spoofing security filtering rules to prevent theft of content or services and to contain service-impacting user-to-user and infrastructure-level DoS attacks.

Access to the routing plane is controlled by strengthening the resistance to DoS attacks. Table 11 lists several DoS attacks and corresponding countermeasures on the 7670 RSP.

Table 11: DoS countermeasures on the 7670 RSP

Network control plane

The following protocols are used to ensure secure transmission:

• Q.2931• PNNI• RSVP (MD5)• LDP (MD5)

IP routing and signaling security

All routing updates destined for the 7670 RSP are automatically assigned to the highest CoS (CoS-1) at the ingress interface. This way, it is guaranteed that routing packets are always serviced before any other traffic.

Type of DoS attack

Description Countermeasure

Ping of death Large ICMP echo request Hardened in stack

Smurf ICMP echo request to broadcast address

Blackhole routes for martian addresses

Land Src Adr/Port = Dst Adr/Port Hardened in stack

TCP syn flood Half-open sessions Node does not crash

Teardrop Fragmented malformed packets

Hardened in stack


120

IP routing and signaling security is managed through protocol authentication. The following protocols are used:

• OSPF (MD5)• BGP-4 (MD5)• IS-IS (MD5)• PNNI• RPF

MD5 authentication between routing peers

Authentication between routing peers is a measure of precaution taken against hackers who might otherwise present themselves as one of the routing peers and feed the network false routing information, which can cause network instability.

The 7670 RSP implements the following MD5 authentication requirements:

• TCP MD5 signature option for protection of BGP-4 sessions• OSPF/IS-IS/RIP neighbor router authentication• a different key for each interface and routing protocol type

Per-IP-flow rate limiting and IP CoS differentiation based on multifield classification

When incoming routing packets destined for the 7670 RSP are detected as routing packets, they are automatically assigned to the highest CoS.

In order to assign packets to different queues, it is necessary to turn on the multifield classification (MFC) feature, and specify the parameters that will govern the rules by which packets are to be assigned to different CoS. The MFC parameters are the source and destination IP address or port and the routing protocol.

Routed packets are assigned automatic priority by the 7670 RSP. All other traffic can be prioritized by the operator.

Rate limiting and CoS differentiation enable the service provider to manage traffic securely and to guarantee obligations under SLAs.

Management plane securityThe 7670 RSP offers service providers the following features for securing the management plane:

• improved user login authentication and support for Remote Authentication Dial-In User Service (RADIUS)

• secure protocols for node management• event logging


121

With these features, service providers can have confidence that they can control access to the management plane (which includes management of the node through CLI and SNMP) and the data plane, protect access to node information, and preserve the integrity of control and management information during its transmission. Furthermore, service providers can collect and analyze performance, management, and traffic records in order to detect any potential system compromise.

All of these features can be enabled at the service provider’s discretion, giving them the flexibility to enforce the level of security that meets their needs.

Improved user login authentication and support for RADIUS

To improve node security, the concept of unique users was introduced, each with an individual username and password. This means that individual node users can be assigned different node access levels and corresponding privileges, such as read-write or read-only. The 7670 RSP also supports the ability to enforce complex passwords, which are more secure than regular passwords.

To be authenticated to use a 7670 RSP, each user must be assigned:

• a unique login username• one or more access levels• privileges that correspond to the assigned access level or levels

Service providers determine how many users to add and what access levels and privileges to assign to each user. One 7670 RSP can support up to 100 users. The access levels that can be assigned are: operator, maintenance, administrator, security, and support.

Authenticating user access to the node is performed either locally against the node database or externally using a RADIUS server. Either the node or the RADIUS server can be used to control and manage all user-attempted logins to the 7670 RSP.

Login authentication using the node database

When RADIUS authentication is disabled, the node verifies user login using its own login table stored in its database. One 7670 RSP node supports a maximum of 100 user accounts.

Login authentication using a RADIUS server

RADIUS is an access server authentication, authorization, and accounting (AAA) protocol. It provides a standardized method of exchanging information between a RADIUS client (located on the 7670 RSP) and a RADIUS server (located externally to the 7670 RSP). RADIUS functionality is transparent to users who are logging in to a node that has RADIUS authentication enabled.


122

With RADIUS authentication, RADIUS provides an extra layer of login security on the 7670 RSP. The RADIUS client relays the user login and password, both encrypted using MD5, to the RADIUS server. The server authenticates the user and returns to the RADIUS client the user access level and privilege information necessary for the node to grant or refuse access to the user.

RADIUS also makes it easier for customers with large numbers of nodes in service to manage and maintain user login and password information. The customer can centralize an existing user database that can be used to access all nodes for that customer, rather than having to maintain a separate database for each node.

With RADIUS accounting, it is possible to track the number of users who have been granted access to the node through the RADIUS server, the number of users who have been refused node access through the RADIUS server, and the number of timeouts for each RADIUS server.

The 7670 RSP supports the following RADIUS standards:

• RFC 2618 RADIUS Authentication Client MIB• RFC 2620 RADIUS Accounting Client MIB• RFC 2865 Remote Authentication Dial In User Service (RADIUS)• RFC 2866 RADIUS Accounting

Secure protocols for node management

With its open management architecture, the 7670 RSP can be managed remotely by SNMP or by remote CLI access through Telnet. As well, files such as software downloads, database backups and restores, CLI configuration, trace logs, and security logs can be transferred to and from the node using FTP. The 7670 RSP secures its open management architecture by supporting the following secure protocols for management traffic:

• SSH• SFTP• SNMP v3

Securing remote access to the node meets the following needs:

• privacyInformation sent to and from the 7670 RSP must be encrypted to prevent any third party from reading it. The system maintains privacy through the use of symmetric key encryption algorithms.

• integrity of dataInformation sent to and from the 7670 RSP must be protected against corruption by a malicious attacker. Integrity is maintained through the use of cryptographic hash algorithms known as message digests.


123

• authenticityWhen the 7670 RSP is downloading files to a file server, the 7670 RSP is considered the client and the file server is considered the server. A client wishing to connect to a server must be sure that the server is who it says it is, to ensure that sensitive information is not sent to a corrupt server. The control path security system authenticates the 7670 RSP to a client and authenticates a server to the 7670 RSP through the use of asymmetric (public) key encryption algorithms.

CLI security through SSH

The 7670 RSP can be managed remotely through the CLI. Access to the CLI can be through a Telnet session or, for enhanced security, through an SSH session. SSH can replace Telnet for both in-band and out-of-band communication with the 7670 RSP.

File transfer security using SFTP

File transfers can be configured individually using FTP or, for enhanced security, using SFTP. Secure transfer using SFTP can be through in-band or out-of-band IP. Files transferred to and from the 7670 RSP include database backup and restore files, software downloads, CLI configurations, trace logs, and security logs.

SFTP is a secure file transfer protocol that is integrated into SSH; that is, the file transfer is performed over a secure SSH session. The remote file server must have SSH version 2 server software installed.

The 7670 RSP uses the same cryptographic algorithms for secure file transfer as those used for SSH.

Node management security through SNMP v3

The 7670 RSP supports SNMP v3 in accordance with RFC 2571, RFC 2572, RFC 2573, RFC 2574, RFC 2575, and RFC 2576. Support for SNMP v3 implicitly includes support for SNMP v1 and SNMP v2c. Support for SNMP v3 enables the secure management of the 7670 RSP by an SNMP manager, increasing the robustness and security of the node management infrastructure. Where SNMP v1 and SNMP v2c use clear text strings (known as community strings) as a crude security mechanism, SNMP v3 includes enhanced security by using authentication, privacy, and access control.

Encrypted configuration databases

The control card can keep the configuration file in encrypted format as an additional security measure in cases where the configuration data need to be kept confidential and accessible only with a password. When the configuration file is encrypted, any unauthorized attempt to download the file is denied.


124

Cryptographic algorithms

The 7670 RSP supports the following symmetric key encryption algorithms to protect privacy of information:

• 3TDES (CBC mode, 168-bit key)• Blowfish (CBC mode, 128-bit key)• RC4 (128-bit key)• AES (CBC mode, 128-bit key)

The 7670 RSP maintains integrity of information through the use of cryptographic hash algorithms known as message digests. A series of nested message digests creates a hashed message authentication code. The 7670 RSP supports HMAC-MD5 and HMAC-SHA-1.

The 7670 RSP ensures its authenticity through the use of public key algorithms.

Public key management

Public key cryptography enables a client to verify the authenticity of a server. The server generates a public and private key pair. The public key is given to any clients needing to connect with the server. The private key is known only to the server.

Generating public and private key pairs for the 7670 RSP can be done through the CLI. When the public and private key pairs are generated, they are stored in the control card database. The private key cannot be accessed by users.

As a server, the 7670 RSP exports public keys to clients who want to access the node. As a client, the 7670 RSP imports public keys from the file servers in order to perform secure file transfers.

The 7670 RSP supports the DSA public/private key algorithm.

Secured local storage of passwords

In addition to the external authentication of passwords by a RADIUS server, login passwords for the 7670 RSP can be encrypted locally (as plain text) for enhanced security. With the additional local encryption, the login password must be authenticated twice before access is granted.

Event logging

The 7670 RSP offers event logging as another method of addressing security concerns. Event logging gives service providers the ability to record and view what is happening on the node as a way of detecting any misuse of resources. With event logging, the node records security events and user activities (audit events).


125

Security events are events that pertain to the node. They can include events such as user account creation and modification, changes in security configuration, user login attempts, card resets, database backup and restores, and software downloads. Security events are stored in a security event log that can be either buffered or spooled.

Audit events are any CLI commands that a user enters and executes on a node. Each audit event, along with a corresponding username, is stored in an audit event log that can be either buffered or spooled.

Events that are stored in a buffered log can be kept on the node, or they can be sent by FTP or SFTP for backup on an external node. Alternatively, service providers may choose to spool their event logs. When configured for spooled logging, the node automatically sends the spooled logs to a syslog server—a network host that accepts and processes logged events. The ability to spool event logs to a syslog server simplifies event log management for service providers who have a large number of nodes in their network.

A user with security access to the node can review a security event log to check for any signs of system compromise, use the log to troubleshoot the node, or cross-reference the log with SNMP traps and alarms for more detailed information. In addition, a user with security access can review an audit event log to monitor user activity on the node. The information can help determine if a user is performing normal, routine duties on the node or if the user’s intention is malicious.

Additional security log events

Additional security log events include:

• access list configuration changes• SNMP configuration changes• access list filter matches

Redundant syslog servers for event logging

To improve the collection and analysis of performance, management, and traffic records to detect misuse, the event logging feature has been enhanced to support spooling to two syslog servers. Each server can be configured to receive both spooled security logs and spooled audit logs, thus providing redundancy. Alternatively, each server can be configured to receive either spooled security logs or spooled audit logs, enabling the separation of security events from audit events.

The event logging feature is also enhanced to include the time zone in the timestamp of all log events in the security and audit logs. This applies to both buffered and spooled logs.

The redundant syslog servers offer the benefit of total security in event logging and storage on the 7670 RSP. This enables non-stop monitoring of the system for signs of system compromise, with access to logs for troubleshooting the node, or the ability to cross-reference the log with the SNMP traps and alarms.


126

Combatting security threatsTable 12 lists some ways to protect the 7670 RSP against common security threats.

Table 12: Solutions to common threats to the 7670 RSP

Threat Solution

Unauthorized access to node, network control, and data

Authenticated CLI, RADIUS

Assumed identities (masquerading), spoofing

Access lists, network ingress filtering, subnet spoofing prevention

Eavesdropping, replay Encryption, one-time passwords

Covert channels, modification of protocols

MD5 authentication

Back doors Close ports, authenticated access

Denial of service Access lists, rate limiting

Component of power failure High availability and redundancy

Flaws in hardware, software, or firmware

Continuous process improvement, reviews, testing

Internal personal abuse of network resources

Syslog, multi-level administration access

127

7670 RSP system management

This chapter provides an overview of the 7670 RSP system management features, including:

• “Integrated Layer 2 and Layer 3 management”• “External management”

• “SNMP”• “CLI”• “5620 NM”

• “Internal management”• “Control card”• “Database”• “System timing”• “Indicators”

9. 7670 RSP system management

128

Integrated Layer 2 and Layer 3 managementThe 7670 RSP is managed by the 5620 Network Manager, which effectively manages a wide range of technologies. The ability of the 5620 NM to combine multiple access types over a multiprotocol core (such as IP, MPLS, or ATM) helps customers to meet the challenges of network consolidation.

Once an operator becomes familiar with using the 5620 NM for one service, management of any other service is easily extended without the overhead of new management systems. In addition, operational expenses decrease because no new training is needed when new technologies are added, and significant reductions in provisioning time and effort can be realized. In fact, time and motion lab studies conducted at Alcatel-Lucent have demonstrated an up to 50% decrease in provisioning and fault isolation time using the 5620 NM. Flow-through provisioning and activation rates using 5620 NM automation were 20 per minute or 10 000 per day.

The effects of provisioning errors in a network may be significant. For every provisioning error, not only must the error be detected and isolated, but time and effort must be spent to reprovision. There is almost always a cost attributable to the error condition, whether in SLA refunds, use of off-network capacity, or prior overprovisioning to compensate. Automated provisioning increases accuracy and efficiency by reducing sources of human error and streamlining the workflow of network operations, which in turn reduce operational expenses by increasing human productivity and reducing provisioning time.

Nodal characteristics can play a significant role in simplifying and reducing workflow for provisioning and fault management. Most important are those features that:

• reduce the number of assemblies and provisioning actions required (accomplished through channelized and multiprotocol interfaces)

• create statistics or fault reports that can be automatically analyzed and flagged (accomplished through diagnostics and OAM functions for all services)

• increase the serviceability of components (accomplished through hitless upgrades and field-replaceable units)

The 5620 NM provides the leading management solution to reduce errors and improve automation and extends its value of provisioning, fault management, and performance management to include Layer 3 in addition to Layer 2.

For information about how to use and maintain the 5620 NM, see the Alcatel-Lucent 5620 Network Manager User Guide.

External managementThe 7670 RSP system is managed locally or remotely with SNMP, the CLI, or by the 5620 NM.


129

SNMP

SNMP is used to control and monitor the 7670 RSP. SNMP is used by the 5620 NM and by third-party network management tools. The 7670 RSP supports SNMP v1, SNMP v2c, and SNMP v3.

SNMP inform message is also supported to guarantee successful event notification.

CLI

The command line interface (CLI) is used to configure, monitor, and troubleshoot the 7670 RSP.

5620 NM

The 5620 NM is an industry-leading network and management platform, distinguished by its open, scalable, highly available, multi-access and multi-technology management capabilities. The 5620 NM provides unsurpassed scalability and flexibility. It can manage networks of any size, each containing thousands of nodes.

Network management functions

The network manager performs the following functions:

• fault management• configuration management• accounting• performance management• security functions

Actions

The network manager performs the following actions:

• network operation monitoring in real time• setup and management of end-to-end connections• diagnostics• backup and restore of node database• software upgrades• problem isolation and management

Internal managementThe management of the 7670 RSP is consolidated on the control card.


130

Control card

The control card manages the system according to the following principles.

• The control card runs application and service card software components. • The control card receives reports on events from the application cards and

makes decisions on actions to take.• The inactive card cannot become active prior to the active card being removed

or reset. When the active card is removed or reset, there is an automatic switchover of activity to the inactive card. This applies to control, fabric, and interface redundancy.

Administrative layer

The administrative layer resides only on the control cards and is responsible for overall decision-making within the 7670 RSP control application. The application environment is responsible for much of the 7670 RSP control application’s decision-making. It defines an environment in which application modules (AM) carry out device- and application-specific activities in response to:

• management requestsThis includes external network and element managers using a supported protocol such as NCI or SNMP as well as CLI.

• system eventsThis includes device status changes (due to either failures or external events).

AMs provide a consistent interface for management entities to access configuration and status information for all system components. These include access to information in the system database. AMs do not typically directly control system resources, such as devices, when a management configuration change request is received. Instead, the AM usually updates the database with the requested change and then passes the request along to another software component responsible for making the change.

Resource layer

The resource layer resides on all cards in the 7670 RSP and is responsible for making administrative layer decisions and for reporting significant occurrences within the platform to the administrative layer so that it can determine what, if any, actions are required. The resources managed by this layer include physical devices, such as ports and cards, and logical software resources, such as control redundancy, software download servers, and slot monitoring software components.

Each card has its own card-specific and/or standard resources, which are managed locally by the card’s own resource layer. Each card contains a control processor (CTL server), which contains card application module (CAM) objects. The CTL server and the CAMs accept requests from the administrative layer and make the changes, possibly using the services of other components


131

in the card’s layer. There is typically a one-to-one correspondence between AM objects in the system’s administrative layer and CAM objects in a card’s resource layer.

Database

The control card contains a database on a 1 Gbyte flash disk. The following summarizes the database functionality.

• The node database stores all the configuration and connections programmed on the switch. The configuration settings and connections are automatically re-established after a system or card reset.

• Changes to the node database generally take effect immediately. A node or card reset should not be required for most changes.

• While the node tries to carry out the request of the management entities, it is responsible for maintaining a “sane” database and will refuse management requests that lead to database inconsistencies.

• The control card default database handshake mechanism is a means to ensure that, in a control redundant system, only the card with a sound database comes up as the active control card (and its database is used), and if a card has a default database, it is forced to be the inactive card.

• Database backup and restore are maintenance operations that enable customers to store a copy of the node database on a remote file server as a method of preparation for disaster recovery. In the event of a disaster, the node database can be restored from the remote file server where a backed-up copy resides.

Database conversion

The database conversion component of the software is added to enable the control card to convert a database created by a previous release of software to work with the current release. Database conversion is executed on an attribute-by-attribute basis and can be invoked by:

• restoration of a database backed up by previous releases of software to systems running the current release

• reconciliation of the database, where an active control card running an older release of software transfers its database to an inactive control card running the current release of software

• propagation of a database update from the active node controller to the inactive node controller during system upgrade of a control redundant system. Database conversion happens in this scenario only when the inactive controller is the newer software release and the active controller is one of the releases supported by the newer release for database conversion. Database conversion is only performed when the software major or minor version changes.

System timing

The 7670 RSP uses system timing to synchronize with the network. The SSU on the control card provides the system timing for the 7670 RSP.


132

Indicators

Each 7670 RSP shelf has indicators in the form of LEDs and alarms.

LEDs

The 7670 RSP uses LEDs to identify and isolate system faults quickly and easily.

Alarms

The 7670 RSP generates alarms to track and report faults. If a fault occurs, the 7670 RSP generates an alarm record. Alarm records are stored in one of the following alarm queues, according to the severity of the alarm condition:

• critical• major• minor• diagnostic

133

7670 RSP standards compliance and specifications

The 7670 RSP complies with the standards and specifications listed in the following tables:

• “Standards compliance”• “IP/MPLS standards compliance”• “ATM standards compliance”• “SNMP standards compliance”• “Interface compliance specifications for SONET and SDH cards”• “Optical parameters for the receive port on Gigabit Ethernet cards”• “Optical parameters for the transmit port on Gigabit Ethernet cards”• “Operating distance for Gigabit Ethernet cards”• “Optical parameters for the receive port on OC3 and STM1 cards”• “Optical parameters for the transmit port on OC3 and STM1 cards”• “Optical parameters for the receive port on OC12 and STM4 cards”• “Optical parameters for the transmit port on OC12 and STM4 cards”• “Optical parameters for the transmit port on OC48c and STM16 cards”• “Optical parameters for the receive port on OC48c and STM16 cards”• “DS3 and OC3c/STM1 electrical transmission information”• “Physical specifications for the shelves”• “Multishelf configuration specifications”• “Circuit-card area components of a single-shelf system”• “Circuit-card area components of the Control shelf”

A. 7670 RSP standards compliance and specifications

134

• “Circuit-card area components of the Switching shelf”• “Circuit-card area components of the Peripheral shelf”• “Physical specifications for the exhaust deflector tray”• “Power consumption of 7670 RSP components”• “Site specifications”


135

Table 13: Standards compliance

Category Standard or recommendation

Environmental and NEBS GR-63-COREGR-1089-COREETSI EN 300 019-2-1: Equipment Class 1.2ETSI EN 300 019-2-2: Equipment Class 2.3ETSI EN 300 019-2-3: Equipment Class 3.2

Timing/Synchronization Telcordia GR-1244 Issue 3Telcordia GR-253 Issue 4ITU-T G.957 ITU-T G.825

EMC GR-1089-CORE Class AFCC Part 15 Class AEN55022 Class BICES-003 Class AEN300-386 Class BAS/NZS 3548 Class A (Australia)MIC Notice No.2001-115 (South Korea)MIC Notice No.2001-116 (South Korea)

Safety CSA C22.2 No.60950-1UL 60950-1FDA CDRH 21-CFR 1040EN 60950-1EN 60825-1AS/NZS 60950


136

Table 14: IP/MPLS standards compliance

Routing protocol Standard Title

IP general RFC 768 User Datagram Protocol

RFC 791 Internet Protocol (1)

RFC 792 Internet Control Message Protocol

RFC 793 Transmission Control Protocol

RFC 854 Telnet Protocol Specification

RFC 1122 Requirements for Internet Hosts – Communication Layers

RFC 1305 Network Time Protocol

RFC 1518 An Architecture for IP Address Allocation with CIDR

RFC 1519 Classless Inter-domain Routing (CIDR): an Address Assignment and Integration Strategy

RFC 1573 Evolution of the Interfaces Group of MIB-II

RFC 1577 Inverse ATM ARP

RFC 1812 Requirements for IP Version 4 Routers

RFC 2011 SNMPv2 Management Information Base for the Internet Protocol using SMIv2

RFC 2096 IP Forwarding Table MIB

RFC 2113 IP Router Alert Option

RFC 2233 The Interfaces Group MIB using SMIv2

RFC 2236 Internet Group Management Protocol, Version 2

RFC 2362 Protocol Independent Multicast-Sparse Mode (PIM-SM): Protocol Specification, Version 2

RFC 2644 Changing the Default for Directed Broadcasts in Routers

RFC 2684 (obsoletes RFC 1483) Multiprotocol Encapsulation over ATM Adaptation Layer 5

RFC 3021 Using 31-Bit Prefixes on IPv4 Point-to-Point Links

draft-ietf-pim-sm-v2-new-09.txt Protocol Independent Multicast - Sparse Mode (PIM-SM: Protocol Specification (Revised)

(1 of 7)


137

IP version 6 RFC 1981 IPv6 path MTU

RFC 2283 Multiprotocol extension for BGP4

RFC 2375 IPv6 multicast addresses

RFC 2460 IPv6 protocol

RFC 2462 Stateless autoconfiguration

RFC 2464 IPv6 over Ethernet

RFC 2472 Definition of the DS field in the IPv4 and IPv6 header

RFC 2492 IPv6 over ATM

RFC 2597 An assured forwarding PHB

RFC 2710 IPv6 MLD

RFC 3246 An expedited forwarding PHB

RFC 3484 Default address selection

RFC 3587 IPv6 global unicast address

RFC 4007 IPv6 address scoping

RFC 4291 IPv6 addressing architecture

RFC 4659 6VPE

draft-ietf-ipngwg-icmp-v3-07.txt ICMPv6

draft-ietf-ipv6-2461bis-04.txt IPv6 neighbor discovery

draft-ietf-ipv6-node-requirements-11.txt IPv6 node requirements

draft-ietf-ipv6-addr-arch-v4-04.txt IPv6 address architecture

draft-ietf-ipv6-rfc2011-update-10.txt IPv6 MIB

draft-ooms-v6ops-bgp-tunnel-05.txt 6PE


(2 of 7)


138

BGP-4 RFC 1657 Definitions of Managed Objects for the Fourth Version of the Border Gateway Protocol (BGP-4) using SMIv2

RFC 1745 BGP4/IDRP for IP – OSPF Interaction

RFC 1771 A Border Gateway Protocol 4 (BGP-4)

RFC 1772 Application of the Border Gateway Protocol in the Internet

RFC 1997 BGP Communities Attribute

RFC 1998 An Application of the BGP Community Attribute in Multi-home Routing

RFC 2385 Protection of BGP Sessions via the TCP MD5 Signature Option

RFC 2439 BGP Route Flap Damping

RFC 2519 A Framework for Inter-Domain Route Aggregation

RFC 2796 (obsoletes RFC 1966) BGP Route Reflection – An Alternative to Full Mesh IBGP

RFC 2842 Capabilities Advertisement with BGP-4

RFC 2858 Multiprotocol Extensions for BGP-4

RFC 2918 Route Refresh Capability for BGP-4

RFC 3065 Autonomous System Confederations for BGP

RFC 3107 Carrying Label Information in BGP-4

draft-ietf-idr-restart-10.txt Graceful Restart Mechanism for BGP

draft-ietf-idr-rfc2842bis-02.txt Capabilities Advertisement with BGP-4

draft-ietf-idr-bgp-ext-communities-05.txt

BGP Extended Communities Attribute

draft-ietf-idr-as4bytes-04.txt BGP support for four-octet AS number space

Diffserv RFC 2474 Definition of the Differentiated Services Field (DS Field) in the IPv4 and IPv6 Headers

RFC 2475 An Architecture for Differentiated Services

RFC 2597 Assured Forwarding PHB Group

RFC 2697 A Single Rate Three Color Marker

RFC 3246 An Expedited Forwarding PHB (Per-Hop Behavior)


(3 of 7)


139

MPLS RFC 2205 (1) Resource ReSerVation Protocol (RSVP) – Version 1 Functional Specification

RFC 3031 Multiprotocol Label Switching Architecture

RFC 3032 MPLS Label Stack Encoding

RFC 3035 MPLS using LDP and ATM VC Switching

RFC 3036 LDP Specification

RFC 3209 RSVP-TE: Extensions to RSVP for LSP Tunnels

RFC 3212 Constraint-based LSP Setup using LDP

RFC 3214 LSP Modification using CR-LDP

RFC 3215 LDP State Machines

RFC 3270 Multi-Protocol Label Switching (MPLS) Support of Differentiated Services

RFC 3478 Graceful Restart Mechanism for Label Distribution Protocol

draft-ietf-mpls-framework-05.txt A Framework for MPLS

draft-ietf-mpls-ftn-mib-04.txt (3) Multiprotocol Label Switching (MPLS) FEC-To-NHLFE (FTN) Management Information Base

draft-ietf-mpls-ldp-mib-08.txt (3) Definitions of Managed Objects for the Multiprotocol Label Switching, Label Distribution Protocol (LDP)

draft-ietf-mpls-lsp-ping-08.txt Detecting MPLS data plane failures

draft-ietf-mpls-lsr-mib-08.txt (3) Multiprotocol Label Switching (MPLS) Label Switch Router Management Information Base Using SMIv2

draft-ietf-mpls-mgmt-overview-01.txt Multiprotocol Label Switching (MPLS) Management Overview

draft-ietf-mpls-tc-mib-03.txt (3) Definitions of Textual Conventions and OBJECT-IDENTITIES for Multi-Protocol Label Switching (MPLS) Management

draft-ietf-mpls-te-mib-08.txt (4) Multiprotocol Label Switching (MPLS) Traffic Engineering Management Information Base Using SMIv2

draft-ietf-mpls-rsvp-lsp-fastreroute-03.txt (as LER)

Fast Reroute Extensions to RSVP-TE for LSP Tunnels

draft-minei-mpls-ldp-planned-restart-00.txt LDP Graceful Restart for Planned Outages


(4 of 7)


140

OSPF RFC 1587 The OSPF NSSA Option

RFC 1765 OSPF Database Overflow

RFC 1850 OSPF Version 2 Management Information Base

RFC 2328 OSPF Version 2

RFC 2370 The OSPF Opaque LSA Option

RFC 3623 Graceful OSPF Restart

draft-ietf-ospf-graceful-impl-report-03.txt Graceful OSPF Restart Implementation Report

draft-ietf-ospf-isis-flood-opt-01.txt Flooding Optimizations in Link-State Routing Protocols

draft-ietf-ospf-mib-update-08.txt OSPF Version 2 Management Information Base

draft-katz-yeung-ospf-traffic-04.txt Traffic Engineering Extensions to OSPF

draft-rosen-ppvpn-ospf2547-area0-01.txt

OSPF Area 0 PE/CE Links in BGP/MPLS VPNs

draft-rosen-vpns-ospf-bgp-mpls-05.txt OSPF as the PE/CE Protocol in BGP/MPLS VPNs

IS-IS RFC 1142 OSI IS-IS Intra-domain Routing Protocol

RFC 1195 Use of OSI IS-IS for Routing in TCP/IP and Dual Environments

RFC 2763 Dynamic Hostname Exchange Mechanism for IS-IS

RFC 3277 Intermediate System to Intermediate System (IS-IS) Transient Blackhole Avoidance

draft-ietf-isis-traffic-02.txt IS-IS extensions for Traffic Engineering

ISO/IEC 10589 IS to IS Interdomain Routing

RIP RFC 1722 RIP Version 2 Protocol Applicability Statement

RFC 2082 RIP-2 MD5 Authentication

RFC 2453 RIP Version 2

PPP RFC 1332 The PPP Internet Protocol Control Protocol (IPCP)

RFC 1377 The PPP OSI Network Layer Control Protocol (OSINLCP)

RFC 1661 The Point-to-Point Protocol (PPP)

RFC 1662 PPP in HDLC-like Framing

RFC 1994 PPP Challenge Handshake Authentication Protocol (CHAP)

RFC 2364 PPP over ATM

RFC 2615 PPP over SONET/SDH


(5 of 7)


141

ATM mediation ATMF af-aic-00178.000 Version 1 ATM-MPLS Network Interworking

draft-ietf-pwe3-atm-encap-03.txt (Cell mode and AAL5 PDU mode)

Encapsulation Methods for Transport of ATM Cells/Frame Over IP and MPLS Networks

ITU-T Y.1711 MPLS OAM

ATMF af-cs-0197.000 ATM-MPLS Network Interworking Signaling Specification 1.0

Y.1411 ATM over MPLS Cell Encapsulation

Y.atmplsf ATM over MPLS Frame Encapsulation

Ethernet IEEE 802.3, 2000 edition CSMA/CD Access Method and Physical Layer Specifications

IEEE 802.1Q-1998 Virtual Bridged Local Area Networks (VLANs)

IEEE 802.1P-1998 Supplement to MAC Bridges: Traffic Class Expediting and Dynamic Multicast Filtering

RFC 826 An Ethernet Address Resolution Protocol

RFC 894 A Standard for the Transmission of IP Datagrams over Ethernet Networks

RFC 1643 (statistics collection only) Definitions of Managed Objects for the Ethernet-like Interface Types

draft-ietf-mpls-rsvp-lsp-fastreroute-00.txt (as LER only)

Fast Reroute Extensions to RSVP-TE for LSP Tunnels

Layer 2 VPNs ATMF af-aic-0178.000 Version 1 (4) ATM-MPLS Network Interworking

ITU-T Y.1711 MPLS OAM

Ltd-cs-atmmpls-01.00 Signaling and Routing Support of ATM-MPLS Network Interworking

RFC 4447 Pseudowire Setup and Maintenance using LDP

draft-ietf-pwe3-ethernet-encap-04.txt Encapsulation Methods for Transport of Ethernet Frames Over IP/MPLS Networks

draft-ietf-pwe3-atm-encap-04.txt (5) (6) Encapsulation Methods for Transport of ATM Cells/Frame Over IP and MPLS Networks

draft-ietf-pwe3-vccv-04.txt Pseudo Wire Virtual Circuit Connectivity Verification (VCCV)

Y.atmplsc ATM over MPLS Cell Encapsulation

Y.atmplsf ATM over MPLS Frame Encapsulation


(6 of 7)


142

Notes1. Conforms to RFC 2205 features required to support extensions for LSP tunnels.2. The 7670 RSP uses an enterprise read/write SNMP MIB for configuring and provisioning

LSPs. (rsextmplste.mib)3. See note (2). Using this MIB, LSPs can be used for the purpose of traffic engineering and

IGP/BGP shortcuts.4. Supporting frame and cell mode encapsulation of ATM cells over MPLS.5. CR-LDP LER functionality for MPLS tunnel interfaces is only provided on the Multi-Rate 8

ATM/IP and MR48 line cards. These cards are currently not able to perform the specialized ATM/MPLS encapsulation; therefore, ATM pseudowires cannot ride over CR-LDP LSPs.

6. The implementation of pseudowires on the MR48 line card differs from the standards as follows.In the ATM-MPLS direction, the U bit in the SDU control word is always set to 0.In the ATM-MPLS direction, the CLP bit and the EFCI bits are set corresponding to the first cell being placed in an MPLS frame.

Table 15: ATM standards compliance

BGP/MPLS VPNs (Layer 3 VPNs)

RFC 2842 Capabilities Advertisement with BGP-4

RFC 2858 Multiprotocol Extensions for BGP-4

RFC 2918 Route Refresh Capability for BGP-4

RFC 3107 Carrying Label Information in BGP-4

draft-ietf-ppvpn-rfc2547bis-03.txt BGP/MPLS VPNs

DHCP RFC 951 Bootstrap Protocol (BOOTP)

RFC 1534 Interoperation Between DHCP and BOOTP

RFC 1542 Clarifications and Extensions for the Bootstrap Protocol

RFC 2131 Dynamic Host Configuration Protocol

RFC 2132 DHCP Options and BOOTP Vendor Extensions

RFC 2939 Procedures and IANA Guidelines for Definition of New DHCP Options and Message Types

RFC 3011 The IPv4 Subnet Selection Option for DHCP

RFC 3527 The Relay Agent Link Selection Option for DHCP

RFC 3046 DHCP Relay Agent Information Option


(7 of 7)

ATM functionality

Standard Title

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

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

(1 of 2)


143

Table 16: SNMP standards compliance

Traffic management

af-uni-0010.002 Traffic Management 3.1

af-tm-0056.000 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.000 Signaling ABR Addendum

ILMI 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.1

af-cs-0125.000 ATM AINI specification

af-cs-0126.000 PNNI Addendum for Generic Application Transport, Version 1.0

af-cs-0127.000 PNNI SPVC Addendum, Version 1.1

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

af-cs-0176.000 AINI Loop Detection

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 specification 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 Version 2.1

Routing and addressing

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

af-ra-0106.000 ATM Forum Addressing: Reference Guide

PNNI at-pnni-0026.000

Interim Inter-Switch Signaling Protocol

af-pnni-0055.002

PNNI Version 1.1

af-cs-0195.000 Policy Routing Version 1.0

IMA af-phy-0086.001 Inverse Multiplexing for ATM (IMA) Specification, Version 1.1

Standard Title

RFC 1903 Textual Conventions for SNMPv2

RFC 1907 SNMPv2 Working Group

RFC 2570 Introduction to SNMPv3

(1 of 2)

ATM functionality

Standard Title

(2 of 2)


144

Table 17: Interface compliance specifications for SONET and SDH cards

RFC 2571 Architecture For SNMP Frameworks

RFC 2572 Message Processing and Dispatching for SNMP

RFC 2573 SNMPv3 Applications

RFC 2574 User Based Security

RFC 2575 Views Based Security

RFC 2576 Coexistence between SNMP v1, v2 and v3

Transmission reach Wavelength (nm) Card type Complies with

Electrical — STS-3/STM1E GR-253-CORE, STS-3ITU-T G.703ANSI T1.102

Electrical — DS3 ITU-T G.703ANSI T1.404

SR 1310 OC3c/STM1 ANSI T1.105.06, SR-0

OC12c/STM4 ANSI T1.105.06, SR-0

OC48c/STM16 GR-253-CORE, SR-1ITU-T G.957, I-16

IR 1310 OC3c/STM1 GR-253-CORE, IR-1ITU-T G.957, S-1.1

OC12c/STM4 GR-253-CORE, IR-1ITU-T G.957, S-4.1

OC48c/STM16 GR-253-CORE, IR-1ITU-T G.957, S-16.1

LR 1310 OC3c/STM1 GR-253-CORE, LR-1ITU-T G.957, L-1.1

OC12c/STM4 GR-253-CORE, LR-1ITU-T G.957, L-4.1

OC48cSTM16 GR-253-CORE, LR-1ITU-T G.957, L-16.1

XLR 1550 OC3c/STM1 GR-253-CORE, LR-2ITU-T G.957, L-1.2



Standard Title

(2 of 2)


145

Table 18: Optical parameters for the receive port on Gigabit Ethernet cards

Table 19: Optical parameters for the transmit port on Gigabit Ethernet cards

Notes1. LX is not the same as 1000BASE-LX (IEEE standard 802.3, section 38.4), in that the

7670 RSP Gigabit Ethernet LX I/O has higher output power, which provides longer reach than the 1000BASE-LX. An optical attenuator may be required to prevent receiver saturation with short fiber runs.

2. When coupled into single-mode fiber.

Reach Fiber type Optical parameter Minimum Maximum Units

SX Multi-mode, 62.5 nm or 50 nm

Wavelength range 770 860 nm

Average received power — 0.0 dBm

Receive sensitivity — –17.0 dBm

LX Single mode Wavelength range 1270 1355 nm

Average received power — –3.0 dBm


LH Single mode Wavelength range 1480 1580 nm

Average received power — –3.0 dBm


Reach Fiber type Optical parameter Minimum Maximum Units

SX Multi-mode, 62.5 nm or 50 nm

Wavelength range 770 860 nm

Spectral width — 0.85 nm

Average launch power –9.5 0.0 dBm

Extinction ratio 9.0 — dB

LX (1) Single mode Wavelength range 1270 1355 nm


Average launch power –11.0 (2) 1.0 dBm


LH Single mode Wavelength range 1480 1580 nm


Average launch power –3.0 2.0 dBm



146

Table 20: Operating distance for Gigabit Ethernet cards

Table 21: Optical parameters for the receive port on OC3 and STM1 cards

Table 22: Optical parameters for the transmit port on OC3 and STM1 cards

Reach Fiber type Modal bandwidth (MHz/km)

Operating distance

Distance units

SX Multi-mode, 62.5 nm 160 220 m

200 275 m

Multi-mode 50 nm 400 500 m

500 550 m

LX Single mode — 20 km

LH Single mode — 70 km

Fiber Optical parameter Minimum Maximum Units

MMF Average received power –30 –14 dBm

Optical path penalty — 1 dB

IR Average received power –28 –8 dBm


LR Average received power –34 –10 dBm


XLR Average received power –34 –10 dBm


Fiber Optical parameter Minimum Maximum Typical Units

MMF Center wavelength 1270 1380 1310 nm

Spectral width (RMS) — 200 — nm

Coupled transmit power –20 –14 — dBm

Extinction ratio 10 — — dB

IR Center wavelength 1261 1360 1310 nm

Spectral width (RMS) — 7.7 — nm


Extinction ratio 8.2 — — dB

LR Center wavelength 1280 1335 1310 nm

Spectral width (∆λ 20) — 1 — nm

Coupled transmit power –5 0 — dBm


(1 of 2)


147

Table 23: Optical parameters for the receive port on OC12 and STM4 cards

Table 24: Optical parameters for the transmit port on OC12 and STM4 cards

XLR Center wavelength 1480 1580 1550 nm





MMF Average received power –26 –14 dB


IR Average received power –28 –8 dBm







MMF Center wavelength 1270 1380 1310 nm


Coupled transmit power

–20 –14 — dBm





–15 –8 — dBm





–3 2 — dBm


(1 of 2)


(2 of 2)


148

Table 25: Optical parameters for the receive port on OC48c and STM16 cards

Table 26: Optical parameters for the transmit port on OC48c and STM16 cards




–3 2 — dBm



SR Average received power –18 –3 dB


IR Average received power –18 0 dBm







SR Center wavelength 1266 1360 1310 nm












(1 of 2)


(2 of 2)


149

Table 27: DS3 and OC3c/STM1 electrical transmission information

Table 28: Physical specifications for the shelves





Rate Reach Method Cable type

DS344.736 Mb/s

Maximum 274 m (900 ft) with reference cable

Electrical 75 Ω coaxial

OC3c/STM1155.52 Mb/s

Maximum 274 m (900 ft) with reference cable

Electrical 75 Ω coaxial

Category Specification

Dimensions Control shelf or Peripheral shelf

Height: 93.3 cm (37 in.) (21 RU)

Width: 54.5 cm (21.5 in.)

Depth: 60.0 cm (23.6 in.)

Weight: empty: 68 kg (150 lb)full: up to 181 kg (400 lb)

Switching shelf Height: 97.8 cm (38.5 in.) (22 RU)

Width: 54.5 cm (21.5 in.)

Depth: 60.0 cm (23.6 in.)

Weight: empty: 66 kg (145 lb)full: up to 138 kg (305 lb)

Mounting Rack mounting Width: NEBS-compliant 23-inch rack, with adapter brackets. It can also be rack-mounted in an 800 mm ETSI rack.Height: two shelves per standard height 7-ft rack

Cabinet mounting Custom-made equipment rack for the 7670 RSP


(2 of 2)


150

Table 29: Multishelf configuration specifications

Table 30: Circuit-card area components of a single-shelf system

Table 31: Circuit-card area components of the Control shelf

Description Specification

Maximum number of Peripheral shelves (not including the Control shelf)

14

Maximum number of Switching shelves 2

Maximum number of I/O shelves 15

Maximum number of I/O shelves at full capacity 8

Maximum number of HISLs 32 + 32 (redundant)

Maximum HISL length 70 m

Maximum number of CSLs 16 + 16 (redundant)

Maximum CSL length 70 m

Location Component Quantity

Front Line cards Up to 14

CC2G cards 2

Back I/O cards Up to 28

Facilities cards 1

CICs 2

Switch cards 2

Cable management brackets 24


Front CC2G cards 2

ICON cards 2

Line cards Up to 12

Back ICON I/O cards 2

ICON I/O expansion cards Up to 2

I/O cards Up to 24

Facilities cards 1

CIC 2

DFICs or QFICs At least 2



151

Table 32: Circuit-card area components of the Switching shelf

Table 33: Circuit-card area components of the Peripheral shelf

Table 34: Physical specifications for the exhaust deflector tray

Table 35: Power consumption of 7670 RSP components


Front SSC card 1

SCH card 1

SMX cards 6

Back SACs Up to 32



Front PSC cards 2

Line cards Up to 14

Back PICs 2

DFICs or QFICs 2

I/O cards Up to 28

Facilities cards 1



Dimensions Height: 19.0 cm (7.5 in.) (2 RU)

Width: 59 cm (23.3 in.)

Depth: 59.3 cm (23.4 in.)

Weight 9 kg (20 lbs)

Component Maximum power consumption (Watts)

Switch card 69

SSC card 37

SMX card 47

SCH card 33

SAC 28

CC2G card 84

PSC 28

(1 of 2)


152

Table 36: Site specifications

CIC 22

ICON Management card, ICON I/O card and ICON Expansion card

130

Facilities card 7

DFIC 48

QFIC 61

Fan unit 103

Multi-Rate 8 ATM/IP line card 122

Multi-Rate 16 ATM line card 107

Multi-Rate 16 POS line card 86

MR48 line card 121

ESC 180

OC48c/STM16 SONET/SDH ATM line card 64

Gigabit Ethernet line card 86

PIC 20

1-port OC12c/STM4 I/O card 16


4-port OC12/STM4 Channelized I/O card 17


4-port STM1c Electrical I/O card 29


8-port OC3/STM1 I/O card 13

8-port STM1 Electrical MR48 I/O card 17

8-port STM1c Electrical I/O card 46

1-port OC48c/STM16 ATM I/O card 27

1-port OC48/STM16 Channelized I/O card 12

8-port DS3 I/O card 17

2-port Gigabit Ethernet I/O card 13


Shipping and storage temperature –40° to 70°C (–40° to 158°F)

Normal operating temperature 5° to 40°C (41° to 104°F)

Short-term operating temperature –5° to 55°C (23° to 131°F)

(1 of 2)

Component Maximum power consumption (Watts)

(2 of 2)


153

Normal relative humidity 5% to 85% at sea level

Short-term relative humidity 5% to 95% at sea level

Altitude Between 60 m (197 ft) below sea level and 1800 m (5906 ft) above sea level

Earthquake Suitable for high risk areas

Pollution degree 2

Rated voltage –48 Vdc/–60 Vdc

Operating voltage range –40 Vdc to –75 Vdc


(2 of 2)


154

155

7670 RSP component features

This appendix contains descriptions and component specifications for the 7670 RSP system, as follows:

• “Characteristics of service categories”• “IP routing protocols supported on the 7670 RSP”• “ESC line card features”• “MR48 line card features”• “Multi-Rate 16 ATM line card features”• “Gigabit Ethernet line card features”• “Multi-Rate 16 POS line card features”• “Multi-Rate 8 ATM/IP line card features”• “OC48c/STM16 SONET/SDH ATM line card features”• “Optical I/O and line card compatibility”• “Electrical I/O and line card compatibility”

B. 7670 RSP component features

156

Table 37: Characteristics of service categories

Service category

Cell switching priority

Bit rate Typical traffic type

Delay sensitivity

Cell loss sensitivity

CBR High Constant Mission-critical dataInteractive multimedia

Yes High

rt-VBR High Bursty Mission-critical dataCompressed videoInteractive video

Yes Medium

nrt-VBR Medium Bursty Mission-critical dataLAN interconnectInterworking

No Medium

ABR Low Bursty LAN interconnectInterworkingIP services

No Low to medium

UBR Low Bursty IP servicesLAN interconnect

No Low


157

Table 38: IP routing protocols supported on the 7670 RSP

Protocol 7670 RSP implementation

Static routing Static routing allows a network operator to configure a route to any destination. The 7670 RSP can also use static routes to override routes learned through dynamic routing protocols. The 7670 RSP supports static routes with configurable administrative distances and weights.

OSPFv2 OSPFv2 is a dynamic IGP deployed within an autonomous system. Integrated OSPF is used to exchange routing information between the 7670 RSP and other routers within an AS. Support for OSPFv2 includes:• non-stop routing• traffic engineering• overload handling• IGP shortcuts• route aggregation, injection, and advertisement• route redistribution to and from other protocols• PE-CE routing in IP VPNs• graceful restart helper• link state database overflow parameters• authentication• messages• adjacencies• neighbors on point-to-point networks• neighbors on broadcast networks

BGP-4 BGP-4 is an Internet routing protocol that exchanges routing information among routers within and between autonomous systems. The 7670 RSP can run BGP-4 as either IBGP or EBGP, depending on whether or not the peering router is in the same autonomous system. Support for BGP includes:• non-stop routing• confederations • communities and extended communities• route flap dampening• route reflectors• route aggregates• route redistribution to and from other protocols• graceful restart helper• multiprotocol extensions• BGP-4 peer group without AS• authentication

(1 of 2)


158

Table 39: ESC line card features

IS-IS Integrated IS-IS is used to exchange routing information between the 7670 RSP and other routers within an AS running IS-IS. Support for IS-IS includes:• non-stop routing• traffic engineering• IGP shortcuts• route redistribution to and from other protocols• dynamic host name exchange• authentication• messages• neighbors and adjacencies• interfaces

RIPv2 RIP is an older, widely used protocol. It is supported by many CE routers that do not support other dynamic routing protocols. RIP is therefore ideal for use as a routing protocol between PE routers and CE routers in a BGP/MPLS VPN. Support for RIP includes:• non-stop routing• RIP version compatibility switch• split horizon• authentication• route redistribution to and from other protocols

Protocol 7670 RSP implementation

(2 of 2)

Feature Description

Endpoints Maximum endpoints per card: 16 000

Maximum endpoints per channel or IMA group: 16 000

Maximum TDM DS1 circuit emulation channels per slot: 672

Maximum TDM DS1 circuit emulation channels per OC3 port: 84

Maximum TDM DS1 circuit emulation channels per OC12 port: 336

Channels/groups Number of OC3 or STM1 channels per card: 8

Number of OC3 or STM1 channels per OC3 or STM1 port: 1

Number of OC3 or STM1 channels per OC12 or STM4 port: 4

Number of DS1 channels per card: 672

Number of E1 channels per card: 504

Number of DS1 channels per OC3 port: 84

Number of DS1 channels per OC12 port: 336

Number of E1 channels per STM1 port: 63

Number of E1 channels per STM4 port: 252

Number of IMA groups per OC3 or STM1 port: 42

Number of IMA groups per OC12 or STM4 port: 168

Number of DS1/E1 links per IMA group: 8

(1 of 3)


159

Traffic management support

All ATM Forum Traffic Management Specification Version 4.1 service categories

Per-VC queuing and traffic shaping

Cell-queuing capacity of 3 million cells shared between ingress and egress directions

Algorithms for strict priority and weighted fair-queuing arbitration to ensure fairness and QoS

Congestion control, including EPD, PPD, and CLP-1 discard

High-priority service for turn-around backpressure cells, loopback cells, and inserted cells (both control and diagnostic)

EFCI marking

Fixed and variable mode shaping

VPA shaping (on OC3 or STM1 channels only)

Ingress policing with CLP-1 discard, CLP-0 tagging (which does not apply to UBR), and CLP transparency

The following are not supported: VS/VD for ABR and ER marking for ABR

Support for hitless modification of active PVC connections, with the exception of: • decreasing the MBS parameter (which can be changed but will incur a data hit)• an ESC endpoint with a UBR or nrt-VBR service category; changing the MIR or

the SIR parameter in the egress direction relative to the ESC port to or from a value of 0 will incur a data hit

• a CDVT parameter

Circuit emulation services Support for unstructured DS1 CE

Performance parameter support

TCAs

Statistics ATM layer

Congestion

VPA

IMA

Physical

Fabric error

PVC billing

Diagnostics support OAM alarm surveillance (1)

OAM connectivity verification (2)

Redundancy support Line card redundancy1+1 Linear APS (port redundancy)1+1 G.841 Annex B bidirectional protection (for IP/MPLS-based transport networks using the 7750 SR and 7705 SAR) (3)

I/O card support One 8-port OC3/STM1

One 8-port STM1 Electrical MR48

One 4-port OC12/STM4 channelized (ports 1 and 2 only)

Feature Description

(2 of 3)


160

Notes1. OAM alarm surveillance is not supported on unstructured DS1 CE channels.2. OAM connectivity verification egress cell tests are not supported on unstructured DS1 CE channels.3. 1+1 G.841 Annex B bidirectional protection is supported in a future release planned for 2008.

Table 40: MR48 line card features

Other supported features Hot-insertable


Loopbacks

A connected I/O port can be a source of node timing

IMA groups

Feature Description

(3 of 3)

Feature Description

Endpoints Maximum endpoints per card: 93 000



Per-VC queuing, per-VC system profiling, and traffic shaping

Cell-queuing capacity of 4 million cells shared between ingress and egress directions

Algorithms for strict priority and weighted fair-queuing arbitration to ensure fairness and QoS

Congestion control, including EPD, PPD, and CLP-1 discard

High-priority service for turn-around backpressure cells, loopback cells, and inserted cells (both control and diagnostic)

EFCI marking

Fixed and variable mode shaping

VPA shaping

Ingress policing with CLP-1 discard, CLP-0 tagging (which does not apply to UBR), and CLP transparency

The following are not supported: VS/VD for ABR and ER marking for ABR

Support for hitless modification of active PVC connections, with the exception of: • decreasing the MBS parameter (which can be changed but will incur a data hit)• an MR48 endpoint with a UBR or nrt-VBR service category; changing the MIR or

the SIR parameter in the egress direction relative to the MR48 port to or from a value of 0 will incur a data hit

(1 of 3)


161

IP characteristics Support for IPv4 and IPv6

450 000 routes

Wirespeed forwarding

MPLS support, as both a core and edge LSR

CR-LDP signaling protocol support

BGP/MPLS VPN support

2000 interfaces (standard mode)16 000 interfaces (scaled mode)

PPP over ATM

Access lists for packet filtering and MFC

Source-based forwarding


Egress DSCP remarking

Ingress DSCP remarking (per card) and egress DSCP remarking (per Layer 3 interface)

ARP support for IP and MAC address mapping

RBE interface support

SRRP (interface protection) for interfaces that are members of an RBE interface group

DHCP relay

IP interface groups

IP multicast

CSPF


TCAs

Statistics ATM layer

IP/MPLS

Congestion (Including Layer 3 congestion statistics)

VPA

Physical

Fabric error

PPP

PVC and SPVC billing

Feature Description

(2 of 3)


162

Note1. 1+1 G.841 Annex B bidirectional protection is supported in a future release planned for

2008.

Table 41: Multi-Rate 16 ATM line card features

Diagnostics support OAM connectivity verification, including round-trip delay

OAM alarm surveillance

OAM continuity checking

OAM performance monitoring

MPLS LSP ping and traceroute and pseudowire VCCV

Redundancy support 1+1 Linear APS (port redundancy)1+1 G.841 Annex B bidirectional protection (for IP/MPLS-based transport networks using the 7750 SR and 7705 SAR) (1)

I/O card support One 1-port OC48/STM16 Channelized

One 4-port OC12/STM4 Channelized

Two 8-port OC3/STM1



Loopbacks

A connected I/O port can be a source of node timing

Monitor TAC support

Trunk-side ATM pseudowires

A port receiver can be disabled (which avoids synchronization problems with equipment without a transmit port)

Feature Description

(3 of 3)

Feature Description

Endpoints Maximum endpoints per port: 64 512 (1)

Maximum endpoints per 4-port group: 64 512 (1)

Maximum endpoints per card: 258 048 (1)

(1 of 3)


163

Traffic management support All ATM Forum Traffic Management Specification Version 4.0 service categories

Point-to-point ABR including VS/VD and ER marking

Per-connection queuing

Weighted fair queuing

VP and VC shaping

Congestion control including EPD, PPD, and CLP-1 discard

Eight QoS classes

Intelligent packet discard

Ingress and egress shaping including static or variable mode shaping

Support for hitless modification of active PVC connections, with the exception of the MCR parameter (which can be changed but will incur a data hit)

IP characteristics 224 CTSIs

Performance parameter support TCAs

Statistics ATM port

Physical port

ATM endpoint connections

Switching fabric errors

Congestion

OAM support Connectivity verification, including round-trip delay

Alarm surveillance

Continuity checking

Performance monitoring

Redundancy support 1+1 Linear APS (port redundancy) (2)

1+1 G.841 Annex B bidirectional protection (for IP/MPLS-based transport networks using the 7750 SR and 7705 SAR) (3)

You can mix types of I/O cardsFor example, an OC3c/STM1 IR card can protect an OC3c/STM1 SR I/O card

I/O card support You can mix I/O cardsFor example, an OC3c/STM1 I/O card and an OC12c/STM4 I/O card will work with one Multi-Rate 16 ATM line card

Feature Description

(2 of 3)


164

Notes1. VCIs 3 and 4 are reserved for OAM and cannot be configured as connections. The maximum

number of connections decreases depending on the number of VPs.2. 1+1 Linear APS (port redundancy) is not supported on the DS3 I/O card.3. 1+1 G.841 Annex B bidirectional protection is supported in future release planned for

2008.4. Ports on the DS3 I/O card cannot be used as a source of timing for the node.

Table 42: Gigabit Ethernet line card features


Each port on the connected I/O card can be a source of timing for the node (on the control shelf only) (4)


Monitor TAC support

Soft recovery mechanism whereby a line card attempts to perform a soft reset in response to an unrecoverable software failure—before this mechanism was introduced, a line card would perform a hard reset in response to an unrecoverable software failureThe introduction of this functionality should greatly reduce the impact of such failuresSoft recovery is supported on the card if the card’s current configuration supports soft reset

IGMP proxy

Feature Description

(3 of 3)

Feature Description

Endpoints Maximum endpoints per port: 3777

Maximum endpoints per card: 3777

Layer 2 ATM endpoints: up to 964

Maximum basic VLAN endpoints per port: 4094

Traffic management support Strict priority and weighted fair queuing

Congestion control including RED

Eight CoS classes

8-QoS port interface

3-QoS and 1-QoS VLANs

(1 of 2)


165

IP characteristics Support for IPv4 and IPv6

250 000 routes


MPLS support, as both a core and an edge LSR


Ethernet RFC 894 encapsulation support

ARP support for IP and MAC address mapping

One to 961 Layer 3 interfaces per port

DSCP remarking

DHCP relay


Source-based forwarding


IP multicast

Performance parameter support Congestion and fabric error statistic TCAs

Statistics Port MAC layer


IP

Congestion (including Layer 3 congestion statistics)

Per LSP

VLAN

Diagnostics support ATM OAM support—CV responses and AIS/RDI for ATM VC-to-Gigabit Ethernet interface connections


I/O card support Two 2-port Gigabit Ethernet I/O cards



Non-service-affecting network processor firmware upgrade

Loopbacks

Auto-negotiation

Link aggregation groups and LACP

Subscriber address support, including E.164 addressing, using Gigabit Ethernet trunk groups for SPVCs that terminate on Gigabit Ethernet port interfaces or VLAN interfaces

Feature Description

(2 of 2)


166

Table 43: Multi-Rate 16 POS line card features

Feature Description

Endpoints Maximum P-LSP endpoints per port: 3777

Maximum endpoints per card: 3777

Traffic management support Strict priority and weighted fair queuing

Congestion control including RED

Eight CoS classes for IP

Ingress policing

Buffer partitioning

IP characteristics 250 000 routes




One interface per port



DSCP remarking

IP multicast

CSPF


Diagnostics support MPLS LSP ping and traceroute and pseudowire VCCV

Statistics SONET port

Physical port

Physical layer SONET port

HDLC port

Congestion (including Layer 3 congestion statistics)


IP

PPP

Per LSP

Redundancy support 1+1 Linear APS (port redundancy)

You can mix types of I/O cardsFor example, an OC48/STM16 IR card can protect an OC48/STM16 SR I/O card

I/O card support Supports the OC48/STM16 SR and IR I/O cards

(1 of 2)


167

Table 44: Multi-Rate 8 ATM/IP line card features


The port on the connected I/O card can be a source of timing for the node


Non-service-affecting network processor firmware upgrade

Feature Description

(2 of 2)

Feature Description





Point-to-point ABR including VS/VD and ER marking

Per-connection queuing

Weighted fair queuing

VP and VC shaping

Congestion control including EPD, PPD, and CLP-1 discard

Eight QoS classes for ATM

Eight CoS classes for IP

Intelligent packet discard

Ingress and egress shaping including static or variable mode shaping

Policing

UNI and NNI interfaces

Support for hitless modification of active PVC connections, with the exception of the MCR parameter (which can be changed but will incur a data hit)

IP characteristics 250 000 routes

Wirespeed routing


CR-LDP signaling protocol support


DHCP relay support

1000 interfaces

Access lists for packet filtering


DSCP remarking

CSPF

(1 of 2)


168

Notes1. VCIs 3 and 4 are reserved for OAM and cannot be configured as connections. The maximum

number of connections decreases depending on the number of VPs.


TCAs

Statistics ATM port

Physical port



IP statistics

Per LSP

Congestion statistics

Diagnostics support OAM connectivity verification, including round-trip delay

OAM alarm surveillance

OAM continuity checking

OAM performance monitoring



You can mix types of I/O cardsFor example, an OC3c/STM1 IR card can protect an OC3c/STM1 SR I/O card

I/O card support You can mix I/O cardsFor example, an OC3c/STM1 I/O card and an OC12c/STM4 I/O card will work with one Multi-Rate 8 ATM/IP line card


Each port on the connected I/O card can be a source of timing for the node (on the control shelf only)


Monitor TAC support

Soft recovery mechanism whereby a line card attempts to perform a soft reset in response to an unrecoverable software failure—before this mechanism was introduced, a line card would perform a hard reset in response to an unrecoverable software failureThe introduction of this functionality should greatly reduce the impact of such failuresSoft recovery is supported on the card if IP services are not configured on the card and if the card’s current configuration supports soft reset

Feature Description

(2 of 2)


169

Table 45: OC48c/STM16 SONET/SDH ATM line card features

Note1. VCIs 3 and 4 are reserved for OAM and cannot be configured as connections. The maximum

number of connections decreases depending on the number of VPs.

Feature Description



Traffic management support All ATM Forum Traffic Management Specification Version 4.0 service categories

Class-based queuing

Strict priority scheduling

Congestion control including EPD and PPD

Support for hitless modification of active PVC connections

IP characteristics 224 CTSIs


Statistics ATM port

Physical port



Congestion

OAM support Connectivity verification

Alarm surveillance


I/O card support One 1-port OC48c/STM16 ATM I/O card


Connected I/O card can be a source of timing for the node (on the control shelf only)


Monitor TAC support

Soft recovery mechanism whereby a line card attempts to perform a soft reset in response to an unrecoverable software failure—before this mechanism was introduced, a line card would perform a hard reset in response to an unrecoverable software failureThe introduction of this functionality should greatly reduce the impact of such failuresSoft recovery is supported on the card if the card’s current configuration supports soft reset


170

Table 46: Optical I/O and line card compatibility

Notes1. Only one I/O card can be installed behind the ESC and must be installed in I/O slot 1. The

card can be physically placed in I/O slot 2, but you cannot configure the card in that slot.2. The OC12/STM4 Channelized I/O card must be installed in I/O slot 1 only. The I/O card

can be physically placed in I/O slot 2, but you cannot configure the card in that slot.3. Two of the four OC12/STM4 ports are available for use with the ESC.4. Only one I/O card can be installed behind the Multi-Rate 16 POS line card; it must be

installed in the bottom slot.5. Only one I/O card can be installed behind the OC48c/STM16 SONET/SDH ATM line

card; it must be installed in the bottom slot.6. The OC48/STM16 Channelized I/O card must be installed in I/O slot 1 only. The I/O card

can be physically placed in I/O slot 2, but you cannot configure the card in that slot.

Card type Multi-Rate 8 ATM/IP line card



MR48 line card



ESC line card

Optical I/O cards

4-port OC3c/STM1

8-port OC3c/STM1

8-port OC3/STM1

(1)

1-port OC12c/STM4

2-port OC12c/STM4

4-port OC12/STM4 Channelized

(2) (1) (3)

1-port OC48c/STM16 ATM

(4) 5)

1-port OC48/STM16 Channelized

(6)

2-port Gigabit Ethernet


171

Table 47: Electrical I/O and line card compatibility

Card type Multi-Rate 8 ATM/IP line card



MR48 line card



ESC line card

Electrical I/O cards

4-port STM1 Electrical

8-port STM1 Electrical

8-port STM1 Electrical MR48

8-port DS3


172

173

Glossary

2Gsecond generation wireless telephone technology

The main difference from previous mobile telephones, retroactively dubbed 1G, is that 1G networks process analog data but 2G networks are digital. This allows a considerable improvement in voice quality, as digital information is not subject to distortions in the same way as analog information, and also increased capacity as calls can be multiplexed more efficiently. 2G networks cannot normally transfer data, such as e-mail or software, other than the digital voice call itself and other basic ancillary data such as time and date.

2.5Gsecond and a half generation wireless telephone technology

2.5G is a stepping stone between 2G and 3G cellular wireless technologies. The term "second and a half generation" is used to describe 2G systems that have implemented a packet switched domain in addition to the circuit switched domain. Commonly referred to as GPRS.

3Gthird-generation mobile telephone technology

The services associated with 3G provide the ability to transfer both voice data (a telephone call) and non-voice data (such as downloading information, exchanging e-mail, and instant messaging). There are three standards: UMTS (universal mobile telephone system) based on W-CDMA technology, CDMA2000 based on 2G CDMA technology, and TD-SCDMA (time division synchronous code division multiple access) based on spread spectrum CDMA technology.

3TDEStriple data encryption standard

Glossary

174

A strengthened version of the data encryption standard that is documented in RFC 1851. Also known as triple DES, this standard is based on the existing DES, but has a key three times as long.

See also DES.

5620 NMAlcatel-Lucent 5620 Network Manager

6PEIPV6 provider edge router

6PE is one method of providing an IPv6 migration over MPLS. This approach allows the deployment of IPv6 over an existing MPLS network with no upgrades to the core infrastructure and minimal operation costs.

6VPEIPv6 virtual private network provider edge router

6VPE is a provider edge router that provides an IPv6 interface from an IPv6-capable site to a service provider backbone network. The 6VPE router maintains separate IPv6 VRFs for each VPN.

7470 MSPAlcatel-Lucent 7470 Multiservice Platform

AALATM adaptation layer

The AAL is the layer of the ATM Reference Model that is divided into the Convergence Sublayer and the Segmentation and Reassembly Sublayer. The AAL converts user data traffic to and from ATM cells. On the originating side of the connection, the AAL segments the user data traffic into the size and format of ATM cells. On the terminating side of the connection, the AAL reassembles the user data into its original format.

There are four different types of AALs. The AAL types are differentiated according to the source-destination timing (delay-tolerant or delay-intolerant), the bit rate (CBR or VBR), and the data transfer mode (connections-oriented or connectionless) of the user data traffic that each converts. At present, the four types of AAL recommended by the ITU-T are AAL-1, AAL-2, AAL-3/4, and AAL-5.

AAL connectionAn AAL connection is an association established by the AAL between two or more next higher layer entities.

AAL-1ATM adaptation layer type 1

Glossary

175

AAL-1 supports the conversion of delay-intolerant, CBR, connection-oriented traffic such as uncompressed, digitized voice and video.


AAL-2 supports the conversion of VBR, delay-intolerant, connection-oriented traffic such as compressed voice and video. This traffic requires precise timing between the source and destination. AAL-2 is undefined by the International Standards bodies.

AAL-3/4ATM adaptation layer type 3/4

AAL-3/4 supports the conversion of VBR, delay-tolerant data traffic such as X.25, packet, and frame relay traffic. This traffic requires some sequencing or error detection support. Two separate AAL types, AAL-3 and AAL-4, were combined to support both connection-oriented and connectionless traffic.


AAL-5 is a simplified version of AAL-3/4. It provides support for point-to-point and point-to-multipoint (ATM layer) connections. AAL-5 is used to carry data traffic such as TCP/IP. This application is the most widely deployed adaptation layer.

ABRavailable bit rate

ABR is a class of service in which the ATM network makes the “best effort” to meet traffic bit rate requirements.

ACLaccess control list

ACLs contain user-defined rules for IP packet filtering, IP route filtering, or MFC.

ACOalarm cutoff

ACO allows the audible alarms to be extinguished without affecting the visual alarms. The audible alarms can be toggled as enabled or disabled.

ADSLasymmetrical digital subscriber line

ADSL is a digital telecommunications protocol designed for an upstream data flow (client-to-server) that is a fraction of the downstream data flow (server-to-client). The upstream data flow is measured in kilobits while the downstream data flow is measured in megabits.

Glossary

176

ADSL uses existing twisted pair telephone lines to deliver access to video on demand and the World Wide Web, where the bulk of the data is sent from the server to the client.

AESadvanced encryption standard

A block cryptographic algorithm (based on the Rijndael algorithm) that uses a multiple-size symmetric key (128, 192, or 256 bit). AES is a next-generation cipher that is meant to replace the older DES algorithm.

See also DES.

AESAATM end system address

The AESA is a 20-byte ATM address that identifies one or more ATM endpoints for SVCs.

AFassured forwarding

AF is an IP forwarding behavior that minimizes long-term local congestion events, while allowing short-term burst traffic. It offers a high level of assurance that each packet will be delivered as long as the traffic conforms to a given service profile.

AINIATM Inter-Network Interface

The AINI acts as a gateway protocol between PNNI and SS7 or B-ISUP networks, and between PNNI networks. AINI is a combination of B-ISUP routing and PNNI signaling.

AISalarm indication signal

The alarm indication signal is a code sent downstream in a digital network to indicate that a traffic-related defect has been detected. It is also known as an RAI or yellow alarm.

ALCAPaccess link control application protocol

ALCAP is a control plane protocol for the transport layer. Basic functionality of ALCAP is multiplexing of different users onto one AAL2 transmission path using channel IDs (CIDs).

ANSIAmerican National Standards Institute

Glossary

177

ANSI is a nonprofit organization that develops and publishes standards and represents the U.S. in some international standards groups.

APSautomatic protection switching

APS is a mechanism for providing line and equipment protection for SONET interfaces.

ARPaddress resolution protocol

ASautonomous system

ATMasynchronous transfer mode

ATM is a high-speed switching and transmission technology. ATM is a high bandwidth, low-delay, packet-like switching and multiplexing technique. Usable capacity is segmented into 53-byte, fixed-size cells, consisting of header and information fields, allocated to services on demand.

ATM ForumThe ATM Forum is an international nonprofit organization formed to advance the use of ATM products and services by standardizing interoperability specifications. In addition, the Forum promotes industry cooperation and awareness.

BellcoreBell Communications Research Inc.

See Telcordia.

B-ICIbroadband inter-carrier interface

B-ISUPinter-nodal broadband signaling protocol

B-ISUP is defined by the ITU-T. Its purpose is to establish, maintain and release ATM connections in a public network through the use of signaling messages.

BGPborder gateway protocol

Glossary

178

An internet routing protocol used to pass routing information between different administrative routing domains. The BGP routing protocol does not pass explicit topology information; it passes a summary of reachability between administrative routing domains. BGP is most commonly deployed as an interautonomous system routing protocol.

BITSbuilding integrated timing source

A BITS is a clock that supplies DS1 or composite clock timing reference to all other clocks in a building.

BlowfishA block cryptographic algorithm that uses a variable-size symmetric key.

BNCBayonet-Neill-Concelman

A BNC connector connects a 10BASE-2 coaxial cable to a transceiver.

BOOTPBOOTstrap Protocol

BOOTP is an Internet protocol that enables a workstation or network device to discover its own IP address, the IP address of a BOOTP server on the network, and a file to be loaded into memory to boot the machine. This enables the workstation to boot without requiring a hard or floppy disk drive. The protocol is defined by RFC 951.

BRASbroadband remote access server

A termination device (commonly called an aggregation router) that terminates PPP over ATM connections.

BSCbase station controller

The BSC handles the allocation of radio channels, receives measurements from the mobile phones, and controls the handovers from base transceiver station to base transceiver station. A key function of the BSC is to act as a concentrator where many different low-capacity connections to BTSs (with relatively low utilization) become reduced to a smaller number of connections towards the MSC (with a high level of utilization).

BSSbase station subsystem

Glossary

179

BSS is the part of a GSM network which is responsible for handling traffic and signaling between a mobile phone and the Network Switching Subsystem (NSS). The BSS carries out transcoding of speech channels, allocation of radio channels to mobile phones, paging, quality management of transmission and reception over the air interface and many other tasks related to the radio network. BSS includes BTS and BSC elements.

BTSbase transceiver station

BTS is the equipment which facilitates the wireless communication between Mobile Stations (handsets) and the network. Typically a BTS has transceivers which allow it to serve several different frequencies and different sectors of the cell (in the case of sectorised base stations). A BTS is controlled and managed by a parent BSC via the Base Station Control Function (BCF). The BCF is implemented as a discrete unit or even incorporated in a TRX in compact base stations.

CACconnection admission control

CAC is the function of an ATM network that determines the acceptability of a virtual circuit connection request and determines the connection route through the network.

CAPEXcapital expenditure

CBCcipher block chaining

A method that enables block cryptographic algorithms to encrypt data that is larger than the algorithm’s required block size. The data is broken down into the cipher-specified block size, then encrypted. The encryption of each block depends on the previously encrypted block.

CBRconstant bit rate

CBR is an ATM class of service for delay-sensitive applications such as video and voice that must be digitized and represented by a constant bit stream. CBR traffic requires guaranteed levels of service and throughput.

CC2GControl Card Second Generation

The CC2G card provides local and remote control of the 7670 RSP system. It is the second-generation control card for the 7670 RSP, introduced in Release 3.0. As of Release 7.1, the CC2G card is the only control card supported by the 7670 RSP.

Glossary

180

CDMAcode division multiple access

CDMA is a form of multiplexing scheme and a method of multiple access that encodes data with a special code and uses the constructive interference properties of the special code to perform the multiplexing. CDMA also refers to digital cellular telephony systems that make use of this multiple access scheme, such as those pioneered by Qualcomm, and W-CDMA by the ITU.

CDVcell delay variation

CDV is a measure of cell clumping, or how much more closely cells are spaced than the nominal interval.

CDVTcell delay variation tolerance

The CDVT is the upper limit of allowable cell delay variation. When cells from two or more ATM connections are multiplexed, cells of an ATM connection may be delayed while cells of another ATM connection are inserted at the output of the multiplexer. Consequently, some randomness may affect the inter-arrival time between consecutive cells of a connection as monitored at the UNI.

CE devicecustomer edge device

A CE device connects a customer network to a provider network.

CICcontrol interconnect card

The CIC provides an external interface for managing the active control card. The CIC is the part of a CCS signaling message used to identify the circuit being established between two signaling points.

CIDRclassless interdomain routing

An internet routing paradigm that passes both the network prefix and a mask of significant bits in the prefix within the routing exchange. CIDR is commonly used to denote an internet environment in which there is no assumption of Class A, B, or C network addresses. BGP-4 is currently used to provide CIDR support.

CHAPChallenge Handshake Authentication Protocol

CHAP is a type of access authentication.

Glossary

181

circuit emulationCircuit emulation allows the connection of TDM circuits to ATM networks so that TDM traffic can be routed over ATM networks.

CLIcommand line interface

The CLI is an interface that allows the user to interact with the operating system by typing alphanumeric commands and optional parameters at a command prompt. UNIX and DOS provide CLIs.

CLPcell loss priority

The CLP bit is a single-priority bit in the ATM cell header that indicates whether the cell may be discarded if necessary. Lower-priority cells (CLP=1) can be discarded if there is congestion.

CLRcell loss ratio

CMIPcommon management information protocol

CMIP is an ITU-T standard for message formats and procedures that exchange management information used to operate, administer, maintain, and provision a network. CMIP services the CMIS.

CMIScommon management information services

CMIS is the ISO-standard, service-level definition for operation with CMIP. It layers the CMIP management exchange protocol on top of the TCP/IP stack.

CoSclass of service

A categorical method of dividing traffic into separate classes to provide differentiated service to each class within the network.

CPEcustomer premises equipment

CPE is the system or devices located at the customer site.

CPSScontrol packet switching system

Glossary

182

CPSS is the proprietary network protocol for communication between Alcatel-Lucent equipment. Similar to X.25, CPSS is a packet-switched system used to transfer configuration and status information between nodes.

CPUcentral processing unit

The CPU is the part of a computer that performs the logic, computational, and decision-making functions. The CPU is typically a single computer chip.

CRcell relay

CR-LDPconstraint-based routing label distribution protocol

A signaling protocol used for MPLS path setup and teardown.

CSACanadian Standards Association

The CSA is the nonprofit Canadian agency that certifies electrical and electronic products that conform to Canadian national safety standards.

CSLcontrol services link

A CSL is a link that provides control communications between the shelves in a 7670 RSP multishelf system.

CSPFconstrained shortest path first

CSPF is an algorithm that allows you to configure constraints on the routing of an S-LSP.

CTDcell transfer delay

CTD is an ATM performance parameter that specifies the average transit delay of cells between a source and a destination over a virtual circuit.

CTSIcontrol terminated service interface

CUGclosed user group

The term CUG is obsolete today, but it was used (as in X.25) to describe VPN functionality.

Glossary

183

CVcoding violation

DACSdigital access carrier system

DACS are used for getting two analog phone lines down one physical copper pair.

DBRdomain-based rerouting

DBR is a rerouting mechanism that replaces a connection segment within a rerouting domain between a source node and a destination node.

DCSdigital cross-connect system

A network element that is used to arrange lower-level digital signals among higher-level digital bit streams; for example, DS1s among DS3s.

DDoSdistributed denial of service

One of the most common form of attacks consisting of attempts to "flood" a network with bogus packets, thereby preventing legitimate network traffic. Often it is conducted by disrupting network connectivity with the use of multiple hosts.

DESdata encryption standard

An unclassified U.S.-government sanctioned encryption and decryption technology using 56-bit encryption (with 8-bit error detection).

DFICdual fabric interface card

A DFIC is a system card that provides two HISL terminations for a Peripheral shelf, which provides data-path connectivity to a Switching shelf. The DFIC is used in a multishelf configuration of the 7670 RSP.

DHCPdynamic host configuration protocol

DHCP is an Internet protocol for automating the configuration of computers that use TCP/IP. DHCP can be used to automatically assign IP addresses, to deliver TCP/IP stack configuration parameters such as the subnet mask and default router, and to provide other configuration information such as the addresses for printer, time, and news servers.

Glossary

184

Diffservdifferentiated services

Diffserv describes the current QoS model in IP.

See also DS, DSCP

DLCdata link connection

A DLC represents a segment of a PVC. The connection can be between an end-user device and a network device or between two network devices.

DLCIdata link connection identifier

A DLCI identifies a DLC. DLCIs must be unique on a given frame stream, but not across the network. All frames that have the same DLCI and that are carried in the same frame stream are associated with the same logical connection

DoDdownstream on demand

A label advertisement mode in which an LSR requests a label for a particular FEC from its peer downstream node. In response to the request, the downstream LSR sends the FEC-label binding to the upstream node, which then forwards the packet.

DoSdenial of service attack

A DoS attack is an attack on a computer system or network that causes a loss of service to users, typically the loss of network connectivity and services by consuming the bandwidth of the victim network or overloading the computational resources of the victim system.

DPdrop precedence

Attribute of a packet that affects the probability of dropping the packet within a CoS. DP is usually indicated as a color. Green indicates a low drop probability; packets are dropped only if a queue overflows. Yellow indicates a medium drop probability, and Red indicates a higher drop probability.

DRdesignated router

A single PIM router on a LAN that acts on behalf of directly connected hosts with respect to the PIM protocol. One DR is assigned per interface using an election process.

Glossary

185

DSdifferentiated services

DS is a method for providing differentiated CoS for Internet traffic. DS supports various types of IP applications.

See also DSCP, Diffserv

DS0digital signal level 0

DS0 is a worldwide standard for PCM digitized voice. It operates at 64 kb/s.

DS1digital signal, level 1

DS1 is created by multiplexing 24 DS0 channels for a combined bandwidth of 1.544 Mb/s. It is also called T1.

DS3digital signal, level 3

DS3 is created by multiplexing 28 T1 channels for a combined bandwidth of 44.736 Mb/s. It is also called T3.

DSAdigital signature algorithms

United States federal government standard for digital signatures.

DSCPdifferentiated services code point

DSCP is a 6-bit value encoded in the TOS field of an IP packet header. It identifies the CoS that the packet should receive.

DSLdigital subscriber line

DSL is a single twisted-pair wire that supports full-duplex transmission at a bit rate of 160 kb/s (144 kb/s for 2B+D data, 12 kb/s for framing and error correction, and 4 kb/s for the embedded operation channel).

DSLAMdigital subscriber line access multiplexer

A DSLAM card converts multiple ADSLs into ATM traffic. For a service management application, if the service user is connected to the ATM network through a DSLAM port, network access is provisioned using a DSLAM attachment type.

Glossary

186

DUdownstream unsolicited

A label advertisement mode in which an LSR distributes its label binding for a particular FEC to all upstream nodes without receiving a specific request. This is the label that the downstream node expects the upstream node to apply when forwarding packets.

E.164E.164 stands for the ITU-T 164 Recommendation, "The international public telecommunication numbering plan". It is commonly used as a guideline for assignment of ATM public network addresses.

E1E1 is a level-1 digital trunk operating at 2.048 Mb/s that is used outside of Canada, the United States, and Japan. E1 identifies primary rate (or aggregate bandwidth) transmissions that conform to ITU-T Recommendations G.703 and G.732. It is made up of 32 DS0 channels (64 kb/s each). Channel 0 is reserved for framing and alarm information, and channel 16 is usually reserved for signaling; 30 channels remain to carry data. E1 is also known as CEPT1.

E3European digital signal level 3

E3 is the European standard used instead of DS3. E3 is the equivalent of 16 E1s or four E2s. An E3 operates at 34.368 Mb/s.

EBGPexternal border gateway protocol

EBGP is a protocol that uses BGP to connect routers that are in different autonomous systems.

ECMPequal cost multipath

A method of distributing traffic to multiple destinations over several equivalent paths.

EFCIexplicit forward congestion indication

EGPexterior gateway protocol

An internet protocol for exchanging routing information between autonomous systems.

E-LSPEXP-inferred per-hop behavior LSP

Glossary

187

An LSP that carries traffic that has only one priority level.

EMCelectromagnetic compatibility

EPDearly packet discard

EPD is a congestion control mechanism for ATM paths that attempts to prevent delivery of partial packets through the network.

EPSequipment protection switching

ERexplicit rate

ER is a field in the ABR RM-cell that limits the source transmission rate to a specific value. It is initially set by the source to a requested rate (such as PCR). It may be subsequently reduced by any network element in the path to a value that the element can sustain.

ESCEdge Services Card

ESSEthernet Service Switch

The 7450 ESS enables the delivery of profitable metro Ethernet services and high-density service-aware Ethernet aggregation over IP/MPLS-based networks.

EthernetThe Ethernet protocol is a data link layer protocol for interconnecting computer equipment into CSMA/CD LANs, jointly developed by Xerox, Digital Equipment Corporation, and Intel. Today, it is loosely referred to as a set of protocols built around IEEE 802.3.

The Ethernet protocol specifies how data is placed on, and retrieved from, a common transmission medium. It is used as the underlying transport vehicle by several upper-level protocols, including TCP/IP and UDP/IP.

ETSIEuropean Telecommunications Standards Institute

ETSI is the primary telecommunications standards organization in Europe.

EXP bitEXPerimental

A field in the MPLS packet header.

Glossary

188

FASTfast activity switch

FAST is a type of fabric activity switch that occurs in 60 ms or less when neither the active fabric nor the inactive fabric has any faults.

FCCFederal Communications Commission

The FCC is a regulatory body responsible for network connection approvals and the management of the radio spectrum in the United States.

FECforwarding equivalence class

A group of IP packets that are forwarded over the same path, with the same forwarding treatment.

FIBforwarding information base

An internal table containing only the IP routes that are actually being used by a router to forward IP traffic.

FICfabric interface card

A FIC is a system card that provides HISL terminations for a Peripheral shelf, which provides data-path connectivity to a Switching shelf. The FIC is used in a multishelf configuration of the 7670 RSP.

FRSee frame relay.

frame relayFrame relay is a packet-switching protocol similar to X.25 that requires much less processing and is designed to operate at much higher speeds. Frame relay combines the high speed and low delay of circuit switching with the port sharing and dynamic bandwidth-allocation capabilities of X.25 packet switching. Unlike X.25, frame relay does not require a lot of processing at each node, delegating error correction and flow control to the attached user devices. Numerous remote LAN terminals can use frame relay packet switching to share the bandwidth of a single DS0 on a T1 link. Frame relay offers a low-cost way of handling high-volume, bursty data transmissions.

FRRfast reroute

Glossary

189

FRR is a mechanism for protecting MPLS LSPs from link and node failures by deploying traffic engineering (TE) extensions and locally repairing the LSPs at the point of failure. FRR allows data to continue to flow by rerouting it over backup tunnels that bypass failed links or nodes.

FTPfile transfer protocol

FTP is the Internet standard client-server protocol for transferring files from one computer to another. FTP generally runs over TCP or UDP.

See also SFTP.

GGSNGateway GPRS Support Node

The GGSN supports the edge routing function of the GPRS network. The GGSN performs the task of an IP router for external packet data networks.

GMSCGateway Mobile Switching Centre

The GMSC provides an edge function within a mobile network. It terminates the Public Switched Telephone Network (PSTN) signaling and traffic formats and converts this to protocols employed in mobile networks. For mobile terminated calls, it interacts with the Home Location Register (HLR) to obtain routing information.

GPRSgeneral packet radio service

GPRS is a new non-voice, value-added service that enables data to be sent and received across a mobile telephone network. It supplements circuit switched data and short message service. Also referred to as 2.5G.

GUIgraphical user interface

A GUI is a computer-user interface that incorporates graphics to make software easier to use.

HDLChigh-level data link control

HDLC is an ISO standard for serial data communication. HDLC is composed of a family of bit-oriented protocols providing frames of information with address, control, and frame-check sequence fields. It is considered a superset of several other protocols, such as SDLC, LAP, LAPB, and LAPD. HDLC is defined in ISO 4335.

HISLhigh-speed intershelf link

Glossary

190

A HISL is an optical link that provides data-path connectivity between the Switching shelves and all other shelves in a 7670 RSP multishelf system.

HMAChashed message authentication code

A series of nested cryptographic hashing algorithms that are used to protect data integrity.

HSDPAhigh-speed downlink packet access

A mobile telephony data access protocol, also referred to as 3.5G technology. HSDPA provides a smooth evolutionary path for UMTS-based 3G networks, allowing higher data transfer speeds (up to 14.4 Mb/s per cell in the downlink and 2 Mb/s per cell in the uplink). An evolution of the W-CDMA standard, HSDPA achieves the increase in data transfer speeds by defining a new W-CDMA channel.

HSUPAhigh-speed uplink packet access

A data access protocol for mobile phone networks with extremely high upload speeds (up to 5.76 Mb/s). Unlike HSDPA, which is 3.5G, HSUPA is considered 3.75G.

IABInternet architecture board

IANAInternet assigned numbers authority

Organization operated under the auspices of the ISOC as a part of the IAB. IANA delegates authority for IP address-space allocation and domain-name assignment to the InterNIC and other organizations. IANA also maintains a database of assigned protocol identifiers used in the TCP/IP stack, including autonomous system numbers.

IBGPinternal border gateway protocol

A protocol that uses BGP to connect routers that are in the same autonomous system.

ICMPinternet control message protocol

A network layer protocol that provides feedback on errors and other information specifically pertinent to IP packet handling.

ICONintershelf connection

Glossary

191

ICON cards connect the control-path communication infrastructure between the shelves in a 7670 RSP multishelf system.

IEEEInstitute of Electrical and Electronics Engineers

IETFInternet Engineering Task Force

The IETF is the organization that provides the coordination of standards and specification development for TCP/IP networking.

IGMPInternet group management protocol

IGPInterior Gateway Protocol

IGP is a generic term referring to any routing protocol, for example, IS-IS or OSPF, used to exchange reachability within an autonomous system.

IISPinterim inter-switch signaling protocol

IISP uses manual entries for address assignments to route ATM SVC call requests. This is a precursor to PNNI version 1.

ILMIintegrated link management interface

IMAinverse multiplexing over ATM

An algorithm that provides modular bandwidth for user access to ATM networks over multiple links.

iMBGPinternal multiprotocol BGP

IMSIP multimedia subsystem

The IMS is an IP multimedia and telephony core network that is defined by 3GPP and 3GPP2 standards and organizations based on IETF Internet protocols. IMS also refers to a standardized reference architecture that extends the NGN concepts, and consists of session control, connection control and an applications services framework along with subscriber and services data.

Glossary

192

InterNICAn organization that serves the Internet community by supplying user assistance, documentation, training, registration service for Internet domain names, and other services. Formerly called NIC.

I/Oinput/output

IPInternet protocol

IP is part of the TCP/IP family of protocols that describe the protocol that tracks the Internet address of nodes, routes outgoing messages, and recognizes messages. IP is used in gateways to connect networks at OSI network level 3 and higher.

IPv4Internet protocol version 4

Version of IP for a large part of the Internet traffic.

IPv6Internet protocol version 6

IPv6 improves on IPv4 in many ways, including a larger, 128-bit address space.

IRintermediate reach

IR is an optical fiber specification for single-mode, fiber-transmission systems suitable for distances of up to 15 km (9.3 mi).

IS-ISintermediate system to intermediate system

IS-IS is an ISO-standard, link-state routing protocol. Integrated IS-IS is an extension that allows IS-IS to be used for route determination in IP networks.

ISOCInternet society

ISPInternet service provider

An ISP is a business that provides access to the Internet.

ITU-TInternational Telecommunications Union–Telecommunications

Glossary

193

The ITU-T is an international body of member countries whose task is to define recommendations and standards relating to the international telecommunications industry.

IubIub interface

UMTS interface between the Radio Network Controller (RNC) and the Node B.

Iu-PSIu–packet switched

UMTS interface which refers to links between the RNC and a 3G Serving GPRS Support Node (3G SGSN).

LACPlink aggregation control protocol

A communication protocol defined in IEEE 802.3ad used to communicate link aggregation membership between two nodes. The information relayed through LACP can be used to dynamically include or exclude links from a link aggregation group.

LAGlink aggregation group

Two links that are treated by a higher layer as a single logical link. A link aggregation group is the logical equivalent to a single port. Applications that require a Gigabit Ethernet port can transparently use a link aggregation group.

LANlocal area network

A LAN is a network that operates in a limited geographical area, such as within a building. It connects a variety of data devices, such as PCs, servers, and printers. Communication between devices is at a very high rate: between 1 and 100 Mb/s.

LANElocal area network emulation

LAPlink access procedure

The LAP protocols are part of a group of data link layer protocols for framing and transmitting data across point-to-point links. LAP variants include LAP, LAPB, LAPD, and Link (LAPM). LAP was the original data link protocol for X.25. It was replaced by LAPB.

LAPBlink access procedure, balanced

Glossary

194

LAPB is a data link layer in the X.25 protocol stack. LAPB is a bit-oriented protocol derived from HDLC that ensures that frames are error-free and in the right sequence. Point to Point Protocol (PPP) from IETF is a variant of LAPB.

LAPDlink access procedure D-channel

LAPD is the protocol used on the Integrated Services Digital Network (ISDN) D channel. Call setup and other signaling takes place on the D channel. Data transmissions take place on B channels. LAPD is defined by the ITU-T Q.921.

LAPMLink Access Procedure for Modems

Layer 2 VPNAny VPN service that effectively operates at Layer 2 (data link) of the OSI stack. Layer 2 VPNs connect sites using frame relay, ATM, or Ethernet.

Layer 3 interfaceA Layer 3 interface is a logical interface that supports native IP routing and forwarding as well as signaling.

Layer 3 VPNLayer 3 VPNs connect sites in a secure and cost-effective manner across the public telecommunications infrastructure. Layer 3 VPNs are also known as RFC 4364 (formerly known as RFC 2547bis) VPNs, BGP/MPLS VPNs, or IP VPNs.

LC-ATMLabel-Controlled Asynchronous Transfer Mode (ATM).

An ATM network element can be referred to as an LC-ATM if it can support MPLS using LDP and ATM VC Switching.

LCRleast cost routing

A feature of a telephone system that automatically connects an outgoing telephone call with the telephone service that costs the least to that location at that time of day. Depending on how it is programmed, least cost routing will either drop down to the second-most efficient service if the first is not available, or it will give the caller a busy signal.

LDPlabel distribution protocol

A specific protocol that distributes labels between label-switched routers in an MPLS network.

Glossary

195

LDP-DoDlabel distribution protocol-downstream on demand

LDP-DUlabel distribution protocol-downstream unsolicited

LEDlight-emitting diode

An LED is a semiconductor diode that emits light when a current passes through it. LEDs are located on the cards and shelves of the 7670 RSP to indicate normal operation and alarm conditions.

LERlabel edge router

LLleased line

Leased lines are permanent telephone connections between endpoints set up by a telco. Typically, leased lines are used by businesses to connect geographically distant offices. Unlike normal dial-up connections, leased lines are always active.

L-LSPlabel-only-inferred per-hop behavior LSP

An LSP that carries traffic that has one or more priority levels.

LRlong range

LR is an optical-fiber specification for carrier-cable length greater than 40 km (24.9 mi).

LSAlink state advertisement

A packet-forwarding, link-state routing process to neighbor nodes that includes information concerning the local node, the link state of attached interfaces, or the topology of the network. LSAs are generated by link-state routing protocols such as OSPF and IS-IS.

LSPlabel-switched path

LSRlabel switch router

Glossary

196

An LSR is an MPLS node that runs MPLS control protocols and is capable of forwarding packets based on labels. An MPLS node may also be capable of forwarding native Layer 3 packets.

MAC addressmedia access control address

a MAC address is a computer’s unique hardware address.

MBSmaximum burst size

MBS is a traffic parameter that specifies the maximum number of cells in a burst that can be transmitted at the peak rate. In the signaling message, the burst tolerance is conveyed through the MBS, which is coded as a number of cells.

MC/ML-PPPmulticlass/multilink point-to-point protocol

MC/ML-PPP is a Layer 2 protocol for connection over synchronous or asynchronous circuits, designed to work with Layer 3 protocols, including IP.

MD5message digest version 5 algorithm

MD5 is a type of authentication. The MD5 algorithm takes an input message of arbitrary length and produces a 128-bit message digest of the input.

MFCmultifield classification

A function that allows service providers to assign CoS and DP to IP packets based on a set of rules in a list.

MIBmanagement information base

MIRminimum information rate

MIR is the minimum data transfer rate for a frame relay, VPC, or VCC path.

MMFmultimode fiber

MMF is an optical fiber capable of supporting the propagation of multiple bound modes through the fiber. The dispersion effects caused by the multiple bound modes limits the useful length of this type of fiber to less than 2 km (1.2 mi).

Glossary

197

MPLSmultiprotocol label switching

MPLS is a technology in which forwarding decisions are based on fixed-length labels inserted between the datalink and network layer headers to increase forwarding performance and path-selection flexibility.

MPLS-TEMPLS traffic engineering

A term, specific to 7670 RSP, that encompasses the protocols that support the traffic engineering used to signal the tunnel LSPs, which include RSVP, CR-LDP, or LDP-DoD.

MSCmobile switching center

MSC is a sophisticated telephone exchange that provides circuit-switched calling, mobility management, and global system for mobile communications services to the mobile phones roaming within the area that it serves.

MSOmultiple service operator

In the cable TV industry, an operator of multiple cable systems.

MTSOMobile Telephone Switching Office

The MTSO is the switching office that connects all of the individual cell towers to the switching equipment. This is a service switching point designed to provide interconnectivity between a cellular network and other cellular networks and the PSTN.

MTUMaximum Transmission Unit

MTU is a size (in bytes) of the largest packet that a given layer of a communications protocol can pass onwards.

NBAPNode B Application Part

NBAP is an application layer protocol for used for signaling communication with Node B.

NCCInetwork call correlation identifier

Glossary

198

NCInetwork control interface

A proprietary protocol that enables the 5620 NM to communicate with and control network nodes. It uses CPSS for inter-node messages.

NEBSNetwork Equipment Building Standards

Ne-NSCnetwork element–network service category

NGNnext generation networking

NGN is a broad term for network architectures where a convergence of voice and data is expected. The main idea behind the NGN concept is full separation of control, data, management and applications or services.

NNINNI is expanded two ways:

network-to-network interface

An NNI is a standard interface between two ATM nodes or two frame relay nodes.

network node interface

NNI is the interface between two ATM network nodes that operate under different administrative domains, such as a vendor ATM switch and an ATM switch from another vendor.

NOCnetwork operations center

A network operations center where administrators supervise, monitor and maintain a telecommunications network.

nrt-VBRnon-real-time VBR

nrt-VBR supports variable bit rate traffic where sustained and peak traffic volumes can tolerate variable but predictable transit delays.

NSSNetwork Switching Subsystem

A Network Switching Subsystem is the component of a GSM system that carries out switching functions and manages the communications between mobile phones and the Public Switched Telephone Network.

Glossary

199

NSSAnot-so-stubby area

An OSPF area type in which OSPF propagates any external routes that it learns about from within the autonomous system.

OAMoperations, administration, and maintenance

OAM functions consist of network maintenance features such as connectivity verification, alarm surveillance, continuity checking, and performance monitoring.

OCnoptical carrier n

OCn is the fundamental unit used in SONET hierarchy. OC indicates an optical signal and n represents increments of 51.84 Mb/s. OC3 has an optical rate of 155 Mb/s, OC12 has an optical rate of 622 Mb/s, and OC48 has an optical rate of 2.488 Gb/s.

OPEXoperational expenditure

OSIopen systems interconnection or interface

OSI is a framework of ISO standards for communication between different systems. Areas covered include systems management, and directory and transaction processing.

OSPFopen shortest path first

OSPF is an IETF standard link-state routing protocol used for route determination in IP networks.

OSSoperations support system

OSS comprises methods and procedures that directly support the daily operation of the telecommunications infrastructure.

P routerprovider router

A P router is a router in a provider network that does not attach to a CE device.

PBRpolicy-based routing

Glossary

200

Policy-based routing gives network administrators control over the way connections are routed across a PNNI routing domain, based on network-specific criteria and resource utilization strategies.

PCMpulse code modulation

In telecommunications, PCM means an 8-bit digital representation of an analog signal that has been compressed by either the A-law or Mu-law companding scheme.

PDUprotocol data unit

PE routerprovider edge router

A PE router is a router in a provider network that attaches to a CE device.

PHBper-hop behavior

PICPeripheral Interconnect card

The PIC is a system card for a multishelf system. The PIC provides a CSL interface port for the Peripheral Shelf Controller card in a Peripheral shelf.

PIMprotocol independent multicast

A multicast routing protocol that uses information in the unicast routing table to perform multicast routing.

PIM-SMprotocol independent multicast - sparse mode

A multicast routing protocol that is designed to provide efficient routing to multicast groups that may be sparsely distributed over wide-area networks. Multicast traffic is forwarded only to networks containing hosts that have explicitly requested the data.

PIM-SSMprotocol independent multicast – source specific mode

PIM-SSM is a derivation of PIM-SM that supports traffic from a single source to many receiving hosts. PIM-SSM uses the same join/prune procedure as PIM-SM, but does not need the RP-based, shared-tree infrastructure required by PIM-SM.

PIRpeak information rate

Glossary

201

PIR is the peak data transfer rate for a frame relay, VPC, or VCC path.

P-LSPpermanent label-switched path

A permanent MPLS path with a specified CoS and bandwidth connecting two specified interfaces.

PNNIprivate network node interface

PNNI is a routing protocol used between private cell relay switches.

POPpoint of presence

An access point to the Internet. Service providers usually have multiple POPs. A POP is a physical location, either part of the facilities of a telecommunications provider that the ISP rents, or a separate location from the telecommunications provider, that houses servers, routers, ATM switches, and digital/analog call aggregators.

PoSpoint of service

POSpacket over SONET

POS is a standard method of transporting Layer 3 packets directly on SONET interfaces using HDLC-like framing and simple link protocols like PPP. POS essentially bypasses Layer 2 processing by transporting Layer 3 packets, with little modification, directly on the physical layer.

POTSplain old telephone service

POTS refers to traditional telephone services with an analog bandwidth of less than 4 kHz. POTS is sometimes expanded as “plain old telephone system”.

See also PSTN.

PPDpartial packet discard

PPD is a congestion-control mechanism that discards remaining cells belonging to a partially discarded AAL PDU packet.

PPPpoint-to-point protocol

Glossary

202

PPP is an IETF standard protocol that allows a computer to use TCP/IP with a standard telephone line and a high-speed modem to establish a link between two (and only two) terminal installations.

PSCperipheral shelf controller

The peripheral shelf controller is a card used to manage all components of a Peripheral shelf and communicate with the Control complex in a multishelf configuration.

pseudowireA pseudowire is an unshared point-to-point link that emulates Layer 2 services (such as frame relay, ATM, or Ethernet) over an IP/MPLS core network. Pseudowires are provisioned through the network by targeted LDP signaling.

PSTNpublic-switched telephone network

PSTN is the worldwide voice telephone system.

PTSEPNNI Topology State Element

PNNI Topology State Element is a collection of PNNI information that is flooded among all logical nodes within a peer group.

PVCpermanent virtual circuit

A PVC is a defined virtual link with fixed endpoints set up by the network manager. A single virtual path may support multiple PVCs.

QFICquad fabric interface card

A QFIC is a system card that provides four HISL terminations for a Peripheral shelf, which provides data-path connectivity to a Switching shelf. The QFIC is used in a multishelf configuration of the 7670 RSP.

QoSquality of service

QoS is a term for the set of parameters and their values that determine the performance of a virtual circuit.

RADIUSRemote Authentication Dial In User Service

Glossary

203

RADIUS is a standardized method of information exchange between a device that provides network access to users (RADIUS client) and a device that contains authentication and profile information for the users (RADIUS server).

RANRadio Access Network

RAN is a part of the mobile network that performs the radio functionality, as well as providing the connection to the CN (Core Network). The RAN typically includes a controller (RNC, BSC elements) and several transmitter/receivers (Node B, BTS elements).

RBE interfacerouted bridged encapsulation interface

A Layer 3 interface on an ATM VC configured to use bridged Ethernet encapsulation.

RBOCregional Bell operating company

RC4Rivest cipher 4

A stream cryptographic algorithm that uses a variable-size symmetric key.

RCCrouting control channel

An RCC can be either a PVC or an SVCC connected through an NNI to a neighboring logical node. The purpose of an RCC is to carry PNNI protocol messages to and from neighboring nodes.

RDIremote defect indication

A signal returned to the transmitting equipment upon detection of certain defects on the incoming signal.

REDrandom early discard

RED is a congestion control method that randomly discards complete AAL-5 packets. The probability of discarding a packet increases as a function of the queue occupancy or loading.

RFCRequest For Comments

Glossary

204

RFC is the name of the result and the process for creating a standard on the Internet. New standards are proposed and published online as RFCs. The IETF is the consensus-building body that facilitates discussion, and eventually a new standard is established.

RFC is the prefix for all published IETF documents for Internet environment standards; for example, the official standard for e-mail is RFC 822. RFC documents typically define IP, TCP, and related application layer protocols.

RIBrouting information base

An internal table containing all of the routes known to a router. It includes routes currently being used for IP forwarding as well as all known alternate routes.

RIProuting information protocol

RIP is an IGP that uses distance vector routing and that is best suited for use in small, homogenous networks.

RNCRadio Network Controller

RPrendezvous point

A PIM router that is designed as the root of a PIM-SM shared tree in IP multicast applications. Join messages from receiving hosts for a multicast group are sent towards the RP, and data from multicast sources is sent to the RP so that hosts can receive the data and discover the senders.

Rp-NSCresource partition - network service category

RSVPresource reservation setup protocol

An IP-based protocol used for communicating application QoS requirements to intermediate transit nodes in a network. RSVP uses a soft-state mechanism to maintain the path and reservation state in each node in the reservation path.

RSVP-TEresource reservation setup protocol—traffic engineering

See RSVP.

rt-VBRreal-time VBR

Glossary

205

rt-VBR supports variable bit rate traffic with sustained and peak traffic parameters that requires strict delay control, such as packetized voice or video.

RUrack unit

Rxreceiver

The receiver is any part of the equipment that decodes entering signals or data into the desired form for use by the equipment.

SACswitch access card

A SAC is a system card that provides the connection point for the Switching shelves to the Control shelf or Peripheral shelves.

SCH cardscheduler card

An SCH card is a system card that analyzes and prioritizes the incoming cells crossing the fabric by communicating with the SACs.

SDHsynchronous digital hierarchy

SDH is an ITU-T standard for optical interfacing that is technically consistent with SONET.

SDLCsynchronous data link control

SDLC is a computer communications protocol. It is the Layer 2 protocol for IBM's Systems Network Architecture (SNA).

SDUservice data unit

An SDU is the payload of a packet, excluding the header, padding, and trailer.

SFTPsecure file transfer protocol

See also FTP.

SGSNServing GPRS Support Node

Glossary

206

The SGSN monitors the location of an individual mobile station and performs security functions and access control. In a UMTS network, the SGSN connects to the RNC over the Iu-PS interface.

SHA-1secure hash algorithm

A 160-bit unpatented hash algorithm.

SHDSLsingle-pair high-speed digital subscriber line

SIPSession Initiation Protocol

SIP is an application-layer control (signaling) protocol for creating, modifying, and terminating sessions with one or more participants. These sessions include Internet telephone calls, multimedia distribution, and multimedia conferences. Originally specified in RFC 3261, it has been accepted as a 3GPP signaling protocol and permanent element of the IMS architecture.

SIRsustained information rate

SIR is the long-term average data transfer rate for a VPC or VCC path.

SLAservice-level agreement

An SLA is a service contract between a network service provider and a subscriber that guarantees a particular QoS. SLAs are used for providing network availability and data-delivery reliability.

S-LSPsignaled label-switched path

A signaled MPLS path used to send IP packets between interfaces.

SMCSONET minimum clock

SMC is a synchronization quality on an OC3-2 or OC12-2 interface.

SMSshort messaging service

SMX cardswitch matrix card

The six SMX cards are system cards that work together to create the switching fabric.

Glossary

207

SMZ connectorAn SMZ connector is a 75O hm connector which features positive latching and quick termination assembly method.

SNMPSimple Network Management Protocol

SNMP is the Internet network management protocol. It provides the means to monitor and set network configuration and runtime parameters.

SONETsynchronous optical network

SONET is an optical interface standard that allows internetworking of transmission products from multiple vendors and that defines a physical interface, optical line rates known as OC signals, frame format and an OAM protocol. The base rate is 51.84 Mb/s (OC1), and higher rates are direct multiples of the base rate.

SPFshortest path first

An algorithm used by IS-IS and OSPF to make routing decisions based on the state of network links.

SPVCsoft permanent virtual circuit

An SPVC is a signaled, end-to-end network connection established as the result of an operator command. The user defines the endpoint at the source UNI, and the system dynamically establishes the network connections and maintains them for the duration of the call.

SRshort range

SR is an optical fiber specification for carrier-cable length less than 2 km (1.2 mi.)

SRRPsingle router redundancy protocol

SRRP is a proprietary Alcatel-Lucent protocol that is a subset of the VRRP protocol. SRRP makes it possible for service providers to replace two redundant routers configured with VRRP with a single 7670 RSP.

SS7Common Channel Signaling System No. 7

SS7 (also called S7 or C7) is a global standard for telecommunications defined by the International Telecommunications Union (ITU) Telecommunication Standardization Sector (ITU-T). The standard defines the procedures and protocol by which network

Glossary

208

elements in the public switched telephone network (PSTN) exchange information over a digital signaling network to effect wireless (cellular) and wireline call setup, routing and control. The ITU definition of SS7 allows for national variants such as the American National Standards Institute (ANSI) and Telcordia standards used in North America and the European Telecommunications Standards Institute (ETSI) standards used in Europe.

SSCSwitching shelf controller

SSHsecure shell

A UNIX-based command interface and protocol for securely getting access to a remote computer. SSH is used in place of Telnet.

SSH is widely used by network administrators to control Web servers and other kinds of servers remotely. SSH commands are encrypted and secure in several ways. Both ends of the client/server connection are authenticated using a digital certificate, and passwords are protected by being encrypted.

SSH version 2 (the latest version) is a proposed set of standards from the IETF.

SSMservice subscription manager

SSUsystem synchronization unit

An SSU is the circuit that generates the system clocks (C4M, FP, C3M) from whatever master clock source is selected.

STMsynchronous transfer mode

STM is a transport and switching method that depends on information occurring in regular and fixed patterns with respect to a reference such as a frame pattern.

STSsynchronous transport signal

STS is an electrical variant of the SONET OC signal. The basic rate is 51.84 Mb/s; higher rates are direct multiples of the base rate.

SVCswitched virtual circuit

An SVC is a signaled, end-to-end network connection. The user defines the endpoint at the source UNI, and the system dynamically establishes the network connections and maintains them for the duration of the call.

Glossary

209

SVCCswitched virtual channel connection

An SVCC is an end-to-end SVC formed by a series of linked VCs between cell relay devices.

switching fabricSwitching fabric is the combination of hardware and software that moves data coming into a network node out by the correct port to the next node in the network. Switching fabric includes the switching units in a node, the integrated circuits that they contain, and the programming that enables the control of switching paths. The switching fabric is independent of the bus technology and infrastructure used to move data between nodes, and also separate from the router. The term is sometimes used to collectively mean all switching hardware and software in a network.

T1transmission signal level 1

T1 is a digital transmission standard that conforms to AT&T Public 62411 at 1.544 Mb/s. It is the first level of the digital transmission hierarchy and is made up of 193 bits, grouped as one framing bit followed by 24 DS0 channels of 8 bits each. T1 is the standard generally used in North America and Japan. It is also known as DS1. The ETSI equivalent to T1 is E1.

TACtest access connection

A TAC allows access to a target connection so that it can be tested for integrity.

TCPtransmission control protocol

TCP is a communication protocol that hosts on the internet use to communicate with one another.

TDMtime division multiplexing

TDM is a process of sharing a communication channel among several users by allowing each to use the channel for a given period of time in a defined, repeated sequence.

TEtraffic extension

TelcordiaTelcordia (formerly known as Bellcore) is the organization responsible for researching and creating telecommunication technologies and concepts that became industry-wide standards.

Glossary

210

TelnetTelnet is the Internet-standard TCP/IP protocol for remote terminal connection service. It allows a user at one site to interact with a remote timesharing system at another site as if the user’s terminal connected directly to the remote machine.

TOStype of service

A bit field in the IP packet header that contains values indicating how each packet should be handled in the network.

triple-playFully integrated solution for the delivery of media-rich voice, data, and video service mix.

TS-CDMAtime division-synchronous code division multiple access

TS-CDMA is a 3G mobile telecommunications technology, formally announced as an approved 3G standard in the People's Republic of China.

TTMtime to market

TTM is the length of time it takes from a product being conceived to its being available for sale.

Txtransmit

Tx means to send or carry signals or data from a device; any part of the equipment that converts or encodes signals or data exiting from the equipment into the desired form for transmission to other equipment.

UBRunspecified bit rate

UBR is an ATM service type in which the network makes a “best effort” to meet the transmission bandwidth requirements.

UDPuser datagram protocol

A connectionless transport-layer protocol in the TCP/IP protocol suite. UDP is a simplified protocol that does not provide congestion management, packet loss notification feedback, or error correction; UDP assumes these will be handled by a high-layer protocol.

UDTunstructured data transfer

Glossary

211

UDT is a method of transporting data using one stream so that the entire 1.544 Mb/s T1 (DS1) stream is sent at once using up the whole bandwidth.

UMTSuniversal mobile telephone system

UMTS is one of the 3G mobile phone technologies. In Europe, the European Telecommunications Standards Institute (ETSI) was responsible for the UMTS standardisation process.

UNIuser-network interface

The UNI is the interface between ATM user equipment and an ATM network.

UTRANUMTS terrestrial radio access network

UTRAN is a collective term for the Node B and RNC network elements that make up the UMTS terrestrial RAN.

VBNvirtual backbone network

A VBN is a virtual network formed by the partitioning and reservation of bandwidth resources on links in an ATM service provider network that are used to establish switched connections for a particular service.

VCvirtual connection

A VC is a defined route between two end nodes that may access multiple virtual paths.

VCCvirtual channel connection

A VCC is virtual channels in two or more sequential physical circuits concatenated to create an end-to-end connection. A VCC represents a specific instance of a PVC, SPVC, or SVC. A VCC may traverse one end-to-end VPC or several sequential VPCs.

VCCVvirtual circuit connection verification

VCIvirtual channel identifier

A VCI is the 16-bit number in an ATM cell header identifying the specific virtual channel on which the cell is traversing on the current physical circuit.

Glossary

212

VLANvirtual bridged LAN

A VLAN divides a physical LAN into multiple virtual LANs whose members are not necessarily based on location. VLAN specifications are contained in IEEE 802.1Q.

VLLvirtual leased lines

VoBBvoice over broadband

VoBB is the use of broadband connections to deliver voice calls. Typically, services are hosted, meaning customers enjoy traditional phone functionality without the need to purchase a phone system at all. Calls are transmitted as IP packets to the host company, where they either “break out” to the public networks or continue as IP calls across the Internet. Due to the use of VoIP, calls can be delivered across the Internet for free in some circumstances.

VoDvideo on demand

VoIPvoice over IP

VoIP means sending voice information in digital form in packets rather than in the traditional protocols of the PSTN.

VoPvoice over packet

The voice over packet application enables both voice and signaling information to be transported over a packet network. In VoP systems, a gateway is needed to connect network traffic between packet-switched and circuit-switched networks. Types of VoP include VoIP, VoDSL, VoFR, and VoATM.

VPvirtual path

A VP is a group of virtual channels that can support multiple virtual circuits.

VPA shapingvirtual path aggregation shaping

VPA shaping is a commissioning capability that aggregates the traffic of multiple VCCs terminating on the same VPI and shapes the aggregated traffic on the egress port of a node to a particular VPC traffic descriptor, rather than shaping individual VCCs to their own traffic descriptors.

Glossary

213

VPCvirtual path connection

VPIvirtual path identifier

A VPI is an 8-bit value used to identify an ATM path. The VPI is part of the ATM Layer 2 address in the 5-byte header of an ATM cell. The VPI is assigned on connection setup by the devices at each end of a hop. Multi-hop VPC paths and VPC links use multiple VPIs to go from source to destination. Each switch that the VPC traverses cross-connects the VPC from one port and VPI to another port and VPI.

VPI/VCIvirtual path identifier/virtual channel identifier

The VPI and VCI are fields in the ATM cell header that combine to identify a connection in the network.

VPNvirtual private network

VRFvirtual routing and forwarding table

A logically partitioned information store containing a set of routing and forwarding information for a VPN or set of VPNs. This routing and forwarding information is made available only to specific Layer 3 interfaces on the PE that provide network connectivity for customer sites that are members of the VPN(s).

VRRPvirtual router redundancy protocol

VRRP is an election protocol that dynamically assigns responsibility for one or more virtual routers to the VRRP routers on a LAN, enabling several routers on a multi-access link to use the same virtual IP address. VRRP is designed to eliminate the single point of failure inherent in the static default-routed environment.

VS/VDvirtual source/virtual destination

VS/VD provides early feedback about congestion.

WANwide area network

A WAN is a geographically dispersed, long-haul telecommunications network usually made up of backbone links. The term distinguishes a broader telecommunication structure from a local area network. A WAN may be privately owned or rented, but the term usually connotes the inclusion of public networks that are highly regulated and provide superior reliability and resilience.

Glossary

214

W-CDMAwideband code division multiple access

W-CDMA is a type of 3G cellular network. W-CDMA is the higher speed transmission protocol used in the UMTS.

X.121ITU-T X.121

X.121 is a standard that describes the international numbering plan for public data networks.

X.25ITU-T X.25

X.25 defines the standard protocol for communication between packet-switched public data networks and user devices in the packet-switched mode.

X.25 provides reliability and end-to-end guaranteed delivery of data.

XLRextra long range

XLR is an optical-fiber specification for carrier-cable length greater than 110 km (68.8 mi).

215

Index

Numbers

3G networksconverged infrastructure, 14evolving 3G RAN aggregation to IP, 12mobile aggregation and backhaul, 8mobile RAN aggregation, 11

6PE, 806VPE, 807670 ESE, 167670 RSP

broadband aggregation, 34combatting security threats, 126Ethernet services, 23high speed Internet access, 35IP VPNs, 27key value propositions, 2, 1MPLS convergence, 30Multiservice IP/MPLS for mobile networks, 16

network applications, 7video services, 38voice over broadband, 36VoP using multiservice IP networks, 45VPNs, 18

A

admission control, 72hierarchy, 72Layer 3 interfaces and LSPs, 72transport interfaces, 72

architecture principles, 86high performance, 87high-availability, 86IP/MPLS and ATM functionality, 87scalability, density, and flexibility, 86

ATMconnection resource display, 56cross-connections, 50Ethernet services, 24ILMI 4.0, 53IMA, 52OAM PM, 56PNNI routing, 53standardized AINI support, 55switching architecture, 50traffic management, 56

ATM pseudowiresMPLS, 33

ATM switching architecturemultishelf system, 50single-shelf system, 50

B

broadbandvideo architecture, 39

broadband services, 35aggregation, 34high speed access, 35video, 38voice over broadband, 36

Index

216

C

control cardredundancy, 108SSC, 109

control card functions, 90alarm consolidation, 90data spooling, 90network management interface support, 90node management support, 90routing and call processing, 90

control plane redundancynon-stop ATM signaling, 111

Control shelfcards, 93circuit-card area, 93fan area, 93

Control shelf cardsCC2G, 93CIC, 93DFIC and QFIC, 93Facilities card, 93ICON I/O and ICON I/O expansion cards, 93ICON management card, 93

converged MPLS data networks7670 RSP solution, 32benefits, 32FR/ATM network interworking, 33MPLS core with ATM over MPLS, 33ships-in-the-night mode, 32

cross-connectionsPVCs, 50SPVCs, 51SVCs, 51

D

data plane redundancyAPS/LCR redundancy, 111LAG redundancy with LACP, 112management interface redundancy, 112soft restart on software upgrades, 113

data plane securityaccess list statistics, 118access lists for rate limiting, 118access lists for traffic filtering, 118packet filtering and copying of traffic, 118

E

Edge Services Card;See ESCESC, 99Ethernet Layer 2 VPNs

benefits, 24Ethernet transparent LAN service, 24Ethernet-to-ATM service interworking over ATM, 26

Ethernet-to-ATM service interworking over MPLS, 26

Ethernet-to-frame relay service interworking over ATM, 25

Ethernet-to-frame relay/ATM interworking services, 25

MPLS convergence, 30services, 24VLL over MPLS, 25VLL service, 24

Ethernet services, 247670 RSP VPN, 24ATM, 24interworking, 25point-to-point, 24virtual leased line, 25

external management5620 Network Manager, 129CLI, 129network management functions, 129SNMP, 129

F

filters, 63LSP tunnels, 63multiple parallel LSPs, 64prefix-based filters, 64

G

Gigabit Ethernetoperating distance, 146receive port optical parameters, 145transmit port optical parameters, 145

Index

217

H

high-availabilitycontrol redundancy, 86diagnostics, 86fabric redundancy, 86hitless upgrade, 86infrastructure redundancy, 86mid-plane, 86safety net, 86

high-speed Internet access, 35

I

I/O cards1-port OC12c/STM4 I/O card, 1021-port OC48/STM16 Channelized I/O card, 103

1-port OC48c/STM16 I/O card, 1032-port Gigabit Ethernet I/O card, 1032-port OC12c/STM4 I/O card, 1024-port OC12/STM4 Channelized I/O card, 103

4-port OC3c/STM1 I/O card, 1024-port STM1 Electrical I/O card, 1028-port DS3 I/O card, 1018-port OC3/STM1 I/O card, 1028-port OC3c/STM1 I/O card, 1028-port STM1 Electrical I/O card, 1028-port STM1 Electrical MR48 card, 102

infrastructurecontrol card redundancy, 108cooling redundancy, 110power redundancy, 110redundancy, 106switching fabric redundancy, 106system timing redundancy, 110

internal managementadministrative layer, 130alarms, 132control card, 130database, 131database conversion, 131indicators, 132LEDs, 132resource layer, 130system timing, 131

IP data plane, 68admission control, 72DHCP relay, 73differentiated services and DSCP to CoS profile, 71

DSCP remarking, 71ICMP, 70IP CoS, 70IP forwarding, 68IP interface groups, 69MR48 line card IP interface, 69multifield classification, 71packet filtering using access lists, 71reverse path filtering, 72routed bridged encapsulation, 69SRRP, 70

IP multicast, 76IGMP, 77PIM-SM, 78static multicast, 77

IP routing support, 73benefits, 74CSPF for RSVP-TE, 75ECMP, 76graceful restart helper for BGP, 75graceful restart helper for OSPF, 76non-stop IP routing, 73non-stop RSVP-TE, 74RIPv2 support, 75routing policies, 76

IP VPNs, 27, 817670 RSP solution, 81ATM pseudowires over MPLS, 33ATM to IP/MPLS convergence, 32dedicated and differentiated tunnels, 81high-availability architecture, 81import and export route targets support, 81Layer 2 and Layer 3 services support, 81QoS and traffic management, 81virtualized DHCP relay, 81

IP/MPLS, 617670 RSP as an LER, 627670 RSP as an LSR, 62filters, 63graceful restart for LDP, 65IP data plane, 61IP multicast, 61IP routing support, 61MPLS signaling link protocols, 61

Index

218

S-LSP hierarchy, 61S-LSP path modification without break, 61S-LSP protection, 61S-LSPs, 61

IPv6, 79certification, 79ICMPv6, 80non-stop routing, 79QoS, 79services, 29tunneling, 80

K

key value propositionscomprehensive management solution, 2FR and ATM services over converged MPLS backbone, 2

new and traditional Layer 2 and Layer 3 services, 2

scalable architecture, 2service resiliency, 2

L

Layer 2 VPNs, 20application achitectures, 27ATM and frame relay Layer 2 VPNs, 22benefits, 21Ethernet Layer 2 VPNs, 23frame relay-to-ATM network interworking, 22

frame relay-to-ATM service interworking, 23

MPLS convergence, 30line cards, 99

ESC, 99Gigabit Ethernet, 100IEEE 802.3ad link aggregation on GigE card, 101

MR 16 ATM card, 100MR 16 POS card, 101MR 8 ATM/IP card, 101MR48 channelized card, 100OC48c/STM 16 SONET/SDH ATM card, 101

M

management plane securityCLI security through SSH, 123cryptographic algorithms, 124encrypted configuration databases, 123event logging, 124file transfer security using SFTP, 123login authentication using a RADIUS server, 121

login authentication using the node database, 121

node management security through SNMP v3, 123

public key management, 124redundant syslog servers for event logging, 125

secure protocols for node management, 122secured local storage of passwords, 124user login authentication, 121

mobile networks7670 RSP, 16converged infrastructure for 2 G, 2.5 G and 3 G, 14

mobile transport infrastructure, 8advanced voice processing, 16IPv6 readiness, 16network optimization, 16reliability, 16scalability, 16seamless migration to 3G services, 16service flexibility, 16simplified operation, 16SLA, 16

MPLSATM pseudowires, 33

MPLS OAM, 68MPLS signaling protocols, 65

parallel links, 66signaling link types, 65

multishelfspecifications, 150

multishelf system, 91control plane, 95control shelf, 92

Index

219

N

network applications, 7, 7high speed Internet access, 35MPLS convergence, 30video services, 38voice over broadband, 36VoP, 45

new featuresATM networking, 6IP features, 6MPLS features, 6security, 6system features, 6

NGN VoP with IP networks, 457670 RSP benefits, 37ATM network requirements, 46end office displacement, 47IP/MPLS requirements, 47toll office displacement, 45VoBB solution, 37voice over broadband, 36

O

OAM PM, 56OAM round-trip delay, 56round-trip delay, 56

operating distanceGigabit Ethernet, 146

optical parametersGigabit Ethernet

receive port, 145transmit port, 145

P

peripheral shelf, 96cards, 97circuit-card area, 97fan area, 97

peripheral shelf cardsDFIC and QFIC, 97Facilities card, 97PIC, 97PSC card, 97

platform securityDoS resiliency, 117hardened real-time operating system, 116multiprocessor availability, 117non-stop services, 117resource utilization metering, 117separate routing and control plane, 117

PNNIaddress summarization, 54hierarchy, 53policy-based routing, 55restricted transit, 54routing, 53routing support for exterior reachable address, 54

topology database display, 53PSC card redundancy, 109Pseudowires, 83

R

redundancycontrol plane, 111data plane, 111switching fabric, 106

routing plane securityIP routing and signaling, 119MD5 authentication between routing peers, 120

network control plane, 119per-IP-flow rate limiting, 120resistance to DoS attacks, 119

S

S-LSPs, 64fast reroute, 68fault detection, 67path modification without break, 66protection, 67reversion, 67tunnel, 66

securitydata plane, 118management plane, 120platform level, 116routing plane, 119

Index

220

single-shelf cardsCC2G, 90CIC, 90facilities, 90switch, 91

single-shelf systembreaker panel and power termination area, 88

cards, 89circuit-card area, 88fan area, 89layout, 88

single-shelf to multishelf upgrade, 98specifications

multishelf, 150SPVCs, 51, 51

hitless SPVC moves using DBR, 52network call correlation identifier, 52point-to-multipoint, 52

SSC card redundancy, 109standardized AINI support

link loop detection, 55switching fabric

redundancy in multishelf system, 107redundancy in single-shelf system, 106

Switching shelf, 95switching shelf

cards, 96circuit-card area, 95fan area, 96SAC card, 96SCH and SMX cards, 96SSC card, 96

system architecture, 85architecture principles, 85I/O cards, 101line and I/O cards, 99multishelf configuration, 85peripheral shelf, 85single-shelf to multishelf configuration upgrade, 85

supported line cards and I/O cards, 85switching shelf, 85

system configurations, 87single-shelf system, 87

system management, 127external, 128Layer 2 and Layer 3, 128

system reliability and redundancy, 105

T

traffic management capabilities, 56ATM call failure diagnostic, 59CAC, 58congestion control, 58network congestion management, 57QoS parameters, 57service categories, 57traffic policing and shaping, 58VP aggregation shaping for CBR VPs, 58

V

video services using DSL and IP networksATM multicast model, 41broadcast TV architecture, 39DSLAM aggregation, 34IP multicast model, 39video on demand architecture, 42

voice over broadband, 36VoIP

Class 4toll office displacement, 45

Class 5end office displacement, 47

VPNsATM and frame relay, 22Ethernet services, 23IP, 27IPv6 services, 29Layer 2, 20

Customer documentation and product support

Technical support

Customer documentation

Product manuals and documentation updates are available through the Alcatel-Lucent SupportDocumentation and Software Download service at alcatel-lucent.com. If you are a new userand require access to this service, please contact your Alcatel-Lucent sales representative.

Customer documentation feedback

http://www.alcatel-lucent.com/support

http://www.alcatel-lucent.com/osds

[email protected]

alcatel lucent 7670 routing switch platform general information release 7.1

Documents