opti-6100 provision -61184500L1-6J

OPTI-6100

SCM1184500L1

ACO HST

STAT ALM

STATUS

ALARM

ON LINE

TEST

DS1VME1184515L2

STATUS

ALARM

ON LINE

TEST

DS1VME1184515L2

1

2

STATUS

ALARM

ON LINE

TEST

DS3M3E1184533L2

STATUS

ALARM

ON LINE

TEST

DS3M3E1184533L2

STATUS

ALARM

ONLINE

TEST

O3TMIR1184543L1

STATUS

ALARM

ONLINE

TEST

O3TMLR1184543L2

MS BLANK1184505L1

MS BLANK1184505L1

TRAM31184532L1

STATUS

ALARM

ON LINE

TEST

TRAM31184532L1

STATUS

ALARM

ON LINE

TEST

STATUS

ALARM

ONLINE

TEST

OMM12VIR1184504L3

STATUS

ALARM

ONLINE

TEST

OMM12VIR1184504L3ETHM8

1184524L1STATUS

ALM

TEST

LNKACT/

ENET2

ENET4

ENET6

ENET8

ENET1

ENET3

ENET5

ENET7

3

4

5

6

7

8

1

OPTI-6100 Maintenance and Troubleshooting PracticeDocument Part Number: 61184500L1-6JMay, 2007

®

OPTI-6100 Maintenance and Troubleshooting Practice

ii 61184500L1-6J

Front Matter

TrademarksAny brand names and product names included in this document are trademarks, registered trademarks, or trade names of their respective holders.

To the Holder of the DocumentThe contents of this document are current as of the date of publication. ADTRAN reserves the right to change the contents without prior notice.

In no event will ADTRAN be liable for any special, incidental, or consequential damages or for commercial losses even if ADTRAN has been advised thereof as a result of issue of this document.

901 Explorer BoulevardP.O. Box 140000

Huntsville, AL 35814-4000(256) 963-8000

©2007 ADTRAN, Inc.All Rights Reserved.

®

61184500L1-6J iii

Revision HistoryThe history of this document is as follows:

Reason for ReissueThis document has been updated to reflect the functionality of OPTI-6100 System Release 4.1. Release 4.1 adds:

• Tributary Modules: DS1M2, PWE3M, ETHM2, and ETHM8-2

• OMM3S Module

• Wirespeed Gigabit Ethernet support

• Optical Y-cable support

• Firmware updates: Refer to OPTI-6100 System Release 4.1 Release Notes (P/N 61184500L1-40) for details

Product Version Document Version Release Date

1.0 61184500L1-6A December, 2003

2.0 61184500L1-6B February, 2004

2.1 61184500L1-6C July, 2004

3.0 61184500L1-6D September, 2004

3.1 61184500L1-6E November, 2004

3.2 61184500L1-6F November, 2005

3.3 61184500L1-6G April, 2006

4.0 61184500L1-6J November, 2006

4.1 61184500L1-6J May, 2007


iv 61184500L1-6J

ConventionsThe 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.

NOTENotes inform the user of additional but essential information orfeatures.

CAUTIONCautions inform the user of potential damage, malfunction, or dis-ruption to equipment, software, or environment.

WARNINGWarnings inform the user of potential bodily pain, injury, or death.

Metric ConversionThe 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.

61184500L1-6J v

TrainingADTRAN 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: [email protected]


vi 61184500L1-6J

This page is intentionally blank.

61184500L1-6J vii

Contents

General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Alarm Response Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Local . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Remote [Menus through Telnet]: (requires IP connectivity) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Remote [TL-1 through Telnet or Rlogin] (requires IP or OSI connectivity) . . . . . . . . . . . . . . . . . . . . . . . . . 4Understanding AIDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Equipment AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Facility AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Path AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Examples: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Environmental AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Clock AID Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Login Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8System Controller Module (SCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8OMM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

OMM3 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10OMM12 Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12OMM48 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Tributary Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16DS1M Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16DS1M2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18DS1VM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20DS1VME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22DS1VMT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24DS1VM2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26DS3EC1M Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28DS3EC1M3 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30DS3M3E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32DS3M3T Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34ETHM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36ETHM2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38ETHM8 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40


viii 61184500L1-6J

ETHM8-2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42ETHM8E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44ETHM8EH Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46TRAM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48TRAM3 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50O3TMIR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52O3TMLR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54O3TMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56O3TME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58O12TME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60GECM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62GESM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64GEMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66GEFM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68GEFMEH Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Cross-Connect Module (OMMXCV) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Fan Assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

FANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74EFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75HFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76SFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Connect and Logon to System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Connecting through a VT100 Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

General Provisioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80UPSR Ring Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Provisioning a DS1 Circuit Through a UPSR Ring (VT1.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Provisioning a DS1 Circuit Through a UPSR Ring (DS3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Provisioning a DS3 Circuit Through a UPSR Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Provisioning an OC-3 Circuit Through a UPSR Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Element Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Management Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

TL1-Encapsulated Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Management Connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Management Application Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90IP Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

Ethernet Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91IP Route Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Default Route Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Interface Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94IP Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95IP Services and Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

OSI Networking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96TID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96DCC Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

DCC Link Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100NSAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Area Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Contents

61184500L1-6J ix

System ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102OSI Routing and Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

GNE – TL1 Translation Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Interoperability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Fujitsu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Lucent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Nortel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Cisco and Turin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

OSI Remote Menu Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Neighbors Display Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Login Bypass . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

IP Over OSI Tunneling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108IP Over OSI Tunnel Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109IP Over OSI Tunnel Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Proxy ARP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

IP Over OSI Tunnel – Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Step-By-Step Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115

IP Over OSI Tunnel – Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Step-By-Step Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

IP Over DCC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119Central Office/Remote Terminal Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

Enabling Central Office/Remote Terminal Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122Remote Terminal Alarm Reporting at the Central Office . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124IP Access to the Remote Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Operation With the OPTI-3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Operation With the Total Access 3000/3010 (OC-3 L5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125

System Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Software Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Upgrade SCM Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127Upgrade OMM Module Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Cross-Copy OMM Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128Upgrade Tributary Module Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129

Cross-Copy Tributary Module Firmware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129Security Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

Users Currently Logged On . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Edit User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Create New User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132

Enable Technical Support Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Enable SNMP Security Account Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Lock-Out User on Login Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Case-Sensitive Password/User-ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Null Password Accepted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Enable Lock-Out Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Number of Login Failure Before Lock-Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Lock-Out Duration in Seconds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Enable Advisory Warning Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133


x 61184500L1-6J

Security Advisory Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Enable Multiple Login Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134RADIUS Server Authentication Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

Restore Back to Default Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Access Tech Support Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Remote Menu Access Login Required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134RADIUS Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

ADTRAN Dictionary Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135ADTRAN-Telnet-Level Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136

Primary RADIUS Server Settings Menu. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Server Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Port Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Number Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Time Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Shared Secret . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138

Secondary RADIUS Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1383rd RADIUS Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1384th RADIUS Server Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Validate RADIUS Server Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Enable TL1 RADIUS Login . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Account Level if None Received . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Enable RADIUS Remote Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139

SNMP Access to RADIUS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139System Configuration Archive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

SCA AutoSave Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141AutoSave System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141AutoSave Only If Prov Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141AutoSave Filename Prefix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142AutoSave Filename Suffix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Max AutoSave File Instances . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142AutoSave Time (Hour) and AutoSave Time (Minute) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142AutoSave Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

SCA SCM Restore Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Restore Provisions to SCM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Restore SCM SCA Provisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Restore SCM Network Provisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Restore SCM Network Interface Provisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Restore SCM SNMP Provisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Restore SCM Security System Provisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

SCA Module Restore Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Card Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146MS1 to MS12, HS1, and HS2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Restore Provisions to Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Restore In Service Module Provisions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Restore to Empty Slot (Pre-Provision) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Contents

61184500L1-6J xi

SCA Operations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Remote File I/O Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147SCA TFTP Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147SCA Remote Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148SCA AutoSave Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

AutoSave Filename Prefix and Suffix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Current/Next AutoSave Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149AutoSave Only if Prov Changes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Cards in Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Cards With Prov Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Cards With Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Date/Time of Last SCA AutoSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Date/Time of Next SCA AutoSave . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149AutoSave Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

Perform SCA Save . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Perform SCA Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149SCA Save Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

SCA Remote Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Cards in Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Cards With Prov Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Cards With Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151SCA Save Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

SCA Restore Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151SCA Remote Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards in Shelf. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards With Prov Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards In SCA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards With Prov In SCA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards Restored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards Excluded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards NOT Restored . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152Cards w/ Exceptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152SCA Restore Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

System Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153SNMP Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Menu Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155

Auto Upgrade Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 162Local File Cache Expire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Auto Upgrade Config BasePath . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Auto Upgrade Config Filename . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Auto Upgrade Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Config File Refresh Interval . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Auto Upgrade Retries . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Auto Upgrade Status Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Chassis Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166DCC Interface Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167


xii 61184500L1-6J

OMM Module Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168OMM3/12 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168OMM48 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172

Tributary Module Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173DS3EC1M Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173DS3EC1M3 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174DS3M3E/DS3M3T Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175DS1M/DS1M2 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176DS1VM/DS1VM2 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Equipment Functional State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Facility Functional State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

DS1VME/DS1VMT Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Equipment Functional State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184

Framing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Facility Functional State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188

ETHM/ETHM2 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Equipment Functional State . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

ETHM8/ETHM8-2 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191ETHM8E Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193ETHM8EH Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195TRAM Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197TRAM3 Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198O3TM Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199O12TME Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200GECM, GESM, and GEMM Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201GEFM/GEFMEH Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

Cross-Connect Module Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203

System Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Shelf Alarm Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Alarm Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208User-Definable Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Environmental Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210MS Module Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211HS Module Removed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211

Alarm Chronology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Remote RT Alarm Reporting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212Alarm Contact Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

Loopbacks and Testing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213DS1VM/DS1VM2 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213CSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213NIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

DS1VME/DS1VMT Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214CSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215NIU (In-band Codes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215NIU (Out-of-band Codes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

Contents

61184500L1-6J xiii

DS1M/DS1M2 Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216DS1 Remote Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216CSU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216NIU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

DS3 Remote Loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216

DS3M3E/DS3M3T Loopback Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Enabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

DS3 Facility Monitoring Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

Performance Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220OMM Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

OMM3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220OMM12 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221OMM48 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

Tributary Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223ETHM, ETHM2, ETHM8, ETHM8-2, ETHM8E, and ETHM8EH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223DS3EC1M . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229DS3EC1M3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230DS3M3E/DS3M3T . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231DS1M/DS1M2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233DS1VM/DS1VM2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235DS1VME/DS1VMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

Performance Remote Messaging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239TRAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240TRAM3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243O3TM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246O12TME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247GECM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248GESM/GEMM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249GEFM/GEFMEH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

Protection Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Terminal Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252

HS Facility Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Protected STS-1 Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Mapping Protected Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Unprotected STS-1 Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253

Mapping Unprotected Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253Line APS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

APS Channel Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254Automatic Switch Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

Line Switch Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Path Switch Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255APS Switch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255Switch Initiation Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255


xiv 61184500L1-6J

Switch Completion Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255UPSR Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Automatic Switch Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256Hierarchy of Switch Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257Path Selection Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Revertive Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Path Protection Switch Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Path BER Detection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

Equipment Protection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Automatic Switch Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261Switch Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

Appendix AAlarms List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Alarms by Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-2

Appendix BService States Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Suffixes. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Service States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2Equipment States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-2Facility States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-3Path States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-4VT States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-5DCC States . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-6

Appendix CAccess Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Summary of Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Appendix DWarranty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Warranty and Customer Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1ADTRAN Sales . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1ADTRAN Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1ADTRAN Repair/CAPS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1Repair and Return Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . D-1

Figures

61184500L1-6J xv

Figures

Figure 1. Block Diagram of the OPTI-6100 System (MX Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1Figure 2. Block Diagram of the OPTI-6100 System (SMX Chassis) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Figure 3. Alarm Response List, TL1 through Telnet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Figure 4. System Controller Module (SCM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8Figure 5. OMM3LR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Figure 6. OMM12LR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Figure 7. OMM48 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Figure 8. DS1M Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Figure 9. DS1M2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Figure 10. DS1VM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Figure 11. DS1VME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Figure 12. DS1VMT Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 13. DS1VM2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Figure 14. DS3EC1M Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Figure 15. DS3EC1M3 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Figure 16. DS3M3E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 17. DS3M3T Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 18. ETHM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Figure 19. ETHM2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Figure 20. ETHM8 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Figure 21. ETHM8-2 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Figure 22. ETHM8E Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Figure 23. ETHM8EH Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 24. TRAM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Figure 25. TRAM3 Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 26. O3TMIR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 27. O3TMLR Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Figure 28. O3TMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 29. O3TME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Figure 30. O12TME Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 31. GECM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 32. GESM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 33. GEMM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 34. GEFM Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Figure 35. GEFMEH Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Figure 36. OMMXCV Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Figure 37. FANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 38. EFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Figure 39. HFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Figure 40. SFANM Assembly . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Figure 41. Provisioning a DS1 Circuit Through a UPSR Ring (VT1.5) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Figure 42. Provisioning a DS1 Circuit Through a UPSR Ring (DS3) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Figure 43. Provisioning a DS3 Circuit Through a UPSR Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Figure 44. Provisioning an OC-3 Circuit Through a UPSR Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Figure 45. Ethernet Interface Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91


xvi 61184500L1-6J

Figure 46. IP Route Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Figure 47. TL1 Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 48. DCC Interface Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Figure 49. DCC Interface Menu for High Speed 1 (LAPD Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Figure 50. SONET DCC Upper Layers Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Figure 51. TL1 Access Behind a Third-Party GNE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Figure 52. Remote Menu Access Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Figure 53. Remote Menu Access – Neighbors Only Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107Figure 54. OSI Tunnel Interface Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Figure 55. IP Route Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Figure 56. Edit Route Entry Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Figure 57. IP Over OSI Tunnel – Example 1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Figure 58. IP Over OSI Tunnel – Example 2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Figure 59. Sample “Route Print” Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Figure 60. DCC Interface Menu for High Speed 1 (PDCCO Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120Figure 61. PPP/DCCO Interface Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Figure 62. Network Management Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Figure 63. System Alarms Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Figure 64. System Administration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Figure 65. Security Administration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131Figure 66. Security Options Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132Figure 67. RADIUS Remote Authentication Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Figure 68. Primary RADIUS Server Authentication Settings Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Figure 69. System Configuration Archive (SCA) Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Figure 70. SCA AutoSave Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Figure 71. SCA SCM Restore Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Figure 72. SCA Module Restore Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145Figure 73. SCA Operations Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147Figure 74. SCA AutoSave Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Figure 75. SCA File Save Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Figure 76. SCA TFTP Restore Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Figure 77. System Event Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Figure 78. Auto Upgrade Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163Figure 79. Shelf Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Figure 80. DCC Interfaces Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167Figure 81. OMM3 Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168Figure 82. OMM3 Clock Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Figure 83. Synchronization Message Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 170Figure 84. OC-3 Shelf Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Figure 85. OMM48 Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Figure 86. DS3EC1M Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173Figure 87. DS3EC1M3 Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Figure 88. DS3M3E Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Figure 89. DS1M Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Figure 90. DS1 Facility Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Figure 91. Equipment Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Figure 92. DS1VM2 Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Figures

61184500L1-6J xvii

Figure 93. DS1 Facility Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Figure 94. Equipment Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Figure 95. DS1VM2 Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Figure 96. Facility Functional State Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Figure 97. DS1VME/DS1VMT Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Figure 98. DS1 Facility Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Figure 99. Equipment Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Figure 100. DS1VME Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Figure 101. Framing Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185Figure 102. Facility Framing Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Figure 103. Enter Facilities to Set Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Figure 104. Facility Functional State Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Figure 105. ETHM Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Figure 106. Equipment Functional State Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Figure 107. ETHM8 Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Figure 108. ETHM8 Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Figure 109. ETHM8E Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193Figure 110. ETHM8E Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Figure 111. ETHM8EH Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Figure 112. ETHM8EH Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196Figure 113. TRAM Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Figure 114. TRAM3 Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Figure 115. O3TM Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199Figure 116. O12TME Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Figure 117. GECM Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Figure 118. GEFM/GEFMEH Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Figure 119. OMMXCV Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Figure 120. OMMXCV Clock Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Figure 121. OMMXCV Shelf Status Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Figure 122. System Alarms Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Figure 123. Shelf Alarm Status Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Figure 124. Master Alarm Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Figure 125. User-Definable Alarms Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209Figure 126. Environmental Alarms Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210Figure 127. Environmental Alarm Summary Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 211Figure 128. DS1VME Line Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Figure 129. DS1VME Local Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214Figure 130. DS3M3E Line Loopback (DS3 Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Figure 131. DS3M3E Line Loopback (EC1 Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217Figure 132. DS3M3E Local Loopback (DS3 Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Figure 133. DS3M3E Local Loopback (EC1 Mode) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218Figure 134. OMM3 Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220Figure 135. OMM12 Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221Figure 136. OMM48 Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222Figure 137. ETHM Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223Figure 138. ETHM Port #1 Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224Figure 139. Port #1 - Performance Group Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225


xviii 61184500L1-6J

Figure 140. Performance Group - Packet TX/RX Counts Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225Figure 141. Performance Group - RX Status and Errors, Part 1 Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 226Figure 142. Performance Group - RX Errors, Part 2 Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Figure 143. Performance Group - TX Status and Errors Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227Figure 144. Performance Group - TX Errors, Part 2 Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228Figure 145. DS3EC1M Daily Performance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229Figure 146. DS3EC1M3 Daily Performance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230Figure 147. DS3M3E Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231Figure 148. DS3M3T Daily Performance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232Figure 149. DS3M3E Daily Performance - Line Near End Customer Interface Screen . . . . . . . . . . . . . . . . . 232Figure 150. DS1 Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233Figure 151. DS1 Daily Performance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234Figure 152. DS1VM2 Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235Figure 153. DS1 Quarter Hourly Performance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Figure 154. DS1 Quarter Hourly Performance Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236Figure 155. DS1VME/DS1VMT Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237Figure 156. DS1 Quarter Hourly Performance Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238Figure 157. DS1 Quarter Hourly Performance - Line (Near End) Customer Interface Screen . . . . . . . . . . . . 238Figure 158. TRAM Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240Figure 159. TRAM Line Near End PM Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Figure 160. Line Near End Daily Thresholds Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241Figure 161. P-Bit Near End Daily Thresholds Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 242Figure 162. TRAM3 Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243Figure 163. TRAM3 Line Near End PM Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Figure 164. Line Near End Daily Thresholds Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244Figure 165. P-Bit Near End Daily Thresholds Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245Figure 166. O3TM Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246Figure 167. O12TME Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247Figure 168. GECM Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248Figure 169. GESM Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249Figure 170. GEFM Performance Monitoring Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250Figure 171. OC-3 Protection Configuration Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251Figure 172. OMM48 Terminal Mode Protection Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252Figure 173. Protection Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Figure 174. Path Protection Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258Figure 175. STS-1 Path Provisioning Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260Figure 176. Equipment Protection Configuration Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262Figure 177. Terminal Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263

Tables

61184500L1-6J xix

Tables

Table 1. SCM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Table 2. OMM3 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Table 3. OMM12 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Table 4. OMM48 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Table 5. DS1M LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Table 6. DS1M2 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Table 7. DS1VM LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Table 8. DS1VME LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Table 9. DS1VMT LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Table 10. DS1VM2 LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Table 11. DS3EC1M Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Table 12. DS3EC1M3 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Table 13. DS3M3E Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Table 14. DS3M3T Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Table 15. ETHM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Table 16. ETHM2 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Table 17. ETHM8 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Table 18. ETHM8-2 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43Table 19. ETHM8E Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Table 20. ETHM8EH Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Table 21. TRAM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Table 22. TRAM3 Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Table 23. O3TMIR Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Table 24. O3TMLR Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Table 25. O3TMM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Table 26. O3TME Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Table 27. O12TME Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Table 28. GECM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Table 29. GESM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Table 30. GEMM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Table 31. GEFM Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Table 32. GEFMEH Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Table 33. OMMXCV Module LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Table 34. FANM Assembly LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Table 35. EFANM Assembly LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Table 36. HFANM Assembly LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Table 37. SFANM Assembly LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Table 38. Key to UPSR Ring Variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Table 39. Management Application Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90Table 40. Ports on Which the OPTI-6100 Listens . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Table 41. Ports To Which the OPTI-6100 Can Send Autonomous Messages . . . . . . . . . . . . . . . . . . . . . . . . 96Table 42. DCC Capacity by OMM Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Table 43. TCP Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Table 44. ADTRAN-Telnet-Level Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Table 45. Menu Events Stored in the System Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155


xx 61184500L1-6J

Table A-1. OMM3, OMM12, and OMM 48 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-2Table A-2. DS1M and DS1M2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-11Table A-3. DS1VM Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-14Table A-4. DS1VME, DS1VMT, and DS1VM2 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-15Table A-5. DS3EC1M and DS3EC1M3 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-21Table A-6. DS3M3E and DS3M3T Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-23Table A-7. TRAM and TRAM3 Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-30Table A-8. Ethernet Module Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-33Table A-9. Gigabit Ethernet Module Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-33Table A-10. OC-3/12 Tributary Module Alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .A-34Table C-1. OPTI-6100 Access Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .C-1

61184500L1-6J 1

OPTI-6100

GENERALThis 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.

OverviewThe 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.

Figure 1. Block Diagram of the OPTI-6100 System (MX Chassis)

HS1

HS2

SCM

OC-3/12/48

OC-3/12/48

I/0

Enet

X.25

Admin

RS-485

Craft

MS1 MS2 MS3 MS4 MS5 MS6 MS7 MS8 MS9 MS10 MS11 MS12

2 x Champ6 x BNC 2 x Champ6 x BNC 2 x Champ 6 x BNC

6 x BNCDS3

EC1

OC-3

OC-12

DS1

OC-3

OC-12

DS3

EC1

OC-3

OC-12

DS3

EC1

DS1

OC-3

OC-12

DS1

OC-3

OC-12

DS3

EC1

OC-3

OC-12

BITS


2 61184500L1-6J

Figure 2 shows a block diagram of the OPTI-6100 system SMX chassis.

Figure 2. Block Diagram of the OPTI-6100 System (SMX Chassis)

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.

NOTEEthernet and OC-3/12 tributary modules use front panel connec-tions and can be installed in any MS slot.

HS1

HS2

SCM

OC-3/12

OC-3/12

I/0EnetX.25

AdminRS-485

Craft

MS1 MS2 MS3 MS4

2 x Champ6 x BNC

6 x BNCDS3EC1OC-3

DS3EC1DS1OC-3

BITS

General

61184500L1-6J 3

Alarm Response ProceduresUse one of the following procedures to respond to an alarm:

Local1. 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.

Remote [Menus through Telnet]: (requires IP connectivity)1. Telnet into the system (using the default port of 23).

2. Login using the ADMIN account (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 the module in alarm, and press ENTER.


4 61184500L1-6J

Remote [TL-1 through Telnet or Rlogin] (requires IP or OSI connectivity)1. Telnet into the system (using port 2001), or Rlogin to the system.

2. Login using the ADMIN account (for information, refer to “Connect and Logon to System” on page 78).

3. Input the following commands:

ACT-USER

RTRV-ALM (Figure 3)

Note the AID in the alarm response(s), and refer to “Appendix A, Alarms List” for a description of the alarm.

Figure 3. Alarm Response List, TL1 through Telnet

Understanding AIDsOPTI-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.

FUZZ-MX 05-01-20 14:02:45

M DENY

IISP

/* Command block empty. */

;act-user::admin:::password;IP ?' - System Help Screen

<

FUZZ-MX 05-01-20 14:02:50

M COMPLD

;rtrv-alm-all;IP

<

FUZZ-MX 05-01-20 14:03:18

M COMPLD

"1-MS5,EQPT:MJ,CTNEQPT,SA,01-20,13-57-25,,,:\"Card Comm Fail\""



"1-MS10,EQPT:MJ,CTNEQPT,SA,12-14,09-35-31,,,:\"Card Removed\""



"1-HS1,EQPT:CR,CTNEQPT,SA,01-20,13-56-47,,,:\"Card Comm Fail\""

"1-HS2-1,OC12:CR,LOS,SA,12-14,09-17-20,NEND,,:\"OC12 LOS\""

"1-HS2,EQPT:MN,CTNEQPT,NSA,01-19,10-49-56,,,:\"Card Removed\""

;

General

61184500L1-6J 5

Equipment AID Structure

(chassis #) – (slot #)

(1-16) - (SCM)

(1-16) - (HS1, HS2)

(1-16) - (MS1 - MS12)

Examples:1-SCM (System controller module)

1-HS1 (High-speed HS1)

1-MS6 (Mid-speed MS6)

Facility AID Structure

(chassis #) – (slot #) – (port #)

(1-16) - (HS1, HS2) - 1

(1-16) - (MS1-MS12) - (1-29)

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)

Path AID Structure

NOTEFor OC-3 interfaces, which have only one STS-3, the STS-3 # isalways “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)


6 61184500L1-6J

Environmental AID Structure

(chassis #) – ENV – (input #)

(1-16) - ENV - (1-23)

For a list of inputs, refer to the OPTI-6100 TL-1 Reference Guide (P/N 61184500L1-35).

Clock AID Structure

(chassis #) – ENV – EXCLKINP (primary clock source)

(chassis #) – ENV – EXCLKINS (secondary clock source)

(1-16) - ENV - EXCLKINP

(1-16) - ENV - EXCLKINS

Login Failure

61184500L1-6J 7

LOGIN FAILUREIf 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.

CAUTIONThe Challenge Key response provided by ADTRAN Technical Sup-port is only valid for one session. At this time, security accountmaintenance must be completed with the appropriate accountsand 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.


8 61184500L1-6J

LEDSEach 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.

System Controller Module (SCM)The SCM (Figure 4) is equipped with four LEDs, and an Alarm Cut Off pushbutton labeled ACO. The ACO pushbutton doubles as an LED test switch. To test the LEDs of all the installed modules in the OPTI-6100, press and hold the ACO pushbutton. After a few seconds all of the LEDs on the modules should light yellow if they are in working order. All of the LEDs used in the OPTI-6100 system can display three different colors; red, yellow, and green. If during an LED test any LED fails to light, the LED may be defective and the module should be returned to ADTRAN for replacement or service.

Figure 4. System Controller Module (SCM)

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.

SCM1184500L1

ACO HST

STATUS

ALARM

CRAFT

LEDs

61184500L1-6J 9

Descriptions of the LEDs on the SCM are provided in Table 1.

Table 1. SCM Module LEDs

LED State Description Notes

STATUS Off Power failure Check the fuse and alarm panel for a blown fuse or make sure the module is fully seated in the chassis

Green Power up and initialization OK

Flashing Green Firmware is being downloaded The module is otherwise operational

ALARM Off No active alarms

Yellow Minor alarm(s) active Go to System Alarms screen for details

Red Major alarm(s) active Go to System Alarms screen for details

Flashing Red Critical alarm(s) active Go to System Alarms screen for details

HST Off SCM is in Client mode SCM can be accessed through Host SCM if daisy chained throughRS-485 interface

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

Green Alarm Cut Off activated External audible alarms are suppressed, if so equipped


10 61184500L1-6J

OMM Modules

OMM3 ModulesAll 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.

Figure 5. OMM3LR Module

STATUS

OMM3LR1184502L1

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 11

Descriptions of the LEDs on the OMM3 modules are provided in Table 2.

Table 2. OMM3 Module LEDs



Green Power up and initialization OK Service State is In Service (IS)

Flashing Green Module is being downloaded The module is otherwise operational

Yellow Out of Service-Unassigned No data traffic is being passed

Flashing Yellow Out of Service-Maintenance or being downloaded in OOS mode

Out of Service-Maintenance ormodule is being downloaded inOut of Service-Unassigned state; data traffic can be passed

Red Module failure Hardware or software failure

Flashing Red Firmware mismatch Working/Protect modules havedifferent firmware revisions; this error always occurs between upgrade of first and second module

ALARM Off Not a valid state LED failure or power failure

Green No alarms Module is operational

Yellow Active alerts Go to System Alarms screen for details

Red LOS or other hard alarms that indicate a facility problem

Go to System Alarms screen for details

ONLINE Off For 1+1 protection, Rx is not being dropped

Not active

Green For 1+1 protection, Rx is being dropped

Active

Yellow Equipment active System clock and intra-systemcommunications link

TEST Off Not in test mode

Yellow Terminal loopback Looped back towards the system

Flashing Yellow Facility loopback Looped back towards the customer


12 61184500L1-6J

OMM12 ModulesAll 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.

Figure 6. OMM12LR Module

STATUS

OMM12LR1184504L1

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 13

Descriptions of the LEDs on the OMM12 modules are provided in Table 3.

















Not active


Active






14 61184500L1-6J

OMM48 ModuleThe 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.

Figure 7. OMM48 Module

STATUS

OMM481184548L1

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 15

Descriptions of the LEDs on the OMM48 module are provided in Table 4.

















Not active


Active






16 61184500L1-6J

Tributary Modules

DS1M ModuleThe 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.

Figure 8. DS1M Module

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

LEDs

61184500L1-6J 17

Descriptions of the LEDs on the DS1M module are provided in Table 5.

Table 5. DS1M LEDs











Yellow Soft failure Includes signal format problems. Go to System Alarms screen for details



ONLINE Off Module is offline Tx is off

Green Module is online Tx is on

Flashing Yellow Module is locked online Protection is inhibited





18 61184500L1-6J

DS1M2 ModuleThe 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.

Figure 9. DS1M2 Module

STATUS

ALARM

ON LINE

TEST

DS1M21184513L2

LEDs

61184500L1-6J 19

Descriptions of the LEDs on the DS1M2 module are provided in Table 6.

Table 6. DS1M2 LEDs





















20 61184500L1-6J

DS1VM ModuleThe 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.

Figure 10. DS1VM Module

STATUS

ALARM

ON LINE

TEST

DS1VM1184515L1

LEDs

61184500L1-6J 21

Descriptions of the LEDs on the DS1VM module are provided in Table 7.

Table 7. DS1VM LEDs





















22 61184500L1-6J

DS1VME ModuleThe 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.

Figure 11. DS1VME Module

DS1VME1184515L2

STATUS

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 23

Descriptions of the LEDs on the DS1VME module are provided in Table 8.

Table 8. DS1VME LEDs





















24 61184500L1-6J

DS1VMT ModuleThe 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.

Figure 12. DS1VMT Module

DS1VME1184515L2

STATUS

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 25

Descriptions of the LEDs on the DS1VMT module are provided in Table 9.

Table 9. DS1VMT LEDs









Flashing Red Module occupies invalid slot Can also indicate:• Incompatible firmware revision• Redundancy provisioning error










Yellow Terminal loopback Module is in line or local loopback

Flashing Yellow Facility loopback Module is in DS1 Remote loopback


26 61184500L1-6J

DS1VM2 ModuleThe 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.

Figure 13. DS1VM2 Module

STATUS

ALARM

ON LINE

TEST

DS1VM21184515L4

LEDs

61184500L1-6J 27

Descriptions of the LEDs on the DS1VM2 module are provided in Table 10.

Table 10. DS1VM2 LEDs





















28 61184500L1-6J

DS3EC1M ModuleThe 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.

Figure 14. DS3EC1M Module

STATUS

ALARM

ON LINE

TEST

DS3EC1M1184503L1

LEDs

61184500L1-6J 29

Descriptions of the LEDs on the DS3EC1M Module are provided in Table 11.

Table 11. DS3EC1M Module LEDs





















30 61184500L1-6J

DS3EC1M3 ModuleThe 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.

Figure 15. DS3EC1M3 Module

STATUS

ALARM

ON LINE

TEST

DS3EC1M31184533L1

LEDs

61184500L1-6J 31

Descriptions of the LEDs on the DS3EC1M3 module are provided in Table 12.

Table 12. DS3EC1M3 Module LEDs








Red Module failure Hardware or software









Yellow Terminal Loopback Looped back towards the system


32 61184500L1-6J

DS3M3E ModuleThe 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.

Figure 16. DS3M3E Module

STATUS

ALARM

ON LINE

TEST

DS3M3E1184533L2

LEDs

61184500L1-6J 33

Descriptions of the LEDs on the DS3M3E module are provided in Table 13.

Table 13. DS3M3E Module LEDs



















34 61184500L1-6J

DS3M3T ModuleThe 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.

Figure 17. DS3M3T Module

STATUS

ALARM

ON LINE

TEST

DS3M3T1184533L3

LEDs

61184500L1-6J 35

Descriptions of the LEDs on the DS3M3T module are provided in Table 14.

Table 14. DS3M3T Module LEDs



















36 61184500L1-6J

ETHM ModuleThe 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.

Figure 18. ETHM Module

STATUSETHM1184510L1

ACT

LNK

ENET

1

ENET

2

ENET

3

LEDs

61184500L1-6J 37

Descriptions of the LEDs on the ETHM Module are provided in Table 15.

Table 15. ETHM Module LEDs









LNK(Link)(per port)

Off Ethernet link is down Can also indicate LED failure or power failure

Green Ethernet link is up Module is operational

ACT(Activity)(per port)

Off Port is neither receiving nortransmitting frames

Can also indicate LED failure or power failure

Yellow Port has a significant traffic load

Flashing Yellow Port has a low level of traffic


38 61184500L1-6J

ETHM2 ModuleThe 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.

Figure 19. ETHM2 Module

STATUSETHM21184510L2

ACT

LNK

ENET

1

ENET

2

ENET

3

LEDs

61184500L1-6J 39

Descriptions of the LEDs on the ETHM2 Module are provided in Table 16.

Table 16. ETHM2 Module LEDs









LNK(Link)(per port)

Off Ethernet link is down Can also indicate LED failure or power failure


ACT(Activity)(per port)

Off Port is neither receiving nortransmitting frames

Can also indicate LED failure or power failure


Flashing Yellow Port has a low level of traffic


40 61184500L1-6J

ETHM8 ModuleThe 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.

Figure 20. ETHM8 Module

ETHM81184524L1

STATUS

ALM

TEST

LNKACT/

ENET2

ENET4

ENET6

ENET8

ENET1

ENET3

ENET5

ENET7

1

2

3

4

5

6

7

8

LEDs

61184500L1-6J 41

Descriptions of the LEDs on the ETHM8 module are provided in Table 17.

Table 17. ETHM8 Module LEDs




Flashing Green Module is being downloaded The module is otherwiseoperational





ALM Off No power or power failure If power has been verified, the LED is damaged

Green Power up and initialization OK Indicates module is operational without any alarms

Red Alarm condition detected Indicates a facility problem such as Loss of Signal (LOS)

TEST Off Not in Test mode

Yellow Port is in Local Loopback mode

ACT/LNK(per port)

Off Ethernet link is down Port is neither receiving nor transmitting frames. Can also indicate LED failure or power failure


Flashing Green Port has a low level of traffic



42 61184500L1-6J

ETHM8-2 ModuleThe 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.

Figure 21. ETHM8-2 Module

ETHM8-21184524L2

STATUS

ALM

TEST

LNKACT/

ENET2

ENET4

ENET6

ENET8

ENET1

ENET3

ENET5

ENET7

1

2

3

4

5

6

7

8

LEDs

61184500L1-6J 43

Descriptions of the LEDs on the ETHM8-2 module are provided in Table 18.

Table 18. ETHM8-2 Module LEDs














ACT/LNK(per port)






44 61184500L1-6J

ETHM8E ModuleThe 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.

Figure 22. ETHM8E Module

ETHM8E1184525L1

STATUS

ALM

TEST

LNKACT/

ENET2

ENET4

ENET6

ENET8

ENET1

ENET3

ENET5

ENET7

1

2

3

4

5

6

7

8

LEDs

61184500L1-6J 45

Descriptions of the LEDs on the ETHM8E module are provided in Table 19.

Table 19. ETHM8E Module LEDs














ACT/LNK(per port)






46 61184500L1-6J

ETHM8EH ModuleThe 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.

Figure 23. ETHM8EH Module

ETHM8EH1184545L1

STATUS

ALM

TEST

LNKACT/

ENET2

ENET4

ENET6

ENET8

ENET1

ENET3

ENET5

ENET7

1

2

3

4

5

6

7

8

LEDs

61184500L1-6J 47

Descriptions of the LEDs on the ETHM8EH module are provided in Table 20.

Table 20. ETHM8EH Module LEDs














ACT/LNK(per port)






48 61184500L1-6J

TRAM ModuleThe 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.

Figure 24. TRAM Module

TRAM1184512L1

STATUS

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 49

Descriptions of the LEDs on the TRAM module are provided in Table 21.

Table 21. TRAM Module LEDs









Flashing Red Invalid slot, incompatiblesoftware revision, or redundantprovisioning


Green Module is operational

Yellow Provisioning failure

Red Facility problem, such as Loss of Signal (LOS)



Flashing Yellow Module protection inhibited

TEST Off Module is not in test mode

Yellow Module is in local loopback

Flashing Yellow Module is in remote loopback


50 61184500L1-6J

TRAM3 ModuleThe 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.

Figure 25. TRAM3 Module

TRAM31184532L1

STATUS

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 51

Descriptions of the LEDs on the TRAM3 module are provided in Table 22.

Table 22. TRAM3 Module LEDs









Flashing Red Invalid slot, incompatiblesoftware revision, or redundantprovisioning








TEST Off Module is not in test mode




52 61184500L1-6J

O3TMIR ModuleThe 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.

Figure 26. O3TMIR Module

STATUS

ALARM

ONLINE

TEST

O3TMIR1184543L1

LEDs

61184500L1-6J 53

Descriptions of the LEDs on the O3TMIR module are provided in Table 23.

Table 23. O3TMIR Module LEDs









Flashing Red Invalid slot, incompatible software revision, or redundant provisioning





ONLINE Off Module is offline Tx off

Green Module is online Tx on


TEST Off Module is in test mode




54 61184500L1-6J

O3TMLR ModuleThe 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.

Figure 27. O3TMLR Module

STATUS

ALARM

ONLINE

TEST

O3TMLR1184543L2

LEDs

61184500L1-6J 55

Descriptions of the LEDs on the O3TMLR module are provided in Table 24.

Table 24. O3TMLR Module LEDs





















56 61184500L1-6J

O3TMM ModuleThe 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.

Figure 28. O3TMM Module

STATUS

ALARM

ONLINE

TEST

O3TMM1184543L3

LEDs

61184500L1-6J 57

Descriptions of the LEDs on the O3TMM module are provided in Table 25.

Table 25. O3TMM Module LEDs





















58 61184500L1-6J

O3TME ModuleThe 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.

Figure 29. O3TME Module

STATUS

ALARM

ONLINE

TEST

O3TME1184543L4

LEDs

61184500L1-6J 59

Descriptions of the LEDs on the O3TME module are provided in Table 26.

Table 26. O3TME Module LEDs





















60 61184500L1-6J

O12TME ModuleThe 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.

Figure 30. O12TME Module

STATUS

ALARM

ONLINE

TEST

O12TME1184544L1

LEDs

61184500L1-6J 61

Descriptions of the LEDs on the O12TME module are provided in Table 27.

Table 27. O12TME Module LEDs





















62 61184500L1-6J

GECM ModuleThe 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.

Figure 31. GECM Module

STATUS LINK

TX RX

GECM1184516L1

GigE

LEDs

61184500L1-6J 63

Descriptions of the LEDs on the GECM module are provided in Table 28.

Table 28. GECM Module LEDs









LINK Off Ethernet link is down Can also indicate LED failure or power failure

Yellow Ethernet link is up Module is operational

TX Off Module is not transmitting through Ethernet

Green Module is transmitting through Ethernet

RX Off Module is not receiving through Ethernet

Green Module is receiving through Ethernet


64 61184500L1-6J

GESM ModuleThe 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.

Figure 32. GESM Module

GESM1184518L1

STATUS

LINK

TX

RX

LEDs

61184500L1-6J 65

Descriptions of the LEDs on the GESM module are provided in Table 29.

Table 29. GESM Module LEDs
















66 61184500L1-6J

GEMM ModuleThe 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.

Figure 33. GEMM Module

GEMM1184519L1

STATUS

LINK

TX

RX

LEDs

61184500L1-6J 67

Descriptions of the LEDs on the GEMM module are provided in Table 30.

Table 30. GEMM Module LEDs








Red Module failure








68 61184500L1-6J

GEFM ModuleThe 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.

Figure 34. GEFM Module

GEFM1184535L1

STATUS

ALARM

ONLINE

LINK

ACT

LEDs

61184500L1-6J 69

Descriptions of the LEDs on the GEFM module are provided in Table 31.

Table 31. GEFM Module LEDs






Flashing Yellow Out of Service-Maintenance orbeing downloaded in OOS mode


Red Hardware or firmware failure,or non-supported SFP installed

Flashing Red Incompatible firmware revision

ALARM Off Facility OOS-UAS Can also indicate no power, power failure, or LED failure

Green Operational without any alarms

Yellow Alert-level alarm present

Red Facility problem E.g., Loss of Signal (LOS)

ON LINE Off Tx off Module not transmitting through Ethernet

Green Tx on Module transmitting through Ethernet



ACT Off Rx off Module not receiving throughEthernet

Green Rx on Module receiving through Ethernet


70 61184500L1-6J

GEFMEH ModuleThe 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.

Figure 35. GEFMEH Module

GEFMEH1184546L1

STATUS

ALM

TEST

LINK

TX

RX

LEDs

61184500L1-6J 71

Descriptions of the LEDs on the GEFMEH module are provided in Table 32.

Table 32. GEFMEH Module LEDs






Flashing Yellow Out of Service-Maintenance orbeing downloaded in OOS mode


Red Hardware or firmware failure,or non-supported SFP installed

ALM Off Facility OOS-UAS Can also indicate no power, power failure, or LED failure

Green Operational without any alarms

Red Facility problem E.g., Loss of Signal (LOS)





TX Off Tx off Module not transmitting through Ethernet

Green Tx on Module transmitting throughEthernet

RX Off Rx off Module not receiving throughEthernet

Green Rx on Module receiving through Ethernet


72 61184500L1-6J

Cross-Connect Module (OMMXCV)The OMMXCV module (Figure 36) 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.

Figure 36. OMMXCV Module

STATUS

OMMXCV1184536L1

ALARM

ON LINE

TEST

LEDs

61184500L1-6J 73

Descriptions of the LEDs on the OMMXCV module are provided in Table 33.

Table 33. OMMXCV Module LEDs














ONLINE Off Module is offline Rx is not being dropped

Green Module is online Rx is being dropped (active)



Flashing Self-test during start-up


74 61184500L1-6J

Fan Assemblies

FANM AssemblyThe FANM Assembly (Figure 37) is equipped with two LEDs.

Figure 37. FANM Assembly

Descriptions of the LEDs on the FANM Assembly are provided in Table 34.

Table 34. FANM Assembly LEDs


PWR/STAN

Off Power failure Check the fuse and alarm panel for a blown fuse

Green Power up and initialization OK No alarms

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 failureMay also indicate loss of com-munication with fan module

More than one fan has failed, or A and B power has failed.

1184507L1

PWR=GRNSFAN=YEL

MFAN

FANM

ORDER REPLACEMENT FILTER NO. 1184509L1

LEDs

61184500L1-6J 75

EFANM AssemblyThe EFANM Assembly (Figure 38) is equipped with a single LED.

Figure 38. EFANM Assembly

Descriptions of the LED indications on the EFANM Assembly are provided in Table 35.

Table 35. EFANM Assembly LEDs


STATUS Off Power failure Check the fuse and alarm panel for a blown fuse





STATUS1184507L2

EFANM

ORDER REPLACEMENT FILTER NO. 1184509L1


76 61184500L1-6J

HFANM AssemblyThe HFANM Assembly (Figure 39) is equipped with two LEDs.

Figure 39. HFANM Assembly

Descriptions of the LEDs on the HFANM Assembly are provided in Table 36.

Table 36. HFANM Assembly LEDs


LED 1 Off Power failure Check the fuse and alarm panel for a blown fuse



LED 2 Off Power up and initialization OK



LEDs

61184500L1-6J 77

SFANM AssemblyThe SFANM Assembly (Figure 40) is equipped with a single LED.

Figure 40. SFANM Assembly

Descriptions of the LED indications on the SFANM Assembly are provided in Table 37.

Table 37. SFANM Assembly LEDs


STATUS Off Power failure Check the fuse and alarm panel for a blown fuse



Red Multiple fan or power failureMay also indicate loss ofcommunication with fanmodule


STATUS


78 61184500L1-6J

CONNECT AND LOGON TO SYSTEMThere are multiple ways to connect and logon to the system: menu session through the craft or Admin port, menu session through Telnet through the Ethernet interface, menu session over TL1 session, TL1 session through Admin port, TL1 session through X.25 (Network Management Port), or TL1 session through Telnet through Ethernet.

Connecting through a VT100 TerminalTo connect either a terminal or a PC emulating a terminal to the craft port, complete the following steps:

1. Set the parameters of the VT100 terminal to the following:

• 9600 baud

• 8 data bits

• No parity

• 1 stop bit

• No flow control

NOTEThe SCM craft port is defaulted to 9600 baud but has additionalavailable baud rates of 19200, 38400, 57600, and 115200 baud. Ifthe craft baud rate is set to an unsupported value and no otheraccess method (Telnet, TL1, ADMIN, etc.) is available, the craftbaud 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.

Connect and Logon to System

61184500L1-6J 79

NOTELogon names and passwords can be provisioned to be case sensi-tive for additional security.

Default accounts are ADMIN, READONLY, and READWRITE. Thedefault password for each of these accounts is PASSWORD. TheADMIN account has privileges to change passwords, accountnames, and other privileges of other accounts.

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.

NOTEIf valid authentication information is not entered within oneminute, the Telnet session expires.


80 61184500L1-6J

GENERAL PROVISIONINGAlthough much of the OPTI-6100 system is provisioned at the module level, there are functions that can be provisioned at a system level.

UPSR Ring ProvisioningThe OMM3VIR, OMM3VLR, OMM3VLR2, OMM12VIR, OMM12VLR, and OMM12VLR2 modules support a Unidirectional Path Switched Ring (UPSR) Add/Drop mode. The following pages detail various methods by which the UPSR mode can be employed, through TL1 messaging.

Provisioning a DS1 Circuit Through a UPSR Ring (VT1.5)To provision a DS1 circuit through a UPSR ring, mapping the DS1 into a VT1.5, complete the following steps:

1. Provision the HS equipment and OC-12 facility (if in an unassigned state) for every node in the ring.

ENT-EQPT:[<TID>]:1-HS1:::[<CLEI>]::IS;ENT-OC12:[<TID>]:1-HS1-1:::[<CLEI>]::IS;ENT-EQPT:[<TID>]:1-HS2:::[<CLEI>]::IS;ENT-OC12:[<TID>]:1-HS2-1:::[<CLEI>]::IS;

2. Provision the MS equipment (DS1VM) and DS1 facility (if in an unassigned state) for the two nodes (1 and 3) where the DS1 facility is terminated.

ENT-EQPT:[<TID>]:1-MSn:::[<CLEI>]::IS;ENT-T1:[<TID>]:1-MSn-1:::[<CLEI>]::IS;

If the equipment is protected:

ENT-EQPT::1-MS(n+1):::[<CLEI>]::IS;ENT-T1:[<TID>]:1-MSn-1:::[<CLEI>]::IS;

3. Provision the cross-connect on nodes 1 and 3.

ENT-CRS-VT1:[<TID>]:1-HS1-STS-x-y-z,1-MSn-STS-1-1-m;ENT-CRS-VT1:[<TID>]:1-HS2-STS-x-y-z,1-MSn-STS-1-1-m;

4. Provision the cross-connect on nodes 2 and 4 to pass through the VT1.

ENT-CRS-VT1:[<TID>]:1-HS1-STS-x-y-z,1-HS2-STS-x-y-z;

General Provisioning

61184500L1-6J 81

See Table 38 for a key to the variables included.

Table 38. Key to UPSR Ring Variables

Variable Represents Range

x STS1 group 1 to 4

y STS1 instance 1 to 3

z VT1 instance 1 to 28

n Valid slot ID N/A

m DS1 instance 1 to 28

p DS3 instance 1 to 3


82 61184500L1-6J

Figure 41 shows a DS1 UPSR ring with VT1.5 mapping.

Figure 41. Provisioning a DS1 Circuit Through a UPSR Ring (VT1.5)

MS12MS11 *3MS10MS9*1*3 MS8MS7 *1MS6MS5 *3MS4MS3 *1MS2MS1 *3 HS2HS1SCM

MS12MS11 *3MS10MS9*1*3 MS8MS7 *1MS6MS5 *3MS4MS3 *1MS2MS1 *3 HS2HS1SCM MS12MS11 *3MS10MS9*1*3 MS8MS7 *1MS6MS5 *3MS4MS3 *1MS2MS1 *3 HS2HS1SCM

OPTI-6100 #1

OPTI-6100 #3

OPTI-6100 #2OPTI-6100 #4

DS1

DS1

provision allpass throughtrafficSTSVT

cross copy provisioningto HS2

provision DS1cross connect to

HS1

provision allpass through

trafficSTS

VT

HS1

HS2

HS2

HS1

DS1VM

HS1

HS2

OMM12VIR




HS1

HS2

HS1

DS1VM

OMM12VIROMM12VIROMM12VIROMM12VIR

OMM12VIR


61184500L1-6J 83

Provisioning a DS1 Circuit Through a UPSR Ring (DS3)To provision a DS1 circuit through a UPSR ring, mapping the DS1 to a DS3, complete the following steps:



2. Provision the MS equipment (DS1M) and DS1 facility (if in an unassigned state) for the two nodes (1 and 3) where the DS1 facility is terminated.

NOTEThe 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;


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.


84 61184500L1-6J

Figure 42 shows a DS1 UPSR ring with DS3 mapping.

Figure 42. Provisioning a DS1 Circuit Through a UPSR Ring (DS3)



OPTI-6100 #1

OPTI-6100 #3

OPTI-6100 #2OPTI-6100 #4

DS1

DS1




HS1


trafficSTS

VT

HS1

HS2

HS2

HS1

DS1M

HS1

HS2

OMM12VIR




HS1

HS2

HS1

DS1M


OMM12VIR


61184500L1-6J 85

Provisioning a DS3 Circuit Through a UPSR RingTo provision a DS3 circuit through a UPSR ring, complete the following steps:



2. Provision the MS equipment (DS3M) and DS3 facility if in an unassigned state for the two nodes (1 and 3) where the DS3 facility is terminated.

ENT-EQPT:[<TID>]:1-MSn:::[<CLEI>]::IS;ENT-T3:[<TID>]:1-MSn-p:::[<CLEI>]::IS;


ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-y,1-MSn-STS-1-p;ENT-CRS-STS1:[<TID>]:1-HS2-STS-x-y,1-MSn-STS-1-p;

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;



86 61184500L1-6J

Figure 43 shows a DS3 UPSR ring.

Figure 43. Provisioning a DS3 Circuit Through a UPSR Ring



OPTI-6100 #1

OPTI-6100 #3

OPTI-6100 #2OPTI-6100 #4

DS3

DS3




HS1


trafficSTS

VT

HS1

HS2

HS2

HS1

TRAM

HS1

HS2

OMM12VIR




HS1

HS2

HS1


OMM12VIR

TRAM


61184500L1-6J 87

Provisioning an OC-3 Circuit Through a UPSR RingProvision the HS equipment and OC-12 facility (if in an unassigned state) for every node in the ring.


5. Provision the MS equipment (O3TM) and OC-3 facility (if in an unassigned state) for the two nodes (1 and 3) where the OC-3 facility is terminated.

ENT-EQPT:[<TID>]:1-MSn:::[<CLEI>]::IS;ENT-OC3:[<TID>]:1-MSn-1:::[<CLEI>]::IS;

6. Provision the cross-connects on nodes 1 and 3 identically.

ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-1,1-MSn-STS-1-1;ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-2,1-MSn-STS-1-2;ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-3,1-MSn-STS-1-3;ENT-CRS-STS1:[<TID>]:1-HS2-STS-x-1,1-MSn-STS-1-1;ENT-CRS-STS1:[<TID>]:1-HS2-STS-x-2,1-MSn-STS-1-2;ENT-CRS-STS1:[<TID>]:1-HS2-STS-x-3,1-MSn-STS-1-3;

Or, if the STS1s are concatenated:

ENT-CRS-STS3:[<TID>]:1-HS1-STS-x,1-MSn-STS-1;ENT-CRS-STS3:[<TID>]:1-HS2-STS-x,1-MSn-STS-1;

7. Provision the cross-connect on nodes 2 and 4 to pass through the 3 STS1s.

ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-1,1-HS2-STS-x-1;ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-2,1-HS2-STS-x-2;ENT-CRS-STS1:[<TID>]:1-HS1-STS-x-3,1-HS2-STS-x-3;

Or, if the STS1s are concatenated:

ENT-CRS-STS3:[<TID>]:1-HS1-STS-x,1-HS2-STS-x;



88 61184500L1-6J

Figure 44 shows an OC-3 UPSR ring.

Figure 44. Provisioning an OC-3 Circuit Through a UPSR Ring



OPTI-6100 #1

OPTI-6100 #3

OPTI-6100 #2OPTI-6100 #4

OC3

OC3




HS1


trafficSTS

VT

HS1

HS2

HS2

HS1

O3TM

HS1

HS2

OMM12VIR




HS1

HS2

HS1

O3TM


OMM12VIR

Element Management

61184500L1-6J 89

ELEMENT MANAGEMENTElement 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).

NOTESome parameters associated with the provisioning of the elementmanagement features are fixed or not accessible when the MountLocation of the system is set to Central Office or Remote Terminal.Setting the Mount Location to Central Office or Remote Terminal isonly appropriate for simple point-to-point applications as describedin “Central Office/Remote Terminal Applications” on page 122. Forflexibility in more complex or multi-vendor applications, the MountLocation should be set to Subtended (default).

Management ApplicationsThe 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 ApplicationsThe 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


90 61184500L1-6J

Management ConnectivityThere 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.

Management Application AccessTable 39 outlines which applications are available by way of each access method.

1. TL1 is available through the TL1 Cut-Through option in the TL1 Provisioning menu2. 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

Table 39. Management Application Access

Application Craft Port ADMIN Port X.25 RS-485 IP Network OSI Network

Menus Yes Yes No Yes Yes2 Yes4

TL1 Yes1 Yes1 Yes Yes Yes3 Yes

SNMP No No No No Yes No

FTP/TFTP No No No No Yes No

SNMP/TL15 No No No No Yes3 Yes

FTOT5 No No No No Yes3 Yes

Element Management

61184500L1-6J 91

IP NetworkingIP (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 InterfaceEthernet 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.

Figure 45. Ethernet Interface Menu

TID: HSV00001 OPTI-6100 System MM/DD/YY hh:mm

Unacknowledged Alarms: MX Chassis: 1

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 :

'?' - System Help Screen


92 61184500L1-6J

This menu includes the following options:

• Interface: Enables/disables the Ethernet interface

• IP Address: The IP address assigned to the interface

• Subnet Mask: Determines the range of IP address available through the Ethernet interface

Example: A value of 255.255.255.0 indicates that all addresses in the range of 10.25.15.0 through 10.25.15.255 are available.

• Gateway: This needs provisioning only when the Ethernet interface is used as the default route interface (refer to “Interface Gateway” on page 94)

• Link: The status of the link (read-only)

• MAC Address: A unique, fixed number assigned to all Ethernet interfaces at the time of manufacture (read-only)

IP Route TableThe 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:





5. From the IP Network Provisioning menu, select IP Route Table, and press ENTER.

Element Management

61184500L1-6J 93

Figure 46 illustrates the IP Route Table.

Figure 46. IP Route Table

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.



IP Route Table

IP Address Netmask Gateway Ifc NSAP

1. 10.25.15.97 255.255.255.0 10.25.15.254 Ether

2. 192.1.0.97 255.255.255.0 None PDCC0

3. 10.25.15.98 255.255.255.255 None OSItu *

Selection :

(C)reate


94 61184500L1-6J

Default Route InterfaceWhen the OPTI-6100 needs to send IP data to a destination address that is not reachable by any of the routes in the route table (including interface routes and manually entered routes), it sends the data to the Default Route Interface.

The Default Route Interface is provisioned in the IP Network Interfaces menu. To access this menu, log on to the OPTI-6100 as ADMIN and complete the following steps:






6. From the IP Network Interfaces menu, select Default Route Interface, and press ENTER.

The Default Route Interface can be set to “None” or any of the three IP interfaces:

• Ethernet

• OSI Tunnel

• PPP/DCC0

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.

Element Management

61184500L1-6J 95

IP ForwardingWhen 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:






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.

IP Services and PortsIP services are usually accessed over TCP and UDP ports. Connection-oriented services (such as Telnet) use TCP while connectionless services (such as SNMP) use UDP.

Table 40 outlines the IP services available on the OPTI-6100 along with the corresponding port numbers on which the OPTI-6100 is listening.

* = These ports are provisionable. The default values are listed.

Table 40. Ports on Which the OPTI-6100 Listens

Service Port Number Description

Telnet TCP 23 ASCII menu interface

SNMP UDP 161 Simple Network Management Protocol

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 theNetwork Management port

Terminal Server, ADMIN Port TCP 2004* Terminal server to device connected on the ADMIN port

Reserved TCP 71, 72, 73TCP 4000, 4001UDP 4000, 4001

Reserved for internal use


96 61184500L1-6J

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.

OSI NetworkingThe 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)

TIDThe 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:



3. From the Provisioning menu, select TL1, and press ENTER.

Table 41. Ports To Which the OPTI-6100 Can Send Autonomous Messages

Service Port Number Description

FTP TCP 21 File Transfer Protocol. The OPTI-6100 can send autonomous requests for file downloads to this port at the provisioned FTP server IP address.

TFTP UDP 69 Trivial File Transfer Protocol. The OPTI-6100 can send autonomous requests for file downloads to this port at the provisioned TFTP server IP address.

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.

Element Management

61184500L1-6J 97

Figure 47 illustrates the TL1 provisioning menu.

Figure 47. TL1 Menu

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 InterfacesThe 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:




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.


Unacknowledged Alarms: None MX Chassis: 1

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 :



98 61184500L1-6J

Figure 48 illustrates the DCC Interface menu.

Figure 48. DCC Interface Menu

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.

NOTEA DCC can be created for a SONET facility that is not yet equipped.

Table 42. DCC Capacity by OMM Type

OMM Module High-Speed DCCs Mid-Speed DCCs

OMM3__ (1184502L1, 4, 9–11) 1 3

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

1. High Speed 1 (HS 01 ): UpAITS

2. Mid Speed 05-1 (MS 05-1): UpAITS

3. Mid Speed 11-1 (MS 11-1): Dn

Selection :

(C)reate a new DCC interface

Element Management

61184500L1-6J 99

Figure 49 illustrates the DCC Interface menu which appears after selecting an existing DCC or creating a new one.

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

NOTEParameters listed below Service State cannot be altered when theDCC 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).



DCC Interface: High Speed 1

1. Name : High Speed 1

2. Service State : Out Of Service (OOS-MA)

3. DCC Mode : User

4. Window Size : 7

5. Response Timeout (msec) : 2000

6. Link Inactivity Timeout : 10

7. Max Retransmissions : 3

Max I-Frame Length : 512

Information Trans. Serv. : Acknowledged

Link Status : UpAITS

Selection :

(D)elete this DCC interface


100 61184500L1-6J

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.

CAUTIONThe remaining parameters should not be modified from the defaultvalues.

DCC Link Status

The last item on the DCC Interface menu is the Link Status, which can be one of the following values:

• UpAITS: Link is up and operating normally

• DnMode: Link is down because both ends are the same mode (both User or both Network)

• DnDisc: Link is down because the far-end has been disabled

• Dn: Link is down for other reasons (e.g., facility fault or the far-end doesn't support DCC)

• DnUas: Link has not yet been started (this should be a temporary indication)

• DnDsbl: No DCC operations have been started (this should be a temporary indication)

NSAPThe 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:





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.

Element Management

61184500L1-6J 101

Area Address

The Area Address is variable and must be provisioned according to the network environment in which the network element is deployed.

NOTEIf Mount Location is Central Office or Remote Terminal, the DCCassociated with High Speed 1 cannot be provisioned. This DCC isautomatically created and locked for support of the point-to-pointfeatures outlined in “Central Office/Remote Terminal Applications”on page 122.

Figure 50 illustrates the SONET DCC Upper Layers Provisioning menu.

Figure 50. SONET DCC Upper Layers Provisioning Menu



SONET DCC Upper Layers Provisioning

1. NSAP Area Address : 39840F80000000000000000000

System ID : 00A0C8050441

Selection :



102 61184500L1-6J

Two formats are supported for the Area Address.

• ISO DCC: This format is a fixed-length field containing 26 hexadecimal characters starting with a prefix of ‘39’. Fujitsu, Lucent, Alcatel, and Tellabs equipment support this format.

39840F80000000000000000000 is the default value.

This format supports three custom fields.

– Country code (identified in blue, above)

– Routing domain (identified in green, above)

– Routing area (identified in red, above)

• Private: This format is a fixed-length field containing 6 hexadecimal characters starting with a prefix of 49. Nortel equipment supports the Private format.

490000 is the default value.

This format supports two custom fields.

– Routing domain (identified in green, above)

– Routing area (identified in red, above)

An Area Address that doesn’t conform to either of the predefined formats can be entered by selecting User-Defined Address. A user-defined address can be any hexidecimal value between 6 and 26 characters long.

NOTECommunications across the SONET DCC is lost if the NSAP AreaAddress 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.

NOTEIf Mount Location is set to Central Office or Remote Terminal, theSystem ID is either 111111111111 or 222222222222. If MountLocation is set to Subtended, the System ID is the same as theMAC address.

OSI Routing and ForwardingRouting and forwarding of OSI traffic is automatic and always enabled. No user provisioning is required for these functions.

Element Management

61184500L1-6J 103

GNE – TL1 Translation DeviceTL1 is the interoperable (with non-ADTRAN equipment) application that the OPTI-6100 supports on the OSI network. The TL1 Translation Device (T-TD) standard allows TL1 commands originating from a management system in an IP network to be translated by a SONET GNE (Gateway Network Element) device to an OSI network. Refer to NSIF-033-1999 for details.

The OPTI-6100 supports T-TD and can be used as a GNE in a multi-vendor SONET network. Likewise, the OPTI-6100 is accessible through TL1 when deployed in a SONET network behind a non-ADTRAN GNE that meets the requirements of NSIF-033-1999.

Over either IP or OSI networks, the OPTI-6100 supports the SNMP and FTOT management protocols that encapsulate data in universal TL1 commands and responses. The Total Access EMS uses these TL1-encapsulated protocols to manage OPTI-6100s deployed behind third-party GNEs. Refer to “TL1-Encapsulated Applications” on page 89.

Figure 51 illustrates TL1 access to the OPTI-6100 behind a third-party GNE.

Figure 51. TL1 Access Behind a Third-Party GNE

GNEThird-Party

Gateway Network Element

Management

SystemTL1 Access

to OPTI-6100

SONET Network

w/OSI Management


104 61184500L1-6J

InteroperabilityWhen 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.

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.

Table 43. TCP Ports

GNE TCP Port Other

ADTRAN:OPTI-6100

2000 (echo)2001 (no echo)

Fujitsu:FLM, Flashwave

2024 Refer to “Fujitsu” on page 104 regarding Fujitsu’s Plus-R mode.

Lucent:DMX

3801

Nortel:OPTera Metro 3500

13666 Refer to “Nortel” on page 105 regarding LAPD frame size.

Cisco:ONS 15454Turin Traverse 6000

N/A These products use IP networking over DCC, compatible with the OPTI-6100 (refer to “IP Over DCC” on page 119). For OSI networks, they support transparent DCC tunnels.

Element Management

61184500L1-6J 105

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).

Cisco and Turin

SONET equipment from Cisco and Turin commonly use IP as the management protocol on DCC. The OPTI-6100 can be provisioned to terminate an IP interface on a DCC link connected with this equipment as outlined in “IP Over DCC” on page 119.

For use within OSI networks, DCC tunnels can be provisioned in Cisco and Turin equipment. This allows them to appear transparent within a DCC link between two surrounding network elements.


106 61184500L1-6J

OSI Remote Menu AccessThe OPTI-6100 includes a proprietary protocol that provides menu access across an OSI network. To access remote menus, log on to the OPTI-6100 (any privilege level) and select Remote Menu Access from the Main menu.

Figure 52 illustrates the Remote Menu Access menu.

Figure 52. Remote Menu Access Menu

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.



Remote Menu Access

Network Elements With Menu Access Other Network Elements

1. MX21MX21 FUJITSU

2. OPTI3-LOWER

3. OPTI3-UPPER

Select Remote System:

(T)id_entry (M)ode

Element Management

61184500L1-6J 107

Neighbors Display ModeType M to toggle in and out of the Neighbors Display Mode. In this mode, only NEs that are directly connected to the OPTI-6100 are displayed. Directly connected NEs terminate both ends of a common DCC link.

Figure 53 illustrates the Remote Menu Access – Neighbors Only menu.

Figure 53. Remote Menu Access – Neighbors Only Menu

The NEs are listed alphabetically by the DCC interface to which they are attached, followed by the TID.

Login BypassRefer to “Remote Menu Access Login Required” on page 134.



Remote Menu Access - Neighbors Only

Network Elements With Menu Access Other Network Elements

1. MS05-DCC-1, MX21MX21 HS01-DCC-1, FUJITSU

2. MS11-DCC-1, OPTI3-UPPER

Select Remote System:

(T)id_entry (M)ode


108 61184500L1-6J

IP Over OSI TunnelingThe OPTI-6100 supports mediation of IP traffic through a native OSI network. The primary benefit of this feature (IP over OSI tunneling) is to enable IP applications on remoteOPTI-6100s that are connected through OSI. These IP applications include Telnet, SNMP, FTP and TFTP as listed in Table 39 on page 90.

For IP over OSI tunneling to work, two or more OSI NEs must support the tunneling protocol. IP traffic is encapsulated within OSI data packets and routed through the OSI network between the tunneling-capable elements. Intermediate OSI NEs do not need to support the tunneling protocol, even when routing the IP encapsulated data.

The OPTI-6100 and OPTI-3 both support IP over OSI tunneling.

To enable IP over OSI tunnels, complete the following procedures:

1. Select two NEs (OPTI-6100 or OPTI-3) between which an IP tunnel is desired. Generally, one element is an IP gateway and has access to a larger IP network through its Ethernet interface (call this Node A). The second NE is a remote system connected to Node A through an OSI network (call this Node B).

2. Provision the Ethernet interface on Node A appropriately for the IP network (refer to “Ethernet Interface” on page 91).

3. Provision the TID, DCC and NSAP appropriately at both nodes and connect them through an OSI network (refer to “OSI Networking” on page 96). Nodes A and B can be connected directly over DCC or over a larger OSI network containing third-party SONET equipment.

4. Provision and enable the IP over OSI tunneling interface at both nodes (refer to “IP Over OSI Tunnel Interface” on page 109).

5. Provision an IP over OSI tunnel as an entry in the IP route table at both nodes (refer to “IP Over OSI Tunnel Routes” on page 111).

6. Enable IP forwarding and set the default route interface appropriately for the IP network (refer to “Default Route Interface” on page 94 and “IP Forwarding” on page 95). Refer to “IP Over OSI Tunnel – Example 1” on page 114 for more details.

7. An external route may be required in the management computer or external IP network specifying that IP traffic destined to the remote node should be routed through Node A. Refer to “IP Over OSI Tunnel – Example 2” on page 116 for more details.

Once an IP over OSI tunneling interface has been provisioned for an NE, additional tunnels (to different nodes) can be added by entering additional IP over OSI tunnel routes (step 5, above).

Element Management

61184500L1-6J 109

IP Over OSI Tunnel Interface

The IP over OSI tunneling interface is provisioned through the OSI Tunnel Interface menu.

NOTEIf Mount Location is Central Office or Remote Terminal, the IP overOSI tunneling interface is inaccessible. For CO/RT applications,the tunneling interface is provisioned automatically and used forthe 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:





5. From the IP Network Provisioning menu, select OSI Tunnel Interface, and press ENTER.

Figure 54 illustrates the OSI Tunnel Interface menu.

Figure 54. OSI Tunnel Interface Menu



OSI Tunnel Interface

1. OSI Tunnel Interface : ENABLE

2. OSI Tunnel IP Address : 10.25.15.65

3. Osi Tunnel Subnet Mask : 255.255.255.255

4. OSI Tunnel Gateway : 0.0.0.0

5. Use Ethernet IP Addr : No

Link : Up

Selection :



110 61184500L1-6J

The options in this menu include the following:

• Interface: Enable to enable IP tunneling, or Disable.

• IP Address: Enter the IP address used to access the NE through an OSI tunnel.

A unique address can be entered for this interface, or it may share the address used by the Ethernet interface (below).

• Subnet Mask: This should always be set to 255.255.255.255 for this interface.

• Gateway: This needs provisioning only when this interface is used as the default route interface (refer to “Default Route Interface” on page 94).

• Use Ethernet IP Addr: When set to Yes, the address for the Ethernet Interface is also used for the OSI Tunnel Interface. When set to No, a unique address can be entered. The Ethernet interface itself does not need to be enabled to use its address on this interface.

• OSI Tunnel Link Status: This read-only item indicates the link status of the interface. It does not necessarily indicate that any tunnels have been successfully provisioned.

Element Management

61184500L1-6J 111

IP Over OSI Tunnel Routes

Once the OSI tunnel interface is enabled, the OPTI-6100 can accept up to 32 IP over OSI tunnel routes. A tunnel route is entered for each OSI-connected NE to which a tunnel is desired.

OSI tunnel routes are entered as static IP routes in the IP Route Table menu (refer to “IP Route Table” on page 92). To access this menu, log on to the OPTI-6100 as ADMIN and complete the following steps:





5. From the IP Network Provisioning menu, select IP Route Table, and press ENTER.

Figure 55 illustrates the IP Route Table.

Figure 55. IP Route Table

Select an exiting route for modification by entering the number, or create a new route by typing C (Create).

NOTEFor OSI tunnel routes, the interface (“Ifc”) is listed as OSItu.



IP Route Table

IP Address Netmask Gateway Ifc NSAP

1. 10.25.15.97 255.255.0.0 10.25.254.254 Ether

2. 192.1.0.97 255.255.255.0 None PDCC0

3. 10.25.15.98 255.255.255.255 None OSItu *

Selection :

(C)reate


112 61184500L1-6J

After selecting or creating a route, the Edit Route Entry menu appears. Figure 56 illustrates the Edit Route Entry menu.

Figure 56. Edit Route Entry Menu

NOTEThe NSAP entry field is not visible until OSItu has been selected asthe interface.

The parameters are provisioned as follows:

• IP Addr: Set this to the IP address of the far-end of the tunnel. This can be the far-end Ethernet address (if enabled) or OSI tunnel interface address (if not of the 127.x.x.x format).

• Netmask: This must be set to 255.255.255.255 when accessing a single IP address. If the tunnel is used to access a range of IP addresses the Netmask can be widened (e.g. 255.255.255.0). If a range of address is specified, the IP address entered must be the first IP address in the range.

• Gateway: This should always be set to None.

• Interface: Set Interface to OSItu to create an IP over OSI tunnel.

• NSAP: Enter the full NSAP of the far-end OSI network element. The NSAP is formed by concatenating the System ID onto the Area Address (refer to “NSAP” on page 100).



IP Route Table: Edit Route Entry

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

Element Management

61184500L1-6J 113

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).


114 61184500L1-6J

IP Over OSI Tunnel – Example 1This IP over OSI tunnel example uses Nodes A and B introduced in “IP Over OSI Tunneling” on page 108. This configuration allows IP applications to be used on Node B even though it is connected only through an OSI network. The configuration is characterized as follows:

• Node A is connected to an IP network through its Ethernet interface.

• Node B is connected to Node A through an OSI network. The Node B Ethernet interface is disabled.

• The IP over OSI tunnel interface at Node B is assigned an IP address on the same subnet as Node A’s Ethernet interface.

• Node A defines an IP over OSI tunnel route to Node B that specifics a single address (255.255.255.255). This allows Node A to proxy ARP for the Node B IP address.

• IP Forwarding is enabled at Node A.

• The Default Route at Node B is set to Node A. All IP traffic from Node B is sent to Node A.

Figure 57 illustrates the setup of an IP over OSI tunnel as described in Example 1.

Figure 57. IP Over OSI Tunnel – Example 1

IPNetwork

MS12MS11*3

MS10MS9*1*3

MS8MS7*1

MS6MS5*3

MS4MS3*1

MS2MS1*3

HS2HS1SCM

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1 STAT

ETHM1184510L1

ACT

LNK

ENET

1

ENET

2

ENET

3

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

SCM1184500L1

ACOHST

STATALM

OPTI-6100

DCC

Ethernet

Ethernet Interface: EnabledEthernet IP Address: 10.25.15.97Ethernet Subnet Mask: 255.255.255.0

OSI Tunnel Interface: EnabledOSI Tunnel IP Address: 10.25.15.97OSI Tunnel Subnet Mask: 255.255.255.255

OSI Tunnel Route: IP Address: 10.25.15.98 Netmask: 255.255.255.255 Gateway: None Interface: OSItu NSAP: 39840F8000000000000000000000A0C80A7FC6

MS12MS11*3

MS10MS9*1*3

MS8MS7*1

MS6MS5*3

MS4MS3*1

MS2MS1*3

HS2HS1SCM

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1 STAT

ETHM1184510L1

ACT

LNK

ENET

1

ENET

2

ENET

3

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

SCM1184500L1

ACOHST

STATALM

OPTI-6100

DCC

Node BNode A

SONETNetwork

Ethernet Interface: Disabled


OSI Tunnel Route: IP Address: 10.25.15.97 Netmask: 255.255.255.255 Gateway: None Interface: OSItu NSAP: 39840F8000000000000000000000A0C8050441

Element Management

61184500L1-6J 115

Step-By-Step Setup

NOTEAll 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.


116 61184500L1-6J

IP Over OSI Tunnel – Example 2The second IP over OSI tunnel example is similar to the first example except that there is an isolated LAN network connected to the far-end Ethernet port (called Node C). A few changes to the setup allow traffic destined for the isolated LAN to be mediated over the OSI tunnel between Nodes A and C. The configuration is characterized as follows (differences from Example 1 are highlighted in bold):

• Node A is connected to an IP network through its Ethernet interface.

• Node C is connected to Node A through an OSI network. The Node C Ethernet interface is enabled.

• The IP over OSI tunnel interface at Node C uses the Ethernet IP address.

• Node A defines an IP over OSI tunnel route to Node C that specifics a range of addresses (255.255.255.0). Node A does not proxy ARP for Node C.

• IP forwarding is enabled at Node A.

• The default route at Node C is set to Node A.

• Because Node A does not proxy ARP for Node C, a manual route to the isolated LAN at Node C must be entered in the external equipment on the Node A Ethernet LAN.

Figure 58 illustrates an IP over OSI tunnel as described in Example 2.

Figure 58. IP Over OSI Tunnel – Example 2

IPNetwork

MS12MS11*3

MS10MS9*1*3

MS8MS7*1

MS6MS5*3

MS4MS3*1

MS2MS1*3

HS2HS1SCM

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1 STAT

ETHM1184510L1

ACT

LNK

ENET

1

ENET

2

ENET

3

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

SCM1184500L1

ACOHST

STATALM

OPTI-6100

DCC

Ethernet



OSI Tunnel Route: IP Address: 10.25.16.0 Netmask: 255.255.255.0 Gateway: None Interface: OSItu NSAP: 39840F8000000000000000000000A0C80A7FC6

MS12MS11*3

MS10MS9*1*3

MS8MS7*1

MS6MS5*3

MS4MS3*1

MS2MS1*3

HS2HS1SCM

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

STATUS

ALARM

ONLINE

TEST

DS3EC1M1184503L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

MS BLANK1184505L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

DS1M1184513L1 STAT

ETHM1184510L1

ACT

LNK

ENET

1

ENET

2

ENET

3

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

STATUS

ALARM

ONLINE

TEST

OMM12LR1184504L1

SCM1184500L1

ACOHST

STATALM

OPTI-6100

DCC

Node CNode A

SONETNetwork

Isolated LAN on10.25.16.0 Subnet

Ethernet



OSI Tunnel Route: IP Address: 10.25.15.98 Netmask: 255.255.255.255 Gateway: None Interface: OSItu NSAP: 39840F8000000000000000000000A0C8050441

Element Management

61184500L1-6J 117

Step-By-Step Setup

NOTEAll 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.


118 61184500L1-6J

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.

Figure 59. Sample “Route Print” Response

13. From the computer on the Node A LAN, addresses on the Node C (isolated) LAN can be pinged (10.25.16.xx).

C:\> route print

:

:

Active Routes:

Network Destination Netmask Gateway Interface Metric

0.0.0.0 0.0.0.0 172.20.18.254 172.20.18.10 20

10.25.15.0 255.255.255.0 10.25.15.10 10.25.15.10 20

10.25.15.10 255.255.255.255 127.0.0.1 127.0.0.1 20

10.25.16.0 255.255.255.0 10.25.15.97 10.25.15.10 1

:

:

============================================================================

Persistent Routes:

Network Address Netmask Gateway Address Metric

10.25.16.0 255.255.255.0 10.25.15.97 1

:

:

Element Management

61184500L1-6J 119

IP Over DCCSome 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.

NOTEThere is a difference between IP over DCC and IP over OSI tunnel-ing (described in “IP Over OSI Tunneling”). IP over DCC uses IP asthe native networking protocol on the SONET DCC. IP over OSItunneling uses OSI as the native networking protocol on theSONET DCC and provides a means to encapsulate and forward IPtraffic over the native OSI network.

A DCC is setup to operate as an IP termination in the DCC Interface Provisioning menu. To access this menu, log on to the OPTI-6100 as ADMIN and complete the following steps:





5. From the SONET SDCC Provisioning menu, select DCC Interface Provisioning, and press ENTER.

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.


120 61184500L1-6J

Figure 60 illustrates the DCC Interface menu for High Speed 1.

Figure 60. DCC Interface Menu for High Speed 1 (PDCCO Mode)

NOTESThis is the same menu as Figure 49 on page 99, except that themode 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 themode is set to PDCC0 the remaining LAPD provisioning parametersare no longer displayed.

Only one DCC may select PDCC0 as its mode. The OPTI-6100 canterminate 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:






6. From the IP Network Interfaces menu, select PPP/DCCO Interface, and press ENTER.



DCC Interface: High Speed 1

1. Name : High Speed 1

2. Service State : Out Of Service (OOS-MA)

3. DCC Mode : PDCC0

4. IP Provisioning

Link Status : PPP Up

Selection :

(D)elete this DCC interface

Element Management

61184500L1-6J 121

Figure 61 illustrates the PPP/DCCO Interface menu.

Figure 61. PPP/DCCO Interface Menu

The PPP/DCCO Interface menu includes the following options:

• Interface: Enable/disable the PPP/DCC0 interface

• IP Address: The IP address assigned to the interface

• Subnet Mask: Determines the range of IP address available through the PPP/DCC0 interface (a value of 255.255.255.0 indicates that all addresses in the range of 192.1.0.0 through 192.1.0.255 are available)

• Gateway: Not required for the PPP/DCC0 interface; Set to zero

• DCC Provisioning: Returns to the associated DCC Interface menu

Status indications are as follows:

• DCC Interface: The DCC terminating the PPP/DCC0 interface

• Peer Address: The IP address of the far-end peer (0.0.0.0 when the link is down)

• Link: The status of the link (up or down)

NOTEThe OPTI-6100 does not run routing software (OSPF, RIP, etc.) forIP networking. Determination of what interface is used for sendingIP 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).



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 :


122 61184500L1-6J

Central Office/Remote Terminal ApplicationsWhen two OPTI-6100s are deployed in a point-to-point arrangement they can be provisioned as a Central Office/Remote Terminal pair. CO/RT provisioning provides two advantages:

• Simplified provisioning of many of remote management features allows easy management of the Remote Terminal.

• The Central Office OPTI-6100 can display the overall alarm level summary of the Remote Terminal on its Shelf Alarm Status screen.

To use CO/RT provisioning, the following conditions must be met:

• Two OPTI-6100 systems must be directly connected through their High Speed interfaces.

• Both OPTI-6100 systems must be in terminal mode operation (not UPSR). This provisioning is maintained on the OMMs.

• One OPTI-6100 must be designated the Central Office chassis. The other OPTI-6100 is designated Remote Terminal.

Under CO/RT operation, the following provisioning items are automatic. In some cases these items may be fixed, and not user-editable.

• If the systems have not already been assigned TIDs, TIDs are automatically assigned as OPTI-CO and OPTI-RT. These default TIDs may be overridden.

• The terminal mode high speed DCC on both systems is automatically enabled and provisioned so the DCC link between them comes up.

• The NSAP address of both systems is fixed to known values.

• The IP over OSI tunnel interface on both systems is enabled and provisioned and an OSI tunnel is established between them.

• A static route to the RT Ethernet IP address is added to the Route Table of the CO OPTI-6100, allowing automatic IP forwarding to the RT.

• The Default Route Interface at the RT is set so all IP traffic is routed to the CO OPTI-6100. This provisioning may be overridden.

Enabling Central Office/Remote Terminal OperationSelect one system for operation as the Central Office shelf and a second as the Remote Terminal. The deployment of the two systems must meet the criteria listed above.

Provisioning a system as Central Office or Remote Terminal is done through the Mount Location option in the Network Management menu. To access this menu, log on to the OPTI-6100 as ADMIN and complete the following steps:




Element Management

61184500L1-6J 123

Figure 62 illustrates the Network Management menu.

Figure 62. Network Management Menu

NOTEWhen the Mount Location is changed, the SCM software mustreboot. If you choose not to reboot the SCM, the change does nottake effect. Rebooting the SCM software does not interrupt traffic,but management connections are closed.



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 :


124 61184500L1-6J

Remote Terminal Alarm Reporting at the Central OfficeBy default, the overall alarm summary (Minor, Major, Critical) of the RT is displayed on the Shelf Alarm Status screen of the CO OPTI-6100. This feature can be enabled/disabled in the System Alarms menu. To access this menu, log on to the OPTI-6100 as ADMIN and select System Alarms from the Main menu.

Figure 63 illustrates the System Alarms menu.

Figure 63. System Alarms Menu

IP Access to the Remote TerminalThe CO OPTI-6100 automatically creates an IP route to the RT Ethernet port IP address. This allows the CO OPTI-6100 to automatically forward IP traffic to the RT.

The ability of the CO to route IP traffic to the RT and the ability of the RT to terminate that traffic does not depend on the state of the RT Ethernet port. Even if the RT Ethernet port is disabled or down, it can still terminate IP traffic forwarded from the CO OPTI-6100.

If the RT Ethernet port is provisioned with a subnet mask of all ones (255.255.255.255) and the IP address falls within the CO Ethernet LAN subnet, the CO OPTI-6100 proxies (proxy ARP) the RT IP address. (Refer to “Proxy ARP” on page 113.) This operation is analogous to “IP Over OSI Tunnel – Example 1” on page 114.

If the RT subnet mask specifies a larger subnet (e.g., 255.255.255.0) the CO OPTI-6100 does not proxy ARP for the RT. A range of IP addresses can be forwarded through the RT to an isolated Ethernet LAN. This is analogous to “IP Over OSI Tunnel – Example 2” on page 116.



System Alarms

1. Shelf Alarm Status

2. Alarm Logs

3. User-Definable Alarms

4. Alarm Chronology : Ascending

5. Remote RT Alarm Reporting : ENABLE

6. Acknowledge RT Alarm Status

7. Alarm Contact Definition : Normally Open

Selection :

Element Management

61184500L1-6J 125

Operation With the OPTI-3The OPTI-3 may be provisioned for either CO or RT operation. Mixed CO/RT operation between an OPTI-6100 and an OPTI-3 supports all of the CO/RT features outlined in this section.

Operation With the Total Access 3000/3010 (OC-3 L5)The Total Access 3000supports remote menu access over OSI, as of the following firmware revisions:

• System Controller Unit: Revision E15.04 or higher

• OC-3 L5 Multiplexer: Revision D03.01 or higher

NOTEWhen a CO OPTI-6100 is set up with a Total Access 3000/3010 forremote menu access, the RT alarm entry in the Shelf Alarm Statusscreen of the OPTI-6100 is present and always indicates that thereare no RT alarms (even if the Total Access 3000/3010 has activealarms).


126 61184500L1-6J

SYSTEM ADMINISTRATIONThis 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.

Figure 64. System Administration Menu

The available options include:

• “Software Update” on page 127

• “Security Administration” on page 130

• “System Configuration Archive” on page 140

• “System Event Log” on page 153

• “Auto Upgrade Status” on page 162



System Administration

1. Software Update

2. Security Administration

3. System Configuration Archive (SCA)

4. System Event Log

5. Auto Upgrade Status

Selection :



61184500L1-6J 127

Software UpdateThe 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

Upgrade SCM SoftwareThe OPTI-6100 SCM can accept software updates through YModem and TFTP.

To update the SCM Software, complete the following steps:

1. Log in to the system as ADMIN.



4. From the Provisioning menu, select System Administration, and press ENTER.

5. From the System Administration menu, select Software Update, and press ENTER.

6. From the Software Update menu, select one of the following options:

• YModem Update – This option is used for updates through Telnet session, craft port, or admin interface.

• Remote File Update – This option is used for updates through IP connectivity. A Remote Filename is required. If the TFTP server has not been set, it must be provisioned here.

7. After the upgrade is complete, select Reboot Controller Unit, and press ENTER to reboot the module into the new firmware.

NOTENewly loaded SCM software does not begin running until the SCMhas been rebooted.


128 61184500L1-6J

Upgrade OMM Module SoftwareOMM modules (OC-3, OC-12, and OC-48) can accept software updates through YModem and TFTP.

To update the OMM software, complete the following steps:


2. From the OPTI-6100 Main menu, select HS1 or HS2-[card type], and press ENTER.

3. From the OMM-3/12/48 menu, select Provisioning, and press ENTER.

4. From the Provisioning menu, select Software Upgrade, and press ENTER.

5. From the Software Upgrade menu, select one of the following upgrade options:

• Start YModem Download – This option is used for updates through Telnet session, craft port, or admin Interface.

• Start TFTP Download – This option is used for updates through IP connectivity. The File Name must be set before this method is available.

6. After the upgrade is complete, select Reboot HS1/HS2 (depending on the module upgraded), and press ENTER to reboot the module into the new firmware.

Cross-Copy OMM Firmware

After the reboot, it is possible to cross-copy firmware between OMM modules in a redundant pair. To initiate a firmware cross-copy, complete the following steps:

1. From the Main menu, select the OMM module to be upgraded, and press ENTER.

2. From the OMM module menu, select Provisioning, and press ENTER.


4. From the Software Upgrade menu, select Start HS1 to HS2 Download, or Start HS2 to HS1 Download, and press ENTER.

NOTENewly loaded OMM software does not begin running until the OMMmodule has been rebooted.


61184500L1-6J 129

Upgrade Tributary Module SoftwareTributary modules can accept firmware updates through YModem and TFTP.

To update a the firmware on a tributary module, complete the following steps:


2. From the OPTI-6100 Main menu, select MS Modules, and press ENTER.

3. From the MS Modules menu, select the module to be upgraded, and press ENTER.

4. From the [module] menu, select Provisioning, and press ENTER.


6. From the Software Upgrade menu, select one of the following options:

• Start YModem Download – This option is used for updates through Telnet session, craft port, or admin interface.

• Start TFTP Download – This option is used for updates through IP connectivity. The File Name must be set before this method is available.

7. After the upgrade is complete, select Reboot Card, and press ENTER to reboot the module into the new firmware.

Cross-Copy Tributary Module Firmware

After the reboot, it is possible to cross-copy firmware between tributary modules in a redundant pair. The cross-copy process is initiated on the module to be upgraded, pulling a copy of the more recent firmware from its mate.

To initiate a firmware cross-copy, complete the following steps:

1. From the MS Modules menu, select the mate to a module that has already been upgraded, and press ENTER.

2. From the Provisioning menu of the upgraded module, select Software Upgrade, and press ENTER.

3. From the Software Upgrade menu, select Start Mate to MS[#] download, and press ENTER.

NOTENewly loaded software does not begin running until the module hasbeen rebooted.


130 61184500L1-6J

Security AdministrationSecurity Administration is used to view which users are currently logged on to the system and create, enable, disable, modify, and delete user accounts.

NOTEYou must be logged in with ADMIN-level privileges to access theSecurity 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”.


61184500L1-6J 131

The Security Administration menu is illustrated in Figure 65.

Figure 65. Security Administration Menu


• “Users Currently Logged On” on page 131

• “Edit User Accounts” on page 131

• “Create New User Account” on page 131

• “Security Options” on page 132

• “Restore Back to Default Accounts” on page 134

• “Access Tech Support Account” on page 134

• “RADIUS Server Configuration” on page 135

Users Currently Logged OnThis option reports a list of all accounts currently in use on the system.

Edit User AccountsSelecting Edit User Accounts displays a list of all current user accounts. Select a listed account to change user privileges and passwords, enable/disable the account, or delete the account.

Create New User AccountUse Create New User Account to create and configure new accounts on the OPTI-6100 system.



Security Administration

1. Users Currently Logged On

2. Edit User Accounts

3. Create New User Account

4. Security Options

5. Restore Back to Default Accounts

6. Access Tech Support Account

7. Radius Server Configuration

Selection :



132 61184500L1-6J

Security OptionsSecurity Options are global, and do not change between privilege levels. The Security Options menu is illustrated in Figure 66.

Figure 66. Security Options Menu


• “Enable Technical Support Account” on page 133

• “Enable SNMP Security Account Access” on page 133

• “Lock-Out User on Login Failure” on page 133

• “Case-Sensitive Password/User-ID” on page 133

• “Null Password Accepted” on page 133

• “Enable Lock-Out Alarm” on page 133

• “Number of Login Failure Before Lock-Out” on page 133

• “Lock-Out Duration in Seconds” on page 133

• “Enable Advisory Warning Message” on page 133

• “Security Advisory Warning” on page 134

• “Enable Multiple Login Accounts” on page 134

• “Remote Menu Access Login Required” on page 134

• “RADIUS Server Authentication Status” on page 134



Security Options

1. Enable Tech Support Account : YES

2. Enable SNMP Security Account Access : NO

3. Lock-Out User on Login Failure : NO

4. Case Sensitive Password/User-ID : YES

5. Null Password Accepted : NO

6. Enable Lock-Out alarm : YES

7. Number of Login Failure Before Lock-Out : 5

8. Lock-Out Duration in Seconds : 60

9. Enable Advisory Warning Message : NO

10. Security Advisory Warning

11. Enable Multiple Login Accounts : YES

12. Remote Menu Access Login Required : NO

RADIUS Server Authentication Status : NO

Selection :



61184500L1-6J 133

Enable Technical Support Account

This option enables or disables the Technical Support Account. Refer to “Access Tech Support Account” on page 134.

Enable SNMP Security Account Access

By default, Security Account Management is not available through SNMP. Use this option to Enable SNMP access to security options.

Lock-Out User on Login Failure

This option locks out a user who tries and fails to access an account. By default, this option is Disabled.

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.

Null Password Accepted

Enabling this option allows accounts to have no password. By default, this option is Disabled.

Enable Lock-Out Alarm

This option is only functional if Lock-Out User on Login Failure is Enabled (see above). If this option is also Enabled, the system generates an alarm when a user is locked-out. This option is Enabled by default, but is not activated until the Lock-Out option is also Enabled.

Number of Login Failure Before Lock-Out

This option is only functional if Lock-Out User on Login Failure is Enabled (see above). This option determines the maximum number of failed login attempts before a lock-out occurs. The default number is five (5).

Lock-Out Duration in Seconds

This option is only functional if Lock-Out User on Login Failure is Enabled (see above). After a user has been locked out for repeat failed login attempts, this option determines the length of time the lock-out remains in effect, from three to sixty seconds. The default lock-out duration is sixty seconds.

Enable Advisory Warning Message

This option is only functional if Lock-Out User on Login Failure is Enabled (see “Lock-Out User on Login Failure” on page 133). If this option is also Enabled, the system displays a message on the login screen when a lock-out is applied. By default, this option is Disabled.


134 61184500L1-6J

Security Advisory Warning

This option is only functional if Lock-Out User on Login Failure and Enable Advisory Warning message are both Enabled (see above). The Security Advisory Warning consists of two user-definable lines of text, to warn a user who has failed login of possible repercussions. By default, the message reads:

Advisory LN 1: NOTICE: This is a private computer system.

Advisory LN 2: Unauthorized access or use may lead to prosecution.

Enable Multiple Login Accounts

This option allows ‘generic’ accounts, with multiple simultaneous users allowed under the same User ID. By default, this option is enabled.

RADIUS Server Authentication Status

This is a read-only indicator of RADIUS operational status. If RADIUS is enabled, this indicator reads Yes. Refer to “RADIUS Server Configuration” on page 135.

Restore Back to Default AccountsRestore Back to Default Accounts deletes all user-defined accounts, and restores all original accounts back to default settings.

Access Tech Support AccountThe Technical Support account is used by ADTRAN Technical Support to help troubleshoot issues with the OPTI-6100. This account has higher access privileges than the ADMIN account. Enabling this feature activates the Challenge Key Response feature. Only ADTRAN Technical Support can provide the key to unlock the Technical Support account, when provided with the Challenge Key issued by the OPTI-6100.

CAUTIONThe Challenge Key response provided by ADTRAN Technical Sup-port is only valid for one session. At this time, security accountmaintenance must be completed with the appropriate accountsand passwords prior to logging out of the system.

Remote Menu Access Login RequiredIf set to Yes (default), the OPTI-6100 requires remote menu users to log in. Set to No, users bypass the login procedure and are automatically logged into the menu system at the same privilege level used in the local system.


61184500L1-6J 135

RADIUS Server ConfigurationRemote Authentication Dial-In User Service (RADIUS) provides a point of authentication other than the SCM itself. Each SCM must be configured with accounts and privileges, which can vary. Use of a RADIUS server overrides local accounts (local logins are disabled when RADIUS is enabled), providing a central point of access for all accounts. RADIUS is disabled by default.

RADIUS uses four redundant servers for authentication. If the primary server is unavailable, the secondary server is employed for authentication, and so on.

RADIUS provides greater flexibility for account logins. Instead of using ADMIN/PASSWORD for all ADMIN account users, each ADMIN account user could have a personal account on a RADIUS Server.

ADTRAN Dictionary Contents

The ADTRAN Dictionary information is as follows. Refer to Table 44 for what each ADTRAN-IAD-Telnet-Level corresponds to on the controller level.

NOTEThe ADTRAN Dictionary contents must be loaded/compiled/addedto the RADIUS Server of choice. Without these additions, all logonsdefault to the ‘Default Radius Logon Level’ as provisioned on the“Primary RADIUS Server Settings Menu” on page 137.

## dictionary.adtran## Authored by: Margaret Hataway [email protected]# 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.

VENDOR Adtran 664

## 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 0VALUE Adtran-IAD-Telnet-Level Level-Support 1VALUE Adtran-IAD-Telnet-Level Level-Config 2VALUE Adtran-IAD-Telnet-Level Level-Router 3VALUE Adtran-IAD-Telnet-Level Level-Voice 4VALUE Adtran-IAD-Telnet-Level Level-Status 5


136 61184500L1-6J

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.

The RADIUS Remote Authentication configuration menu is shown in Figure 67.

Figure 67. RADIUS Remote Authentication Configuration Menu

Table 44. ADTRAN-Telnet-Level Values

Level Access Privilege

Full This level corresponds to the SCM ADMIN level.

Support This level corresponds to the SCM TEST level.

Config This level corresponds to the SCM CONFIG level.

Router This level corresponds to the SCM READWRITE level.

Status This level corresponds to the SCM READONLY level.


Unacknowledged Alarms: None Unit Number: 1

RADIUS Remote Authentication Configuration

1. Primary RADIUS Server Settings

2. Secondary RADIUS Server Settings

3. 3rd RADIUS Server Settings

4. 4th RADIUS Server Settings

5. Validate RADIUS Server Connection : (Run RADIUS Test)

6. Enable RADIUS Remote Authentication : NO

7. Enable TL1 RADIUS Login : YES

8. Account Level if None Received : READ_ONLY

Selection :



61184500L1-6J 137

The RADIUS Remote Authentication Configuration menu options are as follows:

• “Primary RADIUS Server Settings Menu” on page 137

• “Secondary RADIUS Server Settings” on page 138

• “3rd RADIUS Server Settings” on page 138

• “4th RADIUS Server Settings” on page 138

• “Validate RADIUS Server Connection” on page 138

• “Enable RADIUS Remote Authentication” on page 139

• “Enable TL1 RADIUS Login” on page 138

• “Account Level if None Received” on page 138

Primary RADIUS Server Settings MenuPrimary Radius Server Settings

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.

Figure 68. Primary RADIUS Server Authentication Settings Menu

The Primary RADIUS Server Authentication menu options are as follows:

Server AddressThis option displays the value of the IP Address of the RADIUS Server to be queried for authentication.


Unacknowledged Alarms: None Unit Number: 1

Primary RADIUS Server Authentication Settings

1. Server Address : 0.0.0.0

2. Port Number : 1812

3. Number Retires : 3

4. Time Out : 1000(ms)

5. Shared Secret

Selection :



138 61184500L1-6J

Port NumberThis option displays the value of the UDP port of the server. The default value is 1812.

Number RetriesThis 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 OutThis 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 SecretThis 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.

Secondary RADIUS Server SettingsThe options for these settings are identical to the options in the “Primary RADIUS Server Settings Menu” on page 137.

3rd RADIUS Server SettingsThe options for these settings are identical to the options in the “Primary RADIUS Server Settings Menu” on page 137.

4th RADIUS Server SettingsThe options for these settings are identical to the options in the “Primary RADIUS Server Settings Menu” on page 137.

Validate RADIUS Server ConnectionRADIUS cannot be enabled through the menus until validation is successful.

From the RADIUS Remote Authentication Configuration menu, select Validate RADIUS Server Connection, and press ENTER. Press Y to run the validation test for the configured servers.

Enable TL1 RADIUS LoginThis option allows the user to enable or disable RADIUS authentication for TL1.

Account Level if None ReceivedThe default access privilege is used if the RADIUS Server cannot return the Adtran-Telnet-Level attribute.


61184500L1-6J 139

Enable RADIUS Remote AuthenticationTo enable RADIUS, complete the following steps:

1. Log in to the SCM with and ADMIN account.

2. From the Main menu, select System Controller, and press ENTER.


4. From the Provisioning menu, select General, and press ENTER.

5. From the General menu, select Security Administration, and press ENTER.

6. From the Security Administration menu, select RADIUS Remote Authentication Configuration, and press ENTER.

7. From the RADIUS Remote Authentication Configuration menu, select Primary RADIUS Server Settings, and press ENTER.

8. In the Primary RADIUS Server Authentication Setting menu, enter the Server Address and Port Number for the primary RADIUS server. The other settings are optional.

9. Press ESC to return to the RADIUS Remote Authentication Configuration menu.

10. Repeat steps 7 through 9 (as needed) for Secondary, 3rd and 4th RADIUS Servers.

11. From the RADIUS Remote Authentication Configuration menu, select Validate RADIUS Server Connection, and press ENTER.

12. Press Y to run the validation test for the configured servers.

NOTERADIUS cannot be enabled by way of the menus until validation issuccessful.

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.

SNMP Access to RADIUS

RADIUS Authentication can be enabled by way of SNMP (if Enable SNMP Security Account Access is Enabled) by setting the adTAeScuRADIUSServAuthentication OID to 1. Index 2 disables RADIUS Authentication and restores the use of local accounts for authentication.


140 61184500L1-6J

System Configuration ArchiveThe System Configuration Archive (SCA) system allows the chassis administrator to manually or automatically save provisioning information for all installed modules to a remote TFTP server for possible restoration at a later time. Use this feature for:

• Fast recovery of chassis provisioning in the case of disaster

• “Cloning” baseline chassis configurations to new installations so that only a few chassis-specific provisions need to be altered, significantly reducing initial setup time

The menus and SNMP system allow the administrator to perform automatic or manual save and restores of SCA information to a TFTP server. Automatic save operations can be scheduled to occur after a specific time of day so that installations with large numbers of OPTI-6100 chassis can reduce simultaneous SCA network traffic.

While SCA Save operations backup information from all modules present in the chassis, the Restore operation allows control of the type of provisions to be restored to the SCM, and whether or not to restore provisions to specific modules, with an optional exclusion for In Service modules.

SCA menus and operations are available only to privileged administrator-level accounts.

The System Configuration Archive (SCA) menu is shown in Figure 69.

Figure 69. System Configuration Archive (SCA) Menu

The available options are as follows:

• “SCA AutoSave Provisioning” on page 141

• “SCA SCM Restore Provisioning” on page 143

• “SCA Module Restore Provisioning” on page 145

• “SCA Operations” on page 147



System Configuration Archive (SCA)

1. SCA Autosave Provisioning

2. SCA SCM Restore Provisioning

3. SCA Module Restore Provisioning

4. SCA Operations

Selection :



61184500L1-6J 141

SCA AutoSave ProvisioningUse the SCA AutoSave Provisioning menu (Figure 70) to display and configure provisions related to SCA AutoSave operations.

Figure 70. SCA AutoSave Provisioning Menu

Available options are as follows:

• “AutoSave System” on page 141

• “AutoSave Only If Prov Changes” on page 141

• “AutoSave Filename Prefix” on page 142

• “AutoSave Filename Suffix” on page 142

• “Max AutoSave File Instances” on page 142

• “AutoSave Time (Hour) and AutoSave Time (Minute)” on page 142

• “AutoSave Retries” on page 142

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.

AutoSave Only If Prov Changes

This option instructs the SCA to perform AutoSave operations only if provisions have been changed on the SCM or an installed OMM or tributary module.

The next three fields are collectively used to construct the name of the AutoSave SCA file on the TFTP server:



SCA Autosave Provisioning

1. AutoSave System : DISABLE

2. Autosave Only If Prov Changes : ENABLE

3. Autosave Filename Prefix :

4. Autosave Filename Suffix : .sca

5. Max Autosave File Instances : 1

6. Autosave Time (Hour) : 0

7. Autosave Time (Minute) : 0

8. Autosave Retries : 5

Selection :



142 61184500L1-6J

AutoSave Filename Prefix

The AutoSave Filename Prefix is a 0 to 30 character string used to construct the first part of the SCA filename.

AutoSave Filename Suffix

The AutoSave Filename Suffix is a 0 to 8 character string used to construct the trailing type, or extension portion of the SCA filename. If a period is desired between the first and second part of the SCA filename, it should be placed within this suffix field.

Max AutoSave File Instances

The Max AutoSave File Instances field determines the maximum number of SCA filenames to save to the TFTP server. This is often called a backup file rotation scheme, where the last “N” files are always maintained on the backup medium (the TFTP server in this case). For example, if this field is set to a value of seven, seven uniquely named SCA files are written to the TFTP server. After the seventh file has been written, the count recycles to one, and the first file is overwritten. The sequence 1 to 7, 1 to 7, 1 to 7 continually cycles until the value of this field is changed, at which time the value resets to one.

The generated SCA filename takes the following form (excluding parentheses):

(Prefix)_(Instance)(Suffix)

where:

• Prefix is the value of filename prefix field

• Instance is decimal number between 1 and the max AutoSave instances field

• Suffix is the value of the filename suffix field

Example: The prefix is Flintville, the next Autosave file instance is 3, and the suffix is .sca. The name of the next SCA Autosave filename is Flintville_3.sca.

AutoSave Time (Hour) and AutoSave Time (Minute)

The AutoSave fields represent a time of day after which the AutoSave SCA file is written to the remote TFTP server. These fields allow the system administrator to configure the OPTI-6100 systems on the customer network to write their AutoSave SCA files at different times so as to prevent network congestion that might occur if all the systems attempted to save their SCA files at the same time.

Example: AutoSave Time (Hour) is set to 3 and AutoSave Time (Minute) is set to 15. The SCM attempts an SCA AutoSave operation shortly after 03:15 in the morning.

AutoSave Retries

The AutoSave Retries option determines the number of retries the system performs following a failed AutoSave operation.


61184500L1-6J 143

SCA SCM Restore ProvisioningUse the SCA SCM Restore Provisioning menu (Figure 71) to display and configure provisions related to SCA Restore of SCM provisions.

Figure 71. SCA SCM Restore Provisioning Menu


• “Restore Provisions to SCM” on page 143

• “Restore SCM SCA Provisions” on page 143

• “Restore SCM Network Provisions” on page 144

• “Restore SCM Network Interface Provisions” on page 144

• “Restore SCM SNMP Provisions” on page 144

• “Restore SCM Security System Provisions” on page 144

Restore Provisions to SCM

Restore Provisions to SCM is a global override to disable the restoration of all SCM provisions. This protects the current SCM settings during SCA Restore operations.

If this field is set to Disable, no SCM provisions are altered during an SCM Restore regardless of the other settings on this screen.

Restore SCM SCA Provisions

Restore SCM SCA Provisions controls whether or not SCA-related provisions are restored on the SCM.

All SCA provisions such as SCA AutoSave, filename, SCM and access module restore settings, etc. are overwritten if this field is set to Enable.



SCA SCM Restore Provisioning

1. Restore Provisions To SCM : DISABLE

2. Restore SCM SCA Provisions : DISABLE

3. Restore SCM Network Provisions : DISABLE

4. Restore SCM Network Interface Provisions : DISABLE

5. Restore SCM SNMP Provisions : DISABLE

6. Restore SCM Security System Provisions : DISABLE

Selection :



144 61184500L1-6J

Restore SCM Network Provisions

Restore SCM Network Provisions controls whether or not general IP network-related provi-sions are restored on the SCM.

General IP network-related provisions include the various Telnet, DNS, IP-forwarding, and firmware TFTP server settings. This field does not control the restore of network interface settings (such as IP, Netmask, and Gateway.)

Restore SCM Network Interface Provisions

Restore SCM Network Interface Provisions controls whether or not network interface related settings (such as IP, Netmask, and Gateway) for the Ethernet, and Local PPP network interface are restored on the SCM.

Restore SCM SNMP Provisions

Restore SCM SNMP Provisions controls whether or not SNMP-related provisions are restored on the SCM.

SNMP-related provisions include such items as SNMP ifIndexing method, trap-host IP addresses, System Name, Location, and Contact strings, as well as the public and private SNMP community strings.

Restore SCM Security System Provisions

Restore SCM Security System Provisions controls whether or not Security System related provisions are restored on the SCM.

Security System provisions include such items as system and user account names and passwords, as well as security options of user passwords such as case-sensitivity and the options of allowing NULL or empty passwords.


61184500L1-6J 145

SCA Module Restore ProvisioningUse the SCA Module Restore Provisioning menu (Figure 72) to display and configure provi-sions related to SCA restore of tributary and OMM module provisions.

Figure 72. SCA Module Restore Provisioning Menu

Features and available options are as follows:

• “Slot” on page 145

• “Card Type” on page 145

• “Restore” on page 146

• “MS1 to MS12, HS1, and HS2” on page 146

• “Restore Provisions to Module” on page 146

• “Restore In Service Module Provisions” on page 146

• “Restore to Empty Slot (Pre-Provision)” on page 146

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.



SCA Module Restore Provisioning

Slot CardType Restore Slot CardType Restore

1. +DS3EC1M..... No 12. ............ No

2. ............ No A:HS1. +OMM-12...... Yes

3. +DS1M........ No B:HS2. ............ No

4. ............ No

5. ............ No

6. ............ No

7. +TRAM........ No

8. ............ No

9. +DS1VM....... No

10. +GECM........ No

11. +ETHM8....... No

13. Restore Provisions To Modules : ENABLE * = In-Service

14. Restore In-Service Module Provisions : DISABLE + = Out-Of-Service

15. Restore to Empty Slot (Pre-Provision) : DISABLE - = No Prov-Info

x = Unsupported

Selection : ............ = Empty Slot

Normal = Restorable, Inverse = NOT restorable

(E)nable ALL, (D)isable ALL, (T)oggle ALL


146 61184500L1-6J

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.

MS1 to MS12, HS1, and HS2

Select one of these slot identifiers and press ENTER to toggle the SCA Restore Enable/Disable state for the current slot. (The SMX chassis only has MS slots numbered to MS4.)

Restore Provisions to Module

Restore Module Provisions is a global override to disable the restoration of all tributary and OMM module provisions. This protects the current module settings during SCA Restore opera-tions to the SCM.

If this field is set to Disable, no module provisions are altered during an SCM Restore regardless of the other settings on this screen.

Restore In Service Module Provisions

Restore In Service Module Provisions controls whether or not SCM Restore operations affect In Service tributary and OMM modules. Setting this field to Disable prevents In Service modules from being affected by an SCM Restore.

Restore to Empty Slot (Pre-Provision)

Restore to Empty Slot (Pre-Provision) controls whether or not SCM Restore operations attempt to pre-provision empty slots.

If an empty slot is pre-provisioned, inserting a module matching the type of module present in the SCA file for that slot results in automatic pre-provisioning of the module to the settings present in the SCA file.


61184500L1-6J 147

SCA OperationsUse 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.

Figure 73. SCA Operations Menu


• “Remote File I/O Method” on page 147

• “SCA TFTP Server” on page 147

• “SCA Remote Filename” on page 148

• “SCA AutoSave Status” on page 148

• “Perform SCA Save” on page 149

• “Perform SCA Restore” on page 149

• “SCA Save Status” on page 150

• “SCA Restore Status” on page 151

Remote File I/O Method

Use the Remote File I/O Method menu to select the file transfer protocol for Save and Restore operations. Select TFTP or FTOT (File Transfer Over TL1).

SCA TFTP Server

This option is only visible if the Remote File I/O Method is set to TFTP. This specifies the IP address of the TFTP server to be used during manual SCM save and restore operations.



SCA Operations

1. Remote File I/O Method : TFTP (UDP/IP)

2. SCA TFTP server : 0.0.0.0

3. SCA Remote Filename :

4. SCA Autosave status

5. Perform SCA Save

6. Perform SCA Restore

7. SCA Save Status

8. SCA Restore Status

Selection :



148 61184500L1-6J

SCA Remote Filename

The SCA Remote Filename is a forty character field containing the TFTP filename to be written or read by manual SCM Save and Restore operations.

SCA AutoSave Status

The SCA AutoSave Status screen (Figure 74) displays the status of the SCA AutoSave system. There are no user-editable fields on this status-information screen.

Many of these fields are informational displays of the settings present on the SCA AutoSave Provisioning screen.

Figure 74. SCA AutoSave Status Screen


• “AutoSave Filename Prefix and Suffix” on page 149

• “Current/Next AutoSave Instance” on page 149

• “AutoSave Only if Prov Changes” on page 149

• “Cards in Shelf” on page 149

• “Cards With Prov Data” on page 149

• “Cards With Changes” on page 149

• “Date/Time of Last SCA AutoSave” on page 149

• “Date/Time of Next SCA AutoSave” on page 149

• “AutoSave Status” on page 149



SCA Autosave Status

Autosave Filename Prefix :

Autosave Filename Suffix : .sca

Current/Next Autosave Instance : 1

Autosave Only If Prov Changes : ENABLE

Cards in Shelf : 8 (1,3,7,9-11,HS1,SCM)

Cards With Prov Data : 8 (1,3,7,9-11,HS1,SCM)

Cards With Changes : 2 (7,SCM)

Date/Time of last SCA Autosave : N/A

Date/Time of next SCA Autosave : 08/06/05 00:00:00

Autosave Status : Idle

(S)ave



61184500L1-6J 149

AutoSave Filename Prefix and SuffixRefer to “AutoSave Filename Prefix” and “AutoSave Filename Suffix” on page 142.

Current/Next AutoSave InstanceCurrent/Next AutoSave Instance displays the current number of attempts for the AutoSave operation.

AutoSave Only if Prov ChangesIf enabled, AutoSave Only if Prov Changes suspends the scheduled AutoSave operation if no provisioning has been altered since the last Save or AutoSave operation.

Cards in ShelfCards in Shelf displays the number of modules present in the chassis and lists the slots where the modules are installed.

Cards With Prov DataCards With Prov Data displays the number of modules with provision information and lists the slots with such provisioning information.

Cards With ChangesCards With Changes displays the number of modules with provisioning that has been altered since SCM power-up or the last SCA Manual or AutoSave operation, and lists the slots where the modules are installed.

Date/Time of Last SCA AutoSaveDate/Time of Last SCA AutoSave displays the date/time of the last SCA AutoSave operation, or N/A if none have been performed.

Date/Time of Next SCA AutoSaveDate/Time of Next SCA AutoSave displays the date/time of the next scheduled SCA AutoSave operation.

AutoSave StatusAutoSave Status displays the completion status of the last SCA AutoSave operation, or Idle if none have been performed.

Perform SCA Save

Use Perform SCA Save to initiate a manual SCA Save operation.

Perform SCA Restore

Use Perform SCA Restore to initiate a manual SCA Restore operation.


150 61184500L1-6J

SCA Save Status

Use SCA Save Status (Figure 75) to review a status summary of the current manual SCA Save operation.

Figure 75. SCA File Save Status Screen





• “Cards With Changes” on page 151

• “SCA Save Status” on page 151

SCA Remote FilenameThe SCA Remote Filename field displays the filename being written by the SCM Save operation.

Cards in ShelfThis field displays the number of modules present in the chassis as well as a summary of the slot numbers where the modules are installed.

Cards With Prov DataThis field displays the number of modules with provision information as well as a summary of the slot numbers with such provisioning information.



SCA File Save Status

SCA Remote Filename :

Cards in Shelf : 4 (1,5,HS1,SCM)

Cards With Prov Data : 4 (1,5,HS1,SCM)

Cards With Changes : 3 (1,5,SCM)

SCA Save Status : Error: Param error

(S)ave, (A)bort



61184500L1-6J 151

Cards With ChangesThis field displays the number and summary of module slots whose provisions have been changed since the last SCA AutoSave or manual save operation.

SCA Save StatusThis field displays a status summary of the current SCA save operation.

SCA Restore Status

Use SCA Restore Status (Figure 76) to review a status summary of the current manual SCA Restore operation.

Figure 76. SCA TFTP Restore Status Screen

Available options include:




• “Cards In SCA” on page 152

• “Cards With Prov In SCA” on page 152

• “Cards Restored” on page 152

• “Cards Excluded” on page 152

• “Cards NOT Restored” on page 152

• “Cards w/ Exceptions” on page 152

• “SCA Restore Status” on page 152



SCA TFTP Restore

SCA Remote Filename :

Cards in Shelf : 4 (1,5,HS1,SCM)

Cards With Prov Data : 4 (1,5,HS1,SCM)

Cards In SCA : 0

Cards w/ Prov In SCA : 0

Cards Restored : 0

Cards Excluded : 0

Cards NOT Restored : 0

Cards w/ Exceptions : 0

SCA Restore Status : Idle

(R)estore, (A)bort, (F)irst, (P)revious, (N)ext, (L)ast


152 61184500L1-6J

SCA Remote FilenameThe SCA Remote Filename field indicates the remote file from which the Restore operation is retrieving data.

Cards in ShelfThe 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 With Prov DataThe Cards With Prov Data field displays the number of modules having provisioning infor-mation restored, and a summary of the slot numbers with such provisioning information.

Cards In SCAThe Cards In SCA field displays the number and summary of module slots represented in the SCM file retrieved by the Restore operation.

Cards With Prov In SCAThe Cards With Prov In SCA field displays the number of modules with provisioning infor-mation that can be restored.

Cards RestoredThe Cards Restored field lists modules whose provision settings were successfully restored, and their slots.

Cards ExcludedThe 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 NOT RestoredThe Cards NOT Restored field lists the modules that were not restored for any reason, including user exclusions or errors, and their slots.

Cards w/ ExceptionsThe Cards w/ Exceptions field lists the modules slots that experienced exception or error conditions during the restore operation, and their slots.

SCA Restore StatusThe SCA Restore Status field displays a status summary of the current SCA Restore operation.


61184500L1-6J 153

System Event LogA System Event Log (Figure 77) is stored in nonvolatile memory onboard the SCM. The System Event Log stores SNMP and menu events. The log is guaranteed to store the last 250 events that occur. Once 250 events have been stored, the log stores another 250 events before discarding the oldest 250 events. The System Event Log can not be deleted or changed.

The log can be saved to a table with the SNMP command adTAeSCMSystemLogTable. When the System Event Log becomes 90% full an SNMP trap adTAeSCMSystemLogFull is sent.

Figure 77. System Event Log



113 - 124 of 14% Full System Event Log Page 8 of 8

TIME EVENT CONN ACC NAME

113 07/22/05 12:26:39 Logout IP ADMIN

114 07/31/05 20:17:32 SCM Started

115 08/05/05 11:56:11 Login IP ADMIN

116 08/05/05 11:56:35 YMODEM S/W Update Start IP ADMIN

117 08/05/05 11:57:51 Flash S/W Update Success

118 08/05/05 11:58:01 SCM Reset IP ADMIN

119 08/05/05 11:58:33 SCM Started

120 08/05/05 11:58:58 Login IP ADMIN

121 08/05/05 12:19:39 Sec Chg: TechSupport Acct Disable IP ADMIN

122 08/05/05 12:20:03 Sec Chg: TechSupport Acct Enabled IP ADMIN

123 08/05/05 12:39:55 Logout IP ADMIN

124 08/05/05 12:40:18 Login IP ADMIN

--------------------------->>> END OF SYSTEM LOG LIST <<<-----------------------

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


154 61184500L1-6J

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


61184500L1-6J 155

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:

Table 45. Menu Events Stored in the System Log

System Controller/Provisioning/General

Change Date

Change Time

Auto-Logoff

Logoff Croft Port When DTR Lost

Restore Default Provisioning

System Controller/Provisioning/General/Management Ports

Admin Port Baud Rate

Admin Port Communications

Admin Port Use RTS/CTS

Admin Port Terminate Session Upon Carrier Loss

Admin Port De-assert/Drop DTR on Logout

Craft & Admin Port Baud Rate

Interbank Comm. Mode

Network Management Port Mode

System Controller/Provisioning/General/Security Admin

Change Account Password

Create New Account

Change Access Privileges

Delete Account

Enable an account

Disable an account

Lock/Unlock User Account

Reset Account Age

Reset Password Age

Change Account Expiration Allowed

Change Password Aging Allowed

Restore Back to Default Accounts

Access Tech Support Account


156 61184500L1-6J

/Security Options

Enable SNMP Security Account Access

Enable Advisory Warning Message

Enable TL1 Security Warning

Enable Multiple Login Accounts

Remote Menu Access Login Required

Security Options/Account Lock-Out Options

Lock-Out User on Login Failure

Enable Lock-Out Alarm

INDEFINITE LOCK-OUT On Login Failure

Number of Login Failure Before Lock-Out

Lockout Duration in Minutes

Security Options/Security Advisory WarningSecurity Options/Password Options

Activate Password Complexity

Minimum Password Length

Password Upper Case Required

Password Lower Case Required

Password Digit Character Required

Password Special Character Required

Case Sensitive Password/User-ID

Security Options/Account Expiration

Enable Account Expiration

Set All Accounts Expiration Time

Read-Only Accounts Expiration Time

Read-Write Accounts Expiration Time

Test Accounts Expiration Time

Config Accounts Expiration Time

Admin Accounts Expiration Time

User Accounts Expiration Time

Reset all Account Expiration Times to Zero

Send Account Expiration Alarm

Table 45. Menu Events Stored in the System Log (Continued)


61184500L1-6J 157

Security Options/Password Aging

Enable Password Aging

Set All Passwords Expiration Time

Read-only Passwords Expiration Time

Read-Write Passwords Expiration Time

Test Passwords Expiration Time

Config Passwords Expiration Time

Admin Passwords Expiration Time

User Passwords Expiration Time

Reset all Passwords Expiration Times to Zero

Passwords Expiration Notification

/RADIUS Remote Authentication Configuration

Enable RADIUS Remote Authentication

Enable TL1 RADIUS Login

Account Level if None Received

/RADIUS Auth Config /Primary RADIUS Server Setting

Server Address

Port Number

Number Retires

Time out

Shared Secret

/RADIUS Auth Config /Secondary RADIUS Server Setting

Server Address

Port Number

Number Retires

Time out

Shared Secret

/RADIUS Auth Config /3rd RADIUS Server Setting

Server Address

Port Number

Number Retires

Time out

Shared Secret



158 61184500L1-6J

/RADIUS Auth Config /4th RADIUS Server Setting

Server Address

Port Number

Number Retires

Time out

Shared Secret

/Trusted IP Client Access Control

Trusted IP Client Access Control

Trusted Clients List

System Controller/Provisioning/HS/MS Module Provisioning

Auto-Provisioning

System Controller/Provisioning/Network Management

Mount Location

Get Provs From HS


/IP Network Provisioning/IP Network Interfaces

Default Route Interface

IP Forwarding

/IP Network Provisioning/IP Network Interfaces/Ethernet

Ethernet Interface

Ethernet IP Address

Ethernet Subnet Mask

Ethernet Gateway

/IP Network Provisioning/IP Network Interfaces/OSI

OSI Tunnel Interface

OSI Tunnel IP Address

OSI Tunnel Subnet Mask

OSI Tunnel Gateway

/IP Network Provisioning/IP Network Interfaces/PPP

PPP / DCC0 Interface

PPP / DCC0 IP Address

PPP / DCC0 Subnet Mask

PPP / DCC0 Gateway



61184500L1-6J 159

/IP Ntwk Provisioning/IP Services Ports/Terminal Server

Network Management Port Baud Rate

Network Terminal Server Telnet Port

Network Terminal Server Security

Craft & Admin Port Baud Rate

Admin Terminal Server Telnet Port

Admin Terminal Server Security

/IP Ntwk Provisioning/IP Services Ports/IP Service Ports

TL1 Telnet Port

TL1 Raw TCP Port

Secondary Telnet Port

Ntwk Terminal Server Port

ADMIN Terminal Server Port

Telnet Dead Client Detection

RFC1122 TCP Dead Client Detection

/IP Ntwk Provisioning/IP Services Ports/DNS

DNS Lookup System

Primary DNS Server

Secondary DNS Server

/IP Ntwk Provisioning/IP Services Port/Remote File Host

Remote Firmware Host

Remote SCA Host

Remote Host User

Remote Host File



160 61184500L1-6J

/IP Ntwk Provisioning/IP Services Ports/SNMP

Trap Host 1 IP

Trap Host 2 IP

Trap Host 3 IP

Trap Host 4 IP

SCM Traps

System Name

TID/SysName Sync

System Location

System Contact

Read Community

Write Community

NonVol CardStat

/SONET SDCC ProvisioningSystem Controller/Provisioning/TL1

TID (string)

TID/SysNameSync

TL1 Telnet Port

TL1 Raw TCP Port

TL1 Echo

System Controller/Provisioning/System Admin/Software Update

TFTP successful update

TFTP failed update

Y-MODEM successful update

Y-MODEM failed update



61184500L1-6J 161

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.

System Controller/Provisioning/System Admin/SCA/SCA Autosave Provisioning

AutoSave System

Autosave Only if Prov Changes

Autosave Filename Prefix

Autosave Filename Suffix

Max Autosave File Instances

Autosave Time Hour

Autosave Time Minute

Autosave Retries

/SCA Controller Restore Provisioning

Restore Provisions To Controller

Restore Controller SCA Provisions

Restore Controller Network Provisions

Restore Controller Network Interface Provisions

Restore Controller SNMP Provisions

Restore Controller Security System Provisions

/SCA Restore Provisioning

Restore Provisioning To Modules

Restore In-Service Module Provisions

Restore to Empty Slot

/SCA Operations


Remote SCA Host

SCA Remote Filename



162 61184500L1-6J

Auto Upgrade StatusThe Auto Upgrade Status menu provides methods to manually or automatically upgrade the flash firmware for the SCM and modules installed in the OPTI-6100 system.

NOTEOperation of this feature requires IP or FTOT (through Total AccessEMS) connectivity to the OPTI-6100 system, either through IP/DCC or the Ethernet maintenance port. Auto Upgrade does notfunction 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.


61184500L1-6J 163

The AutoUpgrade Status menu is shown in Figure 78.

Figure 78. Auto Upgrade Status Menu


• “Local File Cache Expire” on page 163

• “Auto Upgrade Config BasePath” on page 164

• “Auto Upgrade Config Filename” on page 164

• “Auto Upgrade Mode” on page 164

• “Config File Refresh Interval” on page 164

• “Auto Upgrade Retries” on page 165

• “Auto Upgrade Status Information” on page 165

Local File Cache ExpireLocal File Cache Expire specifies how many minutes a flash file can be retained on the SCM before it is retrieved from the TFTP server. If a subsequent request for the same file is made within the Cache Expire time, the local, cached copy of the file is used, thus reducing upgrade time and network traffic. A value of zero (0) disables TFTP flash file caching.

The local cache is used during all TFTP “gets”, such as OMM module, tributary module, and SCM firmware upgrades, as well as Auto Upgrade configuration file and SCM operations.



Auto Upgrade Status

1. Local File Cache Expire (Min) : 480 minutes

2. Auto Upgrade Config Basepath : L:\TFTP\OPTI6100_LATEST

3. Auto Upgrade Config Filename : 6100.auc

4. Auto Upgrade Mode : Manual

5. Config File Refresh Interval : 96 hours

6. Auto Upgrade Retries : 5

Upgrades: 0/0, Errors: 0/0, Upgrades needed: 3

Shelf( 00:00:00): Idle

Slot (1 , 00:00:00): Idle, 1184503L1 needs upgrade (C02.01 -> C02)

(F)irst Slot, (L)ast Selection : (P)rev Slot, (N)ext

(C)lear File Cache (R)eset Config File Cache

(A)bort Auto Upgrade (S)tart Auto Upgrade


164 61184500L1-6J

Auto Upgrade Config BasePathAuto Upgrade Config BasePath sets the BasePath prefix that precedes all Auto Upgrade configuration and module firmware files, indicating where they are located on the TFTP server. It is assumed that all Auto Upgrade system configuration flash firmware files are located in the same directory, so this field applies to all Auto Upgrade module-specification entries.

The BasePath argument should not contain spaces, commas, quotes, or other unusual characters that would generally be considered invalid in a path specification. Although the SCM does not interpret the contents of this string, different operating systems have different rules concerning what constitutes valid characters and path/file separators.

Auto Upgrade Config FilenameAuto Upgrade Config Filename sets the Auto Upgrade configuration filename that is to be retrieved from the firmware TFTP server. The Auto Upgrade configuration filename is supplied by ADTRAN. The file that is provided by ADTRAN typically has a .auc extension.

Auto Upgrade ModeAuto Upgrade Mode sets the Auto Upgrade system operating mode:

• Auto: Modules are automatically checked and upgraded after power-up of the SCM or on module insertion into the chassis. Actions controlled by the Config File Refresh Interval (“Config File Refresh Interval”, below) are also enabled.

• Manual: Modules are checked and upgraded only when instructed through SNMP or menus. Actions controlled by Refresh Interval (“Config File Refresh Interval”, below) are disabled.

NOTESWhen Auto Upgrade Mode is set to Auto and an upgrade is per-formed manually using the standard YModem or TFTP upgradeprocedure, the module is immediately up/downgraded to the firm-ware version associated with the Auto Upgrade Config file. Set AutoUpgrade 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 ENTER without entering a new value. Thisenters a null value for the Auto Upgrade Config filename and pre-vents any further action by the Auto Upgrade system.

Config File Refresh IntervalConfig File Refresh Interval sets for the Auto Upgrade refresh interval (in hours), which controls how often the Auto Upgrades configuration file should be retrieved from the TFTP server. When in Auto mode, this setting also controls how often Auto Upgrade evaluation operations are automatically performed. A value of zero disables Auto Upgrade operations.


61184500L1-6J 165

Auto Upgrade RetriesAuto Upgrade Retries sets the number of attempts to retrieve the Auto Upgrade configuration file if there are errors contacting the TFTP server. This option also sets the number of times to re-attempt to upgrade the firmware for each module if an error occurs during the upgrade process. A value of zero disables all retries.

Auto Upgrade Status InformationThe Auto Upgrade Status menu contains several fields that provide read-only status infor-mation related to the Auto Upgrade system. The fields include the number of successful and completed module upgrades, the number of errors that have occurred since the last time the auto upgrade procedure began, the number of upgrades needed, the current status of the chassis as it relates to the Auto Upgrade system, the current status of a slot during an Auto Upgrade, and the current status of each slot in the chassis. The following block represents what is typical while the Auto Upgrade system is in progress:

Upgrades: 1/x Errors: 0/x Upgrades needed: 2

Shelf (00:05:26): Busy, upgrading slot 8 (1184510L1)

Slot (8, 00:01:33): Busy, send file to module, 43.2% (1184510L1)

This block indicates the following:

• One successful module upgrade has already been completed.

• No upgrade errors have occurred since the last Auto Upgrade operation.

• Two modules (including the current one in slot 8) require firmware upgrade.

• The chassis is busy upgrading an 1184510L1 module in slot 8 and has been performing Auto Upgrades for 5 minutes and 26 seconds.

• The current module in slot 8 has been in the process of an upgrade for 1 minute and 33 seconds. The SCM has already retrieved the firmware file from the TFTP server (or from the local TFTP Cache). The SCM is in progress sending the firmware file to the module over the maintenance channel using the YModem protocol, which is 43.2% complete.

The following block and associated hotkeys allow the administrator to display the Auto Upgrade status or progress of any slot in the chassis, regardless of which module is currently being upgraded. This allows the administrator to easily determine which modules require a firmware upgrade and which are already up-to-date.

Slot (11, 00:00:00): Idle, 1184510L1 needs upgrade (A05 -> A06)

The F, L, P, and N hotkeys control this block:

(F)irst Slot, (L)ast, (P)rev Slot, (N)ext

This example indicates the state of the module in slot 11:

• The module status is Idle

• The module type is 1184510L1 (TRAM module)

• The module needs a firmware upgrade


166 61184500L1-6J

STATUSThere 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 StatusTo access the Shelf Status screen, complete the following steps:


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.

Figure 79. Shelf Status Screen



Status

Hardware

Primary HS : Installed Alarms

Secondary HS : NONE Open Fuse : None

Ethernet Link : Up ACO : Off

Inband Link : Down

Alarm Relays Visual Audible

Critical Inactive Inactive

Major Active Active

Minor Active Active

Ext ACO Inactive N/A

Aux #1 Input Inactive MAJOR



Single Fan/Pwr Inactive MINOR

Multi Fan Inactive CRITICAL

Power Bus A Inactive MAJOR

Power Bus B Inactive MAJOR


Status

61184500L1-6J 167

DCC Interface StatusTo access the DCC Interface Status screen, complete the following steps:


2. From the System Controller menu, select Status and press ENTER.

3. From the Status menu, select DCC Interface Status, and press ENTER.

NOTEAccess 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.

Figure 80. DCC Interfaces Screen

The DCC Interfaces screen shows the facility state of each of the DCC interfaces.



DCC Interfaces

High Speed 1 (HS 01 ): DnMode



168 61184500L1-6J

OMM Module StatusThis section details the Status screens for OMM modules.

OMM3/12 StatusTo 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.

NOTEOnly slots containing modules can be selected from this menu.

2. From the OMM menu, select Status, and press ENTER.

An OMM Status menu is shown in Figure 81.

Figure 81. OMM3 Status Menu

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



Status

1. Clock Status

2. Synchronization Message Status

3. Shelf Status

HS1 Module Status : In Service-Online

HS2 Module Status :

HS1 Facility Status : In Service-Offline

HS2 Facility Status :

HS1 Facility Alarm : None

HS2 Facility Alarm :

Equipment Fault :

Selection:


Status

61184500L1-6J 169

The following steps explain how to view these screens:

3. From the Status menu, select Clock Status, and press ENTER.

The OMM Clock Status screen in shown in Figure 82.

Figure 82. OMM3 Clock Status Screen

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.



Clock Status

Selected Clock : Primary Fiber

PRI Fiber Clock (HS1) : Fail

SEC Fiber Clock (HS2) : Fail

PRI External Clock : Unavailable

SEC External Clock : Unavailable

PRI Trib Module Clock : Unavailable - MS5, EC1 #1

SEC Trib Module Clock : Unused



170 61184500L1-6J

5. From the Status menu, select Synchronization Message Status, and press ENTER.

The Synchronization Message Status screen is shown in Figure 83.

Figure 83. Synchronization Message Status Screen



Synchronization Message Status

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


Status

61184500L1-6J 171


The OC-3 Shelf Status screen is shown in Figure 84.

Figure 84. OC-3 Shelf Status Screen

The Shelf Status screen indicates which OMM module is carrying the traffic, and the status of Automatic Protection Switching.




Shelf Status

: Slot HDLC Link Drop 1 Drop 2 Drop 3 APS

MS 1 : OK HS1 HS1 HS1 HS1 Enabled

MS 2 : OK HS1 HS1 HS1 HS1 Disabled

MS 3 : Empty

MS 4 : Empty

MS 5 : OK HS1 HS1 Enabled

MS 6 : Empty

MS 7 : Empty


MS 9 : Empty

MS 10 : Empty


MS 12 : Empty

Selection:



172 61184500L1-6J

OMM48 StatusTo access the Status screen for an OMM48 module, complete the following steps:

1. From the Main menu, select an OMM48 module, and press ENTER.


2. From the OMM48 menu, select Status, and press ENTER.

An OMM48 Status menu is shown in Figure 85.

Figure 85. OMM48 Status Menu

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.


Unacknowledged Alarms: Chassis: 1 Slot: HS1

Status

1. Equipment Status

2. Facility Status

3. STS-12C Status

4. STS-3C Status

5. STS-1 Status

6. VT1.5 Status

Selection:


Status

61184500L1-6J 173

Tributary Module StatusThis section details the Status screens for tributary modules.

DS3EC1M StatusTo 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.

Figure 86. DS3EC1M Status Screen


Unacknowledged Alarms: Chassis: 1 Slot: MS7

Status

Equipment Provisioning : IS

Equipment State : IS ACT, PSI

Facility Provisioning : IS

Facility State : OOS-AU FLT

Board Operating Mode : EC1

Equipment Fault : None

Facility Fault : Signal Fail

Line Build Out : Short

Loopback Status : No Loop



174 61184500L1-6J

DS3EC1M3 StatusTo access the DS3EC1M3 Status, complete the following steps:


2. From the MS Modules menu, select a DS3EC1M3 module, and press ENTER.


The DS3EC1M3 Status screen is shown in Figure 87.

Figure 87. DS3EC1M3 Status Screen



Status

Board Operating Mode : DS3


Equipment State : IS STBY


7. Facility 1 Status



Selection:


Status

61184500L1-6J 175

DS3M3E/DS3M3T StatusTo access the DS3M3E or DS3M3T Status, complete the following steps:


2. From the MS Modules menu, select a DS3M3E or DS3M3T module, and press ENTER.


The DS3M3E Status screen is shown in Figure 88.

Figure 88. DS3M3E Status Screen



Status

Board Operating Mode : DS3


Equipment State : OOS-AU AINS, MEA





Selection:



176 61184500L1-6J

DS1M/DS1M2 StatusTo access the DS1M or DS1M2 Status, complete the following steps:


2. From the MS Modules menu, select a DS1M/DS1M2 module, and press ENTER.


The DS1M Status menu is shown in Figure 89.

Figure 89. DS1M Status Menu



Status

1. Facility # 1 16. Facility #16









10. Facility #10 25. Facility #25




14. Facility #14

15. Facility #15 30. Equipment

Selection:


Status

61184500L1-6J 177

4. From the DS1 Status screen, select the desired DS1, and press ENTER.

A DS1 Facility Status screen is shown in Figure 90.

Figure 90. DS1 Facility Status Screen

5. Press ESC to return to the DS1 Status menu.

6. From the DS1 Status menu, select Equipment, and press ENTER.

The DS1 Equipment Status screen is shown in Figure 91.

Figure 91. Equipment Status Screen



Facility #1 Status

Facility Provisioning : OOS-MA UAS

Facility State : OOS-MA UAS

Line Length : 0 - 133 Feet

Line Coding : B8ZS

In-Band Loopback Code Detection : CSU

Line Identification :

Alarm Status : Signal Fail

Loop Status : No Loop

Selection:




Equipment Status

Equipment Provisioned State : IS



DS3 Facility Provisioning : IS

DS3 Facility State : OOS-AU FLT

DS3 Framing : C-BIT

Out of Band Loopback Code Detection : Disabled

Operation Mode : T1

DS3 Facility Fault : Signal Fail

DS3 Loop Status : No Loop

Selection:



178 61184500L1-6J

DS1VM/DS1VM2 StatusTo access the DS1VM/DS1VM2 Status, complete the following steps:


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.

Figure 92. DS1VM2 Status Menu



Status















15. Facility #15 30. DS1 Mapping

Selection:


Status

61184500L1-6J 179






The Equipment Status screen is shown in Figure 94.




Facility #1 Status




Line Coding : B8ZS

Loopback Code Detection : CSU




Selection:




Equipment Status




Selection:



180 61184500L1-6J

Equipment Functional State

The equipment functional state indicates the current condition of the availability of the DS1VM/DS1VM2 hardware to provide service. For functional state definitions, refer to “Appendix B, Service States Glossary”.

To access the DS1VM/DS1VM2 Equipment Functional State, complete the following steps:



3. From the module menu, select Provisioning, and press ENTER.

The DS1VM2 Provisioning menu is shown in Figure 95.

Figure 95. DS1VM2 Provisioning Menu



Provisioning

1. Equipment Provisioned State : OOS-MA

Equipment Functional State : OOS-MA

Operation Mode : T1

4. Facility Provisioning

5. Framing

6. Line Length

7. Line Coding

8. Loopback Detection

9. Line ID ( 1 to 14)

10. Line ID (15 to 28)

11. Mapping : GR-253

12. PRI Clock Output to OMM : Disabled

13. SEC Clock Output to OMM : Disabled

14. Restore Factory Defaults

15. Software Upgrade

Selection:


Status

61184500L1-6J 181

Facility Functional State

The facility functional state indicates the current condition of availability of each of the 28 DS1s to provide service. For functional state definitions, refer to “Appendix B, Service States Glossary”.

To access the DS1VM/DS1VM2 Facility Functional State, complete the following steps:



3. From the module menu, select Provisioning, and press ENTER.

4. From the Provisioning menu select Facility Provisioning, and press ENTER.

5. From the Facility Provisioning menu, select Facility Functional State, and press ENTER.

The DS1VM Facility Functional State screen is shown in Figure 96.

Figure 96. Facility Functional State Screen




DS1 # 1 : OOS-MA UAS DS1 #15 : OOS-AU FLT

DS1 # 2 : OOS-MA UAS DS1 #16 : OOS-MA UAS








DS1 #10 : OOS-MA UAS DS1 #24 : OOS-MA UAS





Selection:



182 61184500L1-6J

DS1VME/DS1VMT StatusTo access the DS1VME/DS1VMT Status, complete the following steps:


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.

Figure 97. DS1VME/DS1VMT Status Menu



Status














14. Facility #14


Selection:


Status

61184500L1-6J 183






The DS1 Equipment Status screen is shown in Figure 99.




Facility #1 Status

Facility Provisioning : IS



Line Coding : B8ZS

Loopback Code Detection : Disabled







Equipment Status






184 61184500L1-6J


The equipment functional state indicates the current condition of the availability of the DS1VME hardware to provide service. For functional state definitions, refer to “Appendix B, Service States Glossary”.

To access the DS1VME/DS1VMT Equipment Functional State, complete the following steps:



3. From the DS1VME/DS1VMT module menu, select Provisioning, and press ENTER.

The DS1VME/DS1VMT Provisioning screen is shown in Figure 100.

Figure 100. DS1VME Provisioning Menu



Provisioning

1. Equipment Provisioned State : IS

Equipment Functional State : IS ACT, PSI

3. Facility Provisioning

4. DS1 Framing

5. DS1 Line Length

6. DS1 Line Coding

7. DS1 Loopback Detection

8. DS1 Line Identification

9. Mapping : GR-253

10. PRI Clock Output to OMM : Disabled

11. SEC Clock Output to OMM : Disabled

12. Restore Factory Defaults

13. Software Upgrade

Selection:


Status

61184500L1-6J 185

FramingEach facility in the DS1VME/DS1VMT supports independent framing. To provision the framing settings for each facility, follow the instructions below:


2. From the MS Modules menu, select a DS1VME module, and press ENTER.


4. From the Provisioning menu, select Framing, and press ENTER.

The DS1VME/DS1VMT Framing menu is shown in Figure 101.

Figure 101. Framing Menu



Framing

1. Facility # 1 : Auto (Unframed) 16. Facility #16 : Auto (Unframed)







8. Facility # 8;: Auto (Unframed) 23. Facility #23 : Auto (Unframed)


10. Facility #10 : Auto (Unframed) 25. Facility #25 : Auto (Unframed)




14. Facility #14 : Auto (Unframed)

15. Facility #15 : Auto (Unframed) 30. Set Multiple

Selection:



186 61184500L1-6J

5. Select a facility to provision framing, and press ENTER.

The DS1VME/DS1VMT Facility Framing menu is shown in Figure 102.

Figure 102. Facility Framing Menu

6. From the Framing menu, select a framing type, and press ENTER.



Facility # 1

1. Auto

2. SLC96

3. ESF

4. SF

5. Unframed

Selection:


Status

61184500L1-6J 187

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.

Figure 103. Enter Facilities to Set Screen

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.



Enter facilities to set



188 61184500L1-6J


The facility functional state indicates the current condition of availability of each of the 28 DS1s to provide service. For functional state definitions, refer to “Appendix B, Service States Glossary”.

To access the DS1VME/DS1VMT Facility Functional State, complete the following steps:




4. From the Provisioning menu select Facility Provisioning, and press ENTER.

5. From the Facility Provisioning menu, select Facility Functional State, and press ENTER.

The DS1VME/DS1VMT Facility Functional State screen is shown in Figure 104.

Figure 104. Facility Functional State Screen




DS1 # 1 : OOS-AU FLT DS1 #15 : OOS-MA UAS















Status

61184500L1-6J 189

ETHM/ETHM2 StatusTo access the ETHM or ETHM2 Status, complete the following steps:


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.

Figure 105. ETHM Status Screen



Status

Equipment State : IS

Facility #1 State : OOS-AU FLT GFP State : Link Down, No Sync

MAC Address : 00:A0:C8:0D:4B:4D Loopback : None

Speed : 10 Mbps Duplex : Half

Link Status : Down

Facility #2 State : OOS-MA UAS GFP State : Link Down, No Sync

MAC Address : 00:A0:C8:0D:4B:4E Loopback : None


Link Status : Down

Facility #3 State : OOS-MA UAS GFP State : Link Down, No Sync

MAC Address : 00:A0:C8:0D:4B:4F Loopback : None


Link Status : Down



190 61184500L1-6J


The equipment functional state indicates the current condition of the availability of the ETHM/ETHM2 hardware to provide service. For functional state definitions, refer to “Appendix B, Service States Glossary”.

To access the ETHM/ETHM2 Equipment Functional State, complete the following steps:


2. From the MS Modules menu, select an ETHM/ETHM2 module, and press ENTER.

3. From the ETHM/ETHM2 module menu, select Provisioning, and press ENTER.

4. From the Provisioning menu, select Equipment Provisioned State, and press ENTER.

The ETHM Equipment Provisioned State menu is shown in Figure 106.

Figure 106. Equipment Functional State Screen



Equipment Provisioned State

1. IS

2. OOS-MA

Selection:


Status

61184500L1-6J 191

ETHM8/ETHM8-2 StatusTo access the ETHM8 or ETHM8-2 Status, complete the following steps:


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.

Figure 107. ETHM8 Status Menu



Status


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:



192 61184500L1-6J

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.

Figure 108. ETHM8 Status Screen



Facility #1 Status

Facility State : IS GFP/PPP/X.86 State : Synced

MAC Address : 00:A0:C8:05:00:01 Loopback : None

Speed : 100 Mbps Duplex : Full

Link Status : Up


Status

61184500L1-6J 193

ETHM8E StatusTo access the ETHM8E Status, complete the following steps:


2. From the MS Modules menu, select an ETHM8E module, and press ENTER.

3. From the ETHM8E module menu, select Status, and press ENTER.


Figure 109. ETHM8E Status Menu



Status

1. Facility 1 Uplink 1 : Synced

2. Facility 2 Uplink 2 : Link Down, No Sync







Equipment State : OOS-MA UAS

Selection:



194 61184500L1-6J



Figure 110. ETHM8E Status Screen



Facility 1 Status




Link Status : Up


Status

61184500L1-6J 195

ETHM8EH StatusTo access the ETHM8EH Status, complete the following steps:


2. From the MS Modules menu, select an ETHM8EH module, and press ENTER.

3. From the ETHM8EH module menu, select Status, and press ENTER.


Figure 111. ETHM8EH Status Menu



Status

1. Facility 1 Uplink 1 : Synced








Equipment State : OOS-MA UAS

Selection:



196 61184500L1-6J



Figure 112. ETHM8EH Status Screen



Facility 1 Status




Link Status : Up


Status

61184500L1-6J 197

TRAM StatusTo access the TRAM Status, complete the following steps:


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.

Figure 113. TRAM Status Screen



Status





Line Build Out : Short


Port Fault : Signal Fail



198 61184500L1-6J

TRAM3 StatusTo access the TRAM3 Status, complete the following steps:


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.

Figure 114. TRAM3 Status Screen



Status


Facility #1 State : IS

Facility #2 State : OOS-MA UAS

Facility #3 State : OOS-MA UAS

Facility #1 DS3 Framing : C-BIT



Facility #1 Line Build Out : Short




Facility #1 Fault : None

Facility #2 Fault : Signal Fail

Facility #3 Fault : Signal Fail


Status

61184500L1-6J 199

O3TM StatusTo access the O3TMIR, O3TMLR, O3TMM, or O3TME Status, complete the following steps:


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.

Figure 115. O3TM Status Screen



Status

1. Clock Status


Working Module Status : In Service

Protect Module Status :

Working Facility Status : In Service-Offline

Protect Facility Status :

Working Facility Alarm : None

Protect Facility Alarm :

Equipment Fault :

Selection:



200 61184500L1-6J

O12TME StatusTo access the O12TME Status, complete the following steps:


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.

Figure 116. O12TME Status Screen



Status

1. Clock Status


Working Module Status : In Service

Protect Module Status :

Working Facility Status : In Service-Offline

Protect Facility Status :

Working Facility Alarm : None

Protect Facility Alarm :

Equipment Fault :

Selection:


Status

61184500L1-6J 201

GECM, GESM, and GEMM StatusTo access the GECM, GESM, or GEMM Status, complete the following steps:


2. From the MS Modules menu, select a Gigabit Ethernet module, and press ENTER.

3. From the module menu, select Status, and press ENTER.

The GECM Status screen is shown in Figure 117.

Figure 117. GECM Status Screen



Status



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

GEFM/GEFMEH StatusTo access the GEFM or GEFMEH Status, complete the following steps:


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.

Figure 118. GEFM/GEFMEH Status Screen



Status



MAC Address : 00:A0:C8:05:00:01

Link State : Down

GFP/PPP/X.86 Link State : Link Down, No Sync

Loopback : None


Status

61184500L1-6J 203

Cross-Connect Module StatusTo access the OMMXCV Status, complete the following steps:

1. From the Main menu, select an OMMXCV module, and press ENTER.


2. From the OMMXCV menu, select Status, and press ENTER.

An OMMXCV Status menu is shown in Figure 119.

Figure 119. OMMXCV Status Menu

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.



Status

1. Clock Status

2. Shelf Status

HS1 Module Status : In Service

HS2 Module Status :

Selection:



204 61184500L1-6J

3. From the Status menu, select Clock Status, and press ENTER.

The OMMXCV Clock Status screen in shown in Figure 120.

Figure 120. OMMXCV Clock Status Screen

The Clock Status screen displays the selected synchronization clock in use and the status of the various clock sources.




Clock Status

: Active Status Sync Msg Fault

Free Run : ** Normal

PRI External :

SEC External :

PRI Trib Module :

:

SEC Trib Module :

:


Status

61184500L1-6J 205


The OMMXCV Shelf Status screen is shown in Figure 121.

Figure 121. OMMXCV Shelf Status Screen

The Shelf Status screen indicates which OMMXCV module is carrying the traffic, and the status of Automatic Protection Switching.




Shelf Status

: Slot HDLC Link Drop 1 Drop 2 Drop 3 APS

MS 1 : Empty

MS 2 : Empty

MS 3 : Empty

MS 4 : Empty

Selection:



206 61184500L1-6J

SYSTEM ALARMSThe 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.

Figure 122. System Alarms Menu

The options on this screen are as follows:

• “Shelf Alarm Status” on page 207

• “Alarm Logs” on page 208

• “User-Definable Alarms” on page 209

• “Alarm Chronology” on page 212

• “Remote RT Alarm Reporting” on page 212

• “Alarm Contact Definition” on page 212



System Alarms

1. Shelf Alarm Status

2. Alarm Logs

3. User-Definable Alarms

4. Alarm Chronology : Ascending

Remote RT Alarm Reporting : Not Applicable

5. Alarm Contact Definition : Normally Open

Selection :


System Alarms

61184500L1-6J 207

Shelf Alarm StatusThe Shelf Alarm Status screen indicates the current alarm levels present on the SCM, OMM modules, and tributary modules on the OPTI-6100 system.

The Shelf Alarm Status menu is shown in Figure 123.

Figure 123. Shelf Alarm Status Menu

To access the System Alarms, complete the following steps:

1. From the Main menu, select System Alarms, and press ENTER.

2. From the System Alarms menu, select Shelf Alarm Status, and press ENTER.

The Shelf Alarm Status menu shows the alarm status for each of the modules/slots and a master log of alarms.



Shelf Alarm Status

M - Master Log HS 1 - OMM-12...... [None]

S - SCM......... [None] HS 2 - ............ [None]

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]

Select Log (M-Master, S-SCM, HS1, HS2, 1..12):


208 61184500L1-6J

Alarm LogsAlarm 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.

Figure 124. Master Alarm Log

To access the Alarm Logs screen, complete the following steps:


2. from the System Alarms menu, select Alarm Logs, and press ENTER.

NOTETo access the Alarm Logs from the Shelf Alarm Status menu, usethe legend at the bottom of the page. Select the alarm log to view,and press ENTER.



Alarm Log - Master Alarms Alarms 1 to 14 of 221 Page 1 of 16

Date Time Type AID Level Desc Stat

07/12/04 15:51:39 DS1M 1-MS9-1 Major DS1 LOS *Act

07/12/04 14:27:28 OMM-12 1-HS1-STS-1-3-28 Major OC12 UNEQ-V *Clr













------------------------------>>> MORE <<<----------------------------------

Inverse = Active * = Unacknowledged Chronology = Descending

(N)ext (P)rev (F)irst (L)ast (C)lear (A)cknowledge (S)elect Log (R)eset Log

System Alarms

61184500L1-6J 209

User-Definable AlarmsUser-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.

Figure 125. User-Definable Alarms Menu

The options on the User-Definable Alarms screen are as follows:

• “Environmental Alarms” on page 210

• “MS Module Removed” on page 211

• “HS Module Removed” on page 211



User-Definable Alarms

1. Environmental Alarms

2. MS Module Removed Level : MAJOR

3. HS Module Removed Level : CRITICAL

Selection :



210 61184500L1-6J

Environmental AlarmsThe 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.

Figure 126. Environmental Alarms Menu

To access the Environmental Alarms, complete the following steps:


2. From the System Alarms menu, select User-Definable Alarms, and press ENTER.

3. From the User-Definable Alarms menu, select Environmental Alarms, and press ENTER.



Environmental Alarms

1. Environmental Alarm Summary

2. Auxiliary #1 Input



5. Auxiliary Fan Alarms

6. Power Bus A Input

7. Power Bus B Input

8. Equipment ID : 0

Selection :


System Alarms

61184500L1-6J 211

4. From the Environmental Alarms menu, select Environmental Alarm Summary, and press ENTER.

The Environmental Alarm Summary menu is shown in Figure 127.

Figure 127. Environmental Alarm Summary Menu

MS Module RemovedMS 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 RemovedHS 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.



Environmental Alarm Summary

(Description, TL1 Condition Code, AID, Level)

1. Aux #1 Input,AUX-1 , 2,MJ



4. Power Bus A ,PWRPRI, 4,MJ

5. Power Bus B ,PWRSEC, 5,MJ

6. Single Fan ,CLFAN , 6,MJ

7. Multi Fan ,MCLFAN, 7,MJ

Selection :



212 61184500L1-6J

Alarm ChronologyBy default, the alarms in the Alarm Logs are listed in ascending chronological order. To change this order:


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.

Remote RT Alarm ReportingIf the chassis is provisioned to Subtended, this option reads Not Applicable, and can not be selected.

If the chassis is provisioned to Central Office, this option enables/disables alarm reporting for any Remote Terminal chassis on the network. By default (when applicable), this option is Enabled.

Refer to “Central Office/Remote Terminal Applications” on page 122.

Alarm Contact DefinitionThis option toggles the Alarm Contact Definition between Normally Open and Normally Closed. The default option is Normally Open.

When this option is set to Normally Open, open alarm contacts are not reported as alarms, and closed contacts are reported as alarms. When this option is set to Normally Closed, closed contacts are not reported, and open contacts are.

Loopbacks and Testing

61184500L1-6J 213

LOOPBACKS AND TESTINGThis section describes loopback and testing options on the OPTI-6100 system.

DS1VM/DS1VM2 Loopbacks

NOTEAll loopbacks are detected from the Fiber Side (Network) towardsthe facility. Loopbacks that are activated are the same as the localloopback (toward the network) that can be activated by the craftport and TL1.

DisabledWhen 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.

CSUWhen 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).

NIUWhen 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).


214 61184500L1-6J

DS1VME/DS1VMT Loopbacks

NOTELoopbacks are detected from the Fiber Side (Network) towards thefacility. Loopbacks that are activated are the same as the localloopback (toward the network) that can be activated by the craftport and TL1.

DisabledWhen 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.

Figure 128. DS1VME Line Loopback

Figure 129. DS1VME Local Loopback

Framer

(1 of 28) LIU

(1 of 28)

X

X

AIS

Framer

(1 of 28)LIU

(1 of 28)

X

X

AIS


61184500L1-6J 215

CSUWhen 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 (In-band Codes)When the T1/E1 Loopback Detection setting for a channel is set to NIU the 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).

NIU (Out-of-band Codes)When the T1/E1 Loopback Detection setting for a channel is set to NIU the channel responds with a T1/E1 loopback toward the network when it receives an ESF FDL loop-up message (00001110 11111111b) 10 consecutive times. The loopback is canceled if an ESF FDL loop-down pattern (00111000 11111111b) is detected 10 consecutive times. This is only valid in ESF Framing mode.


216 61184500L1-6J

DS1M/DS1M2 Loopbacks

NOTEAll loopbacks are detected from the Fiber Side (Network) towardsthe facility. Loopbacks that are activated are the same as the localloopback (toward the network) that can be activated by the craftport and TL1.

DS1 Remote Loopbacks

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).

DS3 Remote Loopbacks

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.


61184500L1-6J 217

DS3M3E/DS3M3T Loopback Detection

NOTEAll loopbacks are detected from the Fiber Side (Network) towardsthe facility. The loopbacks that are activated are the same as thelocal loopback (toward the network) that can be activated by thecraft port and TL1.

DisabledWhen 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.

Figure 130. DS3M3E Line Loopback (DS3 Mode)

Figure 131. DS3M3E Line Loopback (EC1 Mode)

Framer

(1 of 3) LIU

(1 of 3)

X

XAIS

LIU

(1 of 3)

X

AIS


218 61184500L1-6J

Figure 132. DS3M3E Local Loopback (DS3 Mode)

Figure 133. DS3M3E Local Loopback (EC1 Mode)

EnabledWhen 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.

Framer

(1 of 3)LIU

(1 of 3)

X

X

AIS

LIU

(1 of 28)

X


61184500L1-6J 219

DS3 Facility Monitoring ModeFacility Monitoring Mode is a testing option supported on the DS3M3E, DS3M3T, and TRAM3 modules.

CAUTIONWhen enabled, Facility Monitoring Mode disables all DS3 outputsignals, disrupting all traffic on the module. Although the Receivefacility remains in operation, the Transmit facility is shut down.

Facility Monitoring Mode allows "monitoring" or "eavesdropping" on an external DS3 signal. Only the Receive input of the DS3 port is used to monitor an existing DS3 circuit. In this mode, use a splitter to tap into the DS3 circuit. Monitor mode sets the input impedance to a high level, so no loading occurs on the DS3 circuit. The TX DS3 output is turned off, so this output does not affect traffic.


220 61184500L1-6J

PERFORMANCE MONITORINGEach 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 ModulesThis section details the Performance Monitoring options for OMM modules.

OMM3To 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.

Figure 134. OMM3 Performance Monitoring Menu

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.



Performance Monitoring

1. OC-3 Section : No Errors

2. OC-3 Line : No Errors

3. STS-1 Path #1 :

4. STS-1 Path #2 :

5. STS-1 Path #3 :

6. Reset PM Summary

7. Reset All PM Data

8. Reset All PM Thresholds to Defaults

9. Enable All PM Thresholds

10. Disable All PM Thresholds

Selection:



61184500L1-6J 221






From the Performance Monitoring screen, options 1 to 18 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.






3. STS-1 Path # 1 : Some Errors

4. STS-1 Path # 2 : 15. STS-3C Path #1




8. STS-1 Path # 6 : 19. Reset PM Summary

9. STS-1 Path # 7 : 20. Reset All PM Data

10. STS-1 Path # 8 : 21. Reset All PM Thresholds to Defaults

11. STS-1 Path # 9 : 22. Enable All PM Thresholds

12. STS-1 Path #10 : 23. Disable All PM Thresholds

13. STS-1 Path #11 :

14. STS-1 Path #12 :

Selection:



222 61184500L1-6J










1. OC-48 Section Performance Monitoring : Some Errors

2. OC-48 Line Performance Monitoring : Some Errors

3. STS-12C Performance Monitoring : No Errors


5. STS-1 Performance Monitoring : Alarm Errors

6. VT1.5 Performance Monitoring : Alarm Errors

7. Clear All Summaries

8. Reset All Data

9. Reset All Thresholds to Defaults

10. Enable All Thresholds

11. Disable All Thresholds

Selection:



61184500L1-6J 223

Tributary ModulesThis section details the Performance Monitoring options for tributary modules.

ETHM, ETHM2, ETHM8, ETHM8-2, ETHM8E, and ETHM8EHTo access the Performance Monitoring options for the ETHM, ETHM2, ETHM8, ETHM8-2, ETHM8E, or ETHM8EH, complete the following steps:


2. From the MS Modules menu, select an Ethernet module, and press ENTER.

3. From the module menu, select Performance Monitoring, and press ENTER.

4. From the Performance Monitoring menu, select the port or Reset all PM Data, and press ENTER.

An ETHM Performance Monitoring menu is shown in Figure 137.

Figure 137. ETHM Performance Monitoring Menu

NOTEThe ETHM8, ETHM8-2, ETHM8E, and ETHM8EH PerformanceMonitoring menus list eight ports. All submenus of the individualports are the same as in the ETHM or ETHM2, as shown on the fol-lowing pages.




1. Port #1

2. Port #2

3. Port #3


Selection:



224 61184500L1-6J

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.

Figure 138. ETHM Port #1 Performance Monitoring Menu

6. From the Performance Monitoring menu, select Daily Performance or Quarter Hourly Performance, and press ENTER.



Port #1

1. Daily Performance

2. Quarter Hourly Performance

Selection:



61184500L1-6J 225

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.

Figure 139. Port #1 - Performance Group Menu

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.

Figure 140. Performance Group - Packet TX/RX Counts Screen



Port #1 - Performance Group

1. Packet TX/RX Counts

2. RX Status and Errors, part 1

3. RX Errors, part 2

4. TX Status and Errors, part 1

5. TX Errors, part 2

Selection:




Port #1 - Daily Performance

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:



226 61184500L1-6J

8. Press ESC to return to the Performance Group menu.

9. From the Performance Group menu, select RX Status and Errors, Part 1, and press ENTER.

A Performance Group RX Status and Errors, Part 1 screen is shown in Figure 141.

Figure 141. Performance Group - RX Status and Errors, Part 1 Screen


11. From the Performance Group menu, select RX Errors, Part 2, and press ENTER.




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:



61184500L1-6J 227

A Performance Group RX Errors, Part 2 screen is shown in Figure 142.

Figure 142. Performance Group - RX Errors, Part 2 Screen


13. From the Performance Group menu, select TX Status and Errors, and press ENTER.

A Performance Group TX Status and Errors screen is shown in Figure 143.

Figure 143. Performance Group - TX Status and Errors Screen




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:



228 61184500L1-6J


15. From the Performance Group menu, select TX Errors, Part 2, and press ENTER.

A Performance Group TX Errors, Part 2 screen is shown in Figure 144.

Figure 144. Performance Group - TX Errors, Part 2 Screen





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:



61184500L1-6J 229

DS3EC1MTo access the Performance Monitoring options for the DS3EC1M, complete the following steps:


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.

NOTEDepending on the Board Operating Mode selected, the menu titlereads 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.

Figure 145. DS3EC1M Daily Performance Screen



Daily Performance

5/14

Code Violations : 0

Errored Seconds : 0

Severely Errored Seconds : 0


Fault Count : 1

Selection:



230 61184500L1-6J

DS3EC1M31. 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.

NOTEDepending on the Board Operating Mode selected, the menu titlereads ADTRAN Triple DS3 LineCard or ADTRAN Triple EC1 Line-Card.

4. From the Performance Monitoring menu, select one DS3 or EC1.

5. From the DS3 menu, select Daily Performance or Quarter Hourly Performance, and press ENTER.

A DS3EC1M3 Daily Performance screen is shown in Figure 146.

Figure 146. DS3EC1M3 Daily Performance Screen



Daily Performance

7/13 7/12 7/11

Code Violations : 0 0 0

Errored Seconds : 0 0 0

Severely Errored Seconds : 0 0 0

Unavailable Seconds : 41820 86307 39142

Fault Count : 0 0 1

Selection:



61184500L1-6J 231

DS3M3E/DS3M3TTo access the Performance Monitoring options for the DS3M3E or DS3M3T, complete the following steps:


2. From the MS Modules menu, select a DS3M3E or DS3M3T module, and press ENTER.


A DS3M3E Performance Monitoring menu is shown in Figure 147.

Figure 147. DS3M3E Performance Monitoring Menu

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.




1. DS3 1 : Some Errors



4. Reset PM Summary





Selection:



232 61184500L1-6J

A DS3M3T Daily Performance menu is shown in Figure 148.

Figure 148. DS3M3T Daily Performance Menu

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.

Figure 149. DS3M3E Daily Performance - Line Near End Customer Interface Screen



DS3 1 - Daily Performance

1. Line Near End - Customer Interface

2. Path Near End - Customer Interface P-Bit

3. Path Near End - Customer Interface C-Bit

4. Path Far End - Customer Interface

5. Path Near End - Network Interface P-Bit

6. Path Near End - Network Interface C-Bit

7. Path Far End - Network Interface

Selection:




DS3 1 - Daily Performance - Line Near End - Customer Interface

10/6

Code Violations : 0

Errored Seconds : 0



Selection:



61184500L1-6J 233

DS1M/DS1M2To access the Performance Monitoring options for the DS1M or DS1M2, complete the following steps:


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.

Figure 150. DS1 Performance Monitoring Menu

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.




1. DS1 # 1 : 15. DS1 #15 :

2. DS1 # 2 : 16. DS1 #16 :

3. DS1 # 3 : 17. DS1 #17 :

4. DS1 # 4 : 18. DS1 #18 : 29. DS3 Path : E

5. DS1 # 5 : 19. DS1 #19 : 30. DS3 CBIT Path Near End : E

6. DS1 # 6 : 20. DS1 #20 : 31. DS3 CBIT Path Far End : E

7. DS1 # 7 : 21. DS1 #21 : 32. Reset PM Summary

8. DS1 # 8 : 22. DS1 #22 : 33. Reset All PM Data

9. DS1 # 9 : 23. DS1 #23 : 34. Reset All PM Thresholds to Defaults

10. DS1 #10 : 24. DS1 #24 : 35. Enable All PM Thresholds

11. DS1 #11 : 25. DS1 #25 : 36. Disable All PM Thresholds

12. DS1 #12 : 26. DS1 #26 :

13. DS1 #13 : 27. DS1 #27 :

14. DS1 #14 : 28. DS1 #28 :

Selection:



234 61184500L1-6J

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.

Figure 151. DS1 Daily Performance Screen



DS1 # 1 - Daily Performance

5/14

BiPolar Violations : 0

Errored Seconds : 0



Fault Count : 0

Selection:



61184500L1-6J 235

DS1VM/DS1VM2To access the Performance Monitoring options for the DS1VM/DS1VM2, complete the following steps:




A DS1VM2 Performance Monitoring menu is shown in Figure 152.

Figure 152. DS1VM2 Performance Monitoring Menu

4. From the Performance Monitoring menu, select the required DS1, and press ENTER.

There are also options for resetting the performance monitoring data.




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:



236 61184500L1-6J

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.

Figure 153. DS1 Quarter Hourly Performance Menu

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.

Figure 154. DS1 Quarter Hourly Performance Screen



DS1 # 1 - Quarter Hourly Performance

1. Line (Near End) - Customer Interface

2. Path (Near End) - Customer Interface

3. Path (Far End) - Customer Interface

4. Path (Near End) - Network Interface

5. Path (Far End) - Network Interface

Selection:





10:15 10:00 9:45 9:30

BiPolar Violations : 0 0 0 0

Errored Seconds : 0 0 0 0

Severely Errored Seconds : 0 0 0 0

Unavailable Seconds : 0 0 0 0

Fault Count : 0 0 0 0

Selection:



61184500L1-6J 237

DS1VME/DS1VMTTo access the Performance Monitoring options for the DS1VME/DS1VMT, complete the following steps:



3. From the DS1VME/DS1VMT Module menu, select Performance Monitoring, and press ENTER.

A DS1VME/DS1VMT Performance Monitoring menu is shown in Figure 155.

Figure 155. DS1VME/DS1VMT Performance Monitoring Menu

4. From the Performance Monitoring menu, select the required DS1, and press ENTER.

There are also options for resetting the performance monitoring data.




1. DS1 # 1 : Alarm Errors 16. DS1 #16 :

2. DS1 # 2 : 17. DS1 #17 :

3. DS1 # 3 : 18. DS1 #18 :

4. DS1 # 4 : 19. DS1 #19 :

5. DS1 # 5 : 20. DS1 #20 :

6. DS1 # 6 : 21. DS1 #21 :

7. DS1 # 7 : 22. DS1 #22 :

8. DS1 # 8 : 23. DS1 #23 :

9. DS1 # 9 : 24. DS1 #24 :

10. DS1 #10 : 25. DS1 #25 :

11. DS1 #11 : 26. DS1 #26 :

12. DS1 #12 : 27. DS1 #27 :

13. DS1 #13 : 28. DS1 #28 :

14. DS1 #14 : 29. Reset PM Summary

15. DS1 #15 : 30. Reset All PM Data

Selection:



238 61184500L1-6J

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.

Figure 156. DS1 Quarter Hourly Performance Menu

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.

Figure 157. DS1 Quarter Hourly Performance - Line (Near End)Customer Interface Screen




1. Line (Near End) - Customer Interface

2. Path (Near End) - Customer Interface

3. Path (Far End) - Customer Interface

4. Path (Near End) - Network Interface

5. Path (Far End) - Network Interface

Selection:




DS1 # 1 - Quarter Hourly Performance - Line (Near End) - Customer Interface

12:15 12:00 11:45 11:30 11:15 11:00

Coding Violations : 0 0 0 0 0 0

Errored Seconds : 0 0 0 0 0 0

Severely Errored Seconds : 0 0 0 0 0 0

Unavailable Seconds : 132 900 900 900 900 732

Selection:



61184500L1-6J 239

Performance Remote Messaging

When framing is selected for ESF on a facility, Performance Remote Message (PRM), through the ESF Data Link, is transmitted on both customer and network ends. It is transmitted once per second, except when AIS or RAI are being asserted. On the receive side of both customer and network endpoints, any received PRM updates the Far End PM of each respective endpoint with reported CRC, severely-errored framing, or frame-synchronization bit errors. The rate of any received PRM message is once per second.


240 61184500L1-6J

TRAMTo access the Performance Monitoring options for the TRAM, complete the following steps:


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.

Figure 158. TRAM Performance Monitoring Menu

4. From the Performance Monitoring menu, select Line Near End, and press ENTER.




1. Line Near End

2. P-Bit Near End


Selection:



61184500L1-6J 241

The Line Near End menu is shown in Figure 159.

Figure 159. TRAM Line Near End PM Menu

5. A daily or quarter hourly performance or threshold must be selected.

The Line Near End Daily Thresholds menu is shown in Figure 160.

Figure 160. Line Near End Daily Thresholds Menu

6. Press ESC to return to the TRAM Performance Monitoring menu.



Line Near End



3. Daily Thresholds

4. Quarter Hourly Thresholds

Selection:




Line Near End - Daily Thresholds

1. Code Violations : 125

2. Errored Seconds : 100

3. Severely Errored Seconds : 7

4. Unavailable Seconds : 10

6. Code Violations : Disable

7. Errored Seconds : Disable

8. Severely Errored Seconds : Disable

9. Unavailable Seconds : Disable

Selection:



242 61184500L1-6J

7. From the Performance Monitoring menu, select P-Bit Near End, and press ENTER.


The P-Bit Near End - Quarter Hourly Thresholds menu is shown in Figure 161.

Figure 161. P-Bit Near End Daily Thresholds Menu



P-Bit Near End - Quarter Hourly Thresholds









Selection:



61184500L1-6J 243

TRAM3To access the Performance Monitoring options for the TRAM3, complete the following steps:


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.

Figure 162. TRAM3 Performance Monitoring Menu




1. Facility #1 Line Near End

2. Facility #1 C-Bit Near End

3. Facility #1 C-Bit Far End

4. Facility #1 P-Bit Near End










Selection:



244 61184500L1-6J

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.

Figure 163. TRAM3 Line Near End PM Menu


The Line Near End - Daily Thresholds menu is shown in Figure 164.

Figure 164. Line Near End Daily Thresholds Menu



Facility #1 Line Near End



3. Daily Thresholds

4. Quarter Hourly Thresholds


Selection:




Facility #1 Line Near End - Daily Thresholds









Selection:



61184500L1-6J 245

6. Press ESC to return to the TRAM3 Performance Monitoring menu.

7. From the Performance Monitoring menu, select P-Bit Near End, and press ENTER.


The P-Bit Near End - Quarter Hourly Thresholds performance monitoring menu is shown in Figure 165.

Figure 165. P-Bit Near End Daily Thresholds Menu



Facility #1 P-Bit Near End - Quarter Hourly Thresholds









Selection:



246 61184500L1-6J

O3TMTo access the Performance Monitoring options for an OC-3 tributary module, complete the following steps:


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.

Figure 166. O3TM Performance Monitoring Menu






3. STS-1 Path #1 :

4. STS-1 Path #2 :

5. STS-1 Path #3 :

6. Reset PM Summary





Selection:



61184500L1-6J 247

O12TMETo access the Performance Monitoring options for the O12TME module, complete the following steps:


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.

Figure 167. O12TME Performance Monitoring Menu





1. OC-12 Section Performance Monitoring : No Errors

2. OC-12 Line Performance Monitoring : No Errors



5. STS-1 Performance Monitoring : Alarm Errors

6. VT1.5 Performance Monitoring : No Errors

7. Clear All Summaries

8. Reset All Data

9. Reset All Thresholds to Defaults

10. Enable All Thresholds

11. Disable All Thresholds

Selection:



248 61184500L1-6J

GECMTo access the Performance Monitoring options for the GECM, complete the following steps:


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.

Figure 168. GECM Performance Monitoring Menu







Selection:



61184500L1-6J 249

GESM/GEMMTo access the Performance Monitoring options for the GESM or GEMM, complete the following steps:


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.

Figure 169. GESM Performance Monitoring Menu







Selection:



250 61184500L1-6J

GEFM/GEFMEHTo access the Performance Monitoring options for the GEFM or GEFMEH, complete the following steps:


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.

Figure 170. GEFM Performance Monitoring Menu







Selection:


Protection Switching

61184500L1-6J 251

PROTECTION SWITCHINGThis 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.

Figure 171. OC-3 Protection Configuration Screen



OC-3 Protection Configuration

1. APS Command : No Request

Transmit K1 Request : (0x0) No Request

Transmit K1 Request Channel : 0

Transmit K2 Bridged Channel : 0

Transmit K2 APS Architecture : 1+1

Transmit K2 APS Mode : Unidirectional

Receive K1 Request : (0x0) No Request

Receive K1 Request Channel : 0

Receive K2 Bridged Channel : 0

Receive K2 APS Architecture : 1+1

Receive K2 APS Mode : Unidirectional

Selection:



252 61184500L1-6J

Terminal ModeThe OMM48 Protection Configuration menu for Terminal mode is shown in Figure 172.

Figure 172. OMM48 Terminal Mode Protection Configuration Menu

HS Facility ProtectionLinear 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.



Protection Configuration

1. OC-48 Protection Configuration

2. Equipment Protection Configuration

3. Clock Protection Configuration

4. STS-12C Protection Configuration

5. STS-3C Protection Configuration

6. STS-1 Protection Configuration

7. VT1.5 Protection Configuration

Selection:



61184500L1-6J 253

Protected STS-1 PathsThe OPTI-6100 uses STS-1 Path selection on each of its tributary modules. In the drop (or demux) direction, the selector on the tributary module selects traffic from the online facility unless it detects a fault at the STS-1 level. In this case it selects the traffic from the other fiber. In the add (or mux) direction, the selector on each of the OMM modules selects traffic from the online tributary module. The tributary module bridges the traffic to each OMM module. On power up the tributary modules are biased towards traffic selection from the module in HS1.

Mapping Protected Paths

A maximum of three STS-1 SPEs can be dropped to a mid-speed slot or a pair of slots if the modules are in a redundant configuration. There is one selector per STS-1 drop (maximum of three) on each tributary module and similarly one selector in the add direction per STS-1 on the OMM modules for a maximum of three on the OMM3. Each dropped STS-1 is required to be mapped identically on the modules in both HS1 and HS2.

Unprotected STS-1 PathsBesides better fault tolerance, an advantage of architecture based on individual path selection is the flexibility it provides. The protection at the STS-1 level is optional and can be turned off selectively for any of the STS-1s. This feature allows a system to carry protected payload on some of the STS-1s while the others carry unprotected traffic.

Mapping Unprotected Paths

The path selector and traffic bridging is disabled if the STS-1 is mapped only on one of the OMM modules. The STS-1 on the other OMM module can be unmapped or mapped differently. For example, HS1-STS-1-1 on HS1 could be mapped to carry Ethernet payload from a tributary module, and HS2-STS-1-1 could be mapped to carry a payload from a different source.


254 61184500L1-6J

Line APSThe 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.

APS Channel Protocol

The APS channel protocol that is carried in the K1 and K2 bytes on the HS2 fiber is supported. The protocol is not really needed to complete protection switch actions in the case of 1+1 unidirectional operations. It is supported for informational purposes only. The K1 byte is used to inform the far-end of near-end events, and the K2 byte is set to indicate that the K1 byte is being received. For 1+1 unidirectional switching, the working channel is continuously bridged to the protection line. The far end is free to select traffic from either of the fibers. Bridging is performed at the STS-1 level on each of the tributary modules.


61184500L1-6J 255

Automatic Switch CriteriaLine Switch and Path Switch criteria are supported. The Signal Fail and Signal Degrade failures cause insertion of AIS-P downstream that results in a STS-1 Path switch on all the tributary modules that are capable of supporting it.

Line Switch Criteria

• Signal Fail: A Loss of Signal, Loss of Frame and AIS-L defects or a Line BER exceeding a user-provisionable threshold.

• Signal Degrade: A BER exceeding a user-provisionable threshold.

Path Switch Criteria

AIS-P, LOP-P and UEQ-P result in a Path switch on the tributary module that the STS-1 is mapped to.

APS Switch Commands

The APS switch commands as defined in GR253 is supported. Each switch command is issued to the OMM modules but the tributary modules are made aware of it through the communi-cation channel. One of the following switch commands can be issued to the APS controller either through TL1 commands or the menus:

• Clear

• Lockout Of Protection

• Forced Switch of Working (to Protection)

• Forced Switch of Protection (to Working)

• Manual Switch of Working (to Protection)

• Manual Switch of Protection (to Working)

Switch commands that control each individual STS-1 Path are not supported.

Switch Initiation Time

For LOS, LOF,AIS-L, AIS-P, LOP-P and UEQ-P the switch is initiated in 10 ms or less. For SF and SD conditions the time allowed varies with the actual BER.

Switch Completion Time

The switch is completed within 50 ms of detecting it.


256 61184500L1-6J

UPSR ModeA 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.

Automatic Switch CriteriaThe following automatic switch initiation criteria are supported:

• LOP-P, AIS-P, SLM-P, UEQ-P, LOP-V, AIS-V, SLM-V, UEQ-V

• SF-P, SD-P, SD-V

Hierarchy of Switch Criteria

The following is a list of APS requests possible on OPTI-6100 in descending order of priorities. A new request is not processed if a request of equal or higher priority is in effect. A switch command must be cleared before another switch command can be accepted.

1. Lockout Of Protection

2. Forced Switch

3. Automatic Switch criteria.

4. Manual Switch

5. Wait To Restore

NOTEA Forced Switch command permits traffic to be switched into afacility that may be in a fault state.


61184500L1-6J 257

CommandsThe 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


258 61184500L1-6J

The OC-12 Protection Configuration menu is shown in Figure 173.

Figure 173. Protection Configuration Menu

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.

Figure 174. Path Protection Configuration Menu



Protection Configuration

1. OC-12 Protection Configuration

2. STS-3C Path Protection Configuration

3. STS-1 Path Protection Configuration

4. VT Protection Configuration

5. Equipment Protection Configuration

6. Clock Protection Configuration

Selection:




STS-1 Path Protection Configuration

STS-1 1 : No Request Online : <VT Mapped>

STS-1 2 : No Request Online : <VT Mapped>

3. STS-1 3 : No Request Online : HS2

STS-1 4 : No Request Online : <Not Configured>









Selection:



61184500L1-6J 259

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.


260 61184500L1-6J

Path Selection ProvisioningThe STS-1, STS3c and VT1.5 path selectors can be provisioned to support the following features.

Revertive SwitchingEach 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.

Path Protection Switch ReportsThe user has the capability to provision a path protection switch as either “reported” (Enable) or “not reported” (Disable). The default is Disable. The path protection switch reports are always reported as events (alerts). An alert is cleared when a switch back to the preferred path occurs.

Path BER DetectionThe STS-3c and STS-1 Paths (STS-1 Path Provisioning menu shown in Figure 175) can be provisioned to detect excessive STS BER (10–3 to 10–5) and STS SD (10–5 to 10–9).

Figure 175. STS-1 Path Provisioning Menu



STS-1 1 Provisioning

Path Preference : <Not Applicable>

2. HS1 Expected Signal Label : Equip-Non Spec (0x01)

3. HS2 Expected Signal Label : Equip-Non Spec (0x01)

HS1 Transmit Signal Label : VT-Struct STS-1 (0x02)

HS2 Transmit Signal Label : VT-Struct STS-1 (0x02)

HS1 Receive Signal Label : Equip-Non Spec (0x01)

HS2 Receive Signal Label : VT-Struct STS-1 (0x02)

8. Excess BER Detect : 10 E -3

9. Signal Degrade : 10 E -6

10. Revertive Switch : Disable

11. Revertive Switch Time : 5 minutes

12. Path Switch Reports : Disable

Selection:



61184500L1-6J 261

Equipment ProtectionA 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.

Automatic Switch CriteriaThe following automatic switch initiation criteria are supported:

1. A service affecting equipment fault detected

2. A loss of communication due to a fault (OMM only)

3. A loss of communication over the management channel due to a fault (tributary modules only)


262 61184500L1-6J

Switch CommandsThe 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.

Figure 176. Equipment Protection Configuration Menu



Equipment Protection Configuration

1. Switch Now

Equipment Status : Online

Selection:



61184500L1-6J 263

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.

Figure 177. Terminal Configuration

STATUS

OMM12LR1184504L1

ALARM

ON LINE

TEST

SOCN

EK0C

AASO

CNEK

0CAA

MSO

CN

EK0C

AA

MM

SOC

NEK

0CA

AM

STATUS

ALARM

ONLINE

TEST

SOC2

490G

AASO

C249

0GAA

MSO

C24

90G

AA

MM

SOC

2490

GA

AM

DS1M1184513L1

STATUS

ALARM

ONLINE

TEST

SOC2

490G

AASO

C249

0GAA

MSO

C24

90G

AA

MM

SOC

2490

GA

AM

DS1M1184513L1

STATUS

OMM12LR1184504L1

ALARM

ON LINE

TEST

SOCN

EK0C

AASO

CNEK

0CAA

MSO

CN

EK0C

AA

MM

SOC

NEK

0CA

AM

AddSelector

AddSelector

DropSelector

DropSelector

HS1 Rx HS1 Tx HS2 Rx

OMM3/12 OMM3/12

MS2MS1

HS2 Tx


264 61184500L1-6J

This page is intentionally blank.

61184500L1-6J A-1

Appendix AAlarms List

INTRODUCTIONThe 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

OPTI-6100 M

aintenance and Troubleshooting Practice

A-2

61184500L1-6J

ALARMS BY MODULE

Table A-1. OMM3, OMM12, and OMM 48 Alarms

Description Interface Type Severity TL1 Condition SNMP Trap

Loss of Signal OC3/12/48 Facility Critical/Minor LOS adgenOMMXLosAlm

Loss of Frame OC3/12/48 Facility Critical/Minor LOF adgenOMMXLofAlm

Signal Degrade OC3/12/48 Facility Critical/Minor SD adgenOMMXSdAlm

Signal Fail OC3/12/48 Facility Critical/Minor SF adgenOMMXSfAlm

Remote Failure Indication OC3/12/48 Facility Alert RFI-L adgenOMMXRfilClrAlm

Alarm Indication Signal (Line) OC3/12/48 Facility Alert AIS-L adgenOMMXAislAlm

Alarm Indication Signal (Path) STS-1 Facility Alert AIS-P adgenOMMXAispAlm

Loss of Pointer (Path) STS-1 Facility Critical/Minor LOP-P adgenOMMXLopAlm

Unequipped (Path) STS-1 Facility Critical/Minor UNEQ-P adgenOMMXUneqpAlm

Signal Label Mismatch STS-1 Facility Critical/Minor SLMF adgenOMMXSlmAlm

Path Trace Mismatch STS-1 Facility Alert TIM-P adgenOMMXTimpAlm

Remote Failure Indication STS-1 Facility Alert RFI-P adgenOMMXRfipAlm

Signal Degrade STS-1 Facility Critical/Minor SD-P adgenPathSdAlm

Signal Fail STS-1 Facility Critical/Minor SF-P adgenPathSfAlm

Alarm Indication Signal (Path) STS-3 Facility Alert AIS-P adgenOMMXAispAlm

Loss of Pointer (Path) STS-3 Facility Critical/Minor LOP-P adgenOMMXLopAlm

Unequipped (Path) STS-3 Facility Critical/Minor UNEQ-P adgenOMMXUneqpAlm

Signal Label Mismatch STS-3 Facility Critical/Minor SLMF adgenOMMXSlmAlm

Path Trace Mismatch STS-3 Facility Alert TIM-P adgenOMMXTimpAlm

Remote Failure Indication STS-3 Facility Alert RFI-P adgenOMMXRfipAlm


Appendix A, Alarms List - Alarm

s by Module

61184500L1-6JA

-3


Loss of Pointer (VT) VT1.5 Facility Major/Minor LOP-V adgenVtLopAlm

Alarm Indication Signal (VT) VT1.5 Facility Alert AIS-V adgenVtAisAlm

Unequipped (VT) VT1.5 Facility Major/Minor UNEQ-V adgenVtUeqAlm

Signal Label Mismatch (VT) VT1.5 Facility Major/Minor SLM-V adgenVtSlmAlm

Remote Failure Indication (VT) VT1.5 Facility Alert RFI-V adgenVtRfiAlm

Signal Fail (VT) VT1.5 Facility Major/Minor SF-V adgenVtSfAlm

Signal Degrade (VT) VT1.5 Facility Major/Minor SD-V adgenVtSdAlm

Primary Bits Failure Clock ENV Minor SYNCPRI adgenOMMXPriCLKFailAlm

Secondary Bits Failure Clock ENV Minor SYNCSEC adgenOMMXSecCLKFailAlm

Holdover Clock Equip Alert SYNCCLK adgenOMMXCLKHoldOverSetAlm

Line Loopback OC3/12/48 Facility Alert LPBKLINE adgenOMMXLineLPBKAlm

Local Loopback OC3/12/48 Facility Alert LPBKTERM adgenOMMXLocalLPBKAlm

Equipment Switch ON Card Equip Alert WKSWPR adgenOMMXApsEqptOnAlm

Path Switch ON OC3/12/48 Facility Alert WKSWPR adgenOMMXApsLineOnAlm

Equipment Service Affected Alarm Card Equip Critical/Minor EQPT adgenOMMXEqptAlm

LOF with an MS slot detected Card Equip NA EQPT adgenOMMXEqptLofAlm

Clock Protection Switch Event Clock Equip Alert SYNCPS adgenOMMXCLKProtSwitchSetAlm

Maintenance Alert Notification Card Equip Alert MAN adgenOMMXManAlm

Section Coding Violation (Qtr) OC3/12/48 Facility Alert T-CVS adgenOMMXQtrSecCvAlm

Section Errored Seconds (Qtr) OC3/12/48 Facility Alert T-ESS adgenOMMXQtrSecEsAlm

Section Severely Errored Seconds (Qtr)

OC3/12/48 Facility Alert T-SESS adgenOMMXQtrSecSesAlm

Table A-1. OMM3, OMM12, and OMM 48 Alarms (Continued)


OPTI-6100 M


A-4

61184500L1-6J

Section Errored Framing Seconds (Qtr)

OC3/12/48 Facility Alert T-SEFSS adgenOMMXQtrSecSefsAlm

Line Near End Coding Violation (Qtr)

OC3/12/48 Facility Alert T-CVL adgenOMMXQtrLineCvAlm

Line Near End Errored Seconds (Qtr)

OC3/12/48 Facility Alert T-ESL adgenOMMXQtrLineEsAlm

Line Near End Severely Errored Seconds (Qtr)

OC3/12/48 Facility Alert T-SESL adgenOMMXQtrLineSesAlm

Line Near End Unavailable Seconds (Qtr)

OC3/12/48 Facility Alert T-UASL adgenOMMXQtrLineUasAlm

Line Far End Coding Violation (Qtr)

OC3/12/48 Facility Alert T-CV-LFE adgenOMMXQtrFELineCvAlm

Line Far End Errored Seconds (Qtr)

OC3/12/48 Facility Alert T-ES-LFE adgenOMMXQtrFELineEsAlm

Line Far End Severely Errored Seconds (Qtr)

OC3/12/48 Facility Alert T-SES-LFE adgenOMMXQtrFELineSesAlm

Line Far End Unavailable Seconds (Qtr)

OC3/12/48 Facility Alert T-UAS-LFE adgenOMMXQtrFELineUasAlm

Path Near End Coding Violation (Qtr)

STS-1 Facility Alert T-CVP adgenOMMXQtrPathCvAlm

Path Near End Errored Seconds (Qtr)

STS-1 Facility Alert T-ESP adgenOMMXQtrPathEsAlm

Path Near End Severely Errored Seconds (Qtr)

STS-1 Facility Alert T-SESP adgenOMMXQtrPathSesAlm

Path Near End Unavailable Seconds (Qtr)

STS-1 Facility Alert T-UASP adgenOMMXQtrPathUasAlm

Path Far End Coding Violation (Qtr)

STS-1 Facility Alert T-CV-PFE adgenOMMXQtrFEPathCvAlm




s by Module

61184500L1-6JA

-5

Path Far End Errored Seconds (Qtr)

STS-1 Facility Alert T-ES-PFE adgenOMMXQtrFEPathEsAlm

Path Far End Severely Errored Seconds (Qtr)

STS-1 Facility Alert T-SES-PFE adgenOMMXQtrFEPathSesAlm

Path Far End Unavailable Seconds (Qtr)

STS-1 Facility Alert T-UAS-PFE adgenOMMXQtrFEPathUasAlm

Path Near End Coding Violation (Qtr)

STS-3 Facility Alert T-CVP adgenSonetTHSTS3CQPNCVSetAlm

Path Near End Errored Seconds (Qtr)

STS-3 Facility Alert T-ESP adgenSonetTHSTS3CQPNESSetAlm


STS-3 Facility Alert T-SESP adgenSonetTHSTS3CQPNSESSetAlm

Path Near End Unavailable Seconds (Qtr)

STS-3 Facility Alert T-UASP adgenSonetTHSTS3CQPNUASSetAlm

Path Far End Coding Violation (Qtr)

STS-3 Facility Alert T-CV-PFE adgenSonetTHSTS3CQPFCVSetAlm

Path Far End Errored Seconds (Qtr)

STS-3 Facility Alert T-ES-PFE adgenSonetTHSTS3CQPFESSetAlm


STS-3 Facility Alert T-SES-PFE adgenSonetTHSTS3CQPFSESSetAlm

Path Far End Unavailable Seconds (Qtr)

STS-3 Facility Alert T-UAS-PFE adgenSonetTHSTS3CQPFUASSetAlm

VT1.5 Near End Coding Violation (Qtr)

VT1.5 Facility Alert T-CV-V adgenOMMXQtrVTNECvAlm

VT1.5 Near End Errored Seconds (Qtr)

VT1.5 Facility Alert T-ES-V adgenOMMXQtrVTNEEsAlm

VT1.5 Near End Severely Errored Seconds (Qtr)

VT1.5 Facility Alert T-SES-V adgenOMMXQtrVTNESesAlm



OPTI-6100 M


A-6

61184500L1-6J

VT1.5 Near End Unavailable Seconds (Qtr)

VT1.5 Facility Alert T-UAS-V adgenOMMXQtrVTNEUasAlm

VT1.5 Far End Coding Violation (Qtr)

VT1.5 Facility Alert T-CV-VFE adgenOMMXQtrVTFECvAlm

VT1.5 Far End Errored Seconds (Qtr)

VT1.5 Facility Alert T-ES-VFE adgenOMMXQtrVTFEEsAlm

VT1.5 Far End Severely Errored Seconds (Qtr)

VT1.5 Facility Alert T-SES-VFE adgenOMMXQtrVTFESesAlm

VT1.5 Far End Unavailable Seconds (Qtr)

VT1.5 Facility Alert T-UAS-VFE adgenOMMXQtrVTFEUasAlm

Section Coding Violation (Day) OC3/12/48 Facility Alert T-CVS adgenOMMXDaySecCvAlm

Section Errored Seconds (Day) OC3/12/48 Facility Alert T-ESS adgenOMMXDaySecEsAlm

Section Servers Errored Seconds (Day)

OC3/12/48 Facility Alert T-SESS adgenOMMXDaySecSesAlm

Section Errored Framing Seconds (Day)

OC3/12/48 Facility Alert T-SEFSS adgenOMMXDaySecSefsAlm

Line Near End Coding Violation (Day)

OC3/12/48 Facility Alert T-CVL adgenOMMXDayLineCvAlm

Line Near End Errored Seconds (Day)

OC3/12/48 Facility Alert T-ESL adgenOMMXDayLineEsAlm

Line Near End Severely Errored Seconds (Day)

OC3/12/48 Facility Alert T-SESL adgenOMMXDayLineSesAlm

Line Near End Unavailable Seconds (Day)

OC3/12/48 Facility Alert T-UASL adgenOMMXDayLineUasAlm

Line Far End Coding Violation (Day)

OC3/12/48 Facility Alert T-CV-LFE adgenOMMXDayFELineCvAlm

Line Far End Errored Seconds (Day)

OC3/12/48 Facility Alert T-ES-LFE adgenOMMXDayFELineEsAlm




s by Module

61184500L1-6JA

-7

Line Far End Severely Errored Seconds (Day)

OC3/12/48 Facility Alert T-SES-LFE adgenOMMXDayFELineSesAlm

Line Far End Unavailable Seconds (Day)

OC3/12/48 Facility Alert T-UAS-LFE adgenOMMXDayFELineUasAlm

Path Near End Coding Violation (Day)

STS-1 Facility Alert T-CVP adgenOMMXDayPathCvAlm

Path Near End Errored Seconds (Day)

STS-1 Facility Alert T-ESP adgenOMMXDayPathEsAlm

Path Near End Severely Errored Seconds (Day)

STS-1 Facility Alert T-SESP adgenOMMXDayPathSesAlm

Path Near End Unavailable Seconds (Day)

STS-1 Facility Alert T-UASP adgenOMMXDayPathUasAlm

Path Far End Coding Violation (Day)

STS-1 Facility Alert T-CV-PFE adgenOMMXDayFEPathCvAlm

Path Far End Errored Seconds (Day)

STS-1 Facility Alert T-ES-PFE adgenOMMXDayFEPathEsAlm

Path Far End Severely Errored Seconds (Day)

STS-1 Facility Alert T-SES-PFE adgenOMMXDayFEPathSesAlm

Path Far End Unavailable Seconds (Day)

STS-1 Facility Alert T-UAS-PFE adgenOMMXDayFEPathUasAlm

Path Near End Coding Violation (Day)

STS-3 Facility Alert T-CVP adgenSonetTHSTS3CDPNCVSetAlm

Path Near End Errored Seconds (Day)

STS-3 Facility Alert T-ESP adgenSonetTHSTS3CDPNESSetAlm


STS-3 Facility Alert T-SESP adgenSonetTHSTS3CDPNSESSetAlm

Path Near End Unavailable Seconds (Day)

STS-3 Facility Alert T-UASP adgenSonetTHSTS3CDPNUASSetAlm



OPTI-6100 M


A-8

61184500L1-6J

Path Far End Coding Violation (Day)

STS-3 Facility Alert T-CV-PFE adgenSonetTHSTS3CDPFCVSetAlm

Path Far End Errored Seconds (Day)

STS-3 Facility Alert T-ES-PFE adgenSonetTHSTS3CDPFESSetAlm


STS-3 Facility Alert T-SES-PFE adgenSonetTHSTS3CDPFSESSetAlm

Path Far End Unavailable Seconds (Day)

STS-3 Facility Alert T-UAS-PFE adgenSonetTHSTS3CDPFUASSetAlm

VT1.5 Near End Coding Violation (Day)

VT1.5 Facility Alert T-CV-V adgenOMMXDayVTNECvAlm

VT1.5 Near End Errored Seconds (Day)

VT1.5 Facility Alert T-ES-V adgenOMMXDayVTNEEsAlm

VT1.5 Near End Severely Errored Seconds (Day)

VT1.5 Facility Alert T-SES-V adgenOMMXDayVTNESesAlm

VT1.5 Near End Unavailable Seconds (Day)

VT1.5 Facility Alert T-UAS-V adgenOMMXDayVTNEUasAlm

VT1.5 Far End Coding Violation (Day)

VT1.5 Facility Alert T-CV-VFE adgenOMMXDayVTFECvAlm

VT1.5 Far End Errored Seconds (Day)

VT1.5 Facility Alert T-ES-VFE adgenOMMXDayVTFEEsAlm

VT1.5 Far End Severely Errored Seconds (Day)

VT1.5 Facility Alert T-SES-VFE adgenOMMXDayVTFESesAlm

VT1.5 Far End Unavailable Seconds (Day)

VT1.5 Facility Alert T-UAS-VFE adgenOMMXDayVTFEUasAlm

Lock out of Protection OC3/12/48 Facility NA LOCKOUTOFPR adgenLinePsLckAlm

Force Switch to Working OC3/12/48 Facility NA FRCDWKSWBK adgenLineFSTWAlm

Force Switch to Protection OC3/12/48 Facility NA FRCDWKSWPR adgenLineFSTPAlm

Manual Switch to Working OC3/12/48 Facility NA MANWKSWBK adgenLineMSTWAlm




s by Module

61184500L1-6JA

-9

Manual Switch to Protection OC3/12/48 Facility NA MANWKSWPR adgenLineMSTPAlm

Switch to Working OC3/12/48 Facility NA WKSWPR adgenLineWSTPAlm

Switch to Protection OC3/12/48 Facility NA WKSWBK adgenLineWSBAlm

Lock out of Protection STS-1 Facility NA LOCKOUTOFPR adgenPathPsLckAlm

Force Switch to Working STS-1 Facility NA FRCDWKSWBK adgenPathFSTWAlm

Force Switch to Protection STS-1 Facility NA FRCDWKSWPR adgenPathFSTPAlm

Manual Switch to Working STS-1 Facility NA MANWKSWBK adgenPathMSTWAlm

Manual Switch to Protection STS-1 Facility NA MANWKSWPR adgenPathMSTPAlm

Switch to Working STS-1 Facility NA WKSWPR adgenPathWSTPAlm

Switch to Protection STS-1 Facility NA WKSWBK adgenPathWSBAlm








Lock out of Protection VT1.5 Facility NA LOCKOUTOFPR adgenVtPsLckAlm

Force Switch to Working VT1.5 Facility NA FRCDWKSWBK adgenVtFSTWAlm

Force Switch to Protection VT1.5 Facility NA FRCDWKSWPR adgenVtFSTPAlm

Manual Switch to Working VT1.5 Facility NA MANWKSWBK adgenVtMSTWAlm

Manual Switch to Protection VT1.5 Facility NA MANWKSWPR adgenVtMSTPAlm



OPTI-6100 M


A-10

61184500L1-6J

Note: There are three categories of switching events:• Line (or facility) 1+1 protection• Equipment (HS or MS) 1+1 or 1:1 protection• Path protection (UPSR mode only)

Switch to Working VT1.5 Facility NA WKSWPR adgenVtWSTPAlm

Switch to Protection VT1.5 Facility NA WKSWBK adgenVtWSBAlm

Equipment Switch to Protection VT1.5 Equip NA WKSWPR




s by Module

61184500L1-6JA

-11

Table A-2. DS1M and DS1M2 Alarms


Loss of Signal DS1 Facility Major LOS adTAOMXDS1AlmLosSet

Alarm Indication Signal DS1 Facility Alert AIS adTAOMXDS1AlmAISSet

DS3 Local Loopback Diagnostic Facility Alert LPBKTERM adTAOMXDS1AlmLocalLoopbackSet

Trib Loopback Diagnostic Facility Alert LB-TRI adTAOMXDS1AlmTribLoopbackSet

Local Loopback Diagnostic Facility Alert LPBKTERM adTAOMXDS1AlmAnalogLoopbackSet

Line Loopback Diagnostic Facility Alert LPBKLINE adTAOMXDS1AlmDigitalLoopbackSet

Codec Loopback Diagnostic Facility Alert LB-COD adTAOMXDS1AlmCodecLoopbackSet

CSU Loopback Diagnostic Facility Alert LB-CSU adTAOMXDS1AlmCSULoopbackSet

CSU BERT Loopback Diagnostic Facility Alert LB-BERT-CSU adTAOMXDS1AlmCSUBertLoopbackSet

Line BERT Loopback Diagnostic Facility Alert LB-BERT-L adTAOMXDS1AlmLineBertLoopbackSet

Equipment APS ON Card Equip Alert WKSWPR adTAOMXDS1AlmAPSEqpOnSet

Equipment Failed Card Equip Minor EQPT-FAIL adTAOMXDS1AlmAPSEqpOn

Loss of Frame DS3 DS3 Facility Major LOF adTAOMXDS1AlmDS3LOFSet

Alarm Indication Signal (DS3 Path)

DS3 Facility Alert AIS adTAOMXDS1AlmDS3AISPSet

Remote Alarm Indication (DS3 Path)

DS3 Facility Alert RAI adTAOMXDS1AlmDS3RAIPSet

Local (By Remote) Loopback DS3 DS3 Facility Alert LPBKTERM adTAOMXDS1AlmDS3RemoteLPBKDIDSet

Local (By Remote) Loopback DS1 DS1 Facility Alert LPBKTERM adTAOMXDS1AlmDS1RemoteLPBKDIDSet

Software Mismatch Card Equip Alert SW-MM adTAOMXDS1OMXSwMisMatchAlmSet

Invalid Slot Card Equip Alert INVD-SLOT adTAOMXDS1OMXInvalidSlotAlmSet

Redundancy Provisioning DS1 Facility Alert REDUN-PROV adTAOMXDS1OMXRedundancyProvErrAlmSet

Maintenance Alert Notification DS1 Facility Alert MAN adTAOMXDS1OMXMANAlmSet

Path Coding Violation (Qtr) DS3 Facility Alert T-CVP adTAOMXDS1QPCVTHAlmSet

OPTI-6100 M


A-12

61184500L1-6J

Path Errored Seconds (Qtr) DS3 Facility Alert T-ESP adTAOMXDS1QPESTHAlmSet

Path Severely Errored Seconds (Qtr)

DS3 Facility Alert T-SESP adTAOMXDS1QPSESTHAlmSet

Path Unavailable Seconds (Qtr) DS3 Facility Alert T-UASP adTAOMXDS1QPUASTHAlmSet

CBit Near End Coding Violation (Qtr)

DS3 Facility Alert T-CVCP-P adTAOMXDS1QNCCVTHAlmSet

CBit Near End Errored Seconds (Qtr)

DS3 Facility Alert T-ESCP-P adTAOMXDS1QNCESTHAlmSet

CBit Near End Severely Errored Seconds (Qtr)

DS3 Facility Alert T-SESCP-P adTAOMXDS1QNCSESTHAlmSet

CBit Near End Unavailable Seconds (Qtr)

DS3 Facility Alert T-UASCP-P adTAOMXDS1QNCUASTHAlmSet

CBit Far End Coding Violation (Qtr)

DS3 Facility Alert T-CVCP-PFE adTAOMXDS1QFCCVTHAlmSet

CBit Far End Errored Seconds (Qtr)

DS3 Facility Alert T-ESCP-PFE adTAOMXDS1QFCESTHAlmSet

CBit Far End Severely Errored Seconds (Qtr)

DS3 Facility Alert T-SESCP-PFE adTAOMXDS1QFCSESTHAlmSet

CBit Far End Unavailable Seconds (Qtr)

DS3 Facility Alert T-UASCP-PFE adTAOMXDS1QFCUASTHAlmSet

Path Coding Violation (Day) DS3 Facility Alert T-CVP adTAOMXDS1DPCVTHAlmSet

Path Errored Seconds (Day) DS3 Facility Alert T-ESP adTAOMXDS1DPESTHAlmSet

Path Severely Errored Seconds (Day)

DS3 Facility Alert T-SESP adTAOMXDS1DPSESTHAlmSet

Path Unavailable Seconds (Day) DS3 Facility Alert T-UASP adTAOMXDS1DPUASTHAlmSet

CBit Near End Coding Violation (Day)

DS3 Facility Alert T-CVCP-P adTAOMXDS1DNCCVTHAlmSet

Table A-2. DS1M and DS1M2 Alarms (Continued)



s by Module

61184500L1-6JA

-13

CBit Near End Errored Seconds (Day)

DS3 Facility Alert T-ESCP-P adTAOMXDS1DNCESTHAlmSet

CBit Near End Severely Errored Seconds (Day)

DS3 Facility Alert T-SESCP-P adTAOMXDS1DNCSESTHAlmSet

CBit Near End Unavailable Seconds (Day)

DS3 Facility Alert T-UASCP-P adTAOMXDS1DNCUASTHAlmSet

CBit Far End Coding Violation (Day)

DS3 Facility Alert T-CVCP-PFE adTAOMXDS1DFCCVTHAlmSet

CBit Far End Errored Seconds (Day)

DS3 Facility Alert T-ESCP-PFE adTAOMXDS1DFCESTHAlmSet

CBit Far End Severely Errored Seconds (Day)

DS3 Facility Alert T-SESCP-PFE adTAOMXDS1DFCSESTHAlmSet

CBit Far End Unavailable Seconds (Day)

DS3 Facility Alert T-UASCP-PFE adTAOMXDS1DFCUASTHAlmSet

Table A-2. DS1M and DS1M2 Alarms (Continued)


OPTI-6100 M


A-14

61184500L1-6J

Table A-3. DS1VM Alarms


Loss of Signal DS1 Facility Major LOS adTAOMXVT15AlmLosSet

Alarm Indication Signal DS1 Facility Alert AIS adTAOMXVT15AlmAISSet

Trib Loopback Diagnostic Facility Alert LB-TRI adTAOMXVT15AlmTribLoopbackSet

Local Loopback Diagnostic Facility Alert LPBKTERM adTAOMXVT15AlmAnalogLoopbackSet

Line Loopback Diagnostic Facility Alert LPBKLINE adTAOMXVT15AlmDigitalLoopbackSet

Codec Loopback Diagnostic Facility Alert LB-COD adTAOMXVT15AlmCodecLoopbackSet

CSU Loopback Diagnostic Facility Alert LB-CSU adTAOMXVT15AlmCSULoopbackSet

Equipment APS ON Card Equip Alert WKSWPR adTAOMXVT15AlmAPSEqpOnSet

Equipment Failed Card Equip Minor EQPT-FAIL adTAOMXVT15AlmEQPTSet

Local (By Remote) Loopback DS1 Diagnostic Facility Alert LPBKTERM adTAOMXVT15AlmRemoteLPBKDIDSet

Software Mismatch DS1 Facility Alert SW-MM adTAOMXVT15AlmSwMisMatchSet

Invalid Slot Card Equip Alert INVD-SLOT adTAOMXVT15AlmInvalidSlotSet

Redundancy Provisioning DS1 Facility Alert REDUN-PROV adTAOMXVT15AlmRedundancyProvErrSet

Maintenance Alert Notification DS1 Facility Alert MAN adTAOMXVT15AlmMANSet


s by Module

61184500L1-6JA

-15

Table A-4. DS1VME, DS1VMT, and DS1VM2 Alarms


Trib Loopback Diagnostic Facility Alert LB-TRI adTAOMXDS1VMEAlmTribLoopbackSet

Local Loopback Diagnostic Facility Alert LPBKTERM adTAOMXDS1VMEAlmAnalogLoopbackSet

Line Loopback Diagnostic Facility Alert LPBKLINE adTAOMXDS1VMEAlmDigitalLoopbackSet

Codec Loopback Diagnostic Facility Alert LB-COD adTAOMXDS1VMEAlmCodecLoopbackSet

CSU Loopback Diagnostic Facility Alert LB-CSU adTAOMXDS1VMEAlmCSULoopbackSet

Equipment APS ON Card Equip Alert WKSWPR adTAOMXDS1VMEAlmAPSEqpOnSet

Equipment Failed Card Equip Minor EQPT-FAIL adTAOMXDS1VMEAlmEQPTSet

Local (By Remote) Loopback DS1 Diagnostic Facility Alert LPBKTERM adTAOMXDS1VMEAlmRemoteLPBKDIDSet

Software Mis-Match Card Equip Alert SW-MM adTAOMXDS1VMEAlmSwMisMatchSet

Invalid Slot Card Equip Alert INVD-SLOT adTAOMXDS1VMEAlmInvalidSlotSet

Redundancy Provisioning DS1 Facility Alert REDUN-PROV adTAOMXDS1VMEAlmRedundancyProvErrSet

Maintenance Alert Notification DS1 Equip Alert MAN adTAOMXDS1VMEAlmMANSet

Loss of Signal From Customer Side

DS1 Facility Major LOS CP adTAOMXDS1VMEAlmLOSCLISet

Loss of Frame From Customer Side

DS1 Facility Major LOF CP adTAOMXDS1VMEAlmCLILOFSet

Alarm Indication Signal From Customer Side

DS1 Facility Alert AIS CP adTAOMXDS1VMEAlmCLIAISSet

Remote Alarm Indication From Customer Side

DS1 Facility Alert RAI CP adTAOMXDS1VMEAlmCLIRAISet

Loss of Frame Network Interface DS1 Facility Major LOF NI adTAOMXDS1VMEAlmNILOFSet

Alarm Indication Signal Network Interface

DS1 Facility Alert AIS NI adTAOMXDS1VMEAlmNIAISSet

Remote Alarm Indication Network Interface

DS1 Facility Alert RAI NI adTAOMXDS1VMEAlmNIRAISet

OPTI-6100 M


A-16

61184500L1-6J

Line Coding Violations (Qtr) Customer Interface

DS1 Facility Alert T-CVL-C adTAOMXDS1VMEQCVLCNAlmSet

Line Errored Seconds (Qtr) Customer Interface

DS1 Facility Alert T-ESL-C adTAOMXDS1VMEQESLCNAlmSet

Line Severely Errored Seconds (Qtr) Customer Interface

DS1 Facility Alert T-SESL-C adTAOMXDS1VMEQSESLCNAlmSet

Line Unavailable Seconds (Qtr) Customer Interface

DS1 Facility Alert T-UASL-C adTAOMXDS1VMEQUASLCNAlmSet

Path Coding Violations (Qtr) Customer Interface Near End

DS1 Facility Alert T-CV-PN-C adTAOMXDS1VMEQCVPCNAlmSet

Path Errored Seconds (Qtr) Customer Interface Near End

DS1 Facility Alert T-ES-PN-C adTAOMXDS1VMEQESPCNAlmSet

Path Severely Errored Seconds (Qtr) Customer Interface Near End

DS1 Facility Alert T-SES-PN-C adTAOMXDS1VMEQSESPCNAlmSet

Path Severely Errored Framing Seconds (Qtr) Customer Interface Near End

DS1 Facility Alert T-SEFS-PN-C adTAOMXDS1VMEQSEFSPCNAlmSet

Path Controlled Slip Seconds (Qtr) Customer Interface Near End

DS1 Facility Alert T-CSS-PN-C adTAOMXDS1VMEQCCSPCNAlmSet

Path Unavailable Seconds (Qtr) Customer Interface Near End

DS1 Facility Alert T-UAS-PN-C adTAOMXDS1VMEQUASPCNAlmSet

Path Coding Violations (Qtr) Customer Interface Far End

DS1 Facility Alert T-CV-PF-C adTAOMXDS1VMEQCVPCFAlmSet

Path Errored Seconds (Qtr) Customer Interface Far End

DS1 Facility Alert T-ES-PF-C adTAOMXDS1VMEQESPCFAlmSet

Path Severely Errored Seconds (Qtr) Customer Interface Far End

DS1 Facility Alert T-SES-PF-C adTAOMXDS1VMEQSESPCFAlmSet

Table A-4. DS1VME, DS1VMT, and DS1VM2 Alarms (Continued)



s by Module

61184500L1-6JA

-17

Path Severely Errored Framing Seconds (Qtr) Customer Interface Far End

DS1 Facility Alert T-SEFS-PF-C adTAOMXDS1VMEQSEFSPCFAlmSet

Path Controlled Slip Seconds (Qtr) Customer Interface Far End

DS1 Facility Alert T-CSS-PF-C adTAOMXDS1VMEQCCSPCFAlmSet

Path Unavailable Seconds (Qtr) Customer Interface Far End

DS1 Facility Alert T-UAS-PF-C adTAOMXDS1VMEQUASPCFAlmSet

Path Coding Violations (Qtr) Network Interface Near End

DS1 Facility Alert T-CV-PN-N adTAOMXDS1VMEQCVPNNAlmSet

Path Errored Seconds (Qtr) Network Interface Near End

DS1 Facility Alert T-ES-PN-N adTAOMXDS1VMEQESPNNAlmSet

Path Severely Errored Seconds (Qtr) Network Interface Near End

DS1 Facility Alert T-SES-PN-N adTAOMXDS1VMEQSESPNNAlmSet

Path Severely Errored Framing Seconds (Qtr) Network Interface Near End

DS1 Facility Alert T-SEFS-PN-N adTAOMXDS1VMEQSEFSPNNAlmSet

Path Controlled Slip Seconds (Qtr) Network Interface Near End

DS1 Facility Alert T-CSS-PN-N adTAOMXDS1VMEQCCSPNNAlmSet

Path Unavailable Seconds (Qtr) Network Interface Near End

DS1 Facility Alert T-UAS-PN-N adTAOMXDS1VMEQUASPNNAlmSet

Path Coding Violations (Qtr) Network Interface Far End

DS1 Facility Alert T-CV-PF-N adTAOMXDS1VMEQCVPNFAlmSet

Path Errored Seconds (Qtr) Network Interface Far End

DS1 Facility Alert T-ES-PF-N adTAOMXDS1VMEQESPNFAlmSet

Path Severely Errored Seconds (Qtr) Network Interface Far End

DS1 Facility Alert T-SES-PF-N adTAOMXDS1VMEQSESPNFAlmSet

Path Severely Errored Framing Seconds (Qtr) Network Interface Far End

DS1 Facility Alert T-SEFS-PF-N adTAOMXDS1VMEQSEFSPNFAlmSet



OPTI-6100 M


A-18

61184500L1-6J

Path Controlled Slip Seconds (Qtr) Network Interface Far End

DS1 Facility Alert T-CSS-PF-N adTAOMXDS1VMEQCCSPNFAlmSet

Path Unavailable Seconds (Qtr) Network Interface Far End

DS1 Facility Alert T-UAS-PF-N adTAOMXDS1VMEQUASPNFAlmSet

Line Coding Violations (Day) Customer Interface

DS1 Facility Alert T-CVL-C adTAOMXDS1VMEDCVLCNAlmSet

Line Errored Seconds (Day) Customer Interface

DS1 Facility Alert T-ESL-C adTAOMXDS1VMEDESLCNAlmSet

Line Severely Errored Seconds (Day) Customer Interface

DS1 Facility Alert T-SESL-C adTAOMXDS1VMEDSESLCNAlmSet

Line Unavailable Seconds (Day) Customer Interface

DS1 Facility Alert T-UASL-C adTAOMXDS1VMEDUASLCNAlmSet

Path Coding Violations (Day) Customer Interface Near End

DS1 Facility Alert T-CV-PN-C adTAOMXDS1VMEDCVPCNAlmSet

Path Errored Seconds (Day) Customer Interface Near End

DS1 Facility Alert T-ES-PN-C adTAOMXDS1VMEDESPCNAlmSet

Path Severely Errored Seconds (Day) Customer Interface Near End

DS1 Facility Alert T-SES-PN-C adTAOMXDS1VMEDSESPCNAlmSet

Path Severely Errored Framing Seconds (Day) Customer Interface Near End

DS1 Facility Alert T-SEFS-PN-C adTAOMXDS1VMEDSEFSPCNAlmSet

Path Controlled Slip Seconds (Day) Customer Interface Near End

DS1 Facility Alert T-CSS-PN-C adTAOMXDS1VMEDCCSPCNAlmSet

Path Unavailable Seconds (Day) Customer Interface Near End

DS1 Facility Alert T-UAS-PN-C adTAOMXDS1VMEDUASPCNAlmSet

Path Coding Violations (Day) Customer Interface Far End

DS1 Facility Alert T-CV-PF-C adTAOMXDS1VMEDCVPCFAlmSet




s by Module

61184500L1-6JA

-19

Path Errored Seconds (Day) Customer Interface Far End

DS1 Facility Alert T-ES-PF-C adTAOMXDS1VMEDESPCFAlmSet

Path Severely Errored Seconds (Day) Customer Interface Far End

DS1 Facility Alert T-SES-PF-C adTAOMXDS1VMEDSESPCFAlmSet

Path Severely Errored Framing Seconds (Day) Customer Interface Far End

DS1 Facility Alert T-SEFS-PF-C adTAOMXDS1VMEDSEFSPCFAlmSet

Path Controlled Slip Seconds (Day) Customer Interface Far End

DS1 Facility Alert T-CSS-PF-C adTAOMXDS1VMEDCCSPCFAlmSet

Path Unavailable Seconds (Day) Customer Interface Far End

DS1 Facility Alert T-UAS-PF-C adTAOMXDS1VMEDUASPCFAlmSet

Path Coding Violations (Day) Network Interface Near End

DS1 Facility Alert T-CV-PN-N adTAOMXDS1VMEDCVPNNAlmSet

Path Errored Seconds (Day) Network Interface Near End

DS1 Facility Alert T-ES-PN-N adTAOMXDS1VMEDESPNNAlmSet

Path Severely Errored Seconds (Day) Network Interface Near End

DS1 Facility Alert T-SES-PN-N adTAOMXDS1VMEDSESPNNAlmSet

Path Severely Errored Framing Seconds (Day) Network Interface Near End

DS1 Facility Alert T-SEFS-PN-N adTAOMXDS1VMEDSEFSPNNAlmSet

Path Controlled Slip Seconds (Day) Network Interface Near End

DS1 Facility Alert T-CSS-PN-N adTAOMXDS1VMEDCCSPNNAlmSet

Path Unavailable Seconds (Day) Network Interface Near End

DS1 Facility Alert T-UAS-PN-N adTAOMXDS1VMEDUASPNNAlmSet

Path Coding Violations (Day) Network Interface Far End

DS1 Facility Alert T-CV-PF-N adTAOMXDS1VMEDCVPNFAlmSet

Path Errored Seconds (Day) Network Interface Far End

DS1 Facility Alert T-ES-PF-N adTAOMXDS1VMEDESPNFAlmSet



OPTI-6100 M


A-20

61184500L1-6J

Path Severely Errored Seconds (Day) Network Interface Far End

DS1 Facility Alert T-SES-PF-N adTAOMXDS1VMEDSESPNFAlmSet

Path Severely Errored Framing Seconds (Day) Network Interface Far End

DS1 Facility Alert T-SEFS-PF-N adTAOMXDS1VMEDSEFSPNFAlmSet

Path Controlled Slip Seconds (Day) Network Interface Far End

DS1 Facility Alert T-CSS-PF-N adTAOMXDS1VMEDCCSPNFAlmSet

Path Unavailable Seconds (Day) Network Interface Far End

DS1 Facility Alert T-UAS-PF-N adTAOMXDS1VMEDUASPNFAlmSet




s by Module

61184500L1-6JA

-21

Table A-5. DS3EC1M and DS3EC1M3 Alarms


Loss of Signal DS3 DS3 Facility Major LOS adTAOMXDS3AlmLosSet

Loss of Signal EC1 EC1 Facility Major LOS adTAOMXDS3AlmEC1LosSet

Line Loopback DS3 Diagnostic Facility Alert LPBKLINE adTAOMXDS3AlmLineLoopbackSet

Local Loopback DS3 Diagnostic Facility Alert LPBKTERM adTAOMXDS3AlmLocalLoopbackSet

Line Loopback EC1 Diagnostic Facility Alert LPBKLINE adTAOMXDS3AlmLineLoopbackEC1Set

Local Loopback EC1 Diagnostic Facility Alert LPBKTERM adTAOMXDS3AlmLocalLoopbackEC1Set

Loss of Frame EC1 EC1 Facility Major LOF adTAOMXDS3AlmEC1LOFSet

Alarm Indication Signal EC1 EC1 Facility Alert AIS-L adTAOMXDS3AlmEC1AISLSet

Remote Failure Indication EC1 EC1 Facility Alert RFI-L adTAOMXDS3AlmEC1RFILSet

DS3/EC1 Mismatch Card Equip Alert DS3EC1-MM adTAOMXDS3EC1MisMatchAlmSet

Equipment APS ON Card Equip Alert WKSWPR adTAOMXDS3AlmAPSEqpOnSet

Equipment Failed Card Equip Minor EQPT-FAIL adTAOMXDS3AlmEQPTSet

Software Mismatch Card Equip Alert SW-MM adTAOMXDS3SwMisMatchAlmSet

Invalid Slot Card Equip Alert INVD-SLOT adTAOMXDS3InvalidSlotAlmSet

Redundancy Provisioning DS3 Facility Alert REDUN-PROV adTAOMXDS3RedundancyProvErrAlmClr

Maintenance Alert Notification Card Equip Alert MAN adTAOMXDS3MANAlmSet

Section Coding Violation (Qtr) EC1 Facility Alert T-CVS adTAOMXDS3EC1ALMTHQSectCVSet

Section Errored Seconds (Qtr) EC1 Facility Alert T-ESS adTAOMXDS3EC1ALMTHQSectESSet

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

OPTI-6100 M


A-22

61184500L1-6J


EC1 Facility Alert T-SESL adTAOMXDS3EC1ALMTHQLineNSESSet


EC1 Facility Alert T-UASL adTAOMXDS3EC1ALMTHQLineNUASSet

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


EC1 Facility Alert T-SES-LFE adTAOMXDS3EC1ALMTHQLineFSESSet

Line Far End Unavailable Seconds (Qtr) EC1 Facility Alert T-UAS-LFE adTAOMXDS3EC1ALMTHQLineFUASSet

Section Coding Violation (Day) EC1 Facility Alert T-CVS adTAOMXDS3EC1ALMTHDSectCVSet

Section Errored Seconds (Day) EC1 Facility Alert T-ESS adTAOMXDS3EC1ALMTHDSectESSet

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


EC1 Facility Alert T-SESL adTAOMXDS3EC1ALMTHDLineNSESSet


EC1 Facility Alert T-UASL adTAOMXDS3EC1ALMTHDLineNUASSet

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


EC1 Facility Alert T-SES-LFE adTAOMXDS3EC1ALMTHDLineFSESSet


EC1 Facility Alert T-UAS-LFE adTAOMXDS3EC1ALMTHDLineFUASSet

Table A-5. DS3EC1M and DS3EC1M3 Alarms (Continued)



s by Module

61184500L1-6JA

-23

Table A-6. DS3M3E and DS3M3T Alarms


Loss of Signal DS3 (Detected from Customer Interface)

DS3 Facility Major LOS adTAOMXDS3M3EAlmDS3LOSSet

Loss of Frame DS3 (Detected from Customer Interface)

DS3 Facility Major LOF-CP adTAOMXDS3M3EAlmDS3LOFCISet

Loss of Frame DS3 (Detected from Network Interface)

DS3 Facility Major LOF-NI adTAOMXDS3M3EAlmDS3LOFNISet

Alarm Indication Signal From Customer Side

DS3 Facility Alert AIS-CP adTAOMXDS3M3EAlmDS3AISCISet

Alarm Indication Signal Network Interface

DS3 Facility Alert AIS-NI adTAOMXDS3M3EAlmDS3AISNISet

Remote Alarm Indication From Customer Side

DS3 Facility Alert RAI-CP adTAOMXDS3M3EAlmDS3RAICISet

Remote Alarm Indication Network Interface

DS3 Facility Alert RAI-NI adTAOMXDS3M3EAlmDS3RAINISet

Line Loopback DS3 DS3 Facility Alert LPBKLINE adTAOMXDS3M3EAlmDS3LineLoopSet

Local Loopback DS3 DS3 Facility Alert LPBKTERM adTAOMXDS3M3EAlmDS3LocalLoopSet

Loss of Signal EC1 EC1 Facility Major LOS adTAOMXDS3M3EAlmEC1LOSSet

Loss of Frame EC1 EC1 Facility Major LOF adTAOMXDS3M3EAlmEC1LOFSet

Alarm Indication Signal EC1 EC1 Facility Alert AIS-L adTAOMXDS3M3EAlmEC1AISLSet

Remote Failure Indication EC1 EC1 Facility Alert RFI-L adTAOMXDS3M3EAlmEC1RFILSet

Line Loopback EC1 EC1 Facility Alert LPBKLINE adTAOMXDS3M3EAlmEC1LineLoopSet

Local Loopback EC1 EC1 Facility Alert LPBKTERM adTAOMXDS3M3EAlmEC1LocalLoopSet

DS3/EC1 Mismatch Card Equip Alert DS3ec1-MM adTAOMXDS3M3EEqptModeMisMatchAlmSet

Equipment APS ON Card Equip Alert WKSWPR adTAOMXDS3M3EAlmEqpAPSSet

Equipment Failed Card Equip Minor EQPT-FAIL adTAOMXDS3M3EAlmEqpFltSet

Software Mis-Match Card Equip Alert SW-MM adTAOMXDS3M3ESwMisMatchAlmSet

OPTI-6100 M


A-24

61184500L1-6J

Invalid Slot Card Equip Alert INVD-SLOT adTAOMXDS3M3EInvalidSlotAlmSet

Redundancy Provisioning Card Equip Alert REDUN-PROV adTAOMXDS3M3ERedundancyProvDisAlmSet

Maintenance Alert Notification Card Equip Alert MAN adTAOMXDS3M3EOMXMANAlmSet

Section Coding Violation (Qtr) EC1 Facility Alert T-CVS adTAOMXDS3M3EEC1AlmQTHSectCV

Section Errored Seconds (Qtr) EC1 Facility Alert T-ESS adTAOMXDS3M3EEC1AlmQTHSectES

Section Severely Errored Seconds (Qtr)

EC1 Facility Alert T-SESS adTAOMXDS3M3EEC1AlmQTHSectSES

Section Errored Framing Seconds (Qtr)

EC1 Facility Alert T-SEFS-S adTAOMXDS3M3EEC1AlmQTHSectSEFS


EC1 Facility Alert T-CVL adTAOMXDS3M3EEC1AlmQTHLineCV


EC1 Facility Alert T-ESL adTAOMXDS3M3EEC1AlmQTHLineES


EC1 Facility Alert T-SESL adTAOMXDS3M3EEC1AlmQTHLineSES


EC1 Facility Alert T-UASL adTAOMXDS3M3EEC1AlmQTHLineUAS

Line Far End Coding Violation (Qtr) EC1 Facility Alert T-CV-LFE adTAOMXDS3M3EEC1AlmQFTHLineCV

Line Far End Errored Seconds (Qtr)

EC1 Facility Alert T-ES-LFE adTAOMXDS3M3EEC1AlmQFTHLineES


EC1 Facility Alert T-SES-LFE adTAOMXDS3M3EEC1AlmQFTHLineSES

Line Far End Unavailable Seconds (Qtr)

EC1 Facility Alert T-UAS-LFE adTAOMXDS3M3EEC1AlmQFTHLineUAS

Section Coding Violation (Day) EC1 Facility Alert T-CVS adTAOMXDS3M3EEC1AlmDTHSectCV

Section Errored Seconds (Day) EC1 Facility Alert T-ESS adTAOMXDS3M3EEC1AlmDTHSectES

Table A-6. DS3M3E and DS3M3T Alarms (Continued)



s by Module

61184500L1-6JA

-25

Section Severely Errored Seconds (Day)

EC1 Facility Alert T-SESS adTAOMXDS3M3EEC1AlmDTHSectSES

Section Errored Framing Seconds (Day)

EC1 Facility Alert T-SEFS-S adTAOMXDS3M3EEC1AlmDTHSectSEFS


EC1 Facility Alert T-CVL adTAOMXDS3M3EEC1AlmDTHLineCV


EC1 Facility Alert T-ESL adTAOMXDS3M3EEC1AlmDTHLineES


EC1 Facility Alert T-SESL adTAOMXDS3M3EEC1AlmDTHLineSES


EC1 Facility Alert T-UASL adTAOMXDS3M3EEC1AlmDTHLineUAS

Line Far End Coding Violation (Day)

EC1 Facility Alert T-CV-LFE adTAOMXDS3M3EEC1AlmDFTHLineCV

Line Far End Errored Seconds (Day)

EC1 Facility Alert T-ES-LFE adTAOMXDS3M3EEC1AlmDFTHLineES


EC1 Facility Alert T-SES-LFE adTAOMXDS3M3EEC1AlmDFTHLineSES


EC1 Facility Alert T-UAS-LFE adTAOMXDS3M3EEC1AlmDFTHLineUAS

Line Coding Violations Customer Interface (Qtr)

DS3 Facility Alert T-CVL-C adTAOMXDS3M3EDS3AlmQTHLineCICV

Line Errored Seconds Customer Interface (Qtr)

DS3 Facility Alert T-ESL-C adTAOMXDS3M3EDS3AlmQTHLineCIES

Line Severely Errored Seconds Customer Interface (Qtr)

DS3 Facility Alert T-SESL-C adTAOMXDS3M3EDS3AlmQTHLineCISES

Line Unavailable Seconds Customer Interface (Qtr)

DS3 Facility Alert T-UASL-C adTAOMXDS3M3EDS3AlmQTHLineCIUAS



OPTI-6100 M


A-26

61184500L1-6J

P-BIT Coding Violations Customer Interface Near End (Qtr)

DS3 Facility Alert T-CV-PN-C adTAOMXDS3M3EDS3AlmQTHPathCIPbitCV

P-BIT Errored Seconds Customer Interface Near End (Qtr)

DS3 Facility Alert T-ES-PN-C adTAOMXDS3M3EDS3AlmQTHPathCIPbitES

P-BIT Severely Errored Seconds Customer Interface Near End (Qtr)

DS3 Facility Alert T-SES-PN-C adTAOMXDS3M3EDS3AlmQTHPathCIPbitSES

C-BIT Coding Violations Customer Interface Near End (Qtr)

DS3 Facility Alert T-CV-CN-C adTAOMXDS3M3EDS3AlmQTHPathCICbitCV

C-BIT Errored Seconds Customer Interface Near End (Qtr)

DS3 Facility Alert T-ES-CN-C adTAOMXDS3M3EDS3AlmQTHPathCICbitES

C-BIT Severely Errored Seconds Customer Interface Near End (Qtr)

DS3 Facility Alert T-SES-CN-C adTAOMXDS3M3EDS3AlmQTHPathCICbitSES

Path Unavailable Seconds Customer Interface Near End (Qtr)

DS3 Facility Alert T-UASP-C adTAOMXDS3M3EDS3AlmQTHPathCIUAS

Path Severely Errored Framing Seconds Customer Interface Near End (Qtr)

DS3 Facility Alert T-SEFSP-C adTAOMXDS3M3EDS3AlmQTHPathCISEFS

C-BIT Coding Violations Customer Interface Far End (Qtr)

DS3 Facility Alert T-CV-CF-C adTAOMXDS3M3EDS3AlmQFTHPathCICbitCV

C-BIT Errored Seconds Customer Interface Far End (Qtr)

DS3 Facility Alert T-ES-CF-C adTAOMXDS3M3EDS3AlmQFTHPathCICbitES

C-BIT Severely Errored Seconds Customer Interface Far End (Qtr)

DS3 Facility Alert T-SES-CF-C adTAOMXDS3M3EDS3AlmQFTHPathCICbitSES

C-BIT Unavailable Seconds Customer Interface Far End (Qtr)

DS3 Facility Alert T-UAS-CF-C adTAOMXDS3M3EDS3AlmQFTHPathCIUAS

P-BIT Coding Violations Network Interface Near End (Qtr)

DS3 Facility Alert T-CV-PN-N adTAOMXDS3M3EDS3AlmQTHPathNIPbitCV

P-BIT Errored Seconds Network Interface Near End (Qtr)

DS3 Facility Alert T-ES-PN-N adTAOMXDS3M3EDS3AlmQTHPathNIPbitES




s by Module

61184500L1-6JA

-27

P-BIT Severely Errored Seconds Network Interface Near End (Qtr)

DS3 Facility Alert T-SES-PN-N adTAOMXDS3M3EDS3AlmQTHPathNIPbitSES

C-BIT Coding Violations Network Interface Near End (Qtr)

DS3 Facility Alert T-CV-CN-N adTAOMXDS3M3EDS3AlmQTHPathNICbitCV

C-BIT Errored Seconds Network Interface Near End (Qtr)

DS3 Facility Alert T-ES-CN-N adTAOMXDS3M3EDS3AlmQTHPathNICbitES

C-BIT Severely Errored Seconds Network Interface Near End (Qtr)

DS3 Facility Alert T-SES-CN-N adTAOMXDS3M3EDS3AlmQTHPathNICbitSES

Path Unavailable Seconds Network Interface Near End (Qtr)

DS3 Facility Alert T-UASP-N adTAOMXDS3M3EDS3AlmQTHPathNIUAS

Path Severely Errored Framing Seconds Network Interface Near End (Qtr)

DS3 Facility Alert T-SEFSP-N adTAOMXDS3M3EDS3AlmQTHPathNISEFS

C-BIT Coding Violations Network Interface Far End (Qtr)

DS3 Facility Alert T-CV-CF-N adTAOMXDS3M3EDS3AlmQFTHPathNICbitCV

C-BIT Errored Seconds Network Interface Far End (Qtr)

DS3 Facility Alert T-ES-CF-N adTAOMXDS3M3EDS3AlmQFTHPathNICbitES

C-BIT Severely Errored Seconds Network Interface Far End (Qtr)

DS3 Facility Alert T-SES-CF-N adTAOMXDS3M3EDS3AlmQFTHPathNICbitSES

C-BIT Unavailable Seconds Network Interface Far End (Qtr)

DS3 Facility Alert T-UAS-CF-N adTAOMXDS3M3EDS3AlmQFTHPathNIUAS

Line Coding Violations Customer Interface (Day)

DS3 Facility Alert T-CVL-C adTAOMXDS3M3EDS3AlmDTHLineCICV

Line Errored Seconds Customer Interface (Day)

DS3 Facility Alert T-ESL-C adTAOMXDS3M3EDS3AlmDTHLineCIES

Line Severely Errored Seconds Customer Interface (Day)

DS3 Facility Alert T-SESL-C adTAOMXDS3M3EDS3AlmDTHLineCISES

Line Unavailable Seconds Customer Interface (Day)

DS3 Facility Alert T-UASL-C adTAOMXDS3M3EDS3AlmDTHLineCIUAS



OPTI-6100 M


A-28

61184500L1-6J

P-BIT Coding Violations Customer Interface Near End (Day)

DS3 Facility Alert T-CV-PN-C adTAOMXDS3M3EDS3AlmDTHPathCIPbitCV

P-BIT Errored Seconds Customer Interface Near End (Day)

DS3 Facility Alert T-ES-PN-C adTAOMXDS3M3EDS3AlmDTHPathCIPbitES

P-BIT Severely Errored Seconds Customer Interface Near End (Day)

DS3 Facility Alert T-SES-PN-C adTAOMXDS3M3EDS3AlmDTHPathCIPbitSES

C-BIT Coding Violations Customer Interface Near End (Day)

DS3 Facility Alert T-CV-CN-C adTAOMXDS3M3EDS3AlmDTHPathCICbitCV

C-BIT Errored Seconds Customer Interface Near End (Day)

DS3 Facility Alert T-ES-CN-C adTAOMXDS3M3EDS3AlmDTHPathCICbitES

C-BIT Severely Errored Seconds Customer Interface Near End (Day)

DS3 Facility Alert T-SES-CN-C adTAOMXDS3M3EDS3AlmDTHPathCICbitSES

Path Unavailable Seconds Customer Interface Near End (Day)

DS3 Facility Alert T-UASP-C adTAOMXDS3M3EDS3AlmDTHPathCIUAS

Path Severely Errored Framing Seconds Customer Interface Near End (Day)

DS3 Facility Alert T-SEFSP-C adTAOMXDS3M3EDS3AlmDTHPathCISEFS

C-BIT Coding Violations Customer Interface Far End (Day)

DS3 Facility Alert T-CV-CF-C adTAOMXDS3M3EDS3AlmDFTHPathCICbitCV

C-BIT Errored Seconds Customer Interface Far End (Day)

DS3 Facility Alert T-ES-CF-C adTAOMXDS3M3EDS3AlmDFTHPathCICbitES

C-BIT Severely Errored Seconds Customer Interface Far End (Day)

DS3 Facility Alert T-SES-CF-C adTAOMXDS3M3EDS3AlmDFTHPathCICbitSES

C-BIT Unavailable Seconds Customer Interface Far End (Day)

DS3 Facility Alert T-UAS-CF-C adTAOMXDS3M3EDS3AlmDFTHPathCIUAS

P-BIT Coding Violations Network Interface Near End (Day)

DS3 Facility Alert T-CV-PN-N adTAOMXDS3M3EDS3AlmDTHPathNIPbitCV

P-BIT Errored Seconds Network Interface Near End (Day)

DS3 Facility Alert T-ES-PN-N adTAOMXDS3M3EDS3AlmDTHPathNIPbitES




s by Module

61184500L1-6JA

-29

P-BIT Severely Errored Seconds Network Interface Near End (Day)

DS3 Facility Alert T-SES-PN-N adTAOMXDS3M3EDS3AlmDTHPathNIPbitSES

C-BIT Coding Violations Network Interface Near End (Day)

DS3 Facility Alert T-CV-CN-N adTAOMXDS3M3EDS3AlmDTHPathNICbitCV

C-BIT Errored Seconds Network Interface Near End (Day)

DS3 Facility Alert T-ES-CN-N adTAOMXDS3M3EDS3AlmDTHPathNICbitES

C-BIT Severely Errored Seconds Network Interface Near End (Day)

DS3 Facility Alert T-SES-CN-N adTAOMXDS3M3EDS3AlmDTHPathNICbitSES

Path Unavailable Seconds Network Interface Near End (Day)

DS3 Facility Alert T-UASP-N adTAOMXDS3M3EDS3AlmDTHPathNIUAS

Path Severely Errored Framing Seconds Network Interface Near End (Day)

DS3 Facility Alert T-SEFSP-N adTAOMXDS3M3EDS3AlmDTHPathNISEFS

C-BIT Coding Violations Network Interface Far End (Day)

DS3 Facility Alert T-CV-CF-N adTAOMXDS3M3EDS3AlmDFTHPathNICbitCV

C-BIT Errored Seconds Network Interface Far End (Day)

DS3 Facility Alert T-ES-CF-N adTAOMXDS3M3EDS3AlmDFTHPathNICbitES

C-BIT Severely Errored Seconds Network Interface Far End (Day)

DS3 Facility Alert T-SES-CF-N adTAOMXDS3M3EDS3AlmDFTHPathNICbitSES

C-BIT Unavailable Seconds Network Interface Far End (Day)

DS3 Facility Alert T-UAS-CF-N adTAOMXDS3M3EDS3AlmDFTHPathNIUAS



OPTI-6100 M


A-30

61184500L1-6J

Table A-7. TRAM and TRAM3 Alarms


Loss of Signal DS3 DS3 Facility Major LOS adTAOMXTMUX3DS3AlmLosSet

Loss of Frame DS3 DS3 Facility Major LOF adTAOMXTMUX3DS3LOFSet

Alarm Indication Signal DS3 DS3 Facility Alert AIS adTAOMXTMUX3DS3AISSet

Remote Alarm Indication DS3 DS3 Facility Alert RAI adTAOMXTMUX3DS3RAISet

Line Loopback DS3 Facility Alert LPBKLINE adTAOMXTMUX3almLineLoopbackSetAlm

Local Loopback DS3 Facility Alert LPBKTERM adTAOMXTMUX3almLocalLoopbackSetAlm

Equipment APS ON Card Equip Alert WKSWPR adTAOMXTMUX3OMXAlmAPSEqpOnSet

Equipment Failed Card Equip Minor EQPT-FAIL adTAOMXTMUX3almEQPTSet

Software Mismatch DS3 Equip Alert SW-MM adTAOMXTMUX3OMXSwMisMatchAlmSet

Invalid Slot Card Equip Alert INVD-SLOT adTAOMXTMUX3OMXInvalidSlotAlmSet

Redundancy Provisioning DS3 Facility Alert REDUN-PROV adTAOMXTMUX3OMXRedundancyProvErrAlmSet

Maintenance Alert Notification Card Equip Alert MAN adTAOMXTMUX3OMXMANAlmSet


DS3 Facility Alert T-CVL adTAOMXTMUX3PMQTHAlmLCV


DS3 Facility Alert T-ESL adTAOMXTMUX3PMQTHAlmLES


DS3 Facility Alert T-SESL adTAOMXTMUX3PMQTHAlmLSES


DS3 Facility Alert T-UASL adTAOMXTMUX3PMQTHAlmLUAS

Path Coding Violation (Qtr) DS3 Facility Alert T-CVP adTAOMXTMUX3PMQTHAlmPCV

Path Errored Seconds (Qtr) DS3 Facility Alert T-ESP adTAOMXTMUX3PMQTHAlmPES

Path Severely Errored Seconds (Qtr)

DS3 Facility Alert T-SESP adTAOMXTMUX3PMQTHAlmPSES

Path Unavailable Seconds (Qtr) DS3 Facility Alert T-UASP adTAOMXTMUX3PMQTHAlmPUAS


s by Module

61184500L1-6JA

-31

CBit Near End Coding Violation (Qtr)

DS3 Facility Alert T-CVCP-P adTAOMXTMUX3PMQTHAlmCCV

CBit Near End Errored Seconds (Qtr)

DS3 Facility Alert T-ESCP-P adTAOMXTMUX3PMQTHAlmCES

CBit Near End Severely Errored Seconds (Qtr)

DS3 Facility Alert T-SESCP-P adTAOMXTMUX3PMQTHAlmCSES

CBit Near End Unavailable Seconds (Qtr)

DS3 Facility Alert T-UASCP-P adTAOMXTMUX3PMQTHAlmCUAS

CBit Far End Coding Violation (Qtr)

DS3 Facility Alert T-CVCP-PFE adTAOMXTMUX3PMQFarEndTHAlmCCV

CBit Far End Errored Seconds (Qtr)

DS3 Facility Alert T-ESCP-PFE adTAOMXTMUX3PMQFarEndTHAlmCES

CBit Far End Severely Errored Seconds (Qtr)

DS3 Facility Alert T-SESCP-PFE adTAOMXTMUX3PMQFarEndTHAlmCSES

CBit Far End Unavailable Seconds (Qtr)

DS3 Facility Alert T-UASCP-PFE adTAOMXTMUX3PMQFarEndTHAlmCUAS


DS3 Facility Alert T-CVL adTAOMXTMUX3PMDTHAlmLCV


DS3 Facility Alert T-ESL adTAOMXTMUX3PMDTHAlmLES


DS3 Facility Alert T-SESL adTAOMXTMUX3PMDTHAlmLSES


DS3 Facility Alert T-UASL adTAOMXTMUX3PMDTHAlmLUAS

Path Coding Violation (Day) DS3 Facility Alert T-CVP adTAOMXTMUX3PMDTHAlmPCV

Path Errored Seconds (Day) DS3 Facility Alert T-ESP adTAOMXTMUX3PMDTHAlmPES

Path Severely Errored Seconds (Day)

DS3 Facility Alert T-SESP adTAOMXTMUX3PMDTHAlmPSES

Table A-7. TRAM and TRAM3 Alarms (Continued)


OPTI-6100 M


A-32

61184500L1-6J

Path Unavailable Seconds (Day) DS3 Facility Alert T-UASP adTAOMXTMUX3PMDTHAlmPUAS

CBit Near End Coding Violation (Day)

DS3 Facility Alert T-CVCP-P adTAOMXTMUX3PMDTHAlmCCV

CBit Near End Errored Seconds (Day)

DS3 Facility Alert T-ESCP-P adTAOMXTMUX3PMDTHAlmCES

CBit Near End Severely Errored Seconds (Day)

DS3 Facility Alert T-SESCP-P adTAOMXTMUX3PMDTHAlmCSES

CBit Near End Unavailable Seconds (Day)

DS3 Facility Alert T-UASCP-P adTAOMXTMUX3PMDTHAlmCUAS

CBit Far End Coding Violation (Day)

DS3 Facility Alert T-CVCP-PFE adTAOMXTMUX3PMDFarEndTHAlmCCV

CBit Far End Errored Seconds (Day)

DS3 Facility Alert T-ESCP-PFE adTAOMXTMUX3PMDFarEndTHAlmCES

CBit Far End Severely Errored Seconds (Day)

DS3 Facility Alert T-SESCP-PFE adTAOMXTMUX3PMDFarEndTHAlmCSES

CBit Far End Unavailable Seconds (Day)

DS3 Facility Alert T-UASCP-PFE adTAOMXTMUX3PMDFarEndTHAlmCUAS

Table A-7. TRAM and TRAM3 Alarms (Continued)



s by Module

61184500L1-6JA

-33

Table A-8. Ethernet Module Alarms


ETH Link State Ethernet Facility Major LOS adTAOMXETHLinkStateSetAlm

GFP Sync Lost Ethernet Facility Major LOF adTAOMXETHGFPStateSetAlm

PPP Sync Lost Ethernet Facility Major LOF adTAOMXETHPPPStateSetAlm

X86 Sync Lost Ethernet Facility Major LOF adTAOMXETHX86StateSetAlm

Local Loopback Ethernet Facility Alert LPBK-LC adTAOMXETHLocalLoopbackStateSetAlm

Maintenance Alert Notification Card Equip Alert MAN adTAOMXETHMANAlmSet

Table A-9. Gigabit Ethernet Module Alarms


ETH Link State Ethernet Facility Major LOS adTAOMXETHLinkStateSetAlm

GFP Sync Lost Ethernet Facility Major LOF adTAOMXETHGFPStateSetAlm

PPP Sync Lost Ethernet Facility Major LOF adTAOMXETHPPPStateSetAlm

Local Loopback Ethernet Facility Alert LPBK-LC adTAOMXETHLocalLoopbackStateSetAlm

Maintenance Alert Notification Card Equip Alert MAN adTAOMXETHMANAlmSet

OPTI-6100 M


A-34

61184500L1-6J

Table A-10. OC-3/12 Tributary Module Alarms


Loss of Signal OC3/12 Facility Critical/Minor LOS adgenOXTMLosAlm

Loss of Frame OC3/12 Facility Critical/Minor LOF adgenOXTMLofAlm

Signal Degrade OC3/12 Facility Critical/Minor SD adgenOXTMSdAlm

Signal Fail OC3/12 Facility Critical/Minor SF adgenOXTMSfAlm

Remote Failure Indication OC3/12 Facility Alert RFI-L adgenOXTMRfilAlm

Alarm Indication Signal (Line) OC3/12 Facility Alert AIS-L adgenOXTMAislAlm

Alarm Indication Signal (Path) STS-1 Facility Alert AIS-P adgenOXTMAispAlm

Loss of Pointer (Path) STS-1 Facility Critical/Minor LOP-P adgenOXTMLopAlm

Unequipped (Path) STS-1 Facility Critical/Minor UNEQ-P adgenOXTMUneqpAlm

Signal Label Mismatch STS-1 Facility Critical/Minor SLMF adgenOXTMSlmAlm

Path Trace Mismatch STS-1 Facility Alert TIM-P adgenOXTMTimpAlm

Remote Failure Indication STS-1 Facility Alert RFI-P adgenOXTMRfipAlm





Signal Fail (VT) VT1.5 Facility Major/Minor SF-V adgenVtSfAlm

Signal Degrade (VT) VT1.5 Facility Major/Minor SD-V adgenVtSdAlm

Line Loopback OC3/12 Facility Alert LPBKLINE adgenOXTMLineLPBKAlm

Local Loopback OC3/12 Facility Alert LPBKTERM adgenOXTMLocalLPBKAlm

Protection Switch Byte Failure Card Equip NA Not Supported adgenOXTMApsPsbfAlm

Channel Mismatch Failure Card Equip NA Not Supported adgenOXTMApsCmfAlm

APS Mode Mismatch Failure Card Equip NA Not Supported adgenOXTMApsMmfAlm


s by Module

61184500L1-6JA

-35

Far-End Protection line Failure Card Equip NA Not Supported adgenOXTMApsFEPlfAlm

Equipment Switch ON Card Equip Alert WKSWPR adgenOXTMApsEqptOnAlm

Path Switch ON OC3 Facility Alert WKSWPR adgenOXTMApsLineOnAlm

Equipment Service Affected Alarm Card Equip Critical/Minor EQPT adgenOXTMEqptAlm

Software Version Mismatch Card Equip Alert Not Supported adgenOXTMSWMMAlm

APS Mismatch Card Equip Alert Not Supported adgenOXTMAPSMMAlm

Maintenance Alert Notification Card Equip Alert MAN adgenOXTMMANAlm

Section Coding Violation (Qtr) OC3/12 Facility Alert T-CVS adgenOXTMQtrSecCvAlm

Section Errored Seconds (Qtr) OC3/12 Facility Alert T-ESS adgenOXTMQtrSecEsAlm

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


OC3/12 Facility Alert T-SESL adgenOXTMQtrLineSesAlm

Line Near End Unavailable Seconds (Qtr) OC3/12 Facility Alert T-UASL adgenOXTMQtrLineUasAlm

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


OC3/12 Facility Alert T-SES-LFE adgenOXTMQtrFELineSesAlm

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

Table A-10. OC-3/12 Tributary Module Alarms (Continued)


OPTI-6100 M


A-36

61184500L1-6J


STS-1 Facility Alert T-SESP adgenOXTMQtrPathSesAlm

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


STS-1 Facility Alert T-SES-PFE adgenOXTMQtrFEPathSesAlm

Path Far End Unavailable Seconds (Qtr) STS-1 Facility Alert T-UAS-PFE adgenOXTMQtrFEPathUasAlm

Section Coding Violation (Day) OC3 Facility Alert T-CVS adgenOXTMDaySecCvAlm

Section Errored Seconds (Day) OC3/12 Facility Alert T-ESS adgenOXTMDaySecEsAlm

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


OC3/12 Facility Alert T-SESL adgenOXTMDayLineSesAlm

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


OC3/12 Facility Alert T-SES-LFE adgenOXTMDayFELineSesAlm

Line Far End Unavailable Seconds (Day) OC3/12 Facility Alert T-UAS-LFE adgenOXTMDayFELineUasAlm

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




s by Module

61184500L1-6JA

-37


STS-1 Facility Alert T-SESP adgenOXTMDayPathSesAlm

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


STS-1 Facility Alert T-SES-PFE adgenOXTMDayFEPathSesAlm

Path Far End Unavailable Seconds (Day) STS-1 Facility Alert T-UAS-PFE adgenOXTMDayFEPathUasAlm

Lock out of Protection OC3/12 Facility NA LOCKOUTOFPR adgenLinePsLckAlm

Force Switch to Working OC3/12 Facility NA FRCDWKSWBK adgenLineFSTWAlm

Force Switch to Protection OC3/12 Facility NA FRCDWKSWPR adgenLineFSTPAlm

Manual Switch to Working OC3/12 Facility NA MANWKSWBK adgenLineMSTWAlm

Manual Switch to Protection OC3/12 Facility NA MANWKSWPR adgenLineMSTPAlm

Switch to Working OC3/12 Facility NA WKSWPR adgenLineWSTPAlm

Switch to Protection OC3/12 Facility NA WKSWBK adgenLineWSBAlm












OPTI-6100 M


A-38

61184500L1-6J






Lock out of Protection VT1.5 Facility NA LOCKOUTOFPR adgenVtPsLckAlm

Force Switch to Working VT1.5 Facility NA FRCDWKSWBK adgenVtFSTWAlm

Force Switch to Protection VT1.5 Facility NA FRCDWKSWPR adgenVtFSTPAlm

Manual Switch to Working VT1.5 Facility NA MANWKSWBK adgenVtMSTWAlm

Manual Switch to Protection VT1.5 Facility NA MANWKSWPR adgenVtMSTPAlm

Switch to Working VT1.5 Facility NA WKSWPR adgenVtWSTPAlm

Switch to Protection VT1.5 Facility NA WKSWBK adgenVtWSBAlm



61184500L1-6J B-1

Appendix BService States Glossary

SUFFIXESAny entity that is protected and in an IS state can be embellished with the following suffixes:

IS ACT (In Service, ACTive)The entity is in the Active state and is carrying traffic.

IS ACT, PSI (In Service, ACTive, Protection Switch Inhibited)The entity is in the Active state and exists on the working module. Protection switching is locked out so that no switch to the protection module is allowed.

IS ACT, PRI (In Service, ACTive, Protection Release Inhibited)The entity is in the Active state and exists on the protect module. Release of protection switching is locked out so that no switch back to the working module is allowed.

IS STBY (In Service, STandBY)The entity is in the Standby state.

IS STBY, PSI (In Service, STandBY, Protection Switch Inhibited)The entity is in the Standby state and exists on the protect module. Protection switching is locked out so that no switch to the protection module is allowed.

IS STBY, PRI (In Service, STandBY, Protection Release Inhibited)The entity is in the Standby state and exists on the working module. Release of protection switching is locked out so that no switch back to the working module is allowed.Any facility state can be embellished with the loopback suffix:

LPBK (LooPBacK)The facility is in loopback.


B-2 61184500L1-6J

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.

OOS-AUMA UEQ (Out Of Service, AUtonomous MAintenance, UnEQuipped)No module is plugged into the slot but a record for the equipment exists in the database and is provisioned with an OOS service state.

OOS-AU UEQ, AINS (Out Of Service, AUtonomous, UnEQuipped, Automatic IN-Service)No module is plugged into the slot but a record for the equipment exists in the database. The entity is provisioned IS and is therefore in an Automatic In Service state.

OOS-MA UAS (Out Of Service, MAintenance, UnASsigned)A module is plugged into the slot but no record for the equipment exists in the database.

OOS-AUMA MEA (Out Of Service, AUtonomous MAintenance, Mismatched Equipment Alarm)A module is plugged into the slot and a record for the equipment exists in the database, but the module type does not match the record in the database. The entity record is provisioned OOS.

OOS-AU AINS, MEA (Out Of Service, AUtonomous, Automatic IN-Service, Mismatched Equipment Alarm)A module is plugged into the slot and a record for the equipment exists in the database, but the module type does not match the record in the database. The entity record is provisioned IS and is therefore in an Automatic In Service state.

OOS-AUMA FLT (Out Of Service, AUtonomous MAintenance, FauLT)A module is plugged into the slot and a matching record exists in the database. The module is set to OOS, but is in a fault condition.

OOS-AU FLT (Out Of Service, AUtonomous, FauLT)A module is plugged into the slot and a matching record exists in the database. The module is set to IS, but is in a fault condition.

OOS-MA (Out Of Service, MAintenance)A module is plugged into the slot and a matching record exists in the database. The module is set to OOS.

IS (In Service)A module is plugged into the slot and a matching record exists in the database. The module is set to IS.

Appendix B, Service States Glossary - Service States

61184500L1-6J B-3

Facility States

OOS-MA UAS (Out Of Service, MAintenance, UnASsigned)No record for the facility exists in the database.

OOS-AUMA SGEO (Out Of Service, AUtonomous MAintenance, SupportinG Entity Outage)A record for the facility exists in the database and is set to OOS, but the equipment supporting the facility is not IS.

OOS-AU SGEO (Out Of Service, AUtonomous, SupportinG Entity Outage)A record for the facility exists in the database and is set to IS, but the equipment supporting the facility is not IS.

OOS-AUMA FLT (Out Of Service, AUtonomous MAintenance, FauLT)A record for the facility exists in the database and is set to OOS, but the facility is in a fault condition.

OOS-AU FLT (Out Of Service, AUtonomous, FauLT)A record for the facility exists in the database and is set to IS, but the facility is in a fault condition.

OOS-MA (Out Of Service, MAintenance)A record for the facility exists in the database but is set to OOS. The supporting equipment is IS.

OOS-AU FAF, AINS (Out Of Service, AUtonomous, FauLT, Automatic IN-Service)A record for the facility exists in the database and is set to IS. The facility has been placed into an Auto-In Service state awaiting the first occurrence of a valid input signal on the facility.

IS (In Service)A record for the facility exists in the database and is set to IS.


B-4 61184500L1-6J

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.

OOS-MA SDEA (Out Of Service, MAintenance, SupporteD Entity Absent)A record for the path exists in the database and is set to OOS. No cross-connect has been made to it.

OOS-AUMA SDEA (Out Of Service, AUtonomous MAintenance, SupporteD Entity Absent)A record for the path exists in the database and is set to IS. No cross-connect has been made to it.

OOS-AUMA SGEO (Out Of Service, AUtonomous MAintenance, SupportinG Entity Outage)A record for the path exists in the database but the supporting facility is not IS. No cross-connect has been made to the path.

OOS-MA SGEO (Out Of Service, MAintenance, SupportinG Entity Outage)A record for the path exists in the database and is set to OOS, but the supporting facility is not IS. A cross-connect has been made to the path.

OOS-AU SGEO (Out Of Service, AUtonomous, SupportinG Entity Outage)A record for the path exists in the database and is set to IS, but the supporting facility is not IS. A cross-connect has been made to the path.

OOS-MA FLT (Out Of Service, MAintenance, FauLT)A record for the path exists in the database and is set to OOS. A cross-connect has been made to it, but it is in a fault condition.

OOS-AU FLT (Out Of Service, AUtonomous, FauLT)A record for the path exists in the database and is set to IS. A cross-connect has been made to it, but it is in a fault condition.

OOS-MA (Out Of Service, MAintenance)A record for the path exists in the database and is set to OOS. A cross-connect has been made to it.

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.

Appendix B, Service States Glossary - Service States

61184500L1-6J B-5

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.

OOS-MA SDEA (Out Of Service, MAintenance, SupporteD Entity Absent)A record for the VT exists in the database and is set to OOS. No cross-connect has been made to it.

OOS-AUMA SDEA (Out Of Service, AUtonomous MAintenance, SupporteD Entity Absent)A record for the VT exists in the database and is set to IS. No cross-connect has been made to it.

OOS-AUMA SGEO (Out Of Service, AUtonomous MAintenance, SupportinG Entity Outage)A record for the VT exists in the database but the supporting path is not IS. No cross-connect has been made to the VT.

OOS-MA SGEO (Out Of Service, MAintenance, SupportinG Entity Outage)A record for the VT exists in the database and is set to OOS, but the supporting path is not IS. A cross-connect has been made to the VT.

OOS-AU SGEO (Out Of Service, AUtonomous, SupportinG Entity Outage)A record for the VT exists in the database and is set to IS, but the supporting path is not IS. A cross-connect has been made to the VT.

OOS-MA FLT (Out Of Service, MAintenance, FauLT)A record for the VT exists in the database and is set to OOS. A cross-connect has been made to it, but it is in a fault condition.

OOS-AU FLT (Out Of Service, AUtonomous, FauLT)A record for the VT exists in the database and is set to IS. A cross-connect has been made to it, but it is in a fault condition.

OOS-MA (Out Of Service, MAintenance)A record for the VT exists in the database and is set to OOS. A cross-connect has been made to it.

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.


B-6 61184500L1-6J

DCC States

OOS-MA UAS (Out Of Service, MAintenance, UnASsigned)No record for the DCC Channel exists in the database.

OOS-AUMA SGEO (Out Of Service, AUtonomous MAintenance, SupportinG Entity Outage)A record for the DCC channel exists in the database and is set to OOS, but the supporting facility is not IS.

OOS-AU SGEO (Out Of Service, AUtonomous, SupportinG Entity Outage)A record for the DCC channel exists in the database and is set to IS, but the supporting facility is not IS.

OOS-AUMA FLT (Out Of Service, AUtonomous MAintenance, FauLT)A record for the DCC channel exists in the database and is set to OOS, but it is in a fault condition.

OOS-AU FLT (Out Of Service, AUtonomous, FauLT)A record for the DCC channel exists in the database and is set to IS, but it is in a fault condition.

OOS-MA (Out Of Service, MAintenance)A record for the DCC channel exists in the database and is set to OOS.

IS (In Service)A record for the DCC channel exists in the database and is set to IS.

61184500L1-6J C-1

Appendix CAccess Privileges

SUMMARY OF ACCESS PRIVILEGESTable C-1 is a complete listing of access privileges for the ADMIN, READ\WRITE and READONLY user account types.

Table C-1. OPTI-6100 Access Privileges

Menu Items ADMIN READWRITE READONLY

Main Menu

System Controller Submenu Submenu Submenu

HS 1 View/Change View/Change View/Change

HS 2 View/Change View/Change View/Change

MS Modules View/Change View/Change View/Change

System Alarms Submenu Submenu Submenu

Auxiliary Shelf Access View/Change View/Change View/Change

System Inventory View View View

Remote Menu Access

Logoff View/Change View/Change View/Change

System Controller

Configuration Submenu Submenu Submenu

Provisioning Submenu Submenu Submenu

Status Submenu Submenu Submenu

Test Submenu Submenu N/A

Controller Report View

Scratch Pad View/Change


C-2 61184500L1-6J

System Controller/Configuration

Unit Name View View View

CLEI Code View View View

Part Number View View View

Serial Number View View View

Product Revision View View View

Hardware Revision View View View

Software Revision View View View

Boot Room Version View View View

MAC Address View View View

System Controller/Provisioning

General Submenu Submenu Submenu

HS/MS Module Submenu Submenu Submenu

Network Management Submenu Submenu Submenu

SNMP Submenu Submenu Submenu

TL1 Submenu Submenu Submenu

Security Administration Submenu N/A N/A

System Controller/Provisioning/General

Management Ports Submenu Submenu Submenu

Date View/Change View View

Time View/Change View View

Auto-Logoff View/Change View View

Logoff Craft Port When DTR Lost View/Change View View

Restore Default Provisioning View/Change N/A N/A

Security Administration Submenu N/A N/A

Change (Current Account) Password View/Change View/Change N/A

Table C-1. OPTI-6100 Access Privileges (Continued)


Appendix C, Access Privileges - Summary of Access Privileges

61184500L1-6J C-3

System Controller/Provisioning/General/Management Ports

Admin Port Submenu Submenu Submenu

Craft & Admin Port Baud Rate View/Change View/Change View

Interbank Comm. Mode View/Change View View

Network Management Port Mode View/Change View View

System Controller/Provisioning/General/Management Ports/Admin Port

Craft & Admin Port Baud Rate View/Change View/Change View

Admin Port Communications View/Change View View

Use RTS/CTS (Hardware Handshaking View/Change View View

Terminate Session Upon Carrier Loss View/Change View View

De-assert/Drop DTR on Logout View/Change View View

System Controller/Provisioning/HS-MS Module

Write Module Provisioning View/Change View/Change N/A

HS Module Auto-Provisioning View/Change View View

MS Module Auto-Provisioning View/Change View View

System Controller/Provisioning/Network Management

IP Network Provisioning Submenu Submenu Submenu

SONET SDCC Provisioning Submenu Submenu Submenu

Mount Location View/Change

Get Net Prov From HS Module View/Change View View

Remote File I/O Method View/Change

System Controller/Provisioning/Network Management/IP Network Provisioning

IP Network Interfaces Submenu Submenu Submenu

IP Route Table Submenu Submenu Submenu

IP Services and Ports Submenu Submenu Submenu




C-4 61184500L1-6J

System Controller/Provisioning/Network Management/IP Network Provisioning/IP Network Interfaces

Ethernet Interface Submenu Submenu Submenu

OSI Tunnel Interface Submenu Submenu Submenu

PPP/DCC0 Interface Submenu Submenu Submenu

Default Route Interface View/Change

IP Forwarding View/Change

System Controller/Provisioning/Network Management/IP Network Provisioning/IP Network Interfaces/Ethernet Interface

Interface View/Change View View

IP Address View/Change View View

Subnet Mask View/Change View View

Gateway View/Change View View

Link View View View

System Controller/Provisioning/Network Management/IP Network Provisioning/IP Network Interfaces/OSI Tunnel Interface





Link View View View

System Controller/Provisioning/Network Management/IP Network Provisioning/IP Network Interfaces/PPP/DCC0 Interface





DCC Provisioning Submenu

DCC Interface View/Chance

Peer Address View/Change

Link View View View




61184500L1-6J C-5

System Controller/Provisioning/Network Management/SONET SDCC Provisioning

Upper Layers Provisioning Submenu

DCC Interface Provisioning Submenu

System Controller/Provisioning/Network Management/SONET SDCC Provisioning/Upper Layers Provisioning

NSAP Area Address View/Change

System ID View

System Controller/Provisioning/SNMP

Trap Host 1 IP Submenu Submenu Submenu




ifIndex Method View N/A N/A

SCM Traps View/Change View View

System Name View/Change View View

System Location View/Change View View

System Contact View/Change View View

Read Community View/Change N/A N/A

Write Community View/Change N/A N/A

NonVol CardStat View/Change

System Controller/Provisioning/SNMP/Trap Host 1

Trap Host 1 IP View/Change View View

Trap Host 1 Method View/Change View View

Trap Host 1 Confirmation View/Change View View

Trap Host 1 Initial Time-Out View/Change View View

Trap Host 1 Retry Limit View/Change View View

Trap Host 1 Status View/Change View View

Trap Host 1 Seq Num Requested View View View

Trap Host 1 Seq Num Confirmed View View View

Trap Host 1 Cache View View View




C-6 61184500L1-6J


































61184500L1-6J C-7

System Controller/Provisioning/TL1

Unit Number (Expansion Mode only) View/Change View View

Client Shelf Management View/Change View View

Target ID (TID) (Intelligent NE Mode only) View/Change View View

TL1 Telnet Port View/Change View View

TL1 Raw – TCP Port View/Change View View

Exchange TL1 Ports View/Change View View

TL1 Echo View/Change N/A N/A

TL1 Log View

System Controller/Provisioning/System Administration (ADMIN Only)*

Software Update* Submenu N/A N/A

Security Administration* Submenu N/A N/A

System Configuration Archive (SCA)* Submenu N/A N/A

System Event Log View/Change N/A N/A

Auto Upgrade Status View/Change N/A N/A

System Controller/Status

Shelf Status Submenu

DCC Interface Status Submenu

System Controller/Test

Test Alarm Relays View/Change View/Change N/A

Self Test And Restart View/Change View/Change N/A

System Controller/Controller Report

Master Alarm Log Report View

System Event Log Report View

Configuration/Provisioning Report View

Status Report View

ALL Reports View




C-8 61184500L1-6J

System Alarms

Shelf Alarm Status View View View

Alarm Logs View View View

User-Definable Alarms Submenu Submenu Submenu

Alarm Chronology View/Change View/Change N/A

System Alarms/User-Definable Alarms

Environmental Alarms Submenu Submenu N/A

MS Module Removed Level View/Change View/Change N/A

HS Removed Level View/Change View/Change N/A

System Alarms/User-Definable Alarms/Environmental Alarms

Environmental Alarm Summary Submenu

Auxiliary #1 Input View/Change View N/A



Auxiliary Fan Alarms Submenu

Power Bus A Input View/Change View N/A

Power Bus B Input View/Change View N/A

Equipment ID View/Change View/Change N/A

System Alarms/User-Definable Alarms/Environmental Alarms/Environmental Alarm Summary

Aux #1 Input View/Change



Power Bus A View/Change

Power Bus B View/Change

Single Fan/Pwr View/Change

Multi Fan View/Change

Aux Fan Alarm 1-16 View/Change




61184500L1-6J C-9

System Alarms/User-Definable Alarms/Environmental Alarms/Environmental Alarm Summary/Aux #1-3 Input

Aux #1-3 Input Description View/Change

Aux #1-3 Input Level View/Change

Aux #1-3 Input AID Index View/Change

Aux #1-3 Input Condition Code View/Change

System Alarms/User-Definable Alarms/Environmental Alarms/Environmental Alarm Summary/Power Bus A-B

Power Bus A-B Level View/Change

Power Bus A-B AID Index View/Change

Power Bus A-B Condition Code View/Change

System Alarms/User-Definable Alarms/Environmental Alarms/Environmental Alarm Summary/Single Fan Pwr

Single Fan Input Description View/Change

Single Fan Input Level View/Change

Single Fan Input AID Index View/Change

Single Fan Input Condition Code View/Change

System Alarms/User-Definable Alarms/Environmental Alarms/Environmental Alarm Summary/Multi Fan

Multiple Fan Input Description View/Change

Multiple Fan Input Level View/Change

Multiple Fan Input AID Index View/Change

Multiple Fan Input Condition Code View/Change

System Alarms/User-Definable Alarms/Environmental Alarms/Auxiliary Fan Alarms

Auxiliary Fan Mode View/Change

Auxiliary Fan Alarm Inputs Submenu

System Alarms/User-Definable Alarms/Environmental Alarms/Auxiliary Fan Alarms/Auxiliary Fan Alarm Inputs

Single Fan Pwr View/Change

Multi Fan View Change




C-10 61184500L1-6J

* = All System Controller\Provisioning\System Administration submenus require Admin-level privileges.

System Alarms/User-Definable Alarms/Environmental Alarms/Auxiliary Fan Alarms/Auxiliary Fan Alarm Inputs/Single Fan Pwr

Single Fan Input Description View/Change

Single Fan Input Level View/Change

Single Fan Input AID Index View/Change

Single Fan Input Condition Code View/Change

System Alarms/User-Definable Alarms/Environmental Alarms/Auxiliary Fan Alarms/Auxiliary Fan Alarm Inputs/Multi Fan

Multiple Fan Input Description View/Change

Multiple Fan Input Level View/Change

Multiple Fan Input AID Index View/Change

Multiple Fan Input Condition Code View/Change



61184500L1-6J D-1

Appendix DWarranty

WARRANTY AND CUSTOMER SERVICEADTRAN will replace or repair this product within the warranty period if it does not meet its published specifications or fails while in service. Warranty information can be found at www.adtran.com/warranty.

Refer to the following subsections for sales, support, Customer and Product Service (CAPS) requests, or further information.

ADTRAN SalesPricing/Availability:

800-827-0807

ADTRAN Technical SupportPre-Sales Applications/Post-Sales Technical Assistance:

800-726-8663

Standard hours: Monday - Friday, 7 a.m. - 7 p.m. CSTEmergency hours: 7 days/week, 24 hours/day

ADTRAN Repair/CAPSReturn for Repair/Upgrade:

(256) 963-8722

Repair and Return AddressContact CAPS prior to returning equipment to ADTRAN.

ADTRAN, Inc.CAPS Department901 Explorer BoulevardHuntsville, Alabama 35806-2807

http://www.adtran.com/warranty

Carrier Networks Division901 Explorer Blvd.

Huntsville, AL 35806

®

opti-6100 provision -61184500L1-6J

Documents

Transcript of opti-6100 provision -61184500L1-6J