Axc Commissioning

8/18/2019 Axc Commissioning

http://slidepdf.com/reader/full/axc-commissioning 1/214

Nokia Siemens NetworksWCDMA RAN, Rel. RU30,Operating Documentation,Issue 01

Commissioning AXC

DN02166645

Issue 23AApproval Date 2010-12-15

Confidential



2 DN02166645Issue 23A

Commissioning AXC

Id:0900d80580815710Confidential

The information in this document is subject to change without notice and describes only theproduct 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 whichthe document is submitted, and no part of it may be used, reproduced, modified or transmittedin any form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

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 liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens 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 NOEVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITEDTO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITYOR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATIONIN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademarkof Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2010. All rights reserved

f Important Notice on Product SafetyElevated 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 personalinjury 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 zwangsläufig bestimmte Teile der Geräte unter Span-nung. Einige Teile können auch eine hohe Betriebstemperatur aufweisen.

Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Körperverlet-zungen und Sachschäden führen.

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

Geräte müssen die zutreffenden Sicherheitsbestimmungen erfüllen.



DN02166645Issue 23A

3

Commissioning AXC


Table of contentsThis document has 214 pages.

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1 Setting up AXC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.1 Installing AXC Manager from NOLS . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2 Uninstalling AXC Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.3 Installing AXC Manager on Linux operating systems by means of com -

mand line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.4 Installing AXC Manager on Linux operating systems by means of GUI 161.5 Configuring network properties of LMT . . . . . . . . . . . . . . . . . . . . . . . . . 171.6 Connecting to AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181.7 Closing connection to AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

2 Prerequisites for commissioning AXC . . . . . . . . . . . . . . . . . . . . . . . . . . 21

3 Commissioning AXC with XML configuration file . . . . . . . . . . . . . . . . . . 22

4 Using AXC Manager as Command Line Tool . . . . . . . . . . . . . . . . . . . . 26

5 Manual commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 305.1 AXC interface configuration constraints. . . . . . . . . . . . . . . . . . . . . . . . . 305.2 Overview of commissioning AXC manually . . . . . . . . . . . . . . . . . . . . . . 325.3 Using the macro recorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.3.1 Recording a macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345.3.2 Running a macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

5.4 Configuring transmission interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.4.1 Configuring PDH interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375.4.2 Configuring IFUC interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395.4.3 Configuring IFUF interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435.4.4 Configuring IFUH interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.4.5 Configuring AXCF interfaces in IP Iub and Dual Iub mode . . . . . . . . . . 525.4.6 Configuring ATM over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565.4.7 Configuring IMA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 615.4.8 Configuring fractional interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645.4.9 Configuring Q1 EOCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 665.4.10 Configuring CES Interworking function . . . . . . . . . . . . . . . . . . . . . . . . . 685.4.11 Configuring CES pass-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715.4.12 Enabling and disabling NND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735.4.13 Configuring Transport mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 745.5 Configuring Timing over Packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 765.6 Configuring synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 785.7 Configuring ATM settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.7.1 Creating traffic descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 825.7.2 Modifying Access Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 855.8 Configuring ATM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885.9 Configuring Iub terminations without AXCF. . . . . . . . . . . . . . . . . . . . . . 915.10 Configuring Iub terminations in ATM and Dual mode with AXCF . . . . . 965.11 Configuring and activating IP Iub mode with AXCF. . . . . . . . . . . . . . . 102



4 DN02166645Issue 23A

Commissioning AXC


5.12 Configuring and activating IP Iub mode with IFUH. . . . . . . . . . . . . . . . 1075.13 Configuring and activating Dual Iub mode with AXCF . . . . . . . . . . . . . 1125.14 Creating ATM cross-connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

5.14.1 Creating Virtual Path cross-connections. . . . . . . . . . . . . . . . . . . . . . . . 1175.14.2 Creating Virtual Channel cross-connections. . . . . . . . . . . . . . . . . . . . . 1195.15 Creating IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215.15.1 Setting public IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1215.15.2 Creating OSPF areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235.15.3 Creating DCN connections for ATM interfaces . . . . . . . . . . . . . . . . . . . 1255.15.4 Creating IP routes with AXCF/IFUH . . . . . . . . . . . . . . . . . . . . . . . . . . . 1295.15.5 Checking IP connectivity. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1335.15.6 Creating DHCP configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1345.15.7 Configuring BTS IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1365.15.8 Configuring Restricted Mode filtering . . . . . . . . . . . . . . . . . . . . . . . . . . 139

5.15.9 Creating NTP servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1435.15.10 Configuring BTS Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1455.16 Configuring Management Protocol for Secure/Unsecured LDAP connec -

tion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1465.17 Installing CA certificates manually for AXC. . . . . . . . . . . . . . . . . . . . . . 1505.18 Installing CA Certificates manually for AXC Element Manager . . . . . . 1535.19 Installing AXC Certificate and AXC private key manually. . . . . . . . . . . 1585.20 Configuring CMP and CR server IP address . . . . . . . . . . . . . . . . . . . . 1605.21 Configuring VLAN Differentiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1635.22 Configuring AXC Q1 Support Function. . . . . . . . . . . . . . . . . . . . . . . . . 1675.23 Configuring loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1695.24 Configuring BFD triggered static rerouting . . . . . . . . . . . . . . . . . . . . . . 1705.25 Configuring Ethernet OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735.25.1 Configuring Link OAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1735.25.2 Configuring Service OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1795.26 IP Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1875.27 Creating BFD sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1915.28 QoS Aware Ethernet switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1965.29 Dynamic routing for Iub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

6 Verifying commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

7 Checklist for AXC commissioning. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212



DN02166645Issue 23A

5

Commissioning AXC


List of figuresFigure 1 Logging in to AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Figure 2 Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 3 Set FTP server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23Figure 4 Activate restored node configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Figure 5 Node configuration activation result. . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Figure 6 Recording a new macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Figure 7 Modify PDH interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Figure 8 Modify IFUC interface, general settings. . . . . . . . . . . . . . . . . . . . . . . . . 39Figure 9 Modify IFUC interface, Trail Trace settings . . . . . . . . . . . . . . . . . . . . . . 40Figure 10 Modify IFUC interface, Protection settings. . . . . . . . . . . . . . . . . . . . . . . 41Figure 11 Modify IFUF interface, general settings . . . . . . . . . . . . . . . . . . . . . . . . . 43Figure 12 Modify IFUF interface, Trail Trace settings . . . . . . . . . . . . . . . . . . . . . . 44

Figure 13 KLM Chooser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Figure 14 Modify VC-12 frame, General settings. . . . . . . . . . . . . . . . . . . . . . . . . . 46Figure 15 Modify VC-12 frame, Trail Trace settings . . . . . . . . . . . . . . . . . . . . . . . 46Figure 16 Modify IFUF interface, Protection settings. . . . . . . . . . . . . . . . . . . . . . . 47Figure 17 Configuring IFUH interface settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Figure 18 Transport Addresses tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Figure 19 Modifying transport Ethernet interface settings . . . . . . . . . . . . . . . . . . . 50Figure 20 Hardware view pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 21 Configuring AXCF interface settings . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Figure 22 Transport Addresses tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Figure 23 Modifying Transport Ethernet Interface settings . . . . . . . . . . . . . . . . . . 54Figure 24 ATM Over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Figure 25 Modifying general ATM Over Ethernet settings . . . . . . . . . . . . . . . . . . . 57Figure 26 Creating a new PSN tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Figure 27 Creating a new Pseudowire. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Figure 28 QoS tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Figure 29 Modify Traffic Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Figure 30 Inverse Multiplexing for ATM (IMA) window. . . . . . . . . . . . . . . . . . . . . . 61Figure 31 Create new IMA group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62Figure 32 Fractional Interfaces window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 33 Create fractional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64Figure 34 Q1 EOCs dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 35 Adding a Q1 EOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Figure 36 Circuit Emulation Service (CES) window. . . . . . . . . . . . . . . . . . . . . . . . 68Figure 37 Add CES Interworking Function - unstructured . . . . . . . . . . . . . . . . . . . 69Figure 38 Add CES Interworking Function - structured . . . . . . . . . . . . . . . . . . . . . 70Figure 39 Circuit Emulation Service (CES) window. . . . . . . . . . . . . . . . . . . . . . . . 71Figure 40 Adding a CES pass-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72Figure 41 Neighbour Node Discovery window. . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Figure 42 Switch Transport Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Figure 43 Timing over Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Figure 44 Modify Timing over Packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Figure 45 Synchronization window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78



6 DN02166645Issue 23A

Commissioning AXC


Figure 46 Adding a synchronization timing source . . . . . . . . . . . . . . . . . . . . . . . . . 79Figure 47 Synchronization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Figure 48 Traffic Descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Figure 49 Creating a new traffic descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Figure 50 Access Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Figure 51 Modifying an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Figure 52 New VP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Figure 53 Creating a new Virtual Path and Virtual Channel . . . . . . . . . . . . . . . . . . 89Figure 54 Iub Terminations to BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Figure 55 Creating a new Common NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Figure 56 Creating a new Dedicated NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Figure 57 Creating a new AAL2 signalling link (BTS AAL2 Multiplexing not in use)93Figure 58 Creating a new AAL2 signalling link (BTS AAL2 Multiplexing in use). . . 94Figure 59 Creating a new AAL2 user path (BTS AAL2 Multiplexing not in use) . . . 94

Figure 60 Creating a new AAL2 user path (BTS AAL2 Multiplexing in use) . . . . . . 95Figure 61 Iub terminations to BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Figure 62 Creating a new Common NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 63 Creating a new Dedicated NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Figure 64 Common NBAP and Dedicated NBAP in Iub Terminations to BTS window

97Figure 65 Creating a new AAL2 signaling link . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98Figure 66 AAL2 signaling link in Iub Terminations to BTS window. . . . . . . . . . . . . 99Figure 67 Creating a new AAL2 user path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Figure 68 AAL2 User Path in Iub Terminations to BTS window . . . . . . . . . . . . . . 100Figure 69 Defining IP Iub settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Figure 70 QoS tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Figure 71 Modifying queue weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Figure 72 Modifying traffic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Figure 73 IP settings - IP Iub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Figure 74 Defining IP Iub settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Figure 75 QoS tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Figure 76 Modifying queue weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Figure 77 Modifying traffic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111Figure 78 Modify Iub IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Figure 79 QoS tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Figure 80 Modifying queue weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114Figure 81 Modifying traffic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115Figure 82 Creating a new Virtual Path cross-connection . . . . . . . . . . . . . . . . . . . 117Figure 83 Creating a new Virtual Channel cross-connection . . . . . . . . . . . . . . . . 119Figure 84 IP Interfaces window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121Figure 85 Setting the public IP address of the AXC . . . . . . . . . . . . . . . . . . . . . . . 122Figure 86 IP Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123Figure 87 Add OSPF area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124Figure 88 IP Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125Figure 89 Adding a DCN for ATM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126Figure 90 OSPF Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

Figure 91 Modifying DCN for LMP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128



DN02166645Issue 23A

7

Commissioning AXC


Figure 92 IP Settings - Routing window - DCN routing . . . . . . . . . . . . . . . . . . . . 130Figure 93 Add IP Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130Figure 94 IP Settings - Routing window - Transport routing . . . . . . . . . . . . . . . . 131

Figure 95 Checking IP connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133Figure 96 IP Settings - DHCP Configurations window. . . . . . . . . . . . . . . . . . . . . 134Figure 97 Adding a DHCP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135Figure 98 IP Settings - BTS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136Figure 99 Configuring BTS IP settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137Figure 100 Restricted Mode Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139Figure 101 Adding a Restricted Mode rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140Figure 102 System Time window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Figure 103 Add NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143Figure 104 Set system time manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144Figure 105 Management Protocol window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146

Figure 106 Modifying Base ID and Parent ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146Figure 107 Add Registration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148Figure 108 Intervals and Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149Figure 109 Registration Service entry in Management Protocol dialog . . . . . . . . . 149Figure 110 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150Figure 111 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Figure 112 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151Figure 113 AXC Element Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153Figure 114 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154Figure 115 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 155Figure 116 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 156Figure 117 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 157Figure 118 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158Figure 119 Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159Figure 120 Automatic Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161Figure 121 Automatic Management window during storing the values . . . . . . . . . 161Figure 122 Transport Addresses tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164Figure 123 Add VLAN interface window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165Figure 124 Modify VLAN mapping window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Figure 125 Setting Q1 Support Function channel . . . . . . . . . . . . . . . . . . . . . . . . . 167Figure 126 Q1 Support Function output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 168

Figure 127 Creating a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Figure 128 Routing tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Figure 129 Add IP Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171Figure 130 Routing tab with IP routes added. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Figure 131 Set route reinstallation delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172Figure 132 Ethernet Link OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Figure 133 Ethernet Link OAM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Figure 134 Add Link OAM Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 175Figure 135 Ethernet Link OAM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 176Figure 136 Ethernet Link OAM window - Ethernet interfaces . . . . . . . . . . . . . . . . 177Figure 137 Modify Ethernet Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177Figure 138 Newly mapped Link OAM profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177



8 DN02166645Issue 23A

Commissioning AXC


Figure 139 Ethernet Link OAM - Link OAM Loopback . . . . . . . . . . . . . . . . . . . . . . 178Figure 140 Modify Remote Loopback Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178Figure 141 Ethernet Link OAM Loopback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178

Figure 142 Ethernet Link OAM window - Link OAM Reset . . . . . . . . . . . . . . . . . . . 179Figure 143 Ethernet Link OAM Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179Figure 144 Service OAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Figure 145 New Maintenance Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180Figure 146 Service OAM - New Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Figure 147 Add New Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Figure 148 Service OAM - New Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182Figure 149 Add New Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183Figure 150 Add Remote Endpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184Figure 151 Service OAM - Service OAM Cir Value. . . . . . . . . . . . . . . . . . . . . . . . . 184Figure 152 Modify OAM CIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185

Figure 153 Service OAM - Insert optional TLV into reply messages . . . . . . . . . . . 185Figure 154 Modify OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186Figure 155 RTT tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187Figure 156 Modify RTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Figure 157 Modify RTT - Reflector on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Figure 158 RTT tab - Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188Figure 159 Modify Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189Figure 160 RTT tab - Session statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190Figure 161 Transport Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191Figure 162 BFD Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Figure 163 Add BFD Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192Figure 164 Transport Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Figure 165 BFD Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194Figure 166 Add BFD Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Figure 167 BFD Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195Figure 168 Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197Figure 169 Modify QoS Classification - DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198Figure 170 Modify QoS Classification - VLAN-PCP . . . . . . . . . . . . . . . . . . . . . . . . 199Figure 171 Ethernet Switching - VLAN aware configuration . . . . . . . . . . . . . . . . . . 199Figure 172 Modify VLAN Aware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200Figure 173 Modify Ethernet Interface Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . 200

Figure 174 Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201Figure 175 Application Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202Figure 176 Modify Application Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Figure 177 Application Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203Figure 178 OSPF tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204Figure 179 Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205Figure 180 OSPF tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206Figure 181 Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Figure 182 OSPF tab - IP Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207Figure 183 Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Figure 184 OSPF tab - IP Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208Figure 185 Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209



DN02166645Issue 23A

9

Commissioning AXC


List of tablesTable 1 Supported VPI/VCI bits . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Table 2 TLS operating mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138Table 3 Filter rules for management plane traffic . . . . . . . . . . . . . . . . . . . . . . 141Table 4 Filter rules for control plane traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Table 5 Filter rules for user plane traffic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Table 6 Base ID and Parent NE ID naming scheme . . . . . . . . . . . . . . . . . . . . 147



10 DN02166645Issue 23A

Commissioning AXC

Id:0900d8058082eaa6Confidential

Summary of Changes

Summary of Changes Changes between document issues are cumulative. Therefore, the latest documentissue contains all changes made to previous issues.

Changes between issues 23 (2010-10-19, WCDMA RAN RU30) 23A (2010-12-15,WCDMA RAN RU30)

Configuring Ethernet OAM (5.25)

– Figures Ethernet Link OAM , Add Link OAM Profile , Ethernet Link OAM Profiles havebeen updated.

– Figures Service OAM , New Maintenance Domain , Service OAM - New Association ,Service OAM - New Endpoint , Add New Endpoint , Add Remote Endpoint , ServiceOAM - Service OAM Cir Value , Modify OAM CIR have been updated.

– Step Configure inserting optional TLV into reply messages. has been added.

IP Network Management (5.26)

– Purpose has been added. – Figures RTT tab and Modify RTT have been updated. – Figure Modify RTT - Reflector on has been added. – Information on recommended UDP destination port number (7) for UDP echo server

has been added to step 3.

QoS Aware Ethernet switching (5.28)

– Figure Modify QoS Classification - VLAN-PCP has been updated.

Dynamic routing for Iub (5.29)

– Step Configure the public IP address has been removed. – Information on activating OSPF with BFD has been added to Enable OSPF and

activate OSPF with BFD.

Changes between issues 22E (2010-08-25, WCDMA RAN RU20) 23 (2010-10-19,WCDMA RAN RU30)

Configuring IFUH interfaces (5.4.4)

– Procedure of modifying transport Ethernet interface settings has been updated (seestep Configure the transport addresses .). Also figure Modifying transport Ether-

netinterface settings has been updated.Configuring AXCF interfaces in IP Iub and Dual Iub mode (5.4.5)

– Information on configuring Bidirectional Forwarding Detection (BFD) has beenre-moved from section Configuring AXCF interfaces in IP Iub and Dual Iub mode .

– Figure Hardware view pane has been added.

Configuring ATM over Ethernet (5.4.6)

– Figure QoS tab has been added. – Figure Modify Traffic Types has been updated.

Configuring Timing over Packet (5.5)

– Figure Timing over Packet has been updated.



DN02166645Issue 23A

11

Commissioning AXC Summary of Changes


Configuring and activating IP Iub mode with AXCF (5.11)

– Figure QoS tab has been added.

Configuring and activating IP Iub mode with IFUH (5.12)

– Figure IP settings - IP Iub has been updated. – Figure QoS tab has been added.

Configuring and activating Dual Iub mode with AXCF (5.13)

– Figure QoS tab has been added. – Figure Modifying traffic types has been updated.

Setting public IP address (5.15.1)

– Figure IP Interfaces window has been updated.

Creating OSPF areas (5.15.2)

– Figure Add OSPF area has been updated. – Information on creating OSPF areas has been updated (see step 3 and 6 ).

Configuring BTS IP settings (5.15.7)

– Figure IP Settings - BTS Settings has been updated.

Installing CA Certificates manually for AXC Element Manager (5.18)

– Section Installing CA Certificates manually for AXC Element Manager has beenadded.

Configuring VLAN Differentiation (5.21)

– Information on setting BFD parameters has been removed from step 4 . – Figure Add VLAN interface window has been updated. – Figure Modify VLAN mapping window has been updated.

Configuring BFD triggered static rerouting (5.27)

– Section Configuring BFD triggered static rerouting has been added.

Configuring Ethernet OAM (5.28)

– Section Configuring Ethernet OAM has been added.

IP Network Management (5.29)

– Section IP Network Management has been added.

Creating BFD sessions (5.30)

– Section Creating BFD sessions has been added.QoS Aware Ethernet switching (5.31)

– Section QoS Aware Ethernet switching has been added.

Dynamic routing for Iub (5.32)

– Section Dynamic routing for Iub has been added.

Changes between issues 22D (2010-05-25, WCDMA RAN RU20) and 22E (2010-08-25, WCDMA RAN RU20)

Configuring AXCF interfaces in IP Iub and Dual Iub mode (5.4.5)



12 DN02166645Issue 23A

Commissioning AXC


Summary of Changes

– Synchronous Ethernet has been added to the list of mechanisms that require atrans-port address (see step 3).

Configuring and activating IP Iub mode with IFUH (5.12)

– Information on release C6.0 On Top has been added to Before you start section.

Configuring BTS Firewall (5.15.10)

– Section Before you start has been updated.

Configuring Management Protocol for Secure/Unsecured LDAP connection (5.16)

– The state of new configuration has been changed from into Active, Next (see Verifi-cation ).



DN02166645Issue 23A

13

Commissioning AXC Setting up AXC Manager

Id:0900d805807f9e01Confidential

1 Setting up AXC Manager

1.1 Installing AXC Manager from NOLSPurpose

You can install the AXC Manager from Nokia Online Services (NOLS). The setupprogram creates all the necessary directories and installs the program and data files onthe Local Management Tool (LMT).

Before you start

Check that:

• you have access to NOLS • the LMT meets the system requirements given in AXC Manager and AXC-FB

Hopper Manager system requirements • you have administrator rights on the LMT

Read the README.TXT file because it contains the latest information on changes in theapplication.

Make backups of all important files on the LMT, including AXC Manager data files.Recent backups are the best security.

It is recommended that you close all other applications before starting the installation.

Steps

1Go to NOLS web page.

2 Create a temp-directory on the LMT.

3 Extract all AXC Manager installation files into this directory.

4 Open the INDEX.HTML file in the temp-directory with your web browser.

The INDEX.HTML file contains instructions for installing AXC Manager. If you do nothave administrative rights on the LMT, an error message is to be generated. From theerror dialog you can select a directory where you have write access and store AXCManager installation files in this directory.

5 Depending on the configuration, it may be necessary to restart the LMT beforerunning AXC Manager for the first time.

Further information

For instructions on uninstalling AXC Manager, refer to Uninstalling AXC Manager .

http://axc_product_description.pdf/






14 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807f9dfbConfidential

1.2 Uninstalling AXC Manager

Purpose

This procedure describes how to uninstall AXC Manager from the Local ManagementTool.

Steps

1 Start AXC Manager Uninstall program.

Start the program from the Start menu ( Start → Programs → Nokia SiemensNetworks → Managers → AXC → Uninstall Managers ).

2 Uninstall the AXC Manager.

Click Uninstall and wait until the uninstallation is complete. You can cancel the processby clicking Cancel .

The uninstallation process removes the software but not data files you have created.Therefore the AXC Manager directory structure may not be automatically removedeither.



DN02166645Issue 23A

15

Commissioning AXC

Id:0900d805807f9dfcConfidential

1.3 Installing AXC Manager on Linux operating systems bymeans of command line

PurposeThere are two options for installing the AXC Manager on Linux operating systems: as aroot user or simply as an AXC user (non-root user). This means that the user does nothave to have special administrative privileges in order for the installation to succeed.See also Installing AXC Manager on Linux operating systems by means of GUI .

The Red Hat Enterprise Linux 4.5.x or higher is the recommended distribution.

Steps

1 Install AXC Manager:

a) Copy the AXC Manager installer file to the Linux computer.The location of the AXC Manager installer file can be freely chosen provided theuser, that is the non-root user in particular has writing rights.

b) If not executable, type chmod +x <filename> .c) To start installation, type ./ <filename> .d) When the installer window opens, click Next .e) Accept the terms of the license agreement and click Next .f) Installing AXC Manager as root user:

• Enter the installation directory for the AXC Manager. The default path is/opt/Nokia Siemens Networks/Managers/AXC/, you can either accept this orchange it.

Installing AXC Manager as an AXC user (axcuser): • Enter the installation directory for the AXC Manager. The default path is/opt/Nokia Siemens Networks/Managers/AXC/, but a regular user rarely has thewriting rights to the directory. This means that you have to install it to a directoryyou have the writing rights to, for examplehome/axcuser/NSN/AXC_Manager/C6.0 .

g) Continue by clicking Next .Please note that when installing the AXC EM as a non-root user, some of the instal-lation files cannot be written to their correct destination directories and as a result,there will be no menu shortcuts created and the executable axcmanager will not beinstalled in the "/usr/local/bin" directory. You will have to complete some additionalsteps to run the program.

h) Once the installation is complete, click Finish .i) Change the current working directory (pwd) to the installation directory. Check if

AXCEMStart.sh in the installation directory is executable. j) If not executable type chmod + x AXCEMStart.sh

Expected outcome

Root user: The AXC Manager can now be started either from the Applications menu,under the chosen installation directory, or from the terminal by typing axcmanager andpressing Enter .



16 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807f9dfdConfidential

1.4 Installing AXC Manager on Linux operating systems bymeans of GUI

Steps

1 Install AXC Manager:

a) Copy the AXC Manager installer file to the Linux computer. The location of the AXCManager installer file can be freely chosen provided the user, that is the non-rootuser in particular has writing rights.

b) Find the installer package with the file manager (Nautilus).c) Right-click on the installer package file and select Properties from the menu.d) Select the Permissions tab.e) Check the Allow executing file as program box and click OK .

f) Double-click on the installer package. A dialog appears to confirm your choice.g) Choose Run on the dialog.

A terminal window extracting the installer opens.h) When the installer window opens, click Next .i) Accept the terms of the license agreement and click Next .

j) Installing AXC Manager as root user: • Enter the installation directory for the AXC Manager. The default path is

/opt/Nokia Siemens Networks/Managers/AXC/ , you can either accept this orchange it.

Installing AXC Manager as an AXC user (axcuser):

• The default path is /opt/Nokia Siemens Networks/Managers/AXC/ , but a regularuser rarely has the writing rights to the directory. This means that you have toinstall it to a directory you have the writing rights to, for examplehome/axcuser/NSN/AXC_Manager/C6.0 .

k) Continue by clicking Next .The installer will now start installing the program. Please note that when installingthe AXC EM as a non-root user, some of the installation files cannot be written totheir correct directories and as a result, there will be no menu shortcuts created andthe executable axcmanager will not be installed in the "/usr/local/bin" directory. Youwill have to complete some additional steps to run the program.

l) Once the installation is complete, click Finish .

m) Browse to the installation directory and locate the file AXCEMStart.sh .n) Right-click on it and select Properties .o) Select the Permissions tab and check the Allow executing file as program .p) Click Close .

Expected outcome

Root user: The AXC Manager can now be started either from the Applications menu,under the chosen installation directory, or from the terminal by typing axcmanager andpressing Enter .



DN02166645Issue 23A

17

Commissioning AXC

Id:0900d805807f9dfeConfidential

1.5 Configuring network properties of LMT

Purpose

Before you can connect locally to the AXC, you have to configure the network interfaceproperties of the Local Management Tool (LMT).

Steps

1 Set the IP address to 192.168.255.130

2 Set the network mask to 255.255.255.128

3 Set the Default gateway to 192.168.255.129



18 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807f9dff Confidential

1.6 Connecting to AXC

Purpose

You can connect to the AXC either locally or remotely. Through the Local ManagementPort (LMP) of the AXU you can access the AXC you are physically connected to. Oncethe Data Communications Network (DCN) has been configured, it is also possible toaccess any AXC node within the same network.

Before you start

Check that:

• you have a crossed Ethernet cable with RJ-45 connector available • you know the IP address of the AXC to be managed (remote connection) • in order to establish a secure connection CA and AXC certificates as well as AXC

private key must be created from certificate authority. All of these have to be

installed in AXC. CA certificate need to be installed in AXC element manager, too.Steps

1 Connect the Local Management tool (LMT) to the LMP with the communicationcable.

2 Start the AXC Manager.

In Windows OS select Start → Programs → Nokia Siemens Networks → Managers→ AXC → AXC Manager. .

In Linux OS select Applications → Nokia Siemens Networks → Managers → AXC → AXC Manager.

3 Login to the AXC.

Select the Connect tab in the Task Selection window.

If you want to establish a local connection, select Local from the IP Address list. If youwant to establish a remote connection, enter the public IP address of the AXC or selectone of the addresses from the list. The list contains the addresses of five AXCs that havebeen previously connected to.

Then enter the username and password to the appropriate fields. The default name isNemuadmin and default password nemuuser .Name and password are case sensitive.

☞ It is recommended to change the default password. For more information seeChanging AXC local account in Operating and Maintaining AXC .

http://general_glossary.pdf/



http://axc_operating_maintaining.pdf/







DN02166645Issue 23A

19

Commissioning AXC

Id:0900d805807f9dff Confidential

4 Click Connect and wait for the connection to be established.

Figure 1 Logging in to AXC

Further information

If you want to shorten the time you have to wait before you can use AXC Manager toconfigure the AXC after establishing a connection, select Use Background Refresh from File → Preferences . To take this feature immediately into use, restart the AXCManager.



20 DN02166645Issue 23A

Commissioning AXC


1.7 Closing connection to AXC

Steps

1 Click File → Disconnect.

2 Save edited data.

If there is edited data that has not been sent to the node, a confirmation message is dis-played. To send this data to the node, click OK .



DN02166645Issue 23A

21

Commissioning AXC Prerequisites for commissioning AXC


2 Prerequisites for commissioning AXCBefore starting to commission the AXC, check that:

• the equipment has been installed according to the instructions • the Local Management Tool (LMT) complies with the hardware and software

requirements specified in AXC Manager and AXC-FB Hopper Manager systemrequirements

• the network properties of the LMT have been set as described in Configuringnetwork properties of LMT

• the AXC Manager has been installed on the LMT as described in Installing AXCManager from NOLS

• AXC-FB Hopper Manager and GCS R4.2 have been installed on the LMT asdescribed in Commissioning FlexiHopper (Plus) and MetroHopper with IFUE (only ifIFUE is installed)

• you have access rights to the managed AXC • you have all the necessary commissioning documentation and information avail-

able.

The commissioning instructions are based on the assumption that the user knows howto use basic computer software.



http://flexihopper_commissioning.pdf/

http://flexihopper_commissioning.pdf/





22 DN02166645Issue 23A

Commissioning AXC


Commissioning AXC with XML configuration file

3 Commissioning AXC with XML configurationfilePurpose

All parameters needed to configure the AXC are defined in the planning phase.

For automated commissioning an XML file containing the necessary parameters iscreated. This XML file can be created for example with NetAct Transmission Planner,which is also the recommended tool for doing I ub dimensioning for the AXC. The resultof this phase is a network element independent XML file.

The XML file is then imported to NetAct Plan Editor that is used to convert the XML fileto an AXC-specific XML configuration file (sometimes referred to as an AML file). WithPlan Editor it is also possible to include additional parameters in the XML file. After thisthe XML file can be exported to the AXC for automated commissioning.

The XML configuration file is transferred from PlanEditor to the AXC either locally orremotely. In local XML file transfer the XML configuration file is transferred directly fromPlanEditor to the Local Management Tool (LMT). The file is downloaded to the AXCwhen the AXC Manager that is installed to the LMT is connected directly to the AXC. Inremote XML file transfer the XML configuration file is transferred to NetAct Radio AccessConfigurator where the Site Configuration Tool (SCT) organises the files to the particularsites. The AXC Manager running in the NetAct Radio Access Configurator transfers theconfiguration file.

Before you start

Check that:

• the XML configuration file has been prepared and is available • license files for application software are available (if necessary) • the AXC has access to the location of the configuration and license files, for example

Local Management Tool (LMT) or a database in NetAct • the prerequisites and restrictions listed in Prerequisites for commissioning AXC and

AXC interface configuration constraints are fulfilled.

You can restore the AXC to factory settings by selecting Tools → Recover in the AXCManager or by using the AXC web interface. For more information, see Accessing AXCwith web browser in Troubleshooting AXC .

Factory settings can be restored only locally, since all configurations in the AXC, includ-

ing the Data Communication Network (DCN) connection, are deleted.The AXC Manager contains a File Transfer Protocol (FTP) server that is used if theXML configuration files or software packages are located on the same PC as the AXCManager. This integrated FTP server does not need to be configured, and it is activatedautomatically when necessary. For remote file transfer an external FTP server has toused.

If the integrated FTP server is used, you must close all other FTP servers running on thesame PC to avoid port conflicts.

If an external FTP server is used, make sure that the XML configuration file is accessibleto the AXC and that the FTP server is online and running.

http://axc_troubleshooting.pdf/










DN02166645Issue 23A

23

Commissioning AXC Commissioning AXC with XML configuration file


Steps

1 Click Node → Import configuration...

The Import Configuration window opens.

Figure 2 Import Configuration

2 If you are downloading the XML file remotely, set the FTP server.

Select Use remote FTP server and click Set FTP server . If the box is not selected, theFTP server integrated in the AXC Manager will be used.

Figure 3 Set FTP server

Define the following information for the FTP session:

• Host: IP address of the FTP server • Username: the relevant username of the remote FTP server • Password: password configured for the user

Click OK .



24 DN02166645Issue 23A

Commissioning AXC


Commissioning AXC with XML configuration file

3 Select the file to be downloaded.

In local download, click Browse and select the XML configuration file in the dialog that

opens.In remote download, enter the path and filename (relative to the root directory of the FTPserver) in the Node configuration field.

The name of the XML file should not contain any blank characters.

If you want to download license files for application software, click Licensed Features .For instructions, see Managing licenses in Maintaining the AXC .

4 Download the file.

Click Start Download in the Node Configuration window to start downloading the file.

After the download is complete, a message is displayed.

5 Activate the configuration.

Activate the XML configuration by clicking Activate .

Figure 4 Activate restored node configuration

Expected outcome

The AXC will reset after activation, and the new configuration will delete all other config-urations.

If the XML configuration file is activated remotely, the AXC loses the DCN connection. After the commissioning is completed, the AXC uses the new DCN connection and reg-isters to NetAct.

Verification

Once the automated commissioning is completed, you can check the results by clickingShow results in the Import Configuration window.





DN02166645Issue 23A

25

Commissioning AXC Commissioning AXC with XML configuration file


Figure 5 Node configuration activation result

In the Node Configuration activation result window you can view the results of the con-figuration activation. All objects that have been deleted and created are shown, as well

as all errors that occurred during parsing. If an error occurs in any line of the XML con-figuration file, the results show where it occurred.

The results can also be viewed using the AXC web interface. For more information, see Accessing AXC with web browser in Troubleshooting AXC .

Further information

For more information on AXC commissioning, see AXC automated commissioningconcept in AXC product description .









26 DN02166645Issue 23A

Commissioning AXC


Using AXC Manager as Command Line Tool

4 Using AXC Manager as Command Line ToolPurpose

Some AXC Manager operations can be executed from a command line. These opera-tions are the following:

• single node configuration import • single node configuration export • node configuration activation • single node software download • node software activation • node software rollback • single node software configuration export • licence file download

• licence deletion • licence status export • hardware information export

In the Command Line Tool mode, all required information is provided in the commandline parameters. The output of the operation, including possible error messages, iswritten into a log file.

The Command Line Tool is started with the command AXCEMStartWithoutCL.bat .You can find the tool in the directory C:\Program Files\Nokia SiemensNetworks\Managers\AXC\NodeManagers\AXCManager<version> .

The following parameters are obligatory for all operations:

• -ne <IpAddress> specifies the IP address of the remote AXC nodeor -ior <ior | filename> specifies either the CORBA IOR or the file that containsthe CORBA IOR

• -pw <username:password> specifies the NWI3 username and password forlogin

The following obligatory parameters specify the operations to be performed:

• -import_conf <filename> specifies the path and filename for the configurationfile to be imported

• -export_conf <filename> specifies the path and filename for the configurationfile to be exported (if the path is not specified, the file is saved to the AXC Managerinstallation directory)

• -activate_conf sends an activate node configuration command to the remote AXC node (can be used simultaneously with the import_conf parameter)

• -download_sw <filename> specifies the path and filename for the Target BuildDescriptor XML file to be downloaded to the remote AXC node

• -activate_sw sends an activate node software command to the remote AXCnode. The parameter can be used simultaneously with -download_sw<filename> .

• -rollback_sw sends a rollback software command to the remote AXC node • -export_sw_conf <filename> specifies the path and filename for the software

configuration to be exported (if the path is not specified, the file is saved to the AXCManager installation directory)



DN02166645Issue 23A

27

Commissioning AXC Using AXC Manager as Command Line Tool


• -download_lic <filename> specifies the path and filename of the licence fileto be downloaded to the remote AXC node

• -delete_lic <filename> sends a delete licence command to the remote AXC

node • -export_lic_status <filename> sends an export licence status command tothe remote AXC node

• -export_hw_information <filename> specifies the path and filename for thehardware information to be exported (if the path is not specified, the file is saved tothe FileStorage folder in the AXC Manager installation directory)

In addition, there are the following optional parameters:

• -ftp <IpAddress:ftpusername:ftppassword> specifies the parameters foran FTP session if the configuration is imported from an external FTP server (if theparameter is not given, the internal FTP server of the AXC is used)

• -cltlog <filename:clear> specifies the path and filename for the CommandLine Tool log file. If the filename is not given, the operation is logged in the defaultclt.log file in the AXC installation directory. <:clear> indicates that the existinglog file is to be cleared. If it is not given, new log entries are added to the end of thelog file.Parameters -cltlog <filename> and -cltlog <:clear> are also possible.

Before you start

Command Line Tool operations are supported over a remote connection only.

The AXC Manager does not return any values to the calling party (DOS command patch,for example).

Steps

1 Import a node configuration.

Give the following command:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-import_conf <filename>

If you want to import and activate the node configuration, give the following command:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-import_conf <filename> -activate_conf

If you want to import the configuration from an external server, give the followingcommand:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-import_conf <filename> -ftp<IpAddress::ftpusername:ftppassword>

The AXC Manager connects to the remote node and imports the node configuration fileusing the internal or external FTP server. After the operation has been executed, AXCManager logs out from the node and closes. Information about the progress of the oper-ation and possible error messages are logged to the log file.

2 Activate a node configuration.




28 DN02166645Issue 23A

Commissioning AXC


Using AXC Manager as Command Line Tool

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-activate_conf

The AXC Manager connects to the remote node and activates the configuration. You

can also combine the import and activation parameters as shown in step 1. If you givethe activation parameter separately, the AXC Manager activates the previously importedconfiguration.

3 Export a node configuration.


AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-export_conf <filename>

The AXC Manager connects to the remote node and exports the node configuration file. An existing file will be overwritten. If the directory structure does not exist, it will be

created.

4 Download new software.

Extract the software package using an appropriate tool, maintaining the directory struc-ture as described in Changing AXC software in Expanding and upgrading AXC . The fileto be downloaded is the Target Build Descriptor XML file.


AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-download_sw <filename>

If you want download new software from an external FTP server, give the followingcommand:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-download_sw <filename> -ftp <IpAddress:ftpusername:ftppassword>

The AXC Manager connects to the remote node and downloads the new software usingthe internal or external FTP server.

If you want to download and activate the software, give the following command:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-download_sw <filename> -activate_sw

5Activate new or inactive software.Give the following command:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-activate_sw

The AXC Manager connects to the remote node and activates the software.

You can also combine the download and activation parameters as shown in step 4. Ifyou give the activation parameter separately, the AXC Manager activates the previouslydownloaded software.

6 Rollback node software.


http://axc_expanding_upgrading.pdf/




DN02166645Issue 23A

29

Commissioning AXC Using AXC Manager as Command Line Tool


AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-rollback_sw

7 Export node software configuration.Give the following command:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-export_sw_conf <filename>

The AXC Manager connects to the remote node and exports the software configurationto a file. If the directory structure does not exist, it will be created.

8 Download a licence file.


AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-download_lic <filename>

If you want download the licence file from an external FTP server, give the followingcommand:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-download_lic <filename> -ftp<IpAddress:ftpusername:ftppassword>

The AXC Manager connects to the remote node and downloads the licence file usingthe internal or external FTP server. The new licence file is taken automatically in use.

9 Delete a licence file.Give the following command:

AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-delete_lic <filename>

1 Export licence status.


AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-export_lic_status <filename>

The AXC Manager connects to the remote node and exports the licence status file(status.xml ) to the FileStorage folder in AXC Manager installation directory.

11 Export hardware information.


AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>-export_hw_information <filename>

The AXC Manager connects to the remote node and exports the hardware informationfile to the FileStorage folder in AXC Manager installation directory.



30 DN02166645Issue 23A

Commissioning AXC

Id:0900d805808176deConfidential

Manual commissioning

5 Manual commissioning

5.1 AXC interface configuration constraintsPhysical and logical interfaces

A logical interface is an interface that has a logical implementation on top of one or morephysical interfaces. In the AXC there are the following logical interfaces:

• Inverse Multiplexing for ATM (IMA) groups • ATM over fractional interfaces (E1/JT1/T1) • Circuit Emulation Service (CES) links

In the AXC, PDH and SDH/SONET interfaces have both a physical and logical imple-mentation.

The maximum number of logical interfaces is 32.Interfaces can be used for ATM traffic only after they have been taken into use with the

AXC Manager. Only those interfaces that are actually used should be taken into use.

It is recommended to take the required STM-1/STS-3c interfaces into use only after alllower capacity interfaces have been unlocked.

VPI/VCI bit allocation

The VPI/VCI bit allocation is modifiable. The table below shows the number of bits sup-ported for VPI and VCI per physical/logical interface.

In AXC and S-AXC, the sum of bits used for VPI/VCI per interface cannot exceed 13.The VPI/VCI bit range can be increased to a maximum of 13 bits in up to 14 interfaces.

Alternatively, the range can be increased to 12 bits in up to 32 interfaces.

In AXC Compact, the number of VCI bits for each logical interface is always 7. Thedefault number of VPI bits is 2. It can be changed as long as the number of logical inter-faces is smaller than 8. The number of VCI blocks required by an interface is 2 to the

power of VPI bits (2 VPI bits ) and the sum of VCI blocks cannot exceed 32. For example,it is possible to have one interface with 3 VPI bits and 6 interfaces with 2 VPI bits (2 3 *1 + 2 2 * 6 = 32).

For an IFUH interface unit used with AXC Compact, the number of VPI bits is always 0,as a consequence only VP0 is supported.

Virtual Channel (VC) values from 0 to 7 are not configurable. Values from 8 to 31 areconfigurable but should not be used. They are reserved by standardisation bodies forother purposes.

VC 21 in Virtual Path (VP) 0 is reserved for Neighbour Node Discovery (NND) which isan ATM end-to-end management feature.

Bits (AXC and S-AXC) Bits (AXC Compact)

VPI 1–8 (default 4) 1–5 (default 2)

VCI 1–12 (default 7) 7

Table 1 Supported VPI/VCI bits











DN02166645Issue 23A

31

Commissioning AXC Manual commissioning

Id:0900d805808176deConfidential

Characters supported by the AXC Manager

0 1 2 3 4 5 6 7

0 NUL SOH STX ETX EOT ENQ ACK BEL

1 DLE DC1 DC2 DC3 DC4 NAK SYN ETB

2 SP ! $ %

3 0 1 2 3 4 5 6 7

4 @ A B C D E F G

5 P Q R S T U V W

6 ` a b c d e f g

7 p q r s t u v w

8 9 A B C D E F

0 BS HT LF VT FF CR SO SI

1 CAN EM SUB ESC FS GS RS US

2 ( ) * + , - .

3 8 9 : ; = ?

4 H I J K L M N O

5 X Y Z [ ] ^ _

6 h i j k l m n o

7 x y z { | } ~



32 DN02166645Issue 23A

Commissioning AXC


5.2 Overview of commissioning AXC manually

Purpose

The AXC can be commissioned either manually or automatically by downloading anXML configuration file to the AXC . In manual commissioning all necessary parametersare configured manually.

Before you start

Check that the prerequisites listed in Prerequisites for commissioning AXC are fulfilled.

Go through the general constraints to be taken into account when commissioning the AXC in AXC interface configuration constraints .

The AXC Manager automatically detects the installed units. It is also possible to installthe unit in the AXC Manager even in cases when the actual IFU hardware is not pluggedin. To do this, click the right mouse button over the appropriate slot in the AXC hardware

image and select the unit from the menu that opens.For more information on the AXC Manager, refer to the online help.

Steps

1 Log in to the AXC with the AXC Manager.

2 Check the software version of the AXC.

You can check the software version in the AXC Manager hardware view by selecting the AXC pane. If you need to change the software version, follow the instructions in

Changing AXC software .

3 Configure the PDH interface settings.

4 Configure the IFUC interface settings.

5 Configure the IFUF interface settings.

6 Configure the IFUH/AXCF interface settings.

7 Configure the ATM over Ethernet settings.

8 Configure the IMA settings.

9 Configure the fractional interfaces.

1 Configure the Q1 Embedded Operation Channels.

11 Configure the synchronization settings.





DN02166645Issue 23A

33

Commissioning AXC


12 Create Traffic Descriptors and modify Access Profiles if necessary.

13 Configure ATM interfaces.

14 Configure the CES Interworking Function and CES pass-through settings.

15 Create Virtual Path and Virtual Channel connections on the ATM interfaces.

16 Configure the Iub Terminations.

17 Configure the public IP address.

18 Add the OSPF areas.

19 Configure the Data Communication Network (DCN) settings.

2 Configure the IP routing.

21 Create the DHCP configurations.

22 Configure the Restricted Mode filtering settings.

23 Configure the BTS IP settings including the BFD settings.

24 Configure NTP servers.

25 Configure the management protocol settings.

26 Configure the AXC Q1 Support Function.

27 Verify the commissioning.

Further information

The AXC Manager contains a Commissioning Check feature which helps you to ensurethat you have performed all the necessary configurations.

You can open the Commissioning Status dialog by selecting Node → CommissioningStatus . You can also view the status information on the toolbar.

Furthermore, it is possible to have AXC Manager check commissioning status wheneveryou are logging out. To do this, select Check Status During Logout and Exit from File → Preferences .



34 DN02166645Issue 23A

Commissioning AXC


5.3 Using the macro recorder

5.3.1 Recording a macro

Purpose

This procedure describes how to record a macro with the AXC Manager. The macrorecorder function of the AXC Manager can be used to record, store, and run sequencesof operations.

For instructions on how to run a recorded macro, see Running a macro .

Steps

1 Click Tools → Macro → Record.

The Record Macro dialogue box opens.

Figure 6 Recording a new macro

2 Enter the name and description for the macro.

The description field is optional, but it is recommended that this field is filled.

3 Save the macro.

Click Save As... and select a directory for the macro. By default, the macro is saved inthe File Storage directory.

4 Start recording the macro.

When you are ready to start recording the macro, click Start . The recording controldialogue appears with the name of the macro visible in the title bar.

When the Macro Recorder is recording, all operations performed with the AXC Managerare recorded in the open macro.

Note that an operation must be completed and successfully sent to the AXC by the AXCManager before it is recorded in the macro.

☞ No software management operations, such as software download or activation ofnew software, should be carried out during macro recording because of differencesbetween software versions.

Refresh, Inspect, Logout and Disconnect are not recorded in the macro.



DN02166645Issue 23A

35

Commissioning AXC


5 If you want to carry out operations on the AXC Manager that you do not want to bestored in the macro

ThenPause recording the macro.

Click Pause to pause recording. You can now carry out operations that will not berecorded in the macro.

Click Resume to resume recording the macro. Operations carried out are now recordedin the macro.

6 Stop recording and store the macro.

Click Stop to stop recording the macro. A request to confirm the action appears. ClickNo to continue recording the macro. Click Yes to save the macro.

7 If you want to delete a macro

Then

Click Tools → Macro → Delete.

The Delete a Macro dialogue box opens. Select the macro you want to delete. Thedialogue provides information about the selected macro.

Click Delete . Confirm the deletion by clicking Yes .



36 DN02166645Issue 23A

Commissioning AXC


5.3.2 Running a macro

Purpose

This procedure describes how to run macros with the AXC Manager. The pre-recordedmacros can be used to run a sequence of operations in order to, for example, commis-sion the AXC or restore its configuration after the hardware has been reset.

For instructions on how to record a macro, see Recording a macro .

Before you start

When executing a macro, the configuration of the AXC should be the same as when themacro was recorded.

Steps

1 Click Tools → Macro → Run.

The Run Macro dialogue box opens. Select the macro you want to run by clickingBrowse...

2 Click Run to run the macro.

Expected outcome

The macro is executed. A progress bar on the Run Macro dialogue box displays theprogress of macro execution. If the macro is executed successfully, the message nextto the progress bar changes to "Completed". You can see the new settings after the AXCManager has performed an automatic refresh.

Unexpected outcome

If the macro execution is unsuccessful, a message box displays with a list of errors thatoccurred during execution. The message next to the progress bar changes to failed.



DN02166645Issue 23A

37

Commissioning AXC

Id:0900d805808176e0Confidential

5.4 Configuring transmission interfaces

5.4.1 Configuring PDH interfaces

Purpose

The PDH interfaces (E1/JT1/T1) can be deployed as:

• standard links • Inverse Multiplexing for ATM (IMA) links • ATM over fractional interfaces • Circuit Emulation Service (CES) links

In addition, Q1 Embedded Operation Channels (EOC) can be configured on the E1and E1 within Flexbus interfaces.

Before you start

The AXC Compact (AXCC and AXCD) does not support fractional interfaces and Q1EOCs.

In the AXC Manager, the IFUE is displayed as an interface unit with 16 E1 interfacesand 3 Flexbus interfaces (greyed out). The ATM part of the IFUE is treated as any otherinterface unit and can therefore be configured with the AXC Manager. Flexbus-relatedconfigurations are performed with the AXC-FB Hopper Manager.

Steps

1 Select the interface in the Hardware view.

Select the appropriate interface in the Interface pane of the Hardware view and clickModify . The Modify Interface window opens.

Figure 7 Modify PDH interface

2 Take the interface into use.

Select In use , ATM interface or both.

Selecting ATM interface enables you to configure ATM settings for the interface.









38 DN02166645Issue 23A

Commissioning AXC

Id:0900d805808176e0Confidential

When the interface is not in use, framing is transmitted but ATM traffic not. Alarms aresuppressed.

If you are planning to include the interface in an IMA group, do not take it into use before

creating the group. The interface is automatically taken into use after you have createdthe IMA group.

3 Check the transmission standard (PDH interface type) and line type.

If necessary, select another standard from the list. The available standards for the PDHinterface units are:

• IFUA: E1, JT1, T1 • IFUD: E1 • IFUE: E1 • AXCC: E1, JT1, T1

• AXCD: E1Frequent switching between interface types may cause problems and should beavoided.

No mixed configurations of E1/JT1/T1 are allowed on the same IFUA or AXCC. If youchange the PDH interface type, the change is applied to all interfaces of the unit andconfigurations are deleted, cutting off all running traffic.

The available line types are the following:

• E1 (IFUA, IFUD, AXCC/D): MultiFrame G704 (default, CRC on), DoubleFrameG704 (CRC off)

• E1 (IFUE): MultiFrame G704

• T1: Extended SuperFrame (default, CRC on), SuperFrame (CRC off) • JT1: Extended MultiFrame

Once you have selected the interface type of the unit to be E1 or T1, you can set the linetype independently for each interface.

4 Modify the Lbo and BER settings.

Modify the settings:

• Line Build Out (Lbo): possible values are 0 dB (default), 7.5 dB and 15 dB. Thehighest Tx power output for the line interface is 0 dB and it can be attenuated in orderto avoid overloading the interface. The Lbo value has to be defined only for JT1 andT1 interfaces.

• Bit error rate (BER) mode: possible values are 10 -3 (default) and 10 -6.

5 Send the changes to the node.

Click OK to send the changes to the node and close the Modify Unit window, or Apply to send the changes but keep the window open.

Further information

For information on how to create loops, see Configuring loopbacks .





DN02166645Issue 23A

39

Commissioning AXC


5.4.2 Configuring IFUC interfaces

Purpose

The SDH/SONET interfaces of the IFUC interface unit can be configured as either STM-1 mapping VC-4 or STS-3c mapping OC-3.

Redundant SDH/SONET links can also be established to protect operational links incase of a failure. The switching type is bi-directional revertive or non-revertive. For moreinformation, see AXC protection options in AXC product description .

Steps


Select the appropriate interface in the Interface pane of the Hardware view and clickModify . The Modify Interface window opens.

Figure 8 Modify IFUC interface, general settings


Select In use , ATM interface or both.

Selecting ATM interface enables you to configure ATM settings for the interface.When the interface is not in use, framing and ATM traffic is transmitted. Alarms are sup-pressed.

3 Switch the laser on if necessary.

Selecting Laser will switch on the laser on the interface. By default Laser is not selected.

4 Check the Interface Type (STM-1/STS-3c).

If necessary, select another Interface Type from the list.





40 DN02166645Issue 23A

Commissioning AXC


A mixture of STM-1 and STS-3c types is allowed on an IFUC. However, if you changethe interface type, all traffic on the interface is cut off and all configurations are lost.

Frequent switching between interface types may cause problems and should be

avoided.

5 Set the BER (Excessive Bit Error Rate) mode.

BER mode indicates the threshold for raising an EBER alarm. Possible values are 10 -3 (default) and 10 -6.

6 Select RDI on EBER if necessary.

Remote Defect Indication (RDI) On EBER means that the appearance of an EBER faultwill trigger the sending of the Remote Defect Indication signal. By default the RDI onEBER is selected.

7 Define the trail trace settings.

Select the Trail Trace pane.

Figure 9 Modify IFUC interface, Trail Trace settings

Select the check boxes as necessary and enter the values for Send ID and ExpectedID. The maximum length for each value is 15 characters.

The Send ID in the local node and the Expected ID in the remote node (and vice versa)have to be identical. If the identifiers do not match, the a larm 61101 (J0) or 61110 (J1)will be raised.

If the Send ID check box is not selected, an empty string will be sent. If the Expected IDis not selected, an empty string will be expected.


Click OK to send the changes and close the Modify Interface window, or Apply to sendthe changes but keep the window open.



DN02166645Issue 23A

41

Commissioning AXC


9 Configure interface protection.

Click Add Protection... from the right side of the Interface pane in the Hardware view.

Figure 10 Modify IFUC interface, Protection settings

Note that IFUC interface protection is application software that requires a valid licence.Click Licensed Features to download a licence.

Select the following if necessary:

• Revertive. If this is selected, the protection switches back to the working interfacewhen the working interface is repaired after a failure. In non-revertive mode, thetraffic will keep running on the protecting line even after the working line has beenrepaired. Non-revertive operation is the default option.

• Lock group. If selected, interface protection is disabled. • Ignore EBER fault as trigger. If selected, an EBER fault will not cause a switch to the

protecting interface. • MSP compatibility mode. Select MSP1:1 if the far end node operates in MSP1:1

mode and MSP1:1 with MSP1+1 Compatibility if the far end node operates inMSP1+1 mode.The AXC supports MSP1:1. MSP1:1 with MSP1+1 compatibility is interoperable withMSP1+1 implemented in the RNC. The AXC also operates with third-party equip-ment supporting MSP1:1 or MSP1+1 compatible with MSP1:n as described inG.783, Annex A.

Select both Protected and Protecting unit and interface from the lists. The Protectinginterface can be either on the same or different unit as the protected interface. If youwant to change the Protected or Protecting unit or interface, first select the interface andclick Delete Protection . Then click Add Protection... to define the interfaces again.

The following rules apply to the Protecting Unit and Interface:

• interface 1 can be protected by interface 1 of any other IFU or any interface 3 • interface 2 can be protected by interface 2 of another IFU or any interface 3 • interface 3 can be protected by interface 3 of another IFU

It is recommended to reserve interface 3 as the Protecting Interface.



42 DN02166645Issue 23A

Commissioning AXC


Unit protection can be implemented easily by using an appropriate configuration:

• interface 1 of the working unit is protected by interface 1 of a protecting unit • interface 2 of the working unit is protected by interface 2 of a protecting unit

• interface 3 of the working unit is protected by interface 3 of the protecting unitThe AXC supports 8 SDH/SONET interfaces and can use up to 7 additionalSDH/SONET interfaces for protection. Interfaces used for protection cannot carry addi-tional ATM user traffic.

A switchover can be performed by clicking Switch Over and cleared by clicking ClearSwitch Over . The actions depend on the states of the protected and protecting inter-faces as follows:

Note that these MSP requests do not necessarily lead to a switchover. A state machineevaluates all local and remote requests and decides by means of a priority table if a swi-tchover has to be done (see Rec. G.841, Table 7-1).

If the protecting interface (in non-revertive mode) remains active even if the original

switch request (such as a manual switch) has vanished (for example by a clear switcho-ver request), a switch back to the protected interface could be accomplished by tempo-rarily putting the group into revertive mode.

Click Protection Statistics to get information on the number and duration of switchesthat have happened between the protected and protecting interfaces.

Further information

For instructions on how to create loops, see Configuring loopbacks .

Interface state Switch Over Clear Switch Over

Protected IF active, noalarms in protecting IF

Switches the traffic to pro-tecting IF

Disabled

Protecting IF active, noalarms in protected IF

Disabled In revertive mode, switchesthe traffic to protected IF (incase a manual switch hasbeen performed). In non-revertive mode, traffic willstay in protecting IF untilalarms are raised on it.

Protecting IF active,alarms in protected IF

Disabled In revertive mode, switchesthe traffic to protected IFwhen all alarms are cleared(in case a manual switch hasbeen performed). In non-revertive mode, traffic willstay in protecting IF untilalarms are raised on it.

Protected IF active, alarmsin protecting IF

Disabled Traffic will stay in protectedIF even if alarms are clearedin protecting IF.



DN02166645Issue 23A

43

Commissioning AXC


5.4.3 Configuring IFUF interfaces

Purpose

The STM-1 interface of the IFUF interface unit provides 63 x VC-12 connections. Themultiplexing structure for STM-1 frame structure is as follows:

• VC-12 > TU-12 > (3x) TUG-2 > (7x) TUG-3 > (3x) VC-4 > AU-4 > AUG-1 > STM-1

In other words, each VC-4 multiplexes three TUG-3, each TUG-3 multiplexes sevenTUG-2 and each TUG-2 multiplexes three TU-12. The resulting 63 instances arenumbered with three indexes:

• K = TUG-3 within VC-4 (1...3) • L = TUG-2 within TUG-3 (1...7) • M = VC-12 within TUG-2 (1...3)

The ATM traffic is transported by means of E1 frames that are mapped into VC-12 virtual

containers. Inverse Multiplexing for ATM (IMA) can be used to combine several E1s toan IMA group. For more information on IFUF, see Support for structured SDH networks in Product Description of AXC .

Redundant SDH links can be established to protect operational links in case of a failure.For more information, see AXC protection options in Product Description .

Steps


Select the interface of the IFUF unit in the Interface pane of the Hardware view. ClickModify . The Modify Interface window opens.

Figure 11 Modify IFUF interface, general settings


Check the In use box.







44 DN02166645Issue 23A

Commissioning AXC


When the interface is not in use, framing and ATM traffic are transmitted. Alarms aresuppressed.

3 Switch the laser on if necessary.Enabling Laser will switch on the laser on the interface. By default Laser is not selected.

4 Define the Path mapping, BER mode and RDI On EBER.

Possible values for Path mapping are Asynchronous (default) and Byte synchronous.

BER mode indicates the threshold for raising an EBER (Excessive Bit Error Rate) alarm.Possible values are 10 -3 (default) and 10 -6.

Remote Defect Indication (RDI) On EBER means that the appearance of an EBER faultwill trigger the sending of the Remote Defect Indication signal. By default the RDI onEBER is selected.

Interface type cannot be modified.

5 Define the trail trace settings.

Select the Trail Trace pane.

Figure 12 Modify IFUF interface, Trail Trace settings


The Send ID in the local node and the Expected ID in the remote node (and vice versa)have to be identical. If the identifiers do not match, the a larm 61101 (J0) or 61110 (J1)will be raised.

If the Send ID check box is not selected, an empty string will be sent. If the Expected IDis not selected, an empty string will be expected.



DN02166645Issue 23A

45

Commissioning AXC



Click OK to send the changes to the node and close thewindow, or Apply to send the

changes to the node but keep the window open.

7 Configure the VC-12 frames.

Select a VC-12 frame from the KLM Chooser or the table and click Modify .

Figure 13 KLM Chooser

The Modify VC-12 Frame window opens.



46 DN02166645Issue 23A

Commissioning AXC


Figure 14 Modify VC-12 frame, General settings

Take the interface in use by selecting In use , ATM interface or both.


You can also take the interface into use by clicking the right mouse button on the framein KLM Chooser and selecting the appropriate item from the menu that opens.

Select the Trail Trace pane and define the trail trace settings.

Figure 15 Modify VC-12 frame, Trail Trace settings


The Send ID in the local node and the Expected ID in the remote node (and vice versa)

have to be identical. If the identifiers do not match, the alarm 61120 will be raised.If the Send ID check box is not selected, an empty string will be sent. If the Expected IDis not selected, an empty string will be expected.

Click OK to send the changes to the node and close the window, or Apply to send thechanges to the node but keep the window open.

8 Configure interface protection.

Click Add Protection... from the right side of the Interface pane in the Hardware view.



DN02166645Issue 23A

47

Commissioning AXC


Figure 16 Modify IFUF interface, Protection settings

Note that IFUF interface protection is application software that requires a valid licence.Click Licensed Features to download a licence.

Select both Protected and Protecting Interface from the lists. Interfaces used for protec-tion cannot carry additional ATM user traffic.

Select the following if necessary:

• Revertive. If this is selected, the protection switches back to the working interfacewhen the working interface is repaired after a failure. In non-revertive mode, thetraffic will keep running on the protecting line even after the working line has been

repaired. Non-revertive operation is the default option. • Lock group. If selected, interface protection is disabled. • Ignore EBER fault as trigger. If selected, an EBER fault will not cause a switch to the

protecting interface. • MSP compatibility mode. Select MSP1:1 if the far end node operates in MSP1:1

mode and MSP1:1 with MSP1+1 Compatibility if the far end node operates inMSP1+1 mode.The AXC supports MSP1:1. MSP1:1 with MSP1+1 compatibility is interoperable withMSP1+1 implemented in the RNC. The AXC also operates with third-party equip-ment supporting MSP1:1 or MSP1+1 compatible with MSP1:n as described inG.783, Annex A.

If you want to change the Protected or Protecting unit or interface, first select the inter-face and click Delete Protection . Then click Add Protection... to define the interfacesagain.

A switchover can be performed by clicking Switch Over and cleared by clicking ClearSwitch Over . The actions depend on the states of the protected and protecting inter-faces as follows:


Protected IF active, noalarms in protecting IF

Switches the traffic to pro-tecting IF

Disabled



48 DN02166645Issue 23A

Commissioning AXC


Note that these MSP requests do not necessarily lead to a switchover. A state machineevaluates all local and remote requests and decides by means of a priority table if a swi-tchover has to be done (see Rec. G.841, Table 7-1).

If the protecting interface (in non-revertive mode) remains active even if the originalswitch request (such as a manual switch) has vanished (for example by a clear switcho-ver request), a switch back to the protected interface could be accomplished by tempo-rarily putting the group into revertive mode.

Click Protection Statistics to get information on the number and duration of switchesthat have happened between the protected and protecting interfaces.

Further information

For instructions on how to create loops, see Configuring loopbacks .

Protecting IF active, noalarms in protected IF

Disabled In revertive mode, switchesthe traffic to protected IF (in

case a manual switch hasbeen performed). In non-revertive mode, traffic willstay in protecting IF untilalarms are raised on it.

Protecting IF active,alarms in protected IF

Disabled In revertive mode, switchesthe traffic to protected IFwhen all alarms are cleared(in case a manual switch hasbeen performed). In non-revertive mode, traffic willstay in protecting IF untilalarms are raised on it.

Protected IF active, alarmsin protecting IF

Disabled Traffic will stay in protectedIF even if alarms are clearedin protecting IF.




DN02166645Issue 23A

49

Commissioning AXC


5.4.4 Configuring IFUH interfaces

Steps


Select the interface of the IFUH unit in the Interface pane of the Hardware view. ClickModify . The Modify Interface window opens.

Figure 17 Configuring IFUH interface settings

Only one interface can be configured at one time on IFUH.

2 Take the IFUH interface in use and modify Speed and Duplex if required.

Click OK / Apply to send settings to the node. Click Cancel to close the dialog.

3 Configure the transport addresses.

The transport address settings are needed for ATM over Ethernet, IP Iub and Timingover Packet.

Click IP → Settings and select the Transport addresses tab.



50 DN02166645Issue 23A

Commissioning AXC


Figure 18 Transport Addresses tab

Select the unit from the list and click Modify... The following dialog opens:

Figure 19 Modifying transport Ethernet interface settings

a) Enter the local IP address and netmask.b) Modify the bandwidth limit if needed.

The physical maximum of Ethernet bandwidth that cannot be exceeded is 100 Mbps.You can select whether you want the bandwidth to either include the Ethernetoverhead or exclude it.



DN02166645Issue 23A

51

Commissioning AXC


c) Take Virtual LAN (VLAN) in use if necessary by checking the VLAN box and enteringthe identifier of the VLAN to which the interface belongs. Possible values range from0 to 4094.

d) Select the active interface.e) Select Include Ethernet overhead.

Click Close to send the changes to the node and close the dialog, or Apply to send thechanges but keep the window open.



52 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807f9e1aConfidential

5.4.5 Configuring AXCF interfaces in IP Iub and Dual Iub mode

Purpose

This procedure describes how to configure AXCF interfaces for IP/Dual configuration.

Steps


Select the interface of the AXCF unit in the Interface pane of the Hardware view.

Figure 20 Hardware view pane

Click Modify. The Modify Interface window opens.

Figure 21 Configuring AXCF interface settings



DN02166645Issue 23A

53

Commissioning AXC


2 Take the AXCF interface in use and modify Speed and Duplex if required.

Click OK / Apply to send settings to the node. Click Apply to close the dialog.

3 Configure the transport addresses.

The transport address settings are needed for IP/Dual Iub, Timing over Packet and BFD.

Click IP → Settings and select the Transport addresses tab.


Select the unit from the list and click Modify... . The Modify Transport Ethernet Interfacedialog opens:



54 DN02166645Issue 23A

Commissioning AXC


Figure 23 Modifying Transport Ethernet Interface settings

1. Select the active interface.

2. Check the IP Enabled field.3. Enter the local IP address and netmask.4. You can select whether you want the traffic shaper to either include the Ethernet

overhead or exclude it.5. Traffic path shaping level : Choose the Traffic path shaping level from the drop

down list. Default is WFQ aggregator. Other options are VLAN interface andShaping off.

6. Shaper IR total : Enter the shaper information rate. Default is 1000 Mbps. Range isfrom 0.1 to 1000 Mbps, in step of 0.1 Mbps.

7. Shaper burst size total : Enter the shaper burst size value. Default is 1522. Rangeis from 1522 to 2000000, in step of 1 octet.

8. Shaper IR : Enter the shaper information rate. Default value is 1000 Mbps. Range isfrom 0 to 1000 Mbps, in step of 1 Mbps.

9. Shaper burst size : Enter the shaper burst size value. Default value is 1522. Rangeis from 1522 to 2000000, in step of 1 octet.

10. Committed IR : The CIR parameter allows to specify bandwidth that is guaranteedfor higher priority PHBs. Default value is 1000 Mbps. Range is from 0.1 to 1000Mbps, in step of 0.1 Mbps.

11. QoS : can be enabled if the quality of service has to be taken into use at Ethernetinterface level.



DN02166645Issue 23A

55

Commissioning AXC


12. For more information on Proxy ARP, see section Enable Proxy ARP .

Click Close to send the changes to the node and close the dialog, or Apply to send the

changes but keep the window open.



56 DN02166645Issue 23A

Commissioning AXC


5.4.6 Configuring ATM over Ethernet

Purpose

This procedure tells you how to configure the ATM over Ethernet settings for IFUH. TheIFUH interface unit provides a mechanism to carry ATM Iub traffic between the BTS andRNC using Ethernet as the physical transmission layer. The traffic is carried within aPacket-switched Network (PSN) tunnel that contains up to six Pseudowires.

IP encapsulation is supported on the tunnel level and the Pseudowire level uses MPLSencapsulation. For more information, see ATM over Ethernet in Product Description of

AXC .

Before you start

Make sure you have configured the IFUH interfaces as described in Configuring IFUHinterfaces .

Steps

1 Open the ATM Over Ethernet tab.

Click ATM Over Ethernet in the ATM View

Figure 24 ATM Over Ethernet ATM Over Ethernet is application software that requires a valid license. Click LicensedFeatures in the ATM Over Ethernet tab to download a license.

2 Configure the general settings for ATM Over Ethernet.

Click Modify . The following dialog opens:





DN02166645Issue 23A

57

Commissioning AXC


Figure 25 Modifying general ATM Over Ethernet settings

Configure Bi-Directional Forwarding Detection (BFD).

BFD is a mechanism that monitors the operation of each Pseudowire by using a controlword. If a broken Pseudowire connection is detected, the alarm 61601 or 61602 israised.

If you want to enable BFD, select Control word in use and define the transmit andreceive interval values. Since BFD messages are conveyed within the Pseudowire, bothends of the connection must support BFD.

Desired minimum transmit interval determines the minimum rate in which BFD controlpackets are sent to the remote system and required minimum receive interval theminimum rate in which BFD control packets are expected to be received from the remotesystem. The negotiated value is MAX [Desired minimum transmit interval (local),Required minimum receive interval (received from the peer)]. A Pseudowire connection

is deemed to have failed after the Detection time has expired. The Detection time isDetection multiplier (received from the peer) x MAX [Required minimum receive interval(local), Desired minimum transmit interval (received from the peer)]. Interval range:[500, 1000, 1500, 2000, 2500, 3000ms]; default: 500ms. Detection Multiplier range: [2-10]; default: 5.

3 Create the PSN tunnel.

Click New PSN Tunnel . The following dialog opens:

Figure 26 Creating a new PSN tunnel

a) Select In use and ATM interface .



58 DN02166645Issue 23A

Commissioning AXC


b) Enter information for Remote IP address.Remote IP address: the IP address of the remote end of the PSN tunnel

c) Click OK to save changes.

After you have created the PSN tunnel, you can test its connectivity by clicking Check in the ATM Over Ethernet tab.

4 Create the Pseudowires.

Select the PSN tunnel from the list and click New Pseudowire . The following dialogopens:

Figure 27 Creating a new PseudowireEnter the following information for the Pseudowire:

• MPLS header label TX and RX: identifiers for the Pseudowire in the Tx and Rx direc-tionsThe identifiers must be unique within the PSN tunnel.

• Max cells per frame: specifies the maximum number of ATM cells to be concate-nated into a single Pseudowire packet, values range from 1 to 28

• Per Hop Behavior: specifies the forwarding treatment of an aggregate traffic stream • Packetization timer: specifies the time that the AXC waits for cells to arrive for con-

catenation into a pseudowire packet before sending it. Possible values range from

240 to 4800 with steps of 240. • Bidirectional Forwarding Detection in use: can be enabled if Control word in use has been selected in the ATM Over Ethernet Settings.

• Bidirectional Forwarding Detection admin up: Select Bidirectional forwarding detec-tion admin up to activate the bidirectional forwarding detection. Bidirectional for-warding detection in use has to be selected before this can be activated.

Note that the concatenation factor configured in the Pseudowire gateway (at the RNC)is recommended to be 18 or less.

Click OK to add the new Pseudowire to the list. The PSN tunnel can contain up to sixPseudowires.



DN02166645Issue 23A

59

Commissioning AXC


5 Map the priorities for the Pseudowire traffic.

Click IP → Settings → Quality of Service tab.

Figure 28 QoS tab

Modify Priority Mappings if necessary. Click Modify Traffic Types to change themapping of Per Hop Behavior to Virtual LAN priorities and define the values for Differ-entiated Services Code Point (DSCP). The Priority Mappings are used for prioritizing thetraffic in VLAN routers and Ethernet switches.

You can select the Per Hop Behavior for each Pseudowire separately. The value rangefor VLAN is from 0 to 7 and for DSCP from 0 to 63. Clicking the Default button restoresthe default values.



60 DN02166645Issue 23A

Commissioning AXC


Figure 29 Modify Traffic Types



DN02166645Issue 23A

61

Commissioning AXC


5.4.7 Configuring IMA settings

Purpose

Inverse multiplexing for ATM (IMA) is a technique by which ATM traffic can be distrib-uted over several lower bandwidth PDH/VC-12 links, and then recombined again at thefar end. IMA groups can be created in IFUA, IFUD, IFUE and IFUF interface units and

AXC Compact (AXCC/D).

For more information on IMA, refer to Inverse Multiplexing for ATM (IMA) .

Before you start

An IMA group has to be created at both ends of the physical link.

Fractional interfaces cannot be used for IMA.

Steps

1 Click Configuration → IMA...

The Inverse Multiplexing for ATM (IMA) window opens.

Figure 30 Inverse Multiplexing for ATM (IMA) window

2 Click New Group... in the Inverse Multiplexing for ATM (IMA) window.

The New IMA Group window opens.







62 DN02166645Issue 23A

Commissioning AXC


Figure 31 Create new IMA group

3 Select the interface unit on which you want to create the IMA group.

4 Select the links to be included in the IMA group.

Select the IMA links to be included in the IMA group from the list of available links usingthe arrow buttons. The links are to be added to the list of Selected links. The links haveto be located on the same IFU. The Group capacity shows the total capacity of the IMAgroup calculated from the selected links.

The maximum number of IMA groups and links is as follows:

• IFUA: 1 to 4 IMA groups, with 1 to 8 E1/JT1/T1 links per IMA group • IFUD: 1 to 4 IMA groups, with 1 to 8 E1 links per IMA group • IFUE: 1 to 8 IMA groups, with 1 to 8 E1 links per IMA group • IFUF: 1 to 16 IMA groups, with 1 to 32 VC-12 links per IMA group • AXCC: 1 to 4 IMA groups, with 1 to 8 E1/JT1/T1 links per IMA group • AXCD: 1 to 4 IMA groups, with 1 to 8 E1 links per IMA group

5 Define the settings for the IMA group.

Define the following settings for the IMA group:







DN02166645Issue 23A

63

Commissioning AXC


• Version ID: version of the IMA standard to be applied: 10 (ATM Forum af-phy-0086.000), 10Alt (ATM Forum af-phy-0086.000, alternative implementation) or 11(ATM Forum af-phy-0086.001). The default and recommended version is 11.IFUF supports versions 10 and 11 only.

• Tx frame length of the IMA group in the transport direction. Possible values are 32,64, 128 (default) and 256. For example, 128 means that one cell is used for IMAmessages and 127 cells for ATM payload. The Tx Frame length must be the sameon both local and remote site.Note that the Tx frame length cannot be modified for an existing IMA group. If youwant to modify it, you have to create a new IMA group. Delete the old group beforecreating a new IMA group.

• Min. link count: the minimum number of IMA links required to keep the IMA groupactive. Possible values range from 1 to the number of configured IMA links. Thedefault value is 1.

• Max. diff. delay: the maximum allowed differential delay in the physical link. Possiblevalues range from 0 to 25 ms. The default value is 25 ms.

• In use: select to take the IMA group into use. • ATM interface: if selected, you are able to configure ATM settings for the interfaces.

The AXC Manager creates the Group ID automatically after checking the alreadyassigned IDs in the slot. The range of IDs is from 33 to 99 per slot, so that 33 is assignedto the first group and incremented by 1 for the next group.


Click OK to close the New IMA Group window. Click New Group... if you want to createanother IMA group.

Click OK to send the changes to the node and close the IMA window, or Apply to sendthe changes but keep the window open.

Further information

You can view the properties of IMA groups and IMA links by selecting the group or linksfrom the tree view on the left. If the unit of the selected IMA group belongs to an interfaceprotection group, the information in each pane is displayed for both the protected andprotecting interface.

When modifying an IMA group that is contained by a protected interface, the changesyou make to the protected interface are automatically applied also to the protecting inter-face. You cannot modify the settings of the protecting interface manually.

The configured and current Tx frame lengths and IMA version IDs might sometimes bedifferent. This happens, for example, if the IMA versions have not been configured to bethe same at both ends of the physical link.

If an IMA group does not function correctly, you can try restarting it by clicking RestartGroup . This has no effect on the traffic in other interfaces.



64 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807f9e2bConfidential

5.4.8 Configuring fractional interfaces

Purpose

PDH interfaces can be configured as fractional interfaces. ATM over fractionalE1/JT1/T1 enables the use of partial E1/JT1/T1 links for the transport of ATM traffic.With the help of an external PDH 64k multiplexer it is possible to combine 3G traffic overthe fractional interfaces with existing 2G traffic without disturbance. For more informa-tion, refer to ATM over fractional E1/JT1/T1 .

Note that fractional interfaces are not supported by AXC Compact (AXCC and AXCD).

Steps

1 Click Configuration → Fractional interfaces...

The Fractional Interfaces window opens.

Figure 32 Fractional Interfaces window

ATM over fractional E1/T1/JT1 is application software that requires a valid license. ClickLicensed Features in the Fractional interfaces window to download a license.

2 Click Add... in the Fractional Interfaces window.

Figure 33 Create fractional interface





DN02166645Issue 23A

65

Commissioning AXC

Id:0900d805807f9e2bConfidential

3 Select the unit and interface on which you want to c reate a fractional interface.

Only interfaces that are not already configured as fractional are shown in the list.


4 Define the Timeslots for ATM traffic.

The timeslots available for E1 are 1 to 31, for JT1 1 to 24 and for T1 1 to 24. Thefragment always starts from timeslot 1 and is continuous. The minimum number oftimeslots for E1 is 1. The minimum number of timeslots for T1 and JT1 is 2.

For E1 interfaces, you can select Use timeslot 16 if the end timeslot is over 15. The useof timeslot 16 is optional for optimising bandwidth utilisation.

Timeslot 16 can be used for Channel Associated Signalling (CAS) in Time-divisionMultiplexing (TDM) networks. In Nokia Siemens Networks 3G RAN, timeslot 16 can

carry Q1 Embedded Operation Channels (EOC).The window displays the capacity of the ATM fragment.

Click OK .


Click Add... if you want to create another fractional interface. Click OK to send thechanges to the node and close the Fractional interfaces window, or Apply to send thechanges but keep the window open.





66 DN02166645Issue 23A

Commissioning AXC


5.4.9 Configuring Q1 EOCs

Purpose

Q1 Embedded Operation Channels (EOC) can be configured on the E1 interfaces onIFUA and IFUD and on the E1 within Flexbus interfaces on IFUE. Via the Q1 EmbeddedOperation Channels within E1 frames, the AXC Q1 Support Function can poll far-endQ1 network elements.

For more information, see Q1 management in AXC product description .

Q1 information can also be mapped to the Flexbus overhead. This can be configuredwith the AXC-FB Hopper Manager. For more information, see Commissioning FlexiHop-

per (Plus) and MetroHopper with IFUE .

Steps

1 Click Configuration → Q1 EOCs...The Q1 EOCs dialog opens.

Figure 34 Q1 EOCs dialog

2 Click Add... in the Q1 EOCs dialog.

The Add... button is enabled if there are E1 or Flexbus interfaces available that do notalready have configured Q1 EOCs, are not configured as fractional interfaces, or are nota part of a CES interworking function.

Figure 35 Adding a Q1 EOC

3 Define the unit and interface of the Q1 EOC.

Define the Unit and Interface of the new Q1 EOC and click OK .







DN02166645Issue 23A

67

Commissioning AXC


Never activate Q1 EOCs between two AXCs as this can cause Q1 bus conflicts.


Click OK to send the changes to the node and close the Q1 EOCs dialog, or Apply tosend the changes but keep the dialog open.

Further information

Configuring AXC Q1 support function .



68 DN02166645Issue 23A

Commissioning AXC


5.4.10 Configuring CES Interworking function

Purpose

Circuit Emulation Service (CES) for structured or unstructured E1/JT1/T1 allows youto map TDM traffic into ATM cells. CES is supported on interface units IFUA, IFUD,

AXCC/D and IFUE (unstructured).

CES is not supported by individual VC-12s of the IFUF unit. Additionally, it is not recom-mended to use CES on ATM over Ethernet.

Interfaces that belong to an IMA group cannot be used for CES.

For more information on CES, see Circuit Emulation Service (CES) in AXC ProductDescription .

Before you start

Create the required Virtual Channels as described in Configuring ATM interfaces .

Up to 32 CES connections can be supported by the AXC. Each CES connection isequivalent to one logical ATM interface.

Up to 8 x structured/unstructured CES is supported on IFUA/D and AXCC/D and up to16 x unstructured CES on IFUE.

A mixed configuration of structured/unstructured CES is allowed on the same IFUA/D or AXCC/D.

Steps

1 Click Configuration → CES...

The Circuit Emulation Service (CES) window opens.

Figure 36 Circuit Emulation Service (CES) window

CES is application software that requires a valid license. Click Licensed Features in theCircuit Emulation Service window to download a license.

2 Click Add... to add a new CES Interworking Function.

The Add CES Interworking Function window opens.







DN02166645Issue 23A

69

Commissioning AXC


Figure 37 Add CES Interworking Function - unstructured

3 Select Interface 1.

Interface 1 is the interface carrying TDM traffic.

Select the Unit and Interface from the drop down lists on the left side of the window.

4 Select Interface 2.

Interface 2 is the interface carrying ATM traffic.

Select the Virtual Channel from the tree view on the right side of the window.

If you want to modify the settings of the Virtual Channel, click Modify ATM .Make sure The Peak Cell Rate (PCR) of the Virtual Channel used for CES is adequate.The minimum PCR for structured CES with partial fill can be calculated with the followingformula:

This allows for a 95 % load of the Virtual Channel. The following are examples of PeakCell Rates needed for VCs carrying CES links:

• E1 unstructured (32 timeslots): 5733 cells/s • E1 structured (31 timeslots): 5554 cells/s • JT1/T1 unstructured and structured: 4300 cells/s

5 Select the Service Type.

Select the Service Type: Structured or Unstructured.

For Structured CES you also have to define the following settings:

• Timeslots used for transporting TDM signals. The available timeslot range for E1 is1 - 31 and for JT1/T1 1 - 24. The timeslot range must be continuous.

• Partial Fill 4 - 47. Partial Fill value is required to limit the delay that is introduced tofill the 47 bytes of AAL1 payload by the segmentation and reassembly function.

Minimum PCR = 8000 xnumber of timeslots

partial fill bytesx

1

0.95



70 DN02166645Issue 23A

Commissioning AXC


Partial fill represents the number of bytes that carry payload (filling bytes). Thesmaller the value, the more dummy bytes need to be inserted.Partial Fill value must be a t least four times the number of timeslots selected forstructured CES. If the number of timeslots is 12 or more, Partial Fill value must be47.

Figure 38 Add CES Interworking Function - structured

Click OK .


Click OK in the Circuit Emulation Service (CES) window to send the changes to the nodeand close the window, or Apply to send the changes but keep the window open.



DN02166645Issue 23A

71

Commissioning AXC

Id:0900d805807f9e2eConfidential

5.4.11 Configuring CES pass-through

Purpose

The Circuit Emulation Service (CES) pass-through function of the AXC is an internalCES function that allows you to perform a TDM cross-connection by setting up a circuitemulation service simultaneously on two AXC interfaces with an associated ATM con-nection. Pass-through is available for inteface units IFUA, IFUD, AXCC/D and IFUE(unstructured).

CES is not supported by individual VC-12s of the IFUF unit. Additionally, it is not recom-mended to use CES on ATM over Ethernet.

Interfaces that belong to an IMA group cannot be used for CES.

For more information, see Circuit Emulation Service (CES) in AXC product description .

Before you start

Up to 32 CES connections can be supported by the AXC. Each CES connection isequivalent to one logical ATM interface.

Up to 8 x structured/unstructured CES are supported on IFUA/D and AXCC/D and up to16 x unstructured CES on IFUE.

A mixed configuration of structured/unstructured CES is allowed on the same IFUA/D or AXCC/D.

Steps

1 Click Configuration → CES...

The Circuit Emulation Service (CES) window opens.

Figure 39 Circuit Emulation Service (CES) windowCES is application software that requires a valid licence. Click Licensed Features in theCircuit Emulation Service window to download a licence.

2 Click Add Pass-through... to add a new pass-through connection.

The Add Pass-through window opens.







72 DN02166645Issue 23A

Commissioning AXC


Figure 40 Adding a CES pass-through

3 Select Interface 1 and Interface 2.

Select the Unit and Interface from the lists for Interfaces 1 and 2 .

4 Select the Service Type.

Select the Service Type: Structured or Unstructured.

For Structured CES, you also have to define the following settings:

• Timeslot used for transporting TDM signals. The available timeslot range for E1 is 1

- 31 and for JT1/T1 1 - 24. The timeslot range must be continuous. • Partial Fill 4 - 47. Partial Fill value is required to limit the delay that is introduced tofill the 47 bytes of AAL1 payload by the segmentation and reassembly function.Partial fill represents the number of bytes that carry payload (filling bytes). Thesmaller the value, the more dummy bytes need to be inserted.Partial Fill value must be a t least four times the number of timeslots selected forstructured CES. If the number of timeslots is 12 or more, Partial Fill value must be47.

Click OK .


Click OK in the Circuit Emulation Service (CES) window to send the changes to the nodeand close the window, or Apply to send the changes but keep the window open.



DN02166645Issue 23A

73

Commissioning AXC

Id:0900d805807f9e2f Confidential

5.4.12 Enabling and disabling NND

Purpose

Neighbour Node Discovery (NND) provides ATM-level topology information to NetAct ATM Manager for building an ATM network view. NND can send information packetsthrough each AXC interface. By default NND is enabled.

Whenever an interface is taken into use, an ATM channel (VPI=0, VCI=21) is automat-ically created for NND. An alarm is generated if this channel is deleted or modifiedwithout disabling NND.

For more information on Neighbour Node Discovery, see Neighbour Node Discovery(NND) in AXC product description .

Steps

1 Click Configuration → NND...The Neighbour Node Discovery window opens.

Figure 41 Neighbour Node Discovery window

The current NND settings and the detected neighbours can be inspected in this window.

2 Enable or disable NND.

Select the interface for which you want to modify the NND settings and click Enable orDisable .

Do not enable NND for interfaces towards the RNC.

3 Refresh the settings.

Click Refresh to refresh the NND settings in the AXC Manager.

After you have taken an interface in use, it takes approximately two minutes before theinformation on the Remote System and Remote Interface becomes available in the AXCManager. After that time, you can click Refresh to make it appear in the NND window.







74 DN02166645Issue 23A

Commissioning AXC


5.4.13 Configuring Transport mode

Purpose

From C6.0 release, AXC starts supporting three transport modes: ATM, IP and Dualmodes. This procedure describes how to set the AXC node into desired Transport modeusing Element Manager. Note that transport mode change with the AXC Manager issupported only in a local connection with AXC Manager.

The procedure below describes transport mode change with AXCF card in the back-plane. By following similar procedure transport mode can be switched to ATM Iub or IPIub with IFUH card in the backplane.

Before you start

Make sure that you take a configuration backup of your system before switching thetransport mode to some other transport mode as this operation causes the node to comeup in factory default state after the reboot.

Steps

1 Select the desired transport mode.

Click Node → Switch Transport Mode.

The following dialog opens.

Figure 42 Switch Transport Mode

2 Set the desired transport mode.

Select the desired transport mode ATM Iub, IP Iub, Dual Iub and Enable/Disable AXCFas per requirement and click Switch to activate the desired mode. The node goes forreboot and loses all the configurations after reboot.

Verification

Once AXC node comes up after reboot check the transport mode using AXC elementmanager in the Hardware View window.

Note the following :



DN02166645Issue 23A

75

Commissioning AXC


• While switching to Dual Iub mode from ATM Iub mode, Enable AXCF checkbox getsenabled automatically and is to be grayed out.

• While switching to IP Iub mode from ATM Iub mode if AXCF is present on the node

(no IFUH is present on the node), Enable AXCF checkbox gets enabled automati-cally and is to be grayed out. • While switching to IP Iub mode from ATM Iub mode if IFUH is present on the node

(no AXCF is present on the node), Enable AXCF checkbox is disabled and grayedout and the user can not switch to Dual Iub mode.

• When AXC node is commissioned in ATM Iub and IP Iub transport mode with AXCFin use and in Dual Iub transport mode, un-installation of the AXCF unit by elementmanager is not possible as it carries Iub termination.

• If the user wants to uninstall AXCF unit carrying Iub termination below options arepossible: – Change the transport mode to ATM Iub or IP Iub without AXCF in use and unin-

stall the card by element manager. Remove the AXCF unit from backplane. – Recover the AXC node and uninstall the card after recovery. Remove the AXCFunit from backplane.

– Commission the AXC node using XML file where Iub termination point is speci-fied as different AXCF card location than the current AXCF card locationcarrying Iub termination (card to be uninstalled from node).

• When AXC node is commissioned in IP Iub transport mode with IFUH, un-installa-tion of the IFUH by element manager is not possible as it causes Iub termination.

• If the user wants to uninstall IFUH unit carrying Iub termination below options arepossible: – Change the transport mode to ATM Iub and uninstall IFUH by element manager.

Remove the IFUH unit from backplane. – Recover the AXC node and uninstall IFUH after recovery. Remove the IFUH unit

from backplane. – Commission the AXC node using XML file where Iub termination point is speci-

fied as different IFUH card location than the current IFUH card location carryingIub termination (card to be uninstalled from node).



76 DN02166645Issue 23A

Commissioning AXC


5.5 Configuring Timing over Packet

Purpose

Timing over Packet provides a way of synchronizing the BTS in Full Ethernet/IP net-works. For more information, see Synchronization of AXC .

Timing over Packet is application software that requires a valid licence. For more infor-mation, see Managing licences .

Before you start

Make sure that the TOPA module has been installed to the IFUH interface unit asinstructed in Installing the TOPA module to the IFUH .

It is not necessary to install a separate TOP module for AXCF as it is inbuilt in the AXCFhardware.

Steps

1 Configure the IFUH/AXCF interface.

See Configuring IFUH interfaces or Configuring AXCF interfaces for detailed instruc-tions.

2 Configure the Timing over Packet settings.

Click IP → Settings and select the Timing over Packet tab.

Figure 43 Timing over Packet

Select the unit that is used for Timing over Packet and click Modify . The following dialogopens:

Figure 44 Modify Timing over Packet









DN02166645Issue 23A

77

Commissioning AXC


Make sure that In Use is selected and enter the IP addresses for Master Clock .

It is recommended to use the default value for Message Rate (16 messages/s).

Click Apply to save the changes.

3 Add Timing over Packet as a synchronization source.

See Configuring synchronization for detailed instructions.



78 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807f9e3dConfidential

5.6 Configuring synchronization

Purpose

To ensure the synchronization of the AXC, you have to configure the recovered timingsource and the timing protection source.

The Radio Network Controller (RNC) provides the primary reference clock source for allother RAN network elements and as the AXC connects the base station to the RNC italso acts as a synchronization interface between the two elements. This is the preferredoption for synchronization.

You can define one primary (active) synchronization timing source and one secondary(stand-by) timing source. If the primary timing source fails, the AXC automaticallyswitches to the secondary source and a warning is to be generated. If no secondarysource is configured or the secondary source fails as well, an alarm is raised. When theprimary source becomes available again, the AXC switches back to it.

If both of these synchronization sources fail, the AXC switches to hold-over mode for upto 24 hours, and after 24 hours to the internal clock (free-run mode). The hold-over modeis not displayed in the AXC Manager.

For more information, refer to Synchronization of AXC in AXC Product Description .

Before you start

If you define a protected interface as a synchronization timing source, the protectinginterface must also be defined as a source. Otherwise, the synchronization cannot beswitched to the protecting interface if the protected interface fails.

Synchronous Ethernet is application software that requires a valid license. For moreinformation, see Managing licenses in Operating and Maintaining AXC .

Steps

1 Click Configuration → Synchronization...

The Synchronization window opens.

Figure 45 Synchronization window







DN02166645Issue 23A

79

Commissioning AXC


2 Click Add... in the Synchronization window.

The Add Synchronization Timing Source window opens.

3 Define the new synchronization timing source.

You can select either Transmission interface, Timing Over Packet , AXU synchroniza-tion input or GPS clock as the timing source type.

Figure 46 Adding a synchronization timing source

Any of the IFUs with an external source can also be used as a secondary Synchronoussource.

Select the Transmission interface option to add a transmission interface (recovered)timing source. This option is selected by default and it enables the Unit and Interface fields.

Unit Select the unit that you want to use as a recovered timing source. Theselection of the unit updates the Interface drop down menu.

Interface The Interface drop down menu depends on the unit ( E1/JT1/T1, STM-1/STS-3c, E1, Flexbus E1, STM-1 VC-12, E1/JT1/T1, E1, AXCF Ether-net).

To select the timing source as Synchronous Ethernet select the Trans-mission Interface , select the Unit as AXCF (as synchronous Ethernetis only supported in AXCF) and select the Interface as Ethernet inter-face.

g If the In use option of the interface is not selected, the interfacecannot be used as a synchronization source. For more information,see Configuring AXCF interfaces in IP Iub and Dual Iub mode .

IFUH does not support Synchronous Ethernet timing source option,it supports only ToP.





DN02166645Issue 23A

81

Commissioning AXC


Figure 47 Synchronization overview

4 Change the priority of synchronization timing sources if necessary.

Select the source whose priority you want to modify and use the arrow buttons to changethe status.


Click OK to send the changes to the node and close the Synchronization window, orApply to send the changes but keep the window open.









DN02166645Issue 23A

85

Commissioning AXC


5.7.2 Modifying Access Profiles

Purpose

An Access Profile defines the maximum bandwidth, and the Virtual Path Identifier (VPI)and Virtual Channel Identifier (VCI) length for an ATM interface . The Access Profilesthat are modified in the New File Access Profile window are stored in an application file,and can be associated to an ATM interface in the Modify ATM Interface window.

Before you start

Read through the information on VPI/VCI bit allocation in AXC interface configurationconstraints .

Unlock at least one physical/logical interface to make Access Profiles visible in the AXCManager.

Note that changing any Access Profile causes a short traffic break on all cross-connec-

tions.Steps

1 Click Configuration → ATM Settings...

Select the Access Profile pane in the ATM Settings window.

Figure 50 Access Profiles

2 Select the desired interface and click Modify...

The Modify Access Profile window opens.









86 DN02166645Issue 23A

Commissioning AXC


Figure 51 Modifying an Access Profile

3 Modify the settings of the Access Profile if necessary.

The bandwidth of an Access Profile may be modified as long as the new bandwidth issufficient to meet all existing traffic contracts. The VPI/VCI value ranges may bemodified as long as the new values do not conflict with those defined for existing VP/VCson the TCTT.

• Name: name of the Access Profile (max. 10 characters) • Use settings from: select an existing Access Profile from the list if you want to use

its settings as a basis • Policing: if you enable policing for an interface, all incoming traffic of the VP/VCs of

the interface is controlled according to the traffic parameters defined in their TrafficDescriptor. UBR.1 discards and UBR.2 tags cells that do not conform to the trafficcontract.☞ Enabling policing is not recommended.

• VPI range and VCI range: see AXC interface configuration constraints .The VPI/VCI value ranges may be modified as long as the new values do not conflict

with those defined for existing VP/VCs on the TCTT.



DN02166645Issue 23A

87

Commissioning AXC


• Configured capacity: set automatically by the AXC Manager depending on the inter-face type.You can decrease the bandwidth to provide aggregate shaping.The bandwidth of an Access Profile may be modified as long as the new bandwidthis sufficient to meet all existing traffic contracts.If ATM interface oversubscription is in use, you can also increase the bandwidth tobe larger than the physical bandwidth. For more information, see ATM interfaceoversubscription in Product Description of AXC .

ATM interface oversubscription is application software and requires a valid licence.Click Licences to download the licence.

ATM interface oversubscription should not be used together with the UBR+ servicecategory.Because of a quantization function used for determining the Access Profile band-width, the actual value is lower than the value that you can see in the AXC Manager,as shown in the table below:

4 Send the changes to node.

Click OK to close the Modify Access Profile window. Click Modify... if you want to modifyanother Access Profile.

In the ATM Settings window click OK to send the changes to the node and close thewindow, or Apply to send the changes but keep the window open.

Bandwidth in AXCManager (cells/s)

Actual bandwidth(cells/s)

9000 9000

10000 9999

14000 13998

17000 16997

20000 19996

50000 49974







88 DN02166645Issue 23A

Commissioning AXC


5.8 Configuring ATM interfaces

Purpose

You have to configure Virtual Channels (VCs) to be able to create ATM AdaptationLayer 2 (AAL2) connections and Data Communications Network (DCN) connections.For more information, see Configuring Iub terminations and Creating DCN connectionfor ATM interface .

Before you start

Make sure that ATM interface in the general settings dialog of the interface is enabled.

Steps

1 Create a new VP on an ATM interface.

First go to the HW view and select the desired interface from the AXC hardware image.Then click the right mouse button in the ATM view and select New VP... from the pop-up menu.

Figure 52 New VP

The AXC Manager creates a new VP on the ATM interface.









DN02166645Issue 23A

89

Commissioning AXC


Figure 53 Creating a new Virtual Path and Virtual Channel

Define the following settings for the VP:

• VPI: the first free VPI is used by default, but you can change it. • Traffic Descriptor: select the Traffic Descriptor from the list

Note that if you change the Traffic Descriptor for an existing Virtual Path, traffic willbe be cut off for about 100 ms in case the bandwidth is higher than 5000 cells/s.

• Supported service categories : enabled if there is one or more VCs created on theVP and the selected traffic descriptor is CBR

• Performance Monitoring: select if necessary • Generate ATM interface disabled fault: select if you want an fault to be raised

whenever the operational state of the interface changes to disabled. This is requiredif ATM Manager is in use.

• Generate utilization zone performance data: select if you want to enable countersthat measure the number of seconds for which the used bandwidth of the interfaceis less than a certain ratio of its maximum bandwidth





90 DN02166645Issue 23A

Commissioning AXC


• Enable utilization threshold fault: if you have enabled utilization zone performancecounters, you can select whether you want the AXC to generate the fault 61095.Define also the threshold for the fault (25, 50, 75 or 87,5%) and the time after whichthe fault is generated.

2 Create new VCs on the VP.

Click New VC to create a new VC on the VP.

Define the following settings for the VC:

• VCI: the first free VCI is used by default, but you can change it. • Traffic Descriptor: select the Traffic Descriptor from the list. • Pseudowire: in case of IFUH, select the Pseudowire for the VC from the list.

It is possible to create up to 10 VCs on each Pseudowire. • Performance Monitoring: select if necessary

• Egress frame discard: select to enable frame discard (Early Packet Discard andPartial Packet Discard) for egress direction☞ Egress frame discard should only be selected if the configured VC is used for

AAL5 traffic. Using Egress Frame Discard on AAL2 channels may result in trafficloss.

3 Send the changes to node.

Click OK to send the changes to the node and close the New VP window, or Apply tosend the changes but keep the window open.

Further information

Note that you can only modify the properties of Virtual Channels that are not terminatedor cross-connected.



DN02166645Issue 23A

91

Commissioning AXC


5.9 Configuring Iub terminations without AXCF

Purpose

This prodecure tells you how to configure the Iub interface between the RNC and theBTS.

Iub terminations are not configured in a stand-alone AXC.

Before you start

BTS AAL2 Multiplexing requires AXUB or AXC Compact. Furthermore, you need a validlicence to take BTS AAL2 Multiplexing into use. For more information, see Managinglicences in Operating and Maintaining AXC .

If BTS AAL2 multiplexing is in use, the combined number of DCN interfaces (includingthe six default DCN interfaces to the WAMs), AAL2 signalling termination points and

ATM interfaces must be 34 or less.

Steps

1 Create the Virtual Paths and Virtual Channels for the Iub terminations.

See the instructions in Configuring ATM interfaces .

Create one VC for Common NBAP connection and one VC per each WAM for DedicatedNBAP connections.

In addition, if BTS AAL2 Multiplexing is not in use, create up to three VCs for each WAM(one VC for the signalling link and one or two VCs for the user paths). If BTS AAL2 Mul-tiplexing is in use, you should create one signalling link and up to seven user paths.

2 Open the Iub Terminations to BTS tab.

Click Iub Terminations to BTS in the ATM View.

Figure 54 Iub Terminations to BTS







92 DN02166645Issue 23A

Commissioning AXC


3 Create the Common and Dedicated NBAP connections.

Click New Common NBAP and New Dedicated NBAP and select a Virtual Channel

from the dialog that opens. For each Dedicated NBAP connections, you have to definethe WAM.

Figure 55 Creating a new Common NBAP

Figure 56 Creating a new Dedicated NBAP

4 Click BTS AAL2 Multiplexing to enable BTS AAL2 Multiplexing if necessary.

Enabling or disabling BTS AAL2 Multiplexing always deletes any existing AAL2 signal-

ling links and user paths.



DN02166645Issue 23A

93

Commissioning AXC


5 Configure AAL2 signalling links.

Click New AAL2 Signalling .

If BTS AAL2 Multiplexing is not in use, a signalling link for each WAM must be config-ured. Select a Virtual Channel from the tree and the WAM for which you want to createthe link. Enter also the AAL2 End Address.

If you select Autocalculation Method to be other than Manual, the AXC Manager willsuggest a value for the End Address. You can also modify the suggested address.

Note that the address can only be suggested if you have defined the BTS identifier. ClickBTS Settings in the IUB Terminations to BTS tab to define the BTS IP settings. Forinstructions, see Configuring BTS IP settings .

Figure 57 Creating a new AAL2 signalling link (BTS AAL2 Multiplexing not in use)

If BTS AAL2 Multiplexing is in use, one signalling link is enough. Select a VirtualChannel from the tree and the WAMs that are in use.

Enter also the AAL2 End Address for each WAM. If you select Autocalculation Methodto be other than Manual, the AXC Manager will suggest a value for the End Address.

Select STC Alarm in Use to enable alarm 61260 STC connection to signalling peer not

established in cases where the link towards the RNC is not functioning. You can alsoenable Performance Monitoring if necessary.



94 DN02166645Issue 23A

Commissioning AXC


Figure 58 Creating a new AAL2 signalling link (BTS AAL2 Multiplexing in use)

6 Configure AAL2 user paths.

Click New AAL2 User Path .

If BTS AAL2 Multiplexing is not in use, you can configure one or two user paths for eachWAM. Select a Virtual Channel from the tree and enter the Path Identifier and Usage.

The allowed values for Usage are DCH & HSDPA, DCH, HSDPA, HSUPA, and HSPA.With the values Shared DCH & HSDPA or DCH, you have to configure at least one userpath for each WAM.

If you select Autocalculation Method to be other than Manual, the AXC Manager willsuggest a value for the Path Identifier.

Figure 59 Creating a new AAL2 user path (BTS AAL2 Multiplexing not in use)

If BTS AAL2 Multiplexing is in use, you can configure up to seven user pa ths towards

the BTS.



DN02166645Issue 23A

95

Commissioning AXC


Select a Virtual Channel from the tree and enter the Path Identifier. If you select Auto-calculation Method to be other than Manual, the AXC Manager will suggest a value forthe identifier.

The allowed values for Usage are DCH & HSDPA, DCH, HSDPA, HSUPA, and HSPA.With the values Shared DCH & HSDPA or DCH, you have to configure at least one userpath for the BTS.

Define the Timer Cu (Composite Unit). After the expiry of this timer, even a partially filled ATM cell will be transmitted. Possible values range from 0 to 31 ms, with steps of 1 ms.The default value is 2 ms. It is not recommended to change this value.

You can also enable Performance Monitoring if necessary.

Figure 60 Creating a new AAL2 user path (BTS AAL2 Multiplexing in use)

7 Activate the settings.

Click Activate BTS settings to take the new settings in use. It is recommended that youactivate the settings only after you have configured both Iub terminations and BTS IPsettings.

Further information

AAL2 signalling (STC alarm, Performance Monitoring and used WAMs with A2EA) anduser paths (Performance monitoring) can be modified only when BTS AAL2 Multiplexingis enabled. NBAP terminations cannot be modified at all.

Note that deleting an Iub termination does not delete the Virtual Channel or Termination.Deleting a signalling link deletes also the related user paths.

Deleting a signalling link does not delete virtual channel or termination.





DN02166645Issue 23A

97

Commissioning AXC


3 Create the Common and NBAP connections.

Click New Common NBAP and New Dedicated NBAP and select a Virtual Channel

from the dialog that opens. In default state WAM2 remains as telecomm master.

Figure 62 Creating a new Common NBAP

Figure 63 Creating a new Dedicated NBAP

Figure 64 Common NBAP and Dedicated NBAP in Iub Terminations to BTS window



98 DN02166645Issue 23A

Commissioning AXC


4 BTS AAL2 Multiplexing checkbox will be enabled and grayed out in Dual Iub modeas AAL2 multiplexing is always enabled by default.

5 Configure AAL2 signaling links.

Click New AAL2 Signaling

Select a Virtual Channel from the tree to create the Iub link.

Configure AAL2 signaling parameters:

• STC fault in use: By selecting STC fault in use you can enable the STC fault indi-cation. The alarm "STC Connection to signaling peer not established" is triggered atfault condition only if this checkbox is checked.

• Performance monitoring: Select Performance monitoring if you want to enable theperformance monitoring.

Configure AAL2 end addresses parameters:

• Autocalculation method: Choose method for autocalculation from combo box. Thechosen method will be used when A2EA and PID values are being suggested. Ifchosen value is "Manual" no values are being suggested.Values: 1 VCC for WAM, N VCC for WAM and Manual, default N VCC for WAM.

• AXCF: When AXCF is in use only AXCF can be selected for A2EA.

Note that the address can only be suggested if you have defined the BTS identifier. ClickBTS Settings in the Iub Terminations to BTS tab to define the BTS IP settings. Forinstructions, see Configuring BTS IP settings .

Figure 65 Creating a new AAL2 signaling link

If BTS AAL2 Multiplexing is in use, one signaling link is supported.

You can modify the Signaling link by selecting the Signaling Link and clicking on Modify .

While modifying the Signaling link you can not modify the VP/VC termination used forcreation of Signaling link.



DN02166645Issue 23A

99

Commissioning AXC


User can delete the Signaling link by selecting the Signaling Link and clicking on Delete .

Figure 66 AAL2 signaling link in Iub Terminations to BTS window

6 Configure AAL2 user paths.

Click New AAL2 User Path.

In Dual Iub mode user can create maximum up to eight user paths.

Select a Virtual Channel from the tree to create the User Path.

Configuring AAL2 user path parameters:• Path identifier: Enter the path identifier in this field. PID identifies the used ATM

virtual channel inside the ANI. PID has to be unique within each signaling link. PIDcan be autocalculated.

• Timer Cu: Enter the Timer Cu value in this field. The value can be 0 - 31 ms. Thedefault and recommended value is 2 ms. Timer Cu (composite unit timer) is themaximum delay for an incomplete ATM cell to be transmitted in ATM adaptationlayer type 2 (AAL2).

• Usage: Select the appropriate usage method: DCH & HSDPA, DCH, HSDPA,RTDCH, NRTDCH, HSUPA, and HSPA.

• Performance monitoring: Select Performance monitoring if you want to enable the

performance monitoring. • ATM Quality of Service: In this table you can modify the queue weights. The rows

in the table are always enabled and the weight is a mandatory parameter for eachqueue. AXC Manager proposes default values for weight parameters when new

AAL2 User Path is created. Range for weight is 1..1000, and 1000 means highestpriority and 1 lowest priority. Following values are the defaults for weight parame-ters:Q1: Strict queue, weight is not modifiableQ2: 1000Q3: 500Q4: 1

Default: This button sets the default queue weight values in the Quality of Servicetable.



100 DN02166645Issue 23A

Commissioning AXC


The Quality of Service table is visible only if:

• AXCF is in use in ATM and Dual Iub mode.

With AXCF enabled AAL2 multiplexing is always enabled in ATM and Dual Iub mode.

Figure 67 Creating a new AAL2 user path

You can modify the User Path by clicking on Modify .

While modifying the User Path you can modify only the Performance Monitoringcheckbox and QoS parameters.

User can delete the User Path by selecting the desired User Path and clicking onDelete .

Figure 68 AAL2 User Path in Iub Terminations to BTS window



DN02166645Issue 23A

101

Commissioning AXC


7 Activate BTS settings.

Click Activate BTS Settings to take the new settings in use. It is recommended that you

activate the settings only after you have configured both Iub terminations and BTS IPsettings.

Further information

AAL2 signaling (STC alarm, Performance Monitoring) and user paths (Performancemonitoring) can be modified only when BTS AAL2 Multiplexing is enabled. NBAP termi-nations cannot be modified at all.

Note that deleting an Iub termination does not delete the Virtual Channel or Termination.Deleting a signaling link deletes also the related user paths. Deleting a signaling linkdoes not delete virtual channel or termination.



102 DN02166645Issue 23A

Commissioning AXC


5.11 Configuring and activating IP Iub mode with AXCF

Purpose

The AXC has three different transport modes: the normal ATM Iub, IP Iub and Dual Iubmode. The transport mode is changed by downloading an XML configuration file with IPIub settings in the AXC and activating it or using element manager as described in Con -figuring Transport mode section. When the transport mode is IP Iub, the ATM configu-ration is not needed and ATM interfaces can be used only for synchronization. Only alimited number of AXC Manager functions are therefore available. IP Iub is applicationsoftware that requires a valid license in the RNC.

Before you start

The following IP addresses cannot be configured with the IP Iub transport mode:

• 127.0.0.0 / 8

• 255.255.255.255 • 224.0.0.0 / 8 • 192.168.254.0 / 24 • 192.168.255.0 / 25 • 192.168.255.128 / 25

Furthermore, it is recommended that the following addresses are not configured:

• zero addresses from 0.0.0.0 to 0.255.255.255 • Class E addresses (reserved for future use) • Class D addresses (Multicast) from 225.0.0.0 to 239.255.255.255• Network address, for example 128.143.0.0

Steps

1 Set the transport mode of AXC using XML configuration file or via ElementManager.

For instructions, see Commissioning AXC with XML configuration file or ConfiguringTransport mode . If the XML configuration file does not contain the IP Iub settings, con-figure them as described in the following steps.

2 Configure the AXCF interfaces.

For instructions, see Configuring AXCF interfaces in IP Iub and Dual Iub mode .

3 Configure IP Iub settings.

Click IP → Settings and select the IP Iub tab.

Click Modify to open the following dialog.





104 DN02166645Issue 23A

Commissioning AXC


Figure 70 QoS tab

1 Modifying Queue Weights

Click Modify Queue Weights .

Select an appropriate value (0-10000) for each queue type. The list of default valuecontain 1, 10, 100, 1000, and 10000.



DN02166645Issue 23A

105

Commissioning AXC


Figure 71 Modifying queue weights

Click OK to send the settings to the node and Close to close the d ialog.

Click Default to restore the settings to default value.

2 Modifying Traffic Types

Click Modify Traffic Types.

Select the VLAN priority and enter the DiffServ Code Point (DSCP) values for eachtraffic type.

Figure 72 Modifying traffic types



106 DN02166645Issue 23A

Commissioning AXC


The values for DSCP range from 0 to 63. You can enter several values for user planetraffic types and only single DSCP value to other traffic types, but since each DSCPvalue refers to the same Per Hop Behavior value across the entire table, each valuecan be used only once. The value 0 is always mapped to Best Effort.

Click OK to send settings to the node. Click Close to close the dialog.

Click Default to restore the settings to default values.

5 Configure other settings, such as synchronization and Management Protocol.

Note the following :

The user can not assign same DSCP value for two or more Per Hop Behavior entries.

Multiple DSCP values are allowed only for traffic types SG1, SG2, SG3, SG4, SG5 andSG6.

DSCP value zero is reserved for Best Effort traffic.



DN02166645Issue 23A

107

Commissioning AXC


5.12 Configuring and activating IP Iub mode with IFUH

Purpose

The AXC has two different transport modes when working with IFUH: the normal (ATM)mode and IP Iub mode.

The transport mode is changed by downloading an XML configuration file with IP Iubsettings in the AXC and activating it. Note that the transport mode can also be changedwith the AXC Manager, but this is only supported in a local connection with AXCManager.

When the transport mode is IP Iub, the ATM configuration is not needed and ATM inter-faces can be used only for synchronization. Only a limited number of AXC Managerfunctions is therefore available. In IP Iub mode no ATM crossconnect functionality isavailable.

Upgrade scenario to IP Iub must be started with the outmost AXC in the chain towardsRNC.IP Iub is application software that requires a valid licence in the RNC.

Before you start

The following IP addresses cannot be configured with the IP Iub transport mode:

• 127.0.0.0 / 8 • 255.255.255.255 • 224.0.0.0 / 8 • 192.168.254.0 / 24 • 192.168.255.0 / 25

• 192.168.255.128 / 25Furthermore, it is recommended that the following addresses are not configured:

• zero addresses from 0.0.0.0 to 0.255.255.255 • Class E addresses (reserved for future use) • Class D addresses (Multicast) from 225.0.0.0 to 239.255.255.255 • network address, for example 128.143.0.0

Note that in IP Iub mode the IFUH can only route IP packets to the first eight addressesof a configured public LMP subnet, though it is possible to configure host addressranges outside the mentioned first eight addresses while still being in the same subnet.

Note also that prior to switching the transport mode to IP Iub you should have done the

following: • IFUH has been installed to AXC C6.0/ AXC C6.0 On Top/AXC C7.0. • Ethernet network has been connected to IFUH. • Existing AXC has been upgraded to C6.0/C6.0 On Top/C7.0 (including IFUH).

Steps

1 Download and activate the XML configuration file.

For instructions, see Commissioning AXC with XML configuration file .

If the XML configuration file does not contain the IP Iub settings, configure them as

described in the following steps 3-6.



108 DN02166645Issue 23A

Commissioning AXC


2 Switch the transport mode to Iub IP in local connection with AXC Manager.

Click Node → Switch Transport Mode and select Iub IP in the dialog that opens. Click

Switch... to change the transport mode.Note that you must be connected locally in order for this to be possible and that switch-ing the transport mode causes a reboot where all existing configurations will be removedand the traffic interrupted.

After the reboot is finished continue from step 3 onwards.

3 Configure the IFUH interfaces.

For instructions, see Configuring IFUH interfaces .



Figure 73 IP settings - IP Iub

Click Modify... to open the following dialog:



DN02166645Issue 23A

109

Commissioning AXC


Figure 74 Defining IP Iub settings

Define the following settings:

• Far End SCTP Address and Far End SCTP Subnet • Minimum SCTP Port: possible values range from 49152 to 65529.

Note that the BTS is reset if you modify the value of Minimum SCTP Port. • Minimum UDP Port: possible values range from 49152 to 63135.

It is recommended that you do not change the value of Minimum UDP Port during AXC operation. Otherwise calls might be lost.

• CAC Committed Bit Rate: possible values range from 0.4 to 100 Mbps in 0.1 Mbpssteps.

• Signaling Bit Rate: possible values range from 50 to 1000 Kbps in 50 Kbps steps. • DCN Bit Rate: possible values range from 50 to 1000 Kbps in 50 Kbps steps.

Click Close to send the changes to the node and close the dialog, or Apply to send thechanges but keep the window open. Click Activate BTS Settings in Iub IP tab toactivate the settings.

5 Configure the Quality of Service settings.

Click IP → Settings and select the Quality of Service tab.



110 DN02166645Issue 23A

Commissioning AXC


Figure 75 QoS tab



Select an appropriate value (0-10000) for each queue type.


Click OK to send the settings to node and Close to close the dialog.



Click Modify Traffic Types .



DN02166645Issue 23A

111

Commissioning AXC




The values for DSCP range from 0 to 63. You can enter several values for user planetraffic types and only single DSCP value to other traffic types, but since each DSCP

value refers to the same Per Hop Behavior value across the entire table, each valuecan be used only once. The value 0 is always mapped to Best Effort.






112 DN02166645Issue 23A

Commissioning AXC

Id:0900d805808178feConfidential

5.13 Configuring and activating Dual Iub mode with AXCF

Purpose

The AXC has three different transport modes: the normal ATM Iub, IP Iub and Dual Iubmode. The transport mode is changed by downloading an XML configuration file withDual Iub settings in the AXC and activating it or using element manager as described insection Configuring Transport mode .

When the transport mode is Dual Iub, BTS has two Iub links towards RNC: one ATM Iublink and other is IP Iub link. Control plane and Management plane traffic goes over ATM.HSPA calls flows over IP path and VMR/Voice calls flows over ATM path.

Dual Iub is application software that requires a valid licence in the RNC. In order toactivate the Dual Iub mode AXCF card must be physically present on the node.

Before you start

The following IP addresses cannot be configured with the IP Iub transport mode: • 127.0.0.0 / 8 • 255.255.255.255 • 224.0.0.0 / 8 • 192.168.254.0 / 24 • 192.168.255.0 / 25 • 192.168.255.128 / 25

Furthermore, it is recommended that the following addresses are not configured:

• zero addresses from 0.0.0.0 to 0.255.255.255 • Class E addresses (reserved for future use) • Class D addresses (Multicast) from 225.0.0.0 to 239.255.255.255• Network address, for example 128.143.0.0

Steps

1 Set the transport mode of AXC using XML configuration file or via ElementManager.

For instructions, see Commissioning AXC with XML configuration file or ConfiguringTransport mode . If the XML configuration file does not contain the IP/ATM Iub settings,configure them as described in the following steps.

2 Configure the AXCF interfaces.

For instructions, see Configuring AXCF interfaces .



Click Modify to open the following dialog.



DN02166645Issue 23A

113

Commissioning AXC


Figure 78 Modify Iub IP


• Minimum UDP port: possible values range from 49152 to 63135.It is recommended

that you do not change the value of Minimum UDP Port during AXC operation. Oth-erwise calls may be lost. This port is used for user plane call establishment.

• CAC committed bit rate: possible values range from 0.4 to 100 Mbps in 0.1 Mbpssteps. This is used for control plane call establishment.

• External NAT IP address: This is external BTS IP address provided to the RNC asUser Plane BTS IP address during NBAP signaling.

Click Apply to send the changes but keep the window open or Close to close the dialogwithout sending changes to node.

4 Configure the Quality of Service settings

Click IP → Settings and select the Quality of Service tab.



114 DN02166645Issue 23A

Commissioning AXC


Figure 79 QoS tab



Select an appropriate value (0-10000) for each queue type.




DN02166645Issue 23A

115

Commissioning AXC





Click Modify Traffic Types .



The values for DSCP range from 0 to 63. You can enter several values for user planetraffic types and only single DSCP value to other traffic types, but since each DSCPvalue refers to the same Per Hop Behavior value across the entire table, each valuecan be used only once. The value 0 is always mapped to Best Effort.

Click OK to save the settings.

Click Close to close the dialog.

Click Defaults to restore the values to default settings.

5 Configure ATM Iub settings.

For instructions, see Configuring Iub terminations in ATM and Dual mode with AXCF .


Note the following:

User cannot assign same DSCP value for two or more Per Hop Behavior entries.

Multiple DSCP values are allowed only for traffic types SG1, SG2, SG3, SG4, SG5, and

SG6.



116 DN02166645Issue 23A

Commissioning AXC


DSCP value zero is reserved for Best Effort traffic.



DN02166645Issue 23A

117

Commissioning AXC


5.14 Creating ATM cross-connections

5.14.1 Creating Virtual Path cross-connections

Purpose

This procedure describes how to create Virtual Path cross-connections. The AXCsupports semi-permanent Virtual Path cross-connections.

Before you start

Before creating any cross-connections, read through AXC interface configuration con -straints .

Steps

1 Select the ATM view by clicking View → ATM View.If the bottom view is not visible, click the small arrow pointing upwards at the bottom leftof the ATM view.

2 Click New in the bottom view.

The New Cross-connection window opens.

Figure 82 Creating a new Virtual Path cross-connection

3 Define the termination points.

Perform the following tasks on both interfaces you want to cross-connect.

Select the Unit and Interface (IF) on which you want to create a cross-connection fromthe list. Click New VP . A new Virtual Path is created on the interface.



118 DN02166645Issue 23A

Commissioning AXC


4 Select a Traffic Descriptor and Supported Service Categories for the VP.

Select a Traffic Descriptor from the list of predefined Traffic Descriptors or click ATM

Settings to create a new Traffic Descriptor. For more information see Creating TrafficDescriptors .

Select the Supported service categories. The check boxes are enabled if the selectedVP has at least one VC and the selected Traffic Descriptor is CBR.

5 Enable performance monitoring if necessary.

Select Performance Monitoring .

6 Define a name for the cross-connection [optional].

Type the name in the Name field. The maximum length is 20 characters.


Click OK to send the changes to the node and close the New Cross-connection window,or Apply to send the changes but keep the window open.

Further information

The Traffic Descriptor of an existing cross-connection cannot be changed to a descriptorwhose service category (CBR or UBR) is different.

If you change the Traffic Descriptor, traffic will be cut off for about 100 ms in case thebandwidth is higher than 5000 cells/s.



DN02166645Issue 23A

119

Commissioning AXC


5.14.2 Creating Virtual Channel cross-connections

Purpose

This procedure describes how to create Virtual Channel cross-connections. The AXCsupports semi-permanent Virtual Channel cross-connection s.

Before you start

Before creating any cross-connections, read through AXC interface configuration con -straints .

Steps

1 Select the ATM view by clicking View → ATM View.

If the bottom view is not visible, click the small arrow pointing upwards at the bottom leftof the ATM view.

2 Click New in the bottom view.

The New Cross-connection window opens.

Figure 83 Creating a new Virtual Channel cross-connection

3 Define the termination points.

Perform the following tasks on both interfaces you want to cross-connect.

Select the Unit and Interface (IF) on which you want to create a cross-connection fromthe list. Click New VP to create a new Virtual Path and New VC to create a new VirtualChannel on the VP. A new Virtual Channel is created on the interface.





120 DN02166645Issue 23A

Commissioning AXC


4 Select a Traffic Descriptor for the VC.

Select a Traffic Descriptor from the list of predefined Traffic Descriptors or click ATM

Settings to create a new Traffic Descriptor. For more information, see Creating TrafficDescriptors .

5 Select the Pseudowire for the VC in case of IFUH.

Select the Pseudowire from the list if the VC is on the IFUH unit.

It is possible to create up to 10 VCs on each Pseudowire.

6 Enable performance monitoring if necessary.

Select Performance Monitoring .

7 Enable Egress Frame Discard if necessary.

Enable Egress frame discard (Early Packet Discard and Partial Packet Discard) byselecting Egress Frame Discard .

☞ Egress Frame Discard should only be selected if the configured VC is used for AAL5traffic. Using Egress Frame Discard on AAL2 channels may result in traffic loss.

8 Define a name for the cross-connection [optional].

Type the name in the Name field. The maximum length is 20 characters.


Click OK to send the changes to the node and close the New Cross-connection window,or Apply to send the changes but keep the window open.

Further information

Terminated AAL1, AAL2 and AAL5 channels cannot be modified on ATM level.

The Traffic Descriptor of an existing cross-connection cannot be changed to a descriptorwhose service category (CBR or UBR) is different.

If you change the Traffic Descriptor, traffic will be cut off for about 100 ms in case thebandwidth is higher than 5000 cells/s.



DN02166645Issue 23A

121

Commissioning AXC


5.15 Creating IP configuration

5.15.1 Setting public IP address

Purpose

Before doing any IP-level configurations, you have to configure the public IP address ofthe AXC. Public IP address and DCN configuration are required for master WAMchanges to be successful in the BTS.

Steps

1 Click IP → Settings...

The IP Settings window opens.

Figure 84 IP Interfaces window

2 Define the public IP address.

Click Set... at the top of the window and enter the public IP address in the input maskthat opens.



122 DN02166645Issue 23A

Commissioning AXC


Figure 85 Setting the public IP address of the AXC

The public IP address can be any valid IP address except one of the following:

• default address (0.0.0.0) • multicast (former Class-D) addresses (224.0.0.0/4) • reserved (former Class-E) addresses (240.0.0.0/4) • broadcast address (255.255.255.255) • address in the subnets 192.168.254.0/24 and 192.168.255.0/24 (internal

addresses) • addresses in the subnet 127.0.0.0/8 (reserved for local loopbacks)


Click OK . The AXC Manager configures the public IP address.

4 Click Close to close the IP Settings window.

Further information

Changing the IP address usually breaks the DCN connectivity until the other end of theDCN link is re-configured to use the new address as the destination address.



DN02166645Issue 23A

123

Commissioning AXC

Id:0900d805808179eaConfidential

5.15.2 Creating OSPF areas

Purpose

This procedure describes how to create the OSPF areas in the AXC.

Before you start

OSPF is a network-wide feature. For proper operation, the neighboring networkelements must also be configured to use OSPF.

Steps



Figure 86 IP Settings window

2 Click Add OSPF Area...

The Add OSPF Area window opens.





DN02166645Issue 23A

125

Commissioning AXC


5.15.3 Creating DCN connections for ATM interfaces

Purpose

The Data Communications Network (DCN) connections are IP over ATM connectionsthat are terminated in the IP routing instance of the AXC. IP packets are transported via

ATM/AAL5.

Before you start

Virtual Channels (VC) are used as ATM interfaces for the DCN connections. You haveto create these VCs before configuring the DCN settings. For more information, seeConfiguring ATM interface .

Note that the ATM configuration for DCN terminations is limited to 2 MBit/s. This meansthat the aggregate cell rate of all terminations with guaranteed bandwidth (CBR, UBR+)must be less than this value.

Before configuring DCN settings, the public IP address of the AXC has to be configured.For more information, see Setting public IP address .

If you are planning to use OSPF on any of the DCN interfaces, OSPF areas have to becreated first. For more information, see Creating OSPF areas .

Steps



Figure 88 IP Settings window

2 Click Add DCN...

The Add DCN for ATM Interface window opens.







126 DN02166645Issue 23A

Commissioning AXC


Figure 89 Adding a DCN for ATM interface

3 Select the VC.

Select the Virtual Channel (VC) on which you want to create the DCN connection fromthe tree view on the left side of the window.

4 Define the destination address.

Enter the Destination Address. It is the IP address of the remote node to which the DCNinterface is connected.

You can also select Inverse ATM ARP in which case the destination address will bedetected automatically by the AXC once the other node is up and running.

☞ Inverse ATM ARP is selectable only if OSPF is used on the interface.

Before you select Inverse ATM ARP, make sure that the destination node supportsit.

5 Define the OSPF settings [optional].

If you select OSPF, define the area to which the DCN interface will be added. Definealso the OSPF cost of the interface.

If you want to modify the OSPF timing values, click Timing... The OSPF Timing windowopens.





DN02166645Issue 23A

127

Commissioning AXC


Figure 90 OSPF Timing

☞ It is not recommended to change the default values. The Dead Interval timing value(120 sec) should not be modified at all.

OSPF adjacency cannot be established unless both neighbours have the sametiming values set. This concerns especially the Hello Interval and Dead Intervalvalues.

6 Click OK.

7 Configure all necessary DCN connections by repeating steps 2 to 6.


Click OK . The AXC Manager creates the cross-connection from the VC to the internalIP routing device automatically.

If you have selected Inverse ATM ARP, the destination address shows as 0.0.0.0. ClickView → Refresh → All in the AXC Manager main window to update it. This may takesome time depending on the remote node and the connection.

Click Close to close the IP Settings window, or Add DCN... to create another DCN con-nection.

Further information

If you want to delete an existing DCN connection, select the connection from the list andclick Remove . Before you delete a DCN connection you have to delete all routing tableentries that use the connection. For more information, see Creating IP routes .

To modify the LMP interface settings, select the Local Management Port (LMP) inter-face from the list and click Modify... .





128 DN02166645Issue 23A

Commissioning AXC


Figure 91 Modifying DCN for LMP interface

Netmask determines the maximum number of hosts in the LMP.

☞ The IP addresses of the 192.168.254.0/24 subnet are used AXC internally and theIP addresses of the 192.168.255.0/24 subnet are used BTS internally. All other IPaddresses are referred to as public IP addresses.

If you select Advertise via OSPF , Netmask and Broadcast are propagated to the otherrouters in the OSPF area.

Make the necessary modifications to the LMP interface settings and click OK .





130 DN02166645Issue 23A

Commissioning AXC


Steps

1 Click IP → Settings... and select the Routing pane and select Display DCN routing

radio button.

Figure 92 IP Settings - Routing window - DCN routingThe Routing pane is split into two parts. In the upper part you can see the Static RouteTable which shows manually created routes. In the lower part you can see the Forward-ing Table which shows the routing information for all active routes, either manually con-figured or automatically detected by OSPF, for example.

2 Click Add.

The Add IP Route window opens.

Figure 93 Add IP Route



DN02166645Issue 23A

131

Commissioning AXC


3 Define settings for the route.


• Destination (IP address for indirectly connected IP nodes) • Netmask (netmask and netmask bits of the destination address) • Gateway (gateway IP address of the destination)

For a complete entry, you have to define the Destination, Netmask and Gateway.

Selecting Default Gateway sets Destination and Netmask to 0.0.0.0..

4 Add all required DCN routes by repeating steps 2 to 3.

5 Select Display Transport routing.

Add the routes for transport traffic by clicking Add as mentioned in Step 3 above.

Figure 94 IP Settings - Routing window - Transport routing

6 Add all required transport routes by repeating step 5.

7 Click OK

8 Click Close to c lose the IP Settings window.

Further information

If you want to remove a route, select the route from the list and click Remove .

You can only delete routes that have been manually configured. They are shown in theStatic Route Table.



132 DN02166645Issue 23A

Commissioning AXC


Routes can be added in similar way in IP Iub mode in Static route table where only onerouting table is present for both DCN and transport routing entries.





134 DN02166645Issue 23A

Commissioning AXC


5.15.6 Creating DHCP configurations

Purpose

This procedure describes how to create the DHCP (Dynamic Host Configuration Proto-col) configurations to the AXC. The AXC acts as a DHCP server and can pass configu-ration information, such as IP addresses, to hosts.

The information can only be passed via the Local Management Port (LMP). The IFUGinterface unit can be used as a hub to connect up to seven external IP devices to theLMP. For more information, see IP routing function of AXC in AXC product description .

Before you start

The public IP address of the AXC as well as the netmask and subnet for the LMP mustbe configured. For instructions, see Setting public IP address and Creating DCN con -nections for ATM interfaces .

For instructions on creating IP routes in IP iub mode, see Activating and configuring IPIub and Configuring Timing over Packet. .

Note that only two gateway addresses can be maintained by AXC in IP Iub mode. Alsonote that in IP Iub mode the IFUH can only route IP packets to the first eight addressesof a configured public LMP subnet despite a much larger configured actual subnet size.

Steps

1 Click IP → Settings... and select the DHCP pane.

Figure 96 IP Settings - DHCP Configurations window





DN02166645Issue 23A

135

Commissioning AXC


2 Click Add...

The Add DHCP Configuration window opens.

Figure 97 Adding a DHCP configuration

First select the type of configuration. It can be either Client, Hardware or Range.

If you select Client , enter the Client ID (either manually or from the list) and the IP Address of the client. The maximum length of the Client ID is 20 characters and it canonly contain letters and digits (a...z, A...Z, 0...9)

If you select Hardware , enter the MAC Address and IP Address of the client.

If you select Range , enter the IP Address Range from which the AXC will assign IPaddresses to the clients.

The relationship between the configuration types is hierarchical. When the AXCreceives a request for a lease (IP address) from a client, it tries to identify its client iden-tifier first and then its MAC address and assign an IP address accordingly. If neither ofthose is recognised, the AXC the address is assigned from a preconfigured internal pool

(in case the user class option of the client is BTSLOCAL) or from the IP address rangeyou have defined.

☞ The IP addresses that you configure must be within the LMP subnet of the AXC.However, neither the IP addresses of the AXC and the subnet nor the broadcast IPaddress can be used.

3 Click OK to send the changes to the node.

4 Add all required DHCP configurations by repeating steps 2 and 3.

5 Click Close to c lose the IP Settings window.



136 DN02166645Issue 23A

Commissioning AXC


5.15.7 Configuring BTS IP settings

Purpose

This procedure describes how you can configure the IP settings used by the BTS.

Steps

1 Click IP → Settings and select the BTS Settings pane.

Or click IP → BTS Settings.

Figure 98 IP Settings - BTS Settings

2 Click Modify to define the settings.

The Modify BTS Settings dialog opens.



DN02166645Issue 23A

137

Commissioning AXC


Figure 99 Configuring BTS IP settings1. Enter the BTS Identifier. The BTS Identifier can be modified only if no AAL2 config-

uration exists.2. Enter the BTS IP address.3. Enter the RNC IP address. The RNC IP address is needed for the O&M connection

between the BTS and RNC.4. You can also enter the Remote Tilt IP address if it is in use.5. TLS for OMS interface: By default is set to Probing. The UltraSite BTS supports the

following TLS modes: – Off: Insecure plain text connections are to be used. – Forced: Connections are performed using TLS. Insecure plain text connections

are not allowed. – Probing: Secure connections using TLS are probed. The fallback to the insecure

mode is allowed in case of any problems with the secure connection arise.6. OMS connection status: By default the status is set to Not connected. OMS connec-

tion status is read only attribute and returns the connection status between SMA andOMS and value is set by ASN.1 gateway. Possible values are: – Not connected – TLS Secured



138 DN02166645Issue 23A

Commissioning AXC


– UnsecuredOnce the secure O&M connection is established, it is advised to set TLS probingmode to forced (probing mode should be used only initially). Otherwise, in certaincases the secure O&M connection might expire.To avoid manual update of all BTSs follow the procedure:1 Temporarily change TLS mode in the RNC to forced. This causes a temporary

O&M interruption of all BTS not supporting secure O&M (TLS) for the time ofmigration.

2 Set TLSModeSending feature in the RNC to ON.g TLSModeSending can found in Parameter Tool -> ClusterRoot/OMS/Sys-

tem/Network/TLS/TLSModeSending.3 TLS mode of all BTSs changes automatically into forced. Note that this can take

several minutes up to hours depending on the number of BTSs connected to thatRNC.

4Change TLSModeSending parameter back to OFF.5 Change TLS mode in the RNC back to previous setting (for example - probingto enable compatibility of BTSs with unsecured O&M session).

Note that the TLS mode setting in RNC can be different from TLS mode setting inBTS. This means that usually TLS in BTS is set to forced, but TLS in RNC is set toprobing. That allows for using BTSs both with secure (TLS) and unsecured O&Msession, as well as enables initial unsecured O&M session, before the BTS gets acertificate for TLS.

7. ICMP Response in use: Select the ICMP, if ICMP response is required.

More information on TLS operating mode can be found in TLS operating mode table.

3 Activate the BTS settings.

Click Activate BTS settings to send the new settings to the BTS and take it into use.Or click Apply to save the changes to AXC.

Present TLSmode for

OMS inter-face

Present OMSconnection

Status

New TLSMode

Disconnectfrom OMS

(Action to betaken by SMA)

New TLSMode to be

stored in per-sistent DB

Off Unsecured Probing Yes Yes

Probing Unsecured Off No Yes

Probing TLS Secured Off Yes Yes

Probing Unsecured Forced Yes Yes

Probing TLS Secured Forced No Yes

Forced TLS Secured Probing No YesForced TLS Secured Off Yes Yes

Table 2 TLS operating mode



DN02166645Issue 23A

139

Commissioning AXC


5.15.8 Configuring Restricted Mode filtering

Purpose

In the so-called restricted mode of the LMP, it is possible to access only the local AXCand BTS. All IP packets with a public IP address in the source or destination are dis-carded. The IP addresses of the 192.168.254.0/24 subnet are used AXC internally andthe IP addresses of the 192.168.255.0/24 subnet are used BTS internally. All other IPaddresses are referred to as public IP addresses.

However, you can define exception rules to the restricted mode so that any IP packetthat matches any rule in any rule set is not discarded.

In unrestricted mode, other network elements within the same network can also beaccessed by DCN connection.

Steps

1 Click IP → Restricted Mode Filtering.

Figure 100 Restricted Mode Filtering

2 Create a new rule.

Click Add .



140 DN02166645Issue 23A

Commissioning AXC


Figure 101 Adding a Restricted Mode rule

First select the rule set for which you are creating an exception. Enter a descriptivename for the exception in the Description field.

Define the following for the Near Endpoint:

• Port Type: can be sequence, range or any. • Port: either a sequence or range of ports, depending on the selected port type. If the

port type is Any, the field is disabled.

Define the following for the Far Endpoint:

• Address Type: can be single, range, any or alias • Address: IP address of the far endpoint if the address type is single or range • Netmask: defined if the address type is range • Alias: select the alias from the list if the address type is alias.

The Alias is a placeholder for a well-known single IP address or a group of IPaddresses and ports already defined elsewhere (such as for primary and secondaryLDAP server, for example).

• Port Type: can be sequence, range or any. • Port: either a sequence or range of ports, depending on the selected port type. If the

port type is Any, the field is disabled.Port Type and Port are not defined if the far endpoint address type is Alias.

Click OK to add the new exception to the rule table.

3 Activate or deactivate restricted mode.

Click Restricted Mode for LMP On or Restricted Mode for LMP Off .

The restricted mode has to be deactivated if the AXC must be connected to the RAN viaDCN over the LMP. In all other cases the restricted mode should be activated forsecurity reasons. By default, the LMP is in restricted mode.

Rules which can be added for the management, control and user plane traffic are listed

in Filter rules for management plane traffic , Filter rules for control plane traffic and Filterrules for user plane traffic tables.





142 DN02166645Issue 23A

Commissioning AXC


in AXC module based on maximum expected traffic in real time for each known applica-tion (like Top, SCTP, BFD, ICMP, user plane traffic and so on). This cannot be config-ured externally by the user.

• User plane ingress packet rate is limited to 60 000 packets per second. • Top ingress packet rate is limited to 512 packets per second. • ICMP egress packet rate is limited to:

– ICMP Echo Request: 2 packets per second – ICMP Echo Reply: 2 packets per second – ICMP Time Exceeded: 2 packets per second – ICMP Destination Unreachable: 2 packets per second

• ICMP ingress packet rate is limited to: – ICMP Echo Request: 2 packets per second – ICMP Echo Reply: 2 packets per second

• The ARP traffic (ARP requests and ARP replies) is limited to 300 packets persecond.

• The management plane traffic is limited to 2000 frames per second. Note that thisincludes NTP, BFD and IKE traffic.

• The control plane ingress packet rate is limited to 500 packets per second.



DN02166645Issue 23A

143

Commissioning AXC


5.15.9 Creating NTP servers

Purpose

Time setting in the AXC can be handled via Network Time Protocol (NTP) by connect-ing to an NTP server.

If no NTP server is available the system time can be configured also manually. However,in this case the time settings are lost when the AXC is restarted. Therefore it is recom-mended to handle time via NTP servers.

Steps

1 Click IP → System time...

The System Time window opens.

Figure 102 System Time window

2 Define the IP address for the NTP server.

Set NTP to enabled by selecting Use Network Timing Servers . By default NTP is dis-abled.

Click Add... to add a Network Time Protocol server. Enter the IP Address of the NTPserver. Click OK .

Figure 103 Add NTP server

It is possible to configure up to three NTP servers. The AXC chooses the best server,taking into account several factors like stratum or round trip delays. If these criteria arethe same for two or more servers, the preferred server is used.







144 DN02166645Issue 23A

Commissioning AXC


3 If you want to configure the system time manually, click Set... to open the SetSystem Time window.

Figure 104 Set system time manually

Set the desired system time by selecting the Time, Day, Month and Year and click OK .

System time cannot be modified manually when NTP is enabled.


Click OK to send the changes to the node and close the System time window, or Apply to send the changes and keep the window open.



DN02166645Issue 23A

145

Commissioning AXC


5.15.10 Configuring BTS Firewall

Purpose

Firewall feature in BTS is implemented to prevent unauthorized users from accessingand harming the remote networks connected to the BTS. In addition to this, it restrictsthe traffic from unknown applications and IP addresses either from the remote or localnetwork. In this process all messages entering or leaving the AXC module IP interfacespass through the firewall, which examines each packet and blocks those that do notmatch the specified internal or external rules in the system.

Before you start

BTS firewall feature is only supported by AXCF. Make sure that the Transport mode iseither IP Iub or Dual Iub mode. For instructions see Configuring Transport mode .

The precondition for setting any BTS firewall rules.

By default, there are wild card rules for both BTS and AXU domain which allow all thetraffic sent by remote network. To activate BTS firewall rules, the wild card rule set onTRS and BTS domains needs to be deleted by selecting the rule and using Delete button in Element Manager in Restricted mode filtering window. New firewall rules fortraffic filtering can be created using option New in the Restricted mode filtering window.

Steps

1 Configure IP Iub.

For instructions, see Configuring and activating IP Iub mode with AXCF .

2 Configure public IP address.

For instructions, see Setting public IP address .

3 Configure transport IP address.


4 Configure IP route parameter.

For instructions, see Creating IP routes with AXCF/IFUH .

5 Configure Restricted Mode Filtering.

For instructions, see Configuring Restricted Mode filtering .



146 DN02166645Issue 23A

Commissioning AXC


5.16 Configuring Management Protocol for Secure/UnsecuredLDAP connection

PurposeThis procedure describes how to configure the Management Protocol settings for the

AXC for establishing secure and secure/unsecured LDAP connections & registration of AXC into NetAct Network Management system. The settings are mandatory if you wantthe AXC to be registered to and identified by NetAct network management system.

Steps

1 Click Configuration → Management Protocol...

The Management Protocol window opens.

Figure 105 Management Protocol window

2 Modify the Base ID and Parent NE ID.

Click Modify . The Modify System Information window opens.

Figure 106 Modifying Base ID and Parent ID

Modify the settings if necessary. The Base ID is the unique identifier for the AXC in the

network, and the Parent NE ID is the NWI3 identifier of the BTS that the AXC is locatedin. No Parent ID is defined for stand-alone AXC.



DN02166645Issue 23A

147

Commissioning AXC


Choose the parent ID's beginning from the drop-down list: RNC or IADA. Then enter theRNC ID/IADA ID and WBTS ID in the fields. The length of the RNC ID/IADA ID andWBTS ID can be 10 characters.

The Base ID and Parent NE ID are formed according to the following scheme:

The <id> part of Base ID and Parent ID can be up to 10 characters long. It can containletters and numbers (a...z, A....Z, 0...9), spaces, and the following special characters:

! $ ( ) * + , - .; = ? @ [ ] ^_ { } | ~

However, the <id> part of the Parent NE ID cannot contain the "|" character.Click OK to close the window.

3 Set NetAct's Interoperable Object Reference (IOR) string in the AXC.

Click Add... in the Management Protocol window. The Add Registration Service windowopens.

Base ID NE-AXC-<id>

For example: NE-AXC-17

The value for the <id> is planned in advance and it must beunique among the AXCs in the RAN

Parent NE ID The value is entered in format:

<Manager object Specifier> | <BaseId> |<LocalMOID>

• <Managed Object Specifier> = NE • <BaseId> = BaseId of the RNC controlling the BTS in

which the AXC is located • <LocalMOID> = DN:NE-WBTS-Id

For example NE | NE-RNC-5 | DN:NE-WBTS-12

The Parent NE ID value for a stand-alone AXC is NULL |NULL-0 | DN:NULL-0

Table 6 Base ID and Parent NE ID naming scheme



148 DN02166645Issue 23A

Commissioning AXC


Figure 107 Add Registration Service


• Name of the service

• NWI3 Registration Service account parameters: Username and Password (theseare not related to the AXC Manager account parameters) • LDAP Server information: IP address, port, configuration root and people root for

both primary and secondary LDAP server. Note that the settings for secondaryLDAP server are optional. Also, if the TCP port number is omitted the default value389 will be used.

• LDAP Security mode: Only allow secure LDAP connections checkbox is by defaultchecked. This sets LDAP security mode to secure. When the checkbox isunchecked LDAP security mode can be secure/unsecured.

• Configuration of root and people root are optional, since AXC is able to detect themautomatically.

• NWI3 Registration Service IOR: select the file that contains the IOR by clickingFrom File...☞ The IOR file needs to be saved as text.

If you need to modify the Registration and Publication time values, click Intervals andPeriods...



DN02166645Issue 23A

149

Commissioning AXC


Figure 108 Intervals and PeriodsClick Send .

Figure 109 Registration Service entry in Management Protocol dialog

4 Activate the new configuration.

Select the new configuration object from the list and click Take Into Use Next .

Click Restart to start the AXC's registration process towards NetAct. You can enter adelay for the restart.

Close the window by clicking Close .

Verification

Click Refresh in the Management Protocol window and ensure that the state of the newconfiguration is changed to Active, Next.



150 DN02166645Issue 23A

Commissioning AXC


5.17 Installing CA certificates manually for AXC

Purpose

This procedure describes how to install a CA Certificate on AXC.Before you start

The CA and AXC certificates as well as AXC private keys must be created from Certifi-cate Authority. All of these have to be stored in the local machine where the SiteManager is installed.

The supported certificate format for CA key certificate, AXC public key certificate, and AXC private key certificate is .PEM.

These certificates can be installed in AXC in three ways:

• Install CA certificate first and then AXC certificate and private key• CA, AXC certificate, and AXC private key altogether

• AXC certificate and private key without CA (in case CA has longer validity than NEcertificate)

Steps

1 Click Node → Certificate Management

Certificate Management window opens. Select AXC Certificates tab.

Figure 110 Certificate Management window



DN02166645Issue 23A

151

Commissioning AXC


2 Browse to the location where CA certificates are stored.


3 Once CA certificate is selected Send button gets highlighted. Click on the Sendbutton to install the certificate on the AXC node.




152 DN02166645Issue 23A

Commissioning AXC


A CA certificate is installed in the AXC using the Element Manager and is then availableto any application, for example Secure LDAP or Secure NWI3 that requires it. Expiredor outdated CA certificates may be deleted by utilizing the Element Manager. Deletinga CA certificate may affect Secure AXC management interface and other applicationswhich uses the CA certificate.

Verification

Once CA certificate is installed successfully on the AXC node CA certificate details likeIssued To, Issued By, Valid From, Valid To, Serial Number & Fingerprint values can beobserved in the Certificate Management window.





154 DN02166645Issue 23A

Commissioning AXC

Id:0900d80580817a88Confidential

3 Certificate management window opens.





DN02166645Issue 23A

155

Commissioning AXC


5 Once the CA certificate is installed in the AXC Element Manager. The informationregarding the certificates can be seen as shown below.


Steps for installing CA certificate after logging into the AXC Element Manager


Certificate Management window opens. Select AXC Manager Certificates tab and clickAdd Certificate .



156 DN02166645Issue 23A

Commissioning AXC






DN02166645Issue 23A

157

Commissioning AXC


3 Once the CA certificate is installed in the AXC Element Manager. The informationregarding the certificates can be seen as shown below.


VerificationOnce CA certificate is installed successfully in the AXC Element Manager CA certificatedetails like Issued To, Issued By, Valid From, Valid To, Serial Number & Fingerprintvalues can be observed in the Certificate Management window.

Further information

A CA certificate is configured in the AXC Element Manager and is then available to anyapplication like secure NWI3 that requires it. Expired or outdated CA certificates mightbe deleted by using the Element Manager. Deleting all CA certificate might affect Secure

AXC management interface and other applications which use the CA certificate.



158 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807f9e6cConfidential

5.19 Installing AXC Certificate and AXC private key manually

Purpose

This procedure describes how to install AXC certificate and AXC private key manually.Before you start

The CA and AXC certificates as well as AXC private keys must be created from Certifi-cate Authority. All of these have to be stored in the local machine where the ElementManager is installed.

The supported certificate format for CA key certificate, AXC public key certificate, and AXC private key certificate is .PEM.

These certificates can be installed in three ways:

• Install CA certificate first and then AXC certificate and private key• CA and AXC certificate and AXC private key altogether

• AXC certificate and private key without CA (in case CA has longer validity than NEcertificate).

Steps


Certificate Management window opens. Select AXC Certificates tab.


2 Browse to the location where AXC certificates are stored.



DN02166645Issue 23A

159

Commissioning AXC


3 Browse to the location where AXC private keys are s tored.

Once AXC certificate & private key is selected Send button gets highlighted. Click on

the Send button to install the certificate & private key on the AXC node.


Verification

Once AXC certificate & private key are installed successfully on the AXC node AXC cer-tificate details like Issued To, Issued By, Valid From, Valid To, Serial Number & Finger-print values can be observed in the Certificate Management window.



160 DN02166645Issue 23A

Commissioning AXC


5.20 Configuring CMP and CR server IP address

Purpose

This procedure describes how to configure the CMP and CR server IP address.Before you start

The Reference Number and Pre Shared Key must be created from Certificate Authority. All of these have to be stored in the local machine where the Site Manager is installed.

A Certificate Management Protocol (CMP) is used to fetch the CA signed AXC certificateand CA certificates automatically and to perform it in a secure manner.

To do so AXC must be configured with:

• Reference Number (RefNum) and Pre Share Key (PSK). • CMP server IP address and TCP port number. • Certificate repository (CR) IP address and TCP port number.

RefNum and PSK are used for the initial encryption of CMP messages between theCMP client and Certificate Authority. At the initial configuration these values are to bemade out-of-band and using the Site Element Manager the values are downloaded overa local connection. The Certificate Authority IP address and TCP port number are con-figured using the Element Manager or by deploying an AXC Site Configuration File.

This configuration is used by the AXC embedded CMP client to exchange messageswith the Certificate Authority. The CR IP address and TCP port number are configuredusing the Element Manager by deploying an AXC Site Configuration File. This configu-ration is used by the AXC embedded CMP client to retrieve the CA certificate from thecertificate repository (CR). The CA certificate retrieval uses the LDAPv3 protocol.

PSK and RefNum must be generated in the same Certificate Authority which is to beused to get AXC and CA certificates. These values also need to be made available forthe Certificate Authority in order to allow the establishment of a secure CMP messageexchange.

Configuring CMP and CR server IP addresses and PSK and RefNum triggers to takeCMP into use for this particular AXC. This causes the creation of a new private andpublic key pair, followed by a CMP Initialize sequence to obtain a valid and CA signed

AXC certificate as well as the CA certificate to be used by the AXC.

Steps

1 Click Node → Certificate Management.Certificate Management window opens. Select Automatic Management tab.

2 Browse to the location where the text file for the RefNum and PSK are stored ortype the values manually.

3 Enter the Certificate Authority IP address and the TCP port number.



DN02166645Issue 23A

161

Commissioning AXC


4 Enter the CR server IP address and TCP port number.

Figure 120 Automatic Management window

5 Select Send button to store these values in the AXC node.

Figure 121 Automatic Management window during storing the values



162 DN02166645Issue 23A

Commissioning AXC


Further information

CMP initialization can be manually triggered by using the Update Certificates button.



DN02166645Issue 23A

163

Commissioning AXC


5.21 Configuring VLAN Differentiation

Purpose

The idea of the VLAN traffic differentiation is to insert a VLAN ID into Ethernet framesaccording to the traffic plane type of the corresponding radio link. With this mechanism,it is possible to create logically separated networks on Ethernet level what allows oper-ators to separate traffic of different types or to aggregate traffic of the same type in theirbackhaul networks. VLANs are a similar concept on Layer 2 as IP subnets on Layer 3.

Before you start

VLAN traffic differentiation is application software that requires a valid license. For moreinformation, see Managing licenses in Operating and Maintaining AXC .

VLAN traffic differentiation feature is only supported by AXCF. Make sure that the Trans-port mode is either IP Iub or Dual Iub mode. For instructions, see Configuring Transportmode .

Steps

1 Configure public IP address.

For instructions, see Setting public IP address .

2 Configure transport IP address.


3 Add VLAN.In IP settings go to Transport Addresses .





164 DN02166645Issue 23A

Commissioning AXC



4 Click on Add... in the VLAN interface window.

The Add VLAN interface window opens.



DN02166645Issue 23A

165

Commissioning AXC


Figure 123 Add VLAN interface window

1. Enter the identifier of the VLAN to which the interface belongs. Possible valuesrange from 0 to 4094.

2. Enter the local IP address and netmask.3. MTU : Enter the maximum transmission unit value.4. Shaper IR : Default value is 1000 Mbps. Range is from 1 to 1000 Mbps, in step of 1

Mbps.5. Shaper burst size : Default is 1522. Range is 1522 to 2000000 in step of 1 octet.6. Committed IR : Defines CIR as the queue shaping type. The CIR parameter allows

to specify bandwidth that is guaranteed for higher priority PHBs. Default is 1000Mbps. Range is from 0.1 to 1000 Mbps, in step of 0.1 Mbps.

7. QoS : can be enabled if the quality of service has to be taken into use at VLAN inter-face.

8. Select the active interface.

9. For more information on Proxy APR, see Enable Proxy ARP .Click OK to send the changes to the node and close the dialog, or Close to close thewindow.

5 Configure IP Iub

For instructions, see section Configuring and activating IP Iub mode with AXCF .

g Configuring IP Iub is to be required only when CAC has to be calculated. Theseparameters are not present in Dual Iub mode.



166 DN02166645Issue 23A

Commissioning AXC


6 Modify in VLAN settings

Click Configure button under VLAN mapping label to configure VLAN mapping to the

traffic path.Modify VLAN mapping window opens. Click Modify

Figure 124 Modify VLAN mapping window

VLAN mapping is optional. The traffic can be sent either by using VLAN mapping orwithout VLAN mapping.



DN02166645Issue 23A

167

Commissioning AXC


5.22 Configuring AXC Q1 Support Function

Purpose

The Q1 Support Function in AXC acts as a master poller for Nokia Siemens NetworksQ1 managed network elements. The AXC Q1 Support Function can poll far-end Q1 network elements via Q1 Embedded Operation Channels (EOC) as well as networkelements connected to the V.11 Q1 interface of the AXUA/B or the AXCC/D.

AXC Compact supports Q1 polling over V.11 interface but not Q1 EOCs.

Additionally, the AXC Q1 Support Function can poll the Flexbus part of IFUE interfaceunit. See Commissioning FlexiHopper (Plus) and MetroHopper with IFUE for more infor-mation on configuring the Q1 management connection over the Q1SF and the connec-tion type for the Flexbus part of the IFUE.

Before you start

Make sure that General Communications Service GCS R4.2 (or later) tool is installed onthe Local Management Tool.

If the AXC Q1 Support Function is connected via Data Communications Network (DCN) to the Q1 Agent Mediation device, the configuration of Q1 Support Function maydiffer. Please refer to Q1 Agent documentation for more information.

☞ The Q1 Support Function settings are not persistent. If no Q1 Agent connection isavailable, the Q1 Support Function has to be reconfigured if the AXC is rebooted orthe power is lost. If a Q1 Agent connection is available, the Q1 Support Function isautomatically reconfigured in these cases after about 10 minutes.

Steps

1 Set the baud rate to 9600.

Click Node → Q1 Support Function → Set Channel to → 9600 .

Figure 125 Setting Q1 Support Function channel

2 Confirm the baud rate setting.

Click Yes .

Expected outcome

The GCS Command Line Tool starts automatically and configures all necessary set-tings.

Check that the last line of the output reads # clean run, no errors occurred .



















168 DN02166645Issue 23A

Commissioning AXC


Figure 126 Q1 Support Function outputFurther information

See also Configuring Q1 EOCs .



DN02166645Issue 23A

169

Commissioning AXC


5.23 Configuring loopbacks

Purpose

This procedure describes how to configure loopbacks with the AXC Manager. The fol-lowing loopbacks can be configured for PDH and SDH/SONET interfaces:

• loop to interface (incoming signal is looped back to output directly after the interface) • loop to equipment (outgoing signal is looped back to input directly before the inter-

face)

Steps

1 Select the interface on which you want to create a loopback.

Select the interface on which you want to create a loopback in the Hardware view.

2 Create the loopback.

Click Modify . The Modify Interface window opens. Select the Loop pane and check theLoop box.

Figure 127 Creating a loopback

3 Select the loopback type.The loopback type can be either To Equipment (default) or To Interface.

4 Define the loop timeout.

Define the New Timeout. It is the time period after which the loopback stops automati-cally. The default value is 15 minutes and the maximum value 1440 minutes (1 day).


Click OK to send the changes to the node and close window, or Apply to send the

changes but keep the window open.



170 DN02166645Issue 23A

Commissioning AXC

Id:0900d80580817abeConfidential

5.24 Configuring BFD triggered static rerouting

Purpose

This procedure describes how to configure BFD triggered static rerouting in BTS.Before you start

To achieve BFD triggered static rerouting, destination BFD sessions should be createdon the site routers that match the BFD sessions created on the AXC node.

BFD Triggered Static Rerouting is a licensed feature. The operator needs to install avalid license to use this feature.

Steps

1 Configure the transport interfaces.


2 Create BFD sessions.

For instructions, see Creating BFD sessions . Repeat the same procedure to createmultiple BFD sessions.

3 Create route to the destination.

This feature allows for creating multiple routes to the same destination via differentGWs. Moreover, the user can associate BFD sessions with the static routes to monitorroute condition.

Click IP → IP Settings and select the Routing tab.



DN02166645Issue 23A

171

Commissioning AXC


Figure 128 Routing tab

Click Add to create static routes and associate them with the BFD sessions.

Figure 129 Add IP Route

1. Enter the destination address and netmask.2. Define the gateway IP address.3. Assign the BFD session to the created route.4. Cost is the metric used. Assign a value in range 1 – 254.



172 DN02166645Issue 23A

Commissioning AXC


Figure 130 Routing tab with IP routes added

In Dual Iub mode the user can add static routes associated with BFD sessions in thetransport routing table. Routes in DCN routing table are not allowed to be associatedwith the BFD sessions.

4 Set the Route reinstallation delay timer.

Click Set button.

Figure 131 Set route reinstallation delay

Route reinstallation delay can be set in the range from 0 to 30 seconds. Default value is0s.



DN02166645Issue 23A

173

Commissioning AXC

Id:0900d80580817e3dConfidential

5.25 Configuring Ethernet OAMEthernet OAM (Operations, Administration and Maintenance) is a collection of functionsfor Ethernet networks. The purpose of these functions is to assist in operations on

Ethernet networks, for example, troubleshooting, performance monitoring and verifica-tion of the configuration.

Ethernet OAM functions can be divided in two categories:

• Link OAM - functions are performed on a single Ethernet link only • Service OAM - functions are performed on multiple links

5.25.1 Configuring Link OAM

Before you start

Ethernet OAM is a licensed feature. Activating a valid license file on the node is a pre-

requisite.

Steps

1 Click Configuration → Ethernet Link OAM.

Ethernet Link OAM window opens.



174 DN02166645Issue 23A

Commissioning AXC


Figure 132 Ethernet Link OAM

2 Create Ethernet Link OAM Profile.

Click Configure Profiles... .

Ethernet Link OAM Profiles window opens.





176 DN02166645Issue 23A

Commissioning AXC


2. Test frame rate can be set to a value in the range [1…25000].3. Test frame size can be set to a value in the range [64…1518].4. Link lost time can be set to a value in the range [2…10].

5. Critical event alarm clearance delay can be set to a value in the range [1…10].6. Maximum repetition number can be set to a value in the range [1…4].7. Errored frame event threshold can be set to a value in the range

[0…2147483647].8. Errored frame event interval can be set to a value in the range [1…60].9. Errored frame period threshold can be set to a value in the range [0.2417486347].10. Errored frame period interval can be set to a value in the range [100…60000].11. Errored frame seconds threshold can be set to a value in the range [0…65535].12. Errored frame seconds interval can be set to a value in the range [10…900].

g The parameters shown in figure Add Link OAM Profile are default values.

Click OK to send changes to the node. Click Cancel to discard them.Once the parameters are set, new Link OAM profile appears on the Link OAM profile list(see figure Ethernet Link OAM Profiles ).

Figure 135 Ethernet Link OAM Profiles

Click Close to close the window.

3 Mapping Link OAM profile with the interface.

Once the profile has been created, you need to map it to particular Ethernet interface.

Select the interface and cl ick Modify… .



DN02166645Issue 23A

177

Commissioning AXC


Figure 136 Ethernet Link OAM window - Ethernet interfaces

Modify Ethernet Interface window opens.

Figure 137 Modify Ethernet Interface

1. Select In use check box.2. Modify Spped and duplex , if required.3. Select desired Link OAM profile .4. Once the Link OAM profile has been selected, select Link OAM Enabled check box.5. Click OK / Apply to send settings to the node. Click Cancel to close the dialog.

Figure Newly mapped Link OAM profile shows the result of a successful Link OAMprofile mapping to Ethernet interface.

Figure 138 Newly mapped Link OAM profile

4 Enabling Loopback.

Click Modify button as shown on figure Ethernet Link OAM - Link OAM Loopback .



178 DN02166645Issue 23A

Commissioning AXC


Figure 139 Ethernet Link OAM - Link OAM Loopback

Modify Remote Loopback Support window opens.

Figure 140 Modify Remote Loopback Support

The Remote loopback supported field is checked by default. The user can check / un-check the field.

Click OK to send changes to the node.

Next, click Start OAM Loopback (see figure Ethernet Link OAM - Link OAM Loopback ).

The Loopback can be started on the desired interface by selecting the correspondinginterface and clicking Start Loopback , as shown on figure Ethernet Link OAM Loop -back .

Figure 141 Ethernet Link OAM Loopback



DN02166645Issue 23A

179

Commissioning AXC


5 Resetting Link OAM

Click Start OAM Reset (see figure Ethernet Link OAM window - Link OAM Reset ).

Figure 142 Ethernet Link OAM window - Link OAM Reset

Ethernet Link OAM Reset window opens.

Figure 143 Ethernet Link OAM Reset

Select the interface from the drop down list which you need to reset. Click Send .

5.25.2 Configuring Service OAM

Purpose

Ethernet Service OAM defines a set of functions that enables detection of networkdefects, location of the defect and reports alarms in case of anomalies in the networkconnectivity. Service OAM operates end-to-end over multiple links.

Before you start

Ethernet OAM is a licensed feature. Activating a valid license file on the node is a pre-requisite.

Steps

1 Create a Service OAM object and define a new domain.

Click Configuration → Service OAM .



180 DN02166645Issue 23A

Commissioning AXC


Figure 144 Service OAM

Select the Service OAM Objects and click New domain to create a new Maintenance

Domain (MD).

Figure 145 New Maintenance Domain

1. Enter MD name. The name should be unique within the BTS.2. Define a MD level between 0 – 7.

g You can configure only 10 MDs in one BTS.

2 Create New Association.

Click New Association to create a Maintenance Association (MA).



DN02166645Issue 23A

181

Commissioning AXC


Figure 146 Service OAM - New Association

Add New Association window opens.

Figure 147 Add New Association

1. Enter MA name. This name should be unique under defined MD.2. Assign VLAN ID. The value range from 0 to 4094.

g You can configure only 15 MAs in one BTS.

0 is a default value and it is not considered as VLAN ID.

3 Create Endpoint.

Click New Endpoint .



182 DN02166645Issue 23A

Commissioning AXC


Figure 148 Service OAM - New Endpoint

Add New Endpoint window opens.



DN02166645Issue 23A

183

Commissioning AXC


Figure 149 Add New Endpoint

1. Enter ID. ID represents node end point ID. The value range is 1-8191.2. Select CCM sending enabled field.When ETH-CC is enabled, a MEP periodically transmits CCM frames as often as theconfigured transmission period/CCM interval.CCM interval value can be: • 3.33ms: Default transmission period for protection-switching application (trans-

mission rate of 300 frames/second). • 10ms: Transmission rate is 100 frames/second. • 100ms: Default transmission period for performance-monitoring application

(transmission rate of 10 frames/second). • 1s: Default transmission period for fault management application (transmission

rate of 1 frame/second). • 10s: Transmission rate of 6 frames/minute. • 1min: Transmission rate of 1 frame/minute. • 10min: Transmission rate of 6 frames/hour.

3. Select AIS in use field. Select AIS transmission interval . AIS is generated in case of any occurred errors or defects. The purpose of this is tomask OAM alarms on higher level.

AIS transmission interval can be 1/second or 1/minute.4. Assign VLAN priority. The value range is 0 - 7.



184 DN02166645Issue 23A

Commissioning AXC


4 Click Add to map remote MEPs to the local MEPs.

Figure 150 Add Remote Endpoint

Enter ID and MAC address of the remote end point.

g You can configure up to 15 MEPs and 30 remote MEP in one BTS.

5 Configure the Service OAM CIR value.

Figure 151 Service OAM - Service OAM Cir Value

Enter required service Cir value.



DN02166645Issue 23A

185

Commissioning AXC


Figure 152 Modify OAM CIR

6 Configure inserting optional TLV into reply messages.

Click Modify... .

Figure 153 Service OAM - Insert optional TLV into reply messages

Modify OAM window opens. Select Insert received optional TLV into reply messages to include optional TLV for link trace and CCM procedures.



186 DN02166645Issue 23A

Commissioning AXC


Figure 154 Modify OAM



DN02166645Issue 23A

187

Commissioning AXC


5.26 IP Network Management

Purpose

IP Network Measurement allows for active measuring and supervising the IP ne tworkconditions on end-to-end path between the BTS and the RNC.

Steps

1 Click IP settings → RTT tab.

Figure 155 RTT tab

2 Configure the source port.Click Modify... to configure the TWAMP sender port.





DN02166645Issue 23A

189

Commissioning AXC


Figure 159 Modify Session

1. Select In use field.2. Enter the Destination IP address .3. Assign a Destination port . The value range is 1 - 65535.4. Enter the Source IP address .5. Enter a DSCP . The value range is 0 - 63.6. Select Message size . The value range is 69 - 1500.7. Define Packet loss ratio alarm threshold .

8. Select Round trip time alarm threshold . The value range is 0 – 1000 ms.Click OK to create a session.

g For each session the parameter set must be unique in terms of destination IPaddress, UDP port, DSCP value, or packet length. The same parameter set mustnot be used in two sessions.

Some parameters of the session can be modified only after stopping the session.The parameters are Destination IP address, Destination port, and Source IPaddress.

For UDP echo server the destination UDP port should be 7.

4 To view session s tatistics.

Select the required session. The selected session appears highlighted.



190 DN02166645Issue 23A

Commissioning AXC


Figure 160 RTT tab - Session statistics





192 DN02166645Issue 23A

Commissioning AXC

Id:0900d805807fd13bConfidential

Figure 162 BFD Sessions

3. Configure BFD sessions.Click Add to create new BFD session.

Figure 163 Add BFD SessionYou can set the following BFD session parameters: • Enable the session by selecting Active and Session in use checkboxes. • Select Single hop or Multi hop BFD mode using BFD type drop down menu. • For Single hop BFD mode UDP source port can be 3784, 49152 … 65535.

Default is 3784. • For Multi hop BFD mode UDP source port can be 4784, 49152 … 65535.

Default is 4784. • Set Desired min. TX interval . Default is 100ms. Range is from 100 to 5000ms

in step of 100ms. • Set Required min. RX interval . Default is 100ms. Range is from 100 to 5000ms

in step of 100ms.



DN02166645Issue 23A

193

Commissioning AXC


• Set Detection multiplier . Default is 5. Range is from 2 to 10. • Set Destination address . (IP Address of the peer node to which BFD session

needs to be established.)

• Set Source address can be AXCF transport address, VLAN address, or virtualIP address.4. Click OK to send the changes to the node.

g Detection time multiplier is the negotiated transmit interval, multiplied byDetection time multiplier of far end, provides the Detection Time for the transmit-ting system in Asynchronous mode.Desired Min TX interval is the minimum interval, in microseconds that the localsystem would like to use when transmitting BFD Control packets. The value zerois reserved.Required Min RX interval is the minimum interval, in microseconds, betweenreceived BFD Control packets that this system is capable of supporting. If thisvalue is zero, the transmitting system does not want the remote system to sendany periodic BFD Control packets.Up to 16 BFD sessions can be established when Iub termination is pointing tothe AXCF in IP Iub and Dual Iub mode.For Single hop BFD mode UDP destination port is 3784 which is fixed and henceit can not be configured. For Multi hop BFD mode UDP destination port is 4784which is fixed and it can not be configured either. In Single hop mode TTL is 255and in Multi hop mode TTL can be 1…255.

3 Create BFD session when Iub terminates in IFUH in IP Iub mode.

1. Click IP settings → Transport Address tab.





DN02166645Issue 23A

195

Commissioning AXC


Figure 166 Add BFD SessionYou can set the following BFD session parameters: • Enable the session by selecting Active and Session in use checkboxes. • Set Desired min. TX interval . Default is 500ms. Range is from 500 to 3000ms

in step of 500ms. • Set Required min. RX interval . Default is 500ms. Range is from 500 to 3000ms

in step of 500ms. • Set Detection multiplier . Default is 5. Range is from 2 to 10. • Set Destination address . (IP Address of the peer node to which BFD session

needs to be established.) • Set Source address .

4. Click OK to send the changes to the node.g Single BFD session is supported when Iub termination is pointing to IFUH in IP

Iub mode.

4 BFD sessions can be viewed.

Figure 167 BFD Sessions

Click Close to close the window.



196 DN02166645Issue 23A

Commissioning AXC

Id:0900d8058082ea5bConfidential

5.28 QoS Aware Ethernet switching

Purpose

With QoS aware Ethernet switching enabled, transport interface can be enhanced withthe following features:

• QoS awareness • VLAN awareness • Egress scheduling and shaping• Ingress policing (Rate Limiting)

QoS based Ethernet switching is supported on a ll the three AXCF transport interfaces.

Before you start

QoS Aware Ethernet switching is a licensed feature. Activating a valid license file on thenode is a prerequisite.

Steps

1 Configure the transport interface.

For information, see Configuring AXCF interfaces in IP Iub and Dual Iub mode .



DN02166645Issue 23A

197

Commissioning AXC


2 Click Configuration → Ethernet Switching.

Figure 168 Ethernet Switching

3 Configure QoS classification mode.

1. Click Modify... and select QoS classification mode.



198 DN02166645Issue 23A

Commissioning AXC


Figure 169 Modify QoS Classification - DSCP

g The default mode is DSCP.2. Set the parameters and click Apply to send changes to the node.3. To change the QoS classification mode to VLAN-PCP, select it from the drop down

menu.



DN02166645Issue 23A

199

Commissioning AXC


Figure 170 Modify QoS Classification - VLAN-PCP

4. Set the parameters and click Apply to send changes to the node.

4 Configure VLAN aware switching.

QoS aware interfaces can be made VLAN aware.

1. Click Modify... .

Figure 171 Ethernet Switching - VLAN aware configurationModify VLAN Aware Configuration window opens.



200 DN02166645Issue 23A

Commissioning AXC


Figure 172 Modify VLAN Aware Configuration

2. Select VLAN aware switching option and click Apply .

5 Configure Egress scheduling and shaping.

1. Select the interface and click Modify... .

Modify Ethernet Interface Switching window opens.

Figure 173 Modify Ethernet Interface Switching

• Select Switch in use field. • Select Egress shaper rate . Supported Egress shaping rates in Mbps are 1000,

13-1, 16, 17, 18, 22, 24, 26, 29, 32, 36, 41, 48, 58, 72, 96, 143, 286.• Select Ingress rate limiting . Supported Ingress rate limiting rates in Mbps are

1000, 13-1, 16, 17, 18, 22, 24, 26, 29, 32, 36, 41, 48, 58, 72, 96, 143, 286. • Select Marker on field.

• Define range for VLAN ID list from 0 to 4094.g Egress shaping rate set to 1000Mbps indicates no shaping.

Ingress rate limiting rate set to 1000Mbps indicates no rate limiting.2. Click Apply to send changes to the node.



DN02166645Issue 23A

201

Commissioning AXC


Figure 174 Ethernet Switching



202 DN02166645Issue 23A

Commissioning AXC


5.29 Dynamic routing for Iub

Purpose

The purpose of dynamic rerouting for Iub is to improve backhaul network resilience byadding a route protection mechanism in conjunction with the existing BFD functionality.This feature adds OSPF routing protocol for best route calculation to the destination. Italso allows for dynamic auto-configuration of the routing table in the BTS as well as pro-tection of the traffic towards BTS.

Before you start

Dynamic routing for is a licensed feature. Activating a valid license file on the node is aprerequisite.

Steps

1 Configure the router ID.

As router ID you can set transport IP address, virtual IP address, or VLAN address.

1. Configuring transport IP address as router ID.For more information, see Configuring AXCF interfaces in IP Iub and Dual Iub mode .

2. Configuring virtual IP address as router ID.Click Configuration → Application Addresses .

Figure 175 Application AddressesClick Modify... to set the virtual IP address.



DN02166645Issue 23A

203

Commissioning AXC


Figure 176 Modify Application Addresses

Click Apply to send the change to the node. The assigned IP address is reflected in Application Addresses window.

Figure 177 Application Addresses

3. Configuring VLAN address as router ID.For more information, see Configuring VLAN Differentiation .

2 Create OSPF areas.

For more information, see Creating OSPF areas .

3 Enable OSPF and activate OSPF with BFD.

Click IP Settings → OSPF tab.



204 DN02166645Issue 23A

Commissioning AXC


Figure 178 OSPF tabClick Modify... . Modify OSPF window opens.



DN02166645Issue 23A

205

Commissioning AXC


Figure 179 Modify OSPF

Select Enabled field to enable OSPF. Click OK .

To activate OSPF with BFD, click Modify... .



206 DN02166645Issue 23A

Commissioning AXC


Figure 180 OSPF tabModify OSPF window opens. Select OSPF with BFD check box to enable OSPF withBFD.



DN02166645Issue 23A

207

Commissioning AXC



4 Configure OSPF.


Figure 182 OSPF tab - IP InterfacesClick Modify... to modify selected IP interface. Modify OSPF window opens.



208 DN02166645Issue 23A

Commissioning AXC



Configure Timing parameters:

• Hello interval can be set in range 1-65535s. • Router dead interval can be set in range 1-65535s. • Retransmission interval can be in range 1-65535s. • Transmit delay can be set in range 1-65535s. • Hello multiplier varies in range 2-20.

5 Enable OSFP on BFD.


Figure 184 OSPF tab - IP Interfaces

Click Modify... . Modify OSPF window opens.



DN02166645Issue 23A

209

Commissioning AXC



Select Active field and set the parameters:

• Router ID is the transport interface address that has been defined is step 1. • Reference bandwidth value in the range 1-10000 Mbps • Select a Preference value in the range 1-255 Mbps • SPF delay can be set in the range 0-600000 ms. • SPF holdtime can be set in the range 0-600000 ms. • SPF maximum holdtime can be set in the range 0-600000 ms. • For more information on setting BFD parameters, see Creating BFD sessions .



210 DN02166645Issue 23A

Commissioning AXC


Verifying commissioning

6 Verifying commissioningPurpose

It is recommended that the following checks are performed after commissioning.

Steps

1 Check the interface settings interfaces.

Check that the interfaces are functional:

• standard PDH links • Inverse Multiplexing for ATM (IMA) groups • ATM over fractional interfaces • Q1 Embedded Operation Channels (EOC)

• Circuit Emulation Service (CES) links • SDH interfaces • ATM over Ethernet interfaces

You can test the operation of the PDH and SDH interfaces by creating loops. For moreinformation see Configuring loopbacks .

2 Check the synchronization settings.

Check that the synchronization sources are defined and available.

3 Check the Virtual Path and Virtual Channel terminations and connections.

Check the ATM Virtual Path and Virtual Channel terminations and cross-connectionshave been created.

4 Check the DCN settings.

Check the Data Communication Network settings.

5 Check OSPF areas.

Check that all OSPF areas have been created.

6 Check the IP routing.

Check the IP routing entries.

7 Check the DHCP configurations.

Check that all DHCP configurations have been created.

8 Check the BTS IP settings.

Check that the BTS identifier and other related settings have been configured.



DN02166645Issue 23A

211

Commissioning AXC Verifying commissioning


9 Check the Restricted mode settings.

Check that the required exceptions have been defined if the Restricted Mode is enabled.

1 Check the NTP servers or system time.

Check that all configured Network Time Protocol servers, the server ports and their IPaddresses are visible in the list, or that system time has been defined.

11 Check the Iub terminations.

Check that the Iub terminations are functional.

12 Check the management protocol settings.

Check that the management protocol settings are configured.

13 Check faults.

Check the fault list in the AXC Manager. For more information see Reading AXC faults in Operating and Maintaining AXC .

14 Save the configuration.

Save the configuration of the AXC and store it in a safe place for back-up purposes.Click Node → Export Configuration... and select a location and name for the file.

15 Store the item code and serial number report.

It is recommended to store the network configuration on individual unit serial numberlevel to enable fast and efficient search in the network in case such information isneeded. For more information, see Storing item code and serial number for traceabilitypurposes in Operating and Maintaining AXC .

16 Check the Q1 Support Function settings.

Check that the Q1 Support Function has been configured.

17 Close the connection to the AXC.









212 DN02166645Issue 23A

Commissioning AXC


Checklist for AXC commissioning

7 Checklist for AXC commissioningSITE NAME

SITE IDSITE ADDRESS

AXC ID

Commissioning with an XML file

Commissioning with a macro

Manual commissioning

Check Check mark

Equipment has been installed according to the installationinstructions and site-specific documents.

Local Management Tool complies with AXC Manager hardwareand software requirements.TCP/IP settings of the LMT are correct.

All the necessary commissioning information is available.

Connect to the AXC with the AXC Manager.

Check Check mark

Download the XML file.

Activate the XML file and check the parsing results.Ping the public IP address of the node using AXC web interface.

Check Check mark

Run the pre-recorded macro.

Ping the public IP address of the node using AXC web interface.

Check Check mark

Check the hardware configuration.

Start recording macro.

Configure PDH interfaces.

Configure SDH interfaces (IFUC and IFUF).

Configure ATM over Ethernet interface (IFUH).

Create IMA groups.

Create fractional interfaces.

Configure Q1 EOCs.



DN02166645Issue 23A

213

Commissioning AXC Checklist for AXC commissioning


Commissioning IP Iub

Commissioning Dual Iub

Configure NND settings.

Create and activate timing sources.

Create Traffic Descriptors.

Set Access Profiles.

Create ATM terminations and cross-connections.

Configure CES settings.

Configure Iub terminations.

Configure the public IP address of the AXC.

Add OSPF areas.

Configure DCN interfaces.

Configure IP routes.Create DHCP configurations.

Create Restricted Mode exception rules.

Configure BTS IP settings.

Configure Network Timing Protocol.

Configure Q1 support function.

Configure Neighbour Node Discovery.

Configure Management Protocol.

Stop recording the macro and save it.

Ping the public IP address of the node using AXC web interface.

Check Check mark


Activate IP Iub transport mode.

Configure Ethernet interfaces (IFUH / AXCF).

Configure IP Iub settings.

Configure Quality of Service settings.

Configure synchronization.


Check Check mark


Activate Dual Iub transport mode.

Configure Ethernet interfaces ( AXCF).

Configure IP Iub settings.

Check Check mark



Commissioning AXCChecklist for AXC commissioning

Configure Quality of Service settings.

Configure Iub terminations for ATM Iub.

Configure DCN and transport routes.

Configure synchronization.


Check Check mark

Date post:	06-Jul-2018
Category:	Documents
Upload:	sinasabikona
View:	214 times
Download:	4 times

Axc Commissioning

Documents