OMC-H 7.3 R ELEASE NOTES SOFTWARE RELEASE NOTES FOR

LUCENT OMC-H R ELEASE 7.3

(I N SUPPORT OF USDS 6.0 SU3, USDS 6.0)

FILE: 06.cust_srn_omch_7.3.1.5 Page 1 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

TABLE OF CONTENTS

1. INTRODUCTION ...... 3 1.1 RELEASE INFORMATION ...... 3 1.2 RELEASE NOTES OVERVIEW ...... 4 2 SYSTEM REQUIREMENTS ...... 5 2.1 HARDWARE REQUIREMENTS ...... 5 2.2 SOFTWARE REQUIREMENTS ...... 5 2.3 PRE-INSTALLATION REQUIREMENTS ...... 5 3 RELEASE DESCRIPTION ...... 6 3.1 NEW FEATURES ...... 6 3.2 ENHANCEMENTS ...... 7 3.3 RESOLVED CUSTOMER PROBLEMS ...... 9 3.4 KNOWN ISSUES ...... 9 3.4.1 Known Product Issues ...... 9 3.4.2 Known User Documentation Issues ...... 10 3.4.3 Known Vendor Issues ...... 10 3.5 RESTRICTIONS AND SPECIAL CONSIDERATIONS ...... 11 4 NETWORK EQUIPMENT COMPATIBILITY ...... 12

5 DOCUMENTATION ...... 13

6 INSTALLING THE RELEASE/SERVICE PACK ...... 14 6.1 INSTRUCTIONS FOR INSTALLING SOFTWARE ...... 14 6.2 INSTRUCTIONS FOR INSTALLING / UNINSTALLING OS PATCHES ...... 14 6.3 RELEASE MIGRATION (IF APPLICABLE) ...... 15 7 SUPPORTING INFORMATION ...... 16 7.1 GLOSSARY – ACRONYMS AND DEFINITIONS ...... 16 7.2 REVISION ...... 16

FILE: 06.cust_srn_omch_7.3.1.5 Page 2 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

1. INTRODUCTION

1.1 RELEASE INFORMATION

Product Release: OMC-H 7.3 Load number: 01 Build number: 05 number: 08 Release Availability Date: Jan 15th, 2007

Comcode Description File Name Media

109640474 SW for OMCarchivev9.14 Tape the OMC-H Server for (cksum: 2102800973, size: Release R7.3 (In support 1003169801) of USDS6.0 SU3) sol5.9.iso Jump start 109640482 Application SW for OMC-H Main tar DVD- Server for Release R7.3 ROM OMC-H-7.3.1.5.tar (In support of USDS6.0 SU3) (cksum: 1907687980, size: 1047357440)

OMC-H Patch tar OMC-H-PATCH-7.3.1.5.8.tar (cksum: 4210289378, size: 19804160) Operating System Patch tar for Daylight Saving (DST) OMCarchive_Patch_05.tar (Cksum : 568847481, Size: 3 0397952) NOTE: This patch needs to be installed in single user mode. In order to this patch, please refer to section 6.2 Correlation rules package CAomch.tar.gz (cksum: 1929357928 , size: 8153 ) GNU Utilities for installing Sybase libiconv-1.8-sol9-sparc-local.gz (cksum: 2408791809, size: 2270983) tar-1.15.1-sol9-sparc-local.gz (cksum: 2507048253, size: 1475213)

FILE: 06.cust_srn_omch_7.3.1.5 Page 3 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

109640433 OMC-H Release R7.3 (In omch_r73_v1_helpfiles.tar CDROM support of USDS 6.0 SU3) (cksum: 1490628397, size: 33818624) On-Line User Documentation in English Language 109640342 OMC-H Release R7.3 (In 401-380-084R7.3-US.pdf US Letter support of USDS 6.0 SU3) Size

System Installation Paper Documentation in English Language on US Letter Size Paper 109640367 OMC-H Release R7.3 (In 401-380-075R7.3-US.pdf US Letter support of USDS 6.0 SU3) Size

System Administration Paper Documentation in English

Language on US Letter Paper

• value was obtained by running cksum in prompt

1.2 RELEASE NOTES OVERVIEW

This document corresponds to the OMC-H R7.3.

OMC-H R7.3 provides the complete configuration of SS7, SS7overIP and Diameter on USDS 6.0 SU3. OMC-H 7.3 also supports Data Grid and HCF with “Radius” protocol.

This Release Notes contains information on system requirements, resolved customer issues, known issues, network equipment compatibility, and installation instructions.

FILE: 06.cust_srn_omch_7.3.1.5 Page 4 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

2 SYSTEM REQUIREMENTS

2.1 HARDWARE REQUIREMENTS

Refer to the OMC-H System Installation guide (401-380-084R7.3).

2.2 SOFTWARE REQUIREMENTS

Refer to the OMC-H System Installation guide (401-380-084R7.3).

OMC-H 7.3 requires Solaris 2.9 or SunOS 5.9 operating system. The OS version with jumpstart CD –9.4 and OS archive 9.14 needs to be installed prior to installation of the OMC when installing the OMC-H 7.3 afresh.

If Alarm Correlation feature is required, need to install Sybase and activate the CA. For details refer to the OMC-H System Installation guide (401-380-084R7.3).

2.3 PRE-INSTALLATION REQUIREMENTS

Refer to OMC-H System Installation Guide (401-380-084R7.3).

FILE: 06.cust_srn_omch_7.3.1.5 Page 5 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

3 RELEASE DESCRIPTION

3.1 NEW FEATURES

OMC-H Release 7.3 is based on USDS 6.0 SU3 and supports the following new features, apart from the features supported in the previous releases.

1. Upgrade feature for OMC-H

OMC-H supports release upgrade from OMC-H 7.0 to OMC-H 7.3 for OMC-H application. It provides backward compatibility to USDS version 6.0 and upgrade to USDS version 6.0 SU3.

2. Data Grid

The Data Grid is a network element of MiLife Application Servers that provides a client application with a global view of all subscriber-related data, and a single access point to the global view from each of the Data Grid’s “serving data nodes”. For phase 1 only virtual view will be supported. Virtual views always access the data from the data source that masters the data. A Data Grid node consolidates subscriber information from all data sources that contain relevant information. With the global view constructed for all subscriber data, it can serve queries from applications, allowing application writers to access data from a single Data Grid node using a single protocol rather than multiple data sources using multiple protocols.

The Data Grid itself does not store any data. Instead, a virtual view of the global schema is presented to the client application. The Data Grid has configuration information that can map the global schema to a set of data sources. The data sources can be relational data sources or directory data sources. These data sources are considered golden sources of the data (up-to-date and the master source). The data sources can be co- resident or external to the MiLife Application Server. Co-resident data would be stored in one of the supported data repositories, namely TimesTen, Oracle, PostgreSQL, or Sun ONE Directory Server.

OMC-H supports Fault and performance management for Data grid network elements. It also supports all types of views viz. hardware, topological and topographical for DG NE. Alarm Correlation rules are also supported for DG NE.

3. AAA Radius HCF in OMC-H

USDS-AAA is composed of three components:

• Vital AAA server on CF to process AAA requests/responses. It provides protocol stacks for AAA and service logic.

• DAG on CF acting as data access gateway for AAA server to database

• HDF to manage and access USDS-AAA databases.

FILE: 06.cust_srn_omch_7.3.1.5 Page 6 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES To manage AAA services, the AAA servers located on the CFs need to be managed. The AAA server on CF is Vital AAA, a commercial AAA server in lucent product line. In USDS R6.0, Vital AAA is integrated into USDS architecture to provide AAA functionalities. Vital AAA provides a Service Management Tool (SMT) for managing and monitoring its AAA functionalities.

OMC-H supports part of management on USDS-AAA.

4. Support for SNMPv2 on NBI

The OMC-H SNMP NBI has been enhanced to include the provision of SNMP v2c. Now while creating NMSConnInfo object, if the protocol is SNMPv2, snmp security parameters are not applicable. But for both snmpV2 and V3 combination of IPAddress (NMS ip add) & User Name (omch identifier for the NMS) should be unique.

5. Site Name in Alarms for NBI

Alarms will contain additional information of Site name of the Network element.

3.2 ENHANCEMENTS

3.2.1 SS7 Synchronization with OMC-H

Earlier as part of SS7 synchronization with OMC, all the data on NE was deleted and then re-created. This is a performance impact if both CF and OMCH have same data except for few mismatches. Now for synching the OMCH data on HCF new strategy is adopted is Delta Forward Synchronization.

When the NE is freshly created in OMCH and SS7 master data is to be written onto this NE, all the existing data will be deleted (except mandatory ss7 information) and then the same will be populated from OMCH. Once successful synchronization is happened, any further forward synchronization will be differential synch.

In this mechanism, First NE data and OMCH data will be compared to the differences (Delta). Then only these differences between NE and OMCH will be corrected. All other objects remain untouched during the synch operation. Following 3 operations are performed on NE.

a. Deletion: Only objects, which are there on NE but not on OMCH, will be deleted.

b. Creation: Only objects, which are there on OMCH but not on NE, will be created.

c. Modification: Only objects, which have attribute, mismatch between OMCH and NE will be modified.

Advantages:

1. Numbers of SNMP set requests are minimized.

2. error prone because only objects having mismatch will be corrected and the others remain unaffected.

FILE: 06.cust_srn_omch_7.3.1.5 Page 7 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES 3.2.2 OMC-H auto starts as a part of system startup

OMC-H gets started as a part of system startup. The user can find the status of the OMC- H startup by performing the following steps –

b) Logon to OMC-H server as user “omcadm”

c) Execute “$COMMONPATH/pm/bin/state.sh”

o “ADM. STATE “TRANSIENT” indicates component is starting o “OPER. STATE “UP” indicates component is up. OR Launch the Process Monitor GUI as per the instructions provided in System administration guide (401-380-075R7.3) d) To find the percentage progress, check the “/omc/out/traces/omcstart.trace” file.

NOTE : In case the user requires disabling the auto start of the OMC H application as a part of system restart, then do the following:

o Logon to OMC-H server as user “root” o Comment the following line "om: 3:once: - omcadm -exec "omc start"" in /etc/inittab file. o Logout as an “root” user and login as “omcadm” user o Change “start.onboot=true” to “start.onboot=false” in the $COMMONPATH/pm/installation/appl1/data/config/app.properties

3.2.3 Diameter Synchronization with NE

After executing “Diameter Synchronization with NE” Action from OMC-H GUI or managing the Diameter NE (subsequent to first ), user can expect following behavior:

a) If Diameter Objects already exist in OMC-H with the same index and if there no change in the attribute value, then those object will not get deleted or changed.

In case of any change in values of the diameter objects those will get changed.

b) If the Diameter Objects exist on the NE but not in the OMC-H, those Objects will get created in OMC-H.

c) If Objects exist on the OMC-H but on the NE, those will get deleted.

3.2.4 HCF/HDF Synchronization

After executing “HCF/HDF Synchronization” Actions from OMC-H GUI, user can expect following behavior:

a) If Rack View objects already exist in OMC-H with the same index and if there no change in the attribute value, then those object will not get deleted or changed.

FILE: 06.cust_srn_omch_7.3.1.5 Page 8 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES In case of change in values of the objects those object will get changed.

b) If the objects exist on the NE but not in the OMC-H, those objects will get created in OMC-H.

c) If objects exist on the OMC-H but on the NE, those will get deleted from OMC-H.

3.2.5 Support for Virtual set

LinkSets & Combined LinkSets can be grouped into virtual link sets for load distribution.

3.3 RESOLVED CUSTOMER PROBLEMS

Defect Severity Abstract Release # Fixed 48312 - OMCH: A step needs to be added to Client_iEMS page 1-1526672 3: Medium to instruct users to turn off Proxy (KB) 7.3 [Cingilar - 1-1420029] Failed to install USCOUNTIES map for 1-1420029 3: Medium OMC-H 7.3 IR0 SCL - OMC-H System Access Logs - how to initiate a system access log 1-1456103 3: Medium 7.3 [SBC 1-1453805] IR0 SCL - OMC-HReport Manager, Alarms Record Report - Can't name report 1-1453805 3: Medium 7.3 IR0C2 – OMC-H HSS LINK Alarm Details Vague, no interface detail provided 1-1500701 4: Low 7.3 [SBC 1-1456103] IR0 SCL - OMC-H System Access Logs - how to initiate a system access log 1-1456103 3: Medium 7.3

3.4 KNOWN ISSUES

3.4.1 KNOWN PRODUCT ISSUES

# Description OMC-H impact Workaround

1 Get StatFiles On GetStatFilesOnAllNEs Steps: AllNEs scheduled scheduled action has been action has been executing infinitely. User 1) Login as unix “omcadm” user onto OMC- always executing would be unable to retrieve the H server (Sporadic). performance files from NE. 2) Run the command as shown below to get process id (PID) of the GetAllStats action $ /usr/ucb/ -auxww | -i "GetStatsClient" 3) $ –9 4) $ /export/home/omcadm/.ssh/known_host file

FILE: 06.cust_srn_omch_7.3.1.5 Page 9 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

5) Action would be scheduled again for next date and time.

2 Reflected HSA state is OMC-H Network Manager GUI It will get updated when new alarms come not updating newly shows Reflected HSA state as on the NE under a particular group. created groups & also an indeterminate. on ROOT group (OMC-H).

3.4.2 KNOWN USER DOCUMENTATION ISSUES

# Description OMC-H impact Workaround

1 The The ‘missingConnectivityData’ After all the nodes are grown in the ‘missingConnectivityD alarm on HDFs will not be complex, perform ‘HDF Synchronize’ action ata’ alarm on HDFs will auto-cleared when a CF is on all the HDFs. not be auto-cleared grown in the SDHLR complex when a CF is grown in and brought into ‘IS’ state. the SDHLR complex and brought into ‘IS’ This instruction is missing in state. the user-documentation 2 System Administration OMC-H doesn't provide the When backup is invoked from OMC-H GUI, Guide - Chapter 14 - provision to backup to a tape backup file gets created under Backups directly. folder/directory on OMC-H server. User has to manually run the unix command to transfer the backup to tape.

3.4.3 KNOWN VENDOR ISSUES

# Vendor Abstract Work Around

Sybase installation will Correlation Asset functionality fail if Unix hostname will not get activated as 1 Don’t put “-” in the unix name. contains “-” (Hyphen) Sybase installation will fail.

FILE: 06.cust_srn_omch_7.3.1.5 Page 10 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

Under remote Under remote authentication Navis server, change authentication mode, mode, even when the ReadLdap-CacheConnections = “TRUE” to 2 user is able to login password on Navis server ReadLdap-CacheConnections = “FALSE” with old password. changes, you may login to in the file OMC-H UNIX/GUI using the opt/NavisRadius/run/auth_methods original password. Only after using the new password login, (There will be two entries for the same the original password can be attribute in this file). After changing the invalid. value Navis application requires stop and start. This can be done as below

/opt/cso/server/bin/stop_all /opt/cso/server/bin/start_all

3 Increase in global It has been observed that if Its advisable to restart the OMC-H server memory usage during NESSUS scan software is run once NESSUS scan software is completed first run of NESSUS on OMC-H for first time global to get the memory released, if its observed scan software on memory gets increased and that memory usage on the system is OMC-H system does not get released. If any reaching high due to run of NESSUS scan. subsequent runs are done Reason for re-start is under the assumption there is no increase in the that this scanning would not be run in the memory usage is seen. This production but would be done in -labs of increase in memory does not customer before hand. impact any normal functionality of OMC-H and memory is released once the OMC-H server is re-started.

3.5 RESTRICTIONS AND SPECIAL CONSIDERATIONS

• Load profile and Save profile buttons should not be used when modifying the "NE Management" screen in the GUI

• The user shall not change the user labels of auto created objects and Groups like HDFPOOL

• After performing Upgrade/Downgrade Actions, Network manager GUI may become stale. Select Root Group from Network manager GUI and perform refresh action so that Network manager GUI will become active.

• After Upgrading all NEs in SDHLR complex “readhostentries” should be invoked on SDHLR complex to read the “msghost” and “etchost” entries. This is for getting latest entries from the NE in case of Node Growth.

• For Support of SS7 over IP feature, when performing Create/Delete/Modify operations from the OMC-H CLI for the following set of SS7/IP objects, the GDN specified should be of format “SS7=VneId, M3UA=0,ObjectName=[Object ID]”

o SCTPHostConfig o ASP o SGP o ApplicationServer

Example: for SGP object it should be of format 'SS7=VneId, M3UA=0,SGP =[1]'

FILE: 06.cust_srn_omch_7.3.1.5 Page 11 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES • The section 7-21 mentioned in the System Administration Guide (401-380-075R7.3) is changed as follows:

Monitor user sessions with logs

Security logs You may use security logs showing the following system access events to monitor user sessions and maintain system security: The below events are performed by the user logs in the system. The below log details can be viewed by selecting the corresponding row from Log Manager GUI and double clicking on the entry.

System Event Log Details Included Log in IP address and username Log out Username and status Modify allowed IP addresses IP address/sub-network and the operation requested (add or remove). and sub-networks list Change password User name and whether the action was forced or not forced. Authentication failed attempt Authentication failed attempt IP address and number of attempts; this event is listed if the maximum number of failed Authentication attempts have not yet been reached. Maximum number of IP address and the configured maximum number of authentication failed attempts Failed authentication attempts. reached Switch user state User name and operation requested – lock or Unlock; in remarks, if the action is lock, the reason is listed in the Remarks field (for example, if a user is locked because the authentication failure

4 NETWORK EQUIPMENT COMPATIBILITY

This release of the product is compatible with the following products and versions.

Product Version Comments Compatibility

USDS USDS 6.0 Refer to USDS 6.0 release notes document for the correct MAS and SPA versions of 6.0 release

USDS USDS 6.0 SU3 Refer to USDS 6.0 SU3 release notes document for the correct MAS and SPA versions of 6.0 SU3 release

FILE: 06.cust_srn_omch_7.3.1.5 Page 12 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

5 DOCUMENTATION

Following are the manuals that up the documentation set for OMC-H 7.3. They can be accessed from: https://infoproducts.lucent.com/aces/cgi- bin/dbaccessproddoc.cgi.edit?entryId=1-0000000001604&doctype=DOC

Guide Version Description No. Issue 1 Provides instructions for starting a Lucent OMC-H system after 401-380-084R7.3 it is delivered to a customer site for the first time. It also provides instructions for restoring the OS system and Lucent OMC-H System configuring peripheral devices, and describes optional Installation features.

401-380-078R7.3 Issue 1 Provides the configuration management concepts and tasks.

Lucent OMC-H Configuration Management 401-380-079R7.3 Issue 1 Provides information on how performance measurement result files are generated and collected. It also describes Lucent OMC-H Performance performance management administration. Management 401-380-077R7.3 Issue 1 Provides information and procedures required to manage the alarms viewed in the Lucent OMC-H 7.3 Lucent OMC-H Fault Management 401-380-082R7.3 Issue 1 Provides information on the graphical user interface features of the Lucent OMC-H 7.3 Client product. Lucent OMC-H Graphical User Interface 401-380-075R7.3 Issue 1 Provides information on how to perform system administration functions. Lucent OMC-H System Administration 401-380-083R7.3 Issue 1 Provides an overview of the Lucent OMC-H 7.3

Lucent OMC-H System Overview 401-382-210 Issue 2 Describe how to prepare for the on-site installation of Lucent Technologies OMC. Lucent OMC Site Preparation 401-380-818 Issue 3 Provide detailed instructions for installing a fully loaded Universal Network Cabinet (UNC) containing the Lucent OMC Lucent OMC Hardware system at a customer site. Installation 401-380-831R7.3 Issue 1 Provides information about the Common Object Request Broker Architecture - North Bound Interface (CORBA CORBA North Bound Interface NBI). 401-380-832R7.3 Issue 1 Provides information about the Simple Network Management Protocol - North Bound Interface (SNMP NBI). SNMP North Bound Interface 401-380-833R7.3 Issue 1 Provides information about the American Standard Code for Information Interchange based North Bound Interface ASCII North Bound Interface (ASCII NBI).

FILE: 06.cust_srn_omch_7.3.1.5 Page 13 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

6 INSTALLING THE RELEASE /S ERVICE PACK

This is a new release for USDS 6.0 SU3.

6.1 INSTRUCTIONS FOR INSTALLING SOFTWARE

For installation instructions, refer to the OMC-H System Installation guide (401-380-084R7.3).

For alarm correlation to work Sybase needs to be installed and the CA activated. For details refer to the OMC-H System Installation guide (401-380-084R7.3). The machine, on which the software is to be installed, should be configured with a fully qualified domain (host) name if CA needs to be installed. In such case machine needs to be configured for fully qualified domain name even before OMC-H installation is done. For details refer to the OMC-H System Installation guide (401-380-084R7.3).

For details on launching the client refer to the System Installation Guide (401-380-084R7.3).

For installing/uninstalling OMC-H application patch refer to the System Installation Guide (401-380-084R7.3).

6.2 INSTRUCTIONS FOR INSTALLING / UNINSTALLING OS PATCHES

For installing OS Patch tar “ OMCarchive_Patch_05.tar “ for Daylight Saving (DST) please do the following steps before referring to SIG guide as mentioned below:

1. Login as “ omcadm ” user in OMC-H

2. Stop the OMC-H using following command:

$ omc stop

3. Logout as an “ omcadm ” user and login as “ root ” user

4. Copy OMCarchive_Patch_05.tar to the /maint

Note : Please make sure there is only t his tar in /maint directory.

5. Initialize the machine into single user mode using the following command:

# init s

6. Use the console of OMC-H server to apply the “ OMCarchive_Patch_05.tar ”.

Execute the following commands to extract and apply_os_patch.sh script :

#cd /maint #tar -xvf OMCarchive_Patch_05.tar -c apply_os_patch.sh # ./apply_os_patch.sh

FILE: 06.cust_srn_omch_7.3.1.5 Page 14 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

7. Reboot the machine using the following command:

# –y –g 0 –i6

For Uninstalling OS patches, refer to the OMC-H System Installation guide (401-380- 084R7.3).

6.3 RELEASE MIGRATION (IF APPLICABLE)

OMC-H 7.3 Load 1 supports migration from the following base loads of OMC-H 7.0

• OMC-H 7.0 (OMC-H 7.0 GA load with Patch 13) to OMC-H 7.3

Note: Patch 8 was delivered as a part of OMC-H 7.0 GA delivery

Please refer to the System installation document (401-380-084R7.3) for details on the migration steps.

FILE: 06.cust_srn_omch_7.3.1.5 Page 15 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

7 SUPPORTING INFORMATION

7.1 GLOSSARY – ACRONYMS AND DEFINITIONS

AAA – Authentication, Authorization, Accounting

DAG - Data Access Gateway

DG – Data Grid

GUI – Graphical User Interface

HCF – Home Location Register Control Function

HDF – Home Location Register Data Function

HLR - Home Location Register

HSS - Home Subscriber Server

MAS – MiLife Application Server

NE - Network Element

CA - Correlation Asset

OAM - Operations, Administration & Maintenance

OMC-H- Operations and Maintenance Centre for HLR and HSS.

SDHLR - Super Distributed Home Location Register

SMT - Service Management Tool

UMTS - Universal Mobile Telecommunication System

USDS – Unified Subscriber Data Server

CLI – Command Line Interface

7.2 REVISION HISTORY

Date Issue Change Description By 2007-01-04 0.1 Draft release notes OMC-H team

FILE: 06.cust_srn_omch_7.3.1.5 Page 16 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined OMC-H 7.3 R ELEASE NOTES

Date Issue Change Description By 2007-01-09 0.2 Updated with review comments OMC-H team 2007-01-12 1.0 Base line the release notes OMC-H team

FILE: 06.cust_srn_omch_7.3.1.5 Page 17 of 17 Issue 1.0 Dated 2007-01-12 Alcatel-Lucent Proprietary Base lined