ADTRAN | MX2810 | Installation and Maintenance | Adtran MX2810 Installation and Maintenance

Adtran MX2810 Installation and Maintenance
®
MX2810 Controller Module
Installation and Maintenance Practice
Document Number: 61185002L2-5C
CLEI: M3C3HP0A_ _
September 2005
MX2810 Controller Module Installation and Maintenance Practice
Trademarks
Front Matter
Any brand names and product names included in this manual are trademarks, registered
trademarks, or trade names of their respective holders.
To the Holder of the Manual
The contents of this publication are current as of the date of publication. ADTRAN® reserves
the right to change the contents without prior notice.
In no event will ADTRAN be liable for any special, incidental, or consequential damages or
for commercial losses even if ADTRAN has been advised thereof as a result of issue of this
publication.
®
901 Explorer Boulevard
P.O. Box 140000
Huntsville, AL 35814-4000
(256) 963-8000
©2005 ADTRAN, Inc.
All Rights Reserved.
ii
61185002L2-5C
Revision History
Revision
Date
Description
A
November 2003
Initial release
B
April 2004
Update CLEI; detail M13 In-band addressable loopbacks; detail
software mismatch condition and alarm suppression delay
C
September 2005
Update CLEI; changed to DS3 LIU integrated circuit and updated
software.
Conventions
The following typographical conventions are used in this document:
This font indicates a cross-reference link. First-time references to tables and figures are
shown in this font.
This font indicates screen menus, fields, and parameters.
THIS FONT indicates keyboard keys (ENTER, ESC, ALT). Keys that are to be pressed simultaneously are shown with a plus sign (ALT+X indicates that the ALT key and X key should be
pressed at the same time).
This font indicates references to other documentation and is also used for emphasis.
This font indicates on-screen messages and prompts.
This font indicates text to be typed exactly as shown.
This font indicates silkscreen labels or other system label items.
This font is used for strong emphasis.
NOTE
Notes inform the user of additional but essential information or
features.
CAUTION
Cautions inform the user of potential damage, malfunction, or disruption to equipment, software, or environment.
WARNING
Warnings inform the user of potential bodily pain, injury, or death.
61185002L2-5C
iii
MX2810 Controller Module Installation and Maintenance Practice
Training
ADTRAN offers training courses on our products. These courses include overviews on product
features and functions while covering applications of ADTRAN’s product lines. ADTRAN
provides a variety of training options, including customized training and courses taught at our
facilities or at customer sites.
For inquiries concerning training, contact ADTRAN:
Training Phone:
800-615-1176, ext. 7500
Training Fax:
256-963-6700
Training Email:
training@adtran.com
iv
61185002L2-5C
Contents
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Compliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
1
1
1
Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Instructions for Installing the Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Network Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
DS3 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Remote Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
XCV Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Protection Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Active Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Maximum Switch Threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Minimum Switching Period . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Loopback Time Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
DS2 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
T1/E1 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
T1/E1 State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Set Multiple . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
T1/E1 Line Coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
T1/E1 Line Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
T1/E1 Loopback Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
T1/E1 Circuit Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
T1/E1 Line Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
System Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
TL1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Local IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Gateway IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Subnet Mask . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Alarm Relays . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
SNMP Management Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Trap IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Trap Generation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Read Community Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Write Community Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
61185002L2-5C
v
MX2810 Controller Module Installation and Maintenance Practice
Trap Community Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
User Account Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Guest privilege level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interface privilege level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Test privilege level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Admin privilege level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Terminal Time Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Security . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Hosts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Miscellaneous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Equipment Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unit ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Family ID/Location ID/Frame ID/Unit and Equipment Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Syslog Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severity Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Host Facility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Auto Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Utilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Updating Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Update Via XModem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Update via TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Save Configuration and Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
14
14
14
14
14
14
14
15
15
15
15
15
15
15
15
16
16
16
16
16
16
17
17
17
19
19
Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DS3 Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Interval starting at . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Code Violations – Line (CV-L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Errored Seconds – Line (ES-L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severely Errored Seconds – Line (SES-L) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
SEF/AIS Seconds (SAS-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Code Violations – P-Bit (CVP-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Errored Seconds – P-Bit (ESP-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severely Errored Seconds – P-Bit (SESP-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unavailable Seconds – P-Bit (UASP-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Coding Violations – C-Bit (CVCP-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Errored Seconds – C-Bit (ESCP-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C-Bit Severely Errored Seconds (CSES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unavailable Seconds – C-Bit (UASCP-P) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
F-Bit Errors (FBE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
M-Bit Errors (MBE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Code Violation C-bit Parity (CVCP-PFE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Errored Seconds – Far-End (ESCP-PFE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severely Errored Seconds – Far-End (SESCP-PFE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Unavailable Seconds – Far-End (UASCP-PFE) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DS2 Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Local Port Performance Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line Coding Violations (LCV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Errored Seconds (ES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severely Errored Seconds (SES) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Protection Switch Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
20
20
20
20
20
20
20
20
20
20
21
21
21
21
21
21
21
21
21
21
21
22
22
22
22
22
22
Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
vi
61185002L2-5C
Contents
T1/E1 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tributary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Analog Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital Line/Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Codec Line/Net . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSU Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CSU Loopback w/BERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line BERT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DS3 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Digital Diagnostics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Network Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Remote All T1/E1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DS2 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
DS2 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
23
23
23
23
23
23
24
24
24
24
24
24
25
25
25
25
25
Front Panel Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Alarm Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
ACO Buttons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Specifications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Appendix A
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Warranty and Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADTRAN Sales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADTRAN Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
ADTRAN Repair/CAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Repair and Return Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61185002L2-5C
A-1
A-1
A-1
A-1
A-1
vii
MX2810 Controller Module Installation and Maintenance Practice
Figures
Figure 1.
Figure 2.
MX2810 Controller Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
MX2810 Controller Module Menu Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Tables
Table 1.
Table 2.
Table 3.
Table 4.
Table 5.
Table 6.
Table 7.
Table 8.
Table 9.
Table 10.
Table 11.
Table 12.
Table 13.
Table 14.
Table 15.
Table 16.
Table 17.
Table 18.
Table 19.
Table 20.
viii
Compliance Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2
XCV Threshold Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
DS3 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
DS2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
T1/E1 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Power Supply Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Controller Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Power Supply Alarm Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
DS3 Alarm Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
DS3 Alarm Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
DS2 Alarm Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
T1/E1 Alarm Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
MIB II Standard Alarm Traps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Syslog Severity Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Self Test Results . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Status LED Conditions for Active Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Status LED Conditions for Standby Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
DSX-1 LED Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
MX2810 Controller Module Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
61185002L2-5C
MX2810 Controller Module
GENERAL
This practice is an installation and maintenance guide for the ADTRAN MX2810 Controller
Module. Figure 1 illustrates the MX2810 Controller Module (P/N 1185002L2) front panel.
Figure 1. MX2810 Controller Module
Description
The MX2810 Controller Module (CCU) is a plug-in unit for the MX2810 chassis that provides
1:1 redundancy for the T1 and T3 signals. With two cards installed, the MX2810 can recover
from circuit failure.
Features
The basic features of the MX2810 Controller Module, include the following:
• 1:1 redundancy
• Hot-swappable
• Alarm cutoff (ACO) pushbutton
• Meets the requirements for NEBS Level 3
• M13 and C-bit signaling support
Compliance
This device complies with Part 15 of the FCC rules. Operation is subject to the following two
conditions:
61185002L2-5C
1
MX2810 Controller Module Installation and Maintenance Practice
1. This device may not cause harmful interference.
2. This device must accept any interference received, including interference that may cause
undesired operation.
Changes or modifications not expressly approved by ADTRAN could void the user’s authority
to operate this equipment.
Table 1 shows the compliance codes for the MX2810 Controller Module. The MX2810
Controller Module is NRTL listed to the applicable UL standards. The MX2810 Controller
Module is to be installed in a restricted access location.
Table 1. Compliance Codes
Code
Input
Output
Power Code (PC)
C
C
Telecommunication Code (TC)
–
–
Installation Code (IC)
A
–
INSTALLATION
C A U T I O N !
SUBJECT TO ELECTROSTATIC DAMAGE
OR DECREASE IN RELIABILITY.
HANDLING PRECAUTIONS REQUIRED.
After unpacking the MX2810 Controller Module, inspect it for damage. If damage has
occurred, file a claim with the carrier then contact ADTRAN Customer Service. Refer to
“Appendix A, Warranty” for further information. If possible, keep the original shipping
container for returning the MX2810 Controller Module for repair or for verification of shipping
damage.
CAUTION
Electronic modules can be damaged by ESD. When handling modules, wear an antistatic discharge wrist strap to prevent damage to
electronic components. Place modules in antistatic packing material when transporting or storing. When working on modules,
always place them on an approved antistatic mat that is electrically
grounded.
Instructions for Installing the Module
To install the MX2810 Controller Module, perform the following steps:
2
61185002L2-5C
Configuration
1. If present, remove the Access Module Blank from the appropriate access module slot of
the MX2810 chassis.
2. Pull the ejector latches, located on each side of the MX2810 Controller Module front panel,
from the closed position.
3. Hold the MX2810 Controller Module by the front panel while supporting the edges of the
module with the ejector latches opened to engage the chassis edge.
4. Align the module edges to fit in the left and right guide grooves for the access module slot.
5. Slide the module into the access module slot. Simultaneous thumb pressure at each side
of the module will ensure that the module is firmly seated against the backplane of the
chassis.
6. Secure the MX2810 Controller Module in place by pushing in on the ejector latches
simultaneously.
When the MX2810 Controller Module is installed it performs a series of self-tests. Once the
self-tests are complete, the status LEDs will reflect the true state of the hardware.
CONFIGURATION
To configure the MX2810, use a 10Base-T Ethernet connection or a VT100 terminal. Figure 2
shows the CONFIGURATION menu tree.
NOTE
VT100 menus can be accessed by initiating a Telnet connection to
the IP address of the MX2810 on port number 23 (the standard
port number for Telnet connections) or on port number 2002.
61185002L2-5C
3
MX2810 Controller Module Installation and Maintenance Practice
1. C-BIT
1. Framing
DS3 Configuration
2. M13*
2. Timing
1. Network Interface
1. A*
6. Active Controller
Protection Configuration
2. B
1. Disabled
1. Loop*
2. FEAC/C-BIT*
2. Local
3. FEAC
3. Remote Loopbacks
4. C-BIT
4. XCV Threshold
7. Max Switch Threshold (3)*
1. Disabled*
Miscellaneous
8. Min Switch Period (10)*
9. Loopback Timeout
DS2 Configuration
2. Line Coding
1. Disabled
T1 # 1-28
3. Line Length
3. 5 min.
2. G.747 (3 x E1)
4. 10 min.
8. 1 hour*
4. 399-533 ft.
T1 # 1-28
1. Disabled*
5. 533-655 ft.
T1 # 1-28
2. CSU
1. Disabled
6. Line Identification
3. NIU
2. Enabled*
T1 # 1-28
1. Disabled*
1. Controller Traps
2. IE-3
7. XCV Threshold
1. Local IP Address
Mgmt Options
2. Gateway IP Address
Alarm Relays
5. IE-6
6. 30 min.
7. 45 min.
3. 266-399 ft.
2. B8ZS*
5. Circuit Protection
1. 0-133 ft.*
2. 133-266 ft.
1. AMI
4. Loopback Detection
4. IE-5
5. 15 min.
3. Auto Enable*
T1 # 1-28
2. T1/E1 Interface
1. M12 (4 x T1)*
2. Enabled
T1 # 1-28
3. IE-4
2. 1 min.
10-16. DS2 # 1-7
1. State
2. IE-3
1. Disabled
3. IE-4
2. Power Supply Alarm Traps
4. IE-5
3. DS3 Alarm Traps
4. DS2 Alarm Traps
5. IE-6
5. T1/E1 Alarm Traps
3. Subnet Mask
6. MIB II Standard Alarm Traps
4. Alarm Relay Configuration (all Disabled*)
SNMP Mgmt Options
5. Trap IP Address
10. User Account Management
6. Trap Generation
11. Terminal Timeout (15 Min.)*
7. Read Community Name
12. IP Security (Disabled)*
8. Write Community Name
13. IP Hosts (0.0.0.0)*
9. Trap Community Name
1. Unit ID
System Security
3. System Management
Date & Time
2. Local Facility ID Code
14. Date
3. Local Location ID Code
15. Time
4. Local Frame ID Code
16. Circuit Identification
Miscellaneous
5. Local Unit Code
1. Transmission
17. Syslog Setup
1. Disabled
6. Local Equipment Code
2. Enabled*
Far-End Facility ID Code
2. Host IP Address (0.0.0.0)*
Far-End Location ID Code
Far-End Frame ID Code
3. Severity Level
Far-End Unit Code
4. Host Facility
1. Local 0*
Far-End Equipment Code
2. Local 1
18. Autosave (Enabled)*
19. Autoprogram Cards
(Enabled)*
3. Local 2
4. Local 3
5. Local 4
6. Local 5
4. Utilities
1. Load Default Settings
7. Local 6
2. Update FLASH Software
8. Local 7
3. Configuration Transfer
4. System Reset
1. Via XMODEM
2. Update via TFTP Server
1. Emergency
2. Alert
3. Critical
4. Error
5. Warning*
6. Notice
7. Info
8. Debug
5. Save Configuration & Alarm Log
Defaults = *
Figure 2. MX2810 Controller Module Menu Tree
4
61185002L2-5C
Configuration
To connect the MX2810 to a VT100 terminal, follow this procedure:
1. Configure the VT100 terminal for 9600, 19200, 38400, or 57600 baud; 8-bit characters;
no parity; line-wrap = OFF; and one stop bit.
2. Press ENTER repeatedly until the username and password prompt appears.
3. The factory default username and password are username and password.
The following is a list of available menu options:
Network Interface
Select NETWORK INTERFACE to access the network configuration parameters. Configure the
MX2810 network settings to match the DS3 signal received from the service provider.
DS3 Configuration
Use the DS3 configuration selections to configure the DS3 network settings to match your
application.
Descriptions of these settings follow:
Framing
Set the framing format to match the format of the receive signal at the network interface. The
MX2810 supports C-Bit and M13 framing formats.
Timing
In most cases, configure the MX2810 for Loop timing to derive timing from the network.
However, set to Local if the MX2810 is the master timing source for the circuit.
Remote Loopbacks
Enabling this option allows the MX2810 to respond to remote loopback requests received over
the DS3 Far End Alarm and Control (FEAC) channel when operating in C-Bit parity mode.
When disabled, all loopback requests are ignored.
XCV Threshold
The XCV (excessive code violations) Threshold sets a limit on CVs accepted by the unit 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 Table 2.
61185002L2-5C
5
MX2810 Controller Module Installation and Maintenance Practice
Table 2. XCV Threshold Settings
Setting
Threshold When Unit Switches Controller Cards
1E-3
One out of every 1,000 bits received on the DS3 contains a code violation
1E-4
One out of every 10,000 bits received on the DS3 contains a code violation
1E-5
One out of every 100,000 bits received on the DS3 contains a code violation
1E-6
One out of every 1,000,000 bits received on the DS3 contains a code violation
Protection Configuration
The MX2810 houses two controller cards for 1:1 protection against hardware failure. The
selections in this menu enable the customizing of the protection setup for the unit:
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.
Maximum Switch Threshold
This value determines how many times per hour the unit is allowed to switch between
controller cards. If this number is exceeded, the unit issues a trap and stops switching cards
for a period of 24 hours. The default setting is three times per hour.
Minimum Switching Period
This value sets the number of seconds that must pass before another card switch will be
allowed. The default setting is 10 seconds.
Miscellaneous
Loopback Time Out
Sets the Loopback Time Out to Disabled, 1 minute, 5 minutes, 10 minutes, 15 minutes, 30
minutes, 45 minutes, or 1 hour.
DS2 Configuration
The MX2810 can individually frame each of the seven DS2 streams in M12 (four T1s) or G.747
(three E1s) format.
When set to M12 (4xT1), the four T1s for the selected group are framed per ANSI T1.107.
When set to G.747 (3xE1), the first three T1/E1 ports of the selected group are framed per
CCITT G.747 into the DS3 stream. 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.
6
61185002L2-5C
Configuration
T1/E1 Interface
The T1/E1 INTERFACE menu 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.
Configuration selections are described in the following sections:
T1/E1 State
Set unused T1/E1 lines to Disabled. Set used lines to Enabled. Set to Auto Enable to allow
automatic enabling of port.
Set Multiple
Use Set Multiple to enable or disable any 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 to be
enabled or disabled. Enter Apply Settings.
T1/E1 Line Coding
Set the line code for each individual T1/E1 interface to match the connected device. The
choices available for T1 are AMI and B8ZS. The choices available for E1 are AMI and HDB3.
T1/E1 Line Length
Set the line length for each T1 interface according to the distance from the MX2810 to the DTE
device.
The E1 Line Length is not selectable and remains at 0 - 6 dB loss.
T1/E1 Loopback Detection
Choose which T1/E1 lines will respond to CSU or NIU loopback requests coming from the
network. Set to Disable to have the T1/E1 to ignore the request.
T1/E1 Circuit Protection
Choose which T1/E1 lines to protect. If a T1/E1 is set to Disabled, then the failure of that one
line will not cause the controller cards to switch. If set to Enabled, then the line’s failure could
cause the cards to switch (depending on the Protection Threshold setting in this menu). The
Protection Threshold setting determines how many of the Enabled lines must fail before a card
switch occurs. If you want the failure of a single protected (enabled) line to cause a card
switch, set the Protection Threshold to 1. Choices include 1 through 28.
T1/E1 Line Identification
Enter configurable text strings to name the individual T1/E1 lines. This field can accommodate up to 18 alphanumeric characters, including spaces and special characters.
61185002L2-5C
7
MX2810 Controller Module Installation and Maintenance Practice
System Management
Configure the MX2810 for management through SNMP, Telnet, or a VT100 interface.
Embedded SNMP and Telnet are available via 10Base-T Ethernet interface. This menu also
includes options used to customize alarm and trap generation, security setup, and equipment
identification. The MX2810 M13 multiplexer has SNMP and TL1 capabilities, as described in
the following subsections:
SNMP
The MX2810 implements applicable sections of the MIBs from RFC 1213, 1406, 1407, and the
ADTRAN MIB for the MX2810.
Applicable sections of the MIB from RFC 1213 include System, Interfaces, SNMP, ICMP, TCP,
and UDP. In the case of the MIB from RFC 1406 (DS1 MIB), the MX2810 does not support
near- or far-end DSX-1 Current, Interval, and Total counts, or the Fractional Table. All applicable aspects of RFC 1407 (DS3 MIB) are supported.
The options available on the MX2810 menu system are also available from the SNMP
manager.
Status and performance monitoring parameters are read-only elements, whereas configuration items are read-write. The only items that may not be changed through SNMP are
network management elements that would interfere with proper operation of the Ethernet
interface such as IP address, default router, etc.
Alarm traps are sent for any change in alarm status, including cases when existing alarms are
cleared.
TL1
The MX2810 reports alarms via TL1. Initiate a TL1 session to enable or disable autonomous
alarm reporting or query for current alarm status. TL1 can be accessed by initiating a
connection on port number 3116.
Alarm information is provided for the individual CCUs, any of the 28 individual T1s, any of the
seven individual T2s, and the T3.
Management Options
Local IP Address
Enter the MX2810 IP address.
Gateway IP Address
Enter the gateway IP address of the MX2810.
Subnet Mask
Enter the subnet mask of the MX2810.
8
61185002L2-5C
Configuration
Alarm Relays
Alarm Relay Configuration enables audible and visible alarms for specific error conditions.
The following tables (see Table 3 through Table 7) describe the alarm conditions found in this
menu.
Table 3. 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.
AIS (Alert)
The unit is receiving an AIS (blue) alarm condition from the network. AIS
alarms occur when consecutive 1010s are received in the information bits.
This indicates that there is a transmission fault located either at or upstream
from the transmitting terminal.
LOS (Critical)
The unit has lost the network RX signal.
LOF (Critical
The unit detects a framing loss from the network.
SCV (Alert)
The controller card is receiving excessive code violations, exceeding the threshold set in the Configuration menus (See “XCV Threshold” on page 5).
Table 4. DS2 Alarms
Alarm
Description
RAI (Major)
The unit is receiving an RAI (yellow) alarm from the network across a DS2. This
alarm is a signal sent back toward the source of a failed transmit circuit. The
X-bit is set to zero.
AIS (Alert)
The unit is receiving unframed all ones across a DS2.
LOF (Major)
The unit detects a framing loss from the network.
Table 5. System Alarms
Alarm
Description
Controller A Fail
(Critical)
Controller Card A has failed.
Controller B Fail
(Critical)
Controller Card B has failed.
Protection Switch
The system has switched controller cards (either under manual control or due
to a failure).
Controller Card
Removed (Minor)
Controller Card has been removed.
61185002L2-5C
This is a critical alarm only when Card B is not installed or is not working.
This is a critical alarm only when Card A is not installed or is not working.
9
MX2810 Controller Module Installation and Maintenance Practice
Table 6. T1/E1 Alarms
Alarm
Description
LOS (Major)
The unit has lost the receiver signal on a T1/E1.
XCV (Alert)
The controller card is receiving excessive code violations, exceeding the provisioned threshold setting.
CAIS (Carrier side
AIS) (Alert)
The T1 is receiving all ones from the DS3 side of the network.
LAIS (Loop side
AIS) (Alert)
The T1 is receiving all ones from the DSX-1 interface.
Table 7. 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 output is abnormally low.
Power Fail (Minor)
Power supply card input is lost.
Temperature High
(Minor)
Power supply card temperature is above normal.
Temperature
Critical (Minor)
Power supply card temperature is so high that it will soon shut off completely.
–48 VDC Input Fail
(Minor)
–48 VDC input has failed or has been removed.
Power Card
Removed (Minor)
Power supply card has been removed.
10
61185002L2-5C
Configuration
SNMP Management Options
Trap IP Addresses
Enter up to five IP addresses of SNMP managers to which the MX2810 sends traps.
Trap Generation
The TRAP GENERATION menu allows the specification of error conditions that will cause the
unit to send trap messages. See Table 8 through Table 14 for a listing of traps.
Table 8. Controller Traps
Alarm
Description
Protector Switch
Controller cards are switched.
Card Removed
Controller card has been removed.
Card Failure
Controller card has failed.
Communication
Fail
Controller cards can no longer communicate with each other.
Max Switches
Max switch threshold is reached.
Table 9. Power Supply Alarm Traps
Alarm
Description
Card Removed
Power supply card has been removed.
Malfunction
Power supply card is no longer working, and the unit has switched to the
backup power supply or backup battery.
Card Failure
Power supply card has failed.
Power Low
Power supply output is abnormally low.
Temperature High
Power supply card is getting too hot.
Temperature
Critical
Power supply card temperature is extremely high, and complete shutdown is
imminent.
61185002L2-5C
11
MX2810 Controller Module Installation and Maintenance Practice
Table 10. DS3 Alarm Traps
(Near-End Active and Standby Cards)
Alarm
Description
LOS
Controller has lost the network Rx signal.
OOF
Controller card detected a framing loss from the network.
AIS
Controller card is receiving an AIS (blue) alarm condition from the network.
RAI
Controller card 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-bit
(X1 and X2) are set to zero.
IDLE
Controller card detects an idle sequence from the network. Service is immediately available for use.
TX LOS
Controller card transmitter has failed.
XCV
Controller card is receiving excessive code violations, exceeding the provisioned threshold setting (Refer to “XCV Threshold” on page 5).
In/Out Test
DS3 is going in and out of test (applies to the Active Controller Card only).
Table 11. DS3 Alarm Traps
(Far-End Active Cards)
Alarm
Description
LOS
Active controller card of the remote unit has lost the network Rx signal.
OOF
Active controller card of the remote unit detects a framing loss from the network.
AIS
Active controller card of the remote unit is receiving an AIS (blue) alarm condition from the network.
IDLE
Active controller card of the remote unit detects an idle sequence from the network. Service is immediately available for use.
DS3 Eqpt Fail SA
Active controller card of the remote unit is receiving a service-affecting equipment failure message from the network.
DS3 Eqpt Fail NSA
Active controller card of the remote unit is receiving a non-service affecting
equipment failure message from the network.
Comm Eqpt Fail
NSA
Active controller card of the remote unit is receiving a common equipment failure message from the network.
12
61185002L2-5C
Configuration
Table 12. DS2 Alarm Traps
Alarm
Description
OOF
DS2 detects a framing loss from the network.
AIS
DS2 is receiving an AIS (blue) alarm condition from the network. AIS alarms
occur when unit is receiving unframed all ones.
RAI
DS2 is receiving an RAI (yellow) alarm from the network. This alarm is a signal
sent back to the source of a failed transmit circuit. The X-bit is set to zero.
Table 13. T1/E1 Alarm Traps
Alarm
Description
Local T1/E1 Alarms
LOS
Unit has lost the network Rx signal.
CAIS (carrier side
AIS)
T1 is receiving all ones from the DS2 network.
LAIS (loop side AIS)
T1 is receiving all ones from the DSX-1 interface.
XCV
Unit is receiving excessive code violations across a T1/E1, exceeding the configured threshold.
T1/E1 Failure
T1/E1 has failed.
Far-end Alarms (only available in C-bit parity mode)
In/Out test
T1/E1 is going in and out of test.
Multiple DS1 LOS
Far-end equipment has lost multiple T1/E1 lines.
Single DS1 LOS
Far-end equipment has lost single T1/E1.
DS1 Equipment
Fail SA
Service-affecting equipment failure is being reported by the far-end.
DS1 Equipment
Fail NSA
Non-service affecting equipment failure is being reported by the far-end.
Table 14. MIB II Standard Alarm Traps
Alarm
Description
Cold Start
Unit is first powered up.
Link Up
DS3 is up with no alarm.
Link Down
DS3 is in alarm.
Authentication
Failure
An attempt has been made by an unauthorized account to access the unit.
61185002L2-5C
13
MX2810 Controller Module Installation and Maintenance Practice
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
This menu allows Admin privilege-level accounts to provision up to 15 unique accounts, each
with an associated password and privilege level. The passwords and privilege levels apply both
to menu access and TL1 access. The privilege levels are briefly described below. Refer to the
MX2810 M13 System Manual, P/N 61185001L1-1, for a more complete description of the
privileges associated with each menu item and TL1 command.
Guest privilege level
Allows viewing of most menu items and execution of a limited number of TL1 commands, and
may not alter the product configuration.
Interface privilege level
Allows configuration of the network interface and T1/E1 interface, but not activation of
loopbacks, viewing and/or altering of system-level items such as LAN configurables, etc.
Test privilege level
Allows configuration of the network interface and T1/E1 interface and activation of loopbacks,
but may not view and/or alter several system-level items such as LAN configurables, etc.
Admin privilege level
Allows access to all menu items and execution of all supported TL1 commands.
14
61185002L2-5C
Configuration
NOTE
As part of the “Load Default Settings” operation, all 15 accounts
are removed from the User Account database, and Account #1
becomes:
Username = username
Password = password
Privilege = admin
Terminal Time Out
Set the amount of time the terminal or Telnet session remains inactive before automatically
closing the session (logging off the current account). The options include Disabled, 1 minute,
5 minutes, 15 minutes, 60 minutes, 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.
IP Hosts
Enter up to 16 IP addresses of management stations from which the unit should accept
management commands. These addresses are only applicable if IP Security is enabled.
Date and Time
Enter date and time information. Enter the month, date, and year separated by forward
slashes (02/23/01). Enter the time in military time separated by colons (13:15:25).
Miscellaneous
Equipment Identification
This field allows storage of information that identifies the unit. Information provided for the far
end is read-only. Local information is read/write from this menu.
Unit ID
Provides a configurable text string for the name of the MX2810. It may contain up to 32 alphanumeric characters, including spaces and special characters.
Family ID/Location ID/Frame ID/Unit and Equipment Codes
These fields provide configurable text strings to identify the MX2810 over the network. The
Location ID Code, Frame ID Code, and Equipment Code fields support up to 10 alphanumeric
characters each. The Facility ID Code supports 38 characters, and the Unit Code supports six
characters. This information is transmitted over the DS3 on the equipment ID channel.
61185002L2-5C
15
MX2810 Controller Module Installation and Maintenance Practice
Syslog Setup
Selections include Transmission, Host IP Address, Severity Level, and Host Facility.
Transmission
Enables or disables the transmission of log events to the external Syslog server. Define the
host IP address to enable the event logging.
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 15 in order of decreasing severity. Any message at or above a
selected severity level will be logged if a transmission is enabled.
Table 15. Syslog Severity Level
Alarm
Description
Emergency
The system is unusable.
Alert
An action must be taken immediately.
Critical
Shows critical conditions.
Error
Shows error conditions.
Warning
Shows warning conditions.
Notice
Shows normal, but significant, conditions.
Info
Shows informational message.
Debug
Shows a debug-level message.
Host Facility
Specifies the facility destination of log events. Facilities are located on the host and are
managed by the Syslog host daemon running on either a UNIX machine or a PC. Options
include Local 0-7.
Auto Save
Enable this function to save the configuration upon logout. Disable to exit without saving
changes to the configuration data.
16
61185002L2-5C
Configuration
Utilities
The Utilities menu allows the following:
• Viewing of the MX2810 system information (including self-test results) for both controller
cards
• Reverting to default configuration settings
• Flash-loading a new version of software
• Resetting the system
Possible results for the self-test are listed in Table 16.
Table 16. Self Test Results
Alarm
Description
PASS
The self-test was successful, and the unit is ready to place in service.
BAD RAM DATA
Contact ADTRAN Technical Support.
BAD RAM ADDRESS
BAD CODE CHECKSUM
BAD BOOT SECTOR
IOX PROGRAM FAILURE
AFE PROGRAM FAILURE
ETHERNET FAILURE
CONFIGURATION CORRUPT
Select Save Configuration from the main Configuration menu.
If condition persists, contact ADTRAN Technical Support.
Updating Software
Select UPDATE FLASH SOFTWARE from the UTILITIES menu to update software using either
XMODEM protocol or Trivial File Transfer Protocol (TFTP).
NOTE
Before beginning update of FLASH software, disable the Auto Save
feature of the MX2810. From the CONFIGURATION menu, choose
SYSTEM MANAGEMENT, then select OPTION 19 until AUTO SAVE
is set to DISABLE.
Update Via XModem
Updating the Flash Software via XMODEM requires that a VT100 terminal menu session be
active through the craft port. To update the software via XMODEM, follow the steps below:
1. From the MX2810 MAIN MENU, select CONFIGURATION, select UTILITES, select UPDATE
FLASH SOFTWARE, select UPDATE VIA XMODEM.
2. Once it has been determined where the new binary file is located, select START to begin
the transfer.
61185002L2-5C
17
MX2810 Controller Module Installation and Maintenance Practice
3. Once START has been selected, start the XModem transfer from the terminal menu
program that is being used by selecting or typing the file path for the location of the new
binary file. See appropriate documentation for your terminal emulator to begin XModem
transfer.
4. After selecting the binary file, the XModem transfer will begin. If you wish to cancel a
transfer in progress, press CTRL+X three times. The ACT LED on the active card is solid
amber for the duration of XModem transfer. The ACT LED on the standby card is flashing
green.
5. If updating a unit with redundant controller cards, the active controller will begin
uploading the new code to the standby controller after the XModem transfer has
completed, and the unit has successfully loaded and programmed the new software into
its Flash memory. If the unit does not have redundant controller cards, go to Step 7.
6. While the standby card is having code uploaded, the ACT LED on the standby card will be
solid amber. After the code has finished uploading to the standby card, the card will reset
itself and begin running the new code.
NOTE
The standby card must remain in place until the upload process is
complete, and the ACT LED is no longer solid amber and returns to
flashing green. Removing the standby card during the uploading
process will corrupt the software.
7. The system must be manually reset after downloading new software for the active
controller card to begin running the new code.
From the UTILITIES menu, select SYSTEM RESET, and then 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.
NOTE
Update via XModem is available only when updating the software
through the craft port.
18
61185002L2-5C
Configuration
Update via TFTP Server
Updating the Flash Software via TFTP Server requires that the IP address and file name of file
to be downloaded are known. To update the software via TFTP, follow the steps below:
1. Select UPDATE VIA TFTP SERVER from the UTILITIES menu. A new menu displays, allowing the entry of the IP address and file name of the file to be downloaded to the unit. Once
this information is entered, select START/STOPTRANSFER.
2. After selecting the binary file, the TFTP transfer will begin. If you wish to cancel a transfer
in progress, press CTRL+X three times. The ACT LED on the active card is solid amber for
the duration of TFTP transfer. The ACT LED on the standby card is flashing green.
3. If updating a unit with redundant controller cards, the active controller will begin
uploading the new code to the standby controller after the XModem transfer has
completed, and the unit has successfully loaded and programmed the new software into
its FLASH memory. If the unit does not have redundant controller cards, go to Step 5.
4. While the standby card is having code uploaded, the ACT LED on the standby card will be
solid amber. After the code has finished uploading to the standby card, the card will reset
itself and begin running the new code.
WARNING
The standby card must remain in place until the upload process is
complete and the ACT LED is no longer solid amber. Removing the
standby 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. From the UTILITIES menu, select SYSTEM
RESET, and then 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.
Save Configuration and Alarm Log
Commits the current configuration changes and alarm log to nonvolatile memory. If this
option is not selected after making changes to the configuration, the unit reverts to previous
configuration settings when powered down.
61185002L2-5C
19
MX2810 Controller Module Installation and Maintenance Practice
STATISTICS
The following are descriptions of the DS3, DS2, and local port performance parameters and
the protection switch statistics.
DS3 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.
Use the left and right arrow keys to scroll through all 96 15-minute intervals.
Descriptions of each field follow:
Interval starting at
Time that the 15-minute interval began.
Code Violations – Line (CV-L)
Number of BPVs (bipolar violations) and EXZs (excessive zeros) that have occurred.
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 containing 45 or more CV-Ls or one or more LOS (loss of signal) defects.
SEF/AIS Seconds (SAS-P)
Number of seconds with one or more out-of-frame defects or a detected incoming AIS.
Code Violations – P-Bit (CVP-P)
Number of coding violation (CV) error events that have occurred.
Errored Seconds – P-Bit (ESP-P)
Number of seconds with one or more PCVs (P-bit coding violations), one or more out-of-frame
defects, or a detected incoming AIS. This count is not incremented when UASP-Ps are
counted.
Severely Errored Seconds – P-Bit (SESP-P)
Number of seconds with 45 or more PCVs, one or more out-of-frame defects, or a detected
incoming AIS. This count is not incremented when UASP-Ps are counted.
20
61185002L2-5C
Statistics
Unavailable Seconds – P-Bit (UASP-P)
Number of seconds that DS3 path is unavailable. This begins after ten contiguous SESP-Ps
and ends after ten contiguous seconds with no SESP-Ps.
Coding Violations – C-Bit (CVCP-P)
In C-bit parity mode, this is a count of coding violations reported via the C-bits or the number
of C-bit parity errors that have occurred.
Errored Seconds – C-Bit (ESCP-P)
Number of seconds with one or more CVCP-Ps, one or more out-of-frame defects, or a detected
incoming AIS. This count is not incremented when UASCP-Ps are counted.
C-Bit Severely Errored Seconds (CSES)
Number of seconds with 45 or more CVCP-Ps, one or more out-of-frame defects, or a detected
incoming AIS. This count is not incremented when UASCP-Ps are counted.
Unavailable Seconds – C-Bit (UASCP-P)
Number of seconds that DS3 path is unavailable. This begins after ten contiguous SESCP-Ps
and ends after 10 contiguous seconds with no SESCP-Ps.
F-Bit Errors (FBE)
Number of times an F-bit framing error has occurred.
M-Bit Errors (MBE)
Number of times an M-bit framing error has occurred.
Code Violation C-bit Parity (CVCP-PFE)
Number of times the far-end unit has received a C-parity or framing error.
Errored Seconds – Far-End (ESCP-PFE)
Number of seconds containing one or more CVCP-PFEs.
Severely Errored Seconds – Far-End (SESCP-PFE)
Number of seconds containing 45 or more CVCP-PFEs.
Unavailable Seconds – Far-End (UASCP-PFE)
Number of seconds that DS3 path is unavailable. This begins after ten contiguous SESCPPFEs and ends after 10 contiguous seconds with no SESCP-PFEs.
61185002L2-5C
21
MX2810 Controller Module Installation and Maintenance Practice
DS2 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. When viewing the 24
hour history statistics screen, use left and right arrow keys to scroll through all 96 15-minute
intervals; use the up and down arrow keys to scroll between the PBERR and FBERR menus.
Local Port Performance Parameters
View performance parameter information for the local port in one of the three time period
selections.
Line Coding Violations (LCV)
Number of CV errors.
Errored Seconds (ES)
Number of seconds with CV errors or one or more LOS (loss of signal) errors.
Severely Errored Seconds (SES)
Number of seconds with 45 or more CV errors or LOS (loss of signal) errors.
Protection Switch Statistics
View the number of controller card switches during a specific time interval. The number of
switches for the current 15-minute interval, the past 24-hours, and since the count was last
cleared is displayed. A 24-hour history is also displayed. When viewing the 24-hour history,
use the left and right arrow keys to scroll through all 96 15-minute intervals.
22
61185002L2-5C
Loopbacks
LOOPBACKS
The DIAGNOSTICS menu is utilized to initiate loopback tests from the MX2810.
T1/E1 Loopbacks
Select the number that corresponds with the channel required for test, then select the type of
loopback to be performed. Select DATA MODE to end a test in progress.
The T1/E1 loopbacks are described below:
Tributary
A Tributary loopback loops the selected T1/E1 back to the network (DS3). The T1/E1 is demultiplexed through the M23 and M12/G.747 de-multiplexers, looped back, and multiplexed
back up through the M12/G.747 and M23 multiplexers. During this loopback, all network
receive data is passed to the DSX-1/E1 transmitters, but all data received by the DSX-1/E1
loop side is ignored and substituted with the network data.
Analog Network
An Analog Network loopback test loops the selected T1/E1 back to the network (DS3). The T1/
E1 is de-multiplexed, looped back through the T1/E1 line interface unit (LIU) receiver, and
then multiplexed back onto the DS3 network stream.
Digital Line/Net
A Digital Line/Net loopback performs a loopback of the selected T1/E1 in both the network
and local loop directions. The network side loopback occurs within the CODEC while the
T1/E1 loop side loopback occurs deep into the LIU through the receiver, receive equalizer,
transmit jitter attenuator, and finally through the T1/E1 transmit drivers.
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. Both the network and the
local loop side of the loopback are executed at the edge of the codec, completely testing the
M13 MUX and the T1/E1 LIU.
Remote Loopback
A Remote Loopback performs a loopback of the selected T1/E1 on the far-end M13 multiplexer. If an MX2810 is located at the far end, an Analog Network Loopback is executed when
a Remote Loopback is engaged. This loopback is only available when the DS3 is configured for
C-bit parity framing since it requires the availability of the far-end alarm and control (FEAC)
channel.
61185002L2-5C
23
MX2810 Controller Module Installation and Maintenance Practice
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 6 seconds. After 6 seconds have elapsed, the
pattern ceases, and incoming network traffic is passed through to the CSU device. If the CSU
device responds to the CSU loop-up pattern, it returns all data back toward the network. A
loop down pattern (0000100001…) is generated toward the CSU for 6 seconds when Data
Mode is selected. Only the Data Mode for the T1 under test may be selected. Selecting any
other option results in an error message.
CSU Loopback w/BERT
A CSU Loopback w/BERT enables the MX2810 to test the local T1 loop to the CSU using the
standard QRSS pseudorandom bit sequence. When CSU Loopback w/BERT is selected, the
MX2810 initiates a CSU loopback toward the CSU attached to the selected T1 line similar to
the CSU Loopback test. Within 6 seconds after starting the CSU loop up pattern, the MX2810
ceases sending the CSU loop up pattern and begins sending an unframed QRSS pattern
toward the CSU. If the CSU device responds to the CSU loop up pattern, the MX2810 checks
the incoming pattern for errors. Additional menu items appear that display the state of
pattern synchronization, error count, and a clear error count option. Selecting Data Mode
stops the transmission of the QRSS pattern and starts transmission of a loop down pattern.
Only the Data Mode for the T1 under test may be selected. Selecting any other option results
in an error message.
Line BERT
A Line BERT enables the MX2810 to perform a “head-to-head” BERT test toward the CSU.
Selecting Line BERT replaces all incoming network traffic for the selected T1 with an
unframed QRSS pattern toward the CSU. When Line BERT is selected, additional menu items
appear that display the state of pattern synchronization, cumulative error count, and a clear
error count option. Selecting Data Mode stops QRSS pattern generation and substitution of
the incoming data stream. Only one T1 port may engage a CSU Loopback, CSU Loopback w/
BERT, or a Line BERT. If one test is already active when a new test is selected, the former test
is terminated, and the latter is engaged.
DS3 Loopbacks
Line Loopback
Line Loopback performs a loop of the DS3 back to the network. This loopback occurs just
prior to the DS3 framer and B8ZS decoder, but it makes full use of the DS3 LIU in both
receive and transmit directions; therefore, any coding violations received by the DS3 is
inserted back into the network without modification. If a line loopback is active when the
MX2810 is operating in the Local timing mode, the timing source for the DS3 is effectively
removed from the circuit. Therefore, it is up to the test equipment or network to provide DS3
timing into the circuit for the duration of the test.
Digital Diagnostics
A Digital Diagnostic 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
24
61185002L2-5C
Loopbacks
from a DS3. The incoming DS3 data is ignored, and the outgoing DS3 stream is substituted
just prior to exiting the DS3 framer.
Network Loopback
A Network Loopback test 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, and passed through both directions of the DS3 LIU. During this test, the incoming DS3
is disconnected from the DS3 receiver, and the outgoing DS3 signal is substituted.
Remote Loopback
A Remote Loopback performs a loopback on the far-end M13 multiplexer. If an MX2810 is
located at the far end, a Live Loopback is executed when a Remote Loopback is engaged. This
loopback is only available when the DS3 is configured for C-bit parity framing since it requires
the availability of the FEAC channel.
Remote All T1/E1
A Remote All T1/E1 loopback performs a loopback of all T1/E1 channels on the far-end M13
multiplexer. If an MX2810 is located at the far end, an Analog Diagnostic loopback is executed
on all active channels simultaneously. Since this loopback requires the availability of the
FEAC channel, it is only available when the DS3 is configured for C-bit parity framing.
DS2 Loopbacks
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 receives data
normally, but all data inserted into the T1/E1s attached to the selected DS2 is ignored and
replaced by the incoming DS2 network data.
61185002L2-5C
25
MX2810 Controller Module Installation and Maintenance Practice
FRONT PANEL INDICATORS
The MX2810 CCU has LED status indicators. The status LEDs provided are ACT (active), DS3,
ALM (alarm), and PRF (performance). Different conditions are indicated by the state of the
LED (its color and whether it flashes, alternates color, or is on solid).
The condition descriptions vary depending on whether the LED represents the active
controller card or the controller card on standby. The following tables provide LED definitions
for the active (Table 17) and standby (Table 18) cards.
Table 17. Status LED Conditions for Active Cards
Alarm
LED State
ACT
Green Solid
Green/Amber Alternating
Red Solid
Amber Solid
Red/Amber Alternating
Red Flashing
DS3
Green Solid
Red Flashing
Red Solid
Amber Solid
Amber Flashing
Red/Amber Alternating
ALM
Green Solid
Red Flashing
PRF
Normal (All OK)
Normal + console open
Self-test failed
Software update in progress
Self-test failed + console open
Card failure
Normal (All OK)
LOS, TLOS
AIS, LOF, RAI, Idle Alarms
In test (local)
In test (remote)
In test with alarms
Normal (No alarm)
Critical Alarm
Red Solid
(Major)
Amber Flashing
(Minor)
Amber Solid
Alarm suppressed (ACO button was pushed)
Green Solid
Normal (All OK)
Red Flashing (once per
event)
Red Flashing
Red Solid
26
Card Condition
Single/Burst DS3 code violations
Continuous DS3 code violations
DS3 XCV threshold exceeded
61185002L2-5C
Front Panel Indicators
Table 18. Status LED Conditions for Standby Cards
Alarm
LED State
ACT
Green Flashing
Amber Solid
Red Flashing
DS3
Off
Red Flashing
Card Condition
Normal (All OK)
Software update in progress
Self-test failed
Normal (All OK)
DS3 Failure
ALM
Off
Normal (No Alarm)
PRF
Off
Normal (All OK)
The Status DSX-1 LEDs apply to each individual T1 or E1. Different conditions are indicated
by the state of the LED (its color and whether it flashes, alternates color, or is on solid). The
condition descriptions vary depending on whether the LEDs represent T1s or E1s of the active
controller card or the controller card on standby.
Table 19 provides LED descriptions for DSX-1 LEDs on the active and standby cards.
Table 19. DSX-1 LED Conditions
Alarm
LED State
Active
Card
Green Solid
Off
Red Flashing
Red Flash (once per each
event)
Red Solid
Amber Solid
Amber Flashing
Red/Amber Alternating
Standby
Card
Off
Red Flashing
61185002L2-5C
Card Condition
Normal (All OK)
Disabled
LOS
Single/Burst CV
XCV Threshold Exceeded or AIS/CAIS
In Test (local)
In Test (remote)
In test + Alarm
Normal (All OK) or N/A
(in case of E1 configuration)
T1/E1 failure
27
MX2810 Controller Module Installation and Maintenance Practice
Alarm Outputs
The CCU determines alarm states and reports these results via onboard alarm interfaces.
Each of the alarm contacts provide common and normally open functionality. Physical access
to the relay contacts is attained by way of two wire-wrap posts for each of the three alarm
functions located on the rear panel of the MX2810 chassis. The supported alarm functions
are:
• Critical (CRI)
• Major (MAJ)
• Minor (MIN)
The CCU provides front panel indicators to indicate the status of the MX2810 and Alarm Cut
Off (ACO) state.
ACO Buttons
The ACO (alarm cut off) button will allow suppression of an active audible alarm. Once the
ACO button is pressed, the audible alarm remains disabled until a new alarm is activated.
MAINTENANCE
The System Name MX2810 Controller Module does not require routine maintenance for
normal operation.
ADTRAN does not recommend that repairs be attempted in the field. Repair services may be
obtained by returning the defective unit to ADTRAN. Refer to the “Appendix A, Warranty”
section for further information.
28
61185002L2-5C
Specifications
SPECIFICATIONS
Specifications for the System Name MX2810 Controller Module are detailed in Table 20.
Table 20. MX2810 Controller Module Specifications
Environmental
Operating Temperature:
–40°C to +65°C
Storage Temperature:
–40°C to +85°C
Relative Humidity:
Maximum Current Draw:
Maximum Heat Dissipation:
95 percent maximum @ 50°C, noncondensing
0.025 A maximum @ –48VDC
1.21 watts
Physical
Dimensions:
Weight:
Height: .75 inch
Width: 10.867 inches
Depth: 7.75 inches
.80 pound
Part Number
MX2810 Controller Module:
61185002L2-5C
1185002L1
1185002L2
29
MX2810 Controller Module Installation and Maintenance Practice
This page is intentionally blank.
30
61185002L2-5C
Appendix A
Warranty
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.
Refer to the following subsections for sales, support, Customer and Product Service (CAPS)
requests, or further information.
ADTRAN Sales
Pricing/Availability:
800-827-0807
ADTRAN Technical Support
Pre-Sales Applications/Post-Sales Technical Assistance:
800-726-8663
Standard hours: Monday - Friday, 7 a.m. - 7 p.m. CST
Emergency hours: 7 days/week, 24 hours/day
ADTRAN Repair/CAPS
Return for Repair/Upgrade:
(256) 963-8722
Repair and Return Address
Contact CAPS prior to returning equipment to ADTRAN.
ADTRAN, Inc.
CAPS Department
901 Explorer Boulevard
Huntsville, Alabama 35806-2807
61185002L2-5C
A-1
®
Carrier Networks Division
901 Explorer Blvd.
Huntsville, AL 35806
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising