cc/td/doc/product/ong/15400/r70docs
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table Of Contents

Power Down a Node

NTP-G119 Power Down the Node


Power Down a Node


This chapter explains how to power down a node and stop all node activity on the Cisco ONS 15454 ANSI or ETSI.


Note The CTC views referenced in this chapter depend on the ONS 15454 mode. For more information about CTC views, refer to "CTC Information and Shortcuts."


NTP-G119 Power Down the Node

Purpose

This procedure stops all node activity.

Tools/Equipment

None

Prerequisite Procedures

None

Required/As Needed

As needed

Onsite/Remote

Onsite

Security Level

Provisioning or higher



Warning Do not reach into a vacant slot or chassis while you install or remove a module or a fan. Exposed circuitry could constitute an energy hazard. Statement 206



Caution The following procedure is designed to minimize traffic outages when powering down nodes, but traffic will be lost if you delete and recreate circuits that passed through a working node.


Note Always use the supplied ESD wristband when working with the Cisco ONS 15454. Plug the wristband into the ESD jack located on the fan-tray assembly or on the lower right outside edge of the shelf on the NEBS 3 shelf assembly. To access the ESD plug on the NEBS 3 shelf assembly, open the front door of the Cisco ONS 15454. The front door is grounded to prevent electrical shock.



Step 1 Identify the node that you want to power down. If no cards are installed, go to Step 16. If cards are installed, log into the node. See the "DLP-G46 Log into CTC" task for instructions.

Step 2 Choose Go to Network View from the View menu.

Step 3 Verify that the node is not connected to a network.

a. If the node is part of a Software R4.7 or later dense wavelength division multiplexing (DWDM) configuration, see the "NTP-G130 Remove a DWDM Node" task continue with Step 4.

b. If the node is not connected to a working network and the current configurations are no longer required, proceed to Step 4.


Note Before the power-down of a DWDM node, the fiber spans connected around it must be disconnected from the network. This is to prevent the accidental disconnection of wavelengths that pass through the shelf. A good indication that the shelf has been disconnected from the network is optical service channel (OSC) alarms, or no OSC channels provisioned.



Note Current configurations will be saved if Steps 4 to 16 are skipped.


Step 4 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Circuits tab and verify that no circuits appear, then proceed to Step 5. If circuits appear, delete all the circuits that originate or terminate in the node. Complete the "DLP-G106 Delete Optical Channel Network Connections" task on page 7-14, the "DLP-G347 Delete Optical Channel Client Connections" task on page 7-8, or the "DLP-G112 Delete Overhead Circuits" task on page 7-29 as needed.


Note When deleting circuits from a node, make sure that the node is not connected to any network.


Step 5 In node view (single-shelf mode) or shelf view (multishelf mode), click the Provisioning > Protection tabs and delete all protection groups:

a. Click the protection group that needs to be deleted and click Delete.

b. Click Yes.

Repeat until no protection groups appear.

Step 6 In node view (single-shelf mode) or multishelf view (multishelf mode), click the Provisioning > Comm Channels tabs and delete all communications channel terminations:

a. Click the section data communications channel (SDCC), line data communications channel (LDCC), generic communications channel (GCC), or OSC termination that needs to be deleted and click Delete.

b. Click Yes.

Repeat until no SDCC, LDCC, GCC, or OSC terminations are present.


Note Before deleting the OSC termination, make sure the Ring ID is deleted. Click the Provisioning > Comm Channels > OSC tabs. Select the Ring ID and click Delete.


Step 7 Before deleting any installed DWDM cards, the optical patch cords have to be deleted. In node view (single-shelf mode) or multishelf view (multishelf mode), click Provisioning > WDM-ANS > Connections tabs.

a. Select all the connections and click Delete.

b. Click Yes.

Step 8 For each installed channel-bearing card (AD-1C-xx.x, AD-2C-xx.x, and AD-4C-xx.x, where xx.x refers to the specific wavelengths), make sure all lines and bands are not in IS-NR (ANSI) or Unlocked-Enabled (ETSI) service state:

a. In card view, click the Provisioning > Optical Line > Parameters tabs.

b. In the Admin State column for each line, make sure that the default state IS, AINS (ANSI) or Unlocked,automaticInservice (ETSI) is selected.

c. Click the Provisioning > Optical Chn > Parameters tabs.

d. In the Admin State column for each line, make sure that the default state IS, AINS (ANSI) or Unlocked,automaticInservice (ETSI) is selected.

Step 9 For each installed DWDM band-bearing card (AD-1B-xx.x and AD-4B-xx.x, where xx.x refers to the specific wavelengths), make sure all lines and bands are not in the IS-NR (ANSI) or Unlocked-Enabled (ETSI) service state:

a. In card view, click the Provisioning > Optical Line > Parameters tabs.

b. In the Admin State column for each line, make sure that the default state IS, AINS (ANSI) or Unlocked,automaticInservice (ETSI) is selected.

c. Click the Provisioning > Optical Band > Parameters tabs.

d. In the Admin State column for each line, make sure that the default state IS, AINS (ANSI) or Unlocked,automaticInservice (ETSI) is selected.

Step 10 For each installed transponder (TXP), muxponder (MXP), multiplexer, demultiplexer or amplifier card (32MUX-O, 32DMX-0, 32DMX, 32WSS, 4MD-xx.x, OPT-BST, OPT-PRE, TXP_MR_10G, TXP_MR_10E, TXP_MR_2.5G, TXPP_MR_2.5G, MXP_2.5G_10G, MXP_2.5G_10E, MXP_MR_2.5G, MXPP_MR_2.5G), make sure all lines are not in the IS-NR (ANSI) or Unlocked-enabled (ETSI) service state:

a. In card view, click the appropriate tab depending on the card:

For MXP_2.5G_10G, TXP_MR_10G, TXP_MR_10E cards, click the Provisioning > Line > SONET tabs if the card was provisioned for a SONET payload, or the Provisioning > Line > SDH tabs if the card was provisioned for an SDH payload.

For TXP_MR_2.5G, TXPP_MR_2.5G, and MXPP_MR_2.5G cards, click the Provisioning > Line > OC48 tabs.

For MXP_2.5G_10E cards, click the Provisioning > Line > Trunk tabs.

For MXP_MR_2.5G cards, click the Provisioning > Line > Client tabs.

For 32MUX-O, 32DMX-0, 32DMX, 32WSS, OPT-BST, OPT-PRE cards, click the Provisioning > Optical Line > Parameters tabs.

For 32DMX and 32DMX-O cards, click the Provisioning > Optical Chn > Parameters tabs.

For 4MD-xx.x cards, click the Provisioning > Optical Band > Parameters tabs.

For OPT-BST and OPT-PRE cards, click the Provisioning > Optical Ampli Line > Parameters tabs.

b. In the Admin State column for each line, make sure that the default state IS, AINS (ANSI) or Unlocked,automaticInservice (ETSI) is selected.

c. Repeat Steps a and b for each installed DWDM card.


Note Ports are put in service when circuits are provisioned, and put out of service when circuits are deleted. When circuits are deleted the Admin State displays as IS, AINS (ANSI) or Unlocked,automaticInservice (ETSI) and the Service State displays OOS-AU,AINS (ANSI) or Unlocked-disabled,automaticInService (ETSI).


Step 11 Remove all fiber connections to the cards.

Step 12 In node view (single-shelf mode) or shelf view (multishelf mode), right-click an installed card and click Delete.

Step 13 Click Yes.

Step 14 After you have deleted the card, open the card ejectors and remove it from the node.

Step 15 Repeat Step 11 through Step 14 for each installed card.


Note You cannot delete a TCC2 or TCC2P card in Cisco Transport Controller (CTC). Physically remove it after all the other cards have been deleted and removed.


Step 16 Shut off the power from the power supply that feeds the node.

Step 17 Disconnect the node from its external fuse source.

Step 18 Store all of the cards that you removed and update inventory records according to local site practice.

Stop. You have completed this procedure.



hometocprevnextglossaryfeedbacksearchhelp

Posted: Thu Sep 13 00:28:37 PDT 2007
All contents are Copyright © 1992--2007 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.