ADTRAN T200 FNID Specifications download pdf (Page 28)

A-4 61184002L3-5B

2. DCC Operation

2.1 Turnup

2.1.1 Plug in the first OCM.

2.1.1.1 No provisioning data exists in

the serial EPROM, so it must be

entered via the craft interface

located on the front of the card.

2.1.1.2 If this OPTI-3 is to be used at

the central office side, change

the DCC Side parameter to

“Network”. Changes are not

needed if this OPTI-3 is to be

used at the remote side..

2.1.1.3 If this OPTI-3 is to be connected

to another Vender’s equipment,

determine the NSAP area

address by polling that

equipment.

2.1.1.4 If the OPTI-3 is to be connected

to another OPTI-3, in a

back-to-back arrangement, use

the default NSAP address.

2.1.1.5 Define a unique System ID that

will identify the OPTI-3 as an

NE.

2.1.1.6 Define a unique CLLI code that

will identify the OPTI-3 as an

NE.

2.1.1.7 Now enter the NSAP area

address, system ID, and CLLI

code. The OSI stack will be

started after all three

provisioning values are entered.

2.1.2 Plug in the second OCM.

2.1.2.1 No provisioning data exists in

the serial EPROM and the mate

OCM is provisioned and

operational.

2.1.2.2 All provisioning will be

downloaded from the mate.

2.1.2.3 The OSI stack will be started

after the provisioning has been

received from the mate OPTI-3..

2.2 Card Initialization

2.2.1 When the NSAP Area Address, the

System ID, and the CLLI code are

provisioned, a reset of the software, as

in the case of a program download, will

start the OSI stack after initialization.

2.3 Changing the NSAP Address

2.3.1 The NSAP area address or System ID

can be changed at any time.

2.3.2 Changes made before the OSI stack is

started are non-service-affecting and can

be done whenever desired.

2.3.3 Changes made after the OSI stack has

started is service-affecting and will

require the software to be rebooted in

order for the new address to take effect.

2.3.4 For the service-affecting case, an alert

will appear on the menu indicating that

the card must be rebooted for the

address change to take effect.

2.3.5 Special care must be taken when typing

in the area address. DCC

communication will be adversely

affected if the area address is incorrect.

2.3.6 The following steps illustrate how to

change the NSAP address once the OSI

stack has been started.

Step 1. Move all of the traffic to one of

the OCMs.

Step 2. Change the area address or

system ID on the “offline”

OCM.

Step 3. Select the option to reboot the

software after an address change

on the “offline” OCM.

Step 4. Move all of the traffic to the

“offline” OPTI-3.

Step 5. Repeat steps 2-3 to change the

address on the other OCM.

3. State Information (status)

3.1 State information can only be retrieved from

the Craft Interface located on the front of the

OCM card. It cannot be retrieved remotely

via SNMP or TL1.

3.1.1 State information is maintained on the

main status screen.

3.1.2 State definitions:

3.1.2.1 Link Down – this state indicates

that there is no communication

across the DCC.

3.1.2.2 Link Up – this state indicates

that there is communication

across the DCC.

1 2 ... 23 24 25 26 27 28 29 30 31 32 33 ... 75 76

Comments to this Manuals

No comments