Use the WaveStar^® CIT to log in to one of the terminating nodes, if not already performed.

Reference:

Procedure 14-2: Connect Personal Computer (PC) and establish WaveStar^® CIT session

On the System View menu, select Administration → OSI Routing Map and/or Administration → OSI Neighbor Map to retrieve a node-to-node listing of every node in the network.

Important!

If a drawing of the network is not provided with the work instructions, it is recommended that you draw a simple diagram of the network (indicating node-to-node connections) and list each node's TID.

This command may take several minutes to complete depending on the size of the network.

Result:

The OSI Routing Map or OSI Neighbor Map window opens.

Verify that the system configuration is the same as specified on your work instructions.

From your work instructions, determine the circuit pack, port, and cross-connections to be made at each node associated with the service to be established.

NOTICE Service-disruption hazard

If the Ethernet circuit pack is already providing service, changing tagging mode will take down any existing service. The existing tagging mode cannot be changed without removing all existing cross-connections and virtual switch provisioning.

CONFIGURE TAGGING MODE

Determine the existing tagging mode and parameters for the circuit pack being provisioned. Use the TL1 rtrv-eqpt command or select View → Equipment from the System View menu, select the CP, then click Select. Note the VLAN Tagging Mode, and other parameters.

Select one of the following:

If you are going to change the VLAN Tagging Mode that presently exists AND a virtual switch ID already exists, you must delete the existing virtual switch ID before changing the tagging mode.

Determine if a virtual switch ID has already been assigned to the LAN/WAN ports used for this service. Use the TL1 rtrv-vrtsw command or select the View → Data → Virtual Switch command from the System View menu, select the GbE circuit pack being provisioned, then click Select. Note if a virtual switch ID has been assigned.

If required, use the TL1 dlt-vrtsw command or select the Configuration → Data → Delete Virtual Switch command from the System View menu, highlight the circuit pack being provisioned, then click Select. Highlight the VRTSW ID being deleted, then click Apply.

Read the warning message, then click Yes to execute the command. Click Close to exit.

Use the TL1 ed-eqpt command or select the Configuration → Equipment command from the System View menu. Select the circuit pack being provisioned, then click Select.

Verify/Select NOTAG in the Select VLAN Tagging Mode box.

Verify/Enter other parameter values (for example, Burst Size, Credit Interval[LNW67/68], Ethernet Cross Connect Mode [LNW70/LNW170] and Port Configuration [LNW63/64/70]), and Line Rate (LNW87) as required, then click Apply. Read the warning message, then click OK to make your changes. Click Close to exit.

Reference:

Procedure 11-10: Provision Ethernet circuit pack parameters

ESTABLISH SONET CROSS-CONNECTIONS

Determine the necessary cross-connections to be made at each terminating and non terminating node in the network.

Note that full rate Gigabit service requires 21 STS-1 or equivalent cross-connections.

One at a time at each node in the network, use the TL1 ent-crs-sts1 command to provision the cross-connections. Or, select Configuration → Cross-Connections from the System View menu to start the Cross-Connection Wizard. Use the Cross-Connection Wizard at each of the nodes in the network to provision the cross-connections.

Important!

Note that cross-connections at the terminating nodes are add/drop and cross-connections at the non terminating nodes are pass-through.

For the LNW70/LNW170/LNW63/LNW64/LNW87 circuit packs, a VCG may have a bandwidth up to 21 STS1s. Also, there is no pairing of VCGs.

Reference:

Procedure 11-15: Make cross-connections for Ethernet service

From the System View menu, select View → Cross-Connections at each node to verify that the proper connections have been made.

Important!

For LNW63/64/70/74/87 circuit packs, each tributary cross-connected to a VCG must be Enabled before it becomes an active member of the VCG. Select View → Data → Ethernet/Data/VCG Port to verify that VCG Membership has been Enabled in both Input and Ouput Direction.

Use the TL1 ed-vcgtrib command to enable tributaries, or from the System View menu at each node, select Configuration → Equipment. Expand the details for the circuit pack and VCGs being used. Highlight the tributary (Trib) being enabled then click Select.

Select Enabled for the VCG Membership in both the Input and Output Direction. Click Apply, read the warning message, then click Yes to execute the command. Repeat this step for each tributary being enabled. Click Close to exit

When Input VCG Membership (source) (inmbs) is enabled, the VCG tributary is a member of the VCG in the source direction (towards the SONET network). When Output VCG Membership (sink) (outmbs) is enabled, the VCG tributary is a member of the VCG in the sink direction (away from the SONET network).

Reference:

Procedure 11-25: Provision LCAS, add/enable/remove tributaries

After all cross-connections are made, click on the Alarm List button on the System View window and verify no alarms are present.

If alarms are present, look for missing or improperly made cross-connections.

Reference:

Alcatel-Lucent 1665 Data Multiplexer Extend (DMXtend) Alarm Messages and Trouble Clearing Guide, 365-372-326

Important!

For LNW63/64/70/74/87 circuit packs, at least one tributary at each end of the circuit must be Enabled in order for the VCG to go in service.

If required, after all cross-connections have been made, verify that the WAN (VCG) Ports being used have gone in service at each terminating node. From the System View menu at each terminating node, select View → Data → Ethernet/Data/VCG Port.

Result:

The View LAN (Ethernet) WAN (VCG) Port window opens.

Expand the details for the circuit pack being used. Select the required VCG v( ) port, then click Select at the bottom of the window. Verify the VCG AID is correct at the top of the parameter display.

Click on the VCG Data tab. Under the Fault section of the parameter display, verify the VCG Monitoring Mode is IS (in service). If the VCG Monitoring Mode is IS, proceed to Step 21.

• If the VCG Monitoring Mode is NMON (Not Monitored),

  Perform the following:

  1. Click Close to exit this window. From the System View menu, select Configuration → Equipment. Expand the details for the circuit pack being used, then select the required VCG v( ) port and click Select at the bottom of the window.

  2. In the parameters display area, click the VCG Data tab. Under the Fault section, select AUTO for the VCG Monitoring Mode.

  3. Click Apply at the bottom of the window then click Yes in the warning message to execute the command.

  4. Click Close to exit the window, then repeat this procedure from Step 19.

• If the VCG Monitoring Mode is AUTO:

  Look for missing or improperly made cross-connections. Verify that the proper cross-connections were made to the correct VCG at each terminating node.

  If proper cross-connections have been made, then indications are that either the far-end or near-end circuit pack at each end of the span has failed or must be reset. If the circuit pack already has service established on another pair of VCGs, the following will interrupt service.

  • Log in to the NE at the far end of the span that connects to the near-end VCG not in service. Select the Fault → Reset → Smart Pack command from the System View menu, then select the circuit pack to be reset. Click Apply. Read the warning message, then click Yes. Wait until the alarms clear, then check the VCG Monitoring Mode again. If the VCG Monitoring Mode does not go in service (IS), then reset the near-end circuit pack and check the VCG Monitoring Mode.

  • If, after resetting the circuit packs, the VCG is still not in service, replace, one at a time, the far-end and near-end circuit packs.

Reference:

Alcatel-Lucent 1665 Data Multiplexer Extend (DMXtend) Alarm Messages and Trouble Clearing Guide, 365-372-326

PROVISION LAN PORTS

Use the TL1 ed-eport command to provision the LAN port parameters, or select Configuration → Equipment from the System View menu. Expand the details for the circuit pack, highlight the LAN Port, then click Select. Provision the parameters as required.

Reference:

Procedure 11-8: Provision Ethernet LAN port parameters

Click Apply. Read the warning message, then click Yes to execute the command.

PROVISION VCGS

Use the ed-vcg TL1 command to provision the WAN (VCG) port parameters, or select Configuration → Equipment from the System View menu, if window is not already open from the previous step. Expand the details for the circuit pack, highlight the VCG port, then click Select. Provision the parameters as required.

Reference:

Procedure 11-9: Provision VCG parameters

Click Apply. Read the warning message, then click Yes to execute the command. Click Close to exit or repeat from Step 21 for other port provisioning.

End of steps