Lucent Technologies Stinger OC3-ATM User Manual

Stinger™

OC3-ATM Trunk Module Guide

For software version 9.0-139

January 2001

Copyright © 2000, 2001 Lucent Technologies Inc. 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 by any
entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts, or licensing, without the express
written consent of Lucent Technologies. For permis sion to reproduce or distribute, please email your request to [e-mail].

Notice

Every effort was mad e to en sur e that the information in this document was comp lete and accurate at the time of printing, but information is subject to change.

Safety, Compliance, and Warranty Information

Before handling any Lucent Access Netw orks hardwar e product, read the E dge Acc ess Safety an d Complianc e Guide included in your product package. See
that guide also to dete rmin e how prod uc ts com ply w it h the elec tr omag neti c int erfer en ce (E MI) and ne tw ork co mp atib ility r equ irem ents of your country. See
the warranty card included in your product package for the limited warranty that Lucent Technologies provide s for it s pr oducts.

Security Statement

In rare instances, unauthorized individuals make connec ti ons t o the te lecommunications network through the use of access features.

Trademarks

4ESS, 5ESS, A Network of Expertise, AnyMedia, APX 8000 , AqueView, AUDIX, B -STDX 8000, B-STDX 9000, ...Beyond Compare, CaseView, Cajun,
CajunDocs, CAJUNVIEW, Callmaster, CallVisor, CBX 500, CellPi pe , C hoiceNe t, C le arReac h, ComOS, cvMAX, DACSc an, Dac smat e, Da takit, DEFINITY ,
Definity One, DSLMAX, DSL Terminator, DSLPipe, DSLTNT, Elemedia, Elemedia Enhanced, EMMI, End to End Solutions, EPAC, eSight, ESS,
EVEREST, Gigabit-scaled campus networking, Globalview, GRF, GX 250, GX 550, HyperPATH, Inferno, InfernoSpaces, Intragy, IntragyAccess,
IntragyCentral, Intuity, IP Navigator, IPWorX, LineReach, LinkReach, MAX, MAXENT, MAXTNT, Multiband, Multiband PLUS, Multiband RPM,
MultiDSL, MultiVoice, MultiVPN, Navis, NavisAccess, NavisConnect, NavisCore, NavisRadius, NavisXtend, NetCare, NetLight, NetPartner, OneVision,
Open Systems Innovations, OpenTrunk, P550, PacketStar, PathStar, Pinnacle, Pipeline, PMVision, PortMaster, SecureConnect, Selectools, Series56,
SmoothConnect, Stinge r, SYSTIMAX, True Access, WaveLAN, WaveMANAGER, WaveMODE M, WebXtend, and Where Network Solutions Never End
are trademarks of L ucent Technologies Inc. Advantage Pak, Advant age Services, A nyMedia, ...Beyond Compare, End to End Solut ions, Inter.NetWorking,
MAXENT, and NetWork Knowledge Solutions are service marks of Lucent Technologies Inc. Other trademarks, service marks, and trade names mentioned in
this publication belong to th ei r respective owners.

Copyrights for Third-Party Software Incl uded in Lucent Access Networks Software Products

C++ Standard Template Library software copy right© 1994 Hewlett-Packard Comp any and copyright© 1997 Silicon Graphi cs. Permission to use, copy,
modify, distribute, and sell this software and its documentation for any purpose is hereby granted without fee, provided that the above copyright notice appear
in all copies and that both that copyright notice and this permission notice appear in supporting documentation. Neither Hewlett-Packard nor Silicon Graphics
makes any representations about the suitability of this software for any pu rpose. It is provided “as is” without expre ss or im pl ied wa rra nt y.

Berkeley Software Distribution (BSD ) UNIX software copyright© 1982, 1986, 1988, 1993 The Regents of California. All rights reserved. Re distribution and
use in source and binary forms, with or wit hout m odifi cation , are permitt ed prov ided t hat the fol low ing co nditi ons are met: 1. R edistrib utions of sourc e code
must retain the above co pyright notice, this list of condi t ions, and the following discla imer. 2. Redistributions in binary form must reproduce the above copy­right notice, this list of conditions, and the following disclaimer in the documentation and/or other materials p rovi ded with the distribution. 3. A l l advertising
materials mentioning f ea tu res or use of this softwa re m ust display the following a ck now l edgement: This produc t includes software developed by the Univer­sity of California, Berk eley, and its contributo rs. 4. Neit her the name of the Univ ersity no r the na mes of its cont ributors m ay be u sed to en dorse or pro mote
products derived from this softw are wit hout specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
OR SERVICES; LOSS OF USE, DATA OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF
LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

Ordering Information

You can order th e most up-to-date product informa ti on and computer-based training on line at http://www.lucent.com/ins/bookstore.

Feedback

Lucent Technologies appreciates your co mm e nts, either positive or negative , about this manual. Please send them to [e-mail].

Lucent Technologies

Customer Service

To obtain product and service information, software upgrades, and technical assistance, visit

the eSight™ Service Center at http://www.esight.com. The center is open 24 hours a
day, seven days a week.

Finding information and software

The eSight Service Center at http://www.esight.com provides technical information,
product information, and descriptions of available services. Log in and select a service. The
eSight Service Center also provides software upg rades, release notes, an d adden da. Or you can
visit the FTP site at ftp://ftp.ascend.com for this informatio n.

Obtaining technical assistance

The eSight™ Service Center at http://www.esight.com provides access to technical
support. You can obtain technical assistance through email or the Internet, or by telephone.

If you need to contact Lucent Technologies for assistance, make sure that you have the
following information available:

• Active contract number, product name, model, and serial number

• Software version

• Software and hardware options

• If supplied by your carrier, service profile identifiers (SPIDs) associated with your line

• Your local telephone company’s switch type and operating mode, such as AT&T 5ESS

Custom or Northern Telecom National ISDN-1

• Whether you are routing or bridging with your Lucent product

• Type of computer you are using

• Description of the problem

Obtaining assistance through email or the Internet

If your services agreement allows, you can communicate directly with a technical engineer
through Email T ech nical Support or eSight Live chat. Select one of these sites wh en you log in
to http://www.esight.com.

Calling the technical assistance center (TAC)

If you cannot find an answer through th e tools and in for mation o n eSight o r if you have a very
urgent need, contact TAC. Access the eSight Service Center at http://www.esight.com
and click Contact Us below the Lucent Technologies logo for a list of telephone numbers
inside and outside the United States.

You can alternatively call [phone] for a menu of Lucent services, or call
[phone] for an operator. If you do not have an active services agreement or contract,
you will be charged for time and materials.

Stinger OC3-ATM Trunk Module Guide iii

Contents

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

About This Guide.............................................................................. xi

What is in this guide.................................................................................................................. xi

What you should know ............................................................................................................. xi

Documentation conventions...................................................................................................... xi

Stinger documentation set .......................................................................................................xii

Chapter 1 Configuring the OC3-ATM Trunk Module...................................... 1-1

Introducing the OC3-ATM trunk module.............................................................................. 1-1

Installing an OC3-ATM trunk module................................................................................... 1-2

OC3-ATM trunk module specifications ................................................................................ 1-2

Cable specifications........................................................................................................ 1-4

Configuring an OC3-ATM trunk module .............................................................................. 1-5

Overview of OC3-ATM settings .................................................................................... 1-6

Displaying OC3 status and nailed groups....................................................................... 1-7

Changing physical-layer interface settings..................................................................... 1-8

Configuring call-control......................................................................................................... 1-8

Example of OC3-ATM configuration.................................................................................. 1-10

Checking OC3-ATM trunk interface status......................................................................... 1-11

Monitoring errors and performance of the SONET payload ........................................ 1-14

Chapter 2 Configuring Trunk Port Redundancy............................................ 2-1

Introducing trunk port redundancy........................................................................................ 2-1

Trunk port redundancy settings...................................................................................... 2-1

Example of automatic redundancy configuration.................................................................. 2-2

Example of manual redundancy configuration ...................................................................... 2-3

Stinger OC3-ATM Trunk Module Guide v

Figures

Figure 1-1 OC3-ATM trunk module.............................................................................. 1-5

Figure 1-2 OC3 interfaces to the ATM network.......................................................... 1-10

Figure 1-3 SONET layers............................................................................................. 1-14

Stinger OC3-ATM Trunk Module Guide vii

Tables

Table 1-1 OC3-ATM specifications.............................................................................. 1-3

Table 1-2 Cable specifications...................................................................................... 1-4

Stinger OC3-ATM Trunk Module Guide ix

About This Guide

What is in this guide

This guide describes how to configure and monitor the Stinger OC3-ATM trunk module and
includes configuration examples and module specifications. This module also describes how to
configure LIM redundancy.

!

Warning: Before installing your Stinger unit, be sure to read the safety instructions in the

Edge Access Safety and Compliance Guide. For information specific to your unit, see the
“Safety-Related Physical, Environmental, and Electrical Information” appendix in the Getting
Started Gui de for your Stinger unit.

What you should know

To make use of the procedures and sample configurations in this guide, you should have a
general knowledge of Stinger products and a working knowledge of the command-line
interface. You should understand the fundamental concepts of digital subscriber line (DSL)
technology and be familiar with the relationship between DSL interfaces and associated
configuration profiles.

Documentation conventions

Following are the special characters and typographical conventions that might be 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
monospace text

Italics Represent variable information. Do not enter the words themselves in

Represents characters that you enter exactly as shown (unless the
characters 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.

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.

Stinger OC3-ATM Trunk Module Guide xi

About This Guide

Stinger documentation set

Convention Meaning

[ ] Square brackets indicate an optional argument you might add to a

| Separates command choices that are mutually exclusive.
> Points to the next level in the path to a parameter or menu item. The

Key1-Key2 Represents a combination keystroke. To enter a combination

Press Enter Means press the Enter, or Return, key or its equivalent on your

Note:

command. To include such an argument, type only the information
inside the brackets. Do not type the brackets unless they appear in
boldface.

item that follows the angle bracket is one of the options that appear
when you select the item that precedes the angle bracket.

keystroke, 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.)

computer.
Introduces important additional information.

!

Caution:

!

Warning:

Warning:

W arns that a failure to follow the recom mended procedur e could result
in loss of data or damage to equipment.

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

Warns of danger of electric shock.

Stinger documentation set

The Stinger documentation set consists of the following manuals:

• Read me first:

– Edge Access Safety and Compliance Guide. Contains important safety instructions

and country-specific information that you must read before installing a Stinger unit.

– TAOS Command-Line Interface Guide. Introduces the TAOS command-line

environment and shows you how to use the command-line interface effectively. This
guide describes keyboard shortcuts and introduces commands, security levels, profile
structure, and parameter types.

• Installation and basic configuration:

– Getting Started Guide for your unit. Shows how to install your Stinger chassis and

hardware. This guide also shows you how to use the command-line interface to
configure and verify IP access and basic access security on the unit, and how to
configure Stinger control module redundancy.

– The following Stinger module guides describe the features of and provide instru ctions

for configuring and veri fying the stat us of Stinger modules:

xii Stinger OC3-ATM Trunk Module Guide

About This Guide

Stinger documentation set

Stinger ADSL 24-Port Line Interface Module (LIM) Guide
Stinger ADSL 48-Port G.lite Line Interface Module (LIM) Guide
Stinger Copper Loop Test (CLT) Module Guide—includes operating instructions
Stinger DS3-ATM Trunk Module Guide
Stinger E3-ATM Trunk Module Guide
Stinger HDSL2 32-Port Line Interface Module (LIM) Guide
Stinger IDSL 32-Port Line Interface Module (LIM) Guide
Stinger OC3-ATM Trunk Module Guide (this manual)

Stinger SDSL 48-Port Line Interface Module (LIM) Guide

Stinger T1 and E1 Modules Guide

• Configuration:

– Stinger ATM Configuration Guide. Describes how to use the command-line interface

to configure Asynchronous Transfer Mode (ATM) operations on a Stinger unit. The
guide explains how to configure permanent virtual circuits (PVCs), and shows how to
use standard ATM features such as quality of service (QoS), connection admission
control (CAC), and subtending.

– Stinger Private Network-to-Network Interface (PNNI) Supplement. Provides

quick-start instructions for configuring PNNI and soft PVCs (SPVCs), and describes
the related profiles and commands in the Stinger command-line interface.

– Stinger SNMP Management of the ATM Stack Supplement. Describes SNMP

management of ATM ports, interfaces, and connections on a Stinger unit to provide
guidelines for configuring and managing ATM circuits through any SNMP
management utility.

– T AOS R ADIUS Guide and Refer en ce. De scr ibes how to s et up a TAOS unit to use the

Remote Authentication Dial-In User Service (RADIUS) server and contains a
complete reference to RADIUS attributes.

• Administration and troubleshooting:

– Stinger Administration Guide. Describes how to administer the Stinger unit an d

manage its operations. Each chapter focuses on a particular aspect of Stinger
administration and operations. The chapters describe tools for system management,
network management, and Simple Network Management Protocol (SNMP)
management.

• Reference:

– Stinger Reference. An alphabetic reference to Stinger profiles, parameters, and

commands.

– T AOS Glossary. Defines term s used in documentation for Stinger units.

Stinger OC3-ATM Trunk Module Guide xiii

Configuring the OC3-ATM Trunk Module

Introducing the OC3-ATM trunk module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Installing an OC3-ATM trunk module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

OC3-ATM trunk module specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2

Configuring an OC3-ATM trunk module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-5

Configuring call-control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-8

Example of OC3-ATM configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-10

Checking OC3-ATM trunk interface status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-11

The OC3-ATM trunk module provides f iber optic interfaces between the Stinger ™ unit and the
carrier ATM core network. The OC3-ATM trunk module provides one or two 155.52-Mbps
interfaces for connecting to an ATM switch. The following three versions of the OC3-ATM
trunk module are supported:

• OC3-ATM—single mode, intermediate reach

• OC3-ATM—single mode, long reach

• OC3-ATM—multimode

1

All three OC3-ATM trunk modules are installed and configured in the same way.

Introducing the OC3-ATM trunk module

Stinger units support one-port and two-port OC3-ATM modules, each of which is available in
three versions.

Platform Product code Description

Stinger FS STGR-TM-OC3-1 One-port trunk module with OC 3c/STM-1
Stinger LS STGRLS-TM-OC3-1

Stinger FS STGR-TM-OC3-1L One-p ort trunk module with OC3c/STM-1
Stinger LS STGRLS-TM-OC3-1L

Stinger OC3-ATM Trunk Module Guide 1-1

interface (single mode, intermediate reach) for
operation at 155Mbps per port ov er single -mode
fiber, at distances up to 20km (12.4miles).

interface (single mode, long reach) for operation
at 155Mbps over single-mode fiber, at distances
up to 40km (24.9miles).

Configuring the OC3-ATM Trunk Module

Installing an OC3-ATM trunk module

Platform Product code Description

Stinger FS STGR-TM-OC3-1M One-port trunk module with OC3c/STM-1
Stinger LS STGRLS-TM-OC3-1M

Stinger FS STGR-TM-OC3-2 Two-port trunk module with OC3c/STM-1
Stinger LS STGRLS-TM-OC3-2

Stinger FS STGR-TM-OC3-2L Two-port trunk module with OC3c/STM-1
Stinger LS STGRLS-TM-OC3-2L

Stinger FS STGR-TM-OC3-2M Two-port tru nk m od ule with OC3c/STM-1
Stinger LS STGRLS-TM-OC3-2M

interface (multi-mode) for operation at 155Mbps
over multi-mode fiber, at distances up to 2km
(1.2miles).

interface (single mode, intermediate reach) for
operation at 155Mbps per port ov er single -mode
fiber, at distances up to 20km (12.4miles).

interface (single mode, long reach) for operation
at 155Mbps per port over single-mode fiber, at
distances up to 40km (24.9miles).

interface (multi-mode) for operation at 155Mbps
per port over multi-mode fiber, at distances up to
2km (1.2miles).

Installing an OC3-ATM trunk module

See the Getting Started Guide f or installation instructions. Y ou can install up to two OC3-ATM
trunk modules in a Stinger unit.

After installing the OC3-ATM trunk module and connecting it to an ATM switch, you verify
connections by checking the status lights. You then configure the physical link. Use a status
profile to display the state of the OC3 line and any error conditions.

OC3-ATM trunk module specifications

The OC3-ATM trunk module provides up to two 155.52-Mbps ports for optical connections.
Each port supports the OC-3 and the STM-1 interface standards (see Figure 1-1) and comes
with 64-KB cell buffers per port, enabling you to customize your network for specific traffic
needs. The port buffers and the 64-KB cell buffers on the control module are based on the
Stinger architecture.

You can configure each port as one of the following:

• User-to-Network Interface (UNI)

• Interim Interswitch Signaling Protocol (IISP) connection

• Direct trunk

1-2 Stinger OC 3-ATM Trunk Module Gui de

Table 1-1 lists OC3-ATM module specifications.

Table 1-1. OC3-ATM specifications

Category Specifications

Configuring the OC3-ATM Trunk Module

OC3-ATM trunk module specifications

Physical
dimensions

Power requirements 11.5 W (optical).
T emp erature rang e 0
Operating humidity 0 to 90%, noncondensing.
Agency approvals Electromagnetic Emissions Certifications: FCC Part 15 Class A, and

Interface standards
(OC-3c)

Interface standards
(STM-1)

Physical connectors Subscriber Connector (SC).
Physical interfaces Two UNI 3.0/3.1 cell-bearing OC-3c/STM-1 155.52-Mbps ports

Height: 15 inches (38.1 cm).
Width: 1.06 inches (2.69 cm).
Depth: 5 inches (12.7 cm) .
Weight: 1.5 pounds (0.68 kg).

° to 40°C (32° to 104°F).

CISPR Class A.
ANSI T1.105.

ANSI T1.106 .
ITU G.957 (optical).

ITU G.709 (optical).

(optical).
Maximum modules Two per unit.
Signal

distance/levels
(single-m ode laser
optics)

Minimum bend
radius

Other OC-3c
standards

Stinger OC3-ATM Trunk Module Guide 1-3

Medium-Reach:

• Up to 15 kilometers (9.3 miles).

• TX power: -15 decibels referred to 1 milliwatt to -8dBm.

• RX Sensitivity: -8dBm, -28dBm.

• Nominal wavelength: 1310 nanometers.

3 inches (7.62 cm).

ATM Forum UNI 3.0/3. 1.

ANSI T1M1.3/92-005R1.

Bellcore TR-NWT-001112.

Bellcore GR-253-CORE.

RFC 1595.

Configuring the OC3-ATM Trunk Module

OC3-ATM trunk module specifications

Table 1-1. OC3-ATM specifications (continued)

Category Specifications

Other STM-1
standards

Cable specifications

Table 1-2 provides cable specifications.

Table 1-2. Cab le specifications

Interface Type Number

Twisted
Pairs

G.703 - 75-ohm N/A 49.2 ohms/km 75 ohms 66.7 picofarads

ATM Forum UNI 3.0/3. 1.

ANSI T1M1.3/92-005R1.

Bellcore GR-253-CORE.

RFC 1595.

DC
Resistance

Nominal
Impedance

Nominal
Capacitance

(pf)/m

Shield Maximum

Length

95% 120 m

1-4 Stinger OC 3-ATM Trunk Module Gui de

Figure 1-1 shows the OC3-ATM trunk module.

Figure 1-1. OC3-ATM trunk module

STGR-OC3-2P

Configuring the OC3-ATM Trunk Module

Configuring an OC3-ATM trunk module

PORT 0

PORT 1

Configuring an OC3-ATM trunk module

Each 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

Stinger OC3-ATM Trunk Module Guide 1-5

Configuring the OC3-ATM Trunk Module

Configuring an OC3-ATM trunk module

interface, which supports the standard Universal Test and Operations Interface for ATM
(UTOPIA).

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 trunk module in slot 18.

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

[in OC3-ATM/{ any-shelf any-slot 0 }:line-config]
trunk-group = 0
nailed-group = 801
call-route-info = { any-shelf any-slot 0 }
loopback = no-loopback
framer-rate = STS-3c
framer-mode = sonet
tx-scramble-disabled = no
tx-cell-payload-scramble-disabled = no
loop-timing = no
vpi-vci-range = vpi-0-255-vci-32-8191
vc-switching-vpi = [ 0 0 0 0 0 0 0 ]
clock-source = not-eligible
clock-priority = middle-priority

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 you can assign

a text string of up to 16 characters.
PhysicalAddress 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

Sparing-Mode

Physical address of the trunk port to be used as a spare.

Redundancy mode for the port.
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.

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 1-7 for related

information.
Call-Route-Info

Not currently used. Leave the default value (the zero address).

1-6 Stinger OC 3-ATM Trunk Module Gui de

Configuring the OC3-ATM Trunk Module

Configuring an OC3-ATM trunk module

Parameter Specifies

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). For

more information, see “Changing physical-layer interface

settings” on page 1-8.
Framer-Mode

Specify

sonet or sdh. Synchronous optical network (SONET)

and synchronous digital hierarchy (SDH) are American National

Standards Institute (ANSI) optical digital transmis sion standards.

SONET supports data transmission rates from 51.84 Mbps

(STS-1) to 13.2192 Gbps (STS-48). SDH is the corresponding

international standard, supporting rates from 155.52 Mbps

(STM-1) to 4.976 Gbps (STM-32). SONET is the default.
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 fa r-end switch has disabled the corresp onding

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 correspond i ng functions.
Loop-Timing Enable/disable derivation of transmission timing from receiver

Yes causes the T AOS unit to derive TX timing for all trunk

inputs.

ports from the receiver inputs of the ports. Loop timing is disable d

by default. With the default setting, transmission timing is derived

from the reference clock.
VPI-VCI-Range Valid range of virtual channel id enti fi er (VCI ) numbers to be used

with specified virtual path identifiers (VPIs) for virtual channel

connections (VCCs).
VC-Switching-VPI Array of up to seven VPIs to use for VC switching.
Clock-Source Enable/disable obtaining the system clock signal from the port.
Clock-Priority Priority for choosing an interface as the system’s clock source.

Displaying OC3 status and nailed groups

T o see the nailed-gr oup numbers for trun k ports, use th e atmtrunks command. For example,
the command output that follows shows the nailed-grou p numbers for OC3 trunks. In this
example, the system has one OC3-ATM trunk module 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)

Stinger OC3-ATM Trunk Module Guide 1-7

Configuring the OC3-ATM Trunk Module

Configuring call-control

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.

STS-3C setting indicates a
European

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

155.52-Mbps interface (STM-1).

155.52-Mbps interface in the U.S. as well as the equivalent

Configuring call-co ntrol

Using the call-control procedures, you can configure the Stinger to allow connections to be
established even when the line state is not fully up. You can configure the unit to use these
procedures system-wide or on a per-port basis on the DS3-ATM, OC3-ATM, and E3-ATM
trunk modules and on the SDSL, ADSL, and HDSL2 LIMs.

The default

The call-control mechanism enables the Stinger unit to establish and maintain soft PVCs
(SPVCs) across port state changes. This allows xDSL subscribers to establish connections on
LIM interfaces in the operating states before they are fully trained, as well as in the standard
port-up state (in which the modem has successfully trained up). SPVC connections are
accepted when the modem has not fully trained up to the port-up state. If a LIM interface with
an active SPVC connection changes from a port-up state to the state it was in before it was
fully trained, the SPVC remains connected. Connections are broken only if the physical slot or
line stops operating or is disabled by an administrator.

By default, the Stinger unit monitors the physical line state of its interfaces and allows
connections to be established only when the line state is fully up.

Following are examples of the relevant parameters, shown with default settings:

[in SYSTEM]
ignore-lineup = no

[in SDSL/{ any-shelf any-slot 0 }]
ignore-lineup = system-defined

[in DS3-ATM/{ any-shelf any-slot 0 }]
ignore-lineup = system-defined

1-8 Stinger OC 3-ATM Trunk Module Gui de

Parameter Specifies

Configuring the OC3-ATM Trunk Module

Configuring call-control

SYSTEM:
ignore-lineup

line profile:

ignore-lineup

Enable/disable the Stinger system’s ability to ignore line status when
determining whether calls are established or not. Specify one of the
following values:

• no (the default)—The Stinger call-control mechanism allows
calls to be established when the line state is up and disallow calls
when the line state is down.

• yes—The Stinger call-control mechanism ignores the line state
and allows calls to be established on a port as long as the
specified slot is operational and the specified port is enabled.

Whether the line status of a slot has an effect on the Stinger call
control mechanism on the specified port. Specify one of the following
values:

• system-defined (the default)—Sets the Stinger to inherit the
Ignore-Lineup value from the system profile.

• no—Sets the Stinger call-control mechanism to ignore the
system-wide setting and allows calls to be established when the
line state is operational and disallow calls on the port when the
line state is down.

• yes—Sets the Stinger call-control mechanism to ignore the line
state and the system-wide setting and allows calls to be
established on the specified port as long as the specified slot is
operational and the specified port is enabled.

The commands in the following example configure the unit to use the new call-control
procedures system-wide:

admin> read system
SYSTEM read

admin> set ignore-lineup = yes
admin> write

SYSTEM written

When call-control is enabled system-wide, you can disable it on specific interfaces by
modifying the line profile. The commands in the following example disable call-control
procedures on port one of the SDSL 48-port LIM in slot 12:

admin> read sdsl { 1 12 1 }
SDSL/{ shelf-1 slot-12 1 } read
admin> set ignore-lineup = no
admin> write
SDSL/{ shelf-1 slot-12 1 } written

Stinger OC3-ATM Trunk Module Guide 1-9

Configuring the OC3-ATM Trunk Module

Example of OC3-ATM configuration

Example of OC3-ATM configura t ion

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

Figure 1-2. OC3 interfaces to the ATM network

Active OC3-ATM
interfaces

ATM

Spare port

The following commands list the trunk port profiles:

admin> dir oc3-atm
40 08/03/1999 15:33:35 { shelf-1 trunk-module-1 2 } 1:17:2
25 08/03/1999 15:37:13 { shelf-1 trunk-module-2 1 } 1:18:1
25 08/03/1999 15:38:25 { shelf-1 trunk-module-2 2 } 1:18:2
40 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:

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

admin> set enabled = yes
admin> set spare-physical-address shelf = 1
admin> set spare-physical-address slot = 18
admin> set spare-physical-address item-number = 2
admin> set sparing-mode = automatic
admin> write

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

OC3-ATM/{ shelf-1 trunk-module-1 2 } read
admin> set enabled = yes
admin> set spare-physical-address shelf = 1
admin> set spare-physical-address slot = 18
admin> set spare-physical-address item-number = 2
admin> set sparing-mode = automatic
admin> write

OC3-ATM/{ shelf-1 trunk-module-1 2 } written

1-10 Stinger OC3-ATM Trunk Module Guide

Configuring the OC3-ATM Trunk Module

Checking OC3-ATM trunk interface status

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

admin> set enabled = yes
admin> set spare-physical-address shelf = 1
admin> set spare-physical-address slot = 18
admin> set spare-physical-address item-number = 2
admin> set sparing-mode = automatic
admin> write

OC3-ATM/{ shelf-1 trunk-module-2 1 } written

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

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

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

OC3-ATM/{ shelf-1 trunk-module-1 1 } written

Checking OC3-ATM trunk interface status

The Stinger unit creates 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 ATM framer
status information. The Performance-Monitoring and Interval-Performance-Monitoring
subprofiles provide coun ters for the SON ET payload.

The following display shows OC3-ATM-STAT parameters for the physical interface, 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

Stinger OC3-ATM Trunk Module Guide 1-11

Configuring the OC3-ATM Trunk Module

Checking OC3-ATM trunk interface status

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

Line-State Overall state of the OC3 line, which can be any of the

Spare-Physical-Address

Sparing-State

VPI-VCI-Range
VC-Switching-VPI
VCC-VPI

system.

following states:

active—Line is enabled and a multipoint connection

•

is established.

does-not-exist—Link is not physically on the

•

trunk modul e.

•

disabled—Line is disabled.

• loss-of-signal—Near end has lost the signal.

loss-of-frame—Near end has lost framing (also

•

known as a Red Alarm).

•

yellow-alarm—Near end is receiving a Yellow

alarm from the far end, indicating a loss of framing.

ais-receive—Near end is receiving an alarm

•

indication signal (AIS).

The redundant peer of this trunk port. If the curren t 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.

The state of the redundancy function.

sparing-none

indicates that redundancy is not enabled. If redundancy is
enabled and the current port is the primary trunk port, the
value can be

primary-active or

primary-inactive. If redundancy is enabled and the

current port is the secondary trunk port, the value can be

secondary-active or secondary-inactive.

Current valid VCI range configured for the port.
Array of VPIs used for virtual circuit switching.

For internal use only.

1-12 Stinger OC3-ATM Trunk Module Guide

Configuring the OC3-ATM Trunk Module

Checking OC3-ATM trunk interface status

Parameter Indicates

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.

and in frame.
Section-State State of the SONET section.
Path-State State of the SONET path.
AIS-Receive Far end is sending an alarm indication signal (AIS).

indicates that the local device has not received an AIS.
Yellow-Receive Far-end loss-of-frame (Yellow Alarm) occurred on the line.

False indicates that the line is up

False

False indicates that a Yellow Alarm was not received.

Out-Of-Cell-Delineation Out of cell delineation. A header error control (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 (RL OP) 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).
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 A TM Cell Processor (R ACP) correctable

header check sequence (CHCS) er rors. Th e RACP d elineates

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 first in, first out (FIFO)

overflow.

Stinger OC3-ATM Trunk Module Guide 1-13

Configuring the OC3-ATM Trunk Module

Checking OC3-ATM trunk interface status

Parameter Indicates

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

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 cumu lative p erformance 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 events) are defined in RFC 1595, Definitions of Managed

Objects for the SONET/SDH Interface Type.

Performance and error counters

Performance and error counters are maintained at the section, line, path SONET layers (see
Figure 1-3).

Figure 1-3. SONET layers

As shown in Figure 1-3, a 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.

SONET

Section

Line

Path

An errored second is a secon d in which on e or mo re co ding vio lations or inco ming errors have
occurred at the specified layer.

A severely errored second is a second in which more than a certain number of coding
violation s or incoming errors have occurred, with the number based on l ine rate and bit error
rate (BER).

1-14 Stinger OC3-ATM Trunk Module Guide

Configuring the OC3-ATM Trunk Module

Checking OC3-ATM trunk interface status

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.

Performance-Monitori ng and Interval-Performance-Monitoring subprofiles

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 = 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

[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

Stinger OC3-ATM Trunk Module Guide 1-15

Configuring the OC3-ATM Trunk Module

Checking OC3-ATM trunk interface status

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

SONET-Section-Severely-Errored-Seconds Number of severely errored seconds at

SONET-Section-Severely-Errored-Framing-Seconds Number of severely errored framing

SONET-Section-Coding-Vio lations Number of bit-interleaved parity errors

SONET-Line-Errored-Seconds Number of errored seconds at the line

SONET-Line-Severely-Errored-Seconds Number of severely errored seconds at

SONET-Line-Coding-Violations Number of bit-interleaved parity errors

SONET-Line-Unavailable-Seconds Number of unavailable seconds at the

SONET-Far-End-Line-Errored-Seconds Number of errored seconds at the

SONET-Far-End-Line-Severely-Errored-Seconds Number of severely errored seconds at

SONET-Far-End-Line-Coding-Violations Number of bit-interleaved parity errors

SONET-Far-End-Line-Unavailable-Seconds Number of unavailable seconds at the

SONET-Path-Errored-Seconds Number of errored seconds at the path

SONET-Path-Severely-Errored-Seconds Number of severely errored seconds at

SONET-Path-Coding-Violations Number of bit-interleaved parity errors

SONET-Path-Unavailable-Seconds Number of unavailable seconds at the

SONET-Far-End-Path-Errored-Seconds Number of errored seconds at the

SONET-Far-End-Path-Severely-Errored-Seconds Number of severely errored seconds at

SONET-Far-End-Path-Coding-Violations Number of bit-interleaved parity errors

SONET-Far-End-Path-Unavailable-seconds Number of unavailable seconds at the

section layer.

the section layer.

seconds at the section layer.

at the Section layer.

layer.

the line layer.

at the line layer.

line layer.

far-end device’s line layer.

the far-end device’s line layer.

at the far-end device’s line layer.

line layer.

layer.

the path layer.

at the path layer.

path layer.

far-end device’s path layer.

the far-end device’s path layer.

at the far-end device’s path layer.

far-end device’s path layer.

1-16 Stinger OC3-ATM Trunk Module Guide

Configuring Trunk Port Redundancy

Introducing trunk port redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Example of automatic redundancy configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Example of manual redundancy configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

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 sourcin g the ATM network clock on one of the
trunk ports. One or more of the ports can be desig nated as eligible clock s our ces, and assign ed
a priority for use as the clock source.

Introducing trunk port redundancy

Trunk port redundancy provides a 1:1 sparing function for trunk port failure. The trunk port to
be backed up (the primary trunk port) does not have to be of the same type as t h e spare trunk
port. Both automatic and manual trunk port redu ndancy are supported.

2

When the redundancy 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 redundancy, an administrator invokes the sparing function manually by setting the
Sparing-Mode parameter to manual, and manually disables it 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 reestablished on the primary trunk port.

Automatic trunk port redundancy 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
spare becomes inactive, at which point the system reestablishes the logical connections on the
primary port.

Trunk port redundancy settings

Following are the trunk port redundancy parameters, shown with default settin g s:

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

Stinger OC3-ATM Trunk Module Guide 2-1

Configuring Trunk Port Redundancy

Example of automatic redundancy configuration

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

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

primary trunk port and activates

the spare trunk port. Setting it

inactivates the

back to inactive brings down the spare and reactivates the
primary por t .

Example of automatic redundancy configuration

To use automatic trunk port redundancy, you modify the profile of a primary trunk port to
specify a spare trunk port and enable automatic redundancy. For example, the following
commands specify that the first port in slot 17 is a primary trunk port, and the first trunk por t 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> write

OC3-ATM/{ shelf-1 trunk-module-1 1 } written

Note that 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:

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

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

admin> set shelf = 1
admin> set slot = 18
admin> set item-number = 1
admin> list ..

2-2 Stinger OC 3-ATM Trunk Module Gui de

Configuring Trunk Port Redundancy

Example of manual redundancy configuration

admin> set sparing-mode = automatic
admin> write

OC3-ATM/{ shelf-1 trunk-module-1 1 } written

Example of manual redundancy configuration

T o us e manual trunk port redu ndancy, you modify the profile of a primar y 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> 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 = manual
admin> write

OC3-ATM/{ shelf-1 trunk-module-1 1 } written

T o deactivate the s pare trun k p ort an d activate the p rimary po rt again, set the Sparing-Mode to

inactive. For example:

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

admin> set sparing-mode = inactive
admin> write

OC3-ATM/{ shelf-1 trunk-module-1 1 } written

Stinger OC3-ATM Trunk Module Guide 2-3