MX2810 M13 Multiplexer User Manual Manual P/N 61185001L1-1C CD P/N 32536153@A 4185001L1 4185001L2 4185001L3 4185001L4 1200287L1 1200287L5 1200287L7 1200291L1 1200291L5 61185001L1-1C April 2003 MX2810 Chassis with two PSUs and two DS3 Controllers MX2810 Chassis with two PSUs and one DS3 Controller MX2810 Chassis with one PSU and two DS3 Controllers MX2810 Chassis with one PSU and one DS3 Controller Amp to Punch-Down Cable 25 ft. Amp to Punch-Down Cable 50 ft. Amp to Punch-Down Cable 100 ft.
Trademark Information OpenView is a trademark of Hewlett-Packard Company. Spectrum is a registered trademark of Cabletron. 901 Explorer Boulevard P.O. Box 140000 Huntsville, AL 35814-4000 Phone: (256) 963-8000 © 2003 ADTRAN, Inc. All rights reserved. Printed in USA.
FCC regulations require that the following information be provided in this manual: 1. This equipment complies with Part 68 of FCC rules. On the bottom of the equipment housing is a label showing the FCC registration number and ringer equivalence number (REN). If requested, provide this information to the telephone company. 2. If this equipment causes harm to the telephone network, the telephone company may temporarily discontinue service.
Federal Communications Commission Radio Frequency Interference Statement This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.
Canadian Equipment Limitations Notice: The Canadian Industry and Science Canada label identifies certified equipment. This certification means that the equipment meets certain telecommunications network protective, operational, and safety requirements. The Department does not guarantee the equipment will operate to the user’s satisfaction. Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of the local telecommunications company.
Warranty and Customer Service ADTRAN will replace or repair this product within the warranty period if it does not meet its published specifications or fails while in service. Warranty information can be found at www.adtran.com/warranty. U.S. and Canada customers can also receive a copy of the warranty via ADTRAN’s toll-free faxback server at 877-457-5007. • Request document 414 for the U.S. and Canada Carrier Networks Equipment Warranty. • Request document 901 for the U.S.
Table of Contents List of Figures .................................................................................................................... xiii List of Tables ........................................................................................................................ xv Chapter 1. Introduction Product Overview ............................................................................................................... 1-1 Controller Card 1:1 Redundancy..............................
Table of Contents Power Connection ......................................................................................................... 2-8 Front Panel ........................................................................................................................... 2-9 ACO Buttons .................................................................................................................. 2-9 LED Descriptions ..............................................................................
Table of Contents Terminal Time Out ............................................................................................. 3-25 IP Security ............................................................................................................ 3-25 IP Hosts ................................................................................................................ 3-25 Date & Time ...............................................................................................................
Table of Contents DS2 Statistics .................................................................................................................. 5-9 24 Hour Alarm History ........................................................................................ 5-9 Performance Parameters .................................................................................... 5-10 T1/E1 Statistics............................................................................................................
Table of Contents TL1 Messages ....................................................................................................................... 9-4 TL1 Responses ............................................................................................................... 9-5 Acknowledgment Messages ................................................................................ 9-6 Output Response Messages .................................................................................
Table of Contents xii MX2810 M13 User Manual 61185001L1-1
List of Figures Figure 1-1. E1 Patch Panel ................................................................................................. 1-5 Figure 2-1. DC Power Connector ..................................................................................... 2-2 Figure 2-2. The Breakout Panel......................................................................................... 2-6 Figure 2-3. MX2810 Rear View .........................................................................................
List of Figures Figure 5-4. DS3 24-Hour Alarm History Screen............................................................. 5-4 Figure 5-5. DS3 Performance Parameters (Current 15 Minutes) ................................. 5-5 Figure 5-6. DS3 Performance Parameters (24 Hour History) ....................................... 5-6 Figure 5-7. DS3 Performance Parameters (Totals) ......................................................... 5-6 Figure 5-8. DS2 Statistics (Current 15 Minutes) ............................
List of Tables Table 2-1. Table 2-2. Table 2-3. Table 2-4. Table 2-5. Table 3-1. Table 3-2. Table 3-3. Table 7-1. Table 9-1. Table 9-2. Table 9-3. Table 9-4. DC Connector Symbol Definitions............................................................... 2-3 Power Requirements ...................................................................................... 2-3 LED Conditions for Active Cards .............................................................. 2-10 LED Conditions for Standby Cards ...........
List of Tables xvi MX2810 M13 User Manual 61185001L1-1
Chapter 1 Introduction PRODUCT OVERVIEW The MX2810 is an M13 multiplexer that consolidates T1 and E1 signals into a T3 circuit. This unit provides a cost-effective, versatile tool for combining independent T1s, E1s, or a combination of the two over the same T3 circuit. The MX2810 houses two hot-swappable controller cards which provide 1:1 redundancy for the T1 and T3 signals, as well as the T3 connections.
Chapter 1.
Chapter 1. Introduction 10BaseT local area network (LAN) port. The MX2810 supports the MIB-II standard, RFC 1213, and the ADTRAN Enterprise Specific MIB. MIB files are available from ADTRAN in the support section of the ADTRAN Web page at www.adtran.com. The term SNMP broadly refers to the message protocols used to exchange information between the network management system (NMS) and the managed devices, as well as to the structure of device management databases.
Chapter 1. Introduction TL1 Transaction Language 1 (TL1) is an ASCII based language that supports both command-response and autonomous (NE) message generation. Commonly, TL1 is used over a X.25 packet network but is completely independent of any physical layer protocols. For the MX2810, TL1 is implemented as a TELNET session running over Ethernet or an X.25 packet network. Currently, up to eight TL1 TELNET connections can be active at a time.
Chapter 1. Introduction E1 Patch Panel (P/N 1200291L5) The optional E1 patch panel (see Figure 1-1) connects to the MX2810 and provides 28 pairs of BNC connectors for E1 deployment (21 used for E1 deployment). Shipment includes two six-foot, 64-pin to 64-pin amphenol cables which allow direct cabling to the MX2810. Figure 1-1.
Chapter 1.
Chapter 2 Installation and Operation UNPACK, INSPECT, POWER UP Receiving Inspection Carefully inspect the MX2810 for any damage that might have occurred in shipment. If damage is suspected, file a claim with the carrier and contact ADTRAN Technical Support (see Warranty and Customer Service on page -vi of this manual for phone numbers). Keep the original shipping container to use for future shipment or verification of damage during shipment.
Chapter 2. Installation and Operation Power Up The MX2810 is powered using a -48V DC power source. The rear panel of the unit has screw down lugs for both A and B power feeds. The screw down terminal strip is located at the lower right side of the unit, as looking from behind. Figure 2-1 and Table 2-1 on page 2-3 illustrate the DC power connector and give definitions for the connector symbols. It is recommended that a 3 amp fuse be used in the fuse and alarm panel that feeds the MX2810.
Chapter 2. Installation and Operation Table 2-1. DC Connector Symbol Definitions Symbol Definition -48VA Negative side of DC power source (A) -48VB Negative side of DC power source (B) -48 RET Positive side of DC power source (usually ground) Frame Ground If only one power feed is available, lugs for A and B power feed must be jumpered together. Power Requirements Table 2-2 provides the power requirements and heat dissipation properties of the MX2810 chassis. Table 2-2.
Chapter 2. Installation and Operation The following UL requirements must be met during installation of the MX2810 DC version: 1. 2. 3. 4. 5. 6. 7. 8. 9. Disconnect all power sources prior to servicing (unit may use multiple power sources). Input: Minimum -48 VDC, 0.8 A Connect to a reliably grounded -48 VDC source which is electrically isolated from the AC source. The branch circuit overcurrent protection must be a fuse or circuit breaker rated minimum 48 VDC, maximum 20 A.
Chapter 2. Installation and Operation RACKMOUNT INSTALLATION The MX2810 can be mounted into a standard 19-inch or 23-inch equipment rack. Follow these steps to mount your unit into a rack: 1. Install the mounting flanges on each side of the MX2810 at one of the three available positions. Be sure to install the flanges with the screws provided. 2.
Chapter 2. Installation and Operation .
Chapter 2. Installation and Operation equipment. Descriptions for these items follow the figure. Pin assignments are given in Pinouts on page B-1.
Chapter 2. Installation and Operation Critical, Major, and Minor Alarm Connectors Connectors for critical, major, and minor alarms are located on the rear panel of the MX2810. Both C (common) and NO (normally open) contacts are provided. The alarm connectors are wire-wrap headers. The alarm functions can be enabled or disabled through the ALARM RELAYS section of the CONFIGURATION menu (see the section Alarm Relays on page 3-13).
Chapter 2. Installation and Operation FRONT PANEL The MX2810 front panel is shown in Figure 2-4. Descriptions of each part of the front panel follow. Figure 2-4. MX2810 Front Panel ACO Buttons The ACO (alarm cut off) buttons allow you to turn off an active audible alarm. The buttons are recessed, so you must use a pen or other pointed instrument to press them. Once you have used an ACO button to deactivate an alarm, it remains disabled until the condition has cleared.
Chapter 2. Installation and Operation active controller card or the controller card on standby. The following tables provide LED definitions for the active cards (see Table 2-3) and T1/E1 cards (see Table 2-4). Table 2-3.
Chapter 2. Installation and Operation Table 2-3. LED Conditions for Active Cards (Continued) PRF LED State Card Condition green solid Normal (All OK) red flash (once per event) Single/Burst CV red blinking Continuous Code Violations red solid XCV Threshold Exceeded (see XCV Threshold on page 3-4) Table 2-4.
Chapter 2. Installation and Operation Table 2-5.
Chapter 2. Installation and Operation Craft Port The CRAFT port provides connection to a VT100 EIA-232 compatible interface. Establishing Terminal Connection Only one menu session, through either Telnet or craft port, may be active at a time. When an attempt to activate a second menu session is made, the user will be asked if they want to disconnect the other menu session. If “Yes” is chosen, the user (who must have “Admin” privileges) will be required to enter a valid username and password.
Chapter 2. Installation and Operation Figure 2-5. Terminal Main Menu The letter displayed in the upper left-hand corner of the terminal menu indicates which controller card is active (A or B). Navigating Within the Menus Navigate within the MX2810 terminal menus using the following procedures: 2-14 If you want to... Press... select an item the number corresponding to your choice, and then press the Enter key scroll left and right within the same screen the left and right arrow keys.
Chapter 2. Installation and Operation The MX2810 MAIN menu consists of the following sections: Status Provides information on the current state of the DS3, power supplies, system, DS2s, and T1/E1 lines. See the chapter Status on page 4-1 for more detailed information. Statistics Provides detailed statistical information (both current and historical) for the DS3, DS2s, T1/E1 lines, and Protection Switch Statistics. See the chapter Statistics on page 5-1 for more detailed information.
Chapter 2.
Chapter 3 Configuration To configure the MX2810, use a 10BaseT ethernet connection or a VT100 terminal. Figure 3-1 shows the main configuration terminal menu, and Figure 3-2 on page 3-2 shows the CONFIGURATION menu tree. Figure 3-1.
Chapter 3. Configuration 1. Framing DS3 Configuration 1. Network Interface 1. A* 6. Active Controller Protection Configuration 2. B 7. Max Switch Threshold (3)* Miscellaneous 2. Short (0-225 ft.)* 2. Line Length 1. Disabled 3. Auto Enable* T1 # 1-28 2. T1/E1 Interface 1. AMI 4. Loopback Detection 5. Circuit Protection 2. IE-3 3. 5 min. 3. IE-4 2. G.747 (3 x E1) 4. 10 min. 4. IE-5 5. 15 min. 5. IE-6 1. 0-133 ft.* 6. 30 min. 2. 133-266 ft. 7. 45 min. 8. 1 hour* 4. 399-533 ft.
Chapter 3. Configuration NETWORK INTERFACE Select NETWORK INTERFACE to access the network configuration parameters (see Figure 3-3). Configure the MX2810 network settings to match the DS3 signal received from the service provider. Figure 3-3. Network Configuration Menu DS3 Configuration Use the DS3 CONFIGURATION selections to configure the DS3 network settings to match your application.
Chapter 3. Configuration Remote Loopbacks Select FEAC/C-BIT to allow the MX2810 to respond to remote loopback requests received over either the DS3 Far End Alarm and Control (FEAC) channel and/or DS2-level C bits. This mode is valid in both C-BIT or M13 framing formats. Select FEAC to allow the MX2810 to respond only to remote loopback requests received over the DS3 FEAC channel. This mode is only valid when using C-BIT framing. In this mode, DS2 C bit loopbacks will be ignored.
Chapter 3. Configuration Protection Configuration The MX2810 houses two controller cards for 1:1 protection against hardware failure. The selections in this menu allow you to customize the unit’s protection setup: Active Controller This field displays A or B, indicating the active controller card. This setting can be used to force the controller cards to switch. For example, if controller card A is active and you select B, a switchover occurs immediately. Max.
Chapter 3. Configuration The fourth T1/E1 port of the selected group is not available in this mode. Any combination of M12 (4XT1) and G.747 (3XE1) is allowed. T1/E1 INTERFACE The T1/E1 INTERFACE menu (shown in Figure 3-4 on page 3-6) allows you to activate/deactivate individual T1s and E1s and to set their line coding, length, loopback detection, circuit protection, and line ID string. The T1/E1 code violation threshold is also configured through this menu.
Chapter 3. Configuration Figure 3-5. T1/E1 State Menu Set Multiple Use SET MULTIPLE (see Figure 3-6 on page 3-7) to enable or disable a contiguous group or all of the T1/E1s at one time. To enable or disable all T1/E1s, set FIRST to 1 and LAST to 28. Enter APPLY SETTINGS before leaving the menu. To enable or disable only some of the T1/E1s, set FIRST and LAST to correspond to the lines you want to enable or disable. Enter APPLY SETTINGS.
Chapter 3. Configuration T1/E1 Line Coding Set the line code for each individual T1/E1 interface to match the connected device (see Figure 3-7). The choices available for T1 are AMI and B8ZS. The choices available for E1 are AMI and HDB3. Select SET MULTIPLE to set a contiguous group or all of the T1s (or E1s) to the same value at the same time. See Set Multiple on page 3-7 for a description of the SET MULTIPLE option, entering the line code for each line. Figure 3-7.
Chapter 3. Configuration Figure 3-8. T1/E1 Line Length Menu T1/E1 Loopback Detection Choose which T1/E1 lines will respond to CSU or NIU loopback requests coming from the network (see Figure 3-9 on page 3-9). Set to CSU or NIU if you want the T1/E1 to respond to that type of request. Set to DISABLE if you want the T1/E1 to ignore the request. Select SET MULTIPLE to set a contiguous group or all of the T1/E1s to the same value at the same time.
Chapter 3. Configuration T1/E1 Circuit Protection T1/E1 Circuit Protection determines which circuit will be allowed to initiate a protection switch if a failure in the circuitry for that channel is detected (see Figure 3-10 on page 3-10). If a T1/E1 is set to DISABLED, then the failure of the circuitry of that one channel will not cause a protection switch. If set to ENABLED, then the failure of a channel could cause a protection switch to occur (depending on the PROTECTION THRESHOLD setting in this menu).
Chapter 3. Configuration Figure 3-11. Line Identification Menu XCV Threshold Set a limit on code violations (CVs) accepted by the unit over an individual T1/E1 line before it switches controller cards. If set to DISABLED, code violations will not cause the unit to switch controller cards. The threshold limits are described in the following chart: Setting 61185001L1-1 The unit switches controller cards if... 1E-3 more than one out of every 1,000 bits received on a T1/E1 line contains a code violation.
Chapter 3. Configuration SYSTEM MANAGEMENT Configure the MX2810 for management through SNMP, TELNET, or a VT100 interface (see Figure 3-12). Embedded SNMP and TELNET are available via a 10BaseT ethernet interface. This menu also includes options used to customize your unit’s alarm and trap generation, security setup, and equipment identification. Figure 3-12.
Chapter 3. Configuration Subnet Mask Enter the subnet mask of the MX2810. This address is available from your network administrator. Alarm Relays Alarm Relay Configuration Enables audible and visible alarms for specific error conditions (see Figure 3-13). The following charts describe the alarm conditions found in this menu. Conditions marked in the charts with an asterisk (*) sound the critical alarm when enabled. All other conditions sound the non-critical alarm. Figure 3-13.
Chapter 3. Configuration DS3 Alarms Alarm Description RAI (Major) The unit is receiving an RAI (yellow) alarm from the network. This alarm is a signal sent back toward the source of a failed transmit circuit. The X-bits (X1 and X2) are set to zero. LOS (Critical) The unit has lost the network Rx signal. LOF (Critical) The unit detects a framing loss from the network. IDLE (Minor) The unit detects an idle sequence from the network.
Chapter 3. Configuration T1/E1 Alarms T1/E1 alarms are cleared when the T1/E1 is disabled or set to AUTO ENABLE after receiving an alarm. Alarm Description LOS (Major) The unit has lost the receive signal on a T1/E1. Power Supply Alarms Alarm Description Malfunction (Minor) Power supply card is no longer working. The unit has switched to the backup power supply or battery backup. Power Low (Minor) Power supply’s output level is abnormally low.
Chapter 3. Configuration SNMP Management Options Trap IP Addresses Enter up to five IP addresses of SNMP managers to which the MX2810 sends traps. Trap Generation Use this menu (see Figure 3-14) to designate which error conditions will cause the unit to send trap messages. Figure 3-14. Trap Generation Menu Controller Traps Trap If enabled, the unit issues a trap when...
Chapter 3. Configuration Power Supply Alarm Traps 61185001L1-1 Trap If enabled, the unit issues a trap when...
Chapter 3. Configuration DS3 Alarm Traps (Near-End Active and Standby Cards) 3-18 Trap If enabled, the unit issues a trap when... LOS the controller card has lost the network Rx signal OOF the controller card detects a framing loss from the network AIS the controller card is receiving an AIS (blue) alarm condition from the network. AIS alarms occur when consecutive 1010s are received in the information bits.
Chapter 3. Configuration DS3 Alarm Traps (Far-End Active Cards) Trap If enabled, the unit issues a trap when... LOS the remote unit’s active controller card has lost the network Rx signal OOF the remote unit’s active controller card detects a framing loss from the network AIS the remote unit’s active controller card is receiving an AIS (blue) alarm condition from the network IDLE the remote unit’s active controller card detects an idle sequence from the network.
Chapter 3. Configuration T1/E1 Alarm Traps Trap If enabled, the unit issues a trap when...
Chapter 3. Configuration Read Community Name Enter the authentication strings used for SNMP management. Match the MX2810 to the SNMP manager for read privileges. Write Community Name Enter the authentication strings used for SNMP management. Match the MX2810 to the SNMP manager for write privileges. Trap Community Name Enter the identification string used for trap management. This string accompanies all traps transmitted by the MX2810. System Security User Account Management Enter up to 15 user accounts.
Chapter 3. Configuration Admin The user may view and/or alter all menu items. Only a user with an Admin user account may alter the User Account Management information. User accounts provide access to the MX2810 for console interface sessions and TL1 sessions.. The LOAD DEFAULT SETTINGS menu item that is located on the Configuration/Utilities menu will reset the User Account Management table back to the factory default account username/password/admin. Console Menu Item: Table 3-1.
Chapter 3. Configuration Table 3-1.
Chapter 3. Configuration Table 3-1.
Chapter 3. Configuration Terminal Time Out Set the amount of time the terminal or TELNET session remains inactive before automatically closing the session, requiring the user to log in again. The options include DISABLED, 1 MIN., 5 MIN., 15 MIN., 60 MIN., or 1 DAY. IP Security Enable or disable the IP SECURITY option. If ENABLED, the unit accepts management commands and TELNET sessions from the IP addresses entered into the IP HOSTS fields.
Chapter 3. Configuration Figure 3-15. Equipment Identification Menu Unit ID Provides a user-configurable text string for the name of the MX2810. This name can help you distinguish between different installations. You can enter up to 32 alpha-numeric characters in this field, including spaces and special characters (such as an underbar). This information is locally stored and displayed in the upper right-hand corner of the MX2810 terminal screens.
Chapter 3. Configuration Host IP Address Specifies the IP address of the external server that is running the Syslog host daemon. Severity Level Specifies the lowest level of severity that causes messages to be logged to the Syslog server. The levels are listed in Table 3-2, in order of decreasing severity. Any message at or above a selected severity level will be logged if a transmission is enabled. . Table 3-2. Syslog Severity Levels Level Description Emergency The system is unusable.
Chapter 3. Configuration Autoprogram Cards Enable this function to allow the controller cards to automatically update software and ensure that both controller cards are running the same version of code. When the software of both controller cards are not the same, the card running the older software will automatically be updated with the newer version. If the option is disabled, the controller cards will continue to run existing software.
Chapter 3. Configuration UTILITIES The UTILITIES menu (see Figure 3-16) allows you to view MX2810 system information for both controller cards (including self-test results), revert to default configuration settings, flash-load a new version of software, transfer configuration information to and from a TFTP server, and reset the system. Possible results for the self-test are listed in the chart following Figure 3-16. Figure 3-16. System Utilities Menu Table 3-3.
Chapter 3. Configuration If the self test results are... Then... CONFIGURATION CORRUPT select SAVE CONFIGURATION from the main CONFIGURATION menu. If condition persists, contact ADTRAN Technical Support. Loading Default Settings Loading the default settings will disable all DSX ports. The USER ACCOUNT MANAGEMENT table is also reset to default. Select LOAD DEFAULT SETTINGS from the UTILITIES menu.
Chapter 3. Configuration Update Via XMODEM Updating the FLASH Software via XMODEM requires that a VT100 terminal menu session be active through the unit's craft port. To update the software via XMODEM, follow the steps below: 1. 2. 3. 4. 5. 6. From the MX2810 Main Menu, select CONFIGURATION, select UTILITIES, select UPDATE FLASH SOFTWARE, select UPDATE VIA XMODEM. Once it has been determined where the new binary file is located, select START to begin the transfer.
Chapter 3. Configuration select either IMMEDIATE RESET to immediately reset the system or SCHEDULE RESET TIME to set a time for the system to reset. Once the system has been reset, the new software will be running. . This function is available only when updating the software through the CRAFT port. Update via TFTP Server Updating the FLASH Software via TFTP Server requires that the IP address and file name of file to be downloaded is known. To update the software via TFTP, follow the steps below: 1.
Chapter 3. Configuration The stand-by card must remain in place until the upload process is complete and the ACT LED is no longer solid amber. Removing the stand-by card during the uploading process will corrupt the software. 5. The system must be manually reset after downloading new software for the active controller card to begin running the new code.
Chapter 3. Configuration Saving to a TFTP Server To save current configuration information to a TFTP server, follow the steps listed below. 1. Set the SERVER IP ADDRESS field to the IP address of the machine running the TFTP server program. If you are using the ADTRAN TFTP server, the IP address displays in the SERVER IP ADDRESS field. For other TFTP servers, please refer to the appropriate documentation. 2. Change the TFTP Server Filename to a unique filename.
Chapter 3. Configuration Configuration changes will not be implemented until all Telnet sessions are closed. Loading a new configuration may disrupt data traffic. 3. Select LOAD AND USE CONFIG. Resetting the System The system must be manually reset after downloading new software. When the unit has successfully loaded and programmed the new software into its FLASH memory, it will begin uploading the code to the stand-by controller.
Chapter 3.
Chapter 4 Status View MX2810 status information by selecting 1-STATUS from the MAIN menu (see Figure 4-1). The information for the DS3, DS2s, T1/E1 lines, power supplies, and controller cards is provided. Figure 4-1. Status Menu DS3 STATE Displays the current state of the DS3. The following sections describe the DS3 status fields in detail. Rx Framing Shows the network framing type (C-bit or M13).
Chapter 4. Status State Displays the current condition of the network. Possible conditions are listed in the following chart: Condition Description Normal The MX2810 is ready to pass data. Alarm The unit is currently receiving an alarm indication. Alarm types are discussed in the following section, Alarm. In Test The unit is currently in test mode. See Loopbacks on page 6-1 for information on the test type. Alarm This field displays the current alarm condition of the MX2810.
Chapter 4. Status Condition Description Excessive CV The unit is receiving excessive code violations from the network, exceeding the threshold set by the user (see XCV Threshold on page 3-4). TLOS (Tx loss of signal) The transmitter has failed. Idle The unit detects an idle sequence from the network. Remote This field indicates the current state of the remote MX2810.
Chapter 4. Status Condition Description DS3 Eqpt Fail (SA) The far-end unit or network is reporting a serviceaffecting DS3 equipment failure. DS3 Eqpt Fail (NSA) The far-end unit or network is reporting a nonservice-affecting DS3 equipment failure. Common Eqpt The far-end unit or network is reporting a nonFail (NSA) service-affecting common equipment failure. Multiple DS1 LOS The far-end unit is experiencing a loss of signal on multiple DS1s.
Chapter 4. Status SYSTEM STATE These fields display information regarding the two controller cards. The following sections describe the system state fields in detail. Alarm This field displays what type (if any) of system alarm is currently recognized by the unit. The condition is displayed until it clears up, with the exception of the SWITCHED condition (which is cleared manually) and the EXCESSIVE SWITCHES (which is cleared when PROTECTION SWITCH alarms counts are cleared, see page 5-12) .
Chapter 4. Status Card A/Card B These fields display the current state of the two controller cards. Possible states for the controller cards are listed in the following chart: Condition Description Not Installed No controller card is installed in this slot. Stand By The controller card is ready to pass data, but is currently acting as a backup card. Active The controller card is acting as the primary card. Failure The controller card has failed and needs to be replaced.
Chapter 4. Status Card Comm This field displays the current state of the communication link between the two controller cards. OK indicates that the cards are communicating; FAILURE indicates that the cards are not able to communicate with each other. If there is only one card installed, NON-REDUNDANT is displayed. DS2 STATE This field displays the current state of each of the seven DS2s. Possible states are listed in the following chart: Condition Description OK The DS2 is not receiving alarms.
Chapter 4. Status Condition Description TST The T1/E1 is currently in test mode. HOT The T1/E1 transceiver temperature is too high. LAIS The T1 is receiving all ones from the DSX-1 interface. (loop side AIS) CAIS (carrier side AIS) The T1 is receiving all ones from the DS3 side of the network. A DS2 can be divided into either three E1s or four T1s. Therefore, when dealing with an E1 configuration, some of the fields in the T1/E1 STATE menus do not apply (and display nothing).
Chapter 5 Statistics VIEWING STATISTICAL INFORMATION Select 2-STATISTICS from the MAIN menu to access STATISTICS menus (see Figure 5-1). Alarm information and performance parameters are available for both the near and far ends of the network. Information is also given for the individual DS2s and T1/E1 lines.
Chapter 5. Statistics DS3 Statistics This menu provides submenus for alarm history and performance parameters (see Figure 5-2). Figure 5-2. DS3 Statistics Menu 24 Hour Alarm History The MX2810 keeps track of alarms for both the near and far ends of the network. View alarm history information in one of the three time period selections, or view a cumulative alarm count. Information in these fields is for the given time period (if any) since the last reset.
Chapter 5. Statistics The following alarm counts are provided in this menu: Condition Description LOS Number of times the unit has lost the receive signal. LOF Number of times the unit has detected a loss of framing from the network. AIS Number of times the unit has received an AIS (blue) alarm condition from the network. AIS alarms occur when consecutive 1010s are received in the information bits.
Chapter 5. Statistics Figure 5-3. DS3 Current Alarm Count Screen Figure 5-4. DS3 24-Hour Alarm History Screen When a > or < symbol appears in an upper corner of the screen, you can use the arrow keys on your keyboard to scroll right or left to view additional information. See the upper right-hand corner of Figure 5-4. Performance Parameters View performance parameter information for the network in one of the three time period selections.
Chapter 5. Statistics 24-hour history statistics screen, use the left and right arrow keys to scroll through all 96 15-minute intervals. See Figure 5-5, Figure 5-6, and Figure 5-7 on page 5-6 for examples of the performance parameter screens. Descriptions of the fields in each screen follows. Figure 5-5.
Chapter 5. Statistics Figure 5-6. DS3 Performance Parameters (24 Hour History) Figure 5-7. DS3 Performance Parameters (Totals) Interval starting at: Time that the 15-minute interval began. This field is only displayed in the 24-hour history screen, which gives information for the previous 24 hours divided into 15-minute intervals (shown in Figure 5-6 on page 5-6). Coding Violations - Line (CV-L) Number of BPVs (bipolar violations) and EXZs (excessive zeros) that have occurred.
Chapter 5. Statistics Errored Seconds-Line (ES-L) Number of seconds in which one or more CVs or one or more LOS (loss of signal) defects occurred. Severely Errored Seconds-Line (SES-L) Number of seconds with 44 or more LCVs or one or more LOS (loss of signal) defects occurred. SEF/AIS Seconds (SAS-P) Number of seconds with one or more out-of-frame defects or a detected incoming AIS. Coding Violations - P-Bit (CVP-P) Number of coding violation (CV) error events that have occurred.
Chapter 5. Statistics Severely Errored Seconds - C-Bit (SESCP-P) Number of seconds with 44 or more CCVs, one or more out-of-frame defects, or a detected incoming AIS. This count is not incremented when UASs are counted. Unavailable Seconds - C-Bit (UASCP-P) Time in seconds for which the DS3 path is unavailable. The DS3 path becomes unavailable at the onset of 10 contiguous SESCP-Ps. F-Bit Errors (FBE) Number of times an F-bit framing error has occurred.
Chapter 5. Statistics DS2 Statistics 24 Hour Alarm History The MX2810 keeps track of RAI, OOF, and AIS alarms for each of the seven DS2s. View alarm history information in one of the three time period selections, or view a cumulative alarm count. Information in these fields is for the given time period (if any) since the last reset. The cumulative alarm count continues indefinitely until CLEAR ALL DS2 ALARM COUNTS is selected.
Chapter 5. Statistics Performance Parameters The performance parameters screen displays a count of parity bit errors and frame bit errors for the seven DS2s. View this information in any of the three time period selections. Information in these fields is for the given time period since the last reset.
Chapter 5. Statistics T1/E1 Statistics The MX2810 keeps track of LOSS OF SIGNAL ALARMS, LINE CODING VIOLATIONS, AIS LOOP ALARMS, AIS CARRIER ALARMS, ERRORED SECONDS, and SEVERELY ERRORED SECONDS for each of the T1s and E1s (see Figure 5-12). View this information in one of the three time period selections, or view a cumulative alarm count. Information in these fields is for the given time period (if any) since the last reset.
Chapter 5. Statistics PROTECTION SWITCH STATISTICS This menu provides statistics regarding protection switches. The number of protection switches that occur within the particular time period will be listed. (See Figure 5-13.) Figure 5-13. Protection Switch Statistics Menu Performance Parameters View performance parameter information for the network in one of the three time period selections. Information in these fields is for the given time period since the last reset.
Chapter 5. Statistics system configuration are saved to non-volatile memory. Both the alarm log and system configuration may be saved manually when the user executes the SAVE CONFIGURATION & ALARM LOG menu function in the CONFIGURATION menu. Each time the system powers up, the alarm log is retrieved from non-volatile memory. A RESET ALARM LOG function is accessible from the alarm log menu. This option clears the alarm log (See Figure 5-14.) Figure 5-14.
Chapter 5.
Chapter 6 Loopbacks The LOOPBACK menu allows you to initiate loopback tests from the MX2810. Figure 6-1 shows the main LOOPBACK menu. From this menu, select T1/E1, DS3, or DS2 LOOPBACKS. Once this selection is made, a second menu appears displaying the types of tests available. Descriptions and testing diagrams of the loopback tests are provided in the following portions of this chapter: T1/E1 Loopbacks on page 6-2 DS3 Loopbacks on page 6-7 DS2 Loopbacks on page 6-9 Figure 6-1.
Chapter 6. Loopbacks T1/E1 LOOPBACKS After you select the number that corresponds with the line you want to test, the menu in Figure 6-2 appears. The sections following the figure provide descriptions and illustrations of the testing options. Select 1-DATA MODE to end a test in progress. Figure 6-2. T1/E1 Loopback Menu Tributary A TRIBUTARY loopback loops the selected T1/E1 back to the network (DS3). The T1/E1 is de-multiplexed through the M23 and M12/G.
Chapter 6. Loopbacks CODEC F R A M E R M23 MUX/DMUX T1/E1 LIU (1 of 28) (1 of 7) CODEC (28 of 28) .... D S 3 (1 of 28) M12/G.747 MUX/DMUX .... DSX-3 LIU F DR A SM 2E R T1/E1 LIU (28 of 28) Figure 6-3. Tributary Loopback Test Analog Network An ANALOG NETWORK loopback test loops the selected T1/E1 back to the network (DS3).
Chapter 6. Loopbacks CODEC F R A M E R M23 MUX/DMUX T1/E1 LIU (1 of 28) (1 of 7) CODEC (28 of 28) .... D S 3 (1 of 28) M12/G.747 MUX/DMUX .... DSX-3 LIU F DR A SM 2E R T1/E1 LIU (28 of 28) Figure 6-5. Digital Line/Network Loopback Codec Line/Net A CODEC LINE/NET loopback performs a loopback of the selected T1/E1 in both the network and local loop directions. Both loopbacks occur at the T1/E1 codec.
Chapter 6. Loopbacks CSU Loopback A CSU LOOPBACK enables the MX2810 to generate a CSU loop up pattern (001001…) toward the T1 CSU attached to the selected T1 line for six seconds. After six seconds have elapsed, the pattern will cease and incoming network traffic will be passed through to the CSU device. If the CSU device responded to the CSU loop up pattern, it will return all data back toward the network. A loop down pattern (0000100001….
Chapter 6. Loopbacks Figure 6-7. Loopback Menu with BERT Selected Line BERT A LINE BERT enables the MX2810 to perform a “head-to-head” BERT test toward the T1 line/loop. Selecting LINE BERT will replace all incoming network traffic for the selected T1 with an unframed 511 pattern toward the T1 line/loopU. When LINE BERT is selected, additional menu items will appear to show the state of pattern synchronization, cumulative error count, and a clear error count option.
Chapter 6. Loopbacks DS3 LOOPBACKS After you select DS3 LOOPBACK, the menu in Figure 6-8 appears. The sections following the figure provide descriptions and illustrations of the testing options. Select 1=DATA MODE to end a test in progress. Figure 6-8. DS3 Loopback Menu Line Loopback LINE LOOPBACK performs a loop of the DS3 back to the network.
Chapter 6. Loopbacks CODEC F R A M E R M23 MUX/DMUX T1/E1 LIU (1 of 28) (1 of 7) CODEC (28 of 28) .... D S 3 (1 of 28) M12/G.747 MUX/DMUX .... DSX-3 LIU F DR A SM 2E R T1/E1 LIU (28 of 28) Figure 6-9. Line Loopback Test Digital Loopback A DIGITAL LOOPBACK loops the entire DS3 back to the local loop side. The end effect of this test is a loopback of all T1/E1s after being fully multiplexed and de-multiplexed to and from a DS3.
Chapter 6. Loopbacks CODEC T1/E1 LIU (1 of 28) (1 of 7) CODEC (28 of 28) .... M23 MUX/DMUX (1 of 28) M12/G.747 MUX/DMUX .... DSX-3 LIU F D R A S M 3 E R F DR A SM 2E R T1/E1 LIU (28 of 28) Figure 6-11. Network Loopback Test Remote Loopback A REMOTE LOOPBACK performs a loopback on the far-end M13 multiplexer. The form of this loopback code sent to the far-end will depend on the framing mode being used. When in C-Bit parity mode, the MX2810 will send loopback commands over the FEAC channel.
Chapter 6. Loopbacks Figure 6-12. DS2 Loopback Menu DS2 Network A DS2 NETWORK loopback test loops the selected DS2 back to the network (DS3) prior to being passed through the M12/G.747 demultiplexer. All T1/E1s attached to that DS2 will receive data normally, but all data inserted into the T1/E1s attached to the selected DS2 will be ignored and replaced by the incoming DS2 network data. This test is illustrated in Figure 6-13.
Chapter 7 Circuit Redundancy The MX2810 provides backup measures of protection for circuit failure. The following sections describe the possible modes of operation: • • Non-Redundant Mode, which offers no backup protection, is described on page 7-2. Circuit Failure Recovery Mode, which offers backup protection in the event of controller card failure, is described on page 7-3. The descriptions given include illustrations and suggested configuration settings.
Chapter 7. Circuit Redundancy NON-REDUNDANT MODE In Non-Redundant Mode, the MX2810 houses only one controller card. There is no failure protection. In the event of a failure, an alarm is initiated and the front panel LEDs reflect the condition. See Figure 7-1 for an illustration. MX2810 Figure 7-1.
Chapter 7. Circuit Redundancy CIRCUIT FAILURE RECOVERY MODE In Circuit Failure Recovery Mode, two controller cards are installed (see Figure 7-2). In this mode, the MX2810 can continue operating in the event of a controller card failure. When both cards are healthy, the primary card actively processes data while the secondary card stands by ready to take over if the first fails. The secondary card continuously monitors the line and remains framed to the incoming signal.
Chapter 7. Circuit Redundancy Table 7-1. Configuration Requirements for Circuit Recovery Selection Path Recommended Setting Config > Network Interface > XCV Threshold 1E-3 (see the following note) Config > Network Interface > Max. Switch Threshold 3 Config > Network Interface > Min. Switching Period 10 seconds Config > T1/E1 Interface > T1/E1 Circuit Protection Enable all or select the T1/E1s that redundant switching should occur on.
Chapter 8 Power Loss Recovery The MX2810 provides backup measures of protection for both power supply and power source failure. The following sections describe the possible modes of operation: • • • • 61185001L1-1 Non-Redundant Power Mode, which offers no backup protection, is described on page 8-2. Power Supply Recovery Mode, which offers backup protection in the event of power supply card failure, is described on page 8-3.
Chapter 8. Power Loss Recovery NON-REDUNDANT POWER MODE In Non-Redundant Power Mode, the MX2810 houses only one power supply card and only one power source is available. There is no power failure protection. If a power supply card fails, then the unit is down until the card is repaired or replaced. See Figure 8-1 for an illustration. MX2810 Figure 8-1. Non-Redundant Power Mode Power supplies are hot-swappable.
Chapter 8. Power Loss Recovery POWER SUPPLY RECOVERY MODE In Power Supply Recovery Mode, two power supply cards are installed and connected to a single power source (see Figure 8-2). In this mode, the MX2810 can continue operation in the event of a power supply failure, without interrupting service. The power supplies are load sharing, so either power supply can provide power for the entire unit. MX2810 Figure 8-2.
Chapter 8. Power Loss Recovery POWER SUPPLY AND SOURCE RECOVERY MODE In this mode, two power supply cards are installed and are connected to two individual power sources. The MX2810 handles any combination of power source or power supply failure. Much like the backup design for the controller cards, the MX2810 is able to internally re-route the power source if a power supply card and the opposite power source fail.
Chapter 8. Power Loss Recovery BATTERY BACKUP MODE With the installation of the ADTRAN Power Supply/Battery Charger (PS/BC) and backup battery pack, the MX2810 is able to continue operation without service interruption in the event of a power outage. This PS/BC (P/N 4175043L10) provides -48 VDC to the MX2810. It receives 115 VAC through a standard plug and wall socket. The PS/BC maintains the battery at peak charge (-48 V) at all times.
Chapter 8.
Chapter 9 Transaction Language 1 (TL1) INTRODUCTION Transaction Language 1 (TL1) is a BELLCORE standard used in the input and output messages that pass between Operations Systems (OS) and Network Elements (NE) in telecommunication networks. It was developed to standardize equipment surveillance and memory administration, and to test with a common format. This release of TL1 primarily supports the interactive and autonomous retrieval of system events as part of a valid TL1 session.
Chapter 9. Transaction Language 1 (TL1) • • • • • • • • • 1-way in or 2-way operation Up to four SVCs Up to 64 Kbps (synchronous) Packet size: 128 Bytes Packet window: 2 n2 retry limit: 3 T1 ACK timer: 20 seconds T3 time out: 3 seconds k window size: 2 Table 9-1. X.
Chapter 9. Transaction Language 1 (TL1) An account may be setup via the VT100 menus (Configuration/ System Management/System Security/User Account Management.) An account includes a username, password, and privileges. The privileges include ADMIN, GUEST, INTERFACE, TEST, and DISABLED (see Table 9-2). ADMIN privileges allow the user to use all supported commands.
Chapter 9. Transaction Language 1 (TL1) Table 9-2. TL1 Account Privileges (continued) TL1 Command Guest Interface Test Admin RTRV-HDR X X X X RTRV-rr X X X X RTRV-SYS X X X X RTRV-USER-SECU X RTRV-VER X X SET-DAT X X X “x” denotes item is supported by privilege level To bring up a TL1 TELNET connection (up to eight may be active,) a TELNET client is used to request a connection on (TCP) port 3116.
Chapter 9. Transaction Language 1 (TL1) is the Correlation Tag, a 1 to 6 character alphanumeric identifier that is echoed in the response message for the command. is unused in this application and should be empty. is a block that is used in many of the setup TL1 commands. There may be more than one parameter block. If there is, they will be separated by a comma. is a block that is used in TL1 Edit and RTRV commands.
Chapter 9. Transaction Language 1 (TL1) Acknowledgment Messages Acknowledgment messages are brief output messages generated in response to received TL1 commands. The MX2810 currently supports two types of acknowledgment messages: In Progress (IP) and All Right (OK). In Progress The IP acknowledgment message is usually generated as an interim response message to indicate that a message has been received and that the command is being executed.
Chapter 9. Transaction Language 1 (TL1) is the date in the form YY-MM-DD,
Chapter 9. Transaction Language 1 (TL1) The MX2810 specifically uses “quoted line(s)” in the response message of successfully executed RTRV-ALM commands. The quoted line format is as follows: :,,,,,… The NTFCNCDE field will contain one of the following values: • MN - Minor • MJ - Major • CR - Critical Refer to the condition types listed in Table 9-4 on page 9-19 (MX2810 Alarm Events) for possible MX2810 CONDTYPE codes.
Chapter 9. Transaction Language 1 (TL1) Possible values for the ALARM CODE field include: • *C - Critical Alarm • ** - Major Alarm • * - Minor Alarm • A - Non-alarm • NULL - (blank) The parameter is the Autonomously Generated Correlation Tag (ATAG). It is a decimal number assigned by the NE. It must be sequential and must be included in all autonomous messages.
Chapter 9. Transaction Language 1 (TL1) the time in HH-MM-SS format, and whether the alarm is NEND of FEND ("Near End" or "Far End"). An example of an autonomous message event is: Unit 1 01-10-09 16:21:10 A 22 REPT EVT EQPT "405:PROTNA,TC,10-09,16-21-10,NEND,,,," In this example, "Unit 1" is the unit ID or that was set in the menus. "01-10-09 16:21:10" is the date and time stamp. The "A" indicates this is a non-alarm message. "22" is the that is automatically generated.
Chapter 9. Transaction Language 1 (TL1) For possible CONDTYPE codes for both REPT-ALM and REPT-EVT quoted lines, refer to the condition types listed in Table 9-4 on page 9-19 and Table 9-5 on page 9-22, respectively. See the section TL1 Autonomous Messages on page 9-17 for a list of autonomous messages currently supported by the MX2810.
Chapter 9. Transaction Language 1 (TL1) Table 9-3. TL1 Commands (Continued) MOD2 Specifies what entity type to allow: EQPT... General Equipment Unit rr .......... Facility or Circuit (i.e. T1, T2, T3) ALL ...... All entity types TID* Target ID CTAG* Transaction Number (integer) PARAM1* Specifies what notification code to allow: MN ....... minor MJ........ major CR ....... critical ALL........
Chapter 9. Transaction Language 1 (TL1) Table 9-3. TL1 Commands (Continued) TID* Target ID AID Username CTAG* Transaction Number (integer) PARAM1 User’s password PARAM3 User’s privileges: 0 .......... disabled 1 .......... guest 2 .......... interface 4 .......... test 8 ..........
Chapter 9. Transaction Language 1 (TL1) Table 9-3.
Chapter 9. Transaction Language 1 (TL1) Table 9-3. TL1 Commands (Continued) AID* Identifies the component to which the desired alarm pertains. Identifiers are integers and are dependent on the entity specified in "MOD2" as follows: for EQPT: 401 ....Generic 402 ....Control Card A 403 ....Control Card B 404 ....Power Supply A 405 ....Power Supply B ALL....all EQPT identifiers (default selection) for T1: 101 ....DS1#1 102 ....DS1#2 . 128 ....DS1#28 ALL....all DS1 circuits (default selection) for T2: 201 ...
Chapter 9. Transaction Language 1 (TL1) Table 9-3. TL1 Commands (Continued) RTRV-COND-{EQPT|rr|ALL}; Description Retrieves the requested alarms and conditions MOD2 Specifies what entity type to query: EQPT... General Equipment Unit rr .......... Facility or Circuit (i.e. T1, VT1, STS1) ALL ...... All entity types TID* Target ID AID* Identifies the component to which the desired alarm pertains. Identifiers are integers and are dependent on the entity specified in "MOD2" as follows: for EQPT: 401 ...
Chapter 9. Transaction Language 1 (TL1) Table 9-3. TL1 Commands (Continued) CTAG* Transaction Number (integer) PARAM1* Specifies what notification code to query: SC ....... standing condition SET-DAT:::::,; Description Sets the date and time PARAM1 Date in YY-MM-DD format PARAM2 Time in HH-MM-SS format * An asterisk indicates optional command blocks. TL1 Autonomous Messages Autonomous messages provide a mechanism for real time reporting of system events.
Chapter 9. Transaction Language 1 (TL1) An example of this command that would enable "all" autonomous messages is: ALW-MSG-ALL; The response to this command would be: Unit 1 01-10-15 10:34:21 M 0 COMPLD ; Where "Unit 1" is the defined in the menus, "01-10-15 10:34:21" is the date and time, "M 0 COMPLD" is the ctag and completion code.
Chapter 9. Transaction Language 1 (TL1) ; Where "Unit 1" is the defined in the menus, "01-10-15 10:34:21" is the date and time, "M 0 COMPLD" is the ctag and completion code. Similarly, to disable just the T1 autonomous messages the following command could be used: INH-MSG-T1; REPT-ALM indicates an alarm event. Table 9-4 lists possible autonomous messages for alarm events. Table 9-4.
Chapter 9. Transaction Language 1 (TL1) Table 9-4.
Chapter 9. Transaction Language 1 (TL1) Table 9-4.
Chapter 9. Transaction Language 1 (TL1) REPT-EVT indicates an informational event. Table 9-5 lists possible autonomous messages for informational events. Table 9-5.
Chapter 9. Transaction Language 1 (TL1) TL1 ERROR CODES When the MX2810 denies a received TL1 command, the Output Response message has an associated 4-letter error code indicating the reason for denial. Table 9-6 lists possible error codes. Table 9-6.
Chapter 9. Transaction Language 1 (TL1) • • is one of the entries from the following data dictionaries is one of the enumerated types in the data dictionaries, an integer, or Y/N depending on the TYPE.. is an optional parameter. The placemarker (:) must remain in place. The default is 0.
Chapter 9.
Chapter 9. Transaction Language 1 (TL1) Table 9-7. TL1 Editing Data Dictionary for DS3 Keyword ACTIVECONTROLLER CARDSWRLY DIAGDS3 Type ENUM Y/N ENUM DS3AISRLY Y/N DS3CVTHRS ENUM Domain Description One of the following: • A • B Selects which controller card is active. Y or [N] Identifies status of System Protection Switch alarm relay.
Chapter 9. Transaction Language 1 (TL1) Table 9-7. TL1 Editing Data Dictionary for DS3 (Continued) Keyword Type Domain Description DS3MAXNUMSW INT 0, 1, 2, ..., N Maximum number of times per hour the unit is allowed to switch between controller cards. If number is exceeded the unit will issue a trap. DS3MINSWPERIOD INT 0, 1, 2, ..., N Number of seconds that must pass after a protection switch before another protection switch will be allowed.
Chapter 9. Transaction Language 1 (TL1) Table 9-7. TL1 Editing Data Dictionary for DS3 (Continued) Keyword TMG Type ENUM Domain One of the following: • LPD • INT Description Identifies timing supply for the DS3. LPD - loop timed. • LPD - loop timed • INT - internal timing source The following data dictionary (Table 9-8) contains entries that are used to edit or retrieve options for the DS2 portion of the MX2810.
Chapter 9. Transaction Language 1 (TL1) Table 9-8. TL1 Editing Data Dictionary for DS2 Keyword Type DIAGDS2TESTSTATE DS2AISRLY DS2CFGMODE ENUM Y/N ENUM Domain Description One of the following: • DATAMODE • NETWORK Identifies DS2 Diagnostic Loopback. NETWORK selects the available loopback. DATAMODE ends a test in progress. Y or [N] Identifies status of DS2 AIS alarm relay. • Yes (Y) - enables alarm • No (N) - disables alarm One of the following: • T1 • E1 Identifies DS2 Configuration.
Chapter 9. Transaction Language 1 (TL1) Table 9-9. TL1 Editing Data Dictionary for DS1 Keyword DIAGDSXTESTSTATE DSXCAISRLY Type ENUM Y/N Domain Description One of the following: • DATAMODE • TRIBUTARY • ANALOGNET • DIGNET • CODEC • REMLPBK • CSULPBK • CSUBERT • LINEBERT Identifies DSX Diagnostic Loopbacks. Choose an available loopback. DATAMODE ends a test in progress. Y or [N] Identifies status of DSX CAIS alarm relay.
Chapter 9. Transaction Language 1 (TL1) Table 9-9. TL1 Editing Data Dictionary for DS1 (Continued) Keyword DSXLBKDETECTION Type ENUM Domain Description One of the following: • DISABLE • CSU • NIU • UNAVAIL Identifies for each T1/E1 interface whether the T1/E1 will respond to loopback requests. DSXLOSRLY Y/N Y or [N] Identifies status of DSX LOS alarm relay.
Chapter 9. Transaction Language 1 (TL1) The following data dictionary (Table 9-10) contains entries that are used to edit or retrieve options for the equipment portion of the MX2810. When performing TL1 edit commands from this table, the value of rr should be "EQPT" and the value should be one of the following: 400 - All EQPT identifiers 401 - Generic 402 - Control Card A 403 - Control Card B 404 - Power Supply A 405 - Power Supply B Table 9-10.
Chapter 9. Transaction Language 1 (TL1) Table 9-10. TL1 Editing Data Dictionary for EQPT (Continued) Keyword Type Domain Description PSPOWERFAILRLY Y/N Y or [N] Identifies status of Power Supply Power Fail alarm relay. • Yes (Y) - enables alarm • No (N) - disables alarm PSPOWERLOWRLY Y/N Y or [N] Identifies status of Power Supply Power Low alarm relay.
Chapter 9. Transaction Language 1 (TL1) TL1 Loopback Commands: The OPR-LPBK and RLS-LPBK commands are provided as an alternative to ED commands as a way to perform loopbacks through TL1. The general format for these commands is as follows: OPR-LPBK-{T1|T2|T3}::::,,,; RLS-LPBK-{T1|T2|T3}::::,,,; The following table will describe each of the DS3 loopbacks that can be initiated or released with these commands. Table 9-11.
Chapter 9. Transaction Language 1 (TL1) Table 9-12. DS2 TL1 Loopback Commands Verb OPR RLS RLS MOD2 T2 T2 T2 2xy 2xy 2xy Description NEND NEND NETWORK NETWORK Releases the DS2 Network Loopback Initiates the DS2 Network Loopback Releases any active DS2 Loopback For the above DS2 related commands, xy may be 01 through 07 (corresponding to the desired DS2 channel.
Chapter 9.
Appendix A Acceptance Test Procedure OVERVIEW This document describes the procedures to be used in performing acceptance testing of ADTRAN’s Total Access MX2810 M13 Multiplexer. It is assumed that the MX2810 has already been installed, powered-up, equipped and cabled to the DSX-1 and DSX-3 or connecting equipment (e.g., DCS) according to the specifications described in the MX2810 Chassis Practice and local operating company procedures.
Appendix A. Acceptance Test Procedure • Alarm Verification • Redundancy/Protection Switching Tests • Configuring the MX2810 for Remote Access • Restoring the System to Default Configuration • Final System Configuration • Completing the Acceptance Test Procedures Checklist EQUIPMENT VERIFICATION The installed configuration determines the level of redundancy the unit supports. There may be one or two Power Supply Units (PSU) and Controller Card Units (CCU) present.
Appendix A. Acceptance Test Procedure accepted, the MX2810 Main Menu should appear. This is the screen from which all other management and control functions are accessed. Provisioning the DS3 Port In order for the MX2810 to correctly pass traffic through the system, the DS3 and DS1 ports need to be properly configured. The provisioning of the DS3 port will be done in this section, and the provisioning of the DS1 ports will be covered in the following.
Appendix A. Acceptance Test Procedure Miscellaneous • Loopback Time Out = 1 hr. (default) DS2 Configuration (no changes are required to DS2 Configuration) • DS2 #1 = M12(4xT1) • DS2 #2 = M12(4xT1) • DS2 #3 = M12(4xT1) • DS2 #4 = M12(4xT1) • DS2 #5 = M12(4xT1) • DS2 #6 = M12(4xT1) • DS2 #7 = M12(4xT1) 2. Press the key to get back to the main Configuration Menu. Provisioning the DS1 Ports A-4 1. From the main Configuration menu, select T1/E1 Interface (2).
Appendix A. Acceptance Test Procedure menu and proceed to the next step. If not, perform the Set Multiple routine accordingly. 5. Select T1/E1 Line length (3). If all channels are set correctly (0-133, 133-266, 266-399, 399-533 or 533-655 feet) as appropriate for the installation, proceed to the next step. If not, perform the Set Multiple routine accordingly. 6. None of the other settings are important to the acceptance testing process. As such, they will not be addressed. 7.
Appendix A. Acceptance Test Procedure OVERALL SYSTEM AND CABLING TEST Now that the system has been properly provisioned for acceptance testing, we can proceed with the actual acceptance testing of the system. The first key test is to verify that the MX2810 will pass traffic between the DS1 and DS3 ports. Three different methods of testing are presented. One of the three should be selected based on test equipment availability and network configuration.
Appendix A. Acceptance Test Procedure 5. The MX2810 will be in an alarm condition because of the previously tested and now un-terminated DS1 ports, but this should not prohibit a successful BERT between the DS1 and DS3 test sets on the channel under test. 6. Leave this test set-up in place, as it will be used during the redundancy testing portion of this document. Proceed to Alarm Verification.
Appendix A. Acceptance Test Procedure 7. Leave this test set-up in place, as it will be used during the redundancy testing portion of this document. Proceed to Alarm Verification. DS1 to DS3 (Hard) Loopback This test requires minimal test equipment, tests one DS1 at a time and can be performed single-handedly. It does not verify DS3 cabling integrity (transmit Vs receive) to the DSX3 or connecting equipment. Equipment Required: • 1 DS1 Test Set capable of running a BERT test • 1 DS3 Test Cord A-8 1.
Appendix A. Acceptance Test Procedure ALARM VERIFICATION The MX2810 has three sets of alarm relay contacts available for connection to external alarm systems. They are located on the back panel and are designated as CRITICAL, MAJOR and MINOR. Normally "Open" and "Common" contacts are available for each of the relay outputs. In the section above, a test scenario was designed to activate each of the relays. The CRI (Critical) alarm is activated when the DS3 port experiences a Loss of Signal (LOS) event.
Appendix A. Acceptance Test Procedure MAJOR and MINOR Alarm Relay Test This test will actuate the MAJOR and MINOR alarm relay contacts. 1. Ensure that the DS3 is not in alarm (DS3 STATUS LED is solid Green on the Active Controller). The easiest way to do this is to once again re-install a hard loopback of the DS3 toward the MX2810. 2. Ensure that the 28 DS1s are out of alarm.
Appendix A. Acceptance Test Procedure Power Supply Redundancy When installed, the MX2810 can be wired to have either one or two -48VDC power feeds (A and B). In addition, the MX2810 chassis can be equipped with either one or two Power Supply Modules. Test scenarios for the two most common configurations follow. Testing of the other configurations is nothing more than a subset of what follows.
Appendix A. Acceptance Test Procedure 2. Go to the fuse panel at the top of the bay and remove the fuse corresponding to the A power feed. This should have no effect on the operation of the shelf, as the B Power Supply is now running on the B power feed. 3. Reinsert the fuse for the A power feed. 4. Remove the fuse corresponding to the B power feed to the shelf. Again, this should have no effect on the operation of the shelf, as the B Power Supply is now operating on the A power feed. 5.
Appendix A. Acceptance Test Procedure the Controller, an alarm is initiated and the front panel LEDs reflect the condition (ACT LED is either solid or blinking Red). If the MX2810 is equipped with two Controller Modules, all traffic is protected and can be switched over to the Standby Controller in the event of a card failure. The following procedures will demonstrate the functionality of a Controller switchover. 1.
Appendix A. Acceptance Test Procedure 2. From the System Management Configuration screen, select Local IP Address (1). Enter the correct IP Address, e.g., 10.13.254.27, as provided by appropriate engineering personnel. 3. Also from the System Management Configuration screen, enter the correct Gateway and Subnet Mask addresses. Once the IP Address info has been entered into the system, the final step in the process involves assigning a Target ID (TID) to the system.
Appendix A. Acceptance Test Procedure no settings on the MX2810. The RS232 Data Communication Interface on the shelf backplane will be used for that type of connectivity. NOTE: MX2810 chassis’ equipped with X.25 as opposed to Ethernet connectivity will be limited to TL1 provisioning and maintenance, i.e., craft-interface accessibility does not exist. Once the system has been configured for remote access and tested satisfactorily in that regard, autonomous alarm reporting to NMA can then be tested.
Appendix A. Acceptance Test Procedure • Disabled – No signal continuity exists through the MX2810 and no alarms are detected or transmitted. • Enabled – Signal continuity and alarming are always enabled. • Auto Enable (default) – Signal continuity and alarming exist only after a DS1 signal is detected at the DS1 input to the MX2810.
Appendix A. Acceptance Test Procedure MX2810 ATP CHECKLIST/SIGN-OFF Use the table below to identify the MX2810 configuration, identify tests performed, etc.
Appendix A.
Appendix B Pinouts The following tables give the pin assignments for the connectors located on the MX2810. For more information on these connectors, see the chapter Installation and Operation on page 2-1. Table B-1. Craft Port Pin Assignments RJ Pin# DB-9 Function Direction 1 5 GND 2 7 RTS I 3 3 TD I 4 6 DSR O 5 2 RD O 6 8 CTS* O 7 4 DTR I 8 1 DCD O - 9 not used - * Used for hardware flow control.
Appendix B. Pinouts Table B-2. LAN Port Pin Assignments B-2 Pin Name Description 1 TD+ The positive signal for the TD differential pair. This signal contains the serial output data stream transmitted onto the network. 2 TD- The negative signal for the TD differential pair (pins 1 and 2). 3 RD+ The positive signal for the RD differential pair. This signal contains the serial input data stream received from the network.
Appendix B. Pinouts Table B-3.
Appendix B.
Appendix C Specifications Summary SPECIFICATIONS AND FEATURES This section describes the standard specifications and features incorporated in the MX2810. DSX-3 Network Interface Channelized DS3 Line length: short (less than 225 ft.) and long (greater than 225 ft.) Framing format: M13 and C-bit parity Line rate: 44.736 Mbps Line interface: dual 75-ohm BNC coax female connectors DSX-1 Interface(s) Line length: 0-655 feet Line rate: 1.
Appendix C. Specifications Summary Line loopbacks DS2 Interfaces DS2 network loopbacks DSX-1 Interfaces Local and network loopbacks Management VT100 Terminal Interface DB-9, EIA-232 compatible SNMP/TELNET Integrated 10BaseT ethernet MIB II (RFC 1213), RFC 1215 and RFC 1407 compliant. ADTRAN Enterprise MIB for extended monitoring and control/ configuration Alarms External alarm contacts for critical, major, and minor alarms.
Appendix C. Specifications Summary Environment Operating: 0 to 50 °C (32 to 122 °F) Storage: -20 to 70 °C (-4 to 158 °F) Relative Humidity: Up to 95%, non-condensing Power DC version: -48 VDC, 30W Physical Dimensions: 7.86“D x 17.0“W x 1.7“H Weight: 5.5 lbs. (redundant); 4.5 lbs.
Appendix C.
Appendix D Acronyms/Abbreviations ACO .................. alarm cut off ACT ................... active AIS..................... alarm indication signal ALM .................. alarm AMI ................... alternate mark inversion Amp................... amphenol ANSI ................. American National Standards Institute async ................. asynchronous BERT ................. bit error rate test bps ..................... bits per second BPV ...................
Appendix D. Acronyms/Abbreviations CSES.................. C-bit severely errored seconds CSU ................... channel service unit CTS.................... clear to send CV...................... coding violation dB....................... decibel DBU................... dial backup DCD .................. data carrier detect DCE ................... data communications equipment DDS................... digital data service DLCI.................. data link connection identifier DS1 ........
Appendix D. Acronyms/Abbreviations LAIS .................. loop side alarm indication signal LAN................... local area network LCV ................... line coding violation LED ................... light emitting diode LES .................... line errored seconds LIU..................... line interface unit LL....................... local loopback LOF.................... loss of framing LOS ................... loss of signal MBE................... M-bit errors Mbps .............
Appendix D. Acronyms/Abbreviations PVC ................... permanent virtual circuit RD...................... receive data RDL ................... remote digital loopback RL....................... remote loopback RMA.................. return material authorization RS....................... request to send RTS .................... request to send Rx ....................... receive SA ...................... service affecting SEFS .................. severely errored framing seconds SES....
Appendix E Glossary 10BaseT Ethernet connector which implements the IEEE standard on 24-gauge, unshielded twisted-pair wiring. AMI Alternate mark inversion. A bipolar line-coding format in T1 transmission systems whereby successive ones are alternately inverted. ANSI American National Standards Institute. A non-profit organization that coordinates voluntary standards activities in the United States.
Appendix E. Glossary bipolar A signal containing both positive and negative amplitude components. bipolar violation See BPV. bit A binary digit representing a signal, wave, or state as either a one or a zero. A bit is the smallest unit of information a computer can process. bit error The receipt of an encoded bit that differs from what was sent by the transmitter. bit rate The speed at which bits are transmitted, usually expressed in bits per second (bps). bps Bits per second.
Appendix E. Glossary C-bit An overhead bit in the DS3 string not used for framing, parity, or alarm indication. CCITT Consultive Committee for International Telephony and Telegraphy. A standards organization that devises and proposes recommendations for international communications. See also ANSI. CD Carrier detect. A signal generated by a modem or DSU/CSU indicating the presence of a carrier signal on a communications link.
Appendix E. Glossary craft port The electrical interface between the MX2810 and the control terminal. The control terminal is used to communicate commands to the unit. CSU Channel service unit. A device used to connect a digital phone line coming in from the phone company to either a multiplexer, channel bank, or directly to another device producing a digital signal; for example, a digital PBX, a PC, or data communications device.
Appendix E. Glossary delay The amount of time by which a signal is delayed. A round-trip transmission delay measurement helps detect possible causes of protocol timeouts. DLCI Datalink communications identifier. A unique number assigned to a PVC endpoint in a frame relay network. Identifies a particular PVC endpoint within a user's access channel in a frame relay network and has local significance only to that channel. DS1 Digital signal level one.
Appendix E. Glossary ethernet Transmission protocol for packet-switching LANs. facilities The equipment used by carriers to provide communication services. far end The distant end to that being considered. Not the end where testing is being carried out. FCC Federal Communications Commission. The U.S. federal agency responsible for regulating interstate and international communications by radio, TV, wire, satellite, and cable. FDL Facility datalink.
Appendix E. Glossary LAN Local area network. A privately owned network that offers high-speed communications channels to connect information processing equipment in a limited geographic area. local loopback (LL) A type of test used to verify the operation of the local terminal equipment, the CSU, and the connection between the two. The signal from the DTE is looped back by the CSU and is sent back to the DTE. loopback The technique for testing the processing circuitry of a communications device.
Appendix E. Glossary NC Normally closed. Relay switch contacts that remain closed when inactive. near end The unit on-site. NI Network interface. The demarcation point between the CPE and the PSTN. NO Normally open. Relay switch contacts that remain open when inactive. NRZ Non return to zero. A mode in which the digital level is low for a 0 bit and high for a 1 bit, and does not return to zero between successive 1 bits.
Appendix E. Glossary red alarm Unframed all ones signal (keep alive signal). A red alarm is declared on detection of LOS or OOF not caused by an alarm indication signal (AIS) that persists for more than two seconds. remote configuration A feature designed into ADTRAN products that allows remote units to be configured from a local unit or a VT 100 compatible terminal. router A device that supports communications between networks.
Appendix E. Glossary SR Data set ready. A signal on the DTE interface that indicates if a connection exists and if the devices are ready to start handshaking control signals so communications can begin. synchronous Communications in which the timing is achieved by sharing a single clock. Each end of the transmission synchronizes itself with the use of clocks and information sent along with the transmitted data. T1 Transmission rates of 1.544 Mbps are available on T1 communication lines.
Appendix E. Glossary WAN Wide area network. A communications network serving geographically separate areas. A WAN typically extends a LAN outside the building to link to other LANs over telephone lines. yellow alarm A T3 yellow alarm is an indication sent back toward the source of a failed transmit circuit in a DS3 two-way transmission path. The X-bits (X1 and X2) are set to zero.
Appendix E.
Index Numerics 10BaseT connection, location of 2-7 24 Hour Alarm History DS2 Statistics menu 5-9 DS3 Statistics menu 5-2 A Acknowledge Alarms (ACO) menu 4-8 acknowledgment messages 9-6 All Right 9-6 In Progress 9-6 ACO buttons 2-9 ACT LED, active cards 2-10 ACT LED, standby cards 2-11 Active Controller menu 3-5 Active state, Card A/Card B 4-6 AFE PROGRAM FAILURE 3-29 agent, SNMP 1-3 AIS 24 Hour Alarm History (DS2 Statistics) 5-9 24 Hour Alarm History (DS3 statistics) 5-3 Alarm Traps Far-end Active Cards,
Index BERT CSU Loopback w/ 6-5 Line 6-6 Bipolar Violations 5-11 blue alarm DS2 State 4-7 network state 4-2 Remote status 4-3 breakout panel connecting 2-5 overview 1-4 C CAIS T1/E1 Alarm Traps 3-20 T1/E1 State 4-8 Card A/Card B Active state 4-6 Failure 4-6 Not Installed 4-6 Stand By 4-6 Card A/Card B menu 4-6 Card Comm menu 4-6 Card Failure Controller Trap 3-16 Power Supply Alarm Trap 3-17 System State Alarm 4-5 Card Removed Controller Trap 3-16 Power Supply Alarm Trap 3-17 card switching 7-3 C-Bit Coding
Index DS2 State 4-7 AIS 4-7 LOF 4-7 OK 4-7 RAI 4-7 DS2 Statistics menu 5-9 DS3 Alarm Traps Far-end Active Cards 3-19 AIS 3-19 Comn Eqpt Fail NSA 3-19 DS3 Eqpt Fail NSA 3-19 DS3 Eqpt Fail SA 3-19 Idle 3-19 LOS 3-19 OOF 3-19 DS3 Alarm Traps Near-end Active and Standby Cards 3-18 Idle 3-18 In/Out Test 3-18 LOS 3-18 OOF 3-18 RAI 3-18 TX LOS 3-18 XCV 3-18 DS3 Alarms 3-14 DS3 Configuration menu 3-3 DS3 Eqpt Fail (NSA) 4-4 DS3 Eqpt Fail (NSA), Trap Community Name 3-19 DS3 Eqpt Fail (SA) 4-4 DS3 Eqpt Fail (SA), Tr
Index Interface menu, T1/E1 3-6 Interval starting at:, Performance Parameters (DS3) 5-6 IOX PROGRAM FAILURE 3-29 IP address trap 3-16 IP Hosts menu 3-25 IP Security menu 3-25 L LAIS T1/E1 Alarm Traps 3-20 T1/E1 State 4-8 LAN pin assignments B-2 LAN port 2-7 LED conditions active cards 2-10 standby cards 2-11 T1/E1 2-12 LEDs 2-9 ACT, active cards 2-10 ACT, standby cards 2-11 ALM, active cards 2-10 ALM, standby cards 2-11 CHK 2-9 DS3, active cards 2-10 DS3, standby cards 2-11 PRF, active cards 2-11 PRF, sta
Index MIB II Standard Alarm Traps 3-20 Authentication Failure 3-20 Cold Start 3-20 Link Down 3-20 Link Up 3-20 MIB, SNMP 1-3 Min.
Index Power Supply Alarm Traps 3-17 Card Removed 3-17 Malfunction 3-17 Power Low 3-17 Temperature Critical 3-17 Temperature High 3-17 Power Supply Alarms alarm relay 3-15 power supply and source recovery mode 8-4 power supply recovery mode 8-3 Power Supply State Error 4-4 Normal 4-4 Power Fail 4-4 Power Low 4-4 Temp Critical 4-4 Temp High 4-4 Power Supply State menu 4-4 power up AC version 2-2 DC version 2-2 PRF LED, active cards 2-11 PRF LED, standby cards 2-11 protection circuit failure 7-1 network failu
Index specifications, MX2800 C-1 Stand By, Card A/Card B 4-6 State menu (DS3 State) 4-2 State menus, T1/E1 3-6 Statistics menu 5-1 24 Hour Alarm History (DS2) 5-9 24 Hour Alarm History (DS3) 5-2 Clear All T1/E1 Alarm Counts 5-11 DS2 Statistics 5-9 DS3 Statistics 5-2 Performance Parameters (DS3) 5-4 T1/E1 Statistics 5-11 Statistics menus 5-1 status LEDs 2-9 Status menu 4-1 Acknowledge Alarms (ACO) 4-8 Alarm (DS3 State) 4-2 Alarm (System State) 4-5 Card A/Card B 4-6 Card Comm 4-6 DS2 State 4-7 DS3 State 4-1
Index TL1 9-1 alarm events 9-17 autonomous messages 9-17, 9-22 commands 9-11 Editing 9-23 error codes 9-23 informational events 9-22 messages 9-4 responses 9-5 TLOS, State 4-3 Transmission menu 3-26 Trap Community Name menu 3-21 Trap Generation menu 3-16 Trap IP Addresses menu 3-16 traps controller 3-16 Tributary loopback 6-2 TST, T1/E1 State 4-8 TX LOS 3-18 U UL information (DC version) 2-4 Unavailable Seconds (UAS) 5-6 Unit ID Code menu 3-26 Unknown, Remote state 4-4 unpacking the unit 2-1 Index-8 upd
