ECU to ECU2 In-Service Migration Procedure for NCS4000 System with CLI

Available Languages

Download Options

PDF (2.2 MB)
View with Adobe Reader on a variety of devices
ePub (2.5 MB)
View in various apps on iPhone, iPad, Android, Sony Reader, or Windows Phone
Mobi (Kindle) (2.0 MB)
View on Kindle device or Kindle app on multiple devices

Updated:July 14, 2020

Document ID:215796

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Background Information

Establish a connection to the NCS4K and Verify Minimum Software Release of 6.5.26

Introduction

This document describes the necessary information in order to successfully swap an in-service External Connection Unit (ECU) installed in an NCS4016 system and replace with ECU 2. It procedure provides steps to remove/install ECU.

Prerequisites

Requirements

Cisco recommends that you have knowledge of these topics:

CLI Cisco IOS® for the Cisco NCS4000 series
Cisco NCS4000 series inclusive of NCS4016/NCS4009

Components Used

The information in this document is based on NCS4016 system running 6.5.26 or later software before the start of this procedure.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, ensure that you understand the potential impact of any command.

Background Information

The procedure detailed in this document does not affect the traffic. It assumes that the NCS4000 chassis is a 4016 or 4009 shelf. If your network is live, ensure that you understand the potential impact of any command.

Establish a connection to the NCS4K and Verify Minimum Software Release of 6.5.26

Before you begin, ensure that you have set up a laptop connection to the NCS 4016 and the laptop meets the hardware and software requirements.

Step 1. From the computer connected to the NCS 4016 shelf, start a terminal emulator program such as putty and login to the NCS4016 system.

Step 2. At the command prompt, execute show version and verify the software release is 6.5.26 as shown in the image.

Step 3. If the software is not on 6.5.26 or later, stop the procedure and upgrade the software to 6.5.26 before you continue.

Step 4. Verify and note all alarms as shown in the image.

Step 5. Verify hard drive details.

Step 6. Create a database backup.

Step 7. Verify the BITS timing. If the BITS timing is used by the NCS4K, record the output for these commands. If no timing is used, skip to Step 8. Record the output for the command show controller timing controller clock as shown in the image.

Record the output for the command show frequency synchronization clock-interfaces brief as shown in the image.

Step 8. Prepare for ECU removal. In order to safely remove the ECU from service, issue a detach command hw-module provision ecu detach disk rack 0 as shown in the image.

Step 9. Before the ECU Module is removed physically, please ensure the alarm The Detach Operation for disk started is cleared on the system.

Step 10. Remove the ECU Module from the NCS4K chassis:

a. Ensure the user is wearing an ESD wrist strap.

b. Remove all cables connected to the NCS4K-ECU module.

c. When you remove the EMS cable, it will drop all remote management to the shelf. It will not be restored until the EMS cable is reconnected in Step 11. Remote access can still be attained with the use of the console port.

e. Remove all individual timing cables connected to the unit.

f. Use a Philips screwdriver in order to loosen screws on the ECU unit.

g. Use the latch on both sides to plug out the NCS4K-ECU unit.

h. Remove both 2.5” SATA drives (SSD) from the original NCS4K-ECU. Note the exact position, left or right, in the ECU.

i. Insert the 2.5” SATA drives removed from NCS4K-ECU into the new NCS4K-ECU2 module. Ensure they are installed in the same position as the original ECU.

Step 11. Install the ECU2 module and reconnect cables:

a. Place the new NCS4K-ECU2 module with both 2.5” SATA drives into the original ECU slot.

b. Reconnect all cables removed in Step 10. to the new ECU2 Module.

c. Tighten the screws after latches are positioned correctly.

d. Ensure remote management connectivity to the NE is available again.

e. Ensure the NE’s front-panel LCD is operational.

Step 12. Initialize new ECU2 in NCS4K Chassis. Wait for 2 to 3 minutes for NCS4K-ECU2 module to initialize.

Step 13. Execute attach command from the command prompt as shown in the image.

Step 14. Once the ECU attaches successfully to the chassis, the ECU migration from NCS4K-ECU to NCS4K- ECU2 is complete.

Post Checks

Verify Alarms

Verify alarms and ensure there are no new or unexpected alarms on the shelf.

Note: The Disk space alert for location alarm might take a little longer to idle for both RP0 and RP1 but you can verify the disk is operational with the sh media command.

Verify Media

Verify that both solid-state disk drives are slotted correctly and reachable as shown in the image.

BITS Timing Re-Check

If BITS timing was equipped and section 1.5 was completed, run the commands again after you re-attach the BITS timing to ECU2 and compare with previous results as shown in the image.