OMC-H 7.5 RELEASE NOTES SOFTWARE RELEASE NOTES FOR

ALCATEL -LUCENT OMC-H RELEASE 7.5

(I N SUPPORT OF USDS 7.1)

FILE:05.cust_srn_omch_7.5.1.6.doc Page 1 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES

TABLE OF CONTENTS

CHAPTER 1 INTRODUCTION ...... 3

1.1 RELEASE INFORMATION ...... 3 1.2 RELEASE NOTES OVERVIEW ...... 4 2 SYSTEM REQUIREMENTS ...... 4

2.1 HARDWARE REQUIREMENTS ...... 4 2.2 SOFTWARE REQUIREMENTS ...... 4 2.3 PRE -INSTALLATION REQUIREMENTS ...... 5 3 RELEASE DESCRIPTION ...... 5 3.1 NEW FEATURES ...... 5 3.1.1 OMC-H SW ADMINISTRATION PHASE 1 ...... 5 3.1.2 OMC-H Enhanced Log Aggregation Feature ...... 5 3.1.3 OMC-H Support for Unique Alarm Code ...... 5 3.1.4 OMC-H EMF 5.0 MIGRATION ...... 6 3.2 ENHANCEMENTS ...... 6 3.2.1 SS7 Synchronization with OMC ...... 6 3.2.2 OMC-H Application License validator ...... 6 3.3 RESOLVED CUSTOMER PROBLEMS ...... 7 3.4 KNOWN ISSUES ...... 7 3.4.1 Known Product Issues ...... 7 3.4.2 Known Vendor Issues ...... 7 3.5 RESTRICTIONS AND SPECIAL CONSIDERATIONS ...... 8 4 NETWORK EQUIPMENT COMPATIBILITY ...... 9

5 DOCUMENTATION ...... 9

6 INSTALLING THE RELEASE/SERVICE PACK ...... 10

6.1 INSTRUCTIONS FOR INSTALLING SOFTWARE ...... 10 6.2 RELEASE MIGRATION (IF APPLICABLE )...... 11 7 SUPPORTING INFORMATION ...... 11

7.1 GLOSSARY - ACRONYMS AND DEFINITIONS ...... 11 7.2 REVISION ...... 12

FILE:05.cust_srn_omch_7.5.1.6.doc Page 2 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES

Chapter 1 INTRODUCTION

1.1 Release Information

Product Release: OMC-H 7.5 Load 1 Build 6 9 Release Availability Date: July 30 th , 2007

Comcode Description File Name Media

109657478 SW for the OMCarchivev10.2 Tape OMC-H Server for Release (cksum: 1597262044, size: R7.5 (In support of USDS7.1) 1746293959)

sol5.10.iso Jump start (cksum: 1474125923, size: 690073600)

109657486 Application SW for OMC-H Main tar DVD Server for Release R7.5 (In ROM OMC-H-7.5.1.6.tar support of USDS7.1) cksum: 3743575638

size: 1140441088 OMC-H Patch tar OMC-H-PATCH-7.5.1.6.9.tar cksum: 3668197040 size: 119644160 GNU Utilities for installing Sybase libgcc-3.4.6-sol10-sparc-local.gz cksum: 265816990 size: 527922 libiconv-1.11-sol10-sparc-local.gz cksum: 1363373264 size: 1464363 tar-1.16-sol10-sparc-local.gz cksum: 3408792613 size: 978987

FILE:05.cust_srn_omch_7.5.1.6.doc Page 3 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES

Correlation rules package CAomch.tar.gz cksum: 2262387408 size: 8707

109657387 OMC-H Release R7.5 (In omch_r75_v1_helpfiles.tar CD ROM support of USDS 7.1) On-Line cksum: 3777778412 User Documentation in English Language on CDROM size: 28669952 109657288 OMC-H Release R7.5 (In 401-380-084R7.5-US.pdf US Letter support of USDS 7.1) System Size Paper Refer to section 5 Installation Documentation in English Language on US Letter Size Paper 109657304 OMC-H Release R7.5 (In 401-380-075R7.5-US.pdf US Letter support of USDS 7.1) System Size Paper Refer to section 5 Administration Documentation in English Language on US Letter Size Paper

value was obtained by running cksum in prompt

1.2 Release Notes Overview

This document corresponds to the OMC-H R7.5. OMC-H R7.5 provides the complete configuration of SS7 and Diameter on MAS R26SU6 and USDS 7.1.

This release notes contain information on system requirements, resolved customer issues, known issues, network equipment compatibility, and installation instructions.

2 SYSTEM REQUIREMENTS

2.1 Hardware Requirements

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

2.2 Software Requirements

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

OMC-H 7.5 requires Solaris 2.10 or SunOS 5.10 operating system. The OS version with jumpstart CD –10.1 and OS archive 10.2 needs to be installed prior to installation of the OMC when installing the OMC-H 7.5 application.

FILE:05.cust_srn_omch_7.5.1.6.doc Page 4 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES

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

2.3 Pre-Installation Requirements

Refer to OMC-H System Installation Guide (401-380-084R7.5) [5]

3 RELEASE DESCRIPTION

3.1 New Features

OMC-H Release 7.5 is based on USDS 7.1/MAS R26SU6 and supports the following new features apart from the features supported in the previous releases.

3.1.1 OMC-H SW ADMINISTRATION PHASE 1

This feature deals with the management of software files that can be downloaded to the NE’s and to manage and display the software information on NE under the span of control of the OMC-H.

OMC-H is a central place for network management for USDS and HSS network elements will act as the software distributor to download the USDS software. OMC-H will download software required for USDS application. OMC-H will manage the information of USDS software downloaded to or running on USDS NEs.

The software administration phase 1 will support download of USDS software packages and patches only.

3.1.2 OMC-H ENHANCED LOG AGGREGATION FEATURE

This feature is enhancement on existing Log Aggregation feature. OMC-H pulls the logs (OMlog, debuglog and subscriber trace) from NE when OMC-H gets notification from NE. OMC-H will also support on demand log retrieval and aggregation. Using this feature OMC-H will do post-processing of the logs to provide specific information, such as log for a subscriber, for a specific timeframe, etc. The file name and number are configurable for OMlog and debuglog. Now the customers can use filenames other than OMlog0 and OMlog1 or debuglog0 and debuglog1 for OMlogs and debuglogs. OMC-H will utilize the zone information from NE to aggregate the logs from NEs with different time zones. OMC-H will support sorting of aggregated files per NE hostname or date and time.

3.1.3 OMC-H SUPPORT FOR UNIQUE ALARM CODE

OMC-H will display a unique alarm code in the Fault field for every OMC-H internal alarm, EMF alarm, USDS alarm and MAS alarm. Upon receiving alarm from NE (USDS and MAS), the unique alarm code includes in new field provided by USDS

FILE:05.cust_srn_omch_7.5.1.6.doc Page 5 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES and MAS will be populated to the Fault type. The OMC-H Fault Management CORBA and SNMP interface to the north bound system will include the unique alarm code in the Additional Information field when the alarm is forwarded to north bound.

3.1.4 OMC-H EMF 5.0 MIGRATION

OMC-H 7.5 is based on EMF 5.0 platform. Besides Security hardening there are usability enhancements in the areas of Configuration Management, Fault Management, CLI and other general usability enhancements in EMF 5.0.

3.2 Enhancements

3.2.1 SS7 SYNCHRONIZATION WITH OMC

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 which is Delta SS7 Synchronization . This enhancement is available from OMC-H 7.3 onwards.

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

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

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

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

Advantages:

1. Significant reduction in time taken for synchronization because the number of SNMP set requests are minimized

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

3.2.2 OMC-H APPLICATION LICENSE VALIDATOR

OMC-H will validate the OMC-H application license while starting and throw appropriate error message on console if the license is invalid.

FILE:05.cust_srn_omch_7.5.1.6.doc Page 6 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES 3.3 Resolved Customer Problems

Defect Severity Abstract Release # Fixed

1-1589097 3: Medium bulk_ftp.sh script fails due to incorrect 7.5 login/ in /SA/data/fp1/evcor/srcdata/sticomch/params file 1-1573177 3: Medium OMCH: Scripts used for upgrade should not 7.5 execute .profile 1-1456103 3: Medium [SBC 1-1456103] IR0 SCL - OMC-H System 7.5 Access Logs - how to initiate a system access log 1-1451815 3: Medium Ir0 SCL - OMC-H User Initiated Password 7.5 Change

3.4 Known Issues

3.4.1 KNOWN PRODUCT ISSUES

# Description OMC-H impact Workaround

1 Import is not This issue is sporadic The user should download the software completing/failing and occurs when from LED to any FTP server and then even after 4 hours importing files from LED. import the software from FTP server to It usually fails when the OMC-H.

file size is than 60 MB. The problem occurs because LED uses older version of SFTP and an AR 1-1655246 is opened against LED for this issue. 2 NE software details The Download status for The same status can be viewed from window does not the NE is always shown Software Admin window-> View -> reflect download as “Not available” even Download Status -> By NE name. status after download is completed.

3.4.2 KNOWN VENDOR ISSUES

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

FILE:05.cust_srn_omch_7.5.1.6.doc Page 7 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES

3 Increase in global memory It has been observed that if Its advisable to restart the usage during first run of NESSUS scan software is run OMC-H server once NESSUS NESSUS scan software on on OMC-H for first time scan software is completed OMC-H system global memory gets to get the memory released, increased and does not get if its observed that memory released. If any subsequent usage on the system is runs are done there is no reaching high due to run of increase in the memory NESSUS scan. Reason for re- usage is seen. This increase start is under the assumption in memory does not impact that this scanning would not any normal functionality of be run in the production but OMC-H and memory is would be done in -labs of released once the OMC-H customer before hand. server is re-started. 3 If the user tries to open This issue is seen only if the Click on ‘Refresh’ in the any Report (like Audit default page of IE 6 browser browser and the report can report) or PM file from is set to ‘blank’. This issue is be viewed. OMC-H using IE 6.0 SP2 observed in IE 6.0 SP2 but browser, the it throws a works fine with IE 7.0 error message “Access is denied. Error processing resource 'https://:12000/reportsWeb/def ault.xsl'.

3.5 Restrictions and Special Considerations

 The ‘Add Note’ action on the VNE is not of importance because the user will not be able to view the notes for VNE. Hence the user need not invoke the action ‘Add Note’ on a VNE.

 Alarm Synchronization will not work for Medium and High Security settings when the same snmp user name is added to different NE's with different authorization protocol. Alarm Synchronization will not work for the second NE in such a scenario. The user should use different snmp usernames across the NE’s or if the snmp username used is same for all NE’s, then the authorization protocol also should be same for all NE’s.

 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

 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,

- SCTPHostConfig

- ASP

- SGP

FILE:05.cust_srn_omch_7.5.1.6.doc Page 8 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES - ApplicationServer

, the GDN specified should be of format “SS7=VneId,M3UA=0,ObjectName=[Object ID]”

For e.g for SGP object it should be of format 'SS7=VneId,M3UA=0,SGP =[1]'

The same instruction applies to Common OAM objects,

- MsgDestination

- Msgclass

4 NETWORK EQUIPMENT COMPATIBILITY

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

Product Version Comments Compatibility

USDS USDS 7.1/MAS R26SU6

5 DOCUMENTATION

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

FILE:05.cust_srn_omch_7.5.1.6.doc Page 9 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES

Guide Version Description No. Provides instructions for installing and starting Alcatel- 401-380-084R7.5 1.0 Lucent OMC-H system. Alcatel-Lucent OMC-H System Installation

401-380-078R7.5 1.0 Provides the configuration management concepts and tasks. Alcatel-Lucent OMC-H Configuration Management

401-380-079R7.5 1.0 Provides information on how performance measurement result files are generated and collected. It also describes Alcatel-Lucent OMC-H performance management administration. Performance Management

401-380-077R7.5 1.0 Provides information and procedures required to manage the alarms viewed in the Alcatel-Lucent OMC-H 7.5 Alcatel-Lucent OMC-H Fault Management

401-380-080R7.5 1.0 Provides detailed information about each object exposed by the Alcatel-Lucent OMC-H 7.5 Alcatel-Lucent OMC-H Managed Object Descriptions

401-380-082R7.5 1.0 Provides information on the graphical user interface features of the Alcatel-Lucent OMC-H 7.5 Client product. Alcatel-Lucent OMC-H Graphical User Interface

401-380-075R7.5 1.0 Provides information on how to perform system administration functions. Alcatel-Lucent OMC-H System Administration

401-380-083R7.5 1.0 Provides an overview of the Alcatel-Lucent OMC-H 7.5

Alcatel-Lucent OMC-H System Overview

401-380-831R7.5 1.0 Provides information about the Common Object Request Broker Architecture - North Bound Interface CORBA North Bound Interface (CORBA NBI).

401-380-832R7.5 1.0 Provides information about the Simple Network Management Protocol - North Bound Interface (SNMP SNMP North Bound Interface NBI). 401-380-833R7.5 1.0 Provides information about the American Standard Code for Information Interchange based North Bound ASCII North Bound Interface Interface (ASCII NBI).

6 INSTALLING THE RELEASE /S ERVICE PACK

This is a new release for USDS 7.1.

6.1 Instructions for Installing Software

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

During Operating System installation, ignore the following error messages:

FILE:05.cust_srn_omch_7.5.1.6.doc Page 10 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES ======System identification is completed. Jun 12 16:00:05 svc.startd[7]: svc:/platform/sun4u/sf880drd:default: Method "/lib/svc/method/sf880dr" failed with s tatus 96. [ platform/sun4u/sf880drd:default misconfigured (see 'svcs -x' for details) ] ======

Installation continuing...... Extracting Files...... Sun Microsystems Inc. SunOS 5.10 Generic January 2005 Can't open /etc/default/ ======

6.2 Release Migration (if applicable)

NA

7 SUPPORTING INFORMATION

7.1 Glossary- Acronyms and Definitions

GUI – Graphical User Interface

HCF – Home Location Register Control Function

HDF – Home Location Register Data Function

DG – Data Grid

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

UMTS - Universal Mobile Telecommunication System

USDS – Unified Subscriber Data Server

FILE:05.cust_srn_omch_7.5.1.6.doc Page 11 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined OMC-H 7.5 RELEASE NOTES CLI – Command Line Interface

7.2 Revision History

Date Issue Change Description By 2007-07-25 0.1 Draft release notes Kmanoj 2007-07-27 0.2 Comments incorporated Kmanoj 2007-07-30 1.0 Baselined Kmanoj

FILE:05.cust_srn_omch_7.5.1.6.doc Page 12 of 12 Issue 1.0 Dated 2007-07-30 Alcatel-Lucent Proprietary Baselined