Professional Documents
Culture Documents
STAT ALM DS3M3E DS3M3E ETHM8 O3TMIR MS BLANK OMM12VIR OMM12VIR DS1VME DS1VME O3TMLR MS BLANK TRAM3 TRAM3
1184533L2 1184533L2 1184524L1 1184543L1 1184505L1 1184504L3 1184504L3 1184515L2 1184515L2 1184543L2 1184505L1 1184532L1 1184532L1
SCM STATUS STATUS STATUS E 11
E STATUS STATUS STATUS STATUS STATUS STATUS STATUS STATUS
1184500L1
N N
ALARM ALARM ALM E E ALARM ALARM ALARM ALARM ALARM ALARM
T T
ALARM ALARM
1 2 2
ON LINE ON LINE TEST ONLINE ONLINE ONLINE ON LINE ON LINE ONLINE ON LINE ON LINE
3
E E
TEST TEST N N TEST TEST TEST TEST TEST TEST TEST TEST
E E
T T
3
4 4
E 5 E
N N
E E
ACO HST T T
5 6
6
E 7 E
N
E N
T E
7 T
8 8
ACT/
LNK
OPTI-6100
Maintenance and Troubleshooting Practice
Document Part Number: 61184500L1-6J
May, 2007
OPTI-6100 Maintenance and Troubleshooting Practice
Trademarks
Front Matter
Any brand names and product names included in this document are trademarks, registered
trademarks, or trade names of their respective holders.
ii 61184500L1-6J
Revision History
The history of this document is as follows:
61184500L1-6J iii
OPTI-6100 Maintenance and Troubleshooting Practice
Conventions
The following typographical conventions are used in this document:
This font indicates a cross-reference link.
This font indicates screen menus, fields, and parameters.
THIS FONT indicates keyboard keys (ENTER, ESC, ALT). Keys that are to be pressed simulta-
neously 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 silk-screen 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 dis-
ruption to equipment, software, or environment.
WARNING
Warnings inform the user of potential bodily pain, injury, or death.
Metric Conversion
The OPTI-6100 is designed to fit standard 19-inch and 23-inch racks, occupying 2U of vertical
space. The following metric conversions apply:
• 19 inches = 482 millimeters
• 23 inches = 584 millimeters
• 1U (1.75 inches) = 44.5 millimeters
• 2U (3.5 inches) = 89 millimeters
Other measurements are listed in metric and standard notations, where applicable.
iv 61184500L1-6J
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 more information about training, please contact ADTRAN at:
Training Phone: 800-615-1176, ext. 6996
Training Fax: 256-963-6217
Training Email: training@adtran.com
61184500L1-6J v
OPTI-6100 Maintenance and Troubleshooting Practice
vi 61184500L1-6J
Contents
General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1
Alarm Response Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Remote [Menus through Telnet]: (requires IP connectivity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Remote [TL-1 through Telnet or Rlogin] (requires IP or OSI connectivity) . . . . . . . . . . . . . . . . . . . . . . . . . 4
Understanding AIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Equipment AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Facility AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Path AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Environmental AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Clock AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Login Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
System Controller Module (SCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
OMM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
OMM3 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
OMM12 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
OMM48 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Tributary Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
DS1M Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
DS1M2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
DS1VM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
DS1VME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
DS1VMT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
DS1VM2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
DS3EC1M Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
DS3EC1M3 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
DS3M3E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
DS3M3T Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
ETHM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
ETHM2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
ETHM8 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
61184500L1-6J vii
OPTI-6100 Maintenance and Troubleshooting Practice
ETHM8-2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
ETHM8E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
ETHM8EH Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
TRAM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
TRAM3 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
O3TMIR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
O3TMLR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
O3TMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
O3TME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
O12TME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
GECM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
GESM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
GEMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
GEFM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
GEFMEH Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Cross-Connect Module (OMMXCV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Fan Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
FANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
EFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
HFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
SFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
Connect and Logon to System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Connecting through a VT100 Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
General Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
UPSR Ring Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Provisioning a DS1 Circuit Through a UPSR Ring (VT1.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Provisioning a DS1 Circuit Through a UPSR Ring (DS3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Provisioning a DS3 Circuit Through a UPSR Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Provisioning an OC-3 Circuit Through a UPSR Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Element Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
TL1-Encapsulated Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Management Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
Management Application Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
IP Route Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Default Route Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
Interface Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
IP Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
IP Services and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
OSI Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
TID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
DCC Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
DCC Link Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
NSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
Area Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
viii 61184500L1-6J
Contents
System ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
OSI Routing and Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
GNE – TL1 Translation Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Fujitsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Lucent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Nortel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Cisco and Turin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
OSI Remote Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
Neighbors Display Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
Login Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
IP Over OSI Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
IP Over OSI Tunnel Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
IP Over OSI Tunnel Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
IP Over OSI Tunnel – Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Step-By-Step Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
IP Over OSI Tunnel – Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
Step-By-Step Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
IP Over DCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
Central Office/Remote Terminal Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Enabling Central Office/Remote Terminal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
Remote Terminal Alarm Reporting at the Central Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
IP Access to the Remote Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
Operation With the OPTI-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Operation With the Total Access 3000/3010 (OC-3 L5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Upgrade SCM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Upgrade OMM Module Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Cross-Copy OMM Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
Upgrade Tributary Module Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Cross-Copy Tributary Module Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Security Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
Users Currently Logged On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Edit User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Create New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
Enable Technical Support Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Enable SNMP Security Account Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Lock-Out User on Login Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Case-Sensitive Password/User-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Null Password Accepted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Enable Lock-Out Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Number of Login Failure Before Lock-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Lock-Out Duration in Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Enable Advisory Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
61184500L1-6J ix
OPTI-6100 Maintenance and Troubleshooting Practice
x 61184500L1-6J
Contents
61184500L1-6J xi
OPTI-6100 Maintenance and Troubleshooting Practice
xii 61184500L1-6J
Contents
61184500L1-6J xiii
OPTI-6100 Maintenance and Troubleshooting Practice
Appendix A
Alarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
Alarms by Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2
Appendix B
Service States Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Suffixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Service States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2
Facility States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3
Path States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4
VT States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5
DCC States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6
Appendix C
Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Summary of Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Appendix D
Warranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Warranty and Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
ADTRAN Sales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
ADTRAN Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
ADTRAN Repair/CAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
Repair and Return Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1
xiv 61184500L1-6J
Figures
Figures
61184500L1-6J xv
OPTI-6100 Maintenance and Troubleshooting Practice
xvi 61184500L1-6J
Figures
61184500L1-6J xvii
OPTI-6100 Maintenance and Troubleshooting Practice
xviii 61184500L1-6J
Tables
Tables
61184500L1-6J xix
OPTI-6100 Maintenance and Troubleshooting Practice
xx 61184500L1-6J
OPTI-6100
GENERAL
This practice is a Maintenance and Troubleshooting guide for the ADTRAN OPTI-6100 System,
MX and SMX chassis. In places where specifications differ between the two chassis, both are
referenced individually.
Overview
The OPTI-6100 consists of a chassis, Optical Multiplexer Modules (OMM), tributary modules,
and a System Controller Module (SCM). The OMM modules provide the network interface,
while the tributary modules provide the service distribution interfaces.
Figure 1 shows a block diagram of the OPTI-6100 system MX chassis.
OC-3/12/48 HS1
BITS
OC-3/12/48 HS2
SCM MS1 MS2 MS3 MS4 MS5 MS6 MS7 MS8 MS9 MS10 MS11 MS12
I/0 Craft
Enet 6 x BNC 2 x Champ 6 x BNC 2 x Champ 2 x Champ 6 x BNC
X.25 DS3 DS1 DS3 6 x BNC DS1 DS3
Admin EC1 OC-3 EC1 OC-3 EC1
RS-485 OC-3 OC-12 OC-3 DS3 OC-12 OC-3
OC-12 OC-12 EC1 OC-12
DS1
OC-3
OC-12
61184500L1-6J 1
OPTI-6100 Maintenance and Troubleshooting Practice
OC-3/12 HS1
BITS
OC-3/12 HS2
I/0 Craft
Enet 6 x BNC 2 x Champ
X.25
Admin DS3 6 x BNC
RS-485 EC1 DS3
OC-3 EC1
DS1
OC-3
The only routine maintenance required of the system is for a periodic fan filter replacement in
those cases where a fan assembly is used. Troubleshooting normally consists of replacement
of failed modules. All settings on the OPTI-6100 are provisionable through software; there are
no manual configuration switches.
The OPTI-6100 includes a user interface to the system through remote TL1, SNMP, and craft
menus, which can be accessed either through the craft port locally, or through Telnet session
remotely.
NOTE
Ethernet and OC-3/12 tributary modules use front panel connec-
tions and can be installed in any MS slot.
2 61184500L1-6J
General
Local
1. Visually inspect the LEDs for alarm indications. For information, refer to “LEDs” on
page 8.
2. Login through the craft port (for information, refer to “Connect and Logon to System” on
page 78).
3. Check for information regarding standing alarms:
a. From the OPTI-6100 Main menu, select System Alarms, and press ENTER.
b. From the System Alarms menu, select Shelf Alarm Status, and press ENTER.
c. From the Shelf Alarm Status menu, select a module in alarm, and press ENTER.
61184500L1-6J 3
OPTI-6100 Maintenance and Troubleshooting Practice
Understanding AIDs
OPTI-6100 AIDs have a structure that identifies equipment, facility, path, clock or environ-
mental input associated with an alarm. Types of AIDs include:
• An equipment AID is shown for alarms or conditions associated with a circuit pack.
• A facility AID is shown for alarms or conditions associated with a facility (e.g., DS3, DS1,
OC-3).
• A path AID is shown for alarms or conditions associated with paths on the SONET
interface.
• An environmental AID is shown for environmental inputs (AUX 1 through AUX 3, or
Enhanced Fan Pack inputs). The chassis # used in the AID identifies the system, when
multiple systems are managed over the RS-485 bus.
4 61184500L1-6J
General
Examples:
1-SCM (System controller module)
1-HS1 (High-speed HS1)
1-MS6 (Mid-speed MS6)
Examples:
1-HS1-1 (High-speed HS1–port 1)
1-MS2-2 (Mid-speed MS2–port 2)
3-MS6-1 (Chassis #3–mid-speed MS6–port1)
NOTE
For OC-3 interfaces, which have only one STS-3, the STS-3 # is
always “1.”
Examples:
1-HS1-STS-1 (High-speed HS1–STS-3 #1)
1-HS1-STS-1-2 (High-speed HS1–STS-3 #1–STS-1 #2)
1-HS2-STS-3-2-1 (High-speed HS2–STS-3 #3–STS-1 #2–VT #1)
1-HS1-STS-1-3-4 (High-speed HS1–STS-3 #1–STS-1 #3–VT #4)
1-HS1-STS-3 (High-speed HS1–STS-3 #3)
1-MS7-2 (Mid-speed MS7–DS1 #2)
61184500L1-6J 5
OPTI-6100 Maintenance and Troubleshooting Practice
6 61184500L1-6J
Login Failure
LOGIN FAILURE
If an account is accidentally deleted or disabled, or if a password is lost or forgotten, access to
the OPTI-6100 system can be regained through the Technical Support Challenge Key
Response.
Enter CHALLENGE as the username at login. This results in a Challenge Key being provided; a
correct Response Key (provided by ADTRAN Technical Support) must then be supplied. With
the correct Response Key, users gain ADMIN-level access to the system. With the correct
Response Key, ADMIN-level access to the system is enabled.
CAUTION
The Challenge Key response provided by ADTRAN Technical Sup-
port is only valid for one session. At this time, security account
maintenance must be completed with the appropriate accounts
and passwords prior to logging out of the system.
By default, this feature is Disabled. Enable this feature using the Enable Technical Support
Account option. Refer to “Enable Technical Support Account” on page 133.
61184500L1-6J 7
OPTI-6100 Maintenance and Troubleshooting Practice
LEDS
Each of the modules in the OPTI-6100 is equipped with LEDs that provide information as to
the status of the module and system. This section describes the LEDs on each module and
describes the different indications.
SCM
1184500L1
ALARM
STATUS
C
R
A
F
T
ACO HST
At power up of the chassis or the insertion of the SCM into the OPTI-6100, all LEDs illuminate
red, then yellow, then green. Next the LEDs cycle from top to bottom until the self-test is
complete. After a few seconds, all LEDs reflect the true state of the module and system.
8 61184500L1-6J
LEDs
Green SCM is in Host mode SCM can access other systems daisy
chained through RS-485 interface
ACO Off Alarm Cut Off not activated External audible alarms are active, if
so equipped
61184500L1-6J 9
OPTI-6100 Maintenance and Troubleshooting Practice
OMM Modules
OMM3 Modules
All OMM3 modules (see Figure 5) are equipped with four LEDs. At power up of the chassis or
the insertion of a module into the OPTI-6100, all LEDs illuminate red, then yellow, then green.
Next the LEDs may cycle from top to bottom until the self-test is complete. When the TEST
LED extinguishes, the self-test is complete and, after a few seconds, all LEDs reflect the true
state of the module and system.
OMM3LR
1184502L1
STATUS
ALARM
ON LINE
TEST
10 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off For 1+1 protection, Rx is not Not active
being dropped
61184500L1-6J 11
OPTI-6100 Maintenance and Troubleshooting Practice
OMM12 Modules
All OMM12 modules (see Figure 6) are each equipped with four LEDs. At power up of the
chassis or the insertion of a module into the OPTI-6100, all LEDs illuminate red, then yellow,
then green. Next the LEDs may cycle from top to bottom until the self-test is complete. When
the TEST LED extinguishes, the self-test is complete and, after a few seconds, all LEDs reflect
the true state of the module and system.
OMM12LR
1184504L1
STATUS
ALARM
ON LINE
TEST
12 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off For 1+1 protection, Rx is not Not active
being dropped
61184500L1-6J 13
OPTI-6100 Maintenance and Troubleshooting Practice
OMM48 Module
The OMM48 module (see Figure 7) is equipped with four LEDs. At power up of the chassis or
the insertion of a module into the OPTI-6100, all LEDs illuminate red, then yellow, then green.
Next the LEDs may cycle from top to bottom until the self-test is complete. When the TEST
LED extinguishes, the self-test is complete and, after a few seconds, all LEDs reflect the true
state of the module and system.
OMM48
1184548L1
STATUS
ALARM
ON LINE
TEST
14 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off For 1+1 protection, Rx is not Not active
being dropped
61184500L1-6J 15
OPTI-6100 Maintenance and Troubleshooting Practice
Tributary Modules
DS1M Module
The OPTI-6100 DS1 Tributary Module – M13 (DS1M, P/N 1184513L1) is equipped with four
LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all LEDs
illuminate red, then yellow, then green. Next the LEDs may cycle from top to bottom until the
self-test is complete. When the TEST LED extinguishes, the self-test is complete and, after a
few seconds, all LEDs reflect the true state of the module and system.
The DS1M module is illustrated in Figure 8.
DS1M
1184513L1
STATUS
ALARM
ONLINE
TEST
16 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 17
OPTI-6100 Maintenance and Troubleshooting Practice
DS1M2 Module
The OPTI-6100 DS1 Tributary Module – M13 (DS1M2, P/N 1184513L2) is equipped with four
LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all LEDs
illuminate red, then yellow, then green. Next the LEDs may cycle from top to bottom until the
self-test is complete. When the TEST LED extinguishes, the self-test is complete and, after a
few seconds, all LEDs reflect the true state of the module and system.
The DS1M2 module is illustrated in Figure 9.
DS1M2
1184513L2
STATUS
ALARM
ON LINE
TEST
18 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 19
OPTI-6100 Maintenance and Troubleshooting Practice
DS1VM Module
The OPTI-6100 DS1 Tributary Module – VT (DS1VM, P/N 1184515L1) is equipped with four
LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all LEDs
illuminate red, then yellow, then green. Next the LEDs may cycle from top to bottom until the
self-test is complete. When the TEST LED extinguishes, the self-test is complete and, after a
few seconds, all LEDs reflect the true state of the module and system.
The DS1VM module is illustrated in Figure 10.
DS1VM
1184515L1
STATUS
ALARM
ON LINE
TEST
20 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 21
OPTI-6100 Maintenance and Troubleshooting Practice
DS1VME Module
The OPTI-6100 DS1 Tributary Module – VT – Enhanced (DS1VME, P/N 1184515L2) is
equipped with four LEDs. At power up of the chassis or the insertion of a module into the
OPTI-6100, all LEDs illuminate red, then yellow, then green. Next the LEDs may cycle from
top to bottom until the self-test is complete. When the TEST LED extinguishes, the self-test is
complete and, after a few seconds, all LEDs reflect the true state of the module and system.
The DS1VME module is illustrated in Figure 11.
DS1VME
1184515L2
STATUS
ALARM
ON LINE
TEST
22 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 23
OPTI-6100 Maintenance and Troubleshooting Practice
DS1VMT Module
The OPTI-6100 DS1 Tributary Module – VT – Enhanced (DS1VMT, P/N 1184515L3) is
equipped with four LEDs. At power up of the chassis or the insertion of a module into the
OPTI-6100, all LEDs illuminate red, then yellow, then green. Next the LEDs may cycle from
top to bottom until the self-test is complete. When the TEST LED extinguishes, the self-test is
complete and, after a few seconds, all LEDs reflect the true state of the module and system.
The DS1VMT module is illustrated in Figure 11.
DS1VME
1184515L2
STATUS
ALARM
ON LINE
TEST
24 61184500L1-6J
LEDs
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 25
OPTI-6100 Maintenance and Troubleshooting Practice
DS1VM2 Module
The OPTI-6100 DS1 Tributary Module – VT (DS1VM2, P/N 1184515L4) is equipped with four
LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all LEDs
illuminate red, then yellow, then green. Next the LEDs may cycle from top to bottom until the
self-test is complete. When the TEST LED extinguishes, the self-test is complete and, after a
few seconds, all LEDs reflect the true state of the module and system.
The DS1VM2 module is illustrated in Figure 13.
DS1VM2
1184515L4
STATUS
ALARM
ON LINE
TEST
26 61184500L1-6J
LEDs
Descriptions of the LEDs on the DS1VM2 module are provided in Table 10.
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 27
OPTI-6100 Maintenance and Troubleshooting Practice
DS3EC1M Module
The OPTI-6100 DS3/EC1 Tributary Module (DS3EC1M, P/N 1184503L1) is equipped with
four LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate red, then yellow, then green. Next the LEDs may cycle from top to bottom
until the self-test is complete. When the TEST LED extinguishes, the self-test is complete and,
after a few seconds, all LEDs reflect the true state of the module and system.
The DS3EC1M module is illustrated in Figure 14.
DS3EC1M
1184503L1
STATUS
ALARM
ON LINE
TEST
28 61184500L1-6J
LEDs
Descriptions of the LEDs on the DS3EC1M Module are provided in Table 11.
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 29
OPTI-6100 Maintenance and Troubleshooting Practice
DS3EC1M3 Module
The OPTI-6100 DS3/EC1 3-Port Tributary Module (DS3EC1M3, P/N 1184533L1) is equipped
with four LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate red, then yellow, then green. Next the LEDs may cycle from top to bottom
until the self-test is complete. When the TEST LED extinguishes, the self-test is complete and,
after a few seconds, all LEDs reflect the true state of the module and system.
The DS3EC1M3 module is illustrated in Figure 15.
DS3EC1M3
1184533L1
STATUS
ALARM
ON LINE
TEST
30 61184500L1-6J
LEDs
Descriptions of the LEDs on the DS3EC1M3 module are provided in Table 12.
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 31
OPTI-6100 Maintenance and Troubleshooting Practice
DS3M3E Module
The OPTI-6100 DS3/EC1 3-Port Tributary Module – Enhanced (DS3M3E, P/N 1184533L2) is
equipped with four LEDs. At power up of the chassis or the insertion of a module into the
OPTI-6100, all LEDs illuminate red, then yellow, then green. Next the LEDs may cycle from
top to bottom until the self-test is complete. When the TEST LED extinguishes, the self-test is
complete and, after a few seconds, all LEDs reflect the true state of the module and system.
The DS3M3E module is illustrated in Figure 16.
DS3M3E
1184533L2
STATUS
ALARM
ON LINE
TEST
32 61184500L1-6J
LEDs
Descriptions of the LEDs on the DS3M3E module are provided in Table 13.
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 33
OPTI-6100 Maintenance and Troubleshooting Practice
DS3M3T Module
The OPTI-6100 DS3/EC1 3-Port Tributary Module – Enhanced (DS3M3T, P/N 1184533L3) is
equipped with four LEDs. At power up of the chassis or the insertion of a module into the
OPTI-6100, all LEDs illuminate red, then yellow, then green. Next the LEDs may cycle from
top to bottom until the self-test is complete. When the TEST LED extinguishes, the self-test is
complete and, after a few seconds, all LEDs reflect the true state of the module and system.
The DS3M3T module is illustrated in Figure 17.
DS3M3T
1184533L3
STATUS
ALARM
ON LINE
TEST
34 61184500L1-6J
LEDs
Descriptions of the LEDs on the DS3M3T module are provided in Table 14.
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Tx is off
61184500L1-6J 35
OPTI-6100 Maintenance and Troubleshooting Practice
ETHM Module
The OPTI-6100 10/100 3-Port Ethernet Module (ETHM, P/N 1184510L1) is equipped with
seven LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate. When the self-test is complete, all LEDs reflect the true state of the module
and system.
The ETHM module is illustrated in Figure 18.
ETHM
1184510L1 STATUS
LNK
E
N
E
T
1
E
N
E
T
2
E
N
E
T
3
ACT
36 61184500L1-6J
LEDs
Descriptions of the LEDs on the ETHM Module are provided in Table 15.
61184500L1-6J 37
OPTI-6100 Maintenance and Troubleshooting Practice
ETHM2 Module
The OPTI-6100 10/100 3-Port Ethernet Module (ETHM2, P/N 1184510L2) is equipped with
seven LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate. When the self-test is complete, all LEDs reflect the true state of the module
and system.
The ETHM2 module is illustrated in Figure 19.
ETHM2
1184510L2 STATUS
LNK
E
N
E
T
1
E
N
E
T
2
E
N
E
T
3
ACT
38 61184500L1-6J
LEDs
Descriptions of the LEDs on the ETHM2 Module are provided in Table 16.
61184500L1-6J 39
OPTI-6100 Maintenance and Troubleshooting Practice
ETHM8 Module
The OPTI-6100 10/100 8-Port Ethernet Module (ETHM8, P/N 1184524L1) is equipped with
eleven LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate. When the TEST LED extinguishes, the self-test is complete and, after a few
seconds, all LEDs reflect the true state of the module and system.
The ETHM8 module is illustrated in Figure 20.
ETHM8
1184524L1
STATUS E 1
E
N N
ALM E E
T T
1 2 2
TEST
3
E E
N N
E E
T T
3 4 4
E 5 E
N N
E E
T T
5 6
6
E 7 E
N
E N
T E
7 T
8 8
ACT/
LNK
40 61184500L1-6J
LEDs
Descriptions of the LEDs on the ETHM8 module are provided in Table 17.
61184500L1-6J 41
OPTI-6100 Maintenance and Troubleshooting Practice
ETHM8-2 Module
The OPTI-6100 10/100 8-Port Ethernet Module (ETHM8-2, P/N 1184524L2) is equipped with
eleven LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate. When the TEST LED extinguishes, the self-test is complete and, after a few
seconds, all LEDs reflect the true state of the module and system.
The ETHM8-2 module is illustrated in Figure 21.
ETHM8-2
1184524L2
STATUS E 1
E
N N
ALM E E
T T
1 2 2
TEST
3
E E
N N
E E
T T
3 4 4
E 5 E
N N
E E
T T
5 6
6
E 7 E
N
E N
T E
7 T
8 8
ACT/
LNK
42 61184500L1-6J
LEDs
Descriptions of the LEDs on the ETHM8-2 module are provided in Table 18.
61184500L1-6J 43
OPTI-6100 Maintenance and Troubleshooting Practice
ETHM8E Module
The OPTI-6100 10/100 8-Port Ethernet Module – Enhanced (ETHM8E, P/N 1184525L1) is
equipped with eleven LEDs. At power up of the chassis or the insertion of a module into the
OPTI-6100, all LEDs illuminate. When the TEST LED extinguishes, the self-test is complete
and, after a few seconds, all LEDs reflect the true state of the module and system.
The ETHM8E module is illustrated in Figure 22.
ETHM8E
1184525L1
STATUS E 1
E
N N
ALM E E
T T
1 2 2
TEST
3
E E
N N
E E
T T
3 4 4
E 5 E
N N
E E
T T
5 6
6
E 7 E
N
E N
T E
7 T
8 8
ACT/
LNK
44 61184500L1-6J
LEDs
Descriptions of the LEDs on the ETHM8E module are provided in Table 19.
61184500L1-6J 45
OPTI-6100 Maintenance and Troubleshooting Practice
ETHM8EH Module
The OPTI-6100 10/100 8-Port Ethernet Module, Enhanced, High-Capacity (ETHM8EH,
P/N 1184545L1) is equipped with eleven LEDs. At power up of the chassis or the insertion of
a module into the OPTI-6100, all LEDs illuminate. When the TEST LED extinguishes, the self-
test is complete and, after a few seconds, all LEDs reflect the true state of the module and
system.
The ETHM8EH module is illustrated in Figure 23.
ETHM8EH
1184545L1
STATUS E 1
E
N N
ALM E E
T T
1 2 2
TEST
3
E E
N N
E E
T T
3 4 4
E 5 E
N N
E E
T T
5 6
6
E 7 E
N
E N
T E
7 T
8 8
ACT/
LNK
46 61184500L1-6J
LEDs
Descriptions of the LEDs on the ETHM8EH module are provided in Table 20.
61184500L1-6J 47
OPTI-6100 Maintenance and Troubleshooting Practice
TRAM Module
The OPTI-6100 Transmux Tributary Module (TRAM, P/N 1184512L1) is equipped with four
LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all LEDs
illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom several
more times during the self-test. The TEST LED extinguishes when the self-test is complete.
After a few seconds the LEDs indicate the correct status of the module.
The TRAM module is illustrated in Figure 24.
TRAM
1184512L1
STATUS
ALARM
ON LINE
TEST
48 61184500L1-6J
LEDs
Descriptions of the LEDs on the TRAM module are provided in Table 21.
61184500L1-6J 49
OPTI-6100 Maintenance and Troubleshooting Practice
TRAM3 Module
The OPTI-6100 Triple Transmux Tributary Module (TRAM3, P/N 1184532L1) is equipped with
four LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom
several more times during the self-test. The TEST LED extinguishes when the self-test is
complete. After a few seconds the LEDs indicate the correct status of the module.
The TRAM3 module is illustrated in Figure 25.
TRAM3
1184532L1
STATUS
ALARM
ON LINE
TEST
50 61184500L1-6J
LEDs
Descriptions of the LEDs on the TRAM3 module are provided in Table 22.
61184500L1-6J 51
OPTI-6100 Maintenance and Troubleshooting Practice
O3TMIR Module
The OPTI-6100 OC-3 IR Tributary Module (O3TMIR, P/N 1184543L1) is equipped with four
LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all LEDs
illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom several
more times during the self-test. The TEST LED extinguishes when the self-test is complete.
After a few seconds the LEDs indicate the correct status of the module.
The O3TMIR module is illustrated in Figure 26.
O3TMIR
1184543L1
STATUS
ALARM
ONLINE
TEST
52 61184500L1-6J
LEDs
Descriptions of the LEDs on the O3TMIR module are provided in Table 23.
61184500L1-6J 53
OPTI-6100 Maintenance and Troubleshooting Practice
O3TMLR Module
The OPTI-6100 OC-3 LR Tributary Module (O3TMLR, P/N 1184543L2) is equipped with four
LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all LEDs
illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom several
more times during the self-test. The TEST LED extinguishes when the self-test is complete.
After a few seconds the LEDs indicate the correct status of the module.
The O3TMLR module is illustrated in Figure 27.
O3TMLR
1184543L2
STATUS
ALARM
ONLINE
TEST
54 61184500L1-6J
LEDs
Descriptions of the LEDs on the O3TMLR module are provided in Table 24.
61184500L1-6J 55
OPTI-6100 Maintenance and Troubleshooting Practice
O3TMM Module
The OPTI-6100 OC-3 Multi-Mode Tributary Module (O3TMM, P/N 1184543L3) is equipped
with four LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom
several more times during the self-test. The TEST LED extinguishes when the self-test is
complete. After a few seconds the LEDs indicate the correct status of the module.
The O3TMM module is illustrated in Figure 28.
O3TMM
1184543L3
STATUS
ALARM
ONLINE
TEST
56 61184500L1-6J
LEDs
Descriptions of the LEDs on the O3TMM module are provided in Table 25.
61184500L1-6J 57
OPTI-6100 Maintenance and Troubleshooting Practice
O3TME Module
The OPTI-6100 OC-3 Tributary Module – Enhanced (O3TME, P/N 1184543L4) is equipped
with four LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom
several more times during the self-test. The TEST LED extinguishes when the self-test is
complete. After a few seconds the LEDs indicate the correct status of the module.
The O3TME has three operational modes, each dependent on the insertion of a different Small
Form-factor Pluggable (SFP) into a connector on the circuit board.
The O3TME module is illustrated in Figure 29.
O3TME
1184543L4
STATUS
ALARM
ONLINE
TEST
58 61184500L1-6J
LEDs
Descriptions of the LEDs on the O3TME module are provided in Table 26.
61184500L1-6J 59
OPTI-6100 Maintenance and Troubleshooting Practice
O12TME Module
The OPTI-6100 OC-12 Tributary Module – Enhanced (O12TME, P/N 1184544L1) is equipped
with four LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom
several more times during the self-test. The TEST LED extinguishes when the self-test is
complete. After a few seconds the LEDs indicate the correct status of the module.
The O12TME has three operational modes, each dependent on the insertion of a different
Small Form-factor Pluggable (SFP) into a connector on the circuit board.
The O12TME module is illustrated in Figure 30.
O12TME
1184544L1
STATUS
ALARM
ONLINE
TEST
60 61184500L1-6J
LEDs
Descriptions of the LEDs on the O12TME module are provided in Table 27.
61184500L1-6J 61
OPTI-6100 Maintenance and Troubleshooting Practice
GECM Module
The OPTI-6100 Gigabit Ethernet Copper Tributary Module (GECM, P/N 1184516L1) is
equipped with four LEDs. At power up of the chassis or the insertion of a module into the
OPTI-6100, all LEDs illuminate red, then yellow, then green. After that, the LEDs cycle from
top to bottom several more times during the self-test. The STATUS LED extinguishes when the
self-test is complete. After a few seconds the LEDs indicate the correct status of the module.
The GECM module is illustrated in Figure 31.
GECM
1184516L1
STATUS LINK
TX RX
GigE
62 61184500L1-6J
LEDs
Descriptions of the LEDs on the GECM module are provided in Table 28.
61184500L1-6J 63
OPTI-6100 Maintenance and Troubleshooting Practice
GESM Module
The OPTI-6100 Gigabit Ethernet Single-Mode Fiber Tributary Module (GESM,
P/N 1184518L1) is equipped with four LEDs. At power up of the chassis or the insertion of a
module into the OPTI-6100, all LEDs illuminate red, then yellow, then green. After that, the
LEDs cycle from top to bottom several more times during the self-test. The STATUS LED extin-
guishes when the self-test is complete. After a few seconds the LEDs indicate the correct
status of the module.
The GESM module is illustrated in Figure 32.
GESM
1184518L1
STATUS
LINK
TX
RX
64 61184500L1-6J
LEDs
Descriptions of the LEDs on the GESM module are provided in Table 29.
61184500L1-6J 65
OPTI-6100 Maintenance and Troubleshooting Practice
GEMM Module
The OPTI-6100 Gigabit Ethernet Multi-Mode Fiber Tributary Module (GEMM, P/N 1184519L1)
is equipped with four LEDs. At power up of the chassis or the insertion of a module into the
OPTI-6100, all LEDs illuminate red, then yellow, then green. After that, the LEDs cycle from
top to bottom several more times during the self-test. The STATUS LED extinguishes when the
self-test is complete. After a few seconds the LEDs indicate the correct status of the module.
The GEMM module is illustrated in Figure 33.
GEMM
1184519L1
STATUS
LINK
TX
RX
66 61184500L1-6J
LEDs
Descriptions of the LEDs on the GEMM module are provided in Table 30.
61184500L1-6J 67
OPTI-6100 Maintenance and Troubleshooting Practice
GEFM Module
The OPTI-6100 Gigabit Ethernet Over PDH Fiber Module (GEFM, P/N 1184535L1) is equipped
with five LEDs. At power up of the chassis or the insertion of a module into the OPTI-6100, all
LEDs illuminate red, then yellow, then green. After that, the LEDs cycle from top to bottom
several more times during the self-test. The STATUS LED extinguishes when the self-test is
complete. After a few seconds the LEDs indicate the correct status of the module.
The GEFM module is illustrated in Figure 34.
GEFM
1184535L1
STATUS
ALARM
ONLINE
LINK
ACT
68 61184500L1-6J
LEDs
Descriptions of the LEDs on the GEFM module are provided in Table 31.
61184500L1-6J 69
OPTI-6100 Maintenance and Troubleshooting Practice
GEFMEH Module
The OPTI-6100 Gigabit Ethernet Fiber Module, Enhanced, High-Capacity (GEFMEH,
P/N 1184546L1) is equipped with six LEDs. At power up of the chassis or the insertion of a
module into the OPTI-6100, all LEDs illuminate red, then yellow, then green. After that, the
LEDs cycle from top to bottom several more times during the self-test. The STATUS LED extin-
guishes when the self-test is complete. After a few seconds the LEDs indicate the correct
status of the module.
The GEFMEH module is illustrated in Figure 35.
GEFMEH
1184546L1
STATUS LINK
ALM TX
TEST RX
70 61184500L1-6J
LEDs
Descriptions of the LEDs on the GEFMEH module are provided in Table 32.
61184500L1-6J 71
OPTI-6100 Maintenance and Troubleshooting Practice
OMMXCV
1184536L1
STATUS
ALARM
ON LINE
TEST
72 61184500L1-6J
LEDs
Descriptions of the LEDs on the OMMXCV module are provided in Table 33.
Red LOS or other hard alarms that Go to System Alarms screen for
indicate a facility problem details
ONLINE Off Module is offline Rx is not being dropped
61184500L1-6J 73
OPTI-6100 Maintenance and Troubleshooting Practice
Fan Assemblies
FANM Assembly
The FANM Assembly (Figure 37) is equipped with two LEDs.
PWR=GRN
SFAN=YEL
FANM
1184507L1
MFAN
Descriptions of the LEDs on the FANM Assembly are provided in Table 34.
Yellow Single fan or power failure The fan assembly contains multiple
fans. If one fan fails, the assembly
can possibly remain in operation.
MTAN Off Power up and initialization OK
Red Multiple fan or power failure More than one fan has failed, or A
May also indicate loss of com- and B power has failed.
munication with fan module
74 61184500L1-6J
LEDs
EFANM Assembly
The EFANM Assembly (Figure 38) is equipped with a single LED.
STATUS EFANM
1184507L2
Descriptions of the LED indications on the EFANM Assembly are provided in Table 35.
Yellow Single fan or power failure The fan assembly contains multiple
fans. If one fan fails, the assembly
can possibly remain in operation.
Red Multiple fan or power failure More than one fan has failed, or A
May also indicate loss of com- and B power has failed.
munication with fan module
61184500L1-6J 75
OPTI-6100 Maintenance and Troubleshooting Practice
HFANM Assembly
The HFANM Assembly (Figure 39) is equipped with two LEDs.
Descriptions of the LEDs on the HFANM Assembly are provided in Table 36.
Yellow Single fan or power failure The fan assembly contains multiple
fans. If one fan fails, the assembly
can possibly remain in operation.
LED 2 Off Power up and initialization OK
Red Multiple fan or power failure More than one fan has failed, or A
May also indicate loss of com- and B power has failed.
munication with fan module
76 61184500L1-6J
LEDs
SFANM Assembly
The SFANM Assembly (Figure 40) is equipped with a single LED.
STATUS
Descriptions of the LED indications on the SFANM Assembly are provided in Table 37.
Yellow Single fan or power failure The fan assembly contains multiple
fans. If one fan fails, the assembly
can possibly remain in operation.
Red Multiple fan or power failure More than one fan has failed, or A
May also indicate loss of and B power has failed.
communication with fan
module
61184500L1-6J 77
OPTI-6100 Maintenance and Troubleshooting Practice
NOTE
The SCM craft port is defaulted to 9600 baud but has additional
available baud rates of 19200, 38400, 57600, and 115200 baud. If
the craft baud rate is set to an unsupported value and no other
access method (Telnet, TL1, ADMIN, etc.) is available, the craft
baud rate can be restored by performing the following procedure:
1. Remove the SCM from the OPTI-6100.
2. Reinsert the SCM, holding the ACO pushbutton for 10 seconds.
3. Connect to the system.
4. Select Run Primary SCM Application (Flash), to exit Boot ROM mode.
2. When connecting a terminal to the craft port and the terminal has a parallel setting,
disable it and use serial. When connecting a PC emulating a VT100 terminal to the craft
port, set the PC for direct connect (as opposed to dial up connection).
3. When using the front craft port, use a serial cable with a male DB-9 connector on the
OPTI-6100 end.
4. Plug the male end of the data cable into the OPTI-6100. Make the connection to the VT100
terminal as appropriate for your equipment.
5. To log on to the OPTI-6100, press any key. The cursor appears in the Account Name field,
waiting for an account name to be input.
78 61184500L1-6J
Connect and Logon to System
NOTE
Logon names and passwords can be provisioned to be case sensi-
tive for additional security.
6. At the Account Name field, type the account name for the OPTI-6100, and press ENTER.
The cursor appears in the Password field, waiting for a password.
7. At the Password field, type the password for the OPTI-6100, and press ENTER.
8. On entering the correct password, the OPTI-6100 Main menu appears.
The OPTI-6100 menu system can now be accessed.
NOTE
If valid authentication information is not entered within one
minute, the Telnet session expires.
61184500L1-6J 79
OPTI-6100 Maintenance and Troubleshooting Practice
GENERAL PROVISIONING
Although much of the OPTI-6100 system is provisioned at the module level, there are
functions that can be provisioned at a system level.
80 61184500L1-6J
General Provisioning
x STS1 group 1 to 4
y STS1 instance 1 to 3
z VT1 instance 1 to 28
m DS1 instance 1 to 28
p DS3 instance 1 to 3
61184500L1-6J 81
OPTI-6100 Maintenance and Troubleshooting Practice
DS1
OPTI-6100 #1
provision DS1 cross copy
D
cross connect to S H H provisioning
1 S S
HS1 V
M 1 2 OMM12VIR to HS2
*3 *1 *3 *1*3 *1 *3
SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11 MS12
H H H H
S S S S
SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12 SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12
provision all
OPTI-6100 #4 provision all
pass through pass through
OPTI-6100 #2
traffic traffic
STS STS
VT VT
DS1
OPTI-6100 #3
82 61184500L1-6J
General Provisioning
NOTE
The DS3 facility must be provisioned prior to the DS1.
ENT-EQPT:[<TID>]:1-MSn:::[<CLEI>]::IS;
ENT-T3:[<TID>]:1-MSn-29:::[<CLEI>]::IS;
ENT-T1:[<TID>]:1-MSn-m:::[<CLEI>]::IS;
3. Provision the cross-connect on nodes 1 and 3.
ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-y,1-MSn-STS-1-1;
ENT-CRS-STS1::1-HS2-STS-x-y,1-MSn-STS-1-1;
4. Provision the cross-connect on nodes 2 and 4 to pass through the STS1.
ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-y,1-HS2-STS-x-y;
See Table 38 on page 81 for a key to the variables included.
61184500L1-6J 83
OPTI-6100 Maintenance and Troubleshooting Practice
DS1
OPTI-6100 #1
provision DS1 cross copy
D
cross connect to S H H provisioning
1 S S
HS1 M
1 2 OMM12VIR to HS2
*3 *1 *3 *1*3 *1 *3
SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11 MS12
H H H H
S S S S
SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12 SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12
provision all
OPTI-6100 #4 pass through
provision all
pass through
OPTI-6100 #2
traffic traffic
STS STS
VT VT
DS1
OPTI-6100 #3
84 61184500L1-6J
General Provisioning
61184500L1-6J 85
OPTI-6100 Maintenance and Troubleshooting Practice
DS3
OPTI-6100 #1
provision DS1 cross copy
cross connect to
T
R H H provisioning
A
M S S
HS1 1 2 OMM12VIR to HS2
*3 *1 *3 *1*3 *1 *3
SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11 MS12
H H H H
S S S S
SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12 SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12
provision DS1 T
cross copy
cross connect to R
A
H H provisioning
M S S
HS1 1 2 OMM12VIR to HS2
*3 *1 *3 *1*3 *1 *3
SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11 MS12
DS3
OPTI-6100 #3
86 61184500L1-6J
General Provisioning
61184500L1-6J 87
OPTI-6100 Maintenance and Troubleshooting Practice
OC3
OPTI-6100 #1
provision DS1 cross copy
O
cross connect to 3 H H provisioning
T S S
HS1 M
1 2 OMM12VIR to HS2
*3 *1 *3 *1*3 *1 *3
SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11 MS12
H H H H
S S S S
SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12 SCM MS1
*3
MS2
OMM12VIR
MS3
*1
MS4 MS5
*3
MS6
1 2 OMM12VIR
HS1 HS2 MS7
*1*3
MS8 MS9
*1
MS10 MS11
*3
MS12
OPTI-6100 #4 OPTI-6100 #2
provision all provision all
pass through pass through
traffic traffic
STS STS
VT VT
OC3
OPTI-6100 #3
88 61184500L1-6J
Element Management
ELEMENT MANAGEMENT
Element management is the means by which a system is provisioned, alarms and status are
monitored, and firmware is upgraded. The Total-Access Element Management System
(TA-EMS) is a GUI based EMS used to manage the OPTI-6100. Alternately, the OPTI-6100 can
be managed directly through one or more of its own management applications. Refer to
“Management Applications” (below).
NOTE
Some parameters associated with the provisioning of the element
management features are fixed or not accessible when the Mount
Location of the system is set to Central Office or Remote Terminal.
Setting the Mount Location to Central Office or Remote Terminal is
only appropriate for simple point-to-point applications as described
in “Central Office/Remote Terminal Applications” on page 122. For
flexibility in more complex or multi-vendor applications, the Mount
Location should be set to Subtended (default).
Management Applications
The OPTI-6100 supports the following management applications:
• Menus: ASCII based screens for simple menu driven management. Firmware downloads
may be done through the menu interface using the y-modem protocol.
• TL1 (Transaction Language 1): TL1 is a command-line language widely used in the
telecomm industry. TL1 is the only interoperable (with non-ADTRAN equipment)
application that the OPTI-6100 supports on the OSI network (the network protocol
traditionally used on the SONET Data Communications Channel (DCC)).
• SNMP: SNMP is a management protocol developed by the IP networking community.
• FTP/TFTP: FTP and TFTP are protocols used for file transfer. The OPTI-6100 uses file
transfer for software updates and to store the system provisioning on an external device for
backup through the system configuration archive (SCA) feature.
TL1-Encapsulated Applications
The OPTI-6100 supports two additional management applications that encapsulate their data
into TL1 commands and responses. This is done for the purpose of transporting the protocol
to and from remote network elements connected through an OSI network (traditionally used
as the management network on the SONET DCC).
These applications use a standard protocol for data transport (TL1), allowing them to be trans-
ported transparently through an OSI network. The encapsulation into TL1, however, is propri-
etary to ADTRAN and requires proprietary software in the host management system. The Total
Access EMS uses these protocols when connecting to remote OPTI-6100s.
The two TL1 encapsulated protocols are:
• SNMP Over TL1: Allows SNMP access to remote OPTI-6100s on an OSI network
• File Transfer Over TL1 (FTOT): Allows file transfer to/from OPTI-6100s on an OSI network
61184500L1-6J 89
OPTI-6100 Maintenance and Troubleshooting Practice
Management Connectivity
There are several ways to access the OPTI-6100 management applications.
• Craft Port: DB9/RS232 serial port on the front of the SCM
• ADMIN Port: DB25/RS232 serial port on the back of the chassis (shared with the X.25 port)
• X.25 Port: DB25/RS232 serial port on the back of the chassis (shared with the ADMIN port)
• RS-485: Wire wrap pins on the back of the chassis
• IP Networking: Accessed primarily through the Ethernet port on the back of the chassis
• OSI Networking: Accessed through SONET DCC
The Craft, ADMIN/X.25, and RS485 ports are described in detail in the OPTI-6100 Installation
and Turn-Up Practice (P/N 61184500L1-5).
IP Networking and OSI Networking are described in “IP Networking” on page 91 and “OSI
Networking” on page 96, respectively.
Application Craft Port ADMIN Port X.25 RS-485 IP Network OSI Network
SNMP No No No No Yes No
FTP/TFTP No No No No Yes No
1. TL1 is available through the TL1 Cut-Through option in the TL1 Provisioning menu
2. Available through standard telnet (TCP port 23)
3. TL1 is available through TCP ports 2000 (with character echo) and 2001 (without echo)
4. Available through the ADTRAN proprietary Remote Menu Access feature (“Interoperability” on page 104)
5. Used by the Total Access EMS
90 61184500L1-6J
Element Management
IP Networking
IP (Internet Protocol) is the networking protocol used in most computer networks. All of the
OPTI-6100 management applications are available through an IP connection.
The OPTI-6100 supports three interfaces into its IP network software:
• Ethernet: The primary IP network interface (refer to “Ethernet Interface” below)
• IP Over OSI Tunnel: Provides IP connectivity to network elements that are accessible only
through OSI (refer to “IP Over OSI Tunneling” on page 108)
• PPP/DCC0: Provides IP connectivity to SONET systems that support an IP-based
management network over SONET DCC (refer to “IP Over DCC” on page 119)
Ethernet Interface
Ethernet is the primary IP interface, provisioned in the Ethernet Interface menu. To access
this menu, log on to the OPTI-6100 as ADMIN and complete the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select Network Management, and press ENTER.
4. From the Network Management menu, select IP Network Provisioning, and press ENTER.
5. From the IP Network Provisioning menu, select IP Network Interfaces, and press ENTER.
6. From the IP Network Interfaces menu, select Ethernet Interface, and press ENTER.
Figure 45 illustrates the Ethernet Interface menu.
Ethernet Interface
1. Interface : ENABLE
2. IP Address : 10.25.2.24
3. Subnet Mask : 255.255.0.0
4. Gateway : 10.25.254.254
Link : Up
MAC Address : 00:a0:c8:13:06:4e
Selection :
61184500L1-6J 91
OPTI-6100 Maintenance and Troubleshooting Practice
IP Route Table
The OPTI-6100 does not run IP routing software (OSPF, RIP, etc.). The determination as to
which IP interface (Ethernet, OSI tunnel or PPP/DCC0) traffic is sent is based on the desti-
nation address and static routes.
Static IP routes are provisioned in the IP Route Table. To access the IP Route Table, log on to
the OPTI-6100 as ADMIN and complete the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select Network Management, and press ENTER.
4. From the Network Management menu, select IP Network Provisioning, and press ENTER.
5. From the IP Network Provisioning menu, select IP Route Table, and press ENTER.
92 61184500L1-6J
Element Management
IP Route Table
Selection :
(C)reate
Each row in the table specifies an interface to which a range of IP addresses is sent. The
address range is determined by the portion of the IP address that falls under a bit mask
defined by the Netmask. The Netmask is usually written in decimal but is easier to vision
when written in hex or binary (255.255.255.0 becomes FFFFFF00 hex or
111111111111111111111111000000000 binary). The range of addresses defined by the first
route in the menu is 10.25.15.0 through 10.25.15.255.
The gateway applies to shared media networks (such as Ethernet) and specifies the host to
which traffic to remote destinations is sent (this is usually an IP router). A gateway entry is not
applicable to the PPP/DCC0 and OSI Tunnel interfaces.
The first two routes in the example above are known as interface routes and were entered
automatically when the respective interfaces (Ethernet, PPP/DCC0) were enabled. The param-
eters of these routes are determined by the IP address, subnet mask and gateway entered in
the interface provisioning.
The third route in the example is not an interface route and was entered manually. All routes
associated with the OSI tunnel interface must be entered manually with an associated NSAP
address. Refer to “IP Over OSI Tunnel Routes” on page 111 for details.
61184500L1-6J 93
OPTI-6100 Maintenance and Troubleshooting Practice
Interface Gateway
When an interface which is not a point-to-point is selected as the default route, the interface
gateway must also be provisioned. This specifies the remote network element that is directly
reachable on that interface to which the (default routed) IP data is sent.
The non point-to-point interfaces are the Ethernet and OSI tunnel interfaces. If either of these
interfaces is the Default Route Interface, the associated interface gateway must also be provi-
sioned. Refer to “Ethernet Interface” on page 91 and “IP Over OSI Tunnel Interface” on
page 109 for details.
The PPP/DCC0 interface is a point-to-point interface. When selected as the Default Route
Interface, the interface gateway is not applicable (there is only one remote element available
on the network). Refer to “IP Over DCC” on page 119.
94 61184500L1-6J
Element Management
IP Forwarding
When multiple IP interfaces are enabled (for example, Ethernet and IP/OSI tunnel), IP
forwarding can be enabled to allow the NE to mediate IP traffic between the interfaces.
IP forwarding is enabled in the IP Network Interfaces menu. To access this menu, log on to the
OPTI-6100 as ADMIN and complete the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select Network Management, and press ENTER.
4. From the Network Management menu, select IP Network Provisioning, and press ENTER.
5. From the IP Network Provisioning menu, select IP Network Interfaces, and press ENTER.
6. From the IP Network Interfaces menu, select IP Forwarding, and press ENTER.
7. From the IP Forwarding menu, select Enable or Disable, and press ENTER.
TL1 with echo TCP 2000* TL1 access for human interface
TL1 without echo TCP 2001* TL1 access for machine interface
Secondary Telnet TCP 2002* Used for Telnet access when low port numbers
are blocked
Terminal Server, Ntwk Mgmt TCP 2003* Terminal server to device connected on the
Network Management port
Terminal Server, ADMIN Port TCP 2004* Terminal server to device connected on the
ADMIN port
61184500L1-6J 95
OPTI-6100 Maintenance and Troubleshooting Practice
In addition to the ports listed in Table 40 (on which the OPTI-6100 listens for service request
messages), the OPTI-6100 may send autonomous requests to the ports listed in Table 41.
Table 41. Ports To Which the OPTI-6100 Can Send Autonomous Messages
SNMP Traps UDP 162 Simple Network Management Protocol Traps. The
OPTI-6100 can send autonomous SNMP traps to
this port at the provisioned trap host IP address.
Up to four trap host addresses can be
provisioned.
OSI Networking
The OSI (Open Standards Interconnect) protocol is traditionally used by SONET systems to
provide a management network on the SONET DCC (data communication channel).
TL1 is the most common application used on OSI networks and the only interoperable (with
non-ADTRAN vendors) OSI application that the OPTI-6100 supports.
The OPTI-6100 also supports a proprietary OSI application that allows menu access on
remote OPTI-6100 systems from within a menu session of any other OPTI-6100 system. Refer
to “OSI Remote Menu Access” on page 106.
There are three components that require provisioning for OSI networking:
• The TID (TL1 target ID)
• One or more DCC interfaces
• The NSAP (Network Service Access Point)
TID
The TL1 protocol uses a TID (Target ID) for addressing. Although not a component of OSI, TL1
is the primary OSI application and a valid TID must be provisioned before the OPTI-6100
enables its OSI networking software.
The TID is provisioned through the TL1 menu. To access this menu, log on to the OPTI-6100
as ADMIN and complete the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select TL1, and press ENTER.
96 61184500L1-6J
Element Management
TL1
Chassis : 1
1. Client Shelf Management : Intelligent NE
2. Target ID (TID) : NODE-A
3. TL1 Telnet Port : 2000
4. TL1 Raw-TCP Port : 2001
5. Exchange TL1 Ports
6. TL1 Echo : ENABLE
7. TL1 Log
8. TL1 Cut-Through
Selection :
The TID consists of 1 to 20 upper case alphanumeric characters. A dash '–' may also be used
but the first character must be a letter.
DCC Interfaces
The OPTI-6100 is capable of terminating an OSI/DCC link on every SONET interface that it
supports (OC-3, OC-12, OC-48, or EC1). There is, however, a limit to the total number of
DCCs that can be terminated on a single shelf. This limit depends on the OMM hardware and
ranges from four to fourteen (refer to Table 42 on page 98).
DCC interfaces are provisioned through the DCC Interface menu. To access this menu, log on
to the OPTI-6100 as ADMIN and complete the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select Network Management, and press ENTER.
4. From the Network Management menu, select SONET SDCC Provisioning, and press ENTER.
5. From the SONET DCC Provisioning menu, select DCC Interface Provisioning, and press ENTER.
61184500L1-6J 97
OPTI-6100 Maintenance and Troubleshooting Practice
OMM3V__ (1184502L5, 6, 7) 2 6
OMMXCV (1184536L1) 0 6
OMM12__ (1184504L1, 4) 1 6
OMM12V__ (1184504L2, 3, 5) 2 6
OMM12V__E (1184504L6, 7, 8) 2 12
OMM48 (1184548L1) 2 12
DCC Interfaces
Selection :
From this menu, select an existing DCC interface (displayed on the screen) or create a new
interface by pressing C (for “create”). When creating a new interface, a new menu appears
listing the available SONET facilities on which a DCC can be defined. If no facilities appear,
there are no additional SONET facilities equipped that do not already have a DCC termination.
NOTE
A DCC can be created for a SONET facility that is not yet equipped.
98 61184500L1-6J
Element Management
Figure 49 illustrates the DCC Interface menu which appears after selecting an existing DCC or
creating a new one.
Selection :
Figure 49. DCC Interface Menu for High Speed 1 (LAPD Mode)
The first three parameters on this screen are the only ones that normally require provisioning:
• Name: The name is for identification only and has no affect on the operation of the DCC
• Service State: The Service State may be set to one of two values:
– In Service: Normal operation
– Out of Service: Maintenance operation; DCC continues to operate normally, but DCC
alarms are suppressed
NOTE
Parameters listed below Service State cannot be altered when the
DCC is IS. The DCC must be OOS to access the remaining provi-
sioning parameters or to delete the DCC.
• DCC Mode: The DCC Mode can be set to one of three values:
– Network: For connecting to a far-end DCC termination that is set to User
– User: For connecting to a far-end DCC termination that is set to Network
– PDCC0: Used when DCC is used as an IP interface
Network and User use LAPD as the layer 2 protocol (used in OSI networking). PDCC0 selects
PPP as the layer 2 protocol (refer to “IP Over DCC” on page 119).
61184500L1-6J 99
OPTI-6100 Maintenance and Troubleshooting Practice
For OSI operation it is not important that a particular DCC interface be set to Network or User
but it is critical that one termination of a DCC link be User and the other Network. If both
terminations are set the same, the link does not come up.
CAUTION
The remaining parameters should not be modified from the default
values.
NSAP
The OSI protocol uses NSAP (Network Service Access Point) for addressing network elements.
Although the OPTI-6100 may terminate multiple DCC interfaces, it has only one NSAP.
The NSAP is provisioned through the SONET DCC Upper Layers Provisioning menu. To access
this menu, log on to the OPTI-6100 as ADMIN and complete the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select Network Management, and press ENTER.
4. From the Network Management menu, select SONET SDCC Provisioning, and press ENTER.
5. From the SONET DCC Provisioning menu, select Upper Layers Provisioning, and press ENTER.
The NSAP is composed of two components:
• “Area Address” on page 101
• “System ID” on page 102
When required to enter an NSAP (e.g., for IP over OSI tunnels), the complete string containing
both the Area Address and the System ID must be entered.
100 61184500L1-6J
Element Management
Area Address
The Area Address is variable and must be provisioned according to the network environment
in which the network element is deployed.
NOTE
If Mount Location is Central Office or Remote Terminal, the DCC
associated with High Speed 1 cannot be provisioned. This DCC is
automatically created and locked for support of the point-to-point
features outlined in “Central Office/Remote Terminal Applications”
on page 122.
Selection :
61184500L1-6J 101
OPTI-6100 Maintenance and Troubleshooting Practice
NOTE
Communications across the SONET DCC is lost if the NSAP Area
Address is entered incorrectly.
System ID
The System ID is a fixed-length field containing 12 hexadecimal characters. The MAC address
is used for the system ID. There is no reason to ever change the system ID. It is provided for
information purposes only.
NOTE
If Mount Location is set to Central Office or Remote Terminal, the
System ID is either 111111111111 or 222222222222 . If Mount
Location is set to Subtended, the System ID is the same as the
MAC address.
102 61184500L1-6J
Element Management
Management
TL1 Access System
to OPTI-6100
Third-Party
GNE Gateway Network Element
SONET Network
w/OSI Management
61184500L1-6J 103
OPTI-6100 Maintenance and Troubleshooting Practice
Interoperability
When operating the OPTI-6100 with other SONET equipment, the following provisioning must
be considered for support of the OSI/DCC management network:
• The LAPD mode must be User on one side and Network on the other side of each DCC link
that the OPTI-6100 terminates (Refer to “DCC Interfaces” on page 97).
• LAPD Acknowledged Information Transfer Service (AITS) must be used on each DCC link
that the OPTI-6100 terminates. The OPTI-6100 operates in AITS only. Some SONET
equipment also support UITS (Un-acknowledged Information Transfer Service).
• The NSAP Area Address must be set appropriately as explained in “Area Address” on
page 101.
• The correct TCP port must be used for the front-end IP connection to the GNE. Table 43
lists the TCP port for various SONET equipment.
Lucent: 3801
DMX
Nortel: 13666 Refer to “Nortel” on page 105 regarding LAPD frame size.
OPTera Metro 3500
The following sections outline specific interoperability issues for non-adtran SONET vendors.
Fujitsu
The Fujitsu FLM and Flashwave series of products commonly use the ISO Data Country Code
format for NSAP Area Address. Refer to “Area Address” on page 101.
Fujitsu equipment supports a proprietary LAPD mode (Plus-R) in addition to the standard
User and Network. The Plus-R mode is commonly used between Fujitsu equipment but it is
not compatible with the OPTI-6100. The Fujitsu equipment must be set to either User or
Network mode on each DCC link that is directly connected to an OPTI-6100. This provisioning
is referred to as “L2CR” in the Fujitsu provisioning.
104 61184500L1-6J
Element Management
Lucent
Lucent equipment commonly uses the ISO Data Country Code format for NSAP Area Address.
Refer to “Area Address” on page 101.
Nortel
The Nortel OPTera Metro series of equipment commonly use the Private format for NSAP Area
Address. Refer to “Area Address” on page 101.
Nortel equipment commonly uses a LAPD frame size that is incompatible with the OPTI-6100.
The LAPD frame size must be set to 512 bytes (the provisionable range is 512 to 1492).
61184500L1-6J 105
OPTI-6100 Maintenance and Troubleshooting Practice
This selection menu alphabetically lists the TID (Target Identifier) of all NEs on the OSI
network. The NEs supporting remote menu access (the OPTI family of products) are listed in
the left column. NEs which don't support remote menu access are listed in the right column.
To access the menus on any system in the left column, type its selection number and press
ENTER. Alternately, press T for a TID entry screen, and enter the TID.
When finished with the remote menu session, simply logout or press CTRL+X to return to the
originating menu session.
106 61184500L1-6J
Element Management
The NEs are listed alphabetically by the DCC interface to which they are attached, followed by
the TID.
Login Bypass
Refer to “Remote Menu Access Login Required” on page 134.
61184500L1-6J 107
OPTI-6100 Maintenance and Troubleshooting Practice
108 61184500L1-6J
Element Management
NOTE
If Mount Location is Central Office or Remote Terminal, the IP over
OSI tunneling interface is inaccessible. For CO/RT applications,
the tunneling interface is provisioned automatically and used for
the point-to-point features outlined in “Central Office/Remote Ter-
minal Applications” on page 122.
To access the OSI Tunnel Interface menu, log on to the OPTI-6100 as ADMIN and complete
the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select Network Management, and press ENTER.
4. From the Network Management menu, select IP Network Provisioning, and press ENTER.
5. From the IP Network Provisioning menu, select OSI Tunnel Interface, and press ENTER.
Figure 54 illustrates the OSI Tunnel Interface menu.
Selection :
61184500L1-6J 109
OPTI-6100 Maintenance and Troubleshooting Practice
110 61184500L1-6J
Element Management
IP Route Table
Selection :
(C)reate
Select an exiting route for modification by entering the number, or create a new route by
typing C (Create).
NOTE
For OSI tunnel routes, the interface (“Ifc”) is listed as OSItu.
61184500L1-6J 111
OPTI-6100 Maintenance and Troubleshooting Practice
After selecting or creating a route, the Edit Route Entry menu appears. Figure 56 illustrates
the Edit Route Entry menu.
1. IP Addr 10.25.15.98
2. Netmask 255.255.255.255
3. Gateway None
4. Interface OSItu
5. NSAP 39840F8000000000000000000000A0C80A7FC6
Selection :
(A)ccept, (D)elete
NOTE
The NSAP entry field is not visible until OSItu has been selected as
the interface.
112 61184500L1-6J
Element Management
Proxy ARP
Address Resolution Protocol (ARP) is the means by which an IP/Ethernet element matches IP
and Ethernet addresses of other elements on an Ethernet LAN. Knowing an element’s
Ethernet address is required before traffic can be sent to it on an Ethernet LAN.
An OPTI-6100 can proxy ARP for elements to which it is terminating an IP over OSI tunnel
when the following conditions are met:
• The OPTI-6100 Ethernet port is enabled
• The OPTI-6100 has a route for the far-end element and the Netmask of that route is
255.255.255.255 (a single element route)
• The IP address of the far-end element falls within the OPTI-6100 Ethernet subnet
When a Ethernet element proxies ARP for a remote element it requests other elements on the
Ethernet LAN to send it the IP traffic destined for the remote element, for forwarding. In other
words, it advertises the remote IP address as being available on its own Ethernet address.
When using Proxy ARP, elements on the Ethernet LAN automatically find the correct
forwarding path for IP traffic. When Proxy ARP is not used a manual route may be required in
the Ethernet LAN elements (individual computers or a router).
61184500L1-6J 113
OPTI-6100 Maintenance and Troubleshooting Practice
Node A Node B
SCM
STATALM DS3EC1M
1184503L1
STATUS
MS BLANK
1184505L1
DS1M
1184513L1
STATUS
DS1M
1184513L1
STATUS
STAT
LNK
MS BLANK
1184505L1
OMM12LR
1184504L1
STATUS
OMM12LR
1184504L1
STATUS
DS1M
1184513L1
STATUS
OPTI-6100
MS BLANK
1184505L1
DS3EC1M
1184503L1
STATUS
DS3EC1M
1184503L1
STATUS
MS BLANK
1184505L1
MS BLANK
1184505L1
SONET SCM
STATALM DS3EC1M
1184503L1
MS BLANK
1184505L1
DS1M
1184513L1
DS1M
1184513L1 STAT
LNK
MS BLANK
1184505L1
OMM12LR
1184504L1
STATUS
OMM12LR
1184504L1
STATUS
DS1M
1184513L1
OPTI-6100
MS BLANK
1184505L1
DS3EC1M
1184503L1
DS3EC1M
1184503L1
MS BLANK
1184505L1
MS BLANK
1184505L1
Network
STATUS STATUS STATUS STATUS STATUS STATUS
1184500L1 ETHM 1184500L1 ETHM
1184510L1E 1184510L1E
ALARM ALARM ALARM N ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM N ALARM ALARM ALARM ALARM ALARM
E E
T T
ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE
1 1
TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST
DCC DCC
E E
N N
E E
T T
2 2
ACOHST ACOHST
E E
N N
E E
T T
3 3
ACT ACT
*3 *1 *3 *1*3 *1 3 *3 *1 *3 *1*3 *1 3
SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11* MS12 SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11* MS12
Ethernet
IP
Network
114 61184500L1-6J
Element Management
Step-By-Step Setup
NOTE
All IP addresses given are as examples.
To set up an IP over OSI tunnel according to Example 1, complete the following steps:
1. Verify that the Mount Locations on both Nodes A and B are set to Subtended (refer to
“Central Office/Remote Terminal Applications” on page 122).
2. Establish OSI connectivity between Nodes A and B (refer to “OSI Networking” on page 96).
3. Provision and enable the Ethernet interface at Node A (refer to “Ethernet Interface” on
page 91).
4. Provision/enable the IP over OSI tunnel interface at Node A (refer to “IP Over OSI Tunnel
Interface” on page 109).
In this example the Ethernet IP address used.
5. Enter an IP over OSI tunnel route at Node A (refer to “IP Over OSI Tunnel Routes” on
page 111).
This route specifies a single element (Node B) for access. The IP address is the Node B OSI
tunnel interface address. The NSAP address also belongs to Node B.
6. Enable IP forwarding at Node A (refer to “IP Forwarding” on page 95).
7. Disable the Ethernet interface at Node B (refer to “Ethernet Interface” on page 91).
Ensure that the IP address on the disabled Ethernet interface does not conflict/overlap
with the IP address entered on the IP over OSI tunnel interface in the next step.
8. Provision/enable the IP over OSI tunnel interface at Node B (refer to “IP Over OSI Tunnel
Interface” on page 109).
This IP address (10.25.15.98) is used to access Node B.
The gateway is Node A’s Ethernet IP address. This must be entered since this interface is
selected as the default route interface for Node B (below).
The Subnet Mask is always set to 255.255.255.255 for the OSI Tunnel Interface.
9. Enter an IP over OSI tunnel route at Node B (refer to “IP Over OSI Tunnel Routes” on
page 111).
This route specifies a single element (Node A) for access. The IP address is the Node A
Ethernet IP address. The NSAP address also belongs to Node A.
10. Set the IP over OSI tunnel interface as the default route interface at Node B.
11. Verify connectivity to Node B by pinging its address (10.25.15.98) from any device on the
Node A Ethernet LAN.
61184500L1-6J 115
OPTI-6100 Maintenance and Troubleshooting Practice
Node A Node C
SCM
STATALM DS3EC1M
1184503L1
STATUS
MS BLANK
1184505L1
DS1M
1184513L1
STATUS
DS1M
1184513L1
STATUS
STAT
LNK
MS BLANK
1184505L1
OMM12LR
1184504L1
STATUS
OMM12LR
1184504L1
STATUS
DS1M
1184513L1
STATUS
OPTI-6100
MS BLANK
1184505L1
DS3EC1M
1184503L1
STATUS
DS3EC1M
1184503L1
STATUS
MS BLANK
1184505L1
MS BLANK
1184505L1
SONET SCM
STATALM DS3EC1M
1184503L1
MS BLANK
1184505L1
DS1M
1184513L1
DS1M
1184513L1 STAT
LNK
MS BLANK
1184505L1
OMM12LR
1184504L1
STATUS
OMM12LR
1184504L1
STATUS
DS1M
1184513L1
OPTI-6100
MS BLANK
1184505L1
DS3EC1M
1184503L1
DS3EC1M
1184503L1
MS BLANK
1184505L1
MS BLANK
1184505L1
Network
STATUS STATUS STATUS STATUS STATUS STATUS
1184500L1 ETHM 1184500L1 ETHM
1184510L1E 1184510L1E
ALARM ALARM ALARM N ALARM ALARM ALARM ALARM ALARM ALARM ALARM ALARM N ALARM ALARM ALARM ALARM ALARM
E E
T T
ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE ONLINE
1 1
TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST TEST
DCC DCC
E E
N N
E E
T T
2 2
ACOHST ACOHST
E E
N N
E E
T T
3 3
ACT ACT
*3 *1 *3 *1*3 *1 3 *3 *1 *3 *1*3 *1 3
SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11* MS12 SCM MS1 MS2 MS3 MS4 MS5 MS6 HS1 HS2 MS7 MS8 MS9 MS10 MS11* MS12
Ethernet
Ethernet
IP
Network Isolated LAN on
10.25.16.0 Subnet
116 61184500L1-6J
Element Management
Step-By-Step Setup
NOTE
All IP addresses given are as examples.
The step-by-step setup for Example 2 is similar to Example 1 (differences highlighted in bold).
1. Verify that the Mount Locations on both Nodes A and C are set to Subtended (refer to
“Central Office/Remote Terminal Applications” on page 122).
2. Establish OSI between Nodes A and C (refer to “OSI Networking” on page 96).
3. Provision/enable the Node A Ethernet interface (refer to “Ethernet Interface” on page 91).
4. Provision and enable the IP over OSI tunnel interface at Node A (refer to “IP Over OSI
Tunnel Interface” on page 109).
5. Enter an IP over OSI route at Node A (refer to “IP Over OSI Tunnel Routes” on page 111).
Indicate a range of IP addresses (10.25.16.0–255). This is the subnet for the isolated
Ethernet LAN reached through Node C. The NSAP address belongs to Node C.
6. Enable IP forwarding at Node A (refer to “IP Forwarding” on page 95).
7. Provision/enable the Node C Ethernet interface (refer to “Ethernet Interface” on
page 91).
This IP address (10.25.16.99) can access Node C (even when access is through IP over
OSI).
8. Provision/enable the IP over OSI tunnel interface at Node C (refer to “IP Over OSI Tunnel
Interface” on page 109).
This IP address (10.25.16.67) can access Node C. Autonomous messages from Node C
using the IP over OSI tunnel use this as the source address. Use this address (not the
Ethernet address) to identify Node C within a management system.
The gateway is the Node A (Ethernet) IP address.
9. Enter an IP over OSI route at Node C (refer to “IP Over OSI Tunnel Routes” on page 111).
This route specifies a single element (Node A) for access. The IP address is the Node A
Ethernet IP address. The NSAP address also belongs to Node A.
10. Set the IP over OSI tunnel interface as the default route interface at Node C.
11. Set the default gateway of all elements on the LAN to the Node C Ethernet IP
address (10.25.16.99).
12. Enter a manual route in any device on the Node A LAN that needs to reach the
isolated LAN on Node C.
For a windows PC, use the Route Add command, as follows:
C:\> route -p add 10.25.16.0 mask 255.255.255.0 10.25.15.97
The '-p' parameter specifies the route is persistent (i.e., survives reboots of the computer).
The rest of the command specifies that traffic to all addresses between 10.25.16.0 and
10.25.16.255 be sent to 10.25.15.97 for forwarding.
61184500L1-6J 117
OPTI-6100 Maintenance and Troubleshooting Practice
The route entry can be verified with the Route Print command as follows:
C:\> route print
Figure 59 illustrates the Route Print command and a sample response.
13. From the computer on the Node A LAN, addresses on the Node C (isolated) LAN can be
pinged (10.25.16.xx).
118 61184500L1-6J
Element Management
IP Over DCC
Some SONET systems (e.g., Cisco ONS 15454) use IP on the DCC for the networking protocol
rather than OSI. The OPTI-6100 is compatible with most of these systems and may terminate
an IP interface on any one of its DCCs.
NOTE
There is a difference between IP over DCC and IP over OSI tunnel-
ing (described in “IP Over OSI Tunneling”). IP over DCC uses IP as
the native networking protocol on the SONET DCC. IP over OSI
tunneling uses OSI as the native networking protocol on the
SONET DCC and provides a means to encapsulate and forward IP
traffic over the native OSI network.
61184500L1-6J 119
OPTI-6100 Maintenance and Troubleshooting Practice
Selection :
Figure 60. DCC Interface Menu for High Speed 1 (PDCCO Mode)
NOTES
This is the same menu as Figure 49 on page 99, except that the
mode has been set to PDCC0 rather than one of the LAPD modes
(Network or User). As an IP interface the point-to-point protocol
(PPP) is used as the layer 2 element instead of LAPD. When the
mode is set to PDCC0 the remaining LAPD provisioning parameters
are no longer displayed.
Only one DCC may select PDCC0 as its mode. The OPTI-6100 can
terminate only one PPP/DCC IP interface at a time.
The IP Provisioning option is a shortcut to the IP Provisioning menu for the PPP/DCC0
interface. This menu can also be accessed by performing the following steps:
1. From the OPTI-6100 Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Provisioning, and press ENTER.
3. From the Provisioning menu, select Network Management, and press ENTER.
4. From the Network Management menu, select IP Network Provisioning, and press ENTER.
5. From the IP Network Provisioning menu, select IP Network Interfaces, and press ENTER.
6. From the IP Network Interfaces menu, select PPP/DCCO Interface, and press ENTER.
120 61184500L1-6J
Element Management
PPP/DCC0 Interface
1. Interface : ENABLE
2. IP Address : 192.1.0.97
3. Subnet Mask : 255.255.255.0
4. Gateway : 0.0.0.0
5. DCC Provisioning
DCC Interface : High Speed 1
Peer Address : 192.1.0.98
Link : Up
Selection :
NOTE
The OPTI-6100 does not run routing software (OSPF, RIP, etc.) for
IP networking. Determination of what interface is used for sending
IP data is made by the interface settings (IP address, subnet mask,
default gateway) or entries made in the static route table (refer to
“IP Route Table” on page 92).
61184500L1-6J 121
OPTI-6100 Maintenance and Troubleshooting Practice
122 61184500L1-6J
Element Management
Network Management
1. IP Network Provisioning
2. SONET SDCC Provisioning
3. Mount Location : Central Office
4. Get Net Prov From HS Module : ENABLE
5. Remote File I/O Method : TFTP (UDP/IP)
Selection :
NOTE
When the Mount Location is changed, the SCM software must
reboot. If you choose not to reboot the SCM, the change does not
take effect. Rebooting the SCM software does not interrupt traffic,
but management connections are closed.
61184500L1-6J 123
OPTI-6100 Maintenance and Troubleshooting Practice
System Alarms
Selection :
124 61184500L1-6J
Element Management
NOTE
When a CO OPTI-6100 is set up with a Total Access 3000/3010 for
remote menu access, the RT alarm entry in the Shelf Alarm Status
screen of the OPTI-6100 is present and always indicates that there
are no RT alarms (even if the Total Access 3000/3010 has active
alarms).
61184500L1-6J 125
OPTI-6100 Maintenance and Troubleshooting Practice
SYSTEM ADMINISTRATION
This section describes the system administration functions of the OPTI-6100, including the
System Configuration Archive which stores provisioning information, the System Event Log,
which stores SNMP and menu events, and Auto Upgrade features for system firmware
upgrades.
The System Administration menu is illustrated in Figure 64.
System Administration
1. Software Update
2. Security Administration
3. System Configuration Archive (SCA)
4. System Event Log
5. Auto Upgrade Status
Selection :
126 61184500L1-6J
System Administration
Software Update
The following sections detail the procedures to manually upgrade the firmware on the SCM,
the OMM modules, and the tributary modules. If updates are to be performed over TFTP, the
server address must be specified on the SCM (refer to “SCA TFTP Server” on page 147).
This section includes the following topics:
• “Upgrade SCM Software” on page 127
• “Upgrade OMM Module Software” on page 128
• “Upgrade Tributary Module Software” on page 129
NOTE
Newly loaded SCM software does not begin running until the SCM
has been rebooted.
61184500L1-6J 127
OPTI-6100 Maintenance and Troubleshooting Practice
NOTE
Newly loaded OMM software does not begin running until the OMM
module has been rebooted.
128 61184500L1-6J
System Administration
NOTE
Newly loaded software does not begin running until the module has
been rebooted.
61184500L1-6J 129
OPTI-6100 Maintenance and Troubleshooting Practice
Security Administration
Security Administration is used to view which users are currently logged on to the system and
create, enable, disable, modify, and delete user accounts.
NOTE
You must be logged in with ADMIN-level privileges to access the
Security Administration menu and features.
Up to 15 user accounts can exist at one time. Each account has its own password and access
privileges. Account privileges include READ, READ/WRITE, CONFIG, and ADMIN.
• READ privileges provide read-only access to the system menus.
• READ/WRITE privileges provide read and write access to most provisioning items in the
system menus. The READWRITE privilege cannot make changes to the security account
management system, network management settings, SNMP settings, TL1 port assignments
or the Network Management port configuration.
• CONFIG privileges provide the same rights as ADMIN privileges, with the exception of
access to the System Administration functions. (CONFIG is not a default account name.)
• ADMIN privileges provide full access to applicable system menus. The ADMIN-level account
can delete any account (including default accounts) except for the active ADMIN account.
ADMIN-level users can also terminate other users logged into the system through the Users
Currently Logged on menu.
For a full list of access privileges, refer to “Appendix C, Access Privileges”.
130 61184500L1-6J
System Administration
Security Administration
Selection :
61184500L1-6J 131
OPTI-6100 Maintenance and Troubleshooting Practice
Security Options
Security Options are global, and do not change between privilege levels. The Security Options
menu is illustrated in Figure 66.
Security Options
Selection :
132 61184500L1-6J
System Administration
Case-Sensitive Password/User-ID
This option determines if the User ID and password fields of the login screen are case-
sensitive. By default, case-sensitivity is Enabled.
61184500L1-6J 133
OPTI-6100 Maintenance and Troubleshooting Practice
CAUTION
The Challenge Key response provided by ADTRAN Technical Sup-
port is only valid for one session. At this time, security account
maintenance must be completed with the appropriate accounts
and passwords prior to logging out of the system.
134 61184500L1-6J
System Administration
NOTE
The ADTRAN Dictionary contents must be loaded/compiled/added
to the RADIUS Server of choice. Without these additions, all logons
default to the ‘Default Radius Logon Level’ as provisioned on the
“Primary RADIUS Server Settings Menu” on page 137.
#
# dictionary.adtran
#
# Authored by: Margaret Hataway margaret.hataway@adtran.com
# 12/03/2003
#
# Dictionary file for Adtran Vendor-Specific attributes and their values.
# Enable by putting the line "$INCLUDE dictionary.adtran" in the main
# dictionary file.
#
# Attributes
#
ATTRIBUTE Adtran-IAD-Telnet-Level 1 integer Adtran
#
# Attribute Values
#
# Values for Adtran-Telnet-Level attribute for the Total Access IADs
# This attribute sets the access level granted to a user for a particular
# telnet session.
VALUE Adtran-IAD-Telnet-Level Level-Full 0
VALUE Adtran-IAD-Telnet-Level Level-Support 1
VALUE Adtran-IAD-Telnet-Level Level-Config 2
VALUE Adtran-IAD-Telnet-Level Level-Router 3
VALUE Adtran-IAD-Telnet-Level Level-Voice 4
VALUE Adtran-IAD-Telnet-Level Level-Status 5
61184500L1-6J 135
OPTI-6100 Maintenance and Troubleshooting Practice
ADTRAN-Telnet-Level Values
Table 44 displays the ADTRAN-Telnet-Level values. Each level corresponds to an ADTRAN
standard access privilege level on the SCM.
Selection :
136 61184500L1-6J
System Administration
Primary RADIUS Server Configuration is the screen used to set the server address and other
functions for this feature.
The Primary RADIUS Server Authentication Settings menu is displayed in Figure 68.
Selection :
Server Address
This option displays the value of the IP Address of the RADIUS Server to be queried for
authentication.
61184500L1-6J 137
OPTI-6100 Maintenance and Troubleshooting Practice
Port Number
This option displays the value of the UDP port of the server. The default value is 1812.
Number Retries
This option displays the maximum number of request transmissions the unit attempts before
giving up on the RADIUS Server. The default is three, and the allowable range is 0 to 255.
Time Out
This option displays the number of seconds that the unit waits for a response from the
RADIUS Server before re-transmitting a request. The default is five seconds, with a 1-second
minimum value.
Shared Secret
This option is the shared secret that is used when communicating with the host server. This
value is a case-sensitive character string that has a maximum length of 63 ASCII characters.
The default value is a null string.
138 61184500L1-6J
System Administration
NOTE
RADIUS cannot be enabled by way of the menus until validation is
successful.
13. From the RADIUS Remote Authentication Configuration menu, select Enable RADIUS Remote
Authentication, and press ENTER.
14. Select Y to enable or N to abort.
61184500L1-6J 139
OPTI-6100 Maintenance and Troubleshooting Practice
4. SCA Operations
Selection :
140 61184500L1-6J
System Administration
Selection :
AutoSave System
This field enables or disables the AutoSave system. There is a five-minute delay after initial
power-up of the SCM before an AutoSave operation is performed. This is to allow sufficient
time for the chassis and provision settings on the SCM and modules to stabilize.
61184500L1-6J 141
OPTI-6100 Maintenance and Troubleshooting Practice
AutoSave Retries
The AutoSave Retries option determines the number of retries the system performs following a
failed AutoSave operation.
142 61184500L1-6J
System Administration
Selection :
61184500L1-6J 143
OPTI-6100 Maintenance and Troubleshooting Practice
144 61184500L1-6J
System Administration
Slot
These columns represent each of the OPTI-6100 tributary module slots (MS1 through MS12 in
the MX chassis, MS1 through MS4 in the SMX) and OMM slots HS1 and HS2.
Card Type
These columns represent the card type identification of the module currently installed in the
corresponding slot of the OPTI-6100.
61184500L1-6J 145
OPTI-6100 Maintenance and Troubleshooting Practice
Restore
These columns represent whether or not SCA restore to the corresponding slot has been
enabled by the administrator. If the field is displayed in reverse video, some condition (such as
an empty slot, user disable, or exclusion due to the module being In Service) exists that
prevents SCA restore to this slot.
146 61184500L1-6J
System Administration
SCA Operations
Use the SCA Operations menu (Figure 73) to display and configure provisions related to
manual SCA save and restore operations. Use this screen to initiate manual SCA Save and
restore operations or to monitor the status of the SCA AutoSave system.
SCA Operations
Selection :
61184500L1-6J 147
OPTI-6100 Maintenance and Troubleshooting Practice
(S)ave
'?' - System Help Screen
148 61184500L1-6J
System Administration
Cards in Shelf
Cards in Shelf displays the number of modules present in the chassis and lists the slots where
the modules are installed.
AutoSave Status
AutoSave Status displays the completion status of the last SCA AutoSave operation, or Idle if
none have been performed.
61184500L1-6J 149
OPTI-6100 Maintenance and Troubleshooting Practice
(S)ave, (A)bort
'?' - System Help Screen
Cards in Shelf
This field displays the number of modules present in the chassis as well as a summary of the
slot numbers where the modules are installed.
150 61184500L1-6J
System Administration
61184500L1-6J 151
OPTI-6100 Maintenance and Troubleshooting Practice
Cards in Shelf
The Cards in Shelf field displays the number of modules present in the chassis that are being
restored, and a summary of the slot numbers where the modules are installed.
Cards In SCA
The Cards In SCA field displays the number and summary of module slots represented in the
SCM file retrieved by the Restore operation.
Cards Restored
The Cards Restored field lists modules whose provision settings were successfully restored,
and their slots.
Cards Excluded
The Cards Excluded field lists the modules that were not restored due to user or other exclu-
sions. Refer to the “SCA Module Restore Provisioning” and “SCA SCM Restore Provisioning”
sections for a description of user configurable exclusion conditions.
Cards w/ Exceptions
The Cards w/ Exceptions field lists the modules slots that experienced exception or error
conditions during the restore operation, and their slots.
152 61184500L1-6J
System Administration
Selection :
(N)ext (P)revious (F)irst (L)ast
Event Filters- (A)ll S(C)A (D)ateTime lo(G)in accoun(T) Securit(Y) (S)/W Updates
61184500L1-6J 153
OPTI-6100 Maintenance and Troubleshooting Practice
SNMP Events
The following is a list of SNMP events stored in the System Event Log:
• SNMP Events caused by Sets
• AdFactGenSlotSetDefaults
• AdFactGenSlotMacAddress
• AdGenSlotTrapEnable
• AdGenChassisDate
• AdGenChassisTime
• AdGenSlotUpdateSoftware
• AdTrapEnable
• AdGenESCMrestoreFactoryDefaults
• AdTrapInformHostStatus
• AdGenESCMReset
• AdTAeSCMSecAccountUserID
• AdTAeSCMSecAccountStatus
• AdTAeSCMSecAccountAccessRights
• AdTAESCMSecChangeAccountPassword
• AdTAeSCMDefaultRouteInterface
• AdTAeSCMDefaultRouteInterfaceEx
154 61184500L1-6J
System Administration
Menu Events
The following is a list of menu events stored in the System Event Log. The menu events caused
by provisioning are as follows:
61184500L1-6J 155
OPTI-6100 Maintenance and Troubleshooting Practice
156 61184500L1-6J
System Administration
61184500L1-6J 157
OPTI-6100 Maintenance and Troubleshooting Practice
158 61184500L1-6J
System Administration
61184500L1-6J 159
OPTI-6100 Maintenance and Troubleshooting Practice
160 61184500L1-6J
System Administration
The System Event Log uses hot keys to navigate and filter the events. The hot keys are
described at the bottom of the menu screen. (N) Next, (P) Previous, (F) First, and (L) Last
navigate to the various pages of the System Event Log. Filters are provided to view All, SCM,
Date/Time, Login, Account, Security, and S/W Update related events.
61184500L1-6J 161
OPTI-6100 Maintenance and Troubleshooting Practice
NOTE
Operation of this feature requires IP or FTOT (through Total Access
EMS) connectivity to the OPTI-6100 system, either through IP/
DCC or the Ethernet maintenance port. Auto Upgrade does not
function if only OSI connectivity (without FTOT) is enabled.
When the Auto Upgrade System is enabled, either manually or automatically, the SCM
compares the current product revision and firmware revision information against what has
been specified in a retrieved Auto Upgrade Config File. Modules that are not currently running
the firmware revision specified in the Auto Upgrade Config File are marked needs upgrade. If
the operating mode is set to Auto, the module is immediately upgraded or scheduled for future
upgrade if another module upgrade is already in progress.
When more than one module requires firmware upgrade, the Auto Upgrade System follows the
sequence below:
1. Upgrades all tributary modules of the same type in the chassis.
2. Advances to the next module type.
3. Returns to step 1 until all tributary modules requiring upgrade have been upgraded.
4. Upgrades the OMM modules, if necessary.
5. Upgrades the SCM, if necessary.
During the upgrade, the following items may apply:
• If the TFTP Cache feature is enabled, the SCM first attempts to retrieve firmware files
from the TFTP server prior to initiating the upgrade of each module. This eliminates any
chance of service interruption due to missing firmware files or other problems with the
customer IP management network or TFTP server.
• Modules failing to properly upgrade are retried a provisionable number of times before
the SCM gives up on that module, marking as being in an Auto Upgrade error state.
• If a serious TFTP error is encountered the Auto Upgrade system cancels the upgrade
after a provisionable number of retries.
• If a flash firmware file is not present on the TFTP server, all modules requiring the
missing file are skipped, and marked as being in an Auto Upgrade error state.
• The SCM and each upgraded module are reset following the firmware upgrade to allow
the unit to restart and run the new firmware.
• Modules inserted during an active Auto Upgrade are re-evaluated at the time of insertion
and can be upgraded during the current Auto Upgrade session.
162 61184500L1-6J
System Administration
61184500L1-6J 163
OPTI-6100 Maintenance and Troubleshooting Practice
NOTES
When Auto Upgrade Mode is set to Auto and an upgrade is per-
formed manually using the standard YModem or TFTP upgrade
procedure, the module is immediately up/downgraded to the firm-
ware version associated with the Auto Upgrade Config file. Set Auto
Upgrade Mode to Manual if it is necessary to deviate from the firm-
ware versions associated with the Auto Upgrade Config file.
To stop the Auto Upgrade system, press A for Abort Auto Upgrade.
To remove the Auto Upgrade Config filename, select Auto Upgrade Con-
fig Filename, and press E NTER without entering a new value. This
enters a null value for the Auto Upgrade Config filename and pre-
vents any further action by the Auto Upgrade system.
164 61184500L1-6J
System Administration
61184500L1-6J 165
OPTI-6100 Maintenance and Troubleshooting Practice
STATUS
There are several status screens in the OPTI-6100 menu tree. These screens provide a
snapshot of the status of various items in the system. This section describes how to access the
status screens and interpret the data.
Chassis Status
To access the Shelf Status screen, complete the following steps:
1. From the Main menu, select System Controller, and press ENTER.
2. From the System Controller menu, select Status, and press ENTER.
3. From the Status menu, select Shelf Status, and press ENTER.
The Shelf Status screen is shown in Figure 79.
166 61184500L1-6J
Status
NOTE
Access to the OSI Stack is for advanced users only.
4. From the SONET DCC Interface Status menu, select SONET DCC Subnet, and press ENTER.
The DCC Interfaces screen is shown in Figure 80.
DCC Interfaces
The DCC Interfaces screen shows the facility state of each of the DCC interfaces.
61184500L1-6J 167
OPTI-6100 Maintenance and Troubleshooting Practice
OMM3/12 Status
To access the Status screen for an OMM3 or OMM12 module, complete the following steps:
1. From the Main menu, select an OMM module, and press ENTER.
NOTE
Only slots containing modules can be selected from this menu.
Status
1. Clock Status
2. Synchronization Message Status
3. Shelf Status
Selection:
The OMM Status screen displays module and facility status for each of the OMM modules.
It also provides the alarm status of the OMM modules and equipment fault.
The following three status screens are available from the OMM Status screen:
• Clock Status
• Synchronization Message Status
• Shelf Status
168 61184500L1-6J
Status
Clock Status
The Clock Status screen displays the selected synchronization clock in use and the status
of the various clock sources.
4. Press ESC to return to the Status menu.
61184500L1-6J 169
OPTI-6100 Maintenance and Troubleshooting Practice
5. From the Status menu, select Synchronization Message Status, and press ENTER.
The Synchronization Message Status screen is shown in Figure 83.
PRI Fiber Clock (HS1) : DUS (9) DON'T USE for Synchronization
SEC Fiber Clock (HS2) : Unused
PRI External Clock : Unused
SEC External Clock : Unused
PRI Trib Module Clock : Unused
SEC Trib Module Clock : Unused
Fiber Transmission : DUS (9) DON'T USE for Synchronization
170 61184500L1-6J
Status
6. From the Status menu, select Shelf Status, and press ENTER.
The OC-3 Shelf Status screen is shown in Figure 84.
Shelf Status
Selection:
The Shelf Status screen indicates which OMM module is carrying the traffic, and the
status of Automatic Protection Switching.
7. Press ESC to return to the Status menu.
61184500L1-6J 171
OPTI-6100 Maintenance and Troubleshooting Practice
OMM48 Status
To access the Status screen for an OMM48 module, complete the following steps:
1. From the Main menu, select an OMM48 module, and press ENTER.
NOTE
Only slots containing modules can be selected from this menu.
Status
1. Equipment Status
2. Facility Status
3. STS-12C Status
4. STS-3C Status
5. STS-1 Status
6. VT1.5 Status
Selection:
The OMM Status screen displays module and facility status for the OMM module, plus
status at the STS-12, STS-3, STS-1, and VT1.5 level.
172 61184500L1-6J
Status
DS3EC1M Status
To access the DS3EC1M Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS3EC1M module, and press ENTER.
3. From the DS3 module menu, select Status, and press ENTER.
The DS3EC1M Status screen is shown in Figure 86.
Status
Equipment Provisioning : IS
Equipment State : IS ACT, PSI
Facility Provisioning : IS
Facility State : OOS-AU FLT
61184500L1-6J 173
OPTI-6100 Maintenance and Troubleshooting Practice
DS3EC1M3 Status
To access the DS3EC1M3 Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS3EC1M3 module, and press ENTER.
3. From the DS3 module menu, select Status, and press ENTER.
The DS3EC1M3 Status screen is shown in Figure 87.
Status
Equipment Provisioning : IS
Equipment State : IS STBY
Equipment Fault : None
7. Facility 1 Status
8. Facility 2 Status
9. Facility 3 Status
Selection:
174 61184500L1-6J
Status
DS3M3E/DS3M3T Status
To access the DS3M3E or DS3M3T Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS3M3E or DS3M3T module, and press ENTER.
3. From the DS3 module menu, select Status, and press ENTER.
The DS3M3E Status screen is shown in Figure 88.
Status
Equipment Provisioning : IS
Equipment State : OOS-AU AINS, MEA
Equipment Fault : None
7. Facility 1 Status
8. Facility 2 Status
9. Facility 3 Status
Selection:
61184500L1-6J 175
OPTI-6100 Maintenance and Troubleshooting Practice
DS1M/DS1M2 Status
To access the DS1M or DS1M2 Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS1M/DS1M2 module, and press ENTER.
3. From the DS1 module menu, select Status, and press ENTER.
The DS1M Status menu is shown in Figure 89.
Selection:
176 61184500L1-6J
Status
4. From the DS1 Status screen, select the desired DS1, and press ENTER.
A DS1 Facility Status screen is shown in Figure 90.
Facility #1 Status
Selection:
Equipment Status
Selection:
61184500L1-6J 177
OPTI-6100 Maintenance and Troubleshooting Practice
DS1VM/DS1VM2 Status
To access the DS1VM/DS1VM2 Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS1VM/DS1VM2 module, and press ENTER.
3. From the module menu, select Status, and press ENTER.
The DS1VM2 Status menu is shown in Figure 92.
Status
Selection:
178 61184500L1-6J
Status
4. From the DS1 Status screen, select the desired DS1, and press ENTER.
A DS1 Facility Status screen is shown in Figure 93.
Facility #1 Status
Selection:
Equipment Status
Selection:
61184500L1-6J 179
OPTI-6100 Maintenance and Troubleshooting Practice
Provisioning
Selection:
180 61184500L1-6J
Status
Selection:
61184500L1-6J 181
OPTI-6100 Maintenance and Troubleshooting Practice
DS1VME/DS1VMT Status
To access the DS1VME/DS1VMT Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS1VME/DS1VMT module, and press ENTER.
3. From the DS1VME/DS1VMT module menu, select Status, and press ENTER.
The DS1 Status menu is shown in Figure 97.
Status
Selection:
182 61184500L1-6J
Status
4. From the DS1 Status screen, select the desired DS1, and press ENTER.
A DS1 Facility Status screen is shown in Figure 98.
Facility #1 Status
Facility Provisioning : IS
Facility State : OOS-AU FLT
Line Length : 0 - 133 Feet
Line Coding : B8ZS
Loopback Code Detection : Disabled
Line Identification :
Alarm Status : Signal Fail
Loop Status : No Loop
Equipment Status
61184500L1-6J 183
OPTI-6100 Maintenance and Troubleshooting Practice
Provisioning
Selection:
184 61184500L1-6J
Status
Framing
Each facility in the DS1VME/DS1VMT supports independent framing. To provision the
framing settings for each facility, follow the instructions below:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS1VME module, and press ENTER.
3. From the DS1VME/DS1VMT module menu, select Provisioning, and press ENTER.
4. From the Provisioning menu, select Framing, and press ENTER.
The DS1VME/DS1VMT Framing menu is shown in Figure 101.
Framing
Selection:
61184500L1-6J 185
OPTI-6100 Maintenance and Troubleshooting Practice
Facility # 1
1. Auto
2. SLC96
3. ESF
4. SF
5. Unframed
Selection:
6. From the Framing menu, select a framing type, and press ENTER.
186 61184500L1-6J
Status
7. To set multiple facilities (any or all) in the DS1VME/DS1VMT to the same framing type,
select Set Multiple from the Framing menu, and press ENTER.
The Enter Facilities to Set screen is shown in Figure 103.
8. Enter the numbers of each facility to be set, delimited by commas, and press ENTER.
The Set Multiple menu appears, with the same options as the individual facility Framing
menu (see Figure 102 on page 186).
9. From the Set Multiple menu, select a framing type, and press ENTER.
61184500L1-6J 187
OPTI-6100 Maintenance and Troubleshooting Practice
188 61184500L1-6J
Status
ETHM/ETHM2 Status
To access the ETHM or ETHM2 Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select an ETHM/ETHM2 module, and press ENTER.
3. From the ETHM/ETHM2 module menu, select Status, and press ENTER.
The ETHM Status screen is shown in Figure 105.
Status
Equipment State : IS
61184500L1-6J 189
OPTI-6100 Maintenance and Troubleshooting Practice
1. IS
2. OOS-MA
Selection:
190 61184500L1-6J
Status
ETHM8/ETHM8-2 Status
To access the ETHM8 or ETHM8-2 Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select an ETHM8/ETHM8-2 module, and press ENTER.
3. From the ETHM8/ETHM8-2 module menu, select Status, and press ENTER.
4. The Status menu is displayed, as shown in Figure 108.
Status
Equipment State : IS
3. Facility #1
4. Facility #2
5. Facility #3
6. Facility #4
7. Facility #5
8. Facility #6
9. Facility #7
10. Facility #8
Selection:
61184500L1-6J 191
OPTI-6100 Maintenance and Troubleshooting Practice
5. From the Status menu, select an Ethernet facility, and press ENTER.
A Status screen for that Ethernet facility is displayed, as shown in Figure 108.
Facility #1 Status
192 61184500L1-6J
Status
ETHM8E Status
To access the ETHM8E Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select an ETHM8E module, and press ENTER.
3. From the ETHM8E module menu, select Status, and press ENTER.
4. The Status menu is displayed, as shown in Figure 109.
Status
Selection:
61184500L1-6J 193
OPTI-6100 Maintenance and Troubleshooting Practice
5. From the Status menu, select an Ethernet facility, and press ENTER.
A Status screen for that Ethernet facility is displayed, as shown in Figure 110.
Facility 1 Status
194 61184500L1-6J
Status
ETHM8EH Status
To access the ETHM8EH Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select an ETHM8EH module, and press ENTER.
3. From the ETHM8EH module menu, select Status, and press ENTER.
4. The Status menu is displayed, as shown in Figure 111.
Status
Selection:
61184500L1-6J 195
OPTI-6100 Maintenance and Troubleshooting Practice
5. From the Status menu, select an Ethernet facility, and press ENTER.
A Status screen for that Ethernet facility is displayed, as shown in Figure 112.
Facility 1 Status
196 61184500L1-6J
Status
TRAM Status
To access the TRAM Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a TRAM module, and press ENTER.
3. From the TRAM module menu, select Status, and press ENTER.
The TRAM Status screen is shown in Figure 113.
Status
Equipment Provisioning : IS
Equipment State : IS ACT, PSI
Facility Provisioning : OOS-MA UAS
Facility State : OOS-MA UAS
61184500L1-6J 197
OPTI-6100 Maintenance and Troubleshooting Practice
TRAM3 Status
To access the TRAM3 Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a TRAM3 module, and press ENTER.
3. From the TRAM3 module menu, select Status, and press ENTER.
The TRAM3 Status screen is shown in Figure 114.
Status
198 61184500L1-6J
Status
O3TM Status
To access the O3TMIR, O3TMLR, O3TMM, or O3TME Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select an O3TM module, and press ENTER.
3. From the O3TM module menu, select Status, and press ENTER.
The O3TM Status screen is shown in Figure 115.
Status
1. Clock Status
2. Synchronization Message Status
Selection:
61184500L1-6J 199
OPTI-6100 Maintenance and Troubleshooting Practice
O12TME Status
To access the O12TME Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select an O12TME module, and press ENTER.
3. From the O12TME module menu, select Status, and press ENTER.
The O12TME Status screen is shown in Figure 116.
Status
1. Clock Status
2. Synchronization Message Status
Selection:
200 61184500L1-6J
Status
Status
Equipment State : IS
Facility State : OOS-AU FLT
MAC Address : 00:A0:C8:05:00:01
Link State : Down
GFP/PPP/X.86 Link State : Link Down, No Sync
Loopback : None
61184500L1-6J 201
OPTI-6100 Maintenance and Troubleshooting Practice
GEFM/GEFMEH Status
To access the GEFM or GEFMEH Status, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a GEFM or GEFMEH module, and press ENTER.
3. From the GEFM or GEFMEH module menu, select Status, and press ENTER.
The GEFM/GEFMEH Status screen is shown in Figure 118.
Status
Equipment State : IS
Facility State : OOS-AU FLT
MAC Address : 00:A0:C8:05:00:01
Link State : Down
GFP/PPP/X.86 Link State : Link Down, No Sync
Loopback : None
202 61184500L1-6J
Status
NOTE
Only slots containing modules can be selected from this menu.
Status
1. Clock Status
2. Shelf Status
Selection:
The OMMXCV Status screen displays module and facility status for each of the OMMXCV
modules. It also provides the alarm status of the OMMXCV modules and equipment fault.
The following two status screens are available from the OMMXCV Status screen:
• Clock Status
• Shelf Status
The following steps explain how to view these screens.
61184500L1-6J 203
OPTI-6100 Maintenance and Troubleshooting Practice
3. From the Status menu, select Clock Status, and press ENTER.
The OMMXCV Clock Status screen in shown in Figure 120.
Clock Status
The Clock Status screen displays the selected synchronization clock in use and the status
of the various clock sources.
4. Press ESC to return to the Status menu.
204 61184500L1-6J
Status
5. From the Status menu, select Shelf Status, and press ENTER.
The OMMXCV Shelf Status screen is shown in Figure 121.
Shelf Status
MS 1 : Empty
MS 2 : Empty
MS 3 : Empty
MS 4 : Empty
Selection:
The Shelf Status screen indicates which OMMXCV module is carrying the traffic, and the
status of Automatic Protection Switching.
6. Press ESC to return to the Status menu.
61184500L1-6J 205
OPTI-6100 Maintenance and Troubleshooting Practice
SYSTEM ALARMS
The OPTI-6100 system reports alarms in the following ways:
• LEDs
• Visual and audible outputs
• SONET Data Communications Channel
• TL1 access
• RS-485 interface
• Menu-accessed Alarm screens
The System Alarms menu is shown in Figure 122.
System Alarms
Selection :
206 61184500L1-6J
System Alarms
MS 1 - DS3EC1M3.... [None]
MS 2 - DS3EC1M3.... [None]
MS 3 - ............ [None]
MS 4 - ............ [None]
MS 5 - ............ [None]
MS 6 - ............ [None]
MS 7 - ............ [None]
MS 8 - ............ [None]
MS 9 - DS1M........ [None]
MS10 - ............ [None]
MS11 - ............ [None]
MS12 - ............ [None]
61184500L1-6J 207
OPTI-6100 Maintenance and Troubleshooting Practice
Alarm Logs
Alarm Logs displays a history of alarms on the OPTI-6100 system. The Stat column indicates
whether the alarm is active or clear. The bottom line on the screen shows the navigation
commands for this screen. Use (S)elect to change alarm log screens without returning to the
Shelf Alarm Status menu.
An example of a master alarm log is shown in Figure 124.
NOTE
To access the Alarm Logs from the Shelf Alarm Status menu, use
the legend at the bottom of the page. Select the alarm log to view,
and press ENTER.
208 61184500L1-6J
System Alarms
User-Definable Alarms
User-Definable Alarms includes alarms regarding the physical environment of the OPTI-6100
system, and also permits the alarm levels for ‘Module Removed’ alarms to be provisioned.
The User-Definable Alarms menu is illustrated in Figure 125.
User-Definable Alarms
1. Environmental Alarms
2. MS Module Removed Level : MAJOR
3. HS Module Removed Level : CRITICAL
Selection :
61184500L1-6J 209
OPTI-6100 Maintenance and Troubleshooting Practice
Environmental Alarms
The OPTI-6100 has a number of environmental alarms. There are three auxiliary inputs for
user-specified external alarms (plus 16 if the optional EFANM is equipped), two fan alarms,
and two power bus alarms. Each alarm has the following associated fields: description, level,
AID index, and condition code.
The Environmental Alarms menu is illustrated in Figure 126.
Environmental Alarms
Selection :
210 61184500L1-6J
System Alarms
4. From the Environmental Alarms menu, select Environmental Alarm Summary, and press ENTER.
The Environmental Alarm Summary menu is shown in Figure 127.
Selection :
MS Module Removed
MS Module Removed sets the level for the alarm which occurs when an MS Module is removed
from the OPTI-6100 chassis. The options are Minor, Major, or Critical.
HS Module Removed
HS Module Removed sets the level for the alarm which occurs when an HS Module is removed
from the OPTI-6100 chassis. The options are Minor, Major, or Critical.
61184500L1-6J 211
OPTI-6100 Maintenance and Troubleshooting Practice
Alarm Chronology
By default, the alarms in the Alarm Logs are listed in ascending chronological order. To
change this order:
1. From the Main menu, select System Alarms, and press ENTER.
2. From the System Alarms menu, select Alarm Chronology, and press ENTER.
3. From the Alarm Chronology menu, select Descending or Ascending, and press ENTER.
212 61184500L1-6J
Loopbacks and Testing
DS1VM/DS1VM2 Loopbacks
NOTE
All loopbacks are detected from the Fiber Side (Network) towards
the facility. Loopbacks that are activated are the same as the local
loopback (toward the network) that can be activated by the craft
port and TL1.
Disabled
When the T1/E1 Loopback Detection setting for a channel is set to Disabled, then the
detection of any loop-up and loop-down codes/patterns is disabled for that channel.
CSU
When the T1/E1 Loopback Detection setting for a channel is set to CSU, that channel
responds with a T1/E1 loopback toward the network when it receives a CSU loop-up pattern
(00001b) for greater than 5 seconds. The loopback is canceled if a CSU loop-down pattern
(001b) is detected for greater than 5 seconds. The CSU loop-up and loop-down patterns can be
unframed, framed (code pauses for framing bit), or overwritten framed (code does not pause
for the framing bit which overwrites it).
NIU
When the T1/E1 Loopback Detection setting for a channel is set to NIU, that channel
responds with a T1/E1 loopback toward the network when it receives an NIU5 loop-up pattern
(00011b) for greater than 5 seconds. The loopback is canceled if an NIU5 loop-down pattern
(00111b) is detected for greater than 5 seconds. The NIU loop-up and loop-down patterns can
be unframed, framed (code pauses for framing bit), or overwritten framed (code does not pause
for the framing bit which overwrites it).
61184500L1-6J 213
OPTI-6100 Maintenance and Troubleshooting Practice
DS1VME/DS1VMT Loopbacks
NOTE
Loopbacks are detected from the Fiber Side (Network) towards the
facility. Loopbacks that are activated are the same as the local
loopback (toward the network) that can be activated by the craft
port and TL1.
Disabled
When the T1/E1 Loopback Detection setting for a channel is set to Disabled, then the
detection of any loop-up and loop-down codes/patterns is disabled for that channel.
AIS X
Framer
(1 of 28) LIU
(1 of 28)
X AIS
Framer
(1 of 28)
LIU
(1 of 28)
214 61184500L1-6J
Loopbacks and Testing
CSU
When the T1/E1 Loopback Detection setting for a channel is set to CSU, that channel
responds with a T1/E1 loopback toward the network when it receives a CSU loop-up pattern
(00001b) for greater than 5 seconds. The loopback is canceled if a CSU loop-down pattern
(001b) is detected for greater than 5 seconds. The CSU loop-up and loop-down patterns can be
unframed, framed (code pauses for framing bit), or overwritten framed (code does not pause
for the framing bit which overwrites it).
61184500L1-6J 215
OPTI-6100 Maintenance and Troubleshooting Practice
DS1M/DS1M2 Loopbacks
NOTE
All loopbacks are detected from the Fiber Side (Network) towards
the facility. Loopbacks that are activated are the same as the local
loopback (toward the network) that can be activated by the craft
port and TL1.
Disabled
When the T1/E1 Loopback Detection setting for a channel is set to Disabled, then the
detection of any loop-up and loop-down codes/patterns is disabled for that channel.
CSU
When the T1/E1 Loopback Detection setting for a channel is set to CSU, that channel
responds with a T1/E1 loopback toward the network when it receives a CSU loop-up pattern
(00001b) for greater than 5 seconds. The loopback is canceled if a CSU loop-down pattern
(001b) is detected for greater than 5 seconds. The CSU loop-up and loop-down patterns can be
unframed, framed (code pauses for framing bit), or overwritten framed (code does not pause
for the framing bit which overwrites it).
NIU
When the T1/E1 Loopback Detection setting for a channel is set to NIU, that channel
responds with a T1/E1 loopback toward the network when it receives an NIU5 loop-up pattern
(00011b) for greater than 5 seconds. The loopback is canceled if an NIU5 loop-down pattern
(00111b) is detected for greater than 5 seconds. The NIU loop-up and loop-down patterns can
be unframed, framed (code pauses for framing bit), or overwritten framed (code does not pause
for the framing bit which overwrites it).
Disabled
When the DS3 Loopback Detection setting for a channel is set to Disabled, then the detection
of any loop-up and loop-down codes/patterns is disabled for that channel.
Enabled
When the DS3 Loopback Detection item is set to Enabled and the DS3 framing mode is set for
C-BIT framing, DS3 loopbacks can be operated through either the DS3 FEAC channel. The
loopback codes that are detected over the DS3 FEAC channel are defined in ANSI T1.107-
1995, Figure 24 (07h followed by 1Bh for DS3 loop-back activate and 1Ch followed by 1Bh).
This is only valid in CBIT Framing mode.
216 61184500L1-6J
Loopbacks and Testing
NOTE
All loopbacks are detected from the Fiber Side (Network) towards
the facility. The loopbacks that are activated are the same as the
local loopback (toward the network) that can be activated by the
craft port and TL1.
Disabled
When the DS3 Loopback Detection setting for a channel is set to Disabled, then the detection
of any loop-up and loop-down codes is disabled for that channel.
AIS X
Framer
(1 of 3) LIU
(1 of 3)
AIS
LIU
(1 of 3)
61184500L1-6J 217
OPTI-6100 Maintenance and Troubleshooting Practice
X AIS
Framer
(1 of 3)
LIU
(1 of 3)
LIU
(1 of 28)
Enabled
When the DS3 Loopback Detection item is set to Enabled and the DS3 framing mode is set for
C-BIT framing, DS3 loopbacks can be operated through either the DS3 FEAC channel. The
loopback codes that are detected over the DS3 FEAC channel are defined in ANSI T1.107-
1995, Figure 24 (0x07 followed by 0x1B for DS3 loop-back activate and 0x1C followed by
0x1B). This is only valid in CBIT Framing mode.
218 61184500L1-6J
Loopbacks and Testing
CAUTION
When enabled, Facility Monitoring Mode disables all DS3 output
signals, disrupting all traffic on the module. Although the Receive
facility remains in operation, the Transmit facility is shut down.
61184500L1-6J 219
OPTI-6100 Maintenance and Troubleshooting Practice
PERFORMANCE MONITORING
Each of the OMM and tributary modules collect performance monitoring data for use in
troubleshooting and system maintenance. These screens are accessible through the menus
for each module.
OMM Modules
This section details the Performance Monitoring options for OMM modules.
OMM3
To access the Performance Monitoring options for any OMM3 module, complete the following
steps:
1. From the Main menu, select the desired OMM module, and press ENTER.
2. From the OMM menu, select Performance Monitoring, and press ENTER.
A Performance Monitoring menu for OMM3 module is shown in Figure 134.
Performance Monitoring
Selection:
From the Performance Monitoring menu, options can be selected to display detailed
performance monitoring data. Options to reset the performance monitoring data and
options to enable or disable the thresholds are available.
220 61184500L1-6J
Performance Monitoring
OMM12
To access the Performance Monitoring options for any OMM12 module, complete the following
steps:
1. From the Main menu, select the desired OMM module, and press ENTER.
2. From the OMM menu, select Performance Monitoring, and press ENTER.
A Performance Monitoring menu for OMM12 module is shown in Figure 135.
Performance Monitoring
Selection:
61184500L1-6J 221
OPTI-6100 Maintenance and Troubleshooting Practice
OMM48
To access the Performance Monitoring options for any OMM48 module, complete the following
steps:
1. From the Main menu, select the desired OMM module, and press ENTER.
2. From the OMM menu, select Performance Monitoring, and press ENTER.
A Performance Monitoring menu for OMM48 module is shown in Figure 136.
Performance Monitoring
Selection:
222 61184500L1-6J
Performance Monitoring
Tributary Modules
This section details the Performance Monitoring options for tributary modules.
Performance Monitoring
1. Port #1
2. Port #2
3. Port #3
4. Reset All PM Data
Selection:
NOTE
The ETHM8, ETHM8-2, ETHM8E, and ETHM8EH Performance
Monitoring menus list eight ports. All submenus of the individual
ports are the same as in the ETHM or ETHM2, as shown on the fol-
lowing pages.
61184500L1-6J 223
OPTI-6100 Maintenance and Troubleshooting Practice
5. From the Performance Monitoring menu, select the port desired, and press ENTER.
The Performance Monitoring menu for Port #1 is shown in Figure 138.
Port #1
1. Daily Performance
2. Quarter Hourly Performance
Selection:
6. From the Performance Monitoring menu, select Daily Performance or Quarter Hourly Performance,
and press ENTER.
224 61184500L1-6J
Performance Monitoring
The Daily Performance and Quarter Hourly Performance options track the same data in
different time segments. The Daily Performance menu is shown in Figure 139.
Selection:
7. From the Performance Group menu, select Packet TX/RX Counts, and press ENTER.
A Performance Group Packet TX/RX Counts screen is shown in Figure 140.
5/17
Tx/Rx 64 Bytes : 0
Tx/Rx 65-127 Bytes : 0
Tx/Rx 128-255 Bytes : 0
Tx/Rx 256-511 Bytes : 0
Tx/Rx 512-1023 Bytes : 0
Tx/Rx 1024-1518 Bytes : 0
Tx/Rx 1519-1522 VLAN : 0
Selection:
61184500L1-6J 225
OPTI-6100 Maintenance and Troubleshooting Practice
5/17
Unavailable Seconds : 3488
Rx Bytes Total : 0
Rx Packets Total : 0
Rx FCS Errored Packets : 0
Rx Multicast Packets : 0
Rx Broadcast Packets : 0
Rx Total Control Frames : 0
Rx Pause Frames : 0
Rx Unknown Control Frames : 0
Selection:
226 61184500L1-6J
Performance Monitoring
5/17
Rx Unaligned Frames : 0
Rx Frame Length Errors : 0
Rx Invalid Symbols : 0
Rx False Carrier : 0
Rx Undersized Packets : 0
Rx Oversized Packets : 0
Rx Fragment Frames : 0
Rx Jabber Frames : 0
Selection:
5/17
Tx Bytes Total : 0
Tx Packets Total : 0
Tx Multicast Packets : 0
Tx Broadcast Packets : 0
Tx Pause Frames : 0
Tx Deferred Packets : 0
Tx Excessive DFR : 0
Tx Solo Collisions : 0
Tx Multi Collisions : 0
Tx Late Collisions : 0
Selection:
61184500L1-6J 227
OPTI-6100 Maintenance and Troubleshooting Practice
8/26
Tx Excessive Collisions : 0
Tx Total Collisions : 0
Tx Jabber Frames : 0
Tx FCS Errored Frames : 0
Tx Control Frames : 0
Tx Oversized Packets : 0
Tx Undersized Packets : 0
Tx Fragmented Frames : 0
Selection:
228 61184500L1-6J
Performance Monitoring
DS3EC1M
To access the Performance Monitoring options for the DS3EC1M, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS3EC1M module, and press ENTER.
3. From the DS3EC1M module menu, select Performance Monitoring, and press ENTER.
NOTE
Depending on the Board Operating Mode selected, the menu title
reads ADTRAN DS3 LineCard or ADTRAN EC1 LineCard.
4. From the Performance Monitoring menu, select Daily Performance, Quarter Hourly Performance, or
Reset all PM Data, and press ENTER.
A DS3EC1M Daily Performance screen is shown in Figure 145.
Daily Performance
5/14
Code Violations : 0
Errored Seconds : 0
Severely Errored Seconds : 0
Unavailable Seconds : 2423
Fault Count : 1
Selection:
61184500L1-6J 229
OPTI-6100 Maintenance and Troubleshooting Practice
DS3EC1M3
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS3EC1M3 module, and press ENTER.
3. From the DS3EC1M3 module menu, select Performance Monitoring, and press ENTER.
NOTE
Depending on the Board Operating Mode selected, the menu title
reads ADTRAN Triple DS3 LineCard or ADTRAN Triple EC1 Line-
Card.
Daily Performance
Selection:
230 61184500L1-6J
Performance Monitoring
DS3M3E/DS3M3T
To access the Performance Monitoring options for the DS3M3E or DS3M3T, complete the
following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS3M3E or DS3M3T module, and press ENTER.
3. From the module menu, select Performance Monitoring, and press ENTER.
A DS3M3E Performance Monitoring menu is shown in Figure 147.
Performance Monitoring
Selection:
4. From the Performance Monitoring menu, select one DS3 or EC1 (DS3 mode shown above).
5. From the DS3 menu, select Daily Performance or Quarter Hourly Performance, and press ENTER.
61184500L1-6J 231
OPTI-6100 Maintenance and Troubleshooting Practice
Selection:
6. From the Performance menu selected, select a performance monitoring option, and press
ENTER.
A DS3M3E Daily Performance - Line Near End - Customer Interface screen is shown in
Figure 149.
10/6
Code Violations : 0
Errored Seconds : 0
Severely Errored Seconds : 0
Unavailable Seconds : 4914
Selection:
Figure 149. DS3M3E Daily Performance - Line Near End Customer Interface Screen
232 61184500L1-6J
Performance Monitoring
DS1M/DS1M2
To access the Performance Monitoring options for the DS1M or DS1M2, complete the following
steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS1M/DS1M2 module, and press ENTER.
3. From the DS1M/DS1M2 module menu, select Performance Monitoring, and press ENTER.
A DS1M Performance Monitoring menu is shown in Figure 150.
Performance Monitoring
Selection:
4. From the Performance Monitoring menu, select the type of data desired, and press ENTER.
Choose from the 28 DS1s or the DS3 feeding the module. There are also options for
resetting the performance monitoring data and options to enable or disable the
performance monitoring thresholds.
61184500L1-6J 233
OPTI-6100 Maintenance and Troubleshooting Practice
5. After selecting a DS1, a daily or quarter hourly performance threshold must be selected.
A Daily Performance screen for a DS1 is shown in Figure 151.
5/14
BiPolar Violations : 0
Errored Seconds : 0
Severely Errored Seconds : 0
Unavailable Seconds : 0
Fault Count : 0
Selection:
234 61184500L1-6J
Performance Monitoring
DS1VM/DS1VM2
To access the Performance Monitoring options for the DS1VM/DS1VM2, complete the
following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS1VM/DS1VM2 module, and press ENTER.
3. From the module menu, select Performance Monitoring, and press ENTER.
A DS1VM2 Performance Monitoring menu is shown in Figure 152.
Performance Monitoring
1. DS1 # 1 :
2. DS1 # 2 : 16. DS1 #16 :
3. DS1 # 3 : 17. DS1 #17 :
4. DS1 # 4 : 18. DS1 #18 :
5. DS1 # 5 : 19. DS1 #19 :
6. DS1 # 6 : 20. DS1 #20 :
7. DS1 # 7 : 21. DS1 #21 : 29. Reset PM Summary
8. DS1 # 8 : 22. DS1 #22 : 30. Reset All PM Data
9. DS1 # 9 : 23. DS1 #23 :
10. DS1 #10 : 24. DS1 #24 :
11. DS1 #11 : 25. DS1 #25 :
12. DS1 #12 : 26. DS1 #26 :
13. DS1 #13 : 27. DS1 #27 :
14. DS1 #14 : 28. DS1 #28 :
15. DS1 #15 :
Selection:
4. From the Performance Monitoring menu, select the required DS1, and press ENTER.
There are also options for resetting the performance monitoring data.
61184500L1-6J 235
OPTI-6100 Maintenance and Troubleshooting Practice
5. From the DS1 menu, select a daily or quarter hourly performance threshold.
Options appear to select a line or path, near end or far end, at the customer or network
interface. The DS1VM2 Quarter Hourly Performance menu is shown in Figure 153.
Selection:
6. From the daily or quarter hourly performance menu, select a line or path.
A Quarter Hourly Performance screen for a DS1 is shown in Figure 154.
Selection:
236 61184500L1-6J
Performance Monitoring
DS1VME/DS1VMT
To access the Performance Monitoring options for the DS1VME/DS1VMT, complete the
following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a DS1VME/DS1VMT module, and press ENTER.
3. From the DS1VME/DS1VMT Module menu, select Performance Monitoring, and press ENTER.
A DS1VME/DS1VMT Performance Monitoring menu is shown in Figure 155.
Performance Monitoring
4. From the Performance Monitoring menu, select the required DS1, and press ENTER.
There are also options for resetting the performance monitoring data.
61184500L1-6J 237
OPTI-6100 Maintenance and Troubleshooting Practice
5. After selecting a DS1, a daily or quarter hourly performance threshold must be selected.
A Quarter Hourly Performance menu for a DS1 is shown in Figure 156.
Selection:
6. From the Performance menu, select a performance report, and press ENTER.
A Quarter Hourly Performance - Line (Near End) - Customer Interface screen for a DS1 is
shown in Figure 157.
Selection:
238 61184500L1-6J
Performance Monitoring
61184500L1-6J 239
OPTI-6100 Maintenance and Troubleshooting Practice
TRAM
To access the Performance Monitoring options for the TRAM, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a TRAM module, and press ENTER.
3. From the TRAM Module menu, select Performance Monitoring, and press ENTER.
A TRAM Performance Monitoring menu is shown in Figure 158.
Performance Monitoring
Selection:
4. From the Performance Monitoring menu, select Line Near End, and press ENTER.
240 61184500L1-6J
Performance Monitoring
1. Daily Performance
2. Quarter Hourly Performance
3. Daily Thresholds
4. Quarter Hourly Thresholds
Selection:
Selection:
61184500L1-6J 241
OPTI-6100 Maintenance and Troubleshooting Practice
7. From the Performance Monitoring menu, select P-Bit Near End, and press ENTER.
8. A daily or quarter hourly performance or threshold must be selected.
The P-Bit Near End - Quarter Hourly Thresholds menu is shown in Figure 161.
1. Code Violations : 15
2. Errored Seconds : 12
3. Severely Errored Seconds : 3
4. Unavailable Seconds : 10
Selection:
242 61184500L1-6J
Performance Monitoring
TRAM3
To access the Performance Monitoring options for the TRAM3, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a TRAM3 module, and press ENTER.
3. From the TRAM3 Module menu, select Performance Monitoring, and press ENTER.
A TRAM3 Performance Monitoring menu is shown in Figure 162.
Performance Monitoring
Selection:
61184500L1-6J 243
OPTI-6100 Maintenance and Troubleshooting Practice
4. From the Performance Monitoring menu, select Line Near End, and press ENTER.
The Facility #1 Line Near End performance monitoring menu is shown in Figure 163.
1. Daily Performance
2. Quarter Hourly Performance
3. Daily Thresholds
4. Quarter Hourly Thresholds
5. Reset All PM Data
Selection:
Selection:
244 61184500L1-6J
Performance Monitoring
1. Code Violations : 15
2. Errored Seconds : 12
3. Severely Errored Seconds : 3
4. Unavailable Seconds : 10
Selection:
61184500L1-6J 245
OPTI-6100 Maintenance and Troubleshooting Practice
O3TM
To access the Performance Monitoring options for an OC-3 tributary module, complete the
following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a O3TM module, and press ENTER.
3. From the O3TM menu, select Performance Monitoring, and press ENTER.
A O3TM Performance Monitoring menu is shown in Figure 166.
Performance Monitoring
Selection:
246 61184500L1-6J
Performance Monitoring
O12TME
To access the Performance Monitoring options for the O12TME module, complete the following
steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select an O12TME module, and press ENTER.
3. From the O12TME menu, select Performance Monitoring, and press ENTER.
A O12TME Performance Monitoring menu is shown in Figure 167.
Performance Monitoring
Selection:
61184500L1-6J 247
OPTI-6100 Maintenance and Troubleshooting Practice
GECM
To access the Performance Monitoring options for the GECM, complete the following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a GECM module, and press ENTER.
3. From the GECM menu, select Performance Monitoring, and press ENTER.
A GECM Performance Monitoring menu is shown Figure 168.
Performance Monitoring
1. Daily Performance
2. Quarter Hourly Performance
3. Reset All PM Data
Selection:
248 61184500L1-6J
Performance Monitoring
GESM/GEMM
To access the Performance Monitoring options for the GESM or GEMM, complete the following
steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a GESM or GEMM module, and press ENTER.
3. From the GESM or GEMM menu, select Performance Monitoring, and press ENTER.
A GESM Performance Monitoring menu is shown in Figure 169.
Performance Monitoring
1. Daily Performance
2. Quarter Hourly Performance
3. Reset All PM Data
Selection:
61184500L1-6J 249
OPTI-6100 Maintenance and Troubleshooting Practice
GEFM/GEFMEH
To access the Performance Monitoring options for the GEFM or GEFMEH, complete the
following steps:
1. From the Main menu, select MS Modules, and press ENTER.
2. From the MS Modules menu, select a GEFM or GEFMEH module, and press ENTER.
3. From the GEFM or GEFMEH menu, select Performance Monitoring, and press ENTER.
A GEFM Performance Monitoring menu is shown in Figure 170.
Performance Monitoring
1. Daily Performance
2. Quarter Hourly Performance
3. Reset All PM Data
Selection:
250 61184500L1-6J
Protection Switching
PROTECTION SWITCHING
This section describes the various redundancy options available on the OPTI-6100. The
redundancy option is designed to protect traffic in the event of equipment or facility faults.
The OC-3 Protection Configuration screen is shown in Figure 171.
Selection:
61184500L1-6J 251
OPTI-6100 Maintenance and Troubleshooting Practice
Terminal Mode
The OMM48 Protection Configuration menu for Terminal mode is shown in Figure 172.
Protection Configuration
Selection:
HS Facility Protection
Linear Line APS provides protection at the line layer. Therefore, all of the STS SPEs carried in
an OC-N signal are protected together (i.e., if a switch occurs, all of the STS-1 Paths are
switched simultaneously). In addition to Line APS the OPTI-6100 terminal provides a
protection capability at the STS-1 Path layer.
The Line APS switch commands as defined in GR253 are supported in the terminal mode. The
switch commands that control each individual path switch as defined in GR1400 are
supported only in the UPSR mode.
252 61184500L1-6J
Protection Switching
61184500L1-6J 253
OPTI-6100 Maintenance and Troubleshooting Practice
Line APS
The 1+1 architecture of Linear APS in unidirectional mode is supported although the traffic
switch occurs at the STS-1 Path level on the tributary modules. AIS-P is generated
downstream if one of the automatic switch criteria defined in Automatic Switch Criteria
session is detected. The detection of AIS-P forces the drop selector, if enabled, to select traffic
from the other OMM module.
The line APS switch commands are also supported. The switch command is broadcast to all
the tributary modules through the embedded operations channel (EOC).
The OMM supports the 1+1 architecture with the following limitations:
• Unidirectional mode is supported.
• Nonrevertive switching is provided.
254 61184500L1-6J
Protection Switching
61184500L1-6J 255
OPTI-6100 Maintenance and Troubleshooting Practice
UPSR Mode
A path protection switched SHR architecture uses SONET path layer indications to trigger the
protection switching action. The switching action is performed at the STS or VT path layer to
recover from failure conditions, and does not involve line layer indications. Path layer indica-
tions include path layer defects (e.g., LOP-P) and maintenance signals (e.g., AIS-P). Path
switching of a specific path is independent of any other path’s status.
NOTE
A Forced Switch command permits traffic to be switched into a
facility that may be in a fault state.
256 61184500L1-6J
Protection Switching
Commands
The following switch commands can be issued to the APS controller either through TL1
commands or the menus:
• Clear:
– RLS-PROTNSW-STS1:(1-16)-HS1-STS-(1-4)-(1-3)
– RLS-PROTNSW-STS1:(1-16)-HS2-STS-(1-4)-(1-3)
– RLS-PROTNSW-STS1: (1-16)-(MS1-MS12)-STS-1-(1-3)
• Lockout of Path
– OPR-PROTNSW-STS1:(1-16)-HS1-STS-(1-4)-(1-3):LOCKOUT
– OPR-PROTNSW-STS1:(1-16)-HS2-STS-(1-4)-(1-3):LOCKOUT
– OPR-PROTNSW-STS1: (1-16)-(MS1-MS12)-STS-1-(1-3):LOCKOUT
• Forced Switch of Path
– OPR-PROTNSW-STS1:(1-16)-HS1-STS-(1-4)-(1-3):FRCD
– OPR-PROTNSW-STS1:(1-16)-HS2-STS-(1-4)-(1-3):FRCD
– OPR-PROTNSW-STS1: (1-16)-(MS1-MS12)-STS-1-(1-3):FRCD
• Manual Switch of Path
– OPR-PROTNSW-STS1:(1-16)-HS1-STS-(1-4)-(1-3):MAN
– OPR-PROTNSW-STS1:(1-16)-HS2-STS-(1-4)-(1-3):MAN
– OPR-PROTNSW-STS1: (1-16)-(MS1-MS12)-STS-1-(1-3):MAN
61184500L1-6J 257
OPTI-6100 Maintenance and Troubleshooting Practice
Protection Configuration
Selection:
Use the STS-1/STS-3c/VT1.5 Path Protection Configuration menus (STS-1 menu shown in
Figure 174) to enter a protection switch request.
Selection:
258 61184500L1-6J
Protection Switching
The STS-1/STS-3c/VT1.5 Path Protection Configuration menus include the following options:
• Lockout of Protection: Prevents all traffic from switching to the protection module. If the
traffic is currently on the protection module, it is switched back to the working module.
• Forced Switch to Protection: All traffic is switched to the protection module unless the
Lockout of Protection or Forced Switch to Working is in effect.
• Forced Switch to Working: All traffic is switched to the working module unless a Forced
Switch to Protection is in effect.
• Manual Switch to Protection: All traffic is switched to the protection module unless a request
of equal or greater priority is in effect.
• Manual Switch to Working: All traffic is switched to the working module unless a request of
equal or greater priority is in effect.
61184500L1-6J 259
OPTI-6100 Maintenance and Troubleshooting Practice
Revertive Switching
Each STS3c, STS1, and VT1.5 can be individually provisioned to support a revertive mode of
operation. The revertive switch is delayed by a Wait to Restore (WTR) period. The WTR period
is provisionable, also called Revertive Switch Time, from one to twelve minutes in one-minute
increments. If revertive switching is enabled then a preferred path can be provisioned. The
preferred path is the active path in a revertive system under normal conditions. The default
preferred path is HS1. Revertive Switching is Disabled by default.
STS-1 1 Provisioning
Selection:
260 61184500L1-6J
Protection Switching
Equipment Protection
A module can support one or more of the following entities:
• Facility Termination Points
• Path Termination Points
• External Clock Sources
• High Speed Maintenance Channel Communication link (HSMC) with the SCM
• DCC Communication link
• Embedded Operations Channel between the OMM and the tributary modules
• Cross copy communication with a mate module.
By default, the module in HS1 is considered to be the working module and the module in HS2
is considered to be the protect module. The tributary modules can be configured to provide
equipment protection in a 1:1 architecture. By default, the tributary modules in odd
numbered slots are considered to be the working slots and identical tributary modules in the
even numbered slots are considered to be the protect modules. The redundancy option must
be enabled for protection to work. The working modules are normally online and the protect
modules are normally offline but in a “hot standby” mode. The status is reversed if an
equipment protection switch occurs. Both OMM modules select traffic from the online
tributary module to transmit on their respective fibers. The online tributary module alone
transmits traffic downstream on the shared facilities that the protection pair supports. All
provisioning has to be identical on the two modules in a protecting pair.
Equipment switch commands in addition to automatic switch events are supported. A line
APS switch due to an HS facility fault does not switch the equipment. This is in interest of
minimizing the hits to the communication channels that can cause data to be lost.
61184500L1-6J 261
OPTI-6100 Maintenance and Troubleshooting Practice
Switch Commands
The Equipment Protection Configuration menu enables manual switch commands. Each
module can be commanded to go offline or online. The Equipment Protection Configuration
menu is shown in Figure 176.
1. Switch Now
Equipment Status : Online
Selection:
262 61184500L1-6J
Protection Switching
Figure 177 shows the OPTI-6100 in a Terminal Configuration. In the terminal configuration
the OPTI-6100 provides a single redundant high speed interface, and all the payloads
contained in the incoming fiber are dropped to tributary modules. Similarly all the payloads
contained in the outgoing fiber are added from the tributary modules. The diagram uses a
redundant pair of modules in slots MS1 and MS2 to illustrate how traffic is added and dropped.
STATUS
OMM3/12 1184504L1
STATUS
OMM3/12
ALARM ALARM
ON LINE ON LINE
TEST TEST
Add Add
Selector Selector
MSOCNEK0CAAM
MSOCNEK0CAAM
SOCNEK0CAA
SOCNEK0CAA
STATUS STATUS
DropALARM
DropALARM
ONLINE ONLINE
Selector Selector
TEST TEST
MSOC2490GAAM
MSOC2490GAAM
SOC2490GAA
SOC2490GAA
61184500L1-6J 263
OPTI-6100 Maintenance and Troubleshooting Practice
264 61184500L1-6J
Appendix A
Alarms List
INTRODUCTION
The following tables list and describe the alarms for the OPTI-6100 OMM and tributary
modules:
• Table A-1, “OMM3, OMM12, and OMM 48 Alarms” on page 2
• Table A-2, “DS1M and DS1M2 Alarms” on page 11
• Table A-3, “DS1VM Alarms” on page 14
• Table A-4, “DS1VME, DS1VMT, and DS1VM2 Alarms” on page 15
• Table A-5, “DS3EC1M and DS3EC1M3 Alarms” on page 21
• Table A-6, “DS3M3E and DS3M3T Alarms” on page 23
• Table A-7, “TRAM and TRAM3 Alarms” on page 30
• Table A-8, “Ethernet Module Alarms” on page 33
• Table A-9, “Gigabit Ethernet Module Alarms” on page 33
• Table A-10, “OC-3/12 Tributary Module Alarms” on page 34
61184500L1-6J A-1
ALARMS BY MODULE
A-2
Line Near End Coding Violation OC3/12/48 Facility Alert T-CVL adgenOMMXQtrLineCvAlm
(Qtr)
Line Near End Errored Seconds OC3/12/48 Facility Alert T-ESL adgenOMMXQtrLineEsAlm
(Qtr)
Line Near End Severely Errored OC3/12/48 Facility Alert T-SESL adgenOMMXQtrLineSesAlm
Seconds (Qtr)
Line Far End Coding Violation OC3/12/48 Facility Alert T-CV-LFE adgenOMMXQtrFELineCvAlm
(Qtr)
Line Far End Errored Seconds OC3/12/48 Facility Alert T-ES-LFE adgenOMMXQtrFELineEsAlm
(Qtr)
Line Far End Severely Errored OC3/12/48 Facility Alert T-SES-LFE adgenOMMXQtrFELineSesAlm
Seconds (Qtr)
Line Far End Unavailable Seconds OC3/12/48 Facility Alert T-UAS-LFE adgenOMMXQtrFELineUasAlm
(Qtr)
Path Near End Coding Violation STS-1 Facility Alert T-CVP adgenOMMXQtrPathCvAlm
(Qtr)
Path Near End Errored Seconds STS-1 Facility Alert T-ESP adgenOMMXQtrPathEsAlm
(Qtr)
Path Near End Severely Errored STS-1 Facility Alert T-SESP adgenOMMXQtrPathSesAlm
Seconds (Qtr)
Path Far End Coding Violation STS-1 Facility Alert T-CV-PFE adgenOMMXQtrFEPathCvAlm
(Qtr)
Table A-1. OMM3, OMM12, and OMM 48 Alarms (Continued)
61184500L1-6J
Path Far End Errored Seconds STS-1 Facility Alert T-ES-PFE adgenOMMXQtrFEPathEsAlm
(Qtr)
Path Far End Severely Errored STS-1 Facility Alert T-SES-PFE adgenOMMXQtrFEPathSesAlm
Seconds (Qtr)
Path Far End Unavailable Seconds STS-1 Facility Alert T-UAS-PFE adgenOMMXQtrFEPathUasAlm
(Qtr)
Path Near End Coding Violation STS-3 Facility Alert T-CVP adgenSonetTHSTS3CQPNCVSetAlm
(Qtr)
Path Near End Errored Seconds STS-3 Facility Alert T-ESP adgenSonetTHSTS3CQPNESSetAlm
(Qtr)
Path Near End Severely Errored STS-3 Facility Alert T-SESP adgenSonetTHSTS3CQPNSESSetAlm
Seconds (Qtr)
Path Far End Coding Violation STS-3 Facility Alert T-CV-PFE adgenSonetTHSTS3CQPFCVSetAlm
(Qtr)
Path Far End Errored Seconds STS-3 Facility Alert T-ES-PFE adgenSonetTHSTS3CQPFESSetAlm
(Qtr)
Path Far End Severely Errored STS-3 Facility Alert T-SES-PFE adgenSonetTHSTS3CQPFSESSetAlm
Path Far End Unavailable Seconds STS-3 Facility Alert T-UAS-PFE adgenSonetTHSTS3CQPFUASSetAlm
(Qtr)
VT1.5 Near End Coding Violation VT1.5 Facility Alert T-CV-V adgenOMMXQtrVTNECvAlm
(Qtr)
VT1.5 Near End Errored Seconds VT1.5 Facility Alert T-ES-V adgenOMMXQtrVTNEEsAlm
(Qtr)
VT1.5 Near End Severely Errored VT1.5 Facility Alert T-SES-V adgenOMMXQtrVTNESesAlm
Seconds (Qtr)
A-5
Table A-1. OMM3, OMM12, and OMM 48 Alarms (Continued)
A-6
VT1.5 Far End Coding Violation VT1.5 Facility Alert T-CV-VFE adgenOMMXQtrVTFECvAlm
(Qtr)
VT1.5 Far End Errored Seconds VT1.5 Facility Alert T-ES-VFE adgenOMMXQtrVTFEEsAlm
(Qtr)
VT1.5 Far End Severely Errored VT1.5 Facility Alert T-SES-VFE adgenOMMXQtrVTFESesAlm
Seconds (Qtr)
Line Near End Coding Violation OC3/12/48 Facility Alert T-CVL adgenOMMXDayLineCvAlm
(Day)
Line Near End Errored Seconds OC3/12/48 Facility Alert T-ESL adgenOMMXDayLineEsAlm
(Day)
Line Near End Severely Errored OC3/12/48 Facility Alert T-SESL adgenOMMXDayLineSesAlm
Seconds (Day)
Line Far End Coding Violation OC3/12/48 Facility Alert T-CV-LFE adgenOMMXDayFELineCvAlm
61184500L1-6J
(Day)
Line Far End Errored Seconds OC3/12/48 Facility Alert T-ES-LFE adgenOMMXDayFELineEsAlm
(Day)
Table A-1. OMM3, OMM12, and OMM 48 Alarms (Continued)
61184500L1-6J
Line Far End Severely Errored OC3/12/48 Facility Alert T-SES-LFE adgenOMMXDayFELineSesAlm
Seconds (Day)
Line Far End Unavailable Seconds OC3/12/48 Facility Alert T-UAS-LFE adgenOMMXDayFELineUasAlm
(Day)
Path Near End Coding Violation STS-1 Facility Alert T-CVP adgenOMMXDayPathCvAlm
(Day)
Path Near End Errored Seconds STS-1 Facility Alert T-ESP adgenOMMXDayPathEsAlm
(Day)
Path Near End Severely Errored STS-1 Facility Alert T-SESP adgenOMMXDayPathSesAlm
Seconds (Day)
Path Far End Coding Violation STS-1 Facility Alert T-CV-PFE adgenOMMXDayFEPathCvAlm
(Day)
Path Far End Errored Seconds STS-1 Facility Alert T-ES-PFE adgenOMMXDayFEPathEsAlm
(Day)
Path Far End Severely Errored STS-1 Facility Alert T-SES-PFE adgenOMMXDayFEPathSesAlm
Seconds (Day)
Path Far End Unavailable Seconds STS-1 Facility Alert T-UAS-PFE adgenOMMXDayFEPathUasAlm
Path Near End Coding Violation STS-3 Facility Alert T-CVP adgenSonetTHSTS3CDPNCVSetAlm
(Day)
Path Near End Errored Seconds STS-3 Facility Alert T-ESP adgenSonetTHSTS3CDPNESSetAlm
(Day)
Path Near End Severely Errored STS-3 Facility Alert T-SESP adgenSonetTHSTS3CDPNSESSetAlm
Seconds (Day)
Path Far End Coding Violation STS-3 Facility Alert T-CV-PFE adgenSonetTHSTS3CDPFCVSetAlm
(Day)
Path Far End Errored Seconds STS-3 Facility Alert T-ES-PFE adgenSonetTHSTS3CDPFESSetAlm
(Day)
Path Far End Severely Errored STS-3 Facility Alert T-SES-PFE adgenSonetTHSTS3CDPFSESSetAlm
Seconds (Day)
Path Far End Unavailable Seconds STS-3 Facility Alert T-UAS-PFE adgenSonetTHSTS3CDPFUASSetAlm
(Day)
VT1.5 Near End Coding Violation VT1.5 Facility Alert T-CV-V adgenOMMXDayVTNECvAlm
(Day)
VT1.5 Near End Errored Seconds VT1.5 Facility Alert T-ES-V adgenOMMXDayVTNEEsAlm
(Day)
VT1.5 Near End Severely Errored VT1.5 Facility Alert T-SES-V adgenOMMXDayVTNESesAlm
Seconds (Day)
VT1.5 Far End Coding Violation VT1.5 Facility Alert T-CV-VFE adgenOMMXDayVTFECvAlm
(Day)
VT1.5 Far End Errored Seconds VT1.5 Facility Alert T-ES-VFE adgenOMMXDayVTFEEsAlm
(Day)
VT1.5 Far End Severely Errored VT1.5 Facility Alert T-SES-VFE adgenOMMXDayVTFESesAlm
Seconds (Day)
Local (By Remote) Loopback DS3 DS3 Facility Alert LPBKTERM adTAOMXDS1AlmDS3RemoteLPBKDIDSet
Local (By Remote) Loopback DS1 DS1 Facility Alert LPBKTERM adTAOMXDS1AlmDS1RemoteLPBKDIDSet
CBit Near End Coding Violation DS3 Facility Alert T-CVCP-P adTAOMXDS1QNCCVTHAlmSet
(Qtr)
CBit Near End Errored Seconds DS3 Facility Alert T-ESCP-P adTAOMXDS1QNCESTHAlmSet
(Qtr)
CBit Near End Severely Errored DS3 Facility Alert T-SESCP-P adTAOMXDS1QNCSESTHAlmSet
Seconds (Qtr)
CBit Far End Coding Violation DS3 Facility Alert T-CVCP-PFE adTAOMXDS1QFCCVTHAlmSet
(Qtr)
CBit Far End Errored Seconds DS3 Facility Alert T-ESCP-PFE adTAOMXDS1QFCESTHAlmSet
(Qtr)
CBit Far End Severely Errored DS3 Facility Alert T-SESCP-PFE adTAOMXDS1QFCSESTHAlmSet
Seconds (Qtr)
CBit Far End Unavailable Seconds DS3 Facility Alert T-UASCP-PFE adTAOMXDS1QFCUASTHAlmSet
(Qtr)
CBit Near End Coding Violation DS3 Facility Alert T-CVCP-P adTAOMXDS1DNCCVTHAlmSet
(Day)
Table A-2. DS1M and DS1M2 Alarms (Continued)
61184500L1-6J
CBit Near End Errored Seconds DS3 Facility Alert T-ESCP-P adTAOMXDS1DNCESTHAlmSet
(Day)
CBit Near End Severely Errored DS3 Facility Alert T-SESCP-P adTAOMXDS1DNCSESTHAlmSet
Seconds (Day)
CBit Far End Coding Violation DS3 Facility Alert T-CVCP-PFE adTAOMXDS1DFCCVTHAlmSet
(Day)
CBit Far End Errored Seconds DS3 Facility Alert T-ESCP-PFE adTAOMXDS1DFCESTHAlmSet
(Day)
CBit Far End Severely Errored DS3 Facility Alert T-SESCP-PFE adTAOMXDS1DFCSESTHAlmSet
Seconds (Day)
CBit Far End Unavailable Seconds DS3 Facility Alert T-UASCP-PFE adTAOMXDS1DFCUASTHAlmSet
(Day)
Local (By Remote) Loopback DS1 Diagnostic Facility Alert LPBKTERM adTAOMXVT15AlmRemoteLPBKDIDSet
Local (By Remote) Loopback DS1 Diagnostic Facility Alert LPBKTERM adTAOMXDS1VMEAlmRemoteLPBKDIDSet
Path Controlled Slip Seconds (Qtr) DS1 Facility Alert T-CSS-PN-C adTAOMXDS1VMEQCCSPCNAlmSet
Customer Interface Near End
Path Controlled Slip Seconds (Qtr) DS1 Facility Alert T-CSS-PF-C adTAOMXDS1VMEQCCSPCFAlmSet
Customer Interface Far End
Path Controlled Slip Seconds (Qtr) DS1 Facility Alert T-CSS-PN-N adTAOMXDS1VMEQCCSPNNAlmSet
Network Interface Near End
Path Controlled Slip Seconds (Qtr) DS1 Facility Alert T-CSS-PF-N adTAOMXDS1VMEQCCSPNFAlmSet
Network Interface Far End
Path Controlled Slip Seconds (Day) DS1 Facility Alert T-CSS-PN-C adTAOMXDS1VMEDCCSPCNAlmSet
Customer Interface Near End
Path Controlled Slip Seconds (Day) DS1 Facility Alert T-CSS-PF-C adTAOMXDS1VMEDCCSPCFAlmSet
Customer Interface Far End
Path Controlled Slip Seconds (Day) DS1 Facility Alert T-CSS-PN-N adTAOMXDS1VMEDCCSPNNAlmSet
Network Interface Near End
Path Controlled Slip Seconds (Day) DS1 Facility Alert T-CSS-PF-N adTAOMXDS1VMEDCCSPNFAlmSet
Network Interface Far End
Section Severely Errored Seconds (Qtr) EC1 Facility Alert T-SESS adTAOMXDS3EC1ALMTHQSectSESSet
Section Errored Framing Seconds (Qtr) EC1 Facility Alert T-SEFSS adTAOMXDS3EC1ALMTHQSectSEFSSet
Line Near End Coding Violation (Qtr) EC1 Facility Alert T-CVL adTAOMXDS3EC1ALMTHQLineNCVSet
Line Near End Errored Seconds (Qtr) EC1 Facility Alert T-ESL adTAOMXDS3EC1ALMTHQLineNESSet
A-21
Table A-5. DS3EC1M and DS3EC1M3 Alarms (Continued)
A-22
Line Near End Severely Errored EC1 Facility Alert T-SESL adTAOMXDS3EC1ALMTHQLineNSESSet
Seconds (Qtr)
Line Near End Unavailable Seconds EC1 Facility Alert T-UASL adTAOMXDS3EC1ALMTHQLineNUASSet
(Qtr)
Line Far End Coding Violation (Qtr) EC1 Facility Alert T-CV-LFE adTAOMXDS3EC1ALMTHQLineFCVSet
Line Far End Errored Seconds (Qtr) EC1 Facility Alert T-ES-LFE adTAOMXDS3EC1ALMTHQLineFESSet
Line Far End Severely Errored Seconds EC1 Facility Alert T-SES-LFE adTAOMXDS3EC1ALMTHQLineFSESSet
(Qtr)
Line Far End Unavailable Seconds (Qtr) EC1 Facility Alert T-UAS-LFE adTAOMXDS3EC1ALMTHQLineFUASSet
Section Severely Errored Seconds (Day) EC1 Facility Alert T-SESS adTAOMXDS3EC1ALMTHDSectSESSet
Section Errored Framing Seconds (Day) EC1 Facility Alert T-SEFSS adTAOMXDS3EC1ALMTHDSectSEFSSet
Line Near End Coding Violation (Day) EC1 Facility Alert T-CVL adTAOMXDS3EC1ALMTHDLineNCVSet
Line Near End Errored Seconds (Day) EC1 Facility Alert T-ESL adTAOMXDS3EC1ALMTHDLineNESSet
Line Near End Severely Errored EC1 Facility Alert T-SESL adTAOMXDS3EC1ALMTHDLineNSESSet
Seconds (Day)
Line Near End Unavailable Seconds EC1 Facility Alert T-UASL adTAOMXDS3EC1ALMTHDLineNUASSet
(Day)
Line Far End Coding Violation (Day) EC1 Facility Alert T-CV-LFE adTAOMXDS3EC1ALMTHDLineFCVSet
Line Far End Errored Seconds (Day) EC1 Facility Alert T-ES-LFE adTAOMXDS3EC1ALMTHDLineFESSet
Line Far End Severely Errored Seconds EC1 Facility Alert T-SES-LFE adTAOMXDS3EC1ALMTHDLineFSESSet
(Day)
61184500L1-6J
Line Far End Unavailable Seconds EC1 Facility Alert T-UAS-LFE adTAOMXDS3EC1ALMTHDLineFUASSet
(Day)
Table A-6. DS3M3E and DS3M3T Alarms
61184500L1-6J
Loss of Signal DS3 (Detected from DS3 Facility Major LOS adTAOMXDS3M3EAlmDS3LOSSet
Customer Interface)
Loss of Frame DS3 (Detected from DS3 Facility Major LOF-CP adTAOMXDS3M3EAlmDS3LOFCISet
Customer Interface)
Loss of Frame DS3 (Detected from DS3 Facility Major LOF-NI adTAOMXDS3M3EAlmDS3LOFNISet
Network Interface)
Line Near End Coding Violation EC1 Facility Alert T-CVL adTAOMXDS3M3EEC1AlmQTHLineCV
(Qtr)
Line Near End Errored Seconds EC1 Facility Alert T-ESL adTAOMXDS3M3EEC1AlmQTHLineES
(Qtr)
Line Near End Severely Errored EC1 Facility Alert T-SESL adTAOMXDS3M3EEC1AlmQTHLineSES
Seconds (Qtr)
Line Far End Coding Violation (Qtr) EC1 Facility Alert T-CV-LFE adTAOMXDS3M3EEC1AlmQFTHLineCV
Line Far End Errored Seconds EC1 Facility Alert T-ES-LFE adTAOMXDS3M3EEC1AlmQFTHLineES
(Qtr)
Line Far End Severely Errored EC1 Facility Alert T-SES-LFE adTAOMXDS3M3EEC1AlmQFTHLineSES
Seconds (Qtr)
Line Far End Unavailable Seconds EC1 Facility Alert T-UAS-LFE adTAOMXDS3M3EEC1AlmQFTHLineUAS
(Qtr)
61184500L1-6J
Line Near End Coding Violation EC1 Facility Alert T-CVL adTAOMXDS3M3EEC1AlmDTHLineCV
(Day)
Line Near End Errored Seconds EC1 Facility Alert T-ESL adTAOMXDS3M3EEC1AlmDTHLineES
(Day)
Line Near End Severely Errored EC1 Facility Alert T-SESL adTAOMXDS3M3EEC1AlmDTHLineSES
Seconds (Day)
Line Far End Coding Violation EC1 Facility Alert T-CV-LFE adTAOMXDS3M3EEC1AlmDFTHLineCV
(Day)
Line Far End Errored Seconds EC1 Facility Alert T-ES-LFE adTAOMXDS3M3EEC1AlmDFTHLineES
(Day)
Line Far End Severely Errored EC1 Facility Alert T-SES-LFE adTAOMXDS3M3EEC1AlmDFTHLineSES
Seconds (Day)
Line Far End Unavailable Seconds EC1 Facility Alert T-UAS-LFE adTAOMXDS3M3EEC1AlmDFTHLineUAS
Line Near End Coding Violation DS3 Facility Alert T-CVL adTAOMXTMUX3PMQTHAlmLCV
(Qtr)
Line Near End Errored Seconds DS3 Facility Alert T-ESL adTAOMXTMUX3PMQTHAlmLES
(Qtr)
Line Near End Severely Errored DS3 Facility Alert T-SESL adTAOMXTMUX3PMQTHAlmLSES
Seconds (Qtr)
CBit Near End Coding Violation DS3 Facility Alert T-CVCP-P adTAOMXTMUX3PMQTHAlmCCV
(Qtr)
CBit Near End Errored Seconds DS3 Facility Alert T-ESCP-P adTAOMXTMUX3PMQTHAlmCES
(Qtr)
CBit Near End Severely Errored DS3 Facility Alert T-SESCP-P adTAOMXTMUX3PMQTHAlmCSES
Seconds (Qtr)
CBit Far End Coding Violation DS3 Facility Alert T-CVCP-PFE adTAOMXTMUX3PMQFarEndTHAlmCCV
(Qtr)
CBit Far End Errored Seconds DS3 Facility Alert T-ESCP-PFE adTAOMXTMUX3PMQFarEndTHAlmCES
(Qtr)
CBit Far End Severely Errored DS3 Facility Alert T-SESCP-PFE adTAOMXTMUX3PMQFarEndTHAlmCSES
Seconds (Qtr)
Line Near End Coding Violation DS3 Facility Alert T-CVL adTAOMXTMUX3PMDTHAlmLCV
(Day)
Line Near End Errored Seconds DS3 Facility Alert T-ESL adTAOMXTMUX3PMDTHAlmLES
Line Near End Severely Errored DS3 Facility Alert T-SESL adTAOMXTMUX3PMDTHAlmLSES
Seconds (Day)
CBit Near End Coding Violation DS3 Facility Alert T-CVCP-P adTAOMXTMUX3PMDTHAlmCCV
(Day)
CBit Near End Errored Seconds DS3 Facility Alert T-ESCP-P adTAOMXTMUX3PMDTHAlmCES
(Day)
CBit Near End Severely Errored DS3 Facility Alert T-SESCP-P adTAOMXTMUX3PMDTHAlmCSES
Seconds (Day)
CBit Far End Coding Violation DS3 Facility Alert T-CVCP-PFE adTAOMXTMUX3PMDFarEndTHAlmCCV
(Day)
CBit Far End Errored Seconds DS3 Facility Alert T-ESCP-PFE adTAOMXTMUX3PMDFarEndTHAlmCES
(Day)
CBit Far End Severely Errored DS3 Facility Alert T-SESCP-PFE adTAOMXTMUX3PMDFarEndTHAlmCSES
Seconds (Day)
Section Severely Errored Seconds (Qtr) OC3/12 Facility Alert T-SESS adgenOXTMQtrSecSesAlm
Section Errored Framing Seconds (Qtr) OC3/12 Facility Alert T-SEFSS adgenOXTMQtrSecSefsAlm
Line Near End Coding Violation (Qtr) OC3/12 Facility Alert T-CVL adgenOXTMQtrLineCvAlm
Line Near End Errored Seconds (Qtr) OC3/12 Facility Alert T-ESL adgenOXTMQtrLineEsAlm
Line Near End Severely Errored Seconds OC3/12 Facility Alert T-SESL adgenOXTMQtrLineSesAlm
(Qtr)
Line Far End Coding Violation (Qtr) OC3/12 Facility Alert T-CV-LFE adgenOXTMQtrFELineCvAlm
Line Far End Errored Seconds (Qtr) OC3/12 Facility Alert T-ES-LFE adgenOXTMQtrFELineEsAlm
Line Far End Severely Errored Seconds OC3/12 Facility Alert T-SES-LFE adgenOXTMQtrFELineSesAlm
(Qtr)
Line Far End Unavailable Seconds (Qtr) OC3/12 Facility Alert T-UAS-LFE adgenOXTMQtrFELineUasAlm
Path Near End Coding Violation (Qtr) STS-1 Facility Alert T-CVP adgenOXTMQtrPathCvAlm
Path Near End Errored Seconds (Qtr) STS-1 Facility Alert T-ESP adgenOXTMQtrPathEsAlm
A-35
Table A-10. OC-3/12 Tributary Module Alarms (Continued)
A-36
Path Near End Severely Errored Seconds STS-1 Facility Alert T-SESP adgenOXTMQtrPathSesAlm
(Qtr)
Path Near End Unavailable Seconds (Qtr) STS-1 Facility Alert T-UASP adgenOXTMQtrPathUasAlm
Path Far End Coding Violation (Qtr) STS-1 Facility Alert T-CV-PFE adgenOXTMQtrFEPathCvAlm
Path Far End Errored Seconds (Qtr) STS-1 Facility Alert T-ES-PFE adgenOXTMQtrFEPathEsAlm
Path Far End Severely Errored Seconds STS-1 Facility Alert T-SES-PFE adgenOXTMQtrFEPathSesAlm
(Qtr)
Path Far End Unavailable Seconds (Qtr) STS-1 Facility Alert T-UAS-PFE adgenOXTMQtrFEPathUasAlm
Section Severely Errored Seconds (Day) OC3/12 Facility Alert T-SESS adgenOXTMDaySecSesAlm
Section Errored Framing Seconds (Day) OC3/12 Facility Alert T-SEFSS adgenOXTMDaySecSefsAlm
Line Near End Coding Violation (Day) OC3/12 Facility Alert T-CVL adgenOXTMDayLineCvAlm
Line Near End Errored Seconds (Day) OC3/12 Facility Alert T-ESL adgenOXTMDayLineEsAlm
Line Near End Severely Errored Seconds OC3/12 Facility Alert T-SESL adgenOXTMDayLineSesAlm
(Day)
Line Near End Unavailable Seconds (Day) OC3/12 Facility Alert T-UASL adgenOXTMDayLineUasAlm
Line Far End Coding Violation (Day) OC3/12 Facility Alert T-CV-LFE adgenOXTMDayFELineCvAlm
Line Far End Errored Seconds (Day) OC3/12 Facility Alert T-ES-LFE adgenOXTMDayFELineEsAlm
Line Far End Severely Errored Seconds OC3/12 Facility Alert T-SES-LFE adgenOXTMDayFELineSesAlm
(Day)
Line Far End Unavailable Seconds (Day) OC3/12 Facility Alert T-UAS-LFE adgenOXTMDayFELineUasAlm
61184500L1-6J
Path Near End Coding Violation (Day) STS-1 Facility Alert T-CVP adgenOXTMDayPathCvAlm
Path Near End Errored Seconds (Day) STS-1 Facility Alert T-ESP adgenOXTMDayPathEsAlm
Table A-10. OC-3/12 Tributary Module Alarms (Continued)
61184500L1-6J
Path Near End Severely Errored Seconds STS-1 Facility Alert T-SESP adgenOXTMDayPathSesAlm
(Day)
Path Near End Unavailable Seconds (Day) STS-1 Facility Alert T-UASP adgenOXTMDayPathUasAlm
Path Far End Coding Violation (Day) STS-1 Facility Alert T-CV-PFE adgenOXTMDayFEPathCvAlm
Path Far End Errored Seconds (Day) STS-1 Facility Alert T-ES-PFE adgenOXTMDayFEPathEsAlm
Path Far End Severely Errored Seconds STS-1 Facility Alert T-SES-PFE adgenOXTMDayFEPathSesAlm
(Day)
Path Far End Unavailable Seconds (Day) STS-1 Facility Alert T-UAS-PFE adgenOXTMDayFEPathUasAlm
SUFFIXES
Any entity that is protected and in an IS state can be embellished with the following suffixes:
LPBK (LooPBacK)
The facility is in loopback.
61184500L1-6J B-1
OPTI-6100 Maintenance and Troubleshooting Practice
SERVICE STATES
Equipment States
OOS-AUMA UAS, UEQ (Out Of Service, AUtonomous MAintenance, UnASsigned,
UnEQuipped)
No module is plugged into the slot and no record for the equipment exists
in the database.
IS (In Service)
A module is plugged into the slot and a matching record exists in the
database. The module is set to IS.
B-2 61184500L1-6J
Appendix B, Service States Glossary - Service States
Facility States
OOS-MA UAS (Out Of Service, MAintenance, UnASsigned)
No record for the facility exists in the database.
IS (In Service)
A record for the facility exists in the database and is set to IS.
61184500L1-6J B-3
OPTI-6100 Maintenance and Troubleshooting Practice
Path States
OOS-MA UAS (Out Of Service, MAintenance, UnASsigned)
No record for the path exists in the database since no supporting facility
has yet been entered.
IS (In Service)
A record for the path exists in the database and is set to IS. A cross-
connect has been made to it.
B-4 61184500L1-6J
Appendix B, Service States Glossary - Service States
VT States
OOS-MA UAS (Out Of Service, MAintenance, UnASsigned)
No record for the VT exists in the database since no supporting path has
yet been entered.
IS (In Service)
A record for the VT exists in the database and is set to IS. A cross-connect
has been made to it.
61184500L1-6J B-5
OPTI-6100 Maintenance and Troubleshooting Practice
DCC States
OOS-MA UAS (Out Of Service, MAintenance, UnASsigned)
No record for the DCC Channel exists in the database.
IS (In Service)
A record for the DCC channel exists in the database and is set to IS.
B-6 61184500L1-6J
Appendix C
Access Privileges
Main Menu
System Controller
61184500L1-6J C-1
OPTI-6100 Maintenance and Troubleshooting Practice
System Controller/Configuration
System Controller/Provisioning
System Controller/Provisioning/General
C-2 61184500L1-6J
Appendix C, Access Privileges - Summary of Access Privileges
61184500L1-6J C-3
OPTI-6100 Maintenance and Troubleshooting Practice
IP Forwarding View/Change
C-4 61184500L1-6J
Appendix C, Access Privileges - Summary of Access Privileges
System ID View
System Controller/Provisioning/SNMP
61184500L1-6J C-5
OPTI-6100 Maintenance and Troubleshooting Practice
C-6 61184500L1-6J
Appendix C, Access Privileges - Summary of Access Privileges
System Controller/Provisioning/TL1
System Controller/Status
System Controller/Test
61184500L1-6J C-7
OPTI-6100 Maintenance and Troubleshooting Practice
System Alarms
C-8 61184500L1-6J
Appendix C, Access Privileges - Summary of Access Privileges
61184500L1-6J C-9
OPTI-6100 Maintenance and Troubleshooting Practice
C-10 61184500L1-6J
Appendix D
Warranty
ADTRAN Sales
Pricing/Availability:
800-827-0807
ADTRAN Repair/CAPS
Return for Repair/Upgrade:
(256) 963-8722
61184500L1-6J D-1
®