Lucent PacketStar PSAX 1250 User Manual

Multiservice media gateway
Table of Contents

Advertisement

Quick Links

®
PacketStar
PSAX 1250 Multiservice Media Gateway

User Guide

Issue 2, September 2002
System Software Release 8.0.0
Doc. No.: 255-700-247

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the PacketStar PSAX 1250 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Summary of Contents for Lucent PacketStar PSAX 1250

  • Page 1: User Guide

    ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide Issue 2, September 2002 System Software Release 8.0.0 Doc. No.: 255-700-247...
  • Page 2 Copyright © 2002 by Lucent Technologies. All rights reserved. For trademark, regulatory compliance, and related legal information, see the "Legal Notices, Safety, and Regulatory Information" section.
  • Page 3: Legal Notices, Safety, And Regulatory Information

    This material is protected by the copyright laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fash- ion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of the originating organization and the business management owner of the material.
  • Page 4: Warranty Warnings

    Equipment failure due to inadequate maintenance will void your equip- ment warranty. WARNING: Use only air filters supplied by Lucent Technologies in your PSAX chassis. Use of other air filters will void your equipment warranty. WARNING: Using excessive force to install modules that causes damage to the mod- ule and/or the chassis will void your equipment warranty.
  • Page 5: Regulatory Standards Compliance

    Regulatory Standards Compliance Regulatory Standards Compliance The PacketStar PSAX 1250 Multiservice Media Gateway, models 20S00 (19 in. chassis with AC or DC power) and 20S10 (23 in. chassis with DC power), is compliant with the listed Safety, Electromagnetic Compatibility (EMC) and Telecommunications standards.
  • Page 6: Regulatory Statements

    PSAX chassis is a label that contains the FCC registration number, in addition to other information. You must provide this information to the telephone company, if they request it. The FCC requires Lucent Technologies to provide you with the following information: 1.
  • Page 7: Canadian Regulatory Statements

    6. If you experience trouble with this equipment, or need repairs or war- ranty information, please refer to the Lucent Technologies InterNetworking Systems Global Warranty that accompanied your PSAX product shipment for instructions on obtaining technical support in your area.
  • Page 8: European Union Regulatory Statement

    EU-regulativer CE-mærkning Lucent Technologies erklærer hermed at PacketStar PSAX 1000 (-48 V dc og 220 v vekselstrøm), PSAX 1250 (-48 V dc og 220 v vekselstrøm), PSAX 2300, and PSAX 4500 Multiservice Media Gateways overholder kravene i følgende EU-direktiver: •...
  • Page 9 KWWSZZZOXFHQWFRPLQVGRFOLEUDU\ Euroopan unionin sääntelystandardi CE-merkintä Lucent Technologies vakuuttaa täten, että PacketStar PSAX 1000 (-48 V dc ja 220 V vaihtovirtaa), PSAX 1250 (-48 V dc ja 220 V vaihtovirtaa), PSAX 2300, ja PSAX 4500 Multiservice Media Gatewayt täyttävät seuraavien neuvoston direktiivien keskeiset vaatimukset ja asiaankuuluvat määräykset:...
  • Page 10 Norm van de Europese Unie CE-markering Lucent Technologies verklaart hierbij dat de PacketStar PSAX 1000 (-48 V dc en 220V wisselstroom), PSAX 1250 (-48 V dc en 220V wisselstroom), PSAX 2300, en PSAX 4500 Multi Service Media Gateways voldoen aan de essentiële vereisten en andere relevante bepalingen van de volgende Rich-...
  • Page 11 • Elektromagnetische compatibiliteit (EMC) 89/336/EEG • Radioapparatuur en telecommunicatie-eindapparatuur 1999/5/EG De Lucent PacketStar PSAX Multi Service Media Gateways die in de Europese Economische Ruimte (EER) zijn ingezet, zijn bestemd voor aansluiting op E1, E3, STM-1 en STM-4c netwerken. DE EU-verklaringen van overeenstem-...
  • Page 12: Japanese Regulatory Statements

    • Elektromagnetisk kompatibilitet (EMC) 89/336/EEC • Radioutrustning och telekommunikationskopplingsutrustning 1999/5/EC Lucent PacketStar PSAX Multiservice Media Gateways, som är placerad i EEA (European Economic Area), är avsedd för att anslutas till E1, E3, STM-1 och STM-4c nätverk. Europarådets Konformitetsdeklarationer kan ses på bild- skärm eller skrivas ut på...
  • Page 13: Cispr 22, En 55022, As/Nzs-3548 Class A Electromagnetic Compatibility (Emc) Regulatory Statement

    Legal Notices, Safety, and Regulatory Information Regulatory Statements Table 1. JATE Approved Modules Module Jate Model Module Description Approval Number Number 6-Port DS1 IMA ( IMA DS1 20N33 D00-0807 6-Port Enhanced DS1/T1 Multiservice ( DS1/T1 Enh 20N36 D00-0807 1-Port STM-1 Multimode with AQueMan ( STM-1 (MM AQ) 20N62 L00-0198...
  • Page 14 Legal Notices, Safety, and Regulatory Information Regulatory Statements ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 255-700-247...
  • Page 15: Table Of Contents

    Contents Legal Notices, Safety, and Regulatory Information ....iii Copyright ............. iii Trademarks .
  • Page 16 About Lucent Technologies ........
  • Page 17 Contents 220 V ac Power Supply ..........2-9 -48 V dc Power Supply .
  • Page 18 Contents ATM Terminal Emulation ..........3-18 UNI 4.0 Signaling .
  • Page 19 Contents Cell Bus Traffic Shaping ..........3-47 ATM Traffic Shaping .
  • Page 20 Contents Backing Up Configuration Data ........4-32 Configuring GR-303 .
  • Page 21 Contents Viewing the PNNI Neighbor Peer Table ........5-64 Viewing the PNNI Neighbor Peer Port Table.
  • Page 22 Contents Backing Up System Database Files ......... .10-2 Remote Database Operation.
  • Page 23 Contents Appendix B Pin Configurations ........B-1 Overview of This Appendix .
  • Page 24 Contents 1-Port Channelized STS-1e T1 Module ........E-7 Software Features.
  • Page 25 Contents 21-Port High-Density E1 IMA Module ........E-21 Software Features.
  • Page 26 Contents Software Features...........E-34 Hardware Features .
  • Page 27: List Of Figures

    List of Figures Main Menu Help Window ........... .1-6 ®...
  • Page 28 List of Figures 4-14 Console Interface Main Menu Window (Save Configuration Option Selected) ... .4-37 4-15 Remote Reboot Configuration Window (Primary Switchover Option Selected) ... .4-38 4-16 Remote Reboot Configuration Window (Reboot Primary CPU Option Selected) .
  • Page 29 List of Figures 5-26 PNNI SvccRcc Table ............5-61 5-27 PNNI SvccRcc Information Window .
  • Page 30 List of Figures 8-20 V5 Data Link Configuration Window ......... . .8-46 8-21 V5 User Port Table.
  • Page 31 List of Tables JATE Approved Modules ........... -xiii Text Conventions .
  • Page 32 List of Tables 4-12 PSAX System Performance Capabilities Per Node for Release 8.0.0 ....4-30 4-13 Field Descriptions for the Feature Turn On/Off Table ......4-35 4-14 Field Descriptions for the Protection Group Configuration Window.
  • Page 33 List of Tables Field Descriptions for the ATM Trunking Narrowband Routing Table Window ..7-25 Field Descriptions for the ATM Trunking Broadband Routing Table Window ... . 7-26 Field Descriptions for the Feature Turn On/Off Table.
  • Page 34 List of Tables APS Failure Reason Codes..........A-56 ARP Status Codes .
  • Page 35 List of Tables A-47 ntom Protection Reason Codes ..........A-101 A-48 OAM Activation Deactivation Result Codes .
  • Page 36 List of Tables A-88 VPN Trap Status Codes ..........A-157 CONSOLE Connector Pin Assignments .
  • Page 37: Getting Started

    Getting Started Purpose of This Guide ® The PacketStar PSAX 1250 Multiservice Media Gateway User Guide provides a description of the PSAX 1250 system and its functions and features. It also provides information about using the console interface to: • Configure basic system parameters and managing the PSAX 1250 system •...
  • Page 38: Related Reading

    Related Reading Product Information Library To install, operate, and configure your PSAX system and I/O and server mod- ules, read the PSAX publications provided on your Lucent Technologies PacketStar PSAX Multiservice Media Gateways Products, Product Information Library CD-ROM. Printed Documents...
  • Page 39: Icons And Symbols

    Chapter 1 Getting Started Conventions Icons and Symbols Follow all safety guidelines in this document to help prevent personal injury to you and damage to the PSAX 1250 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.
  • Page 40: Selecting Options, Fields, And Commands

    Chapter 1 Getting Started Conventions Identifies editable fields Describes the function of the field or display-only fields on Identifies initial field and special instructions for screens value default configuring modules Table 1-3. Field Description Table Example Field Name Field Value Description Default: 0 The end-to-end connection protocol used.
  • Page 41: Help Information

    Chapter 1 Getting Started Help Information Table 1-4. System Responses to Selecting Options, Fields, or Commands For a selected... the following occurs: option name The window corresponding to the option name is displayed. field The following variations occur: • The field entry area is blank or contains the default or previously entered value.
  • Page 42: Main Menu Help Window

    Chapter 1 Getting Started Help Information error codes and responses to commands. All responses and notifications are recorded in a trap log. See Appendix A 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.
  • Page 43: Technical Support

    Chapter 1 Getting Started Technical Support Technical Support If you experience a problem with your PSAX 1250 system, refer to the Lucent Technologies InterNetworking Systems Global Warranty, which accompanied your shipment, for instructions on obtaining support in your area. About Lucent Technologies...
  • Page 44: Psax 1250 Multiservice Media Gateway

    PSAX 1250 Multiservice Media Gateway The PacketStar PSAX 1250 Multiservice Media Gateway is designed to provide a full range of central office-based multiservice ATM access functions. Ideal for the central office or a large enterprise’s multiservice media gateway, the...
  • Page 45: Comments On This Guide

    PSAX 1250 Multiservice Media Gateway User Guide, please complete the comment card that accompanied your shipment and mail it to the following address: Senior Manager, Information Design and Development Team Lucent Technologies PacketStar PSAX Products 8301 Professional Place Landover, MD 20785 You can also fax the comment card to us at: 301-809-4540.
  • Page 46 Chapter 1 Getting Started Comments on This Guide ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 1-10 255-700-247...
  • Page 47: Hardware Description

    Hardware Description Overview of This Chapter This chapter presents a description of the PacketStar PSAX 1250 Multiservice Media Gateway system hardware. System Features The PacketStar PSAX 1250 Multiservice Media Gateway provides high-capac- ity, universal connectivity over an ATM wide area network (WAN).
  • Page 48 One is required for nonredundant operation. Two are required for active/standby operation. (see your Lucent Technologies sales representative for ordering information) • Input/output (I/O) and server modules (see your Lucent Technologies sales representative for ordering information). • Blank faceplate modules—required for empty I/O and server slots ®...
  • Page 49: Functional Description

    48.26-cm (19-in.) PSAX 1250 chassis. A 58.42-cm (23-in.) chassis with dc input power is available for the 58.42-cm (23-in.) PSAX 1250 chassis (see your Lucent Technologies sales representa- tive for ordering information). Functional Description Chassis The PSAX 1250 system can support either one or two Stratum 3–4 modules,...
  • Page 50: Backplane

    Chapter 2 Hardware Description Functional Description If redundant Stratum 3–4 and Power supply modules are not used, the slots designated for these modules must remain empty. Blank faceplates are required in all empty slots. Backplane The chassis backplane distributes data, clock signals, and power to the mod- ules.
  • Page 51: Power Supply Modules

    In order to use the 220 V ac Power Supply module, you must order a suitable AC power cordset for use in your geographic location. For your convenience, Lucent Technologies has made a variety of international cordsets available for ordering. See your Lucent Tech- nologies representative for ordering details.
  • Page 52: Stratum 3-4 Module

    Chapter 2 Hardware Description Functional Description When the PSAX 1250 chassis is configured to operate in a -48 V dc environ- ment, the -48 V dc power is supplied through the PSAX 1250 Fan Tray power supply cabling. Three LED indicators on the faceplate provide status indications of the mod- ®...
  • Page 53: Cpu2 Module

    Chapter 2 Hardware Description Hardware Specifications with a reliable transport and access infrastructure. The Stratum 3–4 module is accurate to Stratum 3 requirements, allowing the PSAX 1250 system to run even after losing external synchronization, for as long as 24 hours without synchronization problems.
  • Page 54: System Environmental Specifications

    Chapter 2 Hardware Description Hardware Specifications Table 2-1. Chassis Hardware Specifications Specification Description Slot configuration 16 slots total—12 slots for 48.26-cm (19-in.) chassis: CPU modules and user-selected I/O and server modules 20 slots total—16 slots for 58.42-cm (23-in.) chassis: CPU modules and user-selected I/O and server modules 2 reserved slots for Stratum 3–4 Both chassis:...
  • Page 55: Ac Power Supply

    Chapter 2 Hardware Description Hardware Specifications The specifications for each module are described in the following sections. When preparing to install a chassis with redundant Power Supply modules, the modules normally operate in a load-sharing mode. This means that the maximum current required for the chassis is the maximum rated current specified for one Power Supply module, not the combined total for both modules.
  • Page 56: Dc Power Supply

    Chapter 2 Hardware Description Hardware Specifications -48 V dc Power The specifications for the PSAX 1250 -48 V dc Power Supply module are Supply found in Table 2-5. Table 2-5. -48 V dc Power Supply Module Specifications Specification Description Slot configuration Slot 23 or 24 or both (for redundant configuration) Input power -48 V dc...
  • Page 57: Cpu2 Module Specifications

    Chapter 2 Hardware Description Hardware Specifications CPU2 Module Specifications The specifications for the CPU2 module are given in Table 2-7. Table 2-7. CPU2 Module Specifications Specification Description Slot configuration Slots 11 and 12 (19-in.) or Slots 15 and 16 (23-in.) Dimensions 17.3 cm H x 2.4 cm W x 24.1 cm D (6.8 in.
  • Page 58: Performance And Power Specifications For The Psax Modules

    Chapter 2 Hardware Description Hardware Specifications Table 2-9. Performance and Power Specifications for the PSAX Modules Total Module Maximum Output Chassis Power Module Amount of Program and Input † Buffer Speed Consumption SDRAM Data Space Buffer DS1/T1 Interface Modules 6-Port DS1 IMA ( 16 MB 8 MB 1 MB...
  • Page 59 Chapter 2 Hardware Description Hardware Specifications Table 2-9. Performance and Power Specifications for the PSAX Modules (Continued) Total Module Maximum Output Chassis Power Module Amount of Program and Input † Buffer Speed Consumption SDRAM Data Space Buffer 2-Port E3 ATM ( 8 MB 3 MB 1 MB...
  • Page 60 Chapter 2 Hardware Description Hardware Specifications Table 2-9. Performance and Power Specifications for the PSAX Modules (Continued) Total Module Maximum Output Chassis Power Module Amount of Program and Input † Buffer Speed Consumption SDRAM Data Space Buffer 1-Port STM-1 8 MB 3 MB 2.5 MB 2.5 MB...
  • Page 61 Chapter 2 Hardware Description Hardware Specifications Table 2-9. Performance and Power Specifications for the PSAX Modules (Continued) Total Module Maximum Output Chassis Power Module Amount of Program and Input † Buffer Speed Consumption SDRAM Data Space Buffer Ethernet Interface Modules 4-Port Ethernet ( ENET 32 MB...
  • Page 62 Chapter 2 Hardware Description Hardware Specifications ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 2-16 255-700-247...
  • Page 63: System Features

    • An advanced queuing and cell-switching algorithm, provided by the AQue- Man (adaptive queue management) firmware algorithm, a patented tech- nology offered by Lucent Technologies to differentiate voice, video, and data requirements. The AQueMan algorithm maximizes bandwidth effi- ciency while ensuring QoS on a congested network.
  • Page 64: Interface Architecture

    Chapter 3 System Features Interface Architecture • A connection gateway application programming interface (API) that pro- vides an interface to the PSAX 1250 by which an external workstation (gateway) can control the PSAX 1250 ATM switching, using non-native ATM networking protocols Through the use of the API, the gateway and the PSAX 1250 can combine to perform powerful interworking among ATM, Integrated Services Digital Network (ISDN), Signaling System 7 (SS7), channel associated signaling...
  • Page 65: Connections Support

    Chapter 3 System Features Connections Support • Physical media access—The physical media access layer handles functions specific to each physical interface, connecting each user port to other users or network elements. • Service protocol translation—The service protocol translation process per- forms segmentation and reassembly (SAR) to adapt non-native ATM ser- vices to ATM-based services and back again.
  • Page 66: Spvc Reconnection Prioritization

    Chapter 3 System Features Connections Support 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.
  • Page 67: Sample Spvc Reconnection Prioritization Scheme

    Chapter 3 System Features Connections Support Table 3-1. Sample User-Defined Priority Scheme for Reconnecting SPVC ATM IMA Links User-Assigned Traffic Type Typical ATM Service Type Priority Code TDMA/CDMA control channels CBR-1 or VBR-express AMPS channel reserved for 911 CBR-2 emergency calls GSM control channels VBR-express Digital voice channels...
  • Page 68: Switched Virtual Circuit (Svc) Connections

    Chapter 3 System Features Connections Support • The maximum total number of AAL2 SPVC trunk connections in the chas- sis must not exceed 32. • The ATM uplink must be a 6-Port DS1 IMA module. • The PSAX with the priority system enabled will work with a PSAX with passive side SPVCs that has the priority system disabled.
  • Page 69: Svc Functional Description

    Chapter 3 System Features Connections Support SVC Functional SVC signaling, per ATM Forum UNI 3.0 and UNI 3.1, is selectable on a per- Description port basis. Call control is performed on the CPU module, including manage- ment of the call-state transitions for each of the calls. This process allows on- demand allocation of bandwidth and connection resources.
  • Page 70 Chapter 3 System Features Connections Support Both user-side and network-side interfaces undergo similar state transitions. Transition messages trigger these call-state changes as follows: Call States Description #0—Null No call exists. • User—The user has requested that the system #1—Call initiated establish an outgoing call on the network.
  • Page 71 Chapter 3 System Features Connections Support Call States Description • User—For incoming calls, when the user has been #10—Active awarded the call. For outgoing calls, when the user has received an indication that the remote user has answered the call. •...
  • Page 72: User Interfaces

    Chapter 3 System Features User Interfaces User Interfaces The PSAX 1250 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 con- nection, providing service to the end user that is indistinguishable from a real point-to-point, fixed-bandwith circuit.
  • Page 73: Dynamic Bandwidth Circuit Emulation Service

    Chapter 3 System Features User Interfaces 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.
  • Page 74: Hdlc Passthrough Bit Inversion

    Chapter 3 System Features User Interfaces With the PSAX 1250 system, service providers can also now concentrate the various ATM circuits onto an upstream interface to an ATM edge switch, typ- ically at the DS3 rate. With the DS3 interface, service providers can concen- trate various traffic types up to 45 Mbps.
  • Page 75: Pnni Features Supported By The Psax Systems

    Chapter 3 System Features User Interfaces 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 rout- ing, crankback and alternate routing of all call setup requests in case of con- nection setup failure.
  • Page 76: Pnni Topology State Element (Ptse) Information

    Chapter 3 System Features User Interfaces • 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 pack- ets (PTSPs) to advise and update their call routing information.
  • Page 77 Chapter 3 System Features User Interfaces 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).
  • Page 78: Atm Maintenance

    Chapter 3 System Features User Interfaces Grandparent Peer Group Logical Link Logical Group Node Highest Level Peer Group Peer Group Leaders Parent Peer Group PG (A) PG (B) Child Peer Groups PG(A.2) A.2.3 PG(B.1) PG(B.2) A.2.2 PG(A.1) PG(C) B.2.1 A.2.1 B.1.1 PG(A.4) B.2.2...
  • Page 79: Integrated Link Management Interface (Ilmi)

    Chapter 3 System Features User Interfaces • 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.
  • Page 80: Load Balancing For Iisp And Pnni

    Chapter 3 System Features User Interfaces Load Balancing for Load balancing allows communications trunks connecting access and edge IISP and PNNI switches to balance traffic between PNNI (dynamic source routing) and IISP (static hop-by-hop 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.
  • Page 81: Automatic Use Of Ima Links

    Chapter 3 System Features User Interfaces Inverse multiplexing for ATM (IMA) creates virtual access pipes that are faster than an E1 line, but not nearly as expensive as a T3/E3 line. This allows customers to gain ATM capabilities without the costs associated with broadband access.
  • Page 82: Frame Relay-To-Atm Interworking

    Chapter 3 System Features User Interfaces ~ 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.
  • Page 83 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 Nortel’s DMS switch. Operating on T1 circuits, the GR-303 digital loop carrier service has provi- sions for both an open interface network architecture and a digital loop car- rier system.
  • Page 84 PSAX Multiservice Media Gateway as Interworking Functions Using the GR-303 Standard Application Note, Issue 2, Release 7.1.0, Document No. 255-700-135. This document is available for the Lucent Customer Information Center at http://www.lucentdocs.com. In System Software Release 8.0.0, the following enhancements have been...
  • Page 85: Network Management

    Chapter 3 System Features Network Management Network Management The Multiservice Media Gateway system provides all the telecommunications management network (TMN) functions applicable to the system. The PSAX 1250 system (which contains network elements) can be managed in several ways using a network element management system or network man- agement system.
  • Page 86: Aqueview ® Element Management System

    Chapter 3 System Features Network Management • In-band management by using a PVC connection over an ATM wide-area network (WAN). The in-band management feature on the CPU module allows a user to access and manage one or more PSAX systems (managed targets) via a sin- gle PVC connection from a management workstation (management host) running an SNMP client over an ATM WAN.
  • Page 87: Multiservice Media Gateway Software Features

    Chapter 3 System Features Multiservice Media Gateway Software Features ® • Navis™ AQueView Element Management System User Guide for the Client/Server Application ® • Navis™ AQueView Element Management System User Guide for Standalone Sys- tems Multiservice Media Gateway Software Features Connection Gateway API Connection Gateway The Connection Gateway Application Programming Interface (CGAPI) pro-...
  • Page 88: The Psax 1250 As A Tcp Client/Server For The Connection Gateway Api

    Chapter 3 System Features Multiservice Media Gateway Software Features The PSAX 1250 As a If you are using the Connection Gateway API with your PSAX system, you TCP Client/Server for need to configure the system as either a TCP client device or a TCP server the Connection device.
  • Page 89: Ds1 Ani In-Line Codes For Loopbacks

    Chapter 3 System Features Multiservice Media Gateway Software Features DS1 ANI In-line Codes for Loopbacks The Channelized DS3 Multiservice and CES modules support activating and deactivating DS1 access network interface (ANI) in-line loopback codes embedded in the DS1 signal. These codes test transmissions between cus- tomer interface equipment and network interface equipment, for example, between PSAX central office (CO) products and customer premises equip- ment (CPE) products at the edge of an ATM network.
  • Page 90: Psax 1250 System Traffic Protection Capabilities

    Chapter 3 System Features Multiservice Media Gateway Software Features Transmit and monitor mode is exactly the same as transmit mode except that the DS0A module also reports to the CPU2 module a matching of the receive loop up and loop down codes. PSAX 1250 System Traffic Protection Capabilities APS/MSP Protection The 1+1 Automatic Protection Switching (APS)/Multiplex Section Protection...
  • Page 91: Alternate Rerouting Using Dual-Homed Pvcs

    Chapter 3 System Features Multiservice Media Gateway Software Features Figure 3-5 illustrates how a typical interface protection group configuration works. After the protection groups are created, they are displayed on the Pro- tection Group Table and the Interface Protection Table windows on the con- sole interface.
  • Page 92 Chapter 3 System Features Multiservice Media Gateway Software Features connections. DHPVCs for virtual paths can only be implemented on ATM-to- ATM connections. Alternate rerouting is a standard feature of the system software. The system sets up DHPVCs according to an industry-standard technique.
  • Page 93: Firmware Release Control

    Chapter 3 System Features Multiservice Media Gateway Software Features switch the PVCs to the standby link within one second, avoiding service interruptions under reasonably likely network congestion conditions. Figure 3-6 illustrates how the alternate rerouting is accomplished. ATM Network Link failure Interrupted Multiservice Multiservice...
  • Page 94: H.248 Media Gateway Access Protocol

    Chapter 3 System Features Multiservice Media Gateway Software Features H.248 Media Gateway Access Protocol The decomposed transit gateway architecture distributes the call control functionality and the media processing functionality over different network elements. The advantage gained by decomposition is to decentralize control from the SS7 network to local networks.
  • Page 95: Internet Protocol (Ip) Throttling

    Chapter 3 System Features Multiservice Media Gateway Software Features Cell encoding is executed by the CPU module on cell payload data destined for noisy interfaces. Based on a user-selected encoding rate for the connec- tion, source-data cell payloads are divided into six blocks and fed into a Reed Solomon encoder.
  • Page 96: Lanet Protocol

    Chapter 3 System Features Multiservice Media Gateway Software Features The IP Throttling feature, introduced in Release 7.1.0, limits the rate at which the CPU module accepts IP traffic (through the port or by the in- ETHERNET band management virtual port) to prevent the CPU module from being excessively burdened with traffic.
  • Page 97: The Relationship Between Lanet And The Osi Model

    Chapter 3 System Features Multiservice Media Gateway Software Features SERVICE-INDEPENDENT ARCHITECTURE Voice Video Images Data Layer 7 Layer 6 Layer 5 Layer 4 CELL-BY-CELL ENCRYPTION Layer 3 Layer 2 LANET Protocol Layer 1 Encryption Error Correction Bit Interleaf Satellite Radio Land Lines From bits per second to megabits per second Figure 3-7.
  • Page 98: Lanet Frame Structure

    Chapter 3 System Features Multiservice Media Gateway Software Features 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 set- ting up 526 addresses for each channel.
  • Page 99: Operations, Administration, And Maintenance (Oam)

    Chapter 3 System Features Multiservice Media Gateway Software Features Operations, Administration, and Maintenance (OAM) Overview of OAM The Operations, Administration, and Maintenance (OAM) feature, available on all PacketStar Multiservice Media Gateway 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.
  • Page 100: Oam Atm Layer Flows

    Chapter 3 System Features Multiservice Media Gateway Software Features Header Payload OAM Function Type Reserved Header 360 bits (45 bytes) Function-specific field Error Cell Detection Type Code Figure 3-9. OAM Cell Fields • Header: this is the same as the ATM cell header •...
  • Page 101: Oam F4 Flows

    Chapter 3 System Features Multiservice Media Gateway Software Features Figure 3-10. 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.
  • Page 102: Atm Layer Oam Functions

    Chapter 3 System Features Multiservice Media Gateway Software Features • 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.
  • Page 103: Packet Pipe Aal5-To-Aal2 Wireless Trunking For Mobile Voice

    This feature supports packet switched wireless backhaul networks for inter- connecting Lucent MSCs and Series II base stations using the Lucent propri- etary packet pipe protocol over land lines. This protocol performs encapsula- tion within ATM AAL2 for various cell site sizes.
  • Page 104: Trap Descriptions

    Chapter 3 System Features Multiservice Media Gateway Software Features Event handling processes within the PSAX system were improved so that the amount of time needed to set up an SVC connection for a call is reduced. Within the PSAX system, call setup time is now 30 msec or less. Trap Descriptions The PSAX system provides the capability to display SNMP trap messages on the console interface and on the AQueView Element Management System.
  • Page 105: Multiservice Media Gateway System-Supported Service Classes

    Chapter 3 System Features Multiservice Media Gateway Software Features Table 3-3 details the Multiservice Media Gateway system support of defined ATM quality of service (QoS) classes. Table 3-3. Multiservice Media Gateway System-Supported Service Classes ATM Service Class Description Constant Bit Rate (CBR) This service operates on a connection basis and offers consistent delay predictability.
  • Page 106: Class Of Service Descriptions

    Chapter 3 System Features Multiservice Media Gateway Software Features Table 3-4. Class of Service Descriptions Variable Bit Variable Bit Constant Bit Rate Real Rate Non-real Unspecified Bit Rate (CBR) Time Time (VBR- Rate (UBR) (VBR-RT) NRT) Service Private line Com- Frame relay, Raw cell, Examples...
  • Page 107: Mapping Atm Service Classes To Multiservice Media Gateway System Priority Levels

    Chapter 3 System Features Multiservice Media Gateway Software Features Table 3-6. Mapping ATM Service Classes to Multiservice Media Gateway System Priority Levels PVC Connection ATM Classes of Internal Configuration Service Examples Service Priority Selections Constant Bit CBR-1 CBR1 911 calls Rate (CBR) CBR-2 CBR2...
  • Page 108: Atm Traffic Management (Upc Support)

    Chapter 3 System Features Multiservice Media Gateway Software Features • Cell aging This capability prevents the lowest-priority data (for example, IP data) from being buffered in the Multiservice Media Gateway systems indefi- nitely. The AQueMan algorithm keeps track of how long each cell stays in the buffer.
  • Page 109: Cell Bus Traffic Shaping Happens On Egress To The Backplane

    Chapter 3 System Features Multiservice Media Gateway Software Features The Cell bus traffic shaping feature is a method for controlling the flow of data traffic. Specifically, it restricts the peak output rate of a module before the traffic reaches the backplane or midplane. It is implemented in firmware on modules that are offered with Cell bus traffic shaping variations: the OC- 3c MM/SM TS and the STM-1 MM/SM TS modules.
  • Page 110: Cell Bus Traffic Shaping Using The Input Cell-Selection Algorithm

    Chapter 3 System Features Multiservice Media Gateway Software Features Even though LAN switches usually maintain a sustained cell-transport rate of 40,000 cps, they allow LAN traffic to burst in violation of carrier traffic con- tracts, causing clusters of cells to exceed the MBS parameter. Because carriers monitor traffic at the edge of a network and enforce adherence to traffic con- tracts by discarding cells that exceed the MBS parameter, end users whose traffic violates their contractual MBS parameter experience high cell loss...
  • Page 111: Atm Traffic Shaping

    Chapter 3 System Features Multiservice Media Gateway Software Features the connection with the second longest queue, and continues on until the module buffer of the OC-3c TS or the STM-1 TS module reaches the mini- mum-capacity level. The algorithm processes traffic moving out of the input cell selection buffer according to the SCR of the particular VPC/VCC.
  • Page 112: Task Summary For Implementing Atm Traffic Shaping

    Chapter 3 System Features Multiservice Media Gateway Software Features Task Summary for To implement ATM Traffic Shaping, these configuration conditions must be Implementing ATM met: Traffic Shaping • The Traffic Shaping field must be enabled at the interface configuration level. This action ATM traffic-shapes ingress traffic to an ATM port. After this is done, the module(s) used for this feature are ATM Traffic-Shaping enabled.
  • Page 113: Maximum Number Of Atm Traffic-Shaped Connections

    Chapter 3 System Features Multiservice Media Gateway Software Features Maximum Number of Each OC-3c 1+1 APS and STM-1 1+1 MSP module supports 2,046 traffic- ATM 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.
  • Page 114: Formula For Determining The Pcr Of An Atm Traffic-Shaped Connection

    Chapter 3 System Features Multiservice Media Gateway Software Features 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.
  • Page 115: V5.2 European Idlc

    Chapter 3 System Features Multiservice Media Gateway Software Features PCR = the PCR of the ATM traffic-shaped connection SCR = the SCR of the ATM traffic-shaped connection F is a function of the summation of the PCRs of constant bit rate connec- tions plus the SCRs of the variable bit rate (real time) connections divided by the interface data rate.
  • Page 116: Voice Processing

    AAL2 Wireless Trunking feature addresses this need. This feature supports packet switched wireless backhaul networks for inter- connecting Lucent MSCs and Series II base stations using the Lucent propri- etary packet pipe protocol over land lines. This protocol performs encapsula- tion within ATM AAL2 for various cell site sizes.
  • Page 117: Virtual Routing

    Chapter 3 System Features Multiservice Media Gateway Software Features Figure 3-15 shows the application implemented on a VBR-to-ATM connec- tion over the HDLC interface with SAR type AAL2 standard. The SAR type AAL5-to-AAL2 conversion is done on the DSP2E/F Voice Server module. The SAR type AAL1-to-AAL2 is done on the DSP2D module.
  • Page 118: Traffic Flow Description

    Chapter 3 System Features Multiservice Media Gateway Software Features • Service quality through the use of ATM service level mapping Enterprise/Service Provider Ingress IP Egress IP Traffic Traffic Route Server Module Ingress ATM Egress ATM Traffic Traffic ATM Network Figure 3-16. Traffic Flow Description The "virtual router"...
  • Page 119: Psax Module Features

    Chapter 3 System Features PSAX Module Features The Route Server module supports IP over ATM virtual routing in conjunc- tion with the other Multiservice Media Gateway I/O modules. You can con- figure a virtual router at the Route Server module to communicate with the management router at the CPU module.
  • Page 120 Chapter 3 System Features PSAX Module Features ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 3-58 255-700-247...
  • Page 121: Site-Specific Configuration

    Site-Specific Configuration Overview of This Chapter This chapter describes how to: • Log on and off the PSAX system • Configure the basic site-specific parameters of your PSAX 1250 system • Configure call resources • Enable/disable system-wide features • Reboot PSAX system CPUs •...
  • Page 122: Psax 1250 Multiservice Media Gateway System Logon Window

    Chapter 4 Site-Specific Configuration Logging onto the System The PSAX 1250 Logon window is displayed (see Figure 4-1). 3 Enter the values for the fields on this window according to the informa- tion provided in Table 4-1. The Console Interface Main Menu window is displayed (see Figure 4-2). At the time of initial configuration, the Console Interface Main Menu win- dow displays a field with a pair of opposing square brackets in the upper right corner.
  • Page 123: Console Interface Main Menu Window

    Chapter 4 Site-Specific Configuration Logging onto the System Figure 4-2. Console Interface Main Menu Window Table 4-1. Field Descriptions for the Logon Window Field Names Field Values Description Username Default: blank field Provides two levels of access to the PSAX system. Note: You cannot create your own username;...
  • Page 124: Changing The System Password And Other User Options

    Chapter 4 Site-Specific Configuration Changing the System Password and Other User Options Changing the System Password and Other User Options When initially configuring the system, you can log in with configuration access or read-only access. Usernames cannot be changed. However, you should change the default passwords and the default SNMP community string name to ones of your choosing.
  • Page 125: User Options Window

    Chapter 4 Site-Specific Configuration Changing the System Password and Other User Options Note: You must reboot your PSAX system for these changes to take effect. For information on rebooting system components, see Chapter 5, “Using System Diagnostics.” Figure 4-3. User Options Window Command Function Change Password for...
  • Page 126: Field Descriptions For The User Options Window

    Chapter 4 Site-Specific Configuration Changing the System Password and Other User Options Table 4-2. Field Descriptions for the User Options Window Field Names Field Values Description Alternate Default: Up: K If you want to use keyboard short-cuts instead of Navigation Keys Down: J the cursor positioning (arrow) keys for navigating Up, Down, Left,...
  • Page 127 Chapter 4 Site-Specific Configuration Changing the System Password and Other User Options Table 4-2. Field Descriptions for the User Options Window Field Names Field Values Description Timeout Length Default: 10 minutes The setting in this field determines the period of Next SNMP read- time that the session will remain active after the Range: N/A...
  • Page 128: Console Interface Main Menu Options

    Chapter 4 Site-Specific Configuration Console Interface Main Menu Options Console Interface Main Menu Options The Console Interface Main Menu window includes the following options as shown in Table 4-3: Table 4-3. Console Interface Main Menu Options For information on using this see...
  • Page 129: Configuring The System For Your Site

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Table 4-4. Site-Specific Options Documented in the PSAX Multiservice Media Gateways Product Information Library To use this menu option... see this document... ® ATM Trunking Configuration Any PacketStar PSAX User Guide for Multiservice Media Gateways, Release 8.0.0, Issue 1 DSP Resource Configuration...
  • Page 130: Accessing The Site-Specific Menu

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Accessing the Site-Specific Menu To access the Site-Specific Menu window on which you select the option for the function or feature you want to configure, perform the steps in the fol- lowing procedure.
  • Page 131 Chapter 4 Site-Specific Configuration Configuring the System for Your Site Menu Option Description Site-Specific Configuration Accesses the Site-Specific Configuration window on which you configure informa- tion that is unique to this particular PSAX system, including the site ID, Ethernet IP address, system date and time, and SNMP manager IP addresses.
  • Page 132 Chapter 4 Site-Specific Configuration Configuring the System for Your Site Menu Option Description TAS Module System-wide Accesses the TAS Module System-wide Configuration Configuration Menu window on which you perform actions on announcement files on the Tones and Announcements Server module such as compression, play- ing, FTP, and line tests.
  • Page 133: Configuring System Identification Information

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Menu Option Description Trap Activation Accesses the Trap Activation Table win- Configuration dow on which you turn on or off the dis- play of specific minor, information, and system response indicators in the trap log. N to M Protection Feature Access the N to M Protection Feature Menu window on which you add protec-...
  • Page 134: Site-Specific Configuration Window

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Figure 4-5. Site-Specific Configuration Window The commands on this window have the following functions: Command Function Configure TCP Server Displays the TCP Server Configuration window. Apply Site-Specific Applies the values you enter on this win- Configuration dow.
  • Page 135: Rules For Configuring Ip Addresses

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Table 4-5. Field Descriptions for Master ATM Address and OAM Related Data Panel Field Name Field Values Description Master Node Addr Default: 0000.0000. Indicates the master node address where the 0000.0000.0000.
  • Page 136: Rules For Configuring Ip Address Masks

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site 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 CPU2 mod- ule is corrupted, the system cannot access the Ethernet.
  • Page 137: Field Descriptions For Master Atm Address And Oam Related Data Panel On The Site-Specific Configuration Window

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Table 4-6. Field Descriptions for 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. Indicates the master node address where the 0000.0000.0000.
  • Page 138: Field Descriptions For The System Identification Panel Of The Site-Specific Configuration

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Table 4-7. Field Descriptions for the System Identification Panel of the Site-Specific Configuration Window Field Name Field Values Description [Chassis Type] Default: N/A Displays the type of PSAX system you are config- display only uring.
  • Page 139: Configuring System Date And Time

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Table 4-7. Field Descriptions for the System Identification Panel of the Site-Specific Configuration Window Field Name Field Values Description IP Mask Default: Specifies the IP mask for Ethernet access to your (display only) 000.000.000.000 PSAX system.
  • Page 140: Configuring The Psax System As A Tcp Server Or A Tcp Client

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Table 4-8. Field Descriptions for the System Date and Time Panel on the Site-Specific Configuration Window Field Name Field Values Description Mon/Day/Yr Default: today’s date Specifies the current date in month (mm), day (dd), and year (yyyy).
  • Page 141: Tcp Server Configuration Window (Psax System As A Tcp Client)

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site To configure the PSAX 1250 system as a TCP client or server, perform the steps in the following procedure. Begin 1 In the Site-Specific Configuration window, select the Configure TCP Server command.
  • Page 142: Tcp Server Configuration Window (Psax System As A Tcp Server)

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Figure 4-7. TCP Server Configuration Window (PSAX System as a TCP Server) The commands on this window have the following functions: Command Function Apply TCP Server Configu- Applies the configuration. ration Reset TCP Server Display Resets the display.
  • Page 143: Configuring Snmp Trap Destinations

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site Table 4-9. Field Descriptions for the TCP Server Configuration Window Field Name Field Values Description Server IP Address Default: 0000.0000. Specifies the IP address of the server, such as the 0000.0000 call controller.
  • Page 144: Field Descriptions For The Snmp Trap Destinations Panel

    Chapter 4 Site-Specific Configuration Configuring the System for Your Site 3 Select the Apply Site-Specific Configuration command. After you apply (save) the values on this window, the system does the following: • Saves the values you entered to the PSAX system database •...
  • Page 145: Configuring Call Control Resource Allocation

    IP address of the interface you use to connect the PSAX system to the IP network. If you have a complicated network configuration, as described in the description for the value Ethernet, Lucent recommends that you select Ethernet. Ethernet Specifies that the source of PSAX trap messages is the IP address you entered in the Switch IP Addr.
  • Page 146: Site-Specific Menu Window

    Chapter 4 Site-Specific Configuration Configuring Call Control Resource Allocation The Site-Specific Menu window is displayed (see Figure 4-8). 2 Select the Call Control Resource Allocation Configuration option. The Call Control Resource Allocation Configuration window is displayed (see Figure 4-9). 3 Enter values in the fields on this window according to the guidelines pro- vided in the section, “Configuration Guidelines,”...
  • Page 147: Call Control Resource Allocation Configuration Window

    Chapter 4 Site-Specific Configuration Configuring Call Control Resource Allocation Figure 4-9. Call Control Resource Allocation Configuration Window The commands on this window have the following functions: Command Function Apply Configuration Applies the values you entered on this window. Go Back to Site-Specific Redisplays the Site-Specific Menu win- Menu dow.
  • Page 148: Field Descriptions For The Call Control Resource Allocation Configuration Window

    Chapter 4 Site-Specific Configuration Configuring Call Control Resource Allocation • When changing the values in these fields to suit your needs, 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.
  • Page 149: Field Descriptions For The Call Control Resource Allocation Configuration Window

    Chapter 4 Site-Specific Configuration Configuring Call Control Resource Allocation Table 4-11. Field Descriptions for the Call Control Resource Allocation Configuration Window (Continued) Field Name Field Values Description spvcTePtToPtCalls Default: 000100 Specifies the maximum number of SPVC terminal emulation point-to-point calls to be supported by the Range: 0–10000 PSAX system.
  • Page 150 Chapter 4 Site-Specific Configuration Configuring Call Control Resource Allocation Table 4-11. Field Descriptions for the Call Control Resource Allocation Configuration Window (Continued) Field Name Field Values Description sgApiPtToPtSvc Default: 000000 Specifies the Connection Gateway API Applications: Calls maximum number of SVC point-to-point calls for the Range: Connection Gateway API to be supported by the PSAX Format:...
  • Page 151: Saving The Configuration And Rebooting The System

    Chapter 4 Site-Specific Configuration Configuring Call Control Resource Allocation The maximum number of calls (connections) for PVCs, SPVCs, and SVCs you can set up for a PSAX system are provided in Table 4-12. Table 4-12. PSAX System Performance Capabilities Per Node for Release 8.0.0 Maximum Number of Calls per Node Connection Type with CPU2 and CPU3L Modules...
  • Page 152: Diagnostics Menu

    Chapter 4 Site-Specific Configuration Configuring Call Control Resource Allocation The configuration values you entered in the procedure are now in effect. Figure 4-10. Diagnostics Menu Figure 4-11. Remote Reboot Configuration Window ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 4-32 255-700-247...
  • Page 153: Backing Up Configuration Data

    Gateway User Guide, Document Number 255-700-135. This user guide also includes a list of modules certified as interoperable with other call processing ™ devices, such as the Lucent CellPipe IAD and the CO 5ESS switch. Configuring TAS Module System-Wide Use See the Tones and Announcements Module User Guide for instructions on config- uring system-wide use of the TAS module.
  • Page 154 Chapter 4 Site-Specific Configuration Enabling and Disabling System-Wide Features Begin 1 On the Console Interface Main Menu window, select the Site-Specific Configuration option. The Site-Specific Menu window (Figure 4-12) is displayed. 2 On the Site-Specific Menu window, select the Feature Turn On/Off option.
  • Page 155: Feature Turn On/Off Window

    Chapter 4 Site-Specific Configuration Enabling and Disabling System-Wide Features Figure 4-12. Site-Specific Menu Window (Feature Turn On/Off Option Selected) Figure 4-13. Feature Turn On/Off Window The commands on this window have the following functions: ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 255-700-247 4-35...
  • Page 156: Field Descriptions For The Feature Turn On/Off Table

    Chapter 4 Site-Specific Configuration Enabling and Disabling System-Wide Features Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Displays entries at the top of the table. Bottom Displays entries at the bottom of the table. Find .
  • Page 157: Rebooting Redundant Or Non-Redundant Psax System Cpus

    Chapter 4 Site-Specific Configuration Rebooting Redundant or Non-Redundant PSAX System CPUs Table 4-13. Field Descriptions for the Feature Turn On/Off Table Field Name Field Values Description desired status Default: Enable or Specifies whether the feature is to be made oper- (display only) Disable (depend- ational or not.
  • Page 158: Console Interface Main Menu Window (Save Configuration Option Selected)

    Chapter 4 Site-Specific Configuration Rebooting Redundant or Non-Redundant PSAX System CPUs Figure 4-14. 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 CPU modules, this command causes the backup (standby) CPU module to reboot.
  • Page 159: Remote Reboot Configuration Window (Primary Switchover Option Selected)

    Chapter 4 Site-Specific Configuration Rebooting Redundant or Non-Redundant PSAX System CPUs 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 Compo- nents option.
  • Page 160 Chapter 4 Site-Specific Configuration Rebooting Redundant or Non-Redundant PSAX System CPUs module (originally the primary CPU). The green LED ACTIVE is illumi- nated on the primary CPU module. Rebooting the The following procedure applies typically to all nonredundant PSAX systems. Nonredundant PSAX System Begin...
  • Page 161: Configuring Interface Protection Groups

    Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups Figure 4-16. Remote Reboot Configuration Window (Reboot Primary CPU Option Selected) Configuring Interface Protection Groups The Interface Protection Group feature enables you to configure an interface protection group as primary and secondary, with the secondary group serv- ing as a standby in the event the primary ATM link fails.
  • Page 162: Interface Protection Feature Configuration Window

    Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups The Interface Protection Feature Configuration window is displayed (see Figure 4-17). 2 Select the Protection Group Table option. The Protection Group Table window is displayed (see Figure 4-18). 3 Select the Add a Protection Group command. The Protection Group Configuration window is displayed (Figure 4-19).
  • Page 163: Protection Group Table Window

    Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups Figure 4-18. Protection Group Table Window The commands on this window have the following functions. Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Displays entries at the top of the table. Bottom Displays entries at the bottom of the table.
  • Page 164: Protection Group Configuration Window

    Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups Figure 4-19. Protection Group Configuration Window The commands on this window have the following functions. Command Function Add to Protection Group Creates a new protection group ID and applies the values in the fields. Delete from Protection Deletes the protection group ID and redis- Group and Return...
  • Page 165 Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups Table 4-14. Field Descriptions for the Protection Group Configuration Window Field Names Field Values Description Switchover Method Default: Auto Specifies the method used to switch traffic from a failed primary interface to an available standby Range: N/A interface.
  • Page 166: Creating An Interface Protection Group

    Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups 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 4-20). 2 Select the Add a Protection Group command. The Interface Protection Configuration window is displayed (Figure 4-21).
  • Page 167: Interface Protection Configuration Window

    Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Displays entries at the top of the table. Bottom Displays entries at the bottom of the table. Total:0/0 The first number in this field indicates the number of the table entry on the first line of the currently displayed window.
  • Page 168: Field Descriptions For The Interface Protection Configuration Window

    Chapter 4 Site-Specific Configuration Configuring Interface Protection Groups Command Function Add to Interface Protection Adds an interface to an interface protec- Group tion group. Delete from Interface Deletes an interface from an interface pro- Protection and Return tection group. Interface Switchover Initiates a manual switchover from the failed primary interface to the standby interface.
  • Page 169: Internet Protocol (Ip) Throttling

    Chapter 4 Site-Specific Configuration Internet Protocol (IP) Throttling Table 4-15. Field Descriptions for the Interface Protection Configuration Window Field Names Field Values Description Select Standby Default: 0 Specifies the standby interface logical number on Number which to switch traffic. You can use this field only Range: when you select the value Manual in the Format: numeric...
  • Page 170: The Ip Throttling Window (Disabled)

    Chapter 4 Site-Specific Configuration Internet Protocol (IP) Throttling Figure 4-22. Site-Specific Menu (IP Throttling Configuration Option Selected) Figure 4-23. The IP Throttling Window (Disabled) ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 4-50 255-700-247...
  • Page 171: The Ip Throttling Window (Enabled)

    Chapter 4 Site-Specific Configuration Internet Protocol (IP) Throttling Figure 4-24. The IP Throttling Window (Enabled) The commands on this window have the following functions: Command Function Apply Configuration Sets the values you select on this window. Continuous Update Continuously updates all fields once every second.
  • Page 172: Field Descriptions For The Ip Throttling Configuration Window

    Chapter 4 Site-Specific Configuration Internet Protocol (IP) Throttling Table 4-16. 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 desig- nated throughput in the Allowed Rate field.
  • Page 173 Chapter 4 Site-Specific Configuration Internet Protocol (IP) Throttling Table 4-16. Field Descriptions for the IP Throttling Configuration Window Field Name Field Values Description Allowed Rate Default: 2000 fps Specifies the maximum bandwidth allowed to pass through the or in-band manage- ETHERNET Range: 100–2000 fps ment virtual port into the PSAX system in the...
  • Page 174: Snmp Trap Activation/Deactivation

    Chapter 4 Site-Specific Configuration SNMP Trap Activation/Deactivation Table 4-16. Field Descriptions for the IP Throttling Configuration Window Field Name Field Values Description Leaky Bucket Size Default: 32 The virtual buffer that serves as a counter that monitors the rate of ingress traffic to the CPU Range: 1–20000 module.
  • Page 175: Enabling And Disabling Snmp Trap Messages

    Chapter 4 Site-Specific Configuration SNMP Trap Activation/Deactivation • Major (Users cannot deactivate this category.) • Critical (Users cannot deactivate this category.) Traps for all critical and major indicators that detect system-level component problems cannot be turned off, so users will always be notified when a prob- lem affects the entire PSAX system.
  • Page 176: Trap Activation Table

    Chapter 4 Site-Specific Configuration SNMP Trap Activation/Deactivation Figure 4-25. Trap Activation Table Command Function PgUp Displays the previous page in the list of trap names. PgDown Displays the next subsequent page in the list of trap names. Displays the beginning page in the list of trap names.
  • Page 177: Using The Equipment Configuration Window

    Chapter 4 Site-Specific Configuration Using the Equipment Configuration Window Table 4-17. Field Descriptions for the Trap Activation Table Window Field Name Field Values Description Total: Default: 1/xxx, The first number in this field indicates the num- (display only) ber of the trap table entry on the selected line of where xxx indicates a the currently displayed window.
  • Page 178: Sample Equipment Configuration Window On A Psax 1250 System

    Chapter 4 Site-Specific Configuration Using the Equipment Configuration Window 2 View the module status, software version, PEC, and serial number data. 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.
  • Page 179: Sample Equipment Configuration Window On A Psax 1250 System (Page 2)

    Chapter 4 Site-Specific Configuration Using the Equipment Configuration Window Figure 4-27. Sample Equipment Configuration Window on a PSAX 1250 System (Page 2) Commands The commands on this window have the following functions. Command Function Update Equipment Display Refreshes the current status of the mod- ules in the PSAX chassis Page Down Displays the second page of the Equip-...
  • Page 180: Field Descriptions For The Equipment Configuration Window

    Chapter 4 Site-Specific Configuration Using the Equipment Configuration Window Table 4-18. Field Descriptions for the Equipment Configuration Window Field Name Field Values Description Slot Default: N/A Indicates the slot number in the PSAX chassis. Range: 1–25, depend- ing on chassis type Format: Numeric Card Type Default: N/A...
  • Page 181 Chapter 4 Site-Specific Configuration Using the Equipment Configuration Window Table 4-18. Field Descriptions for the Equipment Configuration Window (Continued) Field Name Field Values Description SW Version Default: N/A Displays the version of PSAX system software with which the modules’ firmware was released. Range: (from module The software version is encoded in the module firmware)
  • Page 182: Configuring The Stratum 3-4 Module

    Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module Table 4-19. Alarm Status Descriptions for Modules on the Equipment Configuration Window Module Type Number Alarm Status Description Affected NoAlarm NoAlarm indicates that the module is inserted in the chassis slot and not config- ured.
  • Page 183: Stratum Configuration Window (Freerun)

    Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module To configure the Stratum 3–4 module synchronization source, clock accu- racy, and clock failure backup reference, perform the following procedure. Begin 1 On the Console Interface Main Menu window, select the Equipment Configuration command.
  • Page 184: Stratum Configuration Window (Linetiming Synchronization)

    Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module Figure 4-29. Stratum Configuration Window (LineTiming Synchronization) The commands in the Stratum Configuration window have the following functions: 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.
  • Page 185: Field Descriptions For The Stratum Configuration Window

    Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module Table 4-20. Field Descriptions for the Stratum Configuration Window Field Name Mode of Operation Description [Primary Stratum Default: Holdover Indicates the current mode of operation for the pri- Mode] mary Stratum 3–4 module. Range: N/A (display only) Format: Predefined...
  • Page 186 Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module Table 4-20. Field Descriptions for the Stratum Configuration Window (Continued) Field Name Mode of Operation Description [Line Timing Sta- Default: None Indicates the current line timing status for the tus] module. Range: N/A (display only) Format: Predefined...
  • Page 187 Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module Table 4-20. Field Descriptions for the Stratum Configuration Window (Continued) Field Name Mode of Operation Description [Backup Stratum Default: Unconfig- Indicates the status of the input T1BITS or E1ETSI T1/E1 Port Status] ured clock source connected to the external clock con- (display only)
  • Page 188 Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module Table 4-20. Field Descriptions for the Stratum Configuration Window (Continued) Field Name Mode of Operation Description Synchronization Default: LineTiming Indicates the synchronization source to be used by Source the chassis and specified I/O modules. The I/O Range: NA modules use this source when LocalTiming is Format: Alphabetical...
  • Page 189: Switching The Line Timing Source

    Chapter 4 Site-Specific Configuration Configuring the Stratum 3–4 Module Table 4-20. Field Descriptions for the Stratum Configuration Window (Continued) Field Name Mode of Operation Description Secondary Line Default: Slot: 00 Port: Specifies the secondary line source when LineTim- Source ing is selected in the Synchronization Source field. Enter the values for the slot and the port of the Range: Chassis/mod- desired I/O module port that is providing line tim-...
  • Page 190: Saving The Equipment Configuration Values And Logging Off

    Chapter 4 Site-Specific Configuration Saving the Equipment Configuration Values and Logging Off I/O and server modules display the status value of Primary if they are con- figured, or Unknown if they are unconfigured. The Alarm Status column for unconfigured modules still can have a number listing the ports that are avail- able to be configured.
  • Page 191 Chapter 4 Site-Specific Configuration Saving the Equipment Configuration Values and Logging Off On the Console Interface Main Menu window, [Modified] is displayed next to the Save Configuration command, indicating you have made changes to your system that are not yet saved to the database. 2 Select the Save Configuration command.
  • Page 192 Chapter 4 Site-Specific Configuration Saving the Equipment Configuration Values and Logging Off ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 4-72 255-700-247...
  • Page 193: Configuring Pnni

    Configuring PNNI PNNI System-Wide Configuration For an overview of PNNI and the PNNI features supported on the PSAX 1250 system, see Chapter 3. To configure a PNNI node for your PSAX 1250 system, perform the steps in the following procedure. Note: Before you can configure an I/O module with the ATM PNNI 1.0 interface, you must configure PNNI for your PSAX 1250 system.
  • Page 194: Pnni System-Wide Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration you need to take the node out of service, you must first delete any ATM PNNI interfaces you have configured on your PSAX 1250 sys- tem. 8 Select the Go Back to Previous Screen command (or press Ctrl+B). The PNNI Node Table (see Figure 5-2) is displayed, showing your current node index, node level, and operating status.
  • Page 195 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Menu Option Name Function PNNI Summary Address Displays ATM NSAP addresses for all Configuration nodes to which this link table is attached by PNNI interfaces. PNNI Map Link Informa- Displays the mapping for the nodes and tion their links, and all original port and remote port PNNI topology state element...
  • Page 196: Pnni Node Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-2. PNNI Node Table Window The commands on this window have the following functions: Command Function Page Up Scroll up one page. Page Down Scrolls down one page. Displays entries at the top of the table. Bottom Displays entries at the bottom of the table.
  • Page 197: Pnni Node Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Field Description • Total: 0/0 Displays the first number in this field indi- cates the identification number of the con- nection table entry on the first line of the cur- rently displayed window. The second number indicates the total number of connection table entries for this connection type.
  • Page 198: Field Descriptions For The Pnni Node Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Create Node Entry Create a new PNNI node. Delete Node Entry Delete an existing PNNI node. Bring Node Into Brings an existing PNNI node into or out of service. Service PNNI Node Pgl Displays the PNNI Node Pgl (Peer Group Leader) Table Configuration window.
  • Page 199: Field Descriptions For The Pnni Node Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-1. Field Descriptions for the PNNI Node Configuration Window Field Name Field Values Description Domain Name Default: N/A Indicates the routing domain in which this node participates. Range: N/A Format: alphanumeric Node Level Default: 096 Indicates the level of PNNI hierarchy at which this node exists.
  • Page 200 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-1. Field Descriptions for the PNNI Node Configuration Window Field Name Field Values Description [DB Overload] Default: True Displays whether Database Overload is selected, (display only) which specifies whether the node is currently Range: N/A operating in a topology database overload state.
  • Page 201: Modifying Pnni Configurations

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Modifying PNNI Configurations To modify a PNNI node configuration, do one of the following as shown in Table 5-2. Table 5-2. Steps to Modify a Configured PNNI Node To modify this type of PNNI do this...
  • Page 202: Pnni Node Pgl Configuration

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration A trap message will confirm the configuration at the bottom of the win- dow. 4 Select Go Back to Previous Screen or press Ctrl+B to return to the PNNI Node Configuration window to configure other field values. Figure 5-4.
  • Page 203 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-3. Field Descriptions for the PNNI Node PGL Configuration Window Field Name Field Values Description [Node Index] Default: 0 Displays the node index that identifies a logical (display only) PNNI entity in the PSAX system. Enter the index Range: 1–400 number of each node in this field.
  • Page 204 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-3. Field Descriptions for the PNNI Node PGL Configuration Window Field Name Field Values Description [State] Default: OperPgl Displays the status of this node PGL. (display only) Range: N/A Format: predefined OperPgl Displays that the status of this node is the PGL.
  • Page 205: Configuring The Pnni Node Timer

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-3. Field Descriptions for the PNNI Node PGL Configuration Window Field Name Field Values Description [Preferred Pgl] Default: 0 Displays the preferred PGL. To select, any node (display only) compares the leadership priorities and node IDs Range: N/A advertised in the PTSEs in the topology database, Format: Hexadecimal...
  • Page 206: Pnni Node Timer Configuration

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-5. PNNI Node Timer Configuration The commands on this window perform the following functions: Command Function Apply Configuration Applies the values you set on this win- dow. Go Back to Previous Screen Redisplays the PNNI Node Configuration window.
  • Page 207 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-4. Field Descriptions for the PNNI Node Timer Configuration Window Field Name Field Values Description Node Timer Information Panel [Node Index] Default: 00000 Displays the node index that identifies a logical (display only) PNNI entity in the PSAX system.
  • Page 208: Configuring The Pnni Node Svcc

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-4. Field Descriptions for the PNNI Node Timer Configuration Window Field Name Field Values Description Rxmt Interval..(sec) Default: 00005 Specifies the retransmit interval, which is the period between retransmissions of unacknowl- Range: 0–65535 edged database summary packets, PTSE request Format: numeric packets, and PNNI Topology State Packets...
  • Page 209: Pnni Node Svcc Configuration

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration 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.
  • Page 210: Configuring The Pnni Node Scope Mapping

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-5. Field Descriptions for the PNNI Node SVCC Configuration Window Field Name Field Values Description [Node Index] Default: 0 Displays the node index that identifies a logical (display only) PNNI entity in the PSAX system. Range: 1–400 Format: numeric Init Time...
  • Page 211: Pnni Scope Mapping Configuration

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration 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.
  • Page 212: Field Descriptions For The Pnni Scope Mapping Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-6. Field Descriptions for the PNNI Scope Mapping Configuration Window Field Name Field Values Description [Node Index] Default: 00000 Displays the node index that identifies a logical (display only) PNNI entity in the PSAX system. Range: 1–400 Format: numeric Local Network...
  • Page 213: Configuring The Pnni Route Addresses

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-6. Field Descriptions for the PNNI Scope Mapping Configuration Window Field Name Field Values Description Community Plus Default: 48 Indicates the highest level of PNNI hierarchy (or the smallest PNNI routing level) that lies within Range: 0–104 (display only) the Community Plus One organizational scope.
  • Page 214: Pnni Route Address Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration 6 To add additional route addresses, repeat this procedure. Figure 5-8. PNNI Route Address Table Window The commands in this window have the following functions: Command Function Find.. Searches this table by the values you enter in the Node Index, Prefix Length, Address Index, and Route Address fields.
  • Page 215: Pnni Route Address Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-9. PNNI Route Address Configuration Window The commands in this window have the following functions: 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.
  • Page 216: Field Descriptions For The Pnni Route Address Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-7. Field Descriptions for the PNNI Route Address Configuration Window Field Name Field Values Description Route Address Information Panel Node Index Default: 000000 Displays the node index that identifies a logical PNNI entity in the PSAX system. Enter the same Range: 1–400 value as assigned to the PNNI node.
  • Page 217 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-7. Field Descriptions for the PNNI Route Address Configuration Window Field Name Field Values Description Address Type Default: Exterior Indicates the type of domain address. Range: N/A Format: Predefined Exterior Indicates a connection from the advertising node to the address prefix that belongs to an external domain address.
  • Page 218: Configuring Pnni Metrics

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-7. Field Descriptions for the PNNI Route Address Configuration Window Field Name Field Values Description [Address Proto] Default: Mgmt Displays the protocol by which connectivity from (display only) the advertising node to the address prefix was Range: N/A learned.
  • Page 219: Pnni Metrics Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration 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 Met- rics Table.
  • Page 220: Pnni Metrics Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Find.. Searches this table by the values you enter in the Node Index, Metrics Direction, Metrics Tag, or Metrics Index fields. Add Metrics Entry Displays the PNNI Metrics Configuration window. Go Back to Previous Screen Redisplays the PNNI Route Address Con- figuration window.
  • Page 221: Field Descriptions For The Pnni Metrics Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-8. Field Descriptions for the PNNI Metrics Configuration Window Field Name Field Values Description Metrics Information Panel Node Index Default: 000000 Displays the node index that identifies a logical PNNI entity in the PSAX system. Range: 1–400 Format: numeric Metrics Tag...
  • Page 222 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-8. Field Descriptions for the PNNI Metrics Configuration Window Field Name Field Values Description Max Cell Rate Default: Indicates the maximum cell rate, in hexadecimal 0xFFFFFFFF notation, for directions and specific service cate- gories (see the descriptions for the fields Metrics Range: N/A Direction and Metrics Classes.
  • Page 223: Configuring Pnni Route Tns

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Configuring PNNI Route TNS Begin 1 From 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 5-12). 2 Select the Add Route TNS Entry command (or press Ctrl+A).
  • Page 224: Field Descriptions For The Pnni Route Tns Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Displays entries at the top of the table. Bottom Displays entries at the bottom of the table. Total: 0/0 The first number in this field indicates the identification number of the table entry on the first line of the currently displayed...
  • Page 225: Pnni Route Tns Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-9. Field Descriptions for the PNNI Route TNS Table Window Field Name Description TNS Plan Displays the Transit Network String Plan. Indi- cates the network ID plan of a specified transit network. TNS Id Displays the Transit Network String Identifier.
  • Page 226: Field Descriptions For The Pnni Route Tns Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-10. Field Descriptions for the PNNI Route TNS Configuration Window Field Name Field Values Description Route TNS Information Panel PNNI Node Index Default: 0 Displays the node index identifies a logical PNNI entity in the PSAX system.
  • Page 227 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-10. Field Descriptions for the PNNI Route TNS Configuration Window Field Name Field Values Description Route Type Default: Exterior The route type being used. Range: N/A Format: predefined Other A user-defined route type. Exterior A connection from the advertising node to the address prefix that belongs to an external domain...
  • Page 228: Viewing Pnni Map Tns Information

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-10. Field Descriptions for the PNNI Route TNS Configuration Window Field Name Field Values Description [TNS Proto] Default: Mgmt Displays the local interface over which the adver- (display only) tised node is reachable. Range: N/A Format: predefined Mgmt...
  • Page 229: Pnni Map Tns Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Begin 1 From the PNNI System-Wide Configuration window, select the PNNI Map TNS Information command (or press Ctrl+P). Figure 5-14. PNNI Map TNS Table The commands on this window perform the following functions: Command Function Page Up...
  • Page 230: Field Descriptions For The Pnni Map Tns Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function View Map TNS Configura- Displays the PNNI Map TNS Configuration tion window. Go Back to Previous Screen Redisplays the PNNI System-Wide config- uration window. The fields on this window are explained in Table 5-7: Table 5-11.
  • Page 231: Pnni Route Tns Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-15. PNNI Route TNS Table Window The PNNI Map TNS Configuration window lists information on six parame- ters of the selected node address on the Map TNS Table. The table is read- only, as reachable addresses are discovered during dynamic operation of the PNNI protocol, not manually configured.
  • Page 232: Configuring Summary Addresses

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-12. Field Descriptions for the PNNI Map TNS Configuration Window Field Name Field Values Description [Adv Port Id] Default: 0 Displays the 10-digit port identifer of the node (display only) advertising to reach the given transit network (see Annex H, af-pnni-0055.000).
  • Page 233: Pnni Summary Address Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-16. PNNI Summary Address Table Window The commands in this window have the following functions: Command Function Find.. Searches this table by the values you enter in the Node Index, Prefix Length, Sum- mary Type, and Summary Address fields.
  • Page 234: Pnni Summary Address Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-17. PNNI Summary Address Configuration Window The commands in this window have the following functions: Command Function Create Summary Address Adds the route address to the PNNI Sum- Entry mary Address Table window. This field is displayed only upon initial summary address configuration.
  • Page 235: Field Descriptions For The Pnni Summary Address Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-13. Field Descriptions for the PNNI Summary Address Configuration Window Field Name Field Values Description Node Index Default: 0 Displays the node index that identifies a logical PNNI entity in the PSAX system. Range: 1–400 Format: numeric Summary Address...
  • Page 236: Viewing The Pnni Map Information

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Viewing the PNNI Map Information The PNNI Map Table contains attributes necessary to find and analyze the operation of all links and nodes within the PNNI hierarchy, as seen from the perspective of a local node. It also provides information for network manag- ers to map port identifiers, showing the ports and links between the nodes at both endpoints.
  • Page 237: Pnni Map Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-18. PNNI Map Table Window The commands in this window have the following functions: Command Function Find... Searches this table by the values you enter in the Node Index, Org. Port Id, Map Index, or Org.
  • Page 238: Pnni Map Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-19. PNNI Map Information Window The commands in this window have the following functions: Command Function View Metrics Tables Displays the PNNI Metrics Configuration window. Go Back to Previous Screen Displays the PNNI System-Wide Configu- ration window.
  • Page 239 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-14. Field Descriptions for the PNNI Map Information Window Field Name Field Values Description [Peer Group Id] Default: N/A Displays the Peer group identifier of the originat- (display only) ing node and its peers. Range: N/A Format: Numeric [Org.
  • Page 240: Viewing Pnni Map Node Information

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Viewing 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).
  • Page 241: Field Descriptions For The Pnni Map Node Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration 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: Command Function Find.. Searches this table by the values you enter in the Node Index or Map Node Id fields.
  • Page 242: Pnni Map Node Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-21. 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 manu- ally configured. The command on this window performs the following function: Command Function Go Back to Previous Screen...
  • Page 243: Field Descriptions For The Pnni Map Node Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-16. Field Descriptions for the PNNI Map Node Information Window Field Name Field Values Description Node Index Default: 0 Displays the node index identifies a logical PNNI (display only) entity in the PSAX system. Range: 1–400 Format: numeric Map Node ID...
  • Page 244 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-16. Field Descriptions for the PNNI Map Node Information Window Field Name Field Values Description Restricted Branch- Default: False Displays whether the originating node is able to support additional branches. This attribute Range: T/F (display only) reflects the setting of the restricted branching bit...
  • Page 245: Viewing Pnni Map Address Information

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-16. Field Descriptions for the PNNI Map Node Information Window Field Name Field Values Description Parent ATM Default: 0 Displays the ATM address of the parent LGN Address when the originating node is a peer group leader. Range: N/A (display only) If the originating node is not peer group leader of...
  • Page 246: Pnni Map Address Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-22. PNNI Map Address Table Window The PNNI Map Address Table contains a list of all reachable addresses from each node visible to the local node. The table is read-only, as reach- able addresses are discovered during dynamic operation of the PNNI pro- tocol, not manually configured.
  • Page 247: Pnni Map Address Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-17. Field Descriptions for the PNNI Map Address Table Window Field Name Description Total: 0/0 The first number in this field indicates the identi- fication number of the connection table entry on the first line of the currently displayed window.
  • Page 248: Viewing The Pnni Link Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Go Back to Previous Screen Redisplays the PNNI Map TNS Table win- dow. Table 5-18. Field Descriptions for the PNNI Map Address Entry Window Field Name Field Values Description [Node Index] Default: N/A Displays the node index that identifies a logical (display only)
  • Page 249: Pnni Link Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration The PSAX 1250 allows up to 100 PNNI links per interface. To view PNNI links, perform the steps in the following procedure. Begin 1 From the PNNI System-Wide Configuration window, select the PNNI Link Information command.
  • Page 250: Pnni Link Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration The commands in this window have the following functions: Command Function Find.. Searches this table by the values you enter in the Node Index or the PNNI Link Port Id fields. Go Back to Previous Screen Redisplays the PNNI System-Wide Config- uration window.
  • Page 251: Field Descriptions For The Pnni Link Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-19. Field Descriptions for the PNNI Link Configuration Window Field Name Field Values Description [Node Index] Default: 0 Displays the node index that identifies a logical (display only) PNNI entity in the PSAX system. Range: 1–400 Format: numeric [Link Port Id]...
  • Page 252 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-19. Field Descriptions for the PNNI Link Configuration Window Field Name Field Values Description [Link Hello State] Default: N/A Displays one of the possible conditions that char- (display only) acterize Hello types and the node states that the Range: N/A Hellos originated from.
  • Page 253 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-19. Field Descriptions for the PNNI Link Configuration Window Field Name Field Values Description TwoWayOutside Indicates whether Hellos have recently been received from the neighbor, whose node belongs to a different peer group, and including the cor- rect remote node ID and remote port ID fields, but with a nodal hierarchy list that does not include any common peer group.
  • Page 254: Viewing The Pnni Svcc Rcc Information

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-19. Field Descriptions for the PNNI Link Configuration Window Field Name Field Values Description [Common Peer Gp Default: N/A Displays the common peer group identifier. For outside links and uplinks, this attribute contains Range: N/A (display only) the peer group identifier of the lowest level com-...
  • Page 255: Pnni Svccrcc Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration The PNNI SvccRcc Information window is displayed (see Figure 5-27). Figure 5-26. PNNI SvccRcc Table The commands on this window perform the following functions: Command Function Page Up Scroll up one page. Page Down Scrolls down one page.
  • Page 256: Pnni Svccrcc Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration The display fields on this window have the following values: Table 5-20. Field Descriptions for the PNNI SVCC RCC Table Window Field Name Description Node Index The node index identifies a logical PNNI entity in the (display only) PSAX system.
  • Page 257: Field Descriptions For The Pnni Svcc Rcc Configuration Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-21. Field Descriptions for the PNNI SVCC RCC Configuration Window Field Name Field Values Description [Node Index] Default: 0 Displays the node index identifies a logical PNNI (display only) entity in the PSAX system. Range: 1–400 Format: numeric [Svcc Rcc Index]...
  • Page 258: Viewing The Pnni Neighbor Peer Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Viewing the PNNI Neighbor Peer Table The PNNI Neighbor Peer Table window contains all the attributes necessary to describe the relationship a node in the PSAX system has with a neighbor- ing node within the same peer group. The PNNI Neighbor Peer Table window is read-only because neighboring peers are generated dynamically by the PNNI protocol, not manually configured.
  • Page 259: Pnni Neighbor Peer Table Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-28. 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. The PNNI Neighbor Peer Remote Node Id field is the node identifier of the neighboring peer node.
  • Page 260: Pnni Neighbor Peer Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Figure 5-29. PNNI Neighbor Peer Information Window The command in this window has the following function: Command Function Go Back to Previous Redisplays the PNNI System-Wide Configura- Screen tion window. Table 5-22. Field Descriptions for the PNNI Neighbor Peer Configuration Window Field Name Field Values Description...
  • Page 261 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-22. Field Descriptions for the PNNI Neighbor Peer Configuration Window Field Name Field Values Description [NbrPeer State] Default: Npdown Displays the state of this node’s neighboring peer (display only) state machine associated with the neighbor peer Range: N/A remote node ID.
  • Page 262: Viewing The Pnni Neighbor Peer Port Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-22. Field Descriptions for the PNNI Neighbor Peer Configuration Window Field Name Field Values Description [NbrPeer Rcv Default: N/A Displays a count of the number of database sum- DbSums) mary packets received from the neighboring peer. Range: N/A (display only) Format: numeric...
  • Page 263: Pnni Neighbor Peer Port Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration 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. Figure 5-30. PNNI Neighbor Peer Port Table The PNNI Neighbor Peer Port table shows all ports in hello state two-way inside to a given neighboring peer node.
  • Page 264: Viewing Pnni Topology State Element (Ptse) Information

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Find...Node Index Enter the five-digit value for the node to be searched. Port Id Enter the 10-digit port ID to be searched. Rmt. Node Id: Enter the 11-octet ID address of the remote node to be searched.
  • Page 265: Pnni Ptse Table

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration The PNNI PTSE Table is displayed (see Figure 5-31). The fields in the PNNI PTSE Table window are provided in Table 1-8. 2 To view information about an entry on this table, select an entry. The PNNI PTSE Information window is displayed (see Figure 5-32).
  • Page 266: Pnni Ptse Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Ptse Id Enter the 10-digit PTSE ID to be searched. Org. Node Id: Enter the 11-octet organizational node ID address to be searched. Go Back to Previous Screen Redisplays the PNNI System-Wide config- uration window.
  • Page 267: Field Descriptions For The Pnni Ptse Information Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Go Back to Previous Screen Redisplays the PNNI Map TNS Table win- dow. Table 5-25. Field Descriptions for the PNNI PTSE Information Window Field Name Field Values Description Node Index Default: N/A Displays the node index that identifies a logical (display only) PNNI entity in the PSAX system.
  • Page 268 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-25. Field Descriptions for the PNNI PTSE Information Window Field Name Field Values Description Type Default: Other Describes the architecture parameters set (display only) selected. Range: N/A Format: Predefined Other User defined. NodalState Indicates that the nodal state parameter informa- Parameters...
  • Page 269: Viewing Pnni System Statistics

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Viewing PNNI System Statistics To view PNNI system statistics, perform the steps in the following procedure. Begin 1 On the Console Interface Main Menu, select the Site-Specific Configura- tion option, and press Enter. The Site-Specific Menu is displayed.
  • Page 270 Chapter 5 Configuring PNNI PNNI System-Wide Configuration Command Function Continuous Update Updates the values in the fields on this window continuously. Use this command as a toggle switch to view the statistics. Go Back to Previous Screen Redisplays the PNNI System-Wide Config- uration window.
  • Page 271: Field Descriptions For The Pnni System Statistics Window

    Chapter 5 Configuring PNNI PNNI System-Wide Configuration Table 5-26. Field Descriptions for the PNNI System Statistics Window Field Name Values Description [Route Fail Count Default: 0 The total number of times where the PSAX sys- Org.] tem failed to compute a viable DTL stack as the Range: N/A (display only) DTL originator for a call.
  • Page 272 Chapter 5 Configuring PNNI PNNI System-Wide Configuration ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 5-80 255-700-247...
  • Page 273: Using Vt100 Terminal Emulation

    Using VT100 Terminal Emulation Overview of This Chapter VT100 terminal emulation is used in configuring and managing the PSAX 1250 system from the serial interface port labeled CONSOLE on the faceplate. The PSAX 1250 system software supports the following terminal emulation software: •...
  • Page 274: Connect To Window

    Chapter 6 Using VT100 Terminal Emulation Setting Up The Windows HyperTerminal Emulator 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 6-2).
  • Page 275: Connecting A Dialup Modem To The Chassis

    Chapter 6 Using VT100 Terminal Emulation Connecting a Dialup Modem to the Chassis 7 Enter the appropriate values for the fields on this window according to the information provided in Table 6-1. Table 6-1. Windows HyperTerminal Settings Option Setting Configure: 9600 baud Data bits: Parity:...
  • Page 276 Chapter 6 Using VT100 Terminal Emulation Connecting a Dialup Modem to the Chassis ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 255-700-247...
  • Page 277: Configuring Atm Trunking

    Configuring ATM Trunking Overview of This Chapter ATM trunking configuration supports switched and nonswitched IWF trunks. Configuring Switched For configuring IWF trunks in switched mode, the following list describes the IWF Trunks tasks you need to perform: 1. Configuring the local IWF node 2.
  • Page 278: Site-Specific Menu Window-Atm Trunking Configuration Option Selected

    Chapter 7 Configuring ATM Trunking Overview of This Chapter 4 To apply the configuration values, select the Apply Configuration command. 5 Select the Bring Admin Status Up command to bring the administra- tive status of the local IWF up. After you have completed configuring the local IWF node, configure the remote IWF nodes.
  • Page 279: Atm Trunking Local Node Configuration Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Figure 7-2. ATM Trunking Local Node Configuration Window The commands on this window have the following functions: Command Function Apply Configuration Applies the values you set on this win- dow. Bring Admin Status Up Enables the transmission of calls between the configured local IWF node and the remote IWF nodes.
  • Page 280: Configuring A Remote Iwf Node

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Command Function Go to Narrowband Routing Displays the ATM Trunking Narrowband Table Routing Table window. Go Back to Site-Specific Redisplays the Site-Specific Menu win- Menu dow. Table 7-1. Field Descriptions for the ATM Trunking Local Node Configuration Window Field Name Field Values Description...
  • Page 281: Atm Trunking Remote Iwf Table Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter 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-2.
  • Page 282 Chapter 7 Configuring ATM Trunking Overview of This Chapter 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.
  • Page 283: Atm Trunking Remote Iwf Configuration Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Figure 7-4. ATM Trunking Remote IWF Configuration Window The commands on this window have the following functions: Command Function Add Configuration Applies the values you set on this win- dow. Update Configuration This command is not currently supported.
  • Page 284: Field Descriptions For The Atm Trunking Remote Iwf Configuration Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Command Function Go to Data Channel Table Displays the ATM Trunking Data Channel Table window. This command is displayed only after you have added a remote IWF Go Back to Previous Screen Redisplays the ATM Trunking Remote IWF Table window Table 7-2.
  • Page 285: Adding A Signaling Vcc Identifier

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Adding a Signaling VCC Identifier Begin 1 On the ATM Trunking Remote IWF Configuration window, select the Go to Sig VCC Table command. The ATM Trunking Sig VCC Table window is displayed (see Figure 7-5). 2 Select the Add ATM Trunking Entry command.
  • Page 286 Chapter 7 Configuring ATM Trunking Overview of This Chapter Command Function Add ATM Trunking Displays the ATM Trunking Sig VCC Con- Entry figuration window. Go Back to Previous Redisplays the Remote IWF Configuration Screen window. Find Rmt IWF ID: VCC Searches the table for a specific remote IWF ID with a specific VCC ID.
  • Page 287: Atm Trunking Sig Vcc Configuration Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter The ATM Trunking Sig VCC Configuration window (see Figure 7-6) is displayed. Figure 7-6. ATM Trunking Sig VCC Configuration Window The commands on this window have the following functions: Command Function Apply Configuration Applies the values you set on this window.
  • Page 288 Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-3. Field Descriptions for the ATM Trunking Sig VCC Configuration Window Field Name Field Values Description [Remote IWF ID] Default: Remote IWF identifier for the remote endpoint. (display only) User-assigned Range: N/A Format: Numeric Sig VCC ID...
  • Page 289: Field Descriptions For The Atm Trunking Sig Vcc Configuration Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-3. Field Descriptions for the ATM Trunking Sig VCC Configuration Window Field Name Field Values Description Fwd/Bwd SCR Default: 0 / 0 Forward and backward sustained cell rate (cells (cps) per second) for the connection.
  • Page 290: Adding A Bearer Vcc Identifier

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Adding a Bearer VCC Identifier 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).
  • Page 291: Atm Trunking Bearer Vcc Table Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Figure 7-7. ATM Trunking Bearer VCC Table Window The commands on this window have the following functions: Command Function Find . . .Rmt IWF ID: Searches the table for a specific remote VCC: ID IWF ID with a specific VCC ID.
  • Page 292: Atm Trunking Bearer Vcc Configuration Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-4. Field Descriptions for the ATM Trunking Bearer VCC Table Window Field Names Description Rmt IWF ID This column displays all the remote IWF IDs in the PSAX system. VCC ID This column displays all the corresponding bearer VCC identifiers.
  • Page 293: Field Descriptions For The Atm Trunking Bearer Vcc Configuration Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Command Function Add Configuration Applies the values you set on this win- dow. Delete Configuration Deletes the configuration. Restart Connection Restarts the connection. Display Next Connection Displays the next connecion. Continuous Update Continuously update the window data every ___ msec.
  • Page 294 Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-5. 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 If configuring a Wireless backhaul applications: cell site with an MSC, both the local and remote...
  • Page 295 Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-5. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window (Continued) Field Name Field Values Description Fwd/Bwd MBS Default: 172 (Fwd Specifies the forward and backward maximum (cells) and Bwd) burst size (cells) for the connection.
  • Page 296 Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-5. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window (Continued) Field Name Field Values Description [VCC Owner] Default: Local Indicates whether the bearer VCC owner is the (display only) active (local) side or the passive (remote) side of Range: N/A the connection.
  • Page 297 Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-5. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window (Continued) Field Name Field Values Description Application Type Default: Specifies the PSAX application that will use this Narrowband trunk connection. Range: N/A Format: Predefined Narrowband...
  • Page 298 Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-5. Field Descriptions for the ATM Trunking Bearer VCC Configuration Window (Continued) Field Name Field Values Description Dsp Select Type Default: Automatic Specifies whether the DSP resources are allo- cated. The setting you select in this field must Range: N/A match the setting in the Selection Type column Format: Predefined...
  • Page 299: Adding A Narrowband Address

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-5. 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. (display only) Range: N/A Format: Predefined Idle...
  • Page 300: Atm Trunking Narrowband Routing Table Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Figure 7-9. ATM Trunking NarrowBand Routing Table Window The commands on this window have the following functions: Command Function Find: Searches for the ATM address entry with a value you specify. Go Back to Connection Redisplays the ATM Trunking Local Node Menu...
  • Page 301: Adding A Broadband Address

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-6. Field Descriptions for the ATM Trunking Narrowband Routing Table Window Field Names Values Description Narrowband Default: Displays all Interworking function ATM addresses for the Address (Hex) entries remote endpoint. Type an address in hexadecimal (display table) format up to 20 bytes (160 bits) long (10 groups Range: N/A...
  • Page 302: Atm Trunking Broadband Routing Table Window

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Figure 7-10. ATM Trunking Broadband Routing Table Window The commands on this window have the following functions: Command Function • Find: Searches for the ATM address entry with a value you specify. •...
  • Page 303: Viewing Atm Trunking Information

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Table 7-7. Field Descriptions for the ATM Trunking Broadband Routing Table Window Field Names Values Description Broadband Address Default: Displays all Interworking function ATM addresses for the (Hex) entries remote endpoint. Type an address in hexadecimal (display table) format up to 20 bytes (160 bits) long (10 groups Range: N/A...
  • Page 304: Atm Trunking Data Channel Table

    Chapter 7 Configuring ATM Trunking Overview of This Chapter Figure 7-11. ATM Trunking Data Channel Table The commands on this window have the following functions: Command Function Find... Rmt IWF ID: VCC ID: Searches the table for a specific remote IWF ID with a specific VCC ID.
  • Page 305 Chapter 7 Configuring ATM Trunking Overview of This Chapter Field Name Description Status This column displays whether the administrative status for the remote IWF is up or down. VCC Owner This column displays the corresponding owner of the signaling VCC. NB Intf This column displays the corresponding VCC ID, which is assigned by the owners of the signaling VCC.
  • Page 306 Chapter 7 Configuring ATM Trunking Overview of This Chapter ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 7-30 255-700-247...
  • Page 307: Configuring V5.2 European Idlc

    Configuring V5.2 European IDLC Overview of the V5.2 European IDLC Release 8.0.0 offers two implementations of the V5.2 Integrated Digital Loop Carrier standard (IDLC): ISDN and PSTN. The configuration sequence of either one is the same, but the values entered on some of the windows are different, especially on the User Port Configura- tion windows, the last part of the configuration on the User Side.
  • Page 308 Chapter 8 Configuring V5.2 European IDLC V5.2 PSTN Implementation on the PSAX System 6. Configure the following module parameters: a. STM-1 MSP SM/MM for ATM UNI 3 b. DSP2D Voice Server for AlgoSet6 and AAL2 Standard 7. Go to the Console Interface Main Menu> Site Specific Menu> V5 Inter- face Configuration >...
  • Page 309: Configuring V5.2 European Idlc

    Chapter 8 Configuring V5.2 European IDLC V5.2 PSTN Implementation on the PSAX System 24. Apply the Add V5 Data Link to the table command. 25. On the V5 Interface Variant Configuration window> Bring Into Service V5.2 User Side Configuration Step Summary. The following steps are a summary only.
  • Page 310: V5.2 Isdn Implementation On The Psax System

    Chapter 8 Configuring V5.2 European IDLC V5.2 ISDN Implementation on the PSAX System V5.2 ISDN Implementation on the PSAX System Select the value Isdn in the Port Type field and follow configuration instruc- tions on field description tables. PSTN Configuration Enabling the V5 Feature on the Site Specific Configuration Window Note: If necessary, delete previous configuration files on the modules to...
  • Page 311 Chapter 8 Configuring V5.2 European IDLC PSTN Configuration 5 If you need to reboot now, proceed to the section, “Rebooting PSAX Hardware Components,” in your PSAX Multiservice Media Gateway User Guide. Figure 8-1. Site-Specific Menu Window (Feature Turn On/Off Option Selected) ®...
  • Page 312: Feature Turn On/Off Window

    Chapter 8 Configuring V5.2 European IDLC PSTN Configuration Figure 8-2. Feature Turn On/Off Window The commands on this window have the following functions: Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Displays entries at the top of the table. Bottom Displays entries at the bottom of the table.
  • Page 313 Chapter 8 Configuring V5.2 European IDLC PSTN Configuration Table 8-1. Field Descriptions for the Feature Turn On/Off Table Field Name Field Values Description Total: 0/0 Default: N/A First number: Indicates which Feature ID is cur- rently selected in the table. Range: 1–6 Second number: Indicates the total number of Format: Numeric...
  • Page 314: Setting Call Control Resource Allocation Values

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-1. Field Descriptions for the Feature Turn On/Off Table Field Name Field Values Description desired status Default: Enable or Specifies whether the feature is to be made oper- (display only) Disable (depend- ational or not.
  • Page 315 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values The Call Control Resource Allocation Configuration window is displayed. Upon initial display, it appears as in Figure 8-4. In Figure 8-5, the high- lighted fields are used in V.5 configuration. 3 Enter values in the fields on this window according to the guidelines pro- vided in the section, “Configuration Guidelines,”...
  • Page 316: Call Control Resource Allocation Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-4. Call Control Resource Allocation Configuration Window Figure 8-5. Call Control Resource Allocation Configuration Window The commands on this window have the following functions: ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 8-10 255-700-247...
  • Page 317 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Command Function Apply Configuration Applies the values you entered on this window. Go Back to Site-Specific Redisplays the Site-Specific Menu win- Menu dow. Configuration Guidelines Read the following configuration guidelines before you enter values in the fields on this window.
  • Page 318: Call Control Resource Allocation Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-2. Field Descriptions for the Call Control Resource Allocation Configuration Window Field Name Field Values Description Note: The ranges of values for numeric fields are software imposed. Read the configuration guide- lines and the PSAX System Performance Capabilities per Node table in the preceding section before you enter values in the fields on this window.
  • Page 319 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-2. Field Descriptions for the Call Control Resource Allocation Configuration Window (Continued) Field Name Field Values Description spvcPtToMultiPt Default: 001000 Specifies the maximum number of parties on SPVC Parties point-to-multipoint calls to be supported by the PSAX system.
  • Page 320: Psax System Performance Capabilities Per Node For Release 8.0.0

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-2. Field Descriptions for the Call Control Resource Allocation Configuration Window (Continued) Field Name Field Values Description atmTrunkNarrow Default: 001000 Specifies the maximum number of switched narrow- BandCalls band calls supported by ATM trunking.
  • Page 321: V5 Interface Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values † For all three types of connections, you cannot configure more than the maximum number of calls indicated. For OAM monitoring, the maxi- mum number of connections you can monitor per PSAX system is 2,000.
  • Page 322: V5 Interface Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-6. V5 Interface Configuration Window The menu options on this window perform the following functions: Table 8-4. V5 Interface Configuration Menu Window Menu Option Description V5 Interface Displays the V5 Interface Configuration Configuration window.
  • Page 323: V5 Resource Allocation Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values 2 Enter the value 010 in the Max V5 Interface field. 3 Select the Apply Configuration command. 4 Remain on the window and continue with the next procedure. Figure 8-7.
  • Page 324: Field Descriptions For The V5 Resource Allocation Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-5. Field Descriptions for the V5 Resource Allocation Configuration Window Field Name Values Description Max V5 Interface Default: 004 Indicates the maximum number of V5 interfaces that can be supported in this system. Range: 0–10 Format: Numeric Max User Ports...
  • Page 325 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-5. Field Descriptions for the V5 Resource Allocation Configuration Window Field Name Values Description ReadSA7Bit Timer Default: 050 This timer is used to guarantee that the SA7 bit change has been reported to the AV5 stack.
  • Page 326 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-8. V5 Resource Allocation Configuration Window Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Scrolls to the top of the current page. Bottom Scrolls to the bottom of the current page.
  • Page 327: V5 Interface Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Accessing the V5 Interface Configuration Window, Part 2 Begin 1 From the V5 Interface Table, Select the Add an Interface command. The V5 Interface Configuration window is displayed. The table following the window describes the commands on the window.
  • Page 328 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Command Function Update Updates the window values after a field value change. Delete Interface and return Deletes the interface and returns to the V5 Interface Table. Bring Into Service Brings the variant into service.
  • Page 329: Field Descriptions For The V5 Interface Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-6. Field Descriptions for the V5 Interface Configuration Window Field Name Field Value Description Active Variant ID Default: 0 Specifies the Variant Id which is active for this V5 Interface.
  • Page 330: V5 Resource Allocation Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values 4 Remain on this window and continue with the next procedure. The tables following the window in Figure 8-10 describe the commands and display-only fields on the window. Table 8-8 describes the fields on the win- dow.
  • Page 331: Field Descriptions For The V5 Interface Variant Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-7. Field Descriptions for the V5 Interface Variant Configuration Window Field Name Field Value Field Description V5 Intf ID Default: 0 Specifies the V5 interface identifier. Range: 1–10 Format: Numeric V5 Variant ID Default: 0...
  • Page 332 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-11. V5 Resource Allocation Configuration Window Command Function Add PhysChnl Table to Vari- Displays the V5 PhysCChannel Configura- tion Table. Add E1 Link Table to Vari- Displays the V5 E1 Link Configuration Table.
  • Page 333: Field Descriptions For The V5 Interface Variant Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-8. Field Descriptions for the V5 Interface Variant Configuration Window Field Name Field Value Field Description V5 Intf ID Default: 0 Specifies the V5 interface identifier. Range: 1–10 Format: Numeric V5 Variant ID Default: 0...
  • Page 334 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-8. Field Descriptions for the V5 Interface Variant Configuration Window Field Name Field Value Field Description Align Ports Method Default: V5SecondE Indicates type of flag used for port alignment ditionPortAlign method to use along with interface type.
  • Page 335: V5 Data Link Configuration Table

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Accessing the Data Link Configuration Table Begin 1 On the V5 Interface Variant Configuration window, select the Add DL Table to Variant command. The V5 Data Link Configuration Table dis- plays (see Figure 8-12).
  • Page 336 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Command Function Add Data Link Config Entry Add a data link configuration entry. Go Back to Previous screen Returns to the V5 Interface Variant Con- figuration Window. Command Function Intf ID Displays the interface ID.
  • Page 337: V5 Data Link Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-13. V5 Data Link Configuration Window Command Function Display Next V5 Data Link Displays the next V5 data link in the table. in the table Add V5 Data Link to the Adds V5 Data Link to the V5 Data Link table configuration table.
  • Page 338: Field Descriptions For The V5 Data Link Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-9. Field Descriptions for the V5 Data Link Configuration Window Field Name Field Value Description Comm Path Id Default: V5DLCPath The types described below refer to Data Link Protection1 Control protocol.
  • Page 339: V5 Physical C-Channel Configuration Table

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values 3 Remain on this table on continue with the next procedure. Figure 8-14. V5 Physical C-Channel Configuration Table Command Function Page Up Scrolls up one page. Page Down Scrolls down one page.
  • Page 340 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Command Function Total: 0/0 The top number shows which table entry is selected; the bottom number shows total number of entries on the table. Intf ID Displays the interface ID. Variant ID Displays all the variant IDs for the Inter- face ID.
  • Page 341: V5 Physical C-Channel Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-15. V5 Physical C-Channel Configuration Window Command Function Add V5PhysCChn to the Adds the V5 physical C-channel entry to table the V5 PhysCChannel Configuration Table. Apply V5PhysCChn config- Adds the configuration values you set to uration the network database.
  • Page 342: Field Descriptions For The V5 Physical C Channel Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-10. Field Descriptions for the V5 Physical C Channel Configuration Window Field Name Field Value Description Interface ID Default: 0 This index identifies the V5 Interface configura- tion table.
  • Page 343 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-10. Field Descriptions for the V5 Physical C Channel Configuration Window Field Name Field Value Description Protection Group Default: Pg-1 Specifies whether this logical/physical channel belongs to Protection Group Number 1 or 2. Pro- Range: N/A tection Group 1 always uses the user-assigned Format: Predefined...
  • Page 344: V5 E1 Link Configuration Table

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values 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.
  • Page 345 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Command Function Intf ID Displays the interface ID. Variant ID Displays all the variant IDs for the Inter- face ID. LinkID Displays the link ID of the interface ID. OperStatus Displays the operating status of the con- nection.
  • Page 346: V5 E1 Link Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-17. V5 E1 Link Configuration Window Command Function Display Next V5E1Link in Displays the next V5 E1 link in the table. the table Add V5E1Link to the table Adds the V5 E1 link to the V5 E1 Link Configuration Table.
  • Page 347: Field Descriptions For The V5 E1 Link Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-11. Field Descriptions for the V5 E1 Link Configuration Window Field Name Field Values Description Interface Id Default: 0 Specifies the interface the user created and is cur- rently configuring.
  • Page 348 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-11. Field Descriptions for the V5 E1 Link Configuration Window Field Name Field Values Description [Operational State] Default: Normal Specifies the protection status of the link. (display only) Range: As noted below Format: Predefined...
  • Page 349: The V5 E1 Interface Configuration Window Is Entirely Display-Only Fields

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-18. The V5 E1 Interface Configuration Window Is Entirely Display-Only Fields Table 8-12. Field Descriptions for the V5 E1 Interface Configuration Window Field Name Field Values Description [Phys ID] Default: This index identifies the V5 Interface configura-...
  • Page 350 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-12. Field Descriptions for the V5 E1 Interface Configuration Window Field Name Field Values Description [Channel3] Default: Specifies a C-Channel which carries signalling (display only) information. Generally this channel should be Range: specified on a single E1 in a V5 interface group Format: Numeric...
  • Page 351: V5 Time Slot Table

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-19. V5 Time Slot Table Command Function Bring All Interfaces Into Brings all interfaces into service. Service Take All Interface Out Of Takes all interfaces out of service. Service Go Back to Previous Screen Returns to the V5 E1 Interface Configura-...
  • Page 352: V5 Data Link Configuration Table

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values 2 Remain on this window and continue with next procedure. Figure 8-20. V5 Data Link Configuration Table Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Scrolls to the top of the current page.
  • Page 353 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Command Function DL C Path ID Displays the Data Link Communication Path ID. Total 0/0 The first number in this field indicates the number of the V5 Interface ID on the first line of the currently displayed window.
  • Page 354: V5 Data Link Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-21. V5 Data Link Configuration Window Command Function Display Next V5 Data Link Displays the next V5 data link in the table. in the table Add V5 Data Link to the Adds V5 Data Link to the V5 Data Link table configuration table.
  • Page 355 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-13. Field Descriptions for the V5 Data Link Configuration Window Field Name Field Value Description Comm Path Id Default: V5DLCPath The types described below refer to Data Link Protection1 Control protocol.
  • Page 356 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values User Side Configuration Step Summary The next part of V5.2 configuration is to configure the User Side. The follow- ing steps are a summary; actual configuration begins with the Accessing the User Port Table procedure below.
  • Page 357: V5 User Port Table

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values 2 After completing the remote and local node configuration for ATM trunking, continue with the procedure below. Accessing the V5 User Port Table Begin See the “Accessing the V5 Interface Configuration Window, Part 1” on page 19 to start this procedure.
  • Page 358 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Command Function Page Up Scrolls up one page. Page Down Scrolls down one page. Scrolls to the top of the current page. Bottom Scrolls to the bottom of the current page. Find...
  • Page 359: V5 User Port Configuration Window For Pstn As Port Type

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-23. V5 User Port Configuration Window for PSTN as Port Type Command Function Display Next V5 User Port Displays the next V5 User Port configura- Configuration tion in the database. Add V5 User Port Configu- Adds the V5 User Port configuration for ration...
  • Page 360: Field Descriptions For The V5 User Port Configuration Window

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-14. Field Descriptions for the V5 User Port Configuration Window Field Name Values Description Interface Id Default: 0 Specifies the ID the PSAX uses internally for the interface after the interface is created.
  • Page 361 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-14. Field Descriptions for the V5 User Port Configuration Window Field Name Values Description ISDN D channels Default: [128] Specifies the Cid value of ISDN D channels that the PSAX is dynamically allocating.
  • Page 362 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-14. Field Descriptions for the V5 User Port Configuration Window Field Name Values Description Admin Status Default: Blocked Specifies the administrative status of the user port. Range: As noted below.
  • Page 363 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-14. Field Descriptions for the V5 User Port Configuration Window Field Name Values Description F-Logical Chan ID Default: 0 ISDN Data Type F-Logical channel identifier which must be unique for an interface Range: 0–65503 Note: This configurable field displays only when Format: Numeric...
  • Page 364 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-14. Field Descriptions for the V5 User Port Configuration Window Field Name Values Description Voice Compression Default: None Specifies the user-assigned voice compression Algo algorithm used. Range: N/A Format: Predefined None No compression is used on the connection.
  • Page 365 Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Table 8-14. Field Descriptions for the V5 User Port Configuration Window Field Name Values Description Translation Type Default: None Specifies which companding standard is used. A law is European; Mu law is Japanese and North Range: N/A American.
  • Page 366: V5 User Port Configuration Window, Port Type Isdn Selected

    Chapter 8 Configuring V5.2 European IDLC Setting Call Control Resource Allocation Values Figure 8-24. V5 User Port Configuration Window, Port Type ISDN Selected ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 8-60 255-700-247...
  • Page 367: Using System Diagnostics

    Using System Diagnostics Overview of This Chapter The PSAX system diagnostics 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 CPU ~ CPU and memory utilization details ~ Statistics on the message pool and the cell buffers •...
  • Page 368: Viewing System Status

    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.
  • Page 369: Diagnostics Menu Window

    Chapter 9 Using System Diagnostics Viewing System Status Figure 9-1. Console Interface Main Menu Window (Diagnostics Option Selected) Figure 9-2. Diagnostics Menu Window ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 255-700-247...
  • Page 370: System Information Window

    Chapter 9 Using System Diagnostics Viewing System Status Figure 9-3. System Information Window The commands on this window have the following functions: Command Function Continuous Update Continuously updates the information in the fields every second. Select this com- mand to turn the continuous updating on and off as needed (similar to a toggle switch).
  • Page 371: Field Descriptions For The System Information Window

    Chapter 9 Using System Diagnostics Viewing System Status Table 9-2. Field Descriptions for the System Information Window Field Name Field Values Description [Software Version] Default: N/A The version of the system software currently run- ning on the CPU. (display only) Range: N/A Format: Predefined [Current Time]...
  • Page 372: Running Cell Test Diagnostics

    Chapter 9 Using System Diagnostics Running Cell Test Diagnostics Table 9-2. Field Descriptions for the System Information Window Field Name Field Values Description Rx One Cell Default: N/A Total: Indicates the number of cells within the (display only) receive one cell pool. Range: N/A Used: Indicates the number of cells currently Format: Numeric...
  • Page 373: Cell Test Diagnostics Window

    Chapter 9 Using System Diagnostics Running Cell Test Diagnostics 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 9-3. 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.
  • Page 374: Field Descriptions For The Cell Test Diagnostics Window

    Chapter 9 Using System Diagnostics Running Cell Test Diagnostics The commands on this window have the following functions: Command Function Apply and Configure Pay- Applies the traffic parameters you set, and load displays the Cell Test Payload Configura- tion window. Go Back to Diagnostics Redisplays the Diagnostics Menu window.
  • Page 375: Cell Test Payload Configuration Window

    Chapter 9 Using System Diagnostics Running Cell Test Diagnostics Table 9-3. Field Descriptions for the Cell Test Diagnostics Window Field Names Values Description Flow Default: SimplexTx The type of traffic flow you want to set up for the test: one-way transmit, one-way receive, or two- SimplexRx, Duplex way flow.
  • Page 376: Field Descriptions For The Cell Test Payload Window

    Chapter 9 Using System Diagnostics Running Cell Test Diagnostics Command Function Continuous Update Continuously updates the information in the [Packets Transmitted, Received, and Mis- matched] fields every two seconds. Select this command and press Enter to turn the continu- ous updating on and off as needed (similar to a toggle switch).
  • Page 377: Rebooting Psax Hardware Components

    Chapter 9 Using System Diagnostics Rebooting PSAX Hardware Components Table 9-4. Field Descriptions for the Cell Test Payload Window Field Names Values Description [Packets Transmit- System-generated The number of packets transmitted. ted] (display only) [Packets Received] System-generated The number of packets received. (display only) [Packets Mis- System-generated...
  • Page 378: Remote Reboot Configuration Window

    Chapter 9 Using System Diagnostics Rebooting PSAX Hardware Components 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 mod- ule(s).
  • Page 379 Chapter 9 Using System Diagnostics Rebooting PSAX Hardware Components Command Function Reboot the I/O Card in Reboots the I/O or server module in the Slot:__ slot you designate.This command is the equivalent to physically deinserting the module from and then reinserting it into the chassis.
  • Page 380: Removing Configuration Files

    Chapter 9 Using System Diagnostics Removing Configuration Files Command Function Reboot Chassis 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;...
  • Page 381: Unlocking A Telnet Session

    Chapter 9 Using System Diagnostics Unlocking a Telnet Session 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.
  • Page 382: Operations Administration And Maintenance (Oam)

    Chapter 9 Using System Diagnostics Operations Administration and Maintenance (OAM) This command sends a ping command to the remote PSAX system speci- fied in the IP Address field or to another switching device to indicate whether or not you can connect to that remote device. Figure 9-7.
  • Page 383: Oam Loopback Table Window

    Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Begin 1 On the Console Interface Main Menu window, select the Diagnostics option. The Diagnostics Menu window is displayed (see Figure 9-2). 2 On the Diagnostics Menu window, select the OAM Loopback option. The OAM Loopback Table window is displayed (see Figure 9-8).
  • Page 384: Oam Loopback Window

    Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Command Function Bottom Displays entries at the bottom of the table. 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.
  • Page 385: Field Descriptions For The Oam Loopback Window

    Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions 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.
  • Page 386 Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Table 9-5. Field Descriptions for the OAM Loopback Window Field Name Field Values Description Statistics Panel [Test Status] Default: Inactive Indicates the current status of the loopback test. (display only) Range: N/A Format: predefined alphanumeric Active, Successful,...
  • Page 387: Oam Activation And Deactivation

    Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Table 9-5. Field Descriptions for the OAM Loopback Window Field Name Field Values Description OAM Loopback Default: End-to-end Indicates the method of loopback testing per- Type formed for this PSAX device. Range: N/A Format: predefined alphanumeric...
  • Page 388: Oam Activate & Deactivate Table Window

    Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions The OAM ACTIVATION-DEACTIVATION window is displayed in Figure 9-11. 4 Enter values in the fields on this window according to the information provided in Table 9-6. 5 To begin the test, select the Activate command. 6 To terminate the test, select the Deactivate command.
  • Page 389: Oam Activation -Deactivation Window

    Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Figure 9-11. OAM Activation –Deactivation Window The commands on this window have the following functions: Command Function Update Status Updates the information in the Current Status panel. Activate Starts the OAM test. Deactivate Terminates the OAM test.
  • Page 390 Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Table 9-6. Field Descriptions for the OAM Activation-Deactivation Window Field Name Field Values Description OAM Function Default: Check to see if OAM cells flow continuously Type Continuity-check, throughout the length of a single connection. Pmbr-and-cc, Forward performance monitoring/backward reporting and continuity check...
  • Page 391 Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Table 9-6. Field Descriptions for the OAM Activation-Deactivation Window Field Name Field Values Description [Src Point ETE PM] Default: Displays the current status of the performance (display only) Deactivated, monitoring activation/deactivation request at the source point.
  • Page 392 Chapter 9 Using System Diagnostics Enabling OAM Loopback Functions Table 9-6. Field Descriptions for the OAM Activation-Deactivation Window Field Name Field Values Description [BR Block Error] Default: 0 Backward reporting of a block error on a perfor- (display only) mance monitoring connection. Range: 0-32768 Format: Numeric [BR lost inserted...
  • Page 393: Backing Up And Restoring Psax System Files

    Backing Up and Restoring PSAX System Files Overview of This Chapter This chapter describes how to back up and restore PSAX system configura- tion database files. The following procedures are presented: • Backing up PSAX system, module, and connection configuration database files by using the following methods: ~ Backing up database files using FTP (see “Backing Up System Database Files”...
  • Page 394: Backing Up System Database Files

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database 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 CPU module, you can restore your backup files from the host computer to the PSAX system CPU2 module system disk by using the Remote Data Operation window.
  • Page 395: Field Descriptions For The Remote Database Operation Window

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files Command Function Apply remote database Starts the function you selected in the operation Operation field. Go Back to Main Menu Redisplays the Console Interface Main Menu window. Table 10-1.
  • Page 396 Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files Table 10-1. Field Descriptions for the Remote Database Operation Window Field Name Field Values Description [Oper Status] Default: NoActivity Operational status indicating what activity is cur- (display only) rently taking place.
  • Page 397: Backing Up Database Files Using Ftp

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files You can use one of the following methods: • Upload the database files using FTP server software (see the following sec- tion, “Backing Up Database Files Using FTP”) •...
  • Page 398: Backing Up Database Files Using Xmodem/Ymodem Transfer

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files get filename where filename is the one of the following configuration files on your PSAX system. Note: Because your system might not be configured with some fea- tures, some of the following files might not exist on your system: •...
  • Page 399: Setting Up For The File Transfer Process

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files Setting Up for the File Transfer Process Begin 1 Set up the cabling and connections between the PC workstation, the local modem, and the telephone line. For more information, see the sec- tion, “Upgrading Using the XModem/YModem File Transfer Method,”...
  • Page 400: Software Version Configuration Window

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files The Software Version Configuration window (see Figure 10-2) is dis- played. Figure 10-2. Software Version Configuration window (XMODEM/YMODEM File Transfer Selected) 3 On the Software Version Configuration window, select the XMODEM/YMODEM File Transfer option and press Enter.
  • Page 401: Xmodem/Ymodem File Transfer Window (Send Options Panel Selected)

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files The XMODEM/YMODEM File Transfer window (see Figure 10-3) is dis- played. Figure 10-3. XMODEM/YMODEM File Transfer Window (Send Options Panel Selected) Note: For the database file transfer process, use only the Send Options panel.
  • Page 402: Field Descriptions For The Xmodem/Ymodem File Transfer Window

    Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files Note: To upgrade your PSAX system software, use only the fields on the Receive Options panel. To back up your PSAX system configura- tion (database) files, use only the fields on the Send Options panel. Table 10-2.
  • Page 403 Chapter 10 Backing Up and Restoring PSAX System Files Backing Up System Database Files Table 10-2. Field Descriptions for the XMODEM/YMODEM File Transfer Window (Continued) Field Names Field Values Description Filename Default: N/A Specifies the filename on the CPU2 module sys- tem disk where the software upgrade files are Range: N/A received (stored).
  • Page 404 Range: N/A your computer workstation. Format: alphanu- meric Lucent recommends that you use either the YModem or the Notes: YModem-G protocol. Use the XModem protocol if that is the only one you have available to use. • The YModem-G protocol allows the fastest transmission of the three types;...
  • Page 405: Restoring System Database Files

    Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files x:/directory/filename where x is the drive letter for the PC hard disk and directory is any name you choose (such as acdbase) 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.
  • Page 406: Restoring Database Files Using Ftp

    Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files • IISP VBR route table—iisp.vbr (this file exists even if you have no config- ured SVCs on your PSAX system) Restoring Database Files Using FTP To restore database files from a separate storage medium using FTP, perform the steps in the following procedure.
  • Page 407: Rebooting The Psax System

    Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files • put intfprot.db • put ssid.def • put console.def • put ecd.db • put pnnimib.db • put cnctn.db • put spvc.db • put fwc.def • put eventmgr.cfg 8 If you have SVCs configured on your system, type the following com- mands and press Enter after each one: •...
  • Page 408: Restoring Database Files Using Xmodem/Ymodem File Transfer

    Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files 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 separate storage medium to the CPU hard disk. Restoring the databases using the XModem/YModem file transfer option is a process transferring files from the PC workstation to the PSAX system.
  • Page 409: Copying The Backup Files To The System

    Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files Copying the Backup Steps to Copy the Backup Database Files to the System Files to the System Begin 1 Using the terminal emulator, log on the PSAX system. 2 On the Console Interface Main Menu window, select the Software Ver- sion Configuration option and press Enter.
  • Page 410 Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files Command Function Send File Initiates the send function of the file transfer process from the CPU module hard disk to a storage medium (such as a Unix or PC workstation hard disk). Receive File Initiates the receiving function of the file transfer process to the CPU module hard...
  • Page 411 Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files Table 10-3. Field Descriptions for the XMODEM/YMODEM File Transfer Window Field Names Field Values Description File Type Default: Binary Indicates the format of the file that will be trans- mitted.
  • Page 412 Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files Table 10-3. Field Descriptions for the XMODEM/YMODEM File Transfer Window Field Names Field Values Description File Type Default: Binary Indicates the format of the file that will be trans- mitted.
  • Page 413 Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files Table 10-3. Field Descriptions for the XMODEM/YMODEM File Transfer Window Field Names Field Values Description Protocol Default: YModem Indicates the type of modem protocol used for sending data. See the recommendation notes at Range: N/A the end of this table for additional information.
  • Page 414 Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files Notes: Lucent recommends that you use either the YModem or the YModem-G protocol. Use the XModem protocol if that is the only one you have available to use.
  • Page 415: Rebooting The Psax System

    Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files Rebooting the PSAX Steps to Reboot the PSAX System System Begin 1 Redisplay the Console Interface Main Menu window. 2 On the Console Interface Main Menu window, select the Diagnostics option.
  • Page 416 Chapter 10 Backing Up and Restoring PSAX System Files Restoring System Database Files ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 10-24 255-700-247...
  • Page 417: Upgrading Psax System Software

    Lucent Technologies, Inc. personnel. The Release Note for the system software version to which you are upgrading identifies any affected modules.
  • Page 418: Saving Your Modified System Configuration

    Chapter 11 Upgrading PSAX System Software Saving Your Modified System Configuration • The directory /version/next, where version stands for the new software release number. • The directory /version/mib, which contains the V1 and V2 management information bases (MIBs), which you can use with an SNMP manager. The following directory structure is resident on the hard disk of the CPU2 module: •...
  • Page 419: Preparing To Install A New Software Release

    Chapter 11 Upgrading PSAX System Software Preparing to Install a New Software Release On the Console Interface Main Menu window, [Modified] is displayed next to the Save Configuration command, indicating you have made changes to your system that are not yet saved to the database. 2 Select the Save Configuration command.
  • Page 420: Tasks For Transferring Files To Your Psax System

    Chapter 11 Upgrading PSAX System Software Preparing to Install a New Software Release Table 11-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 CPU2 module (or CPU2 com- ponent) system disk (see the section, “Upgrading Using the File Transfer Protocol Method”).
  • Page 421: Upgrading Using The File Transfer Protocol Method

    Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Software Upgrade Process FTP File Transfer Process (Second Stage) (First Stage) Fallback Directory /scsi/fallback/ Fallback Directory (now contains the old version-- /scsi/fallback/ the original contents are deleted) Old version of software and current databases are copied Current Directory...
  • Page 422: Upgrading The Psax System Software Using Ftp

    Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method ble for following the terms of the author’s licensing agreement, including payment. To set up your FTP server software, perform the steps in the follow- ing procedure. Setting Up a Windows FTP Server Begin 1 If you are using Windows 95 or 98, obtain an FTP server software pro-...
  • Page 423 Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Downloading Software Upgrade Files Using FTP Begin 1 On the Console Interface Main Menu window (see Figure 11-2), select the Software Version Configuration option. Figure 11-2. Console Interface Main Menu Window ®...
  • Page 424: Srd Download Configuration Window

    Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method The Software Version Configuration window (see Figure 11-3) is dis- played. Figure 11-3. Software Version Configuration Window 2 Select the FTP Software Release Distribution option. The SRD Download Configuration window (see Figure 11-4) is dis- played.
  • Page 425: Field Descriptions For The Srd Download Configuration Window

    Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Commands The commands on the SRD Download Configuration window have the fol- lowing functions. Command Function Start System Software FTP Begins the software release download via Process the FTP connection.
  • Page 426 PSAX system Release 6.0.0 or later using a Unix host worksta- tion. License Key Default: N/A Lucent software license. This field is not currently supported. Range: N/A Format: N/A [Copy Status] Default: NoActivity Displays the status of the file copying (display only) during the FTP download.
  • Page 427 Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Table 11-3. 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;...
  • Page 428: Library

    Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Table 11-3. Error Status Code Values for the [Error Status] Field on the SRD Download Configuration Window (Continued) Field Value Description LibraryCRCFail Displayed when the cyclic redundancy checking on a down- loaded library failed.
  • Page 429 Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Table 11-3. Error Status Code Values for the [Error Status] Field on the SRD Download Configuration Window (Continued) Field Value Description UnableToWriteFile Displayed when the system cannot write to a file, for exam- ple, the disk drive failed.
  • Page 430: Determining Whether To Proceed With System Upgrade

    Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Table 11-4. Determining Whether to Proceed with System Upgrade If you want to... do the following: The system... change your system type N (for no). displays the following message: configuration before Operation aborted.
  • Page 431: Determining Whether To Save Your Current System Configuration Before Upgrade

    Chapter 11 Upgrading PSAX System Software Upgrading Using the File Transfer Protocol Method Table 11-5. Determining Whether to Save Your Current System Configuration Before Upgrade If you... do the following: The system... do not want to pro- type N (for no). displays the following message: ceed with an Please save the configuration files from...
  • Page 432: Upgrading Using The Xmodem/Ymodem File Transfer Method

    Chapter 11 Upgrading PSAX System Software Upgrading Using the XModem/YModem File Transfer Method Upgrading Using the XModem/YModem File Transfer Method You can use the XModem/YModem file transfer method to load new system software to the CPU2 module. Upgrading using the XModem/YModem file transfer method includes two major tasks: 1.
  • Page 433: Downloading Software Files Using Xmodem/Ymodem

    Chapter 11 Upgrading PSAX System Software Upgrading Using the XModem/YModem File Transfer Method Table 11-7. Setting Up the Connection Between the Modem and the PSAX System Connect a cable from the... to the... CONSOLE port on the primary CPU2 module modem.
  • Page 434 Chapter 11 Upgrading PSAX System Software Upgrading Using the XModem/YModem File Transfer Method 3 On the Software Version Configuration window, select the XMODEM/YMODEM File Transfer option. The XMODEM/YMODEM File Transfer window (see Figure 11-6) is dis- played. Figure 11-6. XMODEM/YMODEM File Transfer Window (Receive Options Panel Selected) The commands on this window have the following functions: Command...
  • Page 435 Chapter 11 Upgrading PSAX System Software Upgrading Using the XModem/YModem File Transfer Method Note: To upgrade your PSAX system software, use only the fields on the Receive Options panel. To back up your PSAX system configura- tion (database) files, use only the fields on the Send Options panel. Table 11-8.
  • Page 436 Chapter 11 Upgrading PSAX System Software Upgrading Using the XModem/YModem File Transfer Method Table 11-8. Field Descriptions for the XMODEM/YMODEM File Transfer Window (Continued) Field Names Field Values Description Filename Default: N/A Specifies the filename on the CPU2 module sys- tem disk where the software upgrade files are Range: N/A received (stored).
  • Page 437 Range: N/A your computer workstation. Format: alphanu- meric Lucent recommends that you use either the YModem or the Notes: YModem-G protocol. Use the XModem protocol if that is the only one you have available to use. • The YModem-G protocol allows the fastest transmission of the three types;...
  • Page 438: Upgrading The Psax System Software Using Xmodem/Ymodem Transfer

    Chapter 11 Upgrading PSAX System Software Upgrading Using the XModem/YModem File Transfer Method • x:/scsi/next/subdirectory\*.* if you are using YModem or YModem-G where is the drive letter for the CD-ROM drive • x:/scsi/next/subdirectory\filename if you are using XModem where is the drive letter for the CD-ROM drive Be sure you enter the subdirectory name (or the subdirectory and file- name if using XModem) exactly so that it matches the names you previ- ously entered on the XMODEM/YMODEM File Transfer window (see...
  • Page 439: Upgrading Firmware

    PSAX 1250 PSAX AC 60, and PSAX 20 Multiservice Media Gateways. CAUTION: Use the Firmware Version Control window (see Figure 11-7) described in the following procedure only with the advice of Lucent Technologies NetworkCare. See the “Technical Support” section in Chapter 1, “Getting Started.”...
  • Page 440: System Updating Of Firmware Drivers

    You can then either select another available driver or keep the nondefault driver abc. For guidance, seek the advice of Lucent Technologies NetworkCare. Selecting Firmware Drivers You can select either the default driver or a nondefault driver from the avail- able drivers: •...
  • Page 441: Upgrading I/O And Server Module Firmware

    Chapter 11 Upgrading PSAX System Software Upgrading Firmware • If you select a nondefault driver, you can update the firmware for the selected module only if that slot contains the same module that was previ- ously configured in that slot. This constraint exists because the PSAX sys- tem database has stored values for each of the configured modules in the chassis by slot number.
  • Page 442: The Software Version Configuration Window (Firmware Version Control Option Selected)

    Chapter 11 Upgrading PSAX System Software Upgrading Firmware The Software Version Configuration window (see Figure 11-9) is dis- played. Figure 11-9. The Software Version Configuration Window (Firmware Version Control Option Selected) 2 Select the Firmware Version Control option. The Firmware Version Control window (see Figure 11-10) is displayed. Figure 11-10.
  • Page 443: Field Descriptions For The Firmware Version Control Window

    Chapter 11 Upgrading PSAX System Software Upgrading Firmware Command Function Update Screen Refreshes the values on this window to display the current firmware configura- tion for all modules in the system. Start Upgrade Initiates the downloading of firmware by the selected driver in the NextVersion field.
  • Page 444: Falling Back To The Previous Software Release

    Chapter 11 Upgrading PSAX System Software Falling Back to the Previous Software Release 3 Select the line containing the module you want to update, and select the desired driver in the NextVersion field. 4 To download the selected driver, select the Start Upgrade command. When the downloading procedure is completed successfully, a confirma- tion message, , is displayed in the status...
  • Page 445: Software Version Configuration Window (Fallback To Previous Version Selected)

    Chapter 11 Upgrading PSAX System Software Falling Back to the Previous Software Release The Software Version Configuration window (see Figure 11-11) is dis- played. Figure 11-11. Software Version Configuration Window (Fallback to Previous Version Selected) 2 Select the Fallback to Previous Version option. The following message is displayed: Are you sure that you want to Return to the previous ver- sion? (y/n)
  • Page 446 Chapter 11 Upgrading PSAX System Software Falling Back to the Previous Software Release ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 11-30 255-700-247...
  • Page 447: Overview Of This Appendix

    SNMP Trap Messages Overview of This Appendix This appendix describes the SNMP trap and notification messages generated by the PSAX system SNMP agent for Release 8.0.0. External SNMP managers can perform various functions in the PSAX system, and can receive the trap and notification messages.
  • Page 448 Appendix Viewing Trap Log Information Figure A-1. Console Interface Main Menu Window (Trap Log Display Selected) The Trap Log Display window is displayed (see Figure A-2) Figure A-2. Trap Log Display Window 2 To find a description of what a trap message means, follow these steps. ®...
  • Page 449: System Indicators

    Appendix Viewing Trap Log Information a Look in Table A-2 and find the trap message for which you want information. For example, you might want information about the trap message . The entry for the message cardInsertionNotify contains the following information: cardInsertionNotify •...
  • Page 450: Snmp Trap Names And Descriptions With Associated Mib Object Names

    Appendix Viewing Trap Log Information Table A-1. System Indicators (Continued) System Indicator for the Trap Definition (Column 3 in Table A-2) Minor Problem A notification of a problem that does not affect service or function (“Minor” in Table A-2) of a component of the Multiservice Media Gateway system (for example, the failure of a redundant power supply module).
  • Page 451 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number aal2TrunkConfigS Connec- Response aal2TrunkConfigIf, The specified PVC VCC con- etupNotify tion Event,...
  • Page 452 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number ambientTempera- System Information ambientTemperature The ambient temperature tureChangeNotify Event, 52...
  • Page 453 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number atmAtm- Interface Information spvcAddrIfA, atmAtm- An SPVC connection SpvcVccSetUpNo- Event, 67...
  • Page 454 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number atmAtmSpvp- Interface Information spvcAddrIfA, atmAtm- An ATM SPVP configura- ModifiedNotify Event, 108...
  • Page 455 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number atmImaIntf- Interface Information atmImaIntfIndex, atmI- A failure has been cleared in ClearedNotify Event, 39...
  • Page 456 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number atmSpvcConfig- Interface Information atmSpvcVccIfA, atm- An attempt to configure an FailNotify Event, 31...
  • Page 457 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number atmTrunking- Interface Information atmTrunkingBrVc- An ATM trunking bearer BrVccDeletedNo- Event, 126...
  • Page 458 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number atmTrunkingRe- Interface Information atmTrunkingRemoteI- An ATM Trunking Remote moteIWFModify- Event, 120...
  • Page 459 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number bridgeAtmBk- Connec- Response bridgeAtmPvcVccIfA, The DHPVC VCC backup PvcVccReqFailNo- tion Event,...
  • Page 460 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number bridgeDomain- Interface Information bridgeDomainNumber The 15 ports available for FullNotify Event, 7...
  • Page 461 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number channelization- Interface Information portId, interfaceFailure- Channelizing/unchanneliz- ModifyFailNotify Event, 19...
  • Page 462 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number cirEmAtmBk- Connec- Response cirEmAtmPvcVccIfA, The DHPVC VCC backup PvcVccSetupNo- tion Event,...
  • Page 463 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number cirEmCirEmPvc- Connec- Response cirEmCirEmPvcIfA, cir- The PVC connection TearDownNotify tion Event,...
  • Page 464 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number compositeClock- System Critical < NO OBJECTS > The composite clock has FailNotify Event, 6...
  • Page 465 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number ecdBootFail- System Critical < NO OBJECTS > System failed in the Boot ureNotify Event, 3...
  • Page 466 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number frAtmBkPvcVcc- Connec- Response frAtmPvcVccIfA, frAt- The DHPVC VCC backup TearDownNotify tion Event,...
  • Page 467 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number frAtmSpvcModi- Interface Information spvcAddrIfA, frAtm- An SPVC endpoint has been fiedNotify Event, 63...
  • Page 468 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number gr303Aal2PvcTear Connec- Critical gr303Aal2PvcVccGr303 A monitor connection DownNotify tion Event,...
  • Page 469 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number gr303IgOutOfSer Interface Information gr303IgId A GR303IG is out of service.
  • Page 470 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number imaGroupStatus- Module Information interfaceIndex, imaGr- The indicated SSPPCCC has ChangeNotify Event, 11...
  • Page 471 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number interfaceBand- Interface Information interfaceIndex, inter- An interface has undergone widthChangeNo- Event, 104...
  • Page 472 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number ipAtmAppPvcVcc- Connec- Response ipAtmAppPvcVccDes- The PVC VCC connection TearDownNotify tion Event,...
  • Page 473 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number iuaAspState- Interface Information iuaAspEpId, iuaAsId, A change in the state of an ChangeNotify Event, 183...
  • Page 474 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number iuaTBeatValue- Interface Information iuaTBeatValue An attempt to change the ModifyFailNotify Event, 179...
  • Page 475 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number lineStatusChan- Module Major portId, lineStatus The specified port has had a gedNotify Event, 3...
  • Page 476 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number muxReadyCon- System Information < NO OBJECTS > The MUX (the Multiservice firmReceivedNo- Event, 11...
  • Page 477 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number ntomProtection- Module Information workingCardSlot, pro- A switchover in an N to M SwitchoverNotify Event, 13...
  • Page 478 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number oneWayMessage- System Major < NO OBJECTS > A one way message is WhileInTwoWay- Event, 13...
  • Page 479 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number pnniRtAddrAd- System Information swtchNodeIndx, inter- An end system address has dByIlmiNotify Event, 41...
  • Page 480 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number referenceClock- System Critical < NO OBJECTS > The reference clock used for FailNotify Event, 4...
  • Page 481 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number snmpCommuni- System Critical < NO OBJECTS > An error has been detected tyString- Event, 30...
  • Page 482 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number switchAlarmSta- System Critical switchAlarmStatus A change in the status of the tusChangeNotify Event, 59...
  • Page 483 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number tasTstLineNotify System Information tasTstLineReasonCode, The result of the requested Event, 50 tasTrapTstId...
  • Page 484 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5E1LinkCantBeT Interface Information v5IntfId, v5VariantId, The V5 Interfaces variant E1 akenOOSWhen- Event, 189...
  • Page 485 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceCreate Interface Information v5IntfId The V5 Interface has been dNotify Event, 133...
  • Page 486 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceE1Lin Interface Information v5IntfId, v5VariantId, The E1 Link has been suc- kAddedNotify Event, 145...
  • Page 487 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceE1Lin Interface Information v5IntfId, v5VariantId, An attempt to modify one of kModifyFailNotify Event, 153...
  • Page 488 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceLogCC Interface Information v5IntfId, v5VariantId, The logical C Channel has hanDeleteNotify Event, 161...
  • Page 489 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfacePhysC Interface Information v5IntfId, v5VariantId, An attempt to create the ChanCreateFail- Event, 157...
  • Page 490 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceProtect Interface Information v5IntfId, The protection switchover ionSwitchover- Event, 151...
  • Page 491 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceUserPo Interface Information v5IntfId, v5VariantId, The User Port has been suc- rtAddedNotify Event, 165...
  • Page 492 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceUserPo Interface Information v5IntfId, v5VariantId, The v5 Interfaces port is rtBlockedNotify Event, 172...
  • Page 493 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceUserPo Interface Information v5IntfId, v5VariantId, The v5 Interfaces port is rtUnBlockedNo- Event, 173...
  • Page 494 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5InterfaceVarian Interface Information v5IntfId, v5VariantId, An attempt to modify one of tModifyFailNotify Event, 152...
  • Page 495 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number v5PhysCChanCan Interface Information v5IntfId, v5VariantId, The V5 Interfaces variants tBeDeletedWhen- Event, 191...
  • Page 496 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number vbrAtmPvcVc- Connec- Response vbrAtmPvcVccIfA, The PVC VCC connection cReqFailNotify tion Event,...
  • Page 497 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number vbrAtm- Connec- Response vbrAtmSpvcVccIfA, An SPVC connection SpvcVccSetUpNo- tion Event,...
  • Page 498 Appendix Viewing Trap Log Information Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number viprIpIntfTrap Interface Information viprSlot, viprRouterId, The success or failure of IP Event, 48 viprIntfId, ipIntfStatus...
  • Page 499: Definitions Of Mib Objects Used For Trap Messages

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-2. SNMP Trap Names and Descriptions with Associated MIB Object Names (Continued) Trap Group System Enterprise-Specific Indicator for MIB Object Name Trap Description Trap Name Trap Index the Trap Number virtualUNIIntf- Interface Response...
  • Page 500 Appendix Definitions of MIB Objects Used for Trap Messages Table A-3. AAL2 Configure Failure Codes (Continued) Number Enumerated Type Description Value vccIdError The VCC ID for the trunk is 0,or this VCC ID is out of range. cidError The CID for the trunk or this VCC ID is out of range or used by someone else.
  • Page 501: Active Stratum Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - aal2VbrAtmSpvcVccEntry, aal2VbrAtmSpvcVccConfiguredNotify, aal2VbrAtmSpvcVccConfigFailNotify, aal2VbrAtmSpvcDeletedNotify, aal2VbrAtmSpvcVccSetUpNotify activeStratum The current status of the backup Stratum module. Valid range is a number between 1 and 2. See Table A-4 for a mapping between numbers and their enumerated type. Associated Traps - stratumActivitySwitchOverNotify Table A-4.
  • Page 502: Aps Failure Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages apsFailureReasonCode APS failure reason. Valid range is a number between 1 and 10. See Table A-6 for a mapping between numbers and their enumerated type. Associated Traps - apsConfigurationModifyFailNotify Table A-6. APS Failure Reason Codes Number Enumerated Type Description...
  • Page 503 Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - atmAtmSpvcVccSetUpNotify, atmAtmSpvcVccTearDownNotify atmAtmSpvcVccVciA The VCI value for side A of an ATM SPVC VCC connection. Valid range is a number between 0 and 65535. Associated Traps - atmAtmSpvcConfiguredNotify, atmAtmSpvcConfigFailNotify, atmAtmSpvcDe- letedNotify, atmAtmSpvcModifiedNotify, atmAtmSpvcModifyFailNotify, atmAtmSpvcVccSetUp- Notify, atmAtmSpvcVccTearDownNotify atmAtmSpvcVccVciB...
  • Page 504: Atm Ima Interface Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages atmAtmSpvcVpcVpiA The VPI value for side A of an ATM SPVC VPC connection. Valid range is a number between 0 and 4095. Associated Traps - atmAtmSpvpConfiguredNotify, atmAtmSpvpConfigFailNotify, atmAtmSpvp- DeletedNotify, atmAtmSpvpModifiedNotify, atmAtmSpvpModifyFailNotify atmImaIntfIndex Interface index for the ATM IMA interface.
  • Page 505 Appendix Definitions of MIB Objects Used for Trap Messages atmPvcVccVciA VCI value for side A of an ATM-to-ATM PVC VCC connection. Valid range is a number between 0 and 65535. Associated Traps - atmPvcVccReqFailNotify, atmPvcVccSetupNotify, atmPvcVccTearDownNotify, atmBkPvcVccReqFailNotify, atmBkPvcVccSetupNotify, atmBkPvcVccTearDownNotify atmPvcVccVciB The VCI value for side B of an ATM-to-ATM PVC VCC connection.
  • Page 506 Appendix Definitions of MIB Objects Used for Trap Messages atmPvcVpcVpiB The VPI value for side B of an ATM-to-ATM PVC VPC connection. Valid range is a number between 0 and 4095. Associated Traps - atmPvcVpcReqFailNotify, atmPvcVpcSetupNotify, atmPvcVpcTearDownNotify, atmBkPvcVpcReqFailNotify, atmBkPvcVpcSetupNotify, atmBkPvcVpcTearDownNotify atmSpvcVccIfA Interface index for side A of an ATM SPVC VCC connection.
  • Page 507: Atm Trunking Configuration Failure Codes

    Appendix Definitions of MIB Objects Used for Trap Messages atmTrunkingBrVccId The ID of the AAL2 Bear VCC. Associated Traps - atmTrunkingBrVccConfiguredNotify, atmTrunkingBrVccTearDownNotify, atmTrunkingBrVccSetUpNotify, atmTrunkingBrVccDeletedNotify atmTrunkingBrVccRmtIWFId The IWF ID for the remote IWF. Associated Traps - atmTrunkingBrVccConfiguredNotify, atmTrunkingBrVccTearDownNotify, atmTrunkingBrVccSetUpNotify, atmTrunkingBrVccDeletedNotify atmTrunkingConfigFailureCode An identified reason for failure while configuring or modifying ATM Trunking parameters.
  • Page 508 Appendix Definitions of MIB Objects Used for Trap Messages Table A-9. ATM Trunking Configuration Failure Codes (Continued) Number Enumerated Type Description Value vccTrunkParameterNotValid The parameters for the Trunk is not supported, includ- ing BrVccMaxAal2ChanId, BrVccCircuitModeData- Supp, BrVccFrameModeSupp, BrVccFaxModeSupp, CASPktXportSupp, BrVccDTMFPktXportSupp, BrVccMFR1PktXportSupp, BrVccMFR2PktXportSupp, BrVccPCMEncoding, BrVccMaxFrameLength, BrVc- cIdleChannSuprSupp, BrVccSilenceDetSupp, BrVc-...
  • Page 509 Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - atmTrunkingRemoteIWFConfiguredNotify, atmTrunkingRemoteIWFConfig- FailNotify, atmTrunkingRemoteIWFDeletedNotify, atmTrunkingRemoteIWFModifiedNotify, atmTrunkingRemoteIWFModifyFailNotify atmTrunkingSigVccIdentifier The VCC ID assigned by the owner of this signalling VCC. Associated Traps - atmTrunkingSigVccSetUpNotify, atmTrunkingSigVccTearDownNotify, atmTrunkingSigVccConfiguredNotify, atmTrunkingSigVccConfigFailNotify, atmTrunkingSigVc- cDeletedNotify atmTrunkingSigVccRmtIWFIdentifier The IWF ID for the remote IWF.
  • Page 510 Appendix Definitions of MIB Objects Used for Trap Messages bridgeAtmPvcVccVciB The VCI value for side B, the ATM side, of a Bridge-to-ATM PVC VCC connection. Valid range is a number between 0 and 65535. Associated Traps - bridgeAtmPvcVccReqFailNotify, bridgeAtmPvcVccSetupNotify, bridgeAt- mPvcVccTearDownNotify, bridgeAtmBkPvcVccReqFailNotify, bridgeAtmBkPvcVccSetupNotify, bridgeAtmBkPvcVccTearDownNotify bridgeAtmPvcVccVpiB...
  • Page 511: Module Operational Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - cardInsertionNotify Table A-10. Module Operational Status Codes Number Enumerated Type Description Value primary For an I/O module, it is primary if configured. For the CPU, it is the principal CPU.
  • Page 512 Appendix Definitions of MIB Objects Used for Trap Messages Table A-12. Module Type Codes (Continued) Number Enumerated Type Description Value highSpeed High-Speed Serial Interface module mSerial Multiserial Interface module dSP1 DSP1 Voice Server tWStation 2-Wire station tWOffice 2-Wire office Central Processing Unit module stratum Stratum 3–4 module pwrSupply...
  • Page 513 Appendix Definitions of MIB Objects Used for Trap Messages Table A-12. Module Type Codes (Continued) Number Enumerated Type Description Value hD-DS1 High-Density DS1 dS3-IMA DS3 IMA dSP2C DSP2C Voice Server tasm Tones and Announcements Server module mD-DS1 Medium-Density DS1 quadSerial Quadserial Interface module mD-DS1-IMA Medium-Density DS1 IMA...
  • Page 514: Chassis Over Temperature Alarm Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages number between 0 and 1023. If the I/O module interface is circuit emulation, then this will always be 0. Associated Traps - cellTestReqFailNotify cellTestVpiB The VPI value for testing cell transfer to an I/O module. Valid range is a number between 0 and 4095.
  • Page 515 Appendix Definitions of MIB Objects Used for Trap Messages cirEmAtmPvcVccIfA Interface index for side A, the circuit emulation side, of a circuit emulation-to-ATM PVC VCC connection. Number value is interpreted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel number.
  • Page 516: Firmware Download Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages cirEmAtmSpvcVccVpiB The VPI value for side B, the ATM side, of a circuit emulation-to-ATM SPVC VCC connection. Valid range is a number between 0 and 4095. Associated Traps - cirEmAtmSpvcVccSetUpNotify, cirEmAtmSpvcVccTearDownNotify cirEmCirEmPvcIfA Interface index for side A of a circuit emulation-to-circuit emulation PVC connection.
  • Page 517 Appendix Definitions of MIB Objects Used for Trap Messages Table A-14. Firmware Download Reason Codes (Continued) Number Enumerated Type Description Value driverInvalidrecordChecksum The firmware driver file is corrupted (invalid record checksum). requestReplyTimeout Failure to communicate with the I/O module. (request timeout). completeReplyTimeout Failure to communicate with the I/O module.
  • Page 518 Appendix Definitions of MIB Objects Used for Trap Messages frAtmPvcVccVciB The VCI value for side B, the ATM side, of a frame relay-to-ATM PVC VCC connection. Valid range is a number between 0 and 65535. Associated Traps - frAtmPvcVccReqFailNotify, frAtmPvcVccSetupNotify, frAtmPvcVccTearDown- Notify, frAtmBkPvcVccReqFailNotify, frAtmBkPvcVccSetupNotify, frAtmBkPvcVccTearDownNo- tify frAtmPvcVccVpiB...
  • Page 519: Lmi Operational Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - frFrPvcReqFailNotify, frFrPvcSetupNotify, frFrPvcTearDownNotify frFrPvcIfA Interface index for side A of a frame relay-to-frame relay PVC connection. Number value is inter- preted as an interface of the form, SSPPCCC, where SS is the module slot, PP is the port number, and CCC is the channel number.
  • Page 520: Gr-303 Interface Group Backup Eoc Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify, gr303Aal2PvcTearDownNotify gr303Aal2PvcVccVpiB The VPI value for side B (the ATM side) of a circuit emulation-ATM PVC VCC connection. Valid range is a number between 0 and 4095. Associated Traps - gr303Aal2PvcConfigReqFailNotify, gr303Aal2PvcSetUpNotify, gr303Aal2PvcTearDownNotify gr303Aal2PvcVccVciB...
  • Page 521: Gr-303 Interface Group Backup Tmc Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages gr303IgBackupTMCStatus Backup TMC channel Status. A null value (5) indicates that the backup TMC has not been config- ured. Valid range is a number between 1 and 5. See Table A-17 for a mapping between numbers and their enumerated type. Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify, gr303PPSCommandFailNotify Table A-17.
  • Page 522: Gr-303 Interface Group Primary Tmc Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages gr303IgPrimaryTMCStatus Primary TMC channel status. Valid range is a number between 1 and 4. See Table A-19 for a mapping between numbers and their enumerated type. Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify, gr303PPSCommandFailNotify Table A-19.
  • Page 523: Gr-303 Pps Source Codes

    Appendix Definitions of MIB Objects Used for Trap Messages gr303PPSSource Indicates the initiator of the PPS switching. Valid range is a number between 1 and 6. See Table A-21 for a mapping between numbers and their enumerated type. Associated Traps - gr303PPSStateChangeNotify, gr303PPSSwitchoverNotify, gr303PPSCommandFailNotify Table A-21.
  • Page 524: Ima Grp Channel Failure Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-22. IMA GRP Channel End State Codes (Continued) Number Enumerated Type Description Value insufficientLinks There are fewer active transmit or receive links than the associated group configuration parameter. blocked The IMA group has been administratively taken out of service.
  • Page 525: Ima Group Channel Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - imaGroupStatusChangeNotify Table A-24. IMA GRP Channel End State Codes Number Enumerated Type Description Value notConfigured This interface is not configured as an IMA group. startUp This end is in a state of start-up. startUpAck The IMA group has received and accepted the configu- ration parameters of the far-end.
  • Page 526: Ima Grp Channel Symmetry Codes

    Appendix Definitions of MIB Objects Used for Trap Messages imaGrpChannelSymmetry The symmetry of the IMA group. The default value is symOperation. Valid range is a number between 1 and 3. See Table A-26 for a mapping between numbers and their enumerated type. Associated Traps - imaGroupStatusChangeNotify Table A-26.
  • Page 527 Appendix Definitions of MIB Objects Used for Trap Messages Table A-27. Interface Failure Reason Codes (Continued) Number Enumerated Type Description Value t1SigEnableInterfaceNotSupported The interface is not supported if T1 signaling is enabled ts16ForData. ts16ForData ts16 has been set for passing data and the user is attempting to turn on signaling.
  • Page 528 Appendix Definitions of MIB Objects Used for Trap Messages Table A-27. Interface Failure Reason Codes (Continued) Number Enumerated Type Description Value failure-at-call-handler An interface creation failure occurred due to the call handler. unstructuredCE-payloadloop Unstructured CE should not have payload loop- back as a loop back option.
  • Page 529 Appendix Definitions of MIB Objects Used for Trap Messages Table A-27. Interface Failure Reason Codes (Continued) Number Enumerated Type Description Value vISuppConnTrafficShapingMutuallyEx- The VI support flag and traffic shaping flag are clusive mutually exclusive. tS16onPortNotCAS Must have CAS on port for the channel to have a CAS trunk line interface.
  • Page 530 Appendix Definitions of MIB Objects Used for Trap Messages Table A-27. Interface Failure Reason Codes (Continued) Number Enumerated Type Description Value backupTMC-EOCIntfShouldBeSame The backup timeslot management channel and embedded operation channel interfaces should be the same. backupEOCIntfCantBeChanged The backup embedded operation channel inter- face cannot be changed.
  • Page 531 Appendix Definitions of MIB Objects Used for Trap Messages Table A-27. Interface Failure Reason Codes (Continued) Number Enumerated Type Description Value v5IntfPhysCChanAlreadyExists V5 Interface physical C Channel already exists. The same physical C Channel cannot be added in the interface. v5IntfPhysCChanCantBeZero Physical C Channel ID cannot be set to 0.
  • Page 532: Interface Type Codes

    Appendix Definitions of MIB Objects Used for Trap Messages vbrSpvcConfiguredNotify, vbrSpvcConfigFailNotify, vbrSpvcDeletedNotify, vbrSpvcModifiedNo- tify, vbrSpvcModifyFailNotify, pnniProtLnkUpAndAdv, pnniProtLinkUpAndNotAdv, pnniPro- tLnkStatDown, pnniIntfCfgFailNotify, atmSvcIntfLayer2Up, atmSvcIntfLayer2Down, inter- faceCreateFailNotify, gr303TMCChanDownNotify, gr303EOCChanDownNotify, gr303TMCChanUpNotify, gr303EOCChanUpNotify, interfaceBandwidthChangeNotify, lmiDl- ciStatusNotify, dhpvcChangeNotify interfaceType Interface type used for identification in traps. A specific interface is associated with each number. Valid range is a number between 1 and 23.
  • Page 533 Appendix Definitions of MIB Objects Used for Trap Messages Table A-28. Interface Type Codes (Continued) Number Enumerated Type Description Value casTrunkLine Channel Associated Signaling Trunk Line Interface toneAnnce Tone Announcement Interface gr303 GR-303 ipAddrNumber The IP address of the host/network to be echoed. Associated Traps - viprPingTrap ipAtmAppPvcVccDestAddrA The destination IP address of an in-band management-ATM connection.
  • Page 534: Ip Interface Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages ipIntfStatus Return codes for the Route Server module’s IP interface operations. Valid range is a number between 1 and 24. See Table A-29 for a mapping between numbers and their enumerated type. Associated Traps - viprIpIntfTrap Table A-29.
  • Page 535: Ipt Result Codes

    Appendix Definitions of MIB Objects Used for Trap Messages iptResultCode Various result codes for the operator’s command for setting/deleting an interface protection group. Valid range is a number between 1 and 9. See Table A-30 for a mapping between numbers and their enumerated type. Associated Traps - iptResultNotify Table A-30.
  • Page 536 Appendix Definitions of MIB Objects Used for Trap Messages Table A-31. IP Type Reason Codes (Continued) Number Enumerated Type Description Value siteRemoteMgrAddr5 Remote manager IP Address 5, where the trap will be sent. inBandPrimaryIpAddress IP address of the switch when the switch is accessed over the primary in-band connection.
  • Page 537: Iua Application Server Process State Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-31. IP Type Reason Codes (Continued) Number Enumerated Type Description Value siteGatewayInbandAddrClash The newly configured gateway IP address is the same as the inband IP address, which is incor- rect. unableToApplyGatewayIpAddr Unable to apply the Gateway IP address.
  • Page 538: Iua Association State Codes

    Appendix Definitions of MIB Objects Used for Trap Messages iuaAspEpAssocId Association Identification. Value identifying the association for that endpoint. This value is extracted from the SCTP association Id value returned by SCTP when the association is estab- lished to that endpoint. Associated Traps - iuaSctpStateChangeNotify iuaAspEpAssocState The state of this SCTP association.
  • Page 539: Iua Heartbeat Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-35. IUA Heartbeat Codes Number Enumerated Type Description Value Heartbeat is enabled. Heartbeat is disabled. No BEAT messages are sent but BEAT messages received are responded. iuaLocalPort Identifies the port of the IUA service. The SCTP Registered User Port Number Assignment for IUA is 9900.
  • Page 540: Enhanced Ds1 Line Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages The following bit map table shows line statuses for the DS1/T1 and Enhanced DS1 modules: Table A-37. Enhanced DS1 Line Status Codes Bit Value Alarm Description dsx1NoAlarm No alarm present dsx1RcvFarEndLOF Far-end LOF (that is, yellow alarm) dsx1XmtFarEndLOF Near-end sending LOF indication...
  • Page 541: A-40 2-Port Ds3 Atm Module Line Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-39. DS1 Line Status Alarms Bit Value Alarm Description RcvAIS Far-end sending AIS (red alarm) XmtAIS Near-end sending AIS LossOfFrame Near-end LOF LossOfSignal Near-end loss of signal LoopbackState Near-end is looped T16AIS E1 TS16 AIS (not valid for DS1) RcvFarEndLOMF...
  • Page 542: Enhanced E1 Line Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-40. 2-Port DS3 ATM Module Line Status Codes (Continued) Bit Value Alarm Description 2048 dsx3RcvRmtOOF Receiving FEAC OOF code from remote. The far-end device has sent an FEAC OOF code to the PSAX system to indicate that the far-end device has detected an OOF condition on its receiving port.
  • Page 543: A-42 2-Port E3 Atm Module Line Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-41. Enhanced E1 Line Status Codes Bit Value Alarm Description e1LossOfSignal Near-end loss of signal e1LoopbackState Near-end is looped e1T16AIS E1 TS16 AIS e1RcvFarEndLOMF Far-end sending TS16 LOMF 1024 e1XmtFarEndLOMF Near-end sending TS16 LOMF 2048 e1RcvTestCode...
  • Page 544: Ethernet Module Line Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-42. 2-Port E3 ATM Module Line Status Codes (Continued) Bit Value Alarm Description 8192 dsx3RcvRmtIdle The PSAX system detected a DS3 idle signal on its receiving port. If the Cell Mapping field on the DS3 Port and Channel Configu- ration window for this port is set to Plcp, the PSAX system: Displays the values RcvRmtIdle and RcvLCD in the Line Sta- tus field...
  • Page 545: Optical Modules Line Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-43. Ethernet Module Line Status Codes Bit Value Line Status Description 10baseT-HalfDuplex Indicates the line status that was auto-negotiated or preconfigured for this port. The line speed is 10 Mbps and the line is half duplex, which means that the port can only send or receive data during a given time period.
  • Page 546: Voice 2 Wire Office And Voice 2 Wire Station Line Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages The following bit map table shows line status messages for the module: Table A-45. Voice 2 Wire Office and Voice 2 Wire Station Line Status Codes Bit Value Alarm Description NoAlarm No alarm present SignalingFailureState Signals failure state...
  • Page 547: Ntom Protection Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - ntomProtectionSwitchoverNotify, ntomProtectionGroupCreateFailNotify, ntomProtectionGroupModifyFailNotify, ntomProtectionGroupSlotAdd, ntomProtection- GroupSlotRemove, ntomProtectionSlotModifyFail Table A-47. ntom Protection Reason Codes Number Enumerated Type Description Value ntomSwitchProtectionToActive The protection module has switched to active. ntomSwitchProtectionToStandby The protection module has switched to standby. ntomMoreThan1SlotInOneToOneCo More than 1 slot is being configured in the one to nfig...
  • Page 548: Oam Activation Deactivation Result Codes

    Appendix Definitions of MIB Objects Used for Trap Messages oamActDeactVciB The VCI value for OAM CC connection. Valid range is a number between 0 and 65535. Associated Traps - oamActDeactResultNotify oamActDeactVpiB The VPI value for an OAM CC connection. Valid range is a number between 0 and 4095. Associated Traps - oamActDeactResultNotify oamActDeactResultCode Various result codes for the operator’s command for OAM Activation-Deactivation.
  • Page 549 Appendix Definitions of MIB Objects Used for Trap Messages Table A-48. OAM Activation Deactivation Result Codes (Continued) Number Enumerated Type Description Value eteCCDeactDeniedTowardsNearEnd The end-to-end continuity check deactivation request sent toward the near-end is denied. eteCCDeactDeniedTowardsBothEnd The end-to-end continuity check deactivation request toward both ends is denied.
  • Page 550 Appendix Definitions of MIB Objects Used for Trap Messages Table A-48. OAM Activation Deactivation Result Codes (Continued) Number Enumerated Type Description Value oamActDeactInvalidIntf Slot, port, channel, VP, VCI-This interface is not valid. oamNotSupportedForThisConnection This connection is not OAM supported. oamCCnotSupportedForThisConnec- This connection is not OAM CC supported.
  • Page 551 Appendix Definitions of MIB Objects Used for Trap Messages Table A-48. OAM Activation Deactivation Result Codes (Continued) Number Enumerated Type Description Value etePMDeactSuccTowardsFarEnd The end-to-end performance monitoring deacti- vation request was successfully sent toward the far-end. etePMDeactSuccTowardsNearEnd The end-to-end performance monitoring deacti- vation request was successfully sent toward the near-end.
  • Page 552 Appendix Definitions of MIB Objects Used for Trap Messages Table A-48. OAM Activation Deactivation Result Codes (Continued) Number Enumerated Type Description Value etePMBRDeactSuccTowardsBothEnd The end-to-end performance monitoring/back- ward reporting deactivation request was success- fully sent toward both ends. segPMActSuccTowardsFarEnd The segment performance monitoring activation request was successfully sent toward the far-end.
  • Page 553 Appendix Definitions of MIB Objects Used for Trap Messages Table A-48. OAM Activation Deactivation Result Codes (Continued) Number Enumerated Type Description Value segPMBRActDeniedTowardsNearEnd The segment performance monitoring/backward reporting activation request sent toward the near- end is denied. segPMBRActDeniedTowardsBothEnd The segment performance monitoring/backward reporting activation request sent toward both ends is denied.
  • Page 554: Oam Test Failure Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - oamTestReqFailNotify Table A-49. OAM Test Failure Reason Codes Number Enumerated Type Description Value invalidSPCforOAM There is no such slot/port/channel in this box. invalidIntfForOAM There is no such interface that OAM enabled. invalidLocationLength The length of the Loopback Location ID is not valid.
  • Page 555: Oc-3C Aps Protection Line Signal Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - oc3APSStateChangeNotify, oc3APSSwitchoverNotify Table A-50. OC-3c APS Protection Line Signal Status Codes Number Enumerated Type Description Value noAlarm no alarm signalDegradation signal bit error rate is higher than the specified threshold signalFailure signal bit error rate is much higher than the specified threshold...
  • Page 556 Appendix Definitions of MIB Objects Used for Trap Messages Table A-51. OC-3c APS Reason Codes (Continued) Number Enumerated Type Description Value localprotectSF A signal failure occurred at the near- end protec- tion port. localprotectForced A forced switchover occurred at the near-end protection port.
  • Page 557: Oc-3C Aps Selector State Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-51. OC-3c APS Reason Codes (Continued) Number Enumerated Type Description Value remoteworkingSD A signal degradation occurred at the far-end working port. remoteworkingSF A signal failure occurred at the far-end working port.
  • Page 558: Pgt Result Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-53. OC-3c APS Working Line Signal Status Codes (Continued) Number Enumerated Type Description Value 2048 lineLoopBack port is in line loop back state 4096 protocolFailure protocol failure 8192 adminOutOfService The interface is administratively out of service. 16384 lrdi receiving Line RDI 32768 prdi...
  • Page 559: Ping Status Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-54. PGT Result Codes (Continued) Number Enumerated Type Description Value interfaceProtectionpgtFailedSwichOver Interface protection failed switched over. interfaceProtectionpgtFailedSwichBack Interface protection failed switched back. interfaceProtectionpgtInvalidConfiguation The interface protection configuration is not valid. pingStatusReasonCode The response value - Alive/Not Alive.
  • Page 560: Port Failure Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-56. PNNI Codes (Continued) Number Enumerated Type Description Value pnniATMAddrInvInNodeId ATM address entered in node ID is not valid pnniATMAddrInvInPGId ATM address entered in peer group ID is not valid pnniIntfAdmStatNotDel PNNI interface administrative status not deleted pnniNodeAdmStatUp...
  • Page 561: Power Supply Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages powerSupplyReasonCode Identification for a change in the status of a power supply. Valid range is a number between 1 and See Table A-58 for a mapping between numbers and their enumerated type. Associated Traps - powerSupplyStatusNotify Table A-58.
  • Page 562: Pvc Failure Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages ipAtmBkAppPvcVccReqFailNotify, aal2TrunkConfigReqFailNotify, dhpvcChangeNotify Table A-59. PVC Failure Reason Codes Number Enumerated Type Description Value vpiVciUnavailableA2B The virtual path identifier and virtual channel identi- fier are unavailable in the direction of A2B. vpiVciUnavailableB2A The virtual path identifier and virtual channel identi- fier are unavailable in the direction of B2A.
  • Page 563 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value vcGreaterThanVcMaxIgrsA2B The virtual channel is greater than the virtual chan- nel identifier maximum on the ingress side of the A2B direction of the connection.
  • Page 564 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value vpGreaterThanVpMaxIispIgrsB2A The virtual path value is greater than the allowed upper limit for NNI interfaces. The error is in the input side of the B2A direction of the connection.
  • Page 565 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value vpiInReservedListA2B The currently configured virtual path identifier is present in the reserved list of the A side of the A2B direction of the connection.
  • Page 566 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value vpiVciInReservedListB2A The virtual path identifier/virtual channel identifier used is already present in the reserved list for some other connection. The error is in the input side of B2A direction.
  • Page 567 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value connectionsUnavailableInModuleB The connections are unavailable in the module in the B2A direction. scrBandwidthUnavailableIgrsA2B The sustained cell rate bandwidth is unavailable on the ingress side of the A2B direction of the connec- tion.
  • Page 568 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value dlciFoundInReleasedList The data link connection identifier is found in the released list. invalidDlci The data link connection identifier is not valid. slotA-OutOfRange Slot A is out of range.
  • Page 569: Frame Relay

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value unrecognizableSarTypeA2B The SAR (segmentation and reassembly) type is not supported for this connection in the A2B direction. unrecognizableSarTypeB2A The SAR (segmentation and reassembly) type is not supported for this connection in the B2A direction.
  • Page 570 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value interfaceA-InTerminalEmulation- The interface attached to the slot, port, or channel on PvcList the A side is already present in the terminal emula- tion PVC list for another connection.
  • Page 571 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value interfaceB-InTerminalEmulation- The interface attached to the slot, port, or channel on ReleasedList the B side is already present in the hdlc terminal emulation released list for another connection.
  • Page 572 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value ipDestAddrSubnetAInPvcList Used for Inband Management Connections. The IP address is already used for another connection in the PVC list. This is for the A side. ipDestAddrSubnetAInReleasedList Used for Inband Management Connections.
  • Page 573 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value interfaceBInBridgeReleasedList The interface associated with the slot, port, or chan- nel is already present in the released list and is cur- rently in use.
  • Page 574 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value beNotValidA2B The excess burst size is too small if the committed burst and committed information rate is zero. This is in reference to the A2B direction.
  • Page 575 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value dspUnsupportedForMultiCast- DSP support is not available for multicast connec- Conns tions. dspResourceUnavailable DSP resources are not available for the connection configuration given by the user.
  • Page 576 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value vi-OOR-A The requested VI number is out of range for simplex connections (Side A). vi-OOR-B The requested VI number is out of range for simplex connections (Side B).
  • Page 577 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value vuni-Already-Exists The virtual UNI already exists. vuni-Does-Not-Exist The virtual UNI does not exist. vuni-Does-Not-Match-vi If VI is enabled at the main interface level and if the VUNI is non-zero the VI value and VUNI value should match.
  • Page 578 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value stdAal2CIDAlreadyInUse AAL2 CID is already in use. stdAal2TrunkBWUavailableEgrs Bandwidth at the trunk level is not available on the output side. stdAal2TrunkBWUavailableIgrs Bandwidth at the trunk level is not available on the input side.
  • Page 579 Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value dhpvcState-Prim-Act-NoFail- This is not an error trap. This is an informational trap Bkup-Pass-Fail to indicate that the DHPVC has had a change in state but does not result in a switchover.
  • Page 580: Remote Database Operation Error Status

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-59. PVC Failure Reason Codes (Continued) Number Enumerated Type Description Value numRsvChannelsAlreadyUsed This is used when the user has configured the numD- spRsvChannels to be non-zero and have used up to the limit which was reserved.
  • Page 581: Remote Reboot Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages remoteRebootReason Code The result of a remote reboot request. Valid range is a number between 1 and 47. See Table A-62 for a mapping between numbers and their enumerated type. Associated Traps - remoteRebootNotify Table A-62.
  • Page 582 Appendix Definitions of MIB Objects Used for Trap Messages Table A-62. Remote Reboot Reason Codes (Continued) Number Enumerated Type Description Value ioCard10Reboot-NoCardInSlot The I/O module reboot did not occur. No module is present in slot 10. ioCard11Reboot-NoCardInSlot The I/O module reboot did not occur. No module is present in slot 11.
  • Page 583: Remove Configuration Files Codes

    Appendix Definitions of MIB Objects Used for Trap Messages removeConfigFiles Indicates the status of a remove configuration files request. Valid range is a number between 1 and 4. See Table A-63 for a mapping between numbers and their enumerated type. Associated Traps - removeConfigFilesNotify Table A-63.
  • Page 584: Sapphire Interface Address Fail Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages See Table A-65 for a mapping between numbers and their enumerated type. Associated Traps - sapphireInterfaceAddressAssignFailNotify Table A-65. Sapphire Interface Address Fail Reason Codes Number Enumerated Type Description Value address-assign-ok Address assignment succeeded. fail-Ilegal-IP-address Illegal IP address assigned address does not match.
  • Page 585: Spvc Configuration Failure Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-66. Save Configuration Reason Codes (Continued) Number Enumerated Type Description Value fail-backupCpuInitializationIn- Save operation failed due to ongoing secondary CPU Progress initialization. expect2ndCPURebootAfterSave Notification to expect reboot of secondary CPU after a save operation.
  • Page 586 Appendix Definitions of MIB Objects Used for Trap Messages Table A-67. SPVC Configuration Failure Codes (Continued) Number Enumerated Type Description Value interfaceNotConfiguredAsRe- While configuring it as SPVC endpoint, this interface is quired not as desired (e.g., it is not CE, while trying to configure CES SPVC).
  • Page 587: Static Route Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - viprStatRtTrap Table A-68. Static Route Codes Number Enumerated Type Description Value statRtOk Static route OK statRtIntFailure Memory corruption statRtMany Too many static routes statRtSlot Impossible slot ID statRtBadId Bad VPN ID statRtBadState State machine confusion...
  • Page 588: Stratum Configuration Modification Failure Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-69. Stratum Configuration Modification Failure Reason Codes Number Enumerated Type Description Value unSupportedOption The option or configuration is not supported. onlyCompositeClockDS0aAllowed- When a DS0A module is configured, the only AsDS0aCardIsConfigured option for stratum sync source is compositeClockDS0A.
  • Page 589: Switch Alarm Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-71. Subchannel Status Codes (Continued) Number Enumerated Type Description Value scBadId Bad VPN ID scBadState State machine confusion scBadTimerVal Bad timer value: state machine scExists Subchannel already exists scCantFind Unused scDelInProgress Deleting: must wait scLockedIdle...
  • Page 590: Switch Fan Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages See Table A-73 for a mapping between numbers and their enumerated type. Associated Traps - switchFanStatusChangeNotify Table A-73. Switch Fan Status Codes Number Enumerated Type Description Value notAvailable The fan status could not be retrieved. alarmSet The status on the Fan/Alarm module if any of the fans are not spinning.
  • Page 591: Tas Module Continuity Check Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - tasContinuityCheckNotify Table A-75. TAS Module Continuity Check Reason Codes Number Enumerated Type Description Value cc-success Continuity check request has been successfully done. cc-Fail-equipment-Fail Slot, port, channel, VPI, VCI are not in the range. cc-Fail-connections-Fail The TASM connection ID is not valid.
  • Page 592: Tas Module Memory Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages tasMemReasonCode The result of a memory initialization request. Valid range is a number between 1 and 2. See Table A-78 for a mapping between numbers and their enumerated type. Associated Traps - tasMemNotify Table A-78.
  • Page 593: Timing Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - bridgeDomainTimingRelationshipNotify Table A-80. Timing Reason Codes Number Enumerated Type Description Value invalidForwardDelay-MaxAge In violation of: 2 * (BridgeForwardDelay - 1.0 sec) >= BridgeMaxAge invalidHelloTime-MaxAge In violation of: BridgeMaxAge >= 2 * (BridgeHelloTime + 1.0 sec toneAnnceFtpErrorStatus The result of the completion of the tone announcement download.
  • Page 594: Tone Announcement Ftp Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages toneAnnceFtpStatus The current status of the tone announcement download. The initial start state from boot-up is noActivity. During the FTP of the announcement, working is set. The final state is one of done- Successfully, doneWithError, or aborted.
  • Page 595: Upgrade Software Error Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-84. Upgrade Software Error Status Codes Number Enumerated Type Description Value none No errors occurred. userAbort User canceled invalidIpAddress The Ip address is not valid. invalidAccountName The Account name is not valid. invalidAccountPassword The Account password is not valid.
  • Page 596: V5 Data Link Communication Path Id Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Table A-85. V5 Data Link Communication Path ID Codes Number Enumerated Type Description Value v5DLCPathProtection1 This data link communication path refers to PROTECTION1 DL protocol. v5DLCPathProtection2 This data link communication path refers to PROTECTION2 DL protocol.
  • Page 597: V5 Interface User Port Type Codes

    Appendix Definitions of MIB Objects Used for Trap Messages v5IntfUserPortLEPortId LE port number used to identify the ISDN and PSTN ports on a v5 interface. Associated Traps - v5InterfaceUserPortAddedNotify, v5InterfaceUserPortAddFailNotify, v5InterfaceUserPortDeleteNotify, v5InterfaceUserPortBlockedNotify, v5InterfaceUserPortUnBlockedNotify, v5InterfaceUserPortUnblockDeactNotify, v5InterfaceUserPortActivatedNotify, v5InterfaceUserPortActivationInitiatedNotify v5IntfUserPortType Port type used to identify whether this port is ISDN or PSTN in a v5 interface. Valid range is a number between1 and 2.
  • Page 598 Appendix Definitions of MIB Objects Used for Trap Messages v5VariantId This index identifies the variant table. Associated Traps - v5InterfaceVariantAddedNotify, v5InterfaceVariantAddFailNotify, v5InterfaceVariantDeleteNotify, v5InterfaceVariantOutOfServiceNotify, v5InterfaceVariantInServiceNotify, v5InterfaceE1LinkAddedNotify, v5InterfaceE1LinkAddFailNotify, v5InterfaceE1LinkDeleteNotify, v5InterfaceVariantSwitchoverNotify, v5InterfaceVariantSwitchoverFailed, v5InterfaceVariantModifyFailNotify, v5InterfaceE1LinkModifyFailNotify, v5InterfaceE1LinkBlockedNotify, v5InterfaceE1LinkUnBlockedNotify, v5InterfacePhysCChanCreatedNotify, v5InterfacePhysCChanCreateFailNotify, v5InterfacePhysCChanDeleteNotify, v5InterfaceLogCChanCreatedNotify, v5InterfaceLogCChanCreateFailNotify, v5InterfaceLogCChanDeleteNotify, v5InterfaceDLCreatedNotify, v5InterfaceDLCreateFailNotify, v5InterfaceDLDeleteNotify, v5InterfaceUserPortAddedNotify, v5InterfaceUserPortAddFailNotify, v5InterfaceUserPortDeleteNotify, v5E1LinkOperOutOfServiceNotify, v5E1LinkOperInServiceNotify, v5InterfaceUserPortBlockedNotify,...
  • Page 599 Appendix Definitions of MIB Objects Used for Trap Messages vbrAtmPvcVccVpiB The VPI value for side B, the ATM side, of a variable bit rate-to-ATM PVC VCC connection. Valid range is a number between 0 and 4095. Associated Traps - vbrAtmPvcVccReqFailNotify, vbrAtmPvcVccSetupNotify, vbrAtmPvcVccTear- DownNotify, vbrAtmBkPvcVccReqFailNotify, vbrAtmBkPvcVccSetupNotify, vbrAtmBkPvcVccTe- arDownNotify, vbrAtmSpvcIfB...
  • Page 600: Version Configuration Reason Codes

    Appendix Definitions of MIB Objects Used for Trap Messages vbrAtmSpvcVpiB The VPI value for side B, the ATM side, of a variable bit rate-to-ATM SPVC VCC connection. Valid range is a number between 0 and 4095. Associated Traps - vbrAtmSpvcSetUpNotify, vbrAtmSpvcTearDownNotify vbrVbrPvcIfA Interface index for side A of a variable bit rate-to-variable bit rate PVC connection.
  • Page 601 Appendix Definitions of MIB Objects Used for Trap Messages Table A-87. Version Configuration Reason Codes (Continued) Number Enumerated Type Description Value downgrade-sanityCheck-Completed The downgrade sanity check is completed. upgrade-Fail-SanityCheckFail The upgrade failed due to sanity check failure. downgrade-Fail-SanityCheckFail The downgrade failed due to sanity check fail- ure.
  • Page 602 Appendix Definitions of MIB Objects Used for Trap Messages viprRouterId A unique ID for the Router Instance in a router module. Associated Traps - viprPingTrap, viprArpTrap, viprRoutingTrap, viprVpnTrap, viprIpIntfTrap, vipr- SubChanTrap, viprStatRtTrap viprSlot The slot number of the Route Server module (SS). Associated Traps - viprPingTrap, viprArpTrap, viprRoutingTrap, viprVpnTrap, viprIpIntfTrap, vipr- SubChanTrap, viprStatRtTrap viprSubChnlId...
  • Page 603: Vpn Trap Status Codes

    Appendix Definitions of MIB Objects Used for Trap Messages Associated Traps - viprVpnTrap Table A-88. VPN Trap Status Codes Number Enumerated Type Description Value vpnAddOk VPN creation OK vpnInternalFailure Memory corruption failure vpnTooMany Exceeded maximum number of VPNs vpnBadSlot Impossible slot number vpnBadId VPN ID must be between 1-6 vpnBadState...
  • Page 604 Appendix Definitions of MIB Objects Used for Trap Messages ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 A-158 255-700-247...
  • Page 605: Console Connector Pin Assignments

    Pin Configurations Overview of This Appendix This appendix describes the connector pin assignments for the common equipment modules installed in the PSAX 1250 chassis. CONSOLE Connector CONSOLE connector on the CPU2 module accepts an RJ-12 connector. Pin assignments for the connector are listed in Table B-1.
  • Page 606: Ethernet Connector Pin Locations

    Appendix The CPU2 module faceplate also provides a 10Base-T Ethernet interface using an RJ-45 connector. Figure B-1 shows the pin locations for the ETHERNET connector on the faceplate of the module. 1 2 3 4 5 6 7 8 Figure B-1. ETHERNET Connector Pin Locations The CPU2 module ETHERNET connector does not follow the standard Ether-...
  • Page 607: Pin Assignments For The Rj-45 Connector On The Stratum 3-4 Module

    Appendix Configuration for the Stratum 3–4 Connector Table B-5. Pin Assignments for the RJ-45 Connector on the Stratum 3–4 Module Description IN (ring) IN (tip) Not Used Not Used Not Used Frame Ground Not Used Not Used ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 255-700-247...
  • Page 608 Appendix Configuration for the Stratum 3–4 Connector ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 255-700-247...
  • Page 609: Overview Of In-Band Management Configurations

    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 C-2) The management host connects over an ATM WAN directly to an I/O module port in a remote managed target (the PSAX system being man- aged).
  • Page 610: Using The Direct Connection Configuration

    Appendix Using the Direct Connection Configuration 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 C-1). Node E PSAX ATM PVC Connections...
  • Page 611: Setting Up Atm Arp Table Entries

    Appendix Using the Direct Connection Configuration ifconfig fa0 netmask broadcast forecard_Ip_Address Netmask Bcast_address Mtu_Size where, = the IP address of the FORE card (for exam- forecard_Ip_Address ple, 136.242.140.222) = the IP subnet mask (for example, 255.255.255.0) Netmask = the IP address of the broadcast server (for exam- Bcast_address ple, 136.242.140.255) = maximum transfer unit size [packet size] (for example,...
  • Page 612: Using The Routed Connection Configuration

    Appendix Using the Routed Connection Configuration VCI= 302 AAL= 5 Check whether the connections have been configured by using the com- mand atmarp -a 2 All the remote PSAX systems’ in-band interface IP addresses may or may not be in the same subnet as that of the FORE card’s IP address. 3 If the remote PSAX systems’...
  • Page 613: Setting Up Connections For A Routed Connection Configuration

    Appendix Using the Routed Connection Configuration Node E PSAX PSAX PSAX Node C Intermediate PSAX Router PSAX ATM PVC Node B Connections Intermediate PSAX Router PSAX Node D PSAX PSAX Node A PSAX Main Router PSAX Ethernet or ATM PSAX PVC Connections PSAX PSAX...
  • Page 614 Appendix Using the Routed Connection Configuration stream connections to either the router PSAX system or the end system PSAX system. This helps to form a simple tree structure (see Figure C-2 on page C-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.
  • Page 615: Setting Pvc Connections For Routed Connection Configuration

    Appendix Using the Routed Connection Configuration Setting PVC Connections for Routed Connection Configuration Assume that the VPI:VCI for the connection between node A and B is VPIab: VCIab, etc. Also assume that the Ethernet IP addresses of all nodes except node A do not lie in the NMS station’s network address range.
  • Page 616 Appendix Using the Routed Connection Configuration Connections downstream from Node C to subtrees will go directly to end-sys- tem 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.
  • Page 617 Appendix Using the Routed Connection Configuration 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 CPU module of Node A to DS3: For setting up an in-band connection from the DS3 module to the CPU mod- ule, configure the DS3 module and put it into service.
  • Page 618: Using The Hybrid Connection Configuration

    Appendix Using the Hybrid Connection Configuration Channel: 1 Slot: VPI: VPIceIP Address: 020.001.001.003 Slot Number Port:1VCI: VCIceIP Mask: 255.255.255.000 Channel: 1 Slot: VPI: VPIcfIP Address: 020.001.001.004 Slot Number Port:1VCI: VCIcfIP Mask: 255.255.255.000 Channel: 1 12 Set up in-band managment connections on the CPU module of Node E: Example: Slot: VPI: VPIceIP Address:...
  • Page 619: Setting Up Connections For Hybrid Connection Configuration

    Appendix Using the Hybrid Connection Configuration Node E PSAX ATM PVC Connections PSAX PSAX Node C PSAX PSAX Node B PSAX Remote PSAX PSAX Node D PSAX PSAX Node A PSAX Main Router PSAX Ethernet PSAX Connections PSAX PSAX PSAX ATM PVC Connections Physical Connections via Ethernet LAN Figure C-3.
  • Page 620 Appendix Using the Hybrid Connection Configuration 4 For all the PSAX systems except the main router PSAX system, the Ether- net interface IP network should be different from the SUN machine’s Ethernet interface IP network. 5 All of the NMS stations should be in the one IP network, but can be in different subnets connected to the main router PSAX system via Ethernet or OC3-ATM connections.
  • Page 621 Appendix Using the Hybrid Connection Configuration 2 Configure the primary and backup IP Address for in-band management on the CPU 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 CPU module of the main router PSAX system (Node C) using the console interface:...
  • Page 622 Appendix Using the Hybrid Connection Configuration Port:1VCI: VCIacIP Mask: 255.000.000.000 Channel: 1 Slot:Slot Number VPI: VPIadIP Address: 020.001.001.004 Port:1VCI: VCIadIP Mask: 255.000.000.000 Channel: 1 Slot:Slot Number VPI: VPIaeIP Address: 020.001.001.005 Port:1VCI: VCIaeIP Mask: 255.000.000.000 Channel: 1 7 Set up in-band management connections on the CPU module of each of the Nodes B,C,D,and E: Example: Node B...
  • Page 623: Atm Traffic Descriptors

    Reference Information Overview of This Appendix This appendix contains reference information that is helpful while configur- ing your PSAX system. The following types of information are provided: • ATM Traffic Descriptors • SPVC Connection Cause Codes for Connection Retry • Industry Compliance Specifications •...
  • Page 624 Chapter ATM Traffic Descriptors • 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 Multiservice Media Gateway might drop some or all cells during congestion.
  • Page 625 Chapter ATM UNI Specification Cause Codes, Version 3.1 ~ When the connection is configured for variable bit rate (VBR) traffic, the Multiservice Media Gateway 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 Multiservice Media Gateway tags all CLP=0 cells violating the value set for the PCR to CLP=1 in bucket 2.
  • Page 626 Chapter ATM UNI Specification Cause Codes, Version 3.1 Table D-1. Connection Cause Codes for SPVCs (Continued) Cause Prompts Referenced Description Code a Retry Standard Call was rejected. Although the equipment sending this cause ITU-T Q.850 code is neither busy nor incompatible, the equipment sending this cause code does not want to accept the call.
  • Page 627 Chapter ATM UNI Specification Cause Codes, Version 3.1 Table D-1. Connection Cause Codes for SPVCs (Continued) Cause Prompts Referenced Description Code a Retry Standard Access information was discarded. The network failed to ITU-T Q.850 deliver access information to the remote user (for example, user-to-user, low-layer compatibility, high-layer compatibil- ity, or subaddress).
  • Page 628 Chapter ATM UNI Specification Cause Codes, Version 3.1 Table D-1. Connection Cause Codes for SPVCs (Continued) Cause Prompts Referenced Description Code a Retry Standard Endpoint reference is not valid. The equipment sending this ATM Forum UNI cause code received a message with an endpoint reference 3.0/3.1 that is currently not in use on the user-network interface.
  • Page 629: Industry Compliance Specifications

    Chapter Industry Compliance Specifications Table D-1. Connection Cause Codes for SPVCs (Continued) Cause Prompts Referenced Description Code a Retry Standard 102 Recovery on timer expiration. A procedure has been initiated ITU-T Q.850 by the expiration of a timer that is related to error handling procedures.
  • Page 630 Chapter Industry Compliance Specifications Table D-2. 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, Multi-...
  • Page 631 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes ATM Maintenance Mode af-pnni-0055.000 SPVCs- Annex C: Soft PVC Procedures ATM PNNI 1.0 interface Private Network-Network Inter- for circuit emulation, frame face (PNNI) ETSI ISDN Support relay, and terminal emulation In-band Management SVC Soft Permanent Virtual Circuits...
  • Page 632: Circuit Emulation

    Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes Channelized DS3, Channelized af-uni-0010.001 STS-1e, DS1 IMA, DS3 IMA, E1 User-Network Interface (UNI) IMA, DS3 ATM, E3 ATM, Enhanced DS1, Enhanced E1,High-Density E1, High Speed, Medium-Density DS1, Multi-Serial, OC-3c Single- Mode/Multimode/APS, STM-1...
  • Page 633 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes Channelized DS3, Channelized af-vtoa-0085.000 STS-1e, and Enhanced DS1 (DBCES) Dynamic Bandwith modules Utilization in 64 Kbps Time Slot Trunking Over ATM—Using Cir- cuit Emulation Service (CES) •...
  • Page 634 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes 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 CSU/DSU loopback ANSI T1.403 Facsimile Demodulation/ Network-to-Customer Installa-...
  • Page 635 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes DS3 Frame Relay module CCITT G.704 Synchronous Frame Structures Used at Primary and Secondary Hierarchical Levels DSL Forum TR 017 ATM over ADSL Recommenda- tions Multi-serial and Quadserial EIA-232...
  • Page 636 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes ETSI 300 347-1 ITU-T G. 964 and G.965 are functionally equivalent to ETSI V5.2 Interface for the Support of EN 300 324-1 and ETSI EN 300 Access Network (AN) Part 1: 347-1 respectively.
  • Page 637 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes In-band Management FRF.8 Channelized DS3, Channelized Frame Relay ATM/PVC Service STS-1e, DS3 Frame Relay, Internetworking Implementa- Enhanced DS1, Enhanced E1, tion Agreement High-Density E1, Medium-Den- sity DS1, Multi-Serial, Quadse- rial, and Route Server modules PSAX 1000, PSAX 1250,...
  • Page 638 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes Channelized DS3, Channelized GR-822-CORE For milliwatt test refer to Sec- STS-1e, Enhanced DS1, Medium tion 5.2.1.2 T1.207a Density DS1, and Tones and For type 105 termination test, Announcements Server mod- refer to Section 5.2.5 T1.207a ules...
  • Page 639 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes Route Server module IETF RFC 792 Internet Control Message Proto- Route Server module IETF RFC 1058 Routing Information Protocol IETF RFC 1157 Simple Network Management Protocol (SNMP) Version 1.0 DS1 IMA, E1 IMA, Enhanced IETF RFC 1406...
  • Page 640 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes IETF RFC 2364 PPP Over AAL5 Route Server module IETF RFC 2427 Obsoletes RFC 1490 Multiprotocol Interconnect over Frame Relay Route Server module IETF RFC 2464 Obsoletes RFC 1972 Transmission of IPv6 Packets over Ethernet Networks...
  • Page 641 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes 1.544 Mbps, 2.048 Mbps, ITU-T G.704 44.736 Mbps; includes channel- Synchronous frame structures associated signaling (CAS) used at 1544, 6312, 2048, 8488 ABCD in-band signaling and 44 736 Kbps hierarchical levels ITU-T G.706...
  • Page 642 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes ITU-T G.736 General Aspects of Digital Trans- mission: 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...
  • Page 643 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes ITU-T G.823 The control of jitter and wander within digital networks which are based on the 2048 Kbps hierarchy Includes Multiplex Section Pro- ITU-T G.832 tection (MSP) Transmission Systems and Media, Digital Systems and Net-...
  • Page 644 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes ITU-T G.991.2 Draft: Single-pair high speed digital subscriber line (SHDSL) transceivers ITU-T G.992.1 Asymmetric Digital Subscriber Line (ADSL) transceivers ITU-T G.992.2 Splitterless Asymmetric Digital Subscriber Line (ADSL) trans- ceivers ITU-T H.248...
  • Page 645 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes Multiplexing support ITU-T I.363.2 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 Narrow- ITU-T I.366.1 band Services Segmentation and Reassembly...
  • Page 646 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes Channelized DS3, Channelized ITU-T I.431 STS-1e, Channelized DS3/STS- Integrated Services Digital Net- 1e CES, DS3 Frame Relay, work (ISDN) User-Network Enhanced DS1, Enhanced E1, Interfaces: Primary Rate User- High-Density E1, Medium-Den- Network Interface—Layer 1...
  • Page 647 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes Carrier Group AIS Alarm ITU-T I.610 Dual-homed PVCs B-ISDN operation and mainte- nance principles and functions I.610 OAM F4/F5 Processing (remote defect indication [RDI] and alarm indication signal [AIS]) Channelized DS3, Channelized...
  • Page 648 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes ITU-T Q.933 Annex A Digital Subscriber Signaling Sys- tem No. 1—Integrated Services Digital Network (ISDN) Digital Subscriber Signaling System No. 1 (DSS 1)—Signaling Specifica- tions for Frame Mode Switched and Permanent Virtual Connec- tion Control and Status Moni-...
  • Page 649 Chapter Industry Compliance Specifications Table D-2. Industry Compliance Specifications (Continued) Feature Name/Product Name Specification Title Notes ITU-T V.25 Automatic Answering Equip- ment and General Procedures for Automatic Calling Equip- ment on the General Switched Telephone Network Including Procedures for Disabling of Echo Control Devices for Both Manu- ally and Automatically Estab- lished Calls...
  • Page 650: Connection Type By Interface Type Table

    Chapter Interface Type by Connection Type Table Interface Type by Connection Type Table Table D-3. Connection Type by Interface Type Table Interface Connection AAL2 Trunking ATM-to-ATM vir- tual channel con- nection (VCC) PVC ATM-to-ATM vir- tual path connec- tion (VPC) PVC Bridge-to-ATM VCC PVC Bridge-to-bridge...
  • Page 651: Interface Types By I/O Module Types

    Chapter Interface Type by Input/Output Module Type Table Table D-3. Connection Type by Interface Type Table (Continued) Interface Connection Circuit emulation- to-ATM VCC SPVC CE-to-ATM Std AAL2 VCC SPVC Frame relay-ATM VCC SPVC VBR-to-ATM VCC SPVC VBR-to-ATM Std AAL2 VCC SPVC Interface Type by Input/Output Module Type Table Table D-4 shows the available interface types for each PacketStar PSAX I/O ®...
  • Page 652 Chapter Interface Type by Input/Output Module Type Table Table D-4. Interface Types by I/O Module Types (Continued) Interface Module 12-Port Medium- Density DS1 Multiservice ( 12-Port Medium- Density DS1 IMA MD DS1 IMA 12-Port Medium-Density DS1/E1/DS0A CES MD DS1/E1/DS0A E1 Interface Modules 6-Port Enhanced E1 Multiservice ( 21-Port High-...
  • Page 653 Chapter Interface Type by Input/Output Module Type Table Table D-4. Interface Types by I/O Module Types (Continued) Interface Module 1-Port Unchannelized DS3 Frame Relay ( 2-Port DS3 ATM DS3 ATM 2-Port E3 ATM ( 3-Port Channelized DS3/STS-1e CES CH DS3/STS-1e 3-Port Channelized DS3/STS-1e CES Protection (...
  • Page 654 Chapter Interface Type by Input/Output Module Type Table Table D-4. Interface Types by I/O Module Types (Continued) Interface Module 1-Port Channelized OC-3/STM-1 CES Single-mode ( OC-3/STM-1 CES SM 1-Port OC-3c Multimode with AQueMan ( OC-3c (MM AQ) 1-Port OC-3c Single-Mode with AQueMan ( OC-3c (SM AQ)
  • Page 655 Chapter Interface Type by Input/Output Module Type Table Table D-4. Interface Types by I/O Module Types (Continued) Interface Module 1-Port STM-1 Single-Mode with AQueMan ( STM-1 (SM AQ) 1-Port STM-1 Multimode with Traffic Shaping STM-1 (MM TS) 1-Port STM-1 Single-Mode with Traffic Shaping STM-1 (SM TS) 1-Port STM-1 1+1...
  • Page 656: Module Alarm Status Table

    Chapter Module Alarm Status Table Table D-4. Interface Types by I/O Module Types (Continued) Interface Module 8-Port Voice 2-Wire Station ( VOICE 2WS Serial Interface Modules † 2-Port High Speed HIGH SPEED Quadserial ( QUAD SERIAL 6-Port Multiserial SERIAL Ethernet Interface Modules Ethernet ( ENET 4-Port Ethernet...
  • Page 657: Quality Of Service (Qos) Class Tables

    Chapter Quality of Service (QOS) Class Tables Table D-5. Alarm Status Descriptions for Modules on the Equipment Configuration Window Module Type Number Alarm Status Description Affected NoAlarm NoAlarm indicates that the module is inserted in the chassis slot and not config- ured.
  • Page 658: Psax System-Supported Quality Of Service Classes

    Chapter Quality of Service (QOS) Class Tables Table D-6. PSAX System-Supported Quality of Service Classes ATM Service Class Description Constant Bit Rate (CBR) This service operates on a connection basis and offers consistent delay predictability. CBR is used for applications such as circuit emulation, voice, and video.
  • Page 659: Cell Loss And Cell Delay Characteristics Of Atm Service Classes

    Chapter Quality of Service (QOS) Class Tables work applications supported by the PSAX system. The flexibility of the PSAX system allows you to tailor the system based on the required service applica- tions by selecting the appropriate priority levels. Table D-8. Cell Loss and Cell Delay Characteristics of ATM Service Classes QoS Classes Supported by Cell Loss...
  • Page 660 Chapter Quality of Service (QOS) Class Tables ® PacketStar PSAX 1250 Multiservice Media Gateway User Guide, Issue 2 Release 8.0.0 D-38 255-700-247...
  • Page 661: Packetstar Psax Modules

    PSAX Modules Overview of This Appendix This appendix describes the PSAX I/O and server modules that are supported by the PSAX 1250 chassis. I/O, Optical, and Server Modules Table 1-1 lists the PacketStar PSAX modules that are described in this appen- dix.
  • Page 662 Appendix I/O, Optical, and Server Modules Table E-1. PacketStar PSAX Modules (Continued) Module Title (Faceplate Label) 1-Port STM-1 Multimode with AQueMan ( STM-1 (MM AQ) 1-Port STM-1 Multimode with Traffic Shaping ( STM-1 (MM TS) 1-Port STM-1 Single-Mode with AQueMan ( STM-1 (SM AQ) 1-Port STM-1 Single-Mode with Traffic Shaping ( STM-1 (SM TS)
  • Page 663: Example Configuration With The Alarm Module

    Appendix Alarm Module Alarm Module Software Features The Alarm module 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 E-1). In addi- tion, the CPU2 module generates trap messages that reflect state changes of the Alarm module’s sensor inputs, control outputs, and alarm cutoff control.
  • Page 664: Port Channelized Ds3 Module

    Appendix 1-Port Channelized DS3 Module • Outputs: 10 relays with Form 1-C contacts (NO/NC/COM connections), 4 relays to control remote devices and 3 audible and 3 visible relays for exter- nal alarm generation • Indicators: 4 LEDs, 3 for alarm conditions (Critical, Major, and Minor) and 1 LED for the switch operation.
  • Page 665: Hardware Features

    Appendix 3-Port Channelized DS3/STS-1e CES Module • 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.
  • Page 666: Hardware Features

    Appendix 3-Port Channelized DS3/STS-1e CES Module 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.
  • Page 667: Port Channelized Sts-1E T1 Module

    Appendix 1-Port Channelized STS-1e T1 Module • 44.736 DS3 Mbps Physical Layer Specification, af-uni-0010.002 • DS3 Physical Interface Specification, af-phy-0054 1-Port Channelized STS-1e T1 Module The 1-Port Channelized STS-1e, T1 format module provides one port with a line rate of 51.84 Mbps. The user can configure this module to provide n X 64 Kbps (fractional DS1) structured circuit-emulation service.
  • Page 668: Hardware Features

    Appendix 6-Port DS1 IMA Module • Connector type: two BNC connectors, one to receive data and the other to transmit data • Line rate: 51.84 Mbps 6-Port DS1 IMA Module The 6-Port DS1 IMA module has six physical RJ-45 ports. Inverse multiplex- ing over ATM permits a user to strap two to six of the physical ports together to create ATM interfaces that support 3–9 Mbps of bandwidth.
  • Page 669: Port Channelized Ds3/Sts-1E Ces Protection Module

    Appendix 3-Port Channelized DS3/STS-1e CES Protection Module user and network; and ATM PNNI 1.0 interfaces. It is software configurable to function in either the DS3 or the E3 mode, enabling you to deliver DS3 or E3 configurations while maintaining inventory of a single module type. The three high-speed ATM network interfaces operate 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.
  • Page 670: Port Ds3 Atm Module

    Appendix 2-Port DS3 ATM Module • DS3 Physical Interface Specification, af-phy-0054 2-Port DS3 ATM Module The 2-Port DS3 ATM provides a network interface at Digital Signal Level 3 (DS3), with a line rate of 44.736 Mbps. Typically, this module is used to con- nect the PSAX system to an ATM edge switch or digital subscriber line aggre- gation multiplexer (DSLAM) device.
  • Page 671: Port Unchannelized Ds3 Frame Relay Module

    Appendix 1-Port DS3 IMA Module Frame Relay The 1-Port Unchannelized DS3 Frame Relay module has interfaces for frame- relay network-level interworking (FRF.5) and service-level interworking (FRF.8). A maximum of 350 permanent virtual circuits (PVCs) can be assigned on each frame relay user-network interface (UNI) port. These fea- tures 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.
  • Page 672: Software Features

    Appendix 6-Port E1 IMA Module 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)
  • Page 673: Software Features

    Appendix 2-Port E3 ATM Module • Connector type: RJ-45 (120-Ohm symmetrical pair [4 wire] interface) • Line rate: 2.048 Mbps • Line encoding mode: HDB3 • Loopback capabilities: local loopback, line loopback, payload loopback • Line buildout: N/A • Framing mode: cyclic redundancy check multifrequency (CRC-mf) 2-Port E3 ATM Module The 2-Port E3 ATM module provides a network interface with a line rate of 34.368 Mbps.
  • Page 674: Port Enhanced Ds1 Module

    Appendix 6-Port Enhanced DS1 Module 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.
  • Page 675: Port Enhanced E1 Module

    Appendix 6-Port Enhanced E1 Module • Loopback capabilities: local loop, line loop, payload loop 6-Port Enhanced E1 Module The 6-Port Enhanced E1 Multiservice module contains six 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 channel- ized and unchannelized frame relay configurations, circuit emulation service, and ATM service.
  • Page 676: Hardware Features

    Appendix 4-Port Ethernet Module • Traffic policing Hardware Features The Enhanced E1 module has the following features: • Number of ports: six • Connector type: RJ-45 (120-Ohm symmetrical pair [4-wire] interface) • Line rate: 2.048 Mbps • Line encoding mode: HDB3 •...
  • Page 677: Hardware Features

    Appendix Ethernet Module 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 exten- sion ~ Maximum data payload: 1,500 bytes excluding preamble/SFD/MAC addresses/length...
  • Page 678: Ethernet Module

    Appendix Ethernet Module rate bridge groups. The virtual port provides 70 virtual channels that transmit data through the backplane. The Ethernet module has two types of light- emitting diode (LED) indicators. The module provides services for bridging from an Ethernet local area net- work (LAN) to an ATM wide area network (WAN) using RFC 2684 media access control (MAC) layer bridging and both permanent virtual circuits (PVCs) and soft permanent virtual circuits (SPVCs).
  • Page 679: Port High-Density E1 Multiservice Module

    Appendix 21-Port High-Density E1 Multiservice Module ~ virtual port used for backplane connections: 1 • Connector type: RJ-45 • Line rate: NA • Physical interfaces supported: ~ IP over frame relay (RFC 1490) ~ Per port: • port 1 supports 10 or 100 Mbps; •...
  • Page 680: Hardware Features

    Appendix 21-Port High-Density E1 Multiservice Module The High-Density E1 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 net- work.
  • Page 681: Hardware Features

    Appendix 21-Port High-Density E1 IMA Module • Loopback capabilities: line loopback, local loopback • Line buildout: N/A • Framing mode: cyclic redundancy check multi-frequency (CRC-mf) 21-Port High-Density E1 IMA Module The 21-Port High-Density E1 IMA module provides a line rate of 2.048 Mbps per port.
  • Page 682: Hardware Features

    Appendix 2-Port High-Speed Module • Line buildout: N/A • Framing mode: CRC4-CAS 2-Port High-Speed Module The High Speed module has one serial port and one parallel port. These two ports can operate simultaneously or independently. The serial interface oper- ates with a line rate of 2.048–29.824 Mbps. Typically, this module is used to connect to Direct Broadcast Satellite transmitters and receivers.
  • Page 683 Appendix 12-Port Medium-Density DS1 Multiservice Module ~ 1 serial (EIA-422 interface) (port 2) • Connector type: ~ Micro dual-row 36-pin for the parallel port ~ Micro-DB25 for the serial port • Physical interfaces supported on the parallel port: ~ Direct Broadcast Satellite transmitters and receivers ~ Video set-top boxes •...
  • Page 684: Hardware Features

    Appendix 12-Port Medium-Density DS1 Multiservice Module Software Features The Medium-Density DS1 module supports the following software agree- ments, specifications, and services: Frame Relay Forum (FRF) Implementation Agreements: • FRF.1—User-to-Network Interface (UNI) • FRF.2—Network-to-Network Interface (NNI) • FRF.5—Frame Relay/ATM PVC Network Interworking •...
  • Page 685 Appendix 12-Port Medium-Density DS1 IMA Module 12-Port Medium-Density DS1 IMA Module The 12-Port Medium-Density DS1 IMA module provides a line rate of 1.544 Mbps per port. The module’s inverse multiplexing for ATM capability allows you to strap 2 to 12 of the physical ports together to create ATM inter- faces that support up to 18 Mbps of bandwidth.
  • Page 686 Appendix 12-Port Medium-Density DS1/E1/DS0A CES Module 12-Port Medium-Density DS1/E1/DS0A CES Module The 12-Port Medium-Density DS1/E1/DS0A CES module provides DS1 cir- cuit emulation services, including a new Nx64 Kbps CAS mode to support channelized AAL1 tariff services, and a DS0A mode to support SS7 traffic across the network.
  • Page 687 Appendix 6-Port Multiserial Module • 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 ~ DS0A: line loopback, transmit pattern, monitor pattern mode, transmit and monitor pattern mode •...
  • Page 688 Appendix 6-Port Multiserial Module 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.
  • Page 689: Terminal Emulation

    Appendix 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 The implementation of ATM Adaptation Layer 1 (AAL-1) allows for the transmission of circuit emulation data as Constant Bit Rate (CBR) traffic...
  • Page 690: Quadserial Module

    Appendix Quadserial Module • Loopback capabilities: external DTE loopback • Line buildout: N/A • Framing modes: cyclic redundancy check multi-frequency (CRC-mf), Cell Delineation, LANET Quadserial Module The Quadserial module provides four serial ports for several types of serial data interfaces. Each port on the Quadserial module can be independently configured for circuit emulation, HDLC Passthrough, frame relay, and asyn- chronous transfer mode (ATM).
  • Page 691: Hardware Features

    Appendix 3-Port Unstructured DS3/E3 CES Module Hardware Features The Quadserial module provides the following hardware features: • Number of ports: 4 serial (serial interface leads comply with AF-VTOA- 0119.000) • Connector type: Mini-DB26 • Line rate (synchronous): ~ Minimum: 600 bps per port ~ Maximum: 16 Mbps per port ~ Aggregate of all ports maximum: 32 Mbps •...
  • Page 692: Software Features

    Appendix 2-Port Voice 2-Wire Office Module The 3-Port Unstructured DS3/E3 CES module provides the following hard- ware features: • Number of ports: 3 • Connector type: 6 BNC connectors for the 3 ports (each port has one receive connector and one transmit connector) •...
  • Page 693: Software Features

    Appendix 8-Port Voice 2-Wire Station Module 8-Port Voice 2-Wire Station Module The 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 Access Concen- trator system to communicate over an ATM network.
  • Page 694: Specifications

    Appendix 1-Port Channelized OC-3/STM-1 CES Module 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.
  • Page 695: Port Oc-12C/Stm-4C 1+1 Aps/Msp Multimode And Single-Mode Modules

    Appendix 1-Port OC-12c/STM-4c 1+1 APS/MSP Multimode and Single-Mode Modules 1-Port Channelized OC-3/STM-1 CES Modules Table E-2. Hardware Specifications Module Feature Ch OC-3/STM-1 CES Ch OC-3/STM-1 CES Transmitter maximum opti- -8 dBm -14 dBm cal output power (average) Receiver minimum optical -31 dBm -30 dBm input power (average)
  • Page 696: 1-Port Oc-12C/Stm-4C 1+1 Aps/Msp Sm And Mm Modules Hardware Specifications

    Appendix 1-Port OC-3c Multimode and Single-Mode Modules Software Features The 1-Port OC-12c/STM-4c 1+1 APS/MSP SM and MM modules follow the ATM Forum Traffic Management 4.1 standard of traffic prioritization. Hardware Features The 1-Port OC-12c/STM-4c 1+1 APS/MSP SM and MM modules have the hardware specifications shown in Table E-3.
  • Page 697: Port Oc-3C Multimode And Single-Mode Modules

    Appendix 1-Port OC-3c Multimode and Single-Mode Modules These modules are available in two variations, which differ according to the firmware installed in the module. • The OC-3c MM AQ and OC-3c SM AQ modules use the AQueMan algo- rithm for flow control. •...
  • Page 698: Port Oc-3C Multimode And Single-Mode 1+1 Aps Modules

    Appendix 1-Port OC-3c Multimode and Single-Mode 1+1 APS Modules Table E-4. 1-Port OC-3c MM and SM modules with AQueman or Traffic Shaping Hardware Specifications Module Feature OC-3c (SM AQ) or OC-3c (MM AQ) or OC-3c (SM TS) OC-3c (SM TS) Optical input sensitivity -31 to -8 dBm -32.5 to -14 dBm...
  • Page 699: Hardware Features

    Appendix 1-Port STM-1 Multimode and Single-Mode Modules • Private Network-Network Interface (PNNI), af-pnni-0055.000 Hardware Features The 1-Port OC-3c 1+1 APS MM and SM modules have the hardware specifi- cations shown in Table E-5. Table E-5. 1-Port OC-3c 1+1 APS Multimode and Single-Mode Modules Hardware Specifications Module Feature...
  • Page 700: Software Features

    Appendix 1-Port STM-1 Multimode and Single-Mode Modules These modules are available in two variations, which differ according to the firmware installed on the circuit boards. • One variation for both the Multi-Mode and Single-Mode types, with the names STM-1 MM AQ module and STM-1 SM AQ module, uses the AQueMan algorithm for flow control.
  • Page 701: Port Stm-1 Multimode And Single-Mode 1+1 Msp Modules

    Appendix 1-Port STM-1 Multimode and Single-Mode 1+1 MSP Modules 1-Port STM-1 Multimode and Single-Mode Modules Table E-6. Hardware Specifications Module Feature STM-1 (SM TS) or STM-1 (MM TS) or STM-1 (MM AQ) STM-1 (MM AQ) Optical output power -15 to -8 dBm -20 to -14 dBm System gain 15 dB...
  • Page 702: Software Features

    Appendix 1-Port STM-1 Multimode and Single-Mode 1+1 MSP Modules • The STM-1 Multimode (MM) 1+1 MSP module is intended for short-reach applications, for example, interoffice or intraoffice sections of a local area network (LAN) within a radius of 1.93 km. Software Features The STM-1 1+1 MSP modules use the AQueMan™...
  • Page 703: Server Modules

    Appendix Server Modules Table E-7. 1-Port STM-1 1+1 MSP Multimode and Single-Mode Module Hardware Specifications Module Feature STM-1 SM MSP STM-1 MM MSP Transmitter maximum optical -8 dBm -14 dBm output power (average) Receiver minimum optical input -31 dBm -30 dBm power (average) Receiver maximum optical input -8 dBm...
  • Page 704 Appendix DSP2x Voice Server Modules 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. Table E-8.
  • Page 705: Hardware Features

    Appendix DSP2x Voice Server Modules Table E-8. System Software Release 8.0 DSP2x Voice Server Module Configuration Modes (Continued) Available On Number of AlgoSet/ Voice Processing Standards These AAL Mode Connections Module Use Supported Modules: Provided ¶ †† AlgoSet6 DSP2E, G726-voice-compression Standard AAL2 channels G729a-voice-compression...
  • Page 706: Route Server Module

    Appendix Route Server Module The DSP2D module requires System Software Release 7.0. Route Server Module The Route Server module supports internet protoco(IP) virtual private net- works (VPNs). Each VPN supports routing information protocol (RIP version 1 and version 2) and can be assigned to multiple IP network interfaces and static routes.
  • Page 707: Software Features

    Appendix Tones and Announcements Server Module Multicasting reduces load on hosts not using RIP v2.0 messages. Multicasting also allows RIP v2.0 routers to share information that RIP v1.0 routers can- not access. Available bandwidth becomes the tiebreaker in calculating routes using default parameters for both IISP and PNNI routing.
  • Page 708: Software Features

    Appendix Tones and Announcements Server Module The test features work in conjunction with the Enhanced DS1, the Enhanced E1, the High-Density E1/DS1, the Channelized DS3/STS-1e, the CPU mod- ule, and a Connection Gateway Application Programming Interface (API). Software Features The TAS module offers these features: •...
  • Page 710 Part Number: 1250M0A8001A2 Copyright © 2002 Lucent Technologies All rights reserved.

Table of Contents