Professional Documents
Culture Documents
Newbridge, the Newbridge logo and MainStreet are registered trademarks of Newbridge Networks Corporation.
Copyright 1997 Newbridge Networks Corporation.
All rights reserved
Distributor Disclaimer
Newbridge products are intended for standard commercial uses. Without the appropriate network design engineering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control,
direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal
injury, or severe physical or environmental damage. The distributor hereby agrees that the use, sale, licence or other
distribution of the products for any such application without the prior written consent of Newbridge, shall be at the
distributor's sole risk. The distributor hereby agrees to defend and hold Newbridge harmless from any claims for loss, cost,
damage, expense or liability that may arise out of or in connection with the use, sale, licence or other distribution of the
products in such applications.
PRINTED ON
RECYCLED PAPER
Documentation Updates
Updates to Newbridge documentation, including Technical Practices, are easily
accessible on the World Wide Web.
For documentation updates, see:
http://www.newbridge.com/updates/index.html
TechInfo.NOW
TechInfo.NOW is a subscription service that gives customers access to the latest
Newbridge information, including new applications, improved methods of
configuration and upgrading, bug fixes, and product enhancements.
TechInfo.NOW provides access to:
Network Applications
Technical Practices
Technical Bulletins
Product Descriptions
General Information Books
Technical Updates
Software Updates
Upgrade Procedures
iii
Technical Support
Technical Support Engineers are available to assist you 24 hours a day, 7 days a
week.
To get technical help in your region, see the chart below:
Region
Contact Number
(703) 834-5300
(Within UK)
(Outside UK)
Internet
Fax Number
(703) 318-5153
Australia
1 800 62 3645
Hong Kong
Japan
Moscow
http://www.newbridge.com
Customer Feedback
We value your feedback. Please direct questions or comments about Newbridge
documentation to:
http://www.newbridge.com/documentation/feedback.html
iv
Table of Contents
Issue 1, November 1997
Table of Contents
Foreword
16.2
16.2.2
16.2.3
Table of Contents
(400)
xi
Table of Contents
Issue 1, November 1997
16.3
16.3.2
16.3.3
16.3.4
16.3.5
16.3.6
16.4
Using Identifiers
16.4.1
16.4.2
16.4.3
16.4.4
xii
(400)
Table of Contents
16.5
Table of Contents
Issue 1, November 1997
16.5.2
Circuit Connections
17.1.1
17.1.2
17.1.3
17.1.4
17.1.5
17.1.6
17.1.7
17.2
17.2.3
17.2.4
Table of Contents
(400)
xiii
Table of Contents
Issue 1, November 1997
17.2.5
17.2.6
17.2.7
17.2.8
17.2.9
17.3
xiv
(400)
Table of Contents
17.3.2
17.3.3
17.4
17.5
Table of Contents
Issue 1, November 1997
17.5.4
Table of Contents
(400)
xv
Table of Contents
Issue 1, November 1997
17.6
CPSS Configuration
17.6.1
17.6.2
17.6.3
17.6.4
17.6.5
xvi
(400)
Table of Contents
17.6.6
17.6.7
17.6.8
17.6.9
17.6.10
17.6.11
17.7
Table of Contents
Issue 1, November 1997
18. Redundancy
18.1
Control Redundancy
18.1.1
18.1.2
Table of Contents
(400)
xvii
Table of Contents
Issue 1, November 1997
18.1.3
18.1.4
18.1.5
18.1.6
18.1.7
18.1.8
18.1.9
18.2
Protection Switching
18.2.1
18.2.2
18.2.3
18.2.4
xviii
(400)
Table of Contents
18.3
Table of Contents
Issue 1, November 1997
PRI Redundancy
18.3.1
18.3.2
18.3.3
18.3.4
18.3.5
18.3.6
18.3.7
19.1.2
19.2
Table of Contents
(400)
xix
Table of Contents
Issue 1, November 1997
19.3
19.3.2
19.3.3
19.3.4
19.3.5
19.3.6
19.3.7
19.3.8
20.1.2
xx
(400)
Table of Contents
20.2
20.2.3
20.3
20.3.3
20.3.4
Voice Compression
20.4.1
20.4.2
20.4.3
20.5
E1-to-T1 Conversion
20.3.1
20.3.2
20.4
Table of Contents
Issue 1, November 1997
Timeslot 24 Signalling
20.5.1
20.5.2
Table of Contents
Understanding Timeslot 24 Signalling on Dual T1 and Dual T1-2 Cards .... 20.5-1
Configuring Timeslot 24 Signalling on Dual T1 and Dual T1-2 Cards ......... 20.5-2
To configure the DRM for a Dual T1-2 card ............................................. 20.5-2
To configure a Dual T1-2 link for timeslot 24 signalling ........................... 20.5-2
To configure a Dual T1 card for timeslot 24 signalling ............................. 20.5-2
(400)
xxi
Table of Contents
Issue 1, November 1997
20.6
Framing
20.6.1
20.6.2
20.6.3
20.6.4
20.7
20.7.2
20.8.2
Trunk Conditioning
20.9.1
20.9.2
xxii
20.9
Line Length
20.7.1
20.8
(400)
Table of Contents
20.9.3
20.9.4
20.9.5
Table of Contents
Issue 1, November 1997
20.10.2
20.12.2
Table of Contents
(400)
xxiii
Table of Contents
Issue 1, November 1997
20.12.3
20.12.4
20.13 Inversion
20.13.1
20.13.2
20.15.2
20.15.3
20.15.4
xxiv
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
20.16.3
Understanding 24 DS0 Super-rate Circuit Protection for Dual T1-2 Cards 20.16-1
TS24 Frame Fault Signalling ..................................................................... 20.16-1
Normal operation ................................................................................... 20.16-1
TS24 frame fault signalling .................................................................... 20.16-2
Access and Tandem fault signalling ...................................................... 20.16-2
Fault recovery ........................................................................................ 20.16-3
Configuring 24 DS0 Circuit Protection for Dual T1-2 Cards ...................... 20.16-4
To configure the DRM for TS24 signalling ............................................. 20.16-4
To configure the link ............................................................................... 20.16-4
To connect two 24 DS0 super-rate circuits ............................................ 20.16-5
20.17.3
20.17.4
20.17.5
20.18.3
20.18.4
20.18.5
Table of Contents
(400)
xxv
Table of Contents
Issue 1, November 1997
20.18.6
20.18.7
20.18.8
20.18.9
Configuring the E-bit for Dual E1 and Dual E1-2 Cards ............................ 20.18-9
To configure the E-bit for the Dual E1 card .......................................... 20.18-10
To configure the E-bit for the Dual E1-2 card ...................................... 20.18-10
Configuring CRC4 Reframing for Dual E1 and Dual E1-2 Cards ............ 20.18-10
To configure CRC4 reframing for the Dual E1 card ............................. 20.18-10
To configure the CRC4 reframing for the Dual E1-2 card .................... 20.18-11
Configuring Equalization for E3 Cards ..................................................... 20.18-11
To configure equalization for E3 cards ................................................ 20.18-11
Configuring E1 Link Quality Monitoring for E3 Cards .............................. 20.18-11
20.19.3
20.19.4
20.19.5
20.19.6
xxvi
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
21.1.2
21.2
21.2.2
21.3
21.3.2
21.3.3
Table of Contents
(400)
xxvii
Table of Contents
Issue 1, November 1997
21.4
Audio Wires
21.4.1
21.4.2
21.5
21.5.3
21.6.2
21.7.2
xxviii
Line Balance
21.7.1
21.8
Understanding TLPs for Voice Interface Cards and Channel Units ............. 21.5-1
Configuring TLP Levels for Voice Interface Cards and Channel Units ........ 21.5-2
To select TLP levels for voice interface cards and channel units ............ 21.5-7
Configuring TLP Ranges for Voice Interface Cards ..................................... 21.5-7
To select a TLP range for the E&M card .................................................. 21.5-7
To select a TLP range for the LGE and LGS card ................................... 21.5-8
Line Impedance
21.6.1
21.7
Understanding Audio Wires for E&M Cards and Channel Units .................. 21.4-1
Configuring Audio Wires for E&M Cards and Channel Units ....................... 21.4-1
To configure audio wires for E&M cards .................................................. 21.4-1
To configure audio wires for E&M channel units ...................................... 21.4-1
TLPs
21.5.1
21.5.2
21.6
(400)
Table of Contents
21.9
Table of Contents
Issue 1, November 1997
Tx Mute
21.9.1
21.9.2
21.11 Equalization
21.11.1
21.11.2
22.1.2
22.1.3
22.1.4
22.2
Table of Contents
(400)
xxix
Table of Contents
Issue 1, November 1997
22.2.5
22.3
22.3.8
22.3.9
22.3.10
22.3.11
22.3.12
22.3.13
22.3.14
xxx
(400)
Table of Contents
22.3.15
22.3.16
22.3.17
22.3.18
22.3.19
22.3.20
22.3.21
22.3.22
22.3.23
22.3.24
22.3.25
22.3.26
Table of Contents
Table of Contents
Issue 1, November 1997
(400)
xxxi
Table of Contents
Issue 1, November 1997
22.4
23.2
23.3
Configuring Card Slots for the IMC and DSP Cards .................................... 23.2-1
Card type ................................................................................................. 23.2-1
Number of DSP card circuits .................................................................... 23.2-2
Hub identification ..................................................................................... 23.2-2
DSP card applications .............................................................................. 23.2-2
IMC BONDING timers .............................................................................. 23.2-3
To configure DSP card slots .................................................................... 23.2-3
To configure IMC slots ............................................................................. 23.2-5
Voice Compression
23.3.1
23.3.2
23.3.3
23.3.4
23.3.5
23.3.6
xxxii
(400)
Table of Contents
23.3.7
23.3.8
23.4
23.4.2
23.5.3
23.6
23.5
Table of Contents
Issue 1, November 1997
Table of Contents
(400)
xxxiii
Table of Contents
Issue 1, November 1997
23.6.2
23.6.3
23.6.4
23.6.5
23.6.6
23.6.7
23.6.8
23.6.9
23.6.10
23.6.11
23.6.12
xxxiv
(400)
Table of Contents
23.7
23.7.2
23.7.3
23.7.4
23.8
23.9
Table of Contents
Issue 1, November 1997
Configuring DSP Cards for Fax and Modem Data Transmission ................ 23.8-1
Configuring DSP Circuits for Data Transmission ......................................... 23.8-1
Enabling and disabling G3 fax relay ........................................................ 23.8-1
Enabling and disabling V.32 modem relay ............................................... 23.8-2
Data transmission rate ............................................................................. 23.8-2
Data bandwidth ........................................................................................ 23.8-3
NSF frame handling mode ....................................................................... 23.8-3
Data transmit level ................................................................................... 23.8-4
Automatic gain control ............................................................................. 23.8-4
To configure data transmission parameters for the DSP4 card ............... 23.8-5
To configure data transmission parameters for the DSP5 card ............... 23.8-5
To configure data transmission parameters for the DSP5H card ............ 23.8-6
Subrate Switching
23.9.1
23.9.2
23.9.3
23.9.4
Table of Contents
(400)
xxxv
Table of Contents
Issue 1, November 1997
23.9.5
23.10 BONDING
23.10.1
23.10.2
23.10.3
24.2
xxxvi
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
25.1.2
25.2
25.3
25.4
FASTbus Configuration
25.4.1
25.4.2
Table of Contents
(400)
xxxvii
Table of Contents
Issue 1, November 1997
25.5
25.5.2
25.5.3
25.6
25.6.2
25.7.3
Class-of-service Parameters
25.8.1
xxxviii
25.8
25.7
(400)
Table of Contents
25.8.2
25.9
Table of Contents
Issue 1, November 1997
25.9.2
25.9.3
25.9.4
25.9.5
25.10.2
25.10.3
25.10.4
25.10.5
Table of Contents
(400)
xxxix
Table of Contents
Issue 1, November 1997
25.11.2
26.1.2
26.1.3
26.2
xl
(400)
Table of Contents
26.2.4
26.3
26.3.3
26.3.4
26.4
Table of Contents
Issue 1, November 1997
26.4.3
26.4.4
Table of Contents
(400)
xli
Table of Contents
Issue 1, November 1997
26.5
SVC Routing
26.5.1
26.5.2
26.5.3
26.5.4
27.1.3
27.1.4
27.2
27.2.3
xlii
(400)
Table of Contents
27.3
Standards Compliance
27.3.1
27.3.2
27.3.3
27.4
27.4.2
27.4.3
27.4.4
27.5.3
27.6
27.5
Table of Contents
Issue 1, November 1997
GFR Configuration
27.6.1
27.6.2
Table of Contents
(400)
xliii
Table of Contents
Issue 1, November 1997
27.6.3
27.6.4
27.7
Call Routing
27.7.1
27.7.2
27.7.3
27.7.4
27.7.5
xliv
(400)
Table of Contents
27.8
Trunk Circuits
27.8.1
27.8.2
27.8.3
27.8.4
27.8.5
27.9
Table of Contents
Issue 1, November 1997
27.9.2
27.9.3
27.9.4
Table of Contents
(400)
xlv
Table of Contents
Issue 1, November 1997
27.10.2
27.10.3
27.10.4
27.11.2
27.11.3
27.11.4
xlvi
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
27.13.2
27.13.3
27.13.4
27.13.5
27.13.6
27.13.7
27.13.8
27.13.9
Table of Contents
(400)
xlvii
Table of Contents
Issue 1, November 1997
27.14.6
27.14.7
xlviii
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
27.14.8
Table of Contents
(400)
xlix
Table of Contents
Issue 1, November 1997
27.14.11
27.14.12
27.15.5
27.15.6
(400)
Table of Contents
27.15.7
27.15.8
27.15.9
27.15.10
27.15.11
27.15.12
27.15.13
Table of Contents
Table of Contents
Issue 1, November 1997
(400)
li
Table of Contents
Issue 1, November 1997
27.17.2
27.17.3
27.18.2
lii
(400)
Table of Contents
27.18.3
Table of Contents
Issue 1, November 1997
27.20.2
27.20.3
27.20.4
27.20.5
27.20.6
Table of Contents
(400)
liii
Table of Contents
Issue 1, November 1997
28.1.4
28.1.5
28.1.6
28.1.7
28.1.8
28.1.9
28.1.10
28.2
28.2.4
liv
(400)
Table of Contents
28.2.5
28.2.6
Table of Contents
Table of Contents
Issue 1, November 1997
(400)
lv
Table of Contents
Issue 1, November 1997
28.3
29.1.2
29.2
lvi
(400)
Table of Contents
29.3
Non-ISDN Applications
29.3.1
29.3.2
29.3.3
29.3.4
29.4
Table of Contents
Issue 1, November 1997
ISDN Applications
29.4.1
29.4.2
29.4.3
29.4.4
30. CPCs
30.1
30.2
Table of Contents
(400)
lvii
Table of Contents
Issue 1, November 1997
30.3
30.3.4
30.4
CPC Connections
30.5.1
30.5.2
lviii
ISDN Indices
30.4.1
30.4.2
30.5
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
31.1.2
31.2
31.3
31.4.2
31.4.3
31.5
31.4
Table of Contents
(400)
lix
Table of Contents
Issue 1, November 1997
31.6
Broadband Circuits
31.6.1
31.6.2
31.6.3
31.6.4
31.6.5
31.7
31.9.2
31.9.3
31.9.4
lx
31.9
31.8
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
31.10.2
31.12.2
31.12.3
31.12.4
31.12.5
31.13.3
Table of Contents
(400)
lxi
Table of Contents
Issue 1, November 1997
31.14.2
31.15.2
31.15.3
lxii
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
List of Figures
Figure
Title
16.2-1
16.2-2
16.2-3
16.2-4
16.2-5
16.2-6
16.2-7
16.2-8
16.2-9
16.3-1
16.3-2
16.4-1
16.4-2
16.4-3
16.4-4
16.4-5
16.5-1
16.5-2
16.5-3
16.5-4
16.5-5
16.5-6
16.5-7
16.5-8
16.5-9
17.1-1
17.1-2
17.2-1
17.2-2
17.2-3
17.2-4
Table of Contents
(400)
lxiii
Table of Contents
Issue 1, November 1997
17.2-5
17.2-6
17.2-7
17.2-8
17.2-9
17.3-1
17.3-2
17.4-1
17.5-1
17.6-1
17.6-2
17.6-3
17.6-4
17.6-5
17.6-6
17.6-7
17.6-8
17.6-9
17.6-10
17.6-11
17.6-12
17.6-13
18.2-1
18.2-2
18.2-3
18.2-4
18.3-1
20.4-1
20.4-2
20.4-3
20.4-4
20.4-5
20.4-6
20.4-7
20.5-1
20.6-1
20.6-2
20.9-1
20.9-2
20.9-3
20.10-1
lxiv
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
20.11-1
20.12-1
20.12-2
20.14-1
20.14-2
20.14-3
20.14-4
20.14-5
20.15-1
20.16-1
20.17-1
20.17-2
20.17-3
20.18-1
20.18-2
20.18-3
20.19-1
20.19-2
20.20-1
20.20-2
20.20-3
20.20-4
20.20-5
21.3-1
21.3-2
21.5-1
21.9-1
21.9-2
21.9-3
21.11-1
22.3-1
22.3-2
22.3-3
22.3-4
22.3-5
22.3-6
22.3-7
22.3-8
22.3-9
Table of Contents
(400)
lxv
Table of Contents
Issue 1, November 1997
22.3-10
22.3-11
22.3-12
23.3-1
23.3-2
23.4-1
23.4-2
23.4-3
23.4-4
23.5-1
23.5-2
23.5-3
23.5-4
23.5-5
23.5-6
23.5-7
23.6-1
23.6-2
23.6-3
23.6-4
23.6-5
23.6-6
23.6-7
23.6-8
23.6-9
23.6-10
23.6-11
23.6-12
23.6-13
23.6-14
23.6-15
23.6-16
23.6-17
23.6-18
23.6-19
23.6-20
23.6-21
23.6-22
23.6-23
23.6-24
23.6-25
23.6-26
23.6-27
23.6-28
23.6-29
23.6-30
23.6-31
23.6-32
23.6-33
lxvi
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
23.6-34
23.6-35
23.6-36
23.6-37
23.6-38
23.6-39
23.6-40
23.6-41
23.6-42
23.7-1
23.7-2
23.9-1
23.9-2
23.10-1
23.10-2
23.10-3
23.10-4
23.10-5
23.12-1
25.1-1
25.1-2
25.1-3
25.1-4
25.1-5
25.1-6
25.1-7
25.3-1
25.3-2
25.4-1
25.4-2
25.4-3
25.4-4
25.4-5
25.6-1
25.6-2
25.6-3
25.7-1
25.7-2
25.7-3
25.7-4
25.7-5
Table of Contents
(400)
lxvii
Table of Contents
Issue 1, November 1997
25.8-1
25.8-2
25.8-3
25.9-1
25.9-2
25.10-1
25.10-2
25.10-3
25.10-4
25.10-5
25.10-6
25.10-7
25.11-1
25.11-2
26.1-1
26.1-2
26.1-3
26.1-4
26.1-5
26.2-1
26.2-2
26.3-1
26.4-1
26.5-1
26.5-2
27.1-1
27.1-2
27.1-3
27.1-4
27.1-5
27.2-1
27.2-2
27.2-3
27.2-4
27.2-5
27.2-6
27.2-7
lxviii
(400)
Table of Contents
27.2-8
27.2-9
27.2-10
Table of Contents
Issue 1, November 1997
27.4-1
27.4-2
27.5-1
27.5-2
27.6-1
27.6-2
27.6-3
27.6-4
27.6-5
27.6-6
27.6-7
27.6-8
27.6-9
27.6-10
27.7-1
27.7-2
27.7-3
27.7-4
27.7-5
27.7-6
27.7-7
27.7-8
27.7-9
27.7-10
27.7-11
27.7-12
27.7-13
27.7-14
27.7-15
27.8-1
27.8-2
27.9-1
27.9-2
27.9-3
27.9-4
27.9-5
27.9-6
27.9-7
27.9-8
27.9-9
Table of Contents
(400)
lxix
Table of Contents
Issue 1, November 1997
27.10-1
27.10-2
27.10-3
27.10-4
27.10-5
27.10-6
27.10-7
27.10-8
27.10-9
27.11-1
27.11-2
Data Collector Agent XACs and Data Collector Interface XACs ............................. 27.11-2
Data Collector Agent Parameters Display .............................................................. 27.11-5
27.12-1
27.13-1
27.13-2
27.13-3
27.13-4
27.13-5
27.13-6
27.13-7
27.13-8
27.13-9
27.13-10
27.13-11
27.13-12
27.13-13
27.13-14
27.14-1
27.14-2
27.14-3
27.14-4
27.14-5
27.14-6
27.14-7
27.15-1
27.15-2
27.15-3
27.15-4
27.15-5
27.15-6
27.15-7
27.16-1
27.17-1
27.17-2
lxx
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
27.18-1
27.18-2
27.19-1
27.19-2
27.19-3
27.20-1
27.20-2
27.20-3
27.20-4
27.20-5
27.20-6
27.20-7
27.20-8
28.1-1
28.1-2
28.1-3
28.1-4
28.2-1
28.2-2
28.3-1
29.1-1
29.1-2
29.3-1
29.3-2
29.3-3
29.4-1
29.4-2
30.3-1
30.3-2
31.1-1
31.1-2
31.4-1
31.4-2
31.4-3
31.4-4
31.4-5
31.4-6
31.4-7
Table of Contents
(400)
lxxi
Table of Contents
Issue 1, November 1997
31.6-1
31.6-2
31.6-3
31.9-1
31.9-2
31.9-3
31.9-4
31.10-1
31.12-1
31.12-2
31.12-3
31.13-1
31.13-2
List of Tables
Table
Title
16.2-1
16.2-2
16.2-3
16.2-4
16.3-1
16.4-1
16.4-2
16.5-1
16.5-2
17.1-1
17.1-2
17.1-3
17.2-1
17.2-2
17.2-3
17.2-4
17.2-5
17.2-6
lxxii
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
17.3-1
17.3-2
17.3-3
17.4-1
17.5-1
17.5-2
17.5-3
Access Level and Password Configuration Parameters and Options ..................... 17.5-2
Suggested Access Level Definitions for Control Card Sessions .............................. 17.5-5
Suggested Access Level Definitions for FRS, FRE and PE Card Sessions ............. 17.5-6
17.6-1
17.6-2
17.6-3
17.6-4
18.1-1
18.1-2
18.1-3
18.1-4
18.1-5
18.1-6
18.1-7
18.1-8
18.2-1
18.3-1
18.3-2
18.3-3
18.3-4
18.3-5
19.1-1
19.1-2
19.1-3
19.1-4
19.1-5
19.1-6
19.1-7
19.3-1
20.1-1
20.1-2
20.1-3
Modules Supported by the T1, E1 and Optical Extension Cards .............................. 20.1-3
T1 PRI Card Configuration Parameters and Options ............................................... 20.1-6
E1 PRI Card and Optical Extension Card
Configuration Parameters and Options .............................................................. 20.1-9
MPA Card Configuration Parameters and Options ................................................. 20.1-12
TTC2M Card Configuration Parameters and Options ............................................. 20.1-14
X.21 and V.35 PRI Card Configuration Parameters and Options ........................... 20.1-15
DS-3 and DS-3 II Card Configuration Parameters and Options ............................. 20.1-17
E3 Card Configuration Parameters and Options .................................................... 20.1-19
20.1-4
20.1-5
20.1-6
20.1-7
20.1-8
Table of Contents
(400)
lxxiii
Table of Contents
Issue 1, November 1997
20.2-1
20.2-2
20.3-1
20.4-1
20.4-2
20.6-1
20.6-2
20.6-3
20.6-4
20.8-1
20.9-1
20.9-2
20.9-3
20.9-4
20.9-5
20.9-6
20.10-1
20.10-2
20.11-1
Fault Signalling Codes Seized and Idle for PRI Cards ........................................... 20.11-2
20.12-1
20.12-2
20.12-3
20.12-4
20.13-1
20.14-1
20.14-2
20.14-3
20.17-1
20.17-2
20.18-1
20.18-2
20.18-3
20.18-4
20.18-5
20.18-6
20.18-7
lxxiv
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
20.19-1
20.19-2
20.19-3
20.19-4
20.20-1
20.20-2
20.20-3
20.20-4
20.20-5
21.1-1
21.1-2
21.1-3
21.1-4
21.1-5
21.1-6
21.1-7
21.1-8
21.1-9
21.2-1
21.2-2
21.3-1
21.3-2
21.3-3
21.3-4
21.3-5
21.5-1
21.5-2
21.5-3
21.5-4
21.5-5
21.5-6
21.5-7
21.5-8
TLP Levels and Line Impedance for 4WTO Line Card ............................................. 21.5-2
TLP Levels and Line Impedance for E&M Cards ...................................................... 21.5-2
TLP Levels and Line Impedance for LGE Cards ...................................................... 21.5-3
TLP Levels and Line Impedance for LGS Cards ...................................................... 21.5-4
TLP Levels and Line Impedance for E&M Channel Units ......................................... 21.5-5
TLP Levels and Line Impedance for LGE and LGS Channel Units .......................... 21.5-5
TLP Levels and Line Impedance for the 4WDX Channel Unit .................................. 21.5-6
TLP Levels and Line Impedance for MRD Channel Units ........................................ 21.5-6
21.6-1
21.7-1
21.10-1
Loop Balance Options for the 4WDX Channel Unit ................................................ 21.10-1
21.11-1
22.1-1
22.1-2
22.1-3
22.1-4
22.1-5
Table of Contents
(400)
lxxv
Table of Contents
Issue 1, November 1997
22.1-6
22.1-7
22.1-8
22.1-9
22.1-10
22.1-11
22.1-12
22.3-1
22.3-2
22.3-3
22.3-4
22.3-5
22.3-6
22.3-7
22.3-8
22.3-9
22.3-10
22.4-1
22.4-2
23.1-1
23.1-2
23.1-3
23.1-4
23.3-1
23.6-1
23.6-2
23.6-3
23.6-4
23.6-5
23.6-6
23.6-7
23.6-8
23.6-9
23.6-10
23.6-11
23.6-12
23.6-13
23.6-14
Data Card Interface Speeds for DDS Rate Adaption ................................................ 23.6-7
X.50 Division 2 Phases and Frames ....................................................................... 23.6-12
X.50 DSP Applications ............................................................................................ 23.6-14
Transparent and HCM SRM Support ...................................................................... 23.6-22
DDS SRM Support .................................................................................................. 23.6-23
X.50 and X.50 Telco SRM Support ......................................................................... 23.6-23
Transport Bandwidth and Transport Position for
Transparent Rate Adaption .............................................................................. 23.6-38
End-to-End H-bit Signalling Configurations ............................................................ 23.6-40
HCM Interface Speeds ........................................................................................... 23.6-41
X.50 Interface Speeds ............................................................................................ 23.6-42
Valid Subframe Positions for DDS .......................................................................... 23.6-44
Valid Subframe Positions for X.50 .......................................................................... 23.6-44
Configuration Process ............................................................................................ 23.6-46
Rate Adaption and SRM Parameters ..................................................................... 23.6-47
23.7-1
23.8-1
lxxvi
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
23.9-1
23.9-2
23.9-3
23.9-4
23.12-1
24.1-1
25.1-1
25.1-2
25.1-3
25.1-4
25.1-5
25.1-6
25.3-1
25.4-1
25.4-2
25.5-1
25.6-1
25.6-2
25.7-1
25.7-2
25.7-3
25.7-4
25.8-1
25.9-1
25.9-2
25.9-3
25.9-4
25.9-5
25.9-6
25.9-7
25.10-1
25.10-2
25.10-3
25.10-4
25.11-1
26.2-1
26.2-2
26.3-1
Table of Contents
(400)
lxxvii
Table of Contents
Issue 1, November 1997
26.5-1
26.5-2
27.2-1
27.2-2
27.2-3
27.2-4
27.2-5
27.2-6
27.2-7
27.2-8
27.3-1
27.3-2
27.3-3
27.4-1
27.4-2
27.4-3
27.4-4
27.4-5
27.4-6
27.4-7
27.4-8
27.4-9
27.4-10
27.4-11
27.4-12
27.4-13
27.5-1
27.6-1
27.6-2
27.6-3
27.7-1
27.8-1
27.10-1
27.10-2
27.10-3
27.11-1
lxxviii
(400)
Table of Contents
Table of Contents
Issue 1, November 1997
27.13-1
27.13-2
27.13-3
27.13-4
27.14-1
27.14-2
27.14-3
27.14-4
27.14-5
27.16-1
27.17-1
27.20-1
28.1-1
28.1-2
28.1-3
28.1-4
28.1-5
29.1-1
29.1-2
29.3-1
30.1-1
30.4-1
31.1-1
31.1-2
31.2-1
31.4-1
31.4-2
31.7-1
31.9-1
31.9-2
31.11-1
31.12-1
31.12-2
31.12-3
31.12-4
Table of Contents
(400)
lxxix
Table of Contents
Issue 1, November 1997
31.12-5
31.13-1
31.14-1
31.14-2
31.15-1
31.15-2
31.18-1
31.19-1
Fault Signalling Codes Seized and Idle for VT-1.5 and TU-12 Cards .................... 31.19-2
31.20-1
lxxx
(400)
Table of Contents
Foreword
Issue 1, November 1997
Foreword
The Foreword outlines the systems and services described in the 3600 MainStreet
Bandwidth Manager Family Technical Practices, and lists the software generics that
support these systems and services. It briefly describes what is contained in each
volume of the Technical Practices and the special text conventions used, and
provides a list of suggested reading material.
System Support
This release of the 3600 MainStreet Bandwidth Manager Family Technical Practices
provides information required for the installation, operation and configuration, and
maintenance of the systems and services listed in Table 1.
Table 1: System and Services Support
Release (1)
System or Service
Software Generic
7.0 F
1117
7.0 F
S1117
7.0 F
C117/D117/H117/E117
7.0 F
Q117
7.0 F
1117
7.0 F
C117/D117/H117/E117
3.0 H
1.2 F
Notes
1. H indicates hardened product release.
F indicates field trial release.
(400)
lxxxi
Foreword
Issue 1, November 1997
Feature support
Some systems do not have all the components and features described in the
Technical Practices. The components and features that Newbridge supports are
determined by the type of system, the revision level of the installed cards, the generic
release of the installed system software, and the generic release of the Craft Interface,
4601 MainStreet Network Manager, 4601A MainStreet Auxiliary Network Manager,
4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020 Network
Manager software in use. If a feature is configured for an installed card that does not
support the feature, the card or affected circuit is busied out and a revision/feature
mismatch alarm is raised for that slot. For information on alarms, see Maintenance.
Node management
The node management procedures described in the Technical Practices are done
through a node management session initiated from any of the 4601 MainStreet
Network Manager, 4601A MainStreet Auxiliary Network Manager, 4602 MainStreet
Intelligent NetworkStation or MainStreetXpress 46020 Network Manager, the Craft
Interface node manager or an ASCII (VT100-type) terminal.
If you are using a 4601 MainStreet Network Manager, 4601A MainStreet Auxiliary
Network Manager, 4602 MainStreet Intelligent NetworkStation or MainStreetXpress
46020 Network Manager, see the appropriate documentation for instructions on
how to install and commission your network manager and how to manage your
node. The 4601 MainStreet Network Manager, 4601A MainStreet Auxiliary Network
Manager, 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020
Network Manager documentation refers to the Technical Practices when necessary.
If you are using the Craft Interface, refer to your Craft Interface documentation for
instructions on how to install and commission your node manager. Refer to the
Technical Practices for instructions on how to manage your node.
If you are using an ASCII terminal, see Technical Overview for instructions on how to
install and commission your node management terminal. See the remainder of the
Technical Practices for instructions on managing your node.
Technical Overview
Technical Overview provides an introduction to the MainStreet family of bandwidth
managers.
Installation
Installation provides the procedures required to install all 3600 MainStreet series
bandwidth manager systems.
lxxxii
(400)
Foreword
Issue 1, November 1997
Maintenance
Maintenance provides the procedures required to monitor system operation, isolate
faults, service failed components, and perform system upgrades.
Reference documents
It is recommended that you read the following documents:
Conventions
This section describes the text conventions used throughout the Technical Practices.
Special information
These conventions are used to draw your attention to special information:
Danger
Danger means that the described activity or situation may cause personal injury.
Warning
A warning means that the described activity or situation may or will cause
equipment damage.
(400)
lxxxiii
Foreword
Issue 1, November 1997
Caution
A caution means that the described activity or situation may or will cause service
interruption.
Note
A note provides special information.
Description
Example
<Key>
<Esc>
<variable>
<sn>
<LITERAL>
<CPSS>
2.
Steps are denoted by arabic numerals and describe actions that must be
performed. Complete each step in order. This step has substeps.
i.
Substeps are denoted by roman numerals and detail the actions involved
in a complex step. Complete each substep in order.
ii.
lxxxiv
Options are denoted by letters and are conditional actions that depend on
your system requirements. Perform only the applicable option.
i.
ii.
(400)
Foreword
Issue 1, November 1997
MuLaw*
ALaw
SK000002
(400)
lxxxv
16.1
16.1.1
16.1.2
Getting Started
Explains how to use the manual, how to run a node management session and how
to display information about the system configuration.
Node Parameters
Explains how to configure parameters that apply to a node as a whole, or to all the
cards installed in the system; explains general circuit connections, CPSS
configuration and network synchronization.
Redundancy
Explains how to configure control redundancy, protection switching and PRI
redundancy.
Getting Started
(400)
16.1-1
System Cards
Describes the system cards and provides configuration procedures for the Control,
Expander, Switching, Common Carrier, Test and General Facilities cards.
PRI Cards
Describes the PRI cards and explains how to configure T1, E1, MPA, TTC2M, X.21
PRI, X.21 ESI PRI, V.35 PRI, DS-3 and E3 cards.
DCP Cards
Describes DCP cards and explains how to configure them.
16.1-2
(400)
Getting Started
CPCs
Describes the ISDN backup application and explains how to configure CPCs.
HSA Cards
Describes the SONET and SDH applications and explains how to configure HSA
cards.
Note
For instructions on trouble shooting, viewing alarms, using the GFC, GFC2, GFC3
and Test cards and servicing failed components, see Maintenance.
Getting Started
(400)
16.1-3
16.2
16.2.1
All MainStreet functions are software-driven and all configurable parameters are
stored in a non-volatile configuration database. You can access all functions and
parameters during a node management session by reading from and writing to the
configuration database. A node management session is conducted using the CPSS
protocol. CPSS is Newbridges proprietary X.25-based management protocol (for
more information on CPSS, see chapter 17.6).
Figure 16.2-1 shows the nodes with which you can have a node management session.
Getting Started
(400)
16.2-1
Switching
shelf
Node
management
session
Locally controlled
switching shelf
High speed
peripheral shelf
major nodes
minor nodes
Major nodes
The major nodes are:
Control cards
HSPS DS-3 or DS-3II cards
HSPS2 SE3 and DE3 cards
A major node is assigned a CPSS address. The configuration database of a locally
controlled, enhanced locally controlled or peripheral shelf contains all system and
card-specific parameters and functions for all cards installed in the shelf (except for
minor nodes). The configuration database of a switching shelf Control card contains
all DCS connections configured for all the peripheral shelves, HSPSs and HSPS2s
connected to it. Each HSPS and HSPS2 card configuration database contains all
system and card-specific parameters required by the card.
16.2-2
(400)
Getting Started
Minor nodes
The minor nodes are:
CPC
DCC
DCP card
DSP5 and DSP5H cards
DTUs
Dual E1 card
Dual E1-2 card
Dual T1 card
Dual T1-2 card
FRE card
FRS card
MPA card
PE card
A minor node does not have a CPSS address. It is identified by the CPSS address of
the major node and by the slot it occupies in the major node. The configuration
database of a minor node includes all card-specific parameters and functions. All
general system parameters are configured through a node management session with
the major node.
Getting Started
(400)
16.2-3
16.2.2
Management Stations
You can initiate a node management session from any of the following management
stations:
Network managers
The network managers are the preferred tools for network management and remote
node management. The 4602 MainStreet Intelligent NetworkStation,
MainStreetXpress 46020 Network Manager and 4601 MainStreet Network Manager
are network managers. They are connected to the network to manage the network
and any node on the network.
The 4602 MainStreet Intelligent NetworkStation and MainStreetXpress 46020
Network Manager are Sun-based software programs designed for large networks.
They can configure and operate all 3600 MainStreet series bandwidth managers and
provide an advanced graphical user interface in addition to the NMTI. The graphical
user interface is used to simplify network and node configuration and operation
procedures. You can do all configuration and operation procedures through the
NMTI.
The 4601 MainStreet Network Manager is a PC-based software program designed
for small- to medium-sized networks; it can configure and operate all
3600 MainStreet series bandwidth managers. It provides a graphic user interface to
simplify connections to remote nodes. You can do all configuration and operation
procedures through the NMTI.
If you are using a network manager, see the appropriate network management
documentation to install and commission your network manager and manage your
node. The network management documentation describes how to initiate a node
management session with a node and refers you to the 3600 MainStreet Bandwidth
Manager Family Technical Practices when necessary.
16.2-4
(400)
Getting Started
The Craft Interface is a PC-based software program designed for node installation
and initial configuration or on-site trouble shooting. It provides NMTI access to all
MainStreet nodes (major and minor). You can do all configuration and operation
procedures through the Craft Interface.
If you are using the Craft Interface, see your Craft Interface documentation to install
and commission your node manager and to initiate a node management session. See
the 3600 MainStreet Bandwidth Manager Family Technical Practices to manage your
node.
The 3600+ MainStreet system has the automatic baud rate matching feature enabled
by default. For information about setting the baud rate, see chapter 17.3.
Getting Started
(400)
16.2-5
16.2.3
SP1
SP2
Connector
Type
Figure
RJ45
16.2-2
RJ45
16.2-3
DB25
(female)
16.2-4
DB25
(female)
16.2-5
RJ45
16.2-9
Backplane Location
Bulkhead Location
Faceplate Location
16.2-6
Control cards
CPC
RJ45
16.2-6
DCP card
RJ45
16.2-7
DS-3 II card
RJ45
16.2-8
E3 card
RJ45
16.2-8
RJ45
16.2-8
FRS card
RJ45
16.2-6
(400)
Getting Started
Connection Type
Null modem
Null modem
Backplane or
Bulkhead Serial
Port 1
Control Card
Faceplate Serial
Port
Class A
Class B
Class A
Class B
(1)
(1)
Inactive
Inactive
Active
Active
Active
Active
Inactive
Inactive
Active
Active
Inactive
Inactive
Inactive
Inactive
Active
Active
Notes
1. In a dual-shelf, non-control-redundant system, the Control card uses the backplane or bulkhead SP1
connector of the shelf in which it is installed. The backplane or bulkhead SP1 connector of the shelf
without a Control card is not used.
Note
For an NMTI session in a dual-shelf, control-redundant system, connect the
management station to backplane or bulkhead SP1 on both shelves using a Y-cable.
This ensures a connection to the active Control card no matter which shelf is the
active shelf.
Getting Started
(400)
16.2-7
For the active 3600+ MainStreet Control card, insertion of jumper W4 enables SP1 on
the faceplate while disabling SP1 on the bulkhead. See chapter 17.3 for more
information about serial ports and W4 jumper insertion. Access to the inactive
Control card faceplate serial port is available only if W4 is inserted and the node
management station is directly connected.
Several other cards provide faceplate serial ports. These serial ports act as extensions
of the system serial ports in the active shelf only. They provide an alternate
connection point for a management station. Table 16.2-1 lists the system serial ports
supported on 3600 MainStreet series bandwidth manager systems and the pinout
figure number for each.
Default configuration
System serial ports have the default configuration listed in Table 16.2-4. Only port
type, CPSS cost and baud rate are configurable (see chapter 17.3).
Table 16.2-4: System Serial Port Configuration
Serial Port
CPSS
Cost
Data
Bits
Stop
Bits
Parity
Baud
Rate (2)
Gender (3)
VT100
Normal
None
9600
DCE
CPSS_MODEM
Normal
None
1200
DTE
Notes
1. Port type is configurable only on backplane or bulkhead and Control, DS-3 II and E3 card serial ports.
For most other card faceplate serial ports, port type is CPSS. For the CPC, port type is VT100.
2. For CPC and DCP faceplate serial ports, the default baud rate for both serial ports is 9600. For all
other faceplate serial ports, the default baud rates are as shown in the table.
3. For CPC, DCP, FRS, FRE and PE card faceplate serial ports, the gender of both serial ports is DCE.
For all other faceplate serial ports, the gender is listed in the table.
Pinouts
Figures 16.2-2 through 16.2-9 show the pinouts for all system serial ports.
16.2-8
(400)
Getting Started
Figure 16.2-2: Serial Port Pinouts for a Class A Locally Controlled Shelf System
SP1
P5
P6
P7
P8
P9
P10
P11
P12
SP2
CTRL A
CTRL B
Serial port 1
(DCE)
Serial port 2
(DTE)
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
4798
Note
Hardware flow control is supported on SP2 only. For SP1 only, RTS is connected to
CTS and DTR is connected to DSR by the backplane.
Getting Started
(400)
16.2-9
Figure 16.2-3: Serial Port Pinouts for a Class A Switching Shelf System
SP1
SP2
J29A
J29B
J30A
J30B
Serial port 1
(DCE)
Serial port 2
(DTE)
1
2
3
4
5
6
7
8
1
2
3
4
5
6
7
8
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
CTS
RTS
RXD
TXD
Signal GND
DTR
DSR
Chassis GND
4799
Note
Hardware flow control is supported on SP2 only. For SP1 only, RTS is connected to
CTS and DTR is connected to DSR by the backplane.
Warning
Do not make connections to pins identified as n/c in Figure 16.2-4.
16.2-10
(400)
Getting Started
Figure 16.2-4: Serial Port Pinouts for a Class B or 23-inch Locally Controlled or
Peripheral Shelf System
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
Note
Hardware flow control is supported on SP2 only. For SP1 only, RTS is connected to
CTS and DTR is connected to DSR by the backplane.
Warning
Do not make connections to pins identified as n/c in Figure 16.2-5.
Getting Started
(400)
16.2-11
Figure 16.2-5: Serial Port Pinouts for a Class B or 23-inch Switching Shelf System
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
n/c
TXD
RXD
RTS
CTS
DSR
GND
n/c
n/c
n/c
n/c
n/c
n/c
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
n/c
n/c
n/c
n/c
n/c
n/c
DTR
n/c
n/c
n/c
n/c
n/c
Note
Hardware flow control is supported on SP2 only. For SP1 only, RTS is connected to
CTS and DTR is connected to DSR by the backplane.
Warning
Do not make connections to pins identified as n/c in Figures 16.2-6 through 16.2-9.
16.2-12
(400)
Getting Started
Figure 16.2-6: Serial Port Pinout for CPC and FRS Card Faceplates
Serial port 1 (DCE)
Chassis GND
+12V
n/c
Signal GND
TXD
RXD
n/c
+12V
8
7
6
5
4
3
2
1
Chassis GND
DSR
DTR
Signal GND
TXD
RXD
+12V
n/c
8
7
6
5
4
3
2
1
8022
8
7
6
5
4
3
2
1
Chassis GND
+12V
n/c
Signal GND
TXD
RXD
n/c
+12V
8
7
6
5
4
3
2
1
8021
Figure 16.2-8: Serial Port Pinout for DS-3, E3, FRE and PE Card Faceplates
Serial port 1 (DCE)
Chassis GND
+12V
n/c
Signal GND
TXD
RXD
n/c
+12V
8
7
6
5
4
3
2
1
8023
Getting Started
(400)
16.2-13
8
7
6
5
4
3
2
1
9698
16.2-14
(400)
Getting Started
16.3
screen layout
softkeys
keyboard entries
It also provides a sample node management session and explains how to program
automatic log-off.
16.3.1
Craft Interface
To initiate a node management session from a Craft Interface node manager, see
your Craft Interface documentation.
ASCII terminal
To initiate a node management session from an ASCII (VT100) terminal:
make sure that the ASCII terminal is connected to a system serial port
power on the terminal
configure the terminal to match the selected system serial port
press a few times
After you initiate it, the node management session user interface is the same for all
Newbridge nodes regardless of the management station used.
Getting Started
(400)
16.3-1
16.3.2
Screen Layout
The node management session provides a screen 78 characters wide by 24 lines long;
the screen has six functional areas, as shown in Figure 16.3-1. As you make selections
or enter information, the areas of the screen change to display relevant information.
Figure 16.3-1: Header Line Fields
Product
Generic_Release
F1-CONFIG
F6-
long_name
F2-HOUSE
F7-
F3-MAINT
F8-
Alarms
F4-STATS
F9-QUIT
Date
Time
F5-ALARMS
F0-
Header line
The information displayed in the header line (from left to right) depends on the node
with which you are having a node management session.
Product
The type of node to which you are connected, for example the 3600 MainStreet node.
Generic release
The node software version number of the node to which you are connected.
Table 16.3-1 lists the software version numbers of each type of node.
Long name
This field describes which shelf you are connected to and varies depending on the
type of node to which you are connected. Table 16.3-1 lists the long names associated
with each type of node.
16.3-2
(400)
Getting Started
Alarms
The number of unacknowledged alarms in the Major/Prompt alarm queue. For a
session with a major node, the number refers only to the queue of the major node.
For a session with a minor node, the number refers only to the queue of the minor
node.
Date
The date set for the shelf Control card (even for sessions with a minor node). If no
date has been set, No Date appears.
Time
The time set for the shelf Control card (even for sessions with a minor node). Time
is displayed in hours, minutes and seconds in 12- or 24-hour format (hh:mm:ssA, P or
H). If the time has not been set, the number of hours, minutes and seconds since the
last system reset is displayed (hh:mm:ssR).
Table 16.3-1: Generic Release Numbers and Long Names
Node
Generic Release
Long Name
S1117-ab-cd
x117-ab-cd (1)
C117-ab-cd
D117-ab-cd
H117-ab-cd
HSPS2 E3 card
E117-ab-cd
FRS card
P114-ab-cd
node_name:sn (5)
FRE card
P412-ab-cd
node_name:sn (5)
PE card
P611-ab-cd
node_name:sn (5)
Notes
1. where x is 1 for the 3600 MainStreet node or x is Q for the 3664 MainStreet node
2. where s is the shelf identifier (A or B)
3. where s is the shelf identifier (1 or 2)
4. where n is the number of the Switching card to which this peripheral shelf or DS-3, DS-3 II or E3 card
is connected (1 to 8) and where s is the peripheral shelf or DS-3, DS-3 II or E3 card identifier (A or B)
5. where node_name is the name configured for the Control card of the major node and where sn is the
shelf and slot identifier of the slot occupied by the minor node (s = A or B; n = 1 to 8)
Data area
This area displays information associated with the current menu item.
Getting Started
(400)
16.3-3
Command line
This line displays softkey selections and keyboard entries.
Diagnostics line
This line displays prompts, error messages and information about the valid range
for numeric entries.
Softkey area
This area displays softkeys associated with function keys <F1> through <F10> (or
number keys <1> to <9> and <0>).
Status line
The status line appears only when you use the Craft Interface. See your Craft
Interface documentation for a description of the information on the status line.
16.3.3
Softkeys
A softkey is a key that is associated with different functions (commands) at different
times. The softkeys available at any time depend on previous softkey selections.
Selecting a softkey selects the function associated with it at that time.
Softkeys are described according to the name of the function displayed for that
softkey. Function names are usually upper case (for example, HOST). They may
contain underscores (HELLO_TIME), hyphens (END-TO-END), or obliques
(RTS/CTS). In this manual, the term softkey is used to describe both the key
associated with a particular function and the function itself.
The softkey area displays the available softkeys. Each softkey is associated with a
function key (<F1> through <F10>) or number key (<1> through <9> and <0>) on
the keyboard.
In the 3600 MainStreet Bandwidth Managers Family Technical Practices, softkeys are
written as they appear on the screen.
16.3-4
(400)
Getting Started
Softkey menus
A menu is a group of softkeys displayed at one time.
The main menu is the group of six softkeys displayed after you have logged on to a
node.
Selecting softkeys
There are two ways to select a softkey.
Press the function key (<F1> through <F10>) associated with the softkey.
Press the <Esc> key and then press the number key (<1> through <9> and <0>)
associated with the softkey.
Number keys <1> to <9> are associated with function keys <F1> to <F9>. Number
key <0> is associated with function key <F10>.
For example, in Figure 16.3-2, you can select the CONFIG softkey from the main
menu with either of the following key sequences:
<F1> or <Esc> <1>
Softkeys are added to the command line as you select them (exceptions are MORE,
CANCEL, QUIT, PROCEED and display-related softkeys such as SHOW_SLOTS).
Figure 16.3-2: Main Menu for the MainStreet Node
3600 MainStreet
F1-CONFIG
F6-
Getting Started
1117-H1-00
Toronto:A
F2-HOUSE
F7-
F3-MAINT
F8-
(400)
Alarms:1
11-May-1997
F4-STATS
F9-QUIT
8:35a
F5-ALARMS
F0-
16.3-5
Instructions
An instruction is a sequence of softkey selections and keyboard input that results in
an action or change of state. The instruction takes effect only after the PROCEED
softkey is displayed and selected. See the subsection To execute an instruction
(PROCEED).
Toggle softkeys
You use a toggle softkey to select one of two mutually exclusive commands
associated with one softkey.
When you select a toggle softkey, the activity governed by the softkey (and the
softkey label) changes to the alternative option, usually opposite to the original.
For example, when you select MAINT DIAG, the softkey associated with function
key <F3> (DISABLE/ENABLE) is a toggle softkey. When you select DISABLE,
background diagnostic tests are disabled and the softkey changes to read ENABLE.
When you select ENABLE, background diagnostic tests are enabled and the softkey
changes to read DISABLE.
Softkey groups
Some softkeys are grouped so that you can select only one softkey in a group. The
selected function is added to the command line or displayed in the data area and
removed from the softkey area.
For example, when you select HOUSE SER_PORT_1 BAUD_RATE, five baud
rates are displayed. The sixth (currently selected) baud rate appears in the data area
but not in the softkey area. If you select a new baud rate, it is removed from the
softkey area and replaces the old baud rate displayed in the data area. The old baud
rate now appears in the softkey area.
Display-related softkeys
Some softkeys are used to display information while you are entering an instruction.
These softkeys change the display in the data area without interrupting the
instruction. Display softkeys are SHOW_A, SHOW_B, SHOW_SLOTS,
SHOW_GROUP/SHOW_CCT, SHOW_CUR and SHOW_LIST.
16.3-6
(400)
Getting Started
From the main menu, QUIT logs you off the node and displays the management
To log off
To log off (terminate the node management session), select QUIT (<F9>) until you
see the main menu; then, from the main menu, select QUIT again.
The node management session ends and the management station main menu (if any)
appears.
Note
Depending on the configuration specified by your site planner, you may or may not
have access to all of the softkeys. For example, if a particular level of access does not
allow configuration, the CONFIG softkey on the main menu will be inaccessible. For
more information on access levels, see chapter 17.5.
Getting Started
(400)
16.3-7
16.3.4
Keyboard Entries
You make keyboard entries using the alphanumeric keys on the keyboard. For
example, you must enter circuit identifiers, node names, or interface speeds. The
node management session user interface indicates that a keyboard entry is required
in three ways.
As you enter information, your entry replaces the prompt on the command line. Use
the <Delete> or <Backspace> key to correct typing errors.
In this manual, keyboard entries are indicated by text in angle brackets (< >). A
description of the keyboard entry is given using italics surrounded by angle
brackets, for example <number> and <sn-cc>.
16.3-8
(400)
Getting Started
16.3.5
If you are using a network manager, see the appropriate network manager
documentation.
b.
If you are using the Craft Interface node manager, see your Craft Interface
documentation.
c.
If you are using an ASCII (VT100) terminal, make sure that the ASCII
terminal is connected to a system serial port, powered on and configured
to match the selected system serial port; then press a few times.
The system prompts for your access level.
2.
3.
Enter the password (the system is not case sensitive; you can enter the
password in upper or lower case or any combination of upper and lower case).
The default password is <mainstreet>.
The main menu appears (see Figure 16.3-2).
Note
4.
5.
Getting Started
(400)
16.3-9
6.
To select CANCEL or QUIT, enter <Esc> <8> or <Esc> <9>, respectively; if you are
using function keys F8 or F9, you do not need to press <Esc> first. If you simply
entered <8> or <9>, the management station would assume that the number was
part of the slot identifier (a keyboard entry) and add it to the command line.
7.
8.
9.
16.3-10
(400)
Getting Started
MuLaw*
ALaw
SK000003
In this manual, a series of softkey selections and keyboard entries is shown in a tree
form. The tree begins with a single line containing selections and entries with long
dashes between them. The return key is shown as . When you have a choice
between two different keys, the tree branches into a second line. Further choices
result in further branches. For example, this procedure would be shown as:
The softkey PROCEED (used to execute the instruction) is not included because the
management station prompts for it.
16.3.6
To program automatic log-off, select the shelf or card and choose SESSN_TIME. If
there is an automatic log-off programmed, the system displays it on the screen. To
select the new automatic log-off time, press the appropriate number key.
If you select NONE, the terminal stays logged on to the system until you log off
manually by selecting QUIT from the main menu.
Getting Started
(400)
16.3-11
5_MIN
10_MIN
15_MIN
30_MIN*
NONE
SK000004
Note 1
You do not need to select MORE for FRS, FRE or PE cards.
Note 2
The automatic log-off setting is not preserved during a database backup or restore.
When the backup or restore is complete, the automatic log off time is set to the
default (30 min).
16.3-12
(400)
Getting Started
16.4
Using Identifiers
This chapter describes the node management session identifiers used for shelves,
slots and links, and circuits.
16.4.1
About Identifiers
You do configuration procedures on specific items such as card slots, links, or
circuits, each of which has a specific type of identifier. Table 16.4-1 lists the
identifiers.
Getting Started
(400)
16.4-1
<sn>
<CTL>
<GFC>
<EXP>
<Hn>
<Hn-ss>
<A1> <B7>
<CTL>
<GFC>
<EXP>
<H1>
<H1-A> <H1-B>
<sn-l>
<A6-B> <B6-A>
MPA card
<sn-l>
T1, E1, TTC2M, X.21 PRI, X.21 ESI PRI, V.35 PRI,
4WTO, E+M, LGE, LGS, RS-232 DCC, X.21 DCC,
V.35 DCC, RS-422 DCC, 27LC2, DSP, DCP, 64 kb/s
Codirectional and Common Carrier cards
<sn-cc>
<B3-12>
<sn-cc-1>
<A3-3-1> <B5-1-1>
<sn-cc-p>
<A2-1-A> <B3-4-B>
<sn-cc-1>
<sn-cc-2>
<sn-cc-D>
<A5-1-1> <A5-1-2>
<A2-1-D>
Dual T1, Dual T1-2, Dual E1, Dual E1-2 and MPA
<sn-l-cc>
<sn-cc-p>
<A3-11-A> <B3-4-B>
DSP5H, DSP5
<sn-dsp-1>
<sn-dsp-2>
<A1-4-1> <A1-4-2>
<sn-i>
<A1-2> <A3-6>
<sn-i-h>
<A1-2-1> <A1-2-2>
<A1-2-D>
<sn-cc-Bbb>
<A4-3-B2>
SRMs on DCCs
<sn-Mmm>
<B1-M6> <A6-M2>
<sn-cc-Mmm>
<B1-3-M6>
<A6-11-M2>
VCBs on DSPs
<sn-cc-BRr>
<A1-1-BR3>
<sn-cc-Ikk>
<B2-2-I5>
SRS on DSPs
<sn-SRS-dd>
<A3-SRS-4>
<sn-Scc-vv>
<B2-S3-1>
<A3-S6-2>
<sn-Xt>
<A7-X3> <B2-X5>
DS3 identifier
DS1 identifier
DS0s on DS-3 or DS-3 II cards
<DS-3>
<n>
<n-cc>
DS-3
<3>
<5-15>
Link Identifiers
16.4-2
(400)
Getting Started
E3 identifier
E2 identifier
E1 identifier
DS0s on E3 cards
<E3id>
<E3id-E2id>
<E3id-E1id>
<E3id-E1id-cc>
<1>
<2-B>
<1-14>
<2-12-27>
<OW>
<OW>
DS0 on GFC3
<DS0>
<DS0>
<TP>
<TP>
<TT-cc>
<TT-1>
BERT on GFC3
<BT-cc>
<BT-1>
<Hn-ss-pa>
<Hn-ss-AU4>
<Hn-ss-pa>
<Hn-ss-pa-gr>
<Hn-ss-pa-gr>
<Hn-ss-pa-gr-vs>
<Hn-ss-pa-gr-vs>
<Hn-ss-Vvs>
<Hn-ss-Tvs>
<H1-A-1>
<H1-A-AU-4>
<H1-A-1>
<H1-A-1-3>
<H1-A-1-3>
<H1-A-1-3-1>
<H1-A-1-1-1>
<H1-A-V1>
<H1-A-T2>
<Hn-ss-c>
<Hn-c-d>
<H1-A-5>
<H1-A-2>
<Scc>
<Scc>
<Scc>
<Fnn>
<S22>
<S22>
<S22>
<F63>
<Scc-dlci>
<Scc-dici>
<Scc-dici>
<Fnn-dici>
<S22-768>
<S22-768>
<S22-768>
<F63-2127>
<sn-cc-Ixx>
<A1-1-I2>
Getting Started
(400)
16.4-3
16.4-4
(400)
Getting Started
16.4.2
Shelf Identifiers
The identifiers used with switching, locally controlled or peripheral and HSPS are
determined by shelf-select jumpers set during initial installation or intershelf
connections (see Installation, Task 0500 and Task 0600).
Note
In all configurations, if you enter no shelf identifier, the management station
assumes it to be 1 for a switching shelf, or A for a locally controlled, peripheral or
HSPS card.
Getting Started
(400)
16.4-5
HSPS identifiers
HSPS cards (DS-3, DS-3 II or E3 cards) are identified as either card A or B depending
on the slot they are installed in. When installed in an odd-numbered slot (1, 3, 5 or 7),
the card is identified as card A. When installed in an even-numbered slot (2, 4, 6
or 8), the card is identified as card B.
16.4.3
Shelf Numbers
Each peripheral shelf and each HSPS card is also identified by the number of the
switching shelf slot occupied by the Switching card to which the peripheral shelf or
HSPS card is connected. For example, in Figure 16.4-1, the peripheral shelf
connected to the Switching card in switching shelf slot 1 is identified by a 1. The
HSPS2 card connected to the Switching card in switching shelf slot 5 is identified by
a 5, and so on.
This number, called the shelf number, is displayed in the NMTI header and used
when you log onto the switching shelf to configure connections; for example:
CONFIG CONNECT <x-sn-cc> TO_CIRCUIT <x-sn-cc>
where x is the shelf number (1 to 8) of a peripheral shelf or HSPS card
When you log onto a peripheral shelf or HSPS card, the shelf number is not required,
for example:
CONFIG CIRCUIT <sn-cc> NAME <name>
16.4-6
(400)
Getting Started
3645 MainStreet
Switching
card #5
Switching
card #1
Switching
card #6
5 6
3645 MainStreet
This card is
identified as
peripheral shelf
#5.
This card is
identified as
peripheral shelf
#6.
4800
16.4.4
Slot Numbers
The card slots are numbered from left to right on the switching, locally controlled
and peripheral shelves, and HSPSs.
Getting Started
(400)
16.4-7
Switching shelf
As Figure 16.4-2 shows, the use of the slots in the switching shelf is as follows:
Class B
Critical Alarm
Critical Alarm
3645 MainStreet
NEWBRIDGE
3645 MainStreet
Major Alarm
Minor Alarm
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
NEWBRIDGE
Major Alarm
Minor Alarm
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
slots 1 to 8
9 10
slots 1 to 8
9 10
Switching
section
Common
Control
section
Switching
section
Common
Control
section
Class B
23-inch
3645 MainStreet
High Capacity Bandwidth Manager
Critical Alarm
Major Alarm
Minor Alarm
Power Supply
Card
0VR
-BATT
+5
-5
+12
-12
GND
Alarm
Status
Power Supply
Card
0VR
-BATT
+5
-5
+12
-12
GND
Alarm
Status
slots 1 to 8
9 10
Switching
section
Common
Control
section
5393
16.4-8
(400)
Getting Started
Slots 1 through 8, called UCSs, contain any type of interface or application card.
Slot 9 contains the Control card (no configurable parameters).
Slot 10 contains the Expander card in a locally controlled shelf, or a Switching
The type of Expander card or Switching Interface card in slot 10 determines which
UCSs can be configured and which offer double-bandwidth capability (as listed in
Table 16.4-2). For more information, see Technical Overview, chapters 4.7 and 4.10.
Table 16.4-2: Locally Controlled and Peripheral Shelf UCS Access
Card in Slot 10
Accessible UCSs
No card installed
A1-A6
None
Expander 6+2
A1-A8
A7 and A8 (1)
Expander 6+6
None
Expander 8+8
Expander 16+
Notes
1. All UCSs are single bandwidth if the 4602 MainStreet Intelligent NetworkStation or MainStreetXpress
46020 Network Manager is used. UCS 7 and 8 provide double bandwidth if the 4602 or 46020
network manager is not used.
Getting Started
(400)
16.4-9
Figure 16.4-3: Slot Numbers for the Locally Controlled or Peripheral Shelf
Class A
Class B
Critical Alarm
Bandwidth Manager
Bandwidth Manager
PS1
5A
Major Alarm
Minor Alarm
PS2
5A
NEWBRIDGE
NEWBRIDGE
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
slots 1 to 8
9 to 12
slots 1 to 8
9 to 12
Interface
section
Common
control
section
Interface
section
Common
control
section
Class B
23-inch
Bandwidth Manager
Critical Alarm
Major Alarm
Minor Alarm
Power Supply
Card
0VR
- BATT
+5
-5
+ 12
- 12
GND
Alarm
Status
Power Supply
Card
0VR
- BATT
+5
-5
+ 12
- 12
GND
Alarm
Status
slots 1 to 8
9 to 12
Interface
section
Common
control
section
4758
HSPS
As Figure 16.4-4 shows, the use of the slots in an HSPS is as follows:
16.4-10
(400)
Getting Started
Critical Alarm
3645 MainStreet
Major Alarm
Minor Alarm
NEWBRIDGE
PS1
5A
PS2
5A
Alarm
Alarm
Power
Power
1a 1b 2a 2b 3a 3b 4a 4b
Switching
section
Reserved
for future
use
5343
HSPS2
As Figure 16.4-5 shows, slots 1a through 4b in the HSPS2 are reserved for SE3 and
DE3 cards.
Getting Started
(400)
16.4-11
1a
1b
E3 card
interface section
2a 2b 3a 3b
4a
4b
5390
16.4-12
(400)
Getting Started
16.5
Displaying Configuration
Information
This chapter explains how to display information about slots, circuit connections
and configuration.
16.5.1
Getting Started
(400)
16.5-1
3645 MainStreet
#
1
2
3
4
5
6
7
8
CTL
CLK
C117-H1-00
Configured
Toronto:SWA
Installed
SC
SC
Empty
Empty
Empty
Empty
Empty
Empty
Status
SC
SC
Empty
Empty
Empty
Empty
Empty
Empty
Control
Clock
Alarms:1
Name
Ok
Ok
Empty
Empty
Empty
Empty
Empty
Empty
Control
Clock
11-May-1997
8:35a
Options
DOUBLE_BW PS NODE 1
DOUBLE_BW PS NODE 2
Ok
Ok
F2F7-
F3-CONFIG_ALL
F8-CANCEL
F4F9-QUIT
F5F10-
Figure 16.5-2 shows the display for a typical configuration. Table 16.5-1 lists and
describes the fields on this display.
16.5-2
(400)
Getting Started
D117-H1-00
Configured
A1
A5
A3
A4
A5
A6
A7
A8
CTL
GFC
Toronto:P3A
Alarms:1
11-May-1997
8:35a
Installed
Stat
Configured
Installed
Stat
LGS Mu-Law
X.21_DCC 6
E+M Mu-Law
E+M A-Law
LGE Mu-Law
LGE A-Law
E1
DSP
LGS Mu-Law
X.21_DCC 6
E+M Mu-Law
E+M A-Law
E1
E1
DSP
Ok
Ok
Ok
OK
Prob
Prob
OOS
Ok
B1
B2
B3
B4
B5
B6
B7
B8
LGS A-Law
RS-232 DCC
-
X.21 DCC 4
X.21 DCC 6
-
Prob
Prob
Prob
Prob
-
Control
GFC
Control
GFC
Ok
Ok
F1-SHOW_A
F6-SHOW_SLOTS
F2-SHOW_B
F7-
F3-CONFIG_ALL
F8-CANCEL
F4F9-QUIT
F5F10-PROCEED
Getting Started
Indicates
Displays the slot identifier (CTL indicates a Control card, EXP indicates an Expander
card and GFC indicates a General Facilities card).
Configured
The type of card for which the slot has been configured through a node manager.
Installed
The type of the card that has been physically installed in the slot.
Status
(400)
16.5-3
SHOW_A
SHOW_B
SK000005
D117-H1-00
Configured
LGS Mu-Law
X.21_DCC 4
E+M Mu-Law
E+M A-Law
LGE Mu-Law
LGE A-Law
E1
DSP
Installed
Empty
X.21_DCC 4
Empty
T1
Empty
Empty
E1
DSP
Control
SI
GFC
Control
SI
GFC
Toronto:P3A
Alarms:1
11-May-1997
Status
Name
Empty
Ok
Empty
Wrong Card
Empty
Empty
Wrong Module
Ok
8:35a
Options
2-WIRE TYPE-I
2-WIRE TYPE-V
CAS
Ok
Ok
Ok
F1-SHOW_A
F6-SHOW_SLOTS
F2-SHOW_B
F7-
F3-CONFIG_ALL
F8-CANCEL
F4F9-QUIT
F5F10-
16.5-4
(400)
Getting Started
Indicates
Configured
The type of card for which the slot has been configured.
Installed
Status
Name
Options
Notes
1. Not applicable to the Bank-B Memory module.
16.5.2
Getting Started
(400)
16.5-5
Figure 16.5-4 shows a typical card information display. This display also describes
the status of the peripheral shelf connected to the specified Switching card.
Figure 16.5-4: Switching Card Information Display
3645 MainStreet
C117-H1-00
Card Type: SC
Card ID: $2
Card Variant ID:
Slot Status: OK
Peripheral Stat:
Configured Node:
Installed Type:
SI Cables: 1A:
1B:
2A:
2B:
F1F6-
$0
Toronto:SWA
Alarms:1
11-May-1997
8:35a
Peripheral In Service
1
Installed Node: 1
Peripheral Shelf
OK (Active)
Fault
---------------------
F2F7-MORE
F3F8-CANCEL
F4F9-QUIT
F5F10-
<n>
<CTL>
<EXP>
<GFC>
SK000006
16.5-6
(400)
Getting Started
Card
Card
Card
Slot
D117-H1-00
Type
ID
Variant ID
Status
:
:
:
:
Empty
None
None
Empty
Toronto:P3A
Alarms:1
Module Type
Module ID
Module Variant ID
:
:
:
11-May-1997
8:35a
None
None
None
F1F6-
F2F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
<n>
<CTL>
<TIM>
SK000910
Getting Started
(400)
16.5-7
S1117-H1-00
Card Type
: Control
Card ID
: $1
Card Variant ID : $0
Active Bank
: A
Slot Status
: Ok
NarrowBand Module Status
BroadBand Module Status
Memory Module Status
Toronto:A
Alarms:1
Card Revision
Card Serial No.
Card Part No.
11-May-1997
8:35a
: 01
: 123456
: 90-0001-01-00-0000
: Ok
: Ok
: Ok
1-SW_GENERIC
6-RESET_CARD
2-NBAND_MOD
7-
3-BBAND_MOD
8-CANCEL
4-MEMORY_MOD
9-QUIT
50-
DIAG_INFO
For a description of the fields in this display, see Maintenance, chapter 33.3.
NBAND_MOD
BBAND_MOD
MEMORY_MOD
SK000909
Figure 16.5-7 shows a 3600+ MainStreet Control card module information display
for the Narrowband module. The displays for the Broadband and the Bank-B
Memory modules are similar.
16.5-8
(400)
Getting Started
S1117-H1-00
NarrowBand Module
Module Type
Module ID
Module Variant ID
Module Revision
Module Serial No.
Module Part No.
Module Status
:
:
:
:
:
:
:
:
Toronto:A
Alarms:1
11-May-1997
8:35a
8k_X_8k_SW
$30
01
01
123456
90-0002-01-00-0000
Ok
16-
27-
38-CANCEL
49-QUIT
50-
Note
To view circuit connection information for the enhanced locally controlled shelf, see
chapter 31.6.
Figure 16.5-8 shows a typical switching shelf display. If you have configured a
protecting connection, this display also appears.
Getting Started
(400)
16.5-9
C117-H1-00
Name
1-A4-01
1-A4-02
F1-SHOW_CCT
F6-PROTECTING
Toronto:SWA
Alarms:1
Type
Circuit
LGS_EC
LGS_EC
1-A7-13
1-A7-06
F2-DISCONNECT
F7-
F3-TO_CIRCUIT
F8-CANCEL
11-May-1997
Name
8:35a
Type
E1-LGE_EC
E1-LGE_EC
F4F9-QUIT
F5- PROT_BY
F10-
Figure 16.5-9 shows a typical peripheral shelf display. The circuits that are connected
appear with an asterisk. If you have configured a protecting connection, it also
appears.
Figure 16.5-9: Peripheral Shelf Connection Display
3645 MainStreet
Circuit
D117-H1-00
Name
1-A1-01
* = Active connect;
Toronto:P3A
Alarms:1
Type
Circuit
T1_SIG
3-A1-02
11-May-1997
Name
8:35a
Type
T1_SIG
! = Maintenance connect
F1-SHOW_CCT
F6-PROTECTING
16.5-10
F2-DISCONNECT
F7-
F3-TO_CIRCUIT
F8-CANCEL
(400)
F4F9-QUIT
F5- PROT_BY
F10-
Getting Started
Getting Started
(400)
16.5-11
17.1
Circuit Connections
This chapter introduces the types of connections and explains how to do general
circuit operations. It explains how to configure the following types of connections:
17.1.1
simple bidirectional
simple unidirectional
broadcast unidirectional
TS0 NU bit
Understanding Connections
This chapter gives you an overview of the types of connections and describes basic
types that apply to many different situations. Specialized connections are described
in other sections as part of a larger topic, such as CPSS messages, voice compression,
or subrate multiplexing.
You do circuit connections from a locally controlled or switching shelf during a Craft
Interface or NMTI session. With the exception of CPSS connections, if you try to
make a circuit connection from a peripheral shelf, a warning message appears.
Note
The 3645 MainStreet node supports NMTI circuit connection management. Prior to
Release 7.0, circuit connections could only be configured for 3645 MainStreet
systems through a Craft Interface session.
bidirectional connections that provide two identical paths between source and
destination devices: data and signals pass back and forth between the source and
destination devices
unidirectional connections that provide a single path between a source and
destination device: data and signals pass in a single direction only (these
connections are available on PRI cards in 3645 MainStreet peripheral shelves)
Caution
Node Parameters
(400)
17.1-1
Chapter
Bidirectional
Simple
17.1
TS0 NU bit
17.1
18.2
CPSS
17.6
Voice compression
23.3
23.6
23.7
Super-rate
20.15
Unidirectional
17.1.2
Simple
17.1
Broadcast
17.1
Super-rate
20.15
DS-3
Card
E3
Card
E1
Card
Bidirectional connections
17.1.4
17.1.6
Circuit copy
17.1.3
Circuit display
17.1.3
Circuit names
17.1.3
Range copy
17.1.3
TS0 cross-connections
17.1.7
Unidirectional connections
17.1.5
17.1-2
Section
Configuration Procedure
(400)
Node Parameters
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
17.1.3
Node Parameters
(400)
17.1-3
Figure 17.1-2 shows a display for a switching shelf. Table 17.1-3 lists and describes
the symbols on these displays.
Figure 17.1-1: CONFIG CONNECT Display (Peripheral Shelf)
3600 MainStreet
Circuit
2-A1-01
1117-H1-00
Name
Toronto:A
Type
T1_SIG
* = Active connect;
Alarms:1
Circuit
3-A1-02
Name
11-May-1997
8:35a
Type
T1_SIG
Conv
! = Maintenance connect
F2F7-
F3-TO_CIRCUIT
F8-CANCEL
F4F9-QUIT
F5- PROT_BY
F10-
Circuit
1-B8-A-22
C117-H1-00
17.1-4
Type
DE1_Sig
Alarms:1
Circuit
-> *6-A7-B-12
<B *3-B1-4
1-B8-A-23
DE1_Sig
--1-B8-A-24
DE1_NoSig
B> *2-A1-A-1
B> 6-A7-B-13
B> *4-B3-B-7
B> *3-B1-1
<- *4-B3-B-7
1-B8-A-25
DE1_Sig
-> *5-A2-A-11
<- *6-A7-B-12
1-B8-A-26
DE1_Sig
<- *6-A7-B-12
1-B8-A-27
DE1_Sig
*5-A2-A-12
* = Active connect; ! = Maintenance connect
CONFIG CONNECT 1-B8-A-22
F1-ONE_WAY_TO
F6-
Name
Toronto:SWA
F2-BROADCAST
F7-
F3-RMV_BCAST
F8-CANCEL
(400)
Name
11-May-1997
Type
DE1_Sig
64CO_Sig
8:35a
Conv
DE1_NoSig
DE1_NoSig
DE1_NoSig
64CO_NoSig
DE1_NoSig
DE1_Sig
DE1_Sig
DE1_Sig
DE1_Sig
F4-PREV_BCAST
F9-QUIT
F5-NEXT_BCAST
F10-
Node Parameters
Description
blank
>
The circuit listed to the right of the symbol is the destination circuit in a one-way
unidirectional connection.
<
The circuit listed to the right of the symbol is the source circuit in a one-way
unidirectional connection.
B>
The circuit listed to the right of the symbol is a destination circuit in a broadcast
unidirectional connection.
<B
The circuit listed to the right of the symbol is the source circuit in a broadcast
unidirectional connection.
To name circuits
You can assign a name to any circuit in the locally controlled shelf, peripheral shelf,
DS-3 or DS-3 II card, or E3 card, using the NAME softkey. To delete a circuit name
without assigning another one, select NAME and press .
NAME
COPY_TO
<name>
COPY_ADJ
<sn-cc>
COPY_RANGE
<sn-cc>
TO
<sn-cc>
SK000007
where
name is up to 8 alphanumeric characters (no spaces)
the first sn-cc is the source circuit identifier
the second sn-cc is the identifier of the destination circuit or the first circuit of the destination range
the third sn-cc is the last circuit of the destination range
Node Parameters
(400)
17.1-5
Note
Do not use COPY_TO or COPY_ADJ if either circuit is connected.
17.1.4
17.1-6
(400)
Node Parameters
DISCONNECT
TO_CIRCUIT
<sn-cc> or <x-sn-cc>
COMP_CONV
PREFERRED
PROTECTION
NO_CONV
SK000008
where
the first sn-cc or x-sn-cc is the source circuit identifier
the second sn-cc or x-sn-cc is the destination circuit identifier
17.1.5
Node Parameters
(400)
17.1-7
MORE
DISCONNECT
ONE_WAY_TO
<x-sn-cc> or <x-sn-l-cc>
SK000009
where
the first x-sn-cc or x-sn-l-cc is the source circuit identifier
the second x-sn-cc or x-sn-l-cc is the destination circuit identifier
17.1.6
Select the BROADCAST softkey. After the first connection is made, the
ADD_BCAST softkey appears for further connections.
Select DISCONNECT and enter the source circuit identifier. To disconnect one of the
broadcast connections, select RMV_BCAST and enter the destination circuit
identifier.
17.1-8
(400)
Node Parameters
MORE
DISCONNECT
RMV_BCAST
BROADCAST/ADD_BCAST
<x-sn-cc> or <x-sn-l-cc>
SK000010
where
the first x-sn-cc or x-sn-l-cc is the source circuit identifier
the second x-sn-cc or sn-l-cc is the destination circuit identifier
17.1.7
TO_CIRCUIT
<sn-cc> or <x-sn-cc>
DISCONNECT
SK000011
where
sn-TS0 or x-sn-TS0 is the TS0 circuit identifier
sn-cc or x-sn-cc is the destination circuit identifier
Node Parameters
(400)
17.1-9
17.2
17.2.1
17.2.2
Timing sources
The Timing card, SSU or ISSU is driven by a timing source selected from the
programmable timing sources available to the system. Each programmable timing
source can be configured as either external or derived.
If configured as external, the synchronization source is an external device connected
to the backplane or bulkhead BNC or DB-type connectors. Only one external source
may be configured for each node, but a redundant external timing source may be
configured for each 3600+ MainStreet node.
Node Parameters
(400)
17.2-1
Shelf
Number of Possible
Synchronization
Sources
Enhanced locally
controlled shelf
Peripheral shelf
Switching shelf
4
8
17.2-2
(400)
Node Parameters
1117-H1-00
Toronto:A
ANS:DISABLED
Alarms:1
Number
Zone ID:1
1
2
3
4
Source
Recovery
Slot A7
Slot A3
External
Slot B5
Auto
Auto
30 sec
Auto
11-May-1997
Node Class:10
Class
Current Class:1
Threshold
2
1
5
15
8:35a
Status
5
5
5
5
Ready
Current
Ready
Ready
2-MAINT
7-
3-ANS_LINK
8-CANCEL
4-NODE_CLASS
9-QUIT
5-EXT_FREQ
0-
S1117-H1-00
Zone ID:1
Toronto:A
Alarms:1
11-May-1997
Node Class:14
Node Class:14
Threshold
Source
Recovery
Message
External-A
Slot H1
Slot H2
Slot A1-1
Manual
Manual
Manual
Manual
PRS (1)
ST2 (3)
Disabled (2)
--- (2)
5
5
5
5
8:35a
Current Class:5
Status
Current
Ready
Monitoring
Not Ready (AIS)
Node Parameters
2-MAINT
7-MORE
3-ANS_LINK
8-CANCEL
(400)
4-NODE_CLASS
9-QUIT
5-EXTERNAL
0-
17.2-3
Peripheral shelf
For each peripheral shelf, you can build a table of up to four timing sources.
Figure 17.2-3 shows an example for a peripheral shelf.
Figure 17.2-3: Peripheral Shelf Timing Source Display
3645 MainStreet
Number
1
2
3
4
D117-H1-00
Toronto:P3A
Source
Status
Slot A7
Slot A3
External
Slot B5
Ready
Current
Ready
Ready
Alarms:1
11-May-1997
8:35a
Input = 8kHz
CONFIG SYNCH
1-SRC_NUMBER
6-
27-
38-CANCEL
49-QUIT
5-EXT_FREQ
10-
Switching shelf
For the switching shelf, you can build a table of up to eight timing sources selected
from any of the timing sources provided by the peripheral shelves. Figure 17.2-4
shows an example of the table.
17.2-4
(400)
Node Parameters
C117-H1-00
ANS:DISABLED
Number
1
2
3
4
5
6
7
8
Toronto:SWA
Zone ID:1
Source
Recovery
PS3-1,A7
PS2-2,A3
PS4-4,A1
PS6-1,A2
PS3-2,A7
PS2-4,A3
PS4-2,A1
PS6-3,A2
Auto
Auto
Auto
Auto
Auto
Auto
Auto
Auto
Alarms:1
11-May-1997
Node Class:10
Class
5
2
5
5
5
2
5
5
8:35a
Current Class:2
Threshold
5
5
5
5
5
5
5
5
Status
Ready
Current
Ready
Ready
Ready
Ready
Ready
Ready
17.2.3
2-MAINT
7-
3-ANS_LINK
8-CANCEL
4-NODE_CLASS
9-QUIT
5-EXT_FREQ
10-
Synchronization methods
For all 3600 MainStreet series bandwidth manager systems, the programmable
timing source that drives the Timing card, SSU or ISSU can be chosen using one of
two methods: standalone synchronization or ANS.
Standalone
Normally, standalone synchronization is used when a node is used in a single-ended
or point-to-point application. When operating in standalone mode, the node uses
only those timing sources that have been configured at that node.
On all 3600 MainStreet series bandwidth manager systems, preferred standalone
synchronization sources are defined using the class method. For the
3600+ MainStreet system, preferred standalone synchronization sources are defined
using either the class or synchronization status messaging method.
Synchronization status messages are used to determine the current synchronization
source when status message mode is enabled. The timing source offering the best
quality, as indicated by its status message, is selected to be the current source.
Status messages are defined for SONET and SDH interfaces and for external timing
input and output DS1 signals in ESF format. Table 17.2-2 lists the status messages
and their SONET, SDH and DS1 descriptions.
Node Parameters
(400)
17.2-5
Quality Level
SONET Description
SDH Description
DS1 Description
PRS
STU
Synchronized
traceability unknown
Synchronized
traceability unknown
Synchronized
traceability unknown
ST2
Traceable Stratum 2
holdover
Traceable to SDH
synchronization unit (as
defined in ITU-T G.812T)
Traceable Stratum 2
holdover
ST3
Traceable Stratum 3
holdover
Traceable to SDH
element clock (as defined
in ITU-T G.812L)
Traceable Stratum 3
holdover
SIC
Traceable to synchronous
equipment timing source
(as defined in ITU-T
G.81s (1))
ST4
DUS
Traceable Stratum 4
free run
Do not use for
synchronization
17.2-6
(400)
Node Parameters
Status Message
Class
PRS
STU
ST2
11
ST3
14
SIC
ST4
DUS
ANS
ANS is used to give each node access to all timing sources in the network. This lets
all nodes receive timing signals from the same source to ensure that network
synchronization is maintained.
ANS uses CPSS to transport synchronization information between ANS nodes
(CPSS is described in chapter 17.6). ANS works with CPSSv1 or CPSSv2, but is not
tied to the topology of the CPSS network. Changes in the CPSS network are
transparent to the ANS network. When the CPSS network heals itself after the failure
of a CPSS link, there is no change in synchronization sources unless the failure
affected the ANS topology.
With ANS you can configure any valid link as an ANS link regardless of the link
CPSS configuration. A valid ANS link may carry no CPSS channels, one CPSS
channel, or more than one CPSS channel.
In a system running CPSSv2, ANS takes advantage of the improved CPSS packet
transmission services that operate at the network layer. These services include better
error detection, larger packets (for higher throughput) and a new datagram service
(for better performance).
ANS nodes can be organized into independently synchronized groups, called zones,
explicitly identified by a zone identifier.
Note
The communication of ANS messages from one zone to another is not supported.
Node Parameters
(400)
17.2-7
ANS links
ANS links are configured between ANS nodes that are one hop away from each
other (a hop is a point-to-point link, free of intermediate nodes, between two pieces
of network equipment).
The node at the far end of an ANS link is called an adjacent node. Each ANS link is
configured with the node number of the adjacent node. Each adjacent node
represents a potential source of synchronization.
Note
If the far end of an ANS link terminates on a switching shelf controlled system, the
adjacent node is always taken to be the switching shelf, even though the link
terminates on a peripheral shelf.
The path used to communicate with an adjacent node is determined by the CPSS
network and does not actually have to be on an ANS link. However, ANS protocol
operation is always based on the ANS network topology, so that hop counts are ANS
links and not CPSS links.
ANS nodes exchange ANS Update Messages to learn about the existence of all
potential timing sources in the network and automatically generate a map of these
timing sources. Whenever a configuration change occurs (for example, if a new node
is brought online or a timing source is reconfigured), the map is updated.
The best source of synchronization in the networkthe one with the lowest class
numberis identified as the ANS master.
Every ANS node derives synchronization from the ANS master through the
least-hop path to the ANS master. The adjacent node that constitutes the first hop
towards the ANS master is called the ANS source of the node. Every adjacent node
is not necessarily an ANS source. An adjacent node is only an ANS source when it
actively provides synchronization to a given node.
Figure 17.2-5 shows an example ANS network with Node C as a stand-alone feeder
node and Node Y as the current ANS master. Node X has two ANS links: link 1-1 to
Node A and link 2-1 to Node B. Link 3-1 is a non-ANS link to feeder Node C, which
uses stand-alone synchronization.
Nodes A and B are adjacent nodes to Node X because they are each at the far end of
a link one hop away. The path to the ANS master through Node A offers a four-hop
path to Node Y and the path through Node B offers a two-hop path. Because Node
B offers the fewer number of hops to the ANS master, Node B is the current ANS
source to Node X and it actively provides synchronization from Node Y to Node X.
Node A is only a potential source of synchronization.
17.2-8
(400)
Node Parameters
1-1
C
3-1
2-1
X
Stand-alone
feeder node
ANS master
Adjacent node
and ANS source
5446
If the ANS link between Node X and Node B is configured only from Node X
(Node X identifies Node B as its adjacent node but Node B does not identify
Node X as its adjacent node), the link is unidirectional from Node B to Node X.
Synchronization is always incoming to Node X from Node B.
If the ANS link between Node X and Node B is configured only from Node B
(Node B identifies Node X as its adjacent node), the link is unidirectional from
Node X to Node B. Synchronization is always outgoing to Node B from Node X.
If the ANS link between Node X and Node B is configured from both Node B and
Node X (both nodes identify the other node as adjacent), the link is bidirectional.
Synchronization may be incoming from Node B or it may be outgoing to Node B
from Node X.
Whether an ANS link is unidirectional or bidirectional affects how the ANS network
topology stabilizes. For example, in Figure 17.2-5, if ANS link 2-1 is configured as
unidirectional from Node X to Node B, Node X cannot use Node B as its ANS
source. In this case, the ANS master cannot be reached from Node X through Node B
and Node X must use Node A as its ANS source.
More than one ANS master may be active at the same time. For example, if the
lowest-class number is shared by a number of sources, an ANS node selects the ANS
master that is the fewest number of hops away from it.
Node Parameters
(400)
17.2-9
If an ANS node can reach an ANS master by more than one equal cost path, the node
chooses the path offered by the adjacent node with the lowest CPSS node address.
If the ANS network changes, the ANS network topology adapts to the change and
restabilizes. For example, if a better timing source becomes available or the existing
ANS master fails, a new ANS master is selected and, if necessary, ANS nodes choose
new ANS sources to reach the new ANS master.
ANS zones
Within a network it may be desirable or necessary to define zones that have
independent timing hierarchies. For example, a network that links North America to
Europe would require a North American zone and a European zone to
accommodate the differences between the two timing reference standards.
Figure 17.2-6 shows a network divided into two zones, 1 and 2. Zone 1 could be the
North American zone and Zone 2 the European zone.
Figure 17.2-6: ANS Zones
Node
I
Node
A
Node
C
Intra-zone
links
Node
H
Node
E
Intra-zone
links
Node
D
Inter-zone
link
Node
B
Node
F
Intra-zone
links
Node
J
Zone 2
Node
G
Zone 1
4447
You create zones by assigning zone identifiers to ANS nodes. All ANS nodes with
the same zone identifier belong to the same zone. ANS messages are exchanged only
on intra-zone links between nodes with like zone identifiers. ANS links cannot be
configured on inter-zone links between nodes in different zones.
Note
With CPSSv2, all nodes in a zone must be contained in a single CPSSv2 domain; an
ANS zone cannot span more than one CPSSv2 domain.
17.2-10
(400)
Node Parameters
Note
The node at the far end of an ANS link (an adjacent node) cannot be a stand-alone
synchronized node. This means a feeder node such as the 3612, 3620, 3624, 3630 and
8230 MainStreet nodes or FRS cannot be an adjacent node. A stand-alone
synchronized node can be connected to an ANS node, but not through an ANS link
(see Node C, Figure 17.2-5).
17.2.4
Table 17.2-4 lists the ANS and timing source configuration parameters. Each
parameter has a list of options; default options are marked by an asterisk.
Note
Before configuring ANS, make sure that you have configured the CPSS node
parameters, including the CPSS node number (see chapter 17.6).
Control
Card
DS-3 and
E3 Card
Parameter
Options
ANS
ANS enable/disable
enabled
disabled*
enabled
disabled
ANS zones
1 to 255
0 to 10 (* = 5)
1 to 255 (* = 30)
1 to 5 (* = 1)
1 to 255 (* = 15)
Node Parameters
(400)
17.2-11
3600+
Control
Card
Control
Card
DS-3 and
E3 Card
Parameter
Options
external
derived
external
derived
undefined
enabled
disabled*
selected
deselected*
auto
30 s
1 min
10 min
30 min
manual
0 to 30 (* = 5)
unlimited
8 kHz
2 MHz
1.544 MHz
composite clock
8 kHz
2 MHz
1.544 MHz
no clock
Table 17.2-5 lists the locations of the ANS and timing source configuration
procedures.
Table 17.2-5: Timing and Synchronization Configuration Procedures
Configuration Procedure
17.2-12
Section
17.2.6
17.2.7
17.2.7
(400)
Node Parameters
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
17.2.5
To configure the zone identifier, see the procedure To enable and disable ANS on
node.
Node Parameters
(400)
17.2-13
Note
When you change the method of synchronization for a node, its timing sources
remain as configured. They are not reset to default values.
ENABLE/DISABLE*
ZONE_ID_#
<number>
SK000012
17.2.6
display all the links currently enabled for ANS on an ANS node
enable or disable ANS on the link and identify the adjacent node
configure the link failure threshold and recovery time
configure the Timing card or SSU failure threshold and recovery time
Note
17.2-14
(400)
Node Parameters
Figure 17.2-7 shows a sample ANS link display. If there are more ANS links
configured than fit on one screen, use the PREV_PAGE and NEXT_PAGE softkeys
to scroll through the list.
Figure 17.2-7: ANS Links Display
3645 MainStreet
ANS
Link
1-A1-A
1-A1-B
1-B2
1-A2
1-A3
1-A8-A
1-A8-B
2-A1-A
3-A1-B
4-B2
5-A2
6-A1-A
7-A1-B
8-B2
CARD
Type
DUAL_T1
DUAL_T1
DUAL_T1
T1
V35_PRI
DUAL_T1
DUAL_T1
DUAL_T1
DUAL_T1
T1
DUAL_T1
DUAL_T1
DUAL_T1
DUAL_T1
D117-H1-00
Toronto:P3A
CPSS
Far End Node
2
2
3
5
32
34
31
20
59
21
24
25
62
87
Alarms:1
11-May-1997
Link Failure
Threshold
Time (min)
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
5
30
8:35a
SSU Failure
Threshold Time (min)
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
1
60
2- NEXT_PAGE
7-
38-CANCEL
49-QUIT
50-
Single and Dual T1 and DS-3 or DS-3 II links (on a DS1 basis)
Single and Dual E1 and E3 links (on an E1 basis)
V.35 PRI (DTE)
X.21 PRI (DTE)
MPA card link (DTE)
OC-3 and STM-1 card links (the card must be installed in the active HSA subslot)
Node Parameters
(400)
17.2-15
Note
ANS cannot be configured on an MPA card link configured as DCE on an X.21 PRI
or a V.35 PRI link.
To enable ANS on a link, you select ANS_LINK and enter a link identifier. The
system displays FAR_END on the command line and prompts for the CPSS address
of the adjacent node at the far end of the link. To disable a link, you enter the link
identifier and select DISABLE.
Note
You cannot use the default node number (1022) or the CPSS address of a peripheral
shelf to identify an adjacent node. If the adjacent node is a peripheral shelf, enter the
CPSS address of its switching shelf.
To enable and disable ANS on a link, see the procedure To configure ANS links.
17.2-16
(400)
Node Parameters
To configure the SSU failure recovery time, see the procedure To configure ANS
links.
Node Parameters
(400)
17.2-17
<far-end_node>
DISABLE/ENABLE
LINK_RECOV
FAIL_THRES
<threshold>
UNLIMITED
SSU_RECOV
FAIL_TIMED
<time>
INFINITY
SK000013
where
link_id is the slot or link identifier
far-end_node is the CPSS address (1 to 999) of the adjacent node at the far end of this link
threshold is the number of times (0 to 10) the link can fail each hour (5*), or the number of times the SSU
can fail (1*)
time is the number of minutes (1 to 255) the out-of-service link must show a failure rate less than the failure
threshold before the link is returned to service (30*), or the number of minutes (1 to 255) the link remains
out-of-service after exceeding the SSU failure threshold (15*)
Note
The UNLIMITED option applies only to the LINK_RECOV parameter.
17.2.7
external
derived
17.2-18
(400)
Node Parameters
For a peripheral shelf, switching shelf, or a locally controlled shelf, a 2.048 MHz
For 3600 MainStreet series bandwidth managers, you can configure only one source
as external (EXTERNAL) for each node. For 3600+ MainStreet Bandwidth Managers,
you can configure two sources as external (EXT_PORT_A and EXT_PORT_B) for
each node. External sources may be an input to the node or an output from the node.
For more information about external timing inputs and outputs, see Installation, Task
1500: Connecting External Timing Sources and Receivers.
Internal source
In addition to the programmable timing sources, the node has an internal crystal
oscillator that supplies a 2.048 MHz 25 ppm timing signal. Typically, the internal
source class is assigned the highest class number so the node can synchronize to it
only under two conditions:
Node Parameters
(400)
17.2-19
Note
Using the timing source as a reference, the SSU creates a 2.048 MHz clock that
conforms to ITU-T recommendation G.703. This clock is available at J14 on the
equipment backplane.
Figure 17.2-8 shows a sample display. Table 17.2-6 lists the fields on this display.
Figure 17.2-8: Timing Source Display
3600 MainStreet
1117-H1-00
ANS:ENABLED
Number
1
2
3
4
ANS
Toronto:A
Zone ID:1
Source
Slot A7
Slot A3
External
Slot B5
N/A
Recovery
Auto
Auto
30 sec
Auto
N/A
Alarms:1
11-May-1997
Node Class:10
Class
2
5
1
15
N/A
8:35a
Threshold
5
5
5
5
N/A
Current Class:1
Status
Ready
Ready
Current
Ready
Ready
CONFIG SYNCH
1-SRC_NUMBER
6-ANS_NODE
17.2-20
2-MAINT
7-
3-ANS_LINK
8-CANCEL
(400)
4-NODE_CLASS
9-QUIT
5-EXT_FREQ
0-
Node Parameters
Description
Number
Source
Recovery
The method used to resynchronize to the source when it has recovered from a failed
state.
Class
or
Message
Threshold
The maximum number of failures each hour allowed for this source (or alternate source
on the 3600+ MainStreet Bandwidth Manager) when it is the current source of
synchronization.
Status
Manual Recovery:
Not Ready: The source is not available for system timing. If the source is a primary rate
link, there is a primary rate alarm. If the source is a data circuit, the circuit is out of
synchronization.
Ready: The source is available for system timing.
Acquiring: The Timing card, SSU or ISSU is currently trying to synchronize to the source.
Current: The source is providing system timing.
Auto Rec: The source has failed as the current source of synchronization, but will be
available to the system as soon as it has recovered.
Time Rec: The source has failed as the current source of synchronization, but the
system is checking at timed intervals to see if it has recovered.
Cannot Lock: The system is presently unable to take timing from the current source. It
tries to take timing from the source again soon after this state has been entered.
Displays the alternate source as follows:
Validating: The Timing card is currently trying to synchronize to the alternate source.
Monitoring: The alternate source is providing system timing.
Node Parameters
(400)
17.2-21
For 3600 MainStreet series bandwidth managers, when you define a DERIVED
source, you must specify the slot and link identifier or the peripheral shelf and
source number where it originates. For 3600+ MainStreet Bandwidth Managers,
when you define an HSA card as a DERIVED source, the following rules apply:
If the HSA slot is configured for simplex traffic protection, the derived source
You can also specify a previously defined source as UNDEFINED before redefining
it.
For a timing source to become the current (active) source, it must be enabled and
selected. The system automatically selects the source with the highest quality; this is
indicated by the lowest class number or, if status messaging is selected, it is
indicated by the received status message.
17.2-22
(400)
Node Parameters
The SELECT and DESELECT softkeys are used for maintenance operations. When
you SELECT a source, you force the system to use this source as its current timing
source. This source remains the current source of synchronization until it fails or you
DESELECT it, even if there is another source with a higher-quality value. The status
of the source changes from Ready to Current (see Table 17.2-6). When you
DESELECT a source, normal operation begins again. The source status changes from
Current to Ready (see Table 17.2-6), and the system automatically selects the Ready
source with the highest quality as the current source.
You can assign a class number to each programmable timing source (CLASS) and to
the default internal timing source of the node (NODE_CLASS) to determine source
selection. To increase the preference for a source, assign it a low class number; to
decrease the preference for a source, assign it a high number.
The default node class number is 15 in a locally controlled system and 14 in a
enhanced locally controlled or switching shelf controlled system. A node class
number of 15 or 14 indicates a node that will not normally supply network timing.
The network looks only at the class number when determining the source
hierarchyit makes no distinction between node class numbers and source class
numbers.
Note
The system never uses a source configured with a class number higher than the node
class.
To configure the timing source parameters, see the applicable system procedure:
Node Parameters
(400)
17.2-23
Quality-related failures are caused by exceptional jitter, phase hits and frequency
deviations, causing the SSU to lose synchronization with the timing source. With
quality-related failures, the link is still active and can carry data. You can configure
a source failure threshold to disable a synchronization source when excessive
quality-related failures occur.
Link-related failures are caused by loss of clock signal, loss of frame or excessive bit
errors, causing the SSU to lose synchronization with the timing source. With
link-related failures, the link is down and does not carry data. You can configure a
source failure recovery method for synchronization sources that are disabled due to
link-related failures.
Source failure threshold
The source failure threshold is the number of times in an hour a timing source is
allowed to fail as the current synchronization source. If the source failures exceed the
threshold, the source is automatically disabled until it is manually re-enabled.
Source failure threshold is in the range of 0 to 30 failures each hour or UNLIMITED.
When you select UNLIMITED, the source is never declared disabled, regardless of
the number of failures each hour.
To configure the source failure threshold parameters, see the applicable system
procedure:
17.2-24
becomes available to the network (enters the ready state, see Table 17.2-4) as soon
as it recovers. The network tries to synchronize to the recovered source if it has a
lower class number than the current source.
30_SEC, 1_MIN, 10_MIN or 30_MIN for a timed recovery: If timed recovery is
selected, the system checks after the specified time interval up to four times to see
if the source has recovered. If the source has recovered, the source becomes
available to the network (enters the ready state) and will become the current
source if its class number is lower than that of the current source. If the source has
not recovered by the end of the fourth check, the system places the source in the
disabled state.
MANUAL for manual recovery: If manual recovery is selected, the system places
the failed source in the disabled state. The source is not used as a source of
synchronization until it is manually enabled.
(400)
Node Parameters
To configure the source failure recovery method parameters, see the applicable
system procedure:
8_kHz if the external timing source has a frequency of 8 kHz (locally controlled,
To configure external timing input parameters, see the applicable system procedure:
Node Parameters
Then, using the OPTION softkey, you can select 8_KHZ or 2048_KHZ if the
external timing source has a frequency of 8 kHz or 2.048 kHz, respectively.
DS1 if the external timing source is connected to the bulkhead 120 W connector.
Then, using the OPTION softkey, you can select D4_FRAME or ESF_FRAME if
the input signal is in D4 or ESF framing format, respectively.
COMP_CLOCK if the external timing source is connected to the bulkhead 120 W
connector and the external timing source has a frequency of 64 kHz. Then, using
the OPTION softkey, you can select FREQ_LOCK to specify that the timing
source signal is not a DDS composite clock signal or PHASE_LOCK if the signal
is a DDS composite clock signal.
(400)
17.2-25
Using the OPTION softkey, you can enable or disable a bridged mode to specify that
the signal of any external input timing source is to electrically terminate on the
active Timing card (BRIDGE_OFF) or that neither the active nor inactive Timing
card is to electrically terminate the input timing signal (BRIDGE_ON).
To configure external timing input parameters, see the procedure To configure an
external input timing source for the enhanced locally controlled shelf.
External timing output for 3600 MainStreet series bandwidth managers
Using the EXT_FREQ and OUTPUT softkeys, you can configure the frequency of
one external timing output for each switching shelf as:
Then, you can select 8_KHZ or 2048_KHZ to specify the output signal frequency.
DS1_FRAME if the timing receiver is connected to the bulkhead 120 W connector.
Then, you can select D4_FRAME or ESF_FRAME to specify the framing format
of the output DS1 signal.
PORT_A or PORT_B (or both) to specify to which port the external timing
receiver is connected. Then, you can select SYSTEM or HSA_SLOT to specify that
the source of the timing signal is the Timing card Stratum 3 clock or an OC-3 or
STM-1 card installed in an HSA slot. If HSA_SLOT is configured, the following
rules apply:
If the HSA slot is configured for simplex traffic protection, the derived
source must be configured at the HSA slot or HSA subslot A level. If subslot
B is specified, the message That slot cannot be a source of system timing.
is displayed.
If the HSA slot is configured for 1+1 traffic protection, the derived source
must be configured at the HSA slot level. If subslot A or B is specified, the
message That slot is configured for 1+1 protection. Enter an HSA slot. is
displayed.
If the HSA slot is configured for ring mode traffic protection, the derived
source must be configured at the HSA subslot level. If the HSA slot is
specified, the message That slot is configured for ring mode. Enter an HSA
subslot. is displayed.
17.2-26
(400)
Node Parameters
COMP_CLOCK must be configured before the external timing source becomes the
current synchronization source for a locally controlled or peripheral shelf. If you try
to configure COMP_CLOCK to enable the phase lock operation after the external
timing source has been locked, the warning message External source has already
been locked by the system appears.
Figure 17.2-9 shows a sample display of a 3600 MainStreet node configured for the
DDS composite clock (and phase lock operation).
Figure 17.2-9: DDS Composite Clock Display
3600 MainStreet
1117-H1-00
ANS:DISABLED
Number
1
2
3
4
Toronto:A
Zone ID: 1
Source
Ext-CC
Slot A2
Undefined
Undefined
Alarms:1
Node Class:15
11-May-1997
8:35a
Current Class:1
Recovery
Class
Threshold
Manual
Manual
Manual
Manual
1
2
15
15
5
5
5
5
Status
Current
Disabled
Disabled
Disabled
1-2_MHZ
6-
Node Parameters
27-
3-8_kHZ
8-CANCEL
(400)
49-QUIT
50-
17.2-27
NODE_CLASS
EXT_FREQ
<class>
INPUT
2_MHZ
8_kHZ
SRC_NUMBER
COMP_CLOCK
<source>
SELECT/
DESELECT*
CLASS
RECOVERY
<class>
AUTO 30_SEC
1_MIN
THRESHOLD
SOURCE
ENABLE/
DISABLE*
<failures> UNLIMITED
10_MIN
30_MIN
MANUAL
EXTERNAL
DERIVED UNDEFINED
<sn> or <sn-l>
SK000014
where
class is 1 to 15
source is 1 to 4
failures is the number of failures (0 to 30) each hour (5*)
sn or sn-l is the slot or slot and link identifier where the derived source of timing originates
17.2-28
(400)
Node Parameters
NODE_CLASS
<class>
INPUT
8_kHZ
SELECT/
DESELECT*
2_MHZ
CLASS
<class>
AUTO 30_SEC
SRC_NUMBER
EXT_FREQ
OUTPUT
1.5_MHZ
RECOVERY
NO_CLOCK
<source>
SOURCE
THRESHOLD
ENABLE/
DISABLE*
<failures> UNLIMITED
MANUAL
EXTERNAL
DERIVED
UNDEFINED
<p_shelf>
<s_number>
SK000015
where
class is 1 to 14 for a switching shelf
source is 1 to 8 for a switching shelf
failures is the number of failures (0 to 30) each hour (5*)
p_shelf is the peripheral shelf where the derived source of timing originates
s_number is the source number of the derived source
Note
The NO_CLOCK option applies only to OUTPUT.
Node Parameters
(400)
17.2-29
2_MHZ
EXT_FREQ
SRC_NUMBER
INPUT
<source>
8_kHZ
COMP_CLOCK
EXTERNAL
SOURCE
DERIVED
UNDEFINED
<sn> or <sn-l>
SK000016
where
source is 1 to 4 for a peripheral shelf
sn or sn-l is the slot or slot and link identifier where the derived source of timing originates
17.2-30
(400)
Node Parameters
MORE
SELECT/
DESELECT*
CLASS
NODE_CLASS
SRC_NUMBER
<class>
<source>
<class>
STATUS_MSG
THRESHOLD
RECOVERY
SOURCE
ENABLE/
DISABLE*
DERIVED
UNDEFINED
<failures> UNLIMITED
RX_ENABLE/
RX_DISABLE
AUTO
EXT_PORT_A
30_SEC
1_MIN
10_MIN
EXT_PORT_B
30_MIN
MANUAL
where
class is 1 to 14
source is 1 to 4
failures is the number of failures (0 to 30) each hour (5*)
sn or sn-l is the UCS slot or slot and link identifier where the derived source of timing originates
Hn or Hn-ss is the HSA slot or HSA slot and subslot identifier
Node Parameters
(400)
17.2-31
To configure an external input timing source for the enhanced locally controlled
shelf
CONFIG SYNCH EXTERNAL INPUT
COMP_CLOCK
FREQ_LOCK
DS1
PHASE_LOCK
NRZ
D4_FRAME
OPTIONS
ESF_FRAME
8_KHZ
2048_KHZ
BRIDGE _ON/
BRIDGE_OFF
SK000833
To configure timing output for an external timing receiver for the enhanced
locally controlled shelf
CONFIG SYNCH EXTERNAL OUTPUT
PORT_A
SYSTEM
PORT_B
HSA_SLOT
DS1_FRAME
D4_FRAME
NRZ_FREQ
ESF_FRAME
8_KHZ
2048_KHZ
<Hn> or <Hn-ss>
SK000834
where Hn or Hn-ss is the HSA slot or HSA slot and subslot identifier
17.2.8
17.2-32
(400)
Node Parameters
QUAL_LEVEL
PRS
STU
ST2
ST3 DISABLED
MODE
CLASS
TRANS_TABL
ST2
ST3
SK000831
17.2.9
Node Parameters
(400)
17.2-33
SYSTEM
EXT_PORT_A
EXT_PORT_B
SLOT
<Hn> or <Hn-ss>
REMOVE_MSG
PRS
INJECT_MSG
STU
ST3
SIC
ST4
MORE
DUS
SK000832
where Hn or Hn-ss is the HSA slot or HSA slot and subslot identifier
17.2-34
(400)
Node Parameters
17.3
17.3.1
Node Parameters
(400)
17.3-1
Note
For SP1 only, RTS is connected to CTS and DTR is connected to DSR by the
backplane.
In dual-shelf, control-redundant systems, the backplane serial ports are inactive in
the shelf with the inactive Control card. In single-shelf, control-redundant systems,
these ports are inactive when the jumper behind the faceplate on the Control card is
installed.
17.3-2
(400)
Node Parameters
W4
W4
OR
SP1
SP1
faceplate bulkhead
on
on
Bank-B
memory
module
10043
For Control card faceplate serial port pinouts, see section 16.2.3.
3600, 3645, 3664 and 36120 MainStreet Control cards serial ports
The serial port on the Control card faceplate provides access to SP1 of any shelf type.
Only one of the two serial ports of the shelf is active at a time, depending on the shelf
configuration (see Table 17.3-1). This allows a node management session to be
initiated with the inactive Control card.
Note
For a dual-shelf, control-redundant system, connect the node management terminal
to backplane or bulkhead serial ports on both shelves using a Y cable. This ensures
a connection to the active Control card regardless of which shelf is the active shelf.
In a single-shelf, control-redundant Class B shelf, remove the jumper behind the
faceplate on the Control card to enable the faceplate port for a node management
session with the inactive card. (This action disables the backplane port.)
Node Parameters
(400)
17.3-3
Backplane or
Bulkhead Serial
Ports
Control Card
Faceplate Serial
Port
Class A
Class B
Class A
Class B
(1)
(1)
Inactive
Inactive
Active
Active
Active
Active
Inactive
Inactive
Active
Active
Inactive
Inactive
Inactive
Inactive
Active
Active
Notes
1. In a dual-shelf, non-control-redundant system, the Control card uses the backplane or bulkhead SP1
connector of the shelf in which it is installed. The backplane or bulkhead SP1 connector of the shelf
without a Control card is not used.
CPCs
CPCs have two serial ports on their faceplates that provide VT100 access. Both ports
are configured for DCE.
Ethernet port
A Dsub-15 connector located on the 3600+ MainStreet Bandwidth Manager
bulkhead provides an AUI standard, IEEE 802.3 Ethernet port. This port provides a
means to directly attach a network manager to the shelf and only CPSS data is
supported. The active Control card always controls the Ethernet port.
Note
An external MAU is required for the Ethernet port to connect to 10BaseT, 10Base2 or
10Base5 lines.
17.3.2
17.3-4
(400)
Node Parameters
Table 17.3-2 lists the serial port configuration parameters. Each parameter has a list
of options with any default option marked with an asterisk. The Control card
referenced in the table applies to all 3600 MainStreet series bandwidth managers.
Any variance in the options are highlighted in the table notes.
Note
Configuring CPSS cost is described in chapter 17.6 (see Table 17.6-1 for the CPSS
configuration parameters).
CPC
DS-3 II
and E3
Cards
FRS,
FRE and
PE
Cards
Parameter
Options
Device type
VT100
printer
CPSS
CPSS modem
call logger
Baud rate
300
600
1200
2400
4800
9600
19 200
38 400 (1)
auto baud (1)
Flow control
software
hardware
none*
CPSS cost
normal*
bias against
bias toward
Notes
1. These options are only available for the 3600+ MainStreet Control card.
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
Node Parameters
(400)
17.3-5
Device type
Depending on the type of device connected to the port, the backplane or bulkhead
serial ports can be configured for a VT100-compatible terminal (or a personal
computer running terminal emulator software), a printer, a call logger or a computer
running Craft Interface or 4601, 4602 or 46020 network management software
connected directly or through a modem.
The DS-3 II, E3, DCP, and FRS, FRE and PE card ports can be connected to a VT100
(or emulator) or a computer running network management software. The CPC ports
can be connected only to a VT100 or emulator.
VT100-compatible terminal
A VT100-compatible ASCII terminal or VT100 terminal emulator is used for node
management sessions. It can be connected to the serial ports directly or indirectly
using auto-answer, Hayes-compatible modems. The device type is VT100.
Printer
A printer can be connected to a serial port to print alarms. The device type is Printer.
For details on printing alarms, see Maintenance, section 35.2.6.
17.3-6
(400)
Node Parameters
Personal computer
A personal computer can be connected to a serial port if it is running terminal
emulation software (for installation), Craft Interface software, communications
software or network management software.
From the shelf or card whose serial port you are configuring, you can select the port
and configure the device type as:
Node Parameters
management software
CPSS_MODEM for a computer connected through a modem (default for SP2)
(400)
17.3-7
Baud rate
You can configure the baud rate to match that of the device connected to the serial
port as:
300
600
1200
2400
4800
9600
19200
38400 (3600+ MainStreet only)
AUTO_BAUD (3600+ MainStreet only)
For the 3600+ MainStreet Control card, the automatic baud rate matching option is
the default baud rate for SP1. The default baud rate for SP2 is 9600 b/s. The
maximum baud rate for the 3600+ MainStreet Control card is 38 400 b/s.
The default baud rate of the serial ports on all other 3600 MainStreet series
bandwidth managers cards is 9600 b/s, except for SP2 on the Control card which has
a default baud rate of 1200 b/s. The maximum serial port baud rate is 9600 b/s,
except for the DCP, FRS, FRE and PE cards, which have a maximum serial port baud
rate of 19 200 b/s.
A change to the baud rate takes effect when you execute the instruction (PROCEED)
if the port type is VT100 or PRINTER. You must change the baud rate of the terminal,
computer or printer to match the new setting.
With auto baud, it takes approximately five seconds for the system to automatically
match the speed of the serial port to the speed of the connected device. To function
properly, the attached equipment must send characters to the enhanced locally
controlled shelf. The Control card is unable to send any characters over the serial
port while it is performing the auto baud function. If the attached device performs
auto baud and is able to send characters to the shelf, the baud rate that the two settle
on depends on the attached device. The first speed presented to the serial port that
the 3600+ MainStreet Control card can match is locked.
On a serial port that is configured as VT100 or CPSS with auto baud, the baud rate
is renegotiated whenever the Control card starts-up or whenever an NMTI or CPSS
session on that serial ports ends. The 3600+ MainStreet Control card can begin an
NMTI or CPSS session only after the serial port speed locks onto the baud rate of the
attached device.
17.3-8
(400)
Node Parameters
port cannot use the auto baud feature to set-up the baud rate of that serial port, a
fixed baud rate must be configured.
A serial port connected to a modem that does not send characters to the Control
card cannot use auto baud, a fixed baud rate must be configured.
Note
CPSS link failure can occur if a modem manages to connect to the RS-232 backplane
serial ports and negotiate a high-speed connection. It may be necessary to disable the
ARQ of the modem or lock the modem RS-232 serial port speed to a Newbridge
supported baud rate.
Flow control
You can set bidirectional flow control for both serial ports as:
Node Parameters
(400)
17.3-9
SER_PORT_2
SER_PORT_1
PORT_TYPE
300
FLOW_CTRL
BAUD_RATE
600
1200
CPSS_
MODEM
2400
4800
XON/XOFF
9600 19200
DTR
38400
NORMAL*
CPSS_COST
NONE*
AUTO_BAUD
BIAS_AGNST BIAS_TOWRD
SK000017
Note
The AUTO_BAUD feature and the baud rate 38 400 b/s are only available for the
3600+ MainStreet Control card.
17.3-10
(400)
Node Parameters
SER_PORT_1
PORT_TYPE
VT100*
CPSS
SER_PORT_2
CPSS_COST
BAUD_RATE
<baud rate>
NORMAL*
BIAS_AGAINST
BIAS_TOWRD
SK000018
where baud_rate is 300, 600, 1200, 2400, 4800, 9600 or 19200 (*)
SER_PORT_1
PORT_TYPE
VT100*
CPSS
FBCPSS1
BAUD_RATE
FBCPSS2
CPSS_COST
<baud rate>
NORMAL*
BIAS_AGAINST
BIAS_TOWRD
SK000019
where baud_rate is 300, 600, 1200, 2400, 4800, 9600 or 19200 (*). Baud rate is not available for FBCPSS1 and
FBCPSS2.
Note
This configuration applies to Release 2 FRE cards (part number 90-1673-02) only. The
FBCPSS1 and FBCPSS2 softkeys do not appear for Release 1 FRE cards (part number
90-1673-01).
Node Parameters
(400)
17.3-11
SER_PORT_1
SER_PORT_2
BAUD_RATE
<baud_rate>
SK000020
PORT_TYPE
300
FLOW_CTRL
BAUD_RATE
600
1200
XON/XOFF
CPSS_
MODEM
2400
CPSS_COST
NONE*
4800 9600*
NORMAL*
BIAS_AGNST BIAS_TOWRD
SK000021
17.3.3
17.3-12
(400)
Node Parameters
The subnet mask is a hexadecimal code used to parse an IP address into subnet ID
and host ID. You can configure it only if the network is partitioned into
subnetworks. When you configure the subnet mask, the system knows it is in a
network divided into subnets. The subnet mask is used during forwarding decisions
to determine the subnet ID of the outgoing IP frames.
The port can be connected to up to two remote IP addresses. The host remote
addresses are set using the NMTI.
Note
Disabling the Ethernet port forces CPSS paths to the two remote host addresses to
go down.
Figure 17.3-2 shows the HOUSE display for the 3600+ MainStreet Bandwidth
Manager.
Figure 17.3-2: 3600+ MainStreet Bandwidth Manager HOUSE Display
3600+ MainStreet
S1117-H1-00
Toronto:A
Port
Baud Rate
Port Type
1
2
9600
9600
VT100
VT100
Current Port
Session Time
Domain Number
Node Number
Router Version
NOC Number
Shared CPSS Cost
Level Zero Access
:
:
:
:
:
:
:
:
Alarms:1
Flow Control
8:35a
CPSS Cost
XON/XOFF
NONE
11-May-1997
N/A
N/A
Ethernet Port :
Local IP Addr :
Subnet Mask
:
Default Router:
Host 1 IP Addr:
Host 2 IP Addr:
MAC Address
Disabled
Unassigned
Unassigned
Unassigned
Unassigned
Unassigned
: 00.00.00.00.02.00
16-
Node Parameters
27-
38-CANCEL
(400)
49-QUIT
50-
17.3-13
Description
Current Port
Default Router
Domain Number
The CPSS domain number is the number assigned to the active Control
card that is the CPSS overall master for the shelf.
Ethernet Port
Indicates the status of the port which can be either enabled or disabled.
Host 1 IP Addr
Host 2 IP Addr
Indicates if the level zero password is enabled. For more information see
chapter 17.5.
Local IP Addr
This is the Control card IP address and is a unique 32-bit (four octet)
network layer address that uniquely identifies the node within the IP
network. It is entered in dotted decimal format.
MAC Address
Node Number
NOC Number
The telephone number of the modem serving the NOC computer, which
is the computer running the network management software.
Session Time
Subnet Mask
Router Version
The version number assigned to the active Control card that is the CPSS
overall master for the node.
For information about configuring CPSS parameters for the node, see chapter 17.6.
17.3-14
(400)
Node Parameters
DISABLE*/ENABLE
LOCAL_ADDR
SUBNET
DEF_ROUTER
HOST_ADDR1
HOST_ADDR2
<IP_address>
<subnet_mask>
<IP_address>
<IP_address>
<IP_address>
SK000835
where
IP_address is in the decimal format #.#.#.# and where # is in the range 0 through 255
subnet_mask is in the decimal format #.#.#.# and where # is in the range 0 through 255
Node Parameters
(400)
17.3-15
17.4
date
time
node name
17.4.1
F1-CONFIG
F6-
D117-H1-00
Toronto:P3A
F2-HOUSE
F7-
F3-MAINT
F8-
Alarms:1
11-May-1997
F4-STATS
F9-QUIT
8:35a
F5-ALARMS
F0-
You can configure the node for the date, time, and node name. Table 17.4-1 lists the
configurable parameters.
Node Parameters
(400)
17.4-1
DS-3 Card
E3 Card
Parameter
Options
Date
<dd-MMM-yyyy>
Time
<hh:mmA or P or H>
Node name
up to 12 alphanumeric characters
(no spaces, no underscores)
To configure these parameters, see the procedure To configure the date, time, and
node name.
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
Date
In a non control-redundant system, No Date appears in the header line until you
set the date.
In a control-redundant system, the date field indicates whether the node
management session is with the active or inactive Control card. If the programmed
date or No Date appears in the header line, the session is with the active Control
card. If OnStandby appears in the header line, it is with the inactive Control card.
To set the date, select DATE and enter the date in the form <dd-MMM-yyyy>, where:
dd = the day (two digits including a leading zero)
MMM = the month (the first three letters)
yyyy = the year (four digits)
For example, enter November 21, 1996 as <21-NOV-1996>.
Time
Until the time is set, the header line on the node manager screen displays the time
elapsed since a system reset in a 12-h format followed by the indicator R. For
example, if the header line shows 10:03R, it means that the system was reset 10 h and
3 min ago.
Real time appears in the header line in a 12-h format followed by an A or P for a.m.
or p.m. respectively. In the 24-h format, the time is followed by an H.
17.4-2
(400)
Node Parameters
To set the time, select TIME and enter the time in the form <hh:mmA> or <hh:mmP>
or <hh:mmH>, where:
hh = the hour (1 or 2 digits; leading zeros are not required)
mm = the minute (2 digits)
A = a.m.
P = p.m.
H = 24-h format
For example, enter 3:17 p.m. as <3:17P> or <15:17H>. If you do not enter A, P or H,
the node assumes an A.
Node name
Until you assign a node name, the default node name appears in the header line. The
node name can have up to 12 alphanumeric characters. In Figure 17.4-1,
CHEPSTOW is the node name.
The node name is not saved as part of a configuration database backup nor is it
affected when a database is restored. When a database is loaded into a node, the
node name stays as configured to prevent two or more nodes in a network from
having the same node name.
To set the node name, select NODE_NAME and enter up to 12 alphanumeric
characters (no spaces or underscores). To delete the node name, select
NODE_NAME and press .
DATE
TIME
NODE_NAME
<date>
<time>
<name>
SK000023
where
date is dd-MMM-yyyy (dd is the day in 2 digits including a leading zero, MMM is the month indicated in
the first 3 characters, and yyyy is the year in 4 digits)
time is hh:mmA or hh:mmP or hh:mmH (hh is hours in 1 or 2 digits, no leading zeros; mm is minutes in 2
digits; A is a.m., P is p.m., and H is 24-h format)
name is up to 12 alphanumeric characters (no spaces or underscores)
Node Parameters
(400)
17.4-3
17.5
17.5.1
17.5.2
Node Parameters
(400)
17.5-1
Table 17.5-1: Access Level and Password Configuration Parameters and Options
Control
Card
DS-3 Card
E3 Card
FRS, FRE
and PE
Card
Parameter
Options
Access level 5
level 5 + password
Access levels 1 to 4
level 1 + password
level 2 + password
level 3 + password
level 4 + password
Access level 0
level 0
no level 0
Passwords
8 to 12 characters, no spaces
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
17.5.3
Level 5
Level 5 is for the system administrator because level 5 users have read/write access
to all node management functions. Only level 5 users can modify access level
definitions and change passwords. Level 5 cannot be redefined.
To log on as a level 5 user, enter <5> when prompted for the level during log on, then
enter the level 5 password. The default password is <mainstreet>.
You can enter a password from the start-up screen. The node manager tries to use
this password automatically when a level 5 user logs on.
If you are a level 5 user, you can define access levels 1 to 4 for each softkeys as
17.5-2
(400)
Node Parameters
Levels 1 to 4
Levels 1 to 4 are defined to give users access to certain node management functions
and restrict access to other functions. Access can be defined as:
function
read and write access, which means the user can read and make changes to the
function
To log on as a level 1 to 4 user, enter <1>, <2>, <3> or <4> when prompted for the
level during log on, then enter the appropriate password. The default password is
<mainstreet>.
Note
Only level 5 users can modify access level definitions. Levels 1 to 4 cannot be
accessed if a password was entered at the start-up menu of the node manager.
For levels 1 through 4, access can be defined for each of the softkeys listed in Table
17.5-2 (except CHNG_PSSWD) for the locally controlled or peripheral shelf. Access
can be defined for each of the softkeys listed in Table 17.5-3 for the FRE, FRS and PE
cards.
Access levels can also be defined at the main menu level, which represents the access
level immediately after logging on. If you define an access of a level for no access at
the main menu level, the user is only able to log off.
The access definition for a softkey overrides the access level of any softkeys
underneath it if the definition is more restrictive. That is, read-only overrides read
and write, and no access overrides both read-only and the read and write.
For example, on a locally controlled or peripheral shelf, assume the softkeys under
CONFIG have these access definitions: SLOT and CIRCUIT have read and write
access, and SYNCH has no access.
Case 1: If CONFIG has read and write access (the least restrictive definition), the
access definitions of the three softkeys SLOT, CIRCUIT and SYNCH will be in effect.
Case 2: If CONFIG is defined as read-only access (more restrictive), it overrides the
definitions for SLOT and CIRCUIT. Then SLOT and CIRCUIT will have read-only
access and SYNCH will have no access.
Case 3: If CONFIG is defined as no access (the most restrictive definition), it
overrides the definitions for SLOT, SYNCH and CIRCUIT and all three softkeys will
have no access.
As shown in Figure 17.5-1, the data area shows the access defined for a softkey; it
does not indicate if it is overridden by a more restrictive definition on another
softkey. The softkey that you are defining normally appears in the top left corner of
the data area (for example, CONFIG SLOT in Figure 17.5-1). If you are defining a
MORE softkey, the word MORE does not appear; for example, if you are defining
the access level for ALARMS MORE, only the word ALARMS appears.
Node Parameters
(400)
17.5-3
1117-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
CONFIGSLOT??
Level
1
2
3
4
Access Type
No Access
Read Only
Read/Write
Read/Write
CHANGE_ACCESS LEVEL_4 TO
F1-READ_ONLY
F6-
F2F7-
F3-NO_ACCESS
F8-CANCEL
F4F9-QUIT
F5F0-
17.5-4
(400)
Node Parameters
Level 4
You can use level 4 for the system manager who does not modify access level
definitions or change passwords. The main tasks of the level 4 users are managing
the housekeeping functions related to user access and doing maintenance functions
related to the Control card non-volatile memory.
Table 17.5-2: Suggested Access Level Definitions for Control Card Sessions
Softkeys
Access Levels
1
RO (1)
RO
R/W (2)
R/W
CIRCUIT
RO
RO
R/W
R/W
CONNECT
RO
RO
R/W
R/W
SYNCH
RO
RO
R/W
R/W
SYSTEM
RO
RO
R/W
R/W
SER_PORT_1 (3)
RO
RO
R/W
R/W
SER_PORT_2 (3)
RO
RO
R/W
R/W
DATE
RO
R/W
R/W
R/W
TIME
RO
R/W
R/W
R/W
NODE_NAME
RO
RO
RO
R/W
MORE SESSN_TIME
RO
RO
RO
R/W
n/a (4)
n/a (4)
n/a (4)
n/a (4)
MORE NODE_NUM
RO
RO
RO
R/W
MORE NOC_NUM
RO
RO
RO
R/W
DIAG
RO
R/W
R/W
R/W
DISPLAY
RO
R/W
R/W
R/W
UNDO_MAINT
RO
R/W
R/W
R/W
OW_MONITOR
RO
R/W
R/W
R/W
ON_SLOT
RO
R/W
R/W
R/W
ON_CIRCUIT
RO
R/W
R/W
R/W
MORE BACKUP
RO
RO
R/W
R/W
MORE RESTORE
RO
RO
R/W
R/W
MORE VERIFY
RO
RO
R/W
R/W
CONFIG
SLOT
HOUSE
MORE CHNG_PSSWD
MAINT
MORE VIEW_NET
n/a
MORE REDUNDANT
(5)
RO
MORE NVM_DATA
n/a
(4)
n/a
(5)
RO
n/a
(4)
n/a
(5)
RO
n/a
(4)
n/a (5)
RO
n/a (4)
STATS
Node Parameters
(400)
17.5-5
Softkeys
Access Levels
1
USAGE
RO
R/W
R/W
R/W
QUALITY
RO
R/W
R/W
R/W
SYNCH
RO
R/W
R/W
R/W
MAN_CLEAR / AUTO_CLEAR
RO
R/W
R/W
R/W
MIN/DEFER (6)
RO
R/W
R/W
R/W
MAJ/PROMPT (6)
RO
R/W
R/W
R/W
RO
R/W
R/W
R/W
CONFIG
RO
R/W
R/W
R/W
EXTNL_ALRM
RO
R/W
R/W
R/W
RSET_TEP1E
R/W
R/W
R/W
R/W
MORE LOGGING
RO
R/W
R/W
R/W
ALARMS
DIAG/INSTN
(6)
Notes
1. RO = read only.
2. R/W = read and write.
3. Changing the access level of one serial port automatically changes the access level of the other
serial port to the same parameter.
4. This softkey appears for Level 5 users only.
5. By definition, these softkeys are read-only functions.
6. Changing the access level of one alarm queue automatically changes the access levels of the other
alarm queues to the same parameter.
Table 17.5-3: Suggested Access Level Definitions for FRS, FRE and PE Card Sessions
Softkeys
Access Levels
1
RO (1)
RO
R/W (2)
R/W
FASTBUS (3)
RO
R/W
R/W
R/W
STREAM
RO
R/W
R/W
R/W
CONNECT
RO
R/W
R/W
R/W
RO
R/W
R/W
R/W
CONFIG
SWITCH
HOUSE
SESSN_TIME
CHNG_PSSWD
n/a
(4)
n/a
(4)
n/a
(4)
n/a (4)
MAINT
17.5-6
ON_CARD
RO
R/W
R/W
R/W
ON_FASTBUS (3)
RO
R/W
R/W
R/W
ON_STREAM
RO
R/W
R/W
R/W
ON_CONNECT
RO
R/W
R/W
R/W
(400)
Node Parameters
Softkeys
Access Levels
1
RO
R/W
R/W
R/W
MONITOR
RO
R/W
R/W
R/W
REFRESH
RO
R/W
R/W
R/W
MAJ/PROMPT (5)
RO
R/W
R/W
R/W
MIN/DEFER (5)
RO
R/W
R/W
R/W
RO
R/W
R/W
R/W
CONFIG
RO
R/W
R/W
R/W
MORE LOGGING
RO
R/W
R/W
R/W
VIEW_NET
STATS
ALARMS
DIAG/INSTN
(5)
Notes
1. RO = read only.
2. R/W = read and write.
3. This softkey appears for the FRE and PE cards only.
4. This softkey appears for Level 5 users only.
5. Changing the access level of one alarm queue automatically changes the access levels of the other
alarm queues to the same level.
Level 0
Level 0 is a read-only access level for which no password is required. You configure
level 0 access on a per-node basis or on the FRS, FRE and PE card (both serial ports
on the FRS, FRE and PE cards have the same configuration). You can configure the
serial ports with level 0 access or no level 0 access.
When a serial port is configured for level 0 access, any user can look at the NMTI
settings by entering <0> when prompted for the level during log on. The system
does not prompt for a password.
Level 0 users have access to all softkeys except PROCEED. Only level 5 users can
configure a port as level 0 (this softkey does not appear for users logged on at other
levels).
If a serial port is configured for no level 0, users have to give one of the five access
level passwords to log on to the node manager. They have the read and write
privileges defined for that level. The setting for level 0 has no effect on the settings
for levels 1 to 5. Level 0 cannot be redefined or assigned a password.
Set level 0 access for the serial port as:
Node Parameters
(400)
17.5-7
Select the softkey that represents the level for which you want to change the
access.
For example, to define the access to card slots, select CONFIG then SLOT or
CONFIG then FASTBUS.
2.
Enter:
<Esc> <A>
Note
The access levels for the CONFIG CONNECT menu, available on a locally
controlled or switching shelf, cannot be changed.
4.
LEVEL _1
LEVEL_2
LEVEL_3
LEVEL_4
READ/WRITE*
READ_ONLY
NO_ACCESS
To set level 0 access
HOUSE MORE LEVEL_0/NO_LEVEL_0*
17.5.4
Setting Passwords
You can configure each access level with its own password; users must enter the
password when they initiate a node management session.
The default password for levels 1 to 5 is <mainstreet>. The password for levels 1 to
5 can be changed after installation is complete. Passwords must be at least 8 and no
more than 12 alphanumeric characters with no spaces. When the system is first
commissioned, change the level 5 password on each shelf to protect the node
database. Only level 5 users can change passwords (the CHNG_PSSWD softkey
does not appear for users logged on at other levels).
17.5-8
(400)
Node Parameters
The access level passwords are not saved as part of a configuration database backup.
When a database is loaded into a node, the passwords revert to the default
<mainstreet>.
When you select CHNG_PSSWD, you are prompted for the level 5 password. This
prevents unauthorized users from changing passwords if a terminal is left
unattended while logged on at level 5.
When you enter the new password, the system prompts you to enter it a second
time. Then the system enters the password into the database in encrypted form.
Note
The DS-3 and DS-3 II cards support only one access level.
LEVEL_1
LEVEL_2
LEVEL_3
LEVEL_4
LEVEL_5
<new_psswd>
<new_psswd>
SK000025
where
level_5_psswd is your level 5 password (8 to 12 characters, no spaces)
new_psswd is the new password (8 to 12 characters, no spaces)
Node Parameters
(400)
17.5-9
17.6
CPSS Configuration
This chapter introduces CPSS and explains how to configure the following
parameters:
17.6.1
node parameters
CPSS options
CPSS connections for a network manager
CPSS FASTbus connections
CPSS routing protocol
Node Parameters
(400)
17.6-1
17.6-2
(400)
Node Parameters
CPSS cross-connections
You can cross-connect CPSS circuits to:
TS0 on E1, Dual E1, Dual E1-2, MPA and X.21/V.35 PRI links
FDL on T1 and Dual T1 links using ESF framing
all or part of a 64 kb/s channel (DS0) on all primary rate or data links (that is, they
can be subrate-multiplexed)
Unlike TS0 circuits with CPSS over them on other cards, you do not have to
cross-connect the Dual E1 card TS0 to the Control card or DCP card. Since CPSS is
terminated on the Dual E1 card, the system automatically makes the connection
when you enable CPSS over TS0.
CPSS cannot be directly or indirectly (through SRMs) connected to E1 or Dual E1
circuits in 3664 MainStreet systems. However, CPSS that terminates on other nodes
can be transported over E1 circuits.
CPSS is also carried over the system serial ports (directly or through a modem) when
configured for CPSS or modem operation (see section 17.6.8).
Note
Shared and dedicated CPSS circuits cannot be cross-connected to one another.
CPSS versions
There are two versions of CPSS: CPSSv1 and CPSSv2. CPSSv1 is supported on
Release 4 and lower systems. It provides a distance vector routing algorithm (router
version 1) and basic CPSS messaging and link costing options.
CPSSv2 is the most advanced version of CPSS supported in Release 6 and newer
versions of system software. In addition to CPSSv1 capability, it provides:
Router version 2 provides higher reliability, support for bigger networks and faster
routing table updates after a CPSS link failure. Router version 1 supports Release 6
and newer versions of node software in a Release 4 network and simplifies the
upgrade from Release 4 to 6 and up.
Node Parameters
(400)
17.6-3
Note
CPSSv2 nodes are designed to interoperate with CPSSv1 nodes during and after an
upgrade to Release 6 and newer versions of system software (see Upgrading to
CPSSv2 in this section).
Router version 2
Previously, all CPSSv1 nodes performed CPSS message routing using router
version 1. With the introduction of CPSSv2, all nodes support enhanced network
layer services and link cost options, but only certain nodes perform CPSS message
routing using router version 2.
In a network running Release 6 or newer versions of system software, CPSSv2 nodes
running router version 2 typically form the backbone of a network. These are the
3600 MainStreet series bandwidth managers nodes. In these nodes, there are one or
more CPSS routing elements that perform CPSS routing.
Routing elements are the Control card (switching, peripheral and locally controlled
shelf), DCP card, DS-3 II card and E3 card.
CPSSv2 nodes running router version 1 typically form the periphery of a network
and are called feeder nodes. To access the backbone CPSS network, feeder nodes
must be directly connected to a CPSSv2 backbone node, that is, not more than one
hop away. (A CPSS hop is a link between two CPSS routing elements that is free of
any intervening CPSS routing elements.) A node running router version 2 does not
forward CPSS traffic through a node running router version 1. Feeder nodes
typically form the periphery of the network and feed end user devices into the
backbone.
These nodes are the 3612, 3620, 3624, 3630 and 8230 MainStreet systems and the FRS,
FRE and PE cards.
Note
All backbone nodes in the same domain must run the same router version.
Domains
CPSSv2 lets you organize nodes into groups called domains; each domain has a
number. You can define up to 32 000 domains; this means that a large CPSS network
can be divided into smaller subnetworks. All domains are still under the control of
the same network manager, but each node knows only the topology of its own
domain. This reduces routing complexity, improves CPSS performance and
reliability and allows more than 1023 nodes to be included in the CPSS network.
17.6-4
(400)
Node Parameters
Note
The communication of CPSS messages from one domain to another needs an
inter-domain router, such as MDNS on the 4602 MainStreet Intelligent
NetworkStation or MainStreetXpress 46020 Network Manager.
CPSS routing element whose purpose is to route CPSS traffic exclusively, such as
the DCP card
Secondary routing element:
CPSS routing element that can route CPSS but whose main purpose is something
else, such as the Control, FRS, FRE and PE cards and the 4602 MainStreet
Intelligent NetworkStation or MainStreetXpress 46020 Network Manager.
Primary routing elements have lower CPSS path costs than secondary routing
elements to bias CPSS traffic towards them and away from secondary routing
elements.
Node Parameters
(400)
17.6-5
Router Version 1
Router Version 2
Bias
Toward
Normal
Bias
Against
Bias
Toward
Normal
Bias
Against
Primary
Dedicated CPSS circuits
Serial ports
1
1
1
1
2
2
1
1
5
10
50
50
Secondary
Dedicated CPSS circuits
Shared CPSS circuits
Serial ports
1
1
1
1
1
1
2
4
8
1
5
1
10
25
20
50
100
200
Note 1
For switching shelf controlled systems, the CPSS cost of the CPSS link between the
switching shelf and a peripheral shelf is fixed at NORMAL (1 for router version 1
and 10 for router version 2) and is not user-configurable. For all systems, the CPSS
cost of the link between a Control card shared CPSS circuit and a minor node (DCP,
FRS, FRE or PE card) is fixed at NORMAL (7 for router version 2 or 0 for
router version 1) and is not user configurable.
Note 2
For Release 2 FRE (part number 90-1673-02) and PE cards, the default CPSS cost is
BIAS_AGAINST. When you configure for BIAS_AGAINST and a DCP card is
installed, CPSS will route through the DCP card instead of the FRE or PE CPSS link.
Bias towards
B
8453
17.6-6
(400)
Node Parameters
Master/slave protocol
The CPSS master/slave protocol ensures that key CPSS parameters are configured
consistently in all elements of a system. It also simplifies the upgrade procedure
from Release 4 to Release 6 and newer versions of system software.
As shown in Figures 17.6-2 and 17.6-3, there is an overall CPSS master element and
one or more CPSS slave elements in any system. All slave elements receive their
CPSS parameter values from the master. Some slave elements function as
intermediate masters to the slave elements below them.
CPSS parameter changes can only be made on the overall master. In a switching
shelf controlled system, user attempts to change CPSSv2 parameters on peripheral
shelves are blocked.
Any CPSS parameter change made to the overall master is immediately propagated
to all slave elements. If a slave element is added to an existing system, the overall
CPSS master automatically downloads its CPSS parameter values to the new slave
element.
Figure 17.6-2: CPSS Master/Slave Protocol - Switching Shelf Controlled System
Active
switching
shelf
Active
DS-3/E3
Inactive
switching
shelf
Active
peripheral
shelf
Inactive
peripheral
shelf
Inactive
DS-3/E3
DCP
FRE/FRS
DCP
FRE/FRS
5370
Active
Control
card
Inactive
Control
card
DCP
FRE/FRS
DCP
FRE/FRS
5371
Node Parameters
(400)
17.6-7
For example, in a switching shelf controlled system, the active switching shelf is the
overall CPSS master and downloads its CPSS parameter values to the inactive
switching shelf and all active peripheral shelf Control cards, DS-3 II cards or E3
cards. In turn, each active peripheral shelf Control card downloads these values to
its inactive Control card and to all its UCS cards affected by CPSS parameter values.
Similarly, each active DS-3 II or E3 card downloads these values to its inactive
DS-3 II or E3 card mate.
Note
The master/slave protocol operates only within a system, not between all systems
in a network. It guarantees that all slave elements of a system are consistent with the
overall master of that system. The network manager must make sure that the overall
masters of each system in the network are consistent with one another.
Upgrading to CPSSv2
CPSSv2 nodes (both routing and feeder) provide backwards compatibility features
to support interoperability with CPSSv1 nodes and to simplify the upgrade
procedure from Release 4 to Release 6 and newer versions of system software.
Master/slave protocol and upgrades from Release 4 software
The master/slave protocol simplifies the upgrade procedure from Release 4 to
Release 6 and newer versions of system software, and ensures that the overall master
and all slave elements can be reached through the CPSS network at all times during
the upgrade.
The example in Figure 17.6-4 shows the basic steps (a through d) in the upgrade
procedure from Release 4 to Release 6 and how the master/slave protocol functions
for a dual-shelf, control-redundant locally controlled system. (This example applies
to upgrades from Release 4 to Release 6 and newer versions of system software.)
17.6-8
(400)
Node Parameters
(c)
(d)
Release 4
Release 4 Master
Release 6 Master
Release 6 Master
CPSSv1
CPSSv1
CPSSv1
CPSSv1
Router 1
Router 1
CPSSv2
(a)
Router 2
Router 2
x Domain
x Domain
Release 6 Slave
Release 4
CPSSv1
CPSSv1
CPSSv1
CPSSv2
CPSSv2
Router 1
Release 4
Router 1
Router 1
Router 1
Slave
Release 6
Slave
CPSSv1
CPSSv2
Router 1
Router 1
Router 2
Router 2
1 Domain
x Domain
7176
Initially (a), both the active and inactive Control card run Release 4 and the
master/slave protocol does not exist.
The inactive Control card is upgraded (b) to Release 6 (or newer version of system
software) then restarted. The inactive Release 6 Control card identifies the active
Release 4 Control card as its master. Because the master is running CPSSv1, the
inactive Release 6 Control card enters CPSSv1 mode (this mode is not
user-selectable). The router is set to router version 1, by default, and is therefore
compatible with the master. The domain number is set to 1, by default. Now you can
change the domain number on the inactive Release 6 Control card to be ready for the
activity switch that makes the Release 6 Control card active.
When you initiate an activity switch (c), the formerly inactive Release 4 Control card
becomes active. The now-active Release 6 Control card detects that it has become the
new overall master and runs the highest version of CPSS it canCPSSv2. Domain
and router version remain on the active Release 6 Control card as configured. The
master prepares to download these parameters to the inactive Release 4 Control
card, waiting until the inactive can respond to its master/slave protocol requests.
You can then upgrade the inactive Release 4 Control card (d) to Release 6 and restart
the card. The inactive Release 6 Control card identifies the active Release 6 Control
card as its master and gets ready to receive the CPSS parameter values of the master.
The active Release 6 Control card downloads its CPSS parameters values to the
inactive Release 6 Control card.
Now the system is ready for the Router Upgrade Tool to switch the network over to
router version 2. Alternatively, you can select router version 2 manually on the CPSS
overall master (see Table 17.6-2 for the location of the configuration procedure).
Node Parameters
(400)
17.6-9
Caution
As a general rule, leave CPSSv2 parameters at their default during the upgrade. The
exception is domain number (step b, in Figure 17.6-4); it should be configured to
match the domain in which the system is located. For more information on upgrades
and the Router Upgrade Tool, contact your Newbridge representative.
Router interoperability
CPSSv2 backbone nodes support router version 1 and 2 and can exchange CPSS
messages using the small packet size used by CPSSv1 or the large packet size used
by CPSSv2.
When a CPSSv2 backbone node using router version 2 is directly connected to a
CPSSv1 or CPSSv2 node running router version 1 (that is, not more than one hop
away), it automatically translates router version 2 information into router version 1
format. (Router version 1 always uses small packets; router version 2 always uses
large packets.)
CPSSv2 feeder nodes support small and large CPSS message packet sizes. The small
packets option is the default for a CPSSv2 feeder node brought on-line in a CPSSv1
network during an upgrade from Release 4 to Release 6 and newer versions of
system software.
A CPSSv2 node running router version 2 can reach a router version 1 node any
number of hops away as long as the route to the node is through router version 2
nodes only. A CPSSv2 node running router version 2 does not forward CPSS traffic
through a router version 1 node.
CPSS grooming
In a network of Newbridge equipment, only one channel in each pair of adjacent
nodes must be dedicated to CPSS messages. However, if Newbridge equipment is
connected to a network of non-Newbridge equipment, the ability to connect more
than one CPSS channel to a single CPSS carrier is advantageous. This connection is
called CPSS grooming.
17.6-10
(400)
Node Parameters
In Figure 17.6-5, the node on the left side is doing CPSS grooming. It is mediating
between many CPSS channels on one primary rate link and a single CPSS channel
on the other link. The system monitors the incoming CPSS channels from both links
and makes dynamic cross-connections as required. For example, if a CPSS message
addressed to 3624 MainStreet (#3) node comes in on the T1 link, the system connects
the single CPSS channel to the DS0 for 3624 MainStreet (#3) node for the message to
pass. With CPSS grooming, many CPSS channels can be funneled into a single
channel.
In Figure 17.6-5, each CPSS channel is routed separately and transparently through
the non-Newbridge network from the node doing CPSS grooming to the other
Newbridge equipment.
Channel limitations
The following channel limitations affect the PRI cards.
For the E1 card, timeslot 0 and all 30 DS0s can be configured as CPSS channels.
For E1 or Dual E1 cards in a 3664 MainStreet system, no circuits can be configured
for CPSS.
For the T1 card, the FDL and up to 23 DS0s can be configured as CPSS channels.
For the Dual T1 card, FDL cannot be used for CPSS if the host is running router
version 2.
For T1 and Dual T1 cards in a 3664 MainStreet system, the FDL and up to 12 DS0s
can be configured for CPSS.
For DS-3 II and E3 cards, only one DS0 in a card can be configured as a CPSS
channel.
For Dual E3 cards, only two DS0s in a card can be configured as CPSS channels.
There are other limitations on a system level. If a node contains only E1 or T1 cards,
the maximum number of channels (DS0s, TS0s or FDLs) that can be designated as
shared CPSS channels for slots A1 through A6 is 34. For example, if slot A1 contains
an E1 card with all 30 DS0s and TS0 designated as CPSS channels (a total of 31
channels), only three other channels for slots A2 through A6 can be designated as
CPSS channels, for a total of 34 channels.
If you configure more CPSS channels than allowed, the system raises a System
Advisory alarm with subcode 225.
Node Parameters
(400)
17.6-11
T1
T1
Network made up of
non-Newbridge equipment
T1
Single DS0
configured for CPSS
T1
Many DS0s
configured for CPSS
3624 MainStreet node
#5
2034
17.6.2
Configuring CPSS
Table 17.6-2 lists the CPSS configuration parameters and the cards to which they
apply. Each parameter has a list of options with any default option marked by an
asterisk.
17.6-12
(400)
Node Parameters
DCP
DS-3 II
and
E3
Card
FRS
Card
FRE
and
PE
Card
Parameter
Options
4 kb/s CPSS
4 kb/s
8 kb/s
16 kb/s
4 kb/s CPSS
enabled
disabled*
CPSS
connection type
shared
dedicated*
Cost of dedicated
CPSS
normal*
bias against
bias towards
Cost of shared
CPSS
normal*
bias against
bias towards
CPSS node
number
1 to 999
Domain number
1 to 32000 (* = 1)
Interface speed
4 kb/s
8 kb/s
16 kb/s
48 kb/s
56 kb/s
64 kb/s
NOC number
up to 30 characters
Router version
version 1*
version 2
Routing protocol
host router
router version 1*
Satellite delay
satellite
normal
Timers
T200
TACK
N200
T203
(1)
Notes
1. This parameter applies only to Release 2 FRE cards and PE cards.
Table 17.6-3 lists the CPSS connection configuration procedures and the cards to
which they apply. These procedures explain how to make CPSS connections.
Node Parameters
(400)
17.6-13
DCP
DS-3 II
and
E3
Cards
T1
Cards
E1
Cards
X.21,
V.35
and
MPA
Cards
FRE
and
PE
Cards
DNIC
and
2B1Q
Cards
FRS
Card
Configuration Procedure
64 kb/s CPSS
FDL
Signalling
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
17.6.3
node number
NOC number
domain number
CPSS connection type
router version
cost of shared CPSS
Table 17.6-2 lists these parameters and indicates the cards to which they apply.
Figure 17.6-6 shows a typical CPSS node parameter display.
17.6-14
(400)
Node Parameters
Port
1
2
1117-H1-00
Baud Rate
Port Type
9600
1200
Current Port
Session Time
Domain Number
Node Number
Router Version
NOC Number
Shared CPSS Cost
Level Zero Access
Toronto:A
Alarms:1
Flow Control
VT100
CPSS_MODEM
:
:
:
:
:
:
:
:
11-May-1997
NONE
NONE
8:35a
CPSS Cost
N/A
Normal
HOUSE CPSS
1-NODE_NUM
6-
2-NOC_NUM
7-
3-DOMAIN_NUM
8-CANCEL
4-ROUTER
9-QUIT
5-SHARE_COST
0-
Note
Node number, domain number and router version are neither backed up nor
restored. All other node parameters are backed up and overwrite the current
configuration when you do a restore procedure.
Node number
The node number (NODE_NUM) is the address used by major nodes to identify and
communicate with each other. Minor nodes (such as FRS, FRE and PE cards) are
identified by the node number of their major node and their slot.
At installation, each major node in a domain (locally controlled shelf, switching shelf
or peripheral shelf Control card and DS-3 II or E3 card) is assigned a unique node
number. Because the two Control cards in a control-redundant system (or the two
cards in a control-redundant DS-3 II or E3 card pair) act as one node, both cards must
have the same node number.
Setting and changing the node number and assigning a new node number for the
Control card, DS-3 card and E3 card are described in Installation, Task 1400:
Commissioning the Nodes.
You may need to initiate a system restart before the new (programmed) node
number takes effect or appears in the header line. In the HOUSE display, both the
programmed and current node numbers appear.
Node Parameters
(400)
17.6-15
Note
The network manager and the Craft Interface node manager manuals see node
number as CPSS node ID.
To configure the node number, see the procedure To configure node parameters.
NOC number
You must set the NOC number (NOC_NUM) if the node is part of a network
controlled by network management software. The NOC is the computer running the
network management software. Normal communications with the NOC is through
primary rate links in the network. A PSTN link and modems can be used as a
back-up to the primary rate links. The NOC number is the telephone number of the
modem serving the NOC computer.
When you enter the number, include any prefix digits that would be required if the
call were dialed manually from a phone (such as the area code). The number can
include the Hayes AT modem dial modifiers (, = pause; W = wait for dial tone;
@ = wait for silence). The NOC number cannot be more than 30 characters long. For
example, to dial a long distance number from a PBX that provides a second dial tone
after the digit 9, use 9W1-613-591-3645. By default, the node instructs the modem to
dial the NOC number using dial pulsing. For the modem to dial using DTMF, you
must precede the NOC number with the characters DT.
To configure the NOC number, see the procedure To configure node parameters.
Domain number
You configure the domain number (DOMAIN_NUM) by assigning a number in the
range of 1 to 32000 to the CPSS overall master. For a switching shelf controlled
system, the overall master is the active switching shelf Control card. For a locally
controlled system, it is the active shelf. When you configure the master domain
number, CPSSv2 immediately configures the rest of the node with the same domain
number.
To configure the domain number, see the procedure To configure node
parameters.
17.6-16
(400)
Node Parameters
Router version
You configure the router version by assigning a version number (VERSION_1 or
VERSION_2) to the CPSS overall master. For a switching shelf controlled system, the
active switching shelf Control card is the CPSS overall master. For a locally
controlled system, the active shelf is the CPSS overall master. When you configure
the master router version, CPSSv2 immediately configures the rest of the node to the
same router version.
To configure the router version, see the procedure To configure node parameters.
Node Parameters
(400)
17.6-17
To configure the cost of shared CPSS, see the procedure To configure node
parameters.
DOMAIN_NUM
NODE_NUM
NOC_NUM
<node_num>
NORMAL*
ROUTER
BIAS_AGNST
SHARE_COST
BIAS_TOWRD
SK000026
where
node_num is 1 to 999
noc_num is the NOC telephone number with any prefix digits and modem dial codes (up to 30 characters)
domain_num is 1 to 32000 (1*)
17.6.4
Table 17.6-2 lists these parameters and indicates the cards to which they apply.
17.6-18
(400)
Node Parameters
Note
For information about other CPSS options, such as viewing routing tables or CPSS
connections, see Maintenance, chapter 33.8.
Node Parameters
(400)
17.6-19
SATELLITE/NORMAL*
SPEED
<speed>
NORMAL*
PATH_COST
BIAS_AGNST BIAS_TOWRD
SK000027
where
n is 1 to 4
speed is 4, 8, 16, 48, 56 or 64 (*)
TRANSP_BW
SATELLITE/NORMAL
<bw>
NORMAL*
PATH_COST
BIAS_AGNST BIAS_TOWRD
SK000030
17.6.5
17.6-20
(400)
Node Parameters
If the link terminates on the Dual T1 or Dual E1 card, the card only passes CPSS
transparently. If the link terminates on the Control card, a Dual T1 supports up to 24
CPSS channels; a Dual E1 card supports up to 30 on a CAS framed E1 or 31 on a CCS
or 31-channel framed E1.
You can configure the 64 kb/s CPSS channel from the perspective of the CPSS
channel or the 64 kb/s circuit.
The Dual E1-2 card does not support the termination of CPSS on the card but can
cross-connect dedicated CPSS resources. The NU bits in TS0 are used to
cross-connect CPSS information terminated on the Control card or DCP to another
Control card or DCP. See section 17.6.6 for more information.
Note
In single-shelf control-redundant systems, CPSS-4 is automatically configured to
64 kb/s and connected as the mate link. If you try to configure CPSS-4, a warning
message appears.
TO_CIRCUIT
DISC_FROM or DISCONNECT
<sn-cc> or <sn-l-cc>
SK000031
where n is 1 to 4 for a Control card, 1 or 2 for a Dual E3 card and 1 for a DS-3 II card
TO_CIRCUIT
DISCONNECT
<CPSS> or <CPSS-n>
SK000032
where n is 1 to 4 for a Control card, 1 or 2 for a Dual E3 card and 1 for a DS-3 II card
Node Parameters
(400)
17.6-21
TO_CIRCUIT
DISCONNECT
<sn-cc> or <sn-l-cc>
SK000033
where the first sn-cc is the DCP circuit configured to support a 64 kb/s circuit
TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000034
where the second sn-cc is the DCP circuit configured to support a 64 kb/s circuit
17.6.6
17.6-22
(400)
Node Parameters
T1 cards
The FDL is a 4 kb/s channel available when ESF is configured on T1 links. (To
configure ESF, see chapter 20.6.) For the T1 card, you can use the FDL channel for
CPSS by cross-connecting it to a CPSS circuit on the Control card or the DCP card.
Both dedicated and shared CPSS circuits are supported.
When you connect a dedicated CPSS channel to the FDL, you must configure the
interface speed of the CPSS channel to 4 kb/s (see section 17.6.4). You cannot connect
FDL to a shared or dedicated CPSS circuit on a Dual T1 card, but you can enable
CPSS over FDL for the card when configuring the slot.
Note
CPSS on FDL cannot be terminated to Dual T1 cards if the host system is running
CPSSv2.
FDL is not available for CPSS connections on Dual T1-2 cards.
To configure FDL, see the procedure To enable or disable CPSS over FDL on Dual
T1 cards.
To connect a CPSS channel to the FDL, see the procedure To connect a CPSS circuit
to the T1 card FDL.
E1 cards
On E1 cards, you can use TS0 as a CPSS channel by cross-connecting it to a CPSS
circuit. In the resulting CPSS channel, only 16 kb/s of the available 64 kb/s
bandwidth is used.
When you connect a dedicated CPSS channel to TS0, you must configure the
interface speed of the CPSS channel to 16 kb/s (see section 17.6.4). For the E1 card,
connecting and disconnecting the dedicated resources CPSS channel effectively
enables and disables CPSS over TS0. The Dual E1 card terminates CPSS when the
CPSS option is enabled on the card. The CPSS option on the card can be disabled
without disconnecting the CPSS channel.
For the Dual E1-2 card, the NU bits in TS0 can be used to carry a CPSS channel from
the Control card or DCP card in one node to the Control card or DCP card in another
node. Both dedicated and shared CPSS channels are supported. A CPSSv1 or
CPSSv2 connection of either 4, 8 or 16 kb/s is allowed.
Node Parameters
(400)
17.6-23
Note 1
Dual E1 and Dual E1-2 cards support three features that use the same NU bit
resources in TS0: SA4 Bit Error Rate, clear NU bits and CPSS over TS0. You can
enable only one of these three features at a time for the link. Any one of these features
can be used simultaneously with the E-bit option (see chapter 20.18).
Note 2
When an E1 HDSL module is installed on a Dual E1 card, you can use any timeslot
as a CPSS channel.
To configure TS0 on the Dual E1 card, see the procedure To enable or disable CPSS
over TS0 on Dual E1 cards.
To configure TS0 on the Dual E1-2 card, see To connect or disconnect a Control card
CPSS channel on FDL or TS0.
MPA cards
The MPA card supports both shared and dedicated CPSS on each interface port. The
TS0 designated for each port must be configured seperately; however, configuration
of CPSS over TS0 is optional on a per port basis.
Either 8 kb/s or 16 kb/s CPSS can be configured on the TS0 supervisory channel. The
8 kb/s CPSS channel occupies bit position B7 of the supervisory channel and the 16
kb/s CPSS channel occupies bit positions B7 and B6. You must configure the
supervisory channel so that the required bit positions are unoccupied before
enabling CPSS on the link, for more information see chapter 20.20.
Once the framing bits are in the correct position, the speed of the CPSS channel must
be configured. To complete the CPSS circuit, the MPA card TS0 must be
cross-connected to the CPSS channel of the Control card or DCP.
If the message Not Enough Bandwidth appears when enabling CPSS for the
interface, the maximum number of channels available for data on the MPA card is
exceeded. For more information about bandwidth allocation, see chapter 20.20.
To enable 8 kb/s or 16 kb/s CPSS, see the procedure To configure CPSS over TS0
for MPA cards.
17.6-24
(400)
Node Parameters
2.
Connect the Dual E1-2 card link TS0 to the CPSS channel of either the
Control card or the DCP card.
a.
b.
Move the MPA card framing and the HCM framing bits out of bit positions B7
and B6 (see section 20.20.7 for more information).
2.
Select either 8 kb/s or 16 kb/s bandwidth for CPSS transport on the link, enter:
CONFIG SLOT <sn-l> OPTIONS MORE CPSS
8K
16K
SK000692
Node Parameters
Connect the MPA card link TS0 to the CPSS channel of either the Control card
or the DCP card.
(400)
17.6-25
a.
b.
Move the HCM framing bits out of bit positions B7 and B6 (see chapter 23.6 for
more information).
2.
Connect the link to the CPSS channel of either the Control card or the DCP card.
a.
b.
TO_CIRCUIT
<sn-FDL> or <sn-TS0> or <sn-l-TS0>
DISCONNECT
SK000037
17.6-26
(400)
Node Parameters
TO_CIRCUIT
<sn-cc>
DISCONNECT
SK000038
17.6.7
Node Parameters
(400)
17.6-27
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = CPSS
7187
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = CPSS
7188
The subrate CPSS channels from 8 to 56 kb/s are transparent channels that occupy
as many of the most significant bit positions as are required, where each bit position
represents 8 kb/s. For example, a 16 kb/s subrate CPSS channel is a transparent
channel that occupies the two most significant bit positions (bit positions B7 and B6).
17.6-28
(400)
Node Parameters
The circuit carrying the CPSS channel, or the SRM used to multiplex the subrate
CPSS channel with other voice or data channels, needs some preparation, depending
on whether it is a transparent or HCM SRM.
configured for transparent rate adaption and for a bandwidth equal to or greater
than the bandwidth of the CPSS channel.
If a transparent SRM is being used to subrate-multiplex the CPSS channel, the
transport bandwidth must be equal to or greater than the bandwidth of the CPSS
channel. Nothing needs to be done with the transport position.
If an HCM SRM is being used to subrate-multiplex the CPSS channel, the
bandwidth available for transparent channels must be equal to or greater than
the bandwidth of the CPSS channel. That is, the framing bit must be adjusted so
that the HCM frame does not occupy the bit position(s) that the CPSS channel
occupies.
Figures 17.6-9 and 17.6-10 show how the framing bit can be relocated for a 16 and
48 kb/s CPSS channel, respectively.
Figure 17.6-9: 16 kb/s CPSS Channel with Framing Bit at F0-B5
F0
B7
B6
B5
B4
B3
B2
B1
B0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = CPSS
or
a = sn-cc
a DCP
circuit
identifier
7189
Node Parameters
(400)
17.6-29
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
a = sn-cc
7190
Note
If an SRM is carrying a CPSS channel, that SRM cannot be connected to the branch
channel of another SRM.
Configure the DNIC or 2B1Q Line card or DSP card for subrate multiplexing
and either HCM or transparent rate adaption (see chapter 23.6).
2.
If you are connecting an 8 to 56 kb/s CPSS channel to an HCM SRM, adjust the
SRM framing bit so that it does not occupy the bit positions that the CPSS
channel will occupy (see chapter 23.6).
3.
Configure the SRM for CPSS and select the bandwidth to be dedicated to the
CPSS channel as 4_kbps, 8_kbps or 16_kbps.
When CPSS is connected to the SRM, the CPSS bandwidth is listed on the
display to the right under CPSS Speed.
CONFIG CIRCUIT <sn-cc-Mmm> FUNCTION CPSS
4_kbps
8_kbps
16_kbps*
SK000039
17.6-30
(400)
Node Parameters
4.
From the switching shelf, connect an SRM to a circuit on a T1, E1 or X.21 or V.35
PRI link, a supervisory channel on an X.21 or V.35 PRI link, or a DCC, DNIC or
2B1Q circuit by entering:
CONFIG CONNECT <x-sn-Mmm> or <x-sn-cc-Mmm>
TO_CIRCUIT
DISCONNECT
<x-sn-cc> or <x-sn-l-cc>
SK000040
5.
Connect CPSS to the SRM (you cannot connect the SRM to CPSS).
CONFIG CONNECT <CPSS>
TO_CIRCUIT
DISC_FROM
<sn-cc-Mmm>
SK000041
From the locally controlled or peripheral shelf, configure a DCP card to support
4 kb/s CPSS channels by selecting slot option 4KBPS.
CONFIG SLOT <sn> OPTIONS 4KBPS/NO_4KBPS*
2.
TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000042
where
the first sn-cc is one of the DCP circuits from 24 to 31
the second sn-cc is an SRS configured for CPSS or an SRM configured for HCM rate adaption
Node Parameters
Configure the DCP circuit for the CPSS bandwidth you want (see section 17.6.4,
Interface Speed).
(400)
17.6-31
2.
Configure the DCC, DNIC or 2B1Q circuit for transparent rate adaption and
make sure that the circuits transport bandwidth is equal to that of the DCP (see
chapter 23.6).
3.
From the switching shelf, connect the DCP circuit to the DCC, DNIC or 2B1Q
circuit.
CONFIG CONNECT <sn-cc>
TO_CIRCUIT
DISCONNECT
<sn-cc> or <sn-cc-p>
SK000043
Configure the DNIC or 2B1Q Line card or DSP card for subrate multiplexing
and either HCM or transparent rate adaption (see chapter 23.6).
2.
If you are configuring an HCM SRM, adjust the SRM framing bit so that it does
not occupy the bit positions that the CPSS channel will occupy (see
chapter 23.6).
3.
From the switching shelf, connect the SRM to a circuit on a T1, E1 or X.21 or V.35
PRI link, a supervisory channel on an X.21 or V.35 PRI link or a DCC, DNIC or
2B1Q circuit.
CONFIG CONNECT <sn-Mmm> or <sn-cc-Mmm>
TO_CIRCUIT
DISCONNECT
<sn-cc> or <sn-l-cc>
SK000044
4.
Connect the DCP circuit to the SRM. (You cannot connect the SRM to a DCP
circuit.)
CONFIG CONNECT <sn-cc>
TO_CIRCUIT
DISCONNECT
<sn-Mmm> or <sn-cc-Mmm>
SK000045
17.6-32
(400)
Node Parameters
17.6.8
17.6.9
Node Parameters
(400)
17.6-33
Note
The FRS card does not support shared CPSS connections.
3600 MainStreet
Node A
F
R
S
D
C
P
C
T
L
F
R
S
FRS X DCP
D
C
P
C
T
L
3600 MainStreet
Node C
FRS X DCP
LMI
NNI
LMI
NNI
Frame Relay Network
Preferred path
Alternate path
Fault
F
R
S
D
C
P
C
T
L
3600 MainStreet
Node B
FRS X DCP
10484
17.6-34
(400)
Node Parameters
17.6.10
FRE
FRE
CPSS links
FRATM
FRE
FRE
FRE
FRE
FRATM
FASTbus
7620
FASTbus CPSS connections from one station to another are made in NMTI by
connecting one of the two available CPSS resources (CPSS1 or CPSS2) to a target
FASTbus station number. At the target station, a complementary connection must
be made. A special DLCI is automatically used for each frame relay CPSS link.
When you specify a FASTbus to CPSS1 link, the DLCI that is used is 1020; when you
specify a FASTbus to CPSS2 link, the DLCI used is 1021.
Two byte DLCIs are used for CPSS to prevent frame relay encapsulated CPSS from
being switched onto WAN links by FRE or PE cards. CPSS connections to WAN
DLCIs are blocked. FRE or PE cards can be configured only to switch data from
FASTbus DLCIs in the range 2000 to 3983 (see chapter 25.7).
Node Parameters
(400)
17.6-35
CPSS<x>
F<y>-CPSS
TO_DLC F<y>-CPSS
TO_DLC CPSS<x>
SK000046
where x is 1 or 2 and y is 1 to 64
Note
FASTbus CPSS connections can only be made to FASTbus circuits.
Figure 17.6-13 shows the CONFIG CONNECT CPSSx screen used to configure
FASTbus CPSS.
Figure 17.6-13: CONFIG CONNECT CPSSx NMTI Screen
FRE
Stations:nn
P412-H1-00
From
CPSS1
Toronto:A
Status
Unknown
Alarms:1
Connected To
--
11-May-1997
Status
--
8:35a
Traffic Group
16-
17.6-36
2-DISCONNECT
7-
3-TO_DLC
8-CANCEL
(400)
4-INFO_RATE
9-QUIT
50-
Node Parameters
T200 <value>
TACK <value>
N200 <value>
T203 <value>
SK000047
CPSS timers (available on the Release 2 FRE and PE cards only) define the
performance of the CPSS link over the FASTbus. Table 17.6-4 defines the types of
timers available.
Table 17.6-4: CPSS Timers
Timer
17.6.11
Description
T200
This is the amount of time the return ACK has for the point to point link layer
transport times. The timeout value can be between 1 and 30 s (default is 4 s).
TACK
This is the amount of time that the information frame that is received can wait for
acknowledgment. The TACK timeout value can be between 0.5 and 20 s (default
is 1 s).
N200
This establishes the number of retries that are permitted. The number of retries
that are permitted can be between 1 and 10 (default is 5).
T203
This establishes the amount of time the link can remain inactive. The timeout value
can be between 20 and 600 s (default is 30 s). T203 must be greater than twenty
times the T200 value.
Node Parameters
(400)
17.6-37
router version 1
This configures the card to run DV router.
host router
This configures the card to run the same routing protocol as the host Control
card.
To keep the amount of activity on the CPSS resources of the host Control card
manageable, you can configure only two FRS, FRE or PE cards as host router in an
LS routing node. The remaining FRE or FRS cards must be configured for router
version 1.
The CPSS routing protocol for an FRS, FRE or PE card can be configured through
NMTI as follows.
Note
Do not configure an FRS, FRE or PE card for ROUTER_V1 in an LS routing node if
the card is carrying CPSS circuit or serial port connections. If you configure the FRS,
FRE or PE card for ROUTER_V1, the CPSS in the network may be disrupted.
Do not configure an FRS or FRE card for ROUTER_V1 in an LS routing node if the
card is carrying CPSS circuit or serial port connections. If you configure the FRS or
FRE card for ROUTER_V1, the CPSS in the network may be disrupted.
17.6-38
(400)
Node Parameters
17.7
17.7.1
Overview
Backplane card communication links connect the Control card directly to
DCP-based cards. These links provide internal CPSS communications between the
Control card and a DCP-based card without affecting the throughput of the
DCP-based card. Although backplane CPSS is not configurable, the backplane card
communication links can be configured as shared or dedicated through NMTI.
The following DCP-based cards provide configurable backplane card
communication links.
17.7.2
CPC
DCP
FRE
FRS
PE
Node Parameters
(400)
17.7-1
Caution
For CPCs, it is recommended that the backplane card communication link remain
configured for dedicated CPSS. If the link is configured for shared CPSS, it will limit
the number of D channels the CPC can process.
17.7.3
Fault Handling
The FRE and PE cards provide configurable fault handling for backplane card
communications. A card can be set to handle faults in one of two modes: standard
or enhanced.
Note
Enhanced mode is only available to FRE and PE cards that support enhanced mode.
If a packet card that does not support enhanced mode is inserted in a slot configured
for enhanced mode a revision mismatch alarm is raised. For more information,
contact your Newbridge representative.
Standard mode
Standard mode provides card database synchronization at the expense of traffic
speed. Priority is placed on maintaining database synchronization between the
Control card and the packet card, even in the event of communication difficulties. To
assure database continuity, the packet card is automatically reset when
communication difficulties are experienced.
Enhanced mode
In enhanced mode, network or system operators have more control over the action
taken by the Control card when card communications faults are detected. This
control comes at the expense of database configuration synchronization between the
Control card and the packet card. Temporary database configuration mismatches
are possible in enhanced mode, but are resolved automatically by the system once
the fault clears.
Enhanced mode introduces minor and major fault counts, database re-sends, a major
fault count reset threshold and a major fault card dead threshold.
17.7-2
(400)
Node Parameters
Caution
Changing from enhanced to standard mode while a database re-send is in progress
will result in a disruption of service.
a Card Comm Problem alarm is raised with the parameter of the alarm indicating
the cause of the problem
both the current and overall major fault counts are increased by 250
the Control card attempts to restart the link if the link is down; each failed
attempt causes the current and overall major fault count to increase by 250
Node Parameters
(400)
17.7-3
Database re-sends
When a link is successfully restarted after a link failure, a database re-send takes
place. The Control card uses a database re-send to attempt to re-send all database
items needed by the packet card to restore database synchronization after the card
communication difficulty.
Database re-sends are attempted as soon as the link permits and proceed slowly to
increase the chances that re-sent information will be processed successfully by a
busy packet card. As re-sent management packets are successfully acknowledged,
the major and minor fault counts are reduced.
A card receiving a database re-send has an NMTI slot status of RSND or DB Resend.
Packet card-initiated resets
If the flow of CPSS packet data stops due to a serious fault, FRE and PE cards can
initiate a self-reset. Packet card-initiated resets cannot be prevented by using
enhanced mode fault handling.
17.7-4
(400)
Node Parameters
ENHANCED/STANDARD*
THRESHOLD
CARD_RESET
CARD_DEAD
<threshold>
UNLIMITED
SK000913
where threshold is in the range 1 to 30000 with a default of 500 for CARD_RESET and 5000 for
CARD_DEAD
Node Parameters
(400)
17.7-5
18. Redundancy
18.1
Control Redundancy
This chapter explains how to do the following tasks:
18.1.1
Card or Cable
Enhanced
Locally
Controlled
Shelf
Locally
Controlled
Shelf
Switching
Shelf
Peripheral
Shelf
HSPS
Shelf
HSPS 2
Shelf
Clock card
Switching card
SI card
SI cable
DS-3 link
E3 card
E3 cable
Redundancy
(400)
18.1-1
18.1.2
Control
Cards (1)
3600+ MainStreet
Control Card
DS-3 and
DS-3 II
Card
E3
Card
RLS_CTRL
enable
disable*
simplex*
redundant
Parameter
Options
18.1-2
(400)
Redundancy
Control
Cards (1)
3600+ MainStreet
Control Card
DS-3 and
DS-3 II
Card
E3
Card
Options
simplex
redundant*
simplex (unprotected)
interface
access
enable*
disable
AIS
OOF
BER
enable*
disable
alarm time
error rate
error time
Standby mode
hot
Parameter
Notes
1. These are the 3600, 3645, 3664 and 36120 MainStreet Control cards.
2. These options apply only when the Control card is configured as redundant.
3. These parameters apply only to the DS-3 II card.
4. The term warm partitioned is not used with the 3600+ MainStreet Bandwidth Manager. Partitioned and warm partitioned
have the same functionality.
Table 18.1-3 lists the locations of the control redundancy configuration procedures
for the Control, DS-3 II or E3 card.
Table 18.1-3: Control Redundancy Configuration Procedures
Configuration Procedure
Redundancy
Section
18.1.3
18.1.5
Card replacement
18.1.9
(400)
18.1-3
Note
To configure control redundancy for the HSPS equipped with DS-3 cards, you must
install jumpers for the DS-3 cards on the backplane (see Installation, Task 0500:
Setting the Redundancy Jumpers). Control redundancy can be program-configured
for DS-3 II cards.
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
18.1.3
The Activity LED is lit on the active Control card, DS-3 card and E3 card and is
The act of transferring control from one Control card to the other is called an activity
switch.The removal or major failure of an active Control card always causes an
activity switch regardless of the control redundancy mode. The removal or major
failure of an inactive Control card has no effect.
18.1-4
(400)
Redundancy
Configuring 3600, 3645, 3664 and 36120 MainStreet Control cards for
redundancy
For the locally controlled shelf, configure the redundancy mode as:
The system must meet these conditions before you can configure a single-shelf
system as control-redundant.
The shelf Select jumper on the backplane next to the Control card in slot 9 must
be set to position A.
An appropriate filler plate must be installed in slot 10.
The dedicated CPSS-4 circuit must be available for the mate link (if it is already
in use, disconnect it).
The Expander card slot must be configured as empty.
To configure 3600, 3645, 3664 and 36120 MainStreet Control cards for
redundancy
CONFIG SYSTEM REDUNDANT/SIMPLEX*
DUAL_SHELF
SNGL_SHELF
SK000049
Note
For more information about upgrading to single-shelf redundancy, see Maintenance,
chapter 40.3.
Redundancy
(400)
18.1-5
In simplex mode, an inactive Control card will flash a u on its faceplate 7-segment
display to indicate that it is unavailable. If the active Control card is removed from
its slot, or if a serious card failure occurs, an activity switch occurs.
Caution
Because the databases of the inactive and active Control cards are not synchronized,
if an activity switch occurs in simplex mode a major service disruption can occur. All
current configuration information can be lost, but the node will be operational for
new configurations.
Compatible software generic: the software generic of the inactive Control card
and of the active Control card are compared to make sure that they are
compatible. If the software generics are not compatible an Incompatible Mate
Generic alarm is raised.
Compatible CPSS address: the CPSS address of the inactive Control card and of
the active Control card are compared to make sure that they are compatible. If the
CPSS addresses are not the same, the mate link is brought down and a Wrong
Mate Node Number alarm is raised.
Address auto-configure: if the CPSS address of the inactive Control card is
unassigned it will be automatically configured with the CPSS address, domain
number and router version of the active Control card.
If all checks are successfully completed a Talking to Mate CTL is raised. If the mate
link is lost, a Not Talking to Mate alarm is raised and the active Control card will
continue to try to restart the mate link.
In hot standby mode, if one Control card has a Bank-B Memory module installed but
the other Control card does not, the inactive card raises a Memory Module Mismatch
alarm. See Table 35.8-17 in Maintenance.
18.1-6
(400)
Redundancy
Card/Interface
Description
Simplex
(UNPROTECTD)
Interface
(INTFC_PROT)
Access
(ACCES_PROT)
UNPROTECTD
NTFC_PROT
ACCES_PROT
SK000050
Note
Before you change a DS-3 II or E3 card protection mode from unprotected to accessor interface-protected, or vice versa, you must remove any card from the mate HSPS
slot. After you configure the protection mode, replace the inactive card.
MORE
REDUNDANT
ON_SLOT
<sn>
SK000051
Table 18.1-5 lists the fields that appear in the Control card redundancy menu.
Redundancy
(400)
18.1-7
18.1.4
Description
Redundancy
No redundancy
Partitioned
Hot Standby
Protection Mode
Time Switch
Last Switch
System Demerits
SI Cables
The status of the four SI cables (if logged on to a peripheral shelf, HSPS or
HSPS2)
Hot standby
In hot standby mode, the configuration databases of the two cards are the same. Any
change to the database of the active card is automatically copied to the database of
the inactive card. An activity switch occurs after a database reconcile is completed.
Activity switches only occur if failures on the inactive Control card are less severe
than those on the active Control card; otherwise the active Control card will continue
to operate.
When an activity switch occurs in a hot standby system, calls in progress are not
dropped. The output timing of the system can experience a short disturbance and
there can be a short period of corruption of data or a short burst of noise on voice
circuits. This period lasts no longer than 125 ms. Maintenance operations in progress
could be lost and configuration changes in progress could be aborted. After a hot
standby activity switch occurs, the newly inactive card restarts itself and reconciles
its database with the database of the newly active card.
18.1-8
(400)
Redundancy
If the active Timing card fails or is removed in a 3600+ MainStreet system, a fast
activity switch occurs. A fast activity switch can only occur when:
If the active Timing card is lost, the inactive 3600+ MainStreet Control card will also
raise a Timing Failure alarm and report demerits. Timing Failure alarm subcodes are
used to distinguish which of the two Control cards raised the alarm. Demerits
reported for the inactive Control card are substantially less than those reported for
the active Control card when the active Timing card is lost. See Table 18.1-6.
Note
3600+
In hot standby mode, if one 3600+ MainStreet Control card has a Bank-B Memory
module installed but the other Control card does not, the inactive card raises a
Memory Module Mismatch alarm. See Table 35.8-17 in Maintenance.
Partitioned
In partitioned (or warm) mode, the active Control card does not report any changes
in the configuration of the system to the inactive Control card and the inactive
Control card does not monitor the status of the system. Since the configuration
databases of the two cards can differ, database synchronization cannot be
guaranteed in partitioned mode. Partitioned mode permits replacing and upgrading
of the software or hardware of either or both cards with minimal interruption to
service.
The 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020
Network Manager provides backup and restore procedures that can be used to
transfer the configuration database from one card to the other in partitioned mode.
In partitioned mode, if background diagnostics are enabled for the inactive card, the
tests cycle through test 1 (program integrity), test 2 (RAM integrity) and test 3 (NV
RAM integrity). Only tests 1, 2 and 3 are available for directed diagnostic tests as
well (see Maintenance, chapter 39.1).
Redundancy
(400)
18.1-9
Caution
Partitioned mode redundancy is for maintenace purposes only and is not
recommended as an operational mode.
If an activity switch occurs in partitioned mode, calls in progress are dropped, all
interface cards are reset and maintenance operations and configuration changes in
progress are lost. Changes made to the configuration database since the system was
placed in partitioned mode are also lost.
Configure standby mode as:
HOT
18.1.5
PARTITION* or WARM*
SK000052
18.1-10
(400)
Redundancy
Demerits
15
20
100
100
100
100
150
(1)
Inactive Control card has lost contact with the active Timing card
(1)
200
E3 link alarm
250
275
Inactive Timing card is not synchronized to the active Timing cards (1)
275
275
350
400
400
400
400
8+ module absence
400
500
500
550
800
1000
(1)
2000
2500
2500
3000
3000
3500
(1)
5500
5500
Notes
1. This condition applies only to the 3600+ MainStreet Bandwidth Manager.
Redundancy
(400)
18.1-11
In hot standby mode only, an activity switch occurs if the system demerits value for
the active card is greater than the value for the inactive card. If the other Control card
is present, an activity switch is guaranteed when:
18.1.6
18.1-12
(400)
Redundancy
In a redundant switching shelf configuration, the active shelf does not allow an
activity switch to take place if the inactive switching shelf has lost power.
Alarms
Two alarms are raised by activity switches.
A System Restart (Active) alarm is raised by the newly active Control, DS-3,
DS-3 II or E3 card.
A System Restart (Inactive) alarm is raised by the newly inactive Control, DS-3,
DS-3 II or E3 card.
In both alarms, the first parameter is the slot of the card that lost activity. The second
parameter is the reason for the activity switch. (For more information, see
Maintenance, Table 35.8-23.)
Database reconciliation
A database reconciliation is the process of two Control, DS-3, DS-3 II or E3 cards
comparing their databases and making them the same. If differences are detected
between the two databases, the system assumes that the database of the active card
is correct and changes the database of the inactive card to match that of the active
card. A database reconciliation does not affect service.
Redundancy
(400)
18.1-13
after an activity switch (the newly inactive card restarts itself then reconciles its
database with that of the newly active card)
when the two cards begin to communicate after a period of not communicating
A fully loaded control-redundant locally controlled or enhanced locally controlled
shelf takes 20 min to reconcile the database. A fully loaded control-redundant dual
peripheral shelf takes 15 min and a switching shelf redundant configuration takes 2
min for each connected peripheral shelf for reconciliation (20 min for a fully loaded
system).
During database reconciliation, the message Reconcile in Progress and the
number of records processed appear in the data area for node management sessions
running on both the active and inactive cards. The system demerits value for the
inactive card increases by 1000 points.
An inactive Control card displays an L (for Load) on the display LED.
The inactive DS-3 or DS-3 II card cycles the faceplate LEDs as follows:
the alarm LEDs light individually from top to bottom for half a second each
after the bottom LED goes off, all alarm LEDs remain off for half a second
Refresh the screen (<Esc> <R>) to update the number of records and the demerits
value.
When the message Reconcile in Progress disappears from the screen and the
system demerits value for the inactive card decreases by 1000 points, the database
reconciliation is complete.
Note
Do not force an activity switch during a database reconciliation.
18.1-14
(400)
Redundancy
18.1.7
Reason for
Activity
Switch
Description
Range
AIS
AIS fault
500 ms
1500 ms
3000 ms
5000 ms
OOF
OOF fault
500 ms
1000 ms
1500 ms
2000 ms
BER
Error rate
exceeded
Sets the error rate and the time over which the
error rate is integrated, before an activity
switch occurs.
10-6, 3 s
10-6, 10 s
10-4, 2 s
10-4, 6 s
Redundancy
(400)
18.1-15
Reason for
Activity
Switch
Description
Range
ALARM_TIME
E3 fault
100 ms to 30 s in 10 ms
increments (Default is 100 ms)
ERROR_RATE
ERROR_TIME
Error rate
exceeded
18.1-16
(400)
Redundancy
ENABLE*/DISABLE
AIS
OOF
BER
10-6_3sec*
10-6_10sec
10-4_2sec
10-4_6sec
SK000053
ENABLE*/DISABLE
ALARM_TIME
ERROR_RATE
<alarm_time>
<range>
ERROR_TIME
<error_time>
SK000054
where
alarm_time is 100 ms to 30 s in 10 ms increments (100*)
range is 1E-3 to 1E-8 in exponential steps (1E-6*)
error_time is 1 to 3600 s in 1 s increments (3 s*)
18.1.8
Redundancy
(400)
18.1-17
ENABLE/DISABLE*
<day>
DAY
TIME
<hh:mmA or P or H>
<DAILY>
SK000055
where
day is the name of the day
hh is the hour (1 or 2 digits)
mm is the minute (2 digits)
Note
If the system time has not been set, the node manager records the time entered here
in the format <hh:mmR>, where R represents the time elapsed since a system reset.
An automatic activity switch does not occur unless you set the system time.
For example, enter 3:17 P.M. as <3:17P> or <15:17H>. If you do not enter <A>, <P>
or <H>, the system assumes A.
18.1.9
Make sure that the card you want to replace is inactive. If it is active, establish
a node management session with the switching shelf, peripheral shelf, Control
card, DS-3, DS-3 II card or E3 card, then force an activity switch by entering:
MAINT MORE REDUNDANT RLS_CTRL
2.
Enter:
MAINT MORE REDUNDANT PARTITION or WARM
18.1-18
(400)
Redundancy
Note
The PARTITION option applies to the 3600+ MainStreet Bandwidth Manager, 3645
MainStreet Control cards, DS-3, DS-3 II or E3 cards.
The WARM option applies only to 3600, 3664 and 36120 MainStreet Control cards.
The information is passed to the inactive card; the card is then configured for
partitioned mode.
3.
4.
Enter:
MAINT MORE REDUNDANT HOT
The cards reconcile their databases. Wait for the reconciliation to finish before
starting another procedure.
Redundancy
(400)
18.1-19
18.2
Protection Switching
This chapter introduces protecting connections, provides guidelines for designing
protection switching circuits and explains how to configure protecting connections.
18.2.1
Voice card
Preferred
connection
Control card
Primary rate
card
DX
PBX
A2-1
A1-1 (PC)
Primary
rate link
Protecting
connection
Voice card
Control card
Primary rate
card
DX
= Active connection
= Inactive connection
PC = Protected circuit
NPC = Not protected circuit
A3-1
A4-1 (NPC)
Primary
rate link
Protecting
circuit
4176
The preferred connection is the connection that a circuit uses if that circuit is
available.
The protecting connection is the connection that a circuit uses if the preferred
connection fails or cannot be completed. When this happens, the protected circuit is
connected to the protecting circuit and the data follows the alternative route. This
automatic switching from a preferred connection to a pre-configured protecting
connection is called protection switching. There is a short disruption to the data flow
when a switch to a protecting connection occurs.
In general, any two circuit types that can be used to form a preferred connection can
also be used to form a protecting connection. The exceptions are DSP circuits,
circuits connected to branch channels of SRMs and compressors and voice
compression subchannels on Dual E1 and T1 cards.
A protecting connection is made under some conditions. If the preferred connection
is configured and available, the protecting connection is not needed. If the preferred
connection is not configured or not available, the protecting connection is made, if
possible.
Redundancy
(400)
18.2-1
E1 (1)
E1 (2)
E1 (3)
E1 (4)
Phone
Phone
3600
MainStreet node (1)
Fault
3645
MainStreet node (3)
Protecting connection
Active (and preferred) connection
7154
An alarm is raised at node (1) and protection switching occurs at the node (1);
If the circuits on link E1 (1) are configured for seized or idle fault signalling at node
(2), node (3) is not informed that link E1 (1) is out of service, so the node does not
switch the circuits on link E1 (2) to their protecting circuits on link E1 (4).
By configuring the circuits on link E1 (1) for out-of-service signalling at node (2),
node (3) is informed that link E1 (1) is out of service and the node switches the
protected circuits on link E1 (2) to their protecting circuits on link E1 (4).
18.2-2
(400)
Redundancy
18.2.2
Options
Protecting connections
protect by
protecting
preferred
protection
Note
Protection switching applies to all cards except DSP, circuits connected to SRM
branch channels and compressors and voice compression subchannels on Dual E1
and T1 cards.
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
18.2.3
Automatic override
Normally, protecting circuits are not used for other applications. However, you can
set up a shared environment. In a shared environment, a connection involving a
protecting circuit can be broken at any time without warning, so that the protecting
circuit can connect to the circuit it has been configured to protect.
For example, in Figure 18.2-3, circuit A1-1 is connected to circuit A2-1 (the preferred
connection) and is configured for a protecting connection to circuit A3-1. Circuit
A4-1 is connected to circuit A3-1. When all circuits are available, the connection
between circuits A1-1 and A2-1 is active and the connection between circuits A4-1
and A3-1 is active.
Redundancy
(400)
18.2-3
Voice card
PBX
Preferred
connection
Control card
Primary rate
card
DX
A2-1
A1-1 (PC)
Primary
rate link
Protecting
connection
Voice card
Control card
Primary rate
card
DX
= Active connection
= Inactive connection
PC = Protected circuit
NPC = Not protected circuit
A3-1
A4-1 (NPC)
Primary
rate link
Protecting
circuit
4177
However, if circuit A2-1 becomes unavailable for connection, circuit A1-1 switches
to its protecting connection with A3-1 and the connection between A3-1 and A4-1 is
overridden. Circuit A1-1 switches back to its preferred connection when circuit A2-1
becomes available.
Circular protection
The node management software does not let you configure a circular protecting
connection. For example, in Figure 18.2-3, circuit A2-1 cannot act as a protecting
circuit for circuit A4-1.
However, you can establish a chain of connections. Circuit A2-1, for example, could
be protected by a fifth circuit.
Super-rate protection
When you connect a protecting super-rate circuit to an unprotected circuit, the
unprotected circuit must be a super-rate circuit running at the same speed as the
protected circuit. A protecting super-rate circuit must have the same number of DS0s
and bandwidth as the protected circuit.
Compatibility
When planning protection connections, make sure that the protected circuit is
compatible with the protecting connection.
18.2-4
(400)
Redundancy
Note
Only the E&M and OCU-DP channel units support protection switching. All other
channel units do not support protection switching.
For the 3645 MainStreet system, the maximum number of circuits configured for
protection switching is 375.
64 kb/s
Transparent
V.35
DCC
V.35
DCC
Preferred link
E1
card
DTE/Master
(pin 108 is forced high
if preferred path fails)
E1
card
64 kb/s
Transparent
DTE/Slave
(pin 108 is forced high
always)
Switched
64 kb/s
network
NTU
V.35
DCC
E1
card
NTU
4010
V.35 circuits involved in a protecting connection must be configured for DTE and
then configured as the master circuit or the slave circuit.
The AQA master circuit forces DTR high and transmits it to the NTU if the preferred
connection goes down. The slave circuit has DTR forced high at all times. Do not
make any changes to the control leads from the control leads menu (see
Maintenance). Changing the control leads could cause a protecting call to be
dropped.
If you try to configure the V.35 circuit for AQA before configuring it for DTE, the
system displays the message AQA only applicable to circuits configured for DTE
mode. If you try to change the mode from DTE to DCE, the system displays the
message AQA is configured, PROCEED will override; if you press PROCEED,
AQA is disabled.
Redundancy
(400)
18.2-5
After the protecting connection is made, the AQA configuration (master, slave or
disabled) cannot be changed. If you try to change the configuration, the system
displays the message Circuit must be disconnected before proceeding.
Chapter 22.3 describes the procedure for configuring V.35 circuits for AQA.
18.2.4
If you enter the protected circuit with the CONNECT softkey, select PROT_BY
and enter the protecting circuit identifier.
If you enter the protecting circuit with the CONNECT softkey, select
PROTECTING and enter the protected circuit identifier.
To disconnect a connection without defining another one, use the DISCONNECT
softkey, and select PREFERRED for the preferred connection or PROTECTION for
the protecting connection.
Note
If one of the circuits in the connection is on a T1 or E1 card that has a CCM, two
softkeys appear: COMP_CONV and NO_CONV. Select COMP_CONV if you want
companding conversion to be done on that connection; otherwise select NO_CONV.
The data area display indicates whether or not companding conversion is being
done for a connection by displaying Yes or No under the heading Conv.
18.2-6
(400)
Redundancy
PROT_BY
PROTECTING
<sn-cc> or <x-sn-cc>
COMP_CONV
DISCONNECT
PROTECTION
PREFERRED
NO_CONV
SK000056
PROT_BY
PROTECTING
<sn-cc>
SK000776
PREFERRED
PROTECTION
SK000777
Redundancy
(400)
18.2-7
18.3
PRI Redundancy
This chapter introduces PRI redundancy and explains how to do the following tasks:
18.3.1
configuring redundancy
handling failures
forcing an activity switch
handling fault processing
clearing card failures
Hardware requirements
The following cards support primary rate interface redundancy:
Redundancy
(400)
18.3-1
18.3.2
Options
protect by
no protection*
Table 18.3-2 lists the locations of the PRI redundancy configuration procedures.
Table 18.3-2: PRI Redundancy Configuration Procedures
Configuration Procedure
Section
18.3.7
18.3.6
18.3.5
Note
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
18.3-2
(400)
Redundancy
18.3.3
NO_PROTECT*
PROT_BY
<sn>
SK000057
where
the first sn is the identifier of the master slot
the second sn is the identifier of the slave slot
Note
When a redundant primary rate interface pair is deconfigured, the two cards operate
independently. Both cards become active and drive the line. If the Y cable still
connects the two interfaces to the same primary rate link, there is a conflict on the
line. Disconnect the cards or connect them to separate primary rate links before
deconfiguring them.
When a redundant primary rate interface pair is deconfigured, the slave slot is reset
to the default configuration settings (including no connections). The slot that was the
master retains all configuration information.
18.3.4
Handling Failures
To handle failures, you need to know the operating rules for a redundant primary
rate interface pair.
Redundancy
(400)
18.3-3
Operating rules
When you power up the system, the member of a redundant primary rate interface
pair that powers up first is designated the active card and the other member becomes
the standby card. This is independent of which card is in the master slot.
When you power down the system, any card failures are lost.
If only one member of the pair is present, it is always the active card and the system
does not try to switch to the other card regardless of the state of the active card. A
card can be absent because it has been removed or it has been declared failed.
If both members of the pair are present and one card declares the beginning or end
of a link fault (called an event), that card starts a two-second timer. If another event
occurs within those two seconds, the card restarts the two-second timer.
When two seconds have elapsed with no events, the system compares the severity
of the link faults being declared by the two primary rate cards and acts according to
the operating rules listed below (see Figure 18.3-1).
Figure 18.3-1: Operating Rules for Redundant Primary Rate Pair
Declaration
of beginning
or end of
link fault
Is the
active card
link fault more
severe?
Yes
Yes
Yes
No
Is the
standby card
link fault more
severe?
No
Are the
link faults
of equal
severity?
5449
Rule 1: The card that has declared the less severe link fault (including no link fault)
is designated as the active card and the card that has declared the more severe link
fault is designated as the standby card (this may require an activity switch).
Rule 2: The system begins fault processing on the card that has declared the more
severe link fault.
18.3-4
(400)
Redundancy
Rule 3: If the two link faults are equally severe, there is no activity switch and no
fault processing.
Rule 4: If the active card is still declaring a link fault, trunk conditioning is applied if
the slot is so configured.
Link faults
A link fault is a problem with a primary rate link. A card declares the beginning of a
link fault by raising one of the alarms listed in the left column of Table 18.3-3. The
faults are numbered in order of decreasing severity. Faults with the same number
have equal severity. When a card declares the end of a link fault, it raises the
corresponding alarm listed in the right column. Link fault alarms are raised for the
active card only and are listed in the alarm queue under the master slot identifier.
No alarms appear in the alarm queue under the slave slot identifier.
Table 18.3-3: Alarms for Declaring Beginning and End of Link Faults
Beginning of Link Fault Alarm
T1 link
1 Red Alarm
2 Failed State
Framing Err Rate Exceeded
3 Yellow Alarm
E1 link
1 Framing Alarm
Incoming AIS
2 Multi-frame Alarm
Incoming TS16 AIS
3 Failed State
Framing Err Rate Exceeded
4 Distant Alarm
TS16 Distant Alarm
2 Distant Alarm
Fault processing cannot be initiated when the two members of a redundant interface
pair declare different link faults with the same severity (for example, Failed State
and Framing Err Rate Exceeded), because fault processing is done only on the card
declaring the more severe link fault. However, if one card declares a Yellow Alarm
and the other card a Red Alarm, the card that declared the Yellow Alarm (the less
severe alarm) becomes the active card if it is not already and fault processing starts
for the card declaring the Red Alarm.
Redundancy
(400)
18.3-5
18.3.5
Alarms
During an activity switch, the system raises a card Activity Change alarm. When you
display the alarm queue containing the card Activity Change alarm, the subcode is
the slot identifier of the new active card, the first parameter is a software
representation of the slot identifier of the new active card, and the second parameter
is the reason code for the activity switch. Table 18.3-4 lists the reason codes. Reasons
3 through 8 are the alarms that caused the activity switch (the activity switch
occurred because the active card declared the alarm listed and the standby card
declared a less severe alarm or no alarm).
For example, if the active card declares a Red Alarm and the standby card does not
do the same within two seconds, the standby card becomes the active card (an
activity switch). A card Activity Change alarm is raised with parameter 2 set to 3,
because a Red Alarm declaration caused the activity switch.
18.3-6
(400)
Redundancy
Failed State
If there is an activity switch and the new active card does not declare a link fault, the
system does not invoke protection switching because the primary rate link is still in
service. Protection switching is invoked only if the link is out of service; that is, if
both members of the pair have declared a link fault and the link is configured for
two-way trunk conditioning for the class of fault being declared by the active card
(chapter 18.2 explains protection switching).
18.3.6
The card accumulates 70 or more demerit points (the card is declared failed).
The card declares the end of the link fault.
The two cards declare link faults of equal severity, including none (fault
processing can be carried out for only one member of the pair at a time).
Fault processing is automatically carried out in two cases:
when the active card declares a more severe link fault (there is an activity switch
Fault processing consists of assigning demerit points to the card that appears to be
at fault according to the schedule listed in Table 18.3-5.
Redundancy
(400)
18.3-7
Demerit Points
Fault processing begins on the old active card (there is an activity switch).
12
10 every 30 s
-1 every 4 h
Example
Both members of a redundant interface pair have no outstanding link faults. The
active card declares a Red Alarm. Two seconds later, the standby card has still not
declared a link fault, so an activity switch occurs between the active card and the
standby card and fault processing starts on the old active card (12 points). The
difference still exists 30 seconds later (12 + 10 = 22 points). The Red Alarm is cleared
and fault processing stops. If there is no more fault processing on that card, the 22
demerit points are cleared in 88 hours (22 points 4 hours/point).
If the card does not clear the Red Alarm, it accumulates 72 demerit points
(12 + 10 [3/0.5] = 72) after three minutes and the node manager declares the card
failed.
18.3.7
18.3-8
(400)
Redundancy
Alarms
When a card is declared failed, a Card Failure alarm is raised (see Maintenance,
Table 35.8-6). When you display the alarm queue containing the card Failure alarm,
the subcode is the slot identifier of the failed card (master or slave slot), the first
parameter is a software representation of the slot identifier of the failed card and the
second parameter is the reason code for the card failure, where:
Note
You can also clear the failure, without using the node manager, by removing and
re-installing either card of the redundant pair.
Redundancy
(400)
18.3-9
19.1
19.1.1
Switching card (3645 MainStreet systems and switching shelf controlled 36120
MainStreet only)
Common Carrier card
Test card
GFC3
Control cards
The Control card provides all common control node management facilities for the
system.
For the 3600, 3645, 3664 and 36120 MainStreet Control cards in switching shelf
controlled systems, system control is shared between the switching and peripheral
shelf Control cards.
Expander card
The Expander card is used in locally controlled systems to increase the input and
output handling capacity of the Control card from 6 UCSs to 8, 12 or 16 UCSs,
depending on the variant you install.
Switching card
Each Switching card installed in a switching shelf increases the digital cross-connect
switching capacity of the switching shelf Control card by 64 Mb/s. Each Switching
card is connected to a peripheral shelf, DS-3 card or E3 card.
System Cards
(400)
19.1-1
Test card
The Test card is installed in peripheral, locally controlled, and enhanced locally
controlled shelves to provide test access to voice and data circuits. The
user-installable Test module for the Test card provides analog and digital testing.
GFC3
The GFC3 is installed in peripheral and locally controlled shelves to provide analog
and digital tone tests for voice and data circuits, and BERT tests for data circuits.
19.1.2
Options
Card Level
Timing and synchronization
CPSS
Control redundancy
Slot Level
19.1-2
8+ module
no module
Serial port
(400)
System Cards
Options
Card slot
Options
Card slot
Switching card
enabled*
disabled
Options
Card slot
Carrier card
System Cards
(400)
19.1-3
Table 19.1-6 lists the configuration parameters available for digital and analog test
connections through the user-installable Test module.
Table 19.1-5: Test Card Configuration Parameters and Options
Parameter
Options
Card Operation
Card slot
Test card
Interface speed
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
direct monitor
high impedance monitor
split access
4-wire loopback
25-pair connector
Options
Card Operation
Card modules
Test module
no module*
Mu-law*
A-law
Line impedance
600 W*
900 W
Transmission mode
2-wire*
4-wire
BERT Configuration
Rate adaption method
19.1-4
HCM*
Transparent
DDS
(400)
System Cards
Parameter
Options
Transport position
B0 to B7*
Transport bandwidth
1 to 8*
Interface speed
Signalling
enabled*
disabled
Data position
single tone*
white noise
quiet tone
Tone Frequency
Loopback
loopback C
enabled
disabled
equipment*
facility
BERT Maintenance
System Cards
Inject ERR
inject an error
Inject ERR
none*
1.00E-1
1.00E-2
1.00E-3
1.00E-4
1.00E-5
1.00E-6
1.00E-7
Inject BER
BERT pattern
enabled
disabled
BER test
clear statistics
BERT statistics
enabled
disabled*
loopback C
(400)
19.1-5
Options
Card Operation
Card slot
GFC
GFC type
GFC
GFC3
Companding law
Mu-law*
A-law
Ringback tone
Mu-law*
A-law
Mu-law*
A-law
enabled
disabled*
enabled
disabled*
Mu-law*
A-law
TLP
Tx: 3 to +4 dB in 1 dB D (0*)
Rx: 6 to +1 dB in 1 dB D (0*)
Signalling type
E1
Private Line Automatic Ringdown*
Central Battery Working
Loop Calling Disconnect Clear
Earth Calling
Remote Extension
T1
Private Line Automatic Ringdown*
Private Line Automatic Ringdown_D3
Loop Start
Loop Start to E&M Conversion
Ground Start
Ground Start to E&M Conversion
Ringing bias
48 V*
0V
19.1-6
Mu-law*
A-law
(400)
System Cards
Parameter
Options
16.0 to +8.0 dB in 0.1 dB D (0*)
TLP
Tone Tester Configuration
PCM companding law
Mu-law*
A-law
Line impedance
600 W*
900 W
Transmission mode
2-wire*
4-wire
BERT Configuration
Rate adaption method
HCM*
Transparent
DDS DS0-A
Transport position
B0 to B7*
Transport bandwidth
1 to 8*
Interface speed
Signalling
enabled*
disabled
Data position
disabled
enabled*
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
System Cards
Tone type
single tone*
white tone
quiet tone
Tone Frequency
Loopback
loopback C
enabled
disabled
equipment*
facility
(400)
19.1-7
Parameter
Options
BERT Maintenance
Inject ERR
inject an error
Inject BER
none*
1.00E-1
1.00E-2
1.00E-3
1.00E-4
1.00E-5
1.00E-6
1.00E-7
BERT pattern
BER test
enable
disable
BERT statistics
clear statistics
enable
disable*
Loopback
loopback C
Note
During installation, each Control card and Switching card must be assigned a
unique node number (see Installation, chapter 14.1).
Table 16.4-1 in chapter 16.4 explains the formats of the identifiers in the procedures.
19.1-8
(400)
System Cards
19.2
19.2.1
System Cards
(400)
19.2-1
TYPE
OPTIONS
GFC
GFC3
SET_MULAW
SET_ALAW
RBT_MULAW*/
RBT_ALAW
TG_MULAW*/
TG_ALAW
NRZTRM_OFF*/ DS1TRM_OFF*/
NRZTRM_ON
DS1TRM_ON
SK000772
19.2-2
(400)
System Cards
19.3
19.3.1
System Cards
(400)
19.3-1
The system automatically configures the slot location of the Control card on the
shelf, as well as the Timing card and the Alarm Panel. The Narrowband and
Broadband modules installed on the Control card must be manually configured as
present on the card. The Bank-B Memory module is automatically configured as
present on the Control card. The Test card can be configured in the MTA slot. See
section 19.3.8 for slot configuration information.
19.3.2
8+_MODULE
NO_MODULE
To configure the SCC3(8+) card slot
CONFIG SLOT <CTL> OPTIONS
8+_MODULE
NO_MODULE
SK000059
Note
You must configure the Expander card as EMPTY before you can configure the
SCC3(8+).
If you have configured more than four shared CPSS connections, you must
disconnect them before configuring the SCC3(8+).
Before you select NO_MODULE, you must deconfigure slots 7 and 8 and any
double-bandwidth cards.
19.3-2
(400)
System Cards
19.3.3
Expander Card
Configure As
Single shelf
Not required
EMPTY*
6+2
Dual shelf
6+6
8+8
Expander card(16+)
16+
Warning
Configuring an Expander card while the system is in operation causes a temporary
disruption of service.
Note
The Expander card must be configured before a CONFIG_ALL operation. Otherwise
the system assumes only six slots will be configured.
EMPTY*
6+2
6+6
8+8
16+
SK000060
Note
If the Expander card slot is configured as anything other than EMPTY and you want
to change the slot configuration, all slots that will no longer be supported by the
Expander card must be configured to EMPTY. On the warning line, the system
displays the message Configure to EMPTY, followed by the identifiers of the slots
that need to be changed.
System Cards
(400)
19.3-3
19.3.4
TYPE
SC
OPTIONS
ENABLE*/DISABLE
EMPTY*
SK000061
19.3.5
CONFIG_ALL
TYPE
AS_PRESENT
MORE
CARRIER
SK000062
19.3-4
(400)
System Cards
19.3.6
AS_PRESENT
MORE
TESTCARD
SK001051
19.3.7
System Cards
(400)
19.3-5
The Broadband Switching module is required on the Control card to enable the
system to communicate with any HSA cards installed in slots H1, H2 or H3 on the
enhanced locally controlled shelf.
After the modules are physically installed, the Control card must be installed on the
shelf. If the system is configured for control redundancy, the Control cards are
installed in slots CTL-A and CTL-B. For more information about control redundancy
configurations, see chapter 18.1. For simplex system configurations, the card can be
installed in either CTL-A or CTL-B, but the preferred slot is CTL-A. For both system
configurations, the slot chosen for the Control card must be the mate to the slot
where the Timing card is installed.
Note
The Timing card must be installed before the Control card.
The system automatically acknowledges the Control card as present in the slot. In
the case of a control-redundant configuration, the first card to complete the start-up
diagnostic tests becomes the active Control card.
The system raises alarms if the Narrowband or Broadband Switching modules are
configured but not physically installed on the Control card. During this condition,
all cards that would have been available if the module was installed are held in reset
until the correct module is installed. For example, if the Narrowband Switching
module is configured but not installed, and the Broadband Switching module is also
not installed, the cards in slots H1, H2 and B1 to B8 are held in reset.
You cannot deconfigure the Narrowband or Broadband Switching modules while
cards are installed in the slots that the modules make available. The following error
message is displayed: Configure to EMPTY: <slot number>.
NBAND_MOD
NO_MODULE
BRAND_MOD
8k_X_8k_SW
NO_MODULE
4_X_4_SW
SK000838
19.3-6
(400)
System Cards
19.3.8
System Cards
(400)
19.3-7
20.1
20.1.1
Single T1, Dual T1 and Dual T1-2 cards (3600 MainStreet series bandwidth
managers)
Single E1, Dual E1 and Dual E1-2 cards (3600 MainStreet series bandwidth
managers)
Single and Dual Optical Extension cards (3600 MainStreet series bandwidth
managers)
MPA card (3600 MainStreet series bandwidth managers)
TTC2M card (3600 MainStreet series bandwidth managers)
X.21 and V.35 PRI cards (3600 MainStreet series bandwidth managers)
DS-3 and DS-3 II cards (3645 and 36120 MainStreet systems)
Single and Dual E3 cards (3645 and 36120 MainStreet systems)
T1 cards
T1 cards are used in peripheral and locally controlled shelves. They provide
24-channel DS1 digital link interfaces that conform to the relevant sections of AT&T
Channel Bank specifications Pub 43801 and Pub 62411 at 1.544 Mb/s. The Single T1
card provides one link; the Dual T1 and Dual T1-2 cards provide two. You can install
T1 cards in any UCS 1 to 8.
Warning
For shelves with a 6-UCS backplane (part numbers 90-0010-01, 90-0010-02 and
90-0010-08), the Dual T1-2 card must be installed in slots 1 to 6 only. Damage will
occur to the card if it is inserted in slot 7 or 8 (resource slots).
(400)
20.1-1
Note
In 3664 MainStreet systems, T1, Dual T1 and Dual T1-2 cards provide 12-channel
DS1 digital links.
E1 cards
E1 cards are used in peripheral and locally controlled shelves. They provide
32-channel 2.048 Mb/s DS1 digital link interfaces that conform to ITU-T G.703, G.704
and G.732 specifications at 2.048 Mb/s. The Single E1 card provides one link; the
Dual E1 and Dual E1-2 cards provide two. You can install E1 cards in any UCS 1 to 8.
Note
In 3664 MainStreet systems, E1, Dual E1 and Dual E1-2 cards provide 16-channel
DS1 digital links (or 15-channel links when configured for CAS framing).
The Dual E1-2 card can be used wherever a Dual E1 card is used; however, node
software sees the two cards as different types, so they cannot be directly
interchanged. The Dual E1-2 card provides the following additional features:
software downloading over the network, which minimizes card down time
local and remote G.821 statistics compliance
RAI configurable to meet ISDN requirements and detection of F2 and F5 states
enhanced maintenance and performance reports
20.1-2
(400)
Table 20.1-1: Modules Supported by the T1, E1 and Optical Extension Cards
T1 Card
E1 Card
Dual T1
Card
Dual T1-2
Card
Dual E1
Card
Dual E1-2
Card
Opt. Ext.
Cards
CSU
CSU2
CCM
DSX-1
TS24
E1 HDSL LIM
E1 LIM
Module
FT1
NTI
SAM
IHTU-C
IHTU-R
T1 LIM
TSM (1)
DRM (1)
VCM
VCM2 (2)
VCM3
IFM
Notes
1. Dual T1 cards in 3664 MainStreet systems do not support TSMs or DRMs.
2. When this document was published, the VCM2 was not available. Contact your Newbridge representative for information.
FT1 module
The FT1 module provides fractional T1 loopback support on the Dual T1-2 card. This
module generates and detects FT1 loopback activation and deactivation codes
according to Annex B ANSI T1.403. Once the code is generated, it is transmitted to
the remote end, where another FT1 module or an T1.403 compliant device detects it
and applies or removes the loopback.
Fractional T1 loopbacks are remotely initiated on individual or super-rate circuits
without taking down the entire T1 span and interrupting services. These loopbacks
allow the user to systematically test the link for faults at each successive node.
E1 HDSL LIMs and T1 IHTU modules
E1 HDSL LIMs and the T1 IHTU modules use HDSL technology to provide
repeaterless transport of service over two pairs of unconditioned copper loops.
(400)
20.1-3
Two E1 HDSL LIMs are required to provide HDSL transmission. The E1 HDSL LIMs
are used at both ends of an E1 HDSL link to increase the distance between midspan
repeaters in an ETSI DLL.
To establish an E1 HDSL link, the E1 HDSL LIMs at each end of the E1 link must be
programmed to be either a master or slave; this is achieved by configuring the Dual
E1 card Transmit BNC Shield option. By default, the Dual E1 card Transmit BNC
Shield option is set to Earthed, which corresponds to the master mode on the E1
HDSL LIM. To program one of the E1 HDSL LIMs for slave mode, the Dual E1 card
Transmit BNC Shield option must be configured for Floating.
Warning 1
If the Dual E1 cards at each end of the link are programmed for the same Transmit
BNC Shield option (for example, master/master or slave/slave), the E1 HDSL LIMs
do not synchronize.
Warning 2
The Receive BNC Shield option must be configured for Earthed at all times.
Note
Once the E1 HDSL link is connected and the modules are programmed for either
master or slave mode, it takes from 40 to 120 seconds for the E1 HDSL interfaces to
synchronize. It also takes from 40 to 120 seconds for the T1 HDSL interfaces to
synchronize once the T1 HDSL link is connected.
MPA cards
The MPA card is used in peripheral and locally controlled shelves and has four
programmable ports. Each primary rate interface is software configurable to
transport data according to either RS-530-A, RS-449, X.21, X.21 ESI or V.35
specifications. Two alarm contacts on the primary rate interface indicate an
out-of-sync condition on the X.21 interface, making it X.21 ESI compatible. The
20.1-4
(400)
MPA card interface can be configured as either DTE or DCE. The MPA card can
connect to a total of 60 DS0s for data transport. Each interface supports n 48, n 56
or n 64 kb/s channels (where n = 1 to 30). A supervisory channel, TS0, is required
for each port to carry signalling. Super-rate channels are supported, as well as CPSS
over TS0.
A cable connects the MPA card to the UDP, which provides the physical interface to
external devices. You can install the MPA card in any UCS 1 to 8.
TTC2M cards
TTC2M cards are used in peripheral and locally controlled shelves, providing a
channelized 2.048 Mb/s CMI interface to PBXs. The interface to the PBX conforms
with TTC Standard Vol. IV Part 1 JJ-20.11 and supports thirty 64 kb/s data or voice
channels. The interface also has a TS0 supervisory channel and an unused channel,
TS16. The channels can be cross-connected at the TTC2M card to a combination of
card and channel types, including: T1, E1, X.21, V.35, DSP, E&M, LGS PLAR, BRI,
64 kb/s Codirectional, and E3. Signalling for the connected circuit assumes the
TTC2M card signalling. You can install the TTC2M card in any UCS 1 to 8.
DS-3 cards
DS-3 and DS-3 II cards are used in HSPSs. They provide 28 DS1 compatible channels;
each channel contains 24 DS0s for a total of 672 DS0s. The 28 DS1 channels are
bundled together into one DS3-compatible digital trunk interface that conforms to
AT&T Pub 54014, at 44.736 Mb/s. DS-3 II cards are used with Release 6 and newer
versions of 3600 MainStreet series bandwidth managers software. The slot is
configured automatically for the DS-3 or DS-3 II card.
E3 cards
E3 cards are used in HSPS2s. They provide 34.368 Mb/s E3 interfaces that provide
16 E1 DS1 channels; each channel contains 32 DS0s for a total of 512 DS0s. The SE3
card provides one link through coaxial connectors on the bulkhead. The DE3 card
provides two links.
Data interfaces
The 64 kb/s Codirectional card and the OCU-DP Channel Unit are data interfaces
that can perform some primary rate functions. See chapter 22.1 for a description of
data interfaces. See chapters 20.9, 20.10 and 20.12 for a description of the primary
rate functions of data interfaces.
(400)
20.1-5
20.1.2
Dual
T1
Card
Dual
T1-2
Card
Parameter
Options
CPSS
Card type
T1
Dual T1
Dual T1-2
Application module
no module
voice compression
TS24 signalling (for Dual T1 card)
DRM (for Dual T1-2 card)
FT1 module (for Dual T1-2 card)
ISDN
non-ISDN*
ISDN
CCM
conversion
no conversion*
SAM (1)
no module*
normal (installed, not used)
circuit order
timeslot order
Card Level
Slot Level
20.1-6
VCM
delta
delta G3 fax
transitional
transitional G3 fax
timeslot 24 signalling
no timeslot 24 signalling
(400)
Single
T1 Card
Dual
T1
Card
Dual
T1-2
Card
Parameter
Options
DS1 Framing
D4 framing format*
ESF
0 to 46 m (0 to 150 ft)*
46 to 137 m (150 to 450 ft)
137 to 200 m (450 to 655 ft)
15 dB*
7.5 dB
0 dB
transparent
binary 8-zero suppression
jam bit 7*
Trunk conditioning
one-way
two-way*
Fault classes
Loopback detection
none*
through CPSS
through TS24 (3)
on fault (4)
TS24 signalling
enabled
disabled*
Errored seconds
1 to 255 (* = 86)
320/1544* (5)
101/487 (5)
10-3* (4)
10-4 (4)
10-5 (4)
5 x 10-5 (4)
10-6 (4)
10-7 (4)
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Circuit Level
(400)
20.1-7
Single
T1 Card
Dual
T1
Card
Dual
T1-2
Card
Parameter
Options
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Terminate (7)
enabled*
disabled
Clear channels
NOSIG
RBS OFF
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
Notes
1. The SAM is not required in switching shelf controlled systems.
2. These parameters do not apply to T1 cards in 3664 MainStreet systems.
3. This option does not apply to Single T1 cards.
4. These options apply only to Dual T1-2 cards.
5. These options apply only to Dual T1 cards.
6. This parameter applies only to Single T1 cards equipped with T1 LIMs or CSU modules.
7. This signalling type provides T1 termination for frame relay access to frame stream circuits (on FRS,
FRE and PE cards) and Rate Adapted circuits (on FRS cards only). See chapter 25.11 for more
information.
20.1-8
(400)
Table 20.1-3 lists the E1 and Optical Extension card configuration parameters. Each
parameter has a list of options, with any default option marked by an asterisk.
Note
Optical Extension cards are configured using the same card configuration
parameters and options as the Dual E1 card.
Dual E1,
and
Opt. Ext.
Card
Dual E1-2
Card
Parameter
Options
CPSS
Card type
E1
Dual E1
Dual E1-2
Application module
no module
voice compression
ISDN frame (for Dual E1)
ISDN
non-ISDN*
ISDN
RAI
CCM
conversion
no conversion
SAM (1)
no module*
normal (installed, not used)
circuit order
timeslot order
Card Level
Slot Level
VCM
delta
delta G3 fax
transitional
transitional G3 fax
E1 Framing
CAS*
CCS
31 channels
X.21 NTU (for E1 card)
Trunk conditioning
one-way
two-way*
(400)
20.1-9
Single
E1 Card
Dual E1,
and
Opt. Ext.
Card
Dual E1-2
Card
Fault classes
Loopback detection
none*
through CPSS
on fault (for Dual E1-2 card)
Link monitoring
enable
disable*
Statistics type
CRC4
HDB3*
Nu bit
enabled
disabled*
Shield ground
Severely errored
seconds
5 x 10-6
Parameter
Options
10-5
10-4
10-3*
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
enabled
disabled*
SA4 bit on
SA4 bit off*
CRC4 reframing
enabled
disabled*
E-bit
enabled
disabled*
Circuit Level
20.1-10
(400)
Single
E1 Card
Dual E1,
and
Opt. Ext.
Card
Dual E1-2
Card
Parameter
Options
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
Custom trunk
conditioning, ABCD
bits
Custom trunk
conditioning, data
E1 signalling types
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGS PLAR D3
LGE RE
LGE EC
R2 signalling type
R2 digital signalling
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
Notes
1. The SAM is not required in switching shelf controlled systems.
2. This parameter applies only to Single E1 cards equipped with E1 LIMs.
(400)
20.1-11
Options
Slot Level
Card type
MPA
Circuit Level
Alarm Time
Declare
Clear
20.1-12
0.1 to 60 seconds
0.1 to 60 seconds
Channel type
voice*
data
Control leads
(X.21, V.35, RS-449, RS-530-A)
forced on
forced off
on
off
none
enable
disable*
CPSS
disable*
8 kb/s
16 kb/s
DGM Limit
1 to 60 (default = 5*)
Doppler buffer
enable
disable
E1 signalling types
transparent*
clear channel
E&M
LGS RE
LGS EC
LGS GS
LGS LS
LGS PLAR
LGE RE
LGE EC
LGE GS
LGE LS
R2 digital signalling
Fault classes
(400)
Parameter
Options
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
Framing
HCM1
HCM2
HCM3*
HCM4
HCM5
DCE
DTE*
Interface type
RS-530-A*
RS-449/V.36
V.35
X.21
X.21 ESI
Inversion
inverted* (voice)
not inverted (data)
Loopback detection
none*
CPSS
In-band
Number of circuits
R2 signalling type
R2 digital E+M
Slip buffer
10 to 39 frames (10*)
slip by 10 to 39 frames (10*)
SES Limit
1E-3*
1E-4
1E-5
1E-6
5E-5
contiguous
non-contiguous
equidistant
(400)
20.1-13
Parameter
Options
0* to 29
T1 signalling types
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Transport bandwidth
48 kb/s
56 kb/s
64 kb/s*
Trunk conditioning
one-way
two-way*
Notes
1. The MPA card supports both one-way and broadcast unidirectional super-rate connections.
Table 20.1-5 lists TTC2M card configuration parameters. Each parameter has a list of
options, with any default option marked by an asterisk.
Table 20.1-5: TTC2M Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
TTC2M
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Fault classes
Trunk conditioning
one-way
two-way*
Circuit Level
20.1-14
(400)
Parameter
Options
Circuit inversion
none
ADI
even
magnitude inversion*
Companding conversion
none*
A law
Mu law
Fault signalling
in-use
idle*
NIS
none
Protection switching
protected by
protecting
Table 20.1-6 lists the X.21 and V.35 card configuration parameters. Each parameter
has a list of options, with any default option marked by an asterisk.
Table 20.1-6: X.21 and V.35 PRI Card Configuration Parameters and Options
Parameter
Options
Card Level
CPSS
Slot Level
Card type
X.21 PRI 1
X.21 PRI 2
V.35 PRI
Framing (1)
1
2*
Trunk conditioning
one-way
two-way*
Fault classes
Loopback detection
none*
through CPSS
Number of circuits
0* to 29
Clocking source
invert*
normal
(400)
20.1-15
Parameter
Options
Slip buffer
PRI redundancy
Circuit Level
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
E1 signalling types
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGE RE
LGE EC
R2 signalling type
R2 digital signalling
T1 signalling types
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
(2)
Notes
1. These parameters apply only to X.21 PRI cards.
2. The X.21 and V.35 card variants that have 1 to 30 circuits available support both one-way and
broadcast unidirectional super-rate connections.
20.1-16
(400)
Table 20.1-7 lists the DS-3 and DS-3 II card configuration parameters. Each
parameter has a list of options, with any default option marked by an asterisk.
Table 20.1-7: DS-3 and DS-3 II Card Configuration Parameters and Options
Parameter
Options
Card Level
Timing and synchronization
Node name
CPSS
Control redundancy
Slot Level
Serial ports
DS3 level
Line length
0 to 69 m (0 to 225 ft)*
69 to 137 m (225 to 450 ft)
DS3 Framing
transmit as received*
M13
C-bit parity
DS1 Level
DS1 Framing
D4 framing format*
ESF
transparent
jam bit 7*
Trunk conditioning
one-way
two-way*
Fault classes
Circuit Level
(400)
20.1-17
Parameter
Alarm Time
Declare
Clear
Options
0.1 to 60 seconds
0.1 to 60 seconds
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
none
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Clear channels
NOSIG
RBS OFF
enabled*
disabled
Inversion
inverted* (voice)
not inverted (data)
contiguous
non-contiguous
Notes
1. DS-3 II cards support both one-way and broadcast unidirectional super-rate connections.
Table 20.1-8 lists the E3 card configuration parameters. Each parameter has a list of
options, with any default option marked by an asterisk.
20.1-18
(400)
Options
Card Level
Timing and synchronization
Node name
CPSS
Control redundancy
Slot level
Card type
as present
empty
E3
Serial ports
E3 Level
Alarm Time
Declare
Clear
0.1 to 60 seconds
0.1 to 60 seconds
Equalization
0 to 4 dB*
4 to 8 dB
8 to 10 dB
10 to 12 dB
NU bit
0
1*
E2 Level
NU bit
0
1*
(400)
20.1-19
Parameter
Options
E1 Level
E1 Framing
CAS*
CCS
31 channels
Trunk conditioning
one-way
two-way*
NU bit
0000 to 1111*
CRC4 statistics
frame alignment signal statistics*
Circuit Level
20.1-20
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
none
E1 signalling types
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGE RE
LGE EC
R2 signalling type
R2 digital signalling
T1 signalling types
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Inversion
inverted* (voice)
not inverted (data)
Super-rate formats
contiguous
non-contiguous
equidistant
(400)
20.2
20.2.1
20.2.2
Configure the type of application module installed on the card once you have
configured the card type for the slot. See Installation, chapter 13.38 for information
about user-installable application modules.
Table 20.2-1 lists PRI cards and the application modules they support.
(400)
20.2-1
Dual T1
Card
Dual
T1-2
Card
E1 Card
Dual E1
Card
Dual
E1-2
Card
Optical
Ext.
Card
Application
Modules
CCM
DRM
IFM
FT1
SAM
TSM
VCM
You can also configure these options at the card slot level:
ISDN for Dual T1-2, Dual E1, Dual E1-2 and Optical Extension card links
If you select ISDN for a Dual T1-2 card, the system automatically turns on B8ZS and
ESF, and turns off RBS for all circuits in the link. It also sets the signalling type to
NOSIG and sets inversion to DATA.
If you select ISDN for the Dual E1, Dual E1-2 or Optical Extension cards, the system
automatically reconfigures the link. Table 20.2-2 lists the reconfigured link options
with their default ISDN settings.
Table 20.2-2: ISDN Link Default Configuration
Link Option
Default Setting
Signalling type
CCS
Statistics
CRC4
CRC reframing
On
E-bits
On
LIM termination
Twisted pair
Floating
0.8 s
IFM
(1)
On
RAI
(2)
On resynchronization
On BER disable
Disabled
Notes
1. The ISDN framing module is only necessary on the Dual E1 and Optical Extension card.
2. Only for the Dual E1-2 card.
20.2-2
(400)
Note
The Dual E1 and Optical Extension cards require the IFM module to support ISDN
connectivity. The Dual E1-2 card provides ISDN functionality and does not require
the IFM module.
Each Dual E1 or Dual E1-2 card channel has the following options automatically
configured when ISDN is selected for the link.
AS_PRESENT
E1
T1
DUAL_E1
PRIME_RATE
DUAL_T1
DUAL2_E1
X21_PRI_1
X21_PRI_2
DUAL2_T1 MORE
V35_PRI
MPA TTC2M
SK000063
Note
Use the AS_PRESENT softkey if the card is already installed in the slot.
(400)
20.2-3
COMP_CONV/NO_CONV*
SAM
SK000064
To configure Dual T1, Dual E1, Dual E1-2 and Optical Extension card
slot options
CONFIG SLOT <sn> OPTIONS APP_MOD
VOICE_COMP
DELTA
DELTA_G3
NO_MODULE
TRANS
TS24_SIG or ISDN_FRAME
TRANS_G3
SK000065
Note
The TS24_SIG option applies only to the Dual T1 card. The ISDN_FRAME option
applies only to the Dual E1 card.
VOICE_COMP
DELTA
DELTA_G3
NO_MODULE
TRANS
TRANS_G3
DRM
FT1
TS24_SIG
SK000828
To configure ISDN and IFM link options for Dual E1 and Optical Extension cards
CONFIG SLOT <sn-l> OPTIONS MORE ISDN/NON_ISDN or
IFM_ON/IFM_OFF
20.2-4
(400)
20.2.3
AS_PRESENT EMPTY
E3*
SK000066
(400)
20.2-5
20.3
E1-to-T1 Conversion
This chapter introduces E1-to-T1 conversion and explains how to do the following
tasks:
configure a CCM
configure a SAM in a 3600 MainStreet system
enable or disable companding conversion on the TTC2M card
20.3.1
the CCM
the SAM (for the 3600 MainStreet system only)
Single E1 and T1 cards support either a CCM or a SAM but not both, because only
one module can be installed on a card. The TTC2M card performs companding
conversion without an application module.
When analog voice is digitized, the analog waveform is sampled. Each sample, or
pulse, is compared to a non-linear digital scale to obtain a corresponding digital
value. This technique, known as PCM, is used to transmit voice on both E1 and T1
digital links. The process of performing PCM is known as companding.
E1 and T1 companding differ in that each uses its own non-linear digital scale (or
companding law). Voice is digitized according to A-law for transmission on E1 links
and to Mu-law for transmission on T1 links.
The SAM is used to support super-rate T1-to-E1, T1-to-T1 and E1-to-E1
cross-connections. In a locally controlled system, you must configure a SAM to
support super-rate connections in:
Single T1 cards
Single E1 cards, if the super-rate circuit includes channels on either side of TS16
(timeslot 16)
(400)
20.3-1
20.3.2
Note
You cannot configure a slot with both a CCM and a SAM because only one module
can be installed on a card. If you configure a slot for a SAM, the COMP_CONV
softkey will not appear. To access the COMP_CONV softkey, you must select SAM
then NO_MODULE.
20.3.3
Single T1 cards
Single E1 cards, if the super-rate circuit includes channels on either side of TS16
(timeslot 16)
Note
In a switching shelf controlled system, Single T1 and E1 cards do not need a SAM for
super-rate connections. Dual E1 and T1 cards never need a SAM for super-rate
connections.
20.3-2
(400)
For the purposes of the SAM, circuits and timeslots are not synonymous.
A circuit is a device internal to the node. Single T1 and E1 cards are assigned
When two super-rate circuits (see chapter 20.15) are cross-connected, timeslots from
one link map onto timeslots on another. First the master circuits are cross-connected,
mapping their respective timeslots to one another. Then, each successive circuit in
one super-rate bundle is cross-connected to each successive circuit in the other
super-rate bundle, mapping their respective timeslots to one another.
Since super-rate bundles may include non-contiguous circuits and circuits do not
always correspond to timeslots in a one-to-one correspondence, delay equalization
problems can occur between respective timeslots of the two super-rate bundles that
are being connected. This delay equalization problem will prevent the super-rate
connection from functioning properly.
The SAM solves this problem by ensuring that, at cross-connect time, each circuit
that is part of a super-rate bundle has its respective timeslot mapped onto a timeslot
with equal delay.
There are three types of super-rate bundle configurations (see chapter 20.15). In the
case of contiguous super-rate bundles, delay problems are easily resolved prior to
connection time by following the recommended configuration guidelines contained
in this section. For the non-contiguous or equidistant super-rate bundles, delay
problems become subject to the particular circuit arrangement at cross-connect time
and may still exist after SAM configuration due to the numerous circuit arrangement
possibilities. In this case, it may be necessary to choose an alternate SAM
configuration or reconstruct the super-rate bundles with a different circuit ordering
to solve the delay problem.
(400)
20.3-3
The following is a list of recommended SAM configurations. Configure the SAM as:
Circuits in a super-rate bundle follow the ordering outlined in Table 20.3-1. For
example, a 3 circuit contiguous super-rate bundle starting with circuit 15 on an E1
link configured for 31_Chan framing will contain, in order, circuits 15, 31 and 16.
Table 20.3-1: Super-rate Timeslot-to-Circuit Correlation
Switching Order of Circuits
Timeslot 1 2 3...15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
Framing
Type
NORMAL SAM
(See chapter 20.15 for details.)
CCT SAM (1)
E1 Circuit 1 2 3...15 S 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 (2)
E1 Circuit 1 2 3...15 31 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
(2)
T1 Circuit 1 2 3...15 16 17 18 19 20 21 22 23 24
CAS/CCS
31_CHAN (3)
D4/ESF
TS SAM (1)
E1 Circuit 1 2 3...15 S 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 (2)
CAS/CCS
31_CHAN (3)
T1 Circuit 1 2 3...15 16 17 18 19 20 21 22 23 24
D4/ESF
CONTIGUOUS
(4)
E1 Circuit 1 2 3...15 S 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
CAS/CCS
E1 Circuit 1 2 3...15 31 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30
31_CHAN (3)
Notes
1. A maximum of 24 E1 circuits can be cross-connected to a T1.
2. If connecting the italicized E1 circuits to T1 links or the SAM is residing on the E1 card, the italicized
circuits can only be cross-connected on a circuit-by-circuit basis. (For example, they cannot be
connected as part of a super-rate bundle).
3. If 31_CHAN E1 framing is used, the CCT and CONTIGUOUS options will block certain super-rate
connections involving circuit 31. When the CCT option is selected, all connections involving a
super-rate bundle that includes circuit 31 will fail due to unavoidable delay problems. Similarly, when
the CONTIGUOUS option is selected, all connections involving a super-rate bundle that spans circuit
31 will fail due to unavoidable delay problems.
4. The CONTIGUOUS option is not available for SAMs on a T1 card.
20.3-4
(400)
Note
A slot cannot be configured to have both a CCM and a SAM because only one
module can be installed on a card. If COMP_CONV is selected, the SAM softkey will
not appear. To access the SAM softkey, you must select NO_CONV.
NO_MODULE*
NORM
TS
CCT
CONTIGUOUS
SK000067
20.3.4
NONE*
A_LAW
MU_LAW
SK000744
(400)
20.3-5
20.4
Voice Compression
This chapter introduces voice compression on Dual T1, Dual T1-2, Dual E1,
Dual E1-2 and Optical Extension cards and explains how to:
20.4.1
MainStreet node
24 DS-0s
24 DS-0s
Network
Dual T1-2
with
VCM2
Forty-eight 32 kb/s
ADPCM compressed
channels
5190
Note
At the time of publication, the VCM2 was not supported on the 3600 MainStreet
series bandwidth managers. Contact your local Newbridge representative for
information about availability.
(400)
20.4-1
MainStreet node
30 DS-0s
30 DS-0s
Network
Dual E1
with
VCM3
Sixty 32 kb/s
ADPCM compressed
channels
5191
The type of VCM needed to do voice compression depends on the type of card and
the type of signalling. Table 20.4-1 lists VCM requirements. All VCMs can compress
either voice or G3 fax voice-band signals. Figures 20.4-3 and 20.4-4 show delta and
transitional signalling through compressors, subframes and sub-channels for a
Dual T1-2 card with an installed VCM.
Table 20.4-1: VCM Requirements
Card Type
Dual T1 card
VCM or VCM3
VCM3
VCM2
VCM2
VCM or VCM3
VCM3
VCM2
VCM2
VCM or VCM3
VCM3
20.4-2
(400)
ADPCM
64k PCM
Site 1
PBX
DET
Dual Card
T1-2
Card
with
with
VCM Module
module
Site 2
Primary
Rate
Rate Card
card
Primary
Rate card
Dual T1-2
card with
VCM module
PBX
VCM Module
(Transcoder Device)
Primary
Rate
Circuit n
Primary
Rate
Circuit n1
Primary
Rate
Circuit n2
Primary
Rate
Circuit n3
Primary
Rate
Circuit n4
Primary
Rate
Circuit n5
Delta
Dual T1-2 Circuit
S1
S2
S3
S4
S5
S6
S7
S8
S9
S10
S11
M44 ADPCM
Sub-frame
DX connection
Primary Rate line
6638
(400)
20.4-3
The M48 or M60 transitional signalling provides Dual T1, Dual T1-2, Dual E1, Dual
E1-2 and Optical Extension cards with access to 32 compressors. Each transitional
signalling compressor can compress 2 DS0s.
The compressed voice channels can be carried on any 64 kb/s codirectional circuit.
They are supported by: T1, Dual T1, Dual T1-2, E1, Dual E1, Dual E1-2, Optical
Extension, MPA, X.21 PRI, V.35 PRI, DS-3, DE3 and SE3 cards. M48 and M60
compressed channels can be connected to an SRS but M44 and M55 channels cannot.
Figure 20.4-4: Transitional (M48/M60) ADPCM Subframe
64k PCM
ADPCM
64k PCM
Site 2
Site 1
PBX
DET
Dual Card
T1-2
card
with
with
VCM Module
module
Primary
Rate
Rate Card
card
Primary
Rate card
Dual T1-2
card with
VCM module
PBX
VCM module
(Transcoder Device)
Dual T1-2 circuit
S1
S2
Primary
Rate
Circuit n
DX connection
M48 ADPCM
Sub-frame
6639
20.4.2
20.4-4
(400)
Figure 20.4-5 shows the compressor connections of a Dual T1 card configured for
transitional signalling. Displays for the Dual T1-2, Dual E1, Dual E1-2 and Optical
Extension cards are similar to the Dual T1 display.
Figure 20.4-5: Viewing Compressor Connections
3600 MainStreet
Circuit
1117-H1-00
Name
Toronto:A
Alarms:1
Status
DT1_Compressor
DT1_Compressor
DT1_Compressor
DT1_Compressor
DT1_Compressor
Connected
Configured
Configured
Configured
Configured
A1-X1
A1-X2
A1-X3
A1-X4
A1-X5
Type
11-May-1997
8:35a
1-SHOW_CCT
6-
2-NAME
7-
38-CANCEL
49-QUIT
50-
Figure 20.4-6 shows the sub-channel connections of a Dual T1 card with a DS0
connected to a compressor. Displays for Dual T1-2, Dual E1, Dual E1-2 and Optical
Extension cards are similar to the Dual T1 display.
(400)
20.4-5
Name
A1-S1-11
A1-S1-10
A1-S1-09
A1-S1-08
A1-S1-07
A1-S1-06
A1-S1-05
A1-S1-04
A1-S1-03
A1-S1-02
A1-S1-01
A1-S01-02
A1-S01-01
1117-H1-00
Toronto:A
Alarms:1
Type
Status
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
T1_SUBCHAN
Connected
Connected
Connected
Connected
Configured
Configured
Configured
Configured
Configured
Configured
Configured
Configured
Configured
11-May-1997
8:35a
1-SHOW_CCT
6-
20.4.3
2-NAME
7-
38-CANCEL
49-QUIT
50-
For transitional signalling, configure the DS0 that carries the compressed
channel with default data equal to all zeroes (eight 0s). See the procedure To
configure the DS0 that carries the compressed channels.
2.
Configure the Dual T1, Dual T1-2, Dual E1, Dual E1-2 or Optical Extension card
for delta or transitional signalling (either voice or G3 Fax voice band). This step
defines the voice compression algorithm and enables the compressors. See the
procedure To set the compressor type as delta or transitional signalling.
3.
Connect a subframe from the Dual T1, Dual T1-2, Dual E1, Dual E1-2 or Optical
Extension card compressor to a DS0 on the card that will carry the compressed
channels. See the procedure To connect the subframe to a DS0.
4.
Connect a voice channel from the Dual T1, Dual T1-2, Dual E1, Dual E1-2 or
Optical Extension card to a sub-channel on the VCM. See the procedure To
connect a voice channel to the VCM sub-channel.
20.4-6
(400)
Description
Circuit
Protection
Companding
Law
Connection
Robbed Bit
Signalling
SRS
Zero Code
Suppression
(T1)
DELTA
DELTA_G3
TRANS
TRANS_G3
SK000068
Note
When configured for TRANS_G3, only the compressed channels use G3 Fax voice
band lookup tables. Uncompressed circuits are not affected. When a Dual T1-2,
Dual E1, Dual E1-2 or Optical Extension card is configured for transitional
signalling, only the circuits connected to a sub-channel are compressed.
(400)
20.4-7
Note
The circuit to which you are connecting (x-sn-cc, x-sn-l-cc, E3id-E1id-cc or
x-sn-SRS-dd) must not be on the same card as the compressor (x-sn-Xt).
For Release 6 and newer versions of system software, the sn-St in <x-sn-St-vv>
refers to the slot and compressor number of the card on which the VCM resides. For
Release 5.x, these variables refer to the slot and timeslot of the card to which the
compressor connects.
For example, assume the node in Figure 20.4-7 is a 3600 MainStreet node with a
Dual T1 card configured for transitional ADPCM in slot 2, a T1 card in slot 5 and the
subframe connection <A2-X7> TO_CIRCUIT <A5-2>. The softkey sequence for the
Link A subframe connections is as follows.
For Release 6 and newer versions of system software:
CONFIG CONNECT <A2-A-5> TO_CIRCUIT <A2-S7-1>
20.4-8
(400)
MainStreet node
Uncompressed
voice circuit on link A
Dual T1
card
4 5 6
T1 card
VCM3
24 voice circuits
Network
24 voice circuits
1
2
3
24
voice
circuits
Network
14 15 16
Sub-frame
Compressor
Uncompressed
voice circuit on link B
S2 (5)
S1 (15)
Sub-channels
5192
(400)
20.4-9
20.5
Timeslot 24 Signalling
This chapter explains how to configure timeslot 24 signalling on Dual T1 and Dual
T1-2 cards.
20.5.1
23 24
Reserved for
signalling of
circuits 1 to 23
4694
SIG24 is compatible with both ESF and D4 framing and introduces no signalling
distortion. SIG24 can pass regular voice signalling (such as off-hook and ringing),
OOS codes and any of the signalling types that can be configured for timeslots
1 to 23 (see chapter 20.11). Both standard-rate (64 kb/s) and super-rate circuits are
supported.
To support timeslot 24 signalling, the Dual T1-2 card must be equipped with a DRM
and the Dual T1 card with a TSM. As timeslot 24 signalling is a link option for the
Dual T1-2, each link can be independently configured to support timeslot 24
signalling or RBS. Timeslot 24 signalling is a slot-level option for Dual T1 cards.
(400)
20.5-1
Note
A Dual T1-2 card can be equipped with either a DRM or a VCM. A Dual T1 card can
be equipped with either a TSM or a VCM. Dual T1 cards in 3664 MainStreet systems
do not support TSMs, DRMs or timeslot 24 signalling.
20.5.2
20.5-2
(400)
20.6
20.6 Framing
Issue 1, November 1997
Framing
This chapter explains how to configure framing for PRI cards.
20.6.1
20.6.2
DS-3
card
Level
Framing
Option
DS3
Transmit as received
AUTO*
DS3
M13
M13
DS3
C-bit parity
C_BIT
DS1
D4
D4_FRAMING*
DS1
ESF
ESF
(400)
20.6-1
20.6 Framing
Issue 1, November 1997
M13 framing
This format is the established standard for public networks. The M13 process first
combines four DS1 lines into a DS2 bit stream at 6.312 Mb/s and adds 150 kb/s of
overhead for bit stuffing to accommodate variations in the clock rates of incoming
T1 links. Then, seven DS2 streams are combined into one DS3, with extra bits added
to bring the DS3 rate to 44.736 Mb/s.
D4 framing
A D4 frame consists of 193 bits: 24 timeslots containing 8 bits each and one framing
bit. A D4 superframe consists of 12 frames. Figure 20.6-1 shows the D4 superframe
format.
Figure 20.6-1: D4 Framing Format
D4 Superframe
12 D4 frames
10
11
12
2316 bits
12 Framing bits
Framing pattern =
100011011100
Frame 1
Framing bit
Timeslot 1
Timeslot 2
Timeslot 24
8 bits
193 bits
D4 Format
8137
ESF framing
This framing format creates superframes consisting of 24 D4 frames. Figure 20.6-2
shows the ESF format.
20.6-2
(400)
20.6 Framing
Issue 1, November 1997
24 D4 frames
21
22
23
24
4632 Bits
24 bits: 6 framing (2 kb/s)
6 error checking (2 kb/s)
12 FDL (4 kb/s)
7174
Note
In 3664 MainStreet systems, connections to D4- and ESF-framed T1 cards are
restricted to the first 12 channels.
C_BIT
M13
AUTO*
SK000069
To configure the DS-1 framing format for T1, Dual T1 and DS-3 or DS-3 II cards
CONFIG SLOT <n> or <sn> or <sn-l> OPTIONS ESF/D4_FRAMING*
20.6.3
(400)
20.6-3
20.6 Framing
Issue 1, November 1997
Note
When making super-rate connections (connections that occupy more than one
channel on a primary rate link) to an E1 link, timeslot 16 (circuit 31) is not used if
CAS or CCS is selected. Timeslots 1 through 15, then 17 through 31 are used (see
Table 20.3-1 in chapter 20.3). Timeslot 16 is used only if 31_CHAN is selected.
The framing type cannot be changed if any circuit on the card is connected.
Dual E1, Dual E1-2 and Optical Extension cards do not support the X.21 NTU
framing pattern.
Dual
E1,
Dual
E1-2
Cards
E3 Card
Optical
Ext.
Cards
CAS
CCS
Framing
31 channels
X.21 NTU
Option
CAS*
CCS
(1)
31_CHAN
X21_NTU
Notes
1. The 31 channel framing option is not available on E1 cards in 3664 MainStreet systems.
Table 20.6-3 shows the timeslot-to-circuit designation for these framing options. A
circuit is a device internal to the node. E1 cards are assigned circuits 1 to 31. A
timeslot is a channel on the physical E1 link external to the node. E1 links are made
up of timeslots 0 to 31, respectively.
Note
In 3664 MainStreet systems, connections to CCS- and X.21 NTU-framed E1 cards are
restricted to the first 15 channels and channel 31 (timeslot 16). Connections to
CAS-framed E1 cards are restricted to the first 15 channels.
20.6-4
(400)
20.6 Framing
Issue 1, November 1997
Frame Type
CAS
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 S 16... 28 29 30
CCS
31 Channels
X.21_NTU
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 31 16... 28 29 30
Notes
1. F = framing; S = signalling
Common channel signalling, 31 channels and X.21 network termination unit provide
31 configurable circuits, but they treat circuit 31 differently.
CAS framing
Timeslot 16 is used for CAS and is not user-configurable. Timeslot 0 is used for
framing. The rest of the timeslots are used for information. Timeslots 1 through 15
correspond to circuits 1 through 15 and timeslots 17 through 31 correspond to
circuits 16 through 30.
CCS framing
Timeslot 16 corresponds to circuit 31, which can be configured as an additional
64 kb/s data channel (typically for the transport of CCS messages). The rest of the
timeslots are labelled as in CAS: timeslots 1 through 15 correspond to circuits 1
through 15 and timeslots 17 through 31 correspond to circuits 16 through 30. The 31
circuits are treated equally. Timeslot 0 is used for framing.
31 channels framing
This framing pattern has the same designation of timeslots to circuits as CCS.
However, when making super-rate connections (connections that occupy more than
one channel on a primary rate link) to an E1 link, the system does not skip timeslot
16 (the 31st circuit); timeslots 1 through 31 are used consecutively (see Table 20.6-3).
Timeslot 0 is used for framing.
(400)
20.6-5
20.6 Framing
Issue 1, November 1997
Order
CAS
CCS
Timeslot
Circuit
15 17 18 19
15 16 17 18
31 Channels
Timeslot
Circuit
15 16 17 18
15 31 16 17
CAS*
CCS
X.21_NTU
31_CHAN
SK000070
Note 1
You cannot select FRAME_TYPE if any circuits are connected.
Note 2
The X.21_NTU option is available only for E1 cards
To configure framing for Dual E1, Dual E1-2 and Optical Extension cards
CONFIG SLOT <sn-l> OPTIONS PHYSICAL FRAME_TYPE
CAS
CCS
31_CHAN
SK000705
20.6-6
(400)
20.6.4
20.6 Framing
Issue 1, November 1997
The X.21 PRI card uses Frame 1-type framing to provide up to 30 circuits without
The X.21 PRI-2 card is normally configured for Frame 2 type framing. The Frame 1
type option is provided for backwards compatibility with older X.21 PRI cards.
(400)
20.6-7
20.7
Line Length
This chapter explains how to configure line length for:
20.7.1
(400)
20.7-1
OPTIONS
PHYSICAL
LINE_LNGTH
SHORT*
MEDIUM
LONG
SK000071
20.7.2
SHORT*
LONG
SK000072
20.7-2
(400)
20.8
20.8.1
DS-3 and
DS-3 II
cards (1)
Framing
Option
Transparent
TRANSP
B8ZS
Jam Bit 7
JB7*
Notes
1. Zero code suppression is done at the DS1 level on the DS-3 or DS-3 II card.
Caution
The same type of zero code suppression must be configured at both ends of a link.
Transparent framing
The transparent option means that the system uses no zero suppression at the slot
level. Cross-connected devices must use a protocol designed to ensure a sufficient
ones density pattern to avoid line synchronization problems.
(400)
20.8-1
Caution
The transparent setting should be used with caution as network equipment could
lose synchronization if the ones density requirement is not satisfied.
20.8.2
ZERO_SUPPR
TRANSP
B8ZS
JB7*
SK000073
20.8-2
(400)
TRANSP
JB7*
SK000074
(400)
20.8-3
20.9
Trunk Conditioning
This chapter introduces trunk conditioning for PRI cards and explains how to
configure trunk conditioning.
20.9.1
The transmit direction is defined by the transmit path from the aggregate
Table 20.9-1 lists the types of trunk conditioning supported. The default trunk
conditioning direction for all card types is two-way.
Table 20.9-1: Aggregate Interface Card Trunk Conditioning
Card Type
T1
Two-way
E1
(1)
Dual T1
Dual E1
MPA
Optical Extension
One-way
(400)
(1)
(1)
20.9-1
Card Type
One-way
Two-way
TTC2M
DS-3 or DS-3 II
E3
Notes
1. When configured for unidirectional circuits, PRI cards support only one-way trunk conditioning.
2. The 64 kb/s Codirectional card performs trunk conditioning when it detects a Loss of Incoming Signal
condition.
Note
Regardless of the type of trunk conditioning configured, two-way trunk
conditioning is applied to aggregate interface card circuits cross-connected to CPSS
circuits and voice compression subframes.
20.9-2
(400)
Link Faults
Signalling Path
Information Path
Framing Alarm
AIS
Framing Error Rate
Exceeded
Failed State
64 kb/s
Codirectional
Failed State
T1
Red Alarm
Framing Alarm
Failed State
MPA
Framing Alarm
Failed State
Loopback Detected
Clock Speed Mismatch
TTC2M
Framing Alarm
Framing Error Rate
Exceeded
Failed State
LIS
Multi-frame Alarm
Incoming TS16 AIS
No change
TTC2M
Multi-frame Alarm
No change
Distant Alarm
TS16 Distant Alarm
No change
No change
T1
Yellow Alarm
No change
No change
Distant Alarm
No change
No change
MPA
Distant Alarm
No change
No change
TTC2M
Distant Alarm
No change
No change
Notes
1. For TSM-equipped Dual T1 or DRM-equipped Dual T1-2 only.
2. One-way trunk conditioning does not result in the information or the signalling path being broken in
either direction, because the fault lies in the aggregate interface card circuit receive path.
(400)
20.9-3
Table 20.9-3: One-way Trunk Conditioning Signalling and Information Path Codes
Code
Code Transmitted on
Signalling Path
Code Transmitted on
Information Path
All zeros
Notes
1. If the fault signalling configured for this circuit is seized, the system does not transmit an idle code
first, as is the case for two-way trunk conditioning.
2. If the connected circuit is an aggregate interface card circuit configured for DDS rate adaption, an
ASC is transmitted. If it is not configured for DDS, all ones are transmitted.
Figure 20.9-1 shows one-way trunk conditioning for Group 1 link faults.
Figure 20.9-1: One-way Trunk Conditioning (Group 1)
If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Direction of transmission
Fault
If not primary rate circuit,
all 0s.
If primary rate circuit not
carrying a circuit
using DDS, all 1s.
If primary rate circuit
carrying a circuit using
PRI card
Connected circuit
Primary rate circuit
DDS, DDS abnormal
station code (ASC).
Signalling
Information
Direction of transmission
3715
20.9-4
(400)
Figure 20.9-2 shows one-way trunk conditioning for Group 2 link faults.
Figure 20.9-2: One-way Trunk Conditioning (Group 2)
If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Direction of transmission
Connected circuit
Signalling
PRI card
Fault
Direction of transmission
Information
3716
Non-Aggregate
Interface Card
Connected Circuit
Aggregate
Interface Card
Connected Circuit
To Far End
Code Transmitted on
Signalling Path
Code Transmitted on
Information Path
All zeros
Notes
1. Signalling is driven to idle for 2.5 seconds and then fault signalling is transmitted as configured. If
fault signalling is configured as Out-of-service, A, B or C signalling is not driven to idle first.
2. If the connected circuit is an aggregate interface card circuit configured for DDS rate adaption, an
ASC is transmitted. If it is not configured for DDS, all ones are transmitted.
(400)
20.9-5
Signalling
Fault
Direction of transmission
PRI card
Fault
Direction of transmission
Signalling
2.5s
SEIZED
or
IDLE
Signalling
Information
Fault
3714
20.9-6
(400)
20.9.2
Set one-way or two-way trunk conditioning for the link. See section 20.9.3.
2.
Configure the trunk conditioning fault class for the link. See section 20.9.5.
3.
Enable fault signalling for each circuit on the link. See section 20.10.2.
For all aggregate interface cards, you can enable trunk conditioning for certain
groups of link faults called fault classes. Enabling all the fault classes on the link
enables trunk conditioning on that link.
20.9.3
(400)
20.9-7
Note
The MORE option is not applicable for the 64 kb/s Codirectional and the
TTC2M cards.
20.9.4
20.9-8
(400)
Alarm Description
Framing Alarm
Incoming AIS
Multi-frame Alarm
Incoming TS16 AIS
Red Alarm
Distant Alarm
Incoming TS16 AIS
Yellow Alarm
Failed
Failed State
Failed State
Error
Loopback (5)
CPSS Loopback
activated
In-band Loopback
activated
On-fault Loopback
activated
CPSS Loopback
activated
TS24 Loopback
activated
On-fault Loopback
activated
Frame/Red (1)
Distant/Yellow (3)
Notes
1. For E1, MPA, TTC2M, X.21 and V.35 PRI cards, this is the Frame fault class. For DS-3 or DS-3 II and T1 cards, it is the Red
fault class.
2. TS24 alarms apply only to a Dual T1 with TSM installed or Dual T1-2 with DRM.
3. For CEPT cards, this is the Distant fault class. For NA cards, it is the Yellow fault class.
4. Supported on E1, Dual E1 and Optical Extenstion cards only.
5. Different types of loopback alarms apply to the various PRI cards depending on the card type. See chapter 20.14 for details.
(400)
20.9-9
20.9.5
T1 Cards
E1 Cards
MPA
Cards
TTC2M
Cards
X.21 and
V.35
Cards
DS-3 and
DS-3 II
Cards
Frame/Red
Distant/Yellow
Failed
Error
CSU Loopback/Loopback
Fault Class
FRAME_OFF/
FRAME_ON*
DIST_OFF/
DIST_ON*
FAILED_OFF/
FAILED_ON*
LPBK_OFF/
LPBK_ON*
SK000693
FRAME_OFF/
FRAME_ON*
SAI_OFF/
SAI_ON*
FAILED_OFF/
FAILED_ON*
ERROR_OFF/
ERROR_ON*
SK000746
20.9-10
(400)
MORE
FAULT_HNDL
TRUNK_COND
RED_OFF/
YELLOW_OFF/
RED_ON* or
YELLOW_ON* or
FRAME_OFF/ DISTANT_OFF/
FRAME_ON*
DISTANT_ON*
SK000078
where the second sn-l indicates a Dual T1-2 or Dual E1-2 card link
(400)
20.9-11
20.10
Fault Signalling
This chapter describes how to configure fault signalling for PRI cards.
20.10.1
PBX
T1
Link
fault
Network
Phone
Fault signalling
seized
5418
You can configure the type of fault signalling independently for each aggregate
interface card circuit. Table 20.10-1 lists the fault signalling types and defaults for
each aggregate interface card.
Note
The 64 kb/s Codirectional card and the DS0-DP and OCU-DP channel units support
fault signalling, and the procedures in this chapter also apply to them. Certain voice
cards and channel units also support fault signalling (see chapter 21.8).
Of the channel units, only the E&M, DS0-DP and OCU-DP channel units respond to
OOS-A.
When you program a super-rate connection for OOS A, B or C, the first DS0 (the
master circuit) detects the fault condition and transmits the appropriate OOS code
(see chapter 20.9).
When a link carrying a channel that is being compressed fails, the fault signalling
sent to the far end is always seized (regardless of the fault signalling configured).
(400)
20.10-1
Idle(1)
OOS A
OOS B
OOS C (2)
None
Single T1
card
(4)
(5)
(6)
Dual T1
card
(4)
(5)
Single E1
card
(7)
(7)
(8)
Dual E1
card
Optical
Extension
card
MPA card
Card or
Channel
Unit
CMI
NIS
In-use
DATA
TTC2M
card
MOS(3)
X.21 and
V.35 PRI
card
DS-3 or
DS-3 II card
(9)
(10)
(11)
SE3 and
DE3 card
(7)
(7)
(12)
64 kb/s
Codirection
al card
(13)
(13)
DS0-DP
channel
unit
Notes
1. Idle = default.
2. Only one end of a circuit may be configured for OOS-C fault signalling.
3. MOS = default.
4. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or
E&M circuits.
5. Applies to DS0s (on ESF-framed DS1s only) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or E&M circuits.
6. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to data or any voice circuits.
7. Applies to timeslots (on CAS-framed links only) connected to data or any voice circuits.
8. Applies to timeslots (on either CCS- or 31 Channel-framed links) connected to data or any voice circuits.
9. Applies to DS0s (on either D4- or ESF-framed DS1s) connected to data or E&M circuits.
10. Applies to DS0s (on ESF-framed DS1s only) connected to data or E&M circuits.
11. Applies to DS0s (on either D4- or ESF-framed DS1s) connected to data or any voice circuits.
12. Applies to timeslots (on CAS-, CCS- or 31 Channel-framed links) connected to data or any voice circuits.
13. Not applicable for timeslots configured for R2D signalling.
20.10-2
(400)
OOS C (1)
OOS A
OOS B
0100(01) (2)
0110(n/a)
Yellow/Distant Alarm
(2)
0110(n/a)
Dual T1
0100(01)
Dual E1
1111
0110
Yellow/Distant Alarm
Dual E1
1111
0110
Yellow/Distant Alarm
1111
0110
Yellow/Distant Alarm
MPA
1111
0110
Yellow/Distant Alarm
DS-3
0100(01) (2)
0110(n/a)
Yellow/Distant Alarm
1111
0110
Yellow/Distant Alarm
64 kb/s Codirectional
1111
0110
Notes
1. When OOS-C is selected for a DS0 and that circuit connection becomes unavailable, a yellow alarm
is generated on the DS1 circuit for a T1 DS0; a distant alarm is generated for an E1 DS0.
2. For ESF-framed DS1s, all four ABCD signalling bits are defined. For D4-framed DS1s, only the AB
signalling bits (shown in brackets) are defined.
(400)
20.10-3
20.10.2
Restrictions
The following restrictions apply.
For D4-framed T1 circuits connected to E&M or data circuits, you can select
SEIZED, IDLE, OOS-A or OOS-C.
For ESF-framed T1 circuits connected to E&M or data circuits, you can select
20.10-4
(400)
SEIZED
IDLE*
OOS-B
OOS-A
NONE
OOS-C
SK000075
IDLE*
IN_USE
NIS
NONE
DATA
SK000745
MOS*
CMI
SK000076
OPTIONS
PHYSICAL
UNUSD_FSIG
SEIZED
IDLE
OOS-A
OOS-B
NONE
OOS-C
SK000077
(400)
20.10-5
20.10-6
(400)
20.11
20.11.1
LGS-LS
Link
fault
Node A
PBX-1 T1
T1
1
T1
2
T1
Node B
T1
T1
3
E1
1
LGS-LS
Node C
E1
E1
2
E1
3
E1 PBX-2
Seized: 1111
Idle: 0101
5367
For all aggregate interface card circuits (except compressed voice circuits), configure
the custom fault signalling bit patterns independently for each circuit on a link. The
following fault signalling codes are available.
CODE_1 is the code transmitted on the signalling path when the circuit is
configured to transmit idle fault signalling. The default is 0000.
CODE_2 is the code transmitted on the signalling path when the circuit is
(400)
20.11-1
The CODE_1 and CODE_2 bit patterns represent the settings of the ABCD signalling
bits. For D4-framed DS1s, only the AB bits are defined. For ESF-framed DS1s, E1s
and X.21 and V.35 PRIs, all four ABCD bits are defined.
If you change framing on a DS1 from D4 to ESF after configuring CODE_1 or
CODE_2, the configured AB bits are copied into the CD bit positions (that is, ABAB
is transmitted). If you change framing on a DS1 from ESF to D4 after configuring
CODE_1 or CODE_2, only the configured AB bits are transmitted; the CD bits are
ignored.
If an E1 circuit is configured for T1 signalling, you configure only the AB bits; the C
and D bits are fixed at 0 and 1, respectively.
Caution
Never set CODE_1 (idle) and CODE_2 (seized) to all zeros. An all-zero setting can
cause multiframe problems in an E1 network.
Table 20.11-1 lists common seized and idle codes for each signalling type supported
by the system except the TTC2M card. See section 20.12.4 for information about
TTC2M card idle and in-use codes.
Table 20.11-1: Fault Signalling Codes Seized and Idle for PRI Cards
Seized Code
Idle Code
Signalling
E1, E3, MPA, Opt.
Ext., X.21 and V.35
PRI (1)
T1 and G.703
Codir (2)
DS-3 and
DS-3 II
T1 and G.703
Codir (2)
DS-3 and
DS-3 II
DPO/DPT
1111
1111
0000
0000
E&M (T1/NA)
0101
1111
11
1101
0000
00
E&M (E1/UK)
1111
0101
0000
1101
LGE_EC
0101
0101
1101
1101
LGE_GS
0000
0000
00
0101
0101
01
LGE_LCDC
0101
0101
1101
1101
LGE_LS
1111
1111
11
0101
0101
01
LGE_RE
0101
0101
1101
1101
LGS_CBW
1101
1101
1101
1101
LGS_EC
1001
1001
1101
1101
LGS_GS
0101
0101
01
1111
1111
11
LGS_LCDC
1001
1001
1101
1101
LGS_LS
0101
0101
00
0101
0101
01
LGS_PLAR
0000/0101
0000
00
0000/0101
1111
00
LGS_RE
1101
1101
1101
1101
R2D E&M
0011
0011
1011
1011
20.11-2
(400)
Notes
1. When T1 signalling is configured on E1 timeslots, the last two bits (C and D) are set to 0 and 1,
respectively.
2. Codes shown are for ESF-framed DS1s (which use all four ABCD bits). For D4-framed DS1s, only
the first two bits (AB) are transmitted.
20.11.2
CODE_1 for the code transmitted on the signalling path when the circuit is
configured to transmit Idle fault signalling (the default is 0000)
CODE_2 for the code transmitted on the signalling path when the circuit is
CODE_1
CODE_2
<code> <code>
DATA
<data>
SK000079
where
code is a four-digit binary code
data is an eight-digit binary code
(400)
20.11-3
SEIZED
IDLE
OOS-A
OOS-B
NONE
OOS-C
MORE
CUSTOM
CODE_1 CODE_2
DATA
where
code is a four-digit binary code
data is an eight-digit binary code
20.11-4
(400)
20.12
PRI Signalling
This chapter describes the implementation of signalling for the following PRI cards:
20.12.1
cards
TTC2M card
(400)
20.12-1
Note
Optical Extension cards use the same signalling types as the E1 cards.
E1
Card
MPA
Card
X.21
and
V.35
Card
DS-3
and
DS-3 II
Card
E3
Card
64 kb/s
Codir
Card
Transparent
SIG
Clear channel
NoSIG
E&M
E+M
Continuous E&M
E+M_B
Signalling Type
Option
LGS Remote
Extension
LGS
REM_EXT
LGS EC
LGS PLAR
E1_SIG or
T1_SIG) LGS
PLAR or
PLAR_D3
LGE Remote
Extension
LGE
REM_EXT
LGE EC
LGS LS
LGS GS
LGE LS
LGE GS
R2 digital signalling
R2D_E+M
RBS
RBS
Terminate
TERMINATE
20.12-2
(400)
Transparent
Clear channel
Clear channel
E&M
E&M
E&M
LGS PLAR
Notes
1. DE3 or SE3 to DS-3 or DS-3 II connections are supported only by NoSIG connections.
2. Continuous E&M is used to convert a proprietary signalling type to Newbridge standard E&M
signalling. Continuous E&M is supported if the E1 link is configured for CAS.
3. LGS PLAR is equivalent to D4 PLAR signalling as specified in the 1985 Addendum to PUB 43801.
4. PLAR D3 is equivalent to D3 PLAR signalling as specified in the 1982 Addendum to PUB 43801.
Figure 20.12-1 shows an example of how the signalling type for the T1 and E1 circuits
must be configured at the node before connecting them. At the London node, the T1
circuit is configured as type LGS GS (for the device connected in New York) and the
E1 circuit as type LGE EC (for the device type connected in Paris). The New York and
Paris nodes do not need to configure the signalling type.
Figure 20.12-1: Example of Signalling Type Configuration
New York
Paris
London
LGS-GS
T1
36120
MainStreet node
T1
E1
3600
MainStreet node
E1
LGE-EC
3645
MainStreet node
5419
PLAR D3 signalling
When LGS PLAR is selected, the system provides signalling according to the 1985
Addendum to PUB 43801. This Addendum specifies support for D4 channel banks
and inverts the state of the signalling bits specified in the 1982 Addendum. When
LGS PLAR_D3 is selected, the system provides signalling according to the 1982
Addendum to PUB 43801. PLAR_D3 signalling supports third-party nodes (such as
D3 channel banks) that still comply with the 1982 Addendum.
(400)
20.12-3
In Figure 20.12-1, the New York node is a third-party D3 channel bank connected to
a voice interface configured for LGS PLAR. The 3645 MainStreet node in Paris is also
connected to an LGS PLAR voice interface. At the London node, the T1 is configured
for PLAR_D3 signalling (to accommodate the 1982 Addendum-compliant D3
channel bank in New York) and the E1 is configured for PLAR signalling (to
accommodate the 1985 Addendum-compliant 3645 MainStreet node in Paris).
R2 digital signalling
If you are connecting an E1, Dual E1, Dual E1-2 or Optical Extension card circuit
using R2 digital signalling to an E&M circuit, you must configure the primary rate
circuit as type R2D_E+M.
RBS
You can configure RBS for T1 and DS-3 or DS-3 II cards. RBS is usually used to pass
ABCD signalling. When RBS is enabled, the least significant bit (bit 8) of every
channel in frames 6 and 12 (if D4 framing is used) or in frames 6, 12, 18 and 24 (if ESF
framing is used) is overwritten with signalling information.
You cannot use RBS under the following conditions.
If a DCC, DNIC or 2B1Q Line card circuit with a bandwidth of 64 kb/s or greater
When you configure a Dual T1-2 card for ISDN, the system automatically turns RBS
on.
20.12-4
(400)
20.12.2
SIG for transparent, where signalling is passed without being tested for
compatibility with the signalling type at the far end (default for DS-3, DS-3 II and
T1 cards, and Dual T1 cards without TSMs or Dual T1-2 cards without DRMs)
NoSIG for clear channel, where a 64 kb/s clear channel is created without
signalling
E+M for E&M
LGS LS for LGS Loop Start
LGS GS for LGS Ground Start
LGS PLAR or PLAR_D3 for LGS PLAR
LGE LS for LGE Loop Start
LGE GS for LGE Ground Start
RBS_ON to enable RBS
RBS_OFF to disable RBS
TERMINATE for accessing a frame relay network
Note
In a T1-to-T1 tandem node, if you select NoSIG and enable RBS, the system does not
monitor the signalling of the data received and overwrites the outgoing data bits
with the default RBS pattern.
For a Dual T1 with a TSM or a Dual T1-2 with a DRM, you can create 64 kb/s clear
channels without ABCD signalling in common signalling channel timeslot 24. All of
the signalling types described here can be carried by the TSM or DRM (see
chapter 20.5).
TERMINATE
NoSIG
SIG*
LS
E+M
PLAR
PLAR_D3
LGS
LGE
GS
LS
GS
SK000081
(400)
20.12-5
20.12.3
is passed without being tested for compatibility with the far-end signalling type
(E1_SIG SIG is the default for E1 signalling and for PRI circuits with NUM_SIG
set to a value other than 0)
E1_SIG NoSIG or T1_SIG NoSIG for clear channel E1 or T1 signalling, where a 64
kb/s clear channel is created for which signalling is not passed (default for PRI
circuits with NUM_SIG set at the default value of 0)
E1_SIG E+M E+M or T1_SIG E+M for E&M for E1 or T1 signalling, or E1_SIG
E+M E+M_B for conversion of proprietary E1 signalling to Newbridge standard
E1 signalling
E1_SIG LGS REM_EXT for LGS Remote Extension for E1 signalling
E1_SIG LGS EC for LGS Earth Calling for E1 signalling
E1_SIG LGS PLAR for LGS PLAR for E1 signalling
E1_SIG LGE REM_EXT for LGE Remote Extension for E1 signalling
E1_SIG LGE EC for LGE Earth Calling for E1 signalling
T1_SIG LGS LS for LGS Loop Start for T1 signalling
T1_SIG LGS GS for LGS Ground Start for T1 signalling
T1_SIG LGS PLAR or PLAR_D3 for LGS PLAR for T1 signalling
T1_SIG LGE LS for LGE Loop Start for T1 signalling
T1_SIG LGE GS for LGE Ground Start for T1 signalling
R2D_E+M for R2 digital signalling
Unidirectional circuits
Configure unidirectional circuits as:
20.12-6
(400)
a T1 or Dual T1-2 circuit is connected to an E1, Dual E1, X.21 and V.35 PRI, or
E1_SIG NoSIG for clear channel E1 signalling, where a 64 kb/s clear channel is
created without signalling
(400)
20.12-7
To configure signalling type for E1, MPA, X.21 and V.35 PRI, E3 and 64 kb/s
Codirectional cards
CONFIG CIRCUIT <sn-cc> or <sn-l-cc> or <E3id-E1id> MORE SIG_TYPE
E1_SIG
SIG*
T1_SIG
R2D_E+M
NoSIG
E+M
REM_EXT
LGS
E+M
LGE
E+M_B
PLAR
EC
SIG
LS
NoSIG
GS
EC
REM_EXT
E+M
PLAR
LGE
LGS
PLAR_D3
LS
TERMINATE
GS
SK000082
20.12.4
Table 20.12-3 is the signalling conversion table for the TTC2M card. The In-use state
corresponds to the signalling values that appear in that row. The TTC2M card Idle
state corresponds to the signalling values with the asterisk.
20.12-8
(400)
T1
T1 ESF
E1
E&M
In-use = 0
11
1111
1010
Idle
Idle = 1
00*
01
10
0000*
0001
0010
0011
0100
0101
0110
0111
1000
1001
1010
1011
1100
1101
1110
0000
0001
0010
0011
0100
0101
0110
0111
1000
1001
1011
1100
1101*
1110
1111
Seized*
Figure 20.12-2 shows the position of the framing and signalling bits in TS0.
Figure 20.12-2: TS0 Bits for the TTC2M Card
TS0
Bits
MF
9423
Table 20.12-4, shows the TTC2M card signalling bits in TS0 in an eight frame
multiframe.
(400)
20.12-9
Bits
1
A1
A2
A3
A4
A5
A6
A7
A8
A9
A10
A11
A12
A13
A14
A15
A16
A17
A18
A19
A20
A21
A22
A23
A24
A25
A26
A27
A28
A29
A30
20.12-10
(400)
20.13
20.13 Inversion
Issue 1, November 1997
Inversion
This chapter explains how to configure inversion for PRI card circuits.
20.13.1
20.13.2
(400)
20.13-1
20.13 Inversion
Issue 1, November 1997
Description
Option
None
NONE
ADI
ADI
Mark
MARK
Magnitude
Inversion
MAG_INV
NONE
ADI
MARK
MAG_INV*
SK000747
20.13-2
(400)
20.14
Loopback Detection
This chapter explains how to configure loopback detection for PRI cards.
20.14.1
Table 20.14-1 lists the types of loopback detection and identifies the primary rate
cards that support them.
Table 20.14-1: PRI Loopback Detection
T1 Card
Dual T1
Card
Dual T1-2
Card
Dual E1-2
Card
MPA Card
Type
CPSS
TS24 (1)
On-fault
In-band signature
Notes
1. This parameter is not available on Dual T1 or Dual T1-2 cards in 3664 MainStreet systems.
(400)
20.14-1
Preferred
path
PRI
MainStreet
node
PRI
MainStreet
node
PRI
PRI
PRI
MainStreet
node
PRI
Preferred
path
PRI
MainStreet
node
PRI
PSTN
PSTN
PRI
PRI
MainStreet
node
PRI
MainStreet
node
PSTN
Protected
path
1.Normal operation.
MainStreet
node
Fault
PRI
PSTN
PRI
Framing alarm
raised
PRI
PRI
PRI
Protected
path
4.When the fault is repaired and the loopback is
removed, the circuit is switched over the
preferred path.
5198
20.14-2
(400)
20.14.2
CPSS Connections
Dual E1-to-Dual E1
DS0
Dual T1-to-Dual T1
DS0
E1-to-Dual E1
DS0
E1-to-E1
TS0 or DS0
T1-to-Dual T1
DS0
T1-to-T1
FDL or DS0
TS0 or DS0
TS0 or DS0
MPA card:
X.21-to-X.21
V.35-to-V.35
RS-449-to-RS-449
RS-530-A-to-RS-530-A
TS0
TS0
TS0
TS0
Table 20.14-3 lists CPSS resources that are supported by the PRI cards and the
required connection types needed.
Table 20.14-3: CPSS Resources and Connection Types
CPSS Resources
Connection Types
Dedicated, shared
Control card
DCP
(400)
20.14-3
Warning
CPSS connections are live circuits and must be added to an active network carefully
to avoid routing problems.
Establish a CPSS connection over each link in the end-to-end connection. The node
monitors the CPSS channel for a loopback condition if service on the link is
disrupted.
2.
Primary rate
link
Primary rate
link
PSTN
CPSS
resource
CPSS
resource
6071
20.14.3
2.
3.
20.14-4
(400)
DRM
DRM
6073
Note
Tandem nodes that are physically linked together must differ in at least one of the
identification pattern elements (for example, node, slot or link number) to prevent
the false detection of loopbacks (see chapter 17.6). Loopbacks may be falsely
detected in the rare situation where both ends of a link have the same link, slot and
node numbers, but different domain numbers.
20.14.4
2.
3.
PSTN
Pattern
detector
Pattern
detector
Identification
pattern
6072
(400)
20.14-5
Caution
If a fault occurs and a loopback is applied to the link before a Red alarm is declared,
the loopback is not detected and the circuit will not switch to the protecting link.
20.14.5
20.14.6
NONE
VIA_CPSS
VIA_TS24
ON_FAULT
IN_BAND
Configure fault classes for PRI cards according to Table 20.14-1. Only one method of
loopback detection can be enabled on a link at a time.
Figure 20.14-5 shows a typical loopback detection display.
20.14-6
(400)
1117-H1-00
Installed
Status
Empty
Empty
Configured
A1-A DUAL2_T1
Toronto:A
Alarms:1
Name
11-May-1997
8:35a
Options
JB7 D4
DISABLED
DISABLED
Line length:
SHORT
Loopback detection:
NONE
Accept. err sec/24 hr: 86 (99.900%)
Link avail. monitoring: DISABLED
SES Limit BER Exceeding:1E-3
Link Signalling Mode:
RBS
Digital Service Level: DS0
DS1 Fault Signal:
NONE
16-
2-VIA_CPSS
7-
3-VIA_TS24
8-CANCEL
4-ON_FAULT
9-QUIT
50-
NONE*
VIA_CPSS
ON_FAULT
SK000707
NONE*
VIA_CPSS
IN_BAND
SK000694
(400)
20.14-7
OPTIONS
OPTIONS
MORE
FAULT_HNDL
LPBK_DETEC
LPBK_DETEC
NONE
VIA_CPSS
VIA_TS24 ON_FAULT
SK000083
where
the first sn-l indicates a Dual T1 card
the second sn-l indicates a Dual T1-2 card
Note
The VIA_CPSS and VIA_TS24 options apply only to Dual T1 and Dual T1-2 cards.
The ON_FAULT option applies only to Dual T1-2 cards.
20.14-8
(400)
20.15
Super-rate Circuits
This chapter introduces super-rate circuits for PRI cards and explains how to:
20.15.1
bidirectional tandem
unidirectional tandem
unidirectional tandem broadcast
There are two configurable super-rate connection options:
preferred (the set of DS0s that you prefer for the data transmission)
level 2 (the set of DS0s used to protect the preferred tandem super-rate)
(400)
20.15-1
Note
A DS0 may be involved in a level 2 tandem super-rate connection without being
involved in a preferred tandem super-rate connection.
Unidirectional tandem super-rate connections do not support level 2 configuration.
20.15-2
(400)
If you try to enter a circuit that is a master in another list, the system displays the
message Warning. That circuit is already a super-rate master. If you try to enter a
circuit that is a slave in another list, the system displays the message Warning. That
circuit is already a super-rate slave.
16
30
Bandwidth
(DS0s)
Bandwidth
(kb/s)
128
256
512
1024
1920
Bandwidth
(kb/s)
Circuit
Number
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
31 (1)
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Timeslots
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Note
1 Circuit 31 is only available when the link is configured for 31_CHAN, X.21_NTU or CCS framing types.
Circuit 31 cannot be involved in a super-rate configuration on CCS-configured links.
9066
(400)
20.15-3
Note
E1 cards in 3664 MainStreet systems do not support equidistant super-rate circuits.
Delay equalization
The system checks delay equalization for connections between any two super-rate
types. If unequal delays exist, the connection is not allowed.
20.15.2
20.15-4
(400)
Note
A DS0 may be involved in a preferred tandem super-rate at one speed and a level 2
tandem super-rate connection at another speed. A DS0 may be involved in a level 2
tandem super-rate connection without being involved in a preferred tandem
super-rate connection.
After you enter the number of DS0s, you must configure the super-rate format as:
(400)
20.15-5
PREFERRED
LEVEL_2
<number_ of _circuits>
CONTIGUOUS NON_CONTIG
EQUIDIST
where
number_of_circuits is the number of DS0s in the super-rate bundle
list_of_circuits is a list of individual DS0s or ranges of DS0s, separated by returns (for example, <n1>
<n2> <n3:n4> specifies that the bundle includes individual DS0s n1 and n2 and the range of DS0s
between n3 and n4)
SRC_N_CIRC
DST_N_CIRC
<number_of_circuits>
CONTIGUOUS
NON_CONTIG
EQUIDIST
<list_of_circuits>
SK000085
where
number_of_circuits is the number of DS0s in the super-rate bundle
list_of_circuits is a list of individual DS0s or ranges of DS0s, separated by returns (for example, <n1>
<n2> <n3:n4> specifies that the bundle includes individual DS0s n1 and n2 and the range of DS0s
between n3 and n4)
20.15-6
(400)
20.15.3
(400)
20.15-7
TO_CIRCUIT
PROT_BY
PROTECTING
MORE
DISCONNECT
ONE_WAY_TO
PREFERRED PROTECTION
<x-sn-cc> or <x-sn-l-cc>
or <E3id-E1id-cc>
<x-sn-l-cc> or
<E3id-E1id-cc>
SK000086
where
the first x-sn-cc or x-sn-l-cc or E3id-E1id-cc is the master DS0 of the first super-rate bundle, or the source
circuit identifier in a unidirectional connection, or the super-rate DCC circuit identifier in a
DCC-to-primary rate connection
the second x-sn-cc or x-sn-l-cc or E3id-E1id-cc is the master DS0 of the second super-rate bundle, or the
destination identifier in a unidirectional connection, or the primary rate DS0 in a DCC-to-primary rate
connection
Note
If any of the circuits carry CPSS or the source and destination circuits do not have
the same amount of available bandwidth, the system displays the message Those
circuits cannot be connected.
When cross-connecting more than one super-rate circuit to a primary rate link on a
Dual T1 card, connect them in descending bandwidth size, beginning with the one
that occupies the most bandwidth.
The 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020
Network Manager rerouting of some super-rate connections involving single T1 or
E1 and Dual T1 or E1 cards (single card-to-single card and single card-to-dual card
connections) may not succeed. The system is unable to perform delay equalization
and the connection is blocked. The new super-rate connection may be violating the
rule that connections be made in descending bandwidth order. The 4602 MainStreet
Intelligent NetworkStation or MainStreetXpress 46020 Network Manager puts the
path in a Waiting for Repairs state.
To configure a DCC circuit for super-rate operation, see chapter 22.3.
20.15.4
20.15-8
(400)
Note
There is no limit to the number of broadcast sources that can be configured.
(400)
20.15-9
20.15-10
(400)
20.16
20.16.1
20.16.2
Normal operation
Figure 20.16-1 shows a typical connection across four nodes. During normal
operation, the connection is maintained from the access equipment, across the
tandem nodes to the network-side endpoint node.
(400)
20.16-1
TS24
Link failure
TS24
trunk
No trunk
TS24 framing
Trunk
1-way
conditioning TS24 Framing conditioning Red
alarm
Yellow conditioning
Alarm
alarm
1
5
4
4
3
alarm 3
24 DS0
24 DS0
24 DS0
24 DS0
24 DS0
SR
SR
SR
SR
T1
T1
24 DS0
SR
24 DS0
tandem
access
tandem
tandem
SR
tandem T1
SR Normal
Normal
2
access
Dual
Yellow Dual
T1-2
signal T1-2
link
link
7
Level 2 24 DS0
connection
SR
MainStreet node 100
Normal
Normal
T1
Normal
Alternative
Alternative
Normal
24 DS0
SR
24 DS0
SR
T1
24 DS0
SR
24 DS0
SR
Level 2
24 DS0
connection
SR
T1
Normal
Normal
5980
20.16-2
(400)
Fault recovery
When the fault is repaired, the adjacent nodes raise Alarm Cleared signals, and the
affected link is put back in service. If the adjacent node is an end node, the circuit is
disconnected from the protecting connection and switched back over the preferred
connection.
The TS24 framing signal is no longer transmitted downstream. When an endpoint
node determines that the TS24 framing signal is no longer being received, a TS24
Frame OOS Cleared alarm is generated and the 24 DS0 super-rate circuit is switched
back over the preferred connection.
(400)
20.16-3
20.16.3
2.
3.
Make the connections. You connect two super-rate circuits by specifying their
master circuits (see chapter 20.15). For more information about alarm times, see
Maintenance, section 35.4.1.
Caution
All links involved in the connection must be configured for 24 DS0 super-rate
connections and two-way trunk conditioning. If one-way trunk conditioning is
configured, only one end of the network will RAPID switch and data loss will occur.
PHYSICAL
FAULT_HNDL
MORE
SIG_MODE
DS_LEVEL
RBS
DS0*/24_DS0
FAULT_SIG
TRUNK_COND
ONE_WAY/TWO_WAY*
TS24_FRAME
ACCESS
TANDEM
SK000087
20.16-4
(400)
Note
Selecting 24_DS0 configures all 24 DS0s on the link with RBS off and non-inverted
data transmission on.
(400)
20.16-5
20.17
To configure the SES limit for Dual E1 or Dual E1-2 cards, see section 20.18.4.
20.17.1
Threshold monitoring for the following statistics can be configured on each link of
the Dual T1 and Dual T1-2 card:
errored seconds
failed seconds
severely errored seconds
Monitoring of link statistics for Dual T1 and Dual T1-2 cards is enabled or disabled
for the entire link.
(400)
20.17-1
The following Dual E1-2 card statistics can be configured for threshold monitoring
over the 15-min interval and the 24-h period:
errored seconds
bursty error seconds
severely errored seconds
unavailable seconds
control slip seconds
degraded minutes
You can configure the SES limit for each of the links on the Dual T1 and Dual T1-2
cards. On the MPA card, you can configure both the SES and DGM limits for each
link.
20.17.2
20.17-2
(400)
1117-H1-00
Installed
Status
Empty
Empty
Configured
A1-A DUAL2_T1
Toronto:A
Alarms:1
Name
11-May-1997
8:35a
Options
JB7 D4
DISABLED
DISABLED
Line length:
Loopback detection:
Accept. err sec/24 hr:
Link avail. monitoring
SES Limit BER Exceeding:
Link Signalling Mode:
Digital Service Level:
DS1 Fault Signal:
SHORT
NONE
86 (99.900)
DISABLED
1E-3
RBS
DS0
NONE
1-PHYSICAL
6-
2-THRESHOLDS
7-MORE
3-FAULT_HNDL
8-CANCEL
4-ISDN
9-QUIT
50-
Errored seconds threshold for links on Dual T1 and Dual T1-2 card
The link must meet a minimum availability percentage over a 24-h period. If the time
that the link is available drops below this percentage because of error events on the
link, you must take the link out of service until it can meet the minimum availability
percentage.
The errored second threshold is the maximum number of unavailable seconds that
the link can experience within a 24-h period and still meet the minimum availability
percentage. Figure 20.17-2 shows the errored second threshold equation.
Figure 20.17-2: Errored Second Threshold Equation
Minimum availability %
x Number of seconds in 24 hours
100
Minimum availability %
x 86 400
100
9059
(400)
20.17-3
LINK_MON
ENABLE/DISABLE*
SES_LIMIT
ERR_SEC
<threshold>
1E-7
1E-6
5E-6
1E-5
1E-4
1E-3*
SK000088
ENABLE/DISABLE*
ERR_SEC
<threshold>
SK000089
20.17.3
20.17-4
(400)
The Dual E1-2 card informs the node when a threshold is crossed and the system
raises an alarm in the diagnostics queue, see chapter 35.3 for information about the
diagnostics queue. If you configure the statistic threshold monitoring over a 15-min
interval, an alarm is raised at the end of each 15-min interval in which the statistic
threshold is exceeded. If you configure the threshold for a 24-h period, only at the
end of the 24-h period is an alarm raised.
Table 20.17-1 lists and describes the link performance monitoring statistics and the
threshold limits for the 24-h period and the current 15-min interval.
Table 20.17-1: Performance Threshold Statistics and Threshold Ranges
Link
Statistic
Description
Threshold Value
Ranges - 24 h
Threshold Value
Ranges - 15 min
ES
1 through 32 767
1 through 900
BES
1 through 32 767
1 through 900
SES
1 through 32 767
1 through 900
UAS
1 through 32 767
1 through 900
CCS
1 through 32 767
1 through 900
DM
1 through 1440
1 through 15
The system continues to collect quality statistics while performance thresholds are
monitored. The Dual E1-2 card resets the monitored threshold counts to zero if the
cards quality statistics are cleared or the card is reset. If the statistics are cleared after
an alarm has been raised because of a threshold crossing, the card raises the alarm
again when that threshold is crossed a second time.
Figure 20.17-3 shows a link monitoring performance thresholds display. The
configured threshold values for the link statistics are displayed for both the current
15-min and 24-h periods.
(400)
20.17-5
Figure 20.17-3: Dual E1-2 Card Link Monitoring Performance Thresholds Display
3600 MainStreet
Link Quality:
1117-H1-00
Toronto:A
Slot:A2-A
Alarms:1
11-May-1997
8:35a
Status:In Service
Current
Errored seconds:
Bit Error Rate:
Severely errored second:
Unavailable second:
Controlled Slip second:
Degraded Minutes:
34
DISABLED
357
DISABLED
DISABLED
DISABLED
24_HR
DISABLED
DISABLED
1875
DISABLED
DISABLED
DISABLED
2-24_HR
7-
38-
49-QUIT
50-
CURRENT
ES_THRESH
BES_THRESH
SES_THRESH
THRESHOLD
UAS_THRESH
CCS_THRESH
24_HR
DM_THRESH
DISABLE
<threshold>
SK000685
20.17-6
(400)
where
threshold is a value from 1 to 900 in all current 15-min interval statistics except degraded minutes. For
degraded minutes, enter a value from 1 to 15.
threshold is a value from 1 to 32 767 in all 24-h period statistics except degraded minutes. For degraded
minutes, enter a value from 1 to 1440.
20.17.4
ESF Framing
CRC-6 Error Events
ESF Framing
ANSI T1.403 Grade
D4 Framing
BPV Bit Errors
per Second
1E-3
320
G6
1544
1E-4
101
G5
487
11
G4
15
5E-5 (1)
G3
1E-6 (2)
G2
1E-7 (2)
G1
1E-5
(1)
Notes
1. This bit error rate applies only to Dual E1-2 and Dual T1-2 cards.
2. This bit error rate applies only to Dual T1-2 cards.
(400)
20.17-7
20.17.5
SES_LIMIT
DGM_LIMIT
<number>
1E-6
5E-5
1E-4
1E-5
1E-3*
SK000803
where number is 1 to 60
20.17-8
(400)
20.18
20.18.1
Dual E1
Card
Dual
E1-2
Card
E3
Card
Dual E3
Card
Optical
Ext.
Cards
Parameter
NU bit
SES limit
BER
E-bit
CRC4 reframing
Equalization
(400)
20.18-1
20.18.2
Number of NU Bits
Default Value
E3
E2
E1
11111
The system displays the current values for the transmitted and received NU bits.
any aggregate interface card circuit except TS0 on Single E1 cards and the FDL on
20.18-2
(400)
TS0 may only be cross-connected to a 64 kb/s clear channel (that is, a DS0 in
which all bits are available for user data). TS0 cannot be connected to CPSS for
the Dual E1 or Optical Extension card. For the Dual E1-2 card, TS0 can be
connected to CPSS only when CPSS_PIPE is enabled. TS0 cannot be connected to
SRMs, or super-rate circuits. There are no circuit configuration parameters for
TS0; it can only be connected or disconnected. TS0 can be protected by A/B
protection switching.
All five NU bits are set to 1 when trunk conditioning is applied and enabled (see
chapter 20.9).
When the NU bit or CPSS_PIPE parameter is enabled, CCS- and 31
channel-framed E1 links (chapter 20.6) are reduced from 31 to 30 circuits.
Although TS0 occupies 64 kb/s when cross-connected, only 40 kb/s (bits 4
through 8) carry user data. The other 24 kb/s (bits 1 through 3) are not
user-configurable and are forced to zero.
Note
The SA4 BER parameter (see section 20.18.5), NU bits parameter and CPSS in TS0
(see chapter 17.6) are mutually exclusive (only one of these parameters can be
enabled at one time). Any one of these three parameters can be used simultaneously
with the E-bit parameter (see section 20.18.6).
Configure the Dual E1, Dual E1-2 or Optical Extension card NU-bit parameter as:
NU5BIT_ON to enable it
NU5BIT_OFF to disable it (default)
To enable or disable NU bit cross-connections for Dual E1 cards
CONFIG SLOT <sn-l> OPTIONS TS0_OPTION NU5BIT_ON/NU5BIT_OFF*
(400)
20.18-3
20.18.3
Although Optical Extension cards have a proprietary fibre optic interface, they are
configured using the same procedures to configure Dual E1 cards with a few
exceptions exceptions. In order for IOTUs to communicate, Optical Extension cards
must be configured for master and slave operation in the shield grounding mode.
Maintenance in timeslot is enabled by configuring the receive shields.
Configure transmit and receive shields as:
RX_FLOAT/RX_EARTH* TX_FLOAT/TX_EARTH*
SK000090
RX_FLOAT/RX_EARTH*
TX_FLOAT/TX_EARTH*
CHASSIS/SIGNAL*
SK000706
20.18-4
(400)
20.18.4
3630 MainStreet
node
3600 MainStreet
node
3600 MainStreet
node
E1
E1
E1
Network
Dual E1 card
Dual E1 card
Port A Port B
Port A Port B
Telephone
E1
E1
E1
-Non-RAPID
-Standard SES limit
-RAPID primary
-Stricter SES limit
6588
Previously, a standard SES was defined as a second with 832 or more CRC4 error
events or 1400 HDB3 errors. Now you can select the SES limit from four preset
values according to your system and network configuration. Table 20.18-3 lists the
configurable SES limits and the number of CRC4 and HDB3 errors each limit
represents.
Table 20.18-3: Threshold Selection
SES Limit
10-3
832
1400
10-4
184
180
10-5
20
18
5 x 10-6
10
(400)
20.18-5
5E-6
1E-5
1E-4
1E-3*
SK000091
5E-6
1E-5
1E-4
1E-3*
SK000802
20.18.5
20.18-6
(400)
10 11 12 13 14 15
Odd-numbered Frames*
1 2
30 31
Timeslots 0 to 31
Timeslot 0
1
Bits 1 to 8
Sa4 bit
*note:
The timeslot 0 in
even-numbered frames
carries the frame
alignment signal.
The timeslot 0 in
odd-numbered frames
does not carry the
frame alignment signal.
8102
BERAlm
Actions
OFF
OFF
OFF
ON
ON
OFF
ON
ON
Note
The SA4 BER parameter, NU bits parameter (section 20.18.2) and CPSS in TS0
(chapter 17.6) are mutually exclusive; only one of these parameters can be enabled
at any one time. Any of these three parameters can be used simultaneously with the
E-bit parameter (section 20.18.6).
(400)
20.18-7
The BER of the incoming E1 link is calculated based on FAS errors if HDB3 statistics
are gathered, or on CRC4 errors if CRC4 statistics are gathered. If you turn on both
the BER alarm and SA4 options, the Dual E1 and Dual E1-2 cards monitor the BER
and also perform the following functions.
If the BER exceeds the pre-set error threshold, the card sets the transmitted SA4
These events are recorded in the quality statistics for the affected link (see
Maintenance, section 34.1.3).
Table 20.18-5 lists the type of error event detected for Dual E1 and Dual E1-2 card
statistics and the corresponding pre-set error threshold that is applied when the SA4
bit parameter is enabled.
Table 20.18-5: SA4-bit Error Thresholds
Statistics Gathered
Errors Detected
Error Threshold
HDB3
FAS
10-5
CRC4
CRC4
106
TS0_OPTION
MORE
SA4BIT_ON/
SA4BIT_OFF*
BERAlm_ON/
BERAlm_OFF*
SK000092
20.18-8
(400)
20.18.6
Sub-multiframe 2
6
9 10 11 12 13 14 15
Frames 0 to 15
Frame 13
0
Frame 15
30 31
Timeslots 0 to 31
Timeslot 0
1
30 31
Timeslots 0 to 31
Timeslot 0
7
Bits 1 to 8
Bits 1 to 8
E-bit
E-bit
956
Frame 13 E-bit
(SMF1 Status)
Frame 15 E-bit
(SMF2 Status)
SMF1 is error-free
SMF2 is errored
SMF1 is errored
SMF2 is error-free
(400)
20.18-9
EBITS_ON to enable it
EBITS_OFF to disable it (default)
When the E-bit parameter is disabled, the E bit (Si bit) is set to 1 by default.
The E-bit option is not available for configuration unless CRC4_STATS is enabled.
Note 1
The SA4 BER parameter (see section 20.18.5), NU bits parameter (see section 20.18.2)
and CPSS in TS0 (see chapter 17.6) are mutually exclusive (only one of these
parameters can be enabled at any one time). Any of these three parameters can be
used simultaneously with the E-bit parameter.
Note 2
For ISDN links, the Dual E1-2 card can detect RAI with E-bits reporting regular CRC
block errors (ISDN state F2), or with E-bits reporting constant CRC block errors
(ISDN state F5).
20.18.7
20.18-10
(400)
20.18.8
0DB_4DB*
4DB_8DB
8DB_10DB
10DB_12DB
SK000093
20.18.9
(400)
20.18-11
Si
Si
SA4
SA5
SA6
SA7
SA8
20.18-12
(400)
20.19
20.19.1
Bandwidth utilization
Supervisory channel
Clocking source
Clock inversion
20.19.2
Parameter
Slip buffer
(400)
20.19-1
Default
Number of
Circuits
Maximum
Number of
Circuits
Maximum
Bandwidth
Circuit
Total
Aggregate
Bandwidth
90-0669-01
30
30 (1)
64 kb/s
1920 kb/s
90-0669-03
56 kb/s
56 kb/s
90-0569-03 (2)
30
30 (1)
64 kb/s
1920 kb/s
90-0569-06 (2)
30
30 (1)
64 kb/s
1920 kb/s
90-0569-09 (2)
30
30 (1)
64 kb/s
1920 kb/s
90-0569-01 (3)
29
29
64 kb/s
1856 kb/s
90-0569-07
56 kb/s
56 kb/s
Notes
1. The last 64 kb/s of the aggregate link is referred to as the supervisory channel or TS0. The
supervisory channel is used to provide framing and signalling for the other circuits (up to 29).
Supervisory channel bandwidth not used for framing and signalling can be used to carry user data.
See also section 20.19.3.
2. X.21 PRI Type 2.
3. X.21 PRI Type 1.
Each circuit on a multi-circuit V.35 PRI or X.21 PRI card Type 2 represents a 64 kb/s
clear channel (a DS0 in which all bits are available for user data). These variants
support signalling carried in the HCM-framed supervisory channel (see
section 20.19.3).
Each circuit on the multi-circuit X.21 PRI card Type 1 also represents a 64 kb/s clear
channel, but signalling is not supported.
Single-circuit V.35 PRI and X.21 PRI cards provide a single 56 kb/s clear channel for
connection to Switched 56 services. Signalling is not supported.
Number of circuits with signalling for X.21 and V.35 PRI cards
Table 20.19-3 lists the default and maximum number of circuits that can use
signalling for each variant of the X.21 and V.35 PRI card.
20.19-2
(400)
Maximum Number of
Circuits
Maximum Circuits
with Signalling
90-0669-01
30
29
90-0669-03
90-0569-03 (1)
30
29
90-0569-06 (1)
30
29
90-0569-09 (1)
30
29
90-0569-01 (2)
29
90-0569-07
Notes
1. X.21 PRI Type 2.
2. X.21 PRI Type 1 (signalling is not supported on this variant).
When you configure the number of circuits that require signalling (n), the system
supports signalling for circuits in the range 1 to (n-1). For example, if the number of
circuits that require signalling is 7, the system supports signalling on circuits 1 to 6,
inclusive.
If the total number of circuits configured for the link is x, then n must be (x -1). For
example, if the total number of circuits configured for the link is 30, the number of
circuits with signalling must be in the range 1 to 29.
Signalling information for all the circuits in this range is carried in a common
channel called the supervisory channel or TS0. The supervisory channel is carried in
the last 64 kb/s of the aggregate link. If the total number of circuits configured for
the link is x, the supervisory channel is always circuit x (see section 20.19.3).
Note
The bandwidth utilization for X.21 and V.35 PRI cards cannot be changed if any
circuits are cross-connected or the slot is configured as a synchronization source.
(400)
20.19-3
20.19.3
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
B7 B6 B5 B4 B3 B2 B1 B0
F
S
S
S
S
S
S
S
S
S
S
Bandwidth available
for transparent channels
Bandwidth available
for HCM channels
Signalling bits
for 5 channels
4228
20.19-4
(400)
You can also configure the position of the HCM framing bit in the supervisory
channel (see chapter 23.6). Figure 20.19-2 illustrates the slot options display for an
X.21 PRI card Type 2. It shows the card configured for 30 circuits, 5 of which (circuits
1 to 5) require signalling.
Because signalling bit pairs (SS in Figure 20.19-2) are always placed in the same row,
the HCM frame must be 2, 4, 6 or 8 bits wide (depending on the number of circuits
configured for signalling). The framing bit (F in Figure 20.19-2) can be located in any
of columns B1, B3, B5 or B7.
Figure 20.19-2: X.21 PRI Screen Display
3600 MainStreet
1117-H1-00
Toronto:A
Configured
Installed
Status
A2
X21_PRI_2
X21_PRI_2
OOS
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
B7
B6
B5
B4
B3
S
S
B2
S
S
B1
S
S
S
B0
S
S
S
Alarms:1
11-May-1997
Name
8:35a
Options
Circuits : 30 DTE
C-CPSS
F-FRAMING BIT
S-SIGNALLING BIT
Channels with
Signalling
: 5
Framing Type
: 2
Buffering
: SHORT
Transmit Clock : NORMAL
CPSS over TS0 is DISABLED
2-NUM SIG
7-MORE...
3-INVERT
8-CANCEL
4-FRAME BIT
9-QUIT
5-FRAME 1
0-
To configure the supervisory channel for X.21 and V.35 PRI cards
To configure the supervisory channel, set the number of signalling circuit
(NUM_SIG) and the width of the HCM frame (FRAME_BIT).
CONFIG SLOT <sn> OPTIONS
NUM_SIG
FRAME_BIT
<number>
<Bn>
SK000094
where
number is 0* to 29
Bn is B1, B3, B5 or B7*
(400)
20.19-5
Note
You cannot change the number of signalling circuits or the HCM frame width if any
circuits are cross-connected or the slot is configured as a synchronization source.
20.19.4
DTE to specify the PTT that provides the PRI link (default)
DCE to specify the system
To configure the clocking source for X.21 and V.35 PRI cards
CONFIG SLOT <sn> OPTIONS MORE DCE/DTE*
Note
When the interface speed of an X.21 Type 2 (see Table 20.19-3) or V.35 PRI link
configured for DTE differs from the incoming network clock speed by 3 percent,
the port is declared out-of-service and a Speed Mismatch alarm is raised (see
Maintenance, Table 35.8-22).
20.19.5
20.19-6
(400)
Table 20.19-4: Clock Inversion Settings for the X.21 PRI Card
Interface
Speed in
kb/s
Distance in m (ft)
No clock Inversion
Required
Distance in
m (ft)
Clock Inversion
Required
Interface
Speed
in kb/s
Distance in m (ft)
No Clock Inversion
Required
Distance in m (ft)
Clock Inversion
Required
64
0 to 50
(0 to 164)
not applicable
1024
0 to 4/44 to 50
(0 to 13.1/144.3 to 164)
4 to 44
(13.1 to 144.3)
128
0 to 50
(0 to 164)
not applicable
1088
0 to 3.5/41 to 50
(0 to 11.5/134.5 to 164)
3.5 to 41
(11.5 to 134.5)
192
0 to 50
(0 to 164)
not applicable
1152
0 to 2/37.5 to 50
(0 to 6.6/123 to 164)
2 to 37.5
(6.6 to 123)
256
0 to 50
(0 to 164)
not applicable
1216
0 to 1/34 to 50
(0 to 3.3/111.5 to 164)
1 to 34
(3.3 to 111.5)
320
0 to 48
(0 to 157.4)
48 to 50
(157.4 to 164)
1280
32 to 50
(105 to 164)
0 to 32
(0 to 105)
384
0 to 37.5
(0 to 123)
37.5 to 50
(123 to 164)
1344
29 to 50
(95.1 to 164)
0 to 29
(0 to 95.1)
448
0 to 30
(0 to 98.4)
30 to 50
(98.4 to 164)
1408
27.5 to 50
(90.2 to 164)
0 to 27.5
(0 to 90.2)
512
0 to 24
(0 to 78.7)
24 to 50
(78.7 to 164)
1472
26 to 50
(85.3 to 164)
0 to 26
(0 to 85.3)
576
0 to 19
(0 to 62.3)
19 to 50
(62.3 to 164)
1536
24 to 50
(78.7 to 164)
0 to 24
(0 to 78.7)
640
0 to 16
(0 to 52.5)
16 to 50
(52.5 to 164)
1600
22 to 50
(72.2 to 164)
0 to 22
(0 to 72.2)
704
0 to 13
(0 to 42.6)
13 to 50
(42.6 to 164)
1664
21 to 50
(68.9 to 164)
0 to 21
(0 to 68.9)
768
0 to 11
(0 to 36.1)
11 to 50
(36.1 to 164)
1728
19 to 50
(62.3 to 164)
0 to 19
(0 to 62.3)
832
0 to 8
(0 to 26.2)
8 to 50
(26.2 to 164)
1792
17.5 to 50
(57.4 to 164)
0 to 17.5
(0 to 57.4)
896
0 to 7
(0 to 23)
7 to 50
(23 to 164)
1856
17 to 50
(55.8 to 164)
0 to 17
(0 to 55.8)
960
0 to 5/48 to 50
(0 to 16.4/157.4 to 164)
5 to 48
(16.4 to 157.4)
1920
16 to 50
(52.5 to 164)
0 to 16
(0 to 52.5)
(400)
20.19-7
20.19.6
Configuring the Slip Buffer for X.21 and V.35 PRI Cards
You can configure buffering for jitter and wander for the X.21 and V.35 PRI cards.
Jitter is short term variations in a bit cell with respect to its nominal value. It can be
expected when repeaters are used on the lines over which the link is transmitted.
Wander is low frequency excursions of the clock from its nominal value. It is
typically a problem with satellites because of their imperfect orbits.
Because there is only one clock on a PRI aggregate link, buffering is required in both
the transmit and receive directions. Slips are likely to happen at both the send and
receive sides at almost the same time.
For a PRI card, you can select one of two buffer sizes to accommodate jitter and
wander tolerance:
To configure the slip buffer for X.21 and V.35 PRI cards
CONFIG SLOT <sn> OPTIONS LONG_BUF/SHORT_BUF*
20.19-8
(400)
20.20
20.20.1
interface type
gender (DCE or DTE)
total number of channels and channel type
transport bandwidth
HCM framing and frame bit positions in TS0
SRM HCM data on TS0
control leads
lead initiated loopbacks
clock inversion
slip and doppler buffers
2.
3.
The first general procedure is composed of the tasks required to get the MPA card
ready for communications. Table 20.20-1 lists the tasks in logical order and optional
or co-dependent tasks are indicated.
Table 20.20-1: First General Procedure Tasks
Configuration Task
Reference
Interface type
20.20.2
20.20.3
20.20.4
20.20.4
Transport bandwidth
20.20.5
20.20.7
(400)
20.20-1
Configuration Task
Reference
17.6
20.20.9
20.20.9
Lead-initiated loopbacks
20.20.9
Clock inversion
20.20.10
Notes
1. The framing bit position must be configured if CPSS over TS0 is required.
2. CPSS over TS0 is an optional feature of the MPA card.
The second general procedure involves connecting circuits to the MPA card. You can
immediately transmit information if no changes are required to any default settings
or card options. Super-rate circuit configuration is performed at this time, as
described in chapter 20.15. To configure an SRM HCM data circuit on TS0, see
section 20.20.8.
When a circuit is cross-connected on the MPA card, the system automatically sets the
following MPA card channel parameters:
signalling
channel type (voice or data)
The system uses the hardware that the MPA card is cross-connecting with to
determine the channel parameter settings. If you are connecting to hardware that
supports multiple configurations, such as T1 or E1 cards, then the default settings
are used. See chapter 20.12 to manually change the circuit signalling for the
MPA card and section 20.20.4 to change the channel type.
Tasks included in the third general procedure are those dealing with default or
optional settings that may require reconfiguration to match your specific network
requirements. Table 20.20-2 lists these options and features in alphabetical order. See
chapter 20.1 for a complete listing of configurable MPA card parameters, options
and defaults.
Table 20.20-2: MPA Card Optional Configuration Tasks
Configuration Task
Alarm Time
20.20-2
Reference
35.4
Background diagnostics
33.2.4
20.11.2
Doppler buffer
20.20.11
Fault classes
20.9.5
Fault signalling
20.10.2
(400)
Configuration Task
Reference
HCM framing
20.20.6
Loopback detection
20.14.1
Slip buffer
20.20.11
20.17.5
Trunk conditioning
20.9.3
Figure 20.20-1 shows an NMTI slot display for link 1 of an MPA card installed on a
single bandwidth shelf. Two channels are configured as signalling channels.
Figure 20.20-1: Slot Display for an MPA Card Link
3600 MainStreet
#
A1-1
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
1117-H1-00
Configured
MPA
B7
A
A
A
A
A
A
A
A
A
A
B6
F
B5
Toronto:A
Installed
MPA
B4
B3
B2
Status
OOS
B1
B0
Alarms:1
Name
Configured As
Interface Type
CPSS Over TS0
Slip Buf Size
Slip By
SES_LIMIT
DGM_LIMIT
Loopback Detect
CPSS over TS0 is
Transmit Clock
11-May-1997
Options
Circuits :
8:35a
20.20.2
2-64k
7-
3-56k
8-CANCEL
4-48k
9-QUIT
50-
(400)
20.20-3
RS530A
RS449/V36
X.21
V.35
X.21 ESI
SK000689
where l is 1 to 4
20.20.3
In DTE mode, when the speed of the interface clock differs from the incoming
network clock by 3 percent, the port is declared out-of-service and a Clock Speed
Mismatch alarm is raised (see Maintenance, section 35.8.2, Table 35.8-22).
20.20.4
20.20-4
(400)
The MPA card can connect to a total of 62 DS0 channels across the backplane, of
which 60 are available for data transport. One backplane channel per stream is
dedicated to carry CPSS over TS0 (if enabled) and another one is reserved for use by
the system. Framing information does not go out onto the backplane.
Figure 20.20-2 illustrates the default backplane channel assignments for ports 1
through 4 in a double bandwidth shelf.
Figure 20.20-2: Default Backplane Channel Assignments on a Double Bandwidth Shelf
Backplane channel 31
reserved
Channels
on the
backplane 1
32
PORT 1
15 channels
PORT 2
15 channels
CPSS
1
32
PORT 3
15 channels
PORT 4
15 channels
Backplane channel 31
reserved
CPSS
9451
A channel stream represents 32 DS0 level channels on the backplane. Two channel
streams are allocated to the MPA card when it is installed in a double bandwidth
slot. Ports 1 and 2 share the same channel stream, as do ports 3 and 4. Each interface
is assigned 15 of the available 30 data channels. The last 64 kb/s of the channel
stream is reserved to carry CPSS for the first port in that stream to enable CPSS over
TS0. Channel 31 is reserved for use by the system.
If CPSS for port 1 is carried in channel 32 of the first channel stream, when CPSS over
TS0 is enabled for port 2, the highest unassigned 64 kb/s channel is automatically
selected to carry the CPSS. If all of the data channels for port 2 are unassigned, then
channel 29 is used for CPSS, leaving 14 channels available to port 2 for data. This
scenario also applies to ports 3 and 4 on the second channel stream.
All data channels on the link are assigned by default. If one of the two ports sharing
the same channel stream already has CPSS over TS0 enabled, then the message Not
Enough Bandwidth is displayed when attempting to enable CPSS for the second
port. One data channel must be made available to enable CPSS on the second port.
Figure 20.20-3 shows the default channel assignments for ports one through four on
the backplane in a single bandwidth shelf. All four ports share a single channel
stream on the backplane.
(400)
20.20-5
Channels
on the
backplane 1
32
PORT 1
7 channels
PORT 2
7 channels
PORT 3
7 channels
PORT 4
7 channels
CPSS
9450
On a channel stream, either data or voice can be carried on the 30 channels that are
available for payload. When a circuit is cross-connected to the MPA card channel,
the system automatically sets the channel type according to the hardware being
connected. If you are connecting to hardware that supports multiple configurations,
such as T1 or E1 cards, then the system sets the channel type to the default setting
which is voice.
Any available channel on the MPA card link can be configured as a signalling
channel. When this is done, a corresponding signalling bit pair is automatically
placed in the last part of the TS0 frame, see Figure 20.20-4. Typically, any channel
that will carry voice traffic should be configured for signalling. An exception could
be if a nailed-up circuit is configured, which does not necessarily require signalling.
By default, no signalling is carried in the data portion of TS0.
Restrictions
The following restrictions apply when setting the number of channels on the MPA
card.
Before increasing the number of channels to a value greater than the default for
one port, decrease the number of channels allocated to one of the other ports
sharing the same channel stream. The maximum number of channels on a
channel stream is 30 and all are assigned to a port by default.
The number of signalling channels configurable on an interface is between 0 and
the total number of channels (n) configured on the interface minus 1 (n -1). This
is because TS0 is required for supervisory information.
Delay equalization problems may occur in a single bandwidth shelf. You can
either connect to another circuit to avoid fragmented bandwidth or reset the
MPA card to remove this problem.
20.20-6
(400)
Note
If you enter 0 for the number of channels on the port, the following message appears
Warning: Certain port configurations will be changed to default. All channels on
the port are reset to the default configuration and all connections are lost.
20.20.5
Two parameters define the total amount of bandwidth on the MPA card interface.
(400)
20.20-7
64k*
48k
56k
SK000779
where l is 1 to 4
20.20.6
HCM1
HCM2
HCM3
HCM4
HCM5
If the MPA card is already configured for HCM2, changing the configuration of the
selected link to a single 48, 56 or 64 kb/s channel causes the system to automatically
change the framing to HCM1.
HCM2 must be used if the MPA card is connected to a 3606 MainStreet node, a
3612 MainStreet node or to the X.21 and V.35 PRI cards. If the MPA card is used in
an X.21 Transfix I node, HCM2 is not supported.
Note
The MPA card cannot be connected to an X.21 Transfix I card.
HCM3, HCM4 and HCM5 offer enhanced functionality that is not available with
HCM1 and HCM2. They provide G.821 statistics gathering, a maximum
synchronization time of 100 ms and in-band loopback signature detection.
The availability of these three framing patterns makes it possible to transport a PRI
link within a higher speed PRI link without synchronizing from the wrong
link-framing information. Service providers can choose to use either HCM4 or
HCM5 framing while HCM3 framing is for the end user.
20.20-8
(400)
HCM1 and HCM2 framing use 800 b/s of bandwidth on the supervisory channel,
TS0. HCM3, HCM4 and HCM5 framing use 8 kb/s of bandwidth on TS0.
For aggregate link and frame bit position configuration, see section 20.20.7.
HCM
HCM 2
HCM 4
HCM 3
HCM 5
SK000690
where l is 1 to 4
20.20.7
(400)
20.20-9
In Figure 20.20-4, the interface has 16 kb/s CPSS over TS0 enabled, which always
occupies bit positions B7 and B6 (see chapter 17.6 for information on enabling CPSS
over TS0). Both the A-bits and F-bit are shown, so the HCM scheme configured on
the interface is either HCM3, HCM4 or HCM5 (see section 20.20.6 for information).
Figure 20.20-4: Example TS0 Framed with HCM3, HCM4 or HCM5
MPA card
Framing bits
HCM
Framing bit
SRM
Data bit
B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
Bandwidth available
for SRM HCM data
channels
9464
Any unused bit positions to the right of the framing bits are available for SRM HCM
data and channel signalling. The NMTI represents the amount of bandwidth
allocated to an SRM HCM data channel by the number of elements containing a D,
where each D represents 800 b/s of bandwidth.
Signalling includes the clock adjustment if clocking is configured as independent.
The system reserves signalling bit positions in TS0 only if you configure a channel
as a signalling channel on the interface, see section 20.20.4. A pair of signalling bits
(S in Figure 20.20-4) is inserted in TS0 for each channel configured for signalling. The
aggregate link framing bits (the As in Figure 20.20-4) can be located in any column
except B0.
Note
You cannot change the number of signalling circuits or the HCM frame width if any
circuits are cross-connected or the slot is configured as a synchronization source.
20.20-10
(400)
20.20.8
B6
B5
B4
B3
B2
F0
F1
F2
F4
F5
F6
F7
F8
F9
B1
B0
9462
Ensure that the bandwidth of the SRM data is not larger than the unused bit
positions in TS0 so that it does not collide with signalling or framing bits (see
Figure 20.20-4). Configure the position of the SRM framing bits to match the position
of the MPA card links TS0 framing bits. See chapter 23.6 for more information on
configuring SRMs.
(400)
20.20-11
Once you configure the SRM to match the TS0 on the MPA card link, connect the
SRM to the last circuit on the MPA card link. The SRM is automatically assigned to
the unused bit positions in TS0. For more information on MPA card channels, see
section 20.20.4.
20.20.9
Direction
Signal
DCE Mode
DTE Mode
Analog Loopback
ALB
Input
Output
Clear to Send
CTS
Output
Input
DCD
Output
Input
DSR
Output
Input
DTR
Input
Output
LL
Input
Output
RDL
Input
Output
RL
Input
Output
RTS
Input
Output
Ring Indicator
RI
Output
Input
Test Mode
TM
Output
Input
Local Loopback
Remote Digital Loopback
Remote Loopback
Request to Send
Table 20.20-4 compares the MPA card control signals with ANSI, EIA and ITU-T
standard control signals for each interface type. The direction of the signal is listed
with respect to whether the MPA card is configured as a DCE or DTE device.
20.20-12
(400)
RS530-A
RS449
X.21
V.35
Signal
DCE/DTE
Signal
DCE/DTE
Signal
DCE/DTE
Signal (1)
DCE/DTE
ALB
Input/Output
CTS
CB
Output /Input
CS
Output/Input
Output/Input
DCD
CF
Output /Input
RR
Output/Input
Output/Input
Output/Input
DSR
CC
Output/Input
DM
Output/Input
Output/Input
DTR
CD
Input/Output
TR
Input/Output
Input/Output
LL
LL
Input/Output
LL
Input/Output
RDL
n/c
RI
n/c
RL
RL
Input/Output
RL
Input/Output
RTS
CA
Input/Output
RS
Input/Output
Input/Output
Input/Output
TM
TM
Output /Input
TM
Output/Input
Signal
Notes
1. V.35 signal references are actually pin number references. Consult the ITU-T V.35 Recommendation for the corresponding
signal names.
Control signals are configured as either forced on (transmits mark) or forced off
(transmits space). Table 20.20-5 displays the default control lead configuration for
the MPA card interface in DTE mode for the different interface types. The control
signal condition can be set for a circuit even if that circuit is configured as a source
of system synchronization. It can also be changed if a circuit is connected.
Table 20.20-5: Default MPA Card Control Signal Configuration (DTE)
Control Lead Output Signal
Condition
RS-530-A
RS499
Forced off
Forced on
DTR
Forced on
RDL
Forced off
RTS
Forced on
LL
Forced on
RL
Forced off
(400)
V.35
ALB
X.21
20.20-13
The OOS condition is declared when an HCM framing synchronization is lost. This
can occur if, for example, there is a link failure. For each link on the MPA card, you
can configure the state of the output control leads during an OOS condition. One of
three states can be configured.
DTR
RTS
ON*/OFF
LL
RL
ON/OFF*
SK000780
where l is 1 to 4
20.20-14
(400)
DTR
RTS
LL
RL
OOS
ON
OFF
NONE*
SK000781
where l is 1 to 4
INVERT to enable it
NORMAL to disable it
The falling edge of the sampling clock is the default for the received data.
Note 1
The clock inversion feature of the MPA card is not compatible with the X.21 PRI
card. The X.21 PRI card inverts the sampling clock for transmitting data, whereas the
MPA card inverts the sampling clock for the receive data.
Note 2
Interface delay is determined by the cable length, device delays and the data rate.
(400)
20.20-15
20.20-16
(400)
21.1
21.1.1
(400)
21.1-1
21.1.2
Options
Slot Level
Card slot
4WTO
Circuit Level
TLPs
21.1-2
(400)
Table 21.1-2 lists the E&M card configuration parameters. Each parameter has a list
of options with any default option marked by an asterisk.
Table 21.1-2: E&M Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
E+M
Companding law
Mu-law
A-law
type I*
type II
type III
type IV
type V*
Audio wires
2-wires*
4-wires
TLPs
900 W + 2.16 mF
600 W + 2.16 mF*
600 W
Circuit Level
Line balance (1)
nominal*
220 W + (820 W // 115 nF)
383 W + (536 W // 220 nF)
Fault signalling
seized
idle*
Notes
1. This parameter is applicable only for A-law cards.
Table 21.1-3 lists the LGE card configuration parameters. Each parameter has a list
of options with any default option marked by an asterisk.
(400)
21.1-3
Options
Slot Level
Card slot
Card type
LGE
(1)
6 cct
8 cct
Companding law
Mu-law
A-law
TLPs
900 W+ 2.16 mF
600 W + 2.16 mF*
600 W
Circuit Level
Signalling type for E1 signalling
remote extension
earth calling
loop calling disconnect clear (* for 6 cct A-law cards)
loop start
ground start (* for Mu-law cards)
dial pulse terminating
Line balance
<200 W*
>200 W
Fault signalling
seized
idle*
Notes
1. This parameter is applicable only for A-law cards.
Table 21.1-4 lists the LGS card configuration parameters. Each parameter has a list
of options with any default option marked by an asterisk.
21.1-4
(400)
Options
Slot Level
Card slot
LGS
Card type
6 cct Mu-law
12 cct Mu-law
8 cct A-law
10 cct A-law
12 cct A-law
Companding law
Mu-law
A-law
TLPs
600 W + 2.16 mF
900 W + 2.16 mF*
Circuit Level
Signalling type for E1 signalling
remote extension
earth calling
loop calling disconnect clear
PLAR (2)
central battery working
loop start
ground start
loop start to E&M conversion
ground start to E&M conversion
PLAR*
PLAR with D3 framing
Line balance
nominal*
800 W // (100 W + 50 nF) (1)
Fault signalling
seized
idle*
Notes
1. This option is applicable only for Mu-law cards.
2. PLAR is the E1 default signalling type for 10 cct and 12 cct A-law cards.
Table 21.1-5 lists the 4WDX channel unit configuration parameters. Each parameter
has a list of options with any default option marked by an asterisk.
(400)
21.1-5
Options
Slot Level
Card slot
4WDX
Circuit Level
Signalling mode
TLPs
Line impedance
150 W
600 W*
1200 W
Fault signalling
idle
seized*
Tx mute
enabled
disabled*
Loop balance
slope (4)
height (4)
bandwidth (4)
Notes
1. The valid range for build-out capacitance is 0 to 7 mF, step size 1 mF.
2. The valid range for build-out resistance is 1250 to 6250 W, step size 250 W.
3. The loaded, slope, height and bandwidth settings are configurable only when equalization is
enabled.
4. The valid range for slope, height and bandwidth is 0 to 15, step size 1.
Table 21.1-6 lists the E&M channel unit configuration parameters. Each parameter
has a list of options with any default option identified with an asterisk.
21.1-6
(400)
Options
Slot Level
Card slot
E+M
Card type
North America
Asia
Europe
other
Circuit Level
Companding law
Mu-law (1)
A-law (2)
Signalling mode
E&M*
pulse link repeater
transmission only
type I (4)
type II
type III
type IV
type V (5)
type V with filter
type I
type II
Audio wires
2-wire*
4-wire
TLPs
600 W + 2.16 mF
900 W + 2.16 mF*
Line balance
nominal*
alternate
continuous adapt
adapt and freeze
nominal*
continuous adapt
adapt and freeze
Fault signalling
seized
idle*
Tx mute (7)
enabled
disabled*
(400)
21.1-7
Notes
1. Default companding law for module variant IDs 01, 02, 03 and 04.
2. Default companding law for module variant IDs 05, 06 and 07.
3. Signalling types IV, V, and V with filter apply only to module variant IDs 03 through 07 (see
Table 6.6-4 for the list of module variant IDs and their associated country or region).
4. Default signalling type for module variant IDs 01, 02 and 03.
5. Default signalling type for module variant IDs 04, 05, 06 and 07.
6. See Table 6.6-4 for the list of module variant IDs and their associated country or region.
7. Restrictions: Applies to all E&M channel unit variants except 90-1230-01. Applies to 2-wire mode
only. To prevent audio path singing, the Tx mute parameter must be enabled on the called circuit.
While the Tx mute parameter is enabled, on-hook line up and test procedures cannot be performed,
because on-hook transmission is disabled.
Table 21.1-7 lists the LGE channel unit configuration parameters. Each parameter
has a list of options with any default option identified with an asterisk.
Table 21.1-7: LGE Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
LGE
Circuit Level
Signalling type for E1 signalling
loop start *
ground start
dial pulse terminating
TLPs
Line impedance
600 W + 2.16 mF
900 W + 2.16 mF*
Line balance
Fault signalling
seized
idle*
Tx mute (1)
enabled
disabled*
Notes
1. Restrictions: To prevent audio path singing, Tx mute must be enabled on the called circuit. While Tx
mute is enabled, on-hook line up and test procedures cannot be performed (that is, on-hook
transmission is disabled).
21.1-8
(400)
Table 21.1-8 lists the LGS channel unit configuration parameters. Each parameter
has a list of options with any default option identified with an asterisk.
Table 21.1-8: LGS Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
LGS
Card type
North America
Asia
Europe
other
Circuit Level
Companding law
Mu-law (1)
A-law (2)
TLPs
Line impedance
600 W + 2.16 mF
900 W + 2.16 mF*
(400)
21.1-9
Parameter
Line balance
Module variant ID 02
Options
Module variant ID 03
nominal*
alternate
continuous adaption
adapt and freeze
nominal*
continuous adaption
adapt and freeze
Fault signalling
seized
idle*
Tx mute (5)
enabled
disabled*
Notes
1. Default companding law for module variant IDs 02, 03 and 04.
2. Default companding law for module variant IDs 05, 06 and 07.
3. Default for module variant IDs 02 and 03 (see Table 6.8-5 for a list of module variant IDs and their
associated part numbers).
4. Default for module variant IDs 04, 05, 06 and 07 (see Table 6.8-5 for a list of module variant IDs and
their associated part numbers).
5. Restrictions: To prevent audio path singing, Tx mute must be enabled on the called circuit. While Tx
mute is enabled, on-hook line up and test procedures cannot be performed (that is, on-hook
transmission is disabled).
Table 21.1-9 lists the MRD channel unit configuration parameters. Each parameter
has a list of options with any default option identified with an asterisk.
21.1-10
(400)
Options
Slot Level
Card slot
MRD
Card type
on-premise 2-wire
off-premise 2-wire
Circuit Level
TLPs (1)
Line impedance
600 W + 2.16 mF
900 W + 2.16 mF*
Line balance
Notes
1. For transmit TLPs between 10 and 12 dBr, the hardware rounds off the TLPs in 0.3 dB increments.
2. Continuous adapt is available only on the 90-1755-02 variant.
Note
The formats of the identifiers in the procedures are explained in Table 16.4-1 in
chapter 16.4.
Configuring TLPs and fault signalling also applies to the 4WTO channel unit.
(400)
21.1-11
21.2
21.2.1
Tables 21.2-1 and 21.2-2 list the relationship between the country and region
identifiers for the E&M and LGS channel units and their variant identifiers.
(400)
21.2-1
Card
Identifier
Variant
Identifier
North America
$1C
01
E&M Version I
North America
$1C
02
North America
$1C
03
Japan
$C3
04
Germany
$C3
05
UK
$C3
06
France
$C3
07
Card
Identifier
Variant
Identifier
North America
$19
01
LGS Version I
North America
$19
02
North America
$19
03
Japan
$C0
04
Germany
$C0
05
UK
$C0
06
France
$C0
07
Companding laws
There are two types of companding law.
The Mu-law companding law is used most often in 1.544 Mb/s T1 environments.
The A-law companding law is typically used in 2.048 Mb/s E1 environments.
You select a companding law for each voice interface card as you configure the card
slot. For the E&M and LGS channel units, you select the companding law at the
circuit level. You do not need to select a law for the 4WTO Line card and the 4WDX,
LGE and MRD channel units, because they support only Mu-law companding.
21.2-2
(400)
21.2.2
If you change the companding conversion algorithm for a slot configured for a voice
card, all cross-connections for the slot are disconnected. If the new slot option does
not support the configured TLP range, you must select a new TLP range (see
chapter 21.5).
After you have configured the Common Carrier card slot, define the channel unit
position as:
(400)
21.2-3
AS_PRESENT
E+M
MuLaw
VOICE
LGS
LGE
ALaw
ALaw MuLaw
6_CIRCUIT
4W_TO
ALaw
MuLaw
8_CIRCUIT
6_CIRCUIT
8_CIRCUIT
12_CIRCUIT
10_CIRCUIT
12_CIRCUIT
SK000095
E+M
NA
JAPAN
AS_PRESENT
VOICE
LGS
MRD
LGE
ASIA
EUROPE
OTHER GERMANY
OTHER
ON_PREM_2W
DX
4-WIRE
OFF_PREM2W
UK FRANCE OTHER
SK000096
where sn is the Common Carrier card slot number and cc is the channel unit position (1 to 4)
21.2-4
(400)
Note 1
If your channel unit does not match any of the country values shown by the softkeys,
select the OTHER softkey and see the documentation provided with the unit.
Note 2
If you install an off-premise MRD in a Common Carrier card position that is
configured for an on-premise MRD, the channel unit will function as if it is an
on-premise MRD.
(400)
21.2-5
21.3
21.3.1
(400)
21.3-1
Signalling leads
2-wire
PLR
4-wire
E&M Type I
Connecting Equipment
Node
On-hook
Off-hook
On-hook
Off-hook
Grounds
M lead
Provides
battery to
M lead
Opens E
lead
Grounds
E lead
E&M Type II
Opens
relay
between
M and SB
leads
Closes
relay
between
M and SB
leads
Opens
relay
between E
and SG
leads
Closes
relay
between E
and SG
leads
Closes M
and SG
leads
Closes M
and SB
leads
Opens E
lead
Grounds
E lead
E&M Type IV
Same as Type II
E&M Type V
Opens M
lead
E&M Type V
with filter
Same as Type V
PLR Type I
Opens E
lead
Grounds
E lead
Grounds
M lead
Provides
battery to
M lead
Opens
relay
between E
and SG
leads
Closes
relay
between E
and SG
leads
Opens
relay
between
M and SB
leads
Closes
relay
between
M and SB
leads
PLR Type II
TO
Grounds
M lead
Grounds
E lead
A-law
Card
PLR CU
E&M CU
Type I
TYPE_I (2)
Type II
TYPE_II
Type III
TYPE_III
Type IV
TYPE_IV
Type V
TYPE_V (3)
V_FILTER
Signalling Type
Option
Notes
1. Mu-law E&M card (part number 90-0079-06) supports Type IV and V signalling.
2. TYPE_I is the default for Mu-law E&M cards (except part number 90-0079-06) and channel unit
variants (part numbers90-1230-01through 03).
3. TYPE_V is the default for A-law E&M cards, Mu-law E&M card (part number 90-0079-06) and
channel units (part numbers 90-1230-04 through 07).
21.3-2
(400)
Sensor
Sensor
48V
48V
Sensor
Sensor
48V
48V
Connecting equipment
E & M interface
Connecting equipment
E&M type I
E & M interface
E&M type V
SG
Sensor
Sensor
48V
48V
1 uf
SB
48V
M
Connecting equipment
48V
E & M interface
Connecting equipment
E&M type II
Sensor
Sensor
Sensor
E & M interface
48V
Sensor
48V
SG
M
Sensor
Sensor
M
48V
SB
Connecting equipment
48V
E & M interface
Connecting equipment
E & M interface
PLR type I
SG
SG
Sensor
48V
Sensor
48V
SB
SB
48V
Sensor
Sensor
48V
Connecting equipment
E & M interface
Connecting equipment
E&M type IV
E & M interface
PLR type II
6827
(400)
21.3-3
TYPE-I
TYPE-II
TYPE-III
TYPE-IV
TYPE-V
SK000097
TO
E+M
TYPE-I
TYPE-II
TYPE-III TYPE-IV
PLR
TYPE-V V_FILTER
TYPE-I
TYPE-II
SK000098
where sn is the Common Carrier card slot number and cc is the channel unit position number (1 to 4)
21.3.2
21.3-4
(400)
Type
E1
T1
Characteristics
ABCD Bits
Idle
Seized
PLAR
Private Line
Automatic
Ringdown
1101
0101
CBW
Remote
Extension
with Central
Battery
Working
1101
0101
(ring)
LCDC
Loop Calling
Disconnect
Clear
1101
0101
EC
Earth Calling
1101
0101
REM_EXT
Remote
Extension
1101
0101
LS
Loop Start
01
11
LS_EM
Loop Start to
E&M
Conversion
00
11
GS
Ground Start
01
00
GS_EM
Ground
Start to E&M
Conversion
00
11
PLAR
Private Line
Automatic
Ringdown
00
11
PLAR_D3
Private Line
Automatic
Ringdown
D3
11
00
(400)
21.3-5
LGS Card
or CU
Signalling Type
Option
CBW
DPT
Earth Calling
EC
Ground Start
GS (1)
GS_EM
LCDC (2)
Loop Start
LS (3)
LS_EM
PLAR
Remote Extension
REM_EXT
Notes
1. GS is the default for Mu-law LGE cards.
2. LCDC is the default for A-law LGE cards.
3. LS is the default for LGE channel units and LGS channel units (part numbers 90-1229-01 through
03).
4. PLAR is the default for LGS cards and LGS channel units (part numbers 90-1229-04 through 07).
21.3-6
(400)
E1_SIG
REM_EXT
T1_SIG
EC
LCDC
LS
GS
DPT
SK000099
T1_SIG
E1_SIG
PLAR CBW
LS_EM
LCDC
LS
EC
GS
REM_EXT
GS_EM
PLAR PLAR_D
SK000100
21.3.3
(400)
21.3-7
48V
Normal
A-lead
Reverse
On/off
hook
detector
B-lead
Reverse
T1
Bias
48V
R1
7623
Table 21.3-5 lists how the signalling modes apply to the 4WDX channel unit.
21.3-8
(400)
Characteristics
NORM_POL
The A-lead is simplexed onto the T and R pair and the B-lead is simplexed onto the
T1 and R1 pair.
REV_POL
The A-lead is simplexed onto the T1 and R1 pair and the B-lead is simplexed onto
the T and R pair.
FIXED_BIAS
It applies grounding to the A-lead when the call is on-hook and nominal 48 V dc
to the A-lead conductor when the call is off-hook. It applies a constant voltage of
approximately 19 V dc to the B-lead conductor.
SW_BIAS
It applies grounding to the A-lead when the call is on-hook and nominal 48 V dc
to the A-lead conductor when the call is off-hook. It applies nominal 48 V dc to the
B-lead conductor when the call is on-hook and grounding to the B-lead conductor
when the call is off-hook.
Warning
Before connecting a Newbridge 4WDX channel unit to a non-Newbridge 4WDX
channel unit, ensure that both 4WDX channel units are configured for the same type
of bias signalling. Otherwise, damage may occur to the non-Newbridge 4WDX
channel unit.
NORM_POL*/REV_POL
FIXED_BIAS*/SW_BIAS
SK000676
Note 1
Signalling polarity or bias cannot be changed when the circuit is connected.
Note 2
Two 4WDX interfaces can be connected together by configuring one interface for
normal signalling and the other interface for reverse signalling.
(400)
21.3-9
21.4
Audio Wires
This chapter describes how to configure audio wires for E&M cards and channel
units.
21.4.1
21.4.2
(400)
21.4-1
21.5
21.5 TLPs
Issue 1, November 1997
TLPs
This chapter describes how to configure:
21.5.1
Analog
side
Rx
Tx
Voice circuit
7898
The TLPs are measured in dBm, which is the power of a signal relative to a signal of
1 mW.
A TLP is measured with respect to 0 dBm on the digital side. The 0 dBm value is
equal to 1 mW of power imposed on an impedance of 600 W or 900 W at a frequency
of 1004 Hz. On the digital side, 0 dBm is the digital signal power required to produce
0 dBm on the analog side of a standard digital-to-analog converter.
(400)
21.5-1
21.5 TLPs
Issue 1, November 1997
21.5.2
Specification
Transmit TLP Range
Receive TLP Range
90-2687-01
Line Impedance
600 W
Notes
1. D = increment in dB.
Table 21.5-2: TLP Levels and Line Impedance for E&M Cards
E&M Card
Specification
2-Wire
Transmit TLP Range
Receive TLP Range
4-Wire
Transmit TLP Range
Receive TLP Range
90-0091-06
E&M (6) 600C (4-3/0-7) U
90-0079-03
E&M (6) ZCO (8-7/1-14) A
4W: 600 W
90-0079-04
90-0079-03
E&M (6) 600C (8-7/1-14) A
2W: 600 W
4W: 600 W
90-0079-05
90-0079-03
E&M (6) 600C (8-7/1-14) A
90-0079-06
E&M (6) 600C (8-7/1-14) U
90-0091-05
E&M (6) 900C (4-3/0-7) U
Notes
1. 2W = 2-wire; 4W = 4-wire.
2. D = increment in dB.
3. // = in parallel with.
21.5-2
(400)
21.5 TLPs
Issue 1, November 1997
Table 21.5-3: TLP Levels and Line Impedance for LGE Cards
LGE Card
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
Companding
Law
600 W
Mu-law
600 W + 2.16 mF
Mu-law
900 W + 2.16 mF
Mu-law
90-0343-03
LGE (6) PROG (3-4/2-13) A
A-law
90-0343-04
LGE (6) 600C (0-7/2-13) U
600 W + 2.16 mF
Mu-law
90-0343-05
LGE (6) 900C (0-7/1-14) U
900 W + 2.16 mF
Mu-law
90-0343-06
LGE (6) PROG (3-4/2-13) U (RDG)
600 W + 2.16 mF
Mu-law
900 W + 2.16 mF
Mu-law
90-0343-07
LGE (6) PROG (3-4/2-13) A
(REM EXT)
Mu-law
90-0343-01
LGE (6) 600R (3-4/2-13) U
600 W
Mu-law
90-0343-02
LGE (6) PROG (3-4/2-13) U
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
90-0343-03
LGE (6) PROG (3-4/2-13) A
A-law
90-0343-04
LGE (6) 600C (0-7/2-13) U
600 W + 2.16 mF
Mu-law
90-0343-05
LGE (6) 900C (0-7/1-14) U
900 W + 2.16 mF
Mu-law
90-0343-06
LGE (6) PROG (3-4/2-13) U (RDG)
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
600 W + 2.16 mF
900 W + 2.16 mF
Mu-law
A-law
90-0343-01
LGE (6) 600R (34-3/3-4) U
90-0343-02
LGE (6) PROG (3-4/2-13) U
90-0343-07
LGE (6) PROG (3-4/2-13) A
(REM EXT)
(400)
21.5-3
21.5 TLPs
Issue 1, November 1997
Notes
1. D = increment in dB.
2. // = in parallel with.
Table 21.5-4: TLP Levels and Line Impedance for LGS Cards
LGS Card
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
Companding
Law
90-0029-01
LGS (12) ZCO(4-3/1-6) A
A-law
90-0029-02
LGS (10) ZCO(4-3/1-6) A
A-law
90-0030-01
LGS (12) 600R(4-3/1-6) U
600 W + 2.16 mF
Mu-law
90-0030-02
LGS (6) 600C(0-7/0-7) U
600 W + 2.16 mF
Mu-law
90-0030-03
LGS (6) 900C(0-7/0-7) U
900 W + 2.16 mF
Mu-law
90-0030-04
LGS (12) 900R(4-3/1-6) U
900 W + 2.16 mF
Mu-law
90-0029-05
LGS (12) 600 W A
600 W
A-law
Notes
1. D = increment in dB.
2. // = in parallel with.
21.5-4
(400)
21.5 TLPs
Issue 1, November 1997
Table 21.5-5: TLP Levels and Line Impedance for E&M Channel Units
E&M CU
Specification
Line Impedance (1)
2-Wire
Transmit TLP Range
Receive TLP Range
4-Wire
Transmit TLP Range
Receive TLP Range
90-1230-02
90-1230-03
90-1230-04
90-1230-05
90-1230-06
90-1230-07
90-1230-01
Notes
1. 2W = 2-wire; 4W = 4-wire.
2. D = increment in dB.
3. // = in parallel with.
Table 21.5-6: TLP Levels and Line Impedance for LGE and LGS Channel Units
LGE and LGS CU
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
90-1229-01
LGE
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-01
LGS
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-02
LGS
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-03
LGS
600 W + 2.16 mF
900 W + 2.16 mF
90-1228-04
LGS
600 W + 1.0 mF
(400)
21.5-5
21.5 TLPs
Issue 1, November 1997
Specification
Transmit TLP Range
Receive TLP Range
Line Impedance
90-1228-05
LGS
90-1228-06
LGS
90-1228-07
LGS
Notes
1. D = increment in dB.
2. // = in parallel with.
Table 21.5-7: TLP Levels and Line Impedance for the 4WDX Channel Unit
4WDX CU
Specification
Transmit TLP Range
Receive TLP Range
90-2769-01
Line Impedance
150 W
600 W*
1200 W
Notes
1. D = increment in dB.
Table 21.5-8: TLP Levels and Line Impedance for MRD Channel Units
MRD CU
Specification
(1)
Line Impedance
900 W + 2.16 mF
10 to +6 (8.0), D0.1
90-1755-02
12 to +6 (+6.0), D0.1
10 to +6 (8.0), D0.1
600 W + 2.16 mF
900 W + 2.16 mF*
Notes
1. For transmit TLPs between 10 and 12 dB, the hardware rounds off the TLPs in 0.3 increments.
For example, if you enter 10.1, it uses a transmit TLP of 10.0; if you enter 10.2, it uses a transmit
TLP of 10.3.
2. D = increment in dB.
21.5-6
(400)
21.5 TLPs
Issue 1, November 1997
To select TLP levels for voice interface cards and channel units
CONFIG CIRCUIT <sn-cc> or <sn-cc-1> LEVELS
RX_TLP
TX_TLP
<tpl_level>
SK000101
where tlp_level is the appropriate TLP level from Tables 21.5-1 through 21.5-6 (for 4WTO channel units,
TLP level is 17.0 to +13.0 [TX_TLP] and -16.0 to +8.0 [RX_TLP] in increments of 0.1 dB)
21.5.3
(400)
21.5-7
21.5 TLPs
Issue 1, November 1997
21.5-8
(400)
21.6
Line Impedance
This chapter describes how to configure line impedance for voice interface cards and
channel units.
21.6.1
E&M
Mu-law
Card
LGE, LGS
A-law
Card
LGE, LGS
Mu-law
Card
4WDX
CU
E&M, LGE,
LGS, MRD
CU
Option
370C
600 W
600
Line Impedance
600 W + 2.16 mF
600+2.1
900 W + 2.16 mF
900+2.1
600 W + 2.16 mF
600+2.16
900 W + 2.16 mF
900+2.16
150
600*
1200
(400)
21.6-1
21.6.2
E&M cards programmed for four audio wires always have a line impedance of
600 W. Although you can configure line impedance for these cards, the configuration
has no effect and the node manager generates a Wrong card in Slot alarm.
If you select 900 W + 2.16 mF for a LGS Mu-law card, you introduce a 1.76 dB loss that
raises the TLP ranges by 2 dB. The system displays the warning The corresponding
gains must be selected. It rejects the card with a Wrong card in Slot message until
you select a new TLP range.
21.6-2
(400)
600
600+2.1
900+2.1
370C
SK000103
600+2.16
900+2.16*
SK000104
(400)
21.6-3
600*
150
1200
SK000105
21.6-4
(400)
21.7
Line Balance
This chapter describes how to configure line balance for voice interface cards or
channel units.
21.7.1
21.7.2
(400)
21.7-1
Table 21.7-1 lists the fixed balanced impedances for each variant of the E&M and
LGS channel units.
Table 21.7-1: Balanced Impedance for E&M/LGS Channel Units
Country
Balanced Impedance
FIX_SHORT/NOMINAL
Variant
FIX_LONG/ALTERNATE
North America
600 W + 2.16 mF
01, 02, 03
North America
900 W + 2.16 mF
01, 02, 03
Japan
600 W + 1.00 mF
04
Germany
n/a
05
UK
n/a
06
France
600 W
07
If you choose adapt and freeze, the system provides two further options:
21.7-2
(400)
After you establish existing coefficients, you can calibrate line balance to cause the
channel unit to re-adapt to its existing coefficients. During the calibration of line
balance, the re-adapt option instructs the channel unit to adapt to the line for
approximately 0.5 seconds. The channel unit retains and uses these coefficients until
you select re-adapt again or change the line balance mode. For RE-ADAPT to
operate, the system needs a GFC, GFC2 or GFC3 and a white noise source.
Note
To calibrate the line balance coefficients for the channel units, see Maintenance,
chapter 40.1.
For the MRD (variant 02) and 2-wire E&M and LGS channel units (variants 03
through 07), you can also select CONTINUOUS for continuously adapting line
balance. In this mode, the channel unit continuously adapts the transhybrid loss
optimization on the line.
RE_ADAPT
SK000106
Note
If the E&M channel unit is configured for four audio wires and you select
LINE_BAL, the system displays the message Invalid configuration.
(400)
21.7-3
21.8
21.8.1
21.8.2
SEIZED
IDLE
SK000107
(400)
21.8-1
21.9
21.9 Tx Mute
Issue 1, November 1997
Tx Mute
This chapter describes how to configure the Tx Mute parameter for the 4WDX,
2-wire E&M, LGE and LGS channel units.
21.9.1
Voice card or
channel unit
Tx
Off-hook
Called phone
Voice
channel unit
Tx
Rx
Rx
On-hook
8795
The Tx mute parameter prevents audio loop singing by disabling the transmit path
of the called telephone, as shown in Figure 21.9-2. When the called telephone goes
off-hook, the transmit path is enabled. Echo cancellation circuitry on the voice cards
and channel units prevents singing while both telephones are off-hook.
Figure 21.9-2: Tx Mute
Calling phone
Off-hook
Voice card or
channel unit
Called phone
Voice
channel unit
Tx
Tx
Rx
Rx
On-hook
(400)
21.9-1
21.9 Tx Mute
Issue 1, November 1997
21.9.2
Name
1117-H1-00
Toronto:A
Type
Alarms:1
Function
A1-01-01
LGS_LS
Rx -2.0,Tx +0.0
Configured
RX TLP Range
TX TLP Range
Line Impedance
Line Balance
On-hook TX Mute
:
:
:
:
:
11-May-1997
8:35a
Fault
Status
IDLE
Configured
-10.0 to +6.0
-12.0 to +0.0
900 Ohms+2.16uF
Fixed Short
Enabled
2-TX TLP
7-
3-TXMUTE_OFF
8-CANCEL
49-QUIT
50-
Tx mute restrictions
The following restrictions apply.
To prevent audio path singing, the Tx mute parameter must be enabled on the
called circuit.
While the Tx mute parameter is enabled, you cannot do on-hook line-up and test
procedures (on-hook transmission is disabled).
21.9-2
(400)
21.10
Loop Balance
This chapter describes how to configure loop balance for the 4WDX channel unit.
21.10.1
Loop Balance
Options
Definition
Range
Mid-point capacitance
ENABLE*/DISABLE
Build-out capacitance
Build-out resistance
Notes
1. Default setting is 1250 W. This represents an external loop resistance of 0 W.
21.10.2
(400)
21.10-1
MP_CAP_DIS/MP_CAP_ENA*
B_O_CAP
B_O_RES
SK000108
21.10-2
(400)
21.11
21.11 Equalization
Issue 1, November 1997
Equalization
This chapter describes how to configure the equalization parameter for the 4WDX
channel unit.
21.11.1
21.11.2
Description
Range
Loaded/non-loaded
LOADED/NON_LOADED
Slope
Bump height
Bump bandwidth
(400)
21.11-1
21.11 Equalization
Issue 1, November 1997
Name
1117-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Type
Function
Fault
A1-01-01
4W_DX
Rx 0,Tx 0
SEIZED Configured
Configured:
RX_TLP Range
:
TX_TLP Range
:
Line Impedance :
Line Balance
:
On-hook Tx Mute:
Companding Law :
Equalization
Facility
Slope
Height
Bandwidth
:
:
:
:
:
-10.5 to
-15.0 to
600 Ohms
N/A
Disabled
MuLaw
Disabled
Non-Loaded
0
0
0
Status
+6.0
+1.5
Signalling
Bias
Midpoint Cap
Build Out Cap
Build Out Res
:
:
:
:
:
Normal Polarity
Fixed
Enabled
4 uF
1250 ohms
1-ENABLE
6-
2-LOADED
7-
3-SLOPE
8-CANCEL
4-HEIGHT
9-QUIT
5-BANDWIDTH
0-
ENABLE/
DISABLE*
LOADED/
NON_LOADED*
SLOPE
HEIGHT
BANDWIDTH
SK000109
When equalization is disabled, the equalization settings do not reset to their default
values.
21.11-2
(400)
22.1
the procedure for configuring the DCCs and the 2B1Q, 27LC2 and DNIC Line
22.1.1
cards
the procedure for configuring the 2B1Q, 27LC2 and DNIC Line cards for
connection to DTUs
a summary of the configuration procedures in this part of the manual, indicating
how they apply to each interface
The RS-232 DCC provides six full-duplex V.24/RS-232 interfaces that meet or
You can install DCCs in any UCS 1 to 8 of a locally controlled or peripheral shelf.
(400)
22.1-1
Each DNIC Line card circuit connects to three, six or twelve 2600 MainStreet
series DTUs. The DTUs can be located up to 5.8 km (3.6 mi) away, using a
standard twisted-pair wire.
Each 2B1Q Line card circuit connects to six 2700 MainStreet series DTUs. The
DTUs can be located up to 13.9 km (8.7 mi) away, using a standard twisted-pair
wire.
Each 27LC2 Line card circuit connects to six 2715 MainStreet DTUs. The DTUs
can be located up to 13.9 km (8.7 mi) away, using a standard twisted-pair wire.
You can install line cards in any UCS 1 to 8 of a locally controlled or peripheral shelf.
Table 22.1-1 lists card functions and indicates which ones apply to the DPM card
modules or variants.
Table 22.1-1: DNIC, 2B1Q and 27LC2 Line Card Functions
Line Card
Function
Transparent/HCM SRMs
DDS SRMs
X.50 SRMs
4 kb/s CPSS
Line cards connect to DTUs at the customer premises. The DTU connects to between
two and eight user data devices. Tables 22.1-2 and 22.1-3 list the 2600 MainStreet
series DTUs and 2700 MainStreet series DTUs.
Table 22.1-2: 2600 MainStreet Series DTU Types
DTU
22.1-2
Type
Device
Ports
Interface Type
2601
Synchronous or Asynchronous
V.24/RS-232
2602
Synchronous
X.21/V.11
2603
Synchronous
2606
2608
V.35
Synchronous or Asynchronous
(1)
V.24/RS-232
Asynchronous
8 (1)
V.24/RS-232
(400)
DTU
Type
Device
Ports
Interface Type
2610 (2)
2 (1)
V.24/RS-232
2611 (3)
2612
Synchronous or Asynchronous
IBERT
V.24/RS-232
2613
Synchronous IBERT
V.35
2614
Synchronous FRAD
V.24/RS-232
Notes
1. All device ports must be configured identically.
2. The 2610 MainStreet DTU connects up to two asynchronous VT100-compatible devices to a 4602
MainStreet Intelligent NetworkStation or MainStreetXpress 46020 Network Manager over CPSS.
The 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020 Network Manager then
supports an on-screen VT100 Terminal session.
3. On the interface, the 2611 MainStreet DTU is recognized as a 2603 MainStreet DTU
Type
Device Ports
Interface Type
2701
Synchronous or
Asynchronous
V.24/RS-232
2702
Synchronous
X.21/RS-449
2703
Synchronous
V.35
2704
Synchronous or
Asynchronous with V.110
Rate Adaption
V.24/RS-232
2715
Synchronous or
Asynchronous
2720
Fixed-link FRAD
Ethernet-attached IP
2721
Fixed-link FRAD
unlimited
Ethernet-attached IP
and/or IPX
(400)
22.1-3
90-0470-04
Function
Synchronization source
8 kHz timing
AIS enabling/disabling
Trunk conditioning
Fault signalling
Signalling types
Bidirectional connections
Unidirectional connections
22.1-4
(400)
(400)
22.1-5
22.1.2
Line Cards
Step
22.1.3
Connect the data circuit to the SRM or a primary rate or data link.
Connecting DTUs
Most of the parameters you configure for the line cards are used to configure the
attached DTU.
position
rate adaption method
data length, stop bits, parity
signalling, interface speed,
data position
clocking
RTS/CTS delay
multi-drop
control leads
duplex method
To configure the parameters for the DNIC, 2B1Q or 27LC2 Line cards, see
Table 22.1-7. The 2B1Q channel unit, when configured to support a 2700
MainStreet series DTU, has the same configuration parameters as do the DNIC
and 2B1Q Line cards.
22.1-6
(400)
Note
For the 27LC2 line card with a firmware revision of 3 or greater, the EOC feature can
be enabled to provide loss of DTU connectivity reporting to the system.
2.
Set the following parameters for aggregate port B (this configures aggregate
port A and all eight branch ports):
device mode
control leads
clocking
position
data length, stop bits, parity
To configure the parameters for the DNIC Line cards, see Table 22.1-7.
2.
Set the following parameters for port B (which represents all eight branch
ports):
device mode
control leads
data length, stop bits, parity
clocking
interface speed
To configure the parameters for the DNIC Line cards, see Table 22.1-7.
(400)
22.1-7
3.
device mode
RTS/CTS delay
control leads
data length, stop bits, parity
clocking
interface speed
To configure the parameters for the DNIC Line cards, see Table 22.1-7.
2.
22.1.4
RS-232
X.21
V.35
RS-422
Parameter
Options
CPSS
Card type
RS-232 DCC
X.21 DCC
V.35 DCC
RS-422 DCC
Circuit number
3 circuit
4 circuit
6 circuit
Card Level
Slot Level
22.1-8
(400)
RS-232
X.21
V.35
RS-422
Parameter
Options
Card operation
super-rate operation*
SRM operation
Interface type
RS-530-A*
RS-499/V.36
X.21
V.35
Circuit Level
Device mode
synchronous*
asynchronous
Device gender
DTE
DCE*
Duplex method
half duplex
full duplex*
RTS/CTS delay
0* to 1250 ms in 10 ms increments
RTS/CTS delay
0* to 160 ms in 5 ms increments
LL enable
LL disable
RL enable
RL disable
mark
space
custom
internal
external
slave*
special (DCE external; slip buffer not
present)
(400)
22.1-9
RS-232
X.21
V.35
RS-422
Parameter
Options
independent
locked*
enabled
disabled*
6 bits
7 bits
8 bits*
1 bit*
2 bits
Parity (2)
no parity*
odd
even
mark
space
Inversion
enabled
disabled*
enable
disable*
enable
disable
Super-rate circuit
transparent
enhanced transparent
master
slave
disabled*
Interface speed
master
slave
disabled*
transparent
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
Transport position
B7* to B0
22.1-10
(400)
RS-232
X.21
V.35
RS-422
Parameter
Options
Signalling
switched on*
switched off
F0-B7 to F9 to B0 (* = F0-B5)
HCM async
DDS sync
DDS async
X.50 sync
56000
48000
n x m, where n = 2, 4, 6, 8, 10, 12, 14,
16, 18, 20, 22, 24, 26, 28 and 31 and m
= 64, 56, 48, 40, 32, 24, 16 and 8
Super-rates
transparent
HCM*
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
1 to 8* (8 kb/s to 64 kb/s*)
B7* to B0
Data position
F0-B7 to F9 to B0 (* = F0-B5)
Notes
1. This option applies only to synchronous interfaces.
2. This option applies only to asynchronous interfaces.
3. This option applies only to RS-422 DCCs.
4. In an RS-232 DCC, interface speeds greater than 38400 b/s are possible but not guaranteed. For speeds above 38400 b/s,
use V.35 or X.21 interfaces. If you try speeds above 38400 b/s for RS-232, use short-grade shielded cable.
(400)
22.1-11
Table 22.1-7 lists the line card configuration parameters. Each parameter has a list of
options with any default option marked by an asterisk.
Table 22.1-7: Line Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
2B1Q
DNIC
3 circuit
6 circuit
12 circuit
Module type
DPM
DPM2
none
Hub ID (2)
CPSS
Circuit Level
22.1-12
enabled
disabled
Device mode
synchronous*
asynchronous
Device gender
DTE
DCE*
Duplex method
half duplex
full duplex*
RTS/CTS delay
0* to 1250 ms in 10 ms increments
internal
external
slave*
independent
locked*
(400)
Parameter
Options
6 bits
7 bits
8 bits*
1 bit*
2 bits
Parity (5)
no parity*
odd
even
mark
space
enable
disable*
enable
disable
Super-rate circuit
master
slave
disabled*
enable
disable*
mate
no mate
0 to 255000 ms in 1 ms increments
50 ms
250 ms
1000 ms
2000 ms
custom (0 to 300000 ms in 1 ms increments)
transparent
HCM*
DDS
X.50
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
Transport position
B7* to B0
Signalling
switched on*
switched off
(400)
22.1-13
Parameter
Options
HCM async
DDS sync
DDS async
X.50 sync
Data position
F0-B7 to F9 to B0 (* = F0-B5)
transparent
HCM*
DDS-HCM
X.50
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
1 to 8* (8 to 64 kb/s*)
B7* to B0
Interface speed
Continuity checking
enabled
disabled*
22.1-14
transparent
HCM*
DDS-HCM
X.50
Transport bandwidth
1 to 8* (8 to 64 kb/s*)
Transport position
B7* to B0
Signalling
switched on*
switched off
Interface speed
Data position
F0-B7 to F9 to B0 (* = F0-B5)
Composite inputs
composite
not composite*
Input specification
system*
user
(400)
Parameter
Options
0 to 4
enabled
disabled*
Notes
1. This parameter applies only to DNIC cards.
2. This parameter applies only when the line card is configured for DDS or DDS access.
3. Alarm suppression is available only on the 27LC2 and six-circuit DNIC Line cards with a variant ID
of $2.
4. This option applies only to synchronous interfaces.
5. This option applies only to asynchronous interfaces.
6. These parameters apply only to a 2715 MainStreet DTU.
7. In an RS-232 DCC, interface speeds greater than 38400 b/s are possible but not guaranteed. For
speeds above 38400 b/s, use V.35 or X.21 interfaces. If you try speeds above 38400 b/s for RS-232,
use short-grade shielded cable.
8. This option applies only to the 27LC2 line card.
Table 22.1-8 lists the 64 kb/s Codirectional card configuration parameters. Each
parameter has a list of options with any default option marked with an asterisk.
Table 22.1-8: 64 kb/s Codirectional Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card slot
64 kb/s Codirectional
Trunk conditioning
one-way
two-way*
Alarm time
Declare
Clear
0.1 to 60 s
0.1 to 60 s
Circuit Level
Fault signalling
seized
idle*
OOS-A
OOS-B
none
(400)
22.1-15
Parameter
Options
transparent*
clear channel
E&M
continuous E&M
LGS RE
LGS EC
LGS PLAR
LGE RE
LGE EC
R2 digital signalling
transparent
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Terminate
8 kHz timing
AIS
Table 22.1-9 lists the DS0-DP channel unit configuration parameters. Each parameter
has a list of options with any default option marked by an asterisk.
Table 22.1-9: DS0-DP Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
DS0-DP
Circuit Level
22.1-16
Fault signalling
MOS*
CMI
Interface speed
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
(400)
Table 22.1-10 lists the OCU-DP channel unit configuration parameters. Each
parameter has a list of options with any default option marked by an asterisk.
Table 22.1-10: OCU-DP Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
OCU-DP
Circuit Level
Fault signalling
seized*
idle
Interface speed
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
64 kb/s
Error correction
enabled*
disabled
enabled
disabled*
enabled
disabled*
Table 22.1-11 lists the 4WTO channel unit configuration parameters. Each parameter
has a list of options with any default option marked by an asterisk.
Table 22.1-11: 4WTO Channel Unit Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
4WTO
TLP level
Tx TPL
Rx TPL
Circuit Level
Sealing current
enabled
disabled*
Table 22.1-12 lists the 2B1Q channel unit configuration parameters when it is
configured for 3DS0 and 5DS0 ISDN loop extension mode. Each parameter has a list
of options with any default option marked by an asterisk.
The 2B1Q channel unit, when configured to support a 2700 MainStreet series DTU,
has the same configuration parameters as do the DNIC, 2B1Q and 27LC2 Line cards.
For a list of the configuration parameters, see Table 22.1-7.
(400)
22.1-17
Options
Slot Level
Card slot
2B1Q
DTU*
loop extension
3DS0
5DS0
LULT*
LUNT
Circuit Level
Performance monitoring
enabled*
disabled
enabled*
disabled
low nibble*
high nibble
Notes
1. This parameter is available only for the channel unit loop extension application.
2. This parameter is available only for 3DS0 or 5DS0 transport modes.
3. This parameter is available only for 3DS0 transport mode.
4. This parameter is available only for 5DS0 transport mode.
Note
The formats of the identifiers in the procedures are explained in Table 16.4-1 in
chapter 16.4.
22.1-18
(400)
22.2
22.2.1
22.2.2
(400)
22.2-1
TYPE
AS_PRESENT
OPTIONS
DATA
DCC
RS-232_DCC
X.21_DCC
4_CIRCUIT
V.35_DCC
6_CIRCUIT
3_CIRCUIT
RS-422_DCC
6_CIRCUIT
SK000110
Note
Use the AS_PRESENT softkey if the card is installed in the slot.
22.2.3
22.2-2
(400)
If you configure the card with DPM2, you must specify the rate adaption method
(METHOD) as:
If you configure the card for DDS_ACCESS, you must select VERSION_1 or
VERSION_2.
If you configure the card for DDS or DDS_ACCESS, you can set a hub identification
with the HUB_ID softkey.
If you configure the card for X.50_TELCO, you must select DIV_2 or DIV_3.
If you have a 27LC2 line card, configure the slot type as 2B1Q. When you physically
insert the 27LC2 line card into the slot, the system recognizes the correct card type.
TYPE
OPTIONS
AS_PRESENT
DATA
MORE
DNIC
NO_DPM*
DPM
2B1Q
HCM_TRANS* DDS X.50 DDS_ACCESS X50_TELCO
3_CIRCUIT
6_CIRCUIT
12_CIRCUIT
DIV_2
VERSION_1
DIV_3
VERSION_2
SK000111
(400)
22.2-3
Note
Use the AS_PRESENT softkey if the card is installed in the slot.
22.2.4
22.2.5
For the 2B1Q channel unit, you must also configure the unit application as one of the
following:
22.2-4
(400)
Note
When you change a 2B1Q channel unit application, the system removes any existing
connections to the unit. For more information on 2B1Q channel unit applications, see
section 22.3.25.
DS-0_DP
OCU_DP
2B1Q
4W_TO
SK000112
where
sn is the Common Carrier card slot
cc is the position number of the channel unit (1 to 4)
APP
DTU*
I/F_MODE
LOOP_EXT
3_DS0
LULT*
LUNT
5_DS0
SK001047
where
sn is the Common Carrier card slot
cc is the position number of the 2B1Q channel unit (1 to 4)
(400)
22.2-5
22.3
22.3.1
22.3.2
DCCs
Line cards
64 kb/s Codirectional cards
DS0-DP channel units
OCU-DP channel units
4WTO channel units
2B1Q channel units
RS-530*
RS-499/V.36
X.21
V.35
SK000113
(400)
22.3-1
22.3.3
22.3.4
22.3-2
(400)
Note
To change the gender offered by a DCC interface, you must change the cable or the
headshell or both. When the UDP is used with an RS-422 DCC, you must change the
interface module.
22.3.5
(400)
22.3-3
22.3.6
Note
You can set the RTS/CTS delay only when a circuit is configured with half-duplex
mode (see section 22.3.5) or as a multidrop slave (see section 22.3.12).
22.3.7
X.21
DCC
RS-422
DCC (1)
Line
Card
22.3-4
Signal
Parameter
Analog Loopback
ALB
Control
Clear to Send
CTS
DCD
DSR
(400)
RS-232 and
V.35 DCCs
X.21
DCC
RS-422
DCC (1)
Line
Card
Signal
Parameter
DTR
Indication
Local Loopback
LL
RDL
Ring Indicator
RI
Remote Loopback
RL
Request to Send
RTS
Test Mode
TM
Notes
1. Control signals for RS-422 DCCs depend on the interface mode selected.
If the device is DTE, the inputs are DSR, DCD, CTS and RI and the outputs are DTR,
RTS, ALB and RDL. If the device is DCE, the inputs and outputs are reversed.
You can configure three types of parameters related to control leads:
(400)
22.3-5
Default
Control Signal
Output
Default
DCE Gender
DTR
END_TO_END
DSR
FORCED_ON
RTS
END_TO_END
DCD
END_TO_END (1)
ALB
END_TO_END
CTS
END_TO_END (1)
RDL
END_TO_END
TM
FORCED_OFF
LL
END_TO_END
END_TO_END
RL
END_TO_END
RI
FORCED_OFF
END_TO_END
DTE Gender
DSR
END_TO_END
DTR
FORCED_ON
DCD
END_TO_END (1)
RTS
END_TO_END
CTS
END_TO_END (1)
ALB
END_TO_END
TM
END_TO_END
RDL
FORCED_OFF
END_TO_END
LL
END_TO_END
RI
END_TO_END
RL
FORCED_OFF
END_TO_END
Notes
1. For HCM rate adaption, the default setting is END_TO_END. For DDS and X.50 rate adaption, the
default is FORCED_ON.
For 5 kb/s transparent channels, the system forces the value of RTS into bit position
eight when RTS is set to end-to-end. For a DNIC, 2B1Q or 27LC2 Line card, the
far-end DTU maps RTS to its own DCD lead going to DTE devices. With both DTUs
configured for end-to-end, the system maps RTS (in bit position eight) to DCD.
When a V.35 circuit is an AQA master, the system sets DTR to forced off; when it is
an AQA slave, the system sets DTR to forced on. Do not change the control leads;
any change could cause a protecting call to be dropped.
When an SRM on a DCC card carries both HCM and transparent rate adapted
circuits, the state of the RTS (for DCE) or DCD (for DTE) control signal follows that
of the transparent circuit. This will disrupt the HCM circuits unless the transparent
circuit's RTS (or DCD) signal is set to ASSUMED_ON.
For the 2602 MainStreet DTU, the system displays:
22.3-6
(400)
The 2608 MainStreet DTU B circuit (sn-cc-B), which configures the branch ports,
supports only two inputs (DTR and RTS) and two outputs (DSR and DCD). The
circuit is always DCE. This parameter is not relevant to the A circuit (sn-cc-A), which
configures the aggregate port.
The control signals parameter is the only interface parameter that you can set for a
circuit that is configured as a source of system synchronization. It is also the only
interface parameter that you can change if a circuit is connected.
Configure control signals as:
INPUTS or
OUTPUTS
DTR
RTS
LL
RL
ALB
ON
RDL
RL_ENABLE/
RL_DISABLE*
LL_ENABLE/
LL_DISABLE*
OFF
DSR
DCD
CTS
TM
RI
END_TO_END
SK000114
(400)
22.3-7
CTRL_LEADS
MORE
OUTPUTS
DSR
DCD
CTS
OOS_DATA
DTR
RTS
ALB
RDL
TM
LL
RL
OOS
MARK
ON
OFF
NONE
SPACE
CUSTOM
<bits>
SK000115
22.3.8
Configuring Clocking
Clocking applies only to synchronous data interface devices. Synchronous devices
require two timing sources: a receive clock for receive data and a transmit clock for
transmit data. Transmit and receive are defined relative to the device configured as
DTE, so that the transmit clock is used by the DTE to transmit data and by the DCE
to receive data. Figure 22.3-1 illustrates transmit and receive clocks.
Figure 22.3-1: Transmit and Receive Clocks
Transmit clock
Transmit data
DTE
data
device
DCE
data
device
Receive data
Receive clock
1535
You can configure the transmit clock for all DCCs and line cards and receive clock
inversion for RS-422 DCCs.
22.3-8
(400)
Transmit clock
You can configure the source of the transmit clock between a DCC or line card circuit
and the attached local device as: the attached device (external), the DCC or line card
circuit (internal), or a remote source (slave). Setting this parameter depends on the
gender of the attached device and the gender (or device mode) of the connected DCC
or line card circuit (see Table 22.3-3).
Table 22.3-3: Transmit Clock Options
Attached
Device
Gender
DTE
DCE
Circuit
Gender
DTE
Transmit
Clock
Option
Description
DCE
External
DCE external: the transmit clock is provided by the attached device (the
XCLK pin from the DTE). The receive clock is derived from the XCLK.
Internal
DCE internal: the transmit clock is provided by an internal BRG (Baud Rate
Generator) on the DCC. The BRG is locked to the system timing. This mode
is not recommended; use DCE slave instead.
Slave
DCE slave: the transmit and receive clocks are derived from the BRG locked
to the system timing.
External
DTE external: the transmit clock is provided by the attached device (the
XCLK pin from the DCE). The receive clock is derived from the BRG.
Internal
DTE internal: not always valid if the interface is in DTE mode. Use slave or
external instead.
Slave
DTE slave: the transmit clock and the receive clock are supplied by the
attached DCE device (this is the default mode).
(400)
22.3-9
Note
Data interfaces configured for external independent clocking do not support
1.2 kb/s operation (see section 22.3.20).
DRAGA
Rx FIFO
Attached
Equipment
Gender
DTE or DCE
FIFO module
DTE
DCE
Tx FIFO
DTE
Rx FIFO
Tx FIFO
3435
The SBM provides a second FIFO that handles data exchanges between the DRAGA
and the synchronous DCC interface. It is designed to accommodate slips and
Doppler effects common in satellite tail circuits and plesiochronous applications.
The SBM always offers a hardware DTE to both the DRAGA and the synchronous
DCC interface (see Technical Overview, chapter 7.3).
The configuration of the following four parameters determines which clocks are
used to clock data to and from the RS-422 DCC:
22.3-10
(400)
Interface Type
DTE slave
DTE external
DCE internal
DTE internal
SBM Present
DCE external (DTE1 Mode)
Notes
1. DCE and DTE refer to RS-422 DCC circuit gender. All configurations can be further configured as
either locked or independent.
2. This mode is incompatible with existing DCCs. The RS-422 DCC supports separate SCT and SCR
clocks for RS-530-A, RS-449/V.36 and V.35 operation.
3. This mode is compatible with existing DCCs with firmware ID $09 or higher.
Configuration limitations
The following limitations apply to configuring clocking.
define the circuit with external clocking mode if it is DCE and slave clocking
mode if it is DTE.
The 2704 MainStreet DTU does not support any DTE clocking modes.
Table 22.3-5 lists some combinations of clocking options for DCCs and line cards
with DTUs for the configuration shown in Figure 22.3-3. (For more information on
clocking, ask your Newbridge representative for Configuration Note NCN305.)
(400)
22.3-11
DTU2
or DCC2
(DCE)
36120
MainStreet
node
Data
Network
Modem
or NTU
Terminal
Modem
or NTU
DTU1
or DCC1
(DTE)
DTU1
or DCC1
(DCE)
Terminal
7155
DCC/DTU2
(DCE)
HCM
Transparent
Slave
locked
Slave
locked
Yes
Yes
Slave
locked
External
locked
Yes
Yes
Slave
independent
External
independent
Yes
No
Slave
locked
Slave
locked
Yes
Yes
External
locked
Slave
locked
Yes
Yes
Slave
independent
Slave
independent
Yes
No
22.3-12
(400)
MODE
INTERNAL
SLAVE*
INDEPNT/LOCKED*
EXTERNAL
RX_INV/
NO_RX_INV*
SPECIAL
SK000116
Note 1
The SPECIAL and RX_INV/NO_RX_INV options apply only to RS-422 DCC
circuits.
Note 2
Clocking can only be configured for DCC and line card circuits operating in
synchronous mode.
22.3.9
(400)
22.3-13
Note
For the 2608 MainStreet DTU, character length, stop bits and parity can be set for the
B circuit (sn-cc-B), which configures the asynchronous branch ports. It is not relevant
to the A circuit (sn-cc-A), which configures the synchronous aggregate port.
STOP_BITS
CHAR_LEN
6_BITS
7_BITS
8_BITS
1_BIT*
NONE*
PARITY
2_BITS
ODD
EVEN
MARK
SPACE
SK000117
Note
Character length, stop bits and parity can only be configured for DCC and line card
circuits operating in asynchronous mode.
22.3.10
Configuring Inversion
You can configure RS-422 DCC circuits to invert data and signalling bits at the
interface. Inversion is sometimes necessary to maintain line synchronization by
ensuring a sufficient ones density.
Configure inversion as:
INVERT to cause all ones to be inverted to zeros and all zeros to ones
NORMAL to cause all bits to be transmitted and received in their normal state
(default)
To configure inversion
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION I/F_MODE MORE
INVERT/NORMAL*
22.3-14
(400)
22.3.11
DISABLE*
2_BYTES
4_BYTES
8_BYTES
16_BYTES
SK000118
22.3.12
DISABLE*
MASTER
SLAVE
SK000119
(400)
22.3-15
22.3.13
To propagate RTS
To propagate RTS, perform the following steps.
1.
2.
3.
The procedure for configuring control signals is described in section 22.3.7 and the
procedure for RTS/CTS delay is in section 22.3.6.
To disable propagation
To disable propagation, perform the following steps.
1.
2.
3.
The procedure for configuring control signals is described in section 22.3.7 and the
procedure for RTS/CTS delay is in section 22.3.6.
22.3-16
(400)
SIG_ON to enable it
SIG_OFF to disable it (default)
To configure control signal propagation
CONFIG CIRCUIT <sn-cc> or <sn-cc-p> FUNCTION RATE_ADAPT
METHOD
DDS_HCM
SIG_ON/
SIG_OFF*
X50_HCM
SK000120
22.3.14
configure transparent rate adaption for X.21 and V.35 circuits and enhanced
Transport bandwidth
The transport bandwidth must divide evenly into the interface speed. The resulting
number (the interface speed divided by the transport bandwidth) is called the
multiplier. See Figure 22.3-4.
Figure 22.3-4: Calculating the multiplier
interface speed
= multiplier
transport bandwidth
9067
The multiplier represents the number of primary rate DS0s (64 kb/s channels) the
super-rate circuit fills when it is connected. For most interface speeds, several
bandwidth and primary rate channel combinations are possible. For example, for a
448 kb/s device, the possibilities are:
56 kb/s by 8 channels
32 kb/s by 14 channels
16 kb/s by 28 channels
(400)
22.3-17
Although you must consider the multiplier in determining the allowable interface
speeds, do not enter it. Set the transport bandwidth, then the interface speed; the
system decides whether the interface speed is valid based on these rules.
Table 22.3-6 lists the rules for DCC interface speeds; nx represents the multiplier,
which equals the number of DS0s assigned to DCC circuit x.
Table 22.3-7 lists how to configure the speeds for DCC super-rate circuits. The
italicized areas indicate the optimum method of achieving bit rate. Figure 22.3-5
shows the maximum super-rate interface speeds for DCCs.
22.3-18
(400)
Rule
For configuring:
For connecting:
four-circuit X.21
The sum of n1, n2, n3, n4, n5 and n6 must be less than or equal to 31
n2, n3, n4, n5 and n6 must be a power of 2 (that is, occupy 1, 2, 4, 8 or 16 DS0s) (1)
For configuring:
For connecting:
three-circuit V.35
For configuring:
For connecting:
four-circuit RS-422
For configuring:
For connecting:
the sum of n1, n2, n3 and n4 must be less than or equal to 31 (for a single-bandwidth slot) or
62 (for a double-bandwidth slot)
(400)
22.3-19
Notes
1. This rule applies when the clock mode is set to external and the circuit is configured using the 4602 MainStreet Intelligent
NetworkStation and MainStreetXpress 46020 Network Manager. It does not apply when the clock mode is external and the
circuit is configured using an NMTI session.
Bits
per
DS0
10
12
14
16
18
20
22
24
26
28
30
64
128
256
384
512
640
768
896
1024
1152
1280
1408
1536
1664
1792
1920
56
112
224
336
448
560
672
784
896
1008
1120
1232
1334
1456
1568
1680
48
96
192
288
384
480
576
672
768
864
960
1056
1152
1248
1344
1440
40
32
128
192
256
320
384
448
512
576
640
704
768
832
896
960
24
16
96
128
160
192
224
256
288
320
352
384
416
448
480
80
96
112
128
144
160
176
192
208
224
240
1
2
3
4
30 x 64 max
30 x 64 max
30 x 64 max
31 x 64 max
ST bus
30 x 64 max
Channel
1
2
4 circuit
RS-422
3
4
31 x 64 max
31 x 64 max
31 x 64 max
ST bus
31 x 64 max
Channel
1
2
3
6-circuit
X.21,V.35
or RS-422
4
5
6
30 x 64 max
31 x 64 max
30 x 64 max
8 x 64 max
8 x 64 max
16 x 64 max
14 x 64 max
16 x 64 max
31 x 64 max
ST bus
14 x 64 max
8519
22.3-20
(400)
Clocking
You can configure the transmit clock for DCC super-rate circuits as slave or external,
but always configure DCC super-rate circuits as locked.
If a super-rate circuit is configured as a source of network synchronization and the
circuit is in DCE mode, configure it for external clocking mode; if it is in DTE mode,
select slave clocking mode.
DCC circuits configured as DTE need an external clock to support interface speeds
up to 1920 kb/s. Circuits configured as DCE receive clock information from the
DCC, which supports speeds of 128, 256, 512 and 1024 kb/s, plus one additional
speed for each card from 16 to 1920 kb/s in 8 kb/s increments.
An RS-422 DCC circuit configured as DTE needs an external clock to support
interface speeds up to 1984 kb/s. Circuits in DCE mode receive clock information
from the DCC.
If the clocking for a circuit is set to external and you want to change it to slave, you
must change the interface speed of the circuit first to conform with the slave rules.
As well as the configured speeds, DCC super-rate circuits support a 64 kb/s
interface speed. The procedure for configuring clocking is in section 22.3.8.
TRANSP_BW
METHOD
<bw>
TRANSPAREN
I/F_SPEED
<speed>
ENH_TRANSP
SK000121
where
bw is the number of 8 kb/s elements (1 to 8*)
speed is a valid interface speed relative to the bandwidth
(400)
22.3-21
Note
If you enter the interface speed before the transport bandwidth, the system overrides
the interface speed if the transport bandwidth and interface speed combination is
not valid.
To switch back to subrate speeds, enter the interface speed equal to the transport
bandwidth.
To configure and connect super-rate circuits, see chapter 20.15.
22.3.15
Figure 22.3-6: 2B1Q, 27LC2 and DNIC Line Card Super-rate Connections
2602, 2603
or 2613
MainStreet DTU*
128 kb/s
device
128 kb/s
device
MainStreet node
A
B
DNIC
Line card
A
B
2B1Q
Line card
or channel
unit
2702, 2703
or 2715
MainStreet DTU*
Common
Control
card
PRI
card
Network
5722
Both ports on the DTUs can be configured for super-rate operation, but only one port
can be program-connected at a time.
Table 22.3-8 lists the line cards and the DTUs that support transparent 128 kb/s
super-rate operation.
22.3-22
(400)
Interface
Minimum Firmware ID
X.21
$23
V.35
$23
V.35
$23
X.21
$14
V.35
$14
V.35
$14
(2)
or Channel Unit
Notes
1. The DTU must be equipped with a Revision 2 DRAGA.
2. The 2B1Q or DNIC Line card must be equipped with a DPM or DPM2.
The 128 kb/s super-rate circuits on 2B1Q, 27LC2 and DNIC Line cards can be
connected to:
aggregate cards (DS-3, Dual E1, Dual E3, Dual T1-2, E1, E3, T1 and, X.21 and V.35
PRI cards)
data cards (RS-449 DCC, V.35 DCC, X.21 DCC and DNIC cards)
FRE and FRS cards
Configuration summary
Three steps are required to set up and connect a 128 kb/s transparent super-rate
connection between a 2602, 2603, 2613, 2702, 2703 or 2715 MainStreet DTU and an
aggregate or data card.
1.
2.
3.
Connect the DTU port to the target circuit. Table 22.3-9 lists the target circuit
requirements.
(400)
22.3-23
Connection Requirements
Aggregate card
circuit
The target circuit and the next contiguous circuit on the aggregate card must be
available.
Aggregate card
master circuit
The master and slave circuit that will carry the 128 kb/s super-rate connection
must be configured (on the aggregate card) before being connected. The
master and slave circuits do not need to be contiguous.
The target circuit must be configured for 128 kb/s super-rate before being
connected.
The target circuit must be configured for 128 kb/s before being connected.
METHOD
TRANSPAREN
I/F_SPEED
<speed>
SK000122
22.3.16
22.3-24
(400)
Caution
Redundant DTU ports must have the same configuration. Otherwise, if an activity
switch occurs, data may be lost.
ENABLE/DISABLE*
SK000123
To disable redundancy for the DTU port, the system checks connections on the
circuit. If the circuit is connected, the warning message That circuit is in use.
Disconnect it first. is displayed.
MATE settings are configurable only if two 2715 MainStreet DTUs are connected to
their corresponding 27LC2 Line cards; otherwise, the warning message The DTU
does not support this feature. is displayed.
Activity switching
Activity switching occurs due to equipment failures and disconnections or from a
manually initiated forced switch.
(400)
22.3-25
Note 1
Once an activity switch occurs, traffic does not revert to the previously active port
unless a forced activity switch is initiated through NMTI or a cable is physically
disconnected.
Note 2
Active ports are configured independently from standby ports. Software checking is
not provided to ensure compatible configuration between redundant ports. In order
for an activity switch to occur properly, you must ensure that configuration is
consistent between mate DTUs. If mate DTUs are not configured through NMTI,
warning messages will be unavailable.
22.3-26
(400)
DTU_LOSS
NODE_LOSS
<debounce time>
50_MS
250_MS
where
the first debounce_time is in the range of 0 to 255000 ms in 1 ms increments
the second debounce_time is in the range of 0 to 300000 ms in 1 ms increments
SYNC_DEB time can be configure even though the 2715 MainStreet DTU is not physically present. Once
the 2715 MainStreet DTU is present, the port status and Y cable status are displayed as unknown if the
port is configured as standalone.
Note
You can only force standby mode on an active DTU port. Mate DTUs must be
configured and reside on the same node to display the following warning message:
Mate DTU not present. Proceeding will result in data loss.
(400)
22.3-27
1117-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Port
Port Status
Y Cable Status
-----------------------------------------------------A1-01-A
Active
Present
A1-01-B
Standalone
Unknown
1-FRC_STNDBY
6-
27-
38-CANCEL
49-QUIT
50-
22.3.17
DISABLED*
MASTER
SLAVE
SK000127
22.3-28
(400)
22.3.18
If card version 90-0470-04 receives an AIS, which is an all-ones signal, 8 kHz timing
is automatically interrupted until the card stops receiving AIS.
Note
An 8 kHz clock can be derived from a 64 kb/s Codirectional card circuit for use as a
synchronization source for the system. Chapter 16.2 describes configuring
synchronization sources.
22.3.19
AIS to enable the AIS so that it is sent when the circuit is not connected (default)
NO_AIS to disable the AIS so that it is not sent
If card version 90-0470-04 receives an AIS, the AIS enable/disable function is
automatically disabled until the card stops receiving AIS.
22.3.20
(400)
22.3-29
The speed configured for a data interface card circuit must match the speed at which
the attached device is transmitting data.
For the DS0-DP and OCU-DP channel units, you can configure the interface speed
as:
Note
Data interfaces configured for external independent clocking do not support
1.2 kb/s operation.
22.3.21
22.3-30
(400)
22.3.22
SC_ON to enable it
SC_OFF to disable it (default)
To configure a secondary channel operation
CONFIG CIRCUIT <sn-cc-1> FUNCTION SC_ON/SC_OFF*
22.3.23
SW56_ON to enable it
SW56_OFF to disable it (default)
To configure switched 56 kb/s operation
CONFIG CIRCUIT <sn-cc-1> FUNCTION SW56_ON/SW56_OFF*
(400)
22.3-31
22.3.24
ENABLE to enable it
DISABLE to disable it (default)
To configure sealing current
CONFIG CIRCUIT <sn-cc-1> MORE SEAL_CUR ENABLE/DISABLE*
22.3.25
ISDN basics
The ISDN recommendations and standards published by the ITU-T standardize the
transport of digital voice and data over a digital network. Figure 22.3-8 shows the
reference model for basic rate access to the ISDN network. ISDN-compatible devices
can be connected directly to the network through a standard interface at an access
point called the S interface. Equipment that is not ISDN-compatible must be
connected to a TA designed specifically for that equipment, which converts its
transmission format to an ISDN-compatible format at the R interface.
At the end of the subscriber loop, the NT provides line termination for the customer
devices. In the ISDN switch, the LT represents the interface termination. The U
interface is the interface between the NT in the customer premises equipment and
the LT in the network equipment. The U interface provides a BRI of two 64 kb/s
B channels and one 16 kb/s D channel in both directions over a single twisted-pair
cable at distances of up to 5.5 km. Echo cancellation techniques permit full duplex
transmission across the same wiring. The two B channels carry user data: either
voice or data. The D channel carries signalling information. The total effective data
rate across the interface is 160 kb/s, including overhead signalling data and
synchronization words.
22.3-32
(400)
Analog
telephone
TA
Customer
premises
Non-ISDN
computer
G3
FAX
TA
TA
Network
equipment
NT
ISDN
telephone
ISDN
Network
LT
LT
LT
ISDNcompatible
computer
ISDN
U-interface
telephone
ISDN
U-interface
computer
U
6587
LT
LUNT
Non-ISDN
Digital
facility
LULT
LUNT
Subscriber loop
Digital
facility
LULT
NT1
Exchange
termination
ISDN BRI loop extension
6586
(400)
22.3-33
3DS0 format
One loop extension scheme defined by Bellcore in TR-TSY-000397 uses three DS0
channels on a DS1 (or higher) interface to transport the basic rate traffic between the
LULT and LUNT. In the 3DS0 format, one DS0 is used for each B channel and the
third DS0 carries a D+ channel containing signalling. Figure 22.3-10 shows a typical
3DS0 loop extension application. In this example, the U-interface-compatible device
gains access to a remote ISDN network using 3DS0 transport over a T1 link. The B1,
B2 and D+ channels are treated as parts of one 192 kb/s super-rate circuit connected
to the T1 card.
Figure 22.3-10: 3DS0 ISDN Loop Extension Application
3600 MainStreet
node
NT
U
2B1Q
interface CU
T1
3600 MainStreet
node
Digital
facility
U
2B1Q
CU interface LT
LUNT
T1
LULT
ISDN
U-interface
computer
ISDN
network
DS0n
DS0n+1
B1
DS0n+2
B2
D+
5DS0 format
Another transmission scheme, specified in ITU-T Q.512, carries the data stream for
two U interfaces on five DS0 channels of a digital facility. Four DS0s correspond to
the B channels from both interfaces. Two 32 kb/s D+CV channels, which consist of
D-channel bits and overhead bits, are multiplexed into the fifth DS0. Figure 22.3-11
shows a typical 5DS0 loop extension application. In this example, two
U-interface-compatible devices use 5DS0 transport over a T1 link to access a remote
ISDN network. An SRM multiplexes two D+CV channels into one DS0. The B1 and
B2 channels are connected to the T1 link directly as parts of one 128 kb/s super-rate
circuit.
22.3-34
(400)
B11 B21
U
interface LULT
LUNT
D1 CV1
SRM
NT
T1
Digital
facility
D1 CV1
T1
ISDN
Network
SRM
D2 CV2
D2 CV2
U
interface 2B1Q
CU
LULT
U
LT
interface
2B1Q
CU
U
LT
interface
B12 B22 LUNT
B12 B22
ISDN
U-interface
computer
DS0n
B11
DS0n+1
DS0n+2
DS0n+3
DS0n+4
B21
B12
B22
D1CV1 D2CV2
(400)
22.3-35
ZBS_0N*/ZBS_OFF
PM_ON*/PM_OFF
SK000128
PM_ON*/PM_OFF
LOW_NIB*/HIGH_NIB
SK000129
22.3-36
(400)
In 5DS0 applications, 2B1Q channel unit circuit D (configured for 32 kb/s interface
speed) represents the D+CV channel, which can occupy either the upper or lower
nibble in the DS0. You can multiplex two 32 kb/s D circuits from different 2B1Q
channel units into one 64 kb/s DS0 channel using SRM circuits on a DSP card or
DPM module.
Note
Two D circuits must be configured for different nibbles to be connected to the same
SRM circuit.
B1 and B2 channels in 5DS0 applications are represented by the 128 kb/s super-rate
master, circuit 1. You can connect this circuit independently to any circuit that can
be configured for 128 kb/s super-rate speed. You can configure 2B1Q channel units
in 5DS0 transport mode as RAPID-protecting or RAPID-protected circuits.
Connection example
In this example, a T1 card is configured in slot A1, a Carrier card in slot A2 and a
DSP3 card in slot A3. Two 2B1Q channel units are installed in positions 2 and 3 of
the Carrier card and configured for 5DS0 applications. Circuit A3-2-D is configured
for LOW_NIB and circuit A3-3-D is configured for HIGH_NIB.
2.
3.
4.
5.
Figure 22.3-12 shows the screen displaying the resulting connections. In this
example, circuits A1-1 (master circuit) and A1-2 and A1-3 (slave circuits) on the T1
card in slot A1 are connected to circuit A2-1-1 (master) A2-1-2 and A2-1-D (slaves)
on the 2B1Q channel unit in position 1 of the carrier card in slot A2. The 2B1Q
channel unit is configured for 3DS0 application, so the super-rate circuit uses three
DS0s and carries B1, B2 and D+ data.
Channel units in positions 2 and 3 of the same carrier card are configured for 5DS0
application. The two D circuits from these channel units are connected to an SRM
circuit on the DSP card in slot A3, and that SRM is connected to circuit A1-9. The
other two circuits on the channel units (A2-2-1 and A2-3-1) are configured as
super-rate groups and use two DS0s.
The screen displays two pairs of primary rate circuits (A1-5 and A1-6, and A1-7 and
A1-8) involved in the super-rate connections.
(400)
22.3-37
1117-H1-00
Name
Type
A1-01
A1-02
A1-03
A1-04
A1-05
A1-06
A1-07
A1-08
A1-09
A1-10
A1-11
A1-12
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_SIG
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_NoSIG
T1_SIG
T1_SIG
T1_SIG
Toronto:A
Alarms:1
Circuit
*A2-01-01
*A2-01-02
*A2-01-0D
--*A2-02-01
*A2-02-02
*A2-03-01
*A2-03-02
*A3-01-M01
-------
Name
11-May-1997
Type
8:35a
Conv
2B1Q_B
2B1Q_B
2B1Q_D
2B1Q_B
2B1Q_B
2B1Q_B
2B1Q_B
SRM
1-SHOW_CCT
6-PROTECTING
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
5-PROT_BY
0-
Note
Some 2B1Q channel unit circuit connections to single E1 or T1 cards may be blocked
because of delay problems. Use a SAM on these cards to eliminate any delay
equalization problems.
22.3.26
22.3-38
(400)
22.4
22.4.1
Transparent
Enhanced
Transparent (1)
HCM
DDS_ HCM
X.50_ HCM
Parameter
Clocking (sync)
Control signals
Device gender
Device mode
Duplex method
Interface type(1)
Inversion (1)
Parity (async)
RTS/CTS delay
(3) (4)
(4)
Super-rate circuits
(400)
22.4-1
Notes
1. Valid only for RS-422 DCC circuits.
2. C bit.
3. If bandwidth is available (for a 56 kb/s circuit over a 64 kb/s clear channel), control signals are transmitted in all unused
bandwidth.
4. Valid only for DCC circuits.
Table 22.4-2 lists the configurable rate adaption, SRM and branch channel
parameters and indicates how they apply to each type of rate adaption. See
chapter 23.6 for information about rate adaption, SRMs and branch channels.
Table 22.4-2: Rate Adaption, SRM and Branch Channel Parameters
Transparent
Enhanced
Transparent (1)
HCM
DDS_HCM (2)
X.50 (2)
Transport bandwidth
Parameter
Signalling (3)
Data position
Subframe position (3)
CPSS (4)
Composite (5)
User-reserved (5)
Antistreaming
Error correction
Notes
1. Valid only for RS-422 DCC circuits.
2. Not valid for DCC SRMs.
3. Not valid for SRMs.
4. Valid only for SRMs.
5. Valid only for branch channels.
22.4-2
(400)
22.4.2
Note
RS-232 DCCs are automatically configured for SRMs and their configuration cannot
be changed. RS-422 DCCs do not support on-card SRMs. To subrate multiplex an
RS-422 DCC circuit, you must connect it to a DSP-based SRM. See chapter 23.6.
configure the card for a DPM2 module using the slot option DPM2
select the rate adaption method
(400)
22.4-3
DPM2
HCM_TRANS*
DDS
METHOD
X.50
X50_TELCO
DIV_2
DDS_ACCESS
DIV_3
VERSION_1 VERSION_2
SK000130
Note
If there is no DPM2, or if you need multiple rate adaptions, connect the circuits to a
DSP-based SRM. (See chapter 23.6.)
HCM*
<Bn>
<speed>
<Ff-Bb>
TRANSPAREN ENH_TRANS
SK000131
22.4-4
(400)
where
bw is the number of 8 kb/s elements (1 to 8*)
Bn is B7* to B0
speed depends on the rate adaption method (see section 23.6.7)
f is 0 to 9 and
b is 7 to 0 (F0-B5*)
Note
The ENH_TRANS option is applicable only for RS-422 circuits.
ANTISTREAM METHOD
POSITION
I/F_SPEED
<pos>
<speed>
DDS_HCM
DS-0A
DS-0A_EC
SIG_ON/
SIG_OFF*
X50_HCM
DS-0B
MJU
MJU_EC
DIV_2
DIV_3
SK000132
where
pos is the subframe position (see section 23.6.9)
speed depends on the rate adaption method (see section 23.6.7)
Note
The ANTISTREAM option is applicable only when the rate adaption method is
configured as DDS_HCM.
(400)
22.4-5
METHOD TRANSP_BW
<bw>
HCM*
F_POSITION HCM_BW
<Bn>
<hcm_bw>
TRANSPAREN
SK000133
where
bw is the number of 8 kb/s elements (1 to 8*)
Bn is B7* to B0
hcm_bw is the number of columns (1 to 8*)
ANTISTREAM
METHOD
DS-0A
POSITION
I/F_SPEED
<pos>
<speed>
DS-0A_EC
DS_0B
CONT_CHK/
NO_CONT_CK*
MJU MJU_EC
SK000134
where
pos is the subframe position (see section 23.6.9)
speed depends on the rate adaption method (see section 23.6.7)
Note
The CONTCHK/NO_CONT options appear only for DDS access SRMs.
22.4-6
(400)
Distributor Disclaimer
Newbridge products are intended for standard commercial uses. Without the appropriate network design engineering,
they must not be sold, licensed or otherwise distributed for use in any hazardous environments requiring fail-safe
performance, such as in the operation of nuclear facilities, aircraft navigation or communication systems, air traffic control,
direct life-support machines, or weapons systems, in which the failure of products could lead directly to death, personal
injury, or severe physical or environmental damage. The distributor hereby agrees that the use, sale, licence or other
distribution of the products for any such application without the prior written consent of Newbridge, shall be at the
distributor's sole risk. The distributor hereby agrees to defend and hold Newbridge harmless from any claims for loss, cost,
damage, expense or liability that may arise out of or in connection with the use, sale, licence or other distribution of the
products in such applications.
PRINTED ON
RECYCLED PAPER
23.1
23.1.1
Application
DSP
Card (1)
DSP2
Card (1)
DSP3
Card
DSP4
Card
DSP5
Card
DSP5H
Card
IMC
Miscellaneous Applications
CPSS channels (2)
Subrate switching
BONDING
Voice Compression Applications
HCV
G3 Fax relay
LD-CELP
A-CELP
(3)
(400)
23.1-1
Application
DSP
Card (1)
DSP2
Card (1)
DSP3
Card
DSP4
Card
DSP5
Card
DSP5H
Card
IMC
Notes
1. This card supports echo cancellation without voice compression. For more information, see 23.4.
2. The DSP card supports 8 and 16 kb/s CPss channels. The DSP2, DSP3 and DSP4 cards support 4, 8 and 16 kb/s CPSS
channels.
3. On the DSP5 card, super tandem operation is supported only when A-CELP voice compression is enabled.
For information about DSP card, DSP module and IMC variants, see chapter 8.3 in
Technical Overview.
23.1.2
23.1-2
(400)
DSP2
DSP3
DSP4
DSP5
DSP5H
Parameter
Options
Card slots
DSP1
DSP2
DSP3
DSP4
DSP5
Card circuits
2 cct*
6 cct
HCVD* (2)
DDS core
G3 fax relay
subrate switching
G3 fax, stHCV or G3 fax/stHCV
application number
LD-CELP (5)
A-CELP (5)
application number
DSP resources
1x10 (5)
HCV/fax (4)
2x10 (4)
Hub identification
Signalling type
E1
T1*
E1 signalling types
transparent
clear channel
E&M
continuous E&M
LGS remote extension
LGS earth calling
LGS PLAR
LGE remote extension
LGE earth calling
T1 signalling types
transparent*
clear channel
E&M
LGS loop start
LGS ground start
LGS PLAR
LGS PLAR D3
LGE loop start
LGE ground start
(400)
23.1-3
DSP
DSP2
DSP3
DSP4
DSP5
DSP5H
Parameter
Options
transparent*
HCM
8 kb/s
16 kb/s*
Data bandwidth
HCMbandwidth
F0-B6* to F8-B1
B0 to B7*
Echo cancellation
enabled*
disabled
Echo clipping
enabled
disabled*
enabled
disabled*
enabled*
disabled
6 dB attenuation pad
enabled
disabled*
Companding law
A-law
Mu-law
automatic*
enabled
disabled
enabled
disabled*
enabled
disabled*
enabled
disabled*
Super tandem
synchronization time (7)
23.1-4
(400)
DSP
DSP2
DSP3
DSP4
DSP5
DSP5H
Parameter
Options
Master circuit
companding law
A-law
Mu-law*
Master circuit
antistreaming timer
1 to 255 s in 1 s D (20*)
Branch circuit
antistreaming
enabled
disabled*
enabled
disabled*
VCB circuit
VCM
Companding law
A-law
Mu-law*
automatic
Input gain
16 to +9 dB in 0.1 dB D (0*)
Output gain
16 to +9 dB in 0.1 dB D (0*)
Sidetone
enabled
disabled*
16 to 0 dB in 0.1 dB D (0*)
Listen-only mode
enabled
disabled*
Broadcast mode
enabled
disabled*
Broadcaster
enabled
disabled*
HCM
transparent
DDS
DDS access
X.50
X.50 Telco
B7* to B0
F0 to F9 and B7 to B0 (F0-B5*)
Composite inputs
composite
not composite*
User/system reserved
inputs
system
user*
(400)
23.1-5
DSP
DSP2
DSP3
DSP4
DSP5
DSP5H
Parameter
Options
master
slave
disable*
Fax relay
enabled*
disabled
enabled*
disabled
Transmission rate
4800 b/s*
9600 b/s
Modem rate
4800 b/s
7200 b/s (* for A-CELP)
9600 b/s
12000 b/s
14400 b/s (* for LD-CELP)
Set identifiers
Changing sets
previous set
next set
new set
add to set
delete from set
delete set
transparent
HCM*
DDS
X.50
4 kb/s CPSS
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
56 kb/s
23.1-6
(400)
DSP
DSP2
DSP3
DSP4
DSP5
DSP5H
Parameter
Options
2.4 kb/s
4.8 kb/s
9.6 kb/s*
2.4 kb/s
4.8 kb/s
9.6 kb/s*
19.2 kb/s
48 kb/s
HCM transport
bandwidth
B0 to B7*
HCM bandwidth
Notes
1. This option is the default if you are using pre-Release 6 software.
2. This option is the default for Release 6 and post-Release 6 software versions.
3. If a DSP4 card with a firmware ID of $9 (or less) is inserted into a slot configured to support super tandem operation, a
Revision/Feature Mismatch alarm is raised and the card is taken out of service. See section 23.11.1 for details.
4. This option is supported on DSP5H cards only.
5. This option is supported on DSP5 cards only.
6. The DSP5 card supports an 8 kb/s bit rate when A-CELP voice compression is configured and a 16 kb/s bit rate when
LD-CELP voice compression is configured.
7. This option is supported on DSP5 cards configured for A-CELP voice compression.
8. This option is supported on DSP5 cards configured for LD-CELP voice compression.
9. Synchronization is not monitored when the circuit is transporting a G3 fax call.
10. For super tandem operation, the minimum required firmware on the DSP4 card is $E.
11. This range is valid for the DSP4 card.
12. This range is valid for DSP5 and DSP5H cards.
13. For the DSP card, only the HCM and transparent options are supported.
Section
Voice compression
23.3.9
Echo canceller
23.4.2
23.4.2
23.4.2
(400)
23.1-7
Connection Type
Section
VCB
23.5.3
Cascading bridge
23.5.3
SRM
23.6.12
SRS
23.9.5
Super tandem
23.11.1
Options
Slot Level
Card type
IMC
500 ms to 10 s (* = 1 s)
500 ms to 10 s (* = 2 s)
500 ms to 10 s (* = 5 s)
500 ms to 10 s (* = 5 s)
Channel setup
10 ms to 3 s (* = 150 ms)
Equalization timeout
500 ms to 10 s (* = 7 s)
23.1-8
Mode
Mode 1
Mode 3*
56 kb/s
64 kb/s*
0 to 30 s (* = 3 s) (3)
1 to 30 s (* = 3 s)
Bond setup
enabled
disabled*
calling
answering*
Directory (5)
modify one
modify all
(400)
Notes
1. The bearer rate option selection automatically sets the user side interface speed, which must be a
multiple of the bearer rate. For example, if you select the 56 kb/s option for the bearer rate, the user
side interface speed automatically changes to 336 kb/s.
2. Synchronization monitoring applies to BONDING mode 3 only.
3. If the declare time is set to 0, alarms are disabled.
4. The end type parameter is available only when the bond setup parameter is enabled.
5. The directory parameter is available only when the end type parameter is configured as answering.
(400)
23.1-9
23.2
23.2 Configuring Card Slots for DSP Cards and the IMC
Issue 1, November 1997
23.2.1
card type
number of DSP card circuits
hub identification
card applications
IMC BONDING timers
Note
Card type
Configure the type of card as:
(400)
23.2-1
23.2 Configuring Card Slots for DSP Cards and the IMC
Issue 1, November 1997
APP_NUM to select a fixed application stored in the FLASH memory of the card
LDCELP 1x10 to select LD-CELP voice compression using one circuit per DSP
ACELP 1x10 to select A-CELP voice compression using one circuit per DSP
For DSP5H cards, you can configure:
APP_NUM to select a fixed application stored in the FLASH memory of the card
HCV_FAX 2x10 to automatically select HCV with G3 fax capability using
2 HCV circuits per DSP
23.2-2
(400)
23.2 Configuring Card Slots for DSP Cards and the IMC
Issue 1, November 1997
CE_SYNC to modify the value of the calling endpoint BONDING timer. This
timer measures the time it takes for synchronization to occur on the master
channel (the default is 1 second).
AE_SYNC to modify the value of the answering endpoint BONDING timer. This
timer measures the time it takes for synchronization to occur on the master
channel (the default is 2 seconds).
CE_DIR_NUM to modify the value of the calling endpoint directory number
BONDING timer. This measures the time it takes to receive directory numbers
(the default is 5 seconds).
AE_DIR_NUM to modify the value of the answering endpoint directory number
BONDING timer. This measures the time it takes to deliver directory numbers
(the default is 5 seconds).
CHAN_SETUP to modify the value of the channel setup BONDING timer. This
calculates the timeout of the setup of all the individual branch cells (the default
is 150 ms).
EQ_TIMEOUT to modify the value of the equalization timeout BONDING timer.
This timer is used at both endpoints to measure the delay equalization process
(the default is 7 seconds).
TYPE
AS_PRESENT
OPTIONS
MORE
6_CCT/
2_CCT*
HCVD*/DDS_CORE
<id>
DSP
DSP
DSP2
HUB_ID
DSP3 DSP4
IMC DSP5
SK000135
(400)
23.2-3
23.2 Configuring Card Slots for DSP Cards and the IMC
Issue 1, November 1997
Note 1
The HCVD and DDS_CORE options apply only to DSP2 and DSP3 cards.
Note 2
Use the AS_PRESENT softkey if there is a DSP card installed in the slot.
TYPE
AS_PRESENT
OPTIONS
MORE
SRS
OTHER
MODULES
DSP
NONE
DSP
DSP2
DSP3 DSP4
G3FAX
IMC DSP5
SK000136
TYPE
AS_PRESENT
DSP
OPTIONS
MORE
APP_NUM
HCV_FAX
LDCELP
ACELP
DSP
<app_num>
2x10
1x10
1x10
IMC DSP5
SK000983
where app_num is an application number stored in the FLASH memory of the DSP card. The default is 0
(zero).
23.2-4
(400)
23.2 Configuring Card Slots for DSP Cards and the IMC
Issue 1, November 1997
Note 1
The HCV_FAX softkey is only available for the DSP5H card.
Note 2
The LDCELP and ACELP softkeys are only available for the DSP5 card.
TYPE
OPTIONS
BONDING
AS_PRESENT MORE
DSP
<timer_value>
DSP
DSP2
DSP3 DSP4
IMC DSP5
SK000137
(400)
23.2-5
23.3
Voice Compression
This chapter describes LD-CELP, A-CELP and HCV voice compression, and
explains how to configure voice compression parameters on DSP cards.
23.3.1
23.3.2
(400)
23.3-1
To enable voice compression on DSP cards, you must configure the following:
23.3.3
23.3.4
Signalling Type
E1 Signalling Types
23.3-2
SIG
transparent
NoSIG
clear channel
E+M E+M
E&M
E+M E+M_B
continuous E&M
(400)
Softkey
Signalling Type
LGS REM_EXT
LGS EC
LGS PLAR
LGS PLAR
LGE REM_EXT
LGE EC
T1 Signalling Types
SIG
transparent
NoSIG
clear channel
E+M E+M
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR
LGS PLAR_D3
LGS PLAR D3
LGE LS
LGE GS
T1_SIG
E1_SIG
SIG
NoSIG
E+M
REM_EXT
E+M
LGS
R2D_E+M
LGE
E+M_B
EC
PLAR
SIG*
LS
REM_EXT
NoSIG
GS
E+M
PLAR
EC
LGE
LGS
PLAR_D3
LS
TERMINATE
GS
SK000821
(400)
23.3-3
23.3.5
B6
B5
B4
B2
B1
B0
B2
B1
B0
a.
B7
b.
B3
B6
B5
B4
B3
7183
23.3-4
(400)
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7184
When you configure an HCM rate-adapted compressed voice circuit, you must set:
For the DSP3 card, select the HCV softkey twice the first time you configure an
HCV function.
DATA_BW must be compatible with the HCV or data circuit bandwidth.
You cannot configure a DATA_BW of 9.6_kbps for a circuit configured with
transparent rate adaption.
(400)
23.3-5
METHOD
TRANSP_BW
TRANSP_POS HCV_RATE
<bw>
TRANSPAREN*
DATA_POSN
<Bn>
HCM
<Ff-Bb>
8_Kbps
16_Kbps
SK000138
where
bw is 2 to 8 for 8_kbps circuits and 3 to 8 for 16_kbps circuits
Bn is B0 to B7* for HCM and 8 kb/s transparent and B1 to B7* for 16 kb/s transparent
Ff-Bb is F0-B6* to F8-B1 for 8_kbps circuits and F0-B6* to F7-B3 for 16_kbps circuits
RATE_ADAPT
METHOD
TRANSPAREN*
HCV_CONFIG
HCM_BW
TRANSP_POS
DATA_BW
DATA_POSN
<bw>
<Bn>
<n>
<Ff-Bb>
HCV_RATE
8_Kbps
16_Kbps
HCM
SK000816
where
bw is 2 to 8 for 8_kbps circuits and 3 to 8 for 16_kbps circuits
Bn is B0 to B7* for HCM and 8 kb/s transparent and B1 to B7* for 16 kb/s transparent
n is 1 to 20* (1 to 16 000 b/s in 800 b/s increments)
Ff-Bb is F0-B6* to F8-B1 for 8_kbps circuits and F0-B6* to F7-B3 for 16_kbps circuits
23.3-6
(400)
RATE_ADAPT
METHOD
VOICE
HCM_BW
TRANSP_POS
DATA_BW
DATA_POSN
<bw>
<Bn>
<n>
<Ff-Bb>
BIT_RATE
8_kbps
TRANSPAREN*
16_kbps*
HCM
SK000825
where
bw is 2 to 8 for 8_kbps channels and 3 to 8 for 16_kbps channels
Bn is B1 to B7* for 16 kb/s transparent and B0 to B7* for HCM and 8 kb/s transparent
n is 1 to 20* (1 to 16 000 b/s in 800 b/s increments)
Ff-Bb is F0-B6* to F8-B1 for 8_kbps circuits and F0-B6* to F7-B3 for 16_kbps circuits
Note
The DSP5 card supports the 8 kb/s compressed voice bit rate with A-CELP voice
compression and the 16 kb/s compressed voice bit rate with LD-CELP voice
compression only.
23.3.6
(400)
23.3-7
If you select AUTO, the system determines the companding law to use according to
the following rules when the compressed voice circuit is connected to its mate
circuit.
If the mate circuit is on a voice card, the system uses the companding law of the
voice card.
While a circuit configured for AUTO is unconnected, the system displays its default
companding law, which is A-law.
You cannot change the companding law if the circuit is connected.
ALaw
MuLaw
AUTO*
SK000142
ALaw
MuLaw
AUTO*
SK000815
23.3-8
(400)
ALaw
MuLaw
AUTO*
SK000824
23.3.7
echo cancellation
echo cancellation return loss threshold
echo clipping
echo clipping threshold level
6 dB attenuation pad
AC15 tone detection
LD-CELP post filter
Echo cancellation
Echo cancellation removes echo caused by delays in transmission over long distance
tail circuits. The compressed voice algorithm provides 8 ms of built-in tail circuit
echo cancellation. If this is not enough echo cancellation for your application, you
can connect a DSP configured for echo cancellation or an external echo canceller
device into your voice compression connection (see chapter 23.4).
Note
You must disable built-in echo cancellation if you are connecting the circuit to a DSP
circuit configured for echo cancellation or when using an external echo canceller.
Configure built-in echo cancellation for the voice compression channel as:
(400)
23.3-9
Echo clipping
Echo clipping mutes transmission line signals. If echo on a transmission line occurs
outside of the 8 ms echo cancellation window, enabling echo clipping can help
suppress the echo by muting all transmission line signals when the input is below
the user-configurable echo clipping threshold level.
On the DSP5H and DSP5 card, you can configure the echo clipping threshold level
by selecting THRESHOLD and entering a threshold ranging from 10 dBm0 to
50 dBm0.
You can configure echo clipping for the voice compression channel as:
CLIP_ON to enable it
CLIP_OFF to disable it (default)
6 dB attenuation pad
The 6 dB attenuation pad attenuates the input signal by 6 dB before it is compressed.
The resulting decompressed signal is amplified by 6 dB before it is delivered to the
output line. Attenuation and re-amplification do not affect the gain levels.
The padding operation is activated only when a 6 dB capable device is connected to
another 6 dB capable device, and both devices are enabled.
Configure the 6 dB attenuation pad as:
6dBPAD_ON to enable it
6dBPAD_OFF to disable it (default)
23.3-10
(400)
Note
The 6 dB attenuation pad is only available for HCV voice compression.
ECHO_CANC
CLIP_ON/
CLIP_OFF*
CANCEL_ON*/CANCEL_OFF
Note
DSP3 card echo cancellation can also be configured by entering:
CONFIG CIRCUIT <sn-cc> FUNCTION ECHO_CANC
CANCEL_ON*/CANCEL_OFF
(400)
23.3-11
ECHO_CANC
CANCEL_OFF/
CANCEL_ON*
CLIP_ON/
CLIP_OFF*
AC15_ON/
AC15_OFF*
6dBPAD_ON/
6dBPAD_OFF*
RLOSS_3dB/
RLOSS_6dB*
SK000822
OPTIONS
ECHO_CANC
ECHO_CLIP
CLIP_ON/ THRESHOLD
CLIP_OFF*
<clip_thres>
SK000823
where
canc_loss is 0 to 120 (60*)
clip_thres is 50 to 10 (40*)
Note
The 6dBPAD_ON/6dBPAD_OFF softkeys are not supported on the DSP5 card.
23.3.8
23.3-12
(400)
Caution
Both ends of an compressed voice connection configured for HCM rate adaption
must have the same framing bit position, voice bandwidth and data bandwidth to
be able to pass data calls.
(400)
23.3-13
If you are connecting an SRM between the DSP circuit and the primary rate circuit
(as shown in Figure 23.3-4), you must make the following connections:
Connect the DSP circuit to the SRM as follows:
CONFIG CONNECT <x-sn-cc> TO_CIRCUIT <x-sn-cc> TO <x-sn-Mmm>
or <x-sn-cc-Mmm>
where
the first x-sn-cc is the uncompressed voice circuit
the second x-sn-cc is the DSP circuit
x-sn-Mmm or x-sn-cc-Mmm is the SRM circuit
23.3-14
(400)
23.4
23.4.1
MJU
Master connected to
cluster controller
Slaves connected to
terminals via modems
2038
As shown in Figure 23.4-2, you can create larger bridges by cascading them: the
master from the secondary bridge is connected to the branch channel of the primary
bridge. The primary bridge acts as the host processor for the secondary bridge.
(400)
23.4-1
Note
Only one composite input can be connected to an SRM. Cascaded SRMs are
considered as a single SRM.
Terminal
slave inputs
Composite
or slave
inputs
Secondary
data bridge
Primary
data bridge
To host
processor
Composite
input
2048
on a single bridge
10 branch channels in a DSP circuit
23.4-2
(400)
Modem
Local 3600 MainStreet node
Master device
Voice
Interface
card
T1
card
x
Modem
Slave device
PCM Multidrop
data bridge
Slave device
Modem
Remote
3600 MainStreet node
Voice
Interface
card
Modem
Slave device
T1
card
Modem
Slave device
3094
Antistreaming
Streaming occurs when a slave device does not return to the idle state after it has
finished communicating with the master device; this prevents the other slave
devices from communicating.
Antistreaming allows the system to detect streaming and disable the slave device
branch channel if the streaming does not stop after a specified amount of time. The
system then considers the disabled circuit out-of-service, but re-enables it if the
circuit stops streaming. If the branch channel is a composite output from another
bridge, antistreaming is automatically disabled.
Antistreaming timeout
Antistreaming timeout is the maximum time a device can stream before the system
disables the circuit, in the range 1 to 255 seconds.
(400)
23.4-3
ADI
You can use ADI if the input contains information that has been transmitted over
more than one primary rate link and converted between two output formats (the
ITU-T alternate digit inversion PCM generally used on E1 links and the AT&T
true-sign inverted magnitude PCM generally used on T1 links). Enabling the ADI
function re-inverts the information so that it is intelligible.
Figure 23.4-4 shows an example of an ADI application. In a 3600 MainStreet series
bandwidth manager node, the connection is between the T1 cards, rather than
through the switching shelves.
Figure 23.4-4: ADI Application
Switching shelf
Switching shelf
3645 MainStreet
node
3645 MainStreet
node
T1
T1
Configured
for "data"
Configured
for "voice"
DSP
PCM Multidrop
Data Bridge
configured for
"ADI_ON"
7156
23.4.2
23.4-4
(400)
Note
HCVD is the default for DSP, DSP2 and DSP3 cards.
A_LAW/MU_LAW*
STRM_TIMER
<number_of_seconds>
SK000144
STREAM_ON*/
STREAM_OFF
ADI_ON/
ADI_OFF*
SK000145
(400)
23.4-5
23.5
23.5.1
VCBs
companding law
input and output gain
sidetone gain
listen-only mode
broadcast mode for the bridge or the input
conference
broadcast
In a conference VCB, each conferee in the bridge participates equally. If more than
one input has the same gain, each one can be heard. Figure 23.5-1 shows a conference
configuration.
Figure 23.5-1: VCB Conference Configuration
VCB
Cascading link
VCB
2382
In a broadcast VCB, you configure only one input as a broadcaster and all the other
inputs as listen-only. Figure 23.5-2 shows a broadcast configuration.
(400)
23.5-1
Listen-only
Set input to
broadcaster
VCB
Cascading link
VCB
Broadcast
mode
Broadcast
mode
Listen-only
Listen-only
2381
The DSP3 card, which can have two or six DSP circuits, supports VCBs. As shown in
Figure 23.5-3, each DSP circuit supports 14 voice channel inputs, shared between
four bridges. You can connect DSPs in a daisy chain, or hierarchically to create larger
VCBs.
Figure 23.5-3: Large VCBs
Daisy chain
VCB
VCB
VCB
Hierarchical
VCB
VCB
VCB
2049
The inputs must be in a PCM format and can be any combination of:
23.5-2
(400)
Note
An HCV circuit cannot be an input to a VCB, even if the circuit has been
decompressed. For example, if an HCV circuit is decompressed and connected to a
PCM circuit, you cannot connect the PCM circuit to a VCB.
VCB Restrictions
When you configure VCBs, the following restrictions apply.
VCB
VCB
VCB
VCB
VCB
VCB
Parallel links
between two bridges
Two inputs on
the same bridge
23.5.2
(400)
23.5-3
Note
HCVD is the default for DSP, DSP2 and DSP3 cards.
companding law
gain
listen-only mode
Companding law
Configure the companding law for the VCB as:
If you connect to a circuit on a voice card, the VCB input takes the law of the voice
card.
If you connect to a circuit on a T1 primary rate or DS-3 card, the VCB input is
Mu-law.
If you connect to a circuit on an E1, X.21 or V.35 PRI or 64 kb/s Codirectional
card, the VCB input is A-law.
If you connect to a circuit configured for echo cancellation, the VCB input takes
the law of the circuit.
When you connect circuits to a bridge, they can have any combination of the
companding laws.
Gain
Gain is the increase or decrease in signal power or voltage that occurs in transmitting
a signal from one point to another. The three types of gain are:
input
output
sidetone
23.5-4
(400)
Sidetone
Output
2377
The input gain defines the magnitude of the increase or decrease of the signal
transmitted into the bridge. The input gain range is 16 to +9 dB in 0.1 dB steps (the
default is 0 dB).
You can change the input gain at any time, except when the circuit is configured as:
ENABLE to enable it
DISABLE to disable it (default)
You can change the sidetone gain at any time.
Listen-only mode
In listen-only mode, the conferee listens but does not participate in the conversation.
You cannot change the input gain in listen-only mode; the system displays
Overridden beside the Input Gain entry.
Configure listen-only mode as:
ENABLE to enable it
DISABLE to disable it (default)
(400)
23.5-5
COMP_LAW
GAIN
LISTEN
ENABLE/DISABLE*
ALaw
MuLaw AUTO*
INPUT
OUTPUT
<gain>
SIDETONE
ENABLE/DISABLE*
<sidetone>
SK000146
where
sn-cc-Ikk is the VCB input
gain is 16 to +9 dB in 0.1 dB increments (0 dB*)
sidetone is 16 to 0 dB in 0.1 dB increments (0 dB*)
Broadcast mode
For broadcast mode, you configure one circuit as the broadcaster and the system
automatically forces all the other circuits in the bridge into listen-only mode. The
broadcaster cannot listen to any of the other circuits on the bridge.
Configure broadcast mode as:
ENABLE to enable it
DISABLE to disable it (default)
To configure broadcast mode
CONFIG CIRCUIT <sn-cc-BRn> FUNCTION BROADCAST
ENABLE/DISABLE*
where sn-cc-BRn is the bridge and n is 1 to 4
23.5-6
(400)
23.5.3
T1
I3
Slot 1
VCB
Slot 2
2375
Figure 23.5-7 shows an example of a cascading VCB. The figure shows two VCBs:
VCB1 I3 and VCB2 I4.
Figure 23.5-7: Cascading VCB Example
BR1
VCB
BR2
I3
I4
VCB
2376
To connect a VCB
To connect a VCB, connect the voice circuit to the VCB input, and the VCB input to
the voice conference bridge, as follows:
CONFIG CONNECT <sn-cc> TO_CIRCUIT <sn-cc-Ikk> TO <sn-cc-BRn>
where
sn-cc is the voice circuit
sn-cc-Ikk is the VCB input
sn-cc-BRn is the bridge
(400)
23.5-7
To cascade bridges, you must configure both bridges, then connect the first input to
its associated bridge, connect that bridge to the second input, and then connect the
second input to its associated bridge, as follows:
CONFIG CONNECT <sn-cc-Ikk> TO_CIRCUIT <sn-cc-BRn> TO
<sn-cc-Ikk> TO <sn-cc-BRn>
where
the first sn-cc-Ikk is the first VCB input
the first sn-cc-BRn is the first bridge
the second sn-cc-Ikk is the second VCB input
the second sn-cc-BRn is the second bridge
23.5-8
(400)
23.6
23.6.1
(400)
23.6-1
DCCs
DNIC and 2B1Q Line cards
DSP, DSP2, DSP3, DSP4, DSP5H and DSP5 cards
There are two forms of transparent rate adaption:
transparent
enhanced transparent
Transparent
A 64 kb/s transparent channel is made of eight 8 kb/s elements named B7 through
B0. The node manager represents the amount of bandwidth allocated to a
transparent channel by the number of elements containing a D, where each D
represents 8 kb/s of bandwidth. Elements that do not contain a D represent unused
bandwidth. Figure 23.6-1 represents a 32 kb/s transparent channel.
Figure 23.6-1: Transparent Channel
B7
B6
B5
B4
B3
B2
B1
B0
7193
Enhanced transparent
Enhanced transparent rate adaption allows signalling transmission that is
transparent and synchronous for all interface speeds. This rate adaption scheme is
available only on RS-422 DCC circuits.
As shown in Figure 23.6-2, an enhanced transparent circuit is made of a 56 kb/s
supervisory circuit and, if the circuit is super-rate, one or more slave circuits. The
first three bits (24 kb/s) of the supervisory circuit are reserved for framing (bit 7) and
signalling (bits 6 and 5). The remaining 40 kb/s are free for transparent data.
23.6-2
(400)
Slave
circuits
DS0 2
DS0 3
DS0 N
7 6 5 4 3 2 1 0
40 kb/s
DTR/DSR
RTS/DCD
Framing
3468
The system fills the supervisory circuit and the number of slave circuits required
based on the transport bandwidth and interface speed. The system determines
whether the free bandwidth in the supervisory channel is used (it is used if a DS0
can be saved).
As shown in Figure 23.6-3, the signalling bits are used to communicate DCD and
DSR from the DTE to the DCE in the transmit direction. In the receive direction, the
signalling bits are used to communicate RTS and DTR from the DCE to the DTE.
Figure 23.6-3: Enhanced Transparent Rate Adaption Transparent Synchronous
Signalling
Single
bidirectional
HCM link
F
RTS
DTR
HCM frame
MainStreet node
MainStreet node
F
DCD
DSR
RS-422
DTE
RS-422
DCE
Transparent data
only
3469
(400)
23.6-3
DCCs
DNIC and 2B1Q Line cards
DSP, DSP2, DSP3, DSP4, DSP5H and DSP5 cards
HCM divides a 64 kb/s channel into 80 elements that are transmitted at a rate of 800
elements in a second. Each element represents one bit or 800 b/s of bandwidth. As
shown in Figure 23.6-4, the node manager displays an HCM frame as a 10-row by
8-column matrix. The rows are named F0 to F9; the columns are named B7 to B0. The
node manager identifies an element by its row and column, for example F3-B2.
Figure 23.6-4: HCM Frame
B7
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7194
23.6-4
(400)
The system supports multidrop circuits, loopbacks and the appropriate control
codes. DDS supports both synchronous and asynchronous interface speeds.
The system provides the following DDS applications:
DDS
DDS Access
DDS Core
Two types of cards support DDS and DDS Access SRMs:
19.2 kb/s)
DDS_HCM-to-DS0-A and DDS_HCM-to-DS0-B conversions
(400)
23.6-5
DDS Core
DDS Core is a DSP application optimized for high-volume DS0-B and MJU functions
intended for bulk DDS processing on the backbone network. As well as the basic
DDS functions, an SRM configured as DDS Core supports RTS signal propagation
(when DDS Access is being used at the end points of the network). DDS Core is a slot
option for DSP cards (see chapter 23.2).
DS0-A and DS0-B framing and interface speed
Figure 23.6-5 shows the DS0-A and DS0-B framing options. Table 23.6-1 lists the
interface speeds supported by the data interface cards that provide DDS rate
adaption.
Figure 23.6-5: DDS DS0-A and DS0-B Frame Structure
Framing bit
User data for
56 and 64 kb/s
operation
MSB
8-bit DS0
LSB
Primary channel
- user data
- inband
maintenance
codes
Frame
1
2
3
4
5
2.4 kb/s
1 2 3 4
5 6 7 8
9 10 11 12
13 14 15 16
17 18 19 20
4.8 kb/s
1
2
3
4
5
6
7
8
9
10
Standard CSU-to-CSU
communication channel
DDS secondary channel, plus:
- end-to-end control lead propagation
- continuity checking
Switched 56 signalling channel
User data for 64 kb/s operation
9.6 kb/s
1
2
3
4
5
5 frames,
20 channels
5 frames,
10 channels
5 frames,
5 channels
DS0-A:
user data repeated
in all 20 cells
Majority vote 12/20
DS0-B:
each cell
(numbers 1 to 20)
represents a separate
2.4 kb/s channel
DS0-A:
DS0-A:
user data repeated user data repeated
in all 10 cells
in all 5 cells
Majority vote 6/10
Majority vote 3/5
DS0-B:
DS0-B:
each cell
each cell
(numbers 1 to10)
(numbers 1 to 5)
represents a
represents a
separate 4.8 kb/s
separate 9.6 kb/s
channel
channel
19.2 kb/s
1
2
3
4
5
5 frames,
1 channel
56 or 64 kb/s
1
1 frame,
1 channel
DS0-A:
DS0-A:
BCH(17,9) OFF
56 kb/s operation:
user data occupies
user data divided
between cells
framing bit plus
2 and 3
Primary Channel
Pad characters
bits (7 bits total)
64 kb/s operation:
elsewhere
(using the OCU-DP
DS0-A_EC
user data divided
Channel Unit) user
between cells
data occupies
1 and 2
framing bit, Primary
Channel bits, and
BCH code in cells
3 and 4
Secondary Channel
bit (8 bits total)
framing in cell 5
DS0-B:
BCH(17, 9) code in
second DS0
each cell
(numbers 1 to 5)
represents a separate
9.6 kb/s channel
19.2 fits onto 2 and 3
and/or 4 and 5
5964
23.6-6
(400)
Table 23.6-1: Data Card Interface Speeds for DDS Rate Adaption
Interface Speed (b/s)
2400
4800
9600
19200
1200
2400
4800
9600
19200
RS-232
56000
2400
4800
9600
19200
RS-232
1200
2400
4800
9600
19200
DS0-A channels
A 56 kb/s channel consists of 7 data bits (D) in bit positions 1 to 7 and a network
control bit (C) in bit position 8 (see Figure 23.6-6). To meet the ones density
requirement for the T1 link:
the control bit is a logical 1 if data bits 2 through 7 contain customer data (since
C
7195
You can configure a 64 kb/s channel when the OCU-DP channel unit is used. You
can configure user data to occupy all eight bit positions including the framing,
primary channel and secondary channel bits.
DS0-A for subrate speeds
In DDS, any interface speed of 48 kb/s or less is a subrate speed. A subrate DS0-A
channel consists of a logical 1 in bit position 1, six data bits (D) in positions 2 to 7 and
a network control bit (C) in bit position 8. (A composite DS0-A subrate channel with
a zero in bit position 1 is jammed high by a DDS device.) To meet the ones density
requirement for the T1 link:
the control bit is a logical 1 if the data bits contain customer data
the control bit is a logical 0 if the data bits contain a network control code
In a 64 kb/s T1 channel, 8-bit bytes are transmitted at a rate of 8000 every second.
DDS subrate speeds are adapted to the 64 kb/s channel by sending new data every:
(400)
23.6-7
Frame 1
Frame 2
STUFF BYTE
Frame 3
STUFF BYTE
Frame 4
STUFF BYTE
Frame 5
STUFF BYTE
Frame 1
Frame 2
STUFF BYTE
5-frame
pattern
D
7196
Frame 1
Frame 2
STUFF BYTE
Frame 3
STUFF BYTE
Frame 4
STUFF BYTE
Frame 5
STUFF BYTE
Frame 6
STUFF BYTE
Frame 7
STUFF BYTE
Frame 8
STUFF BYTE
Frame 9
STUFF BYTE
Frame 10
STUFF BYTE
Frame 1
Frame 2
STUFF BYTE
10-frame
pattern
7197
23.6-8
(400)
The system supports one non-standard DDS subrate speed, 1.2 kb/s, by adapting
the 2.4 kb/s DS0-A format (see Figure 23.6-9). The 2.4 kb/s channels transmit 6
unique data bits every 20th frame; 1.2 kb/s channels transmit 3 unique data bits
every 20th frame. Each bit is repeated for a total of 6 bits in the pattern aabbcc, so a
1.2 kb/s DDS channel uses the same bandwidth as a 2.4 kb/s channel.
Figure 23.6-9: DS0-A Format for 2.4 kb/s DDS Channel
1
Frame 1
Frame 2
STUFF BYTE
Frame 3
STUFF BYTE
Frame 4
STUFF BYTE
Frame 5
STUFF BYTE
Frame 6
STUFF BYTE
Frame 7
STUFF BYTE
Frame 8
STUFF BYTE
Frame 9
STUFF BYTE
Frame 10
STUFF BYTE
Frame 11
STUFF BYTE
Frame 12
STUFF BYTE
Frame 13
STUFF BYTE
Frame 14
STUFF BYTE
Frame 15
STUFF BYTE
Frame 16
STUFF BYTE
Frame 17
STUFF BYTE
Frame 18
STUFF BYTE
Frame 19
STUFF BYTE
Frame 20
STUFF BYTE
Frame 1
Frame 2
STUFF BYTE
20-frame
pattern
7198
The system transmits 19.2 kb/s by adapting the 9.6 kb/s DS0-A format (see
Figure 23.6-10). Whereas 9.6 kb/s channels transmit new data every fifth frame and
stuff bytes in the intervening four frames, 19.2 kb/s channels transmit new data in
two of the frames.
Figure 23.6-10 shows DDS, DDS Access (Version 1 and Version 2), and DDS Core. In
the DDS format, the data is transmitted every first and second frame, and the other
frames are specific stuff bytes. In the DDS Access format, the data is transmitted
every second and third frame, and the other frames are specific stuff bytes. In the
DDS Access (Version 2), and DDS Core format, the data is transmitted every second
and third frame, the first frame is a ones complement of the third frame, and the
fourth and fifth frames are repeat stuff bytes of the third frame.
(400)
23.6-9
Frame 1
DA
DA
DA
DA
Frame 2
DA
DA
DA
DA
DA
DA
DA
DA
Frame 3
Frame 4
Frame 5
Frame 1
DA
DA
DA
DA
DA
DA
Frame 2
DA
DA
DA
DA
DA
DA
5-frame
pattern
Frame 1
Frame 2
DA
DA
DA
DA
DA
DA
Frame 3
DA
DA
DA
DA
DA
DA
Frame 4
Frame 5
Frame 1
Frame 2
DA
DA
DA
DA
DA
DA
5-frame
pattern
-DA
-DA
-DA
-DA
-DA
-DA
Frame 2
DA
DA
DA
DA
DA
DA
Frame 3
DA
DA
DA
DA
DA
DA
Frame 1
Frame 4
5-frame
pattern
Frame 5
Frame 1
-DA
-DA
-DA
-DA
-DA
-DA
Frame 2
DA
DA
DA
DA
DA
DA
7199
23.6-10
(400)
Note
Because 1.2 kb/s is a non-standard DDS interface speed, it is not necessarily
compatible with other vendor equipment. Data interfaces configured for external
independent clocking do not support 1.2 kb/s operation. Do not connect them to
DDS SRMs at this speed (see also sections 22.3.8 and 22.3.19).
(400)
23.6-11
X.50 framing
and A bit
(one for each
superframe)
8-bit DS0
LSB
User data
End-to-end control
lead propagation
(X.50 Telco only)
Data channels for each phase
X.50
X.50 Telco
E1 frame 1
2
3
4
5
Phase 1
Phase 2
Phase 3
Phase 4
Phase 5
DIV 2
DIV 3
DIV 3
1 x 9.6 kb/s 1 x 9.6 kb/s 1 x 9.6 kb/s
2 x 4.8 kb/s 2 x 4.8 kb/s 2 x 4.8 kb/s
4 x 2.4 kb/s 4 x 2.4 kb/s 4 x 2.4 kb/s
8 x 1.2 kb/s 4 x 1.2 kb/s 4 x 1.2 kb/s
16 x 0.6 kb/s
2 phases can accomodate 1 x 19.2 kb/s
All 5 phases can accomodate 1 x 48 kb/s
7180
Frame
1, 6, 11, 16, 21, 26, 31, 36,41, 46, 51, 56, 61, 66, 71, 76
2, 7, 12, 17, 22, 27, 32, 37, 42, 47, 52, 57, 62, 67, 72, 77
3, 8, 13, 18, 23, 28, 33, 38, 43, 48, 53, 58, 63, 68, 73, 78
4, 9, 14, 19, 24, 29, 34, 39, 44, 49, 54, 59, 64, 69, 74, 79
5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55, 60, 65, 70, 75, 80
In a 64 kb/s E1 channel, frames are transmitted at a rate of 8000 every second, so each
frame represents 600 b/s of bandwidth ([6 data bits 8000 every second]/80). X.50
Division 2 supports interface speeds of 0.6, 2.4, 4.8, 9.6 and 48 kb/s, so each phase
can contain:
23.6-12
(400)
Phase
Frame 1
Frame 2
Frame 3
Frame 4
Frame 5
Frame 6
Frame 7
Frame 8
Frame 9
Frame 10
Frame 11
Frame 12
Frame 13
Frame 14
Frame 15
Frame 16
Frame 17
Frame 18
Frame 19
Frame 20
7200
The framing pattern (the pattern of bits located in bit position 1 of every byte)
enables the receiver to identify and retrieve the individual subrate channels. The first
framing bit (A) of the 20-frame sequence indicates distant alarms, where 1 means no
alarm and 0 means an alarm.
(400)
23.6-13
In a 64 kb/s E1 channel, frames are transmitted at a rate of 8000 every second, so each
frame represents 2.4 kb/s of bandwidth ([6 data bits 8000 every a second]/20). X.50
Division 3 supports interface speeds of 2.4, 4.8, 9.6 and 48 kb/s, so each phase can
contain:
X.50 Telco
Basic X.50
Division 2
Division 3
Division 3
Framing Pattern
80 frame pattern:
5 phases of 16
frames each
20 frame pattern:
5 phases of 4
frames each
20 frame pattern:
5 phases of 4
frames each
Subrate Channels
Supported for each phase
1 x 9.6 kb/s
2 x 4.8 kb/s
4 x 2.4 kb/s
8 x 1.2 kb/s(1) or
16 x 0.6 kb/s(1)
1 x 9.6 kb/s
2 x 4.8 kb/s
4 x 2.4 kb/s(2) or
4 x 1.2 kb/s(2)
1 x 9.6 kb/s
2 x 4.8 kb/s
4 x 2.4 kb/s(2) or
4 x 1.2 kb/s(2)
Subrate Channels
supported for 2 phases
1 x 19.2 kb/s
1 x 19.2 kb/s
1 x 19.2 kb/s
Subrate Channels
supported for 5 phases
1 x 48 kb/s
1 x 48 kb/s
1 x 48 kb/s
12
(4)
(4)
Subrate Switching
Notes
1. The 1.2 and 0.6 kb/s channels occupy exactly 1.2 and 0.6 kb/s of bandwidth, respectively.
2. Each 1.2 kb/s channel connected to an X.50 or X.50 Telco Division 3 SRM is rate adapted by the
X.50 application into 2.4 kb/s of bandwidth for transport across the network (each 1.2 kb/s channel
is made of three data bits repeated as aabbcc to occupy six bits of bandwidth).
3. One input for each X.50 SRM can be an X.50 DS0 aggregate.
4. When the X.50 Telco SRM loses synchronization with the incoming signal, it sets the A bit in the
transmit direction.
5. Only MDDBs at channel speeds less than 19.2 kb/s are supported.
23.6-14
(400)
X.50 Telco
X.50 Telco is an enhanced version of basic X.50 that allows added functions, such as
control lead propagation and loopbacks. X.50 Telco supports ITU-T
Recommendation X.50 Divisions 2 and 3 multiplexing.
Both divisions support a bit-aligned framing pattern that consists of a framing bit
(A) in any bit position, followed by 6 data bits (D) and a status bit (S) in the eighth
position. The status bit, in conjunction with the data bits, conveys call control
information. Bit-aligned framing is used to re-align non-byte protocols.
The framing pattern (the pattern of bits located in the same bit position of every byte)
enables the receiver to identify and retrieve the individual subrate channels. The A
framing bit indicates distant alarms, where 1 means no alarm and 0 means an alarm.
You can configure an SRM as an X.50 Telco SRM; this means that the SRM supports:
The 3600 MainStreet series bandwidth managers systems also support two
non-standard X.50 interface speeds (1.2 and 19.2 kb/s) that can make the speeds
incompatible with the speeds of non-Newbridge equipment.
You can multiplex subrate channels together in any combination for a total of
48 kb/s. A 48 kb/s channel takes up all five phases, a 19.2 kb/s channel takes up two
phases and eight non-standard 1.2 kb/s channels take up one phase. You can
program the same or multiple speeds in the same 12.8 kb/s frame when you are
connecting between Newbridge systems. For other systems, you may need to
program the same speed in the 12.8 kb/s frame.
Basic X.50
Basic X.50 supports ITU-T Recommendation X.50 Division 3 multiplexing. As shown
in Figure 23.6-11, basic X.50 consists of a framing bit (A) in bit position 1, 6 data bits
(D) in positions 2 to 7 and a status bit (S) in bit position 8. The status bit, in
conjunction with the data bits, conveys call control information. The node manager
does not display the frame shown in Figure 23.6-1; it uses the bit numbering
convention used for a primary rate channel (shown in Figure 23.6-39).
You can configure an SRM and circuit as basic X.50 so that rate adaption, subrate
multiplexing and multidrop data bridge configurations are supported.
The system also supports two non-standard X.50 interface speeds (1.2 and 19.2 kb/s)
that can make the speeds incompatible with the speeds of non-Newbridge
equipment. Subrate channels can be multiplexed together in any combination for a
total of 48 kb/s.
(400)
23.6-15
For 1.2 kb/s circuits, a frame contains three data bits repeated in the pattern aabbcc,
using the same bandwidth as a 2.4 kb/s circuit. Four non-standard 1.2 kb/s channels
take up one phase. A 48 kb/s channel takes up all five phases, and a 19.2 kb/s
channel takes up two phases. As with X.50 Telco, you can program the same or
multiple speeds in the same 12.8 kb/s frame when you are connecting between
Newbridge systems.
23.6.2
Understanding SRMs
An SRM is an entity that processes bit streams from one or more circuits. It enables
several subrate circuits (voice or data) to be transmitted over a single 64 kb/s
channel.
As shown in Figure 23.6-13, an SRM acts as a two-way funnel: it merges the bit
streams received from branch channels and delivers the resulting bit stream to an
aggregate channel. An SRM also accepts the bit stream from an aggregate channel
and distributes it among branch channels.
The term branch channels refers to the channels on the distributed side of an SRM.
The term aggregate channel refers to the channel on the merged side of an SRM. The
number of branch channels in an SRM varies, but there is always only one aggregate
channel.
Figure 23.6-13: Branch Channels and Aggregate Channels
Merging
Branch
channels
Aggregate
SRM
channels
Distributing
3120
Transparent SRMs
For a transparent SRM, all the circuits connected to the branch channels must use
transparent rate adaption. You need to configure only one parameter for transparent
SRMs: the bandwidth of the aggregate channel.
As shown in Figure 23.6-14, the system displays the configuration of a transparent
SRM using a transparent channel. The Ts represent the elements allocated to
transparent channels. There are no blank elements allocated in this example.
23.6-16
(400)
B7
B6
B5
B4
B3
B2
B1
B0
B7
B6
B5
B4
B3
B2
B1
B0
B6
B5
B4
B3
B2
B1
B0
HCM SRMs
For an HCM SRM, the circuits connected to the branch channels can use either HCM
or transparent rate adaption. Before you connect any circuits to the branch or
aggregate channels of an HCM SRM, you must indicate which portion of the
bandwidth of the SRM is to be used for HCM data. The rest of the bandwidth is by
default available for transparent data.
You must configure three parameters:
(400)
23.6-17
B7
B6
B5
B4
B3
B2
B1
B0
B7
B6
B5
B4
B3
B2
B1
B0
B1
B0
B0
B7
B6
B5
B4
B3
B2
F = framing bit
= HCM bit position
T = transparent bit
Framing position = B5
Transport bandwidth = 48 kb/s (6 bit positions)
HCM bandwidth = 16 kb/s (2 bit positions)
B7
B6
B5
B4
B3
B2
B1
Note
When an SRM on a DCC card carries both HCM and transparent rate adapted
circuits, the state of the RTS (for DCE) or DCD (for DTE) control signal follows that
of the transparent circuit. This will disrupt the HCM circuits unless the transparent
circuit's RTS (or DCD) signal is set to ASSUMED_ON.
23.6-18
(400)
DDS SRMs
A DDS DS0-B SRM multiplexes several subrate DS0-A or HCM channels onto a
single aggregate channel that you can cross-connect to a DS0 on a primary rate
interface card. DS0-B SRMs increase bandwidth use by eliminating the redundant
stuff bytes in DS0-A channels.
The number of subrate channels you can multiplex together depends on their
interface speed: a maximum of five 9.6 kb/s channels, two 19.2 kb/s channels, ten
4.8 kb/s channels, or twenty 2.4 kb/s channels. Figures 23.6-18 through 23.6-21 show
the DS0-B framing structure for various speeds.
DS0-B channels can have one of three multiplexing schemes:
a 5-frame pattern containing five 9.6 kb/s channels (Figure 23.6-18), or two 19.2
kb/s channels and one 9.6 kb/s (or lower) channel (Figure 23.6-21)
a 10-frame pattern containing ten 4.8 kb/s channels (Figure 23.6-19)
a 20-frame pattern containing twenty 2.4 kb/s channels (Figure 23.6-20)
Each frame contains one byte from each subrate input channel in a fixed order. The
length of the pattern corresponds to the maximum number of subrate channels that
can be multiplexed at the indicated rate.
A subrate framing pattern (the pattern of bits located in bit position 1 of every byte)
is required for the receiver to identify and retrieve the individual subrate channels.
The framing pattern is different for each DS0-B frame length.
Figure 23.6-18: DS0-B Format for 9.6 kb/s and 19.2 kb/s DDS Channels
1
Frame 2
Frame 3
Frame 4
Frame 5
Frame 1
Frame 2
Frame 1
5 - frame
pattern
7205
(400)
23.6-19
Frame 2
Frame 3
Frame 4
Frame 5
Frame 6
Frame 7
Frame 8
Frame 9
Frame 10
Frame 1
Frame 2
Frame 1
10-frame
pattern
7206
You can multiplex DDS subrate channels with lower speeds onto a DS0-B channel
designated for a higher speed, but you cannot multiplex DDS subrate channels with
higher speeds onto a DS0-B channel designated for a lower speed. You should
always select the DS0-B multiplexing scheme to match the highest interface speed
that will be multiplexed onto the DS0-B channel.
For example, if you are multiplexing 9.6, 4.8 and 2.4 kb/s subrate channels,
configure the SRM for DS0-B operation with an interface speed of 9.6 kb/s. When the
4.8 kb/s DDS channel is connected to a branch channel, a new byte appears half as
often. The other frame contains a stuff byte (a repetition of the latest data). Similarly,
each byte of a 2.4 kb/s branch channel appears in four consecutive patterns (1 new
data byte and 3 stuff bytes).
There is an exception to the rule that the DDS channel must be configured for the
same or higher interface speed than that of the branch channel. DDS Core and DDS
Access (Version 2) support the 19.2 kb/s format directly, as shown in Figure 23.6-18.
For DDS and DDS Access (Version 1), you can use a DS0-B 9.6 SRM to multiplex
19.2 kb/s subrate channels, as shown in Figure 23.6-21. The 9.6 kb/s DS0-B SRM
multiplexes the first 19.2 kb/s channel (data byte A) in frames 2 and 3, and the
second (data byte B) in frames 4 and 5.
23.6-20
(400)
Frame 2
Frame 3
Frame 4
Frame 5
Frame 6
Frame 7
Frame 8
Frame 9
Frame 1
Frame 10
Frame 11
Frame 12
Frame 13
Frame 14
Frame 15
Frame 16
Frame 17
Frame 18
Frame 19
Frame 20
Frame 1
Frame 2
20-frame
pattern
7207
Frame 1
Frame 2
DA
DA
DA
DA
DA
DA
Frame 3
DA
DA
DA
DA
DA
DA
Frame 4
DB
DB
DB
DB
DB
DB
Frame 5
DB
DB
DB
DB
DB
DB
DA
DA
DA
Frame 1
Frame 2
DA
DA
5-frame
pattern
7185
(400)
23.6-21
After you configure the card for DDS operation, you can configure the SRMs on the
card for DS0-A formatting or one of the three DS0-B multiplexing schemes. For
SRMs configured as DS0-A, the interface speed selects the formatting pattern. If the
SRM has any connections (branches or aggregates), you cannot change the SRM
function.
DCCs
DNIC and 2B1Q Line cards
DSP, DSP2, DSP3, DSP5H and DSP5 cards
Table 23.6-4 lists the cards that support transparent and HCM SRMs and the total
number of SRMs and branch channels associated with each card.
Note
DSP2 and DSP3 cards support a total maximum of 50 aggregate and branch
channels.
Total Number
of SRMs
Number of Branch
Channels for Each DSP
DCC (1)
12
12
12
24
10
(2)
10
Notes
1. The RS-422 DCC does not support on-card SRMs.
2. DSP5H and DSP5 card SRMs are only intended for HCV circuits on the same DSP.
Two types of cards support DDS, DDS Access and X.50 SRMs:
23.6-22
(400)
Number of
SRMs in a
Card
Number of Branch
Channels in a Card
DDS SRM
DNIC with DPM2
12
12
12
12
DSP2 or DSP3
12
12
36
36
4 or 6 (1)
4 or 6 (1)
4 or 6 (1)
4 or 6 (1)
DSP2 or DSP3
4 or 6 (1)
4 or 6 (1)
12 or 18 (2)
12 or 18 (2)
DSP2 or DSP3
20
12
60
Notes
1. DDS Access (Version 1) supports six SRMs or branch channels; DDS Access (Version 2) supports
four of each.
2. DDS Access (Version 1) supports 18 SRMs or branch channels; DDS Access (Version 2) supports
12 of each.
Table 23.6-6 lists the cards that support X.50 and X.50 Telco SRMs.
Table 23.6-6: X.50 and X.50 Telco SRM Support
Card Type
Number
of SRMs
in a Card
Number of Branch
Channels in a Card
12
12
12
12
DSP2 or DSP3
12
12
36
36
DSP2 or DSP3
18
18
X.50 SRM
(400)
23.6-23
DCC
circuit 1
4182
Line cards
A DNIC or 2B1Q Line card has either a DPM or a DPM2 installed. As shown in
Figure 23.6-23, a line card supports eight transparent or HCM SRMs. Each DPM
contains two DSPs and each DSP supports four SRMs.
Figure 23.6-23: Transparent or HCM SRMs on a Line Card
circuit 2
4183
Each line card with a DPM2 supports twelve DDS or X.50 SRMs, or four (DDS Access
Version 2) or six DDS Access SRMs, or six X.50 Telco SRMs (see Figures 23.6-24 and
23.6-25).
Figure 23.6-24: DDS or X.50 SRMs on a Line Card
circuit 2
4187
23.6-24
(400)
DSP cards
For the DSP, DSP2 and DSP3 cards, the number of transparent or HCM SRMs
available on the card depends on how many DSPs are on the card. Each DSP
supports four transparent SRMs. In Figure 23.6-26, all the DSPs are configured to
support SRMs.
Note
The DSP5H and DSP5 cards provide one non-configurable SRM for each of their 10
DSPs.
DSP card
circuit 1
circuit 2
circuit 3
circuit 4
circuit 5
circuit 6
(400)
23.6-25
The number of DDS or X.50 SRMs supported on DSP2 and DSP3 card depends on
the DDS or X.50 application selected.
DDS or X.50:
DSP card
circuit 1
M01 M02 M03 M04 M05 M06
DDS access
SRMs
circuit 2
circuit 3
circuit 4
DDS SRMs
circuit 5
M01 M02 M03 M04 M05 M06
circuit 6
DDS access
SRMs
23.6.3
23.6-26
(400)
If you are configuring the branch channels as part of a multidrop data bridge, you
must position the data for each circuit so that exactly the same elements are
occupied. Chapter 23.7 describes multidrop data bridges.
Composite inputs
You can connect circuits that may contain multiplexed data (such as a primary rate
channel or an SRM aggregate channel) to an SRM. You define the channels as
COMPOSITE and the node manager lists them under the aggregate channel display
as composite inputs.
If you are connecting a primary rate circuit to a transparent or HCM SRM, you can
configure the type of channel it is carrying as transparent or HCM to indicate to the
system in which section of the SRM (transparent or HCM) to carry the composite
input.
The system shows no elements in the display because it has no way of determining
the occupied elements. You must determine the occupied elements from the
originating circuits and make sure that the elements do not conflict with the
elements of local circuits (in the case of subrate multiplexing), or that they match
exactly (in the case of a multidrop data bridge). If you configure composite inputs to
overlap non-multidrop circuits, data is corrupted.
Note
Only one composite input can be connected to an SRM. Cascaded SRMs are
considered as a single SRM.
If you are connecting a primary rate circuit to an SRM, you can indicate that it is
carrying a DDS channel and, if it is DS0-A, specify some of its characteristics.
If the channel is a DS0-B channel, you must determine the occupied positions from
the originating circuits and make sure that their positions do not conflict with the
positions of local circuits or that the positions match exactly for multidrop data
bridges.
(400)
23.6-27
Line cards
For transparent or HCM SRMs on a line card, you can connect the following circuits
to branch channels:
Each DSP on a line card DPM or DPM2 has 12 branch channels that you can allocate
to the 4 SRMs supported by that DSP in any combination, including all 12 to the
same SRM. Figure 23.6-28 shows branch channels and aggregate channels for
transparent or HCM SRMs on a line card DPM.
Before you connect circuits to a branch channel, you must specify what portion of
the 64 kb/s channel the data for each circuit will occupy. If you configure
subrate-multiplexing for the circuits, the data must not occupy the same elements. If
you are joining the circuits in a multidrop data bridge, the data must occupy the
same elements.
Figure 23.6-28: Channels on Line Card Transparent and HCM SRMs
circuit 1
4 aggregate
channels
12 branch
channels
circuit 2
4 aggregate
channels
4184
For DDS or X.50 SRMs on a line card, you can connect the following circuits to
branch channels:
DCC circuits
DNIC circuits
2B1Q circuits
SRM aggregate channels
primary rate channels
For X.50 SRMs, you can also connect 64 kb/s codirectional circuits.
23.6-28
(400)
DDS or X.50
As shown in Figure 23.6-29, each DDS or X.50 DPM2 has 12 branch channels that you
can allocate to the 12 SRMs in any combination, including all 12 to the same SRM. If
you connect a circuit with an interface speed of 19.2 kb/s to a DDS DPM2, the
number of branch channels available is reduced to nine.
Figure 23.6-29: Channels on Line Card DDS or X.50 SRMs
12 branch
channels
12 aggregate
channels
circuit 2
4189
circuit 1
M01 M02 M03 M04 M05 M06
circuit 2
4 or 6
aggregate
channels
4190
DSP cards
For transparent or HCM SRMs on a DSP card, you can connect the following circuits
to branch channels:
(400)
23.6-29
DSP card
12 branch
channels
circuit 1
4 aggregate
channels
12 branch
channels
circuit 2
4 aggregate
channels
4186
If a DSP module is installed, each DSP circuit configured for transparent or HCM
SRMs has 10 branch channels that you can allocate to the four SRMs supported by
that circuit in any combination. Figure 23.6-32 shows branch channels and aggregate
channels for a circuit on a six-circuit DSP card.
Note
DSP2 and DSP3 cards support a combined maximum of 50 aggregate and branch
channels.
23.6-30
(400)
Figure 23.6-32: Channels on Six-circuit DSP Card Transparent and HCM SRMs
DSP card
10 branch
channels
circuit 1
4 aggregate
channels
10 branch
channels
circuit 2
4 aggregate
channels
10 branch
channels
circuit 3
4 aggregate
channels
10 branch
channels
circuit 4
4 aggregate
channels
10 branch
channels
circuit 5
4 aggregate
channels
10 branch
channels
circuit 6
4 aggregate
channels
The DSP5H and DSP5 card provides one SRM for each of their 10 DSPs. DSP5H
SRMs provide two branch channels for HCV functionality. DSP5 SRMs provide one
branch channels for LD-CELP or A-CELP compressed voice functionality.
Note
The branch channels on the DSP5H and DSP5 cards are not configurable.
Figure 23.6-33 shows branch channels and aggregate channels for DSPs on the
DSP5H card.
(400)
23.6-31
DSP5H Card
DSP Resource #1
input
input
circuit 1
circuit 2
HCV circuit
branch
input
HCV circuit
branch
input
M1
1 aggregate
channel
M1
1 aggregate
channel
M1
1 aggregate
channel
DSP Resource #2
input
input
circuit 3
circuit 4
HCV circuit
HCV circuit
branch
input
branch
input
input
circuit 19
circuit 20
HCV circuit
HCV circuit
branch
input
branch
input
9591
23.6-32
(400)
DSP card
12 branch
channels
circuit 1
4 aggregate
channels
12 branch
channels
circuit 2
4 aggregate
channels
4186
As shown in Figure 23.6-35, each pair of DDS Access or X.50 Telco DSP circuits on a
DSP2 or DSP3 card has four (DDS Access Version 2) or six branch channels that you
can allocate to the four or six SRMs in any combination.
Figure 23.6-35: Channels on Six-circuit DSP Card DDS Access or X.50 Telco SRMs
DSP card
4 or 6
branch
channels
4 or 6
branch
channels
4 or 6
branch
channels
circuit 1
circuit 2
circuit 3
circuit 4
circuit 5
circuit 6
4 or 6
aggregate
channels
4 or 6
aggregate
channels
4 or 6
aggregate
channels
As shown in Figure 23.6-36, each DDS Core DSP circuit on a DSP2 or DSP3 card has
10 branch channels that you can allocate to the two SRMs in any combination.
(400)
23.6-33
DSP card
10 branch
channels
circuit 1
M01 M02
2 aggregate
channels
10 branch
channels
circuit 2
M01 M02
2 aggregate
channels
10 branch
channels
circuit 3
M01 M02
2 aggregate
channels
10 branch
channels
circuit 4
M01 M02
2 aggregate
channels
10 branch
channels
circuit 5
M01 M02
2 aggregate
channels
10 branch
channels
circuit 6
M01 M02
2 aggregate
channels
23.6.4
23.6-34
(400)
On the node manager screen, each element of a transparent channel represents 1 bit
transmitted at a rate of 8000 b/s, or 8 kb/s of bandwidth (1 bit 8000 b/s in 8 kb/s).
You set the transport bandwidth by entering the number of elements (1 through 8)
available to the device, so that the transport bandwidth equals the number of
elements times 8 kb/s. For example, you can establish an 8 kb/s channel by entering
1, or a 16 kb/s channel by entering 2. The default is eight elements or 64 kb/s.
The node manager displays transport bandwidth by placing a D in each allocated
bandwidth element position (B7 to B0). The node manager also lists the bandwidth
on the right side of the screen under Rate Adaption.
For example, in Figure 23.6-37, (a) shows a transparent channel with a transport
bandwidth of 16 kb/s (two elements) and (b) shows a transparent channel with a
transport bandwidth of 48 kb/s (six elements). In (a), the transport position is at B7;
in (b), it is at B5. Section 23.6.5 describes transport position.
Figure 23.6-37: Transparent Transport Bandwidth
B7
B6
B5
B4
B3
B2
B1
B0
B7
B6
B5
B4
B3
B2
B1
B0
D
7209
(400)
23.6-35
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7210
B7
B6
B5
B4
B3
B2
B1
B0
23.6-36
(400)
The following examples show some of the effects of connecting a data circuit to a T1
channel. In the examples, the bit number refers to the T1 channel and the data
channel element number is in brackets. It is assumed that the transport position is
always B7.
If the transport bandwidth is 64 kb/s (eight elements) and the customer data
23.6.5
protocol ensures an adequate ones density, JB7 does not alter bit 7 (B1).
If the transport bandwidth of the channel is 56 kb/s (seven elements), the system
automatically sets bit 8 (B0) to 1, ensuring an adequate ones density. JB7 does not
alter bit 7 (B1).
The RTS control lead signal is transported over all unused bandwidth in a
transparent circuit and over the signalling bit (S) in an HCM circuit. If RTS goes
low, bit 8 (B0) or S is changed to 0. To ensure ones density, you must configure
RTS to be high or on.
If the customer data protocol does not ensure an adequate ones density and bit 8
(B0) is altered (for example, by RBS or RTS signalling), JB7 may alter bit 7 (B1) and
make B1 unavailable for data. To prevent data errors, you must set the transport
bandwidth to 48 kb/s (six elements) or less.
If you are connecting a data circuit with a transport bandwidth of 64 kb/s (eight
elements) to a T1 channel with RBS enabled, you must turn off RBS or reduce the
transport bandwidth to 56 kb/s or seven elements so that bit 8 (B0) is not used.
Selecting B8ZS ensures an adequate ones density in the data stream and disabling
RBS allows you to use 64 kb/s of bandwidth (see chapter 20.8).
(400)
23.6-37
Table 23.6-7: Transport Bandwidth and Transport Position for Transparent Rate
Adaption
Transport Bandwidth
Transport Position
64 kb/s (n = 8)
B7 only
56 kb/s (n = 7)
B7 or B6
48 kb/s (n = 6)
B7, B6, B5
40 kb/s (n = 5)
B7 to B4
32 kb/s (n = 4)
B7 to B3
24 kb/s (n = 3)
B7 to B2
16 kb/s (n = 2)
B7 to B1
8 kb/s (n = 1)
B7 to B0
Set the transport position by entering Bn to define the starting element. The node
manager displays the transport position by the position of the left-most D. The node
manager also lists the bandwidth position on the right side of the screen under
Transport Posn. For example, in Figure 23.6-37, the transport position at (a) shows
B7 and (b) shows it at B5. The default transport position is B7.
The system gives priority to transport position over transport bandwidth, so that if
you change the transport position, you may also be changing the transport
bandwidth. If there are not enough elements to the right of the transport position,
the node manager reduces the transport bandwidth to the available amount, even if
you have configured it for more. To increase the transport bandwidth, you may need
to change the transport position first.
23.6.6
Understanding Signalling
The signalling parameter determines whether the DTU or DCC data in the HCM
frame includes a signalling bit stream (the S in Figure 23.6-38). Turning signalling off
means that no bandwidth is used for signalling.
23.6-38
(400)
S-bit signalling
S-bit signalling propagates all leads through the network. It is available in both
synchronous and asynchronous modes and uses 800 b/s of bandwidth within the
HCM frame. It cannot be provided in a pure transparent frame. S-bit signalling is
configured as:
H-bit Signalling
H-bit signalling propagates only DCD and RTS leads through the network. It
provides end-to-end signalling between a master and slave device in a multidrop
data bridge application (see chapter 23.7). H-bit signalling is available in both
synchronous and asynchronous modes and uses 800 b/s of bandwidth within the
HCM frame. It cannot be provided in a pure transparent frame.
Viewing H-bit signalling configurations
The 3600 and 3645 MainStreet units do not currently show support of H-bit
signalling. However, when you enable both S-bit signalling and multidrop data
bridging with a 3600 and 3645 MainStreet unit, in effect you are enabling H-bit
signalling.
For example, Figure 23.6-40 shows the setting, the NMTI display and the actual
HCM frame data bit positions for a 3600 and 3645 MainStreet unit with the 2612,
2613 and 2715 MainStreet DTUs. In case 4 of the figure, both S-bit and multidrop
data bridging are enabled. The NMTI display (middle column) for case 4 does not
indicate H-bit (H) in B3, even though the actual HCM frame does include the H-bit
in position B3 (far right column).
Figure 23.6-40: H-bit Signalling Results for 2612, 2613 and 2715 MainStreet DTUs
Setting
Case
H-Bit
S-Bit
MDDB B7 B6 B5 B4 B3 B2 B1 B0 B7 B6 B5 B4 B3 B2 B1 B0
D D D
D D D
S D D D
S D D D
D D D
D D D
S D D D
D D D H
9621
(400)
23.6-39
In case 4, the data within the HCM frame is shifted automatically left by one bit,
which means that there must be a free bit for the data to move into. For example, if
the HCM frame format is F_DDD and H-bit signalling is enabled, the frame changes
to FDDDH.
For circuits with H-bit signalling on, the handshake signals should be configured as
end-to-end. Table 23.6-8 shows the possible end-to-end signalling for various RS-232
and V.35 configurations, as well as the pin on which the signal is carried.
Table 23.6-8: End-to-End H-bit Signalling Configurations
From/To
DTU (DTE)
DTU (DCE)
DTU (DTE)
DCD RTS
pin 8 pin 4
DCD DCD
pin 8 pin 8
DTU (DCE)
RTS RTS
pin 4 pin 4
RTS DCD
pin 4 pin 8
You can disable H-bit signalling by disabling either multidrop data bridging or
signalling.
23.6.7
23.6-40
(400)
Note
For asynchronous devices, the tolerance for over-speed and under-speed is 2.5% of
the nominal data rate.
Data interfaces configured for external independent clocking do not support
1.2 kb/s operation. Do not connect them to an HCM SRM at this speed (see
sections 22.3.8 and 22.3.19).
Sync HCM
150 (1)
1600
8000
16800
300 (1)
2400
9600
19200
600 (1)
800
4800
14400
28800
1200
7200
16000
32000
RS-232
4000
12000
24000
300 (1)
2400
9600
19200
40000
600 (1)
4000
12000
24000
48000
800
4800
14400
28800
56000
1200
7200
16000
32000
57600
300
7200
600
9600
1200
14400
2400
19200
38400 (2)
150 (1)
1600
8000
16800
38400
Async HCM (3)
150
4800
38400
Notes
1. Supported by DCCs with gate array version 1 only.
2. RS-232 operation at interface speeds above 38.4 kb/s is not guaranteed (for speeds above
38.4 kb/s, V.35 or X.21 interfaces should be used). If RS-232 speeds above 38.4 kb/s are required,
use short high-grade shielded cable.
3. The 2606 MainStreet DTU or 2610 MainStreet DTU async DTU ports do not support 14400 b/s.
Oversampling
For HCM circuits, asynchronous rates of up to 2400 b/s that are not listed in
Table 23.6-9 can be supported by oversampling. To oversample, set the interface
mode to synchronous. Then, multiply the asynchronous rate you want to support by
16. Enter the next highest synchronous interface speed listed in Table 23.6-9.
For example, to support 110 b/s (asynchronous), set the interface mode to
synchronous. Set the interface speed to 2400 b/s (16 110 b/s = 1760 b/s and
2400 b/s is the next highest synchronous rate supported).
(400)
23.6-41
2400
4800
9600
19200
RS-232
1200
48000
2400
4800
9600
19200
The basic X.50 and X.50 Telco Division 3 applications support interface speeds of
48000, 19200, 9600, 4800, 2400 and 1200 b/s. The X.50 Telco Division 2 application
supports interface speeds of 48000, 19200, 9600, 4800, 2400, 1200 and 600 b/s. The
default is 9600 b/s.
23.6.8
23.6-42
(400)
The HCM bandwidth must be less than or equal to the aggregate channel
bandwidth. If you try to set the HCM bandwidth greater than the aggregate channel
bandwidth, the system displays the error message HCM bandwidth and transport
bandwidth conflict.
If the HCM frame bandwidth is less than the aggregate bandwidth, the system
automatically allocates the rest of the bandwidth to transparent data (indicated by
columns containing Ts).
If you change the transport position or transport bandwidth so that the data
The node manager automatically fills in the signalling bit to the left of the data
position if signalling is on (see section 23.6.6).
23.6.9
(400)
23.6-43
Table 23.6-11 gives the valid DDS positions. For DDS, the default is 1 for 56, 9.6, 4.8,
2.4 and 1.2 kb/s channels and 2 for 19.2 kb/s channels.
Table 23.6-11: Valid Subframe Positions for DDS
Interface Speed (kb/s)
Valid Positions
56
19.2
2, 4
9.6
1 to 5
4.8
1 to 10
2.4
1 to 20
1.2
1 to 20
Table 23.6-12 lists valid X.50 positions. For X.50, the default is 1 for each interface
speed. Position 1 represents phase 1, position 5 phase 2, position 9 phase 3, position
13 phase 4 and position 17 phase 5. In each case, these numbers represent the first
channel in the phase. The numbers between two phases represent the other
channels.
Table 23.6-12: Valid Subframe Positions for X.50
Interface
Speed
(kb/s)
Basic X.50
48
19.2
1, 9 or 5, 13
1 and 33 or 17 and 49
1, 9 or 5, 13
9.6
1, 5, 9, 13, 17
1, 5, 9, 13, 17
4.8
2.4
1 to 20
1 to 20
1.2
1 to 20
1 to 20
0.6
1 to 80
Note
When you change the interface speed, the subframe position reverts to the default
for the new speed. You cannot change the subframe position if the circuit is
connected.
23.6-44
(400)
23.6.10
CONT_CHK to enable it
NO_CONT_CK to disable it (default)
Figure 23.6-41: Continuity Checking on DS0-B SRMs
#1
Data devices
(9.6 kb/s)
SRM#1 performs
continuity checking
on these data devices
#2
DS0-B-9.6
SRM
Data devices
(9.6 kb/s)
DDS
network
DS0-B-9.6
SRM
(400)
23.6-45
#1
Data devices
(9.6 kb/s)
#2
DS0-A
SRMs or MJUs
Continuity checking
cannot be performed
on these data devices
Data devices
(9.6 kb/s)
DDS
network
DS0-A
SRMs or MJUs
23.6.11
Step
DDS or X.50
(1)
Connect the data circuit to the branch channel and the branch
channel to the SRM.
Notes
1. = Optional
23.6-46
(400)
HCM
Parameter
DDS
X.50
Continuity checking
(Telco)
Data position
HCM bandwidth
Interface speed
Signalling
Subframe position
Subrate multiplexing
Transport bandwidth
Transport position
HCM_TRANS
DDS
X.50
DDS_ACCESS
VERSION_1
X50_TELCO
VERSION_2
DIV_2
DIV_3
SK000148
Note
DDS Access VERSION_1 specifies pre-Release 6.0 versions of the 3600 MainStreet
series bandwidth manager systems.
(400)
23.6-47
METHOD
HCM
TRANP_BW
F_POSITION
<bw>
<Bn>
HCM_BW
<hcm_bw>
TRANSPAREN
SK000149
where
bw is the number of 8 kb/s elements (1 to 8*)
Bn is B7* to B0
hcm_bw is the number of columns (1 to 8*)
METHOD
DS-0A
POSITION
I/F_SPEED
<position>
<speed>
DS-0A_EC
DS-0B
MJU
CONT_CHK/
NO_CONT_CK*
MJU_EC
SK000150
where
position is a valid subframe position (see Tables 23.6-11 and 23.6-12)
speed depends on the rate adaption method (see section 23.6.7)
Note
If you select DS0A_EC or MJU_EC for BCH error correction, the system
automatically sets the interface speed to 19.2 kb/s. Error correction should be used
for point-to-point connections, so if you select error correction for one end of a
connection, you should also select it for the other end.
For information on MJUs, see chapter 23.7.
23.6-48
(400)
COMPOSITE/
NO_COMP*
METHOD
HCM
USER/SYSTEM* RATE_ADAPT
<Bn>
<speed>
<Ff-Bb>
TRANSPAREN
SK000151
where
bw is the number of 8 kb/s elements (1 to 8*)
Bn is B7* to B0
speed depends on the rate adaption method (see section 23.6.7)
Ff-Bb is F0 to F9 and B7 to B0 (F0-B5*)
COMPOSITE/NO_COMP*
METHOD
USER/SYSTEM*
POSITION
SIG_ON/SIG_OFF*
<position>
HCM
TRANSPAREN
RATE_ADAPT
I/F_SPEED
<speed>
DDS_HCM or DDS
X50_HCM or X.50
DIV_2
DIV_3
SK000152
where
position is a valid subframe position (see Tables 23.6-11 and 23.6-12)
speed depends on the rate adaption method (see section 23.6.7)
(400)
23.6-49
23.6.12
DDS rules
When you are making connections to DDS rate adapted SRMs, the following rules
apply.
You can connect a data circuit configured for DDS only to an SRM configured for
DDS.
You cannot connect a data circuit to a DS0-B SRM with a lower interface speed.
23.6-50
For example, you cannot connect a line card or DCC circuit at 9.6 kb/s to an SRM
configured for the DS0-B_4.8 or DS0-B_2.4 multiplexing scheme. The exception
to this rule is that you can connect a 19.2 kb/s circuit to a DS0-B_9.6 SRM.
The position of a DDS rate adapted circuit must be valid for the multiplexing
scheme of the SRM to which you are connecting it. For example, you cannot
connect a DCC or line card circuit with an interface speed of 2.4 kb/s and a
position of six to an SRM configured for the DS0-B_9.6 multiplexing scheme,
because the valid positions for that scheme are one through five.
The system does not automatically override connections. For example, if a data
circuit is connected to a DS0-A SRM, you cannot connect a different circuit to the
same SRM without explicitly disconnecting the first circuit.
Circuits connected to branch channels of DDS SRMs cannot be protected.
Branch channels should be configured with the same DDS format as the SRM,
except for DS0-A and DS0-A_EC, which are interchangeable, and MJU and
MJU_EC, which are also interchangeable.
(400)
X.50 rules
When you are making connections to X.50 rate adapted SRMs, the following rules
apply.
You can connect a data circuit configured for X.50 only to an X.50 SRM.
A data circuit you are connecting to an SRM cannot overlap any occupied
positions. For example, you cannot connect a DCC circuit with an interface speed
of 4.8 kb/s and a position of 3 to an SRM that is already connected to a 9.6 kb/s
circuit with a position of 1, because the 9.6 kb/s circuit occupies positions 1
through 4.
The system does not automatically override connections. For example, if a data
circuit is connected to an X.50 SRM, you cannot connect a different circuit to the
same position without disconnecting the first circuit.
Circuits connected to branch channels of X.50 SRMs cannot be protected.
The system assumes that circuits other than data circuits connected to SRMs
configured as X.50 are carrying X.50-formatted data in the correct format and
position for the configured multiplexing scheme. If this is not true, the data on
the connected circuit may be corrupted.
Note
When an SRM on a DCC carries both HCM and transparent rate adapted circuits, the
state of the RTS (for DCE) or DCD (for DTE) control signal follows that of the
transparent circuit. This will disrupt the HCM circuits unless the transparent
circuit's RTS (or DCD) signal is set to ASSUMED_ON.
(400)
23.6-51
23.7
23.7.1
a master device
a slave device
an MJU
MJU antistreaming
Aggregate
SRM
channels
Master device
Polling
3118
(400)
23.7-1
Circuit configuration
The data for each circuit in a multidrop data bridge must be positioned so that it
occupies the same elements. Each slave device transmits data in those elements at a
different time. The system automatically sets the configuration of the circuits
involved to half duplex and signalling off.
The master device communicates with the slave devices in the configured elements.
The system automatically sets the configuration of the master circuit to full duplex
and signalling off.
Caution
HCM multidrop data bridges do not support signal propagation. Do not configure
signalling on.
For circuits in an HCM or X.50 multidrop data bridge, the DCD control signal (if the
circuit is configured as gender DCE) or the RTS control signal (if the circuit is
configured as gender DTE) must be forced on (see section 22.3.7), unless H-bit
signalling is in use (see section 23.6.6).
If you are using the SRM for more than one data bridge or for subrate multiplexing,
the aggregate channel must be distributed at the far end before you can connect it to
the circuit carrying data for the master device.
Because certain circuits have been designated as slaves, the system connects those
circuits to the branch channels of the same SRM even though their data occupies the
same elements. The system does not connect circuits with overlapping data to the
branch channels of the same SRM unless they are designated as slaves.
Note
Do not use the copy adjust function in configuring a multidrop data bridge.
DDS SRMs
Any DDS SRM can support a multidrop data bridge configuration. If you want to
assign branch numbers to the DDS slave circuits, you must configure the SRM as:
DS0-A or DS0-A_EC
MJU or MJU_EC
Note
DS0-A_EC and MJU_EC configure the circuit for BCH error correction and set the
interface speed to 19.2 kb/s. For more information, see chapter 23.6.
23.7-2
(400)
MJUs
You can configure a DDS, DDS Access or DDS Core SRM as an MJU. Chapter 23.6
describes DDS rate adaption.
As shown in Figure 23.7-2, you can assign a unique identification number (1 to 4) to
up to four branch channels for each MJU.
Figure 23.7-2: Multijunction Units and Branch Identification Numbers
Branch
channels 1
2
3
MJU
Aggregate
Channel
Aggregate
MJU
Channel
Master
device
Slave
devices
Branch
identification numbers
8797
Antistreaming
If you select antistreaming for an DDS Access (Version 2) or DDS Core MJU, the
system monitors the MJU branches and disables any branch that streams for longer
than the time you specify.
23.7.2
(400)
23.7-3
DDS
DDS
Core
Step
X.50
()
(1)
()
()
()
()
()
Notes
1. () = optional
MASTER
SLAVE
DISABLE*
SK000153
23.7.3
Configuring MJUs
An MJU combines up to four DS0-A or DDS_HCM inputs to produce a composite
DS0-A signal that you can apply to a second MJU, multiplex into a DS0-B signal or
multiplex directly into a DS1 timeslot. Table 23.7-1 lists the process for configuring
an MJU.
23.7-4
(400)
DDS
DDS_ACCESS
VERSION_1
VERSION_2
SK000155
2.
DS-0A
DS-0A_EC
MJU
MJU_EC
SK000156
METHOD
BRANCH_ID
<number>
MJU
MJU_EC
SK000157
(400)
23.7-5
Note
If you select MJU_EC, the system selects BCH error checking and sets the interface
speed to 19.2 kb/s. For more information, see chapter 23.6.
23.7.4
The MJU branches inherit their antistreaming parameters from the MJU, but you can
enable and disable antistreaming for each branch.
You must configure antistreaming on the MJU before the system will monitor the
branches, but you must configure the branches before you make the connections.
This means that the branches may be enabled for antistreaming, but no monitoring
takes place until you enable the MJU for antistreaming.
Note
When you are connecting a composite input into an MJU, you must configure
antistreaming on the input branch. If the input branch is a primary rate circuit, you
must configure it as a composite (see section 23.6.3).
23.7-6
(400)
ENABLED*/
DISABLED
DATA_MON/
CTL_MON*
DECL_TIME
IDLE_TIME
<decl_time>
<idle_time>
SK000158
where
decl_time is from 0.5 to 6553.5 s in 0.5 s increments (15 s*)
idle_time is from 5 to 255 ms in 5 ms increments (5 ms*)
(400)
23.7-7
23.8
23.8.1
23.8.2
G3 fax relay
V.32 modem relay (DSP5 card only)
data transmission rate
data bandwidth
NSF frame handling mode
data transmit level
(400)
23.8-1
The DSP5 card has a default maximum V.32 modem transmission rate of 7200 b/s
for A-CELP circuits and 14400 b/s for LD-CELP circuits.
If the data device at the far-end does not support the configured transmission rate,
the circuit automatically attempts to negotiate a data connection at a lower rate.
23.8-2
(400)
Data bandwidth
Set the data bandwidth to a transmission rate that accommodates both the data
transmission rate and the compressed voice transmission rate. For example, if the
data rate is 4.8 kb/s and the compressed voice rate is 16 kb/s, the data bandwidth
must be set to 16 kb/s. Table 23.8-1 lists the possible data bandwidth configurations
which depend on voice compression, fax and modem rates and the rate adaption
method used.
Table 23.8-1: Possible Data Bandwidth Configurations
Data Bandwidth
Voice
Compression
Bandwidth
Fax Rate
Modem Rate
Rate Adaption
Method
8 kb/s
8 kb/s
4.8 kb/s
7.2 kb/s
Transparent /
HCM
9.6 kb/s
8 kb/s
9.6 kb/s
7.2 kb/s
HCM
10.4 kb/s
8 kb/s
9.6 kb/s
9.6 kb/s
HCM
12.8 kb/s
8 kb/s
9.6 kb/s
12 kb/s
HCM
14.4 kb/s
8 kb/s
14.4 kb/s
12 kb/s
HCM
15.2 kb/s
8 kb/s
14.4 kb/s
14.4 kb/s
HCM
16 kb/s
8 kb/s
14.4 kb/s
14.4 kb/s
Transparent /
HCM
16 kb/s
16 kb/s
14.4 kb/s
14.4 kb/s
Transparent /
HCM
Use the DATA_BW softkey to select a value from 1 to 20 (1 to 16 000 b/s in 800 b/s
increments).
NSF_TRANSP so that the DSP card forwards but does not process the contents
of the NSF frame; this allows the data devices to negotiate and use non-standard
features
Caution
Configuring NSF_TRANSP could result in the failure of a fax call.
NSF_BLOCK so that the DSP card does not forward NSF frames and the data
devices do not negotiate or use non-standard features
(400)
23.8-3
The configurable range for transmit and receive gain levels is from 12 to +12 dB in
increments of 0.1 dB. The default setting for transmit and receive gain levels is 0 dB.
Note
Transmit and Receive gain levels are independent of the data transmit level. The
transmit gain level must be taken into account when specifying the data transmit
level, as it is added to the data transmit level.
23.8-4
(400)
DATA_CFG
RATE_ADAPT
DATA_TXLVL
DATA_BW
<level>
<n>
FAX_CONFIG
FAX_ENABLE*/ FAX_RATE
FAX_DISABL
NSF_HANDLG
NSF_TRANSP
4800
NSF_BLOCK*
9600*
SK000160
where
n is 1 to 20* (1 to 16 000 b/s in 800 b/s increments)
level is 15 to 3 dBm0 (* = 13 dBm0)
RATE_ADAPT
DATA_BW
<n>
FAX/MODEM
FAX_DISABLE/
FAX_ENABLE*
LEVELS
FAX_RATE
MODEM_RATE
V32_DISABLE/
V32_ENABLE*
FAX_HANDLG
NSF_TRANSP
<tlp>
<data_tx>
SK001046
where
n is 1 to 20* (1 to 16 000 b/s in 800 b/s increments)
tlp is 120 to +120 (0*)
data_tx is 30 to 6 dBm0 (* = 13 dBm0)
(400)
23.8-5
Note
The default FAX_RATE is 4800 for A-CELP circuits and 14400 for LD-CELP circuits.
The default MODEM_RATE is 7200 for A-CELP circuits and 14400 for LD-CELP
circuits.
RATE_ADAPT
DATA_BW
<n>
FAX/MODEM
FAX_DISABLE/
FAX_ENABLE*
FAX_RATE
4800
LEVELS
FAX_HANDLG
9600*
NSF_TRANSP
<data_tx>
NSF_BLOCK*
SK000820
where
n is 1 to 20* (1 to 16 000 b/s in 800 b/s increments)
tlp is 120 to +120 (0*)
data_tx is 30 to 6 dBm0 (* = 13 dBm0)
23.8-6
(400)
23.9
Subrate Switching
This chapter introduces SRS on the DSP4 card and explains how to configure subrate
switching, create a subrate set, configure DS0 ports for SRS, and make SRS
connections.
23.9.1
Understanding SRS
An SRS lets you switch data at rates down to 800 b/s. You can group individual bits
together in subrate sets that then operate as a single entity.
As shown in Figure 23.9-1, there are three components in an SRS connection:
(400)
23.9-1
Data on a
DNIC SRM
F a a
64 kb/s connections
DSP4 card
DS-0
Port
Source and
destination
devices
SRS
Data on a
DCC SRM
c F
c
c
c
Data on an
E1 SRM
c F b
c
b
64 kb/s connections
c
c
b
3093
A switching shelf controlled system supports a total of 48 DSP4 cards configured for
SRS, with a maximum of eight DSP4 cards configured for SRS in any one peripheral
shelf. A locally controlled system supports a total of eight DSP4 cards configured for
SRS.
In a single-bandwidth slot, the DSP4 card supports fully non-blocking, full-duplex
SRSs for up to 30 DS0 (64 kb/s) ports; in a double-bandwidth slot, it supports up to
48 DS0 (64 kb/s) ports.
Use the 4602 MainStreet Intelligent NetworkStation or MainStreetXpress 46020
Network Manager for full subrate switching functionality.
SRS display
Figure 23.9-2 shows a partially filled SRS and Table 23.9-1 describes the symbols in
the display.
23.9-2
(400)
B6
B5
B4
B3
B2
B1
B0
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
7269
Definition
Framing bit
When you are scrolling between transparent or HCM sets, ungrouped bits are
skipped over unless they are program-connected. If the current group is the first
group and you try to move to a previous group, the system displays the message
Showing first set. If the current group is the last group and you try to move to the
next group, the system displays the message Showing last set.
23.9.2
Configuring SRS
Table 23.9-2 lists the steps in the SRS configuration process. The steps followed
depend on whether you are configuring an SRS set using transparent, HCM or X.50
data bits, DDS data bits, or 4 kb/s CPSS.
(400)
23.9-3
DDS
Step
CPSS
Specify set identifiers for DDS and X.50 in the format <sn-SRS-dd-set_id>. For
example:
CONFIG CONNECT <sn-SRS-dd-set_id>
where
sn = slot number
SRS = subrate switch
dd = DS0 port: 1 to 30 without double bandwidth or 1 to 48 with double bandwidth
set_id = see Table 23.9-3
23.9-4
(400)
DS0-A
1 to 20
1 to 10
1 to 5
1 to 20
1, 5, 9, 13, 17
5, 13 or 1, 9
X.50 48 kb/s
TYPE
OPTIONS
OTHER
SRS
DSP
DSP4
SK000161
COPY_TO
FUNCTION
<sn-SRS-dd>
CHG_SET
PREV_SET NEXT_SET
NEW_SET ADD_TO_SET
DEL_FR_SET DEL_SET
SK000162
(400)
23.9-5
23.9.3
Bits in the same set must use the same rate adaption method.
Bits in the same set must lie in the same DS0 switch.
Each bit belongs to one subrate set only.
A single bit is classified as a subrate set only if it is program-connected.
Creating sets
A subrate set is identified by the starting bit (the set identifier). The order of
transparent and HCM bits is assigned from the top left (F0B7) of the HCM map
(Figure 23.9-2) across to the bottom right (F9B0).
When you are creating a new set, or adding or deleting bits from an existing set, you
must enter a set identification number. After you enter the set identification number,
the node manager gives you the option of listing multiple bits.
For transparent rate adaption, enter the list in the form Bb1:Bb2, where Bb1 is the
column number of the first bit in the set and Bb2 is the column number of the last bit
in the set. For example, B7:B2 means that the bits are in columns B7 to B2. If you are
specifying a single bit position, enter only Bb1.
For HCM rate adaption, enter the list in the form Ff1Bb1:Ff2Bb2, where Ff1Bb1 is the
location of the first bit in the set and Ff2Bb2 is the location of the last bit in the set. For
example, F1B6:F1B1 means that the first bit in the set is located in position F1B6 and
the last bit in the set is located in position F1B1. If you are specifying a single bit
position, enter only Ff1Bb1.
If you try to enter a bit or set position that includes the location of the F-bit, the
system displays the message WARNING: Cannot select the F-Bit.
23.9-6
(400)
If you try to enter a bit or set position incorporating a bit position that is already in
another set, the system displays the message WARNING: Proceed will destroy
connections and configuration.
If you try to create a new set that contains bits of different rate adaption methods,
the system displays the message Illegal list bits have mixed data format.
2.4 kb/s
4.8 kb/s
9.6 kb/s (default)
19.2 kb/s
56 kb/s
DDS DS0-B rate adaption for subrate sets supports three interface speeds:
2.4 kb/s
4.8 kb/s
9.6 kb/s (default)
For an X.50 subrate set, you must configure the rate adaption method as X.50 and set
the interface speed as one of:
2.4 kb/s
4.8 kb/s
9.6 kb/s (default)
19.2 kb/s
48 kb/s
For an X.50 subrate set, you must define a sub-frame position. The number is a
subset of the 20 sub-frame positions. Table 23.6-12 lists valid sub-frame positions (set
identifiers) for each interface speed.
CPSS sets
An SRS cannot terminate CPSS data. You must connect a DCP circuit (with ANS
disabled) to one of the circuits on the switch with which CPSS data is switched.
(400)
23.9-7
The SRS can rate-adapt 4 kb/s HCM CPSS into a format usable by a DCP circuit. In
the case where composite data is carrying CPSS, the SRS extracts the 4 kb/s CPSS
data from the circuit, rate adapts it and switches it to the destination circuit where a
DCP circuit is connected.
When you configure a circuit for 4 kb/s CPSS, the entire DS0 is used to carry the
CPSS.
For other CPSS speeds (such as 8, 16, 48 and 56 kb/s), you must configure the SRS as
transparent and use the bit positions beginning at B7 to be compatible with the DCP
cards.
To create sets
CONFIG CIRCUIT <sn-SRS-dd> FUNCTION
METHOD
TRANSP_BW
F_POSITION
HCM_BW
<bw>
<Bn>
<hcm_bw>
I/F_SPEED CHG_SET
<speed>
<position>
HCM*
TRANSPAREN X.50
DDS
DS-0A
CPSS_4K
DS-0B
ADD_TO_SET
<Bb1:Bb2> or
<Ff1Bb1:Ff2:Bb2>
DEL_FR_SET
DEL_SET
<set_id>
<Bb1:Bb2> or <Ff1Bb1:Ff2:Bb2>
SK000163
where
bw is the number of 8 kb/s elements (1 to 8*)
Bn is B7* to B0
hcm_bw is the column position (8*)
speed is in b/s to indicate the speed for a DDS or X.50 set (9600 b/s*)
position is the subrate position for an X.50 set (see Table 23.6-12)
set_id is the set identifier (see Table 23.9-3)
Bb1:Bb2 and Ff1Bb1:Ff2:Bb2 specify the locations of the first and last bits in a transparent and HCM set,
respectively
23.9-8
(400)
23.9.4
The X.50 interface speed configuration sets up the subrate sets of the X.50 frame.
If you try to configure a parameter that is not applicable to the rate adaption method,
the system displays the message Function key not valid with rate adaption
method.
To configure these parameters, see chapter 23.6. Table 23.1-2 provides the locations
of the configuration procedures.
23.9.5
The circuit types that you cannot connect to an SRS DS0 port are:
voice circuits
delta signalling ADPCM compressed voice circuits
(400)
23.9-9
Transparent or HCM
Transparent or HCM
DDS (DS0A/DS0B)
DDS (DS0A/DS0B)
X.50
X.50
HCM
CPSS
If you try to make a connection and the rate adaption methods are not the same, the
system displays the message Rate adaption modes do not match.
Caution
If you change any attribute of a circuit, the system destroys all connections and the
subrate set configuration associated with it.
Note
A data device connected to a DS0 port must have a rate adaption method compatible
with the configuration of the DS0 port.
23.9-10
(400)
(400)
23.9-11
23.10
23.10 BONDING
Issue 1, November 1997
BONDING
This chapter introduces how to configure BONDING and make BONDING
connections.
23.10.1
Understanding BONDING
BONDING is a method of inversely multiplexing an n 56 kb/s or n 64 kb/s call
and transmitting it over networks in which the differential delay is unknown. The
BONDING protocol communicates with the remote end to set up the appropriate
number of channels. It enables the receivers to calculate the amount of delay needed
to make sure that the data is received in the same order in which it was transmitted.
As Figure 23.10-1 shows, the data stream may become delayed as it is inversely
multiplexed and then sent over channels with varying delays.
Figure 23.10-1: Data Transmission without BONDING
64 kb/s
network
ABC
A Channel 1
B Channel 2
C Channel 3
? ? ?
A Channel 1
B Channel 2
C Channel 3
6615
Figure 23.10-2 shows the same data stream with the BONDING function providing
delays for the quicker 64 kb/s lines, allowing the order of the data stream to remain
intact.
(400)
23.10-1
23.10 BONDING
Issue 1, November 1997
ABC
64 kb/s
Network
BONDING
BONDING
ABC
n x 64 kb/s
n x 64 kb/s
A Channel 1
A Channel 1
B Channel 2
B Channel 2
C Channel 3
C Channel 3
6616
Using BONDING
Typically, BONDING is used when inversely multiplexed 56 kb/s or 64 kb/s links
need to go over ISDN or different T1 or E1 streams to reach the remote end. This
practice results in an unpredictable delay between the channels, so BONDING is
used to equalize the delays and maintain data integrity.
Figure 23.10-3 shows a typical leased application in which two communicating data
devices (in 3600 MainStreet nodes #1 and #3) do not have enough bandwidth for
direct connection. The network manager takes the available three 64 kb/s timeslots
between 3600 MainStreet node #1 and 3600 MainStreet node #3 and three timeslots
between 3600 Mainstreet node #1 and 3600 MainStreet node #2 (and then the three
64 kb/s links between 3600 MainStreet node #2 and 3600 MainStreet node #3). Since
the delay is unpredictable, BONDING resources on 3600 MainStreet node #1 and
3600 MainStreet node #3 negotiate and equalize the delay.
Figure 23.10-3: BONDING Application
3600 MainStreet node #1
with BONDING
Data device #2
(384 kb/s)
Data device #1
(384 kb/s)
3 x 64 kb/s
3 x 64 kb/s
23.10-2
(400)
23.10 BONDING
Issue 1, November 1997
BONDING operation
The BONDING protocol begins with the two endpoints transmitting data over the
channels to exchange channel identifiers. This practice makes sure that each end has
the same channel identifiers. Then the endpoints transmit synchronization data over
the channels to allow the receivers at each end to determine the appropriate delays
to add to each frame so that the data stream is equalized. When delay equalization
is finished, the communications path is opened and data transfer can begin. Each
BONDING resource inversely multiplexes the n 56 kb/s or n 64 kb/s link into n
or n+1 separate 56 kb/s or 64 kb/s channels.
As Figure 23.10-4 shows, the side supplying the n 56 kb/s or n 64 kb/s data
stream is called the user side, and the side with the inversely multiplexed channels
is called the network side. During the call setup phase, the BONDING resource
determines the delay. When data is received from the network side during the data
transfer phase of the call, the BONDING resource applies the predetermined delay
to the 56 kb/s or 64 kb/s channels as appropriate and then sends the n 56 kb/s or
n 64 kb/s data stream to the user side. Until the data transfer begins, the user side
receives a continuous stream of ones from the BONDING resource.
Figure 23.10-4: BONDING in the 3600 MainStreet System
BONDING
User side
Network side
56 or 64 kb/s
1
2
n x 56 or 64 kb/s
IMC
n or n + 1
6617
The 3600 MainStreet system supports two BONDING modes: mode 1 and mode 3.
Mode 1 does the channel setup and then the delay equalization. Mode 3 BONDING
does the same as mode 1, and monitors the synchronization during the data transfer
phase of the call. Mode 3 operation uses an extra channel between the BONDING
resource and the network side for framing information resulting from this
monitoring.
A BONDING resource is a DSP circuit on an IMC. There are six DSP circuits on each
IMC. The user side can be any interface card capable of making super-rate
connections (any primary rate card and some DCCs). The network side can be any
of the E1, T1, E3, DS-3, BRI or 64 kb/s Codirectional cards or the 2B1Q channel unit,
or ISDN indices on the CPC.
(400)
23.10-3
23.10 BONDING
Issue 1, November 1997
23.10.2
Configuring BONDING
You can configure four BONDING parameters on the IMC:
mode (MODE)
bearer rate (BEARERRATE)
user side interface speed (I/F_SPEED)
synchronization alarm (see Maintenance, section 35.4.1).
To configure BONDING
CONFIG CIRCUIT <sn-cc> FUNCTION
MODE
BEARERRATE
I/F_SPEED
<speed>
MODE_1
MODE_3*
56k
64k*
SK000164
where speed is the user side interface speed in terms of kb/s; it must be a multiple of the bearer rate
23.10-4
(400)
23.10 BONDING
Issue 1, November 1997
Note
Bond setup allows you to change the BONDING call setup. If bond setup is set to
ON, the end type is configurable. If the end type is set to ANSWERING, you are able
to view and change the values of the directory numbers.
The mode, bearer rate, interface speed and synchronization alarm softkeys are the
same for the BONDING call setup configuration as they are for the BONDING
configuration (see above). The following shows the softkeys available for bond
setup, end type and directory.
BOND_SETUP
END_TYPE
DIRERCTORY
ON/OFF*
ANSWERING* CALLING
MODIFY_ONE
MODIFY_ALL
SK000165
Figure 23.10-5 shows the NMTI screen for IMC circuits with BONDING call setup
enabled.
(400)
23.10-5
23.10 BONDING
Issue 1, November 1997
1117-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NAME:
B7 B6 B5 B4 B3 B2 B1 B0
D D D D D D D D
Configured As
:
Rate Adaption
:
Interface Speed
:
Bearer Channel Rate:
Number of Branches :
Alarm Declare time :
Alarm Clear time
:
BOND Setup
:
End Type
:
BOND_MODE_3
BONDING - MODE_3
384 kbps
64 kbps
7
3 seconds
3 seconds
ON
Answering
D = DATA
CONFIG CIRCUIT 1-1 FUNCTION
1-MODE
6-
23.10.3
27-
38-CANCEL
49-QUIT
5-BOND_SETUP
0-
make the super-rate connection between the user side circuit and the DSP on the
IMC
connect the DSP branch channels to the network side circuit
23.10-6
(400)
23.10 BONDING
Issue 1, November 1997
Note
Although there are six DSP circuits on the IMC, the total number of backplane
channels is 60. With each BONDING channel using one channel for the user side
connection and one channel for the network side connection, the maximum number
of 64 kb/s links using BONDING on each IMC is 30. When mode 3 BONDING is
selected, this number is smaller because n+1 connections between the DSP and the
network side are needed for n connections between the user side and the DSP.
Because the DSP has only one bidirectional serial port, the interface with the
processor is limited to 32 links of 64 kb/s each. Two of these links are used for
message exchanges. As each BONDING channel needs one channel for the user side
connection and one for the network side connection, the maximum number of
56 kb/s or 64 kb/s links that can be used for BONDING on each DSP is 15.
(400)
23.10-7
23.11
23.11.1
(400)
23.11-1
23.11.2
The super tandem synchronization time is the amount of time it takes for the super
tandem circuit to determine whether the remote circuit has super tandem operation
enabled. For the DSP4 card this value can range from 0.1 to 3.1 seconds in 0.1 second
increments. The synchronization time range for the DSP5H and DSP5 card is from
0.1 to 5.0 seconds in 0.1 second increments.
You connect super tandem circuits the same way as HCV and A-CELP circuits (see
chapter 23.3).
23.11-2
(400)
stHCV_DIS/
stHCV_EN*
FORCE_ON/FORCE_OFF*
SYNC_TIME
<sync>
SK000819
DISABLE/ENABLE*
FORCE_ON/FORCE_OFF*
SYNC_TIME
<sync>
SK000818
(400)
23.11-3
23.12
23.12.1
Card
DSP4
HCV
LD-CELP
DSP5
DSP5H
A-CELP
Super
Tandem
G3 Fax Relay
V.32 Modem
Relay
Notes
1. For DSP5 cards, super tandem operation is supported only on circuits configured for A-CELP voice compression.
Figure 23.12-1 shows a DSP4 card equipped with a fax/HCV module, which is
connected to an analog voice interface (LGE card or channel unit) for input and an
aggregate interface (T1 card) for output. By automatically switching between data
and voice mode, the voice compression data application allows both data and voice
to share the same aggregate bandwidth.
(400)
23.12-1
MainStreet node
Phone
LGE
PBX-1
DSP4
fax/HCV
module
T1
Network
FAX
5368
From the access side, the card accepts a PCM-encoded stream representing a
voiceband signal. The card then decides whether the signal is modulated data or
voice and processes it in data or voice mode accordingly.
In data mode, the card demodulates the signal and transports this digital data over
the network. The DSP4 and DSP5H cards can operate at either 4800 or 9600 b/s. The
DSP5 card can operate at either 4800, 9600 or 14 400 b/s for fax transmissions, or at
either 4800, 7200, 9600, 12000 or 14 400 b/s for V.32 modem transmissions.
The transmission mode changes from data to voice if the card detects any of the
following conditions:
In voice mode, the card which is using A-law or Mu-law companding (as
configured), compresses the PCM voice samples to either 8 or 16 kb/s using voice
compression and transports this data over the network. The transmission mode
changes from voice to data mode if the card:
23.12.2
23.12-2
(400)
The DSP5 card also offers combined V.32 modem relay and compressed voice
functionality. These combined operations provide the same modem relay
capabilities as for ordinary modem relay. Chapter 23.8 describes V.32 modem relay.
You can connect the same types of circuits to the data and super tandem circuit as
those you connect to a standard HCV or A-CELP circuit. (Chapter 23.3 describes
voice compression circuit connections). These circuits can support data bandwidths
of 8, 9.6 and 16 kb/s for HCM rate adapted channels, and 8 and 16 kb/s for
transparent channels.
The 8 kb/s configuration allows data rates up to 4.8 kb/s and voice compression at
8 kb/s. The 9.6 kb/s configuration allows data rates up to 9.6 kb/s and voice
compression at 8 kb/s. The 16 kb/s configuration allows data rates up to 9.6 kb/s
and voice compression at 8 or 16 kb/s. For a complete list of possible data bandwidth
configurations, see section 23.8.2.
To enable combinedoperations, configure the following:
(400)
23.12-3
24.1
24.1.1
24.1.2
Options
Card Level
CPSS
Slot Level
DCP Cards
Card slot
DCP
4 kb/s CPSS
4 kb/s CPSS
no 4 kb/s CPSS
Backplane communications
dedicated
shared*
Serial port
(400)
24.1-1
24.2
24.2.1
24.2.2
DCP Cards
(400)
24.2-1
TYPE
OPTIONS
4KBPS/NO_4KBPS*
AS_PRESENT
PACKET
DCP
SK000167
Note
Use the AS_PRESENT softkey if there is a DCP card installed in the slot.
To configure all slots programmed as EMPTY to the default configurations of the
cards installed in the shelf, press the CONFIG_ALL softkey and the <Esc>
simultaneously.
24.2-2
(400)
DCP Cards
25.1
25.1.1
Part Number
Generic
90-1459-03 or 04
90-3259-01
P114
FRE
90-1638-10 or 11
P413
X.25 FRE
90-1638-13 or 14
PA11 F2
PE
90-2311-01 or 12
P611 F2
The FRS, FRE and PE cards give the node the ability to switch the output of the frame
relay interfaces offered by user devices over any primary rate or data link. The FRS
card provides a maximum sustained throughput of 2000 fps, which is 64-byte frames
over a 1920 kb/s frame stream. The FRE card provides a maximum sustained
throughput of 10 000 fps, which is 64-byte frames over two 1536 kb/s frame streams.
(400)
25.1-1
For frame relay switching, the FRS, FRE and PE cards comply to the relevant sections
of the following standards:
ANSI T1.618
ITU-T Q.922 Annex A
Addendum to ANSI T1.606
ANSI T1.617a Annex D (1994)
ITU-T Q.933 Annex A (1994)
Frame Relay Forum document number 001-208966
The FRS card is designed for small to medium frame relay switching requirements.
FRS cards are typically used independently, although FRS-to-FRS card connections
are supported using the circuit-switched backplane bus. FRS cards also support
HDLC encapsulation services that allow them to function as feeder nodes for X.25
subrate or super-rate access to PE or X.25 FRE cards.
The FRE and PE cards are designed for high-capacity frame relay switching
requirements. Up to 64 FRE or PE cards can be used in a 36120 MainStreet system.
FRE and PE cards access both the circuit-switched backplane bus and a 100 Mb/s
packet-switched bus called the FASTbus to provide high-speed connections
between the cards.
Frame streams
A frame stream specifies the bandwidth over which frame relay connections
operate. You can configure a frame stream on any primary rate or data link. On a
primary rate link, you can configure a frame stream on any part of the link, allowing
both frame-relay and circuit-switched service on the same link.
The FRS card supports up to 31 frame streams with a combined bandwidth of
1984 kb/s. Any one frame stream can have a bandwidth of up to 1920 kb/s.
The FRE and PE cards supports up to 62 frame streams with a combined bandwidth
of 3968 kb/s. Bandwidth is split between two backplane buses, each of which
supports a bandwidth of up to 1984 kb/s or 31 channels of 64 kb/s each. Any one
frame stream can have a bandwidth of up to 1984 kb/s. Each FRE and PE card also
has access to the FASTbus.
25.1-2
(400)
Total DLCs
DLCI Range
1024
16 to 1007
1984
16 to 1007, and
2000 to 3983
992
16 to 1007
1984
2000 to 3983
Bandwidth use
In a frame relay network, idle DLCs do not consume any bandwidth. DLCs share the
frame stream bandwidth, which the system allocates on demand.
In Figure 25.1-1, when FRE 1 needs to transmit a frame on DLC 876, the system
allocates all the bandwidth configured for frame stream S12 to the transmission.
While DLC 875 is idle, it consumes no bandwidth.
(400)
25.1-3
S9-875
S12-875 X S9-875
S12-876 X S7-876
FRE
2
S12
S7
36120
MainStreet
S2-875
S2-876
S9
S2
S9-876
FRE
8230
1
MainStreet bridge
A
36120 MainStreet bridge
S2-875 X S12-875
S2-876 X S12-876
FRE
3
8230
MainStreet bridge C
36120 MainStreet bridge
S7-876 X S9-876
4076
Class-of-service parameters
The bandwidth allocated to its frame stream limits a DLC maximum throughput (or
access rate). You can configure class-of-service parameters for each DLC
individually to define the maximum throughput and burst size allowed on the DLC.
This practice lets you control the amount of bandwidth consumed by one DLC and
prevents a large burst of traffic on one DLC from depriving others of the bandwidth
they share.
The four class-of-service parameters are:
CIR:
25.1-4
Specifies the rate of user data transfer that the network commits to transfer under
normal conditions.
Bc:
Specifies the maximum number of bits of user data that the network commits to
transfer over the committed rate measurement interval (Tc) under normal
conditions.
Be:
Specifies the maximum number of bits of uncommitted user data in excess of Bc
that the network attempts to transfer over the committed rate measurement
interval (Tc).
Tc:
Defines the time interval over which the user may transfer Bc bits of committed
or Bc+Be bits of uncommitted data. Tc is not a periodic measurement interval, but
a sliding window used to measure the rate of incoming data. Tc is not
user-configurable. When CIR and Bc are > 0, Tc is calculated as Bc/CIR. When
CIR and Bc = 0, Tc is calculated as Be/Access Rate.
(400)
ss
ra
te
Ac
ce
Discard
all frames
Be + Bc
t
urs
rat
.b
x
Ma
Bc
Send frames
as discard eligible
CIR
Send frames
as received
To
To + Tc
2832
Congestion management
The FRS, FRE and PE card congestion management mechanisms use class-of-service
parameters to avoid and recover from switch, FASTbus and frame stream
congestion.
Note
When an FRS, FRE or PE card becomes congested, the congestion affects only that
card. It does not affect other FRS, FRE or PE cards or the Control card.
The FRS, FRE and PE cards respond to congestion indicators in a private frame relay
network made up of FRS, FRE and PE cards, and when connected to a public frame
relay network or customer premise equipment.
(400)
25.1-5
An FRS, FRE or PE card becomes congested when the applied traffic load exceeds its
capacity. Under these conditions, the card buffers frames. The system measures the
degree of congestion in terms of buffer use: the higher the use, the greater the
congestion. The system measures buffer use against user-configured congestion
thresholds.
CPU congestion occurs when the switching capacity of the card CPU is exceeded.
When this capacity is exceeded, a CPU Congested alarm is raised.
This chapter describes the following congestion management aspects:
congestion thresholds
congestion notification parameters (FRE and PE only)
congestion avoidance
congestion recovery
Congestion thresholds
For the FRS card, you can configure congestion thresholds for the switch and for
each frame stream. For the FRE and PE cards, you can configure congestion
thresholds for the switch, FASTbus interface and each frame stream. Table 25.1-3
summarizes the congestion threshold options available for the cards.
Table 25.1-3: FRS, FRE and PE Card Congestion Thresholds
Card
ACT
SCT
MCT
Switch
FRE and PE
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRS
64 kbyte (1)
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRE and PE
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRS
FRE and PE
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FRS
1 to 64 kbyte (3)
0 to 100% of ACT
0 to 100% of ACT
(MCT SCT)
FASTbus
Stream
Notes
1. This is the amount of buffer space available for buffering frames as they are switched from one DLC
to another. For the switch, ACT is not user-configurable.
2. This is the amount of buffer space available for use as transmit queues to buffer frames transmitted
on the FASTbus.
3. This is the amount of buffer space available for use as transmit queues to buffer frames transmitted
on the network. You can configure ACT for each stream, to control the amount of buffer space
consumed by any one frame stream and prevent one severely congested frame stream from
consuming all frame stream buffer resources.
25.1-6
(400)
Figure 25.1-3 illustrates the relationship between ACT, SCT and MCT. The system
measures SCT and MCT congestion thresholds as a utilization percentage of total
buffer space available (ACT).
Figure 25.1-3: Congestion Thresholds
ACT
Severely
Congested
(Red)
SCT
Mildly
Congested
(Yellow)
Buffer Space
Consumed
MCT
Not
Congested
(Green)
Buffer Space
2689
The level of congestion (Red, Yellow or Green state) determines when the card
initiates congestion avoidance and recovery procedures.
Congestion notification parameters
On FRE and PE cards, you can configure the following frame relay parameters for a
frame relay switch, stream or FASTbus resources:
filtering/non-filtering
congestion raise time
congestion clear time
report type
Filtering debounces the transition of the switch, stream or FASTbus buffer use
between the threshold states. As shown in Figure 25.1-4, when filtering is enabled, a
smooth contiguous transition occurs between the states. When the SCT is exceeded,
the filter delays the raising of a congestion alarm by filtering out the temporary
spikes in congestion, giving a long-term congestion average. On the FRE and PE
cards, filtering can be disabled; in this case, the transition consists of sharp spikes,
allowing alarms to be raised more frequently and giving short-term statistics on
actual buffer space utilization.
(400)
25.1-7
Note
Filtering is enabled by default and cannot be disabled on the FRS card.
Enters
Red state
Leaves
Red state
ACT
Red state
SCT
Yellow state
MCT
Green state
Time
ECN signalling procedures
Frame discard using DE bit
Unfiltered or actual buffer space utilization
Filtered buffer space utilization
3873
The congestion raise time is the length of time that the resource remains in the Red
state before a congestion alarm is raised. The raise time can be configured on the FRE
and PE cards but is fixed at 5 seconds for the FRS card.
The congestion clear time is the length of time that a previously congested resource
remains out of the Red state before a congestion cleared alarm is raised. The clear
time can be configured on the FRE and PE cards but is fixed at 10 seconds for the FRS
card.
The report type is used to determine whether the node reports congestion
information as alarms or network management events (which include alarm
reports).
Congestion avoidance
The card begins congestion avoidance procedures when the switch, FASTbus
interface, or a frame stream enters the Mildly Congested (yellow) state. The card sets
FECN and BECN bits to communicate congestion information to user devices at
either end of a PVC (forward and backward with respect to the congested card).
25.1-8
(400)
Note
The FRS, FRE or PE card sets FECN and BECN bits but does not respond in any way
to frames received with FECN or BECN bits set. The card never clears the FECN or
BECN bits of a received frame. The FRS, FRE and PE cards do not support CLLMs.
When the card sets only the FECN bit in a frame, it means that the frame was
transmitted on a frame stream in the yellow or red state, telling other network
devices to avoid this frame stream.
When the card sets only the BECN bit, it means that the frame was transmitted on
an uncongested frame stream, but the frame encountered a congested frame stream
earlier in its trip. This condition tells other network devices that this frame stream is
not congested but frames sent on it in reply are likely to encounter congestion.
When the card sets both the FECN and BECN bits, it means that the frame was
transmitted by a switch in the yellow or red state, or that the frame was transmitted
on a congested frame stream and has encountered other congested resources earlier
in its trip. This condition tells other network devices that a frame sent in reply on this
frame stream will encounter heavy congestion.
For example, in Figure 25.1-5, DLC S2-456 on FRE 2 is connected to DLC S12-789.
Buffer depletion on FRE 2 has exceeded the MCT configured for frame stream S12
and it has entered the yellow state.
When FRE 1 transmits Frame A on S2, the Frame A FECN and BECN bits are zero,
because FRE 1 is experiencing neither switch congestion nor frame stream
congestion on S2. When FRE 2 receives Frame A and transmits it on S12, FRE 2 sets
the FECN bit to 1 because Frame A is transmitted on congested resource S12.
When FRE 3 transmits Frame B on S12, the Frame B FECN and BECN bits are also
zero: like FRE 1, FRE 3 is experiencing neither switch congestion nor frame stream
congestion on S12. When FRE 2 receives Frame B and transmits it on S2, FRE 2 sets
the BECN bit to 1 because this frame has encountered congested resource S12,
although it is transmitted on uncongested resource S2.
If the FRE 2 switch enters the yellow or red state, or if both frame streams S2 and S12
enter the yellow or red state, FRE 2 sets both the FECN and BECN bits in both Frame
A and B.
When a user device receives a frame with the FECN or BECN bits set, it may initiate
some form of flow control to reduce the load on the affected switch or stream.
(400)
25.1-9
Frame B
FECN
FECN
BECN
BECN
FRE 1
DLC 456
S2
Frame A
FECN
BECN
FRE 2
FRE 3
S12
Congestion
Frame A
FECN
BECN
DLC 789
4078
Congestion recovery
The card continues congestion avoidance and initiates congestion recovery
procedures when the switch, FASTbus or stream enters the Severely Congested
(Red) state.
When consumed buffer space is less than the ACT configured for the switch,
FASTbus, or stream, the card discards all frames with the DE bit set. Discarding
continues until the switch, FASTbus or stream leaves the Severely Congested state.
A user device sets the DE bit in all frames transmitted beyond its allowable
information transmission rate. The card sets the DE bit at the ingress point of a DLC
when rate enforcement is enabled (see chapter 25.8).
When consumed buffer space equals the ACT, the card stops buffering and discards
all newly arriving frames (regardless of the DE bit setting) until consumed buffer
space is less than the ACT. Figure 25.1-6 summarizes frame relay congestion
avoidance and recovery procedures.
25.1-10
(400)
RED
BS = ACT
Discard all
DE frames
Set FECN and/or
BECN bits.
BS < SCT
RED
BS >= SCT
YELLOW
BS >= MCT
BS < MCT
Normal
GREEN
BS = Buffer Space consumed
2691
(400)
25.1-11
User
mode
A
UNI
Network
mode
36120
MainStreet
node
FRE
1
Bidirectional
mode
Bidirectional
mode
NNI
NNI
Bidirectional
mode
User Network
mode
mode
8230
MainStreet
bridge
FRE
2
36120
MainStreet node
Bidirectional
mode
Public
frame relay
network
Network User
mode mode
8230
MainStreet
bridge
9564
The NNI is the interface between two network devices (such as two FRE cards). To
communicate with one another, both network devices must be configured with a
portion of a link management protocol (called the bidirectional mode) that
accommodates network device-to-network device communication. This protocol
allows network devices to monitor and relay link and PVC information across the
network. The Annex D and Annex A link management protocols support
communication across the NNI; the LMI protocol does not.
At another vendors network interface (or the public frame relay network interface),
the Bidirectional mode can be configured if the other end supports it.
Table 25.1-4 summarizes the link management protocol options available on the
FRS, FRE and PE cards.
25.1-12
(400)
End-user
Device Mode
Network
Device Mode
Communication
over the NNI
Dedicated Link
Network Device
Mode
Management
Protocol DLCI (1)
User
Network
Extended (2)
(3)
1023
ANSI T1.617
Annex D (1994)
User
Network
Bidirectional
ITU-T Q.933
Annex A (1994)
User
Network
Bidirectional
No Protocol (4)
Notes
1. When a link management protocol is selected, link management messages are transmitted and
received on this DLCI. The choice of DLCI is not user-configurable.
2. LMI Network Extended is the same as LMI Network except that asynchronous update messages are
supported.
3. The LMI protocol does not support communication over the NNI between two network devices.
4. No Protocol is selected when the frame stream terminates on a device that does not support link
management protocols.
You can configure the FRS, FRE and PE cards to accommodate both user devices and
network devices. In Figure 25.1-7, FRE 1 is configured for:
the heartbeat parameter, chapter 25.6) by sending a status enquiry message with
a report type of sequence only. The network device responds with a status
message of the same report type. This exchange ensures that both user and
network devices are operating properly and the link between them is reliable.
After a set number of status enquiry messages (defined by the status rate
parameter, chapter 25.6), the user device sends a status enquiry message with a
report type of full status update. The network device responds with a status
message of the same report type that details the status of all PVCs configured on
that stream.
Link management protocols operate across the NNI as if each side of the NNI were
configured as a user and network device in parallel.
(400)
25.1-13
Note
In accordance with ANSI T1.617a Annex D (1994) and ITU-T Q.933 (1994) standards,
the 36120 MainStreet system supports D-bit asynchronous transmission, notifying
the end-user device when a PVC is disconnected. However, when the
MainStreetXpress 46020 Network Manager reroutes a PVC, the D-bit asynchronous
transmission is suppressed and is not sent to the user-device.
The auto discovery protocol automatically configures the protocol type and
timeout (T2) value of a network device to match the protocol type and timeout
value of the user device at the other end of the frame stream.
If the protocol type of the network device is set manually, the auto discovery
protocol detects any protocol type mismatch that might occur between the
network device and the user device, and displays an error status.
If the stream goes OOS for any reason, the protocol status field on the NMTI display
is updated.
Automatic protocol type and timeout detection
The auto discovery protocol detects the protocol type of the status enquiry messages
sent by the user device to the network device. When the auto discovery option is
selected, the protocol type of the user device is detected from the first correctly
received status enquiry message. The network device is automatically configured to
match the user device and the enquiry message is processed normally.
The auto discovery protocol detects the protocol type of a remote user device that
is, LMI, Annex A or Annex D and sets the protocol mode of the local interface as
Network for Annex A or Annex D, and Network Extended for LMI.
The timeout value of the user device is calculated from the interval between the first
two correctly received status messages rounded up to the nearest five seconds,
within a range of 5 to 30 seconds. For example, a measured interval of 16 seconds is
rounded up to 20 seconds.
Mismatch detection
When a specific protocol type other than auto discovery is configured on the
network device, the auto discovery protocol enables the card to detect possible
protocol type mismatches that occur between the local and remote ends. If a
mismatch causes the stream to go OOS, an OOS alarm is raised, indicating the type
of protocol detected on the user device. In this case, neither the protocol type nor the
timeout value are configured automatically.
25.1-14
(400)
25.1.2
Configuration Overview
You configure the FRS, FRE and PE cards from two node management interfaces.
Location
CPSS
chapter 17.6
chapter 17.7
SRIM
section 25.9.1
Table 25.1-6 lists the configurable frame relay parameters according to the card type.
Note
The formats of the identifiers in the corresponding procedures are explained in
Table 16.4-1 in chapter 16.4.
Table 25.1-6: FRS, FRE and PE Card Configuration Parameters and Options
Card type
Parameter
Options
Card
Card slot
FRS
FRE
PE
FRS
Card application
SRIM
no module*
Backplane communications
dedicated
shared*
enhanced
standard*
(400)
25.1-15
Card type
Parameter
Options
1 to 30000 (5000*)
unlimited
1 to 30000 (500*)
unlimited
300 b/s
600 b/s
1200 b/s
2400 b/s
4800 b/s
9600 b/s*
19200 b/s
CPSS
VT100*
FRS
Router version 1*
Host router
Normal*
Bias against
Bias toward
FRE and PE
FASTbus CPSS
CPSS1
CPSS2
FRE and PE
Congestion filtering
enable*
disable
FRE and PE
FRE and PE
0 to 240 s (2)
FRE and PE
Report type
Alarm*
Network management events
SCT
0 to 100% (* = 80)
MCT
0 to 100% (* = 50)
FRE and PE
Congestion filtering
enable*
disable
FRE and PE
FRE and PE
0 to 240 s (2)
FRE and PE
Report type
Alarm*
Network management events
FRE and PE
36120 identifier
1 to 32767 (* = 0)
FRE and PE
Station identifier
1 to 64 (* = 0)
FRE and PE
Cable name
1 to 15 alphanumeric characters, no
spaces
FRE and PE
ACT
FRE and PE
SCT
0 to 100% (* = 80)
Switch (1)
FASTbus Interface
25.1-16
(400)
Card type
FRE and PE
Parameter
Options
MCT
0 to 100% (* = 50)
Circuit application
Stream*
Circuit
FRS, FRE and PE
Transport bandwidth
1 to 8 (8 kb/s to 64 kb/s) (* = 8)
Interface speed
0 to 8 alphanumeric characters, no
spaces
FRE and PE
Congestion filtering
enable*
disable
FRE and PE
FRE and PE
0 to 240 s (2)
FRE and PE
Report type
Alarm*
Network management events
ACT
SCT
0 to 100% (* = 80)
MCT
0 to 100% (* = 50)
FRE and PE
1* to 10
Protocol type
Frame Stream
5 to 30 s (* =10)
1 to 255 (* = 6)
5 to 30 s (* = 15) (6)
Encapsulation Circuit
FRS
Encapsulation type
FRS
FRS
ACT
1 to 64 kbytes (* = 4)
FRS
SCT
0 to 100% (* = 80)
(400)
25.1-17
Card type
FRS
Parameter
MCT
Options
0 to 100% (* = 50)
DLC Class-of-service
FRS, FRE and PE
enable
disable
CIR
Bc
Be
Notes
1. The card CPU takes the same congestion clear time and congestion raise time values as those
configured for the switch. Congestion filtering is always enabled on the CPU, regardless of the
configuration for the switch.
2. When congestion filtering is enabled, the default is 5 seconds. When congestion filtering is disabled,
the default is 0 seconds.
3. This option applies only to FRS cards equipped with a SRIM.
4. This option applies only to FRS cards.
5. The auto discovery option sets the auto discovery protocol through the protocol type parameter, even
though the auto discovery protocol is not a link management protocol. See Protocol type in
chapter 25.6.
6. This option is not configurable if the auto discovery protocol is used.
25.1-18
(400)
25.2
25.2.1
25.2.2
(400)
25.2-1
TYPE
OPTIONS
SRIM/NO_MODULE
AS_PRESENT
PACKET
FRS
FRE
PE
SK000677
Note
Use the AS_PRESENT softkey if the card is already installed in the slot.
Select the CONFIG_ALL softkey to configure all slots programmed as EMPTY to the
default configurations of the cards installed in the shelf.
25.2-2
(400)
25.3
25.3.1
25.3.2
(400)
25.3-1
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
SWITCH THRESHOLDS
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
:1500 Kbytes
:80%
:50%
:GREEN
:GREEN
8:35a
F2-SCT
F7-
F3-MCT
F8-CANCEL
F4F9-QUIT
F5F10-
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
Filtering Algorithm:
ENABLED
Clear Time:
15 mins
Report Type:
ALARMS
Raise Time:
5 secs
11-May-1997
8:35a
1-FILTERING
6-
25.3-2
2-CLEAR_TIME
7-
3-RPT_TYPE
8-CANCEL
(400)
4-RAISE_TIME
5-QUIT
50-
Description
ACT
The ACT is the total system buffer space available for switching
frames. It is not user-configurable.
SCT
MCT
Filtering Algorithm
Report Type
Notes
1. When filtering is enabled, the indication of a Congestion Status change is temporarily delayed. You
cannot disable filtering on the CPU.
2. The card CPU takes the same congestion clear time and congestion raise time values as those
configured for the switch. Congestion filtering is always enabled on the CPU, regardless of the
configuration for the switch.
Filtering
A filter is available to debounce the transition through congestion states. Filtering is
always enabled on the FRS card, and can be disabled on FRE and PE cards.
(400)
25.3-3
Options
Configure filtering as one of the following.
Enable:
Default
Enable
Clear time
The clear time is the length of time that a previously congested switch remains below
the Red state before a Switch or CPU Congestion Cleared alarm is raised. For
example, if you configure the clear time to be 20 min, the clearing alarm is raised
20 min after the switch has left the Red state. The clear time can be configured on
FRE and PE cards, and is fixed at 10 s for the FRS card.
Range
1 to 1440 min (1 min to 24 h)
Default
15 min
Raise time
The raise time is the length of time that the switch remains in the Red state before a
Switch or CPU Congested alarm is raised. For example, if you configure the raise
time to be 10 s, an alarm is raised only after the switch has remained in the Red state
for 10 s. The raise time can be configured on FRE and PE cards, and is fixed at 5 s for
the FRS card.
Range
0 to 240 seconds
Default
When filtering is disabled, the default is 0 s. When filtering is enabled, the default is
5 seconds.
25.3-4
(400)
Report type
The report type specifies whether the node reports congestion information as alarms
or network management events (which include alarm reports).
Options
Configure the report type as one of the following.
Alarms
Network management events
Default
Alarms
THRESHOLDS
MORE
CONGESTION
SCT
MCT
<sct>
<mct>
FILTERING
CLEAR_TIME
RAISE_TIME
ENABLE*/DISABLE
<ct>
<rt>
RPT_TYPE
ALARMS*
MGT_EVENTS
SK000932
where
sct is 0 to 100 (80*)
mct is 0 to 100 (50*)
ct is 1 to 1440 min (15*)
rt is 0 to 240 s (5*)
(400)
25.3-5
25.4
FASTbus Configuration
This chapter introduces the FASTbus and explains how to configure the FASTbus.
25.4.1
FASTbus topology
The FASTbus uses a dual counter-rotating ring topology based on a token-passing
access method, as shown in Figure 25.4-1. Each FASTbus interface is made of one
MAC layer and two PHY layers, port A and port B. The MAC layer is responsible for
ring operation, and the transmission and reception of frames on the FASTbus. The
dual physical layers provide an FIP with a high degree of fault tolerance by allowing
FRE and PE cards to bypass (or wrap around) the failure of an FRE or PE card or
card-to-FIP cable.
Under normal operating conditions, port A receives and port B transmits on the
primary ring (this state is referred to as THRU_A). The secondary ring remains idle
in a stand-by mode.
To communicate with each other over the FASTbus, all FRE or PE cards must belong
to the same 36120 MainStreet system. In the FASTbus configuration shown in
Figure 25.4-1, the FRE cards can be installed in the same 36120 MainStreet shelf or in
different shelves, but all the FRE cards belong to the same 36120 MainStreet system.
Figure 25.4-1: FASTbus Topology
FRE card 4
Normal
Normal
Normal
A
MAC
PHY
MAC
PHY
MAC
PHY
A
PHY
MAC
PHY
PHY
FRE card 3
PHY
FRE card 2
PHY
FRE card 1
Normal
Secondary ring
Primary ring
4074
(400)
25.4-1
FRE card 3
FRE card 4
PHY
PHY
PHY
Normal
WRAP-B
MAC
Card or cable
failure
MAC
PHY
MAC
PHY
MAC
PHY
FRE card 2
PHY
FRE card 1
PHY
WRAP-A
4075
If more than one FRE or PE card or cable fails, the FASTbus attempts to heal itself
into multiple isolated rings. For example, if FRE card 4 were to fail, FRE card 1 and
2 (and any FRE or PE cards between them) would continue to communicate.
However, these cards would be isolated from any other FRE or PE cards on the ring
(for example, between FRE card 3 and 4).
Each FRE and PE card maintains a logical map of the FASTbus ring. FASTbus
protocols ensure that the maps are kept up to date under all conditions. The map is
updated within 4 seconds of the addition of a new card to the FASTbus and within
20 seconds of the removal of a card. Wrapping occurs almost instantaneously.
Note
If an FRE or PE card is disconnected from the FASTbus by a cable failure, only
communication between this card and all other FRE and PE cards on the FASTbus is
interrupted. The card continues to switch all local DLCs (see also chapter 25.7).
25.4-2
(400)
Stations:nn
Station
------1
2
3
4
5
6
7
8
9
10
11
12
CONFIG FASTBUS
F1-PREVIOUS
F6-
P412-H1-00
Connections
----------129
12
52
52
12
11
54
11
62
52
52
Toronto:A
Alarms:1
Node Name:Slot
--------------Toronto A4
Toronto A2
Toronto A8
Calgary A2
Calgary A4
Calgary A6
Calgary A8
Charlo :A1
Bronx :A5
Queens :A3
LA
:A2
LA
:A4
11-May-1997
8:35a
Status
-----Reachable
Self
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Reachable
Non-reachable
Non-reachable
SHOW_STNS
F2-NEXT
F7-
F4F8-CANCEL
(400)
F4F9-QUIT
F5F10-
25.4-3
25.4.2
Description
Station
The identifier of the FASTbus circuit used to access the FRE or PE card with
the corresponding station identifier.
Connections
Node Name:Slot
If a remote FRE or PE card with this station identifier is installed in a node and
connected to the FASTbus, the name of the remote FRE or PE card node
(36120 MainStreet shelf in which it is installed) and the slot occupied by the
remote card appear in this field. If no FRE or PE card with this station identifier
is installed and connected to the FASTbus, Unknown appears in this field.
Status
cable name
36120 identifier
station identifier
FASTbus congestion thresholds
FASTbus congestion notification parameters
During this process, you can check FASTbus configuration and parameters using the
FASTbus status display and the FASTbus station status display.
The switch congestion notification parameters include filtering, congestion clear
time, congestion raise time and report type.
25.4-4
(400)
Stations:nn
P412-H1-00
Toronto:A
Cable Name
36120 ID
Station ID
Interface Address
Status
Congestion Status
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
Interconnection
Alarms:1
11-May-1997
8:35a
:FH3-Port8
:542
:27
:00-80-21-01-02-03
:In Service
:GREEN
:100 Kbytes
:80%
:50%
:FASThub
CONFIG FASTBUS
F1-SHOW_STNS
F6-STATION_ID
F2-THRESHOLDS
F7-MORE
F4-CABLE_NAME
F8-CANCEL
F4-SHOW_CONS
F9-QUIT
F5-36120_ID
F10-
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
Filtering Algorithm:
ENABLED
Clear Time:
15 mins
Report Type:
ALARMS
Raise Time:
5 secs
11-May-1997
8:35a
1-FILTERING
6-
2-CLEAR_TIME
7-
3-RPT_TYPE
8-CANCEL
(400)
4-RAISE_TIME
9-QUIT
50-
25.4-5
Description
Cable Name
36120 ID
Station ID
Interface Address
The MAC layer address assigned to the FRE or PE card at the time of
manufacture. Every card has a unique MAC address consisting of a 3-byte
manufacturer designator (mm-mm-mm) followed by a 3-byte MAC address
(aa-aa-aa) displayed in 12-digit hexadecimal format, hyphenated by octet
(1 octet = 8 bits).
Status
ACT
The total amount of buffer memory configured for use by the FASTbus.
SCT
MCT
Filtering Algorithm
Clear Time
Report Type
Raise Time
Notes
1. When filtering is enabled, the indication of a Congestion Status change is temporarily delayed.
Cable name
You can configure a name of up to 15 alphanumeric characters (no spaces) to identify
the cable connecting the FRE or PE card to its FIP. For example, a cable name might
be made of the FIP number and FIP port number, as in FB3-Port8 (port 8 on FIP 3).
To delete a cable name, select CABLE_NAME and press .
25.4-6
(400)
36120 ID
You must assign a unique 36120 ID in the range 0 to 32767 to each 36120 MainStreet
shelf in the network. You must configure all the FRE and PE cards connected to the
FASTbus of a given 36120 MainStreet system with the same 36120 ID number.
The 36120 ID identifies cabling faults that allow an FRE or PE card from one 36120
MainStreet shelf to be connected to the FASTbus of another 36120 MainStreet shelf.
The FASTbus supports up to 64 FRE and PE cards belonging to the same 36120
MainStreet system.
If you configure an FRE or PE card with the wrong 36120 ID or connect it to the
wrong FASTbus, the FASTbus station status display shows only the offending card.
No other FASTbus stations are visible until you configure the offending card with
the correct 36120 ID.
Caution
If the 36120 ID is changed, the system disconnects all FASTbus DLCs and FASTbus
CPSS connections.
Station ID
The station ID distinguishes one FRE or PE card from another on the FASTbus and
associates each card with a FASTbus circuit. You must assign a unique station ID in
the range 0 to 64 to each FRE or PE card in a 36120 MainStreet system. After an FRE
or PE card is configured with station ID nn, it can be reached by making DLC
cross-connections to FASTbus circuit Fnn (see chapter 25.7).
If you configure an FRE or PE card with a station ID already used by another FRE or
PE card, the FASTbus station status display shows only the incorrect card. No other
FASTbus stations are visible until you configure the incorrect card with a unique
station ID.
Caution
If the station ID is changed, the system disconnects all FASTbus DLCs and FASTbus
CPSS connections.
(400)
25.4-7
SCT
A utilization percentage of total buffer space available (ACT). The FASTbus is
considered severely congested when buffer utilization is > SCT. Enter the SCT as a
percentage of ACT (0 to 100%).
MCT
A utilization percentage of total buffer space available (ACT). The FASTbus is
considered mildly congested when buffer utilization is > MCT and SCT. Enter the
MCT as a percentage of ACT (0 to 100%). MCT must be less than or equal to SCT.
Filtering
A filter is available to debounce the transition through congestion states. Filtering
can be enabled or disabled.
Options
Configure filtering as one of the following.
Enable:
Default
Enable
Clear time
The clear time is the length of time that a previously congested FASTbus remains
below the Red state before a FASTBUS Congestion Cleared alarm is raised. For
example, if you configure the clear time to be 20 min, the clearing alarm is raised 20
min after the FASTbus has left the Red state.
Range
1 to 1440 min (1 min to 24 h)
Default
15 min
25.4-8
(400)
Raise time
The raise time is the length of time that the FASTbus remains in the Red state before
a FASTbus Congested alarm is raised. For example, if you configure the raise time
to be 10 seconds, the alarm is raised only after the FASTbus has remained in the Red
state for 10 seconds.
Range
0 to 240 seconds
Default
When filtering is disabled, the default is 0 s. When filtering is enabled, the default is
5 seconds.
Report type
The report type specifies whether the node reports congestion information as alarms
or network management events (which include alarm reports).
Options
Configure the report type as one of the following.
Alarms
Network management events
Default
Alarms
(400)
25.4-9
SHOW_STNS
THRESHOLDS
CABLE_NAME
<name>
NEXT
36120_ID
<36120_id>
STATION_ID
MORE
<station_id>
CONGESTION
PREVIOUS
FILTERING
ACT
SCT
CLEAR_TIME
RAISE_TIME
<ct>
<rt>
MCT
ENABLE*/
DISABLE
RPT_TYPE
ALARMS*
MGT_EVENTS
SK000933
where
36120_id is 0 to 32767
station_id is 0 to 64
name is a 15-character alphanumeric identifier
act is 10 to 1000 kbytes in 1 kbyte increments (100*)
sct is 0 to 100 (80*)
mct is 0 to 100 (50*)
ct is 1 to 1440 min (15*)
rt is 0 to 240 s (5*)
25.4-10
(400)
25.5
25.5.1
A local frame stream connects an FRS, FRE or PE card circuit and a primary rate
(400)
25.5-1
Total
Bandwidth
Available
Circuits
(Frame Streams)
Maximum
Bandwidth
per Frame
Stream
Single Bandwidth
FRE and PE
1984 kb/s
1 to 31 (S1 to S31)
1984 kb/s
Single Bandwidth
FRS
1984 kb/s
1 to 31 (S1 to S31)
1920 kb/s
1 to 62 (S1 to S62)
1984 kb/s
Notes
1. Double bandwidth is always available in UCS 7 and 8. It is available in all UCSs in a 3645 MainStreet
system or Switching shelf controlled 36120 MainStreet system. It is available in all UCSs when an
Expander card (16+) is installed in a 3600 MainStreet system or locally controlled 36120 MainStreet
system.
2. Total bandwidth available is based on two bundles of 1984 kb/s each.
25.5.2
configure an FRS, FRE or PE card circuit for the frame stream application
configure the transport bandwidth for the circuit
configure the interface speed for the circuit
Note
You can configure FRS, FRE and PE card circuits <sn-cc> and frame streams <Scc>
before the circuits are connected to primary rate or data interface circuits.
25.5-2
(400)
Application
The circuit application type determines how the circuit is used. To use an FRS, FRE
or PE card circuit as a frame stream, configure the application as STREAM.
To configure an FRS card circuit for frame relay encapsulation, see section 25.10.2.
To configure an FRE or PE card circuit as a direct circuit, see section 27.13.2.
Caution
When you change the FRS, FRE or PE card circuit application from STREAM to
another application, the system deletes the frame stream associated with the circuit
and loses all frame stream configuration for that frame stream (including DLCs).
Transport bandwidth
The transport bandwidth establishes the maximum allowable data rate for the frame
stream, or its access rate. You set the transport bandwidth by entering the number
of elements (1 through 8) available to the frame stream. The transport bandwidth
equals the number of elements times 8 kb/s, so you can establish an 8 kb/s frame
stream by entering 1, a 16 kb/s frame stream by entering 2 and so on. The default is
8, which specifies a 64 kb/s frame stream.
The transport bandwidth of the FRS, FRE or PE card circuit must match that of the
circuit to which it connects.
Interface speed
You can configure each FRS, FRE or PE card circuit with an interface speed between
8 and 1984 kb/s (in 8 kb/s increments), provided that the sum of the interface speeds
of all configured FRS, FRE or PE card circuits does not exceed the total bandwidth
available (see Table 25.5-1).
Note
Double bandwidth configurations (available only on the FRE and PE cards) provide
access to 62 DS0s (3968 kb/s of bandwidth). The 62 DS0s are divided into two
bundles of 31 DS0s, each providing 1984 kb/s of bandwidth.
When configuring super-rate connections, you cannot configure circuits across
bundles. The bundles are independent and cannot be combined to provide a
super-rate connection. For example, if you want to configure three super-rate
connections of 1280, 1600 and 1088 kb/s (which, combined, is equivalent to 62 DS0s),
the first connection requires 20 DS0s on the Data stream, leaving 11 DS0s. The
second connection requires 25 DS0s on the Control B stream, leaving 6 DS0s. The
third connection, which requires 17 DS0s, cannot be configured because the
remaining DS0s span both bundles.
(400)
25.5-3
If you are connecting the FRS, FRE or PE card circuit to a primary rate circuit, you
must calculate the interface speed using the following formula:
m n 8 kb/s
where
m represents the number of channels needed to carry the interface speed you want
(m = 1 to 31 for both single and double bandwidth)
n 8 kb/s represents the allowable transport bandwidth in any channel (n = 1 to 8)
If you are connecting the FRS, FRE or PE card circuit to a data circuit, you can enter
the interface speed directly as the amount of bandwidth available to the link (in
increments of 8 kb/s).
APPLI
TRANSP_BW
I/F_SPEED
STREAM*
<bw>
<speed>
SK000171
where
bw is the number of 8 kb/s elements (1 to 8*)
speed is 8 to 1920 for FRS cards and 8 to 1984 for FRE and PE cards
Note
See 25.9.3 to configure circuits for rate adaption and section 25.10.2 to configure
circuits for encapsulation.
25.5.3
25.5-4
(400)
When you disconnect an FRS, FRE or PE card circuit, the frame stream associated
with it is disassociated from the bandwidth. After disconnection, the system retains
all existing configuration information unchanged for both the circuit and the
associated frame stream. You can reconfigure or reconnect the FRS, FRE or PE card
circuit and frame stream again (to the same or a different primary rate or data circuit)
to recreate the frame stream with all its configuration intact.
You can connect an FRS, FRE or PE card circuit to any primary rate or data circuit
(for example, T1, E1, X.21, V.35, RS-232, RS-422) including super-rate circuits,
subrate circuits and transparent subrate connections to SRMs and SRSs.
You can connect an FRS, FRE or PE card circuit to another FRS, FRE or PE card circuit
in the same node, as long as the two circuits have the same configuration. After they
are connected, you can connect any DLC on any frame stream of one of the cards to
any DLC on the other card.
Note
Ensure that your primary rate service provider will guarantee temporal order before
cross-connecting an FRS, FRE or PE card circuit to a primary rate super-rate circuit.
Connections on an FRE or PE card should be made in descending bandwidth order.
For more information on subrate and super-rate circuits, see chapters 23.9 and 20.15.
To configure an FRS card for subrate switching, see chapter 25.9.
The FRS, FRE and PE cards support protection switching. See chapter 18.2.
TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000172
where
the first sn-cc is a primary rate or data circuit
the second sn-cc is an FRS, FRE or PE card circuit
(400)
25.5-5
TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000172
where
the first sn-cc is a circuit on one FRS, FRE or PE card
the second sn-cc is a circuit on another FRS, FRE or PE card in the same node
25.5-6
(400)
25.6
25.6.1
frame size
flags between frames (FRE and PE only)
the auto discovery protocol option (FRE and PE only) or the specific link
During the configuration process, you can check frame stream configuration and
parameters using the frame stream status display and the frame stream
configuration display.
The frame stream congestion notification parameters include filtering, congestion
clear time, congestion raise time and report type.
For a description of the frame stream circuit parameters that are configured from the
Control card NMTI, see chapter 25.5.
Note
You can configure FRS, FRE and PE card circuits (sn-cc) and frame streams (Scc)
before the circuits are connected to primary rate or data interface circuits.
(400)
25.6-1
Stations:5
Circuit
------A1-1
A1-2
A1-3
A1-4
A1-5
A1-6
A1-7
A1-8
A1-9
A1-10
A1-11
A1-12
A1-13
P413-H0-00
Toronto:A5
Stream
----------S1
S2
S3
S4
S5
S6
S7
S8
S9
S10
S11
S12
S13
Alarms: 21
Application
-------------STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
STREAM
Speed
--------256000 bps
64000 bps
64000 bps
64000 bps
64000 bps
56000 bps
64000 bps
64000 bps
56000 bps
64000 bps
64000 bps
64000 bps
64000 bps
24-Feb-97 9:40A
Status
------OOS-LMI
In Service
OOS-Idle
In Service
OOS-LMI
OOS-Mismatch
In Service
OOS-Disconnected
In Service
In Service
In Service
In Service
In Service
2-PREVIOUS
7-
38-CANCEL
49-QUIT
50-
Indicates
Circuit
Frame stream (Scc) or FRS, FRE or PE card circuit (cc) identifier in the range 1 to
31 (for single bandwidth) or 1 to 62 (for double bandwidth).
Stream
Application
Speed
Status
Notes
1. If the local device is set for Network mode or auto discovery protocol, and the remote device is set
for Bidirectional mode, the NMTI shows the status of the frame stream on the local end is In Service,
while the status at the remote end is OOS. The frame stream cannot come into service.
25.6-2
(400)
NEXT
PREVIOUS
SK000173
25.6.2
Stations:0
P413-H0-00
36120-A1
Frame Stream S1
Status
Using Circuit
Interface Speed
Congestion Status
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
Maximum Frame Size
Number Of Connections
Flags Between Frames
Protocol Type
Timeout
Alarms:1
24-FEB-97
1:31A
:OOS-Disconnected
:A1-1
:0 bps
:GREEN
:10 Kbytes
:80 %
:50 %
:1600 Octets
:0
:1
:Annex A Network
:15 secs
CONFIG STREAM S1
1-FRAME_SIZE
6-
2-THRESHOLDS
7-MORE
3-NUM_FLAGS
8-CANCEL
(400)
4-SHOW_CONS
9-QUIT
5-PROTOCOL
0-
25.6-3
Stations:0
P413-H0-00
36120-A1
Alarms:1
Filtering Algorithm:
ENABLED
Clear Time:
15 mins
Report Type:
ALARMS
Raise Time:
5 secs
24-Feb-97
9:31A
2-CLEAR_TIME
7-
3-RPT_TYPE
8-CANCEL
4-RAISE_TIME
9-QUIT
50-
25.6-4
Description
Frame Stream
Status
The current operating state of the frame stream. The following status values are
described in Table 25.6-1.
In Service: Active state.
OOS-Idle: Inactive state.
OOS-LMI: Inactive state.
OOS-Mismatch: Inactive state.
OOS-Disconnected: Inactive state.
Busy Out: Inactive state.
Interface Speed
Congestion
Status (1)
ACT
SCT
MCT
Maximum Frame
Size
Number of
Connections
The total number of DLCs configured on this frame stream (this includes both
local and FASTbus DLCs).
Flags Between
Frames
Protocol Type
The auto discovery protocol or the type of link management protocol configured
for the local end of this frame stream.
(400)
Field
Description
Heartbeat
This parameter is configurable only if the protocol type is LMI User, Annex D
User or Bidirectional, or Annex A User or Bidirectional. It specifies the number
of seconds between each sequence only status enquiry message.
Status Rate
This parameter is configurable only if the protocol type is LMI User, Annex D
User or Bidirectional, or Annex A User or Bidirectional. It specifies the number
of heartbeat polling intervals between full status update status enquiry
messages.
Timeout
This parameter appears and is configurable only when the link management
protocol type is LMI Network or Network Extended, Annex D Network or
Bidirectional, or Annex A Network or Bidirectional. A time interval in the range of
5 to 30 s.
Filtering
Algorithm
Clear Time
Report Type
The format in which congestion information is reported. Report Type can be set
to report alarms or network management events.
Raise Time
Notes
1. When filtering is enabled, the indication of a Congestion Status change is temporarily delayed.
(400)
25.6-5
Protocol type
This parameter specifies the auto discovery protocol or the type of link management
protocol configured for the local end of this frame stream. You can configure each
frame stream with either the auto discovery option or a specific link management
protocol. You can also disable link management protocol support.
Note
Do not select the auto discovery option when a Bidirectional or a User mode protocol
is required.
25.6-6
(400)
Options
Configure the protocol type parameter as one of the following.
Auto discovery:
After the auto discovery option is selected, the protocol type field is set to
Auto-Unknown Network and the stream status shows OOS-Idle. After the user
device protocol is discovered, the status field changes to In Service and the
protocol type field value changes to one of the following:
Auto-LMI Network (extended)
Auto-Annex D Network
Auto-Annex A Network
LMI:
The Local Management Interface protocol defined by the Frame Relay Forum
supports User, Network and Network Extended mode for operation over the
User-Network Interface only.
Annex D:
The link management protocol defined by ANSI T1.617 Annex D supports User
and Network modes for operation over the User-Network Interface and
Bidirectional mode for operation over the Network-Network Interface.
Annex A:
The link management protocol defined by ITU-T Q.933 Annex A supports User
and Network modes for operation over the User-Network Interface and
Bidirectional mode for operation over the Network-Network Interface.
No Protocol:
The No Protocol option disables protocol support, and protocol information from
the remote user (or network) device is ignored.
Default
Annex A Network
Heartbeat
The heartbeat polling interval specifies the number of seconds between each
sequence-only status enquiry message. The user device sends a status enquiry
message to the attached network device every heartbeat polling interval and expects
a status message in reply.
This parameter appears only when the link management protocol type is LMI User,
Annex D User or Bidirectional, or Annex A User or Bidirectional.
When the auto discovery protocol is configured and the streams are connected, the
network side monitors the user-side heartbeat value in order to calculate the
network timeout value. This calculation is made whenever the frame stream is OOS,
including the initial startup (which occurs at the time when the streams are
connected or the protocol type is changed). After the initial calculation, if the
network stream goes OOS, the heartbeat value is recalculated. The network stream
can go OOS if the heartbeat value on the user side is increased above the network
timeout value, causing timeout errors.
(400)
25.6-7
Range
5 to 30 seconds in 5 second increments
Default
10 seconds
Status rate
The status message rate specifies the number of heartbeat polling intervals between
full status update status enquiry messages. A user device sends a full status update
status enquiry message at this number of intervals and expects a full status update
in reply from the attached network device.
This parameter appears only when the link management protocol type is LMI User,
Annex D User or Bidirectional, or Annex A User or Bidirectional.
Range
1 to 255
Default
6
Timeout
The status enquiry message timeout specifies the timeout period for the receipt of a
status enquiry message at the network side. The network device expects either a
sequence-only or a full status update status enquiry message from the attached user
device within this interval.
This parameter appears only when the link management protocol type is LMI
Network or Network Extended, Annex D Network or Bidirectional, or Annex A
Network or Bidirectional.
If the auto discovery protocol is configured on the network device, the timeout
parameter is not user configurable. The timeout value is initially set to 30 seconds
and then calculated automatically by the auto discovery protocol, according to the
user device heartbeat polling interval.
The timeout value is not recalculated automatically when the user-side heartbeat
value is changed. It is recalculated only if the change causes the frame stream to go
out of service.
25.6-8
(400)
Range
5 to 30 seconds in 1 second increments
Default
15 seconds
Filtering
A filter is available to debounce the transition through congestion states. Filtering is
always enabled on the FRS card, and can be disabled on FRE and PE cards.
Options
Configure filtering as one of the following.
Enable:
Default
Enable
Clear time
The clear time is the length of time that a previously congested frame stream remains
below the Red state before a Stream Congestion Clear alarm is raised. For example,
if you configure the clear time to be 20 min, the clearing alarm is raised 20 min after
the frame stream has left the Red state. The clear time can be configured on FRE and
PE cards, and is fixed at 10 seconds for the FRS card.
Range
1 to 1440 min (1 min to 24 h)
Default
15 min
(400)
25.6-9
Raise time
The raise time is the length of time that the frame stream remains in the Red state
before a Stream Congested alarm is raised. For example, if you configure the raise
time to be 10 s, an alarm is raised only after the frame stream has remained in the
Red state for 10 s. The raise time can be configured on FRE and PE cards, and is fixed
at 5 s for the FRS card.
Range
0 to 240 seconds
Default
When filtering is disabled, the default is 0 seconds. When filtering is enabled, the
default is 5 seconds.
Report type
The report type specifies whether the node reports congestion information as alarms
or network management events (which include alarm reports).
Options
Configure the report type as one of the following.
Alarms
Network management events
Default
Alarms
25.6-10
(400)
<flags>
ACT
SCT
CONGESTION
MCT
TYPE
ENABLE*/
DISABLE
HEARTBEAT
<interval>
LMI
USER
MORE
STATUS_RATE TIME_OUT
<rate>
NOPROTOCOL ANNEX_D
NETWORK
NETEXT
<ct>
RPT_TYPE
<rt>
ALARMS*
MGT_EVENTS
<time>
ANNEX_A
AUTO
where
size is the number of octets (16 to 4472, 1600*)
flags is the number of inter-frame flags (1 to 10, 1*), not configurable on FRS cards
act is 1 to 64 kbytes on the FRS and 1 to 1500 kbytes on the FRE and PE in 1 kbyte increments (10*)
sct is 0 to 100 (80*)
mct is 0 to 100 (50*)
interval is 5 to 30 seconds in 5 second increments (10*)
rate is 1 to 255 (6*)
time is 5 to 30 seconds in 1 second increments (15*)
ct is 1 to 1440 min (15*)
rt is 0 to 240 seconds (5*)
(400)
25.6-11
25.7
25.7.1
local DLCs
card-to-card DLCs across the backplane
card-to-card DLCs over the FASTbus
You configure a local DLC between two frame stream-DLCIs on the same card,
using DLCIs in the range 16 to 1007. DLCIs must be unique on each frame stream
(the same DLCI can be used on different frame streams). You can connect a DLCI to
only one other DLCI at a time; point-to-multipoint circuits or multicast circuits are
not supported.
You configure a card-to-card DLC between a frame stream-DLCI on one card and a
frame stream-DLCI on another card in the same node over an intermediate frame
stream created between the two cards.
For frame stream connections across the backplane, the intermediate frame stream
uses the 64 Mb/s circuit-switched backplane bus. You configure card-to-card DLCs
using DLCIs in the range 16 to 1007, as for local DLCs.
For FRE and PE cards on a 36120 MainStreet system, the intermediate frame stream
uses the 100 Mb/s packet-switched FASTbus and the connections are called
FASTbus DLCs. You configure FASTbus DLCs using DLCIs in the range 2000 to
3983. You can use a DLCI in this range to identify only a single connection between
two frame stream-DLCIs (multicast circuits are not supported).
Table 25.7-1 lists the maximum number of DLCs and DLCIs available on the FRS,
FRE and PE cards. You can configure class-of-service parameters (CIR, Bc and Be)
for each DLC (see chapter 25.8).
(400)
25.7-1
Total DLCs
DLCI Range
FRS card
1024
16 to 1007
FRE or PE card
1984
16 to 1007 and
2000 to 3983
Frame Stream
992
16 to 1007
FASTbus interface
on any FRE or PE
card
1984
2000 to 3983
Note
You must configure the 36120 ID and station ID on FRE and PE cards before you can
configure DLCs over the FASTbus (see chapter 25.4).
25.7.2
CONFIG
Cards:5
NewYork:A5
Alarms: 21
24-Feb-97
From
Status
Connected To
Status
2-26
2-27
2-100
2-128
2-344
2-472
Loopback
Active
Active
Active
Busy Out
Active
3-128
4-512
5-1000
12-14
22-54
8-472
Loopback
Active
Active
Active
Busy Out
Active
STREAM
1-PREVIOUS
6-
25.7-2
P413-H0-00
S2
9:40A
SHOW_CONNS
2-NEXT
7-
3-START_DLCI
8-CANCEL
(400)
49-QUIT
50
Cards: 4
P413-H0-00
NewYork:A5
Alarms: 21
24-Feb-93
From
Status
Connected To
Status
F5-2006
F5-2700
F5-2477
F5-3600
F5-3784
F5-3878
Loopback
Active
Busy Out
Active
Active
Active
S3-128
S4-512
S5-1000
S21-14
S9-54
S31-472
Loopback
Out Of Service
Busy Out
Active
Active
Active
CONFIG
9:40A
FASTBUS SHOW_CONNS F5
1-PREVIOUS
6-
2-NEXT
7-
3-START_DLCI
8-CANCEL
49-QUIT
50-
Indicates
From
Connected To
Status
(400)
25.7-3
If there are more than 14 DLCs configured, the NEXT and PREVIOUS softkeys move
forward and backward through the list, one screen at a time.
CONFIG STREAM <Scc> SHOW_CONNS
START_DLCI
NEXT
PREVIOUS
<dlci>
SK000175
START_DLCI
NEXT
PREVIOUS
<dlci>
SK000176
where
station is the station identifier (1 to 64, excluding the FRE or PE card running the NMTI session)
dlci is 2000 to 3983
25.7.3
local DLCs
card-to-card DLCs across the backplane
card-to-card DLCs over the FASTbus
25.7-4
(400)
36120 ID 17
36120 ID 17
S9
S8
S12
FASTbus
FRE
23
36120
MainStreet node
FRE
42
36120
MainStreet node
S9-123 X S8-201
4069
Example
Invalid:
S1-876 x S2-42
S1-876 x S3-19
Valid:
S1-876 x S2-876
Invalid:
S1-876 x S1-876
Valid:
S1-456 x S1-789
Notes
1. Unless a DLC loopback is initiated. See Maintenance.
(400)
25.7-5
TO_DLC
DISCONNECT
<Scc-dlci>
SK000177
where
Scc is a frame stream identifier (1 to 31 for FRS cards, 1 to 62 for FRE and PE cards)
dlci is 16 to 1007
S12-147
S12
S13
FRS 1
S12-147 X S3-452
FRE 2
S5-452 X S18-236
S3
S5
S17
S18-236
S18
5448
25.7-6
(400)
The same DLCI (452) must be used at both ends of the intermediate connection to
uniquely identify this particular connection between the two cards. The same DLCI
cannot be used in any other connections between these two cards, but it can be used
in connections between other FRS and FRE cards; for example, between FRS 1 and
any other FRS or FRE card except FRE 2.
The same configuration rules apply to card-to-card DLCs across the backplane as
apply to local DLCs (see Table 25.7-3).
TO_DLC
DISCONNECT
<Scc-dlci2>
SK000178
where
Scc-dlci1 is the frame stream and DLCI (16 to 1007) for the first card
Scc-dlci2 is the frame stream and DLCI (16 to 1007) for the frame stream between cards
2.
TO_DLC
DISCONNECT
<Scc-dlci3>
SK000179
where
Scc-dlci2 is the frame stream and DLCI (16 to 1007) for the frame stream between cards
Scc-dlci3 is the frame stream and DLCI (16 to 1007) for the second card
(400)
25.7-7
36120 ID 17
36120 ID 17
S9
S7
S12
FASTbus
FRE
23
PE
42
36120
MainStreet node
36120
MainStreet node
S9-345 X F42-2013
F23-2013 X S12-124
S9-345 X S7-678
4070
25.7-8
(400)
Example
Invalid:
Valid:
Invalid:
Invalid:
F2-2876 x F2-2876
Invalid:
F1-456 x F2-789
Invalid:
F2-2876 x S2-42
Notes
1. Unless a DLC loopback is initiated. See Maintenance.
Note
For the configuration and maintenance procedures, a FASTbus DLC connection can
be identified by either its frame-stream-DLCI (S9-345 in Figure 25.7-5) or the
FASTbus circuit-DLCI it is connected to (F42-2013 in Figure 25.7-5).
(400)
25.7-9
TO_DLC
DISCONNECT
<Fnn-dlci2>
SK000180
where
Scc-dlci1 is the frame stream and DLCI (16 to 1007) identifier on this FRE or PE card
Fnn-dlci2 is the FASTbus circuit (nn is the station id of the FRE or PE card you want to connect to)
and the connecting DLCI (2000 to 3983) identifier for the frame stream between cards
2.
TO_DLC
DISCONNECT
<Scc-dlci3>
SK000181
where
Fnn-dlci2 is the FASTbus circuit (nn is the station id of the FRE or PE card you are connecting to)
and the connecting DLCI (2000 to 3983) identifier for the frame stream between cards
Scc-dlci3 is the frame stream and DLCI (16 to 1007) identifier on this FRE or PE card
For example, the connections in Figure 25.7-5 are:
CONFIG CONNECT S9-345 TO_DLC F42-2013
CONFIG CONNECT F23-2013 TO_DLC S12-124
25.7-10
(400)
25.8
Class-of-service Parameters
This chapter explains how to configure the class-of-service parameters and enable or
disable of class-of-service enforcement.
25.8.1
Card-to-card DLCs
In Figure 25.8-1, a PVC is created by a card-to-card configuration in which S12-147
on FRS 1 is cross-connected to S18-236 on FRE 2. This PVC is composed of two DLC
cross-connections.
The first DLC cross-connection in this PVC is S12-147 X S3-452 on FRS 1. The second
DLC cross-connection in this PVC is S5-452 X S18-236 on FRE 2.
Class-of-service parameters are independently configured for each
cross-connection. Traffic entering or exiting the network at S12-147 is subject to the
class-of-service you configure for the DLC S12-147 X S3-452.
Class-of-service configuration can be applied to traffic entering or exiting the
intermediate frame stream between the two cards, at S12-147 X S3-452. If
class-of-service is enabled on the DLC, all data that crosses this connection is subject
to the class-of-service that you configure at this connection, regardless of the
class-of-service configured on previous or later cross-connections. If you want a
consistent class-of-service enforcement across the entire PVC, you must configure
the same parameter values at each DLC cross-connection.
For example, if you configure S12-147 X S3-452 with a CIR of 128 kb/s, and S5-452 X
S18-234 with a CIR of 32 kb/s, the prevailing CIR over that PVC will be 32 kb/s
when class-of-service is enabled on each DLC.
(400)
25.8-1
After you configure class-of-service parameters, you can enable or disable the
enforcement of these parameters independently at each DLC for each direction of
traffic.
Figure 25.8-1: Card-to-card Class-of-service Configuration Example
S12-147
S12
S13
FRS 1
S12-147 X S3-452
FRE 2
S5-452 X S18-236
S3
S5
S17
S18-236
S18
5448
36120 ID 17
36120 ID 17
S9
S7
S12
FASTbus
FRE
23
PE
42
36120
MainStreet node
36120
MainStreet node
S9-345 X F42-2013
F23-2013 X S12-124
S9-345 X S7-678
4070
After you configure class-of-service parameters, you can enable or disable the
enforcement of these parameters independently at each frame stream-DLCI
endpoint (S9-345 and S12-124 in Figure 25.8-2) exiting the FASTbus.
25.8-2
(400)
25.8.2
Class-of-service display
Figure 25.8-3 shows an example class-of-service configuration display. Table 25.8-1
summarizes the fields on this display.
Figure 25.8-3: Class-of-Service Configuration Display
FRE
Stations:nn
P412-H1-00
Toronto:A
ENDPOINT 1: S12-147
S3-452
Alarms:1
8:35a
Connected To
ENDPOINT 2:
FROM_1->2
FROM_2->1
DISABLED
DISABLED
11-May-1997
:512000 bps
:512000 bits
:1984000 bits
:64000 bps
:64000 bits
:1984000 bits
1-CIR
6-
2-BE
7-
3-BC
8-CANCEL
(400)
4-ENABLE
9-QUIT
5-DISABLE
0-
25.8-3
You select FROM_1->2 to configure the CIR, Be and Bc for data originating at
ENDPOINT 1 (S12-147) being sent to ENDPOINT 2 (S3-452). You select FROM_2->1
to configure the CIR, Be and Bc for data flowing in the opposite direction through
that DLC.
Table 25.8-1: Class-of-Service Configuration Fields
Field
Indicates
ENDPOINT 1
ENDPOINT 2
FROM_1->2
FROM_2->1
Committed Information
Rate (CIR)
The CIR configured for this DLC, in the range 0 to 1984000 b/s.
25.8-4
This defines the CIR for the DLC. Under normal conditions, the DLC is
guaranteed this throughput.
A DLC may transmit a burst in excess of its CIR provided the total number of bits
transmitted over a time interval of Tc seconds is not more than Be + Bc. The DE
bit is set in frames transmitted in this range.
If a DLC attempts to transmit a burst in excess of its CIR, where the total number
of bits transmitted over a time interval of Tc seconds is more than Be + Bc, the
card discards all frames queued for transmission in this range.
(400)
Note
On FRE and PE cards, class-of-service enforcement can be enabled only for a frame
stream-DLCI. If either DLCI endpoint corresponds to a FASTbus circuit-DLCI, the
system does not allow the selection and issues a warning message.
Disabled
This option specifies that class-of-service parameters remain as configured but are
never enforced. The DE bit is never set in any frame and frames are never discarded
regardless of how much a DLC attempts to transmit.
Caution
Disabling class-of-service enforcement may lead to serious network congestion.
(400)
25.8-5
FROM_1->2
CIR
BC
BE
<cir>
<bc>
<be>
FROM_1->2
ENABLE
DISABLE
SK000182
where
Scc-dlci is the frame stream (1 to 31 or 1 to 62) and DLCI (16 to 1007)
Fnn-dlci is the FASTbus circuit (nn is the station identifier) and dlci (2000 to 3983)
cir is 0 to 1984000 b/s
bc and be are 0 to 1984000 bits
Note
The FASTbus circuit-DLCI (Fnn-dlci) merely identifies a FASTbus DLC. The
class-of-service parameters configured apply only to the FRE or PE Card frame
stream-DLCI (Scc-dlci) endpoints even if you use the FASTbus circuit-DLCI.
25.8-6
(400)
25.9
25.9.1
DDS (kb/s)
X.50 (kb/s)
DS0-A
DS0-B
DIV_2
DIV_3/DIV_5 (1)
1.2
2.4
2.4
2.4
2.4
2.4
4.8
4.8
4.8
4.8
4.8
9.6
9.6
9.6
9.6
9.6
19.2
19.2
19.2
14.4
56
48 (2)
48 (2)
19.2
38.4
Notes
1. X.50 Div. 2, X.50 Div. 3 and HCM are X.50 Div. 5-compliant and can do random framing at all speed
rates.
2. At 48 kb/s, X.50 Div. 2 and X.50 Div. 3 are called X.50 bis.
(400)
25.9-1
Connections
SRIM aggregate circuits can be connected to:
2B1Q and DNIC Line cards and the OCU-DP channel unit
all aggregate primary rate cards
all DCCs and the 64 kb/s Codirectional card
SRMs or MJUs on DSP cards
SRSs on DSP4 cards
Options
Restrictions
Slot
Module Type
No module
SRIM
X.50 or HCM
DDS or HCM
Speed Range
1.2 to 56 kb/s
A-bit Handling
Non-standard
Standard
Loopback Detection
On
Off
SRIM mode:
DDS or HCM
X.50 or HCM
Stream
Rate adaption
Encapsulation
Rate Adaption
HCM
DDS
X.50
Circuit
25.9-2
(400)
Parameter
Options
Restrictions
Interface Speed
2400 b/s
4800 b/s
9600 b/s
19200 b/s
56000 b/s
DDS Method
1 to 20 at 2400 b/s
1 to 10 at 4800 b/s
1 to 5 at 9600 b/s
2 or 4 at 19200 b/s
1 at 56000 b/s (DS-0A only)
B7* to B0
Transport Bandwidth
1 to 8 (x 8 kb/s)
X.50 Method
Div. 2
Div. 3
Data Position
F0-B7 to F9-B0
2400 b/s
4800 b/s
9600 b/s
19200 b/s
56000 b/s
2400 b/s
4800 b/s
9600 b/s
19200 b/s
2400 b/s
4800 b/s
9600 b/s
19200 b/s
X.50 Bis
48000 b/s
Rate Adaption
DDS
HCM
X.50
Signalling
On
Off
Subrate Stream
(400)
25.9-3
Parameter
Options
Restrictions
at 2.4 kb/s:
1 5 9 13 17 21 25 29 33 37 41
45 49 53 57 61 65 69 73 77
at 4.8 kb/s:
1 9 17 25 33 41 49 57 65 73
at 9.6 kb/s:
17 33 49 65
at 19.2 kb/s:
1 17 33 49
at 2.4 kb/s:
1 to 20
at 4.8 kb/s:
1 3 5 7 9 11 13 15 17 19
at 9.6 kb/s:
1 5 9 13 17
at 19.2 kb/s:
1 5 9 13
48 kb/s
1
Transport Bandwidth
1 to 8 (x 8 kb/s)
Transport Position
B7 to B0
Notes
1. There are no restrictions when transport bandwidth is configured at the subrate stream level.
25.9.2
Rate adaption
To select the rate adaption mode for the card, choose X50_OR_HCM or
DDS_OR_HCM.
25.9-4
(400)
Speed range
Table 25.9-1 lists the interface speeds available for each rate adaption method. For
X50_OR_HCM rate adaption mode, you can use the SPEED_RANG softkey to select
an interface speed range of:
For DDS_OR_HCM rate adaption mode, you can select a range of:
Loopback detection
The SRIM does alternating loopback detection on DDS and latching loopback
detection on X.50 subrate streams. The SRIM cannot initiate loopbacks, but can
respond to loopback requests from the network. To enable loopback detection, select
LP_DET_ON; to disable it, select LP_DET_OFF.
A-bit handling
In X50_OR_HCM rate adaption mode, you can configure the card for standard or
non-standard A-bit handling by selecting A_STD_ON or A_STD_OFF.
SRIM/NO_MODULE
X50_OR_HCM/
DDS_OR_HCM
1.2/4.8_K
SPEED_RANG
2.4/1.9_K
FUNCTION
LP_DET_ON/
LP_DET_OFF
4.8/38.4_K
48_K
A_STD_ON/
A_STD_OFF
56_K
SK000183
(400)
25.9-5
25.9.3
DDS
X.50
Parameter
Rate adaption method
DDS method
Interface speed
Subframe position
Transport bandwidth
Chapter 23.6 describes the rate adaption methods and their parameters. Table 25.9-4
lists the valid DDS DS0-B subframe positions for each interface speed.
Table 25.9-4: DDS Subframe Positions
25.9-6
2400
1 to 20
4800
1 to 10
9600
1 to 5
19200
2 to 4
56000
(400)
HCM
DDS
X.50
DIV_2
DIV_3
SK000184
TRANSP_BW
F_POSITION
<bw>
<Bn>
SK000185
where
bw is the number of 8 kb/s elements (1 to 8)
Bn is B7 to B0
METHOD
DS-0A
POSITION
I/F_SPEED
<pos>
<speed>
DS-0B_9.6
DS-0B_4.8
DS-0B_2.4
SK000186
where
pos is a valid subframe position for the selected interface speed (see Table 25.9-4)
speed is 2400, 4800, 9600, 19200 or 56000
Note
The POSITION softkey applies only to DS0-B circuits.
(400)
25.9-7
25.9.4
DDS
X.50
Parameter
Interface speed
Subframe position
Signalling option
Data position
Transport bandwidth
Chapter 23.6 describes the rate adaption methods and their parameters. Table 25.9-6
lists the valid interface speeds for each rate adaption method, and Table 25.9-7 lists
valid DDS and X.50 subframe positions.
Table 25.9-6: Interface Speeds
HCM (b/s)
25.9-8
DDS (b/s)
X.50 (b/s)
DS0-A
DS0-B
DIV_2
DIV_3/DIV_5
1200
2400
2400
2400
2400
2400
4800
4800
4800
4800
4800
9600
9600
9600
9600
9600
14400
19200
19200
19200
19200
38400
48000
48000
56000
(400)
DDS Subframe
Position Range
2400
1 to 20
1 5 9 13
17 21 25 29
33 37 41 45
49 53 57 61
65 69 73 77
1 to 20
4800
1 to 10
1 9 17 25
33 41 49 57
65 73
1357
9 11 13 15
17 19
9600
1 to 5
1 17 33 49
65
1 5 9 13
17
19200
2 to 4
48000
56000
HCM
DDS
X..50
DIV_2
DIV_3
SK000187
TRANSP_BW
TRANSP_POS
I/F_SPEED
<bw>
<Bn>
<speed>
SIG_ON/
SIG_OFF
DATA_POSN
<Ff-Bb>
SK000188
where
bw is the number of 8 kb/s elements (1 to 8)
Bn is B7 to B0
speed is a valid speed from Table 25.9-6
Ff-Bb is F0 to F9 and B7 to B0
(400)
25.9-9
I/F_SPEED
POSITION
<speed>
<position>
SK000189
where
speed is a valid speed from Table 25.9-6
position is a valid subframe position from Table 25.9-7
25.9.5
the combined bandwidth of the subrate streams does not exceed the bandwidth
of the aggregate circuit
Note
See section 25.10.5 to connect subrate encapsulation circuits.
25.9-10
(400)
TO_CIRCUIT
DISCONNECT
<sn-cc>
SK000190
where
sn-SRcc is the subrate stream identifier
sn-cc is the aggregate circuit identifier
Figure 25.9-1 shows the NMTI screen for subrate multiplexing two HCM streams on
an aggregate circuit.
Figure 25.9-1: Subrate Multiplexing HCM Streams
3600 MainStreet
1117-H1-00
F0
F1
F2
F3
F4
F5
F6
F7
F8
F9
B7
F
b
b
-
B6
a
b
b
-
B5
a
b
-
B4
a
b
-
B3
a
b
-
B2
b
b
-
Toronto:A
Alarms:1
NAME:
B1
b
b
-
B0
b
b
-
11-May-1997
8:35a
A1-SR01;
b =
A1-SR02;
1-SHOW_GROUP
6-
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
50-
Figure 25.9-2 shows the NMTI screen for subrate multiplexing two DDS streams on
an aggregate circuit.
(400)
25.9-11
1117-H1-00
Toronto:A
NAME:
Alarms:1
11-May-1997
8:35a
A1-SR04;
2 =
A1-SR03;
1-SHOW_GROUP
6-PROTECTING
25.9-12
27-
3-TO_CIRCUIT
8-CANCEL
(400)
49-QUIT
5-PROT_BY
0-
25.10
25.10.1
LAP
LAPB
LAPD
LAPM
SDLC
DSP
Appletalk
SS7
proprietary HDLC protocols, including CPSS
On the FRS card, encapsulation circuits terminate subrate or super-rate HDLC data
streams. When the FRS card receives frames from the HDLC devices, the frame
feeder subsystem encapsulates the HDLC frames in frame relay frames and inserts
the DLCI for the appropriate PVC. The switch routes the frame relay frames to their
destination over the frame relay network.
The destination device may be another FRS card, or customer-premise equipment
that supports Annex G or RFC 1490 encapsulation methods. The destination device
extracts, or decapsulates, the HDLC frames, and delivers them to the remote HDLC
devices.
The FRS card supports encapsulation and decapsulation according to the following
methods and standards:
Transparent HDLC
Frame Relay Services
(400)
25.10-1
FRS cards must be equipped with a SRIM to provide encapsulation for subrate
HDLC data streams using HCM, DDS or X.50 rate adaption.
Figure 25.10-1 shows an example of using encapsulation to provide LAPB access to
a 36120 MainStreet X.25 network over frame relay.
Figure 25.10-1: LAPB Encapsulation Example
X.25
X.25
FRE
or
FRE
PECard
card
FRS card
LAPB
DTE
Annex G
or
RFC 1490
Annex G
or
RFC 1490
Frame relay
Encapsulation
Encapsulation
X.25
network
Decapsulation
LAPB
DTE
Annex G
or
RFC 1490
Decapsulation
Frame relay
Annex G
or
RFC 1490
PAD/FRAD
7550
FRS card
HDLC
FRS card
Frame
relay
network
Transparent
HDLC
Transparent
HDLC
HDLC
HDLC device
HDLC device
8036
25.10-2
(400)
When you configure an FRS circuit for LAPB Annex G encapsulation, you must
specify the maximum size of the X.25 packets that use the circuit. The size of the
LAPB frames is derived using the algorithms described in Appendix II of
Recommendation X.25; for packet sizes greater than 128 bytes, 9-bytes are added to
the X.25 packet size. The Annex G encapsulation method adds a 2-byte header. The
switch calculates the resulting frame relay T1.618 frame size as shown in
Table 25.10-1.
Table 25.10-1: Packet and Frame Sizes for Annex G
X.25 Packet Size
266
256
267
512
523
1024
1035
2048
2059
4096
4107
0
EA
Data Link
Connection
Identifier
(DLCI)
LAPB frame
T1.618 frame
Check sequence
Check sequence
EA
Flag
1 1
Flag
1 1
DE
BECN
LAPB frame
FECN
C/R
Annex G encapsulation
of a LAPB frame
Frame relay
information
field
7968
(400)
25.10-3
When you configure an FRS circuit for LAPB RFC 1490 encapsulation, you must
specify the maximum size of the X.25 packets that use the circuit. The LAPB frame
size is derived according to Appendix II of Recommendation X.25; for packet sizes
greater than 128 bytes, 9-bytes are added to the X.25 packet size. The RFC 1490
encapsulation method adds an 8-byte header. The switch calculates the resulting
frame relay T1.618 frame size as shown in Table 25.10-2.
Table 25.10-2: Packet and Frame Sizes for RFC 1490
X.25 Packet Size
272
256
273
512
529
1024
1041
2048
2065
4096
4113
Figure 25.10-4 shows the frame format using LAPB as the encapsulated protocol.
Figure 25.10-4: RFC 1490 Encapsulation of LAPB Frames
0
EA
Data Link
Connection
Identifier
(DLCI)
0
EA
Flag
1 1
DE
BECN
FECN
C/R
Control 0 x 03
NLPID 0 x 08
0 x 46
LAPB frame
Flag
1 1
0 x 81
0 x 66
0 x 80
LAPB Frame
T1.618 Frame
Check Sequence
Check Sequence
Layer 2
protocol
ID
Layer 3
protocol
ID
Frame relay
information
field
7967
25.10-4
(400)
25.10.2
APPLI
TRANSP_BW
I/F_SPEED
FR_ENCAP
<bandwidth>
<speed>
SK000191
where
bandwidth is n 8 kb/s, where n is 1 to 8
speed is 8 to1984 kb/s in multiples of 8, and must match the interface speed set for the primary rate or data
interface circuit
(400)
25.10-5
Note
Configure the application as FR_ENCAP before configuring the interface speed or
transport bandwidth. The interface speed for the frame relay encapsulation circuit
must be configured to match the speed of the primary rate or data interface circuit
to which it connects.
RATE_ADAPT
APPLI
(see note)
FR_ENCAP
SK000192
where sn-SRcc is the slot number and subrate circuit number on the FRS card
25.10.3
25.10-6
(400)
P114-F0-00
NMTI Shelves
Alarms:4
ENCAP_CCT SR1
Status
Using Circuit
Interface Speed
Congestion Status
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
Encapsulated Protocol Max Frame Size
Required Frame Relay Frame Size
Connected To
Encapsulation type
19-AUG-94
8:35A
:OOS-Disconnected
:A1-2
:9600 bps
:GREEN
:4 Kbytes
:80%
:50%
:512 Octets
:529 Octets
:S1-100
:LAPB RFC 1490
F2-THRESHOLDS
F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
Description
Status
Using Circuit
Shows the actual FRS circuit selected, or, if a subrate FRS circuit is selected, the
rate adapted FRS circuit to which the subrate encapsulation circuit is connected.
Interface Speed
Congestion Status
Required Frame
Relay Frame Size
The size of the frame relay T1.618 frame after the source protocol frame is
encapsulated. This is a readable value that is calculated based on the value of the
Encapsulated Protocol Max Frame Size parameter. The value of this field must
be less than the Maximum Frame Size parameter for the frame stream to which
this circuit is connected.
Connected to
(400)
25.10-7
Options
Description
Absolute Congestion
Threshold (ACT)
1 64 kbytes in
1-kbyte increments
(* = 4)
1 100% (* = 80%)
1 100% (* = 50%)
Encapsulated Protocol
Maximum Frame Size
Encapsulation Type
25.10.4
congestion thresholds
frame size
number of flags between frames
encapsulation type
The parameters and allowable values are the same for subrate and super-rate
circuits.
25.10-8
(400)
Encapsulation type
This parameter specifies the encapsulation method, either LAPB RFC 1490, LAPB
Annex G or Transparent HDLC. When you select LAPB Annex G or Transparent
HDLC, the switch adds a 2-byte header to each frame being encapsulated. When you
select LAPB RFC 1490, the switch adds an 8-byte multiprotocol header to each LAPB
frame being encapsulated.
For encapsulating X.25 packets for transmission to a PE or X.25 FRE card,
Newbridge recommends that you select LAPB Annex G.
(400)
25.10-9
FRAME_SIZE
ENCAP_TYPE
THRESHOLDS
X.25_PKT_SZ
T_HDLC
<pkt_size>
<frame_size>
ACT
SCT
MCT
<act>
<sct>
<mct>
SK000193
where
pkt_size is the number of octets (16, 32, 64, 128, 256, 512*, 1024, 2048 or 4096)
frame_size is the number of octets (16 to 4472)
act is 1 to 64 kbytes (4*)
sct is 1 to 100% (80*)
mct is 1 to 100% (50*)
25.10.5
25.10-10
(400)
FRS card
Frame
relay
network
m x n x 8 kb/s
1
HDLC device
= Transport bandwidth (1 to 8)
8037
1.
From the Control card NMTI, connect the super-rate encapsulation circuit to a
data or primary rate interface circuit:
CONFIG CONNECT <sn-ccl> TO_CIRCUIT <sn-cc2> PROCEED
where
sn-cc1 is the FRS slot number and encapsulation circuit number
sn-cc2 is the data or primary rate card slot number and circuit number
2.
From the FRS NMTI, connect the super-rate encapsulation circuit to a frame
stream-DLCI:
CONFIG CONNECT <cc> or <Scc-dlci> TO <cc> or <Scc-dlci>
where
cc is the encapsulation circuit
Scc-dlci is the frame stream circuit (1 to 31) and a DLCI (16 to 1007)
Note
See section 25.8.2 for information about setting the class-of-service parameters for
DLCs.
(400)
25.10-11
FRS card
Frame
relay
network
3
1.2 to 56 kb/s
1
2
HDLC device
1.
From the Control card NMTI, connect the subrate encapsulation circuit to a rate
adaption circuit:
CONFIG CONNECT <sn-SRcc> TO_CIRCUIT <sn-cc> PROCEED
where
sn-SRcc is the FRS slot number and subrate encapsulation circuit number
sn-cc is the FRS slot number and rate adaption circuit number
2.
From the Control card NMTI, connect the rate adaption circuit to a data
interface circuit:
CONFIG CONNECT <sn-ccl> TO_CIRCUIT <sn-cc2> PROCEED
where
sn-cc1 is the FRS slot number and rate adaption circuit number
sn-cc2 is the data interface slot and circuit number
3.
From the FRS NMTI, connect the subrate encapsulation circuit to a frame
stream-DLCI:
CONFIG CONNECT <SRcc> TO <Scc-dlci>
where
SRcc is the subrate encapsulation circuit
Scc-dlci is the frame stream circuit (1 to 31) and a DLCI (16 to 1007)
25.10-12
(400)
Note
See section 25.8.2 for information about setting the class-of-service parameters for
DLCs.
(400)
25.10-13
25.11
25.11.1
T1 card
(single/dual)
FRE card
Public
Frame Relay
Network
SDS-56
36120 MainStreet
Interworking Function
7976
In the case of ISDN access, data terminals use Q.931 signalling to access the CO
switch. The maximum user information rate per access channel for interfacing to the
ISDN network is 64 kb/s. The CO switch terminates the Q.931 signalling, and based
on the called number, selects a T1 DS0 on the trunk from its hunt group. The switch
initiates a call on the T1 DS0 using E&M signalling.
The 36120 MainStreet system terminates the T1 E&M signalling at a T1, Dual T1 or
Dual T1-2 card, and returns signalling to the CO switch to indicate that the trunk is
in use. The T1 DS0 is cross-connected to a frame stream on an FRS, FRE or PE card.
The frame stream is configured to support all PVCs required to allow frame relay
traffic to access the remote host.
(400)
25.11-1
Example configuration
Figure 25.11-2 shows an example configuration. The interface speed between the CO
switch and the 36120 MainStreet interworking function is in increments of n 8 kb/s
(where n is 1 to 7), up to 1.536 Mb/s. Since the interface is a channelized 1.544 Mb/s
voice trunk, the number of hunt groups supported is dependent upon the
capabilities of the CO switch. This number can range from 1 DS0 to 24 DS0s per T1
link, or 24 n, where n is the number of T1 links.
Figure 25.11-2: Switched Access over ISDN or Switched 56 Networks
T/A or
SDS-56 DSU
CPE
device
T1_CSU
Router
RS-232
BRI or
switched 56
ISDN
or SDS-56
network
Public
frame relay
network
T1 D4_JB7
36120 MainStreet
node
Interworking
function
D
T
1
F
R
E
A1 A3
T
1
T1 ESF_B8ZS
A7
D F
T R
1 E
A1 A2
D
T
1
A8
Public
frame relay
network
Router
T1_CSU
7975
At point A in the figure, the frame streams are configured to run LMI Network
protocol. In the frame relay backbone network (between points B and C), the frame
streams use Annex D Bidirectional.
At point A, DLCIs are configured to match the DLCIs transmitted over the access
lines. Each of the access lines must use an identical DLCI to represent each distinct
host to simplify the end terminal configuration. PVCs are configured from each
access DS0 to all allowed hosts.
25.11-2
(400)
T1 Signalling Termination
Newbridge support for switched access to frame relay PVCs is implemented
through a feature called T1 Signalling Termination. This feature enables T1, Dual T1,
and Dual T1-2 Line Interface modules to support AB (for D4 framing) and ABCD (for
ESF Framing) voice signalling response codes utilizing robbed bit signalling on a
DS0 basis.
This signalling option provides T1 termination for frame relay access to frame
stream circuits (on FRS, FRE and PE cards) and rate adaption circuits (on FRS cards
only). When configured for signalling termination, T1, Dual T1 and Dual T1-2 card
circuits respond to E&M signals by sending on- and off-hook signalling to the switch
that originated the E&M signals (for example, a DMS-100 or 5ESS).
Release
Comments
1115-H2 or higher
D115-H2 or higher
Q115-H2 or higher
Craft Interface
PBB116F2.00 or
higher
PC version
Craft Interface
SBB116F2.01 or
higher
The T1 digital interface between the DMS-100 or 5ESS and the Newbridge IWF
must support the E&M protocol using AB(CD) bits, as documented in the
signalling specification AT&T Publication #43801. Only the A bit is monitored for
status, but the CD bits match the AB values for ESF T1 lines.
The DMS-100 or 5ESS must perform all ISDN protocol requirements, hunt group
functionality, call blocking, screening and security if required, and PVC
validation and authentication.
The DMS-100 or 5ESS must provide the protocol conversion required to connect
ISDN or switched 56 access lines to T1 digital trunks.
(400)
25.11-3
25.11.2
25.11-4
(400)
T1
DUAL_T1
DUAL2_T1
SK000194
2.
FUNCTION
MORE
RBS_ON
SIG_TYPE
TERMINATE
PROCEED
SK000195
Note
For a super-rate bundle (multiple DS0s), configure the master (primary) circuit for
signalling termination and RBS. Signalling information is carried on this circuit.
3.
I/F_SPEED
TRANSP_BW
<speed>
<bandwidth>
SK000196
where
speed is 8 to 1536 kb/s
bandwidth is 1 to 7
(400)
25.11-5
Note
Calculate the interface speed using the formula m n 8 kb/s, where m is the
number of DS0s and n is the transport bandwidth.
4.
5.
The DLCIs and LMI parameters configured on the frame stream used in step 3 must
match those configured at the user devices.
25.11-6
(400)
26.1
26.1.1
(400)
26.1-1
DTE
UNI
User 1
DTE
Frame relay
SVC
access
device
T1 or
E1 card
Frame relay
SVC
access
device
User 2
SVC
signalling
channel
Frame
streams
SVC
data
channels
FRE card
T1 or E1 card
NNI
Frame relay
network
9875
Physical requirements
Frame relay SVCs require a physical configuration as shown in Figure 26.1-1. The
user device requires a physical connection to a frame relay SVC access device or a
router that manages frame relay SVC connections. The frame relay SVC access
device requires a physical connection to an interface card, such as an E1 or T1 card,
with the same physical and electrical characteristics as the frame relay SVC access
device or router. The 36120 MainStreet PTX requires at least one FRE card with SVC
software installed.
Call processing
Figure 26.1-2 summarizes the functionality of frame relay SVC on an FRE card. Each
user communicates with its DTE (a router or another frame relay SVC access device).
The DTE communicates with the FRE card on a frame stream through the E1 or T1
card. The FRE card processes each call based on the functionality incorporated in its
software.
26.1-2
(400)
User 4
(1-613-591-3606)
DTE
S1
T1 or E1
card
T1 or E1
card
S2
DTE
FRE
Signalling channels
User management
Routing
Connection management
Diagnostics
User 2
(1-613-591-3602)
User 3
(3020-26661010)
S3
DTE
T1 or E1
card
Legend:
S
SVC data channel
Signalling channel
Frame stream
9882
Signalling channel management defines the operations performed at the UNI and
NNI. Signalling channel management includes addressing according to E.164 and
X.121 (national and/or international) numbering plan format and a set of attributes
that control the condition and configuration of the signalling channel. Chapter 26.2
provides the details on signalling channel management.
Call statistics can be collected with each signalling channel. Chapter 34.4 provides
details on the statistics collected.
(400)
26.1-3
User management defines the characteristics of a user device for which a subscribed
service is provided. The characteristics of the user, such as an address, are recorded
in a local user table on the FRE card. User screening ensures that every call received
is associated with a user recorded in the table. Chapter 26.3 provides the details of
user management.
Connection management software controls the method in which data connections
are established and released when SVC calls are processed. Chapter 26.4 provides
the details of connection management.
The routing function routes calls by selecting the path through the network. Calls
can be routed to a local user over a UNI or to a remote user over an NNI. The routing
function uses a static routing table which consists of a local user table and a remote
address table, both maintained by the administrator.
The remote address table consists of switch prefix addresses, and primary and
alternate routes to the destination address of the route user. The table is used to route
calls over a frame relay SVC network. Figure 26.1-3 shows a large network.
Nodes with the same address prefix cluster together inside a group. For example,
nodes with the user prefix of e1614 reside in group A. Each node has a local address
table and an associated remote address table.
User 1 places a call to user 2 with a destination address of e131522. The FRE at node
A1 looks first in its local user table. If the node does not find a match, it looks at its
remote address table and finds a best address match of e1315 using S1 as the primary
path and S2 as the alternate path. The call is routed to node A3, which has a remote
address table similar to A1. The best address match is over primary path S1(N) to
group D. Similar actions take place at D1. When the call arrives at D2, it finds a best
match in its local user table and forwards the call to user 2.
If the call was not successfully routed to user 2, the routing function could
implement alternate path routing, crankback or call clearing. Chapter 26.5 describes
these functions and routing in more detail.
Diagnostic tools, such as route tracing, frame relay ping and a message traffic
recorder are available through NMTI. Chapter 33.6 describes these diagnostic tools.
26.1-4
(400)
FRE
FRE
FRE
Node B3
Node B4
Node D3
S2
S3
S1
FRE
FRE
FRE
FRE
e13152
Node B2
Node B1
Node D1
Node D2
Group
B
Group
D
S1
S1(N)
e1613
e1315
S2(N)
User 2
e131522
e16141
S3
FRE
Node A3
S1
FRE
FRE
e16143
Node C4
Node C3
e16142
FRE
FRE
FRE
FRE
S2
Node A1
Node A2
Node C1
Node C2
Group
A
Group
C
e1614
e1504
User 1
Local User Table for Node D2
Primary Alternate
Route
Route
S2
S1
S2
S1
S2
S1
S2
S1
S2
S1
Name
Address
Frame
Stream
User 1
User 2
User 3
e131521
e131522
e131523
S1
S1
S2
9881
(400)
26.1-5
26.1.2
Configuration Summary
This section describes the general process for setting up SVC calls for nodes at the
edge of the network and nodes within the network. Section 26.1.3 provides a
configuration example using this general process.
card.
Cross-connect the frame streams to the aggregate circuits.
26.1-6
(400)
26.1.3
(400)
26.1-7
FRAD
e1594
DT1
RS-232
FRE
DT1
User A
Address
6135913601
e1416
User B
Address
4162321415
Primary ro
B
route to
Alternate
443
from e1
ute to B fr
ary
from route
e14 to B
43
Prim
Router
FRE
DT1
DE1
FRE
B T1 or E1
to
ute 3
ro
te 161
e
na
ter rom
f
Al
e1443
RS-232
DT1
DE1
T1 T1
or E1
FRE
V.35
e1613
T1 or E1
Router
UNI
om e180
Pr
UNI
Primary route to B
from e1594
e to B
Alternate rout
from e1594
im
ar
fro y rou
m
e1 te to
61
3 B
NNI
DE1
FRE
T1 or E1
e1809
9993
Figure 26.1-5 provides a map of the circuit-switched connections for the network in
Figure 26.1-4.
26.1-8
(400)
A-2 1
1
B-1 2
2
User A
e1594
Slot
DT1
e1613
FRE
A-1
DT1
2
2
RS-232
1
2
User B
A-1
1
1
A-1
Slot
1
2
A-1
B-1
DT1
FRE
2
e1443
DE1
T1 or E1
1
A-1
Slot
FRE
DE1
4
RS-232
T1 or E1
T1 or E1
FRE
e1416
B-1
DT1
V.35
Slot
2
2
B-1
1
1
1 , 2 , 3 , 4 = frame streams
A-1
B-1
FRE
e1809
DE1
T1 or E1
Slot
5
9992
(400)
26.1-9
The following procedures provide the steps to set up the SVC calls for nodes e1613,
e1594 and e1416, using the information in the previous illustrations.
To configure the parameters for node e1613 through the Control card
1.
2.
ii.
To configure the parameters for node e1613 through the FRE card
1.
2.
Configure a new user with the name of A. See section 26.3.3 for details.
3.
i.
ii.
ii.
26.1-10
(400)
4.
ii.
v.
vi.
x.
xi.
To configure the parameters for node e1594 through the Control card
1.
2.
ii.
To configure the parameters for node e1594 through the FRE card
1.
(400)
26.1-11
2.
ii.
v.
vi.
3.
4.
ii.
v.
vi.
x.
xi.
To configure the parameters for node e1416 through the Control card
1.
2.
ii.
26.1-12
(400)
To configure the parameters for node e1416 through the FRE card
1.
2.
3.
i.
ii.
ii.
ii.
v.
vi.
x.
xi.
(400)
26.1-13
26.2
26.2.1
26.2.2
Figure 26.2-1 shows the default configuration for the parameters when a signalling
channel is first connected. See section 26.2.3 to change any of the signalling channel
parameters from the defaults. The parameters for the message traffic recorder are
described in section 33.6.2. CIR and the booking factor are described in section 26.4.3.
(400)
26.2-1
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
2-CONNECT
7-MORE...
3-DISCONNECT
8-CANCEL
4-ADMIN_STAT
9-QUIT
5-SIG_PROFIL
0-
Signalling channels can be disconnected from the SVC software component. Upon
disconnection, the following events occur.
All calls on the frame stream associated with the signalling channel are cleared.
All statistical counters relating to the signalling channel are cleared.
Note
When the SVC software component is connected, the LMI protocol automatically
changes to no protocol.
CONNECT
DISCONNECT
SK000942
26.2-2
(400)
26.2.3
Name
The signalling channel can be assigned a name of 0 to 25 characters, including A to
Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon).
(400)
26.2-3
When the administrator changes an associated signalling profile number, the switch
performs the following actions:
1. All existing SVC calls are cleared.
2. The operational status changes to down.
3. The signalling profile changes.
4. The operational status changes to up.
Stations:nn
FS
Name
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Admin
Oper
Profile MTR
Status
Status
#
--------------------------------------------------------------------S1
Disabled Down
1
S2
not connected
S3
not connected
S4
not connected
S5
not connected
S6
not connected
S7
not connected
S8
not connected
S9
not connected
S10
not connected
CONFIG SVC SIGNALLING CHANNEL 1
1-PAGE_UP
6-
26.2-4
2-PAGE_DOWN
7-
38-CANCEL
(400)
49-QUIT
50-
SHOW_LIST
PAGE_UP
ADMIN_STAT
PAGE_DOWN
SIG_PROFIL
CHG_NAME
<profile_no.>
<name>
MORE
ADMIN_UP ADMIN_DOWN*
STRIP_PREF
PASS_PREF*
SK000941
where
Scc is a frame stream circuit between S1 and S62
profile_no. is a number from 1 to 10, inclusive
name is 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon)
26.2.4
Signalling Profiles
A set of attributes forms the signalling profile. These attributes govern the exchange
of messages within the signalling channel.
Each switch contains a maximum of 10 profiles; each profile can be used by one or
more signalling channels. The following sections provide a description of the
attributes.
Profile name
Each profile can be assigned a name consisting of 0 to 25 characters, including A to
Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon). The characters assigned to the
profile need not be unique because the profile name is only an aid to the network
administrator and has no intrinsic meaning to the switch.
(400)
26.2-5
NAME
PROTOCOLS
<name>
X.36
FRF.4*
X.76
SK000938
where
profile_no. is a number between 1 and 10, inclusive
name is 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, %, and : (colon)
Description
Range
Default
Protocol
T303
1 to 500 s
4s
T305
1 to 500 s
30 s
X.36, FRF.4
T308
1 to 500 s
4s
T310
1 to 500 s
35 s
T316
1 to 500 s
120 s
X.36, X.76
T303
T305
T308
T310
T316
<time>
SK000939
where
profile_no. is a number from 1 to 10, inclusive
time is a value from 1 to 500 s
26.2-6
(400)
Description
Range
Default
Timer T200
1 to 30000 ms
1500 ms
Timer T203
1 to 500 s
30 s
Counter N200
1 to 30
Counter N201
16 to 4472 octets
1600 octets
T200
N200
N201
T203
<time1>
<count>
<octets>
<time2>
SK000940
where
time1 is from 1 to 30000 ms
count is a number from 1 to 30
octets is from 16 and 4472 octets
time2 is from 1 to 500 s
(400)
26.2-7
26.3
26.3.1
26.3.2
(400)
26.3-1
Prefix types
The two switch address prefixes are:
When a switch address prefix is changed from one value to another value, relative
addresses change to the new value. Calls currently using the old value remain
connected using the old value until the call is cleared by the calling DTE.
E.164
X121
<value>
SK000943
where value is between 1 and 11 digits, preceded by an x for X.121 and an e for E.164
26.3.3
User Configuration
A user configuration contains a number of attributes which define a set of privileges
and restrictions, and the identity and access point of each attached user device. A
user configuration can assist in the diagnosis of problems in a network. The
administrator creates and can view, add or delete user configurations. All user
configurations, up to a maximum of 200, are stored in software in a local user table.
The local user table contains information, such as the user name, address and
associated frame stream, that assists in user screening and in route determination.
Name
Each user can be identified by a name. It can be from 0 to 25 characters, including
A to Z, a to z, 0 to 9, - (hyphen), +, &, /, % and : (colon). The default is blank.
26.3-2
(400)
User address
Each user can be identified by an address. An address may be an absolute or a
relative address. The default is derived from the CPSS address of the FRE card.
Absolute addresses have a numbering plan identification (e for E.164 or x for X.121)
plus a numerical portion of 1 to 19 digits where each digit is in the range of 0 to 9.
Example addresses are e16135913601 and x3104203981.
Relative addresses are only complete when the assigned switch prefix is substituted
for the switch prefix representation of e+ and x+. The resulting address must be at
least 1 digit and not greater than 19 digits after the switch prefix. The address must
be assigned in international format. For example, if the switch prefix is e1613591 for
E.164 and x3104 for X.121, e+3601 (a total of 11 digits) and x+213981 (a total of 10
digits) are valid addresses.
Default user
The administrator can assign a default user to each frame stream on the FRE card
when multiple user configurations reference the same frame stream. The default
user is used when no calling party IE is present in the setup message or when the
setup message provides a calling address which is not configured in the local
address table.
(400)
26.3-3
Toronto:A
Alarms:1
11-May-1997
8:35a
Frame
Admin/Op
Is
# Address
User Data
Stream
Status
Default?
------------------------------------------------------------------------------1 E1102301
E.164_Prefix
2 E+1234
Vancouver-10
S43
Enabled
No
3 E+3601
Vancouver-5
S11
Disabled
No
4 X2102301
X.121_Prefix
5 X+416284
User-A
S2
Enabled
No
1-PAGE_UP
6-
2-PAGE_DOWN
7-
3-SHOW_ENTRY
8-CANCEL
49-QUIT
50-
PAGE_UP
PAGE_DOWN
SHOW_ENTRY
<entry_#>
SK000952
26.3-4
(400)
SHOW_LIST
STREAM
CHG_STATUS
NAME
<Scc>
MORE
<name>
ADMIN_UP
ADMIN_DOWN*
DELETE
DEFALT_ON
DEFALT_OFF
SK000951
where
address is an E.164 or X.121 address
Scc is a frame stream circuit from S1 to S62
name is from 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, and : (colon)
26.3.4
User Screening
User screening ensures that every call request is associated with a user configuration
or a default user. When an incoming call request is received, the calling party IE is
checked against the local user table to determine the call admissibility.
Table 26.3-1 summarizes the user screening functionality.
Table 26.3-1: User Screening
Calling
Party IE
User
Configuration
Default User
Configured
No
n/a
Yes
No
n/a
No
Yes
No
Yes
Yes
No
No
Newbridge
enhancement
Yes
Yes
n/a
Yes
Action
(400)
Standards
Compliant
Yes
Newbridge
enhancement
Yes
26.3-5
26.4
26.4.1
(400)
26.4-1
User 1
S1
Frame
relay
SVC
access
device
Setup message
DLCI allocation
call reference allocation,
CAC
S1
Connect message
S2
FRE
Setup message
S2
FRE
Data cross-connection
S1
Connect message
S2
FRE
X
Release message
Legend:
Data disconnection
Release message
Signalling channel
Frame stream
Frame
relay
SVC
access
device
User 2
9876
26.4-2
(400)
If the FRE card is reset, all SVC connections are released. If the operational status of
the signalling channel on a particular frame stream goes down, all calls that cross
that stream are disconnected.
The following sections describe connection management in more detail.
26.4.2
DLCI allocation
The connection manager allocates a DLCI to the incoming stream when a setup
message is received from a calling DTE.
The connection manager allocates a DLCI for the outgoing stream before the setup
message is forwarded. The connection manager keeps track of the used and unused
DLCIs within the available ranges. The range of DLCI values is 16 to 1007 for
backplane frame streams.
When a signalling channel carried over an NNI link has its administrative status
enabled, an automatic negotiation occurs between the FREs on either end of the link.
The negotiation determines which end allocates DLCIs for calls beginning at the
high end of the allowable range, and which end allocates DLCIs at the low end.
The negotiated allocation method used depends on the signalling protocol assigned
to the frame stream. For the X.36 and FRF.4 protocols, the default is to use the DLCI
values starting at the low end of the range. For the X.76 protocol, the default is to use
the negotiated DLCI. If the protocol is changed to X.76, the DLCI used is taken from
what was previously the default before the change was made.
The administrator can override the default allocation for each protocol. The options
are:
negotiated
The FRE uses the end of the DLCI range assigned to the signalling channel during
the negotiation process. This applies only to the X.76 protocol.
low
The FRE assigns DLCIs from the low end of the allowable range.
high
The FRE assigns DLCIs from the high end of the allowable range.
If the administrator changes the value from low or high to negotiated while the
signalling channel is in use, the FRE begins assigning DLCIs from the end of the
range assigned after the signalling channel was last enabled.
(400)
26.4-3
NEGOTIATED
HIGH
LOW
SK000953
26.4.3
CIR
CIR is the committed information rate associated with the signalling channel. It is
not enforced on the signalling channel but it is used by connection management for
connection admission control. The range varies from 0 to 1984000 b/s with a default
of 0 b/s.
Booking factor
The booking factor overbooks or underbooks a frame stream. The values range from
1 to 2000% of the interface speed. The default of 100% implies no overbooking or
underbooking. The booking factor is set on the signalling channel controlling the
frame stream.
26.4-4
(400)
The interface speed for a backplane frame stream is the same as the bandwidth of the
backplane frame stream configured by the administrator.
Any changes made to the booking factor take effect on new call admissions but not
on calls already established on a frame stream.
CIR
BOOKING
<cir>
<%>
SK001021
where
Scc is a frame stream circuit from S1 to S62
cir is between 0 and 1984000 b/s
% is between 1 and 2000%
26.4.4
Class-of-service guarantee
COS guarantee determines whether the admission of a new connection maintains
the class of service for all existing connections, rejecting the connection if congestion
is anticipated.
(400)
26.4-5
COS guarantee can be either no COS guarantee or COS guarantee 1. With the former
choice, every call is accepted. With the latter choice, a call is accepted if the
connection manager finds the following three conditions are satisfied.
This condition is satisfied if the higher of the two requested frame sizes does not
exceed the maximum frame size supported by the two frame streams that the call
crosses.
The requested CIR values are acceptable.
This condition is satisfied if either case 1 or case 2 is valid.
Case 1 - Requested CIR
This information applies to both the incoming and outgoing streams. In the
formulas below, Current CIRs are the CIRs for a particular direction of all
SVC calls currently in progress on a stream. ReqCIR is the requested CIR for
a particular direction in the setup message.
For the backplane stream, the following must be valid:
1. ReqCIR Interface Speed
2. ReqCIR (Booking Factor/100) Interface Speed SCurrentCIRs
NO_GUARNT*
GUARNT_1
SK000944
26.4-6
(400)
26.5
SVC Routing
This chapter describes SVC routing, including the remote address table and route
failure handling.
26.5.1
(400)
26.5-1
26.5.2
destination address
26.5-2
(400)
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Address
Route List
Primary
Alternate
Name
Route
Route
--------------------------------------------------------------------1 e15195726941
Toronto-10
S1
S2
2 e15105183472
Toronto-20
S2
S3
3 e16047232157
Vancouver-2
S2
S1
4 x3245641280
Vancouver-5
S2
S1
5 x345641279
Vancouver-10
S2
S1
2-PAGE_DOWN
7-
3-SHOW_ENTRY
8-CANCEL
4-NEW_ENTRY
9-QUIT
5-DELETE
0-
Table 26.5-1 lists and explains the error and caution messages for routing.
Table 26.5-1: Error and Caution Messages for Routing
Message Type
Error
Caution
Message
Explanation
On first page.
On last page.
Self-explanatory.
(400)
26.5-3
PAGE_UP
PAGE_DOWN
SHOW_ENTRY
NEW_ENTRY
DELETE
<entry_no.>
<address>
<entry_no.>
CHG_NAME
CHG_PRI
CHG_ALT
<name>
<Scc>
<Scc>
SK000948
where
entry_no. is a number from the number column on screen
address is the switch prefix number in international format
name is from 0 to 25 characters, including A to Z, a to z, 0 to 9, - (hyphen), +, &, /, % and : (colon)
Scc is a frame stream circuit between S1 and S62
26.5.3
If the called party is a local user, the call is routed on the link which provides the
best address match inside the local user table.
If the called party is a remote user, the call is routed on the link which provides
If the call request cannot be routed, then route failure handling is invoked; see
section 26.5.4.
26.5.4
26.5-4
(400)
The routing function checks each setup message to determine if the message has
been looped back on the call setup route. If the call is looped back to the calling node,
either crankback or call clearing is invoked.
Routing failures of remote user calls are handled either through alternate path
routing or crankback. Routing failures of local user calls are handled through call
clearing.
Crankback
Crankback is an indication in the IE of the setup message and provides a mechanism
to partially release a connection setup in progress that has encountered a failure.
Crankback releases the call to previous FREs in the call setup path when a call
request cannot be forwarded over an NNI on either a primary or alternate route.
Figure 26.5-2 shows an example of crankback being used. User 1 attempts a call to
user 2. At node A, the primary route to user 2 is through node B with an alternate
route through node C. At node B, the primary route is to node D with an alternate
route to node A over a different frame stream. The link to node D is down. Node B
cannot route the call on its alternate route as this would loop the call on the same
frame stream as it arrived on. Node B invokes a crankback to clear the call request to
node A, which routes the call on its alternate route.
Figure 26.5-2: An Example of a Crankback
User 1
User 2
FRE
DTE
Node D
FRE
Node B
FRE
Node A
DTE
Node C
Primary route to User 2
FRE
9880
(400)
26.5-5
Call clearing
The node releases the call back to the calling party by sending a release message
using the cause values in Table 26.5-2.
Table 26.5-2: Cause Values for Call Clearing
Failure Condition
26.5-6
Cause Value
(400)
27.1
27.1.1
27.1.2
X.25 Service
(400)
27.1-1
27.1-2
(400)
X.25 Serivce
27.1.3
X.25
Link Layer
Reliable
Transfer Protocol
Generic
Frame Router
7354
Link layer
The link layer of 36120 MainStreet X.25 fully supports the 1984, 1988, and 1992
versions of ITU-T Recommendation X.25. The link layer provides X.25 DTEs with
direct X.25 access and frame relay encapsulated access to the switch.
See section 27.14.3 for more information about the link layer.
Network layer
The network layer of 36120 MainStreet X.25 fully supports the 1984, 1988, and 1992
versions of ITU-T Recommendation X.25, as well as some non-standard facilities.
The DCE network layer is a full-featured X.25 packet switch that supports local
switching, and handles all aspects of call setup, routing, and clearing. The network
layer interfaces to the link layer (for traffic to and from X.25 access lines), and the
RTP (for traffic to and from backbone trunks). The network layer reacts to congestion
notifications from both the link layer and RTP subsystems, and implements flow
control mechanisms when required.
See section 27.14.6 for more information about the network layer.
X.25 Service
(400)
27.1-3
27.1-4
(400)
X.25 Serivce
DTE
Network Network
Layer
DCE
Network
Layer
DCE
Network
Layer
RTP
Link
LAPB
LAPB
Encapsulator
Physical Physical
DTE
RTP
LAPB
LAPB
GFR
FR
DTE
Network
Layer
GFR
LAPB
GFR
LAPB
Encapsulator FR or
FR or
FR or
FASTbus FASTbus FASTbus
Physical
FR
Physical
Physical
Physical
Physical
FRS
PE
Transit PE
PE
DTE
7322
27.1.4
X.25 Service
(400)
27.1-5
DCC
or
DNIC
m x n x 8 kb/s
LAPB
X.25
switch
DTE
64 x m kb/s
LAPB
TDM
network
PRI link
PRI
card
X.25
backbone
network
DTE
m
= Transport bandwidth (1 to 8)
7296
RFC 1490 and ANSI T1.617a Annex F Multiprotocol Encapsulation over Frame Relay
ANSI T1.617a Annex G Encapsulation of ITU-T X.25/X.75 over Frame Relay
Encapsulation can be performed by a standards-compliant PAD or FRAD at the user
premises, or by the FRS card on a 3600 MainStreet series bandwidth manager
system. The FRS encapsulates LAPB frames in frame relay frames according to the
multiprotocol encapsulation methods defined in RFC 1490 and ANSI T1.617a Annex
F.
27.1-6
(400)
X.25 Serivce
Figure 27.1-4: Encapsulated Access for Basic Rate and Super-rate Devices
Frame relay site
X.25 site
Frame relay
connection
DCC
or
DNIC
m x n x 8 kb/s LAPB
DTE
DTE
FRS
card
PRI
card
Encapsulated LAPB
PRI
card
X.25
switch
PRI
card
64 x m kb/s
LAPB
X.25
backbone
network
TDM
network
DNIC
FRS
card
X.25
switch
DTU
X.25
backbone
network
8545
X.25 Service
(400)
27.1-7
27.2
27.2.1
X.25 Service
(400)
27.2-1
PE A
PE C
Reliable
Transfer
Protocol
PE D
o
g
w
et
lN
a
ic
o
rk
T
o
p
o
lo
g
y
Backbone trunk
(Frame relay PVC)
PE B
PE A
PE C
Generic
Frame
Router
kb
ac
PE D
lo
T
Frame
relay link
PE B
Public
Frame Relay
Network
PE A
PE C
PE D
ra
F
e
FRE A
ay
el
R
y
g
lo
T
PE B
T1
36XX
MainStreet
PE A
X
36
T1
36XX
MainStreet
Public
Frame Relay
Network
V.
35
PE C
PE D
E1
E1
FRE A
36XX
MainStreet
ee
tr
ai
36XX
MainStreet
k
n
ru
T
y
lo
o
p
o
36XX
MainStreet
732
27.2-2
(400)
X.25 Serivce
27.2.2
guarantees the delivery of frames in sequence, error free and without duplication
selectively retransmits lost frames
implements flow control between the transmitter and receiver X.25 switches
Note
RTP parameter values are not configurable. The default values are optimized for
most network implementations.
X.25 Service
(400)
27.2-3
Keep alive
This function assures that the two peer entities participating in a connection remain
in a link connection-established state even in the case of prolonged absence of data
transfer.
Transfer of user data
This function conveys user-data between users of the service.
Noisy links
RTP handles noisy (high bit error) links effectively through the use of selective
retransmissions. A single retransmission causes the transmit window size to be
reduced: the window size is reduced due to a single, isolated frame loss which is
more likely to occur due to a noisy link rather than frame relay switch congestion but
recovers back to its original size within a short period of time.
Multiple retransmissions can occur during a burst of errors that cause the window
size to be reduced continuously for every retransmitted frame. This effectively
reduces the window to a minimum size of one, and disallows retransmission of any
new traffic until it has recovered from the burst of errors.
27.2-4
(400)
X.25 Serivce
Logical
channel
DTE
Switch A
Switch E
Network layer
Network layer
Link
layer
RTP
RTP VCon
GFR
RTP
GFR
Link
layer
Logical
channel
DTE
Frame
relay
PVCs
Switch B
Switch D
Switch C
7549
A VCon is taken down after the last X.25 call is cleared to the remote switch. This
happens only after a fixed-value timer of eight minutes has expired. When the timer
expires, the resources are returned to the switch. If another call is made within the
eight-minute period, the VCon remains established, and the timer is reset after the
last call has cleared. The VCon then has another eight minutes before it is either
terminated, or another call is established.
Figure 27.2-3 shows the mapping between an X.25 virtual circuit, an RTP VCon, and
a frame relay PVC. The following subsections describe how the mapping occurs in
two virtual call setup scenarios.
X.25 Service
(400)
27.2-5
DTE
Switch C
DCE
VC x
B2
B1
FR
PVC 3
C4
FR
PVC 2
C1
DTE
Switch D
RTP
VCon
A<- ->C
FR
PVC 1
VC z
VC x
DCE
DTE
C2
VC z
FR
PVC 4
C4 C3 C2 C1 B2 B1
RTP
VCon
A<- ->B
VC = virtual circuit
DCE
Transit frame
relay switch F
Switch E
VC y
DTE
Switch A
FR = frame relay
8556
27.2-6
(400)
X.25 Serivce
Note that the frames B2 and B1 on FR PVC 3 at switch B arrive out of order. The RTP
managing VCon A<-->B ensures that the frames are given in order (B1, B2) to the
DCE at switch B.
Example 2, switch A to switch C
Packets are transmitted from switch A to C as follows.
1. A DTE connected to switch A sends a call request using virtual circuit VC z, and
uses VCon A<-->C to reach the DTE at switch C. The same mechanism is
followed as described above to reach transit switch D.
2. At transit switch D: The GFR uses FR PVC 4 as its next hop towards destination
switch C. Note that FR PVC 4 terminates on switches D and C.
3. At transit frame relay switch F: On PVC 4, the frame is only switched by the
frame relay switch en route to its destination at switch C because FR PVC 4 does
not terminate at this switch. This transit frame relay switch could be Newbridge
or other vendor equipment.
4. At destination switch C: The frame relay switch passes the frame to the GFR (FR
PVC 4 terminates at switch C). The GFR determines that the frame has reached
its destination, decapsulates the frame from frame relay format, and passes the
frame to the RTP. The acknowledgment frame from the RTP at switch C is sent
back to the RTP at source switch A using the same mechanism as described
above, and VCon A<-->C is thus established. All subsequent X.25 packets on VC
z follow this route.
Note that frames C1, C2 and C4 on FR PVC 4 arrive at switch B with frame C3
missing. The RTP managing VCon A<-->C ensures that frame C3 is selectively
retransmitted and all four frames (C1, C2, C3, C4) are delivered to switch C in the
correct order.
Congestion management
Because a VCon may physically span one or more intermediate switches, there is a
possibility of delays and congestion within the network switches along the VCon
path. The RTP provides a congestion control mechanism so that the X.25 network
layer protocol is relieved of this responsibility. The X.25 network layer views the
VCon as a normal physical point-to-point link.
BECN bit congestion handling
Congestion between peer RTP endpoints controlled by reacting to frames having the
BECN bit set is not supported but will be available in future releases. When the RTP
receives packets with BECN bit set, it uses them as a means of congestion avoidance.
BECN bits indicate to the receiver that the packets it transmits may encounter
congested resources. This triggers source-controlled transmitter rate adjustment,
whereby the source reduces the transmit window size.
X.25 Service
(400)
27.2-7
27.2-8
(400)
X.25 Serivce
Flow control
The switch uses the following mechanisms to regulate flow control when congestion
is detected.
1. The RTP monitors frames received from a particular backbone trunk over a
pre-set congestion monitoring period. When more than a pre-determined
percentage of all frames receive have the BECN bit set, the transmitter reduces
the size of the transmit window. The transmit window size is increased again
when the percentage of frames with the BECN bit set is less than the
pre-determined threshold. This is done for each VCon.
2. If resources (the system buffer pool) fall below 50%, then no new virtual
connections are allowed. If the system buffer pool availability falls below 10%,
the network layer is put in flow control state. If system buffer pool depletion is
detected by the receiver, then less credit is granted to the transmitter.
3. If frames are retransmitted by the RTP (implicit congestion detection) or BECN
bits are set, the RTP reduces the transmit window size and then gradually
increases the window size as it receives credits. This is done for each VCon.
4. When the transmit queue for the VCon grows above a certain threshold, each
DTE using the VCon is flow controlled. In this condition, the switch disallows
new calls to the destination switch and flow controls the virtual circuits using the
VCon (actively using RNR packets, or passively by not transmitting any RRs
back).
5. When all of the above mechanisms have failed to alleviate the congestion
situation, the VCon becomes absolutely congested (a very remote possibility).
This causes the VCon to go down and send a disconnect indication to the
network layer, which clears all virtual circuits and resets all PVCs that use the
affected VCon.
X.25 Service
(400)
27.2-9
Caution
The decision to use a load balancing topology should be carefully considered for the
following reasons:
To employ load balancing, it must be enabled on every switch across the entire
network.
The GFR load balancing support may adversely affect RTP performance on
27.2.3
The network can segment and combine packets to establish calls between DTEs
27.2-10
(400)
X.25 Serivce
The switch never segments or combines packets across the 128 byte boundary.
Segmenting and combining can occur between any packet size combinations
between 16 and 128 bytes, and between 128 and 4096 bytes; however, segmenting
and combining cannot occur, for example, between 16 and 256 bytes.
P (indicated) 128
P (requested) 128
X.25 Service
(400)
27.2-11
Table 27.2-3: Scenarios Where the Network Avoids Segmenting and Combining Packets
Flow Control
Negotiation at
Calling End
Flow Control
Negotiation at
Called End
Comments
On
On
On
Off
Off
On
Off
Off
Table 27.2-4: Scenarios Where the Network Segments and Combines Packets
Flow Control
Negotiation at
Calling End
Flow Control
Negotiation at
Called End
On
On
On
Off
Off
On
Off
Off
27.2-12
(400)
Comments
X.25 Serivce
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
CC (256)
Use 256
internally
Destination
switch
128
IC(-)
FC neg = No
Def PS = 128
CC(-)
CA(-)
CG DTE
CD DTE
8731
In Figure 27.2-5, the originating switch segments and combines packets because it
supports the interface with the smaller default packet size.
Figure 27.2-5: Example of No Flow Control Negotiation Where the Originating Switch
Segments and Combines Packets
Segment and
combine at
originating switch
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
CC (2048)
Use 2048
internally
CC(-)
Destination
switch
2048
IC(-)
FC neg = No
Def PS = 2048
CA(-)
CG DTE
CD DTE
8732
X.25 Service
(400)
27.2-13
Table 27.2-5 is a matrix that shows all the packet size combinations that are possible
when neither the calling nor called DTEs subscribe to flow control negotiation. The
calling DTE column and called DTE row show the default packet sizes configured
for the calling and called DTEs. The subordinate cells in the matrix indicate the
packet size transmitted across the internal network. The symbol indicates that
the call is cleared because packet segmenting and combining cannot occur across the
128 byte boundary.
Table 27.2-5: Possible Packet Size Combinations When Neither DTE Subscribes to
Flow Control Negotiation
Called DTE Default Size
Calling DTE
Default Size
16
32
64
128
256
512
1024
2048
4096
16
16
32
64
128
32
32
32
64
128
64
64
64
64
128
128
128
128
128
128
256
512
1024
2048
4096
256
256
256
512
1024
2048
4096
512
512
512
512
1024
2048
4096
1024
1024
1024
1024
1024
2048
4096
2048
2048
2048
2048
2048
2048
4096
4096
4096
4096
4096
4096
4096
4096
27.2-14
(400)
X.25 Serivce
Figure 27.2-6: Example of Flow Control Negotiation at the Calling DTE Where Packet
Segmenting and Combining Does Not Occur
No segmenting
or combining at
at either switch
128
CR(256)
Originating
switch
FC neg = Yes
Def PS = XXX
IC (256)
CC (128)
Use 128
internally
Destination
switch
128
IC(-)
FC neg = No
Def PS = 128
CA(-)
CC(128)
CG DTE
CD DTE
8733
Figure 27.2-7 shows a case where the destination switch determines that the
proposed packet size (256) and default packet size of the called DTE (2048) violate
the rules in Table 6-2, and therefore transmits the largest packet size to the
originating switch. Although 2048 may be an allowable packet size for the calling
DTE, it violates the rules in Table 6-2, so the originally proposed values are sent in
the Call Connected packet to the calling DTE. The originating switch subsequently
segments and combines packets.
Figure 27.2-7: Example of Flow Control Negotiation at the Calling DTE Where the
Originating Switch Segments and Combines Packets
Segment and
combine at
originating switch
256
CR(256)
Originating
switch
FC neg = Yes
Def PS = XXX
IC (256)
CC (2048)
Use 2048
internally
CC(256)
Destination
switch
2048
IC(-)
FC neg = No
Def PS = 2048
CA(-)
CG DTE
CD DTE
8734
Table 27.2-6 lists all the packet size combinations that are possible when the calling
DTE subscribes to flow control negotiation, but the called DTE does not. The calling
DTE columns can show two packet sizes: the first value (in parentheses) indicates
the packet size proposed by the calling DTE in the Call Request packet; the second
value indicates the packet size returned by the switch in the Call Connected packet.
The called DTE columns show the default packet sizes configured for the called DTE.
X.25 Service
(400)
27.2-15
The internal network columns indicate the packet size transmitted across the
internal network. The table assumes that all packet sizes received by the originating
switch are allowed for the calling DTE. The symbol indicates that the call is
cleared because packet segmenting and combining cannot occur across the 128 byte
boundary.
Table 27.2-6: Possible Packet Size Combinations When the Calling DTE Subscribes to Flow Control
Negotiation
Calling DTE
Internal
Network
Called
DTE
16
16
16
(16) 32
32
(16) 64
Internal
Network
Called
DTE
Internal
Network
Called
DTE
(32) 32
32
16
(64) 64
64
16
32
(32) 32
32
32
(64) 64
64
32
64
64
(32) 64
64
64
(64) 64
64
64
(16) 128
128
128
(32) 128
128
128
(64) 128
128
128
16
256
32
256
64
256
16
512
32
512
64
512
16
1024
32
1024
64
1024
16
2048
32
2048
64
2048
16
4096
32
4096
64
4096
(128) 128
128
16
256
16
512
16
(128) 128
128
32
256
32
512
32
(128) 128
128
64
256
64
512
64
(128) 128
128
128
(256) 128
128
128
(512) 128
128
128
(128) 128
256
256
(256) 256
256
256
(512) 256
256
256
(128) 128
512
512
(256) 256
512
512
(512) 512
512
512
(128) 128
1024
1024
(256) 256
1024
1024
(512) 512
1024
1024
(128) 128
2048
2048
(256) 256
2048
2048
(512) 512
2048
2048
(128) 128
4096
4096
(256) 256
4096
4096
(512) 512
4096
4096
1024
16
2048
16
4096
16
1024
32
2048
32
4096
32
1024
64
2048
64
4096
64
(1024) 128
128
128
(2048) 128
128
128
(4096) 128
128
128
(1024) 256
256
256
(2048) 256
256
256
(4096) 256
256
256
(1024) 512
512
512
(2048) 512
512
512
(4096) 512
512
512
(1024) 1024
1024
1024
(2048) 1024
1024
1024
(4096) 1024
1024
1024
(1024) 1024
2048
2048
(2048) 2048
2048
2048
(4096) 2048
2048
2048
(1024) 1024
4096
4096
(2048) 2048
4096
4096
(4096) 4096
4096
4096
27.2-16
Calling DTE
(400)
Calling DTE
X.25 Serivce
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
CC (256)
Use 256
internally
Destination
switch
128
IC(256)
FC neg = Yes
Def PS = XXX
CC(-)
CA(128)
CG DTE
CD DTE
8735
Figure 27.2-9 shows a case where the network clears the call because the packet size
indicated in the Incoming Call packet and the packet size requested by the called
DTE violate Table 6-1.
Figure 27.2-9: Example of Flow Control Negotiation at the Called DTE Where the Call is
Cleared
Call cleared
256
CR(-)
Originating
switch
FC neg = No
Def PS = 256
IC (256)
Clear
Destination
switch
2048
IC(256)
FC neg = Yes
Def PS = XXX
Clear
CA(2048)
CG DTE
CD DTE
8736
X.25 Service
(400)
27.2-17
Table 27.2-7 is a matrix that shows all the packet size combinations that are possible
when the called DTE subscribes to flow control negotiation, but the calling DTE does
not. The calling DTE column shows the default packet sizes configured for the
calling DTE, and the called DTE row shows the packet sizes sent to and returned
from the called DTE. The subordinate cells in the matrix indicate the packet sizes
transmitted across the internal network.
In cases where the called DTE packet size values differ from the values received from
the originating switch, the discrepancies result from allowable packet size
restrictions. The table assumes that not all packet sizes received from the originating
switch are allowed for the called DTE. The symbol indicates that the call is
cleared because packet segmenting and combining cannot occur across the 128 byte
boundary.
Table 27.2-7: Possible Packet Size Combinations When the Called DTE Subscribes to
Flow Control Negotiation
Called DTE Negotiated Size
Calling DTE
Default Size
16
32
64
128
256
512
1024
2048
4096
16
16
32
64
128
32
32
32
64
128
64
64
64
64
128
128
128
128
128
128
256
512
1024
2048
4096
256
256
256
512
1024
2048
4096
512
512
512
512
1024
2048
4096
1024
1024
1024
1024
1024
2048
4096
2048
2048
2048
2048
2048
2048
4096
4096
4096
4096
4096
4096
4096
4096
27.2-18
(400)
X.25 Serivce
Figure 27.2-10: Example of Flow Control Negotiation Where Packet Segmenting and
Combining is Avoided
No segmenting
or combining at
either switch
256
CR(512)
Originating
switch
FC neg = Yes
Def PS = XXX
IC (512)
CC (256)
Use 256
internally
CC(256)
Destination
switch
256
IC(512)
FC neg = Yes
Def PS = XXX
CA(256)
CG DTE
CD DTE
8737
Table 27.2-8 lists all the packet size combinations that are possible when both the
calling and called DTEs subscribe to flow control negotiation. The calling DTE
columns can show two packet sizes: the first value (in parentheses) indicates the
packet size proposed by the calling DTE in the Call Request packet; the second value
indicates the packet size returned by the switch in the Call Connected packet. The
called DTE columns show the packet sizes sent to and returned from the called DTE.
In cases where the called DTE values differ from the values received from the
originating switch, the discrepancies result from allowable packet size restrictions.
The internal network columns indicate the packet size transmitted across the
internal network.
The table assumes that all packet sizes received by the originating switch are
allowed for the calling DTE. The symbol indicates that the call is cleared
because packet segmenting and combining cannot occur across the 128 byte
boundary.
X.25 Service
(400)
27.2-19
Table 27.2-8: Possible Packet Size Combinations When Both the Calling and Called DTEs Subscribe to
Flow Control Negotiation
Calling DTE
Internal
Network
Called
DTE
(16) 16
16
16
(16) 32
32
(16) 64
Internal
Network
Called
DTE
Internal
Network
Called
DTE
(32) 32
32
16
(64) 64
64
16
32
(32)32
32
32
(64) 64
64
32
64
64
(32) 64
64
64
(64) 64
64
64
(16) 128
128
128
(32) 128
128
128
(64) 128
128
128
16
256
32
256
64
256
16
512
32
512
64
512
16
1024
32
1024
64
1024
16
2048
32
2048
64
2048
16
4096
32
4096
64
4096
(128) 128
128
16
256
16
512
16
(128) 128
128
32
256
32
512
32
(128) 128
128
64
256
64
512
64
(128) 128
128
128
(256) 128
128
128
(512) 128
128
128
(128) 128
256
256
(256) 256
256
256
(512) 256
256
256
(128) 128
512
512
(256) 256
512
512
(512) 512
512
512
(128) 128
1024
1024
(256) 256
1024
1024
(512) 512
1024
1024
(128) 128
2048
2048
(256) 256
2048
2048
(512) 512
2048
2048
(128) 128
4096
4096
(256) 256
4096
4096
(512) 512
4096
4096
1024
16
2048
16
4095
16
1024
32
2048
32
4096
32
1024
64
2048
64
4096
64
(1024) 128
128
128
(2048) 128
128
128
(4096) 128
128
128
(1024) 256
256
256
(2048) 256
256
256
(4096) 256
256
256
(1024) 512
512
512
(2048) 512
512
512
(4096) 512
512
512
(1024) 1024
1024
1024
(2048) 1024
1024
1024
(4096) 1024
1024
1024
(1024) 1024
2048
2048
(2048) 2048
2048
2048
(4096) 2048
2048
2048
1024) 1024
4096
4096
(2048) 2048
4096
4096
(4096) 4096
4096
4096
27.2-20
Calling DTE
(400)
Calling DTE
X.25 Serivce
27.3
Standards Compliance
This chapter provides information about 36120 MainStreet X.25 standards
compliance.
27.3.1
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
1.
1.1
Yes
Yes
1.2
Multilink procedure
No
No
No
1.3
1.4
Yes
Yes
1.5
D-bit modification
No
No
1.6
Packet retransmission
No
No
1.7
Yes
1.8
Yes
1.9
Yes
1.10
Yes
1.11
Non-standard default packet sizes 16, 32, 64, 256, 1024, 2048, 4096
Yes
Yes
1.12
Yes
Yes
1.13
Yes
Yes
1.14
Yes
1.15
Yes
1.16
Yes
1.17
Yes
1.18
Yes
1.19
Yes
X.25 Service
(2)
(400)
27.3-1
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
1.20
Yes
1.21
Bilateral CUG
No
1.22
No
1.23
Yes
1.24
Yes
1.25
Yes
1.26
Yes
1.27
Yes
1.28
No
1.29
RPOA subscription
No
1.30
Hunt Group
Yes
1.31
Call Redirection
Yes
1.32
No
FS
Yes
FS
No
1.33
1.34
Direct Call
2.
2.1
Yes
2.2
Yes
2.3
Yes
2.4
Yes
2.5
No
2.6
Reverse charging
Yes
2.7
Fast select
Yes
2.8
NUI selection
Yes
No
(6)
2.9
Charging information
2.10
RPOA selection
No
2.11
No
2.12
Yes
2.13
Yes
2.14
Yes
FS
No
2.15
27.3-2
(4)(5)
(8)
(400)
X.25 Service
Notes
1. = Not applicable
A = Additional (optional)
E = Essential (mandatory)
FS = Further study (not yet defined)
2. On-line registration procedures have been agreed to be deleted from X.25 in the next (1996) version.
3. All throughput class values up to 192 kb/s are supported (new values for 128 kb/s and 192 kb/s are included in the 1992
version of ITU-T Recommendation X.25).
4. NUI Override is supported in Release 1 of 36120 MainStreet X.25, but the full range of parameters in X.25 Annex H is not
supported.
5. Charging Information procedures, Charging Information Request, and coding for the Time Duration and Segment Count
facilities will be supported in Release 1.1 of 36120 MainStreet X.25.
6. TOA/NPI address was not fully defined in 1988 versions of ITU-T Recommendations X.2 and X.25. It was still labelled FS
in 1992 versions of ITU-T Recommendations X.2 and X.25 (1992). Note that the TOA/NPI address facility was substantially
changed in the 1992 version of X.25 and further changes have been agreed for the 1996 version of X.25.
7. Extended format of CUG Selection facility is not supported.
8. These facilities will be supported in future releases of 36120 MainStreet X.25.
27.3.2
VC
PVC
Newbridge
Support
VC
PVC
1.
1.1
Yes
Yes
1.2
Multilink procedure
No
No
No
1.3
1.4
Yes
Yes
1.5
D-bit modification
No
No
1.6
Packet retransmission
No
No
1.7
Yes
1.8
Yes
1.9
Yes
1.10
Yes
1.11
Non-standard default packet sizes 16, 32, 64, 256, 1024, 2048,
4096
Yes
Yes
1.12
Yes
Yes
X.25 Service
(2)
(400)
27.3-3
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
1.13
Yes
Yes
1.14
Yes
Yes
1.15
1.16
Yes
1.17
Yes
1.18
Yes
1.19
Yes
1.20
Yes
1.21
Yes
1.22
Bilateral CUG
No
1.23
No
1.24
Yes
1.25
Yes
1.26
Yes
1.27
Yes
Yes
(3)
1.28
NUI Override
1.29
No
1.30
RPOA subscription
No
1.31
Hunt Group
Yes
1.32
Call Redirection
Yes
1.33
No
1.34
FS
Yes
1.35
Direct Call
FS
No
1.
1.36
No
1.37
No
1.38
No
1.39
No
2.
2.1
Yes
2.2
Yes
2.3
Yes
Yes
Yes
No
2.4
(4)
(7)
2.5
2.6
27.3-4
(7)
(400)
X.25 Service
User Class of
Service 8-11 and
13 (X.25) (1)
VC
PVC
Newbridge
Support
VC
PVC
2.7
Reverse charging
Yes
2.8
Fast select
Yes
2.9
NUI selection
Yes
2.10
No
2.11
RPOA selection
No
2.12
No
2.13
Yes
2.14
Yes
2.15
Yes
FS
No
2.16
2.17
ICRD selection
No
2.18
No
(8)
Notes
1. = Not applicable
A = Additional (optional)
E = Essential (mandatory)
FS = Further study (not yet defined)
2. On-line registration procedures have been agreed to be deleted from X.25 in the next (1996) version.
3. All throughput class values up to 192 kb/s are supported.
4. NUI Override is supported in Release 1 of 36120 MainStreet X.25, but the full range of parameters in X.25 Annex H is not
supported.
5. Charging Information procedures, Charging Information Request, and coding for the Time Duration and Segment Count
facilities will be supported in Release 1.1 of 36120 MainStreet X.25.
6. TOA/NPI address was labelled FS in 1992 versions of ITU-T Recommendations X.2 and X.25 (1992). Note that further
changes to the TOA/NPI address facility have been agreed for the 1996 version of X.25.
7. Extended format of CUG Selection facility is not supported.
8. These facilities will be supported in future releases of 36120 MainStreet X.25.
27.3.3
X.25 Service
(400)
27.3-5
Conformance
Conformance to Recommendation X.35 can be stated in one of two ways. The first is
the case where the PSPDN is providing the DTE-like interface to the private PSDN.
In this case, to conform to this recommendation it is necessary that the PSPDN
provide a full set of capabilities as described, including an addressing alternative,
routing functionality, an interworking unit or interworking function, or both, and a
complete set of procedures for restart, reset, setup, clearing, interrupt, facility
handling, and flow control.
The second is the case where the PSPDN is providing a DCE interface to the private
PSDN. To conform, the PSPDN must provide the capabilities described in the
relevant sections of the recommendation.
Table 27.3-3 shows 36120 MainStreet X.25 conformance to the relevant sections of
ITU-T Recommendation X.35.
27.3-6
(400)
X.25 Service
X.25 Service
Description
Conformance
Requirements
Clause 6
Topologies
Clause 7
Addressing
Subclause
7.1
Sharing of PSPDN
address space with
private PSDN
Subclause
7.2
Address assignment
for the
PSPDN/private
PSDN interworking
function
Optional
Mapping or substitution of
an address contained in the
address extension facility is
not supported
Subclause
7.3
Independent private
PSDN address space
Optional
Clause 10
General
considerations
Optional
Fully supported
Clause 11
Restart procedures
Optional
Fully supported
Subclause
12.1
Call setup
procedures
Optional
Supported
Subclause
12.2
Call clearing
procedures
Supported
Clause 13
Data interrupt
procedures
Optional
Supported
Clause 14
Flow control
procedures
Must be supported
Supported
Clause 15
Reset procedures
Supported
Clause 16
Optional user
facilities
Optional
(400)
27.3-7
27.4
27.4.1
F1-CONFIG
F5-ALARMS
F6-
X.25 Service
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
F2-HOUSE
F3-MAINT
F4-STATISTICS
F7-
F8-
F9-QUIT
(400)
8:35a
F10-
27.4-1
In addition to using the PE and X.25 FRE NMTIs, network operators must also
establish node management sessions with the Control card and the FRS card as part
of the X.25 configuration activities.
configure PE and X.25 FRE card circuits for direct X.25 access
configure FRS circuits and FRS subrate circuits for frame relay encapsulation
connect data interface circuits and primary rate interface circuits to direct circuits
on the PE or X.25 FRE cards
Additionally, perform the following non-X.25 specific activities at the Control card
NMTI:
configure the data interface circuits and primary rate interface circuits
configure and connect frame streams between PE or X.25 FRE cards and FRS
cards
27.4-2
(400)
X.25 Service
FRS NMTI
Use the FRS NMTI to perform the following X.25-specific configuration activities:
27.4.2
circuits
configure the parameters for frame stream circuits
connect encapsulation circuits to frame stream-DLCIs
Object
International TOA
FASTbus station
National TOA
Frame stream
Trunk circuit
X (1)
XAC
Xnnnn
XAC number
Xnnnn.Xnnnn
Xnnnn...
xaaa,xbbb,xddd
xaaa.Xnnnn
Notes
1. The identifier used for XACs (X) is always displayed in upper case to differentiate it from the NPI
identifier for X.121 addresses (x), which is always displayed in lower case. This convention is used
for display only; it is not necessary to specifically use upper or lower case when entering data.
X.25 Service
(400)
27.4-3
In some cases, the identifiers are context sensitive and do not have to be entered. For
example, if you omit the identifier after being prompted for a FASTbus station
number, a frame stream number, or an XAC number, the NMTI interprets the
meaning of the number based on the current menu function. However, some NMTI
menus require you to enter the letter before the number to clarify whether the
number represents a frame stream number, a FASTbus station number, an XAC
number or a trunk circuit number.
27.4.3
tasks that are performed to commission the switch and make it operational in the
network
(1)
(1)
Notes
1. Mandatory configuration activities.
27.4-4
(400)
X.25 Service
Configure the
GFR address
Configure
the GAT
Configure
the Switch
Configure
and connect
backbone trunks
Configure
and connect
circuits for X.25
access lines
Configure the
XAC interface parameters
(link layer, network layer,
address translation table)
Configure
User Access
Configure NUAs
and assign
to XACs
Configure
subscription options
and facilities
7523
X.25 Service
(400)
27.4-5
27.4.4
Options
Default
Number of XACs
1 512 (PE)
1 128 (X.25 FRE)
128 (PE)
32 (X.25 FRE)
Options
Default
GFR Address
hub-leaf
None
Redundant Routing
Disabled
Enabled
Disabled
Load Balancing
Disabled
Enabled
Disabled
Disabled
Enabled
Disabled
Delta Value
0 256
List of Aliases
None
Disabled
Enabled
Disabled
0 8 Mb/s
0 40 Mb
27.4-6
Options
Default
Trunk Circuit
1 128
None
Cost
1 255
50
Poll Timer
0 127 500 ms
(400)
X.25 Service
Options
Default
None
None
0 500 s
10 s
Options
Default
DTE
DCE
DCE
8
128
1 7 (modulo 8)
1 127 (modulo 128)
1 20
10
3000 ms
0 3000 ms in multiples of
100 ms
200 ms
60 000 ms
Congestion Timer
3000 ms
519 bytes
X.25 Service
Options
Default
Service Type
X.25
X.25 Gateway
NUI Agent
Accounting Agent
XFR
x.75 Gateway
X.25
DTE DCE
DCE
X.25 Version
1984/1988
1992
1984/1988
8
128
Base LCN
1 4095
1 for XFR
(400)
27.4-7
Parameter
27.4-8
Options
Default
Number of LCNs
1 4095
1 for XFR
32
1 for XFR
Number of PVCs
0 4095
0 1 for XFR
0 4095
0 for XFR
0
0 for XFR
0 4095
32
0 4095
0 1 for XFR
0
0 for XFR
0 630 s
180 s
0 630 s
200 s
0 630 s
180 s
0 630 s
180 s
0 630 s
60 s
Inactivity Timer
0 630 s
0s
1 180 s
1s
1 19 digits
19
Yes
No
No
Yes
No
No
Yes
No
Yes
Default NPI
X.121
E.164 Analog
E.164 Digital
X.121
Yes
No
No
Yes
No
No
Basic
Extended
Basic
Yes
No
No
Yes
No
Yes
Generate Alarms
Yes
No
No
(400)
X.25 Service
Options
Default
ACT (packets)
10 128
10
SCT
0 100%
80%
MCT
0 100%
0%
120 sec
X.25 Service
Options
Default
Entry Number
1 256
None
ix
ix
Direction
Incoming
Outgoing
Both
Both
Which Address
Calling
Called
Both
Both
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
(400)
27.4-9
27.4-10
Options
Default
None
None
0 24 alphanumeric
characters
None
Accounting Activation
Yes
No
No
Yes
No
No
Hot Billing
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
Default NUA
Yes
No
Yes
No
No
Yes
No
No
Redirection Address
None
Signal CRN
Yes
No
Yes
Signal CLAMN
Yes
No
Yes
Call Deflection
Yes
No
No
NUI Subscription
Yes
No
No
(400)
X.25 Service
Parameter
X.25 Service
Options
Default
Yes
No
Yes
Standard
Non Standard
Non Standard
IA5
BCD
IA5
NUI Password
NUI
1 21
CUG Index
0 99
None
Interlock Code
0 65 535
None
Barring
No Barring
Preferential CUG
Yes
No
No
Yes
No
No
Yes
No
No
Yes
No
No
128 bytes
1 7 (modulo 8)
1 127 (modulo 128)
64 000 b/s
(400)
27.4-11
Options
Default
Local Address
None
Local LCN
1 to 4095
None
Remote Address
None
Remote LCN
1 to 4095
None
Accounting Activation
Yes
No
No
Yes
No
No
D-Bit Allowed
Yes
No
No
128 bytes
1 to 127
64 000 b/s
Originating End
Local
Remote
27.4-12
Options
Default
None
Redirection Address
None
None
(400)
X.25 Service
27.5
27.5.1
27.5.2
X.25 Service
(400)
27.5-1
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Global Parameters
----------------Number of
--------XACs
Maximum
------:128
Highest In Use
-------------:112
Trunk Circuits
:128
:64
F2-TRUNK_CCTS
F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-PROCEED
27.5-2
(400)
X.25 Serivce
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
Global Resources
---------------Number of
Maximum
----------------PEs pr Network
:1024
NUAs
:512
CUGs
:5120
ICUGs
:2048
Hunt Groups
:64
Address Translations
:2560
Configured LCN Pages
:4096
Aliases
:3
Accounting Record Intervals
:2
Collection Intervals per Intermediate
Intermediate Record
:4
Configured PVCs
--CUGs per NUA
:20
Members per Hunt Group
:16
8:35a
In Use
-----:3
:85
:100
:100
:8
:43
:127
:3
:2
:1
:12
F2F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
X.25 Service
Description
Number of NUAs
Number of CUGs
(400)
27.5-3
Field Name
Description
Number of Aliases
27.5.3
Number of XACs
This parameter specifies the maximum number of XACs supported by the switch.
This includes XACs for subrate, basic rate, and super-rate X.25 access lines. The
value cannot be set lower than the value displayed in the Highest In Use field.
Range
1 to 128 for X.25 FRE cards
1 to 512 for PE cards
Default
128
27.5-4
(400)
X.25 Serivce
XACS
TRUNK_CCTS
<xac>
<trunk_cct>
SK000403
where
xac is 1 to 512 for PE cards and 1 to 128 for X.25 FRE cards, 128*
trunk_cct is 1 to 128 (128* for PE cards and 32* for X.25 FRE cards)
X.25 Service
(400)
27.5-5
27.6
GFR Configuration
This chapter describes how to configure the GFR parameters to enable the operation
of the connectionless routing system. These parameters specify how a 36120
MainStreet X.25 switch routes frames to, and receives frames from, other switches
across the backbone network.
This chapter does not describe the X.25 call routing process. For information about
how X.25 calls are established using destination addresses, see chapter 25.7.
27.6.1
X.25 Service
(400)
27.6-1
10-10
10-11
10-12
10-13
7527
Hub domains
The hub domain is the upper level of the routing hierarchy and is made up of
1 to 245 hub switches interconnected by trunks that may or may not be fully
meshed. The hub domain interconnects all of the leaf domains. Figure 27.6-2 shows
an example of X.25 switches organized into domains.
27.6-2
(400)
X.25 Serivce
Leaf Domain
PE
PE
PE
PE
FRS
PE
FRS
PE
Leaf Domain
Hub
Domain
PE
PE
PE
Leaf Domain
FRS
PE
FRS
PE
PE
PE
PE
PE
PE
Hub switch
PE
PE
FRS
FRS
FRS
PE
Leaf switch
FRS
FRS
Leaf
Domain
FRS
Feeder switch
7519
The topology of large networks can be designed with a combination of direct link
and dynamic routing sectors in the hub domain. The hub domain may thus be
divided into two tiers. These consist of a dynamic routing core and clusters of feeder
hubs employing direct link routing. These, with the leaf domain, form a three-tier
routing topology.
The dynamic routing sector is a core of hubs which need not be fully meshed. The
direct link routing sector is made up of hub clusters. Each hub in a cluster is directly
linked to a switch in the hub domain dynamic routing sector. In this three-tier
topology, shown in Figure 27.6-3, there are leaves, direct link hub clusters and
dynamic hubs. In the diagram, the hubs and leaves are all shown as X.25 PE switches
but may also be X.25 FRE switches. The shaded hubs are in directly linked clusters
and the dynamic routing hubs are unshaded.
This topology significantly reduces dynamic routing network overhead while still
offering the advantages of dynamic routing in the network core.
X.25 Service
(400)
27.6-3
11
Hub
cluster
PE
PE
PE
PE
Leaf
domain
PE
PE
A
PE 02
Dynamic
routing
sector
05
E
PE 04
PE
Leaf
domain
PE
PE
Direct link
routing sector
Hub domain
01
PE
PE
Hub
cluster
F
PE
PE
PE
Leaf
PE
domain
PE
PE
Three tier network with dynamic
routing hubs and fully meshed hub
clusters serving the leaf domains
PE Leafs
PE
Hub 21
cluster
27.6-4
(400)
X.25 Serivce
10-10
11-11
10-11
11-10
10-15
11-12
10-11
10-11
10-14
11-13
10-13
10-12
11-15
11-14
7528
Leaf domains are mainly used for routing traffic within a collection of switches
collocated on a 3600 MainStreet network. Routing between hub switches is
appropriate for traffic destined for remote switches across the backbone network.
X.25 Service
(400)
27.6-5
PE
PE
PE
PE
PE
PE
PE
PE
PE
PE
Because switch access is not dependent on fully meshed trunks, the number of hub
nodes in a network hub domain can be increased without consuming a large number
of frame relay PVC connection resources on a switch.
27.6-6
(400)
X.25 Serivce
The major advantages of dynamic routing are trunk economy, scaling and
instantaneous rerouting. However, there is a compromise between these advantages
and the increase in network traffic overhead caused by the distribution of dynamic
routing status updates. When topology status changes occur, all the dynamic
routing hubs in the network broadcast the new routing data. In addition, each
dynamic routing hub periodically broadcasts its entire topology status database. The
size of the dynamic routing hub domain also has an effect on GFR memory
resources.
GFR addresses
As part of the initial commissioning process, the network operator assigns a hub
number and a leaf number to every switch in a 36120 MainStreet X.25 network. This
pair of numbers, called the GFR address, identifies the switch as a hub switch or a
leaf switch and provides it with a unique routing address in the network.
Hub switches have hub numbers from 10 to 255 and leaf number 0; for example
110-0. Leaf switches have hub numbers from 10 to 255 and leaf numbers 10 to 255;
for example, 110-55.
When packets are routed between switches, the originating switch adds a routing
header to each packet. This routing header contains the GFR address that identifies
the switch to which the packet is destined. Once a call is established, this routing
header is added to every packet associated with that call, allowing each packet to be
routed independently through the network.
Aliases
Hub switches can be configured to re-route packets to and from leaf domains other
than their own. An alias is a GFR address that a hub switch assumes in order to route
traffic for another hub switch.
When a particular hub is out of service or is unreachable, the forwarding switch
routes frames to the alias instead. The alias switch then attempts to forward the
frames to their destination. This is achieved using alias GFR addresses.
Only hub switches can be aliases. You configure an alias in the same format as a GFR
address, but the ranges are:
X.25 Service
(400)
27.6-7
Hub switch 120-00 is configured as an alias for switch 100-00 using alias 100-01.
This means that if switch 100-00 fails, switch 120-00 performs the task of routing
packets to and from the leaf switches in domain 100. Note that every leaf switch
has direct trunks to both its hub switch and the alias hub switch.
Hub switch 100-00 is configured as an alias for switches 120-00 and 131-00 using
aliases 120-01 and 131-01, respectively. This means that if either switch 120-00 or
131-00 fails, switch 100-00 performs the task of routing packets to and from the
leaf switches in domains 120 and 131.
Due to the GFR forwarding rules, switch 100-00 will always be used to route
frames from 120-10 and 120-11 to leaf nodes in leaf domain 131-00 (for example,
leaf 131-10).
Figure 27.6-6: Redundant Network Topology
110-10
131-10
110-00
(120-02)
120-10
120-11
131-00
120-00
100-00
(100-01)
(110-01)
(131-01)
(120-01)
100-10
100-11
131-11
100-12
100-13
7518
Load balancing
The GFR can load balance over two or three trunks between two switches. However,
load balancing should not be permitted over routes that include intermediate hops.
Furthermore, GFR load balancing is not performed over alias switches if the normal
route is functional.
Load balancing is a network wide feature. It is the network operators responsibility
to decide whether or not to employ load balancing. When enabled, every switch in
the network must be configured for load balancing, even though it is ineffective on
routes with only one trunk.
The GFR splits the traffic when the cost difference between alternate routes is less
than or equal to a configurable parameter, delta (D).
27.6-8
(400)
X.25 Serivce
Splitting traffic by using load balancing means that frames from a given call follow
different paths to the destination. Because of possible unequal delays on the
different routes, frames may arrive at the receiving switch out of sequence. The RTP
buffers frames while it waits for delayed frames to arrive. The greater the difference
between delays on different routes, the more buffering is required to re-sequence the
frames. Hence, load balancing is most efficient when the network is engineered so
that frames belonging to one call are transmitted on identical or very similar trunks.
Load balancing is intended for use on parallel trunks between two switches.
27.6.2
Route builder
The route builder uses direct link and dynamic routing algorithms to build a
forwarding table that is later used to forward frames during data switching. The
route builder uses a least-cost algorithm in selecting the best routes when generating
the forwarding table. This lists available trunks to all connected destinations
through adjacent switches, together with their associated costs. Once established,
the forwarding table changes only when trunk status or topology changes occur.
In the hub domain dynamic routing sector, GFRs use a link state routing protocol to
exchange topology information with each other. This information is used to build a
link state database that describes the entire dynamic routing topology. A link state
database is built on every dynamic routing switch.
X.25 Service
(400)
27.6-9
On hubs configured for dynamic routing, the topology information includes data
relating to all the dynamic routing hubs in the network. The constructed routing
tables are maps of the entire dynamic routing domain. They contain first choice and
up to two alternate choices of trunk for all reachable destinations. Dynamic routing
tables are amended when topology changes occur. Such changes include the
addition or removal of trunks and switches, switch or trunk failures and the
resumption of operations when faults have been rectified. Dynamic routing status
changes are not broadcast to hub clusters. This means that the exchange of routing
status changes can be confined to the dynamic routing sector.
In the case of a local trunk failure, the forwarding table is updated immediately by
the route builder. Routes are also re-calculated immediately and the status change
distributed to the other switches.
When a switch receives a dynamic routing status update from another dynamic
routing switch, it updates its own forwarding table immediately.
Debouncing is applied to bursts of status updates to prevent excessive updates being
exchanged.
Forwarding function
The forwarding function uses the forwarding table, constructed by the route builder
to check the frame routing header for the destination GFR address and forwards the
frame to the appropriate trunk circuit. The route builder updates the forwarding
tables when link state or topology changes occur in the network.
The complex routing calculations are performed off-line by the route builder. The
forwarding table is the result of these calculations. Thus forwarding becomes a
highly efficient operation which takes place in the data path.
Forwarding functions on source and destination switches perform frame relay
encapsulation and decapsulation. Forwarding functions on intermediate switches
transmit the frames between the consecutive trunks. The forwarding function on a
destination switch detects that the frame is addressed to its own GFR address and
delivers the frame to X.25 running on this switch.
27.6-10
(400)
X.25 Serivce
Red
Time
to live
0
EA
0
EA
Data Link
Connection
Identifier
(DLCI)
DE
Flag
1 1
BECN
FR type FECN
C/R
Application
Destination
Hub #
GFR header
Destination
Leaf #
FR type
FECN
BECN
Spare
Spare Remote
RTP header
VCon ID
GFI
Q D 0
LC group
number
LCN
X.25 packet
P(R)
P(S)
User data
(variable)
Q.2110
SD
RTP trailer
PDU
TI.618 Frame
Check Sequence
8673
X.25 Service
(400)
27.6-11
27.6-12
(400)
X.25 Serivce
30-10
3
Hub
40-0
Hub
30-0
30-11
Trunk ID
Trunk cost
1
20-10
Hub 2
20-0 3
4
1
1
4
Hub
2 10-0 5
7
6
1
10-nn
10-12
20-11
10-10
1
10-11
10432
Trunk
Cost
Load
Balancing
!st choice
Alternate Routes
2nd Choice
Cost
3rd Choice
Cost
10-10
T7
No
10-11
T6
No
10-12
T5
No
10-nn
T4
No
20-0
T2
Yes
T1
T3
30-0
T3
Yes
T2
T1
40-0
T2
Yes
T1
T3
Forwarding principles
The forwarding principles encompass routing system characteristics and specific
forwarding rules.
X.25 Service
(400)
27.6-13
The GFR always selects the lowest cost route according to the costs assigned to
the trunks which make up the route and the transit costs of switches on the route.
Frames can be forwarded a maximum of seven times.
Hub switches perform routing within and between leaf domains. Leaf number 0
identifies the actual hub switch, while leaf numbers 1 to 9 identify the hub switch
aliases.
Only hub switches can function as transit switches. Leaf switches can only route
traffic they originate, as well as retransmitting reversed frames.
When forwarding frames the GFR applies the rules detailed below. The GFR applies
the rules in ascending order. For example, if Rule 1 cannot be applied, the GFR
attempts to apply Rule 2.
Although the route selection process is performed for each frame, frames
transmitted between two switches normally follow the same path, except when load
balancing is enabled. In the absence of load balancing, the transmission path changes
only when the network topology changes, a trunk failure occurs, or a node goes out
of service. When load balancing is enabled, X.25 packets associated with the same
virtual call may be transmitted over different backbone trunks to their destination.
Direct link forwarding rules
The following forwarding rules are applied for direct link routing.
1. Select the lowest cost trunk directly connected to the destination switch.
2. Select the lowest cost trunk to the hub of the destination leaf switch.
3. Select the lowest cost trunk to the alias with the lowest leaf number for the
destination leaf domain.
4. If the source switch is a leaf switch, forward the frames on the lowest cost trunk
to its own hub switch.
If the switch is a hub switch, other than the destination hub switch, forward the
frames on the lowest cost trunk to a hub switch participating in dynamic routing.
5. Select the lowest cost trunk to the alias of the forwarding hub switch.
Hub domain dynamic routing forwarding rules
The following forwarding rules are applied for hub domain dynamic routing.
1. Select the lowest cost trunk connected to the destination leaf switch.
2. Select the lowest cost route to the hub of the destination leaf domain.
3. Select the lowest cost route to the alias with the lowest leaf number for the
destination leaf domain.
4. Select the lowest cost route to the alias of the forwarding hub switch.
27.6-14
(400)
X.25 Serivce
Redundant routing
Routing redundancy is achieved by providing alternative routes or by reversing
frames when they cannot be forwarded, thus routing around out of service switches
or trunks.
Redundant routing principles
To provide redundancy in network routing, alternate paths must be available
between switches. The three methods of providing redundancy are listed below.
Trunk redundancy
The GFR also provides a redundant routing function that physically reverses frames.
Frame reversal
The GFR provides a routing redundancy mechanism that physically reverses frames
when routes to a particular switch are not available.
Frame reversal occurs when a hub switch cannot find a route to the destination
switch because of a trunk failure or an out-of-service node. This GFR sends the frame
back along the trunk to the previous switch and sets a redundancy flag. A reversed
frame can only be returned along the trunk on which it was received, since the
switch has no record of the origin for the frame.
When a switch receives a reversed frame with the redundancy bit set, it attempts to
find a route to the destination switch other than the trunk to the switch which
reversed the frame. If an alternative route is available, the GFR resets the
redundancy bit and forwards the frame. If no alternative route is available, the
switch discards the frame. A frame may transmitted up to seven times, after which
it is discarded. This implies that a frame may only be reversed three times before it
is discarded.
Figure 27.6-9 shows an example of frames that are successfully routed to the
destination switch using frame reversal.
X.25 Service
(400)
27.6-15
10-10
10-0
12-0
12-0
3
4
1
2
3
4
5
Forwarding rule 2
Forwarding rule 2
Redundant forwarding rule 1
Forwarding rule 3
Forwarding rule 1
14-0
(12-1)
10430
27.6-16
(400)
X.25 Serivce
27.6.3
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
GFR PARAMETERS
-------------GFR Address
:23-0
Redundant Routing
:Disabled
Load Balancing
:Disabled
Hub Domain Dynamic Routing :No
Delta Value
:0
List of Aliases
:90-2
80-1
12-7
F2-ROUTING
F7-
F3-ALIAS
F8-CANCEL
F4-FASTBUS
F9-QUIT
F5F10-PROCEED
27.6.4
GFR address
You must assign a GFR address to every 36120 MainStreet X.25 switch. The GFR
address designates the switch as a hub or leaf switch and provides it with a unique
routing address in the network. The hub number identifies the switch as a member
of a particular leaf domain, while the leaf number identifies the switch as either a
hub or leaf switch in that domain.
A hub switch has a hub number from 10 to 255, and a leaf number as 0; for example,
110-0. A leaf switch has a hub number from 10 to 255 and a leaf number from 10 to
255, for example, 110-11.
X.25 Service
(400)
27.6-17
Caution
When you change the value of this parameter, the switch resets and rebuilds the
routing table, during which time all trunks are out of service. Once the switch is
operational, change the value only during periods of minimal network activity.
Range
Table 27.6-2 summarizes the allowable values for configuring GFR addresses.
Table 27.6-2: GFR Address Assignment
Hub Switch
Leaf Switch
10 to 255
10 to 255
10 to 255
Default
None
Redundant routing
This parameter specifies whether the GFR on the card performs frame reversal
during routing. When redundant routing is enabled, the GFR physically reverses
those frames that cannot be forwarded due to a trunk failure or an out-of-service
switch. A reversed frame returns to the last switch from which it came, where the
GFR attempts to find an alternate route to the destination switch. If no alternate
route is available, the switch discards the frame.
Caution
When you change the value of this parameter, the switch rebuilds the routing table,
during which time all trunks are out of service.
Options
Enabled or Disabled
Default
Disabled
27.6-18
(400)
X.25 Serivce
Load balancing
Trunk loads can be balanced using the load balancing techniques. It is a cost effective
method of bandwidth utilization when there are two or three parallel routes
between switches.
Caution
The decision to use a load balancing topology should be carefully considered for the
following reasons:
To employ load balancing, it must be enabled on every switch across the entire
network.
It may adversely affect RTP performance on non-load balanced links by delaying
retransmission requests when frame loss occurs.
If load balancing is employed on parallel GFR trunks of unequal speeds,
transmission delays on the slower trunk may degrade performance by causing
excessive RTP retransmission requests.
Options
Enabled or Disabled
Default
Disabled
Options
Yes or No
Default
No
X.25 Service
(400)
27.6-19
Delta value
The Delta Value (D) is a management device which prevents the GFR from using
unacceptable alternative routes. Network operators can restrict balancing on certain
routes based on trunk cost aggregates. The D value is the maximum aggregate cost
difference permitted between two alternative routes used for load balancing. A
route may be utilized if its cost does not exceed the preferred route cost plus the D
value.
For example assume a destination can be reached by a preferred route and two
alternatives. The first choice route cost is 5, the second choice route cost is 7 and the
third choice route cost is 8. A D value of 2 allows the first choice and second choice
routes to be used but precludes the use of the third choice.
Range
0 to 255
Default
0
List of aliases
An alias is a GFR address that a hub switch assumes in order to route traffic on
behalf of another hub switch. Each alias is an alternate GFR address for another hub
switch.
Only hub switches can be assigned aliases. Assigning an alias is similar to assigning
a GFR address but the leaf number must be from 1 to 9.
Cards functioning as hub switches can have a maximum of three aliases. This means
a switch can assume the task of routing traffic in four different leaf domains,
including its own.
Caution
When you add or delete an alias, the GFR rebuilds the routing table, during which
time all trunks are out of service.
Range
Table 27.6-3 summarizes the allowable values for configuring aliases.
27.6-20
(400)
X.25 Serivce
Alias Format
Hub Number Range
PE
10 to 255
1 to 9
X.25 FRE
10 to 255
1 to 9
Default
None
X.25 Service
(400)
27.6-21
Redundant routing
Aliases
Hub domain dynamic routing
Configuring a GFR for dynamic routing increases the network overhead when
trunks state changes occur.
Configuring the network for load balancing may degrade the performance of
non-load balanced routes when frames are dropped.
You can change the values of the following parameters at any time with no
disruption of service. The changes are effective immediately.
27.6-22
Rate Enforcement
Aggregate CIR
Aggregate Bc
Transit cost
Delta cost
(400)
X.25 Serivce
GFR_ADDR
ROUTING
ALIAS
FASTBUS
<hub-leaf>
ADD
DELETE
<alias_id>
DELTA REDUNDANCY
LOAD_BAL
<delta>
ENABLED/DISABLED
CIR
BC
<cir>
<bc>
RATE_ENF
ENABLED/DISABLED
SK000404
where
hub-leaf is the GFR address in the format nnn-nnn
delta is 0 to 256
alias_id is alias for the hub in the format nnn-n
cir is 0* to 8 Mb/s
bc is 0* to 40 Mb
X.25 Service
(400)
27.6-23
27.7
Call Routing
This chapter describes how to configure the call routing functionality for a 36120
MainStreet X.25 switch.
For information about configuring the connectionless routing system on the switch,
see chapter 27.6.
27.7.1
A network can support both E.164 and X.121 address formats simultaneously.
Calls can be made to the network using either of the address formats.
Multiple networks can share the same X.121 DNIC. The digits following the
A 36120 MainStreet X.25 network supports three variations of call routing: basic
routing, gateway and network-wide hunt group routing. The GAT configured on
the switch determines which type is used for each call.
Address Prefix
GFR Address
XAC
Type
Priority
Weight
Link Status
The network operator configures the GAT on every 36120 MainStreet X.25 switch
manually or by using the MainStreetXpress 46020 Network Manager. The GATs
must be identical on all switches in a network.
X.25 Service
(400)
27.7-1
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
F5F10-
Every entry in the GAT has an address prefix, a GFR address, and address prefix
type. The address prefix type field determines whether the switch uses the basic
routing, hunt group or gateway routing method to route calls. If the address prefix
type is X.25, the switch uses basic routing. If the address prefix type is X.25 gateway,
X.75 gateway or hunt group, gateway routing is used. Gateway routing requires that
an XAC be specified in the GAT entry. An XAC configured as an X.25 or X.75
gateway can have multiple address prefixes associated with it, but only one NUA.
Address prefixes and GFR addresses
Address prefixes are variable-length strings that consist of the first n digits of a range
of addresses. In the case of basic routing, the GAT maps each address prefix to a GFR
address that represents the destination switch for addresses that match the address
prefix. For each gateway address prefix, the GAT contains the set of GFR addresses
and XAC number that support the specified address prefix. The number of address
prefixes required depends on the size of the network.
When an originating X.25 switch routes a call, the switch selects the address prefix
that most closely matches the called address, and forwards the Incoming Call packet
to the switch with the corresponding GFR address. This can be the local switch or a
remote switch. While address prefixes can overlap, the switch always chooses the
address prefix that matches the largest number of digits in the called address.
Address prefixes can be configured for multiple routing. Each route has an
associated address prefix type, priority and weight that are used to determine the
call path. For every call, the priority and weight of each available destination link
address prefix is evaluated to select the next route.
27.7-2
(400)
X.25 Serivce
Address prefixes are entered in the GAT in X.121 international data number format
(DNIC+NTN) or E.164 international telephony number format (CC+NSN), and are
1 to 19 digits in length. Because a called address is processed according to the
address translation table for the XAC before it is sent to the GAT, the switch always
searches the GAT using the internal address format. See section 27.14.9 for
information about the address translation table and internal address formats.
The entries in the GAT are sorted in ascending numerical order by the address prefix
and GFR address respectively.
The following GAT example shows the use of address prefixes and GFR addresses:
all calls destined for addresses beginning with 1234 are routed to switch 15-11, with
the exception of calls to addresses beginning with 12345, which are routed to switch
15-22.
GLOBAL ADDRESS TABLE
Address Prefix
GFR Address
XAC
Type
Priority
Weight
----------x1234
15-11
X.25
---
---
x12345
15-22
X.25
---
---
GFR Address
XAC
Type
Priority
Weight
-----------
X.25 Service
x1234?
15-11
X.25
---
---
x12345
15-22
X.25
---
---
(400)
27.7-3
In the example below, all calls destined for addresses beginning with 1111 are routed
to switch 15-31, while addresses 1011, 1211, 1311,...1911 are routed to switch 15-42.
GLOBAL ADDRESS TABLE
Address Prefix
GFR Address
XAC
Type
Priority
Weight
----------x1111
15-31
X.25
---
---
x1?11
15-42
X.25
---
---
In the example below, all calls destined to addresses beginning with 444 are routed
to switch 15-17, while all other addresses beginning with 44 are routed to switch
10-11.
GLOBAL ADDRESS TABLE
Address Prefix
GFR Address
XAC
Type
Priority
Weight
-----------x44?
10-11
X.25
---
---
x444?
15-17
X.25
---
---
27.7-4
(400)
X.25 Serivce
GFR Address
XAC
Type
Priority
Weight
-----------x3110
10-10
X.25
---
---
x1000
10-10
15
X.75
x2000
10-10
15
X.75
x3000
10-10
15
X.75
x4000
10-10
15
X.75
Network
P
x3000
Network
X
Network
Y
x3110
Network
Q
x4000
x2000
Network
R
x1000
9477
The GAT at the gateway switch for network X is configured such that calls to
networks Y, P, Q and R are routed to XAC 15, which supports link A.
Priorities and weights
The use of priorities and weights enables load sharing, redundancy and link
prioritization in gateway routing. When the same address prefix is assigned to
multiple links, the switch uses the configured priorities and weights to determine
the route.
X.25 Service
(400)
27.7-5
When duplicate address prefixes are configured in the GAT, the switch selects the
preferred route in the following order.
Network
D
Network
C
Network
B
Network
A
(Newbridge)
Priority 2
Priority 1
(low cost route)
9454
The weight field is used to specify the relative number of calls routed to links with
the same priority. The switch supports weights ranging from 1 to 15, where the
higher the number, the greater the number of calls on the link. The weight field has
significance only when two or more links support the same address prefix and have
the same priority. For example, if links A and B are both priority 1 links for address
prefix 2045, and the weights are 2 and 1 respectively, link A receives two calls for
every one call routed to link B; however, if link A has a priority of 1 and link B has a
priority of 2, the weight field has no significance.
Table 27.7-1 shows how weights work. Links A, C and D are the preferred links for
address prefix 3022; links B and E are used only if all the preferred links are
unavailable. The weight field specifies how calls are distributed across the preferred
links: for every ten calls routed to address prefix 3022, six calls go to link A, three
calls go to link C and one call goes to link D. Link A receives calls 1, 4, 6, 8, 9 and 10;
link C receives calls 2, 5 and 7; and link D receives call 3. The eleventh call is sent to
link A and the cycle repeats.
27.7-6
(400)
X.25 Serivce
Address Prefix
Priority
Weight
Comments
x3022
x3022
x3022
x3022
x3022
Load sharing
Figure 27.7-4 shows an example of load sharing using weights. The GAT at the
gateway switch for network X is configured as follows.
GLOBAL ADDRESS TABLE
Address Prefix
GFR Address
XAC
Type
Priority
Weight
----------x3110
10-0
X.25
---
---
x3115
10-0
11
X.75
x3115
10-0
22
X.75
XAC 11 supports link A and XAC 22 supports link B. While both links have equal
priorities (1), they have different weights (2 and 1 respectively). When calls are
established from network X to network Y, both links are used, but link A receives
twice as many calls as link B.
Figure 27.7-4: Load Sharing Using Different Weights
Network
X
x3110
Network
Y
x3115
9476
X.25 Service
(400)
27.7-7
Link redundancy
Figure 27.7-5 shows how link redundancy is used with X.75 gateways to route traffic
across a primary transit network, while using a secondary transit network for
backup. The GAT at the gateway switch for network W is configured as follows (the
links supported by the XACs are shown in parentheses).
GLOBAL ADDRESS TABLE
Address Prefix
GFR Address
XAC
Type
Priority
Weight
-----------x3020
20-0
x3022
20-0
x3022
X.25
---
---
10 (A)
X.75
20-0
20 (B)
X.75
x4204
20-0
10 (A)
X.75
x4204
20-0
20 (B)
X.75
x4624
20-0
10 (A)
X.75
x4624
20-0
20 (B)
X.75
The links configured as priority 1 receive all internetwork calls unless the links fail,
in which case priority 2 links are used. Using this configuration, network W has
redundant routes to networks X, Z and Y. Link A is used for all calls to networks X
and Z, and as a backup to network Y. Link B is used for all calls to network Y, and
as a backup to networks X and Z.
Figure 27.7-5: Route Redundancy Using Priorities
Network
Z
x4624
C
Network
X
x3022
Network
Y
x4204
A
Network
W
x3020
9274
27.7-8
(400)
X.25 Serivce
Normally, calls are routed according to the priorities and weights assigned to links:
higher priority links are preferred, and calls are distributed to links of the same
priority based on weights. However, if a link is out of service, information is sent to
each switch indicating that the link is down, and the originating switches select the
next best route.
Calls may be routed to a link that is out of service. This can occur if an originating
switch routes a call to link for which it has not yet received an out-of-service status
indication, the selected link is under flow control, or all LCNs on the link are in use.
In these cases, the destination switch clears the call back to the originating switch,
and the originating switch attempts to reroute the call to a maximum of two
alternative links. This re-routing process is transparent to the network user; the X.25
DTEs do not receive call clears. The link status can be either up or down and is
displayed on the GAT screen on the NMTI.
A status change has to remain in effect for a minimum period of time before it is
distributed to other switches. This is achieved by status filtering at the local switch.
This is to avoid flooding the network with update messages when a link frequently
goes in and out of service.
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NUA
XAC
NUA
XAC
NUA
XAC
---------------------------------------------------------------------------------x302011888801
10
x30201187277960 160
x302011888811
23
x30201187277961 161
x302011888822
25
x30201187277962 162
x302011888833
26
x30201187277963 163
x302011888844
27
x30201187277964 164
x302011888855
28
x302011888866
29
x302011888872
33
x302011888873
35
x302011888875
37
x302011888878
39
CONFIG X25_ACCESS NUA "??"
Enter network user address. ([npi]nnn...)
F1-PREVIOUS
F2-NEXT
F3F6F7F8-CANCEL
X.25 Service
(400)
F4F9-QUIT
F5F10-
27.7-9
The LAT is built dynamically when NUAs are assigned to XACs (see chapter 27.15).
The LAT can contain full or partial addresses. In most cases, the full address of the
user device is defined and assigned to the XAC. However, partial addresses allow
network operators to use the basic routing process, rather than the gateway routing
process, to route calls to X.25 gateway links. In such cases, the network is configured
to route X.25 gateway calls exactly like DTE-to-DTE calls. At the XAC that serves as
the gateway interface, a partial address is used, since it may be impossible to define
every possible called address on the interface. The partial address, similar to the
address prefix used in the GAT, allows the switch to route gateway calls
appropriately.
The following example of a LAT shows a routing scenario where two X.25 gateway
links are configured on the switch. All calls destined for remote network addresses
beginning with 3020111 are routed to XAC 17, while all calls to addresses beginning
with 3020222 are routed to XAC 39.
LOCAL ADDRESS TABLE
NUA
XAC
NUA
XAC
--------------------------------------------------------x3020111
17
x3020222
39
Note
The LAT is never used by the gateway routing process. Both the originating and
destination switches use the GAT exclusively to perform gateway routing.
27.7.2
Basic Routing
Basic routing occurs as follows at the originating and destination switches.
1. The originating switch matches the called address to an entry in the GAT,
determines the destination switch, and routes the Call Request packet
accordingly. This is referred to as remote switching.
2. The destination switch matches the called address to an entry in the LAT,
determines the destination access line, and routes the Incoming Call packet
accordingly. This is referred to as local switching.
27.7-10
(400)
X.25 Serivce
With basic routing, GAT consultation occurs only at originating switches, while LAT
consultation occurs only at destination switches. For calls that originate and
terminate on the same X.25 switch, the two tables are consulted locally before the
calls are routed to the appropriate X.25 access line. Alternatively, calls that originate
and terminate on different X.25 switches are routed over backbone trunks (GFR
trunks), and may traverse several intermediate switches before reaching the
destination switch where they are locally switched.
The basic routing mechanism is used to route calls to switch-wide hunt groups. Once
the LAT has been consulted and it has been determined that the called address refers
to a switch-wide hunt group, the appropriate member is selected. Calls are allocated
to switch-wide hunt group members in a round-robin fashion.
X.25 Service
(400)
27.7-11
27.7-12
(400)
X.25 Serivce
Figure 27.7-7 shows the call routing logic that is common to both basic and gateway
routing at the originating switch; these activities occur before the switch determines
whether to use basic or gateway routing. Figures 27.7-8 and 27.7-9 show the
subsequent basic routing logic at the originating and destination switches.
Figure 27.7-7: Call Routing Process at the Originating Switch: Basic and Gateway
START
Address translation
YES
NO
Process facilities/utilities
NO
YES
Gateway
routing required?
NO
B1
YES
C
9455
X.25 Service
(400)
27.7-13
B1
YES
NO
Route available to
remote switch?
Called address
in LAT?
YES
NO
NO
YES
Send/process
Incoming
Call packet
B2
9461
27.7-14
(400)
X.25 Serivce
NO
DTE link down,
busy or line refused?
B2
YES
Get next member
YES
Member found?
NO
NO
YES
Maximum
redirections exceeded?
YES
Call redirection
configured?
NO
Clear call
YES
Insert facilities/utilities
Address translation
Convert address to
external format
END
9456
X.25 Service
(400)
27.7-15
27.7.3
Gateway Routing
The 36120 MainStreet X.25 gateway routing feature provides versatile and flexible
routing and addressing capabilities.
Multiple X.75 gateways with the same address prefix within a network can be
27.7-16
(400)
X.25 Serivce
DNIC = 3110
Public network
C
DNIC = 3115
Public network
D
X.75
X.75
DNIC = 6550
Newbridge public
network
A
X.35
DNIC = 655040
Private network
E
X.75
X.35
DNIC = 65501/3
Private network
B
X.75
DNIC = 65502
Private network
F
9161
In the case where two networks share the same DNIC value and use X.75 for
interconnection, the user can specify that the TNIC should not be inserted in transit
calls. This scenario is shown in Figure 27.7-11.
X.25 Service
(400)
27.7-17
Figure 27.7-11: Network Migration Scenario Using Networks with Shared DNICs
Network C
TNIC = 3410
Network D
TNIC = 2440
Network A
X.75
X.75
TNIC = 2310
Newbridge network
Does not insert TNIC
in transit calls
X.75
Network B
TNIC = 2310
9188
Figure 27.7-12 shows how priorities and weights provide load sharing and
redundancy for X.75 gateway links.
DTEs in network A need to call DTEs in the network D. Network A has two switches
(FRE 1 and FRE 2) with X.75 gateway links. FRE 1 has direct links to networks B and
C, and address prefix 3115 is configured on both links. The link from FRE 1 to
network B has a lower priority than the link from FRE 1 to network C, because the
route from network B to network D has more transit networks.
The two links on FRE 2 have the same priority, but the direct link to network D has
a higher weight. As a result, when calls are made from DTE X to DTE Y, 3 calls are
routed to FRE 2 for every one call that is routed to FRE 1. The priority 2 link on FRE
1 will only be used if all three priority 1 links are down or unavailable.
27.7-18
(400)
X.25 Serivce
Network C
DNIC = 3110
Network D
DNIC = 3115
X.75
X.75
Network B
DNIC = 2440
X.75
wt =1
pr =1
DTE Y
X.25
X.75
wt =1
pr =1
wt =2
pr =1
X.75
wt =1
pr =2
X.75
FRE 1
FRE 2
FRE 3
Network A
DNIC = 6550
DTE X
wt = weight
pr = priority
9160
X.25 Service
(400)
27.7-19
Retrying calls
Gateway routing enables calls in the connecting state to be retried when a clear
packet is received at the destination switch. Calls are retried when the switch selects
a route that is unavailable (for example, when the ATB status update is delayed so
that the switch is unaware the link is down), and one of the following conditions
applies:
27.7-20
(400)
X.25 Serivce
X.25 Service
(400)
27.7-21
27.7-22
(400)
X.25 Serivce
C
NO
Entry found?
YES
YES
YES
YES
Clear call
Remote link?
NO
Address translation
Convert address to
external format
Send/process Incoming
Call packet
D
9458
X.25 Service
(400)
27.7-23
D
NO
Entry found?
YES
YES
Link down,
busy or line refused?
NO
YES
Address translation
Convert address to
external format
Send Incoming
Call packet to X.25/X.75 link
END
9457
27.7-24
(400)
X.25 Serivce
YES
From a DTE?
NO
Hunt group call?
NO
YES
YES
YES
From an X.25 or
or X.75 gateway?
Received at originating
switch?
NO
NO
D
Clear
call
END
NO
Clear
call
Retry or reroute
call?
YES
END
C
9460
27.7.4
<hub-leaf>
SHOW_ALL
SHOW_GROUP
SK000405
X.25 Service
(400)
27.7-25
<nua>
SHOW_ALL
SHOW_GROUP
SK000406
27.7.5
Address prefix
This field defines a string of address digits for which the GAT entry applies. When
the switch consults the GAT, it compares the called address to the address prefixes
and selects the closest match.
An address prefix can be entered multiple times in the GAT if the address prefix type
is X.25 Gateway, X.75 Gateway or Hunt Group and the combination of the GFR
address and XAC number is different for each instance of the address prefix.
Address prefixes with the X.25 address prefix type cannot have multiple entries in
the GAT.
Range
1 to 19 digits or wildcards in international X.121 or E.164 address format
Default
None
27.7-26
(400)
X.25 Serivce
GFR address
This field specifies the GFR address of the switch that supports the corresponding
address prefix. A call is routed to this GFR address when the called address matches
the address prefix. A GFR address can be entered multiple times in the GAT.
Range
hub-leaf in the format nnn-nnn
Default
None
XAC
This field specifies the XAC to which a call is routed when the called address
matches the address prefix. This parameter is not configurable for entries that are
configured with the X.25 address prefix type, because the LAT on the destination
switch specifies the XAC used to route the call. For address prefix types other than
X.25, an XAC must be defined because LATs are not used for gateway routing and
the various XACs supporting the address prefix must be identified.
Range
0 to 128 for X.25 FRE cards
0 to 512 for PE cards
Default
None
Type
This field specifies the address prefix type that applies to the corresponding address
prefix. If the address prefix type is X.25, the switch uses basic routing. If the address
prefix type is X.25 gateway, X.75 gateway or hunt group, the switch uses gateway
routing and tries to route calls to the specified XAC.
Options
X.25, X.25 Gateway, X.75 Gateway, Hunt Group
Default
None
X.25 Service
(400)
27.7-27
Priority
This field specifies the priority assigned to the link (switch and XAC) that supports
the corresponding address prefix. This parameter is not configurable for entries that
are configured with the X.25 address prefix type.
Range
1 to 15
Default
1
--- for X.25
Weight
This field specifies the weight assigned to the link (switch and XAC) that supports
the corresponding address prefix. When multiple links have the same address prefix
and priority, calls are distributed among the links based on the relative weights.
This parameter is not configurable for entries that are configured with the X.25
address prefix type.
Range
1 to 15
Default
1
--- for X.25
27.7-28
(400)
X.25 Serivce
The operator is prevented from entering address prefixes or making trunk circuit
connections if the GFR address of the switch is not configured (the hub or leaf is
required before any local or remote switching can occur).
The maximum number of extended address prefix entries may not exceed the
value of the maximum number of address prefixes per network (1024 for FRE
and 4096 for PE).
The GFR address for a switch cannot be changed if either the old or the new GFR
address has address prefixes defined.
For an existing extended address prefix entry, only the priority and weight
parameters can be changed. To change any other parameter the entry must be
deleted and re-added.
A maximum of 128 XACs per switch can be configured with extended address
prefixes of type X.25 gateway, X.75 gateway or hunt group.
When configuring an address prefix for local switch the address prefix type must
match the service type of the XAC number if either of them are X.25 or X.75
gateway.
The service type of an XAC cannot be changed to or from X.25 or X.75 gateway if
there are extended address prefixes for that XAC.
If the address prefix type of an extended address prefix entry is X.25 or X.75
gateway, duplicate address prefixes which share the same priority must have the
same address prefix type throughout the network.
The service type of an XAC cannot be changed to or from hunt group if there are
X.25 Service
(400)
27.7-29
DELETE
X25
TYPE
PRIORITY
WEIGHT
<pr>
<wt>
where
addr_prefix is the address prefix (1 to 19 digits or wildcards)
hub-leaf is the GFR address (nnn-nnn)
Xnnn is the XAC number
pr is 0, 1* 15
wt is 0, 1* 15
27.7-30
(400)
X.25 Serivce
27.8
Trunk Circuits
This chapter describes how to configure and connect the backbone trunk circuits that
carry traffic between X.25 switches.
27.8.1
You can provision backbone trunks on either frame streams (frame relay over
TDM circuits) or FASTbus circuits (frame relay over FDDI circuits). Provisioned
backbone trunks are frame relay PVCs with an associated routing metric or cost.
When a PE or X.25 FRE card is connected to a FASTbus, the card automatically
establishes backbone trunks to the other PE and X.25 FRE cards on the FASTbus
ring once the GFR address is configured. See chapter 25.6 for more information
about automatic FASTbus trunks.
Normally, cards residing on the same 36120 MainStreet system use automatic
FASTbus trunks rather than provisioned backbone trunks, although both methods
are possible.
Trunk circuits
Trunk circuits are virtual GFR ports that terminate backbone trunks. Each trunk
circuit has a configurable cost and poll timer. The PE and X.25 FRE cards support a
maximum of 128 trunk circuits. The actual number supported on a particular switch
is specified by the Number of Trunk Circuits parameter (see chapter 25.5).
X.25 Service
(400)
27.8-1
27.8.2
16 or 32
47
64
79
128
143
256
271
512
527
1024
1039
2048
2063
4096
4111
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Trunk Circuit
Cost
Poll Timer
-------------------------------------T1
50
0
T2
10
0
T3
1
1000
T4
15
1000
T5
50
0
T6
5
0
T7
50
0
T8
50
0
T9
255
1500
T10
15
0
T11
15
0
T12
15
0
T13
255
5000
CONFIG TRUNK "?-?"
Enter trunk circuit number. (Tnnn)
F1-PREVIOUS
F2-NEXT
F6F7-
27.8-2
(400)
F3F8-CANCEL
F4F9-QUIT
F5F10-
X.25 Serivce
<Tnnn>
SHOW_ALL
SHOW_GROUP
SK000408
27.8.3
Cost
This parameter specifies the cost, or routing metric, of the trunk in the outgoing
direction. You assign costs to allow the GFR to prioritize routes and perform load
balancing when more than one trunk connects two switches or when dynamic
routing is enabled.
The GFR assigns priority to trunk routes by evaluating the cost associated with each
trunk. When multiple trunks connect to the same remote switch, the GFR normally
selects the lowest-cost trunk to route frames. Higher-cost trunks are used only when
the preferred trunk fails.
When dynamic routing is enabled on switches in the hub domain, each switch has a
transit cost specified. In this case the GFR assigns priority based on the whole route
cost. This is a cumulative calculation which includes the total trunk costs of all the
hops, plus the transit cost of each hub switch.
When load balancing is enabled on the switch, the GFR distributes traffic equally
between parallel trunks when the differences in costs fall within the delta value
configured for the switch. For example, if trunk A has a cost of 50, trunk B has a cost
of 70, trunk C has a cost of 100, and the delta value is 25, load balancing only occurs
over trunks A and B. In a dynamic routing environment, the load balancing metric
is based on the route cost, which is the cumulative trunk and transit switch costs.
Because the cost applies only in the outgoing direction, trunks can have different
costs for each direction of traffic.
X.25 Service
(400)
27.8-3
Range
1 to 255. The value of 255 is infinite, meaning that the GFR never routes traffic to the
trunk.
Default
50
Poll Timer
This parameter specifies the time interval between keep-alive messages sent by the
GFR over an idle trunk. The keep-alive messages, or heartbeats, provide a way for
the switch to detect when a trunk goes down.
When the poll timer value is different at the two ends of the trunk, the endpoint
nodes use the higher of the two values.
Range
0 to 127 500 ms in increments of 500 ms. A value of 0 disables the timer.
Default
0
27.8-4
(400)
X.25 Serivce
COST
POLL_TIMER
<cost>
<time>
SK000409
where
Tnnn is the trunk circuit (1 to 128)
cost is 1 to 255 (50*)
time is 0* to 127 500
27.8.4
TO
<Scc-dlci>
DISCONNECT
SK000410
where
Tnnn is the trunk circuit (1 to 128)
Scc-dlci is the frame stream that connects to the primary rate circuit (1 to 62) and the DLCI for the frame
relay PVC between the nodes (16 to 1007)
X.25 Service
(400)
27.8-5
TO
DISCONNECT
<Fnn-dlci>
SK000411
where
Tnnn is the trunk circuit (1 to 128)
Fnn-dlci is the station ID of the PE or X.25 FRE card you are connecting to (1 to 62), and the DLCI for the
frame relay PVC between the cards (2000 to 3983)
27.8.5
2.
3.
Figure 27.8-2 shows the circuits and connections that must be configured. The
numbers in the illustration correspond to the step numbers in the detailed procedure
that follows.
27.8-6
(400)
X.25 Serivce
PRI card
X.25 FRE or
PE card
64 to 2.048 kb/s
To
remote
node
= Trunk circuit
Configure a circuit on the primary rate interface card that terminates the link to
the remote node. Note the circuit number; it must be used when configuring the
other end of the primary rate link.
2.
3.
X.25 Service
(400)
27.8-7
Note
Ensure that the Maximum Frame Size parameter for the stream is set to
accommodate the maximum X.25 packet size.
5.
6.
Connect the trunk circuit to the frame stream-DLCI (see the subsection To
connect trunk circuits to frame stream-DLCIs). Note the DLCI number; it must
be used when configuring the other end of the frame relay DLC.
7.
27.8-8
1.
Configure the FASTbus to support the PE or X.25 FRE cards (see chapter 24.4).
2.
3.
Connect the trunk circuit to the FASTbus circuit-DLCI (see the subsection To
connect trunk circuits to FASTbus circuit-DLCIs). Note the DLCI number; it
must be used when configuring the other end of the frame relay DLC.
4.
(400)
X.25 Serivce
27.9
27.9.1
Understanding NUIs
NUIs provide a mechanism for identifying network users independently of their
X.121 or E.164 addresses. NUIs ensure secure access to the network and provide a
third billing option, in addition to normal and reverse charging. It is also possible to
associate certain network options, such as CUGs and addresses, with a NUI.
NUIs and passwords are commonly used to facilitate secure dial-in access to X.25
networks. In such cases, the NUI and password not only uniquely identify the user,
but also provide a means to bill the user based on their NUI rather than the calling
address. Because the NUI validation server provides a centralized service to the
entire network, the same validation services are available to users regardless of the
port used for dialling into the network.
As shown in Figure 27.9-1, every 36120 MainStreet X.25 switch requiring access to
NUI validation services can be optionally configured with a redundant pair of SVC
connections to the NUI validation servers. These communication paths are used for
exchanging validation requests between the switch and the server.
X.25 Service
(400)
27.9-1
PE
PE
FRE
NUI
validation server
PE
FRE
FRE
PE
FRE
X.25 network
Primary NUI validation X.25 SVC
Secondary NUI validation X.25 SVC
7323
NUI subscription
Access to NUI validation for subscribers is implemented using the NUI Subscription
facility, which is a configurable NUA parameter. This facility allows a DTE to
include the NUI Selection facility in Call Request packets. The NUI Selection facility
enables the DTE to specify which NUI and password it is using for a particular call.
NUI override
DTEs that subscribe to the NUI Subscription facility are implicitly assigned the NUI
Override facility. This facility allows the subscriber to use the NUI Selection facility
to substitute a set of subscription options that differs from the subscription options
configured for the interface. The Nexus PASS system supports the insertion and
substitution of CUG facilities and calling and called addresses.
CUG insertion and override
In the case of CUGs, the switch either inserts or substitutes information provided by
the NUI validation server. If the Call Request packet contains a CUG facility, the
switch overrides the original interlock code with the interlock code from the NUI
validation server. If no CUG facility is signalled in the Call Request packet, the
switch inserts the interlock code and indicates whether the CUG or CUGOA facility
applies.
Address substitution
The Nexus PASS system can be configured to provide substitute calling and called
addresses. This allows for flexible dial-in access functionality whereby the calling
address does not have to be configured on the XAC. In such cases, the substitute
calling address uses the NUA subscription options of the default NUA assigned to
the XAC.
Called address substitution is a straightforward substitution of the original called
address with the called address received from the NUI validation server.
27.9-2
(400)
X.25 Serivce
X.25 Service
(400)
27.9-3
NUI Subscription
facility assigned?
NO
Clear call
YES
NUI validation
required?
Insert NUI in
internal facility field
of Incoming Call packet
NO
YES
Suspend call setup
and send validation
request to server
Valid NUI
and password?
NO
Clear call
NO
NUI Subscription
facility assigned?
YES
YES
Proced with
call setup
NO
NUI formats
For every DTE that requires NUI validation, you can specify the NUI format as an
NUA option. DTEs can be individually configured to support the standardized NUI
format as defined in Appendix VI of ITU-T Recommendation X.25, and one other
format.
When NUI validation is performed within the 36120 MainStreet X.25 network, the
switch encrypts the password, and converts the NUI format to a standardized
internal format before forwarding the NUI validation request to the validation
server. If the NUI format does not match the format configured for the NUA, the
switch clears the call.
27.9-4
(400)
X.25 Serivce
Figures 27.9-3 to 27.9-6 show example NUI formats and provide the parameter
settings required to define each format. The NUI format parameters are NUA
subscription options (see section 27.15.7).
Figure 27.9-3: Standardized NUI Format (ITU-T Recommendation X.25 1992,
Appendix VI)
8
Control
+
8
Type
Subfield length
NUI
+
8
Type
Subfield length
Password
Parameters:
Default NUI Format = Standard
8662
NUI
(6-8 IA5)
Parameters:
Default NUI Format = Non Standard
Non-standard NUI Coding Method = IA5
Non-standard NUI First Subfield = Password
Non-standard NUI First Subfield Length = 6
8663
Password
(IA5)
Parameters:
Default NUI Format = Non Standard
Non-standard NUI Coding Method = IA5
Non-standard NUI First Subfield = NUI
Non-standard NUI First Subfield Length = 6
8664
X.25 Service
(400)
27.9-5
Password
(4 BCD digits)
Parameters:
Default NUI Format = Non Standard
Non-standard NUI Coding Method = BCD
Non-standard NUI First Subfield = NUI
Non-standard NUI First Subfield Length = 10
8665
27.9.2
NUI
server agent
NUI
agent
XAC
Internal
X.25
network
Validation
server
XAC
Nexus PASS
validation server
8660
27.9-6
(400)
X.25 Serivce
The NUI agent XAC is the virtual port that provides access to the network for the
NUI server agent. Although the NUI agent XAC has the same configuration options
as a regular XAC, the following exceptions apply.
The XAC operates internally. It has no link layer interface, and the link layer
parameters are not configurable.
The NUA assigned to the NUI agent XAC is the calling address of the NUI server
See the subsection CUG considerations for information about CUG membership
requirements for the NUI server agent.
X.25 Service
(400)
27.9-7
Switch 33
Internal
X.25
network
Link
address
= 1234
Link
address
= 2345
Link
address
= 5678
Link
address
= 6789
8661
CUG considerations
To ensure secure access to the NUI validation server, Newbridge recommends that
the NUI server agents and the validation servers belong to the same CUG, which is
used only for this application.
Configure the NUA for the NUI agent so that the NUI agent can establish calls only
to the validation server, and never receive incoming calls. Set the CUG parameters
to:
27.9-8
(400)
X.25 Serivce
Configure the NUAs for the validation servers so that the validation servers can
receive calls only from the NUI agent, but never establish calls to the NUI server
agent. Set the CUG parameters to:
27.9.3
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
:x30204561789
:x30204561799
:10 secs
F2-SEC_ADDR
F7-
F3-MAX_PERIOD
F8-CANCEL
F4F9-QUIT
F5-
X.25 Service
(400)
27.9-9
27.9.4
27.9-10
(400)
X.25 Serivce
Default
None
For every switch that requires NUI validation services, you must configure the
X.25 Service
(400)
27.9-11
PRI_ADDR
SEC_ADDR
MAX_PERIOD
<address>
<address>
<seconds>
SK000412
where
address is the NPI and 1 to 19 digits in X.121 or E.164 address format
seconds is 1 to 500 (*10)
Select an XAC and set the Service Type parameter to NUI Agent.
CONFIG X25_ACCESS XAC <xac> NET_LAYER SERVICE AGENT
NUI PROCEED
CONFIG X25_ACCESS NUA <address> SUBS_OPT CUG <index>
INTERLOCK
BARRING
PREF
<code>
INC_BAR
YES
SK000413
Note
You can accept the default values for all other XAC parameters.
2.
Note
You can accept the default values for all other NUA parameters.
3.
27.9-12
(400)
X.25 Serivce
where
address is the NUA configured in step 2
index is the CUG index (0 to 99)
code is the CUG interlock code (1 to 65 535)
Note
You can accept the default values for all other CUG parameters.
X.25 Service
(400)
27.9-13
27.10
27.10.1
X.25 PE
X.25 DTE
X.25
Network
User
X.25 Vcs
X.25 FRE
NTP
Server
X.25 FRE
Secondary
Data
Collector
X.25 DTE
Accounting
Records
NTP Time
Updates
10619
X.25 Service
(400)
27.10-1
In Figure 27.10-2, one X.25 switch connects physically to the data collector, and other
X.25 switches in the network connect logically to the data collector.
Accounting
generation subsystem
Logical connection
Data collector
agent XAC
Data collector
Network
Network
Physical connection
Data collector
interface XAC
9147
Accounting segments
The accounting generation subsystem counts data in accounting segments. The
number of bytes in each segment is a configurable switch-wide parameter.
Transmitted segments and received segments for each VC are counted separately.
The segment counter increments whenever a segment sized number of bytes is
counted, or when the end of the packet is reached.
27.10-2
(400)
X.25 Serivce
Collection intervals
Along with an ability to accurately count transmitted and received data, the
accounting generation subsystem needs to keep track of network usage for different
times of the day. This capability allows clients to charge for network use based on
the time of day in which the network was used. To address this need, the accounting
generation subsystem groups segments according to the span of time during the day
in which the VC was active. These spans of time are called collection intervals. The
duration of a collection interval is a configurable switch-wide parameter. A
collection interval of 6 h starts at midnight, 6:00 a.m., noon and 6:00 p.m., whereas a
collection interval of 1 h starts every hour on the hour.
The transmit usage count is the number of transmitted segments counted during a
collection interval. The receive usage count is the number of received segments
counted during a collection interval. An interval report is composed of the transmit
usage count and the receive usage count. Figure 27.10-3 shows collection intervals,
interval reports and usage counts.
Figure 27.10-3: Collection Intervals, Interval Reports and Usage Counts
20 x 64 byte & 1 x 256 bytes pkts transmitted
3 x 256 byte pkts received
00:00 GMT
Collection
interval 3
Collection
interval 0
18:00
6:00
Collection
interval 2
Collection
interval 1
Interval Report
TX usage RX usage
count
count
22
12:00
Parameters:
Intermediate Record Interval = 24 h
Collection Interval = 6 h
Number of Collection Intervals = 4
Accounting Segment Size = 128 bytes
9108
Accounting records
Interval reports from successive collection intervals are combined with header
information, such as SVC start time and SVC duration, to form accounting records.
Accounting records are transmitted by the X.25 switch to the data collector for
storage.
Accounting records are produced at one of the two XACs involved in each VC. For
SVCs, accounting records are normally produced at the calling side, although in the
case of a reverse charge SVC the records are produced at the called side.
X.25 Service
(400)
27.10-3
intermediate records
end records
periodic records
time-change records
Intermediate records
An intermediate record is a combination of interval reports and header information.
The time period over which interval reports are collected to produce an intermediate
record is called an intermediate record interval. The intermediate record interval
duration divided by the collection interval duration must be an integer, and cannot
exceed 4 for the X.25 FRE card and 24 for the PE card.
The intermediate record interval is a configurable switch-wide parameter.
Figure 27.10-4 shows the relationship between collection intervals and intermediate
record intervals. In Figure 27.10-4, there are four collection intervals for each
intermediate record interval. The VC must be active during four collection intervals,
but not for the total duration of four collection intervals. In this case, the
intermediate record is generated after the VC is active for part of collection interval
0, plus all of collection intervals 1, 2 and 3.
Figure 27.10-4: Example of an Intermediate Record
24:00
Collection
interval 2
Collection
interval 3
18:00
6:00
Collection
interval 1
Collection
interval 0
Intermediate
record
Interval reports
12:00
Call start
time
Parameters:
Intermediate Record Interval = 24 h
Collection Interval = 6 h
Number of Collection Intervals = 4
Periodic Record Interval = 0 (off)
9110
27.10-4
(400)
X.25 Serivce
End records
The accounting generation subsystem produces an end record when an SVC is
cleared or a PVC is deleted or disabled. If the SVC duration is shorter than the
intermediate record interval and the periodic record interval, the end interval is the
only record produced. Figure 27.10-5 shows the generation of an end record for an
SVC. Figure 27.10-6 shows the relationship between an intermediate record and an
end record for an SVC.
Figure 27.10-5: Example of an End Record
End
record
24:00
Call clear
time
Call set-up
time
Collection
interval 0
Interval reports
Collection
interval 1
18:00
6:00
Collection
interval 3
Collection
interval 2
12:00
Parameters:
Intermediate Record Interval = 24 h
Collection Interval = 6 h
Number of Collection Intervals = 4
Periodic Record Interval = 0 (off)
9109
X.25 Service
(400)
27.10-5
24:00
Collection
interval 2
Collection
interval 3
18:00
Intermediate
record
6:00
Collection
interval 1
Collection
interval 0
Interval reports
Call clear
time
12:00
End
record
Call setup
time
Interval report
Parameters:
Intermediate Record Interval = 24 h
Collection Interval = 6 h
Number of Collection Intervals= 4
Periodic Record Interval = 0 (off)
9111
Periodic records
The periodic record provides redundancy in the collection of usage data. It is a
snapshot of the intermediate record for the current intermediate record interval. As
the VC progresses, periodic records accumulate interval reports but these interval
reports are discarded once the corresponding intermediate record is generated.
Figure 27.10-7 shows the generation of a periodic record for an SVC.
27.10-6
(400)
X.25 Serivce
Interval reports
Periodic
record
24:00
Interval reports
Collection
interval 2
Collection
interval 3
18:00
Intermediate
record
6:00
Collection
interval 1
Collection
interval 0
Interval reports
Call clear
time
12:00
Periodic
record
End
record
Interval reports
Call setup
time
Interval report
Parameters:
Intermediate record Interval = 24 h
Collection Interval = 6 h
Number of Collection Intervals = 4
Periodic Record Interval = 6 h
Time synchronization
The real-time clocks on X.25 switches and data collectors can be synchronized, using
the Internet time synchronization Network Time Protocol, to an accuracy of plus or
minus 1 second.
The data collector operates as an NTP server and synchronizes the switch, which
operates as a NTP client. The data collector also operates as an NTP client for
synchronizing itself with other data collectors and a common clock source.
The data collector can derive its clock source from any of the following references:
X.25 Service
(400)
27.10-7
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
:02-Jan-1970 03:54:27.89
:not Synchronized
27-
38-CANCEL
49-QUIT
50-
If the control card time is not configured, the switch uses time 0 (January 1 1970)
NTP then adjusts time from the best estimate towards central network time on the
data collector.
Time-change records
Time-change records are generated each time a network time adjustment greater
than or equal to 2 seconds is made by the time synchronization service. The
time-change record contains the current and previous time for which the time
change occurred.
27.10-8
(400)
X.25 Serivce
A time adjustment never changes the duration of the current collection interval.
Time changes are handled as follows.
A negative time adjustment (clock turned back) extends the next interval.
For example, assume that collection intervals are due every hour on the hour,
that it is 12:00 midnight and the clocks are automatically turned back to 11:45. If
the next collection interval is due to be complete at 1:00 a.m., it will have a
duration of 1 h and 15 min.
A positive time adjustment (clock turned forward) reduces the next interval.
For example, assume that collection intervals are due every hour on the hour,
that it is 12:00 midnight and the clocks are automatically turned forward to 12:15.
If the next collection interval is due to be complete at 1:00 a.m., it will have a
duration of 45 min.
The length of the first intermediate record interval is varied for each VC. This
X.25 Service
helps to prevent resource usage peaks when intermediate records are generated
for many VCs which start within the same collection interval. The length of each
first intermediate record interval is varied by up to three collection intervals less
than the intermediate record interval on the PE card and by up to two collection
intervals less on the X.25 FRE card. The result of this is that the actual number of
interval reports in the first intermediate record for each VC may be less than the
intermediate record interval divided by the collection interval.
The generation of intermediate records is paced over the first two thirds of each
collection interval. This pacing is subject to a minimum rate of two records per
second. A possible result of this pacing is that, if a VC ends before an
intermediate record is generated, then the intermediate record is replaced by an
end record which may contain one more interval report than the maximum
number of interval reports allowed in an intermediate record.
The generation of end records is paced at a minimum rate of 40 records per
second.
The length of the first periodic record interval for each SVC is varied. This helps
to prevent resource usage peaks when periodic records are generated for many
VCs which start almost simultaneously. They are varied over a 3 min interval on
the PE card and a 7.5 min interval on the X.25 FRE card.
The generation of periodic records is paced over 1 min for the PE card and
2.5 min for the X.25 FRE card.
(400)
27.10-9
27.10-10
(400)
X.25 Serivce
Description
Range
Field Size
Mandatory
or Optional
Header Fields
Data Type
0 = originating
recording interface
accounting
12 bits
Mandatory
0 = intermediate
1 = end
2 = periodic
4 bits
Mandatory
Byte offset:
byte 0 = network
domain identifier
byte 1 = hub identifier
byte 2 = leaf identifier
bytes 3 to 5 = call
identifier
bytes 6 to 9 = unused
10 bytes
Mandatory
0x0 to xFFFFFFFF
4 bytes
Mandatory
0 to 99
1 byte
Mandatory
0x0 to xFFFFFFFF
3 bytes
Mandatory
48 = 12:00
47 = 11:45
...
1 = 00:15
0 = 0 (GMT)
1 = +00:15
...
48 = +12:00
1 byte
Mandatory
1 = 15 min
2 = 30 min
3 = 45 min
4 = 60 min
5 = 120 min
6 = 180 min
7 = 240 min
8 = 360 min
9 = 480 min
A = 720 min
B = 1440 min
1 byte
Mandatory
Local XAC
1 to 512
2 bytes
Mandatory
Local LCN
1 to 4095
2 bytes
Mandatory
1 to 245
1 byte
Mandatory
1 to 245
1 byte
Mandatory
1 to 245
1 byte
Mandatory
X.25 Service
(400)
27.10-11
Field Name
Description
Range
Field Size
Mandatory
or Optional
Remote XAC
1 to 512
2 bytes
Mandatory
Remote LCN
1 to 4095
2 bytes
Mandatory
Cause Code
0 to 255
1 byte
Mandatory
Diagnostic Code
0 to 255
1 byte
Mandatory
Receive Throughput
Class
3 to 44
(75, 150, 300, 600,
1 200, 2 400, 4 800,
9 600, 19 200, 48 000,
64 000, 128 000,
192 000, 256 000,
320 000, 384 000,
448 000, 512 000,
576 000, 640 000,
704 000, 768 000,
832 000, 896 000,
960 000, 1 024 000,
1 088 000, 1 152 000
1 216 000, 1 280 000
1 344 000, 1 408 000,
1 472 000, 1 536 000
1 600 000, 1 664 000,
1 728 000 1 792 000,
1 856 000 1 920 000,
1 984 000 2 048 000
b/s)
1 byte
Mandatory
Transmit Throughput
Class
3 to 44
(75, 150, 300, 600,
1 200, 2 400, 4 800,
9 600, 19 200, 48 000,
64 000, 128 000,
192 000, 256 000,
320 000, 384 000,
448 000, 512 000,
576 000, 640 000,
704 000, 768 000,
832 000, 896 000,
960 000, 1 024 000,
1 088 000, 1 152 000
1 216 000, 1 280 000
1 344 000, 1 408 000,
1 472 000, 1 536 000
1 600 000, 1 664 000,
1 728 000 1 792 000,
1 856 000 1 920 000,
1 984 000 2 048 000
b/s)
1 byte
Mandatory
1 to 127
1 byte
Mandatory
1 to 127
1 byte
Mandatory
27.10-12
(400)
X.25 Serivce
Field Name
Description
Range
Field Size
Mandatory
or Optional
4 = 16
5 = 32
6 = 64
7 = 128
8 = 256
9 = 512
10 = 1024
11 = 2048
12 = 4096 bytes
4 bits
Mandatory
4 = 16
5 = 32
6 = 64
7 = 128
8 = 256
9 = 512
10 = 1024
11 = 2048
12 = 4096 bytes
4 bits
Mandatory
PVC Indication
1 = Yes
0 = No
1 bit
Mandatory
CUG Indication
1 = Yes
0 = No
1 bit
Mandatory
Reverse Charging
Indication
1 = Yes
0 = No
1 bit
Mandatory
1 = Yes
0 = No
1 bit
Mandatory
1 = Yes
0 = No
1 bit
Mandatory
1 = Yes
0 = No
1 bit
Mandatory
Hunted Indication
1 = Yes
0 = No
1 bit
Mandatory
1 = Yes
0 = No
1 bit
Mandatory
1 = X.25
2 = X.25 gateway
3 = X.75 gateway
4 = Traffic generator
5 = NUI agent
6 = data collector agent
7 = X.25 to FR
interworking agent
4 bits
Mandatory
1 = X.25
2 = X.25 gateway
3 = X.75 gateway
4 = Traffic generator
5 = NUI agent
6 = data collector agent
7 = X.25 to FR
interworking agent
4 bits
Mandatory
X.25 Service
(400)
27.10-13
Field Name
Description
Range
Field Size
Mandatory
or Optional
Type of Address
1 = International
3 bits
Mandatory
1 = E.164 digital
2 = E.164 analog
3 = X.121
4 bits
Mandatory
1 to 19 BCD digits
1 byte
Mandatory
1 to 19 BCD address
digits
1 to 32
bytes
Mandatory
Type of Address
1 = International
3 bits
Mandatory
1 = E.164 digital
2 = E.164 analog
3 = X.121
4 bits
Mandatory
1 to 19 BCD digits
1 byte
Mandatory
1 to 19 BCD address
digits
1 to 10
bytes
Mandatory
0 to 16777215
3 bytes
Optional
2 bytes
Optional
0 to 65535
2 bytes
Optional
2 bytes
Optional
2 bytes
Optional
IA5
1 to 24
bytes
Optional
x.00 to x.FF
1 to 21
bytes
Optional
x00000000 to
xFFFFFFFF
4 bytes
Mandatory
x00000000 to
xFFFFFFFF
4 bytes
Mandatory
X.75 Fields
X.75 Call Identifier
(1)
Interval Counts
27.10-14
(400)
X.25 Serivce
Notes
1. These items only appear in X.75 records.
2. These fields are not present in the case of a PVC.
27.10.2
Description
Range
Field Size
0x0 to xFFFFFFFFFF
4 bytes
0 to 99
1 byte
0x0 to xFFFFFFFFFF
4 bytes
0 to 99
1 byte
X.25 Service
(400)
27.10-15
Option or Range
Default
Yes
No
No
Generate
Dont Generate
Dont Generate
64 bytes
Collection Interval
24 h
24 h
0 min
0 to 24 characters
Time Zone
27.10-16
Accounting Activation
Periodic Accounting Activation
Hot Billing
Reverse Charge Acceptance
Local Charge Prevention
Charging Information Subscription
Charging Information Request Allowed
(400)
X.25 Serivce
27.10.3
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Accounting
---------------Generate Accounting Records
Generate Accounting Records on Unsuccessful Calls
Accounting Segment Size
Collection Interval
Intermediate Record Interval :24 hrs
Periodic Record Interval
Optional User Defined Data Length
Time Zone
F3-SEG_SIZE
F8-CANCEL
:Yes
:Yes
:64
:24 hrs
:0 hrs
:0 bytes
:-5:00 hrs
F4-INTERVALS
F9-QUIT
F5-USRDAT_LEN
F10-PROCEED
27.10.4
X.25 Service
(400)
27.10-17
27.10-18
(400)
X.25 Serivce
if this parameter is set to Generate and the clear cause code is:
DTE originated cause code (hex 00)(dec 0)
Remote Procedure Error (hex 11)(dec 17)
Local Procedure Error (hex 13)(dec 19)
Number Busy (hex 01)(dec 1)
Out of Order (hex 09)(dec 9)
Incompatible Destination (hex 21)(dec 33)
Fast Select Acceptance Not Subscribed (hex 29)(dec 41)
Invalid Facility Request (hex 03)(dec 3)
Access Barred (hex 0B)(dec 11)
when the clear cause code is Network Congestion (hex 05) (dec 5) or Not
X.25 Service
(400)
27.10-19
Default
64 bytes
Collection Interval
This parameter specifies the time duration of a collection interval. A collection
interval is the period of time at the end of which an interval report is produced.
An interval report contains the transmit usage count and the receive usage count for
a single collection interval. Collection intervals are discussed in more detail at the
beginning of this chapter.
The value of the Intermediate Record Interval divided by the value for the collection
interval, must:
not produce a fractional value (for example, if the Intermediate Record Interval
parameter is set to 45 min, the collection interval can be set to 15 min [45 15 = 3],
but cannot be set to 30 min [45 30 = 1.5])
be less than or equal to 4 for the X.25 FRE card, and less than or equal to 24 for
the PE card
not produce a fractional value (for example, if the Intermediate Record Interval
27.10-20
parameter is set to 45 min, the collection interval can be set to 15 min [45 15 = 3],
but cannot be set to 30 min [45 30 = 1.5])
be less than or equal to 4 for the X.25 FRE card, and less than or equal to 24 for
the PE card
(400)
X.25 Serivce
X.25 Service
(400)
27.10-21
Default
0
Time Zone
This parameter specifies the time zone in which this switch is located. The parameter
specifies the time zone in 15 min interval offsets from GMT.
Network operators are responsible for manually changing and synchronizing the
Time Zone parameter. The network cannot automatically change and synchronize
time zone settings.
A change in this parameter takes effect when the next accounting record is
generated.
Range
12:00 to 12:00 (hh:mm) in 15 min increments
Default
00:00 (which is GMT)
Range
0, 1, 2, 4, 16, 32, 64, 128, 256, 512, 768 kbytes
Default
512 kbytes for the PE card
256 kbytes for the X.25 FRE card
27.10-22
(400)
X.25 Serivce
USRDAT_LEN TIME_ZONE
INTERVALS
YES/NO
YES/NO
<length>
<segment>
<zone>
<inter>
<period>
SK000684
where
segment is 1, 2, 4, 8, 16, 32, 64*, 128, 256, 512, 1024, 2048 or 4096 bytes
length is 0 to 24 characters
zone is 12:00 to 12:00 (hh:mm) in 15 min increments, 0*
collect is 15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h*
inter is 15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h*
period is 0*, 5, 10, 15, 30, 45 min, 1, 2, 3, 4, 6, 8 and 12 h
* is the default
X.25 Service
(400)
27.10-23
27.11
27.11.1
X.25 Service
(400)
27.11-1
Figure 27.11-1: Data Collector Agent XACs and Data Collector Interface XACs
Primary Data Collector
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
PE or
FRE
X.25 Network
Primary Data Collector SVC
Secondary Data Collector SVC
Data Collector Interface XAC
Data Collector Agent XAC
Physical link
9149
27.11-2
(400)
X.25 Serivce
Configure the NUA for the data collector agent so that the data collector agent can
establish calls only to the data collector and never receive incoming calls. Set the
CUG parameters to:
The output from the data collector can be connected to a data processing computer
or to another data collector called a data server, through a TCP/IP connection
running over X.25, Ethernet or ATM.
GDI protocol
The GDI protocol controls the reliable transfer of transfer blocks between the NVM
of the accounting generation subsystem and the hard disk of the data collector. For
blocks to be transferred, an SVC is established from the data collector agent to the
primary and secondary data collectors. In the event of a primary data collector
failure, transfer blocks are sent to the secondary data collector and no data is lost.
When the primary data collector is running again, it receives the missing data from
the secondary data collector.
The data collector agent initiates a transfer when a transfer block is filled or after the
expiration of a configurable timer called the Maximum Time Between Transfers
Timer. This timer ensures that accounting data is transferred to a collector within a
certain period of time.
When the data collector has received a transfer block and has saved it successfully
to disk, the data collector sends an acknowledgment message to the data collector
agent. Upon receipt of this message, the accounting generation subsystem erases its
copy of the transfer block from NVM, and the data collector agent begins
transferring the next block if one is ready for sending.
X.25 Service
(400)
27.11-3
The transfer block is re-sent if the data collector agent does not complete
transmission of the transfer block or it does not receive an acknowledgment message
within the time period specified by the configurable Transfer Block Retransmission
Timer. Before resending the transfer block, the data collector agent first clears the
existing SVC and attempts to re-establish one to the collector. This sequence is
repeated a configurable Maximum Retransmission Count number of times before
the primary data collector is declared out of service and the transfer block is sent to
the secondary data collector.
If the NVM of the accounting generation subsystem becomes full to the point that it
exceeds a 75% threshold, the data collector agent does not wait a full Maximum
Retransmission Count number of times before sending the transfer block to the
secondary data collector. When the Maximum Retransmission Count is set to zero
the switch attempts to send the transfer block to the secondary collector immediately
after the Transfer Block Retransmission Timer expires.
When transfer blocks are being sent to the secondary data collector, the switch
periodically tries to call the primary data collector. When the call is finally
re-established to the primary data collector, the transfer in progress to the secondary
data collector stops, and transfer to the primary data collector begins. If transfer to
both the primary and secondary data collector is unsuccessful, the switch continues
to try both collectors indefinitely.
27.11.2
27.11-4
Option or Range
Default
None
None
1, 2, 4, 8, 16, 32 or 64 kbytes
24 h
0 10
0 900 s in 5 s increments
60 s
Enable
Disable
Enable
(400)
X.25 Serivce
27.11.3
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Data Collector
---------------Primary Data Collector Address
Secondary Data Collector Address
Transfer Block Size
Maximum Time Between Transfers
Transfer Block Retransmission Timer
Transfer Block Retransmission Count
:x30201002341001
:x30201002342002
:64 Kbytes
:24 hrs
:60 secs
:1
F1-PRI_ADDR
F6-RETR_COUNT
F2-SEC_ADDR
F7-
F3-BLOCK_SIZE
F8-CANCEL
F4-MAX_TIME
F9-QUIT
F5-RETR_TIMER
F10-PROCEED
27.11.4
X.25 Service
(400)
27.11-5
Range
TOA (i for international or n for national), NPI (x for X.121, e for E.164 digital, or m
for E.164 analog) and 1 to 19 address digits or wildcard characters (?).
Default
None
The change occurs while the primary data collector is active: In this case the data
collector agent immediately polls the secondary data collector at the new address
to make sure it can be reached.
The change occurs while the secondary data collector is active and a connection
to the primary data collector cannot be made: In this case, if there is an
unacknowledged transfer block outstanding, it is processed before activation of
the new address. When the new address is activated, the data collector agent
immediately tries to transfer data to it.
Range
TOA (i for international or n for national), NPI (x for X.121, e for E.164 digital, or m
for E.164 analog) and 1 to 19 address digits or wildcard characters (?).
Default
None
27.11-6
(400)
X.25 Serivce
X.25 Service
(400)
27.11-7
Default
1
For every switch that requires data collector services, you must configure the
data collector agent parameters and the data collector agent XAC.
In order for the switch to establish calls to the data collectors, the GAT must
contain entries that correspond to the primary and secondary data collector
addresses.
The NUAs assigned to the data collector agents and the data collectors should
belong to an exclusive CUG.
PRI_ADDR SEC_ADDR
<address>
<address>
BLOCK_SIZE
<kbytes>
<seconds>
<count>
SK000683
where
address is the NPI and 1 to 19 digits in X.121 or E.164 address format, none*
kbytes is 1, 2, 4, 16, 32 and 64, 64* kbytes for the PE card, 16* kbytes for the X.25 FRE card
time is 15, 30, 45 min, 1, 2, 3, 4, 6, 8, 12 and 24 h*
seconds is 0 to 900 s, 60*
count is 1 to 10, 1*
* is the default
Note
You can accept the default values for all other XAC parameters.
27.11-8
(400)
X.25 Serivce
Select an XAC and set the Service Type parameter to Data Collector Agent.
CONFIG X25_ACCESS XAC <xac> NET_LAYER SERVICE AGENT
COLLECTOR PROCEED
where xac is a valid XAC
2.
3.
X.25 Service
(400)
27.11-9
27.12
Accounting Subsystem
Configuration
This chapter provides a procedure describing the configuration of the X.25
accounting generation subsystem. For information on how to configure the data
collector, see the MainStreet Data Collector guide.
27.12.1
Configuration Overview
The following general procedure describes how to set up the accounting subsystem,
including:
X.25 Service
(400)
27.12-1
DC agent
Pri address = 1234
Sec address = 5678
DC agent XAC
NUA = 11xxxx
Switch 22
Switch 33
DC agent
Pri address = 1234
Sec address = 5678
DC agent
Pri address = 1234
Sec address = 5678
DC agent XAC
NUA = 22xxxx
DC agent XAC
NUA = 33xxxx
Internal
X.25
network
DC interface XAC
NUA = 1234
Redirection
address = 2345
Link
address
= 1234
DC interface XAC
NUA = 5678
Redirection
address = 6789
Link
address
= 2345
Link
address
= 5678
Link
address
= 6789
Data Collector
Data Collector
9810
1.
2.
Configure the data collector agent parameters on all switches that require the
generation of accounting records. See section 27.11.4.
The primary and secondary addresses are the same for each switch. For
example, in Figure 27.12-1 the primary address is 1234 and the secondary
address is 5678. Note the addresses as they will be used in step 4.
27.12-2
(400)
X.25 Serivce
3.
Configure the data collector agent XAC on all switches that require the
generation of accounting records. See the procedure To configure a data
collector agent XAC in section 27.11.4.
As shown in Figure 27.12-1, each data collector agent XAC has a dummy NUA.
For example, switch 22 has an NUA of 22xxxx.
Note
The dummy NUA of each data collector agent XAC belongs to the same CUG as the
NUA for the data collector.
4.
Configure the circuits for the access lines that physically connect the switches
to the data collectors. See chapter 27.13.
Newbridge recommends that you use different switches to connect each data
collector.
5.
Configure an interface XAC for the link to the primary data collector.
You can use the default XAC and NUA parameters (with the exception of the
CUG parameters in step 3). The NUA you assign to this XAC is the primary
data collector address configured in step 2.
As shown in Figure 27.12-1, the NUA for the interface XAC on switch 22 is 1234.
6.
Configure an interface XAC for the link to the secondary data collector.
You can use the default XAC and NUA parameters (with the exception of the
CUG parameters in step 3). The NUA you assign to this XAC is the secondary
data collector address configured in step 2.
7.
X.25 Service
For every interface that requires accounting record generation, ensure that
accounting generation is enabled.
a.
For NUAs, set the Accounting Activation parameter to Yes (see section
27.15.4).
b.
For PVCs, set the Accounting Activation parameter to Yes (see section
27.17.3).
c.
For X.75, set the Accounting Activation parameter to Yes (see section
27.10.4).
(400)
27.12-3
27.13
27.13.1
X.25 Service
(400)
27.13-1
DCC
or
DNIC
m x n x 8 kb/s
LAPB
X.25
switch
DTE
64 x m kb/s
LAPB
TDM
network
PRI link
PRI
card
X.25
backbone
network
DTE
m
= Transport bandwidth (1 to 8)
7296
RFC 1490, and ANSI T1.617a Annex F Multiprotocol Encapsulation over Frame Relay
ANSI T1.617a Annex G Encapsulation of ITU-T X.25/X.75 over Frame Relay
LAPB Annex G encapsulation
Annex G encapsulation provides a means to encapsulate LAPB frames using a
2-byte header. Because of the low overhead, this is the preferred encapsulation
method for access to the X.25 switch.
When you configure an FRS circuit for LAPB Annex G encapsulation, you must
specify the maximum size of the X.25 packets that use the circuit. The size of the
LAPB frames is derived using the algorithms described in Appendix VI of
Recommendation X.25; for packet sizes greater than 128 bytes, 9 bytes are added to
the X.25 packet size. The Annex G encapsulation method adds a 2-byte header. The
switch calculates the resulting frame relay T1.618 frame size as shown in
Table 27.13-1.
27.13-2
(400)
X.25 Serivce
266
256
267
512
523
1024
1035
2048
2059
4096
4107
0
EA
Data Link
Connection
Identifier
(DLCI)
LAPB frame
T1.618 frame
Check sequence
Check sequence
EA
Flag
1 1
DE
Flag
1 1
BECN
LAPB frame
FECN
C/R
Annex G encapsulation
of a LAPB frame
Frame relay
information
field
7968
X.25 Service
(400)
27.13-3
272
256
273
512
529
1024
1041
2048
2065
4096
4113
Figure 27.13-3 shows the frame format using LAPB as the encapsulated protocol.
Figure 27.13-3: RFC 1490 Encapsulation of LAPB Frames
0
EA
Data Link
Connection
Identifier
(DLCI)
0
EA
Flag
1 1
DE
BECN
FECN
C/R
Control 0 x 03
NLPID 0 x 08
0 x 46
LAPB frame
Flag
1 1
0 x 81
0 x 66
0 x 80
LAPB Frame
T1.618 Frame
Check Sequence
Check Sequence
Layer 2
protocol
ID
Layer 3
protocol
ID
Frame relay
information
field
7967
27.13-4
(400)
X.25 Serivce
FRS card
Annex G
or
RFC 1490
LAPB
DTE
Annex G
or
RFC 1490
Frame relay
Encapsulation
Encapsulation
X.25
network
Decapsulation
LAPB
DTE
Annex G
or
RFC 1490
Decapsulation
Frame relay
Annex G
or
RFC 1490
PAD/FRAD
7550
LAPB
Frame
relay
DCC
or
DNIC
or
PRI
card
Frame relay
network
DTE
X.25
switch
X.25
backbone
network
LAPB-encapsulating
PAD/FRAD
7551
X.25 Service
(400)
27.13-5
X.25 site
Frame relay
connection
m x n x 8 kb/s LAPB
DTE
DTE
DCC
or
DNIC
FRS
card
PRI
card
PRI
card
64 x m kb/s
LAPB
Encapsulated LAPB
PRI
card
X.25
switch
X.25
backbone
network
TDM
network
In the second scenario, encapsulation is used within the 3600 MainStreet series
bandwidth manager system to increase the number of 64 x n kb/s connections to the
X.25 switch. While the X.25 switch provides a maximum of 62 circuits for direct
connections, the use of frame streams and DLCs allows multiple 64 x n kb/s devices
to access the switch through a single circuit on the card. The number of basic rate and
super-rate X.25 device connections can thus be substantially increased, depending
on engineering limitations.
27.13-6
(400)
X.25 Serivce
DNIC
FRS
card
X.25
switch
X.25
backbone
network
DTU
8545
27.13.2
X.25 Service
(400)
27.13-7
APPLI
I/F_SPEED
TRANSP_BW
DIRECT_CCT
<speed>
<bandwidth>
SK000416
where
sn-cc is the slot number and circuit number on the card
speed is 8 to 1984 kb/s in multiples of 8, and must match the interface speed of the primary rate or data
interface circuit
bandwidth is n x 8 kb/s, where n is 1 to 8
27.13.3
APPLI
I/F_SPEED
TRANSP_BW
FR_ENCAP
<speed>
<bandwidth>
SK000417
where
sn-cc is the slot number and circuit number on the card
speed is 8 to 1984 kb/s in multiples of 8, and must match the interface speed of the primary rate or data
interface circuit
bandwidth is n x 8 kb/s, where n is 1 to 8
27.13-8
(400)
X.25 Serivce
Note
Configure the application as FR_ENCAP before configuring the interface speed or
transport bandwidth. The interface speed for the frame relay encapsulation circuit
must match the speed of the primary rate or data interface circuit to which it
connects.
RATE_ADAPT
APPLI
(see Note)
FR_ENCAP
SK000418
where sn-SRcc is the slot number and subrate circuit number on the FRS card
congestion thresholds
frame size
encapsulation type
The parameters and allowable values are the same for subrate and super-rate
circuits.
Figure 27.13-8 shows the NMTI display for configuring the frame relay
encapsulation parameters. The non-configurable information fields are described in
Table 27.13-3. The configurable parameters are described in the subsections
following the table.
X.25 Service
(400)
27.13-9
Stations:nn
P412-H1-00
Toronto:A
Alarms:1
ENCAP_CCT SR1
Status
Using Circuit
Interface Speed
Congestion Status
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
Encapsulated Protocol Max Frame Size
Required Frame Relay Frame Size
Connected To
Encapsulation type
11-May-1997
8:35a
:OOS-Disconnected
:A1-2
:9600 bps
:GREEN
:4 Kbytes
:80%
:50%
:512 Octets
:529 Octets
:S1-100
:LAPB RFC 1490
F2-THRESHOLDS
F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
27.13-10
Description
Status
Using Circuit
Shows the actual FRS circuit selected, or, if a subrate FRS circuit is selected,
the rate adapted FRS circuit to which the subrate encapsulation circuit is
connected.
Interface Speed
Congestion Status
Required Frame
Relay Frame Size
The size of the frame relay T1.618 frame after the LAPB frame is encapsulated.
This is a readable value that is calculated based on the value of the
Encapsulated Protocol Tax Frame Size parameter. The value of this field must
be less than the Maximum Frame Size parameter for the frame stream to which
this circuit is connected.
Connected To
(400)
X.25 Serivce
Encapsulation type
This parameter specifies the encapsulation method as either LAPB RFC 1490 or
LAPB Annex G. Transparent HDLC is not recommended. When you select LAPB
Annex G, the switch adds a 2-byte header to each frame being encapsulated. When
you select LAPB RFC 1490, the switch adds an 8-byte multiprotocol header to each
LAPB frame being encapsulated.
For encapsulating X.25 packets for transmission to an X.25 switch, you should select
LAPB Annex G.
Options
LAPB RFC 1490 or LAPB Annex G
Default
LAPB Annex G
X.25 Service
(400)
27.13-11
FRS NMTI
266
266
256
256
267
267
512*
512*
523*
523 (1600*)
1024
1024
1035
1035
2048
2048
2059
2059
4096
4096
4107
4107
Notes
1. Asterisks (?) indicate the default values.
Figure 27.13-9 shows the relevant NMTI screens and the packet and frame size
dependencies.
27.13-12
(400)
X.25 Serivce
Figure 27.13-9: Configuring Packet and Frame Sizes for an Encapsulation Circuit
X25FRE Stations:5
PA11-H0-01
OTTAWA:A2
Alarms:4
07-Jun-96
9:17A
NETWORK LAYER
-----------------------Packet Size
Allowed
-----------------------16
No
32
No
64
No
128
Yes
256
Yes
512
Yes
1024
No
2048
No
4096
No
CONFIG X25_ACCESS XAC 112 NET_LAYER PACKETS
F1-ADD
F6-
F2-REMOVE
F7-
FRS MainStreet
P114-H0-00
F3F8-
F4F9-QUIT/SAVE
OTTAWA:A2
Alarms:4
ENCAP_CCT SR1
Status
Using Circuit
Interface Speed
Congestion Status
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
Encapsulated Protocol Max Frame Size
Required Frame Relay Frame Size
Connected to
Encapsulation type
F5F10-CONTINUE
07-Jun-96
9:17A
:OOS-Disconnected
:A1-2
:9600 bps
:GREEN
:4 Kbytes
:80%
:50%
:512 Octets
:529 Octets
:S1-100
:LAPB RFC 1490
F2-THRESHOLDS
F7-
X25FRE Stations:5
F3F8-CANCEL
PA11-H0-01
F4F9-QUIT
OTTAWA:A2
Frame Stream S1
Status
Using Circuit
Interface Speed
Congestion Status
Absolute Congestion Threshold (ACT)
Severe Congestion Threshold (SCT)
Mild Congestion Threshold (MCT)
Maximum Frame Size
Number of Connections
Flags Between Frames
Protocol Type
Timeout
CONFIG
Alarms:4
F5F1007-Jun-96
9:17A
:OOS-Disconnected
:A1-1
:256000 bps
:GREEN
:10 Kbytes
:80%
:50%
:1600 bytes
:0
:1
:Annex D Bidirectional
:15 secs
STREAM S1
F1-FRAME_SIZE
F6-
F2-THRESHOLDS
F7-
F3-NUM_FLAGS
F8-CANCEL
F4-SHOW_CONNS
F9-QUIT
F5-PROTOCOL
F107520
X.25 Service
(400)
27.13-13
FRAME_SIZE
THRESHOLDS
ENCAP_TYPE
X.25_PKT_SZ
LAPB_1490
LAPB_ANNXG
<pkt_size>
ACT
SCT
MCT
<act>
<sct>
<mct>
SK000419
where
pawkiest is the number of octets (16, 32, 64, 128, 256, 512*, 1024, 2048, or 4096)
act is 1 to 64 kbytes, 4*
sct is 1 to 100%, 80*
mct is 1 to 100%, 50*
STREAM
ENCAP_CCT
CPSS
RATE_ADAPT
27.13-14
(400)
X.25 Serivce
Stations:nn
Circuit
--------A1-1
A1-2
A1-3
A1-3
A1-4
A1-5
A1-6
A1-7
A1-8
A1-9
A1-10
A1-11
A1-12
A1-13
A1-14
A1-15
P412-H1-00
Toronto:A
Stream/act
----------S1
2
SR2
SR3
SR4
n/a
SR29
7
S8
9
S10
S11
S12
S13
S14
---
Alarms:1
Application
------------STREAM
ENCAP_CCT
RATE_ADAPT
RATE_ADAPT
RATE_ADAPT
CPSS
RATE_ADAPT
ENCAP_CCT
STREAM
ENCAP_CCT
STREAM
STREAM
STREAM
STREAM
STREAM
RATE_ADAPT
11-May-1997
Speed
-------256000bps
9600bps
9600bps
9600bps
9600bps
56000bps
9600bps
2400bps
56000bps
8000bps
64000bps
64000bps
64000bps
64000bps
64000bps
64000bps
8:35a
Status
-------OOS-LMI
In Service
In Service
In Service
OOS-LMI
In Service
In Service
OOS-Disconnected
In Service
In Service
In Service
In Service
In Service
In Service
In Service
OOS-Disconnected
27.13.4
2-PREVIOUS
7-
38-CANCEL
49-QUIT
510-
Congestion thresholds
On the FRS card, set the ACT to 32 kbytes. Accept the default values for MCT and
SCT.
On the X.25 switch, set the ACT to 100 kbytes. Accept the default values for MCT and
SCT.
X.25 Service
(400)
27.13-15
27.13.5
27.13-16
frame stream circuit on an FRS card (FRS_STREAM). This provides frame relay
encapsulated access to the X.25 switch when the FRS and X.25 FRE cards are
located on the same node.
A frame stream circuit on the X.25 FRE card (FRE_STREAM) is connected to a
primary rate interface circuit on an E1 card (E1_NOSIG). This provides frame
relay encapsulated access to the X.25 switch over a primary rate link when the
FRS and X.25 FRE cards are located on different nodes.
A direct circuit (FRE_DIRCCT) is connected to a data interface circuit on a V.35
card (V.35_DCC). This provides direct LAPB access to the X.25 switch from the
data interface card.
A direct circuit (FRE_DIRCCT) is connected to a primary rate interface circuit on
an E1 card (E1_NOSIG). This provides direct LAPB access to the X.25 switch over
a primary rate link.
A direct circuit is connected to another direct circuit for testing circuits within the
X.25 switch.
(400)
X.25 Serivce
1117-H1-00
Name
Toronto:A
Type
FRE_STREAM
FRE_STREAM
FRE_DIRCCT
FRE_DIRCCT
FRE_DIRCCT
FRE_STREAM
FRE_STREAM
FRE_STREAM
FRE_STREAM
FRE_DIRCCT
FRE_DIRCCT
FRE_DIRCCT
Alarms:1
Circuit
*A3-01
*A6-02
*A7-03
*A6-12
*A5-10
--------*A5-05
-----
Name
11-May-1997
8:35a
Type
FRS_STREAM
E1_NOSIG
V.35_DCC
E1_NO_SIG
FRE_DIRCCT
Conv
FRE_DIRCCT
1-SHOW_CCT
6-PROTECTING
27.13.6
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
5-PROT_BY
0-
27.13.7
X.25 Service
(400)
27.13-17
The DLCI connection is the same for both subrate and super-rate circuits.
Connections are allowed both ways; that is, you can connect an encapsulation circuit
to a DLC, or a DLC to an encapsulation circuit.
Class-of-service parameters can be set for the connections. Class-of-service
enforcement can be enabled only for the DLCI side of the connection, not for the
ENCAP_CCT side. For more information about class-of-service parameters, see
chapter 25.8.
Caution
If you change the values for the class-of-service parameters, the parameters must
also be configured at the X.25 switch end of the connection (the stream-DLCI to
which the XAC connects). The values must match at both ends of the connection.
FRS card
Frame
relay
network
m x n x 8 kb/s
1
HDLC device
= Transport bandwidth (1 to 8)
8037
27.13-18
From the Control card NMTI, connect the super-rate encapsulation circuit to a
data or primary rate interface circuit.
(400)
X.25 Serivce
2.
From the FRS NMTI, connect the super-rate encapsulation circuit to a frame
stream-DLCI.
CONFIG CONNECT <cc> or <Scc-dlci> TO <cc> or <Scc-dlci>
where
cc is the encapsulation circuit
Scc-dlci is the frame stream circuit (1 to 31) and a DLCI (16 to 1007)
Note
See section 27.13.9 for information about setting the class-of-service parameters for
DLCs.
FRS card
Frame
relay
network
3
1.2 to 56 kb/s
1
2
HDLC device
X.25 Service
(400)
27.13-19
Subrate encapsulation circuits on the FRS card can be connected only to FRS circuits
configured for rate adaption. The rate-adapted circuit is typically an aggregate
circuit which carries X.25 traffic to and from X.25 access lines. As shown in
Figure 27.13-14, the connection must be made from the subrate encapsulation circuit
to the rate adapted circuit.
Figure 27.13-14: Subrate Encapsulation Circuit Connection
3600 MainStreet
Circuit
1117-H1-00
Name
Toronto:A
Type
A3-SR01
A3-SR02
A3-SR03
A3-SR04
A3-SR05
A3-SR06
A3-SR07
A3-SR08
A3-SR09
A3-SR10
A3-SR11
Alarms:1
Circuit
FRS_SBRENC
FRS_SBRENC
FRS_SBRENC
FRS_SBRSTR
FRS_SBRENC
FRS_SBRENC
FRS_SBRENC
FRS_SBRENC
FRS_SBRSTR
FRS_SBRENC
FRS_SBRENC
11-May-1997
Name
*A8-B01/3
---------------------
Type
8:35a
Conv
FRS_RATEAD
27-
3-TO_CIRCUIT
8-CANCEL
49-QUIT
50-
From the Control card NMTI, connect the subrate encapsulation circuit to a rate
adaption circuit:
CONFIG CONNECT <sn-SRcc> TO_CIRCUIT <sn-cc> PROCEED
where
sn-SRcc is the FRS slot number and subrate encapsulation circuit number
sn-cc is the FRS slot number and rate adaption circuit number
2.
From the Control card NMTI, connect the rate adaption circuit to a data
interface circuit:
CONFIG CONNECT <sn-cc1> TO_CIRCUIT <sn-cc2> PROCEED
where
sn-cc1 is the FRS slot number and rate adaption circuit number
sn-cc2 is the data interface slot and circuit number
3.
From the FRS NMTI, connect the subrate encapsulation circuit to a frame
stream-DLCI:
CONFIG CONNECT <SRcc> TO <Scc-dlci>
27.13-20
(400)
X.25 Serivce
where
SRcc is the subrate encapsulation circuit
Scc-dlci is the frame stream circuit (1 to 31) and a DLCI (16 to 1007)
Note
See section 27.13.9 for information about setting the class-of-service parameters for
DLCs.
27.13.8
Connecting XACs
An XAC is a virtual port that terminates an X.25 access line on the switch. From the
X.25 switch NMTI, you connect XACs to direct circuits for direct LAPB access, or to
frame-stream-DLCIs (Scc-DLCI) or FASTbus station-DLCIs (Fnn-DLCI) for
encapsulated access. You do not have to set any parameters for
XAC-to-DIRECT_CCT connections. For connections between an XAC and an
Scc-DLCI or Fnn-DLCI, you must select the encapsulation method (RFC 1490 or
Annex G), and optionally configure the class-of-service parameters.
CIR
BC
BE
ENABLE
<cir>
<bc>
<be>
FROM_DLCI
DISABLE
TO_DLCI
SK000420
where
Xxac is a valid XAC
Scc-dlci is a frame stream circuit and DLCI
Fnn-dlci is a FASTbus station and DLCI
cir is the committed information rate (0 to 1984 kb/s)
bc and be are the committed burst size and excess burst size (0 to 1984 kb)
X.25 Service
(400)
27.13-21
27.13.9
all the access lines do not transmit bursts of data at the same time
all the access lines do not burst at 100% of the interface speeds
27.13-22
(400)
X.25 Serivce
Use the following guidelines to configure the class of service parameters for each
frame relay PVC, and to determine the required frame stream bandwidth.
CIR
Set the CIR to 75% of the peak load on the access line. Since the CIR is configured in
1 kb/s increments, always round up to the nearest value. For example, if the peak
load on a 9.6 kb/s access line is 50%, the CIR is calculated as follows:
9.6 0.5 0.75 = 3.6, therefore the CIR = 4 kb/s
Bc
The Bc must be greater than the maximum frame size and greater than the maximum
burst size, if known. If not, set the Bc to 4 CIR or 10 maximum frame size,
whichever is greater. As above, round up to the nearest value. For example, if the
maximum X.25 packet size on an access line is 256 bytes, the maximum frame size is
273 bytes (allowing for RFC 1490 encapsulation overhead), and the Bc is calculated
as follows:
273 8 (bits) 10 = 21 840, therefore the Bc = 22 kb
Be
Set the Be by determining the values of Tc and EIR, and calculating the Be value.
Determine the value of Tc using the CIR and Bc values:
Bc
CIR
Tc=
Determine the value of the EIR using the access line speed and the CIR value:
EIR = speed CIR
Calculate the Be using the values of Tc and EIR:
Be = Tc EIR
For example, for a 9.6 kb/s access line with a CIR of 4 kb/s and a Bc of 22, the above
formulae generate the following:
Tc = 5.5 s
EIR = 5600 b/s
Tc EIR = 30 800; therefore the Be = 31 kb
X.25 Service
(400)
27.13-23
27.13-24
(400)
X.25 Serivce
27.14
XAC Parameters
This chapter describes how to configure the XAC interface parameters.
27.14.1
Understanding XACs
An XAC is a virtual port that terminates an X.25 access line on the switch. XACs
define the link layer, network layer, NUAs, and facilities for physically connected
X.25 devices. One XAC is configured for each X.25 device connected to the switch.
Typically, an XAC identifies an X.25 interface to a subrate or super-rate DTE or an
internal DTE; however, XACs are also used to connect other X.25 switches, in the
case of gateways, and to connect functional subsystems such as the NUI validation
servers.
From a configuration point of view, the term XAC refers to the collection of
parameters that define the link and network layer operation, addresses, and call
subscription options for an X.25 device. Once an NUA is assigned to an XAC
interface, the XAC is considered active.
The PE card supports up to 992 XACs, while the X.25 FRE card supports a maximum
of 128 XACs. The actual number supported on a particular switch is determined by
engineering constraints; the maximum theoretical limit is specified by the Number
of XACs parameter (see chapter 27.5).
27.14.2
Configuration overview
Typically, you perform the following steps to fully configure an XAC.
1.
X.25 Service
2.
Configure the X.121 or E.164 address and assign it to an XAC. See section
27.15.4.
3.
(400)
27.14-1
You can also use the COPY command to copy the configuration parameters of an
XAC to one or more XACs. See chapter 27.16.
27.14.3
Link layer parameters are not configurable for NUI server agent and accounting
agent XACs. Both of these service types operate internally and have no link layer
interface.
27.14.4
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
LINK LAYER
---------Link Layer Interface Type
Frame Sequence Numbering
Maximum Frame Window Size
Retransmission Count (N2)
Frame Response Timer (T1)
Response Delay Timer (T2)
Inactivity Timer (T3)
Congestion Timer
:DCE
:8
:7
:10
:3000 ms
:200 ms
:60000 ms
:3000 ms
:517
8:35a
27.14-2
F2-SEQ_NUMBER
F7-
(400)
F3-WIN_SIZE
F8-CANCEL
F4-N2
F9-QUIT
F5-TIMERS
F10-
X.25 Serivce
27.14.5
Options
DTE or DCE
Default
DCE
X.25 Service
(400)
27.14-3
27.14-4
(400)
X.25 Serivce
The value of T1 must be greater than T2 and less than T3 (T3 > T1 > T2).
Range
10 to 120 000 ms in multiples of 10 ms
Default
3000 ms
X.25 Service
(400)
27.14-5
Congestion Timer
This parameter specifies the maximum time to wait for a congested LAPB link to
become uncongested. This timer starts when the LAPB transmit queue exceeds a
pre-determined threshold. If the timer expires before the transmit queue falls below
the threshold, the link is brought down. This prevents one link from using a
disproportionate amount of resources on the switch. Avoid setting this value too
small for links that experience bandwidth bottlenecks or large volumes of bursty
traffic.
Range
10 to 120 000 ms in multiples of 10 ms
Default
3000 ms
The value of T3 must be sufficiently greater than the value of T1 so that the
27.14-6
(400)
X.25 Serivce
Changing the value of the Inactivity Timer (T3) for an in-service link has the
following results.
When timer T3 is changed from 0 to some other value, the timer starts only when
the link is restarted or when a frame is sent or received over the link. For example,
if the remote DTE is running an idle timer, timer T3 starts when the DTE timer
expires and the DTE transmits an RR frame.
When timer T3 is enabled (not 0) and the value is changed, the current timeout
value is allowed to expire before the new value takes effect. For example, if the
timer is set to 30 seconds and then changed to 1 second, the timer may take up to
30 seconds to expire before 1-second timeouts occur.
You can change the values of all other link layer parameters at any time with no
disruption of service. The changes are effective immediately.
DTE/DCE
SEQ_NUMBER
WIN_SIZE
N2
<DTE/DCE>
<seq_number>
<k>
<n2>
T1
<t1>
T2
TIMERS
T3
<t2> <t3>
CONGST_TMR
<congst_tmr>
SK000421
where
xac is a valid XAC
seq_number is 8* for sequence numbers 1 to 7 or 128 for sequence numbers 1 to 127
k is 1 to 7* if SEQ_NUMBER is set to 8, or 1 to 127 if it is set to 128
n2 is 1 to 20, 10*
t1 is 10 to 120 000 ms in multiples of 10 ms, 3000*
t2 is 0 to 3000 ms in multiples of 100 ms, 200*
t3 is 0 to 120 000 ms in multiples of 10 ms, 60 000*
congst_tmr is 10 to 120 000 ms in multiples of 10 ms, 3000*
27.14.6
X.25 Service
(400)
27.14-7
27.14-8
(400)
X.25 Serivce
Logical channel
X.25
network
DCE
DCE
DTE
DTE
7299
During the call setup phase, the calling DTE selects the logical channel on its X.25
link when it sends a Call Request. The destination DCE selects a logical channel on
the link to the called DTE, on which it transmits the Incoming Call packet. To
minimize the risk of call collision, the calling DTE always selects the highest
available LCN for a call request, while the destination DCE always selects the lowest
available LCN.
By default, each XAC supports 32 two-way SVC LCs. Outgoing SVC LCs and
incoming SVC LCs can be assigned to provide the One-way Logical Channel
Outgoing and One-way Logical Channel Incoming facilities as defined in X.25.
To change the default logical channel assignment, you must define the total number
of LCs required, the base LCN, and the number of channels required for each LC
type. The switch then allocates LCNs according to the type of LC. The number of
two-way SVC LCs is the difference between the total number of LCs and the number
of PVC LCs, incoming SVC LCs, outgoing SVC LCs. That is:
Two-way SVCs = LCNs (PVCs + SVCsout + SVCsin)
Figure 27.14-3 shows how LCNs are allocated.
X.25 Service
(400)
27.14-9
Assignments
HOC
Outgoing LCs
LOC
Number
of LCs
(1 to 4095)
HTC
Two-way LCs
SVC LCs
LTC
HIC
Legend
HOC: highest outgoing
channel
LOC: lowest outgoing
channel
HTC: highest two-way
channel
LTC: lowest two-way
channel
HIC: highest incoming
channel
LIC: lowest incoming
channel
Incoming LCs
LIC
PVC LCs
Base LCN
Reserved
7297
27.14-10
Start Trigger
Stop Trigger
Default
T10
180 s
T11
200 s
T12
180 s
T13
180 s
T20
180 s
T21
200 s
(400)
X.25 Serivce
Timer
Start Trigger
Stop Trigger
Default
T22
180 s
T23
180 s
T24
60 s
Inactivity
0s
Flow
Control
1s
Negotiation facilities
Flow Control and Throughput Class Negotiation facilities are assigned to XACs to
permit the calling and called DTEs and the calling and called DCEs to negotiate the
packet size, window size, and throughput class to be used for each virtual call.
Negotiation occurs during the call setup phase and applies to both directions of data
transmission.
Flow control allows the data receiver to limit the rate at which it accepts data by
restricting the number of unacknowledged packets (window size) and the
maximum size of the packets on a virtual call basis. The throughput class, or rate at
which data is transmitted (in b/s), is similarly negotiable on a virtual call basis.
Negotiation occurs at the three functional interfaces in the call request path: local
DCE, remote DCE, and remote DTE. When a DTE issues a Call Request packet with
a negotiation facility, each functional interface can:
X.25 Service
(400)
27.14-11
For the following address types, the address length after translation must be less
than or equal to the Maximum Address Length parameter:
the called address contained in the call setup and clearing packets to the DTE
the calling address contained in call setup and clearing packets from the DTE
The difference between the Maximum Address Length and the length of the address
assigned to the DTE is the number of subaddress digits allowed.
Address suppression
The calling and called addresses can be optionally suppressed on a per-XAC basis to
meet compatibility requirements of specific DTEs and networks.
Set the Allowable Packet Sizes parameter for the XAC interface, and note the
maximum packet size:
CONFIG X25_ACCESS XAC <xac> NET_LAYER MORE PACKETS
ADD <pkt_size>
2.
If the X.25 device is accessing the switch through a frame relay encapsulation
circuit, determine which FRS card and circuit number support the device.
3.
4.
Check the value of the Encapsulated Protocol Maximum Frame Size parameter
for the encapsulation circuit:
CONFIG ENCAP_CCT <cc> or <SRcc>
5.
27.14-12
Ensure that the Encapsulated Protocol Maximum Frame Size parameter for the
encapsulation circuit is equal to or greater than the highest allowable packet
size value for the XAC interface.
(400)
X.25 Serivce
27.14.7
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
NETWORK LAYER
--------------:X.25
:DCE
:1984/1988
:8
Service Type
Packet Layer Interface Type
Version
Packet Sequence Numbering
:180 s
:200 s
:180 s
:180 s
:60 s
:0 s
:1 s
Base LCN
Number of LCNs
Number of PVCs
Number of Incoming SVCs
(Two Way SVCs)
Number of Outgoing SVCs
:1
:32
:0
:0
:32
:0
F3-SEQ_NUMBER
F8-CANCEL
F4-LCN_ALLOC
F9-QUIT
F5-TIMERS
F10-
27.14.8
The Packet Layer Interface Type parameter must be set to DCE on one end of the
X.25 Service
(400)
27.14-13
Service Type
This parameter specifies the type of service supported by the X.25 access line. Select
AGENT to specify the service type as one of the following internal DTE agents: NUI,
accounting, or traffic generator.
Only one XAC per switch can be configured as a NUI agent, accounting agent, or
traffic generator. XACs that are configured for these service types can be assigned
only one NUA; multi-NUA support does not apply to NUI agents, accounting
agents, or traffic generators.
You cannot change the service type if the XAC is connected to a direct circuit or
frame stream-DLCI. Disconnect the XAC first.
Options
X.25, X.25 Gateway, NUI Agent, Accounting Agent, Traffic Generator, or XFR.
Default
X.25
X.25 Version
This parameter specifies the version of X.25 protocol supported by the DTE. The
length of the facility field is greater in the 1992 version.
Options
1984/1988 or 1992
27.14-14
(400)
X.25 Serivce
Default
1984/1988
Base LCN
This parameter specifies the LCN of the first logical channel supported on the
interface.
Range
1 to 4095
1 for XFR service interworking
Default
1
Number of LCNs
This parameter specifies the total number of logical channels supported on the
interface. This value must be greater than or equal to the number of PVCs + the
number of incoming SVCs + the number of outgoing SVCs.
X.25 Service
(400)
27.14-15
Range
1 to 4095
1 for XFR service interworking
Default
32
1 for XFR service interworking
Number of PVCs
This parameter specifies the number of logical channels on the interface that support
PVCs. The number of PVCs + the number of incoming SVCs + the number of
outgoing SVCs must be less than or equal to the number of LCNs.
Range
0 to 4095
0 to 1 for XFR service interworking
Default
0
1 for XFR service interworking
27.14-16
(400)
X.25 Serivce
Two-way SVCs
This parameter specifies the number of logical channels on the interface that support
both incoming and outgoing SVCs. This parameter is not directly configurable; the
value is determined as follows:
n = LCNs (PVCs + SVCsout + SVCsin)
where
n = Number of Two-way SVCs
LCNs = Number of LCNs
PVCs = Number of PVCs
SVCsout = Number of Outgoing SVCs
SVCsin = Number of Incoming SVCs
Range
1 to 4095
0 to 1 for XFR
Default
32
0 for XFR service interworking
X.25 Service
(400)
27.14-17
27.14-18
(400)
X.25 Serivce
Range
0 to 630 seconds
Default
180 seconds
Inactivity Timer
The network layer inactivity timer starts when the transmit queue is full and stops
when the transmit window opens. When the timer expires, the virtual circuit is reset,
thereby preventing deadlock on the virtual circuit. The default (0) disables this
timer.
Range
0 to 630 seconds
Default
0 seconds
X.25 Service
(400)
27.14-19
27.14-20
(400)
X.25 Serivce
Range
1 to 19 digits
Default
19 digits
X.25 Service
(400)
27.14-21
The switch checks the calling address in Call Request packets against the list of
NUAs configured for the XAC. A match indicates a valid calling address. If there
is no match, and this parameter is set to Yes for the default NUA, the call is
cleared.
In Call Accepted packets, the switch validates the complete calling address.
In Call Accepted packets without the CLAMN facility, the switch validates the
complete called address.
In Call Accepted packets with the CLAMN facility present, the switch validates
the called address, but the subaddress digits of the called address may be
modified. Subaddress digits can differ only when the CLAMN facility is present.
In call clearing packets, the switch validates the called address when the CLAMN
facility is present. Only the subaddresses digits may be modified, otherwise the
call is cleared.
In call clearing packets, when the called DTE inserts the calling address (cases
where the CLAMN facility is present), the switch validates the calling address
even though the address is not passed to the calling DTE.
When this parameter is set to No, the switch handles addresses as follows.
If present in call setup packets, both the calling and called addresses are passed
transparently.
In call clearing packets, the called address is passed transparently if the CLAMN
facility is present. The calling address is forced to 0.
Disabling validation has the effect of allowing any calling address to be accepted as
valid. Generally, this parameter should be set to No only for interfaces that function
as internetwork X.25 gateways.
Options
Yes or No
Default
Yes
Default NPI
This parameter specifies the default NPI to use if the DTE does not subscribe to the
TOA/NPI Address Format option.
27.14-22
(400)
X.25 Serivce
Options
X.121, E.164 digital, or E.164 analog
Default
X.121
X.25 Service
(400)
27.14-23
27.14-24
(400)
X.25 Serivce
Generate Alarms
This parameter specifies whether the switch generates alarms for this XAC to
indicate that the link layer or network layer is down.
Options
Yes or No
Default
No
X.25 Service
(400)
27.14-25
27.14-26
(400)
X.25 Serivce
You can change the following network layer parameters at any time with no
disruption of service. The changes are effective for the next call.
You can change the following network layer parameters at any time with no
disruption of service. The changes are effective immediately.
X.25 Service
(400)
27.14-27
SERVICE
SEQ_NUMBER LCN_ALLOC
INTF_TYPE
TIMERS
ADDRESSING
MORE
<seq_number>
DTE/DCE
VERSION
<version>
X25
X25_GATEW
NUI
AGENT
ACCOUNTING
BASE_LCN
NUM_LCN
TRAFFC_GEN
NUM_PVC
NUM_O_SVC
NUM_I_SVC
<number>
T10T20RST
T11T21CALL
T12T22RES
T13T23CLR
T24WIN
INACTIVITY
MORE
FLOW_CNTL
<seconds>
MAX_LENGTH
SUPRESS_CD SUPRESS_CG
LOCAL_VAL
DEF_NPI
<max_length>
YES/NO
TRANSLATE
(see address
translation section)
PACKETS
ADD
E164_ANA
NEGOTIATE
E164_DIG
CAUSE_CODE
DTE_CAUSE
REMOVE
X121
ALARMS
DIAGNOSTIC
<pkt_size>
YES/NO
FLOW_CNTL
THRU_PUT
TPUT_FORMT
BASIC/EXTENDED
YES/NO
SK000422
27.14-28
(400)
X.25 Serivce
where
xac is a valid XAC
version is the version of X.25 protocol (1984/1988* or 1992)
seq_number is 8* for modulo 8 (normal) or 128 for modulo 128 (extended) operation
number is 1 to 4095, 10* for NUM_LCN
seconds is 1 to 180 for the flow control timer (1*), and 1 to 630 for all other timers
max_length is 1 to 19* digits
pkt_size is one or more of the values 16, 32, 64, 128, 256, 512*, 1024, 2048, or 4096
27.14.9
X.25 Service
(400)
27.14-29
X.25
network
External
address
format
Internal
address
format
DCE
DCE
External
address
format
DTE
DTE
7298
The valid external and internal address formats are listed in Table 27.14-2.
Table 27.14-2: External and Internal Address Formats
External Address Format (Signalled on Link)
SS
x, DNIC+NTN+SS
NTN
x, DNIC+NTN
NTN+SS
x, DNIC+NTN+SS
DNIC+NTN
x, DNIC+NTN
DNIC+NTN+SS
x, DNIC+NTN+SS
P+DNIC+NTN
x, DNIC+NTN
P+DNIC+NTN+SS
x, DNIC+NTN+SS
SN
e or m, CC+NSN
1+NSN
e or m, CC+NSN
011+CC+NSN
e or m, CC+NSN
Legend:
CC = E.164 country code
DNIC = Data network interface code
e = NPI value designating a digital E.164 address
m = NPI value designating an analog E.164 address
NSN = National significant number (NDC + SN)
NTN = National terminal number
P = International prefix digit. (0 to 9)
SN = Subscriber number (local number, for example, 7 digits in North America)
SS = Subaddress digits
x = NPI value designating an X.121 address
+ indicates that two strings are concatenated
, indicates the separation of the NPI and address fields
Address translation
The purpose of address translation is to convert addresses signalled on X.25 access
lines to a normalized internal address format. This is done by inserting, removing or
modifying address digits. The internal format allows calls to be effectively screened
and routed using compact and manageable tables.
27.14-30
(400)
X.25 Serivce
When addresses are transmitted over X.25 access lines, they are converted between
external and internal address formats. At the switch, incoming external addresses
are converted to a common internal address format used to route calls through the
network. Outgoing internal addresses are converted to an external format
recognized by the device to which the call is being established. The process of
conversion between the two formats is referred to as address translation.
Address translation tables
Each XAC has an address translation table that describes how to process addresses
exchanged on the access line. The table contains a variable number of translation
entries which allow each access line to be configured individually to handle specific
address formats. Figure 27.14-6 shows an example of the address translation table.
Figure 27.14-6: Address Translation Table Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
No.
Direction
Which
Addr
Ext
Prefix
Traps
IOCCCA
NUGDLL
T RM
Int
Prefix
-----------------------------------------------------------------------------------1
Both
Both
ix
<-->
ix
X.25 Service
(400)
F4F9-QUIT
F5F10-
27.14-31
Every entry in the address translation table contains two configurable prefix strings
for address digit translation, the External Prefix and Internal Prefix. The direction of
the call determines whether addresses are modified according to the two prefixes.
The Direction field and the corresponding arrows indicate how translation is
performed on the call setup and clearing packets.
Incoming (-->) refers to calls originating on the access line. These translation
entries apply only when the interface originates a call. The switch translates all
call setup and clearing packets received from and sent to the access line.
Outgoing (<--) refers to calls sent to the access line. These translation entries
apply only when the interface is the destination for a call. The switch translates
call setup and clearing packets sent to and received from the access line, with the
exception of calling addresses received from the access line. The switch never
translates calling addresses received from a destination access line, but rather
inserts the original internal calling address when transmitting call setup or
clearing packets to the originating interface.
Both (<-->) refers to calls that either originate on or are sent to the access line.
These translation entries apply whether the interface originates a call or is the
destination for a call. The switch translates call setup and clearing packets sent to
and received from the access line, with the exception of calling addresses in
packets received from the access line.
When the switch receives call setup or clearing packets from an X.25 access line,
addresses contained in the packets are compared to the External Prefix entries in the
address translation table. If a match occurs, the addresses are translated by replacing
the digits that match the External Prefix string with the corresponding Internal
Prefix digits. Translation is performed from left to right of the table.
When the switch sends call setup or clearing packets to an access line, addresses are
compared to the Internal Prefix entries in the table. On a successful match, the digits
matching the Internal Prefix string are replaced by the corresponding External Prefix
digits. Translation is performed from right to left of the table. In both cases, both the
calling and called addresses can be modified.
Address translation is performed in two stages. The first stage involves a
digit-by-digit comparison of an address contained in a packet against an input
pattern in the address translation table. The input pattern is the Internal or External
prefix, depending on the direction of the packet.
In the second stage, the output pattern is substituted for the portion of the address
(the prefix digits) that matched the input pattern. The parsing process compares
digits starting with the first digit of the address and moves from left to right. The
translation entry matching the most number of digits is selected.
Typically, an XAC with an X.121 address would be configured with external and
internal prefixes as shown in Table 27.14-3. The direction arrows indicate that the
entries are valid for both calls originating on and sent to the access line.
27.14-32
(400)
X.25 Serivce
Air
Internal
Prefix
Result
no
< >
ix3020
ix0
< >
ix
In this example, the null entry (ix) is used to either insert or remove digits. Calls to
addresses specified in national format do not begin with 0 and a match on the first
entry occurs. As a result, the switch inserts or removes the DNIC. International calls
match the second entry, in which case the switch inserts or removes the international
prefix digit.
The entries in the above example execute the following functions:
convert external addresses signalled from the access line to the internal address
format, and convert the internal address format to external address format
define the international prefix of the subscriber to be 0
define the DNIC of the subscriber to be 3020
allow the subscriber to signal addresses in two formats:
in national format, where only the NTN is signalled
in international format, where 0+DNIC+NTN is signalled
The Address Translation Table contains parameters that specify whether the calling
address, called address, or both addresses are translated, and for which direction of
the call. In order to be translated, an address must match one of the prefix strings,
and must also be eligible for translation according to its address type (calling or
called) and call direction (incoming or outgoing). For example, for translation to
occur on a called address in a call setup packet originating from an access line, the
address must match an External Prefix string, the Which_Addr field must be set to
Called or Both, and the Direction field must be set to Incoming or Both.
Table 27.14-4 lists examples of how external addresses are converted to internal
format by the address translation process.
X.25 Service
(400)
27.14-33
External Address
Format Signalled on
Link
(before translation)
Address
Translation Table
Entry
Internal Address
Format
(after translation)
SS
NTN
NTN+SS (1)
DNIC+NTN
DNIC+NTN+SS
P+DNIC+NTN
P+DNIC+NTN+SS
27.14-34
x <--> xDNIC+NTN
x <--> xDNIC
x <--> xDNIC
none required
none required
xP <--> x
xP <--> x
x, DNIC+NTN+SS
x, DNIC+NTN
x, DNIC+NTN+SS
x, DNIC+NTN
x, DNIC+NTN+SS
x, DNIC+NTN
x, DNIC+NTN+SS
Escape to E.164
P+0+CC+NSN (E.164
Digital)
P+9+CC+NSN (E.164
Analog)
xP0 <--> e
xP9 <--> m
e, CC+NSN
m, CC+NSN
Non-standard escape to
ISDN or X.32
P+77+NSN
e, CC+NSN
(400)
X.25 Serivce
Signalling Method
External Address
Format Signalled on
Link
(before translation)
Address
Translation Table
Entry
Internal Address
Format
(after translation)
SN
1+NSN
011+CC+NSN
e <--> eCC+NDC
e1 <--> eCC
e011 <--> e
e, CC+NSN
e, CC+NSN
e, CC+NSN
Escape to X.121
0+DNIC+NTN
e0 <--> x
x, DNIC+NTN
Non-standard examples
75+NSN
76+CC+NSN
8+NTN (X.121)
e, CC+NSN
e, CC+NSN
x, DNIC+NTN
Notes
1. In this case a length of up to 14 address digits is permitted for the NTN+SS.
2. Up to 12 address digits are permitted. This increases to 15 digits after December 31, 1996.
Wildcard characters
The wildcard character (?) is used in External and Internal Prefix strings to facilitate
digit manipulation. In most cases, the number of wildcard characters in the External
Prefix and Internal Prefix strings must be the same. The one exception allows
wildcard characters to appear only in the Internal Prefix string, but the type of
address must be calling and the direction must be outgoing. This configuration is
typically used for gateway links.
When wildcard characters appear in a translation entry, the switch translates calls
according to the following method: replace the nth wildcard digit in the output
pattern with the packet address digit that is in the same position as the nth wildcard
digit in the input pattern.
Table 27.14-5 shows examples of digit substitution and removal.
X.25 Service
(400)
27.14-35
Direction
Internal
Prefix
Result
Address
Type
Input Address
From Link
Resulting
Output
Address
Comments
x1?34
<-->
x1?99
Called
x12345678
x12995678
x1?34
-->
x199
Both
x12345678
x1995678
x1?3?5
<-->
x1?3?9
Called
x12345678
x12349678
x1?
<-->
x1
Both
x12345678
x01
<--
x????
Calling
x12345678
translation is not
performed on calling
addresses received
from a destination link
Call screening
The address translation table also contains parameters that permit call screening
options to be set. The call trap function provides a means of clearing a call, raising
an alarm or both when an address in a call setup or clearing packet matches a table
entry. There is one trap parameter for each address type and direction combination:
Trap Incoming Called, Trap Incoming Calling, Trap Outgoing Called, and Trap
Outgoing Calling. The Trap Action parameter specifies the action to take, also called
a treatment.
The trap parameters can be used to assign the Incoming Calls Barred and Outgoing
Calls Barred facilities to access lines, and to provide network security by restricting
calls to and from particular addresses or ranges of addresses.
27.14.10
27.14-36
(400)
X.25 Serivce
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Entry Number
External Prefix
Internal Prefix
Direction
Which Address
Trap Incoming
Trap Outgoing
Trap Action
:1
:ix
:ix
:Both
:Both
Calling
Calling
Clear Call
:No
:No
:No
Called
Called
Cause Alarm
:No
:No
:No
F1-EXT_PREFIX
F5-SCREENING
F6-DELETE
F2-INT_PREFIX
F3-DIRECTION
F4-WHICH_ADDR
F7-MORE
F8-CANCEL
F9-QUIT
F10-
27.14.11
X.25 Service
(400)
27.14-37
Entry Number
The entry in the address translation table.
Range
1 to 256
Default
None
27.14-38
(400)
X.25 Serivce
Direction
This parameter specifies whether the switch attempts address matching on calls
originated by the access line, sent to the access line, or both. For an address to be
translated according to the table entry, the call direction must match the Direction
parameter, and the address must match a prefix string.
Incoming specifies that the entry applies only to calls originated by the access line.
The switch performs address matching on all call setup and clearing packets sent to
and received from the access line.
Outgoing specifies that the entry applies only to calls sent to the access line. The
switch performs address matching on all call setup and clearing packets sent to the
access line, and on called addresses received from the access line. The switch does
not perform address matching on calling addresses received from the access line.
Both specifies that the entry applies to calls originated by and sent to the access line.
Options
Incoming, Outgoing or Both
Default
Both
Which Address
This parameter specifies whether the switch attempts address matching on the
calling address, called address, or both addresses contained in call setup and
clearing packets. An address must match both the prefix string and the Which
Address parameter in a table entry in order to be translated according to that table
entry.
Called specifies that the entry applies only to called addresses.
Calling specifies that the entry applies only to calling addresses.
Both specifies that the entry applies to both called and calling addresses.
Options
Called, Calling or Both
Default
Both
X.25 Service
(400)
27.14-39
27.14-40
(400)
X.25 Serivce
Options
Yes or No
Default
No
X.25 Service
(400)
27.14-41
Which
Ext
Int
Addr
Prefix
Prefix
------------------------------------------------------------1
Incoming
Called
ix3022
-->
ix2624
Incoming
Calling
ix3023
-->
ix2624
Outgoing
Called
ix3024
<--
ix2624
Outgoing
Calling
ix3025
<--
ix2624
An external prefix can appear only once for each direction when the address type is
called. For example, the following entries are valid, but the external prefix ix3022
cannot appear again in the table.
DirecNo. tion
Which
Ext
Int
Addr
Prefix
Prefix
------------------------------------------------------------1
Incoming
Called
ix3022
-->
ix5555
Outgoing
Called
ix3022
<--
ix6666
An external prefix cannot appear more than once when the address type is calling
and the direction is incoming, but can appear multiple times when the address type
is calling and the direction is outgoing. This is permitted because the switch never
translates calling address received from destination access lines. For example, all of
the following entries are valid.
DirecNo. tion
Which
Ext
Int
Addr
Prefix
Prefix
-------------------------------------------------------------
27.14-42
Incoming
Calling
ix3022
-->
ix5555
Outgoing
Calling
ix3022
<--
ix6666
Outgoing
Calling
ix3022
<--
ix7777
Outgoing
Calling
ix3022
<--
ix8888
(400)
X.25 Serivce
Use of wildcards
The number of wildcard characters in the External Prefix and Internal Prefix strings
must be the same. The one exception is when the address type is calling and the
direction is outgoing, wildcard digits may appear in the internal prefix only.
Call screening parameters
At least one of the Trap Action parameters must be set to Yes if any of the following
parameters are set to Yes:
X.25 Service
(400)
27.14-43
<entry_no.>
MORE
TRAP_ACTN
<addr_prefix>
INCOMING OUTGOING
NEW_ENTRY
CLEAR_CALL ALARM
BOTH
YES/NO
CALLING
TRP_INC_CD
CALLED
BOTH
TRP_INC_CG
TRP_OUT_CD TRP_OUT_CG
YES/NO
SK000423
where
xac is 1 to 128 for X.25 FRE cards or 1 to 992 for PE cards
entry_no. is an address translation table entry number (1 to 256)
addr_prefix is the translation prefix string (i or n, x, e, or m, and 0 to 19 digits or wildcard characters [?])
27.14.12
Resetting XACs
The reset command allows you to reset an XAC to the default configuration values.
All NUAs assigned to the XAC are deleted, and the XAC maintenance state resets to
enabled.
To reset an XAC
CONFIG X25_ACCESS XAC <xac> RESET
where xac is 1 to 128 for X.25 FRE cards and 1 to 992 for PE cards
27.14-44
(400)
X.25 Serivce
27.15
NUA Parameters
This chapter describes how to configure NUAs.
27.15.1
Understanding NUAs
An NUA is an X.121 or E.164 address and the call subscription options associated
with that address. You define X.121 addresses in international data number format
(DNIC+NTN), and E.164 addresses in international E.164 number format
(CC+NSN). Both of these formats correspond to the internal address format used in
the address translation table for the XACs. Figure 27.15-1 shows the formats.
Figure 27.15-1: X.121 and E.164 Address Formats
International data number format
DNIC
ZXXX
NTN
Up to 10 digits
NSN
+
NDC
SN
Once you define an NUA, you must assign it to an XAC interface; NUAs cannot exist
independently in the database. The first NUA assigned to an XAC is the default
NUA for the access line; the switch uses the parameters of the default NUA when
the DTE does not signal a calling address in call setup packets. If the XAC supports
multiple NUAs, you can change the default NUA at any time simply by identifying
a different NUA as the default.
X.25 Service
(400)
27.15-1
27.15.2
Configuration Overview
To completely configure an NUA, you must do the following:
1.
2.
3.
Configure the call subscription options and facilities for the NUA, including:
27.15.3
section 27.15.7)
CUG-related parameters, if CUG subscription is required (see
section 27.15.10)
default flow control and throughput class values (see section 27.15.13)
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
27.15-2
(400)
:x302011888866 (default)
:--:--:
:No
F4-AGENTS
F9-QUIT
F5F10-
X.25 Serivce
27.15.4
data number format (DNIC+NTN). The first digit of an X.121 address cannot be
0 or 9.
To define a digital E.164 address, enter e and 1 to 19 digits in international E.164
number format (CC+NSN).
To define an analog E.164 address, enter m and 1 to 19 digits in international
E.164 number format (CC+NSN).
Range
NPI (x, e, or m) and 1 to 19 digits in international address format
Default
None
X.25 Service
(400)
27.15-3
The first NUA assigned to an XAC is the default NUA. See the subsection Default
NUA for more information.
Range
1 to 992 for PE cards
1 to 128 for X.25 FRE cards
Default
None
Range
0 to n alphanumeric characters, where n is the value of the accounting parameter,
Optional User Defined Data Length (see section 27.10.4 for information).
Default
None
Accounting Activation
This parameter specifies whether the switch generates accounting records for all
SVCs associated with this NUA.
The switch-wide accounting parameters Intermediate Record Interval and
Collection Interval determine how often the switch generates accounting records.
Options
Yes or No
Default
No
27.15-4
(400)
X.25 Serivce
Hot Billing
This parameter specifies whether the switch sets a hot billing flag on accounting
records generated for this NUA. The data collector and billing system provide
expedited processing for records that have the hot billing flag set.
Options
Yes or No
Default
No
You cannot change an address after the NUA is assigned to an XAC. You must
X.25 Service
delete the NUA, redefine the address, and assign it to the XAC.
NUAs cannot exist in the database unless they are assigned to XACs. You cannot
define a block of NUAs and assign them at a later date.
An NUA cannot be a hunt group address or hunt group redirection address.
(400)
27.15-5
ASSIGN_TO
USER_DATA
<xac>
<user_string>
ACCOUNTING
ACTIVATE
PERIODIC HOT_BILLING
YES/NO
SK000424
where
address is the NPI and 1 to 19 digits in X.121 or E.164 format
xac is a valid XAC
user_string is 0 to 24 alphanumeric characters
27.15-6
(400)
X.25 Serivce
27.15.5
For information about CUGs and CUG-related facilities, see section 27.15.8.
Charging facilities
Charging facilities are used to permit or restrict reverse charging and local charging,
and to allow DTEs to request and receive charging information.
X.25 Service
(400)
27.15-7
B
Switch
1
Switch
2
Switch
3
7526
The CLAMN facility provides notification when a successful call redirection occurs.
When a calling DTE subscribes to this facility, the originating switch provides the
calling DTE with a Call Connected or Clear Indication packet containing the reason
why the called address in the packet is different from that signalled by the calling
DTE.
27.15-8
(400)
X.25 Serivce
The Call Redirection facility preserves subaddress digits in the called address and
allows for cases where the configured called address and redirection address are
different lengths. The following example describes how addresses are substituted:
Configured destination address: 1222
Configured redirected address: 133
Actual called address: 12225 (5 is a subaddress digit)
Result after redirection: 1335
The Call Redirection facility operates according to the following rules.
The Call Redirection facility does not violate the integrity of the CUG facility. The
27.15.6
switch always checks the CUG subscription options of the originally called DTE,
and allows redirection only if the CUG subscription options would have allowed
the incoming call. When a redirected call reaches the alternate DTE, the CUG
subscription options of that DTE are also checked, and the call is accepted or
cleared based on those options. The switch performs these checks regardless of
whether the originally called DTE and alternate DTE are on the same switch or
different switches.
A call can be redirected only once.
Call redirection indication is included in the accounting record.
Call redirection addresses are configured and displayed in the internal address
format.
charging facilities
fast select facilities
TOA/NPI options
call redirection and notification facilities
NUI subscription options
Figure 27.15-4 shows the NMTI display for the charging facilities.
X.25 Service
(400)
27.15-9
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
:No
:No
:No
:No
F5F10-CONTINUE
27.15.7
27.15-10
(400)
X.25 Serivce
Options
Yes or No
Default
No
X.25 Service
(400)
27.15-11
Options
Yes or No
Default
No
27.15-12
(400)
X.25 Serivce
The called DTE can respond with a Call Accepted or Clear Request packet
containing a called or clear user data field, respectively, of up to 128 octets. If the call
is connected, the called DTE can subsequently transmit a Clear Request packet with
a clear user data field of up to 128 octets.
The DCE mediates by transmitting the called or clear user data fields in Call
Connected and Clear Indication packets, respectively.
Accept the default (No) if the facility is not required.
Options
Yes or No
Default
No
Default NUA
This parameter specifies whether this NUA is the default NUA for the XAC. When
a subscriber does not specify the calling address in a Call Request packet, the switch
inserts the default NUA as the calling address.
You can only designate one NUA as the default. The first NUA assigned to an XAC
automatically becomes the default NUA. If you subsequently configure another
NUA as the default, the switch automatically changes the configuration of the
previous default NUA so that it is no longer the default.
Options
Yes or Undo
Default
None
X.25 Service
(400)
27.15-13
Default
No
Redirection Address
This parameter specifies a valid X.121 or E.164 address used for call redirection.
Once you define a redirection address, the Call Redirection facility is enabled and
incoming calls for this NUA are redirected to the alternate address when the NUA
is busy or out of service. If no redirection address is defined, the Call Redirection
facility is disabled and call redirection is never performed.
You define a redirection address by specifying the NPI and entering the address in
international format. See the subsection Network User Address in section 27.15.4
for information about address formats.
The redirection address can be either another NUA or a hunt group address, and can
be on the same switch or a remote switch. An X.121 NUA can have an E.164
redirection address, and an E.164 NUA can have an X.121 redirection address.
Unlike an NUA, the switch does not automatically check the GAT to determine if an
address prefix exists for the redirection address. You must ensure that the GAT
contains an entry that corresponds to the redirection address.
Range
NPI (x, e, or m) and 1 to 19 digits in X.121 or E.164 address format
Default
None
Signal CRN
This parameter specifies whether to signal the Call Redirection Notification facility
when a call is redirected. This facility indicates to the alternate DTE that the call has
been redirected, the reason for the redirection, and the original called DTE address.
27.15-14
(400)
X.25 Serivce
If the Packet Layer Interface Type is DCE, the CRN facility is included in the
Incoming Call packet. If the Packet Layer Interface Type is DTE, the CRN facility is
included in the Call Request packet; this can occur when the calling DTE is a private
X.25 network.
If the Packet Layer Interface Type is DCE and the parameter Suppress Called
Address is set to Yes, CRN is disabled regardless of whether this parameter is set to
Yes or No.
Options
Yes or No
Default
No
Signal CLAMN
This parameter specifies whether to signal the Called Line Address Modification
Notification facility when a call is redirected. This facility indicates to the calling
DTE why the called address is different from the one originally signalled by the
calling DTE.
If the Packet Layer Interface Type is DCE, the CLAMN facility is included in the Call
Connected or Clear Indication packet. If the Packet Layer Interface Type is DTE, the
CLAMN facility is included in the Call Accepted or Clear Request packet.
When the Suppress Called Address parameter is set to Yes for the network layer,
CLAMN is disabled regardless of whether this parameter is set to Yes or No.
Options
Yes or No
Default
No
Call Deflection
This release of MainStreet X.25 does not support call deflection.
NUI Subscription
This parameter specifies whether the NUI Subscription facility is enabled for the
NUA. This facility allows a DTE to include the NUI Selection facility in Call Request
packets. The NUI Selection facility enables the DTE to specify which NUI and
password it is using for a particular call.
X.25 Service
(400)
27.15-15
When this parameter is set to Yes, the calling DTE has the option of signalling the
NUI Selection facility in the Call Request packet, the network does not absolutely
require the facility to be present.
If this parameter is set to No and the calling DTE does signal the NUI Selection
facility, the switch clears the call.
Options
Yes or No
Default
No
27.15-16
(400)
X.25 Serivce
X.25 Service
(400)
27.15-17
Set the Signal CLAMN parameter to No when the network layer parameter
Suppress Called Address is set to Yes.
The Call Redirection facility does not violate the integrity of the CUG facility.
Change impact and activation
You can change the values of NUA subscription option parameters at any time with
no disruption of service. The changes are effective for the next call.
27.15-18
(400)
X.25 Serivce
CHARGING
FAST_SEL
CUG
CUG_OPT ADDRESSING
REDIRECTN
MORE
NUI
DEFLT_NUA TOA_NPI
CL_ON_FAIL
YES
YES/NO
RED_ADR
DELETE_RED
SIG_CRN
SIG_CLAMN DEFLECTION
<crd_address>
YES/NO
INC_ACCEPT
RESTRICT
UNRESTRICT
YES/NO
SUBSCRIPTN
DEF_FORMAT
VALIDATN
NON_STANDD
STANDARD/NON_STANDD
YES/NO
REV_ACCEPT
LOC_PRVENT
INFO
CODING
1ST_FIELD
1ST_LENGTH
IA5/BCD
NUI/PASSWORD
<length>
INFO_REQ
YES/NO
SK000425
where
address is a valid X.121 or E.164 address (1 to 19 digits)
crd_address is the address to which a redirected call is sent (1 to 19 digits)
length is 1 to 21 characters
X.25 Service
(400)
27.15-19
27.15.8
Understanding CUGs
A CUG is a specific set of NUAs to, from, or to and from which access is restricted.
CUG-related facilities provide a way to create multiple virtual private networks
within an X.25 network. Different combinations of access restrictions can be used to
control communication between members and non-members.
Each CUG to which an NUA belongs is identified by a CUG index number, which
ranges from 0 to 99. When a CUG member originates a call, the subscriber uses the
index number to signal the destination CUG. At the switch, the index number is
mapped to an interlock code which uniquely identifies the CUG in the network. This
allows different subscribers to use different index numbers to identify the same
CUG.
Figure 27.15-5 shows how different DTEs can use different index numbers to signal
the same CUG. For example, DTE A and DTE C use index number 2 to signal CUG
X, which is identified by interlock code 100, while DTE B uses index number 5 to
signal the same CUG. DTEs D, E, and F use index numbers 99, 1, and 55 respectively
to signal CUG Z. DTEs A and F use index numbers 6 and 42 respectively to signal
CUG Y.
Figure 27.15-5: CUG Example
DTE A
DTE B
Index
I/L Code
I/L Code
Index
2
6
100
200
100
CUG Y
Interlock code 200
Members = DTE A
DTE F
I/L Code
Index
100
CUG X
Interlock code 100
Members = DTE A
DTE B
DTE C
DTE C
DTE D
CUG Z
Interlock code 1234
Members = DTE D
DTE E
DTE F
DTE F
Index
I/L Code
42
55
200
1234
I/L Code
Index
1234
99
DTE E
I/L Code
Index
1234
1
8666
27.15-20
(400)
X.25 Serivce
MainStreet X.25 supports basic CUG membership and the following CUG-related
facilities and options:
preferential CUG
incoming or outgoing calls barred within a CUG
CUG with outgoing access and CUG with incoming access
The basic CUG facility permits members to communicate with each other, but
precludes communication with non-members. Users that subscribe to the basic CUG
facility are implicitly assigned the CUG Selection facility, which permits the calling
DTE to specify the CUG selected for a virtual call.
27.15.9
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
X.25 Service
F2-BARRING
F7-
F3-PREF
F8-CANCEL
(400)
F4-DELETE
F9-QUIT
F5F10-PROCEED
27.15-21
CUG
CUG_OPT
SK000426
27.15.10
Configuring CUGs
Membership in a CUG is established by associating the NUA with a CUG index, and
configuring the subscription options.
The parameters CUG With Incoming Access, CUG With Outgoing Access, and
Signal Preferential CUG are configured once for each NUA requiring CUG
membership. The other parameters must be configured for every CUG to which an
NUA belongs.
This section describes the CUG parameters and provides configuration guidelines.
The parameters are ordered as they appear on the NMTI display.
CUG Index
This parameter specifies the index number associated with a particular CUG
interlock code. Each CUG to which a NUA belongs is identified by a CUG index
number, which is a number ranging from 0 to 99. The CUG index number is in turn
mapped to an interlock code which uniquely identifies the CUG in the network.
When a CUG member originates a call, the subscriber uses the index number to
signal the destination CUG, rather than the interlock code.
Range
0 to 99
Default
None
Interlock Code
This parameter specifies the network-wide interlock code that uniquely identifies
the CUG.
27.15-22
(400)
X.25 Serivce
Range
0 to 65 535
Default
None
Barring
This parameter specifies the call barring facilities that apply to the NUA within the
CUG. No barring specifies that the DTE can originate calls to, and receive calls from,
other DTEs in this CUG.
Select Incoming Calls Barred to enable the Incoming Calls Barred Within a CUG
facility, which prevents the DTE from receiving incoming calls from other DTEs in
this CUG.
Select Outgoing Calls Barred to enable the Outgoing Calls Barred Within a CUG
facility, which prevents the DTE from originating calls to other DTEs in this CUG.
Options
Incoming Calls Barred, Outgoing Calls Barred, or No Barring
Default
No Barring
Preferential CUG
This parameter specifies whether this CUG is the preferential CUG. The preferential
CUG is used as the default when a specific CUG is not signalled through one of the
selection facilities. When the DTE places a call request, the preferential CUG is
selected automatically if the DTE does not request a particular CUG.
When an NUA belongs to a CUG but does not subscribe to either the CUG with
Incoming Access or CUG with Outgoing Access facility, a preferential CUG must be
assigned.
Options
Yes or No
Default
No
X.25 Service
(400)
27.15-23
originate calls to, and receive calls from, other members of the same CUG
receive calls from DTEs that do not belong to any CUG
receive calls from DTEs that belong to other CUGs and subscribe to the CUG with
Outgoing Access facility
When this parameter is set to No, the DTE can communicate only with members of
the same CUG.
Options
Yes or No
Default
No
originate calls to, and receive calls from, other members of the same CUG
originate calls to DTEs that do not belong to any CUG
originate calls to DTEs that belong to other CUGs and subscribe to the CUG with
Incoming Access facility
Users that subscribe to the CUG with Outgoing Access facility are implicitly
assigned the CUGOA Selection facility, which permits the calling DTE to specify the
CUG selected for a virtual call.
When this parameter is set to No, the DTE can communicate only with members of
the same CUG.
Options
Yes or No
Default
No
27.15-24
(400)
X.25 Serivce
Options
Yes or No
Default
No
To configure CUGs
CONFIG X25 ACCESS NUA <address> X25 SUBS_OPT
CUG
CUG_OPT
<index>
INC_ACCESS
OUT_ACCESS
SGNAL_PREF
YES/NO
INTERLOCK
BARRING
<code>
INC_BAR
PREF
DELETE
YES/NO
OUT_BAR
NO_BAR
SK000427
where
address is a valid NUA (1 to 19 digits)
index is the CUG index (0 to 99)
code is the interlock code assigned to the CUG (0 to 65 535)
X.25 Service
(400)
27.15-25
27.15.12
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
Send
----
:128
:128
:2
:2
:64000
:64000
27.15-26
F2-WIN_SIZE
F7-
F3-THRU_PUT
F8-
(400)
F4F9-QUIT/SAVE
F5F10-CONTINUE
X.25 Serivce
27.15.13
X.25 Service
(400)
27.15-27
Default
128 bytes
27.15-28
(400)
X.25 Serivce
Values greater than 192 000 b/s are permitted only when the Throughput Class
Negotiation Format parameter is set to Extended.
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
Default
64 000 b/s
Default Throughput Class values greater than 192 000 b/s are permitted only
X.25 Service
when the Throughput Class Negotiation Format parameter is set to extended. See
section 27.14.8.
The values of the default send and receive packet size parameters must match
one of the allowable packet sizes configured for the XAC to which the NUA is
assigned.
The values of the default send and receive window size parameters must be less
than the Packet Sequence Numbering value configured for the XAC to which the
NUA is assigned.
(400)
27.15-29
PKT_SIZE
RECV
SEND
<pkt_size>
WIN_SIZE
RECV
SEND
<win_size>
THRU_PUT
RECV
SEND
<tput_class>
SK000428
where
address is a valid NUA (1 to 19 digits)
pkt_size specifies the default packet sizes (16, 32, 64, 128*, 256*, 512*, 1024, 2048, or 4096 bytes)
win_size specifies the default window sizes (1 to 127, 7*)
tput_class specifies the default throughput classes (75 to 215 b/s, 64 000*)
27.15-30
(400)
X.25 Serivce
27.16
27.16.1
27.16.2
X.25 Service
Copy Format
Example
Single XAC
X1 TO X3
Set of XACs
Range of XACs
X1 TO X7..X15
(400)
27.16-1
Figure 27.16-1 shows an NMTI display in which the configured values for source
XAC 123 are copied to target XACs 124, 127, and 135. Because the source XAC had
an assigned NUA, each of the target XACs must be assigned an NUA.
Figure 27.16-1: COPY Command NMTI Display
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
F2F7-
F3F8-CANCEL
F4F9-QUIT
F5F10-
If a target XAC has an NUA assigned to it that is a member of a hunt group, the
NUA cannot be deleted. The copy process aborts at this point.
The redirection addresses configured for source XACs are not copied to the target
XACs.
27.16-2
(400)
X.25 Serivce
X.25 Service
(400)
27.16-3
27.17
X.25 PVCs
This chapter describes how to configure X.25 PVCs.
27.17.1
X.25 Service
(400)
27.17-1
The following sequence describes how a 36120 MainStreet X.25 network establishes
a PVC for DTEs supported by different switches.
1. When an XAC that supports PVCs goes in service, the switch generates an
internal PVC call setup packet and sends it to the destination switch.
2. Upon receipt of the internal call setup packet, the destination switch determines
if the destination access line is in service.
a. If the destination access line is in service, the switch generates an internal PVC
call accept packet and sends it to the originating switch. The switch also sends a
Reset Indication packet to the destination DTE with reset cause 09h Remote DTE
Operational. Go to number 4.
b. If the destination access line is not in service, the switch generates an internal
clear request and sends it to the originating switch.
3. The switch that supports the PVC originator retries the PVC establishment
procedure three times at 15-second intervals, after which it retries continually at
60 second intervals. This process prevents the originating switch from flooding
the network with call setup packets when the destination access line is out of
service.
4. When the originating switch receives the internal call accept packet, it sends a
Reset Indication packet to the local DTE with reset cause 09h Remote DTE
Operational. The PVC is now established.
In the case of a local PVC, where the same switch serves both DTEs, the switch does
not use call setup packets. However, the network layer follows the same process
described in number 3 if the destination access line is down.
27.17-2
(400)
X.25 Serivce
27.17.2
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
X.25 PVCs
Local Address
Local LCN
Remote Address
Remote LCN
---------------------------------------------------------------------x30220110002
1
x30220330001
1
X.25 Service
(400)
F4F9-QUIT
F5F10-
27.17-3
SHOW_ALL
<local_nua>
SHOW_GROUP
PREVIOUS
NEXT
SORT_LOCAL/
SORT_REMOT
SK000429
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
X.25 PVC
--------------------------------------------------------------Local Address
:x3020441201
(Originator)
Local LCN
:4
Remote Address
:x3020457205
Remote LCN
:32
Accounting Activation
:No
Periodic Accounting Activation
:No
D-Bit Allowed
:No
Send
---:128
:128
:2
:64000
Receive
------:128
:128
:2
:64000
F1-REMOTE_ADR
F6-DELETE
27.17-4
F2-REMOTE_LCN
F7-MORE...
(400)
F3-PKT_SIZE
F8-CANCEL
F4-WIN_SIZE
F9-QUIT
F5-THRU_PUT
F10-
X.25 Serivce
27.17.3
The Packet Sequence Numbering parameter must be greater than the send
and receive window sizes configured for the PVC.
The send and receive packet sizes configured for the PVC must be in the
2.
3.
4.
If both ends of the PVC are on the same switch, configure the parameters
once.
b.
If the local and remote ends are on different switches, configure the
parameters at each switch.
Table 27.17-1 shows an example of the PVC parameters that must agree when the
local and remote ends are on different switches, and the PVC does not support D-bit
packets.
X.25 Service
(400)
27.17-5
Endpoint A
Endpoint B
Local Address
x1111
x2222
Local LCN
10
20
Remote Address
x2222
x1111
Remote LCN
20
10
Originating End
Local
Remote
The following subsections describe the X.25 PVC parameters and provide
configuration guidelines. The parameters are ordered as they appear on the NMTI
display.
Local Address
This parameter specifies the NUA of the DTE that is the local end of the PVC. The
NUA must already be configured on the switch.
Range
NPI plus 1 to 19 digits in X.121 or E.164 address format
Default
None
Local LCN
This parameter specifies the LCN used on the local access line to set up the PVC. This
LCN must be in the range specified by the Number of PVCs parameter at the
network layer of the associated XAC. The LCN cannot already be in use.
When the endpoint DTEs are on different switches, the Local LCN parameter
configured for the local end must match the Remote LCN parameter configured at
the remote end. For example:
27.17-6
(400)
X.25 Serivce
Remote Address
This parameter specifies the NUA of the DTE that is the remote end of the PVC. If
the endpoint DTEs are on the same switch, the NUA must already be configured on
the switch.
Range
NPI plus 1 to 19 digits in X.121 or E.164 address format
Default
None
Remote LCN
This parameter specifies the LCN used on the remote access line to set up the PVC.
This LCN must be in the range specified by the Number of PVCs parameter at the
network layer of the remote XAC. The LCN cannot already be in use.
When the endpoint DTEs are on different switches, the Remote LCN parameter
configured for the local end must match the Local LCN parameter configured at the
remote end. For example:
Accounting Activation
This parameter specifies whether the switch generates accounting records for the
PVC. The frequency and type of accounting record is determined by the switch-wide
accounting parameters rather than the NUA accounting parameters.
This parameter overrides the Accounting Activation parameter configured for the
NUA.
Range
Yes or No
X.25 Service
(400)
27.17-7
Default
No
D-Bit Allowed
This parameter specifies whether the PVC supports D-bit calls. When you set this
parameter to Yes at one or both ends of the PVC, both DTEs can send data packets
with the D-bit set.
Even after a PVC is configured to support D-bit calls, the switch continues to
recognize the significance of the D-bit in the GFI; data packets with the D-bit set are
acknowledged end-to-end after being acknowledged by the receiving DTE.
Range
Yes or No
Default
No
27.17-8
(400)
X.25 Serivce
Options
16, 32, 64, 128, 256, 512, 1024, 2048, or 4096 bytes
Default
128 bytes
X.25 Service
(400)
27.17-9
27.17-10
(400)
X.25 Serivce
This parameter overrides the Default Receive Window Size parameter configured
for the local NUA.
Range
1 to 7 (if the Packet Sequence Numbering parameter is set to 8) or 1 to 127 (if the
Packet Sequence Numbering parameter is set to 128)
Default
2
X.25 Service
(400)
27.17-11
Default
64 000 b/s
Originating End
This parameter specifies which end of the PVC (local or remote) is the originator.
The originator is responsible for retrying the establishment of a PVC, resolving call
collisions, and generating accounting records. If the local and remote DTEs reside on
the same switch, the local address is automatically the originator; the originator is
meaningful only for the purposes of call accounting. If the local and remote DTEs
reside on different switches, then this field must be set differently at each end.
Options
Local or Remote
Default
None
Before you configure a local PVC, you must configure both NUAs on the switch.
Although the switch permits you to specify a remote NUA that does not exist on
the switch (to allow for remotely switched PVCs), the switch establishes local
PVCs only if the NUAs exist before the PVC is configured.
The values of the send and receive packet size parameters must match one of the
allowable packet sizes configured for the associated XAC.
Send and receive throughput class values greater than 192 000 b/s are permitted
only when the Throughput Class Negotiation Format parameter for the
associated XAC is set to extended. See section 27.14.8.
The values of the send and receive window size parameters must be less than the
Packet Sequence Numbering value configured for the associated XAC.
If the D-bit Allowed parameter is set to Yes, the packet and window sizes at the
local and remote ends must match.
Call redirection does not apply to PVCs. The call redirection address configured
for an NUA is ignored when a PVC is established.
27.17-12
(400)
X.25 Serivce
Note
To optimize switch resources, routinely delete any PVC configurations that are not
required. When the access line is in service, the switch continually attempts to
establish a configured PVC.
REMOTE_ADR
REMOTE_LCN
<remote_nua>
<remote_lcn>
PKT_SIZE
WIN_SIZE
SEND
THRU_PUT
RECV
<win_size>
LOCAL_RCV
LOCAL_SND
SEND
MORE
RECV
<tput>
REMOTE_RCV REMOTE_SND
<pkt_size>
ACCOUNTING
ACTIVATE
PERIODIC
YES/NO
ORIGINATE
DBIT
LOCAL/
REMOTE
YES/NO
SK000430
where
local_nua is a valid NUA (1 to 19 digits)
local_lcn is a valid PVC LCN
remote_nua is the NPI and 1 to 19 digits
remote_lcn is a valid PVC LCN
pkt_size specifies the default packet sizes (16, 32, 64, 128*, 256*, 512*, 1024, 2048, or 4096 bytes)
win_size specifies the default window sizes (1 to 127, 7*)
tput specifies the default throughput classes (75 to 215 b/s, 64 000*)
X.25 Service
(400)
27.17-13
27.17-14
(400)
X.25 Serivce
27.18
Hunt Groups
This chapter describes switch-wide hunt groups and how to configure them.
Although the notion of network-wide hunt groups is introduced in this chapter,
section 27.7.3 provides detailed network-wide hunt group information.
27.18.1
If the hunt group has a redirection address, the switch routes the call to that
address.
X.25 Service
(400)
27.18-1
Redirection addresses
You can assign a single redirection address to each hunt group. The redirection
address specifies an alternate address on another switch to which calls are routed
when all of the hunt group members are engaged. The redirection address can be
either an NUA or a hunt group address, but it cannot be a local address; that is, the
redirection address must be served by a remote switch.
For calls to a hunt group address, redirection can occur only to the hunt group
redirection address; the switch does not permit redirection from a hunt group
member NUA. While individual member NUAs can be assigned the Call
Redirection facility, the NUA redirection address is used only when the original
called address is that of the NUA.
Internodal hunting
The redirection address provides a means to achieve hunting between switches. If
all the members of the originally called hunt group are engaged, the local switch
redirects the call to the redirection address on the remote switch. Hunting across
switches is limited to two switches because calls can be redirected only once. When
the redirection address is a hunt group address, hunt group membership is
effectively extended beyond the limit of the card.
27.18-2
(400)
X.25 Serivce
27.18.2
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
F4F9-QUIT
F5F10-
Figure 27.18-2 shows all the members belonging to the hunt group identified by
address x3020447800.
X.25 Service
(400)
27.18-3
PA11-H1-00
Toronto:A
Redirection Address
Alarms:1
11-May-1997
8:35a
:---
F2-DEL_MEMB
F7-
F3-DELETE
F8-CANCEL
F4-REDIRECTN
F9-QUIT
F5F10-
SHOW_ALL
<address>
SHOW_MEMB
SK000431
where address is the X.121 or E.164 address that identifies the hunt group
27.18.3
27.18-4
1.
Configure the hunt group address as described in the procedure To add and
delete hunt group addresses.
2.
3.
(400)
X.25 Serivce
4.
Add the NUA to the hunt group as described in the procedure To add and
delete hunt group members.
The following subsections describe the hunt group parameters and provide
configuration guidelines.
data number format (DNIC+NTN). The first digit of an X.121 address cannot be
0 or 9.
To define a digital E.164 address, enter e and 1 to 19 digits in international E.164
number format (CC+NSN).
To define an analog E.164 address, enter m and 1 to 19 digits in international
E.164 number format (CC+NSN).
Range
NPI (x, e, or m) and 1 to 19 digits in X.121 or E.164 address format
Default
None
Redirection Address
This parameter specifies an X.121 or E.164 address to which calls are redirected
when none of the hunt group members are available. The redirection address cannot
exist on the same switch, it must be either an NUA or hunt group address on another
switch.
Range
NPI (x, e, or m) plus 1 to 19 digits in X.121 or E.164 address format
Default
None
X.25 Service
(400)
27.18-5
Range
NPI (x, e, or m) plus 1 to 19 digits in X.121 or E.164 address format
Default
None
members on PE cards.
The redirection address cannot be an NUA or hunt group address on the same
switch.
A call to a hunt group address can be redirected only to the hunt group
redirection address, and can be redirected only once.
The Link Layer Inactivity Timer (T3) should be set appropriately for all XACs
that have NUAs belonging to hunt groups. The optimum value of T3 depends on
the interface speed of the link and the need for quick detection when the link goes
down. For example, for a critical application running over a high-speed link, the
timer should be set to a relatively low value. See chapter 27.14 for information
about configuring link layer timers.
PROCEED
REDIRECT
DELETE
<rd_address>
PROCEED
SK000432
where
address is the X.121 or E.164 address that identifies the hunt group (NPI plus 1 to 19 digits in international
format)
rd_address is an X.121 or E.164 address for call redirection (NPI plus 1 to 19 digits in international format)
27.18-6
(400)
X.25 Serivce
ADD_MEMB
DEL_MEMB
<member_nua>
<member_nua>
SK000433
where
address is the address that identifies the hunt group (1 to 19 digits in E.164 or X.121 format)
member_nua is a valid NUA configured on the switch (1 to 19 digits in E.164 or X.121 format)
X.25 Service
(400)
27.18-7
27.19
27.19.1
X.25 Service
(400)
27.19-1
X.25 FRE
or PE card
2
m x n x 8 kb/s
3
1
X.25 DTE
= 1 to 31
= 1 to 8
= Direct circuit
7525
Configure the circuit on the data interface card or PRI card to which the X.25
device is connected.
2.
APPLI
I/F_SPEED
TRANSP_BW
DIRECT_CCT
<speed>
<bandwidth>
SK000434
where speed and bandwidth must match the interface speed configured in step 1 (m n 8 kb/s)
Connect the data interface circuit or PRI circuit to the direct circuit.
CONFIG CONNECT <sn-cc> TO_CIRCUIT <sn-cc> PROCEED
27.19-2
(400)
X.25 Serivce
Configure an XAC.
i.
Configure the link and network layer parameters, and the address
translation table for the XAC. See chapter 27.14.
ii.
Configure the NUA and assign it to the XAC. See section 27.15.4.
iii. Configure the NUA subscription options and facilities. See section 27.15.7.
5.
27.19.2
Encapsulated Access
Devices running at basic rate, super-rate, and n 8 kb/s subrate speeds can be
connected using the FRS card or a standards-compliant PAD/FRAD. Devices
running at subrate speeds other than n 8 kb/s must access the switch through the
FRS card.
X.25 Service
(400)
27.19-3
FRS card
X.25 FRE
or PE card
4
5
6
12
m x n x 8 kb/s
9
11
1
2
3
X.25 DTE
= 1 to 31
= 1 to 8
Configure the circuit on the data interface card or PRI card to which the X.25
device is connected.
2.
APPLI
I/F_SPEED
TRANSP_BW
FR_ENCAP
<speed>
<bandwidth>
SK000435
where speed and bandwidth must match the interface speed configured in step 1
(m n 8 kb/s)
See section 27.13.3 for more information.
3.
Connect the data interface or PRI circuit to the FRS encapsulation circuit.
CONFIG CONNECT <sn-cc> TO_CIRCUIT <sn-cc> PROCEED
27.19-4
(400)
X.25 Serivce
4.
APPLI
I/F_SPEED
STREAM
<speed>
SK000436
where speed must be at least the interface speed configured in step 1 (m n 8 kb/s)
5.
Configure a X.25 switch circuit as a frame stream, and set the interface speed
equal to the speed configured in step 4 (m n 8 kb/s).
6.
Connect the two frame stream circuits to set up the frame stream.
CONFIG CONNECT <frs_sn-cc> TO_CIRCUIT <fre_sn-cc> PROCEED
where
frs_sn-cc is the FRS circuit configured in step 4
fre_sn-cc is the X.25 FRE circuit configured in step 5
FRAME_SIZE
THRESHOLDS
X25_PKT_SZ
SK000437
FRAME_SIZE
THRESHOLDS
PROTOCOL
SK000438
X.25 Service
(400)
27.19-5
9.
Connect the encapsulation circuit to a DLCI on the frame stream circuit and set
the class of service parameters.
CONFIG CONNECT <cc> or <Scc-dlci>
TO_DLC
INFO_RATE
<cc> or <Scc-dlci>
SK000439
where
cc is the frame relay encapsulation circuit configured in steps 2 and 7 (0 31)
Scc-dlci is the frame stream circuit configured in steps 4 and 8, and a DLCI (16 to 1007)
FRAME_SIZE
THRESHOLDS
NUM_FLAGS
PROTOCOL
SK000440
Configure the link and network layer parameters, and the address
translation table for the XAC. See chapter 27.14.
ii.
Configure the NUA and assign it to the XAC. See section 27.15.4.
iii. Configure the NUA subscription options and facilities. See section 27.15.7.
12. Connect the XAC to the stream-DLCI, and set the class-of-service parameters.
CONFIG CONNECT <Xxac> TO <Scc-dlci> PROCEED
where
Xxac is the XAC configured in step 11
Scc-dlci is the frame stream circuit configured in steps 5 and 10, and the DLCI used in step 9
27.19-6
(400)
X.25 Serivce
The following procedure shows how to provision encapsulated access for subrate
X.25 devices. Connections are made to the FRS for frame relay encapsulation, then
to the X.25 switch for call processing and routing. The connection from the FRS to
the X.25 switch can be made within the node or to a remote node. In the latter case,
primary rate links must also be configured and connected between the nodes.
Figure 27.19-3 shows the circuits and connections that must be configured when the
FRS and X.25 switch are located on the same node. The numbers in the illustration
correspond to the step numbers in the procedure that follows.
Figure 27.19-3: Subrate Encapsulated Access
FRS card
X.25 FRE
or PE card
7
8
9
12
15
1.2 to 56 kb/s
2
1
14
6
X.25 DTE
Configure the circuit on the data interface card or PRI card to which the X.25
device is connected.
2.
3.
Configure the same FRS subrate circuit for frame relay encapsulation.
CONFIG CIRCUIT <sn-SRcc> FUNCTION APPLI FR_ENCAP
where sn-SRcc is the slot number and subrate circuit number used in step 2
X.25 Service
(400)
27.19-7
4.
HCM
DDS
X.50
SK000441
5.
6.
Connect the rate adapted circuit to the data interface or PRI circuit.
CONFIG CONNECT <ra_sn-cc> TO_CIRCUIT <sn-cc> PROCEED
where
ra_sn-cc is the slot number and circuit number configured in step 4
sn-cc is the slot number and circuit number configured in step 1
7.
APPLI
I/F_SPEED
STREAM
<speed>
SK000436
8.
Configure an X.25 switch circuit as a frame stream, and set the interface speed
equal to the speed configured in step 7.
9.
Connect the two frame stream circuits to set up the frame stream.
CONFIG CONNECT <frs_sn-cc> TO_CIRCUIT <fre_sn-cc> PROCEED
where
frs_sn-cc is the FRS circuit configured in step 7
fre_sn-cc is the X.25 FRE circuit configured in step 8
27.19-8
(400)
X.25 Serivce
FRAME_SIZE
THRESHOLDS
X25_PKT_SZ
SK000437
FRAME_SIZE
THRESHOLDS
PROTOCOL
SK000438
TO_DLC
INFO_RATE
<SRcc> or <Scc-dlci>
SK000445
where
SRcc is the subrate encapsulation circuit configured in steps 2, 3 and 10 (0 to 31)
Scc-dlci is the frame stream circuit configured in steps 7 and 11, and a DLCI (16 to 1007)
FRAME_SIZE
THRESHOLDS
NUM_FLAGS
PROTOCOL
SK000440
X.25 Service
(400)
27.19-9
Configure the link and network layer parameters, and the address
translation table for the XAC. See chapter 27.14.
ii.
Configure the NUA and assign it to the XAC. See section 27.15.4.
iii. Configure the NUA subscription options and facilities. See section 27.15.7.
15. Connect the XAC to the stream-DLCI, and set the class of service parameters.
CONFIG CONNECT <Xxac> TO <Scc-dlci> PROCEED
where
Xxac is the XAC configured in step 14
Scc-dlci is the frame stream circuit configured in steps 8 and 13, and the DLCI used in step 12
27.19-10
(400)
X.25 Serivce
27.20
27.20.1
existing X.25 network user and a new user of the 36120 MainStreet frame relay
network.
users on a non-36120 MainStreet X.25 network and 36120 MainStreet frame relay
users
X.25 to frame relay service interworking also allows new frame relay services to be
introduced into an existing X.25 network.
Service interworking
X.25 to frame relay service interworking allows devices running two different
protocols (X.25 and frame relay) to communicate with each other. To accomplish
data transfer, X.25 data packets are converted into frame relay frames when data is
transmitted from an X.25 DTE to a frame relay device. Conversely, frame relay
frames are converted into X.25 packets when data is transmitted from a frame relay
device to an X.25 DTE.
Figure 27.20-1 shows an example of a X.25 to frame relay service interworking
application.
X.25 Service
(400)
27.20-1
SVC
X.25
XAC
X.25
network
XFR
Frame relay
network
Frame
relay
link
XFR
X.25 SVC
Frame relay
PVC
9987
The figure shows the types of connections that are available on the two ends of the
service interworking virtual circuit. It is also possible to have an X.25 PVC connected
on the X.25 side. However, only one type of connection (either X.25 SVC or X.25
PVC) can be made to a service interworking circuit.
Network interworking
Service interworking should not be confused with network interworking
(encapsulation). Network interworking provides a method for communication
between two X.25 DTEs over a frame relay network. The entire packet (LAPB+data)
being transmitted is encapsulated by a frame relay header (using Annex G
encapsulation) and then transmitted over the frame relay network. Encapsulated
frames received by the destination device are decapsulated and the original packet
is delivered. See section 27.13.1 for detailed information on encapsulation.
Figure shows an example of encapsulated access using a PAD/FRAD.
27.20-2
(400)
X.25 Serivce
Frame
relay
LAPB
DCC
or
DNIC
or
PRI
card
X.25
switch
X.25
backbone
network
Frame relay
network
DTE
LAPB-encapsulating
PAD/FRAD
7551
XFR
X.25
X.25
LAPB
X.25
trunks
LAPB
X.25 DTE
PE
X.25
Frame
relay
X.25
trunks
PE
X.25 SVC/PVC
Frame
relay
Frame
relay
FRE
The X.25 network layer running on the X.25 switch acts as the interface for XFR
connection. For information on how to configure an XAC for XFR operation, see
section 27.20.6.
Frame loss
Packets arriving at the XFR XAC (for a definition, see section X.25 to frame relay
service interworking XAC) are processed and transmitted directly to the frame
relay PVC as frames. These frame relay frames are treated like any other data frames
within the frame relay network and may be subject to discard during congestion. To
handle frame discards, higher layer protocols between the X.25 and frame relay
devices are responsible for frame recovery.
X.25 Service
(400)
27.20-3
27.20.2
27.20-4
(400)
X.25 Serivce
The X.25 PVC connection remains established until it is deleted from the
configuration. If the frame relay PVC is deleted or lost, a reset request is made.
27.20.3
Call Management
An XFR XAC provides call setup and routing, data transfer, and call clearing
management for the duration of the call. Data transfer is terminated when the X.25
SVC is cleared, the X.25 PVC is reset or the frame relay PVC goes out of service.
Call setup
To set up an X.25 SVC to frame relay PVC call, the frame relay PVC connection must
be made before the X.25 SVC connection can be established. To set up an X.25 PVC
to frame relay PVC call, it does not matter which connection is established first. Data
transfer is initiated when the complete call path has been established.
An XFR XAC can be set up anywhere within a network as shown in Figure 27.20-4
does not necessarily have to reside on the same PE or FRE card as the DCE circuit.
Figure 27.20-4 shows an example of the call path from an X.25 DTE to a frame relay
device. XAC1 is configured for X.25 service type and has an NUA of X.121 111111.
XAC2 is configured for XFR service type and has an NUA of X.121 222222. The X.25
DTE establishes communication with the frame relay device by placing a call request
to the XFR. A call request with called address X.121 222222 arriving at XAC1 is
routed to XAC2 (XFR) using standard X.25 call routing techniques. When the call
arrives at the XFR, it is mapped to the frame relay device over the already connected
frame relay PVC. The XFR is now ready to transfer data between the two users.
Figure 27.20-4: End-to-end Call Path
XAC1
(X.25)
Frame
relay
X.25 DTE
Frame relay
device
XAC2 (XFR)
9883
X.25 Service
(400)
27.20-5
Call routing
An SVC session is established by either calling the address of the XFR or the hunt
group to which the XFR belongs. X.25 calls may be distributed across multiple XFR
XACs through the use of switch-wide or network-wide hunt groups. The XFR maps
an allocated LCN to the stream-DLCI pair and the session remains established until
the call is cleared by the remote DTE or the XFR XAC is disabled.
The XFR generates a request to tear down the X.25 SVC when the frame relay PVC
connection is lost.
Data transfer
Data packet transfer between an X.25 DTE and a frame relay device is performed by
removing the X.25 header from the data packet and inserting a frame relay header
when transmitting data from X.25 to frame relay. Conversely, the frame relay header
is removed and the X.25 header is inserted when transmitting data from frame relay
to X.25. The content of the data portion of the frame is not inspected and remains
unaltered. Figure 27.20-5 shows bidirectional XFR header conversion.
Figure 27.20-5: XFR Header Conversion
Flag
1 1
Flag
1 1
LCGN
DLCI
(low)
LCN
FECN
GFI
BECN
DLCI (high)
XFR
0
EA
X.25 to FR
service
interworking
PTI
EA
DE
C/R
Data
Data
CRC
Flag
CRC
Flag
X.25 data packet
9857
27.20-6
(400)
X.25 Serivce
Note
Ensure that the frame size is greater than the data packet size. When data is being
transferred from a frame relay device to an X.25 DTE, the data is segmented and
poses no problem. However, when data is transferred in the opposite direction if the
frame size is not greater than the user data size the frames are discarded.
Connection management
Connection management between an X.25 virtual circuit and a frame relay PVC is
handled by responding to messages received from the LMI implemented on the
frame relay network. It is capable of handling any frame relay PVC status and
configuration change, as well as any required frame relay link rerouting in the event
the connection becomes unavailable.
X.25 Service
(400)
27.20-7
Link 1
Link 2
FRAD
NNI
NNI
8230 MainStreet
X.25 DTE
XAC2
(XFR)
Within the example network, frame relay links 1 and 2 are configured with NNI
protocol. This configuration provides bidirectional status messaging capability
within the frame relay portion of the network.
If link 2 is lost while a call is active, a status change message is propagated towards
the XFR. When this message reaches the XFR XAC, a Frame Relay Reconnect
Timer is started.
If link 2 becomes available before the timer expires, the call status goes back to
Data Transfer and the timer is reset. If link 2 does not become available before the
timer expires, the PVC is deemed to be permanently lost and the call is cleared.
When the timer expires, a Frame Relay Link Not Available cause code message is
sent to clear the X.25 SVC or reset the X.25 PVC.
The frame relay PVC may be configured for rerouting by the MainStreetXpress
46020 Network Manager. In such cases, if the frame relay path is lost during data
transfer, the call is directed to the destination using an alternate path. If the call is
re-established prior to timer expiry, the timer is reset and normal network
operation continues. The call is cleared if the timer expires before alternate path
routing occurs.
Flow control
Flow control is applied only when data is being transferred from the XFR to an
X.25 DTE. It consists of frames being buffered in the To_X.25_Holding queue and
a frame relay flow control notification (BECN) bit being set on frames sent to the
frame relay device.
The closure of the X.25 window triggers flow control or the network layer is flow
controlled by the RTP. Frame relay frames arriving at a congested XFR are placed
in the To_X.25_Holding queue and labelled as frames waiting to be delivered. An
XFR will stay in a congested state until all packets in the holding queue are
delivered. The BECN bit is set on all frames transmitted back to the frame relay
device while the XFR is in a congested state.
27.20-8
(400)
X.25 Serivce
Alarm raising
Service interworking congestion alarming is monitored against a preconfigured SCT
value. Congestion analysis is performed each time a frame is added to or removed
from the congestion queue. An XFR Congested alarm is raised when the SCT value
is met or exceeded.
Alarm clearing
The XFR Congested alarm remains raised until the congestion level falls below a
preconfigured MCT value or until all of the frames with a set DE bit have been
de-queued or discarded. When the congestion is cleared, the XFR Congestion
Cleared alarm is raised.
Accounting
Accounting records are produced at one of the two XACs involved the X.25 virtual
circuit. The records are normally created at the calling end, although records are
produced at the called XAC (XFR XAC) in the case of a reverse charge call.
Accounting records for service interworking connections are generated using the
same methods as is done for normal X.25 calls. For service interworking calls, either
the local or remote Service Type field contained in the accounting record indicates
that an XFR XAC is being used. See chapter 27.10 for details about X.25 accounting.
X.25 Service
(400)
27.20-9
27.20.4
27.20-10
(400)
X.25 Serivce
Range
0% to 100%
Default
80%
X.25 Service
(400)
27.20-11
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
:10
:80 %
:50 %
:120 sec
F2-SCT
F7-
F3-MCT
F8-CANCEL
F4-FR-RCN_TMR F5F9-QUIT
F10-
27.20.5
27.20-12
(400)
X.25 Serivce
Range
Default
Allocated XAC
number
1128
no default
TOA/NPI
address format
NO
YES
Clear on calling
address failure
NO
YES
YES
Default NUA
NO
YES
YES
Figure 27.20-8 provides an example of the XFR NUA parameters NMTI screen.
Figure 27.20-8: NUA Parameters NMTI
X25FRE Stations:nn
PA11-H1-00
Toronto:A
Alarms:1
11-May-1997
8:35a
:x302011888866 (default)
:XFR
:7
:
:Yes
F2-ASSIGN_TO
F7-MORE
F3-DELETE
F8-CANCEL
F4-USER_DATA F5-SUBS_OPT
F9-QUIT
F10-PROCEED
X.25 Service
(400)
27.20-13
27.20.6
Configure the XAC for XFR service type. See Section 27.14.8.
2.
3.
4.
b.
c.
d.
27.20-14
(400)
X.25 Serivce
5.
6.
7.
8.
X.25 Service
(400)
27.20-15
28.1
28.1.1
fully complies with the 1984, 1988, 1992 and 1996 versions of ITU-T
28.1.2
Understanding X.75
The X.75 protocol defines the characteristics and operation of links between
packet-switched (X.25) public networks (see Figure 28.1-1). Each internetwork link
comprises two directly connected signalling terminals (referred to as STEs) each
within a public network.
Figure 28.1-1: X.75 Link
Public
X.25
network
STE
DTE
X.75
STE
Public
X.25
network
DTE
9299
(400)
28.1-1
public
network
X.75
public
network
X.35
X.75
X.75
X.75
Private
network
Public
network
Newbridge
public
network
X.35
X.35
X.75
Private
network
Private
network
9152
28.1.3
X.75 Utilities
The following X.75 utilities are supported and carried in the X.75 utility field in Call
Request, Call Connected and Clear Request packets.
Call identifier
The call identifier utility is used in conjunction with the calling address to identify
the call. The call identifier is always present in a Call Request packet. If a Call
Request packet is received on an X.75 link and the call identifier utility is not present,
the call is cleared. The call identifier is only present in Call Request packets.
28.1-2
(400)
Through a negotiation process in which each X.75 STE may reduce, but not raise, the
requested throughput class value, either X.75 STE is able to request the throughput
class to be used.
If the originating DTE did not request a specific throughput class, each X.75 STE
requests the default throughput class value agreed upon by the network
administrations.
When the called DTE has accepted the call, the STE of the called network confirms
the negotiated throughput class value in the throughput class indication utility of
the Call Connected packet.
If a throughput class value is not explicitly confirmed, the STE of the called network
is assumed to confirm the lowest throughput class value between the default and the
originally requested throughput class value.
(400)
28.1-3
The CLAMN utility is present in the Call Connected packet and the Clear Request
packet when the called DTE address is different from that specified in the initial Call
Request packet.
28.1-4
(400)
The CLAMN utility is not present in a Call Request packet, nor is it present in the
Clear Request packet sent after the call is connected.
28.1.4
(400)
28.1-5
28.1.5
IPVCs
The remote address of the IPVC is configured as the NUA of the X.75 gateway link
to be used for the IPVC. That is, it is not the remote DNIC that is configured as the
remote address. The use of the NUA allows one to specify the link to use on the PVC
in the case where multiple links support the same address prefixes. The same applies
to the local address. For information on how to configure PVCs, see chapter 27.17.
28.1.6
Mode of operation
Three modes of operation are possible:
28.1-6
(400)
(400)
28.1-7
nat.
IC
Network B
DNIC = 3160
ICUG
3110
400
3110
401
2440
1004
DTE 2
nat.
IC
ICUG
400
3110
400
401
3110
401
Network C
DNIC = 2440
Network D
DNIC = 3110
nat.
IC
ICUG
200
2440
1004
301
2160
30
350 3110
400
351 3110
401
DTE 1
Network A
DNIC = 2160
DTE 1 in network A makes a CUG call to DTE 2 in network B. It uses CUG index 5,
which maps onto national interlock code 200. At the X.75 switch, the national
interlock code is mapped onto ICUG 2440 1004. That is, the ICUG is administrated
by network C, which has DNIC 2440. The call is routed via transit network D, which
does not support this ICUG. Since it is a transit network, it merely passes the call to
the next network. Network B maps the ICUG onto national interlock code 3. At the
destination switch, the national interlock code is mapped onto CUG index 7 of the
destination DTE link.
28.1.7
X.75 Accounting
By default, accounting records are generated for X.75. These records allow the
network manager to maintain records of all internetwork calls.
28.1-8
(400)
For outgoing X.75 calls, accounting records are generated at the source switch. If
reverse charging applies, the accounting record is generated at the X.75 XAC of the
source network.
For incoming X.75 calls, accounting records are generated at the incoming X.75 XAC.
If reverse charging applies, the accounting record is generated at the destination
XAC.
For transit calls, accounting records are generated at the X.75 XAC where a
non-reverse charge call enters the network and at the X.75 XAC where a reverse
charge call exits the network.
The party to be charged is identified by the reverse charging field in the accounting
record. If the reverse charging field is not set, the calling DTE is charged, otherwise
the called DTE is charged.
Figure 28.1-4: Rules Governing the Generation of Accounting Records for X.75
DTE Y
DTE X
Switch
1
Switch
2
Switch
3
Switch
4
Network
B
Network
A
Switch Switch
5
6
Network
C
Call Direction
Call Direction
No reverse charge
Reverse charge
Accounting records
generated at
Switch 1
Accounting records
generated at
Switch 2
Incoming from
Network B
to Network C
Accounting records
generated at
Switch 5
Accounting records
generated at
Switch 6
Incoming from
Network A
to Network B
Accounting records
Accounting records
generated at Switch 3. generated at Switch 4.
9438
28.1.8
(400)
28.1-9
If the Diagnostic Code Mapping parameter is set to Yes and the cause code for a
cleared call is Network Congestion, the calling DTE is informed whether the
problem occurred at the X.75 STE X/Y interface or within the remote network. If this
parameter is set to No, the calling DTE will not be able to distinguish between
problems occurring at the gateway link and those occurring within the remote
network.
Also, if this parameter is set to no, proprietary enhanced diagnostic codes are passed
across the STE X/Y interface for all cause code values. This is because it is expected
that diagnostic code mapping would only be disabled in cases where there is a
Newbridge to Newbridge equipment STE X/Y interface.
Diagnostic codes are mapped according to Table 28.1-1. For information on specific
diagnostic codes see Maintenance, chapter 37.1.
Table 28.1-1: Diagnostic Code Mapping for Clear Request Packet
28.1.9
Same
1 to 111
114
112 to 127
Same
128 to 255
113
Set the GFR address in the GAT to that of the switch in the calling network.
2.
Set the address prefix in the GAT to the DNIC of the destination network.
3.
Set the XAC number in the GAT to that of the XAC linked to the destination
network.
4.
Set the service type for the gateway XAC to X.75 gateway or X.25 gateway.
5.
Configure the gateway NUA and set the service type to X.75 gateway or X.25
gateway.
It is important to note that only one NUA can be associated with a gateway link.
The NUA for the gateway XAC is only used to set up PVCs to the destination
network. The NUA must be an address that is reachable by call routing within
the calling network. It must not be prefixed with the DNIC of the destination
network because the internal call attempt will be treated as an X.75 call. For
example, supposing the calling network has a DNIC of 3220, and the called
network has a DNIC of 6550, the GAT entry would be an X.75 GW prefix of
6550. The NUA could have an internal address of 3220300001001 which is
reachable by normal X.25 call routing.
28.1-10
(400)
28.1.10
6.
Set the LAPB address assignment parameter (01 or 03) to the opposite of the
setting in the destination network.
7.
Set the X.75 LCN selection parameter (ascending or descending) to the opposite
of the setting in the destination network.
8.
Set the TNIC/CNIC parameter for the link (it is normally the same as the DNIC
for the calling network).
9.
Parameter Name
Option or Range
Default
03
01
03
Modulo 8
Modulo 128
Modulo 8
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
1 to 20
10
10 to 120 000 ms
increments of 10
3000 ms
0 to 3000 ms
increments of 10
200 ms
0 to 120 000 ms
increments of 10
60 000 ms
Congestion Timer
10 to 120 000 ms
increments of 10
3000 ms
Not configurable
None
(400)
28.1-11
28.1-12
Parameter Name
Option or Range
Default
Service Type
X.75 gateway
X.75
Ascending
Descending
Ascending
Version
1984/1988
1992/1996
1984/1988
Modulo 8
Modulo 128
Modulo 8
Base LCN
1 to 4095
Number of LCNs
1 to 4095
32
Number of PVCs
0 to 4095
0 to 4095
Two-way SVC
1 to 4095
32
0 to 4095
0,1 to 500 s
180 s
0,1 to 500 s
200 s
0,1 to 500 s
180 s
0,1 to 500 s
180 s
Window Timer
0,1 to 500 s
Inactivity Timer
0,1 to 500 s
1 to 180 s
1 to 19
19
Default NPI
E.164 digital
E.164 analog
X.121
X.121
16 bytes
32 bytes
64 bytes
128 bytes
256 bytes
512 bytes
1024 bytes
2048 bytes
4096 bytes
128 bytes
256 bytes
512 bytes
Yes or No
Yes
Basic
Extended
Basic
(400)
Parameter Name
Option or Range
Default
Yes or No
Yes
Generate Alarms
Yes or No
Yes
Status Monitoring
Yes or No
Yes
Gateway TNIC/CNIC
4 BCD digits
None
Insert TNIC
Yes or No
Yes
Signal TNIC
Yes or No
Yes
Signal CNIC
Yes or No
Yes
Parameter Name
Option or Range
Default
None
None
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
(400)
28.1-13
28.1-14
Parameter Name
Option or Range
Default
None
1 to 512 for PE
1 to 128 for X.25 FRE
None
Accounting Activation
Yes or No
Yes
Signal CLAMN
Yes or No
Yes
Signal CRN
Yes or No
Yes
Yes or No
Yes
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
1 to 7 (Modulo 8)
1 to 127 (Modulo 128)
75 b/s to 2 Mb/s
64 kb/s
75 b/s to 2 Mb/s
64 kb/s
16 to 4096 bytes
128
16 to 4096 bytes
128
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
No
Yes or No
Yes
Yes or No
No
(400)
28.2
28.2.1
28.2.2
(400)
28.2-1
Stations:5
P611-F1-01
OTTAWA:A2
Alarms:4
07-Feb-97
9:17:20A
LINK LAYER
--------------------LAPB Address Assignment
:01
Frame Sequence Numbering
:8
Maximum Frame Window Size
:7
Re-transmission Count (N2)
:10
Frame Response Timer (T1)
:3000 ms
Response Delay Timer (T2)
:200 ms
Inactivity Timer (T3)
:6000 ms
Congestion Timer
:3000 ms
Maximum Information Frame Size(N1):259
F1-LAPB_ADDR
F6-
F2-SEQ_NUMBER
F7-
F3-WIN_SIZE
F8-CANCEL
F4-N2
F9-QUIT
F5-TIMERS
F10-PROCEED
28.2.3
28.2-2
(400)
Default
03
(400)
28.2-3
28.2-4
(400)
Congestion Timer
This parameter specifies the maximum time to wait for a congested X.75 link to
become uncongested. This timer starts when the link transmit queue exceeds a
pre-determined threshold. If the timer expires before the transmit queue falls below
the threshold, the link is brought down. This prevents one link from using a
disproportionate amount of resources on the switch. Avoid setting this value too
small for links that experience bandwidth bottlenecks or large volumes of bursty
traffic.
Range
10 - 120 000 ms (increments of 10 ms)
Default
3000 ms
The value of T3 must be sufficiently greater than the value of T1 so that the
expiration of T3 is a valid indication that the link is in a non-active state.
When timer T3 is changed from 0 to some other value, the timer starts only when
the link is restarted or when a frame is sent or received over the link. For example,
if the remote STE is running an idle timer, timer T3 starts when the STE timer
expires and the STE transmits an RR frame.
When timer T3 is enabled (not 0) and the value is changed, the current timeout
value is allowed to expire before the new value takes effect. For example, if the
timer is set to 30 seconds and then changed to 1 second, the timer may take up to
30 seconds to expire before 1-second timeouts occur.
(400)
28.2-5
You can change the values of all other link layer parameters at any time with no
disruption of service. The changes are effective immediately.
LAPB_ADDR
SEQ_NUMBER
WIN_SIZE
N2
<01 or 03>
<seq_number>
<k>
<n2>
TIMERS
T1
<t1>
T2
T3
<t2> <t3>
CONGST_TMR
<congst_tmr>
SK000680
where
xac is a valid XAC with service type X.75
seq_number is 8* for sequence numbers 1 to 7 or 128 for sequence numbers 1 to 127
k is 1 to 7* if SEQ_NUMBER is set to 8, or 1 to 127 if it is set to 128
n2 is 1 to 20, 10*
t1 is 10 to 120 000 ms in multiples of 10 ms, 3000*
t2 is 0 to 3000 ms in multiples of 100 ms, 200*
t3 is 0 to 120 000 ms in multiples of 10 ms, 60 000*
congst_tmr is 10 to 120 000 ms in multiples of 10 ms, 3000*
* indicates the default
28.2-6
(400)
28.2.4
Each of the X.75 parameters are explained with respect to the STE X/Y interface
Figure 28.2-2 shows the NMTI display for the X.75 network layer parameters.
(400)
28.2-7
Stations:5
P611-F1-01
OTTAWA:A2
Alarms:4
07-Feb-97
9:17:20A
NETWORK LAYER
------------------------Service Type
:X.75 Gateway
X.75 LCN Selection
:ASCENDING
Version
:1984/1988
Packet Sequence Numbering
:8
Packet Layer Restart Timer (T30) :180 s
Base LCN
:1
Packet Layer Call Timer (T31)
:200 s
Number of LCNs
:32
Reset Timer (T32)
:180 s
Number of PVCs
:0
Clear Timer (T33)
:180 s
Number of Incoming SVCs :0
Window Timer
:60 s
(Two Way SVCs)
:32
Inactivity Timer
:180 s
Number of Outgoing SVCs :0
Flow Control Timer
:1 s
F3-SEQ_NUMBER
F8-CANCEL
F4-LCN_ALLOC
F9-QUIT
F5-TIMERS
F10-
28.2.5
Service Type
The service type specifies the type of service with which the XAC is associated. For
an XAC to be used in X.75 gateway service, the service type parameter must be set
to X.75 gateway.
You cannot change the service type if the XAC is connected to a direct circuit or
frame stream-DLCI.
You cannot change the service type if there are any NUAs attached to the X.75 XAC
that are members of hunt groups or that have PVCs defined.
28.2-8
(400)
Options
X.75 Gateway
Default
None
Version
This parameter specifies the version of the ITU-T Recommendation X.75 service
supported by the X.75 STE. The difference in operation between the two options is
the control of the X.75 utility field length. In the 1984 and 1988 versions, the utility
field is a maximum of 63 bytes in length. In the 1992 and 1996 versions, an overall
maximum packet length applies with no maximum utility field length.
Options
1984/1988 or 1992/1996
Default
1984/1988
(400)
28.2-9
The Packet Sequence Numbering value configured for an X.75 XAC must be greater
than the Default Send Window Size and Default Receive Window Size values for
SVCs and PVCs associated with the X.75 XAC. For example, if an X.75 XAC uses
modulo 8 sequencing, then any SVC assigned to that X.75 XAC is restricted to
default send and receive window sizes of 1 to 7.
For an active X.75 XAC, you cannot change the value from 128 to 8 if SVCs or PVCs
associated with the X.75 XAC have default send and receive window size values of
greater than 7.
Options
Modulo 8 or Modulo 128
Default
Modulo 8
Base LCN
This parameter specifies the LCN of the first logical channel supported on the X.75
interface.
Range
1 to 4095
Default
1
Number of LCNs
This parameter specifies the total number of logical channels supported on the
interface. This value must be greater than or equal to the number of PVCs + the
number of incoming SVCs + the number of outgoing SVCs.
Range
1 to 4095
Default
32
Number of PVCs
This parameter specifies the number of logical channels on the interface that support
PVCs. The number of PVCs + the number of incoming SVCs + the number of
outgoing SVCs must be less than or equal to the number of LCNs.
28.2-10
(400)
Range
0 to 4095
Default
0
Two-way SVCs
This parameter specifies the number of logical channels on the X.75 interface that
support both incoming and outgoing SVCs. This parameter is not directly
configurable; the value is determined as follows:
n = LCNs (PVCs + SVCsout + SVCsin)
where
n is Number of Two-way SVCs
LCNs is Number of LCNs
PVCs is Number of PVCs
SVCsout is Number of Outgoing SVCs
SVCsin is Number of Incoming SVCs
(400)
28.2-11
Note
The most common arrangement for logical channels at an X.75 STE X/Y interface is
for all LCNs to be two-way SVCs, with a range of LCNs assigned for IPVCs, if the
two networks agree to support inter-network PVCs.
Range
1 to 4095
Default
32
28.2-12
(400)
(400)
28.2-13
Default
180 seconds
Inactivity Timer
The network layer inactivity timer starts when the transmit queue is full and stops
when the transmit window opens. When the timer expires, the virtual circuit is reset,
thereby preventing deadlock on the virtual circuit. The default (0) disables this
timer.
Range
0 or 1 to 500 seconds
Default
0 seconds
28.2-14
(400)
(400)
28.2-15
Default
19
Default NPI
This parameter specifies the default NPI value applicable to the X.75 STE, if the
TOA/NPI address format is not used.
The setting of this parameter must be the same as that of the connected X.75 STE. The
default value (X.121) applies when both X.75 STEs are in public data networks
according to ITU-T Recommendation X.75.
Options
E.164 digital
E.164 analog
X.121
Default
X.121
28.2-16
(400)
(400)
28.2-17
Default
Yes
Generate Alarms
This parameter specifies whether the switch generates alarms for this X.75 STE to
indicate that the link layer or network layer is down.
Options
Yes or No
Default
Yes
Status Monitoring
If this parameter is set to Yes, the MainStreetXpress 46020 Network Manager is
notified as to whether or not the X.75 gateway is in operation. If this parameter is set
to No, the MainStreetXpress 46020 Network Manager is not notified as to whether
or not the X.75 gateway is in operation.
Options
Yes or No
Default
Yes
Gateway TNIC/CNIC
This parameter contains the TNIC/CNIC value associated with this X.75 STE and is
inserted, if not prohibited by the parameters controlling the insertion and signalling.
Options
4 BCD digits
Default
None
28.2-18
(400)
Insert TNIC
This parameter controls whether a TNIC value is inserted in an X.75 call request
signalled by the X.75 STE link. TNIC insertion only occurs for transit X.75 calls,
which is when the call enters and exits the network via X.75 interfaces. When set to
Yes, the TNIC value is inserted if it is not already present (duplicate TNIC values are
not allowed). This method of TNIC insertion control is relevant to cases involving
network migration when there are two parallel networks sharing the same TNIC
value and interconnected by X.75.
Options
Yes or No
Default
Yes
Signal TNIC
This parameter controls whether or not any TNICs are signalled in an X.75 call
request, call connect or clear request transmitted by the X.75 STE. This option is
useful for the unusual case where X.75 is used to connect public and private
networks and no TNICs are to be signalled to the private network.
Options
Yes or No
Default
Yes
Signal CNIC
Since the support of a CNIC is optional, this parameter is used to control whether
the X.75 STE signals a CNIC utility in a Clear Request packet so that it is not sent to
an adjacent network that does not support it.
Options
Yes or No
Default
Yes
(400)
28.2-19
28.2-20
(400)
When you change the following network layer parameters for an active XAC, the
switch automatically disables and immediately re-enables the XAC to activate the
change. The switch clears all calls on the access line and restarts the link. The changes
are effective once the link restarts.
You can change the following network layer parameters at any time with no
disruption of service. The changes are effective for the next call.
You can change the following network layer parameters at any time with no
disruption of service. The changes are effective immediately.
(400)
28.2-21
SERVICE
X75_INTF
SEQ_NUMBER LCN_ALLOC
ADDRESSING
MORE
<seq_number>
X75_GATEW
VERSION
LCN_SELECT
<version>
ASCEND/DESCEND
BASE_LCN
TIMERS
NUM_LCN
NUM_PVC
NUM_O_SVC
NUM_I_SVC
<number>
T30RST
T31CALL
T32RES
T33CLR
<seconds>
<seconds>
<seconds>
<seconds>
<seconds>
INACTIVITY
FLOW_CNTL
<seconds>
<seconds>
MAX_LENGTH
<max_length>
PACKETS
ADD
MORE
DEF_NPI
X121
E164_DIG
E164_AN
NEGOTIATE
CAUSE_CODE
TPUT_FORMT
DIAGNOSTIC
ALARMS
EVENT_MON
BASIC/EXTENDED
YES/NO
YES/NO
YES/NO
REMOVE
<pkt_size>
WIN_TIMER
REPORTS
X75_OPTION
X75CALLS
TNIC_CNIC
INSERT_TNIC
SIGNAL_TNIC
SIGNAL_CNIC
YES/NO
<tnic or cnic>
YES/NO
YES/NO
YES/NO
SK000681
28.2-22
(400)
where
xac is a valid XAC with service type X.75
version is the version of X.75 protocol (1984/1988* or 1992/1996)
seq_number is 8* for modulo 8 (normal) or 128 for modulo 128 (extended) operation
tnic or cnic is 0000 to 9999
number is 1 to 4095, 32* for NUM_LCN
seconds is 1 to 180 for the flow control timer (1*), and 1 to 630 for all other timers
max_length is 1 to 19* digits
pkt_size is one or more of the values 16, 32, 64, 128*, 256*, 512*, 1024, 2048, or 4096
* is the default
28.2.6
(400)
28.2-23
Default
ix
28.2-24
(400)
(400)
28.2-25
Options
Yes or No
Default
No
28.2-26
(400)
Default
No
<entry_no.>
MORE
TRAP_ACTN
<addr_prefix>
INCOMING OUTGOING
NEW_ENTRY
CLEAR_CALL ALARM
BOTH
YES/NO
CALLING
TRP_INC_CD
CALLED
BOTH
TRP_INC_CG
TRP_OUT_CD TRP_OUT_CG
YES/NO
SK000423
where
xac is 1 to 128 for X.25 FRE cards or 1 to 512 for PE cards
entry_no. is an address translation table entry number (1 to 256)
addr_prefix is the translation prefix string (i or n, x, e, or m, and 0 to 19 digits or wildcard characters [?])
(400)
28.2-27
28.3
28.3.1
Understanding NUAs
For an explanation of NUAs, see chapter 27.15.
The NUA of an X.75 gateway link is the remote address for an IPVC. That is, it is not
the DNIC of the remote network that is configured as the remote address. The use of
the NUA allows one to specify the link to use on the IPVC in the case where multiple
links support the same address prefixes.
28.3.2
Stations:5
P611-F1-01
OTTAWA:A2
Alarms:4
07-Feb-97
9:17:20A
:x3011888866
:--:--:
:Yes
(400)
F3-NUI
F8-
(default)
F4-COLLECTOR
F9-
F5-XFR
F10-
28.3-1
28.3.3
data number format (DNIC+NTN). The first digit of an X.121 address cannot be
0 or 9.
To define a digital E.164 address, enter e and 1 to 19 digits in international E.164
number format (CC+NSN).
To define an analog E.164 address, enter m and 1 to 19 digits in international
E.164 number format (CC+NSN).
Range
NPI (x, e, or m) and 1 to 19 digits in international address format
Default
None
28.3-2
(400)
If an NUA is moved from one XAC to another of the same service type, the NUA is
automatically deleted from the current XAC and added to the new XAC.
It is not possible to delete the NUA assigned as the Default NUA, nor is it possible
to move to another XAC, unless it is the only XAC.
Range
1 to 512
Default
None
Accounting Activation
Accounting is activated by default, since accounting records are always generated
for X.75 calls. This parameter applies to transit calls and call attempts at the X.75
interface. Accounting records are generated at the source and destination switches
in the case of other X.75 calls.
Options
Yes or No
Default
Yes
Signal CLAMN
This parameter specifies whether to signal the Called Line Address Modification
Notification utility across the X.75 interface in the Call Connected or Clear Request
packets when a call is redirected. This utility indicates to the calling network why
the called address is different from the one originally signalled by the network.
If this option is set to Yes, the CLAMN utility will be signalled. If this option is set to
No, the CLAMN utility will be omitted from the Call Connected and Clear Request
packets.
Options
Yes or No
Default
Yes
(400)
28.3-3
Signal CRN
Incoming calls that signal the CRN utility are cleared. If redirection occurs within the
Newbridge network and the call is redirected to an X.75 Gateway, then the CRN is
not inserted, but the call is allowed to leave the network.
Options
Yes or No
Default
Yes
28.3-4
(400)
(400)
28.3-5
Options
75, 150, 300, 600, 1200, 2400, 4800, 9600, 19 200, 48 000, 64 000, 128 000, 192 000,
256 000, 320 000, 384 000, 448 000, 512 000, 576 000, 640 000, 704 000, 768 000, 832 000,
896 000, 960 000, 1 024 000, 1 088 000, 1 152 000, 1 216 000, 1 280 000, 1 344 000,
1 408 000, 1 472 000, 1 536 000, 1 600 000, 1 728 000, 1 792 000, 1 856 000, 1 920 000,
1 984 000, 2 048 000 b/s
Default
64 000 b/s
28.3-6
(400)
Default
No
(400)
28.3-7
Options
Yes or No
Default
No
28.3-8
(400)
It is not possible to delete the NUA assigned as the Default NUA, nor is it possible
to move to another XAC, unless it is the only XAC.
You cannot change an address after the NUA is assigned to an XAC. You must delete
the NUA, redefine the address, and assign it to the XAC.
NUAs cannot exist in the database unless they are assigned to XACs. You cannot
define a block of NUAs and assign them at a later date.
An NUA cannot be a hunt group address or hunt group redirection address.
Default Throughput Class values greater than 192 000 b/s are permitted only when
the Throughput Class Negotiation Format parameter is set to Extended. See
section 27.14.8.
The values of the default send and receive packet size parameters must match one
of the allowable packet sizes configured for the XAC to which the NUA is assigned.
The values of the default send and receive window size parameters must be less than
the Packet Sequence Numbering value configured for the XAC to which the NUA is
assigned.
(400)
28.3-9
SUBS_OPT
CHARGING
ADDRESSING
REV_ACCEPT
REDIRECTN
SIG_CRN
YES/NO
SIG_CLAMN
YES/NO
TOA_NPI
CL_ON_FAIL
YES/NO
DEFAULTS
MORE
THRU_PUT
WIN_SIZE
RECV
PKT_SIZE
SEND
RECV
SEND
ACCOUNTING
<thru_put>
<win_size>
RECV
SEND
ACTIVATE
PERIODIC
HOT_BILLING
YES/NO
<pkt_size>
SK000679
where
address is the NUA
pkt_size is 16, 32, 64, ... , 4096 bytes
win_size is 1 to 7 for Modulo 7 and 1 to 127 for Modulo 128
thru_put is 75, 150, ... , 2048000 b/s
28.3-10
(400)
29.1
29.1.1
ISDN basics
The ISDN recommendations and standards published by the ITU-T standardize the
transport of digital voice and data over a digital network. Figure 29.1-1 illustrates the
reference model for basic rate access to the ISDN network. ISDN-compatible devices
can be connected directly to the network through a standard interface at an access
point known as the S/T interface. Equipment that is not ISDN compatible must be
connected to a TA designed specifically for that equipment, which converts its
transmission format to an ISDN-compatible format at the S/T interface.
Figure 29.1-1: Basic ISDN Reference Model
Analog
telephone
TA
Customer
premises
Non-ISDN
computer
G3
FAX
ISDN
telephone
ISDNcompatible
computer
TA
TA
Network
equipment
NT1
U
interface
ISDN
Network
S
6888
(400)
29.1-1
At the end of the subscriber loop, the S/T interface provides line termination for the
customer devices. In Europe and Japan, the S/T interface connects directly to the
ISDN network. In North America, the NT1 provides a further interface between the
S/T reference point and the network. The reference point on the network side of the
NT1 is called the U interface.
ISDN application
The ISDN application differs slightly from the basic model. Figure 29.1-2 shows a
typical application, in which a non-ISDN data device accesses the ISDN network
through a 3600 MainStreet series bandwidth manager node. Although the 3600
MainStreet series bandwidth manager node is not acting as a TA (it does not
translate signalling between the R and S reference points), it passes signalling
generated by the CPC on the S interface. Chapter 29.4 describes ISDN applications
for the BRI S/T card.
Figure 29.1-2: BRI S/T Card Application
Non-ISDN
computer
BRI
S/T
DCC
S
NT
U
interface
ISDN
network
CPC
6889
Applications
In 3600 MainStreet series bandwidth managers, the BRI S/T card is used in both
ISDN and non-ISDN applications. In ISDN applications, the 3600 MainStreet series
bandwidth manager node processes the ISDN signalling carried in the D channel. In
non-ISDN applications, the system may or may not carry ISDN signalling,
depending on the individual situation. If it does, the signalling passes transparently
to the network. The ISDN applications are ISDN leased line backup and the channel
search facility. The non-ISDN applications are leased lines and ISDN loop extension.
29.1-2
(400)
29.1.2
Options
Slot level
Card type
4-circuit card
8-circuit card
Interface type
ISDN
non-ISDN*
Interface mode
TE*
NT
I.430*
ETSI
T3 timer (2)
1 to 30 s in 1 s increments (15*)
point-to-point*
point-to-multipoint
short bus
extended bus
Circuit level
B-channel inversion type
no inversion*
Mu-law
A-law
B1*
B2* (4)
B1 and B2
B1 and D
B2 and D (4)
B1, B2 and D
3DS0 enabled
3DS0 disabled*
B1 to B7 (5)
enabled
disabled
(400)
29.1-3
Notes
1. This parameter applies only to the TE interface mode.
2. This parameter applies only to the NT interface mode.
3. The B1 channel should be configured as the master circuit, unless there is no B1 channel in the
super-rate bundle. In this case, the B2 channel must be configured as the master circuit, because
the D channel can never be the master circuit.
4. This is the only option that applies when configuring B2 channels; this and all other options apply
when configuring B1 channels.
5. By default, the two D-channel bits are placed in positions B7 and B6, but you can place them in any
two contiguous positions from B1 to B7 by entering the starting bit position.
6. This parameter is supported in Release 6.1 (X116-H1-30 software maintenance load) and newer
releases of software.
To make BRI channel connections for non-ISDN applications, see section 29.3.4.
Table 29.1-2: BRI S/T Card Configuration Parameters and Options for ISDN
Applications
Parameter
Options
Slot level
Card type
4-circuit card
8-circuit card
Interface type
ISDN
non-ISDN*
Interface mode
TE*
NT (1)
I.430*
ETSI
T3 timer (2)
1 to 30 s in 1 s increments (15*)
Forced activation
enabled
disabled*
Notes
1. This option applies only to non-ISDN applications.
2. This parameter applies only to the TE interface mode.
To configure BRI S/T circuits for ISDN applications, see section 29.4.4.
Note
For ISDN index configuration, see chapter 30.4.
The formats of the identifiers in the procedures are explained in Table 16.4-1 in
chapter 16.4.
29.1-4
(400)
29.2
29.2.1
29.2.2
BRI_ST_4
BRI_ST_8
SK000197
Note
To configure all slots programmed as EMPTY to the default configurations of the
cards installed in the shelf, press the CONFIG_ALL softkey and the <Esc> key
simultaneously.
(400)
29.2-1
29.3
Non-ISDN Applications
This chapter describes non-ISDN applications and explains how to configure
BRI S/T card interfaces and circuits for these applications.
29.3.1
Leased lines
This application allows non-ISDN devices to access the 2B+D bandwidth for
leased-line applications when there is not enough traffic to warrant an E1 link. In this
non-ISDN application, there is no need for D-channel processing, and the BRI B and
D channels are passed transparently through the node.
Typically, the physical interface of a leased-line application complies with ITU-T
I.430 standards and the interface is called a BRI interface without D-channel
processing. In MainStreet large multiplexer systems, these interfaces are configured
as NON_ISDN.
Figure 29.3-1 illustrates a typical 2B+D leased line application. In this example, the
3600 MainStreet system is used in a private network to access a 2B+D leased line
network. The 2B+D leased line is carrying six 8 kb/s compressed voice calls, three D
channels with the signalling for the voice calls, three 9.6 kb/s X.21 data calls and a
4 kb/s CPSS channel. (The X.21 data calls are connected to an X.21 DCC in the 3600
MainStreet system.) The 3600 MainStreet system passes the D channels
transparently to the network.
Figure 29.3-1: Leased Line Application
ISDN
PBX
D3
9.6 kb/s
X.21
D
D2
Voice 6
B2
Voice 3
Voice 4
Voice 5
4 kb/s
CPSS
and 2 x
9.6 kb/s
X.21
Voice 1
D1
Voice 2
B1
Front end
processor or
mainframe
9.6 kb/s
2B+D
BRI
S/T
2B+D
BRI
S/T
2B+D
Leased
Line network
3600
MainStreet node
6739
(400)
29.3-1
Figure 29.3-2 shows the connections needed in the 3600 MainStreet system for the
leased line application. For more information on subrate multiplexing, see
chapter 23.6.
Figure 29.3-2: Leased Line Connections
4 kb/s CPSS
9.6 kb/s X.21
9.6 kb/s X.21
B1
B2
D
Faaabccd
aa - - bccd
- - - - bccd
eeeebccd
eeeebccd
eeeebccd
- - - - bccd
f f f f bccd
f f f f bccd
f f f f bccd
a
e
f
SRM
b
d
c
B1
gh i F j kk l
gh i j j kk l
gh i j j kk l
gh i j j kk l
gh i j j kk l
gh i j j kk l
gh i j - kk l
gh i - - kk l
gh i - - kk l
gh i - - kk l
j
g
h
SRM
B2
i
l
D
7899
When the BRI S/T card is in non-ISDN mode, you can cross-connect individual
B channels to most other types of circuits (with a few exceptions, such as analog
voice circuits that need signalling). Connections are nailed up, providing a 64 kb/s
clear channel over the 2B+D link.
You can cross-connect D channels to DS0s on a primary rate link, to other 2B+D
non-ISDN interface channels or to SRS or SRM inputs. These connections allow loop
extensions for local ISDN devices to access a remote ISDN network.
29.3-2
(400)
ISDN
device
TE
2B+D
format
BRI
S/T
3600 MainStreet
node
E1
E1
(NT)
BRI
S/T
2B+D
format
NT1
ISDN
network
(TE)
1st DS0
2nd DS0
3rd DS0
B1
B2
11001 D 1
3DS0 format
6741
The loop extension scheme uses three DS0 channels on a DS1 interface to transport
the basic rate traffic between the two 3600 MainStreet systems. One DS0 is used for
each B channel and the third DS0 carries a D channel containing signalling. In
Figure 29.3-3, an ISDN device gains access to a remote ISDN network using 3DS0
transport over an E1 link. If the application needs delay equalization, you can
configure the B1, B2 and D channels as a super-rate group. Otherwise, you can
connect each channel individually.
Note
Section 22.3.25 describes ISDN loop extensions that use the 2B1Q channel unit as the
line or network termination at the U interface. In North America and France, you can
use either a 2B1Q channel unit (up to four interfaces) or a BRI S/T card (up to eight
interfaces) in an ISDN loop extension application. In Europe or Japan, the BRI S/T
card is used.
(400)
29.3-3
29.3.2
interface type
interface mode
layer 1 standard
T3 timer
bus configuration
Interface type
The interface type determines whether the interface is used for ISDN or non-ISDN
purposes. For leased line and ISDN loop extension applications, configure the
interface as NON_ISDN.
To configure the interface type, see the procedure To configure BRI S/T interfaces
in a non-ISDN application.
Interface mode
The interface mode defines the BRI S/T card interface as either NT or TE. In NT
mode, the interface provides timing to the far end; in TE mode, the interface receives
its timing from the line.
In a non-ISDN application, you select the interface mode depending on the role of
the BRI S/T card in the network. When the card acts as an NT, terminating customer
premises TEs, you configure it with NT interface mode. When the card acts as a TE,
with its output connected to an NT, you configure it with TE interface mode. For
example, in the loop extension application in Figure 29.3-3, the BRI S/T card at the
user end is configured as NT, and the one at the network end is configured as TE.
Similarly, in Figure 29.3-1, the BRI S/T card connected to the PBX is configured as
NT, and the card at the network end is configured as TE.
To configure the interface mode, see the procedure To configure BRI S/T interfaces
in a non-ISDN application.
Layer 1 standard
The L1_TYPE softkey allows you to select the layer 1 standard used in the network.
Type I.430 corresponds to the ISDN network protocols used in North America and
Japan. Type ETSI corresponds to European network protocols. The only difference
between the two layer 1 types is a minor difference in the use of the T3 timer.
To configure the layer 1 standard, see the procedure To configure BRI S/T
interfaces in a non-ISDN application.
29.3-4
(400)
T3 timer
The T3 timer is used when the interface is trying to become active. If there is no
response from the NT during the activation sequence, the interface continues its
attempts until the time specified for the T3 timer has elapsed. You can set the time
to any value between 1 second and 30 seconds, in 1 second increments.
To configure the T3 timer, see the procedure To configure BRI S/T interfaces in a
non-ISDN application.
Bus configuration
For a non-ISDN BRI S/T card in NT mode, you must specify the configuration of the
bus between the TEs and the BRI S/T card. The TEs are connected to the network
termination by either of two types of bus: point-to-point or point-to-multipoint. A
BRI S/T card in TE mode can be configured only with a point-to-point bus.
In the point-to-point configuration (PT_TO_PT), a single TE is connected to the
network termination over a bus of up to approximately 1 km.
In a point-to-multipoint (or passive) bus, up to eight TEs can be connected to the
network termination. In a short passive bus configuration (SHORT_BUS), the TEs
are placed at points on a bus of 100 m to 200 m. In an extended bus configuration
(EXTEND_BUS), the TEs are grouped together at the far end of the transmission
cable. In this configuration the bus from the network termination to the first TE can
be up to several hundred metres.
To configure the bus configuration, see the procedure To configure BRI S/T
interfaces in a non-ISDN application.
Note
The BRI S/T card must be the only TE device on the bus.
(400)
29.3-5
I/F_MODE
T3_TIMER BUS_CONFIG
L1_TYPE
ISDN/
NON_ISDN*
<time>
I_430*
TE*
NT
PT_TO_PT*
ETSI
MULTIPOINT
SHORT_BUS
EXTEND_BUS
SK000198
29.3.3
inversion
tandem super-rate
You can configure the D channel for:
3DS0 transport
transport position
You can configure both the B and D channels for an automatic loopback on
physically unconnected BRI circuits.
29.3-6
(400)
Tandem super-rate
You can configure a preferred or level 2 tandem super-rate bundle from the B1, B2
and D channels in a non-ISDN BRI interface. Configuring BRI channels into
super-rate groups is similar to configuring primary rate DS0s into super-rate groups,
except that the BRI interface has only three channels. For more information on
configuring primary rate super-rate groups, see chapter 20.15.
You create a BRI super-rate bundle by configuring the master circuit, which is the
lowest-numbered in the group. The B1 channel is the lowest-numbered in a BRI
interface and the D channel is the highest. The B2 channel is the master circuit only
when the B1 channel is not part of the super-rate bundle; the D channel is never the
master circuit.
Using the NUM_CIRCS softkey, configure the super-rate bundle as:
When you subsequently make a connection to the master circuit of the resulting
super-rate group, the connection is made to the entire group, and you cannot make
a separate connection to any other member of the group. However, any channel
omitted from the group can be treated normally as an individual channel.
To de-configure the super-rate group, select B1_ONLY (if the B1 channel is the
master circuit) or B2_ONLY.
(400)
29.3-7
Note
If you disconnect a super-rate master circuit, the super-rate group is automatically
deconfigured.
For a super-rate connection between a BRI interface and a super-rate DCC (up to
128 kb/s), you only need to connect the DCC circuit to the B1 channel. The system
automatically creates a super-rate bundle consisting of the B1 and B2 channels and
cross-connects both channels appropriately. A super-rate connection to a DCC
circuit can include only the B1 and B2 channels.
To configure a preferred or level 2 tandem super-rate bundle from the B1, see the
procedure To configure B1 channels.
To configure a preferred or level 2 tandem super-rate bundle from the B2, see the
procedure To configure B2 channels.
29.3-8
(400)
To configure B1 channels
CONFIG CIRCUIT <sn-i-1>
COPY_TO
FUNCTION
INVERSION
NO_INVER*
AUTO_LPBK
NUM_CIRCS
MuLaw_INV
ALaw_INV
ENABLE
PREFERRED
B1_ONLY*
B1+B2
B1+D
DISABLE*
LEVEL_2
B1+B2+D
SK000199
To configure B2 channels
CONFIG CIRCUIT <sn-i-2>
COPY_TO
FUNCTION
INVERSION
NO_INVER*
NUM_CIRCS
MuLaw_INV
ALaw_INV
PREFERRED
B2_ONLY*
AUTO_LPBK
ENABLE
DISABLE*
LEVEL_2
B2+D
SK000200
(400)
29.3-9
Note
Because the 3DS0 specifications are intended for the U interface, rather than the S/T
interface, the 3DS0 transport scheme in the 3600 MainStreet system does not comply
with 3DS0 specifications in all respects. Bits 3 and 4 of the DS0 channel, which are
the ZBS bits, are always set to zero, and bit 5, which transports the DSL overhead and
maintenance bits, is always set to one.
To configure the D channel for 3DS0 transport, see the procedure To configure
D channels.
To configure D channels
CONFIG CIRCUIT <sn-i-D>
COPY_TO
<sn-i-D>
3DS0_ENAB/3DS0_DISAB*
FUNCTION
TRANSP_POS
AUTO_LPBK
<Bn>
ENABLE
DISABLE*
SK000201
Note
The 3DS0 setting, the transport position and the automatic loopback setting can be
copied from one D channel to another using the COPY_TO softkey.
29.3-10
(400)
29.3.4
Restrictions
T1 channels
Configure the T1 signalling type for NoSIG or leave it at the default SIG
(if it is SIG, the system automatically changes it to when it makes the
connection).
If the data carried on the BRI channel could be corrupted by RBS
signalling on the T1 channel, turn RBS off.
E1 channels
Configure the signalling type to NoSIG or the default SIG (if it is SIG, the
system automatically changes it to NoSIG when it makes the
connection).
(400)
29.3-11
Connecting Interface
Restrictions
FRS or FRE
Voice circuits
CPSS
VCBs
Note
It is recommended that you use B8ZS for zero suppression on a T1 interface (or B3ZS
on a DS-3).
Most connections between BRI interfaces and ADPCM circuits are not supported.
However, you can connect M48 DS0 outputs to BRI B channels.
To make connections
CONFIG CONNECT <sn-i-h> TO_CIRCUIT <sn-cc>
where
sn-i-h is the BRI interface and channel (i = 1 to 8; h = 1, 2 or D)
sn-cc is the connecting circuit
29.3-12
(400)
29.4
ISDN Applications
This chapter describes the ISDN backup and channel search applications, and
explains how to configure BRI S/T card interfaces and circuits for the applications.
29.4.1
Node
B
Backup
Backup
PSTN
6745
(400)
29.4-1
CPC
D channel
HDLC
2B
D channel
2B
B channels are unconnected,
except when a call is in progress
Connected through
switching matrix
6742
29.4.2
29.4-2
(400)
29.4.3
interface type
interface mode
layer 1 standard
T3 timer
forced activation
The BRI S/T circuits are configured the same way for both the ISDN backup
application and the channel search facility.
Interface type
The interface type determines whether the interface is used for ISDN or non-ISDN
purposes. Configure the interface as ISDN for ISDN backup or channel search
applications.
To configure the interface type, see the procedure To configure BRI S/T interfaces
in an ISDN application.
Interface mode
For the ISDN applications, you must define the interface mode as TE.
To configure the interface mode, see the procedure To configure BRI S/T interfaces
in an ISDN application.
Layer 1 standard
The L1_TYPE softkey allows you to select the layer 1 standard used in the network.
Type I.430/ANSI corresponds to the ISDN network protocols used in North
America and Japan. Type ETSI corresponds to European network protocols. The
only difference between the two layer 1 types is a minor difference in the use of the
T3 timer.
To configure the layer 1 standard, see the procedure To configure BRI S/T
interfaces in an ISDN application.
T3 timer
The T3 timer is used when the interface is trying to become active. If there is no
response from the NT during the activation sequence, the interface continues its
attempts until the time specified for the T3 timer has elapsed. You can set the time
to any value between 1 and 30 seconds, in 1 second increments.
To configure the T3 timer, see the procedure To configure BRI S/T interfaces in an
ISDN application.
(400)
29.4-3
Forced activation
You can use the FRC_ACTIVATE softkey to configure a BRI interface for forced
activation. In this state, the system automatically tries to re-activate the interface
after a short pause (about 2 s) if it is de-activated by the network. Forced activation
is useful when the BRI interface is a source of synchronization for the node.
To configure the forced activation, see the procedure To configure BRI S/T
interfaces in an ISDN application.
T3_TIMER
I/F_MODE
FRC_ACTIVE
L1_TYPE
ISDN/
NON_ISDN*
<time>
TE*
NT
ETSI
I_430*
ENABLE
DISABLE*
SK000202
29.4.4
29.4-4
(400)
30. CPCs
30.1
30.1.1
Understanding CPCs
The CPC provides ISDN layer 2 and 3 processing for the ISDN backup application
and the channel search facility. You can install the CPC in any UCS 1 to 8.
Note
As well as backup connections, you can also set up preferred ISDN connections
through the CPC.
30.1.2
Configuring CPCs
Table 30.1-1 lists the CPC configuration parameters. Each parameter has a list of
options with any default value marked by an asterisk.
Table 30.1-1: CPC Card Configuration Parameters and Options
Parameter
Options
Slot Level
Card type
CPC
shared
dedicated*
BRI
E1 PRI
T1 PRI
none
Interface standard
NTT (1)
EUROISDN (2)
NI-1 (3)
NI-2 (4)
CPCs
(400)
30.1-1
Parameter
Options
1 or 2
1 to 23
1 to 30
PCM encoding
A-law
Mu-law
auto*
report off
report on*
Bearer service
H0 enable
H0 disable*
Nx64 enable
Nx64 disable*
BRI initialization
Bus configuration
point-to-point*
point-to-multipoint
none
local
network specific
national
international
unknown
Subaddress
none
1 to 7 characters
Remote number
Directory number
1 to 25 digits
Subaddress
none
1 to 7 characters
Bearer capability
30.1-2
speech
clear 64 kb/s*
rate adaption (56 kb/s)
3.1 kHz
(400)
CPCs
Parameter
Options
Verification
enabled*
disabled
Number of retries
0 to 10 (* = 2)
infinite
Dial or non-dial
enable*
disable
Dial delay
first (0 to 60 s [0 s*])
subsequent (5 to 60 s, D 5 [10 s*])
1 to 30
auto*
Notes
1. This option complies with Japan standards JT-Q931 and JT-Q921.
2. This option complies with European ETSI standards ETS 300 120-1 and ETS 300 104.
3. This option complies with North American BRI National ISDN-1 standards TR-TSY-268 and
SR-NWT-1953. Select this option only if the interface type is BRI; assign two SPIDs.
4. This option complies with North American National ISDN-2 standards TR-TSY-268, TR-NWT-1203,
SR-NWT-2343, SR-NWT-1953 and TR-NWT-1268.
To configure CPC circuits for the ISDN backup application and channel search
facility, see section 30.3.3.
To make CPC connections involved in the ISDN applications, see chapter 30.5.
Note
The formats of the identifiers in the procedures are explained in Table 16.4-1 in
chapter 16.4.
CPCs
(400)
30.1-3
30.2
30.2.1
Note
To configure all slots programmed as EMPTY to the default configurations of the
cards installed in the shelf, press the CONFIG_ALL softkey and the <Esc> key
simultaneously.
CPCs
(400)
30.2-1
30.3
30.3.1
PBX
Preferred
connection
Data
card
Control
card
A1-1
DX
Dual T1
card
Primary
rate link
A2-1
Physical
protecting
connection
CPC
Programmed
protecting
connection
5-1-I1
Dual T1-2
card
B
A3-A
D
Primary
rate link
6803
Figure 30.3-2 shows the D-channel connections between a Dual T1-2 card and the
CPC. Up to 31 D channels can be connected to each CPC.
CPCs
(400)
30.3-1
CPC
HDLC
D-channel
23B
D-channel
23B
B-channels are unconnected
except when a call is in progress
Connected through
switching matrix
6802
30.3.2
30.3.3
30.3-2
1.
Configure the BRI S/T card, Dual T1-2 card or Dual E1 card interface for ISDN.
See chapter 29.1 for the BRI S/T card and chapter 20.2 for the primary rate
cards.
2.
3.
Connect the D channel of the BRI or PRI to a CPC circuit (see chapter 30.5).
(400)
CPCs
4.
Configure the ISDN call data on the CPC circuit index (see chapter 30.4).
5.
For ISDN backup, configure the CPC circuit and index as the protecting circuit
for the preferred connection. For the channel search application, set up the
preferred connection to the CPC circuit and index (see chapter 30.5).
Note
ISDN is supported on the BRI S/T card, but not on the T1 or E1 PRI card, in the 3664
MainStreet system.
30.3.4
number of B channels
channel search order
PCM encoding
call status reporting
For PRI interfaces only, you can also configure the bearer service.
CPCs
(400)
30.3-3
You cannot change the interface type after the circuit is program connected, unless
you disconnect the circuit first.
To configure the interface type, see the procedure To configure CPC circuits.
Interface standard
Use the I/F_STNDRD softkey to define the ISDN signalling protocol used on the
interface as:
NTT for the protocol conforming to Japanese standards JT-Q931 and JT-Q921
EUROISDN for the protocol conforming to European ETSI standards ETS 300
You must assign two SPIDs if you select NI-1 (see the subsection BRI
initialization).
To configure the interface standard, see the procedure To configure CPC circuits.
Number of B channels
If the subscriber needs less than the maximum number of B channels, use the
NUM_B_CHAN key to specify the number of B channels subscribed. The default
value is the maximum number of B channels for the interface (2 for a BRI interface,
23 for a T1 interface and 30 for an E1 interface).
To configure the number of B channels, see the procedure To configure CPC
circuits.
30.3-4
(400)
CPCs
PCM encoding
Use the PCM_ENCODE softkey to specify the type of encoding indicated for calls on
the interface as:
Bearer service
You can use the BEARER_SVC softkey to enable and disable support for super-rate
connection backup on PRI interfaces. You select H0_ENABLE if the CPC circuit will
be connected to a network supporting H0, or N64_ENAB if the connecting network
supports n 64 calls. Currently, only NI-2 networks support n 64.
To configure the bearer service, see the procedure To configure CPC circuits.
CPCs
(400)
30.3-5
BRI initialization
Because there can be more than one interface, or terminal, on a BRI line, ISDN
standards include methods of distinguishing the terminals from each other.
One method is to assign a TEI to each terminal. You can configure TEI assignment
as automatic or fixed. If you select the default value, AUTO_TEI, the network
assigns a TEI automatically when the terminal initializes.
Some standards do not support automatic TEI assignment. When you select
FIXED_TEI in these cases, the system prompts you for the TEI value (0 to 63).
The SPID uniquely identifies the BRI terminals set of subscription parameters,
allowing the telephone company to assign different subscription parameters to
different SPIDs on the same interface. The SPID is normally the 10-digit directory
number and a code that indicates the terminals characteristics (for example, data
device, ISDN phone, fax).
You should assign a SPID only if the central office needs this function. Currently,
only the NI-1 and NI-2 standards support SPIDs. For the NI-1 protocol to work
properly with two simultaneous calls on the interface, you must configure SPID_1
and SPID_2. For NI-2, configure SPID_1 only. The SPID values are provided by the
telephone company.
To configure the BRI initialization, see the procedure To configure CPC circuits.
Bus configuration
The BUS_CONFIG softkey indicates whether the BRI interface has been configured
as a point-to-point or point-to-multipoint bus. In a CPC circuit, this information is
used for layer 3 configuration, and it must match the hardware configuration of the
interface (for an explanation of BRI bus configuration, see the subsection BRI bus
configuration).
To configure the bus configuration, see the procedure To configure CPC circuits.
30.3-6
(400)
CPCs
I/F_TYPE
NONE
BRI
I/F_STNDRD
E1_PRI
BEARER_SVC
T1_PRI
NTT
MORE
NUM_B_CHAN CH_SRCH_HI*/
CH_SRCH_LO
BRI_INIT
REPORT_ON*/
REPORT_OFF
PCM_ENCODE
<n>
H0_DISABLE*/
H0_ENABLE
NX64_DISAB*/
NX64_ENAB
AUTO_TEI*
FIXED_TEI
<tei>
SPID_1
SPID_2
BUS_CONFIG
<spid>
PT_TO_PT*
MULTIPOINT
ALaw
MuLaw
AUTO*
SK000204
where
n is 1 or 2* for BRI interfaces, 1 to 23* for T1 PRI interfaces and 1 to 30* for E1 PRI interfaces
tei is 0 to 63
spid is 3 to 20 digits
CPCs
(400)
30.3-7
30.4
ISDN Indices
This chapter explains how to configure ISDN indices on CPC circuits.
30.4.1
30.4.2
directory number
bearer capability
verification mode
number of retries
dial or non-dial
number of channels
Directory number
You can assign a directory number for both an outgoing call and incoming call.
CPCs
(400)
30.4-1
Outgoing call
When the system initiates an outgoing ISDN call, it creates a SETUP message
containing the call data and sends it out on the D channel. The call data includes the
REMOTE_NUM you configure for the index associated with the call. In the SETUP
message, this is known as the called party number.
To configure the REMOTE_NUM, you can assign a directory number (DIR_NUM)
and an optional subaddress (SUB_ADDR). Depending on the network,
subaddressing may be used for extension numbers to a main directory number.
Depending on the network and the subscription parameters, the SETUP message
may also contain the directory number and subaddress of the call originator. These
numbers are taken from the configured LOCAL_NUM, and are known as the calling
party number and subaddress in the SETUP message.
You define the local directory number (DIR_NUM) by selecting the format of the
number and then entering the number. The directory number formats are:
In a National ISDN-1 or National ISDN-2 network, you may need to specify the
format as LOCAL, NATIONAL or INTERNAT. For other networks, use
UNKNOWN.
There are some restrictions in entering directory and subaddress numbers.
Directory numbers can contain only digits and hyphens; other characters are not
allowed.
To configure the remote directory number and the local directory number, see the
procedure To configure indices on CPC circuits.
Incoming call
When the 3600 MainStreet system receives an ISDN call, it checks the incoming
SETUP message for the directory number and subaddress to determine the calls
related index. The system compares the called party number and subaddress in the
SETUP message with the configured LOCAL_NUM directory number and
subaddress until there is a match.
30.4-2
(400)
CPCs
If subaddresses are used, they must match exactly. If directory numbers are used, it
may not be possible to do an exact match. The network may transmit a national
number when the user has stored only local numbers, or the network may only
transmit the last few digits of the number. For this reason, the matching is done in
reverse order with the shorter of the two numbers. If your network only transmits
one or two digits, you must make sure that all the directory numbers used on the
interface have unique last digits.
Note
You can use the NONE softkey to remove a previously programmed number. There
is no NONE softkey for the remote directory number, since it is mandatory.
For the ISDN backup application, all index entries must have a unique directory
number.
Hunt groups (channel search facility)
The channel search facility supports a hunt group feature that allows you to use the
same directory number on multiple index entries. When you enter a duplicate
directory number, a warning message is displayed; however, you can ignore it and
proceed with the entry.
There is no restriction on the number of directory numbers in a hunt group, or on the
number of hunt groups defined on the CPC, up to a maximum of 2 (BRI), 23 (T1) or
30 (E1) index entries per D channel, and up to 31 D channels per CPC. Duplicate
directory numbers do not have to be entered consecutively for a D channel. Multiple
hunt groups can be defined for a single D channel, and the same directory number
can be used for more than one D channel.
Table 30.4-1 shows an example of an index table with duplicate directory numbers.
Table 30.4-1: CPC Index Table with Defined Hunt Groups
CPCs
D channel
Entry
0800 1111111
0800 1111111
0800 2222222
0800 1111111
0800 2222222
0800 2222222
0800 1111111
0800 1111111
0800 3333333
0800 3333333
(400)
Directory number
30.4-3
Hunt groups can be defined across multiple CPCs in a 3600 MainStreet system, but
because each CPC operates independently, it is not possible to share available
connections between cards.
Bearer capability
Bearer capability is used to indicate the transmission capacity of the device
connected to the ISDN interface. When the system receives an incoming call, it
compares the requested bearer capability in the SETUP message to that stored in the
index associated with the call. If the two values do not match, the system rejects the
call. You can assign one of four bearer capability.
SPEECH
Used for normal voice connections, this bearer capability does not normally occur on
the 3600 MainStreet system, as any associated signalling cannot be transmitted. This
softkey does not affect PCM encoding; it must be programmed separately for the
circuit (see the subsection PCM encoding). If a PCM encoding method is not
specified for the CPC circuit, the method in use at the far end of the connection is
applied. Do not use SPEECH for compressed voice.
CLEAR_64K
CLEAR_64K is used for unrestricted, transparent digital data transmission across
the network at 64 kb/s, and is the most commonly used in the 3600 MainStreet
system. It is used for compressed voice, super-rate connections and all data
connections that do not conform to V.110 rate adaption.
RATE_AD/56
RATE_AD/56 is used for unrestricted 64 kb/s digital data rate-adapted from
56 kb/s and can be applied to all data circuits that conform to V.110 56 kb/s rate
adaption. It is typically used when a network does not support 64 kb/s connections,
or in a network that interworks with non-ISDN switched 56 kb/s facilities. In V.110
56 kb/s rate adaption, the low order bit in each octet is set to 1 at all times.
3.1KHZ
Used for 3.1 kHz audio information, this bearer capability is another form of
SPEECH. It is typically used when the bearer capability of a call is unknown; for
example, when the network is interworking with non-ISDN facilities. PCM
encoding is handled the same way as it is for SPEECH.
To configure bearer capability, see the procedure To configure indices on CPC
circuits.
30.4-4
(400)
CPCs
Verification
Use the VERIFY/NON_VERIFY softkey to determine whether the node should
verify the originating number of an incoming call. Normally, the system matches the
called party number or subaddress in the incoming SETUP message to the stored
LOCAL_NUM. If you select VERIFY, the system also compares the calling party
number or subaddress in the SETUP message to the REMOTE_NUM data stored for
the index. The system checks the subaddress if there is one in the message, or
otherwise the directory number, and rejects the call in the following circumstances:
Number of retries
Use the RETRIES softkey to specify the number of times the node should try to make
the connection if the first call setup fails. You can enter a value between 0 and 10, or
select INFINITE to cause the node to continue trying indefinitely (as long as there is
no failure that makes the call impossible to set up).
To configure the number of retries, see the procedure To configure indices on CPC
circuits.
Dial or non-dial
Use the DIAL/NON_DIAL softkey to determine whether the node should dial the
call or wait for an incoming call. If you select NON_DIAL, the interface at this end
of the connection will not originate a call in a failure condition; the far end is
expected to detect the error and originate the call. Setting the index to NON_DIAL
makes sure that a glare condition (when both ends try to originate a call
simultaneously) does not occur. If you select NON_DIAL, the BEARER_CAP and
DIAL_DELAY softkeys are not applicable to the index.
If using the channel search facility, select non-dial mode.
To configure dial or non-dial, see the procedure To configure indices on CPC
circuits.
Dial delay
If you select DIAL, you can configure DIAL_DELAY, which is the time the node
should wait before trying an ISDN call. With the FIRST softkey, you can specify the
time (0 to 60 seconds) before the first call attempt; with the SUBSEQUENT key, you
can specify the time (5 to 60 seconds in 5-second increments) between subsequent
attempts if the first call setup fails. If both ends of a call are set to DIAL, the FIRST
timer should be set with several seconds difference at each end to avoid a glare
condition.
CPCs
(400)
30.4-5
To configure dial delay, see the procedure To configure indices on CPC circuits.
Number of channels
The NUM_CHANS softkey can be used to specify the number of B channels needed
for the call. Under normal conditions, you should accept the default value of AUTO,
which means that the node automatically calculates number of channels at
connection time. This softkey is typically used for testing.
To configure the number of B channels, see the procedure To configure indices on
CPC circuits.
30.4-6
(400)
CPCs
COPY_TO
LOCAL_NUM
REMOTE_NUM
DIR_NUM
BEARER_CAP
SUB_ADDR
<number>
<subaddress>
NONE
SUB_ADDR
DIR_NUM
NONE
MORE
<number>
<subaddress>
NONE
SPEECH
VERIFY*/
NON_VERIFY
CLEAR_64K*
DELETE
RETRIES DIAL/
NON_DIAL
<tries>
INFINITE
RATE_AD/56
DIAL_DELAY
FIRST
<first_time>
ENABLE*
DISABLE
3.1KHZ
NUM_CHANS
SUBSEQUENT
<sub_time>
<nn>
AUTO*
SK000205
where
number is 1 to 15 digits for local numbers and 1 to 25 for remote numbers (digits and hyphens only)
subaddress is 1 to 7 characters
tries is 0 to 10 (2*)
first_time is 0 to 60 seconds
sub_time is 5 to 60 seconds in 5 second increments
nn is 1 to 30
CPCs
(400)
30.4-7
Note
Use COPY_TO to copy data from one index to another. Directory numbers and
subaddresses are not copied.
Use DELETE to delete all data associated with the index.
30.4-8
(400)
CPCs
30.5
CPC Connections
This chapter explains how to make the connections involved in the ISDN backup
and channel search applications.
30.5.1
CPSS
super-rate
non super-rate
CPSS
You can back up 64 kb/s standard CPSS connections to a DCP and dedicated CPSS
connections to a Control card, but neither 4 kb/s CPSS over FDL nor shared CPSS is
supported.
Normally, you should not use the FDL on an ISDN PRI interface for CPSS, because
an ISDN interface is usually connected to the public network.
Super-rate
The ISDN applications support two types of super-rate connections: H0 and n 64.
You can configure H0 or n 64 operation for a CPC circuit configured for T1 or E1.
If the H0 capability is available on the network, you can connect six super-rate
channels totalling 384 kb/s by configuring the interface for the H0 bearer service.
You program the connection against the first channel in the super-rate bundle, and
the system assigns five more contiguous channels and sets up a single call when the
need for backup occurs. Because H0 connections need six contiguous channels with
the first channel number 1, 7, 13, 19 or 25 (E1 only), you should not use an H0 PRI
interface for any other types of connections, in case the system cannot find the right
channels at connection time.
The n 64 bearer service operates in the same manner as the H0 capability. The
maximum size super-rate connection is 23 64 for T1 PRI interfaces and 30 64 for
E1 PRI interfaces.
CPCs
(400)
30.5-1
Non super-rate
You can connect any of the following non super-rate circuits to an ISDN index:
Some restrictions may apply to some of these connections (see Table 29.3-1).
30.5.2
make the connection between the D channel of the BRI or PRI interface and the
CPC circuit
To connect D channels
CONFIG CONNECT <sn-i-D> TO_CIRCUIT <sn-cc>
where
sn-i-D is the D channel on the BRI or PRI interface
sn-cc is the CPC circuit (1 to 31)
30.5-2
(400)
CPCs
where
sn-cc or sn-l-cc is the circuit to be protected
sn-cc-Ixx is the CPC circuit and index (cc is 1 to 31; xx is 1 to the number of B channels (NUM_B_CHAN)
configured for the index)
CPCs
(400)
30.5-3
31.1
31.1.1
HSA Cards
(400)
31.1-1
Line Rate
STS-1
51.840 Mb/s
STS-3
STM-1
155.520 Mb/s
STS-9
STM-3
466.560 Mb/s
STS-12
STM-4
622.080 Mb/s
STS-18
STM-6
933.120 Mb/s
STS-24
STM-8
1.244 Gb/s
STS-48
STM-16
2.488 Gb/s
The flexibility of the SONET and SDH frame formats allows for efficient mapping of
network services into payload envelopes. For example, an STS-1 can accommodate
one DS3 or a combination of sub-DS3 signals, and an STM-1 can accommodate one
DS1E or a combination of sub-DS1E signals.
In a SONET payload envelope, sub-DS3 signals are carried in VTs; in an SDH
payload envelope, DS1E and sub-DS1E signals are carried in TUs. There are different
VT and TU types, and they can be distinguished from one another by their line rates.
Table 31.1-2 lists the typical standard signals that can be carried on VTs and TUs.
Table 31.1-2: VT and TU Line Rates
VT or TU Type
Line Rate
Standard Signal
Connection
VT-1.5
1.728 Mb/s
DS1 (T1)
VT-2
2.304 Mb/s
CEPT-1
VT-3
3.456 Mb/s
DS1C
VT-6
6.912 Mb/s
DS2
TU-11
1.728 Mb/s
DS1E
TU-12
2.304 Mb/s
E1
TU-2
6.912 Mb/s
DS2
TU-3
48.384 Mb/s
DS3 or E3
Multiplexing
In a SONET network, individual VTs are combined and mapped to higher-order
structures called VT groups. Any combination of VT types can be used to fill the
payload envelope of an STS-1 frame, but only one type of VT is configurable in each
VT group. STS-1 frames are further combined and mapped to higher-order STS-n
frames. For example, the STS-3 frame, the next higher-order frame relative to the
STS-1, accommodates three STS-1 frames.
31.1-2
(400)
HSA Cards
In an SDH network, broadband data is mapped onto individual VCs, which are in
turn changed into TUs. Individual TUs are combined into TUG-2 or TUG-3 groups,
which are combined into AU-3 or AU-4 structures. An STM-1 frame is composed of
one AU-4 structure in AU-4 mode, and three AU-3 structures in AU-3 mode. The
STM-1 card multiplexes TUs into an STM-1 signal through the following processes.
1. Lower-order VCs are assigned TU pointers that indicate their position relative
to the start of the higher-order VC frame. Once a pointer is assigned to a VC, a
TU is formed.
2. One or more TUs is mapped to a TUG, which allocates for the TU or TUs a fixed
position within the higher-order VC frame.
3. TUGs are assigned AU pointers that indicate their position relative to the start
of the STM-1 frame. Once a pointer is assigned to a TUG, an AU is formed.
4. One or more AUs is mapped to a AUG, which allocates for the AU or AUs a fixed
position within the STM-1 frame.
As with STS-1s, STM-1 frames can be further multiplexed into higher-order STM-n
frames.
For information about SONET and SDH broadband circuit configuration, see
chapter 31.6.
31.1.2
HSA Cards
(400)
31.1-3
Figure 31.1-1 shows an example of how enhanced locally controlled shelves are used
in linear add/drop multiplexing and signal termination applications.
Figure 31.1-1: Example of Linear Add/Drop Multiplexing and Signal Termination
Applications
3600+ MainStreet
Narrowband
and broadband
signal termination
3600+ MainStreet
3600+ MainStreet
Narrowband
and broadband
signal termination
9770
Ring multiplexing
The ring topology consists of a minimum of three enhanced locally controlled
shelves. The advantages of ring multiplexing include support for linear add/drop
multiplexing and signal termination applications and traffic protection at the circuit
level which allows for quick recovery of service in the event of a failure.
Figure 31.1-2 shows an example of how enhanced locally controlled shelves are set
up in a ring.
31.1-4
(400)
HSA Cards
3600+ MainStreet
Corporate
PBX
3600+ MainStreet
3600+MainStreet
3600+ MainStreet
3600+ MainStreet
Linear add/drop
3600+ MainStreet
DS3
POTS
Public
Network
9771
HSA Cards
(400)
31.1-5
31.2
Understanding High-speed
Aggregate Card Configuration
This chapter introduces high-speed aggregate cards.
31.2.1
OC-3 cards
STM-1 cards
VT 1.5 mapper cards
TU-12 mapper cards
The above HSA cards are installed in 3600+ MainStreet system HSA card slots. The
OC-3 and STM-1 cards provide a 155 Mb/s bidirectional optical interface.
OC-3 and VT-1.5 cards are used in SONET applications. The OC-3 card connects
directly to a SONET network, and the VT-1.5 card maps narrowband data onto the
OC-3 card broadband circuits.
STM-1 and TU-12 cards are used in SDH applications. The STM-1 card connects
directly to a SDH network, and the TU-12 card maps narrowband data onto the
STM-1 card broadband circuits.
STM-1
VT-1.5
TU-12
Parameter
Option
See Section
Card
Card type
OC-3
STM-1
VT-1.5
TU-12
HSA Cards
31.3.2
31.4.2
1+1*
simplex
ring
Card name
0 to 8 characters
(400)
31.3.2
31.2-1
OC-3
STM-1
VT-1.5
TU-12
Parameter
Option
See Section
unidirectional*
bidirectional
31.4.2
non-revertive*
revertive
31.4.2
0 to 60 min, D = 1 min
(* = 5 min)
31.4.2
subslot A* or B
31.4.2
Broadband Port
0.1 to 60 s, D = 0.1 s
35.4.2
1 E-5
1 E-6*
1 E-7
1 E-8
1 E-9
disabled
33.10.3
enabled
disabled*
33.10.3
enabled*
disabled
33.10.3
enabled*
disabled
33.10.3
enabled*
disabled
33.10.3
SES threshold
1 to 65535
(* = 2500)
33.10.2
33.10.2
Section trace
trace*
section ID
36.10.1
0 to 255
36.10.1
as present*
16 or 64 alphanumeric
characters
36.10.1
16 or 64 alphanumeric
characters
36.10.1
16 byte*
64 byte
36.10.1
SDH format
AU-3
AU-4*
31.6.3
DCC (2)
enabled
disabled*
31.8.1
Synchronization
system*
self
through
31.5.1
31.2-2
(400)
HSA Cards
OC-3
STM-1
VT-1.5
TU-12
Parameter
Option
See Section
Broadband Circuit
Circuit name
0 to 8 characters
31.6.5
0.1 to 60 s,
(* = 10 s)
35.4.2
1 E-5
1 E-6*
1 E-7
1 E-8
1 E-9
disabled
33.10.3
enabled*
disabled
33.10.3
enabled*
disabled
33.10.3
enabled*
disabled
33.10.3
enabled*
disabled
33.10.3
0 to 65535 (* = 2400)
33.10.2
33.10.2
STS-1 function
VT group*
bulk payload
31.6.2
non-specific
VT structured
31.7.2
AU-3 function
TUG-2*
C3
31.6.3
TUG-3 function
TUG-2*
TU3
31.6.3
non-specific
TU group structured*
31.7.2
0 to 62 alphanumeric
characters
36.10.1
16* or 64 alphanumeric
characters
36.10.1
(3)
as present
16* or 64 alphanumeric
characters
36.10.1
16* or 64 alphanumeric
characters
36.10.1
enabled*
disabled
36.10.1
0 to 60 min, D = 0.1 s
(* = 0 s)
31.4.2
HSA Cards
(400)
31.2-3
VT-1.5
TU-12
OC-3
STM-1
0 to 10 s, D = 0.1s
(* = 0 s)
31.4.2
subslot A circuit*
subslot B circuit
31.4.2
VT-1.5*
VT-2
VT-3
VT-6
31.6.2
TU-11*
TU-12
TU-2
31.6.3
Circuit provisioning
enabled*
disabled
31.6.4
equipped nonspecific
asynchronously mapped
DS-1*
31.7.2
equipped nonspecific
asynchronously mapped
E1*
31.7.2
0.1 to 60 s
35.4.2
DS1 Framing
D4*
ESF
31.13.2
E1 Framing
CAS*
CCS
31 channels
31.13.3
Trunk conditioning
one-way
two-way*
31.12.3
Fault classes
31.12.5
Loopback detection
none
through CPSS
31.20.2
CRC errors
framing bit errors*
31.18.3
CRC re-framing
enabled
disabled*
31.18.2
transparent
jam bit 7*
31.11.1
NU bits
0000 to 1111*
31.17.1
Inversion
inverted* (voice)
not inverted (data)
31.16.2
Parameter
Option
See Section
31.2-4
(400)
HSA Cards
OC-3
HSA Cards
STM-1
VT-1.5
TU-12
Parameter
Super-rate formats
contiguous
non-contiguous
equidistant
31.10.1
Fault signalling
seized
idle*
OOS-A
OOS-B
OOS-C
None
31.14.2
31.19.2
31.19.2
enabled*
disabled
31.15.1
Clear channels
NOSIG
RBS OFF
31.15.1
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
Terminate
31.15.2
E1 signalling types
transparent*
clear channel
E&M
LGS RE
LGS EC
LGS PLAR
LGS PLAR D3
LGE RE
LGE EC
31.15.3
T1 signalling types
transparent*
clear channel
E&M
LGS LS
LGS GS
LGS PLAR
LGS PLAR D3
LGE LS
LGE GS
31.15.3
(400)
Option
See Section
31.2-5
Notes
1. The card must be configured for 1+1 traffic protection.
2. The 3600+ MainStreet system NET address must be configured before the DCC can be enabled.
3. This option is only available for STS-1, AU-3 and TUG-3 links.
4. This option is only available for STS-1, AU-3, TUG-3, VT and TU circuits in ring mode.
5. This option is only available for STS-1 links.
6. This option is only available for AU-3 and TUG-3 links.
31.2.2
Insert the cards into the card slots. If a ring configuration is to be configured on
the OC-3 or STM-1 cards, insert the OC-3 or STM-1 cards into HSA slot H1.
2.
Configure the traffic protection mode for the HSA slots as simplex, ring or 1+1
mode. If you configure a slot for 1+1 protection, configure the 1+1 switching
options now. If you configure a slot for ring mode, path protection options must
be configured for each circuit. If ring mode is configured, and slot H2 is used to
add or drop broadband data to the ring, you must allocate UCS bandwidth to
slot H2. To allocate bandwidth to H2, enter:
CONFIG SYSTEM UCS_BB_BUS TO_H2
When UCS bandwidth is allocated to H2, you cannot configure an STS-1, TU-3
or AU-3 as a circuit on a card in H2. Only VT and TU circuits are allowed.
3.
31.2-6
Connect the Tx and Rx fibre optic cables from the SONET or SDH network to
the OC-3 or STM-1 cards.
(400)
HSA Cards
HSA Cards
4.
Configure the broadband port and circuit parameters on the OC-3 or STM-1
card.
5.
6.
Configure broadband connections between the OC-3 or STM-1 cards and the
SONET or SDH network.
7.
Configure connections between the UCS card primary rate signals and the
mapper card narrowband circuits.
8.
(400)
31.2-7
31.3
31.3.1
31.3.2
STM-1
OC-3
VT-1.5 mapper
TU-12 mapper
Each HSA slot can be configured with a card type, and each HSA card in each subslot
can be configured with a card name.
OC-3 and VT-1.5 mapper cards are used for OC-3 SONET applications, and STM-1
and TU-12 mapper cards are used for STM-1 SDH applications.
When the slot is configured, you should configure traffic protection options before
configuring or connecting any HSA card circuits. See chapter 31.4 for information.
Warning
If traffic protection mode is changed after circuit connections are made, all
connections may be lost.
HSA Cards
(400)
31.3-1
Note
A Revision/Feature Mismatch alarm occurs if VT-1.5 cards (revision 87-1034-03-1A
and earlier) or TU-12 cards (revision 87-1034-04-1A and earlier) are inserted in an
HSA slot. The card is not operational, and must be replaced by a newer revision.
Contact Newbridge support for information.
MAPPER
SONET
SDH
OC-3
STM-1
AS_PRESENT
TU-12
VT-1.5
16_PORT
16_PORT
SK000900
where
Hn is the HSA slot number used to configure card type
31.3-2
(400)
HSA Cards
31.4
31.4.1
simplex
1+1
ring
Mapper cards support the following two modes of traffic protection:
Simplex
1+1
Line protection is provided by 1+1 mode, and path protection is provided by ring
mode. These modes require that the HSA slot has a card inserted in each subslot.
Ring mode
Ring traffic protection mode can only be configured on HSA slot H1. In ring mode,
fiber optic cables are connected between opposite OC-3 or STM-1 card subslots. For
ring mode, connect fiber optic cables from subslot A on one node to subslot B on the
next node, and continue throughout the ring as seen in Figure 31.4-7.
1+1 mode
For OC-3 and STM-1 cards in 1+1 traffic protection mode, fibre optic lines must be
connected between each subslot on the cards in each node. When 1+1 connected
cards on different nodes are connected by fiber optic cables, connect subslot A on
one node to subslot A on the other node, and subslot B on one node to subslot B on
the other node, as seen in Figure 31.4-2.
Mapper cards do not require any special physical connections because mapper card
circuits connect to other circuits through backplane connections.
HSA Cards
(400)
31.4-1
Simplex mode
Simplex mode does not provide traffic protection. To support simplex traffic
protection on a card, it must be inserted in subslot A of an HSA card slot. Subslot B
registers as empty.
Caution
Any change from 1+1 to ring mode or ring mode to 1+1 traffic protection mode
results in a loss of all configured connections. A change from simplex to ring, or from
ring to simplex mode results in a loss of all configured connections.
A change from 1+1 to simplex mode results in a protection switch if subslot B is the
active card. Data is lost during the protection switch.
Circuit
H1-01
S1117-H1-00
Name
Circuit7
Switching
Working Circuit
WTR Timer
Hold Off Timer
Toronto:A
Type
STS-1
:
:
:
:
Alarms:1
11-May-1997
8:35a
Function
Bulk Payload
Non-Revertive
H1-B-01
5 minutes
0.0 seconds
2-WORKING_A
7-
3-WTR_TIMER
8-CANCEL
4-HOLD_OFF
9-QUIT
50-
31.4-2
(400)
HSA Cards
#
H1-A
H1-B
Configured
OC-3
OC-3
S1117-H1-00
Toronto:A
Installed
OC-3
OC-3
Operating Mode
Switching
WTR Timer
Working Card
:
:
:
:
Status
OK
OK
Alarms:1
Name
MUX3-A
MUX3-B
11-May-1997
8:35a
Options
1+1
1+1
Unidirectional
Non-Revertive
5 minutes
H1-A
2-REVERTIVE
7-
3-WTR_TIMER
8-CANCEL
4-WORKING
9-QUIT
50-
Working card
The working card option allows you to designate a working line and a protection
line for a connection between two nodes. The working line is the preferred line for
active data, and the protection line is used as a protection in case of a failure on the
working line. The configuration of working card is only important if revertive
switching is configured.
The active line is the line connected to the active card. The active card is determined
by the severity of card or line faults, and the configured switching type. Until card
or line faults cause a protection switch to the protection line, the working line carries
all the active data traffic.
Working circuit
The working circuit option allows you to designate a working ring and a protection
ring for a UPSR circuit connection. The working ring and associated circuit are the
preferred path for data traffic. The protection ring and associated circuit are used
when the quality of the circuit on the working ring degrades. The configuration of
the working circuit is only important when revertive switching is configured.
The active ring is the ring that is connected to the card that contains the active circuit.
The active circuit is determined by path quality and the configured switching type.
Until the path quality of the circuit associated with the working ring degrades, the
working ring carries all of the active data traffic.
HSA Cards
(400)
31.4-3
Switching type
Switching type can be configured as:
revertive
non-revertive
For 1+1 protected cards, protection switching occurs on the basis of line quality
determined by card or line faults. For ring protected cards, protection switching
occurs on the basis of path quality.
If the revertive switching type is selected, there is a switching bias toward the
working line or working ring circuit. The node selects traffic from the working line
or ring circuit until the line quality of the working line falls below the line quality of
the protection line. When line quality is equal, traffic is selected from the working
line, because the card in the working subslot reverts to being the active card.
If the non-revertive switching type is selected, there is no switching bias toward
either line or ring circuit. The inactive or active card or circuit is determined by the
number of line or card faults on each card, or path quality. A protection switch does
not occur in non-revertive mode until one card has fewer card or line faults than the
other card, or one ring circuit has better path quality than the other ring circuit.
Operating mode
The following protection switching modes are available for 1+1 protected OC-3 and
STM-1 cards:
unidirectional
bidirectional
When bidirectional switching is configured on an HSA card slot, it mimics every
protection switch that takes place on a connected card. In this way, each subslot of
an HSA slot that is configured for bidirectional switching has the same status (active
or inactive) as the connected card.
When unidirectional switching is configured, the status of connected cards can
differ, because the card configured for unidirectional switching does not mimic a
protection switch performed by a connected card.
WTR and hold-off timers
The WTR and hold-off timers delay protection switching to ensure that the change
in card faults or path quality that prompted the system request for a protection
switch are valid, and not merely intermittent.
The WTR timer controls the delay that occurs before a protection switch back to the
working line or ring circuit occurs. The WTR timer starts when a request for a
protection switch to the working line or ring circuit occurs. At the end of the WTR
count, the system checks to see if the conditions that caused the request still exist. If
the conditions do exist, a protection switch occurs. If the conditions do not exist, a
protection switch back to the working line or ring circuit does not occur.
31.4-4
(400)
HSA Cards
The hold-off timer controls the delay that occurs before a protection switch to the
protection ring occurs. The hold-off timer starts when a request for a protection
switch occurs. At the end of the hold-off timer count, the system checks to see if the
conditions that caused the request still exist. If the conditions do exist, a protection
switch occurs. If the conditions do not exist, a protection switch to the protection ring
circuit does not occur.
Node B
subslot A
(active)
Tx
subslot A
(active)
Rx
Working
Rx
Tx
subslot B
(inactive)
Tx
Protection
Rx
subslot B
(active)
Rx
Tx
9730
In this example, the connection between the two sets of HSA cards is carried by a
working line and a protection line. The working line is the preferred line, and is
configured as the line between A subslots. The protection line is configured between
B subslots.
The active card selects traffic from a connected HSA card. The inactive card
transmits the same data as the active card, and is ready to select traffic from the
protection path when a protection switch occurs. The active card in subslot A of
node B selects data traffic from the working line until a line or card fault occurs, as
seen in Figure 31.4-4.
The control card monitors HSA cards for card and line faults, and determines the
active card based on those faults, listed in order of priority in Table 31.4-1.
HSA Cards
(400)
31.4-5
Fault
OC-3 and
STM-1
Mapper
card lockout
forced switch
card dead
signal failure:
LOP, AIS,
UNEQ, TIM(1)
EBER
SD
manual switch
card failure
WTR
Notes
1. Line TIM applies only to OC-3 cards
A line or card fault drives a card toward being the inactive card. For example, if the
HSA card in subslot A registers an EBER, and the mate card in subslot B registers an
SD, the card in subslot B becomes the active card. The card in subslot A does not
become the active card until it registers a lower priority fault.
Figure 31.4-4: 1+1 Traffic protection Line Fault
Node X
Node Y
subslot A
(active)
Tx
subslot A
(active)
Rx
Working
Rx
RDI
subslot B
(inactive)
Tx
Protection
Rx
AIS
Tx
subslot B
(inactive)
Rx
Tx
9731
When the severity of faults on the card on node Y exceeds the severity of faults on
the mate card in subslot B, a protection switch occurs and the card in subslot B
becomes the active card, and the card in subslot A of node Y becomes the inactive
card. Figures 31.4-5 and 31.4-6 show how the switching type affects activity
switches.
31.4-6
(400)
HSA Cards
Node Y
subslot A
(inactive)
Tx
Working
subslot A
(inactive)
Rx
Protection
subslot B
(active)
Rx
Rx
Tx
subslot B
( active)
Tx
Rx
Tx
9732
Unidirectional
switching mode
Node X
Node Y
subslot A
(active)
Tx
Rx
subslot A
(inactive)
Rx
Working
Tx
subslot B
(inactive)
Tx
Rx
Protection
subslot B
(active)
Rx
Tx
9733
HSA Cards
(400)
31.4-7
31.4-8
(400)
HSA Cards
Tx
Rx
Rx
Tx
Rx
Tx
A
Node C
B
Tx
Tx
Rx
Rx
Tx
Rx
Node B
Node A
A
Tx
Rx
Rx
Tx
Rx
Tx
A
Node C
Tx
Tx
Rx
Rx
Tx
Rx
Node B
9729
HSA Cards
(400)
31.4-9
31.4.2
OC-3 or STM-1
Ring Mode
Mapper Card
1+1 Mode
Operation mode
switching type
OC-3 or STM-1
1+1 Mode
working card
working circuit
WTR timer
Traffic protection options are configured on the slot level for 1+1 protection, and on
the circuit level for ring traffic protection.
Working card
The working line is configured by selecting a card in a subslot as the working card.
The protection line is the line that is connected to the card in the other subslot. When
working card is configured in 1+1 mode, you should configure opposing subslots to
both be working subslots or protection subslots. For example, if you want to
configure subslot A of one card as the working line, you should also configure
subslot A of the connected card as the working card. A protection line is provided
by the card that is not selected to be the working card.
Working circuit
The working ring is selected by configuring the working circuit to be contained on
either the subslot A card or the subslot B card. The working ring connects to the Rx
connector of the card that contains the working circuit. The protection ring is the ring
that is connected to the Rx connector of card that does not contain the working
circuit. When the working ring is configured, you should configure opposing
subslots to both be working subslots or protection subslots. For example, if you want
to configure the ring connected to the Rx connector of subslot A to be the working
ring, you should configure each circuit to use subslot A to contain the working
circuit. The protection ring is connected to the Rx connector of the card that is not
selected to contain the working circuit.
31.4-10
(400)
HSA Cards
Switching type
Switching type should be configured as either revertive or non-revertive for each
span between destination nodes. This provides a consistent working line and
protection line throughout a network.
Select revertive switching when the working line or ring is required to be the active
line or ring. In revertive mode, unless there is a problem on the working line, it is
usually receiving active data. The protection line or ring is only active when a fault
exists on the working line or ring.
Select non-revertive switching if there is no need to keep active data on the working
line. When non-revertive switching type is configured, the configuration of working
and protection lines are meaningless, because active data is received by the line or
ring that has the best line or path quality. There is no switching bias toward either
the working or protection line or ring.
Operation mode
Both HSA slots involved in a connection should be configured with the same
operation mode. If the cards in an HSA slot one node are configured for a particular
operation mode, the connected cards should also be configured for that mode.
WTR and HOLD_OFF timers
If the WTR or HOLD_OFF timer has started, it cannot be reconfigured with a new
timer value until it has completed its count and completed the protection switch. A
new configured value will be accepted, but will not take affect until the timer is next
started.
1+1
SIMPLEX
RING
SK000920
UNIDIRECT/BIDIRECT*
NONREVERT*/REVERT
WORKING
WTR_TIME
<value>
SUBSLOT_A
SUBSLOT_B
SK000918
HSA Cards
(400)
31.4-11
NONREVERT*/REVERT
WORKING_A*/WORKING_B
WTR_TIMER
HOLD_OFF
<value_1>
<value_2>
SK000919
where
circuit is a broadband ring circuit in the format Hn-pa or Hn-pa-gr-vs
value_1 is from 0 to 10 s in increments of 0.1 s
value_2 is a number between 0 and 60 min in increments of 1 min
31.4.3
Forced switch
In 1+1 protection mode, a forced switch command prevents traffic from being
received from the selected card unless the mate card is already locked out. If this
command is issued against the working card, the request is blocked if the protection
card is under failure conditions.
In ring protection mode, this command prevents traffic from being selected from the
selected circuit, unless the mate circuit is locked out.
31.4-12
(400)
HSA Cards
Manual switch
This command prevents traffic received on the selected card or circuit from being
selected, unless:
Clear command
A clear protection switch command clears all protection switch commands that are
in place against a card or circuit.
ON_SLOT
ON_CIRCUIT
<Hn-ss>
<circuit>
PROTECTION
PROTECTION
LOCK_OUT
FORCED_SW
MANUAL_SW
CLEAR
SK000921
where
Hn-ss is the HSA slot and sub-slot
circuit is the selected circuit
HSA Cards
(400)
31.4-13
31.5
31.5.1
Synchronization sources
System mode selects the 19.44 MHz system timing source to synchronize the port Tx
line.
Self mode selects an internal timing loop, where the card uses its recovered Rx line
signal to synchronize the port Tx line.
Through mode allows an OC-3 or STM-1 card to synchronize its Tx line to the
recovered clock signal of another HSA card. Any OC-3 or STM-1 card slot can be
selected as a timing source.
HSA Cards
(400)
31.5-1
SYSTEM
SELF
THROUGH
<Hn> or <Hn-ss>
SK000901
31.5-2
(400)
HSA Cards
31.6
Broadband Circuits
This chapter explains how to:
31.6.1
OC-3
STM-1
VT-1.5 mapper
TU-12 mapper
HSA Cards
(400)
31.6-1
31.6.2
four VT 1.5s
three VT-2s
two VT-3s
one VT-6
31.6-2
(400)
HSA Cards
VT - 1.5
or
VT - 2
x4
x3
or
or
VT - 3
x2
VT - 6
x1
VT group
x7
STS - 1 link
or
x3
STS - 1 circuit
x3
OC - 3
9627
VT_1.5*
VT_2
VT_3
VT_6
SK000922
HSA Cards
(400)
31.6-3
31.6.3
TU-11
or
TU-12
x4
x3
or
TU-2
x2
TUG-2
x7
AU-3 link
x3
or
AU-3 circuit
x3
STM-1
9628
The STM-1 card AU-4 link contains three TUG-3s. Each TUG-3 has the same
bandwidth as an AU-3, and like an AU-3, can be configured as a link or as a circuit.
A TUG-3 can be configured to accommodate:
31.6-4
(400)
HSA Cards
TU-11
TU-12
x4
TU-2
x3
x1
TUG-2
or
x7
TU-3
x1
TUG-3
x3
AU-4 link
STM-1
9629
TUG-2s are available on AU-3 and TUG-3 links. In either mode, a TUG-2 can
accommodate one of the following configurations:
four TU-11s
three TU-12s
one TU-2
In AU-4 mode, an AU-4 is divided into three TUG-3 structures. Each of the three
TUG-3 structures can be configured as TUG-2 structured, or TU-3 structured. TUG-2
mode must be selected before TUG-2 sub-structure is configured. If TU-3 structure
is selected, the TUG-3 is mapped as a TU-3 circuit.
HSA Cards
(400)
31.6-5
TU2
TU11
TU12*
SK000894
where
Hn-ss-pa is an AU-3 or TUG-3 identifier
tugnum is a TUG-2 number between 1 and 7
31.6-6
(400)
HSA Cards
31.6.4
31.6.5
HSA Cards
(400)
31.6-7
All destination circuits must be of the same type as the source circuit, or the
operation will be blocked. You can copy the configuration information of a link to a
circuit, but the destination will change configuration to become a link.
You can assign a name to any broadband circuit, using the NAME softkey. To delete
a circuit name without assigning another one, select NAME and press .
NAME
COPY_TO
COPY_RANGE
<name>
<circuit>
<circuit>
TO
<circuit>
SK000917
where
name is up to 8 alphanumeric characters
the first circuit is the source circuit identifier
the second circuit is the identifier of the destination circuit or the first circuit of the destination range
the third circuit is the last circuit of the destination range
31.6-8
(400)
HSA Cards
31.7
31.7.1
31.7.2
unequipped
equipped, non-specific payload
equipped with a specific payload indicated
An unequipped signal label indicates a signal that contains no data. The signal is
routed to the destination device, but the device does not interpret or pass data from
the signal. You cannot configure a OC-3 or STM-1 card broadband signal label as
unequipped.
An equipped signal label indicates a signal that is expected to contain data. If a link
or circuit with an equipped signal is connected to a distant node, the signal label tells
the node that data is present in the payload, and specifies the format of the data.
An equipped-nonspecific payload is used to pass data to a node that does not
support payload-specific signal labels.
Table 31.7-1 shows the signal label options for the applicable cards and circuits.
HSA Cards
(400)
31.7-1
Link or Circuit
Signal Label
Option
OC-3
STS-1 link
equipped-nonspecific payload
equipped-VT-structured
NON_SPECIF
VT_STRUCT
STM-1
equipped-nonspecific payload
equipped-TUG structured
NON_SPECIF
TUG_STRUCT
VT-1.5
VT-1.5 circuit
equipped-nonspecific payload
equipped-asynchronously mapped DS1
NON_SPECIF
ASYNC_DS1
TU-12
TU-12 circuit
equipped-nonspecific payload
equipped-asynchronously mapped E1
NON_SPECIF
ASYNC_E1
31.7-2
(400)
HSA Cards
31.8
31.8.1
HSA Cards
(400)
31.8-1
31.9
31.9.1
bidirectional
pass-through
UPSR add-drop
Broadband circuit connections are connections between two or more broadband
circuits.
Broadband circuits can be connected to other broadband circuits of equal
bandwidth. Table 31.9-1 shows the valid circuit connections for HSA cards.
Table 31.9-1: Valid Broadband Circuit Connections
Circuit Type
HSA Cards
AU-3 (C3)
TU-3
TU-2
TU-2, VT-6
TU-12
TU-12, VT-2
TU-11
TU-11, VT-1.5
STS-1
VT-6
VT-6, TU-2
VT-3
VT-3
VT-2
VT-2, TU-12
VT-1.5
VT1.5, TU-11
(400)
31.9-1
Circuit
S1117-H1-00
Name
Toronto:A
Type
H2-V01
VT-1.5
UPSR Add/Drop Protected By
Alarms:1
Circuit
<->
->
H1-A-1-1-01
H1-B-1-1-01
11-May-1997
8:35a
Name
Type
Mode
NbrigeA
VT-1.5
VT-1.5
Work
Prot
1-SHOW_GROUP
6-UPSR
2-DISCONNECT
7-
3-TO_CIRCUIT
8-CANCEL
4-PASS_THRU
9-QUIT
5-RAP+ID
0-
31.9-2
Description
blank
There is no connection.
<>
>
The circuit listed to the right of the symbol is the protection circuit in a UPSR
protected connection.
(400)
HSA Cards
31.9.2
First
STS-1
VTG-1
VTG-2
VTG-3
Second
STS-1
First
VT1.5
VTG-1
Second
VT1.5
Second
VT1.5
VTG-3
VTG-4
VTG-5
Third
STS-1
First
VT1.5
VTG-6
VTG-7
VTG-2
VTG-4
Third
VT1.5
Third
VT1.5
Fourth
VT1.5
Fourth
VT1.5
to
H1 OC-3 card
H1-A-1-1-1
First
STS-1
Second
STS-1
VTG-5
VTG-6
Third
STS-1
VTG-7
H2 OC-3 card
H2-A-3-3-2
9425
HSA Cards
(400)
31.9-3
Note
If the first circuit is already connected, a warning appears after you select
TO_CIRCUIT, but you can proceed. If you proceed, the previous connection is
broken. After you enter the identifier of the second circuit, a warning appears and
the connection is broken if that circuit is already connected.
manual disconnection
configuring a new connection
A manual disconnection severs the existing connection, leaving the two circuits
disconnected. If two broadband circuits are connected, and a new connection is
configured for one of the circuits, the new connection is made, and the previous
connection is severed.
CONFIG CONNECT <circuit> DISCONNECT PROCEED
where circuit is a connected broadband circuits
31.9.3
Pass-through Connections
A pass-through connection is used to cross connect circuits on two distant nodes by
passing the connection transparently through an intermediate node. No data
dropping or adding occurs on the intermediate node.
A pass-through connection connects two circuits that appear in the same bandwidth
position on each ring. For example, a pass-through connection is made from the first
VT-1.5 to the first VT-1.5 on the mate card.
A pass-through connection made between two VT-1.5 circuits is shown in
Figure 31.9-3.
31.9-4
(400)
HSA Cards
First
STS-1
VTG-1
VTG-2
VTG-3
Second
STS-1
First
VT1.5
VTG-1
Second
VT1.5
Second
VT1.5
VTG-3
VTG-4
VTG-5
Third
STS-1
First
VT1.5
VTG-6
VTG-7
VTG-2
VTG-4
Third
VT1.5
Third
VT1.5
Fourth
VT1.5
Fourth
VT1.5
to
First
STS-1
Second
STS-1
VTG-5
VTG-6
Third
STS-1
VTG-7
H2-B OC-3 card
H1-B-1-1-1
9427
Note
A pass-through connection involving STS-1, TU-3 or AU-3 circuits is switched
through leaving the higher order path labels unaltered.
31.9.4
HSA Cards
(400)
31.9-5
First
STS-1
VTG-1
VTG-2
VTG-3
Second
STS-1
First
VT1.5
VTG-1
Second
VT1.5
Second
VT1.5
VTG-3
VTG-2
VTG-4
VTG-5
Third
STS-1
First
VT1.5
VTG-6
VTG-7
VTG-4
Third
VT1.5
Third
VT1.5
Fourth
VT1.5
Fourth
VT1.5
VT1.5
First
STS-1
Second
STS-1
VTG-5
VTG-6
Third
STS-1
VTG-7
H2-B OC-3 card
First STS-1
First VT group
First VT1.5
(Add/Drop Circuit)
H3 Mapper card
First VT1.5
9428
Make a terminal add-drop connection between a mapper card circuit and a ring
circuit.
2.
31.9-6
(400)
HSA Cards
2.
HSA Cards
b.
c.
d.
(400)
31.9-7
31.10
31.10.1
preferred (the set of DS0s that you prefer for the data transmission)
level 2 (the set of DS0s used to protect the preferred super-rate)
Note
A DS0 may be involved in a level 2 super-rate connection without being involved in
a preferred super-rate connection.
HSA Cards
(400)
31.10-1
31.10-2
(400)
HSA Cards
16
30
Bandwidth
(DS0s)
Bandwidth
(kb/s)
128
256
512
1024
1920
Bandwidth
(kb/s)
Circuit
Number
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
31 (1)
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
Timeslots
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
x
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
Note
Circuit 31 is only available when the narrowband E1 port is configured for
31_CHAN or CCS framing types, and cannot be involved in a super-rate
configuration on CCS configured links.
HSA Cards
(400)
31.10-3
Super-rate circuits can protect voice or data connections. If the preferred connection
is broken, the entire super-rate connection is broken and the protecting DS0 is
connected to the voice or data circuit.
31.10.2
To configure the super-rate circuit, enter the circuit identifier of the master DS0,
select NUM_CIRCS, and configure the super-rate circuit at the connection level
as:
Enter the number of DS0s in the super-rate bundle. The valid range for the
number of the DS0 depends on which timeslot in the narrowband port is
occupied by the master DS0 in the super-rate connection. If there are not
enough timeslots in the primary rate link for the number of circuits in the
super-rate connection, the system displays an error message.
3.
After you enter the number of DS0s, configure the super-rate format as:
After you have configured the first super-rate bundle, repeat the process for the
connecting super-rate circuit, and enter the same number of circuits as for the
first bundle.
Note
A single DS0 may be configured for both a preferred super-rate connection at one
speed and a level 2 super-rate connection at another speed. A DS0 may be involved
in a level 2 super-rate connection without being involved in a preferred super-rate
connection.
31.10-4
(400)
HSA Cards
MORE
SELECT/
DESELECT*
CLASS
NODE_CLASS
SRC_NUMBER
<class>
<source>
<class>
STATUS_MSG
THRESHOLD
RECOVERY
SOURCE
ENABLE/
DISABLE*
DERIVED
UNDEFINED
<failures> UNLIMITED
RX_ENABLE/
RX_DISABLE
AUTO
EXT_PORT_A
30_SEC
1_MIN
10_MIN
EXT_PORT_B
30_MIN
MANUAL
where
number_of_circuits is the number of DS0s in the super-rate bundle
list_of_circuits is a list of individual DS0s or ranges of DS0s, separated by returns (for example, <n1>
<n2> <n3:n4> specifies that the bundle includes individual DS0s n1 and n2 and the range of DS0s
between n3 and n4)
HSA Cards
(400)
31.10-5
31.11
31.11.1
Option
Transparent
TRANSP
Jam Bit 7
JB7*
Caution
The same type of zero code suppression must be configured at both ends of a
narrowband T1 port.
Transparent framing
The transparent option means that the system does not perform zero suppression.
Devices cross-connected to this narrowband T1 port must use a protocol designed to
ensure a sufficient ones density pattern to avoid line synchronization problems.
Caution
The transparent setting should be used with caution as network equipment could
lose synchronization if the ones density requirement is not satisfied.
HSA Cards
(400)
31.11-1
TRANSP
JB7*
SK000862
31.11-2
(400)
HSA Cards
31.12
31.12.1
The transmit direction is defined by the transmit path from the circuit to its
connected circuit.
The receive direction is defined by the receive path from the connected circuit to
its circuit.
Mapper cards support one-way and two-way trunk conditioning. The default trunk
conditioning direction is two-way.
Note
Regardless of the type of trunk conditioning configured, two-way trunk
conditioning is applied to circuits that are cross-connected to CPSS circuits and voice
compression subframes.
HSA Cards
(400)
31.12-1
Link Faults
Signalling Path
Information Path
Framing Alarm
AIS
Framing Error Rate
Exceeded
Failed State
VT-1.5
Red Alarm
Framing Error Rate
Exceeded
Failed State
Multi-frame Alarm
Incoming TS16 AIS
No change
TU-12
Distant Alarm
TS16 Distant Alarm
No change
No change
VT-1.5
Yellow Alarm
No change
No change
Note
One-way trunk conditioning does not result in the information or the signalling path
being broken in either direction, because the fault lies in the narrowband port circuit
receive path.
31.12-2
(400)
HSA Cards
Table 31.12-2: One-way Trunk Conditioning Signalling and Information Path Codes
Code
Code Transmitted on
Signalling Path
Code Transmitted on
Information Path
All zeros
Notes
1. If the fault signalling configured for this circuit is seized, the system does not transmit an idle code
first, as is the case for two-way trunk conditioning.
2. If the connected circuit is an aggregate interface card circuit configured for DDS rate adaption, an
ASC is transmitted. If it is not configured for DDS, all ones are transmitted.
Figure 31.12-1 shows one-way trunk conditioning for Group 1 link faults.
Figure 31.12-1: One-way Trunk Conditioning (Group 1)
If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Direction of transmission
Fault
If not primary rate circuit,
all 0s.
If primary rate circuit not
carrying a circuit
using DDS, all 1s.
If primary rate circuit
carrying a circuit using
VT-1.5 or
Connected circuit
Narrowband port
DDS, DDS abnormal
TU-12 card
station code (ASC).
Signalling
Information
Direction of transmission
9736
HSA Cards
(400)
31.12-3
Figure 31.12-2 shows one-way trunk conditioning for Group 2 link faults.
Figure 31.12-2: One-way Trunk Conditioning (Group 2)
If primary
rate circuit
SEIZED Signalling
or IDLE
If not primary
rate circuit
Frozen
Fault
Direction of transmission
Connected circuit
Signalling
VT-1.5 or
TU-12 card
Fault
Narrowband port
Direction of transmission
Information
9737
Non-Aggregate
Interface Card
Connected Circuit
Aggregate
Interface Card
Connected Circuit
To Far End
Code Transmitted on
Signalling Path
Code Transmitted on
Information Path
All zeros
Notes
1. Signalling is driven to idle for 2.5 seconds and then fault signalling is transmitted as configured. If
fault signalling is configured as Out-of-service, A, B or C signalling is not driven to idle first.
2. If the connected circuit is an aggregate interface card circuit configured for DDS rate adaption, an
ASC is transmitted. If it is not configured for DDS, all ones are transmitted.
31.12-4
(400)
HSA Cards
Signalling
Fault
Direction of transmission
VT-1.5 or
TU-12 card
Fault
Narrowband port
All 1s
or
DDS ASC
Direction of transmission
Signalling
2.5s
SEIZED
or
IDLE
Signalling
Information
Fault
9735
HSA Cards
(400)
31.12-5
31.12.2
Set one-way or two-way trunk conditioning for the narrowband port. See
section 31.12.3.
2.
Configure the trunk conditioning fault class for the narrowband port. See
section 31.12.5.
3.
You can enable trunk conditioning for certain groups of link faults called fault
classes. Enabling all the fault classes on the narrowband enables trunk conditioning
on that narrowband port.
31.12.3
31.12.4
31.12-6
(400)
HSA Cards
Table 31.12-4 lists the fault classes and explains the alarms in each.
Table 31.12-4: Fault Class Descriptions for Mapper Cards
Fault Classes
TU-12
VT-1.5
Alarm Description
Frame/Red (1)
Framing Alarm
Incoming AIS
Multi-frame Alarm
Incoming TS16 AIS
Red Alarm
Distant/Yellow
Distant Alarm
Incoming TS16 AIS
Yellow Alarm
Failed
Failed State
Failed State
Error
Loopback
CPSS Loopback
activated
In-band Loopback
activated
On-fault Loopback
activated
CPSS Loopback
activated
On-fault Loopback
activated
Notes
1. For TU-12 cards, this is the Frame fault class. For VT-1.5 cards, it is the Red fault class.
HSA Cards
(400)
31.12-7
31.12.5
TU-12 Card
Frame/Red
Distant/Yellow
Failed
Error
Fault Class
Loopback
MORE
FAULT_HNDL
TRUNK_COND
RED_OFF/
YELLOW_OFF/
RED_ON* or
YELLOW_ON* or
FRAME_OFF/ DISTANT_OFF/
FRAME_ON*
DISTANT_ON*
FAILED_OFF/
FAILED_ON*
ERROR_OFF/
ERROR_ON*
LPBK_OFF/
LPBK_ON*
SK000864
31.12-8
(400)
HSA Cards
31.13
31.13.1
VT-1.5 card
TU-12 card
The mapper cards each contain 16 narrowband ports. Framing is configured on
individual narrowband T1 and E1 ports.
31.13.2
D4
ESF
If the framing type is changed from one setting to another, a RED alarm is declared.
This alarm state does not clear until framing is achieved, and the alarm clear time
has passed.
If you attempt to change the framing type from ESF to D4 while one of the T1 circuits
on the port is configured for OOS-B signalling, the attempt is blocked and the
message Cannot change to D4. Some circuits are using OOS-B fault signalling is
displayed.
D4 framing
A D4 frame consists of 193 bits: 24 timeslots containing 8 bits each and one framing
bit. A D4 superframe consists of 12 frames. Figure 31.13-1 shows the D4 framing
format within D4 superframe format.
HSA Cards
(400)
31.13-1
12 D4 frames
10
11
12
2316 bits
12 Framing bits
Framing pattern =
100011011100
Frame 1
Framing bit
Timeslot 1
Timeslot 2
Timeslot 24
8 bits
193 bits
D4 Format
8137
ESF framing
This framing format creates superframes consisting of 24 D4 frames. Figure 31.13-2
shows the ESF format.
Figure 31.13-2: ESF Framing Format
24 D4 frames
21
22
23
24
4632 Bits
24 bits: 6 framing (2 kb/s)
6 error checking (2 kb/s)
9755
31.13-2
(400)
HSA Cards
31.13.3
CAS*
CCS
31_CHAN
Table 31.13-1 shows the timeslot-to-circuit designation for these framing options. A
circuit is a device internal to the node. Narrowband E1 ports are assigned circuits 1
to 31. A timeslot is a channel on the physical narrowband E1 port external to the
node. Narrowband E1 ports are made up of timeslots 0 to 31.
Table 31.13-1: Timeslot-to-Circuit Designation for TU-12 Cards
Switching Order of Circuits (1)
Frame Type
CAS
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 S 16... 28 29 30
CCS and
31 channels
Timeslot
Circuit
0 1 2 3... 15 16 17... 29 30 31
F 1 2 3... 15 31 16... 28 29 30
Notes
1. F = framing; S = signalling
CAS framing
Timeslot 16 is used for CAS and is not user-configurable. Timeslot 0 is used for
framing. The rest of the timeslots are used for information. Timeslots 1 through 15
correspond to circuits 1 through 15 and timeslots 17 through 31 correspond to
circuits 16 through 30.
HSA Cards
(400)
31.13-3
CCS framing
Timeslot 16 corresponds to circuit 31, which can be configured as an additional
64 kb/s data channel (typically for the transport of CCS messages). The rest of the
timeslots are labeled as in CAS: timeslots 1 through 15 correspond to circuits 1
through 15 and timeslots 17 through 31 correspond to circuits 16 through 30. The 31
circuits are treated equally. Timeslot 0 is used for framing.
31 channels framing
This framing pattern has the same designation of timeslots to circuits as CCS.
However, when making super-rate connections (connections that occupy more than
one channel on a primary rate link) to an E1 link, the system does not skip timeslot
16 (the 31st circuit); timeslots 1 through 31 are used consecutively (see Table 31.13-1).
Timeslot 0 is used for framing.
CAS*
31_CHAN
CCS
SK000899
31.13-4
(400)
HSA Cards
31.14
31.14.1
Idle (1)
OOS A
OOS B
OOS C (3)
None
VT-1.5 card
(1)
(2)
(3)
TU-12 card
(4)
(5)
(6)
Card
Notes
1. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or
E&M circuits.
2. Applies to DS0s (on ESF-framed DS1s only) with RBS enabled connected to 56 kb/s (or less) data, OCU-DP or E&M circuits.
3. Applies to DS0s (on either D4- or ESF-framed DS1s) with RBS enabled connected to data or any voice circuits.
4. Applies to timeslots (on CAS-framed links only) connected to data or any voice circuits.
5. Applies to timeslots (on either CCS- or 31 Channel-framed links) connected to data or any voice circuits.
6. Applies to DS0s (on either D4- or ESF-framed DS1s) connected to data or E&M circuits.
HSA Cards
(400)
31.14-1
OOS C (1)
OOS A
OOS B
VT-1.5
0100(01) (2)
0110(n/a)
Yellow/Distant Alarm
TU-12
1111
0110
Yellow/Distant Alarm
Notes
1. When OOS-C is selected for a DS0 and that circuit connection becomes unavailable, a yellow alarm
is generated on the DS1 circuit for a T1 DS0; a distant alarm is generated for an E1 DS0.
2. For ESF-framed DS1s, all four ABCD signalling bits are defined. For D4-framed DS1s, only the AB
signalling bits (shown in brackets) are defined.
31.14.2
31.14-2
(400)
HSA Cards
Note
For VT-1.5 card T1 circuits, fault signalling can be transmitted only if RBS is enabled.
If this condition is not met and OOS-A or OOS-B is selected, a warning message
appears when you attempt the cross-connection.
RBS uses the least significant bit of every channel in frames 6 and 12 (if D4 framing
is used) and frames 6, 12, 18 and 24 (if ESF framing is used). Use RBS with caution
on data circuits.
If you configure fault signalling before the signalling type, the system offers OOS
types A, B and C. If you subsequently select an incompatible signalling type (for
example, an LGS signalling type on a circuit with OOS type A enabled), a warning
message appears.
Restrictions
The following restrictions apply.
For D4-framed T1 circuits connected to E&M or data circuits, you can select
OOSA
OOSB
OOSC
SEIZED
IDLE
SK000928
HSA Cards
(400)
31.14-3
31.15
31.15.1
HSA Cards
VT-1.5 Card
TU-12 Card
Signalling Type
Transparent
SIG
Clear channel
NoSIG
E&M
E+M
Continuous E&M
E+M_B
LGS REM_EXT
LGS EC
(400)
Option
31.15-1
VT-1.5 Card
TU-12 Card
Signalling Type
Option
LGS PLAR
LGE REM_EXT
LGE EC
LGS LS
LGS GS
LGE LS
LGE GS
R2 digital signalling
R2D_E+M
RBS
RBS
Terminate
TERMINATE
Transparent
Transparent
Clear channel
Clear channel
E&M
E&M
E&M
LGS PLAR
Notes
1. DE3 or SE3 to DS-3 or DS-3 II connections are supported only by NoSIG connections.
2. Continuous E&M is used to convert a proprietary signalling type to Newbridge standard E&M
signalling. Continuous E&M is supported if the E1 link is configured for CAS.
3. LGS PLAR is equivalent to D4 PLAR signalling as specified in the 1985 Addendum to PUB 43801.
4. PLAR D3 is equivalent to D3 PLAR signalling as specified in the 1982 Addendum to PUB 43801.
31.15-2
(400)
HSA Cards
PLAR D3 signalling
When LGS PLAR is selected, the system provides signalling according to the 1985
Addendum to PUB 43801. This Addendum specifies support for D4 channel banks
and inverts the state of the signalling bits specified in the 1982 Addendum. When
LGS PLAR_D3 is selected, the system provides signalling according to the 1982
Addendum to PUB 43801. PLAR_D3 signalling supports third-party nodes (such as
D3 channel banks) that still comply with the 1982 Addendum.
R2 digital signalling
If you are connecting a TU-12 card narrowband circuit using R2 digital signalling to
an E&M circuit, you must configure the primary rate circuit as type R2D_E+M.
RBS
RBS is usually used to pass ABCD signalling. When RBS is enabled, the least
significant bit (bit 8) of every channel in frames 6 and 12 (if D4 framing is used) or in
frames 6, 12, 18 and 24 (if ESF framing is used) is overwritten with signalling
information.
You cannot use RBS under the following conditions.
If a DCC, DNIC or 2B1Q Line card circuit with a bandwidth of 64 kb/s or greater
HSA Cards
(400)
31.15-3
31.15.2
SIG for transparent, where signalling is passed without being tested for
In a T1-to-T1 tandem node, if you select NoSIG and enable RBS, the system does not
monitor the signalling of the data received and overwrites the outgoing data bits
with the default RBS pattern.
TERMINATE
NoSIG
SIG*
LS
PLAR
E+M
PLAR_D3
LGS
LGE
GS
LS
GS
SK000866
31.15-4
(400)
HSA Cards
31.15.3
HSA Cards
is passed without being tested for compatibility with the far-end signalling type
(E1_SIG SIG is the default for E1 signalling and for PRI circuits with NUM_SIG
set to a value other than 0)
E1_SIG NoSIG or T1_SIG NoSIG for clear channel E1 or T1 signalling, where a 64
kb/s clear channel is created for which signalling is not passed (default for PRI
circuits with NUM_SIG set at the default value of 0)
E1_SIG E+M E+M or T1_SIG E+M for E&M for E1 or T1 signalling, or E1_SIG
E+M E+M_B for conversion of proprietary E1 signalling to Newbridge standard
E1 signalling
E1_SIG LGS REM_EXT for LGS Remote Extension for E1 signalling
E1_SIG LGS EC for LGS Earth Calling for E1 signalling
E1_SIG LGS PLAR for LGS PLAR for E1 signalling
E1_SIG LGE REM_EXT for LGE Remote Extension for E1 signalling
E1_SIG LGE EC for LGE Earth Calling for E1 signalling
T1_SIG LGS LS for LGS Loop Start for T1 signalling
T1_SIG LGS GS for LGS Ground Start for T1 signalling
T1_SIG LGS PLAR or PLAR_D3 for LGS PLAR for T1 signalling
T1_SIG LGE LS for LGE Loop Start for T1 signalling
T1_SIG LGE GS for LGE Ground Start for T1 signalling
R2D_E+M for R2 digital signalling
(400)
31.15-5
E1_SIG
SIG*
T1_SIG
R2D_E+M
NoSIG
E+M
REM_EXT
LGS
E+M
LGE
E+M_B
PLAR
EC
SIG
LS
NoSIG
GS
EC
REM_EXT
E+M
PLAR
LGE
LGS
PLAR_D3
LS
TERMINATE
GS
SK000867
31.15-6
(400)
HSA Cards
31.16
31.16.1
31.16.2
HSA Cards
(400)
31.16-1
31.17
31.17.1
The system displays the current values for the transmitted and received NU bits.
HSA Cards
(400)
31.17-1
31.18
31.18.1
CRC-4 reframing
link quality monitoring (CRC-4 or FAS)
31.18.2
HSA Cards
(400)
31.18-1
31.18.3
Bit
1
Bit
2
Bit
3
Bit
4
Bit
5
Bit
6
Bit
7
Bit
8
Si
Si
SA4
SA5
SA6
SA7
SA8
Configure the TU-12 card for CRC-4 error detection or FAS statistics:
31.18-2
(400)
HSA Cards
31.19
31.19.1
CODE_1 is the code transmitted on the signalling path when the circuit is
The CODE_1 and CODE_2 bit patterns represent the settings of the ABCD signalling
bits. For D4-framed DS1s, only the AB bits are defined. For ESF-framed T1s and E1s,
all four ABCD bits are defined.
If you change framing on a narrowband from D4 to ESF after configuring CODE_1
or CODE_2, the configured AB bits are copied into the CD bit positions (that is,
ABAB is transmitted).
If an E1 circuit is configured for T1 signalling, you configure only the AB bits; the C
and D bits are fixed at 0 and 1, respectively.
Caution
Never set CODE_1 (idle) and CODE_2 (seized) to all zeros. An all-zero setting can
cause multiframe problems in an E1 network.
Table 31.19-1 lists common seized and idle codes for each signalling type supported
by the system.
HSA Cards
(400)
31.19-1
Table 31.19-1: Fault Signalling Codes Seized and Idle for VT-1.5 and TU-12 Cards
Seized Code
Idle Code
Signalling
TU-12 (1)
VT-1.5(2)
TU-12 (1)
VT-1.5 (2)
DPO/DPT
1111
1111
0000
0000
E&M (T1/NA)
0101
1111
1101
0000
E&M (E1/UK)
1111
0101
0000
1101
LGE_EC
0101
0101
1101
1101
LGE_GS
0000
0000
0101
0101
LGE_LCDC
0101
0101
1101
1101
LGE_LS
1111
1111
0101
0101
LGE_RE
0101
0101
1101
1101
LGS_CBW
1101
1101
1101
1101
LGS_EC
1001
1001
1101
1101
LGS_GS
0101
0101
1111
1111
LGS_LCDC
1001
1001
1101
1101
LGS_LS
0101
0101
0101
0101
LGS_PLAR
0000/0101
0000
0000/0101
1111
LGS_RE
1101
1101
1101
1101
R2D E&M
0011
0011
1011
1011
Notes
1. When T1 signalling is configured on E1 timeslots, the last two bits (C and D) are set to 0 and 1,
respectively.
2. Codes shown are for ESF-framed T1s (which use all four ABCD bits). For D4-framed T1s, only the
first two bits (AB) are transmitted.
31.19.2
CODE_1 for the code transmitted on the signalling path when the circuit is
configured to transmit Idle fault signalling (the default is 0000)
CODE_2 for the code transmitted on the signalling path when the circuit is
31.19-2
(400)
HSA Cards
CODE_1
CODE_2
<code> <code>
DATA
<data>
SK000865
where
code is a 2- or 4-digit binary code
data is an 8-digit binary code
HSA Cards
(400)
31.19-3
31.20
31.20.1
HSA Cards
(400)
31.20-1
31.20.2
Connection Types
Dedicated, shared
Control card
DCP card
NONE (default)
VIA_CPSS
31.20.3
2.
31.20-2
(400)
HSA Cards
Index
Index
Issue 1, November 1997
Index
1_BIT, 22.3-14
1200, 21.6-3
150, 21.6-3
16+, 19.3-3
2_BITS, 22.3-14
24_DS0, 20.16-4
2601 MainStreet DTU, 22.1-6
2602 MainStreet DTU, 22.1-6
2603 MainStreet DTU, 22.1-6
2606 MainStreet DTU, 22.1-7
2608 MainStreet DTU, 22.1-7
2610 MainStreet DTU, 22.1-8
2612 MainStreet DTU, 22.1-6
2613 MainStreet DTU, 22.1-6
2600 MainStreet series DTUs, 3.12-2
2701 MainStreet DTU, 22.1-6
2702 MainStreet DTU, 22.1-6
2703 MainStreet DTU, 22.1-6
2715 MainStreet DTU, 22.1-6
forced activity switching, 22.3-27
27LC2 line card, 22.1-2
link quality statistics, 34.1-27
BER threshold, 34.1-29
reset, 34.1-29
view, 34.1-29
2700 MainStreet series DTUs, 3.12-4
2B1Q, 22.2-2, 22.2-4
2B1Q Channel Unit
3DS-0 transmission format, 22.3-34
configuring, 22.1-8
5DS-0 transmission format, 22.3-34
connections, 22.3-36
diagnostics, 7.5-5
faceplate, 7.5-4
functional description, 7.5-2
functions, 22.1-4
ISDN basics, 22.3-32
ISDN loop extension, 22.3-33
loopbacks, 7.5-5
overview, 7.5-1
performance monitoring, 22.3-36
pinout, 14.10-10
quality statistics, 34.1-29
slot configuration, 22.2-4
specifications
physical, 7.5-6
zero byte substitution, 22.3-36
2B1Q Line card, 22.1-2
DTU activity switching, 22.3-25
pinout, 14.10-1, 14.10-11
2-second timer, 18.3-4
2-WIRE, 21.4-1
3.1KHZ, 30.4-4
3_DS0, 22.2-4
31 channels, 20.6-5
3600 MainStreet, 1.2-1
3600+ MainStreet, 1.2-3
alarms
alarm panel, 3.13-1
architecture, 2.2-3
cooling: blower unit, 3.9-7
power feeds, 3.7-4
power supply cards, 3.7-2
LEDs, 3.7-13
slot locations, 3.7-5
redundancy
types, 2.1-12
ringing generators: external, 3.8-6
connectors, 3.8-11
connector pinout, 3.8-10
system configuration, 2.3-4
timing and synchronization, 2.1-9
36120 MainStreet, 1.2-5
36120_ID, 25.4-7
3664 MainStreet, 1.2-4
3DS-0 transmission format, 22.3-34, 29.3-3
3DS-0 transport, 29.3-9, 29.3-10
3DS0_ENAB/DISAB, 29.3-9
4 kb/s CPSS channels, 17.6-27
4600 MainStreet, 17.6-33
4601 MainStreet Network Manager, 16.2-4
4602 MainStreet Intelligent NetworkStation,
16.2-4
MainStreetXpress 46020 Network Manager,
16.2-4
4KPBS, 24.2-2
4W_TO, 21.2-3, 22.2-4
4WDX Channel Unit, 21.1-1
diagnostics, 6.5-4
equalization, 21.11-1
faceplate, 6.5-3
IN-1
Index
Issue 1, November 1997
IN-2
A
A_LAW, 23.4-4
A_STD_ON/OFF, 25.9-5
absent card, 18.3-4
absolute address, 26.3-1
Absolute Congestion Threshold
configuring for encapsulation circuits,
25.10-8, 27.13-9
configuring for frame stream circuits,
27.13-15
ac power feeds
Class A locally controlled shelf
ac power cable connections, 13.29-1
Class A peripheral shelf
ac power cable connections, 13.29-1
Class A switching shelf
ac power cable connection, 13.29-1
Class B locally controlled shelf
ac power cable connections, 13.29-1
Class B peripheral shelf
ac power cable connections, 13.29-1
Class B switching shelf
ac power cable connections, 13.29-1
HSPS
ac power cable connection, 13.29-1
ac power supplies
input specifications, 3.7-6
power cables, 3.7-8
upgrade kits, 3.7-7
variants, 3.7-7
AC15 tone detection, 23.3-11
ACCES_PROT, 18.1-6
ACCESS, 20.16-4
access
direct, 27.13-1
encapsulated, 27.13-2
subrate, 27.13-7
super-rate, 27.13-1
access levels, 17.5-1
and control redundancy, 17.5-1
configuring, 17.5-1
defining, 17.5-4
access rate, 25.1-4, 25.5-3
accounting
accounting agent, 38.1-11
accounting generation subsystem, 27.11-1
accounting NVM buffer size parameter,
27.10-22
accounting segments, 27.10-2
accounting segment size parameter,
27.10-19
accounting activation parameter, 27.15-4,
28.3-3
accounting parameters, 27.10-15
collection intervals, 27.10-3
configuration, 27.12-1
description, 27.10-1
end records, 27.10-5
intermediate records, 27.10-4
periodic records, 27.10-6
records, 27.10-3
statistics, 34.5-11
status, 33.11-5
time synchronisation, 27.10-7
time-change records, 27.10-8
accounting records
description, 27.10-3
NVM storage, 27.10-10
paced generation of, 27.10-9
transfer to the data collector, 27.10-10
ACO pushbutton, 33.1-16
ACT, 25.4-7
active card, 18.3-1, 18.3-4
Activity LED
DS-3 card, 18.1-4
E3 card, 18.1-4
Index
Issue 1, November 1997
IN-3
Index
Issue 1, November 1997
IN-4
ALTERNATE, 21.7-3
Alternate Mark Inversion, 10.6-8
alternate path routing, 26.5-5
alternate route, 26.5-2
AMI, 10.6-8, 10.6-11, 10.6-19, 10.6-22
analog and digital tone tests
GFC3, 36.4-14
Annex F encapsulation, 25.10-3, 27.13-3
Annex G encapsulation, 25.10-2, 27.13-2
ANS
ANS master, 17.2-8, 17.2-9
ANS reachable, 17.2-9
ANS source, 17.2-8, 17.2-10
configuring, 17.2-13
CPSS, 17.2-7
definition, 33.9-1
displaying links, 17.2-14
enabling, 17.2-13
links, 17.2-8
bidirectional, 17.2-9
configuring, 17.2-14
disabling ANS, 17.2-15
enabling ANS, 17.2-15
link failure recovery time, 17.2-16
link failure threshold, 17.2-16
SSU failure recovery time, 17.2-17
SSU failure threshold, 17.2-17
unidirectional, 17.2-9
valid, 17.2-15
programmable derived source, 17.2-19
programmable external source, 17.2-19
transport layer, 17.2-7
viewing basic node information, 33.9-2
viewing network topology information,
33.9-4
zones, 17.2-10
configuring, 17.2-13
ANS v2, 2.1-11
ISSU, 2.1-11
link recovery, 33.9-13
source
derived, 2.1-10
external, 2.1-10
internal, 2.1-10
SSU, 2.1-11
synchronization information
links, 33.9-10
sources, 33.9-7
statistics, 33.9-13, 33.9-15
ANSI, 29.3-4, 29.4-3
ANSI T1.617a
Annex F, 27.13-2
Annex G, 27.13-2
anti-static precautions, 10.8-7, 12.1-2
antistatic strap, 13.1-2
ANTISTREAM, 23.7-7
antistreaming, 23.4-3, 23.7-3
APP_MOD, 20.5-2, 20.16-4
APPLI, 25.9-7
APPLIC, 25.5-3
application cards, 3.14-5
Application module
ID, 33.3-1
revision, 33.3-1
type, 33.3-1
variant ID, 33.3-1
AQA, 18.2-5, 22.3-28
AS_PER_MJU, 23.7-7
ASCII (VT100) terminal, 16.2-5
ASIA, 21.2-4
associated signalling profile, 26.2-3
ASSUMED_ON/OFF, 22.3-7, 22.3-16
ASYNC, 22.3-2
asynchronous device mode, 22.3-2
audio wires, 21.4-1
AUTO, 20.6-3, 23.3-7, 23.5-4, 30.3-5
AUTO_TEI, 30.3-6
automatic log-off, 16.3-11
Automatic Network Synchronization, 17.2-1
B
B channels, 22.3-32, 29.1-2
B1+B2, 29.3-7
B1+B2+D, 29.3-7
B1+D, 29.3-7
B1_ONLY, 29.3-7
B2+D, 29.3-7
B2_ONLY, 29.3-7
B8ZS, 20.8-2
backbone trunks
cost, 27.8-3
definition, 27.1-2
description, 27.8-1
poll timer, 27.8-4
provisioning, 27.8-6
Background diagnostic tests
restart, 33.2-17
sequencing, 33.2-12
viewing, enabling or disabling, 33.2-13
backplanes, 3.6-22
architecture, 3.6-6
Index
Issue 1, November 1997
HSPS, 3.6-15
HSPS architecture, 3.6-18
HSPS2, 3.6-17
HSPS2 architecture, 3.6-20
locally controlled/peripheral shelf, 3.6-9
switching shelf, 3.6-2
Balanced Transceiver card
faceplate, 4.1-3
installation, 13.14-1
LEDs, 4.1-3
overview, 4.1-1
specifications, 4.1-4
Balanced Transceiver cards and cables, 40.10-1
bandwidth, 25.1-3
bandwidth utilization, 20.19-1
FRE card, 8.4-3
FRS card, 8.5-2
MPA card, 20.20-1, 20.20-7, 20.20-8
barring
within CUGs, 27.15-23
Base LCN parameter, 27.14-15, 28.2-10
Basic Rate Interface, 22.3-32
BASIC_RATE, 29.2-1
baud rate, 17.3-8
baud rate generator, 22.3-9
BAUD_RATE, 17.3-8
Bc, 25.1-4, 25.8-5
B-channel search order, 30.3-5
Be, 25.1-4, 25.8-5
bearer capability, 30.4-4
bearer service, 30.3-5
BEARER_SVC, 30.3-5
BER, 18.1-15, 20.18-6
BERT, 4.6-6
audible error bell, 36.5-6
bit error injection, 36.5-7
bit error insertion rate, 36.5-6
bit patterns, 36.5-7
clearing statistics, 36.5-9
configuration, 36.5-4
DDS control codes, 36.5-9
GFC3, 4.8-12
overview, 36.5-1
round trip delay measurement, 36.5-11
statistics, 36.5-13
Test card, 36.3-1
test functions, 36.5-6
BERT statistics
clearing statistics, 36.5-16
BIAS_AGNST, 17.3-10, 17.6-17, 17.6-19
BIAS_TOWRD, 17.3-10, 17.6-17, 17.6-19
Bit Error Rate, 20.18-6
IN-5
Index
Issue 1, November 1997
IN-6
C
C, 22.3-7
C_BIT, 20.6-3
cabinets, 3.5-10
cable exit cover, 13.16-11
cable requirements, 12.1-2
CABLE_NAME, 25.4-6
cables
Class A intershelf, 40.10-1
cabling
DTUs, 10.4-3
external equipment, 10.4-2
CAC, 26.4-5
cadence, 3.8-1, 6.4-1
MRD Channel Unit, 6.9-2
call clearing, 26.5-6
Call Deflection parameter, 27.15-15
call identification allocation, 26.4-4
Call Redirection facility, 27.15-8
call reference allocation, 26.4-4
call routing
definition, 27.7-1
process, 27.7-12
call screening
description, 27.14-29
process, 27.14-36
CALL_LOG, 17.3-7
Called Line Address Modification Notification
facility, 27.15-8
called party number, 30.4-2
CANCEL, 16.3-6
CANCEL_ON/OFF, 23.3-9
card, 16.5-1
failures, 18.3-8
alarm, 18.3-9
ID, 33.3-1, 16.5-5
loopbacks, 36.7-14
power-up diagnostics tests, 33.2-2
reset, 8.6-4, 36.11-1
FRE card, 8.4-7
FRS card, 8.5-8
revision, 33.3-1
type, 33.3-1
display, 16.5-5
variant ID, 33.3-1
view, 33.3-2
Card Activity Change alarm, 18.3-6
CARD_COMM, 30.2-1
CARRIER, 19.3-4
CAS, 20.6-5
Cascade A Insert LED, 33.1-3
Cascade B Insert LED, 33.1-3
Cascade Module
FIP connection, 14.15-1
cause codes, 34.4-1
format, 27.14-24
viewing and resetting, 34.4-4
C-bit parity, 20.6-2
CBW, 21.3-7
CC, 27.15-1
CCITT X.50,, 23.6-11
CCITT X.51,, 23.6-11
CCITT X.54,, 23.6-11
CCM, 5.3-9, 17.1-6, 18.2-6, 20.1-2, 20.3-2
CCS, 20.6-5
CCT, 20.3-3
CH_SRCH_HI/LO, 30.3-5
channel identifiers, 16.4-1
channel search facility
hunt groups, 30.4-3
Channel Service Unit Module, 5.3-11
Index
Issue 1, November 1997
Channel unit
line balance calibration, 40.1-1
power-up diagnostics tests, 33.2-2
channel-associated signalling, 20.6-5
CHAR_LEN, 22.3-14
character length, 22.3-13
charging facilities, 27.15-7
Charging Information Request Allowed
parameter, 27.15-11
Charging Information Subscription parameter,
27.15-11
chassis ground, 3.5-9, 10.8-1, 20.18-4
CHG_SET, 23.9-2, 23.9-5, 23.9-8
CI, 16.2-4
CIR, 25.1-4
CIR, for connection management, 26.4-4
circuit configuration
copying, 17.1-5
displaying, 17.1-3
naming, 17.1-5
circuit connections, 17.1-1
add-drop, 31.9-1
broadcast unidirectional, 17.1-8
configuring, 17.1-2
pass-through, 31.9-1
simple bidirectional, 17.1-6
simple unidirectional, 17.1-7
TS0, 17.1-9
types, 17.1-1
UPSR, 31.9-1
circuit identifiers, 16.4-1
Circuit LED, 33.1-3
circuit protection, 20.16-1
24 DS-0 super-rate, 20.16-1
CPSS connections, 20.14-3
circuits connections
HCV voice compression, 23.3-12
CLAMN, 27.15-8
CLASS, 17.2-23
class
node, 17.2-23
timing sources, 17.2-23
class-of-service parameters
configuring for encapsulated access,
27.13-22
configuring for FASTbus trunks, 27.6-21
guarantee, 26.4-5
parameters, 25.1-4, 25.8-5
clear cause codes, 37.1-2
clear channels, 20.12-6
Clear On Calling Address Failure parameter,
28.3-8
IN-7
Index
Issue 1, November 1997
IN-8
Index
Issue 1, November 1997
IN-9
Index
Issue 1, November 1997
convection, 3.9-1
cooling
convection, 3.9-1
DTU heat dissipation, 10.2-10
equipment, 3.9-1
fan trays, 3.9-4
forced air, 3.9-1
FRE card, 10.2-5
guidelines, 10.2-1
heat deflection, 3.9-1
heat deflectors, 3.9-2
heat dissipation, 10.2-6
high speed peripheral shelf, 10.2-4
J24R/J24, 3.9-5
methods, 3.9-1, 10.2-3
PE card, 10.2-6
peripheral shelf, 10.2-4
requirements, 3.9-1, 10.2-3
Switching shelf, 10.2-3, 10.2-4
COPY XAC parameters, 27.16-1
COPY_ADJ, 17.1-5
COPY_TO, 17.1-5
COS guarantee, 26.4-5
setting, 26.4-5
cost, 17.6-5
Cost parameter, 27.8-3
counters, 26.2-7
CPC, 30.2-1
B-channel search order, 30.3-5
bearer capability, 30.4-4
bearer service, 30.3-5
BRI initialization, 30.3-6
call status information reporting, 30.3-5
called party number, 30.4-2
configuration procedure locations, 30.1-1
diagnostics, 8.1-4
dial delay, 30.4-5
dial or non-dial, 30.4-5
directory number, 30.4-1
duplicate, 30.4-3
directory number format, 30.4-2
faceplate, 8.1-2, 9.1-3
functional description, 8.1-1, 9.2-3
interface standard, 30.3-4
interface type, 30.3-4
ISDN backup, 30.3-1, 30.4-1
ISDN channel search, 30.3-2, 30.4-1
ISDN indices, 30.4-1
ISDN Layer 2 and Layer 3 message tracing,
33.7-3
ISDN Layer 2 status display, 33.7-6
ISDN protocol trace status display, 33.7-6
IN-10
PRI cards
channel limitations, 17.6-11
router version, 17.6-4, 17.6-17
satellite delay, 17.6-19
serial ports, 17.3-10
shared, 17.6-1
shared cost, 17.6-17
status information, 17.6-10
subrate channels, 17.6-27
subrate sets, 23.9-7
systems supporting, 1.2-1
v1, 17.6-3
v2, 17.6-3
versions, 17.6-3
viewing nodes, 33.8-1
CPSS Loopback Detected alarm
logging restrictions, 35.1-9
CPSS_4K, 23.9-7
CPSS_COST, 17.3-10
CPSS_MODEM, 17.3-7
CPSSv2
node information display descriptions,
33.8-6
viewing links
all, 33.8-9, 33.8-10
Craft Interface, 16.2-4
crankback, 26.5-5
CRC4 reframing, 20.18-10
CRC4_STATS, 20.18-11
CRCREFR OC E18-, 20.18-10
Critical Alarm LED, 33.1-3
CRN, 27.15-8
CSU, 20.1-2
CSU Loopback Activated alarm
logging restrictions, 35.1-9
CSU Module, 5.3-11
CSU module, 18.3-6
CTL, 19.3-2
CTL_MON, 23.7-7
CTS, 20.20-12, 22.3-7
CUG index, 27.15-20
CUGIA, 27.15-24
CUGOA, 27.15-24
CUSTOM, 20.11-3, 22.3-7
custom trunk conditioning, 20.11-1
D
D channel, 22.3-32, 29.1-2
D+ channel, 22.3-34
D+CV channel, 22.3-34
D4, 20.6-3
Index
Issue 1, November 1997
IN-11
Index
Issue 1, November 1997
IN-12
loopbacks, 7.3-6
multidrop data bridges, 22.3-15
overview, 7.3-1
parity, 22.3-13
rate adaption, 22.4-1
RTS signal propagation, 22.3-16
RTS/CTS delay, 22.3-4
slot configuration, 22.2-1
Special mode
to set, 10.5-11
specifications, 7.3-6
SRMs, 23.6-24
stop bits, 22.3-13
synchronous, 22.3-2
DCD, 20.20-12, 22.3-7
DCE, 20.19-6, 20.20-1, 20.20-4, 22.3-2
DCP, 24.2-2
DCP card
configuration procedure locations, 24.1-1
faceplate, 8.2-2
functional description, 8.2-2
overview, 8.2-1
pinout, 14.10-1, 14.10-18
serial ports, 8.2-3, 17.3-4, 17.6-33
slot configuration, 24.2-1
specifications, 8.2-4
DDS, 22.2-2, 23.6-47, 23.6-49, 23.9-7, 23.9-8,
25.9-7, 25.9-10
DDS Access, 23.6-5
DDS Core, 23.6-6
DDS loopbacks, 36.7-6
DDS rate adaption
cards supporting, 23.6-4
continuity checking, 23.6-45
DDS Access, 23.6-5
DDS Core, 23.6-6
formatting, 23.6-4
interface speed, 23.6-42
MJUs, 23.7-3
multi-drop data bridges, 23.7-2
secondary channel, 23.6-45
SRMs, 23.6-19
subframe position, 23.6-43
subrate sets, 23.9-7
DDS Telco, 23.6-5
DDS_ACCESS, 22.2-2, 23.6-47, 23.7-5
DDS_CORE, 23.6-47, 23.7-5
DDS_HCM, 22.3-17, 22.4-5, 23.7-5
DDS_OR_HCM, 25.9-4
DE3 card, 20.1-1
LEDs, 14.2-1
power-up LED activity, 33.1-14
Index
Issue 1, November 1997
DE3 card
alarm LED numeric value, 39.2-6
default configuration database, 39.2-12
loopbacks, 36.7-26
replace an inactive, 40.9-1
DECL_TIME, 23.7-7
declare time, 35.4-1
DEDICATED, 30.2-1
dedicated cost, 17.6-5, 17.6-19
Default NPI parameter, 27.14-22, 28.2-16
Default NUA parameter, 27.15-13
Default NUI Format parameter, 27.15-16
Default Receive Packet Size parameter, 28.3-6
Default Receive Throughput Class parameter,
28.3-5
Default Receive Window Size parameter,
28.3-4
Default Send Packet Size parameter, 28.3-6
Default Send Throughput Class parameter,
28.3-5
Default Send Window Size parameter, 28.3-5
default user, 26.3-3
defaults
flow control, 27.15-26
NPI, 27.14-22
throughput class, 27.15-26
deflection, 27.15-15
DEL_FR_SET, 23.9-8
DEL_SET, 23.9-8
delay equalization, 5.5-4, 20.15-4, 23.10-2
DELTA, 20.4-7
delta signalling, 20.4-1
Delta Value parameter, 27.6-20
DELTA_G3, 20.4-7
Demerit
system monitoring, 33.4-2
demerit points, 18.3-8
demerits, 33.4-1
activity switch caution, 33.4-4
DERIVED, 17.2-19, 17.2-22
derived timing source, 17.2-1
DESELECT, 17.2-23
DEST, 25.8-3
destination address, 26.5-2
device gender, 20.20-1, 20.20-4, 22.3-2
device mode, 22.3-2
device type, 17.3-6
device types
personal computer, 17.3-7
printer, 17.3-6
VT100 terminal, 17.3-6
DGM, 20.17-1
IN-13
Index
Issue 1, November 1997
diagnoistic tests
General Facilities cards, 4.8-16
Diagnostic Code Mapping parameter, 28.2-17
Diagnostic code mapping parameter, 28.1-9
diagnostic codes, 37.1-3
enhanced, 27.14-25
diagnostics
2B1Q Channel Unit, 7.5-5
4WDX Channel Unit, 6.5-4
background and directed, 33.2-9
background on inactive card, 33.2-13
BRI S/T card, 7.2-5
cicuit level, 33.2-15
Clock card, 4.2-5
Control card, 4.6-6
Control card, 4.5-8
CPC, 8.1-4
directed, 33.2-17, 33.2-18
DS-0 DP Channel Unit, 7.7-4
DS-3 card, 5.1-10
DS-3 II card, 5.1-10
E&M card, 6.2-5
E&M Channel Unit, 6.6-4
E1 card, 5.3-19
E3 card, 5.2-7
failures, 33.2-16
forced at power-up, 33.2-19
HSA card directed, 33.2-18
LGE card, 6.3-5
LGE Channel Unit, 6.7-4
LGS card, 6.4-5
LGS Channel Unit, 6.8-4
MRD Channel Unit, 6.9-4
OCU-DP Channel Unit, 7.8-4
partitioned mode, 18.1-9
Switching card, 4.9-4
Switching Interface card, 4.10-5
system, 33.2-1
system-wide, 33.2-15
T1 card, 5.3-19
Test card, 4.11-7
TTC2M card, 5.6-6
DIAL, 30.4-5
dial delay, 30.4-5
dial or non-dial, 30.4-5
DIAL_DELAY, 30.4-5
Digital Signal Cross-connect Module, 5.3-11
Digital Signal Processor card, 23.1-1
DIR_NUM, 30.4-2
direct access
description, 27.13-1
IN-14
direct circuit
status information, 33.11-15
direct circuits
configuring, 27.13-7
Direct Connect cards, 22.1-1
directory number, 30.4-1
duplicate, 30.4-3
directory number format, 30.4-2
DISCONNECT, 17.1-6
display, 16.3-4
Display LED, 33.1-3
displaying information, 16.5-1
disruption in service, 18.3-1
dissipation
power and heat dissipation, 10.2-7
Distant Error Rate Exceeded alarm
logging restrictions, 35.1-9
DISTANT_OFF/ON, 20.9-10
distribution box
Class A locally controlled shelf
ac distribution box, 13.26-1
dc distribution box, 13.26-1
Class A peripheral shelf
ac distribution box, 13.26-1
ac distribution box connections,
13.26-1
dc distribution box, 13.26-1
dc distribution box connections,
13.26-1
Class A switching shelf
ac distribution box, 13.24-3, 13.25-1
ac power supply connections, 13.24-3,
13.25-1
backplane connections, 13.24-3, 13.25-1
dc distribution box, 13.24-3, 13.25-1
dc power supply connections, 13.24-3,
13.25-1
power supply connections, 13.24-3,
13.25-1
Class B
backplane connections, 13.27-1
Class B locally controlled shelf
ac distribution box, 13.27-1
ac power supply connections, 13.27-1
dc distribution box, 13.27-1
dc power supply connections, 13.27-1
Class B peripheral shelf
ac distribution box, 13.27-1
ac power supply connections, 13.27-1
dc distribution box, 13.27-1
dc power supply connections, 13.27-1
Index
Issue 1, November 1997
IN-15
Index
Issue 1, November 1997
IN-16
Index
Issue 1, November 1997
IN-17
Index
Issue 1, November 1997
LEDs, 5.3-16
loopbacks, 5.3-19
modules, 5.3-8
overview, 5.3-1
SES limit, 20.17-7
specifications, 5.3-21
Dual T1 card (Wire-wrap adapter)
pinout, 14.10-28
HDSL module, 14.10-31
Dual T1-2 card, 20.1-1
fault classes, 20.9-8
framing, 20.6-1
ISDN backup, 30.3-1
ISDN channel search, 30.3-2
trunk conditioning, 20.9-1, 20.9-7
Dual T1-2 card
24 DS-0 connection, 20.16-5
errored seconds, 20.17-2
faceplate, 5.3-14
functional description, 5.3-6
LEDs, 5.3-16
link monitoring, 20.17-1, 20.17-2
loopbacks, 5.3-19, 36.7-45
maintenance facilities, 36.1-2
modules, 5.3-8
on-fault loopback detection, 20.14-5
overview, 5.3-1
pinout, 14.10-32
power-up LED activity, 33.1-14
quality statistics
clear all, 34.1-33, 34.1-37
clear error events, 34.1-33, 34.1-37
print options, 34.1-34, 34.1-41
print time, 34.1-35, 34.1-42
printing, 34.1-35, 34.1-42
statistics supported, 34.1-31
stop printing, 34.1-35, 34.1-42
view, 34.1-33
SES limit, 20.17-7
specifications, 5.3-21
statistics, 5.3-21
sub-channels, 20.4-5
super-rate protecting connections, 20.16-1
TS24 loopback detection, 20.14-4
DUAL_SHELF, 18.1-5
duplex method, 22.3-3
full, 22.3-3
half, 22.3-3
IN-18
E
E&M card, 21.1-1
audio wires, 21.4-1
card versions, 6.2-2
diagnostics, 6.2-5
faceplate, 6.2-3
functional description, 6.2-1
line balance, 21.7-1
line impedance, 21.6-2
loopbacks, 6.2-5, 36.7-48
overview, 6.2-1
pinout
A-law, 14.10-35
Mu-law, 14.10-36
signalling leads, 6.2-5, 36.2-1
signalling type, 21.3-1
specifications, 6.2-5
statistics, 6.2-5
TLP ranges, 21.5-8
E&M Channel Unit, 21.1-1
audio wires, 21.4-1
diagnostics, 6.6-4
faceplate, 6.6-3
functional description, 6.6-1
installation, 13.43-1
LEDs, 6.6-3
loopbacks, 6.6-5
overview, 6.6-1
pinout, 14.10-37, 14.10-38, 14.10-39
signalling leads, 36.2-1
signalling modes, 21.3-1
signalling states, 6.6-5
signalling type, 21.3-1
specifications, 6.6-5
statistics, 6.6-5
variants, 6.6-2
E&M signalling mode, 21.3-1
E+M, 20.12-5, 20.12-8, 21.2-3, 21.3-4
E.164, 26.3-2
E.164 address format, 27.15-1
E-1 Alarm 1 LED, 33.1-4
E-1 Alarm 2 LED, 33.1-4
E-1 Alarm LED, 33.1-4
E1 card, 20.1-1
CCM, 20.3-2
CRC4 reframing, 20.18-10
E1/T1 Conversion Modules, 20.3-1
faceplate connectors, 5.7-5
fault classes, 20.9-8
framing, 20.6-3
LEDs, 5.7-5
loopbacks, 36.7-26
NU bit, 20.18-2
options, 20.18-1
pinout, 14.10-40, 14.10-41
SAM, 20.3-2
signal ground, 20.18-4
signalling types, 20.12-6
E1 card
alarm declare/clear times, 5.3-21
diagnostics, 5.3-19
faceplate, 5.3-17
faceplate connectors, 5.3-18
functional description, 5.3-4
interface redundancy, 5.3-19
LEDs, 5.3-18
loopbacks, 5.3-19
modules, 5.3-8
overview, 5.3-1
quality statistics, 5.3-21
signalling leads, 5.3-19
specifications, 5.3-21
E1 HDSL LIM, 5.3-12
E1 Line Interface module, 5.3-13
E1 link quality monitoring, 20.18-11
E1/T1 Conversion Modules, 20.3-1
E1_HDSL, 20.1-2
E1_LIM, 20.1-2
E1_PRI, 30.3-4
E1_SIG, 20.12-8, 21.3-7
E3 card, 20.1-1
active and inactive, 18.1-4
alarm declare/clear times, 5.2-8
circuit hierarchy, 5.2-2
diagnostics, 5.2-7
E1 link quality monitoring, 20.18-11
E1id, 5.2-2
E2id, 5.2-2
E3id, 5.2-2
equalization, 20.18-11
faceplate, 5.2-3
FIC card slot configuration, 20.2-5
framing, 20.6-3
LEDs, 5.2-4
loopbacks, 5.2-7
modules, 5.2-3
NU bit, 20.18-2
options, 20.18-1
overview, 5.2-1
protection switching, 18.1-15
redundancy, 5.2-6
replacing, 18.1-18
signal buses, 3.6-21
Index
Issue 1, November 1997
IN-19
Index
Issue 1, November 1997
IN-20
outputs
1.544 MHz, 10.6-10, 10.6-21
2.048 MHz, 10.6-10, 10.6-21
8 kHz, 10.6-10, 10.6-21
DDS composite clock, 10.6-11, 10.6-22
overview, 10.6-1
receivers, 10.6-2, 10.6-12
sources, 10.6-2, 10.6-12
external timing source
Class A locally controlled shelf
J13, 14.7-3
J17, 14.7-3
Class A peripheral shelf
J13, 14.7-3
J17, 14.7-3
Class A switching shelf
J17, 14.7-3
external timing source OC B2-, 17.2-1
External Translation Prefix parameter, 28.2-23
F
F.SYNC LED, 33.1-4
F_POSITION, 22.4-6, 23.6-48, 23.9-8, 25.9-7
Faceplate LEDs, 33.1-4
facilities
Call Redirection, 27.15-8
Called Line Address Modification
Notification, 27.15-8
charging, 27.15-7
Charging Information, 27.15-11
closed user group, 27.15-20
CUG Selection, 27.15-21
CUGIA, 27.15-24
CUGOA, 27.15-24
Fast Select, 27.15-7
Fast Select Acceptance, 27.15-7
Local Charging Prevention, 27.15-11
negotiation, 27.14-11
NUI Override, 27.9-2
NUI Subscription, 27.15-15
Reverse Charge Acceptance, 27.15-10
Facility Data Link, 17.6-23
FAIL_THRES, 17.2-16, 17.2-17
FAIL_TIMED, 17.2-16
failed circuits, 18.3-9
Failed State alarm
logging restrictions, 35.1-9
FAILED_OFF/ON, 20.9-10
fan alarm reporting, 35.6-1
Index
Issue 1, November 1997
fan tray
power connector
23-inch shelf, 13.4-5
Class A shelf, 13.4-2
Class B shelf, 13.4-3
fan trays, 3.9-4
FAS_STATS, 20.18-11
Fast Select Acceptance facility, 27.15-7
Fast Select facility, 27.15-7
FASTbus
36120 ID, 25.4-7
congestion thresholds, 25.4-7
CPSS, 17.6-2
interface, 8.4-3
MAC, 25.4-1
NORMAL, 25.4-2
overview, 8.4-3
PHY, 25.4-1
port A, 25.4-1
port B, 25.4-1
station ID, 25.4-7
station status, 25.4-3
status, 25.4-4
used for backbone trunks, 27.8-8
WRAP_A, 25.4-2
WRAP_B, 25.4-2
FASTbus CPSS
FRE card, 8.4-4
FASTbus Interconnect Panel, 13.8-1
Bypass modules, 3.11-1
Cascade modules, 3.11-1
components, 3.11-1
FASTbus modules, 3.11-1
FASTbus protocol statistics, 34.3-7, 34.3-21
Fault classes, 35.2-3
Distant/Yellow, 35.2-3, 35.4-1
Error, 35.2-3
Failed, 35.2-3
Frame/Red, 35.2-3, 35.4-1
fault classes, 20.9-8
Fault LED, 33.1-4
fault processing, 18.3-1, 18.3-7
fault signalling, 20.10-1, 20.16-1, 21.8-1
configuring, 21.8-1
FAULT_HNDL, 20.9-7, 20.9-10, 20.14-6, 20.16-4
FAULT_SIG, 20.4-7, 20.9-7, 20.10-4, 20.11-3,
20.16-4, 36.3-4
fax
data bandwidth, 23.8-2
DSP4, DSP5 and DSP5H card, 23.8-1
fax transmission level, 23.8-4
NSF frame handling, 23.8-3
IN-21
Index
Issue 1, November 1997
IN-22
FIX_LONG, 21.7-3
FIX_SHORT, 21.7-3
FIXED TEI, 30.3-6
FIXED_BIAS, 21.3-9
FIXED_BIAS signalling mode, 21.3-8
flow control, 17.3-9
defaults, 27.15-26
Flow Control Negotiation facility, 27.14-11
Flow Control Negotiation parameter, 27.14-23
Flow Control Timer parameter, 28.2-15
FLOW_CTRL, 17.3-9
force boot, 36.11-2
FORCE_ON/OFF, 23.11-2
forced activation, 29.4-4
forced activity switching, 22.3-27
FORCED_ON/OFF, 22.3-7, 22.3-16
Fractional T1, 20.1-2
loopbacks, 36.7-45
module, 20.1-3
frame, 3.5-1
frame bandwidth, 23.6-42
frame bandwidth location, 23.6-43
frame relay
encapsulation, 25.10-1
interface to 5ESS, 25.11-1
interface to DMS-100, 25.11-1
SVC call display, 33.6-1
switched access, 25.11-1
configuring, 25.11-4
frame relay encapsulation, 27.13-2
frame relay ping, 33.6-8
frame relay SVC
functionality, 26.1-2
overview, 26.1-1
physical requirements, 26.1-2
Frame Response Timer (T1) parameter, 28.2-4
Frame Response Timer parameter, 27.14-4
frame reversal
configuring, 27.6-18
description, 27.6-16
frame routing rules, 27.6-14
Frame Sequence Numbering parameter,
27.14-4, 28.2-3
frame size
configuring for frame stream circuits,
27.13-15
Frame stream, 25.6-1
configuration, 25.6-1
frame stream, 25.5-1
frame streams
FRE card, 8.4-2
FRS card, 8.5-2
Index
Issue 1, November 1997
IN-23
Index
Issue 1, November 1997
IN-24
loopbacks, 36.7-24
NVM, 33.3-28
statistics, 34.1-35, 34.1-42
view, 34.3-9
stream and station protocol statistics,
34.3-7, 34.3-9
FRS circuits
viewing, 27.13-14
FRS/FRE cards
access rate, 25.1-4, 25.5-3
application, 25.5-3
bandwidth, 25.1-3
Bc, 25.1-4, 25.8-5
Be, 25.1-4, 25.8-5
CIR, 25.1-4, 25.8-5
class-of-service parameters, 25.1-4
configuration overview, 25.1-15
configuration procedure options, 25.1-15
congestion management, 25.1-5
congestion thresholds, 25.3-3, 25.6-5
connections, 25.5-4
data link connections, 25.1-2
DLC class of service, 25.8-1
DLC connections, 25.7-1
DLC status, 25.7-3
FASTbus DLCs, 25.7-7
frame stream, 25.5-1
FRS-to-FRS card DLCs, 25.7-6
heartbeat polling interval, 25.6-7
interface speed, 25.5-3
inter-frame flags, 25.6-6
link management protocol, 25.1-11, 25.6-6
local DLCs, 25.7-5
PVC, 25.1-3
PVC management auto discovery protocol,
25.1-14
slot configuration, 25.2-1
status enquiry message timeout, 25.6-8
status message rate, 25.6-8
stream, 25.5-1
subrate multiplexing, 25.9-1
Tc, 25.1-4
transport bandwidth, 25.5-3
FULL_DPLX, 22.3-3
full-duplex, 22.3-3
Fuse and Alarm Panel, 10.7-1
Fuses
23-inch shelves, 40.14-1
DC powered Class B shelves, 40.13-1
inline fuse, 40.12-1
G
G3_FAX, 23.12-2
GAIN, 23.5-4
GAIN_RANGE, 21.5-7
gateway call routing
process, 27.7-21
gateway routing
definition, 27.7-10, 27.7-19
Gateway TNIC/CNIC parameter, 28.2-18
GDI protocol, 27.11-3
General Facilites cards
pushbuttons, 4.8-15
General Facilities cards, 19.3-7
Alarm module, 4.8-9
BERT, 4.8-12
components, 4.8-7
diagnostic tests, 4.8-16
DS0 Test Access unit, 4.8-11
faceplate, 4.8-13
functional description, 4.8-3
GFC
installation, 13.41-1
GFC3
analog and digital tone tests, 36.4-14
card operation parameters and
options, 19.2-1
DS0 port, 36.4-12
DS0 Port connectors, 4.8-15
Metallic Test Access connections,
36.4-14
MTA connectors, 4.8-15
Rx and Tx DS0 clock connectors, 4.8-15
LEDs, 4.8-14
Metallic Test Access unit, 4.8-10
order wire, 4.8-7, 36.4-1, 36.4-2
Order Wire connectors, 4.8-15
overview, 4.8-1
power rail test points, 4.8-15, 36.1-4
specifications, 4.8-16
synchronization clock, 4.8-9
TEP-1(E) equivalence, 4.8-15
test port, 4.8-8, 36.4-1
Test Port connectors, 4.8-15
tone generator, 36.4-1
tone generator and test port, 36.4-7
Tone Test unit, 4.8-11
Generate Accounting Records on Unsuccessful
Calls parameter, 27.10-18
Generate Accounting Records parameter,
27.10-18
Generate Alarms parameter, 28.2-18
Index
Issue 1, November 1997
IN-25
Index
Issue 1, November 1997
H
HALF_DPLX, 22.3-3
half-duplex, 22.3-3
HCM, 5.5-1, 20.20-1, 20.20-8, 22.4-4, 22.4-6,
23.6-48, 23.6-49, 23.9-8, 23.11-3, 25.9-7, 25.9-9
HCM rate adaption, 23.3-5, 23.6-3, 23.6-17
cards supporting, 23.6-3
data position, 23.6-43
frame bandwidth, 23.6-42
frame bandwidth location, 23.6-43
interface speed, 23.6-40
signalling, 23.6-38
subrate sets, 23.9-6
transport bandwidth, 23.6-35
transport position, 23.6-38
HCM_BW, 22.4-6, 23.6-48, 23.9-8
HCM_TRANS, 22.2-2, 22.4-3, 23.6-47
HCV, 23.8-5
HCV alarm declare and clear times
DSP3 and DSP4, 8.3-4
HCV signalling types
DSP3, DSP4 and DSP5H cards, 23.3-2
HCV voice compression, 23.3-1
companding law, 23.3-7
connecting circuits, 23.3-14
echo cancellation, 23.3-9
HCM rate adaption, 23.3-5
rate adaption parameters, 23.3-4
transparent rate adaption, 23.3-4
HCV_CONFIG, 23.11-2
HCV_OPTION, 23.11-3
HCV_RATE, 23.11-3
HCVD, 23.4-5, 23.5-3, 23.6-47, 23.7-5
HDLC encapsulation, 25.10-1
HEARTBEAT, 25.6-7
heartbeat polling interval, 25.6-7
heat dissipation, 10.2-6, 10.2-7
High Capacity Voice, 23.3-1
High impedance monitor metallic connection,
36.3-7
High speed peripheral shelf
cooling guidelines, 10.2-4
HOT, 18.1-10
Hot Billing parameter, 27.15-5
hot standby, 5.2-6
HSA card
loopbacks, 36.7-51
power-up LED, 33.1-16
IN-26
I
I, 22.3-7
I.430/ANSI, 29.3-4, 29.4-3
I/F_MODE, 22.3-2, 29.3-4, 29.4-3
I/F_SPEED, 22.3-21, 22.3-24, 22.3-29, 22.4-4,
22.4-5, 22.4-6, 23.6-48, 23.6-49, 23.9-8, 25.9-7,
25.9-9, 25.9-10, 36.3-3
I/F_TYPE, 22.3-1
Identifiers, 32.2-1
circuit, 32.2-1
circuit group, 32.2-1
Data Link Connection (DLC), 32.2-1
link, 32.2-1
peripheral shelf (s), 32.2-7
Permenant Virtual Circuit (PVC), 32.2-1
shelf, 32.2-1
shelf-select jumper, 32.2-6
slot, 32.2-1
stream, 32.2-1
switching shelf (w), 32.2-6
identifiers, 16.4-1
channel, 16.4-1
circuit, 16.4-1
circuit group, 16.4-1
DLC, 16.4-1
HSPS, 16.4-6
HSPS numbers (x), 16.4-6
ISDN index OC A4-, 16.4-1
link, 16.4-1
locally controlled shelf (s), 16.4-6
peripheral shelf (s), 16.4-6
peripheral shelf numbers (x), 16.4-6
shelf, 16.4-1
shelf numbers, 16.4-6
shelf-select jumper, 16.4-5
slot, 16.4-1
stream, 16.4-1
switching shelf (w), 16.4-5
IDLE, 20.10-4, 21.8-1
IDLE_TIME, 23.7-7
IFM, 5.3-14, 20.1-2
IHTU modules, 5.3-12
IMC
bonding, 23.10-1
BONDING timers, 23.2-3
configuration features and options, 23.1-8
inverse multiplexing, 23.10-1
slot configuration, 23.2-1
IN_BAND, 20.14-6
Inactivity Timer parameter, 28.2-4, 28.2-14
Inactivity Timer parameter (link layer), 27.14-5
Index
Issue 1, November 1997
IN-27
Index
Issue 1, November 1997
IN-28
J
J2, 3.8-3, 3.8-8
J24F, 3.8-3, 3.8-5
J24R, 3.8-8, 3.8-10
J30, 3.8-8, 3.8-11
JAPAN, 21.2-4
JB7, 20.8-2
jitter, 20.19-8, 20.20-16
K
k parameter, 27.14-4
L
L1 LED, 33.1-5
L1_TYPE, 29.3-4, 29.4-3
L2 LED, 33.1-5
LAPB, 27.14-2
LAPB Address Assignment parameter, 28.1-9,
28.2-2, 28.2-3, 28.2-4, 28.2-5, 28.2-8, 28.2-9,
28.2-10, 28.2-11, 28.2-12, 28.2-13, 28.2-14,
28.2-15, 28.2-16, 28.2-17, 28.2-18, 28.2-19,
28.2-23, 28.2-24, 28.2-25, 28.2-26, 28.3-2,
28.3-3, 28.3-4, 28.3-5, 28.3-6, 28.3-7, 28.3-8
Large multiplexer systems
3600 MainStreet, 1.2-1
36120 MainStreet, 1.2-5
3664 MainStreet, 1.2-4
applications, 2.1-1
MainStreet large multiplexers
description, 1.2-1
shelf requirements, 1.3-2
layer 1 standard, 29.3-4, 29.4-3
LCDC, 21.3-7
LD-CELP post filter, 23.3-11
leaf domains, 27.6-1
leaf switch
configuring, 27.6-17
definition, 27.6-4
Index
Issue 1, November 1997
IN-29
Index
Issue 1, November 1997
IN-30
Index
Issue 1, November 1997
IN-31
Index
Issue 1, November 1997
M
M.SYNC LED, 33.1-7
M13, 20.6-2, 20.6-3
M44 voice compression, 20.4-1
M48 voice compression, 20.4-1
M55 voice compression, 20.4-1
M60 voice compression, 20.4-1
MAC, 25.4-1
MainStreet X.25
configuration summary, 27.4-4
protocols A1-, 27.1-3
switch, 27.1-2
MainStreetXpress 36130
system description, 1.2-1
maintenance commands
undoing, 38.1-12
Maintenance Connections (see Connection
maintenance)
, 36.6-12
Major Alarm LED, 33.1-7
major nodes, 16.2-2
MAKE_ACT, 18.3-6
Mapper card
CPSS loopback detection, 31.20-1
CRC-4, 31.18-1
fault signalling, 31.14-1
Mapper card narrowband circuit
framing, 31.13-1
inversion, 31.16-1
MARK, 22.3-7, 22.3-14
MASTER, 22.3-28, 23.7-3
master and slave designations, 18.3-3
mate E3 card serial bus, 3.6-21
MATE/NO_MATE, 22.3-25
Maximum Allowed Validation Period
parameter, 27.9-11
IN-32
Index
Issue 1, November 1997
IN-33
Index
Issue 1, November 1997
N
N1, 27.14-6
N2, 27.14-4
name
of signalling channel, 26.2-3
of user configuration, 26.3-2
negotiation facilities, 27.14-11
network layer
parameters, 27.14-7
sequence numbering, 27.14-8
status information, 33.11-22, 33.11-24,
33.11-26
timers, 27.14-10
network layer protocol timers, 26.2-6
network layer services, 17.6-5
Network Operations Center, 17.6-16
Network Termination Interface module, 5.3-13
network user address
definition, 27.1-2
description, 27.15-1
Network User Address parameter, 27.15-3,
28.3-2
Network-wide hunt groups, 27.7-16
NEW_SET, 23.9-8
NEXT_SET, 23.9-2, 23.9-5
Nexus PASS, 27.9-1
NI_1, 30.3-4
NI_2, 30.3-4
NMTI, 16.2-1
No Date, 17.4-2
NO_4KPBS, 24.2-2
NO_8K, 22.3-29
NO_ACCESS, 17.5-2
NO_AIS, 22.3-29
NO_COMP, 23.6-49
NO_CONT, 22.4-6
NO_CONT_CK, 23.6-45, 23.6-48
NO_CONV, 18.2-6, 20.2-4
NO_CONV OC E3-, 20.3-2
NO_CRCREFR OC E18-, 20.18-10
NO_INVER, 29.3-6
NO_LEVEL_0, 17.5-7
NO_MODULE, 20.3-3
NO_PROTECT, 18.3-3
NO_RX_INV, 22.3-13
NOC_NUM, 17.6-16
node management sessions
4601 MainStreet, 16.2-4
4602 MainStreet, 16.2-4
46020 MainStreet, 16.2-4
active/inactive nodes, 16.2-3
IN-34
O
OCU_DP, 22.2-4
OCU-DP Channel Unit
configuring, 22.1-8
diagnostics, 7.8-4
faceplate, 7.8-3
fault signalling, 20.10-1
functional description, 7.8-2
functions, 22.1-5
installation, 13.43-1
loopbacks, 7.8-5
overview, 7.8-1
pinout, 14.10-64
Index
Issue 1, November 1997
specifications, 7.8-5
synchronization, 7.8-3
OCU-DP channel unit
error correction, 22.3-30
interface speed, 22.3-29
secondary channel, 22.3-31
slot configuration, 22.2-4
switched 56 kb/s operation, 22.3-31
ODD, 22.3-14
ON_FAULT, 20.14-6
ONE_WAY, 20.9-7
ONE_WAY/TWO_WAY, 20.16-4
ONE_WAY_TO, 20.15-7
ones density, 18.3-6
on-fault loopback detection, 20.14-5
OnStandby, 17.4-2
OOF, 18.1-15
OOS_A, 20.10-4
OOS_B, 20.10-4
OOS_C, 20.10-4
operational status, 26.2-3, 26.3-3
Optical Extension card, 20.1-1, 20.1-2
connections, 5.7-2
faceplate features, 5.7-4
framing, 20.6-1
functional description, 5.7-2
functions, 5.7-2
ground, 20.18-4
loopbacks, 36.7-26
modules, 5.7-4
options, 20.18-1
overview, 5.7-1
SES, 20.18-5
specifications, 5.7-6
trunk conditioning, 20.9-1
Optical Extension card.pinout, 14.10-1
Optical Extension cards, 33.1-14
fault signalling, 20.10-1
NUbit, 20.18-2
Optional User Defined Data Length parameter,
27.10-21
order wire, 4.8-7
Order Wire connectors
General Facilities cards, 4.8-15
originator of PVC, 27.17-12
Outgoing Fast Select Allowed parameter,
28.3-6
Outgoing Restricted Fast Select Allowed
parameter, 27.15-12
Outgoing Unrestricted Fast Select Allowed
parameter, 27.15-12
out-of-service type A, 20.10-4
IN-35
Index
Issue 1, November 1997
P
PACKET, 24.2-2, 25.2-1, 30.2-1
Packet card
loopbacks, 36.7-24
Packet Engine card
definition, 27.1-3
Packet Layer Call Timer (T31) parameter,
28.2-13
Packet Layer Call Timer parameter, 27.14-18
Packet Layer Interface Type parameter,
27.14-14
Packet Layer Restart Timer (T30) parameter,
28.2-12
Packet Layer Restart Timer parameter, 27.14-18
packet segmenting and combining, 27.2-10
Packet Sequence Numbering parameter,
27.14-15, 28.2-9
packet size
configuring for encapsulation circuits,
25.10-8, 27.13-9
defaults, 27.15-27
parameter descriptions
Accounting Activation, 27.15-4, 28.3-3
Accounting NVM Buffer Size, 27.10-22
Accounting Segment Size, 27.10-19
ACT, 27.13-11
address translation and screening, 27.14-37
Aggregate Committed Burst Size, 27.6-21
Aggregate Committed Information Rate,
27.6-21
Alias, 27.6-20
Allocated XAC Number, 27.15-3, 28.3-2
Allowable Packet Sizes, 27.14-23, 28.2-16
Base LCN, 27.14-15, 28.2-10
Bc, 27.13-22
Be, 27.13-22
Call Deflection, 27.15-15
Charging Information Request Allowed,
27.15-11
Charging Information Subscription,
27.15-11
CIR, 27.13-22
Clear On Calling Address Failure, 28.3-8
Clear Timer, 27.14-18
Clear Timer (T33), 28.2-13
closed user group, 27.15-22
Collection Interval, 27.10-20
IN-36
Index
Issue 1, November 1997
IN-37
Index
Issue 1, November 1997
PE card
card reset, 8.6-4
cooling guidelines, 10.2-6
faceplate, 8.6-3
LEDs, 8.6-3
loopbacks, 8.6-4
pinout, 14.10-42
software upgrading, 8.6-5
specifications, 8.6-5
performance monitoring, 22.3-36
Periodic Accounting Activation parameter,
27.15-5, 28.3-8
Periodic Record Interval parameter, 27.10-21
Peripheral shelf
23-Inch
25-pair connectors, 14.10-1
chassis ground points, 13.10-11
dc fuse replacement, 40.14-1
dc power feed connections, 13.33-1
dc terminal block jumpers, 13.33-1
external alarm connector J18 (Alm
Mod 1), 14.14-12
external alarm connector J18 (Alm
Mod 2), 14.14-13
ground points, 13.10-4
intershelf cable connection, 13.14-1
J13 ground option, 14.7-3
J14, 14.8-1
Power Supply card, 13.22-1
redundancy jumpers, 13.11-1
signal ground points, 13.10-2
Class A
ac distribution box, 13.26-1
ac distribution box connections,
13.26-1
ac power cable connection, 13.29-1
cable clamp, 13.30-1
chassis ground, 13.10-11
chassis ground points, 13.10-11
dc distribution box, 13.26-1
dc distribution box connections Class
A dc distribution box connections,
13.26-1
dc power feed connections, 13.30-1
dc terminal block jumpers, 13.30-1
dc terminal block/cable harness,
13.30-1
external alarm connector J18 (Alm
Mod 1), 14.14-10
intershelf cable connection, 13.14-5
J14, 14.8-1
J17, 14.8-1
IN-38
Index
Issue 1, November 1997
IN-39
Index
Issue 1, November 1997
PROTOCOL, 25.6-6
Protocol
CPSS, 1.2-1
protocol
configuring for frame stream circuits,
27.13-16
X.25 version, 27.14-14
provisioning
backbone trunks, 27.8-6
user access
direct, 27.19-1
encapsulated, 27.19-3
subrate encapsulated, 27.19-6
PT_TO_PT, 30.3-6
PUB 43801, 20.12-3
Pushbutton S1, 4.2-5, 4.5-7, 4.6-5, 5.2-5
Pushbutton S1 TO E1-, 5.1-7
Pushbuttons
General Facilities cards, 4.8-15
PVC, 25.1-3
PVC identifiers, 16.4-1
PVCs
FRE card, 8.4-3
FRS card, 8.5-2
Q
Q.2110, 27.2-3
Q.922 link layer, 26.2-7
Quality statistics, 34.1-3
clear statistics, 34.1-10
DE1-2 card, 34.1-36
display, 34.1-9
DT1-2 card, 34.1-31
MPA card, 5.5-7
print-out options, 34.1-34, 34.1-41
reset error events, 34.1-10
TTC2M card, 5.6-7
type (E1 only), 34.1-9
X.21/V.35 PRI cards, 5.4-6
QUIT, 16.3-7
R
R2 digital signalling, 20.12-4, 31.15-3
R2D_E+M, 20.12-8
rack mounting brackets
48 cm (19 in) rack, 3.5-8
58 cm (23 in) rack, 3.5-8
TEP-1(E) or 11B rack, 3.5-8
racks
48 cm (19 in), 3.5-8
58 cm (23 in), 3.5-8
IN-40
dimensions, 3.5-9
TEP-1(E) or 11B, 3.5-8, 3.5-9
RAP+ID, 29.4-1
RAP+ID protection switching, 20.16-2
rate adaption
configuring, 22.4-3
DCCs, 22.4-1
DDS, 23.6-4, 25.9-7, 25.9-10
DDS Access, 23.6-5
DDS Core, 23.6-6
enhanced transparent, 23.6-2
HCM, 23.6-3, 25.9-7, 25.9-9
HCV voice compression for DSP cards and
IMC, 23.3-4
Line cards, 22.4-1
subrate FRS circuits, 25.9-6
subrate FRS streams, 25.9-8
transparent, 23.6-1
types
DSP cards, 23.6-1
X.50, 23.6-11
X.50 Basic, 23.6-15
X.50 Telco, 23.6-15
Rate Enforcement State parameter, 27.6-21
RATE_AD/56, 30.4-4
RATE_ADAPT, 22.3-17, 22.3-21, 22.3-24,
23.6-49, 23.7-5, 23.11-3, 25.9-9, 25.9-10
RBS, 20.12-4, 20.12-5, 20.16-4, 31.15-3
RDL, 20.20-12, 22.3-7
READ/WRITE, 17.5-2
READ_ONLY, 17.5-2
Ready LED, 33.1-8
Rec. Att. LED, 33.1-8
Receive Attention pushbutton, 4.8-15
Recommendation X.2
compliance to, 27.3-1
Recommendation X.35
compliance to, 27.3-5
Reconcile in Progress, 18.1-14
RECOVERY, 17.2-24
Red Alarm LED, 33.1-8
RED_OFF/ON, 20.9-10
Redirection Address parameter, 27.15-14
redirection addresses
hunt group, 27.18-2
NUA, 27.15-14
redundancy, 2.1-12
access, 5.1-10
DS-3 card, 5.1-9
DS-3 II card, 5.1-9
E3 card, 5.2-6
hot standby, 5.2-6
interface, 5.1-10
partitioned standby, 5.2-6
primary rate interface, 18.3-1
single-shelf, 18.1-5
redundancy jumpers
23-Inch locally controlled shelf, 13.11-1
23-Inch peripheral shelf, 13.11-1
23-Inch switching shelf, 13.11-1
Class A locally controlled shelf, 13.11-1
Class A peripheral shelf, 13.11-1
Class A switching shelf, 13.11-1
Class B locally controlled shelf, 13.11-1
Class B peripheral shelf, 13.11-1
Class B switching shelf, 13.11-1
REDUNDANT, 18.1-5, 22.3-25, 22.3-28
Redundant Routing parameter, 27.6-18
refreshing the display, 16.3-4
relative address, 26.3-1
Reliable Transfer Protocol
description, 27.2-3
Reliable Transfer Protocol (RTP)
statistics, 34.5-7
status information, 33.11-12
REM_EXT, 20.12-8, 21.3-7
remote address table
creating and changing, 26.5-4
error and caution messages, 26.5-3
parameters, 26.5-2
remote alarm indication, 35.5-1
REMOTE_NUM, 30.4-2, 30.4-5
REPORT_ON/OFF, 30.3-5
reset cause codes, 37.1-2
Reset Timer (T32) parameter, 28.2-13
Reset Timer parameter, 27.14-18
Response Delay Timer (T2) parameter, 28.2-4
Response Delay Timer parameter, 27.14-5
RET_SERV, 18.3-9
Retransmission Count (N2) parameter, 28.2-3
Retransmission Count parameter, 27.14-4
RETRIES, 30.4-5
Return softkey, 16.3-8
REV_POL, 21.3-9
REV_POL signalling mode, 21.3-8
Reverse Charge Acceptance parameter,
27.15-10, 28.3-4
RFC 1490 encapsulation, 25.10-3, 27.13-3
RI, 20.20-12, 22.3-7
ring terminal, 13.1-2
ringing generator
external
chassis ground point, 13.10-11
ringing generator alarm reporting, 35.6-3
Index
Issue 1, November 1997
ringing generators
connections, 3.8-3, 3.8-8
external, 3.8-6, 40.7-1
external configurations, 3.8-7
internal, 3.8-2, 40.6-1
distribution box connections, 13.20-2,
13.20-3, 13.21-2
J2, 3.8-3, 3.8-8
J24F, 3.8-3, 3.8-5
J24R, 3.8-8, 3.8-10
J30, 3.8-8, 3.8-11
Newbridge, 3.8-1
non-Newbridge, 3.8-1
redundancy, 3.8-7
ringing voltage, 3.8-1
specifications, 3.8-1
variants, 3.8-3, 3.8-7
Ringing LED, 33.1-8
RL, 20.20-12, 22.3-7
RL_ENABLE/DISABLE, 22.3-5
RLS_CTRL, 18.1-14
robbed bit signalling, 20.12-4, 31.15-3
route failure handling, 26.5-4
route list name, 26.5-2
route trace
characteristics, 33.6-4
error messages, 33.6-6
indication types, 33.6-5
LLCP, 33.6-6
setting LLCP, 33.6-8
starting, 33.6-8
router version, 17.6-4, 17.6-17
routing
definition, 26.1-4
in large network, 26.1-4
overview, 26.5-1
remote address table, 26.5-2
selection, 26.5-4
routing domains, 27.6-1
routing system characteristics, 27.6-12
RPT_TYPE, 25.4-9, 25.6-10
RS-232 DCC, 22.1-1
RS-232 Direct Connect card, 22.1-1
backplane or bulkhead
, 14.10-67
pinout
backplane or bulkhead, 14.10-65
faceplate, 14.10-66, 14.10-68
RS-232_DCC, 22.2-1
RS-422 DCC, 22.1-1
clocking, 10.5-7, 22.3-10
DCE external (Slip Buffer present), 10.5-8
IN-41
Index
Issue 1, November 1997
S
S/T interface K1-, 29.1-1
S1 pushbutton, 4.8-15
SA4 BER, 20.18-6
SAI LED, 33.1-8
SAM, 5.3-9, 20.1-2, 20.2-4, 20.3-2
SATELLITE, 17.6-19
satellite delay, 20.20-16
SC, 19.3-4
SC_ON/OFF, 22.3-31
SCT, 25.4-7
SE3 card, 20.1-1
alarm LED numeric value, 39.2-6
default configuration database, 39.2-12
LEDs, 14.2-1
loopbacks, 36.7-26
power-up LED activity, 14.2-1, 33.1-14
replace an inactive, 40.9-1
IN-42
SEAL_CUR, 22.3-32
sealing current, 22.3-32
secondary channel, 22.3-31
Secondary Data Collector Address parameter,
27.11-6
Secondary NUI Server Address parameter,
27.9-10
segmenting packets, 27.2-10
SEIZED, 20.10-4, 21.8-1
SELECT, 17.2-23
sequence numbering, 27.14-8
serial bus, 3.6-7, 3.6-13
serial ports, 17.3-1
backplane, 3.6-21
baud rate, 17.3-8
card faceplate serial ports, 16.2-7
configuring, 17.3-4
Control card, 17.3-2, 17.3-3
CPC, 8.1-4
CPCs, 17.3-4
CPSS cost, 17.3-10
DCP card, 8.2-3, 17.3-4
default configuration, 16.2-8
device type, 17.3-6
for 4600, 17.6-33
FRE card, 8.4-7, 17.3-4
FRS card, 8.5-7, 17.3-4
PE card, 17.3-4
peripheral shelf, 17.3-1
pinouts, 16.2-8
SP1, 16.2-6
SP2, 16.2-6
switching shelf, 17.3-1
Serial Telecom bus, 3.6-7, 3.6-13
Service Type parameter, 27.14-14, 28.2-8
SES, 20.17-1, 20.18-5
SESSN_TIME, 16.3-11
SETUP message, 30.4-2, 30.4-5
Severe Congestion Threshold
configuring for encapsulation circuits,
25.10-8, 27.13-9
configuring for frame stream circuits,
27.13-15
severely errorred seconds, 20.18-5
SHARE_COST, 17.6-17
SHARED, 30.2-1
shared cost, 17.6-5, 17.6-17
shelf
description, 1.3-1
FCC compliance, 1.3-4
identifiers, 16.4-1, 16.4-5
numbers, 16.4-6
Index
Issue 1, November 1997
IN-43
Index
Issue 1, November 1997
REV_POL, 21.3-8
SW_BIAS, 21.3-8
TO, 21.3-1
signalling profile
definition, 26.2-5
setting parameters, 26.2-6
signalling protocol, 26.2-5
signalling states
E&M Channel Unit, 6.6-5
LGE card, 6.3-5
LGE Channel Unit, 6.7-4
LGS card, 6.4-5
LGS Channel Unit, 6.8-5
signalling types
clear channels, 20.12-6
compatibility, 20.12-2
DS-3 card, 20.12-5
HCV signalling for DSP3, DSP4 and
DSP5H cards, 23.3-2
PLAR D3 signalling, 20.12-3
PRI cards, 20.12-1
R2 digital signalling, 20.12-4, 31.15-3
RBS, 20.12-4, 31.15-3
T1 card, 20.12-5
SIMPLEX, 18.1-5
Singing, 21.9-1
single and double bandwidth, 2.1-7
Single E3 card, 20.1-1
Single Optical Extension card, 5.7-1, 20.1-1,
20.1-2
Single Optical Extension card pinout, 14.10-1
Single shelf redundancy, 40.3-1
dual shelf to single shelf redundancy,
40.3-6
simplex to single shelf redundancy, 40.3-2
single shelf to dual shelf redundancy,
40.3-9
site planning
commissioning, 10.1-2
overview, 10.1-1
site requirements, 10.1-1
system requirements, 10.1-1
site requirements, 10.2-1, 12.1-1
ac power source fluctuations, 10.2-2
altitude, 10.2-1
anti-static strap, 10.2-2
cooling, 10.2-3
Electrostatic Discharge, 10.2-2
grounds, 10.2-2
location, 10.2-1
power, 10.2-2
IN-44
SOURCE, 25.8-3
source, 17.2-23
SPACE, 22.3-7, 22.3-14
SPECIAL, 22.3-12
Special mode, 10.5-11
DCCs
to set, 10.5-11
Specifications
Line cards, 7.4-5
specifications
4WDX Channel Unit, 6.5-5
4WTO Channel Unit, 7.6-4
4WTO Line card, 6.1-5
64 kb/s Codirectional card, 7.1-3
Balanced Transceiver card, 4.1-4
BRI S/T card, 7.2-6
Clock card, 4.2-6
Common Carrier card, 4.4-4
Control card, 4.6-7
Control card, 4.5-9
CPC, 8.1-4
DCCs, 7.3-6
DCP card, 8.2-4
DS-3 card, 5.1-11
DS-3 II card, 5.1-11
DS-O DP Channel Unit, 7.7-4
DSP cards and IMC, 8.3-5
E&M card, 6.2-5
E&M Channel Unit, 6.6-5
E1 card, 5.3-21
E3 card, 5.2-8
Expander card, 4.7-4
FRE card, 8.4-8
FRS card, 8.5-8
General Facilities cards, 4.8-16
LGE card, 6.3-6
LGE Channel Unit, 6.7-5
LGS card, 6.4-6
LGS Channel Unit, 6.8-5
MPA card, 5.5-7
MRD Channel Unit, 6.9-4
OCU-DP Channel Unit, 7.8-5
PE card, 8.6-5
physical
2B1Q Channel Unit, 7.5-6
Switching card, 4.9-4
Switching Interface card, 4.10-5
T1 card, 5.3-21
Test card, 4.11-8
Timing card, 4.3-5
transmission
2B1Q Channel Unit, 7.5-6
Index
Issue 1, November 1997
IN-45
Index
Issue 1, November 1997
types, 34.4-1
viewing and resetting, 34.4-4
statistics
ATB, 34.5-3
automatically clear, 34.1-26
BERT statistics, 36.5-13
FASTbus protocol, 34.3-7, 34.3-21
frame relay and X.25, 34.2-1
accumulation periods, 34.2-3
manually clear, 34.2-2
refresh automatically, 34.2-1
FRE card, 34.2-1
FRE cards, 34.3-11
switch
FRS card, 34.2-1
GFR, 34.5-4
HSA card quality statistics, 34.1-10
internodal traffic, 34.5-7
link layer
detailed, 34.5-16
summary, 34.5-15
network layer
invalid packets, 34.5-23
NUI server agent, 34.5-9
PE card, 34.2-1
protocol, 34.3-7
quality statistics, 34.1-3
remote switch, 34.5-7
RTP, 34.5-7
switch level, 34.5-1
synchronization statistics, 34.1-25
usage statistics, 34.1-1
XFR, 34.5-25
statistics on signalling channel, 34.4-1
STATS AUTO_CLEAR, 34.1-27
status information
direct circuits, 33.11-15
NUI server agent, 33.11-3
RTP, 33.11-12
switch, 33.11-1
trunk circuits, 33.11-9
virtual circuit, 33.11-26
XAC link layer, 33.11-20
XAC network layer, 33.11-22, 33.11-24
XACs, 33.11-16
Status LED, 33.1-8
status message rate, 25.6-8
STATUS_RATE, 25.6-8
stHCV, 23.11-3
forcing super tandem, 23.11-2
voice compression, 23.11-1
stHCV and fax operation
IN-46
understanding, 23.11-1
stHCV_EN/DIS, 23.11-2
STM-1 card
loopbacks, 36.7-51
stop bits, 22.3-13
STOP_BITS, 22.3-14
STREAM, 25.5-3, 25.6-3, 25.7-3
stream, 25.5-1, 25.6-1
stream identifiers, 16.4-1
stream protocol statistics, 34.3-7
STREAM_ON/OFF, 23.4-4
STRM_TIMER, 23.4-4
SUB_ADDR, 30.4-2, 30.4-5
subaddressing, 27.14-11
subframe position, 23.6-43
subrate access, 27.13-7
subrate CPSS channels, 17.6-27
subrate multiplexing, 25.9-1
subrate sets, 23.9-6
CPSS, 23.9-7
DDS, 23.9-7
HCM rate adaption, 23.9-6
transparent rate adaption, 23.9-6
X.50, 23.9-7
subrate switching, 23.9-1
subscription options, 27.15-7
summary display, 16.5-2
SUPER_RATE, 22.2-1
super-rate access, 27.13-1
Super-rate Adapter Module, 5.3-9, 20.3-2
super-rate circuits, 20.15-1
24 DS-0 fault recovery, 20.16-3
circuit order, 20.3-2
contiguous, 20.3-2
contiugous, 20.15-2, 31.10-1
DCCs, 22.3-17
clocking, 22.3-21
interface speed, 22.3-18
transport bandwidth, 22.3-17
delay equalization, 20.15-4
equidistant, 20.15-3, 31.10-2
Line cards, 22.3-22
non-contiugous, 20.15-2, 31.10-2
protecting, 20.15-4, 31.10-3
timeslot order, 20.3-2
unidirectional broadcast circuits, 20.15-8
unidirectional tandem, 20.15-7
supervisory channel, 5.5-1, 20.19-4, 20.20-1,
20.20-9
Suppress Called Address parameter, 27.14-21
Suppress Calling Address parameter, 27.14-21
SVC call display, 33.6-1
SVC calls
clearing and viewing, 33.6-2
SVC routing
see routing, 26.5-1
SVCs
signalling channel management, 26.2-1
SW_BIAS, 21.3-9
SW_BIAS signalling mode, 21.3-8
SW56_ON/OFF, 22.3-31
switch prefix
address, 26.3-1
passing or stripping, 26.2-4
setting, 26.2-5
types, 26.3-2
Switched 56
access to frame relay, 25.11-1
switched 56 kb/s operation, 22.3-31
switched access
to frame relay, 25.11-1
switched virtual circuit, 27.14-8
Switching card
diagnostics, 4.9-4
disable, 39.1-12
enable, 39.1-12
faceplate, 4.9-2
functional description, 4.9-1
LEDs, 4.9-3
overview, 4.9-1
specifications, 4.9-4
Switching card, 19.3-4
switching interface cables
Class A
non redundant Switching to
Peripheral, 13.16-2
HSPS2
non redundant Switching to HSPS2,
13.17-12
redundant Switching to HSPS2,
13.17-12
Switching Interface card, 16.4-9
diagnostics, 4.10-5
faceplate, 4.10-3
faceplate connectors, 4.10-3
functional description, 4.10-1
LEDs, 4.10-4
modules, 4.10-3
overview, 4.10-1
specifications, 4.10-5
Switching shelf
23-Inch
chassis ground points, 13.10-11
dc fuse replacement, 40.14-1
Index
Issue 1, November 1997
IN-47
Index
Issue 1, November 1997
IN-48
T
T1 card, 20.1-1
CCM, 20.3-2
E1/T1 Conversion Modules, 20.3-1
faceplate monitor jacks, 36.1-1
fault classes, 20.9-8
line length, 20.7-1
pinout, 14.10-85, 14.10-86
HDSL module, 14.10-87, 14.10-88
RBS, 20.12-4, 31.15-3
SAM, 20.3-2
signalling types, 20.12-5
zero code suppression, 20.8-1
B8ZS, 20.8-2
JB7, 20.8-2
transparent, 20.8-1
T1 card
alarm declare/clear times, 5.3-21
bypass connector, 5.3-15
diagnostics, 5.3-19
faceplate, 5.3-14
faceplate connectors, 5.3-15
functional description, 5.3-4
interface redundancy, 5.3-19
LEDs, 5.3-16
loopbacks, 5.3-19
modules, 5.3-8
monitor jacks, 5.3-15
overview, 5.3-1
signalling leads, 5.3-19
specifications, 5.3-21
statistics, 5.3-21
T1 card (Wire-wrap adapter)
pinout, 14.10-86
HDSL module, 14.10-88
T1 HDSL, 20.1-2
T1 IHTU, 5.3-12
T1 LIM, 20.1-2
T1 signalling termination, 25.11-3
T1 timer, 27.14-4
T1 yellow alarm clearing method, 35.5-3
T1_PRI, 30.3-4
T1_SIG, 20.12-8, 21.3-7
T10/T20 timer, 27.14-18
T11/T21 timer, 27.14-18
T12/T22 timer, 27.14-18
T13/T23 timer, 27.14-18
T2 timer, 27.14-5
T24 timer, 27.14-19
T3 timer, 27.14-5, 29.3-5
T3_TIMER, 29.4-3
tables 6-1 and 6-2 in X.25, 27.2-11
TANDEM, 20.16-4
tandem super-rate configuration, 29.3-7
Tc, 25.1-4
TE, 29.3-4, 29.4-3
TEP-1 (E) alarm interface, 35.7-5
TEP-1(E) equivalence
General Facilities cards, 4.8-15
Test card
clock connectors, 4.11-6
digital test access, 4.11-3
DS-0 connector, 4.11-6
facilities and equipment connectors, 4.11-6
LEDs, 4.11-6
metallic test access, 4.11-4
Index
Issue 1, November 1997
IN-49
Index
Issue 1, November 1997
timers
congestion, 27.14-6
flow control, 27.14-20
link layer, 26.2-7, 27.14-4
link layer inactivity, 27.14-5
network layer, 27.14-10
network layer inactivity, 27.14-19
network layer protocol, 26.2-6
T1, 27.14-4
T10/T20, 27.14-18
T11/T21, 27.14-18
T12/T22, 27.14-18
T13/T23, 27.14-18
T2, 27.14-5
T24, 27.14-19
T3, 27.14-5
window, 27.14-19
timeslot 24 signalling, 20.5-1
timeslot zero, 20.19-4
timing and synchronization, 2.1-9, 10.6-1
automatic, 17.2-1
configuration procedure locations, 17.2-11
configuring, 17.2-11
methods, 17.2-5
sources, 17.2-1
stand-alone, 17.2-1
Timing card
functional description, 4.3-1
microcontroller, 4.3-2
overview, 4.3-1
specifications, 4.3-5
system timing unit, 4.3-2
Timing cards
faceplate LEDs, 4.3-3
timing connectors, 10.6-2, 10.6-12
J13, 10.6-7, 10.6-17
J14, 10.6-10, 10.6-21
J17, 10.6-8, 10.6-11, 10.6-19, 10.6-22
J20, 10.6-17
J21, 10.6-10, 10.6-21
timing inputs
1.544 Mb/s AMI, 10.6-8, 10.6-19
2.048 MHz, 10.6-7, 10.6-17
6DDS composite clock, 10.6-8
8 kHz, 10.6-7, 10.6-17
DDS composite clock, 10.6-19
timing outputs
1.544 MHz, 10.6-10, 10.6-21
2.048 MHz, 10.6-10, 10.6-21
8 kHz, 10.6-10, 10.6-21
DDS composite clock, 10.6-11, 10.6-22
timing receivers, 10.6-2, 10.6-12
IN-50
Index
Issue 1, November 1997
diagnostics, 5.6-6
E1/T1 conversion, 20.3-5
faceplate, 5.6-4
fault signalling, 20.10-1, 20.10-4
functional description, 5.6-3
LEDs, 5.6-5
loopbacks, 5.6-7, 36.7-26
overview, 5.6-1
pinout
backplane or bulkhead, 14.10-91
faceplate, 14.10-92
power-up LED activity, 33.1-16
protection switching, 5.6-6
quality statistics, 5.6-7
reset, 36.11-1
set and show signalling, 36.2-1
signalling, 5.6-2
signalling leads, 5.6-7
signalling type, 20.12-8
signalling types, 20.12-1
software downloading, 5.6-6
specifications, 5.6-8
trunk conditioning, 20.9-1, 20.9-7
trunk conditioning - custom, 20.11-1,
20.11-3
TU-12 mapper card
loopbacks, 36.7-51
TWO_WAY, 20.9-7
Two-way SVCs parameter, 27.14-17
Tx mute, 21.9-1
TX_MODE, 20.6-3
TX_TLP, 21.5-7
TXMUTE_ON/OFF, 21.9-2
TYPE, 19.3-4
TYPE I, 21.3-4
TYPE II, 21.3-4
TYPE III, 21.3-4
TYPE IV, 21.3-4
TYPE V, 21.3-4
U
UDP, 3.10-7, 5.5-4
UK, 21.2-4
UNDO_MAINT
on circuits, 38.1-12
UNIDIR/NO_UNIDIR, 22.2-4
Universal Distribution Panel, 3.10-7, 5.5-4
UNPROTECTD, 18.1-6
unstable card, 18.3-9
UNUSD_FSIG, 20.10-5, 20.11-3
IN-51
Index
Issue 1, November 1997
V
V.35, 22.3-1
V.35 DCC, 22.1-1
super-rate circuits, 22.3-17
V.35 Direct Connect card, 22.1-1
pinout
backplane or bulkhead, 14.10-93,
14.10-95
faceplate, 14.10-94, 14.10-96
V.35 PRI card, 20.1-1
card versions, 5.4-1
overview, 5.4-1
pinout
backplane or bulkhead, 14.10-97
faceplate, 14.10-98
specifications, 5.4-7
V.35_DCC, 22.2-1
V_FILTER, 21.3-4
variant ID, 16.5-5
VCB, 23.5-4
applications, 23.5-1
broadcast mode, 23.5-6
circuit, 23.5-4
companding law, 23.5-4
input gain, 23.5-4
listen-only mode, 23.5-5
output gain, 23.5-4
restrictions, 23.5-3
sidetone gain, 23.5-4
VCM, 5.3-9, 5.3-10, 20.1-2, 20.4-1
VCon
description, 27.2-4
IN-52
verification, 30.4-5
VERIFY, 30.4-5
Verify configuration database, 39.1-8
verifying power connections and LED
operation, 13.36-1
verifying the shipment, 12.2-1
version of X.25, 27.14-14
Version parameter, 28.2-9
VERSION_1, 17.6-17, 23.6-47, 23.7-5
VERSION_2, 17.6-17, 23.6-47, 23.7-5
VIA_CPSS, 20.14-6
VIA_TS24, 20.14-6
View
available and active diagnostics, 33.2-14
virtual call
description, 27.14-8
routing process, 27.7-21
setup process, 27.7-12
virtual circuit
description, 27.14-8
virtual circuit accounting, 27.10-1
VOICE, 20.13-1, 21.2-3
voice and data connections
overview, 10.4-1
voice and data interface connections, 10.4-1
Voice card loopbacks, 36.7-48
voice compression
configuring, 20.4-6
Voice Compression Module, 5.3-9, 5.3-10,
20.4-1
voice conference bridge, 23.5-1
voice interface card
configuration, 21.2-3
Voice interface cards
configuring loop balance, 21.10-1
equalization, 21.11-1
loop balance, 21.10-1
voice interface cards, 3.14-3
companding law, 21.2-2
configuring, 21.1-2
fault signalling, 20.10-1, 21.8-1
line balance, 21.7-1
line impedance, 21.6-1
signalling types, 21.3-1
slot configuration, 21.2-1
TLPs, 21.5-1
voice interface channel unit
configuration, 21.2-3
voice interface channel units, 21.1-1
fault signalling, 21.8-1
line balance, 21.7-2
line impedance, 21.6-3
W
wander, 20.19-8, 20.20-16
WII jumper, 18.1-5
wildcard characters
in the address translation table, 27.14-35
in the Global Address Table, 27.7-3
Window Timer parameter, 27.14-19, 27.14-20,
28.2-14
wire-wrap adapters
installation, 13.45-1
WRAP_A, 25.4-2
WRAP_B, 25.4-2
Wrong Card in Slot alarm, 21.5-7, 21.6-1
X
X.121, 26.3-2
X.121 address format, 27.15-1
X.2, 27.3-1
X.21, 22.3-1
X.21 DCC, 22.1-1
super-rate circuits, 22.3-17
X.21 DCC card
pinout
faceplate, 14.10-100, 14.10-102
X.21 Direct Connect card, 22.1-1
pinout
backplane or bulkhead, 14.10-99,
14.10-101
X.21 ESI PRI card
card versions, 5.4-1
overview, 5.4-1
specifications, 5.4-7
X.21 network termination unit, 20.6-5
X.21 NTU, 20.6-5
X.21 PRI card, 20.1-1
card versions, 5.4-1
framing, 20.6-7
overview, 5.4-1
pinout
backplane or bulkhead, 14.10-103
faceplate, 14.10-104
specifications, 5.4-7
Index
Issue 1, November 1997
IN-53
Index
Issue 1, November 1997
Basic, 23.6-15
Division 2, 23.6-14
Division 2 framing pattern, 23.6-12
Division 3, 23.6-14
Division 3 framing pattern, 23.6-13
interface speed, 23.6-42
RTS signal propagation, 22.3-16
subframe position, 23.6-43
subrate sets, 23.9-7
Telco, 23.6-15
X.50 Telco, 23.6-15
X.50_HCM, 22.4-5
X.50_TELCO, 22.2-2
X.75
interconnection possibilities, 28.1-1
IPVCs, 28.1-6
Overview, 28.1-1, 28.2-1, 28.3-1
overview, 28.1-1, 28.2-1, 28.3-1
Routing examples, 27.7-16
Statistics, 34.5-14
utilities, 28.1-2
Weights and priorities, 27.7-18
X.75 accounting, 28.1-8
X.75 LCN Selection parameter, 28.2-9
X.75 parameters overview, 28.2-1
X.76, 26.2-5
X50, 25.9-7, 25.9-10
X50_OR_HCM, 25.9-4
X50_TELCO, 23.6-47
IN-54
XACs
busy out, 38.1-7, 38.1-8
disable, 38.1-7
enable, 38.1-7
link layer status, 33.11-20
network layer status, 33.11-22
status information, 33.11-16
XCLK pin, 22.3-9
XON/XOFF, 17.3-9
Y
Y-cable connector, 18.3-2
Yel. Alarm LED, 33.1-8
YELLOW_OFF/ON, 20.9-10
Z
ZBS_ON/OFF, 22.3-36
ZCO, 21.6-2
zero byte substitution, 22.3-36
zero code suppression, 20.8-1
B8ZS, 20.8-2
JB7, 20.8-2
transparent, 20.8-1
ZERO_SUPPR, 20.8-2
ZONE_ID, 17.2-13
zones, 17.2-10
CORPORATE
HEADQUARTERS
Newbridge Networks
Corporation
600 March Road
P.O. Box 13600
Kanata, Ontario
Canada K2K 2E6
Tel. 613 591-3600
FAX 613 591-3680
http://www.newbridge.com
North and
South America
Asia Pacific
Newbridge Networks
Limited
Coldra Woods
Chepstow Road
Newport, Gwent
NP6 1JB U.K.
Tel. +44 (0) 1633 413600
FAX +44 (0) 1633 413680
Newbridge Networks
Corporation
600 March Road
P.O. Box 13600
Kanata, Ontario
Canada K2K 2E6
Tel. 613 591-6300
FAX 613 591-3201
Printed in Canada
95-2035-01-00-B