TOS18011D0SGDENI10

1300 XMC (Cross-Domain
Management Center)
7.0 System administration
TOS18011 D0 SG DEN I1.0 Issue 1
STUDENT GUIDE
All Rights Reserved Alcatel-Lucent 2009
All rights reserved Alcatel-Lucent 2009

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent

7.0 System administration - Page 1
Empty page
Switch to notes view!
1300 XMC (Cross-Domain Management Center)

This page is left blank intentionally

Terms of Use and Legal Notices

1. Safetyto
Warning
Switch
notes view!
Both lethal and dangerous voltages may be present within the products used herein. The user is strongly advised not to
wear conductive jewelry while working on the products. Always observe all safety precautions and do not work on the
equipment alone.
The equipment used during this course may be electrostatic sensitive. Please observe correct anti-static precautions.
2. Trade Marks
Alcatel-Lucent and MainStreet are trademarks of Alcatel-Lucent.
All other trademarks, service marks and logos (Marks) are the property of their respective holders, including AlcatelLucent. Users are not permitted to use these Marks without the prior consent of Alcatel-Lucent or such third party owning
the Mark. The absence of a Mark identifier is not a representation that a particular product or service name is not a Mark.
Alcatel-Lucent assumes no responsibility for the accuracy of the information presented herein, which may be subject to
change without notice.
3. Copyright
This document contains information that is proprietary to Alcatel-Lucent and may be used for training purposes only. No
other use or transmission of all or any part of this document is permitted without Alcatel-Lucents written permission, and
must include all copyright and other proprietary notices. No other use or transmission of all or any part of its contents may
be used, copied, disclosed or conveyed to any party in any manner whatsoever without prior written permission from
Alcatel-Lucent.
Use or transmission of all or any part of this document in violation of any applicable legislation is hereby expressly
prohibited.
User obtains no rights in the information or in any product, process, technology or trademark which it includes or
describes, and is expressly prohibited from modifying the information or creating derivative works without the express
3written consent of Alcatel-Lucent.
All rights reserved Alcatel-Lucent 2009
4. Disclaimer
In no event will Alcatel-Lucent be liable for any direct, indirect, special, incidental or consequential damages, including
lost profits, lost business or lost data, resulting from the use of or reliance upon the information, whether or not AlcatelLucent has been advised of the possibility of such damages.
Mention of non-Alcatel-Lucent products or services is for information purposes only and constitutes neither an
endorsement, nor a recommendation.
This course is intended to train the student about the overall look, feel, and use of Alcatel-Lucent products. The
information contained herein is representational only. In the interest of file size, simplicity, and compatibility and, in some
cases, due to contractual limitations, certain compromises have been made and therefore some features are not entirely
accurate.
Please refer to technical practices supplied by Alcatel-Lucent for current information concerning Alcatel-Lucent equipment
and its operation, or contact your nearest Alcatel-Lucent representative for more information.
The Alcatel-Lucent products described or used herein are presented for demonstration and training purposes only. AlcatelLucent disclaims any warranties in connection with the products as used and described in the courses or the related
documentation, whether express, implied, or statutory. Alcatel-Lucent specifically disclaims all implied warranties,
including warranties of merchantability, non-infringement and fitness for a particular purpose, or arising from a course of
dealing, usage or trade practice.
Alcatel-Lucent is not responsible for any failures caused by: server errors, misdirected or redirected transmissions, failed
internet connections, interruptions, any computer virus or any other technical defect, whether human or technical in
nature
5. Governing Law
The products, documentation and information contained herein, as well as these Terms of Use and Legal Notices are
governed by the laws of France, excluding its conflict of law rules. If any provision of these Terms of Use and Legal
Notices, or the application thereof to any person or circumstances, is held invalid for any reason, unenforceable including,
but not limited to, the warranty disclaimers and liability limitations, then such provision shall be deemed superseded by a
valid, enforceable provision that matches, as closely as possible, the original provision, and the other provisions of these
Terms of Use and Legal Notices shall remain in full force and effect.

Blank Page


Course Outline
1. XMC
administration
About
ThisSystem
Course
4. Topic/Section is Positioned Here
Course outline
1. Introduction
Technical
2.support
Operators Management
Course objectives
3. XMC Processes Management
4. Backup
and RestoreHere
1. Topic/Section
is Positioned
Xxx
Xxx
Xxx
5. AS Administration
6. System Management
7. NE Creation
8. Geographical redundancy

9. Glossary


Course Outline [cont.]

6

Course Objectives
Welcome to 7.0 System administration
Upon completion of this course, you should be able to:
By the end of the course, the participant will be able to:
- describe the administrator role and the main mechanisms needed for administration
tasks,
- manage the operator sessions, the processes and restart the server,
- perform backup and restore tasks,
- control the operator access rights,
- handle common system maintenance tasks,
- administrate the CAL alarms,
- manage the NE topology,
- manage the XMC logs
- customize system parameters
7
- Management
perform
OMC systems switch-over (redundant configuration).
1300 XMC (Cross-Domain
Center)

Course Objectives [cont.]

8

About this Student Guide

Conventions
used
in this guide
Switch
to notes
view!
Note
Provides you with additional information about the topic being discussed.
Although this information is not required knowledge, you might find it useful
or interesting.
Technical Reference
(1) 24.348.98 Points you to the exact section of Alcatel-Lucent Technical
Practices where you can find more information on the topic being discussed.
Warning
Alerts you to instances where non-compliance could result in equipment
damage or personal injury.
Where you can get further information

If you want further information you can refer to the following:

Technical Practices for the specific product
Technical support page on the Alcatel website: http://www.alcatel-lucent.com

About this Student Guide [cont.]

10

Self-assessment of Objectives
Contract number :
At the end of each

Course title :
Please, return this
Client (Company, Center) :
Language
:
Switch
section you will be asked to fill this questionnaire

sheet to the trainer at the end of the training
Dates from :
to notes view!
Number of trainees :
to :
Location :
Surname, First name :

Did you meet the following objectives ?
Tick the corresponding box
Please, return this sheet to the trainer at the end of the training
Instructional objectives
11
Yes (or
globally
yes)
No (or
globally
no)


Comments
Self-assessment of Objectives [cont.]

Instructional objectives
12
Yes (or
Globally
yes)
No (or
globally
no)
Comments

Other comments
Thank you for your answers to this questionnaire

Do not delete this graphic elements in here:
11
Section 1
XMC System administration
Module 1
Introduction
3JK11458AAAAWBZZA Edition 3
1300 XMC (Cross-Domain Management Center) 7.0 System administration

All Rights Reserved 2007, Alcatel-Lucent

Section 1 Module 1 Page 1
Blank Page
XMC System administration Introduction
11

Document History
Edition
Date
Author
03
2009-09-24
RANNOU, Raymond
Remarks

Objectives
11
To be able to describe the XMC architecture, to identify its
main software components and the possible network

architectures.


Objectives [cont.]

11

Table of Contents
11
Page

1 TMN Architecture
1.1 Managed Networks and Domains
2 A1300 XMC Software Architecture
2.1 XMC functional architecture
2.2 Network Element supervision
3 A1300 XMC Hardware Platform
3.1 Server configuration
3.2 Single Server configuration
3.3 Geographical Redundancy (option)
3.4 Dimensioning keys
4 Operator Tasks
4.1 XMC operators
4.2 Administration and Maintenance
5 Questions and Solutions


7
8
11
12
13
14
15
16
17
18
20
21
22
26
Table of Contents [cont.]

11

This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

11
1 TMN Architecture


1 TMN Architecture
1.1 Managed Networks and Domains

118
The A1300 XMC :

Is the management system for the following networks :
the Circuit Switched Core Network
the Packet Switched Core Network
the IMS, NGN, UMA
Covers the following management domains :

Fault management
Configuration management
Performance management
Security management
Log management
Geographical redundancy

The charging management is done by the A8965 Charging Gateway

1 Introduction
1.2 XMC General Principle

119
External OSSs
NBI
Integrated XMC
SBI
IP Backbone
Legacy
OMCs
X25/IP
IP
NGN / IMS / UMA /

Packet U3
Circuit
Packet U2
domain
domain

domains
XMC allows to manage all the Alcatel Core Network Elements and releases, including :
Circuit domain U1x, U2, U3 (through OMC CS) as well as NGN networks (Wireless NGN Network)
Packet domain U2 (through OMC PS), and U3
GSM and CDMA domains through ISMC
IMS domain Core nodes for both Fixed and Mobile Networks
UMA network
NBI : Northbound Interface (XML/SOAP, 3GPP) (optional)

to forward topology, alarms, performance data to external OSS
SBI : Southbound Interface (Corba-SOAP-FTP-HTTP/IP)

XMC : Cross-Domains Management Center

1 Introduction
1.2 XMC General Principle [cont.]

1 1 10
NBI : Topo, Alarms, Perfs,

3GPP Corba, SNMP, XML/SOAP,
QOSAC
XMC
Legacy or
Other OMCs
FM SNMP/CORBA
PM SNMP/CSV/XML Files
CM XML/CORBA/CLI
portal
IP
X.25/
EML
EML
EML
EML
IMS network ngXX network UMA network GPRS network
Legacy/other networks:
EVx, SSP HC3.x, PSU2
MGC12, LGP,
Generic MAS
1430 ngHLR
LCP based
8650 SDM
5400 JP
5410 Pres, XDMS
5420 CTS, PCM, CCS
5430 IM, PTX,

IM-HSS
WAS/AAA
Load Balancer
GPRS GW
Security GW
SGSN
iGGSN
GGSN Cisco
Cisco routers
Lu front end
EML
NGN network
5060 WCS, 5060 MGC10
5020 AGCF, 5620 MGC10
7570 MGW, 7510/7515 GW
5900 MRF, 5910 SRP .
The charging management is done by the A8965 Charging Gateway.

The QoSAC Application is running on external server (co-hosted in future release for small
network configuration).
NBI : North Bound Interface
CM : Communication Management
FM : Fault Management
PM : Performance Management

11


11
3 XMC Software
2.1 XMC functional architecture

1 1 12
The
XMC is based on a Web Portal approach.

The XMC is running in a client/server mode
All applications are stored on the XMC server
The Java Web Start application (LSM module) checks the login
parameters and control the application download on the OWP.

Get local
resources
Webstart
cache
Web
Start
E
C
OWP
Only accessible
for verified
applications
WEB Server
Jar files
JNLP pages
External resources
XMC Server
Webstart provides transparent download and caching mechanism that enables application to be started
without any pre-requisite on the client host (Zero Installation Cost feature). At first start of the application,
Webstart downloads the JAR files of the application in its cache and start the application in a separate JVM.
So, the following launch of the application will be quicker by avoiding useless download of JAR files.
By default, Webstart applications have restricted access to the client machine resources (Disk, Network). In
this mode, applications may ask to have access to those protected resources but they must allow their
identification by the Webstart JVM or the Java plug-in (for applet mode). To allow this, the JAR files must be
signed with a trusted signature.
The applications are downloaded on the OWP at the first launch of the application for a given XMC version.
LSM : Local Security Manager

OWP : Operator Workplace Position
JNLP : Java Network Launching Protocol
JWS : Java Web Start Application

2.2 Network Element supervision

1 1 13
Principle :
Network element management (EML) software and associated
graphical user interface (GUI) reside on the network element(NE).
Each NE provides its Element Manager
Accessed via the Web Browser
Uploaded and Run via JNLP (Java Network Launching Protocol)


11


14
3.1 Server configuration

1 1 15
Single server configuration

The only possible configuration.
This configuration is composed of:

ENMS (HP_UX) : based on ENMS-2, ENMS-4, ENMS-6 or ENMS-8 running
client part and server part on the same server.

ENMS_LX (LINUX) : based on ENMS-4-LXor ENMS-8-LX running client part
and server part on the same server. These servers include a rack mounted
system console.
System console for PA-RISC : based on PC connected to ENMS (Operator
session access and system access).
OWP : based on PC connected to ENMS.

Exemple of XMC Server :
2U
DL380 G5 1 or 2
QuadCores

3.2 Single Server configuration

1 1 16
Managed domains
External OSS (if any)

Additional NM
eqts
NE, ...
OWPs
System console
IP
2 * routers
Cisco 2621
Printer
NTP server
(if any)
100 Base-T LAN

Ethernet
Web Console
ENMS
( optional )
External storage
Exemple of single server Configuration (HP-UX)


3.3 Geographical Redundancy (option)

1 1 17
NE, ...
IP

Geographical redundancy is based on the duplication of OMC-Server and associated external storage.
A double LAN is recommended, and if needed, appropriate underlying network is needed (SNCP, IP/MPLS).
The nodes and operator workplaces are connected to both XMC servers.
The geographical redundancy supported by the XMC is in active/ready mode.

An XMC is active, when operators are connected to it and are performing their supervision operation.
The Ready XMC, also connected to the NEs and to the active XMC, does not support any operator session,
does not forward any SNMP traps/corba notification to the upper OSS and does not collect any performance
files/counters on the NE.
All data are synchronized by internal system.

3.4 Dimensioning keys

1 1 18
The ENMS type and configuration will depend on :

The number/type of nodes to be managed,
The number of operator positions
The installed software packages
Proliant server configurations 1 or 2 Quad Core CPUs :

ENMSx = in rack
sENMSx = rackless
Other configurations :
Servers configurations :
Field trial or for very small network (no possible evolution)
HP
B2600 HP-UX workstation : 2GB memory, 1 x 72 GB disk
ML350
Linux workstation : 2 GB memory, 2 x 72 GB disk
Small / Medium / Large networks

HP
PA-RISC RP 44xx / HP-UX 11i
HP Proliant DL580G4 and DL380 G5/Linux RedHat 5 (recommanded)
2
to 8 CPUs,
from
6 to 18 GB memory,
from
2 x 72/146 GB disks + external storage.
DAT
and DVD drives

3.4 Dimensioning keys [cont.]

1 1 19
number of operator sessions dimensioning depends of

network size and selected packages.
Recommended dimensioning is as follows:
The
One operator on system console (PA-RISC only)

One system console is mandatory.
A
system console can be shared between several servers of the same

configuration. This operator position can be used as an administration
workplace in additional of HP system console function.
Core package
One
operator per 3 up to 5 NE is recommended.
QoS Traffic Supervision/ QoS Analysis Package (QoSAC)

1
additional user is recommended if QoS traffic supervision is used.

Note that :
- when nodes are managed directly by the XMC, they count as 1
- but when they are managed through an existing OMC (OMC PS, OMC CS, CMC, ISMC )
they count as 0,6
- the number of operators accessing the legacy network does not impact the XMC
dimensioning.

11
4 Operator Tasks


20
4 Operator tasks Platform
4.1 XMC operators

1 1 21
The following default operators are defined on XMC :

1. Viewer : allowed to only display/access network equipment alarms
he has access to
2. Operator : allowed to manage the network topology (display,
update)
3. Administrator : allowed to manage the network topology and the
XMC processes (start, stop).
4. XMC system administrator authorized to all administration and
maintenance tasks, mainly via HP-UX/LINUX commands.
New operators can only inherit of types 1 to 3 operator

rights.

The XMC system administrator is axadmin.

4.2 Administration and Maintenance

1 1 22
XMC
Maintenance
Administration
Troubleshooting
Users management
System Cleaning up
XMC processes management

XMC server Starting,
Stopping and Restarting
Trace and Events reading

Backup/Restore Management
Etc.

Etc.

4.2 Administration and Maintenance [cont.]

1 1 23
Administration tasks (on request):

On users : assign a password, lock/unlock, force a logout
On processes : check the status, restart a process if stopped, check the
filling percentage of the logical volumes
On Logs : save/export the logs content
Maintenance Tasks (regular):
Check and Analyse the troubleshooting(s) with the Alcatel-Lucent help
Regularly proceed to obsolete files cleaning (alarms log, core files,)
Proceed to preventive application data backup : after any network
topology modification, or users update,
At
least weekly


Introduction
Answer the questions

1 1 24
What is an ENMS ?
Which types of Servers/Operating Systems can be installed ?
OS
OS

About the ILO access :

Term meaning :
Role/purpose ?
The USM run on the server ?

yes

no
Self-Assessment on the Objectives

11
Please be reminded to fill in the form

for this module
The form can be found in the first part
of this course documentation


25
11


26
1 Introduction

1 1 27
What is an ENMS ?
An Equipment and Network Management Server
= Main XMC server

Which types of Servers/Operating Systems can be installed ?
HP rp44xx
DL 380 G5
OS HP-UX 11i
OS HP-Linux RedHat 5
About the ILO access :

Term meaning : Integrated Light-Out
Role/purpose ? HP server configuration and maintenance
interface. Provides, for exemple, the Web Console access,

event if the XMC (applications) is stopped.
The USM run on the server ?
yes
no
The USM(GUI) is downloaded and executed on OWP when

navigating to an application.


11
End of Module
Introduction


28
12
Section 1
Module 2


Blank Page
XMC System administration Operators Management

12
Document History
Edition
Date
Author
03
2009-09-24
RANNOU, Raymond
Remarks

Objectives
To be able to manage the operators sessions, to explain
the security, to create, modify and/or delete an operator

access, and to configure the activity periods.


12
Objectives [cont.]


12
Table of Contents
12
Page

1 Session Management
1.1 Access to the interface
1.2 How to send a message
1.3 How to force a session logout
1.4 Purging closed sessions
1.5 Clear table action
1.6 Refreshing actions
2 The Access Security function
2.1 User characteristics
2.2 Operators profiles
2.3 Security management domains
3 Managing the User Access
3.1 Securing the user database access
3.2 Creating an operator
3.3 Accessing the GUI interface
3.4 Configuring a user access
3.5 Modifying a user access
3.6 Assigning a profile
3.7 Locking/Unlocking a user access
3.8 Setting/modifying a user password (administrator)
3.9 Deleting a user access
3.10 Checking users web portal access
3.11 Unlocking a user web portal access
4 Managing the activity periods
1300 XMC
(Cross-Domain
Management
Center)
4.1
Setting activity
periods
7.0 System
4.2administration
Defining personal weekly schedule
4.3 Defining Personal vacation dates
4.4 Assigning a weekly schedule (or holidays)
5 Questions and Answers

7
8
9
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
40


This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

12


12
1.1 Access to the interface

12
From the Web Portal, in the "Security Management" :

Select Sessions Administration GUI
The "Sessions Administration" window is displayed
Open sessions (default display)
Closed sessions
Forced to close sessions


1.2 How to send a message

From the Sessions Administration GUI

Select a session or a subset of user sessions
Type the message
Select the Message Priority
Select the Sending Type
Click Send


12
1.2 How to send a message [cont.]

12
1
Right Click, or
Actions
Actions
Priority ?

Procedure :
1. Select : Actions Send a message
2. Enter the message text
3. Select the sending context : Notification level, Type
4. Press Send

10
1.3 How to force a session logout

12
Open a Sessions Administration GUI

Select a session
1
Click Actions
Force logout
A Session Logout Confirmation box opens
Select the Logout Type (and delay)

Enter a logout message
Press Confirm
The selected session is closed
2
3

11
1.4 Purging closed sessions

Purpose :
When sessions have been closed, they are displayed in the sessions list.
This option allows to clear all closed sessions.
From a Sessions Administration GUI,

Select : Actions > Purge closed sessions
Press Yes to confirm


12
12
1.5 Clear table action

Purpose :
Unselect all selected items in tables.

Select : Actions > Clear table selection


12
13
1.6 Refreshing actions

Purpose :
Immediate refresh of the session table to display the current state of the
sessions.
Select : Actions > Refresh table


12
14
2 The Access Security function


12
15
2 The Access security function
2.1 User characteristics

A user is defined with personnal and common characteristics.

Personal characteristics :
Login and password
User profile
Personal weekly schedule (*)
Personal vacation (*)
Common characteristics :
Common weekly schedule (*)
Public holidays (*)
(*) optional feature

See : "A1300 XMC - Platform Administration Guide", chapter 3

1 2 16
2.2 Operators profiles

1 2 17
Predefined Profiles define the access rights to the A1300 XMC :
Viewer
allows the end-user to consult the XMC supervised objects
Operator
allows the end-user to manage the XMC supervised objects
Admin
allows the end-user to manage the XMC supervised objects

and gives access to administrator tasks
SECAdmin
gives only the rights to access Security Management dedicated tasks

only assigned to axadmin user

Other profiles (extensions of the SECAdmin profile, only assigned to axadmin) :

GeoredAdmin
access to the Geographical Redundancy management
AWPSecAdmin
allows access rights to Security Management directly from the Web portal
NeacdAdmin
allows access to Access Control Administration
Default created users and profiles :

axadmin
admin+SECAdmin+GeoredAdmin+AWPSecAdmin+NeacdAdmin
operator
operator
viewer
viewer
The axadmin user cannot be removed nor locked.

2.3 Security management domains

Two sub-domains are used to manage XMC user accesses :

The "Operator Access Control" GUI
The "Operator Management" GUI
They are only available for the security manager.
The "Operator Management" GUI is used :

To Declare or delete a user access
To Modify a user password
To Modify user administrative information
Other tasks, like assigning a profile, are done using the "Operator
Access Control" GUI.


12
18


12
19
3.1 Securing the user database access

The two following options can be used to secure the security
database management :
1. Locking the user database
Why do you need to lock the user database ?
To prevent any further update operation on users
Before a backup, for exemple
2. Setting the Exclusive mode
Why do you need to set the exclusive writing mode ?
To ensure that only one security administrator can update the
security database
Other administrators can no more perform write operations
Prerequisites : Your login must be axadmin
These actions can prevent any database inconsistency.

1 2 20
3 Managing the Access
3.2 Creating an operator

To create a new operator, the security manager have :

1.
To Create a user access
to identify the user in the security database
Using the "Operator Management" GUI

2.
To Modify the user access

to assign the user for a profile
and to configure additional personal data
Using the "Operator Access Control" GUI


1 2 21
3.3 Accessing the GUI interface

Launch the "Operator Management" interface to create the user

access in the security database :

Login as axadmin
Open the "Operator Management" session


1 2 22
3.4 Configuring a user access

1 2 23
Right Click on secdb
or
Select :
User Management
Create User
2
1- Enter the "User login"
data (login, password)

2- Enter the "Attributes"
information (Name)
3- Press Apply

In 'User Login', fill in the login name and password :

apply the unix rules related to the user creation. Min 8 alphanumeric characters for the password.
In 'Attributes',
- the 'Name' information is mandatory.
- LockPassword :
TRUE
The account is locked at the next login, user cannot login until the administrator change the
value to FALSE. This value can be position either by the administrator or automatically when
the maximum password authentication failures are reached.
FALSE
The account is unlocked, user can login.
- ResetPassword :
TRUE
FALSE
The user must change its password at the next login

The password does not need to be changed

3.5 Modifying a user access

To access a user modification GUI

Login as axadmin
Launch the "Operator Access Control" GUI

the "ACI management / Operator" window opens
Open the "Operator" list


1 2 24
3.6 Assigning a profile

From the "Operator Access Control" GUI

Select the Operator
In "Edit Operator" tab

Select a Profile Name
Press the right arrow
Select an Access domain

"Access_to_"
Press the right arrow

Press Apply

Following profiles can be assigned to new users : Admin, Operator and Viewer.
When NE access control is activated, you need to assign in addition one or several Domain profile(s).

1 2 25
3.7 Locking/Unlocking a user access


After creation, an operator access is locked (login is forbidden).

The security administrator can lock or unlock an operator access.
To lock or unlock an
operator access :

Select the folder

Operator
Select the operator
name
Press Lock (or Unlock)
Locked operator
Unlocked operator

1 2 26
3.8 Setting/modifying a user password (administrator)

1 2 27
In the "Operator management" GUI

Double-Click on Users
Double-Click on secdb
Select the user
Press Set Password
Enter the new password and
confirm
Press OK

Each operator can change its password from the XMC Web Portal interface, using File -> Change password
-
Enter the old password,
Enter the new password,
Confirm the new password
Click Change
Password rules, more than 8 characters :

- Min 1 numeric character,
- Min 4 alphabetical characters
- Min 2 special characters
- Min 1 char in upper case
- Min 1 char in lower case,
- Max 2 identical consecutive characters
For Details see "Alcatel 1300 XMC Platform administrator Guide Operator Guide" - 3BL 65020 GABA PCZZA
chapter 1, 1.1.3

3.9 Deleting a user access

From the "Operator management" GUI

Double-Click on Users
The 'secdb' user list is displayed
Right click on the user
and select Remove User
Or
Or press
Confirm the user deletion


1 2 28
3.10 Checking users web portal access


Each web portal user account can be displayed from a Unix/Linux CLI.
To list the user accounts (declared operators) use :
# /alcatel/omc1/OMC_SECCF/scripts/list_users.sh
1 2 29
To display the details of an user web account use :

# /alcatel/omc1/OMC_SECCF/scripts/query_user.sh <user>

This command can be used to unlock the web account for axadmin.

3.11 Unlocking a user web portal access

1 2 30
To unlock an user web account (and reset the password) use :

# /alcatel/omc1/OMC_SECCF/scripts/reset_userpw.sh <user>
The user password is reset to default factory password : OM_cc_n1
At next login he will be asked to change this (old) password.

This command can be used to unlock the web account for axadmin.
On a trusted system, the system administrator (root) can use the following commands
To list Unix/Linux user account status :
/install/scripts/user_lock.sh list <user_account>

To unlock a user account :
/install/scripts/user_lock.sh unlock <user_account>

To refresh a password :
/usr/lbin/modprpw -l v <user_account>
If the locked account is root, execute the following command as axadmin
# sudo /install/scripts/user_lock.sh unlock root

4 Managing the activity periods


12
31
4 Managing the Activity Period
4.1 Setting activity periods

Following data can be customized :

For each operator, the activity periods :

Personal weekly schedule : normal daily activity times

Personal vacation dates : operator days off
For all operators :

public holidays periods.


1 2 32
4.2 Defining personal weekly schedule

1 2 33
Use the Weekly Schedule tab to define the personal user activity periods
Select Create New
Weekly Schedule tab
Enter the schedule
Friendly Name
For each day:
Select the day

Remove existing period
Enter the start time and
the period duration
Click Set Period
Press Apply when finished


4.3 Defining Personal vacation dates

Select the Holiday tab

Fill in the Holiday Name
For each period,
Enter the Begin Date
and End Date
Press Add
Press Apply when

completed


1 2 34
4.4 Assigning a weekly schedule (or holidays)

1 2 35
1
2

To assign a weekly or holiday :

1. Select the weekly and/or holiday item in the list
2. Press the right arrow
3. Press Apply

Operators management

1 2 36
To be able to create/delete an operator, you need

An Admin profile ?

A SECAdmin profile ?

To be root user ?

To be axadmin user ?
An XMC administrator can create new profiles ?

yes
no
How many security administrator(s) can work at the

same time on the server ?
one
two
more


Exercise 1
1 2 37
Note : Only one administrator can access this function

As axadmin :
Create a user access : OpeGrx
(x=group number)
Assign the "Operator" profile
From another terminal,

Login as OpeGrx, and check the domains and menus
Logout as OpeGrx
As axadmin,
Assign the "Admin" profile
Duration
15'
From another terminal, check the rights of the previous
operator.
Remove the created operators


Exercise 2
1 2 38
Note : Only one administrator can access this function

As axadmin , modify (then assign) the user personal
weekly schedule to able to work
On Monday to Thursday : 09:00 to 16:30
On Friday : 09:00 to 12:00
On Saturday and Sunday : 08:00 to 12:00
Lock the OpeGrx user access

Try to login from another terminal
Unlock the OpeGrx user

Remove the OpeGrx user
Duration
10'


Evaluation
1 2 39
Objective: to be able to explain the security,
to create or modify or delete a user access, and

to configure the activity periods.
Thank you for answering

the objectives sheet


5 Questions and Answers


12
40

1 2 41
To be able to create/delete an operator, you need

An Admin profile ?

A SECAdmin profile ?

To be root user ?

To be axadmin user ?
An XMC administrator can create new profiles ?

no
yes
they are predefined
How many security administrator(s) can work at the

same time on the server ?
one
two
more
BUT : it is recommended to work in Exclusive mode' to avoid
inconsistencies in the security database.


12
End of Module


42
13
Section 1
Module 3
XMC Processes Management


Blank Page
XMC System administration XMC Processes Management

13
Document History
Edition
Date
Author
Remarks
01
2009-02-20
RANNOU, Raymond
First edition
02
2009-04-21
RANNOU, Raymond

Objectives
To be able to understand the processes and resources
status, to start and stop the processes, to start and stop

the XMC server, and to display system related information.


13
Objectives [cont.]


13
Table of Contents
13
Page

1 Processes and Resources
1.1 Software Packages
1.2 System Resources
1.3 Subsystem processes
1.4 Processes status
1.4.1 The A1300 XMC state summary
1.4.2 XMC processes state via CLI
1.4.3 The System Resource Monitoring
1.4.4 Process and disk status
1.4.5 Exemple of display
2 Managing the Processes and Resources
2.1 How to access to the function
2.2 The XMC Software Inventory
2.3 List of PC and Unix clients
2.4 Displaying the processes status
2.5 Displaying the logical volumes status
2.6 Filesystems usage and purge actions
3 Starting and Stopping the Processes
3.1 Choosing the interface
3.2 Stopping a process
3.3 Starting a process
4 Starting and Stopping the XMC Server
4.1 Stop overview
4.2 Stopping the A1300 XMC
1300 XMC
(Cross-Domain
Center) System
4.3
StoppingManagement
the Operating
7.0 System
4.4administration
Starting the A1300 XMC server
4.5 Rebooting the A1300 XMC server

7
8
10
11
13
14
15
16
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
34
36
37
38
42


This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

13


13
1.1 Software Packages

138
Mandatory Package :
The Core Package
encompasses ALL necessary and basic features requested to operate a network via the
XMC/OMC-CN.
allows NE supervision, alarm management, operator profile management,
Includes :

Packet U3
Circuit NGN R3-R4
IMS mobile
UMA
IMS FMC

IMS FMC : IMS Fixed-Mobile Convergence

1.1 Software Packages [cont.]

139
Optional Packages :
3GPP northbound CORBA Interface provides 3GPP Open interfaces ,
covers the following area:

Alarm Forward & Network Topology Interface

Configuration/Provisioning Interface: node dependent
Performance Data Retrieval
SNMP northbound alarm interface

provides SNMP northbound alarm interface.
Software Management package

to download software releases and evolution package from XMC/OMC CN to Nodes.
Centralized Backup Restore package

allows the operator to handle centralized command and control for NEs backuprestore.
Geographical redundancy package

The XMC/OMC-CN system is duplicated
Traffic supervision and analysis (1342 QoSAC) package
allows to summarize performance data in near real time

highlights abnormal situations (alarm generation on thresholds, graphic views
animations,)

The "Northbound Interfaces" to external systems are based on 3GPP standards.

These interfaces are based on CORBA for supervision, topology, configuration.
The performance files are exported in XML format, via FTP.
SNMP is also supported for Alarm management only.

1.2 System Resources

1 3 10
North
Interface
po
To
gy
lo
em
g
a
an
M
t
en
3GPP Management
Performance
Management
RA Management
Alarms Management
Supervision
Management
ALMAP Web
platform
NE communication Management

System and
Utilities
Third parties
The Network Management includes the Topology and the Supervision management functions.
Topology Management
responsible for the management and persistency of all topological information
Supervision Management
provides the network supervision view to all operators ( dynamic infos about NEs, allows all navigations, ..)
Alarm Management
Responsible for the management of both Current Alarm List (CAL) and Historical Alarm List (HAL)
NE Communication Management
Is in charge of the communication with a range of Nes, applying model mapping to OMC model.
3GPP Management
Is responsible for the collection of PM counters from the Nes.
RA Management
Offers added-on value features compared to RA/RNC management provided by SGSN EML GUI
Ensures data consistency between the SGSN and the DNS
System and Utilities

Offers a various platform services such as : process monitoring, trace management, database management,
purge management, OMC backup/restore
ALMAP Web Platform

Contains several components which allows to launch secured web-based applications
Third parties
Contains all external softwares

1.3 Subsystem processes

The susbsystem list of processes depends on installed software
packages :
Mandatory package for
Topology and network management,

Alarms management
Network Communication management
Performance management
Security management
Optional packages for
Northbound interface (SNMP, itf, )

Software download management



1 3 11
1.3 Subsystem processes [cont.]

Topology management TopoIM

Network Supervision management SupIM
NEs Communication Management
snmpCM, dmscCM, os2osCM, tomasCM, iggsnCM, ismcCM, e10CM
RA management NetraIM
3GPP management 3gppIM
Alarm management :
ascurIM, ashistIM, FMCUR server, FMHIST server, NSP
Performance management pmIM

Third parties
Naming server, http server, Notification server, html browser,
java web start, java telnet application, LDAP
System and Utilities

Process Resources Monitoring, LOG IM, Contextual Alarm Help
ALMAP Web Platform

LSM, SAS, SEC IM
Third parties components :

Name server : contains object reference to all public objects inside the OMC.
Notification server : offers all notification services internally and externally.
ORB (Object Request Broker) : handles the CORBA protocol (JACORB).
HTTP server is the Apache http server.
Java Web Start enables the end-users to launch application and be confident they have the last version.
AMANDA (Advanced Maryland Automated Network Disk Archiver) is a public domain backup utility.
JTA (Java Telnet Application) is a freeware to open a telnet session.
LDAP is a protocol for accessing directory services (over TCP/IP).
Almap Web Platform components :
LSM (Local Session Manager) GUI portal provides the user login window to access applications.
SAS (Session and Authentication Server) allows to open/close a session and authenticate a user.
SEC (Access Control Manager) manages the user profile access control and the administration of the
applicative logins.
Alarms Manager :
FM (Fault Manager) CUR and HIST manage the interfaces between the IM and the USM components of the
alarms application.
NSP (Name Server Process) keeps the location of agents and managers.
System and Utilities :
Logs and Traces : libraries used by any other OMC component in order to apply a trace in a local file of
major events in the execution of the component, according to the chosen trace levels
Process & Resources Monitoring is in charge of starting third parties and OMC components at boot time
and monitoring them.
Contextual Help is in charge of displaying more help from the NE related Alarm Dictionnary.

1 3 12

The processes and disk status can be displayed in the

following ways :
1.
In the "A1300 XMC state summary window" (without the security

policy only)

2.
Using a CLI command

3.
Accessible from the XMC Home page

Display only form
Administrator rights are required
Using the "Platform Management" GUI

Administrator rights are required

Enables to manage the processes status

Related documentation :
A1300 XMC Platform Administration Administration Guide
Chapter 6 : Processes and resources monitoring procedures

1 3 13
1.4.1 The A1300 XMC state summary

In the XMC Home page (without the security policy).

The display is refreshed every 30 seconds.

1 3 14
1.4.2 XMC processes state via CLI

Open an SSH
session as
axadmin
Execute the
command :
CheckXMC

The display is refreshed every 30 seconds.

1 3 15
1.4.3 The System Resource Monitoring

The processes status supervision is automatic.

The administrator has to regularly control their status, or use the
application before installing a patch, or on Alcatel-Lucent explicit

request
The "Platform Management" GUI enables the administrator
To Stop and reboot the A1300 XMC server
To Manage the processes status
To Display the logical volumes status


1 3 16
1.4.3 The System Resource Monitoring [cont.]

1 3 17
Status display tree and icons :
> Server
> Group of processes
> Processes
> Logical volumes groups
> Disk space status :
> Logical volumes
Green color = normally running

Green : no alarm
Yellow : alarm level 1
Orange : alarm level 2
Red : alarm level 3

1.4.4 Process and disk status

The icon shape and color inform the administrator about the object
status.
> Process group status :
Green : all started
Ligtht grey blue : stopping, (un)freezing, partially running
> Process status :

Green :
running
Blue :
stopped
Light blue : froozen

Blue :
init or stopping

Process Group statuses :

Freezing
Some processes of the group were asked to freeze but are not frozen yet. The others are
either frozen, stopped or running
Frozen
The processes of the group are frozen or stopped
Init
Some processes of the group are in initialization phase. The others are running or stopped
Partially running Some processes of the group are running. The others are stopped or have failed
Running
All processes of the group are correctly running
Stopped
All processes of the group are stopped
Stopping
Some processes of the group were asked to stop but are not yet stopped. The others are
stopped or running
Unfreezing
Some processes of the group are between frozen state and running state. The others are
running or stopped or frozen
Process statuses :
Failed
The process has crashed without operator intervention
Freezing
The process was asked to freeze but it is not yet frozen
Frozen
The process no more write to a particular zone of disk
Init
The process is in initialization phase
Unfreezing
The process is between frozen state and running state
Unknown
Initial status of a process: the process monitoring is waiting for the process status
Running
The process is correctly running
Stopped
The process is not running. Either it was never started or it was stopped by the user
Stopping
The process was asked to stop but it has not yet stopped
1 3 18
1.4.5 Exemple of display


1 3 19
To display the UNIX processes, the CORBA processes or the group of logical volumes, the operator can have one
of the following profiles : Administrator, Operator or Viewer.
Processes families:
Unix => Third parties, Services, External applications
Unix-CORBA => A1300 XMC applications, Communication managers
Logical volumes => disks status

2 Managing the Processes and Resources


13
20
2 Managing the Processes and resources
2.1 How to access to the function

1.
From the A1300 XMC home page, click "Launch WEB portal".
The [ALMAP WEB Portal] window displays.
2.
Click "Platform Management".

A login dialog box displays.
3.
Enter your login (user name and password) values

and click "Authenticate me!"
The [Platform Management] window opens
4.
End.


1 3 21
2.2 The XMC Software Inventory

1 3 22
From the WEB Portal, select Platform Management to discover the
status and information at the different levels.

XMC status
Tree view area

XMC softwares releases
XMC :
Installed
Packages and
Softwares
Releases
Detailed explanations in "Appendix C : How to use the System Resource Monitoring GUI"
of the "A1300 XMC Platform Administration Guide"

2.3 List of PC and Unix clients

1 3 23
List of clients on the current server

Current Server Id
and status
Connected OWPs :
XMC operators
Processes
and
logical volumes
statuses
Connected
UNIX clients
Platform management
historical information

Use the "Session Administration" application GUI to display the list of connected operators.

2.4 Displaying the processes status

1 3 24
Displaying Process
group status
Processes in the group
Displaying
Selected Process
details
Unix process status

CORBA
communication state

Group of processes status : Stopped, Init (some processes are in init phase), Running, Partially running (some
processes are running), Frozen, Freezing (some processes has been asked to freeze), Stopping (some
processes has been asked to stop), Unfreezing.
Unix process statuses : Failed (process has crashed), Freezing (process was asked to freeze), Frozen (process
cannot write on to disk), Init (in initialization phase), Unfreezing, Unknown (process initial status),
Running, Stopped, Stopping (in stop phase).
CORBA communication process statuses : Starting (initialization phase), Running, Backup in progress (no
writing to a disk zone), Unreachable (no more communication with other processes).
Resources details :
#Memory size chart : maximum size of the heap

Red = current relative size of the heap actually used
Blue = relative size of the biggest fre area in the heap
Green = relative size of the memory not allocated in the heap
Detailed explanations in chapter 6.5 of the "A1300 XMC Platform Administration Guide"

2.5 Displaying the logical volumes status

1 3 25
Details on the logical

volumes (filling)
Displaying Logical
Volume group
status
Displaying Logical
Volume status

Resources details :
#Disk volume size chart : maximum size of the disk volume
Note
Red = current relative memory size of the disk volume actually used
Green = relative memory size of the disk volume not used
: the thresholds are defined in Unix data files.
Detailed explanation in chapter 4.9 of the "A1300 XMC Platform Administration Guide"

2.6 Filesystems usage and purge actions

1 3 26
Filesystem
Usage
Purge Action
/alcatel
Data and software for XMC applications
NO
/nedata/perfs
Performance monitoring files

=> Limited storage time (7 days)
NO
/nedata/alarms
Historical alarm files

=> Can grow due to archiving
/nedata/log
Files collected by the NE log export
Manual on alarm
/nedata/scripts
Scripts and results of NE scripting
Manual on alarm
/nedata/backup
NE backup directory
Manual on alarm
/nedata/software Data used by the SVC(software version

change)
Manual

Manual or Automatic
/nedata/backup :
=> the dimensionning should be adapted to the number of supervised NEs for which the backup is available,
and to the types of backups.
No purge action should have to be done outside the automatic purge actions (retention of the last 3 backups by
NE and backup type).
These filesystems ("/nedata/xxx") are not saved with the full backup. They can be saved manually using tar, or
exported to an external server.



13
27
3.1 Choosing the interface

The processes can be managed

From the graphical interface using the "Platform Management"
application
From the command line interface, using putty (SSH session) :

Open a session as axadmin

ServiceXMC <action> <process_id>

<action> in start, stop, check,

<process_id> in XMC|<process-group> | <process_name>
This command can be used interactively.

ServiceXMC


1 3 28
3.2 Stopping a process

Right click
Or : # ServiceXMC stop ashistim


1 3 29
3.3 Starting a process

1 3 30
Right click
Or : # ServiceXMC start ashistim

To restart a process, it is recommanded to restart from the process group level so that the system can ensure
they are started in the right order.

4 Starting and Stopping the XMC Server


13
31
4 Starting and Stopping the A1300 XMC server
4.1 Stop overview

1 3 32
This operation can be required before :
Performing software or hardware upgrade

Using third party software package to perform a backup
Stopping the server in two steps :

1. Stop the XMC applications
2. Stop the Unix/Linux Operating System
SERVER running on
UNIX/Linux Operating System
XMC Application
domain

Before stopping the server :

Check the connected users and warn them about the operation.

4.1 Stop overview [cont.]

1 3 33
Recommandations before stopping the server :

Inform the users about the service interruption
In case of Geographical Redundancy system : first proceed to a
switch-over.
Restart the system
Inform the users when the service is available.

Before stopping the server :

Check the connected users and warn them about the operation.

4.2 Stopping the A1300 XMC

Stopping the XMC applications, via the CLI :

Open an SSH session as axadmin
Enter :
ServiceXMC stop XMC
Wait for all the processes to stop

Check they are stopped by :
CheckXMC


1 3 34
4.2 Stopping the A1300 XMC [cont.]

Stopping the XMC applications, via the GUI :

1 3 35
Select XMC, in the tree view of the "Platform Management" window,

Right-click on XMC Stop, Or Menu : Processes Stop
Press Yes in the Confirmation box

End
Open a UNIX session to the XMC server and type the following command
to verify if XMC is stopped :
CheckXMC


4.3 Stopping the Operating System

1 3 36
Stopping the Operating System :

Log out the [XMC WEB Portal]
Open an SSH or a web console session to the XMC server,
Log-on as user root,
Stop the server using the command:
shutdown -h now
Wait for the system message :

"System has halted,
OK to turn off power or reset system,
WAIT for UPS to turn off power"
Power off the XMC server,

End.

If you are using a server other than an ENMS1 (B2600), you can open a telnet session or Web console through
a web browser.
In the shutdown command, 'now' can be replaced by a delay (seconds).
To power off the server,
after the following message is displayed ,

System has halted
OK to turn off power or reset system
UNLESS WAIT for UPS to turn off power
switch off the units in the recommanded order :

1.
CPU
2.
External units : CD-ROM, streamer, external disks unit, printer

4.4 Starting the A1300 XMC server

1 3 37
After a power on or reboot, the XMC normally restarts automatically.
Otherwise,
Restart the Server through command line :
Power on the A1300 XMC server
Open an SSH session, and Login as user 'axadmin'
Start the processes monitoring by the command :
# StartXMC
wait for a few seconds
Check the Server status in one of the following ways :
The command :
# CheckXMC
Or Open the "A1300 XMC Home page" window,
the "A1300 XMC process state summary" option, and
Check the displayed status is "running",
Select
Inform the users that the server is ready.

If you are using a server other than an ENMS1 (B2600), you can open a telnet session or Web console through a
web browser.
To power on the server, proceed in the following order :
1.
External units : CD-ROM, streamer, external disks unit, printer
2.
CPU

4.5 Rebooting the A1300 XMC server

1 3 38
Before operation, notify all users and check they are disconnected
Procedure :
In the tree view of the "Platform Management" window, select XMC
Right-click on XMC Stop, Or Menu : Processes Stop
Press Yes in the Confirmation box
Open an SSH session, and Login as user 'axadmin', then 'root'
Reboot the server by :
# shutdown r now
Once the reboot is completed, the A1300 XMC permanent processes automatically
restart.
Checkings :
Check the A1300 XMC status is "running" in the "A1300 XMC process state summary"
window.
On the A1300 XMC line, check that the displayed status is "running"
End

You can check which users are connected when selecting the Server level in the "Resource Monitoring" tree.

XMC processes management

1 3 39
Which of these users can manage the XMC processes ?

root
axadmin
Any user with 'administrator' profile
You must be 'root' to stop the server ?

yes
no
After a 'reboot', all the processes

have to be restarted manually ?

Restart automatically ?

In which order have you to stop the HP units

(1=CPU, 2=disks, 3=external units) ?
> ________>________>________


OMC processes management
Exercise
1 3 40
Display the processes and logical volume status

On the teacher request, Stop, and restart a process
(ex: fmcurusm, fmhistusm, pmim, supim, topim,)

One group is asked to Stop the server, and to restart it
(15 min)
One group is asked to Proceed to a server reboot (15
min)
20'




for this module


13
41


13
42
2 OMC processes management

1 3 43
Which of these users can manage the XMC processes ?

root
axadmin

Any user with 'administrator' profile
You must be 'root' to stop the server ?

yes

no
After a 'reboot', all the processes

have to be restarted manually ?

Restart automatically ?

Processes Restart in the same state as before the reboot

In which order have you to stop the HP units

(1=CPU, 2=disks, 3=external units) ?
> _1_>_2_>_3_ OR > _1_>_3_>_2_


End of Module
XMC Processes Management


13
44
14
Section 1
Module 4
Backup and Restore


Blank Page
XMC System administration Backup and Restore

14
Document History
Edition
Date
Author
Remarks
01
2009-02-27
RANNOU, Raymond
First edition
02
2009-04-21
RANNOU, Raymond

Objectives
14
To be able to perform backup and restore operations on
the XMC server.


Objectives [cont.]

14

Table of Contents
14
Page

1 Functions presentation
1.1 Data Backup/Restore overview
1.2 Backup and Restore operations
2 Data Backup Operation
2.1 Backup features
2.2 Executing a data backup
2.3 To schedule a data Backup
2.4 Check the backup archive
3 Data Restore Operation
3.1 Data Restore
3.2 Data Restore procedure
4 Full Backup Operation
4.1 Full Backup prerequisites
4.2 Full Backup execution (HP-UX)
4.3 Checking the Full Backup media (HP-UX)
4.4 Full Backup execution (Linux)
4.5 Checking the Full Backup media (Linux)
5 Full Restore Operation
5.1 Full Restore prerequisites
5.2 Full Restore procedure (HP-UX)
5.3 Full Restore procedure (Linux)
6 Exercises

7
8
9
10
11
12
14
15
16
17
18
20
21
22
23
24
25
27
28
29
31
33


This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

14
14


1.1 Data Backup/Restore overview

148
Two types of backup/restore operations

The data backup and restore operations.
The full disks backup and restore operations.
can be used :
The data backup allows saving

all configuration information
NE related data : alarms, topology
Destination : file, streamer
NB : No incremental backup is available
The Full disks backup/restore allows to copy
all system files and data to an external support
(except /nedata/xxx filesystems)
Destination : streamer only
All
the operations are performed from a Unix window.

Operations duration :
- data backup or restore : 5 to 15 min
- full backup or restore : 45 to 75 (depending on disk content)
Documentation : "Platform Administration Guide", chapters 12, 13 and 14.

1.2 Backup and Restore operations

149
When to proceed to backup and restore operations ?

-new release
installation
-Installation of a new
application
-System crash
-hardware bug
-disks OOS
Full backup # b
Full backup # a
Life of the
OS
4
OS data backup
tape #1

10
11
12
Full restore
OS data restore
tape # b
tape #10

14
2 Data Backup Operation


10
2 Data Backup operation
2.1 Backup features

1 4 11
The XMC data backup feature permits creating backup archives to:
the tape device connected to XMC,
a file in a local XMC filesystem.
Before running the backup, notify the users about the service
interruption.
XMC data backup can be launched :
Manually (interactive), using the corresponding unix command
By an automatic schedule, from the cron facility
The XMC processes are automatically frozen during the backup

Before each scheduled backup on tape, the operator must insert the good tape in the unit, and it is mandatory
to use the same order at each new backup operation.

2.2 Executing a data backup

1 4 12
Backup to TAPE
Before execution:

Check if the drive unit is connected and in service with a valid tape.
1. Open a SSH command window

2. Logon as user 'root'
3. Launch the command :
# /alcatel/omc1/OMC_OSM/backup_scripts/data-backup.pl
Successful completion will end with the message :

End : data-backup completed
Logs of backup process are stored in the following file :

/alcatel/omc1/data/traces/data-backup.traces

Before the backup,
- advise the users that service will be interrupted.

- do not perform any Security Management operations.
The script automatically selects the first tape drive configured on XMC server. However, if you are using
another tape drive, you can specify explicitely the (non-rewinding) device path in command line, for example:
# /alcatel/omc1/OMC_OSM/backup_scripts/data-backup.pl tape /dev/rmt/c4t1d0BESTn

2.2 Executing a data backup [cont.]

1 4 13
Backup to FILE
Open an SSH command window
1. Logon as user 'root'
2. Launch the command :
# cd /alcatel/omc1/OMC_OSM/backup_scripts
# ./data-backup.pl file [file_name]
Give the [file_name] in full path
Successful completion will end with the message :

End : data-backup completed
Files are stored in the directory : /nedata/backup
Logs of backup process are stored in the following file :

/alcatel/omc1/data/traces/data-backup.traces

Before the backup,

Syntax and parameters for the data-backup.pl command :
data-backup.pl [-h(elp)] [-t(ape) [tape-device]] | [-f(ile) [file-dest] [-c(leanup)] [-k(eep) <nb>]]

-h
to display the command use and syntax
-t (tape-device)
to specify the destination device (non-rewind devices)
-f (file-dest)
file archive name (in absolute address).

Default : /nedata/backup
The archive filename is built according to rule: <xmc-name>__xmc_data_backup__<date-time>.tgz

-c
to clean obsolete backups
-k <n>
to keep the <n> last backups

2.3 To schedule a data Backup

1 4 14
The schedule data backup is based on the Unix cron facility.

Open a Unix command window
Logon as user 'root'
Check existing scheduled tasks to avoid conflicts, using :
# crontab l
List axadmin tasks :
# crontab l axadmin
# crontab -l u axadmin
(for HP-UX)
(for Linux)
Save the current crontab content to a file
# crontab -l > /tmp/mycrontab

# crontab -l > /tmp/mycrontab.old (second copy)
Edit the /tmp/mycrontab file (using vi or nedit)
Modify the file, and save the changes
Register the changes by
# crontab /tmp/mycrontab
Check the changes using :
# crontab l
Structure of the crontab file :

Minute hour monthday month weekday command_to_run
- minute of the hour : 00-59
- hour of the day : 0-23
- day of the month :1-31
- month of the year : 1-12
- day of the week : 0-6 (0=Sunday)
- command to run
In the crontab, use the command sc-data-backup.sh (instead of data-backup.pl) : same syntax.
Exemples :
1.To schedule a daily backup at 4h00 from Monday to Saturday, to default archive file, cleaning previous backups
except the last 2 ones :
00 04 * * 1-6 /alcatel/omc1/OMC_OSM/backup_scripts/sc-data-backup.sh f c k 2 >/dev/null
2.To schedule a a weekly backup at 18h58 to tape, on sundays :
58 18 * * 0 /alcatel/omc1/OMC_OSM/backup_scripts/sc-data-backup.sh tape >/dev/null

2.4 Check the backup archive

1 4 15
When ?
After a backup to check the tape or file archive
To check a file archive :

Open an SSH session and login as user root,
Run the command :
# gtar -gzip tvf /nedata/backup/<archive_file_name>
To check a tape archive :

Open an SSH session and login as user root,
Run three times the command :
# gtar tvf /dev/rmt/c4t3d0BESTn
(for HP-UX)
# gtar tvf /dev/nst0
(for Linux)
or
Rewind the tape :
# mt /dev/rmt/0m rew
(for HP-UX)
# mt /dev/nst0 rew
(for Linux)
or

Checking a tape archive in 3 times:

-
the first command will list the file .tgz.info
The second command will list nothing
The third command will list all the files in the .tgz archive.

14
3 Data Restore Operation


16
3 Data Restore operation
3.1 Data Restore

1 4 17
Data restore can be processed

A- From tape
B- From file stored on XMC server
Cautions :
To be performed with the exact same A1300 XMC software version as
the last backup.
Warn users about the service interruption.

Before the restore,


3.2 Data Restore procedure

1 4 18
A- Restore from TAPE :

1.
2.
3.
4.
5.
Open an SSH session and login as user root

Protect and Insert the latest backup tape ('write' protect the tape)
Check the XMC permanent processes are stopped, else stop them by
# ServiceXMC stop XMC
Run the restore command :
# /alcatel/omc1/OMC_OSM/backup_scripts/data-restore.pl
Successful completion will end with the message
End : data-restore completed
6.
Restart the processes using :

# StartXMC
7.
End.

Logs of data restore process are stored in file : /alcatel/omc1/data/traces/data-restore.traces.

3.2 Data Restore procedure [cont.]

1 4 19
B- Restore from FILE :

Prerequisite(s) : A file Archive is available on XMC.
Open an SSH session and login as user root
2. Check the XMC permanent processes are stopped, else stop them by
# ServiceXMC stop XMC
3. Run the restore command :
# ./data-restore.pl f file_name
1.
give the file_name in full path.

4.
Successful completion will end with the message

End : data-restore completed
6.
Restart the processes using :

# StartXMC
7.
End.

Before the restore,

Syntax and parameters for the data-restore.pl command :
data-restore.pl [-h(elp)] [-t(ape) [tape-device]] | [-f(ile) [file-archive]] [-l(ist)]
-h
to display the command use and syntax
-t (tape-device)
to specify the destination device (non-rewind devices)
-f (file-archive)
file archive name (in absolute address). The companion information file - suffixed
with '.info' - must exist in the same directory.
The archive filename exemple: <ne-name>__xmc_data_backup__<date-time>.tgz
-l
to list the archive content
Logs of data restore process are stored in file : /alcatel/omc1/data/traces/data-restore.traces.

14
4 Full Backup Operation


20
4 Full backup operation
4.1 Full Backup prerequisites

1 4 21
This operation allows to copy the full disk(s) content on external support.
To be done :
- After the XMC installation
- To be able to restore quickly the data after disks crashes
Prerequisites :
1. Check that each disk volume is below 80% (filling percentage)
2. The files must have sizes below 8 Gbytes
3. The local tape drive is connected to the server and configured
Preliminary actions :
Warn users that service will be interrupted
The XMC must be stopped before launching the operation :
# StopXMC

At the beginning of the backup, an estimation of the number of needed tapes is done. And a message displays the
number of needed tapes.
To check the filling percentage use the bdf command.
Documentation in "Platform Administration Guide",

Chapter 13, for HP-UX
Chapter 14, for Linux

4.2 Full Backup execution (HP-UX)

1 4 22
Steps :
1. Open an SSH session, and login as user root
2. Go to the backup_scripts directory :
3.
Enter the command

# ./fullbackup.sh backup
4.
Information on the current backup are displayed

>
>
>
5.
Number of needed tapes

Message to insert the tape(s)
The backup progress .
The backup ends with the following message :

Full backup was successfully performed
Now protect all your tapes against writing.
Bye.
6.
After the backup operation,

>
>
Protect the tape

Start the XMC.

After the full backup is finished, you can consult the log file "/alcatel/omc1/data/traces/fullbackup.trace".

4.3 Checking the Full Backup media (HP-UX)

1 4 23
Purpose : to check if you can boot on tape

Steps :
2. Determine the drive filename ("..BESTn" file) :
# ioscan funC tape
3.
Insert the tape, and check the media by the command

# mt -f /dev/rmt/c4t3d0BESTn rew
# mt -f /dev/rmt/c4t3d0BESTn fsf 1
# pax v f /dev/rmt/c4t3d0BESTn
4.
If the bdf command shows "../vg01/.." filesystems, they can be

checked by
# vxrestore v -t -f /dev/rmt/c4t3d0BESTn
The duration of the pax command will depend on size of the data stored
during the full backuo (about 1 hour).


4.4 Full Backup execution (Linux)

1 4 24
Steps :
2. Go to the backup_scripts directory :
Enter the command

# ./fullbackup.sh backup
4. Information on the current backup are displayed
3.
>
>
5.
Message to insert the tape(s)

The backup progress .
Wait for end of backup message:

-I- BACKUP FINISHED SUCCESSFULLY on <date-and-time>
-I- WARNING : Do not forget to check integrity of Full Backup TAPE
-I- this can be done with /alcatel/omc1/OMC_OSM/backup_scripts/checkTape.sh script
-I- Restarting XMC <date-and-time>
Done
The XMC restarts automatically

7. Protect the tape after the backup operation.
6.

The contents of backup tape must be verified before removing the tape. To run this sanity check, enter:
#/alcatel/omc1/OMC_OSM/backup_scripts/checkTape.sh
This can take time, please wait . This check will show a status for each filesystem, and lasts approximately
as long as backup creation. Wait for successful end of execution message including:
-I- TAR file are all OK
-I- More info in log: /var/opt/mkcdrec/mkcdrec.log
Finish test on <date-and-time>
After the full backup is finished, you can display the log files using :
# more /var/opt/mkcdrec/mkcdrec.log

4.5 Checking the Full Backup media (Linux)

1 4 25
Purpose : To check the content of the backup tape.

After the backup, before extracting the tape,
Perform the following checking,
# /alcatel/omc1/OMC_OSM/backup_scripts/checkTape.sh

This check will show a status for each filesystem, and lasts
approximately as long as backup creation.
Wait for successful end of execution message including:
-I- TAR file are all OK
-I- More info in log: /var/opt/mkcdrec/mkcdrec.log
Finish test on <date-and-time>

# more /alcatel/omc1/data/traces/fullbackup.trace

4.5 Checking the Full Backup media (Linux) [cont.]

1 4 26
Purpose : To check if you can boot from the tape.

Steps :
1. Open a console session, and login as user root
2. Insert the (first) tape in the drive
3. Perform a reboot using,
# cd /
# shutdown r y now
4.
The system goes down and reboot

After the memory check and the message
.USB Tape-based One Button Recovery Disaster (OBDR) drive detected
<<< Press F8 for configuration option >>>
5. Press F8 and select the OBDR mode (2).

>
>
The tape drive should have its 2 green and amber leds flashing.
The server boots on tape and a splash screen is displayed :
"System can be restored from the tape"
This means that tape is bootable, and system can be restored from tape.
6.
Press CTRL-C to reboot the system.

# more /alcatel/omc1/data/traces/fullbackup.trace

14
5 Full Restore Operation


27
5 Full Restore operation
5.1 Full Restore prerequisites

1 4 28
This operation will restore the content of a previous full backup tape(s).
To be done :

After a complete disks crash

To come back to a previous configuration
Preliminary actions :

Warn users that service will be interrupted

The XMC must be stopped before launching the operation


5.2 Full Restore procedure (HP-UX)

1 4 29
Steps :
1. Insert the (first) tape to restore
3. Perform an immediate reboot :
# cd /
# shutdown r y now
During the reboot, take care at the message :
4.
"To discontinue press any key within 10 sec"

Then,
> Press the space bar to prevent normal booting (from disk)
> Insert the tape in the drive
Determine the tape boot unit, by entering :
5.
Search
The device numbers (Path #) are displayed
Continue the boot sequence by
6.
Boot Pi
("P# " where Device Type = "Sequential access media")

The device numbers will be displayed as follow with a RP4440 server:

Path #
Device Path
(dec)
Device Path
(mnem)
Device Type)
IODC rev
P0
0/1/1/0.1
Intscsia.1
Random access media
P1
0/1/1/1.0
Intscsib.0
Random access media
P2
0/2/1/0.1
Random access media
P3
0/2/1/0.3
Sequential access media
In this example, the path number is P3 for the tape device (Sequential access media).

5.2 Full Restore procedure (HP-UX) [cont.]

1 4 30
System will boot from the selected tape unit

8. If more than one tape have to be restored, a message will ask to
insert the next tape :
7.
" pax: Ready for volume i" .

> Enter the next tape
> Press Enter
9.
At the end of the restore,

>
>
Check the log file content :

/alcatel/omc1/data/traces/fullrestore.trace
Complete the restore (if necessary) by the data restore
10. Start the XMC server.

After the full restore, activate the mirroring (if available) by :

# /install/scripts/createExtendFS.sh start
This action will take about 1H, and can be launched after the server is restarted.
The progress information can be displayed by :
# tail f /install/install.log

5.3 Full Restore procedure (Linux)

1 4 31
Steps :
1. Insert the (first) tape to restore
2. Open a Web console session, and login as user root
3. Perform an immediate reboot :
# cd /
# shutdown r y now
4.
During the reboot, take care at the message :

.USB Tape-based One Button Recovery Disaster (ODBR) drive detected
<<< Press F8 for configuration option >>>
Then, press F8 and select the ODBR mode (2)

See Note below
5.
The system boots on the tape, and a splash screen is displayed,

>
6.
Press Enter to start
Second stage of the boot is performed

Note : If DAT does not enter the OBDR mode (green and amber led of DAT must flash simultaneously), then try
method 1 of Appendix G (Platform Administration Guide).

5.3 Full Restore procedure (Linux) [cont.]

1 4 32
7.
At the shell prompt, enter the following commands

>
>
8.
cd /etc/recovery
./start-restore.sh
At the confirmation message,

press q to quit or any other key to continue .
Press Enter to continue (or 'q' and Enter to quit)

10. At the end of the restoration, this message is displayed
9.
System has been successfully restored
11. Reboot the XMC server by entering :
# busybox reboot
12. Start the XMC.

After the full restore, activate the mirroring (if available) by :

# /install/scripts/createExtendFS.sh start
This action will take about 1H, and can be launched after the server is restarted.
The progress information can be displayed by :
# tail f /install/install.log

Backup - Restore
6
Exercises
1 4 33
Exercise 1 :
1.
Open an SSH session from your terminal
2.
Data Backup :
Display the last backup information
Proceed to a manual backup
Check the backup cycle status

3.
Data Restore :
Restore the previous backup tape
20'+20'


Backup - Restore
Exercises
1 4 34
Exercise 2 :
1.
Open an SSH session from your terminal
2.
Full Backup :
Proceed to the full backup
Check the backup traces

3.

Full Restore (-> at break time) :

Restore the previous backup tape
Check the log
15' + 45'



14

for this module


35
14
End of Module
Backup and Restore


36
15
Section 1
Module 5
AS Administration


Blank Page
XMC System administration AS Administration

15
Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks

Objectives
15
To be able to administrate the current alarm list (CAL),
to set Auto-filters and to configure alarms aging actions.


Objectives [cont.]

15

Table of Contents
15
Page

1 CAL Administration actions
1.1 CAL Administration operations
2 The CAL Administration window
2.1 Setting CAL Administration parameters
2.2 CAL Administration settings
3 Managing the Auto-Filters
3.1 Locating the filters
3.2 Using the Archiving filter
3.3 Creating an Archiving filter
3.4 Using the Auto-Purge and Auto-ACK filters
3.5 Auto-Purge and Auto-ACK filters
4 Alarms Aging Actions
4.1 Using the Alarm Aging administration
4.2 Defining an Alarm Aging action
5 Alarms Trigger Actions
5.1 Using the Alarm Trigger administration
5.2 Defining an Alarm Trigger action
6 Alarms Severity Change
6.1 Alarms Severity Change Administration
6.2 The Severity Change view


7
8
9
10
11
12
13
14
16
17
18
19
20
21
22
23
24
25
26
27

15

This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

15
1 CAL Administration actions


1 Current Alarm list Administration Actions
1.1 CAL Administration operations

158
The CAL Administration interface can be used :

To set overflow and purging criterias
To define Archiving filter characteristics
To define Auto-Purge characteristics
To define Auto-TT characteristics (if available)
To define Auto-ACK characteristics
To access the Aging List and Trigger List
To perform Fault management Resynchronization


15


2.1 Setting CAL Administration parameters

1 5 10
Open the "Current Alarm List" sub-domain,

From the menu, select
Alarm Sources Administration IM as<server>
Then from the IM Administration window,

Modify the parameters in the CAL Administration tab
Click Apply


2.2 CAL Administration settings

1 5 11
Select "CAL Administration"

Number of purged alarms,
in case of overflow
Purging criterias
CAL Filling percentage status
Current number of alarms in CAL

Overflow mode :
Wrap : Specifies that when the Current Alarm List is full, the oldest alarms will be
overwritten.
Halt : Specifies that when the Current Alarm List is full, no more alarms will be
received until action has been taken to reduce the number of active alarms.
New raised alarms are lost.
CAL Status :
Normal
The number of alarms in the CAL is lower than the Warning Filling %
threshold : color is white.
Warning The number of alarms in the CAL is greater than the Warning Filling %
threshold, but lower than the CAL Size : color is yellow.
Overflow The number of alarms in the CAL equals the CAL size : color is red.

15


12
3.1 Locating the filters

1 5 13
AS operator
Static analysis
Real time management

Auto-beeping
Alarm retrieving
Archiving filter
C.A.L.
size
Current
Alarm List
C.A.L
Overflow purge
Historical
Alarm List
H.A.L
Auto-acknowledgement
Auto-purge
Non Archived
alarms
Network
ressources

Fault Management
Alarms filtering

3.2 Using the Archiving filter

1 5 14
This filter defines the archiving characteristics.

Default filter :
all the Cleared and Acknowledged alarms will be archived.
The archiving filter specifies that only alarms matching the
defined archiving filter are archived in the alarm historical list.


3.2 Using the Archiving filter [cont.]

1 5 15
Automatic filters
User-defined filters
Filter(s) description
and selection


3.3 Creating an Archiving filter

1 5 16
5
2
3
6

To create a new Archiving filter (personal filter) :

1.
Select New
2.
Enter the new Filter Name
3.
Press More to define as many matching criteria as needed. A logical AND will apply
between the criterias.
4.
Press OK
Filter activation :
5.
Check the box for the filter to be activated.
6.
Press Apply, to validate this filter.

3.4 Using the Auto-Purge and Auto-ACK filters

1 5 17
The Auto-Purge filter enables
to specify that the matching
alarms
will not appear in the Current Alarm List
and will not require operator action.
Auto purged alarms are archived in the Historical Alarm List

(according to the archiving filter conditions) .
The Auto-ACK filter enables

to specify that the incoming matching alarms will be automatically
acknowledged.


3.5 Auto-Purge and Auto-ACK filters

1 5 18

Indications for the "Rules" :

-
to define a time period define the rule like :

Event Date & Time Equals "2006/03/12 00:00:01 < 2006/03/15 23:59:59"

15


19
4.1 Using the Alarm Aging administration

1 5 20
Alarm aging = Definition of automatic actions (acknowledge, trouble

ticket, purge requests, expiration task, triggering and manual clear)
performed periodically on alarms of the Current Alarm List

whose status (raised, acknowledged, cleared) is set from a given time
and filtered.
All the conditions are operator defined.
Several aging conditions can be active at the same time.
By using Alarm Aging administration you can:

create a new alarm aging configuration,
edit an alarm aging configuration,
Activate/deactivate an alarm aging configuration,
delete an alarm aging configuration.


4.2 Defining an Alarm Aging action

1 5 21
2
1
5
4
1. Select the New folder, in Aging

2. Enter a name for the filter
3. Define the "On " conditions and the "Do " actions, and the filtering criterias,
4. Press "Apply" to save the filter
5. Select the filter to activate and press "Apply"

15


22
5.1 Using the Alarm Trigger administration

1 5 23
Alarm Trigger = triggering consists in invoking external actions when an
alarm is being inserted in the Current Alarm List.
Fault Management automatically sends a command message (script or
navigation order) to the triggering server when the number of alarms

crosses (up or down) operator defined threshold conditions associated
with a given triggering filter.
The triggering mechanism allows the execution of processes on the
Fault Management servers without needing active Fault Management

client sessions.
By using the Alarm trigger administration you can:

create a new trigger,

edit an alarm trigger configuration,
Activate/deactivate an alarm trigger configuration,
delete an alarm trigger configuration.


5.2 Defining an Alarm Trigger action

1 5 24
2
1
3
5
4
1. Select the New folder, in Trigger

2. In the Definition folder
Enter a name for the filter
select "Enable Trigger"
In the Filter folder, define the filtering actions
3. In the Mail/SMS folder, define the mailing action(s)

4. Press "Apply" to save the configuration
5. Press "Apply" to activate the triggering action

15


25
6.1 Alarms Severity Change Administration

1 5 26
Alarm Severity Change consists in defining conditions to change the
alarms Severity.
This change

will apply on new incoming alarms after activation

is not propagated to the 3GPP North interface.
The original severity of an alarm can be displayed in the alarm sublists
using the Original Perceived Severity attribute.

It is not recommended to modify the default sublists configuration (to retrieve the Original
Perceived Severity and filters) :
Main Alarm List
Critical
Major
Minor
Warning
Clear
Indetermined

6.2 The Severity Change view

1 5 27
Select the Severity Change
tab.
Press New to create the new
condition to apply.
In Definition tab, enter

The Filter name

The new severity
In Filter tab
Define the alarm filtering

conditions
Press Apply
Check the Activation State
box to apply the change.

Press Apply.


AS Administration
Exercises
1 5 28
CAL Administration :
Analyse the content of the CAL administration tab
Exercise 1 :
Create a filter to acknowledge alarms coming from a
given NE (ask the teacher, one NE per group if possible)
Generate alarms on this NE, and
check for the statuses and dates : Acknowledgement,
Clearing, Reservation,
Acknowledge the alarms
Solve the default the alarms are removed
Remove the filter
Duration
10'


AS Administration
Exercises
1 5 29
Exercise 2 :
Create a filter to auto-purge alarms coming from a given
NE (ask the teacher)
Generate alarms on this NE
In CAL, check that no alarm appears
Retrieve those alarms in HAL
Remove the filter
Duration
15'



15

for this module


30
15
End of Module
AS Administration


31
16
Section 1
Module 6
System Management


Blank Page
XMC System administration System Management

16
Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks

Objectives
16
To be able
to display the XMC logs and system trace files
to clean files
To customize the common system parameters.


Objectives [cont.]

16

Table of Contents
16
Page

1 The XMC Logs and trap files
1.1 Logs collection management
1.2 Logs files content
1.3 Logs files management
1.4 Displaying the log files
1.4.1 From the Welcome page
1.4.2 From an SSH session
1.4.3 From the Network Management view
1.4.4 Importing the log files
2 The processes trace files
3 Cleaning files
3.1 What to clean and when?
3.2 Checking the disks space
3.3 Cleaning alarms historical files
3.4 Cleaning core files
4 System parameters customizations
4.1 Common Configuration
4.2 Server Common Configuration
4.3 SNMP NBI Configuration
5 Exercises
5.1 Exercises : Logs
5.2 Exercises : Cleaning


7
8
10
11
12
13
15
16
19
20
23
24
25
26
29
30
31
32
33
34
35
36


This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

16
16


1.1 Logs collection management

168
The XMC provides a centralized Network Element (NE) and

XMC log management applicable to a subset of supervised
NE types :
collects Operation, Administration and Maintenance (OAM) logs
periodically or on-demand on all different NEs,
parses this log information and saves it in a database,
provides an interface to manage log collection information.
manages log records retention in database based on a configured
retention duration.

The XMC provides a centralized log management for:

Atrium Distributed Mobile Switching Center (DMSC) NEs,
AlcatelLucent ATCA-based Common Platform NEs,
5350 ASR (Application Server Runtime) platform-based NEs.
XMC.

1.1 Logs collection management [cont.]

169
Collection periodicity
NE logs are collected automatically or on operator request

(see User Interface Handling).
Periodic collection :
Each family of NEs and the XMC have their own frequency of log
collection,
The default value is one hour.
On Demand collection :
The collection period corresponds to the period between the last

collection time and the current time.

By default, when you create an NE, the collection management data is created in the database, but no collection is
done as long as the NE is not supervised.
Once the NE is supervised, the XMC starts collecting logs between the last collected date/time and the current
date/time. For the very first log collection, the XMC collects all the data available on the NE.
To avoid high activity peak, the XMC does not carry out the collection/parsing process for each NE simultaneously.
The collecting time of an NE depends on the date/time of the NE supervision.
On-demand collection is available only for supervised NEs which have a collect started, otherwise the option is
disabled.

1.2 Logs files content

1 6 10
What is recorded in XMC logs ?

Operator commands.
Events (NE, XMC)
Types of logs :

log_file_<n>
sas_log
secserver<n>_log
operators actions
sessions authentications
security server modifications
Traps files record traps of events (system misbehaviors) :

trap_file_<n>

Events, logs and traps are recorded in files with the UTC time.
Files types :
logs : log_file_<n> n=[0-9]
traps : trap_file_<n> n=[0-9]
portal accesses : sas.log

1.3 Logs files management

1 6 11
How are the XMC logs and trap managed ?

In circular files
Data is added at the end of the last active log
When the current file is full, the next one is used
When the last one (10th) is full, the first one is used
To save a log file, you can

Make a copy of the file (under Unix/Linux)

Export data for a selected period


1.4 Displaying the log files

1 6 12
The log files content can be displayed :

From the welcome page (without the security policy)
Using Unix/Linux commands
From the "Network Management" view, in the Log tab


1.2 Displaying the XMC Logs files
1.4.1 From the Welcome page

1 6 13
From the XMC welcome page (without the security policy) :

Click on "XMC log files the log files list is displayed on the right
Select a log file the selected file content replaces the files list


1.4.1 From the Welcome page [cont.]

1 6 14
Recording time : <year><month><day><hour><minute><second>.<miliseconds>Z

(Z=UTC time)
Records format :
EventTime;EventId;EventLevel;EventSource;EventAffected;EventDescription;
EventType;AdditionalInformation
Exemple :
20050901071023.798Z;setSupervisionState;INFO;Operator.axadmin(w0055154);Charging
Gateway.Chartres();SUP - Set supervision state;EVENT.setSupervisionState;free_text.action=start
For a better analysis, the log file can be exported to the OWP, and displayed using any more friendly tool
(Excel, Notepad,).
For more details, see "Operator Administration Guide", Appendix I : "Log files format"

1.4.2 From an SSH session

1 6 15
To access the log files from an SSH session :

Open an SSH session
Go to the logs directory :
# cd /alcatel/var/export/pub/omc/log
Display the log content using :
# more <log_name>

To display the XMC portal log file content, select the sas.log file
Use the same procedure to display
the trace files content : trap_file_*
the security access files content : secserver_1.log.*, sas.log
System trace files can be displayed from the "/alcatel/omc1/data/traces" directory.

1.4.3 From the Network Management view

1 6 16
To display the Log from the Network

Select the "NE Log Information" sheet,
Select the log from the list,
Right-click "Launch Log Browsing"

Management view :

1.4.3 From the Network Management view [cont.]

1 6 17
Exemple of Log Browsing :


1.4.3 From the Network Management view [cont.]

1 6 18
Filtering the display on :

Date and time
NE friendly name
Log type
Event type
Event level
Operator name

NE Friendly Name : list of declared NEs

Log Type : Access, Action, Error, Event

1.4.4 Importing the log files

1 6 19
Additional actions on displayed data Import

to retrieve previously exported files.
Log Files can be imported
From the operator position

(OWP)
From the XMC server
From any external
server
Servers can be configured from the Platform Management application:

XMC Configuration > Log Export Remote Server

Exported logs are saved in the default directory on the XMC server :
- immediate export : /nedata/log/export/immediate/log,

- scheduled export : /nedata/log/export/scheduled/log/
Log files imported from the OWP terminal (CSV format)
Default directory : D:\Documents and Settings\<userid>\Logs

16
2 The processes trace files


20
2 The trace files
Trace files display

1 6 21
For debug and analysis purpose, the XMC store data related
to the processes (applications).
These files
are only accessible via SSH.
Are located in directory :
/alcatel/omc1/data/traces/
You can use vi (or more or cat, or any other viewer) to

display the files content.

The XMC provides a centralized log management for:

Atrium Distributed Mobile Switching Center (DMSC) NEs,
AlcatelLucent ATCA-based Common Platform NEs,
5350 ASR (Application Server Runtime) platform-based NEs.
XMC.

2 The trace files
Trace files display

1 6 22
Exemple of trace files management:


16
3 Cleaning files


23
3 Cleaning Files
3.1 What to clean and when?

1 6 24
When do you need to clean or remove files ?

When they are no more available
To free disk space
Which files can you clean/remove ?

Historical Alarms files
Log files
Core files


3 Cleaning Files
3.2 Checking the disks space

1 6 25
When
do you need to check for the logical volume filling

percentage ?
Weekly
Before a data backup on disk
To
identify the disk space used in the filesystems, and

present file archives, you can use the following commands:
To check global usage on file system :
HP-UX: # bdf
on LINUX: # df -k
on
To check occupation caused by backup-dir only:
# du -sk <backup dir>


3 Cleaning Files
3.3 Cleaning alarms historical files

1 6 26
When do you need to clean alarms from history ?

When you decided they are no more available
First choice : purging oldest alarms

Login as axadmin user (SSH session)
Enter the commands:
# cd /alcatel/omc1/OMC_FMCF/scripts/
# ./purge_histo_alarms.pl [ -r<retention_duration>] [ init | exec | stop ]
Exemple :

Parameters of the purge_histo_alarms command :

no parameter : to display the command help
-r : retention duration in days (default 60 days)
Execution parameters :
init : to register the command in the crontab
stop : te remove the command from the crontab
exec : for immediate execution

3 Cleaning Files
3.3 Cleaning alarms historical files [cont.]

1 6 27
Second choice : from the Platform Management window

Login as axadmin
Open the Platform Management application
Select the XMC Configuration tab > Historical Alarm Files Purge
To display/set the purge hour

To display/set the purge minute
To display/set the retention time
Retention time = number of days to be kept in the history.


3 Cleaning Files
3.3 Cleaning alarms historical files [cont.]

1 6 28
Third choice : removing files manually

Login as administrator to open a UNIX window
Enter the commands:
# cd /nedata/alarms/histDB/<year>[/<month>[/<day>]]
# rm <file_to_delete>
Year 2008
Months : 1:January /
2:February / 3:March
Archived days for
February

The <file_to_delete> can be :

- a day : to delete the the historical data for the corresponding day
- a month : to delete the the historical data for the corresponding month
- a year : to delete the historical data for this year

3 Cleaning Files
3.4 Cleaning core files

1 6 29
When do you need to clean core files ?

To free disk space, when they are no more available
How to proceed ?

Login as user root to open a UNIX window

To find the core files, and display their size and location, enter
# find / -name core type f exec ls l \+
File Size(bytes)
To remove data file(s), enter (for exemple) :

# rm /etc/opt/resmon/core

The Unix/Linux help for the find command is available using :

# man find
-type f
to display data file only (not the directories)
-exec \+
to execute any unix/linux command on the find result

Files location
16


30
4.1 Common Configuration

1 6 31
Following customizations can be done from the Platform

Management application :

Backup checksum control : time and frequency of the backup files checksum control mechanism. To activate
this mechanism, set to true the Backup checksum control activation parameter in the NE configuration of
the NE type considered (only available for NEs from TOMIX architecture). See this parameter configuration in
section 4.7
Banner : customization of the banner that is displayed :
in the browser when the operator connects to the XMC application,
in the terminal when the operator connects to the XMC server.
Historical Alarm Files Purge : time and frequency of the historical alarm files purge mechanism,
Log Export Files Cleanup : time and frequency of the log export files clean up mechanism,
Performance Files Cleanup : time and frequency of the performance files clean up mechanism,
Performance Files Recovery : duration of the performance files recovery,
XMC Gateway : configuration of the XMC when used as a proxy server for the Atrium based NE. When the
XMC is used as a proxy server, the communication between the NE client application (WEM) and the NE server
will go through the XMC server using pre-defined range of ports.

4.2 Server Common Configuration

1 6 32

Common configuration
applicable to the different
types of server :
- backup server,
- log export server
- and software server.

The default server can be the XMC itself, in that case a specific Ethernet interface can be reserved for that
purpose, or it can be an external machine. Choice of one or the other is done during XMC
installation/upgrade and using this interface.
Additional server creation : To create an additional server, select the .... Server1 node, right click, and
choose Create in the popup menu. A new server instance is automatically created with a new instance
number.
Server deletion : To delete a server previously created, select the .... Server n node (n value greater than
1), right click, and choose Delete in the popup menu.
Configuration : configuration of the server, in case of the server configuration must be changed (IP@, disk
space, path) the parameters must be updated in order to reflect the new situation.
Credentials : describes the login/password used to communicate with the server according to each protocol.

4.3 SNMP NBI Configuration

1 6 33

Group of parameters
supported to configure the
SNMP North Bound Interface
used between the XMC and
an external OSS.

NBI Config : describes a list of parameters to configure the SNMP North Interface agent on the XMC :
Agent port number : port number on which the agent on the XMC listens to the SNMP GET requests from
the OSS.
SNMP version : SNMP version used by the agent on the XMC. See SNMP V2 Config or in the SNMP V3
Config.
Trap filter : specificies the traps allowed to be sent to the OSS :
x1 value for new alarm traps,
x3 value for Acknowledge State Changed traps,
x5 value for Cleared Alarm traps,
x6 value for Alarm List Rebuilt traps,
x7 value for Potential Faulty Alarm List traps.
SNMP V2 Config : gives the SNMP2c parameters (Community name) used by the XMC SNMP agent (if used),
SNMP V3 Config : describes the SNMP3 parameters used by the XMC SNMP agent (if used).
OSS config : this group gives the configuration of the OSS to receive traps from the XMC SNMP agent.
Additional OSS creation : Several OSS can be supported. To create an additional OSS, select the OSS
Config 1 node, right click, and choose Create in the popup menu. A new server instance is automatically
created with a new instance number.
OSS deletion : To delete an OSS previously created, select the OSS Config n node (n value greater than
1), right click, and choose Delete in the popup menu.
Filter name : filter to use by the XMC SNMP agent for trap sending to the OSS.
IP Address/Hostname : IP address or hostname of the OSS,
Remote port : port on the OSS used to receive traps from the XMC SNMP agent,
Trap community : Trap community to be used by the XMC SNMP agent to send traps to the OSS.
Filtering Config : allows to define filters to be used by the OSS configuration.

16
5 Exercises


34
5 Exercises
5.1 Exercises : Logs

1 6 35
Logs management :
Exercise 1 : From the Network Management interface
Select an NE,
Retrieve the Event level "Warning" for the last 10 days
Export the result (for the same period)
Exercise 2 : From the Welcome page
Select the XMC log files application
Identify and Display the content of the last used log file
Duration
20'
Exercise 3 : From an SSH session

Open an SSH session as axadmin
Identify and Display the content of the last used log file


5 Exercises
5.2 Exercises : Cleaning

1 6 36
Exercise 3 :
Login as root
Display the disk usage ( bdf)
Find the core files
Display the core files size and location
Ask the teacher before removing files
Exercise 4 :
Login as axadmin
Create an automatic Purge action for historical alarms
older then 30 days.
Check the crontab content
Duration
10'

Exemple of bdf command result (Unix) or df P (Linux):


16

for this module


37
16
End of Module
System Management


38
17
Section 1
Module 7
NE Creation


Blank Page
XMC System administration NE Creation
17

Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks

Objectives
17
To be able to create and/or remove a network element in
the topology, to use the filtering options, to manage the

NE access control.


Objectives [cont.]

17

Table of Contents
17
Page

1 The Network Management
1.1 The Network Management application
1.2 The topology management
1.3 Exemple of Network Management view
2 Creating/Removing an NE
2.1 Configuring the topology
2.2 Declaring an NE
2.3 Declaring an SDM NE
2.4 Modifying an NE declaration
2.5 Checking the NE accessibility
2.6 Removing an NE
2.7 Configuring XMC side parameters
3 Filtering the NE list
3.1 How to use Filtering
3.2 Exemple : Filtering only 'declared' NEs
4 Managing the NE access control
4.1 The access control principle
4.2 Recommended rules
4.3 Exemple of Domain display
4.4 Declaring a domain
4.5 Modifying domain(s)
5 Exercises
5.1 Exercises

7
8
9
11
12
13
14
16
20
22
23
24
27
28
29
30
31
32
33
34
35
36
37

17

This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

17


1.1 The Network Management application

178
Managing the Network consists in :
Topology management operations

Managing the network configuration : declaration of NEs.
Displaying the static attributes of a network element
Displaying the information of the managed network
Supervision management operations

Starting and stopping the supervision on declared NEs,
Displaying the supervision information for the supervised NEs,
Creating and using supervision filters.

These operations only apply to the nodes directly managed by the XMC.
Related documentation :
"A1300 XMC Network Management - Operator Guide"
3BL 65018 GABA PCZZA

1.2 The topology management

179
The Topology Management enables to manage a list of NEs

with a set of static attributes :
Actions : declare, modify, delete
NE related Informations :

name, type, release,

Internet Protocol (@IP) address,
port number for Simple Network Management Protocol (SNMP) NEs,
supervision start flag.
The XMC supervises Legacy and non-legacy network

elements.
Only Network Elements directly connected to the XMC

have to be declared.

These operations only apply to the nodes directly managed by the XMC.

1.2 The topology management [cont.]

1 7 10
The NEs topology is managed in the following modes :

Basic Network Element :
Entity which concerned one physical machine.

Network Elements part of the group are manually created and automatically
grouped per NE type : directly managed from the XMC
Exemple : DNS, iGGSN, NgHLR
Physical Grouping (Physical Compound NE) :
Grouping of Network Elements which are hierarchically linked together : a master

node/function managed one or several sub-groups of nodes.
Hierarchy is composed of a Master node instance and several sub-groups hosting
the NE (discovered/created) instances.
Exemple : OMC-CS, OMC-PS, LCP Mi-Agent for IMS
Virtual Grouping (Virtual Compound NE) :
Grouping of Network Elements which are not physically linked together : the
grouping is virtual, it helps the operator organizing its network topology.
Hierarchy is composed of 1 Group instance and several Sub-Groups instances
hosting the NE (created) instances.
Exemple : USDS, VITAL-Q, 7720 ABN

Exemple of Physical grouping :

Legacy core networks and associated NEs management are managed by the OMC-CS or the OMC-PS.
To
manage legacy NEs, you declare the OMC-CS and/or the OMC-PS as NEs to the XMC.
The
Supervision State of the legacy OMCs and associated NEs then becomes 'declared'.
The
Legacy NE names are displayed with the family container :

CS-NeName for CSCN NEs
PS-NeName for PSCN NEs

1.3 Exemple of Network Management view

1 7 11


17


12
2.1 Configuring the topology

1 7 13
Declaring a Network Element for supervision consists in :

Declaring the NE in the Network Management (topology),
Configuring parameters on NE side :

Setting the XMC name/address

Setting public keys authentication, if the node supports sftp
Configuring parameters on XMC side :

Setting the credentials for the sessions
Declaring the XMC as trap receiver
Starting the supervision

Notes related to the capacity control :

The number of NEs managed by the XMC is limited according to the server hardware and the following
policy:
WARNING: when the threshold is reached, the manual creation of the NEs is accepted and a warning is
displayed.
BLOCKING: when the threshold is reached, the manual creation of the NEs is rejected and an error
message is displayed.
The NEs counter is differently incremented depending on the manually NEs creation (weight of 1) and
automatically NEs creation (weight of 0,6). However, when NEs are automatically discovered through an
other manager, the NEs automatic creation is never rejected even if the blocking threshold is reached.

2.2 Declaring an NE
1 7 14

Open the "Network Management' window

From the menu bar, select Network Element Declare.
The "Declare a Network Element" window opens.
In the NE Type list box, select the type of NE to declare.

The window displays the fields for the selected type of NE.
Fields that are not applicable are grayed out.

Enter the appropriate parameters and click OK.

The message area, located at the bottom of the window, displays
information about the requested action (date, time and duration of the
action,action name, progress percentage and final status).
The NE displays in the tree view.
End.

DMSC Topology management :

A DMSC can be managed in two ways : the integrated view and the separate view.
Integrated view,
the DMSC is seen as a whole. To do that, you must declare, in [Network Management] , the DMSC
with the NE type Atrium DMSC .
Separate view,
the DMSC is declared in [Network Management] as a set of network elements : one WCS (NE type
5020 WCS) and its attached Media GateWay(s) (NE type 7540 WMG).
The WCS is managed in a standard way.

The management of the WMG has some specificities : the attachment WCS must be declared first,
To declare a WMG , the parameter WMG Node Number must be chosen identical to the WMG
Node number assigned to that WMG on the WEM.
DMSC supervision :
With the separate management, each NE forming the DMSC can be supervised independently with its own alarm
synthesis. The DMSC as a whole is not viewable.

The WCS is managed in a standard way. The management of the MGW has some specificities :
A MGW is automatically supervised once its attachment WCS is supervised, that is why the start/stop
supervision menus are not active for a MGW.
A MGW inherits directly its communication state and its supervision state from the communication
state/supervision state of its attachment WCS.

2.2 Declaring an NE [cont.]

1 7 15
Select the NE type

To Check the NE
accessibility
To Automatically
Start the NE
supervision
To define the
parameters to
communicate with
the NE
To Assign the NE in
another ACD

Priority : Attribute assigned to each NE for supervision filtering. Values :

Low, Medium (def), High
Port : used to send SNMP requests to the NE

Note: not applicable to: SGSN,OMC-CS, OMC-PS
Possible values :
161 (default value except for iGGSN MDSS type)
5161 (default value for iGGSN MDSS type)
1024 to 65535

2.3 Declaring an SDM NE

1 7 16
The Alcatel-Lucent 8650 Subscriber Data Management (SDM) R1 HLR

introduces a distributed multi-cluster architecture composed of
multiple individual NEs :

Front-End (FE) NEs

and Back-End (BE) NEs
which communicate through a WAN to perform the global HLR function.

The FEs, grouped in so-called FEGs (Front-End Group),

handle the HLR real time application part as well as the subscriber
provisioning application.
The BEs, grouped in so-called NRGs (Network Redundancy Group)

handle the Data Base application which stores the application data.


2.3 Declaring an SDM NE [cont.]

1 7 17
Declaration rules :
The SDM nodes must be attached to a 8650 SDM family.
Create the FEs and BEs SDM nodes

in any order.
In default FEG# and NRG# number (#1 for exemple),
using the correct information (from EML data).
Start the nodes supervision,

Execute a "Topology Learning" at 8650 SDM name level to update
the topology to its real NRG/FEG organisation.
The XMC
will compare the SDM hierarchy on the network with the one
manually defined on the XMC,
will then propose to update the XMC topology.
Accept, or not, the suggested modifications.

Exemple of Topology Learning result on NRG :


1 7 18
Select the type in :

8650 SDM FE /
8650 SDM BE /
8650 SDM compact

Keep the default

value : #1 (or real)


Possible values :
1024 to 65535


1 7 19
From FE Release : 8650 SDM R1.1 SU1
Select the Application in

the next window :
Configure from the window :



Possible values :
1024 to 65535

2.4 Modifying an NE declaration

1 7 20
The following table

summarizes the NE
parameters that can be
updated, depending on
the NE supervision state.
Most of the parameters

can only be modified in
the declared state (except
the ones on the table on the
right).


2.4 Modifying an NE declaration [cont.]

1 7 21


2.5 Checking the NE accessibility

1 7 22
When can I do it ?
During a declaring or modifying process for an NE
How to do ?
Check you have a valid IP address
Click Ping
End.
Results ?
The message area located at the bottom of the window displays
information about the requested action (date, time and duration of
the action, action name, progress percentage and final status).


2.6 Removing an NE
1 7 23


Select an NE in the tree view.
Stop the NE supervision (if not yet done)
In the menu bar, select Network Element - Remove.
Click Yes.

A confirmation dialog box displays.

The NE is removed from the tree view.
The message area located at the bottom of the window displays
information about the requested action (date, time and duration of the
action, action name, progress percentage and final status).
End.

The NE must be in the "Declared" state in order to remove it.

2.7 Configuring XMC side parameters

1 7 24
Configuration of Credentials, specific to each equipment

type
Modification authorized for axadmin only
Definition of login/password for the following accesses :

ftp/sftp
telnet/SSH
XMC Cli

See the "Network Management Operator Guide" Appendix B

for detailed configurations by NE type.

2.7 Configuring XMC side parameters [cont.]

1 7 25
From the Topology view :

Ne dependant :



2.7 Configuring XMC side parameters [cont.]

1 7 26
From the Platform Management view (to set default

values) :



17


27
3.1 How to use Filtering

1 7 28
Objectif :
To display a specific list (selected on criterias) of NEs in the view
How to filter ?
Using predefined filters
Creating a new filter

Priority selection in :
Any,
High
Medium
Low
Ne states selection in :
Any,
Supervised
Declared

3.2 Exemple : Filtering only 'declared' NEs

1 7 29

A filter may be in :
private access: visible and usable by the owner only (greyed for other users)
public access: visible and usable by all the users (a "*" is displayed before the filter name)

17


30
4.1 The access control principle

1 7 31
This optional features allows :

The "AllNEs" domain is automatically created to include all NEs

It cannot be removed nor modified
A "Domain profile" is automatically created as a consequence of the

domain creation
To group NEs in domain(s) according to criterias : type, location,

To give users access to selected domain(s)
It can be assigned to user(s)

Several domain profiles can be assigned to a user.
Only axadmin can declare, delete, modify and assign domains

Other users can only assign NE(s) to allowed domain(s).


4.2 Recommended rules

1 7 32
For RA/RNC management application

For Geographical redundancy application

Group all the Domain Name Systems(DNS) and all the SGSNs in the same
domain
Group both XMC in the same domain
For NE data backup application

Group in a multi-NE job only NEs belonging to the same domain

Only authorized NEs can be entered in the job
In multi-NEs jobs,

The job is displayed only if the user is authorized for at least one of the NEs
in the job
Actions on jobs are allowed if the user is authorised for all the NEs of the job


4.3 Exemple of Domain display

1 7 33


4.4 Declaring a domain

1 7 34
Domain
name
Assign / Deassign NEs

to the domain


4.5 Modifying domain(s)

1 7 35
Right Click
Assign NE to domain(s)
or
Deassign from domain


17
5 Exercises


36
5 Exercises
5.1 Exercises
1 7 37
Following the trainer instructions :

Select a node
Display and remember its configuration
Remove the node
Recreate the node
Create a new domain (ACD-Grx)

Assign the node to the new domain
Print the network topology list
Duration
10'
Remove the domain ACD-Grx
ACD-Grx : where x is the group number



17

for this module


38
17
End of Module
NE Creation


39
18
Section 1
Module 8


Blank Page
XMC System administration Geographical redundancy

18
Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks

Objectives
To be able to manage the geographical redundancy.


18
Objectives [cont.]


18
Table of Contents
Page

1 Overview of the application
1.1 Geored principles
1.2 XMC End-users
1.3 Geographical Redundancy configuration
2 Replication and Switchover
2.1 Replication and Switch-over
2.2 The Replication process
2.3 Performing the switch-over
2.4 Geographical Redundancy GUI

18

7
8
9
10
11
12
13
14
15
17


This
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally

18
1 Overview of the application


18
1 Overview
1.1 Geored principles

The geographical redundancy is used to

Secure the network supervision,
Reduce the service interruption (system upgrade or system problem).
Configuration principle :
A fully duplicated XMC ("active" and "ready" servers) :

Identical functions level (software)

Identical network supervision
A redundant LAN between both XMCs
The active OMC is used by all users for the network management
operations.
The ready OMC is a replicata of the active one, but no operator will
have access to it for the day to day network management operations.
Each NE is configured to send
their trap/alarm to both servers (active+ready)
their performance data to the active OMC.

Related Documentation :
A1300 XMC Platform Administration Guide Operator Guide

Chapter 10 : Geographical redundancy

188
1 Overview
1.2 XMC End-users

189
The Administrator :
Can access to the active or the ready XMC for redundancy management
operations,
Other Users :
Can only access to the active XMC for daily network management operations


1 Overview
1.3 Geographical Redundancy configuration

1 8 10
Active OMC
IP@1 : primary IP@ used by the NE
IP@2 : secondary IP@ for redundancy LAN purpose
(IP@3 : IP@ used to the upper OS )
Ready OMC
IP@4 : primary IP@ used by the NE
IP@5 : secondary IP@ for redundancy LAN purpose
(IP@6 : IP@ used to the upper OS )

On both OMC, 2 NEs will be created :

one with the IP1@/IP2@ for the active OMC,
one with the IP4@/IP5@ for the standby OMC.
On both OMC the ior file used for the upper OS will be generated with the IP3@/IP6@.
The switch-over is done manually by the operator.
Mutual supervision :
Two NEs (active/ready OMC) will be automatically created by TOPO and supervised by SUP in order to be
able to consult their alarms.

The communication between the 2 OMCs will be periodically checked by SNMP CM. In case of timeout the
SNMP CM will issue an Alarm (NE unreachable) and a notification. The redundancy IM will subscribe to this
notification in order to update the link status (reachable/unreachable) information.

2 Replication and Switchover


18
11
2 Replication and switch-over
2.1 Replication and Switch-over

The
Geographical Redundancy management consists in
A replication operation :
Updating
the ready XMC with data from the active XMC.
And
A switch-over operation :
switching

the supervision from the active server to the ready one,
Switching the active server to ready/standby

Switching the ready server to active.


1 8 12
2.2 The Replication process

1 8 13
On the active OMC, the replication process is in charge of

freezing the processes,

preparing the data to be transferred (tar file),
transferring the file to the ready machine,
notifying the ready machine,
unfreezing the processes.
On the ready machine the replication process (restore) is in charge of

stopping the processes,
restoring the data file,
restarting the processes.
In case of unsuccessful replication an alarm will be issued on the local
OMC, in any case the replication progress will be logged.
The performance data are collected/translated on the active OMC.

Each time a file is ready a notification is send by the CMs and received by
RedundancyIM, this process will be in charge of transferring the file to the

ready server.


2.3 Performing the switch-over

1 8 14
The switch over is to be performed

First on the active OMC,
Then on the ready OMC.
On the active OMC,

if the last replication is not successful the end-user is warned.
Then, all the operators will be locked (except the specific operator),
the status of the OMC will be switched to ready,
the crontab entry concerning the automatic replication will be disabled,
the ftp account will be locked.
On the ready OMC,

if distant OMC is reachable and still in active mode, the switchover is refused,
if distant OMC is not reachable, a warning message is displayed to the operator.
If the last replication is not successful the end-user should be warned.
Then, all the operators will be unlocked,
the status of the OMC will be switched to active,
the crontab entry concerning the automatic replication will be enabled,
the ftp account will be unlocked.
In case of unsuccessful switchover

an alarm will be issued on the local OMC, in any case the switchover progress will be logged.

2.4 Geographical Redundancy GUI


Once the switchover is done on both XMCs, the user have

To open new operator sessions on the new active XMC (previous sessions are closed).
To do a locking redundancy operation, which consists in disabling the redundancy process,
To do an unlocking redundancy operation, which consists in allowing replication and switchover processes.

1 8 15


for this module


18
16


18
17
18
End of Module


18
XMC System administration Glossary
19
Abbreviations and Glossary


Abbreviations and Acronyms

19


Abbreviations and Acronyms [cont.]

19


Glossary
#
3PP
19

Three Third Parties
A
ACI
AGW
ALMAP
API
AS
Access Control Information

Access GateWay
ALcatel Management Platform
Application Program Interface
Alarm Supervision
B
BB
BroadBand
C
CA
CAL
CM
CORBA
CPU
CSCN
Certificate Authority
Current Alarms List
Communication Manager
Common Object Request Broker Architecture
Central Processing Unit
Circuit-Switched Core Network
D
DCN
DNS
DPC
Data Communication Network

Domain Name System
Data Processing Centre

E
EML
ETSI
Equipment Management Layer

European telecomunications Standards Institute
F
FAD
FM
FTP
Functional Access Domain

Fault Management
File Transfert Protocol
G
GGSN
GPRS
GSM
GUI
GW
Gateway GPRS Support Node

General Packet Radio Service
Global System for Mobile communications
Graphical User Interface
GateWay
H
HA
HAL
High Availability
Historical Alarm List
I
IM
IMS
IP
IPL
Information Manager
IP Multimedia Subsystem
Internet Protocol
Initial Program Loader
J
JNLP
JRE
JTA
Java Network Launching Protocol

Java Runtime Environment
Java Telnet Application
K
Glossary [cont.]
L
LSM
LAN
19
Local Session Manager

Local Area Network
M
MIB
Management Information Base
N
NE
NGN
NML
NMS
NTP
Network Element
Next Generation Network
Network Management Layer
Network Management Server
Network Time Protocol
O
OAD
OMC
OMC-CMC
OMC-CN
OMC-CS
OS
OSF
OSP
OWP
Object Access Domain

Operation and Maintenance Center
Operation and Maintenance Center Convergence Management Center
Operation and Maintenance Center Core Network
Operation and Maintenance Center Circuit Side
Operation system
Operation System Functions
Open System Platform
Operator WorkPlace
P
PSCN
Q
QoSAC
Packet-Switched Core Network

Quality of Service Analysis Center
R
S
SDH
SEC
SFTP
SGSN
SNMP
SSH
SSL
Synchronous Digital Hierarchy

SECurity
Secured File Transfert Protocol
Serving GPRS Support Node
Simple Network Management Protocol
Secure Shell
Secured Sockets Layer
T
TMN
Telecommunication Management Network
U
UMA
UMTS
USM
UTRAN
Unlicensed Access Mobile

Universal Mobile Telecommunication System
User Service Manager
UMTS Terrestrial Radio Access Network
V
W
WS
Work Station

References
19
3BL65020GCBAPCZZA 1300 XMC Platform Administration Guide

3BL65018GCBAPCZZA 1300 XMC Network Management
3BL96354GCCAPCZZA 1300 XMC Platform Management
3BL96355GCCAPCZZA Access Control Management
3BL59923GCCADTZZA XMC Security Statement of Compliance
3BL59911GCAAREZZA XMC R6.2 Troubleshooting Guide


19
End of Module
Glossary


Last But One Page

1
@@PRODUCT
@@COURSENAME
All Rights Reserved Alcatel-Lucent @@YEAR

@@COURSENAME - Page 1
All rights reserved Alcatel-Lucent @@YEAR

Passing on and copying of this document, use and communication of its
contents not permitted without written authorization from Alcatel-Lucent
@@COURSENAME - Page 2

TOS18011D0SGDENI10

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

TOS18011D0SGDENI10

Загружено:

Авторское право:

Доступные форматы

1300 XMC (Cross-Domain

All Rights Reserved Alcatel-Lucent 2009

All rights reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

1300 XMC (Cross-Domain Management Center)

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2009

Terms of Use and Legal Notices

All rights reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

All Rights Reserved Alcatel-Lucent 2009

1300 XMC (Cross-Domain Management Center)

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2009

4. Topic/Section is Positioned Here

5. Topic/Section is Positioned Here

3. XMC Processes Management

6. Topic/Section is Positioned Here

7. Topic/Section is Positioned Here

2. Topic/Section is Positioned Here

3. Topic/Section is Positioned Here

All Rights Reserved Alcatel-Lucent 2009

1300 XMC (Cross-Domain Management Center)

All Rights Reserved Alcatel-Lucent 2009

Course Outline [cont.]

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2009

Welcome to 7.0 System administration

Upon completion of this course, you should be able to:

By the end of the course, the participant will be able to:

7.0 System administration

All Rights Reserved Alcatel-Lucent 2009

Course Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2009

About this Student Guide

All Rights Reserved Alcatel-Lucent 2009

Where you can get further information

1300 XMC (Cross-Domain Management Center)

If you want further information you can refer to the following:

All Rights Reserved Alcatel-Lucent 2009

About this Student Guide [cont.]

Switch to notes view!

All Rights Reserved Alcatel-Lucent 2009

This page is left blank intentionally

All Rights Reserved Alcatel-Lucent 2009

At the end of each

section you will be asked to fill this questionnaire

Surname, First name :

All Rights Reserved Alcatel-Lucent 2009

1300 XMC (Cross-Domain Management Center)

All Rights Reserved Alcatel-Lucent 2009

Self-assessment of Objectives [cont.]

All Rights Reserved Alcatel-Lucent 2009

1300 XMC (Cross-Domain Management Center)

Thank you for your answers to this questionnaire

All Rights Reserved Alcatel-Lucent 2009

Do not delete this graphic elements in here:

1300 XMC (Cross-Domain Management Center) 7.0 System administration

All Rights Reserved 2007, Alcatel-Lucent

1300 XMC (Cross-Domain Management Center)