Section 7

"Confidential information -- may not be copied or disclosed without permission".

Administration Procedures

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-1

 Objectives

The tasks listed above are directly linked to OMC-R working aspects.
"Confidential information -- may not be copied or disclosed without permission".

The first three procedures can only be carried out by the OMC-R
administrator who has the power to shut down the OMC-R and knows
the UNIX super-user (root) password.

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-2

 Contents

OMC-R Customization
Configuration Files
Functional States of OMC-R Machines
Start-Up Procedures
"Confidential information -- may not be copied or disclosed without permission".

Shutdown Procedures
Switching Procedures
OMC-R Backup/Restore
Printing Management
Time and Date Management
Retrieval of OMC-R Context
Using the Intranet DNS/NIS Servers
Adding an X Terminal
Adding a Workstation

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-3

 OMC-R Customization

/etc/nmc/omc_system.cfg
/etc/nmc/omc_install.cfg
/etc/nmc/omc_services.cfg
/etc/nmc/omc_configure.cfg
"Confidential information -- may not be copied or disclosed without permission".
used by the script ds_install.sh
for the first installation and
configuration of an OMC-R machine

/CMN/config/omc_internal.cfg
/CMN/install/config/omc_install.cfg used by the configuration
/CMN/config/omc_services.cfg script omc_configure.sh
/CMN/config/omc_configure.cfg

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-4

 Configuration Files

-A To update the configuration files of all the OMC-R machines

-B host1 host2 . Hostn to update a list of machine
"Confidential information -- may not be copied or disclosed without permission".

omc_configure.sh -A /CMN/config/cfSup_hosts.cfg
Under omc login
Modification of /CMN/config/cf_tasksInfo.cfg
omc_configure.cfg
in /CMN/config /CMN/config/cf_crontable_*.cfg

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-5

 Functional States of OMC-R Machines

FUNCTIONAL STATES OF OMC-R MACHINES:

Power off
"Confidential information -- may not be copied or disclosed without permission".

Power on Power off

Halt state

Power on "Boot" Shutdown UNIX

UNIX state

Start
"Boot" Stop application
application

Application running

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-6

 Start-Up Procedures

Start up

Power off
"Confidential information -- may not be copied or disclosed without permission".

Power on

Halt state

Standard "Boot"
Power on
UNIX state

Start
application

Application running

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-7

 Start-Up Procedures
UNIX processing After the Boot

Init: first process run after the boot

"Confidential information -- may not be copied or disclosed without permission".

reads /etc/inittab file

runs script files of /etc/rc2.d directory

These script files match KnnFileName S means start FileName job

SnnFileName K means kill FileName job
nn is the relative sequence number

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-8

 Start-up Procedures
Start-up Subfunction of OMC-R Application

A5000 Run application

processes
"Confidential information -- may not be copied or disclosed without permission".

Start and check

Sun
StorEdge A5000
Sybase
INIT

Mirroring link start

SUPERVISION SUPERVISION

X Terminal

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-9

 Shutdown Procedures

Power off
"Confidential information -- may not be copied or disclosed without permission".

Power off

Halt state

Shutdown
UNIX

UNIX state

Stop
application

Application running

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-10

 Switching Procedures

SERVER No 1 SERVER No 2

ACTIVE BACKUP
INITIAL STATE

AUTOMATIC SWITCHOVER
"Confidential information -- may not be copied or disclosed without permission".

Unix ACTIVE

Application halt

Both servers running under Unix

"cf_majsecours.sh" command

Data on both servers are consistent

Start Application via background

screen menu on both servers
ACTIVE BACKUP
RESULT

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-11

 OMC-R Backup/Restore (1/4)

FILE SYSTEM BACKUP:

Performed on a gigatape
ds_backup.sh, ds_restore.sh
SYSTEM BACKUP /, /usr, /var, /opt and /home
APPLICATION BACKUP (Internal disk except system)
COMPLETE BACKUP (System and local appli)
"Confidential information -- may not be copied or disclosed without permission".

DISK ARRAY DEVICE BACKUP

ENVIRONMENT DATA ARCHIVING (BDE)

Performed on a gigatape or on a Remote
machine
Application running for archiving
Application stopped for restoration
ds_omcDataMgt.sh or cf_save_tool.x or MMI

APPLICATIVE DATA ARCHIVING

Performed on a gigatape or on a Remote
machine
Application running
ds_omcDataMgt.sh or cf_save_tool.x or MMI

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-12

 OMC-R Backup/Restore (2/4)
S1000 E4XXX

1- On active only:
In multi-user mode under croot login:
On active and passive: ds_backup.sh -Y -MdisksArray
File System In single user mode:
(MANDATORY) Just information to generate A5000
init 0 under root login or SSA file systems are saved
"Confidential information -- may not be copied or disclosed without permission".

After installation, boot -s at prompt ok

upgrade or system ds_backup.sh -Y -Mall
change 2- On active and passive:
In single user mode:
init 0 under root login
boot -s at prompt ok

ds_backup.sh -Y -Mall

Environment Data
(=BDE, MANDATORY)
After any change and
at least once a week
Daily Data
On active only under croot:
ds_omcDataMgt.sh -backupBDE -l
label
On active only under croot:
ds_omcDataMgt.sh -backupDaily
archives 4 days of daily data
can be on the same gigatape
On active only under croot:
ds_omcDataMgt.sh -backupBDE -l label
On active only under croot:
ds_omcDataMgt.sh -backupDaily
archives 4 days of daily data
can be on the same gigatape

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-13

 OMC-R Backup/Restore(3/4)

/CMN/base/exe/cf_save_tool.x
logged in as omc

cf-save_tool.x Data type to archive/Restore

"Confidential information -- may not be copied or disclosed without permission".

Operation to perform : 1 : Fault

1 : Archive data 2 : Observations
2 : Restore data 3 : Trace
3 : Retrieve configurations files 4 : Other data
4 : Labelize a tape 5 : Backup
5 : Consult tape label (0 : exit)
6 : List Media content
(0 : exit)

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-14

 OMC-R Backup/Restore (4/4)

Centralized Archiving on a remote workstation

OMC1 OMC2
"Confidential information -- may not be copied or disclosed without permission".

Sun
Sun
StorEdge A5000
StorEdge A5000

Mirroring link Mirroring link

/partition1 NFS Server

Workstation1 /partition2 Workstation2
Workstation3

OMC1
OMC2

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-15

"Confidential information -- may not be copied or disclosed without permission".
Printing Management (1/3)

Laser printer

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-16

 Printing Management (2/3)

Useful commands are:

"Confidential information -- may not be copied or disclosed without permission".

lp prints the named file (via spooler)

lpstat displays printer status information

lpq displays queue of printer jobs

lpd printer daemon

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-17

 Printing Management (3/3)

Useful commands are:

"Confidential information -- may not be copied or disclosed without permission".

lp prints the named file (via spooler)

lpstat displays printer status information

lpq displays queue of printer jobs

lpd printer daemon

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-18

 Time and Date Management

WS
BSS
"Confidential information -- may not be copied or disclosed without permission".

WS OMC-R

UNIX
Passive
OMC-R
WS
UNIX

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-19

 Retrieval of OMC-R Context (1/2)

Log in as croot or omc

%cd /CMN/base/tools/shell
% zap.sh without option, zap.sh is executed on the machine where it is run
-v Version of zap.sh
"Confidential information -- may not be copied or disclosed without permission".

-h Help
-a zap.sh is run on every machine of the OMC-R configuration
-m This option has to be followed by a list of OMC-R
machines e.g: machine1,machine2,machine3
-r This option has to be followed by a list of Role_Types
o for a machine having a manager
m for a machine having a mediation device
s for every kind of station
d for SDO stations
-f Fast Mode: save only the fast mode files specified in zap.cfg
-s Silent Mode: Only the most important messages are displayed
on the screen

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-20

 Retrieval of OMC-R Context (2/2)

result files: in /home/omc/zap

zap_hostname_YYYYMMDD_hhmm.tar
zap_hostname_YYYYMMDD_hhmm.log
"Confidential information -- may not be copied or disclosed without permission".

save files on gigatape using: # cd /home/omc/zap

# tar cvf /dev/rmt/0 .

To display the content of the backups file:# tar tvf *.tar

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-21

 Using the Intranet DNS/NIS Servers
DNS/NIS Server(s): A New Way to Administrate the OMC-R

Intranet

Sun
OMC-R Network StorEdge A5000

DNS Server
"Confidential information -- may not be copied or disclosed without permission".

Hostame <-> IP@

Monitoring link
E4500 E4500

NIS Server

X
omc
X TERMINAL WS croot
Terminal
Workstation sybase
rot
[non std users]

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-22

 Using the Intranet DNS/NIS Servers
Configuring an OMC-R Machine as a DNS Client

Shutdown of the OMC-R application on each machine

"Confidential information -- may not be copied or disclosed without permission".

Update of /etc/nmc/omc_system.cfg under croot login on each machine

DnsDomain.7.DomainName=oamomc (Name of the DNS server without dot)
DnsDomain.7.PriServerIP=136.147.100.120 (IP@ of the Primary DNS server)
#DnsDomain.7.SecServer1IP= (IP@ of the 1st sec DNS server)
#DnsDomain.7.SecServer2IP= (IP@ of the 2nd sec DNS server)

In this example, there is only one DNS server.

Configuration of each machine as DNS client under croot login:

/usr/local/oam/bin/ds_configDnsNis.sh -Aadd -Sdns

Restart of the OMC-R application on each machine

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-23

 Using the Intranet DNS/NIS Servers
Configuring an OMC-R Machine as a NIS Client

Shutdown of the OMC-R application on each machine

"Confidential information -- may not be copied or disclosed without permission".

Update of /etc/nmc/omc_system.cfg under croot login on each machine

Example: NisDomain.8.DomainName=oam.nortel. (With a dot at the end)

NisDomain.8.MasterServerName=hostnis
NisDomain.8.MasterServerIp=136.147.100.123

Configuration of each machine as NIS client under croot login:

/usr/local/oam/bin/ds_configDnsNis.sh -Aadd -Snis

Restart of the OMC-R application on each machine

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-24

 Adding an X Terminal

Sun StorEdge A5000

"Confidential information -- may not be copied or disclosed without permission".

Monitoring link
E4500 E4500

X X TERMINAL WS
Terminal
Workstation

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-25

 Adding a Workstation

Sun StorEdge A5000

"Confidential information -- may not be copied or disclosed without permission".

Monitoring link
E4500 E4500

X WS WS
Terminal

PE/TRD/CN/0303 12.02/EN March, 2000 Administration Procedures 7-26

 "Confidential information -- may not be copied or disclosed without permission".

PE/TRD/CN/0303 12.02/EN
March, 2000
Student Notes

Administration Procedures
7-27
 "Confidential information -- may not be copied or disclosed without permission".

PE/TRD/CN/0303 12.02/EN
March, 2000
Student Notes

Administration Procedures
7-28