You are on page 1of 7

RN3.

0 Install OMS
Index

INTRODUCTION..........................................................................................................................................2 OMS BOOT UP AND INSTALL..............................................................................................................................3

Introduction
A. Upgrading from NEMU to OMS Using USB Stick.pdf (DN70463149 Issue 1-0 en 07/01/2008) Note: We have selected the USB Stick method for OMS installation because of the simplicity and advantages of this method in comparison with FEWS one. All this information can be found in NOLS: Care->Software Delivery->WCDMA RNC>RN3.0.

OMS boot up and install

ESTIMATION TIME

1 hour 1,5 hours


1-B

Connect the screen and keyboard to NEMU In parallel with 1-A or 1-C Connect the USB stick to the first USB ports of NEMU. Reboot the NEMU by pressing the reset button. Wait that prompt Press DEL to enter Setup appears and DEL. When the Setup menu appears, select the boot command, Then change the boot order: Select Hard disk, select your USB memory stick, press the + to move the device upper in boot order. Save the bios settings (f10).

Note:If you disconnect and reconnect the USB memory stick to Nemu, you will have to perform the previous operation again.

Installing the OMS using the USB stick


Purpose
To install the OMS by using the USB stick.

Before you start


Log is written to /var/log/USB_Complete_Install--<timestamp>.log.

Steps

1. Change directory and run CompleteOMS_USBInstallation.sh.


Run the following commands: # cd /opt/Nokia/SS_OMSINST/usb/ # ./CompleteOMS_USBInstallation.sh When you are running the commands, follow the instructions that are displayed on the screen. a. If the OMS has only one ethernet port connected (that is, eth0), you are prompted to answer the following questions to disable alarms for eth1:

OMS binds both eth0 and eth1 to single bond in order to gain network redundancy. However if OMS is connected only with single network cable, alarms are

raised. Do you want to disable alarm monitoring for eth1? Do you want to disable alarm monitoring for eth1? answer 1 to disable eth1 alarms and restart FSNodeOSServer answer 2 to enable eth1 alarms and restart FSNodeOSServer answer 3 to exit
Answer 1 if you are not going to use eth1, otherwise answer 2. b. You are prompted to enter the IP addresses:

c. OMS IP: d. NETMASK: (in bits e.g. 24) e. DNS IP: f. NTP IP: DEFAULT GATEWAY: Para palma3
NEMU IP address: Network mask length: Default Gateway (Gestin): RNC Id: 10.217.192.23 255.255.252.0 / - poner 28 10.217.192.17 307 Tip Give an IP address as an answer to every IP question, because the IP address is mandatory. If you do not give all requested IP addresses, the installation fails. g. You are prompted to enter OMU usernames and passwords:

h.

Type OMU Type OMU Type OMU Type OMU Type OMU Type OMU Type OMU Telnet

i. j. k. l. m.

IP address EMT username [SYSTEM]: EMT password [SYSTEM]: FTP username [SYSTEM]: FTP password [SYSTEM]: Telnet username [SYSTEM]: password [SYSTEM]:

n. You are prompted to enter the id number of the RNC as the cluster id:

Give new RNC id number <1-4095>: 307


o. You are prompted to enter the time zone. Depending on your first choice, a list countries appears.

p. Please identify a location so that time zone rules can be set correctly. q. Please select a continent or ocean. r. 1) Africa 2) Americas s. 3) Antarctica t. 4) Arctic Ocean u. 5) Asia v. 6) Atlantic Ocean w. 7) Australia

x. 8) Europe y. 9) Indian Ocean z. 10) Pacific Ocean 11) none - I want to specify the time zone using the Posix TZ format.
aa. You are prompted to change local passwords:

bb. cc.

Change root password -> rncNOKIA Change users nokfsoperator password -> rncNOKIA Change users nokfssysemoperatorfallback password -> rncNOKIA dd.
Running these commands takes about 10 minutes. OMS is rebooted automatically, and is available after reboot.

Configuring the RNC object for the first time


Purpose
When the RNC RNW Object Browser is first taken into use after commissioning, the very first task is to configure the RNC by setting the required parameters. This is done because the RNC object is the topmost object in the hierarchy, and so it has to be created first. Please note that the RNC RNW Object Browser provides online help to assist you in carrying out the tasks. You can access the online help by clicking the Help button in the RNC dialogue. Note If this initial phase of the configuration is not successful, the user cannot proceed with the rest of the configuration tasks.

Before you start


OMU and OMS have to be configured to the customer O&M network. For more information, see Configuring IP for O&M backbone (RNC - NetAct) .

Steps
Expand/collapse all

1.

Open the RNC RNW Object Browser. A dialogue appears indicating that the RNC has not been configured.

2.

Click OK. The RNC dialogue appears.

3.

Configure the RNC. Enter values at least for the obligatory parameters marked with yellow. For more information on parameters, see WCDMA RAN Parameter Dictionary.

Note You cannot change the value of RNC identifier afterwards.

4. Click OK to confirm operation.

Expected outcome
The general parameters of the RNC have been set.

Unexpected outcome
If in any phase of the configuration an error occurs, you must acknowledge it by clicking OK. The parameter window where the error occurred is displayed, and you can either modify the parameters and try again or cancel the operation.

Configuring Nokia NetAct interface with OMS


Purpose
Note This procedure has to be executed before CUAA (RUIM) configuration.

This procedure informs you to configure the connection from OMS to Nokia NetAct.

Steps
Expand/collapse all 1. Open the Parameter tool via the Application Launcher

2.

Select entry to default instances of: o fsClusterId=ClusterRoot

o o o

fsFragmentId=NWI3 fsFragmentId=mediator fsnwi3N3CFId=1

Then initialize the attributes below.

3.

Edit the required attributes and their values: o NetActs Registration Service IOR (RSIOR) fsnwi3registrationServiceIOR field o NetActs Registration Service username fsnwi3initialRegistrationUsername field o NetActs Registration Service password fsnwi3initialRegistrationPassword field (The default password is neregn, but it should be changed for security reasons. o Change the value of the boolean parameter fsnwi3takeIntoUseNext=true, which means that this configuration parameter set will be taken into use during the next (re)start or re-registration Select entry to default instances of:

4.

o o o o o

fsClusterId=ClusterRoot fsFragmentId=AlarmMgmt fsFragmentId=AlarmProcessors fsAlarmProcessorId=AlarmProcessor1 fsAlarmProcessorConfigurationId=Default

Check that value of fsHeartbeatInterval is '0'.

5.

Take the new parameter values into use NWI3 Adapter takes the new parameter values into use within a re-registration period and registers itself to NetAct (the default re-registration is 60 minutes). The re-registration depends on the situation and the parameters in the LDAP server. The new parameters can be taken into use immediately by restarting the NWI3Adapter recovery group. Restart the recovery group by entering the following command: Entrar como root y ejecutar desde linea de comandos

fshascli r /NWI3Adapter

You might also like