PSAX2300UserGuide.pdf

7/22/2019 PSAX2300UserGuide.pdf

http://slidepdf.com/reader/full/psax2300userguidepdf 1/678

Doc. No.: 255-700-447

PacketStar ®

PSAX 2300 Multiservice Media Gateway

User Guide

for the PacketStar ® PSAX Multiservice Media Gateways

Issue 1, October 2003

System Software Release 9.0.0

Top of Guide



Copyright © 2003 by Lucent Technologies. All rights reserved.

For trademark, regulatory compliance, and related legal information, see

“Legal Notices, Safety, and Regulatory Information”.



PacketStar ® PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 Release 9.0.0

255-700-447 iii

Legal Notices, Safety, and RegulatoryInformation

Copyright

Copyright © 2003 by 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 fash-

ion 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 the originating organization and the business

management owner of the material.

This document was prepared by the Information Design and Development

Team of Lucent Technologies, PacketStar PSAX products. Offices are located in

Landover, Maryland, USA.

Trademarks

PacketStar, AQueView, Lucent, Lucent Technologies, and the Lucent Technolo-

gies logo are registered trademarks of Lucent Technologies in the USA. Other

product and brand names mentioned in this guide are trademarks or regis-

tered trademarks of their respective owners.

Notices

The information in this document is for informational use only, is subject to

change without notice, and should not be construed as a commitment by

Lucent Technologies, Inc. This document is without warranty of any kind,

either expressed or implied. Lucent Technologies, Inc. assumes no responsi-

bility for any errors, inaccuracies, or omissions. Neither is any liability

assumed for damages resulting from the use of the information or instruc-

tions contained herein. Lucent Technologies, Inc. is not responsible for any

damage or loss to your data or equipment resulting either directly or indi-

rectly from use of this document.

Warranty Information

Lucent Technologies provides a 90-day limited software warranty, and a one-

year limited hardware warranty on this product. Refer to the Software License

and Limited Warranty Agreement and the Lucent Technologies InterNetworking Sys-

tems Global Warranty that accompanied your package for more information.



Legal Notices, Safety, and Regulatory InformationRegulatory Standards Compliance

iv 255-700-447


Regulatory Standards Compliance

The PacketStar PSAX 2300 Multiservice Media Gateway, model 23S00, is

compliant with a number of safety, electromagnetic compatibility (EMC), and

telecommunications standards. The applicable standards for this system are

described in the PacketStar ® PSAX 2300 Multiservice Media Gateway Installation

Guide.

Safety Information

When installing and operating the PSAX 2300 Multiservice Media Gateway,

follow the safety guidelines provided in the printed PacketStar ®PSAX Multiser-

vice Media Gateway Safety Guidelines, which accompanies this product to help

prevent serious personal injury and damage to the PSAX 2300 equipment.

Please read all warnings and instructions supplied before beginning installa-

tion or configuration of the PSAX 2300 equipment. In addition to the general

safety information provided, you should also refer to this guide for other

important safety information and procedures.



255-700-447 v


Table of Contents

Legal Notices, Safety, and Regulatory Information . . . . . . . . . . . . . . . . . iii

Copyright . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Notices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Warranty Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iii

Regulatory Standards Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

Safety Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . iv

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

Purpose of This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Audience for This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

What You Should Know . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-1

Related Reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Product Information Library . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Printed Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Other Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Text Types Used in This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

Icons and Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Command Description Tables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Field Description Tables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

Selecting Options, Fields, and Commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

Help Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

About Lucent Technologies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

For More Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7About the PacketStar PSAX Product Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7

PSAX 1000 Multiservice Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7




Comments on This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9



Table of Contents

vi 255-700-447


2 Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

System Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

System Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2

Backplane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Power Supply Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3

Stratum 3–4 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4

CPU4 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5

CPU2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6

Alarm Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7

Hardware Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Chassis Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

System Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-9

Power Supply Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

Stratum 3–4 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-10

CPU4 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

CPU2 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

Alarm Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-11

PacketStar I/O and Server Modules Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

Module Performance and Power Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-12

3 System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-1


System Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

User Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Feature Highlights. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Interface Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2

Connections Supported. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Permanent Virtual Circuit (PVC) Connections. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

Soft Permanent Virtual Circuit (SPVC) Connections . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3

SPVC Reconnection Priority Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4

Modification of Parameters for Active SPVC Connections . . . . . . . . . . . . . . . . . . 3-6Switched Virtual Circuit (SVC) Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6

SVC Functional Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

Call States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-7

User Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

Circuit Emulation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-9

SPVC Support for CES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-10



Table of Contents

255-700-447 vii


Circuit Emulation Service for the Multiserial Module. . . . . . . . . . . . . . . . . . . . . .3-10

Dynamic Bandwidth Circuit Emulation Service. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-10

Dynamic CAC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

DS1 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

DS3 Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

HDLC Passthrough Bit Inversion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-11

Interim Interswitch Signaling Protocol (IISP) Interface. . . . . . . . . . . . . . . . . . . . . . . . .3-12

Private Network-Network Interface (PNNI) 1.0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-12

PNNI Features Supported by the PSAX Systems. . . . . . . . . . . . . . . . . . . . . . . . . .3-13

PNNI Peer Group Dynamics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-13

PNNI Topology State Element (PTSE) Information . . . . . . . . . . . . . . . . . . . . . . . .3-14

PNNI Hierarchies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-14

ATM Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

Integrated Link Management Interface (ILMI) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-17

ILMI over PNNI Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18

Load Balancing for IISP and PNNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18

ATM Terminal Emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18

ATM UNI 4.0 Signaling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-18

Inverse Multiplexing over ATM (IMA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

Automatic Use of IMA Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

IMA Configuration Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-19

Frame Relay-to-ATM Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

FRF.5 Encapsulating Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

FRF.8 Converting Frames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21Inverse Address Resolution Protocol (ARP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

Frame Relay-to-Frame Relay Interworking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

GR-303 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-21

Fax/Modem Master/Slave Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

CAS Refresh Rates in the On-Hook State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

Idle Channel Suppression Support for the CellPipe IAD. . . . . . . . . . . . . . . . . . . .3-23

GR-303 Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-23

Dynamic Bandwidth Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-24

Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25

Network Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-26

Simple Network Management Protocol Version 3 . . . . . . . . . . . . . . . . . . . . . . . . . . .3-27

Navis® AQueView ® Element Management System . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

PSAX System Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Bulk Statistics Collection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-28

Connection Gateway API . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-29



Table of Contents

viii 255-700-447


Connection Gateway API Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-29

PSAX System As a TCP Client/Server for the Connection Gateway API . . . . . . . 3-29

Fractional PRI Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

PNNI Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

DS1 ANI In-line Codes for Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-31

DS0A Non-Latched Loop Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-32

PSAX System Traffic Protection Capabilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

1:1 Traffic Protection Patch Panel Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-33

APS/MSP Protection on the Optical Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . 3-35

Interface Protection Group Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-36

Alternate Rerouting Using Dual-Homed PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . 3-37

Firmware Release Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-39

Forward Error Correction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-40

H.248 Media Gateway Access Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-41

Interface and Connection Naming. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-42

Internet Protocol (IP) Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-43

LANET Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-44

Operations, Administration, and Maintenance (OAM) . . . . . . . . . . . . . . . . . . . . . . . 3-47

Overview of OAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

OAM Cell Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-47

OAM ATM Layer Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-48

OAM F4 Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

OAM F5 Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-49

ATM Layer OAM Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-50

Packet Pipe AAL5-to-AAL2 Wireless Trunking for Mobile Voice . . . . . . . . . . . . . . . . 3-51SNMP Trap Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-52

Traffic Management Using the AQueMan Algorithm . . . . . . . . . . . . . . . . . . . . . . . . 3-52

ATM Traffic Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

Guaranteed Frame Rate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

Usage Parameter Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

UPC Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-54

Early Packet Discard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

Cell Bus Traffic Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-55

ATM Traffic Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

Overview of ATM Traffic Shaping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-58

Configuring ATM Traffic Shaping for HDLC, Frame Relay, and Ethernet VirtualChannels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-59

Task Summary for Implementing ATM Traffic Shaping . . . . . . . . . . . . . . . . . . . . 3-60

VBR ATM Traffic Shaping Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-60

ATM Traffic Shaping for CBR and VBR-rt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-61

Maximum Number of ATM Traffic-Shaped Connections . . . . . . . . . . . . . . . . . . 3-61



Table of Contents

255-700-447 ix


How the ATM Traffic Shaping Algorithm Works . . . . . . . . . . . . . . . . . . . . . . . . .3-61

Formula for Determining the PCR of an ATM Traffic-Shaped Connection . . . . . .3-63

Connection Egress Priority on PSAX Modules Supporting ATM Traffic Shaping . .3-63

ATM Traffic Shaping Capabilities by PSAX Module . . . . . . . . . . . . . . . . . . . . . . .3-64

Virtual Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-66

PSAX Modules Supporting Virtual Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . .3-66

Configuration Compatibility for ATM Traffic Shaping, UPC, and VI . . . . . . . . . . . . . .3-67

Voice Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-68

V5.2 European IDLC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-68

Voice Processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-69

Echo Cancellation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-69

Wireless Mobile Voice Backhaul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-70

Virtual Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-71

Secure Telephone Unit Third Generation (STU-III) Secure Mode . . . . . . . . . . . . . . . . .3-73

Voice Path Assurance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-73

GSM Voice Traffic Compression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-74

System Performance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-74

Optimized Bootup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-74

Synchronization of PSAX System Software on Redundant CPUn Modules . . . . . . . . .3-75

Maintenance Testing on DS1 Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-76

Reduction in Post-Dial Delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-76

System Security. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-76

RADIUS Server Authentication for PSAX System Access. . . . . . . . . . . . . . . . . . . . . . .3-76

ATM Security on Interfaces and Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-78

PSAX Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-78

4 Using VT100 Terminal Emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Setting Up The Windows HyperTerminal Emulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

Connecting a Dialup Modem to the Chassis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-4

5 Site-Specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1


Logging onto the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-1

Console Interface Main Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

Setting Up RADIUS Server Access Authentication for the PSAX System . . . . . . . . . . . . . . .5-6

Overview of Tasks for Setting Up a RADIUS Server . . . . . . . . . . . . . . . . . . . . . . . . . . .5-6

Configuring RADIUS Server Options on the PSAX System . . . . . . . . . . . . . . . . . . . . . .5-7

Changing the System Password and Other User Options . . . . . . . . . . . . . . . . . . . . . . . . .5-11

Changing the System Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-11



Table of Contents

x 255-700-447


Changing Other User Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18

Configuring the System for Your Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Accessing the Site-Specific Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-19

Configuring System Identification Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-22

Rules for Configuring IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-24

Rules for Configuring IP Address Masks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

Configuring System Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

ATM Addresses and OAM Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-25

Configuring System Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

Configuring the PSAX System as a TCP Server or a TCP Client. . . . . . . . . . . . . . . . . 5-29

Configuring Call Control Resource Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

Setting the Configuration Values. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-32

Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-34

Saving the Configuration and Rebooting the System. . . . . . . . . . . . . . . . . . . . . . . . 5-40

Backing Up Configuration Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Configuring GR-303 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Configuring TAS Module System-Wide Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Configuring H.248 Media Gateway Control Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Configuring DSP Resource Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Enabling and Disabling PSAX System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-42

Rebooting CPUn Modules in Redundant and Nonredundant Systems. . . . . . . . . . . . . . . 5-46

Saving Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-46

Rebooting the Redundant PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-47

Rebooting the Nonredundant PSAX System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-49

Configuring ISDN Q.921 User Adaptation (IUA) Layer Protocol. . . . . . . . . . . . . . . . . . . . 5-50Configuring Interface Protection Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-52

Setting Up an Interface Protection Group ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-53

Creating an Interface Protection Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-57

Internet Protocol (IP) Throttling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-61

SNMP Trap Activation and Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-65

Enabling and Disabling SNMP Trap Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66

Trap Activation Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-66

Collecting Bulk Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69

Overview of Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-69

Configuring the PSAX System to Use a Statistics Server . . . . . . . . . . . . . . . . . . . . . . 5-69

Using the Equipment Configuration Window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-71

Accessing the Equipment Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 5-72

Alarm Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-75

Configuring the Stratum 3–4 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76

Setting the Stratum Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77



Table of Contents

255-700-447 xi


Switching the Line Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-83

Alarm Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-84

Saving the Equipment Configuration Values and Logging Off . . . . . . . . . . . . . . . . . . . . .5-84

6 Configuring ATM PNNI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Overview of ATM PNNI Systemwide Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

Configuring an ATM PNNI Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-1

Modifying an ATM PNNI Node Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-9

Configuring an ATM PNNI Node Peer Group Leader (PGL) . . . . . . . . . . . . . . . . . . . . . . . . .6-9

Configuring an ATM PNNI Node Timer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-13

Configuring an ATM PNNI Node SVCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-16

Configuring ATM PNNI Node Scope Mapping . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-18

Configuring an ATM PNNI Route Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-20

Configuring ATM PNNI Metrics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-25

Configuring an ATM PNNI Route TNS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-29

Viewing ATM PNNI Map TNS Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35

Configuring a Summary Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-38

Viewing ATM PNNI Map Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-41

Viewing ATM PNNI Map Node Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-45

Viewing ATM PNNI Map Address Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-50

Viewing the ATM PNNI Link Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-53

Viewing ATM PNNI SVCC RCC Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-59

Viewing the ATM PNNI Neighbor Peer Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-62

Viewing the ATM PNNI Neighbor Peer Port Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-66

Viewing ATM PNNI PTSE Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-68Viewing ATM PNNI System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-72

7 Configuring ATM Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1


Configuring Switched IWF Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

Configuring Nonswitched IWF Trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

Configuring the Local IWF Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-1

Configuring a Remote IWF Node. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-4

Adding a Signaling VCC Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-8

Adding a Bearer VCC Identifier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-13

Adding a Narrowband Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-23

Adding a Broadband Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-25

Viewing ATM Trunking Information. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-27



Table of Contents

xii 255-700-447


8 Configuring V5.2 European IDLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-1

Overview of the V5.2 European IDLC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

V5.2 PSTN Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Network Side Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

V5.2 User Side Configuration Summary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3

V5.2 IWF Device Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

LE Voice Switch Interoperability with the PSAX System . . . . . . . . . . . . . . . . . . . . . . . 8-4

V5.2 IAD Interoperability with the PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

V5.2 ISDN Implementation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

PSTN Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Enabling the V5 Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5

Setting Call Control Resource Allocation Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-9

Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12

Accessing the V5 Resource Allocation Configuration Window. . . . . . . . . . . . . . . . . 8-18

Accessing the V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . 8-22

Adding New Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24

Accessing the V5 Variant Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27

Accessing the V5 Interface Variant Configuration Window . . . . . . . . . . . . . . . . . . . 8-28

Accessing the V5 Physical C-Channel Configuration Table . . . . . . . . . . . . . . . . . . . . 8-32

Accessing the V5 Physical C-Channel Configuration Window . . . . . . . . . . . . . . . . . 8-33

Accessing the V5 E1 Link Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

Accessing the V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 8-38

Accessing the V5 E1 Interface Configuration Window. . . . . . . . . . . . . . . . . . . . . . . 8-40

Accessing the V5 Time Slot Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-42

Accessing the V5 Data Link Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43

Accessing the V5 Data Link Configuration Window. . . . . . . . . . . . . . . . . . . . . . . . . 8-45

User Side Configuration Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-47

Accessing the V5 User Port Table. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48

Accessing the V5 User Port Configuration Window, PSTN Port Type . . . . . . . . . . . . 8-49

Accessing the V5 User Port Configuration Window, ISDN Port Type. . . . . . . . . . . . . 8-55

9 Configuring SNMP Authentication Options. . . . . . . . . . . . . . . . . . . . . . . . .9-1


SNMP Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1Accessing SNMP Configuration Options. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2

Modifying an SNMP Community String Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4

Configuring the User-based Security Model (USM). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

Configuring USM Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-7

Changing a USM User’s Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11

Deleting USM Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14



Table of Contents

255-700-447 xiii


Configuring the View-based Access Control Model (VACM) . . . . . . . . . . . . . . . . . . . . . .9-15

Configuring VACM Access Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15

Modifying VACM Access Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-21

Deleting VACM Access Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-22

Assigning a User to a VACM Access Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-22

Re-assigning a User to a Different VACM Access Group . . . . . . . . . . . . . . . . . . . . . .9-28

Deleting a User from a VACM Access Group. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-28

Configuring SNMP Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-29

Configuring V3 Informs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-34

10 Configuring ATM Security Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Availability of the ATM Security Feature. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Prerequisites for Configuring ATM Security Agents . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-1

Configuring ATM Security for ATM UNI Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2

Accessing ATM Security for an ATM UNI Interface. . . . . . . . . . . . . . . . . . . . . . . . . . .10-2

Configuring an ATM Security Agent for an ATM UNI Interface . . . . . . . . . . . . . . . . .10-4

Viewing ATM Security Agent Statistics for an ATM UNI Interface. . . . . . . . . . . . . . . .10-9

Configuring ATM Security for ATM PNNI SVCC RCC Nodes . . . . . . . . . . . . . . . . . . . . . .10-13

Accessing ATM Security for an ATM PNNI SVCC RCC Node. . . . . . . . . . . . . . . . . . .10-13

Configuring an ATM Security Agent for an ATM PNNI SVCC RCC Node . . . . . . . . .10-14

Viewing ATM Security Agent Statistics for an ATM PNNI SVCC RCC Node. . . . . . . .10-20

Configuring ATM Security for ATM PNNI Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-24

Accessing ATM Security for an ATM PNNI Interface. . . . . . . . . . . . . . . . . . . . . . . . .10-24

Configuring an ATM Security Agent for an ATM PNNI Interface—Signaling PVC . . .10-26Viewing ATM Security Agent Statistics for an ATM PNNI Interface—Signaling PVC .10-32

Configuring an ATM Security Agent for an ATM PNNI Interface—Routing PVC . . . .10-36

Viewing ATM Security Agent Statistics for an ATM PNNI Interface—Routing PVC . .10-41

Viewing All ATM Security Agents in the System. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-45

11 Using System Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-1

Viewing System Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-2

Checking the Module Connection Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-7

Running Cell Test Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-9

Rebooting PSAX Hardware Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-15

Removing Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18

Unlocking a Telnet Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-18

Operations Administration and Maintenance (OAM) . . . . . . . . . . . . . . . . . . . . . . . . . . .11-19

Enabling OAM Loopback Functions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-19



Table of Contents

xiv 255-700-447


OAM Activation and Deactivation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11-23

12 Backing Up and Restoring PSAX System Files . . . . . . . . . . . . . . . . . . . . . .12-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Database Configuration Save and Restore Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-1

Choosing the Configuration Files Transfer Method. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-2

Backing Up System Database Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-3

Backing Up Database Files Using the Console Interface . . . . . . . . . . . . . . . . . . . . . . 12-3

Backing Up Database Files Using FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-7

PSAX System Database Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-8

Backing Up Database Files Using XModem/YModem Transfer . . . . . . . . . . . . . . . . . 12-9

Setting Up for the File Transfer Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-9

Copying the Database Files to a Remote Storage Medium . . . . . . . . . . . . . . . 12-10

Restoring System Database Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-15

Restoring Database Files Using the Console Interface . . . . . . . . . . . . . . . . . . . . . . 12-15

Restoring Database Files Using FTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-16

Restoring Database Files Using XModem/YModem File Transfer. . . . . . . . . . . . . . . 12-17

Setting Up for the File Transfer Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-17

Copying the Backup Files to the PSAX System. . . . . . . . . . . . . . . . . . . . . . . . . 12-18

Restoring Backup Files to the Standby CPUn Module . . . . . . . . . . . . . . . . . . . . . . . . . 12-19

Rebooting the PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12-20

13 Upgrading PSAX System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1Required Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Saving Your Modified System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-1

Backing Up Your Current Database Files Prior to Upgrade . . . . . . . . . . . . . . . . . . . . . . . 13-1

Choosing the System Software File Transfer Method . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-2

Upgrading Using the File Transfer Protocol Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Setting Up a Windows FTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Downloading Software Files Using FTP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-3

Upgrading the PSAX System Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-10

Saving Your System Configuration Before System Upgrade . . . . . . . . . . . . . . . . . . 13-11

Module LED Indicators During Booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-12

System Events During Booting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-13

Verifying Successful Downloading of Module Firmware Drivers . . . . . . . . . . . . . . . . . . 13-13

Upgrading Using the XModem/YModem File Transfer Method. . . . . . . . . . . . . . . . . . . 13-15

Setting Up for the File Transfer Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-15

Downloading Software Files Using XModem/YModem . . . . . . . . . . . . . . . . . . . . . 13-16



Table of Contents

255-700-447 xv


Upgrading the PSAX System Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-22

Manually Selecting I/O and Server Module Firmware Drivers . . . . . . . . . . . . . . . . . . . . .13-22

Accessing the Firmware Version Control Window . . . . . . . . . . . . . . . . . . . . . . . . . .13-23

Selecting a Firmware Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-24

Downloading a Firmware Driver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-29

A Common Equipment Module Connections . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Overview of This Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

CPU4 Module Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

CONSOLE Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

ETHERNET1 and ETHERNET2 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

CPU2 Module Connectors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

CONSOLE Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

ETHERNET Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Console Cable Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

Stratum 3–4 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

Alarm Module Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

ALARM Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

STATUS/CONTROL Connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6

B Configuring In-Band Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Overview of In-Band Management Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-1

Using the Direct Connection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

Setting Up the FORE Card on the SUN Workstation . . . . . . . . . . . . . . . . . . . . . . . . . .B-2

Setting Up ATM ARP Table Entries. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-3

Using the Routed Connection Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-4

Setting Up Connections for a Routed Connection Configuration . . . . . . . . . . . . . . . .B-5

Setting PVC Connections for Routed Connection Configuration . . . . . . . . . . . . . . . . .B-6

Using the Hybrid Connection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .B-10

C Reference Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Overview of This Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

ATM Traffic Descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Purpose of Traffic Descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

ATM Connections Supporting Traffic Descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Types of Traffic Descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2

Traffic Shaping Priorities by Configured Feature on PSAX Modules . . . . . . . . . . . . . . C-3

SPVC Connection Cause Codes for Connection Retry . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4

DSP Tone Detection Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9

DSP Channel Reduction Availability Due to Fax Relay Mode. . . . . . . . . . . . . . . . . . . . . . . C-9

Industry Compliance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

Connection Type by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-30



Table of Contents

xvi 255-700-447


Interface Type by Input/Output Module Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31

ATM Service Categories in the PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-35

ATM Service Category Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-35

Priority of ATM Service Categories. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-36

Traffic Shaping, UPC, and Virtual Interface Configuration Compatibilities. . . . . . . . . . . . C-37

PSAX I/O Module Transmit Clock Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-41

D PSAX Module Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Overview of This Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

DS1/T1 Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

6-Port DS1 IMA Module (20N33) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-3

6-Port Enhanced DS1/T1 Module (20N36) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4



8-Port HDSL-2 Module (23N69). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5



12-Port Medium-Density DS1 IMA Module (23N33) . . . . . . . . . . . . . . . . . . . . . . . . . D-6



12-Port Medium-Density DS1 Multiservice Module (23N64). . . . . . . . . . . . . . . . . . . . D-7



12-Port Medium-Density DS1/E1/DS0A CES Module (24N64) . . . . . . . . . . . . . . . . . . D-8



24-Port High-Density DS1 Multiservice Module (23N35) . . . . . . . . . . . . . . . . . . . . . D-10

Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-10

Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11

DS3, E3, and STS-1e Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-11

1-Port Channelized DS3 Multiservice Module (23N60). . . . . . . . . . . . . . . . . . . . . . . D-11



3-Port Channelized DS3/STS-1e CES Module (23N03) . . . . . . . . . . . . . . . . . . . . . . . D-13



1-Port Channelized STS-1e, T1 Module (23N62) . . . . . . . . . . . . . . . . . . . . . . . . . . . D-15





Table of Contents

255-700-447 xvii


2-Port DS3 ATM Module (20N02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16

Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16


1-Port Unchannelized DS3 Frame Relay Module (20N03) . . . . . . . . . . . . . . . . . . . . D-17



1-Port DS3 IMA Module (23N68) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18



2-Port E3 ATM Module (20N22) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18



3-Port Unstructured DS3/E3 CES Module (23N02). . . . . . . . . . . . . . . . . . . . . . . . . . D-19



DSP2 Voice Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20

DSP2 x Voice Server Modules (23N27 (C), 23N29 (D), 23N26 (E), and 23N25 (F)) . . . D-20



E1 Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20

6-Port E1 IMA Module (20N34) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20



6-Port Enhanced E1 Multiservice Module (20N56). . . . . . . . . . . . . . . . . . . . . . . . . . D-21

Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22

21-Port High-Density E1 IMA Module (23N34) . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-23



21-Port High-Density E1 Multiservice Module (23N66) . . . . . . . . . . . . . . . . . . . . . . D-24



Ethernet Interface Modules. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25

4-Port Ethernet Module (23N40). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25



Ethernet Module (20N40). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-27



Fiber-Optic Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-28



Table of Contents

xviii 255-700-447


1-Port Channelized OC-3/STM-1 CES Module (23N12 (MM)/23N13 (SM)) . . . . . . . . D-28



1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module(23N75 (MM)/23N76 (SM)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-29

Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30

4-Port OC-3c/STM-1 Module (24N72 (MM)/24N73 (SM)). . . . . . . . . . . . . . . . . . . . . D-31



1-Port OC-12c/STM-4c Module (23N72 (MM)/23N73 (SM)). . . . . . . . . . . . . . . . . . . D-32



1-Port OC-3c Module with AQueMan (20N12 (MM)/20N13 (SM)) orTraffic Shaping (20N14 (MM)/20N15 (SM)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33



1-Port OC-3c 1+1 APS Module (20N72 (MM)/20N73 (SM)) . . . . . . . . . . . . . . . . . . . D-35



1-Port STM-1 Module with AQueMan (20N62 (MM)/20N63 (SM)) orTraffic Shaping (20N64 (MM)/20N65 (SM)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-36



1-Port STM-1 1+1 MSP Module (20N92 (MM)/20N93 (SM)) . . . . . . . . . . . . . . . . . . D-37



2-Port OC-3c/STM-1 ATM Module (24N70 (MM)/24N71 (SM)) . . . . . . . . . . . . . . . . D-38



Other Server Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-40

Enhanced Router Module (23N41) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-40



Route Server Module (20N41). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-41Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-42


Tones and Announcements Server Module (23N28). . . . . . . . . . . . . . . . . . . . . . . . . D-43


Special Information Tones (SIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-43

Channel Associated Signaling (CAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-43



Table of Contents

255-700-447 xix


Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44


Serial Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44

6-Port Multiserial Module (20N07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44

Bit Stuffing and CES Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44

Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44


Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45

Circuit Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45

Terminal Emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45

HDLC Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-46

ATM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-46


Quadserial Module (23N07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-46



Voice 2-Wire Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48

4-Port Voice 2-Wire Office Module (20N32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48



8-Port Voice 2-Wire Station Module (20N30) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48





Table of Contents

xx 255-700-447




255-700-447 xxi


List of Figures

1-1 Field Description Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4

1-2 Main Menu Help Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6

2-1 PSAX 2300 Multiservice Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2

2-2 -48 V dc Power Supply Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4

2-3 CPU4 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6

2-4 CPU2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7

2-5 Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8

2-6 Example Configuration with the Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8

3-1 Sample SPVC Reconnection Prioritization Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5

3-2 PNNI Hierarchical Topology Showing Three Node Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16

3-3 DBA-Controlled Backplane Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25

3-4 PSAX System as a TCP Client Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

3-5 PSAX System as a TCP Server Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30

3-6 1:1 Protection Scheme on the PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-34

3-7 Typical Interface Protection Group Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37

3-8 Automatic Traffic Rerouting using Dual-Homed PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39

3-9 Relationship Between LANET and the OSI Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45

3-10 LANET Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-46

3-11 OAM Cell Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-48

3-12 OAM Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-49

3-13 OAM Activation/Deactivation Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51

3-14 Cell Bus Traffic Shaping Occurs on Egress to the Backplane . . . . . . . . . . . . . . . . . . . . . . . . .3-56

3-15 Cell Bus Traffic Shaping Using the Input Cell-Selection Algorithm . . . . . . . . . . . . . . . . . . . . .3-57

3-16 Sample ATM Traffic Shaping Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-59

3-17 ATM Traffic Shaping table Sample Queue 1 Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-62

3-18 Sample Uses of Virtual Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-66

3-19 Combining the UPC Feature and Either the TS or VI Feature on a Connection . . . . . . . . . . .3-68

3-20 PacketPipe AAL5-to-AAL2 Wireless Trunking from Cell Site to MSC for Mobile Voice . . . . . .3-71

3-21 Virtual Router Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-72

3-22 Enhanced Router and Example Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-723-23 End-to-End Continuity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-73

3-24 PSAX System Access Authentication via RADIUS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-77

4-1 Connection Description Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

4-2 Connect To Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2

4-3 COM1 Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

4-4 PSAX 2300 Multiservice Media Gateway System Logon Window . . . . . . . . . . . . . . . . . . . . . .4-4



List of Figures

xxii 255-700-447


5-1 PSAX 2300 Multiservice Media Gateway System Logon Window . . . . . . . . . . . . . . . . . . . . . . 5-2

5-2 Console Interface Main Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5

5-3 User Options Window—Logged on as Username Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8

5-4 User Options Window—Authentication Mode Hybrid Selected . . . . . . . . . . . . . . . . . . . . . . . 5-8

5-5 User Options Window—Logged on as Username Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13

5-6 User Options Window—Logged on as Username Readwrite . . . . . . . . . . . . . . . . . . . . . . . . 5-13

5-7 User Options Window—Logged on as Username Readonly . . . . . . . . . . . . . . . . . . . . . . . . . 5-14

5-8 Site-Specific Menu Window (No System Options Configured) . . . . . . . . . . . . . . . . . . . . . . . 5-19

5-9 Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23

5-10 TCP Server Configuration Window (PSAX System as a TCP Client) . . . . . . . . . . . . . . . . . . . . 5-30

5-11 TCP Server Configuration Window (PSAX System as a TCP Server) . . . . . . . . . . . . . . . . . . . . 5-30

5-12 Site-Specific Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

5-13 Call Control Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33

5-14 Diagnostics Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41

5-15 Remote Reboot Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41

5-16 Site-Specific Menu Window (Feature Turn On/Off Option Selected) . . . . . . . . . . . . . . . . . . . 5-43

5-17 Feature Turn On/Off Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

5-18 Console Interface Main Menu Window (Save Configuration Option Selected) . . . . . . . . . . . 5-47

5-19 Remote Reboot Configuration Window (Primary Switchover Option Selected) . . . . . . . . . . . 5-48

5-20 Remote Reboot Configuration Window (Reboot Primary CPU Option Selected) . . . . . . . . . . 5-50

5-21 Sample IUA Layer Configuration for the OMG and TMG Sides . . . . . . . . . . . . . . . . . . . . . . 5-51

5-22 Interface Protection Feature Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54

5-23 Protection Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55

5-24 Protection Group Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56

5-25 Interface Protection Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-585-26 Interface Protection Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59

5-27 Site-Specific Menu (IP Throttling Configuration Option Selected) . . . . . . . . . . . . . . . . . . . . . 5-61

5-28 The IP Throttling Window (Disabled) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

5-29 The IP Throttling Window (Enabled) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

5-30 Trap Activation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67

5-31 Bulk Statistics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70

5-32 Sample Equipment Configuration Window on a PSAX 2300 or PSAX 4500 System (Page 1) 5-72

5-33 Sample Equipment Configuration Window on a PSAX 1000, PSAX 2300, or PSAX 4500System (Page 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73

5-34 Stratum Configuration Window (Freerun) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77

5-35 Stratum Configuration Window (LineTiming Synchronization) . . . . . . . . . . . . . . . . . . . . . . . 5-78

5-36 Save Configuration [Modified] (Before Saving) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85

6-1 PNNI System-Wide Configuration Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2

6-2 PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

6-3 PNNI Node Configuration Window (Before Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

6-4 PNNI Node Configuration Window (After Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6



List of Figures

255-700-447 xxiii


6-5 PNNI Node PGL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10

6-6 PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14

6-7 PNNI Node SVCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-17

6-8 PNNI Scope Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19

6-9 PNNI Route Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-21

6-10 PNNI Route Address Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-22

6-11 PNNI Metrics Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-26

6-12 PNNI Metrics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27

6-13 PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30

6-14 PNNI Route TNS Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31

6-15 PNNI Map TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35

6-16 PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-37

6-17 PNNI Summary Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-39

6-18 PNNI Summary Address Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-40

6-19 PNNI Map Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-42

6-20 PNNI Map Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-43

6-21 PNNI Map Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-46

6-22 PNNI Map Node Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-47

6-23 PNNI Map Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-51

6-24 PNNI Map Address Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-52

6-25 PNNI Link Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-54

6-26 PNNI Link Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-55

6-27 PNNI SvccRcc Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-59

6-28 PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-61

6-29 PNNI Neighbor Peer Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-636-30 PNNI Neighbor Peer Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-64

6-31 PNNI Neighbor Peer Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-67

6-32 PNNI PTSE Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-69

6-33 PNNI PTSE Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-70

6-34 PNNI System Statistics Screen Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-73

7-1 Site-Specific Menu Window—ATM Trunking Configuration Option Selected . . . . . . . . . . . . .7-2

7-2 ATM Trunking Local Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3

7-3 ATM Trunking Remote IWF Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5

7-4 ATM Trunking Remote IWF Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6

7-5 ATM Trunking Sig VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9

7-6 ATM Trunking Sig VCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10

7-7 ATM Trunking Bearer VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14

7-8 ATM Trunking Bearer VCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15

7-9 ATM Trunking NarrowBand Routing Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-24

7-10 ATM Trunking Broadband Routing Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-26



List of Figures

xxiv 255-700-447


7-11 ATM Trunking Data Channel Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28

8-1 Site-Specific Menu Window (Feature Turn On/Off Option Selected) . . . . . . . . . . . . . . . . . . . . 8-6

8-2 Feature Turn On/Off Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

8-3 Site-Specific Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10

8-4 Call Control Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11

8-5 V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18

8-6 V5 Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19

8-7 V5 Interface Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23

8-8 V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25

8-9 V5 Intf Variant Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27

8-10 V5 Interface Variant Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29

8-11 V5 Physical C-Channel Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32

8-12 V5 Physical C-Channel Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34

8-13 V5 E1 Link Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37

8-14 V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39

8-15 V5 E1 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41

8-16 V5 Time Slot Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43

8-17 V5 Data Link Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44

8-18 V5 Data Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45

8-19 V5 User Port Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48

8-20 V5 User Port Configuration Window for PSTN as Port Type . . . . . . . . . . . . . . . . . . . . . . . . . 8-50

8-21 V5 User Port Configuration Window, Port Type ISDN Selected . . . . . . . . . . . . . . . . . . . . . . 8-56

9-1 Site-Specific Menu Window, SNMP Agent Selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3

9-2 SNMP Agent System-Wide Configuration Window, Non-Root User View . . . . . . . . . . . . . . . 9-3

9-3 SNMP Agent System-Wide Configuration Window, Root User View . . . . . . . . . . . . . . . . . . . 9-49-4 Community String Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5

9-5 Community String Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6

9-6 Usm User Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8

9-7 Usm User Creation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9

9-8 Usm User Key Change Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12

9-9 Vacm Access Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16

9-10 Vacm Access Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

9-11 Vacm Security to Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

9-12 Vacm Security to Group Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26

9-13 Notification Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30

9-14 Notification Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31

10-1 ATM UNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3

10-2 ATM UNI Interface ATM Security Configuration Window (Integrity Security Service Only) . . 10-5

10-3 ATM UNI Interface ATM Security Configuration Window (Both Integrity and ConfidentialitySecurity Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5

10-4 ATM UNI Interface ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10



List of Figures

255-700-447 xxv


10-5 PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-14

10-6 PNNI Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-14

10-7 ATM PNNI SVCC RCC Security Configuration Window (Integrity Security Service Only) . . . .10-15

10-8 ATM PNNI SVCC RCC Security Configuration Window (Both Integrityand Confidentiality Security Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-16

10-9 PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-2110-10 ATM PNNI SVCC RCC Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-21

10-11 ATM PNNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-25

10-12 ATM PNNI Interface ATM Security ConfigurationWindow - Signaling PVC (Integrity Security Service Only) . . . . . . . . . . . . . . . . . . . . . . . . .10-27

10-13 ATM PNNI Interface ATM Security ConfigurationWindow - Signaling PVC (Both Integrity Security and Confidentiality Services) . . . . . . . . .10-28

10-14 ATM PNNI Interface ATM Security Statistics - Signaling PVC Window . . . . . . . . . . . . . . . . .10-33

10-15 ATM PNNI Interface ATM Security Configuration - Routing PVCWindow (Integrity Security Service Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-37

10-16 ATM PNNI Interface ATM Security Configuration - Routing PVCWindow (Both Integrity Security and Confidentiality Services) . . . . . . . . . . . . . . . . . . . . .10-37

10-17 ATM PNNI Interface ATM Security Statistics - Routng PVC Window . . . . . . . . . . . . . . . . . . .10-42

10-18 ATM Security Agents Table Window (Populated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-46

10-19 ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-49

11-1 Console Interface Main Menu Window (Diagnostics Option Selected) . . . . . . . . . . . . . . . . . .11-3

11-2 Diagnostics Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3

11-3 System Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4

11-4 Module Connection Count Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8

11-5 Cell Test Diagnostics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10

11-6 Cell Test Payload Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-1311-7 Remote Reboot Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-16

11-8 Unlock Shell / Ping Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-19

11-9 OAM Loopback Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-20

11-10 OAM LOOPBACK Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-21

11-11 OAM Activate & Deactivate Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-24

11-12 OAM Activation –Deactivation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-25

12-1 Remote Database Operation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-4

12-2 Software Version Configuration window (XMODEM/YMODEM File Transfer Selected) . . . .12-10

12-3 XMODEM/YMODEM File Transfer Window (Send Options Panel Selected) . . . . . . . . . . . . .12-12

12-4 XMODEM/YMODEM File Transfer Window (Receive Options Panel Selected) . . . . . . . . . . . .12-19

13-1 Console Interface Main Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-4

13-2 Software Version Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-4

13-3 SRD Download Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-5

13-4 Migration of the Files During the PSAX System Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11

13-5 Software Version Configuration Window (XMODEM/YMODEM File Transfer Selected) . . . .13-17

13-6 XMODEM/YMODEM File Transfer Window (Receive Options Panel Selected) . . . . . . . . . . . .13-18



List of Figures

xxvi 255-700-447


13-7 Console Interface Main Menu Window (Software Version Configuration Option Selected) 13-23

13-8 The Software Version Configuration Window (Firmware Version Control Selected) . . . . . . 13-24

13-9 Firmware Version Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26

A-1 ETHERNET1 and ETHERNET2 Connector Pin Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

A-2 ETHERNET Connector Pin Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

A-3 ALARM Connector Pin Locations on the Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

A-4 ALARM Cable with 26-Pin Connector and Pigtail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

A-5 Pin Locations for the STATUS/CONTROL Connector on the Alarm Module . . . . . . . . . . . . . . . A-6

A-6 STATUS/CONTROL Cable with 44-Pin Connector and Pigtail . . . . . . . . . . . . . . . . . . . . . . . . . A-7

B-1 Direct Connection Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2

B-2 Routed Connection Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5

B-3 Hybrid Connection Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10

C-1 Combining the UPC Feature and Either the TS or VI Feature on a Connection . . . . . . . . . . C-38



255-700-447 xxvii


List of Tables

1-1 Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2

1-2 Command Description Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3

1-3 System Responses to Selecting Options, Fields, or Commands . . . . . . . . . . . . . . . . . . . . . . . .1-5

1-4 Shortcut Keys for Navigating Console Interface Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5

2-1 Chassis Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9

2-2 System Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9

2-3 -48 V dc Power Supply Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

2-4 Stratum 3–4 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10

2-5 CPU4 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11

2-6 CPU2 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11

2-7 Physical Hardware Specifications for the Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-12

2-8 Physical Hardware Specifications for PSAX I/O and Server Modules . . . . . . . . . . . . . . . . . . . .2-12

2-9 Performance and Power Specifications for the PSAX Modules . . . . . . . . . . . . . . . . . . . . . . . .2-13

3-1 Sample User-Defined Priority Scheme for Reconnecting SPVC ATM IMA Links . . . . . . . . . . . . .3-5

3-2 Forward Error Correction Automatic Rate Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-41

3-3 CBR and VBR Service-Level Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53

3-4 ATM Traffic Shaping Capabilities by Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-64

3-5 ATM Traffic Shaping, UPC Support, and VI Support Configuration Compatibility . . . . . . . . .3-67

4-1 Starting the Hyperterminal Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1

4-2 Windows HyperTerminal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3

5-1 Field Descriptions for the PSAX System Logon Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3

5-2 Console Interface Main Menu Options and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5

5-3 Commands for the User Options Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8

5-4 Field Descriptions for the User Options Window (RADIUS Server Fields) . . . . . . . . . . . . . . . . . .5-9

5-5 Permissions for PSAX-defined Usernames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12

5-6 Commands for the User Options Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14

5-7 Field Descriptions for the User Options Window (Password and MiscellaneousUser Options Fields) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14

5-8 ASCII Characters Permitted for Use in Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-17

5-9 Descriptions for Site-Specific Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-205-10 Commands for the Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23

5-11 Field Descriptions for the Master ATM Address and OAM Related Data Panel on theSite-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23

5-12 Field Descriptions for the Master ATM Address and OAM Related Data Panel on theSite-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26

5-13 Field Descriptions for the System Identification Panel on the Site-SpecificConfiguration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27



List of Tables

xxviii 255-700-447


5-14 Field Descriptions for the System Date and Time Panel on the Site-SpecificConfiguration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28

5-15 Commands for the TCP Server Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31

5-16 Field Descriptions for the TCP Server Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . 5-31

5-17 Commands for the Call Control Resource Allocation Configuration Window . . . . . . . . . . . . 5-34

5-18 Field Descriptions for the Call Control Resource Allocation Configuration Window . . . . . . . 5-345-19 PSAX System Performance Capabilities Per Node for Release 9.0.0 . . . . . . . . . . . . . . . . . . . 5-39

5-20 Commands for the Feature Turn ON/OFF Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44

5-21 Field Descriptions for the Feature Turn On/Off Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45

5-22 Commands for the IUA Layer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51

5-23 Field Descriptions for the IUA Layer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . 5-51

5-24 Commands for the Interface Protection Feature Configuration Window . . . . . . . . . . . . . . . 5-54

5-25 Commands for the Protection Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55

5-26 Commands for the Protection Group Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 5-56

5-27 Field Descriptions for the Protection Group Configuration Window . . . . . . . . . . . . . . . . . . . 5-56

5-28 Commands for the Interface Protection Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58

5-29 Commands for the Interface Protection Configuration Window . . . . . . . . . . . . . . . . . . . . . 5-59

5-30 Field Descriptions for the Interface Protection Configuration Window . . . . . . . . . . . . . . . . . 5-60

5-31 Commands for the IP Throttling Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62

5-32 Field Descriptions for the IP Throttling Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 5-63

5-33 Commands for the Trap Activation Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67

5-34 Field Descriptions for the Trap Activation Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68

5-35 Commands for the Bulk Statistics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70

5-36 Field Descriptions for the Bulk Statistics Configuration Window . . . . . . . . . . . . . . . . . . . . . 5-70

5-37 Commands for the Equipment Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-735-38 Field Descriptions for the Equipment Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . 5-74

5-39 Alarm Status Descriptions for Modules on the Equipment Configuration Window . . . . . . . . 5-76

5-40 Commands for the Stratum Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78

5-41 Field Descriptions for the Stratum Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79

5-42 Messages Generated after the Save Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . 5-85

6-1 Commands for the PNNI System-Wide Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 6-2

6-2 Commands for the PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4

6-3 Field Descriptions for the PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5

6-4 Commands for the PNNI Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6

6-5 Field Descriptions for the PNNI Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . 6-7

6-6 Modifying a Configured PNNI Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9

6-7 Commands for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 6-10

6-8 Field Descriptions for the PNNI Node PGL Configuration Window . . . . . . . . . . . . . . . . . . . . 6-11


6-10 Field Descriptions for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . 6-14




List of Tables

255-700-447 xxix


6-12 Field Descriptions for the PNNI Node SVCC Configuration Window . . . . . . . . . . . . . . . . . . .6-17

6-13 Commands for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . .6-19

6-14 Field Descriptions for the PNNI Scope Mapping Configuration Window . . . . . . . . . . . . . . . .6-19

6-15 Commands for the PNNI Route Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-22

6-16 Commands for the PNNI Route Address Configuration Window . . . . . . . . . . . . . . . . . . . . . .6-22

6-17 Field Descriptions for the PNNI Route Address Configuration Window . . . . . . . . . . . . . . . . .6-23

6-18 Commands for the PNNI Metrics Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27

6-19 Commands for the PNNI Metrics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27

6-20 Field Descriptions for the PNNI Metrics Configuration Window . . . . . . . . . . . . . . . . . . . . . . .6-28

6-21 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30

6-22 Field Descriptions for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31

6-23 PNNI Route TNS Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-32

6-24 Field Descriptions for the PNNI Route TNS Configuration Window . . . . . . . . . . . . . . . . . . . .6-32

6-25 Commands for the PNNI Map TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35

6-26 Field Descriptions for the PNNI Map TNS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-36


6-28 Field Descriptions for the PNNI Map TNS Configuration Window . . . . . . . . . . . . . . . . . . . . .6-37

6-29 Commands for the PNNI Summary Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . .6-39

6-30 Commands for the PNNI Summary Address Configuration Window . . . . . . . . . . . . . . . . . . .6-40

6-31 Field Descriptions for the PNNI Summary Address Configuration Window . . . . . . . . . . . . . . .6-40

6-32 Commands for the PNNI Map Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-42

6-33 PNNI Map Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-43

6-34 Field Descriptions for the PNNI Map Information Window . . . . . . . . . . . . . . . . . . . . . . . . . .6-44

6-35 Commands for the PNNI Map Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-46

6-36 Field Descriptions for the PNNI Map Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-476-37 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-47

6-38 Field Descriptions for the PNNI Map Node Information Window . . . . . . . . . . . . . . . . . . . . . .6-48

6-39 Commands for the PNNI Map Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-51

6-40 Field Descriptions for the PNNI Map Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . .6-51


6-42 Field Descriptions for the PNNI Map Address Entry Window . . . . . . . . . . . . . . . . . . . . . . . . .6-52

6-43 Commands for the PNNI Link Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-54

6-44 Commands for the PNNI Link Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-55

6-45 Field Descriptions for the PNNI Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . .6-55

6-46 Commands for the PNNI SvccRcc Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-59

6-47 Field Descriptions for the PNNI SVCC RCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-60

6-48 Commands for the PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . . . . . .6-61

6-49 Field Descriptions for the PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . .6-61

6-50 Commands for the PNNI Neighbor Peer Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-64

6-51 Command for the PNNI Neighbor Peer Information Window . . . . . . . . . . . . . . . . . . . . . . . .6-64



List of Tables

xxx 255-700-447


6-52 Field Descriptions for the PNNI Neighbor Peer Configuration Window . . . . . . . . . . . . . . . . . 6-65

6-53 Commands for the PNNI Neighbor Peer Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . 6-67

6-54 Field Descriptions for the PNNI Neighbor Peer Port Table Window . . . . . . . . . . . . . . . . . . . 6-68

6-55 Commands for the PNNI PTSE Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69

6-56 Field Descriptions for the PNNI PTSE Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70

6-57 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70

6-58 Field Descriptions for the PNNI PTSE Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71

6-59 Commands for the PNNI System Statistics Screen Window . . . . . . . . . . . . . . . . . . . . . . . . . 6-73

6-60 Field Descriptions for the PNNI System Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74

7-1 Commands for the ATM Trunking Local Node Configuration Window . . . . . . . . . . . . . . . . . 7-3

7-2 Field Descriptions for the ATM Trunking Local Node Configuration Window . . . . . . . . . . . . 7-4

7-3 Commands for the ATM Trunking Remote IWF Table Window . . . . . . . . . . . . . . . . . . . . . . . 7-5

7-4 Field Descriptions for the ATM Trunking Remote IWF Table . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6

7-5 Commands for the ATM Trunking Remote IWF Configuration Window . . . . . . . . . . . . . . . . . 7-6

7-6 Field Descriptions for the ATM Trunking Remote IWF Configuration Window . . . . . . . . . . . . 7-7

7-7 Commands for the ATM Trunking Sig VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9

7-8 Field Descriptions for the ATM Trunking Sig VCC Table Window . . . . . . . . . . . . . . . . . . . . . 7-10

7-9 Commands for the ATM Trunking Sig VCC Configuration Window . . . . . . . . . . . . . . . . . . . 7-10

7-10 Field Descriptions for the ATM Trunking Sig VCC Configuration Window . . . . . . . . . . . . . . 7-11

7-11 Commands for the ATM Trunking Bearer VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . 7-15

7-12 Field Descriptions for the ATM Trunking Bearer VCC Table Window . . . . . . . . . . . . . . . . . . 7-15

7-13 Commands for the ATM Trunking Bearer VCC Configuration Window . . . . . . . . . . . . . . . . 7-16

7-14 Field Descriptions for the ATM Trunking Bearer VCC Configuration Window . . . . . . . . . . . . 7-16

7-15 Commands for the ATM Trunking Narrowband Routing Table Window . . . . . . . . . . . . . . . 7-24

7-16 Field Descriptions for the ATM Trunking Narrowband Routing Table Window . . . . . . . . . . . 7-247-17 Commands for the ATM Trunking Broadband Routing Table Window . . . . . . . . . . . . . . . . . 7-26

7-18 Field Descriptions for the ATM Trunking Broadband Routing Table Window . . . . . . . . . . . . 7-26

7-19 Commands for the ATM Trunking Data Channel Table Window . . . . . . . . . . . . . . . . . . . . . 7-28

7-20 Field Descriptions for the ATM Trunking Data Channel Table Window . . . . . . . . . . . . . . . . 7-28

8-1 V5.2 Voice Switch Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

8-2 V5.2 IAD Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4

8-3 Commands for the Feature Turn ON/OFF Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7

8-4 Field Descriptions for the Feature Turn On/Off Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8

8-5 Commands for the Call Control Resource Allocation Configuration Window . . . . . . . . . . . . 8-11

8-6 Field Descriptions for the Call Control Resource Allocation Configuration Window . . . . . . . 8-12

8-7 PSAX System Performance Capabilities Per Node for Release 9.0.0 . . . . . . . . . . . . . . . . . . . 8-17

8-8 Commands for the V5 Interface Configuration Menu Window . . . . . . . . . . . . . . . . . . . . . . 8-19

8-9 V5 Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20

8-10 Field Descriptions for the V5 Resource Allocation Configuration Window . . . . . . . . . . . . . . 8-20

8-11 Commands for the V5 Interface Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23



List of Tables

255-700-447 xxxi


8-12 Field Descriptions for the V5 Interface Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-23

8-13 Commands for the V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-25

8-14 Field Descriptions for the V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . .8-26

8-15 Commands for the V5 Intf Variant Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-27

8-16 Field Descriptions for the V5 Interface Variant Table Window . . . . . . . . . . . . . . . . . . . . . . . .8-28

8-17 Commands for the V5 Interface Variant Configuration Window . . . . . . . . . . . . . . . . . . . . . .8-29

8-18 Field Descriptions for the V5 Interface Variant Configuration Window . . . . . . . . . . . . . . . . .8-30

8-19 Commands for the V5 Physical C-Channel Configuration Table Window . . . . . . . . . . . . . . .8-32

8-20 Field Descriptions for the V5 Physical C-Channel Configuration Table Window . . . . . . . . . . .8-33

8-21 Commands for the V5 Physical C-Channel Configuration Window . . . . . . . . . . . . . . . . . . . .8-34

8-22 Field Descriptions for the V5 Physical C Channel Configuration Window . . . . . . . . . . . . . . . .8-35

8-23 Commands for the V5 E1 Link Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . . .8-37

8-24 Field Descriptions for the V5 E1 Link Configuration Table Window . . . . . . . . . . . . . . . . . . . .8-38

8-25 Commands for the V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-39

8-26 Field Descriptions for the V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . .8-39

8-27 Commands for the V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-41

8-28 Field Descriptions for the V5 E1 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . .8-41

8-29 Commands for the V5 Timeslot Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-43

8-30 Commands for the V5 Data Link Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . .8-44

8-31 Field Descriptions for the V5 Data Link Configuration Table Window: . . . . . . . . . . . . . . . . . .8-44

8-32 Commands for the V5 Data Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . .8-45

8-33 Field Descriptions for the V5 Data Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . .8-46

8-34 Commands for the V5 User Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48

8-35 Commands for the V5 User Port Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-50

8-36 Field Descriptions for the V5 User Port Configuration Window . . . . . . . . . . . . . . . . . . . . . . .8-519-1 Menu Options for the SNMP Agent System-Wide Configuration Window . . . . . . . . . . . . . . . .9-4

9-2 Commands for the Community String Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5

9-3 Field Descriptions for the Community String Table Window . . . . . . . . . . . . . . . . . . . . . . . . . .9-6

9-4 Commands for the Community String Configuration Window . . . . . . . . . . . . . . . . . . . . . . . .9-6

9-5 Field Descriptions for the Community String Configuration Window . . . . . . . . . . . . . . . . . . . .9-7

9-6 Default USM User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7

9-7 Commands for the Usm User Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9

9-8 Field Descriptions for the Usm User Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9

9-9 Commands for the Usm User Creation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10

9-10 Field Descriptions for the Usm User Creation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10

9-11 Commands for the Usm User Key Change Configuration Window . . . . . . . . . . . . . . . . . . . .9-13

9-12 Field Descriptions for the Usm User Key Change Configuration Window . . . . . . . . . . . . . . . .9-13

9-13 Default VACM Access Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15

9-14 Commands for the Vacm Access Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16

9-15 Field Descriptions for the Vacm Access Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-17



List of Tables

xxxii 255-700-447


9-16 Commands for the Vacm Access Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18

9-17 Field Descriptions for the Vacm Access Configuration Window . . . . . . . . . . . . . . . . . . . . . . 9-19

9-18 Default VACM Access Group Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22

9-19 Valid VACM Group Assignment for USM Security Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23

9-20 Commands for the Vacm Security to Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . 9-24

9-21 Field Descriptions for the Vacm Security to Group Table Window . . . . . . . . . . . . . . . . . . . . 9-25

9-22 Commands for the Vacm Security to Group Configuration Window . . . . . . . . . . . . . . . . . . 9-26

9-23 Field Descriptions for the Vacm Security to Group Configuration Window . . . . . . . . . . . . . . 9-27

9-24 Commands for the Notification Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30

9-25 Field Descriptions for the Notification Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30

9-26 Commands for the Notification Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31

9-27 Field Descriptions for the Notification Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 9-31

10-1 Commands for the ATM UNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . . . 10-3

10-2 Field Descriptions for the ATM UNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . 10-4

10-3 Commands for the ATM UNI Interface ATM Security Configuration Window . . . . . . . . . . . . 10-6

10-4 Field Descriptions for the ATM UNI Interface ATM Security Configuration Window . . . . . . . 10-6

10-5 Commands for the ATM UNI Interface ATM Security Statistics Window . . . . . . . . . . . . . . . 10-10

10-6 Field Descriptions for the ATM UNI Interface ATM Security Statistics Window . . . . . . . . . . 10-11

10-7 Commands for the ATM PNNI SVCC RCC Security Configuration Window . . . . . . . . . . . . 10-16

10-8 Field Descriptions for the ATM PNNI SVCC RCC Security Configuration Window . . . . . . . . 10-17

10-9 Commands for the ATM PNNI SVCC RCC Security Statistics Window . . . . . . . . . . . . . . . . 10-22

10-10 Field Descriptions for the ATM PNNI SVCC RCC Security Statistics Window . . . . . . . . . . . . 10-22

10-11 Commands for the ATM PNNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . 10-25

10-12 Field Descriptions for the ATM PNNI Interface ATM Security Window . . . . . . . . . . . . . . . . 10-26

10-13 Commands for the ATM PNNI Interface ATM Security Configuration - SignalingPVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28

10-14 Field Descriptions for the ATM PNNI Interface ATM Security Configuration - SignalingPVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29

10-15 Commands for the ATM PNNI Interface ATM Security Statistics - SignalingPVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33

10-16 Field Descriptions for the ATM PNNI Interface ATM Security Statistics - SignalingPVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34

10-17 Commands for the ATM PNNI Interface ATM Security Configuration - RoutingPVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38

10-18 Field Descriptions for the ATM PNNI Interface ATM Security Configuration - Routing

PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3810-19 Commands for the ATM PNNI Interface ATM Security Statistics - Routing

PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42

10-20 Field Descriptions for the ATM PNNI Interface ATM Security Statistics - RoutingPVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-43

10-21 Commands for the ATM Security Agents Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46

10-22 Field Descriptions for the ATM Security Agents Table Window . . . . . . . . . . . . . . . . . . . . . 10-47



List of Tables

255-700-447 xxxiii


10-23 Commands for the ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-49

10-24 Field Descriptions for the ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . .10-50

11-1 Menu Option Descriptions for the Diagnostics Menu Window . . . . . . . . . . . . . . . . . . . . . . .11-1

11-2 Commands for the System Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4

11-3 Field Descriptions for the System Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4

11-4 Commands for the Module Connection Count Table Window . . . . . . . . . . . . . . . . . . . . . . .11-8

11-5 Field Descriptions for the Module Connection Count Table Window . . . . . . . . . . . . . . . . . . .11-8

11-6 Commands for the Cell Test Diagnostics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10

11-7 Field Descriptions for the Cell Test Diagnostics Window . . . . . . . . . . . . . . . . . . . . . . . . . . .11-11

11-8 Commands for the Cell Test Payload Configuration Window . . . . . . . . . . . . . . . . . . . . . . .11-13

11-9 Field Descriptions for the Cell Test Payload Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-14

11-10 Commands for the Remote Reboot Configuration Window . . . . . . . . . . . . . . . . . . . . . . . .11-16

11-11 Commands for the OAM Loopback Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-20

11-12 Commands for the OAM Loopback Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-21

11-13 Field Descriptions for the OAM Loopback Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-22

11-14 Commands for the OAM Activate & Deactivate Table Window . . . . . . . . . . . . . . . . . . . . . .11-25

11-15 Commands for the OAM Activate & Deactivate Table Window . . . . . . . . . . . . . . . . . . . . . .11-25

11-16 Field Descriptions for the OAM Activation-Deactivation Window . . . . . . . . . . . . . . . . . . . .11-26

12-1 Tasks for Copying Database Configuration Files Between the PSAX System and aRemote Storage Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-2

12-2 Commands for the Remote Database Operation Window . . . . . . . . . . . . . . . . . . . . . . . . . . .12-4

12-3 Field Descriptions for the Remote Database Operation Window . . . . . . . . . . . . . . . . . . . . . .12-5

12-4 PSAX System Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-8

12-5 Commands for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . . . . . . .12-12

12-6 Field Descriptions for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . .12-1212-7 Connecting a Cable to the Standby (Backup) CPU Module . . . . . . . . . . . . . . . . . . . . . . . . .12-20

13-1 Tasks for Transferring Files to Your PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-2

13-2 Commands for the SRD Download Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . .13-5

13-3 Field Descriptions for the SRD Download Configuration Window . . . . . . . . . . . . . . . . . . . . .13-6

13-4 Error Status Code Values for the [Error Status] Field on the SRD DownloadConfiguration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-7

13-5 Determining Whether to Proceed with System Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . .13-10

13-6 Determining Whether to Save Your Current System Configuration Before Upgrade . . . . . .13-12

13-7 Length of Time Required for Firmware Downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-14

13-8 Setting Up the Connection Between the PC Workstation, the LocalModem, and the Telephone Jack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-16

13-9 Setting Up the Connection Between the Modem and the PSAX System . . . . . . . . . . . . . . .13-16

13-10 Commands for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . . . . . . .13-18

13-11 Field Descriptions for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . .13-19

13-12 Selecting Firmware Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-25

13-13 Commands for the Firmware Version Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-26



List of Tables

xxxiv 255-700-447


13-14 Field Descriptions for the Firmware Version Control Window . . . . . . . . . . . . . . . . . . . . . . 13-27

A-1 CPU4 Module CONSOLE Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

A-2 CPU4 Module ETHERNET1 and ETHERNET2 Connector Pin Assignments . . . . . . . . . . . . . . . . A-2

A-3 CPU2 Module CONSOLE Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

A-4 CPU2 Module ETHERNET Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

A-5 RJ-12-to-DB9 Adapter Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

A-6 RJ-12-to-DB25 Adapter Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3

A-7 Stratum 3–4 Module RJ-45 Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4

A-8 ALARM Connector Pin Assignments and Cable Pigtail Color Code(COMCODE 300164290) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5

A-9 STATUS/CONTROL Connector Pin Assignments and Cable Pigtail Color Code(COMCODE 300164282) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7

C-1 Traffic Processing Options and Priority Queuing for Modules Supporting ATM Interfaces . . . . C-3

C-2 Connection Release Cause Codes for SPVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5

C-3 DSP Tone Detection Modes and Associated Processing Performed . . . . . . . . . . . . . . . . . . . . . C-9

C-4 Channel Reduction Availability Caused by Fax Relay Connections vs. VoiceProcessing Connections on a DSP2C Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9

C-5 Industry Compliance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10

C-6 Connection Type by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-30

C-7 Interface Type by I/O Module Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31

C-8 PSAX System-Supported Quality of Service Category Descriptions . . . . . . . . . . . . . . . . . . . . C-35

C-9 Mapping ATM Service Categories to PSAX System Priority Levels . . . . . . . . . . . . . . . . . . . . . C-36

C-10 ATM Traffic Shaping, UPC Support, and VI Support Configuration Compatibility . . . . . . . . . C-37

C-11 ATM Traffic Shaping CPS Calculation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-38

C-12 I/O Module Transmit Clock Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-41

D-1 PacketStar PSAX Multiservice Media Gateway Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

D-2 1-Port Channelized OC-3/STM-1 CES Module Optical Specifications . . . . . . . . . . . . . . . . . . D-29

D-3 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module Optical Specifications . . . D-30

D-4 4-Port OC-3c/STM-1 Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-32

D-5 1-Port OC-12c/STM-4c Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33

D-6 1-Port OC-3c Module with AQueman or Traffic Shaping Optical Specifications . . . . . . . . . . D-34

D-7 1-Port OC-3c 1+1 APS Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-35

D-8 1-Port STM-1 Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-36

D-9 1-Port STM-1 1+1 MSP Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-38

D-10 2-Port OC-3c/STM-1 ATM Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . D-39




255-700-447 1-1

1 Getting Started

Purpose of This Guide

The PacketStar ® PSAX 2300 Multiservice Media Gateway User Guide provides a

description of the PSAX 2300 system and its functions and features. It also

provides information about using the console interface to:

• Configure basic system parameters and managing the PSAX 2300 system

• Configure PNNI, ATM trunking, V5.2, SNMP authentication, ATM security,

and other system-wide functions

• Run system diagnostics

• Back up and restore system software

• Upgrade system configurations• Access system trap definitions

For instructions on using the Navis® AQueView ® EMS to perform the same

functions, see the appropriate Navis® AQueView ® EMS User Guide.

Note: If you are setting configuration values for a new, unconfigured

PSAX system for the first time, you should read through this guide

before beginning the configuration process.

Audience for This Guide

The information in this guide is intended for users who will configure and

maintain PSAX 2300 systems.

What You Should Know

Before you use this document or operate a PacketStar PSAX system, you

should already understand and have experience with the following:

• Ethernet network capabilities

• Internet Protocol capabilities

• Data network design

• Telephony network design

• General network management practices

Only authorized personnel should install and use the PacketStar ® PSAX Mul-

tiservice Media Gateways.



Chapter 1 Getting StartedRelated Reading

1-2 255-700-447


Related Reading

Product Information Library

To install, operate, and configure your PSAX system and I/O and server mod-

ules, read the PSAX publications provided on your Lucent TechnologiesPacketStar PSAX Multiservice Media Gateways Products, Product Information

Library CD-ROM.

Printed Documents

For your convenience, many of the documents included on the PacketStar

PSAX Multiservice Media Gateways Product Information Library CD-ROM

are also available in printed form. You can order these documents through

the Lucent Technologies Customer Information Center Web site at:

http://www.lucentdocs.com .

Other Publications

Numerous books are currently available on the subject of basic telecommuni-

cations technology and specific protocols. In addition to such general reading,

you should also be familiar with industry specifications identified in the

appendix entitled “Reference Information” at the end of this guide.

Conventions

Text Types Used in This Document

This guide uses a different typeface to denote text displayed on console inter-face windows and equipment, as well as data you enter. Table 1-1 shows how

each typographical convention is used.

Table 1-1. Text Conventions

Appearance How it is used

SANS SERIF BOLD, ALL CAPS Labels on module panels, chassis faceplates, or other

hardware

Fixed-width normal Message text displayed on the user interface window

Serif bold • Button name (GUI interface) or command name

(console interface) on the user interface window

• Literal text for values that the user types or selects

from predefined sets of values for fields

• Commands or literal argument values

Fixed-width bold System prompts displayed on the user interface window

Serif italics • A variable name or string for which you will substi-

tute your own information

• An argument or parameter on a command line for

which you will substitute your own information

http://www.lucentdocs.com/

http://www.lucentdocs.com/



255-700-447 1-3


Chapter 1 Getting StartedConventions

Icons and Symbols

Follow all safety guidelines in this document to help prevent personal injury

to you and damage to the PSAX 2300 Multiservice Media Gateway system.

Standard icons and symbols to alert you to dangers, warnings, cautions, andnotes are described as follows:

! DANGER:

Warnings for a personal injury hazard are identified by this format.

WARNING:!

Warnings relating to risk of equipment damage or failure are identifiedby this format.

! CAUTION:Warnings relating to risk of data loss or other general precautionary

notes are identified by this format.Note: Identifies additional information pertinent to the text preceding

this note.

Command Description Tables

All illustrations for configuration windows in this guide for the PSAX system

console interface are followed by a command description table describing the

command functions displayed on the window (near the bottom of the win-

dow). You should read all the information in the command description table,

especially when first using a window, because these descriptions may have

special instructions or configuration constraints provided in the Function col-

umn by use of the Note: text convention (see Table 1-2).

Field Description Tables

For all illustrations for configuration windows in this guide for both the

PSAX system console interface and the AQueView EMS, the field description

tables normally follow the command description tables. Field description

tables define the editable and the display-only fields, their functions, valid

values, and constraints, if applicable. As in the command description tables,

the Note: text convention is also used, where appropriate, in the field descrip-

tion tables to alert the user to special instructions or configuration constraints

(see Figure 1-1).

Table 1-2. Command Description Table Example

Command Function

Bring All Interfaces

Into Service

Brings the out-of-service configured interfaces to in-service status.

Note: In GR-303 configuration, it is critical to bring into service

only those channels actively configured with DS1 ports.



Chapter 1 Getting StartedConventions

1-4 255-700-447


Selecting Options, Fields, and Commands

Follow these guidelines to select an option, field, or command on the PSAX

console interface windows and to navigate through the windows:

• To select an option, field, or command, do one of the following:

~ Press the Up, Down, Left, or Right Arrow to highlight (reverse video

image) the option name, field name, or command you want to select and

press Enter as many times as necessary until the field choice you want is

displayed.~ Use the alternate keys, K=UP, H=LEFT, L=RIGHT to highlight (reverse

video image) the option name, field name, or command you want to

select and press Enter. (You can optionally redefine these alternate keys

from the User Options window, which is accessible from the Console

Interface Main Menu window.)

~ To quickly select a command, you can also simultaneously press Ctrl and

the letter underlined in the command.

Once an option name, field, or command is selected, the system responds

as described in Table 1-3.

Figure 1-1. Field Description Table Example

Field Name Field Values Description

Interface Type Default: 0

Range: 0-22

Format: Numeric

Specifies the type of end-to-end connection

protocol that governs the transmission parameters

for this configured port and channel interface.

Note: When certain types of interfaces are select-

ed in this field, other configuration fields are dis-

played on this window.

Identifies editable fields

or display-only fields onscreens

Identifies initial field

value default

Describes the function of the field

and special instructions forconfiguring modules

Identifies availablerange for field valuewhen applicable

Identifies field value format asNumeric, Predefined Alphanumeric,Hexadecimal, or Valid Dotted Quad.

Decribes special instructions orconfiguration constraints



255-700-447 1-5


Chapter 1 Getting StartedHelp Information

• To navigate through the Console windows, use the shortcuts listed in

Table 1-4.

On all the PSAX system windows, each command or menu option has an

underlined letter. The control key plus an underlined letter is a shortcut to

that command or menu option. You can use the navigation keys and hotkeys

with the Caps Lock key on or off. Always observe the status line at the bot-

tom of the window for instructions and information.

Help Information

The Help windows are accessible from any window in the PSAX system con-

sole interface. To access the Help windows, press the ? (Question Mark) key

on any window. In addition to the Help windows, the Console Interface win-

dows display contextual help in the information line at the bottom of each

window. Contextual help provides information about the command or field

currently highlighted on that window. The information line also displays

error codes and responses to commands. All responses and notifications are

Table 1-3. System Responses to Selecting Options, Fields, or Commands

For a selected... the following occurs:

option name The window corresponding to the option name is displayed.

field The following variations occur:

• The field entry area is blank or contains the default or previouslyentered value. Press Enter to enter or change data in this field. Press

Enter again to exit edit mode.

• The field entry area, like the field name, is displayed in reverse video

image and contains a predefined set of values, which you can view or

select by pressing Enter to navigate forward through these values. To

navigate backward through these field values, press Ctrl+H or the

Backspace key.

Read-only fields, which you cannot change, are enclosed in square brack-

ets (example: [LineStatus]).

command The following variations occur:

• A message in the information line indicating an error or successful com-

pletion of the command is displayed.• The next higher level or previous window (window name) is displayed.

• The next lower level or succeeding window (window name) is displayed.

Table 1-4. Shortcut Keys for Navigating Console Interface Windows

If you want to... press...

redisplay the previous window Ctrl+B on the window.

redisplay the Console Interface Main Menu window Ctrl+G on the window.

refresh the window Ctrl+R on the window.



Chapter 1 Getting StartedHelp Information

1-6 255-700-447


recorded in a trap log. See the PacketStar ® PSAX Simple Network Management

Protocol (SNMP) Trap Reference Guide for details on displaying the trap log and

obtaining explanations of the trap messages.

To view the Help windows from the Console Interface Main Menu window,

perform the following procedure.

Begin

1 On the window for which help is desired, press the ? (question mark)

key.

The Help window for the current console window is displayed (see

Figure 1-2).

2 To display the remaining Help windows for the current console window,

press the Down Arrow key.

3 To scroll backward through the Help windows for the current console

window, press the Up Arrow key.

4 To exit Help and return to the current console window, press the Enter

key.

End

Figure 1-2. Main Menu Help Window

Your site name appears hereafter initial configuration

Information Line



255-700-447 1-7


Chapter 1 Getting StartedTechnical Support

Technical Support

If you experience a problem with your PSAX 2300 system, refer to the Lucent

Technologies Product Warranty Registration Information, which accompanied your

shipment, for instructions on obtaining support in your area.

About Lucent Technologies

History

Lucent Technologies is the communications systems and technology com-

pany formed through the restructuring of AT&T. We bring with us a tradition

of more than 125 years of experience and a dedication to superior customer

service.

Lucent Technologies manufactures, sells, and services a complete line of cus-

tomer premises communications units, and commercial and multimedia

communications and messaging systems designed and supported by ourresearch and development unit, Bell Laboratories.

Our legacy and our spirit of innovation allow Lucent to provide our custom-

ers with the tools needed to communicate effectively, any time and any-

where, and to integrate the latest technologies into real-life solutions that

help make business work.

For More Information

To learn more about the PacketStar PSAX family of Multiservice Media Gate-

ways and the complete line of Lucent Technologies products, visit our Web

site at http://www.lucent.com.

About the PacketStar PSAX Product Family

Lucent Technologies provides a complete range of PSAX Multiservice Media

Gateways in the PacketStar PSAX family.


The PacketStar PSAX 1000 Multiservice Media Gateway is designed to provide

a full range of central office-based multiservice media gateway functions in a

small, competitively-priced package suitable for customer premise deploy-

ment. Ideal for central office, large enterprise, or wireless cell site multiser-vice media gateway applications, the PSAX 1000 system provides highly reli-

able network access for time-division multiplex voice, frame relay,

10/100BASE-T Ethernet, and ATM data applications.

http://www.lucent.com/

http://www.lucent.com/



Chapter 1 Getting StartedAbout the PacketStar PSAX Product Family

1-8 255-700-447


When it is functioning in a redundant operating mode and after it has experi-

enced a single-point failure, the PSAX 1000 system provides up to 630 Mbps

of ATM cell bus capacity. The total ATM cell bus capacity of the system may

also be scaled to provide nonblocking, nonredundant chassis bandwidths

beyond 630 Mbps.

Supporting up to five slots (19–inch chassis) for I/O and server mod-ules—with a full range of interfaces such as DS0A, DS1/E1, DS3/E3, OC-3,

OC-3c/STM-1, OC-12c/STM-4c, 10/100BASE-T Ethernet, and serial—the

PSAX 1000 system is a cost-effective access switch solution for connecting to

legacy equipment.


The PacketStar PSAX 1250 Multiservice Media Gateway is designed to provide

a full range of central office-based multiservice ATM access functions. Ideal

for the central office or a large enterprise’s multiservice media gateway, the

PSAX 1250 system provides highly reliable network access for time-division

multiplex voice, frame relay, 10/100BASE-T Ethernet, and ATM data applica-tions.


enced a single-point failure, the PSAX 1250 system provides up to 600 Mbps



beyond 600 Mbps.

Supporting 10 slots (19-inch chassis) or 14 slots (23-inch chassis) for I/O and

server modules—with a full range of interfaces such as DS0A, DS1/E1,

DS3/E3, OC-3, OC-3c/STM-1, OC-12c/STM-4c, 10/100BASE-T Ethernet,

and serial—the PSAX 1250 system is a cost-effective access switch solution

for interworking with legacy equipment.


The PacketStar PSAX 2300 Multiservice Media Gateway offers carrier-grade,

high-density multiservice ATM access functions. Designed as the multiservice

media gateway for the central office or for a large enterprise customer, the

PSAX 2300 system provides network access for time-division multiplex

voice, frame relay, 10/100BASE-T Ethernet, and ATM data applications.


enced a single-point failure, the PSAX 2300 system provides up to 1.9 Gbps



beyond 1.9 Gbps.

Supporting 15 slots for I/O and server modules—with provisions for OC-3,

OC-3c/STM-1, and OC-12c/STM-4c interfaces with 1:1 protection, 1:1 DS1

module protection switching, and a full range of interfaces such as DS0A,

DS1/E1, DS3/E3, 10/100BASE-T Ethernet, and serial—the PSAX 2300 sys-

tem solves demanding and diverse network design challenges with ease.



255-700-447 1-9


Chapter 1 Getting StartedComments on This Guide


The PacketStar PSAX 4500 Multiservice Media Gateway provides carrier-class

reliability, with an unmatched range of service capabilities, end-to-end traffic

prioritization, “any-service, any-channel” flexibility, and breakthrough voice

technology. Ideal for the central office or a large enterprise multiservice

media gateway, the PSAX 4500 system provides highly reliable networkaccess for time-division multiplex voice, frame relay, 10/100BASE-T Ether-

net, and ATM data applications.


enced a single-point failure, the PSAX 4500 system provides up to 4.2 Gbps



beyond 4.2 Gbps.

The high-performance midplane design supports 15 interface slots. Module

protection for two groups of four or six multiport DS3, STS-1e, or E3 mod-

ules is provided via an N:1 protection scheme using rear access line interface

modules. The protection module provides backup so that on the failure of

any one of the modules in a group, traffic is maintained. A single PSAX 4500

system at the edge of the carrier network can transition traffic from a large

number of network customers over high-speed DS1/E1 IMA, DS3/E3, OC-3,

OC-3c/STM-4c, and OC-12c/STM-4c trunks into the ATM core, managing

the whole quickly and efficiently, down to the individual permanent virtual

circuit.

Through the use of the latest DSP voice technology, the PSAX 4500 system

supports advanced voice traffic over ATM (VToA) services for up to 6048 DS0

channels. As a multiservice media gateway—with H.248 call control, CAS,

PRI, GR-303, and V5.2 protocols, 3-Port DS3/STS-1e, 1-Port OC-3/STM-1

CES, and Tones and Announcements modules—the PSAX 4500 system pro-

vides packet solutions for voice over x DSL, trunking, tandem, and PRI offload

switching.

Comments on This Guide

To comment on the PacketStar ® PSAX 2300 Multiservice Media Gateway User

Guide, please complete the comment card at the following web address:

http://www.lucent-info.com/comments/

You can also email your comments to [email protected].

Include the following information:

Title: PacketStar ® PSAX 2300 Multiservice Media Gateway User Guide

Release number: Release 9.0.0Document number: 255-700-447

Issue number: Issue 1

Publication date: October 2003


mailto:%[email protected]

mailto:%[email protected]




Chapter 1 Getting StartedComments on This Guide

1-10 255-700-447





255-700-447 2-1

2 Hardware Description

Overview of This Chapter

This chapter presents a description of the PacketStar PSAX 2300 Multiservice

Media Gateway system hardware.

System Features

The PacketStar PSAX 2300 Multiservice Media Gateway provides high-capac-

ity, universal connectivity over an asynchronous transfer mode (ATM) wide

area network (WAN).

The PSAX 2300 system is a carrier-grade, high-density ATM multiservice

media gateway that provides network access for TDM voice, frame relay, and

ATM data applications. The PSAX 2300 system I/O interfaces are supported

by a sophisticated package of features, such as PNNI (private network-node

interface), ILMI (integrated local management interface), 1+1 APS (auto-

matic protection switching) and 1+1 MSP (multisection protection), trunk

conditioning, a connection gateway API, and redundant common equipment

modules. Echo cancellation and silence suppression features make the

PSAX 2300 a true multiservice platform. Featuring a 1.9 Gbps ATM cell bus

capacity, carrier-class reliability, Supporting 15 slots for I/O and server mod-

ules—with provisions for OC-3, OC-3c/STM-1, and OC-12c/STM-4c inter-

faces with 1:1 protection, 1:1 DS1 module protection switching, and a full

range of interfaces such as DS0A, DS1/E1, DS3/E3, 10/100BASE-T Ethernet,

and serial—the PSAX 2300 system solves demanding and diverse network

design challenges with ease.

System Hardware Components

The PSAX 2300 Multiservice Media Gateway base system includes the fol-

lowing hardware components (see Figure 2-1):

• Chassis—17.5 in. chassis with mounting brackets for 48.26 cm (19 in.) or

58.2 cm (23 in.) equipment racks

• -48 V dc Power Supply module—two each for redundant operation

(includes cooling fan for power supply and chassis)

• Stratum 3–4 module—two each for redundant operation

The following items are ordered separately to complete the configuration of

the PSAX 2300 system:

• Central processing unit (CPUn (n=2 or 4)) module with the appropriately

installed system software release (see your Lucent Technologies account

manager for ordering information)

• Input/output (I/O) and server modules (see your Lucent Technologies

account manager for ordering information).





255-700-447 2-3


Chapter 2 Hardware DescriptionFunctional Description

The chassis includes a midplane printed circuit board (PCB) designed to pro-

vide an interface between the front and rear panel slots. This design supports

N:1 protection for DS3, E3, and STS-1e modules while continuing to support

over 30 legacy PSAX I/O and server modules.

The Power Supply and Stratum modules operate in a load-sharing mode,

whereas the CPUn modules operate in an active/standby mode. All modulesare hot swappable.

Backplane

The chassis backplane distributes data, clock signals, and power to the mod-

ules. The backplane is based entirely on switching ATM cells. The backplane

has three segments; each segment has two buses, Bus A and Bus B. The

three-segment architecture of the backplane provides several layers of pro-

tection for system resources and functionality. In conjunction with the Stra-

tum 3–4 modules, this architecture provides the basic ATM concentration

technologies of the PSAX 2300 system. The design provides a maximum 3.9

Gbps total bandwidth and allows live (power supplied) insertion of primaryand redundant common equipment modules, and input/output and server

modules.

Power Supply Modules

Two -48 V dc Power Supply modules (see Figure 2-2) converts -48 V dc

power to voltages required by the chassis for normal operation and distrib-

utes power through the midplane to all of the modules in the chassis. The

modules are installed side-by-side below the cable turndown loops and air

filter compartment. Each module includes a variable-speed fan for power

supply and module cooling, status indicators, power connection to distribute

power to the midplane, and inline circuit protection. Facility power and

frame ground are connected to the chassis through the rear-panel connec-

tions.

The modules operate in a load-sharing mode to increase system reliability.

This configuration ensures that as long as one Power Supply module is active,

the entire system is fully powered. Under normal operation, each module

operates at one-half of its capacity. If one Power Supply module fails, the

other module takes over completely.

The variable-speed fans are controlled through the Stratum modules. The

Stratum modules sense the chassis temperature and change the fan speed to

maintain air flow and temperature through the chassis. The fan speed also

increases when the other fan stops operating due to failure or removal.

Circuit protection is provided through two fuses (one for the -48 V dc sideand one for the return side) located on the faceplate of the module.

Three LED indicators on the faceplate indicate the operational state of the

module.




2-4 255-700-447


Stratum 3–4 Module

The PSAX 2300 Stratum 3–4 ANSI-compliant module provides synchroniza-

tion and common equipment monitoring for the PSAX 2300 system. While

fulfilling the normal clock-timing role, the module also serves as a switch,

connecting Stratum A to bus A and Stratum B to bus B on each of the three

segments of the backplane. Therefore, each module supports one of the two

buses that exists on each of the three segments. Given that a single bus seg-

ment operates at approximately 650 Mbps, then the aggregate for the three

segments can be up to 1.95 Mbps. Although the system can operate with one

active module, two modules provide the maximum of 3.9 Gbps of ATM

bandwidth, and offer redundancy to protect service in case one module fails.

With both modules in service, the installed PSAX I/O modules use all buses.

If one module fails, all the I/O modules in the system use the bus from the

remaining Stratum 3–4 module, and system throughput is reduced by half.

In addition, the PSAX 2300 system can obtain network clock synchronization

from any of its interfaces except the Route Server, the DSP2 x Voice Server,

the Voice 2-Wire Station, the Voice 2-Wire Office, the Ethernet, and the

Alarm modules. With the ability to accept a timing reference from any physi-

cal interface at low transmission rates, the PSAX 2300 system provides the

network with a reliable transport and access infrastructure. The Stratum 3–4

module is accurate to Stratum 3 requirements, allowing the PSAX 2300 sys-

tem to run freely even if the module loses external timing for as long as

24 hours, without synchronization problems.

The faceplate of the Stratum 3–4 module has four LED indicators that pro-

vide operational status of the module.

Figure 2-2. -48 V dc Power Supply Module

10 A



255-700-447 2-5



CPU4 Module

The CPU4 module (model 23N20) is a next generation CPU module for the

PSAX 2300 system. With respect to the current CPU2 module, it has

increased processing power, more SDRAM, a larger flash disk, and a second

Ethernet port for future growth capabilities.

Operating in a non-load sharing, primary/standby mode, the CPU4 module

(see Figure 2-3) provides the processing, switching, and storage functions for

the PSAX systems. With a RISC-based microprocessor, the module has the

processing power to maintain data flow, perform numerical calculations, and

manage PSAX system provisioning functions. The module has a 512 MB

compact flash system disk and 512 MB of SDRAM to support routing and sig-

naling functions, forward error correction, processing of SVC connections,

and management of network capabilities.

In a redundant configuration, when upgrading or removing the primary

(active) module, the standby (inactive) module becomes the primary mod-

ule, and the original primary module becomes the standby module. This

switchover is designed to minimize the time the equipment is down for

maintenance.

The standby module supports complete console and SNMP interfaces, in the

same way the primary module supports them, except that the standby mod-

ule does not allow any settings to be modified.

The module also provides a serial console port and two 10/100BASE-T Ether-

net ports to configure and monitor the operation of the PSAX systems. The

ETHERNET2 port is reserved for future enhancements.

The CPU4 module provides the following interoperability:

• When a chassis contains a primary CPU2 module and a CPU4 module is

inserted, the CPU4 module operates in a low-speed mode, identical to the

CPU2 module in all chassis.




2-6 255-700-447


CPU2 Module

Operating in a nonload-sharing, active/standby mode, the CPU2 module (seeFigure 2-4) provides the processing, switching, and storage functions for the

system. With a RISC-based microprocessor, the module has the processing

power to maintain data flow, perform numerical calculations, and manage

the direct memory access (DMA) interfaces. The processor performs the

interface-specific physical and link layer protocol functions, in addition to the

queuing and traffic management functions being performed on the various

I/O and server modules. The module has 128 MB of memory for routing and

signaling functions, forward error correction, processing SVC connections,

and managing network capabilities.

SVC retention preserves active ATM switched virtual connections (SVCs) and

switched permanent virtual connections (SPVCs). However, virtual connec-

tions on calls in a transient state will not be saved. To preserve active virtualconnections, do not remove the active module while it is synchronizing with

the redundant module.

In a redundant configuration, when you upgrade or remove the active mod-

ule, the standby (backup) module now becomes the active module, and the

original active module becomes the standby module. This switchover is

designed to minimize the time the equipment is down.

Figure 2-3. CPU4 Module

ACTIVE

FAIL

STBY

LOAD

CPU4

CONSOLE

ETHERNET 1LINK

TX/RX

LINK

TX/RX

ETHERNET 2



255-700-447 2-7



The standby module supports complete console and SNMP interfaces, in the

same way the active module supports them, except that the standby module

blocks all set operations.

Alarm Module

The Alarm module (see Figure 2-5) provides two connectors that allow for

connections with external facility sensor inputs (doors, temperature, and so

on), chassis alarm outputs (visible and audible), external device controls

(cooling, heating, doors, and so on), and audible alarm cutoff controls (see

Figure 2-6). In addition, the CPUn module generates trap messages that

reflect state changes of the Alarm module’s sensor inputs, control outputs,

and alarm cutoff control.

The Alarm module is functionally identical to the PSAX 4500 Alarm module

(model 45N79) for the PSAX 4500 system, but the module is designed to be

mounted only in the front panel (slot 14) of the PSAX 1250, PSAX 2300, or

PSAX 4500 chassis.

Like all of the other PSAX modules, the Alarm module is monitored and con-

trolled through the console or AQueView EMS. For a detailed description of

the Alarm module, see the PacketStar PSAX Alarm Module User Guide.

Figure 2-4. CPU2 Module

ACTIVE

CPU2

FAIL

ETHERNET

CONSOLE

LOAD




2-8 255-700-447


Figure 2-5. Alarm Module

Figure 2-6. Example Configuration with the Alarm Module

CRITICAL

MAJOR

MINOR

ACO

S T A T U S / C O N

T R O L

A L A R M

Temp. Sensor

Hot

Cold

Fan

CRITICAL

MAJOR

MINOR

ACO

S T A T U S / C O N T R O L

A L A R M

ALARM

Critical Major Minor

Alarms

Output

Input

CO Alarms



255-700-447 2-9


Chapter 2 Hardware DescriptionHardware Specifications

Hardware Specifications

Chassis Specifications

The chassis specifications for the PSAX 2300 chassis are given in Table 2-1.

System Environmental Specifications

The environmental specifications for the PSAX 2300 system are given in

Table 2-2.

Table 2-1. Chassis Hardware Specifications

Specification Description

Slot configuration 19 module slots (15 for user-selected I/O and server mod-

ules, 2 for CPUn modules, and 2 for Stratum 3–4 mod-

ules) and 2 Power Supply module slots

Dimensions 40.0 cm H x 44.7 cm W x 30.48 cm D

(15.75 in. H x 17.6 in. W x 12.0 in. D)

Rack Unit Height: 9

Weight Empty: 8.17 kg (18.0 lb)

Fully populated: 22.29 kg (49.1 lb)

Material AluminumColor Black

Ventilation Forced convection using two variable-speed fans (one per

Power Supply module)

Table 2-2. System Environmental Specifications


Operating temperature range 0° to 50° C (32° to 122° F)

Operating humidity range 5% to 85% relative humidity

Operating altitude range 60 meters (197 feet) below sea level to 4,000 meters

(13,123 feet) above sea level

Storage temperature range -40° to 70° C (-40° to 158° F)

Storage humidity range 0% to 90% noncondensing




2-10 255-700-447


Power Supply Module Specifications

The specifications for the PSAX 2300/4500 -48 V dc Power Supply module

are given in Table 2-3.

Stratum 3–4 Module Specifications

The specifications for the PSAX 2300 Stratum 3–4 module are given inTable 2-4.

Table 2-3. -48 V dc Power Supply Module Specifications


Slot Configuration Two dedicated slots below module slots

Power Voltage range: -42.5 to -56.5 V dc

Rated current: 12.5 A maximum per module

Maximum input power: 470 W (1605 BTU/hr) maximum per

chassis

Maximum output power: 400 W (1366 BTU/hr)

Circuit protection: Two 10 A, wire-type fast acting, black/white

alarm indicating, fuses

Dimensions 9.55 cm H x 26.67 cm D x 21.27 cm W

(3.76 in. H x 10.50 in. D x 8.375 in. W)

Weight 2.37 kg (5.25 lb)

Units per system Two required for redundancy

Connector Two screw-type terminals on the rear panel

Wire/cable size Power feed: two pair of 3.3–2.1 mm2 (#12–14 AWG) stranded

recommended

Frame ground: up to 5.3 mm2 (#10 AWG) stranded recom-

mended.

Table 2-4. Stratum 3–4 Module Specifications


Slot configuration Front two middle slots labeled A and B


(6.2 in. H x 0.6 in. W x 9.5 in. D)

Weight 0.22 kg (0.5 lb)

Units per system 2 required for redundancy

Power consumption 12 W per pair

Synchronization source Internal or external

Accuracy Stratum 3 or 4, selectable

External clock input ANSI/ITU-T Composite (64 kHz), T1BITS (1.544 MHz),

E1ETSI (2.048 MHz), and DS0A Composite (64 kHz)

Connector One RJ-45 (with either 120 ohm or 75 ohm termination)



255-700-447 2-11



CPU4 Module Specifications

The specifications for the CPU4 module are given in Table 2-5.

CPU2 Module Specifications

The specifications for the CPU2 module are given in Table 2-6.

Alarm Module Specifications

Table 2-7 shows the physical and environmental hardware specifications for

the Alarm module.

Table 2-5. CPU4 Module Specifications


Slot configuration Slots 16 and 17


(6.8 in. H x 0.95 in. W x 9.5 in. D)

Weight 308.4 g (0.68 lb)

Units per system 1 for nonredundant operation and 2 for redundant operation

Power consumption 15 W maximum

Processing RISC-based microprocessor

Memory 512 MB compact flash system disk

512 MB SDRAM

Connectors Two RJ-45 connectors labeled ETHERNET1 and ETHERNET2 (reserved

for future enhancements) and one RJ-12 connector labeled CONSOLE

Table 2-6. CPU2 Module Specifications


Slot configuration Slots 16 and 17


(6.8 in. H x 0.95 in. W x 9.5 in. D)

Weight 454 g (1 lb)

Units per system 1 for nonredundant operation and 2 for redundant operation

Power consumption 18 W maximum

Processing RISC-based microprocessor

Memory 140 MB flash drive

128 MB RAM

Connectors One RJ-45 connector labeled ETHERNET and one RJ-12 connector

labeled CONSOLE




2-12 255-700-447


PacketStar I/O and Server Modules Specifications

Table 2-8 provides the general physical hardware and environmental specifi-

cations for the PacketStar PSAX I/O and server modules.

Detailed specifications for the I/O and server modules are described in the

individual module user guides. Environmental specifications for the modules

are described in Table 2-2. .

Module Performance and Power Specifications

Chassis speed, power consumption, and memory allocation specifications for

each PacketStar PSAX module are described in Table 2-9. A functional descrip-

tion for each I/O and server module can be found in Appendix D.

Note: The PSAX 2300 power supply modules are capable of handling any

module configuration. For power supply specifications, see “Power

Supply Module Specifications” on page 2-10

Table 2-7. Physical Hardware Specifications for the Alarm Module



(6.8 in. H x 0.95 in. W x 9.13 in. D)

Weight 360 g (0.8 lb.)Maximum Relay and Sensor Power 1 A at 48 V dc typical, 60 W maximum, 2 A dc maximum

Alarm and Output Control Relays Form 1-C contacts (NC/NO/COM)

Remote status inputs and remote

ACO input

Opto-isolators (IN/COM) for dry contact* relays

* A “dry contact” is a relay contact that does not cause a spark that damages the contacts when they open

and close. This is usually done by placing a resistive component, like another relay, between the relay

contacts and the voltage source.

Table 2-8. Physical Hardware Specifications for PSAX I/O and Server Modules



(6.8 in. H x 0.95 in. W x 9.5 in. D)

Weight 0.45 kg (1.0 lb.), approximate



255-700-447 2-13



Table 2-9. Performance and Power Specifications for the PSAX Modules

ModuleTotal

Amount ofSDRAM

ModuleProgram andData Space

MaximumInput

Buffer*

OutputBuffer†

ChassisSpeed‡

MaximumPower

Consumption

DS1/T1 Interface Modules

20N33 6-Port DS1IMA

16 MB 8 MB 1 MB 7 MB

(114,688)

LowSpeed

18 W

20N36 6-Port

Enhanced DS1/T1

Multiservice


(114,688)

Low

Speed

18 W

23N64 12-Port

Medium-Density DS1

Multiservice

24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

14.5 W

24N64 12-Port

Medium-Density

DS1/E1/DS0A CES

8 MB 8 MB 2 cells/

port

16 cells/

port

High

Speed

11.5 W

23N33 12-Port

Medium-Density DS1

IMA

24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

14.5 W

23N35 24-Port

High-Density DS1

Multiservice

24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

20.5 W

23N69 8-Port

HDSL-224 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

20.5 W

E1 Interface Modules

20N34 6-Port E1

IMA16 MB 8 MB 1 MB 7 MB

(114,688)

Low

Speed

18 W

20N56 6-Port

Enhanced E1

Multiservice


(114,688)

Low

Speed

18 W

23N66 21-Port

High-Density E1

Multiservice

24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

14.5 W

23N34 21-Port

High-Density E1 IMA24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

14.5 W

DS3, E3, and STS-1e Interface Modules

23N60 1-Port

Channelized DS3Multiservice

24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

13 W

23N61 1-Port

Channelized DS3 CES24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

13 W

23N68 1-Port DS3

IMA24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

13 W




2-14 255-700-447


20N03 1-Port

Unchannelized DS3Frame Relay

8 MB 4 MB 1 MB 4 MB

(65,536)

Low

Speed

13 W

20N02 2-Port DS3

ATM8 MB 3 MB 1 MB 4 MB

(65,536)

Low

Speed

15 W

20N22 2-Port E3

ATM8 MB 3 MB 1 MB 4 MB

(65,536)

Low

Speed

15 W

23N03 3-Port

Channelized

DS3/STS-1e CES

8 MB 8 MB 2 cells/

port

16 cells/

port

High

Speed

17 W

23N74 3-Port

DS3/E3 ATM72 MB 8 MB 32 MB 32 MB

(524,288)

High

Speed

12 W

23N02 3-Port

Unstructured DS3/E3

CES

N/A 8 MB 2 cells/

port

16 cells/

port

High

Speed

7 W

45N02 3-Port

Unstructured DS3/E3

CES Protection

N/A 8 MB 2 cells/

port

16 cells/

port

High

Speed

7 W

23N62 1-Port

Channelized STS-1e,

T1 Format

24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

13 W

Fiber-Optic Interface Modules

23N75 1-Port

Channelized OC-

3/STM-1 Unstructured

CES/ATM Multimode

8 MB 8 MB 64 MB 64 MB

(1,048,576)

High

Speed

10 W

23N76 1-Port

Channelized

OC-3/STM-1

Unstructured

CES/ATM Single-Mode

8 MB 8 MB 64 MB 64 MB

(1,048,576)

High

Speed

10 W

23N12 1-Port

Channelized

OC-3/STM-1 CES

Multimode

8 MB 8 MB 2 cells/

port

16 cells/

port

High

Speed

17 W

23N13 1-Port

Channelized

OC-3/STM-1 CES

Single-mode

8 MB 8 MB 2 cells/

port

16 cells/

port

High

Speed

17 W

20N12 1-Port OC-3c

Multimode with

AQueMan

8 MB 3 MB 2.5 MB 2.5 MB

(40,960)

Low

Speed

15 W

Table 2-9. Performance and Power Specifications for the PSAX Modules (Continued)

ModuleTotal

Amount ofSDRAM


MaximumInput

Buffer*

OutputBuffer†

ChassisSpeed‡

MaximumPower

Consumption



255-700-447 2-15



20N13 1-Port OC-3c

Single-Mode withAQueMan

8 MB 3 MB 2.5 MB 2.5 MB

(40,960)

Low

Speed

15 W

20N14 1-Port OC-3c

Multimode with Traffic

Shaping

8 MB 3 MB 3 MB 2 MB

(32,768)

Low

Speed

15 W

20N15 1-Port OC-3c

Single-Mode with

Traffic Shaping

8 MB 3 MB 3 MB 2 MB

(32,768)

Low

Speed

15 W

20N72 1-Port OC-3c

1+1 APS Multimode32 MB 8 MB 12 MB 12 MB

(196,608)

Low

Speed

11.5 W

20N73 1-Port OC-3c

1+1 APS Single-Mode

32 MB 8 MB 12 MB 12 MB

(196,608)

Low

Speed

11.5 W

24N70 2-Port

OC-3c/STM-1 ATM

Multimode

72 MB 8 MB 32 MB 32MB

(524,288)

High

Speed

12 W

24N71 2-Port

OC-3c/STM-1 ATM

Single-Mode

72 MB 8 MB 32 MB 32MB

(524,288)

High

Speed

12 W

24N72 4-Port

OC-3c/STM-1

Multimode

72 MB 8 MB 32 MB 32MB

(524,288)

High

Speed

18 W

24N73 4-Port

OC-3c/STM-1Single-Mode

72 MB 8 MB 32 MB 32MB

(524,288)

High

Speed

18 W

20N62 1-Port

STM-1 Multimode with

AQueMan

8 MB 3 MB 2.5 MB 2.5 MB

(40,960)

Low

Speed

15 W

20N63 1-Port

STM-1 Single-Mode

with AQueMan

8 MB 3 MB 2.5 MB 2.5 MB

(40,960)

Low

Speed

15 W

20N64 1-Port

STM-1 Multimode with

Traffic Shaping

8 MB 3 MB 3 MB 2 MB

(32,768)

Low

Speed

15 W

20N65 1-Port

STM-1 Single-Mode

with Traffic Shaping

8 MB 3 MB 3 MB 2 MB

(32,768)

Low

Speed

15 W

20N92 1-Port

STM-1 1+1 MSP

Multimode

32 MB 8 MB 12 MB 12 MB

(196,608)

Low

Speed

11.5 W


ModuleTotal

Amount ofSDRAM


MaximumInput

Buffer*

OutputBuffer†

ChassisSpeed‡

MaximumPower

Consumption




2-16 255-700-447


20N93 1-Port

STM-1 1+1 MSPSingle-Mode

32 MB 8 MB 12 MB 12 MB

(196,608)

Low

Speed

11.5 W

23N72 1-Port

OC-12c/STM-4c

Multimode

72 MB 8 MB

(SDRAM)

1 MB

(SRAM)

32 MB 32 MB

(524,288)

High

Speed

13 W

23N73 1-Port

OC-12c/STM-4c

Single-Mode

72 MB 8 MB

(SDRAM)

1 MB

(SRAM)

32 MB 32 MB

(524,288)

High

Speed

13 W

Voice 2-Wire Interface Modules

20N32 4-Port Voice

2-Wire Office8 MB 4 MB N/A N/A Low

Speed

14 W

20N30 8-Port Voice

2-Wire Station8 MB 4 MB N/A N/A Low

Speed

15 W

Serial Interface Modules

23N07 Quadserial 24 MB 7 MB 4 MB 13 MB

(212,992)

Low

Speed

15 W

20N07 6-Port

Multiserial8 MB 3 MB 1 MB 4 MB

(65,536)

Low

Speed

15 W

Ethernet Interface Modules

23N40 4-Port

Ethernet

32 MB§ 8 MB 24 MB¶ N/A High

Speed

13 W

20N40 Ethernet 64 MB 8 MB 4 MB 4 MB

(65,536)

Low

Speed

16 W

DSP2 Voice Servers

23N27 DSP2C Voice

Server

1 MB

(SRAM)

512 KB

(SRAM)

N/A N/A Low

Speed

17 W

23N29 DSP2D Voice

Server2 MB

(SRAM)

2 MB N/A N/A High

Speed

15 W

23N26 DSP2E Voice

Server2 MB

(SRAM)

2 MB N/A N/A High

Speed

13 W

23N25 DSP2F VoiceServer

2 MB(SRAM)

2 MB N/A N/A HighSpeed

13 W

Other Server Modules

23N41 Enhanced

Router512 MB** 490 MB N/A N/A High

Speed

18 W

20N41 Route Server 64 MB 8 MB N/A N/A Low

Speed

15 W


ModuleTotal

Amount ofSDRAM


MaximumInput

Buffer*

OutputBuffer†

ChassisSpeed‡

MaximumPower

Consumption



255-700-447 2-17



23N28 Tones and

AnnouncementsServer

1 MB

(SRAM)

512 KB

(SRAM)

N/A N/A Low

Speed

17 W

Alarm Module

20N79 Alarm N/A N/A N/A N/A N/A 3 W

Stratum 3–4 Module

PSAX 2300 Stratum

3–4N/A N/A N/A N/A N/A 6 W

CPU Modules

20N20 CPU2 128 MB N/A N/A N/A N/A 18 W

23N20 CPU4 512 MB N/A N/A N/A N/A 15 W

* On all PSAX I/O modules, except the 4-Port Voice 2-Wire Office and the 8-Port Voice 2-Wire Station mod-

ules, the I/O buffers carry 16,384 cells per megabyte. The PSAX server modules carry no cells on the I/O

buffers. Any module with 24 MB SDRAM can buffer only 16,384 packets, or approximately 682 packets

per megabyte. Traffic on the 4-Port Ethernet module is buffered packet by packet, not cell by cell.† Indicates the size of the output buffer followed by the maximum number of 64-byte cells in the output

buffer.‡ This column relates only to the speed at which the module communicates within the chassis. A high-speed

module will communicate at high speed (1.2 Gbps) in a chassis that has a high-speed bus (PSAX 4500

chassis). High-speed modules will communicate at 600 Mbps in any other chassis. Low-speed modules will

always communicate at 600 Mbps in any chassis.§ The total SDRAM for this module includes 2 MB of SRAM.¶ The value 24 MB refers to the maximum data buffer (input and output buffers combined).

** The SDRAM listed only takes into account the memory associated with the upper layer processor. It does

not take into account the fastpath processor (firmware) or the hardware reassembly buffers.


ModuleTotal

Amount ofSDRAM


MaximumInput

Buffer*

OutputBuffer†

ChassisSpeed‡

MaximumPower

Consumption




2-18 255-700-447





255-700-447 3-1

3 System Features


This chapter presents an overview of the PSAX 2300 Multiservice Media

Gateway system (PSAX 2300) and software features. The following aspects of

the PSAX 2300 system are discussed:

• Features and capabilities of the system

• Architecture, interfaces, and functions

System Capabilities

User Benefits

The PSAX 2300 system enables service providers, central offices, or end users

at customer premises to consolidate voice, video, and data traffic on a single

ATM network, and to extend the capabilities of embedded ATM-based equip-

ment to voice and video traffic.

The PSAX 2300 system offers a variety of user interfaces to support voice,

video, and data applications. While voice, video, and data traffic have tradi-

tionally been carried on separate overlay networks, the PacketStar Multiser-

vice Media Gateway systems aggregate all traffic types into a common net-

work infrastructure. Even though such consolidation means that traffic, in

effect, competes for the same physical resources, the traffic management and

bandwidth utilization capabilities of the Multiservice Media Gateway systems

help to ensure that the required quality-of-service (QoS) levels are satisfied

within the available constraints of the network.

Feature Highlights

Important features of the PSAX systems include:

• Variable-speed ATM access technology, implemented using the physical

layer protocol LANET (Limitless ATM Network Protocol), efficiently adapts

ATM to high-noise wireless and satellite environments.

• An advanced queuing and cell-switching algorithm, provided by the AQue-

Man (adaptive queue management) firmware algorithm, a patented tech-

nology offered by Lucent Technologies to differentiate voice, video, anddata requirements. The AQueMan algorithm maximizes bandwidth effi-

ciency while ensuring QoS on a congested network.

• A cell-counting capability to allow network data collection systems to gen-

erate ATM usage-based billing reports



Chapter 3 System FeaturesInterface Architecture

3-2 255-700-447


• A connection gateway application programming interface (API) that pro-

vides an interface to the PSAX 2300 by which an external workstation

(gateway) can control the PSAX 2300 ATM switching, using non-native

ATM networking protocols

Through the use of the API, the gateway and the PSAX 2300 can combine

to perform powerful interworking among ATM, Integrated Services DigitalNetwork (ISDN), Signaling System 7 (SS7), channel associated signaling

(CAS), and other protocols

• Inverse multiplexing over ATM (IMA) to create virtual access lines that are

faster than E1 lines, but not as expensive as T3/E3 lines

• Live insertion and removal of modules

• An integrated local management interface (ILMI) feature that supports

bidirectional exchange of ATM interface parameters between two con-

nected ATM interface management entities (IMEs) using Simple Network

Management Protocol (SNMP) and an ATM interface management infor-

mation base (MIB)

• An alternate rerouting feature, known as dual-homed permanent virtual

circuits (DHPVCs), that improves reliability of PVC connections and sup-

ports redundancy options to deliver near-zero downtime using circuit

emulation, terminal emulation, frame relay, Ethernet, and ATM interfaces

• A switched virtual circuit (SVC) feature that provides dynamic allocation of

connections by using Interim Interswitch Signaling Protocol (IISP) or Pri-

vate Network-to-Network Interface (PNNI) for call setup and (automatic)

rerouting

• A soft PVC (SPVC) feature, which is a semipermanent virtual connection

used for call setup and (automatic) rerouting that has attributes of both a

switched virtual connection and a permanent virtual connection

• PNNI, which computes paths through a network by defining a method for

distributing topology information between switches and clusters of

switches. PNNI also provides a method for signaling used to establish point-

to-point and point-to-multipoint connections across ATM networks

• An operations, administration, and maintenance (OAM) feature that

affects the system software and input/output (I/O) module firmware asso-

ciated with generating, receiving, and interpreting F4 and F5 OAM flows.

The function types of the OAM cells include fault management, perfor-

mance management, and system management

• A keep-alive/heartbeat timer to confirm that connections are live

• Unidirectional connection and path modification

• The Firmware Release Control feature that allows upgrading both CPU

software and I/O module firmware at a user site from either a CD-ROM or

a downloaded FTP software file

Interface Architecture

The PSAX system interface architecture distinctly separates the ATM adapta-

tion functions from the switching functions of the Multiservice Media Gate-

way system. The interface architecture has four distinct processes:



255-700-447 3-3


Chapter 3 System FeaturesConnections Supported

• Physical media access—The physical media access layer handles functions

specific to each physical interface, connecting each user port to other users

or network elements.

• Service protocol translation—The service protocol translation process per-

forms segmentation and reassembly (SAR) to adapt non-native ATM ser-

vices to ATM-based services and back again. It ensures that the data streamis mapped to standard ATM Adaptation Layer (AAL) protocols.

• ATM addressing—ATM addressing provides user-specified virtual path

identifier/virtual channel identifier (VPI/VCI) coding, bandwidth alloca-

tion, and quality of service (QoS) information.

• Queuing—Queuing provides a means through which ATM cells are placed

in input and output queues based on their QoS parameters. Employing the

AQueMan adaptive queue management algorithm, the PSAX 2300 Multi-

service Media Gateway transports these cells from the ATM switching fab-

ric to the I/O port.

Connections SupportedThe Multiservice Media Gateway system software uses permanent virtual cir-

cuits (PVCs) and switched virtual circuits (SVCs) to provide end-to-end con-

nectivity for transmission over a network. Because virtual connections are

logical and not physical, multiple connections can be defined simultaneously

across a single network facility, with each connection having flexible band-

width.

Because PVCs establish end-to-end connections, a PVC eliminates the need

to establish a new route (call setup) each time a transmission is sent to a

remote location. When establishing a connection with a PVC, the user only

needs to select a class of service for each connection.

Permanent Virtual Circuit (PVC) Connections

A permanent virtual circuit is established on one side of a packet-switching

network, between interfaces of two or more data or voice processing elec-

tronic components. Unlike a virtual circuit, after a PVC is established, it func-

tions as the equivalent of dedicated private line service, requiring no setup

and disconnect after data or voice signals are passed between a startpoint and

endpoint.

Soft Permanent Virtual Circuit (SPVC) Connections

The SPVC feature is a semipermanent virtual circuit enabled by management

action. It is a PVC circuit in which SVCs are used for call setup and (auto-

matic) rerouting. Once either a PVC or a permanent VPC has been config-

ured, an SPVC can be established between the two network interfaces serv-

ing the PVC by using signaling procedures. Consequently, this type of

connection has attributes of both an SVC and a PVC.




3-4 255-700-447


Specifically, an SPVC is established and released between the two network

interfaces serving the PVC. The user assigns unique ATM addresses, including

the SEL octet in the case of a private ATM address (see Section 3.1 of the UNI

4.0 signaling specification), to the corresponding NIs, thus identifying the

starting point and ending point of the SPVC.

This feature supports ATM-to-ATM VPC at both ends of a network interface.

It uses ATM UNI 4.0 or ATM PNNI 1.0 protocol to set up the SVC connection

depending on the egress route/protocol selected and based on the called

party number and TNS given by the NMS on initiation.

Also offered are DSP2D Voice Server processing options (including voice

compression, silence detection, echo cancellation, tone detection, and PCM

translation) for voice traffic on SPVC connections between two or more

PacketStar PSAX systems.

This feature is available on all PSAX I/O modules supporting SPVCs for ATM.

The standard AAL2 SPVC connection types provide an alternate means of

achieving switched trunking of voice calls using PVCs. These connectiontypes are used in an API or in the H.248 feature and provide another means

for ConnectStar or third-party softswitch software to support switched trunk-

ing of voice calls. The VBR-to-ATM Standard AAL2 VCC SPVC connection

type supports the Packet Pipe functionality.

SPVC ReconnectionPriority Scheme

Nonprioritized SPVCs will be reconnected on a first-come-first-serve basis.

However, since legal requirements require that 911 emergency voice chan-

nels be the last connections to be dropped, 911 emergency calls must be

reconnected first. To ensure that 911 wireless SPVC connections are not

affected in the event of failure by any ATM IMA links, the SPVCs are recon-

nected according to a user-defined priority code 1 through 6. The user-

assigned reconnection priority 1 is the highest reconnection priority forSPVCs. The priority code is assigned in the Priority field on all SPVC connec-

tion configuration windows except the Circuit Emulation-to-ATM Standard

AAL2 VCC SPVC connection and VBR-to-ATM Standard AAL2 VCC SPVC

connection. For these latter two connection types, the priority code is set on

the ATM Trunking Bearer VCC Configuration window.

Prior to System Software Release 7.1.4, the PSAX system provided only two

levels of priorities for IMA link reconnection after failure:

1. PVCs are not affected.

2. All non-PVC connections are reconnected in a random order.

With Release 7.1.4 and subsequent releases, users determine and assign how

many reconnection priority classes they need for their non-PVC connections.See Table 3-1 for a sample priority scheme for a customer running TDMA

protocol migrating to GSM.



255-700-447 3-5



The SPVC Priority Reconnection feature supports all SPVC connection types.

All SPVCs compress voice when configured with the appropriate DSP2 x Voice

Server module. SPVC connections are rerouted in the event of link failure.

Figure 3-1 shows some sample user-assigned priority SPVCs.

The priority reconnection scheme is invoked by one of the following events:

• Chassis reboot

• IMA link failure followed by SPVC reconnection attempts

Upon IMA link failure, all SVC and SPVC calls are disconnected. SPVC calls

are then reconnected according to the priority scheme designated by the

user.

A PSAX system using the user-defined reconnection priority scheme must

meet the following requirements:

• Only active-side SPVCs are permitted in the configuration (no SVCs)

Table 3-1. Sample User-Defined Priority Scheme for Reconnecting SPVC ATM IMA Links

User-AssignedPriority Code

Traffic Type Typical ATM Service Type

1 TDMA/CDMA control channels

AMPS channel reserved for 911emergency calls

CBR-1 or VBR-express

CBR-2

2 GSM control channels VBR-express

3 Digital voice channels VBR-express

4 GSM voice channels CBR-2

5 Most analog voice channels VBR-rt2 (will now try CBR-3)

6 Management data connections UBR

Figure 3-1. Sample SPVC Reconnection Prioritization Scheme

AAL2CIDs

(max. 247)

AAL2CIDs

(max. 247)

DS1/T1 IMA Link

Sample Priority 2,

Sample Priority 1,

Sample Priority 0,

A

B

C PVC

AAL2 Trunk for HDLC SPVC

AAL2 Trunk for CE SPVC

PSAX System

A

B

C




3-6 255-700-447


• The maximum total number of AAL2 SPVC trunk connections in the chas-

sis must not exceed 32.

• The ATM uplink must be a 6-Port DS1 IMA module.

• The PSAX with the priority system enabled will work with a PSAX with

passive side SPVCs that has the priority system disabled.

Note: No preemption of existing connections is supported. Any existing

SVC, PVC, and SPVC connections will not be disconnected to

secure bandwidth for new connections.

Modification ofParameters for ActiveSPVC Connections

Users can now modify traffic descriptors for active ATM-to-ATM VCC SPVC

connections. In previous releases, modifying traffic descriptors required

deleting the connection and creating another one with new traffic descrip-

tors. Tearing down and recreating a connection involves two risks:

• The connection’s clients might detect the deletion of the SPVC and take

action.

• A different connection request may seize the resources as they are freed bythe release of the deleted connection.

The ability to modify an ATM-to-ATM VCC SPVC while it is active eliminates

these two risks.

Switched Virtual Circuit (SVC) Connections

Switched virtual circuit (SVC) connections are used for voice traffic over a

public ATM WAN or private line network. SVCs are supported on all the ATM

cell-bearing interfaces, including the DS3, E3, OC-3c, STM-1, Multi-Serial,

and High Speed modules. The Multiservice Media Gateway system software

supports the following features:

• Each ATM port on a single module can be individually configured for ATM

UNI 3.0, UNI 3.1, IISP user, IISP network, or PNNI interfaces.

• SVCs can be allocated on UNI (public and private), IISP, and PNNI inter-

faces.

• Point-to-point and point-to-multipoint VCC connections are supported.

• VCC connections support both symmetric and asymmetric bandwidth

requirements.

• An Multiservice Media Gateway system can process 60 calls per second.

Maximum limits include 100 UNIs per system; 5,000 simultaneous point-

to-point SVC call originations, and 2,000 point-to-multipoint call origina-

tions.

• An Multiservice Media Gateway system (equipped with 64 MB of memory

on the CPU module) can process a maximum of 20,000 simultaneous SVC

calls in progress.

• The maximum individual call setup time is 16 milliseconds (ms). The mini-

mum call setup time for SVCs is approximately 10 ms from the time the

call setup message enters the CPU module until the acknowledgment

leaves the CPU module.



255-700-447 3-7



SVC FunctionalDescription

SVC signaling, per ATM Forum UNI 3.0 and UNI 3.1, is selectable on a per-

port basis. Call control is performed on the CPU module, including manage-

ment of the call-state transitions for each of the calls. This process allows on-

demand allocation of bandwidth and connection resources. The signaling

protocol supports the following basic functions at the UNI interface:

Call States Call states exist on both the user side and the network side of the transaction.

Call states define which messages can be accepted by the user or the network

entity, and define how they are expected to react to those messages. As theuser or network entity moves from call state to call state, the call switching

process is accomplished.

In cases where the calling party is the user, and the called party is across the

network, the user-side interface (UNI) at the Multiservice Media Gateway

port presents a UNI to the user. The Multiservice Media Gateway port

receives these user-side messages from the user and—based on resource

availability, route determination, and other network factors—presents a net-

work-side interface (NNI or IISP) to the called party or the network-side

Multiservice Media Gateway port.

Both user-side and network-side interfaces undergo similar state transitions.

Transition messages trigger these call-state changes as follows:

Feature Description

Connection/Call Setup With this feature, calls originate and are established.

Connection/Call Request With this feature, requests of resources for connections to

a certain destination are fulfilled. The Information Ele-

ment (IE) field contains resource information including

PCR, SCR, MBS, and QoS class.

Connection/Call Answer With this feature, the destination party can respond to a

request with VPI/VCI and other information related to the

connection/call.

Connection/Call Clearing With this feature, the information associated with remov-

ing the call/connection request is provided. This includes:

1) calls removed because there weren’t enough resources

to meet the call request, 2) connections removed when

call disconnect requests were received from either party,

and 3) calls removed due to link failure and other net-

work failures.

Reason for Clearing With this feature, the clearing party can indicate the cause

for initiating its removal from a connection/call.




3-8 255-700-447


Call States Description

#0—Null No call exists.

#1—Call initiated • User—The user has requested that the system establish an

outgoing call on the network.• Network—The network has received the call establishment

request, but has not yet responded to the outgoing call.

#3—Outgoing call

proceeding

• User—The user has received an acknowledgment that all

call information required for the outgoing call to be estab-

lished has been received from the network.

• Network—The network has sent an acknowledgment to

the user that all call information has been received.

#6—Call present • User—For incoming calls, the user has received the call

establishment request, but has not responded yet.

• Network—For incoming calls, the user has sent the call

establishment request, but has not received a satisfactoryresponse.

#8—Connect request • User—For incoming calls, when the user has answered the

call and is waiting to be awarded the call.

• Network—For incoming calls, when the network has

received an answer but the network has not yet awarded

the call.

#9—Incoming call

proceeding

• User—For incoming calls, when the user has sent acknowl-

edgment that the user has received all call information nec-

essary to establish a call.


received acknowledgment that the user has received all call

information necessary to affect call establishment.

#10—Active • User—For incoming calls, when the user has been awarded

the call. For outgoing calls, when the user has received an

indication that the remote user has answered the call.


awarded the call to the called user. For outgoing calls,

when the network shows that the remote user has

answered the call.

#11—Release

request

• User—The user has requested that the network clear the

end-to-end connection and is waiting for a response.

• Network—The network has requested a request from the

user to clear the end-to-end connection.

#12—Release indica-

tion

• User—The user has received an indication to disconnect

because the network has disconnected the end-to-end con-

nection.

• Network—The network has disconnected the end-to-end

connection and has sent an indication to disconnect the

user-to-network connection.



255-700-447 3-9


Chapter 3 System FeaturesUser Interfaces

The following state transition messages are used for ATM point-to-point call

and connection control:

• The information elements used in the Call Establishment-Setup message

allow the user to request the called party number, specific PCR, SCR, MBS,

QoS class, forward and backward direction rates, performance, congestioncontrol parameters, and so on, from the Multiservice Media Gateway UNI.

The Call Establishment-Connect message allows the called party to respond

with available traffic parameters, such as PCR, SCR, MBS, QoS class, for-

ward and backward direction rates, performance, congestion control

parameters, and so on. Usually this message also indicates the available

VPI/VCI allocated for the connection. The other state-transition messages

are specified by the ATM Forum UNI 3.0 and UNI 3.1 specifications and are

transparent to the user.

User Interfaces

The PSAX 2300 offers a variety of user interfaces to support voice, video, anddata applications.

Circuit Emulation Service

Circuit emulation service transports traffic over a virtual channel-based con-

nection, providing service to the end user that is indistinguishable from a real

point-to-point, fixed-bandwith circuit. The PacketStar PSAX Multiservice

Media Gateways support structured circuit emulation (individual DS0 circuit

emulation) of traditional voice-based and data services on the DS1 and E1

modules. Because voice services are essentially constant bit rate (CBR) data,

ATM Forum ATM Adaptation Layer 1 (AAL1) standards are used in circuit

emulation. The circuit emulation service also provides signaling bit transport based on ATM Forum standards for channel-associated signaling (CAS).

The PacketStar Multiservice Media Gateways provide AAL1 circuit emulation

at the DS0 level. The individual DS0 modes of structured circuit emulation

allow service providers to switch time-division multiplexing (TDM) traffic

across the ATM network at individual subscriber levels; that is, each DS0 can

be assigned a separate virtual path identifier (VPI) or virtual channel identi-

fier (VCI). This service transports ABCD signaling bits based on the ATM

Call establishment messages: • Call proceeding

• Connect

• Connect acknowledgment

• Setup

Call clearing messages: • Release

• Release complete

Miscellaneous messages: • Status

• Status inquiry




3-10 255-700-447


Forum standard for G.704 CAS. M13 multiplexing capabilities are also sup-

ported, providing the ability to perform circuit emulation on a T1 or E1 link

connected to a TDM network and convert it into ATM cells, in accordance

with the ATM Forum CAS specification af-saa-0032.000. Each T1 or E1 carries all

of the Extended Super Frame (ESF) information required for a full T1 or E1

in cases where the interfaces to the service access multiplexer (SAM) are afull T1 or E1. The Multiservice Media Gateways can convert superframe (SF)

format to ESF format. Signaling from any input interface (including customer

premises equipment [CPE] interfaces) is converted to the appropriate signal-

ing on the output interface. Framing information is converted and assign-

ments are made on an individual DS0 basis.

Voice frames are converted into ATM cells based on the ATM Forum Circuit

Emulation Service Interoperability Specification Version 2.0, af-vtm-0078.00. The

DS0 mode of structured circuit emulation transparently supports voice appli-

cations in a network environment.

SPVC Support for CES Also offered are DSP2C through DSP2F Voice Server processing options

(including voice compression, silence detection, echo cancellation, tonedetection, and PCM coding translation) for voice traffic on soft permanent

virtual circuit (SPVC) connections between two or more PacketStar PSAX

systems.

Circuit EmulationService for theMultiserial Module

Circuit emulation to ATM connections made through the Multi-Serial mod-

ule now support 56 Kbps to 64 Kbps bit stuffing for SS7 link transport appli-

cations. Bit stuffing is selectable on a port basis by using the CPU software.

Dynamic Bandwidth Circuit Emulation ServiceThe dynamic bandwidth circuit emulation service (DBCES) feature is used

with voice PVC connections to best utilize the available network bandwidth.

This feature allows channels to be allocated dynamically as needed, based on

ABCD signaling-bit information. The firmware supports 1x56 Kbps time-slot

trunking with channel-associated signaling (CAS) detection used, based on

ATM Forum Specification af-vtoa-0085.000. Note that this feature is not fully

compliant with the specification and does not interoperate with other devices

that are fully compliant.

The DBCES feature, in essence, performs idle channel suppression for voice

traffic. PBX voice traffic uses DBCES to save some of the available T1 WAN

bandwidth for LAN traffic. On average, only 8 DS0s are used for voice traffic,

but at peak times, the number of DS0s used might approach the full 24 T1channels. When channels are not being used for voice traffic, the available

bandwidth can be used for LAN UBR-class traffic.



255-700-447 3-11



Dynamic CAC

Connection Admission Control (CAC) is used to determine if a connection

set-up request can be supported by available resources. When a PSAX system

initializes, the CAC algorithm determines, in a static sense, the maximum

available bandwidth for each interface. As connections are created anddeleted, CAC keeps a running tally on available bandwidth so that it can

determine if new connections can be supported.

In general, since the maximum available bandwidth of an interface is fixed

(that is, DS1=1.536 Mbps), a static approach is usually sufficient. However,

there are exceptions. Dynamic CAC Phase 1 supports the potentially chang-

ing nature of inverse multiplexing for ATM (IMA) groups and accounts for

increases or decreases in the maximum available bandwidth of the interface

due to additions or deletions of component links. Phase 2 permits a user to

change DS3 ATM payload mapping from PLCP to direct mapping (which also

alters the maximum available bandwidth) without taking the interface out of

service or deleting existing connections.

DS1 Service

With the channelized DS1 interface, service providers can concentrate and

adapt voice, video, and data traffic to an ATM network. The DS1 interface

can adapt any number of DS0 channels on the service access interface to

ATM virtual channels with individual virtual path identifiers (VPIs) and vir-

tual channel identifiers (VCIs). Users can thus adapt traffic to ATM at the

individual DS0 level; that is, using structured circuit emulation, frame relay,

HDLC, and native ATM services. The PSAX 2300 system also offers unstruc-

tured circuit emulation on the service interface of the DS1 interface.

DS3 Service

With the PSAX 2300 system, service providers can also now concentrate the

various ATM circuits onto an upstream interface to an ATM edge switch, typ-

ically at the DS3 rate. With the DS3 interface, service providers can concen-

trate various traffic types up to 45 Mbps. The DS3 ATM module, designed to

meet the ATM Forum UNI 3.0 specifications, serves as an interface to the ser-

vice provider’s ATM edge switch. Each DS3 ATM module supports two 45-

Mbps DS3 ports.

HDLC Passthrough Bit Inversion

The High-level data link control (HDLC) Passthrough Bit Inversion featureuses an ITU-TSS link layer protocol standard for point-to-point and point-to-

multipoint communication. To reduce framing errors, control information is

always placed in the same position in the traffic stream, and the control bit

pattern is different from the data bit pattern. Providers are using this feature,

primarily in wireless TDMA applications with ATM, to save money by using

ATM for backhauling calls from wireless cell sites to mobile switching centers,




3-12 255-700-447


instead of using time division multiplexing (TDM). By inverting the HDLC

frame bits, fewer bit value 1s (ones) are transmitted in the backhaul data,

providing additional savings.

The bit inversion process uses the new 5ESS switches that support a mixture

of inverted and standard HDLC passthrough interfaces. The HDLC

Passthrough Bit Inversion feature is enabled by a console screen field value

selection.

The HDLC Bit Inversion feature is supported on the following PSAX modules:

Interim Interswitch Signaling Protocol (IISP) Interface

Interim Interswitch Signaling Protocol (IISP) was formerly known as PNNI

Phase 0. Building on the ATM UNI 3.0/3.1 standard, IISP uses static routing

tables established by the network administrator to route connections around

link failures. IISP is meant to be used pending completion of the PNNI

Phase 1. See “Interface Type by Input/Output Module Type” on page C-31 for

Table C-7 that lists the supporting modules for this interface.

Private Network-Network Interface (PNNI) 1.0

Overview The private network-to-network interface, known as PNNI, is a link state

protocol. This protocol enables extremely scalable, full function, dynamic

multivendor ATM switches to be integrated in a network. PNNI protocol

computes paths through a network by defining a method for distributing

topology information between switches and clusters of switches. This infor-

mation is used to compute paths through the network, whether it is local or

worldwide. The hierarchy mechanism of PNNI ensures that this protocol

scales well for any size ATM network, and automatically configures itself in

networks in which the address structure reflects the topology.

PNNI provides a method for signaling used to establish point-to-point and

point-to-multipoint connections across ATM networks. PNNI is based on theATM Forum UNI signaling, with mechanisms added to support source rout-

ing, crankback and alternate routing of all call setup requests in case of con-

nection setup failure.

The path selections for specific calls are based on route options provided by

PNNI messages. Load sharing between parallel paths is addressed by the

route determination algorithm, which provides options for such factors as

load sharing, cost, and override options.

23N64 12-Port Medium-Density DS1 Multiservice

23N35 24-Port High-Density DS1 Multiservice

23N66 21-Port High-Density E1 Multiservice

23N60 1-Port Channelized DS3 Multiservice

23N62 1-Port Channelized STS-1e, T1 Format



255-700-447 3-13



Phase 3 of the Private Network-Network Interface feature enhancement

includes the additions of functionality from the ATM Forum PNNI standard

af-pnni-0055.000 Annex F , Hierarchy Configuration, and Appendix G, Minimum

Subsets (all border node capable switching systems features). Ten hierarchal

levels are supported.

The PSAX 2300 allows up to 65,535 nodes (2 MB of memory), 100 PNNI

links per interface, 20 PNNI summary addresses, 50 PNNI advertised routes,

and 20 administrative weight entries per PNNI route.

The PNNI, Phase 4, (PNNI Over VPC) feature enables the PSAX system to

support one PNNI interface per VPC, as opposed to one PNNI interface per

physical port. This feature is used to tunnel multiple PNNI interfaces over a

public ATM network, or an ATM network that does not support PNNI, by

enabling signaling protocols to be carried transparently over the ATM net-

work. PNNI Over VPC can also be used to connect several end systems or

switches through a VP multiplexer.

The PNNI Over VPC feature can be used with modules that provide ATM UNI

virtual interfaces (VIs) and is supported on the following PSAX connections:• Point-to-point and point-to-multipoint SPVC, SVC, and PVC

• CES to ATM SPVC, FR to ATM SPVC, and ATM to ATM SPVC

• AAL2 SVC and SPVC

PNNI FeaturesSupported by thePSAX Systems

The following is a list of PNNI features supported for the PSAX systems:

• Multiple peer group hierarchy

• Alternate routing as a result of crankback

• CBR, rt-VBR, nrt-VBR, and UBR service

• Hello protocol

• Peer group leader election algorithm

• Point-to-point SVC and SPVC connections

• Point-to-multipoint SVC and SPVC connections

• Transfer of incoming extended Quality of Service (QoS)

• End-to-end transit delay parameters to outgoing PNNI interfaces

• Topology database synchronization

• PNNI topology state element (PTSE) aging within topology databases

• Summation and advertising of reachable addresses

• Source path selection and generic connection admission control (GCAC)

PNNI Peer GroupDynamics

PNNI performs these functions:

• Simplifies the configuration of large networks because it allows ATM

switches to automatically learn about their neighbors and to distribute call

routing information dynamically.

• Allows switches to be arranged in a hierarchy, where each level represents

one or more switches. A cluster of switches at the same level is called a

peer group. Link-state topology updates circulate within a peer group.




3-14 255-700-447


• Allows up to 10 levels in a hierarchy but does not require them. It is also

possible to deploy PNNI with one peer group encompassing all switches

within a network.

• Sends hello packets across interswitch network-to-network interface (NNI)

links that enable switches in the same peer group to discover one another.

After a switch confirms that its neighbor at the other end of a link is amember of the same peer group, both exchange PNNI topology state pack-

ets (PTSPs) to advise and update their call routing information. PTSPs carry

one or more PTSEs, describing the resources of the originating switch and

the outbound resources of each of that switch’s attached links.

PTSEs describe attributes, such as:

~ Traffic types each link can support (any of the various ATM QoS levels)

~ Maximum cell rate the link can sustain; cell delay variation (only for

constant bit rate (CBR) and variable bit rate real-time circuits (VBRrt)

~ Cell-loss ratio or cell-loss margin (CLM), a measure of the difference

between effective bandwidth allocation and sustainable cell rate

~ Administrative weight (AW), a parameter that allows network architectsto indicate relative link preference when deciding between alternative

routes

Switches make use of this resource information to assess which of the avail-

able paths will best ensure QoS parameters are met.

PNNI Topology StateElement (PTSE)Information

After the initial exchange of topology information among switches in a peer

group, regular broadcast topology updates are unnecessary. Each PTSE has a

finite lifetime. Since individual elements age differently, their refresh updates

occur at different times. This reduces the overhead associated with keeping

the topology of the group updated. The only time a PTSE is rebroadcast is

when there is a significant change in any of the key topology elements. Forexample, any change in cell-delay performance on a link will trigger a PTSE

update from attached switches. Triggered updates further reduce network

overhead.

Every switch in a peer group is aware of the topology state of the entire

group. Thus it can build the entire call setup route from source to destination.

PNNI Hierarchies A topology showing three hierarchal node levels (grandparent, parent, and

child peer groups), peer group leader nodes, and peer group member nodes is

shown in Figure 3-2. Each node, at any level, has its address and rank on the

network described on the PNNI Node Configuration window.

As peer groups grow and incorporate more nodes, the state information in

each switch increases. PNNI supports hierarchies, which collapse the amount

of state information shared by all switches. (See Figure 3-2 for a topology

showing three hierarchal node levels (grandparent, parent, and child peer

groups), peer group leader nodes, and peer group member nodes.)



255-700-447 3-15



In networks that use a PNNI hierarchy, the switches at each level elect one

switch as a peer group leader (PGL). This PGL concurrently belongs to its

own level and to the next highest level, where it acts as a logical group node

(LGN) that represents and summarizes topology information needed to reach

any of the lower-level switches. The higher-level peer group can mirror this

dual constituency, electing a PGL to represent it at the next highest level, upto a maximum of 10 levels, in accordance with ATM Forum PNNI standard

af-pnni-0055.000 Annex F , Hierarchy Configuration, and Appendix G, Minimum

Subsets (all border node capable switching systems features). Each switch in a

PNNI network has a unique 20-byte address that corresponds to the network

service access point (NSAP) schema. Much like IP subnet addresses, NSAP

identifiers have a network part and a user part. The user part is the last seven

bytes, and is reserved for end-system identification (insignificant to the

PNNI). The network part is the first 13 bytes, and is used to identify peer

groups.

Each level in the PNNI hierarchy is also assigned a scope number. Similar to

an IP subnet mask, the scope specifies how much of the 13-byte network part

is common to the switch addresses at a particular level in the hierarchy. Forexample, a scope of 72 (bits) masks the first 9 bytes of the network part as

being common in all switches at that level. Higher levels have shorter scopes

because they do not look as far into the NSAP; a level with a scope of 64

(masking the first 8 bytes) resides above a level with a scope of 72.

To make the best use of PNNI’s capabilities, network architects must pay care-

ful attention to the ATM addressing structure, allocating correct addresses to

switches at each level of the hierarchy.




3-16 255-700-447


ATM Maintenance Adding new equipment, such as another PacketStar PSAX Multimedia Gate-

way, to an ATM circuit already carrying traffic, or taking down an existing

connection, has previously required taking the affected interfaces out of ser-

vice, disrupting all connections. It is now possible, by changing the adminis-

trative weight of a private network-to-network interface (PNNI), to maintainthe ATM connection, without disrupting traffic on existing permanent virtual

circuit (PVC), soft permanent virtual circuit (SPVC), or switched virtual cir-

cuit (SVC) connections.

The new administrative weight is communicated to the PSAX system at

either end of the PNNI link by PNNI link messages. Then, when the user

restarts all the SPVC and SVC connections, the PSAX system reroutes traffic

Figure 3-2. PNNI Hierarchical Topology Showing Three Node Levels

PG(A.2)

PG(A.4)PG(A.3)

PG(A.1)

PG(B.1) PG(B.2)

PG(C)

A.2

A.3A.1

B

A C

A.3.1

A.3.4 A.3.2

A.3.3

A.2.2

A.2.3

A.2.1

A.1.3

A.1.2

A.1.1

B.1.2

B.1.1

B.1.3

B.2.2

B.2.5

B.2.1

B.2.3

B.2.4C.1

C.2

A.4.4

A.4.5A.4.6

A.4.1A.4.2

A.4.3

A.4

B.1 B.2

PG (B)

Highest LevelPeer Group

Logical Link Logical Group Node

Peer Group Leaders

Grandparent Peer Group

Child Peer Groups

Parent Peer Group

PG(A)

[ Source: Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni-0055.000 ]



255-700-447 3-17



away from the PNNI link with the high administrative weight, sending it to

the preferred connection with lower administrative weight. The freed-up

interface can then be reconfigured.

ATM Maintenance Mode is a way of rerouting SPVCs and SVCs from an ATM

port running PNNI. When a PNNI interface’s administrative weight is

changed, traffic on existing connections (PVC, SVC, SPVC) will not be dis-

turbed. New SVCs and SPVCs are routed away from a PNNI link that has

high administrative weight.

ATM Maintenance Mode supports the following:

• PNNI interface on all ATM ports.

• PNNI administrative weights are configured at the PNNI interface level.

The administrative weight can be changed without taking the interface

down or disturbing existing traffic on that ATM port.

• The new administrative weight will be communicated to the ATM switch

on the other end of the PNNI link via PNNI link messages.

• Both SVCs and SPVCs from far end and near end ATM switch [n1]are

routed away from the PNNI link with high administrative weight.

• This procedure interoperates with Marconi/Fore and GX 550 ATM

switches.

Integrated Link Management Interface (ILMI)

The integrated link management interface (ILMI) is a network management

function that supports bidirectional exchange of ATM interface parameters

between two connected ATM Interface Management Entities (IMEs). These

entities are an end user and a public or private network, or a public network

and a private network.

Based on an ATM Forum-defined interim specification, ILMI uses a limited

subset of Simple Network Management Protocol (SNMP) capabilities. ILMI

provides status information and statistics using SNMP and a MIB to provide

any ATM device with status and configuration information about the follow-

ing information available at its ATM interfaces:

• Virtual path connections (VPCs)

• Virtual channel connections (VCCs)

• Registered ATM network prefixes

• Registered ATM addresses

• Registered services and capabilities




3-18 255-700-447


With System Software Release 6.5.0, VPI and VCI range negotiation is sup-

ported. Release 6.5.0 also determines the operational status of the logical

port. ILMI is supported for all ATM UNI 3.0 and ATM UNI 3.1 interfaces.

ILMI over PNNIOverview

The ILMI over PNNI feature supports VPI and VCI range negotiation using

automatic configuration procedures. The automatic configuration procedure

is the ability to automatically configure the following fields, found on the

ATM PNNI Interface Configuration window, based on the local VPI/VCI and

the remote VPI/VCI ranges (VPI and VCI range negotiation):

• Min/Max SVC VPI

• Min/Max SVC VCI

The PNNI ILMI Configuration window and PNNI ILMI Statistics window can

be accessed from the ATM PNNI Interface Configuration window. The PNNI

ILMI Configuration window is very similar to the ATM UNI ILMI Configura-

tion window. For more information on automatic configuration procedures,

see ATM Forum ILMI (Integrated Local Management Interface), 4.0, af-ilmi-

0065.000, Section 8.3.4.

Load Balancing forIISP and PNNI

Load balancing allows communications trunks connecting access and edge

switches to balance traffic between PNNI (dynamic source routing) links. In

addition to the existing parameters of path and route selection, the PSAX

devices consider the values of available bandwidth and available cell rate

associated with the interfaces. The PSAX calculates routes by using available

bandwidth within the default parameters for PNNI routing. Load balancing

between PNNI links uses available bandwidth more efficiently while

strengthening the routing function. See “Interface Type by Input/Output

Module Type” on page C-31 for Table C-7 that lists the supporting modules

for this interface.

ATM Terminal Emulation

Terminal Emulation is an application that follows an intelligent computing

device to mimic the operation of a dumb terminal for communications with a

mainframe or minicomputer. This is made possible by inserting special

printed circuit boards into the motherboard of the emulating device, and/or

special software. The 6-Port Multiserial module is the only PSAX I/O module

that supports this interface.

ATM UNI 4.0 Signaling

The ATM UNI 4.0 Signaling feature supports the mandatory functions

required by the ATM Forum UNI Signaling Specification Version 4.0, as well

as some of its optional features. ATM UNI 4.0 provides the signaling proce-

dures for dynamically establishing, maintaining, and clearing ATM connec-

tions at the ATM user-network interface. ATM UNI 4.0 applies both to public

and private UNI interfaces.



255-700-447 3-19



Major highlights of ATM UNI 4.0 include:

• Individual QoS parameters

• Elements to support narrowband ISDN over ATM

• Procedures,connection scope selection information element, and new MIB

object to support the ATM AnyCast capability.• Procedures and new information elements to support bandwidth modifica-

tion

• New virtual path indicator (VPI)/virtual channel indicator (VCI) options

• Procedures to support multiple virtual UNIs on a physical UNI

• Error handling for instruction indicators

• Using setup for adding parties

Inverse Multiplexing over ATM (IMA)

Inverse multiplexing over ATM (IMA) creates virtual access pipes that are

faster than an E1 line, but not nearly as expensive as a T3/E3 line. Using IMAallows customers to gain ATM capabilities without the costs associated with

broadband access.

Automatic Use of IMA Links

In an IMA group, if one link is broken, the group can be configured to auto-

matically use the other links. For example, if an IMA group has three DS1

links and one of the links fails, although the throughput will drop from 4.5

Mbps to 3.0 Mbps, the IMA group continues to work. If the slowest link fails,

there will be some cell loss on CBR connections as the other links speed up

their cell rate to eliminate excess delay, due to their buffering of cells.

IMA Configuration Considerations

Note: If the PSAX system is interoperating with a device that has imple-

mented ATM Forum IMA ATM Specification Version 1.0 such that

its equipment incorrectly reports link states to the far-end of an

IMA connection, you must configure IMA groups with the compati-

bility mode turned on. This also causes the PSAX system to correctly

report link states and interoperate with your ATM Forum IMA

ATM Specification Version 1.0 equipment.

The following is a list of operations considerations for the IMA interface:

• Once an IMA group has been deleted, its status is displayed as "Insufficient-

Links."

• Links may not be added or removed from a group that is configured. You

must delete any existing interfaces applied to the group before adding or

removing links.

• Operational Status refers to IMA group status, which can be viewed in the

port and channel configuration window.

~ You can restart an IMA group by taking it administratively out of service

and then bringing it back into service.




3-20 255-700-447


~ In order to change any group configuration parameters, the group must

be completely unconfigured.

~ There may be difficulties if the IMA group is configured for symetric

operation but has asymetric link delays. For example, one end may con-

sider links A, B, and C to have problems, while the other end considers

D, E, and F to have problems.

~ Four configurable transmit frame lengths are provided: 32, 64, 128, 256

cells. One ICP (IMA communication protocol) cell is sent over each link

once per IMA frame. If you select a larger frame length, there will be less

overhead. If you select a smaller frame length, the IMA group has better

response in communications with the far end, resulting in faster error

detection and recovery. The IMA specification only requires equipment

to support a frame length of 128. If a frame length other than 128 is con-

figured and the far-end is connected to equipment that doesn’t support

it, the far-end group enters the config-abort state.

~ The IMA identifier (ID) is an 8-bit (0-255) identifier for this IMA group.

There is no significance to any particular values of IMA IDs. Since the

IMA ID is used to identify a group to the far-end, pick a unique valueinstead of leaving it as the default of 0.

The PSAX 1000 and the PSAX 4500 systems provide efficient transport of

traffic transport between cell sites and the mobile switching centers (MSCs).

In cellular phone transmissions, all traffic between the cell sites and the MSC

is wireless backhaul. In North America, due to historical reasons, a cell site

supports multiple radio access technologies such as AMPS, TDMA, CDMA,

and GSM. To provide efficient statistical multiplexing gain, multiple DS1s are

grouped together using IMA over ATM in one IMA group. Furthermore, IMA

provides N:1 protection of the DS1 leased lines under many circumstances.

However, when one or more DS1s fail in the IMA group, enough bandwidth

might not be available to carry all cell site traffic from cell site to the MSC. In

the current dynamic CAC as implemented by the PSAX system, all SPVC andSVC calls are cleared whenever one or more DS1s fail in an IMA group. PVC

connections are not affected; however, an IMA cell may get dropped but the

connection is reestablished immediately.

The Inverse Multiplexing over ATM (IMA) feature is supported on the fol-

lowing PSAX modules:

23N68 1-Port DS3 IMA


20N34 6-Port E1 IMA

23N33 12-Port Medium-Density DS1 IMA

23N34 21-Port High-Density E1 IMA



255-700-447 3-21



Frame Relay-to-ATM Interworking

Frame relay-to-ATM interworking is performed at the network level, Frame

Relay Implementation Agreement FRF.5, and at the service level, FRF.8. This

allows a PacketStar Multiservice Media Gateway to adapt and concentrate

traffic from one frame relay network and transmit it to other frame relay orATM networks. In this way, the Multiservice Media Gateway acts as a gate-

way between routers, remote-dial access servers, systems network architec-

ture (SNA) equipment, and other devices configured for frame relay opera-

tion.

FRF.5 EncapsulatingFrames

With FRF.5 network level interworking, frames are encapsulated within ATM

cells at the network ingress point and "tunneled" through the ATM network.

At the network egress point, the ATM cell headers are removed and the

frames are reassembled for delivery to a frame relay device.

FRF.8 ConvertingFrames

With FRF.8 service level interworking, frames are converted into one or more

ATM cells at the network ingress point. At the network egress point, the ATM

cells are delivered to an ATM device. This conversion is compliant with boththe FRF.8 implementation agreement and the IEFT multiprotocol encapsula-

tion specifications (RFC 1490, RFC 1483). FRF.8 interworking is performed at

the end of the ATM network that connects to the frame relay device.

Note: FRF.5 and FRF.8 are not interoperable and cannot be used at both

sides of a network. You may wish to use an FRF.8 approach for

applications involving interconnectivity between two frame relay

devices because the capabilities of FRF.8 include those that are

available with FRF.5.

Inverse AddressResolution Protocol(ARP)

The Inverse Address Resolution Protocol (ARP) feature using the FRF 8.1

specification provides packet translation between frame relay and ATM inter-

faces. The packet translation is available on both frame relay-to-ATM PVC

and frame-relay-to-ATM SPVC connections. For frame relay-to-ATM SPVC

connections, the ARP/inverse ARP to/from ATM side is treated as ATM PVC

ARP/inverse ARP.

Frame Relay-to-Frame Relay Interworking

In addition to frame relay-to-ATM interworking, it is possible to configure a

Multiservice Media Gateway for strictly frame relay operation. A frame relay-

to-frame relay connection can be made between two ports of a Multiservice

Media Gateway if both ports have frame relay capacity. In this case, frame

relay data received by one of the ports is converted to ATM cells for transmis-

sion across the backplane of the Multiservice Media Gateway, and then con-

verted back into frame relay for transmission from another port.

GR-303 Interface

The Telcordia Technologies General Requirements 303 (GR-303) standard

provides for both an open interface network architecture and a digital loop

carrier system that operates on T1 circuits. This standard allows a remote ter-

minal such as a central office PSAX system to flawlessly interface with a




3-22 255-700-447


Lucent Stinger™ DSLAM, a CellPipe™ IAD or AdTran TA624.850, and a cen-

tral office voice switch, such as the Lucent Technologies 5ESS switch, or with

a Nortel DMS switch.

Operating on T1 circuits, the GR-303 digital loop carrier service has provi-

sions for both an open interface network architecture and a digital loop car-

rier system. The performance standards of the GR-303 interface are derived

from the high-level internetworking capabilities established in Telcordia

Technologies General Requirements 303, and allow a central office PSAX sys-

tem to interface with central office voice switching equipment as a remote

terminal.

The interface assigns and manages connections on a time slot management

channel (TMC) and supports operating functions on an embedded operations

channel (EOC), with each channel configured on I/O modules that support

the GR-303 interface protocol. The user guide details a configuration for one

GR-303 group using the ratio concentration of 2048 CRVs to 668 DS0s,

approximately a 3:1 oversubscription rate per DSP2C/D voice processing

chip. (A CRV is a call reference value that the 5ESS switch will map to a

phone number). The GR-303 specifications recommend connection concen-

trations from 1:1 up to 3:1, expandability from 2 to 28 DS1 circuits for each

GR-303 group, and expandability from 1 to 2,048 subscriber channels per

GR-303 interface group.

The oversubscription factor you can achieve depends on what modules con-

figuration is chosen. You can decide what ratio to oversubscribe the DS0/CE

resource. Higher channel densities per DSP chip resource and more AAL2

trunking groups are achieved by upgrading to the DSP2D Voice Server mod-

ule from the DSP2C.

The maximum number of GR-303 interface groups supported on the PSAX

system is 84. Loop emulation services provide multiplexed AAL2 PVC sup-

port for the PSAX system central office product line. Loop emulation services

allow voice traffic, DTMF, and signaling to be handled over the packet net-

work. The circuits can interwork with time division multiplexing (TDM),

ATM digital subscriber line (DSL), or GR-303 interfaces.

The PSAX system also supports these features:

• Caller ID

• Call forwarding

• Call transfer

• Call waiting

• Cancel call waiting

• Customer callback

• Speed dialing

• Three-way calling

• Loop start line

• Visual and audio message waiting indicator

Because GR-303 software requires a large amount of memory, the feature

can be enabled or disabled as needed. If this feature is not needed, disabling it

allows the system to allocate more memory for other system functions.



255-700-447 3-23



The 6-port DS1/T1, 1-port Channelized DS3,and 1-port Channelized STS-1e

modules, used in conjunction with the DSP2C Voice Server module and also

with the Lucent StingerTM DSLAM and CellPipeTM IAD, provide a complete

end-to-end communications solution that fully complies with the GR-303

interface standard.

In System Software Release 8.0.0, the following enhancements have been

added to the DSP2D Voice Server module for connections using the GR-303

interface standard:

Fax/ModemMaster/Slave Support

The PSAX system supports fax/modem tone detection for the ATM downlink

side at 32 Kbps using ATM Forum profiles. When the DSP2D is configured as

a CP-IWF with an IAD in the CO-IWF, the module performs automatic algo-

rithm switching to match the algorithm used on incoming AAL2 data streams

from CO-IWF devices, such as the Lucent CellPipe and the Adtran

TA624.850. This results in 64 Kbps with voice compression and echo cancel-

lation being turned off for the duration of the fax call. A form of master/slave

device hierarchy, the PSAX system functions as the master device and theIAD functions as the slave. This feature has been added to the firmware on

the DSP2D module and is not configured by the user.

CAS Refresh Rates inthe On-Hook State

Refresh rates are fixed in the firmware for 5 minutes in the on-hook state,

and 5 seconds in the off-hook state, using the AlgoSet6 voice processing fea-

ture set. If you prefer the NOC to be notified sooner in case of connection

failure, turn the call logging feature on in the Stinger DSLAM. The Stinger

notifies the NOC by means of a trap message as soon as a DSL connection

fails and the Stinger port receives a LOS indication. For guidance on Stinger

configuration, see the Stinger Administration Guide, Part Number: 7820-0712-

002, Software Version 9.0-139, January 2001, and the Stinger Reference Guide, Part

Number: 7820-0713-003, Software Version 9.0-139, March 2001 for details.

Idle ChannelSuppression Supportfor the CellPipe IAD

The CellPipe IAD is certified to not transmit silence cells between itself and

the PSAX system when in the on-hook state if a channel is idle (supporting

no active connection).

GR-303Interoperability

The following modules have been certified as interoperable with the Stinger

DSLAM, 5ESS CO switch, the CellPipe IAD, and the PSAX 2300 system:

• 1-Port Channelized STS-1e

• 6-Port Enhanced DS1/T1 Multiservice

• 1-Port Channelized DS3 CES

• DSP2C Voice Server

• DSP2D Voice Server• 2-Port DS3 ATM

This module has been certified as interoperable on the GR-303 protocol with

the 5ESS CO switch and the PSAX 4500 system with redundant CPUn and

redundant Power Supply modules:

• 2-Port DS3/E3 ATM



Chapter 3 System FeaturesDynamic Bandwidth Allocation

3-24 255-700-447


The following modules have been certified as interoperable with the

PSAX 2300 system, the Stinger DSLAM, the CellPipe IAD, and the Nortel

DMS CO switch.

• 1-Port Channelized DS3 Multiservice

• DSP2C Voice Server• 2-Port DS3 ATM

Dynamic Bandwidth Allocation

The Dynamic Bandwidth Allocation (DBA) feature monitors the CBR traffic

on a selected channelized, strapped DS1 circuit emulation (CE) interface.

When the incoming traffic from the backplane towards the CE side of a

CE-to-ATM connection drops to 10 percent or less of the configured interface

(strapped) bandwidth, the DBA feature disables the transmission of cells

from the CE side of the connection to the backplane. DBA measures traffic

throughput with an integration period of 1 ± 0.5 seconds. By disabling the

transmission of cells (CBR traffic) from the CE side of the connection, the

PSAX system saves bandwidth that can used for other types of traffic on the

connected ATM trunk.

When incoming traffic from the backplane towards the CE side of a

CE-to-ATM connection is 50 percent or more of the configured interface

(strapped) bandwidth, cells are being transmitted from the CE side to the

backplane. If the traffic volume begins to drop below 50 percent, cell trans-

mission continues until the traffic volume reaches 10 percent. At this thresh-

old, the transmission of cells from the CE side of the interface to the back-

plane is stopped. When the volume of traffic again rises above 10 percent but

is still below 50 percent, cell transmission remains stopped. At the point

where traffic volume rises to 50 percent or higher, cell transmission resumes.This scheme prevents frequent stopping and starting of the traffic stream on

the interface due to volume fluctuation of incoming traffic from the back-

plane to the CE side of the CE-to-ATM connection.

The DBA feature operations are illustrated in Figure 3-3.



255-700-447 3-25


Chapter 3 System FeaturesNetwork Management

The DBA feature is supported on the following module:

Network Management

The PSAX system provides all the telecommunications management network

(TMN) functions applicable to the system. The PSAX system (which contains

network elements) can be managed in several ways using a network element

management system or network management system. The PSAX system soft-

ware features a Simple Network Management Protocol (SNMP)-compliant

management information base (MIB) that gives external management sys-

tems access to the PSAX system software.

Figure 3-3. DBA-Controlled Backplane Traffic

24N64 12-Port Medium-Density DS1/E1/DS0A CES

(DS1 mode only)

DBACE

Interface

12-Port MD DS1/E1/DS0A CES Module

Backplane TrafficAllowed

DBACEInterface

12-Port MD DS1/E1/DS0A CES Module

Backplane TrafficInhibited

NORMAL OPERATIONS

INHIBITED OPERATIONS

Normal Traffic

No Traffic




3-26 255-700-447


In conjunction with the visual indicators displayed on the front panels of the

individual modules, the system offers a full complement of SNMP trap mes-

sages that alert the user to faults in the PSAX system. Usage-based messages

collected on the CPUn module allow a service provider to collect cell counts

for traffic and performance monitoring, and for fault detection.

The SNMP MIB provides an extensive series of configuration management

and provisioning features that allow the user to prepare the various compo-

nents for supporting services.

Network Management Options

The PSAX system software supports the following options for network man-

agement:

• Serial port interface with a direct connection to a standard VT100 terminal

emulator.

As the simplest option, the CPUn module faceplate provides an EIA-232

serial port (RJ-11 connector labeled CONSOLE), to which a PC workstationor a console monitor, running a standard VT100 terminal emulator, is con-

nected.

The console interface provides access to the configuration, fault, network

data-collection, and security-management features of the system software.

The PSAX system software allows you to perform management tasks using

a menu-based interface.

This port is typically used for local management (using a direct serial con-

nection), but it can also be used for remote management. Remote manage-

ment may be performed over a public switched telephone network (PSTN)

with the use of an external modem, or over an ATM network with the use

of a terminal emulation connection from a Multi-Serial module. The serial

port is also used for the configuration of Internet Protocol (IP) parameters,which are necessary for IP-based management.

• Ethernet interface connection on a local-area network (LAN).

A 10BASE-T Ethernet interface (RJ-45 connector labeled ETHERNET) on

the PSAX CPUn module faceplates allow the user to access the MIB, either

using the AQueView application over a LAN or by telneting to the PSAX sys-

tem. If a telnet session is used to manage a PSAX system, then the console

interface is displayed (similar to that which is used for the serial interface,

as explained above). Only one person can have access to the console inter-

face at a time; therefore, direct access using the serial port precludes telnet

access using the Ethernet port.

• In-band management by using a PVC connection over an ATM wide-area

network (WAN).The in-band management feature on the CPUn module allows a user to

access and manage one or more PSAX systems (managed targets) via a sin-

gle PVC connection from a management workstation (management host)

running an SNMP client over an ATM WAN. This allows for IP-based func-

tions (that is, telnet) and SNMP functions (that is, element and network

management software) to be performed remotely using ATM virtual cir-

cuits, which terminate within the managed node. The PVC/SVC connec-



255-700-447 3-27



tion is set up using an I/O module with an ATM cell bearing port (for

example, the OC-3c, STM-1, DS1, DS3, E1, and E3 modules). Three basic

types of configuration are possible:

• Direct connection

• Routed connection

• Hybrid connection

For more information on these three basic connection types, see

Appendix B. For more information on configuring in-band management

SVC connections, see Chapter 5. For more information on configuring in-

band management PVC connections, see the appropriate PSAX module

user guide.

Simple Network Management Protocol Version 3

The Internet Engineering Task Force Steering Group recently approved Ver-

sion 3 of the Simple Network Management Protocol (SNMPv3) as a full stan-

dard. SNMPv3 contains additional security and authentication features thatprovide data origin authentication, data integrity checks, timeliness indica-

tors and encryption to protect against threats such as masquerade, modifica-

tion of information, message stream modification and disclosure.

The PSAX system features a standard SNMP agent that allows any standard

SNMP management system, such as the AQueView EMS, HP OpenView or

SunNet Manager, to perform all management functions. The PSAX system

software uses Enterprise MIBs and can be made available for any SNMP

management system. SNMP version 3 is supported in addition to the current

SNMPv1 and SNMPv2c support.

The SNMP agent resides within the CPUn module of the PSAX system. The

console interface (accessible via the serial or Ethernet interfaces on the CPUn

module) acts as a shell to the underlying SNMP agent. In addition to provid-ing the status of the visual indicators on the front panels of the individual

modules, the SNMP agent offers a full complement of trap messages that alert

the user to faults within the PSAX system network. A PSAX system can be

configured to automatically transmit these trap messages to up to five net-

work management stations. The SNMP agent also provides an extensive

series of configuration management features.

While SNMPv3 is the latest version and the most feature rich, end users will

need time to migrate their Network Management Systems (NMS) and Opera-

tion Support Systems (OSS) to SNMPv3 support. For this reason, the imple-

mentation of the SNMPv3 feature in the PSAX system maintains support for

the current SNMP versions (SNMPv1 and SNMPv2c) while adding support

for SNMPv3. This allows users to either continue using SNMPv1 or SNMPv2cwhen they upgrade from an older version of software or to use the security

features with SNMPv3.

In addition to the SNMPv3 support, the PSAX software supports inform mes-

sages with both SNMPv2c and SNMPv3.



Chapter 3 System FeaturesPSAX System Software Features

3-28 255-700-447


Navis® AQueView ® Element Management System

The Navis® AQueView ® Element Management System (EMS) is a GUI-based

element management tool that is used to provision the PacketStar PSAX 1000,

PSAX 1250, PSAX 2300, and PSAX 4500 systems. The AQueView EMS

enables a network of PSAX devices to be managed and provisioned from asingle location, using easy-to-use windows. The AQueView EMS also provides

centralized configuration, diagnostic, performance, and security manage-

ment of PSAX systems.

The AQueView EMS is available in two versions:

• Client/Server application:

~ The Client and server can be installed on Sun Solaris platforms with or

without HP OpenView NNM

~ The Client alone can be installed on Sun Solaris platforms with HP Open-

View NNM

~ The Client alone can be installed on Windows NT, Windows 2000, and

Sun Solaris platforms without HP OpenView NNM• Standalone application:

Can be installed on Windows NT, Windows 2000, and Sun Solaris plat-

forms without HP OpenView NNM

For more information on AQueView functionality, refer to the following docu-

ments:

• Navis® AQueView ® Element Management System Release Note for Release 9.0.0

Controlled Introduction, Document Number 255-700-494

• Navis® AQueView ® Element Management System User Guide for the Client/Server

Application, Release 9.0.0, Document Number 255-700-495

• Navis® AQueView ® Element Management System Quick-Start Guide for the Cli-

ent/Server Application, Release 9.0.0, Document Number 255-700-496• Navis® AQueView ® Element Management System User Guide for Standalone Sys-

tems, Release 9.0.0, Document Number 255-700-493

• Navis® AQueView ® Element Management System Quick-Start Guide for Standal-

one Systems, Release 9.0.0, Document Number 255-700-497

PSAX System Software Features

Bulk Statistics Collection

The Bulk Statistics feature provides the ability to send collected interface and

connection statistics to a remote statistics server, such as the NavisXtend Sta-tistics Server. The collection of PSAX system statistics can be used for net-

work management/reporting such as historical trend analysis, network

design and planning, and customer network management (CNM)-based

reports. The Bulk Statistics feature supports collection of statistics on ATM

and frame relay interfaces and connections.



255-700-447 3-29



This feature polls the PSAX MIB every n seconds and stores the information

in memory. The number of records that can be stored is initially set at 1,000.

At the end of the user-specified measurement period, the collected data is

sent via FTP to the statistics server.

Connection Gateway API

Connection GatewayAPI Overview

The Connection Gateway Application Programming Interface (CGAPI) pro-

vides a communications protocol or set of messages by which a call controller

can control ATM switching on a PSAX system using nonnative ATM net-

working protocols. See the PacketStar ® Connection Gateway Application Program-

ming Interface Developer’s Guide for detailed information about implementing a

connection gateway API.

The Connection Gateway application programming interface (API) provides a

robust interface with a goal of allowing the full line of PSAX systems to route

non-ATM traffic, smoothly interworking with nonnative ATM, ISDN, SS7,

CAS, and other protocols.

For channel-associated signaling (CAS), the Connection Gateway API offers

both R1 and R2 support. The gateway supports switched voice traffic over

ATM by improving narrowband options through AAL1 and AAL2 trunking.

The gateway provides service level interworking, provisioning, fault monitor-

ing, continuity service checking, and line testing support for the Channelized

DS3 module and/or the STS-1e T1 module. It extends continuity checks and

line tests to the I/O circuit emulation service (CES) modules. The capabilities

are particularly useful for offering voice traffic over ATM and for conveying

data.

The Connection Gateway API enhancements, Phase 6, are as follows:

• A DSP2D interface failure indication message is sent when a call is set up

with echo cancellation enabled and the DSP2D chip used in this call has afailure.

• DSP2 resource messages are used to obtain interface information on DSP2

modules in the system.

• The DSP2 call reroute feature automatically routes calls from DSP2D mod-

ules with failed chips to other configured chips on the same modules or to

any other DSP2 module in the system.

• When the PSAX system is set up as the client in a Site Specific Configura-

tion, a Connection Gateway API interface address is used as an interface on

which to send Connection Gateway API messages.

PSAX System As aTCP Client/Server forthe ConnectionGateway API

If you are using the Connection Gateway API with your PSAX system, you

need to configure the system as either a TCP client device or a TCP server

device. If you set up the PSAX system as a TCP client device, you can connect

multiple PSAX systems as TCP client devices to a call controller, which is set

up as a TCP server device (see Figure 3-4).




3-30 255-700-447


You can also set up the PSAX system as a TCP server device with the call con-

troller set up as the client device. As an option, you can connect two call con-

trollers, set up as primary and backup client devices, to the PSAX system

(server device) (see Figure 3-5).

Figure 3-4. PSAX System as a TCP Client Device

Figure 3-5. PSAX System as a TCP Server Device

In-bandManagement

PVC Connection

Local Access Concentrator(Primary TCP Client)

Call Controller Device (Computer)

(TCP Server)

ATM I/OModule

EthernetModule

Ethernet Hub

ATM I/OModule

Remote Access Concentrator(TCP Client)

ATM I/OModule

Local Access Concentrator(Backup TCP Client)

In-bandManagement

PVC Connection

EthernetModule

ATMWAN

ATMWAN

Call Controller Device-Primary (Computer)

(TCP Client)

Call Controller Device-Backup (Computer)

(TCP Client)

EthernetConnection

EthernetHub

EthernetConnection

EthernetModule

ATM I/OModule

Local Access Concentrator(TCP Server)

ATM I/OModule

Remote Access Concentrator(TCP Server)

ATMWAN

In-bandManagement

Connection

Route ServerModule



255-700-447 3-31



Fractional PRISupport

In the area of ISDN deployment, there are times when a full PRI (23B+D

channels) is both unnecessary and wasteful. For instance, a small branch

office with 15 phone lines can probably be served comfortably by only 10 B-

channels and 1 D-channel. The remaining 13 time slots can be utilized for

other applications such as Nx64 CE or other fractional T1 type services.

A fractional PRI (F-PRI) is defined as a group of one or more time slots in a

T1 port, with at most one time slot designated as the D-channel and the

remaining time slots in the group as B-channels. In theory, a fractional PRI

can consist of B-channels entirely, or just one D-channel without any B-

channel. Similarly, a fractional PRA (F-PRA) is defined as a group of one or

more time slots in an E1 port, with at most one time slot designated as the D-

channel and the remaining time slots in the group as B-channels.

PNNI Support To utilize the functionality provided by the PNNI protocol, the PSAX system

provides interworking functionality between the PNNI protocol and the Con-

nection Gateway (CG) by communicating signaling parameters required for

call control between the CG and the PSAX system. PNNI protocol is used between private ATM switches, and between groups of private ATM

switches.

The PSAX system support for the PNNI protocol enhances the current ATM

call control capability of CGs to be able to dynamically setup and release ATM

connections through egress/ingress ports of PNNI interfaces connecting to the

PNNI network. With UNI interfaces, the routing of call setup request is based

on static routes through provisioning. The functionality of PNNI routing and

signaling that resides in the PSAX system and functions transparently to the

CG for the following reasons:

• Requires no change to the current implementation of the PNNI protocol in

the PSAX system

• Limits the dependence on types of ATM protocols supported by the PSAX

system

• Limits the change required for the CG.

The CG is considered as an external SPVC-end-point-like user utilizing the

PNNI protocol. Therefore, the PSAX system performs the interworking to

map the messages between PNNI signaling and PSAX system messages from

the CG. Whenever the PSAX system receives a call setup request either from

the CG or from the network, the PNNI route selection is performed by the

PSAX system.

DS1 ANI In-line Codes for Loopbacks

The channelized DS3 multiservice and CES modules support activating and

deactivating DS1 access network interface (ANI) in-line loopback codes

embedded in the DS1 signal. These codes test transmissions between cus-

tomer interface equipment and network interface equipment, for example,

between PSAX central office (CO) products and customer premises equip-




3-32 255-700-447


ment (CPE) products at the edge of an ATM network. The PSAX system also

generates alarm indication signals on all affected DS1 connections whenever

a loop is activated.

DS0A Non-Latched Loop CodesIn addition to the no loopback and the line loopback modes of operation

present in the 12-Port Medium-Density DS1/E1/DS0A module (DS0A mode)

in Release 7.1.3, three new, user-configurable, loopback modes have been

added in Release 8.0.0:

• Transmit mode

• Monitor mode

• Transmit and monitor mode

In conjunction with these three modes, six fields can be configured:

• Transmit loop up code

• Transmit loop down code• Receive loop up code

• Receive loop down code

• BERT pattern

• Timeout (Transmit loop code duration)

In Transmit mode, the module outputs 1 second of transmit loop up code fol-

lowed by 1 second of BERT pattern on the line, repeating this pattern until

Timeout is reached, at which point 1 second of transmit loop down code is

sent on the line. The module is also in remote loopback in this mode. The

purpose of this mode is to test the operation of the module connected on the

far end of the line when it detects and returns the loopcodes transmitted. The

DS0A module reports to the CPUn module whether the transmit loop up

code or transmit loop down code was received.

Monitor mode is the opposite of transmit mode. Here, the module on the far

end must verify that the near-end DS0A module is working properly by

sending loop codes on the line. In monitor mode, the DS0A module operates

normally—that is, passes real traffic—until it receives the receive loop up

code on the line. At that point, the module is set to line loopback and remote

loopback and reports to the CPUn module that it had a matching of the

receive loop up code. When the DS0A module detects the receive loop down

code, it is taken out of loopback and reports the receive loop down code

matching to the CPUn module. If the module is in loopback mode and does

not detect either of the receive loop codes, it automatically returns to normal

mode after two minutes.

Transmit and monitor mode is exactly the same as transmit mode except that

the DS0A module also reports to the CPUn module a matching of the receive

loop up and loop down codes.



255-700-447 3-33



PSAX System Traffic Protection Capabilities

1:1 Traffic ProtectionPatch Panel Module

sThe 1:1 protection capability of the PSAX systems provides traffic protection

by configuring the system with two 1:1 protection capable I/O modules, such

as the 24-Port High-Density DS1 Multiservice module, and the PSAX 24-Port

RJ Protection Patch Panel.

The I/O modules are configured in matched pairs, one working and one pro-

tection. In normal operation, the working module is configured to pass traf-

fic. The protection module is matched with the working module and config-

ured in a standby mode, waiting for the working module to fail or be

replaced. The PSAX 24-Port RJ Protection Patch Panel provides the interface

between the I/O modules and network circuits, and protection control

between the working and protection modules.

Working Module Monitoring

Traffic is switched from a working module to its associated protection moduleunder the following conditions:

• Working module failure

• Removal of the working module from the chassis

• Manual switchover initiated by the user

• Nonservice affecting upgrades

The protection module monitors the operation of the working module. Inter-

Slot Communication (ISC) cells are exchanged between the working and

protection module. If the protection module detects eight consecutive miss-

ing ISC cells from a working module, the protection module sends a message

to the CPU indicating the working module failure. A likely cause of this con-

dition is that processing on the working module is interrupted or suspended.Other causes of this condition are the removal of the working module from

the chassis or a failure of the module.

Switchover Events

During the switchover of traffic from the working module to the protection

module, various events occur depending on the reason why the switchover

was initiated. These events are described in the following scenarios:

• Working module failure or removal

After the protection module detects the failure or removal of the working

module, automatic switchover occurs. The protection module notifies the

CPU that the working module has failed or been removed.The protection module instructs the PSAX 24-Port RJ Protection Patch

Panel to switch control from the working module to the protection mod-

ule, which is now placed into Active mode. The patch panel LEDs change

states signifying that the working module is not active or in standby mode.

A manual switchover is required to return the active protection module to

standby and the standby working module to active.

• Manual switchover initiated by the user




3-34 255-700-447


The user can manually switch traffic from the working module to the pro-

tection module (see Chapter 3 of the module user guide). This action might

be taken in preparation for removing the working module from the chassis

for maintenance purposes or testing the working module for diagnostic

purposes. When the user executes the switchover command, the

PSAX 24-Port RJ Protection Patch Panel switches control from the workingmodule to the protection module.

In both scenarios, the connection downtime (<250 ms) is only the amount of

time needed to switch the PSAX 24-Port RJ Protection Patch Panel from the

working connections to the protection connections.

Figure 3-6 illustrates the data flow in a 1:1 protection scheme during normal

operation, and the data flow while the protection module is in Active mode

following the failure of a working module in a protection group.

Figure 3-6. 1:1 Protection Scheme on the PSAX System

Backplane

Normal Data Flow

WorkingModuleSlot 3

Standby Protection

ModuleSlot 4

Active

Protection Patch Panel

Chassis

Backplane

Backplane

Failed Working Module

WorkingModuleSlot 3

Active Protection

ModuleSlot 4

Failed

Protection Patch Panel

Chassis

Backplane

Line

Line



255-700-447 3-35



Restoring Service to the Working Module

After automatic or manual switchover has been performed and the replace-

ment or testing of the working module is completed, the user manually

switches the traffic back from the protection module to the working module,

which resumes Active mode. The following events occur depending on

whether the working module is an existing one having all configurations

loaded, or is a new module that replaces a failed working module.

• Existing working module

When the user executes the switchover command (Command field on the

N to M Protection Configuration window, see Chapter 3 of the module user

guide), the PSAX system instructs the PSAX 24-Port RJ Protection Patch

Panel to switch control from the protection module running in Active

mode to the working module. The working module is then placed into

Active mode and the protection module is placed into Standby mode. The

patch panel LEDs indicate the working module is active.

• Replacement working module

When the user inserts the new replacement module into the chassis, thePSAX system recognizes it as an unconfigured module. The user then exe-

cutes the switchover command and the PSAX 24-Port RJ Protection Patch

Panel switches control from the protection module running in Active mode

to the working module. The working module is then placed into Active

mode and the protection module is placed into Standby mode.

The connection downtime (<250 ms) during this manual switchover in the

previous scenarios is only the amount of time needed to switch the

PSAX 24-Port RJ Protection Patch Panel from the protection connections to

the working connections.

APS/MSP Protection

on the OpticalModules

The 1+1 Automatic Protection Switching (APS)/Multiplex Section Protection

(MSP) feature provides connection redundancy for traffic flow protection onthe PSAX optical I/O modules. These modules, which can be used in any

PSAX Multiservice Media Gateway chassis, include:

• 1-Port OC-3c 1+1 APS Multimode and Single-Mode modules

• 1-Port STM-1 1+1 MSP Multimode and Single-Mode modules

• 1-Port OC-12c/STM-4c Multimode and Single-Mode modules

These modules are used in pairs, installed in adjacent slots in the PSAX chas-

sis. In the event that the active module in the pair fails, the traffic is switched

to the standby module. The 1+1 protection implementation is compliant with

the GR-253-CORE standard and supports linear nonrevertive 1+1 protection,

in both bidirectional and unidirectional modes. Nonrevertive means that

connections that were switched from the active module to the standby mod-ule are not automatically switched back to the active module after a failed

link becomes operational again. One advantage of nonrevertive switching is

minimal service interruption—one interruption instead of two.




3-36 255-700-447


Interface ProtectionGroup Feature

The Interface Protection Group feature provides the capability to configure

interface protection groups of ATM interfaces that support PVC and SPVC

connections on PSAX modules. Interface protection groups can be configured

as primary (active) and standby (idle). Similar types of interfaces must be

must be grouped together in the same group. For example, in a primary

(active) group, you could set up this group with all DS3 ATM UNI 3.0 havingthe same parameters, and in the secondary (standby) group, you could set up

the same type of interfaces having the same parameters as in the primary

group. Specifically, this feature allows a user to group similar types of inter-

faces together by specifying which interfaces in the group are primary (nor-

mally carrying traffic) or standby (normally idle). The feature permits N:1,

1:1, and M:N schemes by allowing several primary interfaces and one

standby interface to exist with a user-defined interface protection group.

When a failure condition is detected on a primary interface, the feature

moves all affected connections from the primary interface to a standby inter-

face. The standby interface is selected from those available in the interface

protection group based on criteria selected by the user.

To use this feature, the following sequence of configuration tasks must be

performed:

1. Configuring the ports,channels, and interfaces on the modules (physical

layer interface)

2. Configuring connections (ATM layer and IWF)

3. Configuring the inteface protection groups

Figure 3-7 illustrates how a typical interface protection group configuration

works. After the protection groups are created, they are displayed on the Pro-

tection Group Table and the Interface Protection Table windows on the con-

sole interface. When a switchover is initiated by the primary interface, the

IWF for that interface is torn down and replaced by the standby interface’s

IWF within that group. These configurations are displayed on the appropriate

PVC connection screen.



255-700-447 3-37



This software feature moves connections within a defined group whenever a

failure condition occurs or the user issues a switchover/switchback com-

mand.

• The switchover method is either automatic, whereby the traffic from a pri-

mary interface is automatically switched to an available standby interface,

or explicit, whereby the traffic from a failed primary interface is switched

to the available standby interface only when the user selects the switcho-

ver.

• The switchback method is either automatic, whereby the traffic from the

standby interface is switched back to its corresponding recovered primaryinterface, or explicit, whereby the traffic on the standby interface is

switched backed to the corresponding primary interface only when the

user selects the switchback.

Alternate ReroutingUsing Dual-HomedPVCs

To protect ATM traffic from network outages, the PSAX system can detect

alarms or failures on an ATM backbone and reroute PVC traffic around the

affected portions of the network. Using dual-homed permant virtual circuits

(DHPVCs), the PSAX system performs the rerouting function automatically,

without relying on operator intervention or rerouting capabilities within the

network itself. This feature is implemented on the PSAX system according to

industry standards, and includes the following types of PVC connections:

• ATM-to-ATM VCC and VPC connections

• Circuit emulation-to-ATM VCC connections

• Frame relay-to-ATM VCC connections

• Bridge-to-ATM VCC connections

• Terminal emulation-to-ATM VCC connections

Figure 3-7. Typical Interface Protection Group Configuration

AX4000Gen/Ana

DS3

IMA

IMA

DS1

PSAX 2300

Primary 4 Group 1

Primary 5 Group 1

Primary 2 Group 1

Primary 3 Group 1

Primary 6 Group 1

Primary 1 Group 1

ATM




3-38 255-700-447


The DHPVC feature enables users to set up a primary and a standby connec-

tion using one interface on the PSAX system. In other words, users do not

need to configure a separate interface that functions solely for a standby con-

nection. Rather, ATM trunk interfaces can be used in a load-sharing design

with the connection admission control (CAC) constraints automatically con-

sidered when the primary and standby connections are configured. This tech-nique allows particular links to be used as the primary link for certain

DHPVCs while they are used simultaneously as the standby for other

DHPVCs.

Operation

When the DHPVC connection configuration is set up, both the primary and

standby (backup) connections are provisioned from the originating endpoint

to the terminating endpoint, through the ATM network. When provisioning

the primary connection, the user enters the parameters that are appropriate

for the type of PVC connection being established (ingress slot, ingress port,

egress slot, egress port, QoS, AAL type, peak cell rate, VPI, VCI, and so on).

When provisioning the standby connection, the user is required to enter onlythe network parameters that are associated with the standby connection

(egress slot, egress port, VPI, and VCI). The remaining parameters are gov-

erned by the primary connection. Because DHPVC connections make use of

PVCs within the network, interoperability issues do not exist with interven-

ing network devices. During normal operation, the primary connection car-

ries the traffic. While the primary connection is operational, traffic is not sent

over the standby connection.

The DHPVC implementation makes use of ATM Forum OAM F5 flows to

automatically initiate rerouting. If a link failure is detected on the primary

connection (on either the transmitting path or the receiving path), the asso-

ciated network element that detects the failure generates an OAM F5 alarm

indication signal (AIS) to the downstream node, which in turn sends the AISto the destination edge node. At that point, the edge node converts the AIS to

remote defect indication (RDI) messages, which are transmitted to the origi-

nating node.

Intermediary nodes relay the RDI messages upstream, ultimately to the origi-

nating or terminating nodes. Upon detecting an AIS/RDI alarm on a DHPVC-

configured PVC connection, the PSAX system automatically switches the

traffic on a primary connection to its standby (backup) connection. In the

Debouncing Period field on the Site-Specific Configuration window, the user

can select a value from the range 1 sec (1,000 msec) to 300 sec

(300,000 msec). The value the user sets in this field specifies the length of

time that must elapse since receiving any AIS/RDI alarm on a primary PVC

connection before the PSAX system automatically switches the traffic from

the standby (backup) connection back to the primary connection. Currently,

the user cannot choose to prevent the automatic switchback from the

standby connection to the primary connection.



255-700-447 3-39



Application

A pair of PSAX systems, acting as an originating node and a terminating

node, cooperatively accomplish the networkwide rerouting regardless of the

number of connections affected by the network outage. The PSAX system

can switch traffic on a primary connection to a standby connection within

one second, avoiding service interruptions under reasonably likely network

congestion conditions. The automatic rerouting of traffic from a primary con-

nection to a standby connection is shown in Figure 3-8.

Firmware Release Control

The PSAX CPUn module has access to the firmware binaries of all modules

present in the PSAX system. The firmware is downloaded into the random

access memory (RAM), into the secondary FLASH of each module, through a

dedicated communication channel.

The firmware download is performed under the control of two interworking

functions (IWFs) resident in the PSAX CPUn module, and in the I/O or server

module, respectively. Once the binaries are downloaded, the modules exe-

cute the downloaded code that controls the module.

You do not need to download an I/O or server module’s firmware separately

from the PSAX system software upgrade. When the PSAX system software is

upgraded using the SRD Download Configuration window (see Chapter 13),

the system reboots and all firmware of the I/O and server modules (in the

rebooted chassis) is also upgraded.

You can use the firmware upgrade procedure in Chapter 13 to revert to an

older firmware release if a module is not working properly with its currentfirmware.

Figure 3-8. Automatic Traffic Rerouting using Dual-Homed PVCs

MultiserviceMedia

GatewayPrimary PVC

Standby PVC

Primary PVC

Standby PVC

ATM Network

InterruptedLink failure

service

Continuedservice

MultiserviceMedia

Gateway




3-40 255-700-447


PSAX I/O modules released with PSAX system software Release 6.0.0 and

subsequent releases are supported by the Firmware Release Control feature.

The I/O modules that were released before PSAX system software Release

6.0.0 will work in the PSAX system, but are not supported by the Firmware

Release Control feature.

Forward Error Correction

The Forward Error Correction (FEC) feature is a combination of functions

designed to protect data transmission in a noisy communications environ-

ment, such as traffic transmitted across satellite or line-of-sight radio-fre-

quency circuits. Most of these types of circuits transmit at the rate of

2.048 Mbps or slower. The three stages of FEC are multiple redundancy

addressing, cell encoding, and cell scrambling. Since these FEC functions can

be applied in conjunction with the LANET protocol, which helps maintain

cell-delineation capability up to a random 10-2 bit error rate (BER) with

0.625 percent bandwidth overhead, maximum protection can be obtained.

Multiple redundancy addressing sets up multiple virtual circuits to the same

destination. The addresses for the circuits are within the error space of the

principal one used for actual transmission. The most probable error patterns

occurring in the address field cause the address to be changed to another

valid one.

To tolerate 2-bit random errors or 5-bit burst errors, 526 addresses are cre-

ated for each channel. This is not a serious constraint because high-noise,

low-speed links are normally used by only a small number of users. The

more constraining situation, however, is that the signaling channel VPI value

0 and the VCI value 5 are within 2 bit-errors of the null cell address (0,0).

Thus, in high-error conditions, signaling is inhibited. The payload type indi-

cator (PTI) and generic flow control (GFC) fields need to be separately pro-

tected with the payload.

The user needs only to set up a single connection using a VPI value 0 and a

VCI value in the range from 32 to 92. This provides for 60 simultaneous,

noise-tolerant base connections per slot. Each connection (ATM-to-ATM

VCC, or ATM-to-ATM VPC) is created between an ATM-enabled port on a

6-Port Multiserial module or a 4-Port Quadserial module and another ATM

port. Internally within the PSAX system, the connection is routed through

the CPU module or a DSP2E/F module for the cell-encoding stage.

Cell encoding is executed by the CPUn or a DSP2E/F module on cell payload

data destined for noisy interfaces. Based on a user-selected encoding rate for

the connection, source-data cell payloads are divided into six blocks and fed

into a Reed Solomon encoder. The encoded data, now approximately 48

bytes larger, is loaded into new cell payloads and forwarded to the 6-Port

Multiserial module or a 4-Port Quadserial module for transmission.

The user selects a Reed Solomon encoding rate with a specific error-correc-

tion capability, as follows:

• 1/2 rate

For each data cell, the encoder creates two encoded cells. This rate pro-

vides correction of payload cells with 10-3 BER to 10-6 BER.



255-700-447 3-41



• 1/4 rate

For each set of three data cells, the encoder creates four encoded cells. This

rate provides correction of payload cells with 10-4 BER to 0 BER.

• 1/8 rate

For each set of seven data cells, the encoder creates eight encoded cells.This rate provides correction of payload cells with 10-5 BER to 0 BER.

• Dynamically changing rate options (see Table 3-2):

When the user selects the 1/2, the 1/4, or the 1/8 rate, the encoder maintains

that selected rate of encoding regardless of actual error conditions. When the

user selects one of the dynamically changing rate options, the encoder

employs the 1/2, 1/4, or 1/8 rate, dynamically adjusting the rate as needed,

depending on the number of errors encountered on the decoding side of the

circuit.

Cell scrambling moves the first three bytes of the cell header (the GFC, VPI,

and VCI fields) into the payload and spreads them out to protect against burst

errors. This action increases the burst error tolerance of the header from

5 bits to 54 bits with no cell loss.

Note: Cell scrambling is only supported on the 6-Port Multiserial mod-

ule.

The following modules support FEC enabled connections:

20N07 6-Port Multiserial

23N07 Quadserial

H.248 Media Gateway Access Protocol

The PacketStar ® PSAX Multiservice Media Gateways support the ITU-T Rec-

ommendation H.248.1 (03/2002). This communication control protocol for

convergent networks separates call control and media- and bearer-control

functions.

After the call control and media- and-bearer control functions are separated,

they are transmitted over different network elements. The advantage gained

by separation is to decentralize control from the SS7 network to local net-

works. Decentralization enables transmission cost savings resulting from

enabling gateway peripherals from a central MGC to terminate trunking cir-

cuits near the circuit switches from which they originate.

Table 3-2. Forward Error Correction Automatic Rate Options

Bit Error Rate 10-3

Threshold10-4

Threshold10-5

ThresholdCell Encoding Rate

Automatic—low quality 1/2 rate 1/4 rate 1/8 rate

Automatic 1/2 rate 1/2 rate 1/8 rate

Automatic—high quality 1/2 rate 1/2 rate 1/4 rate




3-42 255-700-447


The PacketStar ® PSAX Multiservice Media Gateways support the following

H.248 functions:

• PSTN terminations to PSTN terminations

• Transcoding of media streams between TDM network and ATM packet net-

works• Terminations processed:

~ PSTN-to-PSTN terminations

~ PSTN-to-ATM terminations

• Control the media streams per MGC request

• Apply signals (tone and/or announcement) to the terminations

• Detect media stream events (tone, continuity check, digits, fax modem) per

MGC request

• Extract D channel signaling messages and transport them to the MGC

• Collect, match, and report in-band (DTMF) digits per MGC request

• Create and destroy terminations per MGC request

• Manage ATM resources

For details, see the PacketStar ® PSAX H.248 Media Gateway Control User Guide.

The H.248 protocol feature is supported on all PSAX systems with the follow-

ing modules:

• Redundant CPUn modules

• All PSAX system ATM-interface I/O modules are supported on the ATM

side of the connection

• All PSAX system TDM-interface I/O modules are supported on the TDM

side of the connection, except for those that do not support channelization

at the DS1/E1 level

Interface and Connection Naming

The Interface and Connection Naming feature provides the ability to name

configured interfaces and PVC and SPVC connections in a PSAX system. The

interface configuration windows provide access to the new Interface Name

Assignment window where the user creates the interface name. All named

interfaces in the PSAX system can be viewed on the new Interface Name

Table window, which is accessed from the Equipment Configuration window.

The following interface types support interface naming:

• ATM IISP user and network

• ATM IMA

• ATM UNI 3.0, 3.1, and 4.0

• CAS trunkline

• Circuit emulation

• Frame relay UNI and NNI

• HDLC passthrough



255-700-447 3-43



• PRI ISDN UNI and NNI

• Terminal emulation

The PVC and SPVC connection configuration windows provide access to the

new Connection Name Assignment window where the user creates the con-

nection name. All named connections in the PSAX system can be viewed onthe new Connection Name Table window, which is accessed from the Con-

nection Configuration Menu window. The following PVC and SPVC connec-

tions types support connection naming:

For the interface and connection names, the user can specify up to 35 alpha-

numeric characters including A–Z, a–z, 0–9, / (forward slash), - (hyphen),

and _ (underscore). The PSAX system differentiates between uppercase andlowercase letters, making the text string for the interface name and the con-

nection name case sensitive. For example PSAX-1234 and psax-1234 are

unique names.

Internet Protocol (IP) Throttling

The IP Throttling feature, introduced in Release 7.1.0, limits the rate at which

the CPUn module accepts IP traffic (through the ETHERNET port or by the in-

band management virtual port) to prevent the CPUn module from being

excessively burdened with traffic. The feature may be applied only to the pri-

mary CPUn module, not to the backup CPUn module.

The feature is initially disabled when the system is running. Once the featureis enabled, traffic will go through the ETHERNET port or the in-band manage-

ment virtual port by its maximum designated throughput set in the Allowed

• AAL2 trunk connection PVC • In-band management IP PVC

• ATM-to-ATM VCC PVC • VBR-to-ATM VCC PVC

• ATM-to-ATM VPC PVC • VBR-to-VBR PVC

• Bridge-to-ATM PVC • ATM-to-ATM VCC SPVC

• Bridge-to-bridge PVC • ATM-to-ATM VPC SPVC

• Circuit emulation-to-ATM VCC

PVC

• Circuit emulation-to-ATM VCC

SPVC

• Circuit emulation-to-circuit emu-

lation PVC

• Circuit emulation-to-ATM stan-

dard AAL2 VCC SPVC

• Frame relay-to-ATM VCC PVC • Frame relay-to-ATM VCC SPVC

• Frame relay-to-frame relay PVC • VBR-to-ATM VCC SPVC

• GR-303-to-AAL2 VCC PVC • VBR-to-ATM standard AAL2 VCC

SPVC




3-44 255-700-447


Rate field on the IP Throttling window. The feature has no impact on the IP

data path if the feature is disabled. The IP Throttling feature processes only

ingress traffic, not egress traffic.

LANET ProtocolThe LANET (limitless ATM network) protocol, coupled with a simple error-

tolerant addressing scheme, facilitates reliable delivery of ATM cells in a

noisy, low-speed environment. By maintaining the cell extraction capabilities

and strengthening the cell header error protection. LANET offers application-

dependent payload protection, allowing selective implementation of band-

width-costly, forward-error-correction techniques. It is designed to identify

and extract ATM cells at bit error rates as high as 10-2.

The main features of LANET include the following:

• Regular framing-bit patterns that enhance cell delineation in noisy envi-

ronments

• Compatibility with traditional link enhancement schemes, such as forwarderror correction (FEC) and bit interleaving

• A consistent interface to the higher layer of the protocol stack (that is, the

ATM layer)

• Independence of transmission rate and media

• Natural synchronization with a standard 8-kHz telecommunication clock

The LANET solution offers link quality-dependent header protection while

maintaining maximum compatibility with ATM standards. Figure 3-9 shows

the relationship between LANET and the Open Systems Interconnection

(OSI) model.



255-700-447 3-45



The LANET protocol is designed to be active in the upper end of the physical

layer of the OSI seven-layer model. Within a byte-oriented serial data stream,

LANET provides a framing structure around ATM cells for transmission pur-

poses and regular frame-marker bit patterns for cell extraction. Each LANET

frame (2,400 bytes) is subdivided into 45 ATM cells (totaling 2,385 bytes)with a 15-byte overhead. This structure permits a transmission rate scalable

according to the physical medium.

The 15-byte overhead, accounting for 0.63 percent of the bandwidth,

includes the LANET frame and subframe headers, which are used in conjunc-

tion with traditional cell header error-detection methods, such as header

error control (HEC), to enhance cell delineation for noisy environments. The

protocol thus becomes independent of the transmission rate while still natu-

rally synchronizing with an 8-kHz transmission clock via the 2,400-bytes-

per-frame structure.

Traditionally, block-error correction schemes, such as Reed Solomon coding,

have been used to protect the header. As a simple alternative, the PSAX sys-

tem software uses an error-tolerant addressing scheme (multiple redundancyaddressing) that establishes multiple virtual circuits to the same destination,

requiring no special hardware nor modification to the current standard. The

addresses for the circuits are within the error space of the principal address

used for actual transmission. The most probable error patterns occurring in

the address field will simply change the address to another valid address. This

approach maintains independence from the application layer because it

Figure 3-9. Relationship Between LANET and the OSI Model

Layer 2

Layer 3

Layer 4

Layer 5

Layer 6

Layer 7

LANET Protocol

Encryption Error Correction Bit Interleaf

Satellite Radio Land Lines

ATM

Voice Video Images Data

SERVICE-INDEPENDENT ARCHITECTURE

Layer 1

From bits per second to megabits per second

CELL-BY-CELL ENCRYPTION




3-46 255-700-447


encodes the header address within the same 10-nibble header space of stan-

dard ATM cells. In addition, it avoids the extra delay (detrimental to CBR

traffic) required of multiple header-encoding schemes.

In practice, to tolerate 2-bit random errors or 5-bit burst errors requires set-

ting up 526 addresses for each channel. This is not a serious constraint

because noisy low-speed links will likely only be used to support a small

number of users.

Finally, given the ability to deliver cells, the payload can now be FEC-pro-

tected on each virtual circuit, depending on the error tolerance of the appli-

cation at the service-specific convergence sublayer (SSCS). Figure 3-10

shows the LANET frame structure.

The LANET subframe functions in the following ways:

• The timely arrival of the header patterns is used as a confidence check,

confirming that the system is properly synchronized.

• In the event of synchronization loss, a PSAX system can easily seek and

resynchronize to the regular appearance of the simple header patterns.

See the description for “Forward Error Correction” on page 3-40 for a list of

modules supporting LANET.

Figure 3-10. LANET Frame Structure



255-700-447 3-47



Operations, Administration, and Maintenance (OAM)

Overview of OAM The Operations, Administration, and Maintenance (OAM) feature, available

on all PSAX systems gives Public Service Providers a way to detect and

receive reports on abnormal behavior in virtual path connections (VPCs) and

virtual channel connections (VCCs) in an ATM network.

OAM performs this function by injecting cells which contain OAM informa-

tion into the network traffic. This information is referred to as a flow . In order

for an OAM flow to function properly, there must be an exchange of opera-

tions information between the various nodes in a network. In the case of an

ATM network, this information is exchanged over permanent and switch vir-

tual connections, with F4 flows designated for OAM traffic over a virtual

path connection, and F5 flows designated for OAM traffic over a virtual

channel connection. These flows provide details about defect and failure

detection, performance monitoring, and defect information.

Note: For information about using OAM to enable trunk conditioning for

upstream or downstream interworking, see the Trunk Conditioning

Application Note for PacketStar ® Multiservice Media Gateways.

OAM CellCharacteristics

OAM cells are bidirectional. They follow the same physical and logical route

as user payload cells. Each flow has two variants: one checks a particular seg-

ment, and the other checks the end-to-end flow.

• Segments are indicated by a virtual channel identifier (VCI) of 3 for F4

flows, or a payload type of 4 for F5 flows.

• End-to-end flows are indicated by a VCI of 4 for F4 flows, or a payload

type of 5 for F5 flows.

OAM segments can be a single ATM link, or group of interconnected links on

an ATM connection, although it is important to note that not all links belongto segments. One or more OAM segments can be defined along a VC, VPC, or

VCC connection, although these segments cannot overlap, nor can they be

nested. A source point of segments acting in a downstream direction will ter-

minate unexpected OAM cells coming from the upstream side of a connec-

tion.

End points, either as part of a full connection, or of a segment, use activation

procedures to request continuity checking with the opposite end point. End-

to-end continuity checks and segment continuity checks are also supported.

The requesting end point specifies the direction of the continuity checking

(from the requesting end point, to the requesting end point, or in both direc-

tions). If the far end accepts the request, the specified source point (or points)

starts sending continuity checks periodically to the receiving point.A connection point (CP) along a connection inserts new OAM cells according

to defined OAM cell usage and procedures. It does not terminate the OAM

flow, except when loopbacks are performed.

The format of an OAM cell is shown in Figure 3-11:




3-48 255-700-447


• Header: this is the same as the ATM cell header

• OAM Cell Type: the management type (fault, activation/deactivation)

• OAM Function Type: the specific function (AIS, RDI, continuity check,

loopback, forward monitoring, backward reporting, and so on)

• Function-Specific Field: data required for the specific function

• Reserved: reserved for further specification

• EDC: CRC-10 error detection code computed over the cell payload (except

the CRC-10 field itself) and used to check for data corruption

OAM ATM LayerFlows

OAM has two flows of management information: F4 and F5. F4/F5 in-band

maintenance flows are defined at the ATM layer for the VPC and VCC level,

respectively. F4 is used for path-level connections, where the virtual path

(VP) flows are identified by reserved values within the path. F5 is used for

circuit-level connections, where the circuit virtual channel (VC) flows are

identified by the payload type (PT) indicator field values.

These flows can be initiated at, or after, a connection setup by:

• call process functions

• OAM functions, or• the network operator.

The hierachial structure of OAM flows is shown in Figure 3-11:

Figure 3-11. OAM Cell Fields

OAM FunctionType Reserved

OAMCellType

ErrorDetection

Code

Function-specific field

Payload

Header

Header

4 4 6 10360 bits (45 bytes)



255-700-447 3-49



OAM F4 Flows OAM flows for F4 in-band maintenance are defined at the ATM layer for the

VPC level. It is used for path level connections, where the virtual path (VP)

flows are identified by reserved values within the path. In addition, they

have the following characteristics:

• Bidirectional flow

• The same VPI value as user cells for the VPC

• Identification by one or more preassigned VCIs for both directions

• Existence in the same physical route for fault correlation and performance

information

OAM F5 Flows OAM flows for F5 in-band maintenance are defined at the ATM layer for the

VCC level. They are used for circuit level connections, where the circuit vir-

tual channel (VC) flows are identified by the payload type (PT) values. In

addition, they have the following characteristics:

• Bidrectional flow

• The same VPI/VCI values as the user cells for the VCC

• Identification by one or more preassigned VCIs for both directions

Figure 3-12. OAM Hierarchy




3-50 255-700-447


• Existence in the same physical route for fault correlation and performance

information

User cells at the F5 level carry VCI cells which are defined below:

(Payload Type Indicator) PTI=4 is a segment OAM F5 flow cell. This flow is

identified by its standardized PTI, and is used for end-to-end VCC operationscommunication.

PTI=5 is an end-to-end OAM F5 flow cell. This flow is identified by its stan-

dardized PTI, and is used for communicating operational information within

the bounds of one VCC link that is a part of multiple inter-connected VCC

links (called VCC segments).

ATM Layer OAMFunctions

OAM functions performed at the ATM layer are:

• Fault Management

~ Alarm Indication Signals (AIS) — A network element (NE) transmits an

AIS alarm downstream when it receives a major alarm condition such asa loss of frame. This prevents the generation of unnecessary alarms, and

maintains communications.

~ Remote Defect Indication (RDI) — RDI cells are generated and tranmit-

ted while the AIS state persists in order to indicate in the backward direc-

tion an interruption of the cell transfer capability in the forward direc-

tion.

~ Continuity Check — This check is used within a network to provide the

continuous detection of ATM layer failures. End points, of either the full

connection, or a segment, use activation procedures to request continu-

ity checking with the opposite end point, at predetermined intervals. If

the sink point does not receive continuity cells as expected, AIS and RDI

alarms are transmitted.

~ Loopback — Loopback checks isolate failed entities if defect information

is insufficient. A loopback check detects faults in the physical and ATM

layers, and detects defects and declarations of failure within the network

elements. It is also used for on-demand connectivity monitoring and pre-

service connectivity verification.

A loopback procedure can be initiated at any connecting, segment, or

end point by a Network Management System (NMS) that also receives

the report on loopback performance.

A loopback location identifier is assigned to each connecting point at the

operator’s option. This identifier identifies a unique connecting point

within a segment or within the entire path. Then, a VPC or VCC end or

connecting point sends a loopback cell to a destination end or connecting

point, while a segment loopback is looped back at the destination point.

If the source receives a looped cell back within five seconds, the loopback

is considered successful. If the source does not receive a successful loop-

back, it declares a time out. The following types of loopback are sup-

ported:

• End-to-end: Sends cells from one designated end-point to another.



255-700-447 3-51



• Segment-endpoint: Sends a loopback cell from a designated segment to

a designated segment end-point.

• Next-connection-point: Sends segment OAM cells within designated

segments to check the connectivity between the segment point from

where the cell was issued to the next immediate connection point.

• Specific-location: Sends OAM loopback cells between user-specified

locations within a segment.

• Activation/deactivation is an in-service OAM mechanism used to remotely

start and stop generating the cells that perpetually monitor performance

and continuity.

A VPC or VCC end or connecting point (the source) sends an activation or

deactivation request to the receiving point. The receiving point responds by

either confirming or denying the request. On receiving an activation con-

firmation, the source or receiver (depending upon the direction of the

action) periodically generates performance management or continuity

check cells.

The activation/deactivation cells are OAM cells with the function-specific

fields as shown in Figure 3-13.

Message ID cells indicate whether to request, confirm, or deny the activa-

tion or deactivation of cells

Directions of action cells give the direction (or directions) in which to

start/stop generating performance management or continuity cells

A-B (ingress) cells move away from the activator/deactivator

B-A (egress) cells move toward the activator/deactivator

Both cells are neither A-B nor B-A cells, but are cells that move bidirec-

tionally.

Correlation tag cells give the number used to correlate transmitted activa-

tion/deactivation requests with their responses

PM block size (A-B, B-A) is a feature that works with activation requests

only. It monitors the size of user cell blocks that monitor the performance

in the forward or backward direction. The default is 1,024 cells.

Packet Pipe AAL5-to-AAL2 Wireless Trunking for Mobile Voice

In a wireless TDMA system, using an HDLC passthrough interface over AAL5for backhauling between the BS and the MSC provides cost benefits over a

TDM-based backhauling system currently in use. The Packet Pipe AAL5-to-

AAL2 Wireless Trunking feature on the DSP2E/F Voice Server modules

addresses this need.

Figure 3-13. OAM Activation/Deactivation Cells

MessageID

Directionsof Action

CorrelationTag

PM BlockSize A-B

PM BlockSize B-A

Unused

6 2 8 4 4 336 bits (42 bytes)




3-52 255-700-447


This feature supports packet switched wireless backhaul networks for inter-

connecting Lucent MSCs and Series II base stations using the Lucent propri-

etary packet pipe protocol over land lines. This protocol performs encapsula-

tion within ATM AAL2 for various cell site sizes.

DSP features on wireless applications are supported on these modules:

The following PSAX modules support the Wireless Mobile Voice feature:


• 1-Port Channelized STS-1e, T1 Format

• 12-Port Medium-Density DS1 Multiservice

See the description for “HDLC Passthrough Bit Inversion” on page 3-11 for a

list of modules supporting HDLC Passthrough Interface.

SNMP Trap Descriptions

The PSAX system provides the capability to display SNMP trap messages on

the console interface and on the AQueView Element Management System.The trap message log is 64 KB in size and can hold up to 1,040 trap messages.

If the trap log is full, the PSAX system dumps trap messages on a FIFO (first

in, first out) basis. External SNMP managers can perform various functions in

the PSAX system, and also receive trap and notification messages. The SNMP

trap message log provides the following functions on the console interface

and the AQueView EMS:

• Searching for all instances of a specific character string in the log

• Viewing detailed information, the trap message help, for one or more trap

messages

The procedure to access the console interface Trap Log Display window and

decriptions of the SNMP trap messages are provided in the document,

PacketStar ® PSAX Simple Network Management Protocol (SNMP) Trap Reference

Guide.

Traffic Management Using the AQueMan Algorithm

With ATM, predictable quality of service (QoS) is achieved for all applications

by transmitting voice, video, and data using short, fixed-length cells inter-

leaved at guaranteed bit rates. The guaranteed bit rates are implemented by

assigning ATM Forum-established QoS classes for each type of data to be

transferred. The following attributes are considered in assigning an ATM ser-

vice class:

• Cell transfer delay characteristics• Cell loss ratio

• The type of connection required

• The timing or synchronization of the source and destination

The AQueMan algorithm manages traffic while supporting ATM Forum

classes of service. This adaptive algorithm allocates bandwidth by statistically

multiplexing traffic within two sets of queues according to weighted priori-



255-700-447 3-53



ties. One queue set addresses avoidance of cell loss, which is normally a con-

cern for data traffic, while the other set manages cell transfer delay, which is

critical to voice and some video traffic.

Within each set of queues, The AQueMan algorithm assigns internal priori-

ties even more specialized than the ATM Forum class definitions. Generally,

the lower the assigned priority number, the greater the access to bandwidth

and the less likelihood of loss. For additional information on ATM QoS, see

“ATM Service Categories in the PSAX System” on page C-35.

The AQueMan algorithm classifies traffic based on service-level priorities and

limits congestion by addressing three dimensions of traffic management:

• Cell loss versus cell delay for cell discard

As Table 3-3 indicates, there are VBR traffic types (for example, network

management data traffic) that are, in fact, higher in priority than some

CBR traffic (for example, off-peak cellular voice calls). The AQueMan algo-

rithm accounts for the service-level priorities of the traffic when determin-

ing which cells to discard during traffic congestion. Thus, CBR does not

necessarily imply a higher priority.

• Weighted priorities using queue depth ratios

To alleviate congestion in the network caused by lower-priority VBR traffic,

the AQueMan algorithm provides a weighted priority mechanism. This

mechanism allows lower-priority VBR data to be sent ahead of higher-pri-

ority VBR data in cases where there are too many cells in lower-priorityVBR buffers and relatively few cells in higher-priority VBR buffers. The

execution of this algorithm is based on the priority levels the user selects.

• Cell aging

This capability prevents the lowest-priority data (for example, IP data)

from being buffered in the Multiservice Media Gateway systems indefi-

nitely. The AQueMan algorithm keeps track of how long each cell stays in

the buffer. The lower the priority of the traffic, the longer its cell-aging

time; that is, UBR traffic has a longer cell-aging period than VBR-RT traffic.

This capability allows the Multiservice Media Gateway systems to periodi-

cally send low-priority cells through the network. Doing so prevents

retransmission of IP data traffic while increasing the time-out window for

the TCP/IP sessions. The cell-aging mechanism allows for orderly deconges-tion of the network without resorting to traffic rerouting and other compli-

cated protocols and procedures.

Table 3-3. CBR and VBR Service-Level Priorities

Priority CBR VBR

High 911 voice call Network management data

Low Off-peak cellular voice IP data




3-54 255-700-447


ATM Traffic Management

Guaranteed FrameRate

The Guaranteed Frame Rate feature for ATM traffic management provides

the GFR.2 service type on ATM PVC connections. The GFR.2 service type

enables users to specify a cell transmission rate up to the PCR rate, but the

network can commit to only carry cells in complete unmarked frames at theMCR rate. Traffic transmitted in excess of MCR and MBS rates are delivered

within the limits of available resources. The fairness policy is network spe-

cific.

The Guaranteed Frame Rate (GFR) feature for ATM Traffic Management

operates on the following PSAX I/O modules:


• 12-Port Medium-Density DS1 IMA

• 21-Port High-Density E1 IMA

• 21-Port High-Density E1 Multiservice

• 1-Port Channelized DS3 Multiservice• 1-Port Channelized STS-1e, T1 Format

• 1-Port DS3 IMA

• 3-Port DS3/E3 ATM Protection

• 3-Port DS3/E3 ATM

• 1-Port OC-12c/STM-4c Multimode and Single-Mode

• 4-Port OC-3c/STM-1 Multimode and Single-Mode

• 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Multimode and

Single-Mode (STM-1 ATM mode only)

• 4-Port Quadserial

Usage ParameterControl

Usage parameter control (UPC) allows the end system to police ingress con-nections for service level agreement compliance. After a set of service catego-

ries is specified, UPC is given a set of parameters for each, describing the traf-

fic presented to the network and the quality of service the network requires.

A number of traffic control mechanisms are defined, which the network may

use to meet the QoS objectives.

Note: The feature that was formerly known as “Rate Shaping” is now

called “ATM Traffic Shaping” to distinguish it from the”Cell bus

traffic shaping” feature, which was formerly called “Traffic Shap-

ing”.

UPC Support UPC support is available on these modules:

23N75 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM

Multimode

23N76 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM

Single-Mode

23N72 1-Port OC-12c/STM-4c Multimode



255-700-447 3-55



UPC is available on these DS3 modules (when using channelization to DS0s):

Early Packet Discard The PSAX system ATM Traffic Management feature includes the implemen-

tation of the early packet discard (EPD) function for PVC and SPVC connec-

tions that support the service type UBR and the SAR type AAL5. The EPD

function improves the efficiency of the connection by reducing the amountof bandwidth needed when traffic congestion occurs. During traffic conges-

tion, the EPD function causes packets to be discarded at the moment the sys-

tem detects that the first cell in a packet has a lower priority. This immediate

packet discarding saves bandwidth over a method whereby a packet is dis-

carded after several cells have already been sent. Users enable the EPD func-

tion when they choose the service type UBR and the SAR type AAL5 on ATM

PVC and SPVC connections.

Cell Bus TrafficShaping

The Cell bus traffic shaping feature is a method for controlling the flow of

data traffic. Specifically, it restricts the peak output rate of a module before

the traffic reaches the backplane or midplane. It is implemented in firmware

on modules that are offered with Cell bus traffic shaping variations: the OC-

3c MM/SM TS and the STM-1 MM/SM TS modules. (The feature is not com-

patible with the VI Support feature or the UPC Support feature on the con-

nection interface types ATM IISP, ATM PNNI, and ATM UNI. If the Traffic

Shaping feature is enabled, do not enable the VI Support feature or the UPC

Support feature at the same time).

23N73 1-Port OC-12c/STM-4c Single-Mode

20N72 1-Port OC-3c 1+1 APS Multimode

20N73 1-Port OC-3c 1+1 APS Single-Mode

20N92 1-Port STM-1 1+1 MSP Multimode

20N93 1-Port STM-1 1+1 MSP Single-Mode

24N70 2-Port OC-3c/STM-1 ATM Multimode

24N71 2-Port OC-3c/STM-1 ATM Single-Mode

24N72 4-Port OC-3c/STM-1 Multimode

24N73 4-Port OC-3c/STM-1 Single-Mode





23N07 Quadserial




3-56 255-700-447


Note: The feature that was formerly known as “Traffic Shaping” is now

called “Cell bus traffic shaping”to distinguish it from the “ATM

Traffic Shaping” feature, which was formerly called “Rate Shap-

ing”.

Cell bus traffic shaping ensures that VBR traffic entering the Multiservice

Media Gateway system (via the OC-3c TS and STM-1 TS modules) complies

with the parameters of established service contracts. If bursty VBR traffic

exceeds the parameters of the output connection, the rate of the traffic flow

is controlled to comply with the specified output rate by means of an input

cell-selection algorithm before the traffic flow reaches the Multiservice Media

Gateway backplane. If traffic exceeds the buffer of the OC-3c TS or STM-1 TS

modules, cells are discarded. Cell bus traffic shaping allows the network side

of the Multiservice Media Gateway system to multiplex more efficiently the

traffic shaped VCCs with other CPE traffic (voice, video, and so on) for trans-

port across the ATM network link. CBR traffic is unaffected by Cell bus traffic

shaping.

The Cell bus traffic shaping feature is shown in Figure 3-14.

An end user has an ATM DS3 network connection and has subscribed to a

VBR VCC connection contract from a carrier (service provider) with the fol-

lowing traffic parameters:

• SCR is 40,000 cells/second,

• PCR is 80,000 cells/second, and• MBS is 250 cells.

Even though LAN switches usually maintain a sustained cell-transport rate of

40,000 cps, they allow LAN traffic to burst in violation of carrier traffic con-

tracts, causing clusters of cells to exceed the MBS parameter. Because carriers

monitor traffic at the edge of a network and enforce adherence to traffic con-

tracts by discarding cells that exceed the MBS parameter, end users whose

traffic violates their contractual MBS parameter experience high cell loss

Figure 3-14. Cell Bus Traffic Shaping Occurs on Egress to the Backplane

PSAX

Bus

O C

- 3 c

Any

ATM

Module

Bursty

PCR

6 MB

Traffic Shaping on a 2 MB

Service Contract Occurs Here

Traffic Router

A T

M

OC-3c

Module

Egress



255-700-447 3-57



(and hence high packet loss). With the traffic shaping feature of the OC-3c TS

and the STM-1 TS modules, the Multiservice Media Gateway system effec-

tively smooths bursty input LAN traffic to comply with the carrier traffic con-

tract.

The input cell-selection buffering scheme is shown in Figure 3-15.

Connected to the LAN ATM switch via an ATM OC-3c TS or STM-1 TS link,

the OC-3c TS and the STM-1 TS modules support a total of 119 VCCs and

VPCs. All inbound traffic is processed by the input cell selection algorithm,

dynamically shared by all VCCs and VPCs, which smooths the traffic. The

module buffer of the OC-3c TS or the STM-1 TS module is always 4 MB

smaller than the total amount of memory installed on the module. For exam-

ple, if 8 MBs of memory are installed, 4 MBs are available for queuing; if

32 MBs of memory are installed, 28 MBs are available for queuing. This

dynamically shared buffer allows inbound VBR traffic to burst up to the line

rate.

The module buffer of the OC-3c TS or the STM-1 TS module is set up with a

maximum-capacity level (defined as 31/32 of the buffer size), and a mini-

mum-capacity level (defined as 3/4 of the buffer size). When the incoming

cells exceed the maximum-capacity level, the input cell-selection algorithm

starts discarding cells to maintain a smooth traffic flow. The algorithm dis-cards traffic on the connection with the longest queue first, then traffic on

the connection with the second longest queue, and continues on until the

module buffer of the OC-3c TS or the STM-1 TS module reaches the mini-

mum-capacity level.

Figure 3-15. Cell Bus Traffic Shaping Using the Input Cell-Selection Algorithm

MBSGreater Than

250 Cells

Line Rate

VPC/VCC 1

VPC/VCC 2

S C R

S C R ToBackplane

MBS of Each VPC/VCCConnection UsuallyLess Than 50 Cells

S C R

VPC/VCC 119

Smoothed VPC/VCCs

SCR

Sample Input on a VPC/VCCConnection from a Bursty LAN

Input Enters

OC-3c Module Buffer

OC-3c ModuleBuffer

Maximum Capacity

Minimum Capacity




3-58 255-700-447


The algorithm processes traffic moving out of the input cell selection buffer

according to the SCR of the particular VPC/VCC. The MBSs of traffic shaped

output are set as follows:

The OC-3c TS and the STM-1 TS modules can perform Cell Bus Traffic Shap-

ing on multiple high-rate connections (such as three 40-Mbps connections).

Assigning a SCR to a connection above 75 Mbps, however, is not recom-

mended in sensitive, bursty traffic environments. Assigning a SCR above

120 Mbps will essentially eliminate any Traffic Shaping, and thus is strongly

discouraged.

The OC-3c TS and the STM-1 TS modules perform only limited traffic man-

agement on the output side. The output buffer is limited to 2 Mbps for VBR

traffic and 128 cells for CBR traffic, with only three priority levels supported:

CBR, VBR1, and VBR2. The maximum-capacity level for congestion control

is 32,000 cells, and the minimum-capacity level is 24,576 cells, with VBR

traffic being shut off first from the backplane.

ATM Traffic Shaping

Overview of ATMTraffic Shaping

The ATM Traffic Shaping feature uses an algorithm to transmit frames seg-

mented into ATM cells into the ATM network at a steady rate. This algorithm

performs per-VC queuing with a maximum queue size of 200 cells. ATM

Traffic Shaping can be applied to PVC, SVC, or SPVC connections, on all types

of traffic, but the feature must be configured prior to traffic exiting from the

ATM trunk port. On SPVC connections, the feature must be enabled on the

active and passive sides of the end-to-end connection, as well as on the sup-

porting interface configuration window, for the feature to function as

designed. The ATM Traffic Shaping algorithm is applied to cells as they exit

the PSAX backplane or midplane, as illustrated in Figure 3-16.

Sustained Cell Rate

(SCR) of VPC/VCC

Maximum Burst Size (MBS) of Traffic

Shaped Output0–20 Mbps < 4 cells

20–30 Mbps < 5 cells

30–40 Mbps < 6 cells

75–120 Mbps approximately 20–50 cells



255-700-447 3-59



Any connection that has ATM Traffic Shaping enabled at both the interface

and connection levels will shape traffic on ATM, frame relay, HDLC, and

Ethernet interfaces, before the traffic leaves the ATM trunk port. ATM Traffic

Shaping transmits ATM cells onto the ATM network at the peak cell rate,

based on the ATM Traffic Shaping algorithm.

• For frame relay traffic, the PSAX system software automatically calculates

egress peak cell rate based on frame relay traffic parameters.

• For Ethernet and HDLC traffic, the user must configure the egress peak cell

rate.

For detailed ATM connection configuration instructions, see the PacketStar ®

PSAX System Connections Provisioning Guide.

Configuring ATMTraffic Shaping forHDLC, Frame Relay,

and Ethernet VirtualChannels

To configure the ATM Traffic Shaping feature, the Traffic Shaping field must

be set to Enabled on the ATM UNI 3.1, ATM PNNI, or ATM IISP interface

configuration windows of one of the following modules:

Figure 3-16. Sample ATM Traffic Shaping Flow

PSAX ChassisBackplane orMidplane

2-Port or 4-Port OC-3c/STM-1 ModuleSide B

Tx/Rx

Ingress

4-Port Ethernet ModuleSide A

Bursty PCR to 6 MB

Egress

Traffic Shaping does not occuron egress B to A side direction

ATM

A to B Side

B to A Side

Rx

Tx

Ingress

Traffic Shaping on 2 MB Service Contract

Egress

B to A Side

A to B Side

Traffic Shaping occurs onegress B to A side direction









3-60 255-700-447


For frame relay traffic, the PSAX system software automatically calculates

egress peak cell rate based on frame relay traffic parameters.

For Ethernet and HDLC traffic, you must enter the egress PCR on the VBR-

to-ATM PVC or SPVC Connection window. See the ATM Traffic Shaping

Table in the Reference Appendix of this document for the Minimum/Actual

Target rate for the bps rate you want to use. In either case, the PCR is used to

shape the egress traffic not to exceed the PCR.

Task Summary forImplementing ATMTraffic Shaping

To implement ATM Traffic Shaping, these configuration conditions must be

met:

• The TS field is Disabled by default. The TS field must be set to Enabled at

the interface configuration level. When Traffic Shaping is enabled, egress

traffic on an ATM port is then controlled by the “leaky bucket” algorithm.

• Only traffic on frame relay, Ethernet, HDLC, and ATM connection types

that are routed through an ATM traffic shaping-enabled port is subject to

Traffic Shaping.

• ATM Traffic Shaping is available on the UBR, VBR, and GFR service types.

• ATM traffic is subject to shaping on a per-connection basis.

VBR ATM TrafficShaping Priorities

Connections employing the ATM Traffic Shaping feature on the PSAX CO

product line have an egress priority less than CBR and VBR-rt connections,

and greater than VBR-nrt and UBR connections. The data rate available on

ATM traffic-shaped connections on a given interface is the interface data rate

minus the overall data rate reserved for CBR and VBR-rt connections.

The ATM Traffic Shaping feature is designed to transmit frames segmented

into ATM cells onto the ATM network at a steady rate; for example, at the

sustained PCR of the connection. The feature performs per VC queuing with

a maximum queue size of 200 cells. As the amount of CBR and VBR-rt traffic

on an interface increases, the probability increases that ATM traffic-shaped

traffic will have to be queued. This will impede the ability to maintain the

SCR of the ATM traffic-shaped connection(s) and eventually the queues will

overflow, causing packets to be dropped.

To prevent a ATM traffic-shaped connection from having packets dropped

due to queuing, it is necessary to provision the connection’s PCR greater than

its SCR. Include in your calculation the function (F) in the formula (see the

section titled ”Formula for Determining the PCR of a ATM traffic-Shaped

Connection” below for the total CBR and VBR-rt traffic provisioned for the




24N72 4-Port OC-3c/STM-1 Multimode24N73 4-Port OC-3c/STM-1 Single-Mode

23N74 3-Port DS3/E3 ATM



255-700-447 3-61



interface (for more information, see the earlier section ”VBR ATM Traffic

Shaping Priorities”). Note that the ATM Traffic Shaping feature does not use

the connection's MBS. This, in effect, creates a ‘guard band’ around the con-

nection to minimize the probability that a CBR or VBR-rt cell will be trans-

mitted at the same time a ATM traffic-shaped cell is scheduled to be transmit-

ted. It is critical that accurate values for the connection parameters be used.

ATM Traffic Shapingfor CBR and VBR-rt

The CBR traffic and VBR-rt connection affect the actual PCR rate of the ATM

traffic-shaped connections. CBR and VBR-rt traffic should be limited to 75%

to 80% of the port speed when traffic shaping is being used by the port. Fur-

thermore, to guarantee performance of the traffic shaping algorithm, the SCR

/ PCR of shaping connections should be less than or equal to:

1 – total traffic that is left after the cbr and vbr-rt have been subtracted from

total traffic flow into a port.

Maximum Number ofATM Traffic-Shaped

Connections

Each OC-3c 1+1 APS and STM-1 1+1 MSP module supports 2,046 traffic-

shaped connections. The minimum PCR rate supported by the algorithm is

20 cps; the maximum is 4680 cps (E1 interface speed). A rounding error isintroduced by the integer division used by the algorithm, so the granularity

of the PCR rates supported by the algorithm suffers when the PCR exceeds

the E1 speed. See the ATM Traffic Shaping Table in the Reference Appendix

of the STM-1 1+1 MSP or OC-3c 1+1 APS Module User Guide, or the chassis

User Guide for a comparison between configured PCR and actual PCR deliv-

ered by the ATM Traffic Shaping feature. For example, if the ATM traffic-

shaped connection is configured with a PCR (Min/Actual Target CPS column)

of 906 to (Max Target CPS column) of 909, the ATM Traffic Shaping feature is

actually shaping the traffic to the (Actual PCR column) of 906 cps. The diver-

gence is smallest at low PCR.

How the ATM TrafficShaping AlgorithmWorks

Queuing is maintained for the traffic-shaped connections on a per VC basis.

To schedule the processing of the queues appropriately such that cells will be

sent at appropriate intervals, an offset time (versus no offset time) for each

queue is calculated based on the PCR.

Offset Time ValueFormula

The offset time value is calculated by the following formula:

T = 353207/PCR

ATM Traffic ShapingAlgorithm

The ATM Traffic Shaping feature uses a table of 80,000 data cell storage

boxes. Each box holds a list of queue numbers (see Figure 3-17 for sample

queue values in boxes 1–3). Each queue can have up to 200 data cells. For

example, if the traffic shaper reads the data in box 1(see Figure 3-17) and the

queue number is 386, it will send one cell from queue 386. If the offset time

value T is 20, the ATM traffic shaper moves queue number 386 to box 21(box 1 + T value 20), providing the timing for the next time that queue 386

will be visited. Figure 3-17 shows a graphic illustrating the algorithm logic.

See ATM Traffic Shaping Example section below for a more detailed descrip-

tions of the mechanics of data movement.




3-62 255-700-447


ATM Traffic ShapingSoftware in Action

The example below follows the ATM traffic shaper action for boxes 1–3 on

the ATM Traffic Shaping table.

1. In box 1, the first queue is 386 with a T value = 20. The ATM traffic

shaper reads these values.

2. The ATM traffic shaper sends out a cell from queue 386, and calculates

the new location for queue 386:

T value = 20 + box # 1 = (20+1) = 21

3. The ATM traffic shaper transfers queue 386 into box 21 on the ATM Traf-

fic Shaping table (to the bottom of the queue stack in box 21 if that box

has other queues in it. If the box is empty, queue 386 is now first in line

to transmit a cell when the ATM traffic shaper gets to box 21).

4. The ATM traffic shaper progresses to box 2 on the ATM Traffic Shaping

table, and repeats the process described in Steps 1 and 2 above.

5. On box 2 of the ATM Traffic Shaping table, the first queue is 1999 with a

T value = 35. The ATM traffic shaper reads these values.

6. The ATM traffic shaper sends out a cell from queue 1999, and calculates

the new location for queue 1999:

T value 35 + Box # 2 = (35+2) = 37

7. The ATM traffic shaper transfers queue 1999 into box 37 on the ATM

Traffic Shaping table to the bottom of the queue stack in box 37.

8. The ATM traffic shaper progresses to box 3 on the ATM Traffic Shaping

table, and repeats the process described in Step 1 and 2 above.

9. On box 3 of the ATM Traffic Shaping table, the first queue is 6 with a T

value of 50. The ATM traffic shaper reads these values.

10. The ATM traffic shaper sends out a cell from queue 6 and calculates the

new location for queue 6:

T value 50 + Box # 3 = (50+3) = 53

11. The ATM traffic shaper transfers queue 6 into box 53 on the ATM Traffic

Shaping table to the bottom of the queue stack in box 53.

12. The ATM traffic shaper progresses to box 4 of the ATM Traffic Shaping

table and repeats Steps 1 through 3 and cycles through all 80,000 cells

over and over, using this algorithm.

Figure 3-17. ATM Traffic Shaping table Sample Queue 1 Values

Box 1Queue 1 = 386

2046

Box 2Queue 1 = 1999

2046

Box 3Queue 1 = 6

2046

Box 80,000Queue 1 = n

2046

Example Example Example



255-700-447 3-63



Traffic-shaped queues have the priority of "VBR-shaping" which is below

VBR-rt2 and above VBR-nrt1. Generally, in an AQueMan environment, traf-

fic from all CBR queues and VBR-rt queues will be sent before the traffic

shaped queues are examined. The existence of CBR and VBR-rt traffic on the

ATM module will cause the module to send traffic shaped cells below the tar-

geted PCR.

Formula forDetermining the PCRof an ATM Traffic-Shaped Connection

For ATM traffic-shaped connections, you should set the PCR value so that it

conforms to the following expression:

where:

PCR = the PCR of the ATM traffic-shaped connection

SCR = the SCR of the ATM traffic-shaped connection

F is a function of the summation of the PCRs of constant bit rate connec-

tions plus the SCRs of the variable bit rate (real time) connectionsdivided by the interface data rate. The value of F can be expressed math-

ematically as follows:

The network should be designed with a bounded value of F . When the

value of F is initially calculated, it must use the PCR and SCR of the total

number of CBR and VBRrt connections that will be provisioned on the

network interface.

Connection EgressPriority on PSAXModules SupportingATM Traffic Shaping

:In Traffic Management 4.0, af-tm-0056.000, the ATM Forum defined traffic

shaping as a method to meter traffic onto egress facilities so that traffic con-

tracts are not violated on ingress to the next ATM switch on the VC path. In

the PSAX system, PCR traffic shaping per VC is done on user-selected VCs on

the following modules when the value Enabled is selected in the Traffic

Shaping field on the ATM UNI Interface Configuration window, and in the TS

field on the ATM PVC/SPVC connection configuration windows.

Connections employing the ATM Traffic Shaping feature have egress priority

above VBRrt connections but below that of CBR connections on the follow-

ing modules:

PCR >SCR

(1 - F )

F =∑ PCR of CBR connections + ∑ SCR of VBRrt connections

interface data rate




45N74 3-Port DS3/E3 ATM Protection





3-64 255-700-447


Connections employing the ATM Traffic Shaping feature have egress priority

above VBRnrt and UBR connections but below that of CBR and VBRrt con-

nections on the following modules:

ATM Traffic ShapingCapabilities by PSAXModule

The ATM Traffic Shaping capability is supported on the PSAX modules listed

in Table 3-4. The table includes information on the maximum number of VCs

using traffic shaping, minimum PCR for traffic shaping, queue size, priority,

software release in which traffic shaping was introduced, and precision of

traffic shaping for one connection.













Table 3-4. ATM Traffic Shaping Capabilities by Module

Modules

Max. No.of VCsUsingTraffic

Shaping

Min. PCRfor

TrafficShaping*

QueueSize

Priority

Release inWhichTraffic

ShapingIntroduced

Precision ofTraffic

Shaping forOne

Connection†

20N72 1-Port OC-3c 1+1

APS Multimode2,046 18 cps 1000 After

VBR-rt2

6.3.0 ~50% of

line rate

20N73 1-Port OC-3c 1+1

APS Single-Mode2,046 18 cps 1000 After

VBR-rt2

6.3.0 ~50% of

line rate

20N92 1-Port STM-1 1+1MSP Multimode

2,046 18 cps 1000 AfterVBR-rt2

6.3.0 ~50% ofline rate

20N93 1-Port STM-1 1+1

MSP Single-Mode2,046 18 cps 1000 After

VBR-rt2

6.3.0 ~50% of

line rate

23N72 1-Port

OC-12c/STM-4c Multimode32,000 87 cps Program-

mable

After CBR 7.1.3 ~1% of line

rate



255-700-447 3-65



23N73 1-Port

OC-12c/STM-4c Single-Mode32,000 87 cps Program-

mable


rate

23N74 3-Port DS3/E3 ATM 32,000 7 cps Program-

mable


rate

24N72 4-Port OC-3c/STM-1

Multimode32,000 24 cps Program-

mable


rate


Single-Mode32,000 24 cps Program-

mable


rate

23N64 12-Port Medium-

Density DS1 Multiservice32,000 150 cps Program-

mable

After

VBR-rt2

8.1.1 ~50% of

line rate

23N35 24-Port High-Density

DS1 Multiservice32,000 150 cps Program-

mable

After

VBR-rt2

8.1.1 ~50% of

line rate


E1 IMA32,000 150 cps Program-

mable

After

VBR-rt2

9.0.0 ~50% of

line rate


E1 Multiservice32,000 150 cps Program-

mable

After

VBR-rt2

8.1.1 ~50% of

line rate

23N60 1-Port Channelized

DS3 Multiservice32,000 150 cps Program-

mable

After

VBR-rt2

8.1.1 ~50% of

line rate


STS-1e, T1 Format32,000 150 cps Program-

mable

After

VBR-rt2

8.1.1 ~50% of

line rate


ATM Multimode32,000 24 cps Program-

mable


rate


ATM Single-Mode32,000 24 cps Program-

mable


rate


OC-3/STM-1 Unstructured

CES/ATM Multimode

32,000 24 cps Program-

mable

After CBR 8.1.5 ~50% of

line rate


OC-3/STM-1 Unstructured

CES/ATM Single-Mode

32,000 24 cps Program-

mable

After CBR 8.1.5 ~50% of

line rate

* If you specify a rate below the minimum supported PCR, the module defaults to traffic shapingat the minimum supported PCR.

† A connection configured for a rate less than the specified line rate has an output rate within 1%

of the PCR.

Table 3-4. ATM Traffic Shaping Capabilities by Module (Continued)

Modules

Max. No.of VCsUsingTraffic

Shaping

Min. PCRfor

Traffic

Shaping

*

QueueSize

Priority

Release inWhichTraffic

Shaping

Introduced

Precision ofTraffic

Shaping forOne

Connection†




3-66 255-700-447


Virtual Interfaces

Virtual interfaces (VIs) are configured on a module’s physical ports and allow

virtual channels (VCs) to be assigned to virtual trunks, each with its own pri-

ority queues. By using VIs instead of physical connections, it is possible to

achieve an advanced bandwidth management capability allowing for fullyflexible service provisioning. Working in conjunction with the AQueMan

algorithm and usage parameter control (UPC), VIs give service providers a

way to maximize revenue by oversubscribing their bandwidth without vio-

lating their QoS agreements.

VIs enhance the ability of the PSAX system to do the following:

• Provide flexibility for PSAX system to be set up for VPN services

• Maximize the capabilities of the AQueMan software queuing algorithm

• Provide a mechanism for ingress traffic control features

VIs are a collection of VCs, a VP containing multiple VCs, a collection of mul-

tiple VPs, or a single virtual circuit carrying VBR or UBR service. VIs allow

multiple interfaces to be transported through the system with individual bandwidth controls. They shape a set of ATM connections to the contracted

rate in order to avoid cell loss due to policing. See Figure 3-18 for examples

of the uses for VIs.

PSAX ModulesSupporting VirtualInterfaces

The Virtual Interfaces feature is supported on the following PSAX modules:

Figure 3-18. Sample Uses of Virtual Interfaces

Virtual Interface 1

Virtual Interface 0 WAN ATM Link

Virtual Interface 2

Virtual Interface 3

Virtual Interface 4

Single PVC VCC with UPC

Single VPC w/ multiple SVCVPI/VCI inside

Multiple VPC w/ UPC

All other Traffic with UPC control

and Traffic Shaping





23N72 1-Port OC-12c/STM-4c Multimode23N73 1-Port OC-12c/STM-4c Single-Mode

24N70 2 Port OC-3c/STM-1 ATM Multimode

24N71 2 Port OC-3c/STM-1 ATM Single-Mode




255-700-447 3-67



Configuration Compatibility for ATM Traffic Shaping, UPC, and VI

Configuration compatibility among the ATM Traffic Shaping, UPC Support,

and VI Support features is shown in Table 3-5. In the table, Yes indicates that

the two features coinciding in the matrix can be configured in the same

interface, and No indicates that they cannot. See Figure 3-19 for an illustra-

tion of this concept.



45N74 3-Port DS3/E3 ATM Protection

Table 3-5. ATM Traffic Shaping, UPC Support, and VI Support ConfigurationCompatibility

Fields on ATM UNI, PNNI, and IISPConfiguration Windows ATM TrafficShaping per VC VI Support UPC Support

ATM Traffic Shaping per VC No Yes*

* UPC support and Traffic Shaping per VC are supported on the same end-to-end

connection only when VI is configured on the egress path, and UPC on the

ingress path.

VI Support No Yes

UPC Support Yes* Yes




3-68 255-700-447


Voice Compression

Voice compression over AAL2 works for any voice channel using A-Law or

µ-Law PCM. Non-multiplexed AAL2 sends one ATM cell every 5 seconds

when silence suppression is enabled. Standard AAL2 transmission provides a

triple redundancy every 5 seconds to protect against packet loss. In Release8.0, the DSP2D Voice Server module sends silence suppression packets every

100 msec.

See the PacketStar PSAX DSP2x Voice Server Module User Guide for information

detailing the nine AlgoSets (algorithm sets) and the type of voice compres-

sion offered, if applicable.

V5.2 European IDLC

The PSAX system implementation of the V5.2 IDLC application offers loop

emulation services for PSTN and ISDN-PRI. The VoDSL oversubscription is

done on the local exchange end of the connection. The configuration of the

access network and the IAD supports the oversubscription. Silence suppres-

sion is supported per ITU-T I.366.2 to prevent the use of bandwidth for chan-

nels during silence intervals. Idle channel suppression is supported per ATM

Forum af-vtoa-0113 and af-vtoa-00085, to prevent the use of bandwidth for

channels that are idle.

The ATM virtual circuits through the ATM network between the CP-IWF and

the CO-IWF can be SVCs, PVCs, or SPVCs carrying:

Figure 3-19. Combining the UPC Feature and Either the TS or VI Feature on aConnection

Chassis Backplane

VI or TS

Rx

Tx

Ingress Path

Egress Path

UPC

I/O Module 1

VI or TS

Rx

Tx

Ingress Path

Egress Path

UPC

I/O Module 2



255-700-447 3-69


Chapter 3 System FeaturesVoice Processing

• Bearer traffic and CAS using AAL2, where CAS is carried in the same AAL2

channel as the associated bearer traffic

• Bearer traffic and CCS using AAL2, where CCS for the control of narrow-

band services is carried in a specific AAL2 channel that does not carry

bearer traffic, within the same ATM VCC as the associated bearer traffic.

The V5.2 Protocol Primary Rate Access (PRA) Enhancement provides ISDN

PRA service capable of carrying voice and data traffic, while also maximizing

bandwidth. The PRA enhancement increases the number of channels to a

single D-channel and 30 B-channels, and enables a PBX to be connected to

an IAD via a PRA port. The PSAX system supports a maximum of 100 PRA

ports. DSP resources may be reduced depending on the number of PRA con-

figured ports.

The V5.2 protocol supports ATM VCCs using AAL2 connections for Loop

Emulation Service (LES) in support of ISDN PRA (PRA only) with Emulated

Loop Control Protocol (ELCP). Traffic from a given ISDN PRA interface is car-

ried as a full or fractional ISDN PRA channel with separate AAL2 channels

for each B-channel and the D-channel.

This feature is supported on all PSAX systems with redundant CPUn mod-

ules. The V5.2 application can be configured on the 21-Port High Density E1

Multiservice module. The DSP2D module must be present and configured for

the V5.2 application.

Voice Processing

The DSP2C/D/E modules can process voice traffic on selected DS0 circuits

within the DS1 connections of the PSAX system. The DSP2C/D/E modules

support AAL2 SPVC connections and PVC multiplexing for reduced call

latency. It can also protect facsimile transmissions by automatically turningoff voice processing and echo cancellation on any channel when it detects a

modem tone.


detailing the nine AlgoSets (algorithm sets) and the type of voice compres-


Echo Cancellation

Near-end echo is caused by the transmitted voice signal on a 2-wire sub-

scriber loop being reflected back to the telephone receiver. It sounds like you

are talking to yourself. An echo canceller cancels the echo by sending the sig-

nal back to the receiver at the same amplitude but 180 degrees out of phasewith the transmitted signal.


detailing the seven AlgoSets (algorithm sets) and the type of voice compres-





3-70 255-700-447


Wireless Mobile Voice Backhaul

In a wireless TDMA system, using an HDLC passthrough interface over AAL5

for backhauling between the BS and the MSC provides cost benefits over a

TDM-based backhauling system currently in use. The PacketPipe AAL5-to-

AAL2 Wireless Trunking feature addresses this need.

This feature supports packet-switched wireless backhaul networks for inter-

connecting Lucent MSCs and Series II base stations using the Lucent propri-

etary packet pipe protocol over land lines. This protocol performs encapsula-

tion within ATM AAL2 for various cell site sizes.

The DSP2E module is a high-speed, multifunction digital signal processing

module that performs conventional voice compression, as well as AAL5-to-

AAL2 conversions. These capabilities make it ideal in wireless backhaul appli-

cations between base stations and Mobile Switching Centers (MSCs). The

module is particularly suited to environments where Lucent’s proprietary

HDLC-based PacketPipe is used combined with analog voice traffic.

The DSP2F module is a high-speed, digital signal processing module special-ized to do AAL2-to-AAL5 conversions. These capabilities make it ideal in

wireless backhaul applications at the MSC end in environments where

Lucent’s proprietary HDLC-based PacketPipe is used.

Assuming the traffic arriving at the PSAX system in the MSC has a mix of

analog voice and PacketPipe, from, for example, a remote PSAX system with

DSP2E modules, the analog voice can be handled in a DSP2D module, while

the PacketPipe traffic can use the DSP2F module.

Figure 3-20 shows the application implemented on a VBR-to-ATM connec-

tion over the HDLC interface with SAR type AAL2 standard. The SAR type

AAL5-to-AAL2 conversion is done on the DSP2E/F Voice Server module. The

SAR type AAL1-to-AAL2 is done on the DSP2D module.



255-700-447 3-71



DSP features on wireless applications are supported on these modules:

The following PSAX modules support the Wireless Mobile Voice feature:


• 1-Port Channelized STS-1e, T1 Format


See the description for “HDLC Passthrough Bit Inversion” on page 3-11 for a

list of modules supporting HDLC Passthrough Interface.

Virtual Routing

Another key differentiator using the Route Server module, or Enhanced

Router module in Multi-VPN mode, is the virtual router aspect of the module

(see Figure 3-21). The virtual routing capability arises from its ability to form

groupings of IP interfaces that can combine to act as separate IP networks rel-ative to some other grouping of IP interfaces on the same device. An IP inter-

face may be defined in a variety of ways, depending upon physical interface

type. Each grouping of IP interfaces that belongs to a user will behave as the

interfaces belonging to a standard IP router. The IP addresses assigned to the

IP interfaces (as well as the underlying IP traffic through each module) may

have overlapping address space without the concern of crosstalk from one

VPN to the next.

Figure 3-20. PacketPipe AAL5-to-AAL2 Wireless Trunking from Cell Site to MSCfor Mobile Voice

HDLCAAL5

A

D S P 2 E

C E

A T M

PSAX 1000 Cell Sites

D S P 2 F

A T M

PSAX 4500 in MSC

CO5ESS

AAL2 TrunksBackhauled via Land Lines

Cellular Data/Voicein Same Packet

B

E F

Pure Voice

D S P 2 D

S T S - 1 e

CES

D

H

A

B

D

E

F

H

TDM Voice/AAL1

48 Channels TDM/AAL2

384 Channels TDM/AAL1

Data/AAL5

168 Channels PacketPipeBit Inverted HDLC/AAL2

672 Channels PacketPipe/AAL5

C

G

C 384 Channels AAL2 G 672 Channels/AAL2




3-72 255-700-447


The module supports IP over ATM virtual routing in conjunction with the

other PSAX I/O modules. You can configure a virtual router at the module to

communicate with the management router at the CPUn module. As the

default gateway for the CPUn module, the module can handle all the in-band

management traffic.

Virtual router concepts, network interface assignment, and the relationship

between the existing I/O modules and the Enhanced Router module are

shown in Figure 3-22.

Figure 3-21. Virtual Router Concept

Figure 3-22. Enhanced Router and Example Configuration

Enterprise 2/ Service Provider 2



Ingress/EgressIP Traffic

Ingress/EgressATM Traffic

Edge Device

ROUTING

ROUTING

ROUTING

Each Enterprise/Service Provideroccupies its ownvirtual router space.

The Enterprise/Service Providerconsist of one or morephysical connections.

Interfaces are assigned throughconfiguration mechanismsand may be logical orphysical entities.

ATM Network

P

O

W

E

R

STRATUM

CPU

ATMFR

MODULE

ER

192.001.004.001

255.255.255.000

Existing In-Band Management

ATM Connections Partitionedinto Interfaces

An IP interface can beassigned a VC thatcorresponds to anyATM class of service.

FR Connections Partitionedinto Interfaces

145.123.215.001

255.255.000.000

145.123.215.001255.255.000.000

VirtualRouter#2 145.122.215.001

255.255.000.000

145.121.215.001255.255.000.000

VirtualRouter#1

192.001.002.001255.255.255.000

192.001.003.001255.255.255.000

192.001.001.001255.255.255.000

GoldSilverBronze

192.001.005.001255.255.255.000

Existing

In-BandManagement

Console



255-700-447 3-73



Secure Telephone Unit Third Generation (STU-III) Secure Mode

This feature permits the DSP2D and DSP2E Voice Server modules to detect

the transition of a voice call from 8 kbps or 32 kbps mode to a STU-III secure

mode and to transmit the subsequent data stream in a compressed 32 kbps

rate. The feature then detects the end of the STU-III secure mode and reverts

to the previous voice mode. The STU-III secure mode option is supported on

CE-to-ATM PVC and CE-to-SPVC AAL2 connections only. The DSP2D and

DSP2E Voice Server modules must be set to a DSP mode of AlgoSet 6 in order

to use this feature.

Voice Path Assurance

In a circuit switched voice network, a test to verify continuity of the voice

channel can be made prior to connecting a voice call. This continuity test is

requested during the call establishment phase of a connection using SS7 sig-

naling. Voice circuit switches have been designed to recognize and respond to

requests for a continuity test and to take appropriate action when a failure

occurs. With the introduction of ATM trunking technology between circuit

switches, the ATM elements need to support the circuit switches with respect

to continuity testing (see Figure 3-23).

The Voice Path Assurance (VPA) feature supports voice quality testing over a

packet network for connections used in voice switched tandem networks.

The SS7 continuity test capability is implemented in the DSP2D voice server

for CE-to-CE (AlgoSet 5) , CE-to-AAL1 (AlgoSet 5), and CE-to-AAL2

(AlgoSet 6 only) connections and in the DSP2E voice server for CE-to-AAL2(AlgoSet 6 only) connections. Non-multiplexed AAL2 connections are cur-

rently not supported.

Figure 3-23. End-to-End Continuity Check

Voice Gateway Voice Gateway







Chapter 3 System FeaturesSystem Security

3-76 255-700-447


Maintenance Testing on DS1 Interfaces

The Maintenance Tests feature provides the capability to perform out-of-ser-

vice maintenance testing on full-rate DS1 interfaces (E1 interface support

will be added in phase 2). Capabilities of this feature include the following:

• Generating loopback codes to activate and deactivate line, payload, andfacility loop codes

• Performing bit error rate tests (BERT) using a test pattern (only a finite

number of patterns can be used)

Once the specific facility has been looped, the BER testing is typically used to

qualify the facility before assigning customer traffic, and to perform mainte-

nance testing for troubleshooting sectionalized spans. Because in some cases

customer CSU/DSU equipment might be located downstream at the cus-

tomer premises from the PSAX system, maintenance testing also requires the

ability of the PSAX module’s port in the PSAX system to ignore any facility

loop codes that are received and to simply pass them along. BERT synchroni-

zation status and error counter fields are displayed or can be retrieved via

MIB variables. The following patterns are supported:

• All-1s

• All-0s

• OneIn8

• ThreeIn24

• QRSSnn (where nn=11,15, 20, or 23)

• UserConfigurednByte (where n =1, 2, 3, or 4)

The BER testing can be run as a short-term test for troubleshooting the facil-

ity or as a test running continuously for 24 to 48 hours.

Reduction in Post-Dial Delay

Event handling processes within the PSAX system are designed so that the

amount of time needed to set up a call for an SVC connection is now 30 msec

or less.

System Security

RADIUS Server Authentication for PSAX System Access

The RADIUS Support for Console/Telnet Access feature provides a conve-

nient method for storing centralized user account administration data formultiple PSAX systems. The RADIUS servers can be configured to store

authentication information for many PSAX systems in a large network. The

PSAX system functions as a network access server (NAS) client of the

RADIUS server. The RADIUS server authenticates the PSAX system user

name using the console or telnet methods via a RADIUS protocol. On the



255-700-447 3-77


Chapter 3 System FeaturesSystem Security

PSAX system User Options window, users can set parameters for user name

authentication on the primary and the secondary RADIUS servers. Users

must also set up user names and other parameters on the RADIUS servers.

The PSAX system supports three security levels:

• Read-onlyUsers with this lowest level of access are limited to viewing PSAX system

configurations only, and changing the password for read-only users on the

User Options window.

• Read-write

Users with this level of access can view and modify PSAX system configura-

tions, and change the password for read-write users on the User Options

window.

• Superuser

Users with this highest level of access can view and modify PSAX system

configurations, and change the password for superusers on the User

Options window. They also can configure the parameters for the RADIUS

servers on the User Options window. If a superuser is connected to the

PSAX system via the CONSOLE port on the CPU x module, the superuser

can also change the SNMP community string fields on the User Options

window.

The diagram in Figure 3-24 shows an overview of the PSAX system access

authentication process through the use of redundant RADIUS servers.

Figure 3-24. PSAX System Access Authentication via RADIUS Servers

PrimaryRADIUSServer

SecondaryRADIUSServer

(for redundancy)

Authentication of usernames and passwords

PSAX System PSAX System

Each PSAX system stores

the primary and secondary RADIUS server secret,IP address, and other parameters.

RADIUS servers storeusernames, passwords,

the secret (encryption key),and the PSAX systemIP address for each

PSAX system it supports.

MultiplePSAX Systems



Chapter 3 System FeaturesPSAX Module Features

3-78 255-700-447


ATM Security on Interfaces and Connections

The ATM Security feature protects ATM traffic by encrypting the ATM con-

trol plane, providing integrity and confidentiality security services to signal-

ing messages or routing packets. It also provides a mechanism for signaling

that can provide strong cryptographic data integrity with replay/reorderingprotection. ATM control plane entities are able to verify the source and con-

tents of a signaling message before resources are allocated for the requests.

This function can protect the network from certain security threats. The

PSAX system supports control plane authentication and integrity security

service.

On the PSAX system, users can configure ATM security integrity and confi-

dentiality service for ATM UNI and ATM PNNI interfaces. For ATM PNNI,

security agents are configured both at the PNNI node level and at the inter-

face level for signaling and routing PVCs.

The ATM Security feature is supported on all PSAX Multiservice Media Gate-

way systems and on PSAX I/O modules that support ATM UNI 3.0, 3.1, and4.0 and ATM PNNI 1.0 interfaces

The ATM Security feature is available only to users in certain countries. Con-

tact your Lucent Technologies sales representative to find out whether your

country is eligible to use the ATM Security feature.

PSAX Module Features

For descriptions of the I/O and server modules available for use in the

PacketStar ® PSAX Multiservice Media Gateways, see Appendix D.




255-700-447 4-1

4 Using VT100 Terminal Emulation


VT100 terminal emulation is used in configuring and managing the

PSAX 2300 system from the serial interface port labeled CONSOLE on the

faceplate of the CPUn module. The PSAX 2300 system software supports the

following terminal emulation software:

• Microsoft Windows 98 HyperTerminal terminal emulator

• Microsoft Windows NT HyperTerminal terminal emulator

• Microsoft Windows 2000 HyperTerminal terminal emulator

Use the shielded serial cable (with RJ-12 to RJ-12 plugs) supplied with sys-

tem to connect the Multiservice Media Gateway system to the PC.

Setting Up The Windows HyperTerminal Emulator

To configure VT100 terminal emulation using a Windows HyperTerminal

emulator, perform the following procedure.

Begin

1 Do one of the following, depending on your operating system (see

Table 4-1):

Table 4-1. Starting the Hyperterminal Program

To launch Hyperterminal usingthis operating system...

do this...

Windows 2000 Select Start > Programs > Accessories

> Communications > Hyperterminal

Windows 98 or NT Select Start > Programs > Accessories

> Hyperterminal



Chapter 4 Using VT100 Terminal EmulationSetting Up The Windows HyperTerminal Emulator

4-2 255-700-447


The Connection Description window is displayed (see Figure 4-1).

2 In the Name field, enter a name for the new connection.

3 In the Icon field, click an icon symbol to identify this new connection.

4 Click OK.

The Connect To window is displayed (see Figure 4-2).

5 In the Connect using field, select COM1.

6 Click OK.

Figure 4-1. Connection Description Window

Figure 4-2. Connect To Window



255-700-447 4-3


Chapter 4 Using VT100 Terminal EmulationSetting Up The Windows HyperTerminal Emulator

The COM1 Properties window is displayed (see Figure 4-3).

7 Enter the appropriate values for the fields on this window according to

the information provided in Table 4-2.

8 Click OK.

The named HyperTerminal window is displayed.

9 Press Enter.

The PacketStar PSAX Logon window is displayed (see Figure 4-4). Refer

to Chapter 5 for details on logging into the system.

Figure 4-3. COM1 Properties Window

Table 4-2. Windows HyperTerminal Settings

Option Setting

Bits per second: 9600 baud

Data bits: 8

Parity: NoneStop bits: 1

Flow control: None



Chapter 4 Using VT100 Terminal EmulationConnecting a Dialup Modem to the Chassis

4-4 255-700-447


End

Connecting a Dialup Modem to the Chassis

The following procedure requires the following items to dial-in to the

PSAX 2300 system:

• External 9600-baud dialup modem• Phone line and telephone number

• Computer (or laptop) with a dialup modem and terminal emulator package

at the local site

• Workstation with a dialup modem and terminal emulator package at the

remote site

Note: To perform this operation, the system must have power applied to

it and be operational.

Perform the following procedure to setup and connect the PSAX 2300 system

to a dialup modem.

Begin

@@IG@@ Connecting a Dialup Modem to the system

1 At the local site, install the modem near the system:

a Connect the computer to the serial port on the modem.

b Connect the phone line to the phone jack.

c Plug the power adapter into the modem and power source.

d Set the following interface parameters on the modem:

Figure 4-4. PSAX 2300 Multiservice Media Gateway System Logon Window



255-700-447 4-5



DTR on, DCD on, CTS on, 8-bit character length, 9600 baud, no par-

ity, and no echo.

e Disconnect the computer from the modem.

f Connect the RJ-12-to-DB9 or RJ-12-to-DB25 adapter to the modem.

g Connect the RJ-12-to-RJ-12 cable between the modem and the CON-SOLE connector on the CPUn module.

2 At the remote site:

a Verify that the remote workstation and dialup facilities are function-

ing properly.

b Dial into the local site and verify that Press RETURN to log in...,

is displayed from the system.

3 After you complete this procedure, continue with the next section.

End




4-6 255-700-447





255-700-447 5-1

5 Site-Specific Configuration


This chapter describes how to:

• Log onto the PSAX system

• Configure the basic site-specific parameters of the PSAX 2300 system

• Configure call control resource allocations

• Enable/disable systemwide features

• Configure interface protection groups

• Configure internet protocol throttling

• Activate/deactivate traps

• Collect bulk statistics on the PSAX system to be sent to a remote statistics

server

• Use the Equipment Configuration window

• Configure the Stratum 3–4 module

• Save PSAX system configuration values and log off

Before you begin the system configuration, be sure you have completed all

the installation tasks described in the appropriate PacketStar ® PSAX 2300 Mul-

tiservice Media Gateway Installation Guide. For procedures to configure the

PSAX I/O and server modules, see the appropriate PacketStar PSAX module

user guide. All PacketStar PSAX Multiservice Media Gateway documentation

are contained on the PacketStar PSAX Multiservice Media Gateway Product

Information Library CD-ROM.

Logging onto the System

Before beginning the following procedure, be sure that your cabling on the

CPUn module is connected properly (see the PacketStar ® PSAX 2300 Multiser-

vice Media Gateway Installation Guide).

The PSAX 2300 system is designed for continuous operation after power is

applied. Telnet sessions are supported on the Ethernet interface. Telnet ses-

sions on the Ethernet interface and the console serial interface both support

VT100 terminal emulation. See Chapter 4 for information on configuring

VT100 terminal emulation on a PC.

You can log onto the PSAX system using either of two methods for authenti-

cating user access:

• Using the PSAX system-defined usernames (see the following procedure)

• Using the RADIUS server-defined usernames that you have already set up

on a RADIUS server on your network (see “Setting Up RADIUS Server

Access Authentication for the PSAX System” on page 5-6 for details)



Chapter 5 Site-Specific ConfigurationLogging onto the System

5-2 255-700-447


To log onto the PSAX 2300 system, perform the following procedure.

Begin

1 Configure your VT100 terminal emulator (see Chapter 4 for details).

2 To start the console session, press Enter.

The PSAX 2300 Logon window is displayed (see Figure 5-1).

3 Enter the username and password on this window according to the infor-

mation provided in Table 5-1.

The Console Interface Main Menu window is displayed (see Figure 5-2).

End

Figure 5-1. PSAX 2300 Multiservice Media Gateway System Logon Window



255-700-447 5-3



Table 5-1. Field Descriptions for the PSAX System Logon Window


Username Default: N/A

Range: N/A

Format: Alphanu-

meric

Specifies the user name for logging onto the PSAX sys-

tem, which provides three levels of access to the sys-

tem. User names you use to log on to the PSAX system

fall into two categories:• PSAX system-defined user names. When you are

not using a RADIUS server to authenticate logon,

that is, you are using the PSAX system to authenti-

cate logon, you must enter root, readwrite, or

readonly (not case sensitive) as the user name.

• RADIUS-defined user names. If you are authenticat-

ing your logon by using a RADIUS server, enter a

user name and its associated password that has

already been set up and is stored on the RADIUS

server. Setting up a dictionary containing user names

and passwords on a RADIUS server is a separate task

performed by your system or network administrator.root Indicates the user name with the highest level of

access, also known as a “super user.” If you log on with

the user name root, you can do the following:

• Modify and view the PSAX system configuration

• Configure the user access authentication method on

the User Options window.

• Configure the communication parameters for the

primary and secondary (backup) RADIUS servers on

the User Options window.

• Modify the passwords for the user names root,

readwrite, and readonly on the User Options win-

dow.• Access and modify the all five SNMP authentication

options on the SNMP Agent System-Wide Configu-

ration window. You must be connected to the PSAX

system via the CONSOLE port on the CPUn module.




5-4 255-700-447


readwrite Indicates the user name with the medium level of

access. If you log on with the user name readwrite,

you can do the following:

• Modify and view the PSAX system configuration• Modify the Trap Notification Configuration option

on the SNMP Agent System-Wide Configuration

window

• Modify the password for the user name readwrite

on the User Options window

readonly Indicates the user name with the lowest level of access.

If you log on with the user name readonly, you can do

the following:

• View the PSAX system configuration

• View the Trap Notification Configuration option on

the SNMP Agent System-Wide Configuration win-

dow

• Modify the password for the user name readonly on

the User Options window

Password Default: Not

displayed

Range: N/A

Format: ASCII Char-

acters 32 - 126

Specifies the password for the user name you enter in

the Username field, as described above. The password

is not displayed as you type it. Note the following con-

siderations:

• If you are logging on with the username root (with

super user capabilities), it is recommended that you

change the default passwords (case sensitive) on the

User Options window for all three PSAX-defined

user names—root, readwrite, and

readonly—during your first logon session. To

change the default passwords, see “Changing the

System Password and Other User Options” on

page 5-11.

• If you are logging on with a RADIUS-defined user

name, you enter the password associated with that

user name. The RADIUS-defined user names and

passwords are stored on the RADIUS server.

• If you are logging on with a PSAX-defined user

name, you enter the correct password (case sensi-

tive) stored in the PSAX system database.

Table 5-1. Field Descriptions for the PSAX System Logon Window (Continued)




255-700-447 5-5


Chapter 5 Site-Specific ConfigurationConsole Interface Main Menu Options

Note: At the time of initial configuration, the Console Interface Main

Menu window displays a field with a pair of opposing square

brackets in the upper right corner. This field contains the site

name, which you will enter during site-specific configuration (see

“Configuring System Identification Information” on page 5-22 for

details).

Console Interface Main Menu OptionsThe Console Interface Main Menu window includes the following options as

described in Table 5-2.

Figure 5-2. Console Interface Main Menu Window

Table 5-2. Console Interface Main Menu Options and Commands

For information on using this option... see...

Site-Specific Configuration “Configuring the System for Your Site” on

page 5-19.

Equipment Configuration “Using the Equipment Configuration Window”

on page 5-71.

Connection Configuration PacketStar ® PSAX System Connections Provisioning

Guide.

Software Version Configuration Chapter 7, “Upgrading System Software and

Firmware.”

Trap Log Display PacketStar ® PSAX Simple Network Management Pro-

tocol (SNMP) Trap Reference Guide.



Chapter 5 Site-Specific ConfigurationSetting Up RADIUS Server Access Authentication for the PSAX System

5-6 255-700-447


Setting Up RADIUS Server Access Authentication for thePSAX System

If you plan to use a RADIUS server for authenticating user access to one or

more PSAX Multiservice Media Gateway systems, you need to complete two

main tasks:

1. Setting up a separate RADIUS server on your network first

2. Configuring the options for commuicating with the RADIUS server on

the PSAX system (User Options window)

Overview of Tasks for Setting Up a RADIUS Server

You can access the PSAX system by authenticating logon via a RADIUS

server, or you can log onto the PSAX system without RADIUS server authen-

tication. The PSAX system functions as a network access server (NAS) client.

If you intend to use a RADIUS server with one or more PSAX system clients,

you must set up attributes on the RADIUS server before setting parameters

on the User Options window for each PSAX system client to communicate

with the RADIUS server. The following procedure provides an overview of

tasks for setting up the RADIUS server to work with multiple PSAX system

clients. For specific details on the RADIUS protocol, see the IETF RFC 2865

specification.

Begin

1 For each PSAX system client, add the IP address and the unique client

secret (encryption key).

2 For vendor-specific attributes:

a Set the vendor ID to 1751, which is assigned to the Lucent Technolo-

gies’ PacketStar PSAX product line.

User Options “Setting Up RADIUS Server Access Authentica-

tion for the PSAX System” on page 5-6 and

“Changing the System Password and Other User

Options” on page 5-11.Diagnostics Chapter 5, “Using System Diagnostics.”

Remote Database Operation Chapter 8, “Backing Up and Restoring Database

Configuration Files.”

Save Configuration “Saving the Equipment Configuration Values

and Logging Off” on page 5-84.

Leave Console Interface “Saving the Equipment Configuration Values

and Logging Off” on page 5-84.

Table 5-2. Console Interface Main Menu Options and Commands (Continued)

For information on using this option... see...



255-700-447 5-7



b Set the vendor type to 1, which is defined as PSAX-security-level.

c Set the PSAX-security-level attributes to 0 (super user), 1 (read-

write), and 2 (readonly)

3 Add each user name and specify the appropriate PSAX-security-level

attribute (0, 1, or 2) for each user name.

4 For each user name, add a password that contains a minimum of 8 char-

acters.

5 If you are using a secondary (redundant) RADIUS server, ensure that

these attributes are installed on the secondary server.

End

Configuring RADIUS Server Options on the PSAX System

When accessing the PSAX system, you log onto the system with one of the

PSAX-defined usernames, or a username defined on a remote RADIUS

server. The PSAX-defined usernames, which cannot be changed, and theiraccess permissions are as follows:

• root—This username provides ”super user” access including read/write

and administrative permissions.

• readwrite—This username provides read/write permission.

• readonly—This username provides read-only permission.

You must set up or change the RADIUS server options through the CONSOLE

port (serial port) on the CPUn module, because you cannot change the

RADIUS server options remotely through a network.

To set up the RADIUS server options, perform the following procedure.

Begin

1 On the Console Interface Main Menu window, select the User Options

command.

The User Options window is displayed . Initially this window displays the

value LOCAL_ONLY in the Authentication Mode field (see Figure 5-3);

therefore, the other fields for setting up the RADIUS server options are

not displayed until you select either the value HYBRID or

RADIUS_ONLY in this field (see Figure 5-4).

2 Change the values in the fields according to the information provided in

Table 5-4.

3 Select the Apply User Configuration command. The commands onthis window are described in Table 5-3.

4 To permanently save these values, press Ctrl+G to return to the Console

Interface Main Menu window.

5 On the Console Interface Main Menu window, select the Save Configu-

ration command to store the values in the PSAX system database.

End




5-8 255-700-447


Figure 5-3. User Options Window—Logged on as Username Root

Figure 5-4. User Options Window—Authentication Mode Hybrid Selected

Table 5-3. Commands for the User Options Window

Command Function

Apply User Configuration Applies the configuration field values you entered.



255-700-447 5-9



Reset to System Defaults Resets the values in the fields to the system default values.

Go Back to Main Menu Redisplays the Console Interface Main Menu window.

Table 5-3. Commands for the User Options Window (Continued)

Command Function

Table 5-4. Field Descriptions for the User Options Window (RADIUS Server Fields)

Field Names Field Values Description

RADIUS Server Authentication Mode Panel

Authentication

Mode

Default: LOCAL_ONLY

Range: N/A

Format: Predefined

alphanumeric

Specifies the method that the PSAX system uses to

authenticate the username and password.

Note: This field is displayed only if you logged

onto the PSAX system with the username root.

LOCAL_ONLY Indicates that the PSAX system will not obtain

authentication of the username and password

from the RADIUS server.

RADIUS_ONLY Indicates that the PSAX system will obtain authen-

tication of the username and password from either

the primary RADIUS server or from the secondary

RADIUS server, if you set up the parameters on

this window for a secondary server.

HYBRID Indicates that the PSAX system will obtain authen-

tication of the username and password from either

the primary RADIUS server or from the secondary

RADIUS server (if you set up the parameters for

the secondary server on this window), or from the

PSAX system. If either the primary or secondary

RADIUS server is not available, you can log onto

the PSAX system by using one of the PSAX sys-tem-defined usernames: root, readwrite, or rea-

donly.

Server IP Address Default: 000.000.000.00

0

Range: N/A

Format: Numeric (valid

dotted quad

Specifies the IP address for the primary and the

secondary RADIUS servers. Enter values for the

primary server and for the secondary server if you

want redundant authentication capabilities.

Note: This field is displayed only if you selected

the value RADIUS_ONLY or HYBRID in the

Authentication Mode field.

Server Port Number Default: 1812

Range: N/A

Format: Numeric (4 dig-

its)

Specifies the port numbers for the primary and the

secondary RADIUS servers. Normally, you should

use the default value 1812; however, you canchange this port number if needed







5-10 255-700-447


Server Max Retry Default: 0

Range: 0–9

Format: Numeric

Specifies the number of times the PSAX system

tries to obtain logon authentication from the

RADIUS server. Enter values for the primary

server and for the secondary server if you wantredundant authentication capabilities. If all

authentication attempts specified by the value in

this field fail, an SNMP trap message is displayed

on the PSAX Logon window, and the person who

is trying to log onto the PSAX system is denied

access.




Server Max Time-

out

Default: 10

Range: 0–99

Format: Numeric (sec-onds)

Specifies the length of time in seconds between

authentication attempts by the RADIUS server.

Enter values for the primary server and for the sec-ondary server if you want redundant authentica-

tion capabilities.




Primary RADIUS

Server Secret

Default: None

Range: 4–30

Format: Alphanumeric

(case sensitive)

Specifies the secret (encryption key) that the pri-

mary RADIUS server uses to encrypt the user’s

password. When you enter a case-sensitive text

string in this field, it is not displayed on the win-

dow. The PSAX system does not do any checking

of the text string. This secret must also be set up on

the primary RADIUS server along with the PSAX

system IP address and the usernames and pass-

words of the users who will access the PSAX sys-

tem. When the user logs onto the PSAX system, it

then sends the username and encrypted password

to the RADIUS server for authentication.




Secondary RADIUS

Server Secret

Default: None

Range: 4–30


(case sensitive)

Specifies the secret (encryption key) that the sec-

ondary RADIUS server uses to encrypt the user’s

password. Enter a case-sensitive text string for the

secondary server if you want redundant authenti-

cation capabilities. This secret must also be set upon the secondary RADIUS server along with the

PSAX system IP address and the usernames and

passwords of the users who will access the PSAX

system.




Table 5-4. Field Descriptions for the User Options Window (RADIUS Server Fields) (Continued)




255-700-447 5-11


Chapter 5 Site-Specific ConfigurationChanging the System Password and Other User Options

Changing the System Password and Other User Options

The following functions are available on the User Options window:

• Changing the system password for the PSAX system usernames• Setting up alternate navigation keys

• Configuring settings for the bell, timeout length, and trap display

• For users logging onto the PSAX system with the username root, configur-

ing the logon authentication mode (see “Setting Up RADIUS Server Access

Authentication for the PSAX System”)

Changing the System Password

When accessing the PSAX system, you log in with one of the PSAX-defined

usernames, or a username defined on a remote RADIUS server. The PSAX-

defined usernames, which cannot be changed, and their access permissions

are as follows (details of permissions are provided in Table 5-5):

• root—This username provides ”super user” access including read/write

and administrative permissions.

• readwrite—This username provides read/write permission.

• readonly—This username provides read-only permission.

! CAUTION:If you are using the console session for the first time on this PSAX sys-tem, you are urged to change the initial, default passwords for the threeusernames, root, readwrite, and readonly (see Table 5-7 for guidelines)during this session.

You can change the password for a username at any time, as needed. How-

ever, you must make this change through the CONSOLE port (serial port) on

the CPUn module, because you cannot access user options remotely through

a network.

To change the system password, perform the following procedure.

Begin


command.

The User Options window is displayed. Depending on which usernameyou logged on with, this window is displayed differently as follows:

• Figure 5-3 shows the window that is displayed if you logged on with

username root.


username readwrite.


username readonly.




5-12 255-700-447


The three levels of permissions for changing user options on this window

are described in Table 5-5.

2 To change the password for the username, select the Change Password

For username field, where username is one of the PSAX-defined user-

names listed in Table 5-5.

a Type the current password, or if you are currently configuring your

system for the first time, type the default password that is specified in

the PSAX system software.

b Type a new password using the rules provided in Table 5-7.

c Re-type the new password for verification. The Change Password For

username field changes to Press RETURN to Apply New Passwds.

d Select the Press RETURN to Apply New Passwd command.




ration command to store the values in the PSAX system database. The

new values will take effect after you reboot the PSAX system.

Note: You must reboot your PSAX system for the changed password to

take effect. For information on rebooting system components,

see Chapter 11.

End

Table 5-5. Permissions for PSAX-defined Usernames

If you logged onwith username...

you can change the following fields on the User Optionswindow:

root Alternate Navigation Keys, Bell, Trap Display, TimeoutLength, and the Passwords for root, readwrite, and rea-

donly. In addition, you can change the Authentication

Mode field, and the associated fields for the primary and

secondary RADIUS servers. See the section “Setting Up

RADIUS Server Access Authentication for the PSAX Sys-

tem” for information and procedures on configuring

parameters for the RADIUS servers.

readwrite Alternate Navigation Keys, Bell, Trap Display, Timeout

Length, and the Password for readwrite fields.

readonly Alternate Navigation Keys, Bell, Trap Display, Timeout

Length, and the Password for readonly fields.



255-700-447 5-13



Figure 5-5. User Options Window—Logged on as Username Root

Figure 5-6. User Options Window—Logged on as Username Readwrite




5-14 255-700-447


Figure 5-7. User Options Window—Logged on as Username Readonly

Table 5-6. Commands for the User Options Window

Command Function

Apply User Configuration Applies the configuration field values you entered.

Reset to System Defaults Resets the values in the fields to the system default values.


Table 5-7. Field Descriptions for the User Options Window (Password and MiscellaneousUser Options Fields)


Miscellaneous User Options Panel

Alternate Naviga-

tion Keys Up,

Down, Left, Right

Default: Up: K, Down:

J, Left: H, Right: L

Range: N/A

Format: Predefined

alphabetic

Specifies alternate navigation keys for cursor

movement. If you want to use keyboard short-

cuts instead of the cursor positioning (arrow)

keys for navigating the windows of the PSAX

console system, you can change the keyboard

navigation keys from the default values.

Bell Default: Enabled

Range: N/A

Format: Predefined

alphanumeric

Specifies whether the system audio warning bell

is enabled or disabled. If the warning bell isenabled, it sounds ten seconds before the timeout

period expires.

Enabled Enables the warning bell.

Disabled Disables the warning bell.



255-700-447 5-15



Trap Display Default: Enabled

Range: N/A

Format: Predefinedalphanumeric

Specifies whether or not you see the trap message

displayed at the bottom of the window. All trap

messages generated by the system are sent to thetrap message log whether or not you see them at

the bottom of the window. You can view these

messages on the Trap Log Display window.

Enabled Enables the display of trap messages after you

execute a command or the PSAX system per-

forms a function.

Disabled Disables the display of trap messages after you

execute a command or the PSAX system per-

forms a function.

Timeout Length Default: 10 minutes

Range: N/A

Format: Predefined

alphanumeric

Specifies the period of time that the session will

remain active after the last detected keystroke.

Ten seconds before the session is automaticallyterminated at the end of the session period, you

hear three audio alerts from the warning bell. If

you do not perform a keystroke during this ten-

second period, the system will log off whether

you have saved your configuration or not.

Note: Lucent recommends that you select a rela-

tively short timeout period (for example, 1

minute) to help safeguard the PSAX system from

unauthorized users as well as potential lockout

from a Telnet session.

1 minute Indicates that the session will remain active for 1

minute after the last detected keystroke.5 minutes Indicates that the session will remain active for 5

minutes after the last detected keystroke.

10 minutes Indicates that the session will remain active for

10 minutes after the last detected keystroke.







45 minutes Indicates that the session will remain active for45 minutes after the last detected keystroke.

1 hour Indicates that the session will remain active for 1

hour after the last detected keystroke.

Disabled Indicates that the session will remain active until

you log off the PSAX system.

Table 5-7. Field Descriptions for the User Options Window (Password and MiscellaneousUser Options Fields) (Continued)






255-700-447 5-17



Table 5-8. ASCII Characters Permitted for Use in Passwords

Dec Char Description Dec Char Description

32 space * 80 P Uppercase P

33 ! Exclamation mark 81 Q Uppercase Q

34 " Quotation mark 82 R Uppercase R

35 # Cross hatch (number sign) 83 S Uppercase S

36 $ Dollar sign 84 T Uppercase T

37 % Percent sign 85 U Uppercase U

38 & Ampersand 86 V Uppercase V

39 ‘ Closing single quote (apostrophe) 87 W Uppercase W

40 ( Opening parentheses 88 X Uppercase X

41 ) Closing parentheses 89 Y Uppercase Y

42 * Asterisk (star, multiply) 90 Z Uppercase Z

43 + Plus 91 [ Opening square bracket

44 , Comma 92 \ Reverse slant (Backslash)

45 - Hyphen, dash, minus 93 ] Closing square bracket

46 . Period 94 ^ Caret (Circumflex)

47 / Slant (forward slash, divide) 95 _ Underscore

48 0 Zero 96 ‘ Opening single quote

49 1 One 97 a Lowercase a

50 2 Two 98 b Lowercase b

51 3 Three 99 c Lowercase c

52 4 Four 100 d Lowercase d

53 5 Five 101 e Lowercase e54 6 Six 102 f Lowercase f

55 7 Seven 103 g Lowercase g

56 8 Eight 104 h Lowercase h

57 9 Nine 105 i Lowercase i

58 : Colon 106 j Lowercase j

59 ; Semicolon 107 k Lowercase k

60 < Less than sign 108 l Lowercase l

61 = Equals sign 109 m Lowercase m

62 > Greater than sign 110 n Lowercase n

63 ? Question mark 111 o Lowercase o

64 @ At-sign 112 p Lowercase p

65 A Uppercase A 113 q Lowercase q

66 B Uppercase B 114 r Lowercase r

67 C Uppercase C 115 s Lowercase s

68 D Uppercase D 116 t Lowercase t




5-18 255-700-447


Changing Other User Options

You can change the following miscellaneous user options:

• Alternate navigation keys

• Trap display

• Timeout length for the current console session

• Bell

To change the miscellaneous user options, perform the following procedure:

Begin


command.

Depending on which username you used to log onto the system, the User

Options window is displayed in one of three different versions (see

Figure 5-3, Figure 5-4, and Figure 5-7).

2 Change the values in the Alternate Navigation, Bell, Trap Display, and

Timeout Length fields as provided in Table 5-4.

3 Select the Apply User Configuration command. The commands onthis window are described in Table 5-3.




ration command to store the values in the PSAX system database.

End

69 E Uppercase E 117 u Lowercase u

70 F Uppercase F 118 v Lowercase v

71 G Uppercase G 119 w Lowercase w72 H Uppercase H 120 x Lowercase x

73 I Uppercase I 121 y Lowercase y

74 J Uppercase J 122 z Lowercase z

75 K Uppercase K 123 { Opening curly brace

76 L Uppercase L 124 | Vertical line

77 M Uppercase M 125 } Closing curly brace

78 N Uppercase N 126 ~ Tilde (approximate)

79 O Uppercase O

* The space character is valid only for PSAX passwords for the “root”, “readwrite”, and “readonly”

users. The space character cannot be used in SNMP community strings, or in SNMP authentica-tion or privacy passwords.

Table 5-8. ASCII Characters Permitted for Use in Passwords (Continued)

Dec Char Description Dec Char Description



255-700-447 5-19


Chapter 5 Site-Specific ConfigurationConfiguring the System for Your Site

Configuring the System for Your Site

Before proceeding with your site configuration, you must first determine the

actual values you will use for the following configuration identifiers:

• Site name

• Site identifier

• Switch master IP address

• Ethernet mask address

• Gateway address

• IP addresses of remote network managers configured to receive SNMP

traps

Accessing the Site-Specific Menu Window

To access the Site-Specific Menu window on which you select the option for

the function or feature you want to configure, perform the following proce-

dure.

Begin

On the Console Interface Main Menu window, select the Site-Specific Con-

figuration command.

The Site-Specific Menu window is displayed (see Figure 5-8).

End

Figure 5-8. Site-Specific Menu Window (No System Options Configured)




5-20 255-700-447


The Site-Specific Menu window provides access to the functions that the

PSAX system uses to manage the various systemwide features.

Table 5-9. Descriptions for Site-Specific Menu Options

Menu Option Description

Note: Menu options shown between brackets [ ] are not available until the feature is Enabled by using the Feature Turn ON/OFF option on this same menu, saving the configuration, and

rebooting the chassis. After these steps are done, the menu option is available for configura-

tion. See the section,“Using the Turn On/Off Feature” for more information.

Site-Specific Configuration Accesses the Site-Specific Configuration window on

which you configure information that is unique to this

particular PSAX system, including the site ID, Ethernet IP

address, system date and time, and SNMP manager IP

addresses.

In-band Management IP Con-

figuration

Accesses the In-Band Management IP Configuration win-

dow on which you configure IP over ATM to manage

remotely distributed PSAX systems from a central site

over the data network using the current managementtools.

PNNI System-Wide Configura-

tion

Accesses the PNNI System-Wide Configuration window

on which you configure PNNI nodes, route addresses,

metrics, summary addresses, links, and neighbor peers for

the PSAX system.

Call Control Resource Alloca-

tion Configuration

Accesses the Call Control Resource Allocation Configura-

tion window on which you configure memory allocation

for call resources (SVCs and SPVCs). The PSAX system

calculates the percentage of memory allocation usage

from the combination of values you configure. This is dif-

ferent from the Transport Protocol

[GR303 System-Wide Configu-ration]

Accesses the GR-303 System-Wide Configuration windowon which you configure the GR-303 LES.

Note: To use this feature, you must first enable it by using

the Feature Turn ON/OFF option on this menu.

[V5 Interface Configuration] Accesses the V.5 protocol for configuring European LES.



ATM Trunking Configuration Accesses the ATM Trunking Local Node Configuration

window on which you configure an ATM trunking local

node, remote IWF, signaling VCC, bearer VCC, and nar-

rowband and broadband routing tables.

TAS Module System-Wide Con-

figuration

Accesses the TAS Module System-Wide Configuration

window on which you perform actions on announcement

files on the Tones and Announcements Server module

such as compression, playing, FTP, and line tests.



255-700-447 5-21



[H.248 Management and Con-

figuration]

Accesses the H.248 Management and Configuration win-

dow on which you configure the media gateway control-

ler on a CES-to-ATM AAL1 SVC. This window provides

access to MGC-to-MG communications control, conges-tion handling setup, DTMF tone duration control for the

Tones and Announcements Server module (23N28)

DTMF tone generation if installed, and access and setup to

the context and termination information. Enabling the

H.248 feature disables the CGAPI functionality for H.248

operation and adds the Go to H.248 TID Configuration

command to various virtual port configuration windows.

Refer to the PacketStar ® PSAX H.248 Media Gateway Control

User Guide for details.



DSP Resource Configuration Accesses the DSP Resource Table window on which you

can allocate DSP resources manually, or assign the firm-

ware to do so. You can also view how many of your DSP

resources are available, used, or failed in the 7 AlgoSet

and TAS CAS modes.

Note: If you want manual or automatic DSP resource

allocation, you must configure those resources at the site-

specific (system level) before configuring at the DSP2 x

module-channel level.

[IUA Layer Configuration] Accesses the ISDN Q.921 User Adaptation Layer Configu-

ration windows.

Note: To use this feature, you must first enable it by usingthe Feature Turn ON/OFF option on this menu.

Note: H.248 with PRI ISDN Network Offload Applica-

tions: By turning on this feature, the transport protocol

for ISDN is automatically set to STCP, which is required

for PRI ISDN network offload. This function is different

from selecting sctp on the H.248 Transport and Resource

window.

Feature Turn ON/OFF Accesses the Feature Turn ON/OFF window on which

you enable or disable the NAR GR-303 LES, European V.5

LES, and the H.248 Media Gateway Control options avail-

able on this menu.

Interface Protection Feature Accesses the Interface Protection Feature Configurationwindow on which you configure the switchover of a

group of interfaces from a primary to a standby connec-

tion if a failure is detected on the primary.

IP Throttling Configuration Accesses the IP Throttling Configuration window on

which you enable and disable and set parameters for this

feature.

Table 5-9. Descriptions for Site-Specific Menu Options (Continued)





5-22 255-700-447


Configuring System Identification Information

Perform the following procedure to configure the Master ATM Address and

OAM related data panel on the Site-Specific Configuration window. See the

appropriate PSAX user guide for procedures to configure the System Identifi-

cation panel and System Date, Time and Temperature panel.

Begin

Entering YourSystem MasterATM Address

1 On the Console Interface Main Menu window, select the Site-Specific

Configuration command.

The Site-Specific Menu window is displayed.

2 On the Site-Specific Menu window, select the Site-Specific Configuration

option.

The Site-Specific Configuration window is displayed (see Figure 5-9).

3 Enter the appropriate information in the Master ATM Address and OAM

related data panel of the window as required. Table 5-10 describes the

commands on the window. Table 5-12 describes the fields in the MasterATM Address and OAM related data panel as required.

Note: The system performs error checking on each field by highlighting

any field containing an incorrect value. Use the system message

displayed in the status line to help correct any errors.

End

Trap Activation Configuration Accesses the Trap Activation Table window on which you

turn on or off the display of specific minor, information,

and system response indicators in the trap log.

N to M Protection Feature Accesses the N to M Protection Feature Menu window on

which you add protection groups for PSAX protection

modules. This feature is currently supported only for the

PSAX 4500 Multiservice Media Gateway system.

SNMP Agent Accesses the SNMP Agent System-Wide Configuration

window on which you

ATM Security Agents Accesses the ATM Security Agents Table window on

which you

Bulk Statistics Configuration Accesses the Bulk Statistics Configuration window on

which you can identify a remote sever that can be used to

store bulk statistics generated by the PSAX system.




Table 5-9. Descriptions for Site-Specific Menu Options (Continued)




255-700-447 5-23



Figure 5-9. Site-Specific Configuration Window

Table 5-10. Commands for the Site-Specific Configuration Window

Command Function

Configure TCP Server Displays the TCP Server Configuration window.

Apply Site-Specific Configuration Applies the values you entered on this window.

Reset Site-Specific Display Sets the values in this window to the last saved

(applied) set of values.

Go Back to Site-Specific Menu Redisplays the Site-Specific Menu window.

Table 5-11. Field Descriptions for the Master ATM Address and OAM Related Data Panel on theSite-Specific Configuration Window


Master Node Addr Default: 0000.0000.

0000.0000.0000.

0000.0000.0000.

0000.0000

Range: N/A

Format: Hexadecimal

Specifies the master node address where the

SNMP traps will be sent (20 octets). The address

must start with 39, 45, or 47, depending on your

world region.




5-24 255-700-447


Rules for Configuring IP Addresses

Use the following rules when configuring the CPU IP address, the switch IP

address, and the in-band IP address on the Site-Specific Configuration win-

dow:

1. The CPU IP address is always necessary, and you must not leave it as

zero. However, you can enter the switch IP address in a redundant sys-

tem.

2. The CPU IP and switch IP addresses cannot be the same.

3. The CPU IP and switch IP addresses cannot be on the same subnet as the

in-band IP address.

4. The switch IP and in-band IP management addresses may each be zero. If

the CPU IP address (or switch IP address) and the in-band management

IP address are in the same class, their masks must be the same.

Note: If the CPU IP address is zero and the ssid file on the CPUn mod-

ule is corrupted, the system cannot access the Ethernet.

Address Type Default: Nsap

Range: N/A

Format: Predefined

Specifies the type of address used for the master

node ATM address.

Nsap Indicates that the master node address is a net-

work service access point-type address.

E164 Indicates that the master node address

E164nsap Indicates that the master node address

Loopback Location

ID

Default: FFFF.FFFF.

FFFF.FFFF.FFFF.

FFFF.FFFF.FFFF

Range: N/A

Format: Hexadecimal

Specifies the unique identifier of the ATM node

where the loopback is to occur (8 octets). The

loopback location ID is the location identifier of

the local PSAX system. It is used as the “source

location ID” in all the outgoing OAM loopback

cells and will be compared with the “destination

location ID” of a received OAM loopback cell todetermine whether the received OAM loopback

cell should be looped back by this PSAX sytem.

You must enter a unique value in this field to

perform OAM loopback tests. For more informa-

tion about OAM loopback tests, see Chapter 5,

“Using System Diagnostics.”

Debouncing Period

(msecs)

Default: 3000

Range: 1000–300000

Format: Numeric

(msec)

Specifies the maximum length of time that must

elapse before the PSAX system will clear OAM

AIS and RDI alarms.

Table 5-11. Field Descriptions for the Master ATM Address and OAM Related Data Panel on theSite-Specific Configuration Window (Continued)




255-700-447 5-25



5. If the CPU IP, switch IP, and in-band IP addresses are not zero, then they

must be valid IP addresses.

6. If the switch IP address is not zero, then the system will respond to the

switch IP address; otherwise, the system will respond to the the CPU IP

address on the Ethernet port.

7. The gateway IP address cannot be the same as the CPU IP and switch IPaddresses.

8. In a redundant system, both CPUn modules must have a unique CPU IP

address. They will have the same switch IP address and in-band IP

address if either address is defined. After initial setup, the IP settings can

be modified only on the active CPUn module.

Rules for Configuring IP Address Masks

1. The CPU IP address and switch IP address share the same IP mask.

2. The CPU IP address (or switch IP address) and in-band IP address masks

are independent of each other, as long as the CPU IP address (or switch IP

address) and in-band IP address are in different networks.

3. If the CPU IP address (or switch IP address) and in-band IP address are in

the same class, then their masks must be the same.

4. The CPU IP address and switch IP address must always be on a different

subnet from the in-band IP address; CPU IP and switch IP addresses can-

not be on the same subnet as the in-band IP address.

Configuring System Identification

ATM Addresses andOAM Properties

The Master ATM Address and OAM related data panel allows you to enter

and display information about the master ATM address, the loopback, and

OAM debouncing period.

Perform the following procedure to configure the loopback parameters on

modules that support loopback configuration.

Begin

1 Select the values for the fields in the Master ATM Address and OAM

related data panel as described in Table 5-12.

2 Select the Apply Site-Specific Configuration command.

3 To return to the Console Interface Main Menu window, press Ctrl+G.

End




5-26 255-700-447


Perform the following procedure to set the system identification for your site

from the Site-Specific Configuration window.

Begin

1 Enter values in the fields on the System Identification panel according to

the information provided in Table 5-13.

2 Either select the Apply Site-Specific Configuration command to save

these values now, or after you have entered data in all the fields on this

window.

End

Table 5-12. Field Descriptions for the Master ATM Address and OAM Related Data Panel on theSite-Specific Configuration Window


Master Node Addr Default: 0000.0000.

0000.0000.0000.

0000.0000.0000.0000.0000

Range: N/A

Format: Hexadecimal

Specifies the master node address where the

SNMP traps will be sent (20 octets). The address

must start with 39, 45, or 47, depending on yourworld region.

Address Type Default: Nsap

Range: N/A

Format: Predefined

Specifies the type of address used for the master

node ATM address.

Nsap Indicates that the master node address is a net-

work service access point-type address.

E164 Indicates that the master node address

E164nsap Indicates that the master node address

Loopback Location

ID

Default: FFFF.FFFF.

FFFF.FFFF.FFFF.

FFFF.FFFF.FFFF

Range: N/A

Format: Hexadecimal

Specifies the unique identifier of the ATM node

where the loopback is to occur (8 octets). The

loopback location ID is the location identifier of

the local PSAX system. It is used as the “source

location ID” in all the outgoing OAM loopback

cells and will be compared with the “destination

location ID” of a received OAM loopback cell to

determine whether the received OAM loopback

cell should be looped back by this PSAX sytem.

You must enter a unique value in this field to

perform OAM loopback tests. For more informa-

tion about OAM loopback tests, see Chapter 5,

“Using System Diagnostics.”Debouncing Period

(msecs)

Default: 3000

Range: 1000–300000

Format: Numeric

(msec)

Specifies the maximum length of time that must

elapse before the PSAX system will clear OAM

AIS and RDI alarms.



255-700-447 5-27



Table 5-13. Field Descriptions for the System Identification Panel on the Site-SpecificConfiguration Window


[Chassis Type] Default: N/A

Range: N/A

Format: predefined

alphanumeric

Displays the type of PSAX system you are config-

uring.

Mux Tcp Type Default: Client

Range: N/A

Format: predefined

alphanumeric

Specifies how the PSAX system is defined for the

TCP connection between the PSAX system and

the connection gateway for messages transmitted

through the Connection Gateway API. If the

PSAX system is designated as the client device,

the PSAX system establishes the connection to

the connection gateway. If the PSAX system is

designated as the server device, the connection

gateway establishes the connection to the PSAX

system.

Client Indicates that the PSAX system is serving as the

client device.

Server Indicates that the PSAX system is serving as the

server device.

Site Name Default: N/A

Range: 1–19

Format: predefined

alphanumeric

Specifies the site name that you define for this

PSAX system. Enter a site name having no more

than 19 characters of the following types: alpha-

numeric, - (hyphen), and _ (underscore). Do not

use spaces or periods.

Switch IP Addr Default: 000.000.000.0

00

Range: N/AFormat: valid dotted

quad

Specifies the IP address that identifies the PSAX

system. This field is only required to be set if you

have a redundant PSAX system. Determine from

your network configuration plan the IP address

you want to use.

IP Mask (display

only)

Default: 000.000.000.0

00

Range: N/A

Format: valid dotted

quad

Specifies the IP mask for Ethernet access to your

PSAX system. This field determines which part of

the IP address is the network identifier, and

shows the subnet mask of the network.

Gateway Addr Default: 000.000.000.0

00

Range: N/A


quad

Specifies the Ethernet address of the router,

which will act as a gateway that the PSAX system

will use to access other networks. Leave this field

blank if you are not using a router. This address

cannot be the same as the CPU IP and switch IPaddresses.

CPU IP Addr Default: 000.000.000.0

00

Range: N/A


quad

Specifies the IP address of the active CPU module

for the PSAX system. Determine from your net-

work configuration plan the IP address you want

to use.

Note: Do not leave this field value as 0.




5-28 255-700-447


Configuring System Date and Time

Perform the following procedure to date and time for your PSAX 2300 from

the Site-Specific Configuration window.

Begin

1 Enter values in the fields on the System Date and Time panel according

to the information provided in Table 5-14.

2 Either select the Apply Site-Specific Configuration command to save

these values now, or wait until you have entered data in all the fields on

this window.

Note: The local time is automatically calculated and displayed in the

[Local Time] field after you apply the values. The local time is

calculated based on the values in the Hour:Min:Sec field and the

selected value in the Time From UTC field.

End

Table 5-14. Field Descriptions for the System Date and Time Panel on the Site-SpecificConfiguration Window


Mon/Day/Yr Default: today’s date

Range: N/A

Format: numeric

(mm/dd/yyyy)

Specifies the current date in month (mm), day

(dd ), and year ( yyyy). Enter the current date in

the format: mm/dd/yyyy (2-digit values for the

month and the day, and a 4-digit value for the

year).

Hour:Min:Sec UTC Default: current

timeRange: N/A

Format: numeric

(24-hour format

[HH:MM:SS])

Specifies the current time for your location in

Universal Time Coordinated (UTC) format(24-hour format) (also known as Greenwich

Mean Time [GMT]).



255-700-447 5-29



Configuring the PSAX System as a TCP Server or a TCP Client

The Connection Gateway API is a protocol that you can use in addition to

SNMP to manage multiple PSAX systems. CGAPI provides an interface to the

PSAX system so that an external workstation, which is acting as a gateway,

can control ATM switching with non-native ATM networking protocols.

Using the API, the gateway and the PSAX system can perform the interwork-

ing for ATM, integrated services digital network (ISDN), signaling system 7

(SS7), channel associated signaling (CAS), and additional protocols.

To configure the PSAX 2300 system as a TCP client or server, perform the fol-

lowing procedure.

Begin

1 In the Site-Specific Configuration window, select the Configure TCP

Server command.The TCP Server Configuration window is displayed (see Figure 5-10 for

client device setup, and Figure 5-11 for server device setup).

2 Enter values in the fields on this window according to the information

provided in Table 5-16.

3 Select the Apply TCP Server Configuration command.

Time from UTC Default: -00 : 00

Range: N/A

Format: numeric

Specifies the differential between the local time

and the UTC (GMT) time. Press Enter to cycle

through the predefined set of values to select avalue (either negative or positive) that indicate

the hours and minutes your local time differs

from the UTC time.

Note: Select 30 for the second segment of this

field if your local time zone is 30 minutes offset

from the UTC.

[Local Time] Default: current

time

Range: N/A

Format: numeric

(12-hour format

[HH:MM:SS] am orpm)

Displays the local time of the PSAX system in

12-hour format with the am or pm indicator.

Note:

[Temperature] Default: N/A

Range: N/A

Format: numeric

(degrees Celsius)

Displays the ambient temperature where the

PSAX system is located.

Table 5-14. Field Descriptions for the System Date and Time Panel on the Site-SpecificConfiguration Window (Continued)





5-30 255-700-447


4 To return to the Site-Specific Configuration window, select the Go Back

to Site-Specific Screen command.

End

The commands on this window have the following functions:

Figure 5-10. TCP Server Configuration Window (PSAX System as a TCP Client)

Figure 5-11. TCP Server Configuration Window (PSAX System as a TCP Server)



255-700-447 5-31



Table 5-15. Commands for the TCP Server Configuration Window

Command Function

Apply TCP Server Configu-

ration

Applies the configuration.

Reset TCP Server Display Resets the display.Go Back to Site-Specific

Screen

Redisplays the Site-Specific Configuration

window.

Table 5-16. Field Descriptions for the TCP Server Configuration Window


Mux TCP Type Default: Client

Range: N/A

Format: predefined

alphanumeric

Specifies how the PSAX system is defined for the

TCP connection between the PSAX system and

the connection gateway for messages transmitted

through the Connection Gateway API. If the

PSAX system is designated as the client device,

the PSAX system establishes the connection tothe connection gateway. If the PSAX system is

designated as the server device, the connection

gateway establishes the connection to the PSAX

system.

Client Indicates that the PSAX system is serving as the

client device.

Server Indicates that the PSAX system is serving as the

server device.

Server IP Address Default: 0000.0000.0

000.0000

Range: N/A


quad

Specifies the IP address of the server, such as the

call controller. This field is displayed only if you

designated the PSAX system as a client in the

Mux Tcp Type field on the Site-Specific Configu-ration window.

CGAPI Default: 0000.0000.0

000.0000

Range: N/A


quad

Specifies the IP address of the Ethernet or in-

band interface over which the CGAPI will send

data.

Note: This field is displayed only if you desig-

nated the PSAX system as a client in the Mux Tcp

Type field on the Site-Specific Configuration win-

dow.

TCP Port Number Default: 1025

Range: 1025–65535

(excluding 5000,5009, and 6000)

Format: numeric

Specifies the TCP server port number. This num-

ber must be a valid number based on the agree-

ment between the connection gateway and thecall controller.



Chapter 5 Site-Specific ConfigurationConfiguring Call Control Resource Allocation

5-32 255-700-447


Configuring Call Control Resource Allocation

Setting the Configuration Values

Perform the following procedure to configure the call control resource alloca-

tion on the PSAX system.

Begin


Configuration option.


2 Select the Call Control Resource Allocation Configuration option.

The Call Control Resource Allocation Configuration window is displayed

(see Figure 5-13).

3 Enter values in the fields on this window according to the guidelines pro-

vided in “Configuration Guidelines” on page 5-34,”and Table 5-19.

4 Select the Apply Configuration command to apply the values entered.

The following messages are displayed in the status line:

Applying the resource allocation configuration...

Resource allocation configuration has been applied. Need to save configuration and reboot system to take effect.

5 Press Ctrl+G to return to the Console Interface Main Menu window, and

save the configuration.

Keep Alive Timer

(secs)

Default: 0

Range: 1–100

Format: numeric

(seconds)

Specifies the interval of time that elapses before

the TCP server sends a query message to deter-

mine whether the connection is still active.

In Active Timer

(secs)

Default: 0

Range: 1–100

Format: numeric

(seconds)

Specifies the amount of time that the server is

inactive before the TCP/IP session is automati-

cally terminated.

Client IP Address Default: 0.0.0.0

Range: N/A


quad

Specifies the IP address of the client. This field is

displayed only if you selected Client in the Mux

TCP Type field on the Site-Specific page.

Table 5-16. Field Descriptions for the TCP Server Configuration Window




255-700-447 5-33



6 Perform the chassis reboot procedure at this time. The path to follow is

from the Console Interface Main Menu > Diagnostics > Reboot Hardware

Components > Reboot Chassis.

End


Figure 5-12. Site-Specific Menu Window

Figure 5-13. Call Control Resource Allocation Configuration Window




5-34 255-700-447


Configuration Guidelines

Table 5-17. Commands for the Call Control Resource Allocation Configuration Window

Command Function

Apply Configuration Applies the values you entered on this window.


Table 5-18. Field Descriptions for the Call Control Resource Allocation Configuration Window


Important: The ranges of values for numeric fields are software imposed. When changing the val-

ues in these fields, keep in mind that the PSAX system calculates the percentage of the memory

allocation usage from the combination of values you have entered in the fields. This calculation is

displayed in the callContrlResAllocUsage field. When all the values of SVC calls and parties, SPVC

calls, Connection Gateway API endpoints, and Connection Gateway API calls and parties are calcu-

lated as a percentage of memory allocation, this percentage value cannot exceed 100 percent of thememory allocation. If you enter a combination of values that exceeds 100 percent when calculated

by the system, the following error message is displayed: T-CallControlResAllocFail. If you

receive this error message, adjust the values in the fields and use the Apply Configuration com-

mand to recalculate the allocation usage percentage value. When you enter a combination of values

that correctly results in a value of 100 percent or less, the following informational message is dis-

played: Resource allocation configuration has been applied. Need to save configura-

tion and reboot the system to take effect.

svcPtToPtCalls Default: 002000

Range: 0–15000

Format: Numeric

Specifies the maximum number of SVC point-to-point

calls to be supported by the PSAX system.

H.248 Applications: For AAL2, this field must be

greater than or equal to the sum of the values in the

atmTrunkNarrowBandCalls and atmTrunkVccs fields.

Set this field to the same value as the

sgApiPtToPtSvcCalls field. For example, if the Maxi-

mum Number of Contexts field on the H.248 Transport

and Resource window is set to 4000 and the Maximum

Number of Terminations field on that window is set to

8000, then the recommended values for this field are

4000 for AAL1 and 4100 for AAL2.

svcPtToMultiPtCalls Default: 002000

Range: 0–4000

Format: Numeric

Specifies the maximum number of SVC point-to-mul-

tipoint calls to be supported by the PSAX system.

H.248 Applications: Set the value in this field to 0.

svcPtToMultiPtPar-

ties

Default: 002000

Range: 0–4000Format: Numeric

Specifies the maximum number of parties on SVC

point-to-multipoint calls to be supported by the PSAXsystem. Set the value in this field to be greater than or

equal to the value in the svcPtToMultiPtCalls field,

because each point-to-multipoint call must have at

least one party.




255-700-447 5-35



Important: If you have already configured your PSAX system and you are considering changing the

sum of the values in the SPVC point-to-point calls fields, keep in mind that the sum of these values

cannot be less than the actual number of SPVC connections already configured in the PSAX system

SPVC table, which is stored in the PSAX system database.spvcCePtToPtCalls Default: 001000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC circuit emu-

lation point-to-point calls to be supported by the PSAX

system. Set the values in the SPVC point-to-point call

fields (spvcCePtToPtCalls, spvcTePtToPtCalls, spvcAt-

mPtToPtCalls, and spvcFrPtToPtCalls) so that the sum

of their values does not exceed the maximum number

of duplex calls per node for SPVCs as indicated in the

table entitled “PSAX System Performance Capabilities

Per Node.”

SPVC Priority Configurations: If you select the value

Enabled in the spvcGlobalPriorityScheme field, the

total number of calls specified in all of the SPVC callfields and the number of ATM trunk VCCs cannot

exceed 32 calls.


spvcTePtToPtCalls Default: 000100

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC terminal

emulation point-to-point calls to be supported by the

PSAX system. Set the values in the SPVC point-to-

point call fields (spvcCePtToPtCalls, spvcTePtToPtCalls,

spvcAtmPtToPtCalls, and spvcFrPtToPtCalls) so that the

sum of their values does not exceed the maximum

number of duplex calls per node for SPVCs as indicated

in the table entitled “PSAX System Performance Capa-

bilities Per Node.”



total number of calls specified in all of the SPVC call

fields and the number of ATM trunk VCCs cannot

exceed 32 calls.


Table 5-18. Field Descriptions for the Call Control Resource Allocation Configuration Window (Continued)





5-36 255-700-447


spvcAtmPtToPtCalls Default: 002000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC ATM point-

to-point calls to be supported by the PSAX system. Set

the values in the SPVC point-to-point call fields

(spvcCePtToPtCalls, spvcTePtToPtCalls, spvcAtmPtToPt-Calls, and spvcFrPtToPtCalls) so that the sum of their

values does not exceed the maximum number of

duplex calls per node for SPVCs as indicated in the


Per Node.”





exceed 32 calls.


spvcFrPtToPtCalls Default: 000900Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC frame relaypoint-to-point calls to be supported by the PSAX sys-

tem. Set the values in the SPVC point-to-point call






Per Node.”





exceed 32 calls.


spvcPtToMultiPt-

Calls

Default: 000500

Range: 0–500

Format: Numeric

Specifies the maximum number of SPVC point-to-mul-






exceed 32 calls.


spvcPtToMultiPt-

Parties

Default: 001000


Specifies the maximum number of parties on SPVC

point-to-multipoint calls to be supported by the PSAXsystem.





exceed 32 calls.










255-700-447 5-39



The maximum numbers for PVC, SPVC, and SVC duplex calls per connection

type available on the PSAX system, as well as the call setup rate for all types

of CPUn modules, are shown in Table 5-19.

cgSvcCutThrough-

Option

Default: cgSvcAcIm-

plicitCutThrough

Range: N/A


Specifies whether the PSAX system or the connection

gateway device (connection manager) sends a cut-

through message to initiate an SVC connection.

Note: The value in this field is relevant only if youhave enabled a media gateway control feature (the

Connection Gateway API feature or the H.248 protocol

feature).

cgSvcAcImplicit-

CutThrough

Indicates that the PSAX system sends a cut-through

message to the connection gateway device to initiate

an SVC connection.

cgSvcAcExplicit-

CutThrough

Indicates that the connection gateway device deter-

mines when to send a cut-through message to the con-

nection manager to initiate an SVC connection.

H.248 Applications: You must use the value

cgSvcAcExplicitCutThrough if you are using the

H.248 protocol feature.

spvcGlobalPriority-

Scheme

Default: Disabled

Range: N/A

Format: Predefined

alphanumeric

Specifies whether the PSAX systemwide priority

scheme must be supported for all SPVCs and SPVC

trunks.

Disabled Indicates that the priority scheme is not in force (dis-

abled).

Enabled Indicates that the priority scheme is in force (enabled).

If you select the value Enabled in this field, the total

number of calls specified in all of the SPVC call fields

and the number of ATM trunk VCCs cannot exceed 32

calls.Note: For SPVC reconnections in priority scheme-

enabled trunks in an IMA link, the limit is 32 SPVCs.



Table 5-19. PSAX System Performance Capabilities Per Node for Release 9.0.0

Connection TypeMaximum Numberof Duplex Calls per

Node

Call Set-up Rate forCPU2 and CPU3L

Modules*

Call Set-up Rate forCPU3 and CPU4

Modules*

PVC 60,000 N/A N/A

SPVC 10,000† 60 calls per second 100 calls per second

SVC 15,000† 60 calls per second 100 calls per second

All connections

combined

60,000‡

* A CPU3 or CPU4 module paired in the same chassis with a CPU2 or CPU3L mod-

ule will operate at the lower CPU2/CPU3L module call rate.




5-40 255-700-447


Saving the Configuration and Rebooting the System

Perform the following procedure to save the values set from the previous

procedure, and reboot the PSAX 2300 system.

Begin

1 Select the Console Interface Main Menu window by pressing Ctrl+G.

The Console Interface Main Menu window is displayed.

2 Select the Save Configuration [Modified] option (Ctrl+A) to save the

modification. [Modified] is removed from the window when Save Con-

figuration is selected.

3 Select the Diagnostics option (Ctrl+D).

The Diagnostics Menu window is displayed (see Figure 5-14).

4 Select the Reboot Hardware Components option.

The Remote Reboot Configuration window is displayed (see

Figure 5-15).

5 Select the Reboot Chassis command.

The VxWorks shell is restarted in a process called the auto-boot. If you

press a key during the auto-boot process, the auto-boot process will stop.

To resume the auto-boot process press Shift+2 (the @ symbol). After the

auto-boot process is complete, the configuration values you entered in

the procedure are now in effect.

The CPUn module(s), and I/O and server modules are rebooted.

6 After the Press RETURN to log in... message is displayed, log back

into the system, if necessary.

End

† When using both SPVC and SVC connection types, you can set up any combina-

tion of calls as long as you do not exceed 100% of the call control resource mem-

ory allocation (callContrlResAllocUsage field on the Call Control Resource Alloca-

tion Configuration window).Refer to the configuration guidelines in the field

description table for this window.‡ For all three types of connections, you cannot configure more than the maximum

number of duplex calls indicated. For OAM monitoring the maximum number ofcalls that can be monitored in one direction is 2,000, and the maximum number

of calls that can be monitored in both directions is 1,000.



255-700-447 5-41



Figure 5-14. Diagnostics Menu

Figure 5-15. Remote Reboot Configuration Window







Chapter 5 Site-Specific ConfigurationEnabling and Disabling PSAX System Features

5-44 255-700-447



Figure 5-17. Feature Turn On/Off Window

Table 5-20. Commands for the Feature Turn ON/OFF Table Window

Command Function

Page Up Scrolls up one page.

Page Down Scrolls down one page.

Top Displays entries at the top of the table.

Bottom Displays entries at the bottom of the table.

Find . . . . . Feature ID: This command is currently not supported.

Go Back to Site-Specific

Menu

Redisplays the Site-Specific Menu window.











255-700-447 5-49


Chapter 5 Site-Specific ConfigurationRebooting CPUn Modules in Redundant and Nonredundant Systems

Rebooting the Nonredundant PSAX System

The following procedure applies typically to all nonredundant PSAX systems.

Begin

WARNING:!

Rebooting the PSAX system with a single (nonredundant) CPUn modulewill interrupt all traffic running through the PSAX chassis.

1 On the Console Interface Main Menu window, select the Diagnostics

option.

The Diagnostics Menu window is displayed.

2 On the Diagnostics Menu window, select the Reboot Hardware Compo-

nents option.

The Remote Reboot Configuration window (see Figure 5-20) is dis-

played.

3 Select the Reboot Primary CPU command.

The following message is displayed in the status line:

Are you sure that you want to do the reboot the primary CPU?

(y/n)

4 Press the Y key.


All traffic on this chassis will be interrupted? Are you

really sure? (y/n)

5 Press the Y key.

The PSAX system begins rebooting the CPUn module. The VxWorks shell

is restarted in a process called the auto-boot. If you press a key during the

auto-boot process, the auto-boot process will stop. You can resume the

auto-boot process by pressing Shift+2 (the @ symbol). After the auto-

boot process is complete, the ACTIVE LED is illuminated and traffic on the

connections resumes.

End







Chapter 5 Site-Specific ConfigurationConfiguring Interface Protection Groups

5-52 255-700-447


Configuring Interface Protection Groups

The Interface Protection Group feature enables you to configure an interface

protection group as primary and secondary, with the secondary group serv-

ing as a standby in the event the primary ATM link fails. You can group inter-

faces of the same type into primary and secondary protection groups. Each

group can have up to four primary and four secondary interfaces. Configur-

ing interface protection groups consists of the following procedures:

[Max Peer ASs] Default: 1

Range:

Format: Numeric

Specifies the maximum number of remote peer

application servers.

[Max Outgoing

Streams]

Default: 251

Range:

Format: Numeric

Specifies the maximum number of outgoing

streams per association.

Client Server

Option

Default: Server

Range: N/A

Format: Predefined

alphanumeric

Specifies the role of the signaling gateway for ini-

tiating the SCTP associations.

Server The server waits for SCTP association establish-

ment.

Client The client initiates SCTP association establish-

ment.

Local SCTP Port Default: 9900

Range: 0–99999

Format: Numeric

Identifies the port of the IUA service. The SCTP

Registered User Port Number Assignment for IUA

is 9900.

Failover Buffer Size

(KB)

Default: 64

Range: 0–999

Format: Numeric

(KB)

Specifies the size of the failover retransmission

buffer. The recommended value is 64 KB. This

value is only valid when buffering is enabled. See

the Recovery Timer field for information on set-

ting a value to enable buffering.

Heart Beat Timer

(msec)

Default: 1000

Range: 0–99999

Format: Numeric

(msec)

Specifies the initial value of the heart beat timer.

The recommended value is 1000 msec.

[Max Peer ASPs Per

AS]

Default: 1

Range:

Format: Numeric

Specifies the maximum number of Application

Server Processes per remote application server.

[Max Incoming

Streams]

Default: 251

Range:

Format: Numeric

Specifies the maximum number of incoming

streams per association.

Table 5-23. Field Descriptions for the IUA Layer Configuration Window (Continued)

Field Name Field Values Field Description



255-700-447 5-53



• Creating a group ID for the interface protection group

• Adding interfaces to the protection group

Note: Before configuring an interface protection group, you must first

make sure you have configured the ports and channels on the

modules you want to include in the protection group. You must

also bring these interfaces into service before setting up an inter-face protection group.

Setting Up an Interface Protection Group ID

Begin

1 On the Site-Specific Menu window, select the Interface Protection

Feature option.

The Interface Protection Feature Configuration menu window is dis-

played (see Figure 5-22).

2 Select the Protection Group Table option.

The Protection Group Table window is displayed (see Figure 5-23).

3 Select the Add a Protection Group command.

The Protection Group Configuration window is displayed (Figure 5-24).


given in Table 5-27.

5 To create a protection group ID and apply the values you selected in the

fields, select the Add to Protection Group command.

End








5-56 255-700-447


The commands on this window have the following functions.

Figure 5-24. Protection Group Configuration Window

Table 5-26. Commands for the Protection Group Configuration Window

Command Function

Add to Protection Group Creates a new protection group ID and applies

the values in the fields.

Delete from Protection

Group and Return

Deletes the protection group ID and redisplays

the Protection Group Table window.

Go Back to Protection

Group Table

Redisplays the Protection Group Table window.

Table 5-27. Field Descriptions for the Protection Group Configuration Window


Group ID Default: 0

Range: 1–9999

Format: numeric

Specifies the group ID that represents a unique

interface protection group within the PSAX sys-

tem.

Switchover Method Default: Auto

Range: N/A

Format: predefined

alphanumeric

Specifies the method used to switch traffic from a

failed primary interface to an available standby

interface.

Auto Indicates that the PSAX system automatically

switches the traffic.

Manual Indicates that the traffic on a failed primary inter-

face is not switched automatically, but must be

switched manually on the Interface Protection

Configuration window.











255-700-447 5-61


Chapter 5 Site-Specific ConfigurationInternet Protocol (IP) Throttling

Internet Protocol (IP) Throttling


tions for your Multiservice Media Gateway system.

Begin

1 From the Console Interface Main Menu, select the Site-Specific Configu-

ration option.

The Site-Specific Menu is displayed (see Figure 5-27).

2 Select the IP Throttling Configuration option.

The IP Throttling Configuration window is displayed (see Figure 5-28

and Figure 5-29).

The IP Throttling window contains fields that allow you to configure the

rate at which the CPU module accepts ingress traffic.



4 To apply the values you have entered, select the Apply Configuration

command.

End

Figure 5-27. Site-Specific Menu (IP Throttling Configuration Option Selected)







Chapter 5 Site-Specific ConfigurationInternet Protocol (IP) Throttling

5-64 255-700-447


Allowed Rate Default: 2000 fps

Range: 100–2000 fps

Specifies the maximum bandwidth allowed to pass

through the ETHERNET or in-band management vir-

tual port into the PSAX system in the unit of frames

per second (fps). Select one of the values listed below.Note: If you do not assign any value, then 2,000 fps

will be used. This value will correspond to 2000 x 64

x 8 bits/second = 1.024 Mbps for 64-byte frames,

2,000 x (576+18) x 8 = 9.504 Mbps for default frame

size of 594 bytes, or 2,000 x 1,518 x 8 = 24.288 Mbps

for 1,518-byte frames. The latter rate is larger than

the maximum rate supported by the 10BASE-T ETH-

ERNET port of the CPU module. For current MIPS

CPU/CPU2 modules, FTP sessions will rarely be

affected under the value of 1,500 and above. Lower

values of the Allowed Rate field will subsequently

cause greater loss of ingress packets.

100 fps Select this value to allow up to 100 frames per second

of input to the CPU module.







1000 fps Select this value to allow up to 1,000 frames per sec-

ond of input to the CPU module.

2000 fps Select this value to allow up to 2,000 frames per sec-ond of input to the CPU module.

Other fps Select this value to allow a number of frames per sec-

ond of input to the CPU module that is not selectable

from the other values in this field, and then enter the

rate you want to use in the Rate field that appears.

Rate Default: N/A

Range: 1–20000 fps

This field appears when Other is selected in the

Allowed Rate field. Enter the rate you want to use.

See the Note in the previous field description for

more information. This field is display only unless

Other fps is selected in the Allowed Rate field.

Leaky Bucket Size Default: 32

Range: 1–20000

The virtual buffer that serves as a counter that moni-

tors the rate of ingress traffic to the CPU module. Itcounts the number of packets and drops packets that

exceed the value you select for this field.

In general, the smaller the value that is used, the

more likely the ingress traffic will be dropped. The

greater value that is used, the more unlikely the

ingress packets will be dropped, and the more bursty

the ingress traffic may become.

Table 5-32. Field Descriptions for the IP Throttling Configuration Window (Continued)




255-700-447 5-65


Chapter 5 Site-Specific ConfigurationSNMP Trap Activation and Deactivation

SNMP Trap Activation and Deactivation

The SNMP Trap Activation/Deactivation feature allows you to suppress the

generation of up to 255 lower-level trap messages, enabling you to view onlythe trap messages you want to see. When traps are suppressed (deactivated),

they are not displayed on the console screen or on the trap log display.

The PacketStar PSAX Simple Network Management Protocol (SNMP) Trap Reference

Guide lists the categories of each trap message. The default is active for five

categories of trap system indicators:

• Response

• Information

• Minor

• Major (Users cannot deactivate this category.)

• Critical (Users cannot deactivate this category.)

Traps for all critical and major indicators that detect system-level component

problems cannot be turned off, so users will always be notified when a prob-

lem affects the entire PSAX system. This feature is available on both the

PSAX system console interface and the AQueView Element Management Sys-

tem.

In Packets

(display only)

Default: N/A

Range: N/A

Format: numeric

The total number of input packets that are received

from both the ETHERNET port of the CPU module and

the in-band management virtual port of the CPU

module.Passed Ether Port

(display only)

Default: N/A

Range: N/A

Format: numeric

The number of input packets passed through the ETH-

ERNET port of the CPU module.

Dropped Ether Port

(display only)

Default: N/A

Range: N/A

Format: numeric

The number of input packets dropped through the

ETHERNET port of the CPU module.

Passed IBM

(display only)

Default: N/A

Range: N/A

Format: numeric

The number of input packets passed through the in-

band management virtual port of the CPU module.

Dropped IBM

(display only)

Default: N/A

Range: N/A

Format: numeric

The number of input packets dropped through the

in-band management virtual port of the CPU mod-

ule.

Time Elapsed

(display only)

Default: N/A

Format: Hours, min-

utes, and seconds

Number of seconds since the Reset Statistics com-

mand was selected.

Table 5-32. Field Descriptions for the IP Throttling Configuration Window (Continued)






255-700-447 5-67


Chapter 5 Site-Specific ConfigurationSNMP Trap Activation and Deactivation

Figure 5-30. Trap Activation Table

Table 5-33. Commands for the Trap Activation Table Window

Command Function

PgUp Displays the previous page in the trap names table.

PgDown Displays the next page in the trap names table.

Top Displays the beginning page in the trap names table.

Bottom Displays the last page in the trap names table.

Find . . . “ “ Searches the trap names table for a text string you enter

between the quotation marks. This function is case-sensitive.

Go Back to Site Specific

Menu






255-700-447 5-69


Chapter 5 Site-Specific ConfigurationCollecting Bulk Statistics

Collecting Bulk Statistics

Overview of Tasks

To collect bulk statistics on ATM and frame relay interfaces on the PSAX sys-

tem to be sent to a remote statistics server, you need to perform the followingtasks:

1. Enable the Bulk Statistics feature on the Feature Turn ON/OFF window.

See “Enabling and Disabling PSAX System Features” on page 5-42.

2. Set up the PSAX system for sending collected statistics to a remote statis-

tics server, such as the NavisXtend Statistics Server (offered by Lucent

Technologies). See the following section for instructions.

3. Select the value Enabled in the Bulk Stats Flag field on the ATM UNI,

the ATM IISP, or the frame relay interface configuration window for an

interface on which you want to collect bulk statistics. For instructions on

interface configuration, see the appropriate PacketStar PSAX I/O module

user guide.4. Select the value Enabled in the Bulk Stats Flag field on the ATM or

frame relay connection configuration window for a connection on which

you want to collect bulk statistics. For instructions on ATM or frame relay

connection configuration, see the PacketStar PSAX Connections Provisioning

Guide. Note that you must have already set the Bulk Stats Flag field to

Enabled on an ATM or frame relay interface before you configure a con-

nection associated with that interface.

Configuring the PSAX System to Use a Statistics Server

Perform the steps in the following procedure to configure the PSAX system to

use a remote statistics server such as the NavixXtend Statistics Server. ThePSAX system sends collected statistics periodically at a user-specified fre-

quency.

Begin




2 On the Site-Specific Menu window, select the Bulk Statistics Configura-

tion option.

The Bulk Statistics Configuration window is displayed (see Figure 5-31).


provided in Table 5-36. The commands on this window are described in

Table 5-35.

End





255-700-447 5-71


Chapter 5 Site-Specific ConfigurationUsing the Equipment Configuration Window

Using the Equipment Configuration Window

This section describes how to obtain product, model, version, and serial num-

ber data about a module from the Equipment Configuration window. In

addition, the window provides operational status and alarm conditions on

each installed module. You also use this window to access the port and chan-

nel configuration windows for the PSAX modules.

Directory Default: None

Range: N/A


Specifies the directory pathname on the network

server to which the PSAX system will send the bulk

statistics. Enter a directory pathname no longer

than 79 characters in length. You must havealready set up this directory pathname on the net-

work server.

Collection Time

Period

Default: 60

Range: 60–1440

Format: Numeric (min-

utes)

Specifies the frequency (in minutes) at which bulk

statistics will be collected and sent to the network

server. Enter a value in increments of 60 minutes,

such as, 60, 120, 180 and so on up to 1440. For

example, if you choose every 60 minutes, the PSAX

system will send the collected bulk statistics to the

network server at the beginning of every hour:

12:00 am, 1:00 am, 2:00 am, and so on.

[Operation Status] Default: Inactive

Range: N/AFormat: Predefined

Displays the current operational status of the trans-

mission of bulk statistics files via FTP to the networkserver.

Inactive Indicates that the PSAX system is not currently

sending bulk statistics file to the network server.

InProgress Indicates that the PSAX system is currently sending

bulk statistics file via FTP to the network server.

Successful Indicates that the most recent bulk statistics file was

sent successfully to the network server.

Failed Indicates that the PSAX system could not success-

fully send the bulk statistics file to the network

server due to an FTP or another type of error.

[Max Usage] Default: 1000

Range: 0–1000

Format: Numeric

Displays the maximum number of bulk statisticsrecords the PSAX system can support for collecting

ATM and frame relay interface statistics and ATM

and frame relay PVC connection statistics.

[Current Usage] Default: 0

Range: 0–1000

Format: Numeric

Displays the number of bulk statistics records cur-

rently being collected including ATM and frame

relay interface statistics and ATM and frame relay

connection statistics.

Table 5-36. Field Descriptions for the Bulk Statistics Configuration Window (Continued)






255-700-447 5-73



Commands The commands on this window are described in Table 5-37.

Field Description The display-only fields on this window are described in Table 5-38.

Figure 5-33. Sample Equipment Configuration Window on a PSAX 1000,PSAX 2300, or PSAX 4500 System (Page 2)

Table 5-37. Commands for the Equipment Configuration Window

Command Function

Update Equipment Display Refreshes the current status of the modules in the PSAX

chassis.

Page Down Displays the second page of the Equipment Configurationwindow.

Page Up Displays the first page of the Equipment Configuration

window.

Interface by Name Displays the Interface Name Table window on which you

can view all the interface names in the PSAX system.





5-74 255-700-447


Table 5-38. Field Descriptions for the Equipment Configuration Window


Slot Default: N/A

Range: 1–25, depend-

ing on chassis type

Format: Numeric

Displays the slot number in the PSAX chassis.

Module Type Default: N/A

Range: from PSAX

system database

Format: Predefined

alphanumeric

Displays the type of the module in the slot. When

a module is inserted into the chassis, its name is

displayed in the Module Type field next to the

slot number. When the module is removed from

the chassis, its name is no longer displayed in the

Module Type field and is replaced with None.

Status Default: Unknown

Range: N/A

Format: Predefined

alphanumeric

Displays the operational status of the module.

Unknown Indicates that the module has not been config-ured.

Primary Indicates one of the following:

• at least one port or channel on an I/O module

has been configured.

• a CPU module is functioning as the primary

CPU module.

Standby Indicates one of the following:

• a module in redundant systems is operating as

the standby (backup) module to the primary

(active) module.

• a CPU module in redundant systems is func-tioning as the standby (backup) CPU module.

Alarm Status Default: No Alarm

Range: N/A

Format: Predefined

alphanumeric

Displays the present alarm condition of the mod-

ule. For the alarm status conditions, see the table

“Alarm Status Descriptions for Modules” follow-

ing this field description table.







255-700-447 5-77


Chapter 5 Site-Specific ConfigurationConfiguring the Stratum 3–4 Module

Setting the Stratum Configuration Values

To configure the Stratum 3–4 module synchronization source, clock accu-

racy, and clock failure backup reference, perform the following procedure.

Begin

1 On the Console Interface Main Menu window, select the Equipment

Configuration command.

The Equipment Configuration window is displayed.

2 On the Equipment Configuration window, select the Stratum module.

The Stratum Configuration window is displayed (see Figure 5-34).

3 Enter values for the fields on this window according to the information


If LineTiming is selected in the Synchronization Source field, the Pri-

mary Line Source and the Secondary Line Source fields and the Switch

Line Timing Source command are displayed (see Figure 5-35).

4 When the configuration is complete, select the Apply Stratum Config-

uration command.

If LineTiming is selected as your synchronization source, complete the

procedure by continuing with these steps:

a Return to the Equipment Configuration window

b Select the same slot that was selected in the Primary/Secondary Line

Source fields in the Stratum Configuration window

c Select LocalTiming in the Transmit Clock field of the configuration

window for the module in the selected slot.

End

Figure 5-34. Stratum Configuration Window (Freerun)





255-700-447 5-79



Table 5-41. Field Descriptions for the Stratum Configuration Window

Field Name Mode of Operation Description

[Primary Stratum

Mode]

Default: Holdover

Range: N/A

Format: Predefined

Indicates the current mode of operation for the pri-

mary Stratum 3–4 module.

Holdover Indicates that the primary module has lost its syn-

chronization source because of excessive frequency

offset and that the Holdover timing mode is main-

taining chassis timing.

Freerun Indicates that the primary module is operating from

the internal clock source either by design or

because the Holdover timing mode has excessive

frequency offset.

Synchronized3 Indicates the module clock circuitry is locked to a

Stratum3 level of precision.



CardRemoved Indicates that the primary Stratum 3–4 module is

not present.

[Backup Stratum

Mode]

Default: Holdover

Range: N/A

Format: Predefined

Indicates the current mode of operation for the

backup Stratum 3–4 module.

Holdover Indicates that the backup module has lost its syn-

chronization source because of excessive frequency

offset and that the Holdover timing mode is main-

taining chassis timing.

Freerun Indicates that the backup module is operating from

the internal clock source either by design or because the Holdover timing mode has reached

excessive frequency offset.





CardRemoved Indicates that the backup Stratum 3–4 module is

not present.




5-80 255-700-447


[Line Timing Sta-

tus]

Default: None

Range: N/A

Format: Predefined

Indicates the current line timing status for the

module.

None Indicates that the system timing is not being pro-

vided by the line timing source.

PrimaryLine Indicates that the system timing is provided by the

slot and port of the module specified as the Primary

Line Source when LineTiming is selected as the

synchronization source.

SecondaryLine Indicates that the system timing is provided by the

slot and port of the module specified as the Second-

ary Line Source when LineTiming is selected as

the synchronization source and the primary line

source has been removed or failed.

[Primary StratumT1/E1 Port Status]

Default: Unconfig-ured

Range: NA

Format: Alphabetical

Indicates the status of the input T1BITS or E1ETSIclock source connected to the external clock con-

nector on the primary Stratum 3–4 module.

Unconfigured Indicates the T1BITS or E1ETSI clock source is not

connected to the external clock connector.

noalarm Indicates the connected T1BITS or E1ETSI clock

source is functioning properly.

portAIS Indicates the connected T1BITS or E1ETSI clock

source is reporting an alarm indication signal.

portLOF Indicates the connected T1BITS or E1ETSI clock

source is reporting a loss of frame.portLOS Indicates the connected T1BITS or E1ETSI clock

source is reporting a loss of signal.

portFOS Indicates the connected T1BITS or E1ETSI clock

source is reporting a frequency offset.

Table 5-41. Field Descriptions for the Stratum Configuration Window (Continued)




255-700-447 5-81



[Backup Stratum

T1/E1 Port Status]

Default: Unconfig-

ured

Range: NA


Indicates the status of the input T1BITS or E1ETSI

clock source connected to the external clock con-

nector on the baclup Stratum 3–4 module.

Unconfigured Indicates T1BITS or E1ETSI clock source is not con-

nected to the external clock connector.

noalarm Indicates the connected T1BITS or E1ETSI clock

source is functioning properly.

portAIS Indicates the connected T1BITS or E1ETSI clock

source is reporting an alarm indication signal.

portLOF Indicates the connected T1BITS or E1ETSI clock

source is reporting a loss of frame.

portLOS Indicates the connected T1BITS or E1ETSI clock

source is reporting a loss of signal.

portFOS Indicates the connected T1BITS or E1ETSI clock

source is reporting a frequency offset.

Accuracy Default: Stratum3

Range: NA


Indicates the precision of the clock circuitry when it

locks to the selected external synchronization

source (CompositeClock, CompositeClock-

DS0A, T1BITS, and E1ETSI, selected in the Syn-

chronization Source field).

Stratum3 Indicates the timing source has a Stratum3 level of

precision.

Stratum4 Indicates the timing source has a Stratum4 level of

precision.

On Reference ClockFailure Go To

Default: Freerun

Range: NA


Indicates what timing source is used when theselected synchronization source fails, except

LineTiming. If LineTiming is selected, both the

Primary Line Source and Secondary Line Source

clocks must fail before reverting to this clock.

Freerun Indicates that the module switches to freerun if the

selected synchronization source fails.

Holdover Indicates that the module switches to holdover

mode if the selected synchronization source fails.







255-700-447 5-83



Switching the Line Timing Source

At any time after initial configuration of the Stratum 3–4 module and

LineTiming has been selected as the synchronization source, you can switch between the primary line source or the secondary line source, as follows:

Begin

1 Select the Switch Line Timing Source command.

2 Press Enter.

The value displayed in the [Line Timing Status] field is changed.

End

Secondary Line

Source

Default: Slot: 00 Port:

00

Range: Chassis/mod-

ule dependentFormat: Numeric

Specifies the secondary line source when LineTim-

ing is selected in the Synchronization Source field.

Enter the values for the slot and the port of the

desired I/O module port that is providing line tim-ing. Leave the default value if you do not want to

specify a secondary line source. If both line sources

fail, timing reverts to the timing source selected in

the On Reference Clock Failure Go To field.

Slot Default: 00

Range: Depends on

chassis.

Format: numeric

Displayed as part of the Primary Line Source and

Secondary Line Source fields. Select the slot in the

PSAX system that contains the desired I/O module

you want to use as the primary or secondary line

source.

Port Default: 00

Range: Primary Line

Source, depends onthe number of ports

on the module

selected in the Slot field; Secondary Line

Source, 00–30, or All

Range: numeric

Displayed as part of the Primary Line Source and

Secondary Line Source fields. Select the port of the

I/O module you selected in the Slot field that is pro-viding line timing as the primary or secondary line

source. For the number of ports on a module, refer

to the appropriate PSAX module user guide.





Chapter 5 Site-Specific ConfigurationSaving the Equipment Configuration Values and Logging Off

5-84 255-700-447


Alarm Status Values

I/O and server modules display the status value of Primary if they are con-

figured, or Unknown if they are unconfigured. The Alarm Status column for

unconfigured modules still can have a number listing the ports that are avail-

able to be configured. If numbers in the Alarm Status column are under-

lined, this condition indicates a loss of signal.

Saving the Equipment Configuration Values and LoggingOff

After configuring your basic systemwide values, you must save them to the

PSAX system database. It is recommended that you save your values fre-

quently as you progress through your work. If you modify your system con-

figuration before you begin upgrading your system software release in the

same console session, you must save your configuration first before begin-

ning the upgrade procedure.

Perform the following procedure to permanently save the values for your

system.

! CAUTION:If your system loses power or if you reboot the chassis, and you have notyet saved the values permanently, you will lose all unsaved values youhave applied on the various windows.

Begin


On the Console Interface Main Menu window, [Modified] is displayed

next to the Save Configuration command, indicating you have made

changes to the system that are not yet saved to the PSAX system database

(see Figure 5-36).



255-700-447 5-85



2 Select the Save Configuration command or press Ctrl+A.

Wait a few seconds while the system writes the values to the PSAX sys-

tem database. The system displays the following message while it is exe-

cuting this command:

Saving the equipment and connection information

Note: In PSAX systems with redundant CPUn modules, the standby

CPUn module reboots every time you save the configuration on

the primary CPUn module. This event is a function of the SVCretention feature and the result of saving the configuration

changes you have made.

When the save configuration function is completed, the system displays

an appropriate message as described in Table 5-42.

Figure 5-36. Save Configuration [Modified] (Before Saving)

Table 5-42. Messages Generated after the Save Configuration Process

When a PSAXsystem is...

the system displays...

nonredundant T-SaveConfiguration: saveConfigurationReasonCode=All-OK

redundant T-SaveConfiguration: saveConfigurationReasonCode =

Expect2ndCPUCardFailedOrRemoved*

The standby CPUn module is rebooted when the save command is issued.After the standby CPUn module reboots, the system displays the following

message: T-SaveConfiguration: saveConfigurationReason-

Code=FileTransferCompleted

* This message indicates that while the standby CPUn module reboots after you select the SaveConfiguration command, the standby CPUn module is temporarily unavailable.




5-86 255-700-447


After saving the configuration values, the indicator [Modified] is no

longer displayed next to the Save Configuration command.

3 You can now safely exit the current session by selecting the Leave Con-

sole Interface command. This action logs you off the PSAX system con-

sole interface.

! CAUTION:Always exit the PSAX system by using the Leave Console Interface com-mand. Do not just close your HyperTerminal or Telnet window withoutfirst using this command because doing so might cause access problemsat a later time.

En




255-700-447 6-1

6 Configuring ATM PNNI

Overview of ATM PNNI Systemwide Configuration

For an overview of ATM PNNI and the ATM PNNI features supported on the

PSAX 2300 system, see Chapter 3.

To configure a ATM PNNI node for your PSAX 2300 system, perform the fol-

lowing procedure.

Note: Before you can configure an I/O module with the ATM PNNI 1.0

interface, you must configure one or more ATM PNNI nodes for

your PSAX 2300 system.

Configuring an ATM PNNI Node

Begin

1 At the Console Interface Main Menu, select Site-Specific Configuration

(or press Ctrl+P).

The Site-Specific Menu is displayed.

2 On the Site-Specific Menu window, select the PNNI System-Wide Con-

figuration option (or press Ctrl+N).

The PNNI System-Wide Configuration window is displayed (see

Figure 6-1).

3 Select the PNNI Node Configuration option (or press Ctrl+N).

The PNNI Node Table window is displayed (see Figure 6-2).

4 Select the Add Node Entry command.

The PNNI Node Configuration window is displayed (see Figure 6-3).

5 Select the values for the fields on this window from the values given in

Table 6-5.

6 Select the Create Node Entry command (or press Ctrl+A).

The Node entry is created and the Node Id field displays the node identi-

fier of your PSAX 2300 system.7 Select the Bring Node Into Service command (or press Ctrl+N).

The [OperStatus] display field on the lower left panel indicates that the

node is up (see Figure 6-4).

Note: You must bring the node into service to enable PNNI support on

your PSAX 2300 system. The ATM PNNI interface cannot be

brought into service until a PNNI node is created and in service.



Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Node

6-2 255-700-447


If you need to take the node out of service, you must first delete

any ATM PNNI interfaces you have configured on your

PSAX 2300 system.

8 Select the Go Back to Previous Screen command (or press Ctrl+B).

The PNNI Node Table (see Figure 6-2) is displayed, showing your current

node index, node level, and operating status. Use this screen to check anode’s status whenever you create, delete, or bring a node into service.

9 Press Ctrl+G to go back to the Console Interface Main Menu window.

End

The menu options on this window have the following functions:

Figure 6-1. PNNI System-Wide Configuration Menu Window

Table 6-1. Commands for the PNNI System-Wide Configuration Window

Menu Option Name Function

PNNI Node Configuration Displays the PNNI Node Table window on which

you add a PNNI node.

PNNI Route Address Configura-

tion

Displays the PNNI Route Address Table window on

which you add a PNNI route address.

PNNI Route TNS Configuration Displays the transit network string (TNS) informa-tion: node index, TNS type, TNS plan, TNS ID, and

TNS index.

PNNI Summary Address Config-

uration

Displays ATM NSAP addresses for all nodes to

which this link table is attached by PNNI interfaces.



255-700-447 6-3



PNNI Map Link Information Displays the mapping for the nodes and their links,

and all original port and remote port PNNI topology

state element (PTSE) identifiers and the metrics tag

number.

PNNI Map Node Information Displays the PNNI node ID and Map Node ID (in

hexadecimal).

PNNI Map Address Information Displays the node index, advertising node ID in

hexadecimal, advertising port ID, and address

index.

PNNI Map TNS Information Displays the node index, advertising node ID, and

advertised port ID.

PNNI Link Information Displays an index of nodes and their associated links

for the PSAX system.

PNNI SVCC RCC Information Displays the node index, PNNI SvccRcc Index, VPI,

and VCI.

PNNI Neighbor Peer Informa-

tion

Displays nodes that are on the same level as this

node.

PNNI Neighbor Peer Port Infor-

mation

Displays the status of the node ports on the same

level as this node.

PNNI PTSE Information Displays the node index, PNNI Topology State Ele-

ment (PTSE) originating node ID, and PTSE ID.

PNNI System Statistics Displays PNNI statistics.


Table 6-1. Commands for the PNNI System-Wide Configuration Window (Continued)

Menu Option Name Function




6-4 255-700-447



The display fields on this window have the following values:

Figure 6-2. PNNI Node Table Window

Table 6-2. Commands for the PNNI Node Table Window

Command Function

Page Up Scroll up one page.




Find Node Index Displays default five-number value on the Node Table

window.

Add Node Entry Adds a node entry in the PSAX system. You may add up

to 400 nodes.

Go Back to Previous Screen Redisplays the PNNI System-Wide configuration window.



255-700-447 6-5



Table 6-3. Field Descriptions for the PNNI Node Table Window

Field Name Description

Total: 0/0 Displays the first number in this field indicates the identifica-

tion number of the connection table entry on the first line of

the currently displayed window. The second number indi-

cates the total number of connection table entries for thisconnection type.

Note: For more information on the values in the display fields below, see the Field Descrip-

tion Table for the PNNI Node Configuration window.

Node Index Displays default five-number value on the Node Table win-

dow, and identifies a logical PNNI entity in the PSAX system.

Node Level Displays the number of significant bits in the network portion

of the ATM address on the PSAX system.

Oper Status Displays whether the node is up or down.

Figure 6-3. PNNI Node Configuration Window (Before Configuration)




6-6 255-700-447



Figure 6-4. PNNI Node Configuration Window (After Configuration)

Table 6-4. Commands for the PNNI Node Configuration Window

Command Function

Create Node Entry Creates a new PNNI node.

Delete Node Entry Deletes an existing PNNI node.

Bring Node Into Service Brings an existing PNNI node into or out of service.

PNNI Node Pgl Table Displays the PNNI Node Pgl (Peer Group Leader) Configu-

ration window.

PNNI Node Timer Table Displays the PNNI Node Timer Configuration window.

PNNI Node SVCC Table Displays the PNNI Node SVCC Configuration window.

PNNI Node Scope Mapping

Table

Displays the PNNI Scope Mapping Configuration window.

ATM Security Config - Routing

SVCC

Displays the ATM PNNI SVCC RCC Security Configura-

tion window.

Go Back to Previous Screen Redisplays the PNNI Node Table window.



255-700-447 6-7



Table 6-5. Field Descriptions for the PNNI Node Configuration Window


Node Index Default: 000000

Range: 1–400

Format: Numeric

Displays the node index that identifies a logical

PNNI entity in the PSAX system. Enter the index

number of each node in this field.

Node ID Default: 0

Range: N/A

Format: Hexadecimal

Indicates the system generates your Node Id

automatically. For more information, see

Section 5.3.3, Node Identifiers, in the ATM

Forum Specification, Private Network-Network

Interface (PNNI 1.0) Specification Version 1.0, af-pnni-

0055.000.

Atm Address Default: 0

Range: N/A

Format: Hexadecimal

Enter your ATM NSAP address, a hexadecimal

number within the network’s PNNI hierarchy

that must beginning with 39, 45, or 47, depend-

ing on your world region.

H.248 Applications: This address must be differ-

ent from the Master ATM address configured on

the Site Specific Configuration window.

Peer Grp ID Default: 0

Range: N/A

Format: Hexadecimal

Indicates the first 12 bytes (default) of the ATM

address. This value is the combination of the ATM

address and the node level. The first byte indi-

cates the node level. The following bytes comes

from the ATM address where the number bytes

coming from the ATM address depend on the

Node level. For example, a node level of 96 bits

(default) then the next 12 bytes (96 bits) are

from the ATM address.

This value is generated and displayed by the sys-

tem automatically. For more information, see

Section 5.3.3, Node Identifiers, in the ATM

Forum Specification, Private Network-Network

Interface (PNNI 1.0) Specification Version 1.0, af-pnni-

0055.000.

Domain Name Default: N/A

Range: N/A

Format: Alphanu-

meric

Indicates the routing domain in which this node

participates.

Node Level Default: 096

Range: 96 (deci-

mal)=60 (hexadeci-

mal); 1–104Range: Hexadecimal

Indicates the level of PNNI hierarchy at which

this node exists. Indicates the number of signifi-

cant bits in the network portion of the ATM

address on the PSAX system. This number isrelated to the first octet (two digits) of the node

identifier. All PSAX systems within the same peer

group should be in the same node level.

Enter in decimal form and the system will gener-

ate and display the value automatically.




6-8 255-700-447


Node Lowest Default: True

Range: N/A

Format: Predefined

Indicates whether or not this node is the root

node.

True The current node is the root.

False The current node is not the root.

Res. Transit Default: False

Range: N/A

Format: Predefined

Restricted Transit indicates whether the node is

restricted to not allowing support of SVCs trans-

mitting from this node.

False Indicates SVC transmission from the node is

allowed, or not restricted.

True Indicates SVC transmission from the node is not

allowed, or restricted.

Complex Node Default: False


Specifies whether this node uses the complex

node representation. This attribute determinesthe setting of the nodal representation bit in the

nodal information group originated by this node.

False Indicates that simple node representation is used.

True Indicates that the complex node representation is

used.

[Res Branching] Default: False

Range: N/A

Format: Predefined

Restricted branching indicates whether the node

is able to support additional point-to-multipoint

branches. This attribute reflects the setting of the

restricted branching bit in the nodal information

group originated by this node.

False Indicates that additional branches can be sup-

ported.

True Indicates that additional branches cannot be sup-

ported.

[DB Overload] Default: True

Range: N/A

Format: Predefined

Displays whether Database Overload is selected,

which specifies whether the node is currently

operating in a topology database overload state.

This attribute has the same value as the nontran-

sit for PGL election bit in the nodal information

group originated by this node.

True Indicates the node is currently operating in a

topology database overload state.

False Indicates the node is not currently operating in atopology database overload state.

[No of Ptses] Default: 0

Range: N/A

Format: Numeric

Displays the number of PTSEs displays the total

PTSEs currently in the topology database(s) for

this node.

Table 6-5. Field Descriptions for the PNNI Node Configuration Window (Continued)






Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Node Peer Group Leader (PGL)

6-10 255-700-447


2 Enter the values for this window according to the information provided

in Table 6-8.

3 After all values are selected and entered, select Apply Configuration

press Ctrl+A.

A trap message will confirm the configuration at the bottom of the win-

dow.

4 Select Go Back to Previous Screen or press Ctrl+B to return to the

PNNI Node Configuration window to configure other field values.

End

The command on this window performs the following function:

Figure 6-5. PNNI Node PGL Configuration

Table 6-7. Commands for the PNNI Node Timer Configuration Window

Command Function

Apply Configuration Applies the values you set on this window.

Go Back to Previous Screen Redisplays the PNNI Node Configuration window.



255-700-447 6-11



Table 6-8. Field Descriptions for the PNNI Node PGL* Configuration Window


Node PGL Information Upper Panel

[Node Index] Default: 0

Range: 1–400

Displays the node index that identifies a logical PNNI

entity in the PSAX system. Enter the index number of

each node in this field.

Leadership Prior-

ity

Default: 0

Range: 0–205

Format: numeric

Indicates the user-assigned ranking of a logical node.

Usually the node with the highest ranking in a peer

group will be elected peer group leader (PGL).

Cfg Parent Node

Index

Default: 0

Range: 1–65535

Format: numeric

Indicates a parent node is the logical group node that

represents the contained peer group of a child node(s)

at the next lower level of the hierarchy.

Initiation Time Default: 15

Range: 0–15

Format: seconds

Indicates the initiating time of the PGL election pro-

cess. When this timer fires, the election begins after

the time set by the user.

Override Delay Default: 30Range: 0–30

Format: seconds

Indicates the amount of time the node should wait forall nodes to agree on which node should be elected

PGL.

Reelect Time Default: 15

Range: 0–15

Format: seconds

Indicates the time intervel the node should wait before

restarting the PGL election process, after it discovers it

has no connectivity to the current PGL.




6-12 255-700-447


Upper Panel (display only)

[State] Default: OperPgl

Range: N/A

Format: predefined

Displays the status of this node PGL.

OperPgl Displays that the status of this node is the PGL. It con-

tinues examining PTSEs sent by other nodes to see if

another node has a higher priority than itself.

Starting Displays that this node is in the initial state of the state

machine.

Awaiting Displays that this node has started the Hello FSM on at

least one link, and that no peer group has yet been

found.

AwaitingFull Indicates that at least one neighboring peer has been

found, but no database synchronization process has

been completed.

InitialDelay Indicates that the database synchronization process

has been completed with at least one neighboring

peer, and the PGL initiation timer has started. The

node must wait before for the period of time specified

in the Initiation Time field before it can select and

advertise its preferred PGL.

Calculating Indicates that the node is in the process of calculating

its new choice for the preferred PGL.

AwaitUnanimity Indicates that the node has chosen itself as the PGL.

The node wil check whether all other nodes elect this

node to be the PGL unanimously.

OperNotPgl Indicates that this node is not the PGL. It examines

PTSEs sent by other nodes to determine whether

another node has a higher priority than itself.

HungElection Indicates that the node has chosen itself as the PGL,

but not all other nodes will advertise it as their pre-

ferred PGL.

AwaitReElection Indicates that the node has lost connectivity to the

current PGL. If the connectivity has not been reesetab-

lished before the period of time specified in the Reelect

Time field, the election process is restarted.

Table 6-8. Field Descriptions for the PNNI Node PGL* Configuration Window (Continued)




255-700-447 6-13


Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Node Timer

Configuring an ATM PNNI Node Timer

Begin

1 From the PNNI Node Configuration window, select PNNI Node Timer

Table or press Ctrl+T.

The PNNI Node Timer Configuration window is displayed (seeFigure 6-6).


in Table 6-5.

3 After setting all the values on the window, select Apply Configuration

or press Ctrl+A.

A trap message at the bottom of the window confirms the configuration

application.


PNNI Node Configuration window if you need to configure other field

values.

End

[Preferred Pgl] Default: 0

Range: N/A

Format: Hexadeci-

mal address (up to11 octets)

Displays the preferred PGL. To select, any node com-

pares the leadership priorities and node IDs advertised

in the PTSEs in the topology database, and determines

which nodes reachable from itself.

[Peer Group

Leader]

Default: 0

Range: N/A

Range: Hexadeci-

mal address (up to

11 octets)

Displays a node of a peer group that does the extra

work of collecting, aggregating, and building data that

is used to represent the entire peer group as a single

node. This infomation is available in the parent node.

[Time Stamp] Default: 00:00:00

Range: N/A

Format: hh:ss:mm

(hour, second,

msec.)

Displays the recorded completion time of a successful

PGL election. If the PGL election is unsuccessful, the

timer will display with the default value.

* Peer Group Leader.

Table 6-8. Field Descriptions for the PNNI Node PGL* Configuration Window (Continued)





6-14 255-700-447


The commands on this window perform the following functions:

Figure 6-6. PNNI Node Timer Configuration Window


Command Function



Table 6-10. Field Descriptions for the PNNI Node Timer Configuration Window


Node Timer Information Panel


Range: 1–400

Format: numeric


PNNI entity in the PSAX system.

Ptse Holddown..

(100 msec)

Default: 00010

Range: 1–65535

Format: numeric

multiplier of

100 msec

Indicates a PNNI Topology State Element (PTSE),

a collection of PNNI information that is flooded

among all logical nodes in a peer group. The

hold-down timer prevents a node from sending

hello packets at unacceptably high rates. The ini-

tial value of this timer is used by a node to limitthe rate at which it can re-originate PTSEs.

Note: Each increment entered in this field is a

multiplier of 100 msec. A value of 10 = 1 second,

or 100 msec × 10.



255-700-447 6-15



Hello Holddown..

(100 msec)

Default: 00010

Range: 0–65535

Format: numeric

multiplier of100 msec

Indicates the initial value for the Hello Hold-

down timer, which is used by a node to limit the

rate at which it sends Hellos.

Note: Each increment entered in this field is amultiplier of 100 msec. A value of 10 = 1 second,

or 100 msec × 10.

Hello Interval..(sec) Default: 00015

Range: 0–65535

Format: numeric

(sec)

Indicates the initial value for the Hello timer. In

the absence of triggered Hellos, this node will

send one Hello packet on each of its ports at this

interval.

Hello Inactivity

Factor

Default: 00005

Range: 0–65535

Format: numeric

Indicates the value this node will use to deter-

mine when a neighbor has failed.

Hlink Inact..(sec) Default: 00120

Range: 0–65535

Format: numeric

(sec)

Indicates the horizontal link inactivity time (hori-

zontal links are between nodes in the same peergroup at the same level). The length of time a

node will continue to advertise a horizontal link

for which it has not received and processed the

logical group node (LGN) horizontal link infor-

mation group (IG).

Ptse Refresh Inter-

val..(sec)

Default: 01800

Range: 0–65535

Format: numeric

(sec)

Indicates the time between re-originations of a

self-originated PTSE in the absence of triggered

updates. A node will reoriginate its PTSEs at this

rate in order to prevent flushing of its PTSEs by

other nodes.

Ptse Lifetime Factor Default: 0200

Range: 101–1000

Format: numeric

(percentage)

Indicates the formula which calculates this prod-

uct: Ptse Refresh Interval × PTSE LifetimeFactor = PTSE Lifetime of self-originated PTSEs.

Rxmt Interval..(sec) Default: 00005

Range: 0–65535

Format: numeric

(sec)

Specifies the retransmit interval, which is the

period between retransmissions of unacknowl-

edged database summary packets, PTSE request

packets, and PNNI Topology State Packets

(PTSPs).

Peer Delayed Ack

Interval..

(100 msec)

Default: 00010

Range: 0–65535

Format: numeric

multiplier of100 msec

Specifies the peer-delayed acknowledgement

interval, which is the minimum number of mili-

seconds between transmissions of delayed PTSE

acknowledgement packets.

Note: Each increment entered in this field is a

multiplier of 100 msec. A value of 10 = 1 second,

or 100 msec × 10.

Avcr Proportional

Multiplier

Default: 50

Range: 1–99

Format: numeric

(percentage)

Indicates the available cell rate (Avcr) propor-

tional multiplier (PM), which is used in an algo-

rithm that determines significant change for aver-

age cell rate parameters.

Table 6-10. Field Descriptions for the PNNI Node Timer Configuration Window (Continued)




Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Node SVCC

6-16 255-700-447


Configuring an ATM PNNI Node SVCC

Begin

1 From the PNNI Node Configuration window, select PNNI Node SVCC

Table or press Ctrl+V.

The PNNI Node SVCC Configuration window is displayed (see

Figure 6-7).


in Table 6-12.


or press Ctrl+A.

A trap message confirming the configuration application appears at the

bottom of the window.



values.

En

Avcr Minimum

Threshold

Default: 03

Range: 1–99

Format: numeric

(percentage)

Indicates the available cell rate (Avcr) minimum

threshold (MT), which is used in the algorithm

that determines significant change for average

cell rate parameters.

Cdv Proportional

Multiplier

Default: 25

Range: 1–99

Format: numeric

(percentage)

Indicates the cell delay variance proportional

multiplier, which is used in the algorithm that

determines significant change for CDV metrics.

Ctd Proportional

Multiplier

Default: 50

Range: 1–99

Format: numeric

(percentage)

Indicates the cell transfer delay proportional mul-

tiplier, which is used in the algorithm that deter-

mines significant change for CTD metrics. The

multiplier is the percentage of the last advertised

maximum CTD such that a change within the

range maxCTD ± (maxCTD × maxCTD_PM ÷ 100) is

not considered significant.

Table 6-10. Field Descriptions for the PNNI Node Timer Configuration Window (Continued)




255-700-447 6-17


Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Node SVCC


Figure 6-7. PNNI Node SVCC Configuration Window


Command Function



Table 6-12. Field Descriptions for the PNNI Node SVCC Configuration Window



Range: 1–400

Format: numeric



Init Time Default: 4

Range: 0–65535

Format: seconds

Indicates the initiating time, the amount of time

this node will delay initiating establishment of an

SVCC to a neighbor with a numerically lower

ATM address, after determining that such an

SVCC should be established.

Retry Time Default: 30

Range: 0–65535

Format: seconds

Indicates the number of times that his node will

wait before attempting to re-establish a SVCC- based RCC.



Chapter 6 Configuring ATM PNNIConfiguring ATM PNNI Node Scope Mapping

6-18 255-700-447


Configuring ATM PNNI Node Scope Mapping

A scope defines the level of advertisement for an address. The level is the

ranking of a peer group in the PNNI routing hierarchy.

Begin

1 From the PNNI Node Configuration window, select PNNI Node Scope

Mapping Table or press Ctrl+C.

The PNNI Scope Mapping Configuration window is displayed (seeFigure 6-8).


in Table 6-5.


or press Ctrl+A.





values.

End

Calling Integrity

Time

Default: 35

Range: 0–65535

Format: seconds

Indicates the calling integrity time, which is the

amount of time this node will wait for an SVCC

that it has initiated establishment of as the calling

party, to become fully established, before givingup and tearing the SVCC down.

Called Integrity

Time

Default: 50

Range: 0–65535

Format: seconds

Indicates the called integrity time, which is the

amount of time that this node should wait for an

SVCC that it has decided to accept as the calling

party, to become fully established, before giving

up and tearing the SVCC down.

Traffic Descriptor

Index

Default: 0

Range: 1–65535

Format: numeric

Indicates the traffic descriptor index to the ATM

Traffic Descriptor Parameter Table, as defined in

RFC 1695. This traffic descriptor is used when

establishing SVCs for use as SVCC-based RCCs to

or from PNNI logical group nodes.

Table 6-12. Field Descriptions for the PNNI Node SVCC Configuration Window (Continued)




255-700-447 6-19


Chapter 6 Configuring ATM PNNIConfiguring ATM PNNI Node Scope Mapping


Figure 6-8. PNNI Scope Mapping Configuration


Command Function



Table 6-14. Field Descriptions for the PNNI Scope Mapping Configuration Window



Range: 1–400

Format: numeric

Indicates the node index that identifies a logical


Local Network

(display only)

Default: 96

Range: 0–104

Format: numeric

Indicates the highest level of PNNI hierarchy (or

the smallest PNNI routing level) that lies within

the Local Network organizational scope.

Local Network Plus

One

(display only)

Default: 96

Range: 0–104

Format: numeric



the Local Network Plus One organizational scope.

Local Network Plus

Two

(display only)

Default: 96

Range: 0–104

Format: numeric



the Local Network Plus Two organizational scope.

Site Minus One

(display only)

Default: 80

Range: 0–104

Format: numeric



the Site Minus One organizational scope.





255-700-447 6-21


Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Route Address

Begin

Note: If you are configuring an SPVC as ActiveSvc, do not configure a

route address. If you configuring an SPVC as PassiveSvc, config-

ure a route address.

1 From the PNNI System-Wide Configuration menu, select the PNNI Route

Address Configuration option or press Ctrl+A.

The PNNI Route Address Table is displayed (see Figure 6-9)

2 Select the Add Route Address Entry command.

The PNNI Route Address Configuration window is displayed (see

Figure 6-10).



4 Select the Create Route Address Entry command.

The route is completed.

5 Using the instructions in the appropriate PSAX module user guide, con-

figure a second port with the ATM UNI interface (you must create the

ATM UNI interface if it does not yet exist) and bring the ATM UNI inter-

face into service.

6 To add additional route addresses, repeat this procedure.

En

.

The commands in this window have the following functions:

Figure 6-9. PNNI Route Address Table Window







Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Route Address

6-24 255-700-447


Address Type Default: Exterior

Range: N/A

Format: Predefined

Indicates the type of domain address.

Exterior Indicates a connection from the advertising node

to the address prefix that belongs to an external

domain address.

Other Belongs to a domain address that is not defined as

internal or external.

Reject Indicates that messages from a matching address

prefix should be discarded as unreachable.

Internal Belongs to the same domain address, administra-

tive authority, or attached device.

Address Scope Default: 0

Range: N/A

Format: Numeric

Indicates the level of the PNNI hierarchy where

the connectivity between the advertising node

and the address prefix is located.

VP Capability Default: True

Range: N/A

Format: Predefined

Indicates whether virtual path connections

(VPCs) can be established between the advertis-

ing node and the address prefix.

True VPCs can be established between the advertising

node and the address prefix.

False VPCs cannot be established between the advertis-


Org Advertisement Default: True

Range: N/A

Format: Predefined

Indicates whether the local node should advertise

the reachable address on its domain (where it

originates).

True The local node should advertise the reachable

address on its domain (where it originates).

False The local node should not advertise the reachable

address on its domain (where it originates).

[Adv Ptse Id] Default: 0

Range: 0–2147483647

Format: Numeric

Displays the advertised PTSE identifer of the PTSE

being sent by the originating node, if this was

learned through PNNI 1.0.

Table 6-17. Field Descriptions for the PNNI Route Address Configuration Window (Continued)




255-700-447 6-25


Chapter 6 Configuring ATM PNNIConfiguring ATM PNNI Metrics

Configuring ATM PNNI Metrics

The PNNI Metrics Table window displays the PNNI parameters associated

with a PNNI entity, or connectivity between a node and a reachable address

or transit network. The PSAX system acquires such information as advertised

[Address Proto] Default: Mgmt

Range: N/A

Format: Predefined

Displays the protocol by which connectivity from

the advertising node to the address prefix was

learned.

Mgmt Connectivity from the advertising node to the

address prefix was learned through Management

protocol.

Other Connectivity from the advertising node to the

address prefix was learned through user-defined

protocol.

Local Connectivity from the advertising node to the

address prefix was learned through Local proto-

col.

Pnni Connectivity from the advertising node to the

address prefix was learned through PNNI proto-

col.Metrics Tag Default: 0

Range: 0–2147483647

Format: Numeric

Indicates the primary routing metric for this

route. The semantics of this metric are deter-

mined by the routing-protocol specified in the

Address Proto value of the route. If this metric

is not used, enter 1 in this field.

[Time Stamp] Default: 00:00:00

Range: N/A

Format: Numeric

(days, hours, minutes,

seconds)

Indicates when connectivity became known to

the local node.

Operational Status Default: Inactive

Range: N/A

Format: Predefined

Indicates whether the reachable address prefix is

operational and is being advertised by this node.

Inactive Indicates that the reachable address prefix is not

operational and is not being advertised by this

node.

Advertised Indicates that the reachable address prefix is

operational and is being advertised by this node.

The system will display this value if the ATM

PNNI 1.0 interface is in service, and at least two

nodes must have connectivity to each other.

Table 6-17. Field Descriptions for the PNNI Route Address Configuration Window (Continued)






255-700-447 6-27




Table 6-18. Commands for the PNNI Metrics Table Window

Command Function

Find.. Searches this table by the values you enter in the Node

Index, Metrics Direction, Metrics Tag, or Metrics Index fields.

Add Metrics Entry Displays the PNNI Metrics Configuration window.Go Back to Previous Screen Redisplays the PNNI Route Address Configuration window.

Figure 6-12. PNNI Metrics Configuration Window

Table 6-19. Commands for the PNNI Metrics Configuration Window

Command Function

Create Metrics Entry (This command is displayed upon initial metrics config-

uration.) Adds the metric entry to the PNNI Metrics

Table.

Apply Configuration Applies the configuration values you set.

Delete Metrics Entry Deletes the metric entry from the PNNI Metrics Table.

Go Back to Previous Screen Displays the PNNI Metrics Table.




6-28 255-700-447


Table 6-20. Field Descriptions for the PNNI Metrics Configuration Window


Metrics Information Panel


Range: 1–400

Format: numeric



Metrics Tag Default: 0

Range: N/A

Format: numeric

Indicates a user-defined number that identifies

this set of traffic parameters. The value in this

field should match the value in the Metrics Tag

field on the PNNI Route Address Configuration

window. A single metrics tag can be assigned to

multiple routes if they all have the same set of

traffic parameters.

A maximum of 20 PNNI metric entries per PNNI

route address entries can be created per interface.

Metrics Direction Default: Incoming

Range: N/AFormat: predefined

alphanumeric

Specifies the direction, with respect to the adver-

tising node, to which these parameters apply(may have multiple service categories).

Incoming Indicates that metrics parameters will be applied

to the incoming direction of data traffic.

Outgoing Indicates that metrics parameters will be applied

to the outgoing direction of data traffic

Metrics Index Default: 0

Range: 0–31

Format: numeric

Indicates an index into a set of parameters associ-

ated with the given tag and direction.

Metrics Class Default: 0

Range: 0–31

Format: numeric

Specifies the service class to which this metric

belongs.

CBR Indicates constant bit rate service class.

rt_VBR Indicates real-time variable bit rate service class.

nrt_VBR Indicates nonreal-time variable bit rate service

class.

ABR Indicates available bit rate service class.

Note: This value is not currently supported.

UBR Indicates unspecified bit rate service class.

Admin Weight Default: 05040

Range: 1–16777215Format: numeric

Indicates the administrative weight from the

advertising node to the remote end of the PNNIentity or to the reachable address or transit net-

work, for the specified service categories.

The lower the value of the administrative weight,

the more preferable this interface.

Max Cell Rate Default: 0xFFFFFFFF

Range: N/A

Format: hexadecimal

Indicates the maximum cell rate, in hexadecimal

notation, for directions and specific service cate-

gories (see the descriptions for the fields Metrics

Direction and Metrics Classes.



255-700-447 6-29


Chapter 6 Configuring ATM PNNIConfiguring an ATM PNNI Route TNS

Configuring an ATM PNNI Route TNS

To configure an ATM PNNI route transit network string, perform the steps in

the following procedure.

Begin

1 On the PNNI Node Configuration window, press the PNNI Route TNS

Configuration command (or press Ctrl+T).

The PNNI Route TNS Table window is displayed (see Figure 6-13). The

values for this window are provided in Table 6-22.

2 Select the Add Route TNS Entry command (or press Ctrl+A).

Available Cell Rate Default: 0xFFFFFFFF

Range: N/A

Format: hexadecimal

Indicates the available bandwidth on this inter-

face, in hexadecimal notation.

Max Cell Tx Delay Default: 0xFFFFFFFF

Range: N/A

Format: hexadecimal

Indicates the length of delay as cells are transmit-

ted from point A to point B, in hexadecimal nota-

tion.

Cell Delay Variation Default: 0xFFFFFFFF

Range: N/A

Format: hexadecimal

Indicates the variation in the cell transit delay, in

hexadecimal notation.

Cell Loss Ratio (0) Default: 0xFFFFFFFF

Range: N/A

Format: hexadecimal

Indicates the cells lost/number of cells sent for

the peak cell rate 0 category, in hexadecimal

notation.

Cell Loss Ratio

(0+1)

Default: 0xFFFFFFFF

Range: N/AFormat: hexadecimal

Indicates the cells lost/number of cells sent for

the peak cell rate 0+1 category, in hexadecimalnotation.

Cell Rate Margin Default: 0xFFFFFFFF

Range: N/A

Format: hexadecimal

Indicates the difference between the effective

bandwidth allocation and the allocation for sus-

tainable cell rate (the safety margin above the

sustainable cell rate), in hexadecimal notation.

Variance Factor Default: 0xFFFFFFFF

Range: N/A

Format: hexadecimal

Indicates the relative measure of the square root

of cell rate margin, normalized by the variance of

some of the cell rates of all existing connections,

in hexadecimal notation.

Gcac CLP Default: ClpEqual0

Range: N/AFormat: predefined

alphanumeric

Indicates the cell loss priority for generic connec-

tion admission control (GCAC).

ClpEqual0 Indicates the GCAC CLP is equal to 0.

ClpEqual0or1 Indicates the GCAC CLP is equal to 0 or 1

Table 6-20. Field Descriptions for the PNNI Metrics Configuration Window (Continued)





6-30 255-700-447


The PNNI Route TNS Configuration window is displayed.


in Table 6-22.

4 After setting all the values on the window, select the Add Route TNS

Entry command (or press Ctrl+A).



5 To see the route entry just added, select the Go Back to Previous

Screen command and press Enter (or press Ctrl+B).

End


Figure 6-13. PNNI Route TNS Table Window

Table 6-21. Commands for the PNNI Route TNS Table Window

Command Function



Top Displays entries at the top of the table.Bottom Displays entries at the bottom of the table.

Total: 0/0 The first number in this field indicates the identification

number of the table entry on the first line of the currently

displayed window. The second number indicates the total

number of table entries.

Find... Searches this table by the values you enter in the Index,

Type, Plan, Id, and TNS Index fields.



255-700-447 6-31



The display fields on this window provide the following information:

Add Route TNS Entry Displays the PNNI Route Address Configuration window.

Go Back to Previous Screen Redisplays the PNNI System-Wide Configuration window.

Table 6-21. Commands for the PNNI Route TNS Table Window (Continued)

Command Function

Table 6-22. Field Descriptions for the PNNI Route TNS Table Window


Total: 0/0 The first number in this field indicates the identification number of

the connection table entry on the first line of the currently displayed

window. The second number indicates the total number of connec-

tion table entries for this connection type.

Note: For more information on the values in the display columns below, see the Field

Description Table for the PNNI Route TNS Configuration window.

Node Index Displays the default five-number value on the PNNI Route TNS Tablewindow. Identifies a logical PNNI entity in the PSAX system.

TNS Type Displays the Transit Network String Type. Indicates the type of net-

work ID of a specified transit network.

TNS Plan Displays the Transit Network String Plan. Indicates the network ID

plan of a specified transit network.

TNS Id Displays the Transit Network String Identifier. Indicates the value of

the Transit Network String identifier.

TNS Index Displays the Transit Network String Index. Indicates the value of the

Transit Network String index.

Figure 6-14. PNNI Route TNS Configuration Window




6-32 255-700-447



Table 6-23. PNNI Route TNS Configuration Window

Command Function

Add Route TNS Entry Displays the PNNI Route Address Configuration window.

Delete Route TNS Entry Deletes the route TNS entry.

Go Back to Previous Screen Redisplays the PNNI Route TNS Table.

Table 6-24. Field Descriptions for the PNNI Route TNS Configuration Window


Route TNS Information Panel

PNNI Node Index Default: 0

Range: 1–400

Format: numeric

Displays the node index identifies a logical PNNI

entity in the PSAX system. Enter the same value

as assigned to the PNNI node (see the Node Index

field on the PNNI Node Configuration window).

TNS Type Default: National-NetworkId

Range: N/A

Format: Predefined

Indicates the Transit Network String type; thetype of network ID of a specfied transit network.

NationalNet-

workId

The National Network ID is being used.

Other A user-defined TNS type is being used.

TNS Plan Default: CarrierId-

Code

Range: N/A

Format: predefined

Indicates the network ID plan of a specified tran-

sit network.

CarrierIdCode The Carrier ID TNS Plan is being used.

Other User-defined.

TNS Id Default: 0

Range: N/A

Format: octets

Indicates the TNS ID.

TNS Index Default: 0

Range: N/A

Format: numeric

Indicates the TNS Index.

Adv Node Id Default: 0

Range: N/A

Format: 11 octets

Indicates the Advertised node ID.

Lower Left Panel

TNS Intf Index Range: N/A

Format: numeric

Indicates the TNS Interface Index



255-700-447 6-33



Adv Port Id Default: 0

Range: 0–50

Format: numeric

Indicates the Advertised port identifier. For an

SVC endpoint, enter the slot, port, and channel).

You can create up to 50 routes manually, to dis-

play in the Route Address table. However, morethan 50 routes can be displayed by the PSAX sys-

tem because route addresses are also learned

dynamically.

Route Type Default: Exterior

Range: N/A

Format: predefined

The route type being used.

Other A user-defined route type.

Exterior A connection from the advertising node to the

address prefix that belongs to an external domain

address.

TNS Scope Default: 0Range: N/A

Format: numeric

Indicates the level of the PNNI hierarchy wherethe connectivity between the advertising node

and the address prefix is located.

VP Capability Default: True

Range: N/A

Format: predefined


(VPCs) can be established between the advertis-


True Indicates that VPCs can be established between

the advertising node and the address prefix.

False Indicates that VPCs cannot be established

between the advertising node and the address

prefix.

Metrics Tag Default: 0

Range: N/A

Format: numeric

Indicates the primary routing metric for this

route and the traffic parameter values for that

apply for the connectivity from the advertising

node to the transit network. There will be one or

more entries in the PNNI Metrics Table whose

value matches the value in this field. The seman-

tics of this metric are determined by the routing-

protocol specified in the Address Proto field value

of the route. If this metric is not used, enter 1 in

this field.

Table 6-24. Field Descriptions for the PNNI Route TNS Configuration Window (Continued)






255-700-447 6-35


Chapter 6 Configuring ATM PNNIViewing ATM PNNI Map TNS Information

Viewing ATM PNNI Map TNS Information

The PNNI Map transit network string (TNS) Table window contains a list of

all reachable transit networks from each node visible to the local node. The

Local Node Index, Advertising Node ID, Advertised Port ID, Transit NetworkType, Transit Network Plan, and Transit Network ID are combined to form an

instance ID for this table. The entire table is read-only, as reachable transit

networks are discovered during dynamic operation of the PNNI protocol,

rather than being configured at a previous point in time.

Begin

1 From the PNNI System-Wide Configuration window, select the PNNI

Map TNS Information command (or press Ctrl+P).

The PNNI Map TNS Table is displayed (see Figure 6-15).


Figure 6-15. PNNI Map TNS Table Window

Table 6-25. Commands for the PNNI Map TNS Table Window

Command Function








6-36 255-700-447


The fields on this window are described in Table 6-26.

2 To View Map TNS Configuration information, select the View Map TNS

Configuration command (or press Ctrl+V).

The PNNI Map TNS Configuration window is displayed.


number of the TNS table entry on the first line of the cur-

rently displayed window. The second number indicates the

total number of TNS table entries.

Find...Index Index Enter the five-digit value for the node to be searched.

Node ID: Enter the 11-octet node address for the node to be searched.

View Map TNS Configuration Displays the PNNI Map TNS Configuration window.


Table 6-25. Commands for the PNNI Map TNS Table Window (Continued)

Command Function

Table 6-26. Field Descriptions for the PNNI Map TNS Table


Map TNS InformationPanel

Note: For more information on the values in the display columns below, see the Display

Description Table for the PNNI Map TNS Configuration window.

Node Index (display

only)

Default: 0

Range: 1–400

Format: numeric

Displays a unique indentifier for this PNNI system

node.

Advertising Node

ID

Default: 0

Range: N/A

Format: hexadecimal

address

Displays the Node ID advertising reachability to

the transit network.

Advertised Port ID Default: 0

Range: N/A

Format: 2 octets

Displays the Port ID used from the advertising

mode to reach the given transit network.



255-700-447 6-37



The PNNI Map TNS Configuration window lists information on six parame-

ters of the selected node address on the Map TNS Table. The table is read-

only, as reachable addresses are discovered during dynamic operation of the

PNNI protocol, not manually configured.



Figure 6-16. PNNI Route TNS Table Window


Command Function

Go Back to Previous Screen Redisplays the PNNI Map TNS Table window.

Table 6-28. Field Descriptions for the PNNI Map TNS Configuration Window


Map TNS Information Panel

[PNNI Node Index] Default: 0

Range: 1–400

Format: numeric

Displays the node index, a logical PNNI entity in the

PSAX system.

[Adv Node Id] Default:

Range:

Format: hexadecimal

Displays the 11-octet advertising node identifier.

This node is advertising reachability to the transit

network.

[Adv Port Id] Default: 0

Range:

Format:

Displays the 10-digit port identifer of the node

advertising to reach the given transit network (see

Annex H, af-pnni-0055.000).



Chapter 6 Configuring ATM PNNIConfiguring a Summary Address

6-38 255-700-447


Configuring a Summary AddressThe PSAX system allows up to 20 PNNI summary addresses. To configure

PNNI summary addresses, perform the following procedure.

Begin

1 On the PNNI System-Wide Configuration window, select the PNNI

Summary Address Configuration command.

The PNNI Summary Address Table window is displayed (see

Figure 6-17).

2 Select the Add Summary Address Entry command.The PNNI Summary Address Configuration window is displayed (see

Figure 6-18)


in Table 6-31.


or press Ctrl+A.

5 Select the Create Summary Address Entry command.

This entry is added to the PNNI Summary Address Table.


bottom of the window.6 Type Ctrl+G to return to the Console Interface Main Menu and save the

configuration.

End

[TNS Type] Default: National-

NetworkId

Range:

Format:

Displays the type of network ID used for the transit

network.

[TNS Plan] Default: CarrierId-

Code

Range:

Format:

Displays the type of network ID Plan that the net-

work has been assigned.

[TNS Id] Default: 0

Range:

Format:

Displays the value of the transit network identifier.

Table 6-28. Field Descriptions for the PNNI Map TNS Configuration Window (Continued)




255-700-447 6-39




Figure 6-17. PNNI Summary Address Table Window

Table 6-29. Commands for the PNNI Summary Address Table Window

Command Function

Find.. Searches this table by the values you enter in the Node Index,

Prefix Length, Summary Type, and Summary Address fields.

Add Metrics Entry Displays the PNNI Summary Address Configuration window.





6-40 255-700-447


.


Figure 6-18. PNNI Summary Address Configuration Window

Table 6-30. Commands for the PNNI Summary Address Configuration Window

Command Function

Create Summary Address

Entry

Adds the route address to the PNNI Summary Address

Table window. This field is displayed only upon initial

summary address configuration.

Apply Configuration Applies the configuration values you set.

Delete Summary Address

Entry

Deletes the route address from the PNNI Summary

Address Table window.

Go Back to Previous Screen Redisplays the PNNI Summary Address Table window.

Table 6-31. Field Descriptions for the PNNI Summary Address Configuration Window



Range: 1–400

Format: numeric



Summary Address Default: 0

Range: 1–20 per node

Format: hexadecimal

Indicates the address prefix of the ATM end sys-

tem. This tells a node how to summarize reach-

ability information. A maximum of 20 PNNI sum-

mary addresses can be created per node.

Address Prefix

Length

Default: 0

Range: 0–152

Format: numeric

Indicates the leading portion of the ATM address.



255-700-447 6-41


Chapter 6 Configuring ATM PNNIViewing ATM PNNI Map Information

Viewing ATM PNNI Map Information

The PNNI Map Table contains attributes necessary to find and analyze the

operation of all links and nodes within the PNNI hierarchy, as seen from the

perspective of a local node. It also provides information for network manag-

ers to map port identifiers, showing the ports and links between the nodes at

both endpoints.

The PNNI Map table is read-only, because the map is generated dynamically

during operation of the PNNI protocol, not manually configured.

To view PNNI map information, perform the following procedure.

Note: PNNI map information is not displayed unless a node has been pre-

viously created.

Summary Address

Type

Default: Internal

Range: N/A

Format: predefined

Indicates whether address is inside or outside a

PNNI routing domain.

Internal Denotes that a link, node, or reachable address is

inside a PNNI routing domain.

Exterior Exterior denotes that a link, node, or reachable

address is outside a PNNI routing domain

Suppress Advertise-

ment

Default: False

Range: N/A

Format: predefined

Determines whether the summary is advertised

within this peer group.

False True indicates you do not want to advertise sum-

mary addresses, enabling the node to reach all

the represented end systems and nodes.

True False indicates you want to advertise addresses

that match the reachable address prefix, regard-

less of scope.

[Summary Address

State]

Default: Advertisin-

gActive

Range: 1–50

Format: predefined

Indicates whether or not the summary is cur-

rently being advertised by the node within the

PSAX system into its peer group. A maximum of

50 routes can be advertised.

AdvertisingActive Indicates the summary address is being advertised

by the node within the PSAX system into its peer

group.

Inactive Indicates the summary address is not being

advertised by the node within the PSAX system

into its peer group.

Table 6-31. Field Descriptions for the PNNI Summary Address Configuration Window (Continued)





6-42 255-700-447


Begin

1 On the PNNI System-Wide Configuration window, select the PNNI Map

Information command.

The PNNI Map Table window is displayed (see Figure 6-19).

2 Select the node for which you want to view information.

The PNNI Map Information window is displayed (see Figure 6-20).

The values for the fields in this window are described in Table 6-34.

3 To view the Metrics Table window, select the View Metrics Tables com-

mand.

The Metrics Table is displayed.

4 To return to the Map Table window, select the Go Back to Previous

Screen command and press Enter.

The Map Table window is displayed (see Figure 6-19).

End


Figure 6-19. PNNI Map Table Window

Table 6-32. Commands for the PNNI Map Table Window

Command Function

Find... Searches this table by the values you enter in the Node

Index, Org. Port Id, Map Index, or Org. Node Id fields.




255-700-447 6-43



The PNNI Map Table window displays the Node Index, Originating Node

Identifier, Org Port ID (originating port identifier), and Map Index fields for

various maps.

The Originating Node Identifier is the node identifier of the node whose con-

nectivity within itself or to other nodes is being described.

The Org Port Id is the port identifier of the port as assigned by the originatingnode, to which the port is attached.

The Map Index is an index into the set of link and nodal connectivity associ-

ated with the originating node and port. This index is needed since multiple

entries for nodal connectivity from a specific node and port pair can exist, in

addition to any entry for a horizontal link or uplink.


Figure 6-20. PNNI Map Information Window

Table 6-33. PNNI Map Information Window

Command Function

View Metrics Tables Displays the PNNI Metrics Configuration window.

Go Back to Previous Screen Displays the PNNI System-Wide Configuration window.




6-44 255-700-447


Table 6-34. Field Descriptions for the PNNI Map Information Window


[Node Index] Default: N/A

Range: 1–400

Format: Numeric


entity in the PSAX system.

[Org. Node Id] Default: N/A

Range: N/A

Format: hexadecimal

Displays the Node identifier of the node originat-

ing connectivity within itself or to other nodes.

[Remote Node Id] Default: N/A

Range: N/A

Format: hexadecimal

Displays the Node identifier at the other end of

the link from the originating node. A value of all

zeroes means the node identifier is unknown.

[Peer Group Id] Default: N/A

Range: N/A

Format: Numeric

Displays the Peer group identifier of the originat-

ing node and its peers.

[Org. Port Id] Default: N/A

Range: N/A

Format: Numeric

Displays the Port identifier of the port, as assigned

by the originating node, to which the port isattached.

[Remote Port Id] Default: N/A

Range: N/A

Format: Numeric

Displays the Port identifier of the port at the

remote end of the link as assigned by the remote

node. A value of all zeroes means the port identi-

fier is unknown.

[Aggregate Token] Default: N/A

Range: N/A

Format: Numeric

Displays which links to a given neighbor node are

to be aggregated and advertised as a single logical

link.

[Ptse Identifier] Default: N/A

Range: N/A

Format: Numeric

Displays a PTSE identifier describing this link or

node.

[Map Index] Default: N/A

Range: N/A

Format: Numeric

Displays an index into the set of link and nodal

connectivity associated with the originating node

and port. This index is needed since there may be

multiple entries for nodal connectivity from a

specific node and port pair, in addition to any

entry for a horizontal link or uplink.

[Map Type] Default: Horizontal

Link

Range: N/A

Format: Predefined

Displays the type of PNNI entity.



255-700-447 6-45


Chapter 6 Configuring ATM PNNIViewing ATM PNNI Map Node Information

Viewing ATM PNNI Map Node InformationPerform the following procedure to configure the PNNI map node informa-

tion.

Begin




2 Select the PNNI System-Wide Configuration option and press Enter (or

press Ctrl+N).

The PNNI System-Wide Configuration window is displayed.

3 Select the PNNI Map Node Information command.

The PNNI Map Node Table window is displayed (see Figure 6-21).

4 Select an entry on the table and press Enter.

The PNNI Map Node Information window is displayed. The descriptions

of the display-only fields on this window are provided in Table 6-38.

End

[VP Capability] Default: True

Range: N/A

Format: Predefined


(VPCs) can be established across this PNNI entity.

True VPCs can be established across this PNNI entity.

False VPCs cannot be established across this PNNI

entity.

[Metrics Tag] Default: N/A

Range: N/A

Format: Numeric

Associates a set of traffic parameters that are

always advertised together. This value is used as

an index into the PNNI Metrics Table. A value of

zero indicates no metrics are associated with this

PNNI entity.

Table 6-34. Field Descriptions for the PNNI Map Information Window (Continued)





6-46 255-700-447


The PNNI Map Node Table contains a list of nodes as seen from the per-

spective of a local node, and all information learned by the local node

from nodal information PNNI topology state elements (PTSEs). This table

is read-only, because the map is generated dynamically during operation

of the PNNI protocol, not manually configured.


The display-only fields on this window have the following values:

Figure 6-21. PNNI Map Node Table Window

Table 6-35. Commands for the PNNI Map Node Table Window

Command Function


Index or Map Node Id fields.




255-700-447 6-47



The PNNI Map Node Information window is read-only, as the update is

generated dynamically during operation of the PNNI protocol, not manu-

ally configured.


Table 6-36. Field Descriptions for the PNNI Map Node Table Window

Field Name Field Value Description

Total: 0/0 Default:

Range:

Format:

The first number in this field indicates the identifica-

tion number of the connection table entry on the first

line of the currently displayed window. The second

number indicates the total number of connection tableentries for this connection type.

Node ID Default:

Range:

Format:

Displays the default node identifier (up to 5 digits) on

the Node Table window. The default node identifier of

a logical PNNI entity in the PSAX system.

PNNI Map Node Id Default:

Range:

Format:

Displays the 11-octet PNNI map node identifier.

Figure 6-22. PNNI Map Node Information Window


Command Function





6-48 255-700-447


Table 6-38. Field Descriptions for the PNNI Map Node Information Window


Node Index

(display only)

Default: 0

Range: 1–400

Format: numeric



Map Node ID

(display only)

Default: 0

Range: N/A

Format: hexadecimal

Displays the node whose nodal information is

being described.

Peer Group ID

(display only)

Default: 0

Range: N/A

Format: hexadecimal

Indicates the first 12 bytes (default) of the ATM

address. This value is the combination of the ATM

address and the node level. This value is gener-

ated and displayed by the system automatically.

For more information, see Section 5.3.3, Node

Identifiers, in the ATM Forum Specification, Pri-

vate Network-Network Interface (PNNI 1.0) Specifica-

tion Version 1.0, af-pnni-0055.000.

ATM Address(display only)

Default: 0Range: N/A

Format: hexadecimal

Displays the ATM end system address of the orig-inating node.

Restricted Transit

(display only)

Default: True

Range: T/F

Format: predefined

Indicates whether the originating node is

restricted to only allow support of SVCs originat-

ing or terminating at this node. This attribute

reflects the setting of the restricted transit bit

received in the nodal information PTSE from the

originating node.

True Indicates that the transit capabilities are

restricted. Often, transit connections are not

allowed. A restricted transit node is a node to be

used to transmit by a call in restricted circum-

stances. It is free from such restrictions when it is

used to originate or terminate a call.

False Indicates that transit connections are allowed.

Complex Rep

(display only)

Default: False

Range: T/F

Format: predefined

Indicates the complex node representation, a col-

lection of nodal state parameters that provide

detailed state information associated with the

logical node.

False Indicates that the originating node does not use

the complex node representation.

True Indicates that the originating node uses the com-

plex node representation. If the value is True,the spokes and bypasses that make up the com-

plex node representation should be found in the

PNNI Map Address Table. This attribute reflects

the setting of the nodal representation bit

received in the nodal information PTSE from the

originating node.



255-700-447 6-49



Restricted Branch-

ing

(display only)

Default: False

Range: T/F

Format: predefined

Displays whether the originating node is able to

support additional branches. This attribute

reflects the setting of the restricted branching bit

received in the nodal information PTSE from theoriginating node.

False Indicates that additional branches are supported.

True Indicates that restricted branching is supported.

Database Overload

(display only)

Default: False

Range: T/F

Format: predefined

Indicates whether the originating node’s topology

database is currently overloaded. This attribute

has the same value as the non-transit for PGL

election bit in the nodal information group origi-

nated by this node.

False Indicates that the originating node’s topology

database is not currently overloaded.

True Indicates that the originating node’s topologydatabase is currently overloaded.

I Am Leader

(display only)

Default: False

Range: T/F

Format: predefined

Indicates whether the originating node claims to

be the peer group leader (PGL) of its peer group.

This attribute reflects the setting of the "I Am

Leader" bit received in the nodal information

PTSE from the originating node.

False Indicates the originating node does not claim to

be the PGL of its peer group.

True Indicates that the originating node claims to be

PGL.

Leadership Priority Default: 0

Range: N/A

Format: numeric

Indicates the node ranking in a peer group for the

peer group leader position the next time a PGL is

needed.

Preferred Pgl

(display only)

Default: 0

Range: N/A

Format: hexadecimal

Displays the node that the originating node

believes should be or is peer group leader (PGL)

of its peer group. If the originating node has not

chosen a preferred PGL, this value is set to 0.

Parent Node ID

(display only)

Default: 0

Range: N/A

Format: hexadecimal

Displays the node ID of the parent logical group

node (LGN) when the originating node is a peer

group leader. If the originating node is not peer

group leader of its peer group, and the I Am

Leader field is set to False, then this value is set

to 0.

Table 6-38. Field Descriptions for the PNNI Map Node Information Window (Continued)




Chapter 6 Configuring ATM PNNIViewing ATM PNNI Map Address Information

6-50 255-700-447


Viewing ATM PNNI Map Address Information

Begin


Map Address Information command and press Enter.

The PNNI Map Address Table window is displayed (see Figure 6-23).

2 To access information on an entry on the table, select an entry.

The PNNI Map Address Information window is displayed.

The PNNI Map Address Table contains a list of all reachable addresses

from each node visible to the local node. The table is read-only, as reach-

able addresses are discovered during dynamic operation of the PNNI pro-

tocol, not manually configured.

End

Parent ATM

Address

(display only)

Default: 0

Range: N/A

Format: hexadecimal

Displays the ATM address of the parent LGN

when the originating node is a peer group leader.

If the originating node is not peer group leader of

its peer group, and the I Am Leader field is set toFalse, this value is set to 0.

Parent Peer Group

ID

(display only)

Default: 0

Range: user-defined

Format: hexadecimal

Displays the node’s parent peer group ID when

the originating node is a peer group leader. If the

originating node is not peer group leader of its

peer group, and the I Am Leader field is set to

False, this value is set to 0.

Parent Pgl Node ID

(display only)

Default: 0

Range: user-defined

Format: hexadecimal

Displays the node elected as peer group leader of

the parent peer group when the originating node

is a peer group leader. If the originating node is

not peer group leader of its peer group, and the I

Am Leader field is set to False, this value is set to

0.

Table 6-38. Field Descriptions for the PNNI Map Node Information Window (Continued)




255-700-447 6-51




The descriptions for the display-only fields on this window are provided in

Table 6-42:

Figure 6-23. PNNI Map Address Table Window

Table 6-39. Commands for the PNNI Map Address Table Window

Command Function


Index, Advertised Node Id, Advertised Port Id, and Address

Index fields.


Table 6-40. Field Descriptions for the PNNI Map Address Table Window



number of the connection table entry on the first line of the

currently displayed window. The second number indicates

the total number of connection table entries for this con-

nection type.

Node index Displays default five-digit value on the Node Table window.The default node identifier of a logical PNNI entity in the

PSAX system.

Advertising Node Identifier Displays the hexadecimal address (11 octets).

Advertising Port Id Displays the port identifier of the advertising node.

Addr. Index Displays the address index (up to 5 digits).




6-52 255-700-447


The descriptions for the display-only fields on this window are provided in

Table 6-42. The PNNI Map Address Information window is read-only, as

reachable addresses are discovered during dynamic operation of the PNNI

protocol, not manually configured


Figure 6-24. PNNI Map Address Information Window


Command Function


Table 6-42. Field Descriptions for the PNNI Map Address Entry Window



Range: 1–400

Format: numeric



[Adv. Node Id] Default: N/A

Range: N/A

Format: numeric

Displays the node ID of a node advertising reach-

ability to the address prefix.

[Adv. Port Id] Default: N/A

Range: N/A

Format: numeric

Displays the port identifier the advertising node

uses to reach the given address prefix.



255-700-447 6-53


Chapter 6 Configuring ATM PNNIViewing the ATM PNNI Link Table

Viewing the ATM PNNI Link Table

The PNNI Link Table window contains the attributes necessary to describethe operation of logical links attached to the PSAX system and the relation-

ship with the neighbor nodes on the other end of the links. Links are

attached to a specific node within the PSAX system. Links represent horizon-

tal links between the lowest level of neighboring peers, outside links, uplinks,

or horizontal links to or from logical group nodes (LGNs). A maximum of

100 PNNI links can be created per interface.

The PNNI Link Table window is read-only because the information in the

PNNI link table is generated dynamically by the PNNI protocol, not manually

configured. For more information, see the ATM Forum Specification, Private

Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni-0055.000,

Section 5.6.

The PSAX 2300 allows up to 100 PNNI links per interface. To view PNNI

links, perform the following procedure.

Begin


Link Information command.

The PNNI Link Table window is displayed (see Figure 6-25).

2 If a node has been created, select the node for which you want to view

information and press Enter.

The PNNI Link Information window is displayed (see Figure 6-26).

3 Descriptions for the display-only fields on this window are provided in

Table 6-45.

4 To return to the PNNI Link Table window, select the Go Back to Previ-

ous Screen command.

[Address Index] Default: N/A

Range: N/A

Format: numeric

Displays an arbitrary index generated by the CPU

that is used to number all of the map addresses

advertised by the specified node.

[Map Address] Default: N/A

Range: N/A

Format: numeric

Displays the ATM end system address prefix.

[Prefix Length] Default: N/A

Range: N/A

Format: numeric

Displays the prefix length to be applied to the

ATM end system address prefix.

Table 6-42. Field Descriptions for the PNNI Map Address Entry Window (Continued)





6-54 255-700-447


The PNNI Link Table window is displayed (see Figure 6-25).

End

The PNNI Link Table window displays the node index and link port identifier

for various PNNI links.

The PNNI Link Port Id field is the port identifier of the link as selected by the

local node. This value has meaning only within the context of the node to

which the port is attached.


Figure 6-25. PNNI Link Table Window

Table 6-43. Commands for the PNNI Link Table Window

Command Function


Index or the PNNI Link Port Id fields.




255-700-447 6-55



The command in this window has the following function:

Figure 6-26. PNNI Link Information Window

Table 6-44. Commands for the PNNI Link Information Window

Command Function


Table 6-45. Field Descriptions for the PNNI Link Configuration WindowField Name Field Values Description


Range: 1–400

Format: numeric

Displays the node index that identifies a logical PNNI


[Link Port Id] Default: N/A

Range: N/A

Format: numeric

Displays the port identifier of the link selected by the local

node. This value has meaning only within the context of

the node to which the port is attached.




6-56 255-700-447


[Link Version] Default: Version1p

oint0

Range: N/A

Format: predefinedalphanumeric

Displays the version of PNNI routing protocol used to

exchange information over this link for horizontal and

outside links between lowest-level nodes and for links of

unknown type.

Version1point0 Indicates PNNI Version 1.0 is being used.

Unknown Displays the communication state with the neighbor.

• If the node has not yet been established, the version is

set to Unknown.

• For uplinks (where the port ID is not also used for the

underlying outside link) or links to or from LGNs, the

version is set to Unknown.

[Link Type] Default: Low-

estLevelHorizon-

talLinkRange: network-

dependent

Format: predefined

alphanumeric

Displays the type of link being described.

Unknown Indicates that the link type is unknown.

LowestLevelHori-

zontalLink

Indicates that this link is the logical link between lowest

nodes in the same peer group.

HorizontalLinkTo-

FromLgn

Indicates that this link is the logical link between logical

group nodes (LGNs) in the same peer group.

LowestLevelOut-

sideLink

Indicates that this link is the logical link between the low-

est nodes in the same peer group.Uplink Indicates that connectivity exists from a border node to

an upnode; that is, this link is the uplink to a higher level

node in the hierarchy.

OutsideLinkAnd-

Uplink

Indicates that this link is the logical link between two bor-

der nodes, and the border nodes represent an upnode;

that is, this link is the outside link to another network

and uplink.

[Link Hello

State]

Default: N/A

Range: N/A

Format: Predefined

Displays one of the possible conditions that characterize

Hello types and the node states that the Hellos originated

from.

Down Indicates the initial state of the Hello Finite State Machine(FSM), a table displaying what the software does after

receiving new information. This state is also reached

when lower-level protocols have indicated that the link is

not usable. No PNNI routing packets will be sent or

received over such a link.

Table 6-45. Field Descriptions for the PNNI Link Configuration Window (Continued)




255-700-447 6-57



Attempt Indicates either no Hellos or Hellos with mismatch infor-

mation have been received recently from the neighbor. In

this state, attempts are made to contact the neighbor by

periodically sending the neighbor Hellos with the periodHello Interval.

OneWayInside Indicates whether Hellos have recently been received

from the neighbor and both nodes are members of the

same peer group, but the remote node ID and remote

port ID in the neighbor’s Hellos were set to 0.

TwoWayInside Indicates whether Hellos have recently been received

from the neighbor and whether both nodes are members

of the same peer group, and including the correct remote

node ID and remote port ID fields. When this state is

reached, it indicates that bidirectional communication

over this link between the two nodes has been made.

Database summary packets, PTSE Request packets, PTSPs,and PTSE acknowledgment packets can only be transmit-

ted over links that are in the TwoWayInside state. For

physical links and VPCs, only those links that are in the

TwoWayInside state can be advertised by this node in

PTSEs as horizontal links.

OneWayOutside Indicates whether Hellos have recently been received

from the neighbor and that the neighbor node belongs to

a different peer group, but the remote node ID and

remote port ID in the neighbor’s Hellos were set to 0. In

this state and in the TwoWayOutside state, the node

searches for a common peer group that contains both this

node and the neighbor node.

TwoWayOutside Indicates whether Hellos have recently been received

from the neighbor, whose node belongs to a different

peer group, and including the correct remote node ID and

remote port ID fields, but with a nodal hierarchy list that

does not include any common peer group. In this state

and in the OneWayOutside state, the node searches for

a common peer group that contains both this node and

the neighbor node.

CommonOutside Indicates whether a common level of the routing hierar-

chy has been found, in addition to achieving full bidirec-

tional communication between the two nodes. Links that

have reached the CommonOutside state can be adver-

tised in PTSEs as uplinks to the upnode.

[Remote Node

Id]

Default: N/A

Range: N/A

Format: hexadecimal

Displays the node identifier of the node at the remote end

of the link..






6-58 255-700-447


[Remote Port Id] Default: N/A

Range: N/A

Format: numeric

Displays the port identifier of the port at the remote end

of the link as assigned by the remote node. If Out-

sideLinkAndUplink is displayed in the Link Type field,

this is the port identifier assigned by the lowest-levelneighbor node to identify the outside link. If Unknown

is displayed in this field, or if Uplink is displayed in the Link Type field, the remote port ID is set to 0.

[Derived Agg.

Token]

Default: N/A

Range: N/A

Format: numeric

Displays a PNNI aggregation token, used to determine

which links to a given neighbor node are to be aggregated

and advertised as a single logical link.

[Upnode Id] Default: N/A

Range: N/A

Format: numeric

Displays the node identifier of the upnode (the neighbor

node’s identity within the common peer group) for out-

side links and uplinks. When the upnode, horizontal

links, or link type is not yet known, this field is set to 0.

[Upnode ATM

Address]

Default: N/A

Range: N/A

Format: hexadecimal

Displays the ATM end system address used to establish

connections to the upnode for outside links and uplinks.

When the upnode, horizontal links, or link type is not yet

known, this field is set to 0.

[Common Peer

Gp Id]

Default: N/A

Range: N/A

Format: numeric

Displays the common peer group identifier. For outside

links and uplinks, this attribute contains the peer group

identifier of the lowest level common peer group in the

ancestry of the neighboring node and the node within the

PSAX system. This field value is determined by the Hello

exchange of hierarchical information that occurs between

the two lowest-level border nodes. When the common

peer group, horizontal links, or link type is not yet

known, this field is set to 0.

[Svcc Rcc Index] Default: N/A

Range: N/A

Format: numeric

Displays the value of this object, which identifies the

switched virtual channel connection (SVCC)-based rout-

ing control channel (RCC) for which the entry contains

management information.

Rcv Hellos

(display only)

Default: N/A

Range: N/A

Format: numeric

Indicates the number of hello packets received over this

link for horizontal and outside links between lowest-level

nodes and for links of unknown type. If Horizon-

talLinkToFromLgn or Uplink is displayed in the Link

Type field, this field is set to 0.

[Transmit Hellos] Default: N/A

Range: N/A

Format: numeric

Displays the number of hello packets transmitted over

this link for horizontal and outside links between lowest-

level nodes and for links of unknown type. If Horizon-

talLinkToFromLgn or Uplink is displayed in the Link

Type field, this field is set to 0.





255-700-447 6-59


Chapter 6 Configuring ATM PNNIViewing ATM PNNI SVCC RCC Information

Viewing ATM PNNI SVCC RCC Information

Begin

1 On the Console Interface Main Menu, select the Site-Specific Configu-

ration option and press Enter (or press Ctrl+P).


2 Select the PNNI System-Wide Configuration option and press Enter (or

press Ctrl+N).


3 Select the PNNI SVCC RCC Information command (or press Ctrl+V).

The PNNI Svcc Rcc Table is displayed (see Figure 6-21).

4 Access configuration information on any entry on the SvccRcc Table by

selecting it and pressing Enter.

The PNNI SvccRcc Information window is displayed (see Figure 6-28).End


Figure 6-27. PNNI SvccRcc Table Window

Table 6-46. Commands for the PNNI SvccRcc Table Window

Command Function







6-60 255-700-447


The display fields on this window have the following values:



number of the SvccRcc Table entry on the first line of the cur-

rently displayed window. The second number indicates the

total number of SvccRcc Table entries.

Find...Node Index Enter the five-digit value for the node to be searched.

PNNI SvccRcc Index Enter the single-octet node adress to be searched.


Table 6-46. Commands for the PNNI SvccRcc Table Window (Continued)

Command Function

Table 6-47. Field Descriptions for the PNNI SVCC RCC Table Window


Node Index (display

only)

The node index identifies a logical PNNI entity in the PSAX system.

PNNI Svcc Rcc Index The interface from which the SVCC-based RCC leaves the switching

system. If the RCC has not been established, then the attribute takes

the value of zero.

VPI The VPI used at the interface from which the SVCC-based RCC

leaves the switching system. If the RCC has not been established,

then the attribute takes the value of zero.

VCI The VCI used at the interface from which the SVCC-based RCC

leaves the switching system. If the RCC has not been established,

then the attribute takes the value of zero.



255-700-447 6-61



Table 6-48 describes the commands on this window.

Table 6-49 describes the display fields on this window.:

Figure 6-28. PNNI SVCC RCC Information Window

Table 6-48. Commands for the PNNI SVCC RCC Information Window

Command Function

ATM Security Statistics Displays the ATM PNNI SVCC RCC Security Statistics win-

dow

Go Back to Previous Screen Redisplays the PNNI SvccRcc Table window.

Table 6-49. Field Descriptions for the PNNI SVCC RCC Information Window



Range: 1–400

Format: Numeric



[Svcc Rcc Index] Default: 0

Range: 1–65535

Format: Numeric

Displays the 5-digit switched virtual channel con-

nection routing control channel (SvccRcc) index

number.

[Svcc Rcc Version] Default: Version1poi

nt0

Range: N/A

Format: Predefined

Displays the PNNI version 1.0 routing protocol

that is used to exchange information with the

neighbor node.



Chapter 6 Configuring ATM PNNIViewing the ATM PNNI Neighbor Peer Table

6-62 255-700-447


Viewing the ATM PNNI Neighbor Peer Table

The PNNI Neighbor Peer Table window contains all the attributes necessaryto describe the relationship a node in the PSAX system has with a neighbor-

ing node within the same peer group. The PNNI Neighbor Peer Table window

is read-only because neighboring peers are generated dynamically by the

PNNI protocol, not manually configured. For more information, see the ATM

Forum Specification, Private Network-Network Interface (PNNI 1.0) Specification

Version 1.0, af-pnni-0055.000, Sections 5.7 and 5.8.

To view PNNI neighbor peers, perform the following procedure.

[Svcc Hello State] Default: TwoWayIn-

side

Range: N/A

Format: Predefined

Displays the state of the Hello protocol exchange

over the SVCC-based RCC.

[Remote Node Id] Default: 0

Range: N/A

Format: 11-octet

remote node address

identifier

Displays the remote node where the SVCC-based

RCC terminates.

[Remote ATM

Address]

Default: 0

Range: N/A

Format: 10-octet

address of remote

ATM device

Displays the ATM end system address where the

SVCC establishment was attempted.

[SvccRcc If Index] Default: 0

Range: N/A

Format: Numeric

Displays the interface from which the SVCC- based RCC leaves the PSAX system. If the SVCC-

based RCC has not been established, the default

value is displayed.

[Rcv Hellos] Default: 0

Range: N/A

Format: Numeric

Displays the number of received Hello packets

over this SVCC-based RCC.

[Transmit Hello] Default: 0

Range: N/A

Format: Numeric

Displays the number of transmitted Hello packets

over this VCC-based RCC.

[Vpi] Default: 0

Range: N/A

Format: Numeric

Displays the VPI used at the interface from which

the SVCC-based RCC leaves the PSAX system. Ifthe RCC has not been established, the default

value is displayed.

[Vci] Default: 0

Range: N/A

Format: Numeric

Displays the VCI used at the interface from which

the SVCC-based RCC leaves the PSAX system. If

the RCC has not been established, the default

value is displayed.

Table 6-49. Field Descriptions for the PNNI SVCC RCC Information Window (Continued)




255-700-447 6-63



Begin




2 Select the PNNI System-Wide Configuration option.


3 Select the PNNI Neighbor Peer Information command and press

Enter.

The PNNI Neighbor Peer Table window is displayed (see Figure 6-29).

4 If a node has been created, select the node for which you want to view

information and press Enter.

The PNNI Neighbor Peer Information window is displayed (see

Figure 6-30). The values for the fields in this window are described in

Table 6-52.

5 To return to the Link Table window, select the Go Back to Previous

Screen command.

The Neighbor Peer Table is displayed (see Figure 6-29).

End

The PNNI Neighbor Peer Table window displays the node index and neighbor

peer remote node index for various neighbor peers.

Figure 6-29. PNNI Neighbor Peer Table Window




6-64 255-700-447


The PNNI Neighbor Peer Remote Node Id field is the node identifier of the

neighboring peer node.


The command in this window has the following function:

Table 6-50. Commands for the PNNI Neighbor Peer Table Window

Command Function

Find... Searches this table by the values you enter in the Node

Index or Rem. Node Id fields.


Figure 6-30. PNNI Neighbor Peer Information Window

Table 6-51. Command for the PNNI Neighbor Peer Information Window

Command Function




255-700-447 6-65



Table 6-52. Field Descriptions for the PNNI Neighbor Peer Configuration Window



Range: 1–400

Format: numeric



[NbrPeer Rem Node

Id]

Default: N/A

Range:

Format: numeric

Displays the Node identifier of the neighboring

peer node.

[NbrPeer State] Default: Npdown

Range: N/A

Format: predefined

alphanumeric

Displays the state of this node's neighboring peer

state machine associated with the neighbor peer

remote node ID.

Npdown The initial state of a neighboring peer FSM. This

state indicates that there are no active links (that

is, in Hello state 2-WayInside) to the neighboring

peer. In this state, there are no adjacencies associ-

ated with the neighboring peer.

Negotiating Indicates that this neighbor peer is currently in

the first step in creating an adjacency between

the two neighboring peers. The goal of this step is

to decide which node is the master, and to decide

upon the initial Database Summary (DS)

sequence number.

Exchanging Indicates that the node is in the exchanging state,

in which the node describes its topology database

by sending Database Summary packets to the

neighboring peer. As a result of processing DS

packets, the node can request the required PTSEs.

Loading Indicates that the node is in the loading state, in

which a full sequence of DS packets has been

exchanged with the neighboring peer, the

required PTSEs are requested, and at least one

has not yet been received.

Full Indicates that the node is in the full state, in

which the node node has received all PTSEs

known to be available from the neighboring peer.

Links to the neighboring peer can now be adver-

tised in PTSEs.

[NbrPeer Svcc Rcc

Index]

Default: N/A

Range: N/AFormat: numeric

Displays the switched virtual channel connection

(SVCC)-based routing control channel (RCC) being used to communicate with the neighboring

peer if one exists. If both the local node and the

neighboring peer node are lowest-level nodes,

this field is set to 0.



Chapter 6 Configuring ATM PNNIViewing the ATM PNNI Neighbor Peer Port Table

6-66 255-700-447


Viewing the ATM PNNI Neighbor Peer Port Table

Begin

1 On the Console Interface Main Menu, select the Site-Specific Configu-

ration option or press Ctrl+P.


2 Select the PNNI System-Wide Configuration option or press Ctrl+N.

[NbrPeer Port

Count]

Default: N/A

Range: N/A

Format: numeric

Displays a count of the total number of ports that

connect to the neighboring peer. If the neighbor-

ing peer only communicates via an SVCC-based

RCC, the value of this field is set to zero. Other-wise it is set to the total number of ports to the

neighboring peer in the Hello state two-way

inside.

[NbrPeer Rcv

DbSums)

Default: N/A

Range: N/A

Format: numeric

Displays a count of the number of database sum-

mary packets received from the neighboring peer.

[NbrPeer Xmt

DbSums)

Default: N/A

Range: N/A

Format: numeric

Displays a count of the number of database sum-

mary packets transmitted to the neighboring

peer.

[NbrPeer Rcv Ptsps] Default: N/A


Displays a count of the number of PNNI topology

state packets (PTSPs) received from the neighbor-ing peer.

[NbrPeer Xmt

Ptsps]

Default: N/A

Range: N/A

Format: numeric

Displays a count of the number of PTSPs retrans-

mitted to the neighboring peer.

[NbrPeer Rcv Ptse

Req]

Default: N/A

Range: N/A

Format: numeric

Displays a count of the number of PNNI topology

state element (PTSE) request packets received

from the neighboring peer.

[NbrPeer Xmt Ptse

Req]

Default: N/A

Range: N/A

Format: numeric

Displays a count of the number of PTSE request

packets transmitted to the neighboring peer.

[NbrPeer Rcv Ptse

Ack]

Default: N/A

Range: N/A

Format: numeric

Displays a count of the number of PTSE acknowl-

edgement packets received from the neighboring

peer.

[NbrPeer Xmt Ptse

Ack]

Default: N/A

Range: N/A

Format: numeric

Displays a count of the number of PTSE acknowl-

edgement packets transmitted to the neighboring

peer.

Table 6-52. Field Descriptions for the PNNI Neighbor Peer Configuration Window (Continued)




255-700-447 6-67


Chapter 6 Configuring ATM PNNIViewing the ATM PNNI Neighbor Peer Port Table


3 Select the PNNI Neighbor Peer Port Information command (or press

Ctrl+I).

The PNNI Neighbor Peer Port Table is displayed (see Figure 6-31).

4 Access configuration information on any entry on the Neighbor Peer PortTable by a search using the Find command or by selecting an entry on

the table and and pressing Enter.

End

The PNNI Neighbor Peer Port table shows all ports in hello state two-way

inside to a given neighboring peer node. This table is only used for low-

est-level nodes. For more information, see the ATM Forum Specification,

Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni-

0055.000, Section 5.7.1 “Port ID List.”


Figure 6-31. PNNI Neighbor Peer Port Table Window

Table 6-53. Commands for the PNNI Neighbor Peer Port Table Window

Command Function







Chapter 6 Configuring ATM PNNIViewing ATM PNNI PTSE Information

6-68 255-700-447


The display fields on this window have the following values as described

in Table 6-54:

Viewing ATM PNNI PTSE Information

A PNNI topology state element (PTSE) is a collection of PNNI information set

among all logical nodes within a peer group. The PNNI PTSE table contains

the attributes that describe the most recent instances of PTSEs in a node’s

topology database. For more information, see the ATM Forum Specification,

Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni-

0055.000, Section 5.8.2. The PNNI PTSE Table window displays PTSE entries

currently residing in the PSAX system.

To view PTSE information, perform the following procedure.

Begin


PTSE Information command or press Ctrl+E.

Total: 0/0 The first number in this field indicates the identification number

of the peer port table entry on the first line of the currently dis-

played window. The second number indicates the total number

of peer port table entries.

Find...Node Index Enter the five-digit value for the node to be searched.

Port Id Enter the 10-digit port ID to be searched.

Rmt. Node Id: Enter the 11-octet ID address of the remote node to be searched.


Table 6-53. Commands for the PNNI Neighbor Peer Port Table Window (Continued)

Command Function

Table 6-54. Field Descriptions for the PNNI Neighbor Peer Port Table Window


Node Index

(display only)

Default: N/A

Range: 1–400

Format: numeric



PNNI Neighbor Peer

Port Remote Node

Id

Default: N/A

Range: N/A

Format: hexadecimal

Displays the Node identifier of the neighboring

peer node.

Port ID

(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays a port identifier to the neighboring peer

that is in the hello state two-way inside.

Flood Stat.

(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays whether the port is being used for trans-

mission of flooding and database synchronization

information to the neighboring peer.



255-700-447 6-69



The PNNI PTSE Table is displayed (see Figure 6-32). The fields in the

PNNI PTSE Table window are provided in Table 6-56.

2 To view information about an entry on this table, select an entry.

The PNNI PTSE Information window is displayed (see Figure 6-33).

Descriptions for the fields in the PNNI PTSE Information window are


End

The commands on this table perform the following functions:

Figure 6-32. PNNI PTSE Table Window

Table 6-55. Commands for the PNNI PTSE Table Window

Command Function






number of the table entry on the first line of the currentlydisplayed window. The second number indicates the total

number of table entries.

Find...Node Index Enter the five-digit ID for the node to be searched.

Ptse Id Enter the 10-digit PTSE ID to be searched.




6-70 255-700-447



Org. Node Id: Enter the 11-octet organizational node ID address to be

searched.


Table 6-55. Commands for the PNNI PTSE Table Window (Continued)

Command Function

Table 6-56. Field Descriptions for the PNNI PTSE Table Window



number of the table entry on the first line of the cur-

rently displayed window. The second number indicates

the total number of table entries.

Node Index Displays the 5-digit node index of the table entries.

PNNI PTSE Originating

Node Id

Displays the 11-octet PNNI PTSE Originating Node ID.

PTSE Id ID of the PTSE.

Figure 6-33. PNNI PTSE Information Window


Command Function




255-700-447 6-71



Table 6-58. Field Descriptions for the PNNI PTSE Information Window


Node Index

(display only)

Default: N/A

Range: 1–400

Format: Numeric



Originating Node

ID

(display only)

Default: N/A

Range: N/A

Format: Hexadecimal

Displays the 20-octet node identifier of the node

that originated the PTSE.

Default: N/A

Range: N/A

Format: Numeric

Displays the value of the PTSE identifier assigned

to the PTSE by its originator.

Type

(display only)

Default: Other

Range: N/A

Format: Predefined

Describes the architecture parameters set

selected.

Other User defined.

NodalState Param-

eters

Indicates that the nodal state parameter informa-

tion is contained in the PTSE. A nodal state

parameter provides information that captures an

aspect or property of a node.

Nodal Information Indicates that the nodal information is contained

in the PTSE. Nodal information describes the

node (including resource availability information,

and not including reachability information). It

specifically includes:

• ATM end system address of the node

• Leadership priority

• Node information flags

• Preferred peer group leader node ID

• Next higher-level binding information

(included if this node is Peer Group Leader

Internal Reachable

Addresses

An internal reachable address is an address of a

destination that is directly attached to the logical

node that advertises the address.

Exterior Reachable

Addresses

An exterior reachable address is an address that

can be reached through a PNNI routing domain

but is not located in that PNNI routing domain.

HorizontalLinks A horizontal link is between nodes in the same

peer group.

Uplinks An uplink is connectivity from a border node to

an upnode at a higher level in the PNNI hierar-

chy.



Chapter 6 Configuring ATM PNNIViewing ATM PNNI System Statistics

6-72 255-700-447


Viewing ATM PNNI System Statistics

To view PNNI system statistics, perform the following procedure.

Begin

1 On the Console Interface Main Menu, select the Site-Specific Configura-

tion option, and press Enter.


2 Select the PNNI System-Wide Configuration option, and press Enter.


3 Select the PNNI System Statistics command and press Enter.

The PNNI System Statistics window is displayed (see Figure 6-34). The

fields in this window are described in Table 6-60.

End

Sequence Number

(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the sequence number of the instance of

the PTSE as it appears in the local topology data-

base.

Checksum

(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the value of the PTSE checksum as it

appears in the local topology database.

Lifetime

(display only)

Default: N/A

Range: N/A

Format: Numeric

Displays the value of the remaining lifetime for

the given PTSE as it appears in the local topology

database.

Table 6-58. Field Descriptions for the PNNI PTSE Information Window (Continued)




255-700-447 6-73




Figure 6-34. PNNI System Statistics Screen Window

Table 6-59. Commands for the PNNI System Statistics Screen Window

Command Function

Continuous Update Updates the values in the fields on this window continuously.

Use this command as a toggle switch to view the statistics.





6-74 255-700-447


Table 6-60. Field Descriptions for the PNNI System Statistics Window

Field Name Values Description

[Dtl Count Origina-

tor]

Default: 0

Range: N/A

Format: numeric

The total number of designated transit list (DTL)

stacks that the PSAX system has originated as the

DTL originator and placed into signaling mes-

sages. This includes the initial DTL stacks com-puted by the PSAX system and those for any

alternate route. DTL stacks computed by the

PSAX system in response to crankbacks.

[Dtl Count Border] Default: 0

Range: N/A

Format: numeric

The number of partial DTL stacks that the PSAX

system has added into signaling messages as an

entry border node. This includes the initial par-

tial DTL stacks computed by the PSAX system and

those for any alternate route. Partial DTL stacks

computed by the PSAX system in response to

crankbacks.

[Crankback Count

Org.]

Default: 0

Range: N/A

Format: numeric

The count of the total number of connection

setup messages including DTL stacks originated by the PSAX system that have cranked back to

the PSAX system at all levels of the hierarchy.

[Crankback Count

Border]

Default: 0

Range: N/A

Format: numeric

The count of the total number of connection

setup messages, including DTLs added by the

PSAX system as an entry border node that have

cranked back to the PSAX system at all levels of

the hierarchy. This count does not include crank-

backs for which the PSAX system was not the

crankback destination. Only those crankbacks

that were directed to the PSAX system are

counted here.

[AltRoute CountOrg.]


Format: numeric

The total number of alternate DTL stacks that thePSAX system has computed and placed into sig-

naling messages as the DTL originator.

[AltRoute Count

Border]

Default: 0

Range: N/A

Format: numeric

The total number of alternate partial DTL stacks

that the PSAX system has computed and placed

into signaling messages as an entry border node.

[Route Fail Count

Org.]

Default: 0

Range: N/A

Format: numeric

The total number of times where the PSAX sys-

tem failed to compute a viable DTL stack as the

DTL originator for a call. It indicates the number

of times a call was cleared from the PSAX system

due to originator routing failure.

[Route Fail CountBorder]


Format: numeric

The total number of times where the PSAX sys-tem failed to compute a viable partial DTL stack

as an entry border node for some call. It indicates

the number of times a call was either cleared or

cranked back from the PSAX system due to bor-

der routing failure.



255-700-447 6-75



[Route Fail Unreach

Org.]

Default: 0

Range: N/A

Format: numeric


tem failed to compute a viable DTL stack as the

DTL originator because the destination was

unreachable, that is, calls that were cleared withthe message “specified transit network unreach-

able” or the message “destination unreachable”

in the cause incoming exclusion (IE).

[Route Fail Unreach

Border]

Default: 0

Range: N/A

Format: numeric


tem failed to compute a viable partial DTL stack

as an entry border node because the target of the

path calculation was unreachable,that is, calls

that are cleared or cranked back with the cause

“specified transit network unreachable” or the

cause “destination unreachable” in the cause IE.

[Route Node Num-

ber]

Default: 0


The number associated with the route node from

which the statistics on this window are beinggenerated.

[Route Addr Num-

ber]

Default: 0

Range: N/A

Format: numeric

The number associated with the route address

from which the statistics on this window are

being generated.

Table 6-60. Field Descriptions for the PNNI System Statistics Window (Continued)





6-76 255-700-447





255-700-447 7-1

7 Configuring ATM Trunking


ATM trunking configuration supports switched and nonswitched IWF trunks.

Configuring Switched IWF Trunks

For configuring IWF trunks in switched mode, the following list describes the

tasks you need to perform:

1. Configuring the local IWF node

2. Configuring the remote IWF nodes

3. Configuring one or more signaling VCC identifiers and their parameters

4. Configuring one or more bearer VCC identifiers and their parameters

5. Configuring the addresses for the narrowband routing and the broad-

band routing tables

Configuring Nonswitched IWF Trunks

For configuring IWF trunks in nonswitched mode, the following list describes

the tasks you need to perform:

1. Configuring the local IWF node

2. Configuring the remote IWF nodes

3. Configuring one or more bearer VCC identifiers and their parameters

In addition, you can view all ATM trunking configuration information for

both switched and nonswitched IWF trunks

To configure the system for ATM trunking, perform the following procedures.

Configuring the Local IWF Node

Begin

1 On the Console Interface Main Menu window, select the Site-SpecificConfiguration option.


2 On the Site-Specific Menu window, select the ATM Trunking Configura-

tion option.

The ATM Trunking Local Node Configuration window (see Figure 7-2) is

displayed.



Chapter 7 Configuring ATM TrunkingConfiguring the Local IWF Node

7-2 255-700-447




4 To apply the configuration values, select the Apply Configuration

command.

5 Select the Bring Admin Status Up command to bring the administra-

tive status of the local IWF up.

End

After you have completed configuring the local IWF node, configure the

remote IWF nodes. You can configure a maximum of 100 remote IWF nodes

per PSAX system.

Figure 7-1. Site-Specific Menu Window—ATM Trunking Configuration OptionSelected



255-700-447 7-3


Chapter 7 Configuring ATM TrunkingConfiguring the Local IWF Node


Figure 7-2. ATM Trunking Local Node Configuration Window

Table 7-1. Commands for the ATM Trunking Local Node Configuration Window

Command Function


Bring Admin Status Up Enables the transmission of calls between the configured

local IWF node and the remote IWF nodes.

Bring Admin Status Down Disables the transmission of calls between the local IWF

node and the remote IWF nodes while preserving local

and remote node configuration settings.

Delete Node Deletes the configuration settings of the local IWF node

that is not in service. You must use the Bring Admin

Status Down command before you can use the Delete

Node command.

Go to Remote IWF Table Displays the ATM Trunking Remote IWF Table window.

Go to Broadband Routing Table Displays the ATM Trunking Broadband Routing Table

window.

Go to Narrowband RoutingTable

Displays the ATM Trunking Narrowband Routing Tablewindow.




Chapter 7 Configuring ATM TrunkingConfiguring a Remote IWF Node

7-4 255-700-447


Configuring a Remote IWF Node

Begin

1 On the ATM Trunking Local Node Configuration window, select the Go

to Remote IWF Table command.

2 The ATM Trunking Remote IWF Table window is displayed (seeFigure 7-3).Select the Add Remote IWF Entry command.

The ATM Trunking Remote IWF Configuration window (see Figure 7-4)

is displayed.



4 Select the Add Configuration command.

Table 7-2. Field Descriptions for the ATM Trunking Local Node Configuration Window


Local IWF ID Default: 0

Range: 1–255

Format: numeric

Specifies the local interworking function (IWF)

identifier for the local endpoint.

Wireless Applications: The Cell Site and the MSC

must have different IDs. The Cell site is the localIWF; the MSC is the remote.

ATM Address Default: 0

Range: N/A


quad

Specifies the IWF ATM address for the local end-

point. Type an address in hexadecimal format up

to 20 bytes (160 bits) long (10 groups of 4 charac-

ters each).

Wireless Applications: The Cell Site and MSC

must have different addresses.

Max Remote IWF Default: 100

Range: 1–1024

Format: numeric

Specifies the maximum number of remote IWF

IDs that can be connected to the local endpoint in

the PSAX system. If you enter a value higher

than the default value in this field, you must also

increase the value of the atmTrunkVCCs field on

the Call Control Resource Allocation window

accordingly.

Wireless Applications: For the Cell Site to MSC

applications, the MSC is the remote IWF. You are

limited to 32 ATM VCC IWFs, as configured on

the Call Control Resource Allocation window.

[Admin Status] Default: Down

Range: N/A

Format: predefined

alphanumeric

Specifies whether the local IWF is active.

Up Indicates that the local IWF is active.Down Indicates that the local IWF is inactive.



255-700-447 7-5



The following message in displayed in the status line of the window:

This configuration is added.

Note that the following commands are now displayed in the window: Go

to Bearer VCC Table, Go to Data Channel Table.

5 Select the Bring Admin Status Up command to bring the administra-

tive status of the remote IWF you just added into service.

6 To return to the ATM Trunking Remote IWF Table window to add addi-

tional signaling VCC IDs, press Ctrl+B.

7 Repeat Steps 2–5 to add additional remote IWF nodes (up to a maximum

of 100 per PSAX system).

En


Figure 7-3. ATM Trunking Remote IWF Table Window

Table 7-3. Commands for the ATM Trunking Remote IWF Table Window

Command Function

Find Rmt IWF ID Searches the table for a specific remote IWF ID. To find a specific

remote IWF ID, enter a value in this field. If the remote IWF ID

exists, it is displayed on the first line of the table.

Add Remote IWF Entry Displays the ATM Trunking Remote IWF Configuration window.

Go Back to Previous

Screen

Redisplays the ATM Trunking Local Node Configuration window.




7-6 255-700-447


Note: At the time of initial installation, the ATM Trunking Remote IWF

Table window is empty. After you have added remote IWF nodes,

this window displays all the remote IWF IDs in the PSAX system.

The fields on this window are described below.


Table 7-4. Field Descriptions for the ATM Trunking Remote IWF Table


Rmt IWF ID (display

only)

This column displays all the remote IWF IDs in the PSAX system.

Remote IWF Address

(display only)

This column displays all the corresponding ATM remote IWF ID

addresses in the PSAX system.

Total: 0/0 The first number in this field indicates the number of the remote

IWF ID entry on the first line of the currently displayed window.

The second number indicates the total number of remote IWF ID

entries in the PSAX system.

Figure 7-4. ATM Trunking Remote IWF Configuration Window

Table 7-5. Commands for the ATM Trunking Remote IWF Configuration Window

Command Function

Add Configuration Applies the values you set on this window.

Update Configuration This command is not currently supported.

Bring Admin Status Up When the value in the [Admin Status] field is Down, brings

the remote IWF node to the status Up.



255-700-447 7-7



Bring Admin Status Down When the value in the [Admin Status] field is Up, brings

the remote IWF node to the status Down.

Delete and Return Deletes the remote IWF node that is not in service.

Go to Sig VCC Table Displays the ATM Trunking Sig VCC Table window. This

command is displayed only after you have added a remote

IWF ID.

Go to Bearer VCC Table Displays the ATM Trunking Bearer VCC Table window. This

command is displayed only after you have added a remote

IWF ID.

Go to Data Channel Table Displays the ATM Trunking Data Channel Table window.

This command is displayed only after you have added a

remote IWF ID.

Go Back to Previous Screen Redisplays the ATM Trunking Remote IWF Table window.

Table 7-5. Commands for the ATM Trunking Remote IWF Configuration Window (Continued)

Command Function

Table 7-6. Field Descriptions for the ATM Trunking Remote IWF Configuration Window


Remote IWF ID Default: 0

Range: 1–1024

Format: numeric

Specifies the remote interworking function (IWF)

identifier for the remote endpoint. The value in

this field must be less than or equal to the value

for the maximum number of remote IWFs in the

PSAX system. You specify the maximum number

of IWFs on the ATM Trunking Local Node Config-

uration window.

Wireless Applications: You are limited in the

number of remote IWFs by the values configured

on the Call Control Resource Configuration win-

dow.

Remote IWF ATM

Address

Default: 0

Range: N/A

Format: hexadecimal

Specifies the IWF ATM address for the remote

endpoint. Type an address in hexadecimal format

up to 20 bytes (160) bits long (10 groups of 4

characters each).

Wireless Applications: If configuring a cell site

with an MSC, the MSC is the remote IWF.

Remote IWF Trnk

Mode

(display only)

Default: Switched

Range: N/A

Format: predefined

alphanumeric

Specifies whether the remote IWF trunk is in

switched mode or non-switched mode. Currently

only the nonswitched mode is supported.

Switched Indicates that the specified signaling VCC is used

for the connection trunk.

Non-switched Indicates that no signaling is used for the connec-

tion trunk.

Wireless Applications: If configuring a cell site

with an MSC, select this value.



Chapter 7 Configuring ATM TrunkingAdding a Signaling VCC Identifier

7-8 255-700-447


Adding a Signaling VCC Identifier

Begin

1 On the ATM Trunking Remote IWF Configuration window, select the Go

to Sig VCC Table command.

The ATM Trunking Sig VCC Table window is displayed (see Figure 7-5).

2 Select the Add ATM Trunking Entry command.

The ATM Trunking Sig Configuration window is displayed (see

Figure 7-6).



4 Select the Apply Configuration command.



5 To return to the ATM Trunking Sig VCC Table window to add additional

signaling VCC IDs, press Ctrl+B.

Remote IWF MAX

Call Rate

Default: 60

Range: 1–4096

Format: Numeric

(Calls per second)

Indicates the maximum number of new calls per

second within this remote IWF. This field value is

used to estimate the bandwidth resource require-

ment for an unconfigured SVC SIG VCC.

Remote IWF PCM

Encoding

Default: A-law

Range: N/A

Format: predefined

alphanumeric

Indicates the type of PCM encoding performed on

the bearer VCC.

A-law Indicates that the traffic on the bearer VCC is

encoded as A-law traffic.

U-law Indicates that the traffic on the bearer VCC is

encoded as U-law traffic.

None Indicates that PCM encoding is not performed on

the bearer VCC.

[Admin Status] Default: Up

Range: N/A

Format: predefined

alphanumeric

Specifies whether the remote IWF is active.

Up Indicates that the remote IWF is active.

Down Indicates that the remote IWF is inactive.

Table 7-6. Field Descriptions for the ATM Trunking Remote IWF Configuration Window (Continued)




255-700-447 7-9



6 Repeat Steps 2–5 to add additional signaling VCC IDs.

End


Note: At the time of initial installation, the ATM Trunking Sig VCC Table

window is empty. After you have added signaling VCC IDs, this

window displays all the signaling VCC IDS by remote IWF ID in the

PSAX system.

The fields on this window are described below.

Figure 7-5. ATM Trunking Sig VCC Table Window

Table 7-7. Commands for the ATM Trunking Sig VCC Table Window

Command Function

Add ATM Trunking Entry Displays the ATM Trunking Sig VCC Configuration window.

Go Back to Previous Screen Redisplays the Remote IWF Configuration window.

Find Rmt IWF ID: VCC ID: Searches the table for a specific remote IWF ID with a spe-

cific VCC ID. To find a specific entry, enter values in these

fields. If the specified entry exists, it is displayed on the first

line of the table.




7-10 255-700-447


The ATM Trunking Sig VCC Configuration window (see Figure 7-6) is

displayed.


Table 7-8. Field Descriptions for the ATM Trunking Sig VCC Table Window

Field Names Description

Rmt IWF ID This column displays all the remote IWF IDs in the PSAX system.

VCC ID This column displays all the corresponding VCC IDs, which are

assigned by the owners of the signalling VCC.

Out Intf ID This column displays all the corresponding interface identifier of the

outgoing interfaces.

Out VPI This column displays all the corresponding VPIs for the outgoing

interfaces.

Out VCI This column displays all the corresponding VCIs for the outgoing

interfaces.

Total: 0/0 The first number in this field indicates the number of the remote

IWF ID entry on the first line of the currently displayed window.

The second number indicates the total number of remote IWF IDs in

the PSAX system.

Figure 7-6. ATM Trunking Sig VCC Configuration Window

Table 7-9. Commands for the ATM Trunking Sig VCC Configuration Window

Command Function


Update Configuration Updates the status display in the Oper Status field.



255-700-447 7-11



Delete and Return Deletes the remote IWF node that is not in service.

Go Back to Previous Redisplays the ATM Trunking Sig VCC Table window.

Table 7-9. Commands for the ATM Trunking Sig VCC Configuration Window (Continued)

Command Function

Table 7-10. Field Descriptions for the ATM Trunking Sig VCC Configuration Window


[Remote IWF ID] Default: User-

assigned

Range: N/A

Format: Numeric

Remote IWF identifier for the remote endpoint.

Sig VCC ID Default: 0

Range: 0–16383

Format: Numeric

Virtual channel connection identifier, which is

assigned by the owner of the signaling VCC.

[Out Interface ID] Default: 00/00/00

Range: N/A

Format: SS/PP/CC

Interface identifier of the outgoing interface. This

field is editable only for the PVC connection type.

This field is display only for SVC and SPVC con-

nection types.

VCC Conn Type Default: SVC

Range: N/A

Format: Predefined

alphanumeric

Specifies the connection type that is used for the

signaling VCC ID.

SVC Indicates the connection type for the trunk is an

SVC.

SPVC Indicates the connection type for the trunk is an

SPVC.

PVC Indicates the connection type for the trunk is a

PVC.

[Out VPI/VCC ID] Default: 0 / 0

Range: 0–4095 (VPI);

0–65535 (VCC)

Format: Numeric

Virtual path identifier and virtual channel con-

nection identifier for the outgoing interface. This

field is editable only for the PVC connection type.

This field is display only for SVC and SPVC con-

nection types.

Inactive Time

Period

Default: 3600

Range: N/A

Format: Numeric

Inactive time period allowed to clear the call.

Signaling Default: Other

Range: N/A

Format: Predefined

alphanumeric

Specifies the type of signaling protocol used

between the local and remote IWFs. At thepresent time, both ends of the connection must

be on a PSAX system.

Other Indicates that ATM 4.0 signaling is used.

Pss1 This value is not currently supported.

Dss1 This value is not currently supported.

Dpnss This value is not currently supported.




7-12 255-700-447


Fwd/Bwd PCR

(cps)

Default: 0 / 0

Range: N/A

Format: Numeric

(cells per second)

Forward and backward peak cell rate (cells per

second) for the connection.

Fwd/Bwd SCR

(cps)

Default: 0 / 0

Range: N/A

Format: Numeric

(cells per second)

Forward and backward sustained cell rate (cells

per second) for the connection.

Fwd/Bwd MBS

(cells)

Default: 0 / 0

Range: N/A

Format: Numeric

(cells)

Forward and backward maximum burst size

(cells) for the connection.

Max AAL2 VCC Default: 255

Range: N/A

Format: Numeric

Maximum number of bearer VCCs controlled by

the signaling VCC.

[Active AAL2 VCC] Default: 1

Range: N/A

Format: Numeric

Number of active bearer VCCs controlled by the

signaling VCC.

Egress VIB Default: 0

Range: N/A

Format: Numeric

Virtual identifier to associate with the egress side

of the A to B connection.

Egress VUNIB Default: 0

Range: N/A

Format: Numeric

Virtual UNI identifier to associate with the egress

side of the A to B connection.

[Sig VCC Owner] Default: Local

Range: N/A

Format: Predefined

alphanumeric

Indicates whether the signaling VCC owner is thelocal IWF or the remote IWF. This field is editable

only for the PVC and SPVC connection types.

This field is display only for SVC connection type.

Local The signaling VCC owner is the local IWF.

Remote The signaling VCC owner is the remote IWF.

Table 7-10. Field Descriptions for the ATM Trunking Sig VCC Configuration Window (Continued)




255-700-447 7-13


Chapter 7 Configuring ATM TrunkingAdding a Bearer VCC Identifier

Adding a Bearer VCC Identifier

Begin


to Bearer VCC Table command.

[Oper Status] Default: Idle

Range: N/A

Format: Predefined

alphanumeric

Displays the operational status of the local IWF.

Idle Indicates that the connection is not operational.

OutOfService Indicates that the PVC connection is not

operational.

Init Indicates that the connection is being initiated.

Connecting Indicates that the connection is being connected

but layer 2 is not yet operational.

Active Indicates that the connection is operational and is

transmitting traffic.

Release Indicates that the connection is being released.

Retry Timer Default: 30Range: N/A

Format: Seconds

Indicates the time in seconds that the PSAX sys-tem will wait before attempting to establish the

ATM Trunking Signalling VCC SPVC connection

after a previous failed call attempt. A value of 0

indicates that retries will be attempted immedi-

ately.

Retry Limit Default: 0

Range: N/A

Format: Numeric

Indicates the number of times that the PSAX sys-

tem attempting to establish the ATM Trunking

Signalling VCC SPVC connection. A value of 0

indicates an unlimited number of attempts.

Restart Default: Restart

Range: N/A

Format: Predefined

Indicates whether the active SVC connection is

released, if necessary, and a new connection

setup procedure takes place.

Restart Indicates that the PSAX system will restart the

SPVC connection.

Noop Indicates that the PSAX system will not restart

the SPVC connection.

Retry Counter Default: 0

Range: N/A

Format: Numeric

Indicates the number of failed attempts to estab-

lish the connection. This field resets to 0 when-

ever a connection is successfully established or

the ATM Trunking Signalling VCC SPVC connec-

tion is restarted.

Table 7-10. Field Descriptions for the ATM Trunking Sig VCC Configuration Window (Continued)





7-14 255-700-447


The ATM Trunking Bearer VCC Table window is displayed (see

Figure 7-7).

Note: At the time of initial installation, the ATM Trunking Bearer VCC

Table window is empty. After you have added bearer VCC IDs,

this window displays all the bearer VCC IDS by remote IWF ID in

the PSAX system.

2 Select the Add Bearer VCC Entry command.

The ATM Trunking Bearer VCC Configuration window (see Figure 7-8) is

displayed.






5 To return to the ATM Trunking Bearer VCC Table window to add addi-

tional bearer VCC IDs, press Ctrl+B.

6 Repeat Steps 2–5 to add additional bearer VCC IDs.

End


Figure 7-7. ATM Trunking Bearer VCC Table Window



255-700-447 7-15




Table 7-11. Commands for the ATM Trunking Bearer VCC Table Window

Command Function

Find . . .Rmt IWF ID: VCC:

ID

Searches the table for a specific remote IWF ID with a

specific VCC ID. To find a specific entry, enter values in

these fields. If the specified entry exists, it is displayed on

the first line of the table.

Add Bearer VCC Entry Displays the ATM Trunking Bearer VCC Configuration

window.

Go Back to Previous Screen Redisplays the Remote IWF Configuration window.

Table 7-12. Field Descriptions for the ATM Trunking Bearer VCC Table Window

Field Names Description

Rmt IWF ID This column displays all the remote IWF IDs in the PSAX system.

VCC ID This column displays all the corresponding bearer VCC identifiers.Sig VCC ID This field is not currently supported. This column displays the corresponding

signalling VCC identifiers.

Intf ID This column displays all the corresponding VCC interface identifiers.

VPI This column displays all the corresponding VPIs for the bearer channels.

VCI This column displays all the corresponding VCIs for the bearer channels.

Total: 0/0 The first number in this field indicates the number of the remote IWF ID

entry on the first line of the currently displayed window. The second num-

ber indicates the total number of remote IWF IDs in the PSAX system.

Figure 7-8. ATM Trunking Bearer VCC Configuration Window




7-16 255-700-447



Table 7-13. Commands for the ATM Trunking Bearer VCC Configuration Window

Command Function

Add Configuration Applies the values you set on this window.

Delete Configuration Deletes the configuration.

Restart Connection Restarts the connection.

Display Next Connection Displays the next connecion.

Continuous Update Continuously update the window data.

Configure DSP Parameters Configures DSP parameters.

Note: If DSP parameters are configured on a per connection

basis, the settings on this window are overridden by the

applicable per connection configuration.

Bring Into Service Brings the specified ATM trunk bearer VCC into service.

Take Out of Service Takes the specified ATM trunk bearer VCC out of service.

Go Back to Previous Screen Redisplays the ATM Trunking Bearer VCC Table window.

Table 7-14. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window*


Remote IWF ID Default: User-

assigned

Range: N/A

Format: Numeric

Displays the remote interworking function (IWF) identi-

fier for the remote endpoint. This value is automatically

assigned based on the previously selected remote IWF ID.

ATM Trnk Br

VCC ID

Default: 0

Range: 0–4096

Format: Numeric

Specifies the ATM Trunk bearer VCC ID.

Wireless backhaul applications: For connections between

active (local) Cell Sites and passive (remote) MSCs, usethe same ID number per trunk in the IMA link.

[Sig VCC ID] Default: 0

Range: N/A

Format: Numeric

Displays the identifier of the signaling VCC.



255-700-447 7-17



Service Type Default: Cbr-1

Range: N/A

Format: Predefined

Specifies the service type for the connection.

For any CBR type selected, the CAC only allows 1 DS0

per connection. For any CBR type selected, the total

available bandwidth for all DS0 connections is checked before DSPs are allocated, as VBR has no restrictions on

the number of DS0s allowed per connection.

Wireless backhaul applications: If configuring a cell site

with an MSC, both the local and remote VCC must be the

same service type. Differing types will cause errors, and

the bearer VCC will not become active.

Cbr-1 Indicates contant bit rate, priority 1.




Ubr Indicates unspecified bit rate.

Vbr-nrt2 Indicates variable bit rate, nonreal time, queue 2

Vbr-nrt1 Indicates variable bit rate, nonreal time, queue 1

Vbr-rt2 Indicates variable bit rate, real time, queue 2

Vbr-rt1 Indicates variable bit rate, real time, queue 1

Vbr-express Indicates variable bit rate, express.

SAR Type Default: Aal2

Range: N/A

Format: Predefined

Specifies the segmentation and reassembly type for the

connection.

Aal2 Indicates that compressed, connection-oriented, delay-

sensitive VBR traffic will be transmitted on this connec-tion.

Wireless backhaul applications: Select this SAR Type for

connections between cell sites and MSCs on both sides of

the connection only if a DSP2E/F is available. Do not use

ATM trunking is no DSPs are available.

Aal1 Indicates that uncompressed, connection-oriented, time-

sensitive CBR traffic will be transmitted on this connec-

tion.

Fwd/Bwd PCR

(cps)

Default: 172/172

Range:

Format: Numeric

Specifies the forward and backward peak cell rate (cells

per second) for the connection.

Wireless backhaul applications: This value must be the

same on the local and remote VCC or the bearer VCC

will not become active.

Fwd/Bwd SCR

(cps)

Default: 172/172

Range:

Format: Numeric

Specifies the forward and backward sustained cell rate

(cells per second) for the connection.

Note: This field is displayed only when the value in the

Service Type field is one of the following: Vbr-nrt2, Vbr-

nrt1, Vbr-rt2, Vbr-rt1, Vbr-express.

Table 7-14. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window* (Continued)





7-18 255-700-447


Fwd/Bwd MBS

(cells)

Default: 1/1

Range:

Format: Numeric

Specifies the forward and backward maximum burst size

(cells) for the connection.

Note: This field is displayed only when the value in the

Service Type field is one of the following: Vbr-nrt2, Vbr-nrt1, Vbr-rt2, Vbr-rt1, Vbr-express.

OAM Status Default: Unsupp

Range: N/A

Format: Predefined

Specifies the OAM support used.

Unsupp Indicates that OAM is not in use.

Wireless backhaul applications: The CID range is 8 to 255

when OAM is unsupported.

GR-303/V.5 applications: Select this value. Do not acti-

vate OAM; the feature is not available on AAL2 trunks to

IADs.

End-Pt The PSAX system is used as a termination point for ATMtraffic. The OAM loopback test is supported for end-to-

end connections only.

Wireless backhaul applications: Select End-Pt to enable

OAM for Std AAL2 SPVCs. However, these restrictions

apply: 1) the CE channel range is 32 to 255. In addition,

the CIDs for each CE channel are fixed. Channel 1 must

be CID 32, channel 2 must be CID 33, etc., up to 255

CIDs; 2) only one DS1 per AAL2 SPVC trunk (bearer

VCC) is allowed; 3) no OAM flows are sent toward the

ATM side. Instead, a proprietary OAM implementation

scheme is used; 4) only upstream interworking unframed

1s are supported. A configuration of an SPVC trunk,

OAM enablement, and trunk conditioning upstream

interworking is not supported; and 5) when LOS, AIS or

RDI is received on the CE port, the trunk is torn down

and AIS or RDI is sent to the far end.

VCC Conn Type Default: Svc

Range: N/A

Format: Predefined

Specifies the VCC connection type.

Svc Switched virtual circuit.

Spvc Software-switched permanent virtural circuit.

Wireless backhaul applications: If the spvcGlobalPriori-

tyScheme field is enabled on the Call Control Resource

Allocation Configuration window, you must select Spvc as the VCC Conn Type.

Pvc Permanent virtural circuit.

Wireless backhaul applications: If the spvcGlobalPriori-

tyScheme field is enabled on the Call Control Resource

Allocation Configuration window, you must select Spvc

as the VCC Conn Type.





255-700-447 7-19



[VCC Interface

ID]

Default: 00/00/00

Range: N/A

Format: Numeric

Identifies the VCC interface ID for the outgoing interface.

The trunk bearer VCC does not become active until both

the local and remote trunk terminations are configured

and brought into service. After this is done, the valuesassigned to the trunk are displayed in this field and the

VCC VPI/VCI field below. This field is valid only when

Pvc is selected in the VCC Conn Type field.

[VCC VPI/VCI] Default: 0 / 0

Range: 0–4095

(VPI); 0–65535

(VCI)

Format: Numeric

Identifies the VPI and VCI for the outgoing interface. The

trunk bearer VCC does not become active until both the

local and remote trunk terminations are configured and

brought into service. After this is done, the values

assigned to the trunk are displayed in this field and the

VCC Interface ID field above. This field is valid only when

Pvc is selected in the VCC Conn Type field.

[VCC

VIB/VUNIB]

Default: 0/0

Range: N/AFormat: Numeric

Specifies the egress part of the A to B side of the VI/VUNI.

This field is valid only when Pvc is selected in the VCCConn Type field.

[VCC Owner] Default: Local

Range: N/A

Format: Predefined

Indicates whether the bearer VCC owner is the active

(local) side or the passive (remote) side of the connec-

tion. If the values are improperly set, the bearer VCC will

not become active.

This field is valid only when Spvc or Pvc is selected in

the VCC Conn Type field.

Local The VCC owner is local.

Wireless backhaul applications: Select this VCC Owner

Type for the cell site (caller) side of the connection.

Remote The VCC owner is remote.Wireless backhaul applications: Select this VCC Owner

Type for the MSC (called) side of the connection.

[Retry

Timer/Limit]

Default: 30/0

Range:

Format: Numeric

Timer: Specifies the amount of time(seconds) to wait

before attempting to establish the signaling side of the

connection after a previously failed call attempt. The

value 0 indicates that the call attempt is to be retried

immediately.

Limit: Specifies the maximum limit on how many retried

calls are to be attempted. The value 0 indicates no limit

on how many call attempts can be made. This field is

valid only when Spvc is selected in the VCC Conn Type

field.Wireless backhaul applications: On active (local) side

SPVCs, this is a configurable parameter.






7-20 255-700-447


Inactive Timer Default: 3600

Range: 0–9999999

99

Format: Numeric(msec)

Specifies the time period during which no activity is tak-

ing place before the signaling side of the connection

clears the call. This field is valid only when Svc is selected

in the VCC Conn Type field.

[Admin Status] Default: OutOf-

Service

Range: N/A

Format: Predefined

Indicates whether the connection is attempting to make

calls or receive calls.

OutOfService Indicates that the connection is not available to attempt

making or receiving calls.

InService Indicates that the connection is available to attempt mak-

ing calls or receiving calls.

Priority Default: 3

Range: 1–6

Format: Numeric

Specifies the user-defined priority level of this connec-

tion. Assigning Priority 1 to all wireless calls ensure theywill be reconnected first in the event that an ATM IMA

link failure. Typically, level 1 is the highest priority and

level 6 is the lowest. This value overrides the QoS class,

endpoint type, and/or AAL type with regard to priority.

The AAL2 VCC that is assigned to the bearer VCC will be

transmitted according to the priority value. If the passive

side of the bearer VCC does not have the same value as

the active side, it will not affect the priority because the

active side controls priority.

Application Type Default: Narrow-

band


Specifies the PSAX application that will use this trunk

connection.

Narrowband Indicates the trunk will be used for narrowband connec-

tions.

V5 This value is not currently supported.

Gr303 Indicates the trunk will be used for GR-303 connections.

H248 Indicates the trunk will be used for H.248 protocol con-

nections.

Spvc Indicates the trunk will be used for SPVC connections.

Wireless backhaul applications: If the spvcGlobalPriority-

Scheme field is enabled on the Call Control Resource

Allocation Configuration window, you must select thevalue Spvc in the Application Type field.





255-700-447 7-21



Dsp Iwf Type Default: None

Range: N/A

Format: Predefined

Specifies the Interworking function type on assigning

AAL2 connections to compatible DSP chips on the DSP2C

through DSP2F Voice Server modules.

None Allows the assignment of standard AAL2 connections to

DSP chips on the DSP2C Voice Server module that are

configured as AlgoSet1 through AlgoSet3, and on the

DSP2E/F as AlgoSet1 and AlgoSet6. This parameter

allows the mixture of pure voice (CE-to-ATM) with data

(VBR-to-ATM) in the same AAL2 trunk group, such as is

used in the European LES trunking standard V.5.2. This

parameter supports applicable connection types of previ-

ous PSAX system software releases.

Packet-pipe Allows the assignment of standard AAL2 connections to

DSP chips on the DSP2E/F modules that are configured

as AlgoSet7. This parameter will not allow the mixture

of pure voice (CE-to-ATM) with data (VBR-to-ATM) inthe same AAL2 trunk group. This parameter supports

applicable connection types for pure data (VBR-to-ATM)

in wireless applications.

How bandwidth is assigned for this type depends on what

type of CBR or VBR you select in the Service Type field.

Note: The value Packet-pipe cannot be used with the

DSP2C Voice Server module.

Gsm Allows the assignment of standard AAL2 connections to

DSP chips on the DSP2E/F modules that are configured

as AlgoSet8. This parameter will not allow the mixture

of pure voice (CE-to-ATM) with data (VBR-to-ATM) in

the same AAL2 trunk group.

Note: GSM cannot be used on the DSP2C/D Voice

Server modules.

Dsp Select Type Default: Auto-

matic

Range: N/A

Format: Predefined

Specifies how connections to DSP resources are re-routed

and reconnected to other DSP resources in the event of

DSP resource failure (a DSP resource is a single chip on

any DSP2x module). The setting you select in this field

must match the setting in the Selection Type column on

the Dsp Resource Management Table (after the site-spe-

cific DSP Resource Configuration option), or your con-

nections will not be assigned or activate.

Automatic If a DSP resource fails, connections are rerouted by a soft-

ware DSP resource manager that selects available DSPsfrom a chassis-wide pool.

Manual If a DSP resource fails, the DSP resource manager selects

DSPs from a particular module designated in the Dsp Slot

Id field (configured by you).






7-22 255-700-447


Dsp Card Slot Id Default: 0

Range: Chassis

dependent

Format: Numeric

Specifies the slot number of the DSP2 x Voice Server mod-

ule from which the software DSP Resource Manager

selects DSPs to reroute and reconnect DSP-processed

connections, in the event of active DSP resource failure.If you selected Manual in the Dsp Select Type field, you

must specify the DSP2 x Voice Server module slot number

in the Dsp Card Slot Id field from which you want the

DSP Resource Manager to select replacement DSPs. If no

DSP resource is available on the DSP2 x module in the

specified slot, the connection is rejected. If you selected

Automatic in the Dsp Select Type field, the Dsp Card

Slot Id field is not displayed.

Num of DSP

Chnl

Default: 0

Range: 0–384

Format: Numeric

Specifies the number of DS0s that can be reserved as DSP

channels. If the IWF Type is Packet-pipe, the bandwidth

configured by you for the trunk calculates how many

DS0s fit into the trunk. For example, the DS0 line rate is

approximately 171 cps. If you want 200 cps, the bw actu-

ally alloocated is 200/171, or 1.16 DS0s. The CAC

reserves the DS0 resource when the first connection is

made on the trunk. If the value is left at the default 0, the

number of reserved DS0s is best-effort.

Note: If you have selected Packet-pipe in the Dsp Iwf

Type field, how bandwidth is assigned to the DSP chan-

nels also depends on what type of CBR or VBR you select

in the Service Type field (see the Dsp Iwf Type and Ser-

vice Type fields for more details).

[Last Rls Cause] Default: 0

Range: N/A

Format: Numeric

Displays the last release cause code. The cause code indi-

cates a reason why the last attempted call was released.

See the reference appendix in this guide for the descrip-

tion of SPVC Connection Cause Codes.

[Last Rls Diag] Default: N/A

Range: N/A

Format: predefined

Displays the last release diagnosis. The value in this field

explains how the connection was released and reported

by the far end of the connection.

[Retry Counter] Default: N/A

Range: N/A

Format: Numeric

Displays how many attempts to establish the connection

have failed. The counter is reset whenever a connection

is successfully established or the signaling side of the con-

nection is restarted.





255-700-447 7-23


Chapter 7 Configuring ATM TrunkingAdding a Narrowband Address

Adding a Narrowband Address

Begin


to Narrowband Routing Table command.

2 The ATM Trunking Narrowband Routing Table window is displayed (see

Figure 7-9).Select the Add an Entry field, and select values for the other

fields on this window from the values given in Table 7-16.

Note: At the time of initial installation, the ATM Trunking Narrowband

Table window is empty. After you have added narrowband

addresses, this window displays all of them by remote IWF ID in

the PSAX system.

3 Press Enter to save the address.

The narrowband address you just entered is now displayed in the table.

4 Repeat steps 2–3 to add more narrowband addresses.

End

[Oper Status] Default: Idle

Range: N/A

Format: Predefined

Displays the operational status of the bearer VCC.

Idle Indicates that the bearer VCC is not transmitting.

OutOfService Indicates that the bearer VCC is not operational.

Init Indicates that the bearer VCC is initializing.

Active Indicates that the bearer VCC is transmitting.

Release Indicates that the bearer VCC has been released.

[Active Chnl

Cnt]

Default: 0

Range: N/A

Format: Numeric

Displays the number of currently active channels for the

bearer VCC

[Avail Band-

width]

Default: 0

Range: N/A

Format: Numeric

Displays the available bandwidth remaining for the

bearer VCC.

Wireless backhaul applications: This value is static and

does not change when bandwidth is used; you must

manually keep a record.

* If you are configuring wireless backhaul applications, all parameters selected for the local and remote

VCC must have the same value (symmetric), or the bearer VCC will not become active.





Chapter 7 Configuring ATM TrunkingAdding a Narrowband Address

7-24 255-700-447



Figure 7-9. ATM Trunking NarrowBand Routing Table Window

Table 7-15. Commands for the ATM Trunking Narrowband Routing Table Window

Command Function

Find: Searches for the ATM address entry with a

value you specify.

Go Back to Connection Menu Redisplays the ATM Trunking Local Node Con-

figuration window.

Table 7-16. Field Descriptions for the ATM Trunking Narrowband Routing Table Window


Narrowband

Address (Hex)

(display table)

Default: N/A

Range: N/A

Format: Hexadecimal

Interworking function ATM addresses for the

remote endpoint. Type an address in hexadecimal

format up to 20 bytes (160 bits) long (10 groups

of 4 characters each).



255-700-447 7-25


Chapter 7 Configuring ATM TrunkingAdding a Broadband Address

Adding a Broadband Address

Begin


to Broadband Routing Table command.

The ATM Trunking Broadband Routing Table window is displayed (see

Figure 7-10).

2 Select the Add an Entry field, and select values for the other fields on this

window from the values given in Table 7-18.

Note: At the time of initial installation, the ATM Trunking Broadband

Table window is empty. After you have added broadband

addresses, this window displays all of them by remote IWF ID in

the PSAX system.

3 Press Enter to save the address.

The broadband address you just entered is now displayed in the table.

4 Repeat steps 2–3 to add more broadband addresses.

End

Add an Entry: Default: User pro-

vided

Range: N/A

Format: Hexadecimal

The NSAP address up to 20 bytes (160 bits). Type

an address in hexadecimal format up to 20 bytes

(160 bits) long (10 groups of 4 characters each),

in E.164 ATM format (see the ATM UNI 3.1 spec-ification).

Num Bits Default: N/A

Range: 1–152

Format: Numeric

Enter a value for the number of bits for the ATM

address mask.

IWF ID Default: N/A

Range: 1–100

Format: Numeric

Interworking function identifier (IWF) for the

remote IWF.

Table 7-16. Field Descriptions for the ATM Trunking Narrowband Routing Table Window (Continued)




Chapter 7 Configuring ATM TrunkingAdding a Broadband Address

7-26 255-700-447



Figure 7-10. ATM Trunking Broadband Routing Table Window

Table 7-17. Commands for the ATM Trunking Broadband Routing Table Window

Command Function

Find: Searches for the ATM address entry with a

value you specify.

Go Back to Connection

Menu

Redisplays the ATM Trunking Local Node


Table 7-18. Field Descriptions for the ATM Trunking Broadband Routing Table Window


Broadband Address

(Hex)

(display table)

Default: N/A

Range: N/A

Format: Hexadecimal

Interworking function ATM addresses for the

remote endpoint. Type an address in hexadecimal

format up to 20 bytes (160 bits) long (10 groups

of 4 characters each).



255-700-447 7-27


Chapter 7 Configuring ATM TrunkingViewing ATM Trunking Information

Viewing ATM Trunking Information

Begin


to Data Channel command.

The ATM Trunking Data Channel Table window is displayed (see

Figure 7-11).

Note: At the time of initial installation, the ATM Trunking Data Chan-

nel Table window is empty. After you have added remote IWFs

and their associated signaling and bearer VCC IDs, this window

displays all switched and nonswitched IWF trunks in the PSAX

system by remote IWF ID.

2 View the fields on this window, which are described below.

End

Add an Entry: Default: User pro-

vided

Range: N/A

Format: Hexadecimal

The NSAP address up to 20 bytes (160 bits). Type

an address in hexadecimal format up to 20 bytes

(160 bits) long (10 groups of 4 characters each),

in E.164 ATM format (see the ATM UNI 3.1 spec-ification).

Num Bits Default: N/A

Range: 1–152

Format: Numeric

Enter a value for the number of bits for the ATM

address mask.

Group ID Default: N/A

Range: 1–255

Format: Numeric

The group identifier for the broadband ATM

address.

Table 7-18. Field Descriptions for the ATM Trunking Broadband Routing Table Window (Continued)





7-28 255-700-447



Figure 7-11. ATM Trunking Data Channel Table

Table 7-19. Commands for the ATM Trunking Data Channel Table Window

Command Function

Find... Rmt IWF ID: VCC ID: Searches the table for a specific remote IWF ID with a

specific VCC ID. To find a specific entry, enter values in

these fields. If the specified entry exists, it is displayed

on the first line of the table.

Update Configuration Updates the display of remote IWF trunks.

Go Back to Previous Screen Redisplays the ATM Trunking Remote IWF Configura-

tion window.

Table 7-20. Field Descriptions for the ATM Trunking Data Channel Table Window


Rmt IWF ID This column displays the remote IWF ID.

Sig VCC ID This field is not currently supported.

This column displays the corresponding signaling VCC identifier.

Br VCC ID This column displays the corresponding bearer VCC identifier.

Ch ID This column displays the channel identifier.

Status This column displays whether the administrative status for the remote

IWF is up or down.



255-700-447 7-29



VCC Owner This column displays the corresponding owner of the signaling VCC.

NB Intf This column displays the corresponding VCC ID, which is assigned by

the owners of the signaling VCC.

Total: 0/0 The first number in this field indicates the number of the remote IWF

ID entry on the first line of the currently displayed window. The sec-

ond number indicates the total number of remote IWF IDs in the

PSAX system.

Table 7-20. Field Descriptions for the ATM Trunking Data Channel Table Window (Continued)





7-30 255-700-447





255-700-447 8-1

8 Configuring V5.2 European IDLC

Overview of the V5.2 European IDLC

The application of the V5.2 Integrated Digital Loop Carrier standard (IDLC)

on the PSAX system includes the implementation of two services:

• Integrated Services Digital Network (ISDN)

• Public Switched Telephony Network (PSTN)

The configuration sequence for these two types of services is the same, but

the values entered on some of the windows are different, especially on the

User Port Configuration windows, the last part of the configuration on the

user side. The network side onfiguration is presented first, followed by the

user side.

V5.2 PSTN Implementation

This sample configuration requires the following modules installed in a PSAX

system:

• One 1-Port STM-1 Single-mode MSP module

• One 21-Port High Density E1 Multiservice module

• One DSP2D Voice Server module

• Two CPUn (primary and standby) modules

Note: Follow the order in which the windows are presented in this docu-

ment or incorrect or failed configuration will result. You are

advised to look at each window and its accompanying commands

and field descriptions below the window before starting the proce-

dure. The configuration windows in general have many more field

options and commands than table windows.

Network Side Configuration Summary

The following steps are a summary only. To perform the configuration, see

the procedures after the summary.

1. If necessary, delete previous configuration files on the modules to be

used by using this path: Console Interface Main Menu > Diagnostics >

Remove Configuration Files command.

2. Return to Console Interface Main Menu > Site Specific Menu > Feature

Turn On Off command > Enable V5. Do not reboot yet.

3. Return to Site Specific Menu > Call Control Resource Allocation Config-

uration > You will need to modify values in fields other than the

AtmTrunkVccs field in order to free enough resources to enter the value

4096 in the AtmTrunkVccs field.



Chapter 8 Configuring V5.2 European IDLCV5.2 PSTN Implementation

8-2 255-700-447


4. Return to the Console Interface Main Menu window and select the Save

Configuration [Modified] command to save your configuration. After

you select this command, [Modified] is no longer displayed on the win-

dow.

5. Return to Console Interface Main Menu > Diagostics > Reboot Hardware

Components > Reboot Chassis.6. Return to Console Interface Main Menu > Site Specific Menu > V5

Resource Allocation Configuration, enter 010 in Max V5 Interface field >

Apply Configuration.

7. Configure the following module parameters:

a. STM-1 MSP SM/MM for ATM UNI 3

b. DSP2D Voice Server for AlgoSet6 and AAL2 Standard for all DSP

interfaces.

8. Go to the Console Interface Main Menu> Site Specific Menu> V5 Inter-

face Configuration > V5 Interface Table > Add Interface command > At a

minimum, set 3 values:

a. Intf ID from 1 to 10

b. LE Intf field

c. Active Variant IDvalue

9. Apply the Create Interface command.

10. Go to the V5 Interface Configuration > Variant Table command> Add

Variant entry > enter values to V5 Interface Variant Configuration win-

dow.

11. Enter the V5 Variant ID that matches to the V5 Interface Configuration

value.

12. Apply Create Variant command> Bring Into Service.

13. On the V5 Interface Variant Configuration window, select Add Phys Chnl

Table to Variant command > Add PhysCChan Configuration Entry> V5

PhysCChan Cfg Tbl displays > Add PhysCChan Cfg entry > V5 PhysC-

Chanel Cfg window displays

14. On V5 PhysCChannel Configuration window, at a minimum enter val-

ues for these fields:

a. Enter Phys CChan Id fld values. For Protectgroup-1, always use 16.

For Protectgroup-2, use 15 or 31.

15. On the Configure CommCChan ID fld (local), enter a value higher than

0 to force the configLogical CChan ID (remote switch) field appear.16. Select the Add V5 PhysCChan to table command.

17. Return to the V5 PhysCChannel Configuration Table > Contrl + B to the

V5 Interface Variant Configuration window.

18. Do Add E1 Link Table to Variant command > Displays V5 E1 link Cfg Tbl

> Add E1Link Config Entry >



255-700-447 8-3


Chapter 8 Configuring V5.2 European IDLCV5.2 PSTN Implementation

19. At a minimum, enter values for these fields: Link Id, Phys Id, and

LELink Id.

20. Select the Add V5E1Link to table command.

21. Change the Admin Status field to value Unblocked.

22. Apply the Admin Status command.23. On the V5 Interface Variant Configuration window > Add DL Table to

Variant command > V5 Data Link Configuration Table displays.

24. Select Add Data Link Configuration Entry command > V5 Data Link

Configuration window, set the values starting with protection 1.

25. Apply the Add V5 Data Link command.

Note: Use the same logical C channel ID as entered in the V5 phys-

ical C channel configuration and repeat it for all 6 datalinks.

26. On the V5 Interface Configuration window> Bring Into Service

V5.2 User Side Configuration SummaryThe following steps are a summary only. To perform the configuration, see

the procedures after the summary.

1. Configure ATM Trunking on the Site Specific Configuration Window.

Enter the value 4096 in the Max Remote IWF field

2. Apply Configuration and Bring Admin Status Up.

3. Configure the Remote IWF Table node, Add Remote IWF Entry.

4. On the ATM Trunking Remote IWF Configuration window, enter values

to first two fields, select nonswitched as the Remote IWF Trnk Mode.

5. Add Configuration and Bring Admin Status Up.

6. Go Back to Previous Screen; Go to Bearer VCC Table.

7. Perform Add command. At a minimum, enter values for : VccID, Svc

type vbr, SAR aal2, vcc com type pvc, vcc/vpi/vci info, app type: V5, DSP

IWF value None, DSP select type Auto.

8. Add the Configuration command, Bring Admin Status Up.

9. Return toV5 Interface Variant Configuration > select Add UserPort Table

to Variant-> Add entry > On V5 User Port Configuration screen, at a min-

imum, enter the following values:

• LE Port ID: The port ID on the LE side.

• Port Type: Type of port - ISDN or PSTN.

• VccId: The Bearer Vcc Trunk Id corresponding to the IAD for which the

user port is being added.

• Rem IWF ID: The IWF ID of the Bearer VCC corresponding to the IAD.

• LES intf Port ID: Use the IAD Port ID

• Encode Std: use AF 9, 10, 11. The CellPipe IAD supports Af profiles 9

and 10.

• Encoding profile Num: use 9.



Chapter 8 Configuring V5.2 European IDLCV5.2 IWF Device Interoperability

8-4 255-700-447


• VC algorithm depends on encode profile used.

• Tone detect bypass.

• Translate type: alaw to alaw.

Note: You must choose DSP parameters compatible with the Encod-

ing Profiles

10. Add V5 User Port Configuration command

11. Change the value of the Admin Status field to the value Unblocked.

12. Apply V5 Admin Status on V5 User Port Configuration window

V5.2 IWF Device Interoperability

LE Voice Switch Interoperability with the PSAX System

The V5.2 Interface has been tested with the LE voice switches listed in

Table 8-1 and the PSAX system.

V5.2 IAD Interoperability with the PSAX System

The IADs listed in Table 8-2 have been tested with the PSAX V5.2 Interface

on the PSAX system.

Table 8-1. V5.2 Voice Switch Interoperability

Vendor and Model Software Release Signaling Supporting Module

Lucent 5ESS 5EE14 CCS for POTS and

ISDN

23N66 21-Port High-

Density E1 Multiservice

Alcatel S-10 Contact vendor for

details.

CCS for POTS 23N66 21-Port High-


Ericsson AXE-10 Contact vendor for

details.



Nortel DMS 100 Contact vendor for

details.



Siemens EWSD Contact vendor for

details.



Table 8-2. V5.2 IAD Interoperability

Vendor and ModelSoftwareRelease Signaling

WAN

InterfaceType

LAN Interface Type PortLimits

Lucent CellPipe 4A/4AU 3.4.10-R1 CCS/ELCP ADSL 4 analog FXO ports

Lucent CellPipe 4AI 3.4.10-R1 CCS/ELCP ADSL 4 BRI ports

Lucent CellPipe 4H/8H 3.4.10-R1 CCS/ELCP SHDSL 4 or 8 analog FXO ports

Lucent CellPipe 4HI 3.4.10-R1 CCS/ELCP SHDSL 4 BRI ports



255-700-447 8-5


Chapter 8 Configuring V5.2 European IDLCV5.2 ISDN Implementation

V5.2 ISDN Implementation

Select the value Isdn in the Port Type field and follow configuration instruc-

tions on field description tables.

PSTN Configuration

Enabling the V5 Feature

Perform the following procedure to turn on the desired feature from the Fea-

ture Turn ON/OFF option of the Site-Specific Menu.

Note: If necessary, delete previous configuration files on the modules to

be used. From the Console Interface Main Menu > Select the

Diagnostics option > Select the Remove Configuration Files

option.

Begin

Turning On the H.248 Gateway ControlProtocol Feature




2 Select the Feature Turn ON/OFF option.

The Feature Turn ON/OFF Table window is displayed (see Figure 8-2).

The commands on this window are described in Table 8-3. The fields on

this window are described in Table 8-4.

3 Select the desired interface feature in the Feature Id column and press

Enter.

Verilink NetEngine

6104/6108

3.4.10-R1 CCS/ELCP ADSL 4 or 8 analog FXO ports

Verilink NetEngine 6104i 3.4.10 CCS/ELCP ADSL 4 BRI ports

Verilink NetEngine 6300 3.4.10-R1 CCS/ELCP SDSL 8 analog FXO ports

Verilink NetEngine

6504/6508

3.4.10-R1 CCS/ELCP SHDSL 4 or 8 analog FXO ports

Verilink NetEngine 6504i 3.4.10 CCS/ELCP SHDSL 4 BRI ports

RAD LA-110 Contact ven-

dor for details.

CCS/ELCP SHDSL 4 BRI ports

RAD LA-140 Contact ven-

dor for details.

CCS/ELCP SHDSL 4 BRI ports

Table 8-2. V5.2 IAD Interoperability (Continued)

Vendor and ModelSoftwareRelease

SignalingWAN

InterfaceType

LAN Interface Type PortLimits



Chapter 8 Configuring V5.2 European IDLCPSTN Configuration

8-6 255-700-447


Pressing Enter changes the Desired Status column from Disable to

Enable and vice versa. This action also displays the following message in

the status line:

Are you SURE that you want to change the desired status?

(y/n)

4 To accept the change in status, press Y. Press N to not accept the change.


new configuration will take affect only after chassis reboot

Reboot the chassis only when instructed later in the procedures.

Whether you reboot the chassis now depends on what application you

are configuring. Consult the documentation supplied for the application.

If configuring V.5 applications, do not reboot until after you have set the

values on the Call Control Allocation Resource Configuration window

(this guide will remind you at that time).

5 Return to the Console Interface Main Menu window (Ctrl+G) and select

the Save Configuration [Modified] option (Ctrl+A) to save the modifica-

tion. [Modified] is removed from the window when Save Configuration

is selected.

6 If required, reboot the PSAX system, see “Rebooting PSAX Hardware

Components” on page 11-15 for details.

End

Figure 8-1. Site-Specific Menu Window (Feature Turn On/Off Option Selected)



255-700-447 8-7




Figure 8-2. Feature Turn On/Off Window

Table 8-3. Commands for the Feature Turn ON/OFF Table Window

Command Function





Find . . . . . Feature ID: This command is currently not supported.

Go Back to Site-Specific

Menu





8-8 255-700-447


Table 8-4. Field Descriptions for the Feature Turn On/Off Table


Total: 0/0 Default: N/A

Range: 1–6

Format: Numeric

First number: Indicates which Feature ID is cur-

rently selected in the table.

Second number: Indicates the total number of

Feature IDs in the table.

Note: Of the Feature ID field values listed below, you can enable each of the following fea-

tures only once per session: GR303, H248, or V5. Two or more of these features enabled

together is not permitted by the system software.

Feature ID Default: N/A

Range: N/A

Format: Predefined

alphanumeric

Displays the PSAX system features that you can

enable or disable.

Pnni Private network-to-network interface feature.

Note: Currently, this feature cannot be disabled.

Gr303 ITU-T GR-303 local loop emulation services fea-

ture. For examples of applications using the

GR-303 interface, see Configuring the CellPipe™,

Stinger ™ DSLAM, and PSAX Multiservice Media

Gateway as Interworking Functions Using the GR-303

Standard Application Note.

Vipr Virtual Internet Protocol Router feature.

Note: This feature is not currently supported.

H248 Select this value to enable the H.248 protocol fea-

ture.

V5 European V.5 local loop emulation services

feature.

Iua ISDN Q.921 User Adaptation Layer Protocolfeature. Enables OSI Layer 2 ISDN D-channel sig-

nalling between an Media Gateway Controller

(for example, a Softswitch) and a Media Gateway

(for example, a PSAX system) in PRI offload

applications.

AtmSec ATMsecurity feature.

BulkStats Bulk statistics feature.

space memory Default:

PNNI: 67108864

Gr303: 134217728

Vipr: 67108864

H248: 134217728

V5: 134217728

Iua: 67108864

Range: N/A

Format: Numeric

(bytes)

Displays the amount of system memory in bytes

allocated to the feature.



255-700-447 8-9


Chapter 8 Configuring V5.2 European IDLCSetting Call Control Resource Allocation Values

Setting Call Control Resource Allocation Values


tion on the PSAX system.

Begin




2 Select the Call Control Resource Allocation Configuration option.The Call Control Resource Allocation Configuration window is displayed

(see Figure 8-4).

3 Enter values in the fields on this window according to the guidelines pro-

vided in “Configuration Guidelines” on page 8-12,”and Table 8-7.

4 Select the Apply Configuration command to apply the values entered.

The following messages are displayed in the status line:

desired status Default: Enable or

Disable (depends

on the feature)


alphanumeric

Displays whether the feature is to be made opera-

tional or not.

Note: On the Site-Specific Menu window, the

feature options that are displayed between brack-ets [ ] are disabled.

Disable Indicates that the selected enabled feature is to be

made not operational. After selecting this value,

you must reboot the PSAX system to make this

change take effect. After the system reboots,

Disabled is displayed in the current status field.

Enable Indicates that the selected disabled feature is to be

made operational. After selecting this value, you

must reboot the chassis to make this change take

effect. After the system reboots, Enabled is dis-

played in the current status field.

current status Default: N/A

Range: N/A

Format: Predefined

alphanumeric

Displays the current operational status of the fea-

ture.

Disabled Indicates that the selected feature is currently not

operational.

Enabled Indicates that the selected feature is currently

operational.

Table 8-4. Field Descriptions for the Feature Turn On/Off Table (Continued)





8-10 255-700-447


Applying the resource allocation configuration...

Resource allocation configuration has been applied.

Need to save configuration and reboot system to take effect.

5 Press Ctrl+G to return to the Console Interface Main Menu window, and

save the configuration.

6 Perform the chassis reboot procedure at this time. The path to follow is

from the Console Interface Main Menu > Diagnostics > Reboot Hardware

Components > Reboot Chassis.

End

Figure 8-3. Site-Specific Menu Window



255-700-447 8-11




Figure 8-4. Call Control Resource Allocation Configuration Window

Table 8-5. Commands for the Call Control Resource Allocation Configuration Window

Command Function

Apply Configuration Applies the values you entered on this window.





8-12 255-700-447


Configuration Guidelines

Table 8-6. Field Descriptions for the Call Control Resource Allocation Configuration Window


Important: The ranges of values for numeric fields are software imposed. When changing the val-

ues in these fields, keep in mind that the PSAX system calculates the percentage of the memoryallocation usage from the combination of values you have entered in the fields. This calculation is

displayed in the callContrlResAllocUsage field. When all the values of SVC calls and parties, SPVC

calls, Connection Gateway API endpoints, and Connection Gateway API calls and parties are calcu-

lated as a percentage of memory allocation, this percentage value cannot exceed 100 percent of the

memory allocation. If you enter a combination of values that exceeds 100 percent when calculated

by the system, the following error message is displayed: T-CallControlResAllocFail. If you

receive this error message, adjust the values in the fields and use the Apply Configuration com-

mand to recalculate the allocation usage percentage value. When you enter a combination of values

that correctly results in a value of 100 percent or less, the following informational message is dis-

played: Resource allocation configuration has been applied. Need to save configura-

tion and reboot the system to take effect.

svcPtToPtCalls Default: 002000

Range: 0–15000

Format: Numeric


calls to be supported by the PSAX system.

H.248 Applications: For AAL2, this field must be

greater than or equal to the sum of the values in the

atmTrunkNarrowBandCalls and atmTrunkVccs fields.

Set this field to the same value as the

sgApiPtToPtSvcCalls field. For example, if the Maxi-

mum Number of Contexts field on the H.248 Transport

and Resource window is set to 4000 and the Maximum


8000, then the recommended values for this field are

4000 for AAL1 and 4100 for AAL2.

svcPtToMultiPtCalls Default: 002000

Range: 0–4000

Format: Numeric




svcPtToMultiPtPar-

ties

Default: 002000

Range: 0–4000

Format: Numeric


point-to-multipoint calls to be supported by the PSAX

system. Set the value in this field to be greater than or

equal to the value in the svcPtToMultiPtCalls field,

because each point-to-multipoint call must have at

least one party.




255-700-447 8-13



Important: If you have already configured your PSAX system and you are considering changing the

sum of the values in the SPVC point-to-point calls fields, keep in mind that the sum of these values

cannot be less than the actual number of SPVC connections already configured in the PSAX system

SPVC table, which is stored in the PSAX system database.spvcCePtToPtCalls Default: 001000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC circuit emu-

lation point-to-point calls to be supported by the PSAX

system. Set the values in the SPVC point-to-point call






Per Node.”



total number of calls specified in all of the SPVC callfields and the number of ATM trunk VCCs cannot

exceed 32 calls.


spvcTePtToPtCalls Default: 000100

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC terminal

emulation point-to-point calls to be supported by the

PSAX system. Set the values in the SPVC point-to-

point call fields (spvcCePtToPtCalls, spvcTePtToPtCalls,

spvcAtmPtToPtCalls, and spvcFrPtToPtCalls) so that the

sum of their values does not exceed the maximum

number of duplex calls per node for SPVCs as indicated

in the table entitled “PSAX System Performance Capa-

bilities Per Node.”





exceed 32 calls.







8-14 255-700-447


spvcAtmPtToPtCalls Default: 002000

Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC ATM point-

to-point calls to be supported by the PSAX system. Set

the values in the SPVC point-to-point call fields

(spvcCePtToPtCalls, spvcTePtToPtCalls, spvcAtmPtToPt-Calls, and spvcFrPtToPtCalls) so that the sum of their

values does not exceed the maximum number of

duplex calls per node for SPVCs as indicated in the


Per Node.”





exceed 32 calls.


spvcFrPtToPtCalls Default: 000900Range: 0–10000

Format: Numeric

Specifies the maximum number of SPVC frame relaypoint-to-point calls to be supported by the PSAX sys-

tem. Set the values in the SPVC point-to-point call






Per Node.”





exceed 32 calls.


spvcPtToMultiPt-

Calls

Default: 000500

Range: 0–500

Format: Numeric

Specifies the maximum number of SPVC point-to-mul-






exceed 32 calls.


spvcPtToMultiPt-

Parties

Default: 001000


Specifies the maximum number of parties on SPVC

point-to-multipoint calls to be supported by the PSAXsystem.





exceed 32 calls.






255-700-447 8-15



aal2CirAtmSpvcVcc

Calls

Default: 001000

Range: 0–4000

Format: Numeric

Specifies the maximum number of circuit emulation-

to-ATM standard AAL2 SPVC calls to be supported by

the PSAX system.


aal2VbrAtmSpvcVc

cCalls

Default: 000100

Range: 0–4000

Format: Numeric

Specifies the maximum number of VBR-to-ATM stan-

dard AAL2 SPVC calls to be supported by the PSAX

system.


sgApiCirEmEndPts Default: 001000

Range: 0-15000

Format: Numeric

Specifies the maximum number of circuit emulation

endpoints for the Connection Gateway API to be sup-

ported by the PSAX system.


sgApiAtmSvcEnd-

Pts

Default: 000000

Range: 0-15000

Format: Numeric

Specifies the maximum number of ATM SVC end-

points for the Connection Gateway API to be sup-

ported by the PSAX system.H.248 Applications: Set the value in this field to 0.

sgApiPtToPtSvc-

Calls

Default: 000000

Range: 0-15000

Format: Numeric


calls for the Connection Gateway API to be supported

by the PSAX system.

H.248 Applications: Specifies the maximum number of

point-to-point calls controlled through the H.248 pro-

tocol feature. Set this field to the same value as the

svcPtToPtCalls field. For example, if the Maximum

Number of Contexts field on the H.248 Transport and

Resource window is set to 4000 and the Maximum


8000, then recommended values for this field are 4000for AAL1 and 4100 for AAL2

sgApiPtToMultiPtS-

vcCalls

Default: 000000

Range: 0-4000

Format: Numeric


tipoint calls for the Connection Gateway API to be sup-

ported by the PSAX system.


sgApiPtToMultiPt-

Parties

Default: 000000

Range: 0-4000

Format: Numeric


point-to-multipoint calls for the Connection Gateway

API to be supported by the PSAX system.







8-16 255-700-447


atmTrunkVccs Default: 000100

Range: 1–4096

Format: Numeric

Specifies the maximum number of VCCs supported by

ATM trunking.


Enabled in the spvcGlobalPriorityScheme field, thetotal number of calls specified in all of the SPVC call


exceed 32 calls.

H.248 Applications: Specifies the maximum number

of AAL2 trunks. For AAL1 call setups, this field does

not apply and should be set to 0. For example, if the

Maximum Number of Contexts field on the H.248

Transport and Resource window is set to 4000 and the

Maximum Number of Terminations field on that win-

dow is set to 8000, then recommended values for this

field are 0 for AAL1 and 100 for AAL2.

V5.2 Applications: You can enter up to the value 4096.If you enter 4096, be sure that you have first freed

enough resources in other fields in order to enter a

high value in the atmTrunkVccs field.

atmTrunkNarrow-

BandCalls

Default: 001000

Range: 1–4000

Format: Numeric

Specifies the maximum number of switched narrow-

band calls supported by ATM trunking.

H.248 Applications: Specifies the maximum number

of simultaneous calls through AAL2. For AAL1 call set-

ups, this field does not apply and should be set to 0.

For example, if the Maximum Number of Contexts

field on the H.248 Transport and Resource window is

set to 4000 and the Maximum Number of Termina-

tions field on that window is set to 8000, then recom-

mended values for this field are 0 for AAL1 and 4000

for AAL2

[callContrlResAllo-

cUsage %]

Default: 0098

Range: 0–100

Format: Numeric

Displays the percentage of memory allocated to call

control. A portion of the total system memory is allo-

cated for call control. The value in this field represents

the amount of this allocation that is currently in use.

This percentage value is calculated by the system from

the values you enter in the other fields.





255-700-447 8-17



The maximum numbers for PVC, SPVC, and SVC duplex calls per connection

type available on the PSAX system, as well as the call setup rate for all types

of CPUn modules, are shown in Table 8-7.

cgSvcCutThrough-

Option

Default: cgSvcAcIm-

plicitCutThrough

Range: N/A


Specifies whether the PSAX system or the connection

gateway device (connection manager) sends a cut-

through message to initiate an SVC connection.

Note: The value in this field is relevant only if youhave enabled a media gateway control feature (the

Connection Gateway API feature or the H.248 protocol

feature).

cgSvcAcImplicit-

CutThrough

Indicates that the PSAX system sends a cut-through

message to the connection gateway device to initiate

an SVC connection.

cgSvcAcExplicit-

CutThrough

Indicates that the connection gateway device deter-

mines when to send a cut-through message to the con-

nection manager to initiate an SVC connection.

H.248 Applications: You must use the value

cgSvcAcExplicitCutThrough if you are using the

H.248 protocol feature.

spvcGlobalPriority-

Scheme

Default: Disabled

Range: N/A

Format: Predefined

alphanumeric

Specifies whether the PSAX systemwide priority

scheme must be supported for all SPVCs and SPVC

trunks.

Disabled Indicates that the priority scheme is not in force (dis-

abled).

Enabled Indicates that the priority scheme is in force (enabled).

If you select the value Enabled in this field, the total

number of calls specified in all of the SPVC call fields

and the number of ATM trunk VCCs cannot exceed 32

calls.Note: For SPVC reconnections in priority scheme-

enabled trunks in an IMA link, the limit is 32 SPVCs.



Table 8-7. PSAX System Performance Capabilities Per Node for Release 9.0.0

Connection TypeMaximum Numberof Duplex Calls per

Node

Call Set-up Rate forCPU2 and CPU3L

Modules*

Call Set-up Rate forCPU3 and CPU4

Modules*

PVC 60,000 N/A N/A

SPVC 10,000† 60 calls per second 100 calls per second

SVC 15,000† 60 calls per second 100 calls per second

All connections

combined

60,000‡

* A CPU3 or CPU4 module paired in the same chassis with a CPU2 or CPU3L mod-

ule will operate at the lower CPU2/CPU3L module call rate.




8-18 255-700-447


Accessing the V5 Resource Allocation Configuration Window

Begin

Accessing the V5 Resource Allocation Configuration Window, Part 1

1 From the Console Interface Main Menu, select the Site Specific Menu

(see Figure 8-3).

2 From the Site Specific Menu, select the V5 Interface Configuration(w) command. The V5 Interface Configuration window is displayed (see

Figure 8-5). Table 8-8 describes the options on the window.

The menu options on this window perform the following functions:

† When using both SPVC and SVC connection types, you can set up any combina-

tion of calls as long as you do not exceed 100% of the call control resource mem-

ory allocation (callContrlResAllocUsage field on the Call Control Resource Alloca-

tion Configuration window).Refer to the configuration guidelines in the field

description table for this window.‡ For all three types of connections, you cannot configure more than the maximum

number of duplex calls indicated. For OAM monitoring the maximum number ofcalls that can be monitored in one direction is 2,000, and the maximum number

of calls that can be monitored in both directions is 1,000.

Figure 8-5. V5 Interface Configuration Window



255-700-447 8-19



3 On the V5 Interface Configuration window, select the V5 Resource

Allocation Configuration option. The V5 Resource Allocation Config-

uration window is displayed (see Figure 8-6). Table 8-9 describes the

commands on the window. Table 8-10 describes the fields on this win-

dow.

4 Enter the value 010 in the Max V5 Interface field.


6 Remain on this window and proceed with the following procedure,

“Accessing the V5 Resource Allocation Configuration Window” on

page 8-18.

End

Table 8-8. Commands for the V5 Interface Configuration Menu Window


V5 Interface Configuration Displays the V5 Interface Configuration window.

V5 Variant Table Displays the V5 Variant Table.

[V5 Statistics] The V5 Statistics window is not currently supported.V5 Resource Allocation Con-

figuration

Displays the V5 Resource Allocation Configuration.

Go Back to Site Specific Menu Redisplays the Site Specific Menu.

Figure 8-6. V5 Resource Allocation Configuration Window




8-20 255-700-447


Table 8-9. V5 Resource Allocation Configuration Window

Command Function

Apply Configuration Applies the configuration values you entered in the

fields on the window..

Go Back to V5 Menu screen Re-displays the V5 Interface Configuration window.

Table 8-10. Field Descriptions for the V5 Resource Allocation Configuration Window


Max V5 Interface Default: 004

Range: 0–10

Format: Numeric

Indicates the maximum number of V5 interfaces

that can be supported in this system.

Max User Ports Default: 008000

Range: 1–8000

Format: Numeric

Indicates the maximum number of User Ports

that can be used in this system. This includes

both PSTN and ISDN ports.

Max User Ports/V5Interface Default: 008000Range: 1–8000

Format: Numeric

Indicates the maximum number of User Ports perV5 interface. This includes both PSTN and ISDN

ports per V5 interface.

Max Isdn Ports Default: 008000

Range: 1–8000

Format: Numeric

Indicates the maximum number of ISDN ports

that can be supported in this system. This value is

less than or equal to the Max User Ports value. A

non-zero value for this parameter does not neces-

sarily imply that maximum number of PSTN

ports is the number of Max User Ports minus the

number of Max Isdn Ports.

Max Isdn Ports/V5

Interface

Default: 008000

Range: 1–8000

Format: Numeric

Indicates the maximum number of ISDN ports

per V5 interface. This value is always less than or

equal to the value of the Max User Ports /V5Interface field. A non-zero value for this parame-

ter does not necessarily imply that maximum

number of PSTN ports/V5 interface is this value

minus the value of the Max Isdn Ports/V5 Inter-

face field.

TPL1 Timer Default: 15

Range: 1–30

Format: Seconds

This timer is used by the ISDN basic rate access

(BRA) port manager to supervise the unblock

procedure of a port. Values are represented in

seconds.

T1 Timer Default: 15

Range: 1–30

Format: Seconds

This timer is used by the BRA port manager to

supervise the access activation procedure of a

port. Values are represented in seconds.

BccTbcc5 Timer Default: 1000

Range: 500–1500

Format: msec

This timer is used by the Bearer Channel Control

(BCC) protocol. An AN fault message is sent to

LE whenever AN detects the internal failure and

starts this timer. AN is expected to receive the AN

fault acknowledge message within this time. The

values are represented in milliseconds.



255-700-447 8-21



SetSA7Bit Timer Default: 050

Range: 50–200

Format: Msec.

This timer is used to guarantee that the SA7 bit is

set to zero before the message is sent to LE that

says the bit has been set. Values are represented

in milliseconds.ReadSA7Bit Timer Default: 050

Range: 50–200

Format: Msec.

This timer is used to guarantee that the SA7 bit

change has been reported to the AV5 stack. When

a message is received from the LE indicating the

SA7 bit is set to zero, the AV5 stack waits for the

ReadSA7BitTimer value before it reads the status

from Layer 1 FSM. Values are represented in mil-

liseconds.

LinkId Timeout Default: 00

Range: 0–30

Format: N/A

This timer is used for the Link Id procedure. This

is the maximum time the AN should take to com-

plete the Link Id procedure. This timer can be dis-

abled by setting this value to 0.

Max ISDN Pra Ports Default: 100

Range: 1–100

Format: Numeric

Specifies the maximum number of primary rateaccess (PRA) ports that can be supported by the

PSAX system.






8-22 255-700-447


Configuring the ATMModule for V5.2

See the appropriate PSAX module user guide to configure the connection

interface as ATM UNI 3.0.

Note: This sample configuration uses the STM-1 MSP SM module on an

ATM UNI 3.0 interface.

Configuring theDSP2D for Algoset 6and AAL2 Standard

See the PacketStar

®

PSAX System Connections Provisioning Guide to configure theconnection parameters for AlgoSet6 and SAR type Aal2Std.

Accessing the V5 Interface Configuration Window

Perform the following procedure to access the V5 Interface Configuration

window. This window lists the created V5 interfaces and enables you to cre-

ate new interface IDs.

Target DSP Over

Subscription

Default: 20000%

Range:

Format:

Specifies the limit of the DSP resource oversub-

scription for V5 voice calls. A trap will be sent if

the oversubscription goes beyond this limit due

to the configuration of the ISDN ports.Note: The value is given in %, so 25% means the

resources will be undersubscribed and 800%

means the resources can be oversubscribed up

to 8 times.

[Current DSP Over

Subscription]

Default: 60000%

Range:

Format:

Specifies the current value of the DSP chip

resources oversubscription for V5 voice calls. The

calculation of the current DSP resource oversub-

scription in the chassis is as follows:

the number of DSP resources left in the chassis

after configuration = [{(number of DSP2D mod-

ules * 384) – number of AAL2 trunks} – (number

of AAl2 trunks * no. of ISDN ports/trunk)]. Thepreceding formula assumes that 1 DSP resource is

needed for ELCP connection per IAD and 1 DSP

resource is required for the D channel per ISDN

port on an IAD). To calculate oversubscription =

(no. of B channels for ISDN + no. of PSTN ports

configured) / (no. of DSP resources left in the

chassis after configuration). There are 30 B chan-

nels for PRA and 2 Bchannels for BRA. The value

is expressed as a percentage (see Note in Descrip-

tion for Target DSP). This calculation of the over-

subscription is valid only if the Least Used algo-

rithm is chosen for the DSP resource allocation

scheme.

[Max E1s] Default: 064

Range: 1–160

Format: Numeric

This indicates the maximum number of E1 links

that can be supported in this system. 84 E1 Inter-

faces * 3 = 3-Port Channelized DS3.





255-700-447 8-23



Begin

Accessing the V5 Interface Configuration Window, Part 1

1 From the Console Interface Main Menu, select > Site Specific Menu> V5

Interface Configuration option. The V5 Interface Table is displayed (see

Figure 8-7). Table 8-11 describes the commands and Table 8-12 describes

the display-only fields on the window.

2 Remain on this window and continue with the next procedure.

End

Figure 8-7. V5 Interface Table Window

Table 8-11. Commands for the V5 Interface Table Window

Command Function



Top Scrolls to the top of the current page.

Bottom Scrolls to the bottom of the current page.

Add an Interface Displays the V5 Interface table.

Go Back to V5 Menu screen Re-displays the V5 Interface Configuration window.

Table 8-12. Field Descriptions for the V5 Interface Table Window

Command Function

V5 Interface ID Displays the V5.2 interface ID.




8-24 255-700-447


Adding New Interfaces

Perform the following procedure to add V5 interfaces to the V5 Interface

Table.

Begin

1 From the V5 Interface Table, Select the Add an Interface command.

The V5 Interface Configuration window is displayed. Table 8-13 describes

the commands on the window. Table 8-14 describes the configurable

fields on this window.

2 At a minimum, enter values for these fields:

• V5Intf field

• LE Interface Id

• Active Variant ID

3 Select the Create Interface command.


End

Admin Status Specifies whether the interface is up or down.

Total 0/0 The first number in this field indicates the num-

ber of the V5 Interface ID Data Link on the first

line of the window. The second number indicates

the total number of V5 Interface ID Data Link

table entries on the table.

Table 8-12. Field Descriptions for the V5 Interface Table Window (Continued)

Command Function



255-700-447 8-25



Figure 8-8. V5 Interface Configuration Window

Table 8-13. Commands for the V5 Interface Configuration Window

Command Function

Create Interface Creates the V5 interface.

Apply Configuration Applies the values entered on the fields on the window.

Update Updates the window values after a field value change.

Delete Interface and return Deletes the interface and returns to the V5 Interface

Table.

Bring Into Service Brings the variant into service.

Take (n) OutOfService Takes the variant out of service.

Apply Variant SO Command Switches the channel or trunk to an alternate config-

ured channel or trunk.

Variant Table Displays all configured alternate channels or trunks.

Go Back to V5 Intf Table Returns to the V5 Interface Table.




8-26 255-700-447


Table 8-14. Field Descriptions for the V5 Interface Configuration Window


V5Intf ID: Default: 0

Range: 1–10

Format: Numeric

Specifies the ID the PSAX uses internally for the

interface after the interface is created.

Note: Although the status line on your window

indicates configurable values of 1–127, only 1–10interface IDs are supported in Release 8.0.0.

[Admin Status] Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Specifies the administrative status of the inter-

face.

OutOfService The interface is not in service.

InService The interface is in service.

[Oper Status] Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Specifies if any factor is impeding the configured

interface from operating.

OutOfService Some factor is impeding the interface from oper-

ating.

InService The interface is in service with no impedances.

Active Variant ID Default: 0

Range: 0–127

Format: Numeric

Specifies the Variant Id which is active for this V5

Interface. Only one variant is the active ID. Vari-

ants permit an interface group to have multiple

configurations to connect to the voice switch.

Changing variants only affects the network por-

tion from the Gateway to the voice switch. The

network portion from the gateway to the sub-

scriber is not affected.Note: Whenever the Active variant is changed,

“database contaminated” bits will be marked and

the user has to explicitly save the configuration.

LE Interface ID Default: 0

Range: 0–16777215

Format: Numeric

Specifies the local exchange interface ID used by

the 5ESS. This ID is used externally by the PSAX

to communicate with the 5ESS.

Switchover Variant

ID

Default: 0

Range: 0–127

Format: Numeric

Specifies the Variant Id to which the current

active variant is to be switched.

Variant SO Com-

mand

Default: NoAction


Specifies whether active or standby switchover is

used.

NoAction No switchover action is specified.

NormalSwitchTo-

Standby

This command is used to switch manually from

active to standby variant.

Note: The database must be saved after any Vari-

ant SO command is applied.



255-700-447 8-27



Accessing the V5 Variant Table

Perform the following procedure to view available V5 variants and create

new variants.

Begin

1 From the V5 Interface Configuration window, select the Variant Table

command. The V5 Intf Variant Table is displayed (see Figure 8-9).

Table 8-15 describes the commands and Table 8-16 describes the fields on

this window.

2 Select the Create Variant command.

3 Select the Bring Into Service command.


End

Figure 8-9. V5 Intf Variant Table Window

Table 8-15. Commands for the V5 Intf Variant Table Window

Command Function





Find... Intf ID: ... ID: Finds the interface ID and the variant ID of a par-

ticular connection.




8-28 255-700-447


Accessing the V5 Interface Variant Configuration Window

Perform the following procedure to create and configure V5 variants.

Begin

1 From the V5 Intf Variant Table select the Add Variant Entry command.

The V5 Interface Variant Configuration window displays (see

Figure 8-10). Table 8-17 describes the commands and Table 8-18

describes the fields on this window.

2 Enter the values as described in Table 8-18 and when completed select

the Apply the Configuration command.

Add Variant Entry Displays the V5 Interface Variant Configuration

window.

Go Back to Previous screen Displays the V5 Interface Configuration window.

Table 8-15. Commands for the V5 Intf Variant Table Window (Continued)

Command Function

Table 8-16. Field Descriptions for the V5 Interface Variant Table Window

Field Name Field Value Field Description

V5 Intf ID Default: 0

Range: 1–10

Format: Numeric

Specifies the V5 interface identifier.

V5 Variant ID Default: 0

Range: 0–127

Format: Numeric

Specifies the V5 variant identifier.

[Admin Status]

(display only)

Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Specifies the Administrative status of the Variant

channel.

OutOfService Indicates that the variant channel is not in ser-

vice.

InService Indicates that the variant channel is in service.

[Var Protection Sta-

tus] (display only)

Default: Active

Range: N/A

Format: Predefined

Specifies whether the variant protection status is

active or inactive.The displayed value shows

which variant is active/standby in this particular

V5 interface.

Active Indicates that this variant is active and opera-

tional.

Passive Indicates that this variant is not active but in

standby mode.



255-700-447 8-29




End

Figure 8-10. V5 Interface Variant Configuration Window

Table 8-17. Commands for the V5 Interface Variant Configuration Window

Command Function

Add PhysChnl Table to Variant Displays the V5 PhysCChannel Configuration Table

window.

Add E1 Link Table to Variant Displays the V5 E1 Link Configuration Table window.

Add DL Table to Variant Displays the Data Link Configuration Table window.

Add UserPort Table to Variant Adds the UserPort table to the variant configuration.

Create Variant Creates a variant configuration link.

Apply Configuration Applies the configuration.

Update Updates the configuration.

Delete Variant and return Deletes the variant configuration link and returns to

the V5 Intf Variant Table window.

Bring Into Service Brings the variant configuration in to service.

Go Back to V5 Variant Table Redisplays the V5 Intf Variant Table window.




8-30 255-700-447


Table 8-18. Field Descriptions for the V5 Interface Variant Configuration Window


V5 Intf ID Default: 0

Range: 1–10

Format: Numeric

Specifies the V5 interface identifier.

Default: 0

Range: 1–127

Format: Numeric

Specifies the V5 variant identifier.

[Admin Status] Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Specifies the Administrative Status of the Variant

channel.

OutOfService The variant channel is not in service.

InService The variant channel is in service.

[Var Protection Sta-

tus]

Default: Active

Range: N/A

Format: Predefined

Specifies whether the variant protection status is

active or inactive. This fields also shows whichvariant is active or passive in this particular V5

interface.

Active Active shows this variant is active and opera-

tional.

Passive Passive shows this variant is not active but in

standby mode.

[Interface Type] Default: V52

Range: N/A

Format: Predefined

V.5.2 standard as defined in ETSI EN 300 347-x.

Type of V5 interface being provisioned. V5.2 is

most widely used by customers as it has addi-

tional feature sets over V5.1.

Interface Edition Default: SecondEdi-tion

Range: N/A

Format: Predefined

Specifies the V5 interface edition being provi-sioned. First Edition and Second Edition differs in

the application of these procedures:

• Periodic Pulse Metering

• Accelerated Alignment

• V5 Interface startup

Refer to ETSI EN 300 324-1 V2.1.1, Section 13.1.2 for

details.

FirstEdition First edition interface is used

SecondEdition Second edition interface is used.



255-700-447 8-31



Align Ports Method Default: V5SecondE

ditionPortAlign

Range: N/A


Indicates type of flag used for port alignment

method to use along with interface type.

V5PortAlignUndefi

ned

Port align protocol not defined.

V5PortIndividualP

ortAlign

Informs the V5 stack to unblock all relevant PSTN

and ISDN ports one by one.

V5FirstEditionPort

Align

Informs the V5 stack to unblock all relevant PSTN

and ISDN ports as a single entity.

V5SecondEditionP

ortAlign

Informs V5 stack to unblock or block all relevant

PSTN and ISDN ports as a separate entity.

AN Initiate Link

Proc

Default: False

Range: N/A

Format: Predefined

This flag indicates whether the Access Network or

Local Exchange initiates the Link Id procedure. Iftrue, the AN should initiate it. If False, the LE

should initiate it.

False False informs the V5 stack not to initiate the link

identification procedure.

True True informs V5 stack to initiate the link dentifi-

cation procedure.

[L1 Fsm Normal

Timer]

Default: 500

Range: 1–1000

Format: msec

Specifies the L1 finite state machine normal

timer, that the E1 facility uses to enter into the

NORMAL operational state. Values are given in

milliseconds.

[L1 Fsm LosOrLosTimer]

Default: 2500Range: 1–2500

Format: msec

Specifies the L1 finite state machine loss of signalor loss of frame timer for the E1 facility to enter

into the non-operational state when LOS/LOF is

set. Values are given in milliseconds.

[L1 Fsm Ais Timer] Default: 2500

Range: 1–2500

Format: msec

Specifies the L1 finite state machine alarm indica-

tor signal timer that the E1 facility uses to enter

into the non-operational state when there is an

alarm indication. Values are given in millisec-

onds.

[L1 Fsm Rai Timer] Default: 2500

Range: 1–2500

Format: msec

Specifies the L1 finite state machine RAI signal

timer for the E1 facility to enter into the non-

operational state when an RAI occurs. Values are

given in milliseconds.Resource Manager

TR1

Default: 500

Range: 500–1500

Format: msec

Specifies the timer used by resource manager to

send BCC:ALLOCATION REJECT message if it

does not receive a V5ConnectComplete message

within this time. Values are given in milliseconds.

Table 8-18. Field Descriptions for the V5 Interface Variant Configuration Window (Continued)





8-32 255-700-447


Accessing the V5 Physical C-Channel Configuration Table

Begin

1 From the V5 inft Variant Configuration window, select the Add Phy-

sChnl Table to Variant command.2 The V5 PhysCChannel Configuration Table displays (see Figure 8-11).

Table 8-19 describes the commands and Table 8-20 describes the fields on

this window.

3 Remain on this table on continue with the next procedure.

End

Figure 8-11. V5 Physical C-Channel Configuration Table Window

Table 8-19. Commands for the V5 Physical C-Channel Configuration Table Window

Command Function





Find...Intf ID...Variant ID...Phy-

sCChan

Finds the interface ID, variant ID and physical C-

channel of a particular connection.

Add PhysCChan Config Entry Displayes the V5 PhysCChannel Configuration

window.

Go Back to Previous Screen Returns to the V5 Interface Variant Configuration

window.



255-700-447 8-33



Accessing the V5 Physical C-Channel Configuration Window

Begin

1 On the V5 PhysCChannel Configuration Table, select the Add PhysC-

Chan Config Entry command. The V5 PhysCChannel Configuration

window displays (see Figure 8-12). Table 8-21 describes the commands

and Table 8-22 describes the fields on this window.

2 At a minimum, enter values for these fields: Phys CChan Id, Protection

group num Pg-1 (channel 16); ConfigCommCChan Id (enter value

greater than 0), and ConfigLogical CChan Id.

3 After selecting values, select the Add V5 PhysCChan to the table

command.

4 Press Ctrl+B twice to return to the V5 Intf Variant Configuration window.Remain on window and continue with next procedure.

End

Table 8-20. Field Descriptions for the V5 Physical C-Channel Configuration Table Window

Command Function

Total: 0/0 The top number shows which table entry is selected;

the bottom number shows total number of entries on

the table.

Intf ID Displays the interface ID.

Variant ID Displays all the variant IDs for the Interface ID.

PhysCChan Displays the physical C channel for the interface ID.

OperStatus Displays the operating status of the connection.

P Status Displays protection status, either primary or standby.




8-34 255-700-447


Figure 8-12. V5 Physical C-Channel Configuration Window

Table 8-21. Commands for the V5 Physical C-Channel Configuration Window

Command Function

Add V5PhysCChn to the table Adds the V5 physical C-channel entry to the V5

PhysCChannel Configuration Table.

Apply V5PhysCChn configuration Adds the configuration values you set to the net-

work database.

Update V5PhysCChn in the table Refreshes any changes made to V5 Phys C-Channel

entries in the table.

Delete V5PhysCChn and return Deletes the V5 Phys C-Channel and returns to the

V5 PhysCChannel Configuration Table.

Go to the LogCChan Configuration Displays the Logical C-Channel Configuration Table.

Go Back to Previous Screen Returns to the V5 Phys ical C-Channel Configura-

tion Table.



255-700-447 8-35



Table 8-22. Field Descriptions for the V5 Physical C Channel Configuration Window


Interface ID Default: 0

Range: 1–10

Format: Numeric

This index identifies the V5 Interface configura-

tion table.

Variant Id Default: Active

Range: 0–127

Format: Numeric

This index identifies the variant number in the

V5 interface.

PhysicalC-ChanId Default: 0

Range: 1–44

Format: Numeric:

SSPPCCC

Specifies the physical C-channel ID. This index

identifies the physical channel. This value is user-

assigned. The number value is interpreted as

SSPPCCC , where SS is the module slot, PP is the

port number, and CCC is the channel number.

The C-channel is a 64-Kbps time slot on a V5.2

interface that is assigned to carry logical C-chan-

nels. A physical C-channel may not be used to

carry bearer traffic channels.ConfigCommC

Chan Id

Default: 0

Range: 1–44

Format: Numeric

Identifies the logical C-channel. If it is 0, then this

entry is used as the standby physical C-channel;

otherwise, this value is used as the Active logical

C-channel. 44 Active logical C-Channels and 4

Standby physical C-channels are allowed. This

value shows the initial mapping at provisioning

time. This mapping may be changed during runt-

ime using the protection switchover command,

which is shown using the OperLogicalCChanId

field value. You must enter a value higher than 0

for the channel to be active. Entering a value

higher than 0 causes the ConfigLogicalCChanId

field (see below) to become visible on the win-

dow for configuration.

ConfigLogical

CChan Id

Default: 0

Range: 1–65503

Format: Numeric

This identifies the logical C-channel that is

exchanged between AN and LE on the remote

switch side. This field displays only when the

ConfigCommCChan Id field above is set to the

value 1 or higher.

ISDN Applications: Select one of the values in

this field and enter in the P-Logical Chan ID, F-

Logical Chan ID, and D-Logical Chan ID fields on

the V5 User Port Configuration Window.




8-36 255-700-447


Protection Group

Num

Default: Pg-1

Range: N/A

Format: Predefined

Specifies whether this logical/physical channel

belongs to Protection Group Number 1 or 2. Pro-

tection Group 1 always uses the user-assigned

timeslot value 16. Protection Group 2 uses thetimeslot value 15 and 31 (2 timeslots are neces-

sary to provide sufficient bandwidth on V5.1 sys-

tems with ISDN and most V5.2 systems).

Pg-1 Pg-1 supports one active C-Channel and one

Standby C-Channel where N1 = 1, K1 = 1.

Pg-2 Pg-2 supports 1 <= N2<(3*L-2-K2) Active

C-Channels where L = number of E1 links, and

1<=K2<=3 Standby C-Channels.

[OperCommCChan

Id]

Default: 500

Range: 0–44

Format: Numeric

This indicates the current logical C-channel to

physical C-channel mapping. If it is 0, then this

entry is used as Standby physical C-channel; oth-

erwise, this value is used as Active logicalC-channel. 44 Active logical C Channels and 4

Standby physical C-channels are allowed. This

shows the current active mapping.

[OperLogical

CChan Id]

Default: 0

Range: 0–65503

Format: Numeric

This identifies the logical C-channel that is

exchanged between AN and LE.

[Protection Status] Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Indicates whether this physical C Channel is

active, standby, or out of service.

OutOfService This physical C-Channel is out of service.

Active This physical C-channel is actively transmiting

signalling messages.

Standby This channel is the standby physical C-channel to

carry signalling messages.

[Operational Sta-

tus]

Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Specifies the operational status of physical chan-

nel.

OutOfService This physical C-channel is currently out of ser-

vice.

InService This physical C-channel is currently in service.

Table 8-22. Field Descriptions for the V5 Physical C Channel Configuration Window (Continued)




255-700-447 8-37



Accessing the V5 E1 Link Configuration Table

Begin

1 From the V5 Interface Variant Configuration window, select the Add E1

Link table to Variant command. The V5 E1Link Configuration Tabledisplays (see Figure 8-13). Table 8-23 describes the commands and

Table 8-24 describes the fields on this window.

2 Remain in the window and continue with the next procedure.

Figure 8-13. V5 E1 Link Configuration Table Window

Table 8-23. Commands for the V5 E1 Link Configuration Table Window

Command Function




Bottom Scrolls to bottom of the current page.

Find...Intf ID: Variant ID: Finds the interface ID and variant ID of a partic-

ular connection.

Add E1Link Config Entry Adds an E1 link configuration entry.

Go Back to Previous Screen Returns to the V5 Intface Variant Configuration

window.




8-38 255-700-447


Accessing the V5 E1 Link Configuration Window

Begin

1 fFrom the V5 E1Link Configuration Table, select the Add E1Link Con-

fig Entry. The V5 E1Link Configuration window displays (see



2 Enter the values you need.

3 After all values are entered, change the Administrative Status field to a

setting other than ForceBlocked (the ForceBlocked setting prevents

any call processing functions from occurring).

4 Apply the Apply Administrative Status command. Repeat steps 2 and

3 for all E1 links you want to bring into service.

5 If you are using the High Density E1 module in your configuration, and

want to activate specific timeslots, continue to the next procedure.

End

Table 8-24. Field Descriptions for the V5 E1 Link Configuration Table Window

Command Function


Variant ID Displays all the variant IDs for the Interface ID.

LinkID Displays the link ID of the interface ID.

OperStatus Displays the operating status of the connection.



255-700-447 8-39



Figure 8-14. V5 E1 Link Configuration Window

Table 8-25. Commands for the V5 E1 Link Configuration Window

Command Function

Go To Timeslot Channel Table Displays the Timeslot Channel Table window.

Go Back to Previous Screen Returns to the previous window.

Table 8-26. Field Descriptions for the V5 E1 Link Configuration Window


Interface Id Default: 0

Range: 1–10

Format: Numeric

Specifies the interface the user created and is cur-

rently configuring.

Variant Id Default: 0

Range: 0–127

Format: Numeric

This index identifies the variant channel number in

the V5 interface.

Link Id Default: 0


Specifies the logical link identifier to identify a link.

Phys Id Default: 0

Range: Chassis

dependent

Format: SSPPCCC

Format: Specifies the configured logical C-channel

ID. The ID must be entered as slot number (SS),

port number (PP) and channel number (CCC). The

channel must always be entered as 001.




8-40 255-700-447


Accessing the V5 E1 Interface Configuration Window

Begin

1 From the V5 E1Link Configuration window, select the Go to E1 Inter-

face Configuration command. The V5 E1 Interface Configuration win-

dow displays (see Figure 8-15). Table 8-27 describes the commands and


Administrative Sta-

tus

Default: Force-

Blocked

Range: N/A.

Format: Predefined

Specifies the administrative status of the call pro-

cessing functions on the E1 Link.

ForceBlocked Upon initial configuration, the selected E1 link is at

this setting. To bring the link into service, change

the field value to Unblocked and apply the Apply

Administrative Status command after selecting

all values in configurable fields.

Unblocked There are no restrictions on call processing func-

tions.

NonDeferBlocked Use this setting to immediately block all active and

future calls. This setting immediately terminates

any active calls on the link.

DeferBlocked Use this setting to defer blocking of any active calls.Any current calls will terminate only after caller

has returned to the on-hook status.

LELink ID Default: 0

Range: 0–255

Format: Numeric

Specifies the logical link id on the LE side.

[Operational State] Default: Normal

Range: N/A

Format: Predefined

Specifies the protection status of the link.

Normal The link is operating normally.

LocalFailure A failure has occurred on the PSAX side, either an

LOS or LOF.

RemoteFailure A failure has occurred on the LE side, either an

LOS or LOF.

[Operational Sta-

tus]

Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Specifies the operational status of the link.

OutOfService The link is out of service.

InService The link is in service.

Table 8-26. Field Descriptions for the V5 E1 Link Configuration Window




255-700-447 8-41



2 Make a note of the timeslot data on the table that you want to change.

Remain on the window and continue to the next procedure.

End

Figure 8-15. V5 E1 Interface Configuration Window

Table 8-27. Commands for the V5 E1 Link Configuration Window

Command Function

Go To Timeslot Channel Table Displays the Timeslot Channel Table window.

Go Back to Previous Screen Returns to the previous window.

Table 8-28. Field Descriptions for the V5 E1 Interface Configuration Window


[Phys ID] Default:

Range: N/A

Format: ssppccc

This index identifies the V5 Interface configura-

tion table.

V5 Intf Id

(display only)

Default: 1


This index identifies the variant channel number

in the V5 interface.

Link Id

(display only)

Default: 0

Range:

Format: Numeric

This index identifies the E1 Link Configuration

Table.




8-42 255-700-447


Accessing the V5 Time Slot Table

Begin

1 From the V5 E1 Interface Configuration window, select the Go Timeslot

Channel Table. The V5 Time Slot Table displays (see Figure 8-16).

Table 8-29 describes the commands.

2 Select the timeslots you want to change the status on and press Enter.The action of selecting a timeslot causes the timeslot display to change to

InService if it is OutOfService, and vice versa. You may also select the

appropriate command at the bottom of the table to take all timeslots Out

Of Service or Into Service.

End

[Channel1] Default: 0

Range:

Format: Numeric

Specifies a C-Channel which carries signalling

information. Generally, this channel should be

specified on a single E1 in a V5 interface group

and should be on timeslot 16.[Channel2] Default: 0

Range: B

Format: Numeric


information. Generally, this channel should be


and should be on timeslot 15.

[Channel3] Default:

Range:

Format: Numeric


information. Generally this channel should be


and should be on timeslot 31.

[Operational

Status]

Format: Specifies the E1 interface physical operational

status.

OutOfService The interface is out of service.

InService The interface is in service.

Table 8-28. Field Descriptions for the V5 E1 Interface Configuration Window




255-700-447 8-43



Accessing the V5 Data Link Configuration Table

Begin

1 On the V5 Interface Variant Configuration window, select the Add DL

Table to Variant command. The V5 Data Link Configuration Table dis-

plays (see Figure 8-17). Table 8-30 describes the commands and


2 Remain on this window and continue with next procedure.

End

Figure 8-16. V5 Time Slot Table

Table 8-29. Commands for the V5 Timeslot Table Window

Command Function

Bring All Interfaces Into Service Brings all interfaces into service.

Take All Interface Out Of Service Takes all interfaces out of service.

Go Back to Previous Screen Returns to the V5 E1 Interface Configuration Window.




8-44 255-700-447


Figure 8-17. V5 Data Link Configuration Table

Table 8-30. Commands for the V5 Data Link Configuration Table Window

Command Function





Find... Intf ID: ... Variant ID: Finds the interface ID and the variant ID

of a particular connection.

Add Data Link Config Entry Add a data link configuration entry.

Go Back to Previous screen Returns to the V5 Interface Variant Con-

figuration Window.

Table 8-31. Field Descriptions for the V5 Data Link Configuration Table Window:

Command Function


Variant ID Displays the Variant ID associated with the Interface ID.DL C Path ID Displays the Data Link Communication Path ID.

Total 0/0 The first number in this field indicates the number of

the V5 Interface ID on the first line of the currently dis-

played window. The second number indicates the total

number of V5 Interface IDs table entries on the table.



255-700-447 8-45



Accessing the V5 Data Link Configuration Window

Begin

1 From the V5 Data Link Configuration Table, select the Add Data Link

Config Entry command. The V5 Data Link Configuration window dis-plays (see Figure 8-18). Table 8-32 describes the commands and


2 Enter the values you need.

3 Select the Add V5 Data Link to the table command.

Note: Repeat this step 6 times until the PSTN Data Link is obtained.

4 Return to the V5 inft Variant Cfg window and perform the Bring Into

Service command.


End

.

Figure 8-18. V5 Data Link Configuration Window

Table 8-32. Commands for the V5 Data Link Configuration Window

Command Function

Display Next V5 Data Link in the table Displays the next V5 data link in the table.

Add V5 Data Link to the table Adds V5 Data Link to the V5 Data Link configu-

ration table.

Update V5 Data Link in the table Updates the V5 data link in the table after field

values are altered.




8-46 255-700-447


Delete V5 Data Link and return Deletes a selected data link and returns to the V5

Data Link Table.

Go Back to Previous Screen Return to the V5 Data Link Table.

Table 8-32. Commands for the V5 Data Link Configuration Window (Continued)

Command Function

Table 8-33. Field Descriptions for the V5 Data Link Configuration Window


Configuration Left Panel

Interface ID Default: 0

Range: 1–10

Format: Numeric

Specifies the ID the PSAX uses internally for the inter-

face after the interface is created.

Variant ID Default: 0

Range: 0–127

Format: Numeric

Specifies the associated ID or the Interface ID.

Comm Path Id Default: V5DLCPath

Protection1

Range: N/A

Format: Predefined

The types described below refer to Data Link Control

protocol.

V5DLCPathProtect

ion1

This path carries messages for synchronizing switching

between primary and secondary links. protection level

1 on the digital loop carrier system.

V5DLCPathProtect

ion2

This path carries messages for synchronizing switching

between primary and secondary links at protection

level 2 on the digital loop carrier system.

V5DLCPathControl V5DLCPathControl. This path carries messages to

unblock links and initiate link identification on the dig-ital loop carrier system.

V5DLCPathLinkCo

ntrol

on the digital loop carrier system.

V5DLCPathBcc The link control path for the bearer channel connec-

tion. This path carries messages to allocate and deallo-

cate timeslots on the digital loop carrier system.

V5DLCPathPstn This path carries messages for call processing of PSTN

(analog) circuits such as ESTABLISH, ESTABLISH ACK,

DISCONNECT, DISCONNECT COMPLETE, and SIG-

NAL.

Logical C ChanId

Default: 0Range: 0–65503

Format: Numeric

This value must match the entry on the Physical C-Channel table.



255-700-447 8-47


Chapter 8 Configuring V5.2 European IDLCUser Side Configuration Summary

User Side Configuration Summary

The next part of V5.2 configuration is to configure the User Side. The follow-

ing steps are a summary; actual configuration begins with the Accessing the

User Port Table procedure below.

1. Configure your modules for ATM Trunking on the Site Specific Menu.Configure the Max Remote IWF field on the ATM Trunking Local Node

Configuration window for 4096 connections.

2. Apply Configuration and Bring Admin Status Up.

3. On the ATM Trunking Local Node Configuration window, select the Go

to Remote IWF Table command and Add Remote IWF Entry. On the

ATM Trunking Remote IWF Configuration window, enter values for the

Remote IWF ID and the Remote IWF ATM Address. In the Remote IWF

Trnk Modefield, select Non-switched.

4. Select the Add the Configuration and Bring Admin Status Up commands.

5. On the ATM Trunking Remote IWF Configuration, add and bring into

svc

6. Configure the remote node, All a Node, Enter values for first two fields,

select nonswitched

7. Add and Bring the Admin Status Up

8. Go to the Bearer VCC Table

• Perform the Control Add command, and fill in these fields:

• vcc ID,

• svc type vbr,

• SAR aal2,

• vcc com type pvc,

• vcc/vpi/vci info,

• app type, select V5,

• DSP IWF select None,

• DSP, select type Auto,

9. Perform the Add Configuration command.

Begin

Configuring the Remote and Local Nodesfor ATM Trunking

1 Go to the your PSAX chassis user guide and configure the remote and

local nodes for ATM trunking according to the procedures. You will be

implementing the User Side Configuration Step Summary above.

2 After completing the remote and local node configuration for ATM

trunking, continue with the procedure below.

End




8-48 255-700-447


Accessing the V5 User Port Table

Begin

See the “Accessing the V5 Interface Configuration Window” on

page 8-22 to start this procedure.

1 From the V5 Interface Variant Configuration window, select the Add

User Port Table to Variant command. The User Port Configuration

window displays (see Figure 8-19). Table 8-34 describes the commands.

2 Remain on the window and continue with the next procedure.

End

Figure 8-19. V5 User Port Table

Table 8-34. Commands for the V5 User Port Table Window

Command Function



Top Scrolls to the top of the current page.Bottom Scrolls to the bottom of the current page.

Find... Intf ID: ... Variant ID: Finds the interface ID and the variant ID

of a particular connection.



255-700-447 8-49



Accessing the V5 User Port Configuration Window, PSTN Port Type

Begin

Note: If you are configuring Port type PSTN on the V5 User Port Configu-

ration window, the fields that display for configuration are differ-

ent from those that display for ISDN. Complete this procedure if

you are using a Port Type PSTN. If you are configuring Port Type

ISDN, complete the “Accessing the V5 User Port Configuration

Window, ISDN Port Type” on page 8-55 procedure following the

PSTN port type procedure.

1 From the V5 User Port Table, select the Add User Port Configuration

Entry command. The V5 User Port Configuration Window displays (see



2 At a minimum, enter values for the fields listed below.

• LE Port ID

• Port Type

• Vcc Id

• Rem IWF Id

• LES Interface Port ID

• Encode Standard

• Encoding profile Num

• VC algorithm

• Tone Detection Algo

• Translate Type

3 If you want to add ports, change the Admin Status field to Unblocked

and select the Add V5 User Port Configuration command.

End

Add User Port configuration

Entry

Adds the User Port configuration values of

a specific entry.

Go back to Previous Screen Returns to the V5 Interface Variant Con-

figuration window.

Table 8-34. Commands for the V5 User Port Table Window (Continued)

Command Function




8-50 255-700-447


Figure 8-20. V5 User Port Configuration Window for PSTN as Port Type

Table 8-35. Commands for the V5 User Port Configuration Window

Command Function

Display Next V5 User Port Configu-

ration

Displays the next V5 User Port configuration in the

database.

Add V5 User Port Configuration Adds the V5 User Port configuration for the

selected Interface ID.

Delete V5 User Port Configuration Deletes the V5 User Port configuration for the


Update V5 User Port Configuration Updates the V5 User Port configuration for the


Apply V5 Admin Status Applies the V5 administrative status for the selected

Interface ID.

Go back to Previous Screen Returns to the V5 User Port Table.



255-700-447 8-51



Table 8-36. Field Descriptions for the V5 User Port Configuration Window


Interface Id Default: 0

Range: 1–10

Format: Numeric

Specifies the ID the PSAX uses internally for the

interface after the interface is created.

Note: Although the status line on your window

indicates configurable values of 1–127, only 1–10interface IDs are supported in Release 8.0.0.

Variant Id Default: 0

Range: 1–200

Format: Numeric

Specifies the Variant Id which is active for this V5

Interface. Only one variant is the active variant

ID. Variants permit an interface group to have

multiple configurations to connect to the voice

switch. Changing variants only affects the net-

work portion from the Gateway to the voice

switch. The network portion from the gateway to

the subscriber is not affected.

LE Port ID Default: 0

Range: 0–32767

Format: Numeric

LE port number used to idenify the ISDN and

PSTN ports on a V5 interface. This value maps

directly to a specific call connection.

Port Type Default: Pstn

Range: N/A

Format: Predefined

Specifies whether port is ISDN or PSTN in a V.5

interface.

Pstn Select this value if you are using PSTN ports. The

sample configuration uses this value.

Isdn Select this value if you are using ISDN ports.

When you select this value, eight additional fields

appear for configuration. They are labeled “ISDN”

on the left panel and the P-, F-, and D-Logical

Chan ID fields on the upper right panel.

AAL2 Trunking Vcc

Id

Default: 1

Range: 1–1024

Format: Numeric

Specifies the AAL2 trunk between the CP-IWF

and the CO-IWF which carries the CIDs.

Remote IWF ID Default:

Range: 1–255

Format: Numeric

Specifies the remote IWF connecting to the near-

end IWF.

LES Interface Port

ID

Default: 1

Range: 1–255

Format: Numeric

Specifies the port number of the IAD used on the

connection.

PSTN Port CID Default: 16


Specifies the PSTN port Cid value. This value

must be the same as the CellPipe IAD port number. This field displays only when Port Type is

Pstn.

Note: The following ISDN fields are display only when the Port Type field is set to Isdn.

ISDN D channels

CID

Default: [128]

Range: 16–233

Format: Numeric

Specifies the Cid value of ISDN D channels that

the PSAX is dynamically allocating. Although the

field is editable, do not enter any values.




8-52 255-700-447


ISDN B1 channels

CID

Default: [160]

Range: 16–233

Format: Numeric

Specifies the Cid value of ISDN Bearer-1 channels

that the PSAX is dynamically allocating.

Although the field is editable, do not enter any

values.ISDN B2 channels

CID

Default: [161]

Range: 16–233

Format: Numeric

Specifies the Cid value of ISDN Bearer-2 channels

that the PSAX is dynamically allocating.

Although the field is editable, do not enter any

values.

Encode Standard Default: Itut

Range: N/A

Format: Predefined

Specifies the encoding standard used.

Itut ITU-T standards are used for voice encoding. Use

this value for voice and voiceband data defined

by ITUT specifications.

Af ATM Forum standards are used for use by voiceand voiceband data. Use this value for PSTN con-

nections.

Custom Custom encoding algorithms are not defined by

standards.

EncodingProfile-

Num

Default: 1

Range: 1–255

Format: Numeric

Specifies the user-assigned profile number for use

by voice and voiceband data. Profile 3 and

Profile 7 are ITU-T predefined profiles which

specify the voice compression and silence

removal algorithms. If the custom profile is cho-

sen, all DSP specific parameters have to be speci-

fied by the user. If the default profile is chosen, all

parameters on the AAL2 trunk, containing thisCID, will be used. Enter the profile as a numeric

value.

Note: For PSTN connections, use 9,10, or 11.

Enter 9 or 10 if using an CellPipe IAD in the con-

figuration.

Admin Status Default: Blocked

Range: As noted

below.

Format: Predefined

Specifies the administrative status of the user

port.

Blocked The port is not open; no traffic can pass. If the

Port Type is Pstn, the status is either Blocked or

UnBlocked.

UnBlocked The port is open; traffic can pass. If the Port Type

is Pstn, the status is either Blocked or

UnBlocked.

Shutdown The port is was open but has been administra-

tively closed; no traffic can pass.





255-700-447 8-53



[ISDN Port Type] Default: Bra

Range: N/A

Format: Predefined

Specifies whether rate interface supported is Bra

or Pra. This field displays only when Port Type is

Isdn.

Bra Basic rate supports 2 bearer channels and 1 data

channel.

Pra Primary rate supports 30 bearer channels and 1

data channel.

[Line Type] Default: NotPerm-

Line

Range: N/A

Format: Predefined

Specifies the type of line - permanent or leased

line. This display only field appears only when

Port type is Isdn.

NotPermLine Non-permanent line.

Leased Leased line.

P-Logical Chan ID Default: 0Range: 0–65503

Format: Numeric

ISDN Data Type P-Logical channel identifierwhich must be unique for an interface.

Note: This configurable field displays only when

Port Type selected is Isdn.

Note: The value entered here must also be con-

figured in the ConfigLogicalCChan Id field on the

V5 PhysCChannel Configuration Window. The

same value can be entered in the P-Logical Chan

ID and in the 2 fields below on this table.

F-Logical Chan ID Default: 0

Range: 0–65503

Format: Numeric

ISDN Data Type F-Logical channel identifier

which must be unique for an interface


Port Type selected is Isdn.Note: The value entered here must be also con-

figured in the ConfigLogicalCChan Id field on the



ID, the F-Logical Chan ID field, and the D-Logical

Chan ID fields on the V5 User Port Configuration

window.

D-Logical Chan ID Default: 0

Range: 0–65503

Format: Numeric

ISDN Data Type D-Logical channel identifier

which must be unique for an interface


Port Type selected is Isdn.

Note: The value entered here must be also con-figured in the ConfigLogicalCChan Id field on the



ID, the F-Logical Chan ID field, and the D-Logical

Chan ID fields on the V5 User Port Configuration

window.






8-54 255-700-447


[Operation Status] Default: Blocked

Range: See Admin

Status field

Format: Predefined

Specifies the operational status of the user port

on both LE and LES sides. See Admin Status field

on lower left panel.

[LE OperationSta-

tus]

Default: Blocked

Range: See Admin

Status field

Format: Predefined

Specifies the operational status of the user port

on LE side.

LES OperationSta-

tus

(display only)

Default: Blocked

Range: See Admin

Status field

Format: Predefined

Operational status of the user port on LES side.

Note: The DSP parameters you select below must be compatible with the selected Encoding

Profile Num field. For more information, see the Reference Information Appendix in the

DSP2x Voice Server Modules User Guide. The CellPipe IAD supports ATM Forum Profiles 9 and 10.

Voice Compression

Algo

Default: None

Range: N/A

Format: Predefined

Specifies the user-assigned voice compression

algorithm used.

None No compression is used on the connection.

G726-16K Voice compression ITU-T G.726 standard at

16-Kbps.


24-Kbps.


32-Kbps.


40-Kbps.

G729a-8K Voice compression ITU-T G.729a standard at

8-Kbps.

Silence Detection Default: Disabled

Range: N/A

Format: Predefined

Indicates whether support for silence detection is

disabled or enabled.

Enabled Support for silence detection is enabled.

Disabled Support for silence detection is disabled.

Echo Cancellation

Algo

Default: None

Range: N/A

Format: Predefined

Specifies which echo cancellation algorithm. is

used.

None No echo cancellation is used.

G165-nearEnd ITU-T G.165-nearEnd near end echo cancella-

tion.

G168 ITU-T G.168 echo cancellation.





255-700-447 8-55



Accessing the V5 User Port Configuration Window, ISDN Port Type

Begin

Note: If you are configuring IDSN as the Port Type on the V5 User Port

Configuration window, several new fields display for configura-

tion. Complete this procedure if you are using a ISDN Port Type.

1 On the V5 User Port Configuration window (see Figure 8-21, select Isdn

in the Port Type field. For descriptions of the other ISDN fields, see

Table 8-34.

End

Tone Detection

Algo

Default: Disabled

Range: N/A

Format: Predefined

Specifies whether fax/modem tone detection is

disabled or bypassed.

Disabled Fax modem tone detection is disabled.

Bypass Fax modem tone detection is bypassed Indicates

that the fax tones are to be recognized and data

sent by fax is not to be processed by compression

and echo cancellation algorithms.

Note: For PSTN connections, use this value.

Translation Type Default: None

Range: N/A

Format: Predefined

Specifies which companding standard is used. A

law is European; Mu law is Japanese and North

American.

None Not companding standard is used.

MuLaw2muLaw Companding standard is Mu law to Mu law.ALaw2aLaw Companding standard is A law to A law.

V5.2 Applications: You must use this value for

V5.2 applications.

Note: Use this setting for PSTN and ISDN Port

Types.

MuLaw2aLaw Companding standard is Mu law to A law.

ALaw2MuLaw Companding standard is A law to Mu law.






8-56 255-700-447


Figure 8-21. V5 User Port Configuration Window, Port Type ISDN Selected




255-700-447 9-1

9 Configuring SNMP AuthenticationOptions


This chapter provides an overveiw of SNMP and instructions for using the

console interface to perform the following tasks:

• Accessing SNMP Configuration Options

• Modifying an SNMP Community String Password

• Configuring the User-based Security Model (USM)

• Configuring the View-based Access Control Model (VACM)

• Configuring SNMP Trap Notification

SNMP Overview

The PSAX system uses the SNMP Version 3 protocol to provide authentica-

tion, privacy, and access control groups.

• Authentication is a process that verifies the received message was actually

transmitted by the user whose identifier appears as the source in the mes-

sage header. To perform authentication, a pair of SNMP engines must share

an authentication key.

• Privacy allows the encryption of messages using the data encryption stan-

dard (DES) algorithm. Privacy can only be used in conjunction with

authentication.

• Access control allows the restriction of access rights to only a subset of themanagement information. An access group defines the access rights

afforded to all of the members of that group. The security level associated

with a group identifies the level of security that is assumed when checking

for access rights.

You must be logged in as username “root” and connected to the PSAX system

via the CONSOLE port on the CPUn module in order to access and modify the

following menu options on the SNMP Agent System-Wide Configuration

window:

• USM User Configuration

• VACM Security to Group Configuration

• VACM Access Configuration

• Community String Configuration

To configure SNMP v1/v2C authentication:

• Define SNMPv1/v2C community strings using the Community String Con-

figuration menu option

• Define the remote management system using the Notification Configura-

tion menu option



Chapter 9 Configuring SNMP Authentication OptionsAccessing SNMP Configuration Options

9-2 255-700-447


SNMPv1/v2C community strings are automatically entered in the Vacm

Security to Group Table window.

To configure SNMPv3 authentication:

• Assign a user a security model using the Usm User Creation menu option

• Define access groups using the Vacm Access Configuration menu option

• Assign users to an access group using the Vacm Security to Group Configu-

ration menu option

• Define the remote management system using the Notification Configura-

tion menu option

SNMP authentication options must be configured at each PSAX system.

Up to five network management systems (NMSs) may be configured. If a

notify type of V3Trap or V3Inform is chosen, then the NMS must have a

USM user defined that matches the USM user on the PSAX system. Each

NMS can access the PSAX system using only one USM user name.

Accessing SNMP Configuration OptionsTo access SNMP configuration options, perform the steps in the following

procedure.

Begin

1 At the Console Interface Main Menu window, select Site-Specific Config-

uration.


2 On the Site-Specific Menu window, select the SNMP Agent option (see

Figure 9-1).

The SNMP Agent System-Wide Configuration window is displayed. If

you are logged in as “readwrite” or “readonly” the screen appears as

shown in Figure 9-2. If you are logged in as “root” the screen appears as

shown in Figure 9-3. The commands for this window are described in

Table 9-1.


End



255-700-447 9-3


Chapter 9 Configuring SNMP Authentication OptionsAccessing SNMP Configuration Options

Figure 9-1. Site-Specific Menu Window, SNMP Agent Selected

Figure 9-2. SNMP Agent System-Wide Configuration Window, Non-Root UserView



Chapter 9 Configuring SNMP Authentication OptionsModifying an SNMP Community String Password

9-4 255-700-447


Modifying an SNMP Community String Password

The PSAX system has predefined two SNMPv1/v2C community strings. Tomodify the password associated with a community string, perform the steps

in the following procedure.

Begin

1 On the SNMP Agent System-Wide Configuration window, select the

Community String Configuration option.

Figure 9-3. SNMP Agent System-Wide Configuration Window, Root User View

Table 9-1. Menu Options for the SNMP Agent System-Wide Configuration Window


Trap Notification Configuration Displays the Notification Table window.

USM User Configuration Displays the Usm User Table window.

Note: This option displays only when logged in as root.

VACM Security to Group Con-

figuration

Displays the Vacm Security to Group Table window.


VACM Access Configuration Displays the Vacm Access Table window.


Community String Configura-

tion

Displays the Community String Table window.


Go Back to Site-specific Menu Redisplays the Site-Specific Menu window.



255-700-447 9-5



The Community String Table window is displayed (see Figure 9-4). The

commands for this window are described in Table 9-2. The fields for this

window are described in Table 9-3.

2 On the Community String Table window, select the entry to modify and

press Enter.

The Community String Configuration window is displayed (seeFigure 9-5). The commands for this window are described in Table 9-4.

The fields for this window are described in Table 9-5. Valid ASCII charac-

ters to use for passwords are described in Table 5-8.

3 On the Community String Configuration window, enter the values in the

fields according to the information provided in Table 9-5.

4 Select the Apply command to apply the changes.

5 Select the Go Back to Previous Screen command.

The Community String Table window is displayed.

End

Figure 9-4. Community String Table Window

Table 9-2. Commands for the Community String Table Window

Command Function

Page Up Displays the previous page of the table.

Page Down Displays the next page of the table.

Top Displays the first page of the table.

Bottom Displays the last page of the table.

Go Back to Previous Screen Redisplays the SNMP Agent System-Wide





9-6 255-700-447


Table 9-3. Field Descriptions for the Community String Table Window


ReadOnlyCommu-

nityString

Default: public

Range: 1–32 charac-

ters

Format: ASCII char-

acters 33–126

The ReadOnlyCommunityString provides read-

only access to the PSAX system using

SNMPv1/v2C.

The field value is used as an authentication pass-word to process SNMPv1/v2C requests.

ReadWriteCommu-

nityString

Default: private


ters

Format: ASCII char-

acters 33–126

The ReadWriteCommunityString provides read-

write access to the PSAX system using

SNMPv1/v2C.

The field value is used as an authentication pass-

word to process SNMPv1/v2C requests.

Figure 9-5. Community String Configuration Window

Table 9-4. Commands for the Community String Configuration Window

Command Function

Apply Applies the change to the community

string value.

Go Back to Previous Screen Redisplays the Community String Tablewindow.



255-700-447 9-7


Chapter 9 Configuring SNMP Authentication OptionsConfiguring the User-based Security Model (USM)

Configuring the User-based Security Model (USM)The PSAX system has predefined the default USM users, as shown in

Table 9-6.

Configuring USM Users

To configure a USM user, perform the steps in the following procedure.

Table 9-5. Field Descriptions for the Community String Configuration Window


ReadOnlyCommu-

nityString

Default: public


ters

Format: ASCII char-

acters 33–126

The ReadOnlyCommunityString provides read-

only access to the PSAX system using

SNMPv1/v2C.

The field value is used as an authentication pass-word to process SNMPv1/v2C requests. You can

choose a new password up to 32 characters long.

The text string is case-sensitive. The use of the

space character is not supported.

Note: Changing this value also changes the value

displayed in the Vacm Security to Group Table

under the User column for Models V1 and V2C

for group “anyoneRead”.

ReadWriteCommu-

nityString

Default: private


ters

Format: ASCII char-acters 33–126

The ReadWriteCommunityString provides read-

write access to the PSAX system using

SNMPv1/v2C.

The field value is used as an authentication pass-word to process SNMPv1/v2C requests. You can

choose a new password up to 32 characters long.



Note: Changing this value also changes the value

displayed in the Vacm Security to Group Table

under the User column for Models V1 and V2C

for group “anyone”.

Table 9-6. Default USM User Information

USM User Name Security LevelAuthentication

PasswordPrivacy Password

v3AqvUser AuthPriv lucenttech2 lucenttech2

v3readonly AuthPriv lucenttech2 lucenttech2

v3traponly NoAuthNoPriv N/A N/A

v3readwrite AuthPriv lucenttech1 lucenttech1

v3superuser AuthPriv lucenttech1 lucenttech1




9-8 255-700-447


Note: Once a USM user has been defined, only the authentication and

privacy passwords may be changed. To change other parameters,

delete the USM user and recreate it using the new parameters.

Begin


USM User Configuration option.

The Usm User Table window is displayed (see Figure 9-6). The com-

mands for this window are described in Table 9-7. The fields for this win-

dow are described in Table 9-8.

2 On the Usm User Table window, select the Add New User command.

The Usm User Creation window is displayed (see Figure 9-7). The com-

mands for this window are described in Table 9-9. The fields for this win-

dow are described in Table 9-10. Valid ASCII characters to use for pass-

words are described in Table 5-8.

3 On the Usm User Creation window, enter the values in the fields accord-ing to the information provided in Table 9-10.

4 Select the Create User command.


The Usm User Table window is displayed, showing the new USM user.

End

Figure 9-6. Usm User Table Window



255-700-447 9-9



Table 9-7. Commands for the Usm User Table

Command Function





Restore Default Usm User Resets the default USM users to the

default configuration.

Add New User Displays the Usm User Creation window.



Table 9-8. Field Descriptions for the Usm User Table Window


UsmUserName Default: N/A

Range: 1–32

Format: Alphanu-

meric

Displays the name assigned to this particular

USM user.

SnmpEngineID Default: N/A

Range: N/A

Format: Hexadecimal

Displays the SNMP engine's administratively-

unique identifier. This value can be the agent's

own snmpEngineID value or it can take the value

of the snmpEngineID of a remote SNMP engine

with which this user can communicate.

Figure 9-7. Usm User Creation Window




9-10 255-700-447


Table 9-9. Commands for the Usm User Creation Window

Command Function

Create User Creates the USM user.

Go Back to Previous Screen Redisplays the Usm User Table window.

Table 9-10. Field Descriptions for the Usm User Creation Window


UserName Default: N/A

Range: 1–32

Format: Alphanu-

meric

Specifies the name assigned to this particular

USM user. You can specify alphanumeric charac-

ters including A-Z, a-z, 0-9, / (forward slash), -

(hyphen), and _ (underscore). The text string is

case-sensitive. The use of the space character is

not supported.

SnmpEngineID Default: local SNMP

Engine ID

Range: 12 bytesFormat: Hexadecimal

Specifies the SNMP engine's administratively-

unique identifier. In a simple agent, this value is

always that agent's own snmpEngineID value.The value can also take the value of the

snmpEngineID of a remote SNMP engine with

which this user can communicate.

When the PSAX device is configured to send

SNMPv3 informs to a remote SNMP manager

(including the AQueView EMS), the USM user

entry must use the remote SNMP engine ID.

To determine the engine ID of the AQueView

EMS, the algorithm is as follows:

• The first 8 bytes of the engine ID are the hexa-

decimal equivalents of the letters that spell

“AQueView,” which are 41,51,75,65,56,69,65,and 77, respectively.

• The remaining 4 bytes of the engine ID are the

hexadecimal equivalent of the IP address

where the AQueView server or AQueView Stan-

dalone system is running.

For example, an AQueView server or AQueView

Standalone system running on a machine having

the IP address 180.48.207.161 has an AQueView

engine ID of 4151756556696577B430CFA1.



255-700-447 9-11



Changing a USM User’s Passwords

To change a password associated with a USM user, perform the steps in the

following procedure.

Security Level Default: NoAuthNo-

Priv

Range: N/A

Format: Predefined

Indicates the level of security for remote SNMP

messages or remote SNMP operations. Authenti-

cation verifies the identity of the sender of a mes-

sage by using secret key algorithms. Privacy pro-vides encryption of the messages being sent.

NoAuthNoPriv Indicates a security level without authentication

and without privacy.

AuthNoPriv Indicates a security level with authentication and

without privacy.

AuthPriv Indicates a security level with authentication and

with privacy.

Auth Protocol Default: usmHMAC

MD5AuthProtocol

Range: N/A

Format: Predefined

Indicates the type of authentication protocol used

to verify the sender of the message.

Note: This field appears when the security level is

set to AuthPriv or AuthNoPrivusmHMACMD5Aut

hProtocol

Indicates that the authentication protocol is Mes-

sage-Digest 5 (MD5).

usmHMACSHAAu-

thProtocol

Indicates that the authentication protocol is

Secure Hash Algorithm (SHA).

Priv Protocol Default: usmDE-

SPrivProtocol

Range: N/A

Format: Predefined

Indicates the type of privacy protocol used to

encrypt messages.


set to AuthPriv

usmDESPrivProto-

col

Indicates that the privacy protocol is data encryp-

tion standard (DES).

User Auth Pass-word

Default: N/A


ters

Format: ASCII char-

acters 33–126

Specifies the authentication password. The textstring is case-sensitive. The use of the space char-

acter is not supported. See the reference appen-

dix for a list of permitted ASCII characters.


set to AuthPriv or AuthNoPriv

User Priv Password Default: N/A


ters

Format: ASCII char-

acters 33–126

Specifies the privacy password. The text string is

case-sensitive. The use of the space character is

not supported.


set to AuthPriv

Table 9-10. Field Descriptions for the Usm User Creation Window (Continued)





9-12 255-700-447


Note: Once a USM user has been defined, only the authentication and

privacy passwords may be changed. To change other parameters,

delete the USM user and recreate it using the new parameters.

Begin



The Usm User Table window is displayed.

2 On the Usm User Table window, select the USM user name whose pass-

word you wish to change.

The Usm User Key Change Configuration window is displayed for the

selected user (see Figure 9-8). The commands for this window are

described in Table 9-11. The fields for this window are described in

Table 9-12. Valid ASCII characters to use for passwords are described in

Table 5-8.

3 Review the record and make sure it’s the one you want to change.

4 On the Usm User Key Change Configuration window, enter the values in

the fields according to the information provided in Table 9-12.

5 Select the Apply Key Change command.



End

Figure 9-8. Usm User Key Change Configuration Window



255-700-447 9-13



Table 9-11. Commands for the Usm User Key Change Configuration Window

Command Function

Apply Key Change Applies the password change for the speci-

fied key type.

Delete this User and Return Deletes the displayed user and redisplaysthe Usm User Table window.

Go Back to Previous Screen Redisplays the Usm User Table window.

Table 9-12. Field Descriptions for the Usm User Key Change Configuration Window


[UserName] Default: N/A

Range:

Format: Alphanu-

meric

Displays the name assigned to the USM user.

[SnmpEngineID] Default: N/A

Range: N/A

Format: Hexadecimal

Displays the SNMP engine’s administratively-

unique identifier

[Auth Protocol] Default: N/A

Range: N/A

Format: Predefined

Displays the type of authentication protocol used.

usmNoAuthProto-

col

Indicates that no authentication protocol is used.

usmHMACMD5Aut

hProtocol

Indicates that the authentication protocol is Mes-

sage-Digest 5 (MD5).

usmHMACSHAAu-

thProtocol

Indicates that the authentication protocol is

Secure Hash Algorithm (SHA).[Priv Protocol] Default: N/A

Range: N/A

Format: Predefined

Displays the type of privacy protocol.

usmNoPrivProtocol Indicates that no privacy protocol is used.

usmDESPrivProto-

col

Indicates that the privacy protocol is data encryp-

tion standard (DES).




9-14 255-700-447


Deleting USM Users

To delete a USM user, perform the steps in the following procedure.

Begin




2 On the Usm User Table window, select the USM user name for the user

to be deleted.

The Usm User Key Change Configuration window is displayed.

3 Review the record and make sure it’s the one you want to delete.

4 Select the Delete this User and Return command.

The USM user is deleted and the Usm User Table window is redisplayed.

End

Key Type Default: Authenti-

cation

Range: N/A

Format: Predefined

Indicates the key type password to be changed.

Authentication Indicates that the authentication password is to

be changed.

Privacy Indicates that the privacy password is to be

changed.

Original Password Default: N/A


ters

Format: ASCII char-

acters 33–126

Specifies the original password. See the reference

appendix for a list of permitted ASCII characters.

New Password Default: N/A


ters

Format: ASCII char-

acters 33–126

Specifies the new password. The text string is

case-sensitive. The use of the space character isnot supported.

Table 9-12. Field Descriptions for the Usm User Key Change Configuration Window (Continued)




255-700-447 9-15


Chapter 9 Configuring SNMP Authentication OptionsConfiguring the View-based Access Control Model (VACM)

Configuring the View-based Access Control Model (VACM)

The PSAX system has predefined the default VACM access groups shown in

Table 9-13.

Configuring VACM Access Groups

To create a VACM access group, perform the steps in the following procedure.

Begin


VACM Access Configuration option.

The Vacm Access Table window is displayed (see Figure 9-9). The com-

mands for this window are described in Table 9-14. The fields for thiswindow are described in Table 9-15.

2 On the Vacm Access Table window, select the Add an Entry command.

The Vacm Access Configuration window is displayed (see Figure 9-10).

The commands for this window are described in Table 9-16. The fields for


3 On the Vacm Access Configuration window, enter the values in the fields

according to the information provided in Table 9-17.

4 Select the Apply/Add command.


The Vacm Access Table window is displayed.End

Table 9-13. Default VACM Access Groups

VACM Group NameSecurityModel

Security Level Read View Write View Notify View

anyone V1 noAuthNoPriv PSAXView PSAXView All

anyone V2C noAuthNoPriv PSAXView PSAXView All

anyoneRead V1 noAuthNoPriv PSAXView None All

anyoneRead V2C noAuthNoPriv PSAXView None All

readonlyGrp USM authPriv PSAXView None All

readwriteGrp USM authPriv PSAXView PSAXView All

superuserGrp USM authPriv SuperuserView PSAXView All

v3traponlyGrp USM noAuthNoPriv None None All




9-16 255-700-447


Figure 9-9. Vacm Access Table Window

Table 9-14. Commands for the Vacm Access Table Window

Command Function





Add an Entry Displays the Vacm Access Configuration

window.





255-700-447 9-17



Table 9-15. Field Descriptions for the Vacm Access Table Window


Group Name Default: N/A

Range: 1-32

Format: Alphanu-

meric

Displays the name assigned to the VACM group.

A unique combination of the fields Vacm Group

Name, Vacm Access Security Model, and Vacm

Access Security Level constitute one table entry.Once this entry is created, this combination of

fields cannot be changed, only deleted. If you

attempt to change an entry, a new entry is cre-

ated in addition to the previously existing one.

Model Default: N/A

Range: N/A

Format: Predefined

Displays the security model under which access is

requested.

USM Indicates the access security model to be used is

the User-based security model.

V1 Indicates that the access security model will be

SNMPv1.Note: The only valid Vacm Access Security Level

for V1 is noAuthNoPriv.

V2C Indicates that the access security model will be

SNMPv2c.

Note: The only valid Vacm Access Security Level

for V2c is noAuthNoPriv.

Security Level Default: N/A

Range: N/A

Format: Predefined


messages or remote SNMP operations. Authenti-


sage by using secret key algorithms. Privacy pro-

vides encryption of the messages being sent.

noAuthNoPriv Indicates a security level without authentication


Note: This is the only valid Vacm Access Security

Level for a Vacm Access Security Model of V1 or

V2C.

authNoPriv Indicates a security level with authentication and

without privacy.

authPriv Indicates a security level with authentication and

with privacy.




9-18 255-700-447


Figure 9-10. Vacm Access Configuration Window

Table 9-16. Commands for the Vacm Access Configuration Window

Command Function

Apply/Add Adds an entry to the Vacm Access Table

window when the VACM Group or Secu-

rity information is created or modified.

Applies when a change is made to the

VACM Access View information.

Delete this Entry Deletes the entry and redisplays the Vacm

Access Table window.

Go Back to Previous Screen Redisplays the Vacm Access Table window.



255-700-447 9-19



Table 9-17. Field Descriptions for the Vacm Access Configuration Window


Vacm Group Name Default: N/A

Range: 1-32

Format: Alphanu-

meric

Specifies the name to be assigned to the VACM

group. You can specify alphanumeric characters

including A-Z, a-z, 0-9, / (forward slash), -

(hyphen), and _ (underscore). The text string iscase-sensitive. The use of the space character is

not supported.

A unique combination of the fields Vacm Group

Name, Vacm Access Security Model, and Vacm

Access Security Level constitute one table entry.

Once this entry is created, this combination of

fields cannot be changed, only deleted. If you

attempt to change an entry, a new entry is cre-

ated in addition to the previously existing one.

Vacm Access Secu-

rity Model

Default: USM

Range: N/A

Format: Predefined

Indicates the security model under which access

is requested.

USM Indicates the access security model to be used is

the User-based security model

V1 Indicates that the access security model will be

SNMPv1.


for V1 is noAuthNoPriv.

V2C Indicates that the access security model will be

SNMPv2c.


for V2C is noAuthNoPriv.

Vacm Access Secu-rity Level

Default: noAuthNo-Priv

Range: N/A

Format: Predefined

Indicates the level of security for remote SNMPmessages or remote SNMP operations. Authenti-




noAuthNoPriv Indicates a security level without authentication


Note: This is the only valid Vacm Access Security

Level for a Vacm Access Security Model of V1 or

V2C.

authNoPriv Indicates a security level with authentication and

without privacy.

authPriv Indicates a security level with authentication and

with privacy.




9-20 255-700-447


Vacm Access Read

View

Default: None

Range: N/A

Format: Predefined

Indicates the read privileges for the group. A read

operation occurs when processing a retrieval

operation.

None Indicates that the view group has no read access.

PSAXView Indicates that the view group has read access to

data stored in the PSAX Enterprise MIB and the

ATM Forum MIB. The view group has read

access to the data stored in the Notification Table

window and the Notification Configuration win-

dow (snmpTargetAddrTable, snmpTragetParam-

sTable and snmpNotifyTable).

All Indicates that the view group has read access to

data stored in the PSAX Enterprise MIB, the ATM

Forum MIB, and the SNMPv2 MIB. The view

group has read access to the data stored in the

Notification Table window and the Notification

Configuration window (snmpTargetAddrTable,

snmpTragetParamsTable and snmpNotifyTable).

SuperuserView Indicates that the view group has read access to




window, the Notification Configuration window

(snmpTargetAddrTable, snmpTragetParamsTable

and snmpNotifyTable), and the Usm User Table

(usmUserTable) window.

Vacm Access Write

View

Default: None

Range: N/A

Format: Predefined

Indicates the write privileges for the group.

None Indicates that the view group has no write access.

PSAXView Indicates that the view group has write access to




window and the Notification Configuration win-

dow (snmpTargetAddrTable, snmpTragetParam-

sTable and snmpNotifyTable).

All Indicates that the view group has write access to

data stored in the PSAX Enterprise MIB, the ATMForum MIB, and the SNMPv2 MIB. The view

group has read access to the data stored in the




Table 9-17. Field Descriptions for the Vacm Access Configuration Window (Continued)




255-700-447 9-21



Modifying VACM Access Groups

To modify a VACM access group, perform the steps in the following proce-

dure.

Note: Once a VACM access group has been configured, only the view

options can be changed. Changing the other fields results in a new

VACM access group in addition to the original group. To change

the Security Model or the Security Level for a VACM access group,

delete the group and recreate it with the desired Security Model or

Security Level.

Begin



The Vacm Access Table window is displayed (see Figure 9-9).

Vacm Access Notify

View

Default: None

Range: N/A

Format: Predefined

Indicates the notification privileges for the group.

Notification occurs when the PSAX sends a trap.

None Indicates that the group has no notify access, so it

will not receive any traps.

PSAXView Indicates that the view group will receive traps

generated from the PSAX Enterprise MIB and

the ATM Forum MIB. Traps will be received from

incidents related to the Notification Table win-

dow and the Notification Configuration window


and snmpNotifyTable).

All Indicates that the view group will receive traps

generated from the PSAX Enterprise MIB, the

ATM Forum MIB, and the SNMPv2 MIB. Traps

will be received from incidents related to the




SuperuserView Indicates that the view group will receive traps

generated from the PSAX Enterprise MIB and the

ATM Forum MIB. Traps will be received from

incidents related to the Notification Table win-

dow, the Notification Configuration window


and snmpNotifyTable), and the Usm User Table

(usmUserTable) window.

Table 9-17. Field Descriptions for the Vacm Access Configuration Window (Continued)





9-22 255-700-447


2 On the Vacm Access Table window, select the entry to modify and press

Enter.


3 On the Vacm Access Configuration window, modify the values in the

fields according to the information provided in Table 9-15.



The Vacm Access Table window is displayed.

End

Deleting VACM Access Groups

To delete a VACM access group, perform the steps in the following procedure.

Begin



The Vacm Access Table window is displayed (see Figure 9-9).

2 On the Vacm Access Table window, select the entry to delete and press

Enter.



4 On the Vacm Access Configuration window, select the Delete this

Entry command.


The Vacm Access Table window is displayed.

End

Assigning a User to a VACM Access Group

The PSAX system has preassigned the default USM users to the default

VACM access groups as shown in Table 9-18.

Table 9-18. Default VACM Access Group Assignments

User Name Security Modelfor User

VACM AccessGroup

VACM GroupSecurity Level

VACM ReadView

VACM WriteView

VACMNotify View

public V1 anyoneRead noAuthNoPriv PSAXView None All

private V1 anyone noAuthNoPriv PSAXView PSAXView All

public V2C anyoneRead noAuthNoPriv PSAXView None All

private V2C anyone noAuthNoPriv PSAXView PSAXView All

v3AqvUser USM readonlyGrp AuthPriv PSAXView None All



255-700-447 9-23



The PSAX system does not verify the combination of USM security level and

VACM Group security level in the Vacm Security to Group Configuration

window or the Vacm Security to Group Table window. Valid combinations of

USM security level and VACM Group security level are shown in Table 9-19.

To assign USM users and/or SNMP communities to VACM security groups,

perform the steps in the following procedure.

Begin


VACM Security to Group Configuration option.

The Vacm Security to Group Table window is displayed (see Figure 9-11).



2 On the Vacm Security to Group Table window, select the Add an Entry

command.

The Vacm Security to Group Configuration window is displayed (see

Figure 9-12). The commands for this window are described in

Table 9-22. The fields for this window are described in Table 9-23.

3 On the Vacm Security to Group Configuration window, enter the values

in the fields according to the information provided in Table 9-23.



The Vacm Security to Group Table window is displayed.

End

v3readonly USM readonlyGrp AuthPriv PSAXView None All

v3traponly USM v3traponlyGrp noAuthNoPriv None None All

v3readwrite USM readwriteGrp AuthPriv PSAXView PSAXView All

v3superuser USM superuserGrp AuthPriv Superuser-

View

PSAXView All

Table 9-18. Default VACM Access Group Assignments (Continued)

User NameSecurity Model

for UserVACM Access

GroupVACM GroupSecurity Level

VACM ReadView

VACM WriteView

VACMNotify View

Table 9-19. Valid VACM Group Assignment for USM Security Level

USM Security LevelVACM Group Security Level

noAuthNoPriv AuthNoPriv AuthPriv noAuthNoPriv Yes No No

AuthNoPriv Yes Yes No

AuthPriv Yes Yes Yes




9-24 255-700-447


Figure 9-11. Vacm Security to Group Table Window

Table 9-20. Commands for the Vacm Security to Group Table Window

Command Function





Add an Entry Displays the Vacm Security to Group Config-

uration window.





255-700-447 9-25



Table 9-21. Field Descriptions for the Vacm Security to Group Table Window


Name Default: N/A

Range: 1–32

Format: Alphanu-

meric

Displays the VACM security name.

Note: If the Model is set to V1 or V2C, then this

field value must match one of the Security Name

values on the Community String Table window.If there is no match, then you will not be able to

access the PSAX system from an external SNMP

manager using the SNMPv1/v2c protocol.

Note: If the Model is set to USM, then this field

value must match one of the UsmUserName val-

ues on the Usm User Table window. If there is no

match, then you will not be able to access the

PSAX system from an external SNMP manager

using the SNMPv3 protocol.

Model Default: USM

Range: N/A

Format: Predefined

Displays the security model to use when access-

ing a PSAX from an external SNMP manager.

Note: This is the security model associated withthe Name, not the security model associated with

the VACM group.

V1 Indicates that the security model will be SNMPv1,

which supports only community strings.

V2C Indicates that the security model will be

SNMPv2c, which supports only community

strings.

USM Indicates that the security model will be USM,

which supports authentication and privacy.

Group Default: N/A

Range: 1–32Format: Alphanu-

meric

Displays the name assigned to the VACM group.




9-26 255-700-447


Figure 9-12. Vacm Security to Group Configuration Window

Table 9-22. Commands for the Vacm Security to Group Configuration Window

Command Function

Apply/Add Applies when a change is made to the Vacm

Group Name.

Adds an entry to the Vacm Security to Group

Table window when the Vacm Security

Name is created or modified or when the

Vacm Security Model is modified.

Delete this Entry and

Return

Deletes this entry and redisplays the Vacm

Security to Group Table window.

Go Back to Previous Screen Redisplays the Vacm Security to Group Table

window.



255-700-447 9-27



Table 9-23. Field Descriptions for the Vacm Security to Group Configuration Window


Vacm Security

Name

Default: N/A

Range: 1-32

Format: Alphanu-

meric

Specifies the VACM security name. You can spec-

ify alphanumeric characters including A-Z, a-z, 0-

9, / (forward slash), - (hyphen), and _ (under-

score). The text string is case-sensitive. The use ofthe space character is not supported.

Note: If the Vacm Security Model is set to V1 or

V2C, then this field value must match one of the

Security Name values on the Community String

Table window. If there is no match, then you will

not be able to access the PSAX from an external

SNMP manager using SNMPv1/v2c protocol.

Note: If the Vacm Security Model is set to USM,

then this field value must match one of the

UsmUserName values on the Usm User Table

window. If there is no match, then you will not

be able to access the PSAX from an externalSNMP manager using SNMPv3 protocol.

Vacm Security

Model

Default: USM

Range: N/A

Format: Predefined

Indicates the security model to use when access-

ing a PSAX from an external SNMP manager.

Note: This is the security model associated with

the Vacm Security Name, not the security model

associated with the VACM group.

V1 Indicates that the security model will be V1,


V2C Indicates that the security model will be V2C,


USM Indicates that the security model will be USM,

which supports authentication and privacy.

Vacm Group Name Default: N/A

Range: 1-32

Format: Alphanu-

meric

Specifies the name assigned to the VACM group.

You can specify alphanumeric characters includ-

ing A-Z, a-z, 0-9, / (forward slash), - (hyphen),

and _ (underscore). The text string is case-sensi-

tive. The use of the space character is not sup-

ported.

Note: This field value must match one of the

Group Name values on the Vacm Access Table


be able to access the PSAX from an external

SNMP manager.

Note: A unique combination of Vacm Security

Name and Vacm Security Model can be assigned

to only one Vacm Group Name.




9-28 255-700-447


Re-assigning a User to a Different VACM Access Group

To modify the assignment of USM users and/or SNMP communities to VACM

security groups, perform the steps in the following procedure.

Begin




2 On the Vacm Security to Group Table window, select the entry to modify

and press Enter.

The Vacm Security to Group Configuration window is displayed.

3 Review the record and make sure it’s the one you want to modify.

4 On the Vacm Security to Group Configuration window, modify the val-

ues in the fields according to the information provided in Table 9-23.

Note: If you change the Vacm Security Name or Vacm Security Model,

a new entry will be added to the Vacm Security to Group Table in

addition to the existing entry. If you change the Vacm Group

Name, then the existing entry will be modified.

5 Select the Apply/Add command to apply the changes.



End

Deleting a User from a VACM Access Group

To delete the assignment of USM users and/or SNMP communities to VACM

security groups, perform the steps in the following procedure.

Begin




2 On the Vacm Security to Group Table window, select the entry to delete

and press Enter.

The Vacm Security to Group Configuration window is displayed.


4 Select the Delete this Entry and Return command to delete the infor-

mation.



255-700-447 9-29


Chapter 9 Configuring SNMP Authentication OptionsConfiguring SNMP Notification

The information is deleted and the Vacm Security to Group Table win-

dow is displayed.

End

Configuring SNMP NotificationYou can send SNMP trap or inform messages to remote network manage-

ment systems (NMSs). To define the IP address and notification type for an

NMS destination, perform the steps in the following procedure.

Begin

1 On the SNMP Agent System-Wide Configuration window, select the Trap

Notification Configuration option.

The Notification Table window is displayed (see Figure 9-13). The com-

mands for this window are described in Table 9-24. The fields for this

window are described in Table 9-25.

2 On the Notification Table window, select the NMS name.

The Notification Configuration window is displayed (see Figure 9-14).



3 On the Notification Configuration window, enter the values in the fields

according to the information provided in Table 9-27.

4 Select the Apply command.


The Notification Configuration window is displayed.

6 Repeat Step 2 to Step 5 for each network management station you want

to define (up to a total of five).

End




9-30 255-700-447


Figure 9-13. Notification Table Window

Table 9-24. Commands for the Notification Table Window

Command Function




Bottom Displays the last page of the table.Go Back to Previous Screen Redisplays the SNMP Agent System-Wide


Table 9-25. Field Descriptions for the Notification Table Window


Name Default: N/A

Range: NMS 1 to

NMS 5

Format: Predefined

Identifies the first through fifth network manage-

ment systems to which you want SNMP trap

messages to be sent.

Transport Address Default: 000.000.000.

000

Range: N/A

Format: IP Address

Specifies the IP address of the network manage-

ment system to which you want SNMP trap mes-

sages to be sent.



255-700-447 9-31



Figure 9-14. Notification Configuration Window

Table 9-26. Commands for the Notification Configuration Window

Command Function

Apply Sets the displayed configuration values.

Go Back to Previous Screen Redisplays the Notification Table window.

Table 9-27. Field Descriptions for the Notification Configuration Window


[Notify/TargetAddr

Name]

Default: N/A

Range: NMS1–

NMS5

Format: Predefined

Identifies the network management systems to

which you want SNMP trap messages to be sent.




9-32 255-700-447


Notify Type Default: V1Trap

Range: N/A

Format: Predefined

Indicates the type of notification to be sent. An

inform is an acknowledged notification. A trap is

an un-acknowledged notification.

V1Trap Send SNMP traps in SNMPv1 trap format. This

option does not support authentication or pri-

vacy.

V2Trap Send SNMP traps in SNMPv2 trap format. This

option does not support authentication or pri-

vacy.

V2Inform Send SNMP informs in SNMPv2 inform format.

This option does not support authentication or

privacy.

V3Trap Send SNMP traps with a user-specified USM user

name in SNMPv3 trap format. The user may also

select a security level.V3Inform Send SNMP informs with a user-specified USM

user name in SNMPv3 inform format. The user

may also select a security level.

Note: When the notify type is V3Inform, then

the SnmpEngineID field on the Usm User Cre-

ation window must be set to the remote SNMP

Engine ID.

IP Address Default: 000.000.000.

000

Range: 000–255

Format: IP Address

Specifies the IP address of the network manage-

ment system to which you want SNMP trap or

inform messages to be sent.

Source Interface Default: Interface

Range: N/A

Format: Predefined

Indicates the source type of the sender’s IP

address.

Note: This field only appears when the Notify

Type is set to V1Trap

Interface Use the outgoing interface's local IP address as

the sender's IP address for traps.

Ethernet Use the Ethernet's IP address as the sender's IP

address for traps.

Ibm Use the inband management local IP address as

the sender's IP address for traps.

Timeout Interval Default: 100

Range: 0–214748364

7

Format: Numeric

Indicates the maximum round trip time, in hun-

dredths of seconds, for communicating with the

IP address of the NMS. When a message is sent to

this address, and a response (if one is expected) is

not received within this time period, it is assumed

that the response will not be delivered.


Type is set to V2Inform or V3Inform.

Table 9-27. Field Descriptions for the Notification Configuration Window (Continued)




255-700-447 9-33



Retry Times Default: 3

Range: 0–255

Format: Numeric

Specifies the number of retries to be attempted

when a response is not received for a generated

message. An application may provide its own

retry count, in which case the value of this objectis ignored.


Type is set to V2Inform or V3Inform.

Usm User Name Default: N/A

Range: 1–32

Format: Alphanu-

meric

Specifies the USM user name that the NMS will

use to access the PSAX system. You can specify

alphanumeric characters including A-Z, a-z, 0-9,

/ (forward slash), - (hyphen), and _ (underscore).




Type is set to V3Trap or V3Inform.

Note: This field value must match one of theUsmUserName values on the Usm User Table



SNMP manager using SNMPv3 protocol.

Note: If the Notify Type is set to V3Inform, then

the SnmpEngineID associated with the UsmUser-

Name value on the Usm User Table must be set to

the remote SNMP Engine ID. If it is not, then

delete the existing USM User and recreate the

user using the remote SNMP Engine ID.

Security Level Default: NoAuthNo-

PrivRange: N/A

Format: Predefined


messages or remote SNMP operations. Authenti-cation verifies the identity of the sender of a mes-




Type is set to V3Trap or V3Inform.

Note: This field value must match the Security

Level value configured on the Usm User Creation



SNMP manager using SNMPv3 protocol.

NoAuthNoPriv Indicates a security level without authentication

and without privacy.AuthNoPriv Indicates a security level with authentication and

without privacy.

AuthPriv Indicates a security level with authentication and

with privacy.

Table 9-27. Field Descriptions for the Notification Configuration Window (Continued)





9-34 255-700-447


Configuring V3 Informs

Configuring SNMPv3 informs requires that you know the remote SNMP

Engine ID of the system that will provide the acknowledgement. The follow-

ing procedure only shows the configuration options needed for V3 Informs.

Begin



2 On the Usm User Table window, verify that the desired USM user has the

correct remote SNMP Engine ID displayed. If not, then you must delete

that user. See “Deleting USM Users” on page 14.

3 If the USM user does not exist, create the user.

a At the Usm User Table, select the Add New User command.

b At the Usm User Creation window, set the desired UserName, Secu-

rity Level and enter the remote SnmpEngineID. By default, the localSNMP engine ID is filled in.

c Select the Create User command.

d Select the Go Back to Previous Screen command.

4 On the Usm User Table window, select the Go Back to Previous Screen

command.

5 On the SNMP Agent System-Wide Configuration window, select the Trap

Notification Configuration option.

6 On the Notification Table window, select the NMS name.

7 On the Notification Configuration window, select a Notify Type of

V3Inform and enter the Usm User Name configured with the remote

SNMP Engine ID.

8 Select the Apply command.


The Notification Configuration window is displayed.

En




255-700-447 10-1

10 Configuring ATM Security Agents


This chapter provides information for configuring ATM security agents for

the PSAX system including the following subjects:

• “Prerequisites for Configuring ATM Security Agents”

• “Availability of the ATM Security Feature”

• “Configuring ATM Security for ATM UNI Interfaces”

• “Configuring ATM Security for ATM PNNI SVCC RCC Nodes”

• “Configuring ATM Security for ATM PNNI Interfaces”

• “Viewing All ATM Security Agents in the System”

Availability of the ATM Security Feature

The ATM Security feature is available only to users in certain countries. Con-

tact your Lucent Technologies sales representative to find out whether your

country is eligible to use the ATM Security feature.

Prerequisites for Configuring ATM Security Agents

Before you can configure ATM Security feature on the ATM UNI and PNNI

interfaces, you must have already done the following tasks:

1. You must have installed one of the PSAX system software versions with

profile 2, 3, or 4

2. You must have enabled the ATM Security feature on the Feature Turn

ON/OFF Table window (see the section, “Enabling and Disabling PSAX

System Features” on page 5-42)

3. If you want to configure an ATM security agent for an ATM UNI inter-

face, you must have configured an ATM UNI 3.0, 3.1, or 4.0 interface on

a PSAX module port that supports the ATM UNI interface. (For instruc-

tions, see the appropriate PacketStar PSAX I/O module user guide.)

4. If you want to configure an ATM security agent for an ATM PNNI 1.0

interface, you must have configured the following:

a. An ATM PNNI node. (For instructions, see Chapter 6.)

b. The ATM PNNI interface on a PSAX module port that supports the

ATM PNNI interface. (For instructions, see the appropriate PacketStar

PSAX I/O module user guide.)



Chapter 10 Configuring ATM Security AgentsConfiguring ATM Security for ATM UNI Interfaces

10-2 255-700-447


Configuring ATM Security for ATM UNI Interfaces

Accessing ATM Security for an ATM UNI Interface

To access the ATM UNI Interface ATM Security window on which you begin

configuration of an ATM security agent for an ATM UNI interface, performthe steps in the following procedure.

Begin

1 Make sure that you have already done the following tasks. (For more

information, see the appropriate PacketStar PSAX I/O module user guide.)

a Configured the port on a PSAX I/O module that supports the ATM

UNI interface, and applied this configuration.

b Configured the ATM UNI interface for the port and applied this con-

figuration.

Note: Do not bring the ATM UNI interface into service at this point,or, if the interface is already in service, take it out of service.

2 On the ATM UNI Interface Configuration window, select the ATM Secu-

rity command.

The ATM UNI Interface ATM Security window is displayed (see

Figure 10-1). The commands and fields are described in Table 10-1 and

Table 10-2.

3 To configure an ATM security agent for the ATM UNI interface, go the

procedure in the next section, “Configuring an ATM Security Agent for

an ATM UNI Interface”.

End



255-700-447 10-3





Figure 10-1. ATM UNI Interface ATM Security Window

Table 10-1. Commands for the ATM UNI Interface ATM Security Window

Command Function

ATM UNI Security Configura-

tion

Displays the ATM UNI Interface ATM Security Configuration

window.

ATM UNI Security Statistics Displays the ATM UNI Interface ATM Security Statistics win-

dow.

Go Back to Previous Screen Redisplays the ATM UNI Interface Configuration window.




10-4 255-700-447


Configuring an ATM Security Agent for an ATM UNI Interface

To configure an ATM security agent for an ATM UNI interface, perform the

steps in the following procedure.

Begin

1 On the ATM UNI Interface ATM Security window, select the ATM UNI

Security Configuration command.

The ATM UNI Interface ATM Security Configuration window is displayed

(see Figure 10-2).


provided in Table 10-4. Commands on this window are described in

Table 10-3.

Note: If you select the value Integrity-Confidentiality-172 or Integ-

rity-Confidentiality-ReplayReorderProtection-172 in the

Service Profile field, the Confidentiality Security Service panel is

displayed on the window (see Figure 10-3)

Table 10-2. Field Descriptions for the ATM UNI Interface ATM Security Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric

Specifies the slot number containing the module,

which contains the interface for which ATM

security is being configured.

Port Default: N/A

Range: Depends on

module type

Format: Numeric

Specifies the port number of the module for

which the ATM security is being configured.

Channel Default: N/A

Range: Depends on

module type

Format: Numeric

Specifies the channel number for the module

port for which the ATM security is being config-

ured.

[ATM Security] Default: Unsup-

ported

Range: N/A

Format: Predefined

alphanumeric

Displays an indicator whether ATM security is

configured for signaling PVC connections on this

interface.

Unsupported Indicates that ATM security is not configured for

signaling PVC connections.

SupportedOnSig-

nalingPvc

Indicates that ATM security is configured for sig-

naling PVC connections.



255-700-447 10-5



3 To view the statistics for this ATM security agent, go the procedure in the

next section, “Viewing ATM Security Agent Statistics for an ATM UNI

Interface”.

End

Figure 10-2. ATM UNI Interface ATM Security Configuration Window (IntegritySecurity Service Only)

Figure 10-3. ATM UNI Interface ATM Security Configuration Window (BothIntegrity and Confidentiality Security Services)




10-6 255-700-447




Table 10-3. Commands for the ATM UNI Interface ATM Security Configuration Window

Command Function

Bring Sec Admin Status Into

Service

Brings the security configuration on the specified interface

into service, making the encryption operational.Take Sec Admin Status Out of

Service

Takes the security configuration on the specified interface out

of service, making the encryption not operational.

Create ATM Security Configu-

ration

Adds the security configuration to the specified interface.

Delete ATM Security Configu-

ration

Deletes the security configuration from the specified inter-

face.

Reset Security Configuration

Display

Resets the displayed values in the fields to the last set of saved

values.

Go Back to Previous Screen Redisplays the ATM UNI Interface ATM Security window.

Table 10-4. Field Descriptions for the ATM UNI Interface ATM Security Configuration Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric

Displays the the virtual path identifier for the

connection associated with the interface for

which ATM security is being configured.

[VCI] Default: N/ARange: 32–65535

Format: Numeric

Displays the virtual channel identifier associatedwith the virtual path identifier for the connection

associated with the interface for which ATM




255-700-447 10-7



Service Profile Default: Integrity-

172

Range: N/A

Format: Predefined

Specifies the service type that is provided by the

ATM security agent on this signaling or routing

PVC according to the ATM Forum Specification

af-sec-0172.000.

Integrity-172 Indicates that the integrity security service with-

out replay/reordering protection will be provided

to this connection.

Integrity-Confiden-

tiality-172

Indicates that the integrity security service and

confidentiality security service without

replay/reordering protection will be provided to

this connection.

Integrity-

ReplayReorderPro-

tection-172

Indicates that the integrity security service with


this connection.

Integrity-Confiden-tiality-ReplayReor-

derProtection-172

Indicates that the integrity security service andconfidentiality security service with replay/reor-

dering protection will be provided to this PVC.

Master Key Length Default: Key-128-

bits

Range: 40–256

Format: Predefined

(bits)

Specifies the length of the master key in bits.

Select a value from 40 to 256 bits (in increments

of 8 bits).

Master Key Default: 0

Range: N/A

Format: Hexadecimal

Specifies the master key that is shared between

two peer security agents for integrity and/or con-

fidential security services.

[SKU EncryptionAlgorithm]

Default: MD5Range: N/A

Format: Predefined

Displays the encryption algorithm used forencrypting session keys that need to be for-

warded from this security agent to the peer secu-

rity agent for this interface.

MD5 Indicates that the encryption algorithm used on

this interface will be MD5.

SHA-1 Indicates that the encryption algorithm used on

this interface will be SHA-1.

Integrity Security Service Panel

MAC Algorithm Default: HMAC-

MD5

Range: N/A

Format: Predefined

Specifies the type of MAC algorithm that is used

for integrity security service on this interface.

HMAC-MD5 Indicates that the MAC algorithm used for integ-

rity security service is HMAC-MD5.

HMAC-SHA-1 Indicates that the MAC algorithm used for integ-

rity security service is HMAC-SHA-1.






10-8 255-700-447


SessKeyLength Default: Key-128-

bits

Range: 40–256

Format: Predefined

Specifies the length of the integrity session key.


of 8 bits).

InitSessKeyA Default: 0

Range: N/A

Format: Hexadecimal

Specifies the initial session key for integrity secu-

rity service for communication from this security

agent to the peer security agent (side A of the

connection). The initial session key cannot be 0.

InitSessKeyB Default: 0

Range: N/A

Format: Hexadecimal


rity service for communication from the peer

security agent to this security agent (side B of the


SKU Time Interval Default: No-Auto-

matic-SKU


Specifies the frequency of the session key update

for integrity security service for communication

from this security agent to the peer security

agent.

No-Automatic-SKU Indicates that the session key update will be per-

formed only by executing a manual command.

Hourly Indicates that the session key will be updated

automatically once per hour.

Daily Indicates that the session key will be updated

automatically once per day.

Weekly Indicates that the session key will be updated

automatically once per week.

Confidentiality Security Service Panel

Note: The fields on this panel are displayed only when you select one of the following serviceprofiles in the Service Profile field:

• Integrity-Confidentiality-172

• Integrity-Confidentiality-ReplayReorderProtection-172

Encryption Algo-

rithm

Default: AES-128-

CBC

Range: N/A

Format: Predefined

Specifies the type of encryption algorithm used

for confidentiality security service is used.

AES-128-CBC Indicates that the AES-CBC algorithm with a key

length of 128 bits is used.


length of 192 bits is used.AES-256-192-CBC Indicates that the AES-CBC algorithm with a key


Triple-DES-192-

CBC

Indicates that the triple-DES-CBC algorithm with

a key length of 192 bits is used.





255-700-447 10-9



Viewing ATM Security Agent Statistics for an ATM UNI Interface

To view statistics for a configured ATM security agent for an ATM UNI inter-

face, perform the steps in the following procedure.

Begin

1 On the ATM UNI Interface ATM Security window, select the ATM UNI

Security Statistics command.

The ATM UNI Interface ATM Security Statistics window is displayed (see

Figure 10-2).

2 The commands and fields on this window are described in Table 10-5 and

Table 10-6.


Range: N/A

Format: Hexadecimal

Specifies the initial session key for confidentiality

security service for communication from this

security agent to the peer security agent (side A

of the connection). The initial session key cannot be 0.


Range: N/A

Format: Hexadecimal


security service for communication from the peer




matic-SKU

Range: N/A

Format: Predefined


for confidentiality security service for communi-

cation from this security agent to the peer secu-

rity agent.









[Sec Admin Status] Default: OutOfSer-

vice

Range: N/A

Format: Predefined

Displays the operational status of the ATM secu-

rity agent.

OutOfService Indicates that the ATM security agent is out ofservice.

InService Indicates that the ATM security agent is in ser-

vice.






10-10 255-700-447


3 To view all configured ATM security agents in the PSAX system, go the

procedure in the section, “Viewing All ATM Security Agents in the Sys-

tem” on page 10-45.

End



Figure 10-4. ATM UNI Interface ATM Security Statistics Window

Table 10-5. Commands for the ATM UNI Interface ATM Security Statistics Window

Command Function

Apply Session Key Update for

Integrity Security Services

Requests a session key update for integrity security services.


Confidentiality Security Ser-

vices

Requests a session key update for confidentiality security ser-

vices

Reset Security Statistics Dis-

play

Resets the values in the statistics counter fields on this win-

dow to 0.

Go Back to Previous Screen Redisplays the ATM UNI Interface ATM Security window.



255-700-447 10-11



Table 10-6. Field Descriptions for the ATM UNI Interface ATM Security Statistics Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




[VCI] Default: N/A

Range: 32–65535

Format: Numeric

Displays the virtual channel identifier associated

with the virtual path identifier for the connection



Display Only Fields

Security Agent

State

Default: Null

Range: N/A

Format: Predefined

Displays the current state of the ATM security

agent.

Null Indicates that the ATM security agent for a PVC

or SVC is not configured or it is configured with

the service profile No-Security-Service.

Unavailable Indicates that the interface and the ATM security

agent for a PVC or SVC are configured, but the

ATM security agent has not yet received an

Establish Confirmation or an Establish Indication

(in case of preconfiguration), or the security

negotiation through the security message

exchange protocol is not yet initiated.

Unsecured Indicates that the interface and ATM security


security negotiation process through the security

message exchange protocol has been initiated but

not finished.

Secure Indicates that the interface and ATM security

agent for a PVC or SVC are configured, and the


message exchange protocol has been initiated

and finished.




10-12 255-700-447


Integrity Current

Session Key A

Timer

Default: 0

Range: N/A

Format: Numeric

Displays the number of minutes since the session

key for integrity security service for communica-

tion from this side (side A) to the peer side

(side B) of the connection was last updated.Integrity Current

Session Key B

Timer

Default: 0

Range: N/A

Format: Numeric



tion from the peer side (side B) to this side

(side A) of the connection was last updated.

Confidentiality

Current Session

Key A Timer

Default: 0

Range: N/A

Format: Numeric


key for confidentiality security service for com-

munication from this side (side A) to the peer

side (side B) of the connection was last updated.

Confidentiality

Current Session

Key B Timer

Default: 0

Range: N/A

Format: Numeric





SDU Sent Default: 0

Range: N/A

Format: Numeric

Displays the number of service data units sent to

the upper layer.

SDU Received Default: 0

Range: N/A

Format: Numeric

Displays the number of service data units

received from the lower layer

SDU with Bad MAC Default: 0

Range: N/A

Format: Numeric


received from the lower layer with an incorrect

message authentication code.

SDU with BadSequence No


Format: Numeric

Displays the number of service data unitsreceived from the lower layer with the wrong

sequence number.

SKU OAM Cells

Sent

Default: 0

Range: N/A

Format: Numeric

Displays the number of total OAM session key

update cells sent by this security agent.

SKU OAM Cells

Received

Default: 0

Range: N/A

Format: Numeric


update cells received by this security agent

SKU OAM Cells

Discarded

Default: 0

Range: N/A

Format: Numeric

Displays the number of OAM session key update

cells discarded by this security agent.

Duplicate SKU

OAM Cells with

Mismatched Keys

Default: 0

Range: N/A

Format: Numeric

Displays the number of mismatched session keys

in duplicate session key exchange OAM cells.

Table 10-6. Field Descriptions for the ATM UNI Interface ATM Security Statistics Window (Continued)




255-700-447 10-13


Chapter 10 Configuring ATM Security AgentsConfiguring ATM Security for ATM PNNI SVCC RCC Nodes

Configuring ATM Security for ATM PNNI SVCC RCC Nodes

Accessing ATM Security for an ATM PNNI SVCC RCC Node

To access the ATM PNNI SVCC RCC Security Configuration window on

which you configure an ATM security agent for an ATM PNNI SVCC RCCnode, perform the steps in the following procedure.

Begin




2 On the Site-Specific Menu window, select the PNNI System-Wide Con-

figuration option.

The PNNI System-Wide Configuration menu window is displayed.

3 On the PNNI System-Wide Configuration menu window, select the PNNI

Node Configuration option.

The PNNI Node Table window is displayed (see Figure 10-5).

Note: At the time of initial PSAX system configuration, this table is

empty; that is, no ATM PNNI nodes are configured.

4 On the PNNI Node Table window, do one of the following

a For an existing ATM PNNI node, select the line in the table contain-

ing the node for which you want to configure an ATM security agent

and press Enter.

b For a new ATM PNNI node, select the Add Node Entry command.

Note: If you have not yet configured an ATM PNNI node, see

Chapter 6 for information.

The PNNI Node Configuration window is displayed (see Figure 10-6).

5 To configure an ATM security agent for the ATM PNNI SVCC RCC node,

go to the procedure in the next section, “Configuring an ATM Security

Agent for an ATM PNNI SVCC RCC Node”.

End




10-14 255-700-447


Configuring an ATM Security Agent for an ATM PNNI SVCC RCC Node

To configure an ATM security agent for an ATM PNNI SVCC RCC node, per-

form the steps in the following procedure.

Figure 10-5. PNNI Node Table Window

Figure 10-6. PNNI Node Configuration Window



255-700-447 10-15



Begin

1 On the PNNI Node Configuration window, make sure you have already

created an ATM PNNI node by selecting the Create Node Entry com-

mand (see Chapter 6 for more information).

Note: Do not bring the ATM PNNI node into service at this point, or, if

the node is already in service, take it out of service.

2 On the PNNI Node Configuration window, select the ATM Security

Config - Routing SVCC command.

The ATM PNNI SVCC RCC Security Configuration window is displayed

(see Figure 10-7).



Table 10-7.


rity-Confidentiality-ReplayReorderProtection-172 in theService Profile field, the Confidentiality Security Service panel is

displayed on the window (see Figure 10-8).

4 To view statistics for this ATM security agent, go to the procedure in the

next section, “Viewing ATM Security Agent Statistics for an ATM PNNI

SVCC RCC Node”.

End

Figure 10-7. ATM PNNI SVCC RCC Security Configuration Window (IntegritySecurity Service Only)




10-16 255-700-447




Figure 10-8. ATM PNNI SVCC RCC Security Configuration Window (Both Integrityand Confidentiality Security Services)

Table 10-7. Commands for the ATM PNNI SVCC RCC Security Configuration Window

Command Function


Service


into service, making the encryption operational.

Take Sec Admin Status Out ofService Takes the security configuration on the specified interface outof service, making the encryption not operational.

Create PNNI Security Configu-

ration


Delete PNNI Security Configu-

ration


face.


Display


values.




255-700-447 10-17



Table 10-8. Field Descriptions for the ATM PNNI SVCC RCC Security Configuration Window

Field Name Field Values Descriptions

[Peer Grp Id] Default: 0

Range: N/A

Format: Hexadecimal

Displays the first 12 bytes (default) of the ATM

address. This value, which is generated and dis-

played by the system automatically, is the combi-

nation of the ATM address and the node level.The first byte indicates the node level. The fol-

lowing bytes comes from the ATM address where

the number bytes coming from the ATM address

depend on the Node level. For example, a node

level of 96 bits (default) then the next 12 bytes

(96 its) are from the ATM address. For more

information, see the ATM Forum Specification,

Private Network-Network Interface (PNNI 1.0) Specifi-

cation Version 1.0, af-pnni-0055.000, Section 5.3.3,

Node Identifiers.


172Range: N/A

Format: Predefined


ATM security agent on this signaling or routingPVC according to the ATM Forum Specification

af-sec-0172.000.



to this PVC.

Integrity-Confiden-

tiality-172




this PVC.

Integrity-

ReplayReorderPro-

tection-172



this PVC.

Integrity-Confiden-

tiality-ReplayReor-

derProtection-172


confidentiality security service with replay/reor-



bits

Range: 40–256

Format: Predefined

(bits)



of 8 bits).


Range: 5–32

Format: Hexadecimal(bits)

Spcifies the value for the master key that is

shared between two peer security agents for

integrity or confidential security services or both.




10-18 255-700-447


[SKU Encryption

Algorithm]

Default: MD5

Range: N/A

Format: Predefined

Specifies the encryption algorithm used for

encrypting session keys that need to be for-


rity agent.MD5 Indicates that the MD5 encryption algorithm is

used for session key update.

SHA-1 Indicates that the SHA-1 encryption algorithm is

used for session key update.

IntegritySecurity Service Panel


MD5

Range: N/A

Format: Predefined








bits

Range: 40–256

Format: Predefined

(bits)



of 8 bits).


Range: 5–32

Format: Hexadecimal




connection). The initial session key cannot be 0.InitSessKeyB Default: 0

Range: 5–32

Format: Hexadecimal






matic-SKU

Range: N/A

Format: Predefined




agent.



Hourly Indicates that the session key will be updatedautomatically once per hour.





Table 10-8. Field Descriptions for the ATM PNNI SVCC RCC Security Configuration Window (Continued)




255-700-447 10-19




Note: The fields on this panel are displayed only when you select one of the following service

profiles in the Service Profile field:

• Integrity-Confidentiality-172 • Integrity-Confidentiality-ReplayReorderProtection-172

Encryption Algo-

rithm

Default: AES-128-

CBC

Range: N/A

Format: Predefined







AES-256-192-CBC Indicates that the AES-CBC algorithm with a key


Triple-DES-192-

CBC




Range: 5–32

Format: Hexadecimal

Specifies an initial session key for confidentiality


security agent to peer security agent. The initial

session key cannot be 0.


Range: 5–32

Format: Hexadecimal


security service for communication from peer

security agent to this security agent. The initial

session key cannot be 0.

SKU Time Interval Default: No-Auto-matic-SKU

Range: N/A

Format: Predefined

Specifies the frequency of the session key updatefor confidentiality security service for communi-


rity agent.














10-20 255-700-447


Viewing ATM Security Agent Statistics for an ATM PNNI SVCC RCC Node

To view statistics for a configured ATM security agent for an ATM PNNI SVCC

RCC node, perform the steps in the following procedure.

Begin

1 On the PNNI System-Wide Configuration menu window, select the PNNI

SVCC RCC Information option.

The PNNI SvccRcc Table window is displayed.

2 On the PNNI SvccRcc Table window, select a line containing the node for

which you want to view ATM security agent information.

The PNNI SVCC RCC Information window is displayed (see Figure 10-9).

For more information about this window, see Chapter 6.

3 On the PNNI SVCC RCC Information window, select the ATM Security

Statistics command.

The PNNI SVCC RCC Security Statistics window is displayed (see

Figure 10-10). The commands and fields on this window are described in

Table 10-9 and Table 10-10.


procedure in the section, “Viewing All ATM Security Agents in the Sys-

tem” on page 10-45.

End


vice

Range: N/A

Format: Predefined


rity agent.

OutOfService Indicates that the ATM security agent is out of

service.


vice.





255-700-447 10-21




Figure 10-9. PNNI SVCC RCC Information Window

Figure 10-10. ATM PNNI SVCC RCC Security Statistics Window




10-22 255-700-447



Table 10-9. Commands for the ATM PNNI SVCC RCC Security Statistics Window

Command Function




Apply Session Key Update forConfidentiality Security Ser-

vices

Requests a session key update for confidentiality security ser-vices


play


dow to 0.

Go Back to Previous Screen Redisplays the ATM PNNI SVCC RCC Security Configuration

window.

Table 10-10. Field Descriptions for the ATM PNNI SVCC RCC Security Statistics Window

Field Name Field Values DescriptionSlot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module typeFormat: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




[VCI] Default: N/A

Range: 32–65535

Format: Numeric







255-700-447 10-23



Display Only Fields

Security Agent

State

Default: Null

Range: N/A

Format: Predefined


agent.











Unsecured Indicates that the interface and ATM securityagent for a PVC or SVC are configured, but the



not finished.





and finished.

Integrity Current

Session Key A

Timer

Default: 0

Range: N/A

Format: Numeric



tion from this side (side A) to the peer side(side B) of the connection was last updated.

Integrity Current

Session Key B

Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current Session

Key A Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current Session

Key B Timer

Default: 0

Range: N/A

Format: Numeric



tion from the peer side (side B) to this side(side A) of the connection was last updated.

SDU Sent Default: 0

Range: N/A

Format: Numeric


the upper layer.


Range: N/A

Format: Numeric



Table 10-10. Field Descriptions for the ATM PNNI SVCC RCC Security Statistics Window (Continued)




Chapter 10 Configuring ATM Security AgentsConfiguring ATM Security for ATM PNNI Interfaces

10-24 255-700-447


Configuring ATM Security for ATM PNNI Interfaces

After you have configured an ATM PNNI SVCC RCC node and configured an

ATM security agent for that node, you are then able to configure an ATM

security agent for an ATM PNNI interface that uses that ATM PNNI SVCC

RCC node. For instructions on configuring an ATM security agent for an

ATM PNNI SVCC RCC node, see the section, “Configuring ATM Security for

ATM PNNI SVCC RCC Nodes” on page 10-13.

Accessing ATM Security for an ATM PNNI Interface

To access the ATM PNNI Interface ATM Security window on which you begin

ATM security configuration for an ATM PNNI interface, perform the steps in


Begin

1 On the ATM PNNI Interface Configuration window, be sure you have

already saved your configuration values by selecting the Apply Inter-

face Configuration command.

2 Select the ATM Security command.


Range: N/A

Format: Numeric




SDU with Bad

Sequence No

Default: 0

Range: N/A

Format: Numeric


received from the lower layer with the wrong

sequence number.

SKU OAM Cells

Sent

Default: 0

Range: N/A

Format: Numeric



SKU OAM Cells

Received

Default: 0

Range: N/A

Format: Numeric



SKU OAM Cells

Discarded

Default: 0




Duplicate SKU

OAM Cells with

Mismatched Keys

Default: 0

Range: N/A

Format: Numeric



Table 10-10. Field Descriptions for the ATM PNNI SVCC RCC Security Statistics Window (Continued)




255-700-447 10-25



The ATM PNNI Interface ATM Security window is displayed (see

Figure 10-11). The commands and fields are described in Table 10-11 and

Table 10-12.

3 To configure an ATM security agent for the ATM PNNI interface, go to

one of the following procedure:

• For an ATM PNNI signaling PVC interface, see the section, “Configur-ing an ATM Security Agent for an ATM PNNI Interface—Signaling

PVC”

• For an ATM PNNI routing PVC interface, see the section, “Configuring

an ATM Security Agent for an ATM PNNI Interface—Routing PVC”.

End


Figure 10-11. ATM PNNI Interface ATM Security Window

Table 10-11. Commands for the ATM PNNI Interface ATM Security Window

Command Function

ATM Security Config - Signal-

ing PVC

Displays the ATM PNNI Interface ATM Security

Configuration - Signaling PVC window.

ATM Security Config - Routing

PVC

Displays the ATM PNNI Interface ATM Security

Configuration - Routing PVC window.

ATM Security Stats - Signaling

PVC

Displays the ATM PNNI Interface ATM Security Statistics -

Signaling PVC window.

ATM Security Stats - Routing

PVC

Displays the ATM PNNI Interface ATM Security Statistics -

Routing PVC window.

Go Back to Previous Screen Redisplays the ATM PNNI Interface Configuration window.




10-26 255-700-447


Table 10-12 describes the fields on this table.

Configuring an ATM Security Agent for an ATM PNNI Interface—Signaling PVC

To configure an ATM security agent for an ATM PNNI Signaling PVC inter-

face, perform the steps in the following procedure.

Begin

1 On the ATM PNNI Interface ATM Security window, select the ATM

Security Config - Signaling PVC command.

The ATM PNNI Interface ATM Security Configuration - Signaling PVCwindow is displayed (see Figure 10-12).



Table 10-13.

Table 10-12. Field Descriptions for the ATM PNNI Interface ATM Security Window


Slot Default: N/A

Range: Depends onchassis type

Format: Numeric


which contains the interface for which ATMsecurity is being configured.

Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[ATM Security] Default: Unsup-ported

Range: N/A

Format: Predefined

alphanumeric

Displays an indicator whether ATM security isconfigured for signaling PVC connections or rout-

ing PVC connections or both on this interface.

Unsupported Indicates that ATM security is not configured for

either signaling or routing PVC connections.

SupportedOnSig-

nalingPvc

Indicates that ATM security is configured only

signaling PVC connections.

SupportedOnSig-

nalingPvcRouting-

Pvc

Indicates that ATM security is configured on both

signaling and routing PVC connections.



255-700-447 10-27






displayed on the window (see Figure 10-13)


next section, “Viewing ATM Security Agent Statistics for an ATM PNNIInterface—Signaling PVC”.

End

Figure 10-12. ATM PNNI Interface ATM Security ConfigurationWindow - Signaling PVC (Integrity Security Service Only)




10-28 255-700-447




Figure 10-13. ATM PNNI Interface ATM Security ConfigurationWindow - Signaling PVC (Both Integrity Security and ConfidentialityServices)

Table 10-13. Commands for the ATM PNNI Interface ATM Security Configuration - SignalingPVC Window

Command Function


Service


into service, making the encryption operational.

Take Sec Admin Status Out of

Service




ration



ration


face.


Display


values.

Go Back to Previous Screen Redisplays the ATM PNNI Interface ATM Security window.



255-700-447 10-29



Table 10-14. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - SignalingPVC Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




[VCI] Default: N/A

Range: 32–65535

Format: Numeric






172

Range: N/A

Format: Predefined



PVC according to the ATM Forum Specification

af-sec-0172.000.



to this connection.

Integrity-Confiden-

tiality-172




this connection.

Integrity-

ReplayReorderPro-

tection-172



this connection.

Integrity-Confiden-

tiality-ReplayReor-

derProtection-172





bits

Range: 40–256

Format: Predefined

(bits)



of 8 bits).




10-30 255-700-447



Range: N/A

Format: Hexadecimal




[SKU Encryption

Algorithm]

Default: MD5

Range: N/A

Format: Predefined

Displays the encryption algorithm used for










MD5Range: N/A

Format: Predefined








bits

Range: 40–256

Format: Predefined



of 8 bits).


Range: N/A

Format: Hexadecimal






Range: N/A

Format: Hexadecimal





Table 10-14. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - SignalingPVC Window (Continued)




255-700-447 10-31




matic-SKU




from this security agent to the peer securityagent.










Note: The fields on this panel are displayed only when you select one of the following serviceprofiles in the Service Profile field:



Encryption Algo-

rithm

Default: AES-128-

CBC

Range: N/A

Format: Predefined









Triple-DES-192-

CBC




Range: N/A

Format: Hexadecimal



security agent to the peer security agent (side A

of the connection). The initial session key cannot

be 0.


Range: N/AFormat: Hexadecimal


security service for communication from the peersecurity agent to this security agent (side B of the







10-32 255-700-447


Viewing ATM Security Agent Statistics for an ATM PNNI Interface—SignalingPVC

To view statistics for a configured ATM security agent for an ATM PNNI Sig-

naling PVC interface, perform the steps in the following procedure.

Begin


Security Stats - Signaling PVC command.

The ATM PNNI Interface ATM Security Statistics - Signaling PVC window

is displayed (see Figure 10-14).

2 The commands and fields on this window are described in Table 10-15

and Table 10-16.3 To view all configured ATM security agents in the PSAX system, go the

procedure in the section, See “Viewing All ATM Security Agents in the

System” on page 45.

End


matic-SKU




cation from this security agent to the peer secu-rity agent.










viceRange: N/A

Format: Predefined


rity agent.


service.


vice.





255-700-447 10-33





Figure 10-14. ATM PNNI Interface ATM Security Statistics - Signaling PVCWindow

Table 10-15. Commands for the ATM PNNI Interface ATM Security Statistics - SignalingPVC Window

Command Function






vices


vices


play


dow to 0.





10-34 255-700-447


Table 10-16. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - SignalingPVC Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




[VCI] Default: N/A

Range: 32–65535

Format: Numeric







255-700-447 10-35



Display Only Fields

Security Agent

State

Default: Null

Range: N/A

Format: Predefined


agent.















not finished.





and finished.

Integrity Current

Session Key ATimer

Default: 0



key for integrity security service for communica-tion from this side (side A) to the peer side

(side B) of the connection was last updated.

Integrity Current

Session Key B

Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current Session

Key A Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current SessionKey B Timer

Default: 0



key for integrity security service for communica-tion from the peer side (side B) to this side


SDU Sent Default: 0

Range: N/A

Format: Numeric


the upper layer.

Table 10-16. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - SignalingPVC Window (Continued)





10-36 255-700-447


Configuring an ATM Security Agent for an ATM PNNI Interface—Routing PVC

To configure an ATM security agent for a ATM PNNI Routing PVC interface,

perform the steps in the following procedure.

Begin


Security Config - Routing PVC command.

The ATM PNNI Interface ATM Security Configuration - Routng PVC win-

dow is displayed (see Figure 10-15).

2 Enter values in the fields on this window according to the informationprovided in Table 10-18. Commands on this window are described in

Table 10-17.




displayed on the window (see Figure 10-16).


Range: N/A

Format: Numeric




Range: N/A

Format: Numeric




SDU with Bad

Sequence No

Default: 0

Range: N/A

Format: Numeric



sequence number.

SKU OAM Cells

Sent

Default: 0

Range: N/A

Format: Numeric



SKU OAM CellsReceived


Format: Numeric

Displays the number of total OAM session keyupdate cells received by this security agent

SKU OAM Cells

Discarded

Default: 0

Range: N/A

Format: Numeric



Duplicate SKU

OAM Cells with

Mismatched Keys

Default: 0

Range: N/A

Format: Numeric



Table 10-16. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - SignalingPVC Window (Continued)




255-700-447 10-37




next section, “Viewing ATM Security Agent Statistics for an ATM PNNI

Interface—Routing PVC”.

End

Figure 10-15. ATM PNNI Interface ATM Security Configuration - Routing PVCWindow (Integrity Security Service Only)

Figure 10-16. ATM PNNI Interface ATM Security Configuration - Routing PVCWindow (Both Integrity Security and Confidentiality Services)




10-38 255-700-447




Table 10-17. Commands for the ATM PNNI Interface ATM Security Configuration - RoutingPVC Window

Command Function

Bring Sec Admin Status IntoService Brings the security configuration on the specified interfaceinto service, making the encryption operational.

Take Sec Admin Status Out of

Service




ration



ration


face.


Display


values.


Table 10-18. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - RoutingPVC Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




[VCI] Default: N/A

Range: 32–65535

Format: Numeric







255-700-447 10-39




172




PVC according to the ATM Forum Specificationaf-sec-0172.000.



to this connection.

Integrity-Confiden-

tiality-172




this connection.

Integrity-

ReplayReorderPro-

tection-172



this connection.

Integrity-Confiden-

tiality-ReplayReor-

derProtection-172





bits

Range: 40–256

Format: Predefined

(bits)



of 8 bits).


Range: N/A

Format: Hexadecimal




[SKU Encryption

Algorithm]

Default: MD5

Range: N/A

Format: Predefined

Displays the encryption algorithm used for










MD5

Range: N/A

Format: Predefined







Table 10-18. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - RoutingPVC Window (Continued)





10-40 255-700-447



bits

Range: 40–256Format: Predefined



of 8 bits).


Range: N/A

Format: Hexadecimal






Range: N/A

Format: Hexadecimal






matic-SKU

Range: N/A

Format: Predefined




agent.









Confidentiality Security Service PanelNote: The fields on this panel are displayed only when you select one of the following service

profiles in the Service Profile field:



Encryption Algo-

rithm

Default: AES-128-

CBC

Range: N/A

Format: Predefined





AES-192-CBC Indicates that the AES-CBC algorithm with a keylength of 192 bits is used.



Triple-DES-192-

CBC







255-700-447 10-41



Viewing ATM Security Agent Statistics for an ATM PNNI Interface—Routing PVC

To view statistics for a configured ATM security agent for an ATM PNNI Rout-

ing PVC interface, perform the steps in the following procedure.

Begin


Security Stats - Routing PVC command.

The ATM PNNI Interface ATM Security Statistics - Routing PVC window

is displayed (see Figure 10-17).

2 The commands and fields on this window are described in Table 10-19

and Table 10-20.


Range: N/A

Format: Hexadecimal



security agent to the peer security agent (side Aof the connection). The initial session key cannot

be 0.


Range: N/A

Format: Hexadecimal


security service for communication from the peer




matic-SKU

Range: N/A

Format: Predefined




rity agent.










vice

Range: N/A

Format: Predefined


rity agent.


service.


vice.






10-42 255-700-447



procedure in the section, See “Viewing All ATM Security Agents in the

System” on page 45.

End



Figure 10-17. ATM PNNI Interface ATM Security Statistics - Routng PVC Window

Table 10-19. Commands for the ATM PNNI Interface ATM Security Statistics - Routing

PVC Window

Command Function






vices


vices


play


dow to 0.




255-700-447 10-43



Table 10-20. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - RoutingPVC Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




[VCI] Default: N/A

Range: 32–65535

Format: Numeric








10-44 255-700-447


Display Only Fields

Security Agent

State

Default: Null

Range: N/A

Format: Predefined


agent.















not finished.





and finished.

Integrity Current

Session Key ATimer

Default: 0



key for integrity security service for communica-tion from this side (side A) to the peer side

(side B) of the connection was last updated.

Integrity Current

Session Key B

Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current Session

Key A Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current SessionKey B Timer

Default: 0



key for integrity security service for communica-tion from the peer side (side B) to this side


SDU Sent Default: 0

Range: N/A

Format: Numeric


the upper layer.

Table 10-20. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - RoutingPVC Window (Continued)




255-700-447 10-45


Chapter 10 Configuring ATM Security AgentsViewing All ATM Security Agents in the System

Viewing All ATM Security Agents in the System

You can view all the interfaces on which ATM security agents have been con-

figured on the PSAX system, and the statistics for each configured ATM secu-

rity agent. To view this information on the ATM Security Agents Table win-

dow, perform the steps in the following procedure.

Begin




2 On the Site-Specific Menu window, select the ATM Security Agents

option.

The ATM Security Agents Table window is displayed (see Figure 10-18).

All the interfaces that have been configured with ATM security agents in

the PSAX system are displayed on this window. Figure 10-21 and

Figure 10-22 describe the commands and fields on this window.


Range: N/A

Format: Numeric




Range: N/A

Format: Numeric




SDU with Bad

Sequence No

Default: 0

Range: N/A

Format: Numeric



sequence number.

SKU OAM Cells

Sent

Default: 0

Range: N/A

Format: Numeric



SKU OAM CellsReceived


Format: Numeric

Displays the number of total OAM session keyupdate cells received by this security agent

SKU OAM Cells

Discarded

Default: 0

Range: N/A

Format: Numeric



Duplicate SKU

OAM Cells with

Mismatched Keys

Default: 0

Range: N/A

Format: Numeric



Table 10-20. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - RoutingPVC Window (Continued)





10-46 255-700-447


3 To view statistics for an ATM security agent, select a line containing the

interface ID of the interface for which an ATM security agent was config-

ured, and press Enter.

The ATM Security Statistics window is displayed (see Figure 10-19).

Table 10-23 and Table 10-24 describe the commands and fields on this

window.Note: If you have no ATM security agents configured in your PSAX

system, this window does not display any table entries.

End

Table 10-21 describes the commands for this window.

Figure 10-18. ATM Security Agents Table Window (Populated)

Table 10-21. Commands for the ATM Security Agents Table Window

Command Function





Find... Searches the table for a particular ATM security agent

defined in the PSAX system. To find a particular security

agent, enter values in the Intf Id, VPI, and VCI fields. If the

security agent exists, it is displayed on the first line of the

table.

Go Back to Previous Screen Redisplays the Site-Specific Menu window.



255-700-447 10-47



Table 10-22 describes the fields for this window.

Table 10-22. Field Descriptions for the ATM Security Agents Table Window


Intf ID Default: N/A

Range: Depends onchassis type and mod-

ule type

Format: Numeric

(format represents

SSPPCCC [slot, port,

channel])

Displays the identification (index) number of the

interface. This interface ID is automaticallyassigned by the PSAX system at the time the

interface is configured.

VPI Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




VCI Default: N/A

Range: 32–65535

Format: Numeric








10-48 255-700-447


Security Agent

State

Default: Null

Range: N/A

Format: Predefined


agent.















not finished.





and finished.

Total: 0/0 Default: N/A

Range: Depends on

the chassis type and

module typeFormat: Numeric

Displays the first number and last number of all

ATM-type connections that have ATM security

encryption configured on them in the PSAX sys-

tem.

Table 10-22. Field Descriptions for the ATM Security Agents Table Window (Continued)




255-700-447 10-49





Figure 10-19. ATM Security Statistics Window

Table 10-23. Commands for the ATM Security Statistics Window

Command Function





Confidentiality Security Ser-vices


vices


play


dow to 0.

Go Back to Previous Screen Redisplays the ATM Security Agents Table window.




10-50 255-700-447


Table 10-24. Field Descriptions for the ATM Security Statistics Window


Slot Default: N/A

Range: Depends on

chassis type

Format: Numeric




Port Default: N/A

Range: Depends on

module type

Format: Numeric




Range: Depends on

module type

Format: Numeric



ured.

[VPI] Default: N/A

Range: 0–255 (ATM

UNI); 0–4095 (ATM

NNI)

Format: Numeric




[VCI] Default: N/A

Range: 32–65535

Format: Numeric





Display Only Fields

Security Agent

State

Default: Null

Range: N/A

Format: Predefined


agent.















not finished.





and finished.



255-700-447 10-51



Integrity Current

Session Key A

Timer

Default: 0

Range: N/A

Format: Numeric



tion from this side (side A) to the peer side

(side B) of the connection was last updated.Integrity Current

Session Key B

Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current Session

Key A Timer

Default: 0

Range: N/A

Format: Numeric





Confidentiality

Current Session

Key B Timer

Default: 0

Range: N/A

Format: Numeric





SDU Sent Default: 0

Range: N/A

Format: Numeric


the upper layer.


Range: N/A

Format: Numeric




Range: N/A

Format: Numeric




SDU with BadSequence No


Format: Numeric

Displays the number of service data unitsreceived from the lower layer with the wrong

sequence number.

SKU OAM Cells

Sent

Default: 0

Range: N/A

Format: Numeric



SKU OAM Cells

Received

Default: 0

Range: N/A

Format: Numeric



SKU OAM Cells

Discarded

Default: 0

Range: N/A

Format: Numeric



Duplicate SKU

OAM Cells with

Mismatched Keys

Default: 0

Range: N/A

Format: Numeric



Table 10-24. Field Descriptions for the ATM Security Statistics Window (Continued)





10-52 255-700-447





255-700-447 11-1

11 Using System Diagnostics


The PSAX system diagnostic functions give you the ability to:

• View the status of the PSAX system including:

~ Version of the PSAX system software currently running

~ Status of the system disk on the CPUn module

~ CPUn module and memory utilization details

~ Statistics on the message pool and the cell buffers

• Run cell test diagnostics to determine whether a specified port is operating

correctly

• Reboot (reinitialize) the PSAX chassis, CPUn module, user-selected I/O

modules, or all components in the chassis

• Remove configuration files

• Unlock a telnet session remotely

• Perform OAM loopback tests

• Configure, activate, and deactivate OAM functions

The Diagnostics Menu window provides access to the diagnostic functions of

the PSAX system. See Table 11-1 for a description of the menu options.

Table 11-1. Menu Option Descriptions for the Diagnostics Menu Window

Menu Options Description

System Information Displays the System Information Screen window on which you

can view the status of the PSAX system including the version of

the PSAX system software currently running, the status of the

system disk on the CPUn module, and statistics on the message

pool and the cell buffers.

Cell Test Diagnostics Displays the Cell Test Diagnostics window on which you can

run cell test diagnostics to determine whether a specified port is

operating correctly.

Reboot Hardware

Components

Displays the Remote Reboot Configuration window on you can

reboot (reinitialize) the PSAX chassis, the primary or backup

(standby) CPUn module, I/O and server modules, or all compo-

nents in the chassis; and perform a switchover from the primaryCPUn module to the standby CPUn module.

Note: If you have just upgraded your PSAX system software,

make sure that all module firmware drivers are completely and

successfully downloaded before selecting this menu option.



Chapter 11 Using System DiagnosticsViewing System Status

11-2 255-700-447


Viewing System Status

To view the status of the PSAX system, perform the following procedure.

Begin

1 From the Console Interface Main Menu window (see Figure 11-1), select

the Diagnostics option.


2 Select the System Information option.

The System Information window is displayed (see Figure 11-3). The dis-

play-only fields on this window are described in Table 11-3.

End

Remove

Configuration Files

Deletes all user-created configuration data from the PSAX sys-

tem. However, IP addresses that you set up on the System Iden-

tification panel of the Site-Specific Configuration window are

not deleted.

! CAUTION:Be very certain you have a need to delete all your configura-tion data before you use this option. If you need assistance,call technical support at Lucent Worldwide Services (LWS).

Unlock Shell/Ping Displays the Unlock Shell/Ping window on which you can

unlock a telnet session remotely or send a ping command to a

remote device.

OAM Loopback Displays the OAM Loopback Table window on which you can

an configure an OAM loopback connection.OAM Activate and

Deactivate

Displays the OAM Activate & Deactivate Table window on

which you perform continuity checks on a connection running

between PSAX systems when the interface is out of service.

Go Back to Main

Menu

Redisplays the Console Interface Main Menu window.

Table 11-1. Menu Option Descriptions for the Diagnostics Menu Window (Continued)

Menu Options Description



255-700-447 11-3



Figure 11-1. Console Interface Main Menu Window (Diagnostics Option Selected)

Figure 11-2. Diagnostics Menu Window




11-4 255-700-447


The commands on this window are described in Table 11-2.

Figure 11-3. System Information Window

Table 11-2. Commands for the System Information Screen

Command Function

Go to Module ConnCount Table Displays the Module Connection Count Table window. This

window can be used as a troubleshooting aid by technical

support personnel.

Continuous Update Continuously updates the information in the fields every sec-

ond. Use this command to turn continuous updating on and

off as needed.

Go Back to Diagnostics Screen Redisplays the Diagnostics Menu window.

Table 11-3. Field Descriptions for the System Information Window


Version, Time and MAC Address (display only)

[Software Version] Default: N/A

Range: N/A

Format: Predefined

alphanumeric

Displays the version of the system software cur-

rently running on the CPU.

[Current Time] Default: N/A

Range: N/A

Format: Numeric

(hours:minutes:sec-

onds)

Displays the Universal Coordinated Time (UTC).

This time value for the PSAX system is set on the

Site-Specific Configuration window.



255-700-447 11-5



[System Up Time] Default: N/A

Range: N/A

Format: Numeric

(hours:minutes:sec-onds)

Displays the amount of time the PSAX system has

been running since the last time you applied

power to the system, or booted (initialized) the

CPU module.

[MAC ADDRESS] Default: N/A

Range: N/A

Format:

Displays the media access control (MAC) address

of the Ethernet port of the CPU module.

[Switch Alarm Sta-

tus]

Default: NotAvail-

able

Range: N/A

Format: Predefined

alphanumeric

Displays the current status of the alarm on the

PSAX system.

NotAvailable Indicates that the alarm status could not be

retreived.

None Indicates that no alarm is present.

Minor Indicates that a minor alarm is present.

Major Indicates that a major alarm is present.

Critical Indicates that a critical alarm is present.

Primary CPU, Disc, and Memory (display only)

[Disc Space] Default: N/A

Range: N/A

Format: Numeric

(kilobytes)

Free(Bytes): Displays the amount of unused

(available) system disk space in kilobytes on the

CPU module.

Total(Bytes): Displays the amount of total system

disk space in kilobytes on the CPU module.

[Memory/RAM] Default: N/A

Range: N/A

Format: Numeric

(bytes)

Free(Bytes): Displays the amount of unused

(available) random access memory on the system

disk of the CPU module.

Total(Bytes): Displays the amount of total ran-

dom access memory on the system disk of the

CPU module.

[CPU Type] Default: (see

description)

Range: N/A

Format: Predefined

alphanumeric

Displays the type of CPU module (that is, CPU1,

CPU2, CPU3L, or CPU3 module) and the proces-

sor clock speed (in MHz) of the currently active

(primary) CPU module.

[CPU Utilization] Default: 0.00%

Range: N/A

Format: Percentage

Displays the percentage of time that the CPU

module is used for processing data traffic.






11-6 255-700-447


[Disk Status] Default: Ok

Range: N/A

Format:

Displays the checking status of the system disk on

the CPU module.

Ok Indicates that no errors on the system disk are

detected.

Error Indicates that one or more errors on the system

disk are detected.

Message Pool and Cell Buffers (display only)

Note: The following fields are used primarily by technical support personnel for diagnostic

purposes.

[Tx One Cell] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the number of cells within the

transmit-one-cell pool.

Used: Displays the number of cells currently

being used within the transmit-one-cell pool.

High: Displays the high-water mark of cells usedwithin the transmit-one-cell pool.

[Rx One Cell] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the number of cells within the

receive-one-cell pool.

Used: Displays the number of cells currently

being used within the receive-one-cell pool.

High: Displays the high-water mark of cells used

within the receive-one-cell pool.

[Rx Multi Cell] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the number of multiple cells

within the receive-multicell-pool.

Used: Displays the number of multiple cells cur-

rently being used within the receive-multicell-

pool.

High: Displays the high-water mark of multicells

used within the receive-multicell-pool.

[Message Pool] Default: N/A

Range: N/A

Format: Numeric

Total: Displays the total number of messages in

the message pool.

Used: Displays the number of messages currently

being used in the message pool.

High: Displays the high-water mark number of

messages used in the message pool.

Backplane A/B and Cell Bus (display only)

[Clock] Default: Good

Range: N/A

Format: Predefined

alphanumeric

Plane A: Displays the status of the clock on back-

plane A.

Plane B: Displays the status of the clock on back-

plane B.

[Cell Circuit] Default: Good

Range: N/A

Format: Predefined

alphanumeric

Plane A: Displays the status of the cell circuit on

backplane A.

Plane B: Displays the status of the cell circuit on

backplane B.





255-700-447 11-7


Chapter 11 Using System DiagnosticsChecking the Module Connection Count

Checking the Module Connection Count

To view the Module Connection Count Table, perform the following proce-

dure.

Begin

1 From the Console Interface Main Menu window, select the Diagnosticsoption.


2 Select the System Information option.

The System Information window is displayed.

3 Select the Go to Module ConnCount Table command.

The Module Connection Count Table appears (see Figure 11-4).


4 Select the Continuous Update command to update the field values.

Select it again to end the updates.

End

[Error Cells Rx] Default: 0

Range: N/A

Format: Numeric

Displays the number of errored cells (BIP16)

received since the last time you applied power to

the system, or booted (initialized) the CPU mod-

ule.[Misaligned] Default: 0

Range: N/A

Format: Numeric

Indicates the number of misaligned cells received

since the last time you applied power to the sys-

tem, or booted (initialized) the CPU module.

[Inter CPU Transfer

Type]

Default: Aal5

Range: N/A

Format: Predefined

alphanumeric

Displays the type of format for inter-CPU file

transfer.

AAl5 Indicates that files are transferred by AAL5.

Ftp Indicates that files are transferred by FTP.

Rsh Indicates that files are transferred by RSH.

Nfs Indicates that files are transferred by NFS.





Chapter 11 Using System DiagnosticsChecking the Module Connection Count

11-8 255-700-447


Figure 11-4. Module Connection Count Window

Table 11-4. Commands for the Module Connection Count Table Window

Command Function

Continuous Update Continuously updates the information in the fields every sec-

ond. Use this command to turn continuous updating on and

off as needed.

Go Back to System Information

Screen

Redisplays the System Information window.

Table 11-5. Field Descriptions for the Module Connection Count Table Window


Id Default: N/A

Range: Depends on

chassis type

Format: Numeric

Displays the physical slot location of the module.

Input Default: N/A

Range: -1–2

Format: Numeric

Displays the count of input connections on the

CPUn module.

Output Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output connections on the

CPUn module.

Output MCast Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output multicast connections

on the CPUn module.



255-700-447 11-9


Chapter 11 Using System DiagnosticsRunning Cell Test Diagnostics

Running Cell Test Diagnostics

To determine whether a port is operating correctly, perform the followingprocedure.

Note: This procedure is only applicable for I/O modules configured with

an ATM UNI interface type.

Begin

1 On the Console Interface Main Menu window (see Figure 11-1), select



2 On the Diagnostics Menu window, select the Cell Test Diagnostics option.

The Cell Test Diagnostics window is displayed (see Figure 11-5).

3 To set up a connection for the port you want to test, enter values in the

fields on this window according to the information provided in

Table 11-7.

Note: If you do not enter the correct values for the location (slot, port,

and channel) of the ATM UNI interface on the I/O module, the

connection will not be established.

4 Select the Apply and Configure Payload command.

The Cell Test Payload Configuration window is displayed (see


describes the fields of this window.

5 Select the first line in the Transmitted Payload field and enter the data

you want to transmit. Repeat this step for the second and third lines of

this field.

6 Select the Refresh Transmit Payload command.

This command applies the values for the test payload.

I/O Input Default: N/A

Range: -1–2

Format: Numeric

Displays the count of input connections on the I/O

module.

I/O Output Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output connections on the I/O

module.

I/O Output MCast Default: N/A

Range: -1–2

Format: Numeric

Displays the count of output multicast connections

on the I/O module.

Table 11-5. Field Descriptions for the Module Connection Count Table Window (Continued)





11-10 255-700-447


7 Select the Send Payload Once or the Send Payload Continuously

command.

The system displays the protocol, cells transmitted or the cells received or

both, depending on the type of flow selected on the Cell Test Diagnostics

window (see Figure 11-5).

End


Figure 11-5. Cell Test Diagnostics Window

Table 11-6. Commands for the Cell Test Diagnostics Window

Command Function

Apply and Configure Pay-

load

Applies the traffic parameters you set, and displays the Cell

Test Payload Configuration window.

Go Back to Diagnostics

Menu

Redisplays the Diagnostics Menu window.



255-700-447 11-11



Table 11-7. Field Descriptions for the Cell Test Diagnostics Window

Field Names Values Description

Slot Default: N/A

Range: Chassis

specific

Format: numeric

The slot number containing the I/O module configured with the

ATM UNI interface that you want to test.

Port Default: N/A

Range: depends on

module

Format: numeric

The port number on the I/O module configured with the ATM

UNI interface you want to test.

Channel

(display only)

Default: N/A

Range: depends on

module

Format: numeric

The channel number on the I/O module configured with the

ATM UNI interface for the port you want to test.

Interface Default: Uncon-

figured

Range: N/A

Format: Pre-

defined alphanu-

meric

Indicates the interface type configured on this channel. To run

cell test diagnostics, use the value AtmUni4-0,AtmUni3-0, or

AtmUni3-1.

Unconfigured Indicates that no interface has been applied.

AtmUni3-0 Indicates that the ATM UNI 3.0 interface is applied.



AtmIispUser Indicates that the ATM IISP User interface is applied.

AtmIispNetwork Indicates that the ATM IISP Network interface is applied.

AtmPnni1-0 Indicates that the ATMPNNI interface is applied.

CircuitEmula-

tion

Indicates that the Circuit Emulation interface is applied.

DbCirEm Indicates that the Dynamic Bandwidth Circuit Emulation inter-

face is applied.

PriIsdnUser Indicates that the PRI ISDN User interface is applied.

PriIsdnNetwork Indicates that the PRI ISDN Network interface is applied.

TerminalEmula-

tion

Indicates that the Terminal Emulation interface is applied.

OperStatus

(display only)

Default: InService


Indicates whether conditions are currently affecting the opera-

tional status of this port.

InService Indicates that no conditions are preventing the port from being

fully operational.

OutOfService Indicates that some condition is preventing the port from being

configured with an interface.




11-12 255-700-447


AdminStatus

(display only)

Default: InService

Range: N/A

Format: Predefined

Indicates whether conditions are currently affecting the opera-

tional status of this interface.

InService Indicates that the interface is operational.

OutOfService Indicates that the interface is not operational.

VPI Default: N/A

Range: 0–255

Format: Numeric

The virtual path identifier (VPI) for the channel you want to

test.

VCI/DLCI Default: N/A

Range: 32–65535

(VCI); 16–1024

(DLCI)

The virtual channel identifier (VCI) or the data link connection

identifier (DLCI) for the channel you want to test.

VUNI Default: 001


The virtual UNI (VUNI) associates itself with the egress part of

the A2B or B2A side of the connection.

Service Type Default: Ubr

Vbr-nrt2

Vbr-nrt1,Vbr-rt2

Vbr-rt1

Vbr-express

Cbr4

Cbr3

Cbr2

Cbr1

The service type you have set up for the connection.

Flow Default: Sim-

plexTxSimplexRx

Duplex

The type of traffic flow you want to set up for the test: one-way

transmit, one-way receive, or two-way flow.

[Test Status] Default: Not-run-

ning

Range: N/A

Format: Predefined

Indicates whether or not cell test payload is currently being

transmitted, received, or both.

Not-running Indicates that the cell test payload is currently being transmit-

ted, received, or both.

Running Indicates that the cell test payload is not currently being trans-

mitted, nor received.

Table 11-7. Field Descriptions for the Cell Test Diagnostics Window (Continued)




255-700-447 11-13




Figure 11-6. Cell Test Payload Configuration Window

Table 11-8. Commands for the Cell Test Payload Configuration Window

Command Function

Apply Transmit Payload Applies the values you enter in the Transmitted Pay-

load field.

Reset Display Sets the values in the Transmitted Payload field to the

last saved (applied) set of values.Continuous Update Continuously updates the information in the [Packets

Transmitted, Received, and Mismatched] fields every

two seconds. Select this command and press Enter to

turn the continuous updating on and off as needed

(similar to a toggle switch).

Reset Cell Counters Sets the values in the [Packets Transmitted, Received,

and Mismatched] fields to zero.

Send Payload Once Sends the user-selected payload one time.

Send Payload Continuously Sends the user-selected payload continuously, 10

times per second.

Delete Connection Deletes the connection you set up on the Cell TestDiagnostics window. Use this command after you

have sent a test payload by using the Send Payload

Once command. This command is displayed only

after you have sent a payload one time.




11-14 255-700-447


Stop Cell Test Stops a continuously running test and deletes the

connection you set up on the Cell Diagnostics win-

dow. Use this command after you have sent a test

payload by using the Send Payload Continuouslycommand. This command is displayed only after you

have sent a payload continuously.

Go Back to Cell Test Diag-

nostics

Redisplays the Cell Test Diagnostics window.

Table 11-8. Commands for the Cell Test Payload Configuration Window (Continued)

Command Function

Table 11-9. Field Descriptions for the Cell Test Payload Window


[Received Payload] Default: Dependent

on the input in the

Transmitted Pay-

load field

Range: N/A

Format: Predefined

Displays the data you entered in the Transmitted

Payload field if the port is working.

Transmitted Pay-

load

Default: N/A

Range: N/A

Format: Predefined

Indicates the data you want to transmit for test

purposes.

[Protocol] Default: Atm

Range: N/A

Format: Predefined

Indicates the type of protocol in use. ATM UNI is

the only supported protocol.

[Test Status] Default: N/A


Indicates whether or not the cell test payload is

currently being transmitted or received or both.

Running Indicates the test is running.

Not-running Indicates the test is not running.

[Packets Transmit-

ted]

Default: 0

Range: N/A

Format: Predefined

The number of packets transmitted.

[Packets Received] Default: 0

Range: N/A

Format: Predefined

The number of packets received.

[Packets Mis-

matched]

Default: 0

Range: N/A

Format: Predefined

The number of packets that are not associated

with the number transmitted/number received

pairs.



255-700-447 11-15


Chapter 11 Using System DiagnosticsRebooting PSAX Hardware Components

Rebooting PSAX Hardware Components

Specific hardware components may need to be restarted for several reasons,

including:

• When you want to revert back to a saved configuration

• When a module is not adhering to its configuration

• When timing problems cannot be resolved automatically

• When firmware changes on a module

• After turning on system-wide features (such as the GR-303 Interface)

To reboot (initialize) one or more components in a PSAX system, perform the


Perform the following procedure to reboot the system and apply the configu-

ration changes performed in the previous procedures.

Begin

s

1 Select the Console Interface Main Menu window by pressing Ctrl+G.

The Console Interface Main Menu window is displayed.

2 Select the Save Configuration [Modified] option (Ctrl+A) to save the

modifications. [Modified] is removed from the window when Save Con-

figuration is selected.

3 Select the Diagnostics option.


4 Select the Reboot Hardware Components option.

The Remote Reboot Configuration window is displayed (see

Figure 11-7). The commands on this window are described in

Table 11-10.

5 Select the appropriate command as needed.

For the options preceding the Primary Switchover option, you will be

prompted twice from the following table to confirm whether you want to

proceed with the operation. For the Primary Switchover option, you will

have the opportunity to save you configuration if you did not already do

so (see step 1). The system displays a prompt in the status line, asking

whether you are you sure you want to reboot.

! CAUTION:

Selecting any option on the Remote Reboot Configuration window willinterrupt all traffic running on the chassis and/or the selected I/O mod-ule(s).

6 Press Y (yes) to proceed with the reboot operation, or press N to cancel

the request.




11-16 255-700-447


The VxWorks shell is restarted in a process called the auto-boot. If you

press a key during the auto-boot process, the auto-boot process will stop.

You can resume the auto-boot process by pressing Shift+2 (the @ sym-

bol). The system reboot takes 5–10 minutes, depending your system con-

figuration.

7 After the Press RETURN to log in... message is displayed, log backinto the system, if necessary.

End

Figure 11-7. Remote Reboot Configuration Window

Table 11-10. Commands for the Remote Reboot Configuration Window

Command Function

Note: If you have just upgraded your PSAX system software, make sure that all module firmware

drivers are completely and successfully downloaded before using the commands on this window.

Reboot the I/O Card in Slot:__ Reboots the I/O or server module in the slot you designate.

This command is the equivalent to physically removing the

module from and then reinserting it into the chassis.

Reboot All I/O Cards Reboots all I/O and server modules in the chassis, without

affecting the primary CPU module or backup (standby)

CPU module (if one is present). This command is theequivalent to physically removing the modules from and

then reinserting them into the chassis.



255-700-447 11-17



Reboot Primary CPUWARNING:!

Rebooting the PSAX system with a single (nonredun-

dant) CPU module or component will interrupt all trafficrunning through the PSAX chassis.

Reboots (reinitializes) the primary CPU module. If a

backup (standby) CPU module is present in the system,

traffic running through the PSAX chassis is not inter-

rupted.Reboots (reinitializes) the CPU module. This com-

mand also reboots all I/O and server modules in the chas-

sis, as instructed by the system software initialization

process. In a system with redundant (two) CPU modules,

the primary CPU module remains the primary one.

Reboot Backup CPU Reboots (reinitializes) the backup (standby) CPU module,

without affecting the primary CPU module. Used only in

redundant PSAX systems.Reboot Chassis

WARNING:!

Rebooting the PSAX system with the Reboot Chassiscommand will interrupt all traffic running through thePSAX chassis.

Reboots the primary CPU module, the backup (standby)

CPU module (if one is present), and all I/O and server mod-

ules in the chassis; purges trap log.

This command is equivalent to a system cold start, that is,

removing the power from the chassis and then reapplying

the power.

Use this command:

• After enabling the GR-303 interface feature.

• After changing the call control resource allocation setting

for H.248 protocol feature.

Primary Switchover Switches processing control from the primary CPU module

to the backup (standby module) and immediately begins

rebooting the original primary CPU module. As this process

proceeds, the new primary CPU module (originally the

standby CPU) synchronizes the management information

base (MIB) data with the new standby CPU module (origi-

nally the primary CPU). The green LED ACTIVE is illumi-

nated on the primary CPU module. Used only in redundant

PSAX systems.

Note: Using this command does not interrupt traffic run-

ning through the PSAX chassis.

Go Back to Diagnostics Menu Displays the Diagnostics Menu window.

Table 11-10. Commands for the Remote Reboot Configuration Window (Continued)

Command Function



Chapter 11 Using System DiagnosticsRemoving Configuration Files

11-18 255-700-447


Removing Configuration Files

To remove configuration files, perform the following procedure.

WARNING:!

The following procedure removes all configuration files from the CPUand restores the CPU to its factory default settings. All data will beremoved except the CPU IP address, gateway IP address, and SNMP trapdestinations.

Begin


option.


2 On the Diagnostics Menu window, select the Remove Configuration Files option. The following prompt is displayed.

Are you sure that you want to remove all the configuration

files? (y/n)

3 Answer y to remove the files or n to cancel.

End

Unlocking a Telnet Session

If you are in a telnet session to connect to an PSAX system and a lockup con-dition occurs, you must use another PSAX system in the network to remotely

access and unlock the PSAX system with the telnet lock-up problem. To

unlock the telnet session of a PSAX system, or to check the connectivity of a

PSAX system, perform the following procedure.

Begin

1 From another PSAX system, log onto the PSAX system console interface.




3 On the Diagnostics Menu window, select the Unlock Shell / Ping option.

The Unlock Shell / Ping window is displayed (see Figure 11-8).

4 Type the IP address of the PSAX system that is connected to the locked-

up telnet session in the IP Address field,.

5 Select the Unlock Remote Shell command.



255-700-447 11-19


Chapter 11 Using System DiagnosticsOperations Administration and Maintenance (OAM)

This command corrects a telnet lock-up condition, and enables you to

access the specified PSAX system.

6 To verify that access has been restored to the specified PSAX system,

select the Ping Remote Machine command.

This command sends a ping command to the remote PSAX system speci-

fied in the IP Address field or to another switching device to indicatewhether or not you can connect to that remote device.

End

Operations Administration and Maintenance (OAM)

OAM is supported for end-to-end and end-segment-point connections. In

order to support OAM functionality, you must have already configured one

I/O module for circuit emulation and one I/O module for ATM as follows:

• The first port is assigned to the near-end user.

• The second port is assigned to the far-end user, using the same configura-

tion as the first port.

For further information about OAM, see Chapter 3. To enable OAM connec-tions, see the PacketStar ® PSAX System Connections Provisioning Guide.

Enabling OAM Loopback Functions

To enable OAM loopback functionality, perform the following procedure.

Figure 11-8. Unlock Shell / Ping Window




11-20 255-700-447


Begin


option.


2 On the Diagnostics Menu window, select the OAM Loopback option.

The OAM Loopback Table window is displayed (see Figure 11-9).

3 Select the OAM Add a loopback command.

The OAM LOOPBACK window is displayed (see Figure 11-10).



5 To apply the desired OAM Loopback configuration, select the Apply

Action command.

End


Figure 11-9. OAM Loopback Table Window

Table 11-11. Commands for the OAM Loopback Table Window

Command Function







255-700-447 11-21




Total: 0/0 The first number in this field indicates the number of

the connection table entry on the first line of the cur-

rently displayed window. The second number indi-

cates the total number of connection table entries forthis connection type.

Find . . . To find a particular connection, enter values in the

Slot, Port, Channel, VPI, and VCI fields. If the connec-

tion exists, it displays on the first line of the table.

OAM Add a Loopback Displays the OAM Loopback window.

Go Back to Diagnostics Menu Redisplays the Diagnostics Menu window.

Table 11-11. Commands for the OAM Loopback Table Window (Continued)

Command Function

Figure 11-10. OAM LOOPBACK Window

Table 11-12. Commands for the OAM Loopback Window

Command Function

Continuous Update Continuously updates the fields in the Statistics

panel every two seconds. Select this command toturn the continuous updating on and off as

needed (similar to a toggle switch).

Note: Updating the test display does not always

keep pace with the actual PSAX system operation.

Use this command to avoid misinterpretation of

test results.




11-22 255-700-447


Apply Action Applies the values you enter in this window.

Go Back to OAM Loopback

Table Screen

Redisplays the OAM Loopback Table window.

Table 11-12. Commands for the OAM Loopback Window (Continued)

Command Function

Table 11-13. Field Descriptions for the OAM Loopback Window


Connection Interface Panel

Slot Default: 0

Range: Depends on

chassis

Format: Numeric

The module slot number of the ATM connection on

which you want to perform the OAM loopback test.

Port Default: 0

Range: Depends on

module

Format: Numeric

The port number of the ATM connection on which

you want to perform the OAM loopback test.

Channel Default: 0

Range: Depends on

module

Format: Numeric

The channel number of the ATM connection on

which you want to perform the OAM loopback test.

VPI Default: 0

Range:

Format: Numeric

The virtual path identifier of the ATM connection.

VCI Default: 0

Range:

Format: Numeric

The virtual channel identifier of the ATM connec-

tion. Must be zero for virtual path connections.

Statistics Panel

[Test Status] Default: Inactive

Range: N/A

Format: Predefined

alphanumeric

Displays the current status of the loopback test.

Active Indicates that the test is active.

Successful Indicates that the test is successful.

Failure Indicates that the test is a failure.

Timedout Indicates that the test has timed out.

Waiting-for-

response

Indicates that the test is waiting for a response.

[Cells Transmitted] Default: 0

Range: N/A

Format: numeric

Indicates the total number of loopback cells trans-

mitted on the specified connection since the last

reset.



255-700-447 11-23



OAM Activation and Deactivation

The OAM Activate and Deactivate option can perform continuity checks, as

well as forward performance monitoring, and backward reporting on user-

defined points along an ATM network.

[Cells Received] Default: 0

Range: N/A

Format: numeric

Indicates the number of loopback cells received cor-

rectly on the specified connection since the last

reset.

[Cells Mismatched] Default: 0

Range: N/A

Format: numeric

Indicates the number of times the cells received did

not matched with the cells transmitted on the speci-

fied connection since the last reset.

OAM Loopback

Action Type

Default: SendLoop-

back Once

Range: N/A

Format: predefined

alphanumeric

Indicates how to perform the loopback test function

selected in the OAM Loopback Type field.

SendLoopback

Once

Sends a loopback cell.

StopTest Stops the loopback test.

ResetStats Resets all values in the Statistics panel to zero.

OAM Loopback

Type

Default: End-to-end

Range: N/A

Format: predefined

alphanumeric

Indicates the method of loopback testing performed

for this PSAX device.

End-to-end Sends an end-to-end cell and determines the value

of the Destination Loopback Location ID field in the

cell.

Segment-endpoint Sends a segment loopback cell and determines the

value of the Destination Loopback Location ID field

in the cell.

Next-connection-

point

Sends a segment OAM cell within the designated

physical segments, for example, two PSAX chassis,

to check the connectivity between the segment con-

nection point from where the cell was issued to the

next immediate connection point.

Specific-location Sends a segment OAM cell to test the connectivity

within segments to the specific location ID of a spe-

cific chassis.

Destination Loop-

back Location ID

Default: N/A

Range: N/A

Format: Valid-dotted

quad

The destination loopback location ID where the

loopback must occur. This field is displayed only

when Specific-Location is selected in the OAM

Loopback Type field.

Table 11-13. Field Descriptions for the OAM Loopback Window (Continued)





11-24 255-700-447


To enable OAM Activation-Deactivation, perform the following procedure.

Begin


option.


2 On the Diagnostics Menu window, select the OAM Activate and Deacti-

vate option.

The OAM Activate & Deactivate Table is displayed (see Figure 11-11).

3 On the OAM Activate & Deactivate Table, select the OAM Activate

option.

The OAM ACTIVATION-DEACTIVATION window is displayed (see

Figure 11-12).



5 To begin the test, select the Activate command.

6 To terminate the test, select the Deactivate command.

En


Figure 11-11. OAM Activate & Deactivate Table Window



255-700-447 11-25




Table 11-14. Commands for the OAM Activate & Deactivate Table Window

Command Function





Total: 0/0 The first number in this field indicates the number of

the connection table entry on the first line of the cur-

rently displayed window. The second number indicates

the total number of connection table entries for this

connection type.

Find . . . To find a particular connection, enter values in the Slot,

Port, Channel, VPI, and VCI fields. If the connection

exists, it displays on the first line of the table.

OAM Activate Displays the OAM Activation-Deactivation window.

Go Back to Diagnostics Menu Redisplays the Diagnostics Menu window.

Figure 11-12. OAM Activation –Deactivation Window

Table 11-15. Commands for the OAM Activate & Deactivate Table Window

Command Function

Update Status Updates the information in the Current Status panel.

Activate Starts the OAM test.




11-26 255-700-447


Deactivate Terminates the OAM test.

Go Back to Table Screen Redisplays the OAM Activate and Deactivate Table window.

Table 11-15. Commands for the OAM Activate & Deactivate Table Window (Continued)

Command Function

Table 11-16. Field Descriptions for the OAM Activation-Deactivation Window


Connection Interface Panel

Slot Default: 0

Range: Chassis

dependent

Format: Numeric

Specifies the module slot number of the ATM

connection.

Port Default: 0

Range: Chassis

dependent

Format: Numeric

Specifies the port number of the ATM connec-

tion.

Channel Default: 0

Range: Chassis

dependent

Format: Numeric

The channel number of the ATM connection.

VPI Default: 0

Range: 0–4095

Format: Numeric

Specifies the virtual path identifier of the ATM

connection.

VCI Default: 0

Range: 0–65535

Format: Numeric

Specifies the virtual channel identifier of the

ATM connection.

OAM Function

Type

Default: Continuity-

check

Range: N/A

Format: Predefined

alphanumeric

Specifies the type of method for performing the

OAM function.

Continuity-check Indicates that the OAM cells flow continuously

throughout the length of a single connection is

performed.

Pmbr-and-cc Indicates that forward performance monitor-

ing/backward reporting and continuity checking

is performed.

Pm-and-cc Indicates that forward performance monitoring

and continuity checking is performed.

Fpm-and-br Indicates that forward performance monitor-

ing/backward reporting is performed.

Fpm only Indicates that only forward performance moni-

toring is performed.



255-700-447 11-27



Direction of Flow Default: Towards-

near-end

Range: N/A


Specifies in which direction the OAM cells are

transmitted.

Towards-near-end Indicates that OAM cells are transmitted only

towards the near end of the connection.

Both-way Indicates that OAM cells are transmitted in both

directions.

Towards-far-end Indicates that OAM cells are transmitted only

towards the far end of the connection.

Flow Type Default: End-to-end

Range: N/A

Format: Predefined

alphanumeric

Specifies the distance over which the OAM cells

flow in this connection.

End-to-end Indicates that the OAM cells flow from one end

of the connection to the other.

Segment Indicates that the OAM cells flow across only one

segment of the connection.

Block Size A-B Default: 1024

Range: N/A

Format: Predefined

alphanumeric

Specifies the size of the block of OAM cells taken

into consideration for performance monitoring in

the A to B direction (from near end to far end of

the connection). This field is displayed only when

the selected value in the OAM Function Type

field is a value other than Continuity-check, or

the value Towards-far-end or Both-way is

selected in the Direction of Flow field.

Size128 Indicates that the block size is 128 cells.



Size1024 Indicates that the block size is 1,024 cells.





Table 11-16. Field Descriptions for the OAM Activation-Deactivation Window (Continued)





11-28 255-700-447


Block Size B-A Default: 1024

Range: N/A

Format: Predefined

alphanumeric

Specifies the size of the block of OAM cells taken

into consideration for performance monitoring in

the B to A direction (from far end to near end of

the connection). This field is displayed only whenthe selected value in the OAM Function Type

field is a value other than Continuity-check, or

the value Towards-near-end or Both-way is

selected in the Direction of Flow field.









Current Status Panel

[Src Point ETE CC] Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Source point end-to-end continuity checking.

Displays the current status of the request for con-

tinuity checking of OAM cells from the source

point end of the connection to the sink point end.

Deactivated Indicates that continuity checking is deactivated.

Activated Indicates that continuity checking is activated.

WaitActConfirm Indicates that continuity checking will be acti-

vated pending confirmation of .

WaitDeactConfirm Indicates that continuity checking will be deacti-


[Snk Point ETE CC] Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Specifies how activation or deactivation of sink

point end-to-end continuity checking is per-

formed. Displays the current status of the request

for continuity checking of OAM cells from the

sink point end of the connection to the source

point end.

Deactivated Indicates that continuity checking is deactivated.

Activated Indicates that continuity checking is activated.

WaitActConfirm Indicates that continuity checking will be acti-vated pending confirmation of .

WaitDeactConfirm Indicates that continuity checking will be deacti-






255-700-447 11-29



[Src Point ETE PM] Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Specifies whether source point end-to-end per-

formance monitoring is active or not. The current

status of the request for performance monitoring

of OAM cells from the source point end of theconnection to the sink point end is displayed.

Deactivated Indicates that source point end-to-end perfor-

mance monitoring is deactivated.

Activated Indicates that source point end-to-end perfor-

mance monitoring is activated.

[Snk Point ETE PM] Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Specifies whether sink point end-to-end perfor-

mance monitoring is active or not. The current

status of the request for performance monitoring

of OAM cells from the sink point end of the con-

nection to the source point end is displayed.

Deactivated Indicates that sink point end-to-end performance

monitoring is deactivated.

Activated Indicates that sink point end-to-end performance

monitoring is activated.

[Srce Point ETE

PMBR]

Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Specifies whether source point end-to-end per-

formance monitoring/backward reporting is

active or not. The current status of the perfor-

mance monitoring/backward reporting activa-

tion/deactivation request at the source point is

displayed.

Deactivated Indicates that source point end-to-end perfor-

mance monitoring/backward reporting is deacti-

vated.Activated Indicates that source point end-to-end perfor-

mance monitoring/backward reporting is acti-

vated.

[Snk Point ETE

PMBR]


Range: N/A

Format: Predefined

alphanumeric

Specifies whether sink point end-to-end perfor-

mance monitoring/backward reporting is active

or not. The current status of the performance

monitoring/backward reporting activation/deac-

tivation request at the sink point is displayed.

Deactivated Indicates that sink point end-to-end performance

monitoring/backward reporting is deactivated.

Activated Indicates that sink point end-to-end performance

monitoring/backward reporting is activated.






11-30 255-700-447


[Src Point SEG CC] Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Specifies whether source point segment continu-

ity checking is active or not. The current status of

the source point’s segment continuity check acti-

vation/deactivation request is displayed.

Deactivated Indicates that source point segment continuity

checking is deactivated.

Activated Indicates that source point segment continuity

checking is activated.

[Snk Point SEG CC] Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Specifies whether sink point segment continuity

checking is active or not. The current status of the

sink point’s segment continuity check activa-

tion/deactivation request is displayed.

Deactivated Indicates that sink point segment continuity

checking is deactivated.

Activated Indicates that sink point segment continuity

checking is activated.

[Src Point SEG PM] Default: Deactivated

Range: N/A

Format: Predefined

alphanumeric

Specifies whether source point segment perfor-

mance monitoring is active or not. The current

status of the source point’s segment performance

monitoring activation/deactivation request is dis-

played.

Deactivated Indicates that source point segment performance


Activated Indicates that source point segment performance


[Snk Point SEGPM]


Range: N/A

Format: Predefined

alphanumeric

Specifies whether sink point segment perfor-mance monitoring is active or not. The current

status of the sink point’s segment performance

monitoring activation/deactivation request is dis-

played.

Deactivated Indicates that sink point segment performance


Activated Indicates that sink point segment performance


[Src Point SEG

PMBR]


Range: N/A


Specifies whether source point segment perfor-


or not. The current status of the source point’s

segment forward performance monitoring/back-

ward reporting for an activation/deactivation

request is displayed.

Deactivated Indicates that source point segment performance


Activated Indicates that source point segment performance






255-700-447 11-31



[Snk Point SEG

PMBR]


Range: N/A

Format: Predefined

alphanumeric

Specifies whether sink point segment perfor-


or not. The current status of the sink point’s seg-

ment forward performance monitoring/backwardreporting for an activation/deactivation request is

displayed.

Deactivated Indicates thatsink point segment performance


Activated Indicates thatsink point segment performance


[Result Last Req] Default: None

Range: N/A

Format: Predefined

alphanumeric

Displays the reason for failure of the last activa-

tion request on this connection from the local

user.

None Indicates that no failure occurred or no reason forfailure exists.

Denied Indicates that the OAM activation request is

denied.

Timedout Indicates that the OAM activation request has

been timed out.

Successful Indicates that the OAM activation request is suc-

cessful.

[BR Block Error] Default: 0

Range: 0–32768

Format: Numeric

Displays the backward reporting of a block error

on a performance monitoring connection.

[BR lost insertedcells]

Default: 0

Range: 0–32768

Format: Numeric

Displays the backward reporting of a lost insertedcell on a performance monitoring connection.

[BR missed inserted

cells]

Default: 0

Range: 0–32768

Format: Numeric

Displays the backward reporting of a misinserted

cell on a performance monitoring connection.






11-32 255-700-447





255-700-447 12-1

12 Backing Up and RestoringPSAX System Files


This chapter describes how to back up and restore PSAX system database

configuration files as follows:

• Backing up PSAX system, module, and connection database configuration

files by using the following methods:

~ Backing up files by using the console interface

~ Backing up files using FTP

~ Backing up files using XModem/YModem file transfer

• Restoring PSAX system, module, and connection database configuration

files by using the following methods:~ Restoring files by using the console interface

~ Restoring files using FTP

~ Restoring files using XModem/YModem file transfer

For an explanation of the difference of these methods, see “Choosing the

Configuration Files Transfer Method” on page 12-2.

Database Configuration Save and Restore Feature

The Database Configuration Save and Restore feature enables you to back up

and restore the PSAX system database files to, and from, a remote host com-

puter, such as a Unix or Windows-based workstation. The remote host com-

puter must be running as an FTP server. Files are backed up using FTP from

the CPUn module system disk to a user-defined directory on a remote host

computer. When needed, you can restore the backed up files using FTP to the

CPUn module. The restored files are placed in a temporary location on the

CPUn module and are then checked for errors using a sanity checking proce-

dure. If no errors are found, the PSAX system moves the files from the tem-

porary location to the established current directory on the CPUn module.

This setup includes creating a directory on the remote host computer where

the backup configuration files will be stored, a login name, and a password.

You should plan on setting aside 40 MB of disk space on the remote host

computer system disk. The actual amount of space the backup files will use

depends on the size of their PSAX system configuration files.

After initially storing their PSAX system configuration files onto a remote

host computer, you can back up your files as often as you like. In the event of

hardware or software problems on the PSAX system CPUn module, you can

restore your backup files from the host computer to the PSAX system CPUn

module system disk by using the Remote Data Operation window.



Chapter 12 Backing Up and Restoring PSAX System FilesChoosing the Configuration Files Transfer Method

12-2 255-700-447


Choosing the Configuration Files Transfer Method

Backing up and restoring your database configuration files involves selecting

one of the methods listed in Table 12-1 for copying these files between the

CPUn module system disk and the computer workstation (a remote storage

medium) on which you will store the backup database configuration files.

Lucent recommends that you use either the console interface or the FTP

method for copying files; however, if you have only the XModem or

YModem file transfer method available, you should consider which of thethree XModem or YModem protocols in the following list to use. Of these

three protocols, Lucent recommends you use either the YModem-G or the

YModem protocol per the following considerations:

• The YModem-G protocol allows the fastest transmission of the three types;

however, this protocol does not acknowledge receipt of packets. You can

receive all files grouped under a subdirectory at one time.

Table 12-1. Tasks for Copying Database Configuration Files Between the PSAX System and aRemote Storage Medium

If you are using the... you need to...

console interface (Remote

Database Operation win-

dow) to back up your con-

figuration files

copy the database configuration files from your PSAX system

to a remote storage medium using the procedure in “Backing

Up Database Files Using the Console Interface” on page 12-3.*

FTP method to back up

your configuration files



Up Database Files Using FTP” on page 12-7.

XModem or YModem file

transfer method to back

up your configuration files



Up Database Files Using XModem/YModem Transfer” on

page 12-9.

console interface (Remote

Database Operation win-

dow) to restore your con-

figuration files

copy the database configuration files to your PSAX system

from a remote storage medium using the procedure in

“Restoring Database Files Using the Console Interface” on

page 12-15.*

FTP method to restore

your configuration files


from a remote storage medium using the procedure in

“Restoring Database Files Using FTP” on page 12-16.


transfer method to restoreyour configuration files


from a remote storage medium using the procedure in“Restoring Database Files Using XModem/YModem File Trans-

fer” on page 12-17.

* Using the console interface is the recommended method for users running PSAX system

Release 7.1.1 or subsequent. If you are running Release 7.1.0 or earlier, you must use the FTP

or the XModem/YModem file transfer method. Of the latter two methods, the FTP method is

much preferred because the X/Modem/YModem method is quite slow and labor intensive.



255-700-447 12-3


Chapter 12 Backing Up and Restoring PSAX System FilesBacking Up System Database Files

• The YModem protocol is a slower method of transmission, but is more reli-

able because it acknowledges receipt of packets. You can receive all files

grouped under a subdirectory at one time.

• The XModem protocol is a laborious method of transmission because you

must enter the filename of each file in the complete package of software

upgrade files to perform the upgrade task. Use of the XModem protocol is

discouraged but use it only if this protocol is the only option available to

you.

Note: Transferring the database configuration files using the YModem

protocol could take several hours hours. Using the XModem proto-

col takes longer than the YModem protocol.

Backing Up System Database Files

To backup the database configuration files, select a method from Table 12-1.

Note: You cannot back up files using the Telnet function.

Backing Up Database Files Using the Console Interface

! CAUTION:After initially configuring your PSAX system, after every configurationmodification, and prior to PSAX system software upgrades, be sure toback up the configuration files to a remote storage medium.

It is recommended that you periodically back up your PSAX system configu-

ration database files, which reside on the system disk of the CPUn module to

a remote storage medium located on a computer workstation or PC.

To back up your PSAX system database files to a remote storage medium per-

form the steps in the following procedure, which uses the Remote Database

Operation window on the PSAX console interface. Using this procedure auto-

matically backs up all the configuration database files on your PSAX system.

Begin

1 Determine which computer workstation you will use to store your

backup PSAX system database files, and set up a specific directory for

these files.

2 Ensure that a standard 10Base-T Ethernet cable is connected between

the Ethernet port on the primary CPUn module in the PSAX system andthe network, and that you have a stable connection between the net-

work management workstation and the CPUn module.

3 Log onto the PSAX system console.

4 On the Console Interface Main Menu window, select the Remote Data-

base Operation option.

The Remote Database Operation window is displayed (see Figure 12-1).




12-4 255-700-447


5 Select RemoteSave in the Operation field, and enter values in the other


Table 12-3. The commands for this window are described in Table 12-2.

The PSAX system saves the configuration files to your designated remote

storage medium.

End

Figure 12-1. Remote Database Operation Window

Table 12-2. Commands for the Remote Database Operation Window

Command Function

Apply remote database operation Starts the function you selected in the Operation field.




255-700-447 12-5



Table 12-3. Field Descriptions for the Remote Database Operation Window


Remote Host IP

Addr

Default: 000.000.000.

000

Range: 000–255

Format: Numeric

Specifies the IP address of the remote host com-

puter, for example, a Unix or Windows-based

workstation. The remote host computer must be

running as an FTP server.

Login Default: N/A

Range: 1–20

Format: Alphanu-

meric

Specifies the user-defined login name for the

remote host computer.

Password Default: N/A

Range: 1–20

Format: Alphanu-

meric

Specifies the user-defined password for the

remote host computer.

Directory Default: N/A

Range: 1–79

Format: Alphanu-

meric

Specifies the user-defined directory path on the

remote host computer where you will store the

PSAX system backup database files. Plan on set-

ting aside 40 MB of disk space on the remote host

computer system disk.

Operation Default: NoOpera-

tion

Range: N/A

Format: Predefined

alphanumeric

Specifies the function you want to perform on

the PSAX system database files.

NoOperation Aborts the file transfer operation. This value is

not currently supported.

RemoteSave Performs a backup of the database files by trans-

ferring them from the CPU module to the user-defined directory you specified on the remote

host computer. When performing future backups,

the PSAX system overwrites the existing files in

the directory you specified the last time you per-

formed a backup.

RemoteLoad Performs the restore function by transferring the

database files from the user-defined directory on

the remote host computer to the CPU module.

Note: After this operation is completed success-

fully (DoneSuccessfully is displayed in the Oper

Status field), the PSAX system immediately

reboots.




12-6 255-700-447


[Oper Status] Default: NoActivity

Range: N/A

Format: Predefined

alphanumeric

Displays the operational status indicating what

activity is currently taking place.

NoActivity Indicates that no operation is currently being

done.

Working Indicates that the PSAX system is currently trans-

ferring files from one location to another.

DoneSuccessfully Indicates that the file transfer operation was com-

pleted successfully.

DoneWithError Indicates that the file transfer operation was

attempted, but an error occurred.

Aborted Indicates that the file transfer operation was

aborted. This status is not currently supported.

[Error Status] Default: None

Range: N/A

Format: Predefined

alphanumeric

Displays the error status indicating whether an

error has occurred during processing.

None Indicates that no error condition was detected.

UnableToMakeFtp-

Connection

Indicates that the PSAX system was not able to

connect with the remote host computer.

InvalidDirectory Indicates that the directory name you entered

does not match any directory on the remote host

computer.

UnableToOpenDa-

tabaseFile

Indicates that during the remote load (restore)

operation, the PSAX system was unable to open

one or more database files on the CPU module.

UnableToCom-

pleteFtp

Indicates that during the file transfer operation,

an error occurred that interrupted this operation.

DatabaseSanityFail Indicates that during the remote load (restore)

operation while sanity checking was being per-

formed on the restored files in the temporary

directory on the CPU module, the PSAX system

found errors in these files.

UnableToUpdate-

Backup

Indicates that during the remote load (restore)

operation, the PSAX system was not able to

transfer the database files from the temporarydirectory to the established current directory on

the CPU module.

Table 12-3. Field Descriptions for the Remote Database Operation Window (Continued)




255-700-447 12-7



Backing Up Database Files Using FTP

To back up your PSAX system database files to a remote storage medium,

perform the steps in the following procedure, which is a manual method in

which you copy each configuration database file in sequence to the storage

medium.

Begin

1 Determine which network management workstation (computer) you

will use to store your backup PSAX system database files, and set up a

specific directory for these files on that computer.


the Ethernet port on the primary CPUn module in the PSAX system and

the network, and that you have a stable connection between the net-

work management workstation and the CPUn module.

3 On the workstation, at the DOS prompt, enter:

ftp -n nnn.nnn.nnn.nnn

where

nnn.nnn.nnn.nnn is the IP address of the CPUn module in the PSAX

system.

4 At the prompt ftp, enter the following command:

user readwrite currentpassword

where

readwrite is the PSAX-defined or the RADIUS server-defined username,

and currentpassword is the PSAX-defined or the RADIUS server-defined-

password.

5 To specify the correct path for the location of the configuration databasefiles you are backing up from the PSAX system, enter the following com-

mand:

cd \scsi\current (Windows) or cd /scsi/current (UNIX)

6 To provide a visual indicator during the backup process, enter:

hash

7 To transfer (copy) the configuration files, enter the following commands

in sequence:

bin

get filename

where

filename is the one of the configuration files on your PSAX system (see

Table 12-4).

Note: When you are entering get commands for each individual con-

figuration file listed in Table 12-4, an error message might be dis-

played stating that the particular file does not exist. In this situa-




12-8 255-700-447


tion, the error message is displayed because you are not using a

particular feature that would have created that file on your sys-

tem.

8 To exit the FTP session, enter:

bye

End

PSAX System Database Files

The files containing the PSAX system configuration data, which is located in

the scsi/current/ directory on the CPUn module system disk, are listed in

Table 12-4. Depending on which PSAX system features you have configured,

you might not have all the files listed in Table 12-4 because you are not using

the associated feature. Therefore, if you are backing up or restoring the files

listed in Table 12-4 using the FTP of the XModem/YModem file transfer

method and you get an error message that a particular file cannot be found,

the reason is that it does not exist.Table 12-4. PSAX System Configuration Files

PSAX Database orDefinition Filename

Description

console.def Password definitions file

ssid.def Site-specific identification definitions file

eventmgr.cfg Event management configurations file

atmvuni.db ATM virtual UNI configuration database file

atmtrnk.db ATM trunking configuration database file

cnctn.db Connection configuration database file

ecd.db Module configuration database file

erm.db Enhanced Router module configuration file

features.db Features enabled/disabled database

fwc.def Firmware configuration database

gr303.db GR-303 configuration database

h248.db H.248 configuration database

iisp.cbr IISP CBR routing table (always exists even if you have

no SVCs configured)

iisp.vbr IISP VBR routing table (always exists even if you have

no SVCs configured)

intfprot.db Interface protection configuration database

iproute.db IP routing configuration database

iua.db ISDN User Adaptation configuration database

oam.db OAM configuration database

pnnimib.db PNNI configuration database

/scsi/announce/*.* Announcement files



255-700-447 12-9



Backing Up Database Files Using XModem/YModem Transfer

You can use the XModem/YModem file transfer method to copy the Multi-

service Media Gateway system databases from the CPUn module system disk

to a separate storage medium. Backing up the databases using the

XModem/YModem file transfer option includes two major tasks:

• First, you set up the cabling and connections between the computer work-

station and the PSAX system CPUn module, start up the VT100 terminal

emulation software on the PC workstation, and ensure you have commu-

nication between the two devices (see the following procedure, “Setting Up

for the File Transfer Process”).

• Second, you perform the file transfer (copy) process for the databases to a

separate storage medium (see the procedure, “Copying the Database Files

to a Remote Storage Medium”).

Setting Up for theFile Transfer Process

Perform the following procedure to set up for a file transfer.

Begin

1 Set up the cabling and connections between the computer workstation,

the local modem, and the telephone line. For more information, see

“Upgrading Using the XModem/YModem File Transfer Method” on

page 13-15.

2 Set up the cabling and connections between the PSAX system CPUn

module, the remote modem, and the telephone line. For more informa-

tion, see “Upgrading Using the XModem/YModem File Transfer Method”on page 13-15.

3 On the computer workstation on which you want to store your backup

database configuration files, start the VT100 terminal emulation soft-

ware, and set up the configuration preferences (see Chapter 4).

spclconn.db Special connections configuration database (signaling

connections)

spvc.db SPVC configuration database

spvcaal2.db Standard AAL2 SPVC configuration database

tasm.db Tones and announcements configuration database

trap.db SNMP trap activation database

v5.db V5.2 configuration database

vi.db Virtual interface configuration database

vipr.db VIPR task configuration database

Table 12-4. PSAX System Configuration Files (Continued)

PSAX Database orDefinition Filename

Description




12-10 255-700-447


4 Using the terminal emulator modem communication function, return

the telephone number of the line connected to the modem connected to

the PSAX system.

End

Copying theDatabase Files to aRemote StorageMedium

Perform the following procedure to copy the database files to a remote stor-age medium.

Begin

1 Using the terminal emulator, log onto the PSAX system.

2 On the Console Interface Main Menu window, select the Software Ver-

sion Configuration option.

The Software Version Configuration window (see Figure 12-2) is dis-

played.

3 On the Software Version Configuration window, select the

XMODEM/YMODEM File Transfer option.

The XMODEM/YMODEM File Transfer window (see Figure 12-3) is dis-played.

Note: For the database file transfer process, use only the Send Options

panel on the XMODEM/YMODEM File Transfer window.


provided in Table 12-6. The commands on this window are described in

Table 12-5.

Figure 12-2. Software Version Configuration window (XMODEM/YMODEM FileTransfer Selected)



255-700-447 12-11



5 Select the Send Files command on the XMODEM/YMODEM File Trans-

fer window.

The terminal emulator displaying the PSAX system interface window

scrolls the XMODEM/YMODEM File Transfer window out of view. A

message is displayed indicating that you can cancel the transfer by press-

ing Ctrl+X several times. A second message is displayed indicating thatyou must start the terminal emulator receive function.

6 Using the terminal emulator receive function, select one of the two pro-

tocol types: YModem, YModem-G, or XModem. Be sure to select the

same protocol as the one you selected on the PSAX system

XMODEM/YMODEM File Transfer window.

7 In the terminal emulator field for the location of the file, specify the drive

and the directory pathname on the computer workstation system disk

where you want to transfer (copy) the database files.

For example, specify a pathname like the following:

x :/directory/ filename where x is the drive letter for the computer worksta-

tion system disk and directory is a name that you choose.Be sure you enter the filename of the database file exactly so that it

matches the name you previously entered on the Multiservice Media

Gateway system XMODEM/YMODEM File Transfer window. For a list of

all PSAX system configuration file, see Table 12-4.

8 Select the OK or Receive command in the terminal emulator receive

function dialog box.

9 Repeat steps 4–8 to specify another database filename until you have

transferred all the database files to the computer workstation system

disk.

10 Go to the section, “Rebooting the PSAX System” on page 12-20

End




12-12 255-700-447


Figure 12-3. XMODEM/YMODEM File Transfer Window (Send Options PanelSelected)

Table 12-5. Commands for the XMODEM/YMODEM File Transfer Window

Command Function

Send File Initiates the send function of the file transfer process from

the CPUn module system disk to a storage medium (such

as a Unix or PC workstation system disk).

Receive File Initiates the receiving function of the file transfer process

to the CPUn module system disk from the CD-ROM con-

taining the software upgrade files (running in a CD-ROM

drive in a Unix or PC workstation).

Reset Display to System Defaults Redisplays the default values in the fields.

Go Back to Version Configuration Redisplays the Software Version Configuration window.

Table 12-6. Field Descriptions for the XMODEM/YMODEM File Transfer Window


Note: To upgrade your PSAX system software or restore your database configuration files, use

only the fields on the Receive Options panel. To back up your PSAX system configuration

(database) files, use only the fields on the Send Options panel.



255-700-447 12-13



Receive Options Panel

Protocol Default: YModem

Range: N/A

Format: Predefined

alphanumeric

Specifies the type of modem protocol used for

receiving data.

YModem Indicates that the YModem protocol is to be used

for receiving the software upgrade files.

YModem-G Indicates that the YModem-G protocol is to be

used for receiving the software upgrade files.

XModem Indicates that the XModem protocol is to be used


File Type Default: Binary

Range: N/A

Format: Predefined

alphanumeric

Specifies the format of the file that will be trans-

mitted.

Binary Indicates that the binary format is to be used. Use

this format to download software upgrade files.

Text Indicates that the ASCII text format is to be used.

Use this format only when you are backing up

PSAX system configuration (database) files to

your computer workstation. Do not use it for

software upgrade files.

Error Check Default: CRC-16

Range: N/A

Format: Predefined

alphanumeric

Specifies the type of error checking performed on

the data received. This field is displayed only

when the value XModem is selected in the Pro-

tocol field.

CRC-16 Indicates that the error checking method is cycli-

cal redundant checking, 16 bits.

Checksum Indicates that the error checking method is arith-

metic summation checking, 8 bits.

Directory Default: /scsi/next/

Range: N/A

Format: /scsi/next/ directoryname/

Specifies the subdirectory on the CPUn module

system disk where the software upgrade files are

received (stored). For each subdirectory con-

tained in the package of software upgrade files,

you must enter the subdirectory name in this

field, and then receive this directory on the CPUn

module system disk.

Note: All subdirectory and file names are listed in

the readme.txt file accompanying the software

upgrade files on the CD-ROM.

Table 12-6. Field Descriptions for the XMODEM/YMODEM File Transfer Window (Continued)





12-14 255-700-447


Filename Default: N/A

Range: N/A

Format: alphanu-

meric

Specifies the filename on the CPUn module sys-

tem disk where the software upgrade files are

received (stored). For each file contained in the

package of software upgrade files, enter the file-name in this field, and then receive this file on

the CPUn module system disk. This field is dis-

played only when the value XModem is selected

in the Protocol field.




Send Options Panel


Range: N/A

Format: Predefined

alphanumeric


sending data.


for sending the PSAX system files to the com-

puter workstation where you will store your

PSAX system backup.


used for sending the PSAX system files to the

computer workstation where you will store your

PSAX system backup.




PSAX system backup.


Range: N/A

Format: Predefined

alphanumeric


mitted.












255-700-447 12-15


Chapter 12 Backing Up and Restoring PSAX System FilesRestoring System Database Files

Restoring System Database Files

If your system, module, or connection configuration database files become

corrupted or otherwise unusable, you must restore them from your remote

storage medium to the CPUn module system disk. To restore the database

configuration files, select a method from Table 12-1.

Note: In an PSAX system with redundant CPUn modules, you must

restore the database files to both modules, either simultaneously orsequentially, depending on your physical setup. See “Restoring

Backup Files to the Standby CPUn Module” on page 12-19.

Restoring Database Files Using the Console Interface

To restore up your PSAX system database files from a remote storage

medium, perform the steps in the following procedure, which uses the

Remote Database Operation window on the PSAX console interface. Using

this procedure automatically restores all the configuration database files to

your PSAX system.

Begin


the Ethernet port on the primary CPUn module in the PSAX system and

the network, and that you have a stable connection between the com-

puter workstation on which your backup configuration files are stored

and the CPUn module.

2 Log onto the PSAX system console.

Packet Size Default: 1024

Range: N/A

Format: Predefined

numeric (bytes)

Specifies the size (in bytes) of the packet that will

be transmitted in the data stream.

1024 Indicates that the packet contains 1024 bytes.


Directory Default: /scsi/cur-

rent/

Range: N/A


Specifies the directory on the CPUn module sys-

tem disk where the PSAX system configuration

(database) files are stored. This directory contains

the files that you want to back up on your com-

puter workstation.


Range: N/A

Format: alphanu-

meric

Specifies the filename of the PSAX system config-

uration (database) file you want to back up on

your computer workstation.






12-16 255-700-447


3 On the Console Interface Main Menu window, select the Remote Data-

base Operation option.

The Remote Database Operation window is displayed (see Figure 12-1).

4 Select RemoteLoad in the Operation field, and enter values in the other


Table 12-3. The commands for this window are described in Table 12-2.

The PSAX system restores your configuration files to the primary CPUn

module.

5 Go to “Rebooting the PSAX System” on page 12-20

End

Restoring Database Files Using FTP

To restore database files from a remote storage medium using FTP, perform


Begin

Steps to Restore Database Files Using FTP

1 In a nonredundant PSAX system, connect a standard 10Base-T Ethernet

cable to the Ethernet port on the CPUn module. In a redundant PSAX

system, connect cables to both the primary and the standby CPUn mod-

ules. Ensure that you have a stable connection from the source PC or

network management workstation to the CPUn module.

2 Use the DOS drive and change directory commands to access the drive

and directory on the computer where you have stored the databases.

3 At the DOS prompt, enter:

ftp -n xxx.xxx.xxx.xxx

where

xxx.xxx.xxx.xxx is the IP address of the CPUn module.

4 At the prompt ftp, enter:

user readwrite currentpassword

where

readwrite is the PSAX-defined or the RADIUS server-defined username,

and currentpassword is the PSAX-defined or the RADIUS server-defined-

password.

5 To be sure you have the correct path selected, enter one of the following:

• cd \scsi\current (Windows) or cd /scsi/current (UNIX)

6 To provide a visual indicator during the restore files process, enter

hash

7 To transfer (copy) the configuration files, enter the following commands

in sequence:



255-700-447 12-17



Note: When you are entering put commands for each individual con-

figuration file listed in Table 12-4, an error message might be dis-

played stating that the particular file does not exist. In this situa-

tion, the error message would be displayed because you are not

using a particular feature that would have created that file on

your system.

bin

put filename

where

filename is the one of the following configuration files on your PSAX sys-

tem (see Table 12-4).

8 To exit the FTP session, enter:

bye

9 Go to “Rebooting the PSAX System” on page 12-20.

End

Restoring Database Files Using XModem/YModem File Transfer

You can use the XModem/YModem file transfer option to restore the PSAX

system databases from a remote storage medium to the CPUn module system

disk. Restoring the databases using the XModem/YModem file transfer

method involves transferring files from the PC workstation to the PSAX sys-

tem. This procedure includes two major tasks:

• First, set up the cabling and connections between the PC workstation and

the PSAX system CPUn module, start up the VT100 terminal emulation

software on the PC workstation, and ensure you have communication

between the two devices (see “Setting Up for the File Transfer Process”).

• Second, you perform the file transfer (copy) process for the backup data-

base files to the PSAX system (see “Copying the Backup Files to the PSAX

System”).

Note: In an PSAX system with redundant CPUn modules, you must

restore the database files to both modules.

Setting Up for theFile Transfer Process

Begin

1 Set up the cabling and connections between the PC workstation, the

local modem, and the telephone line. For more information, see

“Upgrading Using the XModem/YModem File Transfer Method” on

page 13-15.

2 Set up the cabling and connections between the PSAX system CPUn

module, the remote modem, and the telephone line. For more informa-

tion, see “Upgrading Using the XModem/YModem File Transfer Method”

on page 13-15




12-18 255-700-447


3 If you have a redundant modem kit, connect cables from the switching

modem to the CONSOLE ports on both CPUn modules, and set up the

switching modem to establish a connection with the primary CPUn mod-

ule.

4 On the PC workstation, start up the VT100 terminal emulation software,

and set up the configuration preferences (see Chapter 4).5 Using the terminal emulator modem communication function, return

the telephone number of the line connected to the modem connected to

the PSAX system.

Copying the BackupFiles to the PSAXSystem Begin

1 Using the terminal emulator, log on the PSAX system.



The Software Version Configuration window is displayed.3 On the Software Version Configuration window, select the


The XMODEM/YMODEM File Transfer window (see Figure 12-4) is dis-

played.

Note: For restoring database files, use only the Receive Options panel.



Table 12-5.

5 Select the Receive File command on the XMODEM/YMODEM File

Transfer window.

The terminal emulator displaying the PSAX system window interface

scrolls the XMODEM/YMODEM File Transfer window out of view. A

message is displayed indicating that you can cancel the transfer by press-

ing Ctrl+X several times. A second message is displayed indicating that

you must start the terminal emulator send function.

6 Using the terminal emulator send function, select one of the three proto-

col types: YModem,YModem-G, XModem. Be sure to select the same

protocol as the one you selected on the PSAX system XMODEM/YMO-

DEM File Transfer window.


where the PSAX system backup database files reside and the directory

pathname.

For example, specify a pathname like one of the following:

~ x :/psaxbackup/*.* if you are using YModem or YModem-G

where x is the drive letter where the backup database files reside

~ x :/psaxbackup/ filename if you are using XModem

where x is the drive letter where the backup database files reside



255-700-447 12-19


Chapter 12 Backing Up and Restoring PSAX System FilesRestoring Backup Files to the Standby CPUn Module

Be sure you enter the directory name (or the directory and filename if

using XModem) exactly so that it matches the names you previously

entered on the PSAX system XMODEM/YMODEM File Transfer window.

8 Select the OK or Send command in the terminal emulator send function

dialog box.

9 Repeat steps 4 through 8 to specify another filename (for XModem) untilyou have transferred all the backup files to the CPUn module system

disk.

10 Go to “Rebooting the PSAX System” on page 12-20

End

Restoring Backup Files to the Standby CPUn Module

If you have a redundant CPUn module configuration, you must restore the

backup database files to the standby CPUn module. To restore the backup

database files to the standby CPUn module, perform the following procedure.

Begin

1 Connect the cable to the standby CPUn module as described in

Table 12-7:

Figure 12-4. XMODEM/YMODEM File Transfer Window (Receive Options PanelSelected)



Chapter 12 Backing Up and Restoring PSAX System FilesRebooting the PSAX System

12-20 255-700-447


2 Repeat the procedure for one of the three restoring methods in the sec-

tion,“Restoring System Database Files” on page 12-15.

End

Rebooting the PSAX SystemAfter you have copied your database configuration files from the computer

workstation on which you have your backup configuration stored, you must

reboot (reinitialize) the PSAX system chassis, so all components are synchro-

nized. To reboot the PSAX system, perform the steps in the following proce-

dure.

Begin

Steps to Reboot the PSAX System

1 Redisplay the Console Interface Main Menu window by pressing Ctrl+G

from any window.

2 On the Console Interface Main Menu window, select the Diagnosticsoption.


3 On the Diagnostics Menu window, select the Reboot Hardware Com-

ponents command.

The Remote Reboot Configuration window is displayed.

4 On the Remote Reboot Configuration window, select the Reboot

Chassis command.

This command reboots the primary and standby (redundant) CPUn mod-

ules, and all I/O and server modules in the PSAX system.

End

Table 12-7. Connecting a Cable to the Standby (Backup) CPU Module

If you are using... do the following:

a redundant modem kit set up the switching modem to

establish a connection with the

standby CPU2 module.

single modem kit connect a cable from the modem to

the CONSOLE port on the standby

CPU2 module.




255-700-447 13-1

13 Upgrading PSAX System Software


This chapter describes how to upgrade the PSAX system software and

firmware.

Before You Begin

Be sure to read the Release Note for Release 9.0.0 Controlled Introduction of the

PacketStar PSAX 4500, PSAX 2300, PSAX 1250, and PSAX 1000 Multiservice Media

Gateways before beginning the PSAX system software upgrade. If any opera-

tional considerations or constraints have been identified for upgrading to

Release 9.0.0, these issues are addressed in that document, and instructionsfor special configurations and workaround procedures will provide guidance

in upgrading your PSAX system(s).

Required Tasks

This chapter provides instructions for upgrading your PacketStar PSAX system

software for Release 9.0.0. The following topics are presented:

• “Saving Your Modified System Configuration” (if applicable)

• “Backing Up Your Current Database Files Prior to Upgrade”

• “Choosing the System Software File Transfer Method”

• “Upgrading Using the File Transfer Protocol Method”• “Module LED Indicators During Booting”

• “System Events During Booting”

• “Verifying Successful Downloading of Module Firmware Drivers”

• “Upgrading Using the XModem/YModem File Transfer Method”

• “Manually Selecting I/O and Server Module Firmware Drivers” (optional)

Saving Your Modified System Configuration

For instructions on saving your modified PSAX system configuration, see

“Saving the Equipment Configuration Values and Logging Off” on page 5-84.

Backing Up Your Current Database Files Prior to Upgrade

! CAUTION:After initially configuring your PSAX system, after every configurationmodification, and prior to PSAX system software upgrades, be sure toback up the configuration files to a remote storage medium.



Chapter 13 Upgrading PSAX System SoftwareChoosing the System Software File Transfer Method

13-2 255-700-447


It is recommended that you periodically back up your PSAX system configu-

ration database files, which reside on the system disk of the CPUn module to

a remote storage medium located on a computer workstation or PC.

To backup the database configuration files, select a method from Table 12-1.

Note: You cannot back up files using the Telnet function.

Choosing the System Software File Transfer Method

Installing a new release of the PSAX system software involves selecting one

of the methods listed in Table 13-1 for downloading the PSAX system soft-

ware upgrade files, which are provided on a CD-ROM.

Lucent recommends that you use the FTP method; however, if you have only

the XModem or YModem file transfer method available, you should consider

which of the three XModem or YModem protocols in the following list touse. Of these three protocols, Lucent recommends you use either the

YModem-G or the YModem protocol per the following considerations:

• The YModem-G protocol allows the fastest transmission of the three types;









discouraged but use it only if this protocol is the only option available toyou.

Note: Transferring the software upgrade files using the YModem protocol

takes approximately 24 hours. Using the XModem protocol takes

longer than the YModem protocol.

Table 13-1. Tasks for Transferring Files to Your PSAX System

If you are using the... you need to...

FTP method download the files from the CD-ROM on a host workstation to

the CPUn module (or CPUn component) system disk (see

“Upgrading Using the File Transfer Protocol Method” on

page 13-3).


transfer method

transfer the files from the CD-ROM on a remote host worksta-

tion to the CPUn module (or CPUn component) system disk

via a modem (see “Upgrading Using the XModem/YModem

File Transfer Method” on page 13-15).



255-700-447 13-3


Chapter 13 Upgrading PSAX System SoftwareUpgrading Using the File Transfer Protocol Method

! CAUTION:Upgrading the software on your PSAX system might affect some aspectsof its operation. See the Release Note for Release 9.0.0 of the PacketStarPSAX 4500, PSAX 2300, PSAX 1250, and PSAX 1000 Multiservice MediaGateways for more information.

Upgrading Using the File Transfer Protocol Method

Upgrading using the FTP method includes two major tasks:

1. Setting up a Windows FTP server (see “Setting Up a Windows FTP

Server”)

2. Downloading the software upgrade files to the PSAX system using FTP,

and upgrading the PSAX system on the CPUn module (see “Downloading

Software Files Using FTP” on page 13-3)

Setting Up a Windows FTP Server

If you are using a computer workstation running Windows NT or 2000, use

the FTP server function that is included in the operating system. If you are

using Microsoft Windows 95 or 98 to upgrade your PSAX system software,

you need to obtain an FTP server software program. For Windows 95 or 98,

obtain an FTP server software program, which is available from several Inter-

net web sites. If you plan to use a shareware program, you are responsible for

following the terms of the author’s licensing agreement, including payment.

To set up your FTP server software, perform the steps in the following proce-

dure.

Begin

1 If you are using Windows 95 or 98, obtain an FTP server software pro-

gram (freeware, shareware, or commercial). Note that Windows NT and

2000 already have FTP functionality included in the software.

2 Set up the FTP server software as follows:

a Create an account and password.

b Assign read-only, recursive access privileges to the pathname con-

taining the drive ID and directory where the CD-ROM drive resides.

En

Downloading Software Files Using FTP

To download the system software files to your PSAX system, perform the

steps in the following procedures.




13-4 255-700-447


Begin


the Software Version Configuration option.


played.

Figure 13-1. Console Interface Main Menu Window

Figure 13-2. Software Version Configuration Window



255-700-447 13-5



2 Select the FTP Software Release Distribution option.

The SRD Download Configuration window (see Figure 13-3) is dis-

played.

Commands The commands on the SRD Download Configuration window are

described in Table 13-2.

Field Descriptions 3 Enter values in the fields on this window according to the information


Figure 13-3. SRD Download Configuration Window

Table 13-2. Commands for the SRD Download Configuration Window

Command FunctionStart System Software FTP Process Begins the software release download via the FTP con-

nection.

Abort System Software FTP Process Stops the downloading of files. This command is dis-

played only after the download process has already

begun.

Update Display Refreshes the screen display. Occasionally, the screen

displays extraneous characters if an error occurs while

you are downloading the new system software. Use this

command to clean up the display.





13-6 255-700-447


Table 13-3. Field Descriptions for the SRD Download Configuration Window


IP Address Default: 000.000.000.000

Range: N/A

Format: numeric (valid dotted

quad)

Specifies the IP address of the computer

that contains the CD-ROM drive and is

running the FTP client.

Account Name Default: N/A

Range: N/A

Format: alphanumeric (up to 20

characters)

Specifies the account name you have

already set up in your FTP client software.

Account Pass-

word

Default: N/A

Range: N/A

Format: alphanumeric (up to 20

characters)

Specifies the account password you have

already set up in your FTP client software.

CD-Rom File Path Default: <Enter file path here>

Range: N/A

Format: alphanumeric

Specifies the path for the CD-ROM drive

where the new PSAX system software

resides. Type over the default value

<Enter file path here>.

x :\upgrade.lib Enter this command string if you are

upgrading from a PSAX system Release

6.0.0 or later using a Windows host

workstation.

Note: x = the CD-ROM drive letter

/cdrom/v0900c00/upgrade.lib Enter this command string if you are

upgrading from a PSAX system Release

6.0.0 or later using a Unix host worksta-

tion.

License Key Default: N/ARange: N/A

Format: N/A

Lucent software license. This field is notcurrently supported.



255-700-447 13-7



[Copy Status] Default: NoActivity

Range: N/A

Format: predefined alphanumeric

Displays the status of the file copying

during the FTP download.

NoActivity Displayed when no copying (download-

ing) is taking place.

Working Displayed when the system is copying

(downloading) files to the CPUn module.

DoneSuccessfully Displayed when all files are successfully

copied (downloaded).

DoneWithError Displayed when the system has finished

an unsuccessful attempt to download

files. The corresponding error status code

is displayed in the [Error Status] field.

[Error Status] Default: None

Range: N/A

Format: predefined alphanumeric

Indicates the result of the finished or

attempted software download. With theexception of the value None, all other

values are system-generated when the

system encounters an error condition. An

error message is also displayed in the sta-

tus line at the bottom of the window. For

descriptions of the error status code val-

ues, see the table below, “Error Status

Codes for the [Error Status] Field on the

SRD Download Configuration Window.”

Table 13-3. Field Descriptions for the SRD Download Configuration Window (Continued)


Table 13-4. Error Status Code Values for the [Error Status] Field on the SRD Download

Configuration Window

Field Value Description

CpuAbort Displayed when the FTP process was terminated due to internal

failure; for example, the CPUn module was performing an activity

that prevented or interrupted the FTP process. Wait several min-

utes and select the Start System Software FTP Process com-

mand again. If you receive this value a second time, wait for

another short period and try the command a third time. If you are

not successful, call Technical Support.*

FailureInCopyingDataFiles Displayed when the PSAX system files could not be copied; for

example, the PSAX software CD-ROM or the CPUn module disk

drive failed. Call Technical Support for assistance.*

FailureInCreatingMsgQ Displayed when an internal execution failed because a sofware

message queue could not be created. Call Technical Support for

assistance.*

FailureInSpawningTask Displayed when an internal execution failed because a software

task could not be created. Call Technical Support for assistance.*




13-8 255-700-447


FailureToRemoveNextTree Displayed when the directory containing an earlier software

release could not be removed, for example, the disk drive failed.

Call Technical Support for assistance.*

FileCRCFail Displayed when the cyclic redundancy checking on a downloaded

file failed. Call Technical Support for assistance.*

InvalidAccountName Displayed when the account name you entered in the Account

Name field does not match the one that you set up in the FTP

server software on the host workstation. Verify the account name,

re-enter the information, and select the Start System Software

FTP Process command again.

InvalidAccountPassword Displayed when the password you entered in the Account Pass-

word field does not match the one that you set up in the FTP

server software on the host workstation. Verify the account pass-

word, re-enter the information, and select the Start System

Software FTP Process command again.

InvalidCdromFile Displayed when the filename or the pathname for the PSAX sys-

tem software CD-ROM is not correct. Verify the filename or the

pathname or both, re-enter the information, and select the Start

System Software FTP Process command again.

InvalidIpAddress Displayed when the IP address you entered in the IP Address field

for the host workstation is not a valid address. Verify the IP

address, re-enter the information, and select the Start System

Software FTP Process command again.

LibraryCRCFail Displayed when the cyclic redundancy checking on a downloaded

library failed. Typically, in this error condition, the CRC on a

downloaded library file does not match the CRC given in the

package list file. Call Technical Support for assistance.*

None Displayed when the value DoneSuccessfully is displayed in the

[Copy Status] field. The PSAX system software download was suc-

cessful.

TaskSuspendOrDead Displayed when an internal execution failed because a software

task did not respond to a command. Call Technical Support for

assistance.*

UnableToCompleteFtp Displayed when an interruption in the connection between the

host workstation and the PSAX system occurs. Determine what

caused the interruption, correct the problem, and try the down-

load again by selecting the Start System Software FTP Process

command.UnableToFindTaskSymbol-

Name

Displayed when the internal software failed because the FTP pro-

cess could not locate a specific symbol in the new software being

downloaded. Call Technical Support for assistance.*

UnableToLoadLibraryMod-

ule

Displayed when the internal software failed because the FTP pro-

cess could not load a specific software library. Call Technical Sup-

port for assistance.*

Table 13-4. Error Status Code Values for the [Error Status] Field on the SRD DownloadConfiguration Window (Continued)




255-700-447 13-9



4 Select the Start System Software FTP Process command.

The value Working is displayed in the the [Copy Status] field, and the

following message is displayed in the status line:

T-FileTransferStatus: percentComplete=n

where n is a number (in increments of 10) from 0 to 100 percent, indi-

cating the amount of data that has been transferred (a progress

indicator).

After the file transfer is complete, the following message is displayed in

the status line:

T-FileTransferStatus: percentComplete=100.

5 After you observe the value, DoneSuccessfully, displayed in the [Copy

Status] field (about 15–20 sec after you see the message indicated in

step 4), go to the next section, “Upgrading the PSAX System Software”.

End

UnableToMakeFtpConnec-

tion

Displayed when the PSAX system cannot make a connection to

the host workstation running the FTP server software. Verify the

following, and correct any problems:• The pathname is correctly entered in the CD-Rom File Path

field.

• The workstation is operational.

• The FTP server software is running.

Try the download again by selecting the Start System Software

FTP Process command.

UnableToMakeNextTree Displayed when the directory, which will contain the new system

software release, could not be created, for example, the disk drive

failed. Call Technical Support for assistance.*

UnableToOpenFile Displayed when a file could not be opened, for example, the disk

drive failed. Call Technical Support for assistance.*

UnableToOpenLibraryFile Displayed when a library file could not be opened, for example,

the disk drive failed. Call Technical Support for assistance.*

UnableToUpdateBackup This status is not currently used.

UnableToWriteFile Displayed when the system cannot write to a file, for example, the

disk drive failed. Call Technical Support for assistance.*

UnableToWritePackageList Displayed when the system cannot write to a package list file, for

example, the disk drive failed. Call Technical Support for assis-

tance.*

UserAbort Displayed when you decide to terminate the download process

while it is running by selecting the Abort System Software FTP

Process command.

* To call Technical Support, see Chapter 1 in this guide for contact instructions.

Table 13-4. Error Status Code Values for the [Error Status] Field on the SRD DownloadConfiguration Window (Continued)





13-10 255-700-447


Upgrading the PSAX System Software

To upgrade your PSAX system software to Release 9.0.0 from an earlier

release, perform the steps in the following procedures.

Begin

1 On the SRD Download Configuration window, select the Go Back to

Version Configuration command.

The Software Version Configuration window is redisplayed.

2 On the Software Version Configuration window, select the Upgrade

Software Version command.

The following system prompt is displayed in the status line:

Are you sure that you want to upgrade the software? (y/n)

3 In response to this system prompt, choose one of the options in

Table 13-5.

End

Table 13-5. Determining Whether to Proceed with System Upgrade

If you want to... do thefollowing:

The system...

change your system

configuration before

upgrading, or you do

not want to proceed

with the upgrade at

the present time

type N (for

no).

displays the following message:Operation aborted.

proceed with the sys-

tem upgrade

type Y (for

yes).

determines whether you made any changes to your system

configuration without saving the configuration before you

selected the Upgrade Software Version command. If this

condition is true, the following message is displayed instead:Configuration files were modified. Do you want to

proceed without saving? (y/n)

If this message is displayed, perform the procedure in “Saving

Your System Configuration Before System Upgrade” on

page 13-11. If you did not make any changes to your system

configuration or you saved any changes prior to selecting the

Upgrade Software Version command, the system is

upgraded to the software release you specified, which is dis-

played in the brackets ([ ]) to the right of the Upgrade Soft-

ware Version command. During the upgrade process, the

following message is displayed: Upgrading the software

to the next version... For information about the CPUn module behavior and sys-

tem events occurring during booting, see“Module LED Indi-

cators During Booting” on page 13-12 and “System Events

During Booting” on page 13-13.



255-700-447 13-11



The migration of system software libraries and the database during the soft-

ware upgrade process is shown in Figure 13-4.

Saving Your System Configuration Before System Upgrade

Before you upgrade your system software, you must determine whether you

need to save your current system configuration first. Perform the steps in the


Begin

1 If you received the following system prompt on the Software Version

Configuration window, choose one of the options in Table 13-6.

Configuration files were modified. Do you want to proceed

without saving? (y/n)

Figure 13-4. Migration of the Files During the PSAX System Upgrade

Fallback Directory/scsi/fallback/

Current Directory/scsi/current/

Next Directory/scsi/next/

FTP File Transfer Process(First Stage)

Software Upgrade Process(Second Stage)

Current database files

are copied

CD-ROM

New version of softwarefiles is copied

Fallback Directory/scsi/fallback/

(now contains the old version--the original contents are

deleted)

Current Directory/scsi/current/

(now contains the new versionwith the existing database files)

Next Directory/scsi/next/

(still contains the new versionuntil the next upgrade)

New version of software and

current database files are copied

Old version of software andcurrent databases are copied



Chapter 13 Upgrading PSAX System SoftwareModule LED Indicators During Booting

13-12 255-700-447


If you selected the first option in Table 13-6, follow these steps to save your

latest system configuration changes:


3 Select the Save Configuration (Modified) command. (The word

Modified in the command indicates that you have changed the systemconfiguration since the last time you used this command.)

The following message is displayed:

T-SaveConfiguration: saveConfigurationReasonCode=All-OK

4 To return to the Software Version Configuration window to finish the

software upgrade process, select the Software Version Configuration

command.

The Software Version Configuration window is displayed.

5 Repeat Steps 2 and 3 in the preceding procedure.

End

Module LED Indicators During Booting

When the primary CPUn module boots, the libraries are loaded, the system

begins to initialize, and the red LED (FAIL) begins to blink. After booting on

the primary CPUn module is complete, the red LED lights and the green LED

(ACTIVE) becomes dark.

Table 13-6. Determining Whether to Save Your Current System Configuration Before Upgrade

If you... do the following: The system...

do not want to pro-

ceed with an

unsaved configura-

tion

type N (for no). displays the following message:Please save the configuration files from the

main screen before Upgrading.

Proceed to steps 2 and 3 in this procedure followingthis table.

do want to proceed

with an unsaved

configuration

type Y (for yes).

Important Note: You

would select yes only

in very unusual cir-

cumstances, for

example, if Lucent

Technologies Techni-

cal Support advises

you to select this

option.

displays the following message:Database not saved. Upgrading the software to

the next version.

The system is upgraded to the new software version

without saving any configuration changes you previ-

ously made in the current console session. The PSAX

system is upgraded to the software release you speci-

fied, which is displayed in the brackets ([ ]) to the

right of the Upgrade Software Version command.

During the upgrade process, the following message is

displayed: Upgrading the software to the next

version...

For information about the CPUn module behavior and

system events occurring during booting, see “Reboot-

ing CPUn Modules in Redundant and Nonredundant

Systems” on page 5-46.



255-700-447 13-13


Chapter 13 Upgrading PSAX System SoftwareSystem Events During Booting

In a redundant PSAX system, when a standby (backup) CPUn module boots,

its red LED is lighted. At the time the PSAX system is initializing, the red LED

begins to blink. After the configuration manager has determined that this

CPUn module is to become the standby CPUn module, a handshake between

the two CPUn modules takes place, and the configuration database files on

the primary CPUn module are transferred to the standby CPUn module. After

the transfer of files is completed, the red LED stops blinking.

If the standby CPUn module has a PSAX system software version that is ear-

lier than that of the primary CPUn module, the database files are incompati-

ble and therefore not transferred from the primary CPUn module to the

standby CPUn module. The red LED on the standby CPUn module continues

to blink. This does not hinder its ability to take over the role as the primary

CPUn module in the event that the primary CPUn module fails. If CPUn

switchover occurs when the red LED is blinking, data will be lost and any old

configuration present on the standby CPUn module is displayed.

System Events During Booting

The following events occur during the final stage of the upgrade process:

• In a PSAX system with redundant (two) CPUn modules, the following

events occur:

~ The system copies the fallback and current directories to the standby

(backup) CPUn module.

~ The standby module boots (initializes).

~ After the standby CPUn module boots successfully, it serves momentarily

as the primary module and sends a command to the original primary

module to boot.

~ The original primary module boots and re-establishes itself as the pri-

mary module, and then the original standby module boots itself.• In a PSAX system with one CPUn module, the CPUn module boots itself.

• If firmware drivers are available in the upgrade software, the affected I/O

and server modules are upgraded.

Verifying Successful Downloading of Module FirmwareDrivers

After you respond Yes to the system prompt to upgrade the PSAX system

software on the Software Version Configuration window, the PSAX system

automatically downloads the firmware drivers to the I/O, server, and Stratum

3–4 modules. The length of time you must wait for the firmware drivers todownload before performing any of actions, listed in the following Caution,

on the PSAX system is described in Table 13-7.



Chapter 13 Upgrading PSAX System SoftwareVerifying Successful Downloading of Module Firmware Drivers

13-14 255-700-447


! CAUTION:You must wait a sufficient length of time for the new firmware drivers tobe completely and successfully downloaded to I/O, server, and Stratum3–4 modules before performing any of the following actions:

• Rebooting the primary or standby CPUn module or the PSAX chassis

• Performing a primary CPU switchover

• Synchronizing the standby CPUn module software version with the pri-mary CPUn module

• Restoring your database files from a separate storage medium to thePSAX system using the Remote Database Operation window

• Changing any configuration values

You can verify successful firmware downloading by viewing both the Firm-

ware Version Control and the Equipment Configuration windows, as

described in the following procedure.

Begin

1 To view the status displayed for the firmware downloading on the Firm-ware Version Control window, perform the following steps:

a After the PSAX system finishes the boot process, log onto the system

in the normal fashion.

b To access the Firmware Version Control window, follow this path:

Console Interface Main Menu window —> select the Software Ver-

sion Configuration option —> Software Version Configuration

window —> select the Firmware Version Control option.

c On the Firmware Version Control window, verify that the value

Done is displayed in the Status field for all modules. If any other

value is displayed in this field for any module, refer to the field

descriptions for this window in Table 19 in the section, “ManuallySelecting I/O and Server Module Firmware Drivers” on page 1-30.”

to find out what the value you are observing means.

2 To view the module status information displayed on the Equipment Con-

figuration window, perform the following steps:

a To access the Equipment Configuration window, follow this path:

press Ctrl+G —> Console Interface Main Menu window —> select

the Equipment Configuration option.

Table 13-7. Length of Time Required for Firmware Downloading

If you are upgrading a... then wait the following period of time forthe firmware drivers to download...

PSAX 1000, PSAX 1250, or

PSAX 2300 system

5 minutes per Stratum 3–4 module

PSAX 4500 system 30 minutes per Stratum 3–4 module



255-700-447 13-15


Chapter 13 Upgrading PSAX System SoftwareUpgrading Using the XModem/YModem File Transfer Method

b On the Equipment Configuration window, verify that PSAX system

software version to which you just upgraded is displayed in the SW

Version field. Be sure to view page 2 of the Equipment Configuration

window (Page Down command) also to check the software version

of the Stratum 3–4 module(s).

End

Upgrading Using the XModem/YModem File TransferMethod

You can use the XModem/YModem file transfer method to load new system

software to the CPUn module. Upgrading using the XModem/YModem file

transfer method includes two major tasks:

1. Setting up the cabling and connections between the PC workstation and

the PSAX system CPUn module, starting up the VT100 terminal emula-

tion software on the PC workstation, and ensuring you have communi-cation between the two devices (see the following section, “Setting Up

for the File Transfer Process”)

2. Transferring the software upgrade files to the PSAX system using the

XModem or YModem protocol, and upgrading the PSAX system on the

CPUn module (see the section “Downloading Software Files Using

XModem/YModem”)

Lucent recommends that you use the FTP method; however, if you have only

the XModem or YModem file transfer method available, you should consider

which of the three XModem or YModem protocols in the following list to

use. Of these three protocols, Lucent recommends you use either the

YModem-G or the YModem protocol per the following considerations:• The YModem-G protocol allows the fastest transmission of the three types;









discouraged but use it only if this protocol is the only option available to

you.

Note: Transferring the software upgrade files using the YModem protocoltakes approximately 24 hours. Using the XModem protocol takes

longer than the YModem protocol.

Setting Up for the File Transfer Process

Before you can begin transferring the files, you must first set up your modem

and cabling. Perform the steps in the following procedure.




13-16 255-700-447


Begin

1 To set up the cabling and connections between the PC workstation, the

local modem, and the telephone line, do one of the following as shown

in Table 13-8.

2 To set up the cabling and connections between the PSAX system CPUn module, the remote modem, and the telephone line, do the following as

shown in Table 13-9.

3 On the PC workstation, start up the VT100 terminal emulation software,and set up the configuration preferences. See any PacketStar PSAX Multi-

service Media Gateway user guide for more information.

4 Using the terminal emulator modem communication function, enter the

telephone number of the line connected to the modem connected to the

PSAX system.

End

Downloading Software Files Using XModem/YModem

Perform the steps in the following procedure to download software files to

your PSAX system.

Begin

1 Using the VT100 terminal emulator, log on to the PSAX system.



Table 13-8. Setting Up the Connection Between the PC Workstation, the LocalModem, and the Telephone Jack

If you are using an... connect a cable from the...

external modem EIA-232 interface port on the PC workstation to

the modem, and a cable from the modem to the

telephone jack.

internal modem modem port on the PC workstation to the tele-

phone jack.

Table 13-9. Setting Up the Connection Between the Modem and the PSAXSystem

Connect a cable from the... to the...

CONSOLE port on the primary CPUn module modem.

modem telephone jack.



255-700-447 13-17




played.

3 On the Software Version Configuration window, select the


The XMODEM/YMODEM File Transfer window (see Figure 13-6) is dis-

played.

Figure 13-5. Software Version Configuration Window (XMODEM/YMODEM FileTransfer Selected)




13-18 255-700-447



Field Descriptions 4 Enter values in the fields on this window according to the information


Figure 13-6. XMODEM/YMODEM File Transfer Window (Receive Options PanelSelected)

Table 13-10. Commands for the XMODEM/YMODEM File Transfer Window

Command Function

Send File Initiates the send function of the file transfer process from

the CPUn module system disk to a storage medium (such

as a Unix or PC workstation system disk).

Receive File Initiates the receiving function of the file transfer process

to the CPUn module system disk from the CD-ROM con-

taining the software upgrade files (running in a CD-ROM

drive in a Unix or PC workstation).

Reset Display to System Defaults Redisplays the default values in the fields.




255-700-447 13-19



Table 13-11. Field Descriptions for the XMODEM/YMODEM File Transfer Window


Note: To upgrade your PSAX system software, use only the fields on the Receive Options panel. To back up your PSAX system configuration (database) files, use only the fields on the

Send Options panel.

Receive Options Panel


Range: N/A

Format: Predefined

alphanumeric


receiving data.




used for receiving the software upgrade files.




Range: N/A

Format: Predefined

alphanumeric


mitted.








Error Check Default: CRC-16

Range: N/A

Format: Predefined

alphanumeric

Specifies the type of error checking performed onthe data received. This field is displayed only

when the value XModem is selected in the Pro-

tocol field.

CRC-16 Indicates that the error checking method is cycli-

cal redundant checking, 16 bits.

Checksum Indicates that the error checking method is arith-

metic summation checking, 8 bits.

Directory Default: /scsi/next/

Range: N/A

Format: /scsi/next/

directoryname/

Specifies the subdirectory on the CPUn module

system disk where the software upgrade files are

received (stored). For each subdirectory con-

tained in the package of software upgrade files,you must enter the subdirectory name in this

field, and then receive this directory on the CPUn

module system disk.







13-20 255-700-447



Range: N/A

Format: alphanu-

meric

Specifies the filename on the CPUn module sys-

tem disk where the software upgrade files are

received (stored). For each file contained in the

package of software upgrade files, enter the file-name in this field, and then receive this file on

the CPUn module system disk. This field is dis-

played only when the value XModem is selected

in the Protocol field.




Send Options Panel


Range: N/A

Format: Predefined

alphanumeric


sending data.




PSAX system backup.


used for sending the PSAX system files to the

computer workstation where you will store your

PSAX system backup.




PSAX system backup.


Range: N/A

Format: Predefined

alphanumeric


mitted.












255-700-447 13-21



5 Select the Receive Files command.

The terminal emulator displaying the PSAX system window interface

takes the XMODEM/YMODEM File Transfer window out of view. A mes-

sage is displayed indicating that you can cancel the transfer by pressing

Ctrl+X several times. A second message is displayed indicating that you

must start the terminal emulator send function.

6 Using the terminal emulator send function, select one of the three proto-

col types: 1) YModem, 2) YModem-G, or 3) XModem. Be sure to select

the same protocol as the one you selected on the Send Options panel ofthe XMODEM/YMODEM File Transfer window (see Figure 13-6).


where the PSAX system software upgrade files reside (normally, the

CD-ROM drive) and the directory pathname.

For example, specify a pathname like one of the following:

• x :/scsi/next/ subdirectory\*.* if you are using YModem or YModem-G

where x is the drive letter for the CD-ROM drive

• x :/scsi/next/ subdirectory\ filename if you are using XModem where x is

the drive letter for the CD-ROM drive

Be sure you enter the subdirectory name (or the subdirectory and file-

name if using XModem) exactly so that it matches the names you previ-ously entered on the XMODEM/YMODEM File Transfer window (see

Figure 13-6). All subdirectory and file names are listed in the readme.txt

file accompanying the software upgrade files on the CD-ROM.

8 Select the Send File command in the terminal emulator send function

dialog box.

Packet Size Default: 1024

Range: N/A

Format: Predefined

numeric (bytes)

Specifies the size (in bytes) of the packet that will

be transmitted in the data stream.



Directory Default: /scsi/cur-

rent/

Range: N/A


Specifies the directory on the CPUn module sys-

tem disk where the PSAX system configuration

(database) files are stored. This directory contains

the files that you want to back up on your com-

puter workstation.


Range: N/A

Format: alphanu-

meric

Specifies the filename of the PSAX system config-

uration (database) file you want to back up on

your computer workstation.





Chapter 13 Upgrading PSAX System SoftwareManually Selecting I/O and Server Module Firmware Drivers

13-22 255-700-447


9 Repeat steps 4–8 to specify another subdirectory name (for YModem or

YModem-G) or another subdirectory name and filename (for XModem)

until you have transferred all files for the PSAX system software upgrade.

Note: The new version of the software and the existing database files are

now resident in the directory /scsi/next/ (see Figure 13-4).

End

Upgrading the PSAX System Software

Perform the steps in the following procedure to upgrade your system soft-

ware.

Begin

1 On the XMODEM/YMODEM File Transfer window, select the Go Back

to Version Configuration command.

The Software Version Configuration window is redisplayed (see

Figure 13-5).

2 Select the Upgrade Software Version command.


Are you sure that you want to upgrade the software - chassis

will reboot? (y/n)

3 In response to this system prompt, type Y (for yes).

Initially, the following message is displayed:

Upgrading the software to the next version...

After about 30 seconds, the chassis boots. When this event is finished,

you are able to log on to the PSAX system again.4 For information about the CPUn module behavior and system events

occurring during booting, see the sections, “Module LED Indicators Dur-

ing Booting” on page 13-12 and “System Events During Booting” on

page 13-13.

5 For information about verifying the downloading of module firmware

drivers, see the section, “Verifying Successful Downloading of Module

Firmware Drivers” on page 13-13.

En

Manually Selecting I/O and Server Module Firmware DriversPacketStar PSAX I/O and server modules released with PSAX system software

Release 6.0.0 and subsequent are supported by the Firmware Release Control

feature. The Release Note for Release 9.0.0 Controlled Introduction of the PacketStar

PSAX 4500, PSAX 2300, PSAX 1250, and PSAX 1000 Multiservice Media Gateways

lists the current firmware driver for each PSAX I/O and server module along

with the reason for releasing a new driver.



255-700-447 13-23



A firmware driver is a binary file used to initialize (boot) an I/O or a server

module. The two types of drivers are the default driver and a nondefault

(configurable) driver. The PSAX system selects the default driver when the

I/O or server module boots for the first time after it is inserted into the PSAX

chassis.

Manually selecting a different firmware driver (other than the default driver)for an I/O or a server module includes the following tasks:

• “Accessing the Firmware Version Control Window”

• “Selecting a Firmware Driver”

• “Downloading a Firmware Driver”

Accessing the Firmware Version Control Window

To access the Firmware Version Control window on which you change or

update firmware drivers for I/O and server modules, perform the steps in the


Begin


the Software Version Configuration option.

The Software Version Configuration window is displayed.

2 On the Software Version Configuration window (see Figure 13-8), select

the Firmware Version Control option.

The Firmware Version Control window is displayed.

Figure 13-7. Console Interface Main Menu Window (Software VersionConfiguration Option Selected)




13-24 255-700-447


End

Selecting a Firmware Driver

To select a firmware driver different from the default driver, or to reselect the

default driver on a module that is currently using a nondefault driver, per-

form the steps in the following procedure.

Begin

1 On the Firmware Version Control window (see Figure 13-9), position the

cursor on the line containing the module for which you want to down-

load a different driver, and press Enter two or more times to display all

the available drivers for that module.

In the NextVersion field, each driver available for that module is dis-

played as you press Enter. The default driver is indicated by an asterisk

next to the driver filename. The first four digits of the driver code corre-

spond to the firmware release number. The last four digits of the driver

code correspond to the checksum. The drivers displayed in this field are

the only downloadable firmware drivers available for the selected mod-ule. The commands on this window are described in Table 13-13, and the

fields are described in Table 13-14.

2 Select either the default driver or a nondefault driver from the drivers

available. To help you correctly select which driver to download to the

selected module, the information in Table 13-12 describes several scenar-

ios.

Figure 13-8. The Software Version Configuration Window (Firmware VersionControl Selected)



255-700-447 13-25



End

Table 13-12. Selecting Firmware Drivers

If you... do the following:

select the default driver, Install any I/O or server module into the PSAX

chassis slot.

select a nondefault

driver,

Install only the particular I/O or server module

that is meant for this driver into the PSAX chassis

slot. If you installed an I/O or server module that

was not meant for this driver, the message,

wrongcardtype, is displayed in the status line on

the Firmware Version Control window. The

PSAX system attempts to download the driver for

this I/O or server module for approximately six

minutes. The PSAX system will recognize the I/O

or server module automatically when you install

the configured I/O or server module during the

download time (six minutes). If the correct I/O

or server module is not installed during the

download time, you must select the StartUpgrade command on the Firmware Version

Control window.

want to install an I/O or

server module into a par-

ticular slot that was for-

merly occupied by a

different module config-

ured in that slot,

Install the new module, select the default driver

for that module, and then select the Start

Upgrade command on the Firmware Version

Control window.

The newly installed module is now displayed on

the Firmware Version Control window.




13-26 255-700-447



Field Descriptions The fields on this window are described in Table 13-14.

Figure 13-9. Firmware Version Control Window

Table 13-13. Commands for the Firmware Version Control Window

Command Function

Update Screen Refreshes the values on this window to display the current

firmware configuration for all modules in the system.

Start Upgrade Initiates the downloading of firmware by the selected driver

in the NextVersion field.Back to Software Config-

uration

Redisplays the Software Version Configuration window.



255-700-447 13-27



Table 13-14. Field Descriptions for the Firmware Version Control Window


Slot Default: N/A

Range: chassis depen-

dent

Format: Numeric

Displays the chassis slot in which the I/O, server,

or Stratum3–4 module is installed.

Card Type Default: N/A

Range: N/A

Format: Predefined

alphanumeric

Displays the name of the I/O or server module in

the slot.

Current Ver Default: N/A

Range: dependent on

installed software

version

Format: Predefined

alphanumeric

Displays the version of the firmware currently

loaded on this module. The first four characters of

the driver filename correspond to the firmware

release number (FRN) in hexadecimal format,

and the last four characters correspond to the

checksum in hexadecimal format.

Note: An asterisk (*) after the driver filenameindicates the default version of the driver for this

module.




13-28 255-700-447


Status Default: N/A

Range: N/A

Format: Predefined

alphanumeric

Displays the status of the firmware downloading

after you select the Start Upgrade command. A

system message is also displayed in the status line

at the bottom of the window.Note: If you have just upgraded your PSAX sys-

tem software, make sure that the value Done is

displayed in this field for all modules before you

do any of the following:

• Reboot the primary or standby CPUn module

or the PSAX chassis

• Perform a primary CPU switchover

• Synchronize the standby CPUn module soft-

ware version with the primary CPUn module

• Restore your database files from a separate

storage medium to the PSAX system using the

Remote Database Operation window• Change any configuration values

Done Indicates that the firmware downloading on the

module was complete and successful.

Progress Indicates that the new firmware is currently

being downloaded.

Retry Indicates that the PSAX system is attempting to

download the firmware. After 2,048 attempts are

tried unsuccessfully, the value Failed is displayed

in this field.

ReqRepTimeout Indicates that a request to download the firm-

ware was made but no reply from the modulewas received during the designated time period.

RequestPending Indicates that a request to download the firm-

ware was made and the system is waiting for a

response from the module.

Failed Indicates that the attempt to download the new

firmware failed.

RemoveCardBefore

Finish

Indicates that while the firmware was being

downloaded to the module, the user removed it

from the PSAX chassis; therefore, the firmware

download was not completed.

WrongCardType Indicates that one type of module was configured

in this slot in the chassis, but now a different

module occupies this slot.

WrongCardSType Indicates that one type of stratum module was

configured in this slot in the chassis, but now a

different stratum module occupies this slot.

Table 13-14. Field Descriptions for the Firmware Version Control Window (Continued)




255-700-447 13-29



Downloading a Firmware Driver

After you have selected the firmware driver you want to use on a selectedmodule, perform the steps in the following procedure to download the

selected driver.

Begin

1 On the Firmware Version Control window, select the Start Upgrade

command to download the firmware driver you selected in Step 2 in the

previous section, “Selecting a Firmware Driver” on page 13-24.

After the downloading process is completed, the following message is dis-

played in the status line:

FirmwareDownloadSucceeded.

2 To verify the installation of the new firmware driver on the selected

module, perform the following steps:

a To redisplay the Console Interface Main Menu window, press Ctrl+G.

The Console Interface Main Menu window is redisplayed.

b On the Console Interface Main Menu window, select the Equipment


NextVersion Default: N/A

Range: dependent on

installed software

versionFormat: Predefined

alphanumeric

Displays the version of the firmware you select to

download to the module. The first four characters

of the driver filename correspond to the firmware

release number (FRN) in hexadecimal format,and the last four characters correspond to the

checksum in hexadecimal format.

Note: An asterisk (*) after the driver filename

indicates the default version of the driver for this

module.

Dnld Cmd Default: None

Range: N/A

Format: Predefined

alphanumeric

Displays the type of firmware download action

the PSAX system performed on the firmware

driver currently displayed in the Current Ver

field.

None Indicates that no firmware driver downloading

has taken place.

normalDownload Indicates that the firmware driver displayed in

the Current Ver field was downloaded as a nor-

mal function of a PSAX system software upgrade.

forceDownload Indicates that the firmware driver displayed in

the Current Ver field was downloaded as a result

of selecting the driver in the NextVersion field

and then selecting the Start Upgrade command.

Table 13-14. Field Descriptions for the Firmware Version Control Window (Continued)





13-30 255-700-447


The Equipment Configuration window is displayed. Updated infor-

mation in the SW Version field is displayed for the newly updated

module. A confirmation message is displayed in the status line at the


End




255-700-447 A-1

A Common Equipment ModuleConnections

Overview of This Appendix

This appendix describes the connector pin assignments for the common

equipment modules installed in the PSAX 2300 chassis.

CPU4 Module Connectors

CONSOLE Connector

The CONSOLE connector on the CPU4 module accepts an RJ-12 connector.

Pin assignments for the CONSOLE connector are listed in Table A-1.

A console cable (straight-thru, pins 1–6) and console cable adapters are sup-

plied with the chassis to connect the system to a workstation. The console

cable adapters are described in “Console Cable Adapters” on page A-3.

ETHERNET1 and ETHERNET2 Connector

The CPU4 module faceplate also provides two 10/100BASE-T Ethernet inter-

faces using two RJ-45 connectors. Figure A-1 shows the pin locations for

both of the Ethernet connectors on the faceplate of the module.

Note: The ETHERNET2 connector is reserved for future enhancements.

Table A-2 lists the pin assignments for the ETHERNET1 and ETHERNET2 con-

nectors on the faceplate.

Table A-1. CPU4 Module CONSOLE Connector Pin Assignments

Pin Description

2 TXD (from CPU4)

3 RXD (to CPU4)

4 Ground

Figure A-1. ETHERNET1 and ETHERNET2 Connector Pin Locations

12345678



Appendix A Common Equipment Module ConnectionsCPU2 Module Connectors

A-2 255-700-447


CPU2 Module Connectors

CONSOLE Connector

The CONSOLE connector on the CPU2 module accepts an RJ-12 connector.

Pin assignments for the CONSOLE connector are listed in Table A-3.

A console cable (straight-thru, pins 1–6) and console cable adapters are sup-

plied with the chassis to connect the system to a workstation. The console

cable adapters are described in “Console Cable Adapters” on page A-3.

ETHERNET Connector

The CPU2 module faceplate also provides a 10BASE-T Ethernet interface

using an RJ-45 connector. Figure A-2 shows the pin locations for the

ETHERNET connector on the faceplate of the module.

Table A-2. CPU4 Module ETHERNET1 and ETHERNET2 Connector PinAssignments

Pin Description

1 TD+ (CPU4 transmit+)

2 TD– (CPU4 transmit–)3 RD+ (CPU4 receive+)

4 Reserved

5 Reserved

6 RD– (CPU4 receive–)

7 Reserved

8 Reserved

Table A-3. CPU2 Module CONSOLE Connector Pin Assignments

Pin Description

2 TXD (from CPU2)

3 RXD (to CPU2)

4 Ground

Figure A-2. ETHERNET Connector Pin Locations

1 2 3 4 5 6 7 8



255-700-447 A-3


Appendix A Common Equipment Module ConnectionsConsole Cable Adapters

The CPU2 module ETHERNET connector does not follow the standard Ether-

net wiring configuration. Under normal operation, you can only control the

system from either the CONSOLE connector or the ETHERNET connector when

you use a standard 8-wire Ethernet cable. If a situation occurs where simul-

taneous operation is required, the Ethernet cable must be modified so only

pins 1,2, 3, and 6 are connected through to the network.

Table A-4 lists the pin assignments for the non-standard RJ-45 ETHERNET

connector on the faceplate.

Console Cable Adapters

If you are using the console cable (supplied with the chassis) to connect to

the serial port of a personal computer (PC) or workstation, use either an

RJ-12-to-DB9 adapter or an RJ-12-to-DB25 adapter (both supplied with the

chassis). Table A-5 describes the pin assignments for RJ-12-to-DB9 adapterand Table A-6 describes the pin assignments for RJ-12-to-DB25 adapter.

Table A-4. CPU2 Module ETHERNET Connector Pin Assignments

Pin Description

1 TD+ (CPU2 transmit+)

2 TD– (CPU2 transmit–)

3 RD+ (CPU2 receive+)

4 Reserved

5 Reserved

6 RD– (CPU2 receive–)

7 Reserved

8 Reserved

Table A-5. RJ-12-to-DB9 Adapter Pin Assignments

RJ-12 Pins DB9 Pins Description

2 2 TX (CPU transmit)

3 3 RX (CPU receive)

4 5 Ground

Table A-6. RJ-12-to-DB25 Adapter Pin Assignments

RJ-12 Pins DB25 Pins*

* Pins 4 (RTS) and 5 (CTS) are jumpered together and pins 6 (DSR) and

20 (DTR) are jumpered together.

Description

2 2 TX (CPU transmit)

3 3 RX (CPU receive)

4 7 Ground



Appendix A Common Equipment Module ConnectionsStratum 3–4 Connector

A-4 255-700-447


Stratum 3–4 Connector

The composite clock signal is a balanced signal, which is transmitted over a

shielded twisted pair cable. The cable shield is grounded at the composite

clock source.

Table A-7 describes the pin assignments for the faceplate RJ-45 connector onthe Stratum 3–4 module.

Alarm Module Connectors

The following connectors (ALARM and STATUS/CONTROL) are provided on the

Alarm module (model 20N79) for CO alarm, sensors, and remote controls.

ALARM Connector

Figure A-3 illustrates the pin locations of the 26-pin ALARM connector on the

Alarm module (model 20N79) faceplate.

Table A-7. Stratum 3–4 Module RJ-45 Connector Pin Assignments

Pin Description

1 IN (ring)

2 IN (tip)

3 Not Used

4 Not Used

5 Not Used

6 Frame Ground

7 Not Used

8 Not Used

Figure A-3. ALARM Connector Pin Locations on the Alarm Module

918

26

110

19

Pin 1

Pin 10

Pin 26

Pin 18Pin 9

Pin 19



255-700-447 A-5


Appendix A Common Equipment Module ConnectionsAlarm Module Connectors

A shielded 3.7-meter (12-foot) Lucent cable (Part Number 42-20N79004,

COMCODE 300164290) is available with a matching connector on one end

and a 16-pair twisted wire pigtail on the other end (see Figure A-4).

The pin assignments for the ALARM connector and the shielded Lucent cable

pigtail color code are described in Table A-8.

Figure A-4. ALARM Cable with 26-Pin Connector and Pigtail

Table A-8. ALARM Connector Pin Assignments and Cable Pigtail Color Code(COMCODE 300164290)

ConnectorPin

Description Cable Pigtail Color Code*

2 Audible Critical Alarm COM† contact‡ White/Brown

13 Audible Critical Alarm NC§ contact White/Violet

1 Audible Critical Alarm NO¶ contact White/Tan

4 Audible Major Alarm COM contact White/Pink

14 Audible Major Alarm NC contact White/Gray

3 Audible Major Alarm NO contact Brown/White

6 Audible Minor Alarm COM contact White/Orange

15 Audible Minor Alarm NC contact Tan/Brown

5 Audible Minor Alarm NO contact Pink/White

20 Battery Return** Orange/Tan

26 Frame Ground Yellow/Tan

24 Remote Alarm Cutoff Battery Return Pink/Tan

23 Remote Alarm Cutoff input†† Brown/Tan

19 Unused Tan/Orange

21 Unused Violet/White

22 Unused Gray/White

25 Unused Tan/Yellow

8 Visible Critical Alarm COM contact

‡

White/Yellow16 Visible Critical Alarm NC contact Tan/Pink

7 Visible Critical Alarm NO contact Orange/White

10 Visible Major Alarm COM contact Tan/White

17 Visible Major Alarm NC contact Yellow/White

9 Visible Major Alarm NO contact White/Green




A-6 255-700-447


STATUS/CONTROL Connector

Figure A-5 illustrates the pin locations of the 44-pin STATUS/CONTROL con-

nector on the Alarm module (model 20N79) faceplate.

A shielded 3.7-meter (12-foot) Lucent cable (Part Number 42-20N79003,COMCODE 300164282) is available with a matching connector on one end

and a 25-pair twisted pair pigtail on the other end (see Figure A-6).

12 Visible Minor Alarm COM contact Blue/White

18 Visible Minor Alarm NC contact Green/White

11 Visible Minor Alarm NO contact White/Blue

* Color code subject to change without notice.† COM is common relay contact between NC and NO contacts.‡ Audible and visible critical alarm relays are shown normally energized when no alarm is

being generated. A critical alarm is generated through a command that de-energizes the

relay or when power is lost.§ NC is normally closed relay contact.¶ NO is normally open relay contact.

** Battery Return is used typically for -48 V dc operation.†† Contact closure or input command is sensed by opto-isolator.

Table A-8. ALARM Connector Pin Assignments and Cable Pigtail Color Code(COMCODE 300164290) (Continued)

ConnectorPin


Figure A-5. Pin Locations for the STATUS/CONTROL Connector on the Alarm Module

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

20

21

22

23

24

25

26

27

28

29

30

16

17

18

19

31

32

33

34

35

36

37

38

39

40

41

42

43

44

S T A T U S / C O N T R O L

Pin 1



255-700-447 A-7



The pin assignments for the STATUS/CONTROL connector and the shielded

Lucent cable pigtail color code are described in Table A-9.

Figure A-6. STATUS/CONTROL Cable with 44-Pin Connector and Pigtail

Table A-9. STATUS/CONTROL Connector Pin Assignments and Cable Pigtail Color Code(COMCODE 300164282)

ConnectorPin


43 Battery Return Brown/Blue

32 Control Output 1 COM contact Violet/Tan

33 Control Output 1 NC† contact Tan/Gray

31 Control Output 1 NO‡ contact Tan/Violet

36 Control Output 2 COM contact Pink/Brown

34 Control Output 2 NC contact Gray/Tan

35 Control Output 2 NO contact Brown/Pink

38 Control Output 3 COM contact Orange/Brown

39 Control Output 3 NC contact Brown/Yellow

37 Control Output 3 NO contact Brown/Orange

42 Control Output 4 COM contact Green/Brown

40 Control Output 4§ NC contact Yellow/Brown

41 Control Output 4 NO contact Brown/Green

44 Frame Ground Blue/Brown

1 Status Input 01 White/Tan

2 Battery Return¶ Tan/White

3 Status Input 02 White/Brown

4 Battery Return Brown/White

5 Status Input 03 White/Pink

6 Battery Return Pink/White7 Status Input 04 White/Orange

8 Battery Return Orange/White

9 Status Input 05 White/Yellow

10 Battery Return Yellow/White

11 Status Input 06 White/Green

12 Battery Return Green/White




A-8 255-700-447


13 Status Input 07 White/Blue

14 Battery Return Blue/White

15 Status Input 08 White/Violet

16 Battery Return Violet/White

17 Status Input 09 White/Gray

18 Battery Return Gray/White

19 Status Input 10 Tan/Brown

20 Battery Return Brown/Tan

21 Status Input 11 Tan/Pink

22 Battery Return Pink/Tan

23 Status Input 12 Tan/Orange

24 Battery Return Orange/Tan

25 Status Input 13 Tan/Yellow

26 Battery Return Yellow/Tan

27 Status Input 14 Tan/Green

28 Battery Return Green/Tan

29 Status Input 15 Tan/Blue

30 Battery Return Blue/Tan

* Color code subject to change without notice.† NC is normally closed relay contact.‡

NO is normally open relay contact.§ Shown in a normally energized state. A control command or loss of power changes the

relay contact state.¶ Battery Return is used typically for -48 V dc operation.

Table A-9. STATUS/CONTROL Connector Pin Assignments and Cable Pigtail Color Code(COMCODE 300164282) (Continued)

ConnectorPin





255-700-447 B-1

B Configuring In-Band Management

Overview of In-Band Management Configurations

Three types of in-band management configurations are available:

• Direct connection (see “Using the Direct Connection Configuration” on

page B-2)

The management host connects over an ATM WAN directly to an I/O

module port in a remote managed target (the PSAX system being man-

aged).

A direct connection can also be made between the network management

system (NMS) machine, usually a Sun Solaris workstation, to a PacketStar

PSAX Multiservice Media Gateway system through an OC-3c interface.

This configuration requires that the NMS machine have a FORE card.

• Routed connection (see “Using the Routed Connection Configuration” on

page B-4)

The management host connects over an Ethernet network to an I/O

module port in an PSAX system acting as a router. The “router” PSAX

system in turn has direct in-band management PVC connections to

remote PSAX systems (managed targets).

The routed connection configuration connects a PSAX system through

another PSAX system, which acts as a main router. The “main router”

PSAX system is connected to the NMS machine through an Ethernet

connection. The “main router” is connected to an “intermediate router”

PSAX system, or an “end system” PSAX system through ATM connec-

tions. In this configuration, ATM connections are made to the nearest

hop in the tree structure.

This route connection allows you to flexibly manage any number of

PSAX devices.

• Hybrid connection (see “Using the Hybrid Connection Configuration” on

page B-10)

Hybrid connection, which connects the main router PSAX device directly

to the end system PSAX systems through ATM PVC connections. These

ATM PVC connections can be sent through several PSAX systems to

reach the “end system” PSAX systems. The main router PSAX system is

connected to the NMS computer through an Ethernet LAN.

Hybrid connection configuration connects the “main router” PSAX sys-tem directly to the “end system” PSAX system through ATM connections.

These ATM connections can be tunneled through a number of switches

to reach the “end system” Multiservice Media Gateway system. The

“main router” PSAX system is connected to the NMS machine through

an Ethernet connection.

The guidelines for setting up an in-band management network for each of

these configurations are provided in the following sections.



Appendix B Configuring In-Band ManagementUsing the Direct Connection Configuration

B-2 255-700-447


Using the Direct Connection Configuration

The default gateway through the in-band network can be configured on all

Multiservice Media Gateway with the IP address of the NMS machine, or

network router, if used in place of an NMS station (see Figure B-1).

The tasks for setting up a direct connection configuration are the following:

1. Setting configuration values for the FORE card on the SUN workstation

(see “Setting Up the FORE Card on the SUN Workstation”)

2. Setting up ATM ARP entries for the end of the ATM connection at theSUN workstation (see “Setting Up ATM ARP Table Entries” on page B-3)

Setting Up the FORE Card on the SUN Workstation

On the SUN workstation, assign the FORE card interface an IP address that is

on a different network than the IP address for the Ethernet interface of the

SUN workstation. Perform the following procedure to set up the FORE card

on the SUN workstation.

Begin

1 On the SUN workstation, log in and type root.

2 To configure the FORE card, type the following command:

Figure B-1. Direct Connection Configuration Diagram

PSAX

ATM PVC Connections

ATM PVC Connections

ATM PVC Connections

Node A

Node BNMS(GenericRouter)

Node C

Node E

Node D

Physical Connections via Ethernet LAN

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX



255-700-447 B-3


Appendix B Configuring In-Band ManagementUsing the Direct Connection Configuration

ifconfig fa0 forecard_Ip_Address netmask Netmask broadcastBcast_address mtu Mtu_Size up

where,

forecard_Ip_Address = the IP address of the FORE card (for example,

136.242.140.222)

Netmask = the IP subnet mask (for example, 255.255.255.0)Bcast_address = the IP address of the broadcast server (for example,

136.242.140.255)

Mtu_Size = maximum transfer unit size [packet size] (for example,

9180—refer to RFC 1577)

3 To test whether the FORE card has been configured correctly, type the

following command:

ifconfig fa0

Consult your FORE user’s manual for additional instructions on the

many variables you may encounter beyond this point.

End

Setting Up ATM ARP Table Entries

ATM ARP table entries should be created on the SUN machine. Each entry

specifies the remote PSAX system in-band management IP address (primary)

and the corresponding ATM connection (VCC: VPC) that is connected to the

remote PSAX system. Add a PVC connection on the FORE card to the

in-band management port on the PSAX system. Perform the following proce-

dure to set up the PVC connections.

Begin

1 Type the following command:

Atmarp -s Remote_Ip fa0 VPI VCI AAL llc

Atmarp -l fa0 VPI VCI AAL llc

Where Remote_Ip = (IP Address of the in-band connection on the

CPUn module)

Example:

Local IP = 136.242.140.223 (Primary IP Address of Node A)

VPI= 0

VCI= 300

AAL= 5

and

Remote IP = 136.242.140.225 (Primary IP Address of Node B)

VPI= 0

VCI= 302

AAL= 5

Check whether the connections have been configured by using the

command atmarp -a



Appendix B Configuring In-Band ManagementUsing the Routed Connection Configuration

B-4 255-700-447


2 All the remote PSAX systems’ in-band interface IP addresses may or may

not be in the same subnet as that of the FORE card’s IP address.

3 If the remote PSAX systems’ in-band interface IP address is not in the

same subnet as that of the FORE card’s IP address, then a route entry

should be added on the SUN machine for the remote PSAX systems’ sub-

net, using the FORE card interface as the gateway.4 On the PSAX system, the in-band management interface (primary)

should be assigned an IP address that lies in a different network than that

of its Ethernet interface.

5 The in-band connection from each of the remote PSAX systems is a direct

connection to the SUN machine’s FORE card interface IP address. (Here a

direct connection implies that it should not be IP routed through a CPUn

module. It should be an ATM connection, which may be tunneled

through a number of switches.)

6 If the ATM end points are connected to a Cisco router instead of a SUN

machine, then the remote PSAX system can be configured with a default

gateway address, which should be the same as the in-band connection

end point’s IP address (that is, the Cisco router’s address).

7 The gateway IP address should be either an Ethernet subnet or an in-

band management subnet. The gateway IP address should not be the

same as the in-band IP address.

8 If the gateway IP address is in the in-band management subnet, then

there should be an in-band connection to that address.

9 If a traffic-shaping OC-3c module is used, the recommended values for

in-band connection are Peak Rate: 2000 cps; Sustained Rate: 1000 cps;

MBS: 10000 cells.

End

Using the Routed Connection Configuration

No default gateway through an in-band network should be configured on

any of the PSAX systems.



255-700-447 B-5



Setting Up Connections for a Routed Connection Configuration

Perform the following procedure to configure the routed connection.

Begin

1 A Routed Connection Configuration consists of a SUN (or PC) host con-

nected through Ethernet to the router PSAX system. The router PSAX

system has direct or routed in-band connections to the remote PSAX sys-

tem. Log in as root on the SUN machine and add a routing table entryusing the "route add" command:

route add net In-band network address PSAX IP address on Ethernet metric

where in-band network address = 20.0.0.0

PSAX IP address on Ethernet = {Check Site Specific Configuration - Site

Specific Configuration - IP Address on the main router PSAX system-

node A}

metric = 10

2 In this configuration, one or more PSAX systems can act as routers to

channel traffic to different subnets. There are two type of router PSAX

system connections. The first type is the main router connected directly

to the NMS stations (either through Ethernet or OC3c-ATM connection),and the second type is the intermediate router PSAX system. The main

router PSAX system has only one type of connection: downstream con-

nections to an intermediate router PSAX system or an end system PSAX

system. The intermediate router PSAX system has two types of in-band

connections: upstream connections to a router PSAX system and down-

stream connections to either the router PSAX system or the end system

PSAX system. This helps to form a simple tree structure (see Figure B-2).

Figure B-2. Routed Connection Configuration Diagram

PSAX

ATM PVCConnections

ATM PVC Connections

Node AMain Router

Ethernet or ATMPVC Connections

Node BIntermediateRouter

NMS

Node CIntermediateRouter

Node E

Node D

NMS

NMS


PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX




B-6 255-700-447


3 On the PSAX system, the in-band management interface (primary)

should be assigned an IP address that should be on a different network

than that of its Ethernet interface.

4 Also, for all the PSAX system models (except the main router PSAX sys-

tem), the Ethernet interface IP network should be different from the SUN

machine’s Ethernet interface IP network.5 All of the NMS stations should be in the one IP network, but can be in

different subnets connected to the main router PSAX system by an Ether-

net or OC3-ATM connection.

6 All the end system and router PSAX system in-band interface IP

addresses should be in the same IP network. They can have different

masks (that is, the PSAX system downstream can have a mask wider in

ones than that of the parent node). This allows multiple connections to

be set to end system PSAX system that are in the same in-band subnet.

Routing to intermediate PSAX systems is done based on the subnet mask.

The subnetwork address provided in the connection table and routing to

the end system PSAX system is based on the host address of the end sys-

tem configured in the connection table. Routing to the NMS stations is based on the mask and network address to the NMS stations configured

in the connection table. (With this configuration, an upstream connec-

tion should be made only to the NMS network).

7 The tree structure is based on subnet routing, where connections to each

subtree lie in one subnet and the connections to a downstream subtree

are configured with in-band subnetwork addresses and a mask larger

(wider in ones) than the parent subtree. (See the example configuration

in the next section).

8 The downstream connections to intermediate routers should be config-

ured with the subnetwork address of the subtree and a mask larger

(wider in ones) than that of the parent connections.

9 The upstream connection should only be to the NMS stations’ network

address with an appropriate mask.

10 On the host (SUN or PC) machine, an IP routing table entry should be

added. This entry should be a network-specific routing table entry, with

the in-band network address of each of the remote PSAX systems and the

main router PSAX system Ethernet interface IP address as the gateway.

The metric should be set to the depth of the tree (or default 10).

11 The default gateway should not be configured with an IP address within

the in-band network.

End

Setting PVC Connections for Routed Connection Configuration

Assume that the VPI:VCI for the connection between node A and B is VPIab:

VCIab, etc. Also assume that the Ethernet IP addresses of all nodes except

node A do not lie in the NMS station’s network address range. Perform the

following procedure to set PVC connections for a routed connection.



255-700-447 B-7



Begin

1 Configure the primary IP address for in-band management on the CPUn

module of the main router PSAX system (Node A) using the console

interface:

Select the Site Specific Configuration> In-Band Management menu

options.

Example:

Primary IP Address: 020.001.001.001

Primary IP Mask: 255.000.000.000

The connection downstream from Node A to subtrees should have a

mask greater than 255.0.0.0 if they go to network 20.0.0.0. For example,

mask 255.255.0.0 is assigned for downstream connection.

2 Configure the primary and backup IP addresses for in-band management

on the CPUn module of the intermediate router PSAX system (Node B)

using the console interface:

Example:

Primary IP Address:020.001.001.002


Connections downstream from Node B to the subtrees should have a

mask greater than for the connection downstream on parent Node A

(255.255.0.0) if they go to network 20.0.0.0. For example, mask

255.255.255.0 is assigned for downstream connection.

3 Configure the primary IP Address for in-band management on the CPUn

module of main router PSAX system (Node C) using the console inter-

face:

Select the Site Specific Configuration> In-Band Management menuoptions.

Example:



Connections downstream from Node C to subtrees will go directly to

end-system PSAX systems and should have mask greater than or equal to

that for connections on parent Node B (255.255.255.0) if they go to net-

work 20.0.0.0. For example, mask 255.255.255.0 is assigned for down-

stream connections


module of main router PSAX system (Node D) using the console inter-face:


options.

Example:






B-8 255-700-447



module of the main router PSAX system (Node E) using the console

interface:


options.

Example:Primary IP Address: 020.001.001.004



module of the main router PSAX system (Node X) using the console

interface:


options.

Example:




module of the main router PSAX system (Node Y) using the console

interface:


options.

Example:




module of main router PSAX system (Node Z) using the console inter-

face:


options.

Example:



9 Set up in-band management connections on the CPUn module of Node A

to DS3:

For setting up an in-band connection from the DS3 module to the CPUn

module, configure the DS3 module and put it into service. Select the

Connection Configuration > In-Band Management IP PVC > Add Con-nection menu options, configure the PVC to the FORECARD.

Example:

Slot:Slot Number VPI: VPIab IP Address: 020.001.000.000

Port:1 VCI: VCIab IP Mask: 255.255.000.000

Channel: 1

Slot: Slot Number VPI: VPIax IP Address: 020.002.000.000



255-700-447 B-9



Port: 1 VCI: VCIax IP Mask: 255.255.000.000

Channel: 1

10 Set up in-band management connections on the CPUn module of

Node B:

Example:

Slot: Slot Number VPI: VPIabIP Address: NMS net. addr

Port: 1 VCI: VCIab IP Mask: NMS net. mask

Channel: 1

Slot: Slot Number VPI: VPIbc IP Address: 020.001.001.000

Port: 1 VCI: VCIbc IP Mask: 255.255.255.000

Channel: 1

Slot: Slot Number VPI: VPIbd IP Address: 020.001.002.000

Port: 1 VCI: VCIbd IP Mask: 255.255.255.000

Channel: 1

11 Set up in-band management connections on the CPUn module of

Node C:

Example:

Slot: Slot Number VPI: VPIbc IP Address: NMS net. addr

Port: 1 VCI: VCIbc IP Mask: NMS net. mask

Channel: 1

Slot: Slot Number VPI: VPIce IP Address: 020.001.001.003

Port: 1 VCI: VCIce IP Mask: 255.255.255.000

Channel: 1

Slot: Slot Number VPI: VPIcf IP Address: 020.001.001.004

Port: 1 VCI: VCIcf IP Mask: 255.255.255.000

Channel: 1

12 Set up in-band managment connections on the CPUn module of Node E:

Example:

Slot: Slot Number VPI: VPIce IP Address: NMS net. addr

Port: 1 VCI: VCIce IP Mask: NMS net. mask

Channel: 113 Verify that a routing table entry from the SUN machine’s network to net-

work 20.0.0.0 exists on the SUN machine using the “netstat -nr”

command.

14 Use ping, telnet, rlogin and ftp from the SUN machine to nodes A, B, C, E

and F to test the TCP/IP connectivity.

End



Appendix B Configuring In-Band ManagementUsing the Hybrid Connection Configuration

B-10 255-700-447


Using the Hybrid Connection Configuration

The main router PSAX system (Node A) has two or more connections to

remote PSAX systems that are in the same in-band subnet as the Node A

PSAX system.

Default gateways through in-band connections can be configured on allremote PSAX systems (that is, all PSAX systems except Node A) with the IP

address of Node A’s in-band interface. In this case, in-band connections on

remote PSAX systems should be configured with Node A’s in-band IP address

and a default gateway should be set to Node A’s in-band IP address.

Setting Up Connections for Hybrid Connection Configuration

Perform the following procedure to configure a hybrid connection.

Begin

1 In the hybrid connection type, Ethernet to in-band network routing as

well as ATM channel tunneling is used. Log in as root on the SUN

machine and add a routing table entry using “route add” command:

route add net In-Band network address PSAX IP address on Ethernet metric

where the in-band network address = 20.0.0.0

PSAX IP address on Ethernet = {Check Site Specific Configuration - Site

Specific Configuration - IP AddrPSAX systemess on the main router

PSAX system [ node A]}

metric = 10

Figure B-3. Hybrid Connection Configuration Diagram

PSAX

ATM PVCConnections

ATM PVC Connections

Node AMain Router

EthernetConnections

Node BRemote PSAX

NMSNode C

Node E

Node D

NMS

NMS


PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX

PSAX



255-700-447 B-11



2 In this configuration, only one PSAX system can act as the router to

channel traffic from Ethernet to the in-band network. This is the main

router PSAX system. The main router PSAX system has direct ATM con-

nections to all remote PSAX systems. (These connections may be tun-

neled through a number of switches.)

3 On the main router PSAX system, the in-band management interface(primary) should be assigned an IP address that is on a different network

than that of its Ethernet interface.

4 For all the PSAX systems except the main router PSAX system, the Ether-

net interface IP network should be different from the SUN machine’s

Ethernet interface IP network.

5 All of the NMS stations should be in the one IP network, but can be in

different subnets connected to the main router PSAX system via Ethernet

or OC3-ATM connections.

6 All the end system and router PSAX system in-band interface IP

addresses may or may not be in the same IP network. For each different

IP network, a route should be configured on each of the NMS station

(SUN machine) to use the main router PSAX system as gateway to that

network. (The metric should be set to 2).

7 The default gateway can be configured on the remote PSAX system to

use the main router PSAX system as a gateway.

8 The main router PSAX system should be configured with in-band con-

nections to each of the remote PSAX systems.

9 The remote PSAX system should have only one connection to the NMS

station’s network and the appropriate mask if the main router PSAX sys-

tem is not used as default gateway by the remote PSAX system.

10 If the main router PSAX system is used as a default gateway by the

remote PSAX system, then the remote PSAX system should have onlyone in-band connection to the main router PSAX system, the in-band IP

address.

End

Setting PVC Connections for Hybrid Connection Configuration

Assume that the VPI: VCI for connection between node A and B is VPIab:

VCIab and so on. Also assume that the Ethernet IP address of all nodes,

except node A, do not lie in the NMS stations’ network address range.

Perform the following procedure to set PVC connections for a hybrid connec-

tion.

Begin


module of the main router PSAX system (Node A) using the console

interface:


options.




B-12 255-700-447


Example:



2 Configure the primary and backup IP Address for in-band management

on the CPUn module of the intermediate router PSAX system (Node B)

using the console interface:

Example:




module of the main router PSAX system (Node C) using the console

interface:


options.

Example:




module of main router PSAX system (Node D) using the console inter-

face:


options.

Example:



5 Configure the primary IP address for in-band management on the CPUn module of main router PSAX system (Node E) using the console inter-

face:


options.

Example:



6 Set up in-band management connections on the CPUn module of Node A

to a remote PSAX system:

For setting up an in-band connection from the DS3 module to the CPUn

module, configure the DS3 module and bring the interface into service.

Select the Connection Configuration > In-Band Management IP PVC >Add Connection menu options, configure the PVC to the FORECARD.

Example:

Slot: Slot Number VPI: VPIab IP Address: 020.001.001.002

Port: 1 VCI: VCIab IP Mask: 255.000.000.000

Channel: 1



255-700-447 B-13



Slot: Slot Number VPI: VPIac IP Address: 020.001.001.003

Port: 1 VCI: VCIac IP Mask: 255.000.000.000

Channel: 1

Slot: Slot Number VPI: VPIad IP Address: 020.001.001.004

Port: 1 VCI: VCIad IP Mask: 255.000.000.000

Channel: 1

Slot: Slot Number VPI: VPIae IP Address: 020.001.001.005

Port: 1 VCI: VCIae IP Mask: 255.000.000.000

Channel: 1

7 Set up in-band management connections on the CPUn module of each of

the Nodes B,C,D,and E:

Example:

Node B

Slot:Slot Number VPI: VPIab IP Address: NMS net. addr

Port: 1 VCI: VCIab IP Mask: NMS net. mask

Channel: 1

Node C

Slot: Slot Number VPI: VPIac IP Address: NMS net. addr

Port: 1 VCI: VCIac IP Mask: NMS net. mask

Channel: 1

Node D

Slot: Slot Number VPI: VPIad IP Address: NMS net. addr

Port: 1 VCI: VCIad IP Mask: NMS net. mask

Channel: 1

Node E

Slot: Slot Number VPI: VPIae IP Address: NMS net. addr

Port: 1 VCI: VCIae IP Mask: NMS net. mask

Channel: 1

8 Verify that a routing table entry from the SUN machine’s network to net-

work 20.0.0.0 exists on the SUN machine using the netstat -nr com-mand:

9 Use ping, telnet, rlogin and ftp from the SUN machine to nodes A, B, C, E

and F to test the TCP/IP connectivity.

End




B-14 255-700-447





255-700-447 C-1

C Reference Information


This appendix contains reference information that is helpful while configur-

ing your PSAX system. The following types of information are provided:

• ATM traffic descriptors

• DSP Tone Detection Modes

• DSP Channel Reduction Availability Due to Fax Relay Mod

• Industry compliance specifications

• Connection type by interface type

• Interface type by input/output module type

• ATM service categories in the PSAX system

• Traffic shaping, usage parameter control, and virtual interface configura-

tion compatibility

• ATM Traffic Shaping Sample CPS Calculation Table

• Module transmit clock options

ATM Traffic Descriptors

Purpose of Traffic Descriptors

When you create a PVC, you can select one of several traffic descriptors byentering the desired value in the Conformance Type field on the user inter-

face windows for certain connection types. The traffic descriptor specifies

which traffic parameters are used for traffic control. It also determines the

number and type of cells that are admitted into a congested queue, and

whether high-priority cells are tagged as low-priority cells when traffic

exceeds the traffic parameter thresholds.

ATM Connections Supporting Traffic Descriptors

The traffic descriptors used in the PSAX system software are supported for

the following types of connections:

• ATM-to-ATM VCC PVC• ATM-to-ATM VPC PVC

• Bridge-to-ATM VCC PVC

• Circuit Emulation-to-ATM VCC PVC

• Frame Relay-to-ATM VCC PVC

• In-band ATM PVC

• VBR-to-ATM VCC PVC



Appendix C Reference InformationATM Traffic Descriptors

C-2 255-700-447


Types of Traffic Descriptors

The types of ATM traffic descriptors supported in the PSAX system are as fol-

lows:

• Best effort (Best-effort)

This traffic descriptor allows the system to attempt to send all cells in a“best effort” fashion, without specifying traffic parameters, similar to the

AQueMan algorithm. The PSAX system might drop some or all cells during

congestion.

• Best effort with tagging (Best-effort-tag)

This traffic descriptor allows the system to tag all CLP=0 (high priority) cells

to change them to CLP=1 (low priority) cells, and then attempt to send all

cells in a “best effort” fashion, without specifying any other traffic parame-

ters, similar to the AQueMan algorithm. The network might drop some or

all cells during congestion.

• One bucket, with no tagging for cells with both CLP bit=0 and CLP bit=1

(1B-NT-0+1)

This traffic descriptor uses the parameters one bucket, no tagging, cell losspriority (CLP)=0+1 cells (high and low priority). The PSAX system ignores

the CLP bit value and drops all cells violating the value set for the peak cell

rate (PCR).

• Two buckets, with no tagging for cells with both CLP bit=0 and CLP bit=1

(2B-NT-0+1-0+1)

This traffic descriptor uses the parameters two buckets, no tagging,

CLP=0+1 cells (high and low priority) for bucket 1, and CLP=0+1 cells

(high and low priority) for bucket 2. The PSAX system ignores the CLP bit

value for cells passing into bucket 1 and drops all cells violating the value

set for the PCR. The remainder of the cells are passed to bucket 2. The

PSAX system ignores the CLP bit value for cells passing into bucket 2, and

drops all cells violating the value set for the sustainable cell rate (SCR).• Two buckets, with no tagging for cells with both CLP bit=0+1 and CLP

bit=0 (2B-NT-0+1-0)

This traffic descriptor uses the parameters two buckets, no tagging,

CLP=0+1 cells (high and low priority) for bucket 1, and CLP=0 cells (high

priority) for bucket 2. For bucket 1, the PSAX system ignores the CLP bit

value for cells passing into bucket 1 and drops all cells violating the value

set for the PCR. For bucket 2, the system takes one of the following actions:

~ When the connection is configured for variable bit rate (VBR) traffic, the

PSAX system drops all CLP=0 cells violating the value set for the SCR in

bucket 2.

~ When the connection is configured for constant bit rate (CBR) traffic, the

PSAX system drops all CLP=0 cells violating the value set for the PCR in bucket 2.

• Two buckets, for cells with CLP bit=0 and CLP bit=0 (2B-NT-0+1-0)

This traffic descriptor uses the parameters two buckets, tagging, CLP=0+1

cells (high and low priority) for bucket 1, and CLP=0 cells (high priority)

for bucket 2. For bucket 1, the PSAX system ignores the CLP bit value for

cells passing into bucket 1 and drops all cells violating the value set for the

PCR. For bucket 2, the system takes one of the following actions:



255-700-447 C-3


Appendix C Reference InformationATM Traffic Descriptors

~ When the connection is configured for variable bit rate (VBR) traffic, the

PSAX system tags all CLP=0 cells violating the value set for the SCR to

CLP=1 in bucket 2.

~ When the connection is configured for constant bit rate (CBR) traffic, the

PSAX system tags all CLP=0 cells violating the value set for the PCR to

CLP=1 in bucket 2.

The network then might drop some or all cells during congestion.

Traffic Shaping Priorities by Configured Feature on PSAX Modules

Table C-1 shows how traffic processing is implemented on the ingress and

egress sides of ATM interfaces on those modules that support ATM interfaces.

Table C-1. Traffic Processing Options and Priority Queuing for Modules Supporting ATM Interfaces

ATM Interface ModulesInterportSharedBuffer*

Ingress TrafficProcessing Priority

Queuing†

Egress Traffic ProcessingPriority Queuing†

23N72 1-Port OC-12c/STM-4c

Multimode

23N73 1-Port OC-12c/STM-4c

Single-Mode

1UPC, AQueMan

‡

,GFR

TM 4.1 priority queuing§

,Per VC traffic shaping, or VI

support¶,

EPD**


Multimode


Single-Mode

4 UPC, TM4.1 TM 4.1 priority queuing,

Per VC traffic shaping, or VI

support¶,

EPD

20N92 1-Port STM-1 1+1 MSP

Multimode

20N93 1-Port STM-1 1+1 MSP

Single-Mode

1†† UPC, AQueMan AQueMan‡‡,


support¶,

EPD**

20N72 1-Port OC-3c 1+1 APS

Multimode

20N73 1-Port OC-3c 1+1 APS

Single-Mode

1†† UPC, AQueMan AQueMan‡‡,


support¶,

EPD**


3-Port DS3/E3 ATM Protection

No UPC, AQueMan TM 4.1 priority queuing§,


support¶,

EPD**

20N02 2-Port DS3 ATM

20N22 2-Port E3 ATM

Yes§§ AQueMan AQueMan‡,

EPD**

23N68 1-Port DS3 IMA N/A AQueMan AQueMan ‡ ,

EPD**

23N60 1-Port Channelized DS3

Multiservice

23N62 1-Port Channelized STS-1e,

T1 Format

N/A UPC, AQueMan AQueMan‡,

EPD**



Appendix C Reference InformationSPVC Connection Cause Codes for Connection Retry

C-4 255-700-447


SPVC Connection Cause Codes for Connection Retry

The SPVC connection release cause codes, displayed in the Last Rls Cause

field on all the SPVC connection configuration windows, are provided in

Table C-2. The word Yes in the “Prompts a Retry” column indicates that if the

cause code number, shown in the “Cause Code” column, is reported by the

23N34 21-Port High-Density E1

IMA

Yes UPC, AQueMan AQueMan‡,

EPD**

23N33 12-Port Medium-Density

DS1 IMAYes UPC, AQueMan AQueMan ‡ ,

EPD**


20N34 6-Port E1 IMA

20N36 6-Port Enhanced DS1/T1

Multiservice

20N56 6-Port Enhanced E1

Multiservice

Yes AQueMan AQueMan‡,

EPD**

23N64 12-Port Medium-Density

DS1 MultiserviceYes UPC, AQueMan AQueMan,

EPD23N66 21-Port High-Density E1

MultiserviceYes UPC, AQueMan AQueMan,

EPD

23N07 QuadserialYes¶¶ UPC, AQueMan AQueMan,

EPD

20N07 6-Port MultiserialYes¶¶ AQueMan AQueMan,

EPD

* This column indicates whether buffer space is shared on modules with more than one I/O port.† The traffic processing option order listed in this column indicates the processing order performed on the

traffic.‡ See the Quality of Service tables in the Reference Information appendix for more information on the

AQueMan algorithm implementation.§ The term TM4.1 refers to af-tm-0021.000, Traffic Management 4.1. This standard for priority queuing

applies to the newest PSAX modules that run at high speed. Further options are available to users within

this standard for Virtual Interfaces (see Section 4.2.2.4), traffic shaping for user-defined VCs, and the

early packet discard (EPD) function.¶ VI support and per VC traffic shaping are not supported at the same time on the same egress path on an

ATM interface. Either one or the other is supported on the same egress path.** EPD is automatically enabled on modules for AAL5 service only.†† On the OC-3c 1+1 APS and STM-1 1+1 MSP modules, users have two choices: 1) AQueMan egress pro-

cessing with UPC and Virtual Interfaces, or 2) VCs can be user-defined for traffic shaping.‡‡ On older modules , AQueMan egress processing is used.§§ These modules do not have separate buffers per port. All other modules have separate buffers per port

except the 1-port modules.¶¶ RS232, RS449, EIA530, V.11.

Table C-1. Traffic Processing Options and Priority Queuing for Modules Supporting ATM Interfaces

ATM Interface ModulesInterportSharedBuffer*

Ingress TrafficProcessing Priority

Queuing†

Egress Traffic ProcessingPriority Queuing†



255-700-447 C-5



equipment at the far (remote) end, the PSAX system will try to establish the

connection again up to the number of times specified in the Retry Limit field

on the SPVC connection configuration windows. The ATM Forum UNI and

Frame Relay Forum FRF.4 standards use many (but not all) of the same

release cause codes, and these standards reference ITU-T standards for many

of the release cause codes.

Table C-2. Connection Release Cause Codes for SPVCs

ReleaseCauseCode

DescriptionPromptsa Retry

ReferencedStandard

1 Unallocated (unassigned) number. The called party number is

not currently assigned. As a result, the called party cannot be

reached.

No ITU-T Q.850

2 No route to specified transit network. The equipment sending

this cause code received a request to route the call through an

unknown transit network. The transit network is unknown

to the equipment because it does not exist or does not serve

the equipment.

No ITU-T Q.850

3 No route to destination. The network through which the call

was routed does not serve the destination. As a result, the

called party cannot be reached.

Yes ITU-T Q.850

10 VCC is unacceptable. The VPI/VCI is unacceptable to the

sending entity for use in the call.

No ATM Forum UNI

3.0/3.1

16 Normal call clearing. No ITU-T Q.850

17 User is busy. The called party is unable to accept another call

because the user-busy condition has been encountered.

Yes ITU-T Q.850

18 No user is responding. A called party did not respond to a call

establishment message with either an alerting or connect

indication within a designated time period.

No ITU-T Q.850

21 Call was rejected. Although the equipment sending this cause

code is neither busy nor incompatible, the equipment sending

this cause code does not want to accept the call. The cause

can be generated by the network to indicate that the call

might have been cleared as a result of a supplementary ser-

vice constraint.

No ITU-T Q.850

22 Number was changed. The number of the called party is no

longer assigned. A new number must be used to call the

called party.

No ITU-T Q.850

23 User rejects all calls with calling line identification restriction

(CLIR). The called party returns this cause code when the call

comes in without calling party number information and thecalled party requires this information.

No ATM Forum UNI

3.0/3.1

27 Destination is out of order. The user cannot reach the destina-

tion because the interface to the destination is not function-

ing properly; that is, a signaling message could not be deliv-

ered to the destination.

Yes ITU-T Q.850




C-6 255-700-447


28 Number format is not valid (address incomplete). The called

party is unreachable because the number of the called party isnot in the proper format or it is not complete.

No ITU-T Q.850

30 Response to STATUS ENQUIRY. A STATUS message was sent

in response to receipt of a STATUS ENQUIRY message.

Yes ITU-T Q.850

31 Normal unspecified. A normal event occurred for which no

other cause applies. As a result, the event is normal but

unspecified.

No ITU-T Q.850

32 Too many pending ADD PARTY requests currently exist. Yes ATM Forum

PNNI 1.0

35 Requested VPCI/VCI is not available. The SPVC attempted to

use a VPCI/VCI that is unavailable.

Yes ITU-T Q.2610

36 VPCI/VCI assignment failure. A VPCI/VCI could not beassigned to the SPVC. Yes ITU-T Q.2610

37 User cell rate is unavailable. The requested cell rate is

unavailable for the SPVC.

Yes ITU-T Q.2610

38 Network is out of order (not used in this implementation

agreement). The problem will probably last a long period of

time; that is, an immediate retry of the call is not likely to suc-

ceed.

Yes ITU-T Q.850

41 Temporary failure. The problem will probably last a short

period of time; that is, an immediately retry of the call has a

good chance to succeed.

Yes ITU-T Q.850

43 Access information was discarded. The network failed to

deliver access information to the remote user (for example,

user-to-user, low-layer compatibility, high-layer compatibil-

ity, or subaddress).

Yes ITU-T Q.850

44 Circuit is unavailable. The requested circuit or channel is not

available.

No ITU-T Q.850

45 No VPCI/VCI is available. A VPCI/VCI is not available for the

SPVC.

Yes ITU-T Q.2610

47 Resource is unavailable or unspecified. A resource is unavail-

able, and no other cause code exists to report this event.

Yes ITU-T Q.850

49 Quality of service is unavailable. The requested QoS class is

unavailable for the SPVC.

No ITU-T Q.850

51 User cell rate is unavailable. The requested cell rate isunavailable for the SPVC.

Yes ATM Forum UNI3.0/3.1

53 PGL was changed. The call was cleared due to a change in the

peer group leader (PGL).

No ATM Forum

PNNI 1.0

57 Bearer capability is not authorized. The SPVC user requested

a bearer capability for which the user is not authorized.

No ITU-T Q.850

58 Bearer capability is not presently available. The SPVC user

requested a bearer capability that is not available at this time.

No ITU-T Q.850

Table C-2. Connection Release Cause Codes for SPVCs (Continued)

ReleaseCauseCode


ReferencedStandard



255-700-447 C-7



63 Service or option is unavailable or unspecified. A service or

option is unavailable, and no other cause code exists to reportthis event.

No ITU-T Q.850

65 Bearer capability is not implemented. The equipment that

generated this cause code does not support the requested

bearer capability.

No ITU-T Q.850

73 Combination of traffic parameters is not supported. No ATM Forum UNI

3.0/3.1

78 AAL parameters cannot be supported. No ITU-T Q.2610

81 Call reference value is not valid. The equipment that sends

this cause code has received a message with a call reference

that is not currently in use on the user-network interface.

No ITU-T Q.850

82 Identified channel does not exist. The equipment sending thiscause code received a request to use a channel that was not

activated on the call interface. For example, if a user sub-

scribed to those channels on a primary rate interface num-

bered from 1 to 12, this cause code would be generated if the

user equipment or the network attempts to use channels 13

through 23.

No ITU-T Q.850

88 Incompatible destination. The equipment sending this cause

code received a request to establish a call with low-layer com-

patibility, or other compatibility attributes that cannot be

accommodated, for example, data rate.

No ITU-T Q.850

89 Endpoint reference is not valid. The equipment sending this

cause code received a message with an endpoint referencethat is currently not in use on the user-network interface.

No ATM Forum UNI

3.0/3.1

91 Transit network selection is not valid. A transit network iden-

tification was received that is not formatted correctly. Correct

formats are defined in the standard, Q.931, Annex C.

No ITU-T Q.850

92 Too many pending ADD PTY requests were generated on the

SPVC. This condition occurs when the calling party sends an

ADD PTY request, but the network cannot accept another

ADD PTY message because its queues are full. This condition

is temporary.

No ATM Forum UNI

3.0/3.1

93 AAL parameters cannot be supported. No ITU-T Q.2610

95 Unspecified message is not valid. This cause code reports a

message event that is not valid when no other message causecode that is not valid applies.

No ITU-T Q.850

96 Mandatory information element is missing. The equipment

sending the cause code received a message that is missing a

mandatory information element.

No ITU-T Q.850


ReleaseCauseCode


ReferencedStandard




C-8 255-700-447


97 Message type is nonexistent or not implemented. The equip-

ment sending the cause code received one of the followingmessage types:

• Not defined

• Defined but not implemented by the equipment sending

the cause code

No ITU-T Q.850

99 Information element is nonexistent or not implemented. The

equipment sending the cause code received a message that

includes information elements or parameters that meet one

of the following criteria:

• Not recognized because the elements or parameters are not

defined

• Defined but not implemented by the equipment sending

the cause codeThe cause code indicates that the elements or parameters

were discarded. However, the information element is not

required to be present in the message so that the equipment

sending the cause code can process the message.

No ITU-T Q.850

100 Information element content is not valid. The equipment

sending this cause code received an information element that

the equipment has implemented, but one or more fields in

the information element are coded in a way that has not been

implemented.

No ITU-T Q.850

101 Message type is not compatible with call state. A message was

received that is incompatible with the call state.

Yes ITU-T Q.850

102 Recovery on timer expiration. A procedure has been initiated

by the expiration of a timer that is related to error handling

procedures.

Yes ITU-T Q.850

104 Message length is not correct. No ATM Forum UNI

3.0/3.1

111 Unspecified protocol error. A protocol error occurred for

which no defined protocol error exists.

No ITU-T Q.850

127 Optional information element content error (nonstandard).

This cause code indicates the occurrence of internetworking

with a network that does not provide cause codes for actions

that it takes. The precise cause for any message that is sent

cannot be determined.

No ITU-T Q.850

128 Next node is unreachable. No ATM Forum

PNNI 1.0

160 DTL transit is not my node ID. No ATM Forum

PNNI 1.0


ReleaseCauseCode


ReferencedStandard



255-700-447 C-9


Appendix C Reference InformationDSP Tone Detection Modes

DSP Tone Detection Modes

DSP tone detection modes are selected through the Circuit Emulation-to-

ATM VCC PVC Connection window. These modes are described in Table C-3.

DSP Channel Reduction Availability Due to Fax Relay Mode

Table C-3. DSP Tone Detection Modes* and Associated Processing Performed

Tone Mode Processing Performed

Disabled Ignores fax tones and modem tones

Bypass If a fax tone or modem tone is received, the firmware switches to G.711 mode

(64 Kbps) and bypasses echo cancellation, if enough bandwidth is available.

Fax Relay If a fax tone is received, the firmware switches to a channel configured for

FaxRelayMode and performs fax demodulation / remodulation. If a modem

tone is received, the firmware ignores it

Fax Relay/Modem

Bypass

If a fax tone is received, the firmware switches to a channel configured for

FaxRelayMode and performs fax demodulation/remodulation. If a modem

tone is received, the firmware switches to G.711 mode (64 Kbps) and

bypasses echo cancellation, if enough bandwidth is available.

* Modes selected on the Circuit Emulation-to-ATM VCC PVC Connection window.

Table C-4. Channel Reduction Availability Caused by Fax Relay Connections vs.Voice Processing Connections on a DSP2C Module

Numberof DSPsfor FaxRelay

Total ConnectionsAssigned for

Fax Relay

Percent of All DSPConnections

Assigned for FaxRelay

Remaining Voice Processing Available

Channels*

1 4 3% 1242 8 6% 120

3 12 9% 116

4 16 13% 112

5 20 16% 108

6 24 19% 104

7 28 22% 100

8 32 25% † 96

9 36 28% 92

10 40 31% 88

11 44 34% 84

12 48 38% 80

13 52 41% 76

14 56 44% 72

15 60 47% 68

16 64 50% 64



Appendix C Reference InformationIndustry Compliance Specifications

C-10 255-700-447


Industry Compliance Specifications

Compliance specifications for the PacketStar ® PSAX Multiservice Media Gate-

ways and the I/O and server modules are contained in Table C-5.

* For every fax transmission call, both the originally assigned DSP resource, plus

the fax relay DSP resource, are consumed for the duration of the call. Thus,

the total remaining DSP connections is reduced by twice the number of con-

nections using fax mode service.† Utilization of DSP resources for fax relay above 25% is not considered realistic

for most service provider environments. If this value exceeds 25%, then the

number of available DSP connections for pure voice mode calls is reduced to

less than 50% of connections available on the DSP2C module.

Table C-5. Industry Compliance Specifications

Feature Name/Product Name Specification Title Notes

Integrated Local ManagementInterface (ILMI)

ILMI over PNNI

Channelized DS3, Channelized

STS-1e, DS1 IMA, DS3 IMA, E1

IMA, DS3 ATM, E3 ATM,

Enhanced DS1, Enhanced E1,

High-Density E1, High Speed,

Medium-Density DS1, Multiser-

ial, OC-3c MM/SM APS, STM-1

MM/SM MSP, OC-12c/STM-4c,

1-Port OC-3/STM-1 Unst.

CES/ATM MM/SM (STM1-ATM

Operating Mode only), and

Quadserial modules

af-ilmi-0065.000Integrated Local Management

Interface (ILMI)

DS1 IMA, DS3 IMA, 1-Port

OC-3/STM-1 Unst. CES/ATM

MM/SM modules

af-phy-0016.000

DS1 Physical Layer Specification

Channelized DS3 module af-phy-0054.000

DS3 Physical Interface Specifica-

tion

E1 IMA, 1-Port Chan OC-

3/STM-1 Unstruct. CES/ATM

MM/SM modules

af-phy-0064.000

E1 Physical Layer Specification

DS1 IMA, DS3 IMA, and E1IMA modules

af-phy-0086.000

Inverse Multiplexing over ATM

(IMA), Version 1.0

DS1 IMA, DS3 IMA, E1 IMA,

1-Port Chan OC-3/STM-1

Unstruct. CES/ATM MM/SM

modules

af-phy-0086.001

Inverse Multiplexing over ATM

(IMA), Version 1.1

Obsoletes af-phy-0086.000 but

PSAX is compatible with both

versions



255-700-447 C-11






Enhanced DS1, EnhancedE1,High-Density E1, High

Speed, Medium-Density DS1,

OC-3c MM/SM APS, STM-1


OC-12c/STM-4c, 1-Port OC-

3/STM-1 Unst. CES/ATM

MM/SM (STM1-ATM Operat-

ing Mode only), and Quadserial

modules

af-pnni-0026.000

Interim Inter-Switch Signaling

Protocol (IISP)

ATM Maintenance Mode

ATM PNNI 1.0 interface

ETSI ISDN SupportIn-band Management SVC

Soft Permanent Virtual Circuits

(SPVCs)

SPVC Support for CES Channel-

ized DS3, Channelized STS-1e,

DS1 IMA, DS3 IMA, E1 IMA,

DS3 ATM, E3 ATM,

DSP2A/B/C/D Voice Servers,

Enhanced DS1, High-Density

E1, Medium-Density DS1, OC-

3c MM/SM APS, STM-1

MM/SM MSP, OC-12c/STM-4c,1-Port OC-3/STM-1 Unst.

CES/ATM MM/SM (STM1-ATM

Operating Mode only), and

Quadserial modules

af-pnni-0055.000

Private Network-Network Inter-

face (PNNI)

SPVCs- Annex C: Soft PVC Pro-

cedures for circuit emulation,

frame relay, and terminal emu-

lation

Annex G, mandatory require-

ments

ATM Maintenance Mode

In-band Management SVC

af-pnni-0066000

Private Network-Network Inter-

face (PNNI) Addendum (Soft

PVC)




Enhanced DS1, Enhanced E1,High-Density E1, High Speed,

Medium-Density DS1, Multiser-

ial, OC-3c MM/SM APS, STM-1



Unstruct. CES/ATM MM/SM,

and Quadserial modules

af-sig-0061.000

User-Network Interface (UNI)

4.0 Signaling Specification

Table C-5. Industry Compliance Specifications (Continued)





C-12 255-700-447


Traffic Management (UPC Sup-

port)

Route Server-to-ATM Inter-

working

af-tm-0121.000

Traffic Management, Usage

Parameter Control

Route Server-to-ATM Inter-

working: Section 5.5




Enhanced DS1, Enhanced

E1,High-Density E1, High

Speed, Medium-Density DS1,

Multiserial, OC-3c MM/SM

APS, STM-1 MM/SM MSP, OC-

12c/STM-4c, OC-12c/STM-4c,

Ch OC3 Unstruct. CES/STM1

ATM, and Quadserial modules

af-uni-0010.001

User-Network Interface (UNI)

3.0

PSAX 1000, PSAX 1250,PSAX 2300, and PSAX 4500

Multiservice Media Gateways

OC-12c/STM-4c, 1-Port Chan

OC-3/STM-1 Unstruct.

CES/ATM, 4-Port OC-3c/STM-1

MM/SM

af-uni-0010.002User-Network Interface (UNI)

3.1

GR-303 DLC Services

VTOA AAL2 Trunking Narrow-

band Services

af-vmoa-0145.000

Voice and Multimedia Over

ATM–Loop Emulation Service

Using AAL2

Carrier Group AIS Alarm

I.610 OAM F4/F5 Processing

(remote defect indication [RDI]

and alarm indication signal

[AIS])


STS-1e, Channelized DS3/STS-

1e CES, DS1 IMA, DS3 IMA, E1

IMA, Enhanced DS1, Enhanced

E1, High-Density E1, Medium-

Density DS1, Multiserial, Quad-

serial and Unstructured DS3/E3

CES modules

af-vtoa-0078.000

Circuit Emulation Service 2.0

Includes 56 (DS1), Nx64 (DS1,

E1)





255-700-447 C-13




STS-1e, Enhanced DS1, and

DSP2 x Voice Server modules

af-vtoa-0085.000

(DBCES) Dynamic Bandwith

Utilization in 64 Kbps Time Slot

Trunking Over ATM—Using Cir-cuit Emulation Service (CES)

• AAL1 Trunking CCS (Q.931)

• AAL1 Trunking CCS

(Q.931/QSIG), AAL1 Trunk-

ing CAS

AAL2 Trunking af-vtoa-0089.000

ATM Trunking Using AAL1 for

Narrow Band Services V1.0




[AIS])

af-vtoa-0098.000

VTOA AAL1 Trunking Services

Quadserial af-vtoa-0113.000

ATM Trunking Using AAL2

af-vtoa-0119.000

Low Speed Circuit Emulation

Service

PSAX 1000, PSAX 1250,

PSAX 2300, and PSAX 4500


ANSI T1.101

Telecommunications - Synchro-

nization Interface Standard

Unstructured DS3/E3 CES mod-

ule

ANSI T1.102

DS3 Electrical Interface Charac-teristics

CSU/DSU loopback

Enhanced DS1, DS3 ATM, OC-

3c MM/SM APS modules

ANSI T1.105

Synchronous Optical Network-

Basic Description



modules. PSAX 1000,

PSAX 1250, PSAX 2300, and

PSAX 4500 Multiservice Media

Gateways

ANSI T1.105.01, Synchronous

Optical Networks, Automatic

Protection Switching

DS1 IMA and E1 IMA modules ANSI T1.107

T1.107a–DS1 and DS3 Format

Specifications

DS1 IMA, DSP2 x Voice Servers,

and E1 IMA modules

ANSI T1.231

DS1/DS3 Performance Monitor-

ing Characteristics






C-14 255-700-447


GR-303 DLC Services ANSI T1.401

Interface Between Carriers and

Customer Installations- Analog

Voice Grade Switched AccessLines Using Loops-start and

Ground-start Signaling

CSU/DSU loopback

Facsimile Demodula-

tion/Remodulation


band Services

DS1 IMA, E1 IMA, Enhanced

DS1, DS3 ATM, DSP2 x Voice

Servers, and OC-3c MM/SM

modules

ANSI T1.403

Network-to-Customer Installa-

tion: DS1 Metallic Interface

CSU/DSU loopback

Enhanced DS1, DS3 ATM,

OC-3c MM/SM modules

ANSI T1.404


tion-DS3 Metallic Interface


Network-to-customer Installa-

tion Interfaces- Direct-inward

Dialing Analog Voice Grade

Switched Access Using Loop-

reverse Battery Signaling



tion Interfaces- Analog VoiceGrade Special Access Lines Using

E&M Signaling

GR-303 DLC Services


band Services

ANSI T1.602

Integrated Services Digital Net-

work (ISDN)- Data-link Layer

Signaling Specification for

Application at the User-Network

Interface

GR-303 DLC Services


band Services

ANSI T1.607; T1.607a

Digital Subscriber Signaling Sys-

tem Number 1 (DSS1)-Layer 3

Signaling Specification for Cir-cuit-switched Bearer Services

T1.607a is for GR-303 DLC Ser-

vices

DS3 Frame Relay module CCITT G.703

Physical/Electrical Characteris-

tics of Hierarchical Digital Inter-

faces





255-700-447 C-15



DS3 Frame Relay module CCITT G.704

Synchronous Frame Structures

Used at Primary and Secondary

Hierarchical Levels

DSL Forum TR 017

ATM over ADSL Recommenda-

tions

Multiserial and Quadserial mod-

ule

EIA-232

Electrical, mechanical, and func-

tional standards for communica-

tion between computers, termi-

nals and modems

High Speed, Multiserial, and

Quadserial modules

EIA-449

Faster version of RS-232-C;

capable of longer cable runsGR-303 DLC Services


band Services

EIA-464-B

Requirements for Private

Branch Exchange (PBX) Switch-

ing Equipment

High Speed, Multiserial, and

Quadserial modules

EIA-530

Defines mechanical/electrical

interfaces between DTEs and

DCEs that transmit serial binary

data

ETSI 300 012-1

Integrated Services Digital Net-work (ISDN); Basic User-Net-

work Interface; Layer 1 Specifi-

cation and Test Principles

ETSI ISDN Support ETSI 300 125 Annex C: Soft PVC Procedures

V5.2 ETSI 300 324-1

V5.1 Interface for the Support of

Access Network (AN) Part 1:

V5.1 Interface Specification

ITU-T G. 964 and G.965 are

functionally equivalent to ETSI

EN 300 324-1 and ETSI EN 300

347-1 respectively. In cases

where detail differences exist

between the ITU-T and ETSI

versions of the specifications,the ETSI versions of the specifi-

cations should apply.






C-16 255-700-447


V5.2 ETSI 300 347-1

V5.2 Interface for the Support of

Access Network (AN) Part 1:

V5.2 Interface Specification



EN 300 324-1 and ETSI EN 300

347-1 respectively. In caseswhere detail differences exist


versions of the specifications,

the ETSI versions of the specifi-


ETSI 300 402-1


work (ISDN), Digital Subscriber

Signaling System No. 1 (DSS1)

Protocol; Data Link Layer, Part

1: General Aspects

ETSI 300 402-2Integrated Services Digital Net-

work (ISDN); Digital Subscriber

System No. 1 (DSS1) protocol;

Data Link Layer, Part 2: General

Protocol Specification

PSAX 1000, PSAX 1250,



FR-796, Reliability and Quality

Generic Requirements


STS-1e, DS3 Frame Relay,


High-Density E1, Medium-Den-sity DS1, Multiserial and Quad-

serial modules

FRF.1.1

User-to-Network (UNI) Imple-

mentation Agreement




High-Density E1, Medium-Den-

sity DS1, Multiserial and Quad-

serial modules

link management interface

(LMI) services between two net-

work-network interface (NNI)

services

FRF.2.1

Frame Relay Network-to-Net-

work (NNI) Implementation

Agreement

LMI services between two NNI

services





sity DS1, Quadserial, and Route

Server modules

FRF.5

Frame Relay ATM/PVC Network

Internetworking Implementa-

tion Agreement





255-700-447 C-17



In-band Management



Enhanced DS1, Enhanced E1,High-Density E1, Medium-Den-

sity DS1, Multiserial, Quadserial,

and Route Server modules

FRF.8

Frame Relay ATM/PVC Service

Internetworking Implementa-

tion Agreement



modules

FRF-796, Reliability and Qual-

ity Generic Requirements



modules. PSAX 1000,

PSAX 1250, PSAX 2300, and

PSAX 4500 Multiservice Media

Gateways

GR-63-CORE

Network Equipment Building

Standards (NEBS): Physical Pro-

tection

Tones and Announcements

Server module

GR-246-CORE

Signalling System Number 7

for test capability

Channelized STS-1e, Channel-

ized DS3/STS-1e CES OC-3c

APS, OC-12c/STM-4c 1+1

APS/MSP MMSM modules

GR-253-CORE

SONET Transport Systems Revi-

sion 1, Dec 1997: Common

Generic Criteria

GR-303 DLC Services

Channelized DS3/STS1-e CES

module

GR-303-CORE

Integrated Digital Loop Carrier

System Generic Requirements,

Objectives, and Interface

D4 Support Stratum DS1 BITSInterfaces

Stratum 3–4 modules

GR-436-CORE

Digital Network Synchroniza-

tion Plan

Does not include the (ANSIT1.101-compliant Stratum 3–4

module, COMCODE

108484890)

OC-3c APS modules GR-474-CORE

Alarm and Control for Network

Elements

Section 8.3.1, Trouble Notifica-

tions for Protection Switches



1-Port OC-3c APS, 1-Port OC-

12c/STM-4c 1+1 APS/MSP

MM/SM, and DSP2 x Voice

Server modules

PSAX 1000, PSAX 1250,



GR-499-CORE

Common Requirements,

DSP2 x : Common Requirements

for TSGR






C-18 255-700-447


D4 Support Stratum DS1 BITS

Interfaces




GR-518-CORE

LSSGR: Synchronization, Sec-

tion 18

Stratum: Does not include the

ANSI T1.101-compliant Stra-

tum 3–4 module, COMCODE

108484890

DSP2 x Voice Server modules DSP2 x : GR-820-CORE

OTGR Section 5.1 Generic

Transmission Surveillance


STS-1e, Enhanced DS1, Medium

Density DS1, and Tones and

Announcements Server mod-

ules

GR-822-CORE

OTGR Section 6.3: Network

Maintenance: Access and Testing

- Switched Circuits, POTS Loops,

and Public Packet Switched Net-

work (PPSN) (a module of

OTGR, FR-439)

For milliwatt test refer to Sec-

tion 5.2.1.2 T1.207a

For type 105 termination test,

refer to Section 5.2.5 T1.207a

and Section 6.1.2.3

For type 108 termination test,refer to Section 5.3.1 T1.207a

and Section 6.1.2.4



modules.

PSAX 1000, PSAX 1250,



GR-1089-CORE (NEBS)

Electromagnetic Compatibility

and Electrical Safety—Generic

Criteria for Network Telecom-

munications Equipment

D4 Support Stratum DS1 BITS

Interfaces




GR-1244-CORE

Clocks for Synchronized

Networks: Common Generic

Criteria

Stratum: Does not include the

ANSI T1.101-compliant Stra-

tum 3–4 module, COMCODE

108484890




[AIS])



OC-3c APS modules

PSAX 1000, PSAX 1250,



GR-1248-CORE

Generic Requirements for oper-

ations of ATM Network Ele-

ments

For OAM, refer to Table 4-1

OAM Type/Function

For OC x APS modules, refer to

Section 6.3 ATM APS Protection

Switching




[AIS])

OC-3c APS modules

GR-2980-CORE

General Criteria for ATM Layer

Protection Switching Mecha-

nism

Coordination protocol cell is

used for automatic protection

switching (APS)





255-700-447 C-19



OC-3c APS modules SR-NWT-001756

Automatic Protection Switching

for SONET, issue 1, October

1990




[AIS])

TR-NWT-00170

Bellcore Digital Cross-Connect

System Generic Requirements

and Objectives

Spanning Tree Protocol

Ethernet module

IEEE 802.1D

Media Access Control (MAC)

Bridges

Ethernet module IEEE 802.3

Carrier Sense Multiple Access

with Collision Detection

(CSMA/CD) Access Method andPhysical Layer Specifications

Route Server module IETF RFC 792

Internet Control Message Proto-

col


Routing Information Protocol

IETF RFC 1157

Simple Network Management

Protocol (SNMP) Version 1.0


Unstruct. CES/ATM MM/SMmodules.

RFC 1213 - Management Infor-

mation Base for NM: MIBII

DS1 IMA, E1 IMA, Enhanced

DS1, and Enhanced E1 modules

IETF RFC 1406

Definitions of Managed Objects

for the DS1 and E1 Interface

Types

DS3 IMA, DS3 ATM, and E3

ATM modules

IETF RFC 1407


for the DS3 and E3 Interface

Types


Unstruct. CES/ATM MM/SMmodules.

RFC 1414 - Identification MIB

Ethernet Bridging

In-band Management

4-Port Ethernet, Ethernet, and

Route Server modules

IETF RFC 1483

Multi-Protocol Encapsulation

and Layer 2 Bridging Service

• Inverse ARP not supported

• IETF RFC 1483 was replaced

by IETF RFC 2684






C-20 255-700-447



Multiprotocol Interconnect over

Frame Relay

IETF RFC 1490 was replaced by

IETF RFC 2427

IETF RFC 1595


for the SONET/SDH Interface

Types

IETF RFC 1661

Point-to-Point Protocol

IETF RFC 1662

PPP in HDLC-like Framing

4-Port OC-3c/STM-3 MM/SM

module

IETF RFC 1695

ATM Statistics/MIB

IETF RFC 1700Assigned Numbers


RIP Version 2


Trivial File Transfer Protocol

Blocksize Option

Section 3.1 (authentication) and

3.5 (multicasting)only


A Method for the Transmission

of IPv6 Packets over Ethernet

Networks

1-Port Chan OC-3/STM-1Unstruct. CES/ATM MM/SM

modules.

RFC 2233 - The InterfacesGroup MIB using SMIv2

Route Server module

Enhanced Router module

IETF RFC 2427

Multiprotocol Interconnect over

Frame Relay

Obsoletes RFC 1490



modules.

IETF RFC 2495 - Definitions of

Managed Objects for the DS1/E1

Interfaces



modules.


Managed Objects for ATM Man-

agement



modules.


Managed Objects for the

SONET/SDH Interface


Transmission of IPv6 Packets

over Ethernet Networks

Obsoletes RFC 1972





255-700-447 C-21



Ethernet Bridging

4-Port Ethernet, Ethernet,

Enhanced Router, and Route

Server modules

IETF RFC 2684

Multiprotocol Encapsulation

over ATM Adaptation Layer 5

Obsoletes RFC 1483

RFC 2685 (VPN identification)

not supported

ITU-T E.164

Overall Network Operation,

telephone service, service opera-

tion, and human factors: Opera-

tion, numbering, routing and

mobile services

International operation- Num-

bering plan of the international

telephone service

DSP2C/D Voice Server modules

Fax/modem detection

ITU-T G.164

Transmission Systems and

Media Apparatus Associated

with Long-Distances Telephone

Circuits and Other Terminal

Equipment: Echo Suppressors

DSP2A/B/C/D Voice Server

modules

Echo cancellation (general)

ITU-T G.165

General Characteristics of Inter-

national Telephone Connec-

tions and International Tele-

phone Circuits: Echo Cancellers

ITU-T G.702

General Aspects of Digital Trans-

mission Systems— TerminalEquipment: Digital Hierarchy Bit

Rates

PSAX 1000, PSAX 1250,



ITU-T G.703

Physical/Electrical Characteris-

tics of Hierarchical Digital Inter-

faces

1.544 Mbps, 2.048 Mbps,

44.736 Mbps; includes channel-

associated signaling (CAS)

ABCD in-band signaling

ITU-T G.704

Synchronous frame structures

used at 1544, 6312, 2048, 8488

and 44 736 Kbps hierarchical

levels

ITU-T G.706

Frame alignment and cyclic

redundancy check (CGC) proce-

dures relating to basic frame

structures defined in Recom-

mendation G.704






C-22 255-700-447




modules.

ITU-T G.707


Media—Digital transmission sys-

tems— Terminal equipment—General: Network node interface

for the synchronous digital hier-

archy (SDH)


modules

64 Kbps fax encoding

ITU-T G.711


mission Systems Terminal

Equipment: Pulse Code Modula-

tion (PCM) of Voice Frequencies


modules

Voice compression (16, 24, 32,

40 Kbps) and tandem encoding

ITU-T G.726


mission Systems Terminal

Equipment: 40, 32, 24, 16 Kbps

Adaptive Differential Pulse Code

Modulation (ADPCM)

DSP2 x Voice Server modules

Annex A: Voice compression

(8 Kbps)

Annex B: Silence suppression

ITU-T G.729


mission Systems: Coding of

Speech at 8 Kbps Using Conju-

gate-Structure Algebraic-Code-

Excited Linear-Prediction (CS-

ACELP)

ITU-T G.732

General Aspects of Digital Trans-mission Systems Terminal

Equipments: Characteristics of

Primary PCM Multiplex Equip-

ment Operating at 2048 Kbit/s

ITU-T G.736


mission: Characteristics of a

Synchronous Digital Multiplex

Equipment Operating at 2048

kbits/sec

ITU-T G.751

Digital multiplex equipmentsoperating at the third order bit

rate of 34 368 kbit/s and the

fourth order bit rate of 139 264

Kbps and using positive justifica-

tion





255-700-447 C-23



PSAX 1000, PSAX 1250,


Multiservice Media Gateways.

1-Port Chan OC-3/STM-1Unstruct. CES/ATM MM/SM,

and OC-3c APS MM/SM mod-

ules.

ITU-T G.783


Media, Digital Systems and Net-

works— Digital TransmissionSystems—Terminal Equip-

ment—Principal Characteristics

of Multiplexing Equipment for

the Synchronous Digital Hierar-

chy: Characteristics of Synchro-

nous Digital Hierarchy (SDH)

Equipment Functional Blocks

PSAX 1000, PSAX 1250,



ITU-T G.803

Architecture of Transport Net-

works Based on Synchronous

Digital Hierarchy (SDH) 1997

DS3 ATM, Enhanced DS1, andEnhanced E1 modules

ITU-T G.804

ATM cell mapping into Plesio-

chronous Digital Hierarchy

(PDH)

PSAX 1000, PSAX 1250,



ITU-T G.812

Timing Requirements of Slave

Clocks Suitable for Use as Node

Clocks in Synchronization Net-

works, June 1998

PSAX 1000, PSAX 1250,



ITU-T G.813

Timing Characteristics of SDH

Equipment Slave Clocks, Aug.1996

ITU-T G.823

The control of jitter and wander

within digital networks which

are based on the 2048 Kbps

hierarchy

Includes Multiplex Section Pro-

tection (MSP)

ITU-T G.832


Media, Digital Systems and Net-

works— Digital transmission

systems—Digital networks—

Network capabilities and func-tions: Transport of SDH Ele-

ments on PDH Net-

works—Frame and Multiplexing

Structures

STM-4c module ITU-T G.837






C-24 255-700-447


STM-4c module ITU-T G.841, Annex A

Types and Characteristics of SDH

Network Protection Architecture

Issue 10/98

Intra-office and short haul ITU-T G.957

Optical interfaces for equipment

and systems relating to the syn-

chronous digital hierarchy

Long haul not supported

ITU-T G.964

V-Interfaces at the Digital Local

Exchange (LE)- V5.1 Interface

(based on 2048 Kbps) for the

Support of Access Network (AN)



EN 300 324-1 and ETSI EN 300





the ETSI versions of the specifi-cations should apply.

ITU-T G.965

V-Interfaces at the Digital Local

Exchange (LE) - V5.1 Interface

(based on 2048 Kbps) for the

Support Of Access Network

(AN)



EN 300 324-1 and ETSI EN 300





the ETSI versions of the specifi-


ITU-T G.991.2

Draft: Single-pair high speed

digital subscriber line (SHDSL)

transceivers

ITU-T G.992.1

Asymmetric Digital Subscriber

Line (ADSL) transceivers

ITU-T G.992.2

Splitterless Asymmetric Digital

Subscriber Line (ADSL) trans-

ceivers

ITU-T H.248

H.248 Base Root Package

Annex E.2

ITU-T I.121


work (ISDN) General Structure

and Service Capabilities: Broad-

band Aspects of ISDN





255-700-447 C-25



ITU-T I.150

B-ISDN ATM Functional charac-

teristics

Enhanced DS1 and Enhanced

E1 modules

ITU-T I.233

Frame Mode Bearer Services

ITU-T I.321


work (ISDN) Overall Network

Aspects and Functions, ISDN

User-Network Interfaces: B-

ISDN Protocol Reference Model

and its Application

ITU-T I.356

B-ISDN ATM layer cell transfer

performance

ABR not supported




[AIS])



modules.

ITU-T I.361

B-ISDN ATM Layer Specification

Virtual Private LAN Services

(VPLS) over ATM



modules

ITU-T I.363

B-ISDN ATM Adaptation Layer

specification

Only AAL1, AAL2, and AAL5

are supported

DSP2 x Voice Server modules ITU-T I.363.1


specification: Type 1 AAL

Multiplexing support for DSP2 x

Voice Server modules

ITU-T I.363.2



ITU-T I.363.5




band Services

ITU-T I.366.1

Segmentation and Reassembly

Service Specific Convergence

Sublayer for the AAL type 2






C-26 255-700-447


Facsimile Demodula-

tion/Remodulation


band ServicesDSP2C/D Voice Server modules

ITU-T I.366.2

AAL Type 2 Specification on

Convergence Sublayer for Nar-

row-band Services.

Annex M




High-Density E1,Medium-Den-

sity DS1, Multiserial, and Quad-

serial modules

ITU-T I.370

Congestion Management for

ISDN Frame Relay Bearing Ser-

vice


STS-1e, DS3 Frame Relay, High-

Density E1, Medium-Density

DS1, Multiserial and Quadserial

modules

ITU-T I.371

Traffic control and congestion

control in B-ISDN

ABR not supported

ITU-T I.372


work (ISDN) Overall Network

Aspects and Functions: Frame

Relaying Bearer Service Net-

work-to-Network Interface

Requirements

ITU-T I.413


work (ISDN) User-Network

Interfaces: B-ISDN User-Net-

work Interface

ITU-T I.430

Basic User-Network Interface -

Layer 1 Specification



1e CES, DS3 Frame Relay,



sity DS1, Multiserial, and Quad-

serial modules

ITU-T I.431


work (ISDN) User-Network

Interfaces: Primary Rate User-

Network Interface—Layer 1

Specification

Scrambling, header error control(HEC) processing, cell delinea-

tion

ITU-T I.432B-ISDN User-Network Inter-

face—Physical layer Specifica-

tion

ITU-T I.432.1

B-ISDN User-Network Inter-

face: Physical Layer Specifica-

tion- General Characteristics





255-700-447 C-27





modules.

ITU-T I.432.2

B-ISDN User-Network- Physical

Layer Specification: 155 520

Kbps and 622 080 Kbps opera-tion

ITU-T I.432.3

B-ISDN User-Network Inter-

face: Physical Layer Specifica-

tion for 1.544 Mbps and 2.048

Mbps

ITU-T I.432.4

B-ISDN User-Network- Physical

Layer Specification: 51 840 Kbps

Operation

Carrier Group AIS AlarmDual-homed PVCs




[AIS])



1e CES, DS3 ATM, E3 ATM, DS1

IMA, DS3 IMA, E1 IMA,


DSP2A/B/C/D Voice Servers,

Route Server, High-Density E1,

High Speed, Medium-Density

DS1, Multiserial, Quadserial,



OC-3c APS MM/SM, STM-1

MSP MM/SM, OC-12c/STM-4c

MM/SM, and Unstructured

DS3/E3 CES modules

ITU-T I.610B-ISDN operation and mainte-

nance principles and functions

ITU-T Q.922


tem No.1 (DSS 1) Data Link

Layer: ISDN Data Link Layer

Specification for Frame ModeBearer Services

Annex A

ITU-T Q.921

Digital Subscriber Signaling sys-

tem No. 1, ISDN User-Network

interface- Data Link Layer Spec-

ification






C-28 255-700-447


AAL1 Trunking CCS (Q.931)

AAL1 Trunking CCS

(Q.931/QSIG), AAL1 Trunking

CASAAL2 Trunking CCS (Q.931)

ITU-T Q.931

Switching and Signaling - Digital

subscriber Signalling System No.

1 - Network layer: Digital Sub-scriber Signaling System No. 1

(DSS 1) - ISDN User-Network

Interface Layer 3 Specification

for Basic Call Control

ITU-T Q.933 Annex A


tem No. 1—Integrated Services

Digital Network (ISDN) Digital

Subscriber Signaling System No.

1 (DSS 1)—Signaling Specifica-

tions for Frame Mode Switched

and Permanent Virtual Connec-tion Control and Status Moni-

toring

ATM UNI interfaces (3.0, 3.1,

4.0)

ITU-T Q.2110

B-ISDN SAAL Service Specific

Connection Oriented Protocol

(SSCOP)

ATM UNI interfaces (3.0, 3.1,

4.0)

ITU-T Q.2130

B-ISDN SAAL Service Specific

Coordination Function (SSCF)

for Support of Signaling at the

User-Network Interface

ITU-T Q.2931

B-ISDN Application protocols

for access signalling—Broad-

band Integrated Services Digital

Network (B-ISDN)— Digital

Subscriber Signalling System

No. 2 (DSS 2)—User Network

Interface (UNI) Layer 3 Specifi-

cation For Basic Call/Connec-

tion Control

ITU-T Q.2941.2

Draft: Broadband Integrated

Services Digital Network (B-

ISDN)- Digital Subscriber Signal-

ing System No. 2 (DSS2):

Generic identifier transport (





255-700-447 C-29



ITU-T Q.2971

B-ISDN—DSS 2—User-network

interface layer 3 specification for

point-to-multipoint call/connec-tion control

ITU-T V.8

Procedures For Starting Ses-

sions of Data Transmission Over

the General Switched Telephone

Network

ITU-T V.25

Automatic Answering Equip-

ment and General Procedures

for Automatic Calling Equip-

ment on the General Switched

Telephone Network Including

Procedures for Disabling of Echo

Control Devices for Both Manu-

ally and Automatically Estab-

lished Calls

Multiserial module ITUT V.35

Defines signaling for data rates

greater than 19.2 Kbps for a

trunk interface between net-

work access device and a packet

network

V5.2 (See ETSI 300 347.1

Enhanced DS1 and Enhanced

E1 modules

TR-TSU-001369

Generic Requirement for Frame

Relay PVC Exchange Services

Multiserial module X.21 bis

CCITT Interface Between Data

Terminal Equipment and Data

Circuit-Terminating Equipment

for Synchronous Operation of

Public Data Networks, Recom-

mendation X.21

Interface between data terminal

equipment (DTE) and data cir-

cuit-terminating equipment for

synchronous operation on pub-

lic data networks

X.144

User information transfer per-formance parameters for data

networks providing interna-

tional frame relay PVC service





Appendix C Reference InformationConnection Type by Interface Type

C-30 255-700-447


Connection Type by Interface Type

The PacketStar ® PSAX Multiservice Media Gateways provide a number of

connection types and interface types to the network as described in

Table C-6. Configuring connections are described in the PacketStar ® PSAX Sys-

tem Connections Provisioning Guide that can be found on the PacketStar PSAX

Multiservice Media Gateways Product Information Library CD-ROM.

Table C-6. Connection Type by Interface Type

Interface Type

A T M I

I S P ( N e t w o r k / U s e r )

A T M I

M A

A T M P

N N I 1 . 0

A T M U

N I 3 . 0 / 3 . 1 / 4 . 0

A T M V

i r t u a l I n t e r f a c e

B r i d g e

C A S T r u n k L i n e

C i r c u i t E m u l a t i o n

F r a m e R e l a y ( U N I , N N I )

G R - 3 0 3

H D L C P a s s - t h r o u g h

P R I I S D N ( N e t w o r k / U s e r )

T e r m i n a l E m u l a t i o n

Connection Type

AAL2 Trunking X X X X X

ATM-to-ATM virtual channel con-

nection (VCC) PVC

X X X X X

ATM-to-ATM virtual path connec-

tion (VPC) PVC

X X X X

Bridge-to-ATM VCC PVC X X X X X X

Bridge-to-bridge PVC X

Circuit emulation-to ATM VCC PVC X X X X X X

Circuit emulation-to circuit emula-

tion PVC

X

Frame relay-to-ATM VCC PVC X X X X X X

Frame relay-to-frame relay PVC X

In-band management ATM PVC X X X X X

Variable bit rate (VBR)-to-ATM VCC

PVC

X X X X X X X

VBR-to-VBR PVC X X

ATM-to-ATM IISP constant bit rate

(CBR) SVC

X X X X

ATM-to-ATM IISP VBR SVC X X X X

ATM-to-ATM VCC SPVC X X X XCircuit emulation-to-ATM VCC

SPVC

X X X X X X

CE-to-ATM Std AAL2 VCC SPVC X X X X

ERM-to-ATM VCC SPVC X X X



255-700-447 C-31


Appendix C Reference InformationInterface Type by Input/Output Module Type

Interface Type by Input/Output Module Type

Table C-7 shows the available interface types for each PacketStar PSAX I/O

module used in the PacketStar ® PSAX Multiservice Media Gateways. This

table does not include other PSAX modules that are not I/O modules, which

include: the Alarm module, the DSP2 x Voice Server modules, the Enhanced

Router module, the Route Server module, and the Tones and Announce-

ments Server module.

Frame relay-ATM VCC SPVC X X X X X

VBR-to-ATM VCC SPVC X X X X X X X

VBR-to-ATM Std AAL2 VCC SPVC X X X X X

Table C-6. Connection Type by Interface Type (Continued)

Interface Type

A T M I


A T M I

M A

A T M P

N N I 1 . 0

A T M U

N I 3 . 0 / 3 . 1 / 4 . 0

A T M V

i r t u a l

I n t e r f a c e

B r i d g

e

C A S T r u n

k L i n e


F r a m e R e l a y

( U N I , N N I )

G R - 3 0 3

H D L C P a s s - t h r o u g h

P R I I S D N ( N e t w

o r k / U s e r )

T e r m i n a l E m

u l a t i o n

Connection Type

Table C-7. Interface Type by I/O Module Type

Interface

A T M I

I S P ( N e t w o r

k / U s e r )

A T M I

M A

A T M P

N N I 1 . 0

A T M U

N I 4 . 0

A T M U

N I 3 . 0 /

3 . 1

A T M V

i r t u a l I n t e

r f a c e

B r i d g e

C A S T r u n k l i n

e

C i r c u i t E m u l a t

i o n

F r a m e R e l a y ( U N

I , N N I )

G R - 3 0 3

H D L C P a s s - t h r o

u g h

P R I I S D N ( N e t w o r

k / U s e r )

R o u t i n g

T e r m i n a l E m u l a

t i o n

V 5 . 2

Module


20N33 6-Port DS1 IMA X X X X X

20N36 6-Port Enhanced

DS1/T1 MultiserviceX X X X X X X X X


Density DS1 MultiserviceX X X X X X X X X X


Density DS1 IMAX X X X X

24N64 12-Port

Medium-Density

DS1/E1/DS0A CES

X* X† X‡ X§




C-32 255-700-447


23N35 24-Port High-

Density DS1 MultiserviceX X X X X X X X X X

23N69 8-Port HDSL-2

(HDSL2 MS)X X X X X


20N34 6-Port E1 IMA X X X X X

20N56 6-Port EnhancedE1 Multiservice

X X X X X X X X X

23N66 21-Port High-

Density E1 MultiserviceX X X X X X X X X X

23N34 21-Port High-

Density E1 IMAX X X X X


23N60 1-Port

Channelized DS3

Multiservice

X X X X X X X X X X

23N61 1-Port

Channelized DS3 CESX X

23N68 1-Port DS3 IMA X X X X X

20N03 1-Port

Unchannelized DS3 Frame

Relay

X

23N62 1-Port

Channelized STS-1e, T1

Format

X X X X X X X X X

20N02 2-Port DS3 ATM X X X X

20N22 2-Port E3 ATM X X X X

23N03 3-Port

Channelized DS3/STS-1e

CES

X X X X

23N74 3-Port DS3/E3

ATMX X X X X

3-Port DS3/E3 ATM

ProtectionX X X X X

Table C-7. Interface Type by I/O Module Type (Continued)

Interface

A T M I


A T M

I M A

A T M P

N N I 1 . 0

A T M U

N I 4 . 0

A T M U N

I 3 . 0 / 3 . 1

A T M V


B r i d g e

C A S T r u n k l i n e


F r a m e R e l a

y ( U N I , N N I )

G R - 3 0 3

H D L C P a s

s - t h r o u g h


R o u

t i n g


V 5 . 2

Module



255-700-447 C-33



23N02 3-Port

Unstructured DS3/E3 CESX

OC-3/STM-1/OC-3c/STM-1 Interface Modules

23N12 1-Port

Channelized OC-3/STM-1

CES Multimode

X X

23N13 1-Port


CES Single-mode

X X X

23N76 1-Port


Unstructured CES/ATM

Single-Mode

X¶ X¶ X¶ X¶ X**

23N75 1-Port


Unstructured CES/ATM

Multimode

X¶ X¶ X¶ X¶ X**

24N70 2-Port

OC-3c/STM-1 ATMMultimode

X X X X

24N71 2-Port

OC-3c/STM-1 ATM Single-

Mode

X X X X

24N72 4-Port

OC-3c/STM-1 MultimodeX X X X

24N73 4-Port

OC-3c/STM-1 Single-ModeX X X X

OC-3c Interface Only Modules

20N12 1-Port OC-3cMultimode with AQueMan X X X X

20N13 1-Port OC-3c

Single-Mode with

AQueMan

X X X X

20N14 1-Port OC-3c


Shaping

X X X X


Interface

A T M I


A T M

I M A

A T M P

N N I 1 . 0

A T M U

N I 4 . 0

A T M U N

I 3 . 0 / 3 . 1

A T M V


B r i d g e



F r a m e R e l a

y ( U N I , N N I )

G R - 3 0 3

H D L C P a s

s - t h r o u g h


R o u

t i n g


V 5 . 2

Module




C-34 255-700-447


20N15 1-Port OC-3c

Single-Mode with Traffic

Shaping

X X X X

20N72 1-Port OC-3c 1+1

APS MultimodeX X X X X

20N73 1-Port OC-3c 1+1

APS Single-ModeX X X X X

STM-1 Interface Only Modules

20N62 1-Port STM-1

Multimode with AQueManX X X X

20N63 1-Port STM-1

Single-Mode with

AQueMan

X X X X

20N64 1-Port STM-1


Shaping

X X X X

20N65 1-Port STM-1

Single-Mode with TrafficShaping

X X X X

20N92 1-Port STM-1

1+1 MSP MultimodeX X X X X

20N93 1-Port STM-1

1+1 MSP Single-ModeX X X X X

OC-12c/STM-4c Interface Modules

23N72 1-Port

OC-12c/STM-4c

Multimode

X X X X X

23N73 1-Port

OC-12c/STM-4cSingle-Mode

X X X X X


20N32 4-Port Voice

2-Wire OfficeX††

20N30 8-Port Voice

2-Wire StationX†

†


Interface

A T M I


A T M

I M A

A T M P

N N I 1 . 0

A T M U

N I 4 . 0

A T M U N

I 3 . 0 / 3 . 1

A T M V


B r i d g e



F r a m e R e l a

y ( U N I , N N I )

G R - 3 0 3

H D L C P a s

s - t h r o u g h


R o u

t i n g


V 5 . 2

Module



255-700-447 C-35


Appendix C Reference InformationATM Service Categories in the PSAX System

ATM Service Categories in the PSAX System

ATM Service Category Descriptions

The PSAX system support of defined ATM quality of service (QoS) categories

is described in Table C-8.


23N07 Quadserial X X X X X X X

20N07 6-Port Multiserial X X X X X X


20N40 Ethernet X X

23N40 4-Port Ethernet X X

* The module supports CAS Trunkline in DS1 and E1 modes only.† The module supports Circuit Emulation in DS1, E1, and DS0A modes.‡ The module supports GR-303 in DS1 mode only.§ The module supports PRI ISDN in DS1 and E1 modes only.¶ The module supports ATM services in the STM-ATM mode only.

** The module supports CE in the OC3-UCE mode only.†† European modules do not support this interface with the 8-Port Voice 2-Wire Station module or the

4-Port Voice 2-Wire Office module.


Interface

A T M I


A T M

I M A

A T M P

N N I 1 . 0

A T M U

N I 4 . 0

A T M U N

I 3 . 0 / 3 . 1

A T M V


B r i d g e



F r a m e R e l a

y ( U N I , N N I )

G R - 3 0 3

H D L C P a s

s - t h r o u g h


R o u

t i n g


V 5 . 2

Module

Table C-8. PSAX System-Supported Quality of Service Category Descriptions

ATM Service Category Description

Constant Bit Rate (CBR) This service offers consistent delay predictability. CBR is used for

applications such as circuit emulation, voice, and video.

Real Time Variable Bit Rate

(VBR-rt)

This service offers low delay variance, but requires access to a variable

amount of network bandwidth. VBR-rt is used for applications such

as packet video and voice.



Appendix C Reference InformationATM Service Categories in the PSAX System

C-36 255-700-447


Priority of ATM Service Categories

The attributes of the categories of service supported by the PSAX system soft-

ware are identified in Table C-9. The service examples in this table are

intended simply as illustrations; you should choose your service category

based on your network applications supported by the PSAX system. The flex-

ibility of the PSAX system allows you to tailor the system based on the

required service applications by selecting the appropriate connection configu-

ration selection field value.

Non-Real Time Variable Bit

Rate (VBR-nrt)

This service allows delay variance between the delivery of cells. VBR-

nrt is used for data applications that have potentially bursty traffic

characteristics.

Guaranteed Frame Rate(GFR)

This service allows delay variance and offers a minimum cell rateguarantee. When used with frame-based data encapsulated in AAL5

PDUs, it provides frame-based cell discard. GFR is used for frame relay

or ethernet over ATM.

Unspecified Bit Rate (UBR) This service allows for best-effort transport by the network. Cells are

transported by the network whenever bandwidth is available and the

user presents traffic.

Table C-8. PSAX System-Supported Quality of Service Category Descriptions (Continued)

ATM Service Category Description

Table C-9. Mapping ATM Service Categories to PSAX System Priority Levels

ATM Service CategoryConnection

ConfigurationField Value

AQueMan Priority(Legacy

Implementation)

ATM Forum TrafficManagement 4.1Priority (CurrentImplementation)

Service Examples

Constant Bit Rate (CBR) CBR1 Highest Highest 911 calls

CBR2 Lower than

CBR1

Preferred customers

CBR3 Lower than

CBR2

Standard

CBR4 Lower than

CBR3

Cellular

Real Time Variable Bit

Rate (VBR-rt)

VBR-express Lower than

CBR4

Lower than CBR Network

management

VBR-rt1 Lower than

VBR-express

Real-time video

VBR-rt2 Lower thanVBR-rt1

MPEG 1-2/JPEG



255-700-447 C-37


Appendix C Reference InformationTraffic Shaping, UPC, and Virtual Interface Configuration Compatibilities

Traffic Shaping, UPC, and Virtual Interface ConfigurationCompatibilities

Configuration compatibility among the ATM Traffic Shaping, UPC Support,

and VI Support features is shown in Table C-10. In the table, Yes indicates

that the two features coinciding in the matrix can be configured in the same

interface, and No indicates that they cannot. See Figure C-1 for an illustra-

tion of this concept.

Non-Real Time VariableBit Rate (VBR-nrt) VBR-nrt1 Lower thanVBR-rt2 Lower thanVBR-rt Data

VBR-nrt2 Lower than

VBR-nrt1

Data

Guaranteed Frame Rate

(GFR)

GFR2 Lowest (shares

queue with UBR)

Lower than

VBR-nrt

Frame relay,

Ethernet, TCP

Unspecified Bit Rate

(UBR)

UBR Lowest Lowest UDP

Table C-9. Mapping ATM Service Categories to PSAX System Priority Levels (Continued)

ATM Service CategoryConnection

ConfigurationField Value

AQueMan Priority(Legacy

Implementation)

ATM Forum TrafficManagement 4.1Priority (CurrentImplementation)

Service Examples

Table C-10. ATM Traffic Shaping, UPC Support, and VI Support ConfigurationCompatibility

Fields on ATM UNI, PNNI, and IISPConfiguration Windows

ATM TrafficShaping per VC

VI Support UPC Support

ATM Traffic Shaping per VC No Yes*

* UPC support and Traffic Shaping per VC are supported on the same end-to-end

connection only when VI is configured on the egress path, and UPC on the

ingress path.

VI Support No Yes

UPC Support Yes* Yes




C-38 255-700-447


ATM Traffic ShapingSample CPSCalculation Table

Use the information in Table C-11 as a guide for calculations to determine

ATM traffic shaping for cps on the appropriate module.

Sample calculation: If the ATM traffic-shaped connection is configured with

the PCR (Minimum/Actual Target CPS column) value 906 and the maximum

target CPS (Maximum Target CPS column) value 909, the ATM Traffic Shap-

ing feature is actually shaping the traffic to the (Actual CPS column) value

906 cps. The divergence is smallest at low PCR.

Figure C-1. Combining the UPC Feature and Either the TS or VI Feature on aConnection

Chassis Backplane

VI or TS

Rx

Tx

Ingress Path

Egress Path

UPC

I/O Module 1

VI or TS

Rx

Tx

Ingress Path

Egress Path

UPC

I/O Module 2

Table C-11. ATM Traffic Shaping CPS Calculation Table

Actual Rate (inbps)

Minimum/ActualTarget CPS

Maximum TargetCPS

Actual CPS

64,000 151 152 151

128,000 302 303 302

192,000 453 454 453

256,000 604 606 604

320,000 755 757 755

383,999 906 909 906

448,383 1,058 1,062 1,058

512,876 1,210 1,215 1,210

575,999 1,358 1,365 1,358

639,999 1,509 1,517 1,509

713,142 1,682 1,691 1,682



255-700-447 C-39



767,999 1,811 1,822 1,811

831,999 1,962 1,974 1,962

896,765 2,115 2,129 2,115

959,999 2,264 2,280 2,264

1,025,752 2,419 2,437 2,419

1,085,216 2,559 2,579 2,559

1,151,998 2,717 2,739 2,717

1,217,559 2,872 2,896 2,872

1,279,998 3,019 3,046 3,019

1,349,187 3,182 3,212 3,182

1,412,828 3,332 3,365 3,332

1,482,770 3,497 3,533 3,4971,543,915 3,641 3,680 3,641

1,610,320 3,798 3,840 3,798

1,663,997 3,925 3,970 3,925

1,741,393 4,107 4,156 4,107

1,782,854 4,205 4,257 4,205

1,804,335 4,256 4,308 4,256

1,826,339 4,307 4,362 4,307

1,848,886 4,361 4,416 4,361

1,871,997 4,415 4,472 4,415

1,895,693 4,471 4,529 4,471

1,919,997 4,528 4,588 4,528

1,944,932 4,587 4,648 4,587

1,970,523 4,647 4,710 4,647

1,996,797 4,709 4,774 4,709

2,023,781 4,773 4,839 4,773

2,051,504 4,838 4,907 4,838

2,079,997 4,906 4,976 4,906

2,109,293 4,975 5,047 4,975

2,139,425 5,046 5,120 5,0462,170,431 5,119 5,195 5,119

2,202,350 5,194 5,273 5,194

2,235,220 5,272 5,353 5,272

2,269,087 5,352 5,435 5,352

2,303,996 5,434 5,520 5,434

2,339,996 5,519 5,607 5,519

Table C-11. ATM Traffic Shaping CPS Calculation Table (Continued)

Actual Rate (inbps)


Maximum TargetCPS

Actual CPS




C-40 255-700-447


2,377,139 5,606 5,698 5,606

2,415,480 5,697 5,791 5,697

2,455,078 5,790 5,888 5,790

2,495,996 5,887 5,988 5,887

2,538,301 5,987 6,091 5,987

2,582,065 6,090 6,198 6,090

2,627,364 6,197 6,308 6,197

2,674,282 6,307 6,423 6,307

2,722,905 6,422 6,542 6,422

2,773,329 6,541 6,665 6,541

2,825,656 6,664 6,793 6,664

2,879,996 6,792 6,927 6,7922,936,466 6,926 7,065 6,926

2,995,195 7,064 7,209 7,064

3,056,322 7,208 7,359 7,208

3,119,995 7,358 7,516 7,358

3,186,378 7,515 7,679 7,515

3,255,647 7,678 7,850 7,678

3,327,995 7,849 8,028 7,849

3,403,631 8,027 8,215 8,027

3,482,785 8,214 8,411 8,214

3,565,709 8,410 8,616 8,410

3,652,677 8,615 8,831 8,615

3,743,994 8,830 9,058 8,830

3,839,994 9,057 9,296 9,057

3,941,047 9,295 9,547 9,295

4,047,561 9,546 9,812 9,546

4,159,994 9,811 10,093 9,811

4,278,851 10,092 10,389 10,092

4,404,699 10,388 10,704 10,388

4,538,175 10,703 11,039 10,7034,679,993 11,038 11,395 11,038

4,830,960 11,394 11,775 11,394

4,991,992 11,774 12,181 11,774

5,164,130 12,180 12,616 12,180

5,348,563 12,615 13,083 12,615

5,546,658 13,082 13,586 13,082


Actual Rate (inbps)


Maximum TargetCPS

Actual CPS



255-700-447 C-41


Appendix C Reference InformationPSAX I/O Module Transmit Clock Options

PSAX I/O Module Transmit Clock Options

Table C-12 lists the available transmit clock options for the PSAX I/O mod-

ules.

5,759,991 13,585 14,129 13,585

5,990,391 14,128 14,718 14,128

6,239,990 14,717 15,358 14,717

6,511,294 15,357 16,056 15,357

6,807,262 16,055 16,820 16,055

7,131,418 16,819 17,661 16,819

7,487,988 17,660 18,591 17,660

7,882,093 18,590 19,624 18,590

8,319,987 19,623 20,778 19,623

8,809,398 20,777 22,076 20,777

9,359,986 22,075 23,548 22,075

9,983,985 23,547 25,230 23,54710,697,126 25,229 27,171 25,229

11,519,982 27,170 29,435 27,170

12,479,981 29,434 32,111 29,434

13,614,524 32,110 35,322 32,110

14,975,977 35,321 39,246 35,321

16,639,974 39,245 44,152 39,245

18,719,971 44,151 50,459 44,151

21,394,253 50,458 58,869 50,458

24,959,961 58,868 70,642 58,868

29,951,954 70,641 88,303 70,641

37,439,942 88,302 117,737 88,302

49,919,923 117,736 176,605 117,736


Actual Rate (inbps)


Maximum TargetCPS

Actual CPS

Table C-12. I/O Module Transmit Clock Options

Model Number and Module Name LocalTiming

LoopTiming

AdaptiveTiming

SRTS*


20N33 6-Port DS1 IMA PC† PC NA‡

20N36 6-Port Enhanced DS1/T1 Multiservice PC PC PC

23N33 12-Port Medium-Density DS1 IMA PC PC NA

23N64 12-Port Medium-Density DS1 Multiservice PC PC PC




C-42 255-700-447


24N64 12-Port Medium-Density DS1/E1/DS0A CES PC§ PC PC

23N35 24-Port High-Density DS1 Multiservice PC¶ PC PC

23N69 8-Port HDSL-2 PC PC


20N34 6-Port E1 IMA PC PC PC

20N56 6-Port Enhanced E1 Multiservice PC PC PC

23N34 21-Port High-Density E1 IMA PC PC NA

23N66 21-Port High-Density E1 Multiservice PC PC PC


23N61 1-Port Channelized DS3 CES PC

VPC**

PC

VPC

NA

VPC

23N60 1-Port Channelized DS3 Multiservice PC

VPC

PC

VPC

NA

VPC

23N62 1-Port Channelized STS-1e, T1 Format PC

VPC

PC

VPC

NA

23N68 1-Port DS3 IMA PC

VPC

PC

VPC

NA

20N03 1-Port Unchannelized DS3 Frame Relay PC†† PC PC

20N02 2-Port DS3 ATM PC PC NA

20N22 2-Port E3 ATM PC PC PC

23N03 3-Port Channelized DS3/STS-1e CES PCVPC

PCVPC

NA

23N74 3-Port DS3/E3 ATM PC PC NA

23N02 3-Port Unstructured DS3/E3 CES PC PC PC


20N12 1-Port OC-3c Multimode with AQueMan PC PC NA

20N13 1-Port OC-3c Single-Mode with AQueMan PC PC NA

20N14 1-Port OC-3c Multimode with Traffic Shaping PC PC NA

20N15 1-Port OC-3c Single-Mode with Traffic Shaping PC PC NA

20N62 1-Port STM-1 Multimode with AQueMan PC PC NA20N63 1-Port STM-1 Single-Mode with AQueMan PC PC NA

20N64 1-Port STM-1 Multimode with Traffic Shaping PC PC NA

20N65 1-Port STM-1 Single-Mode with Traffic Shaping PC PC NA

20N72 1-Port OC-3c 1+1 APS Multimode PC PC NA

20N73 1-Port OC-3c 1+1 APS Single-Mode PC PC NA

Table C-12. I/O Module Transmit Clock Options (Continued)

Model Number and Module NameLocal

TimingLoop

TimingAdaptiveTiming

SRTS*



255-700-447 C-43



20N92 1-Port STM-1 1+1 MSP Multimode PC PC NA

20N93 1-Port STM-1 1+1 MSP Single-Mode PC PC NA

23N72 1-Port OC-12c/STM-4c Multimode PC PC NA

23N73 1-Port OC-12c/STM-4c Single-Mode PC PC NA

23N12 1-Port Channelized OC-3/STM-1 CES Multimode PC

VPC

PC

VPC

NA

23N13 1-Port Channelized OC-3/STM-1 CES Single-

modePC

VPC

PC

VPC

NA

* Sychronous Residual Time Stamp† PC – Port and Interface Configuration window.‡ NA – Not Applicable.§ Also provides a DS0A composite clock.

¶ Also provides a DS0A composite clock.** VPC – Virtual Port and Interface Configuration window.†† Also provides a CardFreeRun clock.

Table C-12. I/O Module Transmit Clock Options (Continued)

Model Number and Module NameLocal

TimingLoop

TimingAdaptiveTiming

SRTS*




C-44 255-700-447





255-700-447 D-1

D PSAX Module Features


This appendix describes the PSAX I/O and server modules that are supported

by the PSAX 2300 chassis.

The PacketStar PSAX I/O and server modules described in this appendix are

also listed in Table D-1.

Table D-1. PacketStar PSAX Multiservice Media Gateway Modules

Model No. Product Name


20N33 6-Port DS1 IMA20N36 6-Port Enhanced DS1/T1 Multiservice

23N69 8-Port HDSL-2 (HDSL2 MS)

23N33 12-Port Medium-Density DS1 IMA





23N61 1-Port Channelized DS3 CES




20N03 1-Port Unchannelized DS3 Frame Relay

20N02 2-Port DS3 ATM

20N22 2-Port E3 ATM

23N03 3-Port Channelized DS3/STS-1e CES


23N02 3-Port Unstructured DS3/E3 CES

DSP2 Voice Servers

20N29 DSP2A Voice Server

20N28 DSP2B Voice Server

23N27 DSP2C Voice Server

23N29 DSP2D Voice Server

23N26 DSP2E Voice Server

23N25 DSP2F Voice Server



Appendix D PSAX Module FeaturesOverview of This Appendix

D-2 255-700-447



20N34 6-Port E1 IMA

20N56 6-Port Enhanced E1 Multiservice

23N34 21-Port High-Density E1 IMA



23N40 4-Port Ethernet

20N40 Ethernet


23N12 1-Port Channelized OC-3/STM-1 CES Multimode

23N13 1-Port Channelized OC-3/STM-1 CES Single-mode

23N75 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Multimode

23N76 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Single-Mode





20N12 1-Port OC-3c Multimode with AQueMan

20N14 1-Port OC-3c Multimode with Traffic Shaping

20N13 1-Port OC-3c Single-Mode with AQueMan

20N15 1-Port OC-3c Single-Mode with Traffic Shaping



20N62 1-Port STM-1 Multimode with AQueMan

20N64 1-Port STM-1 Multimode with Traffic Shaping

20N63 1-Port STM-1 Single-Mode with AQueMan

20N65 1-Port STM-1 Single-Mode with Traffic Shaping






23N41 Enhanced Router

20N41 Route Server

23N28 Tones and Announcements Server


2-Port High Speed

Table D-1. PacketStar PSAX Multiservice Media Gateway Modules (Continued)




255-700-447 D-3


Appendix D PSAX Module FeaturesDS1/T1 Interface Modules


6-Port DS1 IMA Module (20N33)

The 6-Port DS1 IMA module has six physical RJ-45 ports. The inverse multi-

plexing for ATM capabilities of this module permit a user to strap two to six

of the physical ports together to create ATM interfaces that support 3–9 Mbpsof bandwidth. A maximum of three IMA groups may be configured per mod-

ule.

Source data enters the module from the backplane and is divided between

the ports within the IMA group specified in the virtual circuit connection.

The data leaves the front of the module and is transported across individual

T1 lines. At the destination IMA module, the T1 streams are merged back

together in correct order and passed on to other modules as directed by vir-

tual circuit connections. IMA dynamically handles conditions when T1s

within an IMA group become unavailable: the IMA "pipe" shrinks in band-

width to the remaining T1s and continues to pass traffic. When a problem T1

comes back on line, the IMA "pipe" will enlarge to take full advantage of the

restored bandwidth.

Software Features The 6-Port DS1 IMA module offers ATM IMA services, including permanent

virtual circuits, soft permanent virtual circuits, and switched virtual circuits.

The module supports ATM UNI v3.a, IISP, PNNI, and ILMI. This functionality

enables service providers to offer multiple DS1 IMA group services using a

single module.

Hardware Features The 6-Port DS1 IMA module provides the following hardware features:

• Number of ports: 6

• Connector type: RJ-45 (120-Ohm symmetrical pair [4 wire + Frame

Ground] interface)

• Line rate: 1.544 Mbps

• Line encoding mode: B8ZS

• Loopback capabilities: local loopback, line loopback, payload loopback

• Line buildout: Up to 133, 266, 399, 533, and 655 feet; negative 7-5 dB,

negative 15 dB, negative 22-5 dB, zero dB.

• Framing mode: ESF, D4

20N07 6-Port Multiserial

23N07 Quadserial


20N32 4-Port Voice 2-Wire Office

20N30 8-Port Voice 2-Wire Station

Table D-1. PacketStar PSAX Multiservice Media Gateway Modules (Continued)





D-4 255-700-447


6-Port Enhanced DS1/T1 Module (20N36)

The 6-Port Enhanced DS1/T1 Multiservice module provides six ports, each

with a line rate of 1.544 Mbps. The interfaces support American National Stan-

dards Institute (ANSI) T1.403, af-phy-0016.000 and af-test-0037.000. Each port

can be independently configured to provide services for channelized and

unchannelized frame relay configurations, circuit emulation service, dynamic

bandwidth circuit emulation service, and ATM service. Three light-emitting

diode (LED) status indicators provide the operational status of the module.

The module has built-in channel service unit (CSU) capability that allows it

to interface directly to a DS1/T1 line with multiple repeaters. This feature

allows the module to interface with a time-division multiplex (TDM) chan-

nelized DS1/T1 circuit. Configured for channelized T1 service, the 6-Port

Enhanced DS1/T1 Multiservice module maps up to 24 individual high-level

data link control (HDLC) data links on a single T1 connection (144 HDLC

data links per module). This module also provides a data service unit/channel

service unit (DSU/CSU) for each port in order to configure individual DS0s.

The user can configure this module to provide N x 64 Kbps (fractional DS1)

structured circuit-emulation service. When configured for DS1 circuit-emu-

lation service, the 6-Port Enhanced DS1/T1 Multiservice module interfaces

with TDM channelized DS1 circuits. It converts channelized digital signals

(usually voice data) to ATM virtual channels. This module can adapt a maxi-

mum of 24 DS0 channels per port to ATM virtual channels with individual

virtual path identifiers (VPIs) and virtual channel identifiers (VCIs) using

structured (channelized) circuit emulation. Signaling bit transport is also pro-

vided, based on ATM Forum standards for channel-associated signaling

(CAS). This module can connect to a device using 56 Kbps with 8 Kbps for

robbed-bit signaling per DS0. With the 64 Kbps "clear channel" capability,

the 6-Port Enhanced DS1/T1 Multiservice module can connect to a deviceusing an ISDN primary rate interface (PRI) service. Because this structured

circuit-emulation service can be configured to use only a fraction of the time

slots, the user can configure several independent emulated circuits to share

one service interface.

The 6-Port Enhanced DS1/T1 Multiservice module uses an ATM UNI 3.0,

UNI 3.1, or 4.0 interface, which allows any DS1 port to act as a user network

interface (UNI), or an interim inter-switch protocol (IISP) user or network

interface to an ATM network.

Software Features Multiservices:

• ATM: ATM UNI 3.0, 3.1,and 4.0; ATM Interim inter-switch signaling proto-

col (IISP) user, IISP network; ATM private network-network interface

(PNNI) 1.0

• CE: Circuit emulation service (CES) with ISDN PRI using 64 Kbps clear

channel; 1 X 56 Kbps structured CAS; unstructured CES

• HDLC Passthrough

• Frame relay UNI and NNI (FRF.1, FRF.2, FRF.5, and FRF.8)

• PRI ISDN



255-700-447 D-5



• ITU-T I.370 (Frame relay policing)

• Congestion management

• Traffic policing

Hardware Features The 6-Port Enhanced DS1/T1 Multiservice module has the following hard-ware features:


• Connector type: RJ-45


• Physical interfaces supported: T1

• Line encoding modes: B8ZS, AMI

• Line type/framing modes: ESF, D4

• Loopback capabilities: local loop, line loop, payload loop

• Line buildout:

~ Short haul: up to 133, 266, 399, 533, and 655 feet (receiver sensitivity:12 dB)

~ Long haul: 0 dB, -7.5 dB, -15 dB, -22.5 dB (receiver sensitivity: 32 dB)

8-Port HDSL-2 Module (23N69)

The 8-Port HDSL-2 module provides a line rate of 1.552 Mbps per port for

full duplex, symmetric connections. Each port can be independently config-

ured to provide for channelized and unchannelized circuit emulation service

(CES) and ATM services. Typical applications for this module include PBX

network connections, cellular antenna stations, digital loop carrier systems,

interchange POPs, Internet servers, and private data networks.

You can configure each port on the 8-Port HDSL2 Multiservice module to

provide N x 64 Kbps (fractional T1) structured circuit emulation service.

When configured for DS1 circuit emulation service, the module interfaces

with TDM channelized DS1 circuits. It converts channelized data (usually

voice data) to ATM virtual channels. By using structured (channelized) cir-

cuit emulation, this module can adapt a maximum of 24 DS0 channels per

port to ATM virtual channels with individual virtual path identifiers (VPIs)

and virtual channel identifiers (VCIs). Signaling bit transport is also pro-

vided, based on ATM Forum standards for channel-associated signalling

(CAS). With the 64 Kbps "clear channel" capability, this module can connect

to a device using an ISDN PRI service. Because this structured circuit emula-

tion service can be configured to use only a fraction of the time slots, you canconfigure several independent emulated circuits to share one service inter-

face.

The 8-Port HDSL2 Multiservice module uses ATM Forum Specifications UNI

3.0, 3.1 or 4.0 , which allow any DS1 port to act as a user network interface

(UNI), an interim inter-switch protocol (IISP) user or network interface to an

ATM network.




D-6 255-700-447


Software Features The 8-Port HDSL-2 module supports the following services:

• ATM: ATM UNI 3.0, 3.1, and 4.0; Interim inter-switch signaling protocol

(IISP) user, IISP network; PNNI 1.0, all with traffic shaping


channel; 1x64 Kbps structured CAS; Nx64 Kbps structured CCS; unstruc-

tured CES

Hardware Features The 8-Port HDSL-2 module provides the following hardware features:


• Connector type: one, 50-pin Mini-Champ connector


• Physical interfaces supported: ANSI-T1.418-2000

• Loopback capabilities on DS1 port: local loopback, line loopback

12-Port Medium-Density DS1 IMA Module (23N33)

The 12-Port Medium-Density DS1 IMA module provides a line rate of

1.544 Mbps per port. The module’s inverse multiplexing for ATM capability

allows you to strap 2 to 12 of the physical ports together to create ATM inter-

faces that support up to 18 Mbps of bandwidth. A maximum of six IMA

groups may be configured per module.

This module offers native DS1 ATM services and DS1 IMA services, including

permanent virtual circuits, soft permanent virtual circuits, and switched vir-

tual circuits. The module supports UNI v3.a, UNI v4.0, IISP, PNNI, and ILMI.

This functionality enables service providers to offer both individual unchan-

nelized DS1 ATM services (without IMA overhead) and multiple DS1 IMA

group services using a single module.

Using the IMA protocol, this module provides an effective method of com-

bining the transport bandwidths of multiple DS1 links that are grouped to

collectively provide higher intermediate rates. This technique involves

inverse multiplexing and de-multiplexing of ATM cells in a cyclical fashion

among links grouped to form a higher bandwidth logical link whose rate is

approximately the sum of the link rates. This is referred to as an IMA group.

From the system’s viewpoint, these IMA groups are simply new ATM inter-

faces sized as multiples of T1. (Refer to Inverse Multiplexing for ATM Version 1.1,

af-phy-0086.001.)

Software Features The 12-Port Medium-Density DS1 IMA module supports the following pro-

tocols and services:

• Protocols: ATM, IMA

• ATM services over IMA groups:

~ ATM UNI 3.0, 3.1, 4.0, and ILMI

~ IISP user and IISP network

~ ATM PNNI



255-700-447 D-7



Hardware Features The 12-Port Medium-Density DS1 IMA module provides the following hard-

ware features:


• Connector type: one Mini-Champ connector that mates with the AMP

cable #1324936-1


• Physical interfaces supported: ITU-T G.703, ITU-T G.704

• Line encoding mode: B8ZS (default), AMI

• Loopback capabilities: line loopback, local loopback

• Line buildout: Up to 133, 266, 399, 533, and 655 feet

• Framing mode: ESF (default), D4

12-Port Medium-Density DS1 Multiservice Module (23N64)

The 12-Port Medium-Density DS1 Multiservice module provides a line rate

of 1.544 Mbps per port. Each port can be independently configured to pro-vide for channelized and unchannelized frame relay configurations, circuit

emulation service (CES), high-level data link control (HDLC) pass-through

mode, integrated services digital network with a primary rate interface (ISDN

PRI) service, and ATM services.

You can configure the 12-Port Medium-Density DS1 Multiservice module to

provide N x 64 Kbps (fractional T1) structured circuit emulation service.

When configured for DS1 circuit emulation service, the module interfaces

with TDM channelized DS1 circuits. It converts channelized data (usually


cuit emulation, this module can adapt a maximum of 24 DS1channels per


and virtual channel identifiers (VCIs). Signaling bit transport is also pro-vided, based on ATM Forum standards for channel-associated signalling

(CAS). With the 64 Kbps "clear channel" capability, this module can connect

to a device using an ISDN PRI service. Because this structured circuit emula-

tion service can be configured to use only a fraction of the time slots, you can

configure several independent emulated circuits to share one service inter-

face.

The 12-Port Medium-Density DS1 Multiservice module uses ATM Forum

Specification UNI 3.0 or UNI 3.1, which allows any DS1 port to act as a user

network interface (UNI), an interim inter-switch protocol (IISP) user or net-

work interface to an ATM network.

Software Features The 12-Port Medium-Density DS1 Multiservice module supports the follow-ing services:




channel; 1 x 64 Kbps structured CAS; unstructured CES

• HDLC passthrough mode (N x 56 and N x 64)





D-8 255-700-447


• GR-303

• CAS Trunkline




Hardware Features The 12-Port Medium-Density DS1 Multiservice module provides the follow-

ing hardware features:


• Connector type: one Mini-Champ connector


• Physical interfaces supported: ITU-T G.703, ITU G.704

• Line encoding mode: B8ZS, AMI


• Line buildout:~ Short haul: up to 133, 266, 399, 533, and 655 feet (receiver sensitivity

12 dB)

~ Long haul: 0 dB, - 7.5 dB, - 15 dB, - 22.5 dB (receiver sensitivity 32 dB)


12-Port Medium-Density DS1/E1/DS0A CES Module (24N64)

The 12-Port Medium-Density DS1/E1/DS0A CES module provides DS1 and

E1 circuit emulation services, including an Nx64 Kbps CAS mode to support

channelized AAL1 tariff services, and a DS0A mode to support SS7 traffic

across the network. This module also provides a line rate of 1.544 Mbps per

DS1 port, 2.048 Mbps per E1 port, and 64 Kbps per DS0A port. Each port can

be independently configured to provide Nx64 Kbps (fractional T1) struc-

tured, channelized and unchannelized circuit emulation service (CES) with

Nx64 Kbps CAS, and unstructured CES. This module runs at a high speed in

the PSAX 4500 chassis. In Phase 3, the E1 CES mode and SRTS timing for

unstructured DS1 and unstructured E1 circuits are supported. For a descrip-

tion of each operating mode, see the following PSAX module user guides:

• For DS1 mode, see the PacketStar ® PSAX 12-Port Medium-Density

DS1/E1/DS0A CES Module User Guide (DS1 Mode), 255-700-379.

• For E1 mode, see the PacketStar ® PSAX 12-Port Medium-Density DS1/E1/DS0A

CES Module User Guide (E1 Mode), 255-700-348.

• For DS0A mode, see the PacketStar ® PSAX 12-Port Medium-Density

DS1/E1/DS0A CES Module User Guide (DS0A Mode), 255-700-378.

Software Features The 12-Port Medium-Density DS1/E1/DS0A CES (DS1 Mode) module sup-

ports the following services:

• Circuit emulation service (CES):

~ Structured DS1 signal transport

~ Nx64 Kbps circuit emulation (where 1<=N<=24)



255-700-447 D-9



~ Channel-associated signaling (CAS) Nx64

~ Dynamic Bandwidth Allocation (DBA)

• Integrated services digital network with primary rate interface service (PRI

ISDN) with 64 Kbps clear channel capability for the D-channel

• AAL2 cell formatting for interworking with the DSP2A, DSP2B, DSP2C,

and DSP2D Voice Server modules.

The 12-Port Medium-Density DS1/E1/DS0A CES (E1 Mode) module sup-

ports the following services:


~ Structured E1 signal transport


~ Channel-associated signaling (CAS) Nx64

• CAS trunkline



• AAL2 cell formatting for interworking with the DSP2A, DSP2B, DSP2C,and DSP2D Voice Server modules.

The 12-Port Medium-Density DS1/E1/DS0A CES (DS0A Mode) module sup-

ports the following circuit emulation services:

• Unstructured DS0A signal transport

• 1x64 Kbps CES with AAL1

• Trunk Conditioning

Hardware Features The 12-Port Medium-Density DS1/E1/DS0A CES module provides the fol-

lowing hardware features:

• Number of ports: 12• Connector type: one 25-pair, 100-ohm, RJ-48H, 50-pin Telco connector

(receptacle)

• Port Line rate:

~ DS1: 1.544 Mbps

~ E1: 2.048 Mbps

~ DS0A: 64 Kbps

• Physical interfaces supported:

~ DS1: ANSI T1.403; ITU-T G.703, ITU-T G.704

~ E1: ANSI T1.403; ITU-T G.703, ITU-T G.704

~ DS0A: ANSI T1.403; Bellcore TR-TSY-000458, TR-OPT-000489

• Line encoding mode:

~ DS1: B8ZS, AMI

~ E1: HDB3, AMI

~ DS0A: AMI

• Loopback capabilities:

~ DS1: line loopback, local loopback, payload loopback

~ E1: line loopback, local loopback




D-10 255-700-447


~ DS0A: line loopback, transmit pattern, monitor pattern mode, transmit

and monitor pattern mode

• Line buildout:

~ DS1: up to 133, 266, 399, 533, and 655 feet; -7dB through -5dB, -15dB,

and -22dB through -5dB

~ E1: N/A~ DS0A: up to 1500 feet

• Framing mode:

~ DS1: ESF, D4

~ E1: Time Slot 16 CAS, CCS, CRC-4

~ DS0A: N/A

• Transmit clock:

~ DS1: local timing, loop timing

~ E1: local timing, loop timing

~ DS0A: composite clock DS0A

• Pulse:~ DS1: meets pulse shape mask of ANSI T1.403

~ E1: 244 ns pulse width, per ITU-T G.703

~ DS0A: 15.6 ms pulse width NRZ, 8.0 V pp, per TR-TSY-000458

24-Port High-Density DS1 Multiservice Module (23N35)

The 24-Port High-Density DS1 Multiservice module (model 23N35) provides

a line rate of 1.544 Mbps per port and long haul support, with 1:1 protection

when connected to the PSAX 24-Port RJ Protection Patch Panel (COMCODE

300564291). Each port can be independently configured to provide for chan-

nelized and unchannelized frame relay configurations, circuit emulation ser-

vice (CES), CAS trunkline service, high-level data link control (HDLC) pass-

through mode, integrated services digital network with a primary rate inter-

face (ISDN PRI) service, and ATM services. All services are available in pro-

tected or non-protected configurations.

Note: The 24-Port High-Density DS1 Multiservice module and the

PSAX 24-Port RJ Protection Patch Panel are designed to be

installed in a non-protected or 1:1 protection configuration. The

module and protection patch panel are not designed for N:1 Traffic

Protection configurations. For 1:1 protection, two modules and the

PSAX 24-Port RJ Protection Patch Panel are required.

For instructions on configuring and guidance on using this module, see thePacketStar PSAX 24-Port High-Density DS1 Multiservice Module User Guide.

Software Features The 24-Port High-Density DS1 Multiservice module supports the following

services:





255-700-447 D-11


Appendix D PSAX Module FeaturesDS3, E3, and STS-1e Interface Modules


channel; 1x64 Kbps structured CAS; Nx64 Kbps structured CCS; unstruc-

tured CES

• HDLC passthrough mode (Nx56 and Nx64) with bit inversion


• GR-303• CAS trunkline

Hardware Features The 24-Port High-Density DS1 Multiservice module provides the following

hardware features:


• Connector type: two 50-pin .050 CHAMP receptacles



• Line encoding mode: B8ZS, AMI

• Loopback capabilities: no loop, line loop, local loop, payload loop

• Line buildout:

~ Short haul: up to 133, 266, 399, 533, and 655 feet (receiver sensitivity

12 dB)

~ Long haul: 0 dB, - 7.5 dB, - 15 dB, - 22.5 dB (receiver sensitivity 32 dB)



1-Port Channelized DS3 Multiservice Module (23N60)

The 1-Port Channelized DS3 Multiservice and the 1-Port Channelized DS3

CES modules have a line rate of 44.736 Mbps. The physical port is divided

(channelized) into 28 virtual DS1 ports. Each virtual DS1 port can be chan-

nelized into 24 individual DS0s, providing a total of 672 channels. Each vir-

tual DS1 port can also be set up as a single, structured or unstructured chan-

nel. The 1-Port Channelized DS3 CES module provides circuit emulation

service only. The 1-Port Channelized DS3 Multiservice module provides the

following interfaces:

Because the 1-Port Channelized DS3 Multiservice module uses ATM Forum

specifications UNI 3.0, UNI 3.1, or 4.0, any DS1 port acts as a user network

interface (UNI), or an interim inter-switch protocol (IISP) user or IISP net-

• ATM IISP (network/user) • Frame relay (UNI, NNI)

• ATM PNNI 1.0 • GR-303• ATM UNI 3.0, 3.1, and 4.0 • HDLC pass-through

• CAS trunkline • PRI ISDN (network/user)





D-12 255-700-447


work interface to an ATM network. The module can be configured to provide

N x 64 Kbps (fractional DS1) structured circuit emulation service. When con-

figured for DS1 circuit emulation service, the module interfaces with TDM

channelized DS1 circuits. It converts the channelized digital signals (usually


cuit emulation, the 1-Port Channelized DS3 Multiservice module can adapt a

maximum of 28 DS1 channels per port to ATM virtual channels with individ-ual VPIs and VCIs. Signaling bit transport is also provided, using ATM Forum

standards for channel-associated signaling (CAS). The module can be con-

nected to a device using 56 Kbps or 64 Kbps for service transport, with

8 Kbps for robbed-bit signaling per DS0. With the 64 Kbps “clear channel”

capability, this module can connect to a device using ISDN primary rate inter-

face (PRI) service. Because the structured circuit-emulation service can be

configured to use only a fraction of the time slots, several independent emu-

lated circuits can be configured to share one service interface.

Software Features The following services and functions are available on the 1-Port Channelized

DS3 Multiservice module. The 1-Port Channelized DS3 CES module provides

only the functions enabled by circuit emulation service.• ATM services (channelized and unchannelized) with ATM traffic policing

(UPC support) capability:

~ ATM UNI 3.0 and 3.1, with integrated link management interface (ILMI)

capability

~ Interim inter-switch signaling protocol (IISP) user and IISP network

~ ATM private network-node interface (PNNI)


~ Unstructured and structured DS1 signal transport

~ Nx64 Kbps circuit emulation (where 1=N=24)

~ Channel-associated signalling (CAS)


ISDN) with 64 Kbps clear channel capability and HDLC passthrough mode

for the D-channel

• Frame relay UNI and NNI with frame relay policing (ITU-T I.370) capability

• High-level data link link control (HDLC) passthrough mode (Nx64)

• AAL2 cell formatting is provided for interworking with the DSP2A, DSP2B,

and DSP2C Voice Server modules.

• Mixed circuit emulation, ATM, and frame relay channels can be configured

within a virtual DS1 port.

Hardware Features The 1-Port Channelized DS3 Multiservice and CES modules have the follow-ing hardware features:

• Number of ports: one port supports 28 virtual DS1 ports

• Connector type: two BNC connectors, one to receive data and one to trans-

mit data



• Framing mode for CES: ESF and D4



255-700-447 D-13



• Line type: C-bit parity, M13

• Loopback capability: local loop, line loop

• Transmit clock: local timing, loop timing

• Line buildout: short (0–133 feet), long (134–266)

3-Port Channelized DS3/STS-1e CES Module (23N03)

The 3-Port Channelized DS3/STS-1e CES module supports circuit emulation

services (CES) and primary rate interfaces (PRI) with processing power

required to handle 3 × 672 DS0s. Additionally, this module is software con-

figurable to function in either DS3 or STS-1e modes. This dual-mode capabil-

ity allows you to deliver channelized DS3 or STS-1e configurations while

maintaining inventory of a single module type.

The module’s three high-speed circuit emulation network interfaces operate

at Digital Signal Level 3 (DS3), with a line rate of 44.736 Mbps, or at Syn-

chronous Transport Signal Level 1e (STS-1e), with a line rate of 51.84 Mbps.

Each port is capable of supporting 28 channelized DS1 interfaces for circuit

emulation services.

Note: This module provides HDLC controllers to support integrated ser-

vices digital network with primary rate interface service (PRI

ISDN) with 64 Kbps clear channel capability for the D-channel.

Each DS3 port on the module supports up to 64 of these channels.

This is consistent with the requirement for transporting and termi-

nating D-channels on PRI links.

Typically, this module is used to connect the Multiservice Media Gateway

system to a TDM voice switch or digital cross-connect device (DACS) via

three ports.

This module can be configured to provide N × 64 Kbps (fractional DS1) struc-tured circuit emulation service. When configured for DS1 circuit emulation

service, the module interfaces with TDM channelized DS1 circuits. It converts

the channelized digital signals (usually voice data) to ATM virtual channels

for transport to ATM interfaces via the backplane. By using structured (chan-

nelized) circuit emulation, the 3-Port Channelized DS3/STS-1e CES module

can adapt a maximum of 28 DS1 channels per port to ATM virtual channels

with individual VPIs and VCIs. Signaling bit transport is also provided, using

ATM Forum standards for channel-associated signaling (CAS).

You can connect this module to a device using 56 Kbps or 64 Kbps for service

transport, with 8 Kbps for robbed-bit signaling per DS0. With the 64 Kbps

"clear channel" capability, this module can be connected to a device using

ISDN primary rate interface (PRI) service. Because this structured circuit-emulation service can be configured to use only a fraction of the time slots,

several independent emulated circuits can be configured to share one service

interface.

The channelized DS3 multiservice and CES modules support activating and

deactivating DS1 access network interface (ANI) in-line loopback codes

embedded in the DS1 signal. These codes test transmissions between cus-

tomer interface equipment and network interface equipment, for example,




D-14 255-700-447


between PSAX central office (CO) products and customer premises equip-

ment (CPE) products at the edge of an ATM network. The PSAX system also

generates alarm indication signals on all affected DS1 connections whenever

a loop is activated.

Software Features The 3-Port Channelized DS3/STS-1e CES module supports the following ser-vices:




~ Channel-associated signaling (CAS) 1x56



• AAL2 cell formatting for interworking with the DSP2 x Voice Server mod-

ules.

Hardware Features The 3-Port Channelized DS3/STS-1e CES module provides the following

hardware features:


• Connector type: 6 BNC connectors; 1 receive connector and 1 transmit

connector for each port

• Line rate:

~ DS3: 44.736 Mbps

~ STS-1e: 51.84 Mbps


• Loopback capabilities: line loopback, local loopback, and DS1 ANI in-line

codes for loopback

• Line buildout: short (0–133 feet); long (134–266 feet)

• Framing modes: ESF and SF for CES

The 3-Port Channelized DS3/STS-1e Multiservice Protection module pro-

vides N:1 traffic protection when used within a protection group. In addition

to its N:1 Protection capabilities, this module provides ATM, circuit emula-

tion, and HDLC Passthrough services with processing power to handle 3 x

672 DS0s. It is software configurable to function in either DS3 or STS-1e

modes, permitting you to deliver channelized DS3 or STS-1e configurations

while maintaining inventory of a single module type. This dual-mode capa-

bility simplifies ordering, inventory management, and manufacturability.

The module’s three channelized multiservice interfaces operate at Digital Sig-

nal Level 3 (DS3), with a line rate of 44.736 Mbps, or at Synchronous Trans-

port Signal Level 1e (STS-1e), with a line rate of 51.84 Mbps. Each port is

capable of supporting 28 channelized DS1 interfaces for multiservices. Typi-

cally, this module is used to connect the Multiservice Media Gateway system

to a TDM voice switch or digital cross-connect device, such as a DACS, via

three ports.



255-700-447 D-15



1-Port Channelized STS-1e, T1 Module (23N62)

The 1-Port Channelized STS-1e, T1 Format module provides one physicalport with a line rate of 51.84 Mbps. The physical port is divided (channel-

ized) into 28 virtual DS1 ports. Each virtual DS1 port can be configured as a

structured port and channelized into 24 individual DS0s, providing a total of

672 channels. Each virtual DS1 port can also be configured as a single struc-

tured or unstructured channel. The 1-Port Channelized STS-1e, T1 Format

module provides the following interfaces:

The user can configure this module to provide n X 64 Kbps (fractional DS1)

structured circuit emulation service. When configured for DS1 circuit emula-

tion service, the module interfaces with TDM channelized DS1 circuits. It

converts the channelized digital signals (usually voice data) to ATM virtual

channels. Signaling bit transport is also provided, using ATM Forum stan-

dards for channel-associated signaling (CAS). This module can connect to a

device using 56 Kbps or 64 Kbps for service transport, with 8 Kbps for

robbed-bit signaling per DS0. With the 64 Kbps “clear channel” capability,

this module can connect to a device using ISDN primary rate interface (PRI)

service. Because this structured circuit-emulation service can be configured

to use only a fraction of the time slots, the user can configure several inde-pendent emulated circuits to share one service interface.

The 1-Port Channelized STS-1e, T1 Format module uses ATM Forum specifi-

cations UNI 3.0 or UNI 3.1, which allow any DS1 port to act as a user net-

work interface (UNI), or an interim interswitch protocol (IISP) user or IISP

network interface to an ATM network.

Software Features The following services are supported:

• Circuit emulation service (CES) with unstructured and structured DS1 sig-

nal transport

• N X 64 kbps circuit emulation service (1 = N = 24)

• Primary ISDN service with optional HDLC pass-through mode for theD-channel

• Channel-associated signaling (CAS)

• Multiservices:

~ ATM: ATM UNI 3.0 and 3.1; Interim inter-switch signaling protocol

(IISP) user, IISP network, ILMI, PNNI

~ CE: Circuit emulation service (CES) with ISDN PRI using 64 Kbps clear

channel; 1 X 56 Kbps structured CAS; unstructured CES

• ATM IISP (network/user) • Frame relay (UNI, NNI)

• ATM PNNI 1.0 • GR-303

• ATM UNI 3.0, 3.1, and 4.0 • HDLC pass-through

• CAS trunkline • PRI ISDN (network/userP





D-16 255-700-447


~ Frame relay UNI and NNI (FRF.1, FRF.2, FRF.5, and FRF.8)

~ ITU-T I.370 (frame relay policing)

~ Congestion management

~ Traffic policing

Hardware Features The 1-Port Channelized STS-1e, T1 Format module has the following hard-

ware features:

• Number of ports: one port supports 28 virtual DS1 ports


mit data



• Framing mode for CES: ESF and D4

• Loopback capability: local loop, line loop


• Line buildout: short (0–133 feet), long (134–266)

2-Port DS3 ATM Module (20N02)

The 2-Port DS3 ATM provides a network interface at Digital Signal Level 3

(DS3), with a line rate of 44.736 Mbps. Typically, this module is used to con-

nect the PSAX system to an ATM edge switch or digital subscriber line aggre-

gation multiplexer (DSLAM) device. Each port can be configured for ATM

service, including ATM UNI 3.0, 3.1, and 4.0; ATM IISP user and network;

and ATM PNNI 1.0 interfaces. The 2-Port DS3 ATM module has three types

of LED indicators.

Software Features The 2-Port DS3 ATM module uses ATM Forum specifications UNI 3.0 or

UNI 3.1, which allows either DS3 port to act as a user network interface

(UNI), an interim inter-switch protocol (IISP) user or IISP network interface,

or as a PNNI network interface to an ATM network.

Hardware Features The 2-Port DS3 ATM module has the following hardware features:

• Number of ports: two

• Connector type: four BNC connectors for the two ports (each port has one

receive connector and one transmit connector)

• Line rate: 44.736 Mbps (typical)


• Line type: C-bit parity, clear channel


• Cell mapping: PLCP, direct mapping



255-700-447 D-17



1-Port Unchannelized DS3 Frame Relay Module (20N03)

The 1-Port Unchannelized DS3 Frame Relay module provides an unchannel-

ized, high-speed frame relay network interface at digital signal level 3 (DS3),

with a line rate of 44.736 Mbps. Typically, this module is used to connect the

PSAX system to an ATM edge switch. Three light-emitting diode (LED) status

indicators provide the operational status of the module.



• ITU-T I.370 (frame relay policing)



• HDLC pass-through

Frame Relay The 1-Port Unchannelized DS3 Frame Relay module has interfaces for frame-

relay network-level interworking (FRF.5) and service-level interworking

(FRF.8). These features enable the PSAX system to act as a gateway betweenrouters, remote dial-access servers, IBM SNA equipment, and other devices

configured for frame-relay operation.

Frame relay policing, and user-selected point-to-point SVCs are supported on

the 1-Port Unchannelized DS3 Frame Relay module. Frame relay policing

enables the user to manage traffic at the user-network interface (UNI) or net-

work-network interface (NNI) by setting performance parameters such as the

committed information rate (CIR), excess burst size (Be), and committed

burst size (Bc).

HDLC Pass-through Each port on the 1-Port Unchannelized DS3 Frame Relay module can be con-

figured to perform adaptation for high-level data link control (HDLC) pass-

through. Without this feature, AAL1 adaptation would be required for data

from HDLC devices connected to a port on the 1-Port Unchannelized DS3

Frame Relay module. With this feature, AAL5 adaptation can be used to

allow HDLC data to be handled as if it were VBR rather than CBR. Since ATM

cells are only generated when HDLC is present, optimal bandwidth is used.

Hardware Features The 1-Port Unchannelized DS3 Frame Relay module has the following hard-

ware features:


• Connector type: 2 BNC connectors, 1 receive connector, and 1 transmit

connector

• Line rate: 44.736 Mbps (typical)• Line encoding mode: B3ZS

• Line type: C-bit parity

• Line build-out: short, long

• Bandwidth: 44,736 Kpbs

• Loopback capabilities: local loop, line loop




D-18 255-700-447


1-Port DS3 IMA Module (23N68)

The 1-Port DS3 IMA (Inverse Multiplexing over ATM) module combines the

features of the 1-Port Channelized DS3 Multiservice module (see the Packet-

Star ® PSAX 1-Port Channelized DS3 Multiservice Module User Guide) and the 6-

Port DS1 IMA module (see the PacketStar ® PSAX 6-Port DS1 IMA Module User

Guide). It allows you to configure up to 28 virtual T1 ports for native DS1ATM services or for as many as 14 independent IMA groups. This gives you

point-to-point bandwidth options between that of a single T1 line and that of

a T3 line.

Software Features The 1-Port DS3 IMA module supports the following protocols and services:

• Protocols: ATM, IMA (inverse multiplexing over ATM)

• ATM channelized services over IMA groups:

~ ATM UNI 3.0 and 3.1, with integrated link management interface (ILMI)

capability

~ Interim inter-switch signaling protocol (IISP) user and IISP network

~ ATM private network-network interface (PNNI)

Hardware Features The 1-Port DS3 IMA module provides the following hardware features:

• Front-End: DMA interface with one physical port

• Number of ports: one

• Port density: 28 virtual channels


mit data


• Bandwidth: 1.544 to 44.736 Mbps

2-Port E3 ATM Module (20N22)

The 2-Port E3 ATM module provides a network interface with a line rate of

34.368 Mbps. Typically, this module is used to connect the PSAX system to

an ATM edge switch. Each port can be configured for ATM service, including

ATM UNI 3.0, 3.1, and 4.0; IISP user and network; and ATM PNNI 1.0 inter-

faces. This module has three light-emitting diode (LED) indicators.

Software Features The 2-Port E3 ATM module uses ATM Forum specifications UNI 3.0 or

UNI 3.1, which allow either E3 port to act as a user network interface (UNI),

an interim inter-switch protocol (IISP) user or network interface, or as a

PNNI network interface to an ATM network.

Hardware Features The 2-Port E3 ATM module has the following hardware features:

• Number of ports: two

• Connector type: four BNC connectors for the two ports (each port has one




255-700-447 D-19



• Line rate: 34.368 Mbps (typical)

• Line encoding mode: HDB3

• Line type: G832


• Cell mapping: direct mapping

3-Port Unstructured DS3/E3 CES Module (23N02)

The 3-Port Unstructured DS3/E3 CES module provides a clear channel, high-

speed circuit emulation network interface at Digital Signal Level 3 (DS3),

with a line rate of 44.736 Mbps, or at E3, with a line rate of 34.368 Mbps.

Typically, this module is used to connect the Multiservice Media Gateway

system to an ATM edge switch via three ports. The dual-mode capability

allows the customer to deliver unchannelized and unframed traffic in North

American and international ATM networks from a single module. The 3-Port

Unstructured DS3/E3 CES module has three types of LED indicators: FAIL,

ACTIVE, and LOS (loss of signal).

Software Features Each port on the 3-Port Unstructured DS3/E3 CES module can be configured

to perform adaptation for circuit emulation. The implementation of ATM

Adaptation Layer 1 (AAL-1) allows for the transmission of circuit emulation

data as constant bit rate (CBR) traffic across an ATM network. Voice frames

are converted into ATM cells. With circuit emulation support, the 3-Port

Unstructured DS3/E3 CES module can adapt and concentrate circuit emula-

tion traffic onto an ATM network. This feature enables the Multiservice

Media Gateway system to interface with non-frame relay routers, video

encoders, encryption devices, and other devices that use a synchronous

interface.

Hardware Features The 3-Port Unstructured DS3/E3 CES module provides the following hard-

ware features:


• Connector type: 6 BNC connectors for the 3 ports (each port has one


• Line rate: 44.736 Mbps (DS3); 34.368 Mbps (E3)



• Line buildout: short (0–133 feet); long (134–266 feet)

• Framing mode: N/A



Appendix D PSAX Module FeaturesDSP2 Voice Servers

D-20 255-700-447


DSP2 Voice Servers

DSP2 x Voice Server Modules (23N27 (C), 23N29 (D), 23N26 (E), and 23N25 (F))

The DSP2 x Voice Server modules Series C through F process voice and other

digital data on a PSAX system to provide any or all of the following featuresto selected DS0 channels: toll quality voice compression, echo cancellation,

silence suppression, comfort noise insertion, fax demodulation/remodula-

tion, and Packet Pipe AAL5-to-AAL2 Wireless Trunking. All modules have

two types of LED indicators: FAIL and ACTIVE.

All DSP2 x Voice Server modules process circuit emulation voice traffic enter-

ing the chassis from any number of selected interface modules. The DSP2C

and DSP2D modules can also demodulate and remodulate fax signals.

All modules provide some or all of these features in conjunction with the

channelized CES modules, across the entire PacketStar PSAX Multiservice

Media Gateway product line.

Software Features The DSP2 x Voice Server Modules maintain required levels of voice quality

while conserving network bandwidth by using digital signal processor tech-

nology to compress voice traffic. See the DSP2x Voice Server Modules User Guide

for more information.

In System Software Release 8.0.0, the number of connections possible

through the DSP2D Voice Server module has been increased from 672 to

1008, when using the AAL1 mode and the AlgoSet5 voice processing feature

set.

Hardware Features Any number of DSP2 x Voice Server modules can be supported per chassis,within the allowed System Software Release parameters:

• The DSP2A and DSP2B modules require System Software Release 5.0.1 or

subsequent.

• The DSP2C module requires Release 6.2.0 or subsequent.

• The DSP2D module requires System Software Release 7.0.0 or subsequent.

• The DSP2E module requires System Software Release 7.1.2 or subsequent.

• The DSP2F module requires System Software Release 7.1.2 or subsequent.


6-Port E1 IMA Module (20N34)

The 6-Port E1 IMA module has six physical RJ-45 ports. The inverse multi-

plexing for ATM capabilities of this module permit a user to strap two to six

of the physical ports together to create ATM interfaces that support 4 to 12

Mbps of bandwidth. A maximum of three IMA groups may be configured per

module.



255-700-447 D-21


Appendix D PSAX Module FeaturesE1 Interface Modules

Source data enters the module from the backplane and is divided between

the ports within the IMA group specified in the virtual circuit connection.

The data leaves the front of the module and is transported across individual

E1 lines. At the destination IMA module, the E1 streams are merged back

together in correct order and passed on to other modules as directed by vir-

tual circuit connections. IMA dynamically handles conditions when E1s

within an IMA group become unavailable: the IMA "pipe" shrinks in band-width to the remaining E1s and continues to pass traffic. When a problem E1

comes back online, the IMA "pipe" will enlarge to take full advantage of the

restored bandwidth.

Software Features The 6-Port E1 IMA module offers ATM IMA services, including permanent

virtual circuits, soft permanent virtual circuits, and switched virtual circuits.

The module supports ATM UNI v3.a, IISP, PNNI, and ILMI. This functionality

enables service providers to offer multiple E1 IMA group services using a sin-

gle module.

Hardware Features The 6-Port E1 IMA module provides the following hardware features:


• Connector type: RJ-45 (120-Ohm symmetrical pair [4 wire + Frame

Ground] interface)



• Loopback capabilities: local loopback, line loopback

• Line buildout: N/A

• Framing mode: cyclic redundancy check multiframe (CRC-mf)

6-Port Enhanced E1 Multiservice Module (20N56)

The 6-Port Enhanced E1 Multiservice module has six physical ports, each

with a line rate of 2.048 Mbps. When a port is configured for channelized

service, 31 individual high-level data links (HDLCs) on a single E1 connec-

tion are provided, with a total of 180 HDLCs per module. This module pro-

vides a data service unit (DSU)/channel service unit (CSU) for each port so

that individual DS0s can be configured. With built-in CSU capability, the

module can interface directly to an E1 line with multiple repeaters. This fea-

ture allows the module to interface with a time-division multiplex (TDM)

channelized E1 circuit. The 6-Port Enhanced E1 Multiservice module pro-

vides the following interfaces:

• ATM IISP (network/user) • Circuit emulation

• ATM PNNI 1.0 • Frame Relay (UNI, NNI)

• ATM UNI 3.0, 3.1, and 4.0 • HDLC pass-through

• CAS trunkline • PRI ISDN (network/user)




D-22 255-700-447


The interfaces support ITU-T G.703 and ITU G.704. The module uses ATM

Forum Specification UNI 3.0 or UNI 3.1, which allows the E1 port to act as a

user-network interface (UNI), an interim interswitch protocol (IISP) user or

IISP network interface to an ATM network. Each port can be independently

configured to provide services for channelized and unchannelized frame

relay configurations, circuit emulation service, and ATM service. The module

can be configured to provide N x 64 Kbps (fractional E1) structured circuitemulation service. When configured for E1 circuit emulation service, the

module interfaces with TDM channelized E1 circuits. It converts channelized

data (usually voice data) to ATM virtual channels. The module can adapt a

maximum of 31 channels per port to ATM virtual channels with individual

virtual path identifiers (VPIs) and virtual channel identifiers (VCIs), using

structured (channelized) circuit emulation. Signaling bit transport from time

slot 16 is also provided, based on ATM Forum standards for channel-associ-

ated signaling (CAS). With the 64 Kbps “clear channel” capability, the mod-

ule can connect to a device using an integrated services digital network with

a primary rate interface (ISDN PRI) service. Because this structured circuit

emulation service can be configured to use only a fraction of the time slots,

several independent emulated circuits can be configured to share one service

interface.


• ATM: ATM UNI 3.0 and 3.1; Interim inter-switch signaling protocol (IISP)

user, IISP network


channel; dynamic bandwidth circuit emulation service (DBCES—propri-

etary version); 1 X 64 Kbps structured CAS; unstructured CES






Hardware Features The 6-Port Enhanced E1 Multiservice module has the following hardware

features:


• Connector type: RJ-45 (120-Ohm, symmetrical pair [4-wire] interface)



• Framing mode for CES: cyclic redundancy check-multifrequency (CRC-mf)(also known as CRC-4)

• Loopback capabilities: local loop, line loop




255-700-447 D-23



21-Port High-Density E1 IMA Module (23N34)

The 21-Port High-Density E1 IMA module provides a line rate of 2.048 Mbps

per port. The module’s inverse multiplexing for ATM capabilities permit a

user to strap 2 to 21 of the physical ports together to create ATM interfaces

that support up to 43 Mbps of bandwidth. A maximum of 10 IMA groups

may be configured per module.

This module offers native E1 ATM services and E1 IMA services, including

permanent virtual circuits, soft permanent virtual circuits, and switched vir-

tual circuits. The module supports the Traffic Shaping feature on ATM UNI

v3.n, UNI v4.0, IISP, PNNI, and ILMI interfaces. This functionality enables

service providers to offer both individual unchannelized E1 ATM services

(without IMA overhead) and multiple E1 IMA group services using a single

module.

Using the IMA protocol, this module provides an effective method of com-

bining the transport bandwidths of multiple E1 links that are grouped to col-

lectively provide higher intermediate rates. This technique involves inverse

multiplexing and de-multiplexing of ATM cells in a cyclical fashion among

links grouped to form a higher bandwidth logical link whose rate is approxi-

mately the sum of the link rates. This is referred to as an IMA group. From

the system’s viewpoint, these IMA groups are simply new ATM interfaces

sized as multiples of E1. (Refer to Inverse Multiplexing for ATM Version 1.1, af-

phy-0086.001.)

Software Features The 21-Port High-Density E1 IMA module supports the following protocols

and services:

• Protocols: ATM, IMA

• ATM services over IMA groups:

~ ATM UNI 3.0, 3.1, 4.0, and ILMI with traffic shaping

~ IISP user and IISP network with traffic shaping

~ ATM PNNI with traffic shaping

Hardware Features The 21-Port High-Density E1 IMA module provides the following hardware

features:


• Connector type: 2 Mini-Champ connectors



• Line encoding mode: HDB3 (default), AMI



• Framing mode: CRC4-CAS




D-24 255-700-447


21-Port High-Density E1 Multiservice Module (23N66)

The 21-Port High-Density E1 Multiservice module provides 21 ports, each

with a line rate of 2.048 Mbps. The interfaces support ITU-T G.703 and ITU

G.704. Each port can be independently configured to provide services for

channelized and unchannelized frame relay configurations, circuit emulation

service, and ATM service. This module has two types of light-emitting diode(LED) indicators: FAIL and ACTIVE.

Configured for channelized E1 service, the 21-Port High-Density E1 Multi-

service module maps up to 31 individual high level data links (HDLC) on a

single E1 connection (180 HDLC data links per module). This module pro-

vides a data service unit (DSU)/channel service unit (CSU) for each port in

order to configure individual channels. The module has a built-in CSU capa-

bility, which allows it to interface directly to an E1 line with multiple repeat-

ers. This feature allows the module to interface with a time-division multi-

plex (TDM) channelized E1 circuit.

You can configure the 21-Port High-Density E1 Multiservice module to pro-

vide N x 64 Kbps (fractional E1) structured circuit emulation service. When

configured for E1 circuit emulation service, the module interfaces with TDM

channelized E1 circuits. It converts channelized data (usually voice data) to

ATM virtual channels. This module can adapt a maximum of 31channels per


and virtual channel identifiers (VCIs), using structured (channelized) circuit

emulation. Signaling bit transport from time slot 16 is also provided, based

on ATM Forum standards for channel-associated signaling (CAS). With the

64 Kbps "clear channel" capability, this module can connect to a device using

an integrated services digital network with a primary rate interface (ISDN

PRI) service. Because this structured circuit emulation service can be config-

ured to use only a fraction of the time slots, you can configure several inde-

pendent emulated circuits to share one service interface.

The 21-Port High-Density E1 Multiservice module uses ATM Forum Specifi-cation UNI 3.0 or UNI 3.1, which allows any E1 port to act as a user network

interface (UNI), an interim inter-switch protocol (IISP) user or network

interface to an ATM network.

Software Features The 21-Port High-Density E1 Multiservice module supports the following

services:

• ATM: ATM UNI 3.0, 3.1 and 4.0; interim inter-switch signaling protocol

(IISP) user, IISP network; private network-network interface (PNNI) 1.0,

all with traffic shaping

• CAS Trunkline

• CE: Circuit emulation service (CES) with ISDN PRI using 64 Kbps clearchannel; 1 x 64 Kbps structured CAS; unstructured CES


• HDLC Passthrough with bit inversion






255-700-447 D-25


Appendix D PSAX Module FeaturesEthernet Interface Modules

Hardware Features The 21-Port High-Density E1 Multiservice module provides the following

hardware features:


• Connector type: two Mini-Champ connectors that mate with the Lucent

cable (COMCODE 300550639)


• Physical interfaces supported: ITU-T G.703, ITU G.704




• Framing mode: cyclic redundancy check multi-frame (CRC-mf)


4-Port Ethernet Module (23N40)

The 4-Port Ethernet module has four physical ports and a fifth, virtual port.

Each physical port has the ability to autosense to operate at either 10BASE-T

or 100BASE-T, and autonegotiate to automatically detect and switch to half-

or full-duplex port speeds. Each of the physical ports can be configured inde-

pendently to operate within shared or separate bridge groups. The module

has two types of LED indicators.

The module provides services for bridging from an Ethernet LAN to an ATM

WAN using RFC 2684 MAC layer bridging and both PVCs and SPVCs. VLAN

Ethernet frames can be passed transparently by this module.

Software Features The 4-Port Ethernet module supports the following software features. More

information on each feature is provided in the subsections that follow.

• Number of 10/100BASE-T autosensing and autonegotiating ports: 4

• Bridging (RFC 2684)—Includes the encapsulation of the MAC layer data

for filtering (see the PacketStar ® PSAX 4-Port Ethernet Module Guide for more

detail); supports up to 32 bridge groups

Note: RFC 2684 supercedes RFC 1483, but only RFC 1483 aspects are

supported on this module.

• VPLS over ATM:

~ Supports up to 32 bridge groups

~ Supports up to 120 connections

• Maximum number of virtual channels per bridge group: 15

• Maximum number of channels per virtual port (port 5): 120

• IP Forwarding

Note: The IP Forwarding feature is not to be confused with the kind of

routing capability that supports virtual channel multiplexed routed

packets or LLC-SNAP.

• ATM Traffic Shaping




D-26 255-700-447


• LLC and VC Encapsulation

• Multicasting

• Spanning Tree algorithm (IEEE 801.1 Ethernet)

• Maximum number of PVC connections per module: 120

Hardware Features The 4-Port Ethernet module provides the following hardware features:

• Number of ports:

~ physical ports: 4

~ virtual port used for backplane connections: 1


• Total MTU: 1,522 bytes for an Ethernet packet excluding FCS and exten-

sion

~ Maximum data payload: 1,500 bytes excluding preamble/SFD/MAC

addresses/length

~ Ethernet header: 22 bytes (7-byte preamble, 1-byte SFD, 12-byte MAC

address, 2-byte length/type)

• Total MTU: 1,522 bytes for an Ethernet packet excluding FCS and exten-

sion

~ Maximum data payload: 1,500 bytes excluding preamble/SFD/MAC

addresses/length

~ Ethernet header: 22 bytes (7-byte preamble, 1-byte SFD, 12-byte MAC

address, 2-byte length/type)

• Throughput:

~ Each port supports 10 Mbps (10BASE-T) or 100 Mbps (100BASE-T)

~ Maximum throughput: 294,118 pps (based on 64-byte packets, simplex

traffic flow, using two ports configured for 100 Mbps); the rate is approx-

imately 195 Mbps with zero percent loss

~ 235,000 frames per second (to and from the backplane), 64-byte packets

~ Theoretical maximum simplex rate: 297,620 packets per second (for two

100 Mbps ports using 64-byte packets)

~ 100% line rate (port-to-port) for up to three ports (64-byte packets)

~ 75% line rate (port-to-port) for four ports (64-byte packets)

• Measured latency range (when passing 90% traffic):

~ For 64-byte packets: 32 usec

~ For 1,472-byte packets: 72 usec

Note: Performance results may vary depending on the bridge group con-

figuration and the number of ports configured.• Maximum number of connections per module: 120



255-700-447 D-27



Ethernet Module (20N40)

The Ethernet module provides five ports on the faceplate and a sixth virtual

port. The first of these ports has the ability to autosense and operate at either

10BASE-T or 100BASE-T. The remaining four ports operate at 10BASE-T.

Each of the ports can be configured independently to operate within shared

or separate bridge groups. The virtual port provides 70 virtual channels thattransmit data through the backplane. The Ethernet module has two types of

LED indicators.

The module provides services for bridging from an Ethernet LAN to an ATM

WAN using RFC 2684 MAC layer bridging and both PVCs and SPVCs. The

Ethernet module incorporates bridging and bridge management. VLAN

Ethernet frames can be passed by this module, but IEEE 802.1 VLAN process-

ing is not supported.

Software Features The Ethernet module supports the following software features:

• Bridging (RFC 2684)—Includes the encapsulation of the MAC layer data

for filtering and bridge management (see "Bridging"the PacketStar ® PSAX 4-

Port Ethernet Module Guide for more detail); supports up to five bridge

groups

• PVC connections (70 maximum)

• Spanning Tree algorithm (IEEE 801.1 Ethernet)

• IP Forwarding

Note: The IP Forwarding feature is not to be confused with the kind of

routing capability that supports virtual channel multiplexed routed

packets or LLC-SNAP. Do not apply the Routing interface type to

Ethernet virtual channels.

• Multicasting—If the module receives multicast packets from the Route

Server module, the module will flood the Ethernet packet multicast

address to all physical ports and virtual channels in a bridge group.

Hardware Features The Ethernet module provides the following hardware features:


~ physical ports: 5

~ virtual port used for backplane connections: 1


• Line rate: NA

• Total SDRAM: 64 MB

• Module program and data space: 8 MB• Maximum input buffer: 4 MB

• Output buffer: 4 MB

• Maximum power consumption: 16 W

• Total maximum transmission unit (MTU): 1514 bytes

~ Maximum data payload: 1500 bytes

~ Ethernet header: 14 bytes

• Physical interfaces supported:





255-700-447 D-29


Appendix D PSAX Module FeaturesFiber-Optic Interface Modules



~ Channel-associated signaling (CAS) 1x56

• AAL2 cell formatting for interworking with the DSP2x Voice Server mod-

ules.

The following feature is provided with limited support by the module:



Hardware Features The 1-Port Channelized OC-3/STM-1 CES modules have the optical specifi-

cations shown in Table D-2.

1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module(23N75 (MM)/23N76 (SM))

The 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM modules

(23N75 (MM) and 23N76 (SM)) have two operating modes:

• The STM-1 mode offers 63 VC-12 (E1) channels for ATM services only.

• The OC-3 mode offers 84 VT1.5 (DS1) channels for unstructured CES ser-

vices only.

Table D-2. 1-Port Channelized OC-3/STM-1 CES Module Optical Specifications

FeatureModule

Ch OC-3/STM-1 CES SM Ch OC-3/STM-1 CES MM

Number of ports 1 1Type of connector (two for each mod-

ule, transmit and receive)

SC (snap-on connector) SC (snap-on connector)

Type of fiber optic cable single-mode multimode

Fiber optic cable reach (approximate,

depending on fiber makeup)

15 km (9.3 miles) 2 km (6,560 feet or 1.2

miles)

Line rate, per port 155 Mbps (SONET) 155 Mbps (SONET)

Optical wavelength (nominal value) 1,310 nm 1,310 nm

Optical input sensitivity -31 to -8 dBm -30 to -14 dBm

Optical output power -15 to -8 dBm -20 to -14 dBm

Transmitter minimum optical outputpower (average)

-15 dBm -20 dBm

Transmitter maximum optical output

power (average)

-8 dBm -14 dBm

Receiver minimum optical input power

(average)

-31 dBm -30 dBm

Receiver maximum optical input

power (average)

-8 dBm -14 dBm




D-30 255-700-447


The 1+1 APS/MSP protection is supported in either mode. The 1+1 APS/MSP

linear protection architecture consists of a far-end signal that is continuously

bridged (at the electrical level) to the APS working and APS protection I/O

modules so that the same payloads are transmitted identically to the near-

end working and protection I/O modules. At the near-end, the working and

protection OC-3 or STM-1 signals are monitored independently and identi-

cally for failures. The receiving I/O modules select either the working or theprotection signal as the one from which to select the traffic, based on switch

initiation criteria. Because of the continuous far-end bridge, the 1+1 architec-

ture does not allow an unprotected extra traffic channel to be provided.

The modules are supplied with the following transmission types:

• The single-mode (SM) module (23N76) is intended for long-reach applica-

tions, typically between LANs. This module is frequently used to connect

high-speed LAN devices (such as routers) to an ATM network.

• The multimode (MM) module (23N75) is intended for short-reach applica-

tions, for example, connecting interoffice or intraoffice sections of a local

area network (LAN).

For instructions on configuring and guidance on using these modules, see thePacketStar PSAX 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Modules

User Guide.

Software Features These modules use the AQueMan algorithm for traffic flow control. The

modules also support these interfaces:

• ATM IISP (Network/User) (supported only in the STM ATM mode)

• ATM PNNI 1.0 (supported only in the STM ATM mode)

• ATM UNI 4.0 (supported only in the STM ATM mode)

• ATM UNI 3.0/3.1 (supported only in the STM ATM mode)

• Circuit emulation (supported only in the OC-3 UCE mode)

Hardware Features The 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM modules have

the optical specifications shown in Table D-3.

Table D-3. 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module Optical Specifications

Feature

Module

CH OC-3/STM-1UNSTR/ATM SM

CH OC-3/STM-1UNSTR/ATM MM

Number of ports 1 1

Type of connector (two for each module, trans-

mit and receive)

SC (snap-on connec-

tor)

SC (snap-on connec-

tor)


Fiber optic cable reach (approximate, depend-

ing on fiber makeup)

15 km (9.3 miles) 2 km (6,560 feet or

1.2 miles)

Line rate, per port 155 Mbps 155 Mbps






255-700-447 D-31



4-Port OC-3c/STM-1 Module (24N72 (MM)/24N73 (SM))

The 4-Port OC-3c/STM-1 modules (24N72 (MM) and 24N73 (SM)) provide

four independent, full-rate OC-3c or STM-1 ATM interfaces protected by 1+1

APS/MSP on a port by port, inter-module basis. The OC-3c or STM-1 modes

are sofware selectable on a module basis.

The linear 1+1 APS OC-3c/STM-1 feature provides protection against facility,

port or module failure. The 1+1 APS/MSP linear protection architecture con-

sists of a far-end signal that is continuously bridged (at the electrical level) to

the APS working and APS protection I/O modules so that the same payloads

are transmitted identically to the near-end working and protection I/O mod-

ules. At the near-end, the working and protection OC-3 signals are moni-

tored independently and identically for failures. The receiving I/O modules

select either the working or the protection signal as the one from which to

select the traffic, based on switch initiation criteria. Because of the continu-

ous far-end bridge, the 1+1 architecture does not allow an unprotected extra

traffic channel to be provided.

The modules provide connection redundancy between parallel ports on both

APS/MSP-protection modules on a strict one-to-one mapping, enabling reli-

able data transport. The mapping must be port x on the working module to

port x on the APS/MSP protection module, for all ports 1 through 4. “Cross-

port protection” configuration of port 1 (working) to any port on the

APS/MSP protection module other than Port 1, or vice versa, is not permitted

on any port. The modules provide a fiber-optic interface operating in the con-

catenated mode of the SONET-defined line rate of 155 Mbps.

The module is supplied with the following transmission types:• Single-mode (SM) module (23N76) is intended for long-reach applications,

typically between LANs. This module is frequently used to connect high-

speed LAN devices (such as routers) to an ATM network.

• Multimode (MM) module (23N75) is intended for short-reach applications,

for example, interoffice or intraoffice sections of a local area network

(LAN).

Transmitter minimum optical output power

(average)

-15 dBm -20 dBm

Transmitter maximum optical output power

(average)

-8 dBm -14 dBm

Receiver minimum optical input power (aver-

age)

-31 dBm -30 dBm

Receiver maximum optical input power (aver-

age)

-8 dBm -14 dBm

Table D-3. 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module Optical Specifications

Feature

Module

CH OC-3/STM-1UNSTR/ATM SM

CH OC-3/STM-1UNSTR/ATM MM




D-32 255-700-447


Software Features The modules support ATM traffic shaping, and conform to af-tm-0121.000,

Traffic Management Specification 4.1 (see the appropriate PSAX module user

guide for more details).

Hardware Features The 4-Port OC-3c/STM-1 modules have the optical specifications shown inTable D-4.

1-Port OC-12c/STM-4c Module (23N72 (MM)/23N73 (SM))

The 1-Port OC-12c/STM-4c APS/MSP module (23N72 (MM)/23N73 (SM))

provides connection redundancy to convey data reliably for access applica-

tions. These modules provide a fiber-optic interface operating in the concate-nated mode with a line rate of 622.08 Mbps.

The 1:1 protection implementation is compliant with the GR-253-CORE

standard and supports linear non-revertive 1:1 protection, in both bidirec-

tional and unidirectional modes.

The module is supplied with the following transmission types:

Table D-4. 4-Port OC-3c/STM-1 Module Optical Specifications

FeatureModule

OC-3c/STM-1 SM OC-3c/STM-1 MM

Number of ports 4 4

Type of connector (two for each module,

transmit and receive)

SC

(snap-on

connector)

SC

(snap-on

connector)




15 km

(9.3 miles)

2 km

(6,560 feet or 1.2

miles)


Line rate, module total 622.08 Mbps (SONET) 622.08 Mbps (SONET)




Transmitter minimum optical output

power (average)

-15 dBm -20 dBm


power (average)

-8 dBm -14 dBm


(average)

-31 dBm -30 dBm

Receiver maximum optical input power

(average)

-7 dBm -14 dBm



255-700-447 D-33



• Single-mode (SM) module (23N73) is intended for long-reach applications,





(LAN).

Both versions of the module can operate in an OC-12c or an STM-4c mode.

Software Features The 1-Port OC-12c/STM-4c 1+1 APS/MSP modules follow the ATM Forum

Traffic Management 4.1 standard of traffic prioritization.

Hardware Features The 1-Port OC-12c/STM-4c modules have the optical specifications shown in

Table D-5.

1-Port OC-3c Module with AQueMan (20N12 (MM)/20N13 (SM)) orTraffic Shaping (20N14 (MM)/20N15 (SM))

The 1-Port OC-3c with AQueMan (20N12 (MM)/20N13 (SM)) or TrafficShaping (20N14 (MM)/20N15 (SM)) modules provide a fiber optic interface

operating at the OC-3c rate in the concatenated mode of the SONET-defined

line rate of 155 Mbps.


• Single-mode (SM) module (20N13/20N15) is intended for long-reach

applications, typically between LANs. This module is frequently used to

connect high-speed LAN devices (such as routers) to an ATM network.

Table D-5. 1-Port OC-12c/STM-4c Module Optical Specifications

Feature Single-Mode Multimode

Number of ports 1 1

Type of connector (two for each mod-






15 km (9.3 miles) 500 meters (1,640 feet)

Line rate, per port 622.08 Mbps 622.08 Mbps



power

-15 dBm -20 dBm

Transmitter maximum optical outputpower

-8 dBm -14 dBm


(average)

-28 dBm -29 dBm


(average)

-7 dBm -11 dBm




D-34 255-700-447


• Multimode (MM) module (20N12/20N14) is intended for short-reach

applications, for example, interoffice or intraoffice sections of a local area

network (LAN).

Software Features These modules are available in two variations, which differ according to the

firmware installed in the module.

• The 1-Port OC-3c MM AQ and OC-3c SM AQ modules use the AQueMan

algorithm for flow control.

• The 1-Port OC-3c MM TS and OC-3c SM TS modules use traffic shaping

(TS) for flow control. See the appropriate PSAX system user guide for more

information on traffic shaping.

Hardware Features The 1-Port OC-3c modules with AQueman or Traffic Shaping have the opti-

cal specifications shown in Table D-6.

Table D-6. 1-Port OC-3c Module with AQueman or Traffic Shaping Optical Specifications

Feature

Module

OC-3c (SM AQ) orOC-3c (SM TS)

OC-3c (MM AQ) orOC-3c (SM TS)

Number of ports 1 1

Type of connector (two for each mod-


SC

(snap-on

connector)

SC

(snap-on

connector)




15 km

(9.3 miles)

2 km

(6,560 feet or 1.2

miles)

Line rate 155 Mbps (SONET) 155 Mbps (SONET)Optical wavelength (nominal value) 1,310 nm 1,310 nm

Optical input sensitivity -31 to -8 dBm -32.5 to -14 dBm


System gain 15 dB 13.5 dB


power (average)

-15 dBm -20 dBm


power (average)

-8 dBm -14 dBm


(average)

-31 dBm -32.5 dBm


(average)

-8 dBm -14 dBm



255-700-447 D-35



1-Port OC-3c 1+1 APS Module (20N72 (MM)/20N73 (SM))

The 1-Port OC-3c 1+1 Automatic Protection Switching (APS) modules pro-

vide connection redundancy, enabling reliable data transport. These modules

provide a fiber-optic interface operating in the concatenated mode of the

SONET-defined line rate of 155 Mbps.







(LAN).

Software Features The 1-Port OC-3c 1+1 APS modules use the AQueMan algorithm for traffic

flow control.

Hardware Features The 1-Port OC-3c 1+1 APS modules have the optical specifications shown in

Table D-7.

Table D-7. 1-Port OC-3c 1+1 APS Module Optical Specifications

FeatureModule

Single-Mode Multimode

Number of ports 1 1



SC

(snap-on

connector)

ST

(straight

tip)




15 km

(9.3 miles)

2 km

(6,560 feet or 1.2

miles)






power (average)

-15 dBm -20 dBm


power (average)

-8 dBm -14 dBm


(average)

-31 dBm -30 dBm


(average)

-8 dBm -14 dBm




D-36 255-700-447


1-Port STM-1 Module with AQueMan (20N62 (MM)/20N63 (SM)) orTraffic Shaping (20N64 (MM)/20N65 (SM))

The 1-Port STM-1 with AQueMan (20N62 (MM)/20N63 (SM)) or Traffic

Shaping (20N64 (MM)/20N65 (SM)) modules provide a fiber optic interface

operating in the concatenated mode of the SONET-defined line rate of

155 Mbps.


• Single-mode (SM) module (20N63/20N65) is intended for long-reach

applications, typically between LANs. This module is frequently used to

connect high-speed LAN devices (such as routers) to an ATM network.

• Multimode (MM) module (20N62/20N64) is intended for short-reach

applications, for example, interoffice or intraoffice sections of a local area

network (LAN).

These modules are available in two variations, which differ according to the

firmware installed on the circuit boards:

• One variation for both the Multimode and Single-Mode types, with thenames 1-Port STM-1 MM AQ module and 1-Port STM-1 SM AQ module,

uses the AQueMan algorithm for flow control.

• The other variation for both the Multimode and Single-Mode types, with

the names 1-Port STM-1 MM TS module and 1-Port STM-1 SM TS module,

uses traffic shaping for flow control. See Chapter 3 of the appropriate PSAX

system user guide for more information on traffic shaping.

Software Features The software also supports the following traffic management features:

~ AAL-5 (traffic shaping)

~ Ten quality of service (Qos) levels:

• Constant bit rate level 1 (CBR-1), CBR-2, CBR-3, and CBR-4• Variable bit rate (VBR): VBR real time level 1 (VBR-RT1), VBR real

time level 2 (VBR-RT2), VBR non-real time level 1 (VBR-NRT1), VBR

non-real time level 2 (VBR-NRT2), VBR-express

• Unspecified bit rate (UBR)

Hardware Features The 1-Port STM-1 modules have the optical specifications shown in

Table D-8.

Table D-8. 1-Port STM-1 Module Optical Specifications

Feature

Module

STM-1 (SM TS) orSTM-1 (MM AQ)

STM-1 (MM TS) orSTM-1 (MM AQ)

Number of ports 1 1



SC

(snap-on

connector)

ST

(straight tip)

Type of fiber-optic cable single-mode multimode



255-700-447 D-37



1-Port STM-1 1+1 MSP Module (20N92 (MM)/20N93 (SM))

The 1-Port STM-1 1+1 MSP (20N92 (MM)/20N93 (SM)) modules provide

connection redundancy, enabling reliable data transport. These modules pro-vide a fiber-optic interface operating in the concatenated mode of the

SONET-defined line rate of 155 Mbps.

The 1+1 protection implementation is compliant with the GR-253-CORE

standard and supports linear non-revertive 1+1 protection, in both bidirec-

tional and unidirectional modes. Non-revertive, or non-automatic, switch-

back reduces a service interruption due to link failure from two interruptions

to one interruption.




speed LAN devices (such as routers) to an ATM network.• Multimode (MM) module (20N92) is intended for short-reach applications,


(LAN).

Software Features The STM-1 1+1 MSP modules use the AQueMan algorithm for traffic flow

control.

Fiber-optic cable reach (approximate,


15 km

(9.3 miles)

2 km

(6,560 feet or 1.2miles)

Line rate 155 Mbps 155 Mbps

Optical wavelength

(nominal value)

1,310 nm 1,310 nm

Optical input sensitivity -31 to -8 dBm -32.5 to -14 dBm


System gain 15 dB 13.5 dB


(average)

-15 dBm -20 dBm

Transmitter maximum optical output power(average) -8 dBm -14 dBm


(average)

-31 dBm -32.5 dBm


(average)

-8 dBm -14 dBm

Table D-8. 1-Port STM-1 Module Optical Specifications (Continued)

Feature

Module

STM-1 (SM TS) orSTM-1 (MM AQ)

STM-1 (MM TS) orSTM-1 (MM AQ)




D-38 255-700-447


Hardware Features The 1-Port STM-1 1+1 MSP modules have the optical specifications shown in

Table D-9.

2-Port OC-3c/STM-1 ATM Module (24N70 (MM)/24N71 (SM))

The 2-Port OC-3c/STM-1 ATM modules (24N71 (SM) and 24N70 (MM))

provide two independent, full-rate OC-3c or STM-1 ATM interfaces protected

by 1+1 APS/MSP on a port by port, inter-module basis. The OC-3c or STM-1

modes are software selectable on a module basis and both multimode and

single-mode variants are offered. The modules provide a fiber-optic interface

operating in the concatenated mode of the SONET-defined line rate of

155 Mbps.

The linear 1+1 APS/MSP OC-3c/STM-1 feature provides protection againstfacility, port, or module failure. The 1+1 APS/MSP linear protection architec-

ture consists of a far-end signal that is continuously bridged (at the electrical

level) to the APS working and APS protection I/O modules so that the same

payloads are transmitted identically to the near-end working and protection

I/O modules. At the near-end, the working and protection OC-3c signals are

monitored independently and identically for failures. The receiving I/O mod-

ules select either the working or the protection signal as the one from which

Table D-9. 1-Port STM-1 1+1 MSP Module Optical Specifications

FeatureModule

STM-1 SM MSP STM-1 MM MSP

Number of ports 1 1



SC

(snap-on

connector)

ST

(straight tip)

Type of fiber-optic cable single-mode multimode

Fiber-optic cable reach (approximate,


15 km

(9.3 miles)

2 km

(6,560 feet or 1.2

miles)


Optical wavelength

(nominal value)

1,310 nm 1,310 nm




(average)

-15 dBm -20 dBm

Transmitter maximum optical output power

(average)

-8 dBm -14 dBm


(average)

-31 dBm -30 dBm


(average)

-8 dBm -14 dBm



255-700-447 D-39



to select the traffic, based on switch initiation criteria. Because of the contin-

uous far-end bridge, the 1+1 APS/MSP architecture does not allow an unpro-

tected extra traffic channel to be provided.

The modules provide connection redundancy between parallel ports on both

APS/MSP-protection modules on a strict one-to-one mapping, enabling reli-

able data transport. The mapping must be port n on the working module toport n on the protection module, for both ports. “Cross-port protection” con-

figuration of port 1 (working) to any port on the protection module other

than port 1, or vice versa, is not permitted on any port.

The modules are supplied with the following transmission types:

• The single-mode (SM) module (24N71) is intended for long-reach applica-

tions, typically between LANs. This module is frequently used to connect

high-speed LAN devices (such as routers) to an ATM network.

• The multimode (MM) module (24N70) is intended for short-reach applica-

tions, for example, connecting interoffice or intraoffice sections of a local

area network (LAN).

Software Features The modules support ATM traffic shaping, and conform to af-tm-0121.000,

Traffic Management Specification 4.1 (see the appropriate PSAX module user

guide for more details).

Hardware Features The 2-Port OC-3c/STM-1 modules have the optical specifications shown in

Table D-10.

Table D-10. 2-Port OC-3c/STM-1 ATM Module Optical Specifications

FeatureModule

OC-3c/STM-1 SM OC-3c/STM-1 MM

Number of ports 2 2







15 km (9.3 miles) 2 km (6,560 feet or

1.2 miles)


Line rate, module total 310 Mbps 310 Mbps



power (average)

-15 dBm -20 dBm


power (average)

-8 dBm -14 dBm


(average)

-31 dBm -30 dBm


(average)

-7 dBm -14 dBm



Appendix D PSAX Module FeaturesOther Server Modules

D-40 255-700-447



Enhanced Router Module (23N41)

The Enhanced Router module is the premier IP routing platform for the

PacketStar PSAX Multiservice Media Gateway systems. In addition to support-ing existing PSAX multiservice interworking capabilities, the module pro-

vides routing, aggregation, and adaptation capabilities. The key feature added

in Release 9.0.0 is support for SPVC connection options.

The module also builds on the existing functionality of the Route Server

module by offering dynamic routing capabilities such as:

• IP forwarding performance of 540 Mbps simplex cell bandwidth at

64 bytes, IP packets

• IP services from I/O modules routed where I/O modules have IP over

frame relay, IP over ATM, or IP over Ethernet traffic

• Eight virtual router instances supporting eight independent VPNs

• Static routing• Routing information protocol (RIP) v1, v2 including variable length subnet

mask (VLSM)

• Classless inter-domain routing (CIDR) interoperability with other routers

In addition, Phase 1b also supports the new ERM-to-ATM VCC SPVC con-

nection type.

The module parses traffic (using IP filtering) and aggregates the traffic back to

the network backbone routers and switches, or directly to data centers where

the hosting applications reside.

Software Features The Enhanced Router module has the following software features:

• Protocols supported:

~ ICMP (RFC 792)

~ ARP (RFC 2225)

~ Inverse ARP over ATM and frame relay (receives and responds to

requests only)

~ RIP v1, v2 including VLSM (RFC 1058)

The module routes IP among various interfaces, particularly:

~ IP over frame relay (RFC 2427)

~ IP over Ethernet (bridge) (RFC 2684)

~ IP over ATM (RFC 2684) IP over HDLC (over N x DS0s over T1 or E1)

Note: RFC 2684 supersedes RFC 1483, RFC 2225 supersedes RFC 1577,and RFC 2427 supersedes RFC 1490.

• Multi-service routing:

~ Static routing

~ Dynamic protocol-driven routing, includingRIP

• CIDR (RFC 1517–1520)

• Eight VPNs



255-700-447 D-41



• IP filtering

• Interoperability with other basic routers

Hardware Features The Enhanced Router module has the following hardware features:

• Number of ports: 0 (server module)

• IP forwarding performance of 540 Mbps simplex cell bandwidth at

64 bytes, IP packets

• Maximum frame size, including the header:

~ ATM: 9,180 bytes

~ Frame relay: 1,500 bytes

~ Ethernet: 1,500 bytes

~ PPP over HDLC: 1,500 bytes

~ Cisco HDLC: 1,500 bytes

Route Server Module (20N41)

The Route Server module supports internet protocol (IP) virtual private net-

works (VPNs). Each VPN supports routing information protocol (RIP version

1 and version 2) and can be assigned to multiple IP interfaces and static

routes. The module can interact with any other Multiservice Media Gateway

module port that is configured for frame relay, bridge, or asynchronous

transfer mode (ATM). All traffic on the Route Server module runs through IP

in compliance with media access control (MAC) encapsulation:

• IP over ATM (RFC 2684)

• IP over frame relay (RFC 2427)

• IP over Ethernet

Note: RFC 2684 supercedes RFC 1483. The Route Server module supports

RFC 1483 and RFC 2684, but RFC 2685 (VPN identification) is not

supported. RFC 2427 supersedes RFC 1490.

These interfaces can be mixed (that is, IP over ATM to IP over frame relay),

but may be routed same service type to same service type. Further, the traffic

can come from any I/O module supporting this traffic type.

The Route Server module can be configured through either the Multiservice

Media Gateway system console or through the simple network management

protocol (SNMP). Each Multiservice Media Gateway system may support

multiple Route Server modules, but multiple Route Server modules cannot

be configured for hot-standby redundancy purposes.

Software Release 6.3.0 introduces routing information protocol (RIP) Version

2 to the Route Server module. The module now supports Internet Protocol

virtual private networks (VPNs) by assigning multiple IP network interfaces

and static routes. (The Route Server module also supports RIP v1.0, and can

interact with any other PSAX module port that is configured for frame relay,

Ethernet bridging, or ATM.)




D-42 255-700-447


Release 6.3.0 software, supporting RIP v2.0, allows you to divide networks to

a further extent than the traditional subnet classes (Class A, B, and C) avail-

able with RIP v1.0. RIP v2.0 enables authentication and multicasting, and

allows you to run different masks on different subnets. Rip v2.0 can be either

active or passive.

You can assign an authentication password to an IP network interface formaximum security. Doing so can prevent those who cannot directly access

the network from sending false routing information to the routers. RIP v1.0

messages will be ignored when authentication is in use. However, authenti-

cation does not prevent RIP v1.0 routers from viewing RIP v2.0 messages. To

prevent RIP v1.0 routers from viewing RIP v2.0 messages, you must use mul-

ticasting.

Multicasting reduces load on hosts not using RIP v2.0 messages. Multicasting

also allows RIP v2.0 routers to share information that RIP v1.0 routers can-

not access. Available bandwidth becomes the tiebreaker in calculating routes

using default parameters for both IISP and PNNI routing.

Software Features The Route Server module has the following hardware features:• Supported Interfaces:

~ IP over ATM (RFC 2684), RFC 2684 supercedes RFC 1483.

~ IP over frame relay (IRFC 2427)

~ IP over Ethernet (bridge) (RFC 2684)

• Multi-service routing:

~ Internet Control Message Protocol (RFC 792)

~ Static routing with six independent VPNs

~ IP routing

~ Frame relay (FRF.5, FRF.8)

~ ATM• Maximum frame size, including the header (the maximum Ethernet, frame

relay, or ATM frames that can be received by the Enhanced Router mod-

ule): 1518 bytes

Hardware Features The Route Server module has the following hardware features:

• Number of ports: 0 (server module)

• Total SDRAM: 64 MB

• Module program and data space: 8 MB

• Maximum input buffer: N/A

• Output buffer: N/A• Maximum power consumption: 15 W

• Performance parameters for forwarding IP packets (measured in packets

per second; all parameters include header):

~ 64-byte IP packet size: 22K pps (11.3 Mbps)

~ 256-byte IP packet size: 16K pps (32.8 Mbps)

~ 1500-byte IP packet size: 4.6K pps (55.8 Mbps)



255-700-447 D-43



• Maximum frame size: 1518 bytes; that is, the maximum Ethernet, frame

relay, or ATM frame that can be received by the Route Server module is

1518 bytes

• Maximum traffic into/out of module: 30 Mbps

Tones and Announcements Server Module (23N28)

The Tones and Announcements Server (TAS) module offers these tests in a

switch-to-switch capacity:

~ SS7 (Signaling System 7) continuity test for VToA

~ 1004 Hz (miliwatt) test tone support (Type 102)

~ Digital, non-inverting loopback (Type 108)

~ Automatic Transmisson measurement( Type 105)

These tests enable PSAX products to provide tones and signaling testing on

voice equipment in the customer’s premises, such as PBXs. Designed for use

between central office products, such as the PSAX 2300 and the PSAX 1250,and edge devices such as the AC 60 and the PSAX 20, the module offers call

routing information to a connection gateway without using an expensive cir-

cuit switch. Up to 128 circuits can be tested simultaneously using the TAS

Server Module.

The SS7 Continuity Test enables PSAX products to be deployed with other

applications in connection gateways involving hand-offs to ILECs which

require the quality assurance of conducting the continuity test from the cir-

cuit switch.

The test features work in conjunction with the Enhanced DS1, the Enhanced

E1, the High-Density E1/DS1, the Channelized DS3/STS-1e, the CPU mod-

ule, and a Connection Gateway Application Programming Interface (API).

Software Features The TAS module offers these features:

• TAS module can transmit tones and announcements towards the CES or

ATM side

• Maximum duration of a tone or announcement is 45 seconds (240Kb)

• Channel Associated Signaling

• Special Information Tones

Special InformationTones (SIT)

Telephone calls that are not completed as desired usually terminate in

recorded announcements or call progress tones. A special information tone is

sent to the caller in cases where neither the busy or congestion tone can give

the required information for call failure. Automated detection devices cannotdistinguish recorded voice from live voice answer unless a machine-detect-

able signal is included the recorded announcement. Defined SITs identify

network-provided announcements.

Channel AssociatedSignaling (CAS)

• Supports extended super frame (ESF) CAS signaling

• For each CES port, users can select from these signaling modes:

~ Loop-start, network (default) and User

~ Ground-start, network and User



Appendix D PSAX Module FeaturesSerial Interface Modules

D-44 255-700-447


~ Wink-start, 2-way and User

~ Off-premises station (OPS)

Tones • Busy tone

Hardware Features The Tones and Announcements Server module has 32 digital signal processer

chips. All TAS modules connect to the CPU and other modules by a back-

plane connection.

The number of Tones and Announcements Server modules supported by the

PSAX 4500, PSAX 2300, PSAX 1250, and PSAX 1000 Multiservice Media

Gateways depends on how your network configuration is affecting PSAX

System CPU memory availability. (See the Power Consumption table in the

Memory Allocation and Power Consumption section of this document to cal-

culate your network load). A TAS module can be placed in any available I/O

slot on these chassis.


6-Port Multiserial Module (20N07)

The 6-Port Multiserial module provides several types of serial data interfaces,

with a maximum line rate of 2.048 Mbps, and a maximum aggregate rate of

4 Mbps.

Bit Stuffing and CESConversion

The module also supports bit stuffing and 56K–64K circuit emulation service

(CES) conversion.

The framing for SS7's Message Transfer Part (MTP) Level 2 is a modified ver-sion of HDLC. The difference between SS7 MTP framing and standard HDLC

is in the opening and closing 1-byte flag. SS7 MTP messages use only the

closing flag. In order to support external SS7 transport requirements, it is

necessary to exchange information via T1 circuits where each 64 Kbps DS0 of

the T1 is filled with 56 Kbps of SS7 data and 8 Kbps of overhead (stuffing)

data.

The SS7 circuits originating from the Multiserial interface can be mapped

using AAL1 to an individual ATM constant bit rate (CBR) class of service

exiting on a DS3 ATM cell-bearing interface. At the far-end, the ATM circuit

is adapted (based on AAL-1 adaptation) to a native Multiserial (TDM) or CES

(TDM) circuit. SS7 traffic can originate from the Multiserial interface and ter-

minate on the Enhanced DS1 interface.

Interfaces The interfaces support RS-232 (synchronous and asynchronous), EIA-449,

EIA-530, V.351, X.21, and Kg. For synchronous interfaces, each port can be

independently configured as either data terminating equipment (DTE) or

data communications equipment (DCE). Each port can be independently

1 V.35 has been superceded by V.11. Although the V.35 protocol is a subset of V.11,

V.35 more accurately describes the module’s capabilities.



255-700-447 D-45



configured for frame relay, circuit emulation, terminal emulation, HDLC

passthrough, and asynchronous transfer mode (ATM) (using limitless ATM

network [LANET] protocol).

Software Features The 6-Port Multiserial module provides the following software features:

• ATM: ATM UNI 3.0, 3.1, and 4.0• CE: Circuit emulation service (CES)



• Terminal emulation




The following sections explain the application of the interfaces supported on

the 6-Port Multiserial module: frame relay, circuit emulation, terminal emu-

lation, HDLC pass-through, and ATM.

Frame Relay The 6-Port Multiserial module has interfaces for frame-relay network-level

interworking (FRF.5) and service-level interworking (FRF.8). A maximum of

350 permanent virtual circuits (PVCs) can be assigned on each frame relay

user-network interface (UNI) port. These features enable the Multiservice

Media Gateway system to act as a gateway between routers, remote dial-

access servers, IBM SNA equipment, and other devices configured for frame-

relay operation.

Frame relay policing, and user-selected point-to-point SVCs are supported on

the 6-Port Multiserial module. Frame relay policing enables the user to man-

age traffic at the user-network interface (UNI) or network-network interface

(NNI) by setting performance parameters such as the Committed Information

Rate (CIR), Excess Burst size (Be), and Committed Burst size (Bc).

Circuit Emulation Each port on the 6-Port Multiserial module can be configured to perform

adaptation for circuit emulation. The implementation of ATM Adaptation

Layer 1 (AAL-1) allows for the transmission of circuit emulation data as Con-

stant Bit Rate (CBR) traffic across an ATM network. With circuit emulation

support, the 6-Port Multiserial module can adapt and concentrate circuit

emulation traffic onto an ATM network. This feature enables the Multiser-

vice Media Gateway system to interface with non-frame relay routers, video

encoders, encryption devices, and other devices which use a synchronous

interface.

Terminal Emulation Each port on the 6-Port Multiserial module can be configured to perform an

adaptation for terminal emulation. The implementation of ATM AdaptationLayer 5 (AAL-5) allows for the transmission of terminal emulation data as

Variable Bit Rate (VBR) traffic across an ATM network. With terminal emula-

tion support, the 6-Port Multiserial module can adapt and concentrate termi-

nal emulation traffic onto an ATM network. This feature enables the Multi-

service Media Gateway system to interface with terminal equipment such as

monitors, craft interfaces, console ports, sensors, and other devices imple-

menting an asynchronous interface.




D-46 255-700-447


HDLC Passthrough Each port on the 6-Port Multiserial module can be configured to perform

adaptation for high-level data link control (HDLC) pass-through. Without

this feature, AAL-1 adaptation would be required for data from HDLC

devices connected to a port on the 6-Port Multiserial module. With this fea-

ture, AAL-5 adaptation can be used to allow HDLC data to be handled as if it

were VBR rather than CBR. Since ATM cells are only generated when HDLC

is present, optimal bandwidth is utilized.

ATM Each port on the 6-Port Multiserial module can be configured for ATM ser-

vice as per the ATM Forum’s UNI 3.0, 3.1, and 4.0 specifications. With this

feature, a port on the 6-Port Multiserial module can be used as an ATM net-

work interface, using the LANET protocol.

With this feature, statistical multiplexing gains can be achieved over low

speed serial links. By using LANET, the advantages of ATM can be used over

serial links to optimally interleave traffic for efficient bandwidth utilization

and multi-media capability. The LANET protocol efficiently adapts ATM to

low speed, high noise applications such as wireless and satellite. It is a physi-

cal layer protocol that maintains cell extraction capability at bit-error rates up

to 10 to the negative second power (-2). LANET overhead accounts for0.63% of link bandwidth. It can be implemented over each of the supported

serial interface types, and is independent of the transmission rate.

Hardware Features The 6-Port Multiserial module provides the following hardware features:

• Number of ports: 6 serial

• Connector type: micro-DB15

• Physical interfaces supported: RS-232, EIA-530, EIA-449, V.35 (subset of

V.11), X.21, and Kg with the Multiservice Media Gateway system config-

ured as either a data terminating equipment (DTE) or a data communica-

tions equipment (DCE) device.

• Line rate:

~ Minimum: 75 bps per port (asynchronous); 300 bps per port (synchro-

nous)

~ Maximum: 2.048 Mbps per port

~ Aggregate of all ports maximum: 4 Mbps

• Throughput: 5,000 packets per second maximum

• Line encoding mode: N/A

• Loopback capabilities: external DTE loopback


• Framing modes: cyclic redundancy check multi-frame (CRC-mf), LANET

Quadserial Module (23N07)

The Quadserial module provides four serial ports for several types of serial

data interfaces. Each port on the Quadserial module can be independently

configured for circuit emulation, HDLC Passthrough, frame relay, and asyn-

chronous transfer mode (ATM). Each port on the module provides a maxi-

mum line rate of 16 Mbps and a minimum line rate of 56 Kbps. The maxi-



255-700-447 D-47



mum aggregate port rate is 32 Mbps. The Quadserial interfaces support

synchronous RS-232, EIA-449, EIA-530, EIA-530A, V.352, X.21, and Kg.

Each port can be independently configured as either data terminating equip-

ment (DTE) or data communications equipment (DCE).

The Quadserial module also supports bit stuffing and 56K–64K circuit emula-

tion service (CES) conversion, available as standard features in theRelease 9.0.0 software. The framing for SS7 Message Transfer Part (MTP)

Level 2 is a modified version of high-level data link control (HDLC). The dif-

ference between SS7 MTP framing and standard HDLC is in the opening and

closing 1-byte flag. The SS7 MTP messages use only the closing flag. In order

to support external SS7 transport requirements, it is necessary to exchange

information via T1 circuits where each 64 Kbps DS0 of the T1 is filled with 56

Kbps of SS7 data and 8 Kbps of overhead (stuffing) data.

The SS7 circuits originating from the Quadserial interface can be mapped

using AAL1 to an individual ATM constant bit rate (CBR) class of service

exiting on a DS3 ATM cell-bearing interface. At the far-end, the ATM circuit

is adapted (based on AAL1 adaptation) to a native Quadserial (TDM) or CES

(TDM) circuit. The SS7 traffic can originate from the Quadserial interface and

terminate on the Enhanced DS1 interface.

Software Features The Quadserial module supports the following services:

• ATM: ATM UNI 3.0 and 3.1; Interim inter-switch signaling protocol (IISP)

user, IISP network; PNNI user, PNNI network

• CE: Circuit emulation service (CES) with AAL1 adaptive clocking and

unstructured DS1 or E1 interfaces configured in accordance with AF-

VTOA-0078.000






Hardware Features The Quadserial module provides the following hardware features:

• Number of ports: 4 serial (serial interface leads comply with AF-VTOA-

0119.000)

• Connector type: Mini-DB26

• Line rate (synchronous):

~ Minimum: 56 Kbps per port

~ Maximum: 16 Mbps per port~ Aggregate of all ports maximum: 32 Mbps

• Physical interfaces supported: RS-232, EIA-530, EIA-530A, EIA-449, V.35

(subset of V.11 ), X.21, and Kg with the Multiservice Media Gateway sys-

tem configured as either a data terminating equipment (DTE) or a data

communications equipment (DCE) device

2 V.35 has been superceded by V.11. Although the V.35 protocol is a subset of V.11,

V.35 more accurately describes the module’s capabilities.



Appendix D PSAX Module FeaturesVoice 2-Wire Interface Modules

D-48 255-700-447


• Line encoding mode: N/A

• Loopback capabilities: line loopback and local loopback from console, Tel-

net, or EMS interfaces


• Framing modes: HDLC checksum, LANET


4-Port Voice 2-Wire Office Module (20N32)

The 4-Port Voice 2-Wire Office module (20N32) provides support for the

office (central office or PABX switch) end of a two-wire analog telephone

line. This allows a voice loop from a voice switch to be connected directly to a

Multiservice Media Gateway system over an ATM network to a distant tele-

phone or other analog device. The coding translation supported by this mod-

ule is µ-law to µ-law only.

The module has three types of light-emitting diode (LED) indicators:

ACTIVE, FAIL, and LOS (loss of signal). On the faceplate, each port has a LOS

LED which turns on when the port goes off-hook. It also flashes in synchro-

nization with an incoming ringing signal to the port.

Software Features This module is typically configured with an 8-Port Voice 2-Wire Station mod-

ule via a PVC connection to enable a foreign exchange (FXO) voice service to

be transmitted across an ATM network. With FXO service, the voice switch

provides dial tone, ringing, and digit translation, which are not provided by

the ATM network.

Hardware Features The 4-Port Voice 2-Wire Office module supports these hardware features:



• Ringing frequency: 20 Hz

• Termination impedance: 600 Ohms

• Signaling: dual tone multi-frequency (DTMF)

• Supervision: loop start

8-Port Voice 2-Wire Station Module (20N30)The 8-Port Voice 2-Wire Station module provides support for the station

(telephone set) end of a two-wire analog telephone line. A telephone or

other analog voice device can be connected directly to this module in the

multiservice media gateway system over an ATM network. The coding trans-

lation supported by this module is µ-law to µ-law only.



255-700-447 D-49



The module has three types of light emitting diode (LED) indicators: ACTIVE,

FAIL, and LOS (loss of signal). On the faceplate, each port has a LOS LED

that illuminates when the port goes off-hook. It also flashes in synchroniza-

tion with an incoming ringing signal to the port.

Software Features The 8-Port Voice 2-Wire Station module can be used to establish a permanentvirtual circuit (PVC) on a voice circuit that originates on the same module.

This module also provides private-line automatic ring-down (PLAR) service

for the PVC. PLAR provides a point-to-point private line between two tele-

phone sets. If either station goes off-hook, the other one automatically rings.

The ringing will stop when the called station goes off-hook or the calling sta-

tion goes back on-hook. The PLAR service provides 20-Hz ring-down, loop-

start supervision, and no signalling. The module also supports FXS service via

a PVC connection with a 4-Port Voice 2-Wire Office module. This connection

enables a foreign exchange (FXO) voice service to be transmitted across an

ATM network. With FXO service, the voice switch provides dial tone, ringing,

and digit translation, which are not provided by the ATM network.

Hardware Features The 8-Port Voice 2-Wire Station module supports these hardware features:



• Ringing frequency: 20 Hz

• Termination impedance: 600 Ohms

• Signaling: none

• Supervision: loop start


