Replacing Multicontroller RNC Hardware Units

Copyrighted material licensed to carlos.paredes@nokia.com on 08-08-2022.
No further reproduction or networking is permitted. Distributed by Nokia.

Replacing Multicontroller RNC
WCDMA RAN mcRNC, WCDMA
FP21A, Issue 01
Hardware Units
Approval Date 2020-11-11

Nokia condential
DN09109953
Issue 08F
Replacing Multicontroller RNC Hardware Units
Nokia is committed to diversity and inclusion. We are continuously reviewing our customer
documentation and consulting with standards bodies to ensure that terminology is inclusive
and aligned with the industry. Our future customer documentation will be updated
accordingly.
The information in this document applies solely to the hardware/software product

(“Product”) specied herein, and only as specied herein. Reference to “Nokia” later in this
document shall mean the respective company within Nokia Group of Companies with whom
you have entered into the Agreement (as dened below).
This document is intended for use by Nokia's customers (“You”) only, and it may not be used
except for the purposes dened in the agreement between You and Nokia (“Agreement”)
under which this document is distributed. No part of this document may be used, copied,
reproduced, modied or transmitted in any form or means without the prior written
permission of Nokia. If You have not entered into an Agreement applicable to the Product,
or if that Agreement has expired or has been terminated, You may not use this document in
any manner and You are obliged to return it to Nokia and destroy or delete any copies
thereof.
The document has been prepared to be used by professional and properly trained
personnel, and You assume full responsibility when using it. Nokia welcomes your comments
as part of the process of continuous development and improvement of the documentation.
This document and its contents are provided as a convenience to You. Any information or
statements concerning the suitability, capacity, tness for purpose or performance of the
Product are given solely on an “as is” and “as available” basis in this document, and Nokia
reserves the right to change any such information and statements without notice. Nokia has
made all reasonable efforts to ensure that the content of this document is adequate and
free of material errors and omissions, and Nokia will correct errors that You identify in this
document. Nokia's total liability for any errors in the document is strictly limited to the
correction of such error(s). Nokia does not warrant that the use of the software in the
Product will be uninterrupted or error-free.
NO WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO
ANY WARRANTY OF AVAILABILITY, ACCURACY, RELIABILITY, TITLE, NON-INFRINGEMENT,
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, IS MADE IN RELATION TO THE
CONTENT OF THIS DOCUMENT. IN NO EVENT WILL NOKIA BE LIABLE FOR ANY DAMAGES,
INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR
CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED TO LOSS OF PROFIT,
REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY OR DATA THAT MAY ARISE
FROM THE USE OF THIS DOCUMENT OR THE INFORMATION IN IT, EVEN IN THE CASE OF
2 © 2021 Nokia.Nokia confidential

ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.
This document is Nokia proprietary and condential information, which may not be
distributed or disclosed to any third parties without the prior written consent of Nokia.
Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in

this document may be trademarks of their respective owners.
Copyright © 2021 Nokia. Nokia condential.
Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other
sources of danger.
Only trained and qualied personnel may install, operate, maintain or otherwise
handle this product and only after having carefully read the safety information
applicable to this product.
The safety information is provided in the Safety Information section in the “Legal,
Safety and Environmental Information” part of this document or documentation
set.
Nokia is continually striving to reduce the adverse environmental effects of its products and
services. We would like to encourage you as our customers and users to join us in working
towards a cleaner, safer environment. Please recycle product packaging and follow the
recommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental
services we offer, please contact us at Nokia for any additional information.
© 2021 Nokia.Nokia confidential 3

© 2021 Nokia.Nokia confidential

4
Table of Contents
Summary of changes .................................................................................................................. 10
1 Replacing BCN module ............................................................................................................... 13

1.1 Removing the BCN module from the running system ............................................... 14
1.2 Installing the new BCN module ...................................................................................... 20
1.2.1 Preparing LMP in BCN modules .......................................................................... 28
1.2.1.1 Preparing LMP in BCN module 1 in S3-B2 conguration .................... 28
1.2.1.10 Preparing LMP in BCN module 6 in S7-B2 conguration ................. 60
2 Replacing an add-in card ........................................................................................................... 73

2.1 Removing an add-in card ............................................................................................... 74
2.2 Installing an add-in card ................................................................................................. 80
3 Replacing the SO-DIMM on motherboard ............................................................................... 87

3.1 Removing add-in cards from slots 7 and 8 ................................................................. 88
3.2 Removing SO-DIMM memory module .......................................................................... 94
3.3 Installing SO-DIMM memory module ......................................................................... 100
3.4 Installing removed add-in cards back to slots 7 and 8 ........................................... 104
4 Replacing the system hard disk .............................................................................................. 109

4.1 Removing the AMC from BCN module ....................................................................... 110
4.2 Removing the faulty HDD from AMC .......................................................................... 112
4.3 Installing the new HDD on AMC ................................................................................... 112
4.4 Installing the AMC back to BCN module .................................................................... 113
4.5 Enabling the new HDD .................................................................................................. 114
5 Replacing the disaster recovery hard disk ............................................................................ 121

5.1 Removing the AMC from BCN module ....................................................................... 122
5.2 Removing the faulty HDD from AMC .......................................................................... 124
5.3 Installing the new HDD on AMC ................................................................................... 124
5.4 Installing the AMC back to BCN module .................................................................... 125
6 Replacing the failed HDDs on both CFPU nodes ................................................................. 127
7 Replacing the power distribution unit (PDU) ........................................................................ 128

7.1 Removing the PDU ........................................................................................................ 129

7.2 Installing the PDU .......................................................................................................... 131
8 Replacing a power supply unit ................................................................................................ 133

8.1 Removing a power supply unit .................................................................................... 133
8.2 Installing a power supply unit ...................................................................................... 134
9 Replacing a fan module ........................................................................................................... 136

9.1 Removing a fan module ............................................................................................... 138
9.2 Installing a fan module ................................................................................................. 138
10 Replacing the air lter ........................................................................................................... 139
11 Replacing the BCN installation support kit BSK216-A ...................................................... 140

11.1 Removing the BCN installation support kit BSK216-A .......................................... 140
11.2 Installing the new BCN slide rail BSR216-A ............................................................. 141
12 Replacing the BCN installation kit BIK216-A ...................................................................... 142

12.1 Removing the BCN installation kit BIK216-A .......................................................... 142
12.2 Installing the new BCN installation kit BSIK216-A ................................................. 144
13 Performing hardware diagnostics ....................................................................................... 147

13.1 Viewing the hardware diagnostic tests available for an FRU ................................ 148
13.2 Starting a hardware diagnostic test ........................................................................ 153
13.2.1 Failure in the test execution phase .............................................................. 157
13.3 Viewing the status of a hardware diagnostic test ................................................. 159
13.4 Showing the hardware diagnostic results and managing its reports .................. 160
14 Appendix: Screen command ................................................................................................. 163

List of Figures
Figure 1 BCN module 1 in S3-B2 ............................................................................................... 29
Figure 10 BCN module 6 in S7-B2 ............................................................................................. 60
Figure 13 Removing the BCN module top cover ..................................................................... 79
Figure 14 BCN module add-in card screws .............................................................................. 79
Figure 15 Pulling an add-in card out from the BCN module ................................................. 79
Figure 16 Inserting an add-in card into the BCN module ...................................................... 80
Figure 17 BCN add-in card screws ............................................................................................ 80
Figure 18 Installing BCN top cover ............................................................................................ 81
Figure 19 Removing the BCN module top cover ..................................................................... 93
Figure 20 BCN module add-in card screws .............................................................................. 93
Figure 23 SO-DIMM memory module ....................................................................................... 94
Figure 24 Removing SO-DIMM memory module ..................................................................... 96
Figure 25 SO-DIMM sprung up ................................................................................................... 96
Figure 26 Pulling out the SO-DIMM memory module ............................................................. 98
Figure 27 SO-DIMM memory module removed ....................................................................... 99
Figure 28 Installing a new SO-DIMM memory module ......................................................... 100
Figure 29 Installing a new SO-DIMM memory module in socket ........................................ 102
Figure 30 Locking the new SO-DIMM memory module ....................................................... 103
Figure 31 Inserting an add-in card into the BCN module .................................................... 104
Figure 32 Inserting an add-in card into the BCN module .................................................... 104
Figure 33 BCN add-in card screws .......................................................................................... 105
Figure 34 Installing BCN module top cover ........................................................................... 105
Figure 35 The SAS/SATA switch in the HDSAM-A ................................................................. 110
Figure 36 Pulling the hot swap handle of an AMC ................................................................ 111
Figure 37 Removing an AMC from the BCN module ............................................................. 111
Figure 38 HDD on HDSAM-A .................................................................................................... 112
Figure 39 Installing the HDD on HDSAM-A ............................................................................ 113
Figure 40 Inserting an AMC into the BCN module ................................................................ 114

Figure 41 Pressing the hot swap handle ................................................................................ 114

Figure 42 The SAS/SATA switch in the HDSAM-A ................................................................. 122
Figure 43 Pulling the hot swap handle of an AMC ................................................................ 123
Figure 44 Removing an AMC from the BCN module ............................................................. 123
Figure 45 HDD on HDSAM-A .................................................................................................... 124
Figure 46 Installing the HDD on HDSAM-A ............................................................................ 125
Figure 47 Inserting an AMC into the BCN module ................................................................ 126
Figure 48 Pressing the hot swap handle ................................................................................ 126
Figure 49 Power distribution units in the cabinet ................................................................ 128
Figure 50 Location where the digital multimeter should be placed .................................. 130
Figure 51 Replacing a PDU ....................................................................................................... 131
Figure 52 Installing PDU to the cabinet ................................................................................. 131
Figure 53 PDU grounding cable ............................................................................................... 132
Figure 54 Connecting site power supply cables to the PDU ............................................... 132
Figure 55 Removing an AC PSU from the BCN module ........................................................ 134
Figure 56 Removing a DC PSU from the BCN module ......................................................... 134
Figure 57 BCN fan modules ..................................................................................................... 136
Figure 58 Location of the fan to be replaced ....................................................................... 137
Figure 59 Unscrewing the two thumbscrews ........................................................................ 139
Figure 60 Opening the air filter cover and pulling out the air filter ................................... 139
Figure 61 Removing BSK216-A from the cabinet ................................................................. 141
Figure 62 Installing BCN slide rail BSR216-A to the cabinet ............................................... 141
Figure 63 Sliding the BCN module out from the cabinet .................................................... 143
Figure 64 Removing the cable tray from the BCN module ................................................. 143
Figure 65 Removing brackets from the BCN module ........................................................... 144
Figure 66 Fixing brackets to the BCN module ....................................................................... 145
Figure 67 Fixing the cable tray to the BCN module .............................................................. 145
Figure 68 Sliding the BCN module into the cabinet ............................................................. 146

List of Tables
Table 1 SO-DIMM memory module identification details ...................................................... 87
Table 2 List of available DIMI tests ......................................................................................... 150
Table 3 List of available group DIMI tests .............................................................................. 151
Table 4 Parameters of the command for getting the available diagnostic tests ............ 152
Table 5 Parameters of the command for starting a diagnostic test ................................. 155
Table 6 Parameters of the command for viewing the status of a diagnostic test
......................................................................................................................................... 160
Table 7 Parameters of the command for viewing the test reports ................................... 162

Summary of changes
A list of changes between document issues. You can navigate through the
respective changed topics.
In this summary of changes:

Changes between issues 08E (2020-09-30, WCDMA20) and 08F (2020-11-11, WCDMA
20)
Changes between issues 08D (2020-09-01, WCDMA 20) and 08E (2020-09-30,
WCDMA20)
Changes between issues 08C (2020-08-13, WCDMA 20) and 08D (2020-09-01, WCDMA
20)
Changes between issues 08E (2020-09-30, WCDMA20)

and 08F (2020-11-11, WCDMA 20)
Removing the BCN module from the running system
Updated the description and example in the step - Shut down the BCN module using the
zchassis_ex script.
Removing an add-in card
Updated the procedure.
Replacing the SO-DIMM on motherboard
Updated the sections in this chapter as required for BCN module.

Procedure updated for mcRNC.
Removing add-in cards from slots 7 and 8
Updated the example for the step - Shut down BCN module using the zchassis_ex script
and the related steps.

Installing removed add-in cards back to slots 7 and 8
Updated the steps for running the zchassis_ex script and the related steps.
Changes between issues 08D (2020-09-01, WCDMA

20) and 08E (2020-09-30, WCDMA20)
Removing an add-in card
Updated the procedure.
Replacing the SO-DIMM on motherboard
Procedure updated for mcRNC.
Removing add-in cards from slots 7 and 8
Updated additional information on BCN module.
Enabling the new HDD
Reordered the procedure.
Changes between issues 08C (2020-08-13, WCDMA

20) and 08D (2020-09-01, WCDMA 20)
Removing the BCN module from the running system
Updated the description and example in the step - Shut down the mcRNC module using
the zchassis_ex script.
Installing the new BCN module
Added a step instructing to bring down the interface while preparing the replacement
mcRNC module.
Preparing LMP in BCN modules
Following changes are made in the sub-sections:


Added a step to set LMP date and time.
Updated the prerequisites
12
1. Replacing BCN module
Replacing a faulty BCN module requires general steps to be performed.
Purpose
In a multi-chassis environment (two or more BCN modules), if the existing BCN module is
faulty, it needs to be removed and replaced with a new BCN module.
Before you start

To replace one BCN module, the operator must do the following:
1. Identify the BCN module to be replaced.

2. Perform a graceful shutdown of the BCN module.
3. Uninstall the BCN module.
4. Install the new BCN module.
5. Prepare the LMP pre-configuration of the new BCN module.
6. Activate the new BCN module.
7. Verify the system.
Note:
In mcRNC VRRP using 10 Gigabit Ethernet optimized connectivity site solution,

multiple Box Controller Nodes (BCNs) share the same 10GE port group. When a BCN
with the 10GE interface is shutdown, redundancy for other BCNs cannot work
automatically. This means that the recovery group (QNIUB/QNUP) on these BCNs
cannot trigger switchover, and therefore traffic is completely lost. If this scenario
occurs, the customer must manually lock all EIPU nodes on these BCNs, or restart
these BCNs to make the redundancy valid. However, if the 10GE port is broken, all
the recovery groups do the switchover normally.

1.1 Removing the BCN module from

the running system
This chapter provides the steps to remove the BCN module from the system.
Procedure
1 Identify the BCN module to be replaced in the running system.
Note:
In this procedure, the BCN module that is identified to be replaced is BCN
module-2.
2 Connect to the CFPU-0 through the operation and maintenance (O&M)

network of the customer.
3 Check which of the nodes running in the BCN module are to be replaced.
Enter the following command:
show hardware state list
The following output is displayed:
root@CFPU-0 [RNC-1008] > show hardware state list
CFPU-0@RNC-1008 [2017-08-29 15:05:15 +0800]
cabinet-1 : unit /cabinet-1
chassis-1 : unit /cabinet-1/chassis-1
chassis-2 : unit /cabinet-1/chassis-2
LMP-1-1-1 : unit available /cabinet-1/chassis-1/piu-1
LMP-1-2-1 : unit available /cabinet-1/chassis-2/piu-1
CFPU-0 : node available
/cabinet-1/chassis-1/piu-1/addin-1/CPU-1/core-0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27
CFPU-1 : node available
/cabinet-1/chassis-2/piu-1/addin-1/CPU-1/core-0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26,27
USSR-0 : node available /cabinet-1/chassis-1/piu-1/addin-1/CPU-1/core-28,29,30,31
CSPU-0 : node available /cabinet-1/chassis-1/piu-1/addin-2/CPU-1/core-0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17
CSUP-0 : node available /cabinet-1/chassis-1/piu-1/addin-2/CPU-1/core-18,19,20,21,22,23,24,25,26,27,28,29,30,31
USPU-0 : node available /cabinet-1/chassis-1/piu-1/addin-3/CPU-1/core-0,1,2,3,4,5,6,7,8,9,24,25,26,27

USUP-0 : node available
/cabinet-1/chassis-1/piu-1/addin-3/CPU-1/core-10,11,12,13,14,15,16,17,18,19,20,21,22,23,28,29,30,31
EIPU-0 : node available /cabinet-1/chassis-1/piu-1/addin-4/CPU-1/core-0,1,2,3,4,5,6,7,8,9,10,11,12,13,14,15
EITP-0 : node available
/cabinet-1/chassis-1/piu-1/addin-4/CPU-1/core-16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,31
USSR-1 : node available /cabinet-1/chassis-2/piu-1/addin-1/CPU-1/core-28,29,30,31
cluster : cluster available
The output provides that the following nodes are to be replaced in the BCN module:

CFPU-1
CSPU-1
USPU-1
EIPU-1
CSPU-3
USPU-3
USPU-5
EIPU-3
USSR-1
CSUP-1
USUP-1
EITP-1
CSUP-3
USUP-3
USUP-5
EITP-3
Other useful commands are:

show alarm active-summary
show has summary
show radio-network wcelstatus blocked
4 Create a fallback build.
Use the following command:
save sw-manage app-sw-mgmt fb-build build-name <build-name>
5 Check if the SSH service is impacted by the module replacement.
If the BCN module to be replaced is module-1 or module-2, find out with the following
SCLI command the CFPU node, in which the active instance of the FSSSHServer
recovery unit is located:
show has state managed-object /CFPU*/FSSSHServer
Step result
The following outcome is displayed:

OBJECT ADMINISTRATIVE OPERATIONAL USAGE ROLE

PROCEDURAL DYNAMIC
/CFPU-0/FSSSHServer UNLOCKED ENABLED ACTIVE

ACTIVE - RESOURCE_STATE=FUNCTIONAL
RESOURCE_LEVEL=100
HOTSTANDBY - RESOURCE_STATE=FUNCTIONAL
RESOURCE_LEVEL=100
The role field displays whether the recovery unit is in active or standby mode. If the
FSSSHServer recovery unit is active in the BCN module to be replaced, execute a
switchover of the SSH recovery group by entering the following SCLI command:
set has switchover force managed-object /SSH
6 Shut down the BCN module using the zchassis_ex script.
1. Run the zchassis_ex script as root user.

2. Select: 1 - Shut Down Chassis
3. Select Chassis: Enter the chassis number [1-X] to shutdown.
4. Select time limit: Default value is 3(minutes): (this is the time limit when
zchassis is started and no new calls are allocated to the BCN module, and when the
time limit is reached existing calls in the BCN module are dropped).
5. Select: Select the fault handling mode.
6. Select Yes: Do you need power off nodes after shutdown
chassiss?[y/n]
7. Confirm the settings to proceed.
Step example
[root@CFPU-0(RNC-1001) /root]
# zchassis_ex
1 - Shut Down Chassis
2 - Start Up Chassis
3 - Show Chassis Information
0 - Exit

Please enter your choice:1
--------------------------------------------------------------------------------
Enter the chassis number[1-4] to shutdown.
(press <ENTER> to return to main menu):2
<<<INFO>>> Waiting for getting hardware information...
--------------------------------------------------------------------------------
Enter the node shutdown time limit.
Default value is 3(minutes):3
--------------------------------------------------------------------------------
Select the fault handling mode.
It is used for handling unexpected error during chassis shutdown.
0 - Interactive[Default] (interact with operator)
1 - Abort (quit immediately)
2 - Ignore (ignore error)
Please enter [0|1|2]:0
--------------------------------------------------------------------------------
Do you need power off nodes after shutdown chassiss?[y/n]
(Default is yes):
--------------------------------------------------------------------------------
Do you need power off LMP after shutdown chassiss?[y/n]
(If you need power cut of chassis, enter "yes",default is no):
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
<<<INFO>>> Checking chassis-2
<<<INFO>>> Checking chassis-2 Done!
Shutdown operation summary
Shutdown chassis : chassis-2
Fault handling mode : interactive
Node shutdown time limit(minutes): 3
Power off node: YES
Power off LMP: NO

--------------------------------------------------------------------------------
Enter "yes" to proceed:yes
--------------------------------------------------------------------------------
<<<INFO>>> Yield CMF Done!
<<<INFO>>> Disable CMF Done!
<<<INFO>>> Sleep 15 seconds.
<<<INFO>>> Lock RU: /CSPU-1/QNCSCPServer-0-1 /CSPU-3/QNCSCPServer-0-3 /CSPU-3/QNCSCPServer-1-3 /CSPU-1/QNCSCPServer-2-1
/CSPU-3/QNCSCPServer-2-3 /CSPU-1/QNCSCPServer-3-1 /CSPU-1/QNCSCPServer-4-1 /CSPU-3/QNCSCPServer-4-3[Done]
<<<INFO>>> Shutdown time left: 180 sec
<<<INFO>>> Shutdown nodes:CSPU-1 USPU-1 EIPU-1 CSPU-3 USPU-3 USPU-5 EIPU-3 CFPU-1
<<<INFO>>> Shutdown nodes:CSPU-1 USPU-1 CSPU-3 USPU-3 USPU-5
<<<INFO>>> Shutdown nodes:USPU-1 USPU-3 USPU-5
<<<INFO>>> Power off nodes:CSPU-1 USPU-1 EIPU-1 CSPU-3 USPU-3 USPU-5 EIPU-3 CFPU-1
<<<INFO>>> Power off nodes done
<<<INFO>>> Unlock RU: /CSPU-1/QNCSCPServer-0-1 /CSPU-3/QNCSCPServer-0-3 /CSPU-3/QNCSCPServer-1-3 /CSPU-1/QNCSCPServer-2-1
<<<INFO>>> Shutdown Chassiss Done! Total Time : 271.0 sec
<<<INFO>>> Generate shutdown report...
<<<INFO>>> Alarm History :/var/log/SS_ChassisMT/20200714/RNC-1001_chassis-02_ShutDownAlarmHistory_1103.log
<<<INFO>>> Shutdown Report :/var/log/SS_ChassisMT/20200714/RNC-1001_chassis-02_ShutDownReport_1103.log

7 Check the status of the BCN module.
Enter the following commands:
show has summary

show has state managed-object /*PU*
show hardware state list
8 Disconnect all the cables connected to the chassis to be replaced.
To disconnect the cables connected to the chassis to be replaced, refer the following
steps:
1. Switch off the circuit breaker on the power distribution unit (PDU) for the BCN
module in question.
2. Disconnect the power feed cables.
3. Disconnect all the cables from the transceivers on the front side of the chassis.
4. Disconnect the mcRNC grounding cable.
5. Keep the network cables attached to the front cable tray of the chassis.
6. Uninstall the cable tray with attached network cables from the BCN module. The
cable tray is uninstalled by unscrewing the two thumbscrews fixing the cable tray
to the BCN module. If the screws are too tight to be opened by hand, loosening the
screws that fix the BCN module mounting flanges to the cabinet might help. For
more information about detaching the cable tray, see Installing BCN Hardware to
CAB216SET-B.
7. Move the cable tray with attached network cables under the module, so the module
can be easily pulled out from the rack.
9 If there is a hard disk drive (HDD) in the AMC bay, remove it.
If the BCN module has an AMC slot, remove the HDD AMC.
10 Remove the BCN module to be replaced from the rack.
1.2 Installing the new BCN module
This chapter provides the steps in replacing an BCN module. The mcRNC
configuration and the BCN module to be replaced need to be taken into account.

Procedure
1 Insert the new BCN module in the rack.
2 Connect all cables to the new BCN module.
Note:
For detailed cabling information and instructions, see WCDMA RAN Operating
Documentation ► Install ► RNC ► Multicontroller RNC Hardware
Installation Quick Guide.
2.1 Install the cable tray with the attached network cables back to the
BCN module.
For more information about the cable tray installation procedure, see Installing
BCN Hardware to CAB216SET-D.
2.2 Connect the BCN module grounding cable.
2.3 Reconnect the network cables to the transceivers on the front side of
the module.
2.4 Connect the power feed cables.
2.5 Switch on the circuit breaker on the PDU for the BCN module in
question.
2.6 Wait until all LEDs are red or green.
3 Check if the eSW is on supported level.
Login to LMP and check the eSW version using the following command:
sw_fw_versioninfo
The command lists the software version of the LMP and all the add-in cards in the BCN
module. If the versions are compatible with the eSW delivered with mcRNC software
that you are currently using in the mcRNC, upgrading eSW in this step is not required.
You can upgrade eSW using the SCLI commands in a later stage. The operator must
familiarize with minimum required eSW versions described in software release notes.
If the eSW is on supported level on both active and backup bank, continue to step 4.
Otherwise, upgrade the eSW by performing the procedures described in Appendix 2:
Upgrading embedded software of Commissioning Multicontroller RNC HW Rel.2.
4 Prepare the replacement BCN module.
The sub-steps provide instructions for configuring the new BCN module so that it is

taken into use in a running mcRNC network element.
4.1 Bring down the dhcp interface on LMP.
1. Log in to the LMP.

2. Bring down the dhcp interface using the following command: ifdown
eth0.800
Note:
After the reboot in sub-step b, the interface comes up automatically.
If not, run the following command:
ifup eth0.800
4.2 Run the nokia_set_factory_default.sh script in the new module to

ensure that the configuration of the new module is known.
Note:
The following examples show the default MGT eth0 IP addresses used in
the new module:
1. In the LMP, enter the following command:cd /opt/bcntools/

2. Run the nokia_set_factory_default.sh script:
root@LMP-1-2-1:/opt/bcntools#
./nokia_set_factory_default.sh
3. Restart the box controller node (BCN) module to activate the configuration
using the following:
# mch_cli Reset BCN
4. Check the module configuration using the serial connection. Verify the
following values for ensuring that the factory settings was restored
successfully:
a. Check the IP address of the eth0 of the module (IP address of the module
must be 10.10.10.10):

# ip address show dev eth0

root@LMP-1-2-1:~# ip address show dev eth0
1: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500
qdisc
pfifo_fast qlen 1000
link/ether 00:d0:c9:da:f7:2e brd ff:ff:ff:ff:ff:ff
inet 10.10.10.10/24 brd 10.10.10.255 scope global eth0
inet6 fe80::2d0:c9ff:feda:f72e/64 scope link
valid_lft forever preferred_lft forever
root@LMP-1-2-1:~#
b. Check the rack number (rack number must be 1):
# mch_cli GetRackNumber
c. Check the node number (module node number must be 1):
root@LMP-1-2-1:~# mch_cli GetNodeNumber

1
root@LMP-1-2-1:~#
d. Check the network element (NE) ID (NE ID is an eleven-digit number that

must be xxxxxxxxxxx):
root@LMP-1-2-1:~# mch_cli GetNetworkElementId

network element id: xxxxxxxxxxx
root@LMP-1-2-1:~#
4.3 Pre-configure the new module by following the module number

specific instructions for the relevant mcRNC configuration (capacity
step), available in the section, Preparing LMP in BCN modules.
After restarting the BCN module and returning the session back to CFPU node
as the last steps of the pre-configuration procedure, continue to step d.
4.4 Wait for 10 minutes until the new BCN module has started up.
4.5 When connecting from the CFPU-X to the new BCN, Secure Shell (SSH)
keys need to be updated.
1. Delete the file /root/.ssh/known_hosts from both CFPU nodes with the
following command:
rm /root/.ssh/known_hosts

2. When logging in to the LMP of the new BCN module, ensure that the new
LMP prompt is in the following format:root@LMP-1-X-1
If not, delete the file /opt/dhcp_random from the LMP with the following
command:
rm /opt/dhcp_random
After the deletion, the dhcp_hook script runs automatically within ten
minutes and sets the LMP prompt.
3. Verify that the eSW matches the baseline version on the active and the
backup banks.
4. If needed, upgrade the eSW by performing the procedures described in
Appendix B: Upgrading embedded software of Commissioning Multicontroller
RNC HW Rel.2.
5 Check if the distributed replicated block device (DRBD) synchronization has

started.
Use the following:
cat /proc/drbd
If replacement BCN module contains an HDD in the AMC bay, DRBD synchronization is
required. Do not restart the node during the DRBD synchronization. The initialization
process of the new disk is not ready until the synchronization has successfully
completed. Wait until the synchronization is complete.
Step example

# watch -n 10 cat /proc/drbd
Every 10.0s: cat /proc/drbd Wed Apr 24 10:54:39 2013
version: 8.3.7 (api:88/proto:86-92)
srcversion: 35B9BF7C501212268498452
0: cs:Connected ro:Primary/Secondary ds:UpToDate/UpToDate C r----
ns:512081 nr:0 dw:635 dr:512860 al:4 bm:32 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:0
3: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r----
ns:2890764 nr:0 dw:46448 dr:2882497 al:32 bm:190 lo:0 pe:0 ua:0 ap:0 ep:1 wo:b oos:12469416 [==>.................] sync'ed:
18.9% (12176/14996)M
finish: 0:05:37 speed: 36,872 (30,744) K/sec
4: cs:PausedSyncS ro:Primary/Secondary ds:UpToDate/Inconsistent C rap--
7: cs:PausedSyncS ro:Primary/Secondary ds:UpToDate/Inconsistent C rap-- ns:0 nr:0 dw:12 dr:675 al:2 bm:0 lo:0 pe:0 ua:0 ap:0
ep:1 wo:b oos:8152
The example shows that the first blocks are already synchronized. The out-of-synch
(oos) value is zero. For block 3, the synchronization is in process and progress is
displayed. Once synchronization is complete, the oos value for all blocks will be 0.
Mirroring is ready when all partitions are ro:Primary/Secondary

ds:UpToDate/UpToDate.
6 Run the zchassis_ex script.

1. Run the following command:

zchassis_ex
Note:
Since the zchassis_ex operation takes more than 30 minutes, the SSH
might disconnect automatically which breaks the zchassis_ex operation.
Hence, when starting the zchassis_ex script a screen command (a
terminal emulator) is used that multiplexes a physical terminal among
several simultaneous processes. The tool prevents SSH downtime and the
running process continues independently of the SSH connection availability.
For more information, see Appendix: Screen command.
2. Select: 2 - Start Up Chassis

3. Select Chassis: Enter the chassis number[1-X] to startup.
4. Select y or n according to the following note: Do you need to synchronize
the hard disk of the new chassis?[y/n]
Note:
Disk synchronization is applicable only for BCN modules 1 and 2. It is not
relevant for BCN modules 3 to 8.
Note:
Mirroring is ready when all partitions are Primary/Secondary
The mirroring takes about 30 to 40 minutes.
5. Confirm settings to proceed.
Step example
# zchassis_ex

0 - Exit
--------------------------------------------------------------------------------
Enter the chassis number[1-4] to startup.
--------------------------------------------------------------------------------
Do you need to synchronize the hard disk of the new chassis?[y/n]
(Default is yes):
--------------------------------------------------------------------------------
Startup Operation Summary
Startup chassis : chassis-2
Synchronize hard disk of the new chassis: Yes
--------------------------------------------------------------------------------
Are you sure to proceed[y/n]y
<<<INFO>>> Wait for synchronizing the disk drive for the node
<<<INFO>>> Power off node CFPU-1
<<<INFO>>> Power on node CFPU-1
<<<INFO>>> Reset node CFPU-1
<<<INFO>>> Wait to enter into initializing state
<<<INFO>>> Disable Watch dog
<<<INFO>>> Initialise hardware(30~60 minutes)
<<<INFO>>> Wait for CFPU-1 to restart and synchronize the disk drive. This will take a few minutes.
<<<INFO>>> Synchronize the disk drive for node CFPU-1................Done!
<<<INFO>>> Power on nodes: CFPU-1 EIPU-3 USPU-5 USPU-3 CSPU-3 EIPU-1 USPU-1 CSPU-1 Done!
<<<INFO>>> Unlock nodes: CFPU-1 EIPU-3 USPU-5 USPU-3 CSPU-3 EIPU-1 USPU-1 CSPU-1 Done!
<<<INFO>>> Wait for enabling CMF on node CFPU-1 .
<<<INFO>>> CMF node CFPU-1 start up Done!
<<<INFO>>> Wait for chassis to start up, timeout value is 15(mins)
<<<INFO>>> Chassis-2 startup Done!
<<<INFO>>> Startup chassiss Done! Total time : 4382.0 sec

<<<INFO>>> Alarm History :/var/log/SS_ChassisMT/20170731/RNC-1001_chassis-02_StartUpAlarmHistory_1606.log
<<<INFO>>> StartUp Report :/var/log/SS_ChassisMT/20170731/RNC-1001_chassis-02_StartupReport_1606.log
7 Verify the system.
Use the following commands:

1. # cat /proc/drbd
2. show has summary
3. show alarm active-summary
4. show has functional-unit unit-info show-mode verbose
5. show cmf status node-name /CFPU-0
7. show radio-network wcelstatus blocked
1.2.1 Preparing LMP in BCN modules
This section provides steps to prepare LMP in a specific BCN module and
configuration.
1.2.1.1 Preparing LMP in BCN module

1 in S3-B2 configuration
Follow these instructions in replacing the BCN module 1 in S3-B2 configuration.

If replacing another module or configuration, use the instructions for that
combination.
Purpose

Figure 1: BCN module 1 in S3-B2
Before you start

Ensure that the following tasks are completed:
1. Remove the BCN module from the running system.
2. Follow the steps in Installing the new BCN module from step 1 (inserting the new BCN
module in the rack) to step 4 (preparing the replacement BCN module), upto running
the nokia_set_factory_default.sh script and restart the box controller node
(BCN) module.
Procedure
1 Log in to the CFPU through a normal O&M connection.
In this case, CFPU- 1 because BCN module 1 which contains CFPU-0 is being replaced.
2 Switch to root account.
set user
Note:
Log in with the root user password.
3 Copy the bcninit directory content to the LMP on CFPU-1.

scp /opt/nokiasiemens/SS_QNTools/bcninit/bcninit.*
root@lmp-1-3-1:/opt/bcntools
4 Log in to LMP-1-3-1.
ssh root@lmp-1-3-1
5 Write down the NE ID.
mch_cli GetNetworkElementId
6 Add the temporary ethernet address to the LMP eth0 port.
ifconfig eth0:2 10.10.10.13 up mtu 1500 netmask 255.255.255.0
7 Take the SSH connection from the LMP to the new BCN module LMP.
ssh root@10.10.10.10
8 Go to the /opt/bcntools directory.
cd /opt/bcntools
9 Copy the bcninit directory content to the new LMP.
scp root@10.10.10.13:/opt/bcntools/bcninit.* ./
10 Untar the bcninit.tgz package.

tar -zxf bcninit.tgz
11 Go to the new bcninit directory.

cd /opt/bcntools/bcninit
12 Run the node.sh script. Give the eleven-character NE ID as parameter to the

script.
./node.sh 1 BMPP2-B <NetworkElementID>
13 Set the LMP date and time.

For more information, see 2.4.2 Setting the LMP date of Commissioning Multicontroller
RNC HW Rel.2.
14 Reset the BCN module under preparation.
mch_cli Reset BCN
Note:
SSH connection to BCN module under preparation is broken after giving this
command because MGT port IP address changes to a proper one and it is no
longer 10.10.10.10.
15 Exit from LMP-1-3-1 to the bash shell (root) in CFPU-1.

Follow these instructions to replace the BCN module 2 in S3-B2 configuration. If

replacing another module or configuration, use the instructions specific for that
combination.
Purpose

Before you start

the nokia_set_factory_default.sh script and restarting the box controller node
(BCN) module.
Procedure
In this case, CFPU-0 because BCN module 2 which contains CFPU-1 is being replaced.
set user
Note:

ssh root@lmp-1-4-1
6 Add the temporary Ethernet address to the LMP eth0 port.
ssh root@10.10.10.10
8 Go to the /opt/bcntools directory.
cd /opt/bcntools



script.


RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.


combination.
Purpose

Before you start

(BCN) module.
Procedure
Login takes place in the CFPU node that hosts the active SSH server.
set user
Note:
3 Copy the bcninit directory content to the LMP on the logged in CFPU node.

ssh root@lmp-1-1-1
ssh root@10.10.10.10
8 Go to /opt/bcntools directory.
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.
15 Exit from LMP-1-1-1 to the bash shell (root) in the CFPU node that hosts the
active SSH server.


combination.
Purpose

Before you start

(BCN) module.
Procedure
set user
Note:

ssh root@lmp-1-2-1
ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.
active SSH server.


combination.
Purpose

Before you start


(BCN) module.
Procedure
In this case, CFPU- 1 because BCN module 1 which contains CFPU-0 is being replaced.
set user
Note:
ssh root@lmp-1-5-1

ssh root@10.10.10.10
cd /opt/bcntools

tar -zxf bcninit.tgz -C /opt/bcntools


script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.



combination.
Purpose

Before you start


(BCN) module.
Procedure
In this case, CFPU-0 because BCN module 2 which contains CFPU-1 is being replaced.
set user
Note:
ssh root@lmp-1-6-1

ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.



combination.
Purpose

Before you start


(BCN) module.
Procedure
set user
Note:

ssh root@lmp-1-7-1

ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.

active SSH server.


combination.
Purpose

Before you start


(BCN) module.
Procedure
set user
Note:

ssh root@lmp-1-8-1

ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.

active SSH server.


combination.
Purpose

Before you start


(BCN) module.
Procedure
set user
Note:
ssh root@lmp-1-1-1

ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.

active SSH server.


combination.
Purpose

Before you start


(BCN) module.
Procedure
set user
Note:
ssh root@lmp-1-2-1

ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.

active SSH server.


combination.
Purpose

Before you start


(BCN) module.
Procedure
set user
Note:
ssh root@lmp-1-3-1

ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.

active SSH server.


combination.
Purpose

Before you start


(BCN) module.
Procedure
set user
Note:
ssh root@lmp-1-4-1

ssh root@10.10.10.10
cd /opt/bcntools



script.

RNC HW Rel.2.
mch_cli Reset BCN
Note:
longer 10.10.10.10.

active SSH server.

2. Replacing an add-in card
Replacing an add-in card requires general steps to be performed.
Before you start

To replace the add-in card you must perform the following main steps:
1. Identify the BCN module in which the add-in card to be replaced is located.
4. Uninstall the add-in card.
5. Remove the DIMM memories from the add-in card.
6. Insert the DIMM memories to the new add-in card.
7. Install the new add-in card to the BCN module.
8. Install the BCN module.
9. Activate the BCN module.
Note:
There are two instances in which DIMM memories need to be replaced:
A faulty add-in card has been discovered. DIMM memories are not included when
ordering add-in cards from Nokia. The DIMM memories would need to be removed
from the faulty add-in card and installed in the new add-in card.
Generally, an add-in card memory diagnostic test (HW-DDR2) cannot locate the
failure of one or multiple DIMMs. The test only knows the memory address where
the read value is not same as the write value. The failure can be either in the
add-in card address or in the memory buses. Replace the add-in card and all of its
DIMMs.
For more information on DIMM memory, see BCN Hardware Jumper Settings and
DIMM Configurations.
Power off the BCN module before removing or installing an add-in card.

CAUTION!
Electrostatic discharge (ESD) damages components in the module or other

units.
Wear an ESD wrist strap or use a corresponding method when handling the units,
and do not touch the connector surfaces.
2.1 Removing an add-in card
This chapter provides the steps to remove an add-in card.
Procedure
1 Identify the BCN module in which the add-in card to be replaced is located.
2 Connect to CFPU node through the O&M network of the customer.
3 Create Fallback build.

4 Check if the SSH service is impacted by the add-in card replacement.
If the add-in card to be replaced is located in module-1 or module-2, find out with the
following SCLI command the CFPU node, in which the active instance of the
FSSSHServer recovery unit is located:
Step result


PROCEDURAL DYNAMIC

RESOURCE_LEVEL=100
RESOURCE_LEVEL=100
FSSSHServer recovery unit is active in the BCN module that contains the add-in card
to be replaced, execute a switchover of the SSH recovery group by entering the
following SCLI command:

chassiss?[y/n]
Step example
# zchassis_ex

0 - Exit
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
(Default is yes):
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Power off node: YES

Power off LMP: NO
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

6 Disconnect all the cables connected to the chassis, executing the following
steps:
1. Switch off the circuit breaker on the PDU for the BCN module in question.
4. Disconnect the mcRNC grounding cable.
6. Uninstall the cable tray with attached network cables from the BCN module. The
cable tray is uninstalled by unscrewing the two thumbscrews fixing the cable tray
to the BCN module. If the screws are too tight to be opened by hand, loosening the
screws that fix the BCN module mounting flanges to the cabinet should help. For
more information about detaching the cable tray, refer to the document Installing
BCN Hardware to CAB216SET-B.
Option Description
If the BCN module is installed in the cabinet,
Then 1. Pull the module out of the cabinet, until it locks into the outmost
position.
2. If there is another BCN module installed immediately above the module
in question, unscrew the two screws attaching the cable tray to the BCN
module immediately above and lift the cable tray upwards. This creates
enough space for the removal of the lower module's top cover.
7 Loosen the thumbscrews of the top cover. Slide the top cover of module
towards the rear side until it stops. Then, lift the top cover upwards.

Figure 13: Removing the BCN module top cover
8 Unscrew the two thumbscrews securing the add-in card to the rails inside
the BCN module.
Figure 14: BCN module add-in card screws
9 Slide the add-in card upwards to remove it from the BCN module.
Figure 15: Pulling an add-in card out from the BCN module
10 Remove DIMM memories, if necessary.

For more information on DIMM memories, see BCN Hardware Jumper Settings and

DIMM Configurations.
2.2 Installing an add-in card
This chapter provides the steps to install an add-in card.
Procedure
1 Install DIMM memories, if necessary.
2 Slide the add-in card into the rails inside the BCN module until the pins of
the card fall into connectors of the main board.
Figure 16: Inserting an add-in card into the BCN module
3 Secure the add-in card to the rails with the built-in thumbscrews.
The Phillips screws are built into the add-in card and can be tightened either by hand
or with a screwdriver.
Figure 17: BCN add-in card screws
4 Place the BCN module cover on the top of the module, leaving small gap
between the top cover and the front edge of the module.

Figure 18: Installing BCN top cover
5 Slide the top cover to the front side of the module, until it locks into place.
6 Tighten the thumbscrews of the top cover.
7 Connect all the cables to the BCN module, by executing the following steps:
1. Install the cable tray with attached network cables back to the BCN module.
For more information about the cable tray installation, see Installing BCN Modules
to the IR206 Cabinet.
2. Connect the BCN module grounding cable.
3. Connect the network cables back to the transceivers on the front side of the
module.
4. Connect the power feed cables.
5. Switch on the circuit breaker on the PDU for the BCNmodule.
6. Wait until all LEDs are red or green.

zchassis_ex

Note:
Since the zchassis_ex operation takes more than 30 minutes to complete,
the SSH could disconnect automatically which breaks the zchassis_ex
operation. Hence, when starting the zchassis_ex script a screen command
(a terminal emulator) is used that multiplexes a physical terminal among
several simultaneous processes. The tool makes the SSH downtime-proof,
thus, more stable because the running process continues independently of
the SSH connection availability.

3. Select Chassis: Enter the chassis number [1-X] to startup.
Note:
Note:
Step example
# zchassis_ex

0 - Exit
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
Do you need to synchronize the hard disk of the new chassis?[y/n]
(Default is yes):
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
<<<INFO>>> Initialise hardware(30~60 minutes)
<<<INFO>>> Wait for CFPU-1 to restart and synchronize the disk drive. This will take a few minutes.
<<<INFO>>> Synchronize the disk drive for node CFPU-1................Done!
<<<INFO>>> Power on nodes: CFPU-1 EIPU-3 USPU-5 USPU-3 CSPU-3 EIPU-1 USPU-1 CSPU-1 Done!
<<<INFO>>> Unlock nodes: CFPU-1 EIPU-3 USPU-5 USPU-3 CSPU-3 EIPU-1 USPU-1 CSPU-1 Done!
<<<INFO>>> Wait for enabling CMF on node CFPU-1 .
<<<INFO>>> Wait for chassis to start up, timeout value is 15(mins)

<<<INFO>>> Alarm History :/var/log/SS_ChassisMT/20170731/RNC-1001_chassis-02_StartUpAlarmHistory_1606.log
<<<INFO>>> StartUp Report :/var/log/SS_ChassisMT/20170731/RNC-1001_chassis-02_StartupReport_1606.log
9 Check hat the eSW of the replaced add-in card is on supported level.
Log in to LMP and check the eSW version info using the following command:
sw_fw_versioninfo
If active bank eSW is on the supported level, continue to the next step. Only active
banks are displayed. To also show backup banks, run the following SCLI command:
show sw-manage embedded-sw version all
If the active bank eSW is not on the supported level, update by performing the
!
This needs to be performed twice because of the backup bank.
set sw-manage embedded-sw upgrade fru-location <fru-location> all
If the command is not successful then use the offline Upgrade with FEWS described in
Appendix 2: Upgrading embedded software of Commissioning Multicontroller RNC HW
Rel.2.
Note:
In case of eSW upgrade issues, the replacement unit can be faulty.
Therefore, it is highly recommended that two add-in cards are available when
add-in card replacement procedure is conducted.
It is important to keep the spare add-in cards in a storage with a new enough
eSW version, to avoid eSW incompatibility issues when the add-in card is
considered to use.
10 Lock and set up the replaced add-in card to test–state.

set has lock managed-object /<processing unit>

set has test-state on managed-object /<processing unit>
Note:
Locking the external interface processing unit (EIPU) node can lead to a restart
of this node (due to internal reasons, which is a normal behavior), failure in the
non-intrusive subtest during node start-up, and three to five minutes waiting
time for diagnostics to be ready.
11 Start hardware diagnostic test for the replacement add-in card group test
group-all.
To start a hardware diagnostic test, enter the following command:
start hardware diagnostics fru-location <fru location> test

group-all report-name <report name> [blocking <true|false>]
The following test result is displayed:
[SUMMARY] subtest-cpu-io: OK.

+++++++++++++++++++++++++++++++++++++++++++++++++++
[RESULT] subtest-cpu-io: OK.
+++++++++++++++++++++++++++++++++++++++++++++++++++
Use the following command to display the test results:
show hardware diagnostics report-details report-name <report-

name>
If Failed in the test execution phase message is received, see Failure in the
test execution phase. For all other errors, contact Nokia Technical Support.
12 Take the add-in card into use by removing it from the test-state, and then
unlock the add-in card back to operational.
set has test-state off managed-object /<processing unit>
set has unlock managed-object /<processing unit>

Note:
After software upgrade, do not run the intrusive diagnostics for either of the
CFPU nodes before the new software has been accepted (that is, before the
normalization has been conducted). This is to avoid triggering auto-return
because of the excessive number of node restarts, which the diagnostics might
invoke.
13 Verify the system by executing the following commands.

1. # cat /proc/drbd
2. show has summary

3. Replacing the SO-DIMM on

motherboard
This chapter provides the steps to replace the SO-DIMM on motherboard.
Before you start

To replace the SO-DIMM memory module you must execute the following main steps:
1. Identify in which BCN module the SO-DIMM memory module to be replaced is located.
4. Uninstall the add-in cards from slots 7 and 8.
5. Remove the SO-DIMM memory module to be replaced from the motherboard.
6. Insert the new SO-DIMM memory module on to the motherboard.
7. Install the removed add-in cards back to their original location to the slots 7 and 8 in
the BCN module.
8. Install the BCN module.
9. Activate the BCN module.
Note:
The DIMM memory needs to be replaced when a faulty SO-DIMM memory module
has been discovered.
SO-DIMM memory module identification details
The following table lists the Identification details of the SO-DIMM memory module:
Table 1: SO-DIMM memory module identification details
C113202 MUS2A01 BCN SO-DIMM Memory Module 1GB
Power off the BCN module before removing or installing an add-in card.

CAUTION!

units.
3.1 Removing add-in cards from slots

7 and 8
Before you start
WARNING!
Risk of physical injury and equipment damage
Only one BCN module is allowed to be pulled out from the cabinet at one time.
Procedure
1 Identify which BCN module needs the replacement SO-DIMM.
2 Connect to CFPU node through the O&M network of the customer.
3 Create Fallback build.

4 Check if the SSH service is impacted by the SO-DIMM replacement.
If the SO-DIMM to be replaced is located in module-1 or module-2, find out with the
following SCLI command the CFPU node, in which the active instance of the
FSSSHServer recovery unit is located:

Step result

PROCEDURAL DYNAMIC

RESOURCE_LEVEL=100
RESOURCE_LEVEL=100
FSSSHServer recovery unit is active in the BCN module that contains the SO-DIMM to
be replaced, execute a switchover of the SSH recovery group by entering the

chassiss?[y/n]
Step example
# zchassis_ex

0 - Exit
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
(Default is yes):
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

Power off node: YES
Power off LMP: NO
--------------------------------------------------------------------------------
--------------------------------------------------------------------------------

6 Disconnect all the cables connected to the chassis, by executing the

following steps:
1. Switch off the circuit breaker on the PDU for the BCN module.
4. Disconnect the BCN grounding cable.
6. Uninstall the cable tray with attached network cables from the BCN module.
Note:
The cable tray is uninstalled by unscrewing the two thumbscrews fixing the
cable tray to the BCN module. If the screws are too tight to be opened by
hand, loosening the screws that fix the BCN module mounting flanges to the
cabinet could help. For more information about detaching the cable tray,
refer to the document Installing BCN Hardware to CAB216SET-B.
Option Description
If the BCN module is installed in the cabinet:
Then 1. Pull the module out of the cabinet, until it locks into the outmost
position.
2. If there is another BCN module installed immediately above the module
in question, unscrew the two screws attaching the cable tray to the BCN
module immediately above and lift the cable tray upwards. This creates
enough space for the removal of the lower module's top cover.
7 Loosen the thumbscrews of the top cover. Slide the top cover of module
towards the rear side until it stops. Then, lift the top cover upwards.

Figure 19: Removing the BCN module top cover
8 Unscrew the two thumbscrews securing the add-in card in slot 7 and 8 to
the rails inside the BCN module.
Figure 20: BCN module add-in card screws
9 Slide the add-in card in slot 8 upwards to remove it from the BCN module.
10 Slide the add-in card in slot 7 upwards to remove it from the BCN module.

3.2 Removing SO-DIMM memory

module
This sections describes removing the SO-DIMM memory module.
Procedure
1 Locate the SO-DIMM memory module on the motherboard of the BNC
module.
Figure 23: SO-DIMM memory module

2 Bend the locking springs on both sides of the SO-DIMM outwards so that the
SO-DIMM springs up.

Figure 24: Removing SO-DIMM memory module
Figure 25: SO-DIMM sprung up

97
Remove the SO-DIMM by pulling it out from the socket.

3

Figure 26: Pulling out the SO-DIMM memory module
98
99
Figure 27: SO-DIMM memory module removed
3.3 Installing SO-DIMM memory

module
This sections describes installing the SO-DIMM memory module.
Procedure
1 Install the new SO-DIMM to its socket in about 30 degrees angle to the
motherboard.
Figure 28: Installing a new SO-DIMM memory module

101
Figure 29: Installing a new SO-DIMM memory module in socket
2 Push SO-DIMM down from the upper corner until it locks from both sides in
horizontal position.

103
Figure 30: Locking the new SO-DIMM memory module
3.4 Installing removed add-in cards

back to slots 7 and 8
This chapter provides the steps to install removed add-in cards back to slots 7
and 8.
Procedure
1 Slide the add-in card to the slot 7 into the rails inside the BCN module until
the pins of the card fall into connectors of the main board.
2 Slide the add-in card to the slot 8 into the rails inside the BCN module until
the pins of the card fall into connectors of the main board.
3 Secure the add-in cards in slots 7 and 8 to the rails with the built-in
thumbscrews.
The Phillips screws are built into the add-in card and can be tightened either by hand

Figure 33: BCN add-in card screws
4 Place the BCN module’s cover on the top of the module, leaving small gap
between the top cover and the front edge of the module.
Figure 34: Installing BCN module top cover
4 Slide the top cover to the front side of the module, until it locks into place.
4 Tighten the thumbscrews of the top cover.
4 Connect all the cables to the BCN module, by executing the following steps:
1. Install the cable tray with attached network cables back to the BCN module.
Note:
For more information about the cable tray installation, check the document
Installing BCN Modules to the IR206 Cabinet.
2. Connect the BCN module grounding cable.

3. Connect the network cables back to the transceivers on the front side of the

module.
4. Connect the power feed cables.
5. Switch on the circuit breaker on the PDU for the BCN module.
6. Wait until all LEDs are red or green.

zchassis_ex
Note:
Since the zchassis_ex operation takes more than 30 minutes to complete,
the SSH could disconnect automatically which breaks the zchassis_ex
operation. Hence, when starting the zchassis_ex script a screen command
(a terminal emulator) is used that multiplexes a physical terminal among
several simultaneous processes. The tool makes the SSH downtime-proof,
thus, more stable because the running process continues independently of
the SSH connection availability.

3. Select Chassis: Enter the chassis number [1-X] to startup.
Note:
Note:

Step example
# zchassis_ex

0 - Exit
---------------------------------------------------------------
-----------------
---------------------------------------------------------------
-----------------
Do you need to synchronize the hard disk of the new
chassis?[y/n]
(Default is yes):y
---------------------------------------------------------------
-----------------
---------------------------------------------------------------
-----------------
<<<INFO>>> Initialise hardware

<<<INFO>>> Wait for CFPU-1 to restart and synchronize the disk

drive. This will take a few minutes.
<<<INFO>>> Synchronize the disk drive for node
CFPU-1................
Done!
<<<INFO>>> Power on nodes: CFPU-1 EIPU-3 USPU-5 USPU-3 CSPU-3
EIPU-1 USPU-1 CSPU-1 Done!
<<<INFO>>> Unlock nodes: CFPU-1 EIPU-3 USPU-5 USPU-3 CSPU-3
EIPU-1 USPU-1 CSPU-1 Done!
<<<INFO>>> Wait for enabling CMF on node CFPU-1
<<<INFO>>> Wait for chassis to start up, timeout value is
15(mins)
<<<INFO>>> Time elapsed: 30 secs

<<<INFO>>> Startup nodes:
<<<INFO>>> Alarm History

:/var/log/SS_ChassisMT/20140731/RNC-141_chassis-02_StartUpAlarm
History_1331.log
<<<INFO>>> StartUp Report
:/var/log/SS_ChassisMT/20140731/RNC-141_chassis-02_StartupRepor
t_1331.log
[root@CFPU-0(RNC-141) /var/log/esw/2014-
Jul-31-12-46/chassis-1motherboard-1_39538]
4 Verify the system by executing the following commands.
1. # cat /proc/drbd
2. show has summary

4. Replacing the system hard disk
The procedures are outlined for replacing the system hard disk. If there are two
disks in the BCN module, it is necessary to determine first that the faulty HDD is
the system disk.
Purpose
The main steps to replace the HDD are the following:
1. Identify in which BCN module the HDD to be replaced is located.
2. If there are two disks in the BCN module, identify first if the system disk is faulty by
using the following command:
show hardware state system-disk
The output of the command lists the active alarms related to the disk in addition to its
physical location. To ensure that the system disk is faulty and is in need of
replacement, see the documentation of the alarms listed in the command output. For
example, the new alarms 70454 IMPENDING HARD DISK FAILURE and 70455 HDD
TEMPERATURE EXCEEDED introduced in BCN lead to disk replacement.
Note:
There are two disks in the BCN module if a disaster recovery disk is in use in the
mcRNC. To check if the DRD is faulty, follow the steps in Replacing the disaster
recovery hard disk.
3. Shut down the CFPU node in the BCN module where the HDD to be replaced is located.
4. Remove the AMC from the AMC bay.
5. Uninstall the faulty HDD.
6. Install the new HDD.
7. Insert the AMC to the AMC bay.
8. Activate the CFPU with the new HDD.
Before you start

CAUTION!
Electrostatic discharge (ESD) may damage components in the module or

other units.
The HDSAM-A supports both SAS and serial advanced technology attachment (SATA) HDDs
and includes a SAS or SATA switch for selecting the disk type. BCN platform supports only
SAS HDDs, thus, always check that the switch is set to SAS before starting the
replacement procedure.
Figure 35: The SAS/SATA switch in the HDSAM-A
4.1 Removing the AMC from BCN

module
This chapter provides the steps in removing the AMC from BCN module.
Procedure
1 Identify in which BCN module the HDD to be replaced is located.
2 Log into the CFPU node where the HDD is NOT faulty.
3 Create Fallback build, by executing the following command:

4 Prepare BCN module with the HDD to be replaced.
1. Lock the CFPU node where the HDD is located.

set has lock force managed-object /CFPU-<x>
2. Power off the node where the faulty HDD is located.
set has power off managed-object /CFPU-<x>
5 Gently pull the hot swap handle on the front panel of the AMC.
Do not pull the handle out all the way yet. Pulling the handle notifies the hardware
management system that you are going to remove the AMC and tells it to finish all
processes.
The hot swap LED starts flashing.
Figure 36: Pulling the hot swap handle of an AMC
6 Wait until the hot swap LED turns into a solid blue.
This may take a few seconds.
7 Pull the hot swap handle again more firmly and slide the AMC out of the bay.
Figure 37: Removing an AMC from the BCN module
8 If you are not installing another AMC immediately, install an AMC filler into
the empty AMC bay.

This is to ensure adequate cooling and a proper EMC shield in the module.
4.2 Removing the faulty HDD from

AMC
This chapter provides the steps to remove the faulty HDD from AMC.
Procedure
1 Place the AMC so that the faulty HDD side is facing down. Unscrew the four
screws on the metal bracket of the AMC module, then turn the module over
carefully while holding the HDD.
2 Disconnect the faulty HDD.
Detach the faulty HDD from the connector by pulling it gently (from right to left as
shown in the following figure).
Figure 38: HDD on HDSAM-A
4.3 Installing the new HDD on AMC
This chapter provides the steps to install the new HDD on AMC.
Procedure
1 Connect the new HDD to the SAS connector of HDSAM-A.

Connect the new HDD to the SAS connector in the HDSAM-A by pushing it gently (from
left to right as shown in the following figure).
Figure 39: Installing the HDD on HDSAM-A
2 Turn the AMC over and attach the new HDD to the AMC with four screws.
Tighten the screws so that their heads are in line with the metal bracket.
4.4 Installing the AMC back to BCN

module
This chapter provides the steps to install the AMC back to BCN module.
Procedure
1 Check that the EMC gasket is correctly in place and that its contacts are
clean.
2 Insert the AMC into the bay, sliding it along the guide rails.
Ensure that the AMC is firmly seated in the connectors of the module.

Figure 40: Inserting an AMC into the BCN module
3 Press the hot swap handle firmly.
Wait until the blue hot swap LED turns off and the power LED turns solid green.
Figure 41: Pressing the hot swap handle
4.5 Enabling the new HDD
This chapter provides the steps to enable the new HDD.
Procedure
1 Enable the network boot for the CFPU node with the new HDD, by executing
the following steps:
1. Log in as root by using the following command:

set user username root
2. Power on the node using the following command:
hwcli -np on <node_name>
Wait a few seconds before proceeding to the next step.
3. Reset the node using the following command:

hwcli -nr -B 3 <node_name>

4. Exit root using the following command:
exit
Note:
The CFPU node takes some time to reboot and the availability can be checked
by logging through the SSH.
Step example
Log in as root and power on the node:

hwcli -np on CFPU-1
Powering on CFPU-1 [ok]
Reset the node:
hwcli -nr -B 3 CFPU-1
Resetting CFPU-1 [ok]
2 Enable INERT mode for the CFPU node, by executing the following command:
set has inert on managed-object <node-name>
Step example
set has inert on managed-object /CFPU-1
3 Initialize the new HDD from the other CFPU node where the HDD is not

faulty.
To initialize the new disk, use the following SCLI command:
initialise hw
Hardware successfully initialized
Note:
To run the initialization script and display the console output, the space bar
must be pressed several times after entering the command. The initialization of
the new HDD might take an hour.
4 Disable INERT mode for the CFPU node by executing the following command:
set has inert off managed-object <node-name>
Step example
set has inert off managed-object /CFPU-1
5 Reboot the CFPU node with the new HDD from the local HDD.

hwcli -nr -B 2 <node_name>
exit
The node restarts and synchronizes the DRBD. Enter watch -n 10 cat
/proc/drbd to see how the synchronization is progressing. However, if watch -n
10 cat /proc/drbd fails, cat /proc/drbd must be executed.

Note:
Set user username root command tag first before execution of following
command:
watch -n 10 cat /proc/drbd
Do not restart the node during the DRBD synchronization. The initialization process of
the new disk is not ready until the synchronization is successfully completed.
Step example
The following commands are entered:

hwcli -nr -B 2 CFPU-1
exit
Resetting CFPU-1 [ok]
The following example shows that the first blocks are already synchronized. The oos
value is zero. For block 3, the synchronization is in process and the progress is
displayed. Once the synchronization is complete, the oos value for all blocks will be 0.

# watch -n 10 cat /proc/drbd
Every 10.0s: cat /proc/drbd Wed Apr 24 10:54:39 2013
version: 8.3.7 (api:88/proto:86-92)
srcversion: 35B9BF7C501212268498452
3: cs:SyncSource ro:Primary/Secondary ds:UpToDate/Inconsistent C r----
[==>.................] sync'ed: 18.9% (12176/14996)M
finish: 0:05:37 speed: 36,872 (30,744) K/sec
6 Check that the serving and backup Cluster Management Functionality (CMF)
are working normally.
show cmf status recovery-unit node-name <mo-name>
Compare the blocks. The blocks should match for both managed objects.

Step example
_nokadmin@CFPU-0 [RNC-37] > show cmf status recovery-unit node-name /CFPU-1
CFPU-0@RNC-37 [2013-04-24 13:18:51 +0200]
Recovery units with DRBD resources for managed object /CFPU-1:
/CFPU-1/FSDirectoryServer: 1/1 (peer[s]/drbd device[s] up)
/dev/drbd1: DRBD_SECONDARY 1/0 (peer/wait secondary)
/CFPU-1/FSAlarmSystemLightServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/QNOMUServer-1: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/FSPM9Server: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/FSClusterStateServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/FSLogServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/FSSSHServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/QNEMServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/FSCLMServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-1/FSHotSwapMonitorServer: 1/1 (peer[s]/drbd device[s] up)
_nokadmin@CFPU-0 [RNC-37] > show cmf status recovery-unit node-name /CFPU-0
CFPU-0@RNC-37 [2013-04-24 13:18:55 +0200]
Recovery units with DRBD resources for managed object /CFPU-0:
/CFPU-0/FSPM9Server: 1/1 (peer[s]/drbd device[s] up)
/dev/drbd8: DRBD_PRIMARY 1/0 (peer/wait secondary)
/CFPU-0/FSClusterStateServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-0/FSLogServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-0/FSSSHServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-0/QNEMServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-0/FSCLMServer: 1/1 (peer[s]/drbd device[s] up)

/CFPU-0/FSHotSwapMonitorServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-0/FSAlarmSystemLightServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-0/FSDirectoryServer: 1/1 (peer[s]/drbd device[s] up)
/CFPU-0/QNOMUServer-0: 1/1 (peer[s]/drbd device[s] up)
7 Unlock the node with the new HDD, by executing the following command:
set has unlock managed-object <mo-name>
Step example
The following command is used:
set has unlock managed-object /CFPU-1
/CFPU-1 unlocked successfully.

5. Replacing the disaster recovery

hard disk
The procedures are outlined for replacing the disaster recovery hard disk. If
there are two disks in the BCN module, it is necessary to determine first that
the faulty HDD is the DRD.
Purpose
When there are two disks in the BCN module, the following are the possible scenarios:
1. If one system disk becomes faulty, this system disk is changed and initialized following
the instructions in Replacing the system hard disk.
2. If both system disks become faulty simultaneously, the DRDs are physically switched
with the system disks. For detailed instructions, see the Manual switching of system
disk and recovery disk at the site section of RAN3368: mcRNC Disaster Recovery Using
Redundant Hard Disks.
3. If one DRD becomes faulty, this DRD is replaced with a new one after which a DRD
backup is created in total mode. In this case, the CFPU node does not need to be locked
and powered off (the DRD can be hot-plugged).
a. Identify first if the DRD is faulty by using the following command:
show hardware state recovery-disk
The output of the command lists the active alarms related to the disk in addition to
its physical location. To ensure that the DRD is faulty and is in need of replacement,
see the documentation of the alarms listed in the command output. For example, the
new alarms 70454 IMPENDING HARD DISK FAILURE and 70455 HDD
TEMPERATURE EXCEEDED introduced in mcRNC lead to disk replacement.
b. Follow the subsequent steps outlined in replacing the DRD.
4. If both DRDs become faulty simultaneously, both DRDs are replaced with new ones
after which a DRD backup is created in total mode. In this case, the CFPU nodes do not
need to be locked and powered off (the DRDs can be hot-plugged).
a. Identify first if the DRD is faulty by using the following command:
show hardware state recovery-disk
The output of the command lists the active alarms related to the disk in addition to

its physical location. To ensure that the DRD is faulty and is in need of replacement,
see the documentation of the alarms listed in the command output.
b. Follow the subsequent steps outlined in replacing the DRD.
Before you start
CAUTION!
Electrostatic discharge (ESD) may damage components in the module or

other units.
The HDSAM-A supports both SAS and serial advanced technology attachment (SATA) HDDs
and includes a SAS or SATA switch for selecting the disk type. BCN platform supports only
SAS HDDs, thus, always check that the switch is set to SAS before starting the
replacement procedure.
Figure 42: The SAS/SATA switch in the HDSAM-A
5.1 Removing the AMC from BCN

module
This chapter provides the steps to remove the AMC from the BCN module.

Procedure
1 Gently pull the hot swap handle on the front panel of the AMC.
Do not pull the handle out all the way yet. Pulling the handle notifies the hardware
management system that you are going to remove the AMC and tells it to finish all
processes.
The hot swap LED starts flashing.
Figure 43: Pulling the hot swap handle of an AMC
2 Wait until the hot swap LED turns into a solid blue.
This might take a few seconds.
3 Pull the hot swap handle again more firmly and slide the AMC out of the bay.
Figure 44: Removing an AMC from the BCN module
4 If you are not installing another AMC immediately, install an AMC filler into
the empty AMC bay.
This is to ensure adequate cooling and proper EMC shield in the module.

5.2 Removing the faulty HDD from

AMC
This chapter provides the steps to remove the faulty HDD from AMC.
Procedure
1 Place the AMC so that the faulty HDD side is facing down. Unscrew the four
screws on the metal bracket of the AMC module, then turn the module over
carefully while holding the HDD.
2 Disconnect the faulty HDD.
Detach the faulty HDD from the connector by pulling it gently (from right to left as
shown in the following figure).
Figure 45: HDD on HDSAM-A
5.3 Installing the new HDD on AMC
This chapter provides the steps to install the new HDD on AMC.
Procedure
1 Connect the new HDD to the SAS connector of HDSAM-A by pushing it gently
(from left to right as shown in the following figure).

Figure 46: Installing the HDD on HDSAM-A
2 Turn the AMC over and attach the new HDD to the AMC with four screws.
Tighten the screws so that their heads are in line with the metal bracket.
5.4 Installing the AMC back to BCN

module
This chapter provides the steps to install the AMC back to BCN module.
Procedure
1 Check that the EMC gasket is correctly in place and that its contacts are
clean.
2 Insert the AMC into the bay, sliding it along the guide rails.
Ensure that the AMC is firmly seated in the connectors of the module.

Figure 47: Inserting an AMC into the BCN module
3 Press the hot swap handle firmly.
Wait until the blue hot swap LED turns off and the power LED turns solid green.
Figure 48: Pressing the hot swap handle
Postrequisites
At this point, the AMC that contains the new HDD (DRD) is in its place in the BCN module.
When there is no faulty DRD in the mcRNC, the backup can be created on the recovery
disk (in total mode) by using the following SCLI command:
start backup recovery-disk backup-mode total

6. Replacing the failed HDDs on both

CFPU nodes
This section describes replacing the failed HDDs on both CFPU nodes.
When delivered with the HDD, the hard disk drive carrier AMC (HDSAM-A) is
already in place. For more information, see Performing quarterly maintenance
routines in Preventive Maintenance in Multicontroller RNC.
If the HDDs are faulty or in need of upgrade or service, they might need to be
replaced. If both disks become faulty simultaneously, the mcRNC will be out of
order. In this case, replace both disks according to the prerequisites and steps
(from 4.1 to 4.4) in Replacing the system hard disk. Afterwards, perform a full
system restore. For more information, see Clean installation in Commissioning
Multicontroller RNC HW Rel.2.

7. Replacing the power distribution

unit (PDU)
This section describes steps to replace the power distribution unit (PDU) if
found faulty.
Purpose
If the PDU is faulty, it must be replaced with a new PDU.
Figure 49: Power distribution units in the cabinet
Before you start

Ensure you have a digital multimeter or voltage meter available.
WARNING!
Danger of hazardous voltages and electric shock!

Before connecting or removing any power supply cables to or from the power
distribution unit, Ensure that both site power feeds to the power distribution unit are
off, the circuit breakers on the front panel of the power distribution unit are in the
OFF position, and the equipment is properly earthed (grounded).

WARNING!
Danger of hazardous voltages and electric shock!

Ensure your hands are dry. Remove any metal objects such as rings before touching
the power supply equipment.
WARNING!
Risk of personal injury.

Observe the given torque ranges at all times. Incorrect torque can result in damage
to equipment, unreliability, and fire hazards due to excessive power dissipation and
high temperature of materials.
7.1 Removing the PDU
This chapter provides the steps to remove the PDU.
Procedure
1 Ensure that the redundant PDU is functional.
2 Switch off the circuit breakers on the PDU you are going to remove.
3 Check the PDU input feeds with a digital multimeter to ensure there are no
voltages in the cables.

Figure 50: Location where the digital multimeter should be placed
4 Disconnect all cables from the PDU.
1. Disconnect the four power feed cables from the PDU.

2. Disconnect the CGNDB grounding cable from the PDU.
3. Disconnect the eight PSU input feeds from the PDU.
!
For the correct location in disconnecting cables from the PDU, see the location
where the digital multimeter should be placed.
5 Unscrew the four fixing screws attaching the PDU to the cabinet.

Figure 51: Replacing a PDU
6 Remove the PDU from the cabinet.
7.2 Installing the PDU
This chapter provides the steps to install the PDU.
Procedure
1 Insert the PDU into the cabinet and align the holes of its mounting ear with
the cabinet mounting rail.
2 Attach the PDU to the cabinet with four M6x12 screws.
Figure 52: Installing PDU to the cabinet
3 Connect the PDU grounding cable (CGNDB) to the PDU.

Figure 53: PDU grounding cable
4 Check the PDU input feeds with a digital multimeter to ensure there is no
voltage in the cables.
5 Connect the site power supply cables to the PDU (for DC power supply only).
1. Remove the nuts from the power terminals with a 10mm socket wrench.Connect
the feeder cable with lug to terminal connector marked -48/-60 VDC IN, and the
return cable with lug to terminal connector marked RTN.
2.
Figure 54: Connecting site power supply cables to the PDU
3. Secure the cable lugs on the terminal connectors with nuts.
6 Connect the eight PSU input feeds to the PDU.
7 Switch on the site power supply to the PDU.
8 Switch on the circuit breakers on the PDU.

8. Replacing a power supply unit
This section describes the steps to replace the power supply unit.
Before you start
CAUTION!

units.
8.1 Removing a power supply unit
This chapter provides the steps to remove a power supply unit.
Procedure
1 Switch off the circuit breaker on the PDU of the power supply unit to be
replaced.
2 Unplug the power cable connected to the power supply unit.
3 Unscrew the two thumbscrews attaching the power supply unit to the BCN.
The Phillips screws are built into the power supply unit and can be loosened either by
hand or with a screwdriver.
4 Pull out the power supply unit from the BCN module.

Figure 55: Removing an AC PSU from the BCN module
Figure 56: Removing a DC PSU from the BCN module
8.2 Installing a power supply unit
This chapter provides the steps to install a power supply unit.
Procedure
1 Insert the power supply unit into the power supply slot at the rear side of
the BCN module so the screws built into the unit are on the right-hand side.
2 Tighten the unit’s thumbscrews.
The Phillips screws are built into the power supply unit and can be tightened either by
hand or with a screwdriver.
3 Plug the power cable to the power supply unit.
4 Attach the cable clamp to the cable.

5 Switch on the circuit breaker on the PDU for the power supply unit which
was replaced.

9. Replacing a fan module
This section describes the steps to replace fan module while the BCN runs.
The fan modules are located at the rear of the BCN module.
Figure 57: BCN fan modules
The following is an alarm example where Fan 4 speed is zero (0.000) and needs
a replacement:
Alarm ID : 19212067 Specific problem : 70302 - FAN SPEED OUT OF

LIMIT Managed object :
fshwModuleId=FT-2,fshwPIUId=piu-1,fshwEquipmentHolderId=chassis-2,fs
hwEquipmentH
olderId=cabinet-1,fsFragmentId=HW,fsClusterId=ClusterRoot Severity :
2 (critical) Cleared : no Clearing : automatic Acknowledged : no
Ack. user ID : N/A Ack. time : N/A Alarm time : 2016-07-15
11:36:36:650 EEST Event type : x3 (environmental) Application :
fshaRecoveryGroupName=HPIMonitor,fsFragmentId=RecoveryGroups,fsFragm
entId=HA,fsC lusterId=ClusterRoot Identif appl. addl. info :
Unit={BMFU-B} Position=/chassis-2/ft-2 Sensor={number=12} Appl.
addl. info : Name=Fan 4,Reading=0.000,Threshold=lnr

Figure 58: Location of the fan to be replaced
Before you start
CAUTION!

units.
Tip:
Prepare the spare fan unit for replacement beforehand. After removing a fan from
the BCN module, the system starts to heat up very quickly. Proceed immediately
with the new fan installation. The procedure in replacing the fan applies to all three
fan modules of the BCN module.

9.1 Removing a fan module
This chapter provides the steps to remove a fan module.
Procedure
1 Unscrew the two thumbscrews attaching the fan module to the BCN.
The Phillips screws are built into the fan module and can be loosened either by hand
2 Pull the fan module out from the BCN module.
9.2 Installing a fan module
This chapter provides the steps to install a fan module in the BCN module.
Procedure
1 Insert the fan module to the fan module slot at the rear side of the BCN
module.
2 Tighten the fan thumbscrews of the module.
The Phillips screws are built into the fan module and can be tightened either by hand

10. Replacing the air filter
This section describes steps to replace the air filter regularly.
Purpose
To prevent dust from accumulating inside the equipment, the filter element must be
replaced twice a year.
Procedure
1 Unscrew the two thumbscrews attaching the air filter cover to the BCN
module.
Figure 59: Unscrewing the two thumbscrews
2 Open the air filter cover and pull out the air filter.
Figure 60: Opening the air filter cover and pulling out the air filter
3 Push the new air filter into the guide rails on both sides of the air filter
cover.
4 Push the air filter cover back and fasten the two thumbscrews.

11. Replacing the BCN installation

support kit BSK216-A
This section describes the steps to replace the BCN installation support kit
BSK216-A.
Before you start

Power off the BCN module before replacing it.
CAUTION!

units.
11.1 Removing the BCN installation

support kit BSK216-A
This chapter describes how to remove the BSK216-A from the cabinet.
▪ Remove BSK216-A and ETSI rear bracket from the cabinet.

Figure 61: Removing BSK216-A from the cabinet
11.2 Installing the new BCN slide rail

BSR216-A
This chapter describes how to install the new BCN slide rail BSR216-A.
▪ Install new BCN slide rail BSR216-A to the cabinet.
Remove BSR216-A transportation screw and ETSI rear bracket. Screw four M6 screws
and washers to cabinet frame. Screw four M6 screws and washers to cabinet ETSI
flange.
Figure 62: Installing BCN slide rail BSR216-A to the cabinet

12. Replacing the BCN installation kit

BIK216-A
This section describes the steps to replace the BCN installation kit BSK216-A.
Before you start

Power off the BCN module before replacing it.
CAUTION!

units.
12.1 Removing the BCN installation kit

BIK216-A
This chapter describes how to remove the BCN module from the cabinet.
Procedure
1 Remove the BCN module from the support brackets and slide it out from the
cabinet.

Figure 63: Sliding the BCN module out from the cabinet
2 Remove the cable tray from the BCN module.
Remove the cable tray from the brackets by unscrewing two M3x0.5 panel screws.
Figure 64: Removing the cable tray from the BCN module
3 Remove the BCN module side brackets (with handle) from the side of the
BCN module.
Unscrew seven Torx M4 screws for each bracket as shown in the figure below.

Figure 65: Removing brackets from the BCN module
12.2 Installing the new BCN

installation kit BSIK216-A
This chapter describes how to install the new BCN module.
Procedure
1 Fix the BCN module side brackets (with handle) to the side of the BCN
module.
Use six Torx M4 screws for each bracket as shown in the figure below.

Figure 66: Fixing brackets to the BCN module
2 Fix the cable tray to the BCN module.
Fix the cable tray to the brackets with two M3x0.5 panel screws.
Figure 67: Fixing the cable tray to the BCN module
3 Place the BCN module on the BCN shelf and slide it into the cabinet.
Before installation, remove the M6 transportation screw and washer from the BCN
shelf. Then, fix the BCN module onto the BCN shelf with two M4x8 torx screws.

Figure 68: Sliding the BCN module into the cabinet
Note:
The BSIK216-A installation kit can be used in CAB216SET-B and CAB216SET-D
cabinet sets.

13. Performing hardware diagnostics
This section describes the steps to perform hardware diagnostic tests.
Hardware diagnostics include the non-intrusive test that is run even when the Field
Replaceable Unit (FRU) is working in normal state, and the intrusive test that is run when
the FRU is offline.
The user can run diagnostic tests on FRU to detect potentially faulty components. It also
allows the user to view all the available tests for a particular FRU and to manage the test
reports.
The hardware diagnostic test can be run from an SCLI session in a blocking or non-
blocking mode. Multiple diagnostic test cases can be executed simultaneously on different
FRUs.
The hardware diagnostic is used to check and verify the hardware modules of a specific
add-in card.
Hardware diagnostic is usually started for installing a new chassis, add-in card, or checking
hardware module related problems.
Hardware diagnostic framework supports the following operations on an FRU:
Getting the available tests

Checking if a particular test can be run on it
Running a test
Checking the status of a test
Managing the test reports

Tip:
If HDSAM-A with HDD (mcRNC AMC) has any HW diagnostic alarm or has a negative
HDD smart health test status, the AMC is faulty. The system does not set any alarm
if the HDD smart health test status is negative, thus, running an AMC HW diagnostic
is recommended.
After HW replacement or installation, an FRU is healthy if:

The HDSAM-A with HDD does not have any active alarm, which can be checked
using the following SCLI command:
show alarm active
The HDD smartctl shows SMART Health Status: OK (no active alarm), which
is checked through HW diagnostic.
13.1 Viewing the hardware diagnostic

tests available for an FRU
This section describes the process of viewing the hardware diagnostic tests. The
hardware diagnostic tool is used to view the diagnostic tests available for an
FRU.
Hardware diagnostic tests can be categorized in two:
detailed test (which is a prefixed subtest such as subtest-cpu-io)
group tests (such as group-all, group-cpu, group-mmc, group-storage, and
group-all-non-intrusive)
The following example shows how to check the mapping relation between fru-
location and node by command:

user007@CFPU-0 [RNC-477] > show hardware inventory list brief
CFPU-0@RNC-477 [2016-08-02 15:43:27 +0300]
Actual Type Unused Node/Host Expected Type Admin-ignore Entity
HDSAM-A N/A HDSAM-A no /chassis-1/AMC-1
BMFU-B N/A BMFU-B no /chassis-1/ft-1
BAFU-A N/A BAFU-A no /chassis-1/ft-3
BCNMB-B LMP-1-1-1 BCNMB-B no /chassis-1/motherboard-1
BAFE-B N/A BAFE-B no /chassis-1/power-supply-1
BMPP2-B CFPU-0,USSR-0 BMPP2-B no /chassis-1/slot-1
BMPP2-B CSPU-0,CSUP-0 BMPP2-B no /chassis-1/slot-2
BMPP2-B USPU-0,USUP-0 BMPP2-B no /chassis-1/slot-3
BMPP2-B EIPU-0,EITP-0 BMPP2-B no /chassis-1/slot-4
HDSAM-A N/A HDSAM-A no /chassis-2/AMC-1
BAFU-A N/A BAFU-A no /chassis-2/ft-3
BCNMB-B LMP-1-2-1 BCNMB-B no /chassis-2/motherboard-1
BMPP2-B CFPU-1,USSR-1 BMPP2-B no /chassis-2/slot-1
After mcRNC4.0 for hardware type BMPP2-B add-in card, DIMI tests are
available.
The following table lists the available DIMI tests available:

Table 2: List of available DIMI tests
Tests Description
subtest-bmc- This is used to perform Board Management Controller (BMC)

availability availability hardware diagnostic through the system interface
for octeon add-in card.
subtest-cpu-info This is used to display processor details.
subtest-cpu-io This is the same as test CPU offline diagnostic.
subtest-cpu-io-non- This is the same as test CPU offline diagnostic but non-
intrusive intrusive.
subtest-edac-test This is used to check for bit errors reported by the Error
Detection And Correction (EDAC) system.
subtest-flash-read This is used to check if reading of the first sector of mtd0

succeeds.
subtest-fru-info This is used to display FRU upgradable components and

versions.
subtest-hdd-info This is used to display detected hard discs and their properties.
subtest-picmg-led This is used to check PCI Industrial Computer Manufacturers

Group (PICMG) LED properties.
subtest-post-test This is used to check power-on self-test (POST) result code from
bootloader.
subtest-sensor-health This is used to check for any asserted threshold based sensor.
subtest-spd-data-info This is used to check SPD (Serial Presence Detect) Data

information.
subtest-tlv-eeprom This is used to check the Type Length Value EEPROM (TLV
EEPROM) for consistency by verifying the checksums.
The following table lists the available group DIMI tests:

Table 3: List of available group DIMI tests
Group Tests Description
group-all This includes all diagnostic items for an add-in card.
group-all-non- This includes all non-intrusive diagnostic items for an add-

intrusive in card.
group-cpu This includes diagnostic group for central processing unit

(CPU) and its IO interface.
group-cpu-non- This includes non-intrusive diagnostic group for CPU and its
intrusive IO interface.
group-mmc This includes diagnostic group for basic hardware.
group-storage This includes diagnostic group for storage devices.
Purpose
Available tests that can be run on a particular FRU are viewed.
Procedure
1 View hardware diagnostic tests.
To view the available diagnostic tests for an FRU (including add-in cards), enter the
following command:
show hardware diagnostics test-list fru-location <fru location>
Alternatively for add-in cards, the available diagnostic tests for an FRU can be viewed
using the node parameter. Enter the following command:
show hardware diagnostics test-list node <node-name>
Note:
The fru-location can only be used for HDD (AMC-1) or motherboard.
Otherwise, both fru-location and node are allowed.
To view the details of a test, enter the following command:
show hardware diagnostics test-details fru-location <fru

location> test <test name>

Alternatively for add-in cards, you can use the node parameter. Enter the following
command:
show hardware diagnostics test-details node <node-name> test

<test name>
Note:
The following table lists the parameters of show hardware diagnostics

command:
Table 4: Parameters of the command for getting the available diagnostic tests
Parameters Description
test-details This parameter shows the details of the specified

hardware diagnostic test.
test-list This parameter shows the list of hardware diagnostic

tests.
fru-location <fru This parameter specifies the location of an FRU.

location>
node <node-name> This parameter specifies the node.
test <test name> This parameter specifies the name of a test.
Step example
To view all the hardware diagnostic tests for /chassis-1/slot-3, enter the
following command:
show hardware diagnostics test-list fru-location

/chassis-1/slot-3
To view the details of the subtest-cpu-io hardware diagnostic test, enter the
following command:
show hardware diagnostics test-details fru-location

/chassis-1/slot-3 test subtest-cpu-io

To view all the hardware diagnostic tests for /chassis-2/motherboard-1, enter

the following command:
show hardware diagnostics test-list fru-location

/chassis-2/motherboard-1
2 Check if a test can be run on a particular FRU.
To check if a test can be run on a particular FRU, enter the following command:
show hardware diagnostics test-details fru-location <fru

Step example
To check if subtest-cpu-io diagnostic test can be run on /chassis-1/slot-3,

enter the following command:
show hardware diagnostics test-details fru-location

13.2 Starting a hardware diagnostic

test
This section describes process to start a hardware diagnostic test.

The hardware diagnostic tool is used to start a hardware diagnostic test for an
FRU.
The diagnostic process is robust enough, but there might be some exceptional
cases. If the hardware diagnostic is interrupted for any reason and the add-in
card might not be powered on, the add-in card needs to be manually reset with
the following SCLI command:
set has power on managed-object name

Purpose
A hardware diagnostic test is started.
Procedure
1 Set the add-in card of the corresponding testing FRU.
Lock the MO using the following:
set has lock managed-object /USPU-0
2 The hardware diagnostics uses the console port and hence the console
monitoring cannot run in parallel on the same port. Lock ConsoleMonitor
recovery group (RG) by executing the following command:
set has lock managed-object /ConsoleMonitor
Step example
> set has lock managed-object /ConsoleMonitor

/ConsoleMonitor locked successfully.
3 Start the hardware diagnostic test.
To start a hardware diagnostic test (including add-in cards), enter the following
command:
start hardware diagnostics fru-location <fru location> test <test

name> report-name <report name> [blocking <true|false>]
Alternatively for add-in cards, the available diagnostic tests for an FRU can be started
start hardware diagnostics node <node-name> test <test name>

report-name <report name> [blocking <true|false>]

Note:
Furthermore, you can start a diagnostic test using the scope parameter by entering
start hardware diagnostics scope subtree-incl-base fru-location

/chassis-1/motherboard-1 test all-non-intrusive
The following table lists the parameters of start hardware diagnostics

command:
Table 5: Parameters of the command for starting a diagnostic test

location>
node <node name> This parameter specifies the node.
scope This parameter specifies the scope of the request.
test <test name> This parameter specifies the name of a test.
report-name <report This parameter specifies the name of a diagnostic

name> test report. The report should be named for easy
management such as the following format:
AddInCardName-DayMonthYear-SequenceID. An
example is the following:
USPU0-010112-01
This parameter is only optional.
blocking <true|false> This parameter specifies the mode in which a

diagnostic outputs information to the shell (for true
or false) and stops user from inputting any command
in the shell until diagnostic is complete (for true
only).
The CPU hardware diagnostic test can be started in two modes:

Non-blocking mode
To start the CPU hardware diagnostic test in a non-blocking mode, enter the
following command:
start hardware diagnostics fru-location /chassis-1/slot-3
test subtest-cpu-io report-name USPU0-010112-01 blocking

false
Blocking mode
To start the CPU hardware diagnostic test in blocking mode, enter the following
command:
start hardware diagnostics fru-location /chassis-1/slot-3
test subtest-cpu-io report-name USPU0-010112-01 blocking true
Note:
When multiple diagnostic tests are started on a target FRU or node and the
state of the hardware changes because of current or previous test execution,
the diagnostic framework does not execute the queued tests on the target FRU
and the tests are canceled by displaying the following message in the report:
FRU at location <...> is not found.
The following message in the report file is an example of multiple hardware

diagnostic tests that are started and have failed report:
root@CFPU-0 [RNC-1005] > show hardware diagnostics report-details report-name cspu-0201610101
CFPU-0@RNC-1005 [2016-10-10 16:32:49 +0800]
Test details:
Test ID : group-all
FRU location : /chassis-1/slot-2
Node name : CSPU-0
Test user name : root
SCLI command : start hardware diagnostics fru-location /chassis-1/slot-2 test group-all
blocking false report-name cspu-0201610101 rpt_12
Test start time : 2016-10-10 16:23:58+08:00
Test end time : 2016-10-10 16:23:58+08:00
Test report name : cspu-0201610101
The FRU at location "/chassis-1/slot-2" is not found.
===================================================
Test summary:
Diagnostics test result : FAILED
Diagnostics test failure reason : Failed to initiate the test as the target FRU is not available.
Failed in the test preparation phase.

If the hardware diagnostic test fails, do the following recovery:

1. Repeat the HW diagnostic test after The FRU at location <...> is
not found. failure.
2. If the failure persists, contact your local customer support.
System can run hwdiag subtest-cpu-io for 16 add-in cards concurrently.
4 Set recovery state of the add-in card after complete HW diagnostic, by using
set has unlock managed-object /USPU-0
5 Unlock the ConsoleMonitor recovery group (RG), by using the following

command:
set has unlock managed-object /ConsoleMonitor
Step example
> set has unlock managed-object /ConsoleMonitor

/ConsoleMonitor unlocked successfully.
13.2.1 Failure in the test execution

phase
This section describes the process involved in failure in the test execution
phase.
There are times when the diagnostic test is started in the node start-up phase when the
HW diagnostic services of the node are not fully ready. This case is normal when the node
has reset. In this situation, the diagnostic subtest in the diagnostic report gives a Failed
in the test execution phase message:

Diagnostics test result : FAILED

Diagnostics test failure reason : 11 out of 12 subtest(s) in the
group failed.
subtest-bmc-availability : Failed
in the test execution phase.
subtest-cpu-info : Failed in the
test execution phase.
subtest-edac-test : Failed in the
subtest-flash-read : Failed in
the test execution phase.
subtest-fru-info : Failed in the
subtest-hdd-info : Failed in the
subtest-picmg-led : Failed in the
subtest-post-test : Failed in the
subtest-sensor-health : Failed in
subtest-spd-data-info : Failed in
subtest-tlv-eeprom : Failed in
Whenever the node restarts, HWDIAGMAN receives the event

SAHPI_RESE_RESOURCE_REMOVED which means that some DIMI tests (such as subtest-
cpu-info, subtest-edac-test, subtest-spd-data-info, and subtest-flash-read) are not anymore
valid.
Once HWDIAGMAN receives the event SAHPI_RESE_RESOURCE_ADDED after successful

execution, functionalities of some DIMI tests (such as subtest-cpu-info, subtest-edac-test,
subtest-spd-data-info, and subtest-flash-read) already start to work and the HW diagnostic
service is ready for use. If SAHPI_RESE_RESOURCE_ADDED is not received, these DIMI
tests fail.

Note:
Locking the external interface processing unit (EIPU) node might lead to a restart
(due to internal reasons, which is a normal behavior), failure in the non-intrusive
subtest during node start-up, and three to five minutes waiting time for diagnostics
to be ready.
13.3 Viewing the status of a hardware

diagnostic test
This process describes viewing the status of a hardware diagnostic test. The
hardware diagnostic tool is used to view the status of a hardware diagnostic
test for an FRU.
Purpose
The status of a hardware diagnostic test is viewed.
▪ View an ongoing test status, by executing the following command:
show hardware diagnostics report-status fru-location <fru

Alternatively for add-in cards, the available diagnostic tests for an FRU can be viewed
using the node and report-name parameters. Enter the following commands:
show hardware diagnostics report-status node <node name> test
<test name>
show hardware diagnostics report-status report-name <report
name>
Note:
Otherwise, the three parameters (fru-location, node, and report-name )
are allowed.
To view an ongoing report status, enter the following command:

show hardware diagnostics report-status report-name <report name>

command:
Table 6: Parameters of the command for viewing the status of a diagnostic test
report-status This parameter shows the status of an ongoing test.

location>
report-name <report This parameter specifies the name of a diagnostic

name> test report.
Step example
To view the status of subtest-cpu-io hardware diagnostic test, enter the following
command:
show hardware diagnostics report-status fru-location

To view an ongoing status of USPU0-010112-01, enter the following command:
show hardware diagnostics report-status report-name

USPU0-010112-01
13.4 Showing the hardware diagnostic

results and managing its reports
The hardware diagnostic tool is used to manage all reports of tests run on an
FRU.
If subtest-cpu-io item has passed, Diagnostics test result : PASSED is
displayed. The test result also displays the printout subtest-cpu-io: OK.

If an item has failed for any reason, a corresponding error information is

displayed (for example, subtest-cpu-io: REJECT). This information signifies an
FRU HW diagnostic failure, and the operator must correct or replace the FRU. If
the diagnostic fails after the FRU replacement, please contact Nokia Technical
Support for further investigation.
Purpose
Result of hardware diagnostic test is shown and its reports are managed.
▪ View reports of a diagnostic test.
To view the hardware diagnostic test reports (including add-in cards), enter the
following commands:
show hardware diagnostics report-details report-name <report
name>
show hardware diagnostics report-list fru-location <fru
location> filter-by [test <test name>]
Alternatively, for add-in cards the available diagnostic tests for an FRU can be started
show hardware diagnostics report-list node <node name> filter-by

[test <test name>]
Note:

command:

Table 7: Parameters of the command for viewing the test reports
report-details This parameter shows the details of a hardware diagnostic

test report.
report-list This parameter shows the list of all available hardware

diagnostic reports.
fru-location This parameter specifies the location of an FRU.

<fru location>
report-name This parameter specifies the name of the report, which is

<report name> specified by the user.
filter-by This parameter shows the list of diagnostic reports based

on filtering criteria.
Step example
To view the CPU hardware diagnostic test reports, enter the following command:
show hardware diagnostics report-details report-name

USPU0-010112-01
To view the list of available reports for the subtest-cpu-io hardware diagnostic
test, enter the following command:
show hardware diagnostics report-list fru-location

/chassis-1/slot-3 filter-by test subtest-cpu-io

14. Appendix: Screen command
This appendix describes the screen command which is a terminal emulator that
multiplexes a physical terminal among several simultaneous processes. It makes
remote zchassis_ex management downtime-proof, thus, more stable because
the running process continues independently of the SSH connection availability.
Purpose
Using the tool secures time-consuming and critical processes such as zchassis_ex,
restore, incremental software deliveries installation, or major software upgrade from
network issues.
Before you start

Ensure that root access rights are available.
Procedure
1 Run the screen tool, by executing the following command:
screen -LS [screenName]
where [screenName] is the name given to the current terminal to facilitate terminals
management in the future.
2 Verify if the screen command is running, by executing the following

command:
screen -ls
Step example
Assuming that the session name is set to zchassis_ex:

There is a screen on:

7596.zchassis_ex (Attached)
1 Socket in /tmp/screens/S-root.
3 Start the zchassis_ex management process.
Enter the command as in a regular terminal.
Step result
The expected outcome is that the SSH connection does not break. The process ends
successfully.
The unexpected outcome is that the SSH connection gets lost even before the process
ends successfully. If this happens, reattach the existing session using the following
command:
screen –r [screenName]
where [screenName] is the name provided to the terminal emulator.
Wait for the process to end then exit the session.
4 Exit the terminal, by executing the following command:
exit
Note:
Exit all inactive terminals. The list of all running terminals can be retrieved by
entering the screen -ls command. To reattach the running terminal, execute
the screen –r [screenName] command.
Step result
The expected outcome is that the [screen is terminating] is displayed.

Replacing Multicontroller RNC Hardware Units

Uploaded by

Copyright:

Available Formats

You might also like

Replacing Multicontroller RNC Hardware Units

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Replacing Multicontroller RNC Hardware Units

Uploaded by

Copyright:

Available Formats

Copyrighted material licensed to carlos.paredes@nokia.com on 08-08-2022.

No further reproduction or networking is permitted. Distributed by Nokia.

Approval Date 2020-11-11

The information in this document applies solely to the hardware/software product

2 © 2021 Nokia.Nokia conﬁdential

ERRORS IN OR OMISSIONS FROM THIS DOCUMENT OR ITS CONTENT.

Nokia is a registered trademark of Nokia Corporation. Other product names mentioned in

Copyright © 2021 Nokia. Nokia condential.

Important Notice on Product Safety

© 2021 Nokia.Nokia conﬁdential 3

© 2021 Nokia.Nokia conﬁdential

Summary of changes .................................................................................................................. 10

1 Replacing BCN module ............................................................................................................... 13

2 Replacing an add-in card ........................................................................................................... 73

3 Replacing the SO-DIMM on motherboard ............................................................................... 87

4 Replacing the system hard disk .............................................................................................. 109

5 Replacing the disaster recovery hard disk ............................................................................ 121

6 Replacing the failed HDDs on both CFPU nodes ................................................................. 127

7 Replacing the power distribution unit (PDU) ........................................................................ 128

© 2021 Nokia.Nokia conﬁdential 5

7.1 Removing the PDU ........................................................................................................ 129

8 Replacing a power supply unit ................................................................................................ 133

9 Replacing a fan module ........................................................................................................... 136

10 Replacing the air lter ........................................................................................................... 139

11 Replacing the BCN installation support kit BSK216-A ...................................................... 140

12 Replacing the BCN installation kit BIK216-A ...................................................................... 142

13 Performing hardware diagnostics ....................................................................................... 147

14 Appendix: Screen command ................................................................................................. 163

6 © 2021 Nokia.Nokia conﬁdential

© 2021 Nokia.Nokia conﬁdential 7

Figure 41 Pressing the hot swap handle ................................................................................ 114

8 © 2021 Nokia.Nokia conﬁdential

© 2021 Nokia.Nokia conﬁdential 9

In this summary of changes:

Changes between issues 08E (2020-09-30, WCDMA20)

Removing an add-in card

Updated the procedure.

Replacing the SO-DIMM on motherboard

Updated the sections in this chapter as required for BCN module.

Removing add-in cards from slots 7 and 8

10 © 2021 Nokia.Nokia conﬁdential

Installing removed add-in cards back to slots 7 and 8

Changes between issues 08D (2020-09-01, WCDMA

Updated the procedure.

Replacing the SO-DIMM on motherboard

Procedure updated for mcRNC.

Removing add-in cards from slots 7 and 8

Updated additional information on BCN module.

Enabling the new HDD

Reordered the procedure.

Changes between issues 08C (2020-08-13, WCDMA

Installing the new BCN module

Preparing LMP in BCN modules

Following changes are made in the sub-sections:

© 2021 Nokia.Nokia conﬁdential 11

© 2021 Nokia.Nokia conﬁdential

1. Replacing BCN module

Replacing a faulty BCN module requires general steps to be performed.

Before you start