Transcript
Data Networking Products M2 Trunk Module Reference
255-100-231 Issue 3
Copyright 1998 Lucent Technologies All Rights Reserved Printed in USA
Datakit, GlobeView , and StarKeeper are registered trademarks of Lucent Technologies. HALAR is a registered trademark of Allied Chemical Corporation.
The information in this document is subject to change without notice. Lucent Technologies assumes no responsibility for any errors that may appear in this document.
________________ Contents
Preface Document Organization Related Documentation
M2 Trunk Module Overview Physical Description Features
M2 Trunk Module Installation Setting Options on Modules and I/O Boards Procedures
M2 Trunk Module Cabling Module Types Trunk Interfaces Between Nodes Recommended Trunk Selection Configuration Details
M2 Trunk Module Administration StarKeeper II NMS Administration Command Set Parameter Considerations Procedures Reports
M2 Trunk Module Troubleshooting Problem Indicators Problem Areas Procedures
vii vii viii 1-1 1-3 1-4 2-1 2-4 2-14 3-1 3-3 3-4 3-5 3-6 4-1 4-3 4-3 4-4 4-11 4-16 5-1 5-3 5-4 5-6
M2 Trunk Module Commands
6-1
Appendix. M2 Trunk Module Database Entry Forms
A-1
Index
I-1
Data Networking Products M2 Trunk Module Reference, Issue 3
iii
________________ Figures 2-1. 2-2. 2-3. 2-4. 2-5. 2-6. 2-7.
Jumper Locations: CMA9/CMA9B, CMA13, CMA14, CMA18 Modules Jumper Positions: CMA16 Module Jumper and Pin Locations: CMC6 I/O Board Jumper Positions: CMC6B I/O Board Jumper Positions: CMC13 I/O Board Jumper Positions: CMC15 I/O Board Jumper Positions: CMC16 I/O Board
2-5 2-7 2-9 2-10 2-11 2-12 2-13
3-1. 3-2. 3-3. 3-4. 3-5. 3-6. 3-7. 3-8. 3-9. 3-10. 3-11.
BNS-2000 Node to BNS-2000 Node: Direct Connection BNS-2000 Node to BNS-2000 Node: ATM Network Cabling Series M2 Shelf with Trunk-T3 Cabling Series M2 Shelf with Trunk-T3A Cabling Series M2 Shelf with Trunk-T3A via ATM Cabling Series M2 Shelf with Trunk-T3S Cabling Series M2 Shelf with Trunk-E3 Cabling Series M2 Shelf with Trunk-E3A Cabling Series M2 Shelf with Trunk-E3A via ATM Cabling Series M2 Shelf with Trunk-E3S Cabling Series M2 Shelf with Trunk-T3I
3-4 3-4 3-7 3-9 3-11 3-13 3-15 3-17 3-19 3-21 3-23
5-1. 5-2.
Diagnostic Tests: Trunk-T3/E3, Trunk-T3A, Trunk-T3S/E3S, and Trunk-T3I Diagnostic Tests: Trunk-E3A
5-14 5-16
iv
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ Tables 2-1. 2-2. 2-3. 2-4. 2-5. 2-6. 2-7. 2-8.
Trunk Modules and Corresponding I/O Boards Jumper and Pin Positions: CMA9/CMA9B, CMA13, CMA14, CMA18 Modules Jumper and Pin Positions: CMA16 Module Jumper and Pin Positions: CMC6 I/O Board Jumper and Pin Positions: CMC6B I/O Board Jumper Positions and Functions: CMC13 I/O Board Jumper and Pin Positions: CMC15 I/O Board Jumper and Pin Positions: CMC16 I/O Board
2-6 2-8 2-9 2-10 2-11 2-12 2-13
3-1. 3-2.
BNS-2000 Series M2 Shelf Connections Ordering Information
3-5 3-24
4-1. 4-2. 4-3. 4-4.
Trunk Command Set BNS-2000 to GlobeView–2000 System Parameter Mapping DS3/DS3P/E3/E3P Line Card Parameters Reports for Trunk Modules
4-4 4-9 4-10 4-16
5-1. 5-2. 5-3. 5-4. 5-5.
Command Output Module Problems Checklist Trunk Diagnostic Tests Diagnostic Testing Sequence Loopback Cables
5-4 5-5 5-9 5-10 5-10
Data Networking Products M2 Trunk Module Reference, Issue 3
2-4
v
________________ Procedures 2-1. 2-2. 2-3. 2-4.
Inserting the I/O Board Removing the I/O Board Inserting the Trunk Module Removing the Trunk Module
2-14 2-14 2-15 2-15
4-1. 4-2. 4-3. 4-4. 4-5. 4-6.
Preparing to Enter or Change Trunk Database Information Entering a Trunk Module in the Database Changing Trunk Database Configuration Moving Database Information to Another Module Address Copying Database Information to Another Module Address Enabling Measurement Reports
4-11 4-12 4-12 4-13 4-14 4-15
5-1. 5-2. 5-3. 5-4. 5-5. 5-6.
Solving Trunk Module Problems Obtaining Trunk Status Correcting Network Congestion on Trunks Responding to Alarm Messages Starting Loopback Tests Running the Node Remote Test on Trunk-T3/E3, Trunk-T3A/E3A, or Trunk-T3S/E3S 5-7. Running the Module Test 5-8. Running the Local Loopback Test 5-9. Running the Remote Loopback Test on Trunk-T3/E3, Trunk-T3A, Trunk-T3S/E3S, or Trunk-T3I 5-10. Running the Remote Loopback Test on Trunk-E3A 5-11. Correcting Diagnostic Failure 5-12. Completing Trunk Tests
vi
Data Networking Products M2 Trunk Module Reference, Issue 3
5-6 5-7 5-8 5-8 5-11 5-11 5-11 5-12 5-12 5-15 5-17 5-17
________________ Preface
The Data Networking Products M2 Trunk Module Reference provides the information needed to install, configure, and administer trunk modules in BNS-2000 Series M2 Shelves. Procedures for routine operations, maintenance, and troubleshooting are also included. For trunk modules in Series M1 Shelves, see the Data Networking Products Trunk Module Reference.
Document Organization The M2 Trunk Module Reference explains module hardware, software, and troubleshooting in the following six chapters: Trunk Module Overview
includes a physical description of the trunk modules and an overview of their features.
Trunk Module Installation
explains how to insert and remove an input/output (I/O) distribution board and a module.
Trunk Module Cabling
describes the cables and adapters required to connect compatible devices and equipment to trunk modules, and illustrates cabling configurations.
Trunk Module Administration
explains the implications of choosing certain module and I/O board options, and gives procedures for initial and routine administration.
Trunk Module Troubleshooting
provides the information and procedures needed to isolate and resolve trunk-related problems.
Trunk Module Commands
provides a detailed reference of the commands needed to administer, control, and maintain trunk modules. Included are command syntax, parameter options, input/output examples, report field definitions, and system responses.
In addition, the Appendix provides database entry forms as a guide for entering information in the configuration database.
Data Networking Products M2 Trunk Module Reference, Issue 3
vii
________________ Preface
Related Documentation Documents required for use with the Data Networking Products M2 Trunk Module Reference include BNS-2000 Node Reference BNS-2000 SMDS Guide BNS-2000 System Description Data Networking Products Messages Reference Data Networking Products Planning Guide Data Networking Products Session Maintenance Guide—for systems using automatic alternate routing StarKeeper II NMS Core System Guide StarKeeper II NMS Graphics System Guide Data Networking Products Terminology lists and defines many technical terms found in this document. Vendor documentation may be necessary for certain end devices.
viii
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Overview
Physical Description Trunk-T3 Module Trunk-E3 Module Trunk-T3A Module Trunk-E3A Module Trunk-T3S Module Trunk-E3S Module Trunk-T3I Module
Features CLNS/CONS Interconnection Capabilities Diagnostic Capabilities Call Setup Session Maintenance Interworking Configurable Options
Data Networking Products M2 Trunk Module Reference, Issue 3
1-3 1-3 1-3 1-3 1-4 1-4 1-4 1-4 1-4 1-5 1-5 1-5 1-5 1-6 1-6 1-6
________________ M2 Trunk Module Overview
Trunks installed in the BNS-2000 Series M2 Switch Shelf and Extension Shelf provide highcapacity, multi-channel connections between BNS-2000 nodes in one or several networks. Series M2 internodal trunks support both connectionless (CLNS) and connection-oriented (CONS) services. The Trunk-T3 (TRK-T3), Trunk-T3A (TRK-T3A), Trunk-T3S (TRK-T3S), and Trunk-T3I (TRK-T3I) modules provide data transport between nodes, using coaxial cable, and, optionally, an appropriate Data Signal, Level 3 (DS3) transmission facility. The Trunk-E3 (TRK-E3), Trunk-E3A (TRK-E3A), and Trunk-E3S (TRK-E3S) provide data transport between nodes via an E3 transmission facility. The Trunk-T3A and Trunk-E3A are used to connect BNS2000 nodes either directly or through an asynchronous transfer mode (ATM) switch. BNS-2000 Release 5.0 supports AAL5/ATM interworking between M2-FRM modules, if the M2-FRM PVC spans nodes, TRK-T3A or TRK-E3A modules must be used.
Physical Description The following describes the BNS-2000 trunk module types that are used with Series M2 Shelves. Specific details regarding trunk module installation, administration, and troubleshooting are provided in the appropriate chapters.
Trunk-T3 Module The Trunk-T3 (CMA9) module is a single-port DS3 trunk module that provides data transport for both CLNS and CONS traffic. The Trunk-T3 uses the CMC6 or CMC6B I/O board, which supplies a coaxial interface, has a built-in data service unit (DSU) function, and supports the Distributed Queue Dual Bus (DQDB) protocol and the Physical Layer Convergence Procedure (PLCP).
Trunk-E3 Module The Trunk-E3 (CMA9B) module is a single-port trunk module that provides data transport for both CLNS and CONS traffic via an E3 transmission facility. The Trunk-E3 uses the CMC13 I/O board, which has two micro-coaxial cable connectors, one for transmit and one for receive.
Trunk-T3A Module The Trunk-T3A (CMA18) module is a single-port DS3 trunk module that uses the CMC15 I/O board. The Trunk-T3A provides data transport directly between two BNS-2000 nodes, or between two BNS-2000 nodes through an ATM network, for both CLNS and CONS IntraLATA and Private InterLATA traffic. The Trunk-T3A also supports committed information rate (CIR)
Data Networking Products M2 Trunk Module Reference, Issue 3
1-3
________________ M2 Trunk Module Overview
for frame relay traffic. (CIR is a feature of the frame relay protocol for the rate at which the network agrees to transfer information under normal conditions.) For releases supporting AAL5/ATM interworking, the Trunk-T3A module must be used for AAL5.
Trunk-E3A Module The Trunk-E3A (CMA18) module is a single-port trunk module that uses the CMC16 I/O board, and provides data transport directly between two BNS-2000 nodes, or between two BNS-2000 nodes through an ATM network, for both CLNS and CONS traffic. The Trunk-E3A also supports CIR for frame relay traffic. For releases supporting AAL5/ATM interworking, the Trunk-E3A module must be used for AAL5.
Trunk-T3S Module The Trunk-T3S (CMA13) module is a single-port DS3 trunk module that uses the CMC6 or CMC6B I/O board. The module provides both CLNS and CONS data transport for both IntraLATA and Private InterLATA traffic, and supports CIR for frame relay traffic.
Trunk-E3S Module The Trunk-E3S (CMA13) module is a single-port trunk module that uses the CMC13 I/O board, and provides both CLNS and CONS data transport. The Trunk-E3S also supports CIR for frame relay traffic.
Trunk-T3I Module The Trunk-T3I module is a two-board DS3 trunk module that supports CLNS Inter-Carrier Interface (ICI) applications. The Trunk-T3I has an egress module board (CMA14) and an ingress module board (CMA16). The CMC6B (egress) and CMC14 (ingress) I/O boards provide the interface between the Trunk-T3I module and the facility DS3 line.
Features Series M2 internodal trunk modules feature multiple channel high-speed interconnection capabilities, as well as supporting both CLNS and CONS. These features are supported by maintenance diagnostic capabilities, call setup, session maintenance, and interworking. A variety of configurable options are also available.
1-4
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Overview
CLNS/CONS The Trunk-T3/E3, Trunk-T3S/E3S, and Trunk-T3I support CLNS using the IEEE 802.6 DQDB protocol as the SMDS Interface Protocol (SIP). The Trunk-T3A and Trunk-E3A support CLNS using the ATM protocol as the SMDS SIP. The Trunk-T3/E3, Trunk-T3A/E3A, and TrunkT3S/E3S also support CONS. SMDS Inter-Carrier Interface (ICI)
SMDS networks maintained by Local Exchange Carriers (LECs) in different Local Access and Transport Areas (LATAs) can be interconnected via Interexchange Carriers (ICs) across the LATAs using the Trunk-T3I and its various ICI applications. LECs in the same LATA can also interwork via a serving arrangement (SA) interface. Private InterLATA Trunks
Using a Trunk-T3A or Trunk-T3S, a carrier spanning two or more LATAs can use a Private InterLATA interface to transport its own "official" data across the LATA boundaries.
Interconnection Capabilities Trunks provide the following transmission capabilities for interconnecting nodes: The Trunk-T3/T3A/T3S and Trunk-T3I modules operate at DS3 rates of 44.74 Mbps; the Trunk-E3/E3A/E3S operates at speeds up to 34.368 Mbps. The Trunk-T3/E3, Trunk-T3A/E3A, and Trunk-T3S/E3S modules support up to 8172 virtual circuits. No circuits are required for the Trunk-T3I, which provides data transport for CLNS traffic only. The Trunk-T3A/E3A and Trunk-T3S/E3S provide the capability to support CIR for frame relay traffic throughout the network.
Diagnostic Capabilities Trunk module diagnostic software is used to isolate and segment problems that occur on trunk interconnections. Alarms warn of the existence of problems, and StarKeeper II NMS offers network monitoring and fault isolation analysis.
Call Setup A variety of virtual connection capabilities are provided for endpoints at either end of a trunk. These include security screening to manage access to node resources, and alternate routing to provide redundant interconnections and to minimize transmission failures.
Data Networking Products M2 Trunk Module Reference, Issue 3
1-5
________________ M2 Trunk Module Overview
Session Maintenance Session maintenance provides the ability to maintain established calls or sessions despite failed trunk facilities. With session maintenance, when a trunk failure occurs, all active calls on that trunk are rerouted over standby trunks. To configure session maintenance trunks, StarKeeper II NMS is required. See the Session Maintenance Guide for details.
Interworking In keeping with the modular architecture of the network, no restrictions are imposed on connection topology—nodes can be trunked together in any configuration to support the characteristics and requirements of a given network. Only trunks of the same module type can interwork (that is, a trunk module from one node must be connected to the same trunk module type in another node).
Configurable Options The following are some of the parameter options that can be configured in the database with the enter trunk command, depending on the hardware configuration and the application supported. The Commands chapter provides a complete listing and definitions of the options available for configuring trunk modules. The Node Reference, Volume 2: Commands provides information for all other command options related to trunk module configuration. The Trunk-T3I should be configured through StarKeeper II NMS. See the StarKeeper II NMS Graphics System Guide. for all trunks: —
module type options
—
a set of security patterns (for CONS traffic) used to check the destination address of calls at a strategic point in a network to permit, deny, or limit access to a certain host, node, or set of nodes for calls coming in to a trunk
—
threshold profile IDs (configured with the enter threshold command) that tune the limits of the physical performance parameters used to monitor the data transport error rate to trunk modules
for the Trunk-T3/E3, Trunk-T3A/E3A, and Trunk-T3S/E3S: trunk weight options used in determining the shortest path for CLNS traffic between two nodes for the Trunk-T3/E3, Trunk-T3S/E3S and Trunk-T3I: DQDB bus indicators specifying the trunk modules to be configured as head of bus a and head of bus b
1-6
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Overview
for the Trunk-T3A/T3S: —
data transport of "official" traffic within a LEC that extends beyond the LATA boundaries (Private InterLATA)
—
data transport within the same network (IntraLATA)
for the Trunk-T3A/E3A: —
virtual circuit path that carries all BNS-2000 traffic between node pairs
—
ATM interface type user–network interface (UNI) network–node interface (NNI)
—
I/O board timing source
for the Trunk-E3A: —
a local module trail trace address for the local module to send to the far end device
—
a far end trail trace address for the local module to receive from the far end device
—
loss of signal (LOS) standard
for the Trunk-T3I: ICI applications IC
a trunk within an Interexchange Carrier (IC) connected to another trunk within a Local Exchange Carrier (LEC)
LEC
a trunk within a LEC connected to another trunk within an IC
SA
a trunk within a LEC in a serving arrangement (SA) to another LEC within the same LATA
Data Networking Products M2 Trunk Module Reference, Issue 3
1-7
________________ M2 Trunk Module Installation
Setting Options on Modules and I/O Boards Procedures
2-4 2-14
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Installation
Trunk module installation consists of inserting the I/O distribution board in the backplane slot and the module in the corresponding shelf slot. This section provides specific information for setting switches and positioning jumpers, as well as procedures for inserting and removing I/O boards and trunk modules. When installing a trunk module: 1. Ensure protection from electromagnetic interference (EMI, see inside front cover). Wear an electrostatic discharge (ESD) wrist strap to prevent equipment damage. See the Node Reference for grounding locations and related details. 2. Verify that the I/O board to be installed is appropriate for use with the type of trunk module being installed. 3. Ensure that the correct slot is specified for the module. Refer to the Planning Guide and the Node Reference for module placement in the node. 4. When installing a trunk in a two-board configuration (Trunk-T3I), always insert the egress module and I/O board in the lower numbered slot, and the ingress module and I/O board in the next higher numbered slot. 5. Where appropriate, set the switches, or position the jumpers on the I/O board, before inserting it in the backplane; see Setting Options on Modules and I/O Boards in this chapter. CAUTION:
To prevent damage to module circuitry, always insert the I/O board before inserting its corresponding module. Never remove the I/O board before removing the module.
6. Insert the appropriate I/O board(s); see Procedure 2-1. 7. Position the jumpers on the trunk modules where required; see Setting Options on Modules and I/O Boards. 8. Insert the trunk module(s); see Procedure 2-3. 9. Cable the I/O board ports to support external devices; see the M2 Trunk Module Cabling chapter. 10. Examine the LEDs on the I/O board. If they are lit, refer to the M2 Trunk Module Troubleshooting chapter for their significance.
Data Networking Products M2 Trunk Module Reference, Issue 3
2-3
________________ M2 Trunk Module Installation
Setting Options on Modules and I/O Boards This section illustrates and explains the jumper settings and their functions for the trunk modules and I/O boards used with the Series M2 Shelves.
TABLE 2-1. Trunk Modules and Corresponding I/O Boards _____________________________________________________________ Module I/O Trunk Reference _____________________________________________________________ Board Reference Board Trunk-T3 CMA9 Fig. 2-1 CMC6 or CMC6B Fig. 2-3, 2-4 _____________________________________________________________ Table 2-4, 2-5 Trunk-E3 CMA9B Fig. 2-1 CMC13 Fig. 2-5 Table 2-6 _____________________________________________________________ Trunk-T3A CMA18 Fig. 2-1 CMC15 Fig. 2-6 _____________________________________________________________ Table 2-7 Trunk-E3A CMA18 Fig. 2-1 CMC16 Fig. 2-7 _____________________________________________________________ Table 2-7 Trunk-T3S CMA13 Fig. 2-1 CMC6 or CMC6B Fig. 2-3, 2-4 _____________________________________________________________ Table 2-4, 2-5 Trunk-E3S CMA13 Fig. 2-1 CMC13 Fig. 2-5 _____________________________________________________________ Table 2-6 Trunk-T3I CMA14 Fig. 2-1 CMC6B Fig. 2-4 _______________________________________________ (egress) Table 2-5 (egress) CMA16 Fig. 2-2 CMC14 N/A _____________________________________________________________ (ingress) (ingress)
The Trunk-T3 (CMA9) module and the Trunk-E3 (CMA9B) module each has 18 factory-set jumpers. Although these jumpers are used for factory testing only, all 18 must be installed for the module to function properly. The Trunk-T3 (CMA9) and Trunk-T3S (CMA13) can use either the CMC6 or CMC6B I/O boards. On the CMC6B I/O board, all jumpers except P16 must be installed. The Trunk-E3 (CMA9B) and the Trunk-E3S (CMA13) use the CMC13 I/O board. The CMA18 module board has the same jumper positions and settings as the CMA9 module. It is used with the CMC15 I/O board for the Trunk-T3A, and with the CMC16 I/O board for the Trunk-E3A. The Trunk-T3I (CMA14) egress module jumper positions and settings are the same as those for the CMA9 module; the CMC6B is the corresponding egress I/O board. The Trunk-T3I (CMA16) ingress module has nine jumper positions. All jumpers on the CMA16 module are installed. The corresponding ingress (CMC14) I/O board does not require any jumper settings. The following figures show jumper locations and pin positions, where applicable, for the modules and I/O boards, as well as transmit and receive connectors on the I/O boards. Tables provide additional jumper and pin information.
2-4
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Installation
P3202 P3701
P3802
P3801
P3201
P2901
P4101 P2401
P2402
P0402 P0401
P0101
P0102
P0201
P4403
P0301
P4402
P4401
FIGURE 2-1. Jumper Locations: CMA9/CMA9B, CMA13, CMA14, CMA18 Modules
Data Networking Products M2 Trunk Module Reference, Issue 3
2-5
________________ M2 Trunk Module Installation
TABLE 2-2.
Jumper and Pin Positions: CMA9/CMA9B, CMA13, CMA14, CMA18 Modules
____________________________________________________________ ____________________________________________________________ Usage Position Jumper Usage Position Jumper P0101 ____________________________________________________________ Pins 1 and 2 Installed P3201 Pins 1 and 2 Installed P0102 Pins 1 and 2 Installed P3202 Pins 1 and 2 Installed ____________________________________________________________ ____________________________________________________________ P0201 Pins 1 and 2 Installed P3701 Pins 1 and 2 Installed P0301 Pins 1 and 2 Installed P3801 Pins 1 and 2 Installed ____________________________________________________________ P0401 Pins 1 and 2 Installed P3802 Pins 1 and 2 Installed ____________________________________________________________ P0402 Pins 1 and 2 Installed P4101 Pins 1 and 2 Installed ____________________________________________________________ P2401 Pins 1 and 2 Installed P4401 Pins 1 and 2 Installed ____________________________________________________________ ____________________________________________________________ P2402 Pins 1 and 2 Installed P4402 Pins 1 and 2 Installed P2901 Pins 1 and 2 Installed P4403 Pins 1 and 2 Installed ____________________________________________________________
2-6
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Installation
P10
P9
P11 P6
P5
P1
P2 P4
P3
FIGURE 2-2. Jumper Positions: CMA16 Module
Data Networking Products M2 Trunk Module Reference, Issue 3
2-7
________________ M2 Trunk Module Installation
TABLE 2-3.
Jumper and Pin Positions: CMA16 Module ______________________________ Usage Position Jumper ______________________________ P1 ______________________________ Pins 1 and 2 Installed P2 ______________________________ Pins 1 and 2 Installed ______________________________ Pins 1 and 2 Installed P3 P4 ______________________________ Pins 1 and 2 Installed P5 ______________________________ Pins 1 and 2 Installed P6 Pins 1 and 2 Installed ______________________________ P9 ______________________________ Pins 1 and 2 Installed ______________________________ Pins 1 and 2 Installed P10 P11 Pins 1 and 2 Installed ______________________________
2-8
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Installation
P16 12
P21 1 2
P11 12
P19
123
123
P7
P5
1 P6 P2 2 3 1 P9 2 3 123 123 P4 P1
12 P17 123 P20
P18
1 2 3
P8 1234
P3 1 2 3 P12
1 2
P13
1 2
P10
12 J3(R)
J2(T)
FIGURE 2-3. Jumper and Pin Locations: CMC6 I/O Board
TABLE 2-4. Jumper and Pin Positions: CMC6 I/O Board _________________________________________________________________ _________________________________________________________________ Usage Position Jumper Usage Position Jumper P1 _________________________________________________________________ pins 1 and 2 Installed P11 pins 1 and 2 Installed P2 _________________________________________________________________ pins 2 and 3 Installed P12 no jumper Not installed _________________________________________________________________ pins 1 and 2 Installed P13 no jumper Not installed P3 P4 _________________________________________________________________ pins 1 and 2 Installed P16 no jumper Not installed _________________________________________________________________ P5 pins 1 and 2 Installed P17 pins 2 and 3 Installed P6 pins 2 and 3 Installed P18 pins 1 and 2 Installed _________________________________________________________________ P7 _________________________________________________________________ pins 1 and 2 Installed P19 pins 1 and 2 Installed _________________________________________________________________ pins 2 and 3 Installed P20 pins 1 and 2 Installed P8 P9 pins 2 and 3 Installed P21 pins 1 and 2 Installed _________________________________________________________________ P10 _________________________________________________________________ no jumper Not installed
Data Networking Products M2 Trunk Module Reference, Issue 3
2-9
________________ M2 Trunk Module Installation
P16 12
P21
P11
12
12 P19
12
P18
P20 12
12 J3(R)
J2(T)
FIGURE 2-4. Jumper Positions: CMC6B I/O Board
TABLE 2-5. Jumper and Pin Positions: CMC6B I/O Board ________________________________ ________________________________ Usage Position Jumper ________________________________ P11 Pins 1 and 2 Installed P16 ________________________________ No jumper Not installed ________________________________ Pins 1 and 2 Installed P18 ________________________________ P19 Pins 1 and 2 Installed P20 ________________________________ Pins 1 and 2 Installed P21 Pins 1 and 2 Installed ________________________________
2-10
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Installation
WA7
WA10
WA8
WA4 WA6 WA5 WA9
WA11
WA12
WA3
WA2 1
WA1
1
RX (J3) (J2) TX
FIGURE 2-5. Jumper Positions: CMC13 I/O Board
TABLE 2-6. Jumper Positions and Functions: CMC13 I/O Board _______________________________________ _______________________________________ Factory Setting Jumper Function WA1 _______________________________________ FILTRO RX Open WA2 _______________________________________ BITAL 14 Open _______________________________________ WA3 BITAL 13 Open WA4 _______________________________________ BITAL 16 Closed _______________________________________ BUTAL 15 Closed WA5 WA6 Pull-up PERENA Open _______________________________________ WA7 _______________________________________ INIT (Egress) Closed _______________________________________ TREAD Closed WA8 WA9 INIT (Ingress) Closed _______________________________________ WA10 _______________________________________ INIT (OV) Closed WA11 RLOOP 2 and 3 Closed 1 Open _______________________________________ WA12 LLOOP 2 and 3 Closed _______________________________________ 1 Open
Data Networking Products M2 Trunk Module Reference, Issue 3
2-11
________________ M2 Trunk Module Installation
P1 P2
RX
J3
J4
TX
FIGURE 2-6. Jumper Positions: CMC15 I/O Board
TABLE 2-7. Jumper and Pin Positions: CMC15 I/O Board ________________________________ ________________________________ Usage Position Jumper ________________________________ Pins 1 and 2 Not installed P1 P2 Pins 1 and 2 Not installed ________________________________
2-12
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Installation
P1
P5 RX
J5
J6
TX
FIGURE 2-7. Jumper Positions: CMC16 I/O Board
TABLE 2-8. Jumper and Pin Positions: CMC16 I/O Board ________________________________ ________________________________ Usage Position Jumper ________________________________ Pins 1 and 2 Not installed P1 P5 Pins 1 and 2 Not installed ________________________________
Data Networking Products M2 Trunk Module Reference, Issue 3
2-13
________________ M2 Trunk Module Installation
Procedures The following procedures give the steps for inserting and removing an I/O board and for inserting and removing a trunk module.
PROCEDURE 2-1. Inserting the I/O Board The I/O board plugs into the backplane at the rear of the shelf; it is held in place by shrouds on the backplane pinfield, and secured with two screws. Insert the I/O board before inserting its corresponding trunk module. 1. Align the I/O board backplane connector with the backplane pinfield, and align the screw slots with the screw holes. 2. Slip the backplane connector onto the pins. The board should seat easily. If seating is difficult, the board may be canted or some pins may be bent. 3. Insert the screws, and tighten them securely.
PROCEDURE 2-2. Removing the I/O Board Remove the I/O board only for relocation, replacement, or board type confirmation. Requirement: Module in the slot corresponding to the I/O board must be removed. 1. Disconnect all cabling to I/O board ports, labeling the cable ends if appropriate. 2. Remove the screws holding the I/O board in place. 3. Carefully rock the board as you pull it out.
2-14
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Installation
PROCEDURE 2-3.
Inserting the Trunk Module
Requirement: I/O board for the module must be in its corresponding slot on the backplane at the rear of the shelf. 1. Set the mode switch on the module faceplate to Disab. 2. With the module latch(es) extended, carefully push the module all the way into the slot. The backplane pins slip into the module receptacle. 3. Close the latches to lock the module into position. 4. Move the mode switch on the module faceplate to Enabl. For the two-board module, set the mode switch on each module faceplate to Enabl.
PROCEDURE 2-4. Removing the Trunk Module You can remove and replace a trunk module in an operating node without damaging the module itself, or without disrupting calls on other modules. Only the calls on the trunk module being removed are disrupted. Requirement: I/O board for the module must still be in its corresponding slot on the backplane at the rear of the shelf. 1. If the mode switch is in the Enabl position, move it to Disab. For the two-board module, set the mode switch on each module faceplate to Disab. 2. Open the latch(es) on the module faceplate. 3. Pull the module straight out of the slot.
Data Networking Products M2 Trunk Module Reference, Issue 3
2-15
________________ M2 Trunk Module Cabling
Module Types
3-3
Trunk Interfaces Between Nodes
3-4
Recommended Trunk Selection
3-5
Configuration Details Cabling Series M2 Shelf with Trunk-T3 Cabling Series M2 Shelf with Trunk-T3A Cabling Series M2 Shelf with Trunk-T3A via ATM Cabling Series M2 Shelf with Trunk-T3S Cabling Series M2 Shelf with Trunk-E3 Cabling Series M2 Shelf with Trunk-E3A Cabling Series M2 Shelf with Trunk-E3A via ATM Cabling Series M2 Shelf with Trunk-E3S Cabling Series M2 Shelf with Trunk-T3I
Data Networking Products M2 Trunk Module Reference, Issue 3
3-6 3-6 3-8 3-10 3-12 3-14 3-16 3-18 3-20 3-22
________________ M2 Trunk Module Cabling
In a BNS-2000 network, trunk modules provide the interface to connect BNS-2000 nodes either directly or through an ATM switch or network. This chapter provides the following information for cabling BNS-2000 nodes in a network: a brief description of the trunk module types that can be installed in BNS-2000 Series M2 Shelves figures illustrating the trunk module interfaces connecting BNS-2000 nodes in the network tables indicating the specific trunk modules that are best suited, based on trunk speed requirements, for BNS-2000 connections in the network detailed information (speed ranges, interface types supported, and I/O boards) for each trunk module in various connection configurations instructions and figures illustrating each configuration for cabling BNS-2000 nodes in a network tables providing cable ordering information* for each configuration WARNING:
The first 25 feet of data cabling connected to the trunk must be shielded to meet Federal Communications Commission (FCC) Electromagnetic Interference (EMI) requirements. If longer cable runs are needed for a given configuration, unshielded cables can be used after the first 25 feet. When Lucent Technologies cables and other components are specified, no other cables and components can be used. Otherwise, Lucent Technologies is not responsible for failure to meet FCC regulations.
Module Types The Series M2 trunk modules in a BNS-2000 network use coaxial cable, and optionally, an appropriate DS3 or E3 transmission facility between nodes. The Trunk-T3/E3, Trunk-T3A/E3A, Trunk-T3I, and Trunk-T3S/E3S, are used in these configurations.
________________ * Some cables are available with plenum sheathing. These cables have a HALAR outer sheath that satisfies electrical code restrictions on emission of toxic fumes in a fire, and can be used in air-return plenums.
Data Networking Products M2 Trunk Module Reference, Issue 3
3-3
________________ M2 Trunk Module Cabling
Trunk Interfaces Between Nodes The following figures show various trunk interfaces in a BNS-2000 M2 network. Figure 3-1 illustrates Series M2 trunk interfaces directly connecting two BNS-2000 nodes. Figure 3-2 illustrates trunk interfaces connecting two BNS-2000 nodes through an ATM switch or network.
BNS-2000 Series M2 Shelf
FIGURE 3-1.
BNS-2000 Series M2 Shelf
Trk-T3S/E3S
Trk-T3S/E3S
Trk-T3/E3
Trk-T3/E3
Trk-T3I
Trk-T3I
BNS-2000 Node to BNS-2000 Node: Direct Connection
BNS-2000 Series M2 Shelf
Trunk-T3A/E3A
FIGURE 3-2.
3-4
BNS-2000 Series M2 Shelf
ATM Switch
Trunk-T3A/E3A
BNS-2000 Node to BNS-2000 Node: ATM Network
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
Recommended Trunk Selection Certain trunks are recommended based on traffic loads and applications. For additional trunk selection information see the Design Issues chapter in the Planning Guide. This section specifies the trunk modules recommended for use in BNS-2000 network configurations.
TABLE 3-1. BNS-2000 Series M2 Shelf Connections ___________________________________________________________________________ Connections Between Trunk Speed Interface I/O BNS-2000 Type Module (bps) Board(s) Series M2 Shelf and: ___________________________________________________________________________ BNS-2000 Series M2 Shelf Trunk-T3 44.736M BNC coax CMC6 or ___________ __________ CMC6B Trunk-T3A CMC15 ___________ __________ Trunk-T3S CMC6 or CMC6B ___________ __________ Trunk-T3I CMC6B _________________________________________________ CMC14 Trunk-E3 ___________ 34.368M 75 Ω micro-coax CMC13 ___________ Trunk-E3S ______________________________ ___________________________________________________________________________ Trunk-E3A Coax with BT connectors CMC16
Data Networking Products M2 Trunk Module Reference, Issue 3
3-5
________________ M2 Trunk Module Cabling
Configuration Details The following subsections explain cabling configurations for Series M2 trunks in BNS-2000 nodes. Configuration details for connecting BNS-2000 nodes include figures illustrating the configurations, and ordering information for the appropriate cables and adapters.
Cabling Series M2 Shelf with Trunk-T3 Cabling a Series M2 Shelf with Trunk-T3 uses the following: a Trunk-T3 module consisting of a CMA9 circuit pack and a CMC6 or CMC6B I/O board DDM-1000 unit(s) for transmission via private line to the terminating device a pair of 728B coaxial cables originating on the J2 and J3 connectors of the I/O board and connecting to a DDM-1000 NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
One coaxial cable of the pair is the transmit side, J2 (T); the other coaxial cable is the receive side, J3 (R). at the remote end, a pair of 728B coaxial cables connecting the terminating DDM-1000 to the I/O board J2 and J3 ports NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
—
The DDM-1000 facility provides the crossover end-to-end transmit and receive.
—
With no DDM-1000 and a straight connection, each transmit coaxial cable must be connected with the receive connector for the opposite end.
The following figure illustrates this configuration.
3-6
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-T3 CMC6/CMC6B J3
R
J2
T
728B 728B
DDM-1000
BNS-2000 Series M2 Shelf Trunk-T3 CMC6/CMC6B J3
R
J2
T
728B
DDM-1000
~
728B
DS3 Facility
FIGURE 3-3.
Cabling Series M2 Shelf with Trunk-T3
Data Networking Products M2 Trunk Module Reference, Issue 3
3-7
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-T3A Cabling a Series M2 Shelf with Trunk-T3A uses the following: a Trunk-T3A module consisting of a CMA18 circuit pack and a CMC15 I/O board DDM-1000 unit(s) for transmission via private line to the terminating device a pair of 728B coaxial cables originating on the J3 and J4 connectors of the I/O board and connecting to a DDM-1000 NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
One coaxial cable of the pair is the transmit side, J4 (TX); the other coaxial cable is the receive side, J3 (RX). at the remote end, a pair of 728B coaxial cables connecting the terminating DDM-1000 to the I/O board J3 and J4 ports NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
—
The DDM-1000 facility provides the crossover end-to-end transmit and receive.
—
With no DDM-1000 and a straight connection, each transmit coaxial cable must be connected with the receive connector for the opposite end.
The following figure illustrates this configuration.
3-8
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-T3A CMC15 J3
RX
J4
TX
728B 728B
DDM-1000
BNS-2000 Series M2 Shelf Trunk-T3A CMC15 J3
RX
J4
TX
728B
DDM-1000
~
728B
DS3 Facility
FIGURE 3-4.
Cabling Series M2 Shelf with Trunk-T3A
Data Networking Products M2 Trunk Module Reference, Issue 3
3-9
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-T3A via ATM Cabling a Series M2 Shelf with Trunk-T3A through an ATM switch uses the following: a Trunk-T3A module consisting of a CMA18 circuit pack and a CMC15 I/O board an ATM switch with a DS3 line card (LC) for transmission via the ATM network to the terminating device a pair of 728B coaxial cables originating on the J3 and J4 connectors of the I/O board and connecting to the DS3 LC on the ATM switch One coaxial cable of the pair is the transmit side, J4 (TX); the other coaxial cable is the receive side, J3 (RX). NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
at the remote end, a pair of 728B coaxial cables connecting the DS3 LC on the ATM switch to the terminating I/O board J3 and J4 ports NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
The following figure illustrates this configuration.
3-10
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-T3A CMC15 J3
RX
J4
TX
ATM Switch
DS3 Line Card
728B
DS3 Line Card
728B
ATM Switch
BNS-2000 Series M2 Shelf Trunk-T3A CMC15 RX
J4
TX
728B 728B
FIGURE 3-5.
~
J3
DS3 Facility
Cabling Series M2 Shelf with Trunk-T3A via ATM
Data Networking Products M2 Trunk Module Reference, Issue 3
3-11
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-T3S Cabling a Series M2 Shelf with Trunk-T3S uses the following: a Trunk-T3S module consisting of a CMA13 circuit pack and a CMC6 or CMC6B I/O board DDM-1000 unit(s) for transmission via private line to the terminating device a pair of 728B coaxial cables originating on the J2 and J3 connectors of the I/O board and connecting to the DDM-1000 NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
One coaxial cable of the pair is the transmit side, J2 (T); the other coaxial cable is the receive side, J3 (R). at the remote end, a pair of 728B coaxial cables connecting the terminating DDM-1000 to the I/O board J2 and J3 ports NOTE:
728B-90 coaxial cable is used if a 90° connector is required.
—
The DDM-1000 facility provides the crossover end-to-end transmit and receive.
—
With no DDM-1000 and a straight connection, each transmit coaxial cable must be connected with the receive connector for the opposite end.
The following figure illustrates this configuration.
3-12
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-T3S CMC6/CMC6B J3
R
J2
T
728B 728B
DDM-1000
BNS-2000 Series M2 Shelf Trunk-T3S CMC6/CMC6B J3
R
J2
T
728B
DDM-1000
~
728B
DS3 Facility
FIGURE 3-6.
Cabling Series M2 Shelf with Trunk-T3S
Data Networking Products M2 Trunk Module Reference, Issue 3
3-13
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-E3 Cabling a Series M2 Shelf with Trunk-E3 uses the following: a Trunk-E3 module consisting of a CMA9B circuit pack and a CMC13 I/O board distribution frame (DF) a pair of 75 Ω micro-coaxial cables originating on the J2 and J3 connectors of the I/O board and connecting to the DF One micro-coaxial cable of the pair is the transmit side, J2 (TX); the other micro-coaxial cable is the receive side, J3 (RX). at the remote end, a pair of 75 Ω micro-coaxial cables connecting the terminating DF to the I/O board J2 and J3 ports The following figure illustrates this configuration.
3-14
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-E3 CMC13 J3
RX
J2
TX
75 Ω DF
BNS-2000 Series M2 Shelf
E3 Facility
~
75 Ω
Trunk-E3 CMC13 J3
RX
J2
TX
75 Ω 75 Ω
FIGURE 3-7.
DF
Cabling Series M2 Shelf with Trunk-E3
Data Networking Products M2 Trunk Module Reference, Issue 3
3-15
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-E3A Cabling a Series M2 Shelf with Trunk-E3A uses the following: a Trunk-E3A module consisting of a CMA18 circuit pack and a CMC16 I/O board distribution frame (DF) a pair of ATM-E3-S coaxial cables originating on the J5 and J6 connectors of the I/O board and connecting to the DF One coaxial cable of the pair is the transmit side, J6 (TX); the other coaxial cable is the receive side, J5 (RX). at the remote end, a pair of ATM-E3-S coaxial cables connecting the terminating DF to the I/O board J5 and J6 ports The following figure illustrates this configuration.
3-16
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-E3A CMC16 J5
RX
J6
TX
ATM-E3-S ATM-E3-S
DF
BNS-2000 Series M2 Shelf Trunk-E3A CMC16 J5
RX
J6
TX
ATM-E3-S
DF
~
ATM-E3-S
E3 Facility
FIGURE 3-8.
Cabling Series M2 Shelf with Trunk-E3A
Data Networking Products M2 Trunk Module Reference, Issue 3
3-17
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-E3A via ATM Cabling a Series M2 Shelf with Trunk-E3A through an ATM switch uses the following: a Trunk-E3A module consisting of a CMA18 circuit pack and a CMC16 I/O board an ATM switch with an E3 line card (LC) for transmission via the ATM network to the terminating device a pair of ATM-E3-S or ATM-E3-BNC coaxial cables originating on the J5 and J6 connectors of the I/O board and connecting to the E3 LC on the ATM switch One coaxial cable of the pair is the transmit side, J6 (TX); the other coaxial cable is the receive side, J5 (RX). at the remote end, a pair of ATM-E3-S or ATM-E3-BNC coaxial cables connecting the E3 LC on the ATM switch to the terminating I/O board J5 and J6 ports The following figure illustrates this configuration.
3-18
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-E3A CMC16 RX
J6
TX
ATM-E3-S or ATM-E3-BNC
E3 Line Card
ATM-E3-S or ATM-E3-BNC
ATM Switch
BNS-2000 Series M2 Shelf
E3 Facility
~
J5
Trunk-E3A CMC16 J5
RX
J6
TX
ATM-E3-S or ATM-E3-BNC
FIGURE 3-9.
E3 Line Card
ATM-E3-S or ATM-E3-BNC
ATM Switch
Cabling Series M2 Shelf with Trunk-E3A via ATM
Data Networking Products M2 Trunk Module Reference, Issue 3
3-19
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-E3S Cabling a Series M2 Shelf with Trunk-E3S uses the following: a Trunk-E3S module consisting of a CMA13 circuit pack and a CMC13 I/O board a distribution frame (DF) a pair of 75 Ω micro-coaxial cables originating on the J2 and J3 connectors of the I/O board and connected via a DF, or directly to the network. One micro-coaxial cable of the pair is the transmit side, J2 (TX); the other micro-coaxial cable is the receive side, J3 (RX). at the remote end, a pair of 75 Ω micro-coaxial cables connecting the terminating DF to the I/O board J2 and J3 ports The following figure illustrates this configuration.
3-20
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf Trunk-E3S CMC13 J3
RX
J2
TX
75 Ω DF
BNS-2000 Series M2 Shelf
E3 Facility
~
75 Ω
Trunk-E3S CMC13 J3
RX
J2
TX
75 Ω 75 Ω
FIGURE 3-10.
DF
Cabling Series M2 Shelf with Trunk-E3S
Data Networking Products M2 Trunk Module Reference, Issue 3
3-21
________________ M2 Trunk Module Cabling
Cabling Series M2 Shelf with Trunk-T3I Cabling a Series M2 Shelf with Trunk-T3I uses the following: a Trunk-T3I module consisting of —
a CMA14 (egress) circuit pack with a CMC6B (egress) I/O board
—
a CMA16 (ingress) circuit pack with a CMC14 (ingress) I/O board
—
ribbon cable connecting the egress I/O board to the ingress I/O board
DDM-1000 units for transmission via private line to the terminating device a pair of 728B coaxial cables originating on the J2 and J3 connectors of the I/O board and connecting to the DDM 1000 NOTE:
728B-90 coaxial cable is used if a 90° connector is required
One coaxial cable of the pair is the transmit side, J2 (T); the other coaxial cable is the receive side, J3 (R). at the remote end, a pair of 728B coaxial cables connecting the terminating DDM-1000 to the I/O board J2 and J3 ports NOTE:
728B-90 coaxial cable is used if a 90° connector is required
—
The DDM-1000 facility provides the crossover end-to-end transmit and receive.
—
With no DDM-1000 and a straight connection, each transmit coaxial cable must be connected with the receive connector for the opposite end.
The following figure illustrates this configuration.
3-22
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Cabling
BNS-2000 Series M2 Shelf
J2 (T)
CMA14
CMA16
CMC6B J3 P1 (R)
CMC14 P1
Ribbon Cable
728B 728B
DDM-1000
BNS-2000 Series M2 Shelf CMA16 CMC14 P1
Ribbon Cable
728B 728B
FIGURE 3-11.
DS3 Facility
~
J2 (T)
CMA14 CMC6B J3 P1 (R)
DDM-1000
Cabling Series M2 Shelf with Trunk-T3I
Data Networking Products M2 Trunk Module Reference, Issue 3
3-23
________________ M2 Trunk Module Cabling
TABLE 3-2.
Ordering Information
_____________________________________________________________________ Cable or ED5P055-31 Trunk Type Description Adapter Group Number _____________________________________________________________________ Trunk-E3/E3S _____________________________________________________________________ 75 Ω Micro-coaxial cable N11221-S35-B20 Trunk-E3A ATM-E3-BNC Coaxial cable with G(268),G(BD) one BT connector and one BNC connector _____________________________________________ ATM-E3-S Coaxial cable with G(267),G(BD) _____________________________________________________________________ BT connectors Trunk-T3/T3A/T3S/T3I 728B Coaxial cable G(233),G(AV) _____________________________________________ _____________________________________________________________________ 728B-90 90° Coaxial cable G(261),G(AV) For plenum cables, see Appendix B of the Data Networking Products Cabling Guide.
3-24
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
StarKeeper II NMS Administration
4-3
Command Set
4-3
Parameter Considerations
4-4 4-4 4-5 4-5 4-5 4-5 4-5 4-6 4-6 4-6 4-6 4-6 4-7 4-7 4-7 4-7 4-8
Trunk Module Type Comment Number of User Channels Call Screening Profile ID Trunk Weight DQDB Bus Indication Threshold Profile ID Inter-Carrier Interface (ICI) ATM Interface Cell Payload Scrambling Header Error Correction Transmit Reference Clock Virtual Path LOS Standard Trail Trace Address Trunk-T3A/E3A to ATM Switch
Procedures
4-11
Reports
4-16
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
When all appropriate group, profile, trace, and threshold information has been entered, and for the Trunk-T3A/E3A, the ATM Feature Package is installed and, if necessary, Stratum 4 Clock information configured, you can complete the database entry forms provided in the Appendix and begin trunk administration. If these database elements have not been added to the database with the group, profile, ssm4/str4, trace, and threshold commands, or the ATM Feature Package is not installed, refer to the Node Reference before continuing with the procedures in this chapter.
StarKeeper II NMS Administration StarKeeper II NMS provides a variety of tools to support administration of trunks that interconnect nodes in a network. StarKeeper II NMS Network Builder analyzes the interconnections for the best choices for session maintenance, and makes standard trunk administration consistent. StarKeeper II NMS Network Monitor provides an overview of the system consistent with the current status of each node and trunk, a continual view of the status and integrity of the network, and diagnostic capability. StarKeeper II NMS Performance Reporter collects reports on network performance. Trunk administration via StarKeeper II NMS uses Network Builder and the cut-through mode of StarKeeper II NMS. Trunk command entry and execution via StarKeeper II NMS is similar to command entry and execution on the direct console connection. Some of the same abbreviations are not allowed, however, nor is input information validated. Refer to the appropriate StarKeeper II NMS documentation for information on accessing the cut-through mode for your node.
Command Set Information regarding the disposition of trunks with errors is initially entered into the database with the node commands. With the automatically remove trunks with errors? parameter, trunk modules can be taken out of service when a specified error threshold is reached. The response to the parameter after how many error packets (per two minutes) specifies the error threshold. See the Node Reference. Trunk module configuration information is added to the database, and then manipulated and checked, with the enter, change, delete, and verify trunk commands. These commands are used frequently during trunk administration. The enter and change commands have extensive parameter prompting sequences for configurable options. These options can then be checked with the verify command, or removed from the database with the delete command.
Data Networking Products M2 Trunk Module Reference, Issue 3
4-3
________________ M2 Trunk Module Administration
Trunk module service states are controlled by the restore and remove commands. These commands affect call processing on trunks, and are often used with administration and maintenance procedures. The verify oosmods command lists all out-of-service modules. When a trunk carrying connectionless traffic is removed from service, this traffic is automatically rerouted to other trunks, if other suitable trunks are in service. Some delay and/or loss of data may occur before the other trunks take over. The diagnose trunk, dmeas trunk, dstat trunk, display connections, and display traffic commands are used for trunk module maintenance and troubleshooting. The Node Reference, Volume 2 documents all other command objects that are related to trunk modules. Table 4-1 lists all commands related to trunk module administration.
TABLE 4-1. Trunk Command Set _________________________________________________________________ _________________________________________________________________ Administration Operations Maintenance Related Objects routes change trunk remove trunk diagnose trunk connections ssm4*/str4* delete trunk restore trunk dmeas trunk group* enter trunk route trunk** dstat trunk measurements threshold* verify trunk node trace* oosmods traffic profile* _________________________________________________________________ * Must be entered before configuring a trunk in the database. ** Applies only to a configuration in which session maintenance has been administered through StarKeeper II NMS. See the Session Maintenance Guide.
Parameter Considerations Parameters that require special consideration because of the hardware configuration or the application being supported are explained in this section. The Syntax of the enter trunk section in the M2 Trunk Module Commands chapter, and the database entry forms in the Appendix give the correct prompting sequence for the module type being entered. In addition, the parameter definitions in the enter trunk section supplement the following explanations.
Trunk Module Type The TRUNK MODULE TYPE parameter enables you to specify the type of trunk module to be entered. Trunks that connect two nodes must be the same hardware type; that is, the trunk module type in one node must connect to the same trunk module type at the other node. The modules do not, however, have to be installed in the same numbered slots in both nodes.
4-4
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
Comment The COMMENT parameter enables you to enter a string of 1 to 60 characters to annotate a particular module with needed administrative information.
Number of User Channels When configuring trunk modules, you must specify the maximum number of channels (depending on the hardware type and the application) to be used for networking. The number of channels administered must be equal on both sides of the trunk, because the node does not negotiate between different channel ranges. When a channel mismatch occurs, calls originating from one node are completed, but calls originating from the other node may not go through.
Call Screening Profile ID Incoming calls entering the node through a trunk module can be made secure with trunk call screening—a set of security patterns used to check the destination address of calls at strategic points in a network to permit, deny, or limit access to a certain host, node, or set of nodes. These security patterns are specified in a call screening profile ID with the enter profile command. Once a call screening profile ID is administered, the same profile ID can be used for one or more trunk modules. (The same security patterns apply.) For details on trunk call screening, see the Planning Guide and the enter profile command in the Node Reference.
Trunk Weight Trunk weight is used when determining the shortest path for connectionless traffic. The number assigned as the weight of a trunk is used by the routing algorithm to provide connectionless traffic routing and load sharing between trunks. The routing algorithm gives more consideration to a trunk with a lower weight. The TRUNK WEIGHT parameter enables you to select a value (between 1 and 16) to specify the weight for Trunk-T3/E3, Trunk-T3A/E3A, and Trunk-T3S/E3S. Trunk weight must be configured identically for both the local and far-end trunk modules.
DQDB Bus Indication The Distributed Queue Dual Bus (DQDB) protocol is an IEEE 802.6 standard. The two sides of a transmission connection (buses) are denoted "A" and "B". Each DQDB is required to have a head of bus a and a head of bus b. For the Trunk-T3/E3, Trunk-T3S/E3S, and Trunk-T3I to comply with DQDB on a DS3 line, the trunk module at one end of the trunk must be configured as head of bus a and the trunk module at the other end configured as head of bus b. When a module is configured as head of bus a it transmits the bus A protocol and receives the bus B protocol; the head of bus b transmits the bus B protocol and receives the bus A protocol.
Data Networking Products M2 Trunk Module Reference, Issue 3
4-5
________________ M2 Trunk Module Administration
Threshold Profile ID Threshold profiles tune the limits of the physical performance parameters that are used to monitor the data transport error rate to trunk modules. The THRESHOLD PROFILE ID parameter enables you to specify a threshold profile identifier (ID). If a particular threshold profile ID is to be used, it must be configured with the enter threshold command before the trunk module is administered. If you are not using a pre-configured threshold profile ID, select default when prompted for the threshold profile ID.
Inter-Carrier Interface (ICI) The Trunk-T3I can be configured* for one of three Inter-Carrier Interface (ICI) applications. Nodes can then be interconnected in a public SMDS network maintained by Local Exchange Carriers (LECs) in different LATAs by an interexchange carrier (IC), as well as those within the same LATA.
ATM Interface When the ATM Feature Package is installed, the ATM interface type, user–network interface (uni), or network–node interface (nni), must be configured for a Trunk-T3A or Trunk-E3A. The configuration for this parameter should match on both ends of the link. See Table 4-2 for TrunkT3A/E3A to ATM parameter requirements.
Cell Payload Scrambling For the Trunk-T3A/E3A, the CELL PAYLOAD SCRAMBLING parameter provides the ability to improve the security and robustness of the header error correction cell delineation mechanism that allows identification of the cell boundaries. When this option is configured, it helps to improve the transmission performance by randomizing the data in the information field. For a direct connection between two BNS-2000 nodes, you should configure cell payload scrambling identically on both the local and far end. See Table 4-2 for Trunk-T3A/E3A to ATM parameter requirements.
Header Error Correction For the Trunk-T3A/E3A, the HEADER ERROR CORRECTION parameter is used to determine whether single-bit error correction is in effect. When the option is configured as on, single-bit errors are corrected, and multi-bit errors are detected and discarded. When the option is configured as off, both single-bit and multi-bit errors are detected and discarded. ________________ * Trunk-T3I configuration should be administered through StarKeeper II NMS. Refer to the StarKeeper II NMS Graphics System Guide.
4-6
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
Transmit Reference Clock For the Trunk-T3A/E3A, the TRANSMIT REFERENCE CLOCK parameter is used to specify the source from which the I/O board will derive its transmit clocking. These options are local—on board oscillator clock, stratum—Stratum 4 Clock on the node, and facility—the incoming signal from the line. The default is facility. The following configurations are the recommended for the TRANSMIT REFERENCE CLOCK : For a connection to a GlobeView-2000 Broadband System ATM switch, configure the timing source as facility. For a direct connection between two BNS-2000 nodes, set the transmit reference clock to facility, local, or stratum depending on your network configuration. NOTE:
If the transmit reference clock on one end is set to facility, the other end should be stratum or local.
If the Stratum 4 Clock is to be the timing source, it must be installed and configured on the node before the Trunk-T3A/E3A is configured. Refer to the Node Reference for switch setting and jumper position information, and the Commands Reference for Stratum 4 Clock database configuration information. The timing source local does not depend on the far-end configuration, or on the Stratum 4 Clock, therefore, it can be used when the other timing sources are not available. It is also used for testing purposes.
Virtual Path The Trunk-T3A/E3A converts segments it receives from the backplane into ATM cells to be transmitted on a facility, and a single virtual path (VP) is used to carry this traffic between a pair of BNS-2000 nodes. The VIRTUAL PATH NUMBER parameter is used to specify a number (from 1 to 31) to identify the VP over which this traffic is to travel. Only a single virtual path identifier (VPI) is allowed. The setting should match with that of the far-end link. If AAL5/ATM is supported, an additional VP is used.
LOS Standard When administering the Trunk-E3A, a value specifying the loss of signal (LOS) standard as either G.775 (CCITT) or RC8811 (BT) must be configured. Depending on the standard selected, LOS is detected by the absence of signal transitions on the incoming signal for a period of time, or not at all.
Trail Trace Address A trail trace address is used for the transport of 15 ASCII characters required for the E.164 numbering format. The trail trace address repeatedly transmits a trail access pointer identifier so that a trail receiving terminal can verify its continued connection to the intended transmitter. Both a TRANSMIT TRAIL TRACE ADDRESS and an EXPECTED TRAIL TRACE ADDRESS are configured for the Trunk-E3A. See Table 4-2 for local and far-end settings.
Data Networking Products M2 Trunk Module Reference, Issue 3
4-7
________________ M2 Trunk Module Administration
Trunk-T3A/E3A to ATM Switch For a BNS-2000 to GlobeView–2000 System configuration, the ATM DS3/E3 line card (LC) must be administered for compatibility with the connecting Trunk-T3A/E3A module parameters. Table 4-2 illustrates the correlation between the trunk module parameter options and the ATM LC options. Refer to the Node Reference and the appropriate GlobeView–2000 System documentation for additional information. For AAL5, additional virtual paths (up to a maximum of two) must be added on the ATM switch depending on the number of channels configured: For up to 4096 configured channels, add one additional VP on the ATM switch For 4097 to 8192 configured channels, add two additional VPs on the ATM switch NOTE:
Refer to Table 4-2. You must choose a virtual path number for the node from the range of 1 through 31 (VIRTUAL PATH NUMBER parameter). When using AAL5, you must add either one (if up to 4096 configured channels on the node) or two (if 4097 to 8192 configured channels on the node) additional virtual path numbers on the node. For example, if you select virtual path number 1 for the node, and you have up to 4096 channels on the node, you must have virtual path numbers 1 and 2 configured on the ATM switch. If you select virtual path number 1 for the node and have between 4097 and 8192 channels configured, you must configure virtual paths 1, 2, and 3 on the ATM switch.
TABLE 4-2. Formulas for Virtual Path Numbers __________________________________________________ Virtual Path Trunk Channels Virtual Paths Configured on the Node Configured on the ATM Switch __________________________________________________ N N, N+1 __________________________________________________ 1 through 4096 N N, N+1, N+2 __________________________________________________ 4097 through 8192
Additionally, the bandwidth on each VP number should be controlled according to your specific traffic requirements. The GlobeView-2000 System ATM circuit can be provisioned as a CBR or VBR as stated below.
4-8
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
BNS-2000 to GlobeView–2000 System Parameter Mapping _______________________________________________________________________ _______________________________________________________________________ BNS-2000 GlobeView–2000 System Trunk-T3A/E3A DS3/E3 LCa _______________________________________________________________________ ATM Interface Type Facility Interface Type uni uni _______________________________________________________________________ nni external nni b DS3/E3 LC ____________________________________ Header Error Correction HEC Error Correction _______________________________________________________________________ on or off enable or disable c DS3/E3 LC ____________________________________ Virtual Path Identifier (VPI) Virtual Path Number _______________________________________________________________________ 1-31 (see note on previous page) Matching option b Trunk-E3A E3 LC _______________________________________________________________________ Expected Trail Trace Transmit Trail Trace Address 1 to 15 digits Matching option ________________________________________ ________________________________________ Transmit Trail Trace Expected Trail Trace Address 1 to 15 digits Matching option ________________________________________ ________________________________________ Payload Scramble/Descramble Cell Payload Scrambling on enable off disable ________________________________________ ________________________________________ Loss Detection Option LOS Standard _______________________________________________________________________ g.775 or rc8811 CCITT or BT E3 LC ____________________________________ No equivalent option Transmit Reference Clock facility _______________________________________________________________________ Parity Mode CBIT Parity Violation Mode off p-bit on c-bit _______________________________________________________________________ ____________________________________ DS3 LC Onlyb No equivalent option Cell Payload Scrambling off _______________________________________________________________________ DS3P LC Onlyb ____________________________________ Payload Scramble/Descramble Cell Payload Scrambling on enable off disable _______________________________________________________________________
TABLE 4-2.
a Logical Termination Point Form; b Logical Termination Point Profile Form; c VP/VCs Form
Data Networking Products M2 Trunk Module Reference, Issue 3
4-9
________________ M2 Trunk Module Administration
Table 4-3 shows the options to be administered for the LC that have no corresponding trunk module parameter. The GlobeView-2000 System ATM circuit can be provisioned as a CBR or VBR circuit type. A CBR connection should be used to dedicate a full DS3/E3 facility through the ATM network. A VBR connection should be used to take advantage of the variable load on the BNS-2000 internodal trunk, which will be less than 100%. Refer to the Node Reference and the appropriate GlobeView–2000 System documentation for additional information.
TABLE 4-3. DS3/DS3P/E3/E3P Line Card Parameters ________________________________________________ ________________________________________________ Parameter Option a VP Allocation Leave blank ________________________________________________ Circuit Typeb ________________________________________________ VP Delay Priorityc CBR Traffic High d,e VBR Traffic ________________________________________________ Low ________________________________________________ Traffic Description Typec NoClpNoScr Total Peak Cell Ratec For DS3 LC ____________________________________ 96000 ________________ ________________________________________________ 80000 For E3 LC
a Logical Termination Point Form; b VP/VCs Form; c Traffic Profile Form; d For ports associated with the VP connection, the option "CLP1 Transmit Buffer Threshold" in the "Logical Termination Profile" form should be set to 3481. (The option "CLP1 Transmit Buffer Threshold" is only available on the DS3P and E3P cards.) e For a VBR circuit, the parameter "Usage Factor" in the "Provision VP/VC" form should be set taking into account the expected internodal trunk utilization to allow the GlobeView-2000 System to overbook its resources.
4-10
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
Procedures A trunk module does not have to be physically installed before its database information is configured. For routine administration and operations procedures, such as removing and restoring modules to service or displaying module hardware status, module installation is required. When administering a Trunk-T3A or Trunk-E3A to connect to a GlobeView-2000 System ATM switch, check with the GlobeView-2000 System administrator to make sure the options selected for the ATM LC are compatible with the trunk module parameter options for this configuration. (See Tables 4-2 and 4-3.) If AAL5 is used, be sure the correct number of virtual paths have been added based on the number of channels configured: For up to 4096 configured channels, add one VP For 4097 to 8192 configured channels, add two VPs. To enter or change trunk database information, follow Procedure 4-2 or Procedure 4-3. To transfer or duplicate trunk database information from one module address to another module address, follow Procedure 4-4 or Procedure 4-5. NOTE:
You cannot use the move and copy commands for a trunk module configured as a session maintenance trunk.
PROCEDURE 4-1. Preparing to Enter or Change Trunk Database Information 1. Check the output of the verify node command to determine whether the automatically remove trunks with errors parameter has been specified, and whether the specification is appropriate for your configuration. If necessary, use the change node command to make the required adjustments. See the Node Reference for details. 2. Check the output of the verify group, verify profile, verify threshold, verify trace, and verify ssm4/str4 commands to determine if the appropriate group name, profile ID, and threshold profile ID have been entered, as well as the necessary trace and Stratum 4 clocking information. If they do not appear in the database as required (they have been deleted, changed, or misspelled), refer to the Commands Reference for information to make the necessary adjustments. 3. When planning to move or copy trunk database information for a two-board (Trunk-T3I) module, make sure two contiguous slots are available.
Data Networking Products M2 Trunk Module Reference, Issue 3
4-11
________________ M2 Trunk Module Administration
PROCEDURE 4-2.
Entering a Trunk Module in the Database
1. Refer to Procedure 4-1. 2. Have your completed database entry forms available. Use enter trunk to begin module administration. To specify default values, press Return or + as illustrated in the prompted entry examples in M2 Trunk Module Commands. 3. Use verify trunk to check your entries. 4. To correct errors or change parameter specifications, use change trunk. 5. To start over, use delete trunk to eliminate all database entries. 6. If the trunk module has been installed, use restore trunk to place the module back into service.
PROCEDURE 4-3. Changing Trunk Database Configuration For minor database changes, such as adjustments to only a few parameters, follow Method 1. For database changes involving extensive configuration adjustments, follow Method 2. Method 1. Minor Changes 1. Use remove trunk to take the module out of service. 2. Use change trunk to make adjustments. 3. Use verify trunk to review changes. 4. Use restore trunk to place the module back into service. Method 2. Extensive Changes 1. Use verify trunk to display parameter options currently specified in the database. If necessary, complete or revise the database planning forms. 2. Use remove trunk to take the module out of service. 3. Use delete trunk to eliminate all database information. 4. Use enter trunk to re-enter all information in the database. 5. Use verify trunk to review changes. 6. Use restore trunk to place the module back into service.
4-12
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
PROCEDURE 4-4.
NOTE:
Moving Database Information to Another Module Address
The move module command does not duplicate ranges of numbers.
Method 1: 1. Use remove trunk to take the module out of service. 2. Use verify module to ensure that a database entry does not exist for the new module address. (If a database entry does exist for the specified module address, the move command fails.) 3. Use move module to transfer database information from one module address to another. 4. Physically move the hardware. 5. Use restore trunk to place the trunk module into service at the new address. Method 2: 1. If move module is not appropriate, use verify trunk to get a report of the configuration data. 2. Use remove trunk to take the trunk module out of service. 3. Use delete trunk to eliminate all information at the existing module address. 4. Use enter trunk to configure the information at the new module address. 5. Use verify module to check information entered at the new module address. 6. Physically move the hardware. 7. Use restore trunk to place the module back into service.
Data Networking Products M2 Trunk Module Reference, Issue 3
4-13
________________ M2 Trunk Module Administration
PROCEDURE 4-5.
Copying Database Information to Another Module Address
If an additional trunk module must be installed that requires exactly the same parameter specifications as a currently installed and configured trunk module, duplicate information from one module address to another with copy module or with a combination of verify module and enter trunk. NOTE:
The copy module command does not duplicate ranges of numbers.
Method 1: 1. Use remove trunk to take the module out of service. 2. Use verify module to ensure that a database entry does not exist for the new module address. (If a database entry does exist for the specified module address, the copy command fails.) 3. Use copy module to duplicate the database information from one module address to another. 4. Use restore trunk to place both trunk modules back into service. Method 2: 1. If copy module is not appropriate, use verify trunk to get a report of the existing configuration data. If necessary, complete the database planning forms. 2. Use enter trunk to configure the information at the new module address. 3. Use verify trunk to check information entered at the new module address.
4-14
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Administration
PROCEDURE 4-6.
Enabling Measurement Reports
Two types of trunk measurement reports are available: on-demand measurement reports, which are generated at the BNS-2000 console by executing the dmeas trunk command scheduled measurement reports, which are available from StarKeeper II NMS Performance Reporter To obtain either type of measurement report: 1. Enable the collection of measurement data for all trunk modules in the node. a. If you have StarKeeper II NMS in your network, refer to the StarKeeper II NMS Core System Guide for details. Enter yes in response to the NODE MONITORED BY StarKeeper II NMS prompt of the change node command so that your node is aware that it is monitored by StarKeeper II NMS. b. If you do not have StarKeeper II NMS in your network, enter schedule measurements trunk at the BNS-2000 console. NOTE:
This procedure only enables on-demand measurements.
2. In addition to Step 1, measurements must be enabled for each trunk module by entering yes in response to the ENABLE TRUNK MEASUREMENTS prompt of the enter trunk command.
Data Networking Products M2 Trunk Module Reference, Issue 3
4-15
________________ M2 Trunk Module Administration
Reports Table 4-4 explains the reports available to assist with analysis of module/network performance, system expansion, troubleshooting, and other routine tasks.
TABLE 4-4. Reports for Trunk Modules
_____________________________________________________________________________ _____________________________________________________________________________ Report Topic Command Description measurements dmeas trunk On-demand measurement reports detailing usage level of the trunk module. Module must be installed, and collection of measurements must be enabled. (See __________________________________________________________ Procedure 4-6.) verify schedule Reports availability of trunk measurement data. (See Procedure 4-6.) (Refer to the Node Reference for _____________________________________________________________________________ information for this command.) module data verify trunk Hardware/software module data currently configured __________________________________________________________ in the database. Module does not have to be installed. dstat trunk Hardware/software trunk module data. Module must be installed. _____________________________________________________________________________ out-of-service verify oosmods Lists all currently installed out-of-service modules. modules _____________________________________________________________________________ group data verify group Database information for a specific trunk group. _____________________________________________________________________________ connections dmeas connections Measurement reports for connections established __________________________________________________________ through the node for trunk groups. display connections PDD (predefined destination), PVC (permanent virtual circuit), and SVC (switched virtual circuit) information for modules or groups. __________________________________________________________ display traffic Lists established connections for modules, groups, or hosts. Segment counts are included. See the Node _____________________________________________________________________________ Reference. database size dbaudit A utility shell command that shows where database space expenditures occur. If dbresize is used, the database tables are readjusted automatically. See the Node Reference. _____________________________________________________________________________ trace connections verify trace Lists type of trace, trunk module address, source address, and destination address; shows whether the _____________________________________________________________________________ trace is on or off, and the time it was set. routing display routes Connectionless traffic routing information. See the _____________________________________________________________________________ Node Reference. I/O board clocking verify ssm4 Lists source type, service state, primary and secondary _____________________________________________________________________________ verify str4 references, and LOS timer information.
4-16
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
Problem Indicators Faceplate LEDs Command Output
5-3 5-3 5-4
Problem Areas
5-4
Procedures
5-6 5-9
Trunk Diagnostics
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
The Node Reference provides general troubleshooting information and a systematic approach to problem solving. Using methods outlined there, you can determine the problems that affect the entire node and isolate local problems to specific interface modules. This chapter provides problem indicators that are specific to trunk modules, a checklist of problem areas, and detailed remedial procedures, but does not explain problem indicators that are common to all modules, nor problem isolation techniques or procedures for connected SMDS subscriber equipment. Refer to the Node Reference and other vendor documents for this information. StarKeeper II NMS provides continual monitoring of the nodes that make up a network. Alarms from both ends of any facility are correlated, and a network map is available to spot any pending problems (see the StarKeeper II NMS Graphics System Guide). By combining these tools you can quickly identify trouble areas and then follow the diagnostics and other procedures documented in this chapter to further isolate and resolve problems.
Problem Indicators Module faceplate and I/O distribution board light-emitting diodes (LEDs) and the output of certain commands can indicate trunk problems.
Faceplate LEDs The LEDs on the module faceplates are green, yellow, and red. They indicate on-line, off-line, and fault states. When the module circuitry detects an on-board fault, the red LED (fault) is lit. When the Reset button is pressed, the module buffers and registers are cleared, and the module application program is restarted. The module is taken out of service, and all connections are terminated. In addition to the standard module status LEDs, the Trunk-T3/E3, Trunk-T3A/E3A, TrunkT3S/E3S, and Trunk-T3I module faceplates have a carrier failure alarm LED; when lighted, this LED indicates one of the following conditions: loss of signal (LOS) loss of frame (LOF) PLCP loss of frame (PLOF) alarm indication signal (AIS) receiving yellow alarm (DS3 Layer) receiving yellow signal (PLCP Layer) When the failure condition clears, or the module is taken out of service, the LED goes off.
Data Networking Products M2 Trunk Module Reference, Issue 3
5-3
________________ M2 Trunk Module Troubleshooting
Command Output The output of certain operations commands—such as diagnose trunk and others listed in Table 5-1—can indicate an existing or potential problem.
TABLE 5-1. Command Output _____________________________________________________________________________ _____________________________________________________________________________ Command Description Reference diagnose trunk Enables the running of off-line tests to Trunk Diagnostics procedures check the module hardware, and on-line M2 Trunk Module Commands loopback tests that isolate transmission path Appropriate vendor _____________________________________________________________________________ problems. documentation display traffic Shows established connections for modules, Procedure 5-3. Correcting groups, or hosts. Segment counts are Network Congestion on Trunks _____________________________________________________________________________ included. display connections Displays measurements reports for Procedure 5-3. Correcting connections established through the node, Network Congestion on Trunks giving a breakdown of connection failures, _____________________________________________________________________________ and optionally, of security failures. dstat trunk Displays fields showing numerical values Procedure 5-2. Obtaining Trunk that are counts of status packets indicating Status an error. Also gives module service state, Procedure 5-3. Correcting and hardware alarm information. Network Congestion on Trunks Procedure 5-4. Responding to Alarm Messages _____________________________________________________________________________ verify trunk Shows all parameter options configured for Procedure 5-3. Correcting a particular trunk module. Useful for Network Congestion on Trunks _____________________________________________________________________________ determining current channel allocations. display routes Shows how SMDS traffic is routed over Procedure 5-2. Obtaining Trunk connectionless trunks. Status _____________________________________________________________________________
Problem Areas Table 5-2 catalogs trunk module problem areas, listing occurrences that denote lack of or degradation of service, areas to begin troubleshooting, and troubleshooting information sources. Each suggested action is a point of departure for isolating and diagnosing trunk problems.
5-4
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
Module Problems Checklist ___________________________________________________________________________________ ___________________________________________________________________________________ √ Symptoms/Indicators Possible Causes Actions See Procedure 5-1. Solving Trunk cabling connection ____ No transmission in Bad ________________________ Problems. progress or able Faulty module Module ____________________________________ to be made ________________________ See Procedure 5-2. Obtaining Trunk or missing slot fuse ____ Red LED lit on trunk Blown ________________________ Status. module Module not in service ____________________________________ ____ Report alarm message ________________________ See Procedure 5-4. Responding to at capacity ____ dstat trunk output Trunk ________________________ Alarm Messages. ____________________________________ Incorrect routing indicates problems ________________________ See the Node Reference, Vol. 1 for slot are out of service information. ____ Carrier Failure Alarm Addresses ________________________ fuse ____________________________________ LED lit on Trunk-T3/E3/ Service address or trunk T3A/E3A/T3S/E3S/T3I module problems at remote end See the Node Reference, Vol. 2 for ____ Destination address not ________________________ routing information for connectionless trunks. board in loopback mode receiving data transmitted I/O ________________________ ____________________________________ over connectionless trunk Carrier failure See Trunk Diagnostics procedures. ____ Trunk in service, but ________________________ noise Facilities operating state is down ________________________ Parameter option mismatch ________________________ parameter option(s) Incorrect ________________________ ___________________________________________________________________________________ ATM connection problems See Procedure 5-3. Correcting at capacity ____ End users on trunks Trunk ________________________ Congestion on Trunks. report lost or garbled Channel allocation mismatch Network ____________________________________ data. between nodes See troubleshooting procedures in the ____ End users connected ________________________ Node Reference for connected devices outage through a common trunk Facilities ________________________ and end user problems. report slow responses. Facilities noise ____________________________________ ____ dmeas trunk output ________________________ Contact the provider of your Facilities interface (for transmission facilities for service. indicates potential modem) failure example, problem ________________________ ___________________________________________________________________________________ Problem with remote end See Trunk Diagnostics procedures. module ____ diagnose trunk output Faulty ____________________________________ ________________________ indicates problems Faulty connections See troubleshooting procedures in the ________________________ Node Reference for connected devices Problem with remote end and end user problems. device. ____________________________________ appropriate vendor documentation. See ____________________________________ See Procedure 5-10. Correcting Diagnostic Failure. ___________________________________________________________________________________ TABLE 5-2.
Data Networking Products M2 Trunk Module Reference, Issue 3
5-5
________________ M2 Trunk Module Troubleshooting
Procedures This section explains the considerations to take into account and the procedures to follow when troubleshooting a trunk module. Procedure 5-1. Solving Trunk Module Problems discusses common trunk problems and their resolutions. Procedure 5-2. Obtaining Trunk Status explains how to use the dstat trunk command to get status displays for the trunk indicating a problem. Procedure 5-3. Correcting Network Congestion on Trunks lists steps to follow to eliminate overloading. Procedure 5-4. Responding to Alarm Messages provides instructions for correcting conditions causing the alarm. For trunk command details, refer to the M2 Trunk Module Commands chapter. For additional information on trunk features, refer to the M2 Trunk Module Overview. The Trunk Diagnostics section contains procedures for running loopback tests.
PROCEDURE 5-1. Solving Trunk Module Problems For all trunks: 1. Take the following actions for any of these problems: lost or garbled data reported; red LED on the trunk module lit; green LED not lit; an error message on the console or printer; slow responses reported by end users connected through a common trunk, a. Make sure all connections are secure. b. Check all modems or DSUs. c. Enter verify trunk < mod addr > to determine whether the trunk is properly entered in the database, and display connections to see if the trunk is in service on both ends. d. Verify the jumper settings. Refer to the M2 Trunk Module Installation chapter for jumper setting details. e. Check all cable connections. Refer to the M2 Trunk Module Cabling chapter for detailed information. If no cable is connected, remove the module from service and ignore the message. f. If this does not solve the problem, run the trunk diagnostics to further isolate the problem. 2. When running loopback diagnostics, take the device out of loopback mode and rerun the test to confirm a failure. This proves that the previous looped data, which passed, was actually looped back at that test point. 3. Check the dstat trunk report to determine whether the problem is facility-related. See Procedure 5-2.
5-6
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-1.
Solving Trunk Module Problems (continued)
For connectionless trunks: 1. Check the display routes report to determine whether the problem is related to the routing status of the indicated trunk, inconsistent trunk weights, or incorrect source address/destination address information. Refer to the Node Reference, Volume 2 for information for this command. 2. If the problem appears to be facility related, run the appropriate diagnostic tests to isolate the problem and determine corrective action. For a Trunk-T3A or Trunk-E3A: 1. Use verify trunk to insure that a. the virtual path numbers on both ends of the connection are identical b. the cell payload scrambling options on both ends of the trunk match c. the transmit reference clock options are set correctly 2. If the Trunk-T3A/E3A is connected to an ATM switch, check the appropriate ATM documentation for configuration information, line card service state, trunk/line card options, and any other problems that appear to be trunk/ATM-switch related.
PROCEDURE 5-2. Obtaining Trunk Status Enter dstat trunk < mod addr > to display a status report for the indicated trunk module. Report fields that provide service state information are EXPECT SRVC STATE, ACTUAL SRVC STATE, and OPERATING STATE. Report fields indicating module or capacity problems include FM NODE OVERFLO, TO NODE OVERFLO, and MODULE RESET. Report fields that indicate connectionless trunk problems include LINE and FRAME Layer: ALARM IND SIGNAL, LOSS OF FRAME, LOSS OF SIGNAL, YELLOW ALARM, TRAIL TRACE OUT OF FRAME, TRAIL TRACE MISMATCH PLCP Layer: LOSS OF FRAME, YELLOW SIGNAL ATM Layer: VIRTUAL PATH ALARM INDICATION SIGNAL, VIRTUAL PATH FAR END RECEIVE FAILURE DQDB status: HEAD OF BUS
Data Networking Products M2 Trunk Module Reference, Issue 3
5-7
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-2.
Obtaining Trunk Status (continued)
In addition, the FTBL PARITY, ROUTER FILTER, and RTBL PARITY fields also indicate problems related to connectionless trunks. Report fields that indicate I/O board status include IO BOARD and IOB TEST.
PROCEDURE 5-3. Correcting Network Congestion on Trunks For all trunks: 1. Check the routing on each node to be sure that no possible loops exist. 2. Allocate more channels on the trunk, if possible, or change the routing so fewer calls are placed on the trunk. 3. For all I/O boards, check the cable length between the module and the DSU.
PROCEDURE 5-4. Responding to Alarm Messages 1. 2. 3. 4. 5. 6.
5-8
Refer to the Messages Reference for information for the alarm indicated. Check the activity preceding the alarm message, using the dmeas and dstat commands. Check the LEDs on the module faceplate. Check the cabling. Reseat or replace trunk modules or I/O boards that have failed diagnostics. Enter verify node to ensure that a node entry exists for the slot corresponding to the physical position in the Control Computer.
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
Trunk Diagnostics Trunk module diagnostics† are off-line tests run on the module hardware, and on-line loopback tests that isolate problems in a transmission path, such as an improper connection to a replaceable unit. It is recommended that trunk diagnostic tests be run for several repetitions. Diagnostic Tests
The following table lists, according to module, the diagnostic tests that are used to isolate trunk problems.
TABLE 5-3. Trunk Diagnostic Tests ____________________________________________ Trunk Type _____________________________ Test Type T3/T3A/T3S E3/E3A/E3S T3I ____________________________________________ local_lp √ √ √ _ ___________________________________________ √ manu_lp √ √ ____________________________________________ ____________________________________________ lnkrev √ √ √ node_remote √ √ _ ___________________________________________ √ no_loop √ √ ____________________________________________ ____________________________________________ mod_test √ √ √ √ line_farend* √ ____________________________________________ * The line_farend test can only be performed where the remote (far-end) equipment supports the C-bit parity based line loopback command.
This section is supplemented by information contained in the M2 Trunk Module Commands chapter, which explains the diagnostic prompting sequence and the meaning of each parameter and its options, and includes system responses. Trunk module diagnostics can be used when the module is first defined in the database and is physically installed when configuration changes are made when module integrity is in question
________________ † Diagnostic tests for session maintenance trunks should be run using StarKeeper II NMS. See the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
Data Networking Products M2 Trunk Module Reference, Issue 3
5-9
________________ M2 Trunk Module Troubleshooting
Testing Sequence
Tests should be run in a specified order to determine whether a problem exists with the trunks or with the facility. If the node remote test indicates a problem, subsequent tests are run sequentially to locate where, in the path, the fault lies. The following table shows the order for running diagnostic tests according to trunk module type.
TABLE 5-4. Diagnostic Testing Sequence ______________________________________________ Test T3/T3A/T3S/E3/E3A/E3S T3I ______________________________________________ Sequence 1. node_remote mod_test ______________________________________________ 2. ______________________________________________ mod_test local_lp ______________________________________________ 3. local_lp line_farend* 4. ______________________________________________ manual_lp manual_lp 5. ______________________________________________ line_farend* (T3/T3A/T3S only) * The line_farend test can only be performed where the remote (far-end) equipment supports the C-bit parity based line loopback command.
NOTE:
When running diagnostic tests, the trunk module downloads only at the beginning of the testing sequence. It does not repeat the download once a test has been completed, and additional tests are selected by responding yes to the CONTINUE TESTING? prompt.
Loopback Cables
Loopback cables are used with the diagnose trunk command to perform incremental loopback tests of the data circuit between the trunk module and the connected end device. The following table lists the loopback tests and the appropriate loopback cables for the various trunk modules.
TABLE 5-5. Loopback Cables ________________________________________________________ ED5P055-31 Cable Module Type Cable ________________________________________________________ Group Number Description Trunk-T3/T3A/ 728B Coaxial w/BNC G(233),G(AV) T3S/T3I ________________________________________________________ connectors Trunk-E3/E3S 75 Ω Coax with micro-coax N22332-S35-B20 connectors ________________________________________________________ Trunk-E3A ATM-E3-S Coax with BT G(267),G(BD) ________________________________________________________ connectors
5-10
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-5.
Starting Loopback Tests
Requirement: Trunk module is out of service (except for the node_remote test). 1. Before running diagnostics, put any modems in loopback mode. Attach appropriate loopback connectors and cables. Ensure that all loopback connectors and cables are installed properly. Improperly installed connectors and cables can produce diagnostic errors. See the M2 Trunk Module Installation chapter for installation procedures. 2. Verify the service state of the trunk module: verify trunk < mod addr >
PROCEDURE 5-6. Running the Node Remote Test on Trunk-T3/E3, Trunk-T3A/E3A, or Trunk-T3S/E3S Tests the health of the entire trunk and all connections up to and including the remote node. Requirements: Both local and remote trunk modules are in service; trunkloop channels are active. NOTE:
Wait a few minutes after restoring the trunk module to service before running this test. If you run the test too soon after restoring the trunk to service and before the channels become active, a message is displayed indicating that the trunk is inoperable.
1. Enter display connections to ensure that trunkloop channels 10 and 11 are active. 2. Enter diagnose trunk < mod addr > node_remote a. If the test passes, the trunk facility was most likely temporarily impaired. b. Enter dstat trunk < mod addr > to get an indication of the nature of the problem. Note the problem in the system record log along with a description. 3. If the test fails, check each piece of equipment and the trunk facility between the local and remote modules. Replace faulty equipment and repeat the test.
PROCEDURE 5-7. Running the Module Test Requirement: Module must be removed from service. 1. 2. 3. 4.
Enter diagnose trunk < mod addr > When prompted for TEST TYPE , enter mod_test If the test passes and a trunk problem still exists, run the local loopback test. If the test fails completely, a reason is displayed indicating the location of the problem (for example, I/O board not present ). Replace faulty equipment as needed and repeat the test.
Data Networking Products M2 Trunk Module Reference, Issue 3
5-11
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-8.
Running the Local Loopback Test
Requirement: Module must be removed from service. 1. Enter diagnose trunk < mod addr > 2. When prompted for TEST TYPE , enter local_lp 3. If the test passes and a trunk problem still exists, run the manual loopback test. 4. If the test fails completely, a reason is displayed indicating the location of the problem (for example, I/O board not present ). Replace faulty equipment as needed and repeat the test. 5. If error counts are reported: a. Check the connections for both the module and the I/O board and make sure they are properly secured. b. Reseat the module and/or I/O board. c. Check the module and I/O board, replacing faulty equipment as needed and repeat the test.
PROCEDURE 5-9. Running the Remote Loopback Test on Trunk-T3/E3, Trunk-T3A, Trunk-T3S/E3S, or Trunk-T3I Requirements: The trunk module must be in loopback mode. The short loopback coaxial cable is used to run a manual loopback through the local trunk module and its I/O board. For a remote trunk module, lnkrev is used. See Figure 5-1. NOTE:
If the remote location is inaccessible, the line_farend test is used instead of manu_lp. Not all line devices can respond, however, to the line_farend test. Make sure the remote (far-end) equipment supports the C-bit parity based line loopback command, and the CBIT PARITY CODE VIOLATION MODE for the trunk module is on before running line_farend. (The trunk module automatically puts the remote device into loopback mode for the line_farend test and returns it to operating mode after the test.)
1. Use loopback cable as specified in Table 5-5 to loop back the local I/O board. This can be done at both the near end and the far end. 2. Enter diagnose trunk < mod addr > 3. When prompted for TEST TYPE , enter manu_lp with coaxial cable at point a. 4. If the test passes, and the trunk problem still exists: a. Reconnect the facilities and repeat the test at point b. b. If the manu_lp test cannot be run, enter line_farend, if supported, at point b. c. If this test passes, and the problem still exists, reconnect the facilities and go to step 8.
5-12
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-9.
Running the Remote Loopback Test on Trunk-T3/E3, Trunk-T3A, Trunk-T3S/E3S, or Trunk-T3I (continued)
5. If the test fails completely (for example, the trunk module was not put into loopback mode), a reason description is displayed, such as Diagnostic FAILED: Receiver timedout . Check to make sure the module is in loopback mode and repeat the test. 6. If the test continues to fail or if error counts are reported: a. Reseat the module and/or the I/O board, checking all connections to make sure they are properly secured. b. Replace faulty equipment as needed, and repeat the test. 7. Remove the loopback cable on the I/O board and replace both coaxial cables to the facilities. 8. To loop back data at point c, enter diagnose trunk < mod addr > at the remote node console. 9. When prompted for TEST TYPE , at the remote trunk, enter lnkrev and wait for the diagnostic to complete. 10. Enter diagnose trunk < mod addr > at the local node console. 11. When prompted for TEST TYPE , enter manu_lp 12. If the test fails completely (for example, the remote trunk module was not put into loopback mode), a reason description is displayed. Follow any instructions displayed, and repeat the test. 13. If error counts are reported: a. Check the connections for the remote trunk module and I/O board to make sure they are properly secured. b. Replace faulty equipment as needed, and repeat the test. c. If error counts continue, contact your facility services provider. 14. When testing is complete, enter diagnose trunk < mod addr > at the remote node console. 15. When prompted for TEST TYPE , enter no_loop to restore the remote trunk module to normal service.
Data Networking Products M2 Trunk Module Reference, Issue 3
5-13
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-9.
Running the Remote Loopback Test on Trunk-T3/E3, Trunk-T3A, Trunk-T3S/E3S, or Trunk-T3I (continued)
Local Node
Module Test/ (mod_test)
CMA9/13/14/16/18 Local Loopback (local_lp)
CMC6/6B/13/14/15 J3
J4 a. ATM or DTF Remote Loopback (manu_lp or line_farend) b.
J3
J4
CMC6/6B/13/14/15 CMA9/13/14/16/18
c. Link Reverse (lnkrev)
Remote Node
FIGURE 5-1. Diagnostic Tests: Trunk-T3/E3, Trunk-T3A, Trunk-T3S/E3S, and Trunk-T3I
5-14
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-10.
Running the Remote Loopback Test on Trunk-E3A
Requirements: The trunk module must be in loopback mode. The short loopback coaxial cable is used to run a manual loopback through the local trunk module and its I/O board. For a remote trunk module, lnkrev is used. See Figure 5-2. 1. Use loopback cable as specified in Table 5-5 to loop back the local I/O board. This can be done at both the near end and the far end. 2. Enter diagnose trunk < mod addr > 3. When prompted for TEST TYPE , enter manu_lp with coaxial cable at point a. 4. If the test passes, and the trunk problem still exists: a. Reconnect the facilities and repeat the test at point b. b. If this test passes, and the problem still exists, reconnect the facilities and go to step 8. 5. If the test fails completely (for example, the trunk module was not put into loopback mode), a reason description is displayed, such as Diagnostic FAILED: Receiver timedout . Check to make sure the module is in loopback mode and repeat the test. 6. If the test continues to fail or if error counts are reported: a. Reseat the module and/or the I/O board, checking all connections to make sure they are properly secured. b. Replace faulty equipment as needed, and repeat the test. 7. Remove the loopback cable on the I/O board and replace both coaxial cables to the facilities. 8. To loop back data at point c, enter diagnose trunk < mod addr > at the remote node console. 9. When prompted for TEST TYPE , at the remote trunk, enter lnkrev and wait for the diagnostic to complete. 10. Enter diagnose trunk < mod addr > at the local node console. 11. When prompted for TEST TYPE , enter manu_lp 12. If the test fails completely (for example, the remote trunk module was not put into loopback mode), a reason description is displayed. Follow any instructions displayed, and repeat the test. 13. If error counts are reported: a. Check the connections for the remote trunk module and I/O board to make sure they are properly secured. b. Replace faulty equipment as needed, and repeat the test. c. If error counts continue, contact your facility services provider. 14. When testing is complete, enter diagnose trunk < mod addr > at the remote node console. 15. When prompted for TEST TYPE , enter no_loop to restore the remote trunk module to normal service.
Data Networking Products M2 Trunk Module Reference, Issue 3
5-15
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-10.
Running the Remote Loopback Test on Trunk-E3A (continued)
Local Node
Module Test/ (mod_test)
CMA18 Local Loopback (local_lp)
CMC16 J6
J5 a. ATM or DTF
Remote Loopback (manu_lp) b.
J6
J5
CMC16 CMA18
c. Link Reverse (lnkrev)
Remote Node
FIGURE 5-2. Diagnostic Tests: Trunk-E3A
5-16
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ M2 Trunk Module Troubleshooting
PROCEDURE 5-11.
Correcting Diagnostic Failure
1. Replace the failed module. 2. If this does not correct the problem, replace the appropriate I/O board. 3. Check the slot voltage and fuse. Refer to the Node Reference for detailed instructions.
PROCEDURE 5-12. Completing Trunk Tests 1. Restore the module to service: restore trunk < mod addr > 2. Verify that the module has been restored to service: verify trunk < mod addr >
Data Networking Products M2 Trunk Module Reference, Issue 3
5-17
________________ M2 Trunk Module Commands change trunk delete trunk diagnose trunk dmeas trunk dstat trunk enter trunk remove trunk route trunk restore trunk verify trunk System Responses
Data Networking Products M2 Trunk Module Reference, Issue 3
6-4 6-10 6-11 6-24 6-34 6-46 6-58 6-59 6-62 6-63 6-68
________________ M2 Trunk Module Commands
This chapter describes the commands related to the administration, operation, and maintenance of a trunk module. Commands appear in alphabetical order by verb. System responses for all trunk commands conclude this chapter. The enter trunk command, used for initial trunk module administration, gives the full prompting sequence and contains a list of parameter definitions. The database entry forms provided in the Appendix also follow the prompting sequence for entering each module type. Additional parameter information for enter trunk and change trunk is provided in the M2 Trunk Module Administration chapter. Procedures for running diagnostic commands are found in M2 Trunk Module Troubleshooting. Other command objects that are related to the administration, operation, and maintenance of trunk modules are documented in the Node Reference.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-3
________________ change trunk
change trunk Depending on the service state of the trunk module, the change trunk command enables you to modify certain trunk module parameters that are currently administered in the database. The following restrictions apply: The TRUNK MODULE TYPE , MODULE ADDRESS , SESSION MAINTENANCE TRUNK , APPLICATION TYPE , and ICI TYPE parameters cannot be changed with change trunk. To change these parameters, trunk module information must be deleted and re-entered with delete trunk and enter trunk. You can use the move module command to change the MODULE ADDRESS parameter. The M2 Trunk Module Administration chapter provides information for this procedure. When the trunk module is in service, only the following parameters can be changed CALL SCREENING PROFILE ID CARRIER CODE FOR THE FAR END CBIT PARITY CODE VIOLATION MODE COMMENT CELL PAYLOAD SCRAMBLING ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK HEADER ERROR CORRECTION LATA ID FOR THE FAR END LOSS OF SIGNAL STANDARD TRUNK WEIGHT THRESHOLD PROFILE ID
Syntax
You can use change trunk in prompted entry only. The command syntax for enter trunk and change trunk are similar for out-of-service trunks. The defaults for change trunk are those values, conditions, or states that currently exist in the database. They are displayed within parentheses in the parameter prompt. Parameters
Refer to the parameter definitions supplied in the enter trunk section.
6-4
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ change trunk
Prompted Entry: Changing Information for an In-service Trunk-T3I CC0> change OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 24 LATA ID FOR THE FAR END [1-99999: +(12)]: + CARRIER CODE FOR THE FAR END [0000-9999: +(1234)]: + COMMENT [up to 60 chars double quoted: +("this is an ic trunk")]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: 15 ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(yes)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: on MODULE ADDRESS:
CC0>
Prompted Entry: Changing Information for an Out-of-service Trunk-T3I CC0> change OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 24 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [special, standard: +(standard)]: + LATA ID FOR THE FAR END: [1-99999: +(12)]: + CARRIER CODE FOR THE FAR END [0000-9999: +(1234)]: + MAXIMUM NUMBER OF CONCURRENT DATA UNITS (MCDU) [128, 512: +(128)]: 512 COMMENT [up to 60 chars double quoted: +("this is an ic trunk")]: + DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(yes)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: on MODULE ADDRESS: CC0>
Data Networking Products M2 Trunk Module Reference, Issue 3
6-5
________________ change trunk
Prompted Entry: Changing Information for an In-service Trunk-T3 CC0> change OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 22 COMMENT [up to 60 chars double-quoted: +("t3 is in 22")]: "t3 is in slot 22" TRUNK WEIGHT [1-16: +(4)]: 3 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: yes CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: on CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
Prompted Entry: Changing Information for an Out-of-service Trunk-T3
*
CC0> change OBJECT [...trunk...]: trunk MODULE ADDRESS: 22 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + SESSION MAINTENANCE TRUNK [yes, no: +(no)]: + COMMENT [up to 60 chars double quoted, none: +("t3 is in 22")]: "t3 is in slot 22" GROUP [up to 8 chars: +(trkgrp)]: + NUMBER OF USER CHANNELS [1-8172: +(32)]: 520 TRUNK WEIGHT [1-16: +(4)]: + DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: 1 ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: yes CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: on CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
6-6
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ change trunk
Prompted Entry: Changing Information for an In-service Trunk-T3A CC0> change OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 9 COMMENT [up to 60 chars double-quoted: ("t3a in 9 and VP number is 2")]: + TRUNK WEIGHT [1-16: +(2)]: 1 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + CELL PAYLOAD SCRAMBLING [on, off: +(off)]: on HEADER ERROR CORRECTION [on, off: +(off)]: on ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: on CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
Prompted Entry: Changing Information for an Out-of-service Trunk-T3A CC0> enter OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 9 VIRTUAL PATH NUMBER [1-31: +(2)]: 4 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + COMMENT [up to 60 chars double-quoted]: ("t3a in 9 and VP number is 2")]: "t3a in 9 and VP number is 4" GROUP [up to 8 chars: +(test)]: + NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(2)]: 1 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + TRANSMIT REFERENCE CLOCK [local, stratum, facility: +(facility)]: local ATM INTERFACE TYPE [uni, nni: +(nni)]: uni CELL PAYLOAD SCRAMBLING [on, off: +(off)]: on HEADER ERROR CORRECTION [on, off: +(off)]: on ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
Data Networking Products M2 Trunk Module Reference, Issue 3
6-7
________________ change trunk
Prompted Entry: Changing Information for an In-service Trunk-E3A CC0> change OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 10 COMMENT [up to 60 chars double-quoted: ("e3a in 10 and VP number is 2")]: + TRUNK WEIGHT [1-16: +(2)]: 1 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + CELL PAYLOAD SCRAMBLING [on, off: +(off)]: on HEADER ERROR CORRECTION [on, off: +(off)]: on LOSS OF SIGNAL STANDARD [rc8811, g.775: +(g.775)]: rc8811 ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
Prompted Entry: Changing Information for an Out-of-service Trunk-E3A CC0> enter OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 10 VIRTUAL PATH NUMBER [1-31: +(2)]: 4 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + COMMENT [up to 60 chars double-quoted]: ("t3a in 10 and VP number is 2")]: "t3a in 10 and VP number is 4" GROUP [up to 8 chars: +(test)]: + NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(2)]: 1 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + TRANSMIT REFERENCE CLOCK [local, stratum, facility, : +(facility)]: local ATM INTERFACE TYPE [uni, nni: +(nni)]: uni CELL PAYLOAD SCRAMBLING [on, off: +(off)]: on HEADER ERROR CORRECTION [on, off: +(off)]: on LOSS OF SIGNAL STANDARD [rc8811, g.775: +(g.775)]: rc8811 EXPECTED TRAIL TRACE ADDRESS [up to 15 digits, none: +(211838348888887)]: 211838348 TRANSMIT TRAIL TRACE ADDRESS [up to 15 digits, none: +(211818359999999)]: 211818359 ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
6-8
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ change trunk
Prompted Entry: Changing Information for an In-service Trunk-T3S CC0> change OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS:+ COMMENT [up to 60 chars double-quoted: ("t3s in 12")]: + TRUNK WEIGHT [1-16: +(2)]: 1 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: on CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
Prompted Entry: Changing Information for an Out-of-service Trunk-T3S CC0> enter OBJECTS [..., trunk, ...]: trunk MODULE ADDRESS: 12 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + COMMENT [up to 60 chars double-quoted]: ("t3s in 12")]: + GROUP [up to 8 chars: +(test)]: + TRUNK WEIGHT [1-16: +(4)]: 1 DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + MODULE ADDRESS: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-9
________________ delete trunk
delete trunk The delete trunk command enables you to eliminate trunk module information from the database. Before you can delete any information, the trunk module must be out of service. You cannot delete trunk module information while the module is downloading software. Syntax
You can use delete trunk in prompted entry or one-line entry. CC0> delete OBJECT [...trunk...]: trunk MODULE ADDRESS:
Parameters
Refer to the parameter definitions supplied in the enter trunk section. Prompted Entry: Deleting Trunk Information
CC0> delete OBJECT [...trunk...]: trunk MODULE ADDRESS: 55 CC0>
One-line Entry: Deleting Trunk Information CC0> delete trunk 55
6-10
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ diagnose trunk
diagnose trunk The diagnose trunk command initiates loopback tests for a trunk module and enables you to isolate network problems. This section is supplemented by Trunk Diagnostics in the M2 Trunk Module Troubleshooting chapter. Syntax
You can use diagnose trunk in prompted entry or one-line entry. The diagnose trunk command includes extensive prompts, informational messages, and system responses. This Syntax section provides significant portions of this information; System Responses supplements it. CC0> diagnose OBJECT [...trunk...]: trunk MODULE ADDRESS: For a Trunk-T3/T3A/T3S: TEST TYPE [mod_test, local_lp, lnkrev, no_loop, line_farend, node_remote, manu_lp: +(local_lp)]: For a Trunk-E3/E3A/E3S: TEST TYPE [mod_test, local_lp, lnkrev, no_loop, node_remote, manu_lp: +(local_lp)]: If TEST TYPE is "mod_test": If TEST TYPE is "local_lp": TEST DURATION IN SECONDS [10-2400: +(10)]: REPETITIONS [1-1000; ’c’ for continuous: +(1)]: DISPLAY ERRORED DATA? [yes, no: +(yes)]: If TEST TYPE is "lnkrev" or "no_loop": If TEST TYPE is "node_remote" and the module is in service: If TEST TYPE is "node_remote" and the module is out of service: REPETITIONS [1-1000, or ’c’: +(1)]: Diagnose not completed - module must be in service before attempting Node-remote diagnose. If TEST TYPE is "node_remote" and the remote module is out of service: REPETITIONS [1-1000, or ’c’: +(1)]: M Cannot communicate with remote trunk. LOOP AROUND DIAGNOSTIC FAILED If TEST TYPE is "line_farend" or "manu_lp": TEST DURATION IN SECONDS [10-2400: +(10)]: REPETITIONS [1-1000, or ’c’: +(1)]: If TEST TYPE is "manu_lp": DISPLAY ERRORED DATA? [yes, no: +(yes)]: INFO: Place the remote device in loop-around mode. CONTINUE TESTING [yes, no: +(yes)]:
Data Networking Products M2 Trunk Module Reference, Issue 3
6-11
________________ diagnose trunk
Syntax (continued) For a Trunk-T3I: TEST TYPE [mod_test, local_lp, lnkrev, no_loop, line_farend, manu_lp: +(local_lp)]: If TEST TYPE is "mod_test": If TEST TYPE is "local_lp": TEST DURATION IN SECONDS [10-2400: +(10)]: REPETITIONS [1-1000; ’c’ for continuous: +(1)]: DISPLAY ERRORED DATA? [yes, no: +(yes)]: If TEST TYPE is "lnkrev" or "no_loop": If TEST TYPE is "line_farend" or "manu_lp": TEST DURATION IN SECONDS [10-2400: +(10)]: REPETITIONS [1-1000, or ’c’: +(1)]: DISPLAY ERRORED DATA? [yes, no: +(yes)]: If TEST TYPE is "manu_lp": INFO: Place the remote device in loop-around mode. CONTINUE TESTING [yes, no: +(yes)]:
6-12
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ diagnose trunk
Parameters
This section explains parameters in the diagnose trunk prompting sequence that differ from those in enter trunk. Refer to the Syntax section for the prompting sequence, system defaults, and parameter options. CONTINUE TESTING
Specifies whether (yes or no) diagnostic testing should be continued. DISPLAY ERRORED DATA
Specifies whether (yes or no) the errored segment data report is to be displayed. See Test Results for a sample Errored Segment Data Report. MODULE ADDRESS
A single number identifying the node slot that the trunk module occupies. Only a single module address can be entered. REPETITIONS
Specifies whether a particular test is to be run 1 to 1000 times (inclusive) or if continuous testing (c) should occur. You can stop continuous testing by pressing Delete to stop continuous testing. TEST DURATION IN SECONDS
If TEST TYPE is local_lp or manu_lp, specifies the duration of data transmission to be from 10 to 2400 seconds. This information is passed to the module. NOTE:
This test renders the system console inoperative for the duration of the test.
TEST TYPE
Specifies the type of test to be run. With each loopback test, data originates at the trunk module and is looped to the particular test point. If the remote end device (the far end) can interpret the facility (or data link [DL] commands), the module automatically puts the remote device into loopback mode for the testing and returns it to operating mode after the test. If the remote end device cannot interpret DL commands, the manu_lp test—which requires that the remote device be put into loopback mode manually—can be run. If a test is a total failure, the problem area is indicated. If a test is a partial failure, error measurements are reported. Refer to Test Results. lnkrev An option that puts the trunk module into loopback mode to echo incoming (external) data back to its source. It must be specified on the remote node before running manu_lp on the local node. In addition, the remote module must be taken out of loopback mode with the no_loop option before restoring the trunk to service. local_lp Specifies that data is to be looped from the trunk module board to its I/O board. Any error implies a local loopback test failure.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-13
________________ diagnose trunk
Parameters (continued)
manu_lp Verifies link quality between the local trunk module and any remote facility device that does not support data link (DL) commands. The remote device is put into loopback mode manually. When testing is completed, the remote device must be returned to normal mode. mod_test Checks various parts of the module hardware. It includes boot checks and component and subsystem tests. node_remote For Trunk-T3/E3, T3A/E3A, or T3S/E3S, verifies the health of the entire trunk, up to and including the remote node; test results indicate any node fault. (Both the local and remote trunk modules must be in service when this test is run.) no_loop Takes the trunk module out of loopback mode. After running reverse_trk to perform the remote_trk test from the other node, run no_loop to return the trunk module to nonlooping mode. For the trunk module previously put into reverse looping mode, no_loop must be executed before the module can be restored. line_farend If the Trunk-T3/T3A/T3S/T3I supports C-bit parity signaling for loopback commands, line_farend tests the link quality between the trunk module and the remote device. The trunk module automatically puts the remote device into loopback mode for the testing and returns it to operating mode after the test.
6-14
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ diagnose trunk
Prompted Entry: Running Trunk-T3/T3A/T3S Tests CC0> diagnose OBJECT [...trunk...]: trunk MODULE ADDRESS: 9 TEST TYPE [mod_test, local_lp, lnkrev, no_loop, node_remote, line_farend, manu_lp: +(local_lp)]: + TEST DURATION IN SECONDS [10-2400: +(10)]: + REPETITIONS [1-1000; ’c’ for continuous: +(1)]: +
Prompted Entry: Running Trunk-E3/E3A/E3S Tests CC0> diagnose OBJECT [...trunk...]: trunk MODULE ADDRESS: 10 TEST TYPE [mod_test, local_lp, lnkrev, no_loop, node_remote, manu_lp: +(local_lp)]: + TEST DURATION IN SECONDS [10-2400: +(10)]: + REPETITIONS [1-1000; ’c’ for continuous: +(1)]: +
Prompted Entry: Running Trunk-T3I Tests CC0> diagnose OBJECT [...trunk...]: trunk MODULE ADDRESS: 24 TEST TYPE [mod_test, local_lp, lnkrev, no_loop, line_farend, manu_lp: +(local_lp)]: + TEST DURATION IN SECONDS [10-2400: +(10)]: + REPETITIONS [1-1000; ’c’ for continuous: +(1)]: +
Data Networking Products M2 Trunk Module Reference, Issue 3
6-15
________________ diagnose trunk
Test Results
Test results for a trunk module can be a total success, a total failure, or a partial failure. If a test is a total success, appropriate system responses are output. If the Delete key is pressed, the diagnostic exits and the CC0> prompt reappears. If a test fails completely, messages such as the following appear: XXX_XXX Diagnostic failed Cannot put far end device into loopback mode. Diagnostic FAILED: CF Alarms - LOS LOF PLOF YALM Warning: cannot detect far-end loopback
Refer to System Responses for a complete list of these messages and their explanations. To monitor facility performance more fully, error counts are provided for code violations (CV), line code violations (LCV), line errored seconds (LES), line severely errored seconds (LSES), severely errored framing seconds (SEFS), severely errored seconds (SES), and unavailable seconds (UAS). For a description of these performance threshold parameters, see enter threshold parameters in the Node Reference, Volume 2. For report examples, see the following Output Samples. Both the physical layer and the Physical Layer Convergence Procedure (PLCP) layer are represented in the Diagnostic Report. NOTE:
The Trunk-E3A Diagnostic Report does not display PLCP layer information.
In addition, if the response to the DISPLAY ERRORED DATA prompt is yes, the diagnostic prints an optional Errored Segment Data Report.
6-16
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ diagnose trunk
Output Sample: Trunk-T3 Diagnostic Report—Zero Error Count
Loopback diagnostic in progress 95-12-31 15:48:53 NODE= TRK-T3 DIAGNOSTIC REPORT -----------------------------------------------DATA FORMAT: SEGMENT TEST DURATION: 10 SECONDS PHYSICAL LAYER --------------------TYPE ERROR COUNT --------------------LCV 0 LES 0 LSES 0 CV 0 ES 0 SES 0 SEFS 0 UAS 0 PLCP LAYER --------------------TYPE ERROR COUNT --------------------CV 0 ES 0 SES 0 SEFS 0 UAS 0
Data Networking Products M2 Trunk Module Reference, Issue 3
6-17
________________ diagnose trunk
Output Sample: Trunk-E3 Diagnostic Report—Zero Error Count
Loopback diagnostic in progress 95-12-31 15:48:53 NODE= TRK-E3 DIAGNOSTIC REPORT -----------------------------------------------DATA FORMAT: SEGMENT TEST DURATION: 10 SECONDS PHYSICAL LAYER --------------------TYPE ERROR COUNT --------------------CV 0 ES 0 SES 0 SEFS 0 UAS 0 PLCP LAYER --------------------TYPE ERROR COUNT --------------------CV 0 ES 0 SES 0 SEFS 0 UAS 0
6-18
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ diagnose trunk
Output Sample: Trunk-T3 Diagnostic Report—Non-Zero Error Count
Loopback diagnostic in progress Diagnostic FAILED: Receiver timed-out 95-12-31 15:52:15 NODE= TRK-T3 DIAGNOSTIC REPORT -----------------------------------------------DATA FORMAT: SEGMENT TEST DURATION: 10 SECONDS PHYSICAL LAYER --------------------TYPE ERROR COUNT --------------------LCV 24 LES 1 LSES 0 CV 0 ES 0 SES 0 SEFS 0 UAS 4 PLCP LAYER --------------------TYPE ERROR COUNT --------------------CV 0 ES 0 SES 0 SEFS 0 UAS 4
Data Networking Products M2 Trunk Module Reference, Issue 3
6-19
________________ diagnose trunk
Output Sample: Trunk-E3 Diagnostic Report—Non-Zero Error Count
Loopback diagnostic in progress Diagnostic FAILED: Receiver timed-out 95-12-31 15:52:15 NODE= TRK-E3 DIAGNOSTIC REPORT -----------------------------------------------DATA FORMAT: SEGMENT TEST DURATION: 10 SECONDS PHYSICAL LAYER --------------------TYPE ERROR COUNT --------------------CV 0 ES 0 SES 0 SEFS 0 UAS 4 PLCP LAYER --------------------TYPE ERROR COUNT --------------------CV 0 ES 0 SES 0 SEFS 0 UAS 4
6-20
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ diagnose trunk
Output Sample: Trunk-E3A Diagnostic Report—Non-Zero Error Count
Loopback diagnostic in progress - .
M
95-12-31 14:25:46 NODE= diagnose trunk 10 local_lp TRK-E3A DIAGNOSTIC REPORT -----------------------------------------------DATA FORMAT: SEGMENT TEST DURATION: 9 SECONDS --------------------TYPE ERROR COUNT --------------------LCV 0 LES 0 LSES 0 CV 0 ES 0 SES 0 SEFS 0 UAS 0
Data Networking Products M2 Trunk Module Reference, Issue 3
6-21
________________ diagnose trunk
Output Sample: Trunk-T3A Diagnostic Report—Non-Zero Error Count
Loopback diagnostic in progress - .
M
95-12-31 14:28:33 NODE= diagnose trunk 9 local_lp TRK-T3A DIAGNOSTIC REPORT -----------------------------------------------DATA FORMAT: SEGMENT TEST DURATION: 9 SECONDS --------------------TYPE ERROR COUNT --------------------LCV 0 LES 0 LSES 0 CV 0 ES 0 SES 0 SEFS 0 UAS 0 PLCP LAYER --------------------TYPE ERROR COUNT --------------------CV 0 ES 0 SES 0 SEFS 0 UAS 0
6-22
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ diagnose trunk
Output Sample: Errored Segment Data Report
ERRORED SEGMENT DATA REPORT: -------------------------------------------------------------------X1: ec20 8200 514f 328b 7834 79f6 e7cd 3136 3c44 abf0 1c29 e3bd 6fb0 R1: ec20 821d 514f 328b 7834 79f6 e7cd 3136 3c44 abf0 1c29 e3bd 6fb0 X2: d729 7b4b 7d9f f948 c0db 899a c620 6d48 4d73 9934 9414 fbaa b682 R2: d729 7b4b 7d9f f948 e0db 899a c620 6d48 4d73 9934 9414 fbaa b620 X1: cd0d 9400 a9af 0266 be48 1ab5 9363 d94a bc9b c2ea 4fd8 9d64 a296 R1: cd0d 9410 a9af 0266 be48 1ab5 9363 d94a bc9b c2ea 4fd8 8564 a296 X2: 5d17 e718 d32d 2bc3 ff2f f81b a0f3 435f 8eed 4ec0 7345 8e8e 3acc R2: 5d97 e718 d32d 2bc3 ff2f f81b a0f3 435f 8eed 4ec0 7345 8e8e 3965 X1: 0373 0c00 8795 c1fd 93bc 4950 f1b8 bfd4 6685 241d aecb 8e84 e6cd R1: 0373 0c04 8795 c1fd 93bc 4950 f1b8 bfd4 6685 241d aecb 8e84 e6cd X2: 9514 2988 ad62 04f6 8497 3d9b c9c8 4eaa 9948 061b 90cf 4538 762d R2: 9514 2988 ad62 04c0 0004 3b37 9090 9d55 3290 1c37 219e 0270 00dd
The Errored Segment Data Report shows, in hexadecimal notation, transmitted and received error segment data. Each four lines, which is 104 bytes, represents one segment with errors. Lines beginning with X show transmitted data; lines beginning with R show received data. The following 1 or 2 indicates whether it is the first 26 bytes (1) or the second 26 bytes (2).
Data Networking Products M2 Trunk Module Reference, Issue 3
6-23
________________ dmeas trunk
dmeas trunk The dmeas trunk command enables you to request measurement reports detailing the efficiency level of a particular trunk module. The same data can be gathered through scheduled measurement reports. NOTE:
The scheduled report is displayed by StarKeeper II NMS only. Furthermore, scheduled measurements must be activated (Procedure 4-6), otherwise the fields in the dmeas report are not cleared at the end of each measurement interval. If measurements are not scheduled, the fields show counts accumulated from the time the module was restored, and at high speeds, certain counts can roll over, nullifying parts of the report.
To activate measurements for any type of trunk, the trunk module must be restored to service. For all trunks, measurements must be enabled with the enter or change trunk commands. For these trunks, on-demand reports contain information accumulated since the last automatically generated report. NOTE:
When measurements have been scheduled using schedule measurements, it takes 10 minutes before data can be accumulated and displayed via the dmeas trunk command.
Scheduled measurements for a trunk module are generated in machine-readable format only through StarKeeper II NMS. Syntax
You can use dmeas trunk in prompted entry or one-line entry. CC0> dmeas OBJECT [...trunk...]: trunk MODULE ADDRESS: INTERVAL [current, previous: +(current)]:
Parameters
This section explains a parameter in the dmeas trunk prompting sequence that differs from those in enter trunk. Refer to the Syntax section for the prompting sequence, system defaults, and parameter options. MODULE ADDRESS
A number identifying the shelf slot that the module occupies. Only a single address can be entered. To request measurement reports for the second board of a two-board module, you must enter the higher number of the two contiguous slots in which the trunk module resides.
6-24
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dmeas trunk
Parameters (continued) INTERVAL
Specifies whether the on-demand report is to be generated for the current or previous reporting interval. If current is specified, the report includes measurements collected for the portion of the 15-minute interval that is currently elapsing; if previous is specified, the report includes measurements collected for the entire 15-minute interval prior to the time of the measurement report request. Prompted Entry: Displaying Trunk Measurements CC0> dmeas OBJECT [...trunk...]: trunk MODULE ADDRESS: INTERVAL [current, previous: +(current)]: previous
NOTE:
The following trunk measurement reports show samples of on-demand reports. Because they are samples, some reports show error measurements; other reports do not.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-25
________________ dmeas trunk
One-line Entry/Output: Displaying Trunk-T3/T3S Measurements (Previous Interval) CC0> dmeas trunk 22 previous 95-12-31 08:00:10 NODE= M dmeas trunk 22 previous TRUNK MEASUREMENTS - T3 MODULE ADDRESS: 22 <-- TO-NODE ---> BUFFER BUFFER UTIL PEAK UTIL 44% 48% GROUP: trkdef
95-12-31 CPU UTIL 54%
CPU PEAK UTIL 60%
SPEED:
URP SEGMENTS 10000
<-------------- FM-NODE --------------> BUFFER BUFFER BP UTIL PEAK PARITY UTIL ERROR 62% 65% 2
45 Mb/s
<--- RECEIVED BY PORT FM LINE ---> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 15% 754920 12960000 16% L2_PDU CLNS SEGMENTS 12960000
08:00 -----> 08:15
<---- XMITTED FM PORT TO LINE ---> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 5% 251640 4320000 6% L2_PDU CLNS SEGMENTS 43200000
URP SEGMENTS 500
EGRESS CRC ERROR 0
*** FOR ADDITIONAL ON-DEMAND MEASUREMENTS USE STARKEEPER II NMS CC0>
6-26
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dmeas trunk
One-line Entry/Output: Displaying Trunk-E3/E3S Measurements (Current Interval) CC0> dmeas trunk 10 current 95-12-31 13:47:43 NODE= M dmeas trunk 10 current TRUNK MEASUREMENTS - E3 MODULE ADDRESS: 10 <-- TO-NODE ---> BUFFER BUFFER UTIL PEAK UTIL 0% 0% GROUP: trke3grp
95-12-31 CPU UTIL 0%
CPU PEAK UTIL 0%
SPEED:
URP SEGMENTS 0
<-------------- FM-NODE --------------> BUFFER BUFFER BP UTIL PEAK PARITY UTIL ERROR 0% 0% 0
34 Mb/s
<--- RECEIVED BY PORT FM LINE ---> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 0% 0 0 UA L2_PDU CLNS SEGMENTS 0
13:45 -----> 13:47
<---- XMITTED FM PORT TO LINE ---> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 0% 0 0 UA L2_PDU CLNS SEGMENTS 0
URP SEGMENTS 0
EGRESS CRC ERROR 0
*** FOR ADDITIONAL ON-DEMAND MEASUREMENTS USE STARKEEPER II NMS CC0>
Data Networking Products M2 Trunk Module Reference, Issue 3
6-27
________________ dmeas trunk
One-line Entry/Output: Displaying Trunk-T3I Measurements (Current Interval) CC0> dmeas trunk 24 current 95-07-24 12:31:24 NODE= M dmeas trunk 24 current TRUNK MEASUREMENTS - T3I MODULE ADDRESS:
24
95-07-24
<---- TO-NODE(ingress) BUFFER BUFFER CPU UTIL PEAK UTIL UTIL 40% 43% 55%
12:16 -----> 12:31
----------> CPU PEAK UTIL 65%
<----------- FM-NODE(egress) ---------> BUFFER BUFFER CPU CPU BP UTIL PEAK UTIL PEAK PARITY UTIL UTIL ERROR 60% 62% 65% 66% 5
<--- RECEIVED BY PORT FM LINE ---> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 12% 65476 13000000 19%
<------ XMITTED FM PORT TO LINE ------> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 10% 250000 4300000 9%
SPEED:45 Mb/s
L2_PDU CLNS SEGMENTS 13000000
L3_PDU CLNS 15500
L3_PDU SYSTEM MGMT 100
L2_PDU CLNS SEGMENTS 43000000
L3_PDU CLNS 21000
L3_PDU SYSTEM MGMT 32600
*** FOR ADDITIONAL ON-DEMAND MEASUREMENTS USE STARKEEPER II NMS CC0>
6-28
Data Networking Products M2 Trunk Module Reference, Issue 3
EGRESS CRC ERROR 1
________________ dmeas trunk
One-line Entry/Output: Displaying Trunk-T3A Measurements (Current Interval) CC0> dmeas trunk 3 current 95-12-31 08:14:10 NODE= M dmeas trunk 3 current TRUNK MEASUREMENTS - T3A MODULE ADDRESS:
3
<-- TO-NODE ---> BUFFER BUFFER UTIL PEAK UTIL 10% 15% GROUP: atmgp
95-12-31 CPU UTIL 10%
CPU PEAK UTIL 15%
TOTAL OA&M CELLS 30
<---- XMITTED FM PORT TO LINE ----> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 8% 250000 4320000 5% L2_PDU CLNS SEGMENTS 4310000
URP SEGMENTS 10000
<--ATM LVL RECVD BY PORT FM LINE--> TOTAL CELLS ON LINK 19790120
<-------- FM-NODE -------> BUFFER BUFFER BP UTIL PEAK PARITY UTIL ERROR 10% 15% 2
SPEED: 45 Mb/s
<--- RECEIVED BY PORT FM LINE ----> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 15% 750000 19790000 14% L2_PDU CLNS SEGMENTS 19780000
08:00 -----> 08:14
CELLS WITH HEC CORRECTED 111
URP SEGMENTS 500
<-ATM LVL XMITTED FM PORT TO LINE-> TOTAL CELLS ON LINK 4320100
TOTAL OA&M CELLS 16
*** FOR ADDITIONAL ON-DEMAND MEASUREMENTS USE STARKEEPER II NMS CC0>
Data Networking Products M2 Trunk Module Reference, Issue 3
6-29
________________ dmeas trunk
One-line Entry/Output: Displaying Trunk-E3A Measurements (Current Interval) CC0> dmeas trunk 10 current 95-12-31 10:29:10 NODE= M dmeas trunk 10 current TRUNK MEASUREMENTS - E3A MODULE ADDRESS:
10
<-- TO-NODE ---> BUFFER BUFFER UTIL PEAK UTIL 10% 15% GROUP: atmgp
95-12-31 CPU UTIL 10%
CPU PEAK UTIL 15%
TOTAL OA&M CELLS 30
<---- XMITTED FM PORT TO LINE ----> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 8% 250000 4320000 5% L2_PDU CLNS SEGMENTS 4310000
URP SEGMENTS 10000
<--ATM LVL RECVD BY PORT FM LINE--> TOTAL CELLS ON LINK 19790120
<-------- FM-NODE -------> BUFFER BUFFER BP UTIL PEAK PARITY UTIL ERROR 10% 15% 2
SPEED: 45 Mb/s
<--- RECEIVED BY PORT FM LINE ----> LINE TOTAL TOTAL LINE UTIL K BYTES LINE PEAK SEGMENTS UTIL 15% 750000 19790000 14% L2_PDU CLNS SEGMENTS 19780000
10:15 -----> 10:29
CELLS WITH HEC CORRECTED 111
URP SEGMENTS 500
<-ATM LVL XMITTED FM PORT TO LINE-> TOTAL CELLS ON LINK 4320100
TOTAL OA&M CELLS 16
*** FOR ADDITIONAL ON-DEMAND MEASUREMENTS USE STARKEEPER II NMS CC0>
6-30
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dmeas trunk
Report Fields BP PARITY ERROR
The number of times that a backplane parity error is detected within the reported interval. BUFFER PEAK UTIL
The 1-second peak utilization value for the data transport buffer within the reported interval. The to/from (TO/FM) values are reported separately. BUFFER UTIL
The average utilization of the data transport buffer within the reported interval. The to/from (TO/FM) values are reported separately. CELLS WITH HEC CORRECTED
For Trunk-T3A/E3A, number of cells received with header error correction. CPU PEAK UTIL
The 5-minute peak utilization value for the central processing unit (CPU) within the reported interval. CPU UTIL
The average utilization of the CPU within the reported interval. EGRESS CRC ERROR
For Trunk-T3/T3S/E3/E3S and Trunk-T3I, the number of times that an egress Cyclic Redundancy Check (CRC) error is detected within the reported interval. Egress CRC error count is incremented whenever a cell leaves the BNS-2000 network with an invalid CRC. Both the payload CRC and the header CRC are checked and included in this count. A high egress CRC error count could indicate a hardware problem. GROUP
The name of the group associated with the trunk module. LINE PEAK UTIL
The 5-minute peak count of bytes received on the line within the reported 15-minute interval. The 15-minute interval is broken into three 5-minute intervals, with the peak only calculated if data is transported for a full five minutes. The peak is always displayed as UA (unavailable) during the first five minutes of the interval. During the second five minutes, the first five minutes is displayed as peak, and during the last five minutes, the maximum of the first two 5-minute intervals is displayed. The to/from (TO/FM) values are reported separately.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-31
________________ dmeas trunk
Report Fields (continued) LINE UTIL
The fraction of traffic that occupied the line, compared to the full capacity of the line, expressed as a percent. Line utilization is furnished for the receive and transmit (RECEIVE/XMITTED) directions for the reported interval. Peak line utilization is the 5minute maximum value of line utilization within the reported interval. Total line utilization is the line utilization within the interval reported. The to/from (TO/FM) values are reported separately. When a module is first restored, and the line utilization is not calculated until a 15-minute period has elapsed, or if the time is changed during an interval, UA is displayed. L2_PDU CLNS SEGMENTS
The line segment count of the connectionless traffic. L3_PDU CLNS
A Level 3 Protocol Data Unit is a unit of information passed between peer Level 3 entities. This data item represents the count of the variable length L3_PDUs transferred at the ICI. L3_PDU SYSTEM MGMT
The count of L3_PDUs transferred between Level 3 peer functional entities across the ICI with a protocol identifier value of 60. This value is reserved for special system management functions such as fault isolation and congestion management. MINUTES
The number of minutes in which measurements were being collected during the interval. This field only appears if the trunk fails. MODULE ADDRESS
The node slot number (module address) occupied by the trunk module. SPEED
The configured data rate of the trunk. TOTAL CELLS ON LINK(received)
For Trunk-T3A/E3A, total number of cells received. TOTAL CELLS ON LINK(transmitted)
For Trunk-T3A/E3A, total number of cells transmitted. TOTAL K BYTES
The number of thousands of 8-bit data units that occupy a line, including all overhead (derived from the TOTAL LINE SEGMENT count) within the reported interval. The to/from ( TO/FM ) values are reported separately.
6-32
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dmeas trunk
Report Fields (continued) TOTAL LINE SEGMENTS
The total segment counts of data traffic on the line within the reported interval. Line segment counts are module measurements. The to/from ( TO/FM ) values are reported separately. TOTAL OA&M CELLS (received)
For Trunk-T3A/E3A, number of operations, administration, and maintenance (OA&M) cells received. TOTAL OA&M CELLS (transmitted)
For Trunk-T3A/E3A, number of operations, administration, and maintenance (OA&M) cells transmitted. URP SEGMENTS
For Trunk-T3/E3, Trunk-T3A/E3A, and Trunk-T3S/E3S, the line segment count of the Universal Receiver Protocol (URP) connection-oriented traffic.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-33
________________ dstat trunk
dstat trunk The dstat trunk command enables you to display the status of trunk modules. You can use this command to evaluate problems that may or may not be detected by the alarm system. All hardware module data output for dstat module is displayed, as well as on-board software information. Hardware module data is obtained from status packet information; port data is obtained from module software while the module is in service. NOTE:
Use dstat module to display status for the second board of a two-board trunk.
The generation of status packet information is contingent upon the switch setting of the module mode switch: When a trunk module is first installed in a Series M2 Shelf and its mode switch is in the Enabl position, the module does not generate any status packets until it completes its power-up selftest. When the trunk module mode switch is in the Diag or Disab position, the module does not generate any status packets. When the trunk module is reset or an attempt is made to restore the module to service and the mode switch position is toggled from Enabl to Diag, the module stops generating status packets. Syntax
You can input dstat trunk in prompted or one-line entry. CC0> dstat OBJECT [...trunk...]: trunk MODULE ADDRESS: DETAIL [low, high: (+low)]:
Parameters
This section explains a parameter in the dstat trunk prompting sequence that differs from those in enter trunk. Refer to the Syntax section for the prompting sequence, system defaults, and parameter options. DETAIL
Specifies command output as low (limited detail) or high (complete detail). Prompted Entry: Displaying High-Detail Trunk Status CC0> dstat OBJECT [...trunk...]: trunk MODULE ADDRESS: 44 DETAIL [low, high: (+low)]: high
6-34
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dstat trunk
One-line Entry/Output: Displaying High-Detail Trunk-E3 Status CC0> dstat trunk 33 high 95-12-31 06:01:35 NODE= M dstat trunk 33 high ****************************** MODULE 33 *********************************** MODULE TYPE SERVICE STATE HARDWARE ERROR COUNT SERIAL NUMBER trke3 in service 4 4223 LAST HARDWARE ALARM FIFO reset 95-12-31
14:41
LAST SOFTWARE ALARM Quarter-hourly threshold for Near End Framed Path SES exc 95-12-31 10:25 ONLINE yes
ENABLED yes
SELFTEST pass
IO BOARD IOB TEST LOOPBK MODE present fail no ------------------------------ HIGH DETAIL -----------------------------MODULE FIFO FM NODE FM NODE SANITY RESET RESET PARITY OVERFLO ERROR 1 2 0 0 0 EXPECT TYPE trke3
FULL EMPTY PACKETS PACKETS 26557 0
ACTUAL STAT1 0
ACTUAL STAT2 60
ACTUAL STAT3 20
ROUTER FILTER B
RTBL PARITY yes
FTBL PARITY yes
ACTUAL STAT4 20
EXPECT STAT1 0
EXPECT STAT2 60
EXPECT STAT3 20
EXPECT STAT4 34
RANGE BAD ERRORS SEGMENTS 0 0 ****************************** MODULE 33 PORT LEVEL ************************* EXPECT ACTUAL OPERATING SRVC STATE SRVC STATE STATE in service in service up ------------------------------ HIGH DETAIL -----------------------------LINE and FRAME Layer: <-----------NEAR END-------------> <-------FAR END-------> LOSS OF LOSS OF ALARM IND YELLOW SIGNAL FRAME SIGNAL ALARM no no no no CC0>
Data Networking Products M2 Trunk Module Reference, Issue 3
6-35
________________ dstat trunk
One-line Entry/Output: Displaying High-Detail Trunk-T3/T3S Status CC0> dstat trunk 22 high 95-12-31 06:01:35 NODE= M dstat trunk 22 high ****************************** MODULE 22 *********************************** MODULE TYPE SERVICE STATE HARDWARE ERROR COUNT SERIAL NUMBER trkt3 in service 4 4113 LAST HARDWARE ALARM FIFO reset 95-12-31
15:01
LAST SOFTWARE ALARM Quarter-hourly threshold for Near End Framed Path SES exc 95-12-31 10:15 ONLINE yes
ENABLED yes
SELFTEST pass
IO BOARD IOB TEST LOOPBK MODE present fail no ------------------------------ HIGH DETAIL -----------------------------MODULE FIFO FM NODE FM NODE SANITY RESET RESET PARITY OVERFLO ERROR 1 3 0 0 0 EXPECT TYPE trkt3
FULL EMPTY PACKETS PACKETS 34118 0
ACTUAL STAT1 0
ACTUAL STAT2 60
ACTUAL STAT3 20
ROUTER FILTER B
RTBL PARITY yes
FTBL PARITY yes
ACTUAL STAT4 20
EXPECT STAT1 0
EXPECT STAT2 60
EXPECT STAT3 20
EXPECT STAT4 34
RANGE BAD ERRORS SEGMENTS 0 0 ****************************** MODULE 22 PORT LEVEL ************************* EXPECT ACTUAL OPERATING SRVC STATE SRVC STATE STATE in service in service up ------------------------------ HIGH DETAIL -----------------------------LINE and FRAME Layer: <-----------NEAR END-------------> <-------FAR END-------> LOSS OF LOSS OF ALARM IND YELLOW SIGNAL FRAME SIGNAL ALARM no no no no PLCP Layer: <-----------NEAR END-------------> LOSS OF EGRESS FRAME LSS no connected DQDB Status: <-------NEAR END------> HEAD OF BUS A CC0>
6-36
<-------FAR END-------> YELLOW INGRESS SIGNAL LSS no connected <-------FAR END------> HEAD OF BUS B
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dstat trunk
One-line Entry/Output: Displaying High-Detail Trunk-T3A Status CC0> dstat trunk 9 high 95-12-31 06:01:35 NODE= M dstat trunk 9 high ****************************** MODULE 9 *********************************** MODULE TYPE SERVICE STATE HARDWARE ERROR COUNT SERIAL NUMBER trkt3a in service 4 1234 LAST HARDWARE ALARM FIFO reset 95-12-31
15:01
LAST SOFTWARE ALARM Quarter-hourly threshold for Near End Framed Path SES exc 95-12-31 10:15 ONLINE yes
ENABLED yes
SELFTEST pass
IO BOARD IOB TEST LOOPBK MODE present fail no ------------------------------ HIGH DETAIL -----------------------------MODULE FIFO FM NODE FM NODE SANITY RESET RESET PARITY OVERFLO ERROR 1 3 0 0 0 EXPECT TYPE trkt3a
FULL EMPTY PACKETS PACKETS 34118 0
ACTUAL STAT1 0
ACTUAL STAT2 60
ACTUAL STAT3 20
ROUTER FILTER B
RTBL PARITY yes
FTBL PARITY yes
ACTUAL STAT4 20
EXPECT STAT1 0
EXPECT STAT2 60
EXPECT STAT3 20
EXPECT STAT4 34
RANGE BAD ERRORS SEGMENTS 0 0 ****************************** MODULE 9 PORT LEVEL ************************* EXPECT ACTUAL OPERATING SRVC STATE SRVC STATE STATE in service in service up ------------------------------ HIGH DETAIL -----------------------------LINE and FRAME Layer: <-----------NEAR END-------------> <-------FAR END-------> LOSS OF LOSS OF ALARM IND YELLOW SIGNAL FRAME SIGNAL ALARM no no no no ATM Layer: VIRTUAL PATH ALARM INDICATION SIGNAL no
VIRTUAL PATH FAR END RECEIVE FAILURE no
CC0>
Data Networking Products M2 Trunk Module Reference, Issue 3
6-37
________________ dstat trunk
One-line Entry/Output: Displaying High-Detail Trunk-E3A Status CC0> dstat trunk 10 high 95-12-31 06:01:35 NODE= M dstat trunk 10 high ****************************** MODULE 10 *********************************** MODULE TYPE SERVICE STATE HARDWARE ERROR COUNT SERIAL NUMBER trke3a in service 4 5678 LAST HARDWARE ALARM FIFO reset 95-12-31
15:01
LAST SOFTWARE ALARM Quarter-hourly threshold for Near End Framed Path SES exc 95-12-31 10:15 ONLINE yes
ENABLED yes
SELFTEST pass
IO BOARD IOB TEST LOOPBK MODE present fail no ------------------------------ HIGH DETAIL -----------------------------MODULE FIFO FM NODE FM NODE SANITY RESET RESET PARITY OVERFLO ERROR 1 3 0 0 0 EXPECT TYPE trke3a
FULL EMPTY PACKETS PACKETS 34118 0
ACTUAL STAT1 0
ACTUAL STAT2 60
ACTUAL STAT3 20
ROUTER FILTER B
RTBL PARITY yes
FTBL PARITY yes
ACTUAL STAT4 20
EXPECT STAT1 0
EXPECT STAT2 60
EXPECT STAT3 20
EXPECT STAT4 34
RANGE BAD ERRORS SEGMENTS 0 0 ****************************** MODULE 10 PORT LEVEL ************************* EXPECT ACTUAL OPERATING SRVC STATE SRVC STATE STATE in service in service up ------------------------------ HIGH DETAIL -----------------------------LINE and FRAME Layer: <-----------NEAR END-------------> <-------FAR END-------> LOSS OF LOSS OF ALARM IND YELLOW SIGNAL FRAME SIGNAL ALARM no no no no TRAIL TRACE OUT OF FRAME no
TRAIL TRACE MISMATCH no
ATM Layer: VIRTUAL PATH ALARM INDICATION SIGNAL no CC0>
6-38
VIRTUAL PATH FAR END RECEIVE FAILURE no
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dstat trunk
One-line Entry/Output: Displaying High-Detail Trunk-T3I Status dstat trunk 24 high 95-07-10 11:10:09 NODE= dstat trunk 24 high
CC0> M
****************************** MODULE 24 *********************************** MODULE TYPE SERVICE STATE HARDWARE ERROR COUNT SERIAL NUMBER trkt3i in 0 1281 LAST HARDWARE ALARM none LAST SOFTWARE ALARM none EGRESS ONLINE yes
ENABLED yes
IO BOARD present
INGRESS ONLINE ENABLED yes yes
SELFTEST pass
IOB TEST pass
LOOPBK MODE no
IO BOARD present
SELFTEST pass
IOB TEST pass
LOOPBK MODE no
------------------------- EGRESS HIGH DETAIL ---------------------------MODULE FIFO FM NODE FM NODE SANITY RESET RESET PARITY OVERFLO ERROR 0 0 0 0 0 EXPECT TYPE trkt3i
FULL EMPTY PACKETS PACKETS 37448 0
ACTUAL STAT1 0
ACTUAL STAT2 60
ACTUAL STAT3 220
ROUTER FILTER A
RTBL PARITY no
FTBL PARITY no
RANGE ERRORS 0
BAD SEGMENTS 0
ACTUAL STAT4 34
EXPECT STAT1 0
EXPECT STAT2 60
EXPECT STAT3 220
EXPECT STAT4 34
------------------------ INGRESS HIGH DETAIL ---------------------------MODULE FIFO FM NODE FM NODE SANITY RESET RESET PARITY OVERFLO ERROR 0 0 0 0 0 EXPECT TYPE trkt3i
FULL EMPTY PACKETS PACKETS 37448 0
ACTUAL STAT1 0
ACTUAL STAT2 60
RANGE ERRORS 0
BAD SEGMENTS 0
ACTUAL STAT3 60
ACTUAL STAT4 34
EXPECT STAT1 0
EXPECT STAT2 60
EXPECT STAT3 60
EXPECT STAT4 34
Data Networking Products M2 Trunk Module Reference, Issue 3
6-39
________________ dstat trunk
One-line Entry/Output: Displaying High-Detail Trunk-T3I (continued) ****************************** MODULE 24 PORT LEVEL ************************* EXPECT ACTUAL OPERATING SRVC STATE SRVC STATE STATE in service in service down ------------------------------ HIGH DETAIL -----------------------------LINE and FRAME Layer: <-----------NEAR END-------------> <-------FAR END-------> LOSS OF LOSS OF ALARM IND YELLOW SIGNAL FRAME SIGNAL ALARM no no no no PLCP Layer: <-----------NEAR END-------------> LOSS OF EGRESS FRAME LSS no up
<-------FAR END-------> YELLOW INGRESS SIGNAL LSS no down
DQDB Status: <-------NEAR END------> HEAD OF BUS A
<-------FAR END------> HEAD OF BUS UA
Report Fields
References to alarms in the following paragraphs are to alarm messages documented in the Messages Reference. NEAR END refers to local trunks; FAR END refers to remote trunks (that is, on the other end of the transmission facility). ACTUAL SRVC STATE
The actual current service state of the port. ACTUAL STAT1
The actual value of the first hardware status byte of the most recently received status packet for the specified module. In some cases, the actual and expected values of STAT1 differ. ACTUAL STAT2
The actual value of the second software status byte of the most recently received status packet for the specified module. In some cases, the actual and expected values of STAT2 differ. ACTUAL STAT3
The actual value of the third hardware status byte of the most recently received status packet for the specified module. In some cases, the actual and expected values of STAT3 differ. ACTUAL STAT4
The actual value of the fourth hardware status byte of the most recently received status packet for the specified module. In some cases, the actual and expected values of STAT4 differ.
6-40
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dstat trunk
Report Fields (continued) ALARM IND SIGNAL
Indicates whether (yes or no) the near-end equipment has output an alarm indication signal (AIS) for the incoming T3/E3 layer signal or whether this information is unavailable (UA). AVAIL
Shows whether (yes or no) the module is on-line and administered, the trunk cable is connected to the proper module, and the protocol has been established. BAD SEGMENTS
The count of segments transmitted by the module on a channel that is beyond the limit for which the module is configured. Bad segment counts might be attributed to a defective module that is corrupting the address field of the segments or to a channel configuration mismatch on the two sides of the trunk. To determine if the module is defective, run module diagnostics; to determine if a configuration mismatch has occurred, review the module configuration. DIAGNOS_MODE
For Trunk-T3I, indicates whether the module is in the self-test mode: if active, it is in the self-test mode; if inactive, it is not. EGRESS LSS
For Trunk-T3/T3S/E3/E3S and Trunk-T3I, indicates whether the link status signal (LSS) of the PLCP path layer sent out by the near-end equipment is down, up, or connected; or whether this information is unavailable (UA). The EGRESS LSS becomes UA when the near-end equipment declares carrier failure alarms or the I/O board is absent or invalid. EMPTY PACKETS
The number of empty status packets received. Empty packets are received when a module is not physically present in the specified shelf slot. See EMPTY SLOT alarm. If the number is high and continues to increase, it could indicate a module hardware problem. ENABLED
Indicates whether or not (yes or no) the module mode switch is enabled (Enabl). The value of this field is determined only from status information. See MODE SWITCH NOT ENABLED alarm. EXPECT SRVC STATE
The expected current service state of the port. EXPECT STAT1
The expected status of the first hardware status byte for the module. EXPECT STAT2
The expected status of the second software status byte for the module.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-41
________________ dstat trunk
Report Fields (continued) EXPECT STAT3
The expected status of the third hardware status byte for the module. EXPECT STAT4
The expected status of the fourth hardware status byte for the module. EXPECT TYPE
The expected hardware type of the module in the shelf slot. For in-service modules, the value of this field is dependent only on information the administrator supplies. For out-ofservice modules, this field is determined by status information. FM NODE OVERFLO
The measure of any imbalance between the rate at which information arrives at a module and the rate at which the subscriber processes that information. Overflow errors occur during typical operation and do not necessarily indicate a problem. If a high rate is reported, check the main, I/O, and port utilization and traffic count statistics to determine where the overload is occurring. See FROM BUS OVERFLOW alarm. FM NODE PARITY
The number of status packets received, which indicates parity errors detected for packets. FTBL PARITY
Indicates whether (yes or no) a parity error is detected in the address filtering table of the connectionless trunk; or whether this information is unavailable (UA) because the module is out of service. FULL PACKETS
The number of status packets containing data that the Control Computer has received. Full packets are received only when a module is physically present in the specified shelf slot. HARDWARE ERROR COUNT
An approximate number summarizing module errors detected since the last module reboot (that is, error counts in other fields). A count of 3 or 4 indicates a normal level of error. Higher counts usually indicate a problem. HEAD OF BUS
For Trunk-T3/T3S/E3/E3S and Trunk-T3I, indicates whether the a or b Distributed Queue Dual Bus (DQDB) is used by the near-end or far-end equipment for transmission across the transmission facility Subscriber Network Interface (SNI) or whether this information is unavailable (UA). The far-end HEAD OF BUS becomes UA when the near-end equipment declares carrier failure alarms or the I/O board is absent or invalid. INGRESS LSS
For Trunk-T3/T3S/E3/E3S and Trunk-T3I, indicates whether the link status signal (LSS) of the PLCP path layer received from the far-end equipment is down, up, or connected; or whether this information is unavailable (UA).
6-42
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dstat trunk
Report Fields (continued) IO BOARD
Indicates the status of the module I/O distribution board to be present, absent, or invalid. IOB TEST
Indicates the status of the I/O distribution board according to the module self-test. Status is reported as pass if the I/O board has passed the self-test; fail if the I/O board has failed the self-test; n/a if the I/O board is absent or not the valid type; or not done if the I/O board is installed after the module self-test is run. The I/O board self-test is run during power-up and when the module is reset or restored to service. LAST HARDWARE ALARM
The most recent alarm issued for the module hardware. This information, which is based on status packet data, is not stored across Control Computer reboots. LAST SOFTWARE ALARM
The most recent alarm issued by the module against its software. This information is not stored across module or Control Computer reboots. See MODULE WAS RESET alarm. LOOPBAK MODE
Indicates whether (yes or no) the module port is in remote loopback mode or whether this information is unavailable (UA). The module remains in loopback mode after diagnostic testing when lnkrev is not followed by no_loop and the trunk module is restored to service. LOSS OF FRAME
Indicates whether (yes or no) the near-end or far-end equipment has declared a loss of frame (LOF) or whether this information is unavailable (UA). LOSS OF SIGNAL
Indicates whether (yes or no) the near-end or far-end equipment has declared a loss of signal (LOS) for the incoming T3/E3 layer signal or whether the information is unavailable (UA). MODULE RESET
The number of module resets since the last module reboot. For some modules, resets occur during normal operation. MODULE TYPE
Indicates the module type that is physically present. This field is determined from status packet information only and is independent of information supplied via enter and delete. This field is initialized to empty. ONLINE
Indicates whether (yes or no) the module is on-line. A status of yes is shown only if the green LED on the module is lit. This field is determined from status information only.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-43
________________ dstat trunk
Report Fields (continued) OPERATING STATE
Indicates the current state of operation of the link. The valid states are: down—no data transfer can take place, and up—data transfer can take place. RANGE ERRORS
The count of segments with envelope parity errors transmitted by the module and detected by the Switch; the count of packets transmitted by the module on a channel that is beyond the limit for which the module is configured. Bad packet counts might be attributed to a defective module that is corrupting the address field of the packet or to a channel configuration mismatch on the two sides of the trunks. To determine if the module is defective, run module diagnostics; to determine if a configuration mismatch has occurred, review the module configuration. ROUTER FILTER
Indicates whether the active route table and address-filter table set of a connectionless trunk is set A or set B; or whether this information is unavailable (UA) because the module is out of service. RTBL PARITY
Indicates whether (yes or no) a parity error is detected in the route table of a connectionless trunk; or whether this information is unavailable (UA) because the module is out of service. SANITY ERROR
A status packet flag has indicated that the module sanity timer went off. See MODULE MALFUNCTION and WRONG MODULE TYPE alarms. SELFTEST
The result of the on-board hardware diagnostics test. When diagnostics are running, this field reads waiting; when diagnostics are completed, this field shows passed or failed. SELF-TEST FAIL REASON
When SELFTST indicates failed, this field shows the reason. SERIAL NUMBER
The unique factory-encoded number for all modules accessing the backplane. Maintaining records with these numbers can help track circuit pack versions. SERVICE STATE
Shows the current service state of the module to be in service (via restore), oos, manual (out of service via remove), oos, fault, auto (out of service via the alarm system), rfs (ready-forservice), or downloading. In addition, configurations with session maintenance show trunk modules to be oos, rerouted (out of service and connections on the trunk have been rerouted), or rerouted (in service, but the trunk has been rerouted).
6-44
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ dstat trunk
Report Fields (continued) TRAIL TRACE OUT OF FRAME
For Trunk-E3A, the trail trace overhead in the E3 frame is a 16-octet message sequence, which is transmitted and received one octet at a time in each E3 frame. This message is transmitted continuously. The first octet of the sequence is sent with the high order bit set as one. The remaining octets have the high order bit set to zero. When the E3 interface has lost synchronization or is seeking the first octet of the trail trace sequence, this condition is declared. TRAIL TRACE MISMATCH
For Trunk-E3A, the trail trace sequence received within the E3 frame overhead does not match the expected sequence. VIRTUAL PATH ALARM INDICATION SIGNAL
For Trunk-T3A/E3A, indicates an upstream failure has been detected and alarmed. A virtual path alarm indication signal (VP-AIS) ATM OA&M cell was received, indicating an alarm condition at the far end. VIRTUAL PATH FAR END RECEIVE FAILURE
For Trunk-T3A/E3A, indicates downstream failure has been detected and alarmed. A virtual path far end receive failure (VP-FERF) ATM OA&M cell was received, indicating a receive failure on the far end. YELLOW ALARM
Indicates whether (yes or no) the near-end equipment has received a T3/E3 yellow alarm from the far-end equipment, or whether this information is unavailable (UA). A received yellow alarm implies that the far-end equipment detects an alarm indication signal (AIS), loss-of-signal (LOS), or loss-of-frame (LOF) failure. YELLOW SIGNAL
For Trunk-T3/T3A/T3S/E3/E3S and Trunk-T3I, indicates whether (yes or no) the near-end equipment has received a PLCP layer yellow signal from the far-end equipment or whether this information is unavailable (UA). A received yellow signal implies that the far-end equipment detects a loss-of-frame (LOF) failure in the PLCP layer.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-45
________________ enter trunk
enter trunk The enter trunk command enables you to add trunk module information to the database. Syntax
You can use enter trunk in prompted entry only. The sequence of prompts depends on your response to the TRUNK MODULE TYPE prompt. CC0> enter OBJECT [...trunk...]: trunk If ATM Feature Package is not installed: †TRUNK MODULE TYPE [... e3, e3s, t3, t3i, t3s ...]: If ATM Feature Package is installed: †TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: MODULE ADDRESS: If TRUNK MODULE TYPE is "e3a" or "t3a": VIRTUAL PATH NUMBER [1-31: +(1)]: If TRUNK MODULE TYPE is "e3", "e3a", "e3s", "t3", "t3a", "t3i", or "t3s": DOWNLOAD SERVER [+(controller)]: If DOWNLOAD SERVER is "controller" and TRUNK MODULE TYPE is not "t3i": SOFTWARE VERSION [+(standard)]: If DOWNLOAD SERVER is not "controller" and TRUNK MODULE TYPE is not "t3i": SOFTWARE VERSION: If TRUNK MODULE TYPE is "t3i": *SOFTWARE VERSION [special, standard:+(standard)]: If TRUNK MODULE TYPE is "t3a" or "t3s": APPLICATION TYPE [intralata, pvt_interlata: +(intralata)]: If TRUNK MODULE TYPE is "t3i": ICI TYPE [lec, ic, sa: +(sa)]: If ICI TYPE is "ic": CARRIER CODE FOR THE FAR END [0000-9999]: LATA ID FOR THE FAR END [1-99999]: MAXIMUM NUMBER OF CONCURRENT DATA UNITS [128, 512: +(512)]: If TRUNK MODULE TYPE is not "t3i": **SESSION MAINTENANCE TRUNK [yes, no: +(no)]: For all TRUNK MODULE TYPEs: COMMENT [up to 60 chars double-quoted]:
________________ † Trunk-T3I configurations should be administered through StarKeeper II NMS. Refer to the StarKeeper II NMS Graphics System Guide. * For all configurations, standard should be entered. ** For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
6-46
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ enter trunk
Syntax (continued) If TRUNK MODULE TYPE is not "t3i": GROUP [up to 8 chars]: If TRUNK MODULE TYPE is "t3", "t3a", "t3s", "e3", "e3a", or "e3s": NUMBER OF USER CHANNELS [1-8172: +(32)]: If TRUNK MODULE TYPE is "e3", "e3a", "e3s", "t3", "t3a", or "t3s": TRUNK WEIGHT [1-16: +(4)]: If TRUNK MODULE TYPE is "e3", "e3s", "t3", "t3i", or "t3s": DQDB BUS INDICATION [a, b: +(a)]: If TRUNK MODULE TYPE is "e3", "e3a", "e3s", "t3", "t3a", "t3i", or "t3s": THRESHOLD PROFILE ID [1-16, or "default": +(default)]: If TRUNK MODULE TYPE is "e3a", or "t3a": TRANSMIT REFERENCE CLOCK [local, stratum, facility: +(facility)]: ATM INTERFACE TYPE [uni, nni: +(nni)]: CELL PAYLOAD SCRAMBLING [on, off: +(off)]: HEADER ERROR CORRECTION [on, off: +(off)]: If TRUNK MODULE TYPE is "e3a": LOSS OF SIGNAL STANDARD [rc8811, g.775: +(g.775)]: EXPECTED TRAIL TRACE ADDRESS [up to 15 digits, none: +(none)]: TRANSMIT TRAIL TRACE ADDRESS [up to 15 digits, none: +(none)]: For all TRUNK MODULE TYPEs: ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: If TRUNK MODULE TYPE is "t3", "t3a", "t3s", or "t3i": CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: If TRUNK MODULE TYPE is not "t3i": CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: Command loops to TRUNK MODULE TYPE prompt.
Parameters
This section contains explanations of parameters used in the enter trunk prompting sequence. Refer to the Syntax section for the prompting sequence, system defaults, and parameter options. APPLICATION TYPE
If TRUNK MODULE TYPE is t3a or t3s, specifies the application type (intralata or pvt_interlata) for exchange SMDS on the indicated trunk. ATM INTERFACE TYPE
If TRUNK MODULE TYPE is e3a or t3a, specifies the ATM interface type, user–network interface (uni) or network–node interface (nni) to be used on the indicated trunk. The option selected should be compatible with the option specified for the FACILITY INTERFACE TYPE on the ATM line card. (See Table 4-2.) The default is nni.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-47
________________ enter trunk
Parameters (continued) CALL SCREENING PROFILE ID
A string of 1 to 8 alphanumeric characters that specifies the profile ID to be assigned to the trunk to screen incoming calls; or the word none, if a profile ID is not to be assigned to the trunk module. See enter profile in the Node Reference. CARRIER CODE FOR THE FAR END
If TRUNK MODULE TYPE is t3i, a four-digit standard code identifying the LEC at the other end of the IC or SA trunk, or the four-digit standard code identifying the IC on the LEC trunk. CBIT PARITY CODE VIOLATION MODE
If TRUNK MODULE TYPE is t3, t3a, t3i, or t3s, specifies whether the C-bit parity code violation mode is off or on. CELL PAYLOAD SCRAMBLING
If TRUNK MODULE TYPE is e3a or t3a, specifies whether the cell payload scrambling option is off or on. The default is off. When this option is on the scrambling is used to improve the security and robustness of the header error correction cell delineation mechanism. Cell delineation is the process that allows identification of the cell boundaries. COMMENT
An optional string of 1 to 60 characters, enclosed in double quotation marks, containing needed administrative information. DOWNLOAD SERVER
Specifies the source of the software to be downloaded to the module. The source must be a valid service address or the local controller. DQDB BUS INDICATION
If TRUNK MODULE TYPE is e3, e3s, t3, t3s or t3i, specifies whether unidirectional data transport from a source follows path A or path B to reach a destination node. Unidirectional data transport can begin from the head of bus A or the head of bus B. ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK
For all trunks, specifies whether (yes or no) measurement data is to be collected and reported for the specified trunk. EXPECTED TRAIL TRACE ADDRESS
If TRUNK MODULE TYPE is e3a, specifies a far-end address of 1 to 15 digits, which should be received by the local module from the far end equipment. If the address is less than 15 digits then it is padded with zeros in front. The default is none. GROUP
A string of 1 to 8 alphanumeric characters specifying the name of an existing trunk group to be associated with the module.
6-48
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ enter trunk
Parameters (continued) HEADER ERROR CORRECTION
If TRUNK MODULE TYPE is e3a or t3a, specifies whether the header error correction option is off or on. This option controls whether single-bit error correction is in effect. When this option is on, the device corrects single-bit errors, and detects and discards multi-bit errors. When this option is off, the device detects and discards the single-bit and multi-bit errors. The default is off. ICI TYPE
If TRUNK MODULE TYPE is t3i, indicates one of three possible applications (lec, ic, sa): LEC the LEC side of a LEC-to-IC connection IC the IC side of a LEC-to-IC connection SA either side of a serving arrangement LATA ID FOR THE FAR END
If ICI TYPE is ic, a one- to five-digit figure specifying the LATA ID of the network at the far end of the IC trunk. The ICI LATA ID is required to compute routing tables for ICI-IC trunks. LOSS OF SIGNAL STANDARD
If the TRUNK MODULE TYPE is e3a, a value (g.775 or rc8811) that specifies the loss of signal (LOS) standard to be used. The default is g.775. For G.775, LOS is detected by the absence of signal transitions on the incoming signal for a period of 0.3 micro seconds to 1 milliseconds. For RC8811, LOS is detected if the incoming signal has no transitions (that is, when the signal level is 35 dB below nominal, for N consecutive pulse intervals, where 10 ≤ N ≥ 255). MAXIMUM NUMBER OF CONCURRENT DATA UNITS
The number of messages that can be sent or received concurrently. If the TRUNK MODULE TYPE is t3i, a value (128 or 512), indicating the maximum number of concurrent data units (MCDU) on egress from the network. The IC equipment can limit this number to 128. MODULE ADDRESS
A number identifying the shelf slot that the module occupies. Only a single address entry is allowed. For a two-board Trunk-T3I module, the lower of two contiguous slots (the slot in which the egress board resides) is configured. NUMBER OF USER CHANNELS
Specifies the maximum number of active user channels for the module. The number of user channels affects the total channels that can be specified. The range and default vary according to module type; see the Syntax section. The number of channels defined on each end of a trunk must be equal. For example: if node 1 has 51 channels defined on its trunk to node 2, then node 2 must have 51 channels defined on its trunk to node 1.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-49
________________ enter trunk
Parameters (continued) SESSION MAINTENANCE TRUNK
Specifies whether (yes or no) the trunk is to be identified as a session maintenance trunk. For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide. SOFTWARE VERSION
If TRUNK MODULE TYPE is e3/e3a/e3s, or t3/t3a/t3s, a string of 1 to 14 characters specifying the software version filename to be downloaded to the module. If DOWNLOAD SERVER is controller, enter standard as the software version filename. If DOWNLOAD SERVER is not controller, enter a valid software release number or the name of the file to be downloaded from the server. If TRUNK MODULE TYPE is t3i, enter standard as the software version filename. Do not use the option special when administering the trunk module. THRESHOLD PROFILE ID
Specifies a number from 1 to 16 as the identifier of the profile. One threshold profile ID is assigned per trunk. See enter threshold in the Node Reference. TRANSMIT REFERENCE CLOCK
If TRUNK MODULE TYPE is e3a or t3a, specifies whether the I/O board will derive its transmit clocking from the facility, the Stratum 4 Clock (stratum), or on board oscillator clock (local). TRANSMIT TRAIL TRACE ADDRESS
If TRUNK MODULE TYPE is e3a, specifies the 15-digit local module address, which will be sent to the far end equipment by the local module. The default is none. TRUNK MODULE TYPE
Specifies the type of trunk module to be entered as e3, e3a, e3s, t3, t3a, t3i, or t3s. The ATM Feature Package must be installed to include Trunk-T3A/E3A module types. TRUNK WEIGHT
If TRUNK MODULE TYPE is e3/e3a/e3s, or t3/t3a/t3s, specifies the weight of a trunk as a number from 1 to 16. (When computing the distance between nodes, the optimal data transmission path is the one in which the weight of all trunks total the smallest sum.) VIRTUAL PATH NUMBER
If TRUNK MODULE TYPE is e3a or t3a, specifies a number, from 1 to 31, for the virtual path over which all traffic between a pair of nodes is to be carried. Only a single virtual path identifier (VPI) is allowed. The default is 1.
6-50
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ enter trunk
Prompted Entry: Entering Trunk Information for Trunk-T3
*
CC0> enter OBJECTS [..., trunk, ...]: trunk TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: t3 MODULE ADDRESS: 22 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + SESSION MAINTENANCE TRUNK [yes, no: +(no)]: + COMMENT [up to 60 chars double-quoted]: "trunk not installed yet" GROUP [up to 8 chars]: trkgrp NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(4)]: + DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Meintenance Guide and StarKeeper II NMS Graphics System Guide.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-51
________________ enter trunk
Prompted Entry: Entering Trunk Information for Trunk-T3A
*
CC0> enter OBJECTS [..., trunk, ...]: trunk TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: t3a MODULE ADDRESS: 9 VIRTUAL PATH NUMBER [1-31: +(1)]: 2 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + APPLICATION TYPE [intralata, pvt_interlata: +(intralata)]: + SESSION MAINTENANCE TRUNK [yes, no: +(no)]: + COMMENT [up to 60 chars double-quoted]: "t3a in 9 and VP number is 2" GROUP [up to 8 chars]: test NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(4)]: 2 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + TRANSMIT REFERENCE CLOCK [local, stratum, facility: +(facility)]: + ATM INTERFACE TYPE [uni, nni: +(nni)]: + CELL PAYLOAD SCRAMBLING [on, off: +(off)]: + HEADER ERROR CORRECTION [on, off: +(off)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
6-52
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ enter trunk
Prompted Entry: Entering Trunk Information for Trunk-T3S
*
CC0> enter OBJECTS [..., trunk, ...]: trunk TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: t3s MODULE ADDRESS: 12 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + APPLICATION TYPE [intralata, pvt_interlata: +(intralata)]: + SESSION MAINTENANCE TRUNK [yes, no: +(no)]: + COMMENT [up to 60 chars double-quoted]: "t3s in 12" GROUP [up to 8 chars]: test NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(4)]: 2 DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Meintenance Guide and StarKeeper II NMS Graphics System Guide.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-53
________________ enter trunk
Prompted Entry: Entering Trunk Information for Trunk-T3I† CC0> enter OBJECTS [..., trunk, ...]: trunk TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: t3i MODULE ADDRESS: 24 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [special, standard: +(standard)]: + ICI TYPE [lec, ic, sa: +(sa)]: ic CARRIER CODE FOR THE FAR END [0000-9999]: 1234 LATA ID FOR THE FAR END [1-99999]: 12 MAXIMUM NUMBER OF CONCURRENT DATA UNITS (MCDU) [128, 512: +(512)]: 128 COMMENT [up to 60 chars double quoted]: "this is an ic trunk" DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: yes CBIT PARITY CODE VIOLATION MODE [on, off: +(off)]: + TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: CC0>
________________ † Trunk-T3I configuration should be administered through StarKeeper II NMS. Refer to StarKeeper II NMS Graphics System Guide.
6-54
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ enter trunk
Prompted Entry: Entering Trunk Information for Trunk-E3
*
CC0> enter OBJECTS [..., trunk, ...]: trunk TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: e3 MODULE ADDRESS: 26 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + SESSION MAINTENANCE TRUNK [yes, no: +(no)]: + COMMENT [up to 60 chars double-quoted]: "e3 in 26" GROUP [up to 8 chars]: trkgrp NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(4)]: + DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Meintenance Guide and StarKeeper II NMS Graphics System Guide.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-55
________________ enter trunk
Prompted Entry: Entering Trunk Information for Trunk-E3A
*
CC0> enter OBJECTS [..., trunk, ...]: trunk TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: e3a MODULE ADDRESS: 10 VIRTUAL PATH NUMBER [1-31: +(1)]: 2 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + SESSION MAINTENANCE TRUNK [yes, no: +(no)]: + COMMENT [up to 60 chars double-quoted]: "e3a in 10 and VP number is 2" GROUP [up to 8 chars]: test NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(4)]: 2 THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + TRANSMIT REFERENCE CLOCK [local, stratum, facility: +(facility)]: + ATM INTERFACE TYPE [uni, nni: +(nni)]: + CELL PAYLOAD SCRAMBLING [on, off: +(off)]: + HEADER ERROR CORRECTION [on, off: +(off)]: + LOSS OF SIGNAL STANDARD [rc8811, g.775: +(g.775)]: + EXPECTED TRAIL TRACE ADDRESS [up to 15 digits, none: +(none)]: 211838348888887 TRANSMIT TRAIL TRACE ADDRESS [up to 15 digits, none: +(none)]: 211818359999999 ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
6-56
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ enter trunk
Prompted Entry: Entering Trunk Information for Trunk-E3S
*
CC0> enter OBJECTS [..., trunk, ...]: trunk TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: e3s MODULE ADDRESS: 28 DOWNLOAD SERVER [+(controller)]: + SOFTWARE VERSION [+(standard)]: + APPLICATION TYPE [intralata, pvt_interlata: +(intralata)]: + SESSION MAINTENANCE TRUNK [yes, no: +(no)]: + COMMENT [up to 60 chars double-quoted]: "e3s in 28" GROUP [up to 8 chars]: test NUMBER OF USER CHANNELS [1-8172: +(32)]: + TRUNK WEIGHT [1-16: +(4)]: 2 DQDB BUS INDICATION [a, b: +(a)]: + THRESHOLD PROFILE ID [1-16, or "default": +(default)]: + ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no: +(no)]: + CALL SCREENING PROFILE ID [up to 8 chars, none: +(none)]: + TRUNK MODULE TYPE [... e3, e3a, e3s, t3, t3a, t3i, t3s ...]: CC0>
________________ * For all configurations, a no response is required. Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Meintenance Guide and StarKeeper II NMS Graphics System Guide.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-57
________________ remove trunk
remove trunk The remove trunk command enables you to take a trunk module out of service. This command interrupts any calls in progress. If remove trunk is executed for a session maintenance trunk while call rerouting is in progress, the command fails. Syntax
You can use remove trunk in prompted entry or one-line entry. CC0> remove OBJECT [...trunk...]: trunk MODULE ADDRESS:
Parameters
Refer to the parameter definitions in the enter trunk section. Prompted Entry: Removing a Trunk Module from Service CC0> remove OBJECT [...trunk...]: trunk MODULE ADDRESS: 55 CC0>
One-line Entry: Removing a Trunk Module from Service CC0> remove trunk 55
6-58
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ route trunk
route trunk For session maintenance* trunks only, the route trunk command enables you to specify the module address and direction of a trunk reroute. Refer to the Session Maintenance Guide for additional information. Syntax
You can use route trunk in prompted or one-line entry. CC0> route OBJECT [...trunk...]: trunk MODULE ADDRESS: ROUTE DIRECTION [alternate, normal: +(normal)]: If ROUTE DIRECTION is "alternate" and trunk is carrying rerouted calls: WARNING: Trunk is carrying rerouted traffic; rerouted calls will be dropped. If ROUTE DIRECTION is "normal" and recovery declaration criteria is not met: WARNING: Trunk is not fully functional; calls may be dropped. CONTINUE [yes, no: +(no)]:
Parameters
This section contains explanations of parameters in the route trunk prompting sequence. Refer to the Syntax section for the prompting sequence, system defaults, and parameter options. CONTINUE
Specifies whether (yes or no) call rerouting is to continue despite the possibility that calls might be dropped. Calls can be dropped when the specified trunk is already carrying rerouted traffic or recovery declaration criteria has not been met on the original trunk. MODULE ADDRESS
A single number identifying the shelf slot of the session maintenance trunk that is to be routed. ROUTE DIRECTION
Specifies the direction of the reroute to be alternate, which initiates a trunk reroute to standby channel sets, or normal, which returns rerouted channel sets to the original trunk.
________________ * Session maintenance configurations should be administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-59
________________ route trunk
Prompted Entry: Routing Calls to Alternate Trunk CC0> route OBJECT [...trunk...]: trunk MODULE ADDRESS: 7 ROUTE DIRECTION [alternate, normal: +(normal)]: alternate CC0>
Prompted Entry: Routing Calls to Alternate Trunk Carrying Rerouted Traffic CC0> route OBJECT [...trunk...]: trunk MODULE ADDRESS: 14 ROUTE DIRECTION [alternate, normal: +(normal)]: alternate WARNING: Trunk 14 is carrying rerouted traffic; rerouted calls will be dropped. CONTINUE [yes, no: +(no)]: + CC0>
Prompted Entry: Routing Calls to Original Trunk CC0> route OBJECT [...trunk...]: trunk MODULE ADDRESS: 7 ROUTE DIRECTION [alternate, normal: +(normal)]: + CC0>
Prompted Entry: Routing Calls to Original Trunk (Recovery Declaration Criterion Not Met) CC0> route OBJECT [...trunk...]: trunk MODULE ADDRESS: 7 ROUTE DIRECTION [alternate, normal: +(normal)]: + WARNING: Trunk 7 not fully functional; calls may be dropped. CONTINUE [yes, no: +(no)]: + CC0>
6-60
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ route trunk
One-line Entry/Output: Routing Calls to Alternate Trunk CC0> route trunk 7 alternate
One-line Entry/Output: Routing Calls to Alternate Trunk Carrying Rerouted Traffic CC0> route trunk 14 alternate WARNING: Trunk 14 is carrying rerouted traffic; rerouted calls will be dropped. CONTINUE [yes, no: +(no)]: + CC0>
One-line Entry/Output: Routing Calls to Original Trunk CC0> route trunk 7 +
One-line Entry/Output: Routing Calls to Original Trunk (Recovery Declaration Criterion not Met) CC0> route trunk 7 + WARNING: Trunk 7 not fully functional; calls may be dropped. CONTINUE [yes, no: +(no)]: + CC0>
Data Networking Products M2 Trunk Module Reference, Issue 3
6-61
________________ restore trunk
restore trunk The restore trunk command enables you to place a trunk module into service initially, or to put it back into service, after it has been automatically or manually removed from service. Syntax
You can use restore trunk in prompted entry or one-line entry. To execute trunk downloading as a background process, press Delete only after the module download has started. Pressing Delete during the prompting sequence terminates the command process. CC0> restore OBJECT [...trunk...]: trunk MODULE ADDRESS:
Parameters
Refer to the parameter definitions supplied in the enter trunk section. Prompted Entry: Restoring a Trunk to Service CC0> restore OBJECT [...trunk...]: trunk MODULE ADDRESS: 22 Download in progress for module 22. All downloads in progress. Hit to put process in background. Download proceeding > > > > Delete CC0>
One-line Entry: Restoring a Trunk to Service CC0> restore trunk 22 Download in progress for module 22. All downloads in progress. Hit to put process in background. Download proceeding > > > > Delete CC0>
6-62
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ verify trunk
verify trunk The output of the verify trunk command enables you to check the information entered in the database for a specified trunk module or for all trunk modules. Syntax
You can use verify trunk in prompted entry or one-line entry. CC0> verify OBJECT [...trunk...]: trunk MODULE ADDRESS [+(all)]:
Parameters
Except for being able to specify the word all, meaning every trunk module, the MODULE ADDRESS parameter definition for verify trunk is the same as that for enter trunk. Prompted Entry: Verifying Trunk Information
CC0> verify OBJECT [...trunk...]: trunk MODULE ADDRESS [+(all)]: +
One-line Entry/Output: Verifying Trunk Information
M
95-12-31 13:47:26 NODE=samantha verify trunk all MODULE ADDRESS: 26 (shelf 1) MODULE TYPE: trke3 SERVICE STATE: in DOWNLOAD SERVER: luna VERSION: trke3.A.0.7 DQDB BUS INDICATION: head of bus a THRESHOLD PROFILE ID: default ENABLE LINK MEASUREMENT: yes CALL SCREENING PROFILE ID: none COMMENT: e3 in 26 GROUP trkgrp
CHNLS 32
NCHLS: 32
TRUNK WEIGHT: 1
CHNL RANGE 13-44
Data Networking Products M2 Trunk Module Reference, Issue 3
6-63
________________ verify trunk
One-line Entry/Output: Verifying Trunk Information (continued)
M
95-12-31 15:02:24 NODE=samantha verify trunk all MODULE ADDRESS: 22 MODULE TYPE: trkt3 NCHLS: 520 SERVICE STATE: out (manual) DOWNLOAD SERVER: controller VERSION: standard DQDB BUS INDICATION: head of bus a TRUNK WEIGHT: 4 THRESHOLD PROFILE ID: 1 ENABLE LINK MEASUREMENT: yes CBIT PARITY CODE VIOLATION MODE: off CALL SCREENING PROFILE ID: none COMMENT: t3 in 22 GROUP trkgrp
M
CHNLS 520
CHNL RANGE 13-2012
95-07-25 20:22:57 NODE=samantha verify trunk all MODULE ADDRESS: 12 MODULE TYPE: trkt3s NCHLS: 2000 SERVICE STATE: out (manual) DOWNLOAD SERVER: controller VERSION: standard APPLICATION TYPE: pvt_intralata DQDB BUS INDICATION: head of bus a TRUNK WEIGHT: 1 THRESHOLD PROFILE ID: default ENABLE LINK MEASUREMENT: no CBIT PARITY CODE VIOLATION MODE: off CALL SCREENING PROFILE ID: none COMMENT: t3s in 12 GROUP mtlz1
M
CHNLS 2000
CHNL RANGE 13-2012
95-07-25 20:22:57 NODE=samantha verify trunk all MODULE ADDRESS: 24 MODULE TYPE: trkt3i SERVICE STATE: out (manual) DOWNLOAD SERVER: controller VERSION: standard ICI TYPE: ic CARRIER CODE FOR THE FAR END: 1234 LATA ID FOR THE FAR END: 12 MAXIMUM NUMBER OF CONCURRENT DATA UNITS (MCDU): 512 DQDB BUS INDICATION: head of bus a THRESHOLD PROFILE ID: default ENABLE LINK MEASUREMENT: yes CBIT PARITY CODE VIOLATION MODE: off COMMENT: this is an ic trunk
6-64
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ verify trunk
One-line Entry/Output: Verifying Trunk Information (continued)
M
95-07-25 20:22:57 NODE=samantha verify trunk all MODULE ADDRESS: 9 MODULE TYPE: trkt3a VIRTUAL PATH NUMBER: 2 SERVICE STATE: out (manual) DOWNLOAD SERVER: controller VERSION: standard APPLICATION TYPE: pvt_intralata TRUNK WEIGHT: 2 THRESHOLD PROFILE ID: default TRANSMIT REFERENCE CLOCK: facility ATM INTERFACE TYPE: nni HEADER ERROR CORRECTION: off ENABLE LINK MEASUREMENT: no CBIT PARITY CODE VIOLATION MODE: off CALL SCREENING PROFILE ID: none COMMENT: t3a in 9 and VP number is 2 GROUP atmgp
M
CHNLS 1000
NCHLS: 1000
CELL PAYLOAD SCRAMBLING: off
CHNL RANGE 13-1012
95-07-25 20:22:57 NODE=samantha verify trunk all MODULE ADDRESS: 10 MODULE TYPE: trke3a NCHLS: 1000 VIRTUAL PATH NUMBER: 2 SERVICE STATE: out (manual) DOWNLOAD SERVER: controller VERSION: standard TRUNK WEIGHT: 2 THRESHOLD PROFILE ID: default TRANSMIT REFERENCE CLOCK: facility ATM INTERFACE TYPE: nni CELL PAYLOAD SCRAMBLING: off HEADER ERROR CORRECTION: off LOSS OF SIGNAL STANDARD: rc8811 EXPECTED TRAIL TRACE ADDRESS: 211838348888887 TRANSMIT TRAIL TRACE ADDRESS: 211818359999999 ENABLE LINK MEASUREMENT: no CALL SCREENING PROFILE ID: none COMMENT: e3a in 10 and VP number is 2 GROUP atmgp
CHNLS 1000
CHNL RANGE 13-1012
Data Networking Products M2 Trunk Module Reference, Issue 3
6-65
________________ verify trunk
One-line Entry/Output: Verifying Session Maintenance Trunk Information* CC0> verify trunk all 95-12-31 15:49:44 NODE=samantha M verify trunk all MODULE ADDRESS: 22 MODULE TYPE: t3 SERVICE STATE: out (manual) ENABLE LINK MEASUREMENT: yes CALL SCREENING PROFILE ID: none COMMENT: t3 in 22 * * * * * *
NCHLS: 520
SESSION MAINTENANCE DATA: REMOTE NODE: rmtnode EXPECTED BANDWIDTH (bps): 800.0k ACTIVE CHANNEL SETS: 1 BANDWIDTH/ACTIVE CS (bps): 800.0k FAILURE THRESHOLD (secs): 4 GROUP trkgrp
CHLS/CS 520
CHNL RANGE 13-2012
PRIMARY NODE: samantha EXPECTED BANDWIDTH (%): 10.0 STANDBY CHANNEL SETS: 15 STANDBY BANDWIDTH (bps): 7199.9k RECOVERY THRESHOLD (secs): 120
CHNL SET 1
________________ * Output occurs on a node on which session maintenance is administered through StarKeeper II NMS. Consult the Session Maintenance Guide and StarKeeper II NMS Graphics System Guide.
6-66
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ verify trunk
Report Fields
This table correlates each report field heading shown in the output of verify trunk to the parameter for which you are prompted in enter trunk or change trunk. The information beneath each report field heading reflects the parameter option specified in either command. ______________________________________________________________________ ______________________________________________________________________ Report Field Corresponding Parameter APPLICATION TYPE APPLICATION TYPE ______________________________________________________________________ ATM INTERFACE TYPE ATM INTERFACE TYPE ______________________________________________________________________ ______________________________________________________________________ CALL SCREENING PROFILE ID CALL SCREENING PROFILE ID CARRIER CODE FOR THE FAR END CARRIER CODE FOR THE FAR END ______________________________________________________________________ ______________________________________________________________________ CELL PAYLOAD SCRAMBLING CELL PAYLOAD SCRAMBLING CHNL RANGE None: range of channel numbers for this trunk ______________________________________________________________________ NUMBER OF USER CHANNELS CHNLS ______________________________________________________________________ ______________________________________________________________________ COMMENT COMMENT DOWNLOAD SERVER DOWNLOAD SERVER ______________________________________________________________________ DQDB BUS INDICATION DQDB BUS INDICATION ______________________________________________________________________ ______________________________________________________________________ ENABLE LINK MEASUREMENT ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK EXPECTED TRAIL TRACE ADDRESS EXPECTED TRAIL TRACE ADDRESS ______________________________________________________________________ GROUP GROUP ______________________________________________________________________ ______________________________________________________________________ HEADER ERROR CORRECTION HEADER ERROR CORRECTION ICI TYPE ICI TYPE ______________________________________________________________________ ______________________________________________________________________ LATA ID FOR THE FAR END LATA ID FOR THE FAR END LOSS OF SIGNAL STANDARD LOSS OF SIGNAL STANDARD ______________________________________________________________________ MAXIMUM NUMBER OF CONCURRENT MAXIMUM NUMBER OF CONCURRENT DATA UNITS (MCDU) DATA UNITS (MCDU) ______________________________________________________________________ ______________________________________________________________________ MODULE ADDRESS MODULE ADDRESS TRUNK MODULE TYPE MODULE TYPE ______________________________________________________________________ NCHLS None: number of user overhead plus overhead channels ______________________________________________________________________ for call processing None: module service state SERVICE STATE ______________________________________________________________________ None: refer to the Session Maintenance Guide. SESSION MAINTENANCE DATA* ______________________________________________________________________ ______________________________________________________________________ TRANSMIT REFERENCE CLOCK TRANSMIT REFERENCE CLOCK TRANSMIT TRAIL TRACE ADDRESS TRANSMIT TRAIL TRACE ADDRESS ______________________________________________________________________ ______________________________________________________________________ THRESHOLD PROFILE ID THRESHOLD PROFILE ID TRUNK WEIGHT TRUNK WEIGHT ______________________________________________________________________ SOFTWARE VERSION VERSION ______________________________________________________________________ ______________________________________________________________________ VIRTUAL PATH NUMBER VIRTUAL PATH NUMBER * Output occurs on a node that has had session maintenance administered through StarKeeper II NMS.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-67
________________ System Responses
System Responses The following sections contain applicable system responses for the trunk commands. These sections are organized by the key phrases that preface each response. Refer to the Node Reference for a detailed explanation of each key phrase. COMMAND FAILED: Cannot remove trunk ; reroute attempt in progress.
If remove trunk is executed for a session maintenance trunk while call rerouting is in progress, the command fails. Command manually terminated.
The command exited because the
Delete
key was pressed at the system console.
Module is not a trunk.
The specified module address contains a module other than a trunk. Module is not in service.
Measurements cannot be obtained while the module is out of service. No measurement report displayed for trunk .
The measurement report requested for the indicated trunk module was not output to the system console or printer. Requested measurement report timed-out.
The requested report could not be generated within the amount of time allocated. Wait and re-enter the command. Route to path already in progress on trunk .
An attempt was made to route the calls on the trunk to a normal or alternate path with route trunk; however, the reroute to that path was already in progress. Scheduled report is being processed. Try again.
The requested report could not be generated because the system was generating a regularly scheduled report at the time of the request. Trunk already routed to path.
An attempt was made to reroute the calls on the indicated trunk with route trunk but they have already been rerouted to the alternate or normal path. Trunk of type is not fully functional.
An attempt was made to route a session maintenance trunk to its normal path before the trunk module cleared the failure. Unexpected message type received -- [MSG-TYP-VALUE].
Contact your support group. Use StarKeeper II NMS to schedule the measurement reports.
If your node is monitored by StarKeeper II NMS, you must execute the measurements commands from a StarKeeper II NMS console.
6-68
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ System Responses
INPUT ERROR: All is not an allowed value.
The word all cannot be used to name a call screening profile ID. Call screening profile id is not entered.
The indicated call screening profile ID is not configured. See the profile command in the Node Reference. Cannot second board of a trunk module.
Only the first board (the lower slot number) of the two-board Trunk-T3I can be configured, controlled, and maintained with operations commands. Cannot module while .
You cannot change or delete information for the indicated module while it is in service or while it is downloading software. See remove trunk. Cannot get measurements for second board of trunk module.
Measurements data is not available for the second board of a Trunk-T3I. Cannot route trunk alternate while Session Maintenance is not in service.
The route trunk command cannot be executed until session maintenance is in service. Group is not a trunk group, as required.
The name of the group specified is a local receiving, originating, or two-way group. You must specify the name of a trunk group. Measurements are not being collected for trunk .
Measurements are not being gathered for the indicated trunk module. Module address is empty, trunk is expected.
The specified module address is not administered in the database. Module address contains module type - trunk module expected.
The indicated module address contains a module type other than a trunk. Module is already configured. Module is already entered.
The indicated module has already been configured. Module is downloading.
The module cannot be removed from service or restored to service while it is downloading software. Module is not a Session Maintenance trunk.
The indicated module is not a trunk configured for session maintenance.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-69
________________ System Responses
INPUT ERROR Module is not configured.
The indicated module address is not administered in the database. Module is not a trunk.
The indicated module address contains a module other than a trunk module. Module is not configured. Command did not execute.
The indicated module is not entered in the database. Not an allowed value.
The local node name does not exist. Not unique enough.
The input string does not contain the number of characters required to make it unique. Parameter out of Range. Physical slot does not exist. Slot is reserved:
The module address indicated is reserved for another module type. Threshold profile does not exist.
The specified threshold profile ID is not entered into the database. Threshold profile does not match trunk type.
The specified profile ID is not the appropriate type for the particular trunk module. Trunk may only be routed from its primary node.
An attempt was made to route a trunk from its secondary node. Retry the command from a node on the opposite end of the trunk. Trunk may only be routed while in service.
Out-of-service (oos) trunk modules cannot have their calls rerouted. Trunk module is downloading.
Information for the indicated trunk cannot be changed while the module is downloading software. Trunk module is not currently defined in the database.
The indicated trunk module is not administered in the database; therefore, information cannot deleted. Trunk module is not entered. Trunk is not entered.
The indicated trunk module is not administered in the database.
6-70
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ System Responses
REMOVE/RESTORE FAILED: cannot get text file for module . could not send message to config.
The command processor could not send a message to the configuration process. Contact your support group. download failed for module .
NOTE:
Wait for messages that explain the failure. The Data Networking Products Messages Reference Appendix provides additional information for download failure messages.
inconsistent database entry for module . Delete and re-enter.
The information in the database does not agree with that entered for the module address indicated. module address contains a module ( expected).
The indicated module address contains a different module than that type specified on the command line. module address contains no module ( trunk expected).
The indicated address is not administered for any interface module. module is beyond CLOCK.
The specified module address is not allowed. Refer to the Node Reference, Volume 1 for slot numbering restrictions. module is in loop-around mode.
The command processor cannot execute the command because the module is in the looparound mode as a result of diagnostic testing. no switch memory available. Module cannot be restored.
The Control Computer cannot allocate the amount of switch memory the module requires. This situation occurs if all switch memory was allocated or fragmented by removing and restoring several modules. Reboot the system so memory space can be reallocated in a contiguous block. software inconsistency (module ). system too busy to process module . Try again later.
The system is too burdened processing other tasks. Re-enter the command later. unrecognized error code for module .
Re-enter the command. If the message recurs, contact your support group.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-71
________________ System Responses
DIAGNOSTICS: ANOTHER DIAGNOSTIC PROCESS RUNNING
Both Control Computer ports are configured as console ports and another diagnose command is currently running on the other console port. Only one diagnostic process can run at any time. Wait a while before re-entering the command. Cannot communicate with remote trunk.
The trunk is most likely out of service or the trunkcsc channel is not active. Cannot diagnose the second board of a two-board module.
You must specify the slot address of the primary (lower numbered) board of a two-board module set when running diagnostics. Cannot Make Maintenance Process Special.
Both Control Computer ports are configured as console ports and another diagnose command is currently running on the other console port. Only one diagnostic process can run at any time. Wait a while before re-entering the command. Diagnostic download in progress
The diagnostic load module is being downloaded to the trunk so that the complete set of hardware tests or any loopback tests can be run. Diagnostic not completed Command cannot be sent to module . Control computer did not respond. Try again later. DIAGNOSTIC EXIT DUE TO DELETE. Download file not found. Module did not respond to command. Try again later. Module has no resource to process command. Module is being downloaded. Module is too busy to process command. Try again later. Module must be out-of-service for diagnostics. Module task did not respond. System too busy to process command. Try again later. Unexpected error code from config.
The diagnostic did not complete for one of the reasons listed. Error communicating with config.
Because of possible errors in the database, a missing board, Control Computer errors, or a bad disk, the configuration process could not associate diagnostic text with the port being diagnosed. Make sure the trunk module board and I/O board are installed properly. Use verify trunk and dstat trunk to verify module and database integrity. If problems are not found, re-enter the command on another module. If the command executes successfully, replace the trunk module board and re-enter the command. If the command does not execute, the text for the diagnostic might be missing from the disk.
6-72
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ System Responses
LOOP-AROUND DIAGNOSTIC FAILED ON ALL TESTED CHANNELS. MODULE FAILED OPTIONS TEST. CHECK THE I/O DISTRIBUTION BOARD AND CABLES.
The diagnostic failed on all tested channels. Check the appropriate hardware. Line LINK-REVERSE has been set up. LINK-REVERSE has been taken down. LOOP-AROUND DIAGNOSTIC FAILED: ERROR FROM TRUNK CONTROLLER PROCESS ERROR IN LOOP-AROUND SIGNAL NO RESPONSE FROM TRUNK CONTROLLER PROCESS SYSTEM ERROR
The previous response indicates why the loopback diagnostic failed. When an error is detected in a loopback signal, the communications path is faulty. The other error/no response messages indicate a Control Computer software error. For these errors, repeat the command and log recurring similar messages. LOOP AROUND DIAGNOSTIC SUCCEEDED
This message appears for all loop types except reverse_trk and no_loop. Since the loopback process measures the quality of transmission over an interval of time, a message is sent repeatedly (up to 1000 times) and the received data is compared to the transmitted data. An error count is incremented if one or more errors occur in that transmission. The test continues until 10 errors are found or 1000 transmissions have been sent. When the test stops upon receiving 10 errors, the message reports the exact number of transmissions. If one or more errors occur, the message LOOP AROUND DIAGNOSTIC FAILED: ... appears. It is typical to see a few errors on some trunks; but this does not indicate that the trunk module needs to be replaced or cannot be used. Although the module does not detect errors and retransmissions, data integrity is verified at other levels using end-to-end protocols. If errors are numerous and consistent, investigate the trunk service. LOOP-AROUND DIAGNOSTIC SUCCEEDED ON ALL TESTED CHANNELS.
The test has successfully completed. A message is displayed instructing you which diagnostic to run next. Module is in loop state, use the ‘no-loop’ command.
The trunk is in reverse-looping mode. Before any diagnostic test can be run, the module must be taken out of the loop state with the no-loop command. MODULE FAILED OPTIONS TEST
Only the module portion of the diagnostic failed the options test.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-73
________________ System Responses
MODULE MAY STILL BE IN LOOP-AROUND MODE.
The trunk module might still be in the loopback mode; if so, it will not function properly. Use dstat trunk < addr > < high > to determine if it is still in loopback mode; use no_loop to restore the module to normal mode. NO RESPONSE FROM PORT PROCESS
The diagnostic process was unable to communicate with the port process. PORT PROCESS ABORTED BY CONFIG
Hardware complications caused the configuration process to terminate. The complications can include a manual reset (a switch on the board placed in the Diag or Disab position) rather than the Enabl position. Check the physical integrity of the module. If it appears normal, enter dstat trunk < addr > < high > to determine its status. If the status is normal, rerun the test. If the message recurs, replace the trunk module. THE REMOTE TRUNK MODULE MUST ALSO BE IN SERVICE FOR THE node_remote TEST OR IT WILL FAIL. TRUNK MODULE IS IN REQUESTED TRK_REVERSE LOOPING MODE.
The trunk module has been put into the reverse loopback mode. UNABLE TO PLACE TRUNK INTO REQUESTED LOOPING MODE. REPLACE TRUNK BOARD AND TRY AGAIN.
The trunk module cannot be put into the loopback mode. Replace the board and re-enter the command. WAS THE REMOTE TRUNK MODULE IN TRUNK REVERSE LOOPING MODE? IF SO, RUN THE near_dsu LOOP TEST NEXT, BUT FIRST, &...
If the remote trunk is in reverse loopback mode (when running the remote_trk test), run the near_dsu test next. Further self-explanatory instructions are given. XXX_XX diagnostic failed Cannot put far end device into loopback mode. Cannot put far end DSU/CSU into loopback mode. Cannot put local DSU/CSU into loopback mode. The far end device is not in loopback mode.
The diagnostic did not complete for one of the reasons listed. Diagnostic FAILED Cannot configure diagnostics
Indicates a module hardware fault. Cannot detect far-end loopback
An attempt to determine the loopback state of the far-end device or module has failed. Cannot put far-end into loopback mode
An attempt to set the far-end device or module into a loopback state has failed.
6-74
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ System Responses
Far-end stuck in loopback mode
An attempt to clear the far-end device or module loopback state has failed. Incorrect I/O board in the slot Ingress FROM-LINK queue overflow
Could indicate a module hardware fault. I/O board not present I/O board failed diagnostic Premature failure
Indicates a module hardware fault. Pre-existing far-end loopback
The far-end device or module has a loopback path already in place. Receiver timed-out
If this message occurs after the local_lp test, a module or I/O board hardware fault is indicated. If it occurs following manu_lp, or line_farend, it could indicate that the loopback path is not set up correctly. Remote DSU/CSU not using C-Bit frame format
The far-end device is using an incompatible frame format and cannot respond to module loopback commands. Segment data mismatch
The data received differs from that transmitted. This could indicate a module hardware fault or transmission line problem.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-75
________________ System Responses
WARNING: Cannot detect far-end loopback
The far-end device or module is not in a loopback state (manu_lp). Check network Node Reroute Tables for consistency.
This warning indicates that the module for which information is to be changed or deleted, or the module that is to be removed from service, is a session maintenance trunk. Could not send a message to trunksig.
The remove/restore operation could not continue because it could not send a message to the Control Computer process. Comment entry failed. comment file too large. unable to access comment file.
The total comment storage space needed is greater than the allocated space on the disk. Use the dbresize command to resize the database, or eliminate unnecessary comments. File system corruption could be preventing access to the comment file. Check the integrity of the disk system using the file system check command fsck. The Node Reference provides information for this procedure. Download server is not a valid service address.
The download server address must be a valid service address or the local controller. Measurements will not be turned on/off for trunk until module is removed and restored.
The module must be removed and restored to service before the system can begin to collect measurements information. Trunk not fully functional; calls may be dropped.
An attempt was made to route calls to the original (normal) trunk with route trunk, but the trunk is not yet operational. Calls might be dropped. Trunk is carrying rerouted traffic; rerouted calls will be dropped.
An attempt was made to route calls to the alternate trunk with route trunk, but the trunk is already carrying rerouted calls. Calls might be dropped. Trunk is rerouted; rerouted calls will be dropped.
An attempt was made to route calls to the alternate trunk with route trunk, but the trunk is already carrying rerouted calls. Calls might be dropped.
6-76
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ System Responses
No Key Phrase Cannot abort; in progress.
You pressed the
Delete
key when the command process could not be terminated.
DATABASE BEING MODIFIED - TRY AGAIN LATER
The command process cannot continue because the database is being changed. Wait and re-enter the command. Module is already of service.
The module specified is already in the requested service state. Module state unknown -- system did not respond.
The command might have executed successfully; but the system did not respond with status information. Use dstat module or verify module to determine the actual service state of the module. This error message would most likely appear during very heavy use. SERIOUS DATABASE TRANSACTION PROBLEM - UPDATE NOT ACCEPTED
The command process cannot continue because of a critical problem in the database. Contact your support group.
Data Networking Products M2 Trunk Module Reference, Issue 3
6-77
________________ Appendix. M2 Trunk Module Database Entry Forms This section contains sample database entry forms to use when initially entering trunks into the database, or when making extensive changes. They should be used with similar forms, provided in the Node Reference for addresses and groups. After configuration information is entered in the database, save these forms for use in troubleshooting. The sample database entry forms in the Appendix are A-1. Entering a Trunk-T3/T3S Module A-2. Entering a Trunk-T3A Module A-3. Entering a Trunk-E3A Module A-4. Entering a Trunk-E3/E3S Module A-5. Entering a Trunk-T3I Module The forms list prompts that appear when enter commands are used, and the values (or range of values) that can be entered in response to the prompts. Default values are shown in italics. Information contained in this section is supplemented by explanations in the Trunk Module Administration and Trunk Module Commands chapters.
Data Networking Products M2 Trunk Module Reference, Issue 3
A-1
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-1. Entering a Trunk-T3/T3S Module ______________________________________________________________________________________________ TRUNK MODULE TYPE [...e3, e3a, e3s, t3, t3a, t3i, t3s...] t3 t3 t3s t3s ______________________________________________________________________________________________ MODULE ADDRESS ______________________________________________________________________________________________ DOWNLOAD SERVER [controller] ______________________________________________________________________________________________ If DOWNLOAD SERVER is controller: SOFTWARE VERSION [standard] ______________________________________________________________________________________________ If DOWNLOAD SERVER is not controller: SOFTWARE VERSION ______________________________________________________________________________________________ SESSION MAINTENANCE TRUNK* [yes, no] no no no no ______________________________________________________________________________________________ COMMENT [up to 60 chars double-quoted, none] ______________________________________________________________________________________________ GROUP [up to 8 chars] ______________________________________________________________________________________________ NUMBER OF USER CHANNELS [1-8172, 32] ______________________________________________________________________________________________ TRUNK WEIGHT [1-16, 4] ______________________________________________________________________________________________ DQDB BUS INDICATION [a, b] ______________________________________________________________________________________________ THRESHOLD PROFILE ID [1-16, default] ______________________________________________________________________________________________ ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no] ______________________________________________________________________________________________ CBIT PARITY CODE VIOLATION MODE [on, off] ______________________________________________________________________________________________ CALL SCREENING PROFILE ID [up to 8 chars, none] ______________________________________________________________________________________________ ________________ * Session maintenance configurations are administered through StarKeeper II NMS.
A-2
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-2. Entering a Trunk-T3A Module ______________________________________________________________________________________________ TRUNK MODULE TYPE [...e3, e3a, e3s, t3, t3a, t3i, t3s...] t3a t3a t3a t3a ______________________________________________________________________________________________ MODULE ADDRESS ______________________________________________________________________________________________ VIRTUAL PATH NUMBER [1-31] ______________________________________________________________________________________________ DOWNLOAD SERVER [controller] ______________________________________________________________________________________________ If DOWNLOAD SERVER is controller: SOFTWARE VERSION [standard] ______________________________________________________________________________________________ If DOWNLOAD SERVER is not controller: SOFTWARE VERSION ______________________________________________________________________________________________ APPLICATION TYPE [intralata, pvt_interlata] ______________________________________________________________________________________________ SESSION MAINTENANCE TRUNK* [yes, no] no no no no ______________________________________________________________________________________________ COMMENT [up to 60 chars double-quoted, none] ______________________________________________________________________________________________ GROUP [up to 8 chars] ______________________________________________________________________________________________ NUMBER OF USER CHANNELS [1-8172, 32] ______________________________________________________________________________________________ TRUNK WEIGHT [1-16, 4] ______________________________________________________________________________________________ THRESHOLD PROFILE ID [1-16, default] ______________________________________________________________________________________________ TRANSMIT REFERENCE CLOCK [local, stratum, facility] ______________________________________________________________________________________________ ATM INTERFACE TYPE [uni, nni] ______________________________________________________________________________________________
________________ * Session maintenance configurations are administered through StarKeeper II NMS.
Data Networking Products M2 Trunk Module Reference, Issue 3
A-3
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-2. Entering a Trunk-T3A Module (continued) ______________________________________________________________________________________________ CELL PAYLOAD SCRAMBLING [on, off] ______________________________________________________________________________________________ HEADER ERROR CORRECTION [on, off] ______________________________________________________________________________________________ ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no] ______________________________________________________________________________________________ CBIT PARITY CODE VIOLATION MODE [on, off] ______________________________________________________________________________________________ CALL SCREENING PROFILE ID [up to 8 chars, none] ______________________________________________________________________________________________
________________ * Session maintenance configurations are administered through StarKeeper II NMS.
A-4
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-3. Entering a Trunk-E3A Module ______________________________________________________________________________________________ TRUNK MODULE TYPE [...e3, e3a, e3s, t3, t3a, t3i, t3s...] e3a e3a e3a e3a ______________________________________________________________________________________________ MODULE ADDRESS ______________________________________________________________________________________________ VIRTUAL PATH NUMBER [1-31] ______________________________________________________________________________________________ DOWNLOAD SERVER [controller] ______________________________________________________________________________________________ If DOWNLOAD SERVER is controller: SOFTWARE VERSION [standard] ______________________________________________________________________________________________ If DOWNLOAD SERVER is not controller: SOFTWARE VERSION ______________________________________________________________________________________________ SESSION MAINTENANCE TRUNK* [yes, no] no no no no ______________________________________________________________________________________________ COMMENT [up to 60 chars double-quoted, none] ______________________________________________________________________________________________ GROUP [up to 8 chars] ______________________________________________________________________________________________ NUMBER OF USER CHANNELS [1-8172, 32] ______________________________________________________________________________________________ TRUNK WEIGHT [1-16, 4] ______________________________________________________________________________________________ THRESHOLD PROFILE ID [1-16, default] ______________________________________________________________________________________________ TRANSMIT REFERENCE CLOCK [local, stratum, facility] ______________________________________________________________________________________________ ATM INTERFACE TYPE [uni, nni] ______________________________________________________________________________________________ CELL PAYLOAD SCRAMBLING [on, off] ______________________________________________________________________________________________
________________ * Session maintenance configurations are administered through StarKeeper II NMS.
Data Networking Products M2 Trunk Module Reference, Issue 3
A-5
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-3. Entering a Trunk-E3A Module (continued) ______________________________________________________________________________________________ HEADER ERROR CORRECTION [on, off] ______________________________________________________________________________________________ LOSS OF SIGNAL STANDARD [rc8811, g.775] ______________________________________________________________________________________________ EXPECTED TRAIL TRACE ADDRESS [up to 15 digits, none] ______________________________________________________________________________________________ TRANSMIT TRAIL TRACE ADDRESS [up to 15 digits, none] ______________________________________________________________________________________________ ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no] ______________________________________________________________________________________________ CALL SCREENING PROFILE ID [up to 8 chars, none] ______________________________________________________________________________________________
________________ * Session maintenance configurations are administered through StarKeeper II NMS.
A-6
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-4.
Entering a Trunk-E3/E3S Module
______________________________________________________________________________________________ TRUNK MODULE TYPE [...e3, e3a, e3s, t3, t3a, t3i, t3s...] e3 e3 e3s e3s ______________________________________________________________________________________________ MODULE ADDRESS ______________________________________________________________________________________________ DOWNLOAD SERVER [controller] ______________________________________________________________________________________________ If DOWNLOAD SERVER is controller: SOFTWARE VERSION [standard] ______________________________________________________________________________________________ If DOWNLOAD SERVER is not controller: SOFTWARE VERSION ______________________________________________________________________________________________ APPLICATION TYPE [intralata, pvt_interlata] ______________________________________________________________________________________________ SESSION MAINTENANCE TRUNK* no no no no [yes, no] ______________________________________________________________________________________________ COMMENT [up to 60 chars double-quoted, none] ______________________________________________________________________________________________ GROUP [up to 8 chars] ______________________________________________________________________________________________ NUMBER OF USER CHANNELS [1-8172, 32] ______________________________________________________________________________________________ TRUNK WEIGHT [1-16, 4] ______________________________________________________________________________________________ DQDB BUS INDICATION [a, b] ______________________________________________________________________________________________ THRESHOLD PROFILE ID [1-16, default] ______________________________________________________________________________________________
________________ * Session maintenance configurations are administered through StarKeeper II NMS.
Data Networking Products M2 Trunk Module Reference, Issue 3
A-7
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-4. Entering a Trunk-E3/E3S Module (continued) ______________________________________________________________________________________________ ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no] ______________________________________________________________________________________________ CALL SCREENING PROFILE ID [up to 8 chars, none] ______________________________________________________________________________________________
A-8
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ Appendix. M2 Trunk Module Database Entry Forms
FORM A-5.
Entering a Trunk-T3I Module†
______________________________________________________________________________________________ TRUNK MODULE TYPE [...e3, e3a, e3s, t3, t3a, t3i, t3s...] t3i t3i t3i t3i ______________________________________________________________________________________________ MODULE ADDRESS ______________________________________________________________________________________________ DOWNLOAD SERVER [controller] ______________________________________________________________________________________________ SOFTWARE VERSION [special, standard] standard standard standard standard ______________________________________________________________________________________________ ICI TYPE [ic, lec, sa] ______________________________________________________________________________________________ CARRIER CODE FOR THE FAR END [0000-9999] ______________________________________________________________________________________________ If ICI TYPE is "ic" LATA ID FOR THE FAR END [1-99999] ______________________________________________________________________________________________ MAXIMUM NUMBER OF CONCURRENT DATA UNITS (MCDU) [128, 512] ______________________________________________________________________________________________ COMMENT [up to 60 chars double-quoted, none] ______________________________________________________________________________________________ DQDB BUS INDICATION [a, b] ______________________________________________________________________________________________ THRESHOLD PROFILE ID [1-16, default] ______________________________________________________________________________________________ ENABLE TRUNK MEASUREMENTS FOR THIS TRUNK [yes, no] ______________________________________________________________________________________________ CBIT PARITY CODE VIOLATION MODE [on, off] ______________________________________________________________________________________________
________________ † Trunk-T3I configurations should be administered through StarKeeper II NMS. Refer to the StarKeeper II NMS Graphics System Guide. * Session maintenance configurations are administered through StarKeeper II NMS.
Data Networking Products M2 Trunk Module Reference, Issue 3
A-9
________________ Index
A AAL5/ATM, 1-3, 1-4 Address, extended mode, 6-41 module, 5-5, 6-49 service, 6-48 source/destination, 5-7 trail trace, 4-7 Administration, 4-3–4-16 AIS. See Alarm indication signal (AIS) Alarm indication signal (AIS), 5-3, 6-41, 6-45 Alarms, 1-5, 5-3, 5-5, 5-6, 5-8, 6-40, 6-42, 6-43 Alternate routing, 1-5 Asynchronous transfer mode (ATM), 1-3, 1-6, 3-3 feature package, 4-3, 4-6, 4-9, 6-46, 6-50 network, 3-4 switch, 3-10, 3-18, 4-7, 4-8, 4-11 ATM. See Asynchronous transfer mode (ATM)
B Backplane, I/O board, 2-3, 2-14 parity error, 6-31 Bent pins, 2-14 Booting, 6-42, 6-43 Bus indicators, 1-6, 4-5, 6-42
C Cables, loopback, 5-10 Cabling, 3-3–3-24 checking, 5-5, 5-6, 5-7, 5-8 coaxial, 1-3, 3-3, 3-5, 3-6, 3-8, 3-10, 3-12, 3-14, 3-16, 3-18, 3-20, 3-22, 5-10, 5-12, 5-13, 5-15 configuration, 3-3, 3-6, 3-7, 3-9, 3-11, 3-12, 3-13, 3-14, 3-15, 3-17, 3-19, 3-20, 3-21, 3-22, 3-23 Trunk-E3 (TRK-E3) module, 3-15 Trunk-E3A (TRK-E3A) module, 3-17, 3-19 Trunk-E3S (TRK-E3S) module, 3-21
Trunk-T3 (TRK-T3) module, 3-7 Trunk-T3A (TRK-T3A) module, 3-9, 3-11 Trunk-T3I (TRK-T3I) module, 3-23 Trunk-T3S (TRK-T3S) module, 3-13 ribbon, 3-22 Call processing, 4-4 Call screening, 4-5 Cell payload scrambling, 4-6, 5-7, 6-47, 6-48 change node (operations command), 4-11 change trunk (operations command), 4-3, 4-12, 6-3, 6-4–6-9 Channel allocations, 5-4, 5-8 CIR. See Committed Information Rate (CIR) Circuitry—preventing damage to, 2-3 CLNS. See Connectionless network service (CLNS) Code violation (CV), 6-16 Commands, 4-3, 6-3 data link (DL), 6-14 Committed Information Rate (CIR), 1-4, 1-5 Configuration, 6-3 ATM, 5-7 database, 1-6, 4-3, 4-11, 4-12, 4-13, 4-14 hardware, 4-4 modules, 6-4, 6-10 restrictions, 1-6, 4-4 two-board, 1-4, 2-3, 3-22, 3-23, 6-49, 6-69, 6-72 user channels, 4-5 Congestion, management of, 6-32 network, 5-4, 5-6 Connectionless network service (CLNS), 1-3, 1-4, 1-5, 4-4, 4-5, 5-7, 5-8 Connection-oriented network service (CONS), 1-3, 1-4, 1-5 Connections, between nodes, 3-3 faulty, 5-5 restrictions, 1-6 Series M2 Shelves, 3-5
Data Networking Products M2 Trunk Module Reference, Issue 3
I-1
________________ Index
Connectors, backplane, 2-14 loopback, 5-11, 6-14 micro-coaxial, 1-3, 5-10 CONS. See Connection-oriented network service (CONS) Console, 5-13, 5-15 Control Computer, 5-8, 6-42, 6-43 copy module (operations command), 4-11, 4-14 CV. See Code violation (CV)
Documentation, PR-x Downloading, 6-10 DQDB. See Distributed Queue Dual Bus (DQDB) DS3. See Data Signaling Level 3 (DS3) DSR. See Data set ready (DSR) dstat module (operations command), 6-34 dstat trunk (operations command), 4-4, 4-16, 5-4, 5-5, 5-6, 5-7, 5-8, 5-11, 6-34–6-45 DSU. See Data service units (DSUs)
E D Data, errored segment, 6-23 looped, 5-6 lost or garbled, 4-4, 5-5, 5-6 traffic measurement, 6-33 transmission rate(s), 1-6, 6-32 transport, 6-31 Data link (DL) commands, 6-14 Data service units (DSUs), 1-3, 5-6 Data set ready (DSR), 6-41 Data Signaling Level 3 (DS3), 1-3, 1-4, 1-5 Database, configuration, 1-6, 4-11, 6-10 entry forms, 4-3, 4-4, 6-3, A-1–A-9 dbaudit (operations command), 4-16 DDM-1000 units, 3-6, 3-8, 3-12, 3-22 delete trunk (operations command), 4-3, 4-12, 4-13, 6-4, 6-10 diagnose trunk (operations command), 4-4, 5-4, 5-10, 5-11, 5-12, 5-13, 5-15, 6-11–6-23 display connections (operations command), 4-4, 4-16, 5-4, 5-6 display routes (operations command), 4-16, 5-4, 5-7 display traffic (operations command), 4-4, 4-16, 5-4 Distributed Queue Dual Bus (DQDB), 1-3, 1-5, 1-6, 4-5, 6-42 Distribution frame, 3-14, 3-16, 3-20 DL. See Data link (DL) commands dmeas connections (operations command), 4-16 dmeas trunk (operations command), 4-4, 4-16, 5-8, 6-24–6-33
I-2
Electromagnetic interference (EMI), 2-3 Electrostatic discharge (ESD), 2-3 EMI. See Electromagnetic interference (EMI) enter group (operations command), 4-3 enter profile (operations command), 4-3 enter profile (operations command), 4-5, 6-48 enter ssm4 (operations command), 4-3 enter str4 (operations command), 4-3 enter threshold (operations command), 1-6, 4-3, 4-6, 6-16, 6-50 enter trace (operations command), 4-3 enter trunk (operations command), 4-3, 4-4, 4-12, 4-13, 4-14, 6-3, 6-4, 6-10, 6-34, 6-46–6-57 Error(s), correction, 4-6, 4-7, 6-31, 6-49 counts, 5-13, 5-15, 6-16, 6-41, 6-42 detection, 6-31 diagnostic, 5-11 overflow, 6-42 parity, 6-31, 6-42 range, 6-44 transmission, 1-6 ESD. See Electrostatic discharge (ESD)
F Faceplate, 2-15, 5-3, 5-8 Failure, carrier, 5-3, 5-5 connection, 5-4 diagnostic, 5-6, 5-12, 5-13, 5-15, 5-17, 6-13, 6-16 modem, 5-5 security, 5-4 trunk, 1-5, 6-32
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ Index
CMC6B, 1-3, 1-4, 2-4, 2-10, 3-5, 3-6, 3-12 egress/ingress, 1-4, 2-3, 2-4, 3-22 insertion/removal, 2-14 jumper positions/settings, 2-3 local, 5-12, 5-15 remote, 5-13, 5-15 status, 5-8, 6-43 switch settings. See Switch settings tests, 5-8, 6-43 timing source, 1-7, 4-7, 6-47
FCC. See Federal Communications Commission (FCC) Feature Package—ATM, 4-3, 4-9, 6-46, 6-50 Features, 1-4 Federal Communications Commission (FCC), electromagnetic interference (EMI) requirements, 3-3 Frame relay, 1-5 Fuse, 5-5, 5-17
G GlobeView-2000, 4-7, 4-8, 4-9
J
H Hardware, alarms, 6-43 configuration, 4-4 module, 6-41 Header error correction, 4-6, 6-31, 6-47, 6-48, 6-49
I IC. See Interexchange Carrier (IC) ICI. See Inter-Carrier Interface (ICI) Installation, 2-3–2-15, 4-11 cables/connectors, 5-11 Inter-Carrier Interface (ICI), 1-4, 1-5, 4-6 applications, 1-7 Interconnection, 1-5 Interexchange Carrier (IC), 1-5, 4-6 Interfaces, ATM, 1-7, 3-16, 4-6, 6-47, 6-52, 6-56 between BNS-2000 nodes, 3-3, 3-4 BNC coax, 3-6, 3-8, 3-12, 3-22 ICI, 4-6 micro-coax, 3-14, 3-20 network, 4-6 Private InterLATA, 1-5 Interworking, 1-6, 4-3 I/O board, backplane connector, 2-14 clocking, 4-7, 5-7 CMC13, 1-3, 1-4, 2-4, 2-11, 3-5, 3-14, 3-20, 3-22 CMC14, 1-4, 2-4 CMC15, 1-4, 2-4, 2-12, 3-5, 3-8, 3-10 CMC16, 1-4, 2-4, 2-13, 3-5, 3-16, 3-18 CMC6, 1-3, 1-4, 2-4, 2-9, 3-5, 3-6, 3-12, 3-22
Jumper positions/settings, 2-3, 2-4, 5-6 CMA13 module, 2-5 CMA14 module, 2-5 CMA16 module, 2-7 CMA18 module, 2-5 CMA9/CMA9B module, 2-5 CMC13 I/O board, 2-11 CMC15 I/O board, 2-12 CMC16 I/O board, 2-13 CMC6 I/O board, 2-9 CMC6B I/O board, 2-10
L LATA. See Local Access and Transport Area (LATA) Latch(es)—module, 2-15 LCV. See Line code violation (LCV) Leads, 6-41 LEC. See Local Exchange Carrier (LEC) LED. See Light emitting diodes (LEDs) LES. See Line errored second (LES) Light emitting diodes (LEDs), 5-3, 5-5, 5-6, 5-8, 6-43 Line card, 5-7 DS3, 3-10, 4-10 E3, 3-18, 4-10 options, 4-8 Line code violation (LCV), 6-16 Line errored second (LES), 6-16 Line severely errored second (LSES), 6-16 Link status signal (LSS), 6-41, 6-42 Local Access and Transport Area (LATA), 1-5, 4-6 Local Exchange Carrier (LEC), 1-5, 4-6
Data Networking Products M2 Trunk Module Reference, Issue 3
I-3
________________ Index
LOF. See Loss of frame (LOF) Log—system record, 5-11 Loopback, cables, 5-10 connectors, 6-14 mode, 5-5, 6-43 tests, 5-4, 5-6, 5-7, 5-9 LOS. See Loss of signal (LOS) Loss of frame (LOF), 5-3, 6-43 Loss of signal (LOS), 1-7, 4-7, 5-3, 6-43, 6-47 LSES. See Line severely errored second (LSES) LSS. See Link status signal (LSS)
N Network, congestion, 5-4, 5-6, 5-8 map, 5-3 monitoring, 1-5, 5-3 problems, 6-11 Network-node interface (NNI), 1-7, 4-6 NNI. See Network-node interface (NNI) Node-network interface (NNI), 6-47
O Ordering information, 3-24 Overload, 5-6
M Measurement data, 4-15, 5-4, 6-26, 6-27, 6-28, 6-29, 6-30 Mode switch, 2-15, 6-34 Module, address, 5-5, 6-49 board, CMA13, 1-4, 2-4, 3-12, 3-20 CMA14, 1-4, 2-4, 2-5, 3-22 CMA16, 1-4, 2-4, 2-7, 3-22 CMA18, 1-4, 2-4, 3-8, 3-10, 3-16, 3-18 CMA9, 1-3, 2-4, 2-5, 3-6 CMA9B, 1-3, 2-4, 2-5, 3-14 capacity, 5-8 configuration, 4-3, 6-4, 6-10 egress/ingress, 1-4, 2-3, 2-4, 3-22 faceplate, 2-15, 5-3, 5-8 hardware, 5-6, 5-8, 6-41 insertion/removal, 2-15 integrity, 5-9 latch(es), 2-15 local, 5-11, 5-12, 5-15 placement in the node, 2-3 remote, 5-11, 5-12, 5-13, 5-15 resets, 6-34, 6-43 service state, 6-24, 6-42 types, 1-3, 3-3, 6-42, 6-43 move module (operations command), 4-11, 4-13, 6-4
I-4
P Parameter mapping, 4-9 Parameter options, 1-6, 4-4, 5-4, 5-9, 6-4, 6-47–6-50 Parity error, 6-31, 6-42 Performance, module/network, 4-16 threshold parameters, 6-16 transmission, 4-6 Physical Layer Convergence Procedure (PLCP), 1-3, 5-3, 6-16 Pinfield—backplane, 2-14 PLCP. See Physical Layer Convergence Procedure (PLCP) PLCP loss of frame (PLOF), 5-3 Plenum sheathing, 3-3 PLOF. See PLCP loss of frame (PLOF) Port service state, 6-41 Problems, connected devices, 5-5 connectionless trunks, 5-8 facility, 5-10 hardware, 6-41, 6-42 indicators, 5-3 network, 5-8, 6-11 Procedures, administration, 4-9–4-15 installation, 2-14–2-15 maintenance, 4-4 troubleshooting, 5-4, 5-6–5-17
Data Networking Products M2 Trunk Module Reference, Issue 3
________________ Index
Protocol, ATM, 1-5 DQDB, 1-5, 4-5 SIP, 1-5
R Reboot(s), 6-42, 6-43 remove trunk (operations command), 4-4, 4-12, 4-13, 4-14, 6-58 Reports, 4-15, 4-16, 6-23, 6-25, 6-31, 6-34, 6-63 Reset(s), 6-43 restore trunk (operations command), 4-4, 4-12, 4-13, 4-14, 5-17, 6-62 Restrictions, configuration, 4-4 connections, 1-6 electrical, 3-3 route trunk (operations command), 6-59–6-61 Routing, 1-5, 5-4, 5-5, 5-7, 5-8
S Security, 1-5, 4-5 SEFS. See Severely errored framing second (SEFS) Segment error counts, 6-41, 6-44 Self-test, 6-34, 6-41, 6-43, 6-44 Serial number, 6-44 Series M1 Shelves, PR-ix Series M2 Shelf, 1-3, 3-3 connections, 3-5 interfaces, 3-4 status, 6-34 Service problems, 5-4 Service state(s), 4-4, 5-7, 6-24, 6-41, 6-44 Session maintenance, 1-5, 6-46, PR-x Severely errored framing second (SEFS), 6-16 Severely errored second (SES), 6-16 Sheathing, 3-3 Shielding requirements, 3-3 SIP. See SMDS Interface Protocol (SIP) SMDS, PR-x network, 4-6 subscriber equipment, 5-3 SMDS Interface Protocol (SIP), 1-5
SNI. See Subscriber Network Interface (SNI) Software downloading, 6-10 Speeds, 1-5 Standby trunks, 1-5 StarKeeper II NMS, 1-5, 4-3, 4-6, 5-3, 6-24, PR-x Status. See dstat trunk (operations command) Stratum 4 Clock, 4-3, 4-7 Subscriber Network Interface (SNI), 6-42 Switch settings, I/O board, 2-3 mode, 2-15, 6-34 System expansion, 4-16 System Responses, 6-16, 6-68–6-77
T Tests, diagnostic, 5-9, 5-10, 6-14 failure, 5-12, 5-13, 5-15, 6-13 loopback, 5-4, 5-6 self, 6-41 Threshold, error, 4-3 performance parameters, 6-16 profile, 1-6, 4-3, 4-6 Timing source, I/O board, 1-7, 4-7, 6-47 Toxic fumes, 3-3 Trace connections, 4-16. See Also Trail trace Traffic, connectionless, 1-3, 1-4, 4-4, 4-5, 6-32 connection-oriented, 1-3, 1-4 frame relay, 1-5 IntraLATA/Private InterLATA, 1-4 measurement data, 6-33 type(s), 1-5 Trail trace, 1-7, 4-7, 6-8, 6-45, 6-47, 6-48, 6-50, 6-56, 6-65 Transmission, distance, 3-3 facilities, 1-3, 3-6, 3-8, 3-12, 3-14, 3-20, 3-22 TRK-E3. See Trunk-E3 (TRK-E3) module TRK-E3A. See Trunk-E3A (TRK-E3A) module TRK-E3S. See Trunk-E3S (TRK-E3S) module
Data Networking Products M2 Trunk Module Reference, Issue 3
I-5
________________ Index
TRK-T3. See Trunk-T3 (TRK-T3) module TRK-T3A. See Trunk-T3A (TRK-T3A) module TRK-T3I. See Trunk-T3I (TRK-T3I) module TRK-T3S. See Trunk-T3S (TRK-T3S) module Troubleshooting, 4-16, 5-3–5-17 Trunk-E3 (TRK-E3) module, 1-3, 1-5, 2-4, 3-3, 3-14, 3-15, 5-12, 5-13, 6-14, 6-41, 6-42, 6-45 Trunk-E3A (TRK-E3A) module, 1-3, 1-4, 1-5, 2-4, 3-3, 3-17, 3-19, 4-3, 4-6, 4-7, 4-8, 4-11, 5-7, 5-15, 6-14, 6-45. See Trunk-E3S (TRK-E3S) module, 1-3, 1-4, 1-5, 2-4, 3-3, 3-20, 3-21, 5-12, 5-13, 6-14, 6-41, 6-42, 6-45 Trunk-T3 (TRK-T3) module, 1-3, 1-5, 2-4, 3-3, 3-6, 3-7, 5-12, 5-13, 6-14, 6-41, 6-42, 6-45 Trunk-T3A (TRK-T3A) module, 1-3, 1-4, 1-5, 2-4, 3-3, 3-9, 3-11, 4-3, 4-6, 4-7, 4-8, 4-11, 5-7, 5-12, 5-13, 6-14, 6-45. See Trunk-T3I (TRK-T3I) module, 1-3, 1-4, 1-5, 2-3, 2-4, 3-3, 3-22, 3-23, 4-11, 5-12, 5-13, 6-41, 6-42, 6-45 Trunk-T3S (TRK-T3S) module, 1-3, 1-4, 1-5, 3-3, 3-12, 3-13, 5-12, 5-13, 6-14, 6-41, 6-42, 6-45
Virtual circuits, 1-5 Virtual path, 1-7, 5-7, 6-45, 6-50, 6-65 Virtual path identifier (VPI), 4-7 Voltage—slot, 5-17 VPI. See Virtual path identifier (VPI)
W Wrist strap, 2-3
Y Yellow alarm/signal, 5-3, 6-45
U UAS. See Unavailable seconds (UAS) Unavailable seconds (UAS), 6-16 UNI. See User-network interface (UNI) User channel configuration, 4-5 User-network interface (UNI), 1-7, 4-6, 6-47
V verify group (operations command), 4-11, 4-16 verify module (operations command), 4-13, 4-14 verify node (operations command), 4-11, 5-8 verify oosmods (operations command), 4-4, 4-16 verify profile (operations command), 4-11 verify schedule (operations command), 4-16 verify ssm4 (operations command), 4-11, 4-16 verify str4 (operations command), 4-11 verify threshold (operations command), 4-11 verify trace (operations command), 4-11, 4-16 verify trunk (operations command), 4-3, 4-12, 4-13, 4-14, 4-16, 5-4, 5-6, 5-7, 5-11, 5-17, 6-63–6-67
I-6
Data Networking Products M2 Trunk Module Reference, Issue 3
