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.
Contents
Contents 3
1 Documentation changes in RNC Integration 7 1.1 Changes between issues 8-0 and 9-0 7
1.2 Changes between issues 7 and 8-0 8 1.3 Changes in issue 7 10
2 Integration overview 15
3 Configuring IP for O&M backbone (RNC - NetAct) 21 3.1 Configuring IP for O&M backbone (RNC — NetAct) 21
3.2 Creating MMI user profiles and user IDs for remote connections to NetAct 23
3.3 Configuring IP stack in OMU 25 3.4 Configuring IP routing 28
3.4.1 Creating OSPF configuration for O&M connection to NetAct 28 3.4.2 Configuring static routes for the O&M connection to NetAct 33 3.5 Configuring LAN switch 35
3.5.1 Configuring ESA12 35 3.5.2 Configuring ESA24 38
3.6 Configuring NEMU for DCN 41 3.6.1 Configuring NEMU for DCN 41
3.6.2 Configuring DHCP server in NEMU 42
3.6.3 Configuring DNS client and server in NEMU 44 3.6.4 Configuring NEMU to RNC 48
3.6.5 NemuRegEdit 50
3.6.6 NemuRUIMConfiguration 55
3.6.7 Configuring NTP services in NEMU 60 3.6.8 Finalising SQL server configuration 64 3.6.9 Configuring IP address for NEMU 66 3.7 Configuring external IP connections 68
3.7.1 Connecting to O&M backbone via Ethernet 68 3.7.2 Configuring IP over ATM interfaces 69
4 Integrating NEMU 71
4.1 Configuring NEMU system identifier (systemId) 71 4.2 Configuring the RNC object 72
4.3 Configuring Nokia NetAct interface with NEMU 73 5 Configuring heartbeat interval for RNC 77 6 Configuring RNC level parameters 79
6.1 Defining external time source for network element 79 6.2 Creating local signalling configuration for RNC 80
7 Configuring transmission and transport interfaces 85 7.1 Configuring PDH for ATM transport 85
7.3 Configuring SDH for ATM transport 90 7.4 Creating SDH protection group 92 7.5 Creating phyTTP 94
7.6 Creating ATM resources in RNC 97 8 Configuring synchronisation inputs 105 9 Creating Iub interface (RNC-BTS) 111
9.1 Configuring transmission and transport resources 111 9.2 Creating radio network connection configuration 111
9.3 Creating ATM termination point for IP over ATM connection 113 9.4 Configuring IP for BTS O&M (RNC-BTS/AXC) 115
10 Creating Iu-CS interface (RNC-MGW) 121
10.1 Configuring transmission and transport resources 121 10.2 Configuring ATM-based signalling channels 121 10.2.1 Creating remote MTP configuration 121
10.2.2 Activating MTP configuration 126
10.2.3 Setting MTP level signalling traffic load sharing 128 10.2.4 Creating remote SCCP configuration 129
10.2.5 Activating SCCP configuration 133
10.3 Configuring IP-based signalling channels 134 10.4 Configuring Iu-CS parameters of RNC 138
10.5 Creating routing objects and digit analysis for Iu interface in RNC 140 10.6 Creating routing objects and digit analysis with subdestinations and
routing policy for Iu interface 145
11 Creating Iu-PS interface (RNC-SGSN) 153
11.1 Configuring transmission and transport resources 153 11.2 Configuring signalling channels 153
11.3 Configuring Iu-PS parameters of RNC 153
11.4 Configuring IP for Iu-PS User Plane (RNC-SGSN) 154 12 Creating Iur interface (RNC-RNC) 167
12.1 Configuring transmission and transport resources 167 12.2 Configuring signalling channels 167
12.3 Configuring Iur parameters of RNC 167
12.4 Creating routing objects and digit analysis for Iur interface in RNC 168 13 Creating Iu-BC interface (RNC-CBC) 175
13.1 Configuring transmission and transport resources 175 13.2 Configuring Iu-BC parameters of RNC 175
13.3 Configuring IP for Iu-BC (RNC-CBC) 176 14 Configuring radio network objects 183 14.1 Creating frequency measurement control 183 14.2 Creating handover path 184
14.3 Creating a WCDMA BTS site 185 14.4 Creating a WCDMA cell 188
14.5 Creating an internal adjacency for a WCDMA cell 189 14.6 Creating an external adjacency for a WCDMA cell 192
15 Integrating location services 195 15.1 Overview of location services 195
15.2 Creating TCP/IP configuration in RRMU units 195 15.2.1 Overview of TCP/IP configuration in RRMU units 195 15.2.2 Defining IP addresses and IP routes to RRMU units 197 15.3 Configuring ESA24 switches 200
15.3.1 Configuring ESA24-0 200 15.3.2 Configuring ESA24-1 206 15.4 Activating location services 213
15.4.1 Activating the Location Services feature 213 15.4.2 Activating the ADIF interface 213
15.4.3 Activating the Iupc interface 214 16 Printing alarms 217
16.1 Printing alarms using LPD protocol 217
16.2 Printing alarms via Telnet terminal or Web browser 219 Related Topics 223
1
Documentation changes in RNC
Integration
1.1
Changes between issues 8-0 and 9-0
Modified chapters
Table 1. Modified chapters
Title of the modified chapter Description of the change See Configuring IP stack in OMU
A paragraph about IP layer configuration added before the step text. A link to ATM and IP plan interfaces added.
Configuring IP stack in OMU
Configuring static routes for the O&M connection to NetAct
A paragraph about static route configuration added before the step text. A link to ATM and IP plan interfaces added.
Configuring static routes for the O&M connection to NetAct
Creating ATM resources in RNC
Note text on using the Object Browser or NetAct edited and replaced by normal text. A link to ATM and IP plan interfaces added.
Creating ATM resources in RNC
Creating ATM termination point for IP over ATM connection
A paragraph added to Purpose. A link to ATM and IP plan interfaces added.
Creating ATM termination point for IP over ATM connection
Configuring IP for BTS O&M (RNC-BTS/AXC)
A paragraph about IP over ATM connection
configuration added before the steps. A link to ATM and IP plan interfaces added.
Configuring IP for BTS O&M (RNC-BTS/AXC)
Table 1. Modified chapters (cont.)
Title of the modified chapter Description of the change See Configuring IP-based signalling channels
A paragraph about IP over ATM connection
configuration added before the steps. A link to ATM and IP plan interfaces added.
Configuring IP-based signalling channels
Configuring IP for lu-PS User Plane (RNC-SGSN)
A paragraph about lu-PS interface ATM and IP basic resources configuration added before the steps. A link to ATM and IP plan interfaces added.
Configuring IP for lu-PS User Plane (RNC-SGSN)
Activating the location services feature
A document reference to NOLS added.
Activating the location services feature
1.2
Changes between issues 7 and 8-0
New chapters
Table 2. New chapters
Title of the new chapter
Description of the change See
NemuRUIMConfiguration In this release, RNC supports the Remote User Information
Management (RUIM) feature. This sections provides instructions for configuring NEMU when the RUIM feature is used.
Modified chapters
Table 3. Modified chapters
Title of the modified chapter
Description of the change See
NemuRegEdit Registration Account user name corrected.
NEMUFTP user name corrected.
NemuRegEdit
Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface
It has been mentioned that alternative routing is the default routing policy and if alternative routing is used for the subdestination, new subdestination type and
percentages should not be defined.
Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface
Configuring NEMU for DCN
Steps for configuring the RUIM feature in NEMU and finalising the SQL server configuration have been added.
Configuring NEMU for DCN
Configuring NEMU to RNC The NEMU registry variables used when configuring NEMU for RNC connection have been added. Information on the user accounts that must be created in NEMU has been added.
Configuring NEMU to RNC
Configuring IP for O&M backbone (RNC-NetAct)
The note about improving the redundancy of the RNC Ethernet network by installing a redundant ESA24 has been removed.
Configuring IP for O&M backbone (RNC-NetAct)
Configuring IP for Iu-PS User Plane (RNC – SGSN)
Instructions for creating UMTS traffic classification mapping configuration (GTPU) have been added.
Configuring IP for Iu-PS User Plane (RNC – SGSN)
Overview of TCP/IP configuration in RRMU units
Sales item kit information updated. Overview of TCP/IP configuration in RRMU units
Configuring ESA24-0 BiNOS version updated. Information about the standard-compatible implementation of the IEEE 802.1s MSTP protocol updated. Configuration instructions updated.
Configuring ESA24-0
Configuring ESA24-1 BiNOS version updated. Information about the standard-compatible implementation of the IEEE 802.1s MSTP protocol updated. Configuration instructions updated.
Table 3. Modified chapters (cont.)
Title of the modified chapter
Description of the change See
Activating the ADIF interface
ADIF activation instructions updated. Activating the ADIF interface
Activating the Iu-PC interface
Iu-PC activation instructions updated. Activating the Iu-PC interface
Removed chapters
. Configuring O&M IP network
1.3
Changes in issue 7
New chapters
Table 4. New chapters
Title of the new chapter
Description the change See
Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface
In this release, alternative routing can be used in the Iu-CS interface if the connection to the primary direction is broken or the subdestination selected before is congested.
Creating routing objects and digit analysis with subdestinations and routing policy for Iu interface
Configuring IP-based signalling channels
In this release, SS7 signalling over IP is supported in the Iu-PS, Iu-CS, and Iur interfaces.
Configuring IP-based signalling channels
Table 4. New chapters (cont.)
Title of the new chapter
Description the change See
Integrating location services
In this release, the Nokia RNC implementation of the location services includes two different interfaces, Iu-PC and ADIF, to the external LCS server for additional locationing methods.
Overview of location services Overview of TCP/IP configuration in RRMU units
Defining IP addresses and IP routes to RRMU units Configuring ESA24-0 Configuring ESA24-1
Activating the Location Services feature
Activating the ADIF interface Activating the Iu-PC interface Configuring IP addresses to OMU units
Overview of O&M IP network configuration
Configuring OSPF routing to OMU units
Modified chapters
Table 5. Modified chapters
Title of the modified chapter
Description of the change See
Integration Iu-PC and ADIF interface information has been added.
Integration overview
NEMURegEdit Release upgrade related note about providing the RNC baseID, typeID, and OMU IP address for
NemuRegEdit has been removed as this information is no longer required in RN2.1 to RN2.2 upgrade.
NEMURegEdit
Configuring IP for O&M backbone (RNC - NetAct)
A note about improving the
redundancy of the Ethernet network has been added.
Configuring IP for O&M backbone (RNC - NetAct)
Configuring static routes for O&M connection to NetAct
The syntax of theQKCcommand has been changed. This change is related to Multiple Default Route/IP routing (OSPFv2 in Chorus).
Configuring static routes for O&M connection to NetAct
Table 5. Modified chapters (cont.)
Title of the modified chapter
Description of the change See
Configuring ESA24 More information has been added to the step for configuring RSTP and MSTP.
Configuring ESA24
Configuring DNS client and server in NEMU
DNS query has been removed from application launcher; therefore, references to DNS query have been removed from this chapter.
Configuring DNS client and server in NEMU
Finalising SQL server configuration
A screenshot has been added. Finalising SQL server configuration
Configuring IP for BTS O&M (RNC – BTS/AXC)
The syntax of theQKCcommand has been changed. This change is related to Multiple Default Route/IP routing (OSPFv2 in Chorus).
In this release, FlexiBTSs are
supported. Therefore, two notes about the IP and ATM configurations of FlexiBTS have been added.
Configuring IP for BTS O&M (RNC – BTS/AXC)
Creating remote MTP configuration
The syntax of the NRC command has been corrected.
In RN2.2, SIGTRAN can be used as an alternative to the ATM-based MTP3 in the Iu-PS, Iur, and Iu-CS interfaces. Information about SS7 over IP has been added to this chapter.
Creating remote MTP configuration
Configuring IP for Iu-PS User Plane (RNC – SGSN)
The syntax of theQKCcommand has been changed. This change is related to Multiple Default Route/IP routing (OSPFv2 in Chorus).
Configuring IP for Iu-PS User Plane (RNC – SGSN)
Configuring IP for Iu-BC (RNC – CBC)
The syntax of theQKCcommand has been changed. This change is related to Multiple Default Route/IP routing (OSPFv2 in Chorus).
Configuring IP for Iu-BC (RNC – CBC)
Creating frequency measurement control
First step on creating frequency measurement control has been modified.
Creating frequency measurement control
Creating handover path First step on creating handover path has been modified.
Creating handover path
Creating a WCDMA BTS site
A step on Site Creation Confirmation has been deleted.
Creating a WCDMA BTS site
Creating a WCDMA cell A step on creating the cell unlocked has been added to WCDMA cell creation.
Table 5. Modified chapters (cont.)
Title of the modified chapter
Description of the change See
Creating an external adjacency for a WCDMA cell
The internal adjacency creation step 2 has been modified.
Creating an external adjacency for a WCDMA cell
2
Integration overview
You can start the integration of a network element after the network element has been successfully installed and commissioned. During the commissioning phase, the network elements have been configured and tested as stand-alone entities. During the integration phase the
interconnections between the network elements are configured and their parameters are customised. After successful integration the network element is ready for commercial use.
Note
IPv6 is not supported in current releases in WCDMA RAN even if it is included in some IP configuration intructions.
Integration overview
Integration consists of the following steps:
1. configuring internet protocol (IP) for operation and maintenance (O&M) backbone (radio network controller (RNC) - NetAct) a. configuring IP for O&M backbone (RNC - NetAct)
b. creating man-machine interface (MMI) user profiles and user IDs for remote connections to NetAct
c. configuring IP stack in OMU d. configuring IP routing
e. configuring local area network (LAN) switch
f. configuring network element management unit (NEMU) for data communication network (DCN)
g. configuring external IP connections 2. integrating NEMU
a. configuring network element system identifier (systemId) to NEMU
b. configuring the RNC object
c. configuring Nokia NetAct interface with NEMU 3. configuring heartbeat interval for RNC
4. configuring RNC level parameters
a. defining external time source for network element b. creating local signalling configuration for RNC 5. configuring transmission and transport interfaces
a. configuring plesiochronous digital hierarchy (PDH) for asynchronous transfer mode (ATM) transport
b. creating inverse multiplexing for ATM (IMA) group c. configuring synchronous digital hierarchy (SDH) for ATM
transport
d. creating SDH protection group
e. creating physical layer trail termination point (phyTTP) f. creating ATM resources in RNC
6. configuring synchronisation inputs
7. creating Iub interface (RNC - base transceiver station (BTS)) a. configuring transmission and transport resources (see step 5) b. creating radio network connection configuration
c. creating ATM termination point for IP over ATM connection d. configuring IP for BTS O&M (RNC-BTS/ATM cross-connection
(AXC))
8. creating Iu-CS interface (RNC - multimedia gateway (MGW)) a. configuring transmission and transport resources (see step 5) b. configuring ATM-based signalling channels
c. configuring IP-based signalling channels d. configuring Iu-CS parameters of RNC
e. creating routing objects and digit analysis for Iu interface in RNC
f. creating routing objects and digit analysis with subdestinations and routing policy for Iu interface
9. creating Iu-PS interface (RNC-serving GPRS support node (SGSN)) a. configuring transmission and transport resources
b. configuring ATM-based signalling channels c. configuring IP-based signalling channels
d. configuring Iu-PS parameters of RNC
e. configuring IP for Iu-PS User Plane (RNC-SGSN) 10. creating Iur interface (RNC-RNC)
a. configuring transmission and transport resources b. configuring ATM-based signalling channels c. configuring IP-based signalling channels d. configuring Iur parameters of RNC
e. creating routing objects and digit analysis for lur interface in RNC
11. creating Iu-BC interface (RNC-cell broadcast centre (CBC)) a. configuring transmission and transport resources b. configuring Iu-BC parameters of RNC
c. configuring IP for Iu-BC (RNC-CBC) 12. configuring radio network objects
a. creating frequency measurement control (FMC) b. creating handover path
c. creating a WCDMA BTS (WBTS) site d. creating a WCDMA cell (WCEL)
e. creating an internal adjacency for a WCDMA cell f. creating an external adjacency for a WCDMA cell 13. integrating location services
a. creating TCP/IP configuration in RRMU units b. configuring ESA24 switches
c. activating location services d. configuring O&M IP network 14. printing alarms
a. printing alarms using LPD protocol
b. printing alarms via a Telnet terminal or a web browser Example network
The integration instructions are based on the following third generation example network:
Figure 1. Example network and logical interfaces between network elements
The logical interfaces for the RNC in the 3rd generation network are presented in the following list.
Iu-CS logical interface between the RNC and the core network. The Iu interface provides signalling means to establish, maintain and release links and recover fault situations and generic bearer services over its user plane.
Iu-PS logical interface between the RNC and the SGSN Iur logical interface for the interconnection of two RNC
components of the UMTS terrestrial radio access network (UTRAN) system
Iub logical interface between the RNC and the WBTS RNC RNC Multimedia Gateway Rel. 4 SGSN Iu-PS Iur Iub Iub Iu-CS NetAct BTS BTS Iu-BC CBC MSC Server A-GPS Server SAS Iu-PC ADIF
Iu-BC logical interface between the RNC and the cell broadcast centre (CBC)
ADIF Logical interface between the RNC and the A-GPS Server
Iupc Logical interface between the RNC and the Stand-alone SMLC
Required integration planning information
The network planning process delivers all required information for network element installation, commissioning and integration. Network planning can be divided into the following phases: transmission & transport and radio network planning.
The following planning activities must be accomplished before the integration phase starts:
1. radio network planning
2. transport/transmission network planning (in Nokia terminology, transmission is related to the PDH/SDH network and transport to the ATM/AAL2 network).
3
Configuring IP for O&M backbone (RNC
-NetAct)
3.1
Configuring IP for O&M backbone (RNC — NetAct)
Purpose
This chapter shows the procedure to configure the Network Element Management Unit (NEMU), ESA12/ESA24 Ethernet switch and the Operation and Maintenance Unit (OMU) for the data communication network (DCN). After this, you can use the Element Manager to manage the RNC remotely.
The O&M backbone can be configured either via Ethernet or via ATM virtual connections, or via both if OSPF is used.
Before you start
Check that:
. you have the IP address plan and IP parameters for OMU, NEMU,
and ESA12/ESA24.
. your computer has the following: . DHCP client
. Connection to the Element Manager and remote management
application for NEMU
For more information, see Installing Element Manager.
. Ethernet interface connected to a port of ESA12/ESA24
If O&M backbone towards NetAct is connected via ATM virtual connection, the transport and transmission network plan for the interface in question is also required. Usually, this interface is Iu-CS.
Figure 2. Preconfigured settings for O&M network
The default gateway in NEMU and ESA12/ESA24 is 192.168.1.1. Steps
1. Create MMI user profiles and user IDs for remote connection to NetAct
See Creating MMI user profiles and user IDs for remote connections to NetAct for detailed instructions.
2. Configure IP stack in OMU
See instructions in Configuring IP stack in OMU. 3. Configure IP routing
There are two ways to configure routing information:
. by creating OSPF configuration
See instructions in Creating OSPF configuration for O&M connection to NetAct. 192.168.1.5/28 192.168.1.1/28 (logical) RNC OMU 192.168.1.10/28 Computer with Element Manager RNC LAN 192.168.1.0/28 NEMU ESA12/ESA24 192.168.1.9/28
. by configuring static routes
See instructions in Configuring static routes for O&M connection to NetAct.
4. Configure the Ethernet/LAN switch
Configure the Ethernet (LAN) switch according to instructions in Configuring ESA12 or Configuring ESA24, depending on which one you have in your configuration.
5. Configure NEMU
Configure NEMU according to instructions in Configuring NEMU for DCN.
6. Configure external IP connections
Configure the connection to NetAct for O&M traffic. There are two ways to connect the RNC to NetAct:
. by configuring the O&M backbone via Ethernet
Refer to instructions in Connecting to O&M backbone via Ethernet.
. by configuring the O&M backbone via ATM virtual connections
Refer to instructions in Configuring IP over ATM interfaces. The recommended way of connecting RNC to NetAct is via Ethernet. The connection via ATM should only be used as a backup. O&M connections can be configured to use both ways, if OSPF is used for routing.
3.2
Creating MMI user profiles and user IDs for remote
connections to NetAct
Purpose
To enable remote connections from the NetAct to the RNC, you need to create users NUPADM and NEMUAD and their profiles in the RNC. NetAct application (service user management) accesses RNC with NUPADM profile. NUPADM profile is mandatory to create other service users in NetAct application. NEMUAD profile is created to enable communication between NEMU and OMU. For example, without NEMUAD profile, PM data cannot be transferred to NEMU and therefore affects the transfer measurement to NetAct.
See the example below for detailed instructions. Before you start
If you do not know the password, contact your NetAct administrator. Steps
1. Establish a telnet connection to RNC OMU
Enter the preconfigured IP address to OMU (the default IP address is 192.168.1.1):
telnet <IP address of OMU> 2. Create new MMI user profiles
Create the user profiles for NUPADM and NEMUAD. Refer to Creating MMI user profiles in Information Security for details. 3. Create new MMI user IDs
Create the NUPADM and NEMUAD user IDs. Refer to Creating MMI user IDs in Information Security for details.
Example Creating MMI user profiles and user IDs in the RNC This example shows how to create the NUPADM and NEMUAD MMI profiles and user IDs in the RNC.
1. Create the user profiles.
ZIAA:NUPADM:ALL=250:VTIME=FOREVER,UNIQUE=YES; ZIAA:NEMUAD:ALL=250:VTIME=FOREVER,UNIQUE=YES:: FTP=W;
2. Create the user IDs. ZIAH:NUPADM:NUPADM; ZIAH:NEMUAD:NEMUAD;
When creating a new user ID, the system prompts you for a password. The password created here is used for communication between the NEMU or the NetAct and the RNC. The system displays the following output:
/* IDENTIFY PASSWORD:
MINIMUM PASSWORD LENGTH IS 6 MAXIMUM PASSWORD LENGTH IS 16 */ NEW PASSWORD:********
VERIFICATION:******** COMMAND EXECUTED
Enter the same password as used in the NEMU and the NetAct.
3.3
Configuring IP stack in OMU
Purpose
The purpose of this procedure is to configure OMU for data communication network (DCN).
Before you start
Note
In addition to the MML based configuration the IP layer can be configured via the IP plan interface from the NetAct. The IP plan support does not contain the OSPF configuration. For further details on the IP plan interface see IP plan interface in documentRNC Operation and Maintenance.
A telnet connection to RNC OMU must be open. For IPv4:
You can use the QRJ, QRH, QRI, and QRS commands to interrogate the configuration.
For IPv6:
You can use the Q6J, Q6H, Q6I, and Q6S commands to interrogate the configuration.
Steps
1. Configure DNS parameter data
For IPv4:
ZQRK:[<primary DNS server>],[<secondary DNS
server>],[<third DNS server>],[<local domain name>], [<sortlist>],[<netmask>]:[<resolver cache>],
[<round robin>]; For IPv6:
ZQ6K:[<primary DNS server>],[<secondary DNS
server>],[<third DNS server>],[<local domain name>], [<network sortlist>],[<prefix length>]:[<resolver cache>],[<round robin>];
2. Modify TCP/IP parameters
Set host names, define if the OMU forwards IP packets, set the maximum time-to-live value and define if the subnets are considered to be local addresses in both OMU units.
For IPv4:
ZQRT:<unit type>, <unit index>:(HOST=<host name>, [IPF=<IP forwarding>],[TTL=<IP TTL>],[SNL=<subnets are local>]);
For IPv6:
ZQ6T:<unit type>,<unit index>:([IPF=<IP
forwarding>],[HLIM=<hoplimit>],[RADV=<router advertisement>]);
3. Add a new logical IP address
Assign the IP address to both OMU units by QRN for IPv4 and Q6N for IPv6.
ZQRN:OMU:<interface name>,[<point to point interface type>]:[<IP address>],[<IP address type> ]:[<netmask length>]:[<destination IP address>]:[<MTU>]:
[<state>];
ZQ6N:OMU,<unit index>:<interface name>:[<IP address>],[<address type>]:[<prefix length>]: [<destination IP address>];
4. Configure IP routing
There are two ways to configure routing information:
. by creating OSPF configuration
Refer to instructions in Creating OSPF configuration for O&M connection to NetAct.
. by configuring static routes
Refer to instructions in Configuring static routes for O&M connection to NetAct.
5. Remove the preconfigured IP address
Remove the preconfigured IP address from both OMU units by QRN command for IPv4, by Q6G command for IPv6.
ZQRN:OMU:<interface name...>,:<IP address>,,DEL; ZQ6G:OMU,<unit index>:<interface name>:<IP
address>:;
Note
If the unit index for 2N type logical IP address is specified, the logical addresses will be deleted both from WO and SP unit.
Example Configuring IPv4 stack in OMU
This example shows how to configure the IPv4 stack in OMU for DCN. 1. Configure DNS parameter data. The IPV4 address of the primary
DNS server is 10.1.1.5 and the local domain name RNC1.NETACT. OPERATOR.COM.
ZQRK:10.1.1.5,,,"RNC1.NETACT.OPERATOR.COM";
2. Modify IPv4 parameters for both OMU units separately. Set the host name to OMU, set IP forwarding on, and specify that subnets are not local.
ZQRT:OMU,0:HOST="OMU",IPF=YES,SNL=NO; ZQRT:OMU,1:HOST="OMU",IPF=YES,SNL=NO;
3. Add a new logical IPv4 address (10.1.1.2) to the OMU units. The interface name is EL0 and the netmask is length 28.
ZQRN:OMU:EL0:10.1.1.2,L:28:::UP;
4. Configure IPv4 routing. For examples, see Creating OSPF
configuration for O&M connection to NetAct and Configuring static routes for O&M connection to NetAct.
5. Remove the preconfigured IPv4 address (198.168.1.1) from both OMU units.
ZQRN:OMU:EL0:192.168.1.1,,DEL; Example Configuring IPv6 stack in OMU
This example shows how to configure the IPv6 stack in OMU for DCN. 1. Configure DNS parameter data. The IPv6 address of the primary
DNS server is 3FEE::1 and the local domain name RNC1.NETACT. OPERATOR.COM.
ZQ6K:"3FEE::1",,,"RNC1.NETACT.OPERATOR.COM";
2. Modify IPv6 parameters for both OMU units separately. Set the host name to OMU, set IP forwarding on, set hoplimit value as 70, and set router advertisement OFF.
ZQ6T:OMU,0:IPF=ON,HLIM=70,RADV=OFF; ZQ6T:OMU,1:IPF=ON,HLIM=70,RADV=OFF;
3. Add a new logical IPv6 address (3FFE:1200:3012:C020:380:6FFF: FE5A:5BB7) to the OMU units. The interface name is EL0 and the netmask is length 20.
ZQ6N:OMU,0:EL0:"3FFE:1200:3012:C020:380:6FFF: FE5A:5BB7",L:20;
4. Remove the preconfigured IPv6 address (3FEE::1) from both OMU units.
ZQ6G:OMU,0:EL0:"3FEE::1":;
3.4
Configuring IP routing
3.4.1 Creating OSPF configuration for O&M connection to NetAct Purpose
Before you start
If O&M connections towards NetAct use also backup connection via ATM virtual connection, the IP over ATM interface for OMU must be created before OSPF is configured. Refer to instructions in Configuring IP over ATM interfaces.
You must remove the existing default routes before creating the OSPF configuration. If the default routes are not removed, the RNC might advertise itself, incorrectly, as an alternative default route to other routers. For instructions on how to remove default routes, see Configuring static routes for O&M connection to NetAct.
Steps
1. Configure OSPF router parameters (QKS)
If only logical IP addresses are configured for the OMUs, the same router ID can be configured to both OMUs. If the OMU units have physical IP addresses in addition to a logical IP address, the OMU units must have different router IDs. In this case, give the physical address of the OMU unit as the value for the router ID parameter to avoid having two routers with the same router ID in the network. ZQKS:<unit type>, <unit index> :<router id>:
<rfc1583compatibility>:<spf delay>:<spf hold time>; 2. Configure OSPF area parameters (QKE)
Define the OSPF area (both backbone and other area) parameters of an OSPF router.
ZQKE:<unit type>,<unit index>:<area
identification>:<stub area>,[<stub area route cost>],<totally stubby area>;
The area identification specifies the area ID for a new OSPF. The area ID is entered as a dotted-quad. The area ID of 0.0.0.0 is reserved for the backbone. The IP network number of a subnetted network may be used as the area ID.
Note
The area parameters do not become effective (written into the configuration file) until the area has been attached to an interface.
3. Interrogate IP interfaces (QRI)
You must know the “interface identification” of the network interfaces when you are configuring OSPF interfaces.
ZQRI:<unit type>,<unit index>:<interface name>; If you do not give any parameter values, network interface information of all computer units of the network element is listed. 4. Configure OSPF interfaces (QKF)
ZQKF:<unit type>,<unit index> :<interface specification>:<area identification>:[<hello
interval>]:[<router dead interval>]:[<ospf cost>]:< [election priority>]:[<passive>]:[<authentication> | <password>];
5. Configure redistribute parameters (QKU)
ZQKU:<unit type>,<unit index>:<redistribute type and identification>:<metric>;
6. Configure network prefix, if required (QKH)
This command defines a network prefix in the OSPF area. Configuring the network prefix is optional to reduce the routing information exchange between different areas.
ZQKH:<unit type>,<unit index>:<area
identification>:ADD:<network prefix>:<network prefix mask length>:<network prefix restriction>; 7. Configure virtual link parameters, if required (QKV)
If there is an OSPF area which does not have a physical connection to the backbone area, use a virtual link to provide a logical path from the disconnected area to the backbone area. Virtual links have to be configured to both ends of the link. The QKV command has to be entered separately for both border routers using the virtual link. ZQKV:<unit type>,<unit index>:<router
identification>:<transit area>:<hello interval>: <router dead interval>:<authentication>;
The following example illustrates OSPF configuration for O&M DCN. The corresponding IP network interfaces have been configured before this procedure.
Figure 3. Example of OSPF configuration for RNC 10.1.1.5/28 10.1.1.2/28 (logical) RNC 10.1.1.10/28 Computer with Element Manager 10.1.1.2/32 unnumbered lines RAN BTS sites address range 10.1.3.0 10.1.1.1/28 10.3.1.1/24 IP over ATM virtual connection MGW AA0 10.3.1.2/32 O&M backbone
RAN O&M backbone address range 10.0.0.0/14 OSPF Area 0 NetAct 10.1.1.2/32 RAN BTS sites address range 10.1.2.0 RNC LAN 10.1.1.0/28 OMU 10.3.2.1/24 AA255 10.3.2.2/32 ESA12/ESA24 10.1.1.9/28 NEMU
This example presents the configuration of OSPF parameters in the OMU unit. The OMU unit in RNC is a border router. The unit has three interfaces: EL0, AA0, and AA255. The EL0 interface is attached to the backbone area through an Ethernet connection. The AA0 and AA255 interfaces are attached to the backbone area through an IP over ATM connection. 1. Obtain the numbers of the default routes of OMU-0 and OMU-1.
ZQKB:OMU;
The following output is displayed:
UNIT DESTINATION GATEWAY ADDRESS ROUTE TYPE NBR - - --- --
----OMU-0 DEFAULT ROUTE 10.1.1.1 LOG 1
2. Remove the default route from both units. ZQKA:1;
or
ZQKA::OMU,0;
3. Configure OSPF router parameters.
Configure the OSPF parameter data for the OMU with the router ID 10.1.1.2 and accept the default values for the remaining parameters. ZQKS:OMU,0:10.1.1.2;
ZQKS:OMU,1:10.1.1.2;
4. Configure OSPF area parameters.
Configure the backbone area information for the OMU. ZQKE:OMU,0:0.0.0.0;
ZQKE:OMU,1:0.0.0.0; 5. Inquire the attached interfaces.
ZQRI:OMU;
The following output is displayed:
IF ADM IF ADDR
UNIT NAME STATE MTU TYPE TYPE IP ADDRESS --- --- --- --- ---- ----
---OMU-0 AA0 UP 1500 L 10.3.1.2/32
->10.3.1.1
AA255 UP 1500 L 10.3.2.2/32
EL0 UP 1500 L 10.1.1.2/28 OMU-1 AA0 UP 1500 L (10.3.1.2)/32 ->10.3.1.1 AA255 UP 1500 L (10.3.2.2)/32 ->10.3.2.1 EL0 UP 1500 L (10.1.1.2)/28
6. Configure OSPF interfaces.
Configure an OSPF interface for the EL0, AA0, and AA255 interfaces.
The EL0 interface is attached to the backbone area through an Ethernet connection. Accept default values for the hello interval and router dead intervalparameters and set the ospf costto 10.
ZQKF:OMU,0:EL0:0.0.0.0:::10; ZQKF:OMU,1:EL0:0.0.0.0:::10;
The AA0 and AA255 interfaces are attached to the backbone area through an IPoA connection. Set thehello intervalto 30,router dead interval to 120, and ospf costto 100.
ZQKF:OMU,0:AA0:0.0.0.0:30:120:100; ZQKF:OMU,1:AA0:0.0.0.0:30:120:100; ZQKF:OMU,0:AA255:0.0.0.0:30:120:100; ZQKF:OMU,1:AA255:0.0.0.0:30:120:100; 7. Configure redistribute parameters.
Configure the OSPF to redistribute all valid static routes. ZQKU:OMU,0:ST=;
ZQKU:OMU,1:ST=;
3.4.2 Configuring static routes for the O&M connection to NetAct Purpose
Static routes are used when dynamic routing (OSPF in this case, see Creating OSPF configuration for O&M connection to NetAct) does not provide any useful functionality over the static routes. In other words, they are used when a simple static route works as efficient as a more
complicated dynamic routing. Static routes can be used with dynamic routing when creating a host route to a host that does not run dynamic routing.
Static routes are not used for the IP over ATM connections towards NetAct. Configure OSPF to OMU for both connections towards the NetAct router. For instructions, see Creating OSPF configuration for O&M connection to NetAct.
Before you start
Note
You can only configure one default route for each unit.
A logical route must use a logical address to reach its gateway, and it follows the logical address if a switchover occurs.
The static route configuration can be done via the IP plan interface from the NetAct. For further details on the IP plan interface see IP plan interface in document RNC Operation and Maintenance.
Steps
1. Configure the default static route
You do not need to specify the destination IP address for the default route.
Note
If you cannot use the default route, see the next step.
ZQKC:<unit type>,<unit index>::<gateway IP address>, [<local IP address>]:[<route type>];
Note
The parameterlocal IP address is only valid for local IP address based default route. For normal static routes, you do not need to give the local IP address. For more information about local IP address based default routes, refer to Creating and modifying static routes.
2. If the default route cannot be used Then
Delete the default static route for IP configuration a. Obtain the number of the static route to be deleted.
ZQKB:<unit type>,<unit index>;
b. Delete the route by identifying it by its route number or by its identification.
ZQKA:<route number>;
ZQKA::<unit type>,<unit index>;
3. If the default route cannot be used and you deleted it, or if you need to create more routes
Then
Create new static routes (QKC)
You create new static routes by using the QKC command. ZQKC:<unit type>,<unit index>:<destination IP address>,[<netmask length>]:<gateway IP address>: [<route type>];
Example Creating a default static route in RNC OMU The same default route is used for both OMU-0 and OMU-1. ZQKC:OMU,0::10.1.1.1,:LOG;
3.5
Configuring LAN switch
3.5.1 Configuring ESA12
Purpose
The purpose of this procedure is to configure the ESA12 Ethernet switch for O&M DCN.
Steps
1. Establish a telnet connection to ESA12
a. Enter the preconfigured IP address to ESA12 (the default IP address is 192.168.1.9).
telnet <ip address of ESA12> b. Enter your login ID and password.
The default password is empty. Therefore, press Enter to continue. If you have already changed your password during commissioning, enter your new password.
NOKIA ESA-12. Username:nokia Password:******** Expected outcome
The following options are displayed: ESA12 Main Menu 1. General Configuration 2. SNMP Configuration 3. Ports Configuration 4. Ports Status
5. Load Factory Defaults 6. Software Upgrade 7. Reset
8. Logout
2. Press 1 to select General Configuration from the menu
The General Configuration menu shows the current settings. Expected outcome
The General Configuration menu is printed on the command line. General Configuration MAC address 00 A0 12 0B 02 74 1. Agent IP Address : 192.168.001.009 2. Agent Netmask : 255.255.255.240 3. Default Gateway : 192.168.001.001 4. Supervisor/Terminal Password : 5. System Name : 6. Advanced Features 9. Main Menu
3. Press the number of the parameter you want to change Expected outcome
The selected parameter row with the current settings is printed below the menu.
5. Enter the new value for the parameter and press Enter Expected outcome
The General Configuration menu is printed on the command line. The menu shows the new settings.
Expected outcome
The session is interrupted immediately after you change the IP address. Change the IP address only after having changed all other parameters. Example Changing the default gateway in ESA12
This example shows how to change the default gateway in ESA12. 1. Establish a telnet connection to ESA12. In this example, the
password has not been changed yet. telnet 192.168.1.9
Username:nokia Password:
2. Press 1 to select General Configuration in the main menu.
3. Press 3 to select Default Gateway. The current address is displayed on the command line:
Default Gateway : 192.168.1.1
4. Use the backspace key to remove the current parameter value. 5. Enter the new value for the parameter and press Enter:
Default Gateway : 10.1.1.2
The new value is shown in the General Configuration menu: General Configuration MAC address 00 A0 12 0B 02 74 1. Agent IP Address : 192.168.001.009 2. Agent Netmask : 255.255.255.240 3. Default Gateway : 10.001.001.002 4. Supervisor/Terminal Password : 5. System Name : 6. Advanced Features 9. Main Menu
3.5.2 Configuring ESA24 Purpose
This procedure describes how to configure the ESA24 Ethernet/LAN switch.
Before you start
Before you start the configuration, check the following:
. The PC or laptop that you are using is connected to one of the
Ethernet ports of the ESA24 switch with an Ethernet cable.
. The ESA24 Ethernet switch is powered up (the LED on the front
panel of the switch is green). Steps
1. Connect to the IP address of ESA24 via Telnet
Note
If connection to the IP address of ESA24 is via Telnet, the IP address will change to the given address by the command IP address X.X.X. X/x.x and the Telnet connection will stop responding. The initial configuration has to be done by the serial connection. See ESA24 10/ 100 Mbit Ethernet Switch User Guide for the detailed information.
a. Start a Telnet session by selecting Start -> Run on the Windows Taskbar.
b. Connect to the IP address of ESA24: telnet <IP address of ESA24> c. PressEnter.
Expected outcome
The system prompts for a password: User Access Verification Password:
Enter the default password "nokia", or the new password if the password has been changed, and pressEnter.
Expected outcome
After successful login, the ESA24 prompt is displayed: ESA24>
3. Enable RSTP or MSTP for ESA24, if necessary
If you want to prevent cabling loops, enable the Rapid Spanning Tree Protocol (RSTP) or the Multiple Spanning Tree Protocol (MSTP) for ESA24.
a. Plan the STP role of each LAN switch in the L2 broadcast domain area.
b. Check that all LAN switches in the L2 broadcast domain area are running compatible STP versions.
c. Configure the bridge priority of the STP root switch and configure all the links directly connected to computer units as edge ports.
For more information, seeESA24 10/100 Mbit Ethernet Switch User Guide in PDF format in NOLS and Cable Lists and Use of ATM Links and LAN Connections in Site documents.
4. Change to a privileged mode in BiNOS
Enable the privileged mode in ESA24 operating system with the command
ESA24> enable
The privileged mode allows advanced viewing and configuration for the unit.
Note
The command prompt in privileged mode is the hash(#).
By default, the enablecommand does not ask for a password. It is possible to protect the administrator's rights with a password. See theESA24 10/100 Mbit Ethernet Switch User Guide for more information.
5. Change to configuration mode in BiNOS
Enable the configuration mode in ESA24 operating system with the command
ESA24#configure terminal
6. Set the IP address and netmask for ESA24
ESA24(config)#ip address <ip address>/<netmask> 7. Set the default gateway for ESA24
Delete the existing default route before add new route. ESA24(config)#no ip route 0.0.0.0/0
ESA24(config)#ip route <destination address>/ <destination network mask> <ip gateway address> 8. Enable DHCP, if necessary
ESA24(config)#ip address dhcp 9. Save the configuration
ESA24#write
Further information
To view information on the commands, enter? in the ESA24 command prompt. To view more information on the syntax of a specific command, enter<command> ?.
Example Configuring ESA24
This example shows how to configure ESA24.
1. Connect to the IP address of ESA24 via Telnet. a. Select Start -> Run on the Windows Taskbar. b. Connect to the IP address of ESA24:
telnet 192.168.1.9 c. PressEnter.
User Access Verification Password:
2. Enternokia and pressEnter to log in to ESA24. After successful log in, the ESA24 prompt is displayed: ESA24>
3. Change to privileged mode. ESA24> enable
4. Change to configuration mode. ESA24#configure terminal
5. Set the IP address and netmask for ESA24. ESA24(config)#ip address 192.168.0.5/28 6. Set the default gateway for ESA24.
ESA24(config)#ip route 0.0.0.0/0 192.168.0.1 7. Save the configuration.
ESA24#write
3.6
Configuring NEMU for DCN
3.6.1 Configuring NEMU for DCN
Purpose
To get NEMU fully integrated to the DCN, NEMU's default settings are configured to match current network environment.
Steps
1. Open the remote management application for NEMU
Use Communication profile Internet (TCP).
Give a NEMU computer name as a domain. For information security reasons, it is recommended to change the default user ID and/or password immediately after the first login.
For more information, see the instructions in NetOp remote access to NEMU and Configuring NetOp Guest in Network Element Management Unit.
2. Configure the DHCP server
Refer to the instructions in Configuring DHCP server in NEMU. 3. Configure the DNS client and server data
Refer to the instructions in Configuring DNS client and server in NEMU.
4. Configure NEMU to RNC
Refer to the instructions in Configuring NEMU to RNC. 5. Configure the RUIM feature in NEMU
Refer to the instructions in NemuRUIMConfiguration. 6. Configure the NTP server
Refer to the instructions in Configuring NTP services in NEMU. 7. Finalise the SQL server configuration
Refer to the instructions in Finalising SQL server configuration. 8. Define the IP address for NEMU according to the IP plan
Refer to the instructions in Configuring IP address for NEMU.
3.6.2 Configuring DHCP server in NEMU
Purpose
The DHCP server is used for configuring IP hosts automatically. The DHCP client in an IP host sends a broadcast query to the network, where a DHCP server receives it. The DHCP server answers the client by returning its IP address and other parameters. The returned values have been saved in the DHCP server's database.
With the RNC, DHCP is used to distribute IP parameters to IP devices that have been locally attached to the RNC. An example of such a device is a PC that has the Element Manager running.
The DHCP server is configured according to the IP plan. The DHCP server is needed because the PC in which the RNC Element Manager is running receives the IP parameters from the DHCP server of the NEMU. PC is not needed for configuring, but a standard DHCP can be used to configure the PC. However, this requires that the DHCP client is configured to the PC. See also the IETF's RFC 2136.
Steps
1. Open the DHCP manager of the managed NEMU
Select Start -> Programs -> Administrative Tools -> DHCP. 2. Add a new local management scope for NEMU
a. In the list of DHCP servers, select the DHCP server for which you want to create a new scope.
b. Select Action -> New Scope.
c. Enter the name of the scope. For example, Local Management.
d. Enter the IP addresses and masks for the new scope according to the IP plan.
Note
If you have static IP addresses configured on non-DHCP clients (for example, NEMU), you must use the IP address pool that does not contain those IP addresses. If you use an IP address pool that contains those addresses, you must configure the Exclusion Range list on DHCP Scope.
e. When the system asks you if you want to configure the DHCP options for this scope, answer No.
3. Delete the old local management scope
a. Under the server, select the old management scope (192.168.1.0).
b. Select Action -> Delete.
a. Under the server, select Server Options -> Action –> Configure Options.
b. Modify theRouter, DNS server, DNS Domain Name, and NTP Servers as required.
5. Activate the new local management scope
a. Under the server, select the new local management scope. b. Select Action -> Activate.
3.6.3 Configuring DNS client and server in NEMU
Purpose
This section describes how to create a DNS server to the NEMU server (Windows 2000), and how to configure primary and secondary servers. Creating the DNS server to the NEMU server does not require any sofware installations because the DNS server is installed in NEMU by default. Only a new DNS zone needs to be activated and created.
The Domain Name System (DNS) is a distributed database which maps hostnames and IP addresses. DNS servers are needed to enable the use of DNS names (for example,nemu.rnc1.netct.operator.com) instead of IP addresses. The DNS management server is the primary server (Master name server) of the zone. Servers in the network are secondary servers. This means that DNS information is managed in the DNS management server and the secondary servers automatically update their DNS databases from the management server. DNS servers in the network are authoritative for their zone, so they handle the DNS queries concerning the zone.
Figure 4. DNS architecture
The DNS management server is located in the Nokia NetAct. All the RNC NEMUs have a secondary DNS server, which updates its information from the DNS management server. The updating is normally controlled by the DNS management server (see the DNS Notify RFC 1996 by the IETF). If there is no Nokia NetAct, one NEMU is configured as the primary server, which the secondary servers use to update their information.
See also the IETF's documents RFC 1034 and 1035. The primary server is configured according to the IP plan.
ZONE transfers RNS DCN BTS BTS Secondary DNS server Nokia NetAct DNS management server DNS queries RNC Element Manager BTS Element Manager DNS queries
Steps
1. Configure the DNS client data
a. Select Start -> Settings -> Network and Dial-Up Connections.
b. Right-click Local Area Connection 3 and select Properties. c. On the General tab, select Internet Protocol (TCP/IP). d. Select Properties -> Advanced -> DNS.
e. Edit the address(es) of the DNS server(s) and set the search order, if necessary.
f. Click OK -> OK -> OK ->OK-> NO to apply the changes. g. Select Start -> Programs -> Administrative tools ->
Services.
h. Select Workstation Service. i. In Action menu select Start. j. Close Service window.
k. Select Start -> Settings -> Control Panel. l. Double-click the System icon.
m. On the Network Identification tab, select Properties. n. Enter the name of the computer and click More Write down the
original name of the computer as you will need it when running the SQL script. See Finalising SQL server configuration. o. Enter the primary DNS suffix.
p. Click OK -> OK -> OK -> OK to apply the changes. q. If computer name was changed, restart is required before
running sqlnamefix script. See Finalising SQL server configuration.
2. Start and check the DNS service
a. Select Start -> Settings -> Control Panel -> Administrative tools -> Services -> DNS Server.
b. Select Action -> Properties. c. Click Start.
d. Change the current status to 'Automatic'. 3. Start the DNS manager
Start the DNS manager from Start -> Programs -> Administrative tools -> DNS.
4. Add a new secondary or primary DNS zone to the server
a. In the list of DNS servers, select the server to which you want to add the new zone.
b. Select Action -> New Zone.
c. Select Standard secondary as the zone type. d. Select Forward lookup zone.
e. Enter the zone name according to the IP plan. The zone name is the end part of the computer name. For example, if the name of the NEMU isnemu.rnc1.nokia.com, the zone name is then rnc1.nokia.com.
f. Enter the IP address of the master server according to the IP plan. Zone information is refreshed when the secondary server has a connection to the master server.
g. Select Action -> Properties -> Forwarders.
h. Select Enable Forwarders and add the IP address of the master DNS server.
Or
To add a new primary DNS zone to the server:
a. In the list of DNS servers, select the server to which you want to add the new zone.
b. Select Action -> New Zone.
c. Select Standard primary as the zone type. d. Select Forward lookup zone.
e. Enter the zone name according to the IP plan. The zone name is the end part of the computer name. For example, if the name of the NEMU isnemu.rnc1.nokia.com, the zone name is then rnc1.nokia.com.
f. Accept the default zone file name. g. Repeat steps from b to f for each zone. 5. If you added a primary DNS zone to the server
Then
Create the DNS domains and hosts according to the IP plan a. In the list of the server's Forward lookup zones, select the
zone for which you want to create the DNS domain. b. Enter the name of the domain. For example, wbts1.
c. To create a new host, select Action -> New Host. Enter the name of the NEMU server, for example nemu, and the corresponding IP address.
d. Repeat steps b and c for each domain and host according to the IP plan.
6. Update the data files of the server
Select Action -> Update Server Data File.
7. Check that the DNS service configuration succeeded, if necessary
Use Nslookup to check that the configuration was successful.
Note
The Nslookup only works after the RNC integration is completed.
8. If a preconfigured IP address is used, delete the server a. In the list of DNS servers, select the server that has the
preconfigured IP address. b. Select Action -> Delete. Expected outcome
The DNS server should now be up and running.
3.6.4 Configuring NEMU to RNC
Purpose
The External Message Transfer (EMT) connection between NEMU and OMU requires that the Win2000 registry includes the IP address of OMU and the user ID and password of the network element. The user ID and password have been defined in the network element for the EMT connection.
The IP address of the NEMU and the FTP username and password also have to be defined for measurement bulk data transfer.
Any NEMU username and password can be used for NEMU FTP. The network element must have a user ID that the EMT, Telnet and FTP connections can use.
Before you start
. NEMU FTP user (for example NEMUFTP) . NWI3 user
Note that the NWI3 user must be the same as defined in the NetAct maintenance region to which the NEMU belongs. For instructions on creating user accounts, see Creating a new EM user inElement Manager Administration.
Tip
Create a new EM (Element Manager) user to the Users group.
The following table lists the NEMU registry variables used when configuring NEMU for RNC connection:
Table 6. RNC data in NEMU registry
Variable Data
Base identifier of RNC NE-RNC-<id>, where the <id> must be within the range 1 - 4095.
OMU's IP address As configured in Configuring IP stack in
OMU.
NEMU's IP address As configured in Checking IP address for
NEMU.
EMT UserName The NEMUAD user ID created in Creating
MMI user profiles and user IDs for remote connections to NetAct.
EMT Password The NEMUAD user password created in
Creating MMI user profiles and user IDs for remote connections to NetAct.
OMU FTP Username The NEMUAD user ID created in Creating
MMI user profiles and user IDs for remote connections to NetAct.
OMU FTP Password The NEMUAD user password created in
Creating MMI user profiles and user IDs for remote connections to NetAct.
OMU Telnet UserName The NEMUAD user ID created in Creating
MMI user profiles and user IDs for remote connections to NetAct.
OMU Telnet Password The NEMUAD user password created in
Creating MMI user profiles and user IDs for remote connections to NetAct.
Table 6. RNC data in NEMU registry (cont.)
Variable Data
NEMU FTP UserName The name of the service user with NEMU FTP Access (for example, NEMUFTP) as defined in Creating a new EM user in Element Manager Administration.
NEMU FTP Password The password for the NEMU FTP user as defined in Creating a new EM user in Element Manager Administration. NEMU Registration Account Username The NetAct NWI3 Access account
username.
NEMU Registration Account Password The NetAct NWI3 Access account password.
NEMU ID The host name of NEMU. For example: NEMU-2.
Network Management’s Registration IOR (RSIOR)
The Network Management's Registration IOR (RSIOR) in NetAct
Summary
To enable FTP connection from the NEMU to RNC, you must define OMU FTP user ID for the NEMU connection. To enable Telnet connection from the NEMU to RNC, you must define OMU Telnet user ID and password for the NEMU connection.
Steps
1. Open the Command Prompt from Start -> Run
2. Type NemuRegEdit, and click Enter
3. See further instructions in NemuRegEdit
3.6.5 NemuRegEdit
You can add network elements to NEMU by using the NemuRegEdit command line tool. The NEMU platform setup executes NemuRegEdit. The NemuRegEdit tool writes the entered information to the Windows register.
Note
If OMU FTP, OMU Telnet, or EMT passwords or username are changed on the managed element side, the same changes must also be done on the NEMU side.
Start NemuRegEdit
Start NemuRegEdit by entering the commandNemuRegEditin a command prompt window.
When NemuRegEdit is started, it shows the current configuration settings from NEMU and asks if you want to change them:
. Are the current managed network elements settings OK (Y/N)?
If the settings are correct, select Yes and press any key to continue. If something must be changed, select No. You can perform the following actions:
. To modify the default network element settings, select Modify
(M).
If you select modify (M), NemuRegEdit prompts you to enter the number of the network element:
Enter the number of network element you wish to modify and press <enter>, or <0> + <enter> to cancel?
After this, continue from BaseId of managed network element.
. If you do not want to change the current configuration settings,
select Cancel (C). Then continue from Printing the information of the default network element.
BaseId of managed network element
. Insert the baseId of the managed network element: NE-RNC-1
BaseID is a name for a network element, for example, NE-RNC-1. Type of managed network element
. Insert the type of managed network element: RNC
IP address of Network element
. Insert the logical IP address of the OMU unit of the managed
Printing network element information
Given network element [NE-RNC-1] information:
. baseID: NE-RNC-1 . typeID: RNC
. IP address: 192.168.12.1 . Is this correct (Y/N)?
Check the given information and select Y/N. Then enter 1 to select the default network element.
Printing the information of the default network element
You selected [NE-RNC-1] as the default network element:
. Type: RNC
. IP address: 192.168.12.1
. Default Network element set OK.
NemuRegEdit asks the following question:
. Are current managed network element settings OK? (Y/N) ?
If the settings are correct, select Y and press any key to continue. NemuRegEdit shows the current network element settings from NEMU and asks the following question:
. Are current NEMU settings OK (Y/N)?
If the settings are correct, select Yes and press any key to continue. If something must be changed, select No. NemuRegEdit then prompts you to modify the settings again.
IP address of NEMU
Enter the IP address of NEMU. Press ENTER if the current value is OK.
. NEMU IP address [STRING] current value: 10.12.17.123 . NEMU IP address [STRING] new value: 192.168.17.1
EMT UserName
Enter EMT UserName. Press ENTER if the current value is OK.
. EMT UserName [STRING] current value: SYSTEM . EMT UserName [STRING] new value: NEMUAD
EMT Password
Enter EMT Password and press ENTER.
. EMT Password [STRING] new value: ******
Give the current password for NEMUAD. OMU FTP UserName
Enter OMU FTP UserName. Press ENTER if the current value is OK.
. OMU FTP UserName [STRING] current value: SYSTEM . OMU FTP UserName [STRING] new value: NEMUAD
OMU FTP Password
Enter OMU FTP Password and press ENTER.
. OMU FTP Password [STRING] new value: ******
Give the current password for NEMUAD. OMU Telnet UserName
Enter OMU Telnet UserName. Press ENTER if the current value is OK.
. OMU Telnet UserName [STRING] current value: SYSTEM . OMU Telnet UserName [STRING] new value: NEMUAD
OMU Telnet Password
Enter OMU Telnet Password and press ENTER.
. OMU Telnet Password [STRING] new value: ******
NEMU FTP UserName
Enter NEMU FTP UserName. Press ENTER if the current value is OK.
. NEMU FTP UserName [STRING] current value: SYSTEM . NEMU FTP UserName [STRING] new value: NemuFTP
NEMU FTP Password
Enter NEMU FTP Password and press ENTER.
. NEMU FTP Password [STRING] new value: ******
Give the current password for NemuFTP. Registration Account UserName
Enter Registration Account UserName and press ENTER. When you press ENTER, the 'Value set OK' message is shown.
. Registration Account UserName [STRING] new value: neregn
Registration Account Password
Enter Registration Account Password and press ENTER.
. Registration Account Password [STRING] new value:******
Give the current password for neregn. NEMU ID
Enter NEMU ID. Press ENTER if the current value is OK.
. NEMU ID [STRING] current value: NEMU-1 . NEMU ID [STRING] new value: NEMU-2
Network Management's Registration IOR (RSIOR)
Enter Network Management's Registration IOR (RSIOR). If you do not want to set a value, press ENTER.
. Network Management's Registration IOR new value:
IOR:12345678910111213141516
