Procedure 9-3: Discontinue Alcatel-Lucent 1665 DMX node from network
Overview
Use this procedure to discontinue a Alcatel-Lucent 1665 DMX node from a unidirectional path switched ring (UPSR) or bidirectional line switched ring (BLSR).
The Alcatel-Lucent 1665 DMX node may interface with a UPSR/BLSR using the OLIU circuit packs in the Main slot pair or a Function/Growth slot pair.
Important!
All nodes in the existing network must have the same software release before removing a node.
Before you begin
Prior to performing this procedure:
-
Refer to Before you begin in this chapter
-
Refer to Laser safety and Electrostatic discharge information in Chapter 1, Safety.
Steps
Important!
When optical fibers are disconnected during this procedure, inc. LOS, section DCC channel failed, and neighbor SYSCTL CP unavailable alarms are reported. The holdover mode active condition may also be reported depending on the provisioned system timing mode.
Complete the following steps to discontinue a Alcatel-Lucent 1665 DMX node from a UPSR or BLSR.
1 |
To verify that no alarms are present, click the Alarm List button at each node. If required, clear any alarms that are present. Reference: Alcatel-Lucent 1665 Data Multiplexer (DMX) Alarm Messages and Trouble Clearing Guide, 365-372-302 | ||||||
2 |
Important! To retrieve a map of the SONET network, select Administration → OSI Routing Map and Administration → OSI Neighbor Map. To retrieve a map of the BLSR select View → Rings → Ring Map. Determine which Alcatel-Lucent 1665 DMX node is being discontinued. | ||||||
3 |
Verify that the optical loss budget will not be exceeded by removing this node. (Refer to the Alcatel-Lucent 1665 Data Multiplexer (DMX) Applications and Planning Guide, 365-372-300 for the SONET optical specifications of the OLIU circuit packs.) | ||||||
4 |
Verify the system timing at each node using the View → Timing/Sync command. If required, reconfigure the timing of the network using the Configuration → Timing/Sync command. Important! Reconfiguring network timing may cause nodes to temporarily go into the holdover timing mode. Reference: Procedure 6-5: Network Element synchronization provisioning | ||||||
5 |
Discontinuing a node with active add/drop traffic will result in a service interruption. Ensure that ALL service to/from the UPSR/BLSR is removed from the node before continuing. At the node being discontinued, verify that all service to/from the UPSR/BLSR has been removed. From the System View menu, select View → Cross-Connections to verify that there are no add/drop cross-connections to the UPSR/BLSR. If required, delete any existing add/drop cross-connections to the UPSR/BLSR using Configuration → Cross-Connections. | ||||||
6 |
If the node being discontinued is an AGNE, establish another node in the network as an AGNE (if required). If required, disable the AGNE at the node being discontinued. Important! At the new AGNE, the Remote NE Status parameter must be enabled prior to designating the AGNE(s). Reference: | ||||||
7 |
If the node being discontinued is the gateway host node, establish another gateway host node with an IP address for the network element and the required IP addresses in the gateway host file. Reference: Procedure 7-16: Provision/enable/disable the NE as a TL1 TCP/IP GNE | ||||||
8 |
End of steps |
