1300_CDC_PD_tcm228-1474891635

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 authoriza-tion

PRODUCT DESCRIPTION

CROSS-DOMAIN MANAGEMENT CENTER ALCATEL-LUCENT 1300 XMC

PRODUCT RELEASE R6.X

Edition 1.8

#3D

R200

03Q

MW

WPT

AHF0

2


Date: Feb 2008

2/45


SUMMARY

1 INTRODUCTION ....................................................................................................6 1.1 KEY FEATURES ..................................................................................................... 6

2 A1300 XMC FUNCTIONAL DESCRIPTION..............................................................8 2.1 FEATURE LIST ....................................................................................................... 8 2.2 MANAGED NETWORKS ....................................................................................... 9

3 A1300 XMC FEATURE DESCRIPTION .................................................................. 11 3.1 ALARM HANDLING ............................................................................................ 11

3.1.1 CURRENT ALARM MANAGEMENT ............................................................ 12 3.1.2 ALARM REPORTING AND LOGGING........................................................ 13

3.2 TOPOLOGY MANAGEMENT .............................................................................. 14 3.3 NETWORK SUPERVISION ................................................................................... 16 3.4 ACCESS MANAGEMENT .................................................................................... 18

3.4.1 Main functionalitIES .................................................................................. 18 3.4.2 ACCESS CONTROL.................................................................................. 18 3.4.3 Navigation ............................................................................................... 19

3.5 EVENT AND LOG MANAGEMENT ...................................................................... 19 3.5.1 NE Logs ................................................................................................... 19 3.5.2 XMC Logs................................................................................................. 19

3.6 JOB MANAGEMENT........................................................................................... 20 3.7 MULTI NE SCRIPTING......................................................................................... 21 3.8 NE SOFTWARE MANAGEMENT .......................................................................... 21

3.8.1 NE Software downloading: ....................................................................... 22 3.8.2 NE backup/restore: .................................................................................. 22

3.9 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


Date: Feb 2008

3/45


3.15.2 RA/RNC management .............................................................................. 26 4 XMC OVERALL ARCHITECTURE ........................................................................... 28

4.1 HARDWARE ARCHITECTURE............................................................................... 29 4.1.1 XMC server............................................................................................... 30

4.2 SOFTWARE ARCHITECTURE ............................................................................... 31 4.2.1 General concept....................................................................................... 31 4.2.2 detailed software architecture ................................................................... 32

5 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 XMC RESILIENCE................................................................................................ 35 5.2.1 Platform Resilience.................................................................................... 35 5.2.2 MTBF System Availability........................................................................... 36

5.3 DISASTER RECOVERY ......................................................................................... 36 � Different scenarios.................................................................................... 36 � Data integrity............................................................................................ 36

5.4 CAPACITY .......................................................................................................... 36 5.5 TECHNICAL DATA.............................................................................................. 37

5.5.1 Physical dimensions of each element......................................................... 38 5.5.2 Heat dissipation........................................................................................ 38 5.5.3 POWER CONSUMPTION.......................................................................... 38

5.6 DIAL-IN CAPABILITIES ........................................................................................ 39 5.7 SERVICE RESTORATION TIMES ........................................................................... 40

5.7.1 XMC upgrades ......................................................................................... 40 5.7.2 Integration with Network Management System .......................................... 41

5.8 INSTALLATION & COMMISSIONING REQUIREMENTS........................................ 41 5.8.1 XMC installation ....................................................................................... 41 5.8.2 Network management commissioning ...................................................... 41

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

7 GLOSSARY........................................................................................................... 44


Date: Feb 2008

4/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 5: Topology management..................................................................................................14 Figure 6: Map view ......................................................................................................................15 Figure 7: Supervision management...............................................................................................16 Figure 8: Job management ..........................................................................................................21 Figure 9: XMC Overall Architecture...............................................................................................28 Figure 10: XMC Network Architecture ............................................................................................29 Figure 11: XMC General concept...................................................................................................32 Figure 12: XMC Software Architecture ............................................................................................33 Figure 13: Interface between XMC and NEs ...................................................................................34


Date: Feb 2008

5/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


Date: Feb 2008

6/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 Man-agement 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 appli-cations. 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 cov-ered: • 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);


Date: Feb 2008

7/45


Figure 1: XMC key features

- Global Fault Mgt

- Staff and access control Mgt

- Open interface to external OSS’s

Local or Remote Operator Positions via LAN / WAN

Network & Service External OSS

A100 0 S12 A100 0 S12

A100 0 S12 A100 0 S12

A100 0 S12 A100 0 S12

Local Operations: PC With Browser

Data Network XMC

server(s)

- NE software & data Mgt

- Flexible and evolving software and hardware architecture

Core Networks

- Provisioning functions

XMC Integrated Management Center


Date: Feb 2008

8/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 � NE software download and backup/restore

- Centralised for the whole network � Log management

- Centralized log browsing


Date: Feb 2008

9/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.... � Circuit domain U1x, U2, U3, … software releases (through OMC CS) as well as NGN net-

works: 5060 WCS, 1430uHSS, 7570MG, A8965 CDR, routers, … � GSM and CDMA domain through ISMC � UMA network

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 � Gateways: 7570 MGW, 7510 TGW; 7500ABN, Reefpoint security gateway, � 5920 PRBT


Date: Feb 2008

10/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


Date: Feb 2008

11/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 reac-tion time to anomalies. Alarm management is provided by a generic application: Alarm Surveillance (AS). AS provides all services related to the handling of alarms in a distributed TMN system:

o Current alarm management; o Alarm reporting and logging.


Date: Feb 2008

12/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 Acknowledgement state specifies whether any operator has seen the alarm. A current alarm can be acknowledged: � Manually by the operator; � Automatically according to a user-defined severity level.

o Cleared state indicates disappearance of a fault; the EML agent notifies alarm clearance. o Reservation state is the current alarm owned by any operator; operations on a reserved

alarm can only be performed by its owner. Current alarms are removed from the active list to the historical list in the following ways:

• Once cleared; • Manually, on operator request; • 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.


Date: Feb 2008

13/45


Current alarm information including alarm creation, change of alarm states and alarm deletion is dis-tributed through a well-defined open interface giving other TMN application easy access. Alarm synchronisation with EML agents is done:

o Manually on operator request; o Automatically in case of restarts of re-establishment of supervision link..

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, af-fected 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.

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 con-tains 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 histori-cal 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 cus-tomisation of display - and alarm criteria. On/Off Correlation, i.e. correlation of Alarms with their related Off–messages 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.


Date: Feb 2008

14/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, • Friendly name, • Type • Release • IP address • Supervision state • Acces Control Domain

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.


Date: Feb 2008

15/45


The current view (Figure 5: Topology management ) of the network is displayed via a tree. A “geo-graphical map view” is also available , included if needed a background picture(Figure 6: Map view ).

Figure 6: Map view


Date: Feb 2008

16/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 • Unacknowledged alarm synthesis - highest severity unacknowledged 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.


Date: Feb 2008

17/45


The network view is customisable by operator – that is, the view for a specified operator can be re-stricted to a subset of NEs, for example corresponding to a particular geographical region, using filter-ing facilities.


Date: Feb 2008

18/45


3.4 ACCESS MANAGEMENT

Centralised administration of access rights and user profiles helps to protect the system against inten-tional and unintentional damage. The Security Management component, abbreviated as SEC, focuses on the security aspects of the TMN system:

o Specify, store and distribute Access Control Information throughout the TMN system; o Profile the Graphical User Interface of the TMN system according to user access rights;

3.4.1 MAIN FUNCTIONALITIES Main functionality’s 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; � Limited number of unsuccessful login attempt (with user lock).

o User right management: � Functional right management through "on duty" and "off duty" period manage-

ment; � 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.

Default profiles include: Viewer, Network Operator, Administrator, SEC Administrator Access Control Information is stored in a central database and can be consulted through graphical user interface and UNIX configuration files. 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.

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


Date: Feb 2008

19/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 inher-ited 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 distrib-uted 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 operator’s 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


Date: Feb 2008

20/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 Alcatel-LucentAdmin : 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.


Date: Feb 2008

21/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 con-trol, hardware management, SS7management, performance management, log manage-ment, version change, applicative interfaces.

o Open CLI Session for A5020 WCS nodes: monitoring and provisionning domain or other CLI based nodes

o Launch immediate and differed script execution on a group of nodes of same type o Store results of script execution in results files o Handle script job state

3.8 NE SOFTWARE MANAGEMENT


Date: Feb 2008

22/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.

2. Download phase: this phase consists in downloading simultaneously the files into man-aged 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. Activation phase: this phase consists in the activation of the new software in the man-aged NEs.

4. Validation: this phase consists in the declaration of the new software as the default one in the managed NEs

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 installa-tion of the XMC.

o The backup can be scheduled or immediate and can be applied on one NE or a group of NEs.

o 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.

o The NE restore is performed from the XMC, via the Embedded EML. This is done node per node.

o 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.

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 "col-lection". 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 opera-tor terminal.


Date: Feb 2008

23/45


3.10 CONFIGURATION MANAGEMENT

This application is implemented at two different levels: t 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 t The second, at XMC level, which enables the provisioning at multiple NE level

o Multi NE scripting o 3GPP CM: basic in corba or bulk via XML data files for SS7 configuration o XML Soap for MGC30 provisionning. These features allow customers to develop dedicated provisioning procedures (tailored ser-vice)

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.

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.


Date: Feb 2008

24/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 particu-lar, 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) do-main, 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:

• Common Management EP IRP (Entry Point) CS IRP (Communication Surveillance) Notification IRP FT IRP (File Transfer) ( via ftp, sftp)

• Alarm Management Alarm IRP

• Configuration Management Kernel IRP 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 per-formance files are centralised in a single format (xml) and in a single point, but the CM domain is not


Date: Feb 2008

25/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 trans-late XMC/SOAP command from OSS to native Corba MML command. In XMC 7, this XMC/SOAP in-terface 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 re-cover following a major fault (disk crash, corrupted file system, etc)

t Data back up – the system is running but data has been lost or is corrupted 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 backups can be performed by functional domain (topology, performance, alarms, security, XMC configuration, operator’s configuration) t 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:

t Process supervision and (auto) restart t Disk space monitoring with possible threshold definition and alarm generation t Memory occupancy with possible threshold definition and alarm generation t CPU load t Hardware monitoring (disks, PSU, I/O cards)


Date: Feb 2008

26/45


t 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 administrator’s 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 Sub-scriber 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 sub-scriber is currently registered or not, and if yes, on which UNC.

3.15.2 RA/RNC MANAGEMENT


Date: Feb 2008

27/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 ac-cording 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 Au-dit.

• The OMC offers a synthetic view (Tree/Table) of the objects managed by the SGSN/DNS.


Date: Feb 2008

28/45


4 XMC OVERALL ARCHITECTURE

The XMC concept is based on a “portal” approach interfacing the existing OMCs and the new NE em-bedded element managers.

Figure 9: XMC Overall Architecture 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 • To preserve existing product look & feel • To de-couple XMC road maps for different network technologies • To guarantee the stability of the existing installed network and network manangement • To quickly integrate new type of equipment while offering integrated network supervision and unique interface to OSS. 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:

OMC CS, PS, CMC, ISMC, OMC-P

A L M A P

X.25 IP

Network Level

Management

Element Level

Management IP NE

Management Tomix ATCA

Management

• Management of both Circuit, Packet, UMA, @IMS domain

• Log management • Software Download and backup Restore • OMC Plateform auto surveillance • Geographical reduncandy

EML MSC HLR ...

MSC MSC HLR HLR ... ...

XMC

Spatial WEM client

Spatial

Santera MGW

Alcatel MGW

WEM

• Single Platform Login • Common Security Management • Common Performance Management • Common Alarm Management • Common Network Map • Seamless navigation • Northbound Interface


Date: Feb 2008

29/45


• Interoperability XMC provides standard 3GPP/CORBA/SNMP north interfaces for OSS access • 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)

Open architecture for other Alcatel-Lucent XMC The portal architecture is open and can be extended to other Alcatel-Lucent Network Manager to pro-vide unified network view and reduction of operator workplaces.

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/server-distributed architecture, the applications running on different servers. Operator workplaces (OWP) are PC’s. Prefered choice is XP, but Linux is also applicable. They can be local or remote from the Network Operation Center site.

Figure 10: XMC Network Architecture

NTP server (if any)

External storage

100 Base-T LAN

External OSS (if any) Additional NM eqts

OWPs System console

ENMS

NE net 1, ...

Printer Ethernet

Web Console

Bkp LAN 1GbE

NE sub net 2


Date: Feb 2008

30/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 provi-

sioned 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 • From 2 * 73Gb/140GB disks + external storage

• Existing “Legacy” configurations • RP5430, 5470 servers - from 2 to 4 CPUS

Configuration Server CPUs RAM (Gb)

Internal Mir-rored disks (Gb)

External Mir-rored disks (Gb)

Ethernet ports


Date: Feb 2008

31/45


ENMS_2 - legacy ENMS_2 (Unix) ENMS_2 (Linux) ENMS_4 – legacy ENMS_4(Unix) ENMS_4(Linux) ENMS_6(Unix) ENMS_4(Linux) ENMS_8 (Unix) ENMS_8(Linux)

rp5430 rp4440 dl580 rp5470 rp4440 dl580 rp4440 dl580 rp4440 dl580

2 2 2 4 4 4 6 6 8 8

6 6 6 12 12 12 14 14 18 18

2x36 2x144 2x144 2x36 2x144 2x144 2x144 2x144 2x144 2x144

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.

3 5 3 5 5 5

B2600 (Field Trial) C8000 (Field Trial) ML 350 G4 (Field Trial)

pa 8600 pa8800 proliant

1 2 2

2 2 2

1x 36 1*73 1*73

1x36 1 1

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

• 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

32/45


• Provides specific interface to the network specific IMs Each NE provides its Element Manager

• Accessed via web browser • Uploaded and run via JNLP (Java Network Launching protocol)

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 provid-ing the following advantages:

• Same ergonomics for all new generation OS • Easier integration between Alcatel-Lucent’s 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

Navigation Bus

CORBA Bus

CORBA Bus

Generic or network specific Information Managers(IM)

Network Element specific Communication Managers(IM)

Generic or network specific User Interfaces (USM)

NeNetworkElement

Managers


Date: Feb 2008

33/45


It also implements “state of the art” approach such as: • Java Web Start technology for the user interfaces • Full Java / Corba portable software • Clear internal interfaces enabling fast and easy introduction of new network elements • Distributed management: a “distributed architecture” is used where network element manage-

ment software and associated graphical user interface reside on the network element them-selves.

Figure 12: XMC Software Architecture

(Tomix based NEs: Ng HLR, IM HSS, WAS, SGSN…)

Perf mgt IM

Navigation Bus

Supervision IM

Software IM

Topology IM

Supervision USM

Software USM

Topology USM

Naming Service

3GPP Itf IM

3GPP North Interface

CORBA /XML

SNMP/FTP

Ne

Nw Perf Analysis

Notification Service

Tomix CM

SNMP CM

CORBA Bus

FTP/CORBA

IP node Tomix (*)

ASIM

GGSN

GGSN CM

CORBA Bus

AS USM

Network mgt IM

Other

OSS I/F

OMC PS,CS CMC,ISMC…

WSS CM

MSC Atrium

Network mgt USM

Network Element Managers

SNMP North Itf (Alarms)

SNMP Itf IM


Date: Feb 2008

34/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.

XMC server

Tomix NE

IIOP http/ SSL https

SNM PFTP

Operator Workplaces

IIOP / FTP

SNMP NE, iGGSN, Atrium

OMC-CS, OMC PS, CMC,

http SSH

IIOP HTTP X11

Legacy NEs

X25

External OSS IIOP/ FTP/SFTP/SNM P

Figure 13: Interface between XMC and NEs

5.1.1.1 INTERFACES CAPACITY AND BANDWIDTH


Date: Feb 2008

35/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 OmniS-witch 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 volt-

age breakdowns.


Date: Feb 2008

36/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 proce-dure with server provider. The XMC provides 99,995 high availability, in geographical redundancy, and 99,95 , in case of sim-plex 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 NE’s, resynchronization mechanisms allow to realign data between XMC and NE’s – 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


Date: Feb 2008

37/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 in-side a unique hardware box. Additional disks can also be added leading to a fully evolutive configura-tion. Because of the distributed architecture on the Element Management Layer, only single server con-figurations 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 2 5 25 50 100 150

5 ENMS1 ENMS1 ENMS1 NA NA NA25 ENMS2 ENMS2 ENMS2 NA NA NA50 NA ENMS2 ENMS2 ENMS4 NA NA

100 NA NA ENMS4 ENMS6 ENMS8 NA150 NA NA ENMS6 ENMS8 ENMS8 ENMS8

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, � One Switch Router Details information related to the HP servers are available on http://www.hp.com


Date: Feb 2008

38/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 Cabinet Height (mm) Cabinet Width (mm) CabinetDepth(mm) Weight of

equipped cabinet (kg)

XMC 1249.9 596.2 996,2 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)

41.228 Btu/hour

HP rp4400 server From 1400 to 4000 BTU (tbc)

HP DL 580 server Maximum: 5457 BTU

Disk Array 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 100–240VAC, 50/60Hz 1600 W HP DL 580 Proliant 100–240VAC, 50/60Hz 1566 W DDS4 LVD DAT 90–264 VAC, 50–60 Hz 137 W Internal Disk 100–240 VAC, 50–60 Hz 180 W External Disk Array 100–240 VAC, 50–60 Hz 650 W HP LaserJet Printer 220–240 VAC, 50–60 Hz 330 W OS6800-24 Ethernet switch (24 ports)

220–240 VAC, 50–60 Hz 12.5 watts

Environmental conditions and requirements The table below describes the environmental conditions of the Core Network OMC’s: HP 9000 servers

Electromagnetic Interference Complies with FCC Rules and Regulations, part 15, as a Class A digi-tal device. Manufacturer’s Declaration to EN55022 Level A, VCCI Reg-istered, Class I, Korea RLL

Operating Temperature 5º – 35ºC (41º – 95ºF) Non-Operating Temperature -40º – 70ºC (-40º – 158ºF) Maximum Rate of Temperature 10ºC/hour


Date: Feb 2008

39/45


Change Non-Operating Relative Humidity 15% to 90%, non-condensing Operating Altitude To 3.0km (10,000 ft) above sea level Non-Operating Altitude To 4.5km (15,000 ft) above sea level

OS6800-24 switch Temperature Operating Storage

0 to 40 C –20 to 70 C

Humidity Operating Storage

Operating relative humidity: 10 to 90% non-condensing Storage relative humidity: 10 to 95% non-condensing

Safety Compliance Canada CSA 60950, Germany TUV, GS Mark for Germany, Australia c-Tick for Australia, China CCC, CB Certification (per IEC 60950)

Cisco router Temperature Operating Non-operating

32 to 104°F (0 to 40°C) -13 to 158°F (-25 to 70°C)

Humidity 5 to 95% non-condensing Noise Level 38 dbA min./ 42 dbA max. Regulatory compliance FCC Part 15 Class B. For additional compliance informa-

tion, refer to the 2600 Series

DL580 servers RoHS

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 re-quirements of RoHS legislation. NOTE: Directive 2002/95/EC restricts the use of lead, mercury, cad-mium, 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.

Operating Temperature 50° to 95° F (10° to 35° C) Non-Operating Temperature -20° to 140° F (-29° to 60° C) Non-Operating Relative Humidity Relative Humidity (non-condensing) Operating 10% to 70%

5.6 DIAL-IN CAPABILITIES

Modem access to the XMC is not supported.


Date: Feb 2008

40/45


5.7 SERVICE RESTORATION TIMES

Operation time Switchover (synchronisation done )

5 min

Manual resynchronisation + switchover

15 min

Full start of XMC (including op-erating System)

20 min

Full Backup of XMC 55 min Full restore of XMC 55 min Full new installation of XMC ( including Operating System)

3,5 hours in HP UX 1.5 hours in Linux

Minor upgrade 30 minutes Table 3: Service Restoration Times

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 reinstalla-tion (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 configu-ration 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.


Date: Feb 2008

41/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 inter-faces.

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 pres-ence. In addition to the declaration/configuration, when the Qosac option is available, the commissioning of the network takes benefit from the Qosac predefined reports.


Date: Feb 2008

42/45


6 DOCUMENTATION

6.1 XMC DOCUMENTATION

XMC document collection , is composed of: Name Reference Comment Platform Administrator Guide

3BL65020FDAA This document describes the administrative tasks from the Alcatel-Lucent 1300 XMC Operation and Maintenance

Network Management 3BL65018FDAA This document describes the configuration tasks from the Alcatel-Lucent 1300 XMC Operation and Maintenance Center-Core Network

XMC Data Backup Man-agement

3BL77030FDAA This document describes the software management tasks from the Alcatel-Lucent 1300 XMC Operation and Maintenance Center-Core Network

Fault Management 3BL65017FDAA Description of the general principles for Fault Man-agement.

XMC SNMP Alarm For-warding

3BL59971FDAA Description of the SNMP north interface.

Performance Manage-ment

3BL65019FDAA This document describes how to manage perform-ance from an Alcatel-Lucent 1300 XMC. It also lists SNMP counters. This document applies beginning with Release 5.3

Alarm dictionaries 3BLxxx These documents lists all alarms for each managed network element, and corrective actions or proce-sures to be Applied

Counter lists 3BLxxx These documents lists all counters for each man-aged network element

Table 4: XMC Documentation

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.


Date: Feb 2008

43/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


Date: Feb 2008

44/45


7 GLOSSARY

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


Date: Feb 2008

45/45


TMN Telecommunication Management Network VLR Visited Location Register