GSM/EDGE BSS, Rel.
RG30(BSS), Operating
Documentation, Issue 04
Troubleshoot
Maintaining and Troubleshooting mcBSC
and mcTC Hardware
DN0992467
Issue 02B
Approval Date 2013-03-21
Confidential
Nokia Siemens Networks 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 Siemens Networks for any additional information.
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR 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.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright © Nokia Siemens Networks 2013. All rights reserved
f Important Notice on Product Safety
This product may present safety risks due to laser, electricity, heat, and other sources
of danger.
Only trained and qualified 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.
The same text in German:
f Wichtiger Hinweis zur Produktsicherheit
Von diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder
andere Gefahrenquellen ausgehen.
Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch
geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheitsanforderungen erfolgen.
Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,
Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentationssatzes.
2
Id:0900d805809a4b1b
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
Table of contents
This document has 57 pages.
Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
1
About this document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2
2.1
2.2
2.3
2.4
Hardware troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Problem with BCN module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Problem with Ethernet switch domain . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Problem with add-in card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Problem with synchronization or synchronization AMC for BCN (BSAC-A)
12
Problem with hard disk drive carrier AMC (HDSAM-A) . . . . . . . . . . . . . 14
Checking the hard disk drive on mcTC . . . . . . . . . . . . . . . . . . . . . . . . . 14
Problem with SFP or SFP+ transceiver . . . . . . . . . . . . . . . . . . . . . . . . . 16
Dealing with sensor alarms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.5
2.5.1
2.6
2.7
3
3.1
3.1.1
3.1.2
3.2
3.2.1
3.2.2
3.3
3.3.1
3.3.2
3.4
3.4.1
3.4.2
3.5
3.5.1
3.5.2
3.6
3.6.1
3.6.2
3.7
3.7.1
3.7.2
3.8
3.8.1
3.8.2
3.9
3.9.1
3.9.2
3.10
DN0992467
Replacing hardware units . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Replacing a BCN module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Removing a faulty BCN module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Installing a new BCN module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Replacing a synchronization AMC for mcBSC. . . . . . . . . . . . . . . . . . . . 26
Removing a synchronization AMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Installing a synchronization AMC. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Replacing a synchronization AMC for mcTC . . . . . . . . . . . . . . . . . . . . . 30
Removing the BSAC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Installing the new BSAC card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Replacing the hard disk drive on hard disk drive carrier AMC for mcBSC.
31
Removing the hard disk drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Installing the hard disk drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Replacing the hard disk drive on hard disk drive carrier AMC for mcTC 37
Removing the hard disk drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Installing the new hard disk drive. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Replacing a fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Removing a fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Installing a fan module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
Replacing an add-in card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Removing an add-in card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Installing an add-in card. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Replacing a power distribution unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Removing a power distribution unit (PDU). . . . . . . . . . . . . . . . . . . . . . . 50
Installing a power distribution unit (PDU). . . . . . . . . . . . . . . . . . . . . . . . 51
Replacing a power supply unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Removing a power supply unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Installing a power supply unit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Replacing the air filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Id:0900d805809a4b1b
Confidential
3
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
List of figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Figure 19
Figure 20
Figure 21
Figure 22
Figure 23
Figure 24
Figure 25
Figure 26
Figure 27
Figure 28
Figure 29
Figure 30
Figure 31
Figure 32
Figure 33
4
Positions of the PSUs and fan trays . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Pulling the hot swap handle of an AMC . . . . . . . . . . . . . . . . . . . . . . . . . 27
Removing an AMC from the BCN module . . . . . . . . . . . . . . . . . . . . . . . 27
Inserting an AMC into the BCN module . . . . . . . . . . . . . . . . . . . . . . . . . 28
Pressing the hot swap handle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
The SAS/SATA switch in the HDSAM-A . . . . . . . . . . . . . . . . . . . . . . . . . 31
Pulling the hot swap handle of an AMC . . . . . . . . . . . . . . . . . . . . . . . . . 32
Removing an AMC from the BCN module . . . . . . . . . . . . . . . . . . . . . . . 33
The hard disk drive on the hard disk drive carrier AMC . . . . . . . . . . . . . 33
Installing a hard disk drive on the hard disk drive carrier AMC . . . . . . . . 34
Inserting an AMC into the BCN module . . . . . . . . . . . . . . . . . . . . . . . . . 35
Pressing the hot swap handle. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
The SAS/SATA switch in the HDSAM-A . . . . . . . . . . . . . . . . . . . . . . . . . 37
The hard disk drive on the hard disk drive carrier AMC . . . . . . . . . . . . . 39
Installing a hard disk drive on the hard disk drive carrier AMC . . . . . . . . 39
BCN fan modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
BCN top cover screws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Removing the BCN top cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
BCN add-in card screws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Pulling an add-in card out from the BCN module . . . . . . . . . . . . . . . . . . 44
Inserting an add-in card into BCN module . . . . . . . . . . . . . . . . . . . . . . . 45
BCN add-in card screws . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Replacing the BCN top cover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Power distribution units in the cabinet . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Replacing a PDU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
Installing PDU to the cabinet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
PDU grounding cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Connecting site power supply cables to the PDU . . . . . . . . . . . . . . . . . . 53
Routing the site power supply cables . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
Removing an AC PSU from the BCN module . . . . . . . . . . . . . . . . . . . . . 55
Removing a DC PSU from the BCN module. . . . . . . . . . . . . . . . . . . . . . 56
Unscrewing the two thumbscrews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Openning the air filter cover and pulling out the air filter. . . . . . . . . . . . . 57
Id:0900d805809a4b1b
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
Summary of changes
Summary of changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Changes between issues 02B (2013/03/21, RG30(BSS)) and 02A (2013/02/14,
RG30(BSS))
Added a new chapter, “Checking the hard disk drive on mcTC”.
Changes between issues 02A (2013/02/14, RG30(BSS)) and 02 (2012/09/17,
RG30(BSS))
In chapter Hardware troubleshooting
• Dealing with sensor alarms chapter has been added.
In chapter Replacing hardware units
• Replacing BCN module chapter has been added.
Changes between issues 02 (2012/09/17, RG30(BSS)) and 01B (2012/01/04,
RG20(BSS))
In chapter Replacing an add-in card
• Types of add-in cards described.
• The detailed instructions about replacing BOC-A, BMPP2-A, and BMPP2-B were
added in further information.
DN0992467
Id:0900d805809a4a6c
Confidential
5
About this document
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
1 About this document
This document describes how to maintain and replace mcBSC and mcTC hardware
components of Nokia Siemens Networks. Section hardware troubleshooting provides
description of a hardware problem, its symptom and the recovery instructions needed to
repair the components. And section replacing hardware units provides instruction to
replace a hardware units.
6
Id:0900d805809a4a6d
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
Hardware troubleshooting
2 Hardware troubleshooting
2.1
Problem with BCN module
Description
The box controller node (BCN) module is not functioning properly. Possible causes for
the problem are:
•
•
•
•
•
There is a hardware fault in the BCN module.
One of the cables is not properly connected.
The DC converter is malfunctioning.
The IP address configuration is incorrect.
One of the sensors has detected a hazard in the module (too high or low temperature/voltage).
Symptoms
The following symptoms may indicate a problem in the BCN module:
•
•
•
•
•
The node-selected LED is OFF.
The power-on LED is red.
The application-specific LED is red.
There is a fault in the DC converter.
The BCN module does not start up successfully.
Recovery procedures
Note that in the case of 2N-redundant configuration, the same recovery procedures
apply for both single unit failure, and the simultaneous malfunction of both redundant
units.
The node selected LED is OFF
Make sure the BCN module is connected properly.
1. Power off the BCN module in question.
2. Check the cables to see if they are connected correctly.
3. Power on the BCN module again.
Power-on LED is red
Make sure the BCN module is connected properly.
1. Power off the BCN module in question.
2. Check the power supply units to see if they are in healthy state; check the power
cables to see if they are connected correctly.
3. Power on the BCN module again.
4. If the problem persists, try replacing the power supply unit with a new one.
DN0992467
Id:0900d805809b0b1b
Confidential
7
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2.2
Problem with Ethernet switch domain
Description
The Ethernet switch domain is not functioning properly. Possible causes for the problem
are:
•
•
•
a fault in commissioning, deployment or wrong software setup
a fault in switch configuration
crashing of the switch host software
Symptoms
The following symptoms may indicate a problem in the Ethernet switch domain:
•
•
The link/activity indication LED of the Ethernet port is OFF.
There is an IPMI alarm.
Recovery procedures
Note that in the case of 2N-redundant configuration, the same recovery procedures
apply for both single unit failure, and the simultaneous malfunction of both redundant
units.
The link/activity indication LED of the Ethernet port is OFF
Each 10 GigE and 1 GigE interface is associated with a Link/Activity indication LED (ON
when the link is on, blinking OFF every time there is some activity) and a Speed indication LED (ON when the port is using its maximum speed, otherwise OFF).
If the indication LED is OFF, try the following:
•
•
8
Check if the cables are connected correctly.
The connection to the Ethernet switch may not be established. When the switch configuration is completed, a few basic checks should be made to verify that the configuration works as expected:
– Software upload should work within the BSCLAN and the mcBSC BCN stack.
– Plug-in units should get IP addresses and rise up.
– Calls should be successfully created.
These checks do not exclude the possibility of configuration errors and problems
appearing later, but they show whether the basic control and management functions
are active and working.
In case of problems, the following checks should be carried out to eliminate basic
configuration errors:
– Cabling should conform to the models and topologies described in Multicontroller Site IP Connectivity Guidelines and BSC Site IP Configuration Principles
documents. Proper cable attachment and correct choice of SFP units should
also be checked.
– Check that the necessary interfaces are up, and that the port speeds match
(autonegotiation should be applied on all 1G interfaces; no autonegotiation on
the 10G interfaces).
– In traditional BSC and in mcBSC extension configurations, MSTP instance
descriptions must be identical in every switch participating in the Ethernet LAN.
Id:0900d805808edf4e
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
– Check that any switch and switch interface specific MSTP cost settings have
been configured as described in this document.
– Check that the necessary VLANs have been created and are allowed at the
switch interfaces as specified in BSC Site IP Configuration Principles.
– Check that the aggregated switch interfaces (LAGs) have been correctly configured.
DN0992467
Id:0900d805808edf4e
Confidential
9
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2.3
Problem with add-in card
Description
The add-in card is not functioning properly. Possible causes for the problem are:
•
•
•
•
•
•
•
•
•
•
The add-in card is not properly seated.
One of the memory modules is not properly seated.
The FRU data of the add-in card is incorrect.
One of the voltages is too high/low.
One of the temperatures is too high.
There is a fault in the DC converter.
The U-boot variables for the add-in card is not configured correctly.
The Node Manager rejects the add-in card because of insufficient power on the addin card.
The MMC firmware has corrupted.
Failure of BSAC-A usage caused by faulty BIOS settings.
Symptoms
The following symptoms may indicate a problem in the CPU blade:
•
•
•
The BIOS output does not include the expected data.
The computer unit fails to start to the normal operational state.
The boot printouts show that the unit address is FFFF:
UNIT ADDRESS SET FROM IPMI: FFFF
Recovery procedures
Note that in the case of 2N-redundant configuration, the same recovery procedures
apply for both single unit failure, and the simultaneous malfunction of both redundant
units.
The BIOS output does not include the expected data
Make sure that the add-in card and the memory modules are properly seated:
1.
2.
3.
4.
Remove the add-in card.
Remove and re-install the memory modules on the add-in card.
Re-install the add-in card to the module.
Configure the BIOS with expected data.
There are problems with the computer unit start-up
1. Check the states of the MCBC where the failing computer unit is. If the states are
not WO, analyze and change the states.
2. Check if alarm 3481 SHMU COMMUNICATION FAILURE is on. If yes, analyze and
correct.
3. Check the slot (and shelf) number of the BJC_A blade in the failing computer unit.
4. Change the functional state of the failing computer to SE-NH.
5. Delete the BJC_A blade from the failing computer unit.
6. Create the BJC_A blade to the failing computer unit using the correct slot and shelf
numbers.
10
Id:0900d805808ed17f
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
7. Change the failing computer unit to normal operational state.
Results
•
•
DN0992467
The boot printouts show correct unit address, for example 0004:
UNIT ADDRESS SET FROM IPMI: 0004
The boot loading is done correctly and the unit is started to normal operational state.
Id:0900d805808ed17f
Confidential
11
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2.4
Problem with synchronization or synchronization AMC for
BCN (BSAC-A)
Description
The synchronization is not functioning properly. Possible causes for the problem are:
•
•
•
•
•
The configuration for synchronization is wrong.
There is a hardware fault in the motherboard.
The synchronization input interface is not working.
The synchronization cable is not connected correctly.
The synchronization AMC is not functioning properly.
– The AMC module is not properly seated in the AMC bay.
– The FRU information of the AMC is missing, incomplete or incorrect.
– The Node Manager rejects the AMC because of insufficient power on the AMC
card.
– One of the voltages is too high/low.
– One of the temperatures is too high.
– The DC converter is malfunctioning.
– The MMC firmware has corrupted.
– There is a hardware fault in the AMC module.
– There is an IPMI alarm.
– The synchronization AMC (BSAC-A) failed.
– The BSAC-A flash memory is damaged.
Symptoms
The following symptoms may indicate a problem in the synchronization unit:
•
•
•
There is an IPMI alarm about the synchronization fault or AMC fault.
The BSAC-A AMC card LED is OFF or red.
The BSAC-A AMC card failed.
– There is a conflict with the ETH2 Ethernet MAC address.
Recovery procedures
Note that in the case of 2N-redundant configuration, the same recovery procedures
apply for both single unit failure, and the simultaneous malfunction of both redundant
units.
There is a hardware fault in the BSAC-A AMC card
Check the status of the processor BSAC-A AMC card LEDs.
If the LED is OFF, remove the BSAC-A AMC card in question and reinstall it.
The synchronization AMC (BSAC-A) failed
There is a conflict with the ETH2 Ethernet MAC address.
1. Save u-boot env to /tmp/bsac_u_boot.env
# /opt/bcntools/bsp_bootevn -c save
bootenv cmd: 'save'
12
Id:0900d805808ed17d
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
# ll /tmp/bsac_u_boot.env
-rw-r--r-- 1 root root 8192 Jan
1 00:55 /tmp/bsac_u_boot.env
2. Print the MAC address setting in /tmp/bsac_u_boot.env
# /opt/bcntools/bsp_bootevn -c show -n ethaddr
bootenv cmd: 'show'
u-bootenv name: 'ethaddr'
ethaddr=0e:00:21:00:00:00
3. Change the MAC address setting in /tmp/bsac_u_boot.env
# /opt/bcntools/bsp_bootevn -c set -n ethaddr -v
0e:00:21:00:00:01
bootenv cmd: 'set'
u-bootenv name: 'ethaddr'
u-bootenv value: 0e:00:21:00:00:01
4. Print MAC address setting in /tmp/bsac_u_boot.env
# /opt/bcntools/bsp_bootevn -c show -n ethaddr
bootenv cmd: 'show'
u-bootenv name: 'ethaddr'
ethaddr=0e:00:21:00:00:01
5. Update u-boot env from /tmp/bsac_u_boot.env to flash
# /opt/bcntools/bsp_bootevn -c update
bootenv cmd: 'update'
The BSAC-A flash memory is damaged
1. Connect to the BSAC-A through the serial port.
2. Check the start-up logs. If the flash memory is damaged, there are file system error
logs.
3. Change the damaged flash memory.
DN0992467
Id:0900d805808ed17d
Confidential
13
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2.5
Problem with hard disk drive carrier AMC (HDSAM-A)
Description
An AMC is not functioning properly. Possible causes for the problem are:
•
•
•
•
•
•
•
•
•
The AMC module is not properly seated in the AMC bay.
The FRU information of the AMC is missing, incomplete or incorrect.
The Node Manager rejects the AMC because of insufficient power on the AMC card.
One of the voltages is too high/low.
One of the temperatures is too high.
The DC converter is malfunctioning.
The MMC firmware has corrupted.
There is a hardware fault in the AMC module.
There is an IPMI alarm.
Symptoms
The following symptoms may indicate a problem in the AMC:
•
•
•
There is an IPMI alarm about AMC fault.
Hard disk AMC emits noise.
alarm "70359 HARD DISK DRIVE FAILURE" is raised on mcTC.
Recovery procedures
Note that in the case of 2N-redundant configuration, the same recovery procedures
apply for both single unit failure, and the simultaneous malfunction of both redundant
units.
There is an IPMI alarm about the AMC fault
SW Platform/Application to add instructions
2.5.1
Checking the hard disk drive on mcTC
You can check the health of HDSAM-A hard disk drive on mcTC, using the following
steps.
Steps
1
Log on to MCU-0 node.
2
Enable SMART Information Exception with parameter "-s on".
smartctl -s on /dev/sda
Example
root@BMPP2-A:/tmp# smartctl -s on /dev/sdasmartctl 5.39.1 201001-28 r3054 [mips64-target-linux-gnu] (local build)Copyright (C)
2002-10 by Bruce Allen,
http://smartmontools.sourceforge.netInformational Exceptions
(SMART) enabledTemperature warning enabled
14
Id:0900d805809b109d
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3
Check the SMART firmware status.
smartctl -a /dev/sda
Example
root@BMPP2-A:/tmp# smartctl --all /dev/sdasmartctl 5.39.1 201001-28 r3054 [mips64-target-linux-gnu] (local build)Copyright (C)
2002-10 by Bruce Allen,
http://smartmontools.sourceforge.netDevice: FUJITSU MAY2073RC
Version: 4701Serial number: B361P7700U8RDevice type:
diskTransport protocol: SASLocal Time is: Thu Jan 1 00:33:47 1970
UTCDevice supports SMART and is EnabledTemperature Warning
EnabledSMART Health Status: OK
4
Run SMART short test.
smartctl -C -t short /dev/sda
Example
root@BMPP2-A:/tmp# smartctl -C -t short /dev/sdasmartctl 5.39.1
2010-01-28 r3054 [mips64-target-linux-gnu] (local
build)Copyright (C) 2002-10 by Bruce Allen,
http://smartmontools.sourceforge.netShort Foreground Self Test
Successfulroot@BMPP2-A:/tmp#
If the test fails due to disk failure/disk problem, it should be replaced as per the instructions documented in Replacing the hard disk drive on hard disk drive carrier AMC for
mcTC.
DN0992467
Id:0900d805809b109d
Confidential
15
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2.6
Problem with SFP or SFP+ transceiver
Description
If an Ethernet connection is not working properly, there may be a fault in the SFP or
SFP+ transceiver.
Multicontroller BSC and Multicontroller TC Hardware Description for supported SFP
g See
and SFP+ transceiver types.
Symptoms
•
•
Statistics reports show that data packets are lost or there is a high count of one type
of data packet and the count climbs rapidly.
One of the LEDs indicates that there may be an Ethernet link/port failure.
Recovery procedures
1. Check that the transceiver and optical cable are properly connected and the cable
is not crimped.
2. Check if there is IPMI alarms indicating the Ethernet switch domain is faulty.
3. Check the link/activity indication LED of the Ethernet ports.
4. Check the transceiver information.
5. Check the speed settings of the port module.
6. If the port and link status was correct, replace the transceiver at the other end of the
link.
7. If the link is not recovered, replace the cable connecting the transceivers.
8. If the link still does not work, replace the transceiver at this end of the link.
16
Id:0900d805808edf50
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2.7
Dealing with sensor alarms
Symptoms
An alarm about the sensor value of an Field Replacement Unit (FRU) is received.
The following is an example of the alarm:
Alarm ID: 2813
Specific problem: 70307 - VOLTAGE OUT OF LIMIT
Managed object: fshwModuleId=addin-5,fshwPIUId=piu1,fshwEquipmentHolderId=chassis-2,fshwEquipmentHolderId=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: 2012-03-12 09:08:29:940 EET
Event type: x5 (equipment)
Application:
fshaProcessInstanceName=HPIMonitor,fshaRecoveryUnitName=FSHPIMonitorServer,fsipH
ostName=CFPU-0,fsFragmentId=Nodes,fsFragmentId=HA,fsClusterId=ClusterRoot
IAppl Addl. Info: Unit={BCNOC-A} Position=/chassis-2/slot-5
Sensor={number=138,Name=VDD_QLM3}
Appl. Addl. Info: 0.044
Notification ID: 8422
Extended event type : x1 (raise)
Control indicator: 7 (full visible)
Recovery procedures
1. Determine the sensor name from the Sensor field of the IAppl Addl. Info
section of the alarm.
2. Determine the effected FRU from the Position field of the IAppl Addl. Info
section of the alarm.
3. Check the sensor data of the FRU in trouble with the help of the sensor name and
FRU name.
BCN includes several sensors that report on hardware conditions. Many of the
sensor readings can be used to diagnose the hardware fault.
Follow the steps below to check the sensor data of the FRU in trouble:
DN0992467
Id:0900d80580935c8d
Confidential
17
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.1 Check the LMP version.
Issue the following command to show the LMP version:
mch cliVersion
Example:
mch cliVersion
Version 2.8
Build at: Jan 3 2012 14:26:15
3.2 For LMP version 2.8, do the following:
a List the hardware sensors.
Issue the following command to list all the hardware sensors:
mch_cli ShowSensor
g
This will list all the sensors, with the sensor addresses, attached to a
hardware unit.
Example:
mch_cli ShowSensor
Entity: PEM 1
PSU1 IN_Curr
PSU1 Fan 2
PSU1 Fan 1
PSU1 Temp 2
PSU1 Temp 1
PSU1 Status
PSU1 OUT_Curr
PSU1 OUT_3V3
PSU1 OUT_12V
PSU1 INPUT
Entity: PEM 2
PSU2 IN_Curr
PSU2 Fan 2
PSU2 Fan 1
PSU2 Temp 2
PSU2 Temp 1
PSU2 Status
PSU2 OUT_Curr
PSU2 OUT_3V3
PSU2 OUT_12V
PSU2 INPUT
b
0x2c
0x2a
0x28
0x26
0x24
0x22
0x20
0x1e
0x1c
0x1a
0x2d
0x2b
0x29
0x27
0x25
0x23
0x21
0x1f
0x1d
0x1b
Get the hardware sensor threshold.
Find the sensor address of the sensor you want and issue the following
command to get the sensor threshold of the hardware unit:
mch_cli GetSensorThreshold <Sensor addr>
Example:
18
Id:0900d80580935c8d
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
mch_cli GetSensorThreshold 0x20
sensor PSU1 OUT_Curr (32)
Lower Non-Critical
: NA
Lower Critical
: NA
Lower Non-Recoverable : 10.000
Upper Non-Critical
: NA
Upper Critical
: NA
Upper Non-Recoverable : 65.0000
support thresholds: unr
c
Get the hardware sensor data.
Issue the following command to get the sensor data of the hardware unit you
want:
mch_cli ReadSensor <Sensor addr>
Example:
mch_cli ReadSensor 0x20
sensor PSU1 OUT_Curr (0x20)
Value: 15.500000
3.3 For LMP version 3.1, do the following:
a List the hardware sensors.
Issue the following command to list all the hardware sensors:
mch_cli ShowSensor
g
This will list all the sensors, with the Logical Unit Number (LUN) and sensor
addresses, attached to a hardware unit.
Example:
mch_cli ShowSensor
Entity: PEM 1
PSU1 IN_Curr
PSU1 Fan 2
PSU1 Fan 1
PSU1 Temp 2
PSU1 Temp 1
PSU1 Status
PSU1 OUT_Curr
PSU1 OUT_3V3
PSU1 OUT_12V
PSU1 INPUT
Entity: PEM 2
PSU2 IN_Curr
PSU2 Fan 2
PSU2 Fan 1
PSU2 Temp 2
PSU2 Temp 1
PSU2 Status
PSU2 OUT_Curr
DN0992467
Id:0900d80580935c8d
Confidential
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x2c
0x2a
0x28
0x26
0x24
0x22
0x20
0x1e
0x1c
0x1a
0x00
0x00
0x00
0x00
0x00
0x00
0x00
0x2d
0x2b
0x29
0x27
0x25
0x23
0x21
19
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
PSU2 OUT_3V3
PSU2 OUT_12V
PSU2 INPUT
Entity: Fan tray 1
Fan 2
Fan 1
Entity: Fan tray 2
Fan 4
Fan 3
Entity: Fan tray 3
Fan 6
Fan 5
b
0x00
0x00
0x00
0x1f
0x1d
0x1b
0x00
0x00
0x0a
0x09
0x00
0x00
0x0c
0x0b
0x00
0x00
0x0e
0x0d
Get the hardware sensor threshold.
Find the sensor address of the sensor you want and issue the following
command to get the sensor threshold of the hardware unit:
mch_cli GetSensorThreshold <LUN> <Sensor addr>
Example:
mch_cli GetSensorThreshold
0x00
0x1a
sensor PSU1 INPUT (26)
Lower Non-Critical
: NA
Lower Critical
: NA
Lower Non-Recoverable : 44.0000
Upper Non-Critical
: NA
Upper Critical
: NA
Upper Non-Recoverable : 264.0000
support thresholds: lnr unr
c
Get the hardware sensor data.
Issue the following command to get the sensor data of the hardware unit you
want:
mch_cli ReadSensor <LUN> <Sensor addr>
Example:
mch_cli ReadSensor 0x00 0x1a
sensor: PSU1 INPUT
Lun:
0x00
Number: 0x1a
Value: 0.000000
4. If the sensor value is not within the Lower and Upper threshold value, try to replace
the FRU in trouble to correct the sensor value. See chapter Replacing hardware
units for details.
5. If the problem persists even after following the instructions, please contact your local
Nokia Siemens Networks representative with your observations on the sensor
values.
20
Id:0900d80580935c8d
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
Position of the PSUs and fan trays
The following picture shows the positions of the PSUs and fan trays.
Figure 1
DN0992467
Positions of the PSUs and fan trays
Id:0900d80580935c8d
Confidential
21
Replacing hardware units
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3 Replacing hardware units
3.1
Replacing a BCN module
Before you start
f Electrostatic discharge (ESD) may damage 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.
Change the states of the functional units on the faulty BCN module. Then, power off the
BCN module.
the states of the functional units should follow the actual hardware configurag Changing
tion of the BCN module to be replaced. You can refer to the following examples.
Do not power off all the BCN modules. Power off one BCN module once.
1. Change the states of the PCUM, ETME, and ETMA units.
ZUSC:PCUM,0:SP;
ZUSC:PCUM,0:TE;
ZUSC:PCUM,0:SE;
ZUSC:PCUM,0:SE;
ZUSC:ETME,0:TE;
ZUSC:ETME,0:SE;
ZUSC:ETME,0:SE;
ZUSC:ETMA,0:BL;
ZUSC:ETMA,0:TE;
ZUSC:ETMA,0:SE;
ZUSC:ETMA,0:SE;
2. Change the state of the BCXU unit.
ZUSC:BCXU,0:SP;
ZUSC:BCXU,0:TE;
ZUSC:BCXU,0:SE;
ZUSC:BCXU,0:SE;
3. Change the state of the MCMU unit.
ZUSC:MCMU,0:SP;
ZUSC:MCMU,0:TE;
ZUSC:MCMU,0:SE;
ZUSC:MCMU,0:SE;
4. If the BCN module contains an OMU unit, change the state of the OMU unit.
ZUSC:OMU:TE;
22
Id:0900d805809a4b1a
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.1.1
Replacing hardware units
Removing a faulty BCN module
Steps
1
If the BCN module is installed in the cabinet or stacking frame,
Then
Prepare the BCN module for replacement:
a
Gracefully shut down the BCN module.
b
If there is PDU used with the BCN module,
Then
Switch off the circuit breaker on the PDU for the BCN module.
c
Disconnect the power feed cables.
d
Disconnect the network cables from the transceivers on the front side of the
module.
e
Disconnect the BCN grounding cable.
f
Keep the network cables attached to the front cable tray of the BCN module.
g
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, refer to the Installing BCN
Hardware documentations.
h
2
Move the cable tray with attached network cables under the module, so the
module can be easily pulled out from the cabinet or stacking frame.
If the BCN module is installed in the cabinet or stacking frame,
Then
a
Remove the screws that fix the BCN module to the cabinet or stacking frame.
For more information, refer to the Installing BCN Hardware documentations.
b
f
DN0992467
Pull the module out of the cabinet or stacking frame.
CAUTION!
The BCN module is about 23kg. Lifting the module may require more than one
person.
Id:0900d805809a4b1a
Confidential
23
Replacing hardware units
3.1.2
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
Installing a new BCN module
Steps
1
If the BCN module is installed in the 19 inch cabinet,
Then
a
Fix the brackets, the inner rails and handles to the new BCN module.
b
Place the new BCN module in the outer rails and slide the module into the
cabinet, until it locks into position.
Pull the green latches on the inner sliding rails towards you and slide the BCN
module into the cabinet.
c
Fix the BCN module to the cabinet with screws.
For more information, refer to the document Installing BCN Hardware to IR206 Cabinet.
2
If the BCN module is installed in the CAB216-A cabinet,
Then
a
Fix the brackets to the new BCN module.
b
Place the BCN module on the support brackets and slide it into the cabinet.
c
Fix the BCN module to the cabinet with screws.
For more information, refer to the document Installing BCN hardware to CAB216-A
cabinet.
3
If the BCN module is installed in the stacking frame,
Then
a
Assemble and fix the brackets to the new BCN module.
b
Mount the BCN module on the support frame structure.
c
Fix the BCN module to the frame with screws.
For more information, refer to the document BCN Stacking Frame Installation.
4
If the BCN module is installed in the cabinet or stacking frame,
Then
Finish the BCN module replacement:
a
Install the cable tray with attached network cables back to the new BCN
module.
For more information, refer to the Installing BCN Hardware documentations.
24
b
Connect the BCN grounding cable.
c
Connect the network cables back to the transceivers on the front side of the
module.
Id:0900d805809a4b1a
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
d
Connect the power feed cables.
e
If there is PDU used with the BCN module,
Replacing hardware units
Then
Switch on the circuit breaker on the PDU for the BCN module.
5
Power on the BCN module.
6
Change the states of the functional unis to WO-EX or SP-EX.
a
If the BCN module contains an OMU unit, change the state of the OMU unit to WOEX.
ZUSC:OMU:WO;
b
Change the state of the MCMU unit to SP-EX.
ZUSC:MCMU,0:SE;
ZUSC:MCMU,0:TE;
ZUSC:MCMU,0:SP;
c
Change the state of the BCXU unit to SP-EX.
ZUSC:BCXU,0:SE;
ZUSC:BCXU,0:TE;
ZUSC:BCXU,0:SP;
d
Change the states of the PCUM, ETME, and ETMA units to SP-EX or WO-EX.
ZUSC:PCUM,0:SE;
ZUSC:PCUM,0:TE;
ZUSC:PCUM,0:SP;
ZUSC:ETME,0:SE;
ZUSC:ETME,0:TE;
ZUSC:ETME,0:SP;
ZUSC:ETMA,0:SE;
ZUSC:ETMA,0:TE;
ZUSC:ETMA,0:WO;
e
If the BCN module contains a hard disk drive, change the state of the hard disk drive
to WO-BU.
ZISC:,OMU:WDU,0:WO-BU;
DN0992467
Id:0900d805809a4b1a
Confidential
25
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.2
Replacing a synchronization AMC for mcBSC
Purpose
You may need to replace a synchronization AMC (BSAC-A) if it is faulty or if it needs to
be replaced due to configuration changes, extensions or servicing.
Before you start
f Electrostatic discharge (ESD) may damage 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.
3.2.1
Removing a synchronization AMC
Steps
1
Change the working state of the AMC to SE-NH.
For example:
ZUSC:PTUM,0:TE;
ZUSC:PTUM,0:SE-OU;
ZUSC:PTUM,0:SE-NH;
2
Remove the unit description of the AMC.
For example:
ZWTQ:PTUM,0:BOC_A,0;
ZWTV:PTUM,0;
3
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.
26
Id:0900d805809a4b05
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
DN0977767
Figure 2
4
Pulling the hot swap handle of an AMC
Wait until the hot swap LED turns into a solid blue.
This may take a few seconds.
5
Pull the hot swap handle again more firmly and slide the AMC out of the bay.
DN0973762
Figure 3
6
Removing an AMC from the BCN module
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.
DN0992467
Id:0900d805809a4b05
Confidential
27
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.2.2
Installing a synchronization AMC
Steps
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 as shown in the figure
below.
Make sure that the AMC is firmly seated in the module’s connectors.
DN0977588
Figure 4
3
Inserting an AMC into the BCN module
Press the hot swap handle firmly.
Wait until the blue hot swap LED turns off and the power LED turns solid green.
DN0977782
Figure 5
4
Pressing the hot swap handle
Create the unit description of the AMC.
For example:
ZWTU:PTUM,0:1F1-0:UTY=MCBC,UIN=0;
28
Id:0900d805809a4b05
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
ZWTP:PTUM,0:BSAC_A,0,1,1;
5
Change the working state of the AMC to WO-BU.
For example:
ZUSC:PTUM,0:SE-OU;
ZUSC:PTUM,0:TE;
ZUSC:PTUM,0:WO;
DN0992467
Id:0900d805809a4b05
Confidential
29
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.3
Replacing a synchronization AMC for mcTC
The synchronization AMC (BSAC) is delivered with the BSAC card in place.
You may also need to replace the BSAC card if it is faulty or if it needs to be upgraded
or serviced.
Before you start
f Electrostatic discharge (ESD) may damage 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.
3.3.1
Removing the BSAC card
Steps
1
Disconnect the CSYNC and Ethernet cables from the BSAC front panel connectors.
2
Remove the BSAC card.
To remove the BSAC card (BSAC card is also an AMC card), follow the instructions in
the section Removing a synchronization AMC.
3.3.2
Installing the new BSAC card
Steps
1
Install the BSAC card into the AMC bay.
2
Reconnect the CSYNC and Ethernet cables to the BSAC front panel connectors.
3
Restore the configuration for the new BSAC card.
To restore the configuration for the new BSAC card, enter the following command:
set hardware clock-sync cabinet-id cabinet-<id> chassis-id\
chassis-<id> clock-sync-hw ptu restart
Example:
If the BSAC card is located in cabinet 1 of chassis 3, enter the following command:
set hardware clock-sync cabinet-id cabinet-1 chassis-id\
chassis-3 clock-sync-hw ptu restart
30
Id:0900d80580a03f07
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.4
Replacing the hard disk drive on hard disk drive carrier
AMC for mcBSC
The hard disk drive carrier AMC (HDSAM-A) is delivered with the hard disk drive in
place. The hard disk drive should be replaced every 3 to 4 years.
You may also need to replace the hard disk drive if it is faulty or if it needs to be upgraded
or serviced.
Before you start
f Electrostatic discharge (ESD) may damage 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.
The HDSAM-A supports both SAS and SATA hard disk drives and includes a
SAS/SATA switch for selecting the disk type. BCN platform supports only SAS hard disk
drives, thus always check that the switch is set to SAS, before starting the replacement
procedure.
HDSAM-A
Handle
Switch
IPMB-L
SATA
2.5” SAS or SATA Drive
5V
Power
12V
AMC Connector
ON
1
SAS
Switch
Mechanical adapter
MMC
2 X SAS
LEDs
DN0945027
Figure 6
3.4.1
The SAS/SATA switch in the HDSAM-A
Removing the hard disk drive
Steps
1
Check the state of the hard disk.
ZISI:,OMU:WDU;
DN0992467
Id:0900d805809a4b07
Confidential
31
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2
Prevent disk updates.
a
Prevent file updates to the hard disk.
ZDUP:OMU;
b
Prevent database updates to the hard disk.
To check the databases in use, give the DBL command.
To prevent database updates, for example, give the command:
ZDBP:EQUIPM,0:DISK;
ZDBP:ILDATA,0:DISK;
3
Change the state of the hard disk into BL-US.
ZISC:,OMU:WDU,0:WO-ID;
ZISC:,OMU:WDU,0:BL-US;
4
Remove the hard disk drive carrier AMC from the AMC bay.
a
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.
DN0977767
Figure 7
b
Pulling the hot swap handle of an AMC
Wait until the hot swap LED turns into a solid blue.
This may take a few seconds.
32
Id:0900d805809a4b07
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
c
Pull the hot swap handle again more firmly and slide the AMC out of the bay.
DN0973762
Figure 8
d
Removing an AMC from the BCN module
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.
5
Place the AMC so that the hard disk drive side is facing down. Unscrew the four
screws on the metal bracket of the AMC module, then turn the module over.
6
Disconnect the hard disk drive.
Detach the hard disk drive from the connector by pulling it gently (from right to left in the
following figure).
Hard disk drive
DN0945257
Figure 9
DN0992467
The hard disk drive on the hard disk drive carrier AMC
Id:0900d805809a4b07
Confidential
33
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.4.2
Installing the hard disk drive
Steps
1
Connect the hard disk drive to the SAS connector of HDSAM-A.
Connect the hard disk drive to the SAS connector in the HDSAM-A by pushing it gently
(from left to right in the following figure).
Figure 10
2
Installing a hard disk drive on the hard disk drive carrier AMC
Turn the AMC over and attach the hard disk drive to the AMC with four screws.
Tighten the screws so that their heads are in line with the metal bracket.
3
Install the AMC module back into the AMC bay.
a
Check that the EMC gasket is correctly in place and that its contacts are clean.
b
Insert the AMC into the bay, sliding it along the guide rails as shown in the
figure below.
Make sure that the AMC is firmly seated in the module’s connectors.
34
Id:0900d805809a4b07
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
DN0977588
Figure 11
c
Inserting an AMC into the BCN module
Press the hot swap handle firmly.
Wait until the blue hot swap LED turns off and the power LED turns solid green.
DN0977782
Figure 12
4
Pressing the hot swap handle
If the hard disk is a new one, initialize it.
The hard disk must be in the WO-ID state so that it can be initialized.
To change the state, give the command:
ZISC:,:WDU,0:WO-ID;
To initialize the disk, give the command:
ZIWI:,:WB,<format>,<volume label>,<number of
files>,<versionlimit>,<initials>;
5
Change the state of the hard disk into TE-ID.
ZISC:,OMU:WDU,0:TE-ID;
DN0992467
Id:0900d805809a4b07
Confidential
35
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
6
Check the version of the unit’s IPMI software.
ZWDD:UT=OMU,UI=0;
7
Update the IPMI software, if needed.
must be done by experienced personnel who have sufficient knowledge of the
g This
system. Follow the instructions given in the command reference manual.
ZWDF:UT=OMU,UI=0,PT=BJC_A,PI=0;
8
Run diagnostics on the unit.
ZUDD:OMU,0:WDU,0;
9
Check the diagnostics report.
ZUDH:OMU,0:;
10
Change the working state of the hard disk back into WO-ID.
ZISC:,:WDU,0:WO-ID;
11
Copy the SCMANA directory, software package directory, and BOLERO image file
to the hard disk.
ZIWY:S:UNIT=OMU,PATH=/,DRIVE=WDU-S;
ZIWY:D:UNIT=OMU,PATH=/,DRIVE=WDU-B;
ZIBC:,,,,,,,,,DIR:;
12
Change the state of the hard disk into WO-BU.
ZISC:,:WDU,0:WO-BU;
13
Enable disk updates.
a
Resume file updates to the hard disk.
ZDUR:OMU;
b
Resume database updates to the hard disk.
For example:
ZDBR:EQUIPM,0:DISK;
ZDBR:ILDATA,0:DISK;
14
Check that there are no alarms active.
ZAHO:OMU,0;
ZAHO:WDU,0;
36
Id:0900d805809a4b07
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.5
Replacing the hard disk drive on hard disk drive carrier
AMC for mcTC
The hard disk drive carrier AMC (HDSAM-A) is delivered with the hard disk drive in
place. The hard disk drive should be replaced every 3 to 4 years.
You may also need to replace the hard disk drive if it is faulty or if it needs to be upgraded
or serviced.
Before you start
f Electrostatic discharge (ESD) may damage 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.
The HDSAM-A supports both SAS and SATA hard disk drives and includes a
SAS/SATA switch for selecting the disk type. BCN platform supports only SAS hard disk
drives, thus always check that the switch is set to SAS, before starting the replacement
procedure.
HDSAM-A
Handle
Switch
IPMB-L
SATA
2.5” SAS or SATA Drive
5V
Power
12V
AMC Connector
ON
1
SAS
Switch
Mechanical adapter
MMC
2 X SAS
LEDs
DN0945027
Figure 13
3.5.1
The SAS/SATA switch in the HDSAM-A
Removing the hard disk drive
Steps
1
Log on to MCU-0 node.
2
Make a full software backup of the current mcTC.
To backup a full mcTC software, follow the instructions given in Making a full software
backup of Safecopying in BSC, mcBSC and mcTC document.
DN0992467
Id:0900d805809a4b08
Confidential
37
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3
Transfer the mcTC software backup file to an external server.
To transfer the backup mcTC software to an external server, follow the instructions given
in Transferring the backup archive file to an external storage server of Safecopying in
BSC, mcBSC and mcTC document.
4
Lock the mcTC cluster.
To lock the mcTC cluster, give the following command in the command line interface.
# fshascli --lock /
Example:
# fshascli --lock /
/ is the cluster. The request will lock all the nodes in it.
Are you sure you want to proceed? [y/n] y
The following output is displayed:
/ is locked successfully.
5
Log on to LMP via console cable or SSH from FEWS.
6
Deactivate CPU1.
Example:
root@BCNMB-A:~# mch_cli Deactivate cpu1
7
Remove the AMC from the AMC bay.
To remove the AMC, follow the instructions given in section Removing a synchronization
AMC.
8
Place the AMC so that the hard disk drive side is facing down. Unscrew the four
screws on the metal bracket of the AMC module, then turn the module over.
9
Disconnect the hard disk drive.
Detach the faulty hard disk drive from the connector by pulling it gently (from right to left
in the following figure).
38
Id:0900d805809a4b08
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
Hard disk drive
DN0945257
Figure 14
3.5.2
The hard disk drive on the hard disk drive carrier AMC
Installing the new hard disk drive
Steps
1
Connect the new hard disk drive to the SAS connector of HDSAM-A.
Connect the new hard disk drive to the SAS connector in the HDSAM-A by pushing it
gently (from left to right in the following figure).
Hard disk drive
SAS connector
DN0945245
Inserted screw
Figure 15
DN0992467
Installing a hard disk drive on the hard disk drive carrier AMC
Id:0900d805809a4b08
Confidential
39
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2
Turn the AMC over and attach the new hard disk drive to the AMC with four
screws.
Tighten the screws so that their heads are in line with the metal bracket.
3
Install the AMC module back into the AMC bay.
To install the AMC module, follow the instructions given in section Installing a synchronization AMC.
4
Log into LMP via console cable or SSH from FEWS.
5
Activate CPU1.
Example:
root@BCNMB-A:~# mch_cli Activate cpu1
6
Perform either of the following instruction accordingly.
1
For a new HDD.
Re-commission mcTC. To commission a new mcTC, follow the instruction given in
Commissioning mcTC of Commissioning mcBSC and mcTC document.
2
For a commissioned HDD.
Log into MCU-0 and unlock the mcTC cluster.
Example:
# /opt/nokiasiemens/SS_FSetup/bin/fsetupcli --post configure
7
Transfer the backup database stored in the external server to MCU-0 and restore
the whole system.
To transfer stored backup database from the external server back to MCU-0, follow the
instruction given in Restoring the whole system section of Safecopying in BSC, mcBSC
and mcTC document.
8
Check the embedded software version on the new hard disk (HDSAM-A).
To check the version follow the instructions given in Retrieving the embedded software
version of Software Configuration Management in mcBSC and mcTC document.
9
Upgrade the embedded software version.
If there are newer embedded software versions, then upgrade the embedded software
version. For instructions, see Upgrading embedded software of Software Configuration
Management in mcBSC and mcTC document.
40
Id:0900d805809a4b08
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.6
Replacing a fan module
Before you start
f Electrostatic discharge (ESD) may damage 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.
that only one fan module can be replaced at once. Prepare the spare fan unit for
t Note
replacement beforehand. After removing a fan from the BCN module, the systems starts
to heat up very quickly. Proceed immediately with the new fan installation. The following
procedure applies to all three fan modules of the BCN module.
Summary
The fan modules are located at the rear of the BCN module.
DN0973747
Figure 16
3.6.1
BCN fan modules
Removing a fan module
Steps
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 or
with a screwdriver.
2
3.6.2
Pull the fan module out from the BCN module.
Installing a fan module
Steps
1
Insert the fan module to its slot at the rear side of the BCN module.
2
Tighten the fan module’s thumbscrews.
The Phillips screws are built into the fan module and can be tightened either by hand or
with a screwdriver.
DN0992467
Id:0900d805809a4b09
Confidential
41
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.7
Replacing an add-in card
The following types of add-in cards can be installed in the BCN module:
•
•
•
•
•
BCN Octeon Card Variant A (BOC-A)
BCN Octeon2 Card Variant A (BMPP2-A)
BCN Octeon2 Card Variant B (BMPP2-B)
BCN Jasper Card Variant A (BJC-A)
BCN DSP Card Variant A (BDSP-A)
For more information, see Multicontroller BSC and Multicontroller TC Hardware Description.
BOC-A, BMPP2-A, and BMPP2-B are processor add-in cards which can be used in:
•
•
•
Packet Control Unit in Multicontroller BSC (PCUM)
Multicontroller Exchange Terminal for Ethernet Abis (ETME)
Multicontroller Exchange Terminal for A-interface (ETMA)
When replacing BOC-A with BMPP2-A/B, replacing BMPP2-A with BMPP2-B, or replacing BMPP2-B with BMPP2-A, follow the instructions in Further information to handle the
alarms.
Before you start
Power off the BCN module before removing or installing an add-in card.
f Electrostatic discharge (ESD) may damage 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.
3.7.1
Removing an add-in card
Steps
1
If the BCN module is installed in the cabinet,
Then
Prepare the BCN module for add-in card replacement:
a
Gracefully shut down the BCN module.
b
If there is PDU used with the BCN module,
Then
Switch off the circuit breaker on the PDU for the BCN module in question.
42
c
Disconnect the power feed cables.
d
Disconnect the network cables from the transceivers on the front side of the
module.
e
Disconnect the BCN grounding cable.
f
Keep the network cables attached to the front cable tray of the BCN module.
Id:0900d805809a4b0a
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
g
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, refer to the document Installing
BCN Modules to the IR206 Cabinet.
h
2
Move the cable tray with attached network cables under the module, so the
module can be easily pulled out from the cabinet.
Unscrew the two thumbscrews securing the top cover of the BCN module.
The screws are located at the rear side of the module as shown on the figure below. The
Phillips screws are built into the top cover of the BCN module and can be loosened
either by hand or with a screwdriver.
DN0973774
Figure 17
3
BCN top cover screws
If the BCN module is installed in the cabinet,
Then
a
Pull the module out of the cabinet, until it locks into the outmost position.
b
If there is another BCN module installed immediately above the module in question,
Then
Unscrew the two screws attaching the cable tray to the BCN module immediately above and lift the cable tray upwards. This will create enough space for
the removal of the lower module's top cover.
4
Slide the top cover of module towards the rear side until it stops. Lift the top cover
upwards.
2
1
DN0973786
Figure 18
DN0992467
Removing the BCN top cover
Id:0900d805809a4b0a
Confidential
43
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
5
Unscrew the two thumbscrews securing the add-in card to the rails inside the
BCN module.
DN0977525
Figure 19
6
BCN add-in card screws
Slide the add-in card upwards to remove it from the BCN module.
DN0973798
Figure 20
44
Pulling an add-in card out from the BCN module
Id:0900d805809a4b0a
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.7.2
Installing an add-in card
Steps
1
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.
DN0973708
Figure 21
2
Inserting an add-in card into BCN module
Secure the add-in card to the rails with built-in thumbscrews.
The Phillips screws are built into the add-in card and can be tightened either by hand or
with a screwdriver.
DN0977525
Figure 22
3
DN0992467
BCN add-in card screws
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.
Id:0900d805809a4b0a
Confidential
45
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2
1
DN0973786
2
1
DN0977576
Figure 23
Replacing the BCN top cover
4
Slide the top cover to the front side of the module, until it falls into place.
5
If the BCN module is installed in the cabinet,
Then
a
If there is another BCN module installed immediately above the module in question,
Then
Place the cable tray of the above BCN module back to position and secure it
with two built-in screws.
b
Push the module back into the cabinet, until it locks into position.
Pull the green latches on the inner sliding rails towards you and slide the BCN
module into the cabinet.
6
Tighten the thumbscrews of the top cover.
7
If the BCN module is installed in the cabinet,
Then
Finish the add-in card replacement in BCN module:
a
Install the cable tray with attached network cables back to the BCN module.
For more information about the cable tray installation, check the document Installing
BCN Modules to the IR206 Cabinet.
b
46
Connect the BCN grounding cable.
Id:0900d805809a4b0a
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
c
Connect the network cables back to the transceivers on the front side of the
module.
d
Connect the power feed cables.
e
If there is PDU used with the BCN module,
Then
Switch on the circuit breaker on the PDU for the BCN module in question.
f
Power on the BCN module.
Further information
ALARM 3757 - PLUG-IN UNIT TYPE NOT MATCH is set when replacing BOC-A with
BMPP2-A/B, replacing BMPP2-A with BMPP2-B, or replacing BMPP2-B with BMPP2-A.
not replace BMPP2-A/B with BOC-A. Otherwise, IP addresses cannot be configured
g Do
automatically.
Check the value of parameter AUTOMATIC_UPDATE with the following command:
ZWOI:2,2070;
Example output:
EXECUTION STARTED
PARAMETER CLASS: 2
SYSTEM_FUNCT_CONFIGUR
IDENTIFIER
NAME OF PARAMETER
VALUE
CHANGE POSSIBILITY
02070
AUTOMATIC_UPDATE
00FF
YES
COMMAND EXECUTED
•
If the value of parameter AUTOMATIC_UPDATE is 00FF:
1. Change the state of OMU to WO-EX, if necessary.
For example:
ZUSC:OMU:SE,;
ZUSC:OMU:TE,;
ZUSC:OMU:WO,;
2. Change the state of PCUM, ETME, or ETMA to TE-EX, if necessary.
For example:
ZUSC:PCUM,0:SE,;
ZUSC:PCUM,0:TE,;
3. Print out alarm history of ALARM 208 - PIU TYPE HAS BEEN UPDATED IN
DATEBASE to check if the new unit type is updated in the hardware database
automatically.
ZAHP::NR=208;
Example output:
DN0992467
Id:0900d805809a4b0a
Confidential
47
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
mcBSC
Heat
2010-07-25
12:33:12
ALARM HISTORY
<HIST> Heat
OMU
SWITCH
NOTICE OMU
1F001-00-1
EQPPRB
0208 PIU TYPE HAS BEEN UPDATED IN DATEBASE
BMPP2_B 0d 01 46 02 00 01 0A 03
2010-07-25
12:32:54.87
END OF ALARM HISTORY
COMMAND EXECUTED
4. Print out alarm history of ALARM 3757- PLUG-IN UNIT TYPE NOT MATCH
to check if Alarm 3757 is cancelled automatically.
ZAHP::NR=3757;
Example output:
LOADING PROGRAM VERSION 6.7-0
mcBSC
Heat
2010-07-25
12:32:56
ALARM HISTORY
**
..
<HIST> Heat
OMU
TRANSM
ALARM OMU
1F001-00-1
ORZDHC
(0659) 3757 PLUG-IN UNIT TYPE NOT MATCH
BMPP2_B 0129 0d
2010-07-25
12:32:54.87
<HIST> Heat
OMU
TRANSM
CANCEL OMU
1F001-00-1
ORZDHC
(0659) 3757 PLUG-IN UNIT TYPE NOT MATCH
BMPP2_B 0129 0d
2010-07-25
12:32:54.87
END OF ALARM HISTORY
COMMAND EXECUTED
•
48
If the value of parameter AUTOMATIC_UPDATE is 0000:
1. Change the state of OMU to WO-EX, if necessary.
For example:
ZUSC:OMU:SE,;
ZUSC:OMU:TE,;
ZUSC:OMU:WO,;
Id:0900d805809a4b0a
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
2. Configure the new plug-in unit type manually.
For example:
ZUSC:PCUM,0:SE,;
ZUSC:PCUM,0:SE,;
ZWTQ:PCUM,0:BMPP2_B,0:;
ZWTP:PCUM,0:BMPP2_A,0,1,3:;
ZUSC:PCUM,0:SE,;
ZUSC:PCUM,0:TE,;
DN0992467
Id:0900d805809a4b0a
Confidential
49
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.8
Replacing a power distribution unit
Purpose
If the power distribution unit (PDU) is faulty, you must replace it with a new one.
ON
OFF
1
ON
OFF
2
ON
OFF
3
ON
OFF
4
ON
ON
OFF
1
ON
OFF
2
OFF
ON
OFF
3
5
ON
ON
OFF
6
ON
OFF
7
ON
OFF
8
OFF
4
ON
OFF
5
ON
OFF
6
ON
OFF
7
ON
OFF
8
front view
DN0960093
Figure 24
Power distribution units in the cabinet
Before you start
Make sure you have a digital multimeter or voltage meter available.
f Danger of hazardous voltages and electric shock!
Before connecting or removing any power supply cables to or from the power distribution
unit, make sure 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).
f Danger of hazardous voltages and electric shock!
Make sure your hands are dry and remove any metal objects such as rings before
touching the power supply equipment.
f 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.
3.8.1
Removing a power distribution unit (PDU)
Steps
50
1
Make sure that the redundant PDU is functional.
2
Switch off the circuit breakers on the PDU you are going to remove.
Id:0900d805809a4b17
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3
Check the PDU input feeds with a digital multimeter to ensure there are no
voltages in the cables.
4
Disconnect all cables from the PDU.
a) Disconnect the four power feed cables from the PDU.
b) Disconnect the CGNDB grounding cable from the PDU.
c) Disconnect the eight PSU input feeds from the PDU.
5
Unscrew the four fixing screws attaching the PDU to the cabinet.
M6
ON
OFF
1
ON
OFF
2
ON
OFF
3
ON
OFF
4
ON
ON
OFF
1
ON
OFF
2
OFF
ON
OFF
3
ON
5
OFF
5
3.8.2
ON
ON
OFF
OFF
7
6
ON
OFF
ON
OFF
7
8
ON
OFF
8
front view
DN0960109
6
6
4
ON
Figure 25
ON
OFF
OFF
Replacing a PDU
Remove the PDU from the cabinet.
Installing a power distribution unit (PDU)
Steps
DN0992467
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.
Id:0900d805809a4b17
Confidential
51
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
M6
ON
OFF
1
ON
OFF
2
ON
OFF
3
ON
OFF
4
ON
ON
OFF
1
ON
OFF
2
OFF
ON
OFF
3
ON
ON
OFF
5
6
OFF
ON
OFF
5
6
ON
ON
OFF
OFF
7
8
ON
OFF
8
front view
DN0960187
3
7
4
ON
Figure 26
ON
OFF
OFF
Installing PDU to the cabinet
Connect the PDU grounding cable (CGNDB) to the PDU.
- 48
RTN
- 48
7
RTN
5
3
8
1
6
4
2
rear view
DN0977591
Figure 27
PDU grounding cable
4
Check the PDU input feeds with a digital multimeter to ensure there are no
voltages in the cables.
5
Connect the site power supply cables to the PDU (for DC power supply only).
Steps
52
Id:0900d805809a4b17
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
1
Crimp the cable lugs to the power supply cables.
2
Route the cables to the PDUs.
Run the cables through the top or bottom openings of the cabinet, and along the
sides of the cabinet to the rear side of the PDUs. When cables are routed through
the bottom, they have to be routed along the right side of the cabinet when viewed
from the rear.
- 48
3
Remove the nuts from the power terminals with a 10mm socket wrench.
4
Connect the feed cable with lug to terminal connector marked -48/-60 VDC IN,
and the return cable with lug to terminal connector marked RTN.
RTN
- 48
7
RTN
5
3
8
1
6
4
2
DN0977607
Figure 28
5
6
Connecting site power supply cables to the PDU
Secure the cable lugs on the terminal connectors with nuts.
Connect the site power supply cables to the PDU (for AC power supply only).
Steps
1
Route the cables to the PDUs.
Run the cables from the rear side of the PDUs through the top openings (A) or
bottom openings (B) of the cabinet, and along the sides of the cabinet.
DN0992467
Id:0900d805809a4b17
Confidential
53
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
IEC 60309 - 2P+PE 250 V
7
A
5
2
8
1
6
4
2
B
DN0977813
IEC 60309 - 2P+PE 250 V
Figure 29
2
Routing the site power supply cables
Plug the power supply cables to the site power supply.
For the best reliability in the power feed, make sure that the site power supply feeds
PDU 1 and PDU 2 in different phase.
54
7
Connect the eight PSU input feeds to the PDU.
8
Switch on the site power supply to the PDU.
9
Switch on the circuit breakers on the PDU.
Id:0900d805809a4b17
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.9
Replacing a power supply unit
Before you start
f Electrostatic discharge (ESD) may damage 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.
3.9.1
Removing a power supply unit
Steps
1
If there is PDU used with the BCN module,
Then
Switch off the circuit breaker on the PDU for 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 the power supply unit out from the BCN module.
DN0960151
Figure 30
DN0992467
Removing an AC PSU from the BCN module
Id:0900d805809a4b18
Confidential
55
POK
POK
RTN -48V
RTN -48V
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
DN0960163
Figure 31
3.9.2
Removing a DC PSU from the BCN module
Installing a power supply unit
Steps
1
Insert the power supply unit to its 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
If there is PDU used with the BCN module,
Then
Switch on the circuit breaker on the PDU for the power supply unit, which was
replaced.
56
Id:0900d805809a4b18
Confidential
DN0992467
Maintaining and Troubleshooting mcBSC and mcTC
Hardware
3.10
Replacing the air filter
Purpose
Inspect the air filter regularly. To prevent dust from accumulating inside the equipment,
the filter element should be replaced twice a year.
Steps
1
Unscrew the two thumbscrews attaching the air filer cover to the BCN module.
Figure 32
2
Unscrewing the two thumbscrews
Open the air filter cover and pull out the air filter.
DN0960112
Figure 33
DN0992467
Openning 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.
5
Record the date of the air filter change.
Id:0900d805809a4b19
Confidential
57