Technical Note

TN_AXC_SW_2007_14

Upgrading to AXC C2.7 (RAS05.1)

<AXC> <C2.7>

www.online.nokia.com

Company Confidential

1 (9)

Technical Note

The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation. The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document. Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it. This document and the product it describes are considered protected by copyright according to the applicable laws. NOKIA logo is a registered trademark of Nokia Corporation. Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only. Copyright Nokia Corporation 2007. All rights reserved.

Contact:
Contact to your local Nokia support or axc.systemsupport@nokia.com

Summary of changes:
16th March-2007/ 1.0 / First official version

www.online.nokia.com

Company Confidential

2 (9)

Technical Note

Purpose
This document contains generic information about products. These can be instructions that explain problem situations in the field, instructions on how to prevent or how to recover from problem situations, announcements about changes or preliminary information as requirements for new features or releases.

Keywords
AXC WBTS RNC

Summary and Content

This document describes issues and important things to consider during the network update to RAS05.1 with dedicated focus on the AXC. Important notes and procedures are listed for the following topics: Upgrade path Missing backplane IDs Licence distribution when BP target ID is missing Downgrade with automatic configuration restore Troubleshooting hints

www.online.nokia.com

Company Confidential

3 (9)

Technical Note

SW upgrade path
In case the network is upgraded from RAS05 to RAS05.1 the following steps need to be followed:

Network upgrade from RAS05 to RAS05.1

Upgrade RNC

Upgrade AXC

Upgrade WBTS

Upgrade completed

The reason for upgrading the AXC before the WBTS is the change of the interface protocol between the AXC and WBTS from WAIP (WAM AXU Interface Protocol) version 1 to version 21. The AXC running on C2.7 can handle WBTS WAIP version 1 and 2 requests, whereas a WBTS on WN3.2 requests are based on WAIP version 2. These requests cannot be handled by an AXC which is running on C2.6, since this SWversion can only handle WAIP version 1 requests.

Although the AXC C2.7 can handle WAIP version 1 requests, the basic communication towards the WBTS is based on WAIP version 2. Due to this fact it should be avoided to make any changes of ATM and DCN settings towards the WBTS running on WN3.0. The reason is that the AXC uses WAIP version 2 to apply these changes which the WBTS does not understand with WN3.0.
WAIP version change became necessary to take the RAS05.1 feature RNS-split into use, which affects the relocation of ATM and DCN parameters.
1

www.online.nokia.com

Company Confidential

4 (9)

Technical Note

Due to these significant changes the following chapter summarizes the most important things to keep in mind when the AXC is already running on RAS05.1 level (C2.7), whereas the WBTS is still on RAS05 (WN3.0).

Change of BTS ID, BTS IP in WBTS requires manual synchronization of changes in AXC C2.7 as well, otherwise the BTS falls off air in case of WBTS software download of WN 3.2. - not recommended! Change of AAL2Multiplexing settings (AAL2SIG, AAL2UP and A2EA) in the AXC (when already having BTS AAL2 Multiplexing in use), settings cannot be send to WBTS and therefore these settings need to be synchronized also in WBTS. - not recommended! Enabling BTS AAL2Multiplexing on the AXC will not work in most cases, this depends on WBTS configurations and WN3.0 SW levels. not recommended! Export configuration and subsequent import without configuration changes will result in a WBTS off-air, as AXC takes different default values already into account. - not recommended! (possible workaround is a rollback of AXC to previous software version or subsequent upgrade of WBTS to WN3.2 and re-commissioning)

Reset of AXC works. -

no problem!

www.online.nokia.com

Company Confidential

5 (9)

Technical Note

Missing backplane IDs

In rare cases some backplanes have been detected which are not programmed with valid backplane IDs (serial number, information about the installed WBTS, production date, etc.). If this is detected by the AXC C2.7 it tries to retrieve the WBTS configuration file to adapt its internal settings accordingly. If this is unsuccessful the AXC applies its own setup according to the Ultrasite Supreme WBTS setup. This setting works for most of the available basestation variants, except Metrosite (50) and Triplemode WBTS. To support also these basestations in case the WBTS configuration file cannot be retrieved, a login to the AXC via AXC Manager will be denied. The following message will be displayed:

In this case the AXC webinterface should be started. Under the tools-chapter a link allows the selection of the dedicated backplane.

After setting the backplane a restart of the AXC should be initiated to take over the new settings. Please note: The selection of the basestation will not program the backplane with valid ID. The information is stored locally in the AXUs file system, i.e. whenever the AXU is replaced, it might be necessary to repeat the procedure.

www.online.nokia.com

Company Confidential

6 (9)

Technical Note

Licence distribution when BP ID is missing / invalid

In case the serial number of the AXC backplane has got an empty or invalid identifier, the topology upload operation in NetAct has to be performed. The AXU send in this case its own serial number with the prefix A_ instead of the BP serial number. For detailed instructions about topology update, refer to section Performing Topology Upload in the Configuring NetAct for FM Adaptations document of the NetAct documentation set. After the topology is updated, new licenses for the AXC with the AXUs serial number have to be created and have to be imported to AXC. To update the NetAct license database and to show correct information in reports, licence information within NetAct has to be synchronized. To release the old licences back to the pool for further usage, the pool licence substitute process has to be performed. For instructions, refer to Managing Licences with Network License Managerdocument of the NetAct documentation set.

www.online.nokia.com

Company Confidential

7 (9)

Technical Note

Downgrade with automatic configuration restore

By a downgrade of the AXC from C2.7 to C2.6 a former C2.6 configuration will now be automatically restored. The behaviour is similar to the rollback-functionality which selects the previous installed SW version together with the according configuration. The downgrade with the automatic configuration restore enables one to restore the configuration also through various SW versions, e.g. a downgrade to C2.6 after a SWupgrade to C3.0 via C2.7 will startup C2.6 with the old C2.6 configuration. Any changes applied to a new release cannot be taken back into C2.6. An exception from this mechanism is an AXU delivered with active C2.7 package from the production. After a downgrade to C2.6 it will start with factory default settings. In this case it is recommended to make a combined SW-downgrade, i.e. a SW downgrade plus an configuration import followed by the SW activation. The following flowchart describes the process to follow when executing a combined SW downgrade from C2.7 to C2.6 for an AXU which is delivered from the production with the C2.7 SW image:

Combined SW downgrade from C2.7 to C2.6

Import C2.6 configuration file to AXC running on C2.7 (without activation!)

Download C2.6 SW to AXC

Activate C2.6 SW

AXC starts up with C2.6 SW and C2.6 configuration

www.online.nokia.com

Company Confidential

8 (9)

Technical Note

Troubleshooting hints
This chapter shall simply list some troubleshooting hints which should be taken into account when the AXC is remotely accessible but the WBTS is off air or not accessible.

Alarms of AXC and WBTS should be checked and analyzed according the related alarm manuals. Connection settings towards the WBTS should be checked. Remote reset of the AXC should be considered to synchronize AXC and WBTS again (WBTS restarts itself when AXC is restarted). In case the first restart does not work a second or a third restart should be executed. In case the normal restart is unsuccessful a configuration export followed by a configuration import should be executed. If AXC Manager connection is not working, a web browser session towards the AXC is often possible, because of the use o smaller IPpacket sizes. Via AXC Webinterface it is e.g. possible to retrieve logfiles, to ping other network elements, to restart the AXC, execute MBreset (mainboard reset), recover the AXC (locally), etc. If there are still existing problems, a site visit should be considered with a cold reboot of the whole AXC.

o o

www.online.nokia.com

Company Confidential

9 (9)