Replacing An Npu1 C With An Npu1 D; Preparing A Site Visit; Identifying Current Software; Placing Files On An Ftp Server - Ericsson MINI-LINK TN Operating Instructions Manual

Replacing an npu1 c with an npu1 d
Table of Contents

Advertisement

Replacing an NPU1 C with an NPU1 D

4
Replacing an NPU1 C with an NPU1 D
The following sections describe how to replace an NPU1 C with an NPU1 D,
and how to move the existing licenses from the NPU1 C to the NPU1 D by
reusing the RMM from the NPU1 C.
4.1

Preparing a Site Visit

This section presents the preparations needed for a successful completion of
the procedures in this instruction. All these preparations can be performed both
locally and remotely.
4.1.1

Identifying Current Software

To identify which SBL is running on the NE:
1. Access the NE and start MINI-LINK Craft by following the instructions in
2. In the Management Tree, right-click the NE.
3. Point to Tools, Software Upgrade, and click Software Upgrade.
4. On the Software Upgrade page, identify the current SBL running on the
4.1.2

Placing Files on an FTP Server

If the SBL needs to be upgraded, place the SBL files on a remote FTP server or
a local FTP server by following the instructions in Upgrading or Downgrading a
SW Baseline, Reference [11].
4.1.3

Preparing a Configuration File

Because the configuration file for the NPU1 C cannot be used to configure the
NPU1 D, it is recommended to prepare a configuration file for the NPU1 D
before visiting the site. For more information on configuration management,
see applicable Configuration Documents. For more information on preparing
and transferring a CLI script, see Preparing a CLI Script File Offline, Reference
[12], and Transferring a CLI Script File on Site, Reference [13].
It is also recommended to upload the existing configuration file for the NPU1
C and to generate a configuration report as a back up, in case the installation
of the NPU1 D fails. Do this by following the instructions in Backing Up and
Restoring a Configuration File, Reference [3] and Generating a Configuration
Report, Reference [4].
6
Accessing a Network Element, Reference [1].
NE.
107/1543-HRA 901 20-V11 Uen B | 2015-12-01

Advertisement

Table of Contents
loading

Table of Contents