Sie sind auf Seite 1von 214

Nokia Siemens Networks

WCDMA RAN, Rel. RU30,


Operating Documentation,
Issue 01

Commissioning AXC
DN02166645
Issue 23A
Approval Date 2010-12-15

Confidential

Commissioning AXC

The information in this document is subject to change without notice and describes only the
product defined in the introduction of this documentation. This documentation is intended for the
use of Nokia Siemens Networks customers only for the purposes of the agreement under which
the document is submitted, and no part of it may be used, reproduced, modified or transmitted
in any form or means without the prior written permission of Nokia Siemens Networks. The
documentation has been prepared to be used by professional and properly trained personnel,
and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes
customer comments as part of the process of continuous development and improvement of the
documentation.
The information or statements given in this documentation concerning the suitability, capacity,
or performance of the mentioned hardware or software products are given "as is" and all liability
arising in connection with such hardware or software products shall be defined conclusively and
finally in a separate agreement between Nokia Siemens Networks and the customer. However,
Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions
contained in the document are adequate and free of material errors and omissions. Nokia
Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which
may not be covered by the document.
Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO
EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED
TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY
OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION
IN IT.
This documentation and the product it describes are considered protected by copyrights and
other intellectual property rights according to the applicable laws.
The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark
of Nokia Corporation. Siemens is a registered trademark of Siemens AG.
Other product names mentioned in this document may be trademarks of their respective
owners, and they are mentioned for identification purposes only.
Copyright Nokia Siemens Networks 2010. All rights reserved

Important Notice on Product Safety


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

The same text in German:


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

Id:0900d80580815710
Confidential

DN02166645
Issue 23A

Commissioning AXC

Table of contents
This document has 214 pages.
Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1
1.1
1.2
1.3

DN02166645
Issue 23A

1.4
1.5
1.6
1.7

Setting up AXC Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .


Installing AXC Manager from NOLS . . . . . . . . . . . . . . . . . . . . . . . . . . .
Uninstalling AXC Manager. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing AXC Manager on Linux operating systems by means of command line . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Installing AXC Manager on Linux operating systems by means of GUI
Configuring network properties of LMT . . . . . . . . . . . . . . . . . . . . . . . . .
Connecting to AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Closing connection to AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

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

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

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

5
5.1
5.2
5.3
5.3.1
5.3.2
5.4
5.4.1
5.4.2
5.4.3
5.4.4
5.4.5
5.4.6
5.4.7
5.4.8
5.4.9
5.4.10
5.4.11
5.4.12
5.4.13
5.5
5.6
5.7
5.7.1
5.7.2
5.8
5.9
5.10
5.11

Manual commissioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
AXC interface configuration constraints. . . . . . . . . . . . . . . . . . . . . . . . . 30
Overview of commissioning AXC manually . . . . . . . . . . . . . . . . . . . . . . 32
Using the macro recorder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Recording a macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Running a macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Configuring transmission interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring PDH interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Configuring IFUC interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Configuring IFUF interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Configuring IFUH interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Configuring AXCF interfaces in IP Iub and Dual Iub mode . . . . . . . . . . 52
Configuring ATM over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Configuring IMA settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
Configuring fractional interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Configuring Q1 EOCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring CES Interworking function . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configuring CES pass-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Enabling and disabling NND . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Configuring Transport mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring Timing over Packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
Configuring synchronization. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
Configuring ATM settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Creating traffic descriptors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Modifying Access Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Configuring ATM interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Configuring Iub terminations without AXCF . . . . . . . . . . . . . . . . . . . . . . 91
Configuring Iub terminations in ATM and Dual mode with AXCF . . . . . 96
Configuring and activating IP Iub mode with AXCF . . . . . . . . . . . . . . . 102

Id:0900d80580815710
Confidential

13
13
14
15
16
17
18
20

Commissioning AXC

5.12
5.13
5.14
5.14.1
5.14.2
5.15
5.15.1
5.15.2
5.15.3
5.15.4
5.15.5
5.15.6
5.15.7
5.15.8
5.15.9
5.15.10
5.16

5.17
5.18
5.19
5.20
5.21
5.22
5.23
5.24
5.25
5.25.1
5.25.2
5.26
5.27
5.28
5.29

Configuring and activating IP Iub mode with IFUH . . . . . . . . . . . . . . . . 107


Configuring and activating Dual Iub mode with AXCF . . . . . . . . . . . . . 112
Creating ATM cross-connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating Virtual Path cross-connections . . . . . . . . . . . . . . . . . . . . . . . . 117
Creating Virtual Channel cross-connections. . . . . . . . . . . . . . . . . . . . . 119
Creating IP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Setting public IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Creating OSPF areas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Creating DCN connections for ATM interfaces . . . . . . . . . . . . . . . . . . . 125
Creating IP routes with AXCF/IFUH . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
Checking IP connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
Creating DHCP configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
Configuring BTS IP settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
Configuring Restricted Mode filtering . . . . . . . . . . . . . . . . . . . . . . . . . . 139
Creating NTP servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143
Configuring BTS Firewall . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
Configuring Management Protocol for Secure/Unsecured LDAP connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 146
Installing CA certificates manually for AXC. . . . . . . . . . . . . . . . . . . . . . 150
Installing CA Certificates manually for AXC Element Manager . . . . . . 153
Installing AXC Certificate and AXC private key manually . . . . . . . . . . . 158
Configuring CMP and CR server IP address . . . . . . . . . . . . . . . . . . . . 160
Configuring VLAN Differentiation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163
Configuring AXC Q1 Support Function . . . . . . . . . . . . . . . . . . . . . . . . . 167
Configuring loopbacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
Configuring BFD triggered static rerouting . . . . . . . . . . . . . . . . . . . . . . 170
Configuring Ethernet OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Configuring Link OAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 173
Configuring Service OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
IP Network Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Creating BFD sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
QoS Aware Ethernet switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Dynamic routing for Iub . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202

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

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

Id:0900d80580815710
Confidential

DN02166645
Issue 23A

Commissioning AXC

List of figures
Figure 1
Figure 2
Figure 3
Figure 4
Figure 5
Figure 6
Figure 7
Figure 8
Figure 9
Figure 10
Figure 11
Figure 12
Figure 13
Figure 14
Figure 15
Figure 16
Figure 17
Figure 18
Figure 19
Figure 20
Figure 21
Figure 22
Figure 23
Figure 24
Figure 25
Figure 26
Figure 27
Figure 28
Figure 29
Figure 30
Figure 31
Figure 32
Figure 33
Figure 34
Figure 35
Figure 36
Figure 37
Figure 38
Figure 39
Figure 40
Figure 41
Figure 42
Figure 43
Figure 44
Figure 45

DN02166645
Issue 23A

Logging in to AXC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Import Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set FTP server. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Activate restored node configuration . . . . . . . . . . . . . . . . . . . . . . . . . . .
Node configuration activation result. . . . . . . . . . . . . . . . . . . . . . . . . . . .
Recording a new macro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify PDH interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify IFUC interface, general settings. . . . . . . . . . . . . . . . . . . . . . . . .
Modify IFUC interface, Trail Trace settings . . . . . . . . . . . . . . . . . . . . . .
Modify IFUC interface, Protection settings. . . . . . . . . . . . . . . . . . . . . . .
Modify IFUF interface, general settings . . . . . . . . . . . . . . . . . . . . . . . . .
Modify IFUF interface, Trail Trace settings . . . . . . . . . . . . . . . . . . . . . .
KLM Chooser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify VC-12 frame, General settings. . . . . . . . . . . . . . . . . . . . . . . . . .
Modify VC-12 frame, Trail Trace settings . . . . . . . . . . . . . . . . . . . . . . .
Modify IFUF interface, Protection settings . . . . . . . . . . . . . . . . . . . . . . .
Configuring IFUH interface settings . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transport Addresses tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying transport Ethernet interface settings . . . . . . . . . . . . . . . . . . .
Hardware view pane . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring AXCF interface settings . . . . . . . . . . . . . . . . . . . . . . . . . . .
Transport Addresses tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Transport Ethernet Interface settings . . . . . . . . . . . . . . . . . .
ATM Over Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying general ATM Over Ethernet settings . . . . . . . . . . . . . . . . . . .
Creating a new PSN tunnel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a new Pseudowire . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
QoS tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify Traffic Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Inverse Multiplexing for ATM (IMA) window. . . . . . . . . . . . . . . . . . . . . .
Create new IMA group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fractional Interfaces window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Create fractional interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Q1 EOCs dialog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Q1 EOC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Circuit Emulation Service (CES) window . . . . . . . . . . . . . . . . . . . . . . . .
Add CES Interworking Function - unstructured . . . . . . . . . . . . . . . . . . .
Add CES Interworking Function - structured . . . . . . . . . . . . . . . . . . . . .
Circuit Emulation Service (CES) window . . . . . . . . . . . . . . . . . . . . . . . .
Adding a CES pass-through . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Neighbour Node Discovery window . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Switch Transport Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Timing over Packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify Timing over Packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Synchronization window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Id:0900d80580815710
Confidential

19
23
23
24
25
34
37
39
40
41
43
44
45
46
46
47
49
50
50
52
52
53
54
56
57
57
58
59
60
61
62
64
64
66
66
68
69
70
71
72
73
74
76
76
78

Commissioning AXC

Figure 46
Figure 47
Figure 48
Figure 49
Figure 50
Figure 51
Figure 52
Figure 53
Figure 54
Figure 55
Figure 56
Figure 57
Figure 58
Figure 59
Figure 60
Figure 61
Figure 62
Figure 63
Figure 64
Figure 65
Figure 66
Figure 67
Figure 68
Figure 69
Figure 70
Figure 71
Figure 72
Figure 73
Figure 74
Figure 75
Figure 76
Figure 77
Figure 78
Figure 79
Figure 80
Figure 81
Figure 82
Figure 83
Figure 84
Figure 85
Figure 86
Figure 87
Figure 88
Figure 89
Figure 90
Figure 91

Adding a synchronization timing source . . . . . . . . . . . . . . . . . . . . . . . . . 79


Synchronization overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
Traffic Descriptors. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Creating a new traffic descriptor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Access Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
Modifying an Access Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
New VP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Creating a new Virtual Path and Virtual Channel . . . . . . . . . . . . . . . . . . 89
Iub Terminations to BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
Creating a new Common NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Creating a new Dedicated NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
Creating a new AAL2 signalling link (BTS AAL2 Multiplexing not in use)93
Creating a new AAL2 signalling link (BTS AAL2 Multiplexing in use) . . . 94
Creating a new AAL2 user path (BTS AAL2 Multiplexing not in use) . . . 94
Creating a new AAL2 user path (BTS AAL2 Multiplexing in use) . . . . . . 95
Iub terminations to BTS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
Creating a new Common NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Creating a new Dedicated NBAP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Common NBAP and Dedicated NBAP in Iub Terminations to BTS window
97
Creating a new AAL2 signaling link . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
AAL2 signaling link in Iub Terminations to BTS window . . . . . . . . . . . . . 99
Creating a new AAL2 user path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
AAL2 User Path in Iub Terminations to BTS window . . . . . . . . . . . . . . 100
Defining IP Iub settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
QoS tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
Modifying queue weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
Modifying traffic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
IP settings - IP Iub. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
Defining IP Iub settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
QoS tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Modifying queue weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110
Modifying traffic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111
Modify Iub IP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
QoS tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Modifying queue weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114
Modifying traffic types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
Creating a new Virtual Path cross-connection . . . . . . . . . . . . . . . . . . . 117
Creating a new Virtual Channel cross-connection . . . . . . . . . . . . . . . . 119
IP Interfaces window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
Setting the public IP address of the AXC . . . . . . . . . . . . . . . . . . . . . . . 122
IP Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
Add OSPF area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
IP Settings window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
Adding a DCN for ATM interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
OSPF Timing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
Modifying DCN for LMP interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

Id:0900d80580815710
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 92
Figure 93
Figure 94
Figure 95
Figure 96
Figure 97
Figure 98
Figure 99
Figure 100
Figure 101
Figure 102
Figure 103
Figure 104
Figure 105
Figure 106
Figure 107
Figure 108
Figure 109
Figure 110
Figure 111
Figure 112
Figure 113
Figure 114
Figure 115
Figure 116
Figure 117
Figure 118
Figure 119
Figure 120
Figure 121
Figure 122
Figure 123
Figure 124
Figure 125
Figure 126
Figure 127
Figure 128
Figure 129
Figure 130
Figure 131
Figure 132
Figure 133
Figure 134
Figure 135
Figure 136
Figure 137
Figure 138

DN02166645
Issue 23A

IP Settings - Routing window - DCN routing . . . . . . . . . . . . . . . . . . . .


Add IP Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Settings - Routing window - Transport routing . . . . . . . . . . . . . . . .
Checking IP connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Settings - DHCP Configurations window . . . . . . . . . . . . . . . . . . . . .
Adding a DHCP configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
IP Settings - BTS Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Configuring BTS IP settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Restricted Mode Filtering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Adding a Restricted Mode rule. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
System Time window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add NTP server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set system time manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Management Protocol window. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modifying Base ID and Parent ID. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add Registration Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Intervals and Periods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Registration Service entry in Management Protocol dialog . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
AXC Element Manager window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Certificate Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic Management window . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Automatic Management window during storing the values . . . . . . . . .
Transport Addresses tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add VLAN interface window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Modify VLAN mapping window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Setting Q1 Support Function channel . . . . . . . . . . . . . . . . . . . . . . . . .
Q1 Support Function output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Creating a loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Routing tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add IP Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Routing tab with IP routes added. . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Set route reinstallation delay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Link OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Link OAM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Add Link OAM Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Link OAM Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Ethernet Link OAM window - Ethernet interfaces . . . . . . . . . . . . . . . .
Modify Ethernet Interface. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Newly mapped Link OAM profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Id:0900d80580815710
Confidential

130
130
131
133
134
135
136
137
139
140
143
143
144
146
146
148
149
149
150
151
151
153
154
155
156
157
158
159
161
161
164
165
166
167
168
169
171
171
172
172
174
175
175
176
177
177
177

Commissioning AXC

Figure 139
Figure 140
Figure 141
Figure 142
Figure 143
Figure 144
Figure 145
Figure 146
Figure 147
Figure 148
Figure 149
Figure 150
Figure 151
Figure 152
Figure 153
Figure 154
Figure 155
Figure 156
Figure 157
Figure 158
Figure 159
Figure 160
Figure 161
Figure 162
Figure 163
Figure 164
Figure 165
Figure 166
Figure 167
Figure 168
Figure 169
Figure 170
Figure 171
Figure 172
Figure 173
Figure 174
Figure 175
Figure 176
Figure 177
Figure 178
Figure 179
Figure 180
Figure 181
Figure 182
Figure 183
Figure 184
Figure 185

Ethernet Link OAM - Link OAM Loopback . . . . . . . . . . . . . . . . . . . . . . 178


Modify Remote Loopback Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Ethernet Link OAM Loopback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 178
Ethernet Link OAM window - Link OAM Reset . . . . . . . . . . . . . . . . . . . 179
Ethernet Link OAM Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Service OAM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
New Maintenance Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Service OAM - New Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Add New Association . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
Service OAM - New Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182
Add New Endpoint . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Add Remote Endpoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 184
Service OAM - Service OAM Cir Value. . . . . . . . . . . . . . . . . . . . . . . . . 184
Modify OAM CIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 185
Service OAM - Insert optional TLV into reply messages . . . . . . . . . . . 185
Modify OAM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186
RTT tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Modify RTT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Modify RTT - Reflector on . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
RTT tab - Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 188
Modify Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189
RTT tab - Session statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190
Transport Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191
BFD Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Add BFD Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Transport Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
BFD Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Add BFD Session . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
BFD Sessions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Modify QoS Classification - DSCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Modify QoS Classification - VLAN-PCP . . . . . . . . . . . . . . . . . . . . . . . . 199
Ethernet Switching - VLAN aware configuration . . . . . . . . . . . . . . . . . . 199
Modify VLAN Aware Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Modify Ethernet Interface Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . 200
Ethernet Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Application Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 202
Modify Application Addresses. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
Application Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203
OSPF tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
OSPF tab . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 206
Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
OSPF tab - IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207
Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
OSPF tab - IP Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Modify OSPF. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 209

Id:0900d80580815710
Confidential

DN02166645
Issue 23A

Commissioning AXC

List of tables
Table 1
Table 2
Table 3
Table 4
Table 5
Table 6

DN02166645
Issue 23A

Supported VPI/VCI bits . . . . . . . . . . . . . . . .


TLS operating mode . . . . . . . . . . . . . . . . . .
Filter rules for management plane traffic . .
Filter rules for control plane traffic . . . . . . . .
Filter rules for user plane traffic . . . . . . . . .
Base ID and Parent NE ID naming scheme

Id:0900d80580815710
Confidential

.......
.......
.......
.......
.......
.......

......
......
......
......
......
......

.......
.......
.......
.......
.......
.......

. 30
138
141
141
141
147

Summary of Changes

Commissioning AXC

Summary of Changes
Changes between document issues are cumulative. Therefore, the latest document
issue 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 have
been updated.
Figures Service OAM, New Maintenance Domain, Service OAM - New Association,
Service OAM - New Endpoint, Add New Endpoint, Add Remote Endpoint, Service
OAM - 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 (see
step Configure the transport addresses.). Also figure Modifying transport Ethernetinterface 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 beenremoved 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.

10

Id:0900d8058082eaa6
Confidential

DN02166645
Issue 23A

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 been
added.
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-0825, WCDMA RAN RU20)
Configuring AXCF interfaces in IP Iub and Dual Iub mode (5.4.5)

DN02166645
Issue 23A

Id:0900d8058082eaa6
Confidential

11

Summary of Changes

Commissioning AXC

Synchronous Ethernet has been added to the list of mechanisms that require atransport 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 Verification).

12

Id:0900d8058082eaa6
Confidential

DN02166645
Issue 23A

Commissioning AXC

Setting up AXC Manager

1 Setting up AXC Manager


1.1

Installing AXC Manager from NOLS


Purpose
You can install the AXC Manager from Nokia Online Services (NOLS). The setup
program creates all the necessary directories and installs the program and data files on
the 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 the
application.
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
1

Go to NOLS web page.

Create a temp-directory on the LMT.

Extract all AXC Manager installation files into this directory.

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 not
have administrative rights on the LMT, an error message is to be generated. From the
error dialog you can select a directory where you have write access and store AXC
Manager installation files in this directory.

Depending on the configuration, it may be necessary to restart the LMT before


running AXC Manager for the first time.
Further information
For instructions on uninstalling AXC Manager, refer to Uninstalling AXC Manager.

DN02166645
Issue 23A

Id:0900d805807f9e01
Confidential

13

Commissioning AXC

1.2

Uninstalling AXC Manager


Purpose
This procedure describes how to uninstall AXC Manager from the Local Management
Tool.
Steps

Start AXC Manager Uninstall program.


Start the program from the Start menu (Start Programs Nokia Siemens
Networks Managers AXC Uninstall Managers).

Uninstall the AXC Manager.


Click Uninstall and wait until the uninstallation is complete. You can cancel the process
by 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 removed
either.

14

Id:0900d805807f9dfb
Confidential

DN02166645
Issue 23A

Commissioning AXC

1.3

Installing AXC Manager on Linux operating systems by


means of command line
Purpose
There are two options for installing the AXC Manager on Linux operating systems: as a
root user or simply as an AXC user (non-root user). This means that the user does not
have 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

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 the
user, 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 or
change 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 the
writing rights to the directory. This means that you have to install it to a directory
you have the writing rights to, for example
home/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 installation files cannot be written to their correct destination directories and as a result,
there will be no menu shortcuts created and the executable axcmanagerwill not be
installed in the "/usr/local/bin" directory. You will have to complete some additional
steps 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 typechmod + 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 and
pressing Enter.

DN02166645
Issue 23A

Id:0900d805807f9dfc
Confidential

15

Commissioning AXC

1.4

Installing AXC Manager on Linux operating systems by


means of GUI
Steps

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 the user, that is the non-root
user 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 or
change it.
Installing AXC Manager as an AXC user (axcuser):
The default path is /opt/Nokia Siemens Networks/Managers/AXC/, but a regular
user rarely has the writing rights to the directory. This means that you have to
install it to a directory you have the writing rights to, for example
home/axcuser/NSN/AXC_Manager/C6.0.
k) Continue by clicking Next.
The installer will now start installing the program. Please note that when installing
the AXC EM as a non-root user, some of the installation files cannot be written to
their correct directories and as a result, there will be no menu shortcuts created and
the executable axcmanager will not be installed in the "/usr/local/bin" directory. You
will 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 and
pressing Enter.

16

Id:0900d805807f9dfd
Confidential

DN02166645
Issue 23A

Commissioning AXC

1.5

Configuring network properties of LMT


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

DN02166645
Issue 23A

Set the IP address to 192.168.255.130

Set the network mask to 255.255.255.128

Set the Default gateway to 192.168.255.129

Id:0900d805807f9dfe
Confidential

17

Commissioning AXC

1.6

Connecting to AXC
Purpose
You can connect to the AXC either locally or remotely. Through the Local Management
Port (LMP) of the AXU you can access the AXC you are physically connected to. Once
the Data Communications Network (DCN) has been configured, it is also possible to
access 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 communication
cable.

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.

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 you
want to establish a remote connection, enter the public IP address of the AXC or select
one of the addresses from the list. The list contains the addresses of five AXCs that have
been previously connected to.
Then enter the username and password to the appropriate fields. The default name is
Nemuadmin and default password nemuuser.
Name and password are case sensitive.

18

It is recommended to change the default password. For more information see


Changing AXC local account in Operating and Maintaining AXC.

Id:0900d805807f9dff
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 to
configure the AXC after establishing a connection, select Use Background Refresh
from File Preferences. To take this feature immediately into use, restart the AXC
Manager.

DN02166645
Issue 23A

Id:0900d805807f9dff
Confidential

19

Commissioning AXC

1.7

Closing connection to AXC


Steps

Click File Disconnect.

Save edited data.


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

20

Id:0900d805807f9e00
Confidential

DN02166645
Issue 23A

Commissioning AXC

Prerequisites for commissioning AXC

2 Prerequisites for commissioning AXC


Before 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 system
requirements
the network properties of the LMT have been set as described in Configuring
network properties of LMT
the AXC Manager has been installed on the LMT as described in Installing AXC
Manager from NOLS
AXC-FB Hopper Manager and GCS R4.2 have been installed on the LMT as
described in Commissioning FlexiHopper (Plus) and MetroHopper with IFUE (only if
IFUE is installed)
you have access rights to the managed AXC
you have all the necessary commissioning documentation and information available.

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

DN02166645
Issue 23A

Id:0900d805807f9e02
Confidential

21

Commissioning AXC with XML configuration file

Commissioning AXC

3 Commissioning AXC with XML configuration


file
Purpose
All parameters needed to configure the AXC are defined in the planning phase.
For automated commissioning an XML file containing the necessary parameters is
created. This XML file can be created for example with NetAct Transmission Planner,
which is also the recommended tool for doing Iub dimensioning for the AXC. The result
of 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 file
to an AXC-specific XML configuration file (sometimes referred to as an AML file). With
Plan Editor it is also possible to include additional parameters in the XML file. After this
the XML file can be exported to the AXC for automated commissioning.
The XML configuration file is transferred from PlanEditor to the AXC either locally or
remotely. In local XML file transfer the XML configuration file is transferred directly from
PlanEditor to the Local Management Tool (LMT). The file is downloaded to the AXC
when the AXC Manager that is installed to the LMT is connected directly to the AXC. In
remote XML file transfer the XML configuration file is transferred to NetAct Radio Access
Configurator where the Site Configuration Tool (SCT) organises the files to the particular
sites. The AXC Manager running in the NetAct Radio Access Configurator transfers the
configuration 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 AXC
Manager or by using the AXC web interface. For more information, see Accessing AXC
with web browser in Troubleshooting AXC.
Factory settings can be restored only locally, since all configurations in the AXC, including the Data Communication Network (DCN) connection, are deleted.
The AXC Manager contains a File Transfer Protocol (FTP) server that is used if the
XML configuration files or software packages are located on the same PC as the AXC
Manager. This integrated FTP server does not need to be configured, and it is activated
automatically when necessary. For remote file transfer an external FTP server has to
used.
If the integrated FTP server is used, you must close all other FTP servers running on the
same PC to avoid port conflicts.
If an external FTP server is used, make sure that the XML configuration file is accessible
to the AXC and that the FTP server is online and running.

22

Id:0900d805807f9e03
Confidential

DN02166645
Issue 23A

Commissioning AXC

Commissioning AXC with XML configuration file

Steps
1

Click Node Import configuration...


The Import Configuration window opens.

Figure 2
2

Import Configuration

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, the
FTP 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.

DN02166645
Issue 23A

Id:0900d805807f9e03
Confidential

23

Commissioning AXC with XML configuration file

Commissioning AXC

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 FTP
server) 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.

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.

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 configurations.
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 registers to NetAct.
Verification
Once the automated commissioning is completed, you can check the results by clicking
Show results in the Import Configuration window.

24

Id:0900d805807f9e03
Confidential

DN02166645
Issue 23A

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 configuration 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 configuration 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 commissioning
concept in AXC product description.

DN02166645
Issue 23A

Id:0900d805807f9e03
Confidential

25

Using AXC Manager as Command Line Tool

Commissioning AXC

4 Using AXC Manager as Command Line Tool


Purpose
Some AXC Manager operations can be executed from a command line. These operations 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 command
line parameters. The output of the operation, including possible error messages, is
written 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 Siemens
Networks\Managers\AXC\NodeManagers\AXCManager<version>.
The following parameters are obligatory for all operations:

-ne <IpAddress> specifies the IP address of the remote AXC node


or
-ior <ior | filename> specifies either the CORBA IOR or the file that contains
the CORBA IOR
-pw <username:password> specifies the NWI3 username and password for
login

The following obligatory parameters specify the operations to be performed:

26

-import_conf <filename> specifies the path and filename for the configuration
file to be imported
-export_conf <filename> specifies the path and filename for the configuration
file to be exported (if the path is not specified, the file is saved to the AXC Manager
installation 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 Build
Descriptor XML file to be downloaded to the remote AXC node
-activate_sw sends an activate node software command to the remote AXC
node. 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 AXC
Manager installation directory)

Id:0900d805807f9e04
Confidential

DN02166645
Issue 23A

Commissioning AXC

Using AXC Manager as Command Line Tool

-download_lic <filename> specifies the path and filename of the licence file
to 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 to
the remote AXC node
-export_hw_information <filename> specifies the path and filename for the
hardware information to be exported (if the path is not specified, the file is saved to
the FileStorage folder in the AXC Manager installation directory)

In addition, there are the following optional parameters:

-ftp <IpAddress:ftpusername:ftppassword> specifies the parameters for


an FTP session if the configuration is imported from an external FTP server (if the
parameter is not given, the internal FTP server of the AXC is used)
-cltlog <filename:clear> specifies the path and filename for the Command
Line Tool log file. If the filename is not given, the operation is logged in the default
clt.log file in the AXC installation directory. <:clear> indicates that the existing
log file is to be cleared. If it is not given, new log entries are added to the end of the
log 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 following
command:
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 file
using the internal or external FTP server. After the operation has been executed, AXC
Manager logs out from the node and closes. Information about the progress of the operation and possible error messages are logged to the log file.

Activate a node configuration.


Give the following command:

DN02166645
Issue 23A

Id:0900d805807f9e04
Confidential

27

Using AXC Manager as Command Line Tool

Commissioning AXC

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 give
the activation parameter separately, the AXC Manager activates the previously imported
configuration.
3

Export a node configuration.


Give the following command:
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.

Download new software.


Extract the software package using an appropriate tool, maintaining the directory structure as described in Changing AXC software in Expanding and upgrading AXC. The file
to be downloaded is the Target Build Descriptor XML file.
Give the following command:
AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>
-download_sw <filename>
If you want download new software from an external FTP server, give the following
command:
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 using
the 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

Activate 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. If
you give the activation parameter separately, the AXC Manager activates the previously
downloaded software.

Rollback node software.


Give the following command:

28

Id:0900d805807f9e04
Confidential

DN02166645
Issue 23A

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 configuration
to a file. If the directory structure does not exist, it will be created.

Download a licence file.


Give the following command:
AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>
-download_lic <filename>
If you want download the licence file from an external FTP server, give the following
command:
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 using
the internal or external FTP server. The new licence file is taken automatically in use.

Delete a licence file.


Give the following command:
AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>
-delete_lic <filename>

10

Export licence status.


Give the following command:
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.


Give the following command:
AXCEMStartWithoutCL.bat -ne <IpAddress> -pw <username:password>
-export_hw_information <filename>
The AXC Manager connects to the remote node and exports the hardware information
file to the FileStorage folder in AXC Manager installation directory.

DN02166645
Issue 23A

Id:0900d805807f9e04
Confidential

29

Manual commissioning

Commissioning AXC

5 Manual commissioning
5.1

AXC interface configuration constraints


Physical and logical interfaces
A logical interface is an interface that has a logical implementation on top of one or more
physical 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 implementation.
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 all
lower capacity interfaces have been unlocked.
VPI/VCI bit allocation
The VPI/VCI bit allocation is modifiable. The table below shows the number of bits supported for VPI and VCI per physical/logical interface.
Bits (AXC and S-AXC)

Bits (AXC Compact)

VPI

18 (default 4)

15 (default 2)

VCI

112 (default 7)

Table 1

Supported VPI/VCI bits

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. The
default number of VPI bits is 2. It can be changed as long as the number of logical interfaces is smaller than 8. The number of VCI blocks required by an interface is 2 to the
power of VPI bits (2VPI 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 (23 *
1 + 22 * 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 are
configurable but should not be used. They are reserved by standardisation bodies for
other purposes.
VC 21 in Virtual Path (VP) 0 is reserved for Neighbour Node Discovery (NND) which is
an ATM end-to-end management feature.

30

Id:0900d805808176de
Confidential

DN02166645
Issue 23A

Commissioning AXC

Manual commissioning

Characters supported by the AXC Manager

DN02166645
Issue 23A

NUL

SOH

STX

ETX

EOT

ENQ

ACK

BEL

DLE

DC1

DC2

DC3

DC4

NAK

SYN

ETB

SP

BS

HT

LF

VT

FF

CR

SO

SI

CAN

EM

SUB

ESC

FS

GS

RS

US

=
L

Id:0900d805808176de
Confidential

31

Commissioning AXC

5.2

Overview of commissioning AXC manually


Purpose
The AXC can be commissioned either manually or automatically by downloading an
XML configuration file to the AXC. In manual commissioning all necessary parameters
are 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 install
the unit in the AXC Manager even in cases when the actual IFU hardware is not plugged
in. 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

Log in to the AXC with the AXC Manager.

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.

32

Configure the PDH interface settings.

Configure the IFUC interface settings.

Configure the IFUF interface settings.

Configure the IFUH/AXCF interface settings.

Configure the ATM over Ethernet settings.

Configure the IMA settings.

Configure the fractional interfaces.

10

Configure the Q1 Embedded Operation Channels.

11

Configure the synchronization settings.

Id:0900d805807f9e12
Confidential

DN02166645
Issue 23A

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.

20

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 ensure
that you have performed all the necessary configurations.
You can open the Commissioning Status dialog by selecting Node Commissioning
Status. You can also view the status information on the toolbar.
Furthermore, it is possible to have AXC Manager check commissioning status whenever
you are logging out. To do this, select Check Status During Logout and Exit from File
Preferences.

DN02166645
Issue 23A

Id:0900d805807f9e12
Confidential

33

Commissioning AXC

5.3
5.3.1

Using the macro recorder


Recording a macro
Purpose
This procedure describes how to record a macro with the AXC Manager. The macro
recorder function of the AXC Manager can be used to record, store, and run sequences
of operations.
For instructions on how to run a recorded macro, see Running a macro.
Steps

Click Tools Macro Record.


The Record Macro dialogue box opens.

Figure 6
2

Recording a new macro

Enter the name and description for the macro.


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

Save the macro.


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

Start recording the macro.


When you are ready to start recording the macro, click Start. The recording control
dialogue appears with the name of the macro visible in the title bar.
When the Macro Recorder is recording, all operations performed with the AXC Manager
are recorded in the open macro.
Note that an operation must be completed and successfully sent to the AXC by the AXC
Manager before it is recorded in the macro.

No software management operations, such as software download or activation of


new software, should be carried out during macro recording because of differences
between software versions.
Refresh, Inspect, Logout and Disconnect are not recorded in the macro.

34

Id:0900d805807f9e15
Confidential

DN02166645
Issue 23A

Commissioning AXC

If you want to carry out operations on the AXC Manager that you do not want to be
stored in the macro
Then
Pause recording the macro.
Click Pause to pause recording. You can now carry out operations that will not be
recorded in the macro.
Click Resume to resume recording the macro. Operations carried out are now recorded
in the macro.

Stop recording and store the macro.


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

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. The
dialogue provides information about the selected macro.
Click Delete. Confirm the deletion by clicking Yes.

DN02166645
Issue 23A

Id:0900d805807f9e15
Confidential

35

Commissioning AXC

5.3.2

Running a macro
Purpose
This procedure describes how to run macros with the AXC Manager. The pre-recorded
macros can be used to run a sequence of operations in order to, for example, commission 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 the
macro was recorded.
Steps

Click Tools Macro Run.


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

Click Run to run the macro.


Expected outcome
The macro is executed. A progress bar on the Run Macro dialogue box displays the
progress of macro execution. If the macro is executed successfully, the message next
to the progress bar changes to "Completed". You can see the new settings after the AXC
Manager has performed an automatic refresh.
Unexpected outcome
If the macro execution is unsuccessful, a message box displays with a list of errors that
occurred during execution. The message next to the progress bar changes to failed.

36

Id:0900d805807f9e14
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.4
5.4.1

Configuring transmission interfaces


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 E1


and E1 within Flexbus interfaces.
Before you start
The AXC Compact (AXCC and AXCD) does not support fractional interfaces and Q1
EOCs.
In the AXC Manager, the IFUE is displayed as an interface unit with 16 E1 interfaces
and 3 Flexbus interfaces (greyed out). The ATM part of the IFUE is treated as any other
interface unit and can therefore be configured with the AXC Manager. Flexbus-related
configurations 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 click
Modify. The Modify Interface window opens.

Figure 7
2

Modify PDH interface

Take the interface into use.


Select In use, ATM interface or both.
Selecting ATM interface enables you to configure ATM settings for the interface.

DN02166645
Issue 23A

Id:0900d805808176e0
Confidential

37

Commissioning AXC

When the interface is not in use, framing is transmitted but ATM traffic not. Alarms are
suppressed.
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 created
the 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 PDH
interface units are:

IFUA: E1, JT1, T1


IFUD: E1
IFUE: E1
AXCC: E1, JT1, T1
AXCD: E1

Frequent switching between interface types may cause problems and should be
avoided.
No mixed configurations of E1/JT1/T1 are allowed on the same IFUA or AXCC. If you
change the PDH interface type, the change is applied to all interfaces of the unit and
configurations are deleted, cutting off all running traffic.
The available line types are the following:

E1 (IFUA, IFUD, AXCC/D): MultiFrame G704 (default, CRC on), DoubleFrame


G704 (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 line
type 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. The
highest Tx power output for the line interface is 0 dB and it can be attenuated in order
to avoid overloading the interface. The Lbo value has to be defined only for JT1 and
T1 interfaces.
Bit error rate (BER) mode: possible values are 10-3 (default) and 10-6.

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.

38

Id:0900d805808176e0
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.4.2

Configuring IFUC interfaces


Purpose
The SDH/SONET interfaces of the IFUC interface unit can be configured as either STM1 mapping VC-4 or STS-3c mapping OC-3.
Redundant SDH/SONET links can also be established to protect operational links in
case of a failure. The switching type is bi-directional revertive or non-revertive. For more
information, see AXC protection options in AXC product description.
Steps

Select the interface in the Hardware view.


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

Figure 8
2

Modify IFUC interface, general settings

Take the interface into use.


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 suppressed.

Switch the laser on if necessary.


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

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


If necessary, select another Interface Type from the list.

DN02166645
Issue 23A

Id:0900d805807f9e17
Confidential

39

Commissioning AXC

A mixture of STM-1 and STS-3c types is allowed on an IFUC. However, if you change
the 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.

Select RDI on EBER if necessary.


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

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 Expected
ID. 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 alarm 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 ID
is not selected, an empty string will be expected.
8

Send the changes to the node.


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

40

Id:0900d805807f9e17
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 interface
when the working interface is repaired after a failure. In non-revertive mode, the
traffic 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 in
MSP1+1 mode.
The AXC supports MSP1:1. MSP1:1 with MSP1+1 compatibility is interoperable with
MSP1+1 implemented in the RNC. The AXC also operates with third-party equipment supporting MSP1:1 or MSP1+1 compatible with MSP1:n as described in
G.783, Annex A.

Select both Protected and Protecting unit and interface from the lists. The Protecting
interface can be either on the same or different unit as the protected interface. If you
want to change the Protected or Protecting unit or interface, first select the interface and
click 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.

DN02166645
Issue 23A

Id:0900d805807f9e17
Confidential

41

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 unit

The AXC supports 8 SDH/SONET interfaces and can use up to 7 additional


SDH/SONET interfaces for protection. Interfaces used for protection cannot carry additional ATM user traffic.
A switchover can be performed by clicking Switch Over and cleared by clicking Clear
Switch Over. The actions depend on the states of the protected and protecting interfaces as follows:
Interface state

Switch Over

Clear Switch Over

Protected IF active, no
alarms in protecting IF

Switches the traffic to pro- Disabled


tecting IF

Protecting IF active, no
alarms in protected IF

Disabled

In revertive mode, switches


the traffic to protected IF (in
case a manual switch has
been performed). In nonrevertive mode, traffic will
stay in protecting IF until
alarms are raised on it.

Protecting IF active,
alarms in protected IF

Disabled

In revertive mode, switches


the traffic to protected IF
when all alarms are cleared
(in case a manual switch has
been performed). In nonrevertive mode, traffic will
stay in protecting IF until
alarms are raised on it.

Protected IF active, alarms


in protecting IF

Disabled

Traffic will stay in protected


IF even if alarms are cleared
in protecting IF.

Note that these MSP requests do not necessarily lead to a switchover. A state machine
evaluates all local and remote requests and decides by means of a priority table if a switchover 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 switchover request), a switch back to the protected interface could be accomplished by temporarily putting the group into revertive mode.
Click Protection Statistics to get information on the number and duration of switches
that have happened between the protected and protecting interfaces.
Further information
For instructions on how to create loops, see Configuring loopbacks.

42

Id:0900d805807f9e17
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.4.3

Configuring IFUF interfaces


Purpose
The STM-1 interface of the IFUF interface unit provides 63 x VC-12 connections. The
multiplexing 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 seven
TUG-2 and each TUG-2 multiplexes three TU-12. The resulting 63 instances are
numbered 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 to
an 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
1

Select the interface in the Hardware view.


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

Figure 11
2

Modify IFUF interface, general settings

Take the interface into use.


Check the In use box.

DN02166645
Issue 23A

Id:0900d805807f9e18
Confidential

43

Commissioning AXC

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

Switch the laser on if necessary.


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

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 fault
will trigger the sending of the Remote Defect Indication signal. By default the RDI on
EBER is selected.
Interface type cannot be modified.

Define the trail trace settings.


Select the Trail Trace pane.

Figure 12

Modify IFUF interface, Trail Trace settings

Select the check boxes as necessary and enter the values for Send ID and Expected
ID. 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 alarm 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 ID
is not selected, an empty string will be expected.

44

Id:0900d805807f9e18
Confidential

DN02166645
Issue 23A

Commissioning AXC

Send the changes to the node.


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.

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.

DN02166645
Issue 23A

Id:0900d805807f9e18
Confidential

45

Commissioning AXC

Figure 14

Modify VC-12 frame, General settings

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


Selecting ATM interface enables you to configure ATM settings for the interface.
You can also take the interface into use by clicking the right mouse button on the frame
in 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

Select the check boxes as necessary and enter the values for Send ID and Expected
ID. 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 alarm 61120 will be raised.
If the Send ID check box is not selected, an empty string will be sent. If the Expected ID
is 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 the
changes 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.

46

Id:0900d805807f9e18
Confidential

DN02166645
Issue 23A

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 protection cannot carry additional ATM user traffic.
Select the following if necessary:

Revertive. If this is selected, the protection switches back to the working interface
when the working interface is repaired after a failure. In non-revertive mode, the
traffic 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 in
MSP1+1 mode.
The AXC supports MSP1:1. MSP1:1 with MSP1+1 compatibility is interoperable with
MSP1+1 implemented in the RNC. The AXC also operates with third-party equipment supporting MSP1:1 or MSP1+1 compatible with MSP1:n as described in
G.783, Annex A.

If you want to change the Protected or Protecting unit or interface, first select the interface and click Delete Protection. Then click Add Protection... to define the interfaces
again.
A switchover can be performed by clicking Switch Over and cleared by clicking Clear
Switch Over. The actions depend on the states of the protected and protecting interfaces as follows:

DN02166645
Issue 23A

Interface state

Switch Over

Protected IF active, no
alarms in protecting IF

Switches the traffic to pro- Disabled


tecting IF

Id:0900d805807f9e18
Confidential

Clear Switch Over

47

Commissioning AXC

Interface state

Switch Over

Clear Switch Over

Protecting IF active, no
alarms in protected IF

Disabled

In revertive mode, switches


the traffic to protected IF (in
case a manual switch has
been performed). In nonrevertive mode, traffic will
stay in protecting IF until
alarms are raised on it.

Protecting IF active,
alarms in protected IF

Disabled

In revertive mode, switches


the traffic to protected IF
when all alarms are cleared
(in case a manual switch has
been performed). In nonrevertive mode, traffic will
stay in protecting IF until
alarms are raised on it.

Protected IF active, alarms


in protecting IF

Disabled

Traffic will stay in protected


IF even if alarms are cleared
in protecting IF.

Note that these MSP requests do not necessarily lead to a switchover. A state machine
evaluates all local and remote requests and decides by means of a priority table if a switchover 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 switchover request), a switch back to the protected interface could be accomplished by temporarily putting the group into revertive mode.
Click Protection Statistics to get information on the number and duration of switches
that have happened between the protected and protecting interfaces.
Further information
For instructions on how to create loops, see Configuring loopbacks.

48

Id:0900d805807f9e18
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.4.4

Configuring IFUH interfaces


Steps

Select the interface in the Hardware view.


Select the interface of the IFUH unit in the Interface pane of the Hardware view. Click
Modify. 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.

Configure the transport addresses.


The transport address settings are needed for ATM over Ethernet, IP Iub and Timing
over Packet.
Click IP Settings and select the Transport addresses tab.

DN02166645
Issue 23A

Id:0900d805807f9e19
Confidential

49

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 Ethernet
overhead or exclude it.

50

Id:0900d805807f9e19
Confidential

DN02166645
Issue 23A

Commissioning AXC

c) Take Virtual LAN (VLAN) in use if necessary by checking the VLAN box and entering
the identifier of the VLAN to which the interface belongs. Possible values range from
0 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 the
changes but keep the window open.

DN02166645
Issue 23A

Id:0900d805807f9e19
Confidential

51

Commissioning AXC

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 in the Hardware view.


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

52

Configuring AXCF interface settings

Id:0900d805807f9e1a
Confidential

DN02166645
Issue 23A

Commissioning AXC

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.

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.

Figure 22

Transport Addresses tab

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

DN02166645
Issue 23A

Id:0900d805807f9e1a
Confidential

53

Commissioning AXC

Figure 23
1.
2.
3.
4.
5.

6.
7.
8.
9.
10.

11.

54

Modifying Transport Ethernet Interface settings

Select the active interface.


Check the IP Enabled field.
Enter the local IP address and netmask.
You can select whether you want the traffic shaper to either include the Ethernet
overhead or exclude it.
Traffic path shaping level: Choose the Traffic path shaping level from the drop
down list. Default is WFQ aggregator. Other options are VLAN interface and
Shaping off.
Shaper IR total: Enter the shaper information rate. Default is 1000 Mbps. Range is
from 0.1 to 1000 Mbps, in step of 0.1 Mbps.
Shaper burst size total: Enter the shaper burst size value. Default is 1522. Range
is from 1522 to 2000000, in step of 1 octet.
Shaper IR: Enter the shaper information rate. Default value is 1000 Mbps. Range is
from 0 to 1000 Mbps, in step of 1 Mbps.
Shaper burst size : Enter the shaper burst size value. Default value is 1522. Range
is from 1522 to 2000000, in step of 1 octet.
Committed IR: The CIR parameter allows to specify bandwidth that is guaranteed
for higher priority PHBs. Default value is 1000 Mbps. Range is from 0.1 to 1000
Mbps, in step of 0.1 Mbps.
QoS: can be enabled if the quality of service has to be taken into use at Ethernet
interface level.

Id:0900d805807f9e1a
Confidential

DN02166645
Issue 23A

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.

DN02166645
Issue 23A

Id:0900d805807f9e1a
Confidential

55

Commissioning AXC

5.4.6

Configuring ATM over Ethernet


Purpose
This procedure tells you how to configure the ATM over Ethernet settings for IFUH. The
IFUH interface unit provides a mechanism to carry ATM Iub traffic between the BTS and
RNC using Ethernet as the physical transmission layer. The traffic is carried within a
Packet-switched Network (PSN) tunnel that contains up to six Pseudowires.
IP encapsulation is supported on the tunnel level and the Pseudowire level uses MPLS
encapsulation. 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 IFUH
interfaces.
Steps

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 Licensed
Features 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:

56

Id:0900d805807f9e29
Confidential

DN02166645
Issue 23A

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 control
word. If a broken Pseudowire connection is detected, the alarm 61601 or 61602 is
raised.
If you want to enable BFD, select Control word in use and define the transmit and
receive interval values. Since BFD messages are conveyed within the Pseudowire, both
ends of the connection must support BFD.
Desired minimum transmit interval determines the minimum rate in which BFD control
packets are sent to the remote system and required minimum receive interval the
minimum rate in which BFD control packets are expected to be received from the remote
system. 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 is
Detection 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: [210]; 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.

DN02166645
Issue 23A

Id:0900d805807f9e29
Confidential

57

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 dialog
opens:

Figure 27

Creating a new Pseudowire

Enter the following information for the Pseudowire:

MPLS header label TX and RX: identifiers for the Pseudowire in the Tx and Rx directions
The identifiers must be unique within the PSN tunnel.
Max cells per frame: specifies the maximum number of ATM cells to be concatenated 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 concatenation 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 detection admin up to activate the bidirectional forwarding detection. Bidirectional forwarding 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 six
Pseudowires.

58

Id:0900d805807f9e29
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 the
mapping of Per Hop Behavior to Virtual LAN priorities and define the values for Differentiated Services Code Point (DSCP). The Priority Mappings are used for prioritizing the
traffic in VLAN routers and Ethernet switches.
You can select the Per Hop Behavior for each Pseudowire separately. The value range
for VLAN is from 0 to 7 and for DSCP from 0 to 63. Clicking the Default button restores
the default values.

DN02166645
Issue 23A

Id:0900d805807f9e29
Confidential

59

Commissioning AXC

Figure 29

60

Modify Traffic Types

Id:0900d805807f9e29
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.4.7

Configuring IMA settings


Purpose
Inverse multiplexing for ATM (IMA) is a technique by which ATM traffic can be distributed over several lower bandwidth PDH/VC-12 links, and then recombined again at the
far 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

Click Configuration IMA...


The Inverse Multiplexing for ATM (IMA) window opens.

Figure 30
2

Inverse Multiplexing for ATM (IMA) window

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

DN02166645
Issue 23A

Id:0900d80580817702
Confidential

61

Commissioning AXC

Figure 31

Create new IMA group

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

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 using
the arrow buttons. The links are to be added to the list of Selected links. The links have
to be located on the same IFU. The Group capacity shows the total capacity of the IMA
group 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

Define the settings for the IMA group.


Define the following settings for the IMA group:

62

Id:0900d80580817702
Confidential

DN02166645
Issue 23A

Commissioning AXC

Version ID: version of the IMA standard to be applied: 10 (ATM Forum af-phy0086.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 IMA
messages and 127 cells for ATM payload. The Tx Frame length must be the same
on both local and remote site.
Note that the Tx frame length cannot be modified for an existing IMA group. If you
want to modify it, you have to create a new IMA group. Delete the old group before
creating a new IMA group.
Min. link count: the minimum number of IMA links required to keep the IMA group
active. Possible values range from 1 to the number of configured IMA links. The
default value is 1.
Max. diff. delay: the maximum allowed differential delay in the physical link. Possible
values 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 already
assigned IDs in the slot. The range of IDs is from 33 to 99 per slot, so that 33 is assigned
to the first group and incremented by 1 for the next group.
6

Send the changes to the node.


Click OK to close the New IMA Group window. Click New Group... if you want to create
another IMA group.
Click OK to send the changes to the node and close the IMA window, or Apply to send
the changes but keep the window open.
Further information
You can view the properties of IMA groups and IMA links by selecting the group or links
from the tree view on the left. If the unit of the selected IMA group belongs to an interface
protection group, the information in each pane is displayed for both the protected and
protecting interface.
When modifying an IMA group that is contained by a protected interface, the changes
you make to the protected interface are automatically applied also to the protecting interface. You cannot modify the settings of the protecting interface manually.
The configured and current Tx frame lengths and IMA version IDs might sometimes be
different. This happens, for example, if the IMA versions have not been configured to be
the same at both ends of the physical link.
If an IMA group does not function correctly, you can try restarting it by clicking Restart
Group. This has no effect on the traffic in other interfaces.

DN02166645
Issue 23A

Id:0900d80580817702
Confidential

63

Commissioning AXC

5.4.8

Configuring fractional interfaces


Purpose
PDH interfaces can be configured as fractional interfaces. ATM over fractional
E1/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 over
the fractional interfaces with existing 2G traffic without disturbance. For more information, refer to ATM over fractional E1/JT1/T1.
Note that fractional interfaces are not supported by AXC Compact (AXCC and AXCD).
Steps

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. Click
Licensed Features in the Fractional interfaces window to download a license.
2

Click Add... in the Fractional Interfaces window.

Figure 33

64

Create fractional interface

Id:0900d805807f9e2b
Confidential

DN02166645
Issue 23A

Commissioning AXC

Select the unit and interface on which you want to create a fractional interface.
Only interfaces that are not already configured as fractional are shown in the list.
Selecting ATM interface enables you to configure ATM settings for the interface.

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. The
fragment always starts from timeslot 1 and is continuous. The minimum number of
timeslots 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 use
of timeslot 16 is optional for optimising bandwidth utilisation.
Timeslot 16 can be used for Channel Associated Signalling (CAS) in Time-division
Multiplexing (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.

Send the changes to the node.


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

DN02166645
Issue 23A

Id:0900d805807f9e2b
Confidential

65

Commissioning AXC

5.4.9

Configuring Q1 EOCs
Purpose
Q1 Embedded Operation Channels (EOC) can be configured on the E1 interfaces on
IFUA and IFUD and on the E1 within Flexbus interfaces on IFUE. Via the Q1 Embedded
Operation Channels within E1 frames, the AXC Q1 Support Function can poll far-end
Q1 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 configured
with the AXC-FB Hopper Manager. For more information, see Commissioning FlexiHopper (Plus) and MetroHopper with IFUE.
Steps

Click Configuration Q1 EOCs...


The Q1 EOCs dialog opens.

Figure 34
2

Q1 EOCs dialog

Click Add... in the Q1 EOCs dialog.


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

Figure 35
3

Adding a Q1 EOC

Define the unit and interface of the Q1 EOC.


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

66

Id:0900d80580817707
Confidential

DN02166645
Issue 23A

Commissioning AXC

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

Send the changes to the node.


Click OK to send the changes to the node and close the Q1 EOCs dialog, or Apply to
send the changes but keep the dialog open.
Further information
Configuring AXC Q1 support function.

DN02166645
Issue 23A

Id:0900d80580817707
Confidential

67

Commissioning AXC

5.4.10

Configuring CES Interworking function


Purpose
Circuit Emulation Service (CES) for structured or unstructured E1/JT1/T1 allows you
to 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 recommended 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 Product
Description.
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 is
equivalent to one logical ATM interface.
Up to 8 x structured/unstructured CES is supported on IFUA/D and AXCC/D and up to
16 x unstructured CES on IFUE.
A mixed configuration of structured/unstructured CES is allowed on the same IFUA/D or
AXCC/D.
Steps

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 the
Circuit Emulation Service window to download a license.
2

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


The Add CES Interworking Function window opens.

68

Id:0900d80580817713
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 37
3

Add CES Interworking Function - unstructured

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.

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 following
formula:
number of timeslots
Minimum PCR = 8000 x

1
x

partial fill bytes

0.95

This allows for a 95 % load of the Virtual Channel. The following are examples of Peak
Cell 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

Select the Service Type.


Select the Service Type: Structured or Unstructured.
For Structured CES you also have to define the following settings:

DN02166645
Issue 23A

Timeslots 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 to
fill the 47 bytes of AAL1 payload by the segmentation and reassembly function.

Id:0900d80580817713
Confidential

69

Commissioning AXC

Partial fill represents the number of bytes that carry payload (filling bytes). The
smaller the value, the more dummy bytes need to be inserted.
Partial Fill value must be at least four times the number of timeslots selected for
structured CES. If the number of timeslots is 12 or more, Partial Fill value must be
47.

Figure 38

Add CES Interworking Function - structured

Click OK.
6

Send the changes to the node.


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

70

Id:0900d80580817713
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.4.11

Configuring CES pass-through


Purpose
The Circuit Emulation Service (CES) pass-through function of the AXC is an internal
CES function that allows you to perform a TDM cross-connection by setting up a circuit
emulation service simultaneously on two AXC interfaces with an associated ATM connection. 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 recommended 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 is
equivalent to one logical ATM interface.
Up to 8 x structured/unstructured CES are supported on IFUA/D and AXCC/D and up to
16 x unstructured CES on IFUE.
A mixed configuration of structured/unstructured CES is allowed on the same IFUA/D or
AXCC/D.
Steps

Click Configuration CES...


The Circuit Emulation Service (CES) window opens.

Figure 39

Circuit Emulation Service (CES) window

CES is application software that requires a valid licence. Click Licensed Features in the
Circuit 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.

DN02166645
Issue 23A

Id:0900d805807f9e2e
Confidential

71

Commissioning AXC

Figure 40
3

Adding a CES pass-through

Select Interface 1 and Interface 2.


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

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 to
fill the 47 bytes of AAL1 payload by the segmentation and reassembly function.
Partial fill represents the number of bytes that carry payload (filling bytes). The
smaller the value, the more dummy bytes need to be inserted.
Partial Fill value must be at least four times the number of timeslots selected for
structured CES. If the number of timeslots is 12 or more, Partial Fill value must be
47.

Click OK.
5

Send the changes to the node.


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

72

Id:0900d805807f9e2e
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 packets
through each AXC interface. By default NND is enabled.
Whenever an interface is taken into use, an ATM channel (VPI=0, VCI=21) is automatically created for NND. An alarm is generated if this channel is deleted or modified
without disabling NND.
For more information on Neighbour Node Discovery, see Neighbour Node Discovery
(NND) in AXC product description.
Steps

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 or
Disable.
Do not enable NND for interfaces towards the RNC.

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 the
information on the Remote System and Remote Interface becomes available in the AXC
Manager. After that time, you can click Refresh to make it appear in the NND window.

DN02166645
Issue 23A

Id:0900d805807f9e2f
Confidential

73

Commissioning AXC

5.4.13

Configuring Transport mode


Purpose
From C6.0 release, AXC starts supporting three transport modes: ATM, IP and Dual
modes. This procedure describes how to set the AXC node into desired Transport mode
using Element Manager. Note that transport mode change with the AXC Manager is
supported only in a local connection with AXC Manager.
The procedure below describes transport mode change with AXCF card in the backplane. By following similar procedure transport mode can be switched to ATM Iub or IP
Iub with IFUH card in the backplane.
Before you start
Make sure that you take a configuration backup of your system before switching the
transport mode to some other transport mode as this operation causes the node to come
up in factory default state after the reboot.
Steps

Select the desired transport mode.


Click Node Switch Transport Mode.
The following dialog opens.

Figure 42
2

Switch Transport Mode

Set the desired transport mode.


Select the desired transport mode ATM Iub, IP Iub, Dual Iub and Enable/Disable AXCF
as per requirement and click Switch to activate the desired mode. The node goes for
reboot and loses all the configurations after reboot.
Verification
Once AXC node comes up after reboot check the transport mode using AXC element
manager in the Hardware View window.
Note the following:

74

Id:0900d80580817717
Confidential

DN02166645
Issue 23A

Commissioning AXC

DN02166645
Issue 23A

While switching to Dual Iub mode from ATM Iub mode, Enable AXCF checkbox gets
enabled 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 automatically 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 grayed
out and the user can not switch to Dual Iub mode.
When AXC node is commissioned in ATM Iub and IP Iub transport mode with AXCF
in use and in Dual Iub transport mode, un-installation of the AXCF unit by element
manager is not possible as it carries Iub termination.
If the user wants to uninstall AXCF unit carrying Iub termination below options are
possible:
Change the transport mode to ATM Iub or IP Iub without AXCF in use and uninstall the card by element manager. Remove the AXCF unit from backplane.
Recover the AXC node and uninstall the card after recovery. Remove the AXCF
unit from backplane.
Commission the AXC node using XML file where Iub termination point is specified as different AXCF card location than the current AXCF card location
carrying Iub termination (card to be uninstalled from node).
When AXC node is commissioned in IP Iub transport mode with IFUH, un-installation 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 are
possible:
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 specified as different IFUH card location than the current IFUH card location carrying
Iub termination (card to be uninstalled from node).

Id:0900d80580817717
Confidential

75

Commissioning AXC

5.5

Configuring Timing over Packet


Purpose
Timing over Packet provides a way of synchronizing the BTS in Full Ethernet/IP networks. For more information, see Synchronization of AXC.
Timing over Packet is application software that requires a valid licence. For more information, see Managing licences.
Before you start
Make sure that the TOPA module has been installed to the IFUH interface unit as
instructed 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 AXCF
hardware.
Steps

Configure the IFUH/AXCF interface.


See Configuring IFUH interfaces or Configuring AXCF interfaces for detailed instructions.

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 dialog
opens:

Figure 44

76

Modify Timing over Packet

Id:0900d805807f9e32
Confidential

DN02166645
Issue 23A

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.

DN02166645
Issue 23A

Id:0900d805807f9e32
Confidential

77

Commissioning AXC

5.6

Configuring synchronization
Purpose
To ensure the synchronization of the AXC, you have to configure the recovered timing
source and the timing protection source.
The Radio Network Controller (RNC) provides the primary reference clock source for all
other RAN network elements and as the AXC connects the base station to the RNC it
also acts as a synchronization interface between the two elements. This is the preferred
option 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 automatically
switches to the secondary source and a warning is to be generated. If no secondary
source is configured or the secondary source fails as well, an alarm is raised. When the
primary 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 up
to 24 hours, and after 24 hours to the internal clock (free-run mode). The hold-over mode
is 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 protecting
interface must also be defined as a source. Otherwise, the synchronization cannot be
switched to the protecting interface if the protected interface fails.
Synchronous Ethernet is application software that requires a valid license. For more
information, see Managing licenses in Operating and Maintaining AXC.
Steps

Click Configuration Synchronization...


The Synchronization window opens.

Figure 45

78

Synchronization window

Id:0900d805807f9e3d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Click Add... in the Synchronization window.


The Add Synchronization Timing Source window opens.

Define the new synchronization timing source.


You can select either Transmission interface, Timing Over Packet , AXU synchronization 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 Synchronous
source.
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. The
selection of the unit updates the Interface drop down menu.

Interface

The Interface drop down menu depends on the unit ( E1/JT1/T1, STM1/STS-3c, E1, Flexbus E1, STM-1 VC-12, E1/JT1/T1, E1, AXCF Ethernet).
To select the timing source as Synchronous Ethernet select the Transmission Interface, select the Unit as AXCF (as synchronous Ethernet
is only supported in AXCF) and select the Interface as Ethernet interface.

g If the In use option of the interface is not selected, the interface


cannot 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.

DN02166645
Issue 23A

Id:0900d805807f9e3d
Confidential

79

Commissioning AXC

SSM timeout

AXCF interfaces allow for the ssmTimeout and ssmMonitoring values to


be set. The SSM timeout field allows the user to set the timeout value
for the SSM messages in seconds within a range of 2 to 10 seconds.
Default value is 5 seconds. This item is enabled only once if AXCF interface is selected.

SSM monitoring

The SSM monitoring check box allows the user to enable or disable
SSM monitoring on the selected interface. This item is enabled only if
AXCF interface is selected.

SSM value

The SSM value shows the current SSM value obtained from the
concrete timing source. This item is enabled only once, if AXCF interface is selected.

An IMA link which belongs to IMA group can also be selected as a synchronization
timing source.
For the Timing over packet, select the IFUH/AXCF unit.
For the AXU synchronization input (external timing source), define the frequency of
the external source clock:

5 MHz
2 MHz
2 Mbit/s (AXUA/B only)

In AXC Compact, the frequency that is available depends on the type of interface
(E1/T1/JT1). If a 2 Mbit/s synchronization input is needed with AXC Compact, it is
possible to use a spare E1 interface for that purpose.
AXCF supports GPS clock. GPS clock systems provide reliable and secure timing to
networks and critical devices for command centers and secure data networks. The
external GPS device converts the GPS signal into a 1 pps signal. This 1 pps signal is
then transferred to the AXCF's GPS port. AXCF puts a generated 8 KHz signal on the
Backplane towards the AXU. AXU provides a 2.048 MHz clock to the WSC, where the
BTS OXCO is running with 10 MHz. GPS clock is added by default as priority 1 synchronization timing source.
With pure Ethernet Backhaul, a TDM interface connected to the AXU synchronization
input (or IFUA/IFUD interface unit, if present) from, for example, a co-located GSM BTS
or microwave radio indoor unit must be used as a synchronization source.
Click OK to close the Add synchronization timing source window.
The AXC Manager shows the active synchronization source next to Active Source in
Node. Click Refresh to update the Status and Active Source in Node.

80

Id:0900d805807f9e3d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 47
4

Synchronization overview

Change the priority of synchronization timing sources if necessary.


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

Send the changes to the node.


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

DN02166645
Issue 23A

Id:0900d805807f9e3d
Confidential

81

Commissioning AXC

5.7
5.7.1

Configuring ATM settings


Creating traffic descriptors
Purpose
Traffic descriptors define the traffic and Quality of Service (QoS) parameters for one or
more Virtual Path and Virtual Channel connections. You can create traffic descriptors
either to the network element or to an application file.
Steps

Click Configuration ATM Settings...


Select the Traffic Descriptor pane in the ATM Settings window.

Figure 48
2

Traffic Descriptors

Enable UBR+ if necessary.


Click Use UBR+ Service Category.
UBR+ is application software that requires a valid licence. Click Licensed Features to
download a licence.
ATM interface oversubscription should not be used together with the UBR+ service category.

Enable VCC bundle mode if necessary.


Click Use VCC Bundling.

82

Id:0900d805807f9e40
Confidential

DN02166645
Issue 23A

Commissioning AXC

Click New...
The New Traffic Descriptor window opens.

Figure 49
5

Creating a new traffic descriptor

Define the settings for the traffic descriptor.


Define the following settings:

DN02166645
Issue 23A

Name: name for the Traffic Descriptor (max. 20 characters).


Use settings from: select an existing Traffic Descriptor from the list if you want to use
its settings as a basis.
Service category: CBR or UBR/UBR+
Conformance definition: the only available value for CBR is CBR.1. The available
values for UBR and UBR+ are UBR.1 and UBR.2. If policing is enabled, UBR.1
discards and UBR.2 tags cells that do not conform to the traffic contract.
Peak Cell Rate (cells/s)
Note that High Speed Downlink Packet Access requires a CBR Traffic Descriptor
with a Peak Cell Rate of up to 40000 cells/s.
Cell delay variation tolerance (CDVT) defines the acceptable variation of ingress
traffic over the PCR. Default value for CBR is 5000 s and for UBR 20 000 s.
Minimum desired cell rate: defines the guaranteed minimum cell rate in all traffic
conditions (defined for UBR+ traffic descriptors).
UBR share: defines the amount of bandwidth that a UBR+ connection with this traffic
descriptor receives above its Minimum Desired Cell Rate, in proportion to the UBR
Share values of other UBR+ connections.
Note that if the sum of CBR Peak Cell Rate and UBR+ Minimum Desired Cell Rate
on a certain ATM interface is equal to the bandwidth of the interface, UBR Share
value has no impact on traffic scheduling.

Id:0900d805807f9e40
Confidential

83

Commissioning AXC

Create to Equipment or File: if you create the traffic descriptor to a file, you can use
it as a predefined template.

Send the changes to the node.


Click OK to close the New Traffic Descriptor window. Click New... if you want to create
another traffic descriptor.
In the ATM Settings window, click OK to send the changes to the node and close the
window, or Apply to send the changes but keep the window open.
Further information
Note that only traffic descriptors that are not in use can be modified or deleted.

84

Id:0900d805807f9e40
Confidential

DN02166645
Issue 23A

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 Profiles
that 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 configuration
constraints.
Unlock at least one physical/logical interface to make Access Profiles visible in the AXC
Manager.
Note that changing any Access Profile causes a short traffic break on all cross-connections.
Steps

Click Configuration ATM Settings...


Select the Access Profile pane in the ATM Settings window.

Figure 50
2

Access Profiles

Select the desired interface and click Modify...


The Modify Access Profile window opens.

DN02166645
Issue 23A

Id:0900d805807f9e3f
Confidential

85

Commissioning AXC

Figure 51
3

Modifying an Access Profile

Modify the settings of the Access Profile if necessary.


The bandwidth of an Access Profile may be modified as long as the new bandwidth is
sufficient to meet all existing traffic contracts. 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.

86

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 Traffic
Descriptor. UBR.1 discards and UBR.2 tags cells that do not conform to the traffic
contract.

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.

Id:0900d805807f9e3f
Confidential

DN02166645
Issue 23A

Commissioning AXC

Configured capacity: set automatically by the AXC Manager depending on the interface type.
You can decrease the bandwidth to provide aggregate shaping.
The bandwidth of an Access Profile may be modified as long as the new bandwidth
is sufficient to meet all existing traffic contracts.
If ATM interface oversubscription is in use, you can also increase the bandwidth to
be larger than the physical bandwidth. For more information, see ATM interface
oversubscription 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+ service
category.
Because of a quantization function used for determining the Access Profile bandwidth, the actual value is lower than the value that you can see in the AXC Manager,
as shown in the table below:
Bandwidth in AXC
Manager (cells/s)

Actual bandwidth
(cells/s)

9000

9000

10000

9999

14000

13998

17000

16997

20000

19996

50000

49974

Send the changes to node.


Click OK to close the Modify Access Profile window. Click Modify... if you want to modify
another Access Profile.
In the ATM Settings window click OK to send the changes to the node and close the
window, or Apply to send the changes but keep the window open.

DN02166645
Issue 23A

Id:0900d805807f9e3f
Confidential

87

Commissioning AXC

5.8

Configuring ATM interfaces


Purpose
You have to configure Virtual Channels (VCs) to be able to create ATM Adaptation
Layer 2 (AAL2) connections and Data Communications Network (DCN) connections.
For more information, see Configuring Iub terminations and Creating DCN connection
for ATM interface.
Before you start
Make sure that ATM interface in the general settings dialog of the interface is enabled.
Steps

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 popup menu.

Figure 52

New VP

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

88

Id:0900d805807f9e41
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 53

Creating a new Virtual Path and Virtual Channel

Define the following settings for the VP:

DN02166645
Issue 23A

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 will
be 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 the
VP 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 required
if ATM Manager is in use.
Generate utilization zone performance data: select if you want to enable counters
that measure the number of seconds for which the used bandwidth of the interface
is less than a certain ratio of its maximum bandwidth

Id:0900d805807f9e41
Confidential

89

Commissioning AXC

Enable utilization threshold fault: if you have enabled utilization zone performance
counters, 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 which
the fault is generated.

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 and
Partial 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 traffic
loss.
3

Send the changes to node.


Click OK to send the changes to the node and close the New VP window, or Apply to
send the changes but keep the window open.
Further information
Note that you can only modify the properties of Virtual Channels that are not terminated
or cross-connected.

90

Id:0900d805807f9e41
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.9

Configuring Iub terminations without AXCF


Purpose
This prodecure tells you how to configure the Iub interface between the RNC and the
BTS.
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 valid
licence to take BTS AAL2 Multiplexing into use. For more information, see Managing
licences in Operating and Maintaining AXC.
If BTS AAL2 multiplexing is in use, the combined number of DCN interfaces (including
the six default DCN interfaces to the WAMs), AAL2 signalling termination points and
ATM interfaces must be 34 or less.
Steps

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 Dedicated
NBAP 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 Multiplexing is in use, you should create one signalling link and up to seven user paths.

Open the Iub Terminations to BTS tab.


Click Iub Terminations to BTS in the ATM View.

Figure 54

DN02166645
Issue 23A

Iub Terminations to BTS

Id:0900d805807f9e42
Confidential

91

Commissioning AXC

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 define
the WAM.

Figure 55

Creating a new Common NBAP

Figure 56

Creating a new Dedicated NBAP

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


Enabling or disabling BTS AAL2 Multiplexing always deletes any existing AAL2 signalling links and user paths.

92

Id:0900d805807f9e42
Confidential

DN02166645
Issue 23A

Commissioning AXC

Configure AAL2 signalling links.


Click New AAL2 Signalling.
If BTS AAL2 Multiplexing is not in use, a signalling link for each WAM must be configured. Select a Virtual Channel from the tree and the WAM for which you want to create
the link. Enter also the AAL2 End Address.
If you select Autocalculation Method to be other than Manual, the AXC Manager will
suggest 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. Click
BTS Settings in the IUB Terminations to BTS tab to define the BTS IP settings. For
instructions, 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 Virtual
Channel from the tree and the WAMs that are in use.
Enter also the AAL2 End Address for each WAM. If you select Autocalculation Method
to 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 also
enable Performance Monitoring if necessary.

DN02166645
Issue 23A

Id:0900d805807f9e42
Confidential

93

Commissioning AXC

Figure 58
6

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

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 each
WAM. 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 user
path for each WAM.
If you select Autocalculation Method to be other than Manual, the AXC Manager will
suggest 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 paths towards
the BTS.

94

Id:0900d805807f9e42
Confidential

DN02166645
Issue 23A

Commissioning AXC

Select a Virtual Channel from the tree and enter the Path Identifier. If you select Autocalculation Method to be other than Manual, the AXC Manager will suggest a value for
the 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 user
path 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
7

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

Activate the 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 IP
settings.
Further information
AAL2 signalling (STC alarm, Performance Monitoring and used WAMs with A2EA) and
user paths (Performance monitoring) can be modified only when BTS AAL2 Multiplexing
is 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.

DN02166645
Issue 23A

Id:0900d805807f9e42
Confidential

95

Commissioning AXC

5.10

Configuring Iub terminations in ATM and Dual mode with


AXCF
Purpose
This procedure tells you how to configure the ATM Iub interface between the RNC and
the AXC when AXCF is enabled on AXC node.
Iub terminations cannot be configured in a stand-alone AXC.
Before you start
In case of Dual Iub /ATM Iub with AXCF, BTS AAL2 multiplexing is no more a licensed
feature since this is the only mode supported. BTS AAL2 multiplexing in the two modes
can also be supported with AXUA.
Steps

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 for Dedicated NBAP connections. From C6.0 release user is allowed to create only one Common NBAP and only
one Dedicated NBAP.
AAL2 multiplexing is always enabled by default in Dual mode. If BTS AAL2 Multiplexing
is in use, you should create one signaling link and up to eight user paths. Create VCs
for Signaling link and User Paths.

Open Configuration Iub Terminations to BTS.

Figure 61

96

Iub terminations to BTS

Id:0900d805807f9e43
Confidential

DN02166645
Issue 23A

Commissioning AXC

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.

DN02166645
Issue 23A

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

Id:0900d805807f9e43
Confidential

97

Commissioning AXC

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

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 indication. The alarm "STC Connection to signaling peer not established" is triggered at
fault condition only if this checkbox is checked.
Performance monitoring: Select Performance monitoring if you want to enable the
performance monitoring.

Configure AAL2 end addresses parameters:

Autocalculation method: Choose method for autocalculation from combo box. The
chosen method will be used when A2EA and PID values are being suggested. If
chosen 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. Click
BTS Settings in the Iub Terminations to BTS tab to define the BTS IP settings. For
instructions, 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 for
creation of Signaling link.

98

Id:0900d805807f9e43
Confidential

DN02166645
Issue 23A

Commissioning AXC

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

Figure 66
6

AAL2 signaling link in Iub Terminations to BTS window

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:

DN02166645
Issue 23A

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. PID
can be autocalculated.
Timer Cu: Enter the Timer Cu value in this field. The value can be 0 - 31 ms. The
default and recommended value is 2 ms. Timer Cu (composite unit timer) is the
maximum delay for an incomplete ATM cell to be transmitted in ATM adaptation
layer 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 each
queue. AXC Manager proposes default values for weight parameters when new
AAL2 User Path is created. Range for weight is 1..1000, and 1000 means highest
priority and 1 lowest priority. Following values are the defaults for weight parameters:
Q1: Strict queue, weight is not modifiable
Q2: 1000
Q3: 500
Q4: 1
Default: This button sets the default queue weight values in the Quality of Service
table.

Id:0900d805807f9e43
Confidential

99

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 Monitoring
checkbox and QoS parameters.
User can delete the User Path by selecting the desired User Path and clicking on
Delete.

Figure 68

100

AAL2 User Path in Iub Terminations to BTS window

Id:0900d805807f9e43
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 IP
settings.
Further information
AAL2 signaling (STC alarm, Performance Monitoring) and user paths (Performance
monitoring) can be modified only when BTS AAL2 Multiplexing is enabled. NBAP terminations 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 link
does not delete virtual channel or termination.

DN02166645
Issue 23A

Id:0900d805807f9e43
Confidential

101

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 Iub
mode. The transport mode is changed by downloading an XML configuration file with IP
Iub settings in the AXC and activating it or using element manager as described in Configuring Transport mode section. When the transport mode is IP Iub, the ATM configuration is not needed and ATM interfaces can be used only for synchronization. Only a
limited number of AXC Manager functions are therefore available. IP Iub is application
software 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 Element
Manager.
For instructions, see Commissioning AXC with XML configuration file or Configuring
Transport mode. If the XML configuration file does not contain the IP Iub settings, configure them as described in the following steps.

Configure the AXCF interfaces.


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

Configure IP Iub settings.


Click IP Settings and select the IP Iub tab.
Click Modify to open the following dialog.

102

Id:0900d80580817791
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 69

Defining IP Iub settings

Define the following settings:

Far End SCTP Address: is RNC ICSU IP address


Far End SCTP Subnet
Minimum SCTP port: SCTP port range used for NBAP traffic. Range is 49152 to
65529. Note that the BTS is reset if you modify the value of Minimum SCTP Port.
Minimum UDP port: UDP port range is used for sending user plane calls. 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: amount of the committed bit rate available on the IP interface. Possible values range from 0.4 to 100 Mbps in 0.1 Mbps steps.
Signaling bit rate: amount of the committed bit rate is to be reserved for the Control
Plane (NBAP). Possible values range from 50 to 1000 Kbps in 50 Kbps steps.
DCN bit rate: amount of the committed bit rate is to be reserved for Management
Plane (DCN). Possible values range from 50 to 1000 Kbps in 50 Kbps steps.
Click Apply to send the changes but keep the window open or Close to close the
dialog without sending changes to node.

Configure the Quality of Service settings


Click IP Settings and select the Quality of Service tab.

DN02166645
Issue 23A

Id:0900d80580817791
Confidential

103

Commissioning AXC

Figure 70
1

QoS tab

Modifying Queue Weights


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

104

Id:0900d80580817791
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 71

Modifying queue weights

Click OK to send the settings to the node and Close to close the dialog.
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 each
traffic type.

Figure 72

DN02166645
Issue 23A

Modifying traffic types

Id:0900d80580817791
Confidential

105

Commissioning AXC

The values for DSCP range from 0 to 63. You can enter several values for user plane
traffic 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 value
can 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 and
SG6.
DSCP value zero is reserved for Best Effort traffic.

106

Id:0900d80580817791
Confidential

DN02166645
Issue 23A

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 Iub
settings in the AXC and activating it. Note that the transport mode can also be changed
with the AXC Manager, but this is only supported in a local connection with AXC
Manager.
When the transport mode is IP Iub, the ATM configuration is not needed and ATM interfaces can be used only for synchronization. Only a limited number of AXC Manager
functions is therefore available. In IP Iub mode no ATM crossconnect functionality is
available.
Upgrade scenario to IP Iub must be started with the outmost AXC in the chain towards
RNC.
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 / 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

Note that in IP Iub mode the IFUH can only route IP packets to the first eight addresses
of a configured public LMP subnet, though it is possible to configure host address
ranges 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.

DN02166645
Issue 23A

Id:0900d805807f9e45
Confidential

107

Commissioning AXC

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 switching the transport mode causes a reboot where all existing configurations will be removed
and the traffic interrupted.
After the reboot is finished continue from step 3 onwards.

Configure the IFUH interfaces.


For instructions, see Configuring IFUH interfaces.

Configure IP Iub settings.


Click IP Settings and select the IP Iub tab.

Figure 73

IP settings - IP Iub

Click Modify... to open the following dialog:

108

Id:0900d805807f9e45
Confidential

DN02166645
Issue 23A

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 Mbps
steps.
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 the
changes but keep the window open. Click Activate BTS Settings in Iub IP tab to
activate the settings.
5

Configure the Quality of Service settings.


Click IP Settings and select the Quality of Service tab.

DN02166645
Issue 23A

Id:0900d805807f9e45
Confidential

109

Commissioning AXC

Figure 75
1

QoS tab

Modifying Queue Weights


Click Modify Queue Weights.
Select an appropriate value (0-10000) for each queue type.

Figure 76

Modifying queue weights

Click OK to send the settings to node and Close to close the dialog.
Click Default to restore the settings to default value.
2

Modifying Traffic Types


Click Modify Traffic Types.

110

Id:0900d805807f9e45
Confidential

DN02166645
Issue 23A

Commissioning AXC

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

Figure 77

Modifying traffic types

The values for DSCP range from 0 to 63. You can enter several values for user plane
traffic 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 value
can be used only once. The value 0 is always mapped to Best Effort.
Click OK to send the settings to node and Close to close the dialog.
Click Default to restore the settings to default value.
6

DN02166645
Issue 23A

Configure other settings, such as synchronization and Management Protocol.

Id:0900d805807f9e45
Confidential

111

Commissioning AXC

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 Iub
mode. The transport mode is changed by downloading an XML configuration file with
Dual Iub settings in the AXC and activating it or using element manager as described in
section Configuring Transport mode.
When the transport mode is Dual Iub, BTS has two Iub links towards RNC: one ATM Iub
link 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 to
activate 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 Element
Manager.
For instructions, see Commissioning AXC with XML configuration file or Configuring
Transport mode. If the XML configuration file does not contain the IP/ATM Iub settings,
configure them as described in the following steps.

Configure the AXCF interfaces.


For instructions, see Configuring AXCF interfaces.

Configure IP Iub settings.


Click IP Settings and select the IP Iub tab.
Click Modify to open the following dialog.

112

Id:0900d805808178fe
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 78

Modify Iub IP

Define the following settings:

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 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 Mbps
steps. This is used for control plane call establishment.
External NAT IP address: This is external BTS IP address provided to the RNC as
User Plane BTS IP address during NBAP signaling.

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

Configure the Quality of Service settings


Click IP Settings and select the Quality of Service tab.

DN02166645
Issue 23A

Id:0900d805808178fe
Confidential

113

Commissioning AXC

Figure 79
1

QoS tab

Modifying Queue Weights


Click Modify Queue Weights.
Select an appropriate value (0-10000) for each queue type.

Figure 80

114

Modifying queue weights

Id:0900d805808178fe
Confidential

DN02166645
Issue 23A

Commissioning AXC

Click OK to send the settings to node and Close to close the dialog.
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 each
traffic type.

Figure 81

Modifying traffic types

The values for DSCP range from 0 to 63. You can enter several values for user plane
traffic 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 value
can 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.

Configure other settings, such as synchronization and Management Protocol.


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.

DN02166645
Issue 23A

Id:0900d805808178fe
Confidential

115

Commissioning AXC

DSCP value zero is reserved for Best Effort traffic.

116

Id:0900d805808178fe
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.14
5.14.1

Creating ATM cross-connections


Creating Virtual Path cross-connections
Purpose
This procedure describes how to create Virtual Path cross-connections. The AXC
supports semi-permanent Virtual Path cross-connections.
Before you start
Before creating any cross-connections, read through AXC interface configuration constraints.
Steps

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 left
of the ATM view.

Click New in the bottom view.


The New Cross-connection window opens.

Figure 82
3

Creating a new Virtual Path cross-connection

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 from
the list. Click New VP. A new Virtual Path is created on the interface.

DN02166645
Issue 23A

Id:0900d805807f9e53
Confidential

117

Commissioning AXC

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 Traffic
Descriptors.
Select the Supported service categories. The check boxes are enabled if the selected
VP has at least one VC and the selected Traffic Descriptor is CBR.

Enable performance monitoring if necessary.


Select Performance Monitoring.

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


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

Send the changes to the node.


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 descriptor
whose service category (CBR or UBR) is different.
If you change the Traffic Descriptor, traffic will be cut off for about 100 ms in case the
bandwidth is higher than 5000 cells/s.

118

Id:0900d805807f9e53
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.14.2

Creating Virtual Channel cross-connections


Purpose
This procedure describes how to create Virtual Channel cross-connections. The AXC
supports semi-permanent Virtual Channel cross-connections.
Before you start
Before creating any cross-connections, read through AXC interface configuration constraints.
Steps

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 left
of the ATM view.

Click New in the bottom view.


The New Cross-connection window opens.

Figure 83
3

Creating a new Virtual Channel cross-connection

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 from
the list. Click New VP to create a new Virtual Path and New VC to create a new Virtual
Channel on the VP. A new Virtual Channel is created on the interface.

DN02166645
Issue 23A

Id:0900d805807f9e52
Confidential

119

Commissioning AXC

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 Traffic
Descriptors.

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.

Enable performance monitoring if necessary.


Select Performance Monitoring.

Enable Egress Frame Discard if necessary.


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

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 traffic loss.
8

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


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

Send the changes to the node.


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 descriptor
whose service category (CBR or UBR) is different.
If you change the Traffic Descriptor, traffic will be cut off for about 100 ms in case the
bandwidth is higher than 5000 cells/s.

120

Id:0900d805807f9e52
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.15
5.15.1

Creating IP configuration
Setting public IP address
Purpose
Before doing any IP-level configurations, you have to configure the public IP address of
the AXC. Public IP address and DCN configuration are required for master WAM
changes to be successful in the BTS.
Steps

Click IP Settings...
The IP Settings window opens.

Figure 84
2

IP Interfaces window

Define the public IP address.


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

DN02166645
Issue 23A

Id:0900d80580817928
Confidential

121

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)

Send the changes to the node.


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

Click Close to close the IP Settings window.


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

122

Id:0900d80580817928
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 network
elements must also be configured to use OSPF.
Steps

Click IP Settings...
The IP Settings window opens.

Figure 86
2

IP Settings window

Click Add OSPF Area...


The Add OSPF Area window opens.

DN02166645
Issue 23A

Id:0900d805808179ea
Confidential

123

Commissioning AXC

Figure 87
3

Add OSPF area

Enter the required information for the OSPF area.


Enter the Area ID in IP address format.
Select Stub Area if necessary. Stub areas are OSPF areas that have only one exit point
or those have multiple exit points but routing out of the area does not have to take the
shortest path. Only the default route is advertised to the routers within a stub area. The
backbone area (0.0.0.0) cannot be a stub area.
If the area is a stub area, define the cost. The cost can also be 0.
All routers within the same OSPF area must have the same Stub Area configuration
(either selected or not).

g AXC should only belong to one OSPF area as it cannot act as an Area Border
Router (ABR).
4

Click OK to send the changes to the node.

Use the same method to create more OSPF areas.

Click Close to close the IP settings window.


Further information
If you delete an OSPF area, all DCN interfaces in that area become non-OSPF interfaces. This might break DCN connectivity.
When you want to remove static routes and define OSPF areas to an already commissioned AXC because it is moved under another RNC, for example, you should do this
using XML configuration file. For more information, see Modifying AXC configuration
with XML configuration file.

124

Id:0900d805808179ea
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.15.3

Creating DCN connections for ATM interfaces


Purpose
The Data Communications Network (DCN) connections are IP over ATM connections
that 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 have
to create these VCs before configuring the DCN settings. For more information, see
Configuring ATM interface.
Note that the ATM configuration for DCN terminations is limited to 2 MBit/s. This means
that 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 be
created first. For more information, see Creating OSPF areas.
Steps

Click IP Settings...
The IP Settings window opens.

Figure 88
2

IP Settings window

Click Add DCN...


The Add DCN for ATM Interface window opens.

DN02166645
Issue 23A

Id:0900d805807f9e56
Confidential

125

Commissioning AXC

Figure 89
3

Adding a DCN for ATM interface

Select the VC.


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

Define the destination address.


Enter the Destination Address. It is the IP address of the remote node to which the DCN
interface is connected.
You can also select Inverse ATM ARP in which case the destination address will be
detected 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 supports
it.
5

Define the OSPF settings [optional].


If you select OSPF, define the area to which the DCN interface will be added. Define
also the OSPF cost of the interface.
If you want to modify the OSPF timing values, click Timing... The OSPF Timing window
opens.

126

Id:0900d805807f9e56
Confidential

DN02166645
Issue 23A

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 same
timing values set. This concerns especially the Hello Interval and Dead Interval
values.
6

Click OK.

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

Send the changes to the node.


Click OK. The AXC Manager creates the cross-connection from the VC to the internal
IP routing device automatically.
If you have selected Inverse ATM ARP, the destination address shows as 0.0.0.0. Click
View Refresh All in the AXC Manager main window to update it. This may take
some time depending on the remote node and the connection.
Click Close to close the IP Settings window, or Add DCN... to create another DCN connection.
Further information
If you want to delete an existing DCN connection, select the connection from the list and
click Remove. Before you delete a DCN connection you have to delete all routing table
entries that use the connection. For more information, see Creating IP routes.
To modify the LMP interface settings, select the Local Management Port (LMP) interface from the list and click Modify....

DN02166645
Issue 23A

Id:0900d805807f9e56
Confidential

127

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 the
IP addresses of the 192.168.255.0/24 subnet are used BTS internally. All other IP
addresses are referred to as public IP addresses.
If you select Advertise via OSPF, Netmask and Broadcast are propagated to the other
routers in the OSPF area.
Make the necessary modifications to the LMP interface settings and click OK.

128

Id:0900d805807f9e56
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.15.4

Creating IP routes with AXCF/IFUH


Purpose
The AXC has an integrated IP router which has to be configured. In order to allow the
Data Communications Network (DCN) and transport traffic to work the routing table
should be configured so that there is a route to each possible destination address specified.
In case of ATM Iub with IFUH/AXCF and Dual Iub with AXCF, in element manager two
routing tables are supported so that one contains routes for DCN traffic and second
contains routes for transport traffic.
In case of IP Iub with IFUH/AXCF, DCN and transport traffic are carried over IP network.
Before you start
Before creating the routes, configure the DCN interfaces according to the instructions in
Creating DCN connections for ATM interfaces.
In IP Iub no DCN connection has to be created similar to the approach in ATM Iub. Just
set the public IP address and configure the routing table for creating the DCN.
In Dual Iub mode the routing entries have to be configured in the following way. For O&M
traffic (DCN connections) select the Display DCN routing radio button and add the
routing information under static routes if necessary. For the IP transport interface select
the Display transport routing radio button and add the necessary routing information.
If OSPF is in use in ATM or Dual Iub mode, do not configure the IP routes. To avoid
system overload, the number of routes in AXC (either statically configured or dynamically learnt by OSPF) must not exceed 100. When OSPF is in use, there are two routes
per BTS (one for the O&M master WAM and one for the AXC). To overcome the resulting limitation to 50 BTSs, the use of stub areas is strongly recommended. The limit of 50
BTSs then applies to each of the stub areas. By using multiple stub areas per RNC, any
number of BTSs can be supported. In IP Iub mode routing entries have to be configured
by adding routing information in the Static route table.

g In IP Iub mode IFUH supports only 2 routes. One route is used for Timing over
Packet (ToP). The other route is used for all other data to RNC like Control Plane
(NBAP), User Plane, Management Plane (DCN), BFD, and ICMP traffic.
All data to RNC like Control Plane (NBAP), User Plane, Management Plane (DCN),
BFD, and ICMP traffic reaches its destination if the route configured for this traffic is
using a Default Gateway (Destination 0.0.0.0, Netmask 0.0.0.0). Therefore, the user
must configure the default route (default gateway) to RNC within the AXC.
For Timing over Packet (ToP) it depends whether the ToP Master uses the same
gateway as the data towards the RNC. Then the default route to RNC is sufficient.
In case another gateway is used for the connection to the ToP Master, the user must
specify a dedicated route for it. No route is needed if the ToP master is in the same
subnet like the IFUH.

DN02166645
Issue 23A

Id:0900d805807f9e57
Confidential

129

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 routing

The Routing pane is split into two parts. In the upper part you can see the Static Route
Table which shows manually created routes. In the lower part you can see the Forwarding Table which shows the routing information for all active routes, either manually configured or automatically detected by OSPF, for example.
2

Click Add.
The Add IP Route window opens.

Figure 93

130

Add IP Route

Id:0900d805807f9e57
Confidential

DN02166645
Issue 23A

Commissioning AXC

Define settings for the route.


Define the following settings:

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.

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

Add all required transport routes by repeating step 5.

Click OK

Click Close to close 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 the
Static Route Table.

DN02166645
Issue 23A

Id:0900d805807f9e57
Confidential

131

Commissioning AXC

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

132

Id:0900d805807f9e57
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.15.5

Checking IP connectivity
Purpose
This option enables user to execute ping command and check the connectivity on IP
path with far end.
Steps

Click Node IP Connectivity...and specify the IP address of the remote host and
click Start.

Figure 95

Checking IP connectivity

Connectivity status can be seen in the GUI.

DN02166645
Issue 23A

Id:0900d805807f9e58
Confidential

133

Commissioning AXC

5.15.6

Creating DHCP configurations


Purpose
This procedure describes how to create the DHCP (Dynamic Host Configuration Protocol) configurations to the AXC. The AXC acts as a DHCP server and can pass configuration information, such as IP addresses, to hosts.
The information can only be passed via the Local Management Port (LMP). The IFUG
interface unit can be used as a hub to connect up to seven external IP devices to the
LMP. 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 must
be configured. For instructions, see Setting public IP address and Creating DCN connections for ATM interfaces.
For instructions on creating IP routes in IP iub mode, see Activating and configuring IP
Iub and Configuring Timing over Packet..
Note that only two gateway addresses can be maintained by AXC in IP Iub mode. Also
note that in IP Iub mode the IFUH can only route IP packets to the first eight addresses
of a configured public LMP subnet despite a much larger configured actual subnet size.
Steps

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

Figure 96

134

IP Settings - DHCP Configurations window

Id:0900d805807f9e59
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 can
only 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 IP
addresses to the clients.
The relationship between the configuration types is hierarchical. When the AXC
receives a request for a lease (IP address) from a client, it tries to identify its client identifier first and then its MAC address and assign an IP address accordingly. If neither of
those 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 range
you 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 IP
address can be used.

DN02166645
Issue 23A

Click OK to send the changes to the node.

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

Click Close to close the IP Settings window.

Id:0900d805807f9e59
Confidential

135

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

Click IP Settings and select the BTS Settings pane.


Or click IP BTS Settings.

Figure 98
2

IP Settings - BTS Settings

Click Modify to define the settings.


The Modify BTS Settings dialog opens.

136

Id:0900d805807f9e5a
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 99

Configuring BTS IP settings

1. Enter the BTS Identifier. The BTS Identifier can be modified only if no AAL2 configuration 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 connection status is read only attribute and returns the connection status between SMA and
OMS and value is set by ASN.1 gateway. Possible values are:
Not connected
TLS Secured

DN02166645
Issue 23A

Id:0900d805807f9e5a
Confidential

137

Commissioning AXC

Unsecured
Once the secure O&M connection is established, it is advised to set TLS probing
mode to forced (probing mode should be used only initially). Otherwise, in certain
cases 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 of
migration.
2 Set TLSModeSending feature in the RNC to ON.
g TLSModeSending can found in Parameter Tool -> ClusterRoot/OMS/System/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 that
RNC.
4 Change TLSModeSending parameter back to OFF.
5 Change TLS mode in the RNC back to previous setting (for example - probing
to enable compatibility of BTSs with unsecured O&M session).
Note that the TLS mode setting in RNC can be different from TLS mode setting in
BTS. This means that usually TLS in BTS is set to forced, but TLS in RNC is set to
probing. That allows for using BTSs both with secure (TLS) and unsecured O&M
session, as well as enables initial unsecured O&M session, before the BTS gets a
certificate 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.
Present TLS
mode for
OMS interface

New TLS
Mode

Disconnect
from OMS
(Action to be
taken by SMA)

New TLS
Mode to be
stored in persistent 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

Yes

Forced

TLS Secured

Off

Yes

Yes

Table 2
3

Present OMS
connection
Status

TLS operating mode

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.

138

Id:0900d805807f9e5a
Confidential

DN02166645
Issue 23A

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 AXC
and BTS. All IP packets with a public IP address in the source or destination are discarded. The IP addresses of the 192.168.254.0/24 subnet are used AXC internally and
the IP addresses of the 192.168.255.0/24 subnet are used BTS internally. All other IP
addresses are referred to as public IP addresses.
However, you can define exception rules to the restricted mode so that any IP packet
that matches any rule in any rule set is not discarded.
In unrestricted mode, other network elements within the same network can also be
accessed by DCN connection.
Steps

Click IP Restricted Mode Filtering.

Figure 100 Restricted Mode Filtering


2

Create a new rule.


Click Add.

DN02166645
Issue 23A

Id:0900d805807f9e65
Confidential

139

Commissioning AXC

Figure 101 Adding a Restricted Mode rule


First select the rule set for which you are creating an exception. Enter a descriptive
name 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 IP
addresses and ports already defined elsewhere (such as for primary and secondary
LDAP 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 via
DCN over the LMP. In all other cases the restricted mode should be activated for
security 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 Filter
rules for user plane traffic tables.

140

Id:0900d805807f9e65
Confidential

DN02166645
Issue 23A

Commissioning AXC

Ingress Packets are to be filtered through with source IP address, destination IP


address, source port and destination port as given in following tables.
Protocol

Source IP
address

Source port

Destination IP
address

Destination port

NWI3
(Netact/EM)

AXU public IP

49200-49201

XoH
(WI/SEM)

AXU public IP

12000

FTP
(Netact/EM)

AXU public IP

20-21

HTTPS
(SEM)

AXU public IP

12000

ASN.1

OMS public IP

BTS public IP

8002-8003

NTP

EM Configuration

123

AXU public IP

123

LDAP

EM Configuration

AXU public IP

9109

CMP

EM Configuration

AXU public IP

8080

ICMP

N/A

AXU/BTS/Trans
port IP address

N/A

ARP

N/A

AXU/BTS/Trans
port IP address

N/A

Table 3

Filter rules for management plane traffic

*) can be any valid IP address or port number.


Protocol

Source IP
address

Source port

Destination IP
address

Destination port

BFD

EM Configuration

123

AXCF transport
IP

49200-49201

SCTP

RNC IP

minSCTPpo
rt

AXCF transport
IP

minSCTPport

ToP

EM Configuration

123

ToP Slave IP
(hardcoded)

319-320

Table 4

Protocol
User plane
Table 5

Filter rules for control plane traffic

Source IP
address
Dynamic

Source port
Dynamic

Destination IP
address
Dynamic

Destination port
49152-65535

Filter rules for user plane traffic

Limiting the ingress and egress traffic is achieved by limiting the number of packets for
all management, control, and user plane traffics. This packet limiting is done internally

DN02166645
Issue 23A

Id:0900d805807f9e65
Confidential

141

Commissioning AXC

in AXC module based on maximum expected traffic in real time for each known application (like Top, SCTP, BFD, ICMP, user plane traffic and so on). This cannot be configured externally by the user.

142

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 per
second.
The management plane traffic is limited to 2000 frames per second. Note that this
includes NTP, BFD and IKE traffic.
The control plane ingress packet rate is limited to 500 packets per second.

Id:0900d805807f9e65
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.15.9

Creating NTP servers


Purpose
Time setting in the AXC can be handled via Network Time Protocol (NTP) by connecting 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 recommended to handle time via NTP servers.
Steps

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 disabled.
Click Add... to add a Network Time Protocol server. Enter the IP Address of the NTP
server. 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 are
the same for two or more servers, the preferred server is used.

DN02166645
Issue 23A

Id:0900d805807f9e66
Confidential

143

Commissioning AXC

If you want to configure the system time manually, click Set... to open the Set
System 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.
4

Send the changes to the node.


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.

144

Id:0900d805807f9e66
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.15.10

Configuring BTS Firewall


Purpose
Firewall feature in BTS is implemented to prevent unauthorized users from accessing
and harming the remote networks connected to the BTS. In addition to this, it restricts
the traffic from unknown applications and IP addresses either from the remote or local
network. In this process all messages entering or leaving the AXC module IP interfaces
pass through the firewall, which examines each packet and blocks those that do not
match 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 is
either 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 the
traffic sent by remote network. To activate BTS firewall rules, the wild card rule set on
TRS 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 for
traffic filtering can be created using option New in the Restricted mode filtering window.
Steps

Configure IP Iub.
For instructions, see Configuring and activating IP Iub mode with AXCF.

Configure public IP address.


For instructions, see Setting public IP address.

Configure transport IP address.


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

Configure IP route parameter.


For instructions, see Creating IP routes with AXCF/IFUH.

Configure Restricted Mode Filtering.


For instructions, see Configuring Restricted Mode filtering.

DN02166645
Issue 23A

Id:0900d805807f9e67
Confidential

145

Commissioning AXC

5.16

Configuring Management Protocol for Secure/Unsecured


LDAP connection
Purpose
This 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 want
the AXC to be registered to and identified by NetAct network management system.
Steps

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 located
in. No Parent ID is defined for stand-alone AXC.

146

Id:0900d805807f9e69
Confidential

DN02166645
Issue 23A

Commissioning AXC

Choose the parent ID's beginning from the drop-down list: RNC or IADA. Then enter the
RNC ID/IADA ID and WBTS ID in the fields. The length of the RNC ID/IADA ID and
WBTS ID can be 10 characters.
The Base ID and Parent NE ID are formed according to the following scheme:
Base ID

NE-AXC-<id>
For example: NE-AXC-17
The value for the <id> is planned in advance and it must be
unique 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

The <id> part of Base ID and Parent ID can be up to 10 characters long. It can contain
letters 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 window
opens.

DN02166645
Issue 23A

Id:0900d805807f9e69
Confidential

147

Commissioning AXC

Figure 107 Add Registration Service


Define the following settings:

Name of the service


NWI3 Registration Service account parameters: Username and Password (these
are 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 secondary
LDAP server are optional. Also, if the TCP port number is omitted the default value
389 will be used.
LDAP Security mode: Only allow secure LDAP connections checkbox is by default
checked. This sets LDAP security mode to secure. When the checkbox is
unchecked LDAP security mode can be secure/unsecured.
Configuration of root and people root are optional, since AXC is able to detect them
automatically.
NWI3 Registration Service IOR: select the file that contains the IOR by clicking
From File...

The IOR file needs to be saved as text.


If you need to modify the Registration and Publication time values, click Intervals and
Periods...

148

Id:0900d805807f9e69
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 108 Intervals and Periods


Click 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 a
delay for the restart.
Close the window by clicking Close.
Verification
Click Refresh in the Management Protocol window and ensure that the state of the new
configuration is changed to Active, Next.

DN02166645
Issue 23A

Id:0900d805807f9e69
Confidential

149

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 Certificate Authority. All of these have to be stored in the local machine where the Site
Manager 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 NE
certificate)

Steps
1

Click Node Certificate Management


Certificate Management window opens. Select AXC Certificates tab.

Figure 110 Certificate Management window

150

Id:0900d805807f9e6a
Confidential

DN02166645
Issue 23A

Commissioning AXC

Browse to the location where CA certificates are stored.

Figure 111 Certificate Management window


3

Once CA certificate is selected Send button gets highlighted. Click on the Send
button to install the certificate on the AXC node.

Figure 112 Certificate Management window

DN02166645
Issue 23A

Id:0900d805807f9e6a
Confidential

151

Commissioning AXC

A CA certificate is installed in the AXC using the Element Manager and is then available
to any application, for example Secure LDAP or Secure NWI3 that requires it. Expired
or outdated CA certificates may be deleted by utilizing the Element Manager. Deleting
a CA certificate may affect Secure AXC management interface and other applications
which uses the CA certificate.
Verification
Once CA certificate is installed successfully on the AXC node CA certificate details like
Issued To, Issued By, Valid From, Valid To, Serial Number & Fingerprint values can be
observed in the Certificate Management window.

152

Id:0900d805807f9e6a
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.18

Installing CA Certificates manually for AXC Element


Manager
Purpose
This procedure describes how to install CA Certificate on AXC Element Manager
Before you start
The CA Certificate can be created from Certificate Authority and have to be stored in the
local machine where the AXC Element Manager is installed.
There are two ways to install CA certificate in AXC Element Manager.

Using Tools option in the AXC Element Manager front page.


By logging in to AXC.

Steps for installing CA certificate through Tools option in the AXC Element
Manager front page
1

Open the AXC Element Manager front page.

Select Tools option.


In the Available tools select Certificate Management and click Launch.

Figure 113 AXC Element Manager window

DN02166645
Issue 23A

Id:0900d80580817a88
Confidential

153

Commissioning AXC

Certificate management window opens.

Figure 114 Certificate Management window

154

Browse to the location where CA certificates are stored.

Id:0900d80580817a88
Confidential

DN02166645
Issue 23A

Commissioning AXC

Once the CA certificate is installed in the AXC Element Manager. The information
regarding the certificates can be seen as shown below.

Figure 115 Certificate Management window

Steps for installing CA certificate after logging into the AXC Element Manager
1

Click Node Certificate Management


Certificate Management window opens. Select AXC Manager Certificates tab and click
Add Certificate.

DN02166645
Issue 23A

Id:0900d80580817a88
Confidential

155

Commissioning AXC

Figure 116 Certificate Management window


2

156

Browse to the location where CA certificates are stored.

Id:0900d80580817a88
Confidential

DN02166645
Issue 23A

Commissioning AXC

Once the CA certificate is installed in the AXC Element Manager. The information
regarding the certificates can be seen as shown below.

Figure 117 Certificate Management window


Verification
Once CA certificate is installed successfully in the AXC Element Manager CA certificate
details like Issued To, Issued By, Valid From, Valid To, Serial Number & Fingerprint
values 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 any
application like secure NWI3 that requires it. Expired or outdated CA certificates might
be deleted by using the Element Manager. Deleting all CA certificate might affect Secure
AXC management interface and other applications which use the CA certificate.

DN02166645
Issue 23A

Id:0900d80580817a88
Confidential

157

Commissioning AXC

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 Certificate Authority. All of these have to be stored in the local machine where the Element
Manager 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 NE
certificate).

Steps
1

Click Node Certificate Management


Certificate Management window opens. Select AXC Certificates tab.

Figure 118 Certificate Management window


2

158

Browse to the location where AXC certificates are stored.

Id:0900d805807f9e6c
Confidential

DN02166645
Issue 23A

Commissioning AXC

Browse to the location where AXC private keys are stored.


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.

Figure 119 Certificate Management window


Verification
Once AXC certificate & private key are installed successfully on the AXC node AXC certificate details like Issued To, Issued By, Valid From, Valid To, Serial Number & Fingerprint values can be observed in the Certificate Management window.

DN02166645
Issue 23A

Id:0900d805807f9e6c
Confidential

159

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 certificate
and 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 the
CMP client and Certificate Authority. At the initial configuration these values are to be
made out-of-band and using the Site Element Manager the values are downloaded over
a local connection. The Certificate Authority IP address and TCP port number are configured using the Element Manager or by deploying an AXC Site Configuration File.
This configuration is used by the AXC embedded CMP client to exchange messages
with the Certificate Authority. The CR IP address and TCP port number are configured
using the Element Manager by deploying an AXC Site Configuration File. This configuration is used by the AXC embedded CMP client to retrieve the CA certificate from the
certificate repository (CR). The CA certificate retrieval uses the LDAPv3 protocol.
PSK and RefNum must be generated in the same Certificate Authority which is to be
used to get AXC and CA certificates. These values also need to be made available for
the Certificate Authority in order to allow the establishment of a secure CMP message
exchange.
Configuring CMP and CR server IP addresses and PSK and RefNum triggers to take
CMP into use for this particular AXC. This causes the creation of a new private and
public 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.

160

Browse to the location where the text file for the RefNum and PSK are stored or
type the values manually.

Enter the Certificate Authority IP address and the TCP port number.

Id:0900d805807f9e6d
Confidential

DN02166645
Issue 23A

Commissioning AXC

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

DN02166645
Issue 23A

Id:0900d805807f9e6d
Confidential

161

Commissioning AXC

Further information
CMP initialization can be manually triggered by using the Update Certificates button.

162

Id:0900d805807f9e6d
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.21

Configuring VLAN Differentiation


Purpose
The idea of the VLAN traffic differentiation is to insert a VLAN ID into Ethernet frames
according 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 operators to separate traffic of different types or to aggregate traffic of the same type in their
backhaul 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 more
information, see Managing licenses in Operating and Maintaining AXC.
VLAN traffic differentiation feature is only supported by AXCF. Make sure that the Transport mode is either IP Iub or Dual Iub mode. For instructions, see Configuring Transport
mode.
Steps

Configure public IP address.


For instructions, see Setting public IP address.

Configure transport IP address.


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

Add VLAN.
In IP settings go to Transport Addresses.

DN02166645
Issue 23A

Id:0900d805807f9e6e
Confidential

163

Commissioning AXC

Figure 122 Transport Addresses tab


4

Click on Add... in the VLAN interface window.


The Add VLAN interface window opens.

164

Id:0900d805807f9e6e
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 123 Add VLAN interface window


1. Enter the identifier of the VLAN to which the interface belongs. Possible values
range 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 1000
Mbps. 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 interface.
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 the
window.
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. These


parameters are not present in Dual Iub mode.

DN02166645
Issue 23A

Id:0900d805807f9e6e
Confidential

165

Commissioning AXC

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 or
without VLAN mapping.

166

Id:0900d805807f9e6e
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.22

Configuring AXC Q1 Support Function


Purpose
The Q1 Support Function in AXC acts as a master poller for Nokia Siemens Networks
Q1 managed network elements. The AXC Q1 Support Function can poll far-end Q1
network elements via Q1 Embedded Operation Channels (EOC) as well as network
elements 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 interface
unit. See Commissioning FlexiHopper (Plus) and MetroHopper with IFUE for more information on configuring the Q1 management connection over the Q1SF and the connection 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 on
the 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 may
differ. Please refer to Q1 Agent documentation for more information.

The Q1 Support Function settings are not persistent. If no Q1 Agent connection is


available, the Q1 Support Function has to be reconfigured if the AXC is rebooted or
the power is lost. If a Q1 Agent connection is available, the Q1 Support Function is
automatically 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 settings.
Check that the last line of the output reads # clean run, no errors occurred.

DN02166645
Issue 23A

Id:0900d805807f9e7c
Confidential

167

Commissioning AXC

Figure 126 Q1 Support Function output


Further information
See also Configuring Q1 EOCs.

168

Id:0900d805807f9e7c
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.23

Configuring loopbacks
Purpose
This procedure describes how to configure loopbacks with the AXC Manager. The following 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 interface)

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.

Create the loopback.


Click Modify. The Modify Interface window opens. Select the Loop pane and check the
Loop box.

Figure 127 Creating a loopback


3

Select the loopback type.


The loopback type can be either To Equipment (default) or To Interface.

Define the loop timeout.


Define the New Timeout. It is the time period after which the loopback stops automatically. The default value is 15 minutes and the maximum value 1440 minutes (1 day).

Send the changes to the node.


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

DN02166645
Issue 23A

Id:0900d805807f9e7d
Confidential

169

Commissioning AXC

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 created
on 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 a
valid license to use this feature.
Steps

Configure the transport interfaces.


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

Create BFD sessions.


For instructions, see Creating BFD sessions. Repeat the same procedure to create
multiple BFD sessions.

Create route to the destination.


This feature allows for creating multiple routes to the same destination via different
GWs. Moreover, the user can associate BFD sessions with the static routes to monitor
route condition.
Click IP IP Settings and select the Routing tab.

170

Id:0900d80580817abe
Confidential

DN02166645
Issue 23A

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.
2.
3.
4.

DN02166645
Issue 23A

Enter the destination address and netmask.


Define the gateway IP address.
Assign the BFD session to the created route.
Cost is the metric used. Assign a value in range 1 254.

Id:0900d80580817abe
Confidential

171

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 the
transport routing table. Routes in DCN routing table are not allowed to be associated
with 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 is
0s.

172

Id:0900d80580817abe
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.25

Configuring Ethernet OAM


Ethernet OAM (Operations, Administration and Maintenance) is a collection of functions
for Ethernet networks. The purpose of these functions is to assist in operations on
Ethernet networks, for example, troubleshooting, performance monitoring and verification of the configuration.
Ethernet OAM functions can be divided in two categories:

5.25.1

Link OAM - functions are performed on a single Ethernet link only


Service OAM - functions are performed on multiple links

Configuring Link OAM


Before you start
Ethernet OAM is a licensed feature. Activating a valid license file on the node is a prerequisite.
Steps

Click Configuration Ethernet Link OAM.


Ethernet Link OAM window opens.

DN02166645
Issue 23A

Id:0900d80580817e3d
Confidential

173

Commissioning AXC

Figure 132 Ethernet Link OAM


2

Create Ethernet Link OAM Profile.


Click Configure Profiles....
Ethernet Link OAM Profiles window opens.

174

Id:0900d80580817e3d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 133 Ethernet Link OAM Profiles


Click Add Profile. Select the Active mode in use field (see figure Add Link OAM Profile).

Figure 134 Add Link OAM Profile


You can define the following parameters:
1. Loopback duration can be set to a value in range [10600].

DN02166645
Issue 23A

Id:0900d80580817e3d
Confidential

175

Commissioning AXC

2.
3.
4.
5.
6.
7.
8.
9.
10.
11.
12.

Test frame rate can be set to a value in the range [125000].


Test frame size can be set to a value in the range [641518].
Link lost time can be set to a value in the range [210].
Critical event alarm clearance delay can be set to a value in the range [110].
Maximum repetition number can be set to a value in the range [14].
Errored frame event threshold can be set to a value in the range
[02147483647].
Errored frame event interval can be set to a value in the range [160].
Errored frame period threshold can be set to a value in the range [0.2417486347].
Errored frame period interval can be set to a value in the range [10060000].
Errored frame seconds threshold can be set to a value in the range [065535].
Errored frame seconds interval can be set to a value in the range [10900].

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 click Modify.

176

Id:0900d80580817e3d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 136 Ethernet Link OAM window - Ethernet interfaces


Modify Ethernet Interface window opens.

Figure 137 Modify Ethernet Interface


1.
2.
3.
4.
5.

Select In use check box.


Modify Spped and duplex, if required.
Select desired Link OAM profile.
Once the Link OAM profile has been selected, select Link OAM Enabled check box.
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 OAM
profile 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.

DN02166645
Issue 23A

Id:0900d80580817e3d
Confidential

177

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 / uncheck 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 corresponding
interface and clicking Start Loopback, as shown on figure Ethernet Link OAM Loopback.

Figure 141 Ethernet Link OAM Loopback

178

Id:0900d80580817e3d
Confidential

DN02166645
Issue 23A

Commissioning AXC

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 network
defects, location of the defect and reports alarms in case of anomalies in the network
connectivity. 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 prerequisite.
Steps

Create a Service OAM object and define a new domain.


Click Configuration Service OAM.

DN02166645
Issue 23A

Id:0900d80580817e3d
Confidential

179

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).

180

Id:0900d80580817e3d
Confidential

DN02166645
Issue 23A

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.

DN02166645
Issue 23A

Id:0900d80580817e3d
Confidential

181

Commissioning AXC

Figure 148 Service OAM - New Endpoint


Add New Endpoint window opens.

182

Id:0900d80580817e3d
Confidential

DN02166645
Issue 23A

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 the
configured transmission period/CCM interval.
CCM interval value can be:
3.33ms: Default transmission period for protection-switching application (transmission 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 to
mask 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.

DN02166645
Issue 23A

Id:0900d80580817e3d
Confidential

183

Commissioning AXC

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.

184

Id:0900d80580817e3d
Confidential

DN02166645
Issue 23A

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.

DN02166645
Issue 23A

Id:0900d80580817e3d
Confidential

185

Commissioning AXC

Figure 154 Modify OAM

186

Id:0900d80580817e3d
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.26

IP Network Management
Purpose
IP Network Measurement allows for active measuring and supervising the IP network
conditions on end-to-end path between the BTS and the RNC.
Steps

Click IP settings RTT tab.

Figure 155 RTT tab

Configure the source port.


Click Modify... to configure the TWAMP sender port.

DN02166645
Issue 23A

Id:0900d8058082e75d
Confidential

187

Commissioning AXC

Figure 156 Modify RTT


1. Select In use field.
2. Enter the valid Source port number in the range 0 - 65535.
3. Select the required Message rate as either 1 per second or 10 per second.
Similarly configure the TWAMP reflector port (see figure Modify RTT - Reflector on).

Figure 157 Modify RTT - Reflector on


3

Create a session.
You can configure up to 10 sessions between the sender and reflector.
Click Modify... to create a session between the sender and the reflector or to modify an
existing session.

Figure 158 RTT tab - Sessions


Modify Session window opens.

188

Id:0900d8058082e75d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 159 Modify Session


1.
2.
3.
4.
5.
6.
7.
8.

Select In use field.


Enter the Destination IP address.
Assign a Destination port. The value range is 1 - 65535.
Enter the Source IP address.
Enter a DSCP. The value range is 0 - 63.
Select Message size. The value range is 69 - 1500.
Define Packet loss ratio alarm threshold.
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 IP
address, UDP port, DSCP value, or packet length. The same parameter set must
not 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 IP
address.
For UDP echo server the destination UDP port should be 7.
4

To view session statistics.


Select the required session. The selected session appears highlighted.

DN02166645
Issue 23A

Id:0900d8058082e75d
Confidential

189

Commissioning AXC

Figure 160 RTT tab - Session statistics

190

Id:0900d8058082e75d
Confidential

DN02166645
Issue 23A

Commissioning AXC

5.27

Creating BFD sessions


Purpose
Bidirectional Forwarding Detection (BFD) is a network protocol used to detect faults
between two forwarding engines. It provides low-overhead detection of faults even on
physical media that do not support failure detection of any kind, such as Ethernet, virtual
circuits, tunnels and MPLS LSPs. BFD establishes a session between two endpoints
over a particular link.
Steps

Configure the transport interface.


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

Create BFD session when Iub terminates in AXCF in IP Iub and Dual Iub mode.
1. Click IP settings Transport Address tab.

Figure 161 Transport Addresses


2. Create BFD sessions.
Click Configure... under Bidirectional Forwarding Detection label.

DN02166645
Issue 23A

Id:0900d805807fd13b
Confidential

191

Commissioning AXC

Figure 162 BFD Sessions


3. Configure BFD sessions.
Click Add to create new BFD session.

Figure 163 Add BFD Session


You 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.

192

Id:0900d805807fd13b
Confidential

DN02166645
Issue 23A

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 virtual
IP address.
4. Click OK to send the changes to the node.
g Detection time multiplier is the negotiated transmit interval, multiplied by
Detection time multiplier of far end, provides the Detection Time for the transmitting system in Asynchronous mode.
Desired Min TX interval is the minimum interval, in microseconds that the local
system would like to use when transmitting BFD Control packets. The value zero
is reserved.
Required Min RX interval is the minimum interval, in microseconds, between
received BFD Control packets that this system is capable of supporting. If this
value is zero, the transmitting system does not want the remote system to send
any periodic BFD Control packets.
Up to 16 BFD sessions can be established when Iub termination is pointing to
the AXCF in IP Iub and Dual Iub mode.
For Single hop BFD mode UDP destination port is 3784 which is fixed and hence
it can not be configured. For Multi hop BFD mode UDP destination port is 4784
which is fixed and it can not be configured either. In Single hop mode TTL is 255
and in Multi hop mode TTL can be 1255.
3

Create BFD session when Iub terminates in IFUH in IP Iub mode.


1. Click IP settings Transport Address tab.

DN02166645
Issue 23A

Id:0900d805807fd13b
Confidential

193

Commissioning AXC

Figure 164 Transport Addresses


2. Create BFD sessions.
Click Configure... under Bidirectional Forwarding Detection label.

Figure 165 BFD Sessions


3. Configure BFD sessions.
Click Add to create new BFD session.

194

Id:0900d805807fd13b
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 166 Add BFD Session


You 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.

DN02166645
Issue 23A

Id:0900d805807fd13b
Confidential

195

Commissioning AXC

5.28

QoS Aware Ethernet switching


Purpose
With QoS aware Ethernet switching enabled, transport interface can be enhanced with
the following features:

QoS awareness
VLAN awareness
Egress scheduling and shaping
Ingress policing (Rate Limiting)

QoS based Ethernet switching is supported on all the three AXCF transport interfaces.
Before you start
QoS Aware Ethernet switching is a licensed feature. Activating a valid license file on the
node is a prerequisite.
Steps
1

Configure the transport interface.


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

196

Id:0900d8058082ea5b
Confidential

DN02166645
Issue 23A

Commissioning AXC

Click Configuration Ethernet Switching.

Figure 168 Ethernet Switching


3

Configure QoS classification mode.


1. Click Modify... and select QoS classification mode.

DN02166645
Issue 23A

Id:0900d8058082ea5b
Confidential

197

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.

198

Id:0900d8058082ea5b
Confidential

DN02166645
Issue 23A

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 configuration


Modify VLAN Aware Configuration window opens.

DN02166645
Issue 23A

Id:0900d8058082ea5b
Confidential

199

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.

200

Id:0900d8058082ea5b
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 174 Ethernet Switching

DN02166645
Issue 23A

Id:0900d8058082ea5b
Confidential

201

Commissioning AXC

5.29

Dynamic routing for Iub


Purpose
The purpose of dynamic rerouting for Iub is to improve backhaul network resilience by
adding a route protection mechanism in conjunction with the existing BFD functionality.
This feature adds OSPF routing protocol for best route calculation to the destination. It
also allows for dynamic auto-configuration of the routing table in the BTS as well as protection of the traffic towards BTS.
Before you start
Dynamic routing for is a licensed feature. Activating a valid license file on the node is a
prerequisite.
Steps

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 Addresses


Click Modify... to set the virtual IP address.

202

Id:0900d80580817e8d
Confidential

DN02166645
Issue 23A

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.

Enable OSPF and activate OSPF with BFD.


Click IP Settings OSPF tab.

DN02166645
Issue 23A

Id:0900d80580817e8d
Confidential

203

Commissioning AXC

Figure 178 OSPF tab


Click Modify.... Modify OSPF window opens.

204

Id:0900d80580817e8d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 179 Modify OSPF


Select Enabled field to enable OSPF. Click OK.
To activate OSPF with BFD, click Modify....

DN02166645
Issue 23A

Id:0900d80580817e8d
Confidential

205

Commissioning AXC

Figure 180 OSPF tab


Modify OSPF window opens. Select OSPF with BFD check box to enable OSPF with
BFD.

206

Id:0900d80580817e8d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 181 Modify OSPF


4

Configure OSPF.
Click IP Settings OSPF tab.

Figure 182 OSPF tab - IP Interfaces


Click Modify... to modify selected IP interface. Modify OSPF window opens.

DN02166645
Issue 23A

Id:0900d80580817e8d
Confidential

207

Commissioning AXC

Figure 183 Modify OSPF


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.

Enable OSFP on BFD.


Click IP Settings OSPF tab.

Figure 184 OSPF tab - IP Interfaces


Click Modify.... Modify OSPF window opens.

208

Id:0900d80580817e8d
Confidential

DN02166645
Issue 23A

Commissioning AXC

Figure 185 Modify OSPF


Select Active field and set the parameters:

DN02166645
Issue 23A

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.

Id:0900d80580817e8d
Confidential

209

Verifying commissioning

Commissioning AXC

6 Verifying commissioning
Purpose
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 more
information see Configuring loopbacks.
2

Check the synchronization settings.


Check that the synchronization sources are defined and available.

Check the Virtual Path and Virtual Channel terminations and connections.
Check the ATM Virtual Path and Virtual Channel terminations and cross-connections
have been created.

Check the DCN settings.


Check the Data Communication Network settings.

Check OSPF areas.


Check that all OSPF areas have been created.

Check the IP routing.


Check the IP routing entries.

Check the DHCP configurations.


Check that all DHCP configurations have been created.

Check the BTS IP settings.


Check that the BTS identifier and other related settings have been configured.

210

Id:0900d805807f9e7f
Confidential

DN02166645
Issue 23A

Commissioning AXC

Verifying commissioning

Check the Restricted mode settings.


Check that the required exceptions have been defined if the Restricted Mode is enabled.

10

Check the NTP servers or system time.


Check that all configured Network Time Protocol servers, the server ports and their IP
addresses 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 number
level to enable fast and efficient search in the network in case such information is
needed. For more information, see Storing item code and serial number for traceability
purposes in Operating and Maintaining AXC.

16

Check the Q1 Support Function settings.


Check that the Q1 Support Function has been configured.

17

DN02166645
Issue 23A

Close the connection to the AXC.

Id:0900d805807f9e7f
Confidential

211

Checklist for AXC commissioning

Commissioning AXC

7 Checklist for AXC commissioning


SITE NAME
SITE ID
SITE ADDRESS

AXC ID
Check

Check mark

Equipment has been installed according to the installation


instructions and site-specific documents.
Local Management Tool complies with AXC Manager hardware
and 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.

Commissioning with an XML file


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.

Commissioning with a macro


Check

Check mark

Run the pre-recorded macro.


Ping the public IP address of the node using AXC web interface.

Manual commissioning
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.

212

Id:0900d805807f9e80
Confidential

DN02166645
Issue 23A

Commissioning AXC

Checklist for AXC commissioning

Check

Check mark

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.

Commissioning IP Iub
Check

Check mark

Check the hardware configuration.


Activate IP Iub transport mode.
Configure Ethernet interfaces (IFUH / AXCF).
Configure IP Iub settings.
Configure Quality of Service settings.
Configure synchronization.
Configure Management Protocol.

Commissioning Dual Iub


Check

Check mark

Check the hardware configuration.


Activate Dual Iub transport mode.
Configure Ethernet interfaces ( AXCF).
Configure IP Iub settings.

DN02166645
Issue 23A

Id:0900d805807f9e80
Confidential

213

Checklist for AXC commissioning

Commissioning AXC

Check

Check mark

Configure Quality of Service settings.


Configure Iub terminations for ATM Iub.
Configure DCN and transport routes.
Configure synchronization.
Configure Management Protocol.

214

Id:0900d805807f9e80
Confidential

DN02166645
Issue 23A