PSAX2300UserGuide PDF

Top of Guide
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
Doc. No.: 255-700-447
Copyright 2003 by Lucent Technologies. All rights reserved. For trademark, regulatory compliance, and related legal information, see Legal Notices, Safety, and Regulatory Information.
Legal Notices, Safety, and Regulatory Information

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 fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of 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 Technologies logo are registered trademarks of Lucent Technologies in the USA. Other product and brand names mentioned in this guide are trademarks or registered 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 responsibility for any errors, inaccuracies, or omissions. Neither is any liability assumed for damages resulting from the use of the information or instructions contained herein. Lucent Technologies, Inc. is not responsible for any damage or loss to your data or equipment resulting either directly or indirectly from use of this document.
Warranty Information
Lucent Technologies provides a 90-day limited software warranty, and a oneyear limited hardware warranty on this product. Refer to the Software License and Limited Warranty Agreement and the Lucent Technologies InterNetworking Systems Global Warranty that accompanied your package for more information.
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447
Release 9.0.0 iii
Legal Notices, Safety, and Regulatory Information

Regulatory Standards Compliance
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 PacketStarPSAX Multiservice 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 installation 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.
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 iv
Release 9.0.0 255-700-447
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
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-7 About the PacketStar PSAX Product Family . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7 PSAX 1000 Multiservice Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-7 PSAX 1250 Multiservice Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8 PSAX 2300 Multiservice Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-8 PSAX 4500 Multiservice Media Gateway. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9 Comments on This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-9
Release 9.0.0 v
Table of Contents
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 34 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 34 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
System Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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-6 Switched 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
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 vi
Release 9.0.0 255-700-447
Table of Contents
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-21 Inverse 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
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 vii
Table of Contents
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-51 SNMP 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 Virtual Channels. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 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
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 viii Release 9.0.0 255-700-447
Table of Contents
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
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
Site-Specific Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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
Release 9.0.0 ix
Table of Contents
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-50 Configuring 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 34 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-76 Setting the Stratum Configuration Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 x
Release 9.0.0 255-700-447
Table of Contents
Switching the Line Timing Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-83 Alarm Status Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-84 Saving the Equipment Configuration Values and Logging Off . . . . . . . . . . . . . . . . . . . . .5-84
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-68 Viewing ATM PNNI System Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-72
Configuring ATM Trunking. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .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
Release 9.0.0 xi
Table of Contents
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
Configuring SNMP Authentication Options . . . . . . . . . . . . . . . . . . . . . . . . . 9-1

Overview of This Chapter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 SNMP Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1 Accessing 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 Users Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-11 Deleting USM Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-14
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xii
Release 9.0.0 255-700-447
Table of Contents
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 InterfaceSignaling PVC . . .10-26 Viewing ATM Security Agent Statistics for an ATM PNNI InterfaceSignaling PVC .10-32 Configuring an ATM Security Agent for an ATM PNNI InterfaceRouting PVC . . . .10-36 Viewing ATM Security Agent Statistics for an ATM PNNI InterfaceRouting 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
Release 9.0.0 xiii
Table of Contents
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-1 Required 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
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xiv
Release 9.0.0 255-700-447
Table of Contents
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
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 34 Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 Alarm Module Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 ALARM Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 STATUS/CONTROL Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
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
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
Release 9.0.0 xv
Table of Contents
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
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 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-4 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5 8-Port HDSL-2 Module (23N69). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-5 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6 12-Port Medium-Density DS1 IMA Module (23N33) . . . . . . . . . . . . . . . . . . . . . . . . . D-6 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-6 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7 12-Port Medium-Density DS1 Multiservice Module (23N64). . . . . . . . . . . . . . . . . . . . D-7 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-7 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8 12-Port Medium-Density DS1/E1/DS0A CES Module (24N64) . . . . . . . . . . . . . . . . . . D-8 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-8 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-9 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 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-12 3-Port Channelized DS3/STS-1e CES Module (23N03) . . . . . . . . . . . . . . . . . . . . . . . D-13 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-14 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-14 1-Port Channelized STS-1e, T1 Module (23N62) . . . . . . . . . . . . . . . . . . . . . . . . . . . D-15 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-15 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xvi
Release 9.0.0 255-700-447
Table of Contents
2-Port DS3 ATM Module (20N02) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-16 1-Port Unchannelized DS3 Frame Relay Module (20N03) . . . . . . . . . . . . . . . . . . . . D-17 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-17 1-Port DS3 IMA Module (23N68) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18 2-Port E3 ATM Module (20N22) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-18 3-Port Unstructured DS3/E3 CES Module (23N02). . . . . . . . . . . . . . . . . . . . . . . . . . D-19 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-19 DSP2 Voice Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20 DSP2x Voice Server Modules (23N27 (C), 23N29 (D), 23N26 (E), and 23N25 (F)) . . . D-20 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20 E1 Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20 6-Port E1 IMA Module (20N34) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-20 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-21 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-21 6-Port Enhanced E1 Multiservice Module (20N56). . . . . . . . . . . . . . . . . . . . . . . . . . D-21 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-22 21-Port High-Density E1 IMA Module (23N34) . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-23 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-23 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-23 21-Port High-Density E1 Multiservice Module (23N66) . . . . . . . . . . . . . . . . . . . . . . D-24 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-24 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25 Ethernet Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25 4-Port Ethernet Module (23N40). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-25 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-26 Ethernet Module (20N40) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-27 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-27 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-27 Fiber-Optic Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-28
Release 9.0.0 xvii
Table of Contents
1-Port Channelized OC-3/STM-1 CES Module (23N12 (MM)/23N13 (SM)) . . . . . . . . D-28 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-28 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-29 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module (23N75 (MM)/23N76 (SM)) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-29 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-30 4-Port OC-3c/STM-1 Module (24N72 (MM)/24N73 (SM)). . . . . . . . . . . . . . . . . . . . . D-31 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-32 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-32 1-Port OC-12c/STM-4c Module (23N72 (MM)/23N73 (SM)) . . . . . . . . . . . . . . . . . . . D-32 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33 1-Port OC-3c Module with AQueMan (20N12 (MM)/20N13 (SM)) or Traffic Shaping (20N14 (MM)/20N15 (SM)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-34 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-34 1-Port OC-3c 1+1 APS Module (20N72 (MM)/20N73 (SM)) . . . . . . . . . . . . . . . . . . . D-35 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-35 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-35 1-Port STM-1 Module with AQueMan (20N62 (MM)/20N63 (SM)) or Traffic Shaping (20N64 (MM)/20N65 (SM)). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-36 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-36 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-36 1-Port STM-1 1+1 MSP Module (20N92 (MM)/20N93 (SM)) . . . . . . . . . . . . . . . . . . D-37 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-37 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-38 2-Port OC-3c/STM-1 ATM Module (24N70 (MM)/24N71 (SM)) . . . . . . . . . . . . . . . . D-38 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-39 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-39 Other Server Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-40 Enhanced Router Module (23N41) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-40 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-40 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-41 Route Server Module (20N41) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-41 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-42 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-42 Tones and Announcements Server Module (23N28). . . . . . . . . . . . . . . . . . . . . . . . . D-43 Software Features. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-43 Special Information Tones (SIT) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-43 Channel Associated Signaling (CAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-43
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xviii Release 9.0.0 255-700-447
Table of Contents
Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44 Serial Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44 6-Port Multiserial Module (20N07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44 Bit Stuffing and CES Conversion. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44 Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-44 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45 Frame Relay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45 Circuit Emulation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45 Terminal Emulation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-45 HDLC Passthrough . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-46 ATM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-46 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-46 Quadserial Module (23N07) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-46 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-47 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-47 Voice 2-Wire Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48 4-Port Voice 2-Wire Office Module (20N32) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48 8-Port Voice 2-Wire Station Module (20N30) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-48 Software Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-49 Hardware Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-49
Release 9.0.0 xix
Table of Contents
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xx
Release 9.0.0 255-700-447
List of Figures
1-1 1-2 2-1 2-2 2-3 2-4 2-5 2-6 3-1 3-2 3-3 3-4 3-5 3-6 3-7 3-8 3-9 3-10 3-11 3-12 3-13 3-14 3-15 3-16 3-17 3-18 3-19 3-20 3-21 3-22 3-23 3-24 4-1 4-2 4-3 4-4 Field Description Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-4 Main Menu Help Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-6 PSAX 2300 Multiservice Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-2 -48 V dc Power Supply Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-4 CPU4 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-6 CPU2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-7 Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 Example Configuration with the Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-8 Sample SPVC Reconnection Prioritization Scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-5 PNNI Hierarchical Topology Showing Three Node Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-16 DBA-Controlled Backplane Traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-25 PSAX System as a TCP Client Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30 PSAX System as a TCP Server Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-30 1:1 Protection Scheme on the PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-34 Typical Interface Protection Group Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-37 Automatic Traffic Rerouting using Dual-Homed PVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-39 Relationship Between LANET and the OSI Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-45 LANET Frame Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-46 OAM Cell Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-48 OAM Hierarchy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-49 OAM Activation/Deactivation Cells . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-51 Cell Bus Traffic Shaping Occurs on Egress to the Backplane . . . . . . . . . . . . . . . . . . . . . . . . .3-56 Cell Bus Traffic Shaping Using the Input Cell-Selection Algorithm . . . . . . . . . . . . . . . . . . . . .3-57 Sample ATM Traffic Shaping Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-59 ATM Traffic Shaping table Sample Queue 1 Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-62 Sample Uses of Virtual Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-66 Combining the UPC Feature and Either the TS or VI Feature on a Connection . . . . . . . . . . .3-68 PacketPipe AAL5-to-AAL2 Wireless Trunking from Cell Site to MSC for Mobile Voice . . . . . .3-71 Virtual Router Concept . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-72 Enhanced Router and Example Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-72 End-to-End Continuity Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-73 PSAX System Access Authentication via RADIUS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-77 Connection Description Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 Connect To Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-2 COM1 Properties Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3 PSAX 2300 Multiservice Media Gateway System Logon Window . . . . . . . . . . . . . . . . . . . . . .4-4
Release 9.0.0 xxi
List of Figures
5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 5-14 5-15 5-16 5-17 5-18 5-19 5-20 5-21 5-22 5-23 5-24 5-25 5-26 5-27 5-28 5-29 5-30 5-31 5-32 5-33 5-34 5-35 5-36 6-1 6-2 6-3 6-4
PSAX 2300 Multiservice Media Gateway System Logon Window . . . . . . . . . . . . . . . . . . . . . . 5-2 Console Interface Main Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-5 User Options WindowLogged on as Username Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-8 User Options WindowAuthentication Mode Hybrid Selected . . . . . . . . . . . . . . . . . . . . . . . 5-8 User Options WindowLogged on as Username Root . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 User Options WindowLogged on as Username Readwrite . . . . . . . . . . . . . . . . . . . . . . . . 5-13 User Options WindowLogged on as Username Readonly . . . . . . . . . . . . . . . . . . . . . . . . . 5-14 Site-Specific Menu Window (No System Options Configured) . . . . . . . . . . . . . . . . . . . . . . . 5-19 Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-23 TCP Server Configuration Window (PSAX System as a TCP Client) . . . . . . . . . . . . . . . . . . . . 5-30 TCP Server Configuration Window (PSAX System as a TCP Server) . . . . . . . . . . . . . . . . . . . . 5-30 Site-Specific Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33 Call Control Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-33 Diagnostics Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41 Remote Reboot Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-41 Site-Specific Menu Window (Feature Turn On/Off Option Selected) . . . . . . . . . . . . . . . . . . . 5-43 Feature Turn On/Off Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44 Console Interface Main Menu Window (Save Configuration Option Selected) . . . . . . . . . . . 5-47 Remote Reboot Configuration Window (Primary Switchover Option Selected) . . . . . . . . . . . 5-48 Remote Reboot Configuration Window (Reboot Primary CPU Option Selected) . . . . . . . . . . 5-50 Sample IUA Layer Configuration for the OMG and TMG Sides . . . . . . . . . . . . . . . . . . . . . . 5-51 Interface Protection Feature Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-54 Protection Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55 Protection Group Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-56 Interface Protection Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58 Interface Protection Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-59 Site-Specific Menu (IP Throttling Configuration Option Selected) . . . . . . . . . . . . . . . . . . . . . 5-61 The IP Throttling Window (Disabled) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62 The IP Throttling Window (Enabled) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62 Trap Activation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67 Bulk Statistics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70 Sample Equipment Configuration Window on a PSAX 2300 or PSAX 4500 System (Page 1) 5-72 Sample Equipment Configuration Window on a PSAX 1000, PSAX 2300, or PSAX 4500 System (Page 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73 Stratum Configuration Window (Freerun) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-77 Stratum Configuration Window (LineTiming Synchronization) . . . . . . . . . . . . . . . . . . . . . . . 5-78 Save Configuration [Modified] (Before Saving) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-85 PNNI System-Wide Configuration Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 PNNI Node Configuration Window (Before Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 PNNI Node Configuration Window (After Configuration) . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Release 9.0.0 255-700-447
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xxii
List of Figures
6-5 6-6 6-7 6-8 6-9 6-10 6-11 6-12 6-13 6-14 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6-24 6-25 6-26 6-27 6-28 6-29 6-30 6-31 6-32 6-33 6-34 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10
PNNI Node PGL Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-10 PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-14 PNNI Node SVCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-17 PNNI Scope Mapping Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-19 PNNI Route Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-21 PNNI Route Address Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-22 PNNI Metrics Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-26 PNNI Metrics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27 PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30 PNNI Route TNS Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31 PNNI Map TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35 PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-37 PNNI Summary Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-39 PNNI Summary Address Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-40 PNNI Map Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-42 PNNI Map Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-43 PNNI Map Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-46 PNNI Map Node Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-47 PNNI Map Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-51 PNNI Map Address Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-52 PNNI Link Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-54 PNNI Link Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-55 PNNI SvccRcc Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-59 PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-61 PNNI Neighbor Peer Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-63 PNNI Neighbor Peer Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-64 PNNI Neighbor Peer Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-67 PNNI PTSE Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-69 PNNI PTSE Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-70 PNNI System Statistics Screen Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-73 Site-Specific Menu WindowATM Trunking Configuration Option Selected . . . . . . . . . . . . .7-2 ATM Trunking Local Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-3 ATM Trunking Remote IWF Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-5 ATM Trunking Remote IWF Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-6 ATM Trunking Sig VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-9 ATM Trunking Sig VCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-10 ATM Trunking Bearer VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-14 ATM Trunking Bearer VCC Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-15 ATM Trunking NarrowBand Routing Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-24 ATM Trunking Broadband Routing Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7-26
Release 9.0.0 xxiii
List of Figures
7-11 8-1 8-2 8-3 8-4 8-5 8-6 8-7 8-8 8-9 8-10 8-11 8-12 8-13 8-14 8-15 8-16 8-17 8-18 8-19 8-20 8-21 9-1 9-2 9-3 9-4 9-5 9-6 9-7 9-8 9-9 9-10 9-11 9-12 9-13 9-14 10-1 10-2 10-3 10-4
ATM Trunking Data Channel Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-28 Site-Specific Menu Window (Feature Turn On/Off Option Selected) . . . . . . . . . . . . . . . . . . . . 8-6 Feature Turn On/Off Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7 Site-Specific Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10 Call Control Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-11 V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18 V5 Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-19 V5 Interface Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23 V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25 V5 Intf Variant Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-27 V5 Interface Variant Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-29 V5 Physical C-Channel Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-32 V5 Physical C-Channel Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-34 V5 E1 Link Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-37 V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-39 V5 E1 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-41 V5 Time Slot Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-43 V5 Data Link Configuration Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-44 V5 Data Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-45 V5 User Port Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-48 V5 User Port Configuration Window for PSTN as Port Type . . . . . . . . . . . . . . . . . . . . . . . . . 8-50 V5 User Port Configuration Window, Port Type ISDN Selected . . . . . . . . . . . . . . . . . . . . . . 8-56 Site-Specific Menu Window, SNMP Agent Selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3 SNMP Agent System-Wide Configuration Window, Non-Root User View . . . . . . . . . . . . . . . 9-3 SNMP Agent System-Wide Configuration Window, Root User View . . . . . . . . . . . . . . . . . . . 9-4 Community String Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5 Community String Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-6 Usm User Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-8 Usm User Creation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-9 Usm User Key Change Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-12 Vacm Access Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-16 Vacm Access Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 Vacm Security to Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-24 Vacm Security to Group Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-26 Notification Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30 Notification Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31 ATM UNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3 ATM UNI Interface ATM Security Configuration Window (Integrity Security Service Only) . . 10-5 ATM UNI Interface ATM Security Configuration Window (Both Integrity and Confidentiality Security Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-5 ATM UNI Interface ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-10
Release 9.0.0 255-700-447
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xxiv
List of Figures
10-5 10-6 10-7 10-8 10-9 10-10 10-11 10-12 10-13 10-14 10-15 10-16 10-17 10-18 10-19 11-1 11-2 11-3 11-4 11-5 11-6 11-7 11-8 11-9 11-10 11-11 11-12 12-1 12-2 12-3 12-4 13-1 13-2 13-3 13-4 13-5 13-6
PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-14 PNNI Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-14 ATM PNNI SVCC RCC Security Configuration Window (Integrity Security Service Only) . . . .10-15 ATM PNNI SVCC RCC Security Configuration Window (Both Integrity and Confidentiality Security Services) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-16 PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-21 ATM PNNI SVCC RCC Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-21 ATM PNNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-25 ATM PNNI Interface ATM Security Configuration Window - Signaling PVC (Integrity Security Service Only) . . . . . . . . . . . . . . . . . . . . . . . . .10-27 ATM PNNI Interface ATM Security Configuration Window - Signaling PVC (Both Integrity Security and Confidentiality Services) . . . . . . . . .10-28 ATM PNNI Interface ATM Security Statistics - Signaling PVC Window . . . . . . . . . . . . . . . . .10-33 ATM PNNI Interface ATM Security Configuration - Routing PVC Window (Integrity Security Service Only) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-37 ATM PNNI Interface ATM Security Configuration - Routing PVC Window (Both Integrity Security and Confidentiality Services) . . . . . . . . . . . . . . . . . . . . .10-37 ATM PNNI Interface ATM Security Statistics - Routng PVC Window . . . . . . . . . . . . . . . . . . .10-42 ATM Security Agents Table Window (Populated) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-46 ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-49 Console Interface Main Menu Window (Diagnostics Option Selected) . . . . . . . . . . . . . . . . . .11-3 Diagnostics Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-3 System Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4 Module Connection Count Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-8 Cell Test Diagnostics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10 Cell Test Payload Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-13 Remote Reboot Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-16 Unlock Shell / Ping Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-19 OAM Loopback Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-20 OAM LOOPBACK Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-21 OAM Activate & Deactivate Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-24 OAM Activation Deactivation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-25 Remote Database Operation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-4 Software Version Configuration window (XMODEM/YMODEM File Transfer Selected) . . . .12-10 XMODEM/YMODEM File Transfer Window (Send Options Panel Selected) . . . . . . . . . . . . .12-12 XMODEM/YMODEM File Transfer Window (Receive Options Panel Selected) . . . . . . . . . . . .12-19 Console Interface Main Menu Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-4 Software Version Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-4 SRD Download Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-5 Migration of the Files During the PSAX System Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . .13-11 Software Version Configuration Window (XMODEM/YMODEM File Transfer Selected) . . . .13-17 XMODEM/YMODEM File Transfer Window (Receive Options Panel Selected) . . . . . . . . . . . .13-18
Release 9.0.0 xxv
List of Figures
13-7 13-8 13-9 A-1 A-2 A-3 A-4 A-5 A-6 B-1 B-2 B-3 C-1
Console Interface Main Menu Window (Software Version Configuration Option Selected) 13-23 The Software Version Configuration Window (Firmware Version Control Selected) . . . . . . 13-24 Firmware Version Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13-26 ETHERNET1 and ETHERNET2 Connector Pin Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 ETHERNET Connector Pin Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 ALARM Connector Pin Locations on the Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 ALARM Cable with 26-Pin Connector and Pigtail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 Pin Locations for the STATUS/CONTROL Connector on the Alarm Module . . . . . . . . . . . . . . . A-6 STATUS/CONTROL Cable with 44-Pin Connector and Pigtail . . . . . . . . . . . . . . . . . . . . . . . . . A-7 Direct Connection Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2 Routed Connection Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5 Hybrid Connection Configuration Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-10 Combining the UPC Feature and Either the TS or VI Feature on a Connection . . . . . . . . . . C-38
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xxvi
Release 9.0.0 255-700-447
List of Tables
1-1 1-2 1-3 1-4 2-1 2-2 2-3 2-4 2-5 2-6 2-7 2-8 2-9 3-1 3-2 3-3 3-4 3-5 4-1 4-2 5-1 5-2 5-3 5-4 5-5 5-6 5-7 5-8 5-9 5-10 5-11 5-12 5-13 Text Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-2 Command Description Table Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-3 System Responses to Selecting Options, Fields, or Commands . . . . . . . . . . . . . . . . . . . . . . . .1-5 Shortcut Keys for Navigating Console Interface Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . .1-5 Chassis Hardware Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9 System Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-9 -48 V dc Power Supply Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10 Stratum 34 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-10 CPU4 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11 CPU2 Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-11 Physical Hardware Specifications for the Alarm Module . . . . . . . . . . . . . . . . . . . . . . . . . . . .2-12 Physical Hardware Specifications for PSAX I/O and Server Modules . . . . . . . . . . . . . . . . . . . .2-12 Performance and Power Specifications for the PSAX Modules . . . . . . . . . . . . . . . . . . . . . . . .2-13 Sample User-Defined Priority Scheme for Reconnecting SPVC ATM IMA Links . . . . . . . . . . . . .3-5 Forward Error Correction Automatic Rate Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-41 CBR and VBR Service-Level Priorities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-53 ATM Traffic Shaping Capabilities by Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3-64 ATM Traffic Shaping, UPC Support, and VI Support Configuration Compatibility . . . . . . . . .3-67 Starting the Hyperterminal Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-1 Windows HyperTerminal Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4-3 Field Descriptions for the PSAX System Logon Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-3 Console Interface Main Menu Options and Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-5 Commands for the User Options Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-8 Field Descriptions for the User Options Window (RADIUS Server Fields) . . . . . . . . . . . . . . . . . .5-9 Permissions for PSAX-defined Usernames . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-12 Commands for the User Options Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14 Field Descriptions for the User Options Window (Password and Miscellaneous User Options Fields) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-14 ASCII Characters Permitted for Use in Passwords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-17 Descriptions for Site-Specific Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-20 Commands for the Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23 Field Descriptions for the Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-23 Field Descriptions for the Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-26 Field Descriptions for the System Identification Panel on the Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5-27
Release 9.0.0 xxvii
List of Tables
5-14 5-15 5-16 5-17 5-18 5-19 5-20 5-21 5-22 5-23 5-24 5-25 5-26 5-27 5-28 5-29 5-30 5-31 5-32 5-33 5-34 5-35 5-36 5-37 5-38 5-39 5-40 5-41 5-42 6-1 6-2 6-3 6-4 6-5 6-6 6-7 6-8 6-9 6-10 6-11
Field Descriptions for the System Date and Time Panel on the Site-Specific Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-28 Commands for the TCP Server Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Field Descriptions for the TCP Server Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . 5-31 Commands for the Call Control Resource Allocation Configuration Window . . . . . . . . . . . . 5-34 Field Descriptions for the Call Control Resource Allocation Configuration Window . . . . . . . 5-34 PSAX System Performance Capabilities Per Node for Release 9.0.0 . . . . . . . . . . . . . . . . . . . 5-39 Commands for the Feature Turn ON/OFF Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-44 Field Descriptions for the Feature Turn On/Off Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-45 Commands for the IUA Layer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-51 Field Descriptions for the IUA Layer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . 5-51 Commands for the Interface Protection Feature Configuration Window . . . . . . . . . . . . . . . 5-54 Commands for the Protection Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-55 Commands for the Protection Group Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 5-56 Field Descriptions for the Protection Group Configuration Window . . . . . . . . . . . . . . . . . . . 5-56 Commands for the Interface Protection Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-58 Commands for the Interface Protection Configuration Window . . . . . . . . . . . . . . . . . . . . . 5-59 Field Descriptions for the Interface Protection Configuration Window . . . . . . . . . . . . . . . . . 5-60 Commands for the IP Throttling Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-62 Field Descriptions for the IP Throttling Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 5-63 Commands for the Trap Activation Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-67 Field Descriptions for the Trap Activation Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-68 Commands for the Bulk Statistics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 5-70 Field Descriptions for the Bulk Statistics Configuration Window . . . . . . . . . . . . . . . . . . . . . 5-70 Commands for the Equipment Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-73 Field Descriptions for the Equipment Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . 5-74 Alarm Status Descriptions for Modules on the Equipment Configuration Window . . . . . . . . 5-76 Commands for the Stratum Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-78 Field Descriptions for the Stratum Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 5-79 Messages Generated after the Save Configuration Process . . . . . . . . . . . . . . . . . . . . . . . . . 5-85 Commands for the PNNI System-Wide Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 6-2 Commands for the PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4 Field Descriptions for the PNNI Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5 Commands for the PNNI Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6 Field Descriptions for the PNNI Node Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . 6-7 Modifying a Configured PNNI Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-9 Commands for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 6-10 Field Descriptions for the PNNI Node PGL Configuration Window . . . . . . . . . . . . . . . . . . . . 6-11 Commands for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 6-14 Field Descriptions for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . 6-14 Commands for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 6-17
Release 9.0.0 255-700-447
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xxviii
List of Tables
6-12 6-13 6-14 6-15 6-16 6-17 6-18 6-19 6-20 6-21 6-22 6-23 6-24 6-25 6-26 6-27 6-28 6-29 6-30 6-31 6-32 6-33 6-34 6-35 6-36 6-37 6-38 6-39 6-40 6-41 6-42 6-43 6-44 6-45 6-46 6-47 6-48 6-49 6-50 6-51
Field Descriptions for the PNNI Node SVCC Configuration Window . . . . . . . . . . . . . . . . . . .6-17 Commands for the PNNI Node Timer Configuration Window . . . . . . . . . . . . . . . . . . . . . . . .6-19 Field Descriptions for the PNNI Scope Mapping Configuration Window . . . . . . . . . . . . . . . .6-19 Commands for the PNNI Route Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-22 Commands for the PNNI Route Address Configuration Window . . . . . . . . . . . . . . . . . . . . . .6-22 Field Descriptions for the PNNI Route Address Configuration Window . . . . . . . . . . . . . . . . .6-23 Commands for the PNNI Metrics Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27 Commands for the PNNI Metrics Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-27 Field Descriptions for the PNNI Metrics Configuration Window . . . . . . . . . . . . . . . . . . . . . . .6-28 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-30 Field Descriptions for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-31 PNNI Route TNS Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-32 Field Descriptions for the PNNI Route TNS Configuration Window . . . . . . . . . . . . . . . . . . . .6-32 Commands for the PNNI Map TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-35 Field Descriptions for the PNNI Map TNS Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-36 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-37 Field Descriptions for the PNNI Map TNS Configuration Window . . . . . . . . . . . . . . . . . . . . .6-37 Commands for the PNNI Summary Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . .6-39 Commands for the PNNI Summary Address Configuration Window . . . . . . . . . . . . . . . . . . .6-40 Field Descriptions for the PNNI Summary Address Configuration Window . . . . . . . . . . . . . . .6-40 Commands for the PNNI Map Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-42 PNNI Map Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-43 Field Descriptions for the PNNI Map Information Window . . . . . . . . . . . . . . . . . . . . . . . . . .6-44 Commands for the PNNI Map Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-46 Field Descriptions for the PNNI Map Node Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-47 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-47 Field Descriptions for the PNNI Map Node Information Window . . . . . . . . . . . . . . . . . . . . . .6-48 Commands for the PNNI Map Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-51 Field Descriptions for the PNNI Map Address Table Window . . . . . . . . . . . . . . . . . . . . . . . . .6-51 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-52 Field Descriptions for the PNNI Map Address Entry Window . . . . . . . . . . . . . . . . . . . . . . . . .6-52 Commands for the PNNI Link Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-54 Commands for the PNNI Link Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-55 Field Descriptions for the PNNI Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . .6-55 Commands for the PNNI SvccRcc Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-59 Field Descriptions for the PNNI SVCC RCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . .6-60 Commands for the PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . . . . . .6-61 Field Descriptions for the PNNI SVCC RCC Information Window . . . . . . . . . . . . . . . . . . . . . .6-61 Commands for the PNNI Neighbor Peer Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6-64 Command for the PNNI Neighbor Peer Information Window . . . . . . . . . . . . . . . . . . . . . . . .6-64
Release 9.0.0 xxix
List of Tables
6-52 6-53 6-54 6-55 6-56 6-57 6-58 6-59 6-60 7-1 7-2 7-3 7-4 7-5 7-6 7-7 7-8 7-9 7-10 7-11 7-12 7-13 7-14 7-15 7-16 7-17 7-18 7-19 7-20 8-1 8-2 8-3 8-4 8-5 8-6 8-7 8-8 8-9 8-10 8-11
Field Descriptions for the PNNI Neighbor Peer Configuration Window . . . . . . . . . . . . . . . . . 6-65 Commands for the PNNI Neighbor Peer Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . 6-67 Field Descriptions for the PNNI Neighbor Peer Port Table Window . . . . . . . . . . . . . . . . . . . 6-68 Commands for the PNNI PTSE Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-69 Field Descriptions for the PNNI PTSE Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70 Commands for the PNNI Route TNS Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-70 Field Descriptions for the PNNI PTSE Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . 6-71 Commands for the PNNI System Statistics Screen Window . . . . . . . . . . . . . . . . . . . . . . . . . 6-73 Field Descriptions for the PNNI System Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . 6-74 Commands for the ATM Trunking Local Node Configuration Window . . . . . . . . . . . . . . . . . 7-3 Field Descriptions for the ATM Trunking Local Node Configuration Window . . . . . . . . . . . . 7-4 Commands for the ATM Trunking Remote IWF Table Window . . . . . . . . . . . . . . . . . . . . . . . 7-5 Field Descriptions for the ATM Trunking Remote IWF Table . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6 Commands for the ATM Trunking Remote IWF Configuration Window . . . . . . . . . . . . . . . . . 7-6 Field Descriptions for the ATM Trunking Remote IWF Configuration Window . . . . . . . . . . . . 7-7 Commands for the ATM Trunking Sig VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . 7-9 Field Descriptions for the ATM Trunking Sig VCC Table Window . . . . . . . . . . . . . . . . . . . . . 7-10 Commands for the ATM Trunking Sig VCC Configuration Window . . . . . . . . . . . . . . . . . . . 7-10 Field Descriptions for the ATM Trunking Sig VCC Configuration Window . . . . . . . . . . . . . . 7-11 Commands for the ATM Trunking Bearer VCC Table Window . . . . . . . . . . . . . . . . . . . . . . . 7-15 Field Descriptions for the ATM Trunking Bearer VCC Table Window . . . . . . . . . . . . . . . . . . 7-15 Commands for the ATM Trunking Bearer VCC Configuration Window . . . . . . . . . . . . . . . . 7-16 Field Descriptions for the ATM Trunking Bearer VCC Configuration Window . . . . . . . . . . . . 7-16 Commands for the ATM Trunking Narrowband Routing Table Window . . . . . . . . . . . . . . . 7-24 Field Descriptions for the ATM Trunking Narrowband Routing Table Window . . . . . . . . . . . 7-24 Commands for the ATM Trunking Broadband Routing Table Window . . . . . . . . . . . . . . . . . 7-26 Field Descriptions for the ATM Trunking Broadband Routing Table Window . . . . . . . . . . . . 7-26 Commands for the ATM Trunking Data Channel Table Window . . . . . . . . . . . . . . . . . . . . . 7-28 Field Descriptions for the ATM Trunking Data Channel Table Window . . . . . . . . . . . . . . . . 7-28 V5.2 Voice Switch Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 V5.2 IAD Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4 Commands for the Feature Turn ON/OFF Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7 Field Descriptions for the Feature Turn On/Off Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8 Commands for the Call Control Resource Allocation Configuration Window . . . . . . . . . . . . 8-11 Field Descriptions for the Call Control Resource Allocation Configuration Window . . . . . . . 8-12 PSAX System Performance Capabilities Per Node for Release 9.0.0 . . . . . . . . . . . . . . . . . . . 8-17 Commands for the V5 Interface Configuration Menu Window . . . . . . . . . . . . . . . . . . . . . . 8-19 V5 Resource Allocation Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20 Field Descriptions for the V5 Resource Allocation Configuration Window . . . . . . . . . . . . . . 8-20 Commands for the V5 Interface Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xxx
Release 9.0.0 255-700-447
List of Tables
8-12 8-13 8-14 8-15 8-16 8-17 8-18 8-19 8-20 8-21 8-22 8-23 8-24 8-25 8-26 8-27 8-28 8-29 8-30 8-31 8-32 8-33 8-34 8-35 8-36 9-1 9-2 9-3 9-4 9-5 9-6 9-7 9-8 9-9 9-10 9-11 9-12 9-13 9-14 9-15
Field Descriptions for the V5 Interface Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-23 Commands for the V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-25 Field Descriptions for the V5 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . . . .8-26 Commands for the V5 Intf Variant Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-27 Field Descriptions for the V5 Interface Variant Table Window . . . . . . . . . . . . . . . . . . . . . . . .8-28 Commands for the V5 Interface Variant Configuration Window . . . . . . . . . . . . . . . . . . . . . .8-29 Field Descriptions for the V5 Interface Variant Configuration Window . . . . . . . . . . . . . . . . .8-30 Commands for the V5 Physical C-Channel Configuration Table Window . . . . . . . . . . . . . . .8-32 Field Descriptions for the V5 Physical C-Channel Configuration Table Window . . . . . . . . . . .8-33 Commands for the V5 Physical C-Channel Configuration Window . . . . . . . . . . . . . . . . . . . .8-34 Field Descriptions for the V5 Physical C Channel Configuration Window . . . . . . . . . . . . . . . .8-35 Commands for the V5 E1 Link Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . . .8-37 Field Descriptions for the V5 E1 Link Configuration Table Window . . . . . . . . . . . . . . . . . . . .8-38 Commands for the V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-39 Field Descriptions for the V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . .8-39 Commands for the V5 E1 Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-41 Field Descriptions for the V5 E1 Interface Configuration Window . . . . . . . . . . . . . . . . . . . . .8-41 Commands for the V5 Timeslot Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-43 Commands for the V5 Data Link Configuration Table Window . . . . . . . . . . . . . . . . . . . . . . .8-44 Field Descriptions for the V5 Data Link Configuration Table Window: . . . . . . . . . . . . . . . . . .8-44 Commands for the V5 Data Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . .8-45 Field Descriptions for the V5 Data Link Configuration Window . . . . . . . . . . . . . . . . . . . . . . .8-46 Commands for the V5 User Port Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-48 Commands for the V5 User Port Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .8-50 Field Descriptions for the V5 User Port Configuration Window . . . . . . . . . . . . . . . . . . . . . . .8-51 Menu Options for the SNMP Agent System-Wide Configuration Window . . . . . . . . . . . . . . . .9-4 Commands for the Community String Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-5 Field Descriptions for the Community String Table Window . . . . . . . . . . . . . . . . . . . . . . . . . .9-6 Commands for the Community String Configuration Window . . . . . . . . . . . . . . . . . . . . . . . .9-6 Field Descriptions for the Community String Configuration Window . . . . . . . . . . . . . . . . . . . .9-7 Default USM User Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-7 Commands for the Usm User Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9 Field Descriptions for the Usm User Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-9 Commands for the Usm User Creation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10 Field Descriptions for the Usm User Creation Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-10 Commands for the Usm User Key Change Configuration Window . . . . . . . . . . . . . . . . . . . .9-13 Field Descriptions for the Usm User Key Change Configuration Window . . . . . . . . . . . . . . . .9-13 Default VACM Access Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-15 Commands for the Vacm Access Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-16 Field Descriptions for the Vacm Access Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9-17
Release 9.0.0 xxxi
List of Tables
9-16 9-17 9-18 9-19 9-20 9-21 9-22 9-23 9-24 9-25 9-26 9-27 10-1 10-2 10-3 10-4 10-5 10-6 10-7 10-8 10-9 10-10 10-11 10-12 10-13 10-14 10-15 10-16 10-17 10-18 10-19 10-20 10-21 10-22
Commands for the Vacm Access Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . 9-18 Field Descriptions for the Vacm Access Configuration Window . . . . . . . . . . . . . . . . . . . . . . 9-19 Default VACM Access Group Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-22 Valid VACM Group Assignment for USM Security Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-23 Commands for the Vacm Security to Group Table Window . . . . . . . . . . . . . . . . . . . . . . . . . 9-24 Field Descriptions for the Vacm Security to Group Table Window . . . . . . . . . . . . . . . . . . . . 9-25 Commands for the Vacm Security to Group Configuration Window . . . . . . . . . . . . . . . . . . 9-26 Field Descriptions for the Vacm Security to Group Configuration Window . . . . . . . . . . . . . . 9-27 Commands for the Notification Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30 Field Descriptions for the Notification Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-30 Commands for the Notification Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-31 Field Descriptions for the Notification Configuration Window . . . . . . . . . . . . . . . . . . . . . . . 9-31 Commands for the ATM UNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . . . 10-3 Field Descriptions for the ATM UNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . 10-4 Commands for the ATM UNI Interface ATM Security Configuration Window . . . . . . . . . . . . 10-6 Field Descriptions for the ATM UNI Interface ATM Security Configuration Window . . . . . . . 10-6 Commands for the ATM UNI Interface ATM Security Statistics Window . . . . . . . . . . . . . . . 10-10 Field Descriptions for the ATM UNI Interface ATM Security Statistics Window . . . . . . . . . . 10-11 Commands for the ATM PNNI SVCC RCC Security Configuration Window . . . . . . . . . . . . 10-16 Field Descriptions for the ATM PNNI SVCC RCC Security Configuration Window . . . . . . . . 10-17 Commands for the ATM PNNI SVCC RCC Security Statistics Window . . . . . . . . . . . . . . . . 10-22 Field Descriptions for the ATM PNNI SVCC RCC Security Statistics Window . . . . . . . . . . . . 10-22 Commands for the ATM PNNI Interface ATM Security Window . . . . . . . . . . . . . . . . . . . . . 10-25 Field Descriptions for the ATM PNNI Interface ATM Security Window . . . . . . . . . . . . . . . . 10-26 Commands for the ATM PNNI Interface ATM Security Configuration - Signaling PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-28 Field Descriptions for the ATM PNNI Interface ATM Security Configuration - Signaling PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-29 Commands for the ATM PNNI Interface ATM Security Statistics - Signaling PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-33 Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Signaling PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-34 Commands for the ATM PNNI Interface ATM Security Configuration - Routing PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38 Field Descriptions for the ATM PNNI Interface ATM Security Configuration - Routing PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-38 Commands for the ATM PNNI Interface ATM Security Statistics - Routing PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-42 Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Routing PVC Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-43 Commands for the ATM Security Agents Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . 10-46 Field Descriptions for the ATM Security Agents Table Window . . . . . . . . . . . . . . . . . . . . . 10-47
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xxxii
Release 9.0.0 255-700-447
List of Tables
10-23 10-24 11-1 11-2 11-3 11-4 11-5 11-6 11-7 11-8 11-9 11-10 11-11 11-12 11-13 11-14 11-15 11-16 12-1 12-2 12-3 12-4 12-5 12-6 12-7 13-1 13-2 13-3 13-4 13-5 13-6 13-7 13-8 13-9 13-10 13-11 13-12 13-13
Commands for the ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10-49 Field Descriptions for the ATM Security Statistics Window . . . . . . . . . . . . . . . . . . . . . . . . . .10-50 Menu Option Descriptions for the Diagnostics Menu Window . . . . . . . . . . . . . . . . . . . . . . .11-1 Commands for the System Information Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4 Field Descriptions for the System Information Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-4 Commands for the Module Connection Count Table Window . . . . . . . . . . . . . . . . . . . . . . .11-8 Field Descriptions for the Module Connection Count Table Window . . . . . . . . . . . . . . . . . . .11-8 Commands for the Cell Test Diagnostics Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-10 Field Descriptions for the Cell Test Diagnostics Window . . . . . . . . . . . . . . . . . . . . . . . . . . .11-11 Commands for the Cell Test Payload Configuration Window . . . . . . . . . . . . . . . . . . . . . . .11-13 Field Descriptions for the Cell Test Payload Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-14 Commands for the Remote Reboot Configuration Window . . . . . . . . . . . . . . . . . . . . . . . .11-16 Commands for the OAM Loopback Table Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-20 Commands for the OAM Loopback Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-21 Field Descriptions for the OAM Loopback Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11-22 Commands for the OAM Activate & Deactivate Table Window . . . . . . . . . . . . . . . . . . . . . .11-25 Commands for the OAM Activate & Deactivate Table Window . . . . . . . . . . . . . . . . . . . . . .11-25 Field Descriptions for the OAM Activation-Deactivation Window . . . . . . . . . . . . . . . . . . . .11-26 Tasks for Copying Database Configuration Files Between the PSAX System and a Remote Storage Medium . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-2 Commands for the Remote Database Operation Window . . . . . . . . . . . . . . . . . . . . . . . . . . .12-4 Field Descriptions for the Remote Database Operation Window . . . . . . . . . . . . . . . . . . . . . .12-5 PSAX System Configuration Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12-8 Commands for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . . . . . . .12-12 Field Descriptions for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . .12-12 Connecting a Cable to the Standby (Backup) CPU Module . . . . . . . . . . . . . . . . . . . . . . . . .12-20 Tasks for Transferring Files to Your PSAX System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-2 Commands for the SRD Download Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . .13-5 Field Descriptions for the SRD Download Configuration Window . . . . . . . . . . . . . . . . . . . . .13-6 Error Status Code Values for the [Error Status] Field on the SRD Download Configuration Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-7 Determining Whether to Proceed with System Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . .13-10 Determining Whether to Save Your Current System Configuration Before Upgrade . . . . . .13-12 Length of Time Required for Firmware Downloading . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-14 Setting Up the Connection Between the PC Workstation, the Local Modem, and the Telephone Jack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-16 Setting Up the Connection Between the Modem and the PSAX System . . . . . . . . . . . . . . .13-16 Commands for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . . . . . . .13-18 Field Descriptions for the XMODEM/YMODEM File Transfer Window . . . . . . . . . . . . . . . . .13-19 Selecting Firmware Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-25 Commands for the Firmware Version Control Window . . . . . . . . . . . . . . . . . . . . . . . . . . . .13-26
Release 9.0.0 xxxiii
List of Tables
13-14 A-1 A-2 A-3 A-4 A-5 A-6 A-7 A-8 A-9 C-1 C-2 C-3 C-4 C-5 C-6 C-7 C-8 C-9 C-10 C-11 C-12 D-1 D-2 D-3 D-4 D-5 D-6 D-7 D-8 D-9 D-10
Field Descriptions for the Firmware Version Control Window . . . . . . . . . . . . . . . . . . . . . . 13-27 CPU4 Module CONSOLE Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1 CPU4 Module ETHERNET1 and ETHERNET2 Connector Pin Assignments . . . . . . . . . . . . . . . . A-2 CPU2 Module CONSOLE Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2 CPU2 Module ETHERNET Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 RJ-12-to-DB9 Adapter Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 RJ-12-to-DB25 Adapter Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3 Stratum 34 Module RJ-45 Connector Pin Assignments . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4 ALARM Connector Pin Assignments and Cable Pigtail Color Code (COMCODE 300164290) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5 STATUS/CONTROL Connector Pin Assignments and Cable Pigtail Color Code (COMCODE 300164282) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7 Traffic Processing Options and Priority Queuing for Modules Supporting ATM Interfaces . . . . C-3 Connection Release Cause Codes for SPVCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5 DSP Tone Detection Modes and Associated Processing Performed . . . . . . . . . . . . . . . . . . . . . C-9 Channel Reduction Availability Caused by Fax Relay Connections vs. Voice Processing Connections on a DSP2C Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-9 Industry Compliance Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-10 Connection Type by Interface Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-30 Interface Type by I/O Module Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-31 PSAX System-Supported Quality of Service Category Descriptions . . . . . . . . . . . . . . . . . . . . C-35 Mapping ATM Service Categories to PSAX System Priority Levels . . . . . . . . . . . . . . . . . . . . . C-36 ATM Traffic Shaping, UPC Support, and VI Support Configuration Compatibility . . . . . . . . . C-37 ATM Traffic Shaping CPS Calculation Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-38 I/O Module Transmit Clock Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-41 PacketStar PSAX Multiservice Media Gateway Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1 1-Port Channelized OC-3/STM-1 CES Module Optical Specifications . . . . . . . . . . . . . . . . . . D-29 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module Optical Specifications . . . D-30 4-Port OC-3c/STM-1 Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-32 1-Port OC-12c/STM-4c Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-33 1-Port OC-3c Module with AQueman or Traffic Shaping Optical Specifications . . . . . . . . . . D-34 1-Port OC-3c 1+1 APS Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-35 1-Port STM-1 Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-36 1-Port STM-1 1+1 MSP Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-38 2-Port OC-3c/STM-1 ATM Module Optical Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . D-39
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xxxiv
Release 9.0.0 255-700-447
1
Purpose of This Guide
Getting Started
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 Multiservice Media Gateways.
Release 9.0.0 1-1
Chapter 1 Getting Started

Related Reading
Related Reading
Product Information Library
To install, operate, and configure your PSAX system and I/O and server modules, read the PSAX publications provided on your Lucent Technologies PacketStar 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 telecommunications 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 interface 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 SANS SERIF BOLD, ALL CAPS Fixed-width normal How it is used
Labels on module panels, chassis faceplates, or other hardware Message text displayed on the user interface window 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 System prompts displayed on the user interface window A variable name or string for which you will substitute your own information An argument or parameter on a command line for which you will substitute your own information
Serif bold
Fixed-width bold
Serif italics
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 1-2
Release 9.0.0 255-700-447

Conventions
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, and notes 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 identified by 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 window). 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 column by use of the Note: text convention (see Table 1-2).
Table 1-2. Command Description Table Example Command Function
Bring All Interfaces Brings the out-of-service configured interfaces to in-service status. Into Service Note: In GR-303 configuration, it is critical to bring into service only those channels actively configured with DS1 ports.
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 description tables to alert the user to special instructions or configuration constraints (see Figure 1-1).
Release 9.0.0 1-3

Conventions
Identifies editable fields or display-only fields on screens
Identifies initial field value default
Describes the function of the field and special instructions for configuring modules
Field Name Interface Type
Field Values Default: 0 Range: 0-22 Format: Numeric
Description 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 selected in this field, other configuration fields are displayed on this window.
Identifies available range for field value when applicable
Identifies field value format as Numeric, Predefined Alphanumeric, Hexadecimal, or Valid Dotted Quad.
Decribes special instructions or configuration constraints
Figure 1-1. Field Description Table Example
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.
Release 9.0.0 255-700-447

Help Information
Table 1-3. System Responses to Selecting Options, Fields, or Commands
For a selected... option name field
the following occurs: The window corresponding to the option name is displayed. The following variations occur: The field entry area is blank or contains the default or previously entered 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 brackets (example: [LineStatus]). The following variations occur: A message in the information line indicating an error or successful completion 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.
command
To navigate through the Console windows, use the shortcuts listed in Table 1-4.
Table 1-4. Shortcut Keys for Navigating Console Interface Windows
If you want to... redisplay the previous window redisplay the Console Interface Main Menu window refresh the window
press... Ctrl+B on the window. Ctrl+G on the window. Ctrl+R on the window.
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 bottom of the window for instructions and information.
Help Information
The Help windows are accessible from any window in the PSAX system console interface. To access the Help windows, press the ? (Question Mark) key on any window. In addition to the Help windows, the Console Interface windows 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
Release 9.0.0 1-5

Help Information
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).
Your site name appears here after initial configuration
Information Line
Figure 1-2. Main Menu Help Window
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
Release 9.0.0 255-700-447

Technical 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 company 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 customer premises communications units, and commercial and multimedia communications and messaging systems designed and supported by our research and development unit, Bell Laboratories. Our legacy and our spirit of innovation allow Lucent to provide our customers with the tools needed to communicate effectively, any time and anywhere, 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 Gateways 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.
PSAX 1000 Multiservice Media Gateway

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 deployment. Ideal for central office, large enterprise, or wireless cell site multiservice media gateway applications, the PSAX 1000 system provides highly reliable network access for time-division multiplex voice, frame relay, 10/100BASE-T Ethernet, and ATM data applications.
Release 9.0.0 1-7

About the PacketStar PSAX Product Family
When it is functioning in a redundant operating mode and after it has experienced 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 (19inch chassis) for I/O and server moduleswith 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 serialthe 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 enterprises 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 applications. When it is functioning in a redundant operating mode and after it has experienced a single-point failure, the PSAX 1250 system provides up to 600 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 600 Mbps. Supporting 10 slots (19-inch chassis) or 14 slots (23-inch chassis) for I/O and server moduleswith 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 serialthe 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. When it is functioning in a redundant operating mode and after it has experienced a single-point failure, the PSAX 2300 system provides up to 1.9 Gbps 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 1.9 Gbps. Supporting 15 slots for I/O and server moduleswith 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 serialthe PSAX 2300 system solves demanding and diverse network design challenges with ease.
Release 9.0.0 255-700-447

Comments 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 network access for time-division multiplex voice, frame relay, 10/100BASE-T Ethernet, and ATM data applications. When it is functioning in a redundant operating mode and after it has experienced a single-point failure, the PSAX 4500 system provides up to 4.2 Gbps 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 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 modules 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 gatewaywith 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 modulesthe PSAX 4500 system provides packet solutions for voice over xDSL, trunking, tandem, and PRI offload switching.

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 comments@lucent.com. Include the following information: Title: PacketStar PSAX 2300 Multiservice Media Gateway User Guide Release number: Release 9.0.0 Document number: 255-700-447 Issue number: Issue 1 Publication date: October 2003
Release 9.0.0 1-9

Release 9.0.0 255-700-447
2
Overview of This Chapter
Hardware Description
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-capacity, 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 (automatic 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 moduleswith 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 serialthe 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 following hardware components (see Figure 2-1): Chassis17.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 moduletwo each for redundant operation (includes cooling fan for power supply and chassis) Stratum 34 moduletwo 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).
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 2-1
Chapter 2 Hardware Description

Functional Description
Blank faceplate modulesrequired for empty I/O and server slots
FA AC
IL
TIVE FA IL AC
DS IM 1 A
TIVE FA IL AC
LO 1
DS En 1 h
LO
TIVE FA IL AC
DS En 1 h
TIVE FA IL AC
1 LO 2 1 LO 3 2 1 S S
DS AT 1 M
TIVE FA IL AC
DS 1 CE
TIVE FA IL AC
LO 3 2 1
DS 1 CE
S
TIVE FA IL FA AC UN IL FA AC UN 1 2 IL AC
LO 2 1
SE RIA L
S 1 2
TIVE
SE RIA L
TIVE
LO CK
TIVE FA IL AC TIVE FA
LO CK
3 3 4 4 3 4
ST RA TU M 3 CL 4 ST K LO RA TU S M 3 CL 4 K LO S
CH
IL
DS
AC
TIVE FA IL AC
DS AT 3 M
TX LO S LO S
TIVE FA IL AC
LA MP
5 5 6 6
TE ST LA MP TE ST
OC (SM -3c AQ )
TIVE FA IL AC
TX RX
5 6 RX
LO
OC (SM -3c AQ )
TIVE FA IL AC
LO
OC (M -3c MA Q)
TIVE FA IL AC
TX LO TX TX S
LO
OC (M -3c MA Q)
TIVE FA IL AC
EN ET
TIVE FA IL AC
LO
CP U
1
TIVE
TX RX RX RX RX
las er
TX
ET
CP U
HE RN ET ET HE
RX
ha za rd las
2
er
CO
RN ET
NS
AL
E CO NS
ha
za
rd
3 LO KE AD Y 4
AL
ke 5
load y
Po wer
Su
pp
ly
-48
FA IL V nonredu AC TIVE ndan t
10
Po wer
Su
pp
ly
-48
10
Figure 2-1. PSAX 2300 Multiservice Media Gateway
Chassis
The PSAX 2300 chassis is a dc-powered, fully redundant 19- or 23-inch rackmountable chassis. The physical dimensions are 17.5 inches wide, 15.75 inches high, and 12 inches deep. Cable management clips add another 1.5 in. to the front front of the chassis. The chassis includes 17 front-panel slots for input/output (I/O) and server modules for customer traffic, redundant stratum system timing, and central processing units for control and configuration. Two -48 V dc Power Supply modules reside below the cable turndown loops and air filter compartment in the middle of the chassis. The rear panel provides power and ground terminations for the chassis and additional module slots for future enhancements.
Release 9.0.0 255-700-447

The chassis includes a midplane printed circuit board (PCB) designed to provide 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 modules are hot swappable.
Backplane
The chassis backplane distributes data, clock signals, and power to the modules. 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 protection for system resources and functionality. In conjunction with the Stratum 34 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 primary and 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 distributes 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 connections. 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 side and 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.
Release 9.0.0 2-3

10
Figure 2-2. -48 V dc Power Supply Module
Stratum 34 Module
The PSAX 2300 Stratum 34 ANSI-compliant module provides synchronization 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 segment 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 34 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 DSP2x 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 physical interface at low transmission rates, the PSAX 2300 system provides the network with a reliable transport and access infrastructure. The Stratum 34 module is accurate to Stratum 3 requirements, allowing the PSAX 2300 system to run freely even if the module loses external timing for as long as 24 hours, without synchronization problems. The faceplate of the Stratum 34 module has four LED indicators that provide operational status of the module.
Release 9.0.0 255-700-447

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 signaling 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 module, 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 module does not allow any settings to be modified. The module also provides a serial console port and two 10/100BASE-T Ethernet 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.
Release 9.0.0 2-5

FAIL ACTIVE CPU4
LOAD STBY
CONSOLE
ETHERNET 1LINK
TX/RX LINK
TX/RX
ETHERNET 2
Figure 2-3. CPU4 Module
CPU2 Module
Operating in a nonload-sharing, active/standby mode, the CPU2 module (see Figure 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 connections on calls in a transient state will not be saved. To preserve active virtual connections, 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 module, 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.
Release 9.0.0 255-700-447

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.
FAIL ACTIVE
CPU2
ETHERNET
CONSOLE
LOAD
Figure 2-4. CPU2 Module
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 modules 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 controlled through the console or AQueView EMS. For a detailed description of the Alarm module, see the PacketStar PSAX Alarm Module User Guide.
Release 9.0.0 2-7

CRITICAL MAJOR MINOR
ACO
Figure 2-5. Alarm Module

Critical Major Minor
ALARM CRITICAL MAJOR MINOR
STATUS/CONTROL
ALARM
CO Alarms
ACO
Alarms
ALARM
Fan
Output
STATUS/CONTROL
Temp. Sensor Hot
Input
Cold
Figure 2-6. Example Configuration with the Alarm Module
Release 9.0.0 255-700-447

Hardware Specifications
Chassis Specifications
The chassis specifications for the PSAX 2300 chassis are given in Table 2-1.
Table 2-1. Chassis Hardware Specifications Specification Description
Slot configuration
19 module slots (15 for user-selected I/O and server modules, 2 for CPUn modules, and 2 for Stratum 34 modules) and 2 Power Supply module slots 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
Empty: 8.17 kg (18.0 lb) Fully populated: 22.29 kg (49.1 lb)
Dimensions
Weight Material Color Ventilation
Aluminum Black Forced convection using two variable-speed fans (one per Power Supply module)
System Environmental Specifications

The environmental specifications for the PSAX 2300 system are given in Table 2-2.
Table 2-2. System Environmental Specifications Specification Description
Operating temperature range Operating humidity range Operating altitude range Storage temperature range Storage humidity range
0 to 50 C (32 to 122 F) 5% to 85% relative humidity 60 meters (197 feet) below sea level to 4,000 meters (13,123 feet) above sea level -40 to 70 C (-40 to 158 F) 0% to 90% noncondensing
Release 9.0.0 2-9

Power Supply Module Specifications

The specifications for the PSAX 2300/4500 -48 V dc Power Supply module are given in Table 2-3.
Table 2-3. -48 V dc Power Supply Module Specifications Specification Description
Slot Configuration Power
Two dedicated slots below module slots

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 Weight Units per system Connector Wire/cable size 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) 2.37 kg (5.25 lb) Two required for redundancy Two screw-type terminals on the rear panel
Power feed: two pair of 3.32.1 mm2 (#1214 AWG) stranded
recommended
Frame ground: up to 5.3 mm2 (#10 AWG) stranded recom-
mended.
Stratum 34 Module Specifications

The specifications for the PSAX 2300 Stratum 34 module are given in Table 2-4.
Table 2-4. Stratum 34 Module Specifications Specification Description
Slot configuration Dimensions Weight Units per system Power consumption Synchronization source Accuracy External clock input Connector
Front two middle slots labeled A and B 15.8 cm H x 1.6 cm W x 24.1 cm D (6.2 in. H x 0.6 in. W x 9.5 in. D) 0.22 kg (0.5 lb) 2 required for redundancy 12 W per pair Internal or external Stratum 3 or 4, selectable ANSI/ITU-T Composite (64 kHz), T1BITS (1.544 MHz), E1ETSI (2.048 MHz), and DS0A Composite (64 kHz) One RJ-45 (with either 120 ohm or 75 ohm termination)
Release 9.0.0 255-700-447

CPU4 Module Specifications

The specifications for the CPU4 module are given in Table 2-5.
Table 2-5. CPU4 Module Specifications Specification Description
Slot configuration Dimensions Weight Units per system Power consumption Processing Memory Connectors
Slots 16 and 17 17.3 cm H x 2.4 cm W x 24.1 cm D (6.8 in. H x 0.95 in. W x 9.5 in. D) 308.4 g (0.68 lb) 1 for nonredundant operation and 2 for redundant operation 15 W maximum RISC-based microprocessor 512 MB compact flash system disk 512 MB SDRAM Two RJ-45 connectors labeled ETHERNET1 and ETHERNET2 (reserved for future enhancements) and one RJ-12 connector labeled CONSOLE
CPU2 Module Specifications

The specifications for the CPU2 module are given in Table 2-6.
Table 2-6. CPU2 Module Specifications Specification Description
Slot configuration Dimensions Weight Units per system Power consumption Processing Memory Connectors
Slots 16 and 17 17.3 cm H x 2.4 cm W x 24.1 cm D (6.8 in. H x 0.95 in. W x 9.5 in. D) 454 g (1 lb) 1 for nonredundant operation and 2 for redundant operation 18 W maximum RISC-based microprocessor 140 MB flash drive 128 MB RAM One RJ-45 connector labeled ETHERNET and one RJ-12 connector labeled CONSOLE
Alarm Module Specifications

Table 2-7 shows the physical and environmental hardware specifications for the Alarm module.
Release 9.0.0 2-11

Table 2-7. Physical Hardware Specifications for the Alarm Module Specification Description
Dimensions Weight Alarm and Output Control Relays Remote status inputs and remote ACO input
*
17.3 cm H x 2.41 cm W x 23.2 cm D (6.8 in. H x 0.95 in. W x 9.13 in. D) 360 g (0.8 lb.) Form 1-C contacts (NC/NO/COM) Opto-isolators (IN/COM) for dry contact* relays
Maximum Relay and Sensor Power 1 A at 48 V dc typical, 60 W maximum, 2 A dc maximum
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.
PacketStar I/O and Server Modules Specifications

Table 2-8 provides the general physical hardware and environmental specifications for the PacketStar PSAX I/O and server modules.
Table 2-8. Physical Hardware Specifications for PSAX I/O and Server Modules Specification Description
Dimensions Weight
17.3 cm H x 2.41 cm W x 24.1 cm D (6.8 in. H x 0.95 in. W x 9.5 in. D) 0.45 kg (1.0 lb.), approximate 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 description 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
Release 9.0.0 255-700-447

Table 2-9. Performance and Power Specifications for the PSAX Modules Module Total Amount of SDRAM Module Maximum Program and Input Data Space Buffer* DS1/T1 Interface Modules Output Buffer Chassis Speed Maximum Power Consumption
20N33 IMA
6-Port DS1
16 MB 16 MB
8 MB 8 MB
1 MB 1 MB
7 MB (114,688) 7 MB (114,688) 13 MB (212,992) 16 cells/ port 13 MB (212,992) 13 MB (212,992) 13 MB (212,992) 7 MB (114,688) 7 MB (114,688) 13 MB (212,992) 13 MB (212,992) 13 MB (212,992) 13 MB (212,992) 13 MB (212,992)
Low Speed Low Speed Low Speed High Speed Low Speed Low Speed Low Speed Low Speed Low Speed Low Speed Low Speed Low Speed Low Speed Low Speed
18 W 18 W
20N36 6-Port Enhanced DS1/T1 Multiservice 23N64 12-Port Medium-Density DS1 Multiservice 24N64 12-Port Medium-Density DS1/E1/DS0A CES 23N33 12-Port Medium-Density DS1 IMA 23N35 24-Port High-Density DS1 Multiservice 23N69 HDSL-2 20N34 IMA 8-Port
24 MB
7 MB
4 MB
14.5 W
8 MB
8 MB
2 cells/ port 4 MB
11.5 W
24 MB
7 MB
14.5 W
24 MB
7 MB
4 MB
20.5 W
24 MB
7 MB
4 MB
20.5 W
E1 Interface Modules
6-Port E1
16 MB 16 MB
8 MB 8 MB
1 MB 1 MB
18 W 18 W
20N56 6-Port Enhanced E1 Multiservice 23N66 21-Port High-Density E1 Multiservice 23N34 21-Port High-Density E1 IMA 23N60 1-Port Channelized DS3 Multiservice 23N61 1-Port Channelized DS3 CES 23N68 IMA 1-Port DS3
24 MB
7 MB
4 MB
14.5 W
24 MB
7 MB
4 MB
14.5 W
DS3, E3, and STS-1e Interface Modules
24 MB
7 MB
4 MB
13 W
24 MB 24 MB
7 MB 7 MB
4 MB 4 MB
13 W 13 W
Release 9.0.0 2-13

Table 2-9. Performance and Power Specifications for the PSAX Modules (Continued) Module Total Amount of SDRAM Module Maximum Program and Input Data Space Buffer* Output Buffer Chassis Speed Maximum Power Consumption
20N03 1-Port Unchannelized DS3 Frame Relay 20N02 ATM 20N22 ATM 2-Port DS3 2-Port E3
8 MB
4 MB
1 MB
4 MB (65,536) 4 MB (65,536) 4 MB (65,536) 16 cells/ port 32 MB (524,288) 16 cells/ port 16 cells/ port 13 MB (212,992)
Low Speed Low Speed Low Speed High Speed High Speed High Speed High Speed Low Speed
13 W
8 MB 8 MB 8 MB
3 MB 3 MB 8 MB
1 MB 1 MB 2 cells/ port 32 MB 2 cells/ port 2 cells/ port 4 MB
15 W 15 W 17 W
23N03 3-Port Channelized DS3/STS-1e CES 23N74 3-Port DS3/E3 ATM 23N02 3-Port Unstructured DS3/E3 CES 45N02 3-Port Unstructured DS3/E3 CES Protection 23N62 1-Port Channelized STS-1e, T1 Format 23N75 1-Port Channelized OC3/STM-1 Unstructured CES/ATM Multimode 23N76 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Single-Mode 23N12 1-Port Channelized OC-3/STM-1 CES Multimode 23N13 1-Port Channelized OC-3/STM-1 CES Single-mode 20N12 1-Port OC-3c Multimode with AQueMan
72 MB N/A
8 MB 8 MB
12 W 7W
N/A
8 MB
7W
24 MB
7 MB
13 W
Fiber-Optic Interface Modules
8 MB
8 MB
64 MB
64 MB (1,048,576)
High Speed
10 W
8 MB
8 MB
64 MB
64 MB (1,048,576)
High Speed
10 W
8 MB
8 MB
2 cells/ port
16 cells/ port
High Speed
17 W
8 MB
8 MB
2 cells/ port
16 cells/ port
High Speed
17 W
8 MB
3 MB
2.5 MB
2.5 MB (40,960)
Low Speed
15 W
Release 9.0.0 255-700-447

20N13 1-Port OC-3c Single-Mode with AQueMan 20N14 1-Port OC-3c Multimode with Traffic Shaping 20N15 1-Port OC-3c Single-Mode with Traffic Shaping 20N72 1-Port OC-3c 1+1 APS Multimode 20N73 1-Port OC-3c 1+1 APS 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 20N62 1-Port STM-1 Multimode with AQueMan 20N63 1-Port STM-1 Single-Mode with AQueMan 20N64 1-Port STM-1 Multimode with Traffic Shaping 20N65 1-Port STM-1 Single-Mode with Traffic Shaping 20N92 1-Port STM-1 1+1 MSP Multimode
8 MB
3 MB
2.5 MB
2.5 MB (40,960) 2 MB (32,768) 2 MB (32,768) 12 MB (196,608) 12 MB (196,608) 32MB (524,288) 32MB (524,288) 32MB (524,288) 32MB (524,288) 2.5 MB (40,960) 2.5 MB (40,960) 2 MB (32,768) 2 MB (32,768) 12 MB (196,608)
Low Speed Low Speed Low Speed Low Speed Low Speed High Speed High Speed High Speed High Speed Low Speed Low Speed Low Speed Low Speed Low Speed
15 W
8 MB
3 MB
3 MB
15 W
8 MB
3 MB
3 MB
15 W
32 MB 32 MB 72 MB
8 MB 8 MB 8 MB
12 MB 12 MB 32 MB
11.5 W 11.5 W 12 W
72 MB
8 MB
32 MB
12 W
72 MB
8 MB
32 MB
18 W
72 MB
8 MB
32 MB
18 W
8 MB
3 MB
2.5 MB
15 W
8 MB
3 MB
2.5 MB
15 W
8 MB
3 MB
3 MB
15 W
8 MB
3 MB
3 MB
15 W
32 MB
8 MB
12 MB
11.5 W
Release 9.0.0 2-15

20N93 1-Port STM-1 1+1 MSP Single-Mode 23N72 1-Port OC-12c/STM-4c Multimode 23N73 1-Port OC-12c/STM-4c Single-Mode
32 MB
8 MB
12 MB
12 MB (196,608) 32 MB (524,288)
Low Speed High Speed
11.5 W
72 MB
8 MB (SDRAM) 1 MB (SRAM) 8 MB (SDRAM) 1 MB (SRAM) 4 MB 4 MB
32 MB
13 W
72 MB
32 MB
32 MB (524,288)
High Speed
13 W
Voice 2-Wire Interface Modules
20N32 4-Port Voice 2-Wire Office 20N30 8-Port Voice 2-Wire Station 23N07 Quadserial
8 MB 8 MB
N/A N/A
N/A N/A
Low Speed Low Speed Low Speed Low Speed High Speed Low Speed Low Speed High Speed High Speed High Speed High Speed Low Speed
14 W 15 W
Serial Interface Modules
24 MB 8 MB
7 MB 3 MB
4 MB 1 MB
13 MB (212,992) 4 MB (65,536) N/A 4 MB (65,536) N/A N/A N/A N/A
15 W 15 W
20N07 6-Port Multiserial 23N40 4-Port Ethernet 20N40 Ethernet
Ethernet Interface Modules
32 MB 64 MB
8 MB 8 MB
24 MB 4 MB
13 W 16 W
DSP2 Voice Servers
23N27 Server 23N29 Server 23N26 Server 23N25 Server 23N41 Router 20N41
DSP2C Voice DSP2D Voice DSP2E Voice DSP2F Voice
1 MB (SRAM) 2 MB (SRAM) 2 MB (SRAM) 2 MB (SRAM) 512 MB

**
512 KB (SRAM) 2 MB 2 MB 2 MB
N/A N/A N/A N/A
17 W 15 W 13 W 13 W
Other Server Modules
Enhanced Route Server
490 MB 8 MB
N/A N/A
N/A N/A
18 W 15 W
64 MB
Release 9.0.0 255-700-447

23N28 Tones and Announcements Server 20N79 Alarm
1 MB (SRAM)
512 KB (SRAM)
N/A
N/A
Low Speed
17 W
Alarm Module
N/A N/A
N/A N/A
N/A N/A
N/A N/A
N/A N/A
3W 6W
Stratum 34 Module
PSAX 2300 Stratum 34 20N20 23N20

*
CPU Modules
CPU2 CPU4
128 MB 512 MB
N/A N/A
N/A N/A
N/A N/A
N/A N/A
18 W 15 W
**
On all PSAX I/O modules, except the 4-Port Voice 2-Wire Office and the 8-Port Voice 2-Wire Station modules, 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.
Release 9.0.0 2-17

Release 9.0.0 255-700-447
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 equipment 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 traditionally been carried on separate overlay networks, the PacketStar Multiservice Media Gateway systems aggregate all traffic types into a common network 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 AQueMan (adaptive queue management) firmware algorithm, a patented technology offered by Lucent Technologies to differentiate voice, video, and data requirements. The AQueMan algorithm maximizes bandwidth efficiency while ensuring QoS on a congested network. A cell-counting capability to allow network data collection systems to generate ATM usage-based billing reports
Release 9.0.0 3-1
Chapter 3 System Features

Interface Architecture
A connection gateway application programming interface (API) that provides 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 Digital Network (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 connected ATM interface management entities (IMEs) using Simple Network Management Protocol (SNMP) and an ATM interface management information base (MIB) An alternate rerouting feature, known as dual-homed permanent virtual circuits (DHPVCs), that improves reliability of PVC connections and supports 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 Private 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 pointto-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 associated with generating, receiving, and interpreting F4 and F5 OAM flows. The function types of the OAM cells include fault management, performance 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 adaptation functions from the switching functions of the Multiservice Media Gateway system. The interface architecture has four distinct processes:
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 3-2 Release 9.0.0 255-700-447

Connections Supported
Physical media accessThe physical media access layer handles functions specific to each physical interface, connecting each user port to other users or network elements. Service protocol translationThe service protocol translation process performs segmentation and reassembly (SAR) to adapt non-native ATM services to ATM-based services and back again. It ensures that the data stream is mapped to standard ATM Adaptation Layer (AAL) protocols. ATM addressingATM addressing provides user-specified virtual path identifier/virtual channel identifier (VPI/VCI) coding, bandwidth allocation, and quality of service (QoS) information. QueuingQueuing 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 Multiservice Media Gateway transports these cells from the ATM switching fabric to the I/O port.
The Multiservice Media Gateway system software uses permanent virtual circuits (PVCs) and switched virtual circuits (SVCs) to provide end-to-end connectivity 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 bandwidth. 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 electronic components. Unlike a virtual circuit, after a PVC is established, it functions 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 (automatic) rerouting. Once either a PVC or a permanent VPC has been configured, an SPVC can be established between the two network interfaces serving the PVC by using signaling procedures. Consequently, this type of connection has attributes of both an SVC and a PVC.
Release 9.0.0 3-3

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 connection types 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 trunking of voice calls. The VBR-to-ATM Standard AAL2 VCC SPVC connection type supports the Packet Pipe functionality. SPVC Reconnection Priority Scheme Nonprioritized SPVCs will be reconnected on a first-come-first-serve basis. However, since legal requirements require that 911 emergency voice channels 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 reconnected according to a user-defined priority code 1 through 6. The userassigned reconnection priority 1 is the highest reconnection priority for SPVCs. The priority code is assigned in the Priority field on all SPVC connection 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.
Release 9.0.0 255-700-447

Table 3-1. Sample User-Defined Priority Scheme for Reconnecting SPVC ATM IMA Links User-Assigned Priority Code Traffic Type Typical ATM Service Type
TDMA/CDMA control channels AMPS channel reserved for 911 emergency calls GSM control channels Digital voice channels GSM voice channels Most analog voice channels Management data connections
CBR-1 or VBR-express CBR-2 VBR-express VBR-express CBR-2 VBR-rt2 (will now try CBR-3) UBR
2 3 4 5 6
The SPVC Priority Reconnection feature supports all SPVC connection types. All SPVCs compress voice when configured with the appropriate DSP2x Voice Server module. SPVC connections are rerouted in the event of link failure. Figure 3-1 shows some sample user-assigned priority SPVCs.
AAL2 CIDs (max. 247) AAL2 CIDs (max. 247)
A B
DS1/T1 IMA Link
PSAX System
A Sample Priority 1, AAL2 Trunk for HDLC SPVC B Sample Priority 2, AAL2 Trunk for CE SPVC C Sample Priority 0, PVC
Figure 3-1. Sample SPVC Reconnection Prioritization Scheme
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)

The maximum total number of AAL2 SPVC trunk connections in the chassis 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.
Users can now modify traffic descriptors for active ATM-to-ATM VCC SPVC Modification of Parameters for Active connections. In previous releases, modifying traffic descriptors required SPVC Connections deleting the connection and creating another one with new traffic descriptors. Tearing down and recreating a connection involves two risks: The connections clients might detect the deletion of the SPVC and take action. A different connection request may seize the resources as they are freed by the 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 interfaces. 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 pointto-point SVC call originations, and 2,000 point-to-multipoint call originations. 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 minimum 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.

SVC Functional Description
SVC signaling, per ATM Forum UNI 3.0 and UNI 3.1, is selectable on a perport basis. Call control is performed on the CPU module, including management of the call-state transitions for each of the calls. This process allows ondemand allocation of bandwidth and connection resources. The signaling protocol supports the following basic functions at the UNI interface:
Feature Description
Connection/Call Setup Connection/Call Request
With this feature, calls originate and are established. With this feature, requests of resources for connections to a certain destination are fulfilled. The Information Element (IE) field contains resource information including PCR, SCR, MBS, and QoS class. With this feature, the destination party can respond to a request with VPI/VCI and other information related to the connection/call. With this feature, the information associated with removing the call/connection request is provided. This includes: 1) calls removed because there werent 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 network failures. With this feature, the clearing party can indicate the cause for initiating its removal from a connection/call.
Connection/Call Answer
Connection/Call Clearing
Reason for Clearing
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 the user 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 andbased on resource availability, route determination, and other network factorspresents a network-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:
Release 9.0.0 3-7

Call States
Description
#0Null #1Call initiated
No call exists. UserThe user has requested that the system establish an outgoing call on the network. NetworkThe network has received the call establishment request, but has not yet responded to the outgoing call. UserThe user has received an acknowledgment that all call information required for the outgoing call to be established has been received from the network. NetworkThe network has sent an acknowledgment to the user that all call information has been received. UserFor incoming calls, the user has received the call establishment request, but has not responded yet. NetworkFor incoming calls, the user has sent the call establishment request, but has not received a satisfactory response.
#3Outgoing call proceeding
#6Call present
#8Connect request UserFor incoming calls, when the user has answered the call and is waiting to be awarded the call. NetworkFor incoming calls, when the network has received an answer but the network has not yet awarded the call. #9Incoming call proceeding UserFor incoming calls, when the user has sent acknowledgment that the user has received all call information necessary to establish a call. NetworkFor incoming calls, when the network has received acknowledgment that the user has received all call information necessary to affect call establishment. UserFor 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. NetworkFor incoming calls, when the network has awarded the call to the called user. For outgoing calls, when the network shows that the remote user has answered the call. UserThe user has requested that the network clear the end-to-end connection and is waiting for a response. NetworkThe network has requested a request from the user to clear the end-to-end connection.
#10Active
#11Release request
#12Release indica- UserThe user has received an indication to disconnect tion because the network has disconnected the end-to-end connection. NetworkThe network has disconnected the end-to-end connection and has sent an indication to disconnect the user-to-network connection.

User Interfaces
The following state transition messages are used for ATM point-to-point call and connection control: Call establishment messages: Call proceeding Connect Connect acknowledgment Setup
Call clearing messages: Miscellaneous messages:
Release Release complete Status Status inquiry
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, congestion control 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, forward 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, and data applications.
Circuit Emulation Service

Circuit emulation service transports traffic over a virtual channel-based connection, 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 identifier (VCI). This service transports ABCD signaling bits based on the ATM

User Interfaces
Forum standard for G.704 CAS. M13 multiplexing capabilities are also supported, 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 a full 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 signaling on the output interface. Framing information is converted and assignments 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 applications 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, tone detection, and PCM coding translation) for voice traffic on soft permanent virtual circuit (SPVC) connections between two or more PacketStar PSAX systems.
Circuit Emulation Service for the Multiserial Module
Circuit emulation to ATM connections made through the Multi-Serial module now support 56 Kbps to 64 Kbps bit stuffing for SS7 link transport applications. Bit stuffing is selectable on a port basis by using the CPU software.
Dynamic Bandwidth Circuit Emulation Service

The 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 T1 channels. When channels are not being used for voice traffic, the available bandwidth can be used for LAN UBR-class traffic.
Release 9.0.0 255-700-447

User Interfaces
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 and deleted, 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 changing 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 virtual 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 unstructured 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, typically at the DS3 rate. With the DS3 interface, service providers can concentrate 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 service providers ATM edge switch. Each DS3 ATM module supports two 45Mbps DS3 ports.
HDLC Passthrough Bit Inversion

The High-level data link control (HDLC) Passthrough Bit Inversion feature uses an ITU-TSS link layer protocol standard for point-to-point and point-tomultipoint 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,
Release 9.0.0 3-11

User Interfaces
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: 23N64 23N35 23N66 23N60 23N62 12-Port Medium-Density DS1 Multiservice 24-Port High-Density DS1 Multiservice 21-Port High-Density E1 Multiservice 1-Port Channelized DS3 Multiservice 1-Port Channelized STS-1e, T1 Format
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 information 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 the ATM Forum UNI signaling, with mechanisms added to support source routing, crankback and alternate routing of all call setup requests in case of connection 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.

User Interfaces
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 network. 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 Features Supported by the PSAX 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 Group Dynamics
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.
Release 9.0.0 3-13

User Interfaces
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 a member of the same peer group, both exchange PNNI topology state packets (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 switchs 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 architects to indicate relative link preference when deciding between alternative routes Switches make use of this resource information to assess which of the available paths will best ensure QoS parameters are met.
PNNI Topology State Element (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. For example, 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.)
Release 9.0.0 255-700-447

User Interfaces
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, up to 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. For example, 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 PNNIs capabilities, network architects must pay careful attention to the ATM addressing structure, allocating correct addresses to switches at each level of the hierarchy.
Release 9.0.0 3-15

User Interfaces
Grandparent Peer Group

Logical Link Highest Level Peer Group Logical Group Node
A B
Peer Group Leaders
Parent Peer Group
PG(A) A.1 A.4 A.2 A.3
PG (B) B.1 B.2
Child Peer Groups

PG(A.2)
A.2.3 A.2.2 A.2.1
PG(B.1)
B.1.1
PG(B.2)
B.2.1 B.2.2 B.2.5 B.2.3 B.2.4 C.1
PG(A.1)
A.1.3 A.1.2 A.4.2 A.1.1 A.4.3
PG(C)
C.2
PG(A.4)
A.4.1
PG(A.3)
A.3.1 A.3.4 A.4.4 A.3.2 A.3.3
B.1.2 B.1.3
A.4.5 A.4.6 [ Source: Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni-0055.000 ]
Figure 3-2. PNNI Hierarchical Topology Showing Three Node Levels
ATM Maintenance
Adding new equipment, such as another PacketStar PSAX Multimedia Gateway, to an ATM circuit already carrying traffic, or taking down an existing connection, has previously required taking the affected interfaces out of service, disrupting all connections. It is now possible, by changing the administrative weight of a private network-to-network interface (PNNI), to maintain the ATM connection, without disrupting traffic on existing permanent virtual circuit (PVC), soft permanent virtual circuit (SPVC), or switched virtual circuit (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
Release 9.0.0 255-700-447

User Interfaces
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 interfaces administrative weight is changed, traffic on existing connections (PVC, SVC, SPVC) will not be disturbed. 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 following 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
Release 9.0.0 3-17

User Interfaces
With System Software Release 6.5.0, VPI and VCI range negotiation is supported. 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 PNNI Overview 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 Configuration window. For more information on automatic configuration procedures, see ATM Forum ILMI (Integrated Local Management Interface), 4.0, af-ilmi0065.000, Section 8.3.4.
Load Balancing for IISP 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 procedures for dynamically establishing, maintaining, and clearing ATM connections at the ATM user-network interface. ATM UNI 4.0 applies both to public and private UNI interfaces.

User Interfaces
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 modification 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 IMA allows 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 automatically 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 implemented 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 compatibility 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 "InsufficientLinks." 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.

User Interfaces
~ 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 consider 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 configured and the far-end is connected to equipment that doesnt 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 value instead 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 and SVC 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 following PSAX modules: 23N68 20N33 20N34 23N33 23N34 1-Port DS3 IMA 6-Port DS1 IMA 6-Port E1 IMA 12-Port Medium-Density DS1 IMA 21-Port High-Density E1 IMA
Release 9.0.0 255-700-447

User Interfaces
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 or ATM networks. In this way, the Multiservice Media Gateway acts as a gateway between routers, remote-dial access servers, systems network architecture (SNA) equipment, and other devices configured for frame relay operation. FRF.5 Encapsulating Frames 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. 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 both the FRF.8 implementation agreement and the IEFT multiprotocol encapsulation 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.
FRF.8 Converting Frames
Inverse Address Resolution Protocol (ARP)
The Inverse Address Resolution Protocol (ARP) feature using the FRF 8.1 specification provides packet translation between frame relay and ATM interfaces. 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 relayto-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 transmission across the backplane of the Multiservice Media Gateway, and then converted 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 terminal such as a central office PSAX system to flawlessly interface with a

User Interfaces
Lucent Stinger DSLAM, a CellPipe IAD or AdTran TA624.850, and a central 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 provisions for both an open interface network architecture and a digital loop carrier 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 system 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 concentrations 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 configuration 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 module 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 support for the PSAX system central office product line. Loop emulation services allow voice traffic, DTMF, and signaling to be handled over the packet network. 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.

User Interfaces
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/Modem The PSAX system supports fax/modem tone detection for the ATM downlink Master/Slave Support 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 algorithm 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 cancellation 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 the IAD 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 in the 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 feature 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-0712002, 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. 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). 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
Idle Channel Suppression Support for the CellPipe IAD GR-303 Interoperability
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

Dynamic Bandwidth Allocation
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 transmission continues until the traffic volume reaches 10 percent. At this threshold, the transmission of cells from the CE side of the interface to the backplane 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 backplane to the CE side of the CE-to-ATM connection. The DBA feature operations are illustrated in Figure 3-3.
Release 9.0.0 255-700-447

Network Management
NORMAL OPERATIONS
CE Interface
DBA
12-Port MD DS1/E1/DS0A CES Module
Backplane Traffic Allowed
INHIBITED OPERATIONS
CE Interface
DBA
12-Port MD DS1/E1/DS0A CES Module
Backplane Traffic Inhibited
Normal Traffic No Traffic
Figure 3-3. DBA-Controlled Backplane Traffic
The DBA feature is supported on the following module: 24N64 12-Port Medium-Density DS1/E1/DS0A CES (DS1 mode only)
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 software features a Simple Network Management Protocol (SNMP)-compliant management information base (MIB) that gives external management systems access to the PSAX system software.
Release 9.0.0 3-25

Network Management
In conjunction with the visual indicators displayed on the front panels of the individual modules, the system offers a full complement of SNMP trap messages 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 components for supporting services.
Network Management Options

The PSAX system software supports the following options for network management: 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 workstation or a console monitor, running a standard VT100 terminal emulator, is connected. 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 connection), but it can also be used for remote management. Remote management 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 system. 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 interface 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 single PVC connection from a management workstation (management host) running an SNMP client over an ATM WAN. This allows for IP-based functions (that is, telnet) and SNMP functions (that is, element and network management software) to be performed remotely using ATM virtual circuits, which terminate within the managed node. The PVC/SVC connecPacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 3-26 Release 9.0.0 255-700-447

Network Management
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 inband 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 Version 3 of the Simple Network Management Protocol (SNMPv3) as a full standard. SNMPv3 contains additional security and authentication features that provide data origin authentication, data integrity checks, timeliness indicators and encryption to protect against threats such as masquerade, modification 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 providing 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 network 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 Operation Support Systems (OSS) to SNMPv3 support. For this reason, the implementation 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 SNMPv2c when 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 messages with both SNMPv2c and SNMPv3.
Release 9.0.0 3-27

PSAX System Software Features
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 a single location, using easy-to-use windows. The AQueView EMS also provides centralized configuration, diagnostic, performance, and security management 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 OpenView 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 platforms without HP OpenView NNM For more information on AQueView functionality, refer to the following documents: 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 Client/Server Application, Release 9.0.0, Document Number 255-700-496 Navis AQueView Element Management System User Guide for Standalone Systems, Release 9.0.0, Document Number 255-700-493 Navis AQueView Element Management System Quick-Start Guide for Standalone Systems, Release 9.0.0, Document Number 255-700-497

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 Statistics Server. The collection of PSAX system statistics can be used for network 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.
Release 9.0.0 255-700-447

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 Gateway The Connection Gateway Application Programming Interface (CGAPI) proAPI Overview vides a communications protocol or set of messages by which a call controller can control ATM switching on a PSAX system using nonnative ATM networking protocols. See the PacketStar Connection Gateway Application Programming Interface Developers 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 monitoring, 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 a failure. 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 modules 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 Configuration, a Connection Gateway API interface address is used as an interface on which to send Connection Gateway API messages.
PSAX System As a TCP Client/Server for the Connection Gateway 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).
Release 9.0.0 3-29

Ethernet Module
ATM I/O Module
ATM WAN
Local Access Concentrator (Primary TCP Client) Ethernet Hub Call Controller Device (Computer) (TCP Server) Ethernet ATM I/O Module Module In-band Management PVC Connection In-band Management PVC Connection
ATM I/O Module
ATM WAN
Local Access Concentrator (Backup TCP Client) Remote Access Concentrator (TCP Client)
Figure 3-4. PSAX System as a TCP Client Device
You can also set up the PSAX system as a TCP server device with the call controller set up as the client device. As an option, you can connect two call controllers, set up as primary and backup client devices, to the PSAX system (server device) (see Figure 3-5).
Ethernet Connection
Ethernet Hub
Ethernet Module
ATM I/O Module
Route Server Module
Call Controller Device-Primary (Computer) (TCP Client) Local Access Concentrator (TCP Server)
Ethernet Connection
ATM I/O Module In-band Management Connection
ATM WAN
Call Controller Device-Backup (Computer) (TCP Client) Remote Access Concentrator (TCP Server)
Figure 3-5. PSAX System as a TCP Server Device
Release 9.0.0 255-700-447

Fractional PRI Support
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 Bchannels 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 Bchannel. 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 Dchannel 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 Connection 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 customer interface equipment and network interface equipment, for example, between PSAX central office (CO) products and customer premises equip-
Release 9.0.0 3-31

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 Codes

In 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 followed 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 normallythat is, passes real trafficuntil 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.
Release 9.0.0 255-700-447

PSAX System Traffic Protection Capabilities

1:1 Traffic Protection Patch Panel Module The 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.
s
The I/O modules are configured in matched pairs, one working and one protection. In normal operation, the working module is configured to pass traffic. The protection module is matched with the working module and configured 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 module under 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. InterSlot Communication (ISC) cells are exchanged between the working and protection module. If the protection module detects eight consecutive missing 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 condition 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 module, 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

The user can manually switch traffic from the working module to the protection 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 working module 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.
Chassis Backplane Backplane
Active
Working Module Slot 3
Protection Module Slot 4
Standby
Protection Patch Panel Line
Normal Data Flow
Chassis Backplane Backplane
Failed
Working Module Slot 3
Protection Module Slot 4
Active
Protection Patch Panel Line
Failed Working Module
Figure 3-6. 1:1 Protection Scheme on the PSAX System
Release 9.0.0 255-700-447

Restoring Service to the Working Module After automatic or manual switchover has been performed and the replacement 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, the PSAX system recognizes it as an unconfigured module. The user then executes 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 Optical Modules The 1+1 Automatic Protection Switching (APS)/Multiplex Section Protection (MSP) feature provides connection redundancy for traffic flow protection on the 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 chassis. 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 module are not automatically switched back to the active module after a failed link becomes operational again. One advantage of nonrevertive switching is minimal service interruptionone interruption instead of two.
Release 9.0.0 3-35

Interface Protection Group 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 having the 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 interfaces together by specifying which interfaces in the group are primary (normally 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 interface. 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 Protection Group Table and the Interface Protection Table windows on the console interface. When a switchover is initiated by the primary interface, the IWF for that interface is torn down and replaced by the standby interfaces IWF within that group. These configurations are displayed on the appropriate PVC connection screen.
Release 9.0.0 255-700-447

PSAX 2300
IMA DS1
DS3 IMA
Primary 1 Group 1 Primary 2 Group 1 Primary 3 Group 1
AX4000 Gen/Ana
ATM
Primary 4 Group 1 Primary 5 Group 1 Primary 6 Group 1
Figure 3-7. Typical Interface Protection Group Configuration
This software feature moves connections within a defined group whenever a failure condition occurs or the user issues a switchover/switchback command. The switchover method is either automatic, whereby the traffic from a primary 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 switchover. The switchback method is either automatic, whereby the traffic from the standby interface is switched back to its corresponding recovered primary interface, 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 Rerouting Using Dual-Homed PVCs
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
Release 9.0.0 3-37

The DHPVC feature enables users to set up a primary and a standby connection 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 connection. Rather, ATM trunk interfaces can be used in a load-sharing design with the connection admission control (CAC) constraints automatically considered when the primary and standby connections are configured. This technique 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 only the network parameters that are associated with the standby connection (egress slot, egress port, VPI, and VCI). The remaining parameters are governed by the primary connection. Because DHPVC connections make use of PVCs within the network, interoperability issues do not exist with intervening network devices. During normal operation, the primary connection carries 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 associated network element that detects the failure generates an OAM F5 alarm indication signal (AIS) to the downstream node, which in turn sends the AIS to the destination edge node. At that point, the edge node converts the AIS to remote defect indication (RDI) messages, which are transmitted to the originating node. Intermediary nodes relay the RDI messages upstream, ultimately to the originating or terminating nodes. Upon detecting an AIS/RDI alarm on a DHPVCconfigured 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.
Release 9.0.0 255-700-447

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 connection to a standby connection is shown in Figure 3-8.
ATM Network
Link failure Multiservice Media Gateway Interrupted service Primary PVC Standby PVC Continued service Primary PVC Standby PVC Multiservice Media Gateway
Figure 3-8. Automatic Traffic Rerouting using Dual-Homed PVCs
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 execute the downloaded code that controls the module. You do not need to download an I/O or server modules 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 current firmware.
Release 9.0.0 3-39

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 environment, such as traffic transmitted across satellite or line-of-sight radio-frequency 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 created 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 indicator (PTI) and generic flow control (GFC) fields need to be separately protected 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-correction capability, as follows: 1/2 rate For each data cell, the encoder creates two encoded cells. This rate provides correction of payload cells with 10-3 BER to 10-6 BER.

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):
Table 3-2. Forward Error Correction Automatic Rate Options Bit Error Rate Cell Encoding Rate 10-3 Threshold 10-4 10-5 Threshold Threshold
Automaticlow quality Automatic Automatichigh quality
1/2 rate 1/2 rate 1/2 rate
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 module.
The following modules support FEC enabled connections: 20N07 23N07 6-Port Multiserial Quadserial
H.248 Media Gateway Access Protocol

The PacketStar PSAX Multiservice Media Gateways support the ITU-T Recommendation 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 networks. Decentralization enables transmission cost savings resulting from enabling gateway peripherals from a central MGC to terminate trunking circuits near the circuit switches from which they originate.
Release 9.0.0 3-41

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

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 connection name. All named connections in the PSAX system can be viewed on the new Connection Name Table window, which is accessed from the Connection Configuration Menu window. The following PVC and SPVC connections types support connection naming: AAL2 trunk connection PVC ATM-to-ATM VCC PVC ATM-to-ATM VPC PVC Bridge-to-ATM PVC Bridge-to-bridge PVC Circuit emulation-to-ATM VCC PVC Circuit emulation-to-circuit emulation PVC Frame relay-to-ATM VCC PVC Frame relay-to-frame relay PVC GR-303-to-AAL2 VCC PVC In-band management IP PVC VBR-to-ATM VCC PVC VBR-to-VBR PVC ATM-to-ATM VCC SPVC ATM-to-ATM VPC SPVC Circuit emulation-to-ATM VCC SPVC Circuit emulation-to-ATM standard AAL2 VCC SPVC Frame relay-to-ATM VCC SPVC VBR-to-ATM VCC SPVC VBR-to-ATM standard AAL2 VCC SPVC
For the interface and connection names, the user can specify up to 35 alphanumeric characters including AZ, az, 09, / (forward slash), - (hyphen), and _ (underscore). The PSAX system differentiates between uppercase and lowercase letters, making the text string for the interface name and the connection 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 inband management virtual port) to prevent the CPUn module from being excessively burdened with traffic. The feature may be applied only to the primary CPUn module, not to the backup CPUn module. The feature is initially disabled when the system is running. Once the feature is enabled, traffic will go through the ETHERNET port or the in-band management virtual port by its maximum designated throughput set in the Allowed
Release 9.0.0 3-43

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 Protocol
The LANET (limitless ATM network) protocol, coupled with a simple errortolerant 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 applicationdependent payload protection, allowing selective implementation of bandwidth-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 environments Compatibility with traditional link enhancement schemes, such as forward error 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.
Release 9.0.0 255-700-447

SERVICE-INDEPENDENT ARCHITECTURE
Voice
Layer 7 Layer 6 Layer 5 Layer 4 Layer 3 Layer 2 Layer 1 Encryption Satellite
Video
Images
Data
CELL-BY-CELL ENCRYPTION
ATM
LANET Protocol
Error Correction Radio Bit Interleaf Land Lines
From bits per second to megabits per second
Figure 3-9. Relationship Between LANET and the OSI Model
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 purposes 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 conjunction 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 naturally synchronizing with an 8-kHz transmission clock via the 2,400-bytesper-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 system software uses an error-tolerant addressing scheme (multiple redundancy addressing) 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
Release 9.0.0 3-45

encodes the header address within the same 10-nibble header space of standard 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 setting 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-protected on each virtual circuit, depending on the error tolerance of the application at the service-specific convergence sublayer (SSCS). Figure 3-10 shows the LANET frame structure.
Figure 3-10. 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.
Release 9.0.0 255-700-447

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 information 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 operations information between the various nodes in a network. In the case of an ATM network, this information is exchanged over permanent and switch virtual 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 Cell Characteristics
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 segment, 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 belong to 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 terminate unexpected OAM cells coming from the upstream side of a connection. 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. Endto-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 directions). 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:
Release 9.0.0 3-47

Header OAM Function Type Header 4 4 OAM Cell Type

Figure 3-11. OAM Cell Fields
Payload Reserved 6 10 Error Detection Code
360 bits (45 bytes) Function-specific field
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 Layer Flows
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:
Release 9.0.0 255-700-447

Figure 3-12. OAM Hierarchy
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 virtual 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
Release 9.0.0 3-49

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 operations communication. PTI=5 is an end-to-end OAM F5 flow cell. This flow is identified by its standardized 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 OAM Functions
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 as a loss of frame. This prevents the generation of unnecessary alarms, and maintains communications. ~ Remote Defect Indication (RDI) RDI cells are generated and tranmitted while the AIS state persists in order to indicate in the backward direction an interruption of the cell transfer capability in the forward direction. ~ 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 continuity 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 preservice 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 operators 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 loopback, it declares a time out. The following types of loopback are supported: End-to-end: Sends cells from one designated end-point to another.
Release 9.0.0 255-700-447

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 confirmation, 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 6 Directions of Action 2 Correlation Tag 8 PM Block Size A-B 4 PM Block Size B-A 4 Unused 336 bits (42 bytes)
Figure 3-13. OAM Activation/Deactivation Cells
Message ID cells indicate whether to request, confirm, or deny the activation 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 bidirectionally. Correlation tag cells give the number used to correlate transmitted activation/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 AAL5 for backhauling between the BS and the MSC provides cost benefits over a TDM-based backhauling system currently in use. The Packet Pipe AAL5-toAAL2 Wireless Trunking feature on the DSP2E/F Voice Server modules addresses this need.
Release 9.0.0 3-51

This feature supports packet switched wireless backhaul networks for interconnecting Lucent MSCs and Series II base stations using the Lucent proprietary packet pipe protocol over land lines. This protocol performs encapsulation 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 DS3 Multiservice 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 interleaved 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 service 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 prioriPacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 3-52 Release 9.0.0 255-700-447

ties. One queue set addresses avoidance of cell loss, which is normally a concern 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 priorities 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 algorithm accounts for the service-level priorities of the traffic when determining which cells to discard during traffic congestion. Thus, CBR does not necessarily imply a higher priority.
Table 3-3. CBR and VBR Service-Level Priorities Priority CBR VBR
High Low
911 voice call Off-peak cellular voice
Network management data IP data
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-priority VBR data in cases where there are too many cells in lower-priority VBR 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 indefinitely. 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 periodically 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 decongestion of the network without resorting to traffic rerouting and other complicated protocols and procedures.
Release 9.0.0 3-53

ATM Traffic Management

Guaranteed Frame Rate 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 the MCR rate. Traffic transmitted in excess of MCR and MBS rates are delivered within the limits of available resources. The fairness policy is network specific. The Guaranteed Frame Rate (GFR) feature for ATM Traffic Management operates on the following PSAX I/O modules: 12-Port Medium-Density DS1 Multiservice 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 Parameter Control Usage parameter control (UPC) allows the end system to police ingress connections for service level agreement compliance. After a set of service categories is specified, UPC is given a set of parameters for each, describing the traffic 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 theCell bus traffic shaping feature, which was formerly called Traffic Shaping.
UPC Support
UPC support is available on these modules: 23N75 23N76 23N72 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Multimode 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Single-Mode 1-Port OC-12c/STM-4c Multimode
Release 9.0.0 255-700-447

23N73 20N72 20N73 20N92 20N93 24N70 24N71 24N72 24N73 23N66 23N64
1-Port OC-12c/STM-4c Single-Mode 1-Port OC-3c 1+1 APS Multimode 1-Port OC-3c 1+1 APS Single-Mode 1-Port STM-1 1+1 MSP Multimode 1-Port STM-1 1+1 MSP Single-Mode 2-Port OC-3c/STM-1 ATM Multimode 2-Port OC-3c/STM-1 ATM Single-Mode 4-Port OC-3c/STM-1 Multimode 4-Port OC-3c/STM-1 Single-Mode 21-Port High-Density E1 Multiservice 12-Port Medium-Density DS1 Multiservice
UPC is available on these DS3 modules (when using channelization to DS0s): 23N60 23N68 23N07 1-Port Channelized DS3 Multiservice 1-Port DS3 IMA Quadserial
Early Packet Discard
The PSAX system ATM Traffic Management feature includes the implementation of the early packet discard (EPD) function for PVC and SPVC connections that support the service type UBR and the SAR type AAL5. The EPD function improves the efficiency of the connection by reducing the amount of bandwidth needed when traffic congestion occurs. During traffic congestion, the EPD function causes packets to be discarded at the moment the system 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 discarded after several cells have already been sent. Users enable the EPD function when they choose the service type UBR and the SAR type AAL5 on ATM PVC and SPVC connections. 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 OC3c MM/SM TS and the STM-1 MM/SM TS modules. (The feature is not compatible with the VI Support feature or the UPC Support feature on the connection 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).
Cell Bus Traffic Shaping
Release 9.0.0 3-55

Note:
The feature that was formerly known as Traffic Shaping is now called Cell bus traffic shapingto distinguish it from the ATM Traffic Shaping feature, which was formerly called Rate Shaping.
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 transport 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.
Any ATM Module
PSAX Bus
OC-3c Module Traffic Router Egress Bursty PCR 6 MB
Traffic Shaping on a 2 MB Service Contract Occurs Here
Figure 3-14. Cell Bus Traffic Shaping Occurs on Egress to the Backplane
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 following 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 contracts, causing clusters of cells to exceed the MBS parameter. Because carriers monitor traffic at the edge of a network and enforce adherence to traffic contracts by discarding cells that exceed the MBS parameter, end users whose traffic violates their contractual MBS parameter experience high cell loss
OC-3c
ATM

(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 effectively smooths bursty input LAN traffic to comply with the carrier traffic contract. The input cell-selection buffering scheme is shown in Figure 3-15.
MBS Greater Than 250 Cells
Line Rate
SCR
Sample Input on a VPC/VCC Connection from a Bursty LAN VPC/VCC 1 Input Enters OC-3c Module Buffer VPC/VCC 2 Maximum Capacity Minimum Capacity
MBS of Each VPC/VCC Connection Usually Less Than 50 Cells SCR
SCR
To Backplane
VPC/VCC 119 OC-3c Module Buffer Smoothed VPC/VCCs SCR
Figure 3-15. Cell Bus Traffic Shaping Using the Input Cell-Selection Algorithm
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 example, 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 minimum-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 discards 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 minimum-capacity level.
Release 9.0.0 3-57

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:
Sustained Cell Rate (SCR) of VPC/VCC Maximum Burst Size (MBS) of Traffic Shaped Output
020 Mbps 2030 Mbps 3040 Mbps 75120 Mbps
< 4 cells < 5 cells < 6 cells approximately 2050 cells
The OC-3c TS and the STM-1 TS modules can perform Cell Bus Traffic Shaping on multiple high-rate connections (such as three 40-Mbps connections). Assigning a SCR to a connection above 75 Mbps, however, is not recommended 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 management 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 ATM Traffic Shaping The ATM Traffic Shaping feature uses an algorithm to transmit frames segmented 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 supporting 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.
Release 9.0.0 255-700-447

4-Port Ethernet Module Side A A to B Side Tx/Rx Bursty PCR to 6 MB B to A Side Egress Ingress
PSAX Chassis Backplane or Midplane
Traffic Shaping does not occur on egress B to A side direction 2-Port or 4-Port OC-3c/STM-1 Module Side B B to A Side Rx ATM Tx Traffic Shaping on 2 MB Service Contract A to B Side Egress Ingress
Traffic Shaping occurs on egress B to A side direction
Figure 3-16. Sample ATM Traffic Shaping Flow
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 ATM Traffic Shaping for HDLC, Frame Relay, and Ethernet Virtual Channels
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: 20N72 20N73 20N92 20N93 23N72 1-Port OC-3c 1+1 APS Multimode 1-Port OC-3c 1+1 APS Single-Mode 1-Port STM-1 1+1 MSP Multimode 1-Port STM-1 1+1 MSP Single-Mode 1-Port OC-12c/STM-4c Multimode
Release 9.0.0 3-59

23N73 24N70 24N71 24N72 24N73 23N74
1-Port OC-12c/STM-4c Single-Mode 2-Port OC-3c/STM-1 ATM Multimode 2-Port OC-3c/STM-1 ATM Single-Mode 4-Port OC-3c/STM-1 Multimode 4-Port OC-3c/STM-1 Single-Mode 3-Port DS3/E3 ATM
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 VBRto-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 for Implementing ATM Traffic 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 Traffic Shaping 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 connections 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
Release 9.0.0 255-700-447

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 connection to minimize the probability that a CBR or VBR-rt cell will be transmitted at the same time a ATM traffic-shaped cell is scheduled to be transmitted. It is critical that accurate values for the connection parameters be used. ATM Traffic Shaping for 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. Furthermore, 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 of Each OC-3c 1+1 APS and STM-1 1+1 MSP module supports 2,046 trafficATM Traffic-Shaped shaped connections. The minimum PCR rate supported by the algorithm is Connections 20 cps; the maximum is 4680 cps (E1 interface speed). A rounding error is introduced 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 delivered by the ATM Traffic Shaping feature. For example, if the ATM trafficshaped 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 divergence is smallest at low PCR. How the ATM Traffic Queuing is maintained for the traffic-shaped connections on a per VC basis. Shaping Algorithm To schedule the processing of the queues appropriately such that cells will be Works sent at appropriate intervals, an offset time (versus no offset time) for each queue is calculated based on the PCR. Offset Time Value Formula ATM Traffic Shaping Algorithm The offset time value is calculated by the following formula: T = 353207/PCR 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 13). 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 descriptions of the mechanics of data movement.
Release 9.0.0 3-61

Example Example Box 2 Box 1 Queue 1 = 386 Queue 1 = 1999
Example Box 3 Queue 1 = 6
Box 80,000 Queue 1 = n
2046
2046
2046
2046
Figure 3-17. ATM Traffic Shaping table Sample Queue 1 Values
ATM Traffic Shaping Software in Action
The example below follows the ATM traffic shaper action for boxes 13 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 Traffic 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.
Release 9.0.0 255-700-447

Traffic-shaped queues have the priority of "VBR-shaping" which is below VBR-rt2 and above VBR-nrt1. Generally, in an AQueMan environment, traffic 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 targeted PCR. Formula for Determining the PCR of an ATM TrafficShaped Connection For ATM traffic-shaped connections, you should set the PCR value so that it conforms to the following expression: PCR > 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 connections plus the SCRs of the variable bit rate (real time) connections divided by the interface data rate. The value of F can be expressed mathematically as follows: F= PCR of CBR connections + SCR of VBRrt connections interface data rate SCR (1 - F)
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 Egress Priority on PSAX Modules Supporting ATM 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 contracts 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 following modules: 23N72 23N73 23N74 45N74 24N70 1-Port OC-12c/STM-4c Multimode 1-Port OC-12c/STM-4c Single-Mode 3-Port DS3/E3 ATM 3-Port DS3/E3 ATM Protection 2-Port OC-3c/STM-1 ATM Multimode
Release 9.0.0 3-63

24N71 24N72 24N73
2-Port OC-3c/STM-1 ATM Single-Mode 4-Port OC-3c/STM-1 Multimode 4-Port OC-3c/STM-1 Single-Mode
Connections employing the ATM Traffic Shaping feature have egress priority above VBRnrt and UBR connections but below that of CBR and VBRrt connections on the following modules: 20N72 20N73 20N92 20N93 23N60 23N62 24N64 23N66 23N35 1-Port OC-3c 1+1 APS Multimode 1-Port OC-3c 1+1 APS Single-Mode 1-Port STM-1 1+1 MSP Multimode 1-Port STM-1 1+1 MSP Single-Mode 1-Port Channelized DS3 Multiservice 1-Port Channelized STS-1e, T1 Format 12-Port Medium-Density DS1/E1/DS0A CES 21-Port High-Density E1 Multiservice 24-Port High-Density DS1 Multiservice
ATM Traffic Shaping Capabilities by PSAX Module
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 Max. No. Min. PCR of VCs for Using Traffic Traffic Shaping* Shaping Release in Precision of Which Traffic Traffic Shaping for Shaping One Introduced Connection
Modules
Queue Size
Priority
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 23N72 1-Port OC-12c/STM-4c Multimode
2,046 2,046 2,046 2,046 32,000
18 cps 18 cps 18 cps 18 cps 87 cps
1000 1000 1000 1000
After VBR-rt2 After VBR-rt2 After VBR-rt2 After VBR-rt2
6.3.0 6.3.0 6.3.0 6.3.0 7.1.3
~50% of line rate ~50% of line rate ~50% of line rate ~50% of line rate ~1% of line rate
Program- After CBR mable
Release 9.0.0 255-700-447

Table 3-4. ATM Traffic Shaping Capabilities by Module (Continued) Max. No. Min. PCR of VCs for Using Traffic Traffic Shaping* Shaping Release in Precision of Which Traffic Traffic Shaping for Shaping One Introduced Connection
Modules
Queue Size
Priority
23N73 1-Port OC-12c/STM-4c Single-Mode 23N74 3-Port DS3/E3 ATM
32,000 32,000 32,000 32,000 32,000 32,000 32,000 32,000 32,000 32,000 32,000 32,000 32,000
87 cps 7 cps 24 cps 24 cps
Program- After CBR mable Program- After CBR mable Program- After CBR mable Program- After CBR mable After VBR-rt2 After VBR-rt2 After VBR-rt2 After VBR-rt2 After VBR-rt2 After VBR-rt2
7.1.3 7.1.3 8.1.5 8.1.5 8.1.1 8.1.1 9.0.0 8.1.1 8.1.1 8.1.1 9.0.0 9.0.0 8.1.5
~1% of line rate ~1% of line rate ~1% of line rate ~1% of line rate ~50% of line rate ~50% of line rate ~50% of line rate ~50% of line rate ~50% of line rate ~50% of line rate ~1% of line rate ~1% of line rate ~50% of line rate ~50% of line rate
24N72 4-Port OC-3c/STM-1 Multimode 24N73 4-Port OC-3c/STM-1 Single-Mode 23N64 12-Port MediumDensity DS1 Multiservice 23N35 24-Port High-Density DS1 Multiservice 23N34 E1 IMA 21-Port High-Density
150 cps Programmable 150 cps Programmable 150 cps Programmable 150 cps Programmable 150 cps Programmable 150 cps Programmable 24 cps 24 cps 24 cps
23N66 21-Port High-Density E1 Multiservice 23N60 1-Port Channelized DS3 Multiservice 23N62 1-Port Channelized STS-1e, T1 Format 24N70 2-Port OC-3c/STM-1 ATM Multimode 24N71 2-Port OC-3c/STM-1 ATM 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
Program- After CBR mable Program- After CBR mable Program- After CBR mable Program- After CBR mable
32,000
24 cps
8.1.5
* If you specify a rate below the minimum supported PCR, the module defaults to traffic shaping at 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.
Release 9.0.0 3-65

Virtual Interfaces
Virtual interfaces (VIs) are configured on a modules physical ports and allow virtual channels (VCs) to be assigned to virtual trunks, each with its own priority queues. By using VIs instead of physical connections, it is possible to achieve an advanced bandwidth management capability allowing for fully flexible 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 violating 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 multiple 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.
Single PVC VCC with UPC Single VPC w/ multiple SVC VPI/VCI inside Virtual Interface 1 Virtual Interface 2 Virtual Interface 3 Virtual Interface 4 Virtual Interface 0 WAN ATM Link
Multiple VPC w/ UPC All other Traffic with UPC control and Traffic Shaping
Figure 3-18. Sample Uses of Virtual Interfaces
PSAX Modules Supporting Virtual Interfaces
The Virtual Interfaces feature is supported on the following PSAX modules: 20N72 20N73 20N92 20N93 23N72 23N73 24N70 24N71 24N72 1-Port OC-3c 1+1 APS Multimode 1-Port OC-3c 1+1 APS Single-Mode 1-Port STM-1 1+1 MSP Multimode 1-Port STM-1 1+1 MSP Single-Mode 1-Port OC-12c/STM-4c Multimode 1-Port OC-12c/STM-4c Single-Mode 2 Port OC-3c/STM-1 ATM Multimode 2 Port OC-3c/STM-1 ATM Single-Mode 4-Port OC-3c/STM-1 Multimode
Release 9.0.0 255-700-447

24N73 23N74 45N74
4-Port OC-3c/STM-1 Single-Mode 3-Port DS3/E3 ATM 3-Port DS3/E3 ATM Protection
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 illustration of this concept.
Table 3-5. ATM Traffic Shaping, UPC Support, and VI Support Configuration Compatibility Fields on ATM UNI, PNNI, and IISP Configuration Windows ATM Traffic VI Support Shaping per VC UPC Support
ATM Traffic Shaping per VC VI Support UPC Support No Yes

*
No Yes
Yes* 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.
Release 9.0.0 3-67

I/O Module 1 Rx Tx Ingress Path UPC VI or TS Egress Path Chassis Backplane I/O Module 2 Rx Tx Ingress Path UPC VI or TS Egress Path
Figure 3-19. Combining the UPC Feature and Either the TS or VI Feature on a Connection
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 Release 8.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 compression 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 suppression is supported per ITU-T I.366.2 to prevent the use of bandwidth for channels 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:

Voice 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 narrowband 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 configured 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 carried 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 modules. 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 turning off voice processing and echo cancellation on any channel when it detects a modem tone. See the PacketStar PSAX DSP2x Voice Server Module User Guide for information detailing the nine AlgoSets (algorithm sets) and the type of voice compression offered, if applicable.
Echo Cancellation
Near-end echo is caused by the transmitted voice signal on a 2-wire subscriber 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 signal back to the receiver at the same amplitude but 180 degrees out of phase with the transmitted signal. See the PacketStar PSAX DSP2x Voice Server Module User Guide for information detailing the seven AlgoSets (algorithm sets) and the type of voice compression offered, if applicable.
Release 9.0.0 3-69

Voice Processing
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-toAAL2 Wireless Trunking feature addresses this need. This feature supports packet-switched wireless backhaul networks for interconnecting Lucent MSCs and Series II base stations using the Lucent proprietary packet pipe protocol over land lines. This protocol performs encapsulation 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-toAAL2 conversions. These capabilities make it ideal in wireless backhaul applications between base stations and Mobile Switching Centers (MSCs). The module is particularly suited to environments where Lucents proprietary HDLC-based PacketPipe is used combined with analog voice traffic. The DSP2F module is a high-speed, digital signal processing module specialized to do AAL2-to-AAL5 conversions. These capabilities make it ideal in wireless backhaul applications at the MSC end in environments where Lucents 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 connection 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.
Release 9.0.0 255-700-447

Voice Processing
PSAX 4500 in MSC
PSAX 1000 Cell Sites A HDLC AAL5 DSP2E ATM CE B Pure Voice AAL2 Trunks Backhauled via Land Lines Cellular Data/Voice in Same Packet ATM DSP2D C
G DSP2F H CES CO 5ESS
A TDM Voice/AAL1 B 48 Channels TDM/AAL2 C 384 Channels AAL2 D 384 Channels TDM/AAL1
Data/AAL5
168 Channels PacketPipe F Bit Inverted HDLC/AAL2 G 672 Channels/AAL2 H 672 Channels PacketPipe/AAL5
Figure 3-20. PacketPipe AAL5-to-AAL2 Wireless Trunking from Cell Site to MSC for Mobile Voice
DSP features on wireless applications are supported on these modules: The following PSAX modules support the Wireless Mobile Voice feature: 1-Port Channelized DS3 Multiservice 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.
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 relative to some other grouping of IP interfaces on the same device. An IP interface 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.
STS-1e

Voice Processing
Enterprise 1/ Service Provider 1
Each Enterprise/Service Provider occupies its own virtual router space.
The Enterprise/Service Provider consist of one or more physical connections. Interfaces are assigned through configuration mechanisms and may be logical or physical entities.
Ingress/Egress IP Traffic Edge Device Ingress/Egress ATM Traffic
R O U T I N G
R O U T I N G
R O U T I N G
ATM Network
Figure 3-21. Virtual Router Concept
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.
FR Connections Partitioned into Interfaces

192.001.001.001 255.255.255.000
Existing In-Band Management
Console
Virtual Router #1
FR
192.001.002.001 255.255.255.000 192.001.003.001 255.255.255.000
ATM E R
M O D U L E
C P U
S T R A T U M
P O W E R
Virtual Router #2
145.121.215.001 255.255.000.000 145.122.215.001 255.255.000.000 145.123.215.001 255.255.000.000 Existing In-Band Management 192.001.004.001 255.255.255.000 192.001.005.001 255.255.255.000
An IP interface can be assigned a VC that corresponds to any ATM class of service.
ATM Connections Partitioned into Interfaces
145.123.215.001 255.255.000.000
Gold Silver Bronze
Figure 3-22. Enhanced Router and Example Configuration PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 3-72 Release 9.0.0 255-700-447

Voice Processing
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 signaling. 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).
Voice Gateway
Voice Gateway
Figure 3-23. End-to-End Continuity Check
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 currently not supported.
Release 9.0.0 3-73

System Performance
GSM Voice Traffic Compression

The primary objective of GSM Idle Channel (No Speech Frame) Suppression and GSM Idle Speech Frame Suppression is to minimize the number of GSM voice traffic circuits between the cell sites (BTS) and the BSC. Suppressing the idle traffic will allow for greater trunk utilization and greater operational expense savings to wireless carriers. These features are supported on the DSP2E (chips 5 and 6) and DSP2F modules using AlgoSet8. These GSM features will be used either in conjunction with the existing wireless backhaul features or on their own in a GSM-only configuration. Idle Channel (No Speech Frame) suppressionA DS0 can be divided into a 64 Kbps channel, 32 Kbps channels, 16 Kbps channels or 8 Kbps channels. When a channel is not allocated to a wireless call, No Speech Frames are generated on those channels. With the PSAX Idle Channel (No Speech Frame) suppression feature, the No Speech Frames will be detected and suppressed from transmission on the backhaul trunk. Idle Speech Frame suppressionIdle Speech Frames are generated during periods of silence on calls. With the PSAX Idle Speech Frame suppression feature, Idle Speech Frames will be detected and suppressed from transmission on the backhaul trunk. This will only be done for the 16 Kbps channels. The actual savings realized with this feature will depend on the network topology, the types of traffic on the network and the voice activity of the users.
System Performance
Optimized Bootup
To support requirements to reduce the downtime of PSAX modules when they are booted due to firmware upgrades that are provided with PSAX system software upgrades, the Optimized Bootup feature is implemented for the modules listed in the Hardware Dependency section for this feature. The service interruption time on PVC and SPVC connections is now less than 30 seconds after driver download for these modules. If the number of configured connections is more than the number stated, the bootup time might exceed 30 seconds. The Optimized Bootup feature is supported on the following modules, in the PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 systems: 23N74 45N74 3-Port DS3/E3 ATM 3-Port DS3/E3 ATM Protection 100 PVC and SPVC connections configured (E3 mode only) 100 PVC and SPVC connections configured (E3 mode only)
Release 9.0.0 255-700-447

System Performance
24N72 24N73 23N34
4-Port OC-3c/STM-1 Multimode 4-Port OC-3c/STM-1 Single-Mode
500 PVC and SPVC connections configured (STM-1 mode only) 500 PVC and SPVC connections configured (STM-1 mode only)
21-Port High-Density E1 IMA 50 PVC and SPVC connections configured
Synchronization of PSAX System Software on Redundant CPUn Modules

The Synchronize Standby CPU feature provides the user the ability to synchronize the standby CPUn module with the primary CPUn in a redundant PSAX system where the two CPUn modules are loaded with two different PSAX system software releases. In a situation where a user needs to insert a new or replacement CPUn module into the chassis, the primary CPUn module checks the system software release of the newly installed replacement module, which then becomes the standby module. When a new standby CPUn module is installed, two possible scenarios exist: The standby CPUn module is loaded with a PSAX system software release that is later than or the same as the software release on the primary CPUn module. In this scenario, even if the new standby CPUn module has a later release, the primary CPUn module still performs correctly as the primary module. This functioning has not changed from prior releases. To force the copying of the later software release from the new standby module to the primary module that has the older software release, the Primary Switchover command on the Remote Reboot Configuration window must be executed to make the primary CPUn module the standby CPUn module. Then the new Synchronize Standby CPU Software Version command can be executed on the primary CPUn module (with the later software release) to cause it to copy the later software release and configuration files to the former primary CPUn module (with the older software release). The standby CPUn module is loaded with a software release that is earlier than the software release on the primary CPUn module. Prior to Release 8.1.0 in this scenario, the databases were not copied from the primary CPUn module to the new standby CPUn module, thus effectively making the new standby CPUn module unable to function as a standby module. The Synchronize Standby CPU feature provides the new Synchronize Standby CPU Software Version command on the Software Version Configuration window. When the user executes this command, the primary CPUn copies the system software and configuration files to the new standby CPUn module, thus making it operational as a standby module.
Release 9.0.0 3-75

System Security
Maintenance Testing on DS1 Interfaces

The Maintenance Tests feature provides the capability to perform out-of-service 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, and facility 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 maintenance testing for troubleshooting sectionalized spans. Because in some cases customer CSU/DSU equipment might be located downstream at the customer premises from the PSAX system, maintenance testing also requires the ability of the PSAX modules port in the PSAX system to ignore any facility loop codes that are received and to simply pass them along. BERT synchronization 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 facility 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 convenient method for storing centralized user account administration data for multiple 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
Release 9.0.0 255-700-447

System 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-only Users 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 configurations, 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 CPUx 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.
Primary RADIUS Server
RADIUS servers store usernames, passwords, the secret (encryption key), and the PSAX system IP address for each PSAX system it supports.
Secondary RADIUS Server (for redundancy)
Authentication of usernames and passwords
Multiple PSAX Systems PSAX System PSAX System
Each PSAX system stores the primary and secondary RADIUS server secret, IP address, and other parameters.
Figure 3-24. PSAX System Access Authentication via RADIUS Servers
Release 9.0.0 3-77

PSAX Module Features
ATM Security on Interfaces and Connections

The ATM Security feature protects ATM traffic by encrypting the ATM control plane, providing integrity and confidentiality security services to signaling messages or routing packets. It also provides a mechanism for signaling that can provide strong cryptographic data integrity with replay/reordering protection. ATM control plane entities are able to verify the source and contents 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 confidentiality service for ATM UNI and ATM PNNI interfaces. For ATM PNNI, security agents are configured both at the PNNI node level and at the interface level for signaling and routing PVCs. The ATM Security feature is supported on all PSAX Multiservice Media Gateway systems and on PSAX I/O modules that support ATM UNI 3.0, 3.1, and 4.0 and ATM PNNI 1.0 interfaces The ATM Security feature is available only to users in certain countries. Contact your Lucent Technologies sales representative to find out whether your country is eligible to use the ATM Security feature.

For descriptions of the I/O and server modules available for use in the PacketStar PSAX Multiservice Media Gateways, see Appendix D.
Release 9.0.0 255-700-447
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 system 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 using this operating system... Windows 2000 Windows 98 or NT
do this... Select Start > Programs > Accessories > Communications > Hyperterminal Select Start > Programs > Accessories > Hyperterminal
Release 9.0.0 4-1
Chapter 4 Using VT100 Terminal Emulation

The Connection Description window is displayed (see Figure 4-1).
Figure 4-1. Connection Description Window
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).
Figure 4-2. Connect To Window
5 In the Connect using field, select COM1. 6 Click OK.
Release 9.0.0 255-700-447

The COM1 Properties window is displayed (see Figure 4-3).
Figure 4-3. COM1 Properties Window
7 Enter the appropriate values for the fields on this window according to the information provided in Table 4-2.
Table 4-2. Windows HyperTerminal Settings Option Setting
Bits per second: Data bits: Parity: Stop bits: Flow control: 8 Click OK.
9600 baud 8 None 1 None
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.
Release 9.0.0 4-3

Connecting a Dialup Modem to the Chassis
Figure 4-4. PSAX 2300 Multiservice Media Gateway System Logon Window
End

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.
@@IG@@ Connecting a Dialup Modem to the system
Begin
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:

DTR on, DCD on, CTS on, 8-bit character length, 9600 baud, no parity, 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 CONSOLE connector on the CPUn module. 2 At the remote site: a Verify that the remote workstation and dialup facilities are functioning 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
Release 9.0.0 4-5

Release 9.0.0 255-700-447
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 34 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 Multiservice 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 Multiservice 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 sessions 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 authenticating 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)
Release 9.0.0 5-1
Chapter 5 Site-Specific Configuration

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 information 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
Release 9.0.0 255-700-447

Table 5-1. Field Descriptions for the PSAX System Logon Window Field Name Field Values Description
Username
Default: N/A Range: N/A Format: Alphanumeric
Specifies the user name for logging onto the PSAX system, which provides three levels of access to the system. 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 authenticate logon, you must enter root, readwrite, or readonly (not case sensitive) as the user name. RADIUS-defined user names. If you are authenticating 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. 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 window. Access and modify the all five SNMP authentication options on the SNMP Agent System-Wide Configuration window. You must be connected to the PSAX system via the CONSOLE port on the CPUn module.
root
Release 9.0.0 5-3

Table 5-1. Field Descriptions for the PSAX System Logon Window (Continued) Field Name Field Values Description
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 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 window Modify the password for the user name readonly on the User Options window 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 considerations: 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 namesroot, readwrite, and readonlyduring 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 sensitive) stored in the PSAX system database.
readonly
Password
Default: Not displayed Range: N/A Format: ASCII Characters 32 - 126
Release 9.0.0 255-700-447

Console Interface Main Menu Options
Figure 5-2. Console Interface Main Menu Window
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 Options

The Console Interface Main Menu window includes the following options as described in Table 5-2.
Table 5-2. Console Interface Main Menu Options and Commands For information on using this option... see...
Site-Specific Configuration Equipment Configuration Connection Configuration Software Version Configuration Trap Log Display
Configuring the System for Your Site on page 5-19. Using the Equipment Configuration Window on page 5-71. PacketStar PSAX System Connections Provisioning Guide. Chapter 7, Upgrading System Software and Firmware. PacketStar PSAX Simple Network Management Protocol (SNMP) Trap Reference Guide.
Release 9.0.0 5-5

Setting Up RADIUS Server Access Authentication for the PSAX System
Table 5-2. Console Interface Main Menu Options and Commands (Continued) For information on using this option... see...
User Options
Setting Up RADIUS Server Access Authentication for the PSAX System on page 5-6 and Changing the System Password and Other User Options on page 5-11. Chapter 5, Using System Diagnostics. Chapter 8, Backing Up and Restoring Database Configuration Files. Saving the Equipment Configuration Values and Logging Off on page 5-84. Saving the Equipment Configuration Values and Logging Off on page 5-84.
Diagnostics Remote Database Operation Save Configuration Leave Console Interface

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 authentication. 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 Technologies PacketStar PSAX product line.

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 (readwrite), 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 characters. 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 their access permissions are as follows: rootThis username provides super user access including read/write and administrative permissions. readwriteThis username provides read/write permission. readonlyThis 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 on this 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 Configuration command to store the values in the PSAX system database.
End
Release 9.0.0 5-7

Figure 5-3. User Options WindowLogged on as Username Root
Figure 5-4. User Options WindowAuthentication Mode Hybrid Selected Table 5-3. Commands for the User Options Window Command Function
Apply User Configuration
Applies the configuration field values you entered.
Release 9.0.0 255-700-447

Table 5-3. Commands for the User Options Window (Continued) Command Function
Reset to System Defaults Go Back to Main Menu
Resets the values in the fields to the system default values. Redisplays the Console Interface Main Menu window.
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 LOCAL_ONLY
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. Indicates that the PSAX system will not obtain authentication of the username and password from the RADIUS server. Indicates that the PSAX system will obtain authentication 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. Indicates that the PSAX system will obtain authentication 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 system-defined usernames: root, readwrite, or readonly. 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. Specifies the port numbers for the primary and the secondary RADIUS servers. Normally, you should use the default value 1812; however, you can change this port number if needed Note: This field is displayed only if you selected the value RADIUS_ONLY or HYBRID in the Authentication Mode field.
RADIUS_ONLY
HYBRID
Server IP Address
Default: 000.000.000.00 0 Range: N/A Format: Numeric (valid dotted quad
Server Port Number Default: 1812 Range: N/A Format: Numeric (4 digits)
Release 9.0.0 5-9

Table 5-4. Field Descriptions for the User Options Window (RADIUS Server Fields) (Continued) Field Names Field Values Description
Server Max Retry
Default: 0 Range: 09 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 want redundant 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. Note: This field is displayed only if you selected the value RADIUS_ONLY or HYBRID in the Authentication Mode field. Specifies the length of time in seconds between authentication attempts by the RADIUS server. 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. Specifies the secret (encryption key) that the primary RADIUS server uses to encrypt the users password. When you enter a case-sensitive text string in this field, it is not displayed on the window. 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 passwords of the users who will access the PSAX system. When the user logs onto the PSAX system, it then sends the username and encrypted password to the RADIUS server for authentication. Note: This field is displayed only if you selected the value RADIUS_ONLY or HYBRID in the Authentication Mode field. Specifies the secret (encryption key) that the secondary RADIUS server uses to encrypt the users password. Enter a case-sensitive text string for the secondary server if you want redundant authentication capabilities. This secret must also be set up on 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. Note: This field is displayed only if you selected the value RADIUS_ONLY or HYBRID in the Authentication Mode field.
Server Max Timeout
Default: 10 Range: 099 Format: Numeric (seconds)
Primary RADIUS Server Secret
Default: None Range: 430 Format: Alphanumeric (case sensitive)
Secondary RADIUS Default: None Server Secret Range: 430 Format: Alphanumeric (case sensitive)
Release 9.0.0 255-700-447

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, configuring 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 PSAXdefined usernames, which cannot be changed, and their access permissions are as follows (details of permissions are provided in Table 5-5): rootThis username provides super user access including read/write and administrative permissions. readwriteThis username provides read/write permission. readonlyThis username provides read-only permission. ! CAUTION: If you are using the console session for the first time on this PSAX system, you are urged to change the initial, default passwords for the three usernames, 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. However, 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
1 On the Console Interface Main Menu window, select the User Options command. The User Options window is displayed. Depending on which username you 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. Figure 5-4 shows the window that is displayed if you logged on with username readwrite. Figure 5-7 shows the window that is displayed if you logged on with username readonly.

The three levels of permissions for changing user options on this window are described in Table 5-5.
Table 5-5. Permissions for PSAX-defined Usernames If you logged on you can change the following fields on the User Options with username... window:
root
Alternate Navigation Keys, Bell, Trap Display, Timeout Length, and the Passwords for root, readwrite, and readonly. 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 System for information and procedures on configuring parameters for the RADIUS servers. Alternate Navigation Keys, Bell, Trap Display, Timeout Length, and the Password for readwrite fields. Alternate Navigation Keys, Bell, Trap Display, Timeout Length, and the Password for readonly fields.
readwrite readonly
2 To change the password for the username, select the Change Password For username field, where username is one of the PSAX-defined usernames 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. 3 To permanently save these values, press Ctrl+G to return to the Console Interface Main Menu window. 4 On the Console Interface Main Menu window, select the Save Configuration 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
Release 9.0.0 255-700-447

Figure 5-5. User Options WindowLogged on as Username Root
Figure 5-6. User Options WindowLogged on as Username Readwrite
Release 9.0.0 5-13

Figure 5-7. User Options WindowLogged on as Username Readonly Table 5-6. Commands for the User Options Window Command Function
Apply User Configuration Reset to System Defaults Go Back to Main Menu
Applies the configuration field values you entered. Resets the values in the fields to the system default values. Redisplays the Console Interface Main Menu window.
Table 5-7. Field Descriptions for the User Options Window (Password and Miscellaneous User Options Fields) Field Names Field Values Miscellaneous User Options Panel Description
Alternate Navigation Keys Up, Down, Left, Right
Default: Up: K, Down: J, Left: H, Right: L Range: N/A Format: Predefined alphabetic Default: Enabled Range: N/A Format: Predefined alphanumeric Enabled Disabled
Specifies alternate navigation keys for cursor movement. If you want to use keyboard shortcuts 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. Specifies whether the system audio warning bell is enabled or disabled. If the warning bell is enabled, it sounds ten seconds before the timeout period expires. Enables the warning bell. Disables the warning bell.
Bell
Release 9.0.0 255-700-447

Table 5-7. Field Descriptions for the User Options Window (Password and Miscellaneous User Options Fields) (Continued) Field Names Field Values Description
Trap Display
Default: Enabled Range: N/A Format: Predefined alphanumeric
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 the trap 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. Enables the display of trap messages after you execute a command or the PSAX system performs a function. Disables the display of trap messages after you execute a command or the PSAX system performs a function. Specifies the period of time that the session will remain active after the last detected keystroke. Ten seconds before the session is automatically terminated 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 tensecond period, the system will log off whether you have saved your configuration or not. Note: Lucent recommends that you select a relatively 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. Indicates that the session will remain active for 1 minute after the last detected keystroke. Indicates that the session will remain active for 5 minutes after the last detected keystroke. Indicates that the session will remain active for 10 minutes after the last detected keystroke. Indicates that the session will remain active for 15 minutes after the last detected keystroke. Indicates that the session will remain active for 20 minutes after the last detected keystroke. Indicates that the session will remain active for 30 minutes after the last detected keystroke. Indicates that the session will remain active for 45 minutes after the last detected keystroke. Indicates that the session will remain active for 1 hour after the last detected keystroke. Indicates that the session will remain active until you log off the PSAX system.
Enabled
Disabled
Timeout Length
Default: 10 minutes Range: N/A Format: Predefined alphanumeric
1 minute 5 minutes 10 minutes 15 minutes 20 minutes 30 minutes 45 minutes 1 hour Disabled
Release 9.0.0 5-15

Table 5-7. Field Descriptions for the User Options Window (Password and Miscellaneous User Options Fields) (Continued) Field Names Field Values Description
Change Password Panel Note: It is very important that you change the default passwords for the usernames during your first logon session on the User Options window. The rules for the password character string are as follows: 823 characters in length Case sensitive Any ASCII character 32126 (see Table 5-8). Change Password For root Default: lucenttech0 (last character is a zero) Range: 823 characters Format: ASCII Characters 32126 Specifies a new password that you choose for the username root. The new password you type is not displayed on the window. When you select this field, the system displays the message, Enter your password and press Return (Enter), in the status line area at the bottom of the window. After you press Enter, type a new password, and type it again when prompted. Press Enter again to apply the new password. Note: This field is displayed only if you logged on with username root. Specifies a new password that you choose for the username readwrite. The new password you type is not displayed on the window. When you select this field, the system displays the message,
Enter your password and press Return
Change Password For readwrite
Default: lucenttech1 Range: 823 characters Format: ASCII Characters 32126
(Enter), in the status line area at the bottom of the window. After you press Enter, type a new password, and type it again when prompted. Press Enter again to apply the new password. Note: This field is displayed only if you logged on with username root or readwrite. If you logged on with either of these usernames, you can change the password for username readwrite. Change Password For readonly Default: lucenttech2 Range: 823 characters Format: ASCII Characters 32126 Specifies a new password that you choose for the username readonly. The new password you type is not displayed on the window. When you select this field, the system displays the message, Enter your password and press Return (Enter), in the status line area at the bottom of the window. After you press Enter, type a new password, and type it again when prompted. Press Enter again to apply the new password. Note: This field is displayed only if you logged on with username root or readonly. If you logged on with either of these usernames, you can change the password for username readonly.
Release 9.0.0 255-700-447

Table 5-8. ASCII Characters Permitted for Use in Passwords Dec Char Description Dec Char Description
32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 ! " # $ % & ( ) * + , . / 0 1 2 3 4 5 6 7 8 9 : ; < = > ? @ A B C D
space
80 81 82 83 84 85 86 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116
P Q R S T U V W X Y Z [ \ ] ^ _ a b c d e f g h i j k l m n o p q r s t
Uppercase P Uppercase Q Uppercase R Uppercase S Uppercase T Uppercase U Uppercase V Uppercase W Uppercase X Uppercase Y Uppercase Z Opening square bracket Reverse slant (Backslash) Closing square bracket Caret (Circumflex) Underscore Opening single quote Lowercase a Lowercase b Lowercase c Lowercase d Lowercase e Lowercase f Lowercase g Lowercase h Lowercase i Lowercase j Lowercase k Lowercase l Lowercase m Lowercase n Lowercase o Lowercase p Lowercase q Lowercase r Lowercase s Lowercase t
Exclamation mark Quotation mark Cross hatch (number sign) Dollar sign Percent sign Ampersand Opening parentheses Closing parentheses Asterisk (star, multiply) Plus Comma Hyphen, dash, minus Period Slant (forward slash, divide) Zero One Two Three Four Five Six Seven Eight Nine Colon Semicolon Less than sign Equals sign Greater than sign Question mark At-sign Uppercase A Uppercase B Uppercase C Uppercase D
Closing single quote (apostrophe) 87
Release 9.0.0 5-17

Table 5-8. ASCII Characters Permitted for Use in Passwords (Continued) Dec Char Description Dec Char Description
69 70 71 72 73 74 75 76 77 78 79
*
E F G H I J K L M N O
Uppercase E Uppercase F Uppercase G Uppercase H Uppercase I Uppercase J Uppercase K Uppercase L Uppercase M Uppercase N Uppercase O
117 118 119 120 121 122 123 124 125 126
u v w x y z { | } ~
Lowercase u Lowercase v Lowercase w Lowercase x Lowercase y Lowercase z Opening curly brace Vertical line Closing curly brace Tilde (approximate)
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 authentication or privacy passwords.
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
1 On the Console Interface Main Menu window, select the User Options 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 on this 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 Configuration command to store the values in the PSAX system database.
End
Release 9.0.0 255-700-447

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 procedure.
Begin
On the Console Interface Main Menu window, select the Site-Specific Configuration command. The Site-Specific Menu window is displayed (see Figure 5-8).
Figure 5-8. Site-Specific Menu Window (No System Options Configured)

End
Release 9.0.0 5-19

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 configuration. 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. Accesses the In-Band Management IP Configuration window on which you configure IP over ATM to manage remotely distributed PSAX systems from a central site over the data network using the current management tools. 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. Accesses the Call Control Resource Allocation Configuration 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 different from the Transport Protocol Accesses the GR-303 System-Wide Configuration window on 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. Note: To use this feature, you must first enable it by using the Feature Turn ON/OFF option on this menu. 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 narrowband and broadband routing tables.
In-band Management IP Configuration
PNNI System-Wide Configuration
Call Control Resource Allocation Configuration
[GR303 System-Wide Configuration]
TAS Module System-Wide Con- Accesses the TAS Module System-Wide Configuration figuration window on which you perform actions on announcement files on the Tones and Announcements Server module such as compression, playing, FTP, and line tests.
Release 9.0.0 255-700-447

Table 5-9. Descriptions for Site-Specific Menu Options (Continued) Menu Option Description
[H.248 Management and Configuration]
Accesses the H.248 Management and Configuration window on which you configure the media gateway controller on a CES-to-ATM AAL1 SVC. This window provides access to MGC-to-MG communications control, congestion 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. Note: To use this feature, you must first enable it by using the Feature Turn ON/OFF option on this menu.
DSP Resource Configuration
Accesses the DSP Resource Table window on which you can allocate DSP resources manually, or assign the firmware 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 sitespecific (system level) before configuring at the DSP2x module-channel level.
[IUA Layer Configuration]
Accesses the ISDN Q.921 User Adaptation Layer Configuration windows. Note: To use this feature, you must first enable it by using the Feature Turn ON/OFF option on this menu. Note: H.248 with PRI ISDN Network Offload Applications: 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 available on this menu. Accesses the Interface Protection Feature Configuration window on which you configure the switchover of a group of interfaces from a primary to a standby connection if a failure is detected on the primary. Accesses the IP Throttling Configuration window on which you enable and disable and set parameters for this feature.
Interface Protection Feature
IP Throttling Configuration
Release 9.0.0 5-21

Table 5-9. Descriptions for Site-Specific Menu Options (Continued) Menu Option Description
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. 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. Accesses the SNMP Agent System-Wide Configuration window on which you Accesses the ATM Security Agents Table window on which you 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. Note: To use this feature, you must first enable it by using the Feature Turn ON/OFF option on this menu.
N to M Protection Feature
SNMP Agent ATM Security Agents Bulk Statistics Configuration
Go Back to Main Menu
Redisplays the Console Interface Main Menu window.
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 Identification panel and System Date, Time and Temperature panel.
Entering Your System Master ATM Address
Begin
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 Master ATM 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
Release 9.0.0 255-700-447

Figure 5-9. Site-Specific Configuration Window Table 5-10. Commands for the Site-Specific Configuration Window Command Function
Configure TCP Server Apply Site-Specific Configuration Reset Site-Specific Display Go Back to Site-Specific Menu
Displays the TCP Server Configuration window. Applies the values you entered on this window. Sets the values in this window to the last saved (applied) set of values. Redisplays the Site-Specific Menu window.
Table 5-11. Field Descriptions for the Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window Field Name Field Values Description
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.
Release 9.0.0 5-23

Table 5-11. Field Descriptions for the Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window (Continued) Field Name Field Values Description
Address Type
Default: Nsap Range: N/A Format: Predefined Nsap E164 E164nsap
Specifies the type of address used for the master node ATM address. Indicates that the master node address is a network service access point-type address. Indicates that the master node address Indicates that the master node address 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 information about OAM loopback tests, see Chapter 5, Using System Diagnostics.
Loopback Location ID
Default: FFFF.FFFF. FFFF.FFFF.FFFF. FFFF.FFFF.FFFF Range: N/A Format: Hexadecimal
Debouncing Period Default: 3000 Specifies the maximum length of time that must (msecs) Range: 1000300000 elapse before the PSAX system will clear OAM AIS and RDI alarms. Format: Numeric (msec)
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 window: 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 system. 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 module is corrupted, the system cannot access the Ethernet.
Release 9.0.0 255-700-447

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 IP addresses. 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 cannot be on the same subnet as the in-band IP address.
Configuring System Identification

ATM Addresses and OAM 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
Release 9.0.0 5-25

Table 5-12. Field Descriptions for the Master ATM Address and OAM Related Data Panel on the Site-Specific Configuration Window Field Name Field Values Description
Master Node Addr
Default: 0000.0000. 0000.0000.0000. 0000.0000.0000. 0000.0000 Range: N/A Format: Hexadecimal Default: Nsap Range: N/A Format: Predefined Nsap E164 E164nsap
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.
Address Type
Specifies the type of address used for the master node ATM address. Indicates that the master node address is a network service access point-type address. Indicates that the master node address Indicates that the master node address 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 information about OAM loopback tests, see Chapter 5, Using System Diagnostics.
Loopback Location ID
Default: FFFF.FFFF. FFFF.FFFF.FFFF. FFFF.FFFF.FFFF Range: N/A Format: Hexadecimal
Debouncing Period Default: 3000 Specifies the maximum length of time that must (msecs) Range: 1000300000 elapse before the PSAX system will clear OAM AIS and RDI alarms. Format: Numeric (msec)
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
Release 9.0.0 255-700-447

Table 5-13. Field Descriptions for the System Identification Panel on the Site-Specific Configuration Window Field Name Field Values Description
[Chassis Type]
Default: N/A Range: N/A Format: predefined alphanumeric Default: Client Range: N/A Format: predefined alphanumeric
Displays the type of PSAX system you are configuring.
Mux Tcp Type
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. Indicates that the PSAX system is serving as the client device. Indicates that the PSAX system is serving as the server device. 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: alphanumeric, - (hyphen), and _ (underscore). Do not use spaces or periods. 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. 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. 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 IP addresses. Specifies the IP address of the active CPU module for the PSAX system. Determine from your network configuration plan the IP address you want to use. Note: Do not leave this field value as 0.
Client Server Site Name Default: N/A Range: 119 Format: predefined alphanumeric Default: 000.000.000.0 00 Range: N/A Format: valid dotted quad Default: 000.000.000.0 00 Range: N/A Format: valid dotted quad Default: 000.000.000.0 00 Range: N/A Format: valid dotted quad Default: 000.000.000.0 00 Range: N/A Format: valid dotted quad
Switch IP Addr
IP Mask (display only)
Gateway Addr
CPU IP Addr
Release 9.0.0 5-27

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-Specific Configuration Window Field Name Field Values Description
Mon/Day/Yr
Default: todays date Range: N/A Format: numeric (mm/dd/yyyy) Default: current time Range: N/A Format: numeric (24-hour format [HH:MM:SS])
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). Specifies the current time for your location in Universal Time Coordinated (UTC) format (24-hour format) (also known as Greenwich Mean Time [GMT]).
Hour:Min:Sec UTC
Release 9.0.0 255-700-447

Table 5-14. Field Descriptions for the System Date and Time Panel on the Site-Specific Configuration Window (Continued) Field Name Field Values Description
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 a value (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. Displays the local time of the PSAX system in 12-hour format with the am or pm indicator. Note:
[Local Time]
Default: current time Range: N/A Format: numeric (12-hour format [HH:MM:SS] am or pm) Default: N/A Range: N/A Format: numeric (degrees Celsius)
[Temperature]
Displays the ambient temperature where the PSAX system is located.
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 interworking 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 following 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.
Release 9.0.0 5-29

4 To return to the Site-Specific Configuration window, select the Go Back to Site-Specific Screen command.
End
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)
The commands on this window have the following functions:
Release 9.0.0 255-700-447

Table 5-15. Commands for the TCP Server Configuration Window Command Function
Apply TCP Server Configuration Reset TCP Server Display Go Back to Site-Specific Screen
Applies the configuration. Resets the display. Redisplays the Site-Specific Configuration window.
Table 5-16. Field Descriptions for the TCP Server Configuration Window Field Name Field Values Description
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. Indicates that the PSAX system is serving as the client device. Indicates that the PSAX system is serving as the server device. 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 Configuration window. Specifies the IP address of the Ethernet or inband interface over which the CGAPI will send data. Note: This field is displayed only if you designated the PSAX system as a client in the Mux Tcp Type field on the Site-Specific Configuration window. Specifies the TCP server port number. This number must be a valid number based on the agreement between the connection gateway and the call controller.
Client Server Server IP Address Default: 0000.0000.0 000.0000 Range: N/A Format: valid dotted quad Default: 0000.0000.0 000.0000 Range: N/A Format: valid dotted quad
CGAPI
TCP Port Number
Default: 1025 Range: 102565535 (excluding 5000, 5009, and 6000) Format: numeric
Release 9.0.0 5-31

Configuring Call Control Resource Allocation
Table 5-16. Field Descriptions for the TCP Server Configuration Window Field Name Field Values Description
Keep Alive Timer (secs)
Default: 0 Range: 1100 Format: numeric (seconds) Default: 0 Range: 1100 Format: numeric (seconds) Default: 0.0.0.0 Range: N/A Format: valid dotted quad
Specifies the interval of time that elapses before the TCP server sends a query message to determine whether the connection is still active. Specifies the amount of time that the server is inactive before the TCP/IP session is automatically terminated. 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.
In Active Timer (secs)
Client IP Address

Setting the Configuration Values
Perform the following procedure to configure the call control resource allocation on the PSAX system.
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed (see Figure 5-12). 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 provided 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.
Release 9.0.0 255-700-447

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


Table 5-17. Commands for the Call Control Resource Allocation Configuration Window Command Function
Apply Configuration Go Back to Site-Specific Menu
Applies the values you entered on this window. Redisplays the Site-Specific Menu window.
Configuration Guidelines
Table 5-18. Field Descriptions for the Call Control Resource Allocation Configuration Window Field Name Field Values Description
Important: The ranges of values for numeric fields are software imposed. When changing the values 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 calculated 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 command 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 displayed: Resource allocation configuration has been applied. Need to save configuration and reboot the system to take effect.
svcPtToPtCalls
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 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 window is set to 8000, then the recommended values for this field are 4000 for AAL1 and 4100 for AAL2. Specifies the maximum number of SVC point-to-multipoint calls to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of parties on SVC 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. H.248 Applications: Set the value in this field to 0.
svcPtToMultiPtCalls Default: 002000 Range: 04000 Format: Numeric svcPtToMultiPtPar- Default: 002000 ties Range: 04000 Format: Numeric
Release 9.0.0 255-700-447

Table 5-18. Field Descriptions for the Call Control Resource Allocation Configuration Window (Continued) Field Name Field Values Description
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: 010000 Format: Numeric Specifies the maximum number of SPVC circuit 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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0. 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-topoint 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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0.
spvcTePtToPtCalls
Release 9.0.0 5-35

spvcAtmPtToPtCalls Default: 002000 Range: 010000 Format: Numeric
Specifies the maximum number of SPVC ATM pointto-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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of SPVC frame relay 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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of SPVC point-to-multipoint calls to be supported by the PSAX system. SPVC Priority Configurations: If you select the value Enabled in the spvcGlobalPriorityScheme 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. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of parties on SPVC point-to-multipoint calls to be supported by the PSAX system. SPVC Priority Configurations: If you select the value Enabled in the spvcGlobalPriorityScheme 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. H.248 Applications: Set the value in this field to 0.
spvcFrPtToPtCalls
spvcPtToMultiPtCalls
spvcPtToMultiPtParties
Release 9.0.0 255-700-447

aal2CirAtmSpvcVcc Default: 001000 Calls Range: 04000 Format: Numeric aal2VbrAtmSpvcVc Default: 000100 cCalls Range: 04000 Format: Numeric sgApiCirEmEndPts Default: 001000 Range: 0-15000 Format: Numeric Default: 000000 Range: 0-15000 Format: Numeric Default: 000000 Range: 0-15000 Format: Numeric
Specifies the maximum number of circuit emulationto-ATM standard AAL2 SPVC calls to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of VBR-to-ATM standard AAL2 SPVC calls to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of circuit emulation endpoints for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of ATM SVC endpoints for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of SVC point-to-point 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 protocol 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 Number of Terminations field on that window is set to 8000, then recommended values for this field are 4000 for AAL1 and 4100 for AAL2 Specifies the maximum number of SVC point-to-multipoint calls for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of parties on SVC point-to-multipoint calls for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0.
sgApiAtmSvcEndPts
sgApiPtToPtSvcCalls
sgApiPtToMultiPtS- Default: 000000 vcCalls Range: 0-4000 Format: Numeric sgApiPtToMultiPtParties Default: 000000 Range: 0-4000 Format: Numeric
Release 9.0.0 5-37

atmTrunkVccs
Specifies the maximum number of VCCs supported by ATM trunking. SPVC Priority Configurations: If you select the value Enabled in the spvcGlobalPriorityScheme 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. 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 window 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. Specifies the maximum number of switched narrowband calls supported by ATM trunking. H.248 Applications: Specifies the maximum number of simultaneous calls through AAL2. 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 window is set to 8000, then recommended values for this field are 0 for AAL1 and 4000 for AAL2 Specifies the maximum number of Enhanced Routerto-ATM SPVC calls supported on this PSAX system. Displays the percentage of memory allocated to call control. A portion of the total system memory is allocated 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.
atmTrunkNarrowBandCalls
spvcErmPointToPointCalls
[callContrlResAllo- Default: 0098 cUsage %] Range: 0100 Format: Numeric
Release 9.0.0 255-700-447

cgSvcCutThroughOption
Default: cgSvcAcImplicitCutThrough Range: N/A Format: Predefined alphanumeric
Specifies whether the PSAX system or the connection gateway device (connection manager) sends a cutthrough message to initiate an SVC connection. Note: The value in this field is relevant only if you have enabled a media gateway control feature (the Connection Gateway API feature or the H.248 protocol feature). Indicates that the PSAX system sends a cut-through message to the connection gateway device to initiate an SVC connection. Indicates that the connection gateway device determines when to send a cut-through message to the connection manager to initiate an SVC connection. H.248 Applications: You must use the value cgSvcAcExplicitCutThrough if you are using the H.248 protocol feature. Specifies whether the PSAX systemwide priority scheme must be supported for all SPVCs and SPVC trunks. Indicates that the priority scheme is not in force (disabled). 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 schemeenabled trunks in an IMA link, the limit is 32 SPVCs.
cgSvcAcImplicitCutThrough cgSvcAcExplicitCutThrough
spvcGlobalPriority- Default: Disabled Scheme Range: N/A Format: Predefined alphanumeric Disabled Enabled
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.
Table 5-19. PSAX System Performance Capabilities Per Node for Release 9.0.0 Connection Type Maximum Number of Duplex Calls per Node Call Set-up Rate for CPU2 and CPU3L Modules* Call Set-up Rate for CPU3 and CPU4 Modules*
PVC SPVC SVC All connections combined

*
60,000 10,000 15,000 60,000

N/A
N/A
60 calls per second 100 calls per second 60 calls per second 100 calls per second
A CPU3 or CPU4 module paired in the same chassis with a CPU2 or CPU3L module will operate at the lower CPU2/CPU3L module call rate. Release 9.0.0 5-39

When using both SPVC and SVC connection types, you can set up any combination of calls as long as you do not exceed 100% of the call control resource memory allocation (callContrlResAllocUsage field on the Call Control Resource Allocation 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 of calls 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.
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 Configuration 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
Release 9.0.0 255-700-447

Figure 5-14. Diagnostics Menu
Figure 5-15. Remote Reboot Configuration Window
Release 9.0.0 5-41

Configuring GR-303
Backing Up Configuration Data

You can back up the data on the Call Control Resource Allocation window by backing up the file ssid.def, which resides on the CPU module system disk. We highly recommend that you back up the ssid.def file, which contains your configuration data. See Chapter 12 for procedures on backing up your system software data.
Configuring GR-303
See the application note entitled PacketStar PSAX Configuring the GR-303 Voice Gateway User Guide, Issue 3 for instructions on configuring this feature.
Configuring TAS Module System-Wide Use

See the PacketStar PSAX Tones and Announcements Module User Guide for instructions on configuring system-wide use of the TAS module.
Configuring H.248 Media Gateway Control Protocol

See the PacketStar PSAX H.248 Media Gateway Control User Guide for instructions and guidance on configuration of the H.248 protocol feature.
Configuring DSP Resource Use

See the PacketStar PSAX DSP2x Voice Server Modules User Guide for instructions and guidance on DSP resource configuration.
Enabling and Disabling PSAX System Features

Perform the following procedure to turn on the desired feature from the Feature 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.
Turning On the H.248 Gateway Control Protocol Feature
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed (see Figure 5-16). 2 Select the Feature Turn ON/OFF option. The Feature Turn ON/OFF Table window is displayed (see Figure 5-17). The commands on this window are described in Table 5-20. The fields on this window are described in Table 5-21.
Release 9.0.0 255-700-447

3 Select the desired interface feature in the Feature Id column and press Enter. 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. The following message is displayed in the status line:
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 modification. [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 5-16. Site-Specific Menu Window (Feature Turn On/Off Option Selected)
Release 9.0.0 5-43

Figure 5-17. Feature Turn On/Off Window

Table 5-20. Commands for the Feature Turn ON/OFF Table Window Command Function
Page Up Page Down Top Bottom Find . . . . . Feature ID: Go Back to Site-Specific Menu
Scrolls up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. This command is currently not supported. Redisplays the Site-Specific Menu window.
Release 9.0.0 255-700-447

Table 5-21. Field Descriptions for the Feature Turn On/Off Table Field Name Field Values Description
Total: 0/0
Default: N/A Range: 16 Format: Numeric
First number: Indicates which Feature ID is currently 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 features 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 Pnni Gr303 Displays the PSAX system features that you can enable or disable.
Private network-to-network interface feature. Note: Currently, this feature cannot be disabled. ITU-T GR-303 local loop emulation services feature. 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. Virtual Internet Protocol Router feature. Note: This feature is not currently supported. Select this value to enable the H.248 protocol feature. European V.5 local loop emulation services feature. ISDN Q.921 User Adaptation Layer Protocol feature. Enables OSI Layer 2 ISDN D-channel signalling between an Media Gateway Controller (for example, a Softswitch) and a Media Gateway (for example, a PSAX system) in PRI offload applications. ATMsecurity feature. Bulk statistics feature. Displays the amount of system memory in bytes allocated to the feature.
Vipr H248 V5 Iua
AtmSec BulkStats space memory Default: PNNI: 67108864 Gr303: 134217728 Vipr: 67108864 H248: 134217728 V5: 134217728 Iua: 67108864 Range: N/A Format: Numeric (bytes)
Release 9.0.0 5-45

Rebooting CPUn Modules in Redundant and Nonredundant Systems
Table 5-21. Field Descriptions for the Feature Turn On/Off Table (Continued) Field Name Field Values Description
desired status
Default: Enable or Disable (depends on the feature) Range: N/A Format: Predefined alphanumeric Disable
Displays whether the feature is to be made operational or not. Note: On the Site-Specific Menu window, the feature options that are displayed between brackets [ ] are disabled. 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. 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 displayed in the current status field. Displays the current operational status of the feature.
Enable
current status
Default: N/A Range: N/A Format: Predefined alphanumeric Disabled Enabled
Indicates that the selected feature is currently not operational. Indicates that the selected feature is currently operational.

The following procedures are used to reboot the CPUn modules in a redundant or nonredundant PSAX system configuration.
Saving Configurations
Perform the following procedure to save the PSAX system configurations.
Begin
1 On the Console Interface Main Menu window, save the values you have entered during this session by selecting the Save Configuration (Modified) option.
Release 9.0.0 255-700-447

Figure 5-18. Console Interface Main Menu Window (Save Configuration Option Selected)
The following message is displayed in the status line:

T-SaveConfiguration: saveConfigurationReasonCode=All-OK
In a PSAX system with redundant CPUn modules, this command causes the backup (standby) CPUn module to reboot. This event allows the backup CPUn module to synchronize the MIB data with the primary CPUn module. Before proceeding with the following procedure, wait for the backup CPUn module to finish rebooting. The yellow LED LOAD stops flashing. See the next procedure to reboot the PSAX system.
End
Rebooting the Redundant PSAX System

To implement the change in the feature status, you need to reboot the PSAX system. Choose one of the following procedures for rebooting your PSAX system, depending on whether it has redundant CPUn modules or a single CPUn module: Rebooting the Redundant PSAX System Rebooting the Nonredundant PSAX System ! WARNING: Rebooting the PSAX system with a single (nonredundant) CPUn module will interrupt all traffic running through the PSAX chassis. ! CAUTION: Be sure you have saved your modified configuration on the Console Interface Main Menu window before beginning either of the following reboot procedures.

Begin
Note:
Performing this procedure does NOT interrupt 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 Components option. The Remote Reboot Configuration window (see Figure 5-19) is displayed.
Figure 5-19. Remote Reboot Configuration Window (Primary Switchover Option Selected)
3 Select the Primary Switchover command. The following message is displayed in the status line:
Are you sure that you want to do the primary switchover? (y/n)
4 Press the Y key. The PSAX system switches processing control from the primary CPUn module to the backup (standby) CPUn module, and immediately begins rebooting the original primary CPUn module. As this process proceeds, the new primary CPUn module (originally the standby CPUn) synchronizes the management information base (MIB) data with the new standby CPUn module (originally the primary CPUn). The green LED ACTIVE is illuminated on the primary CPUn module.
End
Release 9.0.0 255-700-447

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 module will 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 Components option. The Remote Reboot Configuration window (see Figure 5-20) is displayed. 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. The following message is displayed in the status line:
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 autoboot process is complete, the ACTIVE LED is illuminated and traffic on the connections resumes.
End
Release 9.0.0 5-49

Configuring ISDN Q.921 User Adaptation (IUA) Layer Protocol
Figure 5-20. Remote Reboot Configuration Window (Reboot Primary CPU Option Selected)

Perform the following procedure to configure the IUA layer.
Begin
1 From the Site-Specific Menu window, select the IUA Layer Configuration option. The IUA Layer Configuration Window is displayed (see Figure 5-21). Table 5-22 describes the commands on this window. Table 5-23 describes the fields on this window. 2 Select the field values you need to modify from the information provided in Table 5-23 as described in the sample procedures for setup and tear down messages sent between the MGC and the PSAX system. 3 Save your configuration by using Saving the Equipment Configuration Values and Logging Off on page 5-84. Your PRI ISDN and IUA configuration is now ready to pass D-channel signal traffic, with SCTP as the default transport layer. You may view statistics for the TDM-interface module by consulting the port and channel configuration chapter in your TDM-interface module user guide for instructions on accessing statistics windows.
End
Release 9.0.0 255-700-447

Figure 5-21. Sample IUA Layer Configuration for the OMG and TMG Sides Table 5-22. Commands for the IUA Layer Configuration Window Command Function
Apply IUA Configuration Go To AS Table Go To ASP Table Go Back to Site-Specific Menu
Applies the user-assigned IUA configuration values. Displays the IUA AS Table window. Displays the IUA ASP Table window. Displays the Site-Specific Menu window.
Table 5-23. Field Descriptions for the IUA Layer Configuration Window Field Name Field Values Field Description
[Version]
Default: 1 Range: Format: Numeric Default: 3000 Range: Format: Numeric (msec) Default: Off Range: N/A Format: Predefined alphanumeric On Off
Identifies the current version of the ISDN Q.921 User Adaptation Layer (IUA) protocol. Specifies the initial value of the recovery timer. The recommended value is 3000 msec. Buffering is disabled when the recovery timer is set to 0. Activates or deactivates the heartbeat procedure at the IUA level.
Recovery Timer (msec)
Heart Beat
The heart beat is enabled. The heart beat is disabled. No BEAT messages are sent, but the IUA software responds to received BEAT messages.
Release 9.0.0 5-51

Configuring Interface Protection Groups
Table 5-23. Field Descriptions for the IUA Layer Configuration Window (Continued) Field Name Field Values Field Description
[Max Peer ASs]
Default: 1 Range: Format: Numeric Default: 251 Range: Format: Numeric Default: Server Range: N/A Format: Predefined alphanumeric Server Client
Specifies the maximum number of remote peer application servers. Specifies the maximum number of outgoing streams per association. Specifies the role of the signaling gateway for initiating the SCTP associations.
[Max Outgoing Streams] Client Server Option
The server waits for SCTP association establishment. The client initiates SCTP association establishment. Identifies the port of the IUA service. The SCTP Registered User Port Number Assignment for IUA is 9900. 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 setting a value to enable buffering. Specifies the initial value of the heart beat timer. The recommended value is 1000 msec.
Local SCTP Port
Failover Buffer Size Default: 64 (KB) Range: 0999 Format: Numeric (KB) Heart Beat Timer (msec) Default: 1000 Range: 099999 Format: Numeric (msec)
[Max Peer ASPs Per Default: 1 AS] Range: Format: Numeric [Max Incoming Streams] Default: 251 Range: Format: Numeric
Specifies the maximum number of Application Server Processes per remote application server. Specifies the maximum number of incoming streams per association.

The Interface Protection Group feature enables you to configure an interface protection group as primary and secondary, with the secondary group serving as a standby in the event the primary ATM link fails. You can group interfaces of the same type into primary and secondary protection groups. Each group can have up to four primary and four secondary interfaces. Configuring interface protection groups consists of the following procedures:

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 interface 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 displayed (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). 4 Enter values in the fields on this window according to the information 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
Release 9.0.0 5-53

Figure 5-22. Interface Protection Feature Configuration Window
The menu options on this window have the following functions.

Table 5-24. Commands for the Interface Protection Feature Configuration Window Option Description
Protection Group Table Interface Protection Table Go Back to Site Specific Menu
Displays the Protection Group Table window. Displays the Interface Protection Table window. Redisplays the Site-Specific Menu window.
Release 9.0.0 255-700-447

Figure 5-23. Protection Group Table Window
The commands on this window have the following functions.

Table 5-25. Commands for the Protection Group Table Window Command Function
Page Up Page Down Top Bottom Total:0/0
Scrolls up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. The first number in this field indicates the number of the table entry on the first line of the currently displayed window. The second number indicates the total number of entries in this table. Displays the Protection Group Configuration screen. Redisplays the Interface Protection Feature Configuration window.
Add a Protection Group Go Back to the Interface Protection screen
Release 9.0.0 5-55

Figure 5-24. Protection Group Configuration Window

Table 5-26. Commands for the Protection Group Configuration Window Command Function
Add to Protection Group Delete from Protection Group and Return Go Back to Protection Group Table
Creates a new protection group ID and applies the values in the fields. Deletes the protection group ID and redisplays the Protection Group Table window. Redisplays the Protection Group Table window.
Table 5-27. Field Descriptions for the Protection Group Configuration Window Field Names Field Values Description
Group ID
Default: 0 Range: 19999 Format: numeric
Specifies the group ID that represents a unique interface protection group within the PSAX system. Specifies the method used to switch traffic from a failed primary interface to an available standby interface. Indicates that the PSAX system automatically switches the traffic. Indicates that the traffic on a failed primary interface is not switched automatically, but must be switched manually on the Interface Protection Configuration window.
Release 9.0.0 255-700-447
Switchover Method Default: Auto Range: N/A Format: predefined alphanumeric Auto Manual

Table 5-27. Field Descriptions for the Protection Group Configuration Window (Continued) Field Names Field Values Description
Switchback Method Default: Auto Range: N/A Format: predefined alphanumeric Auto Manual
Specifies the method used to switch traffic from a standby interface to its corresponding recovered primary interface. Indicates that the PSAX system automatically switches traffic. Indicates that the traffic on a standby interface is not switched automatically, but must be switched manually on the Interface Protection Configuration window. Specifies the method used to determine the order of selection of a standby interface that will be used if the primary interface fails. Indicates that the PSAX system internally selects the next higher numbered available standby interface to the last one. Indicates that the PSAX system uses the last available standby interface freed. Not currently supported. Indicates that the PSAX system uses the standby interface that has remained idle for the longest period of time. Not currently supported. Indicates that the PSAX system uses a randomly selected standby interface. Not currently supported. Indicates that the PSAX system uses the standby interface that you select.
Standby Selection
Default: Sequential Range: N/A Format: predefined alphanumeric Sequential
Latest-used
Oldest-used
Random
Explicit
Creating an Interface Protection Group

Begin
1 On the Interface Protection Feature Configuration window, select the Interface Protection Table option. The Interface Protection Table window is displayed (see Figure 5-25). 2 Select the Add a Protection Group command. The Interface Protection Configuration window is displayed (Figure 5-26). 3 Enter values in the fields on this window according to the information given in Table 5-30.
Release 9.0.0 5-57

4 To add the interface to the protection group, select the Add to interface protection group command. Note:
End
Switchover and switchbacks can be initiated only when configuring the primary interface protection.
Figure 5-25. Interface Protection Table Window

Table 5-28. Commands for the Interface Protection Table Window Command Function
Page Up Page Down Top Bottom Total: 0/0
Scrolls up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. The first number in this field indicates the number of the table entry on the first line of the currently displayed window. The second number indicates the total number of entries in this table. Displays the Interface Protection Configuration screen. Redisplays the Interface Protection Feature Configuration window.
Add a Protection Group Go Back to the Interface Protection screen
Release 9.0.0 255-700-447

Figure 5-26. Interface Protection Configuration Window

Table 5-29. Commands for the Interface Protection Configuration Window Command Function
Add to Interface Protection Group Delete from Interface Protection and Return Interface Switchover Interface Switchback Go Back to Protection Group Table
Adds an interface to an interface protection group. Deletes an interface from an interface protection group. Initiates a manual switchover from the failed primary interface to the standby interface. Initiates a switchback. Redisplays the Protection Group Table window.
Release 9.0.0 5-59

Table 5-30. Field Descriptions for the Interface Protection Configuration Window Field Names Field Values Description
Group ID
Default: 0 Range: 19999 Format: numeric Default: 0 Range: 19999 Format: numeric
Specifies the group ID that represents a unique protection group within the PSAX system. You must first set up this group ID on the Protection Group Configuration window. Specifies the logical number that is associated with the group ID within the PSAX system.
Logical ID
Slot
Default: 00 Specifies the slot number containing the module Range: chassis depen- you want to include in this interface protection group. dent Format: numeric Default: 00 Range: module dependent Format: numeric Default: 00 Range: module dependent Format: numeric Default: Primary Range: N/A Format: predefined Primary Secondary Specifies the port number on the module you want to include in this inteface protection group.
Port
Channel
Specifies the channel number of the port on the module you want to include in this interface protection group. Specifies whether this interface is the primary or secondary (standby) interface. Indicates that the interface is the primary interface. Indicates that the interface is the secondary (standby) interface. Specifies the standby interface logical number on which to switch traffic. You can use this field only when you select the value Manual in the Switchover Method field and the value Explicit in the Standby Selection field on the Protection Group Configuration window. You must set the value in this field after performing a switchover. Indicates whether the interface is operational or not. Indicates that the interface is not operationally active. Indicates that the interface is operationally active. Protection operational state of the interface. Indicates which logical interface is carrying traffic originally configured for this interface.
Interface Type
Select Standby Number
Default: 0 Range: Format: numeric
Operational State (display only)
Default: Inactive Range: N/A Format: predefined Inactive Active
Operational Interface (display only)
Default: 0 Range: Format: numeric
Release 9.0.0 255-700-447


Perform the following procedure to configure the call control resource allocations for your Multiservice Media Gateway system.
Begin
1 From the Console Interface Main Menu, select the Site-Specific Configuration 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. 3 Enter values in the fields on this window according to the information provided in Table 5-32. 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)
Release 9.0.0 5-61

Figure 5-28. The IP Throttling Window (Disabled)
Figure 5-29. The IP Throttling Window (Enabled)

Table 5-31. Commands for the IP Throttling Configuration Window Command Function
Apply Configuration Continuous Update
Sets the values you select on this window. Continuously updates all fields once every second.
Release 9.0.0 255-700-447

Table 5-31. Commands for the IP Throttling Configuration Window (Continued) Command Function
Reset Statistics Go Back to Site-Specific Menu
Resets all statistics counters for this window to 0. Redisplays the Site-Specific Menu window.
Table 5-32. Field Descriptions for the IP Throttling Configuration Window Field Name Field Values Description
IP Throttling
Default: Disabled
Indicates whether traffic will go through the ETHERNET port and in-band management virtual port (in the backplane) by its maximum designated throughput in the Allowed Rate field. Note: This feature will not be applied to the backup CPU module. The IP Throttling feature is turned off. If you select this value, the following fields in this table will disappear, and the feature will not affect the IP data path. The IP Throttling feature is turned on. (If you select this value, the following fields in this table will appear.)
Disabled
Enabled
Release 9.0.0 5-63

Table 5-32. Field Descriptions for the IP Throttling Configuration Window (Continued) Field Name Field Values Description
Allowed Rate
Default: 2000 fps Range: 1002000 fps
Specifies the maximum bandwidth allowed to pass through the ETHERNET or in-band management virtual 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 ETHERNET 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. Select this value to allow up to 100 frames per second of input to the CPU module. Select this value to allow up to 200 frames per second of input to the CPU module. Select this value to allow up to 300 frames per second of input to the CPU module. Select this value to allow up to 500 frames per second of input to the CPU module. Select this value to allow up to 1,000 frames per second of input to the CPU module. Select this value to allow up to 2,000 frames per second of input to the CPU module. Select this value to allow a number of frames per second 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. 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. The virtual buffer that serves as a counter that monitors the rate of ingress traffic to the CPU module. It counts 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.
100 fps 200 fps 300 fps 500 fps 1000 fps 2000 fps Other fps
Rate
Default: N/A Range: 120000 fps
Leaky Bucket Size
Default: 32 Range: 120000
Release 9.0.0 255-700-447

SNMP Trap Activation and Deactivation
Table 5-32. Field Descriptions for the IP Throttling Configuration Window (Continued) Field Name Field Values Description
In Packets (display only)
Default: N/A Range: N/A Format: numeric 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. The number of input packets passed through the ETHERNET port of the CPU module. The number of input packets dropped through the ETHERNET port of the CPU module. The number of input packets passed through the inband management virtual port of the CPU module. The number of input packets dropped through the in-band management virtual port of the CPU module. Number of seconds since the Reset Statistics command was selected.
Passed Ether Port (display only)
Dropped Ether Port Default: N/A (display only) Range: N/A Format: numeric Passed IBM (display only) Dropped IBM (display only) Time Elapsed (display only) Default: N/A Range: N/A Format: numeric Default: N/A Range: N/A Format: numeric Default: N/A Format: Hours, minutes, and seconds

The SNMP Trap Activation/Deactivation feature allows you to suppress the generation of up to 255 lower-level trap messages, enabling you to view only the 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 problem affects the entire PSAX system. This feature is available on both the PSAX system console interface and the AQueView Element Management System.
Release 9.0.0 5-65

Enabling and Disabling SNMP Trap Messages

To enable or disable the generation of specific SNMP trap messages in the PSAX system. On the Trap Activation Table window, deactivate the trap message(s) you wish by selecting them and pressing Enter once. The status Deactivated is displayed. Pressing Enter again restores activation. After trap deactivation, if you manually refresh the console interface window related to the specific trap you deactivated, this action results in cancelation of the specific trap deactivation. The trap message is then displayed. A sample procedure for this function follows. This example assumes that the trap cardInsertionNotify is in Activated status. 1 On the Trap Activation Table, using Page Down command, locate the trap cardInsertionNotify. 2 Press Enter to change the status of the cardInsertionNotify trap to Deactivated. 3 Return to the Equipment Configuration window. 4 Insert a module into an unconfigured slot. The module name is not displayed in the slot, although the FirmwareDownloadSucceeded trap is displayed after a few seconds. 5 To refresh the screen display, select the Update Equipment Display command and press Enter. The newly inserted module is displayed on the line for the slot into which it was inserted. The preceding example shows a temporary cancelation of the deactivated trap message using the Update Equipment Display command. This action did not cancel the trap Deactivated status of the trap on the Trap Activation Table window. If a window does not have a specific refresh or reset command, use the shortcut keys Ctrl+R. You do not need to reboot your CPU to use this feature. The trap activation messages can be activated or deactivated at any time.
Trap Activation Table Window

Access the Trap Activation Table window from the Site-Specific Menu window by selecting the Trap Activation Configuration command. This window displays only those traps that are eligible for deactivation.
Release 9.0.0 255-700-447

Figure 5-30. Trap Activation Table Table 5-33. Commands for the Trap Activation Table Window Command Function
PgUp PgDown Top Bottom Find . . .
Displays the previous page in the trap names table. Displays the next page in the trap names table. Displays the beginning page in the trap names table. Displays the last page in the trap names table. Searches the trap names table for a text string you enter between the quotation marks. This function is case-sensitive. Redisplays the Site-Specific Menu window.
Go Back to Site Specific Menu
Release 9.0.0 5-67

Table 5-34. Field Descriptions for the Trap Activation Table Window Field Name Field Values Description
Total: / (display only)
Default: 1/xxx where xxx represents the highest number of the last trap name in the table Range: 1255 Format: Numeric Default: N/A Range: 14 Format: Numeric
Displays the number of the selected trap name and the total number of trap names in the table. The first number in this field identifies the number of the trap name entry on the selected line of the currently displayed window. The second number indicates the total number of trap names in the table. Displays the system-defined trap group ID: 1 = System 2 = Module 3 = Interface 4 = Connection Displays the system-defined trap index number within the trap group, for example, ConnectionEvent = 87, where 87 is the trap index number. Displays the trap name.
ID (display only)
Ind (display only)
Default: N/A Range: 1126 Format: Numeric Default: N/A Range: N/A Format: Predefined alphanumeric Default: Activated Range: N/A Format: Predefined alphanumeric Activated Deactivated
Trap Name (display only)
Status
Displays the current activation status of the trap name.
Enables the display of the trap on the Trap Log Display window. Disables the display of the trap on the Trap Log Display window. When you select the line containing the trap name you want to deactivate and press Enter, Deactivated is displayed in this field.
Release 9.0.0 255-700-447

Collecting Bulk Statistics

Overview of Tasks
To collect bulk statistics on ATM and frame relay interfaces on the PSAX system to be sent to a remote statistics server, you need to perform the following tasks: 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 statistics 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 connection 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. The PSAX system sends collected statistics periodically at a user-specified frequency.
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed. 2 On the Site-Specific Menu window, select the Bulk Statistics Configuration option. The Bulk Statistics Configuration window is displayed (see Figure 5-31). 3 Enter values in the fields on this window according to the information provided in Table 5-36. The commands on this window are described in Table 5-35.
End
Release 9.0.0 5-69

Figure 5-31. Bulk Statistics Configuration Window
Table 5-35 describes the commands on this window.

Table 5-35. Commands for the Bulk Statistics Configuration Window Command Function
Apply Bulk Statistics Configuration Go Back to Site Specific Menu
Applies the configuration values you entered on this window. Redisplays the Site-Specific Menu window.
Table 5-36 describes the fields on this window.

Table 5-36. Field Descriptions for the Bulk Statistics Configuration Window Field Name Field Values Statistics Server Information Description
Statistics Server IP Addr Login
Default: None Range: N/A Format: IP Address
Specifies the IP address of the network server on which the PSAX system bulk statistics will be stored.
Default: None Specifies the username to access the network server. Enter a username no longer than 20 alphaRange: N/A Format: Alphanumeric numeric characters in length. You must have already set up this username on the network server. Default: None Specifies the password to access the network server. Enter a password no longer than 20 alphanumeric Range: N/A Format: Alphanumeric characters in length. You must have already set up this password on the network server.
Password
Release 9.0.0 255-700-447

Using the Equipment Configuration Window
Table 5-36. Field Descriptions for the Bulk Statistics Configuration Window (Continued) Field Name Field Values Description
Directory
Default: None Specifies the directory pathname on the network server to which the PSAX system will send the bulk Range: N/A Format: Alphanumeric statistics. Enter a directory pathname no longer than 79 characters in length. You must have already set up this directory pathname on the network server. Default: 60 Range: 601440 Format: Numeric (minutes) 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. Displays the current operational status of the transmission of bulk statistics files via FTP to the network server. Indicates that the PSAX system is not currently sending bulk statistics file to the network server. Indicates that the PSAX system is currently sending bulk statistics file via FTP to the network server. Indicates that the most recent bulk statistics file was sent successfully to the network server. Indicates that the PSAX system could not successfully send the bulk statistics file to the network server due to an FTP or another type of error. Displays the maximum number of bulk statistics records the PSAX system can support for collecting ATM and frame relay interface statistics and ATM and frame relay PVC connection statistics. Displays the number of bulk statistics records currently being collected including ATM and frame relay interface statistics and ATM and frame relay connection statistics.
Collection Time Period
[Operation Status]
Default: Inactive Range: N/A Format: Predefined Inactive InProgress Successful Failed
[Max Usage]
Default: 1000 Range: 01000 Format: Numeric Default: 0 Range: 01000 Format: Numeric
[Current Usage]

This section describes how to obtain product, model, version, and serial number 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 channel configuration windows for the PSAX modules.
Release 9.0.0 5-71

Accessing the Equipment Configuration Window

Perform the following procedure to access the Equipment Configuration window.
Begin
1 On the Console Interface Main Menu window, select the Equipment Configuration option. The Equipment Configuration window is displayed (see Figure 5-32 and Figure 5-33). Table 5-37 describes the commands on the windows and Table 5-38 describes the fields on these windows. 2 View the operational and alarm status, software version, PEC, and serial number data of the installed modules. 3 When you are ready to begin configuring the ports and channels of the module, select the line displaying the name of the module you want to configure. 4 Proceed to the section, Configuring the Ports, for module configuration procedures.
End
Figure 5-32. Sample Equipment Configuration Window on a PSAX 2300 or PSAX 4500 System (Page 1)
Release 9.0.0 255-700-447

Figure 5-33. Sample Equipment Configuration Window on a PSAX 1000, PSAX 2300, or PSAX 4500 System (Page 2)
Commands
The commands on this window are described in Table 5-37.
Table 5-37. Commands for the Equipment Configuration Window Command Function
Update Equipment Display Page Down Page Up Interface by Name Go Back to Main Menu
Refreshes the current status of the modules in the PSAX chassis. Displays the second page of the Equipment Configuration window. Displays the first page of the Equipment Configuration window. Displays the Interface Name Table window on which you can view all the interface names in the PSAX system. Redisplays the Console Interface Main Menu window.
Field Description
The display-only fields on this window are described in Table 5-38.
Release 9.0.0 5-73

Table 5-38. Field Descriptions for the Equipment Configuration Window Field Name Field Values Description
Slot
Default: N/A Displays the slot number in the PSAX chassis. Range: 125, depending on chassis type Format: Numeric Default: N/A Range: from PSAX system database Format: Predefined alphanumeric Default: Unknown Range: N/A Format: Predefined alphanumeric Unknown Primary 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. Displays the operational status of the module.
Module Type
Status
Indicates that the module has not been configured. 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. 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 functioning as the standby (backup) CPU module. Displays the present alarm condition of the module. For the alarm status conditions, see the table Alarm Status Descriptions for Modules following this field description table.
Standby
Alarm Status
Default: No Alarm Range: N/A Format: Predefined alphanumeric
Release 9.0.0 255-700-447

Table 5-38. Field Descriptions for the Equipment Configuration Window (Continued) Field Name Field Values Description
SW #
Default: N/A Range: (from module firmware) Format: Predefined alphanumeric
Displays the version of PSAX system software with which the modules firmware was released. The software version is encoded in the module firmware. Because not all modules require firmware upgrades with every new PSAX system software release, the software version that is displayed in this window may be lower than the CPU system software that is currently running on the PSAX system. See the most recent Release Note document for the latest software and firmware lineup information. Displays the product element code (PEC) used to identify and order this type of module. The PEC is encoded in the module bootloader.
PEC
Default: N/A Range: from module bootloader Format: Predefined alphanumeric Default: N/A Range: (from module firmware) Format: Predefined alphanumeric
Serial #
Displays the unique serial number of the individual module. The product serial number is encoded in the module firmware. The format of this field is the following: PSAX System Rel. 6.5.0 and later: 12-digit number in the format: YYVVDDnnnnnn, where YY = year of manufacture VV = vendor ID code (manufacturer and location) DD = date code of manufacture (either month or week depending on vendors preference) nnnnnn = sequential number, which in conjunction with YY, VV, and DD, creates a unique number for each hardware component in the PSAX product line For existing products with the 10-digit serial number used in Rel. 6.5.0 or later systems, this number is displayed with two preceding zeros. PSAX Rel. 6.3.0 and earlier: 10-digit number. For products with 12-digit serial numbers used in Rel 6.3.0 or earlier systems, the first two digits (YY) are not displayed.
Alarm Status Values

I/O and server modules display the status value of Primary if they are configured, or Unknown if they are unconfigured. The Alarm Status column for unconfigured modules still can have a number listing the ports that are available to be configured. If numbers in the Alarm Status column are underlined, this condition indicates a loss of signal. The alarm status descriptions for the Alarm Status field on the Equipment Configuration window are provided in Table 5-39.

Configuring the Stratum 34 Module
Table 5-39. Alarm Status Descriptions for Modules on the Equipment Configuration Window Alarm Status Module Type Affected Description
NoAlarm WrongCardType
I/O and Server I/O and Server
Indicates that no alarms have been detected for the module in this slot. Indicates that one type of module was configured in this slot in the chassis, but a now different module occupies this slot. Indicates that the module in this slot is no longer receiving or transmitting signals because the line failed. Indicates that one or more ports on the module in this slot currently have a loss of signal. The numbers indicate which ports have a loss of signal. For modules that have more than eight ports not receiving signals, the value in this field is in hexadecimal format. Indicates that one of the following events occurred: The module in this slot was configured and then removed from the slot. Connections on the OC-3, OC-12, STM-1, or STM-4 APS/MSP primary module in this slot were transferred to the standby module. After the transfer occurs, the former primary module then displays CardRemoved in the Alarm Status field; the former standby module then displays Primary in the Status field. Indicates that the timing reference clock on the Stratum module in this slot failed. Indicates that the timing composite clock on the Stratum module in this slot failed. Indicates that the Power Supply module is operating under an overload condition. Indicates that the power has failed. Indicates that the -48 V dc Power Supply module output failed. Indicates that the reason for failure is not known. Indicates that the backplane detected a clock error. Indicates that no power is coming into the PSAX chassis.
LineFailed Hexadecimal format, Example: 12345678ABC
All I/O and Server
CardRemoved
All
ReferenceClockFailed Stratum 34 CompositeClockFailed Stratum 34 Overload PowerFailed Minus48vFailed UnknownAlarm PowerFailed Power Supply Power Supply Power Supply I/O and Server Power Supply
CompleteClockFailed Stratum 34

Data and voice transmit most efficiently (with the least amount of cells lost per second) if a proper clock timing source is present in the PSAX 2300 chassis. Therefore, we recommend that you configure the Stratum 34 module through the Stratum Configuration window before configuring any I/O or server modules.
Release 9.0.0 255-700-447

Setting the Stratum Configuration Values

To configure the Stratum 34 module synchronization source, clock accuracy, 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 provided in Table 5-41. If LineTiming is selected in the Synchronization Source field, the Primary 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 Configuration 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) PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 5-77

Figure 5-35. Stratum Configuration Window (LineTiming Synchronization)
Commands
The commands in the Stratum Configuration window are described in Table 5-40.
Table 5-40. Commands for the Stratum Configuration Window Command Function
Switch Line Timing Source
Switches between the primary and secondary line timing sources specified in the Primary Line Source and Secondary Line Source fields. This command appears only when LineTiming is selected in the Synchronization Source field. Applies the values you enter in this window to the module. Sets the values in this window to the last saved (applied) set of values. Redisplays the Equipment Configuration window.
Apply Stratum Configuration Reset Stratum Display Go Back to Equipment Configuration
Field Descriptions
The fields in the Stratum Configuration window are described in Table 5-41.
Release 9.0.0 255-700-447

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 Holdover
Indicates the current mode of operation for the primary Stratum 34 module. Indicates that the primary module has lost its synchronization source because of excessive frequency offset and that the Holdover timing mode is maintaining chassis timing. 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. Indicates the module clock circuitry is locked to a Stratum3 level of precision. Indicates the module clock circuitry is locked to a Stratum4 level of precision. Indicates that the primary Stratum 34 module is not present. Indicates the current mode of operation for the backup Stratum 34 module. Indicates that the backup module has lost its synchronization source because of excessive frequency offset and that the Holdover timing mode is maintaining chassis timing. 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. Indicates the module clock circuitry is locked to a Stratum3 level of precision. Indicates the module clock circuitry is locked to a Stratum4 level of precision. Indicates that the backup Stratum 34 module is not present.
Freerun
Synchronized3 Synchronized4 CardRemoved [Backup Stratum Mode] Default: Holdover Range: N/A Format: Predefined Holdover
Freerun
Synchronized3 Synchronized4 CardRemoved
Release 9.0.0 5-79

Table 5-41. Field Descriptions for the Stratum Configuration Window (Continued) Field Name Mode of Operation Description
[Line Timing Status]
Default: None Range: N/A Format: Predefined None PrimaryLine
Indicates the current line timing status for the module. Indicates that the system timing is not being provided by the line timing source. 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. Indicates that the system timing is provided by the slot and port of the module specified as the Secondary Line Source when LineTiming is selected as the synchronization source and the primary line source has been removed or failed. Indicates the status of the input T1BITS or E1ETSI clock source connected to the external clock connector on the primary Stratum 34 module. Indicates the T1BITS or E1ETSI clock source is not connected to the external clock connector. Indicates the connected T1BITS or E1ETSI clock source is functioning properly. Indicates the connected T1BITS or E1ETSI clock source is reporting an alarm indication signal. Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of frame. Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of signal. Indicates the connected T1BITS or E1ETSI clock source is reporting a frequency offset.
SecondaryLine
[Primary Stratum T1/E1 Port Status]
Default: Unconfigured Range: NA Format: Alphabetical Unconfigured noalarm portAIS portLOF portLOS portFOS
Release 9.0.0 255-700-447

[Backup Stratum T1/E1 Port Status]
Default: Unconfigured Range: NA Format: Alphabetical Unconfigured noalarm portAIS portLOF portLOS portFOS
Indicates the status of the input T1BITS or E1ETSI clock source connected to the external clock connector on the baclup Stratum 34 module. Indicates T1BITS or E1ETSI clock source is not connected to the external clock connector. Indicates the connected T1BITS or E1ETSI clock source is functioning properly. Indicates the connected T1BITS or E1ETSI clock source is reporting an alarm indication signal. Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of frame. Indicates the connected T1BITS or E1ETSI clock source is reporting a loss of signal. Indicates the connected T1BITS or E1ETSI clock source is reporting a frequency offset. Indicates the precision of the clock circuitry when it locks to the selected external synchronization source (CompositeClock, CompositeClockDS0A, T1BITS, and E1ETSI, selected in the Synchronization Source field). Indicates the timing source has a Stratum3 level of precision. Indicates the timing source has a Stratum4 level of precision. Indicates what timing source is used when the selected 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. Indicates that the module switches to freerun if the selected synchronization source fails. Indicates that the module switches to holdover mode if the selected synchronization source fails.
Accuracy
Default: Stratum3 Range: NA Format: Alphabetical
Stratum3 Stratum4 On Reference Clock Default: Freerun Failure Go To Range: NA Format: Alphabetical
Freerun Holdover
Release 9.0.0 5-81

Synchronization Source
Default: LineTiming Range: NA Format: Alphabetical
Indicates the synchronization source to be used by the chassis and specified I/O modules. The I/O modules use this source when LocalTiming is selected in the Transmit Clock field that appears on most channel and port configuration windows. Indicates that the synchronization source is to be provided through the slot and port specified in the Primary Line Source or upon failure of the Primary Line Source in the Secondary Line Source fields. Any data rate can be selected on either line source; the module does not care what rate is chosen. If LineTiming is selected, the Primary Line Source and the Secondary Line Source fields and the Switch Line Timing Source command are displayed. Indicates that the synchronization source is to be provided through the internal clock of the Stratum 34 module. Indicates that the synchronization source is to be provided through the external composite clock (64 Kbps) connected to the external clock connector on the primary Stratum 34 module. Indicates that the synchronization source is to be provided through the external composite clock (64 Kbps) connected to the external clock connector on the primary Stratum 34 module. This option is only used by the 12-Port Medium-Density DS1/E1/DS0A CES module when operating in the DS0A mode. Indicates that the synchronization source is to be provided through the external T1BITS clock (1.544 Mbps) connected to the external clock connector on the primary Stratum 34 module. Indicates that the synchronization source is to be provided through the external E1ETSI clock (2.048 Mbps) connected to the external clock connector on the primary Stratum 34 module. Specifies the primary line source when LineTiming 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 timing.
LineTiming
Freerun
CompositeClock
CompositeClockDS0A
T1BITS
E1ETSI
Primary Line Source
Default: Slot: 00 Port: 00 Range: Chassis/module dependent Format: Numeric
Release 9.0.0 255-700-447

Secondary Line Source
Default: Slot: 00 Port: 00 Range: Chassis/module dependent Format: Numeric
Specifies the secondary line source when LineTiming 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 timing. 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. 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. 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 providing 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.
Slot
Default: 00 Range: Depends on chassis. Format: numeric Default: 00 Range: Primary Line Source, depends on the number of ports on the module selected in the Slot field; Secondary Line Source, 0030, or All Range: numeric
Port
Switching the Line Timing Source

At any time after initial configuration of the Stratum 34 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
Release 9.0.0 5-83

Saving the Equipment Configuration Values and Logging Off
Alarm Status Values

I/O and server modules display the status value of Primary if they are configured, or Unknown if they are unconfigured. The Alarm Status column for unconfigured modules still can have a number listing the ports that are available to be configured. If numbers in the Alarm Status column are underlined, this condition indicates a loss of signal.

After configuring your basic systemwide values, you must save them to the PSAX system database. It is recommended that you save your values frequently as you progress through your work. If you modify your system configuration before you begin upgrading your system software release in the same console session, you must save your configuration first before beginning 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 not yet saved the values permanently, you will lose all unsaved values you have applied on the various windows.
Begin
1 To return to the Console Interface Main Menu window, press Ctrl+G. 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).
Release 9.0.0 255-700-447

Figure 5-36. Save Configuration [Modified] (Before Saving)
2 Select the Save Configuration command or press Ctrl+A. Wait a few seconds while the system writes the values to the PSAX system database. The system displays the following message while it is executing 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 SVC retention 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.
Table 5-42. Messages Generated after the Save Configuration Process When a PSAX system is... the system displays... T-SaveConfiguration: saveConfigurationReasonCode=All-OK T-SaveConfiguration: saveConfigurationReasonCode = Expect2ndCPUCardFailedOrRemoved*
nonredundant redundant
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: saveConfigurationReasonCode=FileTransferCompleted
*
This message indicates that while the standby CPUn module reboots after you select the Save Configuration command, the standby CPUn module is temporarily unavailable.
Release 9.0.0 5-85

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 Console Interface command. This action logs you off the PSAX system console interface. ! CAUTION: Always exit the PSAX system by using the Leave Console Interface command. Do not just close your HyperTerminal or Telnet window without first using this command because doing so might cause access problems at a later time.
End
Release 9.0.0 255-700-447
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 following 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 Configuration 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 identifier 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.
Release 9.0.0 6-1
Chapter 6 Configuring ATM PNNI

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 a nodes 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
Figure 6-1. PNNI System-Wide Configuration Menu Window
The menu options on this window have the following functions:

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- Displays the PNNI Route Address Table window on tion which you add a PNNI route address. PNNI Route TNS Configuration Displays the transit network string (TNS) information: node index, TNS type, TNS plan, TNS ID, and TNS index.
PNNI Summary Address Config- Displays ATM NSAP addresses for all nodes to uration which this link table is attached by PNNI interfaces.
Release 9.0.0 255-700-447

Table 6-1. Commands for the PNNI System-Wide Configuration Window (Continued) Menu Option Name Function
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. Displays the PNNI node ID and Map Node ID (in hexadecimal).
PNNI Map Node Information
PNNI Map Address Information Displays the node index, advertising node ID in hexadecimal, advertising port ID, and address index. PNNI Map TNS Information PNNI Link Information PNNI SVCC RCC Information PNNI Neighbor Peer Information PNNI Neighbor Peer Port Information PNNI PTSE Information PNNI System Statistics Go Back to Site-Specific Menu Displays the node index, advertising node ID, and advertised port ID. Displays an index of nodes and their associated links for the PSAX system. Displays the node index, PNNI SvccRcc Index, VPI, and VCI. Displays nodes that are on the same level as this node. Displays the status of the node ports on the same level as this node. Displays the node index, PNNI Topology State Element (PTSE) originating node ID, and PTSE ID. Displays PNNI statistics. Redisplays the Site-Specific Menu window.
Release 9.0.0 6-3

Figure 6-2. PNNI Node Table Window

Table 6-2. Commands for the PNNI Node Table Window Command Function
Page Up Page Down Top Bottom Find Node Index Add Node Entry Go Back to Previous Screen
Scroll up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. Displays default five-number value on the Node Table window. Adds a node entry in the PSAX system. You may add up to 400 nodes. Redisplays the PNNI System-Wide configuration window.
The display fields on this window have the following values:
Release 9.0.0 255-700-447

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 identification 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 connection type.
Note: For more information on the values in the display fields below, see the Field Description Table for the PNNI Node Configuration window. Node Index Node Level Oper Status Displays default five-number value on the Node Table window, and identifies a logical PNNI entity in the PSAX system. Displays the number of significant bits in the network portion of the ATM address on the PSAX system. Displays whether the node is up or down.
Figure 6-3. PNNI Node Configuration Window (Before Configuration)
Release 9.0.0 6-5

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

Table 6-4. Commands for the PNNI Node Configuration Window Command Function
Create Node Entry Delete Node Entry Bring Node Into Service PNNI Node Pgl Table PNNI Node Timer Table PNNI Node SVCC Table PNNI Node Scope Mapping Table ATM Security Config - Routing SVCC Go Back to Previous Screen
Creates a new PNNI node. Deletes an existing PNNI node. Brings an existing PNNI node into or out of service. Displays the PNNI Node Pgl (Peer Group Leader) Configuration window. Displays the PNNI Node Timer Configuration window. Displays the PNNI Node SVCC Configuration window. Displays the PNNI Scope Mapping Configuration window. Displays the ATM PNNI SVCC RCC Security Configuration window. Redisplays the PNNI Node Table window.
Release 9.0.0 255-700-447

Table 6-5. Field Descriptions for the PNNI Node Configuration Window Field Name Field Values Description
Node Index
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 Indicates the system generates your Node Id automatically. For more information, see Range: N/A Format: Hexadecimal Section 5.3.3, Node Identifiers, in the ATM Forum Specification, Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni0055.000. Default: 0 Enter your ATM NSAP address, a hexadecimal number within the networks PNNI hierarchy Range: N/A Format: Hexadecimal that must beginning with 39, 45, or 47, depending on your world region. H.248 Applications: This address must be different from the Master ATM address configured on the Site Specific Configuration window. Default: 0 Indicates the first 12 bytes (default) of the ATM address. This value is the combination of the ATM Range: N/A Format: Hexadecimal address and the node level. The first byte indicates 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 system 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-pnni0055.000. Default: N/A Range: N/A Format: Alphanumeric Default: 096 Range: 96 (decimal)=60 (hexadecimal); 1104 Range: Hexadecimal Indicates the routing domain in which this node participates.
Atm Address
Peer Grp ID
Domain Name
Node Level
Indicates the level of PNNI hierarchy at which this node exists. Indicates the number of significant bits in the network portion of the ATM address on the PSAX system. This number is related 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 generate and display the value automatically.
Release 9.0.0 6-7

Table 6-5. Field Descriptions for the PNNI Node Configuration Window (Continued) Field Name Field Values Description
Node Lowest
Default: True Range: N/A Format: Predefined True False
Indicates whether or not this node is the root node. The current node is the root. The current node is not the root. Restricted Transit indicates whether the node is restricted to not allowing support of SVCs transmitting from this node. Indicates SVC transmission from the node is allowed, or not restricted. Indicates SVC transmission from the node is not allowed, or restricted. Specifies whether this node uses the complex node representation. This attribute determines the setting of the nodal representation bit in the nodal information group originated by this node. Indicates that simple node representation is used. Indicates that the complex node representation is used. 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. Indicates that additional branches can be supported. Indicates that additional branches cannot be supported. 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 nontransit for PGL election bit in the nodal information group originated by this node. Indicates the node is currently operating in a topology database overload state. Indicates the node is not currently operating in a topology database overload state. Displays the number of PTSEs displays the total PTSEs currently in the topology database(s) for this node.
Res. Transit
Default: False Range: N/A Format: Predefined False True
Complex Node
Default: False Range: N/A Format: Predefined False True
[Res Branching]
Default: False Range: N/A Format: Predefined
False True [DB Overload] Default: True Range: N/A Format: Predefined
True False [No of Ptses] Default: 0 Range: N/A Format: Numeric
Release 9.0.0 255-700-447

Modifying an ATM PNNI Node Configuration
Table 6-5. Field Descriptions for the PNNI Node Configuration Window (Continued) Field Name Field Values Description
[Admin Status]
Default: N/A Range: N/A Format: Predefined Up Down
Displays the administrative status for this node.
The node is currently active. The node is not currently active. Displays the operational status for this node.
[Oper Status]
Default: N/A Range: N/A Format: Predefined Up Down
The node is currently active. The node is not currently active.
Modifying an ATM PNNI Node Configuration

To modify an ATM PNNI node configuration, choose one of the options shown in Table 6-6.
Table 6-6. Modifying a Configured PNNI Node To modify this type of do the following: PNNI node:
single-level node
1 Take all of the ATM PNNI interfaces configured on the I/O modules within the PSAX system out of service. 2 Delete the ATM PNNI interfaces. 3 Take the PNNI node out of service. 4 Modify the PNNI node with the desired changes.
multi-level node
1 Take all of the ATM PNNI interfaces configured on the I/O modules within the PSAX system out of service. 2 Delete the ATM PNNI interfaces. 3 Delete the parent nodes. 4 Take the PNNI node out of service. 5 Modify the PNNI node with the desired changes.
Configuring an ATM PNNI Node Peer Group Leader (PGL)

Begin
1 From the PNNI Node Configuration Window, select Pnni Node Pgl Table or press Ctrl+P. The PNNI Node PGL Configuration window is displayed (see Figure 6-5).

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 window. 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
Figure 6-5. PNNI Node PGL Configuration
The command on this window performs the following function:

Table 6-7. Commands for the PNNI Node Timer Configuration Window Command Function
Apply Configuration Go Back to Previous Screen
Applies the values you set on this window. Redisplays the PNNI Node Configuration window.
Release 9.0.0 255-700-447

Table 6-8. Field Descriptions for the PNNI Node PGL* Configuration Window Field Name Field Values Description
Node PGL Information Upper Panel
[Node Index]
Default: 0 Range: 1400 Default: 0 Range: 0205 Format: numeric Default: 0 Range: 165535 Format: numeric Default: 15 Range: 015 Format: seconds Default: 30 Range: 030 Format: seconds Default: 15 Range: 015 Format: seconds
Displays the node index that identifies a logical PNNI entity in the PSAX system. Enter the index number of each node in this field. 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). 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. Indicates the initiating time of the PGL election process. When this timer fires, the election begins after the time set by the user. Indicates the amount of time the node should wait for all nodes to agree on which node should be elected PGL. 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.
Leadership Priority Cfg Parent Node Index Initiation Time
Override Delay
Reelect Time
Release 9.0.0 6-11

Table 6-8. Field Descriptions for the PNNI Node PGL* Configuration Window (Continued) Field Name Field Values Upper Panel (display only) Description
[State]
Default: OperPgl Range: N/A Format: predefined OperPgl
Displays the status of this node PGL.
Displays that the status of this node is the PGL. It continues examining PTSEs sent by other nodes to see if another node has a higher priority than itself. Displays that this node is in the initial state of the state machine. Displays that this node has started the Hello FSM on at least one link, and that no peer group has yet been found. Indicates that at least one neighboring peer has been found, but no database synchronization process has been completed. 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. Indicates that the node is in the process of calculating its new choice for the preferred PGL. 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. 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. Indicates that the node has chosen itself as the PGL, but not all other nodes will advertise it as their preferred PGL. Indicates that the node has lost connectivity to the current PGL. If the connectivity has not been reesetablished before the period of time specified in the Reelect Time field, the election process is restarted.
Starting Awaiting
AwaitingFull
InitialDelay
Calculating AwaitUnanimity
OperNotPgl
HungElection
AwaitReElection
Release 9.0.0 255-700-447

Configuring an ATM PNNI Node Timer Table 6-8. Field Descriptions for the PNNI Node PGL* Configuration Window (Continued) Field Name Field Values Description
[Preferred Pgl]
Default: 0 Range: N/A Format: Hexadecimal address (up to 11 octets) Default: 0 Range: N/A Range: Hexadecimal address (up to 11 octets) Default: 00:00:00 Range: N/A Format: hh:ss:mm (hour, second, msec.)
Displays the preferred PGL. To select, any node compares the leadership priorities and node IDs advertised in the PTSEs in the topology database, and determines which nodes reachable from itself. 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. 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]
[Time Stamp]
Peer Group Leader.
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 (see Figure 6-6). 2 Enter the values for this window according to the information provided 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. 4 Select Go Back to Previous Screen or press Ctrl+B to return to the PNNI Node Configuration window if you need to configure other field values.
End
Release 9.0.0 6-13

Figure 6-6. PNNI Node Timer Configuration Window
The commands on this window perform the following functions:

Table 6-10. Field Descriptions for the PNNI Node Timer Configuration Window Field Name Field Values Node Timer Information Panel Description
[Node Index]
Default: 00000 Range: 1400 Format: numeric Default: 00010 Range: 165535 Format: numeric multiplier of 100 msec
Displays the node index that identifies a logical PNNI entity in the PSAX system. 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 initial value of this timer is used by a node to limit the 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.
Ptse Holddown.. (100 msec)
Release 9.0.0 255-700-447

Table 6-10. Field Descriptions for the PNNI Node Timer Configuration Window (Continued) Field Name Field Values Description
Hello Holddown.. (100 msec)
Default: 00010 Range: 065535 Format: numeric multiplier of 100 msec
Indicates the initial value for the Hello Holddown timer, which is used by a node to limit the rate at which it sends Hellos. Note: Each increment entered in this field is a multiplier of 100 msec. A value of 10 = 1 second, or 100 msec 10. 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. Indicates the value this node will use to determine when a neighbor has failed. Indicates the horizontal link inactivity time (horizontal links are between nodes in the same peer group 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 information group (IG). 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. Indicates the formula which calculates this product: Ptse Refresh Interval PTSE Lifetime Factor = PTSE Lifetime of self-originated PTSEs. Specifies the retransmit interval, which is the period between retransmissions of unacknowledged database summary packets, PTSE request packets, and PNNI Topology State Packets (PTSPs). Specifies the peer-delayed acknowledgement interval, which is the minimum number of miliseconds 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. Indicates the available cell rate (Avcr) proportional multiplier (PM), which is used in an algorithm that determines significant change for average cell rate parameters.
Hello Interval..(sec) Default: 00015 Range: 065535 Format: numeric (sec) Hello Inactivity Factor Hlink Inact..(sec) Default: 00005 Range: 065535 Format: numeric Default: 00120 Range: 065535 Format: numeric (sec)
Ptse Refresh Interval..(sec)
Default: 01800 Range: 065535 Format: numeric (sec)
Ptse Lifetime Factor Default: 0200 Range: 1011000 Format: numeric (percentage) Rxmt Interval..(sec) Default: 00005 Range: 065535 Format: numeric (sec) Peer Delayed Ack Interval.. (100 msec) Default: 00010 Range: 065535 Format: numeric multiplier of 100 msec
Avcr Proportional Multiplier
Default: 50 Range: 199 Format: numeric (percentage)
Release 9.0.0 6-15

Configuring an ATM PNNI Node SVCC
Table 6-10. Field Descriptions for the PNNI Node Timer Configuration Window (Continued) Field Name Field Values Description
Avcr Minimum Threshold
Default: 03 Range: 199 Format: numeric (percentage) Default: 25 Range: 199 Format: numeric (percentage) Default: 50 Range: 199 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. Indicates the cell delay variance proportional multiplier, which is used in the algorithm that determines significant change for CDV metrics. Indicates the cell transfer delay proportional multiplier, which is used in the algorithm that determines 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.
Cdv Proportional Multiplier
Ctd Proportional Multiplier

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). 2 Enter the values for this window according to the information provided in Table 6-12. 3 After setting all the values on the window, select Apply Configuration or press Ctrl+A. A trap message confirming the configuration application appears at the bottom of the window. 4 Select Go Back to Previous Screen or press Ctrl+B to return to the PNNI Node Configuration window if you need to configure other field values.
End
Release 9.0.0 255-700-447

Figure 6-7. PNNI Node SVCC Configuration Window

Table 6-12. Field Descriptions for the PNNI Node SVCC Configuration Window Field Name Field Values Description
[Node Index]
Default: 0 Range: 1400 Format: numeric Default: 4 Range: 065535 Format: seconds
Displays the node index that identifies a logical PNNI entity in the PSAX system. 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. Indicates the number of times that his node will wait before attempting to re-establish a SVCCbased RCC.
Init Time
Retry Time
Default: 30 Range: 065535 Format: seconds
Release 9.0.0 6-17

Configuring ATM PNNI Node Scope Mapping
Table 6-12. Field Descriptions for the PNNI Node SVCC Configuration Window (Continued) Field Name Field Values Description
Calling Integrity Time
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 giving up and tearing the SVCC down. 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. 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.
Called Integrity Time
Traffic Descriptor Index

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 (see Figure 6-8). 2 Enter the values for this window according to the information provided in Table 6-5. 3 After setting all the values on the window, select Apply Configuration or press Ctrl+A. A trap message confirming the configuration application appears at the bottom of the window. 4 Select Go Back to Previous Screen or press Ctrl+B to return to the PNNI Node Configuration window if you need to configure other field values.
End
Release 9.0.0 255-700-447

Figure 6-8. PNNI Scope Mapping Configuration

Table 6-14. Field Descriptions for the PNNI Scope Mapping Configuration Window Field Name Field Values Description
[Node Index]
Indicates the node index that identifies a logical PNNI entity in the PSAX system. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Local Network organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Local Network Plus One organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Local Network Plus Two organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Site Minus One organizational scope.
Release 9.0.0 6-19
Local Network (display only)
Local Network Plus Default: 96 One Range: 0104 (display only) Format: numeric Local Network Plus Default: 96 Two Range: 0104 (display only) Format: numeric Site Minus One (display only) Default: 80 Range: 0104 Format: numeric

Configuring an ATM PNNI Route Address
Table 6-14. Field Descriptions for the PNNI Scope Mapping Configuration Window (Continued) Field Name Field Values Description
Intra Site (display only) Site Plus One (display only)
Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Intra Site organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Site Plus One organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Organization Minus One organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Intra Organization organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Organization Plus One organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Community Minus One organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Intra Community organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Community Plus One organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Regional organizational scope. Return and type the Regional level number. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Inter Regional organizational scope. Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within the Global organizational scope.
Organization Minus Default: 72 One Range: 0104 (display only) Format: numeric Intra Organization (display only) Organization Plus One (display only) Default: 64 Range: 0104 Format: numeric Default: 64 Range: 0104 Format: numeric
Community Minus Default: 64 One Range: 0104 (display only) Format: numeric Intra Community (display only) Community Plus One (display only) Regional (display only) Default: 48 Range: 0104 Format: numeric Default: 48 Range: 0104 Format: numeric Default: 32 Range: 0104 Format: numeric Default: 32 Range: 0104 Format: numeric Default: 0 Range: 0104 Format: numeric
Inter Regional (display only) Global (display only)

The PSAX system allows up to 50 PNNI advertised routes. To configure PNNI route addresses, perform the following procedure.
Release 9.0.0 255-700-447

Begin
Note:
If you are configuring an SPVC as ActiveSvc, do not configure a route address. If you configuring an SPVC as PassiveSvc, configure 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). 3 Enter values in the fields on this window according to the information provided in Table 6-17. 4 Select the Create Route Address Entry command. The route is completed. 5 Using the instructions in the appropriate PSAX module user guide, configure 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 interface into service. 6 To add additional route addresses, repeat this procedure.
End
Figure 6-9. PNNI Route Address Table Window
The commands in this window have the following functions:


Table 6-15. Commands for the PNNI Route Address Table Window Command Function
Find..
Searches this table by the values you enter in the Node Index, Prefix Length, Address Index, and Route Address fields. Displays the PNNI Route Address Configuration window. Redisplays the PNNI System-Wide Configuration window.
Add Route Address Entry Go Back to Previous Screen
Figure 6-10. PNNI Route Address Configuration Window

Table 6-16. Commands for the PNNI Route Address Configuration Window Command Function
Add Route Address Entry
Adds the route address to the PNNI Route Address Table window. You can create up to 50 routes manually, to display in the PNNI Route Address Table window. However, more than 50 routes can be displayed by the PSAX system because route addresses are also learned dynamically.
Delete Route Address Entry Deletes the route address from the PNNI Route Address Table window. View Metrics Table Go Back to Previous Screen Displays the PNNI Metrics Table window. Redisplays the PNNI Route Address Table window.
Release 9.0.0 255-700-447

Table 6-17. Field Descriptions for the PNNI Route Address Configuration Window Field Name Field Values Route Address Information Panel Description
Node Index
Displays the node index that identifies a logical PNNI entity in the PSAX system. Enter the same value as assigned to the PNNI node. Indicates the address prefix of the ATM end system, in 19 bytes (it does not include the NSAP address selector byte). Indicates the node ID of the node advertising connectivity to the specified prefix. If the local node ID is 0, then this must be zeroes. This value is generated and displayed by the PSAX system automatically. A maximum of 50 PNNI routes can be advertised.
Route Address Pre- Default: N/A fix Range: N/A Format: Hexadecimal Adv Node Id Default: N/A Range: N/A Format: Hexadecimal
Interface Index
Default: 0 Indicates the local interface over which the Range: 02147483647 advertised node is reachable. If the node is only reachable through a remote node, this must be Format: Numeric set to 0. If the node is not set to zero, the address protocol (Address Proto field) must not be PNNI, and the Address Type field should not be set to Reject. Default: 0 Range: N/A Format: Numeric Specifies the advertised port identifier, used for call routing purposes: For an SVC endpoint, set this field to 0 or enter the slot, port, and channel number of the interface to which you want the call forwarded. For an SPVC endpoint, set this field to 0, then the PSAX routing functionality will decide whether to route the call out of the PSAX on an available PNNI interface, or to terminate the call on the PSAX itself (in the case of SPVCs). Enter a value that does not exceed 152 (19 octets = 152 bits). For an SPVC, enter the length of the Address Prefix which is accessible through this PNNI node for SPVC (1152 bits). Indicates an entry in a table that keeps track of which nodes can access which prefixes.
Adv Port Id
Prefix Length
Address Index
Release 9.0.0 6-23

Table 6-17. Field Descriptions for the PNNI Route Address Configuration Window (Continued) Field Name Field Values Description
Address Type
Default: Exterior Range: N/A Format: Predefined Exterior
Indicates the type of domain address.
Indicates a connection from the advertising node to the address prefix that belongs to an external domain address. Belongs to a domain address that is not defined as internal or external. Indicates that messages from a matching address prefix should be discarded as unreachable. Belongs to the same domain address, administrative authority, or attached device. Indicates the level of the PNNI hierarchy where the connectivity between the advertising node and the address prefix is located. Indicates whether virtual path connections (VPCs) can be established between the advertising node and the address prefix. VPCs can be established between the advertising node and the address prefix. VPCs cannot be established between the advertising node and the address prefix. Indicates whether the local node should advertise the reachable address on its domain (where it originates). The local node should advertise the reachable address on its domain (where it originates). The local node should not advertise the reachable address on its domain (where it originates).
Other Reject Internal Address Scope Default: 0 Range: N/A Format: Numeric Default: True Range: N/A Format: Predefined True False Org Advertisement Default: True Range: N/A Format: Predefined True False [Adv Ptse Id]
VP Capability
Default: 0 Displays the advertised PTSE identifer of the PTSE Range: 02147483647 being sent by the originating node, if this was learned through PNNI 1.0. Format: Numeric
Release 9.0.0 255-700-447

Configuring ATM PNNI Metrics
Table 6-17. Field Descriptions for the PNNI Route Address Configuration Window (Continued) Field Name Field Values Description
[Address Proto]
Default: Mgmt Range: N/A Format: Predefined Mgmt
Displays the protocol by which connectivity from the advertising node to the address prefix was learned. Connectivity from the advertising node to the address prefix was learned through Management protocol. Connectivity from the advertising node to the address prefix was learned through user-defined protocol. Connectivity from the advertising node to the address prefix was learned through Local protocol. Connectivity from the advertising node to the address prefix was learned through PNNI protocol.
Other
Local
Pnni
Metrics Tag
Default: 0 Indicates the primary routing metric for this Range: 02147483647 route. The semantics of this metric are determined by the routing-protocol specified in the Format: Numeric Address Proto value of the route. If this metric is not used, enter 1 in this field. Default: 00:00:00 Indicates when connectivity became known to the local node. Range: N/A Format: Numeric (days, hours, minutes, seconds) Default: Inactive Range: N/A Format: Predefined Inactive Indicates whether the reachable address prefix is operational and is being advertised by this node. Indicates that the reachable address prefix is not operational and is not being advertised by this node. 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.
[Time Stamp]
Operational Status
Advertised

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
Release 9.0.0 6-25

service categories, bandwidth, and so on. You can also view traffic patterns and other information about routes advertised on other nodes on the Route Address Table window.
Begin
1 From the PNNI Route Address Configuration window, select View Metrics Table. The PNNI Metrics Table window is displayed (see Figure 6-11). 2 Select the Add Metrics Entry command. The PNNI Metrics Configuration window is displayed (see Figure 6-12). 3 Enter the values in the fields on this window according to the information provided in Table 6-20. 4 Select the Create Metrics Entry command. This entry is added to the PNNI Metrics Table window. 5 If you are making changes to an existing metric configuration, select the Apply Configuration command. 6 Type Ctrl+G to return to the Console Interface Main Menu window and save the configuration.
End
Figure 6-11. PNNI Metrics Table Window
Release 9.0.0 255-700-447

Table 6-18. Commands for the PNNI Metrics Table Window Command Function
Find.. Add Metrics Entry Go Back to Previous Screen
Searches this table by the values you enter in the Node Index, Metrics Direction, Metrics Tag, or Metrics Index fields. Displays the PNNI Metrics Configuration window. 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 configuration.) Adds the metric entry to the PNNI Metrics Table. Applies the configuration values you set. Deletes the metric entry from the PNNI Metrics Table. Displays the PNNI Metrics Table.
Apply Configuration Delete Metrics Entry Go Back to Previous Screen
Release 9.0.0 6-27

Table 6-20. Field Descriptions for the PNNI Metrics Configuration Window Field Name Field Values Metrics Information Panel Description
Node Index
Default: 000000 Range: 1400 Format: numeric Default: 0 Range: N/A Format: numeric
Displays the node index that identifies a logical PNNI entity in the PSAX system. 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. Specifies the direction, with respect to the advertising node, to which these parameters apply (may have multiple service categories). Indicates that metrics parameters will be applied to the incoming direction of data traffic. Indicates that metrics parameters will be applied to the outgoing direction of data traffic Indicates an index into a set of parameters associated with the given tag and direction. Specifies the service class to which this metric belongs. Indicates constant bit rate service class. Indicates real-time variable bit rate service class. Indicates nonreal-time variable bit rate service class. Indicates available bit rate service class. Note: This value is not currently supported. Indicates unspecified bit rate service class. Indicates the administrative weight from the advertising node to the remote end of the PNNI entity or to the reachable address or transit network, for the specified service categories. The lower the value of the administrative weight, the more preferable this interface.
Metrics Tag
Metrics Direction
Default: Incoming Range: N/A Format: predefined alphanumeric Incoming Outgoing
Metrics Index
Default: 0 Range: 031 Format: numeric Default: 0 Range: 031 Format: numeric CBR rt_VBR nrt_VBR ABR UBR
Metrics Class
Admin Weight
Max Cell Rate
Default: 0xFFFFFFFF Indicates the maximum cell rate, in hexadecimal notation, for directions and specific service cateRange: N/A Format: hexadecimal gories (see the descriptions for the fields Metrics Direction and Metrics Classes.
Release 9.0.0 255-700-447

Configuring an ATM PNNI Route TNS
Table 6-20. Field Descriptions for the PNNI Metrics Configuration Window (Continued) Field Name Field Values Description
Available Cell Rate
Default: 0xFFFFFFFF Indicates the available bandwidth on this interface, in hexadecimal notation. Range: N/A Format: hexadecimal Default: 0xFFFFFFFF Indicates the length of delay as cells are transmitted from point A to point B, in hexadecimal notaRange: N/A Format: hexadecimal tion.
Max Cell Tx Delay
Cell Delay Variation Default: 0xFFFFFFFF Indicates the variation in the cell transit delay, in hexadecimal notation. Range: N/A Format: hexadecimal Cell Loss Ratio (0) Default: 0xFFFFFFFF Indicates the cells lost/number of cells sent for the peak cell rate 0 category, in hexadecimal Range: N/A Format: hexadecimal notation. Default: 0xFFFFFFFF Indicates the cells lost/number of cells sent for the peak cell rate 0+1 category, in hexadecimal Range: N/A Format: hexadecimal notation. Default: 0xFFFFFFFF Indicates the difference between the effective bandwidth allocation and the allocation for susRange: N/A Format: hexadecimal tainable cell rate (the safety margin above the sustainable cell rate), in hexadecimal notation. Default: 0xFFFFFFFF Indicates the relative measure of the square root of cell rate margin, normalized by the variance of Range: N/A Format: hexadecimal some of the cell rates of all existing connections, in hexadecimal notation. Default: ClpEqual0 Range: N/A Format: predefined alphanumeric ClpEqual0 ClpEqual0or1 Indicates the cell loss priority for generic connection admission control (GCAC).
Cell Loss Ratio (0+1) Cell Rate Margin
Variance Factor
Gcac CLP
Indicates the GCAC CLP is equal to 0. Indicates the GCAC CLP is equal to 0 or 1

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

The PNNI Route TNS Configuration window is displayed. 3 Enter the values for this window according to the information provided in Table 6-22. 4 After setting all the values on the window, select the Add Route TNS Entry command (or press Ctrl+A). A trap message confirming the configuration application appears at the bottom of the window. 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
Scrolls up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. 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. Searches this table by the values you enter in the Index, Type, Plan, Id, and TNS Index fields.
Release 9.0.0 255-700-447
Find...

Table 6-21. Commands for the PNNI Route TNS Table Window (Continued) Command Function
Add Route TNS Entry Go Back to Previous Screen
Displays the PNNI Route Address Configuration window. Redisplays the PNNI System-Wide Configuration window.
The display fields on this window provide the following information:

Table 6-22. Field Descriptions for the PNNI Route TNS Table Window Field Name Description
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 connection 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 TNS Type TNS Plan TNS Id TNS Index Displays the default five-number value on the PNNI Route TNS Table window. Identifies a logical PNNI entity in the PSAX system. Displays the Transit Network String Type. Indicates the type of network ID of a specified transit network. Displays the Transit Network String Plan. Indicates the network ID plan of a specified transit network. Displays the Transit Network String Identifier. Indicates the value of the Transit Network String identifier. Displays the Transit Network String Index. Indicates the value of the Transit Network String index.
Figure 6-14. PNNI Route TNS Configuration Window PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 6-31


Table 6-23. PNNI Route TNS Configuration Window Command Function
Add Route TNS Entry Delete Route TNS Entry Go Back to Previous Screen
Displays the PNNI Route Address Configuration window. Deletes the route TNS entry. Redisplays the PNNI Route TNS Table.
Table 6-24. Field Descriptions for the PNNI Route TNS Configuration Window Field Name Field Values Route TNS Information Panel Description
PNNI Node Index
Default: 0 Range: 1400 Format: numeric Default: NationalNetworkId Range: N/A Format: Predefined NationalNetworkId Other
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). Indicates the Transit Network String type; the type of network ID of a specfied transit network.
TNS Type
The National Network ID is being used.
A user-defined TNS type is being used. Indicates the network ID plan of a specified transit network.
TNS Plan
Default: CarrierIdCode Range: N/A Format: predefined CarrierIdCode Other
The Carrier ID TNS Plan is being used. User-defined. Indicates the TNS ID.
TNS Id
Default: 0 Range: N/A Format: octets Default: 0 Range: N/A Format: numeric Default: 0 Range: N/A Format: 11 octets Range: N/A Format: numeric
TNS Index
Indicates the TNS Index.
Adv Node Id
Indicates the Advertised node ID.
Lower Left Panel
TNS Intf Index
Indicates the TNS Interface Index
Release 9.0.0 255-700-447

Table 6-24. Field Descriptions for the PNNI Route TNS Configuration Window (Continued) Field Name Field Values Description
Adv Port Id
Indicates the Advertised port identifier. For an SVC endpoint, enter the slot, port, and channel). You can create up to 50 routes manually, to display in the Route Address table. However, more than 50 routes can be displayed by the PSAX system because route addresses are also learned dynamically. The route type being used.
Route Type
Default: Exterior Range: N/A Format: predefined Other Exterior
A user-defined route type. A connection from the advertising node to the address prefix that belongs to an external domain address. Indicates the level of the PNNI hierarchy where the connectivity between the advertising node and the address prefix is located. Indicates whether virtual path connections (VPCs) can be established between the advertising node and the address prefix. Indicates that VPCs can be established between the advertising node and the address prefix. Indicates that VPCs cannot be established between the advertising node and the address prefix. 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 semantics of this metric are determined by the routingprotocol specified in the Address Proto field value of the route. If this metric is not used, enter 1 in this field.
TNS Scope
Default: 0 Range: N/A Format: numeric Default: True Range: N/A Format: predefined True False
VP Capability
Metrics Tag
Default: 0 Range: N/A Format: numeric
Release 9.0.0 6-33

Table 6-24. Field Descriptions for the PNNI Route TNS Configuration Window (Continued) Field Name Field Values Description
Org Advertisement Default: True Range: N/A Format: predefined True
Indicates that the transit network specified by this entry is to be advertised by the local node into its PNNI routing domain. Indicates that the transit network that is specified by this entry is to be advertised by the local node. Set this value if the value of the corresponding instance of PNNI Route Node Protocol is other than PNNI. Indicates the transit network specified by this entry is not to be advertised by the local node into its PNNI routing domain.
False
Lower Right Panel
[Adv Ptse Id]
Default: 0 Range: N/A Format: numeric Default: Mgmt Range: N/A Format: predefined Mgmt
Displays the Advertised PTSE ID.
[TNS Proto]
Displays the local interface over which the advertised node is reachable. Indicates configured manually; for example, by the SNMP or the dynamically as displayed on the console interface. Indicates that the local interface is configured in an unspecified manner. Indicates that the local interface is learned by ILMI (UNI side routing address). Indicates that the local interface is learned by PNNI (as described in the ATM Forum PNNI 1.0 specification). Displays when connectivity became known to the local node.
Other Local Pnni
[Time Stamp]
Default: 00:00:00 Range: N/A Format: Numeric (days, hours, minutes, seconds) Default: Inactive Range: N/A Format: predefined Inactive
[Oper Status]
Displays whether the reachable address prefix is operational and is being advertised by this node. Indicates that the reachable address prefix is not operational and is not being advertised by this node. 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 have connectivity to each other.
Release 9.0.0 255-700-447
Advertised

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 Network Type, 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
Page Up Page Down Top Bottom
Scrolls up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table.
Release 9.0.0 6-35

Table 6-25. Commands for the PNNI Map TNS Table Window (Continued) Command Function
Total: 0/0
The first number in this field indicates the identification number of the TNS table entry on the first line of the currently displayed window. The second number indicates the total number of TNS table entries. Enter the five-digit value for the node to be searched. Enter the 11-octet node address for the node to be searched. Redisplays the PNNI System-Wide configuration window.
Find...Index Index Node ID: Go Back to Previous Screen
View Map TNS Configuration Displays the PNNI Map TNS Configuration window.
The fields on this window are described in Table 6-26.

Table 6-26. Field Descriptions for the PNNI Map TNS Table Field Name Field Values Map TNS InformationPanel Description
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 Default: 0 only) Range: 1400 Format: numeric Advertising Node ID Displays a unique indentifier for this PNNI system node.
Default: 0 Displays the Node ID advertising reachability to the transit network. Range: N/A Format: hexadecimal address Default: 0 Range: N/A Format: 2 octets Displays the Port ID used from the advertising mode to reach the given transit network.
Advertised Port ID
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.
Release 9.0.0 255-700-447

Figure 6-16. PNNI Route TNS Table Window
The PNNI Map TNS Configuration window lists information on six parameters of the selected node address on the Map TNS Table. The table is readonly, as reachable addresses are discovered during dynamic operation of the PNNI protocol, not manually configured. The command on this window performs the following 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 Field Name Field Values Map TNS Information Panel Description
[PNNI Node Index] Default: 0 Range: 1400 Format: numeric [Adv Node Id]
Displays the node index, a logical PNNI entity in the PSAX system.
Default: Displays the 11-octet advertising node identifier. This node is advertising reachability to the transit Range: Format: hexadecimal network. 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).
[Adv Port Id]
Release 9.0.0 6-37

Configuring a Summary Address
Table 6-28. Field Descriptions for the PNNI Map TNS Configuration Window (Continued) Field Name Field Values Description
[TNS Type]
Default: NationalNetworkId Range: Format: Default: CarrierIdCode Range: Format: Default: 0 Range: Format:
Displays the type of network ID used for the transit network.
[TNS Plan]
Displays the type of network ID Plan that the network has been assigned.
[TNS Id]
Displays the value of the transit network identifier.

The 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) 3 Enter the values for this window according to the information provided in Table 6-31. 4 After setting all the values on the window, select Apply Configuration or press Ctrl+A. 5 Select the Create Summary Address Entry command. This entry is added to the PNNI Summary Address Table. A trap message confirming the configuration application appears at the bottom of the window. 6 Type Ctrl+G to return to the Console Interface Main Menu and save the configuration.
End
Release 9.0.0 255-700-447

Figure 6-17. PNNI Summary Address Table Window

Table 6-29. Commands for the PNNI Summary Address Table Window Command Function
Find.. Add Metrics Entry Go Back to Previous Screen
Searches this table by the values you enter in the Node Index, Prefix Length, Summary Type, and Summary Address fields. Displays the PNNI Summary Address Configuration window. Redisplays the PNNI System-Wide Configuration window.
Release 9.0.0 6-39

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 Apply Configuration Delete Summary Address Entry Go Back to Previous Screen
Adds the route address to the PNNI Summary Address Table window. This field is displayed only upon initial summary address configuration. Applies the configuration values you set. Deletes the route address from the PNNI Summary Address Table window. Redisplays the PNNI Summary Address Table window.
Table 6-31. Field Descriptions for the PNNI Summary Address Configuration Window Field Name Field Values Description
Node Index
Displays the node index that identifies a logical PNNI entity in the PSAX system.
Summary Address
Default: 0 Indicates the address prefix of the ATM end sysRange: 120 per node tem. This tells a node how to summarize reachFormat: hexadecimal ability information. A maximum of 20 PNNI summary addresses can be created per node. Default: 0 Range: 0152 Format: numeric Indicates the leading portion of the ATM address.
Address Prefix Length
Release 9.0.0 255-700-447

Viewing ATM PNNI Map Information
Table 6-31. Field Descriptions for the PNNI Summary Address Configuration Window (Continued) Field Name Field Values Description
Summary Address Type
Default: Internal Range: N/A Format: predefined Internal Exterior
Indicates whether address is inside or outside a PNNI routing domain. Denotes that a link, node, or reachable address is inside a PNNI routing domain. Exterior denotes that a link, node, or reachable address is outside a PNNI routing domain Determines whether the summary is advertised within this peer group. True indicates you do not want to advertise summary addresses, enabling the node to reach all the represented end systems and nodes. False indicates you want to advertise addresses that match the reachable address prefix, regardless of scope. Indicates whether or not the summary is currently being advertised by the node within the PSAX system into its peer group. A maximum of 50 routes can be advertised. Indicates the summary address is being advertised by the node within the PSAX system into its peer group. Indicates the summary address is not being advertised by the node within the PSAX system into its peer group.
Suppress Advertise- Default: False ment Range: N/A Format: predefined False
True
[Summary Address Default: AdvertisinState] gActive Range: 150 Format: predefined AdvertisingActive
Inactive

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 managers 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 previously created.
Release 9.0.0 6-41

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 command. 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... Go Back to Previous Screen
Searches this table by the values you enter in the Node Index, Org. Port Id, Map Index, or Org. Node Id fields. Redisplays the PNNI System-Wide Configuration window.
Release 9.0.0 255-700-447

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 connectivity within itself or to other nodes is being described. The Org Port Id is the port identifier of the port as assigned by the originating node, to which the port is attached. The Map Index is an index into the set of link and nodal connectivity associated 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 Go Back to Previous Screen
Displays the PNNI Metrics Configuration window. Displays the PNNI System-Wide Configuration window.
Release 9.0.0 6-43

Table 6-34. Field Descriptions for the PNNI Map Information Window Field Name Field Values Description
[Node Index]
Displays the node index identifies a logical PNNI entity in the PSAX system.
[Org. Node Id]
Default: N/A Displays the Node identifier of the node originating connectivity within itself or to other nodes. Range: N/A Format: hexadecimal Default: N/A Displays the Node identifier at the other end of the link from the originating node. A value of all Range: N/A Format: hexadecimal zeroes means the node identifier is unknown. Default: N/A Range: N/A Format: Numeric Default: N/A Range: N/A Format: Numeric Default: N/A Range: N/A Format: Numeric Default: N/A Range: N/A Format: Numeric Default: N/A Range: N/A Format: Numeric Default: N/A Range: N/A Format: Numeric Displays the Peer group identifier of the originating node and its peers. Displays the Port identifier of the port, as assigned by the originating node, to which the port is attached. 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 identifier is unknown. Displays which links to a given neighbor node are to be aggregated and advertised as a single logical link. Displays a PTSE identifier describing this link or node. 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. Displays the type of PNNI entity.
[Remote Node Id]
[Peer Group Id]
[Org. Port Id]
[Remote Port Id]
[Aggregate Token]
[Ptse Identifier]
[Map Index]
[Map Type]
Default: Horizontal Link Range: N/A Format: Predefined
Release 9.0.0 255-700-447

Viewing ATM PNNI Map Node Information
Table 6-34. Field Descriptions for the PNNI Map Information Window (Continued) Field Name Field Values Description
[VP Capability]
Default: True Range: N/A Format: Predefined True False
Indicates whether virtual path connections (VPCs) can be established across this PNNI entity. VPCs can be established across this PNNI entity. VPCs cannot be established across this PNNI entity. 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.
[Metrics Tag]
Default: N/A Range: N/A Format: Numeric

Perform the following procedure to configure the PNNI map node information.
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed. 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
Release 9.0.0 6-45

Figure 6-21. PNNI Map Node Table Window
The PNNI Map Node Table contains a list of nodes as seen from the perspective 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 commands on this window have the following functions:
Table 6-35. Commands for the PNNI Map Node Table Window Command Function
Find.. Go Back to Previous Screen
Searches this table by the values you enter in the Node Index or Map Node Id fields. Displays the PNNI System-Wide Configuration window.
The display-only fields on this window have the following values:
Release 9.0.0 255-700-447

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 identification 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 connection type. 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. Displays the 11-octet PNNI map node identifier.
Node ID
Default: Range: Format: Default: Range: Format:
PNNI Map Node Id
Figure 6-22. PNNI Map Node Information Window
The PNNI Map Node Information window is read-only, as the update is generated dynamically during operation of the PNNI protocol, not manually configured. The command on this window performs the following function:
Release 9.0.0 6-47

Table 6-38. Field Descriptions for the PNNI Map Node Information Window Field Name Field Values Description
Node Index (display only) Map Node ID (display only) Peer Group ID (display only)
Displays the node index identifies a logical PNNI entity in the PSAX system.
Default: 0 Displays the node whose nodal information is being described. Range: N/A Format: hexadecimal Default: 0 Indicates the first 12 bytes (default) of the ATM address. This value is the combination of the ATM Range: N/A Format: hexadecimal address and the node level. This value is generated and displayed by the system 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. Default: 0 Displays the ATM end system address of the originating node. Range: N/A Format: hexadecimal Default: True Range: T/F Format: predefined Indicates whether the originating node is restricted to only allow support of SVCs originating 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. 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 circumstances. It is free from such restrictions when it is used to originate or terminate a call. Indicates that transit connections are allowed. Indicates the complex node representation, a collection of nodal state parameters that provide detailed state information associated with the logical node. Indicates that the originating node does not use the complex node representation. Indicates that the originating node uses the complex node representation. If the value is True, the spokes and bypasses that make up the complex 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.
ATM Address (display only) Restricted Transit (display only)
True
False Complex Rep (display only) Default: False Range: T/F Format: predefined False True
Release 9.0.0 255-700-447

Table 6-38. Field Descriptions for the PNNI Map Node Information Window (Continued) Field Name Field Values Description
Restricted Branching (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 the originating node. Indicates that additional branches are supported. Indicates that restricted branching is supported. Indicates whether the originating nodes topology database is currently overloaded. This attribute has the same value as the non-transit for PGL election bit in the nodal information group originated by this node. Indicates that the originating nodes topology database is not currently overloaded. Indicates that the originating nodes topology database is currently overloaded. 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. Indicates the originating node does not claim to be the PGL of its peer group. Indicates that the originating node claims to be PGL. Indicates the node ranking in a peer group for the peer group leader position the next time a PGL is needed.
False True Database Overload (display only) Default: False Range: T/F Format: predefined
False True I Am Leader (display only) Default: False Range: T/F Format: predefined
False True Leadership Priority Default: 0 Range: N/A Format: numeric Preferred Pgl (display only)
Default: 0 Displays the node that the originating node believes should be or is peer group leader (PGL) Range: N/A Format: hexadecimal of its peer group. If the originating node has not chosen a preferred PGL, this value is set to 0. Default: 0 Displays the node ID of the parent logical group node (LGN) when the originating node is a peer Range: N/A Format: hexadecimal 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.
Parent Node ID (display only)
Release 9.0.0 6-49

Viewing ATM PNNI Map Address Information
Table 6-38. Field Descriptions for the PNNI Map Node Information Window (Continued) Field Name Field Values Description
Parent ATM Address (display only)
Default: 0 Displays the ATM address of the parent LGN when the originating node is a peer group leader. Range: N/A Format: hexadecimal 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. Default: 0 Displays the nodes parent peer group ID when Range: user-defined the originating node is a peer group leader. If the Format: hexadecimal 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 Peer Group ID (display only)
Parent Pgl Node ID Default: 0 Displays the node elected as peer group leader of (display only) Range: user-defined the parent peer group when the originating node Format: hexadecimal 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.

Begin
1 From the PNNI System-Wide Configuration window, select the PNNI 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 reachable addresses are discovered during dynamic operation of the PNNI protocol, not manually configured.
End
Release 9.0.0 255-700-447

Figure 6-23. PNNI Map Address Table Window

Table 6-39. Commands for the PNNI Map Address Table Window Command Function
Find..
Searches this table by the values you enter in the Node Index, Advertised Node Id, Advertised Port Id, and Address Index fields. Redisplays the PNNI System-Wide Configuration window.
The descriptions for the display-only fields on this window are provided in Table 6-42:
Table 6-40. Field Descriptions for the PNNI Map Address Table Window Field Name Description
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 connection table entries for this connection type. Displays default five-digit value on the Node Table window. The default node identifier of a logical PNNI entity in the PSAX system. Displays the hexadecimal address (11 octets). Displays the port identifier of the advertising node. Displays the address index (up to 5 digits).
Node index
Advertising Node Identifier Advertising Port Id Addr. Index
Release 9.0.0 6-51

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

Table 6-42. Field Descriptions for the PNNI Map Address Entry Window Field Name Field Values Description
[Node Index]
Default: N/A Range: 1400 Format: numeric Default: N/A Range: N/A Format: numeric Default: N/A Range: N/A Format: numeric
Displays the node index that identifies a logical PNNI entity in the PSAX system. Displays the node ID of a node advertising reachability to the address prefix. Displays the port identifier the advertising node uses to reach the given address prefix.
[Adv. Node Id]
[Adv. Port Id]
Release 9.0.0 255-700-447

Viewing the ATM PNNI Link Table
Table 6-42. Field Descriptions for the PNNI Map Address Entry Window (Continued) Field Name Field Values Description
[Address Index]
Default: N/A Range: N/A Format: numeric Default: N/A Range: N/A Format: numeric 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. Displays the ATM end system address prefix.
[Map Address]
[Prefix Length]
Displays the prefix length to be applied to the ATM end system address prefix.

The PNNI Link Table window contains the attributes necessary to describe the operation of logical links attached to the PSAX system and the relationship with the neighbor nodes on the other end of the links. Links are attached to a specific node within the PSAX system. Links represent horizontal 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
1 From the PNNI System-Wide Configuration window, select the PNNI 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 Previous Screen command.
Release 9.0.0 6-53

The PNNI Link Table window is displayed (see Figure 6-25).

End
Figure 6-25. PNNI Link Table Window
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. The commands in this window have the following functions:
Table 6-43. Commands for the PNNI Link Table Window Command Function
Find.. Go Back to Previous Screen
Searches this table by the values you enter in the Node Index or the PNNI Link Port Id fields. Redisplays the PNNI System-Wide Configuration window.
Release 9.0.0 255-700-447

Figure 6-26. PNNI Link Information Window
The command in this window has the following function:

Table 6-44. Commands for the PNNI Link Information Window Command Function
Go Back to Previous Screen Redisplays the PNNI System-Wide Configuration window.

Table 6-45. Field Descriptions for the PNNI Link Configuration Window Field Name Field Values Description
[Node Index]
Default: 0 Range: 1400 Format: numeric Default: N/A Range: N/A Format: numeric
Displays the node index that identifies a logical PNNI entity in the PSAX system. 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.
[Link Port Id]
Release 9.0.0 6-55

Table 6-45. Field Descriptions for the PNNI Link Configuration Window (Continued) Field Name Field Values Description
[Link Version]
Default: Version1p oint0 Range: N/A Format: predefined alphanumeric Version1point0 Unknown
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. Indicates PNNI Version 1.0 is being used. 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. Displays the type of link being described.
[Link Type]
Default: LowestLevelHorizontalLink Range: networkdependent Format: predefined alphanumeric Unknown
Indicates that the link type is unknown.
LowestLevelHori- Indicates that this link is the logical link between lowest zontalLink nodes in the same peer group. HorizontalLinkTo- Indicates that this link is the logical link between logical FromLgn group nodes (LGNs) in the same peer group. LowestLevelOutsideLink Uplink Indicates that this link is the logical link between the lowest nodes in the same peer group. 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. Indicates that this link is the logical link between two border nodes, and the border nodes represent an upnode; that is, this link is the outside link to another network and uplink. Displays one of the possible conditions that characterize Hello types and the node states that the Hellos originated from. 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.
OutsideLinkAndUplink
[Link Hello State]
Default: N/A Range: N/A Format: Predefined Down
Release 9.0.0 255-700-447

Attempt
Indicates either no Hellos or Hellos with mismatch information 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 period Hello Interval. 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 neighbors Hellos were set to 0. 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 transmitted 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. 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 neighbors 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. 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. Indicates whether a common level of the routing hierarchy has been found, in addition to achieving full bidirectional communication between the two nodes. Links that have reached the CommonOutside state can be advertised in PTSEs as uplinks to the upnode.
OneWayInside
TwoWayInside
OneWayOutside
TwoWayOutside
CommonOutside
[Remote Node Id]
Default: N/A Displays the node identifier of the node at the remote end of the link.. Range: N/A Format: hexadecimal
Release 9.0.0 6-57

[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 OutsideLinkAndUplink is displayed in the Link Type field, this is the port identifier assigned by the lowest-level neighbor 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. 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. Displays the node identifier of the upnode (the neighbor nodes identity within the common peer group) for outside links and uplinks. When the upnode, horizontal links, or link type is not yet known, this field is set to 0.
[Derived Agg. Token] [Upnode Id]
[Upnode ATM Address]
Default: N/A Displays the ATM end system address used to establish connections to the upnode for outside links and uplinks. Range: N/A Format: hexadecimal When the upnode, horizontal links, or link type is not yet known, this field is set to 0. 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. Displays the value of this object, which identifies the switched virtual channel connection (SVCC)-based routing control channel (RCC) for which the entry contains management information. 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 HorizontalLinkToFromLgn or Uplink is displayed in the Link Type field, this field is set to 0. Displays the number of hello packets transmitted over this link for horizontal and outside links between lowestlevel nodes and for links of unknown type. If HorizontalLinkToFromLgn or Uplink is displayed in the Link Type field, this field is set to 0.
[Common Peer Gp Id]
[Svcc Rcc Index] Default: N/A Range: N/A Format: numeric Rcv Hellos (display only) Default: N/A Range: N/A Format: numeric
[Transmit Hellos] Default: N/A Range: N/A Format: numeric
Release 9.0.0 255-700-447

Viewing ATM PNNI SVCC RCC Information

Begin
1 On the Console Interface Main Menu, select the Site-Specific Configuration option and press Enter (or press Ctrl+P). The Site-Specific Menu is displayed. 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 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
Page Up Page Down Top
Scroll up one page. Scrolls down one page. Displays entries at the top of the table.
Release 9.0.0 6-59

Table 6-46. Commands for the PNNI SvccRcc Table Window (Continued) Command Function
Bottom Total: 0/0
Displays entries at the bottom of the table. The first number in this field indicates the identification number of the SvccRcc Table entry on the first line of the currently displayed window. The second number indicates the total number of SvccRcc Table entries. Enter the five-digit value for the node to be searched. Enter the single-octet node adress to be searched. Redisplays the PNNI System-Wide configuration window.
Find...Node Index PNNI SvccRcc Index Go Back to Previous Screen
The display fields on this window have the following values:

Table 6-47. Field Descriptions for the PNNI SVCC RCC Table Window Field Name Description
Node Index (display only) PNNI Svcc Rcc Index
The node index identifies a logical PNNI entity in the PSAX system. 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. 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. 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.
VPI
VCI
Release 9.0.0 255-700-447

Figure 6-28. PNNI SVCC RCC Information Window

Table 6-48. Commands for the PNNI SVCC RCC Information Window Command Function
ATM Security Statistics Go Back to Previous Screen
Displays the ATM PNNI SVCC RCC Security Statistics window Redisplays the PNNI SvccRcc Table window.
Table 6-49 describes the display fields on this window.:

Table 6-49. Field Descriptions for the PNNI SVCC RCC Information Window Field Name Field Values Description
[Node Index]
Displays the node index identifies a logical PNNI entity in the PSAX system. Displays the 5-digit switched virtual channel connection routing control channel (SvccRcc) index number.
[Svcc Rcc Index]
[Svcc Rcc Version]
Default: Version1poi Displays the PNNI version 1.0 routing protocol nt0 that is used to exchange information with the neighbor node. Range: N/A Format: Predefined
Release 9.0.0 6-61

Viewing the ATM PNNI Neighbor Peer Table
Table 6-49. Field Descriptions for the PNNI SVCC RCC Information Window (Continued) Field Name Field Values Description
[Svcc Hello State]
Default: TwoWayIn- Displays the state of the Hello protocol exchange side over the SVCC-based RCC. Range: N/A Format: Predefined Default: 0 Range: N/A Format: 11-octet remote node address identifier Default: 0 Range: N/A Format: 10-octet address of remote ATM device Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Displays the remote node where the SVCC-based RCC terminates.
[Remote Node Id]
[Remote ATM Address]
Displays the ATM end system address where the SVCC establishment was attempted.
[SvccRcc If Index]
Displays the interface from which the SVCCbased RCC leaves the PSAX system. If the SVCCbased RCC has not been established, the default value is displayed. Displays the number of received Hello packets over this SVCC-based RCC. Displays the number of transmitted Hello packets over this VCC-based RCC. Displays the VPI 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. 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.
[Rcv Hellos]
[Transmit Hello]
[Vpi]
[Vci]

The PNNI Neighbor Peer Table window contains all the attributes necessary to describe the relationship a node in the PSAX system has with a neighboring 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.

Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed. 2 Select the PNNI System-Wide Configuration option. The PNNI System-Wide Configuration window is displayed. 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
Figure 6-29. PNNI Neighbor Peer Table Window
The PNNI Neighbor Peer Table window displays the node index and neighbor peer remote node index for various neighbor peers.
Release 9.0.0 6-63

The PNNI Neighbor Peer Remote Node Id field is the node identifier of the neighboring peer node. The commands in this window have the following functions:
Table 6-50. Commands for the PNNI Neighbor Peer Table Window Command Function
Find... Go Back to Previous Screen
Searches this table by the values you enter in the Node Index or Rem. Node Id fields. Displays the PNNI System-Wide Configuration window.
Figure 6-30. PNNI Neighbor Peer Information Window
The command in this window has the following function:

Table 6-51. Command for the PNNI Neighbor Peer Information Window Command Function
Redisplays the PNNI System-Wide Configuration window.
Release 9.0.0 255-700-447

Table 6-52. Field Descriptions for the PNNI Neighbor Peer Configuration Window Field Name Field Values Description
[Node Index]
Default: N/A Range: 1400 Format: numeric
Displays the node index that identifies a logical PNNI entity in the PSAX system. Displays the Node identifier of the neighboring peer node. Displays the state of this node's neighboring peer state machine associated with the neighbor peer remote node ID. 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 associated with the neighboring peer. 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. 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. 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. 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 advertised in PTSEs. 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.
[NbrPeer Rem Node Default: N/A Id] Range: Format: numeric [NbrPeer State] Default: Npdown Range: N/A Format: predefined alphanumeric Npdown
Negotiating
Exchanging
Loading
Full
[NbrPeer Svcc Rcc Index]
Default: N/A Range: N/A Format: numeric
Release 9.0.0 6-65

Viewing the ATM PNNI Neighbor Peer Port Table
Table 6-52. Field Descriptions for the PNNI Neighbor Peer Configuration Window (Continued) Field Name Field Values Description
[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 neighboring peer only communicates via an SVCC-based RCC, the value of this field is set to zero. Otherwise it is set to the total number of ports to the neighboring peer in the Hello state two-way inside. Displays a count of the number of database summary packets received from the neighboring peer. Displays a count of the number of database summary packets transmitted to the neighboring peer. Displays a count of the number of PNNI topology state packets (PTSPs) received from the neighboring peer. Displays a count of the number of PTSPs retransmitted to the neighboring peer. Displays a count of the number of PNNI topology state element (PTSE) request packets received from the neighboring peer. Displays a count of the number of PTSE request packets transmitted to the neighboring peer. Displays a count of the number of PTSE acknowledgement packets received from the neighboring peer. Displays a count of the number of PTSE acknowledgement packets transmitted to the neighboring peer.
[NbrPeer Rcv DbSums) [NbrPeer Xmt DbSums)
[NbrPeer Rcv Ptsps] Default: N/A Range: N/A Format: numeric [NbrPeer Xmt Ptsps] [NbrPeer Rcv Ptse Req] [NbrPeer Xmt Ptse Req] [NbrPeer Rcv Ptse Ack] [NbrPeer Xmt Ptse Ack] Default: N/A Range: N/A Format: numeric Default: N/A Range: N/A Format: numeric Default: N/A Range: N/A Format: numeric Default: N/A Range: N/A Format: numeric Default: N/A Range: N/A Format: numeric

Begin
1 On the Console Interface Main Menu, select the Site-Specific Configuration option or press Ctrl+P. The Site-Specific Menu is displayed. 2 Select the PNNI System-Wide Configuration option or press Ctrl+N.

The PNNI System-Wide Configuration window is displayed. 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 Port Table by a search using the Find command or by selecting an entry on the table and and pressing Enter.
End
Figure 6-31. PNNI Neighbor Peer Port Table Window
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 lowest-level nodes. For more information, see the ATM Forum Specification, Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni0055.000, Section 5.7.1 Port ID List. The commands on this window perform the following functions:
Table 6-53. Commands for the PNNI Neighbor Peer Port Table Window Command Function
Scroll up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table.
Release 9.0.0 6-67

Viewing ATM PNNI PTSE Information
Table 6-53. Commands for the PNNI Neighbor Peer Port Table Window (Continued) Command Function
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 displayed window. The second number indicates the total number of peer port table entries. Enter the five-digit value for the node to be searched. Enter the 10-digit port ID to be searched. Enter the 11-octet ID address of the remote node to be searched. Redisplays the PNNI System-Wide configuration window.
Find...Node Index Port Id Rmt. Node Id: Go Back to Previous Screen
The display fields on this window have the following values as described in Table 6-54:
Table 6-54. Field Descriptions for the PNNI Neighbor Peer Port Table Window Field Name Field Values Description
Node Index (display only)
Default: N/A Range: 1400 Format: numeric
PNNI Neighbor Peer Default: N/A Displays the Node identifier of the neighboring Port Remote Node Range: N/A peer node. Id Format: hexadecimal Port ID (display only) Flood Stat. (display only) Default: N/A Range: N/A Format: Numeric 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. Displays whether the port is being used for transmission of flooding and database synchronization information to the neighboring peer.

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 nodes topology database. For more information, see the ATM Forum Specification, Private Network-Network Interface (PNNI 1.0) Specification Version 1.0, af-pnni0055.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
1 From the PNNI System-Wide Configuration window, select the PNNI PTSE Information command or press Ctrl+E.

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 provided in Table 6-58.
End
Figure 6-32. PNNI PTSE Table Window
The commands on this table perform the following functions:

Table 6-55. Commands for the PNNI PTSE Table Window Command Function
Scrolls up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. 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. Enter the five-digit ID for the node to be searched. Enter the 10-digit PTSE ID to be searched.
Find...Node Index Ptse Id
Release 9.0.0 6-69

Table 6-55. Commands for the PNNI PTSE Table Window (Continued) Command Function
Org. Node Id: Go Back to Previous Screen
Enter the 11-octet organizational node ID address to be searched. Redisplays the PNNI System-Wide configuration window.
Table 6-56. Field Descriptions for the PNNI PTSE Table Window Field Name Description
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. Displays the 5-digit node index of the table entries. Displays the 11-octet PNNI PTSE Originating Node ID. ID of the PTSE.
Node Index PNNI PTSE Originating Node Id PTSE Id
Figure 6-33. PNNI PTSE Information Window

Release 9.0.0 255-700-447

Table 6-58. Field Descriptions for the PNNI PTSE Information Window Field Name Field Values Description
Node Index (display only) Originating Node ID (display only)
Default: N/A Displays the 20-octet node identifier of the node that originated the PTSE. Range: N/A Format: Hexadecimal Default: N/A Range: N/A Format: Numeric Displays the value of the PTSE identifier assigned to the PTSE by its originator. Describes the architecture parameters set selected. User defined.
Type (display only)
Default: Other Range: N/A Format: Predefined Other
NodalState Param- Indicates that the nodal state parameter informaeters 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 An internal reachable address is an address of a Addresses destination that is directly attached to the logical node that advertises the address. Exterior Reachable An exterior reachable address is an address that Addresses can be reached through a PNNI routing domain but is not located in that PNNI routing domain. HorizontalLinks Uplinks A horizontal link is between nodes in the same peer group. An uplink is connectivity from a border node to an upnode at a higher level in the PNNI hierarchy.
Release 9.0.0 6-71

Viewing ATM PNNI System Statistics
Table 6-58. Field Descriptions for the PNNI PTSE Information Window (Continued) Field Name Field Values Description
Sequence Number (display only) Checksum (display only) Lifetime (display only)
Default: N/A Range: N/A Format: Numeric Default: N/A Range: N/A Format: Numeric 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 database. Displays the value of the PTSE checksum as it appears in the local topology database. Displays the value of the remaining lifetime for the given PTSE as it appears in the local topology database.

To view PNNI system statistics, perform the following procedure.
Begin
1 On the Console Interface Main Menu, select the Site-Specific Configuration option, and press Enter. The Site-Specific Menu is displayed. 2 Select the PNNI System-Wide Configuration option, and press Enter. The PNNI System-Wide Configuration window is displayed. 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
Release 9.0.0 255-700-447

Figure 6-34. PNNI System Statistics Screen Window

Table 6-59. Commands for the PNNI System Statistics Screen Window Command Function
Continuous Update Go Back to Previous Screen
Updates the values in the fields on this window continuously. Use this command as a toggle switch to view the statistics. Redisplays the PNNI System-Wide Configuration window.
Release 9.0.0 6-73

Table 6-60. Field Descriptions for the PNNI System Statistics Window Field Name Values Description
[Dtl Count Origina- Default: 0 tor] 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 messages. This includes the initial DTL stacks computed by the PSAX system and those for any alternate route. DTL stacks computed by the PSAX system in response to crankbacks. The number of partial DTL stacks that the PSAX system has added into signaling messages as an entry border node. This includes the initial partial 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. 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. 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 crankbacks for which the PSAX system was not the crankback destination. Only those crankbacks that were directed to the PSAX system are counted here. The total number of alternate DTL stacks that the PSAX system has computed and placed into signaling messages as the DTL originator. The total number of alternate partial DTL stacks that the PSAX system has computed and placed into signaling messages as an entry border node. The total number of times where the PSAX system 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. The total number of times where the PSAX system 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 border routing failure.
[Dtl Count Border] Default: 0 Range: N/A Format: numeric
[Crankback Count Org.]
Default: 0 Range: N/A Format: numeric Default: 0 Range: N/A Format: numeric
[Crankback Count Border]
[AltRoute Count Org.] [AltRoute Count Border] [Route Fail Count Org.]
Default: 0 Range: N/A Format: numeric Default: 0 Range: N/A Format: numeric Default: 0 Range: N/A Format: numeric
[Route Fail Count Border]
Release 9.0.0 255-700-447

Table 6-60. Field Descriptions for the PNNI System Statistics Window (Continued) Field Name Values Description
[Route Fail Unreach Default: 0 Org.] Range: N/A Format: numeric
The total number of times where the PSAX system failed to compute a viable DTL stack as the DTL originator because the destination was unreachable, that is, calls that were cleared with the message specified transit network unreachable or the message destination unreachable in the cause incoming exclusion (IE). The total number of times where the PSAX system 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. The number associated with the route node from which the statistics on this window are being generated. The number associated with the route address from which the statistics on this window are being generated.
[Route Fail Unreach Default: 0 Border] Range: N/A Format: numeric
[Route Node Num- Default: 0 ber] Range: N/A Format: numeric [Route Addr Number] Default: 0 Range: N/A Format: numeric
Release 9.0.0 6-75

Release 9.0.0 255-700-447
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 broadband 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-Specific Configuration option. The Site-Specific Menu window is displayed (see Figure 7-1). 2 On the Site-Specific Menu window, select the ATM Trunking Configuration option. The ATM Trunking Local Node Configuration window (see Figure 7-2) is displayed.
Release 9.0.0 7-1
Chapter 7 Configuring ATM Trunking

3 Enter values for the fields on this window according to the information provided in Table 7-2. 4 To apply the configuration values, select the Apply Configuration command. 5 Select the Bring Admin Status Up command to bring the administrative 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 WindowATM Trunking Configuration Option Selected
Release 9.0.0 255-700-447

Figure 7-2. ATM Trunking Local Node Configuration Window

Table 7-1. Commands for the ATM Trunking Local Node Configuration Window Command Function
Apply Configuration Bring Admin Status Up Bring Admin Status Down
Applies the values you set on this window. Enables the transmission of calls between the configured local IWF node and the remote IWF nodes. Disables the transmission of calls between the local IWF node and the remote IWF nodes while preserving local and remote node configuration settings. 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. Displays the ATM Trunking Remote IWF Table window. Displays the ATM Trunking Broadband Routing Table window. Displays the ATM Trunking Narrowband Routing Table window. Redisplays the Site-Specific Menu window.
Delete Node
Go to Remote IWF Table Go to Broadband Routing Table Go to Narrowband Routing Table Go Back to Site-Specific Menu
Release 9.0.0 7-3

Configuring a Remote IWF Node
Table 7-2. Field Descriptions for the ATM Trunking Local Node Configuration Window Field Name Field Values Description
Local IWF ID
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 local IWF; the MSC is the remote. Specifies the IWF ATM address for the local endpoint. Type an address in hexadecimal format up to 20 bytes (160 bits) long (10 groups of 4 characters each). Wireless Applications: The Cell Site and MSC must have different addresses. 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. Specifies whether the local IWF is active.
ATM Address
Default: 0 Range: N/A Format: valid dotted quad
Max Remote IWF
[Admin Status]
Default: Down Range: N/A Format: predefined alphanumeric Up Down
Indicates that the local IWF is active. Indicates that the local IWF is inactive.

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 (see Figure 7-3).Select the Add Remote IWF Entry command. The ATM Trunking Remote IWF Configuration window (see Figure 7-4) is displayed. 3 Enter values for the fields on this window according to the information provided in Table 7-6. 4 Select the Add Configuration command.
Release 9.0.0 255-700-447

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 administrative status of the remote IWF you just added into service. 6 To return to the ATM Trunking Remote IWF Table window to add additional signaling VCC IDs, press Ctrl+B. 7 Repeat Steps 25 to add additional remote IWF nodes (up to a maximum of 100 per PSAX system).
End
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. Displays the ATM Trunking Remote IWF Configuration window. Redisplays the ATM Trunking Local Node Configuration window.
Add Remote IWF Entry Go Back to Previous Screen
Release 9.0.0 7-5

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 Field Name Description
Rmt IWF ID (display only) Remote IWF Address (display only) Total: 0/0
This column displays all the remote IWF IDs in the PSAX system. This column displays all the corresponding ATM remote IWF ID addresses in the PSAX system. 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 Update Configuration Bring Admin Status Up
Applies the values you set on this window. This command is not currently supported. When the value in the [Admin Status] field is Down, brings the remote IWF node to the status Up.
Release 9.0.0 255-700-447

Table 7-5. Commands for the ATM Trunking Remote IWF Configuration Window (Continued) Command Function
Bring Admin Status Down Delete and Return Go to Sig VCC Table
When the value in the [Admin Status] field is Up, brings the remote IWF node to the status Down. Deletes the remote IWF node that is not in service. Displays the ATM Trunking Sig VCC Table window. This command is displayed only after you have added a remote IWF ID. Displays the ATM Trunking Bearer VCC Table window. This command is displayed only after you have added a remote IWF ID. Displays the ATM Trunking Data Channel Table window. This command is displayed only after you have added a remote IWF ID. Redisplays the ATM Trunking Remote IWF Table window.
Go to Bearer VCC Table
Go to Data Channel Table
Table 7-6. Field Descriptions for the ATM Trunking Remote IWF Configuration Window Field Name Field Values Description
Remote IWF ID
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 Configuration window. Wireless Applications: You are limited in the number of remote IWFs by the values configured on the Call Control Resource Configuration window.
Remote IWF ATM Address
Default: 0 Specifies the IWF ATM address for the remote endpoint. Type an address in hexadecimal format Range: N/A Format: hexadecimal 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. Default: Switched Range: N/A Format: predefined alphanumeric Switched Non-switched Specifies whether the remote IWF trunk is in switched mode or non-switched mode. Currently only the nonswitched mode is supported. Indicates that the specified signaling VCC is used for the connection trunk. Indicates that no signaling is used for the connection trunk. Wireless Applications: If configuring a cell site with an MSC, select this value.
Remote IWF Trnk Mode (display only)
Release 9.0.0 7-7

Adding a Signaling VCC Identifier
Table 7-6. Field Descriptions for the ATM Trunking Remote IWF Configuration Window (Continued) Field Name Field Values Description
Remote IWF MAX Call Rate
Default: 60 Range: 14096 Format: Numeric (Calls per second) Default: A-law Range: N/A Format: predefined alphanumeric A-law U-law None
Indicates the maximum number of new calls per second within this remote IWF. This field value is used to estimate the bandwidth resource requirement for an unconfigured SVC SIG VCC. Indicates the type of PCM encoding performed on the bearer VCC.
Remote IWF PCM Encoding
Indicates that the traffic on the bearer VCC is encoded as A-law traffic. Indicates that the traffic on the bearer VCC is encoded as U-law traffic. Indicates that PCM encoding is not performed on the bearer VCC. Specifies whether the remote IWF is active.
[Admin Status]
Default: Up Range: N/A Format: predefined alphanumeric Up Down
Indicates that the remote IWF is active. Indicates that the remote IWF is inactive.

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). 3 Enter values in the fields on this window according to the information provided in Table 7-10. 4 Select the Apply Configuration command. The following message in displayed in the status line of the window:
5 To return to the ATM Trunking Sig VCC Table window to add additional signaling VCC IDs, press Ctrl+B.
Release 9.0.0 255-700-447

6 Repeat Steps 25 to add additional signaling VCC IDs.

End
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 Go Back to Previous Screen Find Rmt IWF ID: VCC ID:
Displays the ATM Trunking Sig VCC Configuration window. Redisplays the Remote IWF Configuration window. 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.
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.
Release 9.0.0 7-9

Table 7-8. Field Descriptions for the ATM Trunking Sig VCC Table Window Field Names Description
Rmt IWF ID VCC ID Out Intf ID Out VPI Out VCI Total: 0/0
This column displays all the remote IWF IDs in the PSAX system. This column displays all the corresponding VCC IDs, which are assigned by the owners of the signalling VCC. This column displays all the corresponding interface identifier of the outgoing interfaces. This column displays all the corresponding VPIs for the outgoing interfaces. This column displays all the corresponding VCIs for the outgoing interfaces. 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. The ATM Trunking Sig VCC Configuration window (see Figure 7-6) is displayed.
Figure 7-6. ATM Trunking Sig VCC Configuration Window

Table 7-9. Commands for the ATM Trunking Sig VCC Configuration Window Command Function
Apply Configuration Update Configuration
Applies the values you set on this window. Updates the status display in the Oper Status field.
Release 9.0.0 255-700-447

Table 7-9. Commands for the ATM Trunking Sig VCC Configuration Window (Continued) Command Function
Delete and Return Go Back to Previous
Deletes the remote IWF node that is not in service. Redisplays the ATM Trunking Sig VCC Table window.
Table 7-10. Field Descriptions for the ATM Trunking Sig VCC Configuration Window Field Name Field Values Description
[Remote IWF ID]
Default: Userassigned Range: N/A Format: Numeric Default: 0 Range: 016383 Format: Numeric Default: 00/00/00 Range: N/A Format: SS/PP/CC Default: SVC Range: N/A Format: Predefined alphanumeric SVC SPVC PVC
Remote IWF identifier for the remote endpoint.
Sig VCC ID
Virtual channel connection identifier, which is assigned by the owner of the signaling VCC. 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 connection types. Specifies the connection type that is used for the signaling VCC ID.
[Out Interface ID]
VCC Conn Type
Indicates the connection type for the trunk is an SVC. Indicates the connection type for the trunk is an SPVC. Indicates the connection type for the trunk is a PVC. Virtual path identifier and virtual channel connection identifier for the outgoing interface. This field is editable only for the PVC connection type. This field is display only for SVC and SPVC connection types. Inactive time period allowed to clear the call.
[Out VPI/VCC ID]
Default: 0 / 0 Range: 04095 (VPI); 065535 (VCC) Format: Numeric Default: 3600 Range: N/A Format: Numeric Default: Other Range: N/A Format: Predefined alphanumeric Other Pss1 Dss1 Dpnss
Inactive Time Period Signaling
Specifies the type of signaling protocol used between the local and remote IWFs. At the present time, both ends of the connection must be on a PSAX system. Indicates that ATM 4.0 signaling is used. This value is not currently supported. This value is not currently supported. This value is not currently supported.
Release 9.0.0 7-11

Table 7-10. Field Descriptions for the ATM Trunking Sig VCC Configuration Window (Continued) Field Name Field Values Description
Fwd/Bwd PCR (cps)
Default: 0 / 0 Range: N/A Format: Numeric (cells per second) Default: 0 / 0 Range: N/A Format: Numeric (cells per second) Default: 0 / 0 Range: N/A Format: Numeric (cells) Default: 255 Range: N/A Format: Numeric
Forward and backward peak cell rate (cells per second) for the connection.
Fwd/Bwd SCR (cps)
Forward and backward sustained cell rate (cells per second) for the connection.
Fwd/Bwd MBS (cells)
Forward and backward maximum burst size (cells) for the connection.
Max AAL2 VCC
Maximum number of bearer VCCs controlled by the signaling VCC. Number of active bearer VCCs controlled by the signaling VCC. Virtual identifier to associate with the egress side of the A to B connection. Virtual UNI identifier to associate with the egress side of the A to B connection. Indicates whether the signaling VCC owner is the local 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. The signaling VCC owner is the local IWF. The signaling VCC owner is the remote IWF.
[Active AAL2 VCC] Default: 1 Range: N/A Format: Numeric Egress VIB Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: Local Range: N/A Format: Predefined alphanumeric Local Remote
Egress VUNIB
[Sig VCC Owner]
Release 9.0.0 255-700-447

Adding a Bearer VCC Identifier
Table 7-10. Field Descriptions for the ATM Trunking Sig VCC Configuration Window (Continued) Field Name Field Values Description
[Oper Status]
Default: Idle Range: N/A Format: Predefined alphanumeric Idle OutOfService Init Connecting Active Release
Displays the operational status of the local IWF.
Indicates that the connection is not operational. Indicates that the PVC connection is not operational. Indicates that the connection is being initiated. Indicates that the connection is being connected but layer 2 is not yet operational. Indicates that the connection is operational and is transmitting traffic. Indicates that the connection is being released. Indicates the time in seconds that the PSAX system 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 immediately. Indicates the number of times that the PSAX system attempting to establish the ATM Trunking Signalling VCC SPVC connection. A value of 0 indicates an unlimited number of attempts. Indicates whether the active SVC connection is released, if necessary, and a new connection setup procedure takes place. Indicates that the PSAX system will restart the SPVC connection. Indicates that the PSAX system will not restart the SPVC connection. Indicates the number of failed attempts to establish the connection. This field resets to 0 whenever a connection is successfully established or the ATM Trunking Signalling VCC SPVC connection is restarted.
Retry Timer
Default: 30 Range: N/A Format: Seconds
Retry Limit
Default: 0 Range: N/A Format: Numeric Default: Restart Range: N/A Format: Predefined Restart Noop
Restart
Retry Counter
Default: 0 Range: N/A Format: Numeric

Begin
1 On the ATM Trunking Remote IWF Configuration window, select the Go to Bearer VCC Table command.

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. 3 Enter values in the fields on this window according to the information provided in Table 7-14. 4 Select the Apply Configuration command. The following message in displayed in the status line of the window:
5 To return to the ATM Trunking Bearer VCC Table window to add additional bearer VCC IDs, press Ctrl+B. 6 Repeat Steps 25 to add additional bearer VCC IDs.
End
Figure 7-7. ATM Trunking Bearer VCC Table Window
Release 9.0.0 255-700-447

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. Displays the ATM Trunking Bearer VCC Configuration window.
Add Bearer VCC Entry
Go Back to Previous Screen Redisplays the Remote IWF Configuration window. The fields on this window are described in Table 7-12.
Table 7-12. Field Descriptions for the ATM Trunking Bearer VCC Table Window Field Names Description
Rmt IWF ID VCC ID Sig VCC ID Intf ID VPI VCI Total: 0/0
This column displays all the remote IWF IDs in the PSAX system. This column displays all the corresponding bearer VCC identifiers. This field is not currently supported. This column displays the corresponding signalling VCC identifiers. This column displays all the corresponding VCC interface identifiers. This column displays all the corresponding VPIs for the bearer channels. This column displays all the corresponding VCIs for the bearer channels. 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-8. ATM Trunking Bearer VCC Configuration Window PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 7-15


Table 7-13. Commands for the ATM Trunking Bearer VCC Configuration Window Command Function
Add Configuration Delete Configuration Restart Connection Display Next Connection Continuous Update Configure DSP Parameters
Applies the values you set on this window. Deletes the configuration. Restarts the connection. Displays the next connecion. Continuously update the window data. 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 Take Out of Service Go Back to Previous Screen
Brings the specified ATM trunk bearer VCC into service. Takes the specified ATM trunk bearer VCC out of service. Redisplays the ATM Trunking Bearer VCC Table window.
Table 7-14. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window* Field Name Field Values Description
Remote IWF ID
Default: Userassigned Range: N/A Format: Numeric Default: 0 Range: 04096 Format: Numeric Default: 0 Range: N/A Format: Numeric
Displays the remote interworking function (IWF) identifier for the remote endpoint. This value is automatically assigned based on the previously selected remote IWF ID. Specifies the ATM Trunk bearer VCC ID. Wireless backhaul applications: For connections between active (local) Cell Sites and passive (remote) MSCs, use the same ID number per trunk in the IMA link. Displays the identifier of the signaling VCC.
ATM Trnk Br VCC ID
[Sig VCC ID]
Release 9.0.0 255-700-447

Adding a Bearer VCC Identifier Table 7-14. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window* (Continued) Field Name Field Values Description
Service Type
Default: Cbr-1 Specifies the service type for the connection. Range: N/A For any CBR type selected, the CAC only allows 1 DS0 Format: Predefined 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 Cbr-2 Cbr-3 Cbr-4 Ubr Vbr-nrt2 Vbr-nrt1 Vbr-rt2 Vbr-rt1 Vbr-express Indicates contant bit rate, priority 1. Indicates contant bit rate, priority 2. Indicates contant bit rate, priority 3. Indicates contant bit rate, priority 4. Indicates unspecified bit rate. Indicates variable bit rate, nonreal time, queue 2 Indicates variable bit rate, nonreal time, queue 1 Indicates variable bit rate, real time, queue 2 Indicates variable bit rate, real time, queue 1 Indicates variable bit rate, express.
SAR Type
Default: Aal2 Specifies the segmentation and reassembly type for the connection. Range: N/A Format: Predefined Aal2 Indicates that compressed, connection-oriented, delaysensitive VBR traffic will be transmitted on this connection. 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. Indicates that uncompressed, connection-oriented, timesensitive CBR traffic will be transmitted on this connection. 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. 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, Vbrnrt1, Vbr-rt2, Vbr-rt1, Vbr-express.
Aal1
Fwd/Bwd PCR (cps)
Default: 172/172 Range: Format: Numeric
Fwd/Bwd SCR (cps)
Release 9.0.0 7-17

Table 7-14. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window* (Continued) Field Name Field Values Description
Fwd/Bwd MBS (cells)
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, Vbrnrt1, Vbr-rt2, Vbr-rt1, Vbr-express.
OAM Status
Default: Unsupp Specifies the OAM support used. Range: N/A Format: Predefined 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 activate OAM; the feature is not available on AAL2 trunks to IADs. The PSAX system is used as a termination point for ATM traffic. The OAM loopback test is supported for end-toend 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.
End-Pt
VCC Conn Type Default: Svc Specifies the VCC connection type. Range: N/A Format: Predefined Svc Spvc Switched virtual circuit. Software-switched permanent virtural circuit. Wireless backhaul applications: If the spvcGlobalPriorityScheme field is enabled on the Call Control Resource Allocation Configuration window, you must select Spvc as the VCC Conn Type. Permanent virtural circuit.
Wireless backhaul applications: If the spvcGlobalPriori-
Pvc
tyScheme field is enabled on the Call Control Resource Allocation Configuration window, you must select Spvc as the VCC Conn Type.
Release 9.0.0 255-700-447

[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 values assigned 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. 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. 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 VCC Conn Type field.
[VCC VPI/VCI]
Default: 0 / 0 Range: 04095 (VPI); 065535 (VCI) Format: Numeric
[VCC VIB/VUNIB] [VCC Owner]
Default: 0/0 Range: N/A Format: Numeric
Default: Local Indicates whether the bearer VCC owner is the active (local) side or the passive (remote) side of the connecRange: N/A Format: Predefined 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.
Release 9.0.0 7-19

Inactive Timer
Default: 3600 Range: 09999999 99 Format: Numeric (msec)
Specifies the time period during which no activity is taking 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: OutOfIndicates whether the connection is attempting to make Service calls or receive calls. Range: N/A Format: Predefined OutOfService InService Indicates that the connection is not available to attempt making or receiving calls. Indicates that the connection is available to attempt making calls or receiving calls. Specifies the user-defined priority level of this connection. Assigning Priority 1 to all wireless calls ensure they will 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.
Priority
Application Type Default: Narrow- Specifies the PSAX application that will use this trunk band connection. Range: N/A Format: Predefined Narrowband V5 Gr303 H248 Spvc Indicates the trunk will be used for narrowband connections. This value is not currently supported. Indicates the trunk will be used for GR-303 connections. Indicates the trunk will be used for H.248 protocol connections. Indicates the trunk will be used for SPVC connections. Wireless backhaul applications: If the spvcGlobalPriorityScheme field is enabled on the Call Control Resource Allocation Configuration window, you must select the value Spvc in the Application Type field.
Release 9.0.0 255-700-447

Dsp Iwf Type
Default: None Specifies the Interworking function type on assigning AAL2 connections to compatible DSP chips on the DSP2C Range: N/A Format: Predefined 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 previous PSAX system software releases. 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) in the 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. 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. 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-specific DSP Resource Configuration option), or your connections will not be assigned or activate. If a DSP resource fails, connections are rerouted by a software DSP resource manager that selects available DSPs from a chassis-wide pool. 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).
Packet-pipe
Gsm
Dsp Select Type
Default: Automatic Range: N/A Format: Predefined
Automatic
Manual
Release 9.0.0 7-21

Dsp Card Slot Id Default: 0 Range: Chassis dependent Format: Numeric
Specifies the slot number of the DSP2x Voice Server module 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 DSP2x 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 DSP2x 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. 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 actually 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 channels also depends on what type of CBR or VBR you select in the Service Type field (see the Dsp Iwf Type and Service Type fields for more details). Displays the last release cause code. The cause code indicates a reason why the last attempted call was released. See the reference appendix in this guide for the description of SPVC Connection Cause Codes.
Num of DSP Chnl
[Last Rls Cause] Default: 0 Range: N/A Format: Numeric [Last Rls Diag]
Default: N/A Displays the last release diagnosis. The value in this field explains how the connection was released and reported Range: N/A Format: predefined by the far end of the connection. 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 connection is restarted.
[Retry Counter] Default: N/A Range: N/A Format: Numeric
Release 9.0.0 255-700-447

Adding a Narrowband Address Table 7-14. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window* (Continued) Field Name Field Values Description
[Oper Status]
Default: Idle Displays the operational status of the bearer VCC. Range: N/A Format: Predefined Idle OutOfService Init Active Release Indicates that the bearer VCC is not transmitting. Indicates that the bearer VCC is not operational. Indicates that the bearer VCC is initializing. Indicates that the bearer VCC is transmitting. Indicates that the bearer VCC has been released. Displays the number of currently active channels for the bearer VCC 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.
[Active Chnl Cnt] [Avail Bandwidth]
Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric
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.
Adding a Narrowband Address

Begin
1 On the ATM Trunking Local Node Configuration window, select the Go 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 23 to add more narrowband addresses.
End
Release 9.0.0 7-23

Adding a Narrowband Address
Figure 7-9. ATM Trunking NarrowBand Routing Table Window

Table 7-15. Commands for the ATM Trunking Narrowband Routing Table Window Command Function
Find: Go Back to Connection Menu
Searches for the ATM address entry with a value you specify. Redisplays the ATM Trunking Local Node Configuration window.
Table 7-16. Field Descriptions for the ATM Trunking Narrowband Routing Table Window Field Name Field Values Description
Narrowband Address (Hex) (display table)
Default: N/A Interworking function ATM addresses for the remote endpoint. Type an address in hexadecimal Range: N/A Format: Hexadecimal format up to 20 bytes (160 bits) long (10 groups of 4 characters each).
Release 9.0.0 255-700-447

Adding a Broadband Address
Table 7-16. Field Descriptions for the ATM Trunking Narrowband Routing Table Window (Continued) Field Name Field Values Description
Add an Entry:
Default: User provided Range: N/A Format: Hexadecimal Default: N/A Range: 1152 Format: Numeric Default: N/A Range: 1100 Format: Numeric
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 specification). Enter a value for the number of bits for the ATM address mask. Interworking function identifier (IWF) for the remote IWF.
Num Bits
IWF ID

Begin
1 On the ATM Trunking Local Node Configuration window, select the Go 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 23 to add more broadband addresses.
End
Release 9.0.0 7-25

Figure 7-10. ATM Trunking Broadband Routing Table Window

Table 7-17. Commands for the ATM Trunking Broadband Routing Table Window Command Function
Find: Go Back to Connection Menu
Searches for the ATM address entry with a value you specify. Redisplays the ATM Trunking Local Node Configuration window.
Table 7-18. Field Descriptions for the ATM Trunking Broadband Routing Table Window Field Name Field Values Description
Broadband Address Default: N/A Interworking function ATM addresses for the (Hex) remote endpoint. Type an address in hexadecimal Range: N/A (display table) Format: Hexadecimal format up to 20 bytes (160 bits) long (10 groups of 4 characters each).
Release 9.0.0 255-700-447

Viewing ATM Trunking Information
Table 7-18. Field Descriptions for the ATM Trunking Broadband Routing Table Window (Continued) Field Name Field Values Description
Add an Entry:
Default: User provided Range: N/A Format: Hexadecimal Default: N/A Range: 1152 Format: Numeric Default: N/A Range: 1255 Format: Numeric
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 specification). Enter a value for the number of bits for the ATM address mask. The group identifier for the broadband ATM address.
Num Bits
Group ID

Begin
1 On the ATM Trunking Remote IWF Configuration window, select the Go 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 Channel 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
Release 9.0.0 7-27

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. Updates the display of remote IWF trunks. Redisplays the ATM Trunking Remote IWF Configuration window.
Update Configuration Go Back to Previous Screen
Table 7-20. Field Descriptions for the ATM Trunking Data Channel Table Window Field Name Description
Rmt IWF ID Sig VCC ID Br VCC ID Ch ID Status
This column displays the remote IWF ID. This field is not currently supported. This column displays the corresponding signaling VCC identifier. This column displays the corresponding bearer VCC identifier. This column displays the channel identifier. This column displays whether the administrative status for the remote IWF is up or down.
Release 9.0.0 255-700-447

Table 7-20. Field Descriptions for the ATM Trunking Data Channel Table Window (Continued) Field Name Description
VCC Owner NB Intf Total: 0/0
This column displays the corresponding owner of the signaling VCC. This column displays the corresponding VCC ID, which is assigned by the owners of the signaling VCC. 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.
Release 9.0.0 7-29

Release 9.0.0 255-700-447
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 Follow the order in which the windows are presented in this document 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 procedure. The configuration windows in general have many more field options and commands than table windows.
Note:
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 Configuration > 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.
Release 9.0.0 8-1
Chapter 8 Configuring V5.2 European IDLC

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 window. 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 Interface 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 window. 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 PhysCChanel Cfg window displays 14. On V5 PhysCChannel Configuration window, at a minimum enter values 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 >
Release 9.0.0 255-700-447

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

The 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 minimum, 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.

V5.2 IWF Device Interoperability
VC algorithm depends on encode profile used. Tone detect bypass. Translate type: alaw to alaw. Note: You must choose DSP parameters compatible with the Encoding 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.
Table 8-1. V5.2 Voice Switch Interoperability Vendor and Model Software Release Signaling Supporting Module
Lucent 5ESS Alcatel S-10 Ericsson AXE-10 Nortel DMS 100 Siemens EWSD
5EE14 Contact vendor for details. Contact vendor for details. Contact vendor for details. Contact vendor for details.
21-Port HighCCS for POTS and 23N66 Density E1 Multiservice ISDN CCS for POTS CCS for POTS CCS for POTS CCS for POTS 23N66 21-Port HighDensity E1 Multiservice 23N66 21-Port HighDensity E1 Multiservice 23N66 21-Port HighDensity E1 Multiservice 23N66 21-Port HighDensity E1 Multiservice
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-2. V5.2 IAD Interoperability Vendor and Model Software Release Signaling WAN Interface Type LAN Interface Type Port Limits
Lucent CellPipe 4A/4AU Lucent CellPipe 4AI Lucent CellPipe 4H/8H Lucent CellPipe 4HI
3.4.10-R1 3.4.10-R1 3.4.10-R1 3.4.10-R1
CCS/ELCP CCS/ELCP CCS/ELCP CCS/ELCP
ADSL ADSL SHDSL SHDSL
4 analog FXO ports 4 BRI ports 4 or 8 analog FXO ports 4 BRI ports
Release 9.0.0 255-700-447

V5.2 ISDN Implementation
Table 8-2. V5.2 IAD Interoperability (Continued) Vendor and Model Software Release Signaling WAN Interface Type LAN Interface Type Port Limits
Verilink NetEngine 6104/6108 Verilink NetEngine 6300 Verilink NetEngine 6504/6508 RAD LA-110 RAD LA-140
3.4.10-R1
CCS/ELCP CCS/ELCP CCS/ELCP CCS/ELCP CCS/ELCP
ADSL ADSL SDSL SHDSL SHDSL SHDSL SHDSL
4 or 8 analog FXO ports 4 BRI ports 8 analog FXO ports 4 or 8 analog FXO ports 4 BRI ports 4 BRI ports 4 BRI ports
Verilink NetEngine 6104i 3.4.10 3.4.10-R1 3.4.10-R1
Verilink NetEngine 6504i 3.4.10
Contact ven- CCS/ELCP dor for details. Contact ven- CCS/ELCP dor for details.
V5.2 ISDN Implementation

Select the value Isdn in the Port Type field and follow configuration instructions on field description tables.
PSTN Configuration
Enabling the V5 Feature
Perform the following procedure to turn on the desired feature from the Feature 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.
Turning On the H.248 Gateway Control Protocol Feature
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed (see Figure 8-1). 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.
Release 9.0.0 8-5

PSTN Configuration
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. The following message is displayed in the status line:
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 modification. [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)
Release 9.0.0 255-700-447

PSTN Configuration
Figure 8-2. Feature Turn On/Off Window

Table 8-3. Commands for the Feature Turn ON/OFF Table Window Command Function
Page Up Page Down Top Bottom Find . . . . . Feature ID: Go Back to Site-Specific Menu
Scrolls up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. This command is currently not supported. Redisplays the Site-Specific Menu window.
Release 9.0.0 8-7

PSTN Configuration
Table 8-4. Field Descriptions for the Feature Turn On/Off Table Field Name Field Values Description
Total: 0/0
First number: Indicates which Feature ID is currently 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 features 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 Pnni Gr303 Displays the PSAX system features that you can enable or disable.
Private network-to-network interface feature. Note: Currently, this feature cannot be disabled. ITU-T GR-303 local loop emulation services feature. 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. Virtual Internet Protocol Router feature. Note: This feature is not currently supported. Select this value to enable the H.248 protocol feature. European V.5 local loop emulation services feature. ISDN Q.921 User Adaptation Layer Protocol feature. Enables OSI Layer 2 ISDN D-channel signalling between an Media Gateway Controller (for example, a Softswitch) and a Media Gateway (for example, a PSAX system) in PRI offload applications. ATMsecurity feature. Bulk statistics feature. Displays the amount of system memory in bytes allocated to the feature.
Vipr H248 V5 Iua
AtmSec BulkStats space memory Default: PNNI: 67108864 Gr303: 134217728 Vipr: 67108864 H248: 134217728 V5: 134217728 Iua: 67108864 Range: N/A Format: Numeric (bytes)
Release 9.0.0 255-700-447

Setting Call Control Resource Allocation Values
Table 8-4. Field Descriptions for the Feature Turn On/Off Table (Continued) Field Name Field Values Description
desired status
Default: Enable or Disable (depends on the feature) Range: N/A Format: Predefined alphanumeric Disable
Displays whether the feature is to be made operational or not. Note: On the Site-Specific Menu window, the feature options that are displayed between brackets [ ] are disabled. 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. 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 displayed in the current status field. Displays the current operational status of the feature.
Enable
current status
Default: N/A Range: N/A Format: Predefined alphanumeric Disabled Enabled
Indicates that the selected feature is currently not operational. Indicates that the selected feature is currently operational.

Perform the following procedure to configure the call control resource allocation on the PSAX system.
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed (see Figure 8-3). 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 provided 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:

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
Release 9.0.0 255-700-447

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 Go Back to Site-Specific Menu
Applies the values you entered on this window. Redisplays the Site-Specific Menu window.
Release 9.0.0 8-11

Configuration Guidelines
Table 8-6. Field Descriptions for the Call Control Resource Allocation Configuration Window Field Name Field Values Description
Important: The ranges of values for numeric fields are software imposed. When changing the values 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 calculated 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 command 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 displayed: Resource allocation configuration has been applied. Need to save configuration and reboot the system to take effect.
svcPtToPtCalls
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 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 window is set to 8000, then the recommended values for this field are 4000 for AAL1 and 4100 for AAL2. Specifies the maximum number of SVC point-to-multipoint calls to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of parties on SVC 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. H.248 Applications: Set the value in this field to 0.
svcPtToMultiPtCalls Default: 002000 Range: 04000 Format: Numeric svcPtToMultiPtPar- Default: 002000 ties Range: 04000 Format: Numeric
Release 9.0.0 255-700-447

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: 010000 Format: Numeric Specifies the maximum number of SPVC circuit 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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0. 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-topoint 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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0.
spvcTePtToPtCalls
Release 9.0.0 8-13

spvcAtmPtToPtCalls Default: 002000 Range: 010000 Format: Numeric
Specifies the maximum number of SPVC ATM pointto-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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of SPVC frame relay 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 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 call fields and the number of ATM trunk VCCs cannot exceed 32 calls. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of SPVC point-to-multipoint calls to be supported by the PSAX system. SPVC Priority Configurations: If you select the value Enabled in the spvcGlobalPriorityScheme 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. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of parties on SPVC point-to-multipoint calls to be supported by the PSAX system. SPVC Priority Configurations: If you select the value Enabled in the spvcGlobalPriorityScheme 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. H.248 Applications: Set the value in this field to 0.
spvcFrPtToPtCalls
spvcPtToMultiPtCalls
spvcPtToMultiPtParties
Release 9.0.0 255-700-447

aal2CirAtmSpvcVcc Default: 001000 Calls Range: 04000 Format: Numeric aal2VbrAtmSpvcVc Default: 000100 cCalls Range: 04000 Format: Numeric sgApiCirEmEndPts Default: 001000 Range: 0-15000 Format: Numeric Default: 000000 Range: 0-15000 Format: Numeric Default: 000000 Range: 0-15000 Format: Numeric
Specifies the maximum number of circuit emulationto-ATM standard AAL2 SPVC calls to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of VBR-to-ATM standard AAL2 SPVC calls to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of circuit emulation endpoints for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of ATM SVC endpoints for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of SVC point-to-point 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 protocol 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 Number of Terminations field on that window is set to 8000, then recommended values for this field are 4000 for AAL1 and 4100 for AAL2 Specifies the maximum number of SVC point-to-multipoint calls for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0. Specifies the maximum number of parties on SVC point-to-multipoint calls for the Connection Gateway API to be supported by the PSAX system. H.248 Applications: Set the value in this field to 0.
sgApiAtmSvcEndPts
sgApiPtToPtSvcCalls
sgApiPtToMultiPtS- Default: 000000 vcCalls Range: 0-4000 Format: Numeric sgApiPtToMultiPtParties Default: 000000 Range: 0-4000 Format: Numeric
Release 9.0.0 8-15

atmTrunkVccs
Specifies the maximum number of VCCs supported by ATM trunking. SPVC Priority Configurations: If you select the value Enabled in the spvcGlobalPriorityScheme 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. 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 window 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. Specifies the maximum number of switched narrowband calls supported by ATM trunking. H.248 Applications: Specifies the maximum number of simultaneous calls through AAL2. 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 window is set to 8000, then recommended values for this field are 0 for AAL1 and 4000 for AAL2 Displays the percentage of memory allocated to call control. A portion of the total system memory is allocated 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.
atmTrunkNarrowBandCalls
[callContrlResAllo- Default: 0098 cUsage %] Range: 0100 Format: Numeric
Release 9.0.0 255-700-447

cgSvcCutThroughOption
Default: cgSvcAcImplicitCutThrough Range: N/A Format: Predefined alphanumeric
Specifies whether the PSAX system or the connection gateway device (connection manager) sends a cutthrough message to initiate an SVC connection. Note: The value in this field is relevant only if you have enabled a media gateway control feature (the Connection Gateway API feature or the H.248 protocol feature). Indicates that the PSAX system sends a cut-through message to the connection gateway device to initiate an SVC connection. Indicates that the connection gateway device determines when to send a cut-through message to the connection manager to initiate an SVC connection. H.248 Applications: You must use the value cgSvcAcExplicitCutThrough if you are using the H.248 protocol feature. Specifies whether the PSAX systemwide priority scheme must be supported for all SPVCs and SPVC trunks. Indicates that the priority scheme is not in force (disabled). 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 schemeenabled trunks in an IMA link, the limit is 32 SPVCs.
cgSvcAcImplicitCutThrough cgSvcAcExplicitCutThrough
spvcGlobalPriority- Default: Disabled Scheme Range: N/A Format: Predefined alphanumeric Disabled Enabled
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.
Table 8-7. PSAX System Performance Capabilities Per Node for Release 9.0.0 Connection Type Maximum Number of Duplex Calls per Node Call Set-up Rate for CPU2 and CPU3L Modules* Call Set-up Rate for CPU3 and CPU4 Modules*
PVC SPVC SVC All connections combined

*
60,000 10,000 15,000 60,000

N/A
N/A
60 calls per second 100 calls per second 60 calls per second 100 calls per second
A CPU3 or CPU4 module paired in the same chassis with a CPU2 or CPU3L module will operate at the lower CPU2/CPU3L module call rate. Release 9.0.0 8-17

When using both SPVC and SVC connection types, you can set up any combination of calls as long as you do not exceed 100% of the call control resource memory allocation (callContrlResAllocUsage field on the Call Control Resource Allocation 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 of calls 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.
Accessing the V5 Resource Allocation Configuration Window

Accessing the V5 Resource Allocation Configuration Window, Part 1
Begin
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.
Figure 8-5. V5 Interface Configuration Window
The menu options on this window perform the following functions:
Release 9.0.0 255-700-447

Table 8-8. Commands for the V5 Interface Configuration Menu Window Menu Option Description
V5 Interface Configuration V5 Variant Table [V5 Statistics] V5 Resource Allocation Configuration
Displays the V5 Interface Configuration window. Displays the V5 Variant Table. The V5 Statistics window is not currently supported. Displays the V5 Resource Allocation Configuration.
Go Back to Site Specific Menu Redisplays the Site Specific Menu.
3 On the V5 Interface Configuration window, select the V5 Resource Allocation Configuration option. The V5 Resource Allocation Configuration window is displayed (see Figure 8-6). Table 8-9 describes the commands on the window. Table 8-10 describes the fields on this window. 4 Enter the value 010 in the Max V5 Interface field. 5 Select the Apply Configuration command. 6 Remain on this window and proceed with the following procedure, Accessing the V5 Resource Allocation Configuration Window on page 8-18.
End
Figure 8-6. V5 Resource Allocation Configuration Window
Release 9.0.0 8-19

Table 8-9. V5 Resource Allocation Configuration Window Command Function
Apply Configuration Go Back to V5 Menu screen
Applies the configuration values you entered in the fields on the window.. Re-displays the V5 Interface Configuration window.
Table 8-10. Field Descriptions for the V5 Resource Allocation Configuration Window Field Name Values Description
Max V5 Interface
Default: 004 Range: 010 Format: Numeric Default: 008000 Range: 18000 Format: Numeric Default: 008000 Range: 18000 Format: Numeric Default: 008000 Range: 18000 Format: Numeric
Indicates the maximum number of V5 interfaces that can be supported in this system. Indicates the maximum number of User Ports that can be used in this system. This includes both PSTN and ISDN ports. Indicates the maximum number of User Ports per V5 interface. This includes both PSTN and ISDN ports per V5 interface. 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 necessarily imply that maximum number of PSTN ports is the number of Max User Ports minus the number of Max Isdn Ports. 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 /V5 Interface field. A non-zero value for this parameter does not necessarily imply that maximum number of PSTN ports/V5 interface is this value minus the value of the Max Isdn Ports/V5 Interface field. 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. This timer is used by the BRA port manager to supervise the access activation procedure of a port. Values are represented in seconds. 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.
Max User Ports
Max User Ports/V5 Interface Max Isdn Ports
Max Isdn Ports/V5 Interface
TPL1 Timer
Default: 15 Range: 130 Format: Seconds Default: 15 Range: 130 Format: Seconds Default: 1000 Range: 5001500 Format: msec
T1 Timer
BccTbcc5 Timer
Release 9.0.0 255-700-447

SetSA7Bit Timer
Default: 050 Range: 50200 Format: Msec. Default: 050 Range: 50200 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. 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 milliseconds. This timer is used for the Link Id procedure. This is the maximum time the AN should take to complete the Link Id procedure. This timer can be disabled by setting this value to 0. Specifies the maximum number of primary rate access (PRA) ports that can be supported by the PSAX system.
ReadSA7Bit Timer
LinkId Timeout
Default: 00 Range: 030 Format: N/A
Max ISDN Pra Ports Default: 100 Range: 1100 Format: Numeric
Release 9.0.0 8-21

Target DSP Over Subscription
Default: 20000% Range: Format:
Specifies the limit of the DSP resource oversubscription 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. Specifies the current value of the DSP chip resources oversubscription for V5 voice calls. The calculation of the current DSP resource oversubscription in the chassis is as follows: the number of DSP resources left in the chassis after configuration = [{(number of DSP2D modules * 384) number of AAL2 trunks} (number of AAl2 trunks * no. of ISDN ports/trunk)]. The preceding 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 channels for PRA and 2 Bchannels for BRA. The value is expressed as a percentage (see Note in Description for Target DSP). This calculation of the oversubscription is valid only if the Least Used algorithm is chosen for the DSP resource allocation scheme. This indicates the maximum number of E1 links that can be supported in this system. 84 E1 Interfaces * 3 = 3-Port Channelized DS3.
[Current DSP Over Default: 60000% Subscription] Range: Format:
[Max E1s]
Configuring the ATM See the appropriate PSAX module user guide to configure the connection Module for V5.2 interface as ATM UNI 3.0. Note: Configuring the DSP2D for Algoset 6 and AAL2 Standard This sample configuration uses the STM-1 MSP SM module on an ATM UNI 3.0 interface.
See the PacketStar PSAX System Connections Provisioning Guide to configure the connection 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 create new interface IDs.
Release 9.0.0 255-700-447

Accessing the V5 Interface Configuration Window, Part 1
Begin
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
Page Up Page Down Top Bottom Add an Interface Go Back to V5 Menu screen
Scrolls up one page. Scrolls down one page. Scrolls to the top of the current page. Scrolls to the bottom of the current page. Displays the V5 Interface table. 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.
Release 9.0.0 8-23

Table 8-12. Field Descriptions for the V5 Interface Table Window (Continued) Command Function
Admin Status Total 0/0
Specifies whether the interface is up or down. The first number in this field indicates the number 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.
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. 4 Remain on this window and continue with the next procedure.
End
Release 9.0.0 255-700-447

Figure 8-8. V5 Interface Configuration Window Table 8-13. Commands for the V5 Interface Configuration Window Command Function
Create Interface Apply Configuration Update Delete Interface and return Bring Into Service Take (n) OutOfService Apply Variant SO Command Variant Table Go Back to V5 Intf Table
Creates the V5 interface. Applies the values entered on the fields on the window. Updates the window values after a field value change. Deletes the interface and returns to the V5 Interface Table. Brings the variant into service. Takes the variant out of service. Switches the channel or trunk to an alternate configured channel or trunk. Displays all configured alternate channels or trunks. Returns to the V5 Interface Table.
Release 9.0.0 8-25

Table 8-14. Field Descriptions for the V5 Interface Configuration Window Field Name Field Value Description
V5Intf ID:
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 1127, only 110 interface IDs are supported in Release 8.0.0. Specifies the administrative status of the interface.
[Admin Status]
Default: OutOfService Range: N/A Format: Predefined OutOfService InService
The interface is not in service. The interface is in service. Specifies if any factor is impeding the configured interface from operating.
[Oper Status]
Some factor is impeding the interface from operating. The interface is in service with no impedances. Specifies the Variant Id which is active for this V5 Interface. Only one variant is the active ID. Variants permit an interface group to have multiple configurations to connect to the voice switch. Changing variants only affects the network portion from the Gateway to the voice switch. The network portion from the gateway to the subscriber 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. Specifies the local exchange interface ID used by the 5ESS. This ID is used externally by the PSAX to communicate with the 5ESS. Specifies the Variant Id to which the current active variant is to be switched. Specifies whether active or standby switchover is used. No switchover action is specified. This command is used to switch manually from active to standby variant. Note: The database must be saved after any Variant SO command is applied.
Active Variant ID
LE Interface ID
Switchover Variant Default: 0 ID Range: 0127 Format: Numeric Variant SO Command Default: NoAction Range: N/A Format: Predefined NoAction NormalSwitchToStandby
Release 9.0.0 255-700-447

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. 4 Remain on this window and continue with the next procedure.
End
Figure 8-9. V5 Intf Variant Table Window Table 8-15. Commands for the V5 Intf Variant Table Window Command Function
Page Up Page Down Top Bottom Find... Intf ID: ... ID:
Scrolls up one page. Scrolls down one page. Scrolls to the top of the current page. Scrolls to the bottom of the current page. Finds the interface ID and the variant ID of a particular connection.
Release 9.0.0 8-27

Table 8-15. Commands for the V5 Intf Variant Table Window (Continued) Command Function
Add Variant Entry Go Back to Previous screen
Displays the V5 Interface Variant Configuration window. Displays the V5 Interface Configuration window.
Table 8-16. Field Descriptions for the V5 Interface Variant Table Window Field Name Field Value Field Description
V5 Intf ID
Default: 0 Range: 110 Format: Numeric Default: 0 Range: 0127 Format: Numeric Default: OutOfService Range: N/A Format: Predefined OutOfService InService
Specifies the V5 interface identifier.
V5 Variant ID
Specifies the V5 variant identifier.
[Admin Status] (display only)
Specifies the Administrative status of the Variant channel.
Indicates that the variant channel is not in service. Indicates that the variant channel is in service. Specifies whether the variant protection status is active or inactive.The displayed value shows which variant is active/standby in this particular V5 interface. Indicates that this variant is active and operational. Indicates that this variant is not active but in standby mode.
[Var Protection Sta- Default: Active tus] (display only) Range: N/A Format: Predefined Active Passive
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.
Release 9.0.0 255-700-447

3 Remain on this window and continue with the next procedure.

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 Add E1 Link Table to Variant Add DL Table to Variant Add UserPort Table to Variant Create Variant Apply Configuration Update Delete Variant and return Bring Into Service Go Back to V5 Variant Table
Displays the V5 PhysCChannel Configuration Table window. Displays the V5 E1 Link Configuration Table window. Displays the Data Link Configuration Table window. Adds the UserPort table to the variant configuration. Creates a variant configuration link. Applies the configuration. Updates the configuration. Deletes the variant configuration link and returns to the V5 Intf Variant Table window. Brings the variant configuration in to service. Redisplays the V5 Intf Variant Table window.
Release 9.0.0 8-29

Table 8-18. Field Descriptions for the V5 Interface Variant Configuration Window Field Name Field Value Field Description
V5 Intf ID
Specifies the V5 interface identifier.
Specifies the V5 variant identifier.
[Admin Status]
Specifies the Administrative Status of the Variant channel.
The variant channel is not in service. The variant channel is in service. Specifies whether the variant protection status is active or inactive. This fields also shows which variant is active or passive in this particular V5 interface. Active shows this variant is active and operational. Passive shows this variant is not active but in standby mode. 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 additional feature sets over V5.1. Specifies the V5 interface edition being provisioned. 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. First edition interface is used Second edition interface is used.
[Var Protection Sta- Default: Active tus] Range: N/A Format: Predefined Active Passive [Interface Type] Default: V52 Range: N/A Format: Predefined Default: SecondEdition Range: N/A Format: Predefined
Interface Edition
FirstEdition SecondEdition
Release 9.0.0 255-700-447

Table 8-18. Field Descriptions for the V5 Interface Variant Configuration Window (Continued) Field Name Field Value Field Description
Align Ports Method Default: V5SecondE Indicates type of flag used for port alignment method to use along with interface type. ditionPortAlign Range: N/A Format: Predefined alphanumeric V5PortAlignUndefi Port align protocol not defined. ned V5PortIndividualP Informs the V5 stack to unblock all relevant PSTN ortAlign and ISDN ports one by one. V5FirstEditionPort Informs the V5 stack to unblock all relevant PSTN Align and ISDN ports as a single entity. V5SecondEditionP Informs V5 stack to unblock or block all relevant ortAlign PSTN and ISDN ports as a separate entity. AN Initiate Link Proc Default: False Range: N/A Format: Predefined False True [L1 Fsm Normal Timer] Default: 500 Range: 11000 Format: msec Default: 2500 Range: 12500 Format: msec This flag indicates whether the Access Network or Local Exchange initiates the Link Id procedure. If true, the AN should initiate it. If False, the LE should initiate it. False informs the V5 stack not to initiate the link identification procedure. True informs V5 stack to initiate the link dentification procedure. 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. Specifies the L1 finite state machine loss of signal or 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. Specifies the L1 finite state machine alarm indicator signal timer that the E1 facility uses to enter into the non-operational state when there is an alarm indication. Values are given in milliseconds. Specifies the L1 finite state machine RAI signal timer for the E1 facility to enter into the nonoperational state when an RAI occurs. Values are given in milliseconds. 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.
[L1 Fsm LosOrLos Timer]
[L1 Fsm Ais Timer] Default: 2500 Range: 12500 Format: msec
[L1 Fsm Rai Timer] Default: 2500 Range: 12500 Format: msec Resource Manager TR1 Default: 500 Range: 5001500 Format: msec
Release 9.0.0 8-31

Accessing the V5 Physical C-Channel Configuration Table

Begin
1 From the V5 inft Variant Configuration window, select the Add PhysChnl 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
Scrolls up one page. Scrolls down one page. Scrolls to the top of the current page. Scrolls to the bottom of the current page.
Find...Intf ID...Variant ID...Phy- Finds the interface ID, variant ID and physical CsCChan channel of a particular connection. Add PhysCChan Config Entry Go Back to Previous Screen Displayes the V5 PhysCChannel Configuration window. Returns to the V5 Interface Variant Configuration window.
Release 9.0.0 255-700-447

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. Displays the interface ID. Displays all the variant IDs for the Interface ID. Displays the physical C channel for the interface ID. Displays the operating status of the connection. Displays protection status, either primary or standby.
Intf ID Variant ID PhysCChan OperStatus P Status
Accessing the V5 Physical C-Channel Configuration Window

Begin
1 On the V5 PhysCChannel Configuration Table, select the Add PhysCChan 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
Release 9.0.0 8-33

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 Apply V5PhysCChn configuration Update V5PhysCChn in the table Delete V5PhysCChn and return
Adds the V5 physical C-channel entry to the V5 PhysCChannel Configuration Table. Adds the configuration values you set to the network database. Refreshes any changes made to V5 Phys C-Channel entries in the table. Deletes the V5 Phys C-Channel and returns to the V5 PhysCChannel Configuration Table. Returns to the V5 Phys ical C-Channel Configuration Table.
Go to the LogCChan Configuration Displays the Logical C-Channel Configuration Table. Go Back to Previous Screen
Release 9.0.0 255-700-447

Table 8-22. Field Descriptions for the V5 Physical C Channel Configuration Window Field Name Field Value Description
Interface ID
Default: 0 Range: 110 Format: Numeric Default: Active Range: 0127 Format: Numeric Default: 0 Range: 144 Format: Numeric: SSPPCCC
This index identifies the V5 Interface configuration table. This index identifies the variant number in the V5 interface. Specifies the physical C-channel ID. This index identifies the physical channel. This value is userassigned. 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-channels. A physical C-channel may not be used to carry bearer traffic channels. 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 runtime 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 window for configuration. 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, FLogical Chan ID, and D-Logical Chan ID fields on the V5 User Port Configuration Window.
Variant Id
PhysicalC-ChanId
ConfigCommC Chan Id
ConfigLogical CChan Id
Release 9.0.0 8-35

Table 8-22. Field Descriptions for the V5 Physical C Channel Configuration Window (Continued) Field Name Field Value Description
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. Protection Group 1 always uses the user-assigned timeslot value 16. Protection Group 2 uses the timeslot value 15 and 31 (2 timeslots are necessary to provide sufficient bandwidth on V5.1 systems with ISDN and most V5.2 systems). Pg-1 supports one active C-Channel and one Standby C-Channel where N1 = 1, K1 = 1. 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. 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; otherwise, this value is used as Active logical C-channel. 44 Active logical C Channels and 4 Standby physical C-channels are allowed. This shows the current active mapping. This identifies the logical C-channel that is exchanged between AN and LE. Indicates whether this physical C Channel is active, standby, or out of service.
Pg-1 Pg-2
[OperCommCChan Default: 500 Id] Range: 044 Format: Numeric
[OperLogical CChan Id] [Protection Status]
Default: 0 Range: 065503 Format: Numeric Default: OutOfService Range: N/A Format: Predefined OutOfService Active Standby
This physical C-Channel is out of service. This physical C-channel is actively transmiting signalling messages. This channel is the standby physical C-channel to carry signalling messages. Specifies the operational status of physical channel.
[Operational Status]
This physical C-channel is currently out of service. This physical C-channel is currently in service.
Release 9.0.0 255-700-447

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 Table displays (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
Page Up Page Down Top Bottom Find...Intf ID: Variant ID: Add E1Link Config Entry Go Back to Previous Screen
Scrolls up one page. Scrolls down one page. Scrolls to the top of the current page. Scrolls to bottom of the current page. Finds the interface ID and variant ID of a particular connection. Adds an E1 link configuration entry. Returns to the V5 Intface Variant Configuration window.
Release 9.0.0 8-37

Table 8-24. Field Descriptions for the V5 E1 Link Configuration Table Window Command Function
Intf ID Variant ID LinkID OperStatus
Displays the interface ID. Displays all the variant IDs for the Interface ID. Displays the link ID of the interface ID. Displays the operating status of the connection.
Accessing the V5 E1 Link Configuration Window

Begin
1 fFrom the V5 E1Link Configuration Table, select the Add E1Link Config Entry. The V5 E1Link Configuration window displays (see Figure 8-14). Table 8-25 describes the commands and Table 8-26 describes the fields on this window. 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
Release 9.0.0 255-700-447

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 Go Back to Previous Screen
Displays the Timeslot Channel Table window. Returns to the previous window.
Table 8-26. Field Descriptions for the V5 E1 Link Configuration Window Field Name Field Values Description
Interface Id
Default: 0 Range: 110 Format: Numeric Default: 0 Range: 0127 Format: Numeric Default: 0 Range: 015 Format: Numeric Default: 0 Range: Chassis dependent Format: SSPPCCC
Specifies the interface the user created and is currently configuring. This index identifies the variant channel number in the V5 interface. Specifies the logical link identifier to identify a link.
Variant Id
Link Id
Phys Id
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.
Release 9.0.0 8-39

Table 8-26. Field Descriptions for the V5 E1 Link Configuration Window Field Name Field Values Description
Administrative Sta- Default: Forcetus Blocked Range: N/A. Format: Predefined ForceBlocked
Specifies the administrative status of the call processing functions on the E1 Link.
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. There are no restrictions on call processing functions. Use this setting to immediately block all active and future calls. This setting immediately terminates any active calls on the link. 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. Specifies the logical link id on the LE side.
Unblocked NonDeferBlocked
DeferBlocked
LELink ID
[Operational State] Default: Normal Range: N/A Format: Predefined Normal LocalFailure RemoteFailure [Operational Status] Default: OutOfService Range: N/A Format: Predefined OutOfService InService
Specifies the protection status of the link.
The link is operating normally. A failure has occurred on the PSAX side, either an LOS or LOF. A failure has occurred on the LE side, either an LOS or LOF. Specifies the operational status of the link.
The link is out of service. The link is in service.
Accessing the V5 E1 Interface Configuration Window

Begin
1 From the V5 E1Link Configuration window, select the Go to E1 Interface Configuration command. The V5 E1 Interface Configuration window displays (see Figure 8-15). Table 8-27 describes the commands and Table 8-28 describes the fields on this window.

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 Go Back to Previous Screen
Displays the Timeslot Channel Table window. Returns to the previous window.
Table 8-28. Field Descriptions for the V5 E1 Interface Configuration Window Field Name Field Values Description
[Phys ID]
Default: Range: N/A Format: ssppccc Default: 1 Range: 110 Format: Numeric Default: 0 Range: Format: Numeric
This index identifies the V5 Interface configuration table. This index identifies the variant channel number in the V5 interface. This index identifies the E1 Link Configuration Table.
V5 Intf Id (display only) Link Id (display only)
Release 9.0.0 8-41

Table 8-28. Field Descriptions for the V5 E1 Interface Configuration Window Field Name Field Values Description
[Channel1]
Default: 0 Range: Format: Numeric Default: 0 Range: B Format: Numeric Default: Range: Format: Numeric Format: OutOfService InService
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. 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 15. 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 31. Specifies the E1 interface physical operational status. The interface is out of service. The interface is in service.
[Channel2]
[Channel3]
[Operational Status]
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
Release 9.0.0 255-700-447

Figure 8-16. V5 Time Slot Table Table 8-29. Commands for the V5 Timeslot Table Window Command Function
Bring All Interfaces Into Service Take All Interface Out Of Service Go Back to Previous Screen
Brings all interfaces into service. Takes all interfaces out of service. Returns to the V5 E1 Interface Configuration Window.
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 displays (see Figure 8-17). Table 8-30 describes the commands and Table 8-31 describes the fields on this window. 2 Remain on this window and continue with next procedure.
End
Release 9.0.0 8-43

Figure 8-17. V5 Data Link Configuration Table Table 8-30. Commands for the V5 Data Link Configuration Table Window Command Function
Page Up Page Down Top Bottom Find... Intf ID: ... Variant ID: Add Data Link Config Entry Go Back to Previous screen
Scrolls up one page. Scrolls down one page. Scrolls to the top of the current page. Scrolls to the bottom of the current page. Finds the interface ID and the variant ID of a particular connection. Add a data link configuration entry. Returns to the V5 Interface Variant Configuration Window.
Table 8-31. Field Descriptions for the V5 Data Link Configuration Table Window: Command Function
Intf ID Variant ID DL C Path ID Total 0/0
Displays the interface ID. Displays the Variant ID associated with the Interface ID. Displays the Data Link Communication Path ID. The first number in this field indicates the number of the V5 Interface ID on the first line of the currently displayed window. The second number indicates the total number of V5 Interface IDs table entries on the table.
Release 9.0.0 255-700-447

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 displays (see Figure 8-18). Table 8-32 describes the commands and Table 8-33 describes the fields on this window. 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. 5 Remain on this window and continue with the next procedure.
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 Add V5 Data Link to the table Update V5 Data Link in the table
Displays the next V5 data link in the table. Adds V5 Data Link to the V5 Data Link configuration table. Updates the V5 data link in the table after field values are altered.
Release 9.0.0 8-45

Table 8-32. Commands for the V5 Data Link Configuration Window (Continued) Command Function
Delete V5 Data Link and return Go Back to Previous Screen
Deletes a selected data link and returns to the V5 Data Link Table. Return to the V5 Data Link Table.
Table 8-33. Field Descriptions for the V5 Data Link Configuration Window Field Name Field Value Configuration Left Panel Description
Interface ID
Specifies the ID the PSAX uses internally for the interface after the interface is created. Specifies the associated ID or the Interface ID.
Variant ID
Comm Path Id
Default: V5DLCPath The types described below refer to Data Link Control Protection1 protocol. Range: N/A Format: Predefined V5DLCPathProtect This path carries messages for synchronizing switching ion1 between primary and secondary links. protection level 1 on the digital loop carrier system. V5DLCPathProtect This path carries messages for synchronizing switching ion2 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 digital loop carrier system. V5DLCPathLinkCo ntrol V5DLCPathBcc on the digital loop carrier system. The link control path for the bearer channel connection. This path carries messages to allocate and deallocate timeslots on the digital loop carrier system. This path carries messages for call processing of PSTN (analog) circuits such as ESTABLISH, ESTABLISH ACK, DISCONNECT, DISCONNECT COMPLETE, and SIGNAL. This value must match the entry on the Physical CChannel table.
V5DLCPathPstn
Logical C Chan Id
Release 9.0.0 255-700-447

User Side Configuration Summary

The next part of V5.2 configuration is to configure the User Side. The following 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.
Configuring the Remote and Local Nodes for ATM Trunking
Begin
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
Release 9.0.0 8-47

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
Page Up Page Down Top Bottom Find... Intf ID: ... Variant ID:
Scrolls up one page. Scrolls down one page. Scrolls to the top of the current page. Scrolls to the bottom of the current page. Finds the interface ID and the variant ID of a particular connection.
Release 9.0.0 255-700-447

Table 8-34. Commands for the V5 User Port Table Window (Continued) Command Function
Add User Port configuration Entry Go back to Previous Screen
Adds the User Port configuration values of a specific entry. Returns to the V5 Interface Variant Configuration window.
Accessing the V5 User Port Configuration Window, PSTN Port Type

Begin
Note:
If you are configuring Port type PSTN on the V5 User Port Configuration window, the fields that display for configuration are different 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 Figure 8-19). Table 8-35 describes the commands and Table 8-36 describes the fields on this window. 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
End
If you want to add ports, change the Admin Status field to Unblocked and select the Add V5 User Port Configuration command.
Release 9.0.0 8-49

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- Displays the next V5 User Port configuration in the ration database. Add V5 User Port Configuration Delete V5 User Port Configuration Adds the V5 User Port configuration for the selected Interface ID. Deletes the V5 User Port configuration for the selected Interface ID.
Update V5 User Port Configuration Updates the V5 User Port configuration for the selected Interface ID. Apply V5 Admin Status Go back to Previous Screen Applies the V5 administrative status for the selected Interface ID. Returns to the V5 User Port Table.
Release 9.0.0 255-700-447

Table 8-36. Field Descriptions for the V5 User Port Configuration Window Field Name Values Description
Interface Id
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 1127, only 110 interface IDs are supported in Release 8.0.0. 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 network portion from the Gateway to the voice switch. The network portion from the gateway to the subscriber is not affected. LE port number used to idenify the ISDN and PSTN ports on a V5 interface. This value maps directly to a specific call connection. Specifies whether port is ISDN or PSTN in a V.5 interface. Select this value if you are using PSTN ports. The sample configuration uses this value. 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. Specifies the AAL2 trunk between the CP-IWF and the CO-IWF which carries the CIDs. Specifies the remote IWF connecting to the nearend IWF. Specifies the port number of the IAD used on the connection. 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. Specifies the Cid value of ISDN D channels that the PSAX is dynamically allocating. Although the field is editable, do not enter any values.
Variant Id
LE Port ID
Default: 0 Range: 032767 Format: Numeric Default: Pstn Range: N/A Format: Predefined Pstn Isdn
Port Type
AAL2 Trunking Vcc Default: 1 Id Range: 11024 Format: Numeric Remote IWF ID Default: Range: 1255 Format: Numeric Default: 1 Range: 1255 Format: Numeric Default: 16 Range: 16127 Format: Numeric
LES Interface Port ID PSTN Port CID
Note: The following ISDN fields are display only when the Port Type field is set to Isdn. ISDN D channels CID Default: [128] Range: 16233 Format: Numeric
Release 9.0.0 8-51

ISDN B1 channels CID
Default: [160] Range: 16233 Format: Numeric Default: [161] Range: 16233 Format: Numeric Default: Itut Range: N/A Format: Predefined Itut
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. 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. Specifies the encoding standard used.
ISDN B2 channels CID
Encode Standard
ITU-T standards are used for voice encoding. Use this value for voice and voiceband data defined by ITUT specifications. ATM Forum standards are used for use by voice and voiceband data. Use this value for PSTN connections. Custom encoding algorithms are not defined by standards. 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 chosen, all DSP specific parameters have to be specified by the user. If the default profile is chosen, all parameters on the AAL2 trunk, containing this CID, 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 configuration. Specifies the administrative status of the user port.
Af
Custom EncodingProfileNum Default: 1 Range: 1255 Format: Numeric
Admin Status
Default: Blocked Range: As noted below. Format: Predefined Blocked
The port is not open; no traffic can pass. If the Port Type is Pstn, the status is either Blocked or UnBlocked. The port is open; traffic can pass. If the Port Type is Pstn, the status is either Blocked or UnBlocked. The port is was open but has been administratively closed; no traffic can pass.
UnBlocked
Shutdown
Release 9.0.0 255-700-447

[ISDN Port Type]
Default: Bra Range: N/A Format: Predefined Bra Pra
Specifies whether rate interface supported is Bra or Pra. This field displays only when Port Type is Isdn. Basic rate supports 2 bearer channels and 1 data channel. Primary rate supports 30 bearer channels and 1 data channel. Specifies the type of line - permanent or leased line. This display only field appears only when Port type is Isdn. Non-permanent line. Leased line. ISDN Data Type P-Logical channel identifier which 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 configured 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. ISDN Data Type F-Logical channel identifier which must be unique for an interface Note: This configurable field displays only when Port Type selected is Isdn. Note: The value entered here must be also configured in the ConfigLogicalCChan Id field on the V5 PhysCChannel Configuration Window. The same value can be entered in the P-Logical Chan ID, the F-Logical Chan ID field, and the D-Logical Chan ID fields on the V5 User Port Configuration window. ISDN Data Type D-Logical channel identifier which must be unique for an interface Note: This configurable field displays only when Port Type selected is Isdn. Note: The value entered here must be also configured in the ConfigLogicalCChan Id field on the V5 PhysCChannel Configuration Window. The same value can be entered in the P-Logical Chan ID, the F-Logical Chan ID field, and the D-Logical Chan ID fields on the V5 User Port Configuration window.
[Line Type]
Default: NotPermLine Range: N/A Format: Predefined NotPermLine Leased
P-Logical Chan ID
F-Logical Chan ID
D-Logical Chan ID
Release 9.0.0 8-53

[Operation Status]
Default: Blocked Range: See Admin Status field Format: Predefined Default: Blocked Range: See Admin Status field Format: Predefined 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. Specifies the operational status of the user port on LE side.
[LE OperationStatus]
LES OperationStatus (display only)
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 Default: None Algo Range: N/A Format: Predefined None G726-16K G726-24K G726-32K G726-40K G729a-8K Silence Detection Default: Disabled Range: N/A Format: Predefined Enabled Disabled Echo Cancellation Algo Default: None Range: N/A Format: Predefined None G165-nearEnd G168 Specifies the user-assigned voice compression algorithm used. No compression is used on the connection. Voice compression ITU-T G.726 standard at 16-Kbps. Voice compression ITU-T G.726 standard at 24-Kbps. Voice compression ITU-T G.726 standard at 32-Kbps. Voice compression ITU-T G.726 standard at 40-Kbps. Voice compression ITU-T G.729a standard at 8-Kbps. Indicates whether support for silence detection is disabled or enabled. Support for silence detection is enabled. Support for silence detection is disabled. Specifies which echo cancellation algorithm. is used. No echo cancellation is used. ITU-T G.165-nearEnd near end echo cancellation. ITU-T G.168 echo cancellation.
Release 9.0.0 255-700-447

Tone Detection Algo
Default: Disabled Range: N/A Format: Predefined Disabled Bypass
Specifies whether fax/modem tone detection is disabled or bypassed. Fax modem tone detection is disabled. 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. Specifies which companding standard is used. A law is European; Mu law is Japanese and North American. Not companding standard is used. Companding standard is Mu law to Mu law. 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. Companding standard is Mu law to A law. Companding standard is A law to Mu law.
Translation Type
Default: None Range: N/A Format: Predefined None MuLaw2muLaw ALaw2aLaw
MuLaw2aLaw ALaw2MuLaw
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 configuration. 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
Release 9.0.0 8-55

Figure 8-21. V5 User Port Configuration Window, Port Type ISDN Selected
Release 9.0.0 255-700-447
Configuring SNMP Authentication Options

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 authentication, 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 message header. To perform authentication, a pair of SNMP engines must share an authentication key. Privacy allows the encryption of messages using the data encryption standard (DES) algorithm. Privacy can only be used in conjunction with authentication. Access control allows the restriction of access rights to only a subset of the management 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 Configuration menu option Define the remote management system using the Notification Configuration menu option
Release 9.0.0 9-1
Chapter 9 Configuring SNMP Authentication Options

Accessing SNMP Configuration Options
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 Configuration menu option Define the remote management system using the Notification Configuration 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.

To access SNMP configuration options, perform the steps in the following procedure.
Begin
1 At the Console Interface Main Menu window, select Site-Specific Configuration. The Site-Specific Menu window is displayed. 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. 3 To return to the Console Interface Main Menu window, press Ctrl+G.
End
Release 9.0.0 255-700-447

Figure 9-1. Site-Specific Menu Window, SNMP Agent Selected
Figure 9-2. SNMP Agent System-Wide Configuration Window, Non-Root User View
Release 9.0.0 9-3

Modifying an SNMP Community String Password
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 Menu Option Description
Trap Notification Configuration Displays the Notification Table window. USM User Configuration VACM Security to Group Configuration VACM Access Configuration Community String Configuration Go Back to Site-specific Menu Displays the Usm User Table window. Note: This option displays only when logged in as root. Displays the Vacm Security to Group Table window. Note: This option displays only when logged in as root. Displays the Vacm Access Table window. Note: This option displays only when logged in as root. Displays the Community String Table window. Note: This option displays only when logged in as root. Redisplays the Site-Specific Menu window.

The PSAX system has predefined two SNMPv1/v2C community strings. To modify 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.
Release 9.0.0 255-700-447

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 (see Figure 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 characters 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 Page Down Top Bottom Go Back to Previous Screen
Displays the previous page of the table. Displays the next page of the table. Displays the first page of the table. Displays the last page of the table. Redisplays the SNMP Agent System-Wide Configuration window.
Release 9.0.0 9-5

Table 9-3. Field Descriptions for the Community String Table Window Field Name Field Values Description
ReadOnlyCommu- Default: public nityString Range: 132 characters Format: ASCII characters 33126 ReadWriteCommu- Default: private nityString Range: 132 characters Format: ASCII characters 33126
The ReadOnlyCommunityString provides readonly access to the PSAX system using SNMPv1/v2C. The field value is used as an authentication password to process SNMPv1/v2C requests. The ReadWriteCommunityString provides readwrite access to the PSAX system using SNMPv1/v2C. The field value is used as an authentication password 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 Go Back to Previous Screen
Applies the change to the community string value. Redisplays the Community String Table window.
Release 9.0.0 255-700-447

Configuring the User-based Security Model (USM)
Table 9-5. Field Descriptions for the Community String Configuration Window Field Name Field Values Description
ReadOnlyCommu- Default: public nityString Range: 132 characters Format: ASCII characters 33126
The ReadOnlyCommunityString provides readonly access to the PSAX system using SNMPv1/v2C. The field value is used as an authentication password 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. The ReadWriteCommunityString provides readwrite access to the PSAX system using SNMPv1/v2C. The field value is used as an authentication password 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 anyone.
ReadWriteCommu- Default: private nityString Range: 132 characters Format: ASCII characters 33126

The PSAX system has predefined the default USM users, as shown in Table 9-6.
Table 9-6. Default USM User Information USM User Name Security Level Authentication Password Privacy Password
v3AqvUser v3readonly v3traponly v3readwrite v3superuser
AuthPriv AuthPriv NoAuthNoPriv AuthPriv AuthPriv
lucenttech2 lucenttech2 N/A lucenttech1 lucenttech1
lucenttech2 lucenttech2 N/A lucenttech1 lucenttech1
Configuring USM Users

To configure a USM user, perform the steps in the following procedure.
Release 9.0.0 9-7

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
1 On the SNMP Agent System-Wide Configuration window, select the USM User Configuration option. The Usm User Table window is displayed (see Figure 9-6). The commands for this window are described in Table 9-7. The fields for this window 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 commands for this window are described in Table 9-9. The fields for this window are described in Table 9-10. Valid ASCII characters to use for passwords are described in Table 5-8. 3 On the Usm User Creation window, enter the values in the fields according to the information provided in Table 9-10. 4 Select the Create User command. 5 Select the Go Back to Previous Screen command. The Usm User Table window is displayed, showing the new USM user.
End
Figure 9-6. Usm User Table Window
Release 9.0.0 255-700-447

Table 9-7. Commands for the Usm User Table Command Function
Page Up Page Down Top Bottom Restore Default Usm User Add New User Go Back to Previous Screen
Displays the previous page of the table. Displays the next page of the table. Displays the first page of the table. Displays the last page of the table. Resets the default USM users to the default configuration. Displays the Usm User Creation window. Redisplays the SNMP Agent System-Wide Configuration window.
Table 9-8. Field Descriptions for the Usm User Table Window Field Name Field Values Description
UsmUserName
Default: N/A Range: 132 Format: Alphanumeric
Displays the name assigned to this particular USM user.
SnmpEngineID
Default: N/A Displays the SNMP engine's administrativelyunique identifier. This value can be the agent's Range: N/A Format: Hexadecimal 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
Release 9.0.0 9-9

Table 9-9. Commands for the Usm User Creation Window Command Function
Create User Go Back to Previous Screen
Creates the USM user. Redisplays the Usm User Table window.
Table 9-10. Field Descriptions for the Usm User Creation Window Field Name Field Values Description
UserName
Specifies the name assigned to this particular USM user. You can specify alphanumeric characters 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. Specifies the SNMP engine's administrativelyunique 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 hexadecimal 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 Standalone 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.
SnmpEngineID
Default: local SNMP Engine ID Range: 12 bytes Format: Hexadecimal
Release 9.0.0 255-700-447

Table 9-10. Field Descriptions for the Usm User Creation Window (Continued) Field Name Field Values Description
Security Level
Default: NoAuthNoPriv Range: N/A Format: Predefined NoAuthNoPriv AuthNoPriv AuthPriv
Indicates the level of security for remote SNMP messages or remote SNMP operations. Authentication verifies the identity of the sender of a message by using secret key algorithms. Privacy provides encryption of the messages being sent. Indicates a security level without authentication and without privacy. Indicates a security level with authentication and without privacy. Indicates a security level with authentication and with privacy. 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 AuthNoPriv
Auth Protocol
Default: usmHMAC MD5AuthProtocol Range: N/A Format: Predefined
usmHMACMD5Aut Indicates that the authentication protocol is MeshProtocol sage-Digest 5 (MD5). usmHMACSHAAu- Indicates that the authentication protocol is thProtocol Secure Hash Algorithm (SHA). Priv Protocol Default: usmDESPrivProtocol Range: N/A Format: Predefined Indicates the type of privacy protocol used to encrypt messages. Note: This field appears when the security level is set to AuthPriv
usmDESPrivProto- Indicates that the privacy protocol is data encrypcol tion standard (DES). User Auth Password Default: N/A Range: 132 characters Format: ASCII characters 33126 Specifies the authentication password. The text string is case-sensitive. The use of the space character is not supported. See the reference appendix for a list of permitted ASCII characters. Note: This field appears when the security level is set to AuthPriv or AuthNoPriv Specifies the privacy password. The text string is case-sensitive. The use of the space character is not supported. Note: This field appears when the security level is set to AuthPriv
User Priv Password Default: N/A Range: 132 characters Format: ASCII characters 33126
Changing a USM Users Passwords

To change a password associated with a USM user, perform the steps in the following procedure.
Release 9.0.0 9-11

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
1 On the SNMP Agent System-Wide Configuration window, select the USM User Configuration option. The Usm User Table window is displayed. 2 On the Usm User Table window, select the USM user name whose password 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 its 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. 6 Select the Go Back to Previous Screen command. The Usm User Table window is displayed.
End
Figure 9-8. Usm User Key Change Configuration Window
Release 9.0.0 255-700-447

Table 9-11. Commands for the Usm User Key Change Configuration Window Command Function
Apply Key Change
Applies the password change for the specified key type.
Delete this User and Return Deletes the displayed user and redisplays the 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 Field Name Field Values Description
[UserName]
Default: N/A Range: Format: Alphanumeric
Displays the name assigned to the USM user.
[SnmpEngineID]
Default: N/A Displays the SNMP engines administrativelyunique identifier Range: N/A Format: Hexadecimal Default: N/A Range: N/A Format: Predefined usmNoAuthProtocol Displays the type of authentication protocol used.
[Auth Protocol]
Indicates that no authentication protocol is used.
usmHMACMD5Aut Indicates that the authentication protocol is MeshProtocol sage-Digest 5 (MD5). usmHMACSHAAu- Indicates that the authentication protocol is thProtocol 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- Indicates that the privacy protocol is data encrypcol tion standard (DES).
Release 9.0.0 9-13

Table 9-12. Field Descriptions for the Usm User Key Change Configuration Window (Continued) Field Name Field Values Description
Key Type
Default: Authentication Range: N/A Format: Predefined Authentication Privacy
Indicates the key type password to be changed.
Indicates that the authentication password is to be changed. Indicates that the privacy password is to be changed. Specifies the original password. See the reference appendix for a list of permitted ASCII characters.
Original Password
Default: N/A Range: 132 characters Format: ASCII characters 33126 Default: N/A Range: 132 characters Format: ASCII characters 33126
New Password
Specifies the new password. The text string is case-sensitive. The use of the space character is not supported.
Deleting USM Users

To delete a USM user, perform the steps in the following procedure.
Begin
1 On the SNMP Agent System-Wide Configuration window, select the USM User Configuration option. The Usm User Table window is displayed. 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 its 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
Release 9.0.0 255-700-447

Configuring the View-based Access Control Model (VACM)

The PSAX system has predefined the default VACM access groups shown in Table 9-13.
Table 9-13. Default VACM Access Groups VACM Group Name Security Model Security Level Read View Write View Notify View
anyone anyone anyoneRead anyoneRead readonlyGrp readwriteGrp superuserGrp v3traponlyGrp
V1 V2C V1 V2C USM USM USM USM
noAuthNoPriv PSAXView noAuthNoPriv PSAXView noAuthNoPriv PSAXView noAuthNoPriv PSAXView authPriv authPriv authPriv PSAXView PSAXView SuperuserView
PSAXView PSAXView None None None PSAXView PSAXView None
All All All All All All All All
noAuthNoPriv None
Configuring VACM Access Groups

To create a VACM access group, perform the steps in the following procedure.
Begin
1 On the SNMP Agent System-Wide Configuration window, select the VACM Access Configuration option. The Vacm Access Table window is displayed (see Figure 9-9). The commands for this window are described in Table 9-14. The fields for this window 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 this window are described in Table 9-17. 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. 5 Select the Go Back to Previous Screen command. The Vacm Access Table window is displayed.
End
Release 9.0.0 9-15

Figure 9-9. Vacm Access Table Window Table 9-14. Commands for the Vacm Access Table Window Command Function
Page Up Page Down Top Bottom Add an Entry Go Back to Previous Screen
Displays the previous page of the table. Displays the next page of the table. Displays the first page of the table. Displays the last page of the table. Displays the Vacm Access Configuration window. Redisplays the SNMP Agent System-Wide Configuration window.
Release 9.0.0 255-700-447

Table 9-15. Field Descriptions for the Vacm Access Table Window Field Name Field Values Description
Group Name
Default: N/A Range: 1-32 Format: Alphanumeric
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 created in addition to the previously existing one. Displays the security model under which access is requested. Indicates the access security model to be used is the User-based security model. Indicates that the access security model will be SNMPv1. Note: The only valid Vacm Access Security Level for V1 is noAuthNoPriv. Indicates that the access security model will be SNMPv2c. Note: The only valid Vacm Access Security Level for V2c is noAuthNoPriv. Indicates the level of security for remote SNMP messages or remote SNMP operations. Authentication verifies the identity of the sender of a message by using secret key algorithms. Privacy provides encryption of the messages being sent. Indicates a security level without authentication and without privacy. Note: This is the only valid Vacm Access Security Level for a Vacm Access Security Model of V1 or V2C. Indicates a security level with authentication and without privacy. Indicates a security level with authentication and with privacy.
Model
Default: N/A Range: N/A Format: Predefined USM V1
V2C
Security Level
Default: N/A Range: N/A Format: Predefined
noAuthNoPriv
authNoPriv authPriv
Release 9.0.0 9-17

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 Security information is created or modified. Applies when a change is made to the VACM Access View information. Deletes the entry and redisplays the Vacm Access Table window. Redisplays the Vacm Access Table window.
Delete this Entry Go Back to Previous Screen
Release 9.0.0 255-700-447

Table 9-17. Field Descriptions for the Vacm Access Configuration Window Field Name Field Values Description
Vacm Group Name Default: N/A Range: 1-32 Format: Alphanumeric
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 is case-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 created in addition to the previously existing one. Indicates the security model under which access is requested. Indicates the access security model to be used is the User-based security model Indicates that the access security model will be SNMPv1. Note: The only valid Vacm Access Security Level for V1 is noAuthNoPriv. Indicates that the access security model will be SNMPv2c. Note: The only valid Vacm Access Security Level for V2C is noAuthNoPriv. Indicates the level of security for remote SNMP messages or remote SNMP operations. Authentication verifies the identity of the sender of a message by using secret key algorithms. Privacy provides encryption of the messages being sent. Indicates a security level without authentication and without privacy. Note: This is the only valid Vacm Access Security Level for a Vacm Access Security Model of V1 or V2C. Indicates a security level with authentication and without privacy. Indicates a security level with authentication and with privacy.
Vacm Access Security Model
Default: USM Range: N/A Format: Predefined USM V1
V2C
Vacm Access Security Level
Default: noAuthNoPriv Range: N/A Format: Predefined noAuthNoPriv
authNoPriv authPriv
Release 9.0.0 9-19

Table 9-17. Field Descriptions for the Vacm Access Configuration Window (Continued) Field Name Field Values Description
Vacm Access Read View
Default: None Range: N/A Format: Predefined None PSAXView
Indicates the read privileges for the group. A read operation occurs when processing a retrieval operation. Indicates that the view group has no read access. 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 window (snmpTargetAddrTable, snmpTragetParamsTable and snmpNotifyTable). 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). 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, the Notification Configuration window (snmpTargetAddrTable, snmpTragetParamsTable and snmpNotifyTable), and the Usm User Table (usmUserTable) window. Indicates the write privileges for the group.
All
SuperuserView
Vacm Access Write View
Default: None Range: N/A Format: Predefined None PSAXView
Indicates that the view group has no write access. Indicates that the view group has write 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 window (snmpTargetAddrTable, snmpTragetParamsTable and snmpNotifyTable). Indicates that the view group has write 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).
All
Release 9.0.0 255-700-447

Table 9-17. Field Descriptions for the Vacm Access Configuration Window (Continued) Field Name Field Values Description
Vacm Access Notify Default: None View Range: N/A Format: Predefined None PSAXView
Indicates the notification privileges for the group. Notification occurs when the PSAX sends a trap. Indicates that the group has no notify access, so it will not receive any traps. 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 window and the Notification Configuration window (snmpTargetAddrTable, snmpTragetParamsTable and snmpNotifyTable). 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 Notification Table window and the Notification Configuration window (snmpTargetAddrTable, snmpTragetParamsTable and snmpNotifyTable). 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 window, the Notification Configuration window (snmpTargetAddrTable, snmpTragetParamsTable and snmpNotifyTable), and the Usm User Table (usmUserTable) window.
All
SuperuserView
Modifying VACM Access Groups

To modify a VACM access group, perform the steps in the following procedure. 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
1 On the SNMP Agent System-Wide Configuration window, select the VACM Access Configuration option. The Vacm Access Table window is displayed (see Figure 9-9).
Release 9.0.0 9-21

2 On the Vacm Access Table window, select the entry to modify and press Enter. The Vacm Access Configuration window is displayed (see Figure 9-10). 3 On the Vacm Access Configuration window, modify the values in the fields according to the information provided in Table 9-15. 4 Select the Apply/Add command. 5 Select the Go Back to Previous Screen command. 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
1 On the SNMP Agent System-Wide Configuration window, select the VACM Access Configuration option. 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. The Vacm Access Configuration window is displayed (see Figure 9-10). 3 Review the record and make sure its the one you want to delete. 4 On the Vacm Access Configuration window, select the Delete this Entry command. 5 Select the Go Back to Previous Screen 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 Model for User VACM Access Group VACM Group Security Level VACM Read VACM Write VACM View View Notify View
public private public private v3AqvUser
V1 V1 V2C V2C USM
anyoneRead anyone anyoneRead anyone readonlyGrp
noAuthNoPriv PSAXView noAuthNoPriv PSAXView noAuthNoPriv PSAXView noAuthNoPriv PSAXView AuthPriv PSAXView
None PSAXView None PSAXView None
All All All All All

Release 9.0.0 255-700-447

Table 9-18. Default VACM Access Group Assignments (Continued) User Name Security Model for User VACM Access Group VACM Group Security Level VACM Read VACM Write VACM View View Notify View
v3readonly v3traponly v3readwrite v3superuser
USM USM USM USM
readonlyGrp readwriteGrp superuserGrp
AuthPriv AuthPriv AuthPriv
PSAXView PSAXView
None None PSAXView
All All All All
v3traponlyGrp noAuthNoPriv None
Superuser- PSAXView View
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.
Table 9-19. Valid VACM Group Assignment for USM Security Level USM Security Level VACM Group Security Level noAuthNoPriv AuthNoPriv AuthPriv
noAuthNoPriv AuthNoPriv AuthPriv
Yes Yes Yes
No Yes Yes
No No Yes
To assign USM users and/or SNMP communities to VACM security groups, perform the steps in the following procedure.
Begin
1 On the SNMP Agent System-Wide Configuration window, select the VACM Security to Group Configuration option. The Vacm Security to Group Table window is displayed (see Figure 9-11). The commands for this window are described in Table 9-20. The fields for this window are described in Table 9-21. 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. 4 Select the Apply/Add command. 5 Select the Go Back to Previous Screen command. The Vacm Security to Group Table window is displayed.
End
Release 9.0.0 9-23

Figure 9-11. Vacm Security to Group Table Window Table 9-20. Commands for the Vacm Security to Group Table Window Command Function
Page Up Page Down Top Bottom Add an Entry Go Back to Previous Screen
Displays the previous page of the table. Displays the next page of the table. Displays the first page of the table. Displays the last page of the table. Displays the Vacm Security to Group Configuration window. Redisplays the SNMP Agent System-Wide Configuration window.
Release 9.0.0 255-700-447

Table 9-21. Field Descriptions for the Vacm Security to Group Table Window Field Name Field Values Description
Name
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 values 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. Displays the security model to use when accessing a PSAX from an external SNMP manager. Note: This is the security model associated with the Name, not the security model associated with the VACM group. Indicates that the security model will be SNMPv1, which supports only community strings. Indicates that the security model will be SNMPv2c, which supports only community strings. Indicates that the security model will be USM, which supports authentication and privacy. Displays the name assigned to the VACM group.
Model
Default: USM Range: N/A Format: Predefined
V1 V2C
USM Group Default: N/A Range: 132 Format: Alphanumeric
Release 9.0.0 9-25

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. Deletes this entry and redisplays the Vacm Security to Group Table window. Redisplays the Vacm Security to Group Table window.
Delete this Entry and Return Go Back to Previous Screen
Release 9.0.0 255-700-447

Table 9-23. Field Descriptions for the Vacm Security to Group Configuration Window Field Name Field Values Description
Vacm Security Name
Default: N/A Range: 1-32 Format: Alphanumeric
Specifies the VACM security name. You can specify alphanumeric characters including A-Z, a-z, 09, / (forward slash), - (hyphen), and _ (underscore). The text string is case-sensitive. The use of the 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 external SNMP manager using SNMPv3 protocol. Indicates the security model to use when accessing 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. Indicates that the security model will be V1, which supports only community strings. Indicates that the security model will be V2C, which supports only community strings. Indicates that the security model will be USM, which supports authentication and privacy. Specifies the name 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 is case-sensitive. The use of the space character is not supported. Note: This field value must match one of the Group Name values on the Vacm Access Table window. If there is no match, then you will not 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.
Vacm Security Model
Default: USM Range: N/A Format: Predefined
V1 V2C USM Vacm Group Name Default: N/A Range: 1-32 Format: Alphanumeric
Release 9.0.0 9-27

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
1 On the SNMP Agent System-Wide Configuration window, select the VACM Security to Group Configuration option. The Vacm Security to Group Table window is displayed. 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 its the one you want to modify. 4 On the Vacm Security to Group Configuration window, modify the values 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. 6 Select the Go Back to Previous Screen command. The Vacm Security to Group Table window is displayed.
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
1 On the SNMP Agent System-Wide Configuration window, select the VACM Security to Group Configuration option. The Vacm Security to Group Table window is displayed. 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. 3 Review the record and make sure its the one you want to delete. 4 Select the Delete this Entry and Return command to delete the information.
Release 9.0.0 255-700-447

Configuring SNMP Notification
The information is deleted and the Vacm Security to Group Table window is displayed.
End

You can send SNMP trap or inform messages to remote network management 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 commands 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). The commands for this window are described in Table 9-26. The fields for this window are described in Table 9-27. 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. 5 Select the Go Back to Previous Screen 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
Release 9.0.0 9-29

Figure 9-13. Notification Table Window Table 9-24. Commands for the Notification Table Window Command Function
Page Up Page Down Top Bottom Go Back to Previous Screen
Displays the previous page of the table. Displays the next page of the table. Displays the first page of the table. Displays the last page of the table. Redisplays the SNMP Agent System-Wide Configuration window.
Table 9-25. Field Descriptions for the Notification Table Window Field Name Field Values Description
Name
Default: N/A Range: NMS 1 to NMS 5 Format: Predefined
Identifies the first through fifth network management systems to which you want SNMP trap messages to be sent.
Transport Address
Default: 000.000.000. Specifies the IP address of the network manage000 ment system to which you want SNMP trap messages to be sent. Range: N/A Format: IP Address
Release 9.0.0 255-700-447

Figure 9-14. Notification Configuration Window Table 9-26. Commands for the Notification Configuration Window Command Function
Apply Go Back to Previous Screen
Sets the displayed configuration values. Redisplays the Notification Table window.
Table 9-27. Field Descriptions for the Notification Configuration Window Field Name Field Values Description
[Notify/TargetAddr Default: N/A Name] Range: NMS1 NMS5 Format: Predefined
Identifies the network management systems to which you want SNMP trap messages to be sent.
Release 9.0.0 9-31

Table 9-27. Field Descriptions for the Notification Configuration Window (Continued) Field Name Field Values Description
Notify Type
Default: V1Trap Range: N/A Format: Predefined V1Trap
Indicates the type of notification to be sent. An inform is an acknowledged notification. A trap is an un-acknowledged notification. Send SNMP traps in SNMPv1 trap format. This option does not support authentication or privacy. Send SNMP traps in SNMPv2 trap format. This option does not support authentication or privacy. Send SNMP informs in SNMPv2 inform format. This option does not support authentication or privacy. Send SNMP traps with a user-specified USM user name in SNMPv3 trap format. The user may also select a security level. 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 Creation window must be set to the remote SNMP Engine ID.
V2Trap
V2Inform
V3Trap
V3Inform
IP Address
Default: 000.000.000. Specifies the IP address of the network management system to which you want SNMP trap or 000 inform messages to be sent. Range: 000255 Format: IP Address Default: Interface Range: N/A Format: Predefined Interface Ethernet Ibm Indicates the source type of the senders IP address. Note: This field only appears when the Notify Type is set to V1Trap Use the outgoing interface's local IP address as the sender's IP address for traps. Use the Ethernet's IP address as the sender's IP address for traps. Use the inband management local IP address as the sender's IP address for traps. Indicates the maximum round trip time, in hundredths 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. Note: This field only appears when the Notify Type is set to V2Inform or V3Inform.
Source Interface
Timeout Interval
Default: 100 Range: 0214748364 7 Format: Numeric
Release 9.0.0 255-700-447

Table 9-27. Field Descriptions for the Notification Configuration Window (Continued) Field Name Field Values Description
Retry Times
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 object is ignored. Note: This field only appears when the Notify Type is set to V2Inform or V3Inform. 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). The text string is case-sensitive. The use of the space character is not supported. Note: This field only appears when the Notify Type is set to V3Trap or V3Inform. Note: 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 external SNMP manager using SNMPv3 protocol. Note: If the Notify Type is set to V3Inform, then the SnmpEngineID associated with the UsmUserName 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. Indicates the level of security for remote SNMP messages or remote SNMP operations. Authentication verifies the identity of the sender of a message by using secret key algorithms. Privacy provides encryption of the messages being sent. Note: This field only appears when the Notify Type is set to V3Trap or V3Inform. Note: This field value must match the Security Level value configured on the Usm User Creation window. If there is no match, then you will not be able to access the PSAX from an external SNMP manager using SNMPv3 protocol. Indicates a security level without authentication and without privacy. Indicates a security level with authentication and without privacy. Indicates a security level with authentication and with privacy.
Usm User Name
Security Level
Default: NoAuthNoPriv Range: N/A Format: Predefined
NoAuthNoPriv AuthNoPriv AuthPriv
Release 9.0.0 9-33

Configuring V3 Informs
Configuring SNMPv3 informs requires that you know the remote SNMP Engine ID of the system that will provide the acknowledgement. The following procedure only shows the configuration options needed for V3 Informs.
Begin
1 On the SNMP Agent System-Wide Configuration window, select the USM User Configuration option. 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, Security Level and enter the remote SnmpEngineID. By default, the local SNMP 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. 9 Select the Go Back to Previous Screen command. The Notification Configuration window is displayed.
End
Release 9.0.0 255-700-447
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. Contact 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 interface, 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 instructions, 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.)
Release 9.0.0 10-1
Chapter 10 Configuring ATM Security Agents

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, perform the 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 configuration. 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 Security 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
Release 9.0.0 255-700-447

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 Configuration ATM UNI Security Statistics Go Back to Previous Screen
Displays the ATM UNI Interface ATM Security Configuration window. Displays the ATM UNI Interface ATM Security Statistics window. Redisplays the ATM UNI Interface Configuration window.
Release 9.0.0 10-3

Table 10-2. Field Descriptions for the ATM UNI Interface ATM Security Window Field Name Field Values Description
Slot
Default: N/A Range: Depends on chassis type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: Unsupported Range: N/A Format: Predefined alphanumeric Unsupported SupportedOnSignalingPvc
Specifies the slot number containing the module, which contains the interface for which ATM security is being configured. Specifies the port number of the module for which the ATM security is being configured.
Port
Channel
Specifies the channel number for the module port for which the ATM security is being configured. Displays an indicator whether ATM security is configured for signaling PVC connections on this interface.
[ATM Security]
Indicates that ATM security is not configured for signaling PVC connections. Indicates that ATM security is configured for signaling PVC connections.
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). 2 Enter values in the fields on this window according to the information 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 Integrity-Confidentiality-ReplayReorderProtection-172 in the Service Profile field, the Confidentiality Security Service panel is displayed on the window (see Figure 10-3)
Release 9.0.0 255-700-447

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 (Integrity Security Service Only)
Figure 10-3. ATM UNI Interface ATM Security Configuration Window (Both Integrity and Confidentiality Security Services) PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 10-5


Table 10-3. Commands for the ATM UNI Interface ATM Security Configuration Window Command Function
Bring Sec Admin Status Into Service Take Sec Admin Status Out of Service Create ATM Security Configuration Delete ATM Security Configuration Reset Security Configuration Display Go Back to Previous Screen
Brings the security configuration on the specified interface into service, making the encryption operational. Takes the security configuration on the specified interface out of service, making the encryption not operational. Adds the security configuration to the specified interface. Deletes the security configuration from the specified interface. Resets the displayed values in the fields to the last set of saved values. Redisplays the ATM UNI Interface ATM Security window.

Table 10-4. Field Descriptions for the ATM UNI Interface ATM Security Configuration Window Field Name Field Values Description
Slot
Default: N/A Range: Depends on chassis type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: N/A Range: 0255 (ATM UNI); 04095 (ATM NNI) Format: Numeric Default: N/A Range: 3265535 Format: Numeric
Port
Channel
Specifies the channel number for the module port for which the ATM security is being configured. Displays the the virtual path identifier for the connection associated with the interface for which ATM security is being configured.
[VPI]
[VCI]
Displays the virtual channel identifier associated with the virtual path identifier for the connection associated with the interface for which ATM security is being configured.
Release 9.0.0 255-700-447

Service Profile
Default: Integrity172 Range: N/A Format: Predefined Integrity-172
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. Indicates that the integrity security service without replay/reordering protection will be provided to this connection.
Integrity-Confiden- Indicates that the integrity security service and tiality-172 confidentiality security service without replay/reordering protection will be provided to this connection. Indicates that the integrity security service with IntegrityReplayReorderPro- replay/reordering protection will be provided to this connection. tection-172 Integrity-Confiden- Indicates that the integrity security service and tiality-ReplayReor- confidentiality security service with replay/reorderProtection-172 dering protection will be provided to this PVC. Master Key Length Default: Key-128bits Range: 40256 Format: Predefined (bits) Master Key Specifies the length of the master key in bits. Select a value from 40 to 256 bits (in increments of 8 bits).
Default: 0 Specifies the master key that is shared between two peer security agents for integrity and/or conRange: N/A Format: Hexadecimal fidential security services. Default: MD5 Range: N/A Format: Predefined MD5 SHA-1 Displays the encryption algorithm used for encrypting session keys that need to be forwarded from this security agent to the peer security agent for this interface. Indicates that the encryption algorithm used on this interface will be MD5. Indicates that the encryption algorithm used on this interface will be SHA-1.
Integrity Security Service Panel
[SKU Encryption Algorithm]
MAC Algorithm
Default: HMACMD5 Range: N/A Format: Predefined HMAC-MD5 HMAC-SHA-1
Specifies the type of MAC algorithm that is used for integrity security service on this interface.
Indicates that the MAC algorithm used for integrity security service is HMAC-MD5. Indicates that the MAC algorithm used for integrity security service is HMAC-SHA-1.
Release 9.0.0 10-7

SessKeyLength
Default: Key-128bits Range: 40256 Format: Predefined
Specifies the length of the integrity session key. Select a value from 40 to 256 bits (in increments of 8 bits).
InitSessKeyA
Default: 0 Specifies the initial session key for integrity security service for communication from this security Range: N/A Format: Hexadecimal agent to the peer security agent (side A of the connection). The initial session key cannot be 0. Default: 0 Specifies the initial session key for integrity security service for communication from the peer Range: N/A Format: Hexadecimal security agent to this security agent (side B of the connection). The initial session key cannot be 0. Default: No-Automatic-SKU Range: N/A Format: Predefined Specifies the frequency of the session key update for integrity security service for communication from this security agent to the peer security agent.
InitSessKeyB
SKU Time Interval
No-Automatic-SKU Indicates that the session key update will be performed only by executing a manual command. Hourly Daily Weekly Indicates that the session key will be updated automatically once per hour. Indicates that the session key will be updated automatically once per day. 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 service profiles in the Service Profile field: Integrity-Confidentiality-172 Integrity-Confidentiality-ReplayReorderProtection-172 Encryption Algorithm Default: AES-128CBC Range: N/A Format: Predefined AES-128-CBC AES-192-CBC AES-256-192-CBC Triple-DES-192CBC Specifies the type of encryption algorithm used for confidentiality security service is used.
Indicates that the AES-CBC algorithm with a key length of 128 bits is used. Indicates that the AES-CBC algorithm with a key length of 192 bits is used. Indicates that the AES-CBC algorithm with a key length of 256 bits is used. Indicates that the triple-DES-CBC algorithm with a key length of 192 bits is used.
Release 9.0.0 255-700-447

InitSessKeyA
Default: 0 Specifies the initial session key for confidentiality security service for communication from this Range: N/A Format: Hexadecimal security agent to the peer security agent (side A of the connection). The initial session key cannot be 0. Default: 0 Specifies the initial session key for confidentiality security service for communication from the peer Range: N/A Format: Hexadecimal security agent to this security agent (side B of the connection). The initial session key cannot be 0. Default: No-Automatic-SKU Range: N/A Format: Predefined Specifies the frequency of the session key update for confidentiality security service for communication from this security agent to the peer security agent.
InitSessKeyB
SKU Time Interval
No-Automatic-SKU Indicates that the session key update will be performed only by executing a manual command. Hourly Daily Weekly [Sec Admin Status] Default: OutOfService Range: N/A Format: Predefined OutOfService InService Indicates that the session key will be updated automatically once per hour. Indicates that the session key will be updated automatically once per day. Indicates that the session key will be updated automatically once per week. Displays the operational status of the ATM security agent.
Indicates that the ATM security agent is out of service. Indicates that the ATM security agent is in service.
Viewing ATM Security Agent Statistics for an ATM UNI Interface

To view statistics for a configured 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 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.
Release 9.0.0 10-9

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 System 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 Apply Session Key Update for Confidentiality Security Services Reset Security Statistics Display Go Back to Previous Screen
Requests a session key update for integrity security services. Requests a session key update for confidentiality security services Resets the values in the statistics counter fields on this window to 0. Redisplays the ATM UNI Interface ATM Security window.
Release 9.0.0 255-700-447

Table 10-6. Field Descriptions for the ATM UNI Interface ATM Security Statistics Window Field Name Field Values Description
Slot
Port
Channel
[VPI]
[VCI]
Displays the virtual channel identifier associated with the virtual path identifier for the connection associated with the interface for which ATM security is being configured. Displays the current state of the ATM security agent. 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. 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. Indicates that the interface and ATM security agent for a PVC or SVC are configured, but the security negotiation process through the security message exchange protocol has been initiated but not finished. Indicates that the interface and ATM security agent for a PVC or SVC are configured, and the security negotiation process through the security message exchange protocol has been initiated and finished.
Release 9.0.0 10-11
Display Only Fields
Security Agent State
Default: Null Range: N/A Format: Predefined Null
Unavailable
Unsecured
Secure

Table 10-6. Field Descriptions for the ATM UNI Interface ATM Security Statistics Window (Continued) Field Name Field Values Description
Integrity Current Session Key A Timer Integrity Current Session Key B Timer Confidentiality Current Session Key A Timer Confidentiality Current Session Key B Timer SDU Sent
Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric
Displays the number of minutes since the session key for integrity security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of minutes since the session key for confidentiality security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of service data units sent to the upper layer. Displays the number of service data units received from the lower layer Displays the number of service data units received from the lower layer with an incorrect message authentication code. Displays the number of service data units received from the lower layer with the wrong sequence number. Displays the number of total OAM session key update cells sent by this security agent. Displays the number of total OAM session key update cells received by this security agent Displays the number of OAM session key update cells discarded by this security agent. Displays the number of mismatched session keys in duplicate session key exchange OAM cells.
SDU Received
SDU with Bad MAC Default: 0 Range: N/A Format: Numeric SDU with Bad Sequence No SKU OAM Cells Sent SKU OAM Cells Received SKU OAM Cells Discarded Duplicate SKU OAM Cells with Mismatched Keys Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric
Release 9.0.0 255-700-447

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 RCC node, perform the steps in the following procedure.
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed. 2 On the Site-Specific Menu window, select the PNNI System-Wide Configuration 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 containing 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
Release 9.0.0 10-13

Figure 10-5. PNNI Node Table Window
Figure 10-6. PNNI Node Configuration Window
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, perform the steps in the following procedure.
Release 9.0.0 255-700-447

Begin
1 On the PNNI Node Configuration window, make sure you have already created an ATM PNNI node by selecting the Create Node Entry command (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). 3 Enter values in the fields on this window according to the information provided in Table 10-8. Commands on this window are described in Table 10-7. Note: If you select the value Integrity-Confidentiality-172 or Integrity-Confidentiality-ReplayReorderProtection-172 in the Service 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 (Integrity Security Service Only)
Release 9.0.0 10-15

Figure 10-8. ATM PNNI SVCC RCC Security Configuration Window (Both Integrity and Confidentiality Security Services)

Table 10-7. Commands for the ATM PNNI SVCC RCC Security Configuration Window Command Function
Bring Sec Admin Status Into Service Take Sec Admin Status Out of Service
Brings the security configuration on the specified interface into service, making the encryption operational. Takes the security configuration on the specified interface out of service, making the encryption not operational.
Create PNNI Security Configu- Adds the security configuration to the specified interface. ration Delete PNNI Security Configu- Deletes the security configuration from the specified interration face. Reset Security Configuration Display Go Back to Previous Screen Resets the displayed values in the fields to the last set of saved values. Redisplays the PNNI Node Configuration window.
Release 9.0.0 255-700-447

Table 10-8. Field Descriptions for the ATM PNNI SVCC RCC Security Configuration Window Field Name Field Values Descriptions
[Peer Grp Id]
Default: 0 Displays the first 12 bytes (default) of the ATM address. This value, which is generated and disRange: N/A Format: Hexadecimal played by the system automatically, is the combination of the ATM address and the node level. The first byte indicates 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 its) are from the ATM address. 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.3.3, Node Identifiers. Default: Integrity172 Range: N/A Format: Predefined Integrity-172 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. Indicates that the integrity security service without replay/reordering protection will be provided to this PVC.
Service Profile
Integrity-Confiden- Indicates that the integrity security service and tiality-172 confidentiality security service without replay/reordering protection will be provided to this PVC. IntegrityIndicates that the integrity security service with ReplayReorderPro- replay/reordering protection will be provided to tection-172 this PVC. Integrity-Confiden- Indicates that the integrity security service and tiality-ReplayReor- confidentiality security service with replay/reorderProtection-172 dering protection will be provided to this PVC. Master Key Length Default: Key-128bits Range: 40256 Format: Predefined (bits) Master Key Specifies the length of the master key in bits. Select a value from 40 to 256 bits (in increments of 8 bits).
Default: 0 Spcifies the value for the master key that is shared between two peer security agents for Range: 532 Format: Hexadecimal integrity or confidential security services or both. (bits)
Release 9.0.0 10-17

Table 10-8. Field Descriptions for the ATM PNNI SVCC RCC Security Configuration Window (Continued) Field Name Field Values Descriptions
Default: MD5 Range: N/A Format: Predefined MD5 SHA-1
Specifies the encryption algorithm used for encrypting session keys that need to be forwarded from this security agent to the peer security agent. Indicates that the MD5 encryption algorithm is used for session key update. Indicates that the SHA-1 encryption algorithm is used for session key update.
IntegritySecurity Service Panel
MAC Algorithm
Indicates that the MAC algorithm used for integrity security service is HMAC-MD5. Indicates that the MAC algorithm used for integrity security service is HMAC-SHA-1. Specifies the length of the integrity session key. Select a value from 40 to 256 bits (in increments of 8 bits).
SessKeyLength
Default: Key-128bits Range: 40256 Format: Predefined (bits)
InitSessKeyA
Default: 0 Specifies the initial session key for integrity security service for communication from this security Range: 532 Format: Hexadecimal agent to the peer security agent (side A of the connection). The initial session key cannot be 0. Default: 0 Specifies the initial session key for integrity security service for communication from the peer Range: 532 Format: Hexadecimal security agent to this security agent (side B of the connection). The initial session key cannot be 0. Default: No-Automatic-SKU Range: N/A Format: Predefined Specifies the frequency of the session key update for integrity security service for communication from this security agent to the peer security agent.
InitSessKeyB
SKU Time Interval
Release 9.0.0 255-700-447

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 Algorithm Default: AES-128CBC Range: N/A Format: Predefined AES-128-CBC AES-192-CBC AES-256-192-CBC Triple-DES-192CBC InitSessKeyA Specifies the type of encryption algorithm used for confidentiality security service is used.
Default: 0 Specifies an initial session key for confidentiality security service for communication from this Range: 532 Format: Hexadecimal security agent to peer security agent. The initial session key cannot be 0. Default: 0 Specifies the initial session key for confidentiality security service for communication from peer Range: 532 Format: Hexadecimal security agent to this security agent. The initial session key cannot be 0. Default: No-Automatic-SKU Range: N/A Format: Predefined Specifies the frequency of the session key update for confidentiality security service for communication from this security agent to the peer security agent.
InitSessKeyB
SKU Time Interval
Release 9.0.0 10-19

[Sec Admin Status] Default: OutOfService Range: N/A Format: Predefined OutOfService InService
Displays the operational status of the ATM security agent.
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. 4 To view all configured ATM security agents in the PSAX system, go the procedure in the section, Viewing All ATM Security Agents in the System on page 10-45.
End
Release 9.0.0 255-700-447

Figure 10-9. PNNI SVCC RCC Information Window
Figure 10-10. ATM PNNI SVCC RCC Security Statistics Window
Release 9.0.0 10-21

Table 10-9. Commands for the ATM PNNI SVCC RCC Security Statistics Window Command Function
Requests a session key update for integrity security services. Requests a session key update for confidentiality security services Resets the values in the statistics counter fields on this window to 0. 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 Description
Slot
Port
Channel
[VPI]
[VCI]
Release 9.0.0 255-700-447

Table 10-10. Field Descriptions for the ATM PNNI SVCC RCC Security Statistics Window (Continued) Field Name Field Values Display Only Fields Description
Displays the current state of the ATM security agent. 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. 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. Indicates that the interface and ATM security agent for a PVC or SVC are configured, but the security negotiation process through the security message exchange protocol has been initiated but not finished. Indicates that the interface and ATM security agent for a PVC or SVC are configured, and the security negotiation process through the security message exchange protocol has been initiated and finished. Displays the number of minutes since the session key for integrity security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of minutes since the session key for confidentiality security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of service data units sent to the upper layer. Displays the number of service data units received from the lower layer
Unavailable
Unsecured
Secure
SDU Received
Release 9.0.0 10-23

Configuring ATM Security for ATM PNNI Interfaces
Table 10-10. Field Descriptions for the ATM PNNI SVCC RCC Security Statistics Window (Continued) Field Name Field Values Description
Displays the number of service data units received from the lower layer with an incorrect message authentication code. Displays the number of service data units received from the lower layer with the wrong sequence number. Displays the number of total OAM session key update cells sent by this security agent. Displays the number of total OAM session key update cells received by this security agent Displays the number of OAM session key update cells discarded by this security agent. Displays the number of mismatched session keys in duplicate session key exchange OAM cells.

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 the following procedure.
Begin
1 On the ATM PNNI Interface Configuration window, be sure you have already saved your configuration values by selecting the Apply Interface Configuration command. 2 Select the ATM Security command.
Release 9.0.0 255-700-447

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, Configuring an ATM Security Agent for an ATM PNNI InterfaceSignaling PVC For an ATM PNNI routing PVC interface, see the section, Configuring an ATM Security Agent for an ATM PNNI InterfaceRouting 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 - Signaling PVC
Displays the ATM PNNI Interface ATM Security Configuration - Signaling PVC window.
ATM Security Config - Routing Displays the ATM PNNI Interface ATM Security PVC Configuration - Routing PVC window. ATM Security Stats - Signaling PVC ATM Security Stats - Routing PVC Go Back to Previous Screen Displays the ATM PNNI Interface ATM Security Statistics Signaling PVC window. Displays the ATM PNNI Interface ATM Security Statistics Routing PVC window. Redisplays the ATM PNNI Interface Configuration window.
Release 9.0.0 10-25

Table 10-12 describes the fields on this table.

Table 10-12. Field Descriptions for the ATM PNNI Interface ATM Security Window Field Name Field Values Description
Slot
Default: N/A Range: Depends on chassis type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: Unsupported Range: N/A Format: Predefined alphanumeric Unsupported SupportedOnSignalingPvc SupportedOnSignalingPvcRoutingPvc
Port
Channel
Specifies the channel number for the module port for which the ATM security is being configured. Displays an indicator whether ATM security is configured for signaling PVC connections or routing PVC connections or both on this interface.
[ATM Security]
Indicates that ATM security is not configured for either signaling or routing PVC connections. Indicates that ATM security is configured only signaling PVC connections. Indicates that ATM security is configured on both signaling and routing PVC connections.
Configuring an ATM Security Agent for an ATM PNNI InterfaceSignaling PVC

To configure an ATM security agent for an ATM PNNI Signaling PVC interface, 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 PVC window is displayed (see Figure 10-12). 2 Enter values in the fields on this window according to the information provided in Table 10-14. Commands on this window are described in Table 10-13.
Release 9.0.0 255-700-447

Note:
If you select the value Integrity-Confidentiality-172 or Integrity-Confidentiality-ReplayReorderProtection-172 in the Service Profile field, the Confidentiality Security Service panel is displayed on the window (see Figure 10-13)
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 PNNI InterfaceSignaling PVC.
End
Figure 10-12. ATM PNNI Interface ATM Security Configuration Window - Signaling PVC (Integrity Security Service Only)
Release 9.0.0 10-27

Figure 10-13. ATM PNNI Interface ATM Security Configuration Window - Signaling PVC (Both Integrity Security and Confidentiality Services)

Table 10-13. Commands for the ATM PNNI Interface ATM Security Configuration - Signaling PVC Window Command Function
Brings the security configuration on the specified interface into service, making the encryption operational. Takes the security configuration on the specified interface out of service, making the encryption not operational. Adds the security configuration to the specified interface. Deletes the security configuration from the specified interface. Resets the displayed values in the fields to the last set of saved values. Redisplays the ATM PNNI Interface ATM Security window.
Release 9.0.0 255-700-447

Table 10-14. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - Signaling PVC Window Field Name Field Values Description
Slot
Default: N/A Range: Depends on chassis type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: N/A Range: Depends on module type Format: Numeric Default: N/A Range: 0255 (ATM UNI); 04095 (ATM NNI) Format: Numeric Default: N/A Range: 3265535 Format: Numeric Default: Integrity172 Range: N/A Format: Predefined Integrity-172
Port
Channel
[VPI]
[VCI]
Displays the virtual channel identifier associated with the virtual path identifier for the connection associated with the interface for which ATM security is being configured. 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. Indicates that the integrity security service without replay/reordering protection will be provided to this connection.
Service Profile
Integrity-Confiden- Indicates that the integrity security service and tiality-172 confidentiality security service without replay/reordering protection will be provided to this connection. IntegrityIndicates that the integrity security service with ReplayReorderPro- replay/reordering protection will be provided to tection-172 this connection. Integrity-Confiden- Indicates that the integrity security service and tiality-ReplayReor- confidentiality security service with replay/reorderProtection-172 dering protection will be provided to this PVC. Master Key Length Default: Key-128bits Range: 40256 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).
Release 9.0.0 10-29

Table 10-14. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - Signaling PVC Window (Continued) Field Name Field Values Description
Master Key
Default: 0 Specifies the master key that is shared between two peer security agents for integrity and/or conRange: N/A Format: Hexadecimal fidential security services. Default: MD5 Range: N/A Format: Predefined MD5 SHA-1 Displays the encryption algorithm used for encrypting session keys that need to be forwarded from this security agent to the peer security agent for this interface. Indicates that the encryption algorithm used on this interface will be MD5. Indicates that the encryption algorithm used on this interface will be SHA-1.
MAC Algorithm
Indicates that the MAC algorithm used for integrity security service is HMAC-MD5. Indicates that the MAC algorithm used for integrity security service is HMAC-SHA-1. Specifies the length of the integrity session key. Select a value from 40 to 256 bits (in increments of 8 bits).
SessKeyLength
InitSessKeyA
Default: 0 Specifies the initial session key for integrity security service for communication from this security Range: N/A Format: Hexadecimal agent to the peer security agent (side A of the connection). The initial session key cannot be 0. Default: 0 Specifies the initial session key for integrity security service for communication from the peer Range: N/A Format: Hexadecimal security agent to this security agent (side B of the connection). The initial session key cannot be 0.
InitSessKeyB
Release 9.0.0 255-700-447

SKU Time Interval
Default: No-Automatic-SKU Range: N/A Format: Predefined
Specifies the frequency of the session key update for integrity security service for communication from this security agent to the peer security agent.
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 Algorithm Default: AES-128CBC Range: N/A Format: Predefined AES-128-CBC AES-192-CBC AES-256-192-CBC Triple-DES-192CBC InitSessKeyA Specifies the type of encryption algorithm used for confidentiality security service is used.
Default: 0 Specifies the initial session key for confidentiality security service for communication from this Range: N/A Format: Hexadecimal security agent to the peer security agent (side A of the connection). The initial session key cannot be 0. Default: 0 Specifies the initial session key for confidentiality security service for communication from the peer Range: N/A Format: Hexadecimal security agent to this security agent (side B of the connection). The initial session key cannot be 0.
InitSessKeyB
Release 9.0.0 10-31

SKU Time Interval
Default: No-Automatic-SKU Range: N/A Format: Predefined
Specifies the frequency of the session key update for confidentiality security service for communication from this security agent to the peer security agent.
Viewing ATM Security Agent Statistics for an ATM PNNI InterfaceSignaling PVC
To view statistics for a configured ATM security agent for an ATM PNNI Signaling PVC interface, perform the steps in the following procedure.
Begin
1 On the ATM PNNI Interface ATM Security window, select the ATM 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
Release 9.0.0 255-700-447

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

Table 10-15. Commands for the ATM PNNI Interface ATM Security Statistics - Signaling PVC Window Command Function
Requests a session key update for integrity security services. Requests a session key update for confidentiality security services Resets the values in the statistics counter fields on this window to 0. Redisplays the ATM PNNI Interface ATM Security window.
Release 9.0.0 10-33

Table 10-16. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Signaling PVC Window Field Name Field Values Description
Slot
Port
Channel
[VPI]
[VCI]
Release 9.0.0 255-700-447

Table 10-16. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Signaling PVC Window (Continued) Field Name Field Values Display Only Fields Description
Displays the current state of the ATM security agent. 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. 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. Indicates that the interface and ATM security agent for a PVC or SVC are configured, but the security negotiation process through the security message exchange protocol has been initiated but not finished. Indicates that the interface and ATM security agent for a PVC or SVC are configured, and the security negotiation process through the security message exchange protocol has been initiated and finished. Displays the number of minutes since the session key for integrity security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of minutes since the session key for confidentiality security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of service data units sent to the upper layer.
Unavailable
Unsecured
Secure
Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric
Release 9.0.0 10-35

Table 10-16. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Signaling PVC Window (Continued) Field Name Field Values Description
SDU Received
Displays the number of service data units received from the lower layer Displays the number of service data units received from the lower layer with an incorrect message authentication code. Displays the number of service data units received from the lower layer with the wrong sequence number. Displays the number of total OAM session key update cells sent by this security agent. Displays the number of total OAM session key update cells received by this security agent Displays the number of OAM session key update cells discarded by this security agent. Displays the number of mismatched session keys in duplicate session key exchange OAM cells.
Configuring an ATM Security Agent for an ATM PNNI InterfaceRouting PVC

To configure an ATM security agent for a ATM PNNI Routing PVC interface, perform the steps in the following procedure.
Begin
1 On the ATM PNNI Interface ATM Security window, select the ATM Security Config - Routing PVC command. The ATM PNNI Interface ATM Security Configuration - Routng PVC window is displayed (see Figure 10-15). 2 Enter values in the fields on this window according to the information provided in Table 10-18. Commands on this window are described in Table 10-17. Note: If you select the value Integrity-Confidentiality-172 or Integrity-Confidentiality-ReplayReorderProtection-172 in the Service Profile field, the Confidentiality Security Service panel is displayed on the window (see Figure 10-16).
Release 9.0.0 255-700-447

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 PNNI InterfaceRouting PVC.
End
Figure 10-15. ATM PNNI Interface ATM Security Configuration - Routing PVC Window (Integrity Security Service Only)
Figure 10-16. ATM PNNI Interface ATM Security Configuration - Routing PVC Window (Both Integrity Security and Confidentiality Services) PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 10-37


Table 10-17. Commands for the ATM PNNI Interface ATM Security Configuration - Routing PVC Window Command Function
Brings the security configuration on the specified interface into service, making the encryption operational. Takes the security configuration on the specified interface out of service, making the encryption not operational. Adds the security configuration to the specified interface. Deletes the security configuration from the specified interface. Resets the displayed values in the fields to the last set of saved values. Redisplays the ATM PNNI Interface ATM Security window.

Table 10-18. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - Routing PVC Window Field Name Field Values Description
Slot
Port
Channel
[VPI]
[VCI]
Release 9.0.0 255-700-447

Table 10-18. Field Descriptions for the ATM PNNI Interface ATM Security Configuration - Routing PVC Window (Continued) Field Name Field Values Description
Service Profile
Default: Integrity172 Range: N/A Format: Predefined Integrity-172
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. Indicates that the integrity security service without replay/reordering protection will be provided to this connection.
Integrity-Confiden- Indicates that the integrity security service and tiality-172 confidentiality security service without replay/reordering protection will be provided to this connection. Indicates that the integrity security service with IntegrityReplayReorderPro- replay/reordering protection will be provided to this connection. tection-172 Integrity-Confiden- Indicates that the integrity security service and tiality-ReplayReor- confidentiality security service with replay/reorderProtection-172 dering protection will be provided to this PVC. Master Key Length Default: Key-128bits Range: 40256 Format: Predefined (bits) Master Key Specifies the length of the master key in bits. Select a value from 40 to 256 bits (in increments of 8 bits).
Specifies the master key that is shared between Default: 0 two peer security agents for integrity and/or conRange: N/A Format: Hexadecimal fidential security services. Default: MD5 Range: N/A Format: Predefined MD5 SHA-1 Displays the encryption algorithm used for encrypting session keys that need to be forwarded from this security agent to the peer security agent for this interface. Indicates that the encryption algorithm used on this interface will be MD5. Indicates that the encryption algorithm used on this interface will be SHA-1.
MAC Algorithm
Indicates that the MAC algorithm used for integrity security service is HMAC-MD5. Indicates that the MAC algorithm used for integrity security service is HMAC-SHA-1.
Release 9.0.0 10-39

SessKeyLength
Specifies the length of the integrity session key. Select a value from 40 to 256 bits (in increments of 8 bits).
InitSessKeyA
Default: 0 Specifies the initial session key for integrity security service for communication from this security Range: N/A Format: Hexadecimal agent to the peer security agent (side A of the connection). The initial session key cannot be 0. Default: 0 Specifies the initial session key for integrity security service for communication from the peer Range: N/A Format: Hexadecimal security agent to this security agent (side B of the connection). The initial session key cannot be 0. Default: No-Automatic-SKU Range: N/A Format: Predefined Specifies the frequency of the session key update for integrity security service for communication from this security agent to the peer security agent.
InitSessKeyB
SKU Time Interval
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 Algorithm Default: AES-128CBC Range: N/A Format: Predefined AES-128-CBC AES-192-CBC AES-256-192-CBC Triple-DES-192CBC Specifies the type of encryption algorithm used for confidentiality security service is used.
Release 9.0.0 255-700-447

InitSessKeyA
Default: 0 Specifies the initial session key for confidentiality security service for communication from this Range: N/A Format: Hexadecimal security agent to the peer security agent (side A of the connection). The initial session key cannot be 0. Default: 0 Specifies the initial session key for confidentiality security service for communication from the peer Range: N/A Format: Hexadecimal security agent to this security agent (side B of the connection). The initial session key cannot be 0. Default: No-Automatic-SKU Range: N/A Format: Predefined Specifies the frequency of the session key update for confidentiality security service for communication from this security agent to the peer security agent.
InitSessKeyB
SKU Time Interval
Viewing ATM Security Agent Statistics for an ATM PNNI InterfaceRouting PVC
To view statistics for a configured ATM security agent for an ATM PNNI Routing PVC interface, perform the steps in the following procedure.
Begin
1 On the ATM PNNI Interface ATM Security window, select the ATM 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.

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
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
Requests a session key update for integrity security services. Requests a session key update for confidentiality security services Resets the values in the statistics counter fields on this window to 0. Redisplays the ATM PNNI Interface ATM Security window.
Release 9.0.0 255-700-447

Table 10-20. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Routing PVC Window Field Name Field Values Description
Slot
Port
Channel
[VPI]
[VCI]
Release 9.0.0 10-43

Table 10-20. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Routing PVC Window (Continued) Field Name Field Values Display Only Fields Description
Displays the current state of the ATM security agent. 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. 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. Indicates that the interface and ATM security agent for a PVC or SVC are configured, but the security negotiation process through the security message exchange protocol has been initiated but not finished. Indicates that the interface and ATM security agent for a PVC or SVC are configured, and the security negotiation process through the security message exchange protocol has been initiated and finished. Displays the number of minutes since the session key for integrity security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of minutes since the session key for confidentiality security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of service data units sent to the upper layer.
Unavailable
Unsecured
Secure
Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric Default: 0 Range: N/A Format: Numeric
Release 9.0.0 255-700-447

Viewing All ATM Security Agents in the System
Table 10-20. Field Descriptions for the ATM PNNI Interface ATM Security Statistics - Routing PVC Window (Continued) Field Name Field Values Description
SDU Received
Displays the number of service data units received from the lower layer Displays the number of service data units received from the lower layer with an incorrect message authentication code. Displays the number of service data units received from the lower layer with the wrong sequence number. Displays the number of total OAM session key update cells sent by this security agent. Displays the number of total OAM session key update cells received by this security agent Displays the number of OAM session key update cells discarded by this security agent. Displays the number of mismatched session keys in duplicate session key exchange OAM cells.

You can view all the interfaces on which ATM security agents have been configured on the PSAX system, and the statistics for each configured ATM security agent. To view this information on the ATM Security Agents Table window, perform the steps in the following procedure.
Begin
1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window is displayed. 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.
Release 9.0.0 10-45

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 configured, 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:
End
If you have no ATM security agents configured in your PSAX system, this window does not display any table entries.
Figure 10-18. ATM Security Agents Table Window (Populated)
Table 10-21 describes the commands for this window.

Table 10-21. Commands for the ATM Security Agents Table Window Command Function
Page Up Page Down Top Bottom Find...
Displays the previous page of the table. Displays the next page of the table. Displays the first page of the table. Displays the last page of the table. 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. Redisplays the Site-Specific Menu window.
Release 9.0.0 255-700-447

Table 10-22 describes the fields for this window.

Table 10-22. Field Descriptions for the ATM Security Agents Table Window Field Name Field Values Description
Intf ID
Default: N/A Range: Depends on chassis type and module type Format: Numeric (format represents SSPPCCC [slot, port, channel]) Default: N/A Range: 0255 (ATM UNI); 04095 (ATM NNI) Format: Numeric Default: N/A Range: 3265535 Format: Numeric
Displays the identification (index) number of the interface. This interface ID is automatically assigned by the PSAX system at the time the interface is configured.
VPI
Displays the the virtual path identifier for the connection associated with the interface for which ATM security is being configured.
VCI
Release 9.0.0 10-47

Table 10-22. Field Descriptions for the ATM Security Agents Table Window (Continued) Field Name Field Values Description
Displays the current state of the ATM security agent. 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. 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. Indicates that the interface and ATM security agent for a PVC or SVC are configured, but the security negotiation process through the security message exchange protocol has been initiated but not finished. Indicates that the interface and ATM security agent for a PVC or SVC are configured, and the security negotiation process through the security message exchange protocol has been initiated and finished. Displays the first number and last number of all ATM-type connections that have ATM security encryption configured on them in the PSAX system.
Unavailable
Unsecured
Secure
Total: 0/0
Default: N/A Range: Depends on the chassis type and module type Format: Numeric
Release 9.0.0 255-700-447

Figure 10-19. ATM Security Statistics Window

Table 10-23. Commands for the ATM Security Statistics Window Command Function
Requests a session key update for integrity security services. Requests a session key update for confidentiality security services Resets the values in the statistics counter fields on this window to 0. Redisplays the ATM Security Agents Table window.
Release 9.0.0 10-49

Table 10-24. Field Descriptions for the ATM Security Statistics Window Field Name Field Values Description
Slot
Port
Channel
[VPI]
[VCI]
Displays the virtual channel identifier associated with the virtual path identifier for the connection associated with the interface for which ATM security is being configured. Displays the current state of the ATM security agent. 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. 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. Indicates that the interface and ATM security agent for a PVC or SVC are configured, but the security negotiation process through the security message exchange protocol has been initiated but not finished. Indicates that the interface and ATM security agent for a PVC or SVC are configured, and the security negotiation process through the security message exchange protocol has been initiated and finished.
Release 9.0.0 255-700-447
Display Only Fields
Unavailable
Unsecured
Secure

Table 10-24. Field Descriptions for the ATM Security Statistics Window (Continued) Field Name Field Values Description
Displays the number of minutes since the session key for integrity security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of minutes since the session key for confidentiality security service for communication from this side (side A) to the peer side (side B) of the connection was last updated. Displays the number of minutes since the session key for integrity security service for communication from the peer side (side B) to this side (side A) of the connection was last updated. Displays the number of service data units sent to the upper layer. Displays the number of service data units received from the lower layer Displays the number of service data units received from the lower layer with an incorrect message authentication code. Displays the number of service data units received from the lower layer with the wrong sequence number. Displays the number of total OAM session key update cells sent by this security agent. Displays the number of total OAM session key update cells received by this security agent Displays the number of OAM session key update cells discarded by this security agent. Displays the number of mismatched session keys in duplicate session key exchange OAM cells.
SDU Received
Release 9.0.0 10-51

Release 9.0.0 255-700-447
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. Displays the Cell Test Diagnostics window on which you can run cell test diagnostics to determine whether a specified port is operating correctly. 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 components in the chassis; and perform a switchover from the primary CPUn 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.
Cell Test Diagnostics
Reboot Hardware Components
Release 9.0.0 11-1
Chapter 11 Using System Diagnostics

Viewing System Status
Table 11-1. Menu Option Descriptions for the Diagnostics Menu Window (Continued) Menu Options Description
Remove Configuration Files
Deletes all user-created configuration data from the PSAX system. However, IP addresses that you set up on the System Identification panel of the Site-Specific Configuration window are not deleted. ! CAUTION: Be very certain you have a need to delete all your configuration 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. Displays the OAM Loopback Table window on which you can an configure an OAM loopback connection. 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. Redisplays the Console Interface Main Menu window.
OAM Loopback OAM Activate and Deactivate Go Back to Main Menu

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. The Diagnostics Menu window is displayed (see Figure 11-2). 2 Select the System Information option. The System Information window is displayed (see Figure 11-3). The display-only fields on this window are described in Table 11-3.
End
Release 9.0.0 255-700-447

Figure 11-1. Console Interface Main Menu Window (Diagnostics Option Selected)
Figure 11-2. Diagnostics Menu Window
Release 9.0.0 11-3

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. Continuously updates the information in the fields every second. Use this command to turn continuous updating on and off as needed. Redisplays the Diagnostics Menu window.
Continuous Update
Go Back to Diagnostics Screen
Table 11-3. Field Descriptions for the System Information Window Field Name Field Values Description
Version, Time and MAC Address (display only)
[Software Version]
Default: N/A Range: N/A Format: Predefined alphanumeric Default: N/A Range: N/A Format: Numeric (hours:minutes:seconds)
Displays the version of the system software currently running on the CPU.
[Current Time]
Displays the Universal Coordinated Time (UTC). This time value for the PSAX system is set on the Site-Specific Configuration window.
Release 9.0.0 255-700-447

[System Up Time]
Default: N/A Range: N/A Format: Numeric (hours:minutes:seconds) Default: N/A Range: N/A Format:
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. Displays the media access control (MAC) address of the Ethernet port of the CPU module. Displays the current status of the alarm on the PSAX system.
[MAC ADDRESS]
[Switch Alarm Sta- Default: NotAvailtus] able Range: N/A Format: Predefined alphanumeric NotAvailable None Minor Major Critical [Disc Space] Default: N/A Range: N/A Format: Numeric (kilobytes) Default: N/A Range: N/A Format: Numeric (bytes)
Indicates that the alarm status could not be retreived. Indicates that no alarm is present. Indicates that a minor alarm is present. Indicates that a major alarm is present. Indicates that a critical alarm is present. 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. 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 random access memory on the system disk of the CPU module. Displays the type of CPU module (that is, CPU1, CPU2, CPU3L, or CPU3 module) and the processor clock speed (in MHz) of the currently active (primary) CPU module. Displays the percentage of time that the CPU module is used for processing data traffic.
Primary CPU, Disc, and Memory (display only)
[Memory/RAM]
[CPU Type]
Default: (see description) Range: N/A Format: Predefined alphanumeric Default: 0.00% Range: N/A Format: Percentage
[CPU Utilization]
Release 9.0.0 11-5

[Disk Status]
Default: Ok Range: N/A Format: Ok Error
Displays the checking status of the system disk on the CPU module. Indicates that no errors on the system disk are detected. 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 used within the transmit-one-cell pool. 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. Total: Displays the number of multiple cells within the receive-multicell-pool. Used: Displays the number of multiple cells currently being used within the receive-multicellpool. High: Displays the high-water mark of multicells used within the receive-multicell-pool. 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. Plane A: Displays the status of the clock on backplane A. Plane B: Displays the status of the clock on backplane B. Plane A: Displays the status of the cell circuit on backplane A. Plane B: Displays the status of the cell circuit on backplane B.
[Rx One Cell]
[Rx Multi Cell]
[Message Pool]
Backplane A/B and Cell Bus (display only)
[Clock]
Default: Good Range: N/A Format: Predefined alphanumeric Default: Good Range: N/A Format: Predefined alphanumeric
[Cell Circuit]
Release 9.0.0 255-700-447

Checking the Module Connection Count
[Error Cells Rx]
Default: 0 Range: N/A Format: Numeric 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 module. Indicates the number of misaligned cells received since the last time you applied power to the system, or booted (initialized) the CPU module. Displays the type of format for inter-CPU file transfer.
[Misaligned]
[Inter CPU Transfer Default: Aal5 Type] Range: N/A Format: Predefined alphanumeric AAl5 Ftp Rsh Nfs
Indicates that files are transferred by AAL5. Indicates that files are transferred by FTP. Indicates that files are transferred by RSH. Indicates that files are transferred by NFS.

To view the Module Connection Count Table, perform the following procedure.
Begin
1 From the Console Interface Main Menu window, select the Diagnostics option. The Diagnostics Menu window is displayed. 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). The fields on this window are described in Table 11-5. 4 Select the Continuous Update command to update the field values. Select it again to end the updates.
End
Release 9.0.0 11-7

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 second. Use this command to turn continuous updating on and off as needed.
Go Back to System Information Redisplays the System Information window. Screen
Table 11-5. Field Descriptions for the Module Connection Count Table Window Field Name Field Values Description
Id
Default: N/A Range: Depends on chassis type Format: Numeric Default: N/A Range: -12 Format: Numeric Default: N/A Range: -12 Format: Numeric Default: N/A Range: -12 Format: Numeric
Displays the physical slot location of the module.
Input
Displays the count of input connections on the CPUn module. Displays the count of output connections on the CPUn module. Displays the count of output multicast connections on the CPUn module.
Output
Output MCast
Release 9.0.0 255-700-447

Running Cell Test Diagnostics
Table 11-5. Field Descriptions for the Module Connection Count Table Window (Continued) Field Name Field Values Description
I/O Input
Default: N/A Range: -12 Format: Numeric Default: N/A Range: -12 Format: Numeric Default: N/A Range: -12 Format: Numeric
Displays the count of input connections on the I/O module. Displays the count of output connections on the I/O module. Displays the count of output multicast connections on the I/O module.
I/O Output
I/O Output MCast

To determine whether a port is operating correctly, perform the following procedure. 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 the Diagnostics option. The Diagnostics Menu window is displayed (see Figure 11-2). 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 Figure 11-6). Table 11-8 describes the commands and Table 11-9 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.
Release 9.0.0 11-9

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 Payload Go Back to Diagnostics Menu
Applies the traffic parameters you set, and displays the Cell Test Payload Configuration window. Redisplays the Diagnostics Menu window.
Release 9.0.0 255-700-447

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 The port number on the I/O module configured with the ATM Range: depends on UNI interface you want to test. module Format: numeric
Channel Default: N/A The channel number on the I/O module configured with the (display only) Range: depends on ATM UNI interface for the port you want to test. module Format: numeric Interface Default: Unconfigured Range: N/A Format: Predefined alphanumeric Unconfigured AtmUni3-0 AtmUni3-1 AtmUni4-0 AtmIispUser AtmPnni1-0 CircuitEmulation DbCirEm PriIsdnUser PriIsdnNetwork TerminalEmulation Indicates the interface type configured on this channel. To run cell test diagnostics, use the value AtmUni4-0,AtmUni3-0, or AtmUni3-1.
Indicates that no interface has been applied. Indicates that the ATM UNI 3.0 interface is applied. Indicates that the ATM UNI 3.1 interface is applied. Indicates that the ATM UNI 4.0 interface is applied. Indicates that the ATM IISP User interface is applied. Indicates that the ATMPNNI interface is applied. Indicates that the Circuit Emulation interface is applied. Indicates that the Dynamic Bandwidth Circuit Emulation interface is applied. Indicates that the PRI ISDN User interface is applied. Indicates that the PRI ISDN Network interface is applied. Indicates that the Terminal Emulation interface is applied.
AtmIispNetwork Indicates that the ATM IISP Network interface is applied.
OperStatus Default: InService Indicates whether conditions are currently affecting the opera(display only) Range: N/A tional status of this port. Format: Predefined InService OutOfService Indicates that no conditions are preventing the port from being fully operational. Indicates that some condition is preventing the port from being configured with an interface.
Release 9.0.0 11-11

Table 11-7. Field Descriptions for the Cell Test Diagnostics Window (Continued) Field Names Values Description
AdminStatus Default: InService Indicates whether conditions are currently affecting the opera(display only) Range: N/A tional status of this interface. Format: Predefined InService OutOfService VPI Default: N/A Range: 0255 Format: Numeric Default: N/A Range: 3265535 (VCI); 161024 (DLCI) Default: 001 Range: 0255 Format: Numeric Indicates that the interface is operational. Indicates that the interface is not operational. The virtual path identifier (VPI) for the channel you want to test. The virtual channel identifier (VCI) or the data link connection identifier (DLCI) for the channel you want to test.
VCI/DLCI
VUNI
The virtual UNI (VUNI) associates itself with the egress part of the A2B or B2A side of the connection.
Service Type
Default: Ubr The service type you have set up for the connection. Vbr-nrt2 Vbr-nrt1,Vbr-rt2 Vbr-rt1 Vbr-express Cbr4 Cbr3 Cbr2 Cbr1 Default: SimplexTx SimplexRx Duplex The type of traffic flow you want to set up for the test: one-way transmit, one-way receive, or two-way flow.
Flow
[Test Status]
Default: Not-run- Indicates whether or not cell test payload is currently being ning transmitted, received, or both. Range: N/A Format: Predefined Not-running Running Indicates that the cell test payload is currently being transmitted, received, or both. Indicates that the cell test payload is not currently being transmitted, nor received.
Release 9.0.0 255-700-447

Figure 11-6. Cell Test Payload Configuration Window

Table 11-8. Commands for the Cell Test Payload Configuration Window Command Function
Apply Transmit Payload Reset Display Continuous Update
Applies the values you enter in the Transmitted Payload field. Sets the values in the Transmitted Payload field to the last saved (applied) set of values. 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). Sets the values in the [Packets Transmitted, Received, and Mismatched] fields to zero. Sends the user-selected payload one time.
Reset Cell Counters Send Payload Once
Send Payload Continuously Sends the user-selected payload continuously, 10 times per second. Delete Connection Deletes the connection you set up on the Cell Test Diagnostics 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.
Release 9.0.0 11-13

Table 11-8. Commands for the Cell Test Payload Configuration Window (Continued) Command Function
Stop Cell Test
Stops a continuously running test and deletes the connection you set up on the Cell Diagnostics window. Use this command after you have sent a test payload by using the Send Payload Continuously command. This command is displayed only after you have sent a payload continuously. Redisplays the Cell Test Diagnostics window.
Go Back to Cell Test Diagnostics
Table 11-9. Field Descriptions for the Cell Test Payload Window Field Names Values Description
[Received Payload] Default: Dependent Displays the data you entered in the Transmitted on the input in the Payload field if the port is working. Transmitted Payload field Range: N/A Format: Predefined Transmitted Payload [Protocol] Default: N/A Range: N/A Format: Predefined Default: Atm Range: N/A Format: Predefined Default: N/A Range: N/A Format: Predefined Running Not-running [Packets Transmitted] [Packets Received] Default: 0 Range: N/A Format: Predefined Default: 0 Range: N/A Format: Predefined Default: 0 Range: N/A Format: Predefined Indicates the data you want to transmit for test purposes. Indicates the type of protocol in use. ATM UNI is the only supported protocol. Indicates whether or not the cell test payload is currently being transmitted or received or both. Indicates the test is running. Indicates the test is not running. The number of packets transmitted.
[Test Status]
The number of packets received.
[Packets Mismatched]
The number of packets that are not associated with the number transmitted/number received pairs.
Release 9.0.0 255-700-447

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 following procedure. Perform the following procedure to reboot the system and apply the configuration changes performed in the previous procedures.
s
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 modifications. [Modified] is removed from the window when Save Configuration is selected. 3 Select the Diagnostics option. The Diagnostics Menu window is displayed. 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 will interrupt all traffic running on the chassis and/or the selected I/O module(s). 6 Press Y (yes) to proceed with the reboot operation, or press N to cancel the request.
Release 9.0.0 11-15

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). The system reboot takes 510 minutes, depending your system configuration. 7 After the Press RETURN to log in... message is displayed, log back into 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. 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 the equivalent to physically removing the modules from and then reinserting them into the chassis.
Reboot All I/O Cards
Release 9.0.0 255-700-447

Table 11-10. Commands for the Remote Reboot Configuration Window (Continued) Command Function
Reboot Primary CPU
! WARNING: Rebooting the PSAX system with a single (nonredundant) CPU module or component will interrupt all traffic running 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 interrupted.Reboots (reinitializes) the CPU module. This command also reboots all I/O and server modules in the chassis, 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. ! WARNING: Rebooting the PSAX system with the Reboot Chassis command will interrupt all traffic running through the PSAX chassis. Reboots the primary CPU module, the backup (standby) CPU module (if one is present), and all I/O and server modules 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.
Reboot Chassis
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 (originally the primary CPU). The green LED ACTIVE is illuminated on the primary CPU module. Used only in redundant PSAX systems. Note: Using this command does not interrupt traffic running through the PSAX chassis.
Go Back to Diagnostics Menu
Displays the Diagnostics Menu window.
Release 9.0.0 11-17

Removing Configuration Files
Removing Configuration Files

To remove configuration files, perform the following procedure. ! WARNING: The following procedure removes all configuration files from the CPU and restores the CPU to its factory default settings. All data will be removed except the CPU IP address, gateway IP address, and SNMP trap destinations.
Begin
1 On the Console Interface Main Menu window, select the Diagnostics option. The Diagnostics Menu window is displayed (see Figure 11-2). 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 condition 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. 2 On the Console Interface Main Menu window (see Figure 11-1), select the Diagnostics option. The Diagnostics Menu window is displayed (see Figure 11-2). 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 lockedup telnet session in the IP Address field,. 5 Select the Unlock Remote Shell command.
Release 9.0.0 255-700-447

Operations 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 specified in the IP Address field or to another switching device to indicate whether or not you can connect to that remote device.
End
Figure 11-8. Unlock Shell / Ping Window

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 configuration as the first port. For further information about OAM, see Chapter 3. To enable OAM connections, see the PacketStar PSAX System Connections Provisioning Guide.
Enabling OAM Loopback Functions

To enable OAM loopback functionality, perform the following procedure.
Release 9.0.0 11-19

Begin
1 On the Console Interface Main Menu window, select the Diagnostics option. The Diagnostics Menu window is displayed (see Figure 11-2). 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). 4 Enter values in the fields on this window according to the information provided in Table 11-12. 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
Scroll up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table.
Release 9.0.0 255-700-447

Table 11-11. Commands for the OAM Loopback Table Window (Continued) 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 currently displayed window. The second number indicates the total number of connection table entries for this connection type. 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. Displays the OAM Loopback window. Redisplays the Diagnostics Menu window.
Find . . .
OAM Add a Loopback Go Back to Diagnostics Menu
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 to turn 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.
Release 9.0.0 11-21

Table 11-12. Commands for the OAM Loopback Window (Continued) Command Function
Apply Action Go Back to OAM Loopback Table Screen
Applies the values you enter in this window. Redisplays the OAM Loopback Table window.
Table 11-13. Field Descriptions for the OAM Loopback Window Field Name Field Values Connection Interface Panel Description
Slot
Default: 0 Range: Depends on chassis Format: Numeric Default: 0 Range: Depends on module Format: Numeric Default: 0 Range: Depends on module Format: Numeric Default: 0 Range: Format: Numeric Default: 0 Range: Format: Numeric Default: Inactive Range: N/A Format: Predefined alphanumeric Active Successful Failure Timedout Waiting-forresponse
The module slot number of the ATM connection on which you want to perform the OAM loopback test.
Port
The port number of the ATM connection on which you want to perform the OAM loopback test.
Channel
The channel number of the ATM connection on which you want to perform the OAM loopback test.
VPI
The virtual path identifier of the ATM connection.
VCI
The virtual channel identifier of the ATM connection. Must be zero for virtual path connections.
Statistics Panel
[Test Status]
Displays the current status of the loopback test.
Indicates that the test is active. Indicates that the test is successful. Indicates that the test is a failure. Indicates that the test has timed out. Indicates that the test is waiting for a response. Indicates the total number of loopback cells transmitted on the specified connection since the last reset.
[Cells Transmitted] Default: 0 Range: N/A Format: numeric
Release 9.0.0 255-700-447

Table 11-13. Field Descriptions for the OAM Loopback Window (Continued) Field Name Field Values Description
[Cells Received]
Indicates the number of loopback cells received correctly on the specified connection since the last reset. Indicates the number of times the cells received did not matched with the cells transmitted on the specified connection since the last reset. Indicates how to perform the loopback test function selected in the OAM Loopback Type field.
[Cells Mismatched] Default: 0 Range: N/A Format: numeric OAM Loopback Action Type Default: SendLoopback Once Range: N/A Format: predefined alphanumeric SendLoopback Once StopTest ResetStats OAM Loopback Type
Sends a loopback cell. Stops the loopback test. Resets all values in the Statistics panel to zero.
Default: End-to-end Indicates the method of loopback testing performed for this PSAX device. Range: N/A Format: predefined alphanumeric 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-connectionpoint Sends a segment OAM cell within the designated physical segments, for example, two PSAX chassis, to check the connectivity between the segment connection point from where the cell was issued to the next immediate connection point. Sends a segment OAM cell to test the connectivity within segments to the specific location ID of a specific chassis. 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.
Specific-location
Destination Loopback Location ID
Default: N/A Range: N/A Format: Valid-dotted quad
OAM Activation and Deactivation

The OAM Activate and Deactivate option can perform continuity checks, as well as forward performance monitoring, and backward reporting on userdefined points along an ATM network.

To enable OAM Activation-Deactivation, perform the following procedure.

Begin
1 On the Console Interface Main Menu window, select the Diagnostics option. The Diagnostics Menu window is displayed (see Figure 11-2). 2 On the Diagnostics Menu window, select the OAM Activate and Deactivate 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). 4 Enter values in the fields on this window according to the information provided in Table 11-16. 5 To begin the test, select the Activate command. 6 To terminate the test, select the Deactivate command.
End
Figure 11-11. OAM Activate & Deactivate Table Window
Release 9.0.0 255-700-447

Table 11-14. Commands for the OAM Activate & Deactivate Table Window Command Function
Scroll up one page. Scrolls down one page. Displays entries at the top of the table. Displays entries at the bottom of the table. The first number in this field indicates the 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 connection type. 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. Displays the OAM Activation-Deactivation window. Redisplays the Diagnostics Menu window.
Find . . .
OAM Activate Go Back to Diagnostics Menu
Figure 11-12. OAM Activation Deactivation Window

Table 11-15. Commands for the OAM Activate & Deactivate Table Window Command Function
Update Status Activate
Updates the information in the Current Status panel. Starts the OAM test.
Release 9.0.0 11-25

Table 11-15. Commands for the OAM Activate & Deactivate Table Window (Continued) Command Function
Deactivate Go Back to Table Screen
Terminates the OAM test. Redisplays the OAM Activate and Deactivate Table window.
Table 11-16. Field Descriptions for the OAM Activation-Deactivation Window Field Name Field Values Connection Interface Panel Description
Slot
Default: 0 Range: Chassis dependent Format: Numeric Default: 0 Range: Chassis dependent Format: Numeric Default: 0 Range: Chassis dependent Format: Numeric Default: 0 Range: 04095 Format: Numeric Default: 0 Range: 065535 Format: Numeric
Specifies the module slot number of the ATM connection.
Port
Specifies the port number of the ATM connection.
Channel
The channel number of the ATM connection.
VPI
Specifies the virtual path identifier of the ATM connection. Specifies the virtual channel identifier of the ATM connection.
VCI
OAM Function Type
Default: Continuity- Specifies the type of method for performing the check OAM function. Range: N/A Format: Predefined alphanumeric Continuity-check Indicates that the OAM cells flow continuously throughout the length of a single connection is performed. Indicates that forward performance monitoring/backward reporting and continuity checking is performed. Indicates that forward performance monitoring and continuity checking is performed. Indicates that forward performance monitoring/backward reporting is performed. Indicates that only forward performance monitoring is performed.
Pmbr-and-cc
Pm-and-cc Fpm-and-br Fpm only
Release 9.0.0 255-700-447

Table 11-16. Field Descriptions for the OAM Activation-Deactivation Window (Continued) Field Name Field Values Description
Direction of Flow
Default: Towardsnear-end Range: N/A Format: Predefined alphanumeric Towards-near-end Both-way Towards-far-end
Specifies in which direction the OAM cells are transmitted.
Indicates that OAM cells are transmitted only towards the near end of the connection. Indicates that OAM cells are transmitted in both directions. Indicates that OAM cells are transmitted only towards the far end of the connection.
Flow Type
Default: End-to-end Specifies the distance over which the OAM cells flow in this connection. Range: N/A Format: Predefined alphanumeric End-to-end Segment Indicates that the OAM cells flow from one end of the connection to the other. Indicates that the OAM cells flow across only one segment of the connection. 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. Indicates that the block size is 128 cells. Indicates that the block size is 256 cells. Indicates that the block size is 512 cells. Indicates that the block size is 1,024 cells. Indicates that the block size is 4,098 cells. Indicates that the block size is 8,192 cells. Indicates that the block size is 16,384 cells. Indicates that the block size is 32,768 cells.
Block Size A-B
Default: 1024 Range: N/A Format: Predefined alphanumeric
Size128 Size256 Size512 Size1024 Size4098 Size8192 Size16384 Size32768
Release 9.0.0 11-27

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 when the 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. Indicates that the block size is 128 cells. Indicates that the block size is 256 cells. Indicates that the block size is 512 cells. Indicates that the block size is 1,024 cells. Indicates that the block size is 4,098 cells. Indicates that the block size is 8,192 cells. Indicates that the block size is 16,384 cells. Indicates that the block size is 32,768 cells.
Size128 Size256 Size512 Size1024 Size4098 Size8192 Size16384 Size32768 [Src Point ETE CC] Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated WaitActConfirm WaitDeactConfirm [Snk Point ETE CC] Default: Deactivated Range: N/A Format: Predefined alphanumeric
Current Status Panel
Source point end-to-end continuity checking. Displays the current status of the request for continuity checking of OAM cells from the source point end of the connection to the sink point end. Indicates that continuity checking is deactivated. Indicates that continuity checking is activated. Indicates that continuity checking will be activated pending confirmation of . Indicates that continuity checking will be deactivated pending confirmation of . Specifies how activation or deactivation of sink point end-to-end continuity checking is performed. 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. Indicates that continuity checking is deactivated. Indicates that continuity checking is activated. Indicates that continuity checking will be activated pending confirmation of . Indicates that continuity checking will be deactivated pending confirmation of .
Deactivated Activated WaitActConfirm WaitDeactConfirm
Release 9.0.0 255-700-447

[Src Point ETE PM] Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated [Snk Point ETE PM] Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated [Srce Point ETE PMBR] Default: Deactivated Range: N/A Format: Predefined alphanumeric
Specifies whether source point end-to-end performance monitoring is active or not. The current status of the request for performance monitoring of OAM cells from the source point end of the connection to the sink point end is displayed. Indicates that source point end-to-end performance monitoring is deactivated. Indicates that source point end-to-end performance monitoring is activated. Specifies whether sink point end-to-end performance monitoring is active or not. The current status of the request for performance monitoring of OAM cells from the sink point end of the connection to the source point end is displayed. Indicates that sink point end-to-end performance monitoring is deactivated. Indicates that sink point end-to-end performance monitoring is activated. Specifies whether source point end-to-end performance monitoring/backward reporting is active or not. The current status of the performance monitoring/backward reporting activation/deactivation request at the source point is displayed. Indicates that source point end-to-end performance monitoring/backward reporting is deactivated. Indicates that source point end-to-end performance monitoring/backward reporting is activated. Specifies whether sink point end-to-end performance monitoring/backward reporting is active or not. The current status of the performance monitoring/backward reporting activation/deactivation request at the sink point is displayed. Indicates that sink point end-to-end performance monitoring/backward reporting is deactivated. Indicates that sink point end-to-end performance monitoring/backward reporting is activated.
Deactivated
Activated
[Snk Point ETE PMBR]
Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated
Release 9.0.0 11-29

[Src Point SEG CC] Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated [Snk Point SEG CC] Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated [Src Point SEG PM] Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated [Snk Point SEG PM] Default: Deactivated Range: N/A Format: Predefined alphanumeric Deactivated Activated [Src Point SEG PMBR] Default: Deactivated Range: N/A Format: Predefined alphanumeric
Specifies whether source point segment continuity checking is active or not. The current status of the source points segment continuity check activation/deactivation request is displayed. Indicates that source point segment continuity checking is deactivated. Indicates that source point segment continuity checking is activated. Specifies whether sink point segment continuity checking is active or not. The current status of the sink points segment continuity check activation/deactivation request is displayed. Indicates that sink point segment continuity checking is deactivated. Indicates that sink point segment continuity checking is activated. Specifies whether source point segment performance monitoring is active or not. The current status of the source points segment performance monitoring activation/deactivation request is displayed. Indicates that source point segment performance monitoring is deactivated. Indicates that source point segment performance monitoring is activated. Specifies whether sink point segment performance monitoring is active or not. The current status of the sink points segment performance monitoring activation/deactivation request is displayed. Indicates that sink point segment performance monitoring is deactivated. Indicates that sink point segment performance monitoring is activated. Specifies whether source point segment performance monitoring/backward reporting is active or not. The current status of the source points segment forward performance monitoring/backward reporting for an activation/deactivation request is displayed. Indicates that source point segment performance monitoring/backward reporting is deactivated. Indicates that source point segment performance monitoring/backward reporting is activated.
Deactivated Activated
Release 9.0.0 255-700-447

[Snk Point SEG PMBR]
Default: Deactivated Range: N/A Format: Predefined alphanumeric
Specifies whether sink point segment performance monitoring/backward reporting is active or not. The current status of the sink points segment forward performance monitoring/backward reporting for an activation/deactivation request is displayed. Indicates thatsink point segment performance monitoring/backward reporting is deactivated. Indicates thatsink point segment performance monitoring/backward reporting is activated. Displays the reason for failure of the last activation request on this connection from the local user. Indicates that no failure occurred or no reason for failure exists. Indicates that the OAM activation request is denied. Indicates that the OAM activation request has been timed out. Indicates that the OAM activation request is successful. Displays the backward reporting of a block error on a performance monitoring connection. Displays the backward reporting of a lost inserted cell on a performance monitoring connection. Displays the backward reporting of a misinserted cell on a performance monitoring connection.
Deactivated Activated [Result Last Req] Default: None Range: N/A Format: Predefined alphanumeric None Denied Timedout Successful [BR Block Error] Default: 0 Range: 032768 Format: Numeric Default: 0 Range: 032768 Format: Numeric
[BR lost inserted cells]
[BR missed inserted Default: 0 cells] Range: 032768 Format: Numeric
Release 9.0.0 11-31

Release 9.0.0 255-700-447
12
Backing Up and Restoring PSAX 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 computer, such as a Unix or Windows-based workstation. The remote host computer 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 procedure. If no errors are found, the PSAX system moves the files from the temporary 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.
Release 9.0.0 12-1
Chapter 12 Backing Up and Restoring PSAX System Files

Choosing the Configuration Files Transfer Method
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.
Table 12-1. Tasks for Copying Database Configuration Files Between the PSAX System and a Remote Storage Medium If you are using the... you need to...
console interface (Remote copy the database configuration files from your PSAX system Database Operation win- to a remote storage medium using the procedure in Backing dow) to back up your con- Up Database Files Using the Console Interface on page 12-3.* figuration files FTP method to back up your configuration files copy the database configuration files from your PSAX system to a remote storage medium using the procedure in Backing Up Database Files Using FTP on page 12-7.
XModem or YModem file copy the database configuration files from your PSAX system to a remote storage medium using the procedure in Backing transfer method to back up your configuration files Up Database Files Using XModem/YModem Transfer on page 12-9. console interface (Remote Database Operation window) to restore your configuration files FTP method to restore your configuration 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.* copy the database configuration files to your PSAX system from a remote storage medium using the procedure in Restoring Database Files Using FTP on page 12-16.
XModem or YModem file copy the database configuration files to your PSAX system transfer method to restore from a remote storage medium using the procedure in your configuration files Restoring Database Files Using XModem/YModem File Transfer 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.
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 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; however, this protocol does not acknowledge receipt of packets. You can receive all files grouped under a subdirectory at one time.
Release 9.0.0 255-700-447

Backing Up System Database Files
The YModem protocol is a slower method of transmission, but is more reliable 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 protocol takes longer than the YModem protocol.

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 configuration modification, and prior to PSAX system software upgrades, be sure to back up the configuration files to a remote storage medium. It is recommended that you periodically back up your PSAX system configuration 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 perform the steps in the following procedure, which uses the Remote Database Operation window on the PSAX console interface. Using this procedure automatically 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 and the network, and that you have a stable connection between the network management workstation and the CPUn module. 3 Log onto the PSAX system console. 4 On the Console Interface Main Menu window, select the Remote Database Operation option. The Remote Database Operation window is displayed (see Figure 12-1).
Release 9.0.0 12-3

5 Select RemoteSave in the Operation field, and enter values in the other fields on this window according to the information provided in 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 Go Back to Main Menu
Starts the function you selected in the Operation field. Redisplays the Console Interface Main Menu window.
Release 9.0.0 255-700-447

Table 12-3. Field Descriptions for the Remote Database Operation Window Field Name Field Values Description
Remote Host IP Addr
Default: 000.000.000. 000 Range: 000255 Format: Numeric Default: N/A Range: 120 Format: Alphanumeric Default: N/A Range: 120 Format: Alphanumeric Default: N/A Range: 179 Format: Alphanumeric Default: NoOperation Range: N/A Format: Predefined alphanumeric NoOperation RemoteSave
Specifies the IP address of the remote host computer, for example, a Unix or Windows-based workstation. The remote host computer must be running as an FTP server. Specifies the user-defined login name for the remote host computer.
Login
Password
Specifies the user-defined password for the remote host computer.
Directory
Specifies the user-defined directory path on the remote host computer where you will store the PSAX system backup database files. Plan on setting aside 40 MB of disk space on the remote host computer system disk. Specifies the function you want to perform on the PSAX system database files.
Operation
Aborts the file transfer operation. This value is not currently supported. Performs a backup of the database files by transferring them from the CPU module to the userdefined 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 performed a backup. 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 successfully (DoneSuccessfully is displayed in the Oper Status field), the PSAX system immediately reboots.
RemoteLoad
Release 9.0.0 12-5

Table 12-3. Field Descriptions for the Remote Database Operation Window (Continued) Field Name Field Values Description
[Oper Status]
Default: NoActivity Range: N/A Format: Predefined alphanumeric NoActivity Working DoneSuccessfully DoneWithError Aborted
Displays the operational status indicating what activity is currently taking place.
Indicates that no operation is currently being done. Indicates that the PSAX system is currently transferring files from one location to another. Indicates that the file transfer operation was completed successfully. Indicates that the file transfer operation was attempted, but an error occurred. Indicates that the file transfer operation was aborted. This status is not currently supported. Displays the error status indicating whether an error has occurred during processing.
[Error Status]
Default: None Range: N/A Format: Predefined alphanumeric None
Indicates that no error condition was detected.
UnableToMakeFtp- Indicates that the PSAX system was not able to Connection connect with the remote host computer. InvalidDirectory Indicates that the directory name you entered does not match any directory on the remote host computer. Indicates that during the remote load (restore) operation, the PSAX system was unable to open one or more database files on the CPU module. Indicates that during the file transfer operation, an error occurred that interrupted this operation.
UnableToOpenDatabaseFile UnableToCompleteFtp
DatabaseSanityFail Indicates that during the remote load (restore) operation while sanity checking was being performed on the restored files in the temporary directory on the CPU module, the PSAX system found errors in these files. UnableToUpdateBackup Indicates that during the remote load (restore) operation, the PSAX system was not able to transfer the database files from the temporary directory to the established current directory on the CPU module.
Release 9.0.0 255-700-447

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. 2 Ensure that a standard 10Base-T Ethernet cable is connected between the Ethernet port on the primary CPUn module in the PSAX system and the network, and that you have a stable connection between the network 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-definedpassword. 5 To specify the correct path for the location of the configuration database files you are backing up from the PSAX system, enter the following command: 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 configuration file listed in Table 12-4, an error message might be displayed stating that the particular file does not exist. In this situa-
Release 9.0.0 12-7

tion, the error message is displayed because you are not using a particular feature that would have created that file on your system. 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 or Definition Filename Description
console.def ssid.def eventmgr.cfg atmvuni.db atmtrnk.db cnctn.db ecd.db erm.db features.db fwc.def gr303.db h248.db iisp.cbr iisp.vbr intfprot.db iproute.db iua.db oam.db pnnimib.db /scsi/announce/*.*
Password definitions file Site-specific identification definitions file Event management configurations file ATM virtual UNI configuration database file ATM trunking configuration database file Connection configuration database file Module configuration database file Enhanced Router module configuration file Features enabled/disabled database Firmware configuration database GR-303 configuration database H.248 configuration database IISP CBR routing table (always exists even if you have no SVCs configured) IISP VBR routing table (always exists even if you have no SVCs configured) Interface protection configuration database IP routing configuration database ISDN User Adaptation configuration database OAM configuration database PNNI configuration database Announcement files
Release 9.0.0 255-700-447

Table 12-4. PSAX System Configuration Files (Continued) PSAX Database or Definition Filename Description
spclconn.db spvc.db spvcaal2.db tasm.db trap.db v5.db vi.db vipr.db
Special connections configuration database (signaling connections) SPVC configuration database Standard AAL2 SPVC configuration database Tones and announcements configuration database SNMP trap activation database V5.2 configuration database Virtual interface configuration database VIPR task configuration database
Backing Up Database Files Using XModem/YModem Transfer

You can use the XModem/YModem file transfer method to copy the Multiservice 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 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 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 the File 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 information, 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 software, and set up the configuration preferences (see Chapter 4).
Release 9.0.0 12-9

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 the Database Files to a Remote Storage Medium
Perform the following procedure to copy the database files to a remote storage medium.
Begin
1 Using the terminal emulator, log onto the PSAX system. 2 On the Console Interface Main Menu window, select the Software Version Configuration option. The Software Version Configuration window (see Figure 12-2) is displayed.
Figure 12-2. Software Version Configuration window (XMODEM/YMODEM File Transfer Selected)
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 displayed. Note: For the database file transfer process, use only the Send Options panel on the XMODEM/YMODEM File Transfer window.
4 Enter values in the fields on this window according to the information provided in Table 12-6. The commands on this window are described in Table 12-5.
Release 9.0.0 255-700-447

5 Select the Send Files command on the XMODEM/YMODEM File Transfer 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 pressing Ctrl+X several times. A second message is displayed indicating that you must start the terminal emulator receive function. 6 Using the terminal emulator receive function, select one of the two protocol 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 workstation 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 48 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
Release 9.0.0 12-11

Figure 12-3. XMODEM/YMODEM File Transfer Window (Send Options Panel Selected) 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). Initiates the receiving function of the file transfer process to the CPUn module system disk from the CD-ROM containing the software upgrade files (running in a CD-ROM drive in a Unix or PC workstation). Redisplays the default values in the fields. Redisplays the Software Version Configuration window.
Receive File
Reset Display to System Defaults Go Back to Version Configuration
Table 12-6. Field Descriptions for the XMODEM/YMODEM File Transfer Window Field Names Field Values Description
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.
Release 9.0.0 255-700-447

Table 12-6. Field Descriptions for the XMODEM/YMODEM File Transfer Window (Continued) Field Names Field Values Receive Options Panel Description
Protocol
Default: YModem Range: N/A Format: Predefined alphanumeric YModem YModem-G XModem
Specifies the type of modem protocol used for receiving data.
Indicates that the YModem protocol is to be used for receiving the software upgrade files. Indicates that the YModem-G protocol is to be used for receiving the software upgrade files. Indicates that the XModem protocol is to be used for receiving the software upgrade files. Specifies the format of the file that will be transmitted.
File Type
Default: Binary Range: N/A Format: Predefined alphanumeric Binary Text
Indicates that the binary format is to be used. Use this format to download software upgrade files. 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. Specifies the type of error checking performed on the data received. This field is displayed only when the value XModem is selected in the Protocol field. Indicates that the error checking method is cyclical redundant checking, 16 bits. Indicates that the error checking method is arithmetic summation checking, 8 bits. Specifies the subdirectory on the CPUn module system disk where the software upgrade files are received (stored). For each subdirectory contained 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.
Error Check
Default: CRC-16 Range: N/A Format: Predefined alphanumeric CRC-16 Checksum
Directory
Default: /scsi/next/ Range: N/A Format: /scsi/next/ directoryname/
Release 9.0.0 12-13

Table 12-6. Field Descriptions for the XMODEM/YMODEM File Transfer Window (Continued) Field Names Field Values Description
Filename
Default: N/A Range: N/A Format: alphanumeric
Specifies the filename on the CPUn module system disk where the software upgrade files are received (stored). For each file contained in the package of software upgrade files, enter the filename in this field, and then receive this file on the CPUn module system disk. This field is displayed only when the value XModem is selected in the Protocol field. Note: All subdirectory and file names are listed in the readme.txt file accompanying the software upgrade files on the CD-ROM. Specifies the type of modem protocol used for sending data.
Send Options Panel
Protocol
Default: YModem Range: N/A Format: Predefined alphanumeric YModem
Indicates that the YModem protocol is to be used for sending the PSAX system files to the computer workstation where you will store your PSAX system backup. Indicates that the YModem-G protocol is to be used for sending the PSAX system files to the computer workstation where you will store your PSAX system backup. Indicates that the XModem protocol is to be used for sending the PSAX system files to the computer workstation where you will store your PSAX system backup. Specifies the format of the file that will be transmitted.
YModem-G
XModem
File Type
Indicates that the binary format is to be used. Use this format to download software upgrade files. 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.
Release 9.0.0 255-700-447

Restoring System Database Files
Packet Size
Default: 1024 Range: N/A Format: Predefined numeric (bytes) 1024 128
Specifies the size (in bytes) of the packet that will be transmitted in the data stream.
Indicates that the packet contains 1024 bytes. Indicates that the packet contains 128 bytes. Specifies the directory on the CPUn module system disk where the PSAX system configuration (database) files are stored. This directory contains the files that you want to back up on your computer workstation. Specifies the filename of the PSAX system configuration (database) file you want to back up on your computer workstation.
Directory
Default: /scsi/current/ Range: N/A Format: /scsi/next/ directoryname/ Default: N/A Range: N/A Format: alphanumeric
Filename

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 or sequentially, 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
1 Ensure that a standard 10Base-T Ethernet cable is connected between the Ethernet port on the primary CPUn module in the PSAX system and the network, and that you have a stable connection between the computer workstation on which your backup configuration files are stored and the CPUn module. 2 Log onto the PSAX system console.
Release 9.0.0 12-15

3 On the Console Interface Main Menu window, select the Remote Database 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 fields on this window according to the information provided in 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 the following procedure.
Steps to Restore Database Files Using FTP
Begin
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 modules. 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-definedpassword. 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:
Release 9.0.0 255-700-447

Note:
When you are entering put commands for each individual configuration file listed in Table 12-4, an error message might be displayed stating that the particular file does not exist. In this situation, 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 system (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 system. 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 database files to the PSAX system (see Copying the Backup Files to the PSAX System). Note: Setting Up for the File Transfer Process In an PSAX system with redundant CPUn modules, you must restore the database files to both modules.
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 information, see Upgrading Using the XModem/YModem File Transfer Method on page 13-15
Release 9.0.0 12-17

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 module. 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 Backup Files to the PSAX System
Begin
1 Using the terminal emulator, log on the PSAX system. 2 On the Console Interface Main Menu window, select the Software Version Configuration option. The Software Version Configuration window is displayed. 3 On the Software Version Configuration window, select the XMODEM/YMODEM File Transfer option. The XMODEM/YMODEM File Transfer window (see Figure 12-4) is displayed. Note: For restoring database files, use only the Receive Options panel.
4 Enter values in the fields on this window according to the information provided in Table 12-6. Commands on this window are described in 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 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 protocol types: YModem,YModem-G, 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 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
Release 9.0.0 255-700-447

Restoring 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) until you have transferred all the backup files to the CPUn module system disk. 10 Go to Rebooting the PSAX System on page 12-20
End
Figure 12-4. XMODEM/YMODEM File Transfer Window (Receive Options Panel Selected)
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:
Release 9.0.0 12-19

Rebooting the PSAX System
Table 12-7. Connecting a Cable to the Standby (Backup) CPU Module
If you are using... a redundant modem kit
do the following: set up the switching modem to establish a connection with the standby CPU2 module. connect a cable from the modem to the CONSOLE port on the standby CPU2 module.
single modem kit
2 Repeat the procedure for one of the three restoring methods in the section,Restoring System Database Files on page 12-15.
End
Rebooting the PSAX System

After 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 synchronized. To reboot the PSAX system, perform the steps in the following procedure.
Steps to Reboot the PSAX System
Begin
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 Diagnostics option. The Diagnostics Menu window is displayed. 3 On the Diagnostics Menu window, select the Reboot Hardware Components 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 modules, and all I/O and server modules in the PSAX system.
End
Release 9.0.0 255-700-447
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 operational considerations or constraints have been identified for upgrading to Release 9.0.0, these issues are addressed in that document, and instructions for 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 configuration modification, and prior to PSAX system software upgrades, be sure to back up the configuration files to a remote storage medium.
Chapter 13 Upgrading PSAX System Software

Choosing the System Software File Transfer Method
It is recommended that you periodically back up your PSAX system configuration 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 software upgrade files, which are provided on a CD-ROM.
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 the files from the CD-ROM on a remote host workstation 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).
XModem or YModem file transfer method
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; however, this protocol does not acknowledge receipt of packets. You can receive all files grouped under a subdirectory at one time. The YModem protocol is a slower method of transmission, but is more reliable 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 software upgrade files using the YModem protocol takes approximately 24 hours. Using the XModem protocol takes longer than the YModem protocol.
Release 9.0.0 255-700-447

Upgrading Using the File Transfer Protocol Method
! CAUTION: Upgrading the software on your PSAX system might affect some aspects of its operation. See the Release Note for Release 9.0.0 of the PacketStar PSAX 4500, PSAX 2300, PSAX 1250, and PSAX 1000 Multiservice Media Gateways for more information.

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 Internet web sites. If you plan to use a shareware program, you are responsible for following the terms of the authors licensing agreement, including payment. To set up your FTP server software, perform the steps in the following procedure.
Begin
1 If you are using Windows 95 or 98, obtain an FTP server software program (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 containing the drive ID and directory where the CD-ROM drive resides.
End
Downloading Software Files Using FTP

To download the system software files to your PSAX system, perform the steps in the following procedures.
Release 9.0.0 13-3

Begin
1 On the Console Interface Main Menu window (see Figure 13-1), select the Software Version Configuration option.
Figure 13-1. Console Interface Main Menu Window
The Software Version Configuration window (see Figure 13-2) is displayed.
Figure 13-2. Software Version Configuration Window PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 13-4 Release 9.0.0 255-700-447

2 Select the FTP Software Release Distribution option. The SRD Download Configuration window (see Figure 13-3) is displayed.
Figure 13-3. SRD Download Configuration Window
Commands
The commands on the SRD Download Configuration window are described in Table 13-2.
Table 13-2. Commands for the SRD Download Configuration Window Command Function
Start System Software FTP Process
Begins the software release download via the FTP connection.
Abort System Software FTP Process Stops the downloading of files. This command is displayed 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. Redisplays the Software Version Configuration window.
Go Back to Version Configuration
Field Descriptions
3 Enter values in the fields on this window according to the information provided in Table 13-3.
Release 9.0.0 13-5

Table 13-3. Field Descriptions for the SRD Download Configuration Window Field Name Field Values Description
IP Address
Default: 000.000.000.000 Range: N/A Format: numeric (valid dotted quad) Default: N/A Range: N/A Format: alphanumeric (up to 20 characters) Default: N/A Range: N/A Format: alphanumeric (up to 20 characters)
Specifies the IP address of the computer that contains the CD-ROM drive and is running the FTP client. Specifies the account name you have already set up in your FTP client software.
Account Name
Account Password
Specifies the account password you have already set up in your FTP client software.
CD-Rom File Path Default: <Enter file path here> Specifies the path for the CD-ROM drive where the new PSAX system software Range: N/A resides. Type over the default value Format: alphanumeric <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 Enter this command string if you are upgrading from a PSAX system Release 6.0.0 or later using a Unix host workstation. Lucent software license. This field is not currently supported.
/cdrom/v0900c00/upgrade.lib
License Key
Default: N/A Range: N/A Format: N/A
Release 9.0.0 255-700-447

Table 13-3. Field Descriptions for the SRD Download Configuration Window (Continued) Field Name Field Values Description
[Copy Status]
Default: NoActivity Displays the status of the file copying during the FTP download. Range: N/A Format: predefined alphanumeric NoActivity Working DoneSuccessfully DoneWithError Displayed when no copying (downloading) is taking place. Displayed when the system is copying (downloading) files to the CPUn module. Displayed when all files are successfully copied (downloaded). 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 Indicates the result of the finished or attempted software download. With the Range: N/A Format: predefined alphanumeric exception 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 status line at the bottom of the window. For descriptions of the error status code values, see the table below, Error Status Codes for the [Error Status] Field on the SRD Download Configuration Window.
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 minutes and select the Start System Software FTP Process command 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.* 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.* Displayed when an internal execution failed because a sofware message queue could not be created. Call Technical Support for assistance.* Displayed when an internal execution failed because a software task could not be created. Call Technical Support for assistance.*
FailureInCopyingDataFiles
FailureInCreatingMsgQ
FailureInSpawningTask
Release 9.0.0 13-7

Table 13-4. Error Status Code Values for the [Error Status] Field on the SRD Download Configuration Window (Continued) Field Value Description
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.* Displayed when the cyclic redundancy checking on a downloaded file failed. Call Technical Support for assistance.* 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. Displayed when the password you entered in the Account Password field does not match the one that you set up in the FTP server software on the host workstation. Verify the account password, re-enter the information, and select the Start System Software FTP Process command again. Displayed when the filename or the pathname for the PSAX system 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. 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. 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.* Displayed when the value DoneSuccessfully is displayed in the [Copy Status] field. The PSAX system software download was successful. Displayed when an internal execution failed because a software task did not respond to a command. Call Technical Support for assistance.* 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 download again by selecting the Start System Software FTP Process command. Displayed when the internal software failed because the FTP process could not locate a specific symbol in the new software being downloaded. Call Technical Support for assistance.* Displayed when the internal software failed because the FTP process could not load a specific software library. Call Technical Support for assistance.*
FileCRCFail InvalidAccountName
InvalidAccountPassword
InvalidCdromFile
InvalidIpAddress
LibraryCRCFail
None
TaskSuspendOrDead
UnableToCompleteFtp
UnableToFindTaskSymbolName UnableToLoadLibraryModule
Release 9.0.0 255-700-447

Table 13-4. Error Status Code Values for the [Error Status] Field on the SRD Download Configuration Window (Continued) Field Value Description
UnableToMakeFtpConnection
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. 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.* Displayed when a file could not be opened, for example, the disk drive failed. Call Technical Support for assistance.* Displayed when a library file could not be opened, for example, the disk drive failed. Call Technical Support for assistance.* This status is not currently used. Displayed when the system cannot write to a file, for example, the disk drive failed. Call Technical Support for assistance.* Displayed when the system cannot write to a package list file, for example, the disk drive failed. Call Technical Support for assistance.* Displayed when you decide to terminate the download process while it is running by selecting the Abort System Software FTP Process command.
UnableToMakeNextTree
UnableToOpenFile UnableToOpenLibraryFile UnableToUpdateBackup UnableToWriteFile UnableToWritePackageList
UserAbort
To call Technical Support, see Chapter 1 in this guide for contact instructions.
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, indicating 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 1520 sec after you see the message indicated in step 4), go to the next section, Upgrading the PSAX System Software.
End
Release 9.0.0 13-9

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.
Table 13-5. Determining Whether to Proceed with System Upgrade If you want to... do the following: 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- type Y (for tem upgrade 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 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, seeModule LED Indicators During Booting on page 13-12 and System Events During Booting on page 13-13.
End
Release 9.0.0 255-700-447

The migration of system software libraries and the database during the software upgrade process is shown in Figure 13-4.
FTP File Transfer Process (First Stage) Software Upgrade Process (Second Stage)
Fallback Directory /scsi/fallback/ (now contains the old version-the original contents are deleted)
Old version of software and current databases are copied
Fallback Directory /scsi/fallback/
Current Directory /scsi/current/
Current Directory /scsi/current/ (now contains the new version with the existing database files)
New version of software and current database files are copied
Current database files are copied
Next Directory /scsi/next/
Next Directory /scsi/next/ (still contains the new version until the next upgrade)
New version of software files is copied
CD-ROM
Figure 13-4. Migration of the Files During the PSAX System Upgrade
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 following procedure.
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)
Release 9.0.0 13-11

Module LED Indicators During Booting
Table 13-6. Determining Whether to Save Your Current System Configuration Before Upgrade If you... do the following: The system...
do not want to proceed with an unsaved configuration do want to proceed with an unsaved configuration
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 following this table. type Y (for yes). displays the following message:
Important Note: You Database not saved. Upgrading the software to would select yes only the next version.
in very unusual circumstances, for example, if Lucent Technologies Technical Support advises you to select this option.
The system is upgraded to the new software version without saving any configuration changes you previously made in the current console session. The PSAX system is upgraded to the software release you specified, 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 Rebooting CPUn Modules in Redundant and Nonredundant Systems on page 5-46.
If you selected the first option in Table 13-6, follow these steps to save your latest system configuration changes: 2 To return to the Console Interface Main Menu window, press Ctrl+G. 3 Select the Save Configuration (Modified) command. (The word Modified in the command indicates that you have changed the system configuration 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.

System 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 earlier than that of the primary CPUn module, the database files are incompatible 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 primary 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 Firmware Drivers

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 34 modules. The length of time you must wait for the firmware drivers to download before performing any of actions, listed in the following Caution, on the PSAX system is described in Table 13-7.
Release 9.0.0 13-13

Verifying Successful Downloading of Module Firmware Drivers
Table 13-7. Length of Time Required for Firmware Downloading If you are upgrading a... then wait the following period of time for the firmware drivers to download...
PSAX 1000, PSAX 1250, or PSAX 2300 system PSAX 4500 system
5 minutes per Stratum 34 module 30 minutes per Stratum 34 module
! CAUTION: You must wait a sufficient length of time for the new firmware drivers to be completely and successfully downloaded to I/O, server, and Stratum 34 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 primary CPUn module Restoring your database files from a separate storage medium to the PSAX system using the Remote Database Operation window Changing any configuration values You can verify successful firmware downloading by viewing both the Firmware 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 Firmware 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 Version 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, Manually Selecting 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 Configuration 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.

Upgrading 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 34 module(s).
End

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 emulation software on the PC workstation, and ensuring you have communication 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; however, this protocol does not acknowledge receipt of packets. You can receive all files grouped under a subdirectory at one time. The YModem protocol is a slower method of transmission, but is more reliable 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 software upgrade files using the YModem protocol takes 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.

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.
Table 13-8. Setting Up the Connection Between the PC Workstation, the Local Modem, 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. modem port on the PC workstation to the telephone jack.
internal modem
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.
Table 13-9. Setting Up the Connection Between the Modem and the PSAX System Connect a cable from the... CONSOLE port on the primary CPUn module to the...
modem. telephone jack.
modem
3 On the PC workstation, start up the VT100 terminal emulation software, and set up the configuration preferences. See any PacketStar PSAX Multiservice 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. 2 On the Console Interface Main Menu window, select the Software Version Configuration option.
Release 9.0.0 255-700-447

The Software Version Configuration window (see Figure 13-5) is displayed.
Figure 13-5. Software Version Configuration Window (XMODEM/YMODEM File Transfer Selected)
3 On the Software Version Configuration window, select the XMODEM/YMODEM File Transfer option. The XMODEM/YMODEM File Transfer window (see Figure 13-6) is displayed.
Release 9.0.0 13-17

Figure 13-6. XMODEM/YMODEM File Transfer Window (Receive Options Panel Selected)
Commands
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). Initiates the receiving function of the file transfer process to the CPUn module system disk from the CD-ROM containing the software upgrade files (running in a CD-ROM drive in a Unix or PC workstation). Redisplays the default values in the fields. Redisplays the Software Version Configuration window.
Receive File
Reset Display to System Defaults Go Back to Version Configuration
Field Descriptions
4 Enter values in the fields on this window according to the information provided in Table 13-11.
Release 9.0.0 255-700-447

Table 13-11. Field Descriptions for the XMODEM/YMODEM File Transfer Window Field Names Field Values Description
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
Protocol
Default: YModem Range: N/A Format: Predefined alphanumeric YModem YModem-G XModem
Specifies the type of modem protocol used for receiving data.
Indicates that the YModem protocol is to be used for receiving the software upgrade files. Indicates that the YModem-G protocol is to be used for receiving the software upgrade files. Indicates that the XModem protocol is to be used for receiving the software upgrade files. Specifies the format of the file that will be transmitted.
File Type
Indicates that the binary format is to be used. Use this format to download software upgrade files. 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. Specifies the type of error checking performed on the data received. This field is displayed only when the value XModem is selected in the Protocol field. Indicates that the error checking method is cyclical redundant checking, 16 bits. Indicates that the error checking method is arithmetic summation checking, 8 bits. Specifies the subdirectory on the CPUn module system disk where the software upgrade files are received (stored). For each subdirectory contained 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.
Error Check
Default: CRC-16 Range: N/A Format: Predefined alphanumeric CRC-16 Checksum
Directory
Default: /scsi/next/ Range: N/A Format: /scsi/next/ directoryname/
Release 9.0.0 13-19

Filename
Default: N/A Range: N/A Format: alphanumeric
Specifies the filename on the CPUn module system disk where the software upgrade files are received (stored). For each file contained in the package of software upgrade files, enter the filename in this field, and then receive this file on the CPUn module system disk. This field is displayed only when the value XModem is selected in the Protocol field. Note: All subdirectory and file names are listed in the readme.txt file accompanying the software upgrade files on the CD-ROM. Specifies the type of modem protocol used for sending data.
Send Options Panel
Protocol
Default: YModem Range: N/A Format: Predefined alphanumeric YModem
Indicates that the YModem protocol is to be used for sending the PSAX system files to the computer workstation where you will store your PSAX system backup. Indicates that the YModem-G protocol is to be used for sending the PSAX system files to the computer workstation where you will store your PSAX system backup. Indicates that the XModem protocol is to be used for sending the PSAX system files to the computer workstation where you will store your PSAX system backup. Specifies the format of the file that will be transmitted.
YModem-G
XModem
File Type
Indicates that the binary format is to be used. Use this format to download software upgrade files. 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.
Release 9.0.0 255-700-447

Packet Size
Default: 1024 Range: N/A Format: Predefined numeric (bytes) 1024 128
Specifies the size (in bytes) of the packet that will be transmitted in the data stream.
Indicates that the packet contains 1024 bytes. Indicates that the packet contains 128 bytes. Specifies the directory on the CPUn module system disk where the PSAX system configuration (database) files are stored. This directory contains the files that you want to back up on your computer workstation. Specifies the filename of the PSAX system configuration (database) file you want to back up on your computer workstation.
Directory
Default: /scsi/current/ Range: N/A Format: /scsi/next/ directoryname/ Default: N/A Range: N/A Format: alphanumeric
Filename
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 message 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 protocol 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 of the XMODEM/YMODEM File Transfer window (see Figure 13-6). 7 In the terminal emulator field for the location of the file, specify the drive 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 filename if using XModem) exactly so that it matches the names you previously 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.
Release 9.0.0 13-21

Manually Selecting I/O and Server Module Firmware Drivers
9 Repeat steps 48 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:
End
The new version of the software and the existing database files are now resident in the directory /scsi/next/ (see Figure 13-4).
Upgrading the PSAX System Software

Perform the steps in the following procedure to upgrade your system software.
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. The following message is displayed in the status line:
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 During 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.
End

PacketStar 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.
Release 9.0.0 255-700-447

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 following procedure.
Begin
1 On the Console Interface Main Menu window (see Figure 13-7), select the Software Version Configuration option. The Software Version Configuration window is displayed.
Figure 13-7. Console Interface Main Menu Window (Software Version Configuration Option Selected)
2 On the Software Version Configuration window (see Figure 13-8), select the Firmware Version Control option. The Firmware Version Control window is displayed.
Release 9.0.0 13-23

Figure 13-8. The Software Version Configuration Window (Firmware Version Control Selected)
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, perform 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 download 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 displayed 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 correspond 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 module. 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 scenarios.
Release 9.0.0 255-700-447

Table 13-12. Selecting Firmware Drivers If you... do the following:
select the default driver, select a nondefault driver,
Install any I/O or server module into the PSAX chassis slot. 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 Start Upgrade command on the Firmware Version Control window. 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.
want to install an I/O or server module into a particular slot that was formerly occupied by a different module configured in that slot,
End
Release 9.0.0 13-25

Figure 13-9. Firmware Version Control Window
Commands
Table 13-13. Commands for the Firmware Version Control Window Command Function
Update Screen Start Upgrade
Refreshes the values on this window to display the current firmware configuration for all modules in the system. Initiates the downloading of firmware by the selected driver in the NextVersion field.
Back to Software Config- Redisplays the Software Version Configuration window. uration
Field Descriptions
Release 9.0.0 255-700-447

Table 13-14. Field Descriptions for the Firmware Version Control Window Field Name Field Values Description
Slot
Default: N/A Displays the chassis slot in which the I/O, server, Range: chassis depen- or Stratum34 module is installed. dent Format: Numeric Default: N/A Range: N/A Format: Predefined alphanumeric Default: N/A Range: dependent on installed software version Format: Predefined alphanumeric Displays the name of the I/O or server module in the slot.
Card Type
Current Ver
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 filename indicates the default version of the driver for this module.
Release 9.0.0 13-27

Table 13-14. Field Descriptions for the Firmware Version Control Window (Continued) Field Name Field Values Description
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 system 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 software 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 Indicates that the firmware downloading on the module was complete and successful. Indicates that the new firmware is currently being downloaded. 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. Indicates that a request to download the firmware was made but no reply from the module was received during the designated time period. Indicates that a request to download the firmware was made and the system is waiting for a response from the module. Indicates that the attempt to download the new firmware failed.
Done Progress Retry
ReqRepTimeout
RequestPending
Failed
RemoveCardBefore Indicates that while the firmware was being Finish 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. Indicates that one type of stratum module was configured in this slot in the chassis, but now a different stratum module occupies this slot.
WrongCardSType
Release 9.0.0 255-700-447

Table 13-14. Field Descriptions for the Firmware Version Control Window (Continued) Field Name Field Values Description
NextVersion
Default: N/A Range: dependent on installed software version Format: 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. Displays the type of firmware download action the PSAX system performed on the firmware driver currently displayed in the Current Ver field. Indicates that no firmware driver downloading has taken place. Indicates that the firmware driver displayed in the Current Ver field was downloaded as a normal function of a PSAX system software upgrade. 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.
Dnld Cmd
Default: None Range: N/A Format: Predefined alphanumeric None normalDownload
forceDownload
Downloading a Firmware Driver

After you have selected the firmware driver you want to use on a selected module, 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 displayed 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 Configuration option.
Release 9.0.0 13-29

The Equipment Configuration window is displayed. Updated information in the SW Version field is displayed for the newly updated module. A confirmation message is displayed in the status line at the bottom of the window.
End
Release 9.0.0 255-700-447
Common Equipment Module Connections
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.
Table A-1. CPU4 Module CONSOLE Connector Pin Assignments Pin Description
2 3 4
TXD (from CPU4) RXD (to CPU4) Ground
A console cable (straight-thru, pins 16) and console cable adapters are supplied 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 interfaces 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.
8 7 6 5 4 3 2 1 Figure A-1. ETHERNET1 and ETHERNET2 Connector Pin Locations
Table A-2 lists the pin assignments for the ETHERNET1 and ETHERNET2 connectors on the faceplate.
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 A-1
Appendix A Common Equipment Module Connections

Table A-2. CPU4 Module ETHERNET1 and ETHERNET2 Connector Pin Assignments Pin Description
1 2 3 4 5 6 7 8
TD+ (CPU4 transmit+) TD (CPU4 transmit) RD+ (CPU4 receive+) Reserved Reserved RD (CPU4 receive) Reserved Reserved

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.
Table A-3. CPU2 Module CONSOLE Connector Pin Assignments Pin Description
2 3 4
TXD (from CPU2) RXD (to CPU2) Ground
A console cable (straight-thru, pins 16) and console cable adapters are supplied 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.
1 2 3 4 5 6 7 8
Figure A-2. ETHERNET Connector Pin Locations PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 A-2
Release 9.0.0 255-700-447

Console Cable Adapters
The CPU2 module ETHERNET connector does not follow the standard Ethernet 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 simultaneous 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.
Table A-4. CPU2 Module ETHERNET Connector Pin Assignments Pin Description
1 2 3 4 5 6 7 8
TD+ (CPU2 transmit+) TD (CPU2 transmit) RD+ (CPU2 receive+) Reserved Reserved RD (CPU2 receive) Reserved Reserved
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 adapter and Table A-6 describes the pin assignments for RJ-12-to-DB25 adapter.
Table A-5. RJ-12-to-DB9 Adapter Pin Assignments RJ-12 Pins DB9 Pins Description
2 3 4
2 3 5
TX (CPU transmit) RX (CPU receive) Ground
Table A-6. RJ-12-to-DB25 Adapter Pin Assignments RJ-12 Pins DB25 Pins* Description
2 3 4
*
2 3 7
TX (CPU transmit) RX (CPU receive) Ground
Pins 4 (RTS) and 5 (CTS) are jumpered together and pins 6 (DSR) and 20 (DTR) are jumpered together.
Release 9.0.0 A-3

Stratum 34 Connector
Stratum 34 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 on the Stratum 34 module.
Table A-7. Stratum 34 Module RJ-45 Connector Pin Assignments Pin Description
1 2 3 4 5 6 7 8
IN (ring) IN (tip) Not Used Not Used Not Used Frame Ground Not Used Not Used
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.
Pin 18 Pin 26
26 18 9
Pin 9
19
10
Pin 19
Pin 1 Pin 10
Figure A-3. ALARM Connector Pin Locations on the Alarm Module PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 A-4 Release 9.0.0 255-700-447

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).
Figure A-4. ALARM Cable with 26-Pin Connector and Pigtail
The pin assignments for the ALARM connector and the shielded Lucent cable pigtail color code are described in Table A-8.
Table A-8. ALARM Connector Pin Assignments and Cable Pigtail Color Code (COMCODE 300164290) Connector Pin Description Cable Pigtail Color Code*
2 13 1 4 14 3 6 15 5 20 26 24 23 19 21 22 25 8 16 7 10 17 9
Audible Critical Alarm COM contact Audible Critical Alarm NC contact Audible Critical Alarm NO contact Audible Major Alarm COM contact Audible Major Alarm NC contact Audible Major Alarm NO contact Audible Minor Alarm COM contact Audible Minor Alarm NC contact Audible Minor Alarm NO contact Battery Return** Frame Ground Remote Alarm Cutoff Battery Return Remote Alarm Cutoff input Unused Unused Unused Unused Visible Critical Alarm COM contact Visible Critical Alarm NC contact Visible Critical Alarm NO contact Visible Major Alarm COM contact Visible Major Alarm NC contact Visible Major Alarm NO contact

White/Brown White/Violet White/Tan White/Pink White/Gray Brown/White White/Orange Tan/Brown Pink/White Orange/Tan Yellow/Tan Pink/Tan Brown/Tan Tan/Orange Violet/White Gray/White Tan/Yellow White/Yellow Tan/Pink Orange/White Tan/White Yellow/White White/Green
Release 9.0.0 A-5

Table A-8. ALARM Connector Pin Assignments and Cable Pigtail Color Code (COMCODE 300164290) (Continued) Connector Pin Description Cable Pigtail Color Code*
12 18 11
*
Visible Minor Alarm COM contact Visible Minor Alarm NC contact Visible Minor Alarm NO contact
Blue/White Green/White 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.
STATUS/CONTROL Connector
Figure A-5 illustrates the pin locations of the 44-pin STATUS/CONTROL connector on the Alarm module (model 20N79) faceplate.
30 44 43 42 41
STATUS/CONTROL
15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
29 28 27 26 25 24 23 22 21 20 19 18 17 16
40 39 38 37 36 35 34 33 32 31
Pin 1
Figure A-5. Pin Locations for the STATUS/CONTROL Connector on the Alarm Module
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).
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 A-6
Release 9.0.0 255-700-447

Figure A-6. STATUS/CONTROL Cable with 44-Pin Connector and Pigtail
The pin assignments for the STATUS/CONTROL connector and the shielded Lucent cable pigtail color code are described in Table A-9.
Table A-9. STATUS/CONTROL Connector Pin Assignments and Cable Pigtail Color Code (COMCODE 300164282) Connector Pin Description Cable Pigtail Color Code*
43 32 33 31 36 34 35 38 39 37 42 40 41 44 1 2 3 4 5 6 7 8 9 10 11 12
Battery Return Control Output 1 COM contact Control Output 1 NC contact Control Output 1 NO contact Control Output 2 COM contact Control Output 2 NC contact Control Output 2 NO contact Control Output 3 COM contact Control Output 3 NC contact Control Output 3 NO contact Control Output 4 COM contact Control Output 4 NC contact Control Output 4 NO contact Frame Ground Status Input 01 Battery Return Battery Return Status Input 03 Battery Return Status Input 04 Battery Return Status Input 05 Battery Return Status Input 06 Battery Return

Brown/Blue Violet/Tan Tan/Gray Tan/Violet Pink/Brown Gray/Tan Brown/Pink Orange/Brown Brown/Yellow Brown/Orange Green/Brown Yellow/Brown Brown/Green Blue/Brown White/Tan Tan/White White/Brown Brown/White White/Pink Pink/White White/Orange Orange/White White/Yellow Yellow/White White/Green Green/White
Release 9.0.0 A-7
Status Input 02

Table A-9. STATUS/CONTROL Connector Pin Assignments and Cable Pigtail Color Code (COMCODE 300164282) (Continued) Connector Pin Description Cable Pigtail Color Code*
13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
*
Status Input 07 Battery Return Status Input 08 Battery Return Status Input 09 Battery Return Status Input 10 Battery Return Status Input 11 Battery Return Status Input 12 Battery Return Status Input 13 Battery Return Status Input 14 Battery Return Status Input 15 Battery Return
White/Blue Blue/White White/Violet Violet/White White/Gray Gray/White Tan/Brown Brown/Tan Tan/Pink Pink/Tan Tan/Orange Orange/Tan Tan/Yellow Yellow/Tan Tan/Green Green/Tan Tan/Blue 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.
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 A-8
Release 9.0.0 255-700-447
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 managed). 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 connections. 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 system 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.
Release 9.0.0 B-1
Appendix B Configuring In-Band Management

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).
Node E ATM PVC Connections
PSAX PSAX
Node C
PSAX PSAX
PSAX
NMS (Generic Router) Node B
PSAX
Node D
PSAX PSAX
PSAX
Node A ATM PVC Connections
PSAX PSAX PSAX PSAX PSAX
ATM PVC Connections Physical Connections via Ethernet LAN

Figure B-1. Direct Connection Configuration Diagram
PSAX
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 the SUN 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:
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 B-2
Release 9.0.0 255-700-447

ifconfig fa0 forecard_Ip_Address netmask Netmask broadcast Bcast_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, 9180refer to RFC 1577) 3 To test whether the FORE card has been configured correctly, type the following command: ifconfig fa0 Consult your FORE users 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 procedure 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
Release 9.0.0 B-3

Using the Routed Connection Configuration
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 cards IP address. 3 If the remote PSAX systems in-band interface IP address is not in the same subnet as that of the FORE cards IP address, then a route entry should be added on the SUN machine for the remote PSAX systems subnet, 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 machines 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 points IP address (that is, the Cisco routers address). 7 The gateway IP address should be either an Ethernet subnet or an inband 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

No default gateway through an in-band network should be configured on any of the PSAX systems.
Release 9.0.0 255-700-447

Node E
PSAX PSAX
NMS ATM PVC Connections Node C Intermediate Router
PSAX PSAX PSAX PSAX
PSAX
Node B Intermediate Router
PSAX
Node D
PSAX
NMS Node A Main Router Ethernet or ATM PVC Connections NMS ATM PVC Connections Physical Connections via Ethernet LAN
PSAX PSAX PSAX PSAX PSAX PSAX
Figure B-2. Routed Connection Configuration Diagram
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 connected through Ethernet to the router PSAX system. The router PSAX system has direct or routed in-band connections to the remote PSAX system. Log in as root on the SUN machine and add a routing table entry using 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 systemnode 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 connections 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 downstream 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).
Release 9.0.0 B-5

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 system), the Ethernet interface IP network should be different from the SUN machines 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 Ethernet 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 system 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 connection 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 configured 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 stations network address range. Perform the following procedure to set PVC connections for a routed connection.
Release 9.0.0 255-700-447

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 Primary IP Mask: 255.255.000.000 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 interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.001.001.003 Primary IP Mask: 255.255.255.000 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 network 20.0.0.0. For example, mask 255.255.255.0 is assigned for downstream connections 4 Configure the primary IP Address for in-band management on the CPUn module of main router PSAX system (Node D) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.001.002.001 Primary IP Mask: 255.255.255.000
Release 9.0.0 B-7

5 Configure the primary IP Address for in-band management on the CPUn module of the main router PSAX system (Node E) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.001.001.004 Primary IP Mask: 255.255.255.000 6 Configure the primary IP address for in-band management on the CPUn module of the main router PSAX system (Node X) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.002.001.001 Primary IP Mask: 255.255.000.000 7 Configure the primary IP Address for in-band management on the CPUn module of the main router PSAX system (Node Y) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.002.001.002 Primary IP Mask: 255.255.255.000 8 Configure the primary IP Address for in-band management on the CPUn module of main router PSAX system (Node Z) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.002.002.001 Primary IP Mask: 255.255.255.000 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 Connection 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
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 B-8 Release 9.0.0 255-700-447

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: 1 13 Verify that a routing table entry from the SUN machines network to network 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
Release 9.0.0 B-9

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 all remote PSAX systems (that is, all PSAX systems except Node A) with the IP address of Node As in-band interface. In this case, in-band connections on remote PSAX systems should be configured with Node As in-band IP address and a default gateway should be set to Node As in-band IP address.
Node E ATM PVC Connections
PSAX PSAX
Node C
PSAX PSAX
NMS
PSAX
Node B Remote PSAX
PSAX
Node D
PSAX PSAX
PSAX
NMS Node A Main Router Ethernet Connections NMS
PSAX PSAX PSAX PSAX PSAX PSAX
ATM PVC Connections Physical Connections via Ethernet LAN Figure B-3. Hybrid Connection Configuration Diagram
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
Release 9.0.0 255-700-447

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 connections to all remote PSAX systems. (These connections may be tunneled 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 Ethernet interface IP network should be different from the SUN machines 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 connections to each of the remote PSAX systems. 9 The remote PSAX system should have only one connection to the NMS stations network and the appropriate mask if the main router PSAX system 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 only one 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 connection.
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.
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 B-11

Example: Primary IP Address: 020.001.001.001 Primary IP Mask: 255.000.000.000 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: Primary IP Address: 020.001.001.2 Primary IP Mask: 255.000.000.000 3 Configure the primary IP address for in-band management on the CPUn module of the main router PSAX system (Node C) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.001.001.003 Primary IP Mask: 255.000.000.000 4 Configure the primary IP Address for in-band management on the CPUn module of main router PSAX system (Node D) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.001.001.004 Primary IP Mask: 255.000.000.000 5 Configure the primary IP address for in-band management on the CPUn module of main router PSAX system (Node E) using the console interface: Select the Site Specific Configuration> In-Band Management menu options. Example: Primary IP Address: 020.001.001.005 Primary IP Mask: 255.000.000.000 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
Release 9.0.0 255-700-447

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 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 machines network to network 20.0.0.0 exists on the SUN machine using the netstat -nr command: 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
VPI: VPIad IP Address: NMS net. addr
Port: 1 VCI: VCIad IP Mask: NMS net. mask
Release 9.0.0 B-13

Release 9.0.0 255-700-447
Reference Information

This appendix contains reference information that is helpful while configuring 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 configuration 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 by entering the desired value in the Conformance Type field on the user interface 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
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 C-1
Appendix C Reference Information

Types of Traffic Descriptors

The types of ATM traffic descriptors supported in the PSAX system are as follows: 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 parameters, 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 loss priority (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:
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 C-2 Release 9.0.0 255-700-447

~ 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 Modules Interport Shared Buffer* Ingress Traffic Processing Priority Queuing Egress Traffic Processing Priority Queuing
23N72 1-Port OC-12c/STM-4c Multimode 23N73 1-Port OC-12c/STM-4c Single-Mode 24N72 4-Port OC-3c/STM-1 Multimode 24N73 4-Port OC-3c/STM-1 Single-Mode 20N92 1-Port STM-1 1+1 MSP Multimode 20N93 1-Port STM-1 1+1 MSP Single-Mode 20N72 1-Port OC-3c 1+1 APS Multimode 20N73 1-Port OC-3c 1+1 APS Single-Mode 23N74 3-Port DS3/E3 ATM 3-Port DS3/E3 ATM Protection
UPC, AQueMan, GFR
TM 4.1 priority queuing, Per VC traffic shaping, or VI support, EPD** TM 4.1 priority queuing, Per VC traffic shaping, or VI support, EPD AQueMan, Per VC traffic shaping, or VI support, EPD** AQueMan, Per VC traffic shaping, or VI support, EPD** TM 4.1 priority queuing, Per VC traffic shaping, or VI support, EPD** AQueMan, EPD** AQueMan, EPD** AQueMan, EPD**
UPC, TM4.1
UPC, AQueMan
UPC, AQueMan
No
UPC, AQueMan
20N02 20N22 23N68
2-Port DS3 ATM 2-Port E3 ATM 1-Port DS3 IMA
Yes N/A N/A
AQueMan AQueMan UPC, AQueMan
23N60 1-Port Channelized DS3 Multiservice 23N62 1-Port Channelized STS-1e, T1 Format
Release 9.0.0 C-3

SPVC Connection Cause Codes for Connection Retry
Table C-1. Traffic Processing Options and Priority Queuing for Modules Supporting ATM Interfaces ATM Interface Modules Interport Shared Buffer* Ingress Traffic Processing Priority Queuing Egress Traffic Processing Priority Queuing
23N34 IMA
21-Port High-Density E1
Yes Yes Yes
UPC, AQueMan UPC, AQueMan AQueMan
AQueMan, EPD** AQueMan, EPD** AQueMan, EPD**
23N33 12-Port Medium-Density DS1 IMA 20N33 6-Port DS1 IMA 20N34 6-Port E1 IMA 20N36 6-Port Enhanced DS1/T1 Multiservice 20N56 6-Port Enhanced E1 Multiservice 23N64 12-Port Medium-Density DS1 Multiservice 23N66 21-Port High-Density E1 Multiservice 23N07 20N07
*
Yes Yes Yes Yes
UPC, AQueMan UPC, AQueMan UPC, AQueMan AQueMan
AQueMan, EPD AQueMan, EPD AQueMan, EPD AQueMan, EPD
Quadserial 6-Port Multiserial
**
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 processing 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.

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

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 Release Cause Code Description Prompts a Retry Referenced Standard
Unallocated (unassigned) number. The called party number is not currently assigned. As a result, the called party cannot be reached. 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 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. VCC is unacceptable. The VPI/VCI is unacceptable to the sending entity for use in the call. Normal call clearing. User is busy. The called party is unable to accept another call because the user-busy condition has been encountered. 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. 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 service constraint. Number was changed. The number of the called party is no longer assigned. A new number must be used to call the called party. 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 the called party requires this information. Destination is out of order. The user cannot reach the destination because the interface to the destination is not functioning properly; that is, a signaling message could not be delivered to the destination.
No
ITU-T Q.850
No
ITU-T Q.850
Yes
ITU-T Q.850
10 16 17 18
No No Yes No
ATM Forum UNI 3.0/3.1 ITU-T Q.850 ITU-T Q.850 ITU-T Q.850
21
No
ITU-T Q.850
22
No
ITU-T Q.850
23
No
ATM Forum UNI 3.0/3.1
27
Yes
ITU-T Q.850
Release 9.0.0 C-5

Table C-2. Connection Release Cause Codes for SPVCs (Continued) Release Cause Code Description Prompts a Retry Referenced Standard
28
Number format is not valid (address incomplete). The called party is unreachable because the number of the called party is not in the proper format or it is not complete. Response to STATUS ENQUIRY. A STATUS message was sent in response to receipt of a STATUS ENQUIRY message. Normal unspecified. A normal event occurred for which no other cause applies. As a result, the event is normal but unspecified. Too many pending ADD PARTY requests currently exist. Requested VPCI/VCI is not available. The SPVC attempted to use a VPCI/VCI that is unavailable. VPCI/VCI assignment failure. A VPCI/VCI could not be assigned to the SPVC. User cell rate is unavailable. The requested cell rate is unavailable for the SPVC. 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 succeed. 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. 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 compatibility, or subaddress). Circuit is unavailable. The requested circuit or channel is not available. No VPCI/VCI is available. A VPCI/VCI is not available for the SPVC. Resource is unavailable or unspecified. A resource is unavailable, and no other cause code exists to report this event. Quality of service is unavailable. The requested QoS class is unavailable for the SPVC. User cell rate is unavailable. The requested cell rate is unavailable for the SPVC. PGL was changed. The call was cleared due to a change in the peer group leader (PGL). Bearer capability is not authorized. The SPVC user requested a bearer capability for which the user is not authorized. 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
30 31
Yes No
ITU-T Q.850 ITU-T Q.850
32 35 36 37 38
Yes Yes Yes Yes Yes
ATM Forum PNNI 1.0 ITU-T Q.2610 ITU-T Q.2610 ITU-T Q.2610 ITU-T Q.850
41
Yes
ITU-T Q.850
43
Yes
ITU-T Q.850
44 45 47 49 51 53 57 58
No Yes Yes No Yes No No No
ITU-T Q.850 ITU-T Q.2610 ITU-T Q.850 ITU-T Q.850 ATM Forum UNI 3.0/3.1 ATM Forum PNNI 1.0 ITU-T Q.850 ITU-T Q.850
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 C-6
Release 9.0.0 255-700-447

63
Service or option is unavailable or unspecified. A service or option is unavailable, and no other cause code exists to report this event. Bearer capability is not implemented. The equipment that generated this cause code does not support the requested bearer capability. Combination of traffic parameters is not supported. AAL parameters cannot be supported. 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. Identified channel does not exist. The equipment sending this cause code received a request to use a channel that was not activated on the call interface. For example, if a user subscribed to those channels on a primary rate interface numbered from 1 to 12, this cause code would be generated if the user equipment or the network attempts to use channels 13 through 23. Incompatible destination. The equipment sending this cause code received a request to establish a call with low-layer compatibility, or other compatibility attributes that cannot be accommodated, for example, data rate. Endpoint reference is not valid. The equipment sending this cause code received a message with an endpoint reference that is currently not in use on the user-network interface. Transit network selection is not valid. A transit network identification was received that is not formatted correctly. Correct formats are defined in the standard, Q.931, Annex C. 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. AAL parameters cannot be supported. Unspecified message is not valid. This cause code reports a message event that is not valid when no other message cause code that is not valid applies. 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
65
No
ITU-T Q.850
73 78 81
No No No
ATM Forum UNI 3.0/3.1 ITU-T Q.2610 ITU-T Q.850
82
No
ITU-T Q.850
88
No
ITU-T Q.850
89
No
ATM Forum UNI 3.0/3.1 ITU-T Q.850
91
No
92
No
ATM Forum UNI 3.0/3.1
93 95
No No
96
No
ITU-T Q.850
Release 9.0.0 C-7

97
Message type is nonexistent or not implemented. The equipment sending the cause code received one of the following message types: Not defined Defined but not implemented by the equipment sending the cause code 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 code The 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. 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. Message type is not compatible with call state. A message was received that is incompatible with the call state. Recovery on timer expiration. A procedure has been initiated by the expiration of a timer that is related to error handling procedures. Message length is not correct. Unspecified protocol error. A protocol error occurred for which no defined protocol error exists. 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. Next node is unreachable. DTL transit is not my node ID.
No
ITU-T Q.850
99
No
ITU-T Q.850
100
No
ITU-T Q.850
101 102
Yes Yes
104 111 127
No No No
ATM Forum UNI 3.0/3.1 ITU-T Q.850 ITU-T Q.850
128 160
No No
ATM Forum PNNI 1.0 ATM Forum PNNI 1.0
Release 9.0.0 255-700-447

DSP Tone Detection Modes
DSP Tone Detection Modes

DSP tone detection modes are selected through the Circuit Emulation-toATM VCC PVC Connection window. These modes are described in Table C-3.
Table C-3. DSP Tone Detection Modes* and Associated Processing Performed Tone Mode Processing Performed
Disabled Bypass Fax Relay
Ignores fax tones and modem tones 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. 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 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.
Fax Relay/Modem Bypass
Modes selected on the Circuit Emulation-to-ATM VCC PVC Connection window.
DSP Channel Reduction Availability Due to Fax Relay Mode

Table C-4. Channel Reduction Availability Caused by Fax Relay Connections vs. Voice Processing Connections on a DSP2C Module Number of DSPs for Fax Relay Total Connections Assigned for Fax Relay Percent of All DSP Connections Assigned for Fax Relay Remaining Voice Processing Available Channels*
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
4 8 12 16 20 24 28 32 36 40 44 48 52 56 60 64
3% 6% 9% 13% 16% 19% 22% 25%
124 120 116 112 108 104 100 96 92 88 84 80 76 72 68 64
28% 31% 34% 38% 41% 44% 47% 50%
Release 9.0.0 C-9

Industry Compliance Specifications
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 connections 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.

Compliance specifications for the PacketStar PSAX Multiservice Media Gateways and the I/O and server modules are contained in Table C-5.
Table C-5. Industry Compliance Specifications Feature Name/Product Name Specification Title Notes
Integrated Local Management af-ilmi-0065.000 Interface (ILMI) Integrated Local Management ILMI over PNNI Interface (ILMI) 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, Multiserial, 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 DS1 IMA, DS3 IMA, 1-Port OC-3/STM-1 Unst. CES/ATM MM/SM modules Channelized DS3 module af-phy-0016.000 DS1 Physical Layer Specification af-phy-0054.000 DS3 Physical Interface Specification af-phy-0064.000 E1 Physical Layer Specification af-phy-0086.000 Inverse Multiplexing over ATM (IMA), Version 1.0 af-phy-0086.001 Inverse Multiplexing over ATM (IMA), Version 1.1 Obsoletes af-phy-0086.000 but PSAX is compatible with both versions
E1 IMA, 1-Port Chan OC3/STM-1 Unstruct. CES/ATM MM/SM modules DS1 IMA, DS3 IMA, and E1 IMA modules DS1 IMA, DS3 IMA, E1 IMA, 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules
Release 9.0.0 255-700-447

Table C-5. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes
Channelized DS3, Channelized af-pnni-0026.000 STS-1e, DS1 IMA, DS3 IMA, E1 Interim Inter-Switch Signaling IMA, DS3 ATM, E3 ATM, Protocol (IISP) Enhanced DS1, Enhanced E1,High-Density E1, High Speed, Medium-Density DS1, OC-3c MM/SM APS, STM-1 MM/SM MSP, OC-12c/STM-4c, OC-12c/STM-4c, 1-Port OC3/STM-1 Unst. CES/ATM MM/SM (STM1-ATM Operating Mode only), and Quadserial modules ATM Maintenance Mode af-pnni-0055.000 ATM PNNI 1.0 interface Private Network-Network Interface (PNNI) ETSI ISDN Support In-band Management SVC Soft Permanent Virtual Circuits (SPVCs) SPVC Support for CES Channelized 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, OC3c 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 ATM Maintenance Mode In-band Management SVC af-pnni-0066000 Private Network-Network Interface (PNNI) Addendum (Soft PVC) SPVCs- Annex C: Soft PVC Procedures for circuit emulation, frame relay, and terminal emulation Annex G, mandatory requirements
Channelized DS3, Channelized af-sig-0061.000 STS-1e, DS1 IMA, DS3 IMA, E1 User-Network Interface (UNI) IMA, DS3 ATM, E3 ATM, 4.0 Signaling Specification 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, 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM, and Quadserial modules
Release 9.0.0 C-11

Traffic Management (UPC Support) Route Server-to-ATM Interworking
af-tm-0121.000 Traffic Management, Usage Parameter Control
Route Server-to-ATM Interworking: Section 5.5
Channelized DS3, Channelized af-uni-0010.001 STS-1e, DS1 IMA, DS3 IMA, E1 User-Network Interface (UNI) IMA, DS3 ATM, E3 ATM, 3.0 Enhanced DS1, Enhanced E1,High-Density E1, High Speed, Medium-Density DS1, Multiserial, OC-3c MM/SM APS, STM-1 MM/SM MSP, OC12c/STM-4c, OC-12c/STM-4c, Ch OC3 Unstruct. CES/STM1 ATM, and Quadserial modules PSAX 1000, PSAX 1250, af-uni-0010.002 PSAX 2300, and PSAX 4500 User-Network Interface (UNI) Multiservice Media Gateways 3.1 OC-12c/STM-4c, 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM, 4-Port OC-3c/STM-1 MM/SM GR-303 DLC Services VTOA AAL2 Trunking Narrowband Services af-vmoa-0145.000 Voice and Multimedia Over ATMLoop Emulation Service Using AAL2 Includes 56 (DS1), Nx64 (DS1, E1)
Carrier Group AIS Alarm af-vtoa-0078.000 I.610 OAM F4/F5 Processing Circuit Emulation Service 2.0 (remote defect indication [RDI] and alarm indication signal [AIS]) Channelized DS3, Channelized STS-1e, Channelized DS3/STS1e CES, DS1 IMA, DS3 IMA, E1 IMA, Enhanced DS1, Enhanced E1, High-Density E1, MediumDensity DS1, Multiserial, Quadserial and Unstructured DS3/E3 CES modules
Release 9.0.0 255-700-447

Channelized DS3, Channelized STS-1e, Enhanced DS1, and DSP2x Voice Server modules
af-vtoa-0085.000 (DBCES) Dynamic Bandwith Utilization in 64 Kbps Time Slot Trunking Over ATMUsing Circuit Emulation Service (CES) AAL1 Trunking CCS (Q.931) AAL1 Trunking CCS (Q.931/QSIG), AAL1 Trunking CAS af-vtoa-0089.000 ATM Trunking Using AAL1 for Narrow Band Services V1.0 af-vtoa-0098.000 VTOA AAL1 Trunking Services
AAL2 Trunking
I.610 OAM F4/F5 Processing (remote defect indication [RDI] and alarm indication signal [AIS]) 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 Multiservice Media Gateways
ANSI T1.101 Telecommunications - Synchronization Interface Standard
Unstructured DS3/E3 CES mod- ANSI T1.102 ule DS3 Electrical Interface Characteristics CSU/DSU loopback Enhanced DS1, DS3 ATM, OC3c MM/SM APS modules 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways DS1 IMA and E1 IMA modules ANSI T1.105 Synchronous Optical NetworkBasic Description ANSI T1.105.01, Synchronous Optical Networks, Automatic Protection Switching
ANSI T1.107 T1.107aDS1 and DS3 Format Specifications ANSI T1.231 DS1/DS3 Performance Monitoring Characteristics
DS1 IMA, DSP2x Voice Servers, and E1 IMA modules
Release 9.0.0 C-13

GR-303 DLC Services
ANSI T1.401 Interface Between Carriers and Customer Installations- Analog Voice Grade Switched Access Lines Using Loops-start and Ground-start Signaling ANSI T1.403 Network-to-Customer Installation: DS1 Metallic Interface
CSU/DSU loopback Facsimile Demodulation/Remodulation VTOA AAL2 Trunking Narrowband Services DS1 IMA, E1 IMA, Enhanced DS1, DS3 ATM, DSP2x Voice Servers, and OC-3c MM/SM modules CSU/DSU loopback Enhanced DS1, DS3 ATM, OC-3c MM/SM modules GR-303 DLC Services
ANSI T1.404 Network-to-Customer Installation-DS3 Metallic Interface ANSI T1.405 Network-to-customer Installation Interfaces- Direct-inward Dialing Analog Voice Grade Switched Access Using Loopreverse Battery Signaling ANSI T1.409 Network-to-Customer Installation Interfaces- Analog Voice Grade Special Access Lines Using E&M Signaling ANSI T1.602 Integrated Services Digital Network (ISDN)- Data-link Layer Signaling Specification for Application at the User-Network Interface ANSI T1.607; T1.607a T1.607a is for GR-303 DLC SerDigital Subscriber Signaling Sys- vices tem Number 1 (DSS1)-Layer 3 Signaling Specification for Circuit-switched Bearer Services CCITT G.703 Physical/Electrical Characteristics of Hierarchical Digital Interfaces
GR-303 DLC Services
GR-303 DLC Services VTOA AAL2 Trunking Narrowband Services
GR-303 DLC Services VTOA AAL2 Trunking Narrowband Services
DS3 Frame Relay module
Release 9.0.0 255-700-447

DS3 Frame Relay module
CCITT G.704 Synchronous Frame Structures Used at Primary and Secondary Hierarchical Levels DSL Forum TR 017 ATM over ADSL Recommendations
Multiserial and Quadserial mod- EIA-232 ule Electrical, mechanical, and functional standards for communication between computers, terminals and modems High Speed, Multiserial, and Quadserial modules GR-303 DLC Services VTOA AAL2 Trunking Narrowband Services High Speed, Multiserial, and Quadserial modules EIA-449 Faster version of RS-232-C; capable of longer cable runs EIA-464-B Requirements for Private Branch Exchange (PBX) Switching Equipment EIA-530 Defines mechanical/electrical interfaces between DTEs and DCEs that transmit serial binary data ETSI 300 012-1 Integrated Services Digital Network (ISDN); Basic User-Network Interface; Layer 1 Specification and Test Principles ETSI ISDN Support V5.2 ETSI 300 125 ETSI 300 324-1 V5.1 Interface for the Support of Access Network (AN) Part 1: V5.1 Interface Specification Annex C: Soft PVC Procedures 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 specifications should apply.
Release 9.0.0 C-15

V5.2
ETSI 300 347-1 V5.2 Interface for the Support of Access Network (AN) Part 1: V5.2 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 specifications should apply.
ETSI 300 402-1 Integrated Services Digital Network (ISDN), Digital Subscriber Signaling System No. 1 (DSS1) Protocol; Data Link Layer, Part 1: General Aspects ETSI 300 402-2 Integrated Services Digital Network (ISDN); Digital Subscriber System No. 1 (DSS1) protocol; Data Link Layer, Part 2: General Protocol Specification PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways FR-796, Reliability and Quality Generic Requirements
Channelized DS3, Channelized FRF.1.1 STS-1e, DS3 Frame Relay, User-to-Network (UNI) ImpleEnhanced DS1, Enhanced E1, mentation Agreement High-Density E1, Medium-Density DS1, Multiserial and Quadserial modules Channelized DS3, Channelized STS-1e, DS3 Frame Relay, Enhanced DS1, Enhanced E1, High-Density E1, Medium-Density DS1, Multiserial and Quadserial modules link management interface (LMI) services between two network-network interface (NNI) services Channelized DS3, Channelized STS-1e, DS3 Frame Relay, Enhanced DS1, Enhanced E1, High-Density E1, Medium-Density DS1, Quadserial, and Route Server modules FRF.2.1 Frame Relay Network-to-Network (NNI) Implementation Agreement LMI services between two NNI services
FRF.5 Frame Relay ATM/PVC Network Internetworking Implementation Agreement
Release 9.0.0 255-700-447

In-band Management Channelized DS3, Channelized STS-1e, DS3 Frame Relay, Enhanced DS1, Enhanced E1, High-Density E1, Medium-Density DS1, Multiserial, Quadserial, and Route Server modules 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways Tones and Announcements Server module Channelized STS-1e, Channelized DS3/STS-1e CES OC-3c APS, OC-12c/STM-4c 1+1 APS/MSP MMSM modules GR-303 DLC Services Channelized DS3/STS1-e CES module D4 Support Stratum DS1 BITS Interfaces Stratum 34 modules OC-3c APS modules
FRF.8 Frame Relay ATM/PVC Service Internetworking Implementation Agreement
FRF-796, Reliability and Quality Generic Requirements GR-63-CORE Network Equipment Building Standards (NEBS): Physical Protection
GR-246-CORE Signalling System Number 7 GR-253-CORE SONET Transport Systems Revision 1, Dec 1997: Common Generic Criteria GR-303-CORE Integrated Digital Loop Carrier System Generic Requirements, Objectives, and Interface GR-436-CORE Digital Network Synchronization Plan
for test capability
Does not include the (ANSI T1.101-compliant Stratum 34 module, COMCODE 108484890)
GR-474-CORE Section 8.3.1, Trouble NotificaAlarm and Control for Network tions for Protection Switches Elements GR-499-CORE Common Requirements, DSP2x: Common Requirements for TSGR
1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM, 1-Port OC-3c APS, 1-Port OC12c/STM-4c 1+1 APS/MSP MM/SM, and DSP2x Voice Server modules PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways
Release 9.0.0 C-17

D4 Support Stratum DS1 BITS Interfaces Stratum 34 modules PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways DSP2x Voice Server modules
GR-518-CORE LSSGR: Synchronization, Section 18
Stratum: Does not include the ANSI T1.101-compliant Stratum 34 module, COMCODE 108484890
DSP2x: GR-820-CORE OTGR Section 5.1 Generic Transmission Surveillance GR-822-CORE OTGR Section 6.3: Network Maintenance: Access and Testing - Switched Circuits, POTS Loops, and Public Packet Switched Network (PPSN) (a module of OTGR, FR-439) GR-1089-CORE (NEBS) Electromagnetic Compatibility and Electrical SafetyGeneric Criteria for Network Telecommunications Equipment GR-1244-CORE Clocks for Synchronized Networks: Common Generic Criteria Stratum: Does not include the ANSI T1.101-compliant Stratum 34 module, COMCODE 108484890 For milliwatt test refer to Section 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
Channelized DS3, Channelized STS-1e, Enhanced DS1, Medium Density DS1, and Tones and Announcements Server modules
1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways D4 Support Stratum DS1 BITS Interfaces Stratum 34 modules PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways I.610 OAM F4/F5 Processing (remote defect indication [RDI] and alarm indication signal [AIS]) 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM, OC-3c APS modules PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways I.610 OAM F4/F5 Processing (remote defect indication [RDI] and alarm indication signal [AIS]) OC-3c APS modules
GR-1248-CORE Generic Requirements for operations of ATM Network Elements
For OAM, refer to Table 4-1 OAM Type/Function For OCx APS modules, refer to Section 6.3 ATM APS Protection Switching
GR-2980-CORE General Criteria for ATM Layer Protection Switching Mechanism
Coordination protocol cell is used for automatic protection switching (APS)
Release 9.0.0 255-700-447

OC-3c APS modules
SR-NWT-001756 Automatic Protection Switching for SONET, issue 1, October 1990 TR-NWT-00170 Bellcore Digital Cross-Connect System Generic Requirements and Objectives IEEE 802.1D Media Access Control (MAC) Bridges IEEE 802.3 Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method and Physical Layer Specifications IETF RFC 792 Internet Control Message Protocol IETF RFC 1058 Routing Information Protocol IETF RFC 1157 Simple Network Management Protocol (SNMP) Version 1.0
I.610 OAM F4/F5 Processing (remote defect indication [RDI] and alarm indication signal [AIS]) Spanning Tree Protocol Ethernet module Ethernet module
Route Server module
Route Server module
1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules.
RFC 1213 - Management Information Base for NM: MIBII
DS1 IMA, E1 IMA, Enhanced IETF RFC 1406 DS1, and Enhanced E1 modules Definitions of Managed Objects for the DS1 and E1 Interface Types DS3 IMA, DS3 ATM, and E3 ATM modules IETF RFC 1407 Definitions of Managed Objects for the DS3 and E3 Interface Types RFC 1414 - Identification MIB
1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. 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
Release 9.0.0 C-19

Route Server module
IETF RFC 1490 IETF RFC 1490 was replaced by Multiprotocol Interconnect over IETF RFC 2427 Frame Relay IETF RFC 1595 Definitions of Managed Objects 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 1700 Assigned Numbers
Route Server module Route Server module
IETF RFC 1723 RIP Version 2 IETF RFC 1783 Trivial File Transfer Protocol Blocksize Option IETF RFC 1972 A Method for the Transmission of IPv6 Packets over Ethernet Networks RFC 2233 - The Interfaces Group MIB using SMIv2 IETF RFC 2427 Obsoletes RFC 1490 Multiprotocol Interconnect over Frame Relay IETF RFC 2495 - Definitions of Managed Objects for the DS1/E1 Interfaces IETF RFC 2515 - Definitions of Managed Objects for ATM Management IETF RFC 2558 - Definitions of Managed Objects for the SONET/SDH Interface IETF RFC 2464 Transmission of IPv6 Packets over Ethernet Networks Obsoletes RFC 1972 Section 3.1 (authentication) and 3.5 (multicasting)only
Route Server module
1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. Route Server module Enhanced Router module 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. Route Server module
Release 9.0.0 255-700-447

Ethernet Bridging 4-Port Ethernet, Ethernet, Enhanced Router, and Route Server modules
IETF RFC 2684 Multiprotocol Encapsulation over ATM Adaptation Layer 5 ITU-T E.164 Overall Network Operation, telephone service, service operation, and human factors: Operation, numbering, routing and mobile services International operation- Numbering plan of the international telephone service
Obsoletes RFC 1483 RFC 2685 (VPN identification) not supported
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 ITU-T G.165 General Characteristics of International Telephone Connections and International Telephone Circuits: Echo Cancellers ITU-T G.702 General Aspects of Digital Transmission Systems Terminal Equipment: Digital Hierarchy Bit Rates
DSP2A/B/C/D Voice Server modules Echo cancellation (general)
PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways 1.544 Mbps, 2.048 Mbps, 44.736 Mbps; includes channelassociated signaling (CAS) ABCD in-band signaling
ITU-T G.703 Physical/Electrical Characteristics of Hierarchical Digital Interfaces 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) procedures relating to basic frame structures defined in Recommendation G.704
Release 9.0.0 C-21

ITU-T G.707 Transmission Systems and MediaDigital transmission systems Terminal equipment General: Network node interface for the synchronous digital hierarchy (SDH) ITU-T G.711 General Aspects of Digital Transmission Systems Terminal Equipment: Pulse Code Modulation (PCM) of Voice Frequencies ITU-T G.726 General Aspects of Digital Transmission Systems Terminal Equipment: 40, 32, 24, 16 Kbps Adaptive Differential Pulse Code Modulation (ADPCM) ITU-T G.729 General Aspects of Digital Transmission Systems: Coding of Speech at 8 Kbps Using Conjugate-Structure Algebraic-CodeExcited Linear-Prediction (CSACELP) ITU-T G.732 General Aspects of Digital Transmission Systems Terminal Equipments: Characteristics of Primary PCM Multiplex Equipment Operating at 2048 Kbit/s ITU-T G.736 General Aspects of Digital Transmission: Characteristics of a Synchronous Digital Multiplex Equipment Operating at 2048 kbits/sec ITU-T G.751 Digital multiplex equipments operating at the third order bit rate of 34 368 kbit/s and the fourth order bit rate of 139 264 Kbps and using positive justification
DSP2A/B/C/D Voice Server modules 64 Kbps fax encoding
DSP2A/B/C/D Voice Server modules Voice compression (16, 24, 32, 40 Kbps) and tandem encoding
DSP2x Voice Server modules Annex A: Voice compression (8 Kbps) Annex B: Silence suppression
Release 9.0.0 255-700-447

PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways. 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM, and OC-3c APS MM/SM modules.
ITU-T G.783 Transmission Systems and Media, Digital Systems and Networks Digital Transmission SystemsTerminal EquipmentPrincipal Characteristics of Multiplexing Equipment for the Synchronous Digital Hierarchy: Characteristics of Synchronous Digital Hierarchy (SDH) Equipment Functional Blocks ITU-T G.803 Architecture of Transport Networks Based on Synchronous Digital Hierarchy (SDH) 1997 ITU-T G.804 ATM cell mapping into Plesiochronous Digital Hierarchy (PDH) ITU-T G.812 Timing Requirements of Slave Clocks Suitable for Use as Node Clocks in Synchronization Networks, June 1998 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
PSAX 1000, PSAX 1250, PSAX 2300, and PSAX 4500 Multiservice Media Gateways DS3 ATM, Enhanced DS1, and Enhanced E1 modules
Includes Multiplex Section Pro- ITU-T G.832 tection (MSP) Transmission Systems and Media, Digital Systems and Networks Digital transmission systemsDigital networks Network capabilities and functions: Transport of SDH Elements on PDH NetworksFrame and Multiplexing Structures STM-4c module ITU-T G.837
Release 9.0.0 C-23

STM-4c module
ITU-T G.841, Annex A Types and Characteristics of SDH Network Protection Architecture Issue 10/98 ITU-T G.957 Long haul not supported Optical interfaces for equipment and systems relating to the synchronous digital hierarchy 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) 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 specifications should apply. 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 specifications should apply.
Intra-office and short haul
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)
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) transceivers ITU-T H.248 H.248 Base Root Package ITU-T I.121 Integrated Services Digital Network (ISDN) General Structure and Service Capabilities: Broadband Aspects of ISDN Annex E.2
Release 9.0.0 255-700-447

ITU-T I.150 B-ISDN ATM Functional characteristics Enhanced DS1 and Enhanced E1 modules ITU-T I.233 Frame Mode Bearer Services ITU-T I.321 Integrated Services Digital Network (ISDN) Overall Network Aspects and Functions, ISDN User-Network Interfaces: BISDN Protocol Reference Model and its Application ITU-T I.356 B-ISDN ATM layer cell transfer performance I.610 OAM F4/F5 Processing (remote defect indication [RDI] and alarm indication signal [AIS]) 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules. Virtual Private LAN Services (VPLS) over ATM 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM modules DSP2x Voice Server modules ITU-T I.361 B-ISDN ATM Layer Specification ABR not supported
ITU-T I.363 B-ISDN ATM Adaptation Layer specification
Only AAL1, AAL2, and AAL5 are supported
ITU-T I.363.1 B-ISDN ATM Adaptation Layer specification: Type 1 AAL
Multiplexing support for DSP2x ITU-T I.363.2 Voice Server modules B-ISDN ATM Adaptation Layer specification: Type 2 AAL ITU-T I.363.5 B-ISDN ATM Adaptation Layer specification: Type 5 AAL VTOA AAL2 Trunking Narrowband Services ITU-T I.366.1 Segmentation and Reassembly Service Specific Convergence Sublayer for the AAL type 2
Release 9.0.0 C-25

Facsimile Demodulation/Remodulation VTOA AAL2 Trunking Narrowband Services DSP2C/D Voice Server modules Channelized DS3, Channelized STS-1e, DS3 Frame Relay, Enhanced DS1, Enhanced E1, High-Density E1,Medium-Density DS1, Multiserial, and Quadserial modules
ITU-T I.366.2 AAL Type 2 Specification on Convergence Sublayer for Narrow-band Services. ITU-T I.370 Congestion Management for ISDN Frame Relay Bearing Service
Annex M
Channelized DS3, Channelized ITU-T I.371 STS-1e, DS3 Frame Relay, High- Traffic control and congestion Density E1, Medium-Density control in B-ISDN DS1, Multiserial and Quadserial modules ITU-T I.372 Integrated Services Digital Network (ISDN) Overall Network Aspects and Functions: Frame Relaying Bearer Service Network-to-Network Interface Requirements ITU-T I.413 Integrated Services Digital Network (ISDN) User-Network Interfaces: B-ISDN User-Network Interface ITU-T I.430 Basic User-Network Interface Layer 1 Specification Channelized DS3, Channelized STS-1e, Channelized DS3/STS1e CES, DS3 Frame Relay, Enhanced DS1, Enhanced E1, High-Density E1, Medium-Density DS1, Multiserial, and Quadserial modules ITU-T I.431 Integrated Services Digital Network (ISDN) User-Network Interfaces: Primary Rate UserNetwork InterfaceLayer 1 Specification
ABR not supported
Scrambling, header error control ITU-T I.432 (HEC) processing, cell delinea- B-ISDN User-Network Intertion facePhysical layer Specification ITU-T I.432.1 B-ISDN User-Network Interface: Physical Layer Specification- General Characteristics

ITU-T I.432.2 B-ISDN User-Network- Physical Layer Specification: 155 520 Kbps and 622 080 Kbps operation ITU-T I.432.3 B-ISDN User-Network Interface: Physical Layer Specification 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 Alarm ITU-T I.610 Dual-homed PVCs B-ISDN operation and maintenance principles and functions I.610 OAM F4/F5 Processing (remote defect indication [RDI] and alarm indication signal [AIS]) Channelized DS3, Channelized STS-1e, Channelized DS3/STS1e CES, DS3 ATM, E3 ATM, DS1 IMA, DS3 IMA, E1 IMA, Enhanced DS1, Enhanced E1, DSP2A/B/C/D Voice Servers, Route Server, High-Density E1, High Speed, Medium-Density DS1, Multiserial, Quadserial, 1-Port Chan OC-3/STM-1 Unstruct. CES/ATM MM/SM, OC-3c APS MM/SM, STM-1 MSP MM/SM, OC-12c/STM-4c MM/SM, and Unstructured DS3/E3 CES modules ITU-T Q.922 Annex A Digital Subscriber Signaling System No.1 (DSS 1) Data Link Layer: ISDN Data Link Layer Specification for Frame Mode Bearer Services ITU-T Q.921 Digital Subscriber Signaling system No. 1, ISDN User-Network interface- Data Link Layer Specification
Release 9.0.0 C-27

AAL1 Trunking CCS (Q.931) AAL1 Trunking CCS (Q.931/QSIG), AAL1 Trunking CAS AAL2 Trunking CCS (Q.931)
ITU-T Q.931 Switching and Signaling - Digital subscriber Signalling System No. 1 - Network layer: Digital Subscriber Signaling System No. 1 (DSS 1) - ISDN User-Network Interface Layer 3 Specification for Basic Call Control ITU-T Q.933 Annex A Digital Subscriber Signaling System No. 1Integrated Services Digital Network (ISDN) Digital Subscriber Signaling System No. 1 (DSS 1)Signaling Specifications for Frame Mode Switched and Permanent Virtual Connection Control and Status Monitoring
ATM UNI interfaces (3.0, 3.1, 4.0)
ITU-T Q.2110 B-ISDN SAAL Service Specific Connection Oriented Protocol (SSCOP) 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 signallingBroadband Integrated Services Digital Network (B-ISDN) Digital Subscriber Signalling System No. 2 (DSS 2)User Network Interface (UNI) Layer 3 Specification For Basic Call/Connection Control ITU-T Q.2941.2 Draft: Broadband Integrated Services Digital Network (BISDN)- Digital Subscriber Signaling System No. 2 (DSS2): Generic identifier transport (
ATM UNI interfaces (3.0, 3.1, 4.0)
Release 9.0.0 255-700-447

ITU-T Q.2971 B-ISDNDSS 2User-network interface layer 3 specification for point-to-multipoint call/connection control ITU-T V.8 Procedures For Starting Sessions of Data Transmission Over the General Switched Telephone Network ITU-T V.25 Automatic Answering Equipment and General Procedures for Automatic Calling Equipment on the General Switched Telephone Network Including Procedures for Disabling of Echo Control Devices for Both Manually and Automatically Established Calls Multiserial module ITUT V.35 Defines signaling for data rates greater than 19.2 Kbps for a trunk interface between network access device and a packet network TR-TSU-001369 Generic Requirement for Frame Relay PVC Exchange Services X.21 bis CCITT Interface Between Data Terminal Equipment and Data Circuit-Terminating Equipment for Synchronous Operation of Public Data Networks, Recommendation X.21 X.144 User information transfer performance parameters for data networks providing international frame relay PVC service Interface between data terminal equipment (DTE) and data circuit-terminating equipment for synchronous operation on public data networks
V5.2 (See ETSI 300 347.1 Enhanced DS1 and Enhanced E1 modules Multiserial module
Release 9.0.0 C-29

Connection Type by Interface Type
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 System 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 ATM IISP (Network/User) PRI ISDN (Network/User) Frame Relay (UNI, NNI)
ATM Virtual Interface
ATM UNI 3.0/3.1/4.0
Interface Type
Connection Type
AAL2 Trunking ATM-to-ATM virtual channel connection (VCC) PVC ATM-to-ATM virtual path connection (VPC) PVC Bridge-to-ATM VCC PVC Bridge-to-bridge PVC Circuit emulation-to ATM VCC PVC Circuit emulation-to circuit emulation PVC Frame relay-to-ATM VCC PVC Frame relay-to-frame relay PVC In-band management ATM PVC Variable bit rate (VBR)-to-ATM VCC PVC VBR-to-VBR PVC ATM-to-ATM IISP constant bit rate (CBR) SVC ATM-to-ATM IISP VBR SVC ATM-to-ATM VCC SPVC Circuit emulation-to-ATM VCC SPVC CE-to-ATM Std AAL2 VCC SPVC ERM-to-ATM VCC SPVC
X X X X X
X X X X X
X X X X X
X X X X X
X X
X X
X X X X
X X X
X X X
X X X
X X X
X X X
X X X X X X
X X X X
X X X X X
X X X X X X
X X X X X X X X X
Release 9.0.0 255-700-447
Terminal Emulation
HDLC Pass-through
Circuit Emulation
CAS TrunkLine
ATM PNNI 1.0
ATM IMA
GR-303
Bridge

Interface Type by Input/Output Module Type
Table C-6. Connection Type by Interface Type (Continued) ATM IISP (Network/User) PRI ISDN (Network/User) Terminal Emulation Routing Frame Relay (UNI, NNI)
ATM Virtual Interface
ATM UNI 3.0/3.1/4.0
Interface Type
Connection Type
Frame relay-ATM VCC SPVC VBR-to-ATM VCC SPVC VBR-to-ATM Std AAL2 VCC SPVC
X X
X X X
X X X
X X X X
X X X X X

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 DSP2x Voice Server modules, the Enhanced Router module, the Route Server module, and the Tones and Announcements Server module.
Table C-7. Interface Type by I/O Module Type ATM IISP (Network/User) PRI ISDN (Network/User) Frame Relay (UNI, NNI) ATM Virtual Interface HDLC Pass-through
Circuit Emulation
ATM UNI 3.0/3.1
CAS Trunkline
ATM PNNI 1.0
ATM UNI 4.0
ATM IMA
GR-303
Bridge
Terminal Emulation C-31 V5.2
Interface
Module
DS1/T1 Interface Modules
20N33
6-Port DS1 IMA
X X
X X X
X X X X X X X X X X X X X X
20N36 6-Port Enhanced DS1/T1 Multiservice
23N64 12-Port Medium- X Density DS1 Multiservice 23N33 12-Port Medium- X Density DS1 IMA 24N64 12-Port Medium-Density DS1/E1/DS0A CES X
X X
X X
X* X
HDLC Pass-through
Circuit Emulation
CAS TrunkLine
ATM PNNI 1.0
ATM IMA
GR-303
Bridge
Release 9.0.0

Table C-7. Interface Type by I/O Module Type (Continued) ATM IISP (Network/User) PRI ISDN (Network/User) Frame Relay (UNI, NNI) ATM Virtual Interface Terminal Emulation HDLC Pass-through
Circuit Emulation
ATM UNI 3.0/3.1
CAS Trunkline
ATM PNNI 1.0
ATM UNI 4.0
ATM IMA
Routing
GR-303
Bridge
Interface
Module
23N35 24-Port HighDensity DS1 Multiservice 23N69 8-Port HDSL-2 (HDSL2 MS) 20N34 6-Port E1 IMA
X X
X X
X X
X X
X X
X X X X
X X X
X X X X
X X X X X X X X X X X X X X X
20N56 6-Port Enhanced E1 Multiservice 23N66 21-Port HighDensity E1 Multiservice 23N34 21-Port HighDensity E1 IMA 23N60 1-Port Channelized DS3 Multiservice 23N61 1-Port Channelized DS3 CES 23N68 1-Port DS3 IMA
X X X X X X
20N03 1-Port Unchannelized DS3 Frame Relay 23N62 1-Port Channelized STS-1e, T1 Format 20N02 20N22 2-Port DS3 ATM 2-Port E3 ATM X X X X X
X X
X X
X X
X X X X X X
23N03 3-Port Channelized DS3/STS-1e CES 23N74 ATM 3-Port DS3/E3 X X X X X X X X X X
3-Port DS3/E3 ATM Protection
Release 9.0.0 255-700-447
V5.2

Circuit Emulation
ATM UNI 3.0/3.1
CAS Trunkline
ATM PNNI 1.0
ATM UNI 4.0
ATM IMA
Routing
GR-303
Bridge
Interface
Module
23N02 3-Port Unstructured DS3/E3 CES 23N12 1-Port Channelized OC-3/STM-1 CES Multimode 23N13 1-Port Channelized OC-3/STM-1 CES Single-mode 23N76 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Single-Mode 23N75 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Multimode 24N70 2-Port OC-3c/STM-1 ATM Multimode 24N71 2-Port OC-3c/STM-1 ATM SingleMode 24N72 4-Port OC-3c/STM-1 Multimode 24N73 4-Port OC-3c/STM-1 Single-Mode 20N12 1-Port OC-3c Multimode with AQueMan 20N13 1-Port OC-3c Single-Mode with AQueMan 20N14 1-Port OC-3c Multimode with Traffic Shaping X X X X
X
OC-3/STM-1/OC-3c/STM-1 Interface Modules
X**
X X X
X**
X X
X X
X X
X X
OC-3c Interface Only Modules
X X
X X
X X
X X
Release 9.0.0 C-33
V5.2

Circuit Emulation
ATM UNI 3.0/3.1
CAS Trunkline
ATM PNNI 1.0
ATM UNI 4.0
ATM IMA
Routing
GR-303
Bridge
Interface
Module
20N15 1-Port OC-3c Single-Mode with Traffic Shaping 20N72 1-Port OC-3c 1+1 APS Multimode 20N73 1-Port OC-3c 1+1 APS Single-Mode 20N62 1-Port STM-1 Multimode with AQueMan 20N63 1-Port STM-1 Single-Mode with AQueMan 20N64 1-Port STM-1 Multimode with Traffic Shaping 20N65 1-Port STM-1 Single-Mode with Traffic Shaping 20N92 1-Port STM-1 1+1 MSP Multimode 20N93 1-Port STM-1 1+1 MSP Single-Mode 23N72 1-Port OC-12c/STM-4c Multimode 23N73 1-Port OC-12c/STM-4c Single-Mode 20N32 4-Port Voice 2-Wire Office 20N30 8-Port Voice 2-Wire Station
X X
X X
X X
X X
X X
STM-1 Interface Only Modules
X X
X X
X X
X X
X X
X X
X X
X X
X X
OC-12c/STM-4c Interface Modules
Release 9.0.0 255-700-447
V5.2

ATM Service Categories in the PSAX System
Circuit Emulation
ATM UNI 3.0/3.1
CAS Trunkline
ATM PNNI 1.0
ATM UNI 4.0
ATM IMA
Routing
GR-303
Bridge
Interface
Module
23N07 20N07 20N40 23N40

* **
Quadserial 6-Port Multiserial Ethernet 4-Port Ethernet
X X
X X X X
X X
X X
X X X 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.

ATM Service Category Descriptions
The PSAX system support of defined ATM quality of service (QoS) categories is described in Table C-8.
Table C-8. PSAX System-Supported Quality of Service Category Descriptions ATM Service Category Description
Constant Bit Rate (CBR) Real Time Variable Bit Rate (VBR-rt)
This service offers consistent delay predictability. CBR is used for applications such as circuit emulation, voice, and video. 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.
Release 9.0.0 C-35
V5.2

Table C-8. PSAX System-Supported Quality of Service Category Descriptions (Continued) ATM Service Category Description
Non-Real Time Variable Bit Rate (VBR-nrt) Guaranteed Frame Rate (GFR)
This service allows delay variance between the delivery of cells. VBRnrt is used for data applications that have potentially bursty traffic characteristics. This service allows delay variance and offers a minimum cell rate guarantee. 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. 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.
Unspecified Bit Rate (UBR)
Priority of ATM Service Categories

The attributes of the categories of service supported by the PSAX system software 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 flexibility of the PSAX system allows you to tailor the system based on the required service applications by selecting the appropriate connection configuration selection field value.
Table C-9. Mapping ATM Service Categories to PSAX System Priority Levels Connection AQueMan Priority Configuration (Legacy Field Value Implementation) ATM Forum Traffic Management 4.1 Priority (Current Implementation)
ATM Service Category
Service Examples
Constant Bit Rate (CBR)
CBR1 CBR2 CBR3 CBR4
Highest Lower than CBR1 Lower than CBR2 Lower than CBR3 Lower than CBR4 Lower than VBR-express Lower than VBR-rt1
Highest
911 calls Preferred customers Standard Cellular
Real Time Variable Bit Rate (VBR-rt)
VBR-express VBR-rt1 VBR-rt2
Lower than CBR
Network management Real-time video MPEG 1-2/JPEG
Release 9.0.0 255-700-447

Traffic Shaping, UPC, and Virtual Interface Configuration Compatibilities
Table C-9. Mapping ATM Service Categories to PSAX System Priority Levels (Continued) Connection AQueMan Priority Configuration (Legacy Field Value Implementation) ATM Forum Traffic Management 4.1 Priority (Current Implementation)
ATM Service Category
Service Examples
Non-Real Time Variable Bit Rate (VBR-nrt)
VBR-nrt1 VBR-nrt2
Lower than VBR-rt2 Lower than VBR-nrt1 Lowest (shares queue with UBR) Lowest
Lower than VBR-rt
Data Data
Guaranteed Frame Rate (GFR) Unspecified Bit Rate (UBR)
GFR2 UBR
Lower than VBR-nrt Lowest
Frame relay, Ethernet, TCP UDP

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 illustration of this concept.
Table C-10. ATM Traffic Shaping, UPC Support, and VI Support Configuration Compatibility Fields on ATM UNI, PNNI, and IISP Configuration Windows ATM Traffic VI Support Shaping per VC UPC Support
ATM Traffic Shaping per VC VI Support UPC Support

*
No No Yes
*
Yes* Yes
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.
Release 9.0.0 C-37

I/O Module 1 Rx Tx Ingress Path UPC VI or TS Egress Path Chassis Backplane I/O Module 2 Rx Tx Ingress Path UPC VI or TS Egress Path
Figure C-1. Combining the UPC Feature and Either the TS or VI Feature on a Connection
ATM Traffic Shaping Sample CPS Calculation 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 Shaping feature is actually shaping the traffic to the (Actual CPS column) value 906 cps. The divergence is smallest at low PCR.
Table C-11. ATM Traffic Shaping CPS Calculation Table Actual Rate (in bps) Minimum/Actual Maximum Target Target CPS CPS Actual CPS
64,000 128,000 192,000 256,000 320,000 383,999 448,383 512,876 575,999 639,999 713,142
151 302 453 604 755 906 1,058 1,210 1,358 1,509 1,682
152 303 454 606 757 909 1,062 1,215 1,365 1,517 1,691
151 302 453 604 755 906 1,058 1,210 1,358 1,509 1,682
Release 9.0.0 255-700-447

Table C-11. ATM Traffic Shaping CPS Calculation Table (Continued) Actual Rate (in bps) Minimum/Actual Maximum Target Target CPS CPS Actual CPS
767,999 831,999 896,765 959,999 1,025,752 1,085,216 1,151,998 1,217,559 1,279,998 1,349,187 1,412,828 1,482,770 1,543,915 1,610,320 1,663,997 1,741,393 1,782,854 1,804,335 1,826,339 1,848,886 1,871,997 1,895,693 1,919,997 1,944,932 1,970,523 1,996,797 2,023,781 2,051,504 2,079,997 2,109,293 2,139,425 2,170,431 2,202,350 2,235,220 2,269,087 2,303,996 2,339,996
1,811 1,962 2,115 2,264 2,419 2,559 2,717 2,872 3,019 3,182 3,332 3,497 3,641 3,798 3,925 4,107 4,205 4,256 4,307 4,361 4,415 4,471 4,528 4,587 4,647 4,709 4,773 4,838 4,906 4,975 5,046 5,119 5,194 5,272 5,352 5,434 5,519
1,822 1,974 2,129 2,280 2,437 2,579 2,739 2,896 3,046 3,212 3,365 3,533 3,680 3,840 3,970 4,156 4,257 4,308 4,362 4,416 4,472 4,529 4,588 4,648 4,710 4,774 4,839 4,907 4,976 5,047 5,120 5,195 5,273 5,353 5,435 5,520 5,607
1,811 1,962 2,115 2,264 2,419 2,559 2,717 2,872 3,019 3,182 3,332 3,497 3,641 3,798 3,925 4,107 4,205 4,256 4,307 4,361 4,415 4,471 4,528 4,587 4,647 4,709 4,773 4,838 4,906 4,975 5,046 5,119 5,194 5,272 5,352 5,434 5,519
Release 9.0.0 C-39

2,377,139 2,415,480 2,455,078 2,495,996 2,538,301 2,582,065 2,627,364 2,674,282 2,722,905 2,773,329 2,825,656 2,879,996 2,936,466 2,995,195 3,056,322 3,119,995 3,186,378 3,255,647 3,327,995 3,403,631 3,482,785 3,565,709 3,652,677 3,743,994 3,839,994 3,941,047 4,047,561 4,159,994 4,278,851 4,404,699 4,538,175 4,679,993 4,830,960 4,991,992 5,164,130 5,348,563 5,546,658
5,606 5,697 5,790 5,887 5,987 6,090 6,197 6,307 6,422 6,541 6,664 6,792 6,926 7,064 7,208 7,358 7,515 7,678 7,849 8,027 8,214 8,410 8,615 8,830 9,057 9,295 9,546 9,811 10,092 10,388 10,703 11,038 11,394 11,774 12,180 12,615 13,082
5,698 5,791 5,888 5,988 6,091 6,198 6,308 6,423 6,542 6,665 6,793 6,927 7,065 7,209 7,359 7,516 7,679 7,850 8,028 8,215 8,411 8,616 8,831 9,058 9,296 9,547 9,812 10,093 10,389 10,704 11,039 11,395 11,775 12,181 12,616 13,083 13,586
5,606 5,697 5,790 5,887 5,987 6,090 6,197 6,307 6,422 6,541 6,664 6,792 6,926 7,064 7,208 7,358 7,515 7,678 7,849 8,027 8,214 8,410 8,615 8,830 9,057 9,295 9,546 9,811 10,092 10,388 10,703 11,038 11,394 11,774 12,180 12,615 13,082
Release 9.0.0 255-700-447

PSAX I/O Module Transmit Clock Options
5,759,991 5,990,391 6,239,990 6,511,294 6,807,262 7,131,418 7,487,988 7,882,093 8,319,987 8,809,398 9,359,986 9,983,985 10,697,126 11,519,982 12,479,981 13,614,524 14,975,977 16,639,974 18,719,971 21,394,253 24,959,961 29,951,954 37,439,942 49,919,923
13,585 14,128 14,717 15,357 16,055 16,819 17,660 18,590 19,623 20,777 22,075 23,547 25,229 27,170 29,434 32,110 35,321 39,245 44,151 50,458 58,868 70,641 88,302 117,736
14,129 14,718 15,358 16,056 16,820 17,661 18,591 19,624 20,778 22,076 23,548 25,230 27,171 29,435 32,111 35,322 39,246 44,152 50,459 58,869 70,642 88,303 117,737 176,605
13,585 14,128 14,717 15,357 16,055 16,819 17,660 18,590 19,623 20,777 22,075 23,547 25,229 27,170 29,434 32,110 35,321 39,245 44,151 50,458 58,868 70,641 88,302 117,736

Table C-12 lists the available transmit clock options for the PSAX I/O modules.
Table C-12. I/O Module Transmit Clock Options Model Number and Module Name DS1/T1 Interface Modules Local Timing Loop Timing Adaptive Timing SRTS*
20N33 20N36 23N33 23N64
6-Port DS1 IMA 6-Port Enhanced DS1/T1 Multiservice 12-Port Medium-Density DS1 IMA 12-Port Medium-Density DS1 Multiservice
PC PC PC PC
PC PC PC PC
NA PC NA PC
Release 9.0.0 C-41

Table C-12. I/O Module Transmit Clock Options (Continued) Model Number and Module Name Local Timing Loop Timing Adaptive Timing SRTS*
24N64 23N35 23N69 20N34 20N56 23N34 23N66 23N61 23N60 23N62 23N68 20N03 20N02 20N22 23N03 23N74 23N02 20N12 20N13 20N14 20N15 20N62 20N63 20N64 20N65 20N72 20N73
12-Port Medium-Density DS1/E1/DS0A CES 24-Port High-Density DS1 Multiservice 8-Port HDSL-2
PC PC
PC PC PC PC PC PC PC PC VPC PC VPC PC VPC PC VPC PC PC PC PC VPC PC PC PC PC PC PC PC PC PC PC PC PC
PC PC
PC PC PC PC PC PC VPC** PC VPC PC VPC PC VPC PC PC PC PC VPC PC PC PC PC PC PC PC PC PC PC PC PC
6-Port E1 IMA 6-Port Enhanced E1 Multiservice 21-Port High-Density E1 IMA 21-Port High-Density E1 Multiservice 1-Port Channelized DS3 CES 1-Port Channelized DS3 Multiservice 1-Port Channelized STS-1e, T1 Format 1-Port DS3 IMA 1-Port Unchannelized DS3 Frame Relay 2-Port DS3 ATM 2-Port E3 ATM 3-Port Channelized DS3/STS-1e CES 3-Port DS3/E3 ATM 3-Port Unstructured DS3/E3 CES
PC PC NA PC NA VPC NA VPC NA NA PC NA PC NA NA PC NA NA NA NA NA NA NA NA NA NA
1-Port OC-3c Multimode with AQueMan 1-Port OC-3c Single-Mode with AQueMan 1-Port OC-3c Multimode with Traffic Shaping 1-Port OC-3c Single-Mode with Traffic Shaping 1-Port STM-1 Multimode with AQueMan 1-Port STM-1 Single-Mode with AQueMan 1-Port STM-1 Multimode with Traffic Shaping 1-Port STM-1 Single-Mode with Traffic Shaping 1-Port OC-3c 1+1 APS Multimode 1-Port OC-3c 1+1 APS Single-Mode
Release 9.0.0 255-700-447

Table C-12. I/O Module Transmit Clock Options (Continued) Model Number and Module Name Local Timing Loop Timing Adaptive Timing SRTS*
20N92 20N93 23N72 23N73 23N12 23N13 mode

* **
1-Port STM-1 1+1 MSP Multimode 1-Port STM-1 1+1 MSP Single-Mode 1-Port OC-12c/STM-4c Multimode 1-Port OC-12c/STM-4c Single-Mode 1-Port Channelized OC-3/STM-1 CES Multimode 1-Port Channelized OC-3/STM-1 CES Single-
PC PC PC PC PC VPC PC VPC
PC PC PC PC PC VPC PC VPC
NA NA NA NA NA 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.
Release 9.0.0 C-43

Release 9.0.0 255-700-447

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. 20N33 20N36 23N69 23N33 23N64 24N64 23N35 23N61 23N60 23N62 23N68 20N03 20N02 20N22 23N03 23N74 23N02 20N29 20N28 23N27 23N29 23N26 23N25
Product Name
6-Port DS1 IMA 6-Port Enhanced DS1/T1 Multiservice 8-Port HDSL-2 (HDSL2 MS) 12-Port Medium-Density DS1 IMA 12-Port Medium-Density DS1 Multiservice 12-Port Medium-Density DS1/E1/DS0A CES 24-Port High-Density DS1 Multiservice
1-Port Channelized DS3 CES 1-Port Channelized DS3 Multiservice 1-Port Channelized STS-1e, T1 Format 1-Port DS3 IMA 1-Port Unchannelized DS3 Frame Relay 2-Port DS3 ATM 2-Port E3 ATM 3-Port Channelized DS3/STS-1e CES 3-Port DS3/E3 ATM 3-Port Unstructured DS3/E3 CES
DSP2 Voice Servers
DSP2A Voice Server DSP2B Voice Server DSP2C Voice Server DSP2D Voice Server DSP2E Voice Server DSP2F Voice Server
Release 9.0.0 D-1
Appendix D PSAX Module Features

Table D-1. PacketStar PSAX Multiservice Media Gateway Modules (Continued)
Model No. 20N34 20N56 23N34 23N66 23N40 20N40 23N12 23N13 23N75 23N76 23N72 23N73 20N72 20N73 20N12 20N14 20N13 20N15 20N92 20N93 20N62 20N64 20N63 20N65 24N70 24N71 24N72 24N73 23N41 20N41 23N28
Product Name
6-Port E1 IMA 6-Port Enhanced E1 Multiservice 21-Port High-Density E1 IMA 21-Port High-Density E1 Multiservice
4-Port Ethernet Ethernet

1-Port Channelized OC-3/STM-1 CES Multimode 1-Port Channelized OC-3/STM-1 CES Single-mode 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Multimode 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Single-Mode 1-Port OC-12c/STM-4c Multimode 1-Port OC-12c/STM-4c Single-Mode 1-Port OC-3c 1+1 APS Multimode 1-Port OC-3c 1+1 APS Single-Mode 1-Port OC-3c Multimode with AQueMan 1-Port OC-3c Multimode with Traffic Shaping 1-Port OC-3c Single-Mode with AQueMan 1-Port OC-3c Single-Mode with Traffic Shaping 1-Port STM-1 1+1 MSP Multimode 1-Port STM-1 1+1 MSP Single-Mode 1-Port STM-1 Multimode with AQueMan 1-Port STM-1 Multimode with Traffic Shaping 1-Port STM-1 Single-Mode with AQueMan 1-Port STM-1 Single-Mode with Traffic Shaping 2-Port OC-3c/STM-1 ATM Multimode 2-Port OC-3c/STM-1 ATM Single-Mode 4-Port OC-3c/STM-1 Multimode 4-Port OC-3c/STM-1 Single-Mode
Enhanced Router Route Server Tones and Announcements Server

2-Port High Speed

PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 D-2 Release 9.0.0 255-700-447

Table D-1. PacketStar PSAX Multiservice Media Gateway Modules (Continued)
Model No. Product Name 20N07 6-Port Multiserial 23N07 20N32 20N30 Quadserial
4-Port Voice 2-Wire Office 8-Port Voice 2-Wire Station

6-Port DS1 IMA Module (20N33)
The 6-Port DS1 IMA module has six physical RJ-45 ports. The inverse multiplexing 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 39 Mbps of bandwidth. A maximum of three IMA groups may be configured per module. 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 virtual circuit connections. IMA dynamically handles conditions when T1s within an IMA group become unavailable: the IMA "pipe" shrinks in bandwidth 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
Release 9.0.0 D-3

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 Standards 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) channelized 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-emulation 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 maximum 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 provided, 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 device using 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 protocol (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
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 D-4
Release 9.0.0 255-700-447

ITU-T I.370 (Frame relay policing) Congestion management Traffic policing
Hardware Features
The 6-Port Enhanced DS1/T1 Multiservice module has the following hardware features: Number of ports: 6 Connector type: RJ-45 Line rate: 1.544 Mbps 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 configured 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) circuit 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 provided, 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 emulation service can be configured to use only a fraction of the time slots, you can configure several independent emulated circuits to share one service interface. 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.
Release 9.0.0 D-5

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 CE: Circuit emulation service (CES) with ISDN PRI using 64 Kbps clear channel; 1x64 Kbps structured CAS; Nx64 Kbps structured CCS; unstructured CES
Hardware Features
The 8-Port HDSL-2 module provides the following hardware features: Number of ports: 8 Connector type: one, 50-pin Mini-Champ connector Line rate: 1.552 Mbps 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 modules inverse multiplexing for ATM capability allows you to strap 2 to 12 of the physical ports together to create ATM interfaces 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 virtual circuits. The module supports UNI v3.a, UNI v4.0, IISP, PNNI, and ILMI. This functionality enables service providers to offer both individual unchannelized 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 combining 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 systems viewpoint, these IMA groups are simply new ATM interfaces 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 protocols 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
Release 9.0.0 255-700-447

Hardware Features
The 12-Port Medium-Density DS1 IMA module provides the following hardware features: Number of ports: 12 Connector type: one Mini-Champ connector that mates with the AMP cable #1324936-1 Line rate: 1.544 Mbps 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 provide 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 voice data) to ATM virtual channels. By using structured (channelized) circuit emulation, this module can adapt a maximum of 24 DS1channels per port to ATM virtual channels with individual virtual path identifiers (VPIs) and virtual channel identifiers (VCIs). Signaling bit transport is also provided, 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 emulation service can be configured to use only a fraction of the time slots, you can configure several independent emulated circuits to share one service interface. 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 network interface to an ATM network. Software Features The 12-Port Medium-Density DS1 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; PNNI 1.0, all with traffic shaping CE: Circuit emulation service (CES) with ISDN PRI using 64 Kbps clear channel; 1 x 64 Kbps structured CAS; unstructured CES HDLC passthrough mode (N x 56 and N x 64) Frame relay UNI and NNI (FRF.1, FRF.2, FRF.5, and FRF.8)
PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 D-7

GR-303 CAS Trunkline ITU-T I.370 (Frame relay policing) Congestion management Traffic policing
Hardware Features
The 12-Port Medium-Density DS1 Multiservice module provides the following hardware features: Number of ports: 12 Connector type: one Mini-Champ connector Line rate: 1.544 Mbps Physical interfaces supported: ITU-T G.703, ITU G.704 Line encoding mode: B8ZS, AMI Loopback capabilities: line loopback, local loopback 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) Framing mode: ESF, D4
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) structured, 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 description 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 supports the following services: Circuit emulation service (CES): ~ Structured DS1 signal transport ~ Nx64 Kbps circuit emulation (where 1<=N<=24)

~ 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 supports the following services: Circuit emulation service (CES): ~ Structured E1 signal transport ~ Nx64 Kbps circuit emulation (where 1<=N<=24) ~ Channel-associated signaling (CAS) Nx64 CAS trunkline 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 (DS0A Mode) module supports 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 following 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
Release 9.0.0 D-9

~ 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 channelized and unchannelized frame relay configurations, circuit emulation service (CES), CAS trunkline service, high-level data link control (HDLC) passthrough mode, integrated services digital network with a primary rate interface (ISDN PRI) service, and ATM services. All services are available in protected 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 the PacketStar PSAX 24-Port High-Density DS1 Multiservice Module User Guide. Software Features The 24-Port High-Density DS1 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; PNNI 1.0, all with traffic shaping
Release 9.0.0 255-700-447

CE: Circuit emulation service (CES) with ISDN PRI using 64 Kbps clear channel; 1x64 Kbps structured CAS; Nx64 Kbps structured CCS; unstructured CES HDLC passthrough mode (Nx56 and Nx64) with bit inversion Frame relay UNI and NNI (FRF.1, FRF.2, FRF.5, and FRF.8) GR-303 CAS trunkline
Hardware Features
The 24-Port High-Density DS1 Multiservice module provides the following hardware features: Number of ports: 24 Connector type: two 50-pin .050 CHAMP receptacles Line rate: 1.544 Mbps Physical interfaces supported: ITU-T G.703, ITU-T G.704 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) Framing mode: ESF, D4

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 channelized into 24 individual DS0s, providing a total of 672 channels. Each virtual DS1 port can also be set up as a single, structured or unstructured channel. The 1-Port Channelized DS3 CES module provides circuit emulation service only. The 1-Port Channelized DS3 Multiservice module provides the following interfaces: ATM IISP (network/user) ATM PNNI 1.0 ATM UNI 3.0, 3.1, and 4.0 CAS trunkline Circuit emulation 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 netPacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 255-700-447 Release 9.0.0 D-11
Frame relay (UNI, NNI) GR-303 HDLC pass-through PRI ISDN (network/user)

work interface to an ATM network. The module can be configured to provide N x 64 Kbps (fractional DS1) structured 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. By using structured (channelized) circuit emulation, the 1-Port Channelized DS3 Multiservice 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). The module can be connected 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 the 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. 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) Circuit emulation service (CES): ~ Unstructured and structured DS1 signal transport ~ Nx64 Kbps circuit emulation (where 1=N=24) ~ Channel-associated signalling (CAS) Integrated services digital network with primary rate interface service (PRI 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 following hardware features: Number of ports: one port supports 28 virtual DS1 ports Connector type: two BNC connectors, one to receive data and one to transmit data Line rate: 44.736 Mbps Line encoding mode: B3ZS Framing mode for CES: ESF and D4
Release 9.0.0 255-700-447

Line type: C-bit parity, M13 Loopback capability: local loop, line loop Transmit clock: local timing, loop timing Line buildout: short (0133 feet), long (134266)
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 configurable to function in either DS3 or STS-1e modes. This dual-mode capability allows you to deliver channelized DS3 or STS-1e configurations while maintaining inventory of a single module type. The modules three high-speed circuit emulation network interfaces operate at Digital Signal Level 3 (DS3), with a line rate of 44.736 Mbps, or at Synchronous 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 services 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 terminating 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) structured 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 (channelized) 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 circuitemulation 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 customer interface equipment and network interface equipment, for example,

between PSAX central office (CO) products and customer premises equipment (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 services: Circuit emulation service (CES): ~ Structured DS1 signal transport ~ Nx64 Kbps circuit emulation (where 1<=N<=24) ~ Channel-associated signaling (CAS) 1x56 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 DSP2x Voice Server modules.
Hardware Features
The 3-Port Channelized DS3/STS-1e CES module provides the following hardware features: Number of ports: 3 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 Line encoding mode: B3ZS Loopback capabilities: line loopback, local loopback, and DS1 ANI in-line codes for loopback Line buildout: short (0133 feet); long (134266 feet) Framing modes: ESF and SF for CES
The 3-Port Channelized DS3/STS-1e Multiservice Protection module provides N:1 traffic protection when used within a protection group. In addition to its N:1 Protection capabilities, this module provides ATM, circuit emulation, 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 capability simplifies ordering, inventory management, and manufacturability. The modules three channelized multiservice interfaces operate at Digital Signal Level 3 (DS3), with a line rate of 44.736 Mbps, or at Synchronous 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 multiservices. Typically, 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.

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

The 1-Port Channelized STS-1e, T1 Format module provides one physical port with a line rate of 51.84 Mbps. The physical port is divided (channelized) 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 structured or unstructured channel. The 1-Port Channelized STS-1e, T1 Format module provides the following interfaces: ATM IISP (network/user) ATM PNNI 1.0 ATM UNI 3.0, 3.1, and 4.0 CAS trunkline Circuit emulation The user can configure this module to provide n X 64 Kbps (fractional DS1) structured 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. Signaling bit transport is also provided, using ATM Forum standards 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 independent emulated circuits to share one service interface. The 1-Port Channelized STS-1e, T1 Format module uses ATM Forum specifications UNI 3.0 or UNI 3.1, which allow any DS1 port to act as a user network 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 signal transport N X 64 kbps circuit emulation service (1 = N = 24) Primary ISDN service with optional HDLC pass-through mode for the D-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
Frame relay (UNI, NNI) GR-303 HDLC pass-through PRI ISDN (network/userP

~ 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 hardware features: Number of ports: one port supports 28 virtual DS1 ports Connector type: two BNC connectors, one to receive data and one to transmit data Line rate: 51.84 Mbps Line encoding mode: B3ZS Framing mode for CES: ESF and D4 Loopback capability: local loop, line loop Transmit clock: local timing, loop timing Line buildout: short (0133 feet), long (134266)
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 connect the PSAX system to an ATM edge switch or digital subscriber line aggregation 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 encoding mode: B3ZS Line type: C-bit parity, clear channel Loopback capabilities: local loop, line loop, payload loop Cell mapping: PLCP, direct mapping
Release 9.0.0 255-700-447

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

The 1-Port Unchannelized DS3 Frame Relay module provides an unchannelized, 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. Software Features Multiservices: 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 HDLC pass-through Frame Relay The 1-Port Unchannelized DS3 Frame Relay module has interfaces for framerelay network-level interworking (FRF.5) and service-level interworking (FRF.8). These features enable the PSAX 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 1-Port Unchannelized DS3 Frame Relay module. Frame relay policing enables the user to manage 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). HDLC Pass-through Each port on the 1-Port Unchannelized DS3 Frame Relay module can be configured to perform adaptation for high-level data link control (HDLC) passthrough. 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 hardware features: Number of ports: 1 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
Release 9.0.0 D-17

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 PacketStar PSAX 1-Port Channelized DS3 Multiservice Module User Guide) and the 6Port 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 DS1 ATM 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 Connector type: two BNC connectors, one to receive data and one to transmit data Line rate: 44.736 Mbps 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 interfaces. 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 receive connector and one transmit connector)
Release 9.0.0 255-700-447

Line rate: 34.368 Mbps (typical) Line encoding mode: HDB3 Line type: G832 Loopback capabilities: local loop, line loop, payload loop Cell mapping: direct mapping
3-Port Unstructured DS3/E3 CES Module (23N02)

The 3-Port Unstructured DS3/E3 CES module provides a clear channel, highspeed 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 emulation 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 hardware features: Number of ports: 3 Connector type: 6 BNC connectors for the 3 ports (each port has one receive connector and one transmit connector) Line rate: 44.736 Mbps (DS3); 34.368 Mbps (E3) Line encoding mode: B3ZS Loopback capabilities: line loopback, local loopback Line buildout: short (0133 feet); long (134266 feet) Framing mode: N/A
Release 9.0.0 D-19

DSP2 Voice Servers
DSP2 Voice Servers

DSP2x Voice Server Modules (23N27 (C), 23N29 (D), 23N26 (E), and 23N25 (F))
The DSP2x 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 features to selected DS0 channels: toll quality voice compression, echo cancellation, silence suppression, comfort noise insertion, fax demodulation/remodulation, and Packet Pipe AAL5-to-AAL2 Wireless Trunking. All modules have two types of LED indicators: FAIL and ACTIVE. All DSP2x Voice Server modules process circuit emulation voice traffic entering 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 DSP2x Voice Server Modules maintain required levels of voice quality while conserving network bandwidth by using digital signal processor technology 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 DSP2x 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 multiplexing 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.

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 virtual circuit connections. IMA dynamically handles conditions when E1s within an IMA group become unavailable: the IMA "pipe" shrinks in bandwidth 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 single module.
Hardware Features
The 6-Port E1 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: 2.048 Mbps Line encoding mode: HDB3 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 connection are provided, with a total of 180 HDLCs per module. This module provides 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 feature allows the module to interface with a time-division multiplex (TDM) channelized E1 circuit. The 6-Port Enhanced E1 Multiservice module provides the following interfaces: ATM IISP (network/user) ATM PNNI 1.0 ATM UNI 3.0, 3.1, and 4.0 CAS trunkline Circuit emulation Frame Relay (UNI, NNI) HDLC pass-through PRI ISDN (network/user)
Release 9.0.0 D-21

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 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. 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-associated signaling (CAS). With the 64 Kbps clear channel capability, the 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 configured to use only a fraction of the time slots, several independent emulated circuits can be configured to share one service interface. Software Features Multiservices: ATM: ATM UNI 3.0 and 3.1; Interim inter-switch signaling protocol (IISP) user, IISP network CE: Circuit emulation service (CES) with ISDN PRI using 64 Kbps clear channel; dynamic bandwidth circuit emulation service (DBCESproprietary version); 1 X 64 Kbps structured CAS; unstructured CES HDLC Passthrough 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 6-Port Enhanced E1 Multiservice module has the following hardware features: Number of ports: 6 Connector type: RJ-45 (120-Ohm, symmetrical pair [4-wire] interface) Line rate: 2.048 Mbps Line encoding mode: HDB3 Framing mode for CES: cyclic redundancy check-multifrequency (CRC-mf) (also known as CRC-4) Loopback capabilities: local loop, line loop Transmit clock: local timing, loop timing
Release 9.0.0 255-700-447

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 modules 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 virtual 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 combining the transport bandwidths of multiple E1 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 systems viewpoint, these IMA groups are simply new ATM interfaces sized as multiples of E1. (Refer to Inverse Multiplexing for ATM Version 1.1, afphy-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: Number of ports: 21 Connector type: 2 Mini-Champ connectors Line rate: 2.048 Mbps Physical interfaces supported: ITU-T G.703, ITU-T G.704 Line encoding mode: HDB3 (default), AMI Loopback capabilities: line loopback, local loopback Line buildout: N/A Framing mode: CRC4-CAS
Release 9.0.0 D-23

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 Multiservice module maps up to 31 individual high level data links (HDLC) on a single E1 connection (180 HDLC data links per module). This module provides 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 capability, which allows it to interface directly to an E1 line with multiple repeaters. This feature allows the module to interface with a time-division multiplex (TDM) channelized E1 circuit. You can configure the 21-Port High-Density E1 Multiservice module to provide 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 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-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 configured to use only a fraction of the time slots, you can configure several independent emulated circuits to share one service interface. The 21-Port High-Density E1 Multiservice module uses ATM Forum Specification 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 clear channel; 1 x 64 Kbps structured CAS; unstructured CES Frame relay UNI and NNI (FRF.1, FRF.2, FRF.5, and FRF.8) HDLC Passthrough with bit inversion ITU-T I.370 (Frame relay policing) Congestion management Traffic policing
Release 9.0.0 255-700-447

Hardware Features
The 21-Port High-Density E1 Multiservice module provides the following hardware features: Number of ports: 21 Connector type: two Mini-Champ connectors that mate with the Lucent cable (COMCODE 300550639) Line rate: 2.048 Mbps Physical interfaces supported: ITU-T G.703, ITU G.704 Line encoding mode: HDB3 Loopback capabilities: line loopback, local loopback Line buildout: N/A 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 halfor full-duplex port speeds. Each of the physical ports can be configured independently 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


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 Connector type: RJ-45 Total MTU: 1,522 bytes for an Ethernet packet excluding FCS and extension ~ 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 extension ~ 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 approximately 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 configuration and the number of ports configured.
Maximum number of connections per module: 120
Release 9.0.0 255-700-447

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 that transmit 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 processing 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 4Port 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.
MulticastingIf 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: Number of ports: 6 ~ physical ports: 5 ~ virtual port used for backplane connections: 1 Connector type: RJ-45 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:
Release 9.0.0 D-27

~ Per port: port 1 supports 10 Mbps (10BASE-T) or 100 Mbps (100BASE-T); ports 2, 3, 4, and 5 each support 10 Mbps ~ Aggregate bandwidth of all ports, maximum: 30 Mbps throughput Line encoding modes: NA Loopback capabilities: NA Line build out: NA Framing modes: NA

1-Port Channelized OC-3/STM-1 CES Module (23N12 (MM)/23N13 (SM))
The 1-Port Channelized OC-3/STM-1 CES modules (23N13 (SM) and 23N12 (MM)) offer two operating modes: The OC-3 CES operational mode supports 84 asynchronous VT1.5s (DS1s), with each DS1 supporting 24 DS0s. In the OC-3 mode, up to 2 DS0s per T1 can be configured for the HDLC support. The STM-1 operating mode supports 63 asynchronous, channelized VC-12 (E1) interfaces for circuit emulation services (ISDN) and the HDLC Passthrough Interface. Each E1 supports 30 DS0s. The line rate of the modules is approximately 155 Mbps. The linear 1+1 APS/MSP feature provides protection against facility, port, or module failure. The linear APS/MSP feature supports 1+1 protection only; the N:1 protection feature is not supported by this module. The 1+1 architecture consists of a far-end signal that is continuously bridged (at the electrical level) to the APS/MSP working and APS/MSP protection I/O modules so that the same payloads are transmitted identically to the nearend working and protection I/O modules. At the near-end, the working and protection OC-3/STM-1 signals are monitored 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 continuous far-end bridge, the 1+1 architecture does not allow an unprotected extra traffic channel to be provided. The module is supplied with the following transmission types: Single-mode (SM) module (23N13) is intended for long-reach applications, typically between LANs. This module is frequently used to connect highspeed LAN devices (such as routers) to an ATM network. Multimode (MM) module (23N12) is intended for short-reach applications, for example, interoffice or intraoffice sections of a local area network (LAN). Software Features The 1-Port Channelized OC-3/STM-1 CES module supports the following services: Circuit emulation service (CES):

~ Structured DS1 signal transport ~ Nx64 Kbps circuit emulation (where 1<=N<=24) ~ Channel-associated signaling (CAS) 1x56 AAL2 cell formatting for interworking with the DSP2x Voice Server modules. The following feature is provided with limited support by the module: Integrated services digital network with primary rate interface service (PRI ISDN) with 64 Kbps clear channel capability for the D-channel
Hardware Features
The 1-Port Channelized OC-3/STM-1 CES modules have the optical specifications shown in Table D-2.
Table D-2. 1-Port Channelized OC-3/STM-1 CES Module Optical Specifications Feature Module Ch OC-3/STM-1 CES SM Ch OC-3/STM-1 CES MM
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber optic cable Fiber optic cable reach (approximate, depending on fiber makeup) Line rate, per port Optical wavelength (nominal value) Optical input sensitivity Optical output power Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
SC (snap-on connector) SC (snap-on connector) single-mode 15 km (9.3 miles) 155 Mbps (SONET) 1,310 nm -31 to -8 dBm -15 to -8 dBm -15 dBm -8 dBm -31 dBm -8 dBm multimode 2 km (6,560 feet or 1.2 miles) 155 Mbps (SONET) 1,310 nm -30 to -14 dBm -20 to -14 dBm -20 dBm -14 dBm -30 dBm -14 dBm
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 services only.
Release 9.0.0 D-29

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 nearend working and protection I/O modules. At the near-end, the working and protection OC-3 or STM-1 signals are monitored 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 continuous far-end bridge, the 1+1 architecture 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 applications, 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 applications, for example, connecting interoffice or intraoffice sections of a local area network (LAN). For instructions on configuring and guidance on using these modules, see the PacketStar 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 Module Feature CH OC-3/STM-1 UNSTR/ATM SM CH OC-3/STM-1 UNSTR/ATM MM
Number of ports
Type of connector (two for each module, trans- SC (snap-on connec- SC (snap-on connecmit and receive) tor) tor) Type of fiber optic cable Fiber optic cable reach (approximate, depending on fiber makeup) Line rate, per port Optical wavelength (nominal value) Optical input sensitivity Optical output power single-mode 15 km (9.3 miles) 155 Mbps 1,310 nm -31 to -8 dBm -15 to -8 dBm multimode 2 km (6,560 feet or 1.2 miles) 155 Mbps 1,310 nm -30 to -14 dBm -20 to -14 dBm
Release 9.0.0 255-700-447

Table D-3. 1-Port Channelized OC-3/STM-1 Unstructured CES/ATM Module Optical Specifications Module Feature CH OC-3/STM-1 UNSTR/ATM SM CH OC-3/STM-1 UNSTR/ATM MM
Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
-15 dBm -8 dBm -31 dBm -8 dBm
-20 dBm -14 dBm -30 dBm -14 dBm
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 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 signals are monitored 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 continuous 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 reliable 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. Crossport 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 concatenated 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 highspeed 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).
Release 9.0.0 D-31

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 in Table D-4.
Table D-4. 4-Port OC-3c/STM-1 Module Optical Specifications Feature Module OC-3c/STM-1 SM OC-3c/STM-1 MM
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber optic cable Fiber optic cable reach (approximate, depending on fiber makeup) Line rate, per port Line rate, module total Optical wavelength (nominal value) Optical input sensitivity Optical output power Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
4 SC (snap-on connector) single-mode 15 km (9.3 miles) 155 Mbps (SONET) 1,310 nm -31 to -8 dBm -15 to -8 dBm -15 dBm -8 dBm -31 dBm -7 dBm
4 SC (snap-on connector) multimode 2 km (6,560 feet or 1.2 miles) 155 Mbps (SONET) 1,310 nm -30 to -14 dBm -20 to -14 dBm -20 dBm -14 dBm -30 dBm -14 dBm
622.08 Mbps (SONET) 622.08 Mbps (SONET)
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 applications. These modules provide a fiber-optic interface operating in the concatenated 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 bidirectional and unidirectional modes. The module is supplied with the following transmission types:
Release 9.0.0 255-700-447

Single-mode (SM) module (23N73) is intended for long-reach applications, typically between LANs. This module is frequently used to connect highspeed LAN devices (such as routers) to an ATM network. Multimode (MM) module (23N72) is intended for short-reach applications, for example, interoffice or intraoffice sections of a local area network (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.
Table D-5. 1-Port OC-12c/STM-4c Module Optical Specifications Feature Single-Mode Multimode
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber optic cable Fiber optic cable reach (approximate, depending on fiber makeup) Line rate, per port Optical wavelength (nominal value) Transmitter minimum optical output power Transmitter maximum optical output power Receiver minimum optical input power (average) Receiver maximum optical input power (average)
SC (snap-on connector) SC (snap-on connector) single-mode 15 km (9.3 miles) 622.08 Mbps 1,313 nm -15 dBm -8 dBm -28 dBm -7 dBm multimode 500 meters (1,640 feet) 622.08 Mbps 1,330 nm -20 dBm -14 dBm -29 dBm -11 dBm
1-Port OC-3c Module with AQueMan (20N12 (MM)/20N13 (SM)) or Traffic Shaping (20N14 (MM)/20N15 (SM))
The 1-Port OC-3c with AQueMan (20N12 (MM)/20N13 (SM)) or Traffic Shaping (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. The module is supplied with the following transmission types: 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.

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 optical specifications shown in Table D-6.
Table D-6. 1-Port OC-3c Module with AQueman or Traffic Shaping Optical Specifications Module Feature OC-3c (SM AQ) or OC-3c (SM TS) OC-3c (MM AQ) or OC-3c (SM TS)
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber optic cable Fiber optic cable reach (approximate, depending on fiber makeup) Line rate Optical wavelength (nominal value) Optical input sensitivity Optical output power System gain Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
1 SC (snap-on connector) single-mode 15 km (9.3 miles) 155 Mbps (SONET) 1,310 nm -31 to -8 dBm -15 to -8 dBm 15 dB -15 dBm -8 dBm -31 dBm -8 dBm
1 SC (snap-on connector) multimode 2 km (6,560 feet or 1.2 miles) 155 Mbps (SONET) 1,310 nm -32.5 to -14 dBm -20 to -14 dBm 13.5 dB -20 dBm -14 dBm -32.5 dBm -14 dBm
Release 9.0.0 255-700-447

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

The 1-Port OC-3c 1+1 Automatic Protection Switching (APS) modules provide 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. The module is supplied with the following transmission types: Single-mode (SM) module (20N73) is intended for long-reach applications, typically between LANs. This module is frequently used to connect highspeed LAN devices (such as routers) to an ATM network. Multimode (MM) module (20N72) is intended for short-reach applications, for example, interoffice or intraoffice sections of a local area network (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 Feature Module Single-Mode Multimode
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber optic cable Fiber optic cable reach (approximate, depending on fiber makeup) Line rate, per port Optical wavelength (nominal value) Optical input sensitivity Optical output power Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
1 SC (snap-on connector) single-mode 15 km (9.3 miles) 155 Mbps (SONET) 1,310 nm -31 to -8 dBm -15 to -8 dBm -15 dBm -8 dBm -31 dBm -8 dBm
1 ST (straight tip) multimode 2 km (6,560 feet or 1.2 miles) 155 Mbps (SONET) 1,310 nm -30 to -14 dBm -20 to -14 dBm -20 dBm -14 dBm -30 dBm -14 dBm
Release 9.0.0 D-35

1-Port STM-1 Module with AQueMan (20N62 (MM)/20N63 (SM)) or Traffic 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. The module is supplied with the following transmission types: 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 the names 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 Module Feature STM-1 (SM TS) or STM-1 (MM AQ) STM-1 (MM TS) or STM-1 (MM AQ)
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber-optic cable
1 SC (snap-on connector) single-mode
1 ST (straight tip) multimode
Release 9.0.0 255-700-447

Table D-8. 1-Port STM-1 Module Optical Specifications (Continued) Module Feature STM-1 (SM TS) or STM-1 (MM AQ) STM-1 (MM TS) or STM-1 (MM AQ)
Fiber-optic cable reach (approximate, depending on fiber makeup) Line rate Optical wavelength (nominal value) Optical input sensitivity Optical output power System gain Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
15 km (9.3 miles) 155 Mbps 1,310 nm -31 to -8 dBm -15 to -8 dBm 15 dB -15 dBm -8 dBm -31 dBm -8 dBm
2 km (6,560 feet or 1.2 miles) 155 Mbps 1,310 nm -32.5 to -14 dBm -20 to -14 dBm 13.5 dB -20 dBm -14 dBm -32.5 dBm -14 dBm
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 provide 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 bidirectional and unidirectional modes. Non-revertive, or non-automatic, switchback reduces a service interruption due to link failure from two interruptions to one interruption. The module is supplied with the following transmission types: Single-mode (SM) module (20N93) is intended for long-reach applications, typically between LANs. This module is frequently used to connect highspeed LAN devices (such as routers) to an ATM network. Multimode (MM) module (20N92) is intended for short-reach applications, for example, interoffice or intraoffice sections of a local area network (LAN). Software Features The STM-1 1+1 MSP modules use the AQueMan algorithm for traffic flow control.
Release 9.0.0 D-37

Hardware Features
The 1-Port STM-1 1+1 MSP modules have the optical specifications shown in Table D-9.
Table D-9. 1-Port STM-1 1+1 MSP Module Optical Specifications Feature Module STM-1 SM MSP STM-1 MM MSP
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber-optic cable Fiber-optic cable reach (approximate, depending on fiber makeup) Line rate, per port Optical wavelength (nominal value) Optical input sensitivity Optical output power Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
1 SC (snap-on connector) single-mode 15 km (9.3 miles) 155 Mbps 1,310 nm -31 to -8 dBm -15 to -8 dBm -15 dBm -8 dBm -31 dBm -8 dBm
1 ST (straight tip) multimode 2 km (6,560 feet or 1.2 miles) 155 Mbps 1,310 nm -30 to -14 dBm -20 to -14 dBm -20 dBm -14 dBm -30 dBm -14 dBm
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 against facility, port, or module failure. 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-3c signals are monitored independently and identically for failures. The receiving I/O modules select either the working or the protection signal as the one from which
Release 9.0.0 255-700-447

to select the traffic, based on switch initiation criteria. Because of the continuous far-end bridge, the 1+1 APS/MSP 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 reliable data transport. The mapping must be port n on the working module to port n on the protection module, for both ports. Cross-port protection configuration 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 applications, 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 applications, 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 Feature Module OC-3c/STM-1 SM OC-3c/STM-1 MM
Number of ports Type of connector (two for each module, transmit and receive) Type of fiber optic cable Fiber optic cable reach (approximate, depending on fiber makeup) Line rate, per port Line rate, module total Optical wavelength (nominal value) Transmitter minimum optical output power (average) Transmitter maximum optical output power (average) Receiver minimum optical input power (average) Receiver maximum optical input power (average)
2 SC (snap-on connector) single-mode 15 km (9.3 miles) 155 Mbps 310 Mbps 1,310 nm -15 dBm -8 dBm -31 dBm -7 dBm
2 SC (snap-on connector) multimode 2 km (6,560 feet or 1.2 miles) 155 Mbps 310 Mbps 1,310 nm -20 dBm -14 dBm -30 dBm -14 dBm
Release 9.0.0 D-39


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 supporting existing PSAX multiservice interworking capabilities, the module provides 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 connection 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 15171520) Eight VPNs

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 networks (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.)
Release 9.0.0 D-41

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) available 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 for maximum 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, authentication 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 multicasting. 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 cannot 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 module): 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)
Release 9.0.0 255-700-447

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 customers 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 circuit 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 circuit 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 module, 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 Information Tones (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 cannot distinguish recorded voice from live voice answer unless a machine-detectable signal is included the recorded announcement. Defined SITs identify network-provided announcements. 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
Channel Associated Signaling (CAS)

~ 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 backplane 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 calculate 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 CES Conversion The module also supports bit stuffing and 56K64K circuit emulation service (CES) conversion. The framing for SS7's Message Transfer Part (MTP) Level 2 is a modified version 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 terminate 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 modules capabilities. Release 9.0.0 255-700-447

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) Frame relay UNI and NNI (FRF.1, FRF.2, FRF.5, and FRF.8) HDLC Passthrough Terminal emulation ITU-T I.370 (frame relay policing) Congestion management Traffic policing The following sections explain the application of the interfaces supported on the 6-Port Multiserial module: frame relay, circuit emulation, terminal emulation, 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 dialaccess servers, IBM SNA equipment, and other devices configured for framerelay 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 manage 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 Constant 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 Multiservice Media Gateway system to interface with non-frame relay routers, video encoders, encryption devices, and other devices which use a synchronous interface. Each port on the 6-Port Multiserial module can be configured to perform an adaptation for terminal emulation. The implementation of ATM Adaptation Layer 5 (AAL-5) allows for the transmission of terminal emulation data as Variable Bit Rate (VBR) traffic across an ATM network. With terminal emulation support, the 6-Port Multiserial module can adapt and concentrate terminal emulation traffic onto an ATM network. This feature enables the Multiservice Media Gateway system to interface with terminal equipment such as monitors, craft interfaces, console ports, sensors, and other devices implementing an asynchronous interface.
Terminal Emulation
Release 9.0.0 D-45

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 feature, 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. Each port on the 6-Port Multiserial module can be configured for ATM service as per the ATM Forums 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 network 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 physical layer protocol that maintains cell extraction capability at bit-error rates up to 10 to the negative second power (-2). LANET overhead accounts for 0.63% of link bandwidth. It can be implemented over each of the supported serial interface types, and is independent of the transmission rate.
ATM
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 configured as either a data terminating equipment (DTE) or a data communications equipment (DCE) device. Line rate: ~ Minimum: 75 bps per port (asynchronous); 300 bps per port (synchronous) ~ 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 Line buildout: N/A 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 asynchronous transfer mode (ATM). Each port on the module provides a maximum line rate of 16 Mbps and a minimum line rate of 56 Kbps. The maxiPacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 D-46 Release 9.0.0 255-700-447

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 equipment (DTE) or data communications equipment (DCE). The Quadserial module also supports bit stuffing and 56K64K circuit emulation service (CES) conversion, available as standard features in the Release 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 difference 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 AFVTOA-0078.000 HDLC Passthrough 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 Quadserial module provides the following hardware features: Number of ports: 4 serial (serial interface leads comply with AF-VTOA0119.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 system 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 modules capabilities. Release 9.0.0 D-47

Line encoding mode: N/A Loopback capabilities: line loopback and local loopback from console, Telnet, or EMS interfaces Line buildout: N/A 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 telephone or other analog device. The coding translation supported by this module 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 synchronization with an incoming ringing signal to the port. Software Features This module is typically configured with an 8-Port Voice 2-Wire Station module 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: Number of ports: 4 Connector type: RJ-11 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 translation supported by this module is -law to -law only.
Release 9.0.0 255-700-447

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 synchronization with an incoming ringing signal to the port. Software Features The 8-Port Voice 2-Wire Station module can be used to establish a permanent virtual 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 telephone 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 station goes back on-hook. The PLAR service provides 20-Hz ring-down, loopstart 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: Number of ports: 8 Connector type: RJ-12 Ringing frequency: 20 Hz Termination impedance: 600 Ohms Signaling: none Supervision: loop start
Release 9.0.0 D-49

Release 9.0.0 255-700-447
Part Number: 2300M0A9001A1 Copyright 2003 Lucent Technologies All rights reserved.

PSAX2300UserGuide PDF

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

PSAX2300UserGuide PDF

Hochgeladen von

Copyright:

Verfügbare Formate

Top of Guide

PacketStar PSAX 2300 Multiservice Media Gateway User Guide

Doc. No.: 255-700-447

Legal Notices, Safety, and Regulatory Information

Release 9.0.0 iii

Legal Notices, Safety, and Regulatory Information

Regulatory Standards Compliance

PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 iv

Release 9.0.0 255-700-447

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

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

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

PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 vi

Release 9.0.0 255-700-447

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

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

Release 9.0.0 255-700-447

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

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

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

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

Release 9.0.0 255-700-447

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

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

Release 9.0.0 xiii

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

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

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

Release 9.0.0 255-700-447

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

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

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

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

Release 9.0.0 255-700-447

Release 9.0.0 xvii

Release 9.0.0 xix

PacketStar PSAX 2300 Multiservice Media Gateway User Guide, Issue 1 xx

Release 9.0.0 255-700-447

Release 9.0.0 xxiii

Release 9.0.0 255-700-447

Release 9.0.0 xxix

Release 9.0.0 255-700-447

Release 9.0.0 xxxi

Release 9.0.0 255-700-447

Release 9.0.0 255-700-447

Audience for This Guide

What You Should Know

Release 9.0.0 1-1

Chapter 1 Getting Started

Release 9.0.0 255-700-447

Chapter 1 Getting Started

Icons and Symbols

Command Description Tables

Field Description Tables

Release 9.0.0 1-3

Chapter 1 Getting Started

Identifies editable fields or display-only fields on screens

Identifies initial field value default

Field Name Interface Type

Field Values Default: 0 Range: 0-22 Format: Numeric

Identifies available range for field value when applicable

Decribes special instructions or configuration constraints