stinger configuration guide - ip-sa · stinger configuration guide part number: 7820-0711-002 for...

Stinger Configuration Guide

Part Number: 7820-0711-002For software version 7.11.0

August 1999

Lucent Technologies

Copyright© 1999 Lucent Technologies. All Rights Reserved.

This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion byany entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the expresswritten consent of Lucent Technologies, Inc.

Notice

Every effort was made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject tochange.

Security Statement

In rare instances, unauthorized individuals make connections to the telecommunications network through the use of access features.

Trademarks

DSLPipe, DSLMAX, DSL Terminator, MAX, MAX TNT, MultiDSL, Pipeline, and Stinger are trademarks of Lucent Technologies. Other trademarks andtrade names mentioned in this publication belong to their respective owners.

Ordering Information

To order copies of this document, contact your Lucent Technologies representative or reseller.

Support Telephone Numbers

For a menu of support and other services, call (800) 272-3634. Or call (510) 769-6001 for an operator.

Stinger Configuration Guide iii

Customer ServiceCustomer Service provides a variety of options for obtaining technical assistance, information about Lucent products and services, and software upgrades.

Obtaining technical assistance

You can obtain technical assistance by telephone, email, fax, or modem, or over the Internet. If you need help with a problem, make sure that you have the following information when you call or that you include it in your correspondence:

• Product name and model.

• Software and hardware options.

• Software version.

• Type of computer you are using.

• Description of the problem.

Calling from within the United States

In the U.S., you can take advantage of Priority Technical Assistance or an Advantage Pak service contract, or you can call to request assistance.

Priority Technical Assistance

If you need to talk to an engineer right away, call 900-555-2763 to reach the Lucent InterNetworking Systems Priority Call queue. The charge of $2.95 per minute does not begin to accrue until you are connected to an engineer. Average wait times are less than three minutes.

Advantage Pak

Advantage Pak is a one-year service contract that includes overnight advance replacement of failed products, technical support, software maintenance releases, and software update releases. For more information, call 800-272-3634.

Other telephone numbers

For a menu of Lucent InterNetworking Systems services, call 800-272-3634. Or call 510-769-6001 for an operator.

Calling from outside the United States

Outside the United States, use one of the following numbers:

Telephone outside the United States 510-769-8027

Asia Pacific (except Japan) +61 3 9656 7000

Austria/Germany/Switzerland +33 492 96 5672

Benelux +33 492 96 5674

iv Stinger Configuration Guide

For a list of support options in the Asia Pacific Region, refer to

http://apac.ascend.com/contacts.html

Obtaining assistance through correspondence

Use one of two email addresses for technical support questions: one is for customers in the United States, and the other is for customers in Europe, the Middle East, and Asia. If you prefer to correspond by fax, BBS, or regular mail, please direct your inquiry to U.S. offices. Following are the ways in which you can reach Customer Service:

• Email from within the U.S.—[email protected]

• Email from Europe or the Middle East—[email protected]

• Email from Asia Pacific—[email protected]

• Fax—510-814-2312

• Customer Support BBS (by modem)—510-814-2302

• Write to Lucent InterNetworking Systems at the following address:

Attn: Customer Service1701 Harbor Bay ParkwayAlameda, CA 94502-3002

Finding information and software on the Internet

Visit http://www.ascend.com for technical information, product information, and descriptions of available services.

Visit ftp.ascend.com for software upgrades, release notes, and addenda.

France +33 492 96 5673

Italy +33 492 96 5676

Japan +81 3 5325 7397

Middle East/Africa +33 492 96 5679

Scandinavia +33 492 96 5677

Spain/Portugal +33 492 96 5675

UK +33 492 96 5671

Stinger Configuration Guide v

Contents

Customer Service ..................................................................................................................... iii

About This Guide ............................................................................. xiii

Documentation conventions................................................................................................... xii iDocumentation set................................................................................................................... xivRelated publications ................................................................................................................ xiv

Related RFCs ................................................................................................................... xivITU-T recommendations................................................................................................... xvANSI standards ................................................................................................................. xvATM specifications........................................................................................................... xv

Chapter 1 Getting Started ................................................................................ 1-1

Using a Stinger unit as a DSL Access Multiplexer................................................................ 1-1Stinger switching operations.................................................................................................. 1 -2

Virtual circuit (VC) switching ........................................................................................ 1-2Virtual path (VP) switching............................................................................................ 1-2

Overview of Stinger configuration ........................................................................................ 1-3Configuring the primary Control Module (CM)............................................................. 1-3Configuring the Line Interface Modules (LIMs)............................................................ 1-3Configuring the Trunk Modules (TM)............................................................................ 1-4Configuring system clocking modes............................................................................... 1-4Defining ATM traffic contracts ...................................................................................... 1-4Configuring ATM circuits and terminating connections ................................................ 1-4

Stinger management features ................................................................................................. 1-5Using the command-line interface.................................................................................. 1-5Tracking system activity ................................................................................................. 1-5Onboard flash memory and software updates................................................................. 1-6SNMP support................................................................................................................. 1-6RADIUS support............................................................................................................. 1-6

Where to go next .................................................................................................................... 1-7

Chapter 2 Configuring the Control Modules.................................................. 2-1

Logging into the primary CM ................................................................................................ 2-1Restricting administrative access ........................................................................................... 2-2

Changing defaults for serial-port logins ......................................................................... 2-2Changing the default admin password............................................................................ 2-3Setting a Telnet password ............................................................................................... 2-4

Providing a basic system IP configuration............................................................................. 2-5IP address syntax ............................................................................................................ 2-5Assigning the Ethernet IP addresses ............................................................................... 2-7Defining the soft interface for fault tolerance................................................................. 2-7

vi Stinger Configuration Guide

Contents

Configuring a default route............................................................................................. 2-8Verifying a LAN connection for administrators............................................................. 2-9

Enabling a Stinger unit to use RADIUS ................................................................................ 2-9Overview of external authentication settings................................................................ 2-10Example of configuring a Stinger unit to use RADIUS ............................................... 2-11

Configuring controller redundancy...................................................................................... 2-12Overview of redundancy operations ............................................................................. 2-12Overview of the Redundancy profile settings............................................................... 2-13Example of specifying a primary CM preference......................................................... 2-14

Chapter 3 Configuring the Line Interface Modules ....................................... 3-1

Manual LIM sparing ............................................................................................................. . 3-1Allocating LIM bandwidth..................................................................................................... 3-3

Overview of bandwidth settings ..................................................................................... 3-3Guaranteed vs. maximum upstream bandwidth.............................................................. 3-4Example of bandwidth allocation configuration............................................................. 3-4

Configuring VPI/VCI ranges for LIM slots ........................................................................... 3-5Configuring ATM SDSL interfaces....................................................................................... 3-6

Overview of SDSL settings ............................................................................................ 3-7Displaying SDSL port status and nailed groups ...................................................... 3-8Maximum data rates and session data rates............................................................. 3-8VPI used for VP switching on SDSL port ............................................................... 3-8

Example of SDSL interface configuration...................................................................... 3-9Configuring ATM ADSL-DMT interfaces ............................................................................ 3-9

Overview of AL-DMT settings..................................................................................... 3-10Line activation and DMT parameters .................................................................... 3-10Rate-adaptive mode parameters............................................................................. 3-12Power Spectral Density (PSD) and power-level parameters ................................. 3-13Fast and interleaved bit-rate parameters ................................................................ 3-14Interleaving delay parameters................................................................................ 3-15Noise margin parameters ....................................................................................... 3-16Dynamic rate-adaptive noise margin parameters .................................................. 3-17

Examples of AL-DMT interface configuration ............................................................ 3-18Checking LIM status............................................................................................................ 3-20

Checking the status of an SDSL interface .................................................................... 3-20Checking the status of the physical interface ........................................................ 3-20Obtaining statistics about operations ..................................................................... 3-21

Checking the status of an AL-DMT interface .............................................................. 3-23Checking the status of the physical interface ........................................................ 3-23Obtaining statistics about operations ..................................................................... 3-25

Checking the status of manual LIM sparing ................................................................. 3-26Checking bandwidth status ........................................................................................... 3-26

Chapter 4 Configuring the Trunk Modules..................................................... 4-1

Trunk port sparing............................................................................................................. ..... 4-1Trunk port sparing settings ............................................................................................. 4-2Example of automatic sparing configuration.................................................................. 4-2Example of manual sparing configuration...................................................................... 4-3

Using trunk ports as clock source .......................................................................................... 4-3Informing the system of its clock source ........................................................................ 4-4Configuring trunk ports as eligible clock sources .......................................................... 4-4

Contents

Stinger Configuration Guide vii

VPI/VCI allocation for trunk ports ........................................................................................ 4-5Configuring DS3-ATM interfaces ......................................................................................... 4-7

Overview of DS3-ATM settings..................................................................................... 4-8Displaying DS3 port status and nailed groups................................................................ 4-9Setting DS3 framing formats .......................................................................................... 4-9Example of DS3-ATM configuration ........................................................................... 4-10

Configuring OC3-ATM interfaces....................................................................................... 4-11Overview of OC3-ATM settings .................................................................................. 4-11Displaying OC3 status and nailed groups..................................................................... 4-13Changing physical-layer interface settings ................................................................... 4-13Examples of OC3-ATM configuration ......................................................................... 4-13

Checking ATM trunk interface status .................................................................................. 4-15DS3 ATM status information ....................................................................................... 4-15Checking OC3-ATM interface status ........................................................................... 4-17

Checking line and ATM framer status .................................................................. 4-17Monitoring errors and performance of the SONET payload ................................. 4-19

Chapter 5 Specifying Traffic Contracts .......................................................... 5-1

Overview of ATM Quality of Service parameters................................................................. 5-1ATM service categories .................................................................................................. 5-3Traffic policing and shaping ........................................................................................... 5-4Flow control .................................................................................................................... 5-4

Examples of defining a traffic contract.................................................................................. 5-5Example of a Constant Bit Rate contract........................................................................ 5-6Example of a Variable Bit Rate contract ........................................................................ 5-7Example of an Available Bit Rate (ABR) contract......................................................... 5-8

Chapter 6 Configuring ATM Circuits............................................................... 6-1

Overview of ATM circuit settings ......................................................................................... 6-2RADIUS profile settings................................................................................................. 6-4How circuits are established ........................................................................................... 6-5Identifying a circuit’s physical interfaces....................................................................... 6-5Assigning valid VPI/VCI pairs ....................................................................................... 6-6

VPIs and VCIs on LIM slots ................................................................................... 6-6VPIs and VCIs on trunk ports.................................................................................. 6-6

Applying traffic contracts ............................................................................................... 6-7Examples of ATM circuits using VC switching .................................................................... 6-7

Configuring a LIM-to-trunk circuit (DSLAM operations) ............................................. 6-7Configuring a trunk-to-trunk circuit ............................................................................... 6-8Configuring a LIM-to-LIM circuit ............................................................................... 6-10

Example of VP switching configuration.............................................................................. 6-11Example of Stinger-A configuration (VP switching) ................................................... 6-12

Sample LIM port configuration............................................................................. 6-12Sample trunk port configuration............................................................................ 6-12Sample CPE Connection profile............................................................................ 6-13Sample trunk-to-trunk circuit for traffic from Stinger-B....................................... 6-13

Example of Stinger-B CPE configurations (VC switching) ......................................... 6-14Checking the status of an ATM circuit ................................................................................ 6-15

viii Stinger Configuration Guide

Contents

Chapter 7 Configuring Terminating ATM Connections ................................. 7-1

Overview of ATM connection settings.................................................................................. 7-2Local Connection profile settings ................................................................................... 7-2RADIUS profile settings................................................................................................. 7-3IP information ................................................................................................................. 7-4AAL5 multiplexing......................................................................................................... 7-4

Example of a terminating connection .................................................................................... 7-4Sample Stinger configuration ......................................................................................... 7-5Sample far-end DSLTNT configuration ......................................................................... 7-6

Checking the status of an ATM connection........................................................................... 7-7

Index.......................................................................................... Index-1

Stinger Configuration Guide ix

Figures

Figure 1-1 Example of DSLAM operations ................................................................... 1-1Figure 1-2 VC switching ................................................................................................ 1-2Figure 1-3 VP switching................................................................................................. 1-2Figure 2-1 Default subnet mask for class C IP address.................................................. 2-5Figure 2-2 Local backbone router to be used as default route ....................................... 2-8Figure 2-3 RADIUS servers on local network ............................................................. 2-11Figure 2-4 Redundant paths to each CM...................................................................... 2-12Figure 3-1 Maximum upstream real-time traffic in Mbits per second ........................... 3-3Figure 3-2 Default VPI/VCI range ................................................................................. 3-5Figure 3-3 SDSL ATM LIM configuration.................................................................... 3-9Figure 3-4 How noise margin parameters relate to power adjustments ....................... 3-16Figure 3-5 Future support: How noise margins related to dynamic rate adaptation .... 3-17Figure 3-6 ADSL ATM LIM configuration ................................................................. 3-19Figure 4-1 DS3 interfaces to the ATM network........................................................... 4-10Figure 4-2 OC3 interfaces to the ATM network .......................................................... 4-14Figure 4-3 SONET layers............................................................................................. 4-20Figure 5-1 When traffic policing and shaping can occur during DSLAM operations ... 5-4Figure 5-2 Congestion management with Explicit Forward Congestion Indicator........ 5-5Figure 5-3 Flow control for ABR traffic with Explicit Rate Marking ........................... 5-5Figure 6-1 ATM circuits on LIM and trunk interfaces................................................... 6-1Figure 6-2 LIM to trunk circuit (DSLAM operations)................................................... 6-7Figure 6-3 Trunk-to-trunk circuit ................................................................................... 6-9Figure 6-4 LIM-to-LIM circuit..................................................................................... 6-10Figure 6-5 Example of VP switching and VC switching ............................................. 6-12Figure 7-1 Terminating ATM connection ...................................................................... 7-1Figure 7-2 Terminating connection from DSLTNT....................................................... 7-5

Stinger Configuration Guide xi

Tables

Table 1-1 Where to go next........................................................................................... 1-7Table 2-1 IP address classes and number of network bits............................................. 2-5Table 2-2 Decimal subnet masks and prefix lengths..................................................... 2-6Table 3-1 VPI/VCI bit sizes .......................................................................................... 3-6Table 4-1 Combined settings and resulting number of VCCs on the port .................... 4-7

Stinger Configuration Guide xiii

About This Guide

This guide describes how to configure a Stinger unit and define ATM connections for different types of traffic. In the current software version, ATM connections are Permanent Virtual Circuits (PVCs).

This guide assumes that you have already installed the Stinger unit and connected a workstation to the primary controller’s serial port. If you have not already finished those tasks, please see the Stinger Hardware Installation Guide.

! Warning: Please read the safety instructions in the Stinger Hardware Installation Guide before installing or operating the product.

Documentation conventionsFollowing are all the special characters and typographical conventions used in this manual:

Convention Meaning

Monospace text Represents text that appears on your computer’s screen, or that could appear on your computer’s screen.

Boldface mono-space text

Represents characters that you enter exactly as shown (unless the char-acters are also in italics—see Italics, below). If you could enter the characters but are not specifically instructed to, they do not appear in boldface.

Italics Represent variable information. Do not enter the words themselves in the command. Enter the information they represent. In ordinary text, italics are used for titles of publications, for some terms that would otherwise be in quotation marks, and to show emphasis.

[ ] Square brackets indicate an optional argument you might add to a command. To include such an argument, type only the information inside the brackets. Do not type the brackets unless they appear in bold type.

| Separates command choices that are mutually exclusive.

Key1-Key2 Represents a combination keystroke. To enter a combination key-stroke, press the first key and hold it down while you press one or more other keys. Release all the keys at the same time. (For example, Ctrl-H means hold down the Control key and press the H key.)

Press Enter Means press the Enter, or Return, key or its equivalent on your com-puter.

xiv Stinger Configuration Guide

About This GuideDocumentation set

Documentation setThe Stinger documentation set includes the following manuals:

• TAOS Command-Line Interface Guide. Introduces the Stinger command-line environment and shows you how to use the command line interface effectively. Describes keyboard shortcuts. Introduces commands, security levels, profile structure, and parameter types.

• Stinger Hardware Installation Guide. Shows how to install the Stinger hardware. Includes the Stinger technical specifications and an architectural overview.

• Stinger Configuration Guide (this manual). Describes how to use the command-line interface to configure the Stinger modules. Provides instructions for configuring ATM PVCs using the command-line interface or an external RADIUS server.

• Stinger Reference Guide. An alphabetic reference to all Stinger profiles, parameters, and commands.

• Stinger Administration Guide. Describes how to administer the Stinger, including how to monitor the system and its modules, troubleshoot the unit, and enable SNMP.

Related publicationsThis guide and documentation set do not provide a detailed explanation of products, architectures, or standards developed by other companies or organizations. Following are some publications that you might find useful:

Related RFCs

RFCs are available on the Web. The Stinger unit supports the standards and MIBs described in the following RFCs:

• RFC 1407: Definitions of Managed Objects for the DS3/E3 Interface Type

• RFC 1483: Multiprotocol Encapsulation over ATM Adaptation Layer 5

• RFC 1595: Definitions of Managed Objects for the SONET/SDH Interface Type

• RFC 2138: Remote Authentication Dial In User Service (RADIUS)

• RFC 2515: Definitions of Managed Objects for ATM Management

Note: Introduces important additional information.

!Caution:

Warns that a failure to follow the recommended procedure could result in loss of data or damage to equipment.

!Warning:

Warns that a failure to take appropriate safety precautions could result in physical injury.

Convention Meaning

About This GuideRelated publications

Stinger Configuration Guide xv

ITU-T recommendations

ITU-T (formerly CCITT) recommendations are available commercially. You can order them at http://www.itu.ch/publications/.

ANSI standards

The Stinger unit supports the ANSI T1.413 (Issue 2) specification: Telecommunications - Network and Customer Installation Interfaces - Asymmetric Digital Subscriber Line (ADSL) Metallic Interface

ATM specifications

The Stinger unit is compliant with the following ATM specifications:

• ATM Forum Traffic Management Specification Version 4.0.

• ATM User-Network-Interface (UNI) Signaling Specification Version 3.1.

Stinger Configuration Guide 1-1

1Getting Started

:

Using a Stinger unit as a DSL Access MultiplexerA Stinger unit operates as an ATM switch-through Digital Subscriber Line Access Multiplexer

(DSLAM). It switches data from multiple xDSL subscribers onto a high-speed ATM backbone.

Figure 1-1. Example of DSLAM operations

For DSLAM operations, data transmitted from the CPE to the Stinger unit is upstream traffic.

Data transmitted from the Stinger unit to the CPE is downstream traffic.

In the current software version, Stinger units switch traffic at OSI Layer 2. They do not

currently route user data. However, they do support IP routing for terminating connections,

such as administrative Telnet or SNMP sessions to the unit itself.

Using a Stinger unit as a DSL Access Multiplexer . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Stinger switching operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Overview of Stinger configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3

Stinger management features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Where to go next . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1- 7

D O W N S T R E A M

U P S T R E A M

ATM

DSL CPE

DSL Terminator

1-2 Stinger Configuration Guide

Getting StartedStinger switching operations

Stinger switching operationsA Stinger unit receives cells across a link on a known VPI/VCI pair, and retransmits the cells on another interface using another VPI/VCI pair. For PVCs, the administrator configures both VPI/VCI pairs manually by specifying an ATM circuit in a Connection or RADIUS profile, as described in Chapter 6, “Configuring ATM Circuits.” An ATM circuit can specify a virtual circuit or a virtual path.

Virtual circuit (VC) switching

A virtual circuit is a point-to-point connection between an end system (such as a user) and an end point in the ATM network (the point at which the cell stream leaves the ATM layer). VCCs are switched on the basis of a unique VPI/VCI pair, an operation called VC switching.

Figure 1-2. VC switching

When the Stinger unit is performing VC switching, it switches cells on the basis of the VCI number and a VPI number which is typically (but not necessarily) zero. Both the VPI and VCI numbers may change as they are switched onto the outbound leg of the circuit.

Virtual path (VP) switching

A virtual path is a bundle of virtual channels that are grouped together and switched on the basis of a common VPI. The VCI numbers associated with the individual connections are not used for switching purposes. This operation is called VP switching.

Figure 1-3. VP switching

For VP switching, the Stinger switches cells on the basis of the VPI number. The VCI numbers do not change as they are switched onto the next VPI. VP switching leaves the VCI numbers untouched.

VPI 2

VPI 3VPI 1

VCI 35

VCI 37

VCI 22

VCI 137

VPI 3VPI 1

VCI 35

VCI 37

Getting StartedOverview of Stinger configuration


Overview of Stinger configurationBefore you configure a Stinger unit, you should create a diagram that illustrates how the unit will interoperate with your current network configuration. Creating a comprehensive network diagram helps prevent problems during installation and configuration, and can help in troubleshooting any problems later.

Stinger configuration tasks include the following:

• Configuring the primary control module

• Configuring the DSL line interface modules

• Configuring the trunk modules

• Defining ATM traffic contracts

• Configuring connections, either locally or through RADIUS

Note: Stinger configuration settings are stored in onboard flash memory, and should be backed up to a TFTP host whenever changes are made. For details about backing up and restoring the Stinger configuration, see the Stinger Administration Guide.

Configuring the primary Control Module (CM)

Each of the Control Modules (CMs) has an RS-232 serial port (labeled Diag Port) and a 10Base-T Ethernet port. The serial port is for system management from a local workstation. It is also the standard error output for stack traces and messages in the event of a system crash. Until you have assigned IP addresses to the system’s Ethernet interfaces, you must use a local workstation connected to the primary controller’s serial port to configure the Stinger unit. There is no other way to log into the unit to perform the initial configuration.

The system’s Ethernet ports are intended for light data and management traffic. Once you have assigned the ports IP addresses, administrators can Telnet into the unit from a local host and download configuration files from a TFTP server to the Stinger system.

A Stinger unit has a range of options for configuring IP and for protecting the unit from unauthorized administrative access. In addition, you should verify that the default CM redundancy configuration is appropriate for your site. Most sites operate the unit with redundant controllers, although it can operate with a single controller. If the unit has two CMs installed, check the status lights on the CM front panel to see which CM is the primary module. For details, see the Stinger Hardware Installation Guide.

Note: All configuration must take place on the primary CM. The primary CM configuration repository overwrites that of the secondary CM immediately after every configuration change and at regular intervals.

Configuring the Line Interface Modules (LIMs)

A Stinger unit supports up to 14 Line Interface Modules (LIMs), which can be any combination of 48-port SDSL and 12-port ADSL-DMT ATM modules. LIMs reside in the front panel of the unit. Each port on a LIM has a variety of configuration options, including line rates and bandwidth. The way you configure each line depends on your connectivity needs.


Getting StartedOverview of Stinger configuration

On LIM slots, administrators can configure VPI/VCI ranges to enable the slot to accept inbound connections from particular types of DSL modems. For example, Alcatel™ modems assume a VPI of 8 and a VCI of 35. All ports on a LIM slot use the same configured VPI/VCI range.

Every enabled DSL port has a unique nailed-group number assigned as a factory default. Most sites enable only the DSL ports that are in use, which results in better system performance. (By default, DSL ports are disabled.)

Configuring the Trunk Modules (TM)

A Stinger unit can support up to two Trunk Modules (TMs), which can be OC3-ATM or DS3-ATM. TMs reside in the back panel of the unit. You can set up the unit to use the full trunk-side bandwidth actively, or you can designate one or two of the trunk ports as spares, to be used only when one or the other of the other trunks goes down.

Each of the Stinger trunks connects to an ATM switch, and the line configuration includes settings that must match between the local and far-end switch interfaces.

Trunk-side, the Stinger unit supports up to 32K connections using VC switching. By default, the system distributes the maximum of 32K VCCs equally across the four trunk ports. Administrators can configure VCI ranges to cause a port to handle more or less of the total number of VC-switched connections.

Note: There is no restriction on the number of VCIs supported on virtual path connections (VPCs).The system does not examine the VCI value when it is performing VP switching.

Configuring system clocking modes

The unit requires a clock source for its timing subsystem. By default, it uses a built-in 8KHz clock on the primary CM as its timing source. Administrators can configure the system to take its clock source from a trunk port or from an external Building Interoffice Timing Source (BITS) clock connected to the Stinger Alarm board.

For details about configuring a trunk port to source the ATM network clock and feed it to the primary CM, see “Using trunk ports as clock source” on page 4-3.

For details about using the BITS source, see the Stinger Hardware Installation Guide.

Defining ATM traffic contracts

A Stinger unit supports ATM traffic management, which is configurable as a group of related capabilities (a contract). After you define a number of traffic contracts that specify a service category and related attributes, you can apply a contract to each upstream and each downstream data flow through the unit.

Configuring ATM circuits and terminating connections

An ATM circuit is a switch-through ATM connection received on one physical interface of the Stinger unit and transmitted on another. For example, if the unit is operating as a DSLAM, a connection received on a LIM port and switched out on a trunk port is one ATM circuit.

Getting StartedStinger management features


DSLAM operations make use of LIM-to-trunk circuits. The system also supports LIM-to-LIM and trunk-to-trunk circuits.

The unit can also accept inbound ATM connections that terminate locally. These are IP-routed connections that specify a local destination address.

You can configure connections locally or in RADIUS. With the current software version, all ATM connections are PVCs, which means they are nailed connections.

Stinger management featuresTo enable administrators to configure the system and monitor its activity, Stinger units support profiles, commands, and status windows in the command-line interface. Stinger units also support SNMP management, RADIUS profiles, and the ability to upload (back up) and download software and configuration files via TFTP or serial connection.

A Stinger system provides several permission levels to control the management and configuration functions that are accessible in the command-line interface. For information about User profiles and other management features, see the Stinger Administration Guide.

For an introduction to the command-line interface and its shortcuts, see the TAOS Command-Line Interface Guide.

Using the command-line interface

The Stinger command-line interface provides access to commands, profiles, and status windows. You must use the command-line interface to provide the initial system and IP configuration for the unit, although you can choose to perform subsequent configuration tasks remotely through SNMP, or by downloading configuration files via TFTP.

Tracking system activity

A Stinger unit supports many commands for monitoring system activity. To display the commands that are available with the permission settings in the current User profile, enter the help (or ?) command. The following example shows the commands available for the admin login. The left column shows command names, and the right column shows the command class, which determines the permissions required to use the command.

admin> ? ? ( user ) arptable ( system ) auth ( user ) callroute ( diagnostic ) clear ( user ) clock-source ( diagnostic ) clr-history ( system ) connection ( system ) date ( update ) debug ( diagnostic ) delete ( update ) device ( diagnostic ) dir ( system )


Getting StartedStinger management features

dircode ( system ) ether-display ( diagnostic ) fatal-history ( system ) format ( code ) fsck ( code ) get ( system ) hdlc ( system )[More? <ret>=next entry, <sp>=next page, <^C>=abort]

For details about each command, see the Stinger Reference Guide. For more information about command help, see the TAOS Command-Line Interface Guide.

The command-line interface supports several status windows that focus on different aspects of system activity (such as connection status and log messages). The windows provide a great deal of read-only information about what is currently happening in the unit. To display a status window, enter the Status command:

admin> status

The system prompt moves to just below the status window. To close the status window, enter the command again:

admin> status

If the system prompt is not visible below the status window, press Escape to display it.

Onboard flash memory and software updates

Onboard flash RAM enables you to perform software upgrades in the field. You can upgrade the Stinger unit through its serial port by accessing it locally, or you can download software upgrades from a TFTP server. For details, see the Stinger Administration Guide.

SNMP support

In addition to managing a Stinger unit by means of the command-line interface, administrators can manage the unit by using an SNMP management station such as NavisAccess. A Stinger unit can generate SNMP traps to indicate alarm conditions and it relies on SNMP community strings to implement SNMP security.

For information about using SNMP with Stinger units, see the Stinger Administration Guide.

RADIUS support

Administrators can use RADIUS to store user profiles for ATM circuits and terminating connections. The RADIUS server must be compliant with the Vendor-Specific Attribute (VSA), as defined in RFC 2138. To use RADIUS, you must also configure the Stinger unit to communicate with the RADIUS server.

Getting StartedWhere to go next


Where to go nextWhen you have planned your network, you are ready to configure the Stinger unit. You can perform configuration tasks in any order you want. Table 1-1 shows where to look for the information you need.

Table 1-1. Where to go next

To do this: See:

Determine which CM is primary Stinger Hardware Installation Guide

Establish a serial connection Stinger Hardware Installation Guide

Set up basic access security “Restricting administrative access” (page 2-2)

Configure IP “Providing a basic system IP configuration” (page 2-5)

Configure the unit to use RADIUS “Enabling a Stinger unit to use RADIUS” (page 2-9)

Check the Redundancy settings “Configuring controller redundancy” (page 2-12)

Configure the unit’s LIMs “Configuring the Line Interface Modules” (page 3-1)

Checking LIM port status “Checking LIM status” (page 3-20)

Configure the unit’s trunk lines “Configuring the Trunk Modules” (page 4-1)

Checking trunk status “Checking ATM trunk interface status” (page 4-15)

Define ATM traffic contracts “Specifying Traffic Contracts” (page 5-1)

Configure ATM circuits “Configuring ATM Circuits” (page 6-1)

Configure VP switching “Example of VP switching configuration” (page 6-11)

Configure IP-routed connections that terminate in the Stinger

“Configuring Terminating ATM Connections” (page 7-1)

Check details about parameters and commands

Stinger Reference Guide

Use SNMP with the unit Stinger Administration Guide

Configure login permissions Stinger Administration Guide

Back up the system configurationStinger Administration Guide

Test lines and ports Stinger Administration Guide


2Configuring the Control Modules

The primary Control Module (CM) performs all controller operations for the Stinger unit. It manages and boots the LIMs, maintains a central repository of the unit’s configuration, performs call control and processing operations, and manages all centralized functions, such as SNMP access or communication with a RADIUS server.

The secondary CM does not perform controller operations unless the primary CM resets or the administrator manually changes the primary/secondary status of the CMs. However, administrators can Telnet into the secondary CM and run commands. The secondary CM has up-to-date configuration and system activity information.

Control module configuration includes the following tasks:

• Logging into the unit from a workstation connected to the primary CM serial port

• Changing default security settings to protect the unit

• Configuring IP to make the system accessible by Telnet, SNMP, and Ping

• Configuring RADIUS access (if appropriate)

• Checking the Redundancy profile settings, and modifying them if appropriate

Logging into the primary CMTo configure the unit initially, or after clearing its NVRAM, you must connect a workstation to the primary CM serial port (labeled Diag Port). For information about checking the status lights to determine which CM has been elected primary, and about establishing a serial connection between a workstation and the primary CM serial port, see the Stinger Hardware Installation Guide.

After connecting the management workstation, launch a communications program that supports terminal emulation. The terminal emulation settings should specify 9600 bps, 8 data bits, 1 stop bit, and no parity or flow control. When you launch the program, the Stinger unit uses settings in the Serial profile to authenticate the serial-port login. With the default settings in that profile, it prompts for the password of the User profile named admin. For example:

Password:

Logging into the primary CM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Restricting administrative access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Providing a basic system IP configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

Enabling a Stinger unit to use RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Configuring controller redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12


Configuring the Control ModulesRestricting administrative access

Enter the password Ascend to authenticate the admin User profile. For example:

Password: Ascend

Typically, the name specified in the User profile appears as your system prompt. For example, if you log in as admin, the following prompt appears:

admin>

After you have supplied basic IP information, as described in “Providing a basic system IP configuration” on page 2-5, you can access the Stinger command-line interface through the serial port, or by using Telnet from an IP host. Or, you can log in by using an SNMP management station, such as NavisAccess, from an IP host. In any case, no matter how you access the unit, you must authenticate a User profile and supply a password to acquire administrative permissions.

For details about User profiles, see the Stinger Administration Guide.

Restricting administrative accessEach Stinger unit is shipped from the factory with its security features set to defaults that enable you to configure and set up the unit without any restrictions. Before you bring the unit online, you should change the default security settings to protect the configured unit from unauthorized access.

Changing defaults for serial-port logins

To help protect the system from unauthorized access on one of its CM serial interfaces, change the following (factory default) settings:

[in SERIAL/{ shelf-1 control-module 2 }] user-profile = admin auto-logout = no

A Stinger unit automatically creates a Serial profile for each installed CM. To list the Serial profiles, use the Dir command as follows:

admin> dir serial 5 06/20/1999 02:57:48 { shelf-1 control-module-2 2 }12 06/20/1999 03:01:46 { shelf-1 control-module 2 }

Parameter Specifies

User-Profile Name of the User profile to be used for logins on the CM serial port. User profiles set permissions and other parameters for logins to the Stinger command-line interface. If no name is specified, the system prompts for both the name and password of a User profile, as it does for Telnet logins.

Auto-Logout Enable/disable termination of the serial-port login if the DTR signal is lost on the interface. A yes setting causes the system to log out the administrative login even if the administrator forgets to enter the Quit command in the terminal-emulation program.



The designations control-module and control-module-2 refer to the slot position, not the primary/secondary status of each CM. To make serial logins more secure, modify both Serial profiles to specify a null User profile name and enable the Auto-Logout parameter. For example:

admin> read serial {1 control-module 2}SERIAL/{ shelf-1 control-module 2 } read

admin> set user-profile =

admin> set auto-logout = yes

admin> writeSERIAL/{ shelf-1 control-module 2 } written

admin> read serial {1 control-module-2 2}SERIAL/{ shelf-1 control-module-2 2 } read

admin> set user-profile =

admin> set auto-logout = yes

admin> writeSERIAL/{ shelf-1 control-module-2 2 } written

Changing the default admin password

The admin User profile sets permissions that enable most levels of activity, so access to that login should be carefully restricted. To protect the admin login, you should change its well-known password the first time you log into the unit. Following is the relevant parameter, shown with the factory default setting:

[in USER/admin]password = "Ascend"

You can specify any password, up to 20 characters. All future logins governed by the admin User profile must provide the new password.

For example, the following commands change the password to x1!35DPG:

admin> read user adminUSER/admin read

admin> set password = x1!35DPG

admin> writeUSER/admin written

Note: If the password is displayed as a string of asterisks rather than readable text, you do not have sufficient permissions to read or change the password. For information about how to enable the permission or log in with a different User profile, see the Stinger Administration Guide or the Allow-Password entry in the Stinger Reference Guide.

Parameter Specifies

Password Text string of up to 20 characters, which must be entered by a user to log in with permissions authorized by the admin profile. The value is case sensitive.



When an administrator Telnets into the Stinger unit, the system prompts for the name and password of a User profile and authenticates the information before allowing the Telnet session. For example:

% telnet 1.1.1.1Trying 1.1.1.1...Connected to 1.1.1.1Escape character is ‘^]’.

User: adminPassword: x1!35DPG

Setting a Telnet password

A Telnet password is a global, system-wide password to be required for Telnet logins to the unit. The Telnet password is requested before the system accepts the connection and prompts for the name of a User profile. Following are the parameters, shown with default settings, related to Telnet logins to a Stinger unit:

[in IP-GLOBAL]telnet-password = ""user-profile = ""

For example, the following commands set the Telnet password to dpg01!:

admin> read ip-globalIP-GLOBAL read

admin> set telnet-password = dpg01!

admin> writeIP-GLOBAL written

When a Telnet password has been specified, the system requires a two-tier password authentication for Telnet logins. For example:

% telnet 1.1.1.1<stinger01> Enter Password: dpg01!

Trying 1.1.1.1...Connected to 1.1.1.1Escape character is ‘^]’.

User: adminPassword: **********

Parameter Specifies

Telnet-Password Text string of up to 20 characters, required from all users requesting a Telnet session. A user is allowed three attempts, with 60 seconds per attempt, to enter the correct password. A third unsuccessful attempt terminates the login process. The value is case-sensitive.

User-Profile Name of a default User profile for authenticating Telnet logins. If no name is specified, the system prompts the user to enter the name of a User profile.

Configuring the Control ModulesProviding a basic system IP configuration


If the user enters an incorrect Telnet password, the system prompts again, allowing up to three attempts before timing out. If the user specifies the correct password, the connection is established and the user is prompted to enter the name and password of a valid User profile.

Providing a basic system IP configurationTo enable Telnet and SNMP access to the unit, and to allow connectivity between the unit and local IP hosts, you must assign IP addresses to the Stinger Ethernet ports and configure basic IP routing.

Note: A Stinger unit does not require IP routing to operate as a DSLAM. The system does not provide IP routing for user data.

IP address syntax

A Stinger unit uses dotted decimal format (not hexadecimal) for IP addresses. If no subnet mask is specified, the unit assumes a default mask based on the address class. Table 2-1 shows address classes and the number of network bits in the default mask for each class.

For example, a class C address, such as 198.5.248.40, has 24 network bits, leaving 8 bits for the host portion of the address. If no subnet mask is specified for a class C address, the Stinger assumes the default mask of 24 bits:

Figure 2-1. Default subnet mask for class C IP address

A subnet address includes a prefix length, which specifies the number of network bits in the address. For example, the following address specifies a 29-bit subnet:

ip-address = 198.5.248.40/29

In this address, 29 bits of the address are used to specify the network. The three remaining bits are used to specify unique hosts on the subnet. With three bits used to specify hosts on a 29-bit subnet, eight different bit combinations are possible. Of those eight possible host addresses, two are reserved:

000 — Reserved for the network (base address)001010100

Table 2-1. IP address classes and number of network bits

Class Address range Default network bits

Class A 0.0.0.0—127.255.255.255 8

Class B 128.0.0.0—191.255.255.255 16

Class C 192.0.0.0—223.255.255.255 24

1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 0 0 0 0 0 0 0 0

Default 24 bits



110

101011111 — Reserved for the broadcast address of the subnet

Note: Be careful with zero subnets (subnets with the same base address as a class A, B, or C network). Early implementations of TCP/IP did not allow them. For example, the subnet 192.32.8.0/30 was illegal because it had the same base address as the class C network 192.32.8.0/24, while the subnet 192.32.8.4/30 was legal. Modern implementations of TCP/IP

support zero subnets, and the Stinger implementation of RIP treats these subnets the same as any other network. However, it is important that you treat zero subnets consistently throughout your network. Otherwise, you will encounter routing problems.

Table 2-2 shows subnet masks and prefix lengths for a class C network number.

The broadcast address of any subnet has the host portion of the IP address set to all ones. The

network address (or base address) represents the network itself, because the host portion of the IP address is all zeros. For example, if the Stinger configuration assigns the following address to a remote router:

198.5.248.120/29

The Ethernet network attached to that router has the following address range:

198.5.248.120 — 198.5.248.127

A host route is a special-case IP address with a prefix length of /32. For example:

198.5.248.40/32

Host routes are to a single host, rather than to a router or subnet.

Table 2-2. Decimal subnet masks and prefix lengths

Subnet mask Number of host addresses Prefix length

255.255.255.0 254 hosts + 1 broadcast, 1 network base /24







255.255.255.254 invalid mask (no hosts) /31

255.255.255.255 1 host—a host route /32



Assigning the Ethernet IP addresses

A Stinger unit creates an IP interface for the Ethernet port of each CM. To list the IP interfaces, use the Dir command as follows:

admin> dir ip-interface16 03/30/1999 20:22:58 { { shelf-1 control-module-2 1 } 0 }14 04/05/1999 10:03:32 { { any-shelf any-slot 0 } 0 }16 04/05/1999 10:11:35 { { shelf-1 control-module 1 } 0 }

The designations control-module and control-module-2 refer to the slot position, not the primary/secondary status of each CM. The IP-Interface profile with the zero index (the default any-shelf any-slot index) is reserved for the soft interface, which is described in “Defining the soft interface for fault tolerance” on page 2-7.

In this example, the CM in the first control-module slot position is the primary CM. The following commands assign the primary CM the address 1.1.1.1/24:

admin> read ip-interface { { shelf-1 control-module 1 } 0 }IP-INTERFACE/{ { shelf-1 control-module 1 } 0 } read

admin> set ip-address = 1.1.1.1/24

admin> writeIP-INTERFACE/{ { shelf-1 control-module 1 } 0 } written

The following commands assign the address 1.1.1.2/24 to the secondary CM:

admin> read ip-interface { { shelf-1 control-module-2 1 } 0 }IP-INTERFACE/{ { shelf-1 control-module-2 1 } 0 } read

admin> set ip-address = 1.1.1.2/24

admin> writeIP-INTERFACE/{ { shelf-1 control-module-2 1 } 0 } written

After you assign IP addresses, you can verify that the Stinger unit is a valid IP host on its configured networks by Pinging other hosts on those networks, as shown in the following example:

admin> ping 1.1.1.56PING 1.1.1.56: 56 Data bytes64 bytes from 1.1.1.56: icmp_seq=0 ttl=255 time=0 ms64 bytes from 1.1.1.56: icmp_seq=3 ttl=255 time=0 ms^C--- 1.1.1.56: Ping statistics ---2 packets transmitted, 2 packets received, 0% packet lossround-trip min/avg/max = 0/0/0 ms

Defining the soft interface for fault tolerance

A Stinger unit supports a soft IP interface, which is an internal interface that never goes down. Therefore, as long as one of the unit’s IP interfaces is up, the soft interface address is reachable.

The soft IP interface is associated only with the primary CM, regardless of which slot is operating as primary. The soft interface is hidden from the secondary CM. When the system powers on, it waits until a controller becomes the primary CM before setting up the soft



interface. If a switchover occurs (the secondary CM becomes primary), the system reinitializes the soft interface at that time.

The IP-Interface profile with the zero index is reserved for the soft interface. If RIP is enabled, the unit advertises the interface address as a host route (with a prefix length of /32) using the loopback interface. If RIP is not enabled, routers one hop away from the unit must have a static route to the soft interface address. (For more information, see “Verifying a LAN connection for administrators” on page 2-9.)

The following commands set the soft interface IP address to 1.1.1.128/24:

admin> read ip-interface { 0 0 0 }IP-INTERFACE/{ { any-shelf any-slot 0 } 0 } read

admin> set ip-addr = 1.1.1.128/24

admin> writeIP-INTERFACE/{ { any-shelf any-slot 0 } 0 } written

Configuring a default route

A default route is a static route that specifies destination address of zero and the IP address of an external router. The Stinger unit routes all IP packets with unknown destinations to the specified external router. If no default route is defined, the unit drops IP packets for which it has no route.

Figure 2-2 shows the Stinger Ethernet interfaces on a subnet, connected to the same Ethernet segment as a local backbone router. In this network, the Stinger can use the local router as its default route.

Figure 2-2. Local backbone router to be used as default route

Making a local router the default route enables the Stinger unit to pass all unrecognized IP packets to that router, so its own routing tables can remain small. The external router maintains large routing tables, and assumes the responsibility and overhead of routing most packets.

For example, the following commands define a default route to the LAN router in Figure 2-2:

admin> new ip-route defaultIP-ROUTE/default read

admin> set gateway-address = 1.1.1.3

admin> set active-route = yes

admin> writeIP-ROUTE/default written

Secondary CMEthernet Port

Primary CMEthernet Port

1.1.1.1/24

1.1.1.2/24

Hub

1.1.1.3/241.1.2.3/24

Local router

Configuring the Control ModulesEnabling a Stinger unit to use RADIUS


The system can support multiple default routes. The profile name does not have to be default. The only requirements are that the destination address must be zero, and Gateway-Address must specify a valid, reachable router.

For information about other settings in the IP-Route profile, see the Stinger Reference Guide.

Verifying a LAN connection for administrators

To enable administrators to log into the Stinger unit’s interface from local IP hosts, you must also make sure that the external LAN router can route to the unit. By default, RIP is disabled on Stinger interfaces. Because the unit is not primarily a Layer-3 device, many sites do not enable RIP on the local interfaces.

If RIP is disabled on the Stinger interfaces, you must inform the local router about the Stinger addresses and which of the local router interfaces connect to the same subnet. The method you use to do so depends on the type of router. For example, if the hosts on the local network can already Ping each other and the local router, you would use commands such as the following to inform the local router about the Stinger addresses. These sample commands specify the Stinger LAN interfaces shown in Figure 2-2, as well as the Stinger unit’s soft interface address:

% route add 1.1.1.1 1.1.1.3 1

% route add 1.1.1.2 1.1.1.3 1

% route add 1.1.1.128 1.1.1.3 1

After adding the routes, you should be able to Ping the unit from local hosts. For example, the following command executed on a local host tests connectivity to the soft interface:

% ping 1.1.1.128PING 1.1.1.128 (1.1.1.128): 56 Data bytes64 bytes from 1.1.1.128: icmp_seq=0 ttl=255 time=0 ms64 bytes from 1.1.1.128: icmp_seq=7 ttl=255 time=0 ms^C--- 1.1.1.128 Ping statistics ---8 packets transmitted, 8 packets received, 0% packet lossround-trip min/avg/max = 0/0/0 ms

Enabling a Stinger unit to use RADIUSMany sites choose to maintain a centralized external RADIUS database of user profiles. To use RADIUS with Stinger units, the RADIUS server must comply with the Vendor-Specific Attribute (VSA) specification, defined in RFC 2138, Remote Authentication Dial In User Service (RADIUS). All Ascend attributes of Type 91 or smaller are available only in VSA compatibility mode. The Ascend Vendor-Id is 529.

In addition, you must add the ATM-related VSAs from the most recent Ascend RADIUS dictionary to the RADIUS server’s dictionary. The relevant RADIUS attributes are documented in Chapter 6, “Configuring ATM Circuits,” and Chapter 7, “Configuring Terminating ATM Connections.”



Overview of external authentication settings

To configure a Stinger unit to forward access requests to a RADIUS server, you must set values in the External-Auth profile. Following are the relevant parameters, shown with default settings:

[in EXTERNAL-AUTH]auth-type = Nonelocal-profiles-first = lpf-yes

[in EXTERNAL-AUTH:rad-auth-client]auth-server-1 = 0.0.0.0auth-server-2 = 0.0.0.0auth-server-3 = 0.0.0.0auth-port = 0auth-key = ""auth-timeout = 0auth-radius-compat = old-ascend

Parameter Specifies

Auth-Type Type of external authentication server. Must be set to radius.

Local-Profiles-First Enable/disable searching for a local Connection profile before attempting to access the RADIUS server. If the parameter is set to lpf-no, the unit searches RADIUS first, and checks local profiles only if it does not find a matching RADIUS profile. Set the parameter to lpf-no if you intend to configure all (or most) ATM connections in RADIUS profiles.

Auth-Server-1

Auth-Server-2

Auth-Server-3

IP address of up to three RADIUS servers. The Stinger unit first tries to connect to Auth-Server-1. If it receives no response and the next two parameters specify nonzero addresses, it tries to connect to Auth-Server-2. If it still receives no response, it tries Auth-Server-3. If the unit connects to a server other than Auth-Server-1, it continues to use that server until the server fails to service requests, even if the first server has come back online.

Auth-Port UDP port for communication with RADIUS. The port number must match the port specified for use in the server’s configuration.

Auth-Key Shared secret (a text string of up to 22 characters, known to both the Stinger unit and the RADIUS server).A shared secret is used to authenticate packets exchanged between the unit and the RADIUS server. On the RADIUS server, the same shared secret must be specified for the Stinger unit in the server’s clients file.

Auth-Timeout Number of seconds between attempts to reach RADIUS servers. The Stinger unit waits the specified number of seconds for a response. If the unit does not receive a response within the specified number of seconds, it times out the request and attempts to reach the next server, if one has been specified in the Auth-Server-2 or Auth-Server-3 settings.



Note: For details about other parameters in the External-Auth profile, see the Stinger Reference Guide.

Example of configuring a Stinger unit to use RADIUS

In Figure 2-3, the Stinger unit is connected to a backbone router, and two RADIUS servers reside on the local backbone. The RADIUS dictionaries on both servers have been updated to

include Vendor-Specific Attributes related to Stinger configuration.

Figure 2-3. RADIUS servers on local network

In this example, the Stinger unit is configured to search first for RADIUS profiles, and to

check for local profiles only if a match is not found. It is also configured to send RADIUS

requests to UDP port 512 on the RADIUS server with which it is communicating, and to use rasecret as the shared secret.

The following commands configure the External-Auth profile:

admin> read external-auth

EXTERNAL-AUTH read

admin> set local-profiles-first = lpf-no

admin> set rad-auth-client auth-server-1 = 1.1.2.1

admin> set rad-auth-client auth-server-2 = 1.1.2.2

admin> set rad-auth-client auth-radius-compat = vendor-specific

admin> set rad-auth-client auth-port = 512

admin> set rad-auth-client auth-key = rasecret

admin> write external-auth

EXTERNAL-AUTH written

Auth-RADIUS-Compat Enable/disable VSA compatibility mode when the unit is using RADIUS for authentication and authorization purposes. Must be set to vendor-specific to enable VSA compatibility mode. In VSA compatibility mode, the Stinger unit uses the Vendor-Specific attribute to encapsulate Ascend vendor attributes and uses the RFC-defined User-Password encryption algorithm.

Parameter Specifies

Secondary CMEthernet Port

Primary CMEthernet Port

1.1.1.1/24

1.1.1.2/24

Hub

1.1.1.3/241.1.2.3/24

Backbone router

1.1.2.1/24

1.1.2.2/24


Configuring the Control ModulesConfiguring controller redundancy

Configuring controller redundancyIf two CMs are installed and both modules are available, the system chooses one of the modules to be the primary CM when the system starts up. If the Redundancy profile specifies that one of the controllers is preferred, the system makes that CM primary. If no preference is configured in the Redundancy profile, the system chooses the controller that was primary most recently. If neither of these criteria apply, the system chooses the controller in the first CM slot.

By default, the system allows either CM to become primary without agreement from the other CM, and does not specify a preference for either CM to become primary. Unless you change the default settings in the Redundancy profile, the CM in the first slot becomes primary.

Note: If you keep the default settings, no configuration is required for CM redundancy. The default settings are recommended for the current software version.

Overview of redundancy operations

The primary and secondary CMs use a heartbeat protocol to monitor each other and maintain synchronized repositories of the system configuration stored in the primary CM flash memory. If the primary CM resets, the system switches over to the standby CM. The mechanism for switchover is built into the CM hardware and allows the switchover to occur instantaneously.

To maintain full functional redundancy, the primary and secondary CMs have separate paths to each LIM and TM, as shown in Figure 2-4.

Figure 2-4. Redundant paths to each CM

The primary CM manages the LIMs and assumes all the normal controller responsibilities of managing the unit and handling the call control and circuit management functions.

In the event of a switchover, the LIMs are not hardware reset (to avoid the need to retrain the DSL modems). However, the system drops all connections. It rebuilds them after the new primary CM completes its initialization. Log messages notify user of the following significant events related to CM redundancy:

• CM becomes primary.

• CM became primary and no secondary is present.

TM TM

CMCM

LIMs

LPMs and 1:n LIM switchover redundancy

1:1 redundant CMs

TMs and 1:1 port switchover redundancy



• Primary CM lost heartbeat communication with secondary CM.

• Primary CM has established heartbeat communication with secondary.

• CM has a software crash (Fatal log message).

Overview of the Redundancy profile settings

The Redundancy profile stores information, or contexts, that the two CMs exchange within the heartbeat protocol to track each other’s status. The contexts are stored as two arrays. The first array (context 1) represents the first CM slot, and the second array (context 2) represents the second CM slot.

Most of the settings in the Redundancy profile are visible only when debug permissions are enabled in the current User profile, and cannot be set by administrators. But administrators can modify the following Redundancy parameters (shown with default settings):

[in REDUNDANCY]primary-preference = no-preference

[in REDUNDANCY:context[1]]must-agree = False

[in REDUNDANCY:context[2]]must-agree = False

Note: Most of the parameter settings in context 1 and context 2 of the Redundancy profile are for internal use and cannot be set by administrators.

Parameter Specifies

Primary-Preference Which controller is given preference to become primary. With the default no-preference setting, the decision is left up to the system. The system chooses the controller that was primary most recently, or the controller in the first CM slot.

If the parameter is set to first-controller-preferred, the system gives preference to the controller in the first CM slot. If the CM in the first slot is not available, it makes the CM in the second slot primary.

If the parameter is set to second-controller-preferred, the system gives preference to the controller in the second CM slot. If that CM is not available, it makes the CM in the first slot primary.

Must-Agree Enable/disable the requirement that the controllers must agree about which CM is primary. The default setting of False, which is the recommended setting for this release, allows a CM to become primary without agreement from the other CM.



Example of specifying a primary CM preference

In the following example, the administrator configures the controller in the second CM slot to be elected primary unless the controller is unavailable:

admin> read redundancyREDUNDANCY read

admin> set primary-preference = second-controller-preferred

admin> writeREDUNDANCY written


3Configuring the Line Interface Modules

The Line Interface Modules (LIMs) communicate with subscriber-side DSL Customer Premise Equipment (CPE). With the current software version, a Stinger unit supports multiple line codes, including a 48-port SDSL LIM and a 12-port ADSL Discrete Multitone (DMT) LIM.

Manual LIM sparingManual LIM sparing provides a 1:1 sparing function for LIMs. The LIM used as the spare must have an Interface Redundancy Module (IRM) installed, as described in the Stinger Hardware Installation Guide. The LIM to be backed up (the primary LIM) must be of the same type as the spare.

When the sparing function is invoked, the primary LIM is deactivated. Its logical connections are terminated and then reestablished on the spare LIM. With manual LIM sparing, an administrator invokes the sparing function manually, by setting the Sparing-Mode parameter to manual, and disables it manually by setting the Sparing-Mode parameter to inactive. When the sparing function is disabled, the spare LIM is deactivated. Its logical connections are terminated and then reestablished on the primary LIM.

Automatic LIM sparing, in which the system detects a LIM failure and automatically sets up the virtual channels of that LIM on the spare, is not currently supported. However, the parameters related to automatic LIM sparing are present in the LIM-Sparing-Config subprofiles. The subprofiles are numbered from 1 to 16, representing LIM slot numbers. Setting the parameters in the numbered subprofiles currently has no effect.

Following are the LIM sparing parameters (shown with default values):

[in LIM-SPARING-CONFIG]sparing-mode = inactivespare-slot-number = any-slotmanually-spared-slot-number = any-slotlim-sparing-config = [ { yes 10 100 12 } { yes 10 100 12 } { yes 10 10+

Manual LIM sparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Allocating LIM bandwidth. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Configuring VPI/VCI ranges for LIM slots . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5

Configuring ATM SDSL interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

Configuring ATM ADSL-DMT interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Checking LIM status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-20


Configuring the Line Interface ModulesManual LIM sparing

[in LIM-SPARING-CONFIG:lim-sparing-config[1]]active = yeserror-averaging-period = 10error-threshold = 100

modem-failure-threshold = 12

For example, by using the following commands, the administrator deactivates the primary LIM in slot 2 and activates the spare LIM in slot-15:

admin> read lim-sparing-configLIM-SPARING-CONFIG read

admin> set sparing-mode = manual

admin> set spare-slot-number = slot-15

admin> set manually-spared-slot-number = slot-2

admin> writeLIM-SPARING-CONFIG written

The following commands deactivate the spare LIM and reactivates the primary LIM in slot 2:

admin> read lim-sparing-configLIM-SPARING-CONFIG read

Parameter Specifies

Sparing-Mode Current sparing mode. The manual setting gracefully deactivates the LIM specified in the Manually-Spared-Slot-Number parameter, terminating its connections and then reestablishing them on the spare LIM. The inactive setting disables the sparing function. If manual sparing is currently in use, setting the parameter to inactive causes the spare LIM to become inactive again, terminating its connections and then reestablishing them on the primary LIM that was manually spared. The automatic setting is not currently supported.

Spare-Slot-Number Slot number designated as the spare LIM. The specified slot must have an IRM installed.

Manually-Spared-Slot-Number

Slot number of the primary LIM to be manually deactivated and spared.

Active Not currently used. Enable/disable the LIM slot (from 1 to 16, as specified in the subprofile index) to participate in automatic LIM sparing. Only slots that have this parameter set to yes can be backed up by the spare.

Error-Averaging-Period Not currently used. Number of seconds during which the number of errors specified by Error-Threshold must be observed on the line before the modem is considered nonfunctional.

Error-Threshold Not currently used. Number of errors to occur during the specified Error-Averaging-Period before the modem is considered nonfunctional.

Modem-Failure-Threshold

Not currently used. Number of modems on the LIM that are considered nonfunctional before the LIM is considered nonfunctional.

Configuring the Line Interface ModulesAllocating LIM bandwidth


admin> set sparing-mode = inactive

admin> writeLIM-SPARING-CONFIG written

Allocating LIM bandwidthThe Stinger unit’s ATM switch capacity is 622 Mbits per second (Mbps) duplex, so it can handle a total of up to 622 Mbps traffic from LIMs and 622 Mbps traffic from TMs.

Figure 3-1. Maximum upstream real-time traffic in Mbits per second

The system supports 14 LIMs for transporting data traffic. In addition, the two CMs have management-traffic requirements. The total upstream guaranteed real-time traffic from all LIMs and CMs cannot exceed 622 Mbps. Within this limit, the individual LIMs can support varying amounts of bandwidth.

By default, the system allocates an equal amount of guaranteed bandwidth (44 Mbps) to each LIM. Administrators can change the default bandwidth allocation to allocate bandwidth in a flexible way, according to the requirements of each slot. However, you must keep in mind that the sum of guaranteed traffic from all front-panel slots cannot exceed 622 Mbps.

Overview of bandwidth settings

Following are the parameters for reallocating LIM bandwidth (shown with default settings):

[in ATM-CONFIG:config]config[1] = { 70000 44000 }config[2] = { 70000 44000 }config[3] = { 70000 44000 }config[4] = { 70000 44000 }config[5] = { 70000 44000 }config[6] = { 70000 44000 }config[7] = { 70000 44000 }

I N G R E S S

~44 Mbits each

LIMs

LIMs

CMs

1234567

89

10111213141516

1718

TMs ~155 Mbits per interface

Back panelFront panel

~622 Mbits

E G R E S S

~622 Mbits

(upstream)


Configuring the Line Interface ModulesAllocating LIM bandwidth

config[8] = { 1000 1000 }config[9] = { 1000 1000 }config[10] = { 70000 44000 }config[11] = { 70000 44000 }config[12] = { 70000 44000 }config[13] = { 70000 44000 }config[14] = { 70000 44000 }config[15] = { 70000 44000 }config[16] = { 70000 44000 }

[in ATM-CONFIG:config[1]]allow-max-up-stream-bandwidth = 70000

allow-guaranteed-up-stream-bandwidth = 44000

Guaranteed vs. maximum upstream bandwidth

The maximum possible upstream bandwidth for an ATM ADSL LIM is 155000, which would enable the LIM to handle 155 Mbps if other LIMs are not handling traffic. However, 155 Mbps throughput on a LIM is not guaranteed. If a LIM ships traffic up to that limit, the system makes a best-effort attempt to deliver it.

The slot should be able to send upstream traffic at up to the specified Allow-Guaranteed-Up-Stream-Bandwidth value even when the system is heavily loaded or the network is congested. The total of all guaranteed upstream bandwidth of all slots cannot exceed the maximum upstream capacity of the system (622 Mbps). Typically, slots with a high requirement for real-time traffic will need high guaranteed bandwidth.

Example of bandwidth allocation configuration

In this example of LIM bandwidth allocation, the administrator keeps the total upstream guaranteed traffic to 622 Mbps by allocating a larger guaranteed bandwidth to the LIMs in slots 4 and 5, and decreasing the guaranteed bandwidth for slots 11 through 14:

admin> read atm-configATM-CONFIG read

admin> set config 4 allow-max-up-stream-bandwidth 155520

admin> set config 4 allow-guaranteed-up-stream-bandwidth = 70000

admin> set config 5 allow-max-up-stream-bandwidth 155520




Parameter Specifies

Allow-Max-Up-Stream-Bandwidth

Maximum upstream bandwidth for the slot, expressed in Kbps. Valid values are from 0 to 155520 (155.52 Mbps, which is OC3 speed). The default value is 70 Mbps for each LIM and 1Mbps for each CM.

Allow-Guaranteed-Up-Stream-Bandwidth

Guaranteed upstream bandwidth for the slot, expressed in Kbps. The default value is 44 Mbps for each LIM, which distributes the sum of 622 Mbps across the 14 LIM slots.

Configuring the Line Interface ModulesConfiguring VPI/VCI ranges for LIM slots




admin> writeATM-CONFIG written

The LIMs in slots 4 and 5 each have a guaranteed upstream bandwidth of 70 Mbps rather than the default 44 Mbps. This is a combined increase of 52 Mbps bandwidth, for which a compensating decrease must be configured on some of the remaining LIMs. The LIMs in slots 11 through 14 each have a guaranteed upstream bandwidth of 31 Mbps. Each of the LIM’s bandwidth has been reduced by 13 Mbps, for a combined decrease of 52 Mbps.

Configuring VPI/VCI ranges for LIM slotsOn LIM slots, administrators can configure VPI/VCI ranges to enable the slot to accept inbound connections from particular types of DSL modems. While some DSL modems (such as DSL CellPipes) are routers, and have no restriction on the VPI/VCI range, other types of modem expect a particular VPI/VCI assignment. For example, Alcatel modems assume the VPI/VCI pair 8/35.

By default, out of a total of 11 bits available for VPI/VCI ranges on LIM slots, LIMs use 4 bits for the VPI and 7 for the VCI, as shown in Figure 3-2:

Figure 3-2. Default VPI/VCI range

The default setting for LIMs allows VPI numbers from 0 to 15 (4 bits) and VCI numbers from 32 to 127 (7 bits). This is the required setting for Alcatel modems, which assume a VPI of 8 and a VCI of 35.

Administrators can change the default VPI-VCI ranges on a per-LIM basis. Following are the relevant parameters, shown with their default settings:

[in ATM-CONFIG:slot-vpi-vci-range]slot-vpi-vci-range[1] = vpi-0-15-vci-32-127slot-vpi-vci-range[2] = vpi-0-15-vci-32-127slot-vpi-vci-range[3] = vpi-0-15-vci-32-127slot-vpi-vci-range[4] = vpi-0-15-vci-32-127slot-vpi-vci-range[5] = vpi-0-15-vci-32-127slot-vpi-vci-range[6] = vpi-0-15-vci-32-127slot-vpi-vci-range[7] = vpi-0-15-vci-32-127slot-vpi-vci-range[8] = ( bad value )slot-vpi-vci-range[9] = ( bad value )slot-vpi-vci-range[10] = vpi-0-15-vci-32-127slot-vpi-vci-range[11] = vpi-0-15-vci-32-127slot-vpi-vci-range[12] = vpi-0-15-vci-32-127slot-vpi-vci-range[13] = vpi-0-15-vci-32-127slot-vpi-vci-range[14] = vpi-0-15-vci-32-127

11 10 9 8 7 6 5 4 3 2 1 0

+----------------+----------------------------+

| VPI bits | VCI bits |

+----------------+----------------------------+


Configuring the Line Interface ModulesConfiguring ATM SDSL interfaces

slot-vpi-vci-range[15] = vpi-0-15-vci-32-127slot-vpi-vci-range[16] = vpi-0-15-vci-32-127

Note: To make the LIM configuration effective immediately, when you write the ATM-Config profile after changing a value, the system drops all connections on the relevant LIM, reconfigures the internals with the new range, and then reinstates all connections. While this has the advantage of not requiring a LIM reset, administrators should be very careful when changing this profile, to avoid connection delays.

Following are the corresponding VPI/VCI bit sizes for each setting:

For example, the following commands designate a 3-bit VPI number for a LIM in slot 1:

admin> read atm-configATM-CONFIG read

admin> set slot-vpi-vci-range 1 = vpi-0-7-vci-32-255

admin> writeATM-CONFIG written

Configuring ATM SDSL interfacesThe SDSL modules provide up to 48 interfaces per LIM, with each interface supporting up to 2.3 Mbps. A Stinger unit creates an SDSL profile for each SDSL interface in the system. For example, for a LIM installed in slot 1, the system creates profiles such as the following:

admin> dir sdsl 18 06/20/1999 23:18:51 { shelf-1 slot-1 1 } 1:1:1 18 06/20/1999 23:18:51 { shelf-1 slot-1 2 } 1:1:2 18 06/20/1999 23:18:51 { shelf-1 slot-1 3 } 1:1:3 18 06/20/1999 23:18:51 { shelf-1 slot-1 4 } 1:1:4 18 06/20/1999 23:18:51 { shelf-1 slot-1 5 } 1:1:5

Parameter Specifies

Slot-VPI-VCI-Range [N] Valid range of VPI and VCI numbers for each LIM slot in the system, where N is the slot number. All ports on a LIM use the same VPI/VCI range. Following are valid values: vpi-0-3-vci-32-511, vpi-0-7-vci-32-255, vpi-0-15-vci-32-127, vpi-0-31-vci-32-63.

Table 3-1. VPI/VCI bit sizes

VPI/VCI range values # of VPI bits # of VCI bits

vpi-0-3-vci-32-511 2 9

vpi-0-7-vci-32-255 3 8

vpi-0-15-vci-32-127 4 7

vpi-0-31-vci-32-63 5 6



18 06/20/1999 23:18:51 { shelf-1 slot-1 6 } 1:1:6 18 06/20/1999 23:18:51 { shelf-1 slot-1 7 } 1:1:7 18 06/20/1999 23:18:51 { shelf-1 slot-1 8 } 1:1:8 18 06/20/1999 23:18:51 { shelf-1 slot-1 9 } 1:1:9 19 06/20/1999 23:18:51 { shelf-1 slot-1 10 } 1:1:10 19 06/20/1999 23:18:51 { shelf-1 slot-1 11 } 1:1:11 19 06/20/1999 23:18:51 { shelf-1 slot-1 12 } 1:1:12 ...

Overview of SDSL settings

To configure SDSL ports, you must set relevant parameters in SDSL profiles. Following are the SDSL parameters, shown with default settings:

[in SDSL/{ any-shelf any-slot 0 }]name = ""physical-address* = { any-shelf any-slot 0 }enabled = no

[in SDSL/{ any-shelf any-slot 0 }:line-config]trunk-group = 0nailed-group = 1vp-switching-vpi = 15activation = staticcall-route-info = { any-shelf any-slot 0 }data-rate-mode = singlebaudmax-rate = 784000unit-type = coe

Parameter Specifies

Name Name of the interface. The default value is the interface address in shelf:slot:item format (for example, 1:2:3), but an administrator can assign a text string of up to 16 characters.

Physical-Address Physical address of the interface in the Stinger unit.

Enabled Enable/disable the SDSL interface. SDSL lines are disabled until an administrator activates the line in the SDSL profile.

Trunk-Group Not currently used. Use the default value (zero).

Nailed-Group Nailed-group number for the SDSL physical interface. A Connection or RADIUS profile specifies this number to make use of the interface, as described in Chapter 6, “Configuring ATM Circuits,” and Chapter 7, “Configuring Terminating ATM Connections.”

Each interface is assigned a unique default number, so you do not need to modify this parameter. If you assign a new value, it must be a number from 1 to 1024 that is unique within the system. For related information, see “Displaying SDSL port status and nailed groups” on page 3-8.

VP-Switching-VPI VPI to use for VP switching on the LIM port. The default is 15. All other VPIs are used for VC switching. For related information, see “Configuring VPI/VCI ranges for LIM slots” on page 3-5.

Activation Not currently used. Leave the default value (Static).



Displaying SDSL port status and nailed groups

To display the nailed-group numbers for SDSL ports, enter the SDSL command. For example, the command output that follows shows the nailed-group numbers for SDSL LIMs. In this example, the administrator includes the -a (all) flag, and the system has one SDSL LIM installed in slot 6:

admin> sdsl -a

All SDSL lines:(dvOp dvUpSt dvRq sAdm nailg)Line { 1 6 1 } (Down Idle UP UP 00251) Line { 1 6 2 } (Down Idle UP UP 00252) Line { 1 6 3 } (Down Idle UP UP 00253) Line { 1 6 4 } (Down Idle UP UP 00254) Line { 1 6 5 } (Down Idle UP UP 00255) Line { 1 6 6 } (Down Idle UP UP 00256) Line { 1 6 7 } (Down Idle UP UP 00257) Line { 1 6 8 } (Down Idle UP UP 00258) Line { 1 6 9 } (Down Idle UP UP 00259) Line { 1 6 10 } (Down Idle UP UP 00260) Line { 1 6 11 } (Down Idle UP UP 00261) Line { 1 6 12 } (Down Idle UP UP 00262) ...

Maximum data rates and session data rates

After the administrator configures a maximum data rate for an SDSL line, the unit initially establishes a CPE session on the line at that rate. If the Connection or RADIUS profile for the CPE session specifies a different rate, the unit terminates the session and then reestablishes it at the rate specified in the Connection or RADIUS profile. The next time the CPE initiates a connection, the Stinger unit does not retrain if the initial rate is the same as the rate used previously for that CPE.

VPI used for VP switching on SDSL port

By default, VPI 15 is reserved for VP switching on LIM ports. Administrators can reserve any VPI other than zero for VP switching, as long as the number is within the valid range of VPIs on the LIM slot, as described in “Configuring VPI/VCI ranges for LIM slots” on page 3-5.

Call-Route-Info Not currently used. Leave the default value (the zero address).

Data-Rate-Mode Per-session SDSL data-rate mode. Must be set to singlebaud, which causes the LIM to train to a single data rate, even if the modem can train at a higher or lower data rate.

Max-Rate Maximum data rate for the line, expressed in bits per second. The loop can be set to support up to 2.32 Mbps. The following maximum data rates are supported: 144000, 272000, 400000, 528000, 784000 (the default), 1168000, 1552000, 2320000.

Unit-Type Type of unit: COE or CPE. Remote equipment must have opposite setting.

Parameter Specifies

Configuring the Line Interface ModulesConfiguring ATM ADSL-DMT interfaces


When an ATM circuit is established between a LIM port and a trunk port, and uses the VPI reserved for VP switching, the Stinger unit switches the traffic on the basis of the VPI number alone. It does not examine or change the VCI number. For more information, see “Example of VP switching configuration” on page 6-11.

Example of SDSL interface configuration

In this example, an SDSL interface of a Stinger unit is configured to support a symmetric DSL connection to a DSL-CELL-50S CPE. For details about the Connection profile settings for the CPE, see “Configuring ATM Circuits” on page 6-1.

Figure 3-3. SDSL ATM LIM configuration

The following commands enable the SDSL interface and increase the maximum data rate to 1.5 Mbps:

admin> read sdsl { 1 11 22 }SDSL/{ shelf-1 slot-11 22 } read

admin> set enabled = yes

admin> set line-config max-rate = 1552000

admin> writeSDSL/{ shelf-1 slot-11 22 } written

The following commands reserve VPI 3 for VP switching on the interface:


admin> set line-config vp-switching-vpi = 3


Configuring ATM ADSL-DMT interfacesThe ADSL Discrete Multitone (AL-DMT) modules provide up to 12 interfaces per LIM. A Stinger unit creates an AL-DMT profile for each AL-DMT interface in the system. For example, for an AL-DMT LIM installed in slot 14, the system creates the following profiles:

admin> dir al-dmt 28 06/20/1999 00:27:37 { shelf-1 slot-14 1 } 1:14:1 28 06/20/1999 00:27:37 { shelf-1 slot-14 2 } 1:14:2

ATM

DSL-CELL-50S

SDSL LIM

(remote)



28 06/20/1999 00:27:37 { shelf-1 slot-14 3 } 1:14:3 28 06/20/1999 00:27:37 { shelf-1 slot-14 4 } 1:14:4 28 06/20/1999 00:27:37 { shelf-1 slot-14 5 } 1:14:5 28 06/20/1999 00:27:37 { shelf-1 slot-14 6 } 1:14:6 28 06/20/1999 00:27:37 { shelf-1 slot-14 7 } 1:14:7 28 06/20/1999 00:27:37 { shelf-1 slot-14 8 } 1:14:8 28 06/20/1999 00:27:37 { shelf-1 slot-14 9 } 1:14:9 29 06/20/1999 00:27:37 { shelf-1 slot-14 10 } 1:14:10 29 06/20/1999 00:27:37 { shelf-1 slot-14 11 } 1:14:11 29 06/20/1999 00:27:37 { shelf-1 slot-14 12 } 1:14:12

Note: The AL-DMT modules are based on Alcatel chipset technology. As such, any Alcatel-compliant CPE is fully interoperable with the AL-DMT interfaces. The DSL-CELL-50A CPE is such a device and is recommended for ADSL service deployment.

Overview of AL-DMT settings

Issue 2 of the T1.413 ANSI standard defines the fast and interleave data latencies for each direction (upstream and downstream) of ADSL transmission. In the Stinger AL-DMT profiles, administrators set parameters to specify the data rate, signal quality and power, and data delay of the interface. The Stinger unit references these parameters in the training process.

The following AL-DMT features are soon to be supported:

• Dual latency and mixed latency

• Dynamic Rate Adaptation

• Trellis encoding

• Automatic Gain Control

These features are not present in the current software version. However, the parameters related to these features are present in the AL-DMT profile, and setting them causes the port to retrain. However, the port will retrain to the same settings it used before the parameters were changed.

The following sets of parameters are active in the current software version:

• Line activation and DMT parameters

• Rate adaptive mode parameters

• Power spectral density (PSD) and power parameters

• Bit-rate parameters

• Interleaving delay parameters

• Noise margin parameters

• Dynamic rate adaptation parameters

Line activation and DMT parameters

With the current software version, all AL-DMT lines use full-rate DMT line coding. G.lite and auto-selection between the full-rate and G.lite will be supported soon.

Each direction of traffic (upstream and downstream) on an AL-DMT line can have a different minimum and maximum bit rate. Dual latency, which can use both the fast and interleaved channels in both directions, and mixed latency, which can use a different channel in each direction, are not currently supported.



Following are the parameters, shown with default values, for activating and setting up the AL-DMT line:

[in AL-DMT/{ any-shelf any-slot 0 }]name = ""physical-address* = { any-shelf any-slot 0 }enabled = no

[in AL-DMT/{ any-shelf any-slot 0 }:line-config]trunk-group = 0nailed-group = 1vp-switching-vpi = 15activation = staticcall-route-info = { any-shelf any-slot 0 }line-code = auto-selectline-latency-down = fastline-latency-up = fasttrellis-encoding = yes

Parameter Specifies


Physical-Address Physical address of the interface in the Stinger unit.

Enabled Enable/disable the AL-DMT interface. AL-DMT lines are disabled until the administrator activates the line in the AL-DMT profile.

Trunk-Group Does not apply. Leave the default value (zero).

Nailed-Group Nailed-group number for the AL-DMT physical interface. A Connection or RADIUS profile specifies this number to make use of the interface, as described in Chapter 6, “Configuring ATM Circuits,” and Chapter 7, “Configuring Terminating ATM Connections.”

Each interface is assigned a unique default number, so you do not need to modify this parameter. If you assign a new value, it must be a number from 1 to 1024 that is unique within the system.

VP-Switching-VPI VPI to use for VP switching on the LIM port. The default is 15. All other VPIs are used for VC switching. For related information, see “Configuring VPI/VCI ranges for LIM slots” on page 3-5.

Activation Does not apply. Leave the default value (Static).


Line-Code The DMT line code to be used for training. Currently, the full-dmt setting is always used, regardless of the setting of this parameter. The g-lite setting, and auto-select (which will cause the modem to determine which line code is in use at the other end and to use that code) are not yet supported.



Displaying AL-DMT port status and nailed groups

To display the nailed-group numbers for AL-DMT lines, use the DMTAL command. For example, the following command output shows the nailed-group numbers for an AL-DMT module in slot 4:

admin> dmtal -a

All DMT Alcatel ADSL lines:(dvOp dvUpSt dvRq sAdm nailg)Line { 1 4 1 } (Up Idle UP UP 00151) Line { 1 4 2 } (Up Idle UP UP 00152) Line { 1 4 3 } (Up Idle UP UP 00153) Line { 1 4 4 } (Up Idle UP UP 00154) Line { 1 4 5 } (Up Idle UP UP 00155) Line { 1 4 6 } (Up Idle UP UP 00156) Line { 1 4 7 } (Up Idle UP UP 00157) Line { 1 4 8 } (Up Idle UP UP 00158) Line { 1 4 9 } (Up Idle UP UP 00159) Line { 1 4 10 } (Up Idle UP UP 00160) Line { 1 4 11 } (Up Idle UP UP 00161) Line { 1 4 12 } (Up Idle UP UP 00162)

VPI used for VP switching on the AL-DMT port

By default, VPI 15 is reserved for VP switching on LIM ports. Administrators can reserve any VPI other than zero for VP switching, as long as the number is within the valid range of VPIs on the LIM slot, as described in “Configuring VPI/VCI ranges for LIM slots” on page 3-5.

When an ATM circuit is established between a LIM port and a trunk port, and uses the VPI reserved for VP switching, the Stinger unit switches the traffic on the basis of the VPI number alone. It does not examine or change the VCI number. For more information, see “Example of VP switching configuration” on page 6-11.

Rate-adaptive mode parameters

Administrators can specify rate-adaptive operations for each direction (upstream and downstream). Dynamic rate adaptation is not currently supported, so administrators choose between automatic-at-startup (the default) and operator-controlled.

Line-Latency-Down Latency path (fast or interleave) to be used for downstream data transport. For related settings, see “Fast and interleaved bit-rate parameters” on page 3-14.

Line-Latency-Up Latency path (fast or interleave) to be used for upstream data transport. For related settings, see “Fast and interleaved bit-rate parameters” on page 3-14.

Trellis-Encoding Not currently used. Enable/disable trellis encoding, which is not currently implemented. Trellis encoding is specified in the DMT standard. Disabling it can increase performance, at the cost of becoming noncompliant with the standard.

Parameter Specifies



Automatic-at-startup rate adaptation means that the rate is selected during the training (startup) process. The line initializes at a minimum specified bit rate and target noise margin. If the line fails to achieve the minimum bit rate in either direction, it cannot initialize, and it sends a message that the requested bit rate was too high. If the line can support a bit rate that is higher than the minimum and not higher than the maximum bit rate, it can train up to a higher rate within the acceptable noise margin. Each direction can have a different minimum and maximum bit rate using the fast or interleaved ADSL channel. (Dual latency, which can utilize both the fast and interleaved channels in both directions, and mixed latency, which can utilize a different channel in each direction, are not currently supported.)

Operator-controlled rate adaptation means that the line must initialize at and maintain a specific planned bit rate with an acceptable target noise margin. If the line fails to achieve the planned bit rate in either direction, it fails to initialize, and reports that the requested bit rate was too high. The line does not use a higher bit rate, even if it can support one.

For details about specifying bit rates, see “Fast and interleaved bit-rate parameters” on page 3-14. For information about defining acceptable noise margins, see “Noise margin parameters” on page 3-16.

The following parameters, shown with default values, define how rate adaptation will operate on the line:

[in AL-DMT/{ any-shelf any-slot 0 }:line-config]rate-adapt-mode-up = automatic-at-startuprate-adapt-mode-down = automatic-at-startuprate-adapt-ratio-up = 100rate-adapt-ratio-down = 100

Power Spectral Density (PSD) and power-level parameters

PSD is the power of bandwidth divided by the bandwidth. In the AL-DMT profile, it represents the PSD allowed on the line at the transmitter output, expressed in dBm/Hz. It is defined for the downstream direction only, with a valid range from -34 to -52 in even-number increments. If you lower the value from its default value of -40, the line consumes less power but also has a lower capacity. Increasing the value can boost the PSD to achieve a higher capacity.

Parameter Specifies

Rate-Adapt-Mode-Up Rate-adaptive mode for upstream training. The default is automatic-at-startup. If set to operator-controlled, the line trains upstream using a constant planned bit rate. The dynamic setting is not currently used.

Rate-Adapt-Mode-Down Rate-adaptive mode for downstream training. The default is automatic-at-startup. If set to operator-controlled, the line trains downstream using a constant planned bit rate. The dynamic setting is not currently used.

Rate-Adapt-Ratio-Up Not currently used. Ratio for distributing excess upstream bit rate among the fast and interleaved channels when dual latency is supported.

Rate-Adapt-Ratio-Down Not currently used. Ratio for distributing excess downstream bit rate among the fast and interleaved channels when dual latency is supported.



Maximum aggregate power level is the maximum output power allowed on the line at the transmitter output, expressed in dBm. It is defined for both directions. If you lower the default value, the line consumes less power and has less capacity. The default value is the maximum allowed setting.

Following are the AL-DMT parameters, shown with default values, for configuring power settings:

[in AL-DMT/{ any-shelf any-slot 0 }:line-config]max-aggr-power-level-up = 13max-aggr-power-level-down = 20max-power-spectral-density = 40gain-default = 16-db

Fast and interleaved bit-rate parameters

Bit-rate parameters define minimum, maximum, and planned upstream and downstream bit rates for a rate-adaptive connection. Bit rates depend on the physical interface (the line to which the COE and CPE are connected) and the ADSL interleaved or fast channel.

The Line-Latency-Up and Line-Latency-Down settings determine which channel will be used in each direction. For more information, see “Line activation and DMT parameters” on page 3-10.

In the following sample listings of the latency parameters, the settings indicate use of the fast channel for both upstream and downstream traffic. This is the default. Note that in the current software version, both upstream and downstream traffic must use the same channel.

[in AL-DMT/{ any-shelf any-slot 0 }:fast-path-config]min-bitrate-up = 128min-bitrate-down = 128max-bitrate-up = 1000max-bitrate-down = 8000planned-bitrate-up = 512planned-bitrate-down = 1000

[in AL-DMT/{ any-shelf any-slot 0 }:interleave-path-config]min-bitrate-up = 128min-bitrate-down = 128max-bitrate-up = 1000

Parameter Specifies

Max-Aggr-Power-Level-Up

Maximum aggregate power level on the upstream channel. Valid range is from 0 to 13 dBm.

Max-Aggr-Power-Level-Down

Maximum aggregate power level on the downstream channel. Its valid range is from 0 to 20 dBm.

Max-Power-Spectral-Density

Maximum PSD in both directions. Its valid range is from 34 to 52 in even-number increments. If you specify an odd number, the system uses the even-number setting below that number. The actual value used is the negative value of the number that is specified.

Gain-Default Not currently used. The default gain value in dB (16 or 20 dB) for Automatic Gain Control (AGC).



max-bitrate-down = 8000planned-bitrate-up = 512planned-bitrate-down = 1000

Interleaving delay parameters

Data interleaving increases the noise resilience of the system. However, it also increases the latency (delay) of the data traffic. When using the interleave channel, determine the maximum amount of latency by considering the type of traffic sent on the line. The more tolerant of delay the traffic is, the higher these settings can be.

Following are the AL-DMT parameters, shown with default values, for specifying the maximum tolerable delay for interleaver/deinterleaver operations:

[in AL-DMT/{ any-shelf any-slot 0 }:interleave-path-config]max-delay-up = 16

max-delay-down = 16

Parameter Specifies

Min-Bitrate-Up Minimum bit rate for upstream traffic, from 0 to 2,000 Kbps. When the automatic rate-adaptive mode is in use, the line initializes at this upstream rate or fails to initialize. Does not apply for operator-controlled rate adaptation.

Min-Bitrate-Down Minimum bit rate for downstream traffic, from 0 to 15,000 Kbps. When the automatic rate-adaptive mode is in use, the line initializes at this downstream rate or fails to initialize.Does not apply for operator-controlled rate adaptation.

Max-Bitrate-Up Maximum bit rate for upstream traffic, from 0 to 2,000 Kbps.Does not apply for operator-controlled rate adaptation.

Max-Bitrate-Down Maximum bit rate for downstream traffic, from 0 to 15,000 Kbps. Does not apply for operator-controlled rate adaptation.

Planned-Bitrate-Up Constant bit rate for upstream traffic when operator-controlled rate-adaptive mode is in use. Valid values are from 0 to 2,000 Kbps. Does not apply when automatic-at-startup rate adaptation is in use on the line.

Planned-Bitrate-Down Constant bit rate for downstream traffic when operator-controlled rate-adaptive mode is in use. Valid values are from 0 to 15,000 Kbps. Does not apply when automatic-at-startup rate adaptation is in use on the line.

Parameter Specifies

Max-Delay-Up Maximum allowed upstream delay induced by interleaving data, expressed in milliseconds. The valid range is 0 to 255, but only the default value of 16 is currently accepted.

Max-Delay-Down Maximum allowed downstream delay induced by interleaving data, expressed in milliseconds. The valid range is 0 to 255, but only the default value of 16 is currently accepted.



Note: In the current software version, the delay parameters must specify the default 16 millisecond value.

Noise margin parameters

The Bit Error Rate (BER) is the ratio between erroneous bits and transmitted bits. Noise margins can be controlled to ensure that the line provides a BER of 10-7or better, as required by ANSI standards.

Noise margins are defined in decibels (dB). A BER of 10-7represents 0 dB. The line tolerates a certain noise level with respect to its received signal.If the maximum noise level is exceeded, the ADSL Transceiver Unit (ATU) attempts to reduce the far-end output power. If the noise drops below a minimum margin, the ATU attempts to increase the far-end power output until the noise level is at or above the configured minimum.

Although the noise-margin settings can be from 1 to 31 dB, the modem software limits the maximum noise margin to 15 dB. If you specify a setting greater than 15, the modem software uses 15 dB.

Figure 3-4. How noise margin parameters relate to power adjustments

Following are the AL-DMT parameters, shown with default values, for configuring the noise margins on the AL-DMT line:

[in AL-DMT/{ any-shelf any-slot 0 }:margin-config]target-noise-margin-up = 6target-noise-margin-down = 6min-noise-margin-up = 6min-noise-margin-down = 6max-add-noise-margin-up = 31max-add-noise-margin-down = 31

Parameter Specifies

Target-Noise-Margin-Up Upstream noise margin, relative to 0 dB, that must be present before the line can initialize successfully and rate adapt during normal operations. The valid range is 1 to 31 dB, with a practical limitation of 15 dB set by the modem software.

Target-Noise-Margin-Down

Downstream noise margin, relative to 0 dB, that must be present before the line can initialize successfully and rate adapt during normal operations. The valid range is 1 to 31 dB, with a practical limitation of 15 dB set by the modem software.

Reduce output power

Increase output power

Steady-state operations

Target noise margin

Minimum noise margin

0 dB margin

Maximum additional noise margin



Dynamic rate-adaptive noise margin parameters

Dynamic rate adaptation will be supported soon, but it is not in the current software version. Therefore, if you set any of the parameters described in this section, the modem retrains with its previous behavior. When dynamic rate adaptation is in use, the line adjusts its bit rate dynamically (it upshifts to increase its bit rate, or downshifts to reduce it) on the basis of specified noise margins and intervals for which a noise level is maintained, provided that the maximum or minimum bit rate has not been reached.

Figure 3-5. Future support: How noise margins related to dynamic rate adaptation

When dynamic rate adaptation is supported, the following parameters will configure it:

[in AL-DMT/{ any-shelf any-slot 0 }:margin-config]ra-downshift-margin-up = 0ra-downshift-int-up = 0ra-downshift-margin-down = 0ra-downshift-int-down = 0ra-upshift-margin-up = 0ra-upshift-int-up = 0

Min-Noise-Margin-Up Minimum upstream noise margin the line will tolerate relative to 0 dB before attempting to increase power output. The valid range is 1 to 31 dB, with a practical limitation of 15 dB set by the modem software.

Min-Noise-Margin-Down Minimum downstream noise margin the line will tolerate relative to 0 dB before attempting to increase power output. The valid range is 1 to 31 dB, with a practical limitation of 15 dB set by the modem software.

Max-Add-Noise-Margin-Up

Maximum upstream noise margin beyond the Target-Noise-Margin-Up setting the line will tolerate relative to 0 dB before attempting to reduce power output. The valid range is 1 to 31 dB, with a practical limitation of 15 dB set by the modem software.

Max-Add-Noise-Margin-Down

Maximum downstream noise margin beyond the Target-Noise-Margin-Up setting the line will tolerate relative to 0 dB before attempting to reduce power output. The valid range is 1 to 31 dB, with a practical limitation of 15 dB set by the modem software.

Parameter Specifies

Reduce output power

Increase output power

Steady-state operationsTarget noise margin

Minimum noise margin

0 dB margin

Maximum additional noise margin

Upshift noise margin

Downshift noise marginSteady-state operations

Increase bit rate (upshift)

Reduce bit rate (downshift)



ra-upshift-margin-down = 0ra-upshift-int-down = 0

Examples of AL-DMT interface configuration

In Figure 3-6, an AL-DMT interface in a Stinger unit is configured to support a rate-adaptive connection to a DSL-CELL-50A CPE. (For details about the Connection profile settings for the CPE connection, see Chapter 6, “Configuring ATM Circuits.”)

Parameter Specifies

Ra-Downshift-Margin-Up

Not currently used. Upstream noise margin relative to 0 dB. If the noise level remains at this level for more than the specified time interval, the line reduces its upstream bit rate.The valid range is 1 to 31 dB.

Ra-Downshift-Int-Up Not currently used. Number of seconds (1 to 255) the downshift noise margin may be maintained before the line reduces its upstream bit rate.

Ra-Downshift-Margin-Down

Not currently used. Downstream noise margin relative to 0 dB. If the noise level remains at this level for more than the specified time interval, the line reduces its downstream bit rate. The valid range is 1 to 31 dB.

Ra-Downshift-Int-Down Not currently used. Number of seconds (1 to 255) the downshift noise margin may be maintained before the line reduces its downstream bit rate.

Ra-Upshift-Margin-Up Not currently used. Upstream noise margin relative to 0 dB. If the noise level remains at this level for more than the specified time interval, the line increases its upstream bit rate.The valid range is 1 to 31 dB.

Ra-Upshift-Int-Up Not currently used. Number of seconds (1 to 255) the upshift noise margin may be maintained before the line increases its upstream bit rate.

Ra-Upshift-Margin-Down

Not currently used. Downstream noise margin relative to 0 dB. If the noise level remains at this level for more than the specified time interval, the line increases its downstream bit rate. The valid range is 1 to 31 dB.

Ra-Upshift-Int-Down Not currently used. Number of seconds (1 to 255) the upshift noise margin may be maintained before the line increases its downstream bit rate.



Figure 3-6. ADSL ATM LIM configuration

The following commands configure the interface to use a constant, planned (operator-controlled) bit rate of 56 Kbps upstream and 1.5 Mbps downstream, using the fast channel in both directions:

admin> read al-dmt { 1 3 4 }AL-DMT/{ shelf-1 slot-3 4 } read


admin> set line-config line-latency-up = fast

admin> set line-config line-latency-down = fast

admin> set line-config rate-adapt-mode-up = operator-controlled

admin> set line-config rate-adapt-mode-down = operator-controlled

admin> set fast-path-config planned-bitrate-up = 56

admin> set interleave-path-config planned-bitrate-down = 1500

admin> writeAL-DMT/{ shelf-1 slot-3 4 } read

The following commands configure the interface to automatically select the best possible rate at startup time. They specify a possible upstream bit rate range from 56 Kbps to 256 Kbps, and a possible downstream bit-rate range from 512 Kbps to 1.5 Mbps. They also specify use of the interleaved channel in both directions.



admin> set line-config rate-adapt-mode-up = automatic-at-startup

admin> set line-config rate-adapt-mode-down = automatic-at-startup

admin> set line-config line-latency-up = interleave

admin> set line-config line-latency-down = interleave

admin> set interleave-path-config min-bitrate-up = 56

admin> set interleave-path-config max-bitrate-up = 256

admin> set interleave-path-config min-bitrate-down = 512

DSL-CELL-50AEthernet

DSL

POTS

POTSSplitter

ATM

Copper pair

POTS Splitter Shelf

PBX


Configuring the Line Interface ModulesChecking LIM status

admin> set interleave-path-config max-bitrate-up = 1500


The following commands reserve VPI 7 for VP switching on the interface:


admin> set line-config vp-switching-vpi = 7


Checking LIM statusThe Stinger unit creates status profiles for each SDSL interface and AL-DMT interface in the system. The profiles provide information about the physical interfaces and their operational status. The Stinger unit also creates LIM-sparing and Bandwidth status profiles that reflect sparing and bandwidth status of all the LIMs.

Checking the status of an SDSL interface

The Stinger unit creates an SDSL-Stat profile for each SDSL interface in the system. Following are the SDSL-Stat parameters, shown with sample settings for an active line:

[in SDSL-STAT/{ shelf-1 slot-11 22 }]physical-address* = { shelf-1 slot-11 22 }line-state = activeerror-count = 0physical-status = { 0 coe port-up 784000 784000 13 2 2 }physical-statistic = { { 1 1 1 } yes 15 0 passed 4 normal-operation 5+}

The Line-State setting in this example specifies that the line is active (it has been enabled). Error-Count indicates the number of errors experienced since the last reset.

Checking the status of the physical interface

The Physical-Status subprofile provides information about the physical interface. For example:

[in SDSL-STAT/{ shelf-1 slot-11 22 }:physical-status]if-group-index = 0unit-type = coedev-line-state = port-upup-stream-rate = 784000down-stream-rate = 784000major-firmware-ver = 13minor-firmware-ver = 2hardware-ver = 2

Parameter Indicates

IF-Group-Index SNMP interface group index of the line



The Dev-Line-State parameter shows one of the following possible states:

Obtaining statistics about operations

The Physical-Statistic subprofile enables administrators to check interface operations. For example:

[in SDSL-STAT/{ shelf-1 slot-11 22 }:physical-statistic]

line-up-timer = { 1 1 1 }

rx-signal-present = yes

Unit-Type Operating mode specified by the Unit-Type setting in the SDSL profile

Dev-Line-State Current state of the interface (described below)

Up-Stream-Rate Upstream data rate

Down-Stream-Rate Downstream data rate

Major-Firmware-Ver Major version number of the SDSL modem firmware

Minor-Firmware-Ver Minor version number of the SDSL modem firmware

Hardware-Ver Hardware version of the SDSL modem

Dev-Line-State value Meaning

config The interface is being configured.

deactivate Transitioning to the Down state.

inactive Starting up.

activating Waiting for remote to start up.

active-rx Waiting for four-level transmission from remote.

port-up Connected to CPE and data can be transferred.

portup-pending-deactive

Loss of Signal or noise-margin error (noise greater than -5dB).

deactivate-lost Waiting for Loss of Signal Timer to expire.

hardware-test Hardware self-test in progress.

out-of-service Interface out of service.

tip-ring-detect Running a simple internal Bit Error Rate Test (BERT) to detect correct tip-ring orientation.

tip-wait1 Running internal BERT to detect correct tip-ring orientation.

tip-hunt Running internal BERT to detect correct tip-ring orientation.

tip-wait2 Running internal BERT to detect correct tip-ring orientation.

cell-delineation Attempting to recover ATM cells (idle cells as well as data cells) from the receiving octets. If recovery is successful, the interface transitions to the Up state.

deactivate-wait Waiting to transition to the Down state.

Parameter Indicates



line-quality = 15up-dwn-cntr = 0self-test = passedfar-end-db-attenuation = 4firmware-startup-stage = normal-operationhdlc-rx-crc-error-cnt = 5bert-timer = 2 minutesbert-enable = nobert-operation-state = stoppedbert-error-counter = 0

Administrators can run a BERT to check the data integrity of the interface or connection. While a BERT is running, normal data transmission is interrupted on the line.

To run a BERT, set BERT-Enable to Yes. The test counts bit errors continuously for the interval specified by BERT-Timer. If both the CPE and COE are connected and have BERT enabled, the test runs between the two systems. If the two ends are not connected, the test runs within the SDSL interface in the Stinger unit.

When BERT is enabled and the BERT timer has not expired, BERT-Operation-State reports one of the following states:

Parameter Indicates

Line-Up-Timer How long the line has been up (days, hours, and minutes in {dd hh mm} format.

RX-Signal-Present Receiving signal from the remote (Yes or No).

Line-Quality Line quality in decibels. A value of -5dB or better is required for reliable data transfer.

Up-Down-Cntr Number of times the link has transitioned from an Up state to a Down state since the module was last reset.

Self-Test Outcome of modem chipset self-test.

Far-End-Db-Attenuation Attenuation level of the signal received from remote.

Firmware-Startup-Stage Current firmware state.

HDLC-RX-CRC-Error-Cnt

Number of CRC errors. A few CRC errors are normal. The line disconnects if 1500 errors occur within a two-second period.

BERT-Timer Bit Error Rate Test (BERT) timer.

BERT-Enable Enable/disable BERT. (Note that a BERT disrupts data transmission.)

BERT-Operation-State State of the test, described below.

BERT-Error-Counter Number of bit errors counted by BERT.

BERT-Operation-State value

Meaning

waiting-for-511-sync

Waiting for remote before starting the BERT.



Checking the status of an AL-DMT interface

The system creates an AL-DMT-STAT profile for each AL-DMT interface. The profiles provide statistics and connection status. Following are the relevant parameters, shown with sample settings for an active line:

[in AL-DMT-STAT/{ shelf-1 slot-3 4 }]physical-address* = { shelf-1 slot-3 4 }line-state = activephysical-status = { 0 coe port-up 128 2944 fast fast 1.4.1 2 0 1 init-+physical-statistic = { { 1 1 1 } yes 3 passed 3 6 56 19 5 41 11 0 0 0 +}

The Line-State setting specifies that the line is active (it has been enabled).

Checking the status of the physical interface

The Physical-Status subprofile provides information about the physical interface. The interface uses its unused bandwidth to run a continuous Bit Error Rate Test (BERT), so bit-error counts are always available without explicitly running a BERT and disrupting data transmission. Integrated BERT test results are displayed in the Accum-Bit-Err, Num-Sec-Valid, and Num-Sec-Invalid parameters.

Following are sample Physical-Status settings for an active interface:

[in AL-DMT-STAT/{ shelf-1 slot-3 4 }:physical-status]if-group-index = 0unit-type = coedev-line-state = port-upup-stream-rate = 128000down-stream-rate = 2944000up-stream-latency = fastdown-stream-latency = fastfirmware-ver = 1.4.1ansi-adsl-ver = 2initial-adsl-ver = 0hardware-ver = 1modem-hw-state = init-okaccum-bit-err = 0

local-loop-active The interface is in local analog loopback and is running the test. No remote device is involved.

active BERT is running with remote.

stopped BERT was disabled.

loop-back-setup The interface is being placed into analog loopback.

start-up BERT is starting up.

BERT-Operation-State value

Meaning



num-sec-valid = 91

num-sec-invalid = 0

Parameter Indicates

IF-Group-Index SNMP interface group index of the line.

Unit-Type Operating mode (should always be COE).

Dev-Line-State The current state of the interface. Valid values are as follows:

down—Either there is no connection or the interface is disabled.

activation—Interface is trying to train but not detecting a modem on the other end.

training—Training with a modem on the other end.

port-up—Interface is successfully trained up.

failed—Interface failed training (usually a log message gives the reason).

loopback—Interface is in special loopback test mode.

Up-Stream-Rate Upstream data rate in bps. Zero means the data rate is unknown.

Down-Stream-Rate Downstream data rate in bps. Zero means the data rate is unknown.

Up-Stream-Latency Operational upstream latency (none, fast, or interleave). The none setting indicates that the line is not operational.

Down-Stream-Latency Operational downstream latency (none, fast, or interleave). The none setting indicates that the line is not operational.

Firmware-Ver Version number of the ADSL modem firmware.

ANSI-ADSL-Ver Supported issue of the ANSI T1.413 standard (Issue 2).

Initial-ADSL-Ver Number of changes made to the Alcatel Proprietary Exchange phase in this version of software. Both ends of the connection must agree on this proprietary Alcatel parameter for the chip sets to take advantage of advanced functionality that is not supported by non-Alcatel equipment. Zero is the current value.

Hardware-Ver Hardware version of the ADSL modem.

Modem-Hw-State State of the interface after initialization. Valid values are init-ok (all is well), bad-sdram, bad-cache, or bad-cache-sdram. The last three values imply memory problems, probably associated with a self-test failure.

Accum-Bit-Err Number of actual bit errors detected during the continuous BERT.

Num-Sec-Valid How many seconds were error free during the continuous BERT.

Num-Sec-Invalid How many error seconds were detected during the continuous BERT.



Obtaining statistics about operations

The Physical-Statistic subprofile enables administrators to check interface operations. Following are sample Physical-Statistics settings for an active interface:

[in AL-DMT-STAT/{ shelf-1 slot-3 4 }:physical-statistic]line-up-timer = { 0 0 1 }rx-signal-present = yesup-dwn-cntr = 3self-test = passednoise-margin-down = 6attenuation-down = 56output-power-down = 19noise-margin-up = 5attenuation-up = 41output-power-up = 11near-end-fec = 0near-end-crc = 0near-end-hec = 0far-end-fec = 10far-end-crc = 0

far-end-hec = 0

Parameter Indicates

Line-Up-Timer How long the interface has been up (days, hours, and minutes in {dd hh mm} format.

RX-Signal-Present Receiving (yes) or not receiving (no) signal from the CPE.

Up-Down-Cntr Number of times the link has transitioned from an Up state to a Down state since the module was last reset.

Self-Test Whether the port has passed the modem chipset self-test.

Noise-Margin-Down Current downstream noise margin in dB.

Attenuation-Down Current downstream attenuation in dB.

Output-Power-Down Current downstream aggregate power level in dBm.

Noise-Margin-Up Current upstream noise margin in dB.

Attenuation-Up Current upstream attenuation in dB.

Output-Power-Up Current upstream aggregate power level in dBm.

Near-End-FEC Forward Error Correction (FEC) errors detected by the COE ADSL Transceiver Unit (ATU).

Near-End-CRC Cyclic Redundancy Check (CRC) errors detected by the COE ATU.

Near-End-HEC Header Error Checksum (HEC) errors detected by the COE ATU.

Far-End-FEC Forward Error Correction (FEC) errors detected by the CPE ATU.

Far-End-CRC Cyclic Redundancy Check (CRC) errors detected by the CPE ATU.

Far-End-HEC Header Error Checksum (HEC) errors detected by the CPE ATU.



Checking the status of manual LIM sparing

The LIM-Sparing-Status profile provides information about whether LIM sparing is enabled and which of the LIMs are participating. Automatic LIM sparing is not currently supported. Following are the relevant parameters (shown with sample values for an active line):

[in LIM-SPARING-STATUS]sparing-mode = manualspare-slot-number = slot-15spared-slot-number = slot-2lim-sparing-status = [ { yes yes sparing-none } { yes yes primary-inac+

[in LIM-SPARING-STATUS:lim-sparing-status[1]]active = yeslim-status-ok = yessparing-state = sparing-none

Checking bandwidth status

The system creates a Bandwidth-Stats profile that provides information about bandwidth allocation. Following are the relevant parameters (shown with default values):

[in BANDWIDTH-STATS]max-upstream-bandwidth = 622160active-upstream-bandwidth-on-trunks = 155520

standby-upstream-bandwidth-on-trunks = 466620

Parameter Indicates

Sparing-Mode Whether LIM sparing has been enabled, and if so, whether manual or automatic sparing is in use. Currently, only manual LIM sparing is supported. Valid values are inactive and manual.

Spare-Slot-Number Slot number designated as the spare LIM in the LIM-Sparing-Config profile.

Spared-Slot-Number Slot number of the primary LIM to be backed up, as configured in the LIM-Sparing-Config profile.

Active Not currently used. Whether the LIM slot (from 1 to 16) can be automatically backed up by the spare.

LIM-Status-OK Not currently used. Whether the LIM slot (from 1 to 16) is functioning properly or not.

Sparing-State Not currently used. The state of the sparing function. A value of sparing-none indicates that sparing is not enabled. If sparing is enabled and the LIM slot is a primary LIM, the value can be primary-active or primary-inactive. If sparing is enabled and the LIM slot is the secondary (spare) LIM, the value can be secondary-active or secondary-inactive.

Parameter Indicates

Max-Upstream-Bandwidth

Maximum upstream bandwidth of all configured LIMs.



Active-Upstream-Bandwidth-On-Trunks

Active trunk-side bandwidth.

Standby-Upstream-Bandwidth-On-Trunks

Not currently used. Total bandwidth of standby trunks. A standby trunk becomes active and takes over traffic handling only when an active trunk becomes unavailable.

Parameter Indicates


4Configuring the Trunk Modules

Administrators can choose to run the full trunk-side bandwidth or to set up a redundant configuration.

The Stinger unit can obtain its system clock by source the ATM network clock on one of the trunk ports. One or more of the ports can be designated as eligible clock sources, and assigned a priority for use as the clock source

The Stinger unit can switch a total of 32K concurrent Virtual Channel Connections (VCCs). By default, the system distributes this maximum equally across the four trunk ports by enabling each port to handle 8K VCCs. Administrators can change the default number to direct VCCs to a particular port or to reserve some of a port’s bandwidth for Virtual Path connections (VPCs).

Trunk port sparingTrunk port sparing provides a 1:1 sparing function for trunk ports. The trunk port to be backed up (the primary trunk port) does not have to be of the same type as the spare trunk port. Both automatic and manual trunk port sparing are supported.

When the sparing function is invoked, the primary trunk port is deactivated. Its logical connections are terminated and then reestablished on the spare trunk port. With manual trunk port sparing, an administrator invokes the sparing function manually, by setting the Sparing-Mode parameter to manual, and disables it manually by setting the Sparing-Mode parameter to inactive. When the sparing function is disabled, the spare trunk port is deactivated. Its logical connections are terminated and then reestablished on the primary trunk port.

Automatic trunk port sparing is invoked when the system detects that a primary port has become inactive. At that point, the spare port becomes active, and the primary port’s logical connections are brought up on the spare. The connections are maintained on the spare until the

Trunk port sparing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Using trunk ports as clock source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3

VPI/VCI allocation for trunk ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5

Configuring DS3-ATM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7

Configuring OC3-ATM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11

Checking ATM trunk interface status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-15


Configuring the Trunk ModulesTrunk port sparing

spare becomes inactive, at which point the system reestablishes the logical connections on the primary port.

Trunk port sparing settings

Following are the trunk port sparing parameters, shown with default settings:

[in DS3-ATM/{ any-shelf any-slot 0 }]name = ""spare-physical-address = { any-shelf any-slot 0 }sparing-mode = inactive

[in OC3-ATM/{ any-shelf any-slot 0 }]name = ""spare-physical-address = { any-shelf any-slot 0 }sparing-mode = inactive

Example of automatic sparing configuration

To use automatic trunk port sparing, you modify the profile of a primary trunk port to specify a spare trunk port and enable automatic sparing. For example, the following commands specify that the first port in slot 17 is a primary trunk port, and the first trunk port in slot 18 is its spare:

admin> read oc3-atm {1 trunk-module-1 1}OC3-ATM/{ shelf-1 trunk-module-1 1 } read

admin> set spare-physical-address shelf = 1

admin> set spare-physical-address slot = 18

admin> set spare-physical-address item-number = 1

admin> set sparing-mode = automatic

admin> writeOC3-ATM/{ shelf-1 trunk-module-1 1 } written

Note that the Spare-Physical-Address is a complex field. You can set its value by specifying the parameter name and the relevant subfield on the Set command line, as shown immediately above, or by listing the complex field and then setting its values directly. For example:


Parameter Specifies

Spare-Physical-Address Physical address of the trunk port to be used as a spare for this port. The value is a complex field that specifies the shelf-number, slot-number, and item (port) number of the spare port.

Sparing-Mode Sparing mode for the port. If set to inactive (the default), the sparing function is disabled. The automatic setting means the active port changes from primary to the spare port and back, based on the line status of the active port. Setting this parameter to manual inactivates the primary trunk port and activates the spare trunk port. Setting it back to inactive brings down the spare and reactivates the primary port.

Configuring the Trunk ModulesUsing trunk ports as clock source


admin> list spare-physical-address[in OC3-ATM/{ shelf-1 trunk-module-2 1 }:spare-physical-address]shelf = any-shelfslot = any-slotitem-number = 0

admin> set shelf = 1

admin> set slot = 18

admin> set item-number = 1

admin> list ..



Example of manual sparing configuration

To use manual trunk port sparing, you modify the profile of a primary trunk port to specify a spare trunk port and enable manual sparing. For example, the following commands specify that the first port in slot 17 is a primary trunk port, designate the first trunk port in slot 18 as its spare, and invoke the sparing function manually:





admin> set sparing-mode = manual


To deactivate the spare trunk port and activate the primary port again, set the Sparing-Mode to inactive. For example:


admin> set sparing-mode = inactive


Using trunk ports as clock sourceIf you configure trunk ports as eligible clock sources for the Stinger unit, the selected port sources the ATM network clock and feeds it to the primary CM as the master clock.


Configuring the Trunk ModulesUsing trunk ports as clock source

Informing the system of its clock source

The Stinger unit has an internal 8KHz clock on its CMs. By default, it uses the clock on the primary CM as the source for its timing subsystem. To configure the unit to obtain its clock from another source, set the following parameter (shown with its default setting):

[in SYSTEM]

system-8k-clock = controller

For example, the following commands cause the system to first attempt to use a trunk port as its clock source, and to use the built-in clock only if it finds no ports that are eligible clock sources:

admin> read systemSYSTEM read

admin> set system-8k-clock = trunk-module

admin> writeSYSTEM written

Configuring trunk ports as eligible clock sources

Both the DS3-ATM and OC3-ATM profiles support Clock-Source and Clock-Priority parameters for specifying whether the port can be used to source the ATM network clock and feed it to the primary CM as the master clock for the unit. Each of the four trunk ports can be configured as eligible or ineligible for this use, and can be assigned a high, middle, or low priority for being elected as the clock source. Following are the relevant parameters, shown with default settings:

[in DS3-ATM/{ any-shelf any-slot 0 }:line-config]clock-source = not-eligibleclock-priority = middle-priority

[in OC3-ATM/{ any-shelf any-slot 0 }:line-config]clock-source = not-eligibleclock-priority = middle-priority

Parameter Specifies

System-8K-Clock Source for the master system clock. With the default controller setting, the Stinger unit uses the built-in 8KHz clock on the primary CM. If set to trunk-module, the unit obtains its clock from a trunk port that has been configured as an eligible clock source, using the ports in order of their priority. If no eligible trunk ports are available, it uses the CM clock. If set to bits, the unit sources its clock from the Building Interoffice Timing Source T1 framer on its Alarm module.

Parameter Specifies

Clock-Source Enable/disable obtaining the system clock signal from the port. By default, ports are not eligible clock sources. For information about using an OC3 line as the source for the system clock, see “Using trunk ports as clock source” on page 4-3.

Configuring the Trunk ModulesVPI/VCI allocation for trunk ports


If more than one line is eligible to be the clock source, the system chooses the one with the highest priority, as specified by the Clock-Priority setting. If multiple sources of equal priority are present, the system selects the first valid clock source. (A clock source is valid if the Clock-Source parameter is set to eligible and the DS3 or OC3 interface is synchronized.)

Once it has selected a clock source, the system uses that source until the source becomes unavailable or a higher priority source becomes available. If there are no eligible external sources, the system uses an internal clock generated by the primary CM.

For example, the following commands configure both ports of the first DS3-ATM module as a eligible clock sources, with the first port assigned a higher priority for this use:

admin> read ds3-atm { 1 trunk-module-1 1 }DS3-ATM/{ shelf-1 trunk-module-1 1 } read

admin> set line-config clock-source = eligible

admin> set line-config clock-priority = high

admin> writeDS3-ATM/{ shelf-1 trunk-module-1 1 } written

admin> read ds3-atm { 1 trunk-module-1 2 }DS3-ATM/{ shelf-1 trunk-module-1 2 } read


admin> set line-config clock-priority = low


For another example, the following commands configure only the first port of the second OC3-ATM trunk module as an eligible clock source. If this port becomes unavailable and is not backed up, the unit begins using the built-in clock on the primary CM.

admin> read oc3-atm { 1 trunk-module-1 1 }OC3-ATM/{ shelf-1 trunk-module-1 1 } read


admin> set line-config clock-priority = high


VPI/VCI allocation for trunk portsTrunk-side, the Stinger unit can support a maximum of 32K connections using VC switching. By default, the system provisions 8K VCCs to each of the four trunk ports. Administrators can configure VCI ranges on a port to change the number of VC-switched connections handled by

Clock-Priority Priority of the interface as the system’s clock source. (High, middle, or low priority.) Once the Stinger unit chooses a clock source, it uses that source until the interface becomes unavailable or a higher-priority source becomes available.

Parameter Specifies


Configuring the Trunk ModulesVPI/VCI allocation for trunk ports

each port. For example, an administrator might provision a port that handles traffic to a corporate network with more VCCs, and ports that handle traffic to ISPs with fewer VCCs.

Note: There is no restriction on the number of VCIs supported on virtual path connections (VPCs).The system does not examine the VCI value when it is performing VP switching.

For each trunk port, the VPI range is always 0 to 255, which is the full 8-bit value specified in the UNI signaling standards. The VCI range is used in combination with specific VPI numbers that have been reserved for VC switching purposes. Zero is always reserved for VC switching. Following are the relevant parameters, shown with their default settings:

[in DS3-ATM/{ any-shelf any-slot 0 }:line-config]vpi-vci-range = vpi-0-255-vci-32-8191vc-switching-vpi = [ 0 0 0 0 0 0 0 ]

[in OC3-ATM/{ any-shelf any-slot 0 }:line-config]vpi-vci-range = vpi-0-255-vci-32-8191vc-switching-vpi = [ 0 0 0 0 0 0 0 ]

Note: To make the configuration effective immediately, when you change either of these values in the profile of a trunk port, the system drops all connections in the system, reconfigures the internals with the new range, and then reinstates all connections. While this has the advantage of not requiring a reset, administrators should be very careful when changing this profile, to avoid connection delays.

Table 4-1 shows sample (arbitrary) VPIs used for VC switching in combination with the configured VCI ranges, and the resulting number of VCCs the port handles:

Parameter Specifies

VPI-VCI-Range Valid range of VCI numbers to be used with VPI zero for virtual channel connections (VCCs). The default is 8K, which distributes the system maximum of 32K VCCs across four trunk ports. If you specify additional VPIs for VC switching (see the VC-Switching-VPI setting), the number of VCCs supported on a port increases proportionally for each of the reserved VPIs. You must set this parameter together with the VC-Switching-VPI parameter to distribute the 32K VCCs across active trunk ports. Following are valid values: vpi-0-255-vci-32-255, vpi-0-255-vci-32-511, vpi-0-255-vci-32-1023, vpi-0-255-vci-32-2047, vpi-0-255-vci-32-4095, vpi-0-255-vci-32-8191, vpi-0-255-vci-32-16383.

VC-Switching-VPI Array of up to 7 VPIs to use for VC switching. The default is zero, which is always used for VC switching. With the default zero settings, the range of VCIs specified in the VPI-VCI-Range setting determines the total number of VCCs the port will handle. If you specify another VPI number to use for VC switching, the number of VCCs the port will allow is doubled. You must set this parameter together with the VPI-VCI-Range setting to distribute the maximum 32K VCCs across active trunk ports.

Configuring the Trunk ModulesConfiguring DS3-ATM interfaces


For example, the following commands configure the first trunk port in slot 17 to handle 16K VCCs (rather than the default 8K) by adding one additional VPI to be used for VC switching:


admin> set line-config vc-switching-vpi 2 = 1


The following commands also enable the first trunk port in slot 17 to handle 16K VCCs, but use only the default zero VPI for VC switching:



admin> set line-config vpi-vci-range = vpi-0-255-vci-32-16383


Configuring DS3-ATM interfacesEach DS3-ATM trunk module supports two 44.736 Mbps interfaces, and each DS3-ATM interface connects to one ATM switch.

Table 4-1. Combined settings and resulting number of VCCs on the port

VCI range Sample VPIs used for VC switching

# of VCCs on port

vpi-0-255-vci-32-255 0 (default) .25K

0 and 1 .5K

vpi-0-255-vci-32-511 0 (default) .5K

0, 1, and 2 1.5K

vpi-0-255-vci-32-1023 0 (default) 1K

1, 10, 20, and 40 4K

vpi-0-255-vci-32-2047 0 (default) 2K

0 and 100 4K

vpi-0-255-vci-32-4095 0 (default) 4K

0 and 80 8K

vpi-0-255-vci-32-8191 0 (default) 8K

0 and 30 16K

vpi-0-255-vci-32-16383 0 (default) 16K

0 and 25 32K



Overview of DS3-ATM settings

The Stinger unit creates a DS3-ATM profile containing the following parameters for each DS3 interface detected in the system. The parameters are shown with default settings for the first port of a TM in slot 17.

[in DS3-ATM/{ shelf-1 trunk-module-1 1 }]name = 1:17:1physical-address* = { shelf-1 trunk-module-1 1 }enabled = nospare-physical-address = { any-shelf any-slot 0 }sparing-mode = inactive

[in DS3-ATM/{ shelf-1 trunk-module-1 1 }:line-config]trunk-group = 9nailed-group = 801activation = staticcall-route-info = { any-shelf any-slot 0 }loopback = no-loopbackhigh-tx-output = noframer-mode = C-BIT-PLCPvpi-vci-range = vpi-0-255-vci-32-8191vc-switching-vpi = [ 0 0 0 0 0 0 0 ]clock-source = not-eligibleclock-priority = middle-priority

Parameter Specifies


Physical-Address Physical address of the trunk port in the Stinger unit.

Enabled Enable/disable the DS3-ATM interface. (Disabled by default.)

Spare-Physical-Address Physical address of the trunk port to be used as a spare. For details, see “Trunk port sparing” on page 4-1.

Sparing-Mode Sparing mode for the port. For details, see “Trunk port sparing” on page 4-1.

Trunk-Group Not currently used. Leave the default value (zero).

Nailed-Group Nailed-group number for the DS3-ATM physical interface. A Connection or RADIUS profile specifies this number to make use of the interface, as described in Chapter 6, “Configuring ATM Circuits,” and Chapter 7, “Configuring Terminating ATM Connections.”

Each interface is assigned a unique default number, so you do not need to modify this parameter. If you assign a new value, it must be a number from 1 to 1024 that is unique within the system. See “Displaying DS3 port status and nailed groups” on page 4-9 for related information.

Activation Line activation mode. Only the static setting is currently supported.




Displaying DS3 port status and nailed groups

To see the nailed-group numbers for trunk ports, use the ATMTrunks command. For example, the command output that follows shows the nailed-group numbers for DS3 trunks. In this example, the system has one DS3-ATM installed in slot 18:

admin> atmtrunks -a

All OC3 ATM trunks:OC3 Lines (dvOp dvUpSt dvRq sAdm nailg)

All DS3 ATM trunks:DS3 Lines (dvOp dvUpSt dvRq sAdm nailg)Line { 1 18 1 } (Up Idle UP UP 00851Line { 1 18 2 } (Up Idle UP UP 00852

Setting DS3 framing formats

Administrators can specify C-bit Physical Layer Convergence Protocol (PLCP) or C-bit ATM Direct Mapping (ADM) framing format for a DS3-ATM interface. Both sides of a DS3-ATM link must agree about the framing format.

The PLCP format incurs some overhead for framing. ADM format does not. When ADM framing is used, the entire DS3 payload is used for ATM cells. Within each format, the framer can operate in the following modes:

• Free-running and fixed-stuffing

• Loop-timed (the Stinger unit obtains the clock from the other side of the link)

• Frame-locked (the Stinger unit provides the clock)

Loopback Enable/disable loopback for diagnosing connectivity or possible equipment problems. Loopback is disabled by default, which is required for normal operations.

High-Tx-Output Enable/disable high transmit output. The default is no, which is correct for DS3 cables that are less than 255 long. For cables longer than 255 feet, set to yes.

Framer-Mode DS3 ATM framer mode. Valid values are C-bit-ADM, C-BIT-PLCP, c-bit-adm-loop-timed, c-bit-plcp-loop-timed, c-bit-adm-frame-locked, and c-bit-plcp-frame-locked.

VPI-VCI-Range Valid range of VCI numbers to be used with specified VPIs for VCCs. See “VPI/VCI allocation for trunk ports” on page 4-5.

VC-Switching-VPI Array of up to seven VPIs to use for VC switching. See “VPI/VCI allocation for trunk ports” on page 4-5.

Clock-Source Enable/disable obtaining the system clock signal from the port. See “Using trunk ports as clock source” on page 4-3.

Clock-Priority Priority of the interface as the system’s clock source. See “Using trunk ports as clock source” on page 4-3.

Parameter Specifies



Free-running means that the DS3 transmit clock is derived from an on-board oscillator. Fixed stuffing applies to PLCP framing. It means that the PLCP frame is also being derived from the on-board oscillator. The free-running and fixed-stuffing mode is typically used when the line is neither providing the clock (frame-locked) nor syncing to an incoming clock (loop-timed).

Example of DS3-ATM configuration

In this example, the administrator enables two DS3-ATM interfaces and designates the ports of the other DS3-ATM trunk module as spare ports, for use if the primary trunk ports becomes inactive. Because two ports are spares, the administrator increases the number of VCCs that can be handled by both of the primary ports from 8K to 16K.

Figure 4-1. DS3 interfaces to the ATM network

The following commands list the trunk port profiles:

admin> dir ds3-atm40 08/03/1999 15:33:35 { shelf-1 trunk-module-1 2 } 1:17:225 08/03/1999 15:37:13 { shelf-1 trunk-module-2 1 } 1:18:125 08/03/1999 15:38:25 { shelf-1 trunk-module-2 2 } 1:18:240 08/04/1999 10:18:22 { shelf-1 trunk-module-1 1 } 1:17:1

The following commands enable the ports of the first TM and make the ports of the module spares:

admin> read ds3-atm {1 trunk-module-1 1}DS3-ATM/{ shelf-1 trunk-module-1 1 } read











Spare ports

ATM

Active DS3-ATM interfaces

Configuring the Trunk ModulesConfiguring OC3-ATM interfaces





The following commands adds VPI 10 and VPI 20 as a valid VPI for VC switching on the first and second active ports, respectively, which doubles the number of VCCs the ports can handle (from 8K VCCs to 16K):







Configuring OC3-ATM interfacesEach OC3-ATM trunk module supports two 155.52 Mbps interfaces, and each OC3-ATM interface connects to one ATM switch. With two OC3-ATM modules installed, the total trunk-side bandwidth is 622 Mbps.

The Stinger unit creates an OC3-ATM profile for each OC3 interface detected in the system. The OC3-ATM profiles provide an interface to the physical ATM framer associated with each interface, which supports the standard UTOPIA interface for ATM.

Overview of OC3-ATM settings

Following are the parameters for configuring an OC3-ATM interface. The parameters are shown with default settings for the first port of a TM in slot 18.

[in OC3-ATM/{ shelf-1 trunk-module-2 1 }]name = 1:18:1physical-address* = { shelf-1 trunk-module-1 1 }enabled = nospare-physical-address = { any-shelf any-slot 0 }sparing-mode = inactive

[in OC3-ATM/{ any-shelf any-slot 0 }:line-config]trunk-group = 0nailed-group = 801call-route-info = { any-shelf any-slot 0 }loopback = no-loopbackframer-rate = STS-3ctx-scramble-disabled = notx-cell-payload-scramble-disabled = noloop-timing = yes



vpi-vci-range = vpi-0-255-vci-32-8191vc-switching-vpi = [ 0 0 0 0 0 0 0 ]clock-source = not-eligibleclock-priority = middle-priority

Parameter Specifies


Physical-Address Physical address of the trunk port in the Stinger unit.

Enabled Enable/disable the OC3-ATM interface. (Disabled by default.) When the OC3 interface is disabled, it transmits the OC3 Idle Signal to the far end.

Spare-Physical-Address Physical address of the trunk port to be used as a spare. For details, see “Trunk port sparing” on page 4-1.

Sparing-Mode Sparing mode for the port. For details, see “Trunk port sparing” on page 4-1.

Trunk-Group Not currently used. Leave the default value (zero).

Nailed-Group Nailed-group number for the OC3-ATM physical interface. A Connection or RADIUS profile specifies this number to make use of the interface, as described in Chapter 6, “Configuring ATM Circuits,” and Chapter 7, “Configuring Terminating ATM Connections.”

Each interface is assigned a unique default number, so you do not need to modify this parameter. If you assign a new value, it must be a number from 1 to 1024 that is unique within the system. See “Displaying OC3 status and nailed groups” on page 4-13 for related information.


Loopback Enable/disable loopback for diagnosing connectivity or possible equipment problems. Loopback is disabled by default, which is required for normal operations.

Framer-Rate Framing operations. Only the default STS-3C setting is used, which represents both the 155.52 Mbps interface in the U.S. and the equivalent European 155.52 Mbps interface (STM-1).

Tx-Scramble-Disabled Enable/disable scrambling and descrambling of the entire transmit and receive stream. This function is enabled by default. Disable it only if the far-end switch has disabled the corresponding functions.

Tx-Cell-Payload-Scramble-Disabled

Enable/disable scrambling and descrambling of the 48-byte ATM cell payload in transmitted and received cells. This function is enabled by default. Disable it only if the far end switch has disabled the corresponding functions.

Loop-Timing Enable/disable derivation of transmission timing from receiver inputs. Loop timing is enabled by default. If the parameter is set to No, transmission timing is derived from the reference clock instead.



Displaying OC3 status and nailed groups

To see the nailed-group numbers for trunk ports, use the ATMTrunks command. For example, the command output that follows shows the nailed-group numbers for OC3 trunks. In this example, the system has one OC3-ATM installed in slot 17:

admin> atmtrunks -a

All OC3 ATM trunks:OC3 Lines (dvOp dvUpSt dvRq sAdm nailg)Line { 1 17 1 } (Up Idle UP UP 00801) Line { 1 17 2 } (Up Idle UP UP 00802)

All DS3 ATM trunks:DS3 Lines (dvOp dvUpSt dvRq sAdm nailg)

Changing physical-layer interface settings

The ATM framer multiplexes ATM cells into the SONET payload and extracts cells from the SONET payload for reassembly into packets. It uses the STS-3C frame format. The default STS-3C setting indicates a 155.52 Mbps interface in the U.S. as well as the equivalent European 155.52 Mbps interface (STM-1).

The interface provides a SONET-level scrambler and one at the cell payload level. Typically, these functions are enabled. They should be disabled only if the far-end switch requires it.

Examples of OC3-ATM configuration

Figure 4-2 shows three active OC3-ATM interfaces and one spare port, which remains inactive until one of the other trunk ports becomes inactive.

VPI-VCI-Range Valid range of VCI numbers to be used with specified VPIs for VCCs. See “VPI/VCI allocation for trunk ports” on page 4-5.

VC-Switching-VPI Array of up to seven VPIs to use for VC switching. See “VPI/VCI allocation for trunk ports” on page 4-5.

Clock-Source Enable/disable obtaining the system clock signal from the port. See “Using trunk ports as clock source” on page 4-3.

Clock-Priority Priority for choosing of the interface as the system’s clock source. See “Using trunk ports as clock source” on page 4-3.

Parameter Specifies



Figure 4-2. OC3 interfaces to the ATM network

The following commands list the trunk port profiles:

admin> dir oc3-atm40 08/03/1999 15:33:35 { shelf-1 trunk-module-1 2 } 1:17:225 08/03/1999 15:37:13 { shelf-1 trunk-module-2 1 } 1:18:125 08/03/1999 15:38:25 { shelf-1 trunk-module-2 2 } 1:18:240 08/04/1999 10:18:22 { shelf-1 trunk-module-1 1 } 1:17:1

The following commands enable the first three ports and make the second port in the second module the spare:



















Spare port

ATM

Active OC3-ATM interfaces

Configuring the Trunk ModulesChecking ATM trunk interface status





Because one port is a spare, the administrator increases the number of VCCs that can be handled by the first trunk port from 8K to 16K. This allows the system to handle the full 32K maximum VCCs trunk-side, even though it has only three active ports. The following commands increase the valid range of VCIs from 8K to 16K on port 1 of the first trunk module:


admin> set line-config vpi-vci-range = vpi-0-255-vci-32-16383


Checking ATM trunk interface statusThe Stinger unit creates a DS3-ATM-Stat profile for each of its DS3 interfaces and an OC3-ATM-Stat profile for each of its OC3 interfaces. The profiles provide information about the state of the physical interfaces, error counters, and other status information.

DS3 ATM status information

The error counters in the DS3-ATM-Stat profile are cleared when the DS3 physical interface becomes active (synchronized). The counts accumulate every second if there is any error. Following are the DS3-ATM-Stat parameters, shown with sample settings for an active line:

[in DC3-ATM-STAT/{ shelf-1 trunk-module-2 1 }]

physical-address* = { shelf-1 trunk-module-2 1 }

line-state = active

spare-physical-address = { any-shelf any-slot 0 }

sparing-state = sparing-none

vpi-vci-range = vpi-0-255-vci-32-8191

vc-switching-vpi = 0

vcc-vpi = [ 0 0 0 0 0 0 0 ]

f-bit-error-count = 0

p-bit-error-count = 0

cp-bit-error-count = 0

feb-error-count = 0

bpv-error-count = 0

loss-of-signal = False

loss-of-frame = False

yellow-receive = False

ais-receive = False

Parameter Indicates

Physical-Address Physical location of the DS3-ATM line within the Stinger system.



Line-State Overall state of the DS3 line. May be set to active (the line is enabled and multipoint has been established), does-not-exist (link is not physical on board), disabled, loss-of-signal (near end loss of signal), loss-of-frame (near end loss of frame - red alarm), yellow-alarm (receiving far end loss of frame - yellow alarm), and ais-receive (receiving alarm indication signal).

Spare-Physical-Address The sparing peer of this trunk port. If the current port is the primary trunk port, the value identifies its spare (secondary) trunk port. If the current port is the secondary trunk, the value identifies the primary trunk port.

Sparing-State The state of the sparing function. sparing-none indicates that sparing is not enabled. If sparing is enabled and the current port is the primary trunk port, the value can be primary-active or primary-inactive. If sparing is enabled and the current port is the secondary trunk port, the value can be secondary-active or secondary-inactive.

VPI-VCI-Range Current valid VCI range configured for the port. For details, see “VPI/VCI allocation for trunk ports” on page 4-5.

VC-Switching-VPI Array of VPIs used for VC switching. For related information, see “VPI/VCI allocation for trunk ports” on page 4-5.

VCC-VPI For internal use only.

F-Bit-Error-Count Number of F-bit errors. If three or more errors occur in up to 16 consecutive F-bits in a DS3 M-frame, a DS3 out-of-frame defect is detected. If an out-of-frame defect is consistent for up to ten seconds, a DS3 loss-of-frame detect is detected.

P-Bit-Error-Count Number of P-bit parity errors. These errors occur when the system receives P-bit code on a DS3 M-frame that is not identical to the corresponding P-bit code that was calculated locally.

CP-Bit-Error-Count Number of CP-bit parity errors.

FEB-Error-Count Number of far-end C-bit coding violations reported via the far end block error count.

BPV-Error-Count Number of Bipolar Violation (BPV) errors. BPV errors may indicate that the line sent consecutive one bits with the same polarity. It could also mean that three or more consecutive zeroes were sent or an incorrect polarity.

Loss-of-Signal Loss of signal on the line. False indicates that the carrier is maintaining a connection.

Loss-of-Frame Loss of frame on the line (also known as a red alarm.) False indicates that the line is up and in frame.

Yellow-Receive Far end loss-of-frame (Yellow Alarm) occurred on the line. False indicates that a Yellow Alarm was not received.

AIS-Receive Far end is sending Alarm Indication Signal (AIS). False indicates local device has not received an AIS.

Parameter Indicates



For details about DS3 line errors, see RFC 1407, Definitions of Managed Objects for the DS3/E3 Interface Type.

Checking OC3-ATM interface status

The system creates an OC3-ATM-Stat profile for each OC3 interface. The profiles provide ATM framer status and error counters, as well as performance-monitoring and interval-performance-monitoring counters for the SONET payload.

Checking line and ATM framer status

Following are the OC3-ATM-STAT parameters for the physical interface, shown with sample settings for an active line:

[in OC3-ATM-STAT/{ shelf-1 trunk-module-2 1 }]

physical-address* = { shelf-1 trunk-module-2 1 }

line-state = active

spare-physical-address = { any-shelf any-slot 0 }

sparing-state = sparing-none

vpi-vci-range = vpi-0-255-vci-32-8191

vc-switching-vpi = 0

vcc-vpi = [ 0 0 0 0 0 0 0 ]

loss-of-signal = False

loss-of-frame = False

out-of-frame = False

section-state = sonet-section-active-no-defect

path-state = sonet-path-active-no-defect

ais-receive = False

yellow-receive = False

out-of-cell-delineation = False

loss-of-cell-delineation = False

aps-receive = False

rsop-bip-error-count = 0

rlop-bip-error-count = 0

rlop-febe-error-count = 0

rpop-bip-error-count = 0

rpop-febe-error-count = 0

racp-chcs-error-count = 0

racp-uchcs-error-count = 12064

racp-rx-cell-count = 32855

tacp-tx-cell-count = 16

frequency-justification-count = 0

HEC-cell-drop-counter = 0

FIFO-overflow-counter = 0

idle-cell-counter = 0

valid-cell-counter = 0

performance-monitoring = { 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 }

interval-performance-monitoring = [ { 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0+

Parameter Indicates

Physical-Address Physical location of the OC3-ATM line within the Stinger system.



Line-State Overall state of the OC3 line. May be set to active (the line is enabled), does-not-exist (no link has been established), disabled, loss-of-signal, loss-of-frame, yellow-alarm (receiving yellow-alarm from far end), and ais-receive (receiving alarm indication signal).

Spare-Physical-Address The sparing peer of this trunk port. If the current port is the primary trunk port, the value identifies its spare (secondary) trunk port. If the current port is the secondary trunk, the value identifies the primary trunk port.

Sparing-State The state of the sparing function. sparing-none indicates that sparing is not enabled. If sparing is enabled and the current port is the primary trunk port, the value can be primary-active or primary-inactive. If sparing is enabled and the current port is the secondary trunk port, the value can be secondary-active or secondary-inactive.

VPI-VCI-Range Current valid VCI range configured for the port. For details, see “VPI/VCI allocation for trunk ports” on page 4-5.

VC-Switching-VPI Array of VPIs used for VC switching. For related information, see “VPI/VCI allocation for trunk ports” on page 4-5.

VCC-VPI For internal use only.

Loss-of-Signal Loss of signal on the line. False indicates that the carrier is maintaining a connection.

Loss-of-Frame Loss of frame on the line (also known as a red alarm.) False indicates that the line is up and in frame.

Out-of-Frame Near end is out of frame. False indicates that the line is up and in frame.

Section-State State of the SONET section.

Path-State State of the SONET path.

AIS-Receive Far end is sending Alarm Indication Signal (AIS). False indicates local device has not received an AIS.

Yellow-Receive Far end loss-of-frame (Yellow Alarm) occurred on the line. False indicates that a Yellow Alarm was not received.

Out-Of-Cell-Delineation Out of cell delineation - HEC check failed.

Loss-Of-Cell-Delineation Loss of cell delineation.

Aps-Receive Not currently used.

RSOP-Bip-Error-Count Number of Receive Section Overhead Processor (RSOP) Bit Interleaved Parity (BIP)-8 errors. The RSOP synchronizes and descrambles frames and provides section-level alarms and performance monitoring.

RLOP-BIP-Error-Count Number of Receive Line Overhead Processor (RLOP) BIP-8 errors. The RLOP is responsible for line-level alarms and for monitoring performance.

RLOP-FEBE-Error-Count

Number of RLOP Far End Block Errors (FEBE).

Parameter Indicates



Monitoring errors and performance of the SONET payload

The Performance-Monitoring and Interval-Performance-Monitoring subprofiles include counters for SONET performance and error conditions.

The Performance-Monitoring values are the cumulative performance counters, which are reset at the end of every 15-minute interval. The information in the Performance-Monitoring counters is used to update the values in the Interval-Performance-Monitoring subprofile.

The Interval-Performance-Monitoring values represent performance for the preceding four 15-minute intervals, thereby providing performance data about the past hour.

Events that constitute errors (such as Severely Errored Frames, Loss of Signal, Alarm Indication Signal, or STS-Path Loss of Pointer) are defined in RFC 1595, Definitions of Managed Objects for the SONET/SDH Interface Type.

Performance and error counters are maintained at the Section, Line, Path, and Far-End layers.

RPOP-BIP-Error-Count Number of Receive Path Overhead Processor (RPOP) BIP-8 errors. The RSOP interprets pointers and extracts path overhead and the synchronous payload envelope. It is also responsible for path-level alarms and for monitoring performance.

RPOP-FEBE-Error-Count

Number of RPOP Far End Block Errors (FEBE).

RACP-CHCS-Error-Count

Number of Receive ATM Cell Processor (RACP) Correctable Header Check Sequence (CHCS) errors. The RACP delineates ATM cells and filters cells on the basis of their idle or unassigned status or HCS errors. It also descrambles the cell payload.

RACP-UCHCS-Error-Count

Number of RACP Uncorrectable Header Check Sequence (UCHCS) errors.

RACP-Rx-Cell-Count Receive ATM Cell Processor (RACP) receive cell count.

TACP-Tx-Cell-Count Transmit ATM Cell Processor (TACP) transmit cell count.

Frequency-Justification-Count

Number of frequency justification operations.

Hec-Cell-Drop-Counter Number of cells dropped by HEC processing.

Fifo-Overflow-Counter Number of cells dropped because of FIFO overflow.

Idle-Cell-Counter Total number of idle cells received.

Valid-Cell-Counter Total number of valid cells received.

Parameter Indicates



Figure 4-3. SONET layers

As shown in Figure 4-3, SONET section is a single run of cable. Section-terminating equipment is any adjacent pair of switches. A line is one or more sections. A path is an end-to-end circuit.

Coding violations are bit-interleaved parity errors detected in the incoming signal. A Severely Errored Frame defect begins when four contiguous words are detected with an error in frame alignment, and ends when two contiguous words occur with error-free frame alignment.

An Errored Second is a second in which one or more coding violations or incoming errors have occurred at the specified layer.

A Severely Errored Second is a second in which more than a certain number of coding violations or incoming errors have occurred, with the number based on line rate and Bit Error Rate (BER).

A Severely Errored Framing Second is a second in which one or more Severely Errored Frame defects occur at the Section layer.

An Unavailable Second is a second in which the interface is unavailable at the specified layer. An interface is considered unavailable after 10 consecutive Severely Errored Seconds.

Following are the two levels of performance monitoring counters, shown with no errors (zero counts):

[in OC3-ATM-STAT/{ shelf-1 trunk-module-2 1 }:performance-monitoring]sonet-section-errored-seconds = 0sonet-section-severely-errored-seconds = 0sonet-section-severely-errored-framing-seconds = 0sonet-section-coding-violations = 0sonet-line-errored-seconds = 0sonet-line-severely-errored-seconds = 0sonet-line-coding-violations = 0sonet-line-unavailable-seconds = 0sonet-far-end-line-errored-seconds = 0sonet-far-end-line-severely-errored-seconds = 0sonet-far-end-line-coding-violations = 0sonet-far-end-line-unavailable-seconds = 0sonet-path-errored-seconds = 0sonet-path-severely-errored-seconds = 0sonet-path-coding-violations = 0sonet-path-unavailable-seconds = 0sonet-far-end-path-errored-seconds = 0sonet-far-end-path-severely-errored-seconds = 0

Path

Line

Section

SONET



sonet-far-end-path-coding-violations = 0

sonet-far-end-path-unavailable-seconds = 0

[in OC3-ATM-STAT/{ shelf-1 trunk-module-2 1 }:interval-performance-

monitoring[1]]

sonet-section-errored-seconds = 0

sonet-section-severely-errored-seconds = 0

sonet-section-severely-errored-framing-seconds = 0

sonet-section-coding-violations = 0

sonet-line-errored-seconds = 0

sonet-line-severely-errored-seconds = 0

sonet-line-coding-violations = 0

sonet-line-unavailable-seconds = 0

sonet-far-end-line-errored-seconds = 0

sonet-far-end-line-severely-errored-seconds = 0

sonet-far-end-line-coding-violations = 0

sonet-far-end-line-unavailable-seconds = 0

sonet-path-errored-seconds = 0

sonet-path-severely-errored-seconds = 0

sonet-path-coding-violations = 0

sonet-path-unavailable-seconds = 0

sonet-far-end-path-errored-seconds = 0

sonet-far-end-path-severely-errored-seconds = 0

sonet-far-end-path-coding-violations = 0

sonet-far-end-path-unavailable-seconds = 0

Parameter Indicates

SONET-Section-Errored-Seconds

Number of Errored Seconds at the Section layer.

SONET-Section-Severely-Errored-Seconds

Number of Severely Errored Seconds at the Section layer.

SONET-Section-Severely-Errored-Framing-Seconds

Number of Severely Errored Framing seconds at the Section layer.

SONET-Section-Coding-Violations

Number of bit-interleaved parity errors at the Section layer.

SONET-Line-Errored-Seconds

Number of Errored Seconds at the Line layer.

SONET-Line-Severely-Errored-Seconds

Number of Severely Errored Seconds at the Line layer.

SONET-Line-Coding-Violations

Number of bit-interleaved parity errors at the Line layer.

SONET-Line-Unavailable-Seconds

Number of Unavailable Seconds at the Line layer.

SONET-Far-End-Line-Errored-Seconds

Number of Errored Seconds at the far-end device’s Line layer.

SONET-Far-End-Line-Severely-Errored-Seconds

Number of Severely Errored Seconds at the far-end device’s Line layer.

SONET-Far-End-Line-Coding-Violations

Number of bit-interleaved parity errors at the far-end device’s Line layer.



SONET-Far-End-Line-Unavailable-Seconds

Number of Unavailable Seconds at the Line layer.

SONET-Path-Errored-Seconds

Number of Errored Seconds at the Path layer.

SONET-Path-Severely-Errored-Seconds

Number of Severely Errored Seconds at the Path layer.

SONET-Path-Coding-Violations

Number of bit-interleaved parity errors at the Path layer.

SONET-Path-Unavailable-Seconds

Number of Unavailable Seconds at the Path layer.

SONET-Far-End-Path-Errored-Seconds

Number of Errored Seconds at the far-end device’s Path layer.

SONET-Far-End-Path-Severely-Errored-Seconds

Number of Severely Errored Seconds at the far-end device’s Path layer.

SONET-Far-End-Path-Coding-Violations

Number of bit-interleaved parity errors at the far-end device’s Path layer.

SONET-Far-End-Path-Unavailable-seconds

Number of Unavailable Seconds at the far-end device’s Path layer.

Parameter Indicates


5Specifying Traffic Contracts

ATM traffic management specifications define service categories for different types of traffic that must have particular characteristics. For example, voice traffic requires a constant amount of bandwidth and cannot tolerate delays, whereas file transfer can tolerate delay and variable bandwidth. ATM switches that reside between two end systems use the ATM service categories and related traffic management settings to alter the characteristics of a cell stream to meet service requirements.

Stinger units support configurable traffic contracts to specify a service category and define related traffic management parameters. Once you have specified the contracts you need, you can apply a contract to the upstream or downstream traffic (or both) of any number of connections.

Note: With the current software version, the Stinger unit does not correlate bit rates configured for an AL-DMT port with those specified in a traffic contract. The two bit-rate specifications currently operate independently.

Overview of ATM Quality of Service parametersNote: Some of the ATM Quality of Service parameters are designated as not-available when you display the contents of an ATM-QOS profile. Those settings require the next generation of LIM hardware. For information about availability of the hardware, please contact your service representative.

To configure an ATM traffic contract, you must set relevant parameters in ATM-QOS profiles. Following are the ATM-QOS parameters, shown here with default settings:

[in ATM-QOS/""]contract-name* = ""qos-class = cbrpeak-rate-kbits-per-sec = 10peak-cell-rate-cells-per-sec = 23sustainable-rate-kbits-per-sec = 10sustainable-cell-rate = 23cell-delay-variation-tolerance = 20max-burst-size = 0aal-type = aal-5early-packet-discard = yespartial-packet-discard = yestag-or-discard = discard

Overview of ATM Quality of Service parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Examples of defining a traffic contract . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5


Specifying Traffic ContractsOverview of ATM Quality of Service parameters

Parameter Specifies

Contract-Name A unique name for the contract (a text string of up to 16 characters). The name is used to apply the specified traffic settings to any number of connections.

QoS-Class ATM service category. Supported values are CBR (Constant Bit Rate), Real-Time-VBR (Real-Time Variable Bit Rate), Non-Real-Time-VBR (Non-Real-Time Variable Bit Rate), ABR (Available Bit Rate), and UBR (Unspecified Bit Rate).

Peak-Rate-Kbits-Per-Sec Peak bit rate per second in Kbps. For CBR traffic, this setting specifies the static bit rate. For ABR, it is the maximum explicit rate. For VBR, it is the upper boundary of the variable bit rate.

Peak-Cell-Rate-Cells-Per-Sec

Peak Cell Rate (PCR), which is the maximum number of cells allowed per second. The value is read-only. The PCR is calculated from the Peak-Rate-Kbits-Per-Sec setting and used in the internal ATM configuration.

Sustainable-Rate-Kbits-Per-Sec

Sustainable bit rate in Kbps. This setting applies only to VBR traffic, for which the bit rate is variable within the values defined for Peak Cell Rate (PCR), Sustainable Cell Rate (SCR), and Maximum Burst Size (MBS).

Sustainable-Cell-Rate Sustainable Cell Rate (SCR), which is the average cell transmission rate allowed over a given period of time on a given circuit. The value is read-only. It is calculated from the Sustainable-Rate-Kbits-Per-Sec setting and used in the internal ATM configuration.

Cell-Delay-Variation-Tolerance

Cell delay variation in microseconds. This setting is related to the jitter tolerance of the application. For example, the ideal delay variation would be zero for an application such as voice. The default 20 milliseconds is a reasonable jitter threshold for most applications with a low tolerance for delay (CBR and real-time VBR traffic, for example). A higher value could be used for non-real-time VBR and other applications that are not delay sensitive.

Max-Burst-Size Maximum Burst Size (MBS), which is the maximum number of cells that can be transmitted at PCR before the Stinger unit determines that the connection is exceeding the traffic contract and begins discarding or tagging cells. This value is expressed relative to the PCR (as a cell rate, not Kbps). It applies only to VBR traffic.

AAL-Type ATM Adaptation Layer type. Stinger units support AAL5 and AAL0 types. AAL0 is used for all traffic that is not AAL5. You can accommodate specific AAL types other than 5 by using the AAL0 setting with the appropriate service category setting. AAL5 circuits always handle packet traffic, which requires that the system monitor the cellstream for the end-of-packet flag, thereby ensuring that packets rather than individual cells are discarded or tagged when necessary.



ATM service categories

ATM service categories specify the bandwidth and other requirements of various kinds of traffic. In a Stinger unit, ATM traffic contracts can specify one of the following categories:

• Constant Bit Rate (CBR)

• Real-time Variable Bit Rate (real-time-VBR)

• Non-real-time Variable Bit Rate (non-real-time-VBR)

• Available Bit Rate (ABR)

• Unspecified Bit Rate (UBR)

CBR is used for applications that do not tolerate delay (for example, voice or video transmission). It guarantees that a static amount of bandwidth (the PCR) is always available to the circuit. The source system can send cells at or below the specified PCR without compromising the quality of service.

Real-time VBR is used for applications such as compressed audio or interactive multimedia, which do not tolerate significant delay but can tolerate some delay variance (jitter). Real-time VBR allows a variable amount of bandwidth, characterized by a PCR, SCR, and MBS. The source system can send cells at a rate that varies (and may include bursts) but is within the boundaries defined by these settings.

Non-real-time VBR is used for applications such as transaction processing, which can tolerate delay but not cell loss. The bandwidth must remain with the boundaries of the PCR, SCR, and MBS.

ABR is used for data applications such as file transport or message delivery, which can tolerate delay. This category, which is characterized by PCR, provides a way for switches to instruct multiple source systems to slow down if required by network conditions. For end systems that adapt transmission rates on the basis of the feedback they receive from the switch, connections experience a low cell loss ratio and obtain a fair share of the available bandwidth.

Early-Packet-Discard Enable/disable Early Packet Discard (EPD). If the parameter is set to yes (the default), the unit discards the entire outbound packet if it detects buffer congestion on the first cell of the packet. This parameter applies only to AAL5 circuits.

Partial-Packet-Discard Enable/disable Partial Packet Discard (PPD). If the parameter is set to yes (the default), and the unit detects buffer congestion after some cells of a packet have been queued, the unit discards the remaining cells of an inbound packet up to but not including the last cell (which contains the end-of-packet flag). In addition, if congestion occurs when the unit is receiving the last cell of a packet, it discards the entire next packet. PPD relies on a higher layer to reject the partial packet when it is received. This parameters applies only to AAL5 circuits.

Tag-or-Discard Enable/disable tagging of cells that do not conform to the SCR part of the traffic contract. Tagging means changing the Cell Loss Priority (CLP) bit to 1. Cells not conforming to PCR are discarded.

Parameter Specifies



UBR is the lowest level of service. In effect, it makes no service or bandwidth guarantees and does not enforce traffic management. UBR is used for applications such as telecommuting or background data transfer, which can tolerate delay.

For a detailed definition of the ATM service categories, see the ATM Forum Traffic Management Specification Version 4.0. This section contains a brief overview.

Traffic policing and shaping

A Stinger unit monitors ingress traffic on its ATM interfaces to verify that the traffic does not exceed the bandwidth specified in the contract (traffic policing). If the interface is receiving traffic at too high a rate, the unit buffers the cells. It can tag or discard traffic if necessary to ensure that its egress traffic conforms to the contract (traffic shaping).

Figure 5-1. When traffic policing and shaping can occur during DSLAM operations

Stinger units implements a dual leaky bucket algorithm to regulate sustainable and peak traffic rates (SCR and PCR). For a description of the algorithm, see the ATM Forum Traffic Management Specification Version 4.0. The unit uses the virtual scheduling algorithm described in the ATM Forum UNI Specification Version 3.1 to calculate the expected arrival time of the next cell, compare that time to the actual arrival time with allowance for burst tolerance (or cell delay variation for PCR), and determine whether or not the cell is conforming. Cells that do not conform to the SCR part of the traffic contract can be tagged (CLP changed to 1) or discarded. Cells that do not conform to the specified PCR are discarded.

If the call is an AAL5 frame based call, the system can use Partial Packet Discard and Early Packet Discard to ensure that it manages the connection’s packets rather than individual cells.

Flow control

Stinger units support Explicit Forward Congestion Indication (EFCI) marking for all traffic types and explicit rate marking for ABR traffic. Both methods of flow control use ATM Resource Management (RM) cells to inform other switches in the network about the state of a connection.

In EFCI marking, if the Stinger buffer thresholds are exceeded, the unit signals its congestion to the next switch by setting the EFCI bit in the header of transmitted data cells. The destination system stores the EFCI state and includes it in the congestion-indication bit of its

DSL CPE

Traffic policing

Traffic shaping ATM

Specifying Traffic ContractsExamples of defining a traffic contract


RM cells. The source system then uses the information it obtains from the RM cells to adjust its cell transmission rate.

Figure 5-2. Congestion management with Explicit Forward Congestion Indicator

Figure 5-2 shows a Stinger unit setting the EFCI bit in its transmitted data cells to 1. The destination system returns RM cells that cause the source system to slow down its transmissions.

Explicit Rate Marking is employed only for ABR traffic. A source system sets its initial explicit rate to the PCR specified for the connection or a lower rate negotiated when the PVC is established. If bandwidth is scarce, the Stinger unit sends a lower value in the Explicit Rate field of its forward or reverse RM cells. When the source system receives an RM cell with a lower Explicit Rate value, it reduces its transmission rate to that value.

Figure 5-3. Flow control for ABR traffic with Explicit Rate Marking.

Figure 5-3 shows a Stinger unit setting the Explicit Rate field in reverse RM cells to a lower cell transmission rate for a VCC. The destination system receives the RM cell and slows down its transmission rate to the specified explicit rate.

Examples of defining a traffic contractYou should specify a traffic contract for each type of application that subscribers require. When you configure a Connection or RADIUS profile for subscribers’ PVCs, each profile can apply a contract for upstream traffic and one for downstream traffic. Each subscriber (each xDSL port) can support up to eight PVCs, one for each required application.

ATM switch

ATM

source destination0

EFCI bit

1

EFCI bit

RMRM

ATM

ATM switch

ATM

sourceCPE

RM 1024



Example of a Constant Bit Rate contract

A contract that specifies CBR demands a static amount of bandwidth, characterized by a Peak Cell Rate (PCR). CBR is the highest-priority service category, and is typically used for high-demand applications such as voice or video transmission. For CBR traffic, bandwidth is reserved for the PVC even if traffic requirements drop. The following parameters are relevant to a CBR AAL5 circuit:

[in ATM-QOS/""]

contract-name* = ""1

qos-class = cbr

peak-rate-kbits-per-sec = 10

peak-cell-rate-cells-per-sec = 23

cell-delay-variation-tolerance = 20

aal-type = aal-5

early-packet-discard = yes

partial-packet-discard = yes

tag-or-discard = discard

CBR service is characterized by a specified PCR, which is calculated from the specified peak rate in Kbps when you write the ATM-QOS profile. Maximum burst size does not apply. The following commands define a contract for CBR traffic with a bit rate of 1 Mbps and a cell delay variation tolerance of 10 milliseconds:

admin> read atm-qos cbr1

ATM-QOS/cbr1 read

admin> set qos-class = cbr

admin> set peak-rate-kbits-per-sec = 1024

admin> set cell-delay-variation-tolerance = 10

admin> write

ATM-QOS/cbr1 written

admin> list

[in ATM-QOS/cbr1]

contract-name* = cbr1

qos-class = cbr

peak-rate-kbits-per-sec = 1024

peak-cell-rate-cells-per-sec = 2415

sustainable-rate-kbits-per-sec = 1024

sustainable-cell-rate-cells-per-sec = 2415

cell-delay-variation-tolerance = 10

max-burst-size = 0

aal-type = aal-5

early-packet-discard = yes

partial-packet-discard = yes

tag-or-discard = discard

This contract allows the default discard actions (both early and partial packet discard are allowed when congestion occurs). Notice that the system sets the sustainable rates equal to the peak rates for CBR service.



Example of a Variable Bit Rate contract

Real-time VBR allows a variable amount of bandwidth, characterized by PCR, SCR, and MBS. Real-time VBR can be used in place of CBR for voice or video. It can also be used for applications such as compressed audio or interactive multimedia. Although the bandwidth is allowed to vary, real-time VBR does not allow long delays in the cell stream. The following parameters are relevant to real-time VBR traffic:

[in ATM-QOS/""]contract-name* = ""qos-class = real-time-vbrpeak-rate-kbits-per-sec = 10peak-cell-rate-cells-per-sec = 23sustainable-rate-kbits-per-sec = 10sustainable-cell-rate = 23cell-delay-variation-tolerance = 20max-burst-size = 0aal-type = aal-5early-packet-discard = yespartial-packet-discard = yestag-or-discard = discard

The following commands define a contract for real-time traffic with a peak bit rate of 1 Mbps, a sustainable bit rate of 512 Kbps, and a maximum of 20 consecutive cells at the peak rate before cells become candidates for discard:

admin> new atm-qos rt-vbr1ATM-QOS/rt-vbr1 read

admin> set qos-class = real-time-vbr


admin> set sustainable-rate-kbits-per-sec = 512

admin> set max-burst-size = 2048

admin> writeATM-QOS/rt-vbr1 written

admin> list[in ATM-QOS/rt-vbr1]contract-name* = rt-vbr1qos-class = real-time-vbrpeak-rate-kbits-per-sec = 1024peak-cell-rate-cells-per-sec = 2415sustainable-rate-kbits-per-sec = 512sustainable-cell-rate-cells-per-sec = 1207cell-delay-variation-tolerance = 20max-burst-size = 2048aal-type = aal-5early-packet-discard = yespartial-packet-discard = yestag-or-discard = discard

The connection that applies this contract will initially be established at a bit rate of 512 Kbps. It can then accommodate bursts of up to 2048 cells at double its bit rate (up to 1 Mbps).



Example of an Available Bit Rate (ABR) contract

ABR service makes use of flow control mechanisms to allocate bandwidth fairly in response to network conditions. For details about the mechanisms used, see “Flow control” on page 5-4. The following parameters are relevant to ABR traffic:

[in ATM-QOS/""]contract-name* = ""qos-class = abrpeak-rate-kbits-per-sec = 10peak-cell-rate-cells-per-sec = 23aal-type = aal-5early-packet-discard = yespartial-packet-discard = yestag-or-discard = discard

The following commands define a contract for ABR traffic with a peak bit rate of 2 Mbps:

admin> new atm-qos abr1ATM-QOS/abr1 read

admin> set qos-class = abr


admin> writeATM-QOS/abr1 written

admin> list[in ATM-QOS/abr1]contract-name* = abrqos-class = abrpeak-rate-kbits-per-sec = 2048peak-cell-rate-cells-per-sec = 4830sustainable-rate-kbits-per-sec = 2048sustainable-cell-rate-cells-per-sec = 4830cell-delay-variation-tolerance = 20max-burst-size = 20aal-type = aal-5early-packet-discard = yespartial-packet-discard = yestag-or-discard = discard

The end-system whose profile applies this contract will initially request a bit rate of 2 Mbps. It might obtain this initial bit rate or a lower one, depending on network conditions. If the network later becomes more heavily loaded, the source system will receive instructions to lower its transmission rate.


6Configuring ATM Circuits

An ATM circuit is a point-to-point switch-through ATM connection established in the Stinger unit. Circuit traffic is switched at OSI Layer 2. Currently, there is no Layer-3 routing of user data for ATM circuits.

A circuit has two sides, which means it has two physical interfaces in the unit. To configure a circuit, you identify the two sides of the circuit by specifying the nailed-group number of each of the two physical interfaces. The which command displays the nailed group assigned to any physical interface in the unit.

The most widely used circuits are LIM-to-trunk circuits for DSLAM operations. However, LIM-to-LIM, and trunk-to-trunk circuits are also supported.

Figure 6-1. ATM circuits on LIM and trunk interfaces

Each LIM physical interface connects to a single CPE. However, that physical connection can support up to eight circuits. Configuring more than one PVC on a LIM port enables the system to manage different types of ATM traffic at the same time for the same subscriber.

Overview of ATM circuit settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

Examples of ATM circuits using VC switching. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

Example of VP switching configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-11

Checking the status of an ATM circuit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-15

ATM switches DSL Terminator

LIM-to-trunk circuit

LIM-to-LIM circuit

Trunk-to-trunk circuit


Configuring ATM CircuitsOverview of ATM circuit settings

Overview of ATM circuit settingsYou configure both sides of an ATM circuit in one Connection or RADIUS profile. ATM circuits are not password authenticated. They must specify ATM-Circuit encapsulation to make use of the system’s circuit management software.

When the system establishes an ATM circuit, it places a call on one side of the circuit and then uses its circuit management software to handle the switch-through to the other side of the circuit. In the descriptions that follow, the side on which the call is placed is referred to as the first side of the circuit, which is built using the settings in the ATM-Options subprofile. The other side is referred to as the second side of the circuit, which is built using the settings in the ATM-Connect-Options subprofile.

ATM circuits can use either VC or VP switching. However, with the current software version, VP switching is not supported for RADIUS profiles. VP switching is also not supported between LIM interfaces. For an introduction to VC and VP switching operations, see “Stinger switching operations” on page 1-2.

The following local Connection parameters (shown with default settings) are used to specify ATM circuits:

[in CONNECTION/""]station* = ""active = noencapsulation-protocol = atm-circuit

[in CONNECTION/"":atm-options]atm1483type = aal5-llcvpi = 0vci = 35nailed-group = 0vp-switching = no

[in CONNECTION/"":atm-connect-options]atm1483type = aal5-llcvpi = 0vci = 35nailed-group = 0vp-switching = no

[in CONNECTION/"":atm-qos-options]usr-up-stream-contract = ""usr-dn-stream-contract = ""

[in CONNECTION/"":ip-options]ip-routing-enabled = yes

Parameter Specifies

Station Name of the PVC. Because a subscriber can have up to eight configured PVCs, a common convention is to use the name of the subscriber device followed by a number (for example, bijal-1, bijal-2, and so forth).

Active Enable/disable the profile for active use.

Encapsulation-Protocol Encapsulation protocol to use for the circuit. Must be set to atm-circuit (the default) for circuits.



ATM-Options: ATM1483type

Not used for circuit configurations. (See Chapter 7, “Configuring Terminating ATM Connections.”)

ATM-Options:VPI VPI for the first side of the circuit. For DSLAM operations, the first side of the circuit must be the subscriber side (a LIM port). The default zero value means the system uses VC switching. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6.

ATM-Options:VCI VCI for the first side of the circuit. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6.

ATM-Options:Nailed-Group

Nailed-group number of the interface used by the first side of the circuit. (For a command that displays a port’s nailed-group number, see “Identifying a circuit’s physical interfaces” on page 6-5.)

ATM-Options:VP-Switching

Enable/disable VP switching for the first side of the circuit. The default value is no. If set to yes, you must enable VP switching on both sides of the circuit and specify a valid VPI number for each side. VP switching is not supported for LIM-to-LIM circuits. For related information, see “Assigning valid VPI/VCI pairs” on page 6-6.

ATM-Connect-Options:ATM1483type

Not used for circuit configurations. (See Chapter 7, “Configuring Terminating ATM Connections.”)

ATM-Connect-Options:VPI

VPI for the second side of the circuit. For DSLAM operations, the second side of the circuit must be trunk-side. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6.

ATM-Connect-Options:VCI

VCI for the second side of the circuit. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6.

ATM-Connect-Options:Nailed-Group

Nailed-group number of the physical interface used by the second side of the circuit. (For a command that displays a port’s nailed-group number, see “Identifying a circuit’s physical interfaces” on page 6-5.)

ATM-Connect-Options:VP-Switching

Enable/disable VP switching for the second side of the circuit. The default value is no. If set to yes, you must enable VP switching on both sides of the circuit and specify a VPI number for each side. VP switching is not supported for LIM-to-LIM circuits.VP switching is not supported for LIM-to-LIM circuits. For related information, see “Assigning valid VPI/VCI pairs” on page 6-6.

ATM-QOS-Options:Usr-Up-Stream-Contract

Traffic contract name for upstream traffic on the circuit: a text string of up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

ATM-QOS-Options:Usr-Dn-Stream-Contract

Traffic contract name for downstream traffic on the circuit: a text string of up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

IP-Options:IP-Routing-Enabled

Enable/disable IP routing for the interface. IP routing should be disabled for circuit connections.

Parameter Specifies



RADIUS profile settings

With the current software version, VP switching is not supported in RADIUS profiles. Following is a sample RADIUS profile for an ATM circuit:

permconn-ST-1 Password = "ascend"

Service-Type = Outbound,

Framed-Protocol = ATM-CIR, User-Name = "bijal-1",

Ascend-Route-IP = Route-IP-No,

Ascend-ATM-Group = 112,

Ascend-ATM-Vpi = 0, Ascend-ATM-Vci = 100,

Ascend-ATM-Connect-Group = 171,

Ascend-ATM-Connect-Vpi = 0,

Ascend-ATM-Connect-Vci = 200, Ascend-QOS-Upstream = "qos1",

Ascend-QOS-Downstream = "qos2"

Attribute Value

User-Name (1) Name of the PVC. Because a subscriber can have up to eight configured PVCs, a common convention is to use the name of the subscriber device followed by a number (for example, bijal-1, bijal-2, and so forth).

Framed-Protocol (7) Encapsulation protocol to use for the circuit. Must be set to ATM-CIR for a circuit definition.

Ascend-Route-IP (228) Enable/disable IP routing for the interface. IP routing must be disabled for circuit connections.

Ascend-ATM-Group (64) Nailed-group number of the interface used by the first side of the circuit. For a command that displays a port’s nailed-group number, see “Identifying a circuit’s physical interfaces” on page 6-5.

Ascend-ATM-Vpi (94) VPI for the first side of the circuit. For DSLAM operations, the first side of the circuit must be the subscriber side (a LIM port). The default zero value means the system uses VC switching. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6. VP switching is not currently supported in RADIUS profiles.

Ascend-ATM-Vci (95) VCI for the first side of the circuit. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6.

Ascend-ATM-Connect-Group (63)

Nailed-group number of the physical interface used by the second side of the circuit. For a command that displays a port’s nailed-group number, see “Identifying a circuit’s physical interfaces” on page 6-5.

Ascend-ATM-Connect-Vpi (61)

VPI for the second side of the circuit. For DSLAM operations, the second side of the circuit must be the trunk side. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6. VP switching is not currently supported in RADIUS profiles.

Ascend-ATM-Connect-Vci (62)

VCI for the second side of the circuit. For a discussion of valid values, see “Assigning valid VPI/VCI pairs” on page 6-6.



How circuits are established

A Stinger unit makes only one call in establishing an ATM circuit. It places the call on the first side of the circuit, which is built with the settings in the ATM-Options subprofile. After the system has placed the call to establish the initial nailed connection, switch-through to the second side of the circuit is handled internally. The unit generates Call-Info log information only for the side of the circuit on which it placed the call.

For LIM-to-trunk circuits (DSLAM), the call must be placed on the LIM port rather than the trunk port. For LIM-to-LIM and trunk-to-trunk circuits, either port can be used for the call that initiates a circuit.

Identifying a circuit’s physical interfaces

The which command enables administrators to look up the nailed group associated with the ports to be used for an ATM connection. The command has the following syntax:

admin> help whichtranslate between nailed group and actual physical port

usage: which [-p|n] port|groupexample: which -p 55or: which -n { 1 3 7 }

When used with the -p flag and a nailed-group number, the command displays the port address associated with that number. When used with the -n flag and a port address, the command displays the nailed group assigned to that port.

For examples of how to use the which command to find a port’s nailed-group assignment for use in an ATM connection, see “Examples of ATM circuits using VC switching” on page 6-7. You can also use the which command to determine which port is in use when you have the nailed-group assignment of a Connection profile. For example, if the circuit uses nailed-group 296:

admin> which -p 296The port corresponding to nailed group 296 is: { shelf-1 slot-6 46 }

If the argument specifies a slot that is not populated, or a nailed-group that is not assigned, the command returns a message that the number was not found. For example:

admin> which -p 43The port corresponding to nailed group 43 is:NONE!

Ascend-QOS-Upstream (59)

Traffic contract name for upstream traffic on the circuit: a text string up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

Ascend-QOS-Downstream (60)

Traffic contract name for downstream traffic on the circuit: a text string up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

Attribute Value



If more than one port has the same nailed group associated with it (which is illegal), the which command returns all the ports that have this nailed group. Consequently, the command provides a convenient way to find duplicate nailed-groups. For example:

admin> read sdsl {1 6 46}SDSL/{ shelf-1 slot-6 46 } read

admin> set line-config nailed-group = 801


admin> which -p 801The port corresponding to nailed group 801 is:{ shelf-1 slot-6 46 } { shelf-1 trunk-module-1 1 }

Duplicate nailed-group assignments can occur only when the administrator changes default nailed-group numbers. To correct the problem, change the nailed-group assignments in one or more profiles, and then verify by using the which command again.

Assigning valid VPI/VCI pairs

Administrators must be sure to use a VPI/VCI pair that is within the valid range assigned to both ports of a circuit. A VPI/VCI assignment that is not compatible with the port’s configuration causes the connection to fail with an error message.

VPIs and VCIs on LIM slots

On a LIM slot, the default range of valid VPIs is from 0 to 15, and the default range of valid VCIs is from 32 to 127. Administrators can change these defaults, as described in “Configuring VPI/VCI ranges for LIM slots” on page 3-5.

Each LIM port allocates one VPI for VP switching—by default, VPI 15 is allocated. Administrators can allocate a different VPI for VP switching, as described in “VPI used for VP switching on SDSL port” on page 3-8 or “VPI used for VP switching on the AL-DMT port” on page 3-12.

For a VC-switching circuit, the subscriber-side VPI setting can use any VPI other than the one allocated for VP switching, and the VCI setting must specify a VCI within the valid range for the slot.

For a VP-switching circuit, the subscriber-side VPI setting must use the VPI allocated for VP switching, and the VCI setting must specify a VCI within the valid range for that slot, even though the VCI number is not used for switching purposes.

VPIs and VCIs on trunk ports

On a trunk port, the default range of valid VPIs is from 0 to 255 (with 0 reserved for VC switching), and the default range of valid VCIs is from 32 to 8191. Administrators can change these defaults, as described in “VPI/VCI allocation for trunk ports” on page 4-5.

Each trunk port allocates VPI 0 for VC switching. Administrators can allocate additional VPIs for VC switching, as described in “VPI/VCI allocation for trunk ports” on page 4-5.

Configuring ATM CircuitsExamples of ATM circuits using VC switching


For a VC-switching circuit, the trunk-side VPI setting must use one of the VPIs reserved on the trunk port for VC switching (for example, VPI 0), and the VCI setting must specify a VCI within the valid range for the trunk port.

For a VP-switching circuit, the trunk-side VPI setting can use any VPI other than the VPIs allocated for VC switching. There is no restriction for VP-switched circuits on the VCI number, and there is no restriction on the number of VCCs switched across a virtual path.

Applying traffic contracts

The way the system handles and prioritizes traffic for a circuit is determined by the traffic contract or contracts applied in the circuit’s Connection or RADIUS profile. For some circuits, the requirements differ for upstream and downstream traffic. For example, a circuit used to receive video transmissions might have constant bit-rate downstream requirements and relatively few upstream requirements. Administrators control these differing requirements by applying two traffic contracts in the profile, one for upstream and another for downstream traffic. (For details about defining traffic contracts and the effects of applying them to a data stream, see Chapter 5, “Specifying Traffic Contracts.”)

Examples of ATM circuits using VC switchingWhen configuring a DSLAM ATM circuit, the user (LIM) side of the circuit must be defined in the ATM-Options subprofile, and the network (trunk) side of the circuit must be defined in the ATM-Connect-Options subprofile. For LIM-to-LIM or trunk-to-trunk circuits, there is no restriction on which side of the circuit must be specified in the ATM-Options subprofile.(For related information, see “How circuits are established” on page 6-5.)

Configuring a LIM-to-trunk circuit (DSLAM operations)

Figure 6-2 shows a sample configuration in which a Stinger unit receives ATM traffic from an ADSL subscriber and switches it onto a high-speed ATM backbone (DSLAM):

Figure 6-2. LIM to trunk circuit (DSLAM operations)

For DSLAM operations, the first side of the circuit (the side specified in the ATM-Options subprofile) must be the subscriber side. The following commands create a local Connection profile and assign both of the ATM circuit’s VCI numbers:

admin> new connection simon-1CONNECTION/simon-1 read

ATM

DSL-CELL-50A



admin> set active = yes

admin> set encapsulation-protocol = atm-circuit

admin> set ip-options ip-routing-enabled = no

admin> set atm-options vci = 32

admin> set atm-connect-options vci = 33

The following commands display the nailed-group number of an AL-DMT interface (slot-4 port-5) and assign it to the first side of the circuit:

admin> which -n {1 4 5}

Nailed group corresponding to port { shelf-1 slot-4 5 } is 155

admin> set atm-options nailed-group = 155

The following commands display the nailed-group number of an OC3-ATM interface (trunk-module 1, port 2) and assign it to the second side of the circuit:

admin> which -n {1 17 2}

Nailed group corresponding to port { shelf-1 trunk-module-1 2 } is 802

admin> set atm-connect-options nailed-group = 802

The following commands assign an upstream and downstream traffic contract and write the profile:

admin> set atm-qos-options usr-up-stream-contract = abr-1

admin> set atm-qos-options usr-dn-stream-contract = cbr-1

admin write

CONNECTION/simon-1 read

Following is a comparable circuit definition in a RADIUS profile:



Framed-Protocol = ATM-CIR,

User-Name = "simon-1",


Ascend-Route-IP = Route-IP-No,

Ascend-ATM-Vpi = 0,

Ascend-ATM-Vci = 32,

Ascend-ATM-Connect-Vpi = 0,

Ascend-ATM-Connect-Vci = 33,

Ascend-ATM-Connect-Group = 802,

Ascend-QOS-Upstream = "abr-1",

Ascend-QOS-Downstream = "cbr-1"

Configuring a trunk-to-trunk circuit

Figure 6-3 shows a sample configuration in which a Stinger unit receives ATM traffic from an ATM switch on one trunk interface and switches it through to a switch on another trunk interface.



Figure 6-3. Trunk-to-trunk circuit

For a trunk-to-trunk circuit, the system can place the call on either interface, so either side of the circuit can be specified in the ATM-Options subprofile. The following commands create a local Connection profile for the trunk-to-trunk circuit:

admin> new connection kai-1CONNECTION/kai-1 read




The following commands assign VCI numbers to each side of the circuit:



The following commands display the nailed-group number of a trunk interface (trunk-module 1, port 1) and assign it to the first side of the circuit:

admin> which -n {1 17 1}Nailed group corresponding to port { shelf-1 trunk-module-1 1 } is 801


The following commands display the nailed-group number of a different trunk interface (trunk-module 2, port 2) and assign it to the second side of the circuit:





admin> set atm-qos-options usr-dn-stream-contract = abr-1

admin writeCONNECTION/kai-1 read


permconn-ST-4 Password = "ascend" Service-Type = Outbound, Framed-Protocol = ATM-CIR,

ATM switches



User-Name = "kai-1", Ascend-ATM-Group = 801, Ascend-Route-IP = Route-IP-No, Ascend-ATM-Vpi = 0, Ascend-ATM-Vci = 100, Ascend-ATM-Connect-Vpi = 0, Ascend-ATM-Connect-Vci = 200, Ascend-ATM-Connect-Group = 852, Ascend-QOS-Upstream = "abr-1", Ascend-QOS-Downstream = "abr-1"

Configuring a LIM-to-LIM circuit

Figure 6-3 shows a sample configuration in which a Stinger unit receives ATM traffic from a CellPipe unit on one SDSL interface and switches it through to another SDSL interface.

Figure 6-4. LIM-to-LIM circuit

For a LIM-to-LIM circuit, the system can place the call on either interface, so either side of the circuit can be specified in the ATM-Options subprofile.

Note: VP switching is not supported for LIM-to-LIM circuits.

The following commands create a local Connection profile and assign both of the ATM circuit’s VCI numbers:

admin> new connection jintao-1CONNECTION/jintao-1 read






The following commands display the nailed-group number of an SDSL interface (slot 2, port 5) and assign it to the first side of the circuit:

admin> which -n {1 2 5}Nailed group corresponding to port { shelf-1 slot-2 5 } is 55


ATM

DSL-CELL-50S

DSL-CELL-50S

Configuring ATM CircuitsExample of VP switching configuration


The following commands display the nailed-group number of another SDSL interface (slot 10, port 3) and assign it to the second side of the circuit:

admin> which -n {1 10 3}Nailed group corresponding to port { shelf-1 slot-10 3 } is 803



admin> set atm-qos-options usr-up-stream-contract = cbr-1

admin> set atm-qos-options usr-dn-stream-contract = cbr-1

admin writeCONNECTION/jintao-1 read


permconn-ST-5 Password = "ascend" Service-Type = Outbound, Framed-Protocol = ATM-CIR, User-Name = "jintao-1", Ascend-ATM-Group = 55, Ascend-Route-IP = Route-IP-No, Ascend-ATM-Vpi = 0, Ascend-ATM-Vci = 42, Ascend-ATM-Connect-Vpi = 0, Ascend-ATM-Connect-Vci = 43, Ascend-ATM-Connect-Group = 803, Ascend-QOS-Upstream = "cbr-1", Ascend-QOS-Downstream = "cbr-1"

Example of VP switching configurationFigure 6-5 shows two Stinger units. The unit labeled Stinger-B is concentrating multiple incoming VCCs to a single outgoing VPC that uses VPI 5 with a range of VCIs starting with VCI 32.

The unit labeled Stinger-A is performing two VP switching operations. One VP switching operation is a LIM-to-trunk circuit from CPE-1 to the Telco switch using VPI 20. Another VP switching operation is a trunk-to-trunk circuit on which the unit switches the VPC from Stinger-B to the Telco switch using VPI 10.



Figure 6-5. Example of VP switching and VC switching

Example of Stinger-A configuration (VP switching)

The following examples show how to configure the LIM port, trunk ports, and Connection profiles in the command-line interface of the unit labeled Stinger-A.

Sample LIM port configuration

The VPI/VCI ranges for LIM slots must be configured to support the VPI selected for VP switching on LIM ports (see “Configuring VPI/VCI ranges for LIM slots” on page 3-5). The following commands configure a LIM port on Stinger-A for VP switching using VPI 3:



admin> set line-config vp-switching = 3


Sample trunk port configuration

The following commands enables the first port of the first TM and the second port of the second TM on Stinger-A. The profiles retain their default settings, which will allow the ports to use VP switching using any VPI other than zero:



CPE-1

Telco ABC

Stinger-A

Stinger-B

CPE-1

CPE-1CPE-2

CPE-1CPE-3

VPI = 3

CPE-1CPE-1 VPI = 8, VCI = 35

VPI = 8, VCI = 35

VPI = 8, VCI = 35

VPI = 5, VCI = 32

VPI = 5, VCI = 33

VPI = 5, VCI = 34

(In)

(Out)

VPI = 3 (In), VPI = 20 (Out)

VPI = 5 (In), VPI = 10 (Out)

VC switching

VP switching







Sample CPE Connection profile

The following commands create a Connection profile for the CPE-1 connection to Stinger-A:

admin> new connection cpe-1CONNECTION/cpe-1 read




admin> set atm-options vpi = 3


admin> set atm-options vp-switching = yes

admin> set atm-connect-options vpi = 20


admin> set atm-connect-options vp-switching = yes

admin writeCONNECTION/cpe-1 read

The first side of the circuit uses the SDSL port in slot 5, port 5. That port has the nailed group 155, which has been configured for VP switching using VPI 3. The second side uses the first trunk port (nailed-group 801) with VPI 20.

Note: The CPE connection must use a VCI within the valid VCI range configured for the LIM port, even when VP switching is used. However, the value is not used for switching.

Sample trunk-to-trunk circuit for traffic from Stinger-B

The following commands create a Connection profile for the trunk-to-trunk connection from Stinger-B to the Telco switch:

admin> new connection stinger-bCONNECTION/stinger-b read






admin> set atm-options vp-switching = yes





admin> set atm-qos-options usr-up-stream-contract = ubr-1

admin> set atm-qos-options usr-dn-stream-contract = ubr-1

admin writeCONNECTION/stinger-b read

The first side of the circuit uses the second port of the second TM (nailed-group 852) with VPI 5. The second side uses the first port of the first TM (nailed-group 801) with VPI 20.

Example of Stinger-B CPE configurations (VC switching)

The following commands create three Connection profiles for the CPEs connecting to Stinger-B in Figure 6-5:


























Configuring ATM CircuitsChecking the status of an ATM circuit










Checking the status of an ATM circuitEach side of an ATM circuit is VCC. The system creates an ATMVCC-Stat profile for each VCC interface. These profiles provide status information about each side of a circuit. Administrators can read these profiles to check VCC status. Following are the relevant parameters (shown with sample settings):

[in ATMVCC-STAT/{ shelf-1 slot-10 47 0 35 }]vcc-ident* = { shelf-1 slot-10 47 0 35 }circuit-name = bijal-1current-state = vcc-data-transfervcc-type = connecting

The system also creates an ATMPVC-Stat profile for each configured ATM circuit. Following are the relevant parameters (shown with sample settings):

[in ATMPVC-STAT/bijal-1]circuit-name* = bijal-1pvc-type = connectingcurrent-state = pvc-data-transfervcc-members = [ { shelf-1 slot-10 47 0 35 } { shelf-1 slot-2 1 0 77 } ]

Parameter Indicates

VCC-Ident Unique VCC identifer, made up of the interface address (shelf, slot, and modem numbers), the VPI, and the VCI.

Circuit-Name Name of the PVC, which is the value of the Station parameter in a local profile or the User-Name attribute in a RADIUS profile.

Current-State Current state of the circuit. Value may be VCC-Inactive, VCC-Closed (the VCC exists but is closed), or VCC-Data-Transfer (the VCC is up and data may be transferred).

VCC-Type For an ATM circuit, the value of this parameter is always connecting (point-to-point connecting). The other possible value is terminating. (For details, see Chapter 7, “Configuring Terminating ATM Connections.”)


Configuring ATM CircuitsChecking the status of an ATM circuit

Parameter Indicates

Circuit-Name Name of the PVC, which is the value of the Station parameter in a local profile or the User-Name attribute in a RADIUS profile.

PVC-Type For an ATM circuit, the value of this parameter is always connecting (point-to-point connecting). The other possible value is terminating. (For details, see Chapter 7, “Configuring Terminating ATM Connections.”)

Current-State Current state of the circuit. Value may be PVC-Inactive, PVC-Closed (the PVC exists but is closed), or PVC-Data-Transfer (the PVC is up and data may be transferred).

VCC-Members The two member VCCs of the circuit (the two sides). Each side has a unique VCC identifer, made up of the interface address (shelf, slot, and modem numbers), the VPI, and the VCI.


7Configuring Terminating ATM Connections

A terminating ATM connection is a PVC that is not switched through at OSI Layer 2. Instead, it terminates in the Stinger system itself and is passed up to Layer 3 for further handling. As an example of a terminating routed IP connection, Figure 7-1 shows an administrative Telnet or SNMP login from a remote workstation (4.4.4.1/24) to the Stinger interface across an ATM trunk.

Figure 7-1. Terminating ATM connection

A terminating connection uses a single physical interface in a Stinger unit, such as the trunk interface shown in Figure 7-1. It is an ATM connection that carries IP packets, which are reassembled in the Stinger unit and then handled as regular IP traffic.

The profile for a terminating connection must specify the far-end IP address, and it can set a number of other routing-related values. The profile must also specify the ATM characteristics of the connection (for example, a VPI and VCI assignment, a nailed group, and the type of protocol multiplexing to use for the AAL5 layer).

Overview of ATM connection settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2

Example of a terminating connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4

Checking the status of an ATM connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7

ATM DSL Terminator

terminating connection

2.2.2.1/32

1.1.2.3/24

1.1.1.3/24 1.1.1.1/243.3.3.1/24

4.4.4.1/24


Configuring Terminating ATM ConnectionsOverview of ATM connection settings

Overview of ATM connection settingsA terminating ATM connection can be configured in a single Connection or RADIUS profile. The cells received on the connection are reassembled into IP packets. The connections are not password authenticated.

Local Connection profile settings

Following are the Connection profile parameters (shown with sample settings) for ATM terminating connections:

[in CONNECTION/mitch]

station* = mitch

active = yes

encapsulation-protocol = atm

[in CONNECTION/"":ip-options]

ip-routing-enabled = yes

remote-address = 3.3.3.3/24

[in CONNECTION/"":atm-options]

atm1483type = aal5-llc

vpi = 0

vci = 35

nailed-group = 171

vp-switching = no

[in CONNECTION/"":atm-qos-options]

usr-up-stream-contract = ""

usr-dn-stream-contract = ""

Parameter Specifies

Station Name of the far-end device.

Active Enable/disable the profile for active use.

Encapsulation-Protocol Encapsulation protocol to use for the connection. Must be set to atm for terminating connections.

IP-Options:IP-Routing-Enabled

Enable/disable IP routing for the interface. IP routing must be enabled (as it is by default) for terminating connections.

IP-Options:Remote-Address

IP address of the far-end device, which can include a subnet specification. If it does not include a subnet mask, the router software in the Stinger unit assumes a default subnet mask that is based on address class. (For related information, see “IP address syntax” on page 2-5.)

ATM1483type Method of multiplexing Layer-3 packets into ATM cells. Valid values are AAL5-LLC and AAL5-VC. (For details, see “AAL5 multiplexing” on page 7-4.)

ATM-Options:VPI VPI for the connection. For a discussion of valid VPI values, see “Assigning valid VPI/VCI pairs” on page 6-6.

ATM-Options:VCI VCI for the connection. For a discussion of valid VCI values, see “Assigning valid VPI/VCI pairs” on page 6-6.

Configuring Terminating ATM ConnectionsOverview of ATM connection settings


RADIUS profile settings

Following is a sample RADIUS profile for an ATM terminating connection:



Framed-Protocol = ATM-1483,

User-Name = "yossi",

Ascend-Route-IP = Route-IP-Yes,

Framed-IP-Address = 3.3.3.3,

Framed-IP-Netmask = 255.255.255.0,


Ascend-ATM-Vpi = 1,

Ascend-ATM-Vci = 33,

Ascend-QOS-Upstream = "qos1",

Ascend-QOS-Downstream = "qos2"

ATM-Options:Nailed-Group

Nailed-group number of the physical interface used by the connection. (For a command that displays a port’s nailed-group number, see “Identifying a circuit’s physical interfaces” on page 6-5.)

ATM-Options:VP-Switching

Not used for terminating connections. (See Chapter 6, “Configuring ATM Circuits.”)

ATM-QOS-Options:Usr-Up-Stream-Contract

Traffic contract name for upstream traffic on the connection: a text string of up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

ATM-QOS-Options:Usr-Dn-Stream-Contract

Traffic contract name for downstream traffic on the connection: a text string of up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

Parameter Specifies

Attribute Value

User-Name (1) Name of the far-end device.

Framed-Protocol (7) Encapsulation protocol to use for the connection. Must be set to ATM-1483 for terminating ATM connections. This setting corresponds to ATM AAL5 encapsulation as defined in RFC 1483.

Ascend-Route-IP (228) Enable/disable IP routing for the interface. IP routing must be enabled for terminating connections (as it is by default).

Framed-IP-Address (8) IP address of the calling device.

Framed-IP-Netmask (9) Subnet mask of the caller’s address. If you do not specify a subnet mask, the router assumes a default subnet mask that is based on address class. (For related information, see “IP address syntax” on page 2-5.)

Ascend-ATM-Group (64) Nailed-group number of the physical interface used by the connection. (For a command that displays a port’s nailed-group number, see “Identifying a circuit’s physical interfaces” on page 6-5.)


Configuring Terminating ATM ConnectionsExample of a terminating connection

IP information

When a Stinger unit starts up, it creates a routed interface for terminating connections specified in local Connection profiles. For those defined in RADIUS profiles, a Stinger unit creates a routing interface when a session becomes active.

The IP address of the far-end device is the minimum IP information that must be supplied in the profile. The default settings for the IP-Options subprofile enable IP routing. They also enable Van Jacobsen header compression and turn off RIP, which is appropriate for many IP connections. You can change these defaults, or set a variety of routing and service parameters (which are described in the Stinger Reference Guide).

If the far-end device specifies the Stinger unit’s soft interface IP address as its destination, the connection will be robust even if the unit switches over to its redundant controller. For information about the unit’s soft interface, see “Defining the soft interface for fault tolerance” on page 2-7.

AAL5 multiplexing

Stinger units support the two encapsulation methods for carrying routed PDUs in the payload field of ATM Adaptation Layer (AAL) type 5, which are defined in RFC 1483, Multiprotocol Encapsulation over ATM Adaptation Layer 5.

The AAL5-LLC encapsulation method multiplexes multiple protocols on a single ATM virtual circuit. Each protocol is identified in the 802.2 LLC header of the packet. This is the default method for Stinger connections and is recommended for the current software version, in which only PVCs are supported.

The AAL5-VC method carries each protocol on a separate ATM virtual circuit (in effect, it multiplexes the circuits rather than the individual protocols). This method is sometimes used in private networks, in which VC creation is very economical.

Example of a terminating connectionA Stinger unit brings up a PVC to the far-end unit on the basis of the VPI-VCI assignment and other ATM parameters. For an IP-routed connection, it then validates the far-end device’s IP

Ascend-ATM-Vpi (94) VPI for the connection. For a discussion of valid VPI values, see “Assigning valid VPI/VCI pairs” on page 6-6.

Ascend-ATM-Vci (95) VCI for the connection. For a discussion of valid VCI values, see “Assigning valid VPI/VCI pairs” on page 6-6.

Ascend-QOS-Upstream (59)

Traffic contract name for upstream traffic on the connection: a text string of up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

Ascend-QOS-Downstream (60)

Traffic contract name for downstream traffic on the connection: a text string of up to 30 characters. For details, see “Applying traffic contracts” on page 6-7.

Attribute Value



address. After the connection has been established, users can Telnet across the connection or access the Stinger from an SNMP management station.

In the following example, a Stinger unit has a Connection or RADIUS profile for the DSLTNT unit, and vice versa. The ATM PVC between the two units allows an administrator at the DSLTNT side to connect to the Stinger unit, where he or she can authenticate the appropriate User profile for an administrative session.

Figure 7-2. Terminating connection from DSLTNT

Figure 7-2 shows the IP addresses assigned to the Stinger unit’s primary CM (1.1.1.1/24) and secondary CM (1.1.1.2/24), and a soft interface address of 1.1.1.128/24. Many sites use the soft interface as the Stinger unit’s destination IP address because it enables the profile to reach the unit regardless of which CM is acting as the primary. For information about the soft interface, see “Defining the soft interface for fault tolerance” on page 2-7.

Sample Stinger configuration

In Figure 7-2, the connection from the Stinger to the DSLTNT unit uses an OC3-ATM interface. The following commands create a local Connection profile and specify the IP address of the DSLTNT unit:

admin> new connection dsltnt-1CONNECTION/dsltnt-1 read


admin> set encapsulation-protocol = atm

admin> set ip-options remote-address = 3.3.3.3/24

The following commands specify the AAL5 multiplexing method and assign VCI 101 to the link:

admin> set atm-options atm1483type = aal5-llc


The following commands display the nailed-group number of the OC3 trunk interface (trunk-module-1 port-2) and assign it to the PVC:



ATM

DSLTNT

Management workstation

1.1.1.1/243.3.3.3/24

1.1.1.2/24

Soft interface address: 1.1.1.128/24





admin> set atm-qos-options usr-dn-stream-contract = abr-1

admin writeCONNECTION/dsltnt-1 read

Following is a comparable definition in a RADIUS profile:

permconn-ST-1 Password = "ascend" Service-Type = Outbound, Framed-Protocol = ATM-1483, User-Name = "dsltnt-1", Framed-IP-Address = 3.3.3.3, Framed-IP-Netmask = 255.255.255.0, Ascend-ATM-Group = 802, Ascend-Route-IP = Route-IP-Yes, Ascend-ATM-Vci = 101 Ascend-QOS-Upstream = "abr-1", Ascend-QOS-Downstream = "abr-1"

Sample far-end DSLTNT configuration

In this example, the DSLTNT unit has a DS3 interface to the ATM network. The following command displays the nailed-group value assigned to the DS3-ATM interface used for this connection:

admin> get atm-ds3 {1 7 1} line-config nailed-group[in ATM-DS3/{ shelf-1 slot-7 1 }:line-config]nailed-group = 70

The following commands on the DSLTNT unit configure a Connection profile for the Stinger connection using the Stinger unit’s soft interface address and VCI 101:

admin> get connection stinger-1CONNECTION/stinger-1 read


admin> set encapsulation = atm

admin> set ip-options remote-address = 1.1.1.128/24

admin> set telco-options call-type = ft1

admin> set telco-options nailed-group = 70


admin> writeCONNECTION/stinger-1 written

Note: Because the Connection profile specifies the soft interface address as the remote address, the terminating connection will be briefly dropped if the primary CM fails, and then will be reestablished within a few seconds using the new primary CM.

For more details about creating Connection profiles on DSLTNT units, see the DSLTNT documentation.

Configuring Terminating ATM ConnectionsChecking the status of an ATM connection


Checking the status of an ATM connectionThe system creates an ATMVCC-Stat profile for each PVC. The profiles provide status information about the Virtual Channel Connection (VCC) interface. The system also creates an ATMPVC-Stat profile for each Permanent Virtual Circuit. Administrators can read the profiles to check connection status. Following are the relevant parameters (shown with sample settings):

[in ATMVCC-STAT/{ shelf-1 slot-17 1 0 35 }]vcc-ident* = { shelf-1 slot-17 1 0 35 }circuit-name = bijal-1current-state = vcc-data-transfervcc-type = terminating

[in ATMPVC-STAT/bijal-1]circuit-name* = bijal-1pvc-type = terminatingcurrent-state = pvc-data-transfervcc-members = [ { shelf-1 slot-17 1 0 35 }]

For terminating connections, the value of the VCC-Type and PVC-Type parameters is always terminating, and VCC-Members always specifies a single member. The rest of the parameters in the profiles are the same for terminating PVCs as for ATM circuits. For details, see “Checking the status of an ATM circuit” on page 6-15.

Stinger Configuration Guide Index-1

Index

A

AAL type, 5-2activity, system, 1-5admin login

default password, 2-2recommended password change, 2-3

AL-DMTbandwidth, 3-3BERT, 3-23configuration overview, 3-10interface configuration, 3-18latency channels, 3-12physical status, 3-23profiles, 3-9status, 3-23valid range of VPIs and VCIs, 3-5VPI for VP switching, 3-12

AL-DMT profilelatency channel settings, 3-14line activation settings, 3-10noise margin settings, 3-16power spectral density, 3-13power-level settings, 3-13rate-adaptive mode settings, 3-12

AL-DMT-Stat profile, 3-23physical status, 3-23statistics on active line, 3-25

ATMAAL5 multiplexing, 7-4ABR traffic, explicit rate marking, 5-5Adaptation Layer type, 5-2cell delay variation tolerance, 5-2circuits and connections, described, 1-5circuits. See circuitscongestion management, 5-5EFCI, 5-4explicit rate marking, 5-5flow control, 5-5packet discard, 5-3peak cell rate, 5-2Resource Management (RM) cells, 5-4service categories, explained, 5-4sustainable cell rate, 5-2terminating connections. See connectionstraffic contracts, applied to PVC, 6-7traffic contracts, examples of, 5-5

traffic contracts, introduced, 1-4traffic contracts, LIMs required, 5-1traffic policing, 5-4traffic shaping, 5-4VC switching, 1-2, 4-6, 6-7VP switching, 1-2, 3-8, 3-12, 6-11VPI/VCI allocation, 4-6

ATM framer, 4-11settings, 4-13status, 4-15, 4-17

ATM-Configbandwidth, 3-3VPI/VCI ranges, 3-5

ATM-Config profile, 3-3ATMPVC-Stat profile, 6-15ATM-QOS profile

parameters marked not-available, 5-1QoS class, 5-3settings related to traffic policing and shaping, 5-4

ATMtrunks command, 4-9, 4-13attributes, RADIUS, 6-4, 7-3automatic trunk port sparing, 4-2available bit rate (ABR), 5-3

B

backups, 1-3bandwidth

configuring, example of, 3-4diagram of unit, 3-3guaranteed, maximum upstream, 3-4LIMs, 3-3

bandwidth status, 3-26Bandwidth-Stats profile, 3-26BERT, AL-DMT lines, 3-23BERT, SDSL lines, 3-22bit sizes, VPI/VCI on slots, 3-6

C

cell delay variation tolerance, 5-2

Index-2 Stinger Configuration Guide

IndexD

circuitsassigning to physical ports, 6-5configuration settings, 6-2defined, 6-1DSLAM example, 6-7how Stinger establishes, 6-5multiple on LIM interfaces, 6-1nailed groups, for, 6-6RADIUS attributes, related, 6-4status, 6-15valid VPI/VCI pairs, 6-6VC switching, 6-7VP switching, 6-12See also connections, terminating

clock source, 1-4, 4-3command help, 1-6command-line interface, introduced, 1-5commands

ATMtrunks, 4-9, 4-13Dir, 2-2DMTAL, 3-12List, 4-3listing, 1-5Ping, 2-9Read and Write, 2-7SDSL, 3-8Set, 2-7Set, for complex fields, 4-2STATUS, 1-6Which, 6-5

complex fields, how to set, 4-2configuration overview, 1-3configuration, initial serial port login, 2-1congestion management, 5-5Connection profile

ATM circuits, 6-2settings for terminating connections, 7-2

connections, terminatingAAL5 multiplexing, 7-4configuring, examples of, 7-5defined, 7-1IP information required, 7-4minimal configuration, 7-1multiplexing protocols onto ATM, 7-4RADIUS attributes, related, 7-3status, 7-7Stinger to DSLTNT, 7-5See also circuits

constant bit-rate (CBR), 5-3control modules

configuration overview, 1-3, 2-1interface-independent address, 2-8primary and secondary, defined, 2-1redundancy settings, 2-12switchover from primary, 2-12

D

default nailed groups, 3-8, 4-9, 4-13default route, IP, 2-8defaults for initial admin login, 2-2Diag Port. See serial portDMT line codes, 3-11DMT. See AL-DMTDMTAL command, 3-12downstream traffic, defined, 1-1DS3-ATM

clock source, 4-4clock source settings, 4-4framing formats, 4-10sparing, 4-2status, 4-15trunk port sparing, 4-1valid VPIs and VCIs, 4-6VPIs used for VC switching, 4-6VPI/VCI range on, 4-6

DS3-ATM profileconfiguring, example of, 4-10settings, 4-8

DS3-ATM-Stat profileline errors, 4-15physical interface status, 4-15

DSLAMcircuit configuration, 6-7circuit definitions, 6-1diagram of operations, 1-1

E

early packet discard (EPD), 5-3encapsulation protocols

ATM, 7-2, 7-3ATM-CIR, 6-4ATM-Circuit, 6-2

Ethernet portsIP addresses, 2-7logging into the Stinger, 2-9on control modules, 1-3

Explicit Forward Congestion Indica, 5-5Explict Rate Marking, 5-5External-Auth profile, 2-10

F

fast channel, 3-14fault tolerance

control module switchover, 2-12

IndexI


fault tolerance (continued)controller IP address, 2-7manual LIM sparing, 3-1trunk port sparing, 4-1

flash memorybackups, 1-3upgrades, 1-6

flow control, 5-5framing formats, DS3, 4-10

I

interleaved channel, 3-14delay settings, 3-15

IPaddresses for CM Ethernet ports, 2-7default route, 2-8host routes, 2-6level of support, 1-1minimal configuration, 2-5soft interface address, 2-8subnet notation, 2-6

IP-Global profile, 2-4IP-Interface profile, 2-7IP-Route profiles, 2-8

J

jitter threshold of applications, 5-2

L

latencyfast and interleaved, 3-14

LIM sparing, 3-1LIMs, 3-26

ADSL. See AL-DMTallocating total bandwidth, 3-3ATM QoS, required for, 5-1configuration overview, 1-3displaying nailed group for port, 6-5displaying port for nailed group, 6-5manual sparing, 3-1multiple PVCs on, 6-1nailed-groups, 6-6SDSL. See SDSLsparing, 3-1status, 3-20valid VPIs and VCIs, 3-5

LIM-Sparing-Config profile, 3-1LIM-Sparing-Status profile, 3-26

List command, 4-3logging into the Stingert, 2-1

M

management features, 1-5manual trunk port sparing, 4-1maximum burst size (MBS), 5-2

N

nailed groupsdefaults, 3-8detecting duplications, 6-6displaying for an interface, 6-5

netmask. See subnet masknoise margins, 3-16non-real-time variable bit rate (non-rt-VBR), 5-3

O

OC3-ATMclock source, 4-4clock-source settings, 4-4sparing, 4-2status, 4-17trunk port sparing, 4-1valid VPIs and VCIs, 4-6VPIs used for VC switching, 4-6VPI/VCI range on, 4-6

OC3-ATM profile, 4-11configuring, example of, 4-14physical interface settings, 4-13

OC3-ATM-Stat profile, 4-17peformance of SONET payload, 4-19physical interface status, 4-17

online help, commands, 1-6

P

partial packet discard (PPD), 5-3passwords

changing defaults, 2-3default for admin login, 2-2telnet, 2-4

peak cell rate (PCR), 5-2performance monitoring, SONET payload, 4-19permission levels, 1-5power, power spectral density, 3-13

Index-4 Stinger Configuration Guide

IndexQ

profilesAL-DMT, 3-11AL-DMT-Stat, 3-23ATM-Config, 3-3ATMPVC-Stat, 6-15ATM-QOS, 5-1Bandwidth-Stats, 3-26Connection

ATM circuits, 6-2ATM terminating connections, 7-2

DS3-ATM, 4-8DS3-ATM-Stat, 4-15External-Auth, 2-10IP-Global, 2-4IP-Interface, 2-7IP-Route, 2-8LIM-Sparing-Config, 3-1LIM-Sparing-Status, 3-26OC3-ATM, 4-11OC3-ATM-Stat, 4-17RADIUS permconn, 6-4, 7-3Redundancy, 2-13SDSL, 3-6SDSL-Stat, 3-20Serial, 2-2User, 2-3

PVCs. See circuits, connections

Q

Quality of Service contracts. See ATM

R

RADIUSATM-related VSAs, listed, 6-4example network setup, 2-11parameters, required, 2-10permconn profiles for circuits, 6-4permconn profiles for terminating connections, 7-3Stinger configuration for, 2-10VSA requirement, 1-6

rate-adaptive modeauotmatic, 3-13dynamic, described, 3-17operator-controlled, 3-13

real-time variable bit rate (real-time-VBR), 5-3redundancy

CM, 2-12configurable settings, 2-13control module operations, 2-12diagram of unit, 2-12LIM, 3-1

switchover from primary CM, 2-12trunk ports, 4-1

Redundancy profile, 2-13Resource Management (RM) cells, 5-4

S

SDSLbandwidth, 3-3BERT operations, 3-22data rates, 3-8default nailed groups, 3-8interface configuration, 3-9nailed groups, 3-8operational statistics, 3-21status, 3-20status, checking, 3-20valid range of VPIs and VCIs, 3-5VPI for VP switching, 3-8

SDSL command, 3-8SDSL profile

configuration, 3-9overview of settings, 3-7

SDSL-Stat profile, 3-20physical status, 3-20statistics on active lines, 3-21

securitychanging admin password, 2-3restricting serial port access, 2-2telnet password, 2-4

serial portinitial login to unit, 2-1restricting access, 2-2

Serial profile, 2-2Set command for complex fields, 4-2Slot VPI/VCI bit sizes, 3-6SNMP support, 1-6soft interface address, 2-8SONET payload, monitoring performance, 4-19sparing

LIMs, 3-1trunk modules, 4-1

sparing, LIMs, 3-1sparing, trunks, 4-1statistics

AL-DMT, 3-25SDSL, 3-21

statusAL-DMT interfaces, 3-23bandwidth, 3-26circuits, 6-15DS3-ATM, 4-15

IndexT


status (continued)LIM sparing, 3-26OC3-ATM, 4-17SDSL interfaces, 3-20terminating connections, 7-7trunk modules, 4-15

status windows, displaying, 1-6subnet notation, 2-6sustainable cell rate (SCR), 5-2switching. See VC switching, VP switchingsystem activity, tracking, 1-5system clock source, 4-3

T

telnet password, 2-4terminal emulation settings, required, 2-1terminating connections. See connections, terminatingTFTP, downloading files, 1-5timing subsystem, 1-4traffic contracts. See ATMtraffic policing, 5-5traffic shaping, 5-5trunk modules, 4-9, 4-13

displaying nailed group for port, 6-5displaying port for nailed group, 6-5overview, 1-4status, 4-15types supported, 4-7, 4-11

trunk port sparing, 4-1automatic mode, 4-2manual mode, 4-1, 4-3parameters, 4-2

trunk port status, 4-15, 4-17trunk port VPI/VCI assignments, 4-6trunk ports

nailed-groups, 6-6trunk ports, default nailed groups, 6-6

U

unspecified bit rate (UBR), 5-3upstream bandwidth, 3-4upstream traffic, defined, 1-1User profile, 2-3UTOPIA interface, 4-11

V

VC switchingdefined, 1-2LIM to LIM circuit, 6-10LIM to TM circuit, 6-7VPIs used on trunk ports, 4-6

vendor-specific attributesfor ATM circuits, 6-4for terminating connections, 7-3introduced, 2-9

VP switchingdefined, 1-2LIM port configuration, 6-12LIM to TM circuit, 6-13trunk to trunk circuit, 6-13VPI used on LIMs, 3-8, 3-12

VPI for VC switching on trunk ports, 4-6VPI for VP switching on LIMs, 3-8, 3-12VPI/VCI assignments to PVCs, 7-2, 7-4VPI/VCI valid range on trunk ports, 4-6VPI/VCI valid ranges on LIM slots, 3-5

W

Which command, 6-5

stinger configuration guide - ip-sa · stinger configuration guide part number: 7820-0711-002 for...

Documents