TA-200 Manual R7

TransAccess 200
Operations Manual
940-00008-001
Manual Revision 7.0
August 2003
TA-200 OP ii
8/29/03
NO WARRANTIES ARE EXTENDED BY THIS DOCUMENT. The technical information in this
document is proprietary to Turin Networks, Inc. and the recipient has a personal, non-exclusive and non-
transferable license to use this information solely with the use of Turin Networks products. The only
product warranties made by Turin Networks, if any, are set forth in the agreed terms and conditions for
purchase of an Turin Networks product. Turin Networks disclaims liability for any and all damages that
may result from publication or use of this document and/or its contents except for infringement of third
party copyright or misappropriation of third party trade secrets. No part of this document may be
reproduced in any manner without the prior written consent of Turin Networks.
U.S. GOVERNMENT RESTRICTED AND LIMITED RIGHTS
All software and related software documentation supplied by Turin Networks, Inc. to the United States
Government are provided with Restricted Rights. Use, duplication, or disclosure by the Government is
subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.227-7013 or subparagraph (c)(2) of the Commercial Computer Software
Restricted Rights at CFR 52.227-19, as applicable.
All documentation, other than software documentation that is provided with Restricted Rights, is provided
with Limited Rights. U.S. Government rights to use, duplicate, or disclose documentation, other than
software documentation, are governed by the restrictions defined in paragraph (a)(15) of the Rights in
Technical Data and Computer Software clause at DFARS 252.227-7013.
“DFARS” is the Department of Defense Supplement to the Federal Acquisition Regulation.
Manufacturer is Turin Networks, Inc., 1415 N. McDowell Blvd., Petaluma, CA 94954. To contact
customer service please call 1-866-TURINET (1-866-887-4638).
The information in this document is subject to change without notice. Revisions may be issued at any
time.
Turin Networks is a registered trademark of Turin Networks, Inc.

TransAccess is a registered trademark of Turin Networks, Inc.
WARNING NO OPERATOR SERVICEABLE PARTS ARE INSIDE

THIS EQUIPMENT. QUALIFIED SERVICE
PERSONNEL MUST PERFORM SERVICE.
TA-200 OP
8/29/03 iii
WARNING
This equipment is to be installed in a rack above a non-combustible surface or

above a solid metal plate or material rated 94-5V.
Any site construction, whether new construction or renovation work, that
allows traceable amounts of dust (from gypsum products, sheet rock, cement,
etc.) or airborne corrosives (chlorine-based solvents used in preparation of
ceilings, walls, and floors, such as muriatic acid) to enter or contact any Turin
Networks equipment can lead to catastrophic damage to electronic
components and circuitry.
Unless appropriate steps are taken to secure the construction area to prevent
these materials from coming in contact with the equipment, short-term failure
can occur and/or long-term reliability can be adversely affected.
References that can be used to define normal and acceptable environmental
conditions:
• Telcordia Technical Reference GR-63-CORE.
• International Electromechanical Commission (IEC) Standard Publication 721
Any customer installing Turin Networks equipment in unfinished premises or
contemplating construction or renovation (or storage of corrosives) at or near
an Turin Networks equipment installation should be aware of the potential
damage and impact to warranties that can be caused if such equipment is not
properly protected.
Steps that should be taken to protect Turin Networks equipment, if exposure to
airborne contamination is likely, include, but are not limited to:
1. Equipment cabinets should be covered with plastic sheeting from floor to
ceiling (or sufficient to isolate it from the source of contamination), allowing
sufficient surrounding airspace for proper equipment cooling.
2. Fresh external (clean) air should be piped in to the enclosed area via a
temporary duct.
3. Positive internal air pressure should be maintained inside the enclosure.
4. Corrosive-type materials used for etching should NOT BE USED OR
STORED IN THE VICINITY OF THE Turin Networks EQUIPMENT. This type of
activity should be completed in advance of installation or equipment already in
place must be de-installed and removed from the area until the process is
completed.
TA-200 OP
8/29/03 iv
TABLE OF CONTENTS
1 PRODUCT OVERVIEW ............................................................................................................................... 1-1
1.1 INTRODUCTION .............................................................................................................................................. 1-1
1.2 THEORY OF OPERATION ................................................................................................................................ 1-1
2 SYSTEM INSTALLATION .......................................................................................................................... 2-1
2.1 UNPACKING AND INITIAL INSPECTION ........................................................................................................... 2-1
2.2 EQUIPMENT INSTALLATION ........................................................................................................................... 2-2
2.3 INSTALLATION/REPLACEMENT OF SERVICE MODULES .................................................................................. 2-4
2.4 REDUNDANCY INTERFACE MODULE (RIM) INSTALLATION .......................................................................... 2-5
2.5 OFFICE WIRING ............................................................................................................................................. 2-6
2.5.1 Battery & Ground Connections ........................................................................................................... 2-6
2.5.2 Office Alarm & External Clock Connections....................................................................................... 2-7
2.5.3 Service Module Facility Connections .................................................................................................. 2-7
2.5.4 Remote Management Interface Connection ......................................................................................... 2-7
2.6 EQUIPPING MPU AND SERVICE MODULES .................................................................................................... 2-9
2.6.1 MPU Modules...................................................................................................................................... 2-9
2.6.2 Service Modules................................................................................................................................... 2-9
2.7 SHELF POWER-UP ....................................................................................................................................... 2-10
2.8 CONFIGURATION AND TESTING ................................................................................................................... 2-10
3 MODULE OPERATION ............................................................................................................................... 3-1
3.1 MICROPROCESSOR UNIT (MPU).................................................................................................................... 3-1
3.1.1 Theory of Operation............................................................................................................................. 3-1
3.1.2 MPU Auxiliary Board.......................................................................................................................... 3-2
3.1.3 Installation/Replacement ..................................................................................................................... 3-2
3.1.4 Diagnostics/Troubleshooting............................................................................................................... 3-2
3.2 T3/STS-1 TO T1 PROGRAMMABLE MULTIPLEXER MODULE (PM13/PM13+)............................................... 3-3
3.2.1.1 Status Indicator ............................................................................................................................................3-3
3.2.2 Installing DS3/STS-1 and T1 Cables ................................................................................................... 3-4
3.2.3 Replacing PM13 Modules.................................................................................................................... 3-4
3.2.4 Diagnostics/Troubleshooting............................................................................................................... 3-5
3.2.4.1 Step 1. Identify Alarm.................................................................................................................................3-7
3.2.4.2 Step 2. Analyze Data Flow..........................................................................................................................3-7
3.2.4.3 Step 3. Perform Loopbacks and Non-intrusive Tests ..................................................................................3-8
3.3 T3/STS-1/AU3 TO E1 PROGRAMMABLE MULTIPLEXER MODULE (PM13E)................................................. 3-9
3.3.1.1 Status Indicator ..........................................................................................................................................3-10
3.3.2 Installing DS3/STS-1 and T1 Cables ................................................................................................. 3-10
3.3.3 Replacing PM13E Modules ............................................................................................................... 3-10
3.3.4 Diagnostics/Troubleshooting............................................................................................................. 3-11
3.3.4.1 Step 1. Identify Alarm...............................................................................................................................3-14
3.3.4.2 Step 2. Analyze Data Flow........................................................................................................................3-14
3.3.4.3 Step 3. Perform Loopbacks and Non-intrusive Tests ................................................................................3-14
3.4 PM13/PM13E 1X1 INCOMING REDUNDANCY SERVICE MODULE (RIM) .................................................... 3-15
3.4.1 Theory of Operation........................................................................................................................... 3-16
3.4.2 Installation/Replacement ................................................................................................................... 3-17
3.5 OC-3/STM-1 TO STS-1/T3/AU3 SERVICE MODULE .................................................................................. 3-17
3.5.1 Theory of Operation........................................................................................................................... 3-17
3.5.1.1 Status Indicator ..........................................................................................................................................3-18
3.5.2 Installing DS3/STS-1 and OC-3 Optical Cables................................................................................ 3-18
3.5.3 Replacing OC-3/STM-1 to STS-1/T3/AU3 Service Module Modules................................................. 3-19
3.5.4 Diagnostics/Troubleshooting............................................................................................................. 3-20
3.5.4.1 Step 1. Identify Alarm...............................................................................................................................3-21
TA-200 OP
8/29/03 v
3.5.4.2 Step 2. Analyze Data Flow........................................................................................................................3-22
3.5.4.3 Step 3. Perform Loopbacks and Non-intrusive Tests ................................................................................3-22
3.6 OMX3 1X1 REDUNDANCY SERVICE MODULE (RIM) ................................................................................. 3-24
3.6.1 Theory of Operation – 1x1 RIM......................................................................................................... 3-24
3.6.2 Theory of Operation – Terminal RIM ................................................................................................ 3-24
3.6.3 RIM Installation/Replacement ........................................................................................................... 3-25
4 USER AND TELNET INTERFACES .......................................................................................................... 4-1
4.1 USER INTERFACE DEVICE HARDWARE REQUIREMENTS ................................................................................ 4-1
4.2 USER INTERFACE DEVICE CONNECTION TO THE TRANSACCESS 200............................................................. 4-1
4.3 USER INTERFACE DEVICE SETUP ................................................................................................................... 4-1
4.3.1 Establishing a Direct Connection........................................................................................................ 4-1
4.3.2 Establishing a Remote Connection via a Modem ................................................................................ 4-2
4.3.3 Connect the TransAccess 200 to the Network...................................................................................... 4-4
4.4 BACKUP AND RESTORE TRANSACCESS 200 DATABASE ................................................................................ 4-4
4.4.1 Database Management via Telnet ....................................................................................................... 4-4
4.4.2 Database Management via Web Browser ............................................................................................ 4-5
4.4.3 Database Management via Front Panel RS232 Port (VT100) ............................................................ 4-5
4.5 TRANSACCESS 200 INITIALIZATION .............................................................................................................. 4-6
4.6 TOP-LEVEL MENU SCREEN ............................................................................................................................ 4-6
4.6.1 System .................................................................................................................................................. 4-8
4.6.1.1 Alarm Summary...........................................................................................................................................4-8
4.6.1.2 Passwords and System Security ...................................................................................................................4-9
4.6.1.3 Download...................................................................................................................................................4-12
4.6.1.4 Backup/Restore Configuration Database ...................................................................................................4-15
4.6.1.5 Logout........................................................................................................................................................4-15
4.6.1.6 Discover .....................................................................................................................................................4-15
4.6.1.7 Restore .......................................................................................................................................................4-15
4.6.1.8 System Info ................................................................................................................................................4-15
4.6.1.9 Module Info ...............................................................................................................................................4-16
4.6.2 Service Module – PM13, PM13+, and M13-T3................................................................................. 4-17
4.6.2.1 Alarm Summary.........................................................................................................................................4-17
4.6.2.2 VT1.5 Alarm Summary..............................................................................................................................4-19
4.6.2.3 T1 Alarm Details........................................................................................................................................4-20
4.6.2.4 PM13 T3 Alarm Details .............................................................................................................................4-21
4.6.2.5 PM13 Performance Summary ....................................................................................................................4-22
4.6.2.6 PM13 Performance History........................................................................................................................4-24
4.6.2.7 PM13 Configuration – T3/STS-1 Line.......................................................................................................4-28
4.6.2.8 Configuration – T1 Drop LBO...................................................................................................................4-32
4.6.2.9 Configuration – T1 Line Code ...................................................................................................................4-33
4.6.2.10 T1 In-band Loopback Configuration..........................................................................................................4-34
4.6.2.11 Circuit Tags................................................................................................................................................4-35
4.6.2.12 PM13 Diagnostics......................................................................................................................................4-36
4.6.3 Service Module Diagnostics .............................................................................................................. 4-41
4.6.3.1 Protection Switch .......................................................................................................................................4-42
4.6.3.2 Reset/Reprogram........................................................................................................................................4-43
4.6.3.3 Restore .......................................................................................................................................................4-43
4.6.4 Service Module – PM13E .................................................................................................................. 4-44
4.6.4.1 Alarm Summary.........................................................................................................................................4-44
4.6.4.2 VT/VC Alarm Summary ............................................................................................................................4-46
4.6.4.3 E1 Alarm Summary ...................................................................................................................................4-47
4.6.4.4 T3 Alarm Details........................................................................................................................................4-48
4.6.4.5 PM13E Performance Summary..................................................................................................................4-49
4.6.4.6 PM13E Performance History .....................................................................................................................4-51
4.6.4.7 Configuration – T3/STS-1/AU3 Line ........................................................................................................4-54
4.6.4.8 E1 Drop Configuration...............................................................................................................................4-58
4.6.4.9 Circuit Tags................................................................................................................................................4-58
4.6.4.10 PM13E Diagnostics ...................................................................................................................................4-59
4.6.5 Service Module – OMX3.................................................................................................................... 4-65
4.6.5.1 Alarm Summary.........................................................................................................................................4-65
TA-200 OP
8/29/03 vi
4.6.5.2 OC-3 Path Alarm Summary .......................................................................................................................4-67
4.6.5.3 OMX3 Drop Port Alarm Summary............................................................................................................4-68
4.6.5.4 Performance Summary...............................................................................................................................4-69
4.6.5.5 OMX3 Performance History ......................................................................................................................4-71
4.6.5.6 Configuration .............................................................................................................................................4-72
4.6.5.7 OMX3 Loopback .......................................................................................................................................4-74
4.6.6 MPU................................................................................................................................................... 4-76
4.6.6.1 Configuration .............................................................................................................................................4-76
4.6.6.2 Setting the Ethernet Port IP Address..........................................................................................................4-77
4.6.6.3 Configuration for TL1................................................................................................................................4-77
4.6.6.4 Alarm Summary.........................................................................................................................................4-77
4.6.6.5 Protection Switch .......................................................................................................................................4-78
4.6.6.6 Reset ..........................................................................................................................................................4-78
4.6.6.7 Disconnect a Telnet/TL1 Session...............................................................................................................4-78
5 REMOTE NETWORK MANAGEMENT CONFIGURATION ................................................................ 5-1
5.1 CONNECT THE TRANSACCESS 200 TO THE NETWORK ................................................................................... 5-1
5.2 CONFIGURING THE TRANSACCESS 200 FOR SNMP, TL1, TELNET, OR WEB BROWSER OPERATION ............ 5-1
5.3 OTHER REMOTE MANAGEMENT OPTIONS ..................................................................................................... 5-4
6 REMOTE MANAGEMENT USING TELNET ........................................................................................... 6-1
6.1.1 Telnet Configuration Menu.................................................................................................................. 6-1
6.1.2 Disconnect a Telnet Session................................................................................................................. 6-2
7 SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP) ............................................................... 7-1
7.1 SNMP MANAGEMENT STATION.................................................................................................................... 7-1
7.2 SAVING IP/SNMP CHANGES ......................................................................................................................... 7-3
7.3 CHARTS FOR UI AND SNMP TERMS COMPARISON ........................................................................................ 7-3
7.3.1 System / oEx2SysObjects ..................................................................................................................... 7-3
7.3.2 MPU / oEx2MPUObjects..................................................................................................................... 7-4
7.3.3 Service Module / oEx2CommonObjects............................................................................................... 7-5
7.3.4 Service Module / oEx2Pm13Objects / Configuration .......................................................................... 7-5
7.3.5 Service Module / oEx2Pm13Objects / Diagnostics............................................................................ 7-10
7.3.6 Service Modules / OC3 / oEx2Omx3Objects ..................................................................................... 7-11
7.3.7 Service Module / PM13E/ oEx2Pm13EObjects ................................................................................. 7-14
7.3.8 Service Module / oEx2Pm13EObjects / Diagnostics ......................................................................... 7-19
8 TRANSACTION LANGUAGE 1 (TL1) ....................................................................................................... 8-1
8.1 TL1 MANAGEMENT STATION........................................................................................................................ 8-1
8.2 CONNECT THE TRANSACCESS 200 TO THE NETWORK ................................................................................... 8-1
8.3 CONFIGURING THE TRANSACCESS 200 FOR TL1 OPERATION ...................................................................... 8-1
8.3.1 Telnet Configuration Menu.................................................................................................................. 8-3
8.3.2 Disconnect a Telnet Session................................................................................................................. 8-3
8.4 TL1 COMMAND SET ...................................................................................................................................... 8-4
8.4.1 TL1 FORMAT ...................................................................................................................................... 8-4
8.4.2 General Syntax..................................................................................................................................... 8-4
8.4.2.1 Command Syntax.........................................................................................................................................8-4
8.4.2.2 Response Syntax ..........................................................................................................................................8-5
8.4.2.3 Multiple Output Responses ..........................................................................................................................8-5
8.4.3 Error Responses................................................................................................................................... 8-5
8.4.3.1 Valid Error Code Values..............................................................................................................................8-5
8.4.4 Parameter Types .................................................................................................................................. 8-6
8.4.4.1 Correlation Tag ............................................................................................................................................8-6
8.4.4.2 Automatic Message Tag...............................................................................................................................8-6
8.4.4.3 Target Identifier and Source Identifier .........................................................................................................8-6
8.4.4.4 2nd Modifier Types .......................................................................................................................................8-6
8.4.4.5 Access Identifier ..........................................................................................................................................8-6
8.4.4.6 Completion Codes........................................................................................................................................8-7
TA-200 OP
8/29/03 vii
8.4.5 Security Commands ............................................................................................................................. 8-8
8.4.5.1 Activate User ...............................................................................................................................................8-8
8.4.5.2 Cancel User..................................................................................................................................................8-8
8.4.5.3 Delete-User-Security....................................................................................................................................8-9
8.4.5.4 Enter-User-Security .....................................................................................................................................8-9
8.4.5.5 Edit-User-Security .....................................................................................................................................8-10
8.4.5.6 Edit Password ............................................................................................................................................8-12
8.4.5.7 Retrieve Password Information..................................................................................................................8-12
8.4.6 Configuration Commands.................................................................................................................. 8-13
8.4.6.1 Allow Automatic Alarms ...........................................................................................................................8-13
8.4.6.2 Inhibit Alarms ............................................................................................................................................8-13
8.4.6.3 Edit System Identification..........................................................................................................................8-14
8.4.6.4 Edit T1/E1 LBO and Linecode (enable/disable) ........................................................................................8-15
8.4.6.5 Edit T1/E1 Circuit Tags .............................................................................................................................8-16
8.4.6.6 Edit Telnet/UI Session ...............................................................................................................................8-16
8.4.7 Retrieve Commands ........................................................................................................................... 8-17
8.4.7.1 Retrieve Header .........................................................................................................................................8-17
8.4.7.2 Manual Request for Alarms .......................................................................................................................8-17
8.4.7.3 Retrieve Performance Monitoring Data .....................................................................................................8-19
8.4.8 Automatic Alarm Reporting ............................................................................................................... 8-21
8.4.8.1 Normal Response .......................................................................................................................................8-21
8.4.8.2 T1 LOS Input Alarm ..................................................................................................................................8-21
8.4.8.3 T1 AIS Input Alarm ...................................................................................................................................8-22
8.4.8.4 E1 LOS Input Alarm ..................................................................................................................................8-22
8.4.8.5 E1 AIS Input Alarm ...................................................................................................................................8-22
8.4.8.6 PM13(E) T2/G.747 LOF Alarm.................................................................................................................8-22
8.4.8.7 PM13(E) T2/G.747 X-bit (RAI) Alarm .....................................................................................................8-22
8.4.8.8 PM13(E) T3 LOS Input Alarm ..................................................................................................................8-22
8.4.8.9 PM13(E) T3 LOF Input Alarm ..................................................................................................................8-22
8.4.8.10 PM13(E) T3 AIS Input Alarm ...................................................................................................................8-23
8.4.8.11 PM13(E) T3 X-bit (RAI) Input Alarm .......................................................................................................8-23
8.4.8.12 PM13(E) STS-1/AU3 LOS Input Alarm....................................................................................................8-23
8.4.8.13 PM13(E) STS-1/AU3 LOF Input Alarm....................................................................................................8-23
8.4.8.14 PM13(E) STS-1/AU3 SLM Input Alarm ...................................................................................................8-23
8.4.8.15 PM13(E) STS-1/AU3 LOP Input Alarm....................................................................................................8-23
8.4.8.16 PM13(E) STS-1/AU3 AIS Input Alarm.....................................................................................................8-23
8.4.8.17 PM13(E) VT/VC LOP Input Alarm...........................................................................................................8-24
8.4.8.18 PM13(E) VT/VC AIS Input Alarm............................................................................................................8-24
8.4.8.19 PM13(E) VT/VC RDI Alarm.....................................................................................................................8-24
8.4.8.20 PM13(E) Board Alarm...............................................................................................................................8-24
8.4.8.21 PM13(E) No Output Alarm........................................................................................................................8-24
8.4.8.22 OMX3 Board Alarm ..................................................................................................................................8-24
8.4.8.23 OMX3 Clock Alarm ..................................................................................................................................8-24
8.4.8.24 OMX3 OC-3/STM-1 LOS Input Alarm.....................................................................................................8-25
8.4.8.25 OMX3 OC-3/STM-1 LOF Input Alarm.....................................................................................................8-25
8.4.8.26 OMX3 OC-3/STM-1 AIS Input Alarm ......................................................................................................8-25
8.4.8.27 OMX3 OC-3/STM-1 SLM Input Alarm ....................................................................................................8-25
8.4.8.28 OMX3 OC-3/STM-1 RDI Input Alarm......................................................................................................8-25
8.4.8.29 OMX3 STS-1/AU3 LOP Path Alarm.........................................................................................................8-25
8.4.8.30 OMX3 STS-1/AU3 AIS Path Alarm..........................................................................................................8-25
8.4.8.31 OMX3 STS-1/AU3 RDI Path Alarm .........................................................................................................8-26
8.4.8.32 OMX3 T3/STS-1/AU3 LOS Drop Alarm ..................................................................................................8-26
8.4.8.33 OMX3 T3/STS-1/AU3 LOF Drop Alarm ..................................................................................................8-26
8.4.8.34 OMX3 T3/STS-1/AU3 AIS Drop Alarm ...................................................................................................8-26
8.4.8.35 OMX3 T3/STS-1/AU3 RAI Drop Alarm...................................................................................................8-26
8.4.8.36 OMX3 T3/STS-1/AU3 No Output Drop Alarm.........................................................................................8-26
8.4.8.37 MPU Board Alarm.....................................................................................................................................8-26
8.4.8.38 Service Module Missing Alarm .................................................................................................................8-26
8.4.8.39 MPU Card Missing Alarm .........................................................................................................................8-27
9 WEB-BASED INTERFACE (WBI) .............................................................................................................. 9-1
TA-200 OP
8/29/03 viii
9.1 REQUIREMENTS ............................................................................................................................................. 9-1
9.2 WBI SECURITY ............................................................................................................................................. 9-1
9.3 WBI OPERATION........................................................................................................................................... 9-2
9.3.1 System Alarm Screen ........................................................................................................................... 9-2
9.3.2 Summary Information .......................................................................................................................... 9-3
9.3.3 Module Information Summary ............................................................................................................. 9-3
9.3.4 Diagnostics Menu ................................................................................................................................ 9-4
9.3.4.1 Protection Switch .........................................................................................................................................9-4
9.3.4.2 Reset ............................................................................................................................................................9-5
9.3.4.3 Reset MPU...................................................................................................................................................9-6
9.3.4.4 Restore .........................................................................................................................................................9-6
9.3.4.5 Discover .......................................................................................................................................................9-6
9.3.5 Backup Configuration File .................................................................................................................. 9-6
9.3.6 Restore Configuration or FPGA File................................................................................................... 9-7
9.3.7 Optical Mux Configuration Menu........................................................................................................ 9-7
9.3.8 Optical Mux Alarms........................................................................................................................... 9-10
9.3.9 OMX3 Performance Summary........................................................................................................... 9-13
9.3.10 OMX3 Performance History.......................................................................................................... 9-14
9.3.11 OMX3 Loopbacks .......................................................................................................................... 9-15
9.3.12 PM13/PM13E/M13-T3 Line Configuration .................................................................................. 9-16
9.3.13 PM13E Line Configuration Change Menu.................................................................................... 9-18
9.3.14 PM13/PM13E Drop Configuration Change Menu........................................................................ 9-20
9.3.15 Inband Loopback Configuration ................................................................................................... 9-22
9.3.16 PM13/PM13E Alarm Summary ..................................................................................................... 9-23
9.3.17 PM13/PM13E Alarm Details ........................................................................................................ 9-25
9.3.18 PM13/PM13E Performance Summary .......................................................................................... 9-26
9.3.19 PM13/PM13E Performance History ............................................................................................. 9-28
9.3.20 PM13/PM13E Loopbacks.............................................................................................................. 9-31
9.3.21 T1/E1 Test Generator and Receiver .............................................................................................. 9-31
9.3.22 PM13/PM13E Frame Monitor ...................................................................................................... 9-33
9.3.23 PM13/PM13E Front Panel Monitor.............................................................................................. 9-35
9.4 MPU MODULE CONFIGURATION................................................................................................................. 9-35
9.4.1 MPU Alarms ...................................................................................................................................... 9-35
10 GENERAL SYSTEM SPECIFICATIONS................................................................................................. 10-1
10.1 GENERAL SPECIFICATIONS ...................................................................................................................... 10-1
10.1.1 Physical Configuration.................................................................................................................. 10-1
10.2 ELECTRICAL REQUIREMENTS .................................................................................................................. 10-1
10.2.1 DC Power Requirements ............................................................................................................... 10-1
10.3 MPU MODULE SPECIFICATIONS ............................................................................................................. 10-2
10.3.1 General Specifications................................................................................................................... 10-2
10.4 PM13 MODULE SPECIFICATIONS ............................................................................................................ 10-2
10.4.2 T1 Interface Specifications ............................................................................................................ 10-2
10.4.4 STS-1 Interface Specification ........................................................................................................ 10-3
10.5 OMX3 MODULE SPECIFICATIONS........................................................................................................... 10-3
10.5.3 STS-1 Interface Specification ........................................................................................................ 10-3
10.5.4 OC-3 Interface Specification......................................................................................................... 10-3
10.6 PM13E MODULE SPECIFICATIONS.......................................................................................................... 10-4
10.6.3 STS-1/AU3 Interface Specification................................................................................................ 10-4
10.6.4 E1 Interface Specifications............................................................................................................ 10-4
TA-200 OP
8/29/03 ix
11 APPENDIX B – T3 FRAMING FORMATS .............................................................................................. 11-1
11.1 M13 FRAMING FORMAT FOR T2 FRAMING.................................................................................. 11-1
11.2 M13 FORMAT DS2 OVERHEAD BITS ...................................................................................................... 11-3
11.3 M13 FRAMING FORMAT FOR T3 FRAMING.................................................................................. 11-3
11.3.1 M13 Format T3 Overhead Bits...................................................................................................... 11-4
11.4 M13 FORMAT BIT STUFFING .................................................................................................................. 11-6
11.5 C-BIT PARITY FORMAT .................................................................................................................... 11-7
11.5.1 X-Bits............................................................................................................................................. 11-9
11.5.2 C-Bits........................................................................................................................................... 11-10
11.5.2.1 Application Identification Channel (AIC)................................................................................................11-10
11.5.2.2 Reserved Network Application Bit ..........................................................................................................11-10
11.5.2.3 Data Links (Communication Data Links) ................................................................................................11-10
11.5.2.4 T3 Parity Bits ...........................................................................................................................................11-10
11.5.2.5 Far-End Block Error Function (FEBE) ....................................................................................................11-10
11.5.3 C-Bit Parity Format Bit Stuffing ................................................................................................. 11-11
12 APPENDIX C – SONET FRAMING .......................................................................................................... 12-1
12.1 SONET NETWORK HIERARCHY ............................................................................................................. 12-1
12.2 SONET STS-1 FRAME STRUCTURE ....................................................................................................... 12-2
12.2.1 Transport Overhead ...................................................................................................................... 12-2
12.2.2 Synchronous Payload Envelope .................................................................................................... 12-4
12.2.2.1 Path Overhead............................................................................................................................................12-4
12.2.2.2 SPE Payload Capacity................................................................................................................................12-4
12.2.2.3 Tributary Signals........................................................................................................................................12-5
12.3 SONET STS-3 FRAME STRUCTURE ....................................................................................................... 12-5
TA-200 OP
8/29/03 x
1 PRODUCT OVERVIEW
1.1 Introduction
Turin Networks’ TransAccess 200 (or TA-200) was originally designed to address the ever-increasing
demand for cost-effective multiplexing from T1 to either T3 or STS-1. Traditional T1 to T3 multiplexers
have been available for many years. However, next generation equipment being developed today is
geared for the SONET infrastructure being deployed by most of the carriers. Many of these SONET
systems are deployed with STS-1 interfaces rather than T3, resulting in the need for STS-1 compatible
multiplexers.
The TA-200 was the first system that provides a programmable multiplexer from T1 to either T3 or STS-
1 on the same module. The TA-200 was also the first product that supported up to seven fully redundant
multiplexers in a single 2 RU shelf.
Release 4.0 added three new features. First, it enhances the choices of managing the TransAccess 200
with the addition of a web browser interface. Second, a modification of the OMX3 module has been
made so that we could offer a cost reduced version that only support T3 drops. This new module is the
OMXT3. Finally, the TransAccess 200 system can be powered from +24 VDC in addition to the standard
–48 VDC.
Release 5.0 added additional software features such as T1 Loop-up/Loop-down functionality to the PM13
family of modules, expanded alarm logs, remote management via DCC, protection switching for T1/E1
failures, and software download via TFTP. The PM13 modules will generate and react to Loop-up/Loop-
down codes by way of the 28 T1 drop ports. In addition, the TransAccess 200 menu structure has been
altered to better organize common functions across all the different types of modules.
Release 6.1 adds another choice for managing the TransAccess 200 using TL1 commands and adds the
ability to backup and restore the configuration data of the TransAccess 200. Release 7.0 modifies the
OC-3/STM-1 DCC protocol to support IP/PPP.
1.2 Theory of Operation
The TransAccess 200 shelf accommodates 16 card slots in a 23” shelf or 12 card slots in a 19” shelf and
is 3.5” tall.
TM
TM
EXchange Mux
EXchange Mux
STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT
ACO ACO
LAMP LAMP
TEST TEST
T1 T1 T1 T1 T1 T1 T1 T1 T1 T1
MON MON MON MON MON MON MON MON MON MON
Programmable Programmable Programmable P rogrammable Programmable Programmable P rogrammable Programmable

USI USI M13 M13 M13 M13 M13 M13 M13 M13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
MPU
MPU
Figure 1-1: TransAccess 200 23” Shelf
Slot 1 is reserved for the MPU (MicroProcessor Unit) and slot 2 for a second MPU for redundancy. Slots
3 – 16 are universal card slots for TransAccess 200 service modules. Each pair of service module card
slots provide 1x1 redundancy. Any combination of PM13, PM13E, or OMX3 modules can be configured
in the TransAccess 200 shelf.
TA-200 OP
8/29/03 1-1
The 19” shelf is shown in Figure 1-2.
EXchange MuxTM
EXchange MuxTM
STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT STAT
ACO ACO
LAMP LAMP
TEST TEST
T1 T1 T1 T1 T1 T1
MON MON MON MON MON MON
Programmable Programmable Programmable Programmable Programmable Programmable

USI USI M13 M13 M13 M13 M13 M13
PM13
PM13
PM13
PM13
PM13
PM13
MPU
MPU
Figure 1-2: TransAccess 200 19” Shelf
The PM13 (Programmable M13 multiplexer) module was the first TransAccess 200 service module
released. As depicted in Figure 1-3, the T1/VT1.5 mapper exchanges 28 T1s for 28 VT1.5s when the
PM13 module is configured for STS-1 operation. When the PM13 is programmed for T3 operation, the
T1’s are multiplexed into 7 T2’s and then into the T3 signal.
Programmable M13
T3/STS-1 T1/VT1.5
T3/STS-1 STS-1 T1 LIU T1 x 28
LIU Mapper Mapper
(28 circuits)
T3/T1
M13 Mux
Figure 1-3: PM13 Block Diagram
PM13 Redundancy Interface Mdules (RIM) screw to the rear of the shelf. An Input RIM and an Output
RIM are used for each pair of redundant slots. Each PM13 RIM provides a 68-pin SCCI-II connector for
interfacing the T1 signals and a BNC connector for the T3/STS-1 signals.
The OMX3 module can work in an add/drop configuration or in a terminal application. As Figure 1-4
shows, the OMX3 module has three drop ports that can be configured for T3, STS-1, or AU3. The three
electrical interfaces (TX and RX) exit out the back of the shelf via SMA connectors on the OMX3 IN and
OUT RIMs or can be interconnected to the PM13 modules with the “terminal” RIM option. The optical
connections are made from the front of the module via an ‘LC’ type connector.
Figure 1-5 shows a picture of the PM13E block diagram. The PM13E module accepts up to 21 E1
signals and can be programmed to multiplex any of 3 ways. Either T3 via G.747 multiplexing, STS-1 via
VT2 mapping, or AU3 via VC12/TUG-2 mapping.
TA-200 OP
8/29/03 1-2
Figure 1-4: OMX3 Block Diagram
Programmable M13
T3/STS-1/AU3 T3/AU3/
STS-1
VT/VC E1 x 21
STS-1 Mapper E1 LIU
LIU or AU3
Mapper (21 circuits)
T3/E1
Mux
Figure 1-5: PM13E Block Diagram
The PM13E modules use the same Redundancy Interface Module (RIM) as the PM13 modules. PM13
Redundancy Interface Modules (RIM) screw to the rear of the shelf. An Input RIM and an Output RIM
are used for each pair of redundant slots. Each PM13 RIM provides a 68-pin SCCI-II connector for
interfacing the E1 signals and a BNC connector for the T3, STS-1, or AU3 signals.
TA-200 OP
8/29/03 1-3
2 SYSTEM INSTALLATION
The TransAccess 200 System is intended only for installation in a RESTRICTED ACCESS LOCATION.
The installation of an TransAccess 200 system consists of the following steps:
• Unpacking the equipment and initial inspection.
• Mounting the equipment into the rack.
• Installing Redundancy Service Modules onto the shelf.
• Connecting office wiring to the shelf.
• Equipping MPU and Service Modules.
• Shelf Power-up.
• Configuration and Testing.
2.1 Unpacking and Initial Inspection

Remove the TransAccess 200 equipment from its shipping container(s). Normal ESD precautions should
be taken during the handling of MPU or Service Modules. After unpacking, verify all contents against
the packing slip and inspect the equipment for any damage that may have occurred during shipping.
IF PRODUCT IS RECEIVED DAMAGED:
Forward an immediate request to the delivering carrier to perform an inspection and prepare a damage
report. SAVE container and packing material until contents are verified.
Concurrently, report the nature and extent of damage to Customer Support so that action can be initiated
to repair or replace damaged items or instructions issued for returning items.
The responsibility of the manufacturer ends with delivery to the first carrier. ALL CLAIMS for loss,
damage, or non-delivery must be made against the delivering carrier WITHIN 10 DAYS OF RECEIPT of
shipment.
TO RETURN PRODUCT
Please obtain instructions from Customer Support before returning any item(s). Report the fault or
deficiency along with the model, type, and serial number of the item(s) to Customer Support. Upon
receipt of this information, Customer Support will provide service instructions or a Return Authorization
Number and other shipping information.
TA-200 OP
8/29/03 2-1
2.2 Equipment Installation
The 23-inch or 19-inch TransAccess 200 Shelf can be mounted in Standard EIA 23-inch or 19- inch
racks. The racks may be channel, duct, or unequal flange duct. Mounting ears are reversible, as shown in
Figure 2-1, allowing:
• Flush mounting to the front of the rack (Figure 2-1a)

• Offset mounting that projects the shelf 5 inches out from the front of the rack (Figure 2-1b)
Figure 2-1a: Shelf Mounting Ear Position for Flush Mounting
Figure 2-1b: Shelf Mounting Ear Position for Offset Mounting
Access to the rear of an TransAccess 200 shelf is normally required only during the initial installation and
when adding additional facility connections. Once installed, the TransAccess 200 System only requires
front access for normal maintenance and configuration operations.
1. Verify rack-mounting ears are installed in proper orientation. If required, change orientation:
A. Remove ears by removing four screws on the outside of the shelf.
TA-200 OP
8/29/03 2-2
B. Reverse ears and reinstall using four screws.
C. Repeat steps A and B for ear on opposite side of shelf.
2. Locate mounting position in rack according to configuration, Figure 2-2.
PRECAUTION: IF THE TRANSACCESS 200 SYSTEM IS BEING INSTALLED

ABOVE HEAT GENERATING EQUIPMENT, A HEAT BAFFLE
MAY BE REQUIRED BELOW THE TRANSACCESS 200 SHELF.
RACK
12-24
Screws
Figure 2-2: TransAccess 200 Rack Mounting
3. Route Battery A, Battery B, and Battery Return leads as shown in Figure 2-3. Battery
leads should attach to the TransAccess 200 terminal block (J33). See Table 2-1 for pin-out.
Figure 2-3: Battery A/B Connections
4. Connect earth ground lead to green mounting screw at rear of shelf.
5. Install Baffle above and/or below TransAccess 200 as necessary (Figure 2-4). Baffles are only
required when airflow to the TransAccess 200 is restricted.
NOTE: This equipment is designed to permit the connection of the earthed conductor of the DC supply
circuit to the earthing conductor (screw) on the TransAccess 200 equipment.
TA-200 OP
8/29/03 2-3
NOTE: To be compliant with CE Mark standards, a ferrite ring must be placed on each battery feed with
at least 10 wire turns around the ferrite with the BAT and BATRTN wires.
Figure 2-4. Baffle Installation
2.3 Installation/Replacement of Service Modules

PRECAUTION: MODULES USED IN THIS EQUIPMENT CONTAIN
ELECTRONIC COMPONENTS THAT MAY BE DAMAGED BY
STATIC ELECTRICITY. WHEN HANDLING MODULES, USE
A STATIC-DISSIPATIVE KIT AND TOUCH ONLY THE
FRONT PANEL OR SIDE EDGES. AVOID TOUCHING THE
REAR EDGE CONNECTORS, SOLDER CONNECTIONS,
COMPONENTS, OR COMPONENT PINS.
Modules operate in conjunction with an In and Out 1x1 Redundancy Service Module (RIM). In order for
the service modules to be recognized by the MPU, the RIM must be installed at the time the system is
powered up or the module is plugged in. If a service module is plugged in without a RIM in the rear slot,
it will not be configured by the MPU.
1. Locate the slot position for the module.

2. Install the service module as follows:
A. Carefully slide module into slot module guides.
B. Press firmly on the faceplate and handle to engage module into place.
C. Tighten screw to lock in module.
TA-200 OP
8/29/03 2-4
2.4 Redundancy Interface Module (RIM) Installation
Redundancy Interface Modules (RIMs) are used to provide 1x1 redundancy for the TransAccess 200
service modules. Two redundancy modules are provided; one to handle the outgoing T1/E1 and
T3/AU3/STS-1 signals and another to handle the incoming T1/E1 and T3/AU3/STS-1 signals. Both In
and Out RIMs are required whether or not redundant PM13, PM13E, or OMX3 modules are equipped. In
OMX3 terminal mode applications, those in which all the T3/AU3/STS-1 signals drop out at the node and
connect to PM13 or PM13E modules, an optional “terminal” RIM may be installed to eliminate the
external coax cabling to the PM13 or PM13E modules.
Install two or more RIMs from the rear of the TransAccess 200, Figure 2-6. Each RIM should be
plugged into a connector on the rear of the shelf such that it matches the card slots that are to be serviced
by the RIM. The Transmit RIM plugs in behind the 1st slot and the Receive RIM next to it. The slots are
keyed so that the Transmit and Receive RIMs cannot be interchanged. The optional “terminal” RIM is
installed across 8 slots, starting with an odd-numbered slot.
For example, a 1x1 Out RIM should be installed into connector J18 and an In RIM into J19 to equip
service module card slots 1 and 2 for 1x1 redundancy. Additional 1x1 RIMs could be installed into
connectors J20 through J31 to provide 1x1 redundancy for card slots 3 through 14.
If the TRML RIM is used, install it first as shown in Figure 2-5. The TRML can go across any 8 module
slots as long as the first slot is an odd-numbered slot. Once the TRML RIM is installed, plug in the RIM
cover (behind the OMX3 modules) and IN and OUT RIMs as shown in Figure 2-6.
Figure 2-5: Rear of TransAccess 200 23” Shelf (with OMX3 TRML RIM installed)
Figure 2-6: TransAccess 200 23” Shelf with OMX3 and PM13 RIMs Installed
TA-200 OP
8/29/03 2-5
2.5 Office Wiring
Wiring the TransAccess 200 consists of making the following connections:
• A & B Office Battery, Return, and Grounds
• Office Alarms
• Service Module Facilities
• External 64KHz Composite Clock (used only by OMX3 module)
• Remote Management Interface Port (SNMP, Telnet, Web Browser, and TL1)
• OMX3 DCC Port (future)
Figure 2-7 shows the location of all connections on the rear of the TransAccess 200 shelf.
Service Module Facilities External Timing Power/Ground

OC-3 DCC (future) (various)
Remote Management
Office Alarms Interface Port
Figure 2-7: TransAccess 200 External Connections
2.5.1 Battery & Ground Connections

J33 provides screw-type terminal block connections as follows. Pin 1 is at the top of connector J33.
Table 2-1: Battery Connections

Pin J33 Leads Function Max Wire Size
"A" Office Battery (-48 VDC or
1 BAT A Up to 12 Ga. (14 Ga. recommended)
+24 VDC)
Return Lead to the Office
2, 3 BAT RTN Up to 12 Ga. (14 Ga. recommended)
Battery
"B" Office Battery (-48 VDC or
4 BAT B Up to 12 Ga. (14 Ga. recommended)
+24 VDC)
5 GND Signal Ground * Up to 12 Ga. (14 Ga. recommended)
6 CHS GND Chassis Ground * Up to 12 Ga. (14 Ga. recommended)
Note: Ground connections should be made to the green grounding screw at the rear of the shelf.
TA-200 OP
8/29/03 2-6
"A" and "B" Office Battery signals are fed to all modules, providing redundant power connections. The
Signal Ground and Chassis Ground is common within the TransAccess 200 system. 14-gauge wire is
recommended for distances up to 100 feet to the battery source.
2.5.2 Office Alarm & External Clock Connections
J32 provides terminal block connections for connection to the external clock and office alarms. Up to 18
gauge wire should be used. Pin 1 is at the top of connector J32.
NOTE: The alarm relay connections can also be used to drive remote alarms using the Normally
Open (NO) or Normally Closed (NC) contacts.
NOTE: Older backplanes will require a small adapter card to be installed between the input
clock terminal block and the clock cable entering the shelf. Screw down the two pins of the clock
adapter module into the clock inputs of the terminal block and then connect the clock cable to the
adapter module.
Table 2-2: Office Alarm Contacts

J32 Leads Function Max Wire
SYNC & SYNC’ Positive and Negative clock inputs (64KHz Composite Clock for 18 Gauge
(Pin 1, 2) OMX3 modules)
COM1, NO1, NC1 Major Audible Alarm form C contacts (Common, Normally Open, 18 Gauge
(Pin 3, 4, 5) Normally Closed)
Major Visual Alarm form C contacts (Normally energized). Use
COM2, NO2, NC2 18 Gauge
Common and Normally Closed to provide a contact closure when the
(Pin 6, 7, 8)
MPU fails or is unplugged.
COM3, NO3, NC3 Minor Audible Alarm Form C contacts (Common, Normally Open, 18 Gauge
COM4, NO4, NC4 Minor Visual Alarm form C contacts (Common, Normally Open, 18 Gauge
In general, Major Alarms indicated that live traffic might be down. Minor alarms indicate that a failure
has occurred, but the redundant module is OK. Minor alarms are also generated while diagnostic
commands (loopbacks or T1/E1 test signals, for example) are active.
2.5.3 Service Module Facility Connections
T1/E1 and T3/STS-1/AU3 facility connections are made directly to the Redundancy Interface Modules.
T3/STS-1/AU3 signals are provided on BNC type connectors for the PM13 or PM13E modules and SMA
connectors for the OMX3 module. T1/E1 facility connections are made through the 68-pin connector on
the IN and OUT RIM modules. A Turin Networks cable adapter (consult Turin sales or customer service
for part number) can be used to convert the T1/E1 signals to a standard 64-pin CHAMP (Plug) connector
for connection to a T1/E1 jackpanel or cable assembly. Wirewrap cables are also available (consult Turin
sales or customer service for part number) for wiring to DSX panels. The T1/E1 cable pin-out is shown
in Table 2-4. OC-3/STM-1 optical connections are made from the front of the OMX3 service module via
‘LC’ type connectors.
2.5.4 Remote Management Interface Connection
J17 on the rear of the TransAccess 200 shelf provides an interface for various remote management
connections. The following types of Remote Management Interfaces are available:
• 10BaseT/RS422 – backplane jumpers J34/J35 in left-hand position

• Future feature – backplane jumpers J34/J35 in right-hand position
TA-200 OP
8/29/03 2-7
Table 2-3: UID Cable Pin-out
8-pin. 9-Pin DIN 9-Pin DIN
Modular UID Null Modem
1
2 5 5
3
4 3 2
5
6 2 3
7
8
The cable pin-outs for the Turin Networks UID cable/Null Modem cable, and T1/E1 cables,
SNMP/Telnet/Modem are shown in Table 2-2, Table 2-3, and Table 2-4 respectively.
Table 2-4: T1/E1 Cable Connector Assignments

T1/E1 68-Conn. 64-Conn Wire-Wrap 68-Conn. 64-Conn Wire Wrap
Circuit # TIP Pin # TIP Pin # Color RING Pin # RING Pin # Color
1 35 33 WHT/BLU 1 1 BLU/WHT
2 36 34 WHT/ORG 2 2 ORG/WHT
3 37 35 WHT/GRN 3 3 GRN/WHT
4 38 36 WHT/BRN 4 4 BRN/WHT
5 39 37 WHT/SLT 5 5 SLT/WHT
6 40 38 RED/BLU 6 6 BLU/RED
7 41 39 RED/ORG 7 7 ORG/RED
8 42 40 RED/GRN 8 8 GRN/RED
9 43 41 RED/BRN 9 9 BRN/RED
10 44 42 RED/SLT 10 10 SLT/RED
11 45 43 BLK/BLU 11 11 BLU/BLK
12 46 44 BLK/ORG 12 12 ORG/BLK
13 47 45 BLK/GRN 13 13 GRN/BLK
14 48 46 BLK/BRN 14 14 BRN/BLK
15 21 47 BLK/SLT 55 15 SLT/BLK
16 56 48 YEL/BLU 22 16 BLU/YEL
17 23 49 YEL/ORG 57 17 ORG/YEL
18 58 50 YEL/GRN 24 18 GRN/YEL
19 25 51 YEL/BRN 59 19 BRN/YEL
20 60 52 YEL/SLT 26 20 SLT/YEL
21 27 53 VIO/BLU 61 21 BLU/VIO
22* 62 54 VIO/ORG 28 22 ORG/VIO
23* 29 55 VIO/GRN 63 23 GRN/VIO
24* 64 56 VIO/BRN 30 24 BRN/VIO
25* 31 57 VIO/SLT 65 25 SLT/VIO
26* 66 58 WHT/BLU 32 26 BLU/WHT
27* 33 59 WHT/ORG 67 27 ORG/WHT
28* 68 60 WHT/GRN 34 28 GRN/WHT
* T1 circuits only
TA-200 OP
8/29/03 2-8
Table 2-5: SNMP/Telnet Cable Pin-out
8-pin. SNMP
Modular Cable
1 TX+
2 TX-
3 RX+
4
5
6 RX-
7
8
2.6 Equipping MPU and Service Modules

All modules plug into the front of the TransAccess 200 shelf. When facing the front of the TransAccess
200 shelf, module slots count from left to right as shown in Figure 2-8.
TM
TM
EXchange Mux
EXchange Mux
ACO ACO
LAMP LAMP
TEST TEST
T1 T1 T1 T1 T1 T1 T1 T1 T1 T1
Programm able Programm able P rogram mable Program mable Programmable Programm able Programmable Programm able
USI USI M 13 M 13 M13 M13 M 13 M 13 M 13 M 13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
MPU
MPU
A B 1 2 3 4 5 6 7 8 9 10 11 12 13 14
MPU Service Module

Slots Slots
Figure 2-8: 23” TransAccess 200 Front View
2.6.1 MPU Modules
The two far-left slots are reserved for MPU Modules. Equip an MPU Module in either slot (and the
second slot if redundancy is required) by simply sliding the module in until it fully engages with the back
connector. Engage the screw at the top of the module to fully lock it in place. If a second MPU is not
equipped, a blank faceplate should be equipped in the second slot. Both screws on the blank faceplate
should be fully engaged.
CAUTION: The MPU contains a Lithium battery inside one of its components (U3). Risk of explosion
can occur if an incorrect battery is replaced.. Replacement can only be performed at an Turin Networks
facility. Dispose of used batteries according to the manufacturer’s instructions.
2.6.2 Service Modules

Up to 14 Service Modules can be equipped in a 23" TransAccess 200 shelf and up to 10 Service Modules
in a 19” shelf. In a 23” system, the shelf is divided into seven sections thus providing seven 1x1
redundant-paired slots. Figure 2-9 shows the positioning of redundancy modules.
TA-200 OP
8/29/03 2-9
1x1 Redundancy Groups
TM
TM
EXchange Mux
EXchange Mux
ACO ACO
LAMP LAMP
TEST TEST
T1 T1 T1 T1 T1 T1 T1 T1 T1 T1
Programmable Programmable Programmable Programmable Programmable Programmable Programmable Programmable

USI USI M13 M13 M13 M13 M13 M13 M13 M13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
MPU
MPU
Service 1 2 3 4 5 6 7 8 9 10 11 12 13 14
Module
Slots
Figure 2-9: 23” TransAccess 200 Front View Showing Redundancy Module Positions
Equip the Service Modules by sliding them into their respective slot until they are fully engaged with the
back connector. Engage the screw at the top of each Service Module to fully lock it in place. A blank
faceplate must be equipped in each unused Service Module slot. Both screws on each blank faceplate
should be fully engaged.
2.7 Shelf Power-Up
Enable power to the TransAccess 200 shelf by engaging the switch(es) or fuse(s) at the Distribution Fuse
Panel that feed the "A" and/or "B" Battery connections.
After the power is connected, the MPU(s) will perform a self-test. After this, the online MPU will
download any necessary firmware to each Service Module and then configure each Service Module per
its default template (only for those card slots that had previously configured modules plugged in). The
MPU will declare any unconfigured Service Module slots as "not equipped" and will not alarm them.
Verify that the on-line MPU module displays a steady green Status LED after the download and
configuration routines are complete. If not, refer to the MPU troubleshooting details in Section 3. The
off-line MPU Module LED should be off.
Verify that all "on-line" Service Modules display a steady green LED, indicating that they are on line and
fully operational with good signals attached. If a Service Module LED is red or flashing red, first verify
that all incoming signals are properly connected and are known good signals. Refer to Service Module
troubleshooting details in Section 3.1.4, Section 3.2.4, and Section 3.3.4 for those modules that still do
not display a green LED. The LED on each off-line Protection Module should be off.
Press and quickly release the Lamp Test/ACO button on either MPU Module. The LED indicators on all
modules should illuminate. All STATUS LEDs should turn yellow during Lamp Test. The Lamp Test
will automatically terminate in 3 seconds.
2.8 Configuration and Testing
After its normal power-on self-test, the MPU Modules should be fully operational. Previously
programmed Service Modules are automatically configured with default settings at the initial power-up.
Modules added at a later time must be configured using the Discover command from the User Interface
Device per Chapter 4.
TA-200 OP
8/29/03 2-10
Change any parameters from their default settings by connecting a User Interface Device (PC running a
terminal emulation program or a dumb terminal) to either MPU Module per Chapter 4.
Verify proper operation of each Service Module by attaching an appropriate Bit Error Rate Test Set
(BERTS) signal to each input and measuring the corresponding output signal. As a minimum, the
following functions/alarms should be checked via the User Interface Device:
• Error-free performance under normal conditions

• Loss of the incoming signal
• Loss of Framing on the incoming signal
• Errored Second performance for degraded incoming signal
Utilizing the User Interface Device, invoke each available loopback command on each Service Module
and verify the appropriate response on the BERTS. Return all cables to their normal connections and
restore all diagnostic parameters to their normal conditions.
TA-200 OP
8/29/03 2-11
3 MODULE OPERATION
This section provides information on the operation, installation, replacement, and diagnostic features of
the TransAccess 200 service modules.
3.1 Microprocessor Unit (MPU)
The MPU Module manages communications, stores configuration data, and monitors performance of an
TransAccess 200 node.
3.1.1 Theory of Operation
The MPU module is responsible for configuration, diagnostics, and alarming (local and remote) of the
service modules. An 8-bit address bus and 8-bit data bus are distributed across the backplane to control
the I/O ports on all Service Modules. Alarm Interrupt lines from each card slot are delivered back to the
MPU module.
The MPU module provides an interface through the front panel for connection to a terminal used for
configuration, diagnostics, or alarm retrieval. Form C alarm contacts for Visual/Audible Major/Minor are
provided on the backplane for connection to a central office alarm panel. A tri-color LED is provided on
the faceplate to indicate the status of the MPU.
The main communications tasks performed by the MPU Module include:

• Downloading configuration, provisioning, and diagnostic commands from the terminal
interface (User Interface Device) to all modules.
• Collecting performance statistics and alarm status from service modules for transmission to
the terminal interface or remote management station.
The MPU Module stores configuration data, status, and alarm information for all modules.
The MPU Module monitors overall system status and performance. Additionally, the MPU Module
signals alarm conditions to the local office alarms (if connected) and reports those alarms through the
terminal interface or remote management station.
Physical features on the front panel of the MPU Module include the User System Interface (USI)
connector for connection to the User Interface Device; an LED indicator for displaying module status; a
switch for initiating LED indicator test (LAMPTEST), alarm cut-off (ACO) and an MPU reset function.
When depressing the faceplate push-button for less than 3 seconds will initiate the LAMPTEST feature
(momentarily turning all status LEDs yellow). Depressing the push-button for 3 to 10 seconds activates
the ACO. Depressing the push-button for more than 10 seconds resets the MPU.
The failure or removal of a non-redundant MPU Module suspends all of the above functions, but does not
affect traffic flow through the system. The Form C alarm contacts will return to their non-energized
position. The Major Visual alarm relay is energized in the non-alarmed state and will thus generate a
contact closure across the common and normally closed contacts when a non-redundant MPU module
fails or is unplugged and the relay becomes unenergized. If a redundant MPU module is equipped, it will
hold the Major Visual alarm relay energized if no Major alarm condition is present.
NOTE: Failure of both MPU modules does not affect the functionality of a programmed service
modules as long as power is maintained on the TransAccess 200 system. Only alarm
TA-200 OP
8/29/03 3-1
reporting, redundancy switching, and local/remote communications are unavailable if
both MPUs have failed or are missing.
3.1.2 MPU Auxiliary Board

The areas enclosed in dotted lines in the above block diagram identify sections of the MPU located on the
auxiliary daughter board that plugs into the MPU. The AUX board contains the 10Base-T Ethernet
interface circuitry, an RS422 interface, additional RAM expansion, and additional flash memory for
expanded program code and FPGA code storage.
The functions of the auxiliary board have now been incorporated into a single MPU printed circuit board
module. MPUs with the auxiliary board can be interchanged and mixed with this new MPU module.
3.1.3 Installation/Replacement
PRECAUTION: MODULES USED IN THIS EQUIPMENT CONTAIN ELECTRONIC
COMPONENTS THAT MAY BE DAMAGED BY STATIC ELECTRICITY.
WHEN HANDLING MODULES, USE A STATIC-DISSIPATIVE KIT AND
TOUCH ONLY THE FRONT PANEL OR SIDE EDGES. AVOID TOUCHING
THE REAR EDGE CONNECTORS, SOLDER CONNECTIONS,
The Service Modules must be installed with the Redundancy Service Modules (RIM). The RIM must be
initially installed with the service module in order for the MPU to program the service module.
1. Locate the slot position for the module.

2. Install the service module as follows:
B. Press firmly on the faceplate and handle to lock module into place.
3.1.4 Diagnostics/Troubleshooting
The troubleshooting procedure assumes the TransAccess 200 System was operating normally before a
malfunction occurred. The particular malfunction can be isolated using front panel indicators and
diagnostic tests. Follow the troubleshooting steps listed below in the order given to locate and correct
network failures. Before troubleshooting, ensure:
• Power is applied to TransAccess 200 and to all peripheral equipment.

• All cables are correctly and securely connected.
NOTE: Node and module level diagnostics are available through the User Interface Device at
the front of the MPU module, or through Telnet/SNMP via the Ethernet port. Some
procedures described below require access from the User Interface Device, Telnet, or
SNMP. Refer to Chapter 4 for more information.
If a malfunction occurs immediately after installing new equipment or replacing equipment at an

TransAccess 200 node, do the following:
TA-200 OP
8/29/03 3-2
1. Check configuration: Refer to Chapter 4 (Configuration) to verify that parameter selections
are correct.
2. Identify alarm: Determine the nature of the alarm. Observe the alarm indicators on the
MPU and the Service Modules. Upload the alarm status to the User Interface Device (if
available) to quickly pinpoint the failure.
3. Loss of Communication: If communication is lost to the MPU module from the User
Interface Device, first verify that the cable is operational and connected securely to the
terminal and MPU module. If communication does not return, unplug the on-line MPU
module. This will cause the protection MPU module to go on-line. Plug the User Interface
Device into the remaining MPU and verify that communication has been restored.
3.2 T3/STS-1 to T1 Programmable Multiplexer Module (PM13/PM13+)

Two versions of the PM13 are available. The standard version supports either T3 or STS-1
programmable interfaces towards the line. A second version, called the M13-T3, provides only T3
operation towards the line. The M13-T3 only module supports all the features except those related to
VT1.5 and STS-1 operation.
The PM13 module frames up to either a single T3 or STS-1 signal and demultiplexes it into 28 T1
signals. When configured for STS-1 operation, the STS-1 and VT1.5 path is terminated and monitored
for alarm and bit errors prior to demultiplexing the 28 T1 signals from the VT1.5 tributaries. When
configured for T3 operation, the PM13 module automatically detects M13 or C-bit parity T3 framing.
The PM13 monitors input alarms at the T3 and T2 levels and demultiplexes the T2's into 28 T1 signals.
In the reverse direction, when configured for STS-1 operation, the 28 T1 signals are mapped into VT1.5
tributaries that are multiplexed into the STS-1 Synchronous Payload Envelope (SPE) per the SONET
standard in GR-253-CORE. When configured for T3 operation, the 28 T1 signals are multiplexed into
T2’s and then T3. The T3 output conforms to the standard DSX-3 levels.
The T3/STS-1 port supports Loop Timing and Local Timing. Using Loop Timing, the recovered T3 or
STS-1 clock generates the outgoing T3 or STS-1 timing. Using Local Timing, a local oscillator (accurate
to +/- 20 ppm) generates the outgoing timing.
The PM13 module provides the capability to monitor any T1 passing through the module. The monitored
T1 signal is brought out though a Bantum Jack through the faceplate of the PM13 module. T1’s from any
of the drop ports or T1’s demultiplexed from the incoming T3/STS-1 port can be monitored. Other test
capabilities include the ability to generated and monitor T1 test patterns to/from any T1 tributary and the
ability to monitor the T1 framing of any incoming T1 from the drop ports.
The PM13 module does not cross-connect or groom the T1 or VT1.5 signals with other modules.
However, when configure for STS-1 operation, two forms of T1 to VT1.5 mapping are selectable,
Interleaved and Transparent. Refer to Tables 4-1 and 4-2 for the mapping assignments.
3.2.1.1 Status Indicator

The MPU Module controls the PM13 module configuration parameters and diagnostic features. A tri-
color Status LED is provided on the faceplate to reflect the status of the module. The MPU module
TA-200 OP
8/29/03 3-3
controls the Status LED on the PM13 Module. Table 3-1 describes the alarms and status for each color
of the Status LED.
3.2.2 Installing DS3/STS-1 and T1 Cables
DS3/STS-1 lines require 734A coaxial or equivalent cable with BNC connectors or adapters. These
cables connect to the BNC connectors on the Redundancy Interface Modules located at the rear of the
shelf. The T1 interface requires an adapter cable to convert from the 68-pin connector on the RIMs to a
standard 64-pin CHAMP connector.
1. Plug BNC cables into DS3/STS-1 LINE IN and DS3/STS-1 LINE OUT BNC connectors,
and 68-pin cables to the T1 LINE IN and T1 LINE OUT connectors on PM13 Redundancy
Interface Module. These are located at the rear of the shelf.
2. Use cable ties, as necessary, to secure cables.

T3 Interface T1 Interface
PM13 RIMs Remote Management

Figure 3-1. Suggested Routing of Wires
3.2.3 Replacing PM13 Modules
Before replacing any module or other equipment suspected of failure, isolate the malfunction using
procedures from the troubleshooting section, or using the diagnostic procedures.
If the malfunction is isolated to the communication line or equipment other than the TransAccess 200
System, proceed as follows:
• Perform BERT tests on any questionable facilities to verify their proper operation.
• Take appropriate action to repair or replace faulty equipment other than the TransAccess 200
System.
If the malfunction is isolated to TransAccess 200 equipment, proceed as follows:
• Replace the defective component as described in the appropriate procedure. Do not attempt to
repair modules.
• In a redundant configuration, replace failed modules as soon as possible to ensure maximum
system availability.
All TransAccess 200 System modules may be replaced in an operating TransAccess 200 node without
turning off power.
PRECAUTION: IN SOME CASES, REPLACING A MODULE MAY DISRUPT

TRAFFIC SUPPORTED BY THAT MODULE. EACH
TA-200 OP
8/29/03 3-4
PROCEDURE DESCRIBES THE IMPLICATIONS OF THE
REPLACEMENT TO AN OPERATING TRANSACCESS 200
SYSTEM. READ THE PROCEDURE CAREFULLY BEFORE
PERFORMING THE REPLACEMENT IN ORDER TO
ENSURE MINIMUM USER DATA LOSS.

STATIC-DISSIPATIVE KIT AND TOUCH ONLY THE FRONT
PANEL OR SIDE EDGES. AVOID TOUCHING THE REAR
EDGE CONNECTORS, SOLDER CONNECTIONS,
1. Make sure the service module being replaced is offline and remains protected by using the
Force Manual Protection Switch command to initiate protection switching for the module to
be replaced.
2. Unscrew the module faceplate from the shelf assembly.
3. Remove the PM13 module in question.
4. Install replacement PM13 module as follows:
NOTE: The MPU module automatically configures and provisions the
replacement service module after it is inserted in the shelf.
5. Use the Restore command to enable automatic protection switching.
Under certain conditions, the TransAccess 200 system can automatically protect for system failures.
Conditions that will cause a redundant PM13 to automatically protect are listed below.
• T3/STS-1 Input Alarm (LOS/OOF/LOP/SLM)

• T2/VT1.5 Input Alarm (LOF, LOP, SLM)
• Board Alarm (board not programmable, internal clock failure)
OTE: Protection switching may not occur if both the primary and redundant modules report the
same alarm. Usually, these cases indicate an input line failure.
The troubleshooting procedure assumes that the TransAccess 200 System was operating normally before
a malfunction occurred. The particular malfunction can be isolated using front panel indicators and
• Power is applied to local and remote nodes and to all peripheral equipment.
TA-200 OP
8/29/03 3-5
Table 3-1. PM13 Service Module STAT Indicator
Indicator Color Description
Green Indicates one of the following conditions:

The PM13 Service Module is online and functioning properly
During Lamp Test, green indicates the red portion of the LED has failed
Yellow Indicates a maintenance condition (loopback enabled, T1 test enabled etc.) is
active. During Lamp Test, yellow indicates the LED is functioning properly.
Flashing Yellow Indicates the PM13 module is unconfigured or configuration is in progress.
Red Indicates one of the following conditions for a failed off-line (protected) PM13
Service Module and causes a Minor System Alarm:
PM13 Board Alarm
DS3/STS-1 output loss
Incoming DS3/STS-1 Alarms (LOS, OOF, AIS)
DS3 X-bit (far-end alarm)
STS-1 Line Alarms (SLM, LOP)
Incoming DS2 Out-of-Frame (OOF)
DS2 X-bit (far-end alarm)
Incoming VT1.5 Alarms (LOP, AIS, RDI)
Incoming T1 LOS, AIS
During Lamp Test, red indicates the green portion of the LED has failed
Flashing Red Indicates one of the following conditions for a failed on-line (unprotected) PM13
Service Module and causes a Major System Alarm (far-end alarms and T1 alarms
are Minor System Alarms):
PM13 Board Alarm
DS3/STS-1 output loss
Incoming DS3/STS-1 Alarms (LOS, OOF, AIS)
DS3 X-bit (far-end alarm – minor)
STS-1 Line Alarms (SLM, LOP)
Incoming DS2 Out-of-Frame (OOF)
DS2 X-bit (far-end alarm - minor)
Incoming VT1.5 Alarms (LOP, AIS, RDI)
Incoming T1 LOS, AIS
Off Indicates one of the following conditions:
PM13 Module is off-line and standing by to protect online PM13 Module(s)
Loss of power to PM13 Module and/or to the TransAccess 200 System. This
condition could indicate the failure of the PM13 Module’s internal power
supply. Failure to the internal power supply causes a Minor System Alarm if
the failed module is protected by another PM13 Module. If the failed module
is unprotected, this condition initiates a Major System Alarm.
NOTE: Some procedures described below require access from the User
Interface Device attached to the User System Interface (USI)
connector at the front of the MPU Module. Refer to Chapter 4 for
more information.
TA-200 OP
8/29/03 3-6
TransAccess 200 node, check the configuration. Refer to Chapter 4 (PM13 Configuration) to verify that
parameter selections are correct.
The troubleshooting procedure is summarized below:
1. Identify alarm: Determine the nature of the alarm. Observe the system alarm indicators on
the MPU Module and the STAT indicator on all modules. Use the User Interface Device
diagnostics (if available) to quickly pinpoint the failure.
2. Analyze data flow: If service is degraded or has been interrupted but no system alarm has
been asserted, determine how the malfunction is affecting data flow in the network by
examining the PM13 bit error counters.
3. Perform loopbacks and non-intrusive tests: Perform channel and/or line loopbacks and
non-intrusive channel tests to isolate problem locations. Channel and line loopbacks are
intrusive tests that disrupt traffic on the channel or line being tested.
4. Initiate module protection switching: After identifying the suspect TransAccess 200 node,
initiate protection switching for suspected service modules.
The following paragraphs describe each step in the troubleshooting procedure in detail. Some steps
include diagnostic test procedures.
3.2.4.1 Step 1. Identify Alarm
TransAccess 200 node, T3/STS-1 channel and T1 channel alarm events are indicated by a LED indicator
on the front panels of the modules installed in the node. System alarms are also reported by local office
alarm systems connected to the TransAccess 200 and by messages displayed on the User Interface
Device. Alarms reported by the local office alarm system are silenced using the ACO button on the MPU
Module.
Note: To activate the Alarm Cut-Off feature, the ACO/LAMPTEST button should be depressed for at least
2 seconds (the MPU LED will turn yellow when 2 seconds have passed). Depressing the button for less
than 2 seconds will perform the LAMPTEST function, which illuminates all the LEDs in the TransAccess
200. If the ACO/LAMPTEST button continues to be depressed for 10 seconds, the MPU LED will begin
to blink red. Once it blinks 3 times, the MPU will reset after the ACO/LAMPTEST button is released.
After identifying an alarm, refer to Table 3-1 for descriptions of possible alarm causes. Then perform the
corrective action shown. When multiple alarms occur simultaneously, troubleshoot one alarm at a time.
3.2.4.2 Step 2. Analyze Data Flow
If problems occur that aren't indicated by system alarms, begin the troubleshooting process by analyzing
data flow. Analyze reports from communication systems manager, maintenance personnel, or user to
isolate the problem to one of the following:
• No or faulty data flow on a T1 facility path indicates possible PM13 module failure,
T3/STS-1 facility problem, or T1 facility problem. If the redundant module reports the same
problem, the problem is likely with the facility. If only one module reports the input alarm,
then that module likely has a failure. Use the diagnostic features to check signal quality at
each service module in the path. If necessary use loopback tests to isolate cause of failure.
TA-200 OP
8/29/03 3-7
• No or faulty data flow on all T1 and T3/STS-1 facilities to a node indicates loss of power
or faulty electrical service. If the redundant module reports the same problem, the problem is
with the facility. If only one module reports the input alarm, then that module has a failure.
3.2.4.3 Step 3. Perform Loopbacks and Non-intrusive Tests

An apparent failure of a T3/STS-1 or T1 connection can be caused by malfunctioning equipment at either
end of the channel path. Before performing channel loopbacks or non-intrusive tests, verify that the
equipment at both ends is operating properly.
When sufficient information is available to localize a problem to a particular T3/STS-1 or T1 connection,

non-intrusive tests and loopback tests performed in a logical sequence help isolate the problem.
Non-intrusive tests allow testing of signals without disrupting data transmission. In any troubleshooting
sequence, non-intrusive tests should be performed first to allow gathering of information without
interrupting other traffic.
Each loopback tests a section of the channel path, allowing the point of failure to be isolated to a specific
portion of the channel path or to a piece of equipment. In a loopback test, a transmit line is connected to a
receive line at some point within the path under test. Test data is transmitted through the loop by external
test equipment. If the test data is received correctly, assume the looped section of the path is operating
properly.
PRECAUTION: BEFORE INITIATING LOOPBACK TESTS, NOTIFY ALL AFFECTED

USERS THAT CHANNELS ARE BEING TAKEN OFFLINE AND
THAT DATA OR VOICE CONNECTIONS WILL BE LOST.
The non-intrusive T3/STS-1 or T1 signal test is able to test a T3/STS-1 or T1 signal using a T3/STS-1 or
T1 patch panel, if equipped, as shown in Figure 3-5. Simply connect a DS3/STS-1 or T1 signal to the
monitor connector of the jackpanel to measure the incoming or outgoing signal to the TransAccess 200.
Loopback tests (shown in Figure 3-2) to diagnose network failures include:
• T3/STS-1 Line Loopback

• T1 loopback towards T3/STS-1
• T1 Line Loopback (towards T1 drop port)
T1 test generation and detection is described in 4.5.2.10.2.
TA-200 OP
8/29/03 3-8
TRANSACCESS 200 SYSTEM T3/STS-1
TERMINAL
PATCH PANEL EQUIPENT
T1 T1 T1 TO T3/STS-1
PATCH PANEL LINE T3/STS-1 LINE
INTERFACE MUX INTERFACE
T1 T3/STS-1 T3/STS-1
SIGNAL SIGNAL Telect DNX-1 SIGNAL
010-7424-7401
or Equivalent
T1 T1 T3
MONITOR
DROP LOOPBACK LINE ONLY
LOOPBACK TOWARDS LOOPBACK
T3/STS-1 T3/STS-1
TEST
SET
Figure 3-2: T3/STS-1 Signal Test and Loopbacks
3.3 T3/STS-1/AU3 to E1 Programmable Multiplexer Module (PM13E)

The PM13E module frames up to either a single T3, STS-1, or AU3 signal and demultiplexes it into 21
E1 signals. When configured for STS-1 operation, the STS-1 and VT2 path is terminated and monitored
for alarm and bit errors prior to demultiplexing the 21 E1 signals from the VT2 tributaries. When
configured for T3 operation, the PM13E module automatically detects M13 or C-bit parity T3 framing.
The PM13E monitors input alarms at the T3 and G.747 levels and demultiplexes the G.747 signals into 21
E1 signals. When configured for AU3 operation, the AU3 and VC-12 path is terminated and monitored
for alarm and bit errors prior to demultiplexing the 21 E1 signals.
In the reverse direction, when configured for STS-1 operation, the 21 E1 signals are mapped into VT2
tributaries that are multiplexed into the STS-1 Synchronous Payload Envelope (SPE) per the SONET
standard in GR-253-CORE. When configured for T3 operation, the 21 E1 signals are multiplexed into a
G.747 format and then T3. The T3 output conforms to the standard DSX-3 levels and supports both
standard M13 and C-Par framing. When configured for AU3 operation, the 21 E1 signals are mapped
into the VC-12/TUG-2 format before being multiplexed to AU3. The AU3 signal conforms to the same
electrical standards as STS-1.
The T3/STS-1/AU3 port supports Loop Timing and Local Timing. Using Loop Timing, the recovered
T3, STS-1, or AU3 clock generates the outgoing T3, STS-1, or AU3 timing. Using Local Timing, a local
oscillator (accurate to +/- 20 ppm) generates the outgoing timing.
The PM13E module provides the capability to monitor any E1 passing through the module. The
monitored E1 signal is brought out though a Bantum Jack through the faceplate of the PM13E module.
TA-200 OP
8/29/03 3-9
E1’s from any of the drop ports or E1’s demultiplexed from the incoming T3/STS-1/AU3 port can be
monitored. Other test capabilities include the ability to generated and monitor E1 test patterns to/from
any E1 tributary and the ability to monitor the E1 framing of any incoming E1 from the drop ports.
The PM13E module does not cross-connect or groom the E1 or VT/VC signals with other modules.
However, when configure for STS-1 or AU3 operation, two forms of E1 to VT/VC mapping are
selectable, Interleaved and Transparent. Refer to Table 4-1 and Table 4-2 for the mapping assignments.
The MPU Module controls the PM13E module configuration parameters and diagnostic features. A tri-
color Status LED is provided on the faceplate to reflect the status of the module. The MPU module
controls the Status LED on the PM13E Module. Table 3-2 describes the alarms and status for each color
of the Status LED.
3.3.2 Installing DS3/STS-1 and T1 Cables
T3/STS-1/AU3 lines require 734A coaxial or equivalent cable with BNC connectors or adapters. These
cables connect to the BNC connectors on the Redundancy Interface Modules located at the rear of the
shelf. The E1 interface requires an adapter cable to convert from the 68-pin connector on the RIMs to a
standard 64-pin CHAMP connector.
1. Plug BNC cables into T3/STS-1/AU3 LINE IN and T3/STS-1/AU3 LINE OUT BNC
connectors, and 68-pin cables to the E1 LINE IN and E1 LINE OUT connectors on PM13
Redundancy Interface Module. These are located at the rear of the shelf.

T3 Interface T1 Interface
PM13 RIMs Remote Management

Figure 3-3. Suggested Routing of Wires
3.3.3 Replacing PM13E Modules

System.
TA-200 OP
8/29/03 3-10
repair modules.
turning off power.

TRAFFIC SUPPORTED BY THAT MODULE. EACH
PROCEDURE DESCRIBES THE IMPLICATIONS OF THE
REPLACEMENT TO AN OPERATING TRANSACCESS 200
SYSTEM. READ THE PROCEDURE CAREFULLY BEFORE
PERFORMING THE REPLACEMENT IN ORDER TO
ENSURE MINIMUM USER DATA LOSS.

STATIC-DISSIPATIVE KIT AND TOUCH ONLY THE FRONT
PANEL OR SIDE EDGES. AVOID TOUCHING THE REAR
EDGE CONNECTORS, SOLDER CONNECTIONS,
be replaced.
3. Remove the PM13E module in question.
4. Install replacement PM13E module as follows:
NOTE: As long as the RIMs are installed, the MPU module automatically configures and
provisions the replacement service module after it is inserted in the shelf.
5. Use the Restore command to enable automatic protection switching.
Conditions that will cause a redundant PM13E to automatically protect are listed below.
• T3/STS-1/AU3 Input Alarm (LOS/OOF/LOP/SLM)

• G.747/VT/VC Input Alarm (LOF, LOP, SLM)
TA-200 OP
8/29/03 3-11
OTE: Protection switching may not occur if both the primary and redundant modules report the
same alarm. Usually, these cases indicate an input line failure.

TransAccess 200 node, check the configuration. Refer to Chapter 4 (PM13 Configuration) to verify that

examining the PM13E bit error counters.
TA-200 OP
8/29/03 3-12
Table 3-2. PM13E Service Module STAT Indicator

The PM13E Service Module is online and functioning properly
Flashing Yellow Indicates the PM13E module is unconfigured or configuration is in progress.
Red Indicates one of the following conditions for a failed off-line (protected) PM13E
PM13E Board Alarm
T3/STS-1/AU3 output loss
Incoming T3/STS-1/AU3 Alarms (LOS, OOF, AIS)
T3 X-bit (far-end alarm)
STS-1/AU3 Line Alarms (SLM, LOP)
Incoming G.747 Out-of-Frame (OOF)
G.747 RAI (far-end alarm)
Incoming VT/VC Alarms (LOP, AIS, RDI)
Incoming E1 LOS, AIS
Flashing Red Indicates one of the following conditions for a failed on-line (unprotected)
PM13E Service Module and causes a Major System Alarm (far-end alarms and
T1 alarms are Minor System Alarms):
PM13E Board Alarm
T3 X-bit (far-end alarm – minor)
STS-1/AU3 Line Alarms (SLM, LOP)
Incoming G.747 Out-of-Frame (OOF)
G.747 RAI (far-end alarm - minor)
Incoming VT/VC Alarms (LOP, AIS, RDI)
Incoming E1 LOS, AIS
PM13E Module is off-line and standing by to protect online PM13E
Module(s)
Loss of power to PM13E Module and/or to the TransAccess 200 System.
This condition could indicate the failure of the PM13E Module’s internal
power supply. Failure to the internal power supply causes a Minor System
Alarm if the failed module is protected by another PM13E Module. If the
failed module is unprotected, this condition initiates a Major System Alarm.
more information.
TA-200 OP
8/29/03 3-13
TransAccess 200 node, T3/STS-1/AU3 channel and E1 channel alarm events are indicated by a LED
indicator on the front panels of the modules installed in the node. System alarms are also reported by
local office alarm systems connected to the TransAccess 200 and by messages displayed on the User
Interface Device. Alarms reported by the local office alarm system are silenced using the ACO button on
the MPU Module.
Note: To activate the Alarm Cut-Off feature, the ACO/LAMPTEST button should be depressed for at least
2 seconds (the MPU LED will turn yellow when 2 seconds have passed). Depressing the button for less
than 2 seconds will perform the LAMPTEST function, which illuminates all the LEDs in the TransAccess
200. If the ACO/LAMPTEST button continues to be depressed for 10 seconds, the MPU LED will begin
to blink red. Once it blinks 3 times, the MPU will reset after the ACO/LAMPTEST button is released.
• No or faulty data flow on a E1 facility path indicates possible PM13E module failure,
T3/STS-1/AU3 facility problem, or T1 facility problem. If the redundant module reports the
same problem, the problem is likely with the facility. If only one module reports the input
alarm, then that module likely has a failure. Use the diagnostic features to check signal quality
at each service module in the path. If necessary use loopback tests to isolate cause of failure.
• No or faulty data flow on all E1 and T3/STS-1/AU3 facilities to a node indicates loss of
power or faulty electrical service. If the redundant module reports the same problem, the
problem is with the facility. If only one module reports the input alarm, then that module has
a failure.

An apparent failure of a T3/STS-1/AU3 or E1 connection can be caused by malfunctioning equipment at
either end of the channel path. Before performing channel loopbacks or non-intrusive tests, verify that the
equipment at both ends is operating properly.
When sufficient information is available to localize a problem to a particular T3/STS-1/AU3 or E1

connection, non-intrusive tests and loopback tests performed in a logical sequence help isolate the
problem.
TA-200 OP
8/29/03 3-14
properly.
PRECAUTION: BEFORE INITIATING LOOPBACK TESTS, NOTIFY ALL AFFECTED

USERS THAT CHANNELS ARE BEING TAKEN OFFLINE AND
THAT DATA OR VOICE CONNECTIONS WILL BE LOST.
The non-intrusive T3/STS-1/AU3 or E1 signal test is able to test a T3/STS-1/AU3 or E1 signal using a
T3/STS-1/AU3 or E1 patch panel, if equipped, as shown in Figure 3-5. Simply connect a T3/STS-1/AU3
or E1 signal to the monitor connector of the jackpanel to measure the incoming or outgoing signal to the
TransAccess 200.
• T3/STS-1/AU3 Line Loopback

• E1 loopback towards T3/STS-1/AU3
• E1 Line Loopback (towards E1 drop port)
E1 test generation and detection is described in 4.5.2.10.2.
TRANSACCESS 200 SYSTEM
PATCH PANEL
E1 E1 E1 TO T3/STS-1
PATCH PANEL LINE T3/STS-1 AU3 LINE
INTERFACE MUX INTERFACE
E1 T3/STS-1 T3/STS-1
010-7424-7401
or Equivalent
MONITOR T3/STS-1 /AU3

ONLY TERMINAL EQUIPENT
E1 E1 T3/STS-1
DROP LOOPBACK AU3 LINE
LOOPBACK TOWARDS LOOPBACK
T3/STS-1 T3/STS-1/
AU3 TEST
SET
Figure 3-4: T3/STS-1/AU3 Signal Test and Loopbacks
3.4 PM13/PM13E 1x1 Incoming Redundancy Service Module (RIM)

The PM13 RIM is used for the PM13, PM13+, M13-T3 and PM13E modules.
TA-200 OP
8/29/03 3-15
Connecting an incoming and outgoing redundancy Service Module (RIM) to the rear of the backplane
provides hardware redundancy for the PM13E modules. Each slot has a 70-pin connector to interface the
RIM to the backplane.
Signal to Primary
T3/STS-1/AU3 PM13 or PM13E
Signal In Module
(BNC)
Signal to Redundant
PM13 or PM13E
Module
TIP Signal to Primary

T1 or E1 and Redundant
Signal In PM13 or PM13E
Signal to Primary
RING
and Redundant
PM13 or PM13E
Figure 3-5. PM13 IN 1x1 RIM Block Diagram
The diagrams above and below are repeated 28 times for each T1 signal.
Signal from Primary

T3/STS-1/AU3 PM13 or PM13E
Signal Out Module
(BNC) Signal from Redundant
Relay PM13 or PM13E
Module
Signal from Primary

TIP and Redundant
T1 or E1 PM13 or PM13E
Signal Out
Signal from Primary
RING and Redundant
PM13 or PM13E
Figure 3-6. PM13 OUT 1x1 RIM Block Diagram
The diagrams above are repeated 28 times for each T1 signal. The relay for the outgoing T3/STS-1/AU3
signal is controlled by the MPU module through latches on the redundant PM13E module. If the
redundant module is removed, the relay contacts will connect the T3/STS-1/AU3 signal to the primary
PM13E module. The MPU tri-states the outgoing T1 line drivers when a PM13E module is off-line.
TA-200 OP
8/29/03 3-16
3.4.2 Installation/Replacement
PRECAUTION: IN ALL CASES, REPLACING A REDUNDANCY
INTERFACE MODULE WILL DISRUPT TRAFFIC
SUPPORTED BY THAT MODULE.

ELECTRONIC COMPONENTS THAT MAY BE
DAMAGED BY STATIC ELECTRICITY. WHEN
HANDLING MODULES, USE STATIC-DISSIPATIVE
KIT AND TOUCH ONLY THE SIDE EDGES.
To install a 1x1 RIM, slide the module into one of the slots at the rear of the shelf. The slots are keyed so
that only a 1x1 OUT RIM is only intalled into the odd numbered slots. The 1x1 IN RIM is only installed
into the even numbered slots. Once the RIM is inserted all the way, screw the RIM faceplate into the
shelf. Once the faceplate is screwed down, the cables are ready to be attached.
To remove a 1x1 RIM, first disconnect the cables and unscrew the RIM faceplate from the shelf. Pull at
the edge of the RIM faceplate to unplug the RIM.
3.5 OC-3/STM-1 to STS-1/T3/AU3 Service Module (OMX3)

This section describes the operation of the OMX3 module. The OMXT3 module has the same
functionality of the OMX3 except that it can only be configured to drop T3 from either OC-3 or STM-1.
The OMX3 module multiplexes/de-multiplexes three T3, STS-1, or AU3 signals from an OC-3 or STM-1
optical interface. The user must choose between T3, STS-1, or AU3 for each of the three drop interfaces.
When the OMX3 module is configured for OC-3, the drop ports can be configured for either T3 or STS-1.
When configured for STM-1, the drop ports can be configured for T3 or AU3.
The OMX3 module provides T3/STS-1/AU3 alarm detection. For the T3/STS-1/AU3 drop ports, the
OMX3 detects bipolar violations, LOS, OOF, and AIS for each of the incoming T3/STS-1/AU3 signals
via a microprocessor interface. For the OC-3/STM-1 line, LOS, LOF, AIS, RDI, SLM, and section, line,
and path code violations.
The OMX3 module supports Loop Timing, Local Timing, Through Timing, or External Timing. Using
Loop Timing, the recovered OC-3/STM-1 clock generates the outgoing OC-3/STM-1 timing. Using
Local Timing, a local oscillator (accurate to +/- 20 ppm) generates the outgoing timing. Through Timing
is used in add/drop applications in which case the outgoing OC-3/STM-1 clock is generated from the
receive OC-3/STM-1 from the adjacent OMX3 module. An external clock can be connected to a
backplane terminal block. This 64KHz composite clock can be used to time the outgoing OC-3/STM-1
signal.
NOTE: Older backplanes will require an small adapter card to be installed between the input
clock terminal block and the clock cable entering the shelf. Screw down the two pins of the clock
adapter module into the clock inputs of the terminal block and then connect the clock cable to the
adapter module.
The OMX3 module can be configured to work in both add/drop ring applications as well as in terminal
applications, that is, those applications that terminate all 84 T1 signals at the node.
TA-200 OP
8/29/03 3-17
The MPU Module controls the OMX3 module configuration parameters and diagnostic features. A tri-
color Status LED is provided on the faceplate to reflect the status of the module and an amber LED to
indicate the transmit laser is enabled. The MPU module controls the Status LED and 'Laser On' LED on
the OMX3 Module. Table 3-3 describes the alarms and status for each color of the Status LED.
3.5.2 Installing DS3/STS-1 and OC-3 Optical Cables
T3/STS-1/AU3 lines require 734A coaxial or equivalent cable with BNC connectors or adapters.
However, due to mechanical limitations, SMA connectors are provided out the rear of the OMX3 RIM.
Therefore, cable adapters are used to convert from SMA to BNC for connection to PM13E modules (if
terminating T1 signals) or for connection to other T3/STS-1/AU3 equipment. Optionally, when the
OMX3 IN and OUT RIMs are used, a Turin Networks BNC Connector Panel can be used to manage the
T3/STS-1/AU3 cable routing.
1. Plug SMA-to-BNC cables into T3/STS-1/AU3 LINE IN and T3/STS-1/AU3 LINE OUT
SMA connectors. These are located at the rear of the shelf, see Figure 3-7. The optical ‘LC’
type single-mode cables are connected at the front faceplate of the OMX3 module, see
Figure 3-8.
OMX3 Service Module External Timing Power/Ground

OC-3 DCC (future) T3/STS-1/AU3 FacilitiesOffice Alarms
PM13 RIMs OMX3 OMX3 Terminal RIM Remote Management

1x1 RIM Interface Port
Figure 3-7. Suggested T1, T3/STS-1, Power, and Alarm Cable Routing
EXchange MuxTM
EXchange MuxTM
ACO ACO
LAMP LAMP
TEST TEST
T1 T1 T1 T1 T1 T1 T1 T1 T1 T1
Programmable Programmable Programmable Programmable Programmable Programmable Programmable Programmable

USI USI M13 M13 M13 M13 M13 M13 M13 M13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
PM13
MPU
MPU
Figure 3-8. Suggested OC-3 Routing of Wires
PRECAUTION: EYE PROTECTION IS RECOMMENDED IN AREAS NEAR FIBER OPTIC

EQUIPMENT.
PRECAUTION: TO AVIOD POSSIBLE EYE DAMAGE, CONNECT THE FIBER CABLES TO

THE OMX3 MODULES PRIOR TO INSERTING THE OMX3 MODULES INTO
TA-200 OP
8/29/03 3-18
THE SHELF. DO NOT REMOVE CABLES FROM THE OMX3 MODULE
WHILE IT IS PLUGGED INTO THE SHELF.
3.5.3 Replacing OMX3 Modules

System.
repair modules.

turning off power.

TRAFFIC SUPPORTED BY THAT MODULE. EACH PROCEDURE
DESCRIBES THE IMPLICATIONS OF THE REPLACEMENT TO AN
OPERATING TRANSACCESS 200 SYSTEM. READ THE
PROCEDURE CAREFULLY BEFORE PERFORMING THE
REPLACEMENT IN ORDER TO ENSURE MINIMUM USER DATA
LOSS.
PRECAUTION: MODULES USED IN THIS EQUIPMENT CONTAIN ELECTRONIC

COMPONENTS THAT MAY BE DAMAGED BY STATIC
ELECTRICITY. WHEN HANDLING MODULES, USE STATIC-
DISSIPATIVE KIT AND TOUCH ONLY THE FRONT PANEL OR
SIDE EDGES. AVOID TOUCHING THE REAR EDGE
CONNECTORS, SOLDER CONNECTIONS, COMPONENTS, OR
COMPONENT PINS.
be replaced.
3. Partially remove the OMX3 module in question.
4. Disconnect the optical cables and then remove the module from the shelf.
TA-200 OP
8/29/03 3-19
5. Install replacement OMX3 module as follows:
B. Attach optical cables at the faceplate connector.
C. Press firmly on the faceplate and handle to lock module into place.
D. Tighten screw to lock in module.
NOTE: When replacing a configured service module, the MPU module
automatically configures and provisions the replacement service
module after it is inserted in the shelf.
6. Connect the optical cables.
7. Use the Restore command to enable manual protection switching.
Conditions that will cause a redundant OMX3 to automatically protect are listed below.
• OC-3/STM-1 Input Alarm (LOS, LOF, LOP, SLM)

• T3/STS-1/AU3 Input Alarm (LOS, OOF, LOP)
NOTE: Protection switching may not occur if both the primary and redundant modules report
the same alarm. Usually, these cases indicate an input line failure.
more information.

TransAccess 200 node, check the configuration. Refer to Chapter 4 (OMX3 Configuration) to verify that
TA-200 OP
8/29/03 3-20
examining the OMX3 bit error counters.
Table 3-3. OMX3 Service Module STAT Indicator

The OMX3 Service Module is online and functioning properly
Flashing Yellow Indicates the OMX3 module is unconfigured or configuration is in progress.
Red Indicates one of the following conditions for a failed off-line (protected) OMX3
OMX3 Board Alarm or Clock Alarm
STS-1/AU3 Drop Alarms (LOS, LOF, LOP, AIS, SLM, RDI)
Incoming OC-3STM-1 Alarms (LOS, LOF, LOP, AIS, SLM, RDI-L, RDI-P,
AIS-P)
Flashing Red Indicates one of the following conditions for a failed on-line (unprotected) OMX3
Service Module and causes a Major System Alarm
• OMX3 Board Alarm or Clock Alarm
STS-1/AU3 Path Alarms (LOP, AIS, SLM, RDI)
Incoming OC-3/STM-1 Alarms (LOS, LOF, AIS, SLM)
OMX3 Module is off-line and standing by to protect online OMX3 Module(s)
Loss of power to OMX3 Module and/or to the TransAccess 200 System. This
condition could indicate the failure of the OMX3 Module’s internal power
supply. Failure to the internal power supply causes a Minor System Alarm if
the failed module is protected by another OMX3 Module. If the failed
module is unprotected, this condition initiates a Major System Alarm.
TA-200 OP
8/29/03 3-21
TransAccess 200 node, T3/STS-1 channel and OC-3 alarm events are indicated by a LED indicator on the
front panels of the modules installed in the node. System alarms are also reported by local office alarm
systems connected to the TransAccess 200 and by messages displayed on the User Interface Device.
Alarms reported by the local office alarm system are silenced using the ACO button on the MPU Module.
Note: To activate the Alarm Cut-Off feature, the ACO/LAMPTEST button should be depressed for at
least 2 seconds (the MPU LED will turn yellow when 2 seconds have passed). Depressing the
button for less than 2 seconds will perform the LAMPTEST function, which illuminates all the
LEDs in the TransAccess 200. If the ACO/LAMPTEST button continues to be depressed for 10
seconds, the MPU LED will begin to blink red. Once it blinks 3 times, the MPU will reset after
the ACO/LAMPTEST button is released.
• No or faulty data flow on a T3/STS-1/AU3 facility path indicates possible OMX3 module
failure, T3/STS-1/AU3 facility problem, or an OC-3/STM-1 facility problem. If the redundant
module reports the same problem, the problem is likely with the facility. If only one module
reports the input alarm, then that module likely has a failure. Use the diagnostic features to
check signal quality at each service module in the path. If necessary use loopback tests to
isolate cause of failure.
• No or faulty data flow on all T3/STS-1/AU3 and OC-3/STM-1 facilities to a node indicates
loss of power or faulty electrical service. If the redundant module reports the same problem,
the problem is with the facility. If only one module reports the input alarm, then that module
has a failure.

An apparent failure of a T3/STS-1/AU3 or OC-3/STM-1 connection can be caused by malfunctioning
equipment at either end of the channel path. Before performing channel loopbacks or non-intrusive tests,
verify that the equipment at both ends is operating properly.
When sufficient information is available to localize a problem to a particular T3/STS-1/AU3 or OC-

3/STM-1 connection, non-intrusive tests and loopback tests performed in a logical sequence help isolate
the problem.
properly.
TA-200 OP
8/29/03 3-22
PRECAUTION: BEFORE INITIATING LOOPBACK TESTS, NOTIFY ALL
AFFECTED USERS THAT CHANNELS ARE BEING TAKEN
OFFLINE AND THAT DATA OR VOICE CONNECTIONS
WILL BE LOST.
The non-intrusive T3/STS-1/AU3 signal test is able to test a T3/STS-1/AU3 signal using a T3/STS-
1/AU3 patch panel, if equipped, as shown in Figure 3-10. Simply connect a T3/STS-1/AU3 signal to the
monitor connector of the jackpanel to measure the incoming or outgoing signal to the TransAccess 200.

• OC-3/STM-1 Line Loopback
• OC-3/STM-1 Drop Loopback (towards drop ports)
• T3/STS-1/AU3 Line Loopback (towards OC-3/STM-1)
• T3/STS-1/AU3 Drop Loopback
PRECAUTION: THE OC-3/STM-1 DROP LOOPBACK AND T3/STS-1/AU3 LINE
LOOPBACKS CANNOT BE ENABLED SIMULTANEOUSLY AS ERRORS
WILL OCCUR DUE TO THE LOSS OF A STABLE CLOCK AND DATA
SOURCE
TRANSACCESS 200 SYSTEM T3/STS-1/AU3

TERMINAL
PATCH PANEL EQUIPENT
T3/STS-1/
OC-3 AU3 LINE
FRAMER INTERFACE
OC-3 T3/STS-1 T3/STS-1
010-7424-7401
or Equivalent
MONITOR
OC-3 OC-3 T3/STS-1/AU3 T3/STS-1/
ONLY
LINE DROP LOOPBACK AU3 DROP
LOOPBACK LOOPBACK TOWARDS LOOPBACK
T3/STS-1 T3/STS-1/
AU3 TEST
SET
Figure 3-9: T3/STS-1/AU3 Signal Test and Loopbacks
TA-200 OP
8/29/03 3-23
3.6 OMX3 1x1 Redundancy Service Module (RIM)
3.6.1 Theory of Operation – 1x1 RIM

Connecting an incoming and outgoing redundancy Service Module (RIM) to the rear of the backplane
provides hardware redundancy for the OMX3 modules. Each slot has a 70-pin connector to interface the
RIM to the backplane.
Signal to Primary
T3/STS-1/AU3 OMX3 Module
Signal In
(SMA)
Signal to Redundant
OMX3 Module
Signal from Primary

T3/STS-1/AU3 OMX3 Module
Signal Out
(SMA) Signal from Redundant
Relay OMX3 Module
Figure 3-10: OMX3 IN and OUT 1x1 RIM Block Diagram (each circuit repeated 3 times)
The diagrams above are repeated 3 times for each T3/STS-1 signal. The relay for the outgoing T3/STS-1
signal is controlled by the MPU module through latches on the redundant OMX3 module. If the
redundant module is removed, the relay contacts will connect the T3/STS-1 signal to the primary OMX3
module. The primary and secondary OC-3 optical signals are driven directly out the front of the primary
and secondary OMX3 modules.
3.6.2 Theory of Operation – Terminal RIM

The OMX3 Terminal RIM can be used in applications where all 84 T1’s are to be dropped and inserted
from an OC-3. The Terminal RIM interconnects 8 slots of the TransAccess 200 and is configured so that
a pair of redundant OMX3 modules and up to 3 pairs of redundant PM13 modules can be interconnected
with either T3 or STS-1 signals. The benefit of the OMX3 Terminal RIM is to eliminate the need for
external coax cables to interconnect the OMX3 T3/STS-1 drop ports with the PM13 modules.
When implementing the Terminal RIM solution, there is also a 1x1 IN and OUT RIM to mate with the
PM13 modules. These RIMs are different in nature to the standard PM13 1x1 RIM described in section
3.5.1 as they do not have the T1 transformers mounted on them nor the T3/STS-1 BNC connector.
Rather, the T1 transformers have been moved to the OMX3 Terminal RIM and as mentioned, the
T3/STS-1 signals pass through the TRML RIM from PM13 to OMX3. The Terminal (TRML) IN and
OUT RIMs provide the connectors to interface the receive and transmit T1 signals from the PM13
modules.
TA-200 OP
8/29/03 3-24
!
Standard 1x1 RIMs Terminal RIMs
Figure 3-11: RIM Installation
3.6.3 RIM Installation/Replacement

PRECAUTION: IN ALL CASES, REPLACING A REDUNDANCY
INTERFACE MODULE WILL DISRUPT TRAFFIC
SUPPORTED BY THAT MODULE.

ELECTRONIC COMPONENTS THAT MAY BE
DAMAGED BY STATIC ELECTRICITY. WHEN
HANDLING MODULES, USE STATIC-DISSIPATIVE
KIT AND TOUCH ONLY THE SIDE EDGES.
To install a 1x1 RIM, slide the module into one of the slots at the rear of the shelf. The slots are keyed so
that only a 1x1 OUT RIM can plug into the odd numbered slots. The 1x1 IN RIM can only plug into the
even numbered slots. Once the RIM is inserted all the way, screw the RIM faceplate into the shelf.
Once the faceplate is screwed down, the cables are ready to be attached.
To remove a 1x1 RIM, first disconnect the cables and unscrew the RIM faceplate from the shelf. Pull at
the edge of the RIM faceplate to unplug the RIM.
TA-200 OP
8/29/03 3-25
4 USER AND TELNET INTERFACES
4.1 User Interface Device Hardware Requirements
(Note: The User Interface Device is not provided by Turin Networks, Inc.)
• Standard terminal or PC running an ANSI or VT100 compatible ASCII terminal emulation
program.
• Configured by default for 8-bits, 1 stop bit, no parity. The MPU baud rate will auto-detect the
User Interface Device baud rate between 1200 bps and 115.2 Kbps.
• The baud rate is configurable after initial auto-detection for most standard rates.
4.2 User Interface Device Connection to the TransAccess 200
The User Interface Device is connected directly to the front panel RJ-45 jack labeled USI (User System
Interface) on either the left or right MPU module using an RS-232 cable (available from Turin Networks,
consult sales or customer service for part number). If remote access is required, attach a modem and null
modem cable provided by Turin Networks (consult Turin sales or customer service for part number).
Various cable lengths from 6 to 50 feet are available. Once connected two [ENTER] characters will
trigger a response from the MPU to display the opening screen.
4.3 User Interface Device Setup
The User Interface Device is configured according to the type of connection (local or remote via
modems).
4.3.1 Establishing a Direct Connection
The following procedures may be used to establish local communications directly between a PC running
Windows 95 or Windows 98 operating systems using the Hyper Terminal application previously
installed, and the TransAccess 200.
NOTE: Hyper Terminal may not function properly if running Windows XP, Windows 2000,
Windows NT, or Windows ME. If using these operating systems on your PC, use the TeraTerm
PRO shareware program provided on the Turin Networks CDROM or another VT100 emulation
program.
Connect the Oasys-supplied cable (815-00011-XXX) between an unused COM port on the PC and the
front panel USI jack on the MPU Module. If the TransAccess 200 is equipped with redundant MPUs, the
cable may be connected to either MPU Module, whether it’s on-line or off-line.
Turn on the PC and wait for the Windows operating system to boot up.
The following conventions are used in the detailed procedures below:

1. (95) refers to selections unique to Windows 95
2. (98) refers to selections unique to Windows 98
3. Underlined text refers to items on PC screen.
4. “Quoted” text refers to entries typed in by the user.
5. Italicized text refers to window or box titles.
6. [Brackets] denote specific keys entered by the user.
Launch the Hyper Terminal application:

• Click the START button.
TA-200 OP
8/29/03 4-1
• Select: Programs> Accessories> (98) Communications> Hyper Terminal
• Double click on Hypertrm.exe
The first time Hyper Terminal is executed, a Local Information box will appear.
Enter a telephone area code under What area (or city) code are you in now?
Click Close
NOTE - This box will not appear in the future.
The Connection Description box should appear. If it does not, click File New connection
Under Enter a name and choose an icon for the connection
Type “EXMUX” or any meaningful name.
Select any icon.
Click OK
The (95) Phone Number box or (98) Connect To box appears in place of the Connection Description box.
Under Connect Using choose Direct to Com1, or Direct to Com2 depending on which COM port the
cable was connected to in the first step.
The other entries in this box may be ignored.
Click OK
The COM1 Properties or COM2 Properties box appears in place of the previous box.
Under the Phone Number tab select the following settings:
Bits per second 1200 bps to 115.2 Kbps (115.2 Kbps recommended)
Data Bits 8
Parity None
Stop Bits 1
Flow Control None
Click OK
Under the Port Settings tab select the following settings:

Select “Terminal keys”
Emulation: VT100
Backscroll buffer lines: 0
Terminal Settings:
Character Set: ASCII
ASCII Setup (receiving):

Select “Force incoming data to 7-bit ASCII”
Select “Wrap lines that exceed terminal width
Click OK
The blank terminal screen should be displayed.

Maximize the screen by clicking the box in the upper right corner.
Hit [Enter] twice to signal to the TransAccess 200 that the User Interface Device is ready.
4.3.2 Establishing a Remote Connection via a Modem
The following procedure may be used to establish remote communications via customer-supplied
modems between a PC running the Windows 95 or Windows 98 operating system with the Hyper
Terminal application previously installed, and the TransAccess 200.
TA-200 OP
8/29/03 4-2
It is assumed that the user has previously installed a modem in the PC and that it is connected to a dial-up
telephone circuit. It is further assumed that a separate stand-alone modem has been configured at the
TransAccess 200 location as follows:
Automatic Answer Mode [ATS0=0]

Carrier Detect (DCD) always on [AT&C0]
Data Terminal Ready (DTR) ignored by modem [AT&D0]
Request to Send (RTS) ignored by modem [AT&R1]
Data Set Ready (DSR) always on [AT&S0]
Return Results Code off [ATQ0]
Using a directly connected PC or terminal, the TransAccess 200 MPU must first be set to operate at the
same speed as the modem that it will be connected to:
Select MPU from the main menu screen
From the drop-down menu, select Configuration
Select the baud rate of the modem
Press Esc to return to the top-level menu. This prevents the TransAccess 200 MPU Module
from initially streaming data back to the modem when it is connected (this prevents the
MPU Module from accidentally hanging up the modem immediately after it answers).
Disconnect the local User Interface Device from the MPU Module and connect the
modem to the MPU Module.
The connection between the modem and the front panel USI jack on the MPU Module should be made
with the Oasys-supplied cable (815-00055-XXX). This cable is equivalent to the 815-00011-XXX cable
plus a "null modem". If the TransAccess 200 is equipped with redundant MPUs, the cable may be
connected to either MPU Module.
Turn on the PC and wait for the Windows operating system to boot up.
The conventions used in section 4.3.1 above apply to detailed procedures below:
Launch the Hyper Terminal application:

• Click the START button.
• Select: Programs> Accessories> (98) Communications> Hyper Terminal
• Double click on Hypertrm.exe
The first time Hyper Terminal is executed, a Local Information box will appear.
Enter a telephone area code under What area (or city) code are you in now?
Click Close
NOTE - This box will not appear in the future.
The Connection Description box should appear. If it does not, click File New connection
Under Enter a name and choose an icon for the connection

Type “EXMUX Remote” or any meaningful name.
Select any icon.
Click OK
The (95) Phone Number box or (98) Connect To box appears in place of the Connection Description box.
TA-200 OP
8/29/03 4-3
Under Connect Using choose the modem installed in the PC
Enter the Area Code and Phone Number of the telephone line attached to the modem at the
TransAccess 200 location.
Click OK
The Connect box appears in place of the previous box.
Adjust the Dialing Properties as necessary.

Click Dial
The PC modem should dial the remote modem.

After the far-end modem answers, the blank terminal screen should be displayed.
Maximize the screen by clicking the box in the upper right corner.
Press [CTRL + R], if necessary, to refresh the screen.
4.3.3 Connect the TransAccess 200 to the Network
If the TransAccess 200 is to be managed remotely, connect a Customer-provided standard Category 5
Unshielded Twisted Pair (UTP) cable terminated with a modular connector to the RJ45 jack located near
the rear of left side of the TransAccess 200 shelf. The other end of this cable should be connected to a
10Base-T Ethernet access point on the Internet Protocol (IP) network used by the SNMP, TL1, Telnet, or
Web Browser platforms. Refer to Chapter 6 on how to configure the Ethernet port.
4.4 Backup and Restore TransAccess 200 Database
The current MPU configuration data can be stored remotely and later used to restore a system during a
disaster recovery scenario. Three means of backup and restore are available: via Telnet (TFTP), via Web
Browser, or via the Craft Port (using transmit and send from a VT100 terminal).
4.4.1 Database Management via Telnet
To backup the TransAccess 200 database using telnet, login to the TransAccess 200 system. Access the
SYSTEM/DOWNLOAD menu and select TFTP Loader Mode (see Section 4.6.1.3 for more information).
Using the TFTP Client software supplied on the TransAccess 200 CDROM (other TFTP Client software
packages may also be used) enter the settings shown in the example in Figure 4-1 below.
Figure 4-1: TFTP Configuration Backup
Enter the following into each location:
TA-200 OP
8/29/03 4-4
TFTP Server - enter the TransAccess 200 IP address
Operation - Download
Format - Binary
REMOTE FILE: sysconf.bin
LOCAL FILE: choose a Directory Path and Backup Filename
Select Download Now… to backup the TransAccess 200 database.
To restore the TransAccess 200 database via telnet, first login to the TransAccess 200 system. Access the
SYSTEM/DOWNLOAD menu and select TFTP Loader Mode (see Section 4.6.1.3 for more information).
Using the TFTP Client software supplied on the TransAccess 200 CDROM (other TFTP Client software
packages may also be used) enter the settings shown in the example in Figure 4-2 below.
Figure 4-2: TFTP Configuration Restore
TFTP Server – enter the TransAccess 200 IP address

Operation - Upload
Format - Binary
LOCAL FILE: select the Directory Path and Filename to restore
REMOTE FILE: sysconf.bin
Select Upload Now… to restore the TransAccess 200 database.

4.4.2 Database Management via Web Browser
See Section 9.3.5 and 9.3.6 for information about this feature.
4.4.3 Database Management via Front Panel RS232 Port (VT100)
To backup the TransAccess 200 database using a VT100 terminal, first login to the EXchange Mux
system. From the System Menu, select Download/Backup. Use the Receive command from the VT100
terminal, select the configuration file path\filename, and select 1K Xmodem to transfer the database from
the TransAccess 200.
To restore the TransAccess 200 database using a VT100 terminal, first login to the EXchange Mux
system. From the System Menu, select Download/Restore. Use the Send command from the VT100
TA-200 OP
8/29/03 4-5
terminal, select the configuration file, and configure for 1K Xmodem to transfer the database to the
TransAccess 200.
4.5 TransAccess 200 Initialization
All installed MPU and Service Modules are configured with default settings when the TransAccess 200 is
powered up for the first time, regardless of whether or not a user interface device is connected. The
Service Module default parameters are stored on the MPU module and downloaded at power up.
Once the TransAccess 200 has been powered up, new modules can only be configured using the User
Interface Device, SNMP, Telnet, TL1, or Web Browser.
Figure 4-3: EXM II (TA-200) Initial Screen After Login
At the initial screen, a login prompt will appear. The factory default login is admin. If the factory default
has been changed, enter the password corresponding to your security level.
4.6 Top-level Menu Screen
After hitting <RETURN> from the initial screen of the User Interface Device, three selections are
presented:
TA-200 OP
8/29/03 4-6
Figure 4-4: Top Level Menu
The diagram below shows the menu structure of the TransAccess 200 and PM13 service modules.
The diagram below shows the menu structure of the TransAccess 200 and PM13E service module.
The diagram below shows the menu structure of the TransAccess 200 and OMX3 service module.
The details of each menu are described in the sections below. Use the cursor keys on the keyboard and
press [ENTER] to select each item.
User Interface
Device
System Service MPU

Module
Alarm Summary Alarms PM13 Configuration
Passwords PM13E Alarm Summary

Performance
Download OMX3 Protection Switch
Perf. History
Backup/Restore PM13 Reset
Configure PM13E Disconnect Telnet

Logout
OMX3
Discover Diagnostics PM13
Line Config
Restore PM13E Loopback
Drop Config
Protection Switch
System Info OMX3 E1 Test
Reset/Reprogram Circuit Tags
Frame Monitor
Module Info
Restore User Interface
Device Front Panel Mon.
TA-200 OP
8/29/03 4-7
4.6.1 System
The System Menu consists of 7 selections as shown below in Figure 4-5:
Figure 4-5: System Menu
4.6.1.1 Alarm Summary

The Alarm Summary window shown below in Figure 4-6 is activated by selecting Alarm Summary from
the System Menu shown highlighted above in Figure 4-5. This screen provides a summary of all system
and module alarms.
Alarm status consists of the following information:
1. On-Line/Off-line/Protection Status
2. Minor Alarm/Major Alarm Status
3. Far-end Alarm Status
4. Maintenance Status
5. External Power Supply Alarm Status
6. Alarm Cut-Off (ACO) activation
The Online Status column displays the service status for each module. The choices are described below.
EMPTY – Indicates that there are no modules inserted into this card slot.
UNCONFG – Indicates that the module plugged into this slot is not configured. Use the Discover
command to configure the module.
MISSING – Indicates that a configured module has been removed from the card slot.
ONLINE – Indicates that there is a configured module installed in the card slot.
OFFLINE – Indicates that there is a configured protection module installed in the card slot, but it
is not currently protecting another module.
TA-200 OP
8/29/03 4-8
Figure 4-6: Alarm Summary Screen
4.6.1.2 Passwords and System Security

The TransAccess 200 utilizes a password login system for security. If enabled, operators may only access
the system using a pre-established password.
Typically, the system administrator may assign the same password to several operators. In doing so, he
assigns to the operators a common “user access level.” Every item within the TransAccess 200 menu has
associated with it its own “required access level.” An operator holding the same or greater access level
can only access these items. If the operator does not have sufficient user access for a menu item, the
menu will response with access denied. For instance an operator with access level 3 can invoke menu
items having required access levels 1, 2 or 3. But an operator with access level 1 can only invoke level 1
menu items. Level 4 operators have unrestricted access to all menu items.
To view the current password level, select Passwords and Show current level from the System menu as
shown in Figure 4-7.
Use of the password system is optional, and enabling and disabling passwords is a configurable
parameter. If the password system is disabled, then the operator is not prompted for a login password at
system startup, and all system configuration options are available to him or her.
TransAccess 200 comes factory-configured with a single password: admin, having level 4 access rights.
The password can and should be changed, but the password level must remain level 4 (the highest user
level) and cannot be deleted or changed to a different level.
A redundant MPU inserted next to an on-line MPU assumes all the passwords and the current system
level of the on-line MPU.
TA-200 OP
8/29/03 4-9
Figure 4-7: System Menu - Passwords
WARNING: Turin Networks strongly suggests that the system administrator change the factory default
password (admin) immediately upon system start-up. Leaving the default ‘admin’
password in place can be the source of a security risk.
Password Limits
• Number of user passwords: 15

• Legal characters: a-z, A-Z, 0-9 (password characters are case sensitive)
• Password length: 1 to 12 characters.
• Access levels: 1 (lowest) to 4 (highest)
Four security levels are built into the UID as shown below. Security levels are cumulative, that is each
higher level includes all levels below it.
1. LEVEL 1 – Passive viewing only of module information, configuration, alarm, and

performance screens.
2. LEVEL 2 – Intrusive diagnostic commands such as loopbacks, forced protection switching,
T1 tests. Does not include the authority to change any configuration settings that are retained
in non-volatile memory.
3. LEVEL 3 – Software download, MPU and Service Module configuration, default template
editing, discovery.
4. LEVEL 4 – Password and level assignment administration.
The UID is programmed initially with a factory default level 4 password. The user with level 4 access
will have the ability to add, delete, or change passwords at their convenience. A password can be
assigned to each user along with the access level for that user. Each password must be different from the
rest. It will be the responsibility of the level 4 user to assign and document each password.
TA-200 OP
8/29/03 4-10
If it’s decided that passwords are not necessary, the level 4 user may disable all passwords. When
disabled, subsequent password entry prompts will not be displayed at start-up. In this case, all users are
level 4 users.
NOTE: If the level 4 password is lost or forgotten, contact Turin Networks.
Figure 4-8 shows the system menu screen for the Administrator selection. Only users who login at level
4 have access to his menu.
Figure 4-8: Password Administrator Menu
Selecting (1) Redisplay Passwords from the System Menu refreshes the password assignments created by
the Level 4 user.
Selecting (2) Add a Password, allows new passwords to be made. Enter the password number (1 to 15) to
add a new password to the list. Up to 15 passwords can be stored at a time. One user with Level 4 access
can assign or modify passwords. However, the security level for password #1 can only be level 4 and
cannot be edited.
Selecting (3) Modify Password, allows password names to be changed.
Selecting (4) Delete a Password will prompt you to enter the ID number (2-15) for the password you want
to delete.
Selecting (5) Disable Passwords cancels the login prompt at the start of a session.
Disabling all passwords will disable the login prompt at start-up. Therefore, anyone connecting to the
TransAccess 200 will be given Level 4 security access. However, none of the defined login names will
be deleted from the password list.
TA-200 OP
8/29/03 4-11
Selecting (6) Enable Passwords allows the user to enable the password login entry at start-up.
Selecting (7) Restore Password Factory Defaults deletes all password entries and returns password #1 to
admin.
4.6.1.3 Download
The procedure to download new MPU program code, new MPU programmable gate array (FPGA) code
or PM13 programmable gate array code is described in this section. See Figure 4-9. If Passwords are
enabled, level 3 or 4 is required to perform Downloads. Passwords and System Security are explained in
Section 4.6.1.2 below.
Figure 4-9: Software Download Menu
The top-level screen on the user’s terminal should be displayed.
Select SYSTEM
From the menu, select DOWNLOAD
Select a type of code to download
The current version of the code will be displayed. Press [ENTER] to continue.
The system will respond with the prompt: Waiting for download…
A series of Cs will appear on the screen, indicating that the TransAccess 200 is expecting a
download. If the user waits more than 3 minutes to execute the transfer, the session will abort and
return to the top-level menu.
To initiate a download through the UID serial port:

Insert the Oasys-supplied CD-ROM into the appropriate drive.
From the top of the Hyper Terminal screen click Transfer, then click Send File
Select 1K Xmodem from the Protocol choices.
From the Send file box, click the Browse button.
TA-200 OP
8/29/03 4-12
Select the file to be downloaded using the Browse feature.
Click SEND
Upon completion, wait approximately 30 seconds for the MPU to reboot. Hit [ENTER] twice and enter
the password at the login prompt. Switch the MPU over the redundant module and repeat the download.
NOTE: If the MPU Loader program is updated, the MPU will reboot back into the loader
program after the MPU resets. The screen in Figure 4-9 will appear. Login and then press ‘q’
to quit. The MPU will then reboot into the system operation software.
To initiate a download through the Ethernet port (initiated via Telnet) see Figure 4-10:
Insert the Oasys-supplied CD-ROM into the appropriate drive.

From the Telnet screen, under the SYSTEM menu, select DOWNLOAD and TFTP loader mode.
Using your own TFTP Client program, input the System IP and the program filename and click on
SEND.
The file transfer will commence. Upon completion, wait approximately 30 seconds for the MPU to
reboot and then reconnect the telnet session and enter the password at the login prompt.
To abort a download via telnet, abort the download of the TFTP loader program. The MPU will have a
solid yellow LED. If the yellow LED is blinking, DO NOT REMOVE THE MPU as the program code
has been downloaded and is being copied into the MPU program memory. Reconnect the telnet session
to display the screen in Figure 4-11.
Figure 4-10: MPU Loader Prompt
Type in the password at the login prompt and then type ‘q’ to quit the loader program. The MPU will
then reboot. Reconnect the telnet session and enter the password at the login prompt.
TA-200 OP
8/29/03 4-13
`Figure 4-11: MPU Loader Prompt
4.6.1.3.1 Download Using TFTP Shareware Program

To download the TransAccess 200 software using the TFTP Client shareware program, first install the
software on your computer and then run the executable file. The screen in Figure 4-12 will appear.
Figure 4-12: TFTP Client Software Download Screen
Operation - Upload
Format - Binary
LOCAL FILE: select the file to download from the CDROM
REMOTE FILE: select one of the following software files
Selected Software to Download Remote File Entry Name CDROM File*
TA-200 OP
8/29/03 4-14
MPU Boot code mpub.odf boot60.odf
MPU Program code mpu.odf xmuxii70.odf
MPU Loader code mpul.odf mpul30.odf
MPU FPGA mpux.odf mpux90.odf
PM13 T3 FPGA pm13x1.odf pm13t340.odf
PM13 T1 FPGA pm13x2.odf pm13t130.odf
PM13E T3 FPGA pm13ex1.odf pm13et330.odf
PM13E T1 FPGA pm13ex2.odf pm13et120.odf
OMX3 FPGA omx3x.odf omx3x70.odf
* Revisions may change over time. The revision is indicated at the end of the file name.
When all the fields are entered, click ‘Upload Now’ to transfer the file to the TransAccess 200 MPU
module. After all the files are updated on the MPU, switch to the redundant MPU and download the same
files to it. If FPGA files have been updated, use the Discover command under the system menu to
transfer the new s/w file to the service modules. This software transfer will disrupt traffic for
approximately 5 seconds.
4.6.1.4 Backup/Restore Configuration Database
See Section 4.4 for information.
4.6.1.5 Logout
This feature serves dual purposes: First, if password security is enabled, logout will exit the currently
logged privilege level. The second purpose is to place the MPU module into ‘Auto-baud’ mode. Once
you enter ‘Y’ at the logout prompt you can disconnect the UID from the MPU module. When another
user connects their UID to the MPU, the MPU will wait for two RETURN key entries and will then allow
the new user to login, or will go directly to the top-level menu if password security is disabled.
If the user does not logout, the MPU will remain at its current baud rate setting. Any users connecting to
the MPU will need to set their UID to the same baud rate. If the MPU baud rate is not known, the MPUs
must be reset to return to auto baud mode.
4.6.1.6 Discover
This feature commands the MPU module to discover all the modules in the shelf. Those modules that had
been previously unconfigured will be downloaded with their default configuration. Any physically
missing modules will be deleted from the logical installed equipment list. This will not affect the
operation of any of the modules already configured in the shelf.
4.6.1.7 Restore
This selection removes all active diagnostic functions (loopbacks, protection switches, T1 tests, etc.) for
all modules in the TransAccess 200 shelf.
4.6.1.8 System Info
The System Info screen displays the system description name, front panel baud rate, IP address, IP Mac
address, IP gateway address, and software revision levels currently stored in the MPU modules. The
software revision levels displayed on this screen reflect what is stored in the MPU but not necessarily
what has been downloaded to the service modules. Check the Module Information screen to view
software levels that the service modules are running with. If a difference is detected, use the ‘Discover’
command to update the system.
TA-200 OP
8/29/03 4-15
NOTE: If the FPGA software is different between the service module and MPU, a ‘Discover’
command will cause traffic to go down for approximately 5 seconds while the service module is
updated.
Figure 4-13: System Information Screen

4.6.1.9 Module Info
The Module Info command allows the user to view the software, firmware, and assembly revision levels
of each of the MPU and Service Modules in the shelf. Software Revision refers to the MPU
microprocessor embedded software. Firmware Revision refers to the programmable gate array firmware.
When selecting this feature, the following table is displayed.
Figure 4-14: TransAccess 200 Module Information Summary
TA-200 OP
8/29/03 4-16
4.6.2 Service Module – PM13, PM13+, and M13-T3
The Service Module Menu consists of five sections, Alarms, Performance, Performance History,
Configure, and Diagnostic menus. Under each subsection, a module selection is listed. Hit [Enter] while
the cursor is on the service module to select an alarm or performance screen. If trying to enter configure
or diagnostic screens, select the item from the sub-menu under the particular service module type.
PM13 menus support PM13, PM13+, and M13-T3 modules. The PM13 module is the original module.
PM13+ added the capability to program individual T1 tributaries for either AMI or B8ZS (the PM13
module provided this programming as a group of 7 T1 tributaries). The M13-T3 is only programmed for
T3. That is, STS-1 is not supported.
Figure 4-15 below displays the PM13 service module Alarm Menu.

The Alarm Summary table summarizes the Input and Board Alarms for each of the PM13 service
modules. Place the cursor on PM13 and hit [Enter] to open the PM13 alarm summary screen shown in
Figure 4-16.
Figure 4-15: PM13 Module Menu
Type
Indicates which service module type is installed.
State
TA-200 OP
8/29/03 4-17
Figure 4-16: PM13 Service Module Alarm Summary
To pause/update the display press [Û].

To return to the Main Menu press [ESC].
To enter the T1, VT1.5, or T3 alarm details screen, move the cursor to the field and press [Enter].
A description of each field is shown below:
Board Alarm:
BRD ALM – Board Alarm indicates that there has been a hardware failure detected. The PM13 Module
will transmit a T3 AIS (framed 1010 pattern) or an STS-1 Yellow Alarm if possible. A Protection
Module may protect it.
T1 Alarm:
T1 ALM – Indicates that an alarm has been detected at the T1 level. Move the cursor to the ‘X’ in this
column to view the T1 Alarm Details screen shown in Figure 4-18.
Line Side Alarms

Line side alarms are broken into three categories, common alarms for both T3 and STS-1 operation,
alarms for T3 operation only, and alarms for STS-1 operation only.
TA-200 OP
8/29/03 4-18
Common Alarms:
LOS – Loss of Signal indicates that the incoming T3 or STS-1 signal is missing. When this event is
declared, T1 AIS will be transmitted out all 28 T1 ports.
OOF – Out-of-Frame indicates that the incoming T3 or STS-1 framing is not detected. When this event is
declared, T1 AIS will be transmitted out all 28 T1 ports.
AIS – The Alarm Indication Signal (AIS) indicates that a T3 or STS-1 failure (AIS – bits 5 and 6 of the
H1 byte) has occurred upstream from the TransAccess 200. When this event is detected, T1 AIS will be
transmitted out all 28 T1 ports.
NO OUT – This alarm indicates that the outgoing T3 or STS-1 signal has failed.
T3 Operation Alarms:
To view the details of these T3 alarms, move the cursor over the field and hit [Enter]. The T3 Alarm
Details window in Figure 4-19 will appear.
T2 OOF – T2 Out-of-Frame indicates that at least one of the T2 tributaries within the incoming T3 signal
has lost its frame pattern. When this event is detected, the T1 signals associated with the failed T2
tributaries will have T1 AIS (all 1’s) inserted into the VT1.5 tributaries within the outgoing STS-1 signal.
T3X BIT – The received T3 X-bit is used to identify a T3 far-end alarm. When the alarm is detected, the
T3 transmit path to the far-end equipment has failed.
T2X BIT – The receive T2 X-bit is used to identify a T2 far-end alarm. When the alarm is detected, at
least one of the seven transmit T2 tributaries has failed towards the far-end equipment.
STS-1 Operation Alarms:
LOP – Loss of Pointer indicates that the PM13 module is unable to locate the start of the Synchronous
Payload Envelope (SPE) within the STS-1 signal. When this event is declared, T1 AIS will be inserted
into each of the outgoing T1 tributaries within the outgoing T3 signal.
SLM – A Signal Label Mismatch alarm indicates that there is a mismatch between the signal type
generated by the far-end equipment and the TransAccess 200.
VT ALM – This is a VT1.5 alarm summary indicator. For details on the specific VT1.5 alarm detected,
you should view the VT1.5 Alarm Summary screen by pressing [^V]. To view the VT1.5 alarm
generated, place the cursor on the ‘X’ and hit [Enter]. The VT1.5 Alarm Details screen in Figure 4-17
will appear.
4.6.2.2 VT1.5 Alarm Summary

The VT1.5 Alarm Summary table summarizes the VT1.5 alarms for each of the PM13 service modules.
Figure 4-17 shows the VT1.5 Detailed Alarm screen. The 28 tributaries in the chart are shown as Group
and VT (n,n).
NOTE: If STS-1 LOS, LOF, LOP, or AIS is detected, VT1.5 alarms will not be reported.
LOP – Loss-of-pointer is based on bit-8 of the V5 byte of the incoming SONET signal.
TA-200 OP
8/29/03 4-19
AIS – Alarm Indication Signal indicates that a VT1.5 signal failure has occurred upstream. The alarm is
based on detecting an all 1’s in the V1 and V2 bytes for 3 consecutive superframes of the incoming
SONET signal.
RDI – Remote Defect Indicator is detected from bits 5-8 of the incoming G1 byte. RDI indicates that the
far-end equipment has detected an error on its incoming VT1.5 tributary.
Errored Seconds (ES) are based on a BIP-3 error in a one second interval. Severely Errored Seconds
(SES) indicate that 5 or more BIP-3 errors occurred in a one second interval.
Figure 4-17: VT1.5 Alarm Details
As the cursor is moved down under each tributary, the T1 Circuit Tag mapped to that VT1.5 tributary is
displayed in the upper right hand corner of the screen.
4.6.2.3 T1 Alarm Details

The T1 Alarm Summary table summarizes the T1 alarms for each of the PM13 service modules. Figure
4-18 shows the T1 Alarm Details alarm screen.
T1 Circuit Tags are displayed for each tributary. To enter the Circuit Tag information, select the Circuit
Tag screen under the PM13 Configuration Menu.
LOS – Loss-of-signal for each of the 28 T1 tributaries.
AIS – Alarm Indication Signal indicates that a T1 signal failure has occurred upstream. The alarm is
based on detecting 175 consecutive 1’s on the incoming T1 signal.
BPV – This indicates the total number of bipolar violations detected. The count will stop at 32,767.
TA-200 OP
8/29/03 4-20
NOTE: BPV error counts will reset to 0 when LOS is detected on a T1 tributary.
Figure 4-18: T1 Alarm Details

To clear all the BPV counters press [Â].
To clear the BPV counters on a selected tributary, place the cursor on the tributary and press [^T].
4.6.2.4 PM13 T3 Alarm Details

The T3 Alarm Details table summarizes the T3 and T2 alarms for each of the PM13 service modules.
Figure 4-19 shows the alarm screen. An ‘X’ will appear under the detected T3 or T2 alarm for each
service module. If a T3 LOS, AIS, or OOF is detected, the T2 alarms will not be displayed.
TA-200 OP
8/29/03 4-21
To pause/update the display press [Û]

To return to the Main Menu press [ESC]
4.6.2.5 PM13 Performance Summary

The Performance Summary is accessed from the menu in Figure 4-20. The Performance Summary table
in Figure 4-21 displays the framing format and current bit error rate for each of PM13 modules. An
example of the display on the User Interface Device is shown below.
Module State:
TA-200 OP
8/29/03 4-22
Figure 4-20: PM13 Performance Selection Menu
Figure 4-21: PM13 Service Module Performance Summary

To clear all the errored counters for all slots press [Â]
To clear all the errored counters for a particular slot press [^T]
TA-200 OP
8/29/03 4-23
T3/STS-1 Errored Second Reporting
The maximum count of the errored counters is 65,535 seconds. It the count reaches the maximum it will
be held until it is manually cleared. The following describes each alarm field. If the PM13 module is
programmed for T3, the STS-1 fields will be left blank and if configured for STS-1, the T3 fields will be
left blank.
T3/B2 SES – The Severely Errored Counter will increment by one for each second that contains 44 T3
path bit errors, 13 STS-1 B2 errors, detection of loss-of-signal, or detection of out-of-frame.
T3 FRAME – Indicates the current T3 framing pattern (M13 or C-bit). This field cannot be modified. If
the PM13 module is configure for STS-1, the four T3 fields will be left blank.
T3 PARITY – The parity errored seconds will increment every time a T3 P-bit is detected in error for a
one-second interval.
T3 PATH – The T3 path count is only available for C-bit parity T3 framing. The CP-bits in the T3
overhead are used to detect a bit error in the T3 path. The path count will increment every time a CP-bit
is detected in error during a one-second interval.
T3 FAR-END – The T3 far-end block error (FEBE) count is only available for C-bit parity T3 framing.
The far-end block error count will increment every time a FEBE-bit is detected in error for a one second
period. Far-End Block Errors indicate that the far-end equipment is detecting bit errors on its incoming
T3 signal.
STS-1 B1 – The errored second count will increment every time a STS-1 B1 byte is detected in error for a
one second interval. The B1 byte is part of the STS-1 section overhead.
one second interval. The B2 byte is part of the STS-1 line overhead.
4.6.2.6 PM13 Performance History

Errored Second (ES) and Severely Errored Second (SES) statistics are kept for a 24-hour period for the
T3/STS-1 Line, VT/VC tributaries, or T1 drop interfaces. The PM13 performance history can be selected
via the menu shown in Figure 4-22.
TA-200 OP
8/29/03 4-24
Figure 4-22: PM13 Performance History Menu
4.6.2.6.1 PM13 T3/STS-1 Line Performance History

Selecting the PM13 Line Performance History menu brings up the screen in Figure 4-23.
Figure 4-23: PM13 Line Performance History
TA-200 OP
8/29/03 4-25
[Â] Clears the 96 15-minute errors and 24-hour errors for the selected slot.
[Ô] Allows you to enter a slot number to move to. When the cursor is on the SLOT field,
pressing the [SPACE] bar will change to the next on-line PM13 slot number.
[Î] Allows you to enter the 15-minute interval you wish to view. Enter a ‘1’ to view the most
recent 15-minute interval.
[Ê] Automatically selects the next 15-minute interval containing errors.
T3 P-BIT – The parity errored seconds will increment every time a T3 P-bit is detected in error for a one-
second interval. The Severely Errored Counter will increment by one for each second that contains 44 T3
parity bit errors, detection of loss-of-signal, or detection of out-of-frame.
T3 CP-BIT – The T3 path count is only available for C-bit parity T3 framing. The CP-bits in the T3
is detected in error during a one-second interval. The Severely Errored Counter will increment by one for
each second that contains 44 T3 path bit errors, detection of loss-of-signal, or detection of out-of-frame.
T3 FEBE – The T3 far-end block error (FEBE) count is only available for C-bit parity T3 framing. The
far-end block error count will increment every time a FEBE-bit is detected in error for a one second
T3 signal. The Severely Errored Counter will increment by one for each second that contains 44 T3
FEBE bit errors, detection of loss-of-signal, or detection of out-of-frame.
one second interval. The B1 byte is part of the STS-1 section overhead. The Severely Errored Counter
will increment by one for each second that contains 32 STS-1 B1 errors, detection of loss-of-signal, or
detection of out-of-frame.
one second interval. The B2 byte is part of the STS-1 line overhead. The Severely Errored Counter will
increment by one for each second that contains 13 STS-1 B2 errors, detection of loss-of-signal, or
4.6.2.6.2 PM13 VT/VC Performance History

Selecting the PM13 VT/VC Performance History menu brings up the screen in Figure 4-24. The screen
displays the VT1.5 alarms for each tributary of the selected PM13 slot. Errored Seconds (ES) are based
on a BIP-3 error in a one second interval. Severely Errored Seconds (SES) indicate that 5 or more BIP-3
errors occurred in a one second interval.
TA-200 OP
8/29/03 4-26
Figure 4-24: PM13 VT/VC Performance History
[Â] Clears the 96 15-minute errors and 24-hour errors for the selected tributary. To clear the
errors, place the cursor on the selected tributary.
[^C] Clears the VT/VC errors for all 28 tributaries.
4.6.2.6.3 PM13 T1 Drop Performance History

Selecting the PM13 T1 Drop Performance History menu brings up the screen in Figure 4-25. An errored
second indicates that a T1 bipolar violation has occurred within a one-second interval. A severely errored
second indicates that at least 320 T1 bipolar violations have occurred within a one-second interval.
TA-200 OP
8/29/03 4-27
Figure 4-25: PM13 T1 Drop Performance History
[^C] Clears the drop errors for all 28 tributaries.
4.6.2.7 PM13 Configuration – T3/STS-1 Line

The Line Side configuration menu provides settings that control the signals from the T3/STS-1 port of the
PM13 module. Figure 4-27 displays the current Line Side configuration of all the service modules and
allows each configuration item to be modified using the cursor keys.
TA-200 OP
8/29/03 4-28
Figure 4-26: PM13 Line Configuration Menu Selection
Entering Configuration Changes

To change a configuration setting and download the change to the PM13 module, first highlight the field
using the cursor keys and press the [SPACE] bar on the keyboard to toggle through the selections. [^S]
will save the configuration change on the MPU and download that change to the module.
To set all the PM13 modules to their default value, press [^T]. Once the default values are set, press [^S]
to save and download the changes. The default values are displayed on the bottom line of the menu and
can also be edited and stored so future modules will be initially configured as desired.
Configuration Options
The configurable items and their options for the PM13 Line Side are listed below.
Type
This feature provides the ability to program the PM13 for either T3 or STS-1 operation.
Protection Switch
This feature provides the ability to enable or disable protection switching for a particular PM13 module.
There are two choices for enabling protection switching, a) protection switching including T1 drop alarms
(ENAB LINE/DROP) or b) protection switching not including T1 drop alarms (ENAB LINE ONLY).
Selecting DISABLE ALL prevents protection switching from occurring unless the module is unplugged
or the power supply fails.
Hold-off
The MPU will detect a PM13 alarm within 50 ms. This feature delays PM13 protection switching after
the MPU detects the alarm. Protection switching hold-off can be programmed for NONE (switch
immediately), 50ms, 100ms, 500ms, 1 second, 2 seconds, or 5 seconds.
LBO
• <225 – Outgoing T3 Line Build Out selection for cable lengths less than or equal to 225 feet.
• >225 – Outgoing T3 Line Build Out selection for cable lengths greater than to 225 feet.
TA-200 OP
8/29/03 4-29
Figure 4-27: PM13 Service Module Line Side Configuration
Timing Mode
• LOOP – The T3 or STS-1 clock will be set for Loop Timing. That is, the Transmit Clock
will be timed from the Receive Clock.
• INTERNAL – The Transmit T3 or STS-1 clock will be timed to the PM13 Module’s local
oscillator.
T1/VT15 Mapping – (Selectable only when configured for STS-1 operation)

See Table 4-1 and Table 4-2.
• TRANSPARENT – T1 circuits are mapped into VT1.5 tributaries in accordance Telcordia

specification GR-253-CORE.
• INTERLEAVED – T1 circuits are mapped sequentially into VT1.5 tributaries.
TA-200 OP
8/29/03 4-30
TABLE 4-1: Interleaved Mapping
T1 Drop Port VT Group#, VT# STS-1 Frame Columns
1 1, 1 2, 31, 60
2 1, 2 9, 38, 67
3 1, 3 16, 45, 74
4 1, 4 23, 52, 81
5 2, 1 3, 32, 61
6 2, 2 10, 39, 68
7 2, 3 17, 46, 75
8 2, 4 24, 53, 82
9 3, 1 4, 33, 62
10 3, 2 11, 40, 69
11 3, 3 18, 47, 76
12 3, 4 25, 54, 83
13 4, 1 5, 34, 63
14 4, 2 12, 41, 70
15 4, 3 19, 48, 77
16 4, 4 26, 55, 84
17 5, 1 6, 35, 64
18 5, 2 13, 42, 71
19 5, 3 20, 49, 78
20 5, 4 27, 56, 85
21 6, 1 7, 36, 65
22 6, 2 14, 43, 72
23 6, 3 21, 50, 79
24 6, 4 28, 57, 86
25 7, 1 8, 37, 66
26 7, 2 15, 44, 73
27 7, 3 22, 51, 80
28 7, 4 29, 58, 87
TA-200 OP
8/29/03 4-31
TABLE 4-2: Transparent Mapping
T1 Drop Port VT Group#, VT# STS-1 Frame Columns
1 1, 1 2, 31, 60
2 2, 1 3, 32, 61
3 3, 1 4, 33, 62
4 4, 1 5, 34, 63
5 5, 1 6, 35, 64
6 6, 1 7, 36, 65
7 7, 1 8, 37, 66
8 1, 2 9, 38, 67
9 2, 2 10, 39, 68
10 3, 2 11, 40, 69
11 4, 2 12, 41, 70
12 5, 2 13, 42, 71
13 6, 2 14, 43, 72
14 7, 2 15, 44, 73
15 1, 3 16, 45, 74
16 2, 3 17, 46, 75
17 3, 3 18, 47, 76
18 4, 3 19, 48, 77
19 5, 3 20, 49, 78
20 6, 3 21, 50, 79
21 7, 3 22, 51, 80
22 1, 4 23, 52, 81
23 2, 4 24, 53, 82
24 3, 4 25, 54, 83
25 4, 4 26, 55, 84
26 5, 4 27, 56, 85
27 6, 4 28, 57, 86
28 7, 4 29, 58, 87
4.6.2.8 Configuration – T1 Drop LBO

Figure 4-28 displays the Line Build Out (LBO) configuration screen for the PM13 T1 ports. The
configurable items and their options for the PM13 Drop Side are listed below.
All 28 T1 tributaries can be individually programmed for different cable line lengths. The six selectable
cable lengths are:
0 – Port disabled (transmitter turned off and alarms disabled)

1 – 0 to 133’ of cable
2 – 133’ to 266’ of cable
3 – 266’ to 399’ of cable
4 – 399’ to 533’ of cable
5 – 533’ to 655’ of cable
6 – 0 to 133’ of cable but alarms disabled (for test purposes only)
TA-200 OP
8/29/03 4-32
If the PM13 module is configured for T3 operation and a group of T1 tributaries are all disabled within a
T2 group, the T2 alarms for those groups will be disabled.
Figure 4-28: PM13 Service Module Drop Side LBO Configuration
Short-cut Keys
The keys [0], [1], [2], [3], [4], [5], [6] can be used to simultaneously select the LBO for each pair of T1
tributaries. To set a common LBO setting for a module pair, simply place the cursor on the selected pair
of slots and then select the LBO setting. Make the selection (0-6) and then enter [^S] to save and
download the changes to the TransAccess 200 modules.
4.6.2.9 Configuration – T1 Line Code

Figure 4-29 displays the Line Code configuration screen for the PM13 T1 ports. The configurable items
and their options for the PM13 Drop Side are listed below.
There are currently two vintages of PM13 modules. For the original version, the T1 tributaries for each
redundant pair of modules can be programmed for either B8ZS (B) or AMI (A) encoding in groups of 7
tributaries. Thus, there are four programmable fields for each standard PM13 module pair. The
selections are made as follows.
1st Field – T1’s 1-7

2nd Field – T1’s 8-14
3rd Field – T1’s 15-21
4th Field – T1’s 22-28
NOTE: These selections may affect the operation of the Front Panel Monitor feature. If a mix of B8ZS
and AMI is programmed on a module pair, only those T1 tributaries programmed with the same line
coding, beginning at T1 #1 will function.
TA-200 OP
8/29/03 4-33
With the PM13+ module or M13-T3 module, line coding can be performed on the individual T1
tributaries.
Figure 4-29: PM13 Service Module Drop Side Line Code Configuration
4.6.2.10 T1 In-band Loopback Configuration

PM13+ and M13-T3 modules have the ability to generate and react to T1 In-band loop-up/loop-down
commands via the 28 T1 drop ports. Each T1 tributary can be enabled, by groups of 7 T1s, to activate
loopbacks towards the drop port. Activation and deactivation patterns can also be programmed for groups
of 7 T1s. If a valid loop-up signal is received for 5 seconds, the incoming T1 signal will be looped back
out the outgoing T1 line. When an in-band loopback command is activated, the activation pattern is sent
down the T1 line for 5.1 seconds. During this period, live T1 traffic on the tributary is disrupted.
Figure 4-30 shows the T1 In-band Loopback Configuration screen.
TA-200 OP
8/29/03 4-34
Figure 4-30: T1 In-band Loopback Configuration Screen
4.6.2.11 Circuit Tags

Circuit Tag entries are provided for each T1 tributary per module. In addition, a Circuit Tag can be
entered for each T3/STS-1 port. Circuit Tag entries are optional and are only provided to help determine
the identification of failed facilities.
Figure 4-31: PM13 Circuit Tag
TA-200 OP
8/29/03 4-35
Figure 4-31 shows the Circuit Tag entry screen. Each Circuit Tag can have up to 15 characters. Once
the Circuit Tags are stored, they will then be displayed on the T1 Alarm Detail screen and VT1.5 Alarm
Detail screen (STS-1 configuration only) for reference. In addition, the LBO and Line Code can be set
from this screen. Any changes made will also be reflected on the Drop LBO and Drop Line Code
configuration screens.
4.6.2.12 PM13 Diagnostics

PM13 diagnostics consist of Loopbacks, including Loop-up/Loop-down, T1 Test Pattern Generator and
Receiver, T1 Frame Monitor, and a T1 Monitor at the PM13 front panel. To select each of these features,
place the cursor on the field and hit the [Enter] key.
Figure 4-32: PM13 Diagnostic Menu Selection

4.6.2.12.1 Loopbacks
Selecting ‘loopback’ brings up the menu shown in Figure 4-33. All loopbacks are bridged. That is, the
receive signal is sent to the far-end while the transmit signal is also connected to the receive signal.
Loopback Indicators
L – Indicates a local T1 loopback is enabled on the T1 tributary
F – Indicates a far-end C-bit loopback request has been transmitted and is active on the outgoing
T1 tributary (will not activate if a remote C-bit loopback request has been received and is
active). This is only available if the PM13 is configured for T3 operation.
R – Indicates either a far-end C-bit loopback request (Line side) or T1 loop-up command (drop
side) has been received and is active on the T1 tributary. C-bit loopbacks are only
available if the PM13 is configured for T3 operation.
l – Indicates that a local loopback is ready to be initiated (will not activate if a remote C-bit
TA-200 OP
8/29/03 4-36
loopback has been received and is active)
f – Indicates that a far-end C-bit loopback is ready to be transmitted. This is only available if the
PM13 is configured for T3 operation.
a – Enables a T1 tributary to send an Inband Loop-up command to the far-end T1 port.
A – Indicates that an Inband Loop-up command has been sent and is active on the farend T1 port.
d - Enables a T1 tributary to send an Inband Loop-down command to the far-end T1 port.
To toggle the selected field to the next state, press [SPACE]. T3 and STS-1 line loopbacks activate in this
manner.
Figure 4-33: PM13 Service Module Loopback Control
To select a new slot (1-14) either move the cursor to the top line and hit the [SPACE] bar to toggle
between 14 card slots (the cursor must be in the far left column in order to move it to the top field), or
enter [Ô] to enter the specific PM13 card slot. A prompt will appear saying “Enter new slot:”. Enter the
PM13 slot number.
To download and activate the loopback request, enter [^S].
To redraw the screen, enter [^R].
To return to the main menu, enter [ESC].
To enable all 28 T1 loopbacks towards the T3 or STS-1 port, enter [^L].
To enable a far-end T1 loopback request on all 28 T1 tributaries towards the T3 port, enter [^F].
To enable all local T1 loopbacks, enter [^D].
To clear all 28 T1 loopbacks, enter [^T].
To clear all 28 T1 loopbacks towards the drop ports, enter [^W].
To enable all In-band loop-ups from the 28 drop ports, enter [Â].
To enable each loopback individually, place the cursor on the particular T1 port and press [SPACE].
TA-200 OP
8/29/03 4-37
NOTE: T1 loopbacks towards a T3 or STS-1 tributary will not be active if a T1 Test signal is generated
on the same tributary.
4.6.2.12.2 T1 Test
This feature provides the capability to non-intrusively monitor any T1 signal dropping from either the
incoming T3/STS-1 signal or incoming T1 signal. If the PM13 is programmed for STS-1 operation a
selection of 4 test signals can be used to intrusively inject into any T1 towards the T3/STS-1 port or 28 T1
drop ports. If the PM13 is programmed for T3 operation, only a QRSS pattern is available. Figures 4-33
and 4-34 show the T1 Test Configuration screens with T3 and STS-1 respectively. If the selected PM13
is programmed for STS-1 operation, the tributaries are selected by VT group and VT tributary number.
To select the PM13 module, highlight the SLOT number and press the space bar to toggle to the next
PM13 slot or press Ô to enter the specific slot number.
The Test Pattern can be inverted or non-inverted. Move the cursor over to PATTERN POLARITY to
select between a Normal (non-inverted) and Inverted test pattern.
To select the Test Generator Pattern, highlight the PATTERN field and press the space bar to selection
one of the 4 test pattern options (STS-1 mode only): QRSS, 2E15-1, 2E20-1, or 2E23-1. Select a Framed
or Unframed pattern.
NOTE: If the PM13 is configured for T3 operation, only a QRSS pattern is available.
Figure 4-34: PM13 (Configured for T3) T1 Test Configuration Screen
To inject a pattern into a tributary, move the cursor and select the direction in which to inject the test
signal. If the PM13 is configured for T3, 28 T1 tributaries will be displayed as in Figure 4-34. If the
PM13 is configured for STS-1, the Group and VT will be displayed as in Figure 4-35. Press the space
bar to select the tributary either towards the T3/STS-1 or T1 output or press ^X to select all the generator
tributaries. A lower case ‘x’ will appear. Press ^S to save the entry and to initiate the T1 monitor. The
TA-200 OP
8/29/03 4-38
lower case ‘x’ will change to an upper case ‘X’. Multiple tributaries can be selected simultaneously in
one direction only.
^Y will clear all the selections from the T1 Generator. Press ^S to save and download the cleared entries.
All tributary selections must be removed before the direction of the T1 Generator or T1 Receiver can be
toggled.
One tributary can be monitored at a time. Before selecting the tributary to monitor, first select a T1
pattern, framing, and receive direction. To select the tributary to monitor, move the cursor under the
tributary (T3 or T1 drop) or Group/VT (STS-1) number and press the space bar. An ‘X’ will appear.
Press ^S to save the entry and to initiate the T1 monitor. The RECEIVED ERRORS will display the
number of T1 bit errors received (up to 65,535 errors). To clear the errors, enter ^C.
Figure 4-35: PM13 (Configured for STS-1) T1 Test Configuration Screen
NOTE: WHEN THE T1 TEST GENERATOR OR RECEIVER IS ENABLED ON THE PM13

MODULE, THE PM13 STATUS LED WILL TURN YELLOW.
NOTE: T1 LOOPBACKS TOWARD A T3 OR STS-1 TRIBUTARY WILL NOT BE ACTIVE IF A

T1 TEST SIGNAL IS GENERATED ON THE SAME TRIBUTARY.
4.6.2.12.3 T1 Frame Monitor
The PM13 module has the ability to monitor the framing of any incoming T1 signals from the drop side.
Figure 4-36 shows the T1 Frame Monitor screen.
For each module, select a T1 tributary to monitor in the T1 TRIB column. Both the on-line and off-line
PM13 modules can monitor an incoming T1 at the same time. Once a T1 tributary is selected, the
FRAMING column will automatically display the type of framing, namely D4, ESF, or OOF (Out-Of-
Frame) that has been detected.
TA-200 OP
8/29/03 4-39
The errored counts are incremented in the following fashion:
D4 Framing ESF Framing

Errored Seconds Any Frame Bit Error in 1 second CRC error in 1 second
Severely Errored Seconds 320 Frame Bit Errors/LOS/OOF 320 CRC errors/LOS/OOF
Figure 4-36: PM13 T1 Frame Monitor
To Toggle the selection, move the cursor to the appropriate card slot and press [SPACE]
To end monitoring of the selected card slot, press [^C]
To save and download the changes, press [^S]
To clear the errors on the selected slot, press [Ê]
To manually select a new tributary, press [^T]
To pause/update the display press [^R]
To end monitoring on all card slots, press [Â]
To clear all errored counters, press [^B]
To enable/disable automatic updates, press [Û]
4.6.2.12.4 T1 Front Panel Monitor
The PM13 module has a bantam jack on the front panel that provides a T1 monitor point for any of the
incoming T1 tributaries from the drop ports. Figure 4-37 shows the Front Panel T1 Monitor screen.
For each module, simply select a T1 tributary to monitor. Selections can be made for the incoming T1s
from the drop ports. Once the T1 tributary is selected, the DSX-1 signal from the selected tributary will
be transmitted out the front bantam connector. Monitoring a T1 will not disrupt the live traffic on the
selected tributary.
When a T1 tributary is selected and downloaded, the PM13 module’s status LED will turn yellow and a
minor alarm will be generated indicating that a maintenance condition is active.
TA-200 OP
8/29/03 4-40
Figure 4-37: PM13 Front Panel T1 Monitor
To select a new service module slot, press [Ô]
To end monitoring of the selected card slot, press [^C]
4.6.3 Service Module Diagnostics

The selection for general Service Module Diagnostics commands is under the initial Service Module
menu. These commands are common to all types of service modules. The diagnostic commands
available are:
1. Protection Switch
2. Reset/Reprogram
3. Restore
Figure 4-38 shows the menu options for the Service Module Diagnostics selections.
TA-200 OP
8/29/03 4-41
Figure 4-38: TransAccess 200 General Diagnostic Menu
4.6.3.1 Protection Switch
Selecting Protection Switch brings up the screen shown in Figure 4-39.
Prior to activating a manual protection switch, the screen will show the current module status for each
slot. A description of the indicators is below.
A – Active, online
O – Offline
M – Missing (configured module not present)
F – Force online
U – Unconfigured slot (but service module is plugged in)
To select a Service Module to protect, move the cursor beneath one of the card slots and press the
appropriate switch command to toggle the protection switch choices. See below for the available
selections. Any combination of the seven protection modules can be on-line or off-line at the same time.
There are two types of protection switch commands available.
Safe On-line Switch [s] – This will cause the selected module to go on-line. A 50 ms ‘hit’ will occur to
the T1 traffic during the switch. Redundancy remains available after a safe on-line protection switch.
Force On-line Switch [f]– This will cause the selected module to go on-line. A 50 ms ‘hit’ will occur to
the T1 traffic during the switch. Redundancy is disabled while a force protection switch is active.
Therefore, any failures to the on-line module will not be protected. Therefore, the status LED will be
turned yellow to indicate that a maintenance condition is active on the selected module and redundancy is
no longer available.
TA-200 OP
8/29/03 4-42
Figure 4-39: Service Module Protection Switching Control
If a force protection switch was selected the status LED of the online module will be yellow and a minor
alarm will be generated.
4.6.3.2 Reset/Reprogram
This feature forces the MPU module to reprogram the selected module in the shelf. This includes
downloading the current firmware and re-configuring the module with the configuration stored in the
MPU module. Traffic on the selected module will be disrupted for approximately 3 seconds.
When this feature is selected, the user will be prompted for a slot number. Enter the slot number and
press return to invoke the reset.
4.6.3.3 Restore
This selection removes all active diagnostic functions (loopbacks, force protection switches, T1 Testing)
for the selected Service Module.
When this feature is selected, the user will be prompted for a slot number. Enter the slot number and
press return to invoke the restore.
TA-200 OP
8/29/03 4-43
4.6.4 Service Module – PM13E
The Service Module Menu consists of five sections, Alarms, Performance, Performance History,
Configure, and Diagnostic menus. Under each subsection, a module selection is listed. Hit [Enter] while
the cursor is on the service module to select an alarm or performance screen. If trying to enter configure
or diagnostic screens, select the item from the sub-menu under the particular service module type.
Figure 4-40 below displays the service module Alarm Menu. Select PM13E and hit [Enter] to select the
PM13E Alarm Summary screen.
Figure 4-40: PM13E Module Menu

The Alarm Summary table summarizes the Input and Board Alarms for each of the PM13E service
modules. An example of the Alarm Summary is shown in Figure 4-41 below.
Type
Indicates whether the PM13E module is configured for T3, STS-1, or AU3 operation.
State
UNUSED – Indicates that the module plugged into this slot is not configured.
TA-200 OP
8/29/03 4-44
Figure 4-41: PM13E Service Module Alarm Summary

To view the E1, T3, or VT2/VC alarm details, move the cursor to the appropriate field and press
[ENTER].
A description of each alarm field is shown below:
Board Alarm:
BRD ALM – Board Alarm indicates that there has been a hardware failure detected. The PM13E
Module will transmit a T3 AIS (framed 1010 pattern) or an STS-1/AU3 Yellow Alarm if
possible. A Protection Module may protect it.
E1 Alarm:
E1 ALM – Indicates that an alarm has been detected at the E1 level. Press [^T] to display the E1
alarm summary screen.
Line Side Alarms

Line side alarms are broken into three categories, common alarms for T3, STS-1, or AU3
operation, alarms for T3 operation only, and alarms for STS-1/AU3 operation only.
Common Alarms:
LOS – Loss of Signal indicates that the incoming T3, STS-1, or AU3 signal is missing. When
this event is declared, E1 AIS will be transmitted out all 21 E1 ports.
TA-200 OP
8/29/03 4-45
OOF – Out-of-Frame indicates that the incoming T3, STS-1, or AU3 framing is not detected.
When this event is declared, E1 AIS will be transmitted out all 21 E1 ports.
AIS – The Alarm Indication Signal (AIS) indicates that a T3, STS-1, or AU3 failure (AIS – bits 5
and 6 of the H1 byte) has occurred upstream from the TransAccess 200. When this event is
detected, E1 AIS will be transmitted out all 21 E1 ports.
NO OUT – This alarm indicates that the outgoing T3, STS-1, or AU3 signal has failed.
G.747 OOF – G.747 Out-of-Frame indicates that at least one of the G.747 tributaries within the
incoming T3 signal has lost its frame pattern. When this event is detected, the E1 signals
associated with the failed G.747 tributaries will have E1 AIS (all 1’s) inserted out the drop port.
T3X BIT – The received T3 X-bit is used to identify a T3 far-end alarm. When the alarm is
detected, the T3 transmit path to the far-end equipment has failed.
G.747 RAI – The receive G.747 far-end alarm bit is used to identify a G.747 far-end alarm.
When the alarm is detected, at least one of the seven transmit G.747 tributaries has failed towards
the far-end equipment.
STS-1/AU3 Operation Alarms:
LOP – Loss of Pointer indicates that the PM13E module is unable to locate the start of the
Synchronous Payload Envelope (SPE) within the STS-1/AU3 signal. When this event is
declared, E1 AIS will be inserted into each of the outgoing E1 drop ports.
TRIB ALM – This is a VT2 or VC12 alarm summary indicator. For details on the specific
VT/VC alarm detected, you should view the VT/VC Alarm Summary screen by pressing [^V].
4.6.4.2 VT/VC Alarm Summary

As shown, the menu displays an alarm summary for each service module slot. By highlighting the VT
alarm on the PM13E Alarm Summary screen and pressing [ENTER], additional alarm detail, broken
down by VT/VC tributary, can be seen for the selected slot. Figure 4-42 shows the VT/VC Alarm Status
screen for slot 13.
NOTE: If STS-1/AU3 LOS, LOF, LOP, or AIS is detected, VT/VC alarms will not be reported.
AIS – Alarm Indication Signal indicates that a VT/VC signal failure has occurred upstream. The alarm is
SONET signal.
far-end equipment has detected an error on its incoming VT/VC tributary.
TA-200 OP
8/29/03 4-46
The screen shown in Figure 4-42 displays the VT/VC alarms for each tributary of the selected PM13E
slot. Errored Seconds (ES) are based on a BIP-3 error in a one second interval. Severely Errored
Seconds (SES) indicate that 5 or more BIP-3 errors occurred in a one second interval.
Figure 4-42: VT/VC Alarm Details
As the cursor is moved down under each tributary, the E1 Circuit Tag mapped to that VT/VC tributary is
displayed in the upper right hand corner of the screen.
4.6.4.3 E1 Alarm Summary

As shown, the menu displays an alarm summary for each service module slot. By highlighting the E1
alarm on the PM13E Alarm Summary screen and pressing [ENTER], additional alarm detail, broken
down by E1 tributary, can be seen for the selected slot. Figure 4-43 shows the E1 Alarm Details screen
for slot 13.
E1 Circuit Tags are displayed for each tributary. To enter the Circuit Tag information, select the Circuit
Tag screen under the PM13E Configuration Menu.
LOS – Loss-of-signal alarm for each of the 21 E1 tributaries.
AIS – Alarm Indication Signal indicates that a E1 signal failure has occurred upstream. The alarm is
based on detecting 175 consecutive 1’s on the incoming E1 signal.
NOTE: BPV error counts will reset to 0 when LOS is detected on a E1 tributary.
TA-200 OP
8/29/03 4-47
Figure 4-43: E1 Alarm Details

To clear all the BPV counters press [Â].
To clear the BPV counters on a selected tributary, place the cursor on the tributary and press [^T].
4.6.4.4 T3 Alarm Details

The T3 Alarm Details table summarizes the T3 and G.747 alarms for each of the PM13E service modules.
By highlighting the T3 alarm on the PM13E Alarm Summary screen and pressing [ENTER], additional
alarm detail, broken down by G.747 tributary, can be seen for the selected slot. Figure 4-43 shows the
alarm screen. An ‘X’ will appear under the detected T3 or G.747 alarm for the service module. If a T3
LOS or OOF is detected, the G.747 alarms will not be displayed.
TA-200 OP
8/29/03 4-48

4.6.4.5 PM13E Performance Summary

The Performance Summary table displays the framing format and current bit error rate for each of the
PM13E modules. An example of the display on the User Interface Device is shown below.
Slot State:
ONLINE – Indicates that there is a configured module installed and the module is on-line.
OFFLNE – Indicates that there is a configured module installed and off-line.
TA-200 OP
8/29/03 4-49
Figure 4-45: PM13E Service Module Performance Summary
To enable/disable automatic updates, press [Û]

To clear all the errored counters for all slots press [Â]
To clear all the errored counters for a particular slot press [^T]
A description of each bit error field is shown below:
T3/STS-1/AU3 Errored Second Reporting
The maximum count of each errored counter is 65,535 seconds. It the count reaches the maximum it will
be held until it is manually cleared. The following describes each alarm field. If the PM13E module is
programmed for T3, the STS-1/AU3 fields will be left blank and if configured for STS-1/AU3, the T3
fields will be left blank.
path bit errors, 13 STS-1/AU3 B2 errors, detection of loss-of-signal, or detection of out-of-frame.
the PM13E module is configure for STS-1/AU3, the four T3 fields will be left blank.
T3 PARITY – The parity errored seconds will increment every time a T3 P-bit is detected in error for a
one second interval.
T3 PATH – The T3 path count is only available for C-bit parity T3 framing. The CP-bits in the T3
is detected in error for a one second interval.
T3 FAR-END – The T3 far-end block error (FEBE) count is only available for C-bit parity T3 framing.
The far-end block error count will increment every time a FEBE-bit is detected in error for a one second
TA-200 OP
8/29/03 4-50
T3 signal.
STS-1/AU3 B1 – The errored second count will increment every time a STS-1/AU3 B1 byte is detected
in error for a one second interval. The B1 byte is part of the STS-1/AU3 section overhead.
STS-1/AU3 B2 – The errored second count will increment every time a STS-1/AU3 B2 byte is detected
in error for a one second interval. The B2 byte is part of the STS-1/AU3 line overhead.
4.6.4.6 PM13E Performance History

T3/STS-1/AU3 Line, VT/VC tributaries, or T1 drop interfaces. The PM13E history can be selected via
the menu shown in Figure 4-46.
Figure 4-46: PM13E Performance History Menu
4.6.4.6.1 PM13E T3/STS-1/AU3 Line Performance History

Selecting the PM13E Line Performance History menu brings up the screen in Figure 4-47.
TA-200 OP
8/29/03 4-51
Figure 4-47: PM13E Line Performance History
pressing the [SPACE] bar will change to the next on-line PM13E slot number.
TA-200 OP
8/29/03 4-52
4.6.4.6.2 PM13E VT/VC Performance History

Selecting the PM13E VT/VC Performance History menu brings up the screen in Figure 4-48. The screen
displays the VT1.5 alarms for each tributary of the selected PM13E slot. Errored Seconds (ES) are based
Figure 4-48: PM13E VT/VC Performance History
[^C] Clears the VT/VC errors for all 21 tributaries.
4.6.4.6.3 PM13E E1 Drop Performance History
TA-200 OP
8/29/03 4-53
Selecting the PM13E E1 Drop Performance History menu brings up the screen in Figure 4-49.
Figure 4-49: PM13E E1 Drop Performance History
[^C] Clears the drop errors for all 21 tributaries.
4.6.4.7 Configuration – T3/STS-1/AU3 Line

There are three configuration menus for the PM13E module, one for the Line Side (T3/STS-1 port), one
for the Drop Side (T1 ports), and one for Circuit Tag entries. Figure 4-50 displays the PM13E
configuration choices. Figure 4-51 displays PM13E Configuration screen.
TA-200 OP
8/29/03 4-54
Figure 4-50: PM13E Configuration Menu
Figure 4-51: PM13E Service Module Line Side Configuration
TA-200 OP
8/29/03 4-55
To change a configuration setting and download the change to the PM13E module, first highlight the field
To set all the PM13E modules to their default value, press [^T]. Once the default values are set, press
[^S] to save and download the changes. The default values are displayed on the bottom line of the menu
and can also be edited and stored so that future modules will be initially configured as desired.
The configurable items and their options for the PM13E Line Side are listed below.
Type
This feature provides the ability to program the PM13E for T3, STS-1, or AU3 operation.
Protection Switch
This feature provides the ability to enable or disable protection switching for a particular PM13E module.
There are two choices for enabling protection switching, a) protection switching including T1 drop alarms
(ENAB LINE/DROP) or b) protection switching not including T1 drop alarms (ENAB LINE ONLY).
Hold-off
The MPU will detect a PM13E alarm within 50 ms. This feature delays PM13E protection switching
after the MPU detects the alarm. Protection switching hold-off can be programmed for NONE (switch
LBO
Timing Mode
• LOOP – The T3, STS-1, or AU3 clock will be set for Loop Timing. That is, the Transmit
Clock will be timed from the Receive Clock.
• INTERNAL – The Transmit T3 or STS-1 clock will be timed to the PM13E Module’s local
oscillator.
VT/VC Mapping – (Selectable only when configured for STS-1 or AU3 operation)
• TRANSPARENT – E1 circuits are mapped into VT2 tributaries in accordance Telcordia

• INTERLEAVED – E1 circuits are mapped sequentially into VT2 tributaries.
TA-200 OP
8/29/03 4-56
TABLE 4-3: Interleaved Mapping
E1 Drop Port VT/VC Group#, VT/VC#

1 1, 1
2 1, 2
3 1, 3
4 2, 1
5 2, 2
6 2, 3
7 3, 1
8 3, 2
9 3, 3
10 4, 1
11 4, 2
12 4, 3
13 5, 1
14 5, 2
15 5, 3
16 6, 1
17 6, 2
18 6, 3
19 7, 1
20 7, 2
21 7, 3
TABLE 4-4: Transparent Mapping
E1 Drop Port VT/VC Group#, VT/VC#
1 1, 1
2 2, 1
3 3, 1
4 4, 1
5 5, 1
6 6, 1
7 7, 1
8 1, 2
9 2, 2
10 3, 2
11 4, 2
12 5, 2
13 6, 2
14 7, 2
15 1, 3
16 2, 3
17 3, 3
18 4, 3
19 5, 3
20 6, 3
21 7, 3
TA-200 OP
8/29/03 4-57
4.6.4.8 E1 Drop Configuration
Figure 4-52 displays the Drop configuration screen for the PM13E E1 ports. Each E1 tributary for each
redundant pair of modules can be programmed for HDB3 (H), AMI (A), or Disable (D). When disable is
selected, the E1 transmitter will be turned off and alarms disabled for that tributary.
If the PM13 module is configured for T3 operation and a group of E1 tributaries are all disabled within a
T2 group, the T2 alarms for those groups will be disabled.
Figure 4-52: PM13E Service Module E1 Line Code Configuration
4.6.4.9 Circuit Tags

Circuit Tag entries are provided for each E1 tributary per module. In addition, a Circuit Tag can be
entered for each T3/STS-1/AU3 port. Circuit Tags entries are optional and are only provided to help
determine the identification of failed facilities.
TA-200 OP
8/29/03 4-58
Figure 4-53: PM13E Circuit Tag
Figure 4-53 shows the Circuit Tag entry screen. Each Circuit Tag can have up to 15 characters. Once
the Circuit Tags are stored, they will then be displayed on the E1 Alarm Detail screen and VT/VC Alarm
Detail screen (STS-1/AU3 configuration only) for reference.
4.6.4.10 PM13E Diagnostics

PM13E diagnostics consist of Loopbacks, E1 Test Pattern Generator and Receiver, E1 Frame Monitor,
and a E1 Monitor at the PM13 front panel. To select each of these features, place the cursor on the field
and hit the [Enter] key.
TA-200 OP
8/29/03 4-59
Figure 4-54: PM13E Diagnostic Menu
4.6.4.10.1 Loopbacks
Selecting ‘loopback’ brings up the screen shown in Figure 4-55. All loopbacks are bridged. That is, the
Figure 4-55: PM13E Service Module Loopback Control
Loopback Indicators
TA-200 OP
8/29/03 4-60
To toggle the selected field to the next state, press [SPACE]. T3 and STS-1/AU3 line loopbacks activate
in this manner.
To download and activate the loopback request, enter [^S]

To clear all 21 E1 loopbacks towards the T3 or STS-1 port, enter [^T].
To set all E1 loopbacks towards the E1 drop port, enter [^D].
To set all E1 loopbacks towards the T3 or STS-1 port, enter [^L].
To clear all 21 E1 loopbacks towards the drop ports, enter [^W].
To select a new service module slot, enter [Ô].
To enable each loopback individually, place the cursor on the particular E1 port and press [SPACE].
To select a new slot (1-14) either move the cursor to the top line and hit the [SPACE] bar to toggle
between 14 card slots (the cursor must be in the far left column in order to move it to the top field), or
enter [Ô] to enter the specific PM13E card slot. A prompt will appear saying “Enter new slot:”. Enter
the PM13E slot number.
To select a tributary to loopback, move the cursor under the E1 tributary number and hit the [SPACE] bar.
An ‘x’ will appear. Other tributaries may also be selected as well. When all tributaries have been
selected, save by pressing ^S. An upper case ‘X’ will appear to indicate that the loopback is active.
NOTE: T1 loopbacks towards a T3 or STS-1/AU3 tributary will not be active if a E1 Test signal is
generated on the same tributary.
4.6.4.10.2 E1 Test
This feature provides the capability to non-intrusively monitor any E1 signal dropping from either the
incoming T3/STS-1/AU3 signal or incoming E1 signal. If the PM13E is programmed for STS-1/AU3
operation a selection of 4 test signals can be used to intrusively inject into any E1 towards the STS-1/AU3
port or 21 E1 drop ports. If the PM13E is programmed for T3 operation, only a QRSS pattern is
available. Figure 4-56 shows the E1 Test Configuration screen. If the selected PM13E is programmed
for STS-1/AU3 operation, the tributaries are selected by VT/VC group and VT/VC tributary number.
To select the PM13E module, highlight the SLOT number and press the space bar to toggle to the next
PM13E slot or press Ô to enter the specific slot number.
When configured for STS-1/AU3 the Test Pattern can be inverted or non-inverted. Move the cursor over
to PATTERN POLARITY to select between a Normal (non-inverted) and Inverted test pattern.
To select the Test Generator Pattern, highlight the PATTERN field and press the space bar to selection
one of the 4 test pattern options (STS-1/AU3 mode only): QRSS, 2E15-1, 2E20-1, or 2E23-1. Select a
Framed or Unframed pattern.
NOTE: If the PM13E is configured for T3 operation, only a QRSS pattern is available.
TA-200 OP
8/29/03 4-61
Figure 4-56: PM13E E1 Test Configuration Screen
To inject a pattern into a tributary, move the cursor and select the direction in which to inject the test
signal. If the PM13E is configured for STS-1 or AU3, 21 E1 tributaries will be displayed as in Figure 4-
56. Press the space bar to select the tributary either towards the T3/STS-1/AU3 or E1 output or press ^X
to select all the generator tributaries. A lower case ‘x’ will appear. Press ^S to save the entry and to
initiate the E1 monitor. The lower case ‘x’ will change to an upper case ‘X’. Multiple tributaries can be
selected simultaneously in one direction only.
^Y will clear all the selections from the E1 Generator. Press ^S to save and download the cleared entries.
All tributary selections must be removed before the direction of the E1 Generator or E1 Receiver can be
toggled.
One tributary can be monitored at a time. Before selecting the tributary to monitor, first select a E1
pattern, framing, and receive direction. To select the tributary to monitor, move the cursor under the
tributary (T3 or E1 drop) or Group/VT (STS-1/AU3) number and press the space bar. An ‘X’ will appear.
Press ^S to save the entry and to initiate the E1 monitor. The RECEIVED ERRORS will display the
number of E1 bit errors received (up to 65,535 errors). To clear the errors, enter ^C.
NOTE: WHEN THE E1 TEST GENERATOR OR RECEIVER IS ENABLED ON THE PM13E

MODULE, THE PM13E STATUS LED WILL TURN YELLOW.
NOTE: E1 LOOPBACKS TOWARD A T3 OR STS-1/AU3 TRIBUTARY WILL NOT BE ACTIVE

IF AN E1 TEST SIGNAL IS GENERATED ON THE SAME TRIBUTARY.
4.6.4.10.3 E1 Frame Monitor

The PM13E module has the ability to monitor the framing of any incoming E1 signals from the drop side.
Figure 4-57 shows the E1 Frame Monitor screen.
TA-200 OP
8/29/03 4-62
For each module, select a E1 tributary to monitor in the E1 TRIB column. Both the on-line and off-line
PM13E modules can monitor an incoming E1 at the same time. Once a E1 tributary is selected, the
FRAMING column will automatically display the type of framing, namely CCS, CAS, or OOF (Out-Of-
Frame) that has been detected.
The errored counts are incremented in the following fashion:

• Errored Seconds Any Frame Bit Error in 1 second
• Severely Errored Seconds 320 Frame Bit Errors/LOS/OOF
Figure 4-57: PM13E E1 Frame Monitor
To end monitoring on all card slots, press [Â]
To clear all errored counters, press [^B]
To end monitoring the selected card slots, press [^C]
To clear the errors on the selected slot, press [Ê]
To manually select a new tributary to monitor, press [^T]
To enable/disable automatic updating, press [Û]
4.6.4.10.4 E1 Front Panel Monitor

The PM13E module has a bantam jack on the front panel that provides a E1 monitor point for any of the
incoming E1 tributaries from the drop ports. Figure 4-58 shows the Front Panel E1 Monitor screen.
For each module, simply select a E1 tributary to monitor. Selections can be made for the incoming E1s
from the drop ports. Once the E1 tributary is selected, the signal from the selected tributary will be
transmitted out the front bantam connector. Monitoring a E1 will not disrupt the live traffic on the
selected tributary.
TA-200 OP
8/29/03 4-63
When a E1 tributary is selected and downloaded, the PM13E module’s status LED will turn yellow and a
minor alarm will be generated indicating that a maintenance condition is active.
Figure 4-58: PM13E Front Panel T1 Monitor
To toggle the selection, move the cursor to the appropriate card slot and press [SPACE]
To select a new card slot, press [Ô]
To end monitoring of all card slot, press [^C]
TA-200 OP
8/29/03 4-64
4.6.5 Service Module – OMX3
The Service Module Menu consists of four sections, Alarms, Performance, Configure, and Diagnostic
menus. Under each subsection, a module selection is listed. Hit [Enter] while the cursor is on the service
module to select an alarm or performance screen. If trying to enter configure or diagnostic screens, select
the item from the sub-menu under the particular service module type.
Figure 4-59 below displays the service module Alarm Menu. Select OMX3 and hit [Enter] to select the
OMX3 Alarm Summary screen.
Figure 4-59: Service Module Alarm Menu

The Alarm Summary table summarizes the Input and Board Alarms for each of the OMX3 service
Type
This column displays the module type installed in each service module slot.
State
UNCONFG – Indicates that the module plugged into this slot is not configured.
TA-200 OP
8/29/03 4-65
Figure 4-60: OMX3 Service Module Alarm Summary

To display the alarm details of the PATH-SUM or DROP alarms, move the cursor to the appropriate
field and press [ENTER].
Board Alarm:
BRD ALM – Board Alarm indicates that there has been a hardware failure detected (clock failure
or loss of any of the drop port transmit signals). A Protection Module may protect it.
Clock Alarm:
CLK ALM – Clock Alarm indicates that the primary configured clock source has failed. If
configured for External Timing, Through Timing, or Source Timing and the timing source fails,
the OMX3 module will switch to its Internal Oscillator.
Optical Input Alarms:
LOS – Loss of Signal indicates that the incoming OC-3/STM-1 signal is missing. When this
event is declared, c AIS will be transmitted out all 3 drop ports.
LOF – Loss-of-Frame indicates that the incoming OC-3/STM-1 framing is not detected. When
this event is declared, T3, STS-1, or AU3 AIS will be transmitted out all 3 drop ports.
TA-200 OP
8/29/03 4-66
AIS – The Alarm Indication Signal (AIS) indicates that an OC-3/STM-1 failure (AIS – bits 5 and
6 of the H1 byte) has occurred upstream from the TransAccess 200. When this event is declared,
T3, STS-1, or AU3 AIS will be transmitted out all 3 drop ports.
RDI – The Remote Defect Indicator (RDI) alarm indicates that the far-end OC-3/STM-1
equipment has detected an OC-3/STM-1 Line alarm.
PATH-SUM – This is a summary of the incoming OC-3/STM-1 path alarms. For details on what
alarm was detected, place the cursor on the alarm and press [Enter] to proceed to the OC-3/STM-
1 Path Alarm Details screen.
Drop Alarm:
When an ‘X’ appears in this location, an alarm has been detected by the receive drop port. For details on
what alarm was detected, place the cursor on the alarm and press [Enter] to proceed to the OC-3 Drop
Alarm Details screen for that particular drop port.
4.6.5.2 OC-3 Path Alarm Summary

The OC-3/STM-1 Path Alarm Summary table summarizes the OC-3/STM-1 path alarms for each of the
OMX3 service modules. Figure 4-61 shows the alarm screen.
NOTE: If OC-3 LOS, LOF, or AIS is detected, OC-3 path alarms will not be reported.
LOP – Loss of Pointer indicates that the OMX3 module is unable to locate the start of the
Synchronous Payload Envelope (SPE) within the STS-1/AU3 signal.
AIS – Alarm Indication Signal indicates that an STS-1/AU3 tributary signal failure has occurred
upstream. The alarm is based on detecting an all 1’s in the V1 and V2 bytes for 3 consecutive
superframes of the incoming SONET signal.
SLM – Signal Label Mismatch indicates that the C2 byte of the STS-1/AU3 tributary was invalid.
RDI – Remote Defect Indicator is detected from bits 5-8 of the incoming G1 byte. RDI indicates
that the far-end equipment has detected an error on its incoming STS-1/AU3 tributary.
TA-200 OP
8/29/03 4-67
Figure 4-61: OMX3 Path Alarm Summary

To display the Drop Alarm Details screen press [TAB]
4.6.5.3 OMX3 Drop Port Alarm Summary

The Drop Port Alarm Summary table summarizes the STS-1/AU3 or T3 alarms for the OMX3 service
module incoming drop ports. Figure 4-62 shows the alarm summary screen for port 1 (ports 2 and 3 are
identical).
Board Alarm – Indicates a hardware failure on the OMX3 module.
STS-1/AU3 Input Alarms:
LOS – Indicates a Loss-of-Signal has been detected on the incoming port.

LOF – Indicates a Loss-of-Frame has been detected on the incoming port.
LOP – Indicates a Loss-of Pointer has been detected on the incoming port.
AIS – Indicates that the Alarm Indication Signal has been detected on the incoming port.
SLM – Indicates that an invalid Signal Label was detected in error.
RDI – The Remote Defect Indicator is a far-end alarm. If detected, it indicates that the receive
port of the far-end STS-1/AU3 equipment is in alarm.
TA-200 OP
8/29/03 4-68
T3 Input Alarms:
LOS – Indicates a Loss-of-Signal has been detected on the incoming port.

OOF – Indicates a Out-of-Frame has been detected on the incoming port.
AIS – Indicates that the Alarm Indication Signal has been detected on the incoming port.
RAI – Indicates a Remote Alarm Indicator (T3 X-bit) has been detected on the incoming port.
Figure 4-62: OMX3 Drop Port Alarm Summary

To display the Path Alarm Details screen press [TAB]
4.6.5.4 Performance Summary

The Performance Summary table displays the current bit Error Second (ES) and Severely Errored Second
(SES) for each of the OMX3 modules. An example of the display on the User Interface Device is shown
below.
TA-200 OP
8/29/03 4-69
Figure 4-63: OMX3 Service Module Performance Summary
Type
Slot State:
UNCONFG – Indicates that the module plugged into this slot is not configured.
OC-3 Errored Second Reporting

The maximum count of all the errored counter is 65,535 seconds. It the count reaches the maximum it
will be held until it is manually cleared. The following describes each alarm field.
B1 ES – The B1 Errored Counter will increment by one for each second that contains at least 1
code violation detected in the B1 byte (Section CV).
B1 SES – The Severely Errored Counter will increment by one for each second that contains at
least 16 OC-3 B1 errors, detection of loss-of-signal, or detection of out-of-frame.
B2 ES – The errored second count will increment every time an OC-3/STM-1 B2 byte (Line CV)
TA-200 OP
8/29/03 4-70
least 32 OC-3/STM-1 B2 errors, detection of loss-of-signal, or detection of out-of-frame.
Drop Port Error Reporting

be held until it is manually cleared. The following describes each alarm field.
T3/STS-1/AU3 ES – The Errored Second Counter will increment by one each second that
contains a T3 parity error or an STS-1/AU3 code violation.
T3/STS-1/AU3 SES – The Severely Errored Second Counter will increment by one for each
second that contains 44 T3 parity bit errors, 32 STS-1/AU3 code violation errors, detection of
loss-of-signal, or detection of out-of-frame.
4.6.5.5 OMX3 Performance History

Figure 4-64 displays the OMX3 Performance History for the OC-3/STM-1 port and three drop ports.
Figure 4-64: OMX3 Performance History
pressing the [SPACE] bar will change to the next on-line OMX3 slot number.
TA-200 OP
8/29/03 4-71

4.6.5.6 Configuration
Figure 4-65 displays the configuration screen for the OMX3 service module and allows each
configuration item to be modified using the cursor keys.
To change a configuration setting and download the change to the OMX3 module, first highlight the field
To set all the OMX3 modules to their default value, press [^T]. Once the default values are set, press [^S]
to save and download the changes. The default values are displayed on the bottom line of the menu and
can also be edited and stored so future modules will be initially configured as desired.
The configurable items and their options for the OMX3 module are listed below.
Type
Line Mode
This feature configures the optical interface for OC-3 or STM-1.
TA-200 OP
8/29/03 4-72
OP Mode
This configuration item defines the operation of the OMX3 module. The choices are either Terminal
mode (TERM) or Add/Drop (ADRP). In Terminal mode, all 3 T3/STS-1/AU3 tributaries are dropped
from the OC-3/STM-1 line. OMX3 protection switching is based on the SONET Automatic Protection
Switch (APS) algorithm.
In Add/Drop mode, each tributary can be selected to either pass through the node or dropped from the
OC-3 ring. OMX3 protection switching is based on Unidirectional Path Switched Rings (UPSR).
Figure 4-65: OMX3 Service Module Configuration
Protection Switch
This feature provides the ability to enable or disable protection switching for a particular OMX3 module.
Hold-off
The MPU will detect a OMX3 alarm and switch to the redundant module within 50 ms. The hold-off
feature delays OMX3 protection switching after the MPU detects the alarm. Protection switching hold-
off can be programmed for NONE (switch immediately), 50ms, 100ms, 500ms, 1 second, 2 seconds, or 5
seconds.
Timing Mode
• LOOP – If configured for Terminal Mode (TRML), the OC-3/STM-1 clock can be set for
Loop Timing. That is, the Transmit Clock will be timed from the Receive Clock.
• INTERNAL – The Transmit OC-3/STM-1 clock will be timed to the OMX3 Module’s local
oscillator.
• EXTERNAL – The Transmit OC-3/STM-1 clock will be timed from the 64KHz external
composite clock connected at the TransAccess 200 backplane.
TA-200 OP
8/29/03 4-73
• THRU – If configured for Add/Drop, the Transmit OC-3/STM-1 clock can be timed from the
recovered clock of the adjacent OMX3 module.
• Dn – Timing of the Transmit OC-3/STM-1 clock can be derived from any of the Incoming
Drop Ports (1-3) only if they are configured for STS-1/AU3.
• SRC – Source Timing can be configured for one OMX3 card in the TransAccess 200 shelf. It
is used to distribute timing to the other OMX3 modules. It does this by deriving an 8KHz
clock from the incoming OC-3/STM-1 recovered clock and placing the 8KHz clock on the
external clock bus on the backplane. Select External Clock for the other OMX3 modules
that need to be timed to this clock. Only one OMX3 module can be configured for SRC
timing at a time.
NOTE: IF SRC TIMING IS SELECTED ON ANY OMX3 SERVICE MODULE, BE SURE TO

DISCONNECT THE EXTERNAL CLOCK FROM THE BACKPLANE AS BOTH SRC
AND EXTERNAL CLOCKS USE THE SAME CLOCK BUS. FAILURE TO DO SO WILL
CAUSE THE SRC AND EXTERNAL CLOCKS TO COLLIDE WITH EACH OTHER.
Drop Signal
Each drop port can be configured for either T3, STS-1 (STS), AU3, Bypass (BP), or Disable (DIS). STS-
1 can only be selected if the OMX3 is configured for OC-3. AU3 can only be selected if the OMX3 is
configured for STM-1. Bypass (BP) can only be selected when configured for ADRP operation. If the
OMXT3 module is installed, only T3, Bypass (BP), or Disable (DIS) can be selected.
LBO
Each drop port can be configured independently.
• I (LBO In)– Outgoing T3/STS-1 Line Build Out selection for cable lengths less than or equal
to 225 feet.
• O (LBO Out)– Outgoing T3/STS-1 Line Build Out selection for cable lengths greater than to
225 feet.
4.6.5.7 OMX3 Loopback

Selecting ‘loopback’ brings up the screen shown in Figure 4-66. All loopbacks are bridged. That is, the
Four loopbacks are available:
OC-3/STM-1 Line Loopback – Loops the entire receive OC-3/STM-1 signal back out the transmit port.
OC-3/STM-1 Drop Loopback – Loops the entire transmit OC-3/STM-1 signal back into the receive port.
T3/STS-1/AU3 Line Side – Loops the selected STS-1/AU3 or T3 transmit tributary back into the receive
tributary.
T3/STS-1/AU3 Drop Side – Loops the selected STS-1/AU3 or T3 receive tributary back out the transmit
port.
PRECAUTION: DO NOT ENABLE THE OC-3/STM-1 DROP LOOPBACK AND THE STS-1/T3
LINE SIDE LOOPBACKS SIMULTANEOUSLY. IF SO, ALARMS WILL BE
GENERATED SINCE THERE IS NO ORIGINATING SOURCE OF TIMING.
TA-200 OP
8/29/03 4-74
To select a loopback, use the cursor keys to highlight the selected loopback field. Press the space bar and
an ‘x’ (lower case) will appear. Enter [^S] to save and download the loopback command. After the
command is downloaded, the ‘X’ will become upper case to indicate that the loopback is active.
Figure 4-66: OMX3 Service Module Loopback Control

To download and activate the loopback request, enter [^S]
To cancel all OMX3 loopbacks, press [^C]
To redraw the screen, enter [^R].
To enable each loopback individually, place the cursor on the particular port and press [SPACE].
NOTE: When using the OC-3/STM-1 DCC for communications to a remote node, an OC-3 Line
or Drop Loopback at the remote node will block communications to that node. Therefore,
clearing the loopback will be unsuccessful via the DCC.
TA-200 OP
8/29/03 4-75
4.6.6 MPU
Figure 4-67 shows the MPU menu.
Figure 4-67: MPU Menu
4.6.6.1 Configuration
The MPU has five configuration options; setting the baud rate of the Terminal Port, setting the time,
setting the date, setting the System Name, and Enable/Disable of the External Power Alarm. The time
and date settings are used by the MPU to time-stamp the alarm traps sent out via SNMP.
4.6.6.1.1 Setting the Baud Rate

The default baud rate setting is Auto baud (recommended). However, the baud rate can be adjusted from
the Terminal Device so that it can be attached to standard modem lines. The baud rate selections are:
1200 baud
2400 baud
4800 baud
9600 baud
19.2K baud
38.4K baud
57.6K baud
115.2K baud
Auto baud
The baud rate configuration is used to set the speed of the serial port (craft port) at the front of the MPU
modules. Press the [SPACE] bar to toggle between the baud rate selections. Press ^S and [Enter] to save
and download the change. Use the Auto Baud option whenever possible as this allows the MPU to
TA-200 OP
8/29/03 4-76
automatically sync up to the serial input. When you are finished communicating to the TransAccess 200,
use the Logout command under the System Menu. This will place the MPU in ‘Auto Baud’ mode and
allow next user to connect at the same or different baud rate.
4.6.6.1.2 Set Time and Date

To set the time and date, simply enter the current time and date.
4.6.6.1.3 Set System Description

The System Description can be used to identify each TransAccess 200 system in the network. A name
can be assigned to each system and displayed in the upper right hand corner of most of the management
screens. Simply enter the character string you wish and press [ENTER]. The MPU must be reset to
activate the new System Description setting.
4.6.6.1.4 Enable/Disable External Power Alarm

If the MPU modules have been installed with External Power Sense circuitry, the Mini-Mux 155 can
detect a loss of the –48VDC or +24VDC on the Battery A or Battery B feeds. The software will
automatically detect whether the External Power Sense circuit is equipped. If equipped, the menu will
allow you to enable or disable the detection of each power feed.
4.6.6.2 Setting the Ethernet Port IP Address

Section 5.1 gives instructions on how to set the Ethernet Port IP Address.
4.6.6.3 Configuration for TL1

Section 6.3.1 gives instructions on how to configure the TransAccess 200 for TL1 operation.

The alarm summary screen shows the status summary of the on-line and off-line MPU modules. The
screen is shown in Figure 4-68. The MPU alarm summary shows the MPU status for the left and right
modules. Major and Minor alarms for the MPU indicate the level of alarm for the MPU. A Major alarm
will be declared if the MPU FPGA is not programmed. Minor Alarms will be generated for MPU internal
clock or circuitry failure. If the failure is protected by the redundant MPU (if equipped) the alarm will be
Minor. If not protected, the alarm will be Major. The MPU failures reported will be either for the
Watch-dog Timer (WDT), the Real Time Clock (RTC), or the Communications to the redundant MPU
(Comm). The STATUS indication will show whether the MPU is On-line, Off-line, Missing (if the
redundant module is configured but unplugged), or Empty (if the redundant MPU is not configured).
TA-200 OP
8/29/03 4-77
Figure 4-68: MPU Status Summary

Protection Switch causes the off-line MPU to go on-line.
4.6.6.6 Reset
The Reset command causes the on-line MPU module to re-boot. This will not disrupt any service module
traffic. However, it will cause a protection switch to the opposite MPU module while the re-boot process
completes. Once the MPU module re-boots, it will remain off-line until a protection switch command is
issued or hardware failure occurs to the on-line MPU module.
PRECAUTION: PM13(E) LOOPBACKS, PM13(E) MANUAL PROTECTION

SWITCH, AND PM13(E) T1/E1 TEST FUNCTION
COMMANDS WILL BE DROPPED IF AN MPU RESET,
PROTECTION SWITCH, OR MODULE DISCOVERY OCCURS.
4.6.6.7 Disconnect a Telnet/TL1 Session

Only one Telnet or TL1 session can be active at a time. Therefore, it is important to remember to
disconnect your Telnet or TL1 session when done. Disconnecting a Telnet or TL1 sessions will allow
another user to connect at a later time. To prevent lockout, go to the Telnet Configuration menu and
enable the Telnet timeout. To view the Telnet Configuration Menu, please refer to Figure 6-1.
Please refer to Figure 6-2 to view the Telnet Disconnect menu.
TA-200 OP
8/29/03 4-78
5 REMOTE NETWORK MANAGEMENT CONFIGURATION
SNMP, TL1, Web Browser, and Telnet management capability are TransAccess 200 features that provide
standards-based ways to remotely manage the TransAccess 200 from anywhere on the network. The
TransAccess 200 MPU must be equipped with an Ethernet Auxiliary board to enable SNMP, TL1, Web
Browser, or Telnet functionality. If redundant MPUs are equipped, both must have Ethernet Auxiliary
boards installed. If your TransAccess 200 was not factory-equipped for SNMP or Telnet operation, it
may be upgraded in the field by ordering Ethernet Aux. Board (consult Turin sales or customer service for
part number) for each MPU and install them per the instructions included. If you have an early
TransAccess 200 shelf without an on-board network connector on the backplane, an interface adapter,
(consult Turin sales or customer service for part number), should also be ordered from Turin Networks.
New MPU modules have been developed with the Ethernet circuitry integrated into a single printed
circuit board (consult Turin sales or customer service for part number). If this MPU is equipped, no
additional upgrades are necessary to support SNMP, TL1, Web Browser, or Telnet.
5.1 Connect the TransAccess 200 to the Network
Connect a Customer-provided standard Category 5 Unshielded Twisted Pair (UTP) cable terminated with
a modular connector to the RJ45 jack located near the rear of the left side of the TransAccess 200 shelf.
The other end of this cable should be connected to a 10Base-T Ethernet access point on the Internet
Protocol (IP) network used by the SNMP, TL1, Web Browser, or Telnet Management platform.
5.2 Configuring the TransAccess 200 for SNMP, TL1, Telnet, or Web Browser
Operation
The following information must be available before proceeding.
• IP Address
• IP Network Address Mask
• Default Gateway IP Address
• The Community Name for read-write access, and optionally, the IP address of the SNMP
management station if read-write access is to be limited to a single station. (This parameter is not
required for Telnet or Web Browser operation.)
• The Community Name for read-only access, and optionally, the IP address of the SNMP
management station if read-only access is to be limited to a single station. (This parameter is not
Connect the User Interface Device (UID) to the TransAccess 200 as described in Chapter 4 and log in as a
level 3 or level 4 user.
Using the UID, select MPU from the top-level menu, and select Configuration from the resulting menu as
Select IP/SNMP CONFIG from the MPU Configuration menu. The first time this screen is displayed, it
will contain default values in each of the fields as shown below in Figure 5-2.
The IP/SNMP configuration screen allows you to set the configuration information specific to your
TransAccess 200 system installation. The IP/SNMP Configuration operation must be done using the UID
before any access by an SNMP, TL1, Web Browser, or Telnet management station will be possible.
TA-200 OP
8/29/03 5-1
Figure 5-1: MPU Configuration
Figure 5-2: IP/SNMP Port Configuration
The IP/SNMP Configuration screen consists of the following fields:

IP Address
This is the unique Internet Protocol (IP) address assigned by your network administrator for the
TransAccess 200 shelf. This is a mandatory user entry. Each of the 4 parts of the IP address may be
accessed using the ‘Tab’ key.
TA-200 OP
8/29/03 5-2
MAC Address
This is an information-only field. It cannot be modified. The Media Access Control (MAC) Address is
an identification number required to uniquely identify each TransAccess 200 MPU/Ethernet Aux. module
on the network.
Net Mask
This is the IP address subnet range mask assigned by your network administrator. The default value is
255.255.255.0. If your network administrator has assigned a different mask value, edit this field to match
that value.
Gateway
This is the IP address of the gateway device, if required, as assigned by your network administrator. The
default value is 0.0.0.0. This field must be changed to a valid IP address if the SNMP management or
Telnet client stations are located on a different subnet than the TransAccess 200.
DCC Parameters
In order to provide interoperability with other vendor’s equipment, the Turin TransAccess 200 supports
remote management over the SONET Section DCC when an OC-3 fiber facility from the other equipment
is connected to an OMX3 service module in the TransAccess 200 shelf.
The Section DCC, which occupies bytes D1, D2, D3 in the overhead of the SONET frame for the first
STS-1, is used to provide a serial 192 Kbps physical layer data communications channel between the two
nodes.
At the data link layer, RFC 1661-compliant Point-to-Point Protocol (PPP) is used over High-level Data
Link Control (HDLC). The details of the frame format used between the physical and data link layers are
given in RFC 1662 “PPP in HDLC-like Framing”.
Once the optical/electrical connection is established, the first communications between the two nodes is a
sequence of Link Control Protocol (LCP) messages. Turin recommends using the following PPP LCP
options:
• Maximum Receive Unit (MRU) 1524

• No Authentication Protocol
• No Quality Protocol
• No Magic Number
• Frame Check Sequence (FCS): CCITT 32 bit CRC
• No Asynchronous Control Character Map (ACCM)
Once the LCP process is complete and the link successfully established, communications to the network
layer may begin. The standard Network Control Protocol (NCP) and Internet Protocol Control Protocol
(IPCP) are used to configure the network layer to accept Internet Protocol (IP), or Internet Control
Message Control Protocol (ICMP), or Address Resolution Protocol (ARP) messages. Turin recommends
the IPCP configuration include the IP Address of sender.
The TransAccess 200 does not currently support IP routing since it can only be configured as an end
point.
At this point, entry into the transport layer and above depends on which management application is being
used. Simple Network Management Protocol (SNMPv2) uses the User Datagram Protocol (UDP). If a
TA-200 OP
8/29/03 5-3
Telnet session is established, which contains either our VT-100 User Interface or Transaction Language 1
(TL-1) messages, or a Web browser using the HyperText Transfer Protocol (HTTP), then Transmission
Control Protocol (TCP) is used.
DCC communication is designed to function mainly in point-to-point (terminal) applications but can work
in a ring to an adjacent node. In terminal applications using APS, if an OC-3/STM-1 failure should
occur, the DCC will switch to the redundant path. However, in Add/Drop applications, the DCC will be
disabled if the OC-3 facility to the adjacent node should fail.
Configure the TransAccess 200 system as follows to activate the use of the DCC.
For the Local system (connected to the LAN):

1. Set MODE to LOCAL
2. Set SLOT to the OMX3 primary card slot number
3. Enter [^S] to save the changes. The MPU module will reboot to activate the changes.
For the Remote system:

1. Set MODE to REMOTE (NOTE: This will disable the Ethernet port.)
2. Set SLOT to the OMX3 primary card slot number
3. Enter [^S] to save the changes. The MPU module will reboot to activate the changes.
Communications over the DCC can now begin. Refer to Chapter 7 for SNMP parameter settings.
5.3 Other Remote Management Options
Other remote management methods are described in greater detail as follows.
1. Telnet Chapter 6
2. SNMP Chapter 7
3. TL1 Chapter 8
4. Web Browser Chapter 9
TA-200 OP
8/29/03 5-4
6 REMOTE MANAGEMENT USING TELNET
The following procedure assumes the user is using a conventional personal computer or laptop and is
running Windows 95, 98 or ME, and is connected to the same network as the TransAccess 200.
Click the Start button on the desktop task bar. From the Start menu, click Run... and type "telnet"
(without the quotes) in the Open: box in the Run window and click OK. Click Connect from the menu
bar in the Telnet window, and click Remote System... Enter the IP address of the TransAccess 200
system in the Host Name: box in the Connect window, select telnet from the Port: box menu, select
VT100 from the TermType: box menu, and click the Connect button.
The response should be a login: prompt from the TransAccess 200. Enter your password just as described
for the User Interface Device in Chapter 4. Refer to Chapter 4 for all other telnet operations.
6.1.1 Telnet Configuration Menu
By selecting Telnet Configuration, three configuration items will be displayed as shown in Figure 6-1.
First, a selection for UI or TL1 will be displayed. Choosing UI will configure the TransAccess 200 to use
the graphical user interface menus during a telnet session and provide access for the use of the
TransAccess 200 Web Browser management interface. If TL1 is selected, the Telnet interface will accept
TL1 command messages and will output automatic TL1 alarms.
The third configuration choice will be to select a timeout period to disconnect a TL1 and Telnet session if
no activity is detected in a certain period of time. The selectable time period is from 0 to 60 minutes. If 0
is selected, no timeout will occur.
After making all selections, enter a 4 to save the changes. The changes will take affect at the next telnet
login.
Figure 6-1: Telnet Configuration Menu
TA-200 OP
8/29/03 6-1
6.1.2 Disconnect a Telnet Session
In order to prevent logout problems if a user does not disconnect a telnet session when done, a command
will be added to manually disconnect the telnet session from the UID menu. Please refer to Figure 6-2.
Figure 6-2: Telnet Disconnect Screen
TA-200 OP
8/29/03 6-2
7 SIMPLE NETWORK MANAGEMENT PROTOCOL (SNMP)
SNMP or Telnet management capability is an TransAccess 200 feature that provides standards-based
ways to remotely manage the TransAccess 200 from anywhere on the network. The TransAccess 200
MPU must be equipped with an Ethernet Auxiliary board to enable SNMP or Telnet functionality. If
redundant MPUs are equipped, both must have Ethernet Auxiliary boards installed. If your TransAccess
200 was not factory-equipped for SNMP or Telnet operation, it may be upgraded in the field by ordering
Ethernet Aux. Board, (consult Turin sales or customer service for part number), for each MPU and install
them per the instructions included. If you have an early TransAccess 200 shelf without an on-board
network connector on the backplane, an interface adapter, (consult Turin sales or customer service for
part number), should also be ordered from Turin Networks.
additional upgrades are necessary to support SNMP or Telnet.
7.1 SNMP Management Station
Turin Networks does not supply a SNMP management platform or application. It is assumed that the
Customer has, or will provide, one or more networked computers with standards-compliant SNMP
management application suites installed.
Turin Networks provides three files on the CD-ROM included with the TransAccess 200 equipment that
must be loaded onto the SNMP Management platform in order to recognize and access the TransAccess
200. These files are:
OTI-Ex2-CAP.my Turin Networks, Inc. TransAccess 200 CAPabilities module

OTI-Ex2-MIB.my Turin Networks, Inc. TransAccess 200 Management Information
Base
OTI-SMI.my Turin Networks, Inc. Structure of Management Information
Select IP/SNMP CONFIG from the MPU Configuration menu. The IP address must also be entered if
using TL1 management. The first time this screen is displayed, it will contain default values in each of
the fields as shown below in Figure 7-1.
The SNMP configuration screen allows you to set the configuration information specific to your
TransAccess 200 system installation. The SNMP Configuration operation must be done using the UID
before any access by an SNMP, TL1, Telnet, or Web Browser management station will be possible.
To begin, configure the IP/SNMP port as described in Chapter 5. Then continue to configure the
following parameters, as required, for SNMP operation.
SNMP Parameters
The SNMP Parameters provide a place to define the System Name, Contact, and Location of the
TransAccess 200 system for use with the SNMP management interface. To enter this information, move
the cursor to the appropriate field and type in the information. Hit ENTER to complete the entry.
NOTE: If any of the text in the System Name, Contact, or Location contains spaces, the entire
entry must be enclosed in double quotes. If it is not, only the first word will be preserved when
saved.
TA-200 OP
8/29/03 7-1
Figure 7-1: IP/SNMP Port Configuration
Community
The Community Name fields provide the customer with two levels of security against unauthorized
access to the TransAccess 200 by a SNMP management station. The Community Name entry with
“Read” command access should be assigned to any SNMP management stations that are to be allowed
“Get” command access to the TransAccess 200. Any “Set” command attempts by these stations will be
refused. The Community Name entry with “Write” command access should be assigned only to SNMP
management stations that are to be allowed unrestricted “Set” as well as “Get” command access to the
TransAccess 200. (These parameters are not required for Telnet, TL1, or Web Browser operation.)
Note - The Read Community Name and Write Community Name must be different. Only
alpha characters and numbers are allowed in the Community Name and Trap Name fields.
Spaces, punctuation, and other characters are illegal.
If an optional Community IP Address is entered, then only a single SNMP management station with the
correct Community Name and IP Address will be authorized for access to the TransAccess 200 as
determined by the corresponding Access field. If this field is set to 0.0.0.0, which is the default, then any
SNMP management station with the correct Community Name will be authorized for appropriate access.
The Read and Write values in the Access fields may be toggled between Read and Write by pressing the
space bar when the cursor is on them.
Trap
A trap is a message automatically generated by the TransAccess 200 and sent to up to three SNMP
management stations. These messages are sent out whenever an TransAccess 200 alarm is asserted or
cleared. Enter the IP Addresses of the SNMP management stations, if any, to which the traps are to be
sent in the Trap IP Address fields. Unused fields should be set to 0.0.0.0, which are the defaults. If all 3
Trap IP Addresses are set to 0.0.0.0, then no trap messages will be generated. A Trap Name may be
optionally entered for each of the trap recipients to identify the source of the trap. This entry is useful if
more than one network element reports traps to the same SNMP management station. The rules for Trap
TA-200 OP
8/29/03 7-2
Name entries are the same as for Community Names. (These parameters are not required for Telnet, TL1,
or Web Browser operation.)
Authen Traps
An Authentication Trap, if enabled, is a security alert message generated by the TransAccess 200
whenever an unauthorized SNMP command is received. It is sent to the trap recipients, if any, identified
in the Trap fields. An Authentication Trap message is sent in response to a command received with an
incorrect Community Name, or incorrect IP Address, if a specific IP Address was entered, or if a “Set”
command was attempted by a station with only Read access.
Authentication Traps are disabled by default. To change the Authen Trap setting, press the space bar
when the cursor is on it to toggle the value between Disable and Enable. (This setting has no effect on
Telnet, TL1, or Web Browser operation.)
T1/E1 Alarm Traps

T1/E1 alarm traps can be generated two ways. By selecting SUMMARY, a single alarm trap will be
transmitted when single or multiple T1 alarms are detected. By selecting DETAIL, an alarm trap that
includes the slot, tributary, and circuit tag will be sent for each T1 and/or E1 alarm detected.
NOTE: - The MPU must be reset following any changes to the SNMP Configuration for the
new values to become effective.
7.2 Saving IP/SNMP Changes
When all of the IP/SNMP parameters have been entered, press <Control C> to save the information. The
MPU will reboot at this point to activate the changes.
7.3 Charts for UI and SNMP terms comparison
The following section provides a set of charts that relate the User Interface (UI) displays and commands,
as described in Section 4, to the closest equivalent SNMP objects.
7.3.1 System / oEx2SysObjects
UI SNMP
Alarm Summary No Equivalent Entry
Heading Possible States Object Possible Values
Left Mpu/ Right Empty/ Online/ Offline
Mpu
Slots 1 thru 14 Empty/Uncfg/ Offline/ Online/
Protecting/ Minor/ Pm13/
Major/Maint/Far-End
Node (Blank)/Minor/ Major/ACO oEx2SysRelays
(See note below) Active oEx2MajorVisualRelay
oEx2MajorAudioRelay Active/ Inactive
oEx2MinorVisualRelay
oEx2MinorAudioRelay
Note: 'Node' in the Alarm Summary has no direct equivalent entry in SNMP. Hence to see the alarm
status of the node, the user must view the oEx2SysRelays table.
Discover: No equivalent SNMP object
Restore: The equivalent command in SNMP is oEx2SysRestore under oEx2SysDiagnostics, which
should be set to Perform to execute a Restore command.
TA-200 OP
8/29/03 7-3
UI SNMP
Module Info oEx2SystemInfo Table
Slot Mpu1/ Mpu2/1-14 oEx2SysInfoSlotPos Left/ Right/ 1-14
Module Type (Blank)/MPU/PM13, etc. oEx2SysInfoModuleType Ex2ModuleType*
Assembly (Blank)/ nnn-nnnnn-nnn oEx2SysInfoAssemblyNumber nnn-nnnnn-nnn
Number
Hardware Bld. (Blank)/ n oEx2SysInfoHardwareBuild 0/n
Hardware Rev (Blank)/ n oEx2SysInfoHardwareRev 0/n
Serial Number (Blank)/ nnnnnnn oEx2SysInfoSerialNumber 0/nnnnnnn
FPGA 1 Rev (Blank)/ n oEx2SysInfoFpga1Version 0/ n
FPGA 2 Rev (Blank)/ n.n oEx2SysInfoFpga1Version 0/ n
Mod Status (Blank)/Offline/Online/Norm oEx2SysInfoModuleStatus Ex2ModuleState**
RIM Type (Blank)/ 1:1 oEx2SysInfoRimType Ex2RIMType***
RIM Pos. None, Left, Right oEx2SysInfoRimPos None, left, right
* invalid, mpu, pm13, m13-T3, pm13Plus, m13Plus-T3, pm13E, m13E-T3, m13E-STS1, omx3
** online, offline, empty, missing, uncfg, protecting, fault
*** invalid, oneToOne.
7.3.2 MPU / oEx2MPUObjects

UI SNMP
Configuration oEx2MpuConfig
Baud Rate 1200, 2400, 4800, oEx2MpuBaudRate 1200baud, 2400baud, 4800baud,
9600, 19200, 38400, 9600baud, 19200baud, 38400baud,
57600, 115200, Auto 57600baud, 115200baud, Autobaud
Set Date As set by admin oEx2MpuDate As set by admin
Set Time As set by admin oEx2MpuTime As set by admin
UI SNMP
Alarm Summary oEx2MpuAlarmTable
Status Empty/ Online/ Offline oEx2MpuModuleStatus ExmModuleState **
Major Asserted/ Not Asserted * oEx2MpuAlarmStatus Major/ Minor
Minor Asserted/ Not Asserted *
WDT Asserted/ Not Asserted * oEx2WatchDogTimer Invalid, Ok, Alarm
RTC Asserted/ Not Asserted * oEx2RealTimeClock Invalid, Ok, Alarm
Comm Asserted/ Not Asserted * oEx2AdjacentComm Invalid, Ok, Alarm
* Empty/ X
** online, offline, empty, missing, unconfigured, alarm, protected
TA-200 OP
8/29/03 7-4
7.3.3 Service Module / oEx2CommonObjects
UI SNMP
oEx2GeneralDiagsTable
Protection Active, Forced oEx2GeneralDiagsProtectionSwitch Invalid, performSafeProtection,
Switch Online, Offline, performForcedProtection,
Missing, clearProtection,
Unconfigured, protectionActive,
Empty forcedProtectionActive,
noProtectionActive
Reset 1…14 oEx2GeneralDiagsRestore Invalid, perform, normal
Restore 1…14 oEx2GeneralDiagsReset Invalid, perform, normal
7.3.4 Service Module / oEx2Pm13Objects / Configuration

UI SNMP
PM13: Configuration – Line oEx2Pm13LineConfig Table
Slots 1…14 oEx2Pm13LineConfigSlotIndex 1…14
Module Empty, Pm13, oEx2Pm13LineConfigModuleType Ex2ModuleType*
etc.
Type STS-1/ T3 oEx2Pm13LineConfigPortType Ex2Pm13IfType**
Prot Switch Enabled, oEx2Pm13LineConfigProtectionEnable Invalid, Enabled,
Disabled Disabled
Hold Off None, 50ms, oEx2Pm13LineConfigHoldOffTime None, Fiftymillisec,
100ms, 500ms, Hundredmillisec, Halfsec,
1sec, 2sec, 5sec Onesec, Twosec, Fivesec
LBO <225 ft, >225 ft oEx2Pm13LineConfigLineBuildOut Ex2LBOSetting***
Timing Mode Loop, Internal oEx2Pm13LineConfigTimingMode Invalid, Loop , Internal
STS-1 T1Vt15 Transpar, oEx2Pm13LineConfigT1toVt15Mapping Invalid,
Mapping Interlvd Interleaved, Transparent
* invalid, mpu, pm13, m13-T3, pm13Plus, m13Plus-T3, pm13E, m13E-T3, m13E-STS1, omx3
** invalid, t3, sts1, au3
*** invalid, lessThan225Feet, greaterThan225Feet
UI SNMP
PM13: Configuration - Drop oEx2Pm13DropConfigTable
Slots 1…14 oEx2Pm13DropConfigSlotIndex 1…14
Module Empty, Pm13, etc. oEx2Pm13DropConfigModuleType Ex2ModuleType
LBO/ 1…28 0… 5* oEx2Pm13DropConfigT1LBOTrib[i], Ex2T1LBO**
i = 1…28
oEx2Pm13DropConfigTrib[i]LnCode, Invalid, b8zs, ami
i = 1…28
* 0: Ports Disabled, 1: 0 – 133, 2: 133- 266, 3: 266- 399, 4: 399- 533, 5: 533- 655
** invalid, lessThan133, range133-266, range266-399, range399-533, range533-655
• Service Module / oEx2Pm13Objects (Cont.)
TA-200 OP
8/29/03 7-5
UI SNMP
PM13: Configuration – Inband oEx2Pm13InbandLoopbackConfigTable
Loopback
Heading Possible Object Possible Values
States
Slot Pairs (1,2)...(1 oEx2Pm13InbandLoopbackConfigSlotIndex 1…14
3,14)
Module Type Pm13, oEx2Pm13InbandLoopbackConfigModuleType Ex2ModuleType
etc. *
oEx2Pm13InbandLoopbackConfigModuleState Ex2ModuleState
**
Enable/ Trib. Enabled, oEx2Pm13InbandLoopbackConfigTrib1to7Respons Ex2Pm13Inband-
Disable 1-7 Disabled e LoopbackRespon
Response Trib. oEx2Pm13InbandLoopbackConfigTrib8to14Respo se***
8-14 nse
Trib. oEx2Pm13InbandLoopbackConfigTrib15to21Resp
15-21 onse
Trib. oEx2Pm13InbandLoopbackConfigTrib22to28Resp
22-28 onse
Inband Trib. 0-255 oEx2Pm13InbandLoopbackConfigTrib1to7- DisplayString***
Loopback 1-7 ActivatePattern *
Activation Trib. oEx2Pm13InbandLoopbackConfigTrib8to14-
Pattern 8-14 ActivatePattern
Trib. oEx2Pm13InbandLoopbackConfigTrib15to21-
15-21 ActivatePattern
22-28 ActivatePattern
Inband Trib. 0-255 oEx2Pm13InbandLoopbackConfigTrib1to7- DisplayString***
Loopback 1-7 DeactivatePattern *
DeActivation Trib. oEx2Pm13InbandLoopbackConfigTrib8to14-
Pattern 8-14 DeactivatePattern
15-21 DeactivatePattern
22-28 DeactivatePattern
* invalid, mpu, pm13, m13-T3, pm13Plus, m13Plus-T3, pm13E, m13E-T3, m13E-STS1, omx3,
omxT3
** invalid, empty, unconfigured, configured, missing, rimMissing, online, offline
*** invalid, enabled, disabled
**** A string of 8, ‘0’s and ‘1’s
TA-200 OP
8/29/03 7-6
UI SNMP
Module Alarm Summary oEx2Pm13AlarmTable
Slot Type STS1, T3 oEx2Pm13AlarmPortType Ex2Pm13IfType
Slot State Empty, Unused, Missing, oEx2Pm13AlarmModuleStatu Ex2ModuleState
Online, Offline s
Alarm State Minor, Major oEx2Pm13AlarmAlarmStatus Ex2AlarmState*
Board Alm Asserted/ Not Asserted ** oEx2Pm13AlarmFpga Ex2AlarmOnOff***
T1 Alarm Asserted/ Not Asserted ** oEx2Pm13AlarmT1 Ex2AlarmOnOff***
LOS Asserted/ Not Asserted ** oEx2Pm13AlarmLOS Ex2AlarmOnOff***
OOF Asserted/ Not Asserted ** oEx2Pm13AlarmOOF Ex2AlarmOnOff***
AIS Asserted/ Not Asserted ** oEx2Pm13AlarmAIS Ex2AlarmOnOff***
No Out Asserted/ Not Asserted ** oEx2Pm13AlarmNoOutput Ex2AlarmOnOff***
T3 T2 OOF Asserted/ Not Asserted ** oEx2Pm13AlarmT2OOF 0…127 ****
T3 X-Bit Asserted/ Not Asserted ** oEx2Pm13AlarmT3Xbit Ex2AlarmOnOff***
T3 T2 X-Bit Asserted/ Not Asserted ** oEx2Pm13AlarmT2Xbit 0…127 ****
Sts-1 LOP Asserted/ Not Asserted ** oEx2Pm13AlarmSts1LOP Ex2AlarmOnOff***
Sts-1 SLM Asserted/ Not Asserted ** oEx2Pm13AlarmSts1SLM Ex2AlarmOnOff***
Sts-1 VT Asserted/ Not Asserted ** oEx2Vt15SmryLOP Ex2AlarmOnOff***
Alarm oEx2Vt15SmryAIS Ex2AlarmOnOff***
oEx2Vt15SmryRDI Ex2AlarmOnOff***
* noAlarm, minor, major, critical
** The UI screen actually shows X for Asserted and (Blank) for Not Asserted.
*** asserted, notactive
**** 0 means no alarm. To interpret the DS2s in alarm, any number is first converted to binary. For
example, if the output is 64, 01000000, then DS2 # 7 is in alarm. If the output is 15,
00001111, then DS2 # 1, DS2 # 2, DS2 # 3, DS2 # 4 are in alarm and so on.
UI SNMP
Performance Summary oEx2Pm13PerformanceEntry
Slot State Empty, Unused, oEx2Pm13PerformanceModuleStatus Ex2ModuleState*
Missing, Online,
Offlne
T3/ B2 SES 0…n oEx2Pm13PerformanceT3B2Ses 0…65535
T3 Frame C-Bit Parity, oEx2Pm13PerformanceT3Framing Ex2Pm13FramingType*
M13
T3 Parity ES 0…n oEx2Pm13PerformanceT3ParityES 0…65535
T3 Path ES 0…n oEx2Pm13PerformanceT3PathES 0…65535
T3 Far End 0…n oEx2Pm13PerformanceT3FarendES 0…65535
ES
Sts-1 B1 ES 0…n oEx2Pm13PerformanceSts1B1ES 0…65535
Sts-1 B2 ES 0…n OEx2Pm13PerformanceSts1B2ES 0…65535
* invalid, cbit, m13
TA-200 OP
8/29/03 7-7
UI SNMP
Performance History : Line oEx2Pm13LinePerfHistEntry
States
Slot Num 1…14 oEx2Pm13LinePerfHistSlotNumber Ex2SlotSelection*
15 Min. Interval 1…96 oEx2Pm13LinePerfHistTimeInterval 1…96
Select
Elapsed 15 Minute 0…900 oEx2Pm13LinePerfHistElapsedTime 0…900
Time
15 Min. Line ES oEx2Pm13Line15MinLnCodeEs
Code Violations SES 0…900 oEx2Pm13Line15MinLnCodeSes 0…900
15 Min ES oEx2Pm13Line15MinT3PBitSts1B1Es
T3 P-Bit/ SES 0…900 oEx2Pm13Line15MinT3PBitSts1B1Ses 0…900
STS-1 B1
15 Min T3 C-PAR ES oEx2Pm13Line15MinT3CParSts1B2Es
STS-1 B2 0…900 0…900
SES oEx2Pm13Line15MinT3CParSts1B2Ses
15 Min. ES 0…900 oEx2Pm13Line15MinT3FebeEs 0…900
FEBE SES oEx2Pm13Line15MinT3FebeSes
24 Hr. Line ES oEx2Pm13Line24HrLnCodeEs 0…86400
Code Violations SES 0…8640 oEx2Pm13Line24HrLnCodeSes
0
24 Hr. ES 0…8640 oEx2Pm13Line24HrParityB2Es 0…86400
Parity/B2 SES 0 oEx2Pm13Line24HrParityB2Ses
24 Hr. ES 0…8640 oEx2Pm13Line24HrCParityEs 0…86400
C-PAR SES 0 oEx2Pm13Line24HrCParitySes
24 Hr. ES 0…8640 oEx2Pm13Line24HrFebeEs 0…86400
FEBE SES 0 oEx2Pm13Line24HrFebeSes
UI SNMP
Performance History : VT15 oEx2Pm13Vt15PerfHistEntry
Heading Possible Object Possible
States Values
Slot Num 1…14 oEx2Pm13Vt15PerfHistSlotNumber Ex2SlotSe
lection*
15 Min. Interval 1…96 oEx2Pm13Vt15PerfHistTimeInterval 1…96
Select
Elapsed 15 Minute 0…900 oEx2Pm13Vt15PerfHistElapsedTime 0…900
Time
15 Min. ES 0…900 oEx2Pm13Vt15- oEx2Pm13Vt15PerfHist15MinEs 0…900
Tribs 15 Min. SES 0…900 PerfHist- oEx2Pm13Vt15PerfHist15MinSes 0…900
1- 28 24 Hr. ES 0…86400 TribNumber oEx2Pm13Vt15PerfHist24HrEs 0…86400
24 Hr. SES 0…86400 oEx2Pm13Vt15PerfHist24HrSes 0…86400
TA-200 OP
8/29/03 7-8
UI SNMP
Performance History : DROP oEx2Pm13DropHistPerfEntry
States Values
Slot Num 1…14 oEx2Pm13DropPerfHistSlotNumber Ex2Slot-
Selection*
15 Min. Interval 1…96 oEx2Pm13DropPerfHistTimeInterval 1…96
Select
Elapsed 15 Minute 0…900 oEx2Pm13DropPerfHistElapsedTime 0…900
Time
15 Min. ES 0…900 oEx2Pm13- oEx2Pm13DropPerfHist15MinBpvEs 0…900
Tribs 15 Min. SES 0…900 DropPerf- oEx2Pm13DropPerfHist15MinBpvSes 0…900
1- 28 24 Hr. ES 0…86400 HistTrib- oEx2Pm13DropPerfHist24HrBpvEs 0…86400
24 Hr. SES 0…86400 Number oEx2Pm13DropPerfHist24HrBpvSes 0…86400
UI SNMP
VT1.5 Alarm Details* oEx2Pm13VT15AlarmTable
LOP Asserted/ Not Asserted OEx2Pm13Vt15DetailedLOP Ex2AlarmOnOff
AIS Asserted/ Not Asserted oEx2Pm13Vt15DetailedAIS Ex2AlarmOnOff
RDI Asserted/ Not Asserted oEx2Pm13Vt15DetailedRDI Ex2AlarmOnOff
ES 0…n oEx2Pm13Vt15Es 0…65535
SES 0…n oEx2Pm13Vt15Ses 0…65535
UI SNMP
T1 Alarm Details oEx2Pm13T1AlarmTable
LOS Asserted/ Not Asserted oEx2Pm13T1LOS Ex2AlarmOnOff
AIS Asserted/ Not Asserted oEx2Pm13T1AIS Ex2AlarmOnOff
BPV 0…n oEx2Pm13T1Bpv 0…65535
UI SNMP
T3 Alarm Detail OEx2Pm13T3AlarmTable
State Empty, Unused, Missing, Online, oEx2Pm13T3ModuleStatus Ex2ModuleState
Offline
T3 LOS Asserted/ Not Asserted oEx2Pm13T3T3LOSAlarm Ex2AlarmOnOff
T3 OOF Asserted/ Not Asserted oEx2Pm13T3T3OOFAlarm Ex2AlarmOnOff
T2 OOF 1…7 Asserted/ Not Asserted oEx2Pm13T3T2OOFTrib[i] Ex2AlarmOnOff
i = 1…7
T2 X- BIT Asserted/ Not Asserted oEx2Pm13T3T2XbitTrib[i] Ex2AlarmOnOff
1…7 i = 1…7
TA-200 OP
8/29/03 7-9
7.3.5 Service Module / oEx2Pm13Objects / Diagnostics
UI SNMP
Loopback oEx2Pm13LoopbackDiagsTable
States
Slot 1…14 oEx2Pm13LoopbackDiagsSlotIndex 1…14
Line Loopback Asserted/Not oEx2Pm13LoopbackDiagsLineLoopback Clear, active
Active
T1 to Line All/ 1…28 oEx2Pm13LoopbackLineTrib[i], i = Ex2Pm13LineLoopback-
Status 1..28 Selection *
Command
Drop Side All/ 1…28 oEx2Pm13LoopbackDropTrib[i], i = Ex2Pm13DropLoopback-
1..28 Selection **
* invalid, clear, local, farend, remote, local-remote
** invalid, clear, local, activateFarendInband, deactivateFarendInband, remote, local-remote
UI SNMP
T1 Test Configuration OEx2Pm13TestTable
Slot 1…14 oEx2Pm13TestSlotIndex 1…14
Pattern Normal/ Inverted oEx2Pm13TestPolarity Invalid, normal,
Polarity inverted
Test Generator QRSS, 2\23-1, 2\20- oEx2Pm13TestGeneratorPattern Invalid, qrss, 2 exp 23-
P*attern 1, 2\15-1 1,
2 exp 20-1, 2 exp 15-1
Test Generator Framed/ Unframed oEx2Pm13TestGeneratorFraming Invalid, Framed,
Framing Unframed
Test Generator Line/ Drop oEx2Pm13TestGeneratorDirection Invalid, lineSide,
Direction dropSide
Test Generator 1…28 for T3/ oEx2Pm13TestGeneratorTributaries 0…268435456*
Tributaries Vt. Number/ Group
Number 1…4/ 1…7
*
Test Receiver QRSS, 2\23-1, 2\20- oEx2Pm13TestReceiverPattern Invalid, qrss, 2 exp 23-
Pattern 1, 2\15-1 1,
2 exp 20-1, 2 exp 15-1
Test Receiver Framed/ Unframed oEx2Pm13TestReceiverFraming Invalid, Framed,
Framing Unframed
Test Receiver Line/ Drop oEx2Pm13TestReceiverDirection Invalid, lineSide,
Direction dropSide
Test Receiver 1…28 for T3/ oEx2Pm13TestReceiverTributary 0-28
Tributaries Number/ Group
Number 1…4/ 1…7
Received >= 0 oEx2TestReceivedErrors 0, -1, >0
Errors
* Bit-map indicating which of the tributary has been selected
TA-200 OP
8/29/03 7-10
• Service Module / oEx2Pm13Objects / oEx2Pm13Diagnostics (contd.)
UI SNMP
T1 Frame Monitor OEx2Pm13T1FrmMonTable
Slot 1…14 oEx2Pm13T1FrmMonSlotIndex 1…14
State Empty, Unused, Missing, oEx2Pm13T1FrmMonState Ex2ModuleState
Online, Offlne
T1 Trib None, 1…28 oEx2Pm13T1FrmMonTrib 0…28
Framing D4, ESF, OOF oEx2Pm13T1FrmMonFraming Invalid, noFrm, d4, esf, oof
ES 0…n oEx2Pm13T1FrmMonES 0…65535
SES 0…n oEx2Pm13T1FrmMonSES 0…65535
UI SNMP
T1 Monitor oEx2Pm13T1MonitorTable
Slot 1…14 oEx2Pm13T1MonitorSlotIndex 1…14
T1 Monitor Incoming oEx2Pm13T1MonitorDirection Invalid, inComing,
Direction outGoing
T1 Drop Trib Asserted/ Not Asserted oEx2Pm13T1DropTrib 0…28
7.3.6 Service Modules / OC3 / oEx2Omx3Objects

UI SNMP
Configuration oEx2Omx3ConfigTable
Module OC3, Pm13, etc. oEx2Omx3ConfigModuleType Ex2ModuleType
Type OC3/STM1 oEx2Omx3ConfigInterfaceType invalid, oc3, stm1
OP Mode Term/ADRP oEx2Omx3ConfigOperationMode Invalid, term, adrp
Prot Switch Enabled/ oEx2Omx3ConfigProtSwitch invalid, enabled,
Disabled disabled
Hold Off None, 50ms, oEx2Omx3ConfigHoldOffTime None, fiftyMilliSec,
100ms, 1s, 2s, hundredMilliSec,
5s fiveHundredMilliSec,
oneSec, twoSec,
fiveSec
Timing Mode Loop, Internal, oEx2Omx3ConfigPrimaryTimingMode invalid, loop,
External, Thru oEx2Omx3ConfigSecondaryTimingMode internal, external,
Pri Sec Source, Drop1, thru, source, drop1,
Drop2, Drop 3 drop2, drop3
Drop Signal Sts-1, T3, Dis, oEx2Omx3ConfigDrop1Signal invalid, sts1, t3, bp,
BP, Au3 oEx2Omx3ConfigDrop2Signal dis, au3
D1 D2 D3
oEx2Omx3ConfigDrop3Signal
Drop LBO I = LBO In oEX2Omx3ConfigDrop1Lbo Ex2LBOSetting*
D1 D2 D3 O = LBO Out oEX2Omx3ConfigDrop2Lbo
oEX2Omx3ConfigDrop3Lbo
* invalid, lessThan225Feet, greaterThan225Feet
TA-200 OP
8/29/03 7-11
• Service Module / oEx2Omx3Objects (Cont.)
UI SNMP
Alarm Summary oEx2Omx3AlarmTable
Type OMX3, Pm13, etc. oEx2Omx3AlarmModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Omx3AlarmSlotState Ex2ModuleState
Board Alarm Asserted/ Not Asserted oEx2Omx3AlarmBoard Ex2AlarmOnOff
Oc3 LOS Asserted/ Not Asserted oEx2Omx3AlarmLOS Ex2AlarmOnOff
Oc3 LOF Asserted/ Not Asserted oEx2Omx3AlarmLOF Ex2AlarmOnOff
Oc3 AIS Asserted/ Not Asserted oEx2Omx3AlarmAIS Ex2AlarmOnOff
Oc3 RDI Asserted/ Not Asserted oEx2Omx3AlarmRDI Ex2AlarmOnOff
Oc3 Path Asserted/ Not Asserted oEx2Omx3AlarmPathSmry Ex2AlarmOnOff
Drop 1 ALM Asserted/ Not Asserted oEx2Omx3AlarmDrop1Smry Ex2AlarmOnOff
UI SNMP
Path Alarm Details oEx2Omx3PathAlarmTable
Type OMX3, Pm13, etc. oEx2Omx3PathAlarmModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Omx3PathAlarmModuleState Ex2ModuleState
Path LOP Asserted/ Not Asserted OEx2Omx3PathAlarmLOP Ex2AlarmOnOff
Path AIS Asserted/ Not Asserted OEx2Omx3PathAlarmAIS Ex2AlarmOnOff
Path SLM Asserted/ Not Asserted OEx2Omx3PathAlarmSLM Ex2AlarmOnOff
Path RDI Asserted/ Not Asserted oEx2Omx3PathAlarmRDI Ex2AlarmOnOff
UI SNMP
Drop 1/2/3 Alarm Table oEx2Omx3DropAlarmTable
No Equivalent Entry in UI oEx2Omx3DropAlarmDropNum invalid, drop1, drop2,
drop3
Type OMX3, Pm13, etc. oEx2Omx3DropAlarmModuleType Ex2ModuleType
State Online, Offline, etc oEx2Omx3DropAlarmModuleState Ex2ModuleState
Sts-1 LOS Asserted/ Not Asserted oEx2Omx3DropAlarmSTS1LOS Ex2AlarmOnOff
Sts-1 LOF Asserted/ Not Asserted oEx2Omx3DropAlarmSTS1LOF Ex2AlarmOnOff
Sts-1 LOP Asserted/ Not Asserted oEx2Omx3DropAlarmSTS1LOP Ex2AlarmOnOff
Sts-1 AIS Asserted/ Not Asserted oEx2Omx3DropAlarmSTS1AIS Ex2AlarmOnOff
Sts-1 SLM Asserted/ Not Asserted oEx2Omx3DropAlarmSTS1SLM Ex2AlarmOnOff
Sts-1 RDI Asserted/ Not Asserted oEx2Omx3DropAlarmSTS1RDI Ex2AlarmOnOff
T3 LOS Asserted/ Not Asserted oEx2Omx3DropAlarmT3LOS Ex2AlarmOnOff
T3 OOF Asserted/ Not Asserted oEx2Omx3DropAlarmT3OOF Ex2AlarmOnOff
T3 AIS Asserted/ Not Asserted oEx2Omx3DropAlarmT3AIS Ex2AlarmOnOff
T3 RAI Asserted/ Not Asserted oEx2Omx3DropAlarmT3RAI Ex2AlarmOnOff
TA-200 OP
8/29/03 7-12
• Service Module / oEx2Omx3Objects (Cont.)
UI SNMP
Performance Summary oEx2Omx3PerformanceTable
Type OMX3, Pm13, etc. oEx2Omx3PerformanceModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Omx3PerformanceModuleState Ex2ModuleState
Oc3 B1 ES 0…65535 oEx2Omx3PerformanceOc3B1ES 0…65535
Oc3 B1 Ses 0…65535 oEx2Omx3PerformanceOc3B1SES 0…65535
Oc3 B2 Es 0…65535 oEx2Omx3PerformanceOc3B2ES 0…65535
Oc3 B2 Ses 0…65535 oEx2Omx3PerformanceOc3B2SES 0…65535
Drop1 Es 0…65535 oEx2Omx3PerformanceDrop1ES 0…65535
Drop1 Ses 0…65535 oEx2Omx3PerformanceDrop1SES 0…65535
Drop2 Es 0…65535 oEx2Omx3PerformanceDrop2SES 0…65535
Drop3 Es 0…65535 oEx2Omx3PerformanceDrop3SES 0…65535
UI SNMP
Performance History oEx2Omx3PerfHistoryObjects
States Values
Slot Num 1…14 oEx2Omx3PerfHistSlotNumber Ex2Slot-
Selection*
15 Min. Interval Select 1…96 oEx2Omx3PerfHistTimeInterval 1…96
Elapsed 15 Minute Time 0…900 oEx2Omx3PerfHistElapsedTime 0…900
15 Min. ES 0…900 oEx2Omx3PerfHist15MinOc3Stm1SectionEs 0…900
OC-3/STM-1 15 Min. SES 0…900 oEx2Omx3PerfHist15MinOc3Stm1SectionSes 0…900
Section 24 Hr. ES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1SectionEs 0…86400
Errors (B1) 24 Hr. SES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1SectionSes 0…86400
15 Min. ES 0…900 oEx2Omx3PerfHist15MinOc3Stm1LineEs 0…900
OC-3/STM-1 15 Min. SES 0…900 oEx2Omx3PerfHist15MinOc3Stm1LineSes 0…900
Line Errors 24 Hr. ES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1LineEs 0…86400
(B2) 24 Hr. SES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1LineEs 0…86400
15 Min. ES 0…900 oEx2Omx3PerfHist15MinOc3Stm1Path1Es 0…900
OC-3/STM- 15 Min. SES 0…900 oEx2Omx3PerfHist15MinOc3Stm1Path1Ses 0…900
1 Path #1 24 Hr. ES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1Path1Es 0…86400
24 Hr. SES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1Path1Ses 0…86400
OC-3/STM- 15 Min. SES 0…900 oEx2Omx3PerfHist15MinOc3Stm1Path2Ses 0…900
1 Path #2 24 Hr. ES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1Path2Es 0…86400
OC-3/STM-1 15 Min. SES 0…900 oEx2Omx3PerfHist15MinOc3Stm1Path3Ses 0…900
Path #3 24 Hr. ES 0…86400 oEx2Omx3PerfHist24HrOc3Stm1Path3Es 0…86400
TA-200 OP
8/29/03 7-13
UI SNMP
Loopback Control oEx2Omx3LoopbackTable
Type OMX3, Pm13, etc. oEx2Omx3LoopbackModuleType Ex2ModuleType
State Online, Offline, oEx2Omx3LoopbackModuleState Ex2ModuleState
etc.
Oc3 Line Asserted/ Not oEx2Omx3LoopbackOc3LineLoopback invalid, asserted,
Asserted notAsserted
Sts-1/ T3 Drop 1 Asserted/ Not oEx2Omx3LoopbackDrop1ToLine invalid, asserted,
(Drop 1 to Line) Asserted notAsserted
Oc3 Drop Asserted/ Not oEx2Omx3LoopbackOc3DropLoopback invalid, asserted,
Asserted notAsserted
Sts-1/ T3 Drop 1 Asserted/ Not oEx2Omx3LoopbackDrop1ToDrop invalid, enabled,
(Drop 1 to Drop) Asserted disabled
Sts-1/ T3 Drop 1 Asserted/ Not oEx2Omx3LoopbackDrop2ToDrop invalid, asserted,
(Drop 2 to Drop) Asserted notAsserted
Sts-1/ T3 Drop 1 Asserted/ Not oEx2Omx3LoopbackDrop3ToDrop invalid, asserted,
(Drop 3 to Drop) Asserted notAsserted
7.3.7 Service Module / PM13E/ oEx2Pm13EObjects
UI SNMP
PM13E: Configuration – Line oEx2Pm13ELineConfig Table
Slots 1…14 oEx2Pm13ELineConfigSlotIndex 1…14
Module Empty, Pm13, etc. oEx2Pm13ELineConfigModuleType Ex2ModuleType
State Online, offline, etc. oEx2Pm13ELineConfigModuleState Ex2ModuleState
If Type STS-1/ T3/AU3 oEx2Pm13ELineConfigInterfaceType Ex2Pm13IfType*
Prot Switch Enabled, Disabled oEx2Pm13ELineConfigProtectionState Invalid, Enabled,
Disabled
Hold Off None, 50ms, oEx2Pm13ELineConfigHoldOffTime None, Fiftymillisec,
100ms, 500ms, Hundredmillisec,
1sec, 2sec, 5sec Halfsec, Onesec,
Twosec, Fivesec
LBO <225 ft, >225 ft oEx2Pm13ELineConfigLineBuildOut Ex2LBOSetting**
Timing Mode Loop, Internal oEx2Pm13ELineConfigTimingMode Invalid, Loop , Internal
STS-1 Transpar, Interlvd oEx2Pm13ELineConfigT1toVt15Map Invalid,
T1Vt15 ping Interleaved,
Mapping Transparent
* invalid, t3, sts1, au3
** invalid, lessThan225Feet, greaterThan225Feet
TA-200 OP
8/29/03 7-14
UI SNMP
PM13E: Configuration – Drop oEx2Pm13EDropConfig Table
Slots 1…14 oEx2Pm13EDropConfigSlotIndex 1…14
Module Empty, Pm13, etc. oEx2Pm13EDropConfigModuleType Ex2ModuleType
State Online, etc. oEx2Pm13EDropConfigModuleState Ex2ModuleState
LineCode/ 0… 5** oEx2Pm13EDropConfigTrib[I]LnCode Ex2Pm13ELineCode*
1…21 I = 1…21
* invalid, hdb3, ami, disabled
UI SNMP
Performance Summary oEx2Pm13EPerfromanceEntry
Module Empty, Pm13, etc. oEx2Pm13EPerformanceModuleType Ex2ModuleType
Slot State Online, Offline, oEx2Pm13EPerformanceModuleState Ex2ModuleState
etc.
T3 Frame C-Bit Parity, M13 oEx2Pm13EPerformanceT3Frame Invalid, C-Bit Parity,
M13
T3/ B2 SES 0…n oEx2Pm13EPerformanceT3B2SES 0…65535
T3 Parity ES 0…n oEx2Pm13EPerformanceT3ParityES 0…65535
T3 Path ES 0…n oEx2Pm13EPerformanceT3PathES 0…65535
T3 Far End ES 0…n oEx2Pm13EPerformanceT3FebeES 0…65535
Sts-1/Au3 B1 0…n oEx2Pm13EPerformanceSts1B1ES 0…65535
ES
Sts-1/Au3 B2 0…n oEx2Pm13EPerformanceSts1B2ES 0…65535
ES
TA-200 OP
8/29/03 7-15
• Service Module / oEx2Pm13EObjects (Cont.)
UI SNMP
Module Alarm Summary oEx2Pm13EAlarmTable
Module Empty, Pm13, etc. oEx2Pm13EAlarmModuleType Ex2ModuleType
Slot State Online, Offline, etc. oEx2Pm13EAlarmModuleState Ex2ModuleState
Brd Alm Asserted/ Not Asserted oEx2Pm13EAlarmBoard Ex2AlarmOnOff
T1 Alm Asserted/ Not Asserted oEx2Pm13EAlarmE1 Ex2AlarmOnOff
LOS Asserted/ Not Asserted oEx2Pm13EAlarmLOS Ex2AlarmOnOff
OOF Asserted/ Not Asserted oEx2Pm13EAlarmOOF Ex2AlarmOnOff
AIS Asserted/ Not Asserted oEx2Pm13EAlarmAIS Ex2AlarmOnOff
No Out Asserted/ Not Asserted oEx2Pm13EAlarmNoOutput Ex2AlarmOnOff
T3 G747 OOF Asserted/ Not Asserted oEx2Pm13EAlarmT3G747OOF Ex2AlarmOnOff
T3 X-Bit Asserted/ Not Asserted oEx2Pm13EAlarmT3Xbit Ex2AlarmOnOff
T3 G747 FE Asserted/ Not Asserted oEx2Pm13EAlarmT3G47FE Ex2AlarmOnOff
Sts-1 LOP Asserted/ Not Asserted oEx2Pm13EAlarmSts1Au3LOP Ex2AlarmOnOff
Sts-1 SLM Asserted/ Not Asserted oEx2Pm13EAlarmSts1Au3SLM Ex2AlarmOnOff
Sts-1 VT2/VC Asserted/ Not Asserted oEx2Pm13EVtVcSmryLOP Ex2AlarmOnOff
Summary oEx2Pm13EVtVcSmryAIS Ex2AlarmOnOff
Alarms oEx2Pm13EVtVcSmryRDI Ex2AlarmOnOff
E1 Smry LOS Asserted/ Not Asserted oEx2Pm13EE1SmryLOS Ex2AlarmOnOff
E1 Smry AIS Asserted/ Not Asserted oEx2Pm13EE1SmryAIS Ex2AlarmOnOff
TA-200 OP
8/29/03 7-16
• Service Module / oEx2Pm13EObjects (Cont.)
UI SNMP
Performance History : Line oEx2Pm13eLinePerfHistEntry
States Values
Slot Num 1…14 oEx2Pm13eLinePerfHistSlotNumber Ex2Slot-
Selection*
15 Min. Interval 1…96 oEx2Pm13eLinePerfHistTimeInterval 1…96
Select
Elapsed 15 Minute 0…900 oEx2Pm13eLinePerfHistElapsedTime 0…900
Time
15 Min. Line Code ES oEx2Pm13eLine15MinLnCodeEs
Violations SES 0…900 oEx2Pm13eLine15MinLnCodeSes 0…900
15 Min T3 P-Bit/ ES oEx2Pm13eLine15MinT3PBitSts1B1Es

STS-1 B1 SES 0…900 oEx2Pm13eLine15MinT3PBitSts1B1Ses 0…900
15 Min T3 C-PAR ES oEx2Pm13eLine15MinT3CParSts1B2Es

STS-1 B2 0…900 0…900
SES oEx2Pm13eLine15MinT3CParSts1B2Ses
15 Min. FEBE ES 0…900 oEx2Pm13eLine15MinT3FebeEs 0…900
SES oEx2Pm13eLine15MinT3FebeSes
24 Hr. Line Code ES oEx2Pm13eLine24HrLnCodeEs 0…86400
Violations SES 0…86400 oEx2Pm13eLine24HrLnCodeSes
24 Hr. ES 0…86400 oEx2Pm13eLine24HrParityB2Es 0…86400
Parity/B2 SES oEx2Pm13eLine24HrParityB2Ses
24 Hr. ES 0…86400 oEx2Pm13eLine24HrCParityEs 0…86400
C-PAR SES oEx2Pm13eLine24HrCParitySes
24 Hr. ES 0…86400 oEx2Pm13eLine24HrFebeEs 0…86400
FEBE SES oEx2Pm13eLine24HrFebeSes
UI SNMP
Performance History : VC oEx2Pm13eVtVcPerfHistEntry
States Values
Slot Num 1…14 oEx2Pm13eVtVcPerfHistSlotNumber Ex2Slot-
Selection*
15 Min. Interval 1…96 oEx2Pm13eVtVcPerfHistTimeInterval 1…96
Select
Elapsed 15 Minute 0…900 oEx2Pm13eVtVcPerfHistElapsedTime 0…900
Time
15 Min. ES 0…900 oEx2Pm13eVtVcPerfHist15MinEs 0…900
Tribs 15 Min. 0…900 oEx2Pm13e- oEx2Pm13eVtVcPerfHist15MinSes 0…900
1- 21 SES VtVcPerfHist-
24 Hr. ES 0…86400 TribNumber oEx2Pm13eVtVcPerfHist24HrEs 0…86400
24 Hr. SES 0…86400 oEx2Pm13eVtVcPerfHist24HrSes 0…86400
TA-200 OP
8/29/03 7-17
UI SNMP
Performance History : DROP oEx2Pm13eDropHistPerfEntry
States Values
Slot Num 1…14 oEx2Pm13eDropPerfHistSlotNumber Ex2Slot-
Selection*
15 Min. Interval 1…96 oEx2Pm13eDropPerfHistTimeInterval 1…96
Select
Elapsed 15 Minute 0…900 oEx2Pm13eDropPerfHistElapsedTime 0…900
Time
15 Min. ES 0…900 oEx2- oEx2Pm13eDropPerfHist15MinBpvEs 0…900
Tribs 15 Min. SES 0…900 Pm13e- oEx2Pm13eDropPerfHist15MinBpvSes 0…900
1- 28 24 Hr. ES 0…86400 DropPerf- oEx2Pm13eDropPerfHist24HrBpvEs 0…86400
24 Hr. SES 0…86400 HistTrib- OEx2Pm13eDropPerfHist24HrBpvSes 0…86400
Number
UI SNMP
VT2/VC1.2 Alarm Details oEx2Pm13EVtVcAlarmTable
Module Empty, Pm13, etc. oEx2Pm13EVtVcAlarmModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Pm13EVtVcAlarmModuleState Ex2ModuleState
LOP Asserted/ Not Asserted oEx2Pm13EVtVcAlarmLOP Ex2AlarmOnOff
AIS Asserted/ Not Asserted oEx2Pm13EVtVcAlarmAIS Ex2AlarmOnOff
RDI Asserted/ Not Asserted oEx2Pm13EVtVcAlarmRFI Ex2AlarmOnOff
ES 0…n oEx2Pm13EVtVcAlarmES 0…65535
SES 0…n oEx2Pm13EVtVcAlarmSES 0…65535
UI SNMP
E1 Alarm Details oEx2Pm13EE1AlarmTable
Module Empty, Pm13, etc. oEx2Pm13EE1AlarmModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Pm13EE1AlarmModuleState Ex2ModuleState
LOS Asserted/ Not Asserted oEx2Pm13EE1AlarmLOS Ex2AlarmOnOff
AIS Asserted/ Not Asserted oEx2Pm13EE1AlarmAIS Ex2AlarmOnOff
BPV 0…n oEx2Pm13EE1AlarmBpv 0…65535
UI SNMP
T3 Alarm Detail OEx2Pm13T3AlarmTable
Module Empty, Pm13, etc. oEx2Pm13ET3AlarmModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Pm13ET3AlarmModuleState Ex2ModuleState
T3 LOS Asserted/ Not Asserted OEx2Pm13ET3AlarmT3LOS Ex2AlarmOnOff
T3 OOF Asserted/ Not Asserted OEx2Pm13T3AlarmT3OOF Ex2AlarmOnOff
G747 OOF 1…7 Asserted/ Not Asserted OEx2Pm13T3AlarmG747XXOOF Ex2AlarmOnOff
XX = One, Two – Seven
G747 FarEnd Asserted/ Not Asserted OEx2Pm13T3AlarmG747XXFE Ex2AlarmOnOff
1…7 XX = One, Two – Seven
TA-200 OP
8/29/03 7-18
7.3.8 Service Module / oEx2Pm13EObjects / Diagnostics
UI SNMP
Loopback oEx2Pm13ELoopbackTable
Module Empty, Pm13, etc. oEx2Pm13ELoopbackModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Pm13ELoopbackModuleState Ex2ModuleState
Line Loopback Asserted/Not Asserted oEx2Pm13ELoopbackLineLoopback Clear, active
E1 towards Asserted/Not Asserted oEx2Pm13ELoopbackE1toLineLoopback Bit Map*
Line Loopback
E1 towards Asserted/Not Asserted oEx2Pm13ELoopbackE1toLineLoopback Bit Map*
Drop Loopback
UI SNMP
E1 Test Configuration oEx2Pm13ETestTable
Module Empty, Pm13, etc. oEx2Pm13ETestModuleType Ex2ModuleType
State Online, Offline, oEx2Pm13ETestModuleState Ex2ModuleState
etc.
Pattern Normal/ Inverted oEx2Pm13ETestPolarity Invalid, normal, inverted
Polarity
Test Generator QRSS, 2\23-1, oEx2Pm13ETestGeneratorPattern Invalid, qrss, 2 exp 23-1,
Pattern 2\20-1, 2\15-1 2 exp 20-1, 2 exp 15-1
Test Generator Framed/ oEx2Pm13ETestGeneratorFraming Invalid, Framed,
Framing Unframed Unframed
Test Generator Line/ Drop oEx2Pm13ETestGeneratorDirection Invalid, lineSide,
Direction dropSide
Test Generator 1…21 for T3/ oEx2Pm13ETestGeneratorTributaries Bit Map*
Tributaries Vt. Number/
Group Number
1…4/ 1…7
Test Receiver QRSS, 2\23-1, oEx2Pm13ETestReceiverPattern Invalid, qrss, 2 exp 23-1,
Pattern 2\20-1, 2\15-1 2 exp 20-1, 2 exp 15-1
Test Receiver Framed/ oEx2Pm13ETestReceiverFraming Invalid, Framed,
Framing Unframed Unframed
Test Receiver Line/ Drop oEx2Pm13ETestReceiverDirection Invalid, lineSide,
Direction dropSide
Test Receiver 1…21 for T3/ oEx2Pm13ETestReceiverTributary 0-21
Tributaries Number/ Group
Number
1…4/ 1…7
Received >= 0 oEx2Pm13ETestReceivedErrors 0, -1, >0
Errors
TA-200 OP
8/29/03 7-19
• Service Module / oEx2Pm13Objects / oEx2Pm13Diagnostics (contd.)
UI SNMP
E1 Frame Monitor oEx2Pm13EE1FrmMonTable
Module Empty, Pm13, etc. oEx2Pm13EE1FrmMonModuleType Ex2ModuleType
State Online, Offline, etc. oEx2Pm13EE1FrmMonModuleState Ex2ModuleState
E1 Tributary None, 1…21 oEx2Pm13EE1FrmMonTrib 0…21
E1 Framing D4, ESF, OOF oEx2Pm13EE1FrmMonFraming Invalid, d4, esf, oof
ES 0…n oEx2Pm13EE1FrmMonES 0…65535
SES 0…n oEx2Pm13EE1FrmMonSES 0…65535
UI SNMP
E1 Front Panel Monitor oEx2Pm13EE1FrtPnlTable
Module Empty, Pm13, etc. oEx2Pm13EE1FrtPnlMonModuleType Ex2ModuleType
State Online, Offline, oEx2Pm13EE1FrtPnlMonModuleState Ex2ModuleState
etc.
E1 Monitor Incoming oEx2Pm13EE1FrtPnlMonDirection Invalid, inComing,
Direction outGoing
E1 Drop Trib Asserted/ Not oEx2Pm13EE1FrtPnlMonDropTrib 0…21
Asserted
TA-200 OP
8/29/03 7-20
8 TRANSACTION LANGUAGE 1 (TL1)
TL1 management capability is an TransAccess 200 feature that provides standards-based ways to
remotely manage the TransAccess 200 from anywhere on the network. The TransAccess 200 MPU must
be equipped with an Ethernet Auxiliary board to enable TL1 and Telnet functionality. If redundant MPUs
are equipped, both must have Ethernet Auxiliary boards installed. If your TransAccess 200 was not
factory-equipped for Ethernet, it may be upgraded in the field by ordering Ethernet Aux. Board, (consult
Turin sales or customer service for part number), for each MPU and install them per the instructions
included. If you have an early TransAccess 200 shelf without an on-board network connector on the
backplane, an interface adapter, (consult Turin sales or customer service for part number), should also be
ordered from Turin Networks.
additional upgrades are necessary to support TL1.
8.1 TL1 Management Station
Turin Networks does not supply a TL1 management platform or application. It is assumed that the
Customer has, or will provide, a networked computer with standards-compliant TL1 management
application suites installed. Only one TL1 session can be opened at a time.
8.2 Connect the TransAccess 200 to the Network
Connect a Customer-provided standard Category 5 Unshielded Twisted Pair (UTP) cable terminated with
a modular connector to the RJ45 jack located near the rear of the left side of the TransAccess 200 shelf.
The other end of this cable should be connected to a 10Base-T Ethernet access point on the Internet
Protocol (IP) network used by the TL1 Management platform.
8.3 Configuring the TransAccess 200 for TL1 Operation
The following information must be available before proceeding.
• IP Address
• IP Network Address Mask
• Default Gateway IP Address
• The Community Name for read-write access, and optionally, the IP address of the TL1
management station if read-write access is to be limited to a single station. (This parameter is not
• The Community Name for read-only access, and optionally, the IP address of the TL1
management station if read-only access is to be limited to a single station. (This parameter is not
Connect the User Interface Device (UID) to the TransAccess 200 as described in Chapter 4 and log in as a
level 3 or level 4 user.
Using the UID, select MPU from the top-level menu, and select Configuration from the resulting menu as
shown in Figure 8-1. Select the IP/SNMP Config menu to input the IP address information for the
TransAccess 200 system. The IP address must also be programmed for TL1. Figure 8-2 shows the IP
Configuration Screen.
TA-200 OP
8/29/03 8-1
Figure 8-2: TCP/IP Configuration Screen
TA-200 OP
8/29/03 8-2
8.3.1 Telnet Configuration Menu
By selecting Telnet Configuration, three configuration items will be displayed as shown in Figure 8-3.
First, a selection for UI or TL1 will be displayed. Choosing UI will configure the TransAccess 200 to use
the graphical user interface menus during a telnet session and provide access for the use of the
TransAccess 200 Web Browser management interface. If TL1 is selected, the UI Interface via Telnet will
accept TL1 command messages and will display automatic TL1 alarms.
The third configuration choice will be to select a timeout period to disconnect a TL1 or Telnet session if
no activity is detected in a certain period of time. The selectable time period is from 0 to 60 minutes. If 0
is selected, no timeout will occur.
After making all selections, enter a 4 to save and implement the changes. The changes will take affect at
the next Telnet login.
Figure 8-3: SNMP Port Configuration
8.3.2 Disconnect a Telnet Session

In order to prevent logout problems if a user does not disconnect a telnet session when done, a command
will be added to manually disconnect the telnet session from the UID menu. Please refer to Figure 8-4.
TA-200 OP
8/29/03 8-3
Figure 8-4: Telnet Disconnect Screen
8.4 TL1 Command Set
This section describes the commands, responses, and automatic messages for the TL1 interface of the
TransAccess 200.
8.4.1 TL1 FORMAT
This section describes the TL1 command codes for TransAccess 200. The following is a
description of notations, symbols, and conventions used when describing TL1 command
responses or TL1 command formats.
cr indicates a carriage return
lf indicates a line feed
^ indicates a space appearing in the message
[] encloses parameters that are optional
<> encloses parameters that are determined by current events or commands
{} indicates a range of numbers
{|} indicates that one of the parameters within the {} and separated by the pipe |
must be used.
& indicates an ‘and’ function when displaying values (ex. 1&6)
&& indicates a range of values (ex. 1&&6)
8.4.2 General Syntax
Brief descriptions of the syntax for commands and responses are given here. TL1 syntax is described in
detail in Telcordia GR-833-CORE.
8.4.2.1 Command Syntax
All TL1 commands have the following general format:
Verb[-Modifier[-Modifier]]:[Target_ID]:[<aid>]:<ctag>::[Parameter];
TA-200 OP
8/29/03 8-4
The parts of the command shown between square brackets are optional, however some of these options
may be required to successfully complete specific commands.
8.4.2.2 Response Syntax
The general format of a command response is shown below:
<cr><lf><lf> ^^^ <Source_ID> ^ <year-month-day> ^ <hour:minute:second>
<cr><lf>M ^^ <ctag>^COMPLD
<cr><lf>[Text_Block(s)<cr><lf>];
A response without a text block is used to signify that the command was received and executed. The
correlation tag <ctag> matches that of the command. The correlation tag is assigned to the command by
the user when the command is issued. In this way, a command and its associated response can be
correlated. A rejected command will be returned with a DENY and an message that describes why the
command failed.
8.4.2.3 Multiple Output Responses
In the case where the total size of a response exceeds 4096 bytes, the response is partitioned into multiple
responses. These responses have a separate header with the same <ctag>, but all except the last one use
the ‘>’ instead of the ‘;’ terminator.
8.4.3 Error Responses
Error responses have the following format:
<cr><lf><lf> ^^^ <Source_ID> ^ <year-month-day> ^ <hour:minute:second>
<cr><lf>M^^ <ctag> ^ DENY
<cr><lf> ^^^ <ERROR CODE>
(<cr><lf> ^^^ /* <Optional free format error text> */)
<cr><lf>;
For example, when an invalid or unsupported command is received by the TransAccess 200, the
following error response is transmitted:
EXMII-TL1 2002-08-30 14:42:30

M 34 DENY
ICNV
/* Input, Command Not Valid */
;
8.4.3.1 Valid Error Code Values
Valid error codes and their descriptions are shown below.
ICNV Input, Command Not Valid
IDNV Input, Data Not Valid
IIAC Input, Invalid ACcess identifier
IICT Input, Invalid Correlation Tag
IISP Input, Invalid Syntax or Punctuation
IITA Input, Invalid Target Identifier
PICC Privilege, Invalid Command Code
PIUC Privilege, Invalid User Code
PIUI Privilege, Invalid User Id
SAAL Status, Already ALlowed
SAIN Status, Already INhibited
SROF Status, Requested Operation Failed
TA-200 OP
8/29/03 8-5
8.4.4 Parameter Types
8.4.4.1 Correlation Tag

This field is represented by <ctag>. The correlation tag is used to match commands and responses. It is
sent out as part of the command, and the TransAccess 200 returns it as part of the response. The
correlation tag is assigned by the user issuing the command and can be arbitrarily chosen. Each command
issued can be assigned a different correlation tag to prevent confusing commands and responses. The
length of the correlation tag can be up to 6 alphanumeric characters (A-Z, a-z, and 0-9). An invalid
CTAG is responded with DENY and IICT error code.
8.4.4.2 Automatic Message Tag
This field is represented by <atag>. This tag is used to sequence messages from the TransAccess 200
when sending automatic alarm messages. If an out of sequence value of this tag is received by the
operating system, it means that some automatic messages may have been missed. The length of the
automatic message tag is up to 10 digits.
8.4.4.3 Target Identifier and Source Identifier
The Target IDentifier <tid> or Source Identifier <sid> specify the network element to which the
command is sent. The source identifier specifies which network element transmitted the response. The
<tid> can be up to 20 characters and is optional for the TransAccess 200. If TID is specified, it must
match the target ID of the system being addressed. If the TID does not back the system ID, a DENY
response will be returned with an IITA error message.
The examples in this document will be represented by the TransAccess 200 default name ‘EXMII-TL1’.
8.4.4.4 2nd Modifier Types
This parameter specifies the type of entity that the operating system wants to address. Fields of this type
are represented by {MOD2}.
EQPT Equipment Unit
E1 E1 Circuit
T1 T1 Circuit
VT1 VT1.5 Circuit
VT2 VT2 Circuit
T2 T2 Circuit
G747 G.747 Circuit
T3 T3 Circuit
STS1 STS-1 Circuit
OC3 OC-3 Circuit
AU3 AU3 Circuit
STM1 STM-1 Circuit
ALL or blank All access identifiers
The error response for an invalid 2nd Modifier Type is shown below.
EXMII-TL1 2002-08-30 14:42:30
M 34 DENY
ICNV
8.4.4.5 Access Identifier
TA-200 OP
8/29/03 8-6
This identifier determines which entity in the TransAccess 200 is addressed. Access identifier fields are
represented by <aid> and are used when retrieving data from the TransAccess 200.
Table 8-1: Access Identifiers

Field 2nd Modifier Description and Possible Values* Example AID
Format <slot#>-<tributary>
Circuits T1 <SLOT#>[-1-28|blank] 3-14&&20
E1 <SLOT#>[-1-21|blank] 11-6
VT1 <SLOT#>[-1-28|blank] 1-1&5
VT2 <SLOT#>[-1-21|blank] 1
T2 <SLOT#>-[1-7|blank] 5
G747 <SLOT#>-[1-7|blank] 7-2
T3 <SLOT#> 1-14
T3 <SLOT#>[-1-3|blank] 12-1
STS1 <SLOT#> 3
STS1 <SLOT#>[-1-3|blank] 3-3
AU3 <SLOT#> 1
AU3 <SLOT#>[-1-3|blank] 12
OC3 <SLOT#> ALL
STM1 <SLOT#> 1&2
PM13 EQPT {1-14|ALL} 1
PM13E EQPT {1-14|ALL} ALL
PM13+ EQPT {1-14|ALL} 11
M13T3+ EQPT {1-14|ALL} 12
M13T3 EQPT {1-14|ALL} 9&11
OMX3 EQPT {1-14|ALL} 5&&14
OMXT3 EQPT {1-14|ALL} 4
MPU – left EQPT A A
MPU - right EQPT B B
* The field after a hyphen (-) cannot contain the ‘ALL’ parameter. Leaving the field ‘blank’ is the default
for ‘ALL’.
8.4.4.6 Completion Codes

The Command Completion Codes are listed below.
COMPLD Command Received and Executed
DENY Execution Denied
TA-200 OP
8/29/03 8-7
8.4.5 Security Commands
These commands are discussed in Telcordia GR-835-CORE.
8.4.5.1 Activate User
This command opens a TL1 session. The format of this command is shown below.
ACT-USER:[<tid>]:<user-id>:<ctag>::<password>;
8.4.5.1.1 Normal Response
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.5.1.2 Error Response: Invalid User ID
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IIAC
/* Input, Invalid Access Identifier */
;
8.4.5.1.3 Error Response: Password is Null
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
IDNV
/* Input, Data Not Valid */
;
8.4.5.1.4 Error Response: Login Failed
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
PICC
/* Privilege, Illegal Command Code */
;
8.4.5.1.5 Error Response: Valid Commands when a User is Not Logged In
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
PICC
;
8.4.5.2 Cancel User
This command closes the current session. The format of this command is shown below.
CANC-USER:[<tid>]:<user-id>:<ctag>;

EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
EXMII-TL1 2002-08-30 10:30:22
TA-200 OP
8/29/03 8-8
M 80 DENY
IDNV
;
8.4.5.3 Delete-User-Security
The administrator uses this command to close the account of one or more users. Multiple users can be
deleted with a single command.
DLT-USER-SECU:[<tid>]:<user-id>:<ctag>;
The <user-id> field is the account that is to be closed. The <user-id> range is 2-15.
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.5.3.2 Error Response: Invalid or Non-Existent User ID
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IIAC
;
8.4.5.3.3 Error Response: Try to Delete Admin Password
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
PIUC
/* Privilege, Invalid User Code
;
8.4.5.3.4 Error Response: Insufficient Privilege to Execute Command
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
;
8.4.5.4 Enter-User-Security
The administrator uses this command to enter the security parameters associated with a particular user.
The result is that an account is created for the user. The format of this command is shown below.
ENT-USER-SECU:[<tid>]:<user-id>:<ctag>::<password>, , <uap>;
8.4.5.4.1 Command Parameters
ENT-USER-SECU Verb-Modifier-Modifier
tid Target ID (EXMII-TL1 is the system default)
user-id User ID: {1-15}
ctag Correlation Tag – matches responses with commands
password User Password: ASCII string up to 14 characters long
uap User Access Privilege: {RWA|RW|RD|R}
8.4.5.4.2 User Access Privilege
TA-200 OP
8/29/03 8-9
This parameter determines which commands the user can issue and is represented by <uap>.
RWA Level 4 Administrator: Can issue any command.

RW Level 3 Operator: Can issue any command except modifying passwords.
RD Level 2 Craft: Can monitor any parameter and access diagnostics.
R Level 1 Monitor: Cannot change any parameter or configuration items.
<tid> 2002-08-30 10:30:22
M <ctag> COMPLD
8.4.5.4.4 Error Response: UAP String is Invalid
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
IDNV
/* Input Data Not Valid */
;
8.4.5.4.5 Error Response: User ID Already in Use
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
PIUI
/* Privilege, Invalid User ID */
;
8.4.5.4.6 Error Response: Illegal User ID Level
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
IDNV
;
8.4.5.4.7 Error Response: Illegal Password Format
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
IDNV
;
8.4.5.4.8 Error Response: Password Already Exists
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
PIUI
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
/* Privilege, Invalid Command Code */
;
8.4.5.5 Edit-User-Security
TA-200 OP
8/29/03 8-10
The administrator uses this command to edit the security parameters associated with a particular user.
The format for this command is shown below.
ED-USER-SECU:[<tid>]:<user-id>:<ctag>::<new-user-id>,<new-password>, , <uap>;
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.5.5.2 Error Response: UAP String is Invalid
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
IDNV
;
8.4.5.5.3 Error Response: Change Admin ID or Level
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
PIUC
/* Privilege, Invalid User Code */
;
8.4.5.5.4 Error Response: Invalid or Non-Existent Old User ID
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IDNV
;
8.4.5.5.5 Error Response: New User ID Already in Use
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
IDNV
;
8.4.5.5.6 Error Response: Illegal User Password Format
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IDNV
;
8.4.5.5.7 Error Response: Attempt to Demote Only Supervisor
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
PIUC
/* Privilege, Invalid User Code */
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
TA-200 OP
8/29/03 8-11
PICC
;
8.4.5.6 Edit Password
An administrator or user uses this command to change his/her own password. Only the administrator can
change user passwords other than their own. The format of this command is shown below.
ED-PID:[<tid>]:<user-id>:<ctag>::<old-password>,<new-password>;
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.5.6.2 Error Response: Incorrect Old Password
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
PIUI
/* Old Password Incorrect */
;
8.4.5.6.3 Error Response: Illegal format for new password
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
PIUI
;
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
PIUI
;
8.4.5.6.5 Error Response: Changing Level of Admin Password
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
PIUI
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
;
8.4.5.7 Retrieve Password Information
The administrator or user uses this command to retrieve the security parameters associated with a user or
a list of users. An administrator can access the security parameters of any user, but an ordinary user can
only access his/her own parameters. The format of this command is shown below.
TA-200 OP
8/29/03 8-12
RTRV-USER-SECU:[<tid>]:UserID-1[&UserID-2&UserID3&&UserID15]:<ctag>;
The UserID format range is from 1-15. A single user ID can be entered, or several specific UserID
numbers (1&4&6, for example) or a range of numbers (4&&13, for example). If ‘ALL’ is entered, all
defined UserIDs will be returned as shown in the Normal Response below.
EXMII-TL1 2002-08-30 12:14:00
M 102 COMPLD
“UserID-1:RWA, <password>”
“UserID-2:RD,<password>”
“UserID-3:RW,<password>”
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
/* Invalid Command Code */
;
8.4.6 Configuration Commands
A user requires security level 3 or 4 to use the configuration commands.
8.4.6.1 Allow Automatic Alarms
The administrator uses this command to enable the transmission of automatic alarm messages. The
format of this command is shown below.
ALW-MSG-ALL:[<tid>]::<ctag>;
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.6.1.2 Error Response: Already Allowed
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
SAAL
/* Status, Already Allowed */
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
;
8.4.6.2 Inhibit Alarms
The administrator uses this command to disable the transmission of automatic alarm messages. The
format of this command is shown below.
TA-200 OP
8/29/03 8-13
INH-MSG-ALL:[<tid>]::<ctag>;
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.6.2.2 Error Response: Already Inhibited
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
SAIN
/* Status, Already Inhibited */
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
;
8.4.6.3 Edit System Identification
This command is used to configure the System ID (tid) for use with TL1. The format of this command is
shown below.
ED-SID:[<tid>]::<ctag>::<new SID>;

<NEW SID> 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.6.3.2 Error Response: Length of New SID is missing or longer than 20 characters
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
IDNV
;
8.4.6.3.3 Error Response: Contains Characters Other Than Alphanumeric or ‘-‘
EXMII-TL1 2002-08-30 10:30:22
M 78 DENY
IDNV
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
;
TA-200 OP
8/29/03 8-14
8.4.6.4 Edit T1/E1 LBO and Linecode (enable/disable)
This command is used to configure the LBO for T1/E1 drop ports on a PM13, PM13+, M13-T3, or
PM13E modules. The format of this command is shown below.
ED-{T1|E1}:[<tid>]:<aid>:<ctag>::<pvalue>;
The Access Identifier types are shown below (SLOT – TRIB).

T1 {1-14}-{1-28} or ALL
E1 {1-14}-{1-21} or ALL
T1/E1 <pvalue> Parameters

LBO 0 – T1 Port Disabled
1 – T1 DSX (0’ – 133’)
2 – T1 DSX (133’ – 266’)
3 – T1 DSX (266’ – 399’)
4 – T1 DSX (399’ – 533’)
5 – T1 DSX (533’ – 655’)
LINECDE Line Code: T1 – {AMI | B8ZS}

Line Code: E1 – {AMI | HDB3}
DLCID Circuit ID: ASCII string – up to 15 characters (no spaces)
PST IS – in service
OOS – out of service
TEST – enable for test only (T1=B8ZS, E1=HDB3)
If PST=OOS, all other parameters are invalid and therefore can be omitted. If configuring an E1 port, the
LBO parameter is omitted.
Here’s an example for setting the LBO for DS1 #14 on Slots 3 and 4 to 133’ – 266’, the Line Code to
AMI, and the Circuit Tag to CIRCUIT17. Quotes must be used around the circuit tag entry.
ED-T1:EXMII-TL1:3-14:651::PST=IS,LBO=2,LINECDE=AMI,DLCID=”CIRCUIT17”;

EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.6.4.2 Error Response: Invalid Access Identifier
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IIAC
/* Invalid Access Identifier */
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
TA-200 OP
8/29/03 8-15
/* Illegal Command Code */
;
8.4.6.5 Edit T1/E1 Circuit Tags
The circuit tag command can be included in the LBO and Line Code command. No spaces are allowed in
the circuit tag field.
ED-{T1|E1}:[<tid>]:<aid>:<ctag>::<pvalue>;
The Access Identifier types are shown below (SLOT – TRIB).

T1 {1-14}-{1-28}
E1 {1-14}-{1-21}
Here’s an example for setting the Circuit Tag for DS1 #14 on Slots 3 and 4 to T1Circuit14.
ED-T1:EXMII-TL1:3-14:651::DLCID=”T1Circuit14”;
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IIAC
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
;
8.4.6.6 Edit Telnet/UI Session
This command allows the administrator to end the TL1 session and allow the next session to reconnect
via Telnet rather than TL1.
ED-EQPT:[<tid>]::<ctag>::TELNETUI;

EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.6.6.2 Error Response: Illegal Format
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IDNV
TA-200 OP
8/29/03 8-16
;
EXMII-TL1 2002-08-30 10:30:22
M 67 DENY
PICC
;
8.4.7 Retrieve Commands
These commands are used to retrieve system information from the TransAccess 200 product.
8.4.7.1 Retrieve Header
This command is used to ping the TransAccess 200 system. Login is not required for this command. The
format of the command is shown below.
RTRV-HDR:::<ctag>;
EXMII-TL1 2002-08-30 10:30:22
M <ctag> COMPLD
;
8.4.7.2 Manual Request for Alarms
This section describes the commands for manually retrieving alarms from the TransAccess 200.
RTRV-ALM-{MOD2}:[<tid>]:[<aid>]:<ctag>;
Valid MOD2 parameters are T1, E1, VT1, VT2, T2, G747, T3, STS1, AU3, OC3, STM1, EQPT, or INT.
EQPT selections are used to request all alarms for a particular module. Specific alarms can be viewed for
each card slot.
The format for the <aid> is [<slot number>-<tributary>]. Slot numbers can be 1-14 or ALL.
8.4.7.2.1 Example: Retrieve all Active Alarms
RTRV-ALM-EQPT:EXMII-TL1:ALL:23;
8.4.7.2.2 Example: Retrieve all Active T1 Alarms for Slot 6

RTRV-ALM-T1:EXMII-TL1:6-1&&28:56;
8.4.7.2.3 Example: Retrieve a Specific T3 Alarm

RTRV-ALM-T3:EXMII-TL1:1:566;

EXMII-TL1^<yy-mm-dd>^<hh:mm:ss><cr><lf>
M^^<ctag>^COMPLD<cr><lf>
^^^”[<aid>]:<ntfcncde>,<condtype>,<srveff>,[<ocrdat>],[<ocrtm>],[<locn>],
[<dirn>],[:[<conddescr>],[<aiddet>]]”<cr><lf>*
;
A description of each parameter is listed below.
TA-200 OP
8/29/03 8-17
aid Access Identifier
ntfcncde Severity or class of alarm, event, or condition
condtype Type of alarm or condition
srveff Service Effect
ocrdat Date when the event was detected (format mm-dd)
ocrtm Time when event was detected (format hh-mm-ss)
locn Location of alarm or condition
dirn Direction of alarm or condition
conddescr Detailed description of alarm (maximum of 64 characters enclosed in “\”)
aiddet Additional information for module (active or standby)
Access Identifier
The <aid> response format is “<module type>-<signal level>,<slot number>-<tributary>”.
Notification Code
The notification code specifies the severity or class of alarm, event, or condition. This field is represented
by <ntfncde>.
MJ Major Alarm
MN Minor Alarm
CL Condition Cleared
Condition Type
This parameter describes the type of alarm, event, or condition. This field is represented by <condtype>.
AIS Alarm Indication Signal

CLK Clock Alarm
EQPT Equipment Failure
IMPROPRMVL Improper removal, card missing
INT Internal equipment failure, board alarm
LOF Loss of frame
LOS Loss of signal
LOP Loss of pointer
OOF Out of Frame
RAI Remote Alarm Indication
RDI Remote Defect Indication
SLM Signal Label Mismatch
SYNC Loss of External Clock
XBIT Far-end Alarm Indication
Effect of Alarm or Condition on Service

This field is represented by <srveff>.
NSA Non-service affecting condition
SA Service affecting condition
Location of Alarm or Condition

This field is represented by <locn>.
NEND Near End: At the local equipment
FEND Far End: At a distant equipment connected to the local
equipment.
Direction of Alarm or Condition
TA-200 OP
8/29/03 8-18
This field is represented by <dirn>.
TRMT Transmit from TransAccess 200
RCV Receive into TransAccess 200
NA Not applicable
8.4.7.2.5 Response Example: None of the Requested Alarms Active
EXMII-TL1 2002-08-04 11:51:55
M 883 COMPLD
;
8.4.7.2.6 Response Examples: Active Alarms Present (ALL)
EXMII-TL1 2002-07-24 14:43:21
M 566 COMPLD
“M13-T3,3:MJ,LOS,SA,02-02,01-41-19,NEND,RCV:\”Loss of Signal\”,ACTIVE”
“PM13+-T3,3:MJ,OOF,SA,02-02,01-41-19,NEND,RCV:\”Out of Frame\”,ACTIVE”
“PM13+-T3,11:MN,RAI,NSA,02-02,06-22-58,NEND,RCV:\”Remote Alarm\”,ACTIVE”
“PM13+-T3,12:MN,RAI,NSA,02-02,06-22-58,NEND,RCV:\”Remote Alarm\”,STANDBY”
“PM13+-T1,11-28:MJ,LOS,SA,02-04,16-30-00,NEND,RCV:\”Loss of Signal\”,ACTIVE”
“MPU-EQPT,B:MN,IMPROPRMVL,NSA,01-12,13-17-56:\”Improper Removal\”,STANDBY”
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IIAC
;
8.4.7.2.8 Error Response: Invalid Modifier

EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
ICNV
;
8.4.7.2.9 Error Response: Unconfigured Slot
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IDNV
;
8.4.7.3 Retrieve Performance Monitoring Data
This command instructs the TransAccess 200 to transmit the performance data associated with one or
more service modules.
RTRV-PM-{MOD2}:[<tid>]:[<aid>]:<ctag>]::[<montype>],,,,[<tmper>],,[<montm>];
The Access Identifier <aid> is formatted as “<slot#>-<tributary>”.
MOD2 can be T1, E1, VT1, VT2, T3, STS1, OC3, or STM1.
TA-200 OP
8/29/03 8-19
TMPER is the accumulated time period. The field syntax is <VAL-UN> (see below). The NULL value
defaults to 1 hour.
VALue UNit
1 DAY
1 to 24 HR
1 to 1440 MIN
MONTM is the time of day of the requested performance-monitoring period specified in TMPER. The
format for MONTM is <HOD-MOH>. If a <tmper> is for an hour, the errors will be for the errors
recorded starting at the time specified in <montm>. If TMPER is 1-DAY, then MONTM is ignored. A
null value of TMPER displays errors for the current 1-hour period.
This field is represented by <montype>.

CVL T1/E1Bipolor coding violation
ESL T3 Parity Errored Seconds
ESP T3 Path Errored Seconds
ESL-LFE T3 FEBE Errored Seconds
SESL-LFE T3 FEBE Severely Errored Seconds
ALS-P VT-Path AIS/LOP Errored Seconds
SESV VT-Path AIS/LOP Severely Errored Seconds
ESL OC-3/STM-1 or STS-1/AU3 Errored Second – Line
ESS OC-3/STM-1 Errored Second – Section
SESL Severely Errored Second – Line
SESP Severely Errored Second – Path
SESS Severely Errored Second – Section
<blank> Display alarms pertaining to the 2nd Modifier
For example, to retrieve all performance history for a particular slot (only one slot can be selected at a
time), then enter the following command.
RTRV-PM-ALL:<tid>:<slot#>:<ctag>::,,,,1-HR,,11-00;

EXMII-TL1 2002-08-30 10:30:22
M 86 COMPLD
<aid>:<montype>,<monval>,[<vldy>],,,[<tmper>],[mondat],[<montm>];
The Access Identifier <aid> format is “<slot#>-<tributary>,MOD2”. TMPER is the timeperiod recorded
in minutes.
MONVAL is the measured value of the monitored parameter. MONVAL will indicate the measured
value over the defined period.
VLDTY (validity) indicates whether the data was for the entire time period or whether just a part of the
time period. COMPLD means that the data was accumulated over the entire requested period. PRTL
means that it was only collected during part of the requested time period. PRTL should be reported if
data for all 96 15-minute intervals has not elapsed when 24-hour totals had been requested.
MONDAT is the start date for the displayed data. MONTM is the start time for the displayed data.
TA-200 OP
8/29/03 8-20
8.4.7.3.2 Response Example
EXMII-TL1 2002-09-03 15:55:45
M 233 COMPLD
“4-16:CVL,233,CMPL,NEND,2-09,3-45”
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IIAC
;
8.4.7.3.4 Error Response: Invalid Time Period
EXMII-TL1 2002-08-30 10:30:22
M 80 DENY
IDNV
;
8.4.8 Automatic Alarm Reporting
For every automatic alarm message generated, there is an automatic alarm to clear that reported alarm.
The TL1 message to clear an alarm is the same one used to indicate the alarm except for the severity field
(MJ or MN) is shown as CL. In the following alarm tables, <AID> will be in the following format.
Module Type – Interface (MOD2) Type – Slot-Tributary

8.4.8.1 Normal Response
EXMII-TL1^<yy-mm-dd>^<hh:mm:ss><cr><lf>
<almtype>^^<ctag>^REPT ALM <alarm type><cr><lf>
(^^^”<aid>:<ntfcncde>,<condtype>,<srveff>,<ocrdat>,<ocrtm>,[<locn>],
[<dirn>]:<conddescr>,<aiddet>”<cr><lf>*
;
Alarm Type is T1, E1, VT1, VT2, T2, G747, T3, STS1, AU3, OC3, STM1, TRK, EQPT, or INT. Refer
to section 6.4.7.2.4 for descriptions of the other fields.
An example of an automatic message:
EXMII-TL1 2002-07-22 13:45:02

<almtype> 40 REPT ALM EQPT
“PM13+-EQPT,5:MN,IMPROPRMVL,NSA,02-02,01-01-40,,:\”BoardAlarm\”,STANDBY”
;
The valid alarm types <almtype> are:

** - Major Alarm
*^ - Minor Alarm
A^ - Alarm cleared
8.4.8.2 T1 LOS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM T1
TA-200 OP
8/29/03 8-21
“<aid,>:<ntfncde>,LOS,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Loss of
Signal\”,{ACTIVE|STANDBY}”
;
8.4.8.3 T1 AIS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,AIS,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Alarm Indication
;
8.4.8.4 E1 LOS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM E1
;
8.4.8.5 E1 AIS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM E1
;
8.4.8.6 PM13(E) T2/G.747 LOF Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM {T2|G747}
“<aid,>:<ntfncde>,OOF,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Loss of
Frame\”,{ACTIVE|STANDBY}”
;
8.4.8.7 PM13(E) T2/G.747 X-bit (RAI) Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM {T2|G747)
“<aid,>:<ntfncde>,RAI,<srveff>,<ocrdat>,<ocrtm>,FEND,RCV:\”Remote Alarm
Indication\”,{ACTIVE|STANDBY}”
;
8.4.8.8 PM13(E) T3 LOS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.9 PM13(E) T3 LOF Input Alarm
EXMII-TL1 2002-01-01 09:01:01
TA-200 OP
8/29/03 8-22
“<aid,>:<ntfncde>,LOF,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Loss of
;
8.4.8.10 PM13(E) T3 AIS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,AIS,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Alarm Indication Signal
\”,{ACTIVE|STANDBY}”
;
8.4.8.11 PM13(E) T3 X-bit (RAI) Input Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.12 PM13(E) STS-1/AU3 LOS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM {STS1|AU3}
;
8.4.8.13 PM13(E) STS-1/AU3 LOF Input Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.14 PM13(E) STS-1/AU3 SLM Input Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,SLM,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Signal Label
Mismatch\”,{ACTIVE|STANDBY}”
;
8.4.8.15 PM13(E) STS-1/AU3 LOP Input Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,LOP,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Loss of
Pointer\”,{ACTIVE|STANDBY}”
;
8.4.8.16 PM13(E) STS-1/AU3 AIS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
TA-200 OP
8/29/03 8-23
;
8.4.8.17 PM13(E) VT/VC LOP Input Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM {VT1|VT2|VC12}
;
8.4.8.18 PM13(E) VT/VC AIS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,AIS,<srveff>, <ocrdat>,<ocrtm>,NEND,RCV:\”Alarm Indication
;
8.4.8.19 PM13(E) VT/VC RDI Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,RDI,<srveff>,<ocrdat>,<ocrtm>,FEND,RCV:\”Remote Alarm
;
8.4.8.20 PM13(E) Board Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM INT
“<aid,>:<ntfncde>,INT,<srveff>, <ocrdat>,<ocrtm>:\”Internal Hardware
Fault\”,{ACTIVE|STANDBY}”
;
8.4.8.21 PM13(E) No Output Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.22 OMX3 Board Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.23 OMX3 Clock Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM CLK
“<aid,>:<ntfncde>,INT,<srveff>,<ocrdat>,<ocrtm>:\”Clock Alarm\”,{ACTIVE|STANDBY}”
TA-200 OP
8/29/03 8-24
;
8.4.8.24 OMX3 OC-3/STM-1 LOS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM {OC3|STM1}
;
8.4.8.25 OMX3 OC-3/STM-1 LOF Input Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.26 OMX3 OC-3/STM-1 AIS Input Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.27 OMX3 OC-3/STM-1 SLM Input Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,SLM,<srveff>,<ocrdat>,<ocrtm>,NEND,RCV:\”Signal Label
Mismatch\”,{ACTIVE|STANDBY}”
;
8.4.8.28 OMX3 OC-3/STM-1 RDI Input Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,RDI,<srveff>,<ocrdat>,<ocrtm>,FEND,RCV:\”Remote Defect
Indicator\”,{ACTIVE|STANDBY}”
;
8.4.8.29 OMX3 STS-1/AU3 LOP Path Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM TRK
;
8.4.8.30 OMX3 STS-1/AU3 AIS Path Alarm
EXMII-TL1 2002-01-01 09:01:01
;
TA-200 OP
8/29/03 8-25
8.4.8.31 OMX3 STS-1/AU3 RDI Path Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,RDI,<srveff>,<ocrdat>,<ocrtm>,FEND,RCV:\”Remote Defect Indication\”,
{ACTIVE|STANDBY}”
;
8.4.8.32 OMX3 T3/STS-1/AU3 LOS Drop Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM {T3|STS1|AU3}
;
8.4.8.33 OMX3 T3/STS-1/AU3 LOF Drop Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.34 OMX3 T3/STS-1/AU3 AIS Drop Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.35 OMX3 T3/STS-1/AU3 RAI Drop Alarm
EXMII-TL1 2002-01-01 09:01:01
;
8.4.8.36 OMX3 T3/STS-1/AU3 No Output Drop Alarm
EXMII-TL1 2002-01-01 09:01:01
“<aid,>:<ntfncde>,INT,<srveff>,<ocrdat>,<ocrtm>:\”Internal Hardware
Failure\”,{ACTIVE|STANDBY}”
;
8.4.8.37 MPU Board Alarm
EXMII-TL1 2002-01-01 09:01:01
“MPU–INT,{A|B}:<ntfncde>,INT,<srveff>,<ocrdat>,<ocrtm>:\”Internal Hardware
Failure\”,{ACTIVE|STANDBY}”
;
8.4.8.38 Service Module Missing Alarm
TA-200 OP
8/29/03 8-26
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM EQPT
“<AID>:<ntfncde>,IMPROPRMVL,<srveff>,<ocrdat>,<ocrtm>:\”Improper
Removal\”,{ACTIVE|STANDBY}”
;
8.4.8.39 MPU Card Missing Alarm
EXMII-TL1 2002-01-01 09:01:01
<almtype>^<ctag> REPT ALM EQPT
“MPU–EQPT,{A|B}:<ntfncde>,IMPROPRMVL,<srveff>,<ocrdat>,<ocrtm>:\”Improper
Removal\”,{ACTIVE|STANDBY}”
;
TA-200 OP
8/29/03 8-27
9 WEB-BASED INTERFACE (WBI)
WBI is an TransAccess 200 feature that provides a way to remotely manage the TransAccess 200 from
anywhere on the network.
9.1 Requirements
WBI requires Internet Explorer 4.5 or higher web browser with Java support enabled. Older versions of
this browser may not display the WBI information properly.
The user must set the IP address, Net Mask, and gateway address through the ‘IP/SNMP Config’ screen
on the User Interface (UI), to enable the WBI. The user must refer to section 5.3 for configuring the
TransAccess 200 for Telnet, SNMP or WBI operation.
9.2 WBI Security

The TransAccess 200 system information is protected with a security mechanism. Entering the IP address
of the TransAccess 200 system into the browser pops up a username and password window as shown in
Figure 9.1 below. The username entry may be skipped, but the password entry must match one of the
passwords entered into the TransAccess 200 as described in section 4.5.1.3 to access the system.
Figure 9-1: TransAccess 200 Login Prompt
CAUTION: It is strongly advised that the user close the browser window after the completion of the
session to avoid any unauthorized access to the EXchange Mux system.
TA-200 OP
8/29/03 9-1
9.3 WBI Operation
The following section is a description of the screens displayed on the client Web browser. The
functionality of the WBI is similar in operation to the UI, hence it is advised that the user be familiar with
the UI as described in chapter 4. Additional information regarding the details of each screen is also
available in chapter 4.
Following successful login, the TransAccess 200 Diagnostics menu shown in Figure 9-5 will appear.
Click on the menu items in the left-hand column to access the features.
9.3.1 System Alarm Screen
Figure 9-2: System Alarm Summary Screen
The System Alarm screen summarizes the alarm status for the entire shelf. An ‘X’ will be displayed in
the alarm fields whenever an alarm is detected. This screen is automatically updated every 5 seconds.
For details on what alarm is detected, proceed to the alarm summary screen for that particular module.
Alarm status consists of the following information:
1. On-Line/Off-line/Protection Status
2. Minor Alarm/Major Alarm Status
3. Far-end Alarm Status
4. Maintenance Status
5. Nodal Alarm Summary
TA-200 OP
8/29/03 9-2
9.3.2 Summary Information
The System Info screen displays the software revision levels currently stored in the MPU modules. The
software revision levels displayed on this screen reflect what is stored in the MPU but not necessarily
what has been downloaded to the service modules. Check the Module Information screen to view
software levels that the service modules are running with. If a difference is noticed, use the ‘Discover’
command to update the system.
Figure 9-3: System Information Screen
NOTE: If the FPGA software is different between the service module and MPU, a ‘Discover’
command will cause traffic to go down for approximately 5 seconds while the service module is
updated.
9.3.3 Module Information Summary

The Module Info screen allows the user to view the software, firmware, and assembly revision levels of
each of the MPU and Service Modules in the shelf. Software Revision refers to the MPU microprocessor
embedded software. Firmware Revision refers to the programmable gate array firmware. When selecting
this feature, the following table is displayed.
TA-200 OP
8/29/03 9-3
Figure 9-4: Module Information Summary
9.3.4 Diagnostics Menu

The selection for Service Module Diagnostics commands is under the initial System menu. The
diagnostic commands available are:
1. Protection Switch
2. Reset
3. Restore
4. Discover
Figure 9-5 shows the menu options for the Service Module Diagnostics selections.

Prior to activating a manual protection switch, the screen will show the current module status for each
slot. A description of the indicators is below.
A – Active, online
O – Offline
M – Missing (configured module not present)
F – Force online
U – Unconfigured slot (but service module is plugged in)
To select a Service Module to protect, move the cursor beneath one of the off-line card slots and ‘click’
on the button on the bottom row. Select the appropriate switch command to enable the protection switch.
TA-200 OP
8/29/03 9-4
See below for the available selections. Any combination of the seven protection modules can be on-line
or off-line at the same time.
Figure 9-5: TransAccess 200 General Diagnostic Menu
There are two types of protection switch commands available.
Safe Switch – This will cause the selected module to go on-line. A 50ms ‘hit’ will occur to the T1 traffic
during the switch. Redundancy remains available after a safe on-line protection switch. If an alarm is
active on the selected module, a protection switch may not occur.
Force On-line Switch – This will cause the selected module to go on-line. A 50ms ‘hit’ will occur to the
traffic during the switch. Redundancy is disabled while a force protection switch is active. Therefore,
any failures to the on-line module will not be protected. The status LED will be yellow to indicate that a
maintenance condition is active on the selected module and redundancy is no longer available. However,
if an alarm is detected, the LED will blink red.
Clear Force Online – This will remove the forced condition and enable protection switching for the
service module pair.
9.3.4.2 Reset
This feature forces the MPU module to reprogram the selected module in the shelf. This includes
downloading the current firmware and re-configuring the module with the configuration stored in the
MPU module. Traffic on the selected module will be disrupted for approximately 5 seconds. ‘Click’ on
the radio button under the slot number and ‘click’ on RESET to invoke the reset. RESET ALL will
command the MPU to reprogram all the service modules.
TA-200 OP
8/29/03 9-5
9.3.4.3 Reset MPU
This feature will reset the on-line MPU and force an MPU protection switch. An MPU protection switch
will be hitless to any live traffic carried by the service modules.
9.3.4.4 Restore
This selection removes all active diagnostic functions (loopbacks, force protection switches, T1 Testing)
for the selected Service Module. Modules with active diagnostics will have a yellow status LED unless
that module is detecting an alarm. When detecting an alarm, the status LED will be red or flashing red.
9.3.4.5 Discover
This feature commands the MPU module to discover all the modules in the shelf. Those modules that had
been previously unconfigured will be downloaded with their default configuration. Any physically
missing modules will be deleted from the logical installed equipment list. This will not affect the
operation of any of the modules already configured in the shelf.
9.3.5 Backup Configuration File

The current MPU configuration data can be stored remotely and later used to restore a system during a
disaster recovery scenario. Three means of backup and restore are available: via Telnet (TFTP), via Web
Browser, or via the Craft Port (using transmit and send from a VT100 terminal).
To create and store a backup TransAccess 200 configuration file, click on Backup File from the System
Menu. The screen shown in Figure 9-6 will appear.
Figure 9-6: TransAccess 200 Configuration File Backup
TA-200 OP
8/29/03 9-6
9.3.6 Restore Configuration or FPGA File
To download the TransAccess 200 configuration or FPGA Software from a remote file, click on Restore
File from the system menu. The screen shown in Figure 9-7 will appear.
Figure 9-7: TransAccess 200 Configuration Restore
In the Select File Type, select the file to be restored. In the Select File field, enter the path and filename
where the configuration file is currently stored. Click on Restore File to transfer the new configuration
data to the MPU module. Once the configuration file is transferred and verified, the MPU will reboot and
program the service modules with the new configuration. If a FPGA file was downloaded, the MPU must
be reset for the new software file to activate.
9.3.7 Optical Mux Configuration Menu

Figure 9-6 displays the configuration menu of the OMX3 and OMXT3 service module and allows each
configuration item to be modified using the cursor keys.

To change a configuration setting of the default template or to the OMX3 modules, ‘click’ on the card slot
that you wish to change. The screen shown in Figure 9-9 will be displayed.
The configurable items and their options for the OMX3 module are listed below.
Line Type
This feature configures the optical interface for OC-3 or STM-1.
TA-200 OP
8/29/03 9-7
Figure 9-8: OMX3 Service Module Configuration
Figure 9-9: OMX3 Configuration Parameter Modification Screen
TA-200 OP
8/29/03 9-8
OP Mode
This configuration item defines the operation of the OMX3 module. The choices are either Terminal
mode (TERM) or Add/Drop (ADRP). In Terminal mode, all 3 T3/STS-1/AU3 tributaries are dropped
from the OC-3/STM-1 line. OMX3 protection switching is based on the SONET Automatic Protection
Switch (APS) algorithm.
In Add/Drop mode, each tributary can be selected to either pass through the node or dropped from the
OC-3/STM-1 ring. OMX3 protection switching is based on Unidirectional Path Switched Rings (UPSR).
Protection Switch
This feature provides the ability to enable or disable protection switching for a particular OMX3 module.
Hold-off
The MPU will detect an OMX3 alarm and switch to the redundant module within 50 ms. The hold-off
feature delays OMX3 protection switching after the MPU detects the alarm. Protection switching hold-
off can be programmed for NONE (switch immediately), 50ms, 100ms, 500ms, 1 second, 2 seconds, or 5
seconds.
Timing Mode
• LOOP – If configured for Terminal Mode (TRML), the OC-3/STM-1 clock can be set for
Loop Timing. That is, the Transmit Clock will be timed from the Receive Clock.
• INTERNAL – The Transmit OC-3/STM-1 clock will be timed to the OMX3 Module’s local
oscillator which has +/- 20 ppm accuracy.
• EXTERNAL – The Transmit OC-3/STM-1 clock will be timed from the 8KHz external clock
connected at the TransAccess 200 backplane.
• THRU – If configured for Add/Drop, the Transmit OC-3/STM-1 clock can be timed from the
recovered clock of the adjacent OMX3 module.
• Dn – Timing of the Transmit OC-3/STM-1 clock can be derived from any of the Incoming
Drop Ports (1-3) only if they are configured for STS-1/AU3.
• SRC – Source Timing can be configured for one OMX3 card in the TransAccess 200 shelf. It
is used to distribute timing to the other OMX3 modules. It does this by deriving an 8KHz
clock from the incoming OC-3/STM-1 recovered clock and placing the 8KHz clock on the
external clock bus on the backplane. Select External Clock for the other OMX3 modules
that need to be timed to this clock. Only one OMX3 module can be configured for SRC
timing at a time.
NOTE: IF SRC TIMING IS SELECTED ON ANY OMX3 SERVICE MODULE, BE SURE TO

DISCONNECT THE EXTERNAL CLOCK FROM THE BACKPLANE AS BOTH SRC
AND EXTERNAL CLOCKS USE THE SAME CLOCK BUS. FAILURE TO DO SO WILL
CAUSE THE SRC AND EXTERNAL CLOCKS TO COLLIDE WITH EACH OTHER.
Drop Signal
Each drop port can be configured for either T3, STS-1 (STS), AU3, Bypass (BP) or Disable (DIS). AU3
cannot be selected if the OMX3 is configured for OC-3. STS-1 cannot be selected if the OMX3 is
configured for STM-1. Bypass (BP) can only be selected when configured for ADRP operation. If the
OMXT3 module is installed, only T3, Bypass (BP), or Disable (DIS) can be selected.
TA-200 OP
8/29/03 9-9
LBO
Each drop port can be configured independently.
• I (LBO In) – Outgoing T3/STS-1/AU3 Line Build Out selection for cable lengths less than or
equal to 225 feet.
• O (LBO Out) – Outgoing T3/STS-1/AU3 Line Build Out selection for cable lengths greater
than to 225 feet.
9.3.8 Optical Mux Alarms

The Alarm Summary table summarizes the Input and Board Alarms for each of the OMX3 service
Module
State
Figure 9-10: OMX3 Service Module Alarm Summary
TA-200 OP
8/29/03 9-10
Board Alarm:
Board Alarm indicates that there has been a hardware failure detected (clock failure or loss of any
of the drop port transmit signals). A Redundant Module may protect it.
Clock Alarm:
CLK ALM – Clock Alarm indicates that the primary configured clock source has failed. If
configured for External Timing, Through Timing, or Source Timing and the timing source fails,
the OMX3 module will switch to its Internal Oscillator.
Optical Input Alarms

Optical input alarms are broken into three categories, board alarms, OC-3 alarms, and common alarms for
each T3/STS-1/AU3 drop port.
LOS – Loss of Signal indicates that the incoming OC-3/STM-1 signal is missing. When this
event is declared, AIS will be transmitted out all 3 drop ports.
LOF – Loss-of-Frame indicates that the incoming OC-3/STM-1 framing is not detected. When
this event is declared, T3, STS-1, or AU3 AIS will be transmitted out all 3 drop ports.
AIS – The Alarm Indication Signal (AIS) indicates that an OC-3/STM-1 failure (AIS – bits 5 and
6 of the H1 byte) has occurred upstream from the TransAccess 200. When this event is declared,
T3, STS-1, or AU3 AIS will be transmitted out all 3 drop ports.
RDI – The Remote Defect Indicator (RDI) alarm indicates that the far-end OC-3/STM-1
equipment has detected an OC-3/STM-1 Line alarm.
Path Alarms:
This field is a summary of the OC-3/STM-1 path alarms. If an ‘X’ is displayed in this field, one of the
following alarms has been detected on at least one of the STS-1/AU3 paths. ‘Click’ on OMX3 Path
Alarms to see the details of which alarm has been detected. Figure 9-11 shows the OMX3 Path Alarm
screen.
LOP – The Loss of Pointer (LOP) alarm indicates that one of the incoming STS-1 paths cannot
detect the pointer.
AIS – The Alarm Indication Signal (AIS) indicates that an STS-1 failure has occurred upstream
from the TransAccess 200. When this event is declared, T3, STS-1, or AU3 AIS will be
transmitted out the drop port.
SLM – The Signal Label Mismatch (SLM) indicates that the STS-1 tributary has an invalid
number detected.
RDI – The Remote Defect Indicator (RDI) alarm indicates that the far-end equipment has
detected an STS-1 Path alarm.
TA-200 OP
8/29/03 9-11
Figure 9-11: OMX3 Path Alarm Summary
Figure 9-12: OMX3 Drop Alarm Summary
TA-200 OP
8/29/03 9-12
Drop Alarm:
When an ‘X’ appears in these locations, the incoming drop port has detected an alarm. ‘Click on the
OMX3 Drop Alarms to see the details of which alarm has been detected. Figure 9-12 will show the drop
alarm details.
LOS – When configured for T3, STS-1, or AU3, this alarm indicates a loss of the signal.
LOF – When configured for T3, STS-1, or AU3, this alarm indicates a loss of frame.
LOP – The Loss of Pointer (LOP) alarm indicates that one of the incoming STS-1/AU3 paths
cannot detect the pointer.
AIS - When configured for T3, STS-1, or AU3, this alarm indicates that the Alarm Indication
Signal is being received. This indicates that equipment upstream from the TransAccess 200 has
failed.
SLM – The Signal Label Mismatch (SLM) indicates that the STS-1/AU3 tributary has an invalid
number detected.
RDI – The Remote Defect Indicator (RDI) alarm indicates that the far-end equipment has
detected an STS-1/AU3 Path alarm.
9.3.9 OMX3 Performance Summary
A description of each field found in Figure 9-13 is shown below:
Figure 6-13: OMX3 Performance Summary
TA-200 OP
8/29/03 9-13
Slot Type
Slot State:

least 16 OC-3 B1 errors, or detection of loss-of-signal, or detection of out-of-frame.
least 32 OC-3/STM-1 B2 errors, or detection of loss-of-signal, or detection of out-of-frame.

second that contains 44 T3 parity bit errors, 32 STS-1/AU3 code violation errors, or detection of
9.3.10 OMX3 Performance History

Selecting Performance History brings up the menu shown in Figure 9-14.

TA-200 OP
8/29/03 9-14

Figure 9-14: OMX3 Performance History
9.3.11 OMX3 Loopbacks

Selecting ‘Loopback’ brings up the menu shown in Figure 9-15. Select an OMX3 slot by ‘clicking’ on
the top blue menu.
TA-200 OP
8/29/03 9-15
Four loopbacks are available:
OC-3/STM-1 Line Loopback – Loops the entire receive OC-3/STM-1 signal back out the transmit port.
OC-3/STM-1 Drop Loopback – Loops the entire transmit OC-3/STM-1 signal back into the receive port.
T3/STS-1/AU3 Line Side – Loops the selected STS-1/AU3 or T3 transmit tributary back into the receive
tributary.
T3/STS-1/AU3 Drop Side – Loops the selected STS-1/AU3 or T3 receive tributary back out the transmit
port.
PRECAUTION: DO NOT ENABLE THE OC-3/STM-1 DROP LOOPBACK AND THE STS-1/T3
LINE SIDE LOOPBACKS SIMULTANEOUSLY. IF SO, ALARMS WILL BE
GENERATED SINCE THERE IS NO ORIGINATING SOURCE OF TIMING.
To select a loopback, ‘click’ on the button next to the loopback you’d like to select. ‘Click’ on SAVE
LOOPBACKS and the loopback command will be enabled. The status LED of the OMX3 module will
turn yellow while the loopback is active. If an alarm is detected by the OMX3 module, the status LED
will blink red.
Figure 9-15: OMX3 Service Module Loopback Control
9.3.12 PM13/PM13E/M13-T3 Line Configuration

Figure 9-16 shows the current configuration settings for the PM13, PM13E, and M13-T3 modules. To
make changes to any of the settings, first ‘click’ on the module in the left-hand column.
TA-200 OP
8/29/03 9-16
To change a configuration setting of the default template or of a service module, ‘click’ on the slot
number to view the list of configuration options. Figure 9-18 shows the configuration change menu for
the PM13E module. Figure 9-17 shows the configuration change menu for the PM13 and M13-T3
modules. Once the changes are made, ‘click’ on SAVE. This will cause the MPU to download the
changes.
The Drop Configuration command takes you to the configuration menu for the drop ports. This menu is
Figure 9-16: PM13/PM13E Service Module Line Side Configuration
After selecting a PM13 or M13-T3 slot number, the screen shown in Figure 9-17 will appear.
The configurable items and their options for the PM13 or M13-T3 Line Side are listed below.
Line Type
This feature provides the ability to program the PM13 for either T3 or STS-1 operation.
Protection Switch
This feature provides the ability to enable or disable protection switching for a particular PM13 module.
Hold-off
The MPU will detect a PM13 alarm within 50 ms. This feature delays PM13 protection switching after
the MPU detects the alarm. Protection switching hold-off can be programmed for NONE (switch
TA-200 OP
8/29/03 9-17
LBO
Figure 9-17: PM13/M13-T3 Configuration Change Menu
Timing Mode
• LOOP – The T3 or STS-1 clock will be set for Loop Timing. That is, the Transmit Clock
will be timed from the Receive Clock.
• INTERNAL – The Transmit T3 or STS-1 clock will be timed to the PM13 Module’s local
oscillator.
T1/VT15 Mapping – (Selectable only when configured for STS-1 operation)

• TRANSPAR – T1 circuits are mapped into VT1.5 tributaries in accordance Telcordia

• INTERLVD – T1 circuits are mapped sequentially into VT1.5 tributaries.
9.3.13 PM13E Line Configuration Change Menu

If a PM13E module was selected from the screen shown in Figure 9-18, the following menu will be
displayed.
TA-200 OP
8/29/03 9-18
The configurable items and their options for the PM13E Line Side are listed below.
Figure 9-18: PM13E Line Configuration Change Menu
Line Type
This feature provides the ability to program the PM13E for either T3, STS-1, or AU3 operation.
Protection Switch
This feature provides the ability to enable or disable protection switching for a particular PM13E module.
Hold-off
The MPU will detect a PM13E alarm within 50 ms. This feature delays PM13E protection switching
after the MPU detects the alarm. Protection switching hold-off can be programmed for NONE (switch
LBO
Timing Mode
• LOOP – The T3, STS-1, or AU3 clock will be set for Loop Timing. That is, the Transmit
Clock will be timed from the Receive Clock.
• INTERNAL – The Transmit T3 or STS-1 clock will be timed to the PM13E Module’s local
oscillator.
TA-200 OP
8/29/03 9-19
VT/VC Mapping – (Selectable only when configured for STS-1 or AU3 operation)
• TRANSPARENT – E1 circuits are mapped into VT2 tributaries in accordance Telcordia

• INTERLEAVED – E1 circuits are mapped sequentially into VT2 tributaries.
9.3.14 PM13/PM13E Drop Configuration Change Menu

Figure 6-19 shows the current configuration settings for the PM13, PM13E, and M13-T3 modules. To
make changes to any of the settings, first ‘click’ on the module in the left-hand column. When a PM13 or
M13-T3 module is selected, the screen shown in Figure 9-20 will appear.
All 28 T1 tributaries can be individually programmed for different cable line lengths (E1’s do not require
an LBO setting). The six selectable Line Build Out (LBO) settings are:
0 – Port disabled (alarms disabled only)

1 – 0 to 133’ of cable
2 – 133’ to 266’ of cable
3 – 266’ to 399’ of cable
4 – 399’ to 533’ of cable
5 – 533’ to 655’ of cable
Figure 9-19: PM13/PM13E/M13-T3 Drop Configuration
TA-200 OP
8/29/03 9-20
B8ZS and AMI Line Coding is selectable for on a per-channel basis for PM13+ and M13-T3 modules.
PM13 modules can be programmed by groups of 7 T1s. HDB3, AMI, or Disabled selections can be
made for each of the 21 E1 drop ports. If ‘Disabled’ is selected, no alarms will be generated for the E1
tributary.
Figure 9-20: PM13+/M13-T3 Drop Configuration Change Menu
If a PM13E module is selected from the Drop Configuration menu, the screen in Figure 9-21 will appear.
Figure 6-21: PM13E Drop Configuration Change Menu
TA-200 OP
8/29/03 9-21
9.3.15 Inband Loopback Configuration
The PM13 modules have the ability to generate and react to T1 In-band loop-up/loop-down commands
via the 28 T1 drop ports. Each T1 tributary can be enabled, by groups of 7 T1s, to activate loopbacks
towards the drop port. Activation and deactivation patterns can also be programmed for groups of 7 T1s.
If a valid loop-up signal is received for 5 seconds, the incoming T1 signal will be looped back out the
outgoing T1 line. When an in-band loopback command is activated, the activation pattern is sent down
the T1 line for 5.1 seconds. During this period, live T1 traffic on the tributary is disrupted.
Figure 9-22: T1 In-band Loopback Configuration Screen
Figure 9-22 shows the current configuration. To change any of the configuration settings, click on the
slot number. The screen shown in Figure 9-23 will appear.
TA-200 OP
8/29/03 9-22
Figure 9-23: T1 In-band Loopback Slot Configuration Screen
9.3.16 PM13/PM13E Alarm Summary

The PM13/PM13E Alarm Summary table summarizes the Input and Board Alarms for each of the PM13
service modules. An example of the Alarm Summary is shown in Figure 9-24 below.
Figure 9-24: PM13/PM13E Alarm Summary
TA-200 OP
8/29/03 9-23
Type
Indicates the type of module plugged in.
State
Board Alarm:
BRD ALM – Board Alarm indicates that there has been a hardware failure detected. The PM13
Module will transmit a T3 AIS (framed 1010 pattern) or an STS-1 Yellow Alarm if possible. A
Protection Module may protect it.
T1/E1 Drop Alarm:

T1/E1 LOS – Indicates that one of the incoming T1 or E1 drop signals has been lost. ‘Click’ on
the service module slot to display the alarm detail screen. It will show the T1 or E1 tributary
alarms.
T1/E1 AIS – Indicates that one of the incoming T1 or E1 drop signals has detected a valid AIS
signal. An AIS signal indicates that a failure has occurred upstream from the TransAccess 200
system. ‘Click’ on the service module slot to display the alarm detail screen. It will show the T1
or E1 tributary alarms.
Line Side Alarms

Line side alarms are broken into three categories, common alarms for T3, STS-1, and AU3 operation,
alarms for T3 operation only, and alarms for STS-1/AU3 operation only.
Common Alarms:
LOS – Loss of Signal indicates that the incoming T3, STS-1, or AU3 signal is missing. When
this event is declared, AIS will be transmitted out all 28 T1 ports or 21 E1 ports.
OOF – Out-of-Frame indicates that the incoming T3, STS-1, or AU3 framing is not detected.
When this event is declared, AIS will be transmitted out all 28 T1 ports or 21 E1 ports.
AIS – The Alarm Indication Signal (AIS) indicates that a T3 or STS-1 failure (AIS – bits 5 and 6
of the H1 byte) has occurred upstream from the TransAccess 200. When this event is detected,
AIS will be transmitted out all 28 T1 ports or 21 E1 ports.
NO OUT – This alarm indicates that the outgoing T3, STS-1, or AU3 signal has failed.
TA-200 OP
8/29/03 9-24
T2/747 OOF – T2 or G.747 Out-of-Frame indicates that at least one of the T2 or G.747 tributaries
within the incoming T3 signal has lost its frame pattern. When this event is detected, the signals
associated with the failure will have AIS inserted into the 4 T1 tributaries or 3 E1 tributaries.
T3X BIT – The received T3 X-bit is used to identify a T3 far-end alarm. When the alarm is
detected, the T3 transmit path to the far-end equipment has failed.
T2X/747FE BIT – The receive T2 X-bit or G.747 Far-end bit is used to identify a T2 or G.747
far-end alarm. When the alarm is detected, at least one of the seven transmit tributaries has failed
towards the far-end equipment.
STS-1/AU3 Operation Alarms:
LOP – Loss of Pointer indicates that the PM13 module is unable to locate the start of the
Synchronous Payload Envelope (SPE) within the STS-1 signal. When this event is declared, T1
AIS will be inserted into each of the outgoing T1 tributaries within the outgoing T3 signal.
VT ALM – This is a VT1.5 alarm summary indicator. ‘Click’ on the service module slot to
display the alarm detail screen. It will show the VT1.5 or VT2 tributary alarms.
9.3.17 PM13/PM13E Alarm Details

The PM13 Alarm Details table summarizes the VT1.5 and T1 alarms for each of the PM13 service
modules. Figure 9-25 shows the tributary alarm screen. Similar alarm results are also displayed for the
PM13E module.
NOTE: If STS-1 LOS, LOF, LOP, or AIS is detected, VT1.5 alarms will not be reported.
VT1.5 Alarms:
The following VT1.5 alarms are detected from the incoming STS-1 signal. Similar VT2 alarms are
displayed for PM13E modules.
AIS – Alarm Indication Signal indicates that a VT1.5 signal failure has occurred upstream. The alarm is
SONET signal.
far-end equipment has detected an error on its incoming VT1.5 tributary.
Errored Seconds (ES) are based on a BIP-3 error in a one second interval. Severely Errored Seconds
(SES) indicate that 5 or more BIP-3 errors occurred in a one second interval.
TA-200 OP
8/29/03 9-25
Circuit Tags are displayed for each tributary. To enter the Circuit Tag information, select the Circuit Tag
screen under the PM13 Configuration Menu using SNMP or UID via Telnet.
T1/E1 Alarms:
The following T1 or E1 alarms are detected at the drop input ports.
LOS – Loss-of-signal for each of the 28 T1 tributaries or 21 E1 tributaries.
AIS – Alarm Indication Signal indicates that a T1 or E1 signal failure has occurred upstream. The alarm
is based on detecting 175 consecutive 1’s on the incoming signal.
NOTE: BPV error counts will reset to 0 when LOS is detected on a T1 or E1 tributary.
Figure 9-25: PM13 Tributary Alarm Details
9.3.18 PM13/PM13E Performance Summary

The Performance Summary table in Figure 9-26 displays the framing format and current bit error rate for
each of the PM13 and PM13E modules.
Slot Type
Indicates the type of module plugged in.
TA-200 OP
8/29/03 9-26
Slot State
A description of each bit error field is shown below:
Figure 9-26: PM13/PM13E Performance Summary
T3/STS-1/AU3 Errored Second Reporting
The maximum count of all the errored counters is 65,535 seconds. If the count reaches the maximum it
will be held until it is manually cleared. The following describes each alarm field. If the PM13E module
is programmed for T3, the STS-1/AU3 fields will be left blank and if configured for STS-1/AU3, the T3
fields will be left blank.
path bit errors, 13 STS-1/AU3 B2 errors, detection of loss-of-signal, or detection of out-of-frame.
TA-200 OP
8/29/03 9-27
the PM13E module is configure for STS-1/AU3, this field will be left blank.
T3 PARITY ES – The parity errored seconds will increment every time a T3 P-bit is detected in error for
a one second interval.
T3 PATH ES – The T3 path count is only available for C-bit parity T3 framing. The CP-bits in the T3
T3 FAR-END ES – The T3 far-end block error (FEBE) count is only available for C-bit parity T3
framing. The far-end block error count will increment every time a FEBE-bit is detected in error for a
one second period. Far-End Block Errors indicate that the far-end equipment is detecting bit errors on its
incoming T3 signal.
STS-1/AU3 B1 ES – The errored second count will increment every time a STS-1/AU3 B1 byte is
detected in error for a one second interval. The B1 byte is part of the STS-1/AU3 section overhead.
STS-1/AU3 B2 ES – The errored second count will increment every time a STS-1/AU3 B2 byte is
detected in error for a one second interval. The B2 byte is part of the STS-1/AU3 line overhead.
9.3.19 PM13/PM13E Performance History

T3/STS-1/AU3 Line, VT/VC tributaries, or T1 drop interfaces.
PM13E T3/STS-1/AU3 Line Performance History
Selecting the PM13E Line Performance History menu brings up the screen in Figure 9-27.
TA-200 OP
8/29/03 9-28
Figure 9-27: PM13/PM13E Line Performance History

PM13E VT/VC Performance History
Selecting the PM13E VT/VC Performance History menu brings up the screen in Figure 9-28. The screen
displays the VT1.5 alarms for each tributary of the selected PM13E slot. Errored Seconds (ES) are based
PM13E E1 Drop Performance History
Selecting the PM13E E1 Drop Performance History menu brings up the screen in Figure 9-29.
TA-200 OP
8/29/03 9-29
Figure 9-28: PM13/PM13E VT/VC Performance History
Figure 9-29: PM13E E1 Drop Performance History
TA-200 OP
8/29/03 9-30
9.3.20 PM13/PM13E Loopbacks
Selecting ‘loopback’ brings up the menu shown in Figure 9-30. The slot shown is for a PM13 module.
The PM13E module will show 21 tributaries to choose and will not have the Local/Far-end Loop feature.
To enable or disable a loopback, ‘click’ on the box under the numbered tributary. Multiple loopback
tributaries can be selected simultaneously. When done selecting, ‘click’ on SAVE to download the
change. When the loopbacks are enabled, the status LED of the PM13 will turn yellow unless an alarm
condition is detected.
To select a new slot (1-14) , click on a PM13 or PM13E module along the blue bar at the top of the
screen. Only numbers with underscores are selectable.
NOTE: T1 or E1 loopbacks towards a T3 or STS-1/AU3 tributary will not be active if a T1 or E1 Test

signal is generated on the same tributary.
Figure 9-30: PM13/PM13E Loopbacks
9.3.21 T1/E1 Test Generator and Receiver

This feature provides the capability to test any T1 or E1 signal dropping from either the T3/STS-1/AU3
signal or T1/E1 signal. If the PM13 or PM13E is programmed for STS-1/AU3 operation, a selection of 4
test signals can be used to intrusively inject into any T1 or E1 towards the STS-1/AU3 port or the T1/ E1
drop ports. If the PM13 or PM13E is programmed for T3 operation, only a QRSS pattern is available.
Figure 9-31 shows the E1 Test Configuration screen. Figure 9-32 shows the PM13 T1 Test
Configuration Screen.
TA-200 OP
8/29/03 9-31
To select a PM13 or PM13E module, ‘click’ on the module name appearing in the blue bar across the top
of the screen.
When configured for STS-1/AU3 the Test Pattern can be inverted or non-inverted. Move the cursor over
to PATTERN POLARITY to select between a Normal (non-inverted) or Inverted test pattern.
To select the Test Generator Pattern, move the cursor to the PATTERN to select one of the 4 test pattern
options (STS-1/AU3 mode only): QRSS, 2E15-1, 2E20-1, or 2E23-1. Select a Framed or Unframed
pattern. Also select the direction to inject the signal, either towards the Line or towards the Drop.
To inject a pattern into a tributary, ‘click’ on the radio button under the numbered tributary. More than
one selection can be made at the same time. Once all the selections are made, ‘click’ on SAVE to
download and activate the loopbacks.
All tributary selections must be removed before the direction of the E1 Generator or E1 Receiver can be
toggled. Select Clear Selections to remove the selections of this module. ‘Click’ on Save to download
the changes.
Figure 9-31: PM13E E1 Test Configuration Screen
One tributary can be monitored at a time. Before selecting the tributary to monitor, first select a test
pattern, framing, and receive direction. To select the tributary to monitor, ‘click’ on the radio button
under the numbered tributary. The RECEIVED ERRORS will display the number of bit errors received
(up to 65,535 errors). To clear the errors, ‘click’ on Clear Error.
‘Clicking’ on Loopback displays the PM13 or PM13E Loopback screen for the same slot.
NOTE: WHEN THE T1 or E1 TEST GENERATOR OR RECEIVER IS ENABLED ON THE PM13 or

PM13E MODULE, THE STATUS LED WILL TURN YELLOW.
TA-200 OP
8/29/03 9-32
NOTE: T1 or E1 LOOPBACKS TOWARD A T3 OR STS-1/AU3 TRIBUTARY WILL NOT BE
ACTIVE IF A T1 or E1 TEST SIGNAL IS GENERATED ON THE SAME TRIBUTARY.
Inject Error generates 1 bit error in the generated test pattern.
Figure 9-32: PM13 Test Configuration Screen

9.3.22 PM13/PM13E Frame Monitor
The PM13 and PM13E modules have the ability to non-intrusively monitor the framing of any incoming
T1/E1 signals from the drop side. Figure 9-33 shows the T1/E1 Frame Monitor screen.
For each module, select a T1/E1 tributary to monitor in the T1/E1 TRIB column. Both the on-line and
off-line modules can monitor an incoming T1/E1 at the same time. Once a T1/E1 tributary is selected, the
FRAMING column will automatically display the type of framing, namely D4, ESF, or OOF (Out-Of-
Frame) for T1 or CCS, CAS, or OOF (Out-Of-Frame) for E1.
The T1 errored counts are incremented in the following fashion:
D4 Framing ESF Framing

Errored Seconds Any Frame Bit Error in 1 second CRC error in 1 second
Severely Errored Seconds 320 Frame Bit Errors/LOS/OOF 320 CRC errors/LOS/OOF
The E1 errored counts are incremented in the following fashion:
Errored Seconds Any Frame Bit Error in 1 second

Severely Errored Seconds 320 Frame Bit Errors/LOS/OOF
TA-200 OP
8/29/03 9-33
Figure 9-33: T1/E1 Frame Monitor
Figure 9-34: PM13/PM13E Front Panel Monitor
TA-200 OP
8/29/03 9-34
9.3.23 PM13/PM13E Front Panel Monitor
The PM13 and PM13E modules have a bantam jack on the front panel that provides a T1/E1 monitor
point for any of the incoming T1/E1 tributaries from the drop ports. Figure 9-34 shows the Front Panel
Monitor screen.
For each module, simply select a T1/E1 tributary to monitor. Selections can be made for the incoming
T1/E1s from the drop ports. Once the tributary is selected, the signal from the selected tributary will be
transmitted out the front bantam connector. Monitoring a T1 or E1 will not disrupt the live traffic on the
selected tributary.
When a T1/E1 tributary is selected and downloaded, the PM13/PM13E module’s status LED will turn
yellow and a minor alarm will be generated indicating that a maintenance condition is active.
Once the selections are made, ‘click’ on Save to download the changes to the modules.
9.4 MPU Module Configuration
The MPU has three configuration options; setting the baud rate of the Terminal Port, setting the time, and
setting the date. The time and date settings are used by the MPU to time-stamp the alarm traps sent out
the SNMP (10Base-T) port. Figure 9-35 shows the configuration screen.
The default baud rate setting is Auto baud. However, the baud rate is only displayed and cannot be
adjusted via the Web Browser. The baud rate selections are:
1200 baud
2400 baud
4800 baud
9600 baud
19.2K baud
38.4K baud
57.6K baud
115.2K baud
Auto baud
9.4.1 MPU Alarms

The alarm summary screen shows the status summary of the on-line and off-line MPU modules.
The screen is shown in Figure 9-36. The MPU alarm summary shows the MPU status for the left and
right modules. Major and Minor alarms for the MPU indicate the level of alarm for the MPU. A Major
alarm will be declared if the MPU FPGA is not programmed. Minor Alarms will be generated for MPU
internal clock or circuitry failure. If the failure is protected by the redundant MPU (if equipped) the alarm
will be Minor. If not protected, the alarm will be Major. The MPU failures reported will be either for
the Watch-dog Timer (WDT), the Real Time Clock (RTC), or the Communications to the redundant MPU
(Comm). The STATUS indication will show whether the MPU is On-line, Off-line, Missing (if the
redundant module is configured but unplugged), or Empty (if the redundant MPU is not configured).
TA-200 OP
8/29/03 9-35
Figure 9-36: MPU Alarm Summary
TA-200 OP
8/29/03 9-36
10 GENERAL SYSTEM SPECIFICATIONS
This chapter provides specifications and electrical requirements for the TransAccess 200 System.
10.1 General Specifications
Table 10-1 lists specifications for the TransAccess 200 System and associated modules.
TABLE 10-1: TransAccess 200 SYSTEM SPECIFICATIONS

Specification Description
Shelf Capacities: Up to 2 MPU Modules.
Up to 14 PM13 or OMX3 Modules.
Shelf Size: 3.5” (8.89 cm) high by 20.925” (53.15 cm) wide by 12” (30.48 cm)
deep.
2 EIA Rack Mounting Units.
Weight: 18 lbs. max.
Power Consumption: Fully loaded shelf: 2.7A @ -48VDC/130 watts max.
Fully loaded shelf: 5.4A @ +24VDC/130 watts max.
MPU Module: 0.083A/4 watts (@ -48VDC)
PM13/PM13E Module: 0.156A/7.5 watts (typical online @ -48VDC)
0.119A/5.7 watts (typical offline @ -48VDC)
OMX3 Module: 0.187A/9.0 watts (@ -48VDC)
Environmental: Ambient operating temperature: 0° to +45° C
Storage temperature: -20° to +85° C
Relative humidity: 95% non-condensing
Altitude: to 12,000 ft (3660 m)
10.1.1 Physical Configuration

The TransAccess 200 System is designed into a 23" shelf and may be installed in standard 23" racks. The
TransAccess 200 is powered directly by either -48 VDC or +24 VDC. Separate –48V or +24V modules
must be ordered for each type of DC powered system.
10.2 Electrical Requirements
The TransAccess 200 System operates in the following DC electrical environments:
• -40 to -70 VDC at 130 watts per shelf
• +18 to +36 VDC at 130 watts per shelf
10.2.1 DC Power Requirements

The DC-powered TransAccess 200 System requires no external power supply modules. Connections
from the DC power source are made directly to each TransAccess 200 shelf. If redundancy is required,
the shelves accept both "A" and "B" battery leads.
Primary (A lead) and secondary (B lead) power sources connect to the backplane of each shelf in an
TransAccess 200 node using solderless lug-type screw connections.
When supplying DC power to a single TransAccess 200 shelf:
TA-200 OP
8/29/03 10-1
• Always use a separate cable run for each TransAccess 200 shelf.
• Cable diameter must be 12 gauge for distances not to exceed 100 feet.
• Power cables require shielding.
• Ensure that battery voltage is correct according to Section 7-2
10.3 MPU Module Specifications
10.3.1 General Specifications

Power Range: -40 to -70 VDC inputs (A and B Battery)
+18 to +36 VDC inputs (A and B Battery)
Power Consumption: approx. 4 watts
PCB Dimensions: approx. 3.5” x 10”
Weight: 1/3 lbs.
10.4 PM13 Module Specifications

Power Consumption: approx. 7.5 watts typical (online module)
Weight: 1/3 lbs.
10.4.2 T1 Interface Specifications

Line Rate: 1.544 Mbps +/- 50ppm
Line Format: Bipolar B8ZS or AMI
Framing: ESF, D4, or Unframed
LBO Settings: 0 to 655 feet
Amplitude: 2.4 volts to 3.6 volts (3.0 volts typical) – with LBO
Output Jitter: 0.05 maximum
Input Dynamic Range: 0.5 volts peak minimum

Line Format: Bipolar (B3ZS)
Framing: AT45 or M13
LBO Settings: < 225 ft. or > 225 ft.
Amplitude: +/- 0.67 volts (+/- 10%) – with LBO
Output Jitter: 0.05 UI maximum with jitter-free input clock
Input Dynamic Range: 35mV peak minimum
TA-200 OP
8/29/03 10-2
10.4.4 STS-1 Interface Specification
VT1.5 Mapping: Asynchronous T1’s
10.5 OMX3 Module Specifications

Power Consumption: approx. 9 watts typical (online module)
Weight: 1/3 lbs.

10.5.3 STS-1 Interface Specification

10.5.4 OC-3 Interface Specification
Laser: 1310 Single-mode
Power Budget: 20 db
Receiver Sensitivity: -34 dbm
Optical Connection: LC transceiver connector
TA-200 OP
8/29/03 10-3
10.6 PM13E Module Specifications

Power Consumption: approx. 7.5 watts typical (online module)
Weight: 1/3 lbs.

10.6.3 STS-1/AU3 Interface Specification

10.6.4 E1 Interface Specifications

Line Format: Bipolar HDB3 or AMI
Framing: CCS, CAS, or Unframed
LBO Settings: 0 to 655 feet
Amplitude: 2.7 Volts to 3.3 Volts - 120 ohm balanced
Output Jitter: 0.05 maximum
Input Dynamic Range: 0.5 volts peak minimum
TA-200 OP
8/29/03 10-4
11 APPENDIX B – T3 FRAMING FORMATS
The multiplexing involved in forming a T3 signal is a two-step process. The first step is the multiplexing
of four T1 signals into one T2 signal. The second step is the combining of seven T2 signals to form a T3
signal. The T3 Service Module offers two industry standard T3 formats to accomplish this:
• M13 format
• C-Bit Parity format
Both steps in the multiplexing process require bit stuffing, a synchronization method used to adjust
varying input rates. The M13 format requires the use of specific bits within each subframe to control the
occurrence of bit stuffing, whereas bit stuffing is preset in each subframe of the C-Bit Parity format. By
freeing up this group of bits for other uses, the C-Bit Parity format available with the TransAccess 200
System offers the following additional maintenance capabilities:
• An application identification channel
• Communication data links
• Bi-directional end-to-end parity checking
The following paragraphs describe how each of the framing formats combines 28 separate T1 signals into
a single DS3 signal.
11.1 M13 FRAMING FORMAT FOR T2 FRAMING

The first step is to combine four T1 signals to form one T2 signal. The T2 frame created with the M13
Framing format, Figure 11-1, is generally called a T2 M-frame. The T2 M-frame is composed of four
subframes designated M1 through M4. Each subframe consists of 6 blocks containing 49 bits each. The
first bit in each block is a T2 overhead bit, or OH-bit. Each T2 M-frame contains 24 OH-bits (6 blocks
per subframe x 4 subframes per M-frame). The remaining 48 bits in a block are T1 information bits. The
total number of T1 information bits in a T2 M-frame is 1,152 (48 bits per block x 6 blocks per subframe x
4 subframes per M-frame).
The four subframes do not represent the four individual T1 signals, one for one. Rather, interleaving the
four T1 signals bit-by-bit, as demonstrated in Figure 11-1 forms the T2 M-frame.
TA-200 OP
8/29/03 11-1
49 BITS
OH 1 2 3 4 1 2 3 4 - - - - - 4 1 2 3 4
BLOCK1 BLOCK2 BLOCK3 BLOCK4 BLOCK5 BLOCK6
294 BITS
M1 SUBFRAME M2 SUBFRAME M3 SUBFRAME M4 SUBFRAME
DS2 M-FRAME
4 X 294 = 1176 BITS
(1152 INFORMATION BITS)
NOTE:
1 = BIT FROM T1 CIRCUIT 1
Figure 11-1: M13 Format T2 Frame
Notice that each block in every subframe has the bit sequence:
OH 01 02 03 04
The overhead bit, OH, leads off every block and is followed by the interleaved T1 information bits where
0n designates the time slot devoted to T1 input n. Following every 48 T1 information bits, 12 bits from
each of the 4 T1 signals, a T2 OH-bit is inserted. The total number of T1 information bits transmitted in
one second in a T2 M-frame is calculated by multiplying the T1 rate by the number of T1 signals in an M-
frame:
1.544 Mbps x 4 = 6.176 Mbps
To provide extra bandwidth for bit stuffing and OH-bits, an overall rate of 6.312 Mbps is chosen.
TA-200 OP
8/29/03 11-2
11.2 M13 Format DS2 Overhead Bits
The M13 T2 overhead bits (OH-bits) provide alignment and bit stuffing control. M13 OH-bits are located
in the first bit position of every block. The location of various OH-bits designated F, M, and C is
presented in Table 11-1.
Frame bits, or F-bits, form the frame alignment signal. There are eight F-bits per T2 M-frame (two per
subframe). The T2 F-bits are located in the first bit position in blocks 3 and 6. The frame alignment
pattern "01" is repeated in every subframe.
Multiframe bits, or M-bits, form the multiframe alignment signal. There are four M-bits per T2 M-
frame (one per subframe). The M-bits are located in the first bit position in each subframe. Transmission
equipment uses the M-bit pattern "011X", where X can equal 0 or 1, to locate the four subframes.
C-bits are used to control bit stuffing. There are three C-bits per T2 subframe located in the first bit
position in blocks 2, 4, and 5. The use of C-bits in the bit stuffing process is discussed in the M13 Format
Bit Stuffing paragraph.
TABLE 11-1: M13 Format T2 M-Frame Overhead Bit assignment

BLOCK 1 BLOCK 2 BLOCK 3 BLOCK 4 BLOCK 5 BLOCK 6
M1 M0 = 0 C11 F0 = 0 C12 C13 F1 = 1
SUBFRAME
M2 M1 = 1 C21 F0 = 0 C22 C23 F1 = 1
SUBFRAME
M3 M1 = 1 C31 F0 = 0 C32 C33 F1 = 1
SUBFRAME
M4 MX = X C41 F0 = 0 C42 C43 F1 = 1
SUBFRAME
NOTES:
1. F0 F1 is the frame alignment signal. F0 = 0 and F1 = 1.
2. M0 M1 M1 MX is the multiframe alignment signal. M0 = 0, M1 = 1, and MX may be a 0 or a 1.
3. C11 C12 C13 = stuffing indicators for T1 input 1.
C21 C22 C23 = stuffing indicators for T1 input 2.
If the three C-bits in a subframe are all zeros, no stuffing was done for the T1 input associated with that subframe.
If the three C-bits are all ones, stuffing was done.
11.3 M13 FRAMING FORMAT FOR T3 FRAMING

The second step in forming a T3 signal is the multiplexing of seven T2 signals, each containing four T1
signals, into one T3 signal. The same method used to multiplex the four T1 signals is used to multiplex
the T2 signals. Figure 11-2 shows the T3 framing format known as the standard M13 asynchronous
format. The T3 frame created in this step, sometimes called a T3 M-frame, is composed of seven
subframes designated 1st through 7th. Each subframe consists of eight blocks containing 85 bits each.
The first bit in each subframe is a T3 OH-bit. Each T3 M-frame contains 56 OH-bits (8 blocks per
subframe x 7 subframes per M-frame). The remaining 84 bits in a block are T2 information bits. The
TA-200 OP
8/29/03 11-3
total number of T2 information bits in a T3 M-frame is 4,704 (84 bits per block x 8 blocks per subframe x
7 subframes per M-frame).
85 BITS
OH 1 2 3 4 5 6 7 1 - - - - - 3 4 5 6 7
BLOCK1 BLOCK2 BLOCK3 BLOCK4 BLOCK5 BLOCK6 BLOCK7 BLOCK8
680
BITS
SUBFRAME1 SUBFRAME2 SUBFRAME3 SUBFRAME4 SUBFRAME5 SUBFRAME6 SUBFRAME7
T3 M-FRAME
7 X 680 = 4760 BITS
(4704 INFORMATION BITS)
NOTES:
Figure 11-2: M13 Format T3 Frame
11.3.1 M13 Format T3 Overhead Bits

The M13 format T3 overhead bits (OH-bits) provide alignment, error checking, in-band communications,
and bit stuffing control information. The OH-bits are located in the first bit position of every block. See
Table 11-2 for T3 overhead bit assignment.
Frame bits (F-bits) form the frame alignment signal. There are 28 F-bits per T3 M-frame (four per
subframe). The T3 F-bits are located in the first bit position in blocks 2, 4, 6, and 8 of every subframe.
The frame alignment pattern "1001" is repeated in every subframe.
Multiframe bits (M-bits) form the multiframe alignment signal. There are three M-bits per T3 M-frame
located in the first bit position in block 1 of subframes 5, 6, and 7. T3 equipment uses the M-bit pattern
"010" to locate the seven subframes.
TA-200 OP
8/29/03 11-4
Table 8-11: M13 Format T3 M-Frame Overhead Bit Assignment
BLOCK 1 BLOCK 2 BLOCK 3 BLOCK 4 BLOCK 5 BLOCK 6 BLOCK 7 BLOCK 8
1st SUBFRAME X-BIT F1 = 1 C11 F0 = 0 C12 F0 = 0 C13 F1 = 1
2nd SUBFRAME X-BIT F1 = 1 C21 F0 = 0 C22 F0 = 0 C23 F1 = 1
3rd SUBFRAME P-BIT F1 = 1 C31 F0 = 0 C32 F0 = 0 C33 F1 = 1
4th SUBFRAME P-BIT F1 = 1 C41 F0 = 0 C42 F0 = 0 C43 F1 = 1
5th SUBFRAME M 0= 0 F1 = 1 C51 F0 = 0 C52 F0 = 0 C53 F1 = 1

NOTES:
1. F1 F0 F0 F1 is the frame alignment signal. F0 = 0 and F1 = 1.
2. M0 M1 M0 is the multiframe alignment signal. M0 = 0 and M1 = 1.
3. P is the parity information taken over all information bits in the preceding M-frame.
4. X-bits may be used to report far-end alarm conditions (T3 LOS or OOF). In any one M-frame, the two X-bits must be
identical and may not change more than once per second.
5. C11 C12 C13 = stuffing indicators for T2 input 1.
C-bits are used to control bit stuffing. There are three C-bits per T3 subframe located in the first bit
position in blocks 3, 5, and 7. The use of C-bits in the bit stuffing process is discussed in the M13 Format
Bit Stuffing paragraph.
X-bits are far-end alarm signals. There are two X-bits per T3 M-frame located in the first bit position in
block 1 of subframes 1 and 2. In any one T3 M-frame, the two X-bits must be identical—either both ones
or both zeros. In addition, the source may not change the state of the X-bits more than once every second.
Parity bits (P-bits) contain the parity information. There are two P-bits per T3 subframe located in the
first bit position of subframes 3 and 4. T3 sources compute parity over all 4,704 information bits (4,760
total bits minus 56 OH-bits) following the first X-bit in a T3 M-frame. The resulting parity information is
inserted in the P-bit positions of the following frame. The state of the two P-bits within a single T3 M-
frame is always identical. The two P-bits are set to "1" if the previous T3 M-frame contained an odd
number of ones. Conversely, the two P-bits are set to "0" if the previous T3 M-frame contained an even
number of ones.
The parity bits provide a means of in-service error detection. If, on the receive side, the number of ones
for a given frame does not match the parity information in the following frame, one or more bit errors
occurred during the transmission.
TA-200 OP
8/29/03 11-5
11.4 M13 Format Bit Stuffing
The four T1 signals are asynchronous relative to each other, and therefore may be operating at different
rates, Figure 11-3. The seven T2 signals may be asynchronous relative to each other because they may
not have been formed within a common multiplexer, Figure 11-4. Bit stuffing is used to adjust for
different input rates occurring on both the T2 and T3 levels of the T3 multiplexing process (see Table 11-
3). In both cases, the state of the three C-bits determines whether or not bit stuffing takes place.
Specifically, the state of the three C-bits in a subframe indicates whether stuffing occurs for the associated
T1 input signal. The multiplexing equipment physically determines the state of the C-bits.
T1 INPUT 1 = 1,544,000 bps

1,545,796 bps
STUFFING = 1796 bps
T1 INPUT 2 = 1,545,796 bps

1,545,796 bps
STUFFING = 0 bps
T2 OUTPUT = 6,312,000 bps
T1 INPUT 3 = 1,540,429 bps

1,545,796 bps
STUFFING = 5367 bps
T1 INPUT 4 = 1,544,500 bps

1,545,796 bps
STUFFING = 1296 bps
NOTE: THE “INTERMEDIATE” T1 RATE OF 1,545,796 BPS IS OBTAINED BY ADDING A GIVEN

T1 INPUT RATE TO ITS ASSOCIATED STUFFING RATE. THE “PSEUDO” T2 OUTPUT
RATE OF 6,312,000 BPS IS OBTAINED BY ADDING THE FOUR “INTERMEDIATE” T1
RATES AND THE T2 OVERHEAD RATE.
Figure 11-3: M13 Multiplexing of T1 Signals
In each T2 frame, one bit can be stuffed for each of the four T1 signals. In each T3 frame, one bit can be
stuffed for each of the seven T2 signals. The location of the stuffed bit is the first information bit position
associated with that T1 or T2 signal following the last F1 bit in a subframe. If the three C-bits are all
zeros, no stuffing occurs and the associated "stuff" bit is treated as a normal T1 or T2 information bit.
TA-200 OP
8/29/03 11-6
During the demultiplexing process, the three C-bits are used to determine if the "stuff" bit is to be
included in the reconstructed T1 or T2 signal. If C21=C22=C23=0, for example, then bit 2 following F1 in
the last block of subframe M2 is an information bit, and is therefore included in the reconstruction of the
second T1 signal. If, to consider another example, C61=C62=C63=0, then bit 6 following F1 in the last block
of subframe M6 is an information bit, and is therefore included in the reconstruction of the sixth T2
signal.
Table 11-3: T2 AND T3 BIT STUFFING RATES

T2 BIT STUFFING RATES T3 BIT STUFFING RATES
T2 frame rate 6,312,000 bps T3 frame rate 44,736,000 bps

(Maximum Stuffing Rate) 1,176 bits/frame (Maximum Stuffing Rate) 4,760 bits/frame
=5,367.35 frames/sec =9,398.32 frames/sec

x24 OH-bits/frame T3 OH-bits/sec x 56 OH-bits/frame
T2 OH-bits/sec 128,816.40 OH-bits/sec 526,305.92 OH-bits/sec
Bit Stuffing Rate 6,312,000 bps (total T2 bits) Bit Stuffing Rate for T2 44,736,000 bps (total T3 bits)
for T1 operating -6,176,000 bps (4 x 1.544 Mbps) operating at nominal rate -44,184,000 bps (7 x 6.312 Mbps)
at nominal rate -128,816 bps (T2 OH-bits) -526,306 bps (T3 OH-bits)
7,184 bps (Stuffing Bits 25,694 bps (Stuffing Bits
Available) Available)
÷4 (4 T1 signals) ÷7 (7 T2 signals)
= 1,796 bps = 3,671 bps
Maximum Allowable 6,312,000 bps (T2 Signal Rate) Maximum Allowable T2 44,736,000 bps (T3 Signal Rate)
T1 Rate -128,816 bps (T2 OH-rate) Rate -526,306 bps (T3 OH-rate)
6,183,184 bps Total T1 bits 44,209,694 bps Total T2 bits
÷4 (4 T1 Signals) ÷7 (7 T2 Signals)
=1,545,796 bps =6,315,671 bps
Minimum Allowable -5,367 (Max Stuff Rate) Minimum Allowable T2 -9,398 (Max Stuff Rate)
T1 Rate 1,540,429 bps Rate 6,306,272 bps
11.5 C-BIT PARITY FORMAT

The M13 asynchronous framing format discussed above uses all 21 C-bits for bit stuffing control. Since
M13 multiplexers perform bit stuffing when forming the seven T2 signals, the resulting T2 signals can be
synchronous to each other. Therefore, the bit stuffing that takes place when seven T2 signals are
multiplexed into a single T3 signal is redundant. The C-bit Parity format available with the TransAccess
200 System, unlike the M13 format, does not use the T3-level C-bits for bit stuffing control. Instead, the
C-bits, as well as the X-bits, are redefined to provide:

• Far-end alarm and channel control
• Bi-directional performance monitoring from near-end and far-end terminal equipment
TA-200 OP
8/29/03 11-7
T2 INPUT 1 = 6,307,500 bps
6,315,671 bps
STUFFING = 3761 bps
T2 INPUT 2 = 6,307,500 bps

6,315,671 bps
STUFFING = 3671 bps
T2 INPUT 3 = 6,307,500 bps

6,315,671 bps
STUFFING = 3671 bps
T3 OUTPUT = 44,736,000 bps
T2 INPUT 4 = 6,307,500 bps

6,315,671 bps
STUFFING = 3671 bps
T2 INPUT 5 = 6,307,500 bps

6,315,671 bps
STUFFING = 3671 bps
T2 INPUT 6 = 6,307,500 bps 6,315,671 bps
STUFFING = 3671 bps

NOTE:
THE “INTERMEDIATE” T2 RATE OF 6,315,671
BPS IS OBTAINED BY ADDING A GIVEN T2
INPUT RATE TO ITS ASSOCIATED STUFFING
T2 INPUT 7 = 6,307,500 bps RATE. THE T3 OUTPUT RATE OF 44.736 MBPS IS
6,315,671 bps OBTAINED BY ADDING THE SEVEN
“INTERMEDIATE” T2 RATES AND THE T3
OVERHEAD RATE.
STUFFING = 3671 bps
Figure 11-4: M13 Multiplexing of T2 Signals
TA-200 OP
8/29/03 11-8
Table 11-4 provides T3 M-frame overhead bit assignment within the C-bit parity framing format. The
definition for the framing, multiframe, and parity bits are the same as in standard M13 asynchronous
format. The revised X-bit and C-bit definitions are described in the following paragraphs.
Table 11-4: C-Bit Parity T3 M-Frame Overhead Bit Assignment

BLOCK 1 BLOCK 2 BLOCK 3 BLOCK 4 BLOCK 5 BLOCK 6 BLOCK 7 BLOCK 8
1st SUBFRAME X-BIT F1 = 1 AIC F0 = 0 N/A F0 = 0 N/A F1 = 1
2nd SUBFRAME X-BIT F1 = 1 N/A F0 = 0 N/A F0 = 0 N/A F1 = 1
3rd SUBFRAME P-BIT F1 = 1 CP F0 = 0 CP F0 = 0 CP F1 = 1
4th SUBFRAME P-BIT F1 = 1 FEBE F0 = 0 FEBE F0 = 0 FEBE F1 = 1
5th SUBFRAME M 0= 0 F1 = 1 N/A F0 = 0 N/A F0 = 0 N/A F1 = 1
6th SUBFRAME M 1= 1 F1 = 1 N/A F0 = 0 N/A F0 = 0 N/A F1 = 1
7th SUBFRAME M 0= 0 F1 = 1 DL F0 = 0 DL F0 = 0 DL F1 = 1
NOTES:
1. F1 F0 F0 F1 is the frame alignment signal. F0 = 0 and F1 = 1.
2. M0 M1 M0 is the multiframe alignment signal. M0 = 0 and M1 = 1.
3. P is the parity information taken over all information bits in the preceding M-frame. Both P-bits equal 1 if the digital sum
of all information bits is 1. Both P-bits equal 0 if the sum is 0.
4. X-bits are used to indicate far-end T3 LOS or OOF conditions. In any one M-frame, the two X-bits must be identical and
may not change more than once per second.
AIC = Application Identification Channel = 1
5. N/A = Reserved Network Application Bit
DL = Data Link
CP = C-bit Parity
FEBE = Far-End Block Error
N/A = Not used by TransAccess 200 System
11.5.1 X-Bits
X-bits are far-end alarm signals. There are two X-bits per T3 M-frame located in the first bit position in
block 1 of subframes 1 and 2. In any one T3 M-frame, the two X-bits must be identical—either both ones
or both zeros. In addition, the source may not change the state of the X-bits more than once every second.
As in the M13 format, the X-bits are located in the first bit position in block 1 of subframes 1 and 2.
TA-200 OP
8/29/03 11-9
11.5.2 C-Bits
In the C-bit parity format, the C-bits are used to provide the following maintenance capabilities:
• Bi-directional performance monitoring from near-end and far-end terminal equipment
11.5.2.1 Application Identification Channel (AIC)

The first C-bit in subframe 1 is defined as an application identification channel (AIC) and can be used by
T3 terminal equipment to automatically identify a specific T3 framing format. For C-bit parity, this
position is set to 1.
11.5.2.2 Reserved Network Application Bit

The second C-bit in subframe 1 is reserved for future applications.
11.5.2.3 Data Links (Communication Data Links)

The three C-bits located in subframe 7, all designated DL, are defined as data links for applications and
terminal-to-terminal path maintenance and will be used in future releases of the TransAccess 200 System.
11.5.2.4 T3 Parity Bits

The three C-bits in subframe 3, designated CP-bits, are used to carry the T3 path parity information. At
the T3 terminal equipment (TE) transmitter, the CP-bits are set to the same value as the two P-bits.
Unlike the P-bits that are subject to correction by each facility section in the T3 path, the CP-bits pass
through the network unchanged (except in the case of errors). The T3 TE receiver can determine if an
error occurred in an M-frame by computing the parity based on the contents of the given M-frame and
comparing this parity value with the parity received in the CP-bits in the following M-frame. As a result,
the C-bit Parity format provides end-to-end parity checking.
11.5.2.5 Far-End Block Error Function (FEBE)

The far-end block error (FEBE) function uses the three C-bits in subframe 4. The FEBE function,
illustrated in Figure 11-5, involves the monitoring of incoming (westbound) transmission on the part of
the near-end terminal equipment for the occurrence of framing or parity errors. Upon detection of a
framing or parity error event via the westbound CP-bits, the near-end terminal equipment:
• Counts the event as a CP-bit parity error
• Indicates the occurrence of the error to the far-end terminal equipment via the eastbound
FEBE bits
To inform the far-end terminal equipment of the error, the three FEBE bits are set to 000. Under error-
free conditions, the three FEBE bits are set to 111. Because the T3 terminal equipment monitors both the
TA-200 OP
8/29/03 11-10
CP and FEBE bits, as well as the FEAC channel, the overall performance of the T3 path can be
determined at either end of the path for both directions of transmission.
11.5.3 C-Bit Parity Format Bit Stuffing

T1 to T3 multiplexing with the C-bit Parity format is basically the same two-step multiplexing process
described for the standard M13 asynchronous format. With the C-bit Parity format, bit stuffing occurs
100% of the time during the second step of multiplexing, eliminating the need to use C-bits for bit
stuffing control. This "full-time" bit stuffing at the T3 level, however, requires the seven T2 signals to be
lower in frequency than the 6.312 Mbps used with the M13 format. Therefore, in the first step of
multiplexing, four T1 signals are multiplexed to form a "pseudo" T2 signal at a frequency of 6,306,272
bps. This frequency is chosen in order that the seven "pseudo" T2 signals are multiplexed along with the
"full-time" DS3-level stuff bits and the 56 OH-bits to produce the nominal T3 output frequency of 44.736
Mbps.
EASTBOUND
NEAR-END FAR-END
TERMINAL TERMINAL
EQUIPMENT EQUIPMENT
WESTBOUND
Figure 11-5: DS3 Span
Figure 11-6 illustrates the first step of T1 to T3 multiplexing in the C-bit Parity format. Note that the bit
stuffing rates are lower than those used for M13-type multiplexing (Figure 11-3). The lower bit stuffing
rates yield an intermediate T1 rate of 1,544,364 bps (instead of 1,545,796 bps) and therefore a T2 pseudo
output rate of 6,306,272 bps (instead of 6,312,000 bps). Note also that this new intermediate T1 rate
forces the maximum allowable T1 input rate (i.e., when bit stuffing is 0 bps) to be 1,544,364 bps.
TA-200 OP
8/29/03 11-11
T1 INPUT 1 = 1,544,000 bps
1,544,364 bps
STUFFING = 364 bps
T1 INPUT 2 = 1,544,000 bps

1,544,364 bps
STUFFING = 364 bps

T2 OUTPUT = 6,306,272 bps
T1 INPUT 3 = 1,544,000 bps

1,544,364 bps
STUFFING = 364 bps
T1 INPUT 4 = 1,544,000 bps 1,544,364 bps
STUFFING = 364 bps
NOTE: THE “INTERMEDIATE” T1 RATE OF 1,544,364 BPS IS OBTAINED BY ADDING A GIVEN

T1 INPUT RATE TO ITS ASSOCIATED STUFFING RATE. THE “PSEUDO” T2 OUTPUT
RATE OF 6,306,272 BPS IS OBTAINED BY ADDING THE FOUR “INTERMEDIATE” T1
RATES AND THE T2 OVERHEAD RATE.
Figure 11-6: C-Bit Parity Multiplexing of T1 Signals
TA-200 OP
8/29/03 11-12
Figure 11-7 shows the complete progression from a nominal T1 rate (1.544 Mbps) to a nominal T3 rate
(44.736 Mbps) for both the standard M13 asynchronous format and the C-bit Parity format.
M13 FORMAT C-BIT FORMAT

Nominal T1 Rate 1,544,000 bps 1,544,000 bps
+ T1 Bit Stuffing Rate 1,796 bps 364 bps
= "Intermediate" T1 Rate 1,545,796 bps 1,544,364 bps

x 4 T1s per T2 4 4
= Subtotal 6,183,184 bps 6,177,456 bps

+ T2 Overhead Rate 128,816 bps 128,816 bps
= Nominal T2 Rate 6,312,000 bps 6,306,272 bps

+ T2 Bit Stuffing Rate 3,671 bps 9,398 bps
= "Intermediate" T2 Rate 6,315,671 bps 6,315,671 bps

x 7 T2s per T3 7 7
= Subtotal 44,209,694 bps 44,209,694 bps

+ T3 Overhead Rate 526,306 bps 526,306 bps
= Nominal T3 Rate 44,736,000 bps 44,736,000 bps
NOTE: THE CALCULATIONS ARE NOT EXACT BECAUSE EACH

INTERMEDIATE RESULT IS ROUNDED OFF TO THE NEAREST WHOLE
NUMBER.
Figure 11-7: M13 Format vs. C-Bit Parity Format
TA-200 OP
8/29/03 11-13
12 APPENDIX C – SONET FRAMING
SONET (Synchronous Optical NETwork) is an American National Standard for a high-speed
optical telecommunications network based on the principles of synchronous multiplexing. The
basic structure of a SONET signal is the STS-1 (Synchronous Transport Signal Level 1) and has a
rate of 51.840 Mbps. The optical equivalent of STS-1 is called OC-1 (Optical Carrier Level 1).
Higher levels of SONET signals are created by byte-interleaving STS-1 signals. Table 12-1
shows the SONET Signal Hierarchy.
TABLE 12-1: SONET Signal Hierarchy

Synchronous Transport Optical Carrier Line Rate (Mbps)
Signal
VT1.5 none 1.728
STS-1 OC-1 51.84
STS-3 OC-3 155.52
STS-12 OC-12 622.08
STS-48 OC-48 2488.32
12.1 SONET Network Hierarchy

The SONET standard uses a layered approach, with the overhead and transport functions divided
into four layers. They are the Photonic, Section, Line, and Path Layers, Figure 12-1.
The Photonic layer deals with the transmission of actual bits of information across the fiber. It
converts the electrical signals to optical signals, and vice versa. There is no overhead associated
with the photonic layer.
The Section layer deals with the transmission of multiplexed STS frames across the physical
medium. An OC-3 Section is any part of the optical transmission path that interfaces a fiber
regenerator. It may lie between two regenerators or between a regenerator and a SONET
multiplexer or SONET digital switch.
The Line layer provides for the reliable transmission of the Path layer payload and its associated
overhead across the physical medium. A Line span lies between two SONET network elements
such as a SONET multiplexer or SONET digital switch. There may or may not be sections within
the Line layer.
The main purpose of the Path layer is to map the various services into the STS-1 payload
capacity, which is required by the Line layer. The Synchronous Payload Envelope SPE defines a
Path span. The ends of the Path are where the SPEs are assembled and disassembled.
TA-200 OP
8/29/03 12-1
PATH
LINE LINE
SECTION SECTION SECTION SECTION
MULTI- REG ADM OR REG MULTI-

PLEXER SONET PLEXER
(TX3) DCS (TX3)
SECTION/ SECTION SECTION/LINE SECTION SECTION/

LINE/PATH TERMINATING TERMINATING TERMINATING LINE/PATH
TERMINATING EQUIPMENT EQUIPMENT EQUIPMENT TERMINATING
EQUIPMENT EQUIPMENT
REG: REGENERATOR
ADM: ADD-DROP MULTIPLEXER
DCS: DIGITAL CROSS-CONNECT SYSTEM
Figure 12-1: SONET Signal Hierarchy
12.2 SONET STS-1 Frame Structure

The STS-1 signal frame comprises 9 rows of bytes 90 columns wide, Figure 12-2. Total frame
capacity is 810 bytes, or 6480 bits. A frame rate of 8000 frames per second gives a signal rate of
51.84 Mbps (810 bytes * 8 bits/byte * 8000 frames/sec).
The STS-1 frame consists of two components: Transport Overhead and Synchronous Payload
Envelope (SPE).
12.2.1 Transport Overhead

The Transport Overhead occupies the first 3 columns of the STS-1 frame (27 bytes), Figure 12-2
and Figure 12-3. The Transport Overhead consists of the Section Overhead and the Line
Overhead. The Section Overhead is located in the first three rows of the three columns of the
Transport Overhead. The Section Overhead provides facilities to manage and maintain the
transportation of the SPE over a SONET Section span.
The Line Overhead is located in the remaining six rows of the three columns making up the
Transport Overhead. The Line Overhead provides facilities to manage and maintain the
transportation of the SPE over a SONET Line span.
The remaining 87 columns of the STS-1 frame (783 bytes) are allocated to the Synchronous
Payload Envelope (SPE), giving the SPE a channel capacity of 50.11 Mbps.
TA-200 OP
8/29/03 12-2
SERIAL SIGNAL
STREAM
F F F F
51.84 MBPS
SYNCHRONOUS
PAYLOAD
ENVELOPE
TRANSPORT PATH OVERHEAD
9 ROWS
OVERHEAD
PAYLOAD CAPACITY = 49.54 MBPS
DESIGNED FOR DS3 TRANSPORT
9 BYTES
1 COLUMN 86 COLUMNS
Figure 12-2: SONET STS-1 Frame Structure
SECTION
OVERHEAD
1 COLUMN
3 ROWS
PATH
PATH OVERHEAD
OVERHEAD
6 ROWS
9 ROWS
3 COLUMNS
LINE
OVERHEAD
STS-1 SYNCHRONOUS PAYLOAD ENVELOPE
Figure 12-3: SONET STS-1 Overhead
TA-200 OP
8/29/03 12-3
Table 12-2: STS-1 Section and line Overhead Byte Assignment
SECTION FRAMING FRAMING STS-1 ID

OVERHEAD A1 A2 C1
BIP-8 ORDERWIRE USER
B1 E1 F1
DATA COM DATA COM DATA COM
D1 D2 D3
LINE POINTER POINTER POINTER
OVERHEAD H1 H2 H3
BIP-8 APS APS
B2 K1 K2
D4 D5 D6
D7 D8 D9
D10 D11 D12
GROWTH GROWTH ORDERWIRE
Z1 Z2 E2
12.2.2 Synchronous Payload Envelope

The STS-1 SPE is divided into two parts: Path Overhead and Payload Capacity.
12.2.2.1 Path Overhead

The SPE Path Overhead provides the alarm monitoring and performance monitoring capabilities
required to support and maintain transportation of the SPE, Table 12-3.
12.2.2.2 SPE Payload Capacity

The SPE Payload Capacity is designed to transport specific tributary signals. The STS-1 payload
capacity provides 774 bytes, structured as 86 columns of 9 bytes. This provides a 49.536 Mbps
transport capacity with a frame rate of 8000 Hz.
TA-200 OP
8/29/03 12-4
Table 12-3: STS-1 Path Overhead Byte Assignment
PATH PATH TRACE
OVERHEAD J1
BIP-8
B3
SIGNAL LABEL
C2
PATH STATUS
G1
USER CHANNEL
F2
MULTIFRAME
H4
GROWTH
Z3
GROWTH
Z4
GROWTH
Z5
12.2.2.3 Tributary Signals

The SONET STS-1 SPE provides transport for a DS3 (44.736 Mbps) tributary signal. Tributary
signals with a lower signal rate are accommodated by the SPE by the use of a Virtual Tributary
(VT) frame structure. Each virtual tributary frame is designed to carry a specific digital signal.
The most important of the virtual tributaries is the VT1.5, which is designed to accommodate a
T1 tributary signal. An SPE can carry up to twenty-eight VT1.5s. A list of the available Virtual
Tributaries is provided below, Table 12-4.
Table 12-4: Virtual Tributary Frame Structures

Virtual Digital Signal Frame Size Capacity
Tributary Structure (Bytes) (Mbps)
(Rows x
Columns)
VT1.5 T1 9x3 27 1.728

VT2 2M 9x4 36 2.304
VT3 T1c 9x6 54 3.456
VT6 DS2 9 x 12 108 6.912
12.3 SONET STS-3 Frame Structure

Higher order SONET signals are created using byte-interleaved multiplexing, which takes parallel
STS-1 signals and multiplexes them together, Figure 12-4. A SONET STS-3 signal is made up
of three parallel frame synchronized STS-1 signals that have been byte-interleaved together. A
two dimensional map for the STS-1 signal frame has the same 9-row depth of the STS-1, but has
270 columns - three times the number of an STS-1, Figure 12-4. Total frame capacity of the
STS-3 signal is 2430 bytes, or 19,440 bits. A frame rate of 8000 frames per second gives a signal
rate of 155.52 Mbps (2430 bytes * 8 bits/byte * 8000 frames/sec).
TA-200 OP
8/29/03 12-5
The first nine columns of the STS-3 frame contain the Transport (section and line) Overhead.
The remaining 261 columns contain the three SPEs of the three STS-1s making up the STS-3,
Figure 9-5.
STS-1
SIGNAL "A" A A A
STS-1
SIGNAL "B" B B B A B C A B C A B
BYTE
INTERLEAVED STS-3
MULTIPLEXER [3 * STS-1]
STS-1
SIGNAL "C" C C C
DENOTES 8-BIT BYTE

AT STS-1 SIGNAL RATE
DENOTES 8-BIT BYTE

AT STS-3 SIGNAL RATE
Figure 12-4: Synchronous Byte-Interleaved Multiplexing
2430 BYTE/S
SERIAL SIGNAL
PER FRAME
STREAM
F F F F
155.52 MBPS
9 ROWS
9 COLUMNS 261 COLUMNS

TRANSPORT 3 STS-1 SPEs
OVERHEAD INTERLEAVED
INTERLEAVED
Figure 12-5: SONET STS-3 Frame Structure
TA-200 OP
8/29/03 12-6

TA-200 Manual R7

Hochgeladen von

Dokumentinformationen

Originalbeschreibung:

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

TA-200 Manual R7

Hochgeladen von

Copyright:

Verfügbare Formate

TransAccess 200

U.S. GOVERNMENT RESTRICTED AND LIMITED RIGHTS

“DFARS” is the Department of Defense Supplement to the Federal Acquisition Regulation.

Turin Networks is a registered trademark of Turin Networks, Inc.

WARNING NO OPERATOR SERVICEABLE PARTS ARE INSIDE

This equipment is to be installed in a rack above a non-combustible surface or

Programmable Programmable Programmable P rogrammable Programmable Programmable P rogrammable Programmable

Figure 1-1: TransAccess 200 23” Shelf

Programmable Programmable Programmable Programmable Programmable Programmable

Figure 1-2: TransAccess 200 19” Shelf

Figure 1-3: PM13 Block Diagram

Figure 1-5: PM13E Block Diagram

• Unpacking the equipment and initial inspection.

• Mounting the equipment into the rack.

• Installing Redundancy Service Modules onto the shelf.

• Connecting office wiring to the shelf.

• Equipping MPU and Service Modules.

• Configuration and Testing.

2.1 Unpacking and Initial Inspection

IF PRODUCT IS RECEIVED DAMAGED:

• Flush mounting to the front of the rack (Figure 2-1a)

Figure 2-1a: Shelf Mounting Ear Position for Flush Mounting

Figure 2-1b: Shelf Mounting Ear Position for Offset Mounting

2. Locate mounting position in rack according to configuration, Figure 2-2.

PRECAUTION: IF THE TRANSACCESS 200 SYSTEM IS BEING INSTALLED

Figure 2-2: TransAccess 200 Rack Mounting

Figure 2-3: Battery A/B Connections

4. Connect earth ground lead to green mounting screw at rear of shelf.

Figure 2-4. Baffle Installation

2.3 Installation/Replacement of Service Modules

1. Locate the slot position for the module.

Service Module Facilities External Timing Power/Ground

Figure 2-7: TransAccess 200 External Connections

2.5.1 Battery & Ground Connections

Table 2-1: Battery Connections

Table 2-2: Office Alarm Contacts

• 10BaseT/RS422 – backplane jumpers J34/J35 in left-hand position

Table 2-4: T1/E1 Cable Connector Assignments

2.6 Equipping MPU and Service Modules

MPU Service Module

2.6.2 Service Modules

Programmable Programmable Programmable Programmable Programmable Programmable Programmable Programmable

• Error-free performance under normal conditions

The main communications tasks performed by the MPU Module include:

3.1.2 MPU Auxiliary Board

1. Locate the slot position for the module.

• Power is applied to TransAccess 200 and to all peripheral equipment.

If a malfunction occurs immediately after installing new equipment or replacing equipment at an

3.2 T3/STS-1 to T1 Programmable Multiplexer Module (PM13/PM13+)

3.2.1.1 Status Indicator

Service Module Facilities External Timing Power/Ground

PM13 RIMs Remote Management

PRECAUTION: IN SOME CASES, REPLACING A MODULE MAY DISRUPT

PRECAUTION: MODULES USED IN THIS EQUIPMENT CONTAIN

• T3/STS-1 Input Alarm (LOS/OOF/LOP/SLM)

Green Indicates one of the following conditions:

The troubleshooting procedure is summarized below:

3.2.4.3 Step 3. Perform Loopbacks and Non-intrusive Tests

When sufficient information is available to localize a problem to a particular T3/STS-1 or T1 connection,

PRECAUTION: BEFORE INITIATING LOOPBACK TESTS, NOTIFY ALL AFFECTED

Loopback tests (shown in Figure 3-2) to diagnose network failures include:

• T3/STS-1 Line Loopback

T1 test generation and detection is described in 4.5.2.10.2.