RNC Integration Cookbook RNC01CRP

RNC INTEGRATION COOKBOOK

1 (7)

Ana Barros Version 2 OSSGuilherme CamposJyri Hamalainen 18/03/2008

RNC Integration cookbook

1- ADDING RNC AND NEMU/OMS TO THE DNS

#NAMESURF####################################################add rnc and ran forward zone

RAN zone: ran.netact.oi.com

RNC zone:rnc<system_id>.ran.netact.oi.com

OBS: -System_id of OMS in format NE-RNC-<system_id> -Use same data, as follows, for both zones:

[email protected] 20 minsTTL 1 hourrc01scs.r01.netact.oi.comrc01dbs.r01.netact.oi.com


2 (7)


##############################################################add omu and oms hosts to rnc90.ran.netact.oi.com forward zone:

10.126.92.225 rnc-212302-omu.rnc90.ran.netact.oi.com10.126.92.228 rnc-212302-oms.rnc90.ran.netact.oi.com##############################################################

Add new alias RNC01CIN.rcn90 maped as rnc-212302-omu.rnc90.ran.netact.oi.com##############################################################Add reverse zone, use same data as for forward zones:

92.126.10.in-addr.arpa

Add new hosts omu and oms to reverse zone:

225.92.126.10.IN-ADDR.ARPA rnc-212302-omu.rnc90.ran.netact.oi.com228.92.126.10.IN-ADDR.ARPA rnc-212302-oms.rnc90.ran.netact.oi.com##############################################################

Configure Bind, using same configuration for scs and dbs:

Backup and add following zones to named.conf:

zone "rnc90.ran.netact.oi.com."{ type slave; masters port 8054 { 10.21.4.79 ; } ;file "db.rnc90.ran.netact.oi.com" ;} ;

zone "ran.netact.oi.com."{ #APENAS 1X NO ARQUIVO type slave; masters port 8054 { 10.21.4.79 ; } ;file "db.ran.netact.oi.com" ;} ;

zone "92.126.10.in-addr.arpa." { type slave; masters port 8054 { 10.21.4.79 ; };file "db.95.126.10";};


3 (7)


rndc reload

Make a backup and editcf /etc/resolv.conf to add ran.netact.oi.com parent zone, like:

search r01.netact… “ran.netact.oi.com” nameserver <IP1>nameserver <IP2>retry 3retrans 1000

2. CONFIGURE MR SERVICE USERS IN NETACT

Examples of a MR service user’s username

Service Type and profileConnected to NetAct user group

MR

applau Programmatic PC Access sysop MR-NWI3applau Programmatic PC Access sysop MR-RNC (definitive MR)ftpuse FTP Unix Access ftpuse MR-NWI3omsFtpUser FTP Unix Access ftpuse MR-RNC (definitive MR)Nemuadmin NWI3 Access sysop MR-NWI3Nemuadmin NWI3 Access sysop MR-RNC (definitive MR)sysop1 Default Access sysop MR-NWI3sysop1 Default Access sysop MR-RNC (definitive MR)

OBS: omsFtpUser must have same password as in RNC OMS.

3. CONFIGURE OMS

From GUIS, open internet explorer and go to site https://<OMS IP> and click on link: Download Application Launcher Client.

Run Launcher Client. Fill Network Element with OMS ip address and use Nemuadmin/nemuuser to login.

Open the Parameter tool

a) Go to fsClusterId=ClusterRoot / fsFragmentId=NWI3 / fsFragmentId=mediator. Select item fsnwi3N3CFId=1, and edit the required attributes and their values (Double-click the current value to modify)- NetAct’s Registration Service IOR (don’t forget to begin with “IOR:…”)- NetAct’s Registration Service username: Nemuadmin- NetAct’s Registration Service password: nemuuserChange parameter fsnwi3takeIntoUseNext: true


4 (7)


b) Go to fsClusterId=ClusterRoot / fsFragmentId=AlarmMgmt / fsFragmentId=AlarmProcessors / fsAlarmProcessorId=AlarmProcessor1. Select fsAlarmProcessorConfigurationId=Default and edit the required attributes and their values:- Edit the value of fsHeartbeatInterval: '0'.

c) Restart the NWI3Adapter recovery group by openning Putty ssh to OMS ip address. Log as Nemuadmin/nemuuser and run following command in linux shell:fshascli –r /NWI3Adapter

4. ADDING THE RNC TO A NETWORK VIEW

Inicially put RNC to NWI3 MR. After the automatic upload put RNC and all children to Definitive MR-RNC.

RNC ID: The number taken from the System ID (NE-RNC-<System id>).

This value must be between 1-4095.

Name: Usually, the name is an alias of the RNC. The value will appear in the Top-Level User Interface above the RNC icon. For example: RNC2

Address: The physical address where the RNC is located.

For example: Building2, Room 1006

Vendor: Nokia

Version: The RN version information is interrogated from the RNC.

IP Address: The IP address of RNC OMU.

Hostname: FQDN of RNC's OMU unit. Should be filled automatically.

5. CONFIGURING CONNECTION SERVER SOFTWARE

Make a backup copy and editcf $NMSCONFDIR/common/cnxdcnmx.cf, adding following lines:

######################################################## RNC01CIN - START ############################################################ Arc definitions(arcName "A_SSRV_TELNET_TCPIP_RNC01CIN" (maxConns "18")


5 (7)


(address "10.126.92.225") >>> RNC OMU IP ADDRESS (connChannel "telnet") (loginSeqFileName "cnxlogindx2mx.cf") (logoutSeqFileName "cnxlogoutdxmx.cf"))# Route definitions(routeName "R_SSRV_TELNET_TCPIP_RNC01CIN" (arcs "A_SSRV_TELNET_TCPIP_RNC01CIN") (host "rc01cre1.r01.netact.oi.com") #>>> osscore1 hostname (port "7715") (checkScript "") (commandLine "cnxdx200vtxmx.cf"))#Node definitions(id "504063" #>> int id (tecName "RNC01CIN") #>> RNC Name (maxMMLConns "6") (maxFileConns "6") (maxSpontConns "6") (totalMaxConns "18") (edMMLConns "Y") (edFileConns "Y") (edSpontConns "Y") (edAllConns "Y") (edMMLLog "N") (edFileLog "N") (edSpontLog "N") (edAllLog "Y") (users "" (groups "sysop,…" #>>>unix groups (connTypes "MML_HUMAN,MML_MACHINE" (routes "R_SSRV_TELNET_TCPIP_RNC01CIN") #>> RNC Name ) ) ))######################################################## RNC01CIN - END ###############################################################################

Re-read the configuration file by entering:

omc% $OMCROOT/bin/cnxreconfigmx.perl

6. CREATE NECESSARY USERS IN RNC OMU

Create the PROFILE NUPADM: ZIAA:NUPADM:ALL=250:VTIME=FOREVER,UNIQUE=YES:TLIMIT=15:FTP=W;

Create the USER NUPADM and give the proper password: ZIAH:NUPADM:NUPADM;


6 (7)


Create the PROFILE NEMUAD: ZIAA:NEMUAD:ALL=250:VTIME=FOREVER,UNIQUE=YES:TLIMIT=15:FTP=W;

Create the USER NEMUAD and give the proper password: ZIAH:NEMUAD:NEMUAD;

Updating the MR service users in the network

Go to Utils / System Management / Service User Management. Click File / Update Network...

7. ADD WBTS’S TO DNS

- Add each WBTS to DNS RNC forward zone only.

- Fill WBTS information in Network Editor with ip.

- Fill WBTS information in Network Editor with hostname. That will not be updated automatically!

8. PUT RNC AND ALL CHILDREN TO DEFINITIVE MR

Open Network Editor and change RNC to MR-RNC. Don´t forget to mark “update all children” button.

9. OMU DNS SETTINGS

ZQRK:10.21.4.35,10.21.4.37,,"RNC90.RAN.NETACT.OI.COM",;

RNC IPA2800 2008-03-18 11:42:58

CONFIGURED DNS PARAMETERS

PRIMARY DNS SERVER..: 10.21.4.35SECONDARY DNS SERVER: 10.21.4.37

DOMAIN NAME.........: RNC90.RAN.NETACT.OI.COM

RESOLVER CACHE IS IN USEROUND ROBIN IS IN USE

COMMAND EXECUTED

TCP/IP STACK DATA HANDLING COMMAND <QR_>


7 (7)


<

10.OMS DNS SETTINGS:

Open linux ssh through putty.

# cp -p /etc/clusterdns.conf /etc/clusterdns.conf.18032008[root@CLA-0(RNC-90) /root]# cd /etc[root@CLA-0(RNC-90) /etc]# vi clusterdns.conf[root@CLA-0(RNC-90) /etc]# vi clusterdns.conf[root@CLA-0(RNC-90) /etc]#

# diff /etc/clusterdns.conf /etc/clusterdns.conf.1803200815c15< forwarders { 10.21.4.35; 10.21.4.37;};---> forwarders { ; };[root@CLA-0(RNC-90) /etc]#

# fsdistribute /etc/clusterdns.conf[root@CLA-0(RNC-90) /etc]# fshascli -r /ClusterDNSThe request will terminate all the processes running in /ClusterDNS.Are you sure you want to proceed? [y/n] y/ClusterDNS is restarted successfully

11. VERIFY INTEGRATION

RNC Integration Cookbook RNC01CRP

Documents

Transcript of RNC Integration Cookbook RNC01CRP