Sie sind auf Seite 1von 23

Nokia Siemens Networks

WCDMA RAN, Rel. RU30,


Operating Documentation,
Issue 01

Expanding and Upgrading AXC


DN70554681
Issue 03B
Approval Date 2010-08-25

Confidential

Expanding and Upgrading AXC

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 2010. All rights reserved

Important Notice on Product Safety


Elevated voltages are inevitably present at specific points in this electrical equipment.
Some of the parts may also have elevated operating temperatures.
Non-observance of these conditions and the safety instructions can result in personal
injury or in property damage.
Therefore, only trained and qualified personnel may install and maintain the system.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected
has to comply with the applicable safety standards.

The same text in German:


Wichtiger Hinweis zur Produktsicherheit
In elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teile knnen auch eine hohe Betriebstemperatur aufweisen.
Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen und Sachschden fhren.
Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die
Anlagen installiert und wartet.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.

Id:0900d805807d5908
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Table of contents
This document has 23 pages.
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

DN70554681
Issue 03B

Adding and replacing IFUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Installing the TOPA module to the IFUH . . . . . . . . . . . . . . . . . . . . . . . . 10

Replacing AXUA with AXUB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Adding another S-AXC node to S-AXC subrack . . . . . . . . . . . . . . . . . . 13

Changing AXC software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Changing software with AXC-FB Hopper Manager . . . . . . . . . . . . . . . . 19

Checklist for AXC HW expansion and upgrade . . . . . . . . . . . . . . . . . . . 22

Id:0900d805807d5908
Confidential

Expanding and Upgrading AXC

List of figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8

Installing the TOPA module on the IFUH unit . . . . . . . . . . . . . . . . . . . . . 10


Both S-AXC cartridges fully equipped. . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Node Software window before software upgrade . . . . . . . . . . . . . . . . . . 16
Downloading new software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
Setting FTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Selecting software for download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Node Software window after software upgrade . . . . . . . . . . . . . . . . . . . 18
FB Hopper Manager Software window . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Id:0900d805807d5908
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Summary of Changes

Summary of Changes
Changes between document issues are cumulative. Therefore, the latest document
issue contains all changes made to previous issues.
Note that the issue numbering system is changing. For more information, see Guide to
WCDMA RAN operating documentation.
Changes between issues 03A (2009-12-14, WCDMA RAN RU20) and 03B (2010-0825, WCDMA RAN RU20)
Changing software with AXC-FB Hopper Manager (6)
Additional information on setting reset after activation has been added (see Further
information).
Figure FB Hopper Manager Software window has been added.

Changes between issues 03 (2009-09-18, WCDMA RAN RU20) and 03A (2009-1214, WCDMA RAN RU20)
Stickers have been removed from the steps and the image in section Installing the
TOPA module to the IFUH.

Changes between issues 2-0 (20-11-2008, WCDMA RAN RU10) and 03 (2009-09-18,
WCDMA RAN RU20)
Editorial modifications have been made in sections Changing AXC software, Adding and
replacing IFUs and Replacing AXUA with AXUB.

DN70554681
Issue 03B

Id:0900d805807d5955
Confidential

Summary of Changes

Expanding and Upgrading AXC

Id:0900d805807d5955
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Adding and replacing IFUs

1 Adding and replacing IFUs


Purpose
The procedures in this section describe how to add and replace units in an operating
AXC. There are several options:

install an IFU to an empty slot


replace an IFU with an IFU of the same type
replace an IFU with an IFU of a different type
remove an IFU and leave the slot empty

When performing these tasks you will have to reconfigure the AXC with AXC Manager
or AXC-FB Hopper Manager. Reconfiguration is not necessary when an IFU is replaced
with an IFU that is of the same type and that contains the same software version.
The removal of an IFU does not interrupt traffic in other IFUs.
Before you start
Go through the precautions, restrictions and instructions for handling units in Requirements for installing AXC in Installing AXC.

!
Risk of eye damage caused by invisible laser radiation. Never look directly at the internal
optical fibre connector exit of the transmitter apparatus when it is switched on. In the
event of possible exposure, consult a doctor immediately.
Switch off the lasers with AXC Manager and disconnect the optical connectors before
removing an IFUC or IFUF. After removing the unit, put the protective caps back on the
optical interfaces.

!
The unit is hot. Do not remove the unit until it has cooled down.
Switch off the power on the IFUE interfaces before removing the Flexbus cables connected to the outdoor units.
Mixed software releases are not allowed within the same AXC. When replacing a unit
check that the software version of the old and new unit are the same.
If a new unit contains a different software version, unit LED remains yellow until you
change its software. For more information, see Changing AXC software in Expanding
and upgrading AXC.
A faulty IFUH/AXCF unit must be returned to NSN Hardware Services without the SFP
module.
Steps
1

Installing an IFU to an empty slot


Steps
a

DN70554681
Issue 03B

Remove the blanking plate.

Id:0900d805806f0380
Confidential

Adding and replacing IFUs

Expanding and Upgrading AXC

Insert the new unit into the correct slot.


Close the ejectors when the unit is in place. Tighten the unit's locking screws firmly.
Wait until the unit has booted (this can take several minutes).

Connect the cables to the interfaces.


Route the electrical cables and optical fibres.

Click View Refresh All in AXC Manager.


Check that the new hardware configuration is displayed in the Hardware view. See
Inspecting hardware and modifying identifications in Operating and maintaining
AXC.

e
2

Make all necessary configurations.

Replacing an IFU with an IFU of the same type


Steps
a

Disconnect all cables from the external interfaces.

Remove the unit from the slot.


Open the locking screws and ejectors. Pull out the unit holding it by the ejectors.
Store the removed unit in its original package.

Insert the new unit into the correct slot.


Close the ejectors when the unit is in place. Tighten the unit's locking screws firmly.

Connect the cables to the interfaces.


Route the electrical cables and optical fibres.

Click View Refresh All after the unit LED becomes green, yellow or red.
If the unit LED remains yellow, it may run on a different software version. See
Changing AXC software in Expanding and upgrading AXC.
If the unit LED turns red, check the physical cable connection.
Check that the new hardware configuration is displayed in the Hardware view. See
Inspecting hardware and modifying identifications Operating and maintaining AXC.
Note that the configurations of the old unit are restored automatically. However,
when removing an IFUE, only the configurations in the ATM part are restored. The
configurations of the Flexbus part may be lost and may have to be configured again.
For more information, see Commissioning FlexiHopper (Plus) and MetroHopper
with IFUE.

Replacing an IFU with an IFU of different type


Steps
a

Disconnect all cables from the external interfaces.

Id:0900d805806f0380
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Adding and replacing IFUs

Right-click the slot in the Hardware view and select Uninstall unit.
AXC Manager asks for confirmation, since all configurations of the removed unit are
lost.
Wait until the unit has disappeared from the Hardware view.

Remove the unit from the slot.


Open the locking screws and ejectors. Pull out the unit holding it by the ejectors.
Store the removed unit in its original package.

Insert the new unit into the correct slot.


Close the ejectors when the unit is in place. Tighten the unit's locking screws firmly.
Wait until the unit has booted (this can take several minutes).

Connect the cables to the interfaces.


Route the electrical cables and optical fibres.

Click View Refresh All.


Check that the new hardware configuration is displayed in the Hardware view. See
Inspecting hardware and modifying identifications in Operating and maintaining
AXC.

g
4

Make all necessary configurations.

Removing an IFU and leaving the slot empty


Steps
a

Disconnect all cables from the external interfaces.

Right-click the slot in the Hardware view and select Uninstall unit.
AXC Manager asks for confirmation, since all configurations of the removed unit are
lost.

Remove the unit from the slot.


Open the locking screws and ejectors. Pull out the unit holding it by the ejectors.
Store the removed unit in its original package.

d
5

Install a blanking plate to the slot.

Update hardware information in your IM system.


For more information, see Storing item code and serial number for traceability purposes
in Operating and maintaining AXC.

DN70554681
Issue 03B

Id:0900d805806f0380
Confidential

Installing the TOPA module to the IFUH

Expanding and Upgrading AXC

2 Installing the TOPA module to the IFUH


Before you start
Make sure you have the ESD wrist strap connected and grounded.
Steps
1

Check that the delivery contents of the TOPA module package are correct.

Request shutdown for the BTS from the OSS/NMS.

Remove the IFUH unit from the AXC rack.

Remove the TOPA module from the delivery package.

Place the TOPA module on the IFUH unit as shown in the figure.
Make sure you have the correct position.

Figure 1
6

10

Installing the TOPA module on the IFUH unit

Press the TOPA until the connectors snap into place.

Id:0900d805806f03ce
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Installing the TOPA module to the IFUH

Fix the TOPA module with the screws as shown in the figure.
Tighten until fixed.

DN70554681
Issue 03B

Re-insert the IFUH unit to the rack.

Wait until the LED shows green light. This may take several minutes.

10

Change the AXC synchronization source to the correct IFUH interface from the
AXC manager.

11

Request for power-up for the BTS from the network management system.

12

Ensure via the network management system that the BTS is working correctly.

Id:0900d805806f03ce
Confidential

11

Replacing AXUA with AXUB

Expanding and Upgrading AXC

3 Replacing AXUA with AXUB


Purpose
This procedure describes how to replace AXUA with AXUB and take BTS AAL2 Multiplexing into use.
Steps
1

Make a backup of the AXC configuration.


Click Node Export Configuration and select the directory. After exporting the configuration, make sure that the configuration file has been stored in the directory.

Switch off the AXC.

Disconnect all cables from the AXUA and remove it from its slot.
Open the locking screws and ejectors. Pull out the unit holding it by the ejectors. Store
the removed unit in its original package.

Insert the AXUB.


Close the ejectors when the unit is in place. Tighten the unit's locking screws firmly.

Reconnect all cables.

Switch on the AXC.


Wait until the AXC has booted and the AXUB LED is green or red.

Restore the AXC configuration.


Click Node Import Configuration and Start Download. After the configuration has
been downloaded, click Activate.
It is recommended that an XML file containing the configuration changes required by
BTS AAL2 Multiplexing is prepared beforehand and imported to the AXC. For more
information, see Commissioning AXC with XML configuration file in Commissioning
AXC.
If an XML file has not been prepared beforehand, the BTS AAL2 Multiplexing can be
configured manually. See Configuring Iub terminations in Commissioning AXC.

Configure the radio network controller (RNC).


For instructions, see Radio Network Controller Product Documentation.

12

Id:0900d805806f03d1
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Adding another S-AXC node to S-AXC subrack

4 Adding another S-AXC node to S-AXC


subrack
Purpose
This procedure describes how to add another S-AXC node to an S-AXC subrack.
The second S-AXC node can be added to the subrack by installing the necessary plugin units in the second S-AXC cartridge. The two S-AXC nodes in the subrack are independent and they can be cascaded. Traffic from one S-AXC node can be transferred to
the other S-AXC node, for example, via an optical fibre between the IFUC interface
units.
Steps

DN70554681
Issue 03B

Check the DC-PIU jumper settings.

Connect the power and alarm cables to S-AXC cartridge.

Connect the station alarm and power cables to DC-PIU.

Check the jumper settings of the fan unit.

Install the S-AXC plug-in units.

Mark the optical fibres and electrical cables.

Route the electrical cables.

Lay the optical fibres.

Connect S-AXC interfaces.

10

Tie the cables to strain reliefs.

11

Verify the S-AXC installation.

12

Connect the battery voltage to the S-AXC.

Id:0900d805806f03d6
Confidential

13

Adding another S-AXC node to S-AXC subrack

Expanding and Upgrading AXC

Expected outcome

Figure 2

14

Both S-AXC cartridges fully equipped

Id:0900d805806f03d6
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Changing AXC software

5 Changing AXC software


Purpose
The software of the AXC can be updated from one release to the next. After the update,
the configuration of AXC is restored automatically.
If the XML configuration files or software packages are downloaded to the AXC locally
from the Local Management Tool, no external FTP server needs to be configured. The
AXC Manager contains an internal File Transfer Protocol (FTP) server. This server is
activated automatically when necessary.
When you are upgrading the AXC software, the AXC Manager C6.0 is connected to a
C5.5 node. Only limited configuration features are available, the most important one
being the software upgrade.
This procedure does not cover updating the software of the Flexbus part of the IFUE.
For more information see Changing software with AXC-FB Hopper Manager.
Before you start
If you are downloading the new software from a remote FTP server, check that you have
access to it.
The FTP server integrated in AXC Manager is recommended to be used for remote and
local software download if the new software configuration files are located on the same
PC to which the AXC Manager is installed.
Steps
1

Download and extract the software package.


The AXC download package is a compressed (tar) package that consists of individual
images for the existing units and the Target Build Descriptor file. Download the software
package from NOLS and extract it using an appropriate tool, such as WinZip. Do not
decompress the individual unit software packages (AXU_main.tar, for example).
Make sure that the Target Build Descriptor (TBD) is on the same level in the directory
structure with the SPM directory that accommodates all unit software packages, and
that the TBD and SPM directory structures are consistent. If the SPM directory does not
exist it must be created. Maintain the following directory structure in order not to change
anything in the TBD:
Directory X

TBD
SPM
AXU_main.tar
IFU8P1_main.tar
IFU3S_main.tar
...

Start the download of the new software.


Click Node Software....
The Node Software window opens. In this window you can view all active and inactive
software versions that are currently available in the AXC.

DN70554681
Issue 03B

Id:0900d805806f03da
Confidential

15

Changing AXC software

Expanding and Upgrading AXC

Figure 3

Node Software window before software upgrade

Click Download New SW.... The Download New SW window opens.

Figure 4
3

Downloading new software

If you want to download the new software from a remote FTP server
Then
Configure the remote FTP server.
Select Use Remote FTP Server. If it is not selected, the internal FTP server of the AXC
Manager is used.
Click Set FTP Server... and define the following information for the FTP session:

16

IP address of the FTP server

Id:0900d805806f03da
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Changing AXC software

username for the remote FTP server


password configured for the user

Figure 5

Setting FTP server

Click OK.
4

Download the new software.


If the new node software files are located on the same PC as AXC Manager, click
Browse in the Download New SW window and select the Target Build Descriptor in the
dialog that opens. Click Open.

Figure 6

Selecting software for download

If the new node software files are located on a remote FTP server, enter the path for the
new software in the File name field.
Click Start Download to start downloading the new software.
Local software download takes approximately 5 minutes per unit, or 30 minutes for a
fully equipped 6-slot system. Remote download time depends on the bandwidth and
DCN setup. After the download is complete a message is displayed.
5

Activate the new software.


Click Activate New Downloaded SW..
When you activate the new node software, you lose the connection to the AXC. The
AXC will restart automatically with the previous configuration and the connection can be
restored.

DN70554681
Issue 03B

Id:0900d805806f03da
Confidential

17

Changing AXC software

Expanding and Upgrading AXC

Expected outcome
The new software will be shown in the Active SW Version field of the Node Software
window.

Figure 7

Node Software window after software upgrade

The AXC Manager includes a possibility to initiate a rollback of the software upgrade.
This means that the node will be rolled back to the previous software build without downloading the old software to the node again. To initiate a rollback, click Rollback SW in
the Node Software window.
Note that if you perform a rollback from C6.0 to C5.x, all configuration changes are lost
and the C5.x configuration restored. It is not recommended to perform a rollback if new
units have already been installed to the AXC.
Unexpected outcome
If the AXU does not start up successfully after the software upgrade, the complete node
software will automatically fall back to the previous software build.
Verification
Once the software download and activation is completed the results can be checked
with the AXC Manager. For more information, see Commissioning the AXC with XML
configuration file in Commissioning AXC.
Further information
The procedure for changing the software for single interface units is similar to changing
it for all units. After you have downloaded and extracted the correct software package
and clicked "Activate New Downloaded SW", the software is activated only for the IFU
whose software you are changing.
During the software change the AXU and other interface units remain operational and
the AXC Manager connection to the AXC is not lost.
Make sure that the version of the software you intend to activate is correct. Otherwise
the software of every unit will be upgraded or downgraded and the AXC reboots.

18

Id:0900d805806f03da
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Changing software with AXC-FB Hopper Manager

6 Changing software with AXC-FB Hopper


Manager
Purpose
AXC-FB Hopper Manager can perform several actions on each software unit in the
network element:

showing properties of the software


changing the software user label
erasing the software
activating the software
erasing the pending state of the software
downloading a software file to a unit
validating the software file on the unit
printing the software configuration

The software configuration of a network element is managed through the Software


window of AXC-FB Hopper Manager. The window displays the details of the software
packages installed in the network element.
Note that Transmission Loader (available in NOLS, Nokia Siemens Networks Online
Services) allows the user to upgrade a network of Q1 transmission elements.
Steps
1

Select Maintenance Software View to access the Software window.


To support the software upgrade process, each functional entity (hardware unit) in the
network element contains two or more software banks. Each bank can contain a
software package, but only one of these banks may be active at a time. The software
which is in the active state is the currently running software in the unit. In the most
common situation, one bank contains the active software while others are either empty
or inactive.
New software can only be downloaded into one of the non-active banks. Once the
download is completed, the software must be activated so that it can be used. This
causes a reset of the functional entity which interrupts traffic.

In the Software window, select the software unit from the list.

Download the new software from NOLS.

Check that the downloaded software is now in a Valid state.


If not, validate it manually by selecting Maintenance Software Validate Unit on
the menu or using the toolbar in the window. If the validation process is still not successful, go back to step 2.

DN70554681
Issue 03B

Id:0900d805807d5b81
Confidential

19

Changing software with AXC-FB Hopper Manager

Expanding and Upgrading AXC

Select Maintenance Software Select reset after activation checkbox.

Figure 8

FB Hopper Manager Software window

Click Activate button.


When the software is activated, the functional entity resets automatically and the new
software is launched.
Note that if you activate the software, the traffic is cut.
Further information
Further information is given in the Status and Activity fields. The Activity field shows
whether the software is currently active, inactive or waiting to become active. The
Status shows whether the software is present and if it is valid.
The download process can take some time depending on the speed of the connection
to the unit. You can select the connection speed in Network Element Settings dialogue
box (see Configuring network element settings) according to the type of equipment you
are using. Typically, the download process takes up to 20 minutes using the fastest baud
rate (115 kbit/s) and approximately two hours using the rate 9600 bit/s.
When the download is complete the functional entity attempts to validate the new software. If this process does not succeed, it is possible to retry the validation of the
software manually from the menu of the Software window. The validation process
checks the new software for errors which may have occurred during the download.
Software download does not cause a traffic interruption, but it slows down the management connection to the node. Traffic is cut briefly when new software is activated and
the respective functional entity is reset.

20

Id:0900d805807d5b81
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Changing software with AXC-FB Hopper Manager

g It is mandatory to enable the "reset after activation" checkbox before activating the
inactive software. However, it is not mandatory to check it before downloading the
new software.

DN70554681
Issue 03B

Id:0900d805807d5b81
Confidential

21

Checklist for AXC HW expansion and upgrade

Expanding and Upgrading AXC

7 Checklist for AXC HW expansion and


upgrade
SITE NAME
SITE ID
SITE ADDRESS

AXC ID
Removing interface units
Check

Check mark

Uninstall unit with AXC Manager.


Disconnect all interface cables and remove the unit from the slot.
Refresh the new hardware configuration with AXC Manager.

Adding interface units


Check

Check mark

Insert the unit into the slot.


Connect all interface cables.
Refresh the new hardware configuration with AXC Manager.

Replacing interface units with units of the same type


Check

Check mark

Disconnect all interface cables and remove the unit from the slot.
Insert the new unit into the slot and connect all interface cables.
Check that the configurations have been restored correctly.
Refresh the new hardware configuration with AXC Manager.

Replacing AXU or AXC Compact


Check

Check mark

Take a backup from the current configuration.


Disconnect all cables from the AXU or AXC Compact and
remove it from the slot.
Insert the new AXU or AXC Compact and connect all interface
cables.
Restore the configuration.

22

Id:0900d805806f03e0
Confidential

DN70554681
Issue 03B

Expanding and Upgrading AXC

Checklist for AXC HW expansion and upgrade

Replacing AXUA with AXUB


Check

Check mark

Take a backup from the current configuration.


Disconnect all cables from the AXU and remove it from the slot.
Insert the new AXU and connect all interface cables.
Restore the configuration.
Configure the RNC and BTS AAL2 multiplexing settings in the
AXC.

Replacing DC-PIU
Check

Check mark

Remove all cables from the external interfaces and switch off the
DC-PIU.
Remove the DC-PIU from the slot.
Insert the new DC-PIU into the slot.
Connect the power cables and the alarm cables to the interfaces.

DN70554681
Issue 03B

Id:0900d805806f03e0
Confidential

23