Professional Documents
Culture Documents
Management Center)
7.0 System administration
TOS18011 D0 SG DEN I1.0 Issue 1
STUDENT GUIDE
Empty page
Switch to notes view!
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
All Rights Reserved Alcatel-Lucent 2009
3written consent of Alcatel-Lucent.
1300 XMC (Cross-Domain Management Center)
7.0 System administration
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
Switch to notes view!
Course Outline
1. XMC
administration
About
ThisSystem
Course
Course outline
1. Introduction
Technical
2.support
Operators Management
Course objectives
4. Backup
and RestoreHere
1. Topic/Section
is Positioned
Xxx
Xxx
Xxx
5. AS Administration
6. System Management
7. NE Creation
8. Geographical redundancy
6
1300 XMC (Cross-Domain Management Center)
7.0 System administration
Course Objectives
Switch to notes view!
- 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
All Rights Reserved Alcatel-Lucent 2009
7
- Management
perform
OMC systems switch-over (redundant configuration).
1300 XMC (Cross-Domain
Center)
8
1300 XMC (Cross-Domain Management Center)
7.0 System administration
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.
10
1300 XMC (Cross-Domain Management Center)
7.0 System administration
Self-assessment of Objectives
Contract number :
to notes view!
Number of trainees :
to :
Location :
Instructional objectives
11
Yes (or
globally
yes)
No (or
globally
no)
Comments
12
Yes (or
Globally
yes)
No (or
globally
no)
Comments
Other comments
11
Section 1
XMC System administration
Module 1
Introduction
3JK11458AAAAWBZZA Edition 3
Blank Page
XMC System administration Introduction
11
Document History
Edition
Date
Author
03
2009-09-24
RANNOU, Raymond
Remarks
Objectives
XMC System administration Introduction
11
Objectives [cont.]
XMC System administration Introduction
11
Table of Contents
XMC System administration Introduction
11
Page
7
8
11
12
13
14
15
16
17
18
20
21
22
26
11
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
11
1 TMN Architecture
1 TMN Architecture
1 Introduction
External OSSs
NBI
Integrated XMC
SBI
IP Backbone
Legacy
OMCs
X25/IP
IP
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)
IMS domain Core nodes for both Fixed and Mobile Networks
UMA network
1 Introduction
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
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 .
11
11
3 XMC Software
The
Webstart
cache
Web
Start
E
C
OWP
Only accessible
for verified
applications
WEB Server
Jar files
JNLP pages
External resources
XMC Server
1300 XMC (Cross-Domain Management Center)
7.0 System administration
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.
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
2U
DL380 G5 1 or 2
QuadCores
Managed domains
NE, ...
OWPs
System console
IP
2 * routers
Cisco 2621
Printer
NTP server
(if any)
( optional )
External storage
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.
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.
Other configurations :
Servers configurations :
Field trial or for very small network (no possible evolution)
HP
ML350
2
to 8 CPUs,
from
6 to 18 GB memory,
from
DAT
Core package
One
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
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.
XMC
Maintenance
Administration
Troubleshooting
Users management
System Cleaning up
Etc.
Etc.
least weekly
Introduction
What is an ENMS ?
OS
OS
yes
no
11
25
11
26
1 Introduction
What is an ENMS ?
An Equipment and Network Management Server
OS HP-UX 11i
OS HP-Linux RedHat 5
yes
no
11
End of Module
Introduction
28
12
Section 1
XMC System administration
Module 2
Operators Management
3JK11460AAAAWBZZA Edition 3
Blank Page
XMC System administration Operators Management
12
Document History
Edition
Date
Author
03
2009-09-24
RANNOU, Raymond
Remarks
Objectives
XMC System administration Operators Management
12
Objectives [cont.]
XMC System administration Operators Management
12
Table of Contents
XMC System administration Operators Management
12
Page
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
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
12
1 Session Management
12
1 Session Management
12
Closed sessions
Forced to close sessions
1 Session Management
12
1 Session Management
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 Session Management
12
1
Click Actions
Force logout
Press Confirm
The selected session is closed
2
3
1300 XMC (Cross-Domain Management Center)
7.0 System administration
11
1 Session Management
Purpose :
When sessions have been closed, they are displayed in the sessions list.
This option allows to clear all closed sessions.
12
12
1 Session Management
Purpose :
Unselect all selected items in tables.
12
13
1 Session Management
Purpose :
Immediate refresh of the session table to display the current state of the
sessions.
From a Sessions Administration GUI,
Select : Actions > Refresh table
12
14
12
15
Common characteristics :
Common weekly schedule (*)
Public holidays (*)
1 2 16
1 2 17
Viewer
Operator
Admin
SECAdmin
AWPSecAdmin
allows access rights to Security Management directly from the Web portal
NeacdAdmin
admin+SECAdmin+GeoredAdmin+AWPSecAdmin+NeacdAdmin
operator
operator
viewer
viewer
Other tasks, like assigning a profile, are done using the "Operator
12
18
12
19
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
1300 XMC (Cross-Domain Management Center)
7.0 System administration
1 2 20
1 2 21
Login as axadmin
Open the "Operator Management" session
1 2 22
or
Select :
User Management
Create User
2
1- Enter the "User login"
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
- ResetPassword :
TRUE
FALSE
Login as axadmin
1 2 24
"Access_to_"
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
To lock or unlock an
operator access :
Locked operator
Unlocked operator
1300 XMC (Cross-Domain Management Center)
7.0 System administration
1 2 26
1 2 27
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
-
Click Change
Or press
1 2 28
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
This command can be used to unlock the web account for axadmin.
1 2 30
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 :
/usr/lbin/modprpw -l v <user_account>
If the locked account is root, execute the following command as axadmin
12
31
1 2 32
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:
1 2 34
1
2
Operators management
1 2 36
Operators management
Exercise 1
XMC System administration Operators Management
1 2 37
As axadmin,
Assign the "Admin" profile
Duration
15'
operator.
Remove the created operators
Operators management
Exercise 2
XMC System administration Operators Management
1 2 38
Duration
10'
Operators management
Evaluation
1 2 39
12
40
Operators management
yes
two
more
12
End of Module
Operators Management
42
13
Section 1
XMC System administration
Module 3
XMC Processes Management
3JK11459AAAAWBZZA Edition 2
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
XMC System administration XMC Processes Management
13
Objectives [cont.]
XMC System administration XMC Processes Management
13
Table of Contents
XMC System administration XMC Processes Management
13
Page
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
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
13
13
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
139
Optional Packages :
3GPP northbound CORBA Interface provides 3GPP Open interfaces ,
allows the operator to handle centralized command and control for NEs backuprestore.
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
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
RA Management
Offers added-on value features compared to RA/RNC management provided by SGSN EML GUI
Offers a various platform services such as : process monitoring, trace management, database management,
purge management, OMC backup/restore
Third parties
packages :
Mandatory package for
1 3 11
RA management NetraIM
3GPP management 3gppIM
Alarm management :
ascurIM, ashistIM, FMCUR server, FMHIST server, NSP
1 3 12
1.
2.
3.
Related documentation :
A1300 XMC Platform Administration Administration Guide
Chapter 6 : Processes and resources monitoring procedures
1 3 13
1 3 14
Open an SSH
session as
axadmin
Execute the
command :
CheckXMC
1 3 15
1 3 16
> Server
> Group of processes
> Processes
> Logical volumes groups
Green : no alarm
Yellow : alarm level 1
Orange : alarm level 2
Red : alarm level 3
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
running
Blue :
stopped
init or stopping
Some processes of the group were asked to freeze but are not frozen yet. The others are
either frozen, stopped or running
Frozen
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
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
Freezing
Frozen
Init
Unfreezing
Unknown
Initial status of a process: the process monitoring is waiting for the process status
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
All Rights Reserved 2007, Alcatel-Lucent
3JK11459AAAAWBZZA Edition 2
Section 1 Module 3 Page 18
1 3 18
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
13
20
1.
From the A1300 XMC home page, click "Launch WEB portal".
The [ALMAP WEB Portal] window displays.
2.
3.
4.
End.
1 3 21
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"
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.
Displaying Process
group status
Displaying
Selected Process
details
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 :
Detailed explanations in chapter 6.5 of the "A1300 XMC Platform Administration Guide"
Displaying Logical
Volume group
status
Displaying Logical
Volume status
Resources details :
Note
Red = current relative memory size of the disk volume actually used
Detailed explanation in chapter 4.9 of the "A1300 XMC Platform Administration Guide"
Filesystem
Usage
Purge Action
/alcatel
NO
/nedata/perfs
NO
/nedata/alarms
/nedata/log
Manual on alarm
/nedata/scripts
Manual on alarm
/nedata/backup
NE backup directory
Manual on alarm
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
ServiceXMC
1 3 28
Right click
1 3 29
1 3 30
Right click
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.
13
31
XMC Application
domain
Check the connected users and warn them about the operation.
1 3 33
Check the connected users and warn them about the operation.
CheckXMC
1 3 34
1 3 35
Open a UNIX session to the XMC server and type the following command
to verify if XMC is stopped :
CheckXMC
1 3 36
shutdown -h now
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,
CPU
2.
1 3 37
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
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.
2.
CPU
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.
Exercise
XMC System administration XMC Processes Management
1 3 40
(15 min)
One group is asked to Proceed to a server reboot (15
min)
20'
13
41
13
42
1 3 43
End of Module
XMC Processes Management
13
44
14
Section 1
XMC System administration
Module 4
Backup and Restore
3JK11461AAAAWBZZA Edition 2
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
XMC System administration Backup and Restore
14
Objectives [cont.]
XMC System administration Backup and Restore
14
Table of Contents
XMC System administration Backup and Restore
14
Page
7
8
9
10
11
12
14
15
16
17
18
20
21
22
23
24
25
27
28
29
31
33
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
14
14
1 Functions presentation
1 Functions presentation
can be used :
All
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 Functions presentation
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
10
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
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.
Backup to TAPE
Before execution:
Check if the drive unit is connected and in service with a valid tape.
# /alcatel/omc1/OMC_OSM/backup_scripts/data-backup.pl
/alcatel/omc1/data/traces/data-backup.traces
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
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]
/alcatel/omc1/data/traces/data-backup.traces
-t (tape-device)
-f (file-dest)
-k <n>
# crontab l axadmin
# crontab -l u axadmin
(for HP-UX)
(for Linux)
# crontab /tmp/mycrontab
Check the changes using :
# crontab l
1300 XMC (Cross-Domain Management Center)
7.0 System administration
When ?
After a backup to check the tape or file archive
(for HP-UX)
(for Linux)
or
# mt /dev/rmt/0m rew
(for HP-UX)
# mt /dev/nst0 rew
(for Linux)
or
The third command will list all the files in the .tgz archive.
14
16
Cautions :
To be performed with the exact same A1300 XMC software version as
the last backup.
Warn users about the service interruption.
6.
7.
End.
6.
7.
End.
-t (tape-device)
-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
14
20
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.
Steps :
1. Open an SSH session, and login as user root
2. Go to the backup_scripts directory :
# cd /alcatel/omc1/OMC_OSM/backup_scripts
3.
4.
5.
Bye.
6.
After the full backup is finished, you can consult the log file "/alcatel/omc1/data/traces/fullbackup.trace".
4.
The duration of the pax command will depend on size of the data stored
during the full backuo (about 1 hour).
Steps :
1. Open an SSH session, and login as user root
2. Go to the backup_scripts directory :
# cd /alcatel/omc1/OMC_OSM/backup_scripts
>
>
5.
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
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 /alcatel/omc1/data/traces/fullbackup.trace
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.
After the full backup is finished, you can display the log files using :
# more /alcatel/omc1/data/traces/fullbackup.trace
14
27
This operation will restore the content of a previous full backup tape(s).
To be done :
Preliminary actions :
Steps :
1. Insert the (first) tape to restore
2. Open an SSH session, and login as user root
3. Perform an immediate reboot :
# cd /
# shutdown r y now
4.
5.
Search
The device numbers (Path #) are displayed
6.
Boot Pi
Device Path
(dec)
Device Path
(mnem)
Device Type)
IODC rev
P0
0/1/1/0.1
Intscsia.1
P1
0/1/1/1.0
Intscsib.0
P2
0/2/1/0.1
P3
0/2/1/0.3
In this example, the path number is P3 for the tape device (Sequential access media).
# tail f /install/install.log
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.
6.
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).
7.
8.
cd /etc/recovery
./start-restore.sh
# busybox reboot
12. Start the XMC.
# tail f /install/install.log
Backup - Restore
6
Exercises
1 4 33
Exercise 1 :
1.
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.
2.
Full Backup :
Proceed to the full backup
Check the backup traces
3.
15' + 45'
14
35
14
End of Module
Backup and Restore
36
15
Section 1
XMC System administration
Module 5
AS Administration
3JK11462AAAAWBZZA Edition 3
Blank Page
XMC System administration AS Administration
15
Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks
Objectives
XMC System administration AS Administration
15
Objectives [cont.]
XMC System administration AS Administration
15
Table of Contents
XMC System administration AS Administration
15
Page
7
8
9
10
11
12
13
14
16
17
18
19
20
21
22
23
24
25
26
27
15
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
15
15
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
AS operator
Static analysis
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
Automatic filters
User-defined filters
Filter(s) description
and selection
5
2
3
6
Select New
2.
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.
6.
alarms
will not appear in the Current Alarm List
and will not require operator action.
15
19
2
1
5
4
1300 XMC (Cross-Domain Management Center)
7.0 System administration
15
22
2
1
3
5
4
1300 XMC (Cross-Domain Management Center)
7.0 System administration
15
25
alarms Severity.
This change
It is not recommended to modify the default sublists configuration (to retrieve the Original
Perceived Severity and filters) :
Critical
Major
Minor
Warning
Clear
Indetermined
tab.
Press New to create the new
condition to apply.
In Definition tab, enter
In Filter tab
Press Apply
Check the Activation State
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
30
15
End of Module
AS Administration
31
16
Section 1
XMC System administration
Module 6
System Management
3JK11463AAAAWBZZA Edition 3
Blank Page
XMC System administration System Management
16
Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks
Objectives
XMC System administration System Management
16
To be able
to display the XMC logs and system trace files
to clean files
To customize the common system parameters.
Objectives [cont.]
XMC System administration System Management
16
Table of Contents
XMC System administration System Management
16
Page
7
8
10
11
12
13
15
16
19
20
23
24
25
26
29
30
31
32
33
34
35
36
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
16
16
XMC.
Collection periodicity
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 :
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.
Types of logs :
log_file_<n>
sas_log
secserver<n>_log
operators actions
sessions authentications
security server modifications
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
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
(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"
# 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.
Management view :
Exported logs are saved in the default directory on the XMC server :
16
20
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/
XMC.
16
3 Cleaning files
23
3 Cleaning Files
3 Cleaning Files
When
To
HP-UX: # bdf
on LINUX: # df -k
on
3 Cleaning Files
# cd /alcatel/omc1/OMC_FMCF/scripts/
# ./purge_histo_alarms.pl [ -r<retention_duration>] [ init | exec | stop ]
Exemple :
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 Cleaning Files
# cd /nedata/alarms/histDB/<year>[/<month>[/<day>]]
# rm <file_to_delete>
Year 2008
Months : 1:January /
2:February / 3:March
Archived days for
February
3 Cleaning Files
How to proceed ?
File Size(bytes)
-exec \+
Files location
16
30
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 :
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.
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.
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
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'
5 Exercises
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'
16
37
16
End of Module
System Management
38
17
Section 1
XMC System administration
Module 7
NE Creation
3JK11464AAAAWBZZA Edition 3
Blank Page
XMC System administration NE Creation
17
Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks
Objectives
XMC System administration NE Creation
17
Objectives [cont.]
XMC System administration NE Creation
17
Table of Contents
XMC System administration NE Creation
17
Page
7
8
9
11
12
13
14
16
20
22
23
24
27
28
29
30
31
32
33
34
35
36
37
17
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
17
These operations only apply to the nodes directly managed by the XMC.
Related documentation :
"A1300 XMC Network Management - Operator Guide"
These operations only apply to the nodes directly managed by the XMC.
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
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
17
2 Creating/Removing an NE
12
2 Creating/Removing an NE
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 Creating/Removing an NE
2.2 Declaring an NE
1 7 14
End.
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 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
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 Creating/Removing an NE
To Automatically
Start the NE
supervision
To define the
parameters to
communicate with
the NE
To Assign the NE in
another ACD
Possible values :
1024 to 65535
2 Creating/Removing an NE
handle the HLR real time application part as well as the subscriber
provisioning application.
handle the Data Base application which stores the application data.
2 Creating/Removing an NE
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).
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.
2 Creating/Removing an NE
Possible values :
1024 to 65535
2 Creating/Removing an NE
Possible values :
1024 to 65535
2 Creating/Removing an NE
2 Creating/Removing an NE
2 Creating/Removing an NE
When can I do it ?
During a declaring or modifying process for an NE
How to do ?
Open the "Network Management' window
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 Creating/Removing an NE
2.6 Removing an NE
1 7 23
Click Yes.
End.
2 Creating/Removing an NE
2 Creating/Removing an NE
2 Creating/Removing an NE
17
27
Objectif :
How to filter ?
Priority selection in :
Any,
High
Medium
Low
Ne states selection in :
Any,
Supervised
Declared
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
Group all the Domain Name Systems(DNS) and all the SGSNs in the same
domain
Group both XMC in the same domain
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
Domain
name
Right Click
Assign NE to domain(s)
or
Deassign from domain
17
5 Exercises
36
5 Exercises
5.1 Exercises
1 7 37
Duration
10'
17
38
17
End of Module
NE Creation
39
18
Section 1
XMC System administration
Module 8
Geographical redundancy
3JK11465AAAAWBZZA Edition 3
Blank Page
XMC System administration Geographical redundancy
18
Document History
Edition
Date
Author
03
2009-09-25
RANNOU, Raymond
Remarks
Objectives
XMC System administration Geographical redundancy
18
Objectives [cont.]
XMC System administration Geographical redundancy
18
Table of Contents
XMC System administration Geographical redundancy
Page
18
7
8
9
10
11
12
13
14
15
17
All Rights
Reserved
Alcatel-Lucent
2007
page
is left
blank
intentionally
18
18
1 Overview
Configuration principle :
A fully duplicated XMC ("active" and "ready" servers) :
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 :
188
1 Overview
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 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 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
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.
18
11
The
A replication operation :
Updating
And
A switch-over operation :
switching
1 8 12
1 8 13
1 8 14
To open new operator sessions on the new active XMC (previous sessions are closed).
To do an unlocking redundancy operation, which consists in allowing replication and switchover processes.
1 8 15
18
16
18
17
18
End of Module
Geographical redundancy
18
19
19
19
Glossary
XMC System administration Glossary
#
3PP
19
A
ACI
AGW
ALMAP
API
AS
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
E
EML
ETSI
F
FAD
FM
FTP
G
GGSN
GPRS
GSM
GUI
GW
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
K
All Rights Reserved 2007, Alcatel-Lucent
3JK11466AAAAWBZZA Edition 1
Section 1 Module 9 Page 4
Glossary [cont.]
L
LSM
LAN
19
M
MIB
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
P
PSCN
Q
QoSAC
R
S
SDH
SEC
SFTP
SGSN
SNMP
SSH
SSL
T
TMN
U
UMA
UMTS
USM
UTRAN
V
W
WS
Work Station
References
XMC System administration Glossary
19
19
End of Module
Glossary
1
@@PRODUCT
@@COURSENAME