gprs config in omcr

GSM

GPRS configuration on OMC-R

Reference : DS/OMC/APP/0039 Version : 01.09 / EN Date : 06/07/2001

Ext. ref. : none Type : PROC Product : OMC-R Cat : E Status : A

Author : C Marmignon Documentalist : A.-M. Le Berre Approved by : Y. Evain Quality manager :

Abstract / Comments :

Distribution lists : Refer to lists 2 & 4 defined in the SQ/DS/APP/0004 document.

This confidential document is the property of NORTEL MATRA CELLULAR and may not be copied or circulated without permission Ce document confidentiel est la propriété de NORTEL MATRA CELLULAR et ne peut être reproduit ou communiqué sans autorisation


GPRS configuration on OMC-R Page I.2

DS/OMC/APP/0039 01.09 / EN 06/07/2001

DOCUMENT AMENDMENTS

VERSION DATE COMMENTS AUTHOR

01.01 / EN 10/02/2000 Creation F. Borel

01.02 / EN 06/04/00 Sheet “OMC-R restart” : Trouble shooting addition &

clearer explanation about restart in dual or single-

server configuration

Modifications in Scope

MC. Corbeaux

F. Borel

01.03 / EN 17/05/2000 Modifications for PCU-OAM install introduction F. Borel

01.04 / EN 13/07/00 SR 30326912 fix F. Borel

01.05 / EN 28/07/00 SR 30322540 fix :The definition of NMS, GPRS and

MDP have been added.

E. Mesbahi

01.06 / EN 02/08/00 SR 30328477 fix F. Borel

01.07 / EN 02/09/2000 SR 30328477, 30331094, 30328181 Fixed

omc_confugure is missing after step 5

TL Benmebarek

01.08 / EN 24/10/2000 SR 30137125 Fixed JF Poignant

01.09 / EN 06/07/2001 SR 30363429 fixed C Marmignon

GSM

Reference : DS/OMC/APP/0039 Version : 01.09 / EN Date : 06/07/2001

GPRS CONFIGURATION ON OMC-R



GPRS configuration on OMC-R Page 2/23

DS/OMC/APP/0039 01.09 / EN 06/07/2001

T A B L E O F C O N T E N T S

1. INTRODUCTION.......................................................................................................4

1.1 OBJECT .........................................................................................................4

1.2 SCOPE...........................................................................................................4

2. RELATED DOCUMENTS .........................................................................................4

2.1 APPLICABLE DOCUMENTS..........................................................................4

2.2 REFERENCE DOCUMENTS .........................................................................4

3. ABBREVIATIONS & DEFINITIONS .........................................................................4

3.1 ABBREVIATIONS...........................................................................................4

3.2 DEFINITIONS.................................................................................................6

3.3 TYPOGRAPHIC CONVENTIONS ..................................................................7

3.3.1 GENERAL CONVENTIONS...............................................................7 3.3.2 INTERACTIVE TERMINAL SESSIONS.............................................7 3.3.3 INTERACTIVE GRAPHIC SESSIONS...............................................8

3.4 SEQUENCE TABLE CONVENTION ..............................................................8

4. GENERAL DESCRIPTION .....................................................................................10

4.1 PLEASE READ CAREFULLY.......................................................................10

4.2 PREREQUISITES ........................................................................................10

4.2.1 HARDWARE CONFIGURATION.....................................................10 4.2.2 SOFTWARE CONFIGURATION......................................................10

4.3 RESOURCES...............................................................................................10

4.3.1 HUMAN RESOURCES ....................................................................10

5. PRELIMINARIES ....................................................................................................10

6. OPERATION DETAILED DESCRIPTION...............................................................12

6.1 UPGRADING THE SDO HARDWARE .........................................................12

6.2 PCU OAM INSTALLATION ..........................................................................12

6.3 GPRS CONFIGURATION ON OMC-R SERVERS.......................................12

7. POST OPERATIONS..............................................................................................13

8. SHEETS..................................................................................................................14

HOW TO…..................................................................................................................15



DS/OMC/APP/0039 01.09 / EN 06/07/2001

AUTOMATIC OMC-R STARTUP CONFIGURATION..................................................17 APPLICATION CONFIGURATION..............................................................................18 EXIT AND CLEAN.......................................................................................................19 OMC-R CONFIGURATION UPDATE FOR GPRS ......................................................20 OMC-R STOP .............................................................................................................21 OMC-R RESTART ......................................................................................................22 Z End of DOCUMENT Y ...........................................................................................23



DS/OMC/APP/0039 01.09 / EN 06/07/2001

1. INTRODUCTION 1.1 OBJECT This procedure describes how to configure the GPRS functionality on an OMC-R already operational.

1.2 SCOPE It applies from V12.4 or V13 releases, on OMC-R servers, SDO and PCU OAM workstations.

2. RELATED DOCUMENTS 2.1 APPLICABLE DOCUMENTS

[A1] DS/OMC/APP/0001 OMC-R OEM equipment installation procedure

[A2] DS/OMC/APP/0007 OMC-R hardware upgrade procedure

[A3] DS/OMC/APP/0003 OMC-R software installation procedure

[A4] PE/OMC/DD/0182 SIE OMC-R: OMC Administration [A5] DS/OMC/APP/0019 OMC-R customization parameter

notebook

2.2 REFERENCE DOCUMENTS

[R1] DS/BSS/APP/0008 BSS Network Upgrade high level Procedure

3. ABBREVIATIONS & DEFINITIONS 3.1 ABBREVIATIONS

A5000 Sun™ StorEdge™ A5000 BDA BSC application database BDE OMC-R operations database BSC Base Station Controller BSS Base-station Sub-System BTS Base Transceiver Station CDROM Compact Disk Read Only Memory CPU Central Processing Unit DAT Digital Audio Tape (magnetic cartridge) DCE Data Communication Equipment



DS/OMC/APP/0039 01.09 / EN 06/07/2001

DDTI Dual Digital Trunk Interface DNS Domain Name Server DTE Data Terminal Equipment EFD Event Forwarding Discriminator EFT “Ensemble de Fichiers Transférables” (set of downloadable

files) E4XXX Sun™ Enterprise™ server family (E4002, E4500) FPRX Front Processor for Reception Gb Gigabyte GMT Greenwich Mean Time GPRS General Packet Radio Service HSI High Speed Interface LAN Local Area Network MD Mediation Device MDP Management Data Provider MMI Man Machine Interface NIS Network Information Service NMS Network Management System NVRAM Non Volatile Random Access Memory NVSIMM Non Volatile Single In-line Memory Module OBP Open Boot Prom (processor monitor of Sun™ machines) OEM Original Equipment Manufacturer OEME Original Equipment Manufacturer Equipment OMC-R Operation and Maintenance Centre - Radio part OMN Operation and Maintenance Network (BSC-MD Link, also

known as the "REM" link) OS Operating System PCM Pulse Code Modulation PROM Programmable Read Only Memory PSDN Public Switched Data Network RAM Random Access Memory RARP Reverse Address Resolution Protocol ROM Read Only Memory ROT Remote Operation Terminal SCSI Small Computer Standard Interface SDO "Serveur de Données de l’OMC-R" (OMC-R Data Server) SDS Solstice DiskSuit™ SS1000 Sun™ SPARCserver™ 1000 SSA Sun™ SPARCstorage™ Array STATX Role of an OMC-R workstation acting as X terminal server TCU TransCoder Unit

UTC Universal Time Coordinates



DS/OMC/APP/0039 01.09 / EN 06/07/2001

3.2 DEFINITIONS Active (respectively passive) server: term that designates the actual active (respectively passive) server on an operational OMC-R, in case of dual servers configuration.

Data mirroring : process whereby the data is updated on OMC-R server(s) disks.

Disks array device: external storage device attached to OMC-R E4xxx OMC-R server(s). OMC-R disks array device may be either SSA device (on E4002 OMC-R server(s)) or A5000 device (on E4002/E4500 OMC-R server(s)).

DNS: service, which allows sharing information about IP addresses and the associated hostnames between a set of machines, on a network. Two parts are implied in this service: the DNS clients and the DNS server(s).

DNS client: machine, which asks the DNS server for resolving IP addresses.

DNS server: machine, which centralises information about IP addresses and the associated hostnames. It responds to the requests sent by DNS clients, which want to resolve hostnames. There are two kinds of DNS servers, the primary server, which is mandatory and one or more secondary servers which are optional.

EFT: on the OMC-R, an EFT is a collection of files, corresponding to the downloadable part of a sub-system software (BSC, BCF, ..).

Ethernet address: LAN hardware address of equipment, also called MAC address.

Master DAT: DAT, which contains all the software and the tools to install or to upgrade an OMC-R server or an OMC-R workstation:

- Installation and upgrade tools - OEM software and patches - OEME software and patches

MDP Management Data Provider

NMS Network Management System

OEM software: trade software such as Sun™ Solaris™ operating system, SUNLink®, Sybase®, etc.

OMC-R : the OMC-R software installed on an OMC-R server or an OMC-R workstation.

OMC-R machine: a machine running the OMC-R software (an OMC-R server or an OMC-R workstation).

PCUOAM : workstation which hosts at least OMC-R, NMS, MDP.

Preferential active (respectively passive) server: term that designates the server administratively declared as active (respectively passive). The preferential passive server can become the operational active server after a switchover on an operational OMC-R.

SDO: application that allows the user to interface in a pre-defined ASCII format with configuration management, performance management and fault management.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

Source server: term that designates the old server to be upgraded.

System under OBP: system under control of processor monitor. The operating system is not running, as after a shutdown (init 0 ).

Target server: term that designates the new server to be installed.

3.3 TYPOGRAPHIC CONVENTIONS 3.3.1 GENERAL CONVENTIONS

Words in italic style (italic) means a parameter to substitute by its value. The following syntax indicates on which machine the actions should be run:

)) ON A LOCAL OMC-R WORKSTATION:

Conditional commands are indicated with the following syntax:

For all the unlocked bscMdInterface objects: { ..... }

3.3.2 INTERACTIVE TERMINAL SESSIONS

An interactive session on a terminal can be obtained using two methods: � Choosing the "Access to Unix" option of the background

menu on the server or the station, � Open a remote connection to the server or the station from a

shell window on any other machine, using the telnet or rlogin command.

An interactive session on a terminal (line terminal or Command Tool window) is described with the following syntax:

Convention used Meaning Courier New All characters of a terminal session are in Courier New font. Bold The lines, commands, or parameters entered with the keyboard

are in bold style. Italic A variable output display is in italic style. Words in italic have to

be substituted by real values. italic-bold An input parameter, which should be substituted by its value, is in

italic and bold style. �� The ENTER key has to be pressed. [STOP],[a] The STOP and a keys have to be pressed simultaneously.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

.......... A group of dots replace a certain number of lines. � A command line is truncated and continues on the next line. % or ( user ) % The C shell prompt $ or ( user ) $ The Bourne and Korn shell prompt # or (root) # The root super-user prompt in any shell

Terminal session sample:

Under omc login:

/ (omc) % cd my_directory �� my_directory (omc) % ls �� a.out i_am_a_short_file_with_a_really_i_mean_really_no_but_unbelievably_ � long_name ........ toto.o my_directory (omc) % vi my_file �� my_directory (omc) %

The typographic conventions of a terminal session are also used to display the content of a UNIX file.

3.3.3 INTERACTIVE GRAPHIC SESSIONS

The graphic interactive commands are described with the following syntax:

Convention used Meaning GOTO « Title » Go to the window named "Title" SELECT « Save - OK » Click with the mouse on the buttons or options

named "Save", then "OK". SELECT_OBJ « omc » Select the object « omc » SET State = locked T2 = 30s

Enter with the keyboard the values of the parameters

CLOSE « Title » Close the window named "Title"

3.4 SEQUENCE TABLE CONVENTION For each major step of the procedure, a sequence table lists the operation steps to perform. Each operation step is described completely in the sheet referenced by its page number. A sheet may have to be executed at different stages of the procedure and in different contexts; in that case, a set of input parameters for the sheet indicates the context.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

A sequence table provides for each operation step the time required to perform it. The time indicated for an operation step corresponds to a maximum network configuration, and may change depending on the hardware configuration. Since the sheets are not in the execution order and can be executed several times, the sequence tables should be considered as the reference guide during the procedure. A sequence table has the following format: Step Operation description (Total 315 mn) mn Sheet

page OK / NOK

NOK step

Input Parameters

STATUS COMMENT

S1 Description of the operation 1 30 12 OK F1

Parameter1 = value Parameter2 : explanations



Parameter1 = value

Each time an operation has been performed, the operator should note the result in the « OK / NOK » column.

� If the result is « OK », the next operation is described in the following line of the table,

� If the result is « NOK », the procedure can not be continued. The next operation could be indicated in the last column of the current line and is either a fallback or a trouble-shooting step. In case of a fallback (indicated with a "F"), the fallback procedure should be started at the specified step.

Result of the operation, filled in by the operator

Fallback or trouble shooting step to execute (ifany), if the result of the operation is NOK

Sheet page number

Maximum elapsed time of the operation step with a maximum configuration

Comment indicating the status at this stage of the major step

Name and value of input para-meters of the sheet (optional or

« none » for no argument)



DS/OMC/APP/0039 01.09 / EN 06/07/2001

4. GENERAL DESCRIPTION 4.1 PLEASE READ CAREFULLY The utmost care was taken to prevent any unexpected event to occur during this procedure. However, nothing on earth is 100% secure. Thus, if you feel you have to cope with a problem or a situation the procedure does not explicitly or accurately deal with, call for help (according to your level of expertise).

Before executing this procedure, ask your support for any special actions (workaround, patch...) to perform before and after the procedure.

4.2 PREREQUISITES 4.2.1 HARDWARE CONFIGURATION

The hardware configuration of the OMC-R machines must conform to the GPRS hardware requirements, as described in the [R1] document.

4.2.2 SOFTWARE CONFIGURATION

The OMC-R software must be running at least in V12.4 release on the OMC-R configuration. If the current OMC-R software is running in a previous release, it is asked to upgrade it to V12.4 release at least.

4.3 RESOURCES 4.3.1 HUMAN RESOURCES

This procedure can be performed by one person. The operator should be confident with the OMC-R.

5. PRELIMINARIES This major step is the first one for any operation described in this document.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

Step Operation description Sheet page

OK / NOK

NOK step

Input Parameters

BEGINNING OF PRELIMINARIES

S1 How to… 15 no

END OF PRELIMINARIES



DS/OMC/APP/0039 01.09 / EN 06/07/2001

6. OPERATION DETAILED DESCRIPTION The following sections describe how to configure the GPRS functionality on an already operational OMC-R.

6.1 UPGRADING THE SDO HARDWARE This section is to be applied if the SDO hardware is not compliant with GPRS hardware requirements. Step Operation description Sheet

page OK / NOK

NOK step

Input Parameters

THE OMC-R IS OPERATIONAL AND RUNNING FROM V12.4 RELEASE

S1 Upgrade the SDO hardware in accordance with the requirements of [R1]

[A2]

THE HARDWARE IS UPGRADED ON THE OMC-R

6.2 PCU OAM INSTALLATION The PCU OAM server can be installed before the GPRS configuration on the OMC-R, or after.

Install the PCU OAM server by applying the following major-step. Step Operation description (Total 0 mn) mn Sheet

page OK / NOK

NOK step

Input Parameters

S2 Install the PCU OAM server Install the hardware: Install the software:

[A1] [A3]

THE PCU OAM IS INSTALLED AND REACHABLE FROM THE OMC-R

6.3 GPRS CONFIGURATION ON OMC-R SERVERS

This section explains how to configure the GPRS function on the OMC-R.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

Step Operation description (Total 19 mn) mn Sheet page

OK / NOK

NOK step

Input Parameters

THE OMC-R IS OPERATIONAL FROM V12.4 RELEASE THE OMC-R HARDWARE CONFORMS TO GPRS REQUIREMENTS

S3 If not already done , stop the OMC-R application on each server, from the OMC-R preferential active server

3 21 no

S4 Modify the OMC-R configuration files on the OMC-R preferential active server, to configure the GPRS functionality.

5 20 no

S5 If not already done , declare the PCU OAM (even if not already installed ) on all OMC-R machines; for that, apply the 7.1§ of the [A3] document

5 [A3] no

S6 Reconfigure each OMC-R machine, from the OMC-R preferential active server

5 18 no

args = -A

S7 Start the OMC-R on each server, from the OMC-R preferential active server

1 22 no

args = -S

THE GPRS FUNCTION IS ACTIVATED ON OMC-R

7. POST OPERATIONS This major step is the last one for any machine concerned in this document.

Step Operation description Sheet

page OK / NOK

Input Parameters

THE GPRS FUNCTION IS ACTIVATED ON THE OMC-R

S8 Exit and clean 19

END OF POST OPERATIONS



DS/OMC/APP/0039 01.09 / EN 06/07/2001

8. SHEETS The sheets of operations are not in the order of execution. Always refer to the sequence table of the operations to determine the sheet to execute and the values of its input parameters. The sheets used in this specific procedure are applicable in other procedures (other hardware configurations). For this reason, it is possible to find some conditional sections or sentences available only in other procedures.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

HOW TO…

PRESENTATION The purpose of this sheet is to describe how to perform some basic operations, which you will have to achieve all along your procedure.

Initial status The OMC-R is running and the MMI is accessible on the local workstation.

Actions

)) ON A SERVER, without graphic screen and keyboard

)) ON A PCUOAM WORKSTATION, without graphic screen

and keyboard

On server OR PCUOAM workstation without graphic screen and keyboard, the console window is displayed on a supervisory workstation, and is named the deported console window. This deported console window is mandatory to reach the server when the UNIX network layer is not raised (e.g. reboot, stop A…).

Most of the commands can remotely be executed, from a workstation, via a remote access, as described below. So, each time a server OR PCUOAM workstation session has to be opened, it means that a remote session from an OMC-R workstation has to be opened (See the D1 step). No deported console via the " terminal server" from the supervisory workstation is required.

But each time the console window is required, (such as reboot after "stop A"…), the deported console via the " terminal server" from the supervisory workstation is mandatory and is precisely specified before launching a command.

A1. How to update the environment variable to use the "vi" editor on the deported server console: Under deported server console:

... # TERM=sun-cmd ; export TERM �

)) ON SERVER

B1. Secured mode: How to lock a server Lock the server by turning the front key to the LOCKED position ( ).

B2. Unsecured mode: How to unlock a server Lock the server by turning the front key to the ON position (I).



DS/OMC/APP/0039 01.09 / EN 06/07/2001

)) ON A SERVER, with graphic screen and keyboard

)) ON A WORKSTATION

C1. How to open a shell session: In the background menu SELECT « Access to UNIX »

Then enter the username (omc, root... ) Enter the appropriate password.

C2. How to open a command tool: Under (c)root login:

... (root) # cmdtool & �

)) ON A LOCAL OMC-R WORKSTATION

D1. How to remotely log in on the active server from a workstation: D1.1 Open a omc session window (as explain in the C1 step) D1.2 Remotely log in on the active server

GOTO « Xterm »

Under omc login:

... (root) # rlogin active_server_name �

D2. How to open a session log: GOTO « OMC-R browser » SELECT « View » = Logical SELECT « Administration » SELECT « user session log... »

D3. How to open a notification window: GOTO « OMC-R browser » SELECT « View » = Logical SELECT_OBJ « MD-R » SELECT « Object – Display|Set »

Locate the managerServer parameter. The value of this parameter is the hostname of the active server

Final status Now you know how to perform all above basic operations



DS/OMC/APP/0039 01.09 / EN 06/07/2001

AUTOMATIC OMC-R STARTUP CONFIGURATION

PRESENTATION The purpose of this sheet is to modify the system configuration of an OMC-R workstation or a server to enable or disable the automatic OMC-R start-up or to enable motif graphical environment start-up without OMC-R start-up.

INPUT PARAMETERS Flag(s) ( enable | disable | enable motif)

The flag motif should be used with enable only. Exemple : ds_omcAutoStart.sh –enable -motif

INITIAL STATUS A croot session is available on the machine.

ACTIONS 1. If not already done, open a shell session under croot user. 2. If the OMC-R version is a V10

Execute the dedicated tool on the machine: Under croot login on the machine:

# /usr/local/omcmaint/ds_omcAutoStart.sh - flag(s) ��

else

Execute the dedicated tool on the machine: Under croot login on the machine:

# /usr/local/oam/bin/ds_omcAutoStart.sh - flag(s) ��

FINAL STATUS The /etc/inittab file is modified to start or not start the OMC-R software at the system boot.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

APPLICATION CONFIGURATION

PRESENTATION The purpose of this sheet is to configure the OMC-R software with the information of the following files:

/CMN/config/omc_configure.cfg /CMN/install/config/omc_install.cfg /CMN/config/omc_services.cfg

This configuration can be applied to an OMC-R server or an OMC-R workstation and even to several OMC-R machines simultaneously.

INPUT PARAMETERS target OMC-R machine(s) to configure; is one of the following arguments:

x -only_local_srv a local OMC-R machine

x -A all OMC-R machines of an OMC-R configuration

x -B" a space separated hostname list" a list of specified OMC-R machines

x -Bhostname a single OMC-R machines source OMC-R machine with the up to date configuration files, where the tool has to be

launched part OMC-R applicative part to configure (ALL | CF | COM), default is ALL

INITIAL STATUS The operating system is running on the OMC-R machine(s) to configure The OMC-R application has to be halted on each OMC-R server if the applicative part to configure is ALL. An omc session is available on the source machine.

ACTIONS 1. If not already done, open a shell session under omc user on the source OMC-R

machine. 2. Launch the configuration tool, from the source OMC-R machine:

Under omc login on the source OMC-R machine:

... (omc) % /CMN/shell/omc_configure.sh target [-f part ] ��

FINAL STATUS The OMC-R software configuration is complete.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

EXIT AND CLEAN

PRESENTATION The purpose of this sheet is to complete accurately the operations procedures.

INITIAL STATUS The OMC-R is running and the MMI is accessible on the local workstation.

ACTIONS

)) ON SERVER

1. If not already done, lock each server by turning the front key to the LOCKED position ( ).

)) ON EACH SITE

1. Gather all backup DAT, check that each of them have a written sticker on it and is write-protected.

2. Take all backup DAT, master DAT, CD-ROM(s), all procedures, all documents (and so on…) and put them in a safe place.

FINAL STATUS



DS/OMC/APP/0039 01.09 / EN 06/07/2001

OMC-R CONFIGURATION UPDATE FOR GPRS

PRESENTATION The purpose of this sheet is to modify the OMC-R configuration files to configure the GPRS function on OMC-R.

INITIAL STATUS Each OMC-R server is installed and configured. The OMC-R application may be running on each server.

ACTIONS 1. If not already done, open a shell session under omc user on the OMC-R preferential active server. 2. Edit the /CMN/base/config/omc_services.cfg file and customize it in order to enable the GPRS function on the OMC-R. At least, the GPRS_Mode parameter needs to be configured. For that purpose, refer to the following document:

� [A4] 3. If not already done, open a shell session under croot user on the OMC-R preferential active server. 4. Save the OMC-R configuration files in the /etc/nmc directory:

Under croot login on the active server:

... (root) # cp /CMN/base/config/omc_services.cfg /etc/nmc �

FINAL STATUS The OMC-R configuration files are updated to take the GPRS function on the OMC-R into account.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

OMC-R STOP

PRESENTATION The purpose of this sheet is to stop the OMC-R application, either on OMC-R server(s), or on an OMC-R workstation.

Initial status The OMC-R application is running. An omc session is available on the OMC-R machine to stop.

Actions 1. If not already done, open a shell session under omc user, on the OMC-R machine

to stop. 2. Launch the command.

Under omc login on the OMC-R machine to stop:

... (omc) % appstop std �

... OMC- R is completely stopped ... (omc) %

Note: in case of a dual-server configuration, both OMC-R servers are stopped in one shot by launching the above command from the preferential active server.

TROUBLE SHOOTING 1. The log file of the OMC-R application stopping is /CMN/base/diagnostic/diag_init. 2. The historic log file (including all OMC-R machine starting and stopping) of an

OMC-R machine is /CMN/base/diagnostic/diag_restart_omc.

Final status The OMC-R is stopped on the specified machine (the OMC-R server(s) or the OMC-R workstation).



DS/OMC/APP/0039 01.09 / EN 06/07/2001

OMC-R RESTART

PRESENTATION The purpose of this sheet is to start the OMC-R software on OMC-R server(s) or on an OMC-R workstation. For a dual-server configuration launching the command on the preferential active server allows both the preferential passive and then the preferential active server to start the OMC-R application.

INPUT PARAMETERS args arguments of the command tool; may include some following options:

[-nodbcc] no database check performed [-S] the OMC-R is started on the OMC-R server(s); on OMC-R

server(s) owning a graphic screen, it displays the OMC-R start-up supervision window without confirmation

INITIAL STATUS The OMC-R is not running. An omc session is available on the machine to restart.

ACTIONS 1. Open a New shell session under omc user, on the machine to restart. 2. Launch the start command on the machine to restart (on the preferential active

server for starting the OMC-R on the OMC-R server(s) or on the OMC-R workstation). Under omc login on the machine to restart:

... (omc) % /usr/local/oam/bin/ds_startOmc.sh [ args ] ��

TROUBLE SHOOTING 1. The log file of the OMC-R application starting is

/CMN/base/diagnostic/diag_init . 2. The historic log file (including all OMC-R machine starting and stopping) of an

OMC-R machine is /CMN/base/diagnostic/diag_restart_omc .

FINAL STATUS OMC-R is running on each OMC-R server or on the OMC-R workstation.



DS/OMC/APP/0039 01.09 / EN 06/07/2001

ZZ END OF DOCUMENT YY

gprs config in omcr

Documents