1300 CDC PD tcm228-1474891635

PRODUCT DESCRIPTION
CROSS-DOMAIN MANAGEMENT CENTER ALCATEL-LUCENT 1300 XMC PRODUCT RELEASE R6.X

Edition 1.8
#3DR20003QMWWPTAHF02
1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

Alcatel-Lucent
3DN 00801 AAAA DEZZA

Date: Feb 2008
1/45
All rights reserved. Passing on and copying of this document, use and communication of its contents, not permitted without written authorization
SUMMARY
1 INTRODUCTION ....................................................................................................6 1.1 2 2.1 2.2 3 3.1 3.2 3.3 3.4 KEY FEATURES ..................................................................................................... 6 FEATURE LIST ....................................................................................................... 8 MANAGED NETWORKS ....................................................................................... 9
A1300 XMC FUNCTIONAL DESCRIPTION..............................................................8
A1300 XMC FEATURE DESCRIPTION .................................................................. 11 ALARM HANDLING ............................................................................................ 11 3.1.1 CURRENT ALARM MANAGEMENT ............................................................ 12 3.1.2 ALARM REPORTING AND LOGGING........................................................ 13 TOPOLOGY MANAGEMENT .............................................................................. 14 NETWORK SUPERVISION ................................................................................... 16
3.5 3.6 3.7 3.8 3.9
ACCESS MANAGEMENT .................................................................................... 18 3.4.1 Main functionalitIES .................................................................................. 18 3.4.2 ACCESS CONTROL.................................................................................. 18 3.4.3 Navigation ............................................................................................... 19
EVENT AND LOG MANAGEMENT ...................................................................... 19 3.5.1 NE Logs ................................................................................................... 19 3.5.2 XMC Logs................................................................................................. 19 MULTI NE SCRIPTING......................................................................................... 21
JOB MANAGEMENT........................................................................................... 20
NE SOFTWARE MANAGEMENT .......................................................................... 21 3.8.1 NE Software downloading: ....................................................................... 22 3.8.2 NE backup/restore: .................................................................................. 22 ON LINE DOCUMENTATION............................................................................. 22
3.10 CONFIGURATION MANAGEMENT .................................................................... 23 3.11 EQUIPMENT MANAGEMENT.............................................................................. 23 3.12 OBSERVATION MANAGEMENT .......................................................................... 24
3.13 EXTERNAL INTERFACES ...................................................................................... 24 3.13.1 3GPP ....................................................................................................... 24 3.13.2 SNMP....................................................................................................... 25 3.13.3 XML/SOAP ............................................................................................... 25 3.14 XMC PLATFORM FUNCTIONS ............................................................................ 25 3.14.1 XMC platform backup/restore................................................................... 25 3.14.2 XMC PLATFORM MONitoring ................................................................... 25 3.14.3 Geographical REDUNDANCY CONCEPT.................................................. 26 3.14.4 TIME MANAGEMENT................................................................................ 26 3.15 NETWORK MANAGEMENT................................................................................. 26 3.15.1 Latency Report Management and Tracing ................................................. 26
Alcatel-Lucent

Date: Feb 2008
2/45
3.15.2 RA/RNC management .............................................................................. 26 4 XMC OVERALL ARCHITECTURE ........................................................................... 28 4.1 4.2 HARDWARE ARCHITECTURE............................................................................... 29 4.1.1 XMC server............................................................................................... 30 SOFTWARE ARCHITECTURE ............................................................................... 31 4.2.1 General concept....................................................................................... 31 4.2.2 detailed software architecture ................................................................... 32
TECHNICAL DESCRIPTION .................................................................................. 34 5.1 PROTOCOLS AND INTERFACES ......................................................................... 34 5.1.1 interface between XMC and network element ............................................ 34 5.1.2 interface between Xmc and OTHER OMCs ................................................ 35 5.1.3 Interfaces between Xmc and oss (OPtional features) .................................. 35
5.2 5.3 5.4 5.5
XMC RESILIENCE................................................................................................ 35 5.2.1 Platform Resilience.................................................................................... 35 5.2.2 MTBF System Availability........................................................................... 36
DISASTER RECOVERY ......................................................................................... 36 Different scenarios.................................................................................... 36 Data integrity............................................................................................ 36 CAPACITY .......................................................................................................... 36
5.6 5.7 5.8
TECHNICAL DATA.............................................................................................. 37 5.5.1 Physical dimensions of each element......................................................... 38 5.5.2 Heat dissipation........................................................................................ 38 5.5.3 POWER CONSUMPTION.......................................................................... 38 SERVICE RESTORATION TIMES ........................................................................... 40 5.7.1 XMC upgrades ......................................................................................... 40 5.7.2 Integration with Network Management System .......................................... 41 INSTALLATION & COMMISSIONING REQUIREMENTS........................................ 41 5.8.1 XMC installation ....................................................................................... 41 5.8.2 Network management commissioning ...................................................... 41 XMC DOCUMENTATION ................................................................................... 42
DIAL-IN CAPABILITIES ........................................................................................ 39
DOCUMENTATION ............................................................................................. 42 6.1 6.2 OTHER RELATED DOCUMENTATION: ................................................................ 43
GLOSSARY........................................................................................................... 44

Alcatel-Lucent

Date: Feb 2008
3/45
LIST OF FIGURES
Figure 1: XMC key features ............................................................................................................7
Figure 2: Example of IMS management with XMC with portal on OMC-P.......................................10 Figure 3: XMC Alarm supervision panel ........................................................................................11 Figure 4: Alarm Management........................................................................................................12 Figure 6: Map view ......................................................................................................................15 Figure 5: Topology management..................................................................................................14 Figure 7: Supervision management...............................................................................................16 Figure 8: Job management ..........................................................................................................21 Figure 9: XMC Overall Architecture...............................................................................................28 Figure 11: XMC General concept...................................................................................................32
Figure 10: XMC Network Architecture ............................................................................................29 Figure 12: XMC Software Architecture ............................................................................................33
Figure 13: Interface between XMC and NEs ...................................................................................34

Alcatel-Lucent

Date: Feb 2008
4/45
LIST OF TABLES
Table 1: XMC ENMS server configuration.......................................................................................31 Table 2: ENMS versus XMC Capacity .............................................................................................37 Table 3: Service Restoration Times .................................................................................................40 Table 4: XMC Documentation........................................................................................................42

Alcatel-Lucent

Date: Feb 2008
5/45
1 INTRODUCTION
In co-ordination with the renovation of the next generation of networks, and taking advantage of a new distributed management architecture, the Alcatel-Lucent-Lucent 1300 XMC Cross-Domain Management Center provides the combination of field proven network management technologies issued from the switching world, with state-of-the-art packet/circuit/fixed/mobile network management applications. Seamless integration of both technologies is offered by the XMC for network supervision and configuration and for 2G, 3G or mixed networks (UMA, IMS, NGN). The following domains are covered: Fault management, Configuration management, Performance Management, Security Management.
Charging Management is done by the A8965 Charging Gateway/C3S, by 8615 eCCF or 8610 ICC.
1.1 KEY FEATURES

The XMC is the management system of the both Fixed Networks and Mobile Networks, covering both Circuit and Packet Switched. It encompasses the centralized element management of these NEs and some network management functions: Unified platform administration mechanisms; Single platform login and common security management mechanisms; Common alarm management for all the managed elements; Common performance management for all the managed elements;
Common network hierarchical system view for the managed network;
Network level configuration management functions, encompassing several elements in order to simplify configuration management tasks and to ensure configuration data coherency between the different elements (e.g. for APN configuration);

Alcatel-Lucent

Date: Feb 2008
6/45
Network & Service External OSS
Local or Remote Operator Positions via LAN / WAN
- Global Fault Mgt - Provisioning functions - NE software & data Mgt - Staff and access control Mgt
A100 0 S12
A100 0S12
A100 0 S12
A1000 S12
Data Network
A100 0S12
XMC server(s)
A100 0 S12
Core Networks
XMC Integrated Management Center
- Flexible and evolving software and hardware architecture - Open interface to external OSSs
Local Operations: PC With Browser
Figure 1: XMC key features

Alcatel-Lucent

Date: Feb 2008
7/45
2 A1300 XMC FUNCTIONAL DESCRIPTION

This section highlights the main function provided by XMC.
2.1 FEATURE LIST Management of network elements both on Fixed/Mobile networks, covering circuit and packet domains - Both domains can be managed with the same product and be used either individually or in combination in the same network Network topology - With animated tree /map and covering the totality of the network Alarm collection and centralised alarm management - X733 alarm format current and historical alarm database - Alarm filtering, automatic and manual acknowledge
Centralised performance collection - All the observation counters concerning the complete network are centralised on the XMC - Available in XML format to external performance management tool for on-line real time traffic supervision and off-line traffic analysis functions - Files are retrieved periodically - periodicity is configurable Network Element counter definition depends on the type of network element - Alcatel-Lucent based NEs : list of counters is customisable by the operator - SNMP based Nes : list of counters is predefined or customizable Seamless navigation - Between integrated and non integrated (distributed) application - 3 tier architecture based on Java Web Start technology Centralised operators and profile management - Single Sign On - Operators sign-on defines the associated profile
North Interface for OSS access - Fault, Configuration, Performance 3GPP based model (Interfaces are Corba / XML based) - SNMP interface, restricted to alarms forwarding Optional North Interface SOAP/XML Log management - Centralized log browsing
Alcatel-Lucent
NE software download and backup/restore - Centralised for the whole network

Date: Feb 2008
8/45
-Actions and events logging
-Access to NE based log management XMC platform management - Online backup / restore - Full backup - Process supervision - Active / Ready hardware redundancy
Network Management Level functions for packet domain - RA 2G/3G management between SGSNs and DNS - Tariff Time Change between SGSNs and iGGSNs - APN management between iGGSNs and DNS - CACOM Network Management Level functions
Multi NE function scripting
Connection to A1342 QOSAC for traffic Analisys and traffic Supervision purpose
2.2 MANAGED NETWORKS

XMC allows to manage all of Alcatel-Lucent Core Network Elements and relesases, including:
Packet domain U2 (through OMC PS), and U3, namely
7500 SGSN, iGGSN, 7500GGSN, Cisco Routers, DNS, A8965 CDR.... GSM and CDMA domain through ISMC UMA network
Circuit domain U1x, U2, U3, software releases (through OMC CS) as well as NGN networks: 5060 WCS, 1430uHSS, 7570MG, A8965 CDR, routers,
5060 SUS, 7500 UCG GPRS gateway, 7500 USG Security gateway, 1430 uHSS Alcatel-Lucent IMS domain nodes, covering both Fixed and Mobile Networks: 1440 USDS, 1430 uHSS, 8650 SDM 5060 WCS, 5020 CSC; 5020 MGC,
5450 MRF, 5450 AGCF, 5450 ISCF, 5450 IRC
5420 CTS, 5420 PCM ,5430 SRB, 5750 SSC, ACME SD, Vital QIP 5920 PRBT
Gateways: 7570 MGW, 7510 TGW; 7500ABN, Reefpoint security gateway,

Alcatel-Lucent

Date: Feb 2008
9/45
Application servers : 5400 IAS, 5410 Presence, 5410 XDMS, 5430 Pts, 5430 IM, 5430 ECN IN applications : 8626 MMPR; 8610 ICC, 8615 IeCCF; portal with legacy managers : OMC-P, CMC-10, CMC-12
Figure 2: Example of IMS management with XMC with portal on OMC-P

Alcatel-Lucent

Date: Feb 2008
10/45
3 A1300 XMC FEATURE DESCRIPTION
3.1 ALARM HANDLING
Figure 3: XMC Alarm supervision panel Real-time collection and display of Alarms provide early detection of network faults and improve reaction time to anomalies. AS provides all services related to the handling of alarms in a distributed TMN system: o o Current alarm management; Alarm reporting and logging. Alarm management is provided by a generic application: Alarm Surveillance (AS).

Alcatel-Lucent

Date: Feb 2008
11/45
Figure 4: Alarm Management
3.1.1
CURRENT ALARM MANAGEMENT
The X.733 alarm reports are converted into Managed Objects called current alarms. It contains both the information sent by the EML agents and additional state information reflecting the management of the alarm by the operator: o Manually by the operator;
Acknowledgement state specifies whether any operator has seen the alarm. A current alarm can be acknowledged: Automatically according to a user-defined severity level.
o o
Cleared state indicates disappearance of a fault; the EML agent notifies alarm clearance.
Current alarms are removed from the active list to the historical list in the following ways: Once cleared; Manually, on operator request;
Reservation state is the current alarm owned by any operator; operations on a reserved alarm can only be performed by its owner.
On periodic purging according to user-criteria; On reaching storage capacity overflow criteria.
The criteria for the two automatic purging mechanisms can be based on alarm date and time, alarm severity, alarm type, alarm probable cause, affected network element, alarm states or a combination of these.
Alcatel-Lucent

Date: Feb 2008
12/45
Current alarm information including alarm creation, change of alarm states and alarm deletion is distributed through a well-defined open interface giving other TMN application easy access. Alarm synchronisation with EML agents is done: o o Manually on operator request;
Current alarm counters present a synthesis of alarm information to the operator. Alarm counters can be defined according to user-defined criteria such as alarm severity, type, state, probable cause, affected network element, or a combination of these. Alarm severity assignment profile is also an option available, allowing operator to define himself the severity level of an alarm. This feature is available only at the XMC level, and is not applicable in the embedded EML.
Automatically in case of restarts of re-establishment of supervision link..
3.1.2
ALARM REPORTING AND LOGGING
Alarm reports are received from agents through an open interface conform to the standard ITU-T X.733. The operator may consult the alarm log configuration and display and remove log records. Each time a current alarm has been removed, an historical alarm is created. A historical alarm contains both the information of the current alarm and additional information describing the reason of the removal. Historical alarms can be exported to flat files in a well-defined format for post-processing by external applications for special needs (alarm statistics...).
Lists of current and historical alarms are displayed to the operator according to user-defined criteria. These criteria can be based on alarm severity, alarm type, alarm probable cause, affected network element, alarm time and date, alarm states or a combination of these.
Each alarm in the current and historical alarm lists is displayed with a colour representing its severity. The mapping between alarm severity and colours is configurable. The layout of the current and historical alarm lists can be fully customised. The alarm attributes and the order in which they have to be displayed can also be specified by the user. Filtering of the displayed alarms is provided: the operator can define and store his own default customisation of display - and alarm criteria.
On/Off Correlation, i.e. correlation of Alarms with their related Offmessages allows to close alarms automatically when the system reports that the situation does no longer exist. Alarms can also be sent by email or SMS.

Alcatel-Lucent

Date: Feb 2008
13/45
3.2
TOPOLOGY MANAGEMENT
Figure 5: Topology management
The TOPO management provides a coherent and effective supervision of the managed network.
It is responsible for the management and persistency of the list of all managed elements within the network. It stores all the static information concening each network element, namely: Logical name, Type Friendly name, Release
IP address
Supervision state
It allows the operator to create, delete or modify network topology attributes as well as exporting the data in a XML file in 3GPP compliant format.
Alcatel-Lucent
Acces Control Domain

Date: Feb 2008
14/45
The current view (Figure 5: Topology management ) of the network is displayed via a tree. A geographical map view is also available , included if needed a background picture(Figure 6: Map view ).
Figure 6: Map view

Alcatel-Lucent

Date: Feb 2008
15/45
3.3 NETWORK SUPERVISION
Figure 7: Supervision management The Network Supervision component manages the dynamic states of the managed elements, namely:
Supervision state - declared or supervised. Nodes connected to the Management LAN should be explicitly declared via their OAM interface ( there is no auto discovery, since on the same management LAN, several manager and nodes could co-exist) Communication state state of the link between the NE and the XMC (polling frequence is Node dependant, from 40 sec to 1 minute) Administrative state Operational state Alignment status
Alarm synthesis highest severity alarm present on the NE
The operator may perform some operations on the Nes such as start / stop the supervision or lock / unlock. The components stores in a log file all state changes occurring on the Nes. From this component and for a selected NE, the operator can navigate to the map, the corresponding alarm panel, the software management view or the equipment management.
Alcatel-Lucent
Unacknowledged alarm synthesis - highest severity unacknowledged alarm present on the NE

Date: Feb 2008
16/45
The network view is customisable by operator that is, the view for a specified operator can be restricted to a subset of NEs, for example corresponding to a particular geographical region, using filtering facilities.

Alcatel-Lucent

Date: Feb 2008
17/45
3.4 ACCESS MANAGEMENT

Centralised administration of access rights and user profiles helps to protect the system against intentional and unintentional damage. The Security Management component, abbreviated as SEC, focuses on the security aspects of the TMN system: o o Specify, store and distribute Access Control Information throughout the TMN system; Profile the Graphical User Interface of the TMN system according to user access rights;
3.4.1 MAIN FUNCTIONALITIES

Main functionalitys provided are: o User access control:
Authentication based on username/password (per user basis); Ilicit access logging with log consultation (different criteria);
Inactivity period management; o User right management:
Limited number of unsuccessful login attempt (with user lock). Functional right management through "on duty" and "off duty" period management; Work schedule: based on day/hour with default or specific user calendar.
3.4.2 ACCESS CONTROL

Access Control Information may specify: o Users having log-in authorisation. They can be arranged in user groups having a dedicated role and access profile.
SEC supports User Interface profiling by building several resource - and registration files; according to the user access rights, these files are used to profile the user interface when this user logs in to the system. Access rights are thus reflected at HMI level by greying or removing menu items or icons.
Access Control Information is stored in a central database and can be consulted through graphical user interface and UNIX configuration files.
Default profiles include: Viewer, Network Operator, Administrator, SEC Administrator
3.4.2.1 NETWORK ACCESS DOMAIN
The XMC supports the NE access control. The target of this feature is to allow customer to define "management domain", and allowing an operator to work only on a restricted set of management domain, without visibiliy on the other domains. In particular, a management domain could be a "geographical area": An operator is allowed to manage a configured set of NEs

Alcatel-Lucent

Date: Feb 2008
18/45
The set of authorized NEs is configured by grouping already created NE together
A NE can belong to several groups. The XMC administrator can define as many domains as needed, without any constraint; he can give them any name.
The NE access control allows to restrict the functional rights of an operator, an operator keeps only one functional profile (viewer, operator or administrator): functional rights and domain rights are not combined.
3.4.2.2 FUNCTIONAL ACCES DOMAIN
XMC allows restricting the right of an operator to a functional basis. These access domains are inherited from the functional access domain provided by each node (i.e.: the subscriber Mngt on the ngHLR, the routing configuration on the 5020 call server)XMC administrator has the availability to configure operators profiles according these FAD. The profile of operators are stored in the XMC LDAP Database, and, when possible, are distributed in the node itself, avoiding double declaration.
3.4.3 NAVIGATION
The XMC product uses the latest web based, java web start technology as well as principles of distributed network management. In order to offer the user complete transparency of where applications actually run, the navigation component allows the user to navigate between XMC resident applications and other web based applications in a transparent, seamless manner.
3.5 EVENT AND LOG MANAGEMENT 3.5.1 NE LOGS

In a distributed network management environment, the log files corresponding to actions and events on the network elements are kept on the NE itself. A NE specific application and user interface enables the user to browse and work on the NE logs. NE logs cover operators accesses, operations, alarms, events and errors. Log files can be backed-up locally. In addition, centralized Log browsing is provided by XMC, for all the 5020 WCS / Tomix based/Application servers NE and for the XMC. This feature consists in collecting periodically (each hour per default) the log information on the nodes, parsing this information in order to populate a database and offering consultion / filtering / sorting / searching / exporting operations on these data. On demand collection is also provided. The filtering criteria are based on date, NE type, Event type, operator name, action result/progress, functional domain, error type or free text. The data collected by the XMC concerns the OAM logs only. The other trace/log files are excluded for several reasons: their content is usually reserved to Alcatel-Lucent experts. Their format is free text and can only be parsed with classical Unix tools (perl, grep,..)
3.5.2 XMC LOGS

Alcatel-Lucent

Date: Feb 2008
19/45
The XMC server manages directly a set of log files keeping track of XMC operations such as:
Access log files
2006/06/14 13:35:38 - access from FRORVD0C20959 (IP: 155.132.235.221), by user AlcatelLucentAdmin : success
Security log file
2006/06/14 13:28:38:sablet:SAS(0):Operator name=axadmin:LogNameCommand: SAS has started and is ready to accept incoming connections.
Administration operations (creation / deletion of NE, creation of users), relevant internal events ( XMC services, Trap received from NEs) and scheduled actions results.
20060614112910.595Z;stateChange;INFO;Process.logim();Process.logim();MON - Monitored Process state change;EVENT.stateChange;previousState.init<>free_text.change to freezing
Logs files are circular. Log file sizes are configurable.
3.6 JOB MANAGEMENT

XMC provides an internal Job management, providing a synthesis of all the NEs Jobs launched from XMC. This addresses the Multi_NE scriptiong, and the operations of Software Download and NE Backup/Restore. A dedicated panel shows the status of all the jobs launched.

Alcatel-Lucent

Date: Feb 2008
20/45
Figure 8: Job management
3.7 MULTI NE SCRIPTING

The XMC provides a centralized management for Multi NE scripting. This feature allows to: o Open Corba/Python session for Tomix based NE for access to OAM services: access control, hardware management, SS7management, performance management, log management, version change, applicative interfaces. Open CLI Session for A5020 WCS nodes: monitoring and provisionning domain or other CLI based nodes Launch immediate and differed script execution on a group of nodes of same type Store results of script execution in results files Handle script job state
o o o o
3.8 NE SOFTWARE MANAGEMENT

Alcatel-Lucent

Date: Feb 2008
21/45
This application enables the operator to manage and control the network elements software releases from a central position. It consists of the following operations, which can be manually controlled or can be scheduled and automatically performed:
3.8.1 NE SOFTWARE DOWNLOADING:

1. Import phase: this phase consists in loading on the software repository the software necessary to NEs downloading.
3. Activation phase: this phase consists in the activation of the new software in the managed NEs. 4. Validation: this phase consists in the declaration of the new software as the default one in the managed NEs
2. Download phase: this phase consists in downloading simultaneously the files into managed NEs (limitation to 20 NEs). The downloading progress status is displayed. In the case of tomix based Nodes, this is the node which is responsible of download session.
3.8.2 NE BACKUP/RESTORE:
o
The XMC offers the possibility to control backup/restore operations for the NE data (NE system backup is not supported) onto an XMC external disk. The backup repository server can be the XMC or an external server: configuration is done during the installation of the XMC. The operator is able to consult through a specific user interface the state of the backup jobs and the state of the backup repository. A Progress tool bar is provided. In case of failure, a message is provided to warn the operator. The NE restore is performed from the XMC, via the Embedded EML. This is done node per node. Note that external backup agent can be installed on XMC, allowing customer to use its own backup infrastructure, and to store NE data backup within this infrastructure.
o o
The backup can be scheduled or immediate and can be applied on one NE or a group of NEs.
o o
3.9 ON LINE DOCUMENTATION

Electronic customer documentation is delivered by Alcatel-Lucent as an integral part of its products and is integrated in the Alcatel-Lucent 1300 XMC. Each customer documentation package is composed of document sets that are enriched with display and viewing capabilities to become what is called a "collection". There is one collection of electronic documents for a given product release (version, date of issue). Such collections are accessed through a dedicated documentation user interface, commonly known as the "electronic library". Stored and shipped on CD-ROM, an entire customer documentation package may be consulted via an appropriately configured personal computer, workstation or operator terminal.

Alcatel-Lucent

Date: Feb 2008
22/45
3.10 CONFIGURATION MANAGEMENT

This application is implemented at two different levels:
M
The first one is NE dependent as it resides directly on the NE. A graphical interface specific to the Network Element will enable the provisioning of the network element The second, at XMC level, which enables the provisioning at multiple NE level o o o Multi NE scripting
3GPP CM: basic in corba or bulk via XML data files for SS7 configuration XML Soap for MGC30 provisionning.
In addition, where appropriate, the XMC provides co-operative management function to simplify network level configuration; for example Routing Area con figuration in a GPRS network. In the specific case of the A5060 WCS, the ADAMS tools can be used from the XMC when auditing the configuration is required. This tool allows the audit of the configuration parameters on the A5060 WCS, to compare with a referential.
These features allow customers to develop dedicated provisioning procedures (tailored service)
3.11 EQUIPMENT MANAGEMENT

This application shows the operator the network element from the aspect of the physical layout of the NE (with status information mapped on it). The application is NE dependent as it resides directly on the NE.

Alcatel-Lucent

Date: Feb 2008
23/45
3.12 OBSERVATION MANAGEMENT

Thanxs to the embedded EMLs, XMC enables the operator to configure, activate (reporting period, granularity period) and visualise network element counters for each individual network element. In addition, the XMC centralises, for the whole network, the resulting performance files in a central location in XML 3GPP format. The performances files are collecting (through SNMP or using FTP for nodes providing counter in files) from the node, according to the reporting period (minimium 15 min), translated in 3GPP XML format, and then can be exported to another system (A1342 QoSAC, Other external tool) for analysis.
As an option, A1342 QoSAC tool is available for the analysis of the QOS for the network. In particular, this allows operator to select a set of counters to be displayed, to define KPIs for Alarm generation on XMC, and to provide QoS Reports.
3.13 EXTERNAL INTERFACES 3.13.1 3GPP

The external interfaces provided are based on the 3GPP standard R6; they cover the alarm (AM) domain, the configuration domain (CM) and the performance management domain (PM) in CORBA / XML format. The objects / modules (IRP Integration Reference Point) which are implemented are: EP IRP (Entry Point) Notification IRP Common Management
CS IRP (Communication Surveillance) FT IRP (File Transfer) ( via ftp, sftp) Alarm IRP Alarm Management
Kernel IRP
Configuration Management
BasicCM IRP BulkCM IRP Performance Management
PM IRP (Performance Management) The interfaces are only partially covering legacy nodes managed through existing OMCs (OMC CS, OMC PS, CMC): The AM domain is fully covered, the PM domain is covered in as much as all performance files are centralised in a single format (xml) and in a single point, but the CM domain is not
Alcatel-Lucent

Date: Feb 2008
24/45
covered. Provisioning interfaces for these networks still go through the specific interfaces, which exist, on the corresponding OMC.
3.13.2 SNMP
XMC provides a northbound interface allowing external OSSs to retrieve all the alarms, according to SNMP trap. This includes also the alarms provided by legacy managers (OMC-CS, PS, OMC-P CMC). This is a generic mapping , providing also resnchronisaton capabilities?
3.13.3 XML/SOAP
In addition, an XML/SOAP interface can be supported, in order to provision the MGC30, and to translate XMC/SOAP command from OSS to native Corba MML command. In XMC 7, this XMC/SOAP interface will be extended by re-using CMC-12 and OMC-P XML/SOAP north interface.
3.14 XMC PLATFORM FUNCTIONS 3.14.1 XMC PLATFORM BACKUP/RESTORE

The XMC offers internal backup / restore facilities of its own system and data partitions in order to recover following a major fault (disk crash, corrupted file system, etc)
M
Data backups can be performed as either full backups or partial backups (incremental). During the backup, the processes are automatically put in a frozen state.
Data back up the system is running but data has been lost or is corrupted
Data backups can be performed by functional domain (topology, performance, alarms, security, XMC configuration, operators configuration)
M
System backup the system will not boot or initialise correctly
Note that external backup agent can be installed on XMC, allowing customer to use its own backup infrastructure.
3.14.2 XMC PLATFORM MONITORING

The XMC product implements a number of monitoring services to ensure service continuity of the XMC platform; these are:
M
Process supervision and (auto) restart
Disk space monitoring with possible threshold definition and alarm generation Memory occupancy with possible threshold definition and alarm generation CPU load Hardware monitoring (disks, PSU, I/O cards)
Alcatel-Lucent

Date: Feb 2008
25/45
XMC software inventory
Note that advanced platform monitoring function are provided by external 3rd PP such as HPGlance.
3.14.3 GEOGRAPHICAL REDUNDANCY CONCEPT

The XMC can work in a redundant scheme based on geographical redundancy where the hardware is duplicated on two separate sites, the machines work in an active / ready mode with mutual supervision via a heartbit mechanism. The data is automatically replicated between the two machines. The switch over is performed under the administrators control. Thanks to the embedded EML, it is still possible for an operator to work on the node while the Management system is not fully operational. The total time of service perturbation is less than 5 minutes.
3.14.4 TIME MANAGEMENT

The XMC can be synchronised on an external timeserver using the NTP protocol. It can also act as a server for the network elements if required.
3.15 NETWORK MANAGEMENT 3.15.1 LATENCY REPORT MANAGEMENT AND TRACING

This feature is specific to UMA network and concern the A 5020 WCS: The XMC periodically builds a Latency report per NE, which contains statistics about UMA Subscriber Location Service Based events. The calculated statistics concerns latency measurement regarding 2 types of subscriber location event requests. The format of the report is XML or CSV.
The Tracing function is applicable on WCS and GGW : Tracing a UMA subscriber : - for subscriber observation following customer complaint, - on suspicion of equipment malfunction, - as a maintenance aid and an integration tool, e.g. during deployment of UMAN.
The operator is able to easily characterize encountered problems, i.e. the solution can not rely on just copying messages exchanged on different interfaces (e.g. URR, A) in files . Furthermore, the operator is able to get the current UMA registration status of the subscriber, i.e. whether the subscriber is currently registered or not, and if yes, on which UNC.
3.15.2 RA/RNC MANAGEMENT

Alcatel-Lucent

Date: Feb 2008
26/45
This feature allows the monitoring of the data consistency between Serving GPRS Support Node (SGSN) and Domain Name System (DNS) configuration. The XMC is in charge of monitoring the SGSN(s) in order to get their RA/RNC configuration. The monitoring is triggered either by the SGSN or automatically: resynchronisation. The XMC automatically updates the primary DNS(s) configuration regarding the list of RA/RNC objects known by the SGSN(s).
The XMC offers an Audit feature, which allows to check the DNS configuration consistency according to the data gathered on all DNS(s) and SGSN(s).
The XMC allows the resynchronisation of the DNS(s) according to the results of a previous Audit. The OMC offers a synthetic view (Tree/Table) of the objects managed by the SGSN/DNS.

Alcatel-Lucent

Date: Feb 2008
27/45
4 XMC OVERALL ARCHITECTURE
The XMC concept is based on a portal approach interfacing the existing OMCs and the new NE embedded element managers.
Single Platform Login Common Security Management Common Performance Management Common Alarm Management Common Network Map Seamless navigation Northbound Interface Management of both Circuit, Packet, Network Level UMA, @IMS domain Management Log management Software Download and backup Restore OMC Plateform auto surveillance Geographical reduncandy
A L M A P
OMC CS, PS, CMC, ISMC, OMC-P
Spatial WEM client
IP NE Management
Management
Tomix ATCA
Element Level Management
X.25
WEM Spatial
IP
XMC
MSC HLR ...
EML
Santera MGW Alcatel MGW
In such an approach, integartion between existing OMC and new element managers is done in a loose manner. This loose integration enables: Existing OMCs investment saving
Figure 9: XMC Overall Architecture
To preserve existing product look & feel
To de-couple XMC road maps for different network technologies
To quickly integrate new type of equipment while offering integrated network supervision and unique interface to OSS.
To guarantee the stability of the existing installed network and network manangement
This portal approach can be extended to other existing Alcatel-Lucent 1300 OMC equipement offering standard external interface. The main benefits of the Alcatel-Lucent network Management solution are:
Alcatel-Lucent

Date: Feb 2008
28/45
Interoperability XMC provides standard 3GPP/CORBA/SNMP north interfaces for OSS access
Open architecture for other Alcatel-Lucent XMC The portal architecture is open and can be extended to other Alcatel-Lucent Network Manager to provide unified network view and reduction of operator workplaces.
Independency between element manager level and network management level This distributed architecture - Removes the constraints for synchronisation between NE evolutions and XMCs - Simplifies the upgrade procedure: no impact on XMC system in case of NE upgrade - Offers one unique EML software accessible both from remote or local point - Reduces delay (no need to have specific developments in XMC, less network validation)
4.1 HARDWARE ARCHITECTURE

The XMC, is built on the hardware platform composed of a IT server (HP RP4440 server running the operating system HP UX 11i; or HP DL 580 intel X86 based server, running Linux). XMC server(s) are connected to a fast Ethernet LAN to the operator workplaces and printers. They provide client/serverdistributed architecture, the applications running on different servers.
Operator workplaces (OWP) are PCs. Prefered choice is XP, but Linux is also applicable. They can be local or remote from the Network Operation Center site.
NE sub net 2
External OSS (if any) Additional NM eqts OWPs System console
NE net 1, ...
NTP server (if any) Web Console ENMS
100 Base-T LAN Ethernet
Printer
1GbE Bkp LAN
External storage
Figure 10: XMC Network Architecture

Alcatel-Lucent

Date: Feb 2008
29/45
4.1.1 XMC SERVER

XMC server is equipped in standard with: DAT and DVD drives, Optional external storage cabinet containing up to 10 * 73/140 Gbytes disks. The disks are provisioned by pairs (mirroring) according to the storage capacity needed.
Different hardware configurations are possible
Field Trial
HP B2600 Workstation: 2 GB memory, 1* 36 GB disk (for field trial only or very small network - no evolution possible) C8000 HPUx Server. 2 Gb memory, 1* 73 Gb disk (for field trial only or very small network - no evolution possible)
ML 350 G4 Linux server, 2 Gb memory, 1* 73 Gb disk (for field trial only or very small network - no evolution possible)
Small / Medium / Large
HP RP4440 Unix Server or HP DL 580 Linux Server 2, 4, 6 or 8 CPUs From 6 to 18 GB memory
Existing Legacy configurations
From 2 * 73Gb/140GB disks + external storage
RP5430, 5470 servers - from 2 to 4 CPUS
Configuration
Server
CPUs
RAM (Gb)
Internal Mirrored disks (Gb)
External Mirrored disks (Gb)
Ethernet ports

Alcatel-Lucent

Date: Feb 2008
30/45
ENMS_2 - legacy ENMS_2 (Unix) ENMS_2 (Linux) ENMS_4(Unix) ENMS_6(Unix)
rp5430 rp4440 dl580 rp5470 rp4440 dl580 dl580 dl580 rp4440 rp4440
2 2 2 4 4 4 6 6 8 8 1 2 2
6 6 6 12 12 12 14 14 18 18 2 2 2
2x36
2x144 2x144 2x36 2x144 2x144 2x144 2x144 2x144 2x144 1x 36 1*73 1*73
2x36
Acc. to conf. Acc. to conf. Acc. to conf. Acc. to conf. Acc. to conf. Acc. to conf. Acc. to conf. Acc. to conf. Acc. to conf. 1x36
3 5 3 5 5 5
ENMS_4 legacy ENMS_4(Linux) ENMS_4(Linux) ENMS_8 (Unix) ENMS_8(Linux) B2600 (Field Trial)
pa 8600 pa8800 proliant
1 1
C8000 (Field Trial)
ML 350 G4 (Field Trial)
Table 1: XMC ENMS server configuration
4.2 SOFTWARE ARCHITECTURE 4.2.1 GENERAL CONCEPT

Each software module is split into an Information Manager and a User Service Manager (GUI) Each Information IM/USM handles a management area

Alcatel-Lucent
Either a general purpose area (e.g. network topology, network supervision, alarm management...), independently of the Network Element technology, Or a network specific area (e.g. APN management, ...)
Each NE communication Manager
Handles the communication with the related Network Element with the appropriate management protocol, Provides the same interface to the general purpose IMs
Date: Feb 2008
31/45
Each NE provides its Element Manager
Provides specific interface to the network specific IMs Accessed via web browser
Uploaded and run via JNLP (Java Network Launching protocol)
Ne Network Element Managers Navigation Bus
Generic or network specific User Interfaces (USM)

CORBA Bus
Generic or network specific Information Managers (IM)

CORBA Bus
Network Element specific Communication Managers (IM)
Figure 11: XMC General concept
4.2.2 DETAILED SOFTWARE ARCHITECTURE

XMC is based on the Alcatel-Lucent standard platform ALMAP, the common platform for the new generation management systems developed within Alcatel-Lucent. The added-value of this common platform is that it enables integrated management across different network technologies, thus providing the following advantages: Same ergonomics for all new generation OS Easier integration between Alcatel-Lucents Operation Systems (OS)
Simplified configuration and maintenance of the OS itself, enabling homogeneous operator administration, access security, OS backup and restore, etc Easy operator access to all management functions

Alcatel-Lucent

Date: Feb 2008
32/45
It also implements state of the art approach such as: Full Java / Corba portable software
Java Web Start technology for the user interfaces Clear internal interfaces enabling fast and easy introduction of new network elements
Distributed management: a distributed architecture is used where network element management software and associated graphical user interface reside on the network element themselves.
3GPP North Interface
SNMP North Itf (Alarms)
Nw Perf
Analysis
CORBA /XML 3GPP Itf IM SNMP Itf IM Network mgt USM
Navigation Bus Supervision USM CORBA Bus Supervision IM CORBA Bus Software IM Topology IM Software USM Topology USM
Ne Network Element Managers
AS USM
Notification Service
Naming Service
Perf mgt IM
Network mgt IM
ASIM
Other OSS I/F OMC FTP/CORBA
Tomix CM
WSS CM SNMP/FTP
SNMP CM
GGSN CM
PS,CS CMC,ISMC
Tomix (*)
MSC Atrium
IP node
GGSN
Figure 12: XMC Software Architecture (Tomix based NEs: Ng HLR, IM HSS, WAS, SGSN)

Alcatel-Lucent

Date: Feb 2008
33/45
5 TECHNICAL DESCRIPTION
5.1 PROTOCOLS AND INTERFACES 5.1.1 INTERFACE BETWEEN XMC AND NETWORK ELEMENT
All connections to XMC are done using the IP network (X25 is only used through the OMC CS, 1300 CMC, ISMC). The Network Elements use standard protocols such as IP/Corba, IP/http or IP/SNMP. These southbound interfaces are proprietary.
External O SS
IIO P/ FT P/SFTP /SN M P
Operator W orkplaces
IIOP H TTP
X 11 Legacy NEs X25 OM C-CS, O M C PS, CM C,
http
SSH
IIO P / F TP
X M C server
IIO P
SN M P F TP
http/ SSL https
SN M P NE, iGG SN, A trium
Tom ix NE
Figure 13: Interface between XMC and NEs
5.1.1.1 INTERFACES CAPACITY AND BANDWIDTH

Alcatel-Lucent

Date: Feb 2008
34/45
The XMC provides Ethernet 10_10-1000Base-T interface to the managed Core Network NEs. 5.1.2 INTERFACE BETWEEN XMC AND OTHER OMCS All connections between XMC and other OMCs are done using the IP network The Corba interface in used for interconnection with OMC CS, OMC PS, 1300 CMC. SNMP and FTP interfaces are used for interconnection with OMC-P Other interfaces may be used as required
5.1.3 INTERFACES BETWEEN XMC AND OSS (OPTIONAL FEATURES)

The XMC provides open North interfaces to external systems, based on 3GPP standards. They cover fault, topology, configuration and performance management.
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.
5.1.3.1 INTERFACES CAPACITY AND BANDWIDTH
External interfaces are provided through the Ethernet 10-100-1000 Base-T LAN, thanxs to an OmniSwitch 24 ports. 2 OSS maximum can be connected to each interface at a time. A 1Gb port is reserved for connection to a customer backup LAN.
5.2 XMC RESILIENCE 5.2.1 PLATFORM RESILIENCE

XMC Server redundancy is ensured at different levels: The use of mirrored internal disk guarantees the system availability,
The use of mirrored high availability disk arrays ensures the database integrity,
An uninterruptible power supply (UPS), takes care of bridging, even in the event of prolonged voltage breakdowns.

Alcatel-Lucent

Date: Feb 2008
35/45
5.2.2 MTBF SYSTEM AVAILABILITY

A1300 XMC total , ( MTBF about 49 000 Hours for HP RP44xx, about 60 000 for HP DL 580, about 124 000 for the internal switch 6800-24 ) corresponds to a figure significantly less than one major failure per 5 years. Precise information is available from Alcatel-Lucent under a confidentitiality procedure with server provider. The XMC provides 99,995 high availability, in geographical redundancy, and 99,95 , in case of simplex server.
5.3 DISASTER RECOVERY

Please refer to chapter Redundancy plan for the description of the types of redundancy proposed for XMC. Different scenarios connectivity loss (addressed by link redundancy implemented at DCN level), problem at server level (mirrored disks and redundant power supply) site disaster (site redundancy) Data integrity In case of loss of connection to the NEs, resynchronization mechanisms allow to realign data between XMC and NEs there is no loss of data for alarms (all NEs) and observations (all NEs except SNMP NEs which do not store files locally). This is done by date comparison between the data available on the XMC and the data still available on the nodes. At server level, data integrity is ensured by mirrored disk. Data integrity in case of site disaster is ensured thanks to periodical automatic replication of XMC data from the main active XMC to the backup active XMC.
5.4 CAPACITY
Through the different server sizes the XMC scales to: the number of operator connections the size of the managed network
the management applications of the XMC

Alcatel-Lucent

Date: Feb 2008
36/45
Thanks to the distributed management architecture of the XMC, the GUI of the XMC can be distributed onto the operators workplaces.
The XMC server can be scaled easily from 2 to 4, 6 and 8 CPUs and corresponding memory sizes inside a unique hardware box. Additional disks can also be added leading to a fully evolutive configuration. Because of the distributed architecture on the Element Management Layer, only single server configurations are now proposed. These figures are given as an indication precise dimensionning is required for each network and options. These figures correspond to a typical mix of circuit and packet network elements with an XMC with no options and no external interfaces apart from the Alarm Management 3GPP module. 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, OMC-P,) they count as 0,8 and the number of operators accessing the legacy network does not impact the XMC dimensioning.
NE/op 5 25 50 100 150 ENMS1 ENMS2 NA NA NA 2 ENMS1 ENMS2 ENMS2 NA NA 5 ENMS1 ENMS2 ENMS2 ENMS4 ENMS6 25 NA NA ENMS4 ENMS6 ENMS8 50 NA NA NA ENMS8 ENMS8 100 NA NA NA NA ENMS8 150
Table 2: ENMS versus XMC Capacity
5.5 TECHNICAL DATA

For the standard configuration, an XMC 22U cabinet contains the following devices:
One HP server of RP4440 series/HP Ux 11i v1/ PA rRISC , or HPLinux Server DL 580 running Red Hat, Proliant Intel Based Mirrored disks, One DAT,
One DVD ROM,
Details information related to the HP servers are available on http://www.hp.com

Alcatel-Lucent
One Switch Router

Date: Feb 2008
37/45
Environment certificates ( RoHS ) are available on hp site :
http://h40047.www4.hp.com/certificates/sublevel.html?id=141
5.5.1 PHYSICAL DIMENSIONS OF EACH ELEMENT

The XMC is composed of several devices stored in a 19 cabinet, 22U.The cabinet dimensions are the following:
Node XMC Cabinet Height (mm) Cabinet Width (mm) 1249.9 596.2 CabinetDepth(mm) 996,2 Weight of equipped cabinet (kg) 196.5
5.5.2 HEAT DISSIPATION
The table below lists the known heat dissipation figures for the OMC components: Heat Dissipation / hour OS6800-24 Ethernet switch (24 ports) HP rp4400 server HP DL 580 server Disk Array 41.228 Btu/hour From 1400 to 4000 BTU (tbc) Maximum: 5457 BTU 3000 BTU
5.5.3 POWER CONSUMPTION
Power consumption of all OMC component are listed in the table below : Power Consumption max HP 9000 rp4400 server 100240VAC, 50/60Hz 1600 W HP DL 580 Proliant 100240VAC, 50/60Hz 1566 W DDS4 LVD DAT 90264 VAC, 5060 Hz 137 W Internal Disk 100240 VAC, 5060 Hz 180 W External Disk Array 100240 VAC, 5060 Hz 650 W HP LaserJet Printer 220240 VAC, 5060 Hz 330 W OS6800-24 Ethernet switch 220240 VAC, 5060 Hz 12.5 watts (24 ports) Environmental conditions and requirements The table below describes the environmental conditions of the Core Network OMCs:
HP 9000 servers Electromagnetic Interference
Complies with FCC Rules and Regulations, part 15, as a Class A digital device. Manufacturers Declaration to EN55022 Level A, VCCI Registered, Class I, Korea RLL Operating Temperature 5 35C (41 95F) Non-Operating Temperature -40 70C (-40 158F) Maximum Rate of Temperature 10C/hour 1300 XMC PRODUCT DESCRIPTION RELEASE 6.X
Alcatel-Lucent

Date: Feb 2008
38/45
Change Non-Operating Relative Humidity Operating Altitude Non-Operating Altitude OS6800-24 switch Temperature Operating Storage Humidity Operating Storage Safety Compliance Cisco router Temperature Operating Non-operating Humidity Noise Level Regulatory compliance DL580 servers
15% to 90%, non-condensing To 3.0km (10,000 ft) above sea level To 4.5km (15,000 ft) above sea level 0 to 40 C 20 to 70 C Operating relative humidity: 10 to 90% non-condensing Storage relative humidity: 10 to 95% non-condensing Canada CSA 60950, Germany TUV, GS Mark for Germany, Australia c-Tick for Australia, China CCC, CB Certification (per IEC 60950) 32 to 104F (0 to 40C) -13 to 158F (-25 to 70C) 5 to 95% non-condensing 38 dbA min./ 42 dbA max. FCC Part 15 Class B. For additional compliance information, refer to the 2600 Series Compliant with RoHS legislation (see NOTE) (e.g. EU, China, etc.) The use of the noted material in a solution and subsequent resale of that solution will result in the solution no longer meeting the requirements of RoHS legislation. NOTE: Directive 2002/95/EC restricts the use of lead, mercury, cadmium, hexavalent chromium, PBBs and PBDEs in electronic products. Countries/regions outside the EU, eg. China, are introducing similar legislation. References to 'RoHS legislation' means requirements of Directive 2002/95/EC or to similar substance restriction legislation enacted by any country/region outside the EU. 50 to 95 F (10 to 35 C) -20 to 140 F (-29 to 60 C) Relative Humidity (non-condensing) Operating 10% to 70%
RoHS
Operating Temperature Non-Operating Temperature Non-Operating Relative Humidity
5.6 DIAL-IN CAPABILITIES
Modem access to the XMC is not supported.

Alcatel-Lucent

Date: Feb 2008
39/45
5.7 SERVICE RESTORATION TIMES

Operation time
Switchover (synchronisation done 5 min ) Manual resynchronisation + switchover
15 min 20 min
Full start of XMC (including operating System) Full Backup of XMC Full restore of XMC
55 min
Full new installation of XMC Minor upgrade
55 min
( including Operating System)
3,5 hours in HP UX 1.5 hours in Linux
Table 3: Service Restoration Times
30 minutes
5.7.1 XMC UPGRADES XMC release upgrades can be divided into two groups:
Major release upgrades, generally synchronized with Core Network release upgrades; Minor release upgrades, which are XMC maintenance deliveries.
Major release upgrades bring major functional evolutions and may require complete XMC reinstallation (only in case of changes in 3PP software or Operating sustem). Minor release upgrades always consist in patching the running XMC software. There is only a partial interruption of the supervision service, if some processes needs to be frozen while performing the patch.
At Core Network release upgrade, the XMC needs not necessarily be upgraded as the network release now carries its specific element level management software. Depending on the type of upgrade (needing XMC reinstallation or not) and on the hardware configuration of the XMC, different upgrade procedures can be proposed. The time taken for a migration is, at worse, the time taken for a complete re-installation.

Alcatel-Lucent

Date: Feb 2008
40/45
5.7.2 INTEGRATION WITH NETWORK MANAGEMENT SYSTEM Integration with an external network management system is possible through the external interfaces offered by the XMC. Please refer to the chapter External Interfaces for the description of these interfaces.
5.8 INSTALLATION & COMMISSIONING REQUIREMENTS 5.8.1 XMC INSTALLATION

Basic requirements for the room where the XMC is installed are : have air conditioning, have a raised floor, have double secured 220 V power supply, offer access to the external networks (accessing to the managed network elements). Detailed installation and commissioning requirements listed in the installation documentation.
5.8.2 NETWORK MANAGEMENT COMMISSIONING

Thanxs to the Embedded EML technology, the installation of the nodes and the installation of the XMC can be de-coupled: the GUI required to install/configure a node can be reached from the XMC itself, or directly from the node console. In other words, a node can be installed with ou without XMC presence. In addition to the declaration/configuration, when the Qosac option is available, the commissioning of the network takes benefit from the Qosac predefined reports.

Alcatel-Lucent

Date: Feb 2008
41/45
6 DOCUMENTATION
6.1 XMC DOCUMENTATION

XMC document collection , is composed of: Name Platform Administrator Guide Network Management Reference 3BL65020FDAA Comment This document describes the administrative tasks from the Alcatel-Lucent 1300 XMC Operation and Maintenance This document describes the configuration tasks from the Alcatel-Lucent 1300 XMC Operation and Maintenance Center-Core Network This document describes the software management tasks from the Alcatel-Lucent 1300 XMC Operation and Maintenance Center-Core Network Description of the general principles for Fault Management. Description of the SNMP north interface. This document describes how to manage performance from an Alcatel-Lucent 1300 XMC. It also lists SNMP counters. This document applies beginning with Release 5.3 These documents lists all alarms for each managed network element, and corrective actions or procesures to be Applied These documents lists all counters for each managed network element
Table 4: XMC Documentation
3BL65018FDAA
XMC Data Backup Management Fault Management XMC SNMP Alarm Forwarding Performance Management
3BL77030FDAA
3BL65017FDAA 3BL59971FDAA 3BL65019FDAA
Alarm dictionaries
3BLxxx
Counter lists
3BLxxx
Documentation is delivered on CD, and can be installed on the XMC server itself, or on any XP PCs. Documents are available in HTML or PDF format.
Alcatel-Lucent

Date: Feb 2008
42/45
6.2 OTHER RELATED DOCUMENTATION:

XMC Alarm management feature Description 3DN00811AAAA XMC Geographical redundancy Feature Description 3DN00810AAAAFSZZA XMC Performance Management Feature Description 3DN 00812 AAA FS ZZA XMC Security Strategy Feature Fescription 3BL 59923 GBAA DTZZA XMC 3GPP Northbound interface SOC 3DN00832AAAAFOZZA XMC Security strategy 3BL59923GACADTZZA A1342 QOSAC Product description 3DN 00770 AAA

Alcatel-Lucent

Date: Feb 2008
43/45
7 GLOSSARY
AAL API CS APN DHCP DNS ETSI ATM Adaptation Layer 5 Access Point Name Circuit-Switched
Application Programming Interface
eTOM enhanced Telecom Operations Map
Domain Name System
Dynamic Host Configuration Protocol
iGGSN GPRS GSM HLR IP
Intelligent Gateway GPRS Support Node General Packet Radio Service Home Location Register Internet Protocol
European Telecommunication Standardization Institute
Global System for Mobile communication
LAN
NGOSS NMC NS OAM XMC PDP O&M PDN QoS RA
Local Area Network
Telemanagement Forum's New Generation Operations Systems and Software Network Management Centre
Operation, Administration and Maintenance Operation and Maintenance Packet Data Network Quality of Service Packet Data Protocol
Network Service
Operation & Maintenance Center Core Network
PLMN
Public Land Mobile Network
SGSN SID SNMP SSH TCP
Routeing Area
Serving GPRS Support Node Simple Network Management Protocol Transfer Control Protocol Secured SHel Shared Information/Data
TMF
Alcatel-Lucent
TeleManagement Forum

Date: Feb 2008
44/45
TMN VLR
Telecommunication Management Network Visited Location Register

Alcatel-Lucent

Date: Feb 2008
45/45

1300 CDC PD tcm228-1474891635

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

1300 CDC PD tcm228-1474891635

Uploaded by

Copyright:

Available Formats

PRODUCT DESCRIPTION

CROSS-DOMAIN MANAGEMENT CENTER ALCATEL-LUCENT 1300 XMC PRODUCT RELEASE R6.X

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

A1300 XMC FUNCTIONAL DESCRIPTION..............................................................8

3.5 3.6 3.7 3.8 3.9

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

5.2 5.3 5.4 5.5

5.6 5.7 5.8

DIAL-IN CAPABILITIES ........................................................................................ 39

DOCUMENTATION ............................................................................................. 42 6.1 6.2 OTHER RELATED DOCUMENTATION: ................................................................ 43

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

Figure 13: Interface between XMC and NEs ...................................................................................34

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

1.1 KEY FEATURES

Common network hierarchical system view for the managed network;

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

Network & Service External OSS

Local or Remote Operator Positions via LAN / WAN

XMC Integrated Management Center

Local Operations: PC With Browser

Figure 1: XMC key features

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

2 A1300 XMC FUNCTIONAL DESCRIPTION

NE software download and backup/restore - Centralised for the whole network

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

-Actions and events logging

2.2 MANAGED NETWORKS

Packet domain U2 (through OMC PS), and U3, namely

5450 MRF, 5450 AGCF, 5450 ISCF, 5450 IRC

Gateways: 7570 MGW, 7510 TGW; 7500ABN, Reefpoint security gateway,

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

Figure 2: Example of IMS management with XMC with portal on OMC-P

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

3 A1300 XMC FEATURE DESCRIPTION

3.1 ALARM HANDLING

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

Figure 4: Alarm Management

CURRENT ALARM MANAGEMENT

On periodic purging according to user-criteria; On reaching storage capacity overflow criteria.

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

Automatically in case of restarts of re-establishment of supervision link..

ALARM REPORTING AND LOGGING

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA

Figure 5: Topology management

Acces Control Domain

3DN 00801 AAAA DEZZA

Figure 6: Map view

1300 XMC PRODUCT DESCRIPTION RELEASE 6.X

3DN 00801 AAAA DEZZA