Professional Documents
Culture Documents
TN_AXC_SW_2007_14
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
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:
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)
no problem!
www.online.nokia.com
Company Confidential
5 (9)
Technical Note
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
www.online.nokia.com
Company Confidential
7 (9)
Technical Note
Activate C2.6 SW
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)