OMC-P Software Release Notice Release 10.0.0 · OMC-P Software Release Notice Release 10.0.0.1 ... 1.5.3 Oracle database requirements ... OMC-P RELEASE 10.0.0.1 4

OMC-P Software Release Notice Release 10.0.0.1

255-400-402R10.0.0.1 Issue 6 14 December 2006

RELEASE CONTENT DESCRIPTION OMC-P RELEASE 10.0.0.1

2 Alcatel-Lucent – Proprietary

See Notice on Page 2 255-400-402R10.0.0.1

Issue 5, December 2006

Copyright © 2006 by Alcatel-Lucent. All Rights Reserved.

This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced, distributed, or altered in any fashion by any entity (either internal or external to Alcatel-Lucent), except in accordance with applicable agreements, contracts or licensing, without the express written consent of the Lucent Session Manager (Lucent SM) Product Management Team and the business management owner of the material.

About Alcatel-Lucent

Alcatel-Lucent, with US headquarters in Murray Hill, N.J., USA, designs and delivers networks for the world’s largest communications service providers. Backed by Bell Labs research and development, Lucent relies on its strengths in mobility, optical, data and voice networking technologies as well as software and services to develop next-generation networks. The company’s systems, services and software are designed to help customers quickly deploy and better manage their networks and create new revenue-generating services that help businesses and consumers. For more information on , visit its web site at http://www.alcatel-lucent.com.

Notice

At the time of publication, this document reflects the latest information on the OMC-P Element Management System offering. However, as we are continually enhancing our products and solutions, we recommend that 6 months after the date of publication you obtain the latest version of this document from your Alcatel-Lucent representative.

Trademarks

Not applicable.





CONTENTS

1 OVERVIEW .................................................................................................................................... 5 1.1 INTRODUCTION .......................................................................................................................... 5

1.1.1 Overview .......................................................................................................................... 5 1.1.2 Release Notes Issue........................................................................................................ 5

1.2 SOFTWARE RELEASE OVERVIEW................................................................................................. 6 1.3 CUSTOMER DOCUMENTATION ..................................................................................................... 8 1.4 MANAGEABLE SWITCHES AND APPLICATIONS ............................................................................... 9

1.4.1 Supported Lucent Gateway Platform switch configurations ............................................ 9 1.4.2 Supported Lucent Gateway Platform switch software releases ...................................... 9 1.4.3 Supported Feature Server 5000 switch software releases............................................ 10 1.4.4 Supported Lucent Session Manager software releases ................................................ 10 1.4.5 Supported Lucent Communication Manager software releases.................................... 10

1.5 SYSTEM REQUIREMENTS.......................................................................................................... 11 1.5.1 Server requirements ...................................................................................................... 11 1.5.2 Solaris version and patch requirements ........................................................................ 11 1.5.3 Oracle database requirements..................................................................................... 11 1.5.4 Java JDK requirements.................................................................................................. 11 1.5.5 Client requirements........................................................................................................ 11

1.6 INSTALLATION AND START-UP PROCEDURES.............................................................................. 12 1.7 RESTRICTIONS AND SPECIAL CONSIDERATIONS ......................................................................... 12

1.7.1 Supported products and releases.................................................................................. 12 1.7.2 OMC-P server startup time ............................................................................................ 12 1.7.3 Security events .............................................................................................................. 12 1.7.4 Default system logins..................................................................................................... 12 1.7.5 User activity audit logs ................................................................................................... 13 1.7.6 International echo control variant type........................................................................... 13

2 NEW FEATURES/FUNCTIONS................................................................................................... 13 2.1 NEW FEATURES....................................................................................................................... 13 2.2 TL1 COMMAND TO OMC-P SCREEN MATRIX ............................................................................. 14 2.3 CONFIGURABLE PROPERTIES.................................................................................................... 17

2.3.1 New plexview.properties template properties................................................................ 17 2.3.2 New plexcore.properties template properties ................................................................ 19

2.4 NAL (NODE ACCESS LIST) CHANGES ....................................................................................... 19 3 ADVANCED REPORTING SOFTWARE RELEASE................................................................... 20

3.1 ADVANCED REPORTING SYSTEM WITH OR WITHOUT ADVANCED TRAFFIC COLLECTION................ 20 3.2 LICENSE KEYS ......................................................................................................................... 20 3.3 ADVANCED REPORTING SYSTEM REQUIREMENTS ...................................................................... 20

3.3.1 EMS Server with Advanced Reporting workstation requirements................................. 20 3.3.2 Advanced Traffic Collector workstation requirements ................................................... 20 3.3.3 Business Objects PC requirements ............................................................................... 22

3.4 VALIDATED SUPPORTED SWITCH RELEASES............................................................................... 22 3.5 WEBINTELLIGENCE PATCH ....................................................................................................... 22 3.6 ADVANCED REPORTING SYSTEM FIXED AND KNOWN ANOMALIES ................................................ 22

4 EXCEPTIONS AND WORKAROUNDS....................................................................................... 23 4.1 EXCEPTIONS ........................................................................................................................... 23 23

23

222222222020202020

20

191917171413

13

131312121212121211111111111110101099986555

5





4.1.1 OMC-P managing Lucent Gateway Platform switches fixed anomalies ....................... 23 4.1.2 OMC-P Advanced Reporting System fixed anomalies .................................................. 27 4.1.3 OMC-P managing Feature Server 5000 and Lucent Communication Manager fixed anomalies ..................................................................................................................................... 28

4.2 WORKAROUNDS ...................................................................................................................... 28 4.2.1 OMC-P managing Lucent Gateway Platform switches known anomalies..................... 28 4.2.2 OMC-P Advanced Reporting System known anomalies ............................................... 29 4.2.3 OMC-P managing Feature Server 5000 and Lucent Communication Manager known anomalies ..................................................................................................................................... 29

29

29282828

2723





1 OVERVIEW

1.1 Introduction

1.1.1 Overview This release of OMC-P software consists of the following software packages:

• PlexView Client Release, Version 10.0.0.1

• PlexView Server Release, Version 10.0.0.1

The detailed content can be found in Section 1.5, “Full List of New Features/Functions”, of this document.

1.1.2 Release Notes Issue

Issue Date Purpose

1.0 20-July-2006 Preliminary Release Notice for the controlled introduction (CI) delivery of 10.0.0.0.

2.0 11-Sept-2006 Release Notice for the general availability (GA) delivery of 10.0.0.0

3.0 15-Sept-2006 Release Notice for the general availability (GA) delivery of 10.0.0.0 with updated list of exceptions and workarounds.

4.0 10 Oct-2006 Correct required Solaris and supplied Oracle version.

5.0 13 Dec-2007 Updated to correct issue with GR reporting and reissued as 10.0.0.1.

6.0 14 Dec 2007 Updated to correct issue with GR

This software release notice for version 10.0.0.0 of the OMC-P (formerly titled the Lucent Control and Gateway Platform (PlexView®) Element Management System (EMS)) software describes the system architecture and features provided by this product.

This SRN provides software release notice information for the OMC-P Element Management System managing the Feature Server 5000 on the Lucent Control Platform, the Lucent Communications Manager on a Sun Fire server platform and all Lucent Gateway Platform applications.

All Lucent Gateway Platform provisioning sections are documented in the OMC-P for Lucent Gateway Platform Management Reference Guide and the OMC-P Lucent Gateway Platform Management User Guide. For Lucent Control Platform applications, the Feature Server 5000 has its own User Guide and the Lucent Communication Manager has its own user guide. Consult the Reference Documentation section in this document for further details.





The terms OMC-P, EMS, and PlexView are used interchangeably throughout this document and all references refer to the OMC-P Element Management System.

OMC-P software allows you to perform element and network management functions on your Lucent Gateway Platform Switches and LCP (Lucent Control Platform) and cLCP (compact Lucent Control Platform) network elements configured with the Feature Server 5000 application. The Lucent Communication Manager (LCM) application, running on a server, provides a web portal for subscriber applications on the Feature Server 5000. This EMS software provides the functionality to configure, monitor, and manage faults on multiple network elements on multiple platforms simultaneously.

This software release notice (SRN) contains important release-specific information that is not available elsewhere. The section titled, Restrictions and Special Considerations and the section titled, Known and Fixed Anomalies both describe issues discovered during the development and testing of this software release that you need to be aware of.

1.2 Software release overview The following list shows the release numbers and names of the software packages that make up the OMC-P software suite, the optional Web API, the optional Advanced Reporting Universe, the optional Advanced Reporting System (ARS) and the optional Advanced Traffic Collector (ATC)

The server and directory path to obtain the software is listed in 255-400-401 the Lucent Control and Gateway Platform Element Management System (PlexView) Installation Guide.

Important ! You must use the provided instance of Oracle or your support agreement will not apply.

Software Software Package

Release Number

Filenames

Oracle 8.1.7.4 /release/em/ECO/oracle/09_08_00_00/cdrom_db_8174.tar

Server 10.0.0.1 /release/em/ECO/10_00_00_01/Server/Server.bin

Client 10.0.0.1 /release/em/ECO/10_00_00_01/Client/Client.bin (Sun) or Client.exe (Windows)

Web API 10.0.0.0 /release/em/ECO/10_00_00_00/WebApi/WebApi.bin

AR Universe

10.0.0.0 /release/em/ECO/10_00_00_00/universe/PlexView.unv

ARS Server

10.0.0.0 /release/em/ECO/10_00_00_00/webi/webi* and uninst-webi.sh

ARS Client

10.0.0.0 /release/em/ECO/ARS/518/*.zip





ATC 10.0.0.0 /release/em/ECO/10_00_00_00/ATC/Stats.bin





1.3 Customer documentation The following list describes the available customer documentation related to this release:

Doc # Title

255-400-400 OMC-P for Lucent Gateway Platform Management Reference Guide Part Number 255-400-400R9.11.0.0

255-400-401 Lucent Control and Gateway Platform Element Management System (PlexView EMS) Installation Guide for the Lucent Gateway Platform Part Number 255-400-401R9.11.0.0.

255-400-418 OMC-P Lucent Gateway Platform Management User Guide Part Number 25504990499R10.0.0.0

255-400-420 OMC-P for Lucent Feature Server 5000 Management User Guide Part Number 255-400-420R10.0.0.0

255-400-421 OMC-P for the Lucent Communication Manager User Guide Part Number 255-400-421R10.0.0.0.

255-400-200 Lucent Gateway Platform Advanced Traffic Collection for the Advanced Reporting System User Guide Part Number 255-400-200R9.7.0.0

255-400-201 Lucent Gateway Platform Advanced Reporting System Installation & Setup Guide Part Number 255-400-201R9.11.0.0

255-400-202 Lucent Gateway Platform Advanced Traffic Collection for the Advanced Reporting System Installation & Setup Guide Part Number 255-400-202R9.11.0.0

255-400-205 Lucent Gateway Platform Advanced Reporting System Master Checklist – Part Number 255-400-205





1.4 Manageable switches and applications This version of EMS software can manage a network of many Lucent Control Platform and Gateway Platform network elements with many simultaneously connected clients. All supported network element applications can all be managed from a single EMS Server.

1.4.1 Supported Lucent Gateway Platform switch configurations Lucent Gateway Platform switch configuration that can be managed by this software release include:

• Lucent Compact Switch (SG-MGC-MG)

• Lucent Compact Controller (SG-MGC)

• Lucent Signaling Gateway (SG)

• PSG: Default �ignalling gateway

• ISG: Improved Signaling Gateway

• DSG: Distributed Signaling Gateway

• Lucent Network Controller (MGC)

• Lucent Network Gateway (MG)

• PG : Default Plexus Media Gateway

• TDMIP : Determines whether AMR/AAL2 will be enabled. Currently AMR cannot be intermixed with TDP to VOIP.

• UMTS: Universal Mobile Telecommunications System

The platform switch configurations available for use depend on the switch software release on the switch. Not all listed applications work with all releases of switch software.

1.4.2 Supported Lucent Gateway Platform switch software releases This version of EMS software has been validated against and only supports Lucent Gateway Platform Switches running switch releases:

6.2.0.2

6.2.0.1

6.1.1.2

5.3.0.6

5.1.2.3

5.1.0.3

3.13.01

of switch software. This release of EMS software may not manage switches running other versions of switch software correctly. For switches running software revisions from earlier than 3.10, contact Lucent Worldwide Services for further support information.





1.4.3 Supported Feature Server 5000 switch software releases Lucent Control Platform network element applications working on the LCP and cLCP hardware platforms that can be managed by this OMC-P software release include the Lucent Feature Server 5000 releases:

• FS5000 R1.0

• FS5000 R1.1

• FS5000 R2.0

• FS5000 R2.1

1.4.4 Supported Lucent Session Manager software releases Lucent Session Manager network element applications working on the LCP and cLCP hardware platforms that can be managed by this OMC-P software release include the following Lucent Session Manager releases:

• SM 3.1

• SM 4.0

• SM 4.1

1.4.5 Supported Lucent Communication Manager software releases The Lucent Communication Manager (LCM) application, running on a Sun Fire server, provides a web portal for subscriber applications on the Feature Server 5000. Lucent Communications Manager releases that can be managed by this OMC-P software release include the following Lucent Session Manager releases:

• LCM 6.1.1

• LCM 6.2.1B





1.5 System requirements

1.5.1 Server requirements OMC-P Server software runs on a Sun Solaris platform. The minimum recommended hardware configuration is:

• A Sun Solaris platform with a 550 MHz CPU minimum

• 2 Gbyte of memory minimum

• 36 Gbytes of hard disk space minimum

• A 100MB Ethernet connection

• Sun Solaris 8 or Solaris 9

• Oracle Database 8.1.7.4 (The instance provided by Lucent must be used)

• Java JVM 1.5.0.7 (The instance provided by Lucent must be used)

The EMS Server software can also be deployed in a High Availability (HA) configuration. This configuration requires two Sun Solaris platforms as described above and a 3X18GB (minimum) RAID 1 disk array. It also requires installation of the Veritas Storage Foundation 4.1 software. The EMS Install Guide provides more information on installing the Veritas and OMC-P software in a HA configuration

1.5.2 Solaris version and patch requirements OMC-P software (client or server) requires a Solaris 8 or Solaris 9 platform operating system. Lucent recommends that the latest available Solaris patch sets and packages be installed on the host machine and that the patches be updated as part of regularly scheduled maintenance procedures.

1.5.3 Oracle database requirements The OMC-P Server employs an Oracle database for persistent storage of selected configuration information as well as user account information. Oracle 8i Standard Edition Release 3 (8.1.7.4) is bundled into this release of EMS software. Use of the provided instance of Oracle is required. Using a different instance of Oracle will void your Alcatel-Lucent support agreement.

1.5.4 Java JDK requirements Java JDK version 1.5.0_02 is bundled in with the EMS software. This is the only version of Java that should be used to run this software and there is no need to install a different version. Using a different instance of Java will void your Alcatel-Lucent support agreement.

1.5.5 Client requirements The OMC-P Client software is written in Java™ and runs on Sun/Solaris, Windows XP™, Windows NT™ or Windows 2000™ platforms.

The minimum recommended configuration for a Windows-based client is:





• A 200MHz CPU

• A minimum of256 Mbytes of RAM

• A minimum of 4 Gb of free disk space is necessary to install the client application

• Executing other applications may require additional memory

To run the client on a Sun/Solaris platform:

• A Sparc or greater level system is recommended

• A minimum of 256 Mbytes of memory is recommended

• A minimum of 4 Gb of free disk space is necessary to install the client application

The Common Desktop Environment (CDE) must be used when running the client in the Sun environment.

Alcatel-Lucent recommends that only one client run on each platform.

Alcatel-Lucent does not recommend using a configuration where a single server runs multiple clients or the client applications are x-termed to user displays.

1.6 Installation and start-up procedures Installation is essentially identical to the installation of previous releases. Use the EMS 9.11.0.0 Installation Guide.

1.7 Restrictions and special considerations

1.7.1 Supported products and releases Supported products and releases are now documented in the section titled Manageable Switches and Applications.

1.7.2 OMC-P server startup time The OMC-P application can start up within approximately four (4) minutes. There are no major startup configuration options.

1.7.3 Security events Alarms and events are logged in the EMS Alarm and event logs. For security event filtering, see document number 255-400-418, the OMC-P User Guide for Lucent Gateway Platform Management’s Chapter 3, the section titled, Adding a User Client. This section includes information adding or modifying alarm and event filtering client by client.

1.7.4 Default system logins OMC-P has two default passwords.

One for the unix account plx/plx – this account owns the OMC-P software – not root.

The second is account telica_admin/telica_admin, which is the EMS default user account.





1.7.5 User activity audit logs User activity can be reviewed by using the Config Log tool filtered by user. To use the Config Log tool, see 255-400-400, the OMC-P for Lucent Gateway Platform Management Reference Guide’s chapter 2, Introducing the Navigator. Additional filtering information is linked to user setup and additional user setup tools are referenced in section 1.7.3 Security events in this document.

1.7.6 International echo control variant type A new international echo control variant has been added to the switch software and is enabled for all trunk group types. When configuring a Trunk Group you must select the proper echo control type.

2 NEW FEATURES/FUNCTIONS

2.1 New features This release introduces Geographic Redundancy switch support in the EMS. The Lucent Signaling Gateway (SG and the Lucent Network Controller (MGC) both have switch-to-protection scenarios that are supported on the EMS. The EMS’s Status and Application pane now has new columns to display status for GR provisioned switches. The new columns display GR status and list the GR Peer devices. GR Status will be updated from either an administrative or autonomous failover. Also, TL1 commands issued to the working switch from the craft port or the EMS will be logged and replicated to the standby switch. Given an unavailable standby peer, the replicated commands will be queued and flowed down to the standby peer switch when it is available again. A new Synchronize TL1 Script command allows a file representing the inventory within the Oracle database to be saved and viewed as an HTML report. Differences between the scripts of the working and standby switch can be checked.

A new switch configuration type, the Lucent Compact Controller, combines Signaling Gateway and Media Gateway Controller functionality into a single chassis. The EMS nomenclature displayed in the Status and Application pane lists the Lucent Compact Controller as an SG-MGC. Additionally, new types of Lucent Signaling Gateways are supported.

Lucent Signaling Gateway (SG) types supported:

• PSG: Default �ignalling gateway which supports ANSI and ITU variants. Does not support the China variant

• ISG: Improved Signaling Gateway which supports all PSG functionality and China variant.

• DSG: Distributed Signaling Gateway which supports distributed SG configuration for higher throughput. Presently, same as ISG.

Lucent Network Gateways (MG) types supported:

• PG : Default Plexus Media Gateway





• TDMIP : Determines whether AMR/AAL2 will be enabled. Currently AMR cannot be intermixed with TDP to VOIP.

• UMTS: Universal Mobile Telecommunications System

Also new with this release is EMS support of STG links and profiles that supports a Lucent Signaling Gateway configured as an ISG (Improved Signaling Gateway). The STG node performs SG functions with the China MTP-3 variant.

This release introduces new Application and Status Pane tabs. The BTS tab allows you to view events from the BTS server when the BTS server’s SNMP agent issues traps to the EMS server’s IP address. You can also create an equivalent AudioCodes tab. Follow the procedure in the OMC-P Lucent Gateway Platform Management User Guide 255-400-418 titled, Report BTS Events to the EMS, but substitute AudioCodes for BTS in the procedure.

The Event tab allows display of TL1 events or SNMP traps from SNMP agents from the following devices: the TAOS MG, the BTS (Billing and Traffic Server), the NGFS, the LCM (Lucent Communications Manager), and the AC (AudioCodes). The event log wraps after 250 events but old events are available from a log file. The fields include the timestamp, the issuing device and the contents in the variable binding in the SNMP trap or the event data. Fault log controls such as removing cleared events are not supported. Events can be forwarded northbound.

New PBX trunks and profiles allow communication between Lucent Gateway Platform switches and PBXs over ISDN PRI, CAS or SIP trunks. The choice of trunk type supports both IP and TDM PBXs.

Performance monitoring (PM) has been expanded and enhanced for this release. The Ethernet ports of the SP cards can now be monitored, plus NP (number portability) statistics can be collected, The ENA and ANA cards now have their performance monitored, the VSM card’s AAL, VP, and VCC endpoint statistics can now be monitored, and the ENET card’s VoIP endpoint statistics can be monitored.

A new international echo control variant has been added to the switch software and is enabled for all trunk group types.

2.2 TL1 command to OMC-P screen matrix The following table contains the new and modified TL1 commands and lists the GUI screens in the EMS that correspond to those TL1 commands. Some commands are only valid on switches that have that function. As an example, you will only see the node for SG Protection on an SG provisioned in a Geographically Redundant application.

TL1 Command

TLTL1 TL1 Command Equivalent EMS Screen Location

PRFL-IS41TMR SS7>Intelligent Network Services>IS41 Protocol Profile

PRFL-ORIGPBX IMT> Origination PBX Profiles PRFL-TERMPBX IMT>Termination PBX Profiles PRFL-INSAP SS7>Intelligent Network Services>Service

Access Point Profile PRFL-ISUPAR IMT>ISUPAR Profiles INIT-REG/RTRV-PM-ENET Cards>Active ENA Card>Select Port>Right-click

Port>View Performance





TL1 Command Equivalent EMS Screen Location INIT-REG/RTRV-PM-ENETSP Cards>Active SP>Right click SP>View>Click

PM ENET SP tab>Click Refresh INIT-REG/RTRV-PM-ENETEQPT Cards>Active ENA Card>View>Click PM

ENEQPT tab>Click Refresh RTRV-PM-ENETENDPT Cards>Active ENA Card>Ports>ENET

Port>ENET Endpoint>Highlight Endpoint>View

INIT-REG/RTRV-PM-APC Cards>Active ENA Card>View>Click PM APC tab>Click Refresh

INIT-REG/RTRV-PM-VSMAAL Cards>VSM Card>Right-click>View>PM VSMAAL Stats tab

INIT-REG/RTRV-PM-VSMVP Cards>VSM Card>Right-click>View>PM VSM VP Stats tab

INIT-REG/RTRV-PM-VCCENDPT Cards>VSM Card>Right-click>View>PM VCC Endpt Stats tab

RTRV-PM-WIN Right click switch>View Performance (from Monitor Performance>Select PM Type)

RTRV-PM-NP Right click switch>View Performance (from Monitor Performance>Select PM Type)

NP-SYS SS7>Intelligent Network Services>NP Sys MGC-PROTN MEGACO>Associations>MGC Protection SG-PROTN MEGACO>SG Protection M2UA-SYS M2UA>System SG-M2UAASSOC M2UA>SG M2UA Assoc M2UA-SGASSOC M2UA>M2UA SG Assoc SG-SLK M2UA>SG SLK LCC Calling Area Administration>Line Class Code ED/RTRV-STG-SYS STG>STG System LIST-SCREEN Subscriber Database>List Screen SW-TOPROTN-SG SS7>MEGACO>SG Protection SW-TOPROTN-MGC SS7>MEGACO>MGC Protection CALLING-AREA Calling Area Administration>Local Calling Area STG-MTPNETTYPE STG>STG MTP NetType STG-PCOWN STG>STG Pc Own STG-LSET STG>STG Lset STG-PRFLSLKL3 STG>MTP3 Profile STG-SLK STG>STG SLK STG-ROUTEPRIORITY STG>STG Route Priority STG-MTPROUTE STG>STG MTP Route STG-PCALIAS STG>STG PC Alias SUB-PBX Subscriber Database>Subscriber PBX Modified TL1 Commands

DEF-GENIE Modified TL1 command paths in the EMS are not provided.

ROUTE TREATMENT DLT/ED/ENT/RTRV-STS1 ENET-ENDPTVOIP OC3/OC12 RTRV-PM-RSRC INIT-SYS SNMP-TRAP





TL1 Command Equivalent EMS Screen Location OPR-CCR OPR-CQM SS7-TRK TRKGRP PRFL-SDP MGC-PCOWN MGC-PC SWITCH-CFG SG-ISUPPROXY GMSC-ANSISYS MGC-SGASSOC SG-SYS SG-MGCASSOC AUDIO-SYS CHASSIS-EQPT IPROUTE PRFL-INSAP SLHR-SCP LIST-AINTRIGGER PRFL-SLKL2 SLK ISDN-IF VOP-SYS RTRV-STATUS-CTXT RTRV-STATUS-TDMTERMID RTRV-STATUS-VOIPTERMID RTRV-STATUS-VOATERMID RTRV-ALM-LSET RTRV-ALM-ROUT RTRV-COND-LSET RTRV-COND-ROUT SERVICE-ACCESSCODE





2.3 Configurable properties The OMC-P provides two editable properties files to customize the software’s appearance and operation. Both files are located in the following directory:

{ROOT}/opt/PlexView/Server/Properties .

The first file, plexview.properties, customizes client side behavior and appearance. If you edit this file, restart your client session(s) for the change to take effect.

The second file, plexcore.properties, customizes server behavior. If you edit this file, reboot the server for the changes to take effect.

Each new version of software ships with template versions of these files. The template versions are called plexview.properties.template and plexcore.properties.template respectively. Examine the template files and merge the required changes into the plexcore.properties and plexview.properties files.

2.3.1 New plexview.properties template properties The following new properties are included in plexview.properties.template for this release:

# /** # * Status Panel Customization Property # * # * Description: Enable/Disable “GR Status” / “GR Peer” columns in status panel # * # * Rules: N/A # * # * enableGRStatus – Enable/disable the GR Status # * Type: boolean # * Range: True/False # * Default: true # */ #enableGRStatus=true # /** # * SW_TOPROTN-MGC Operator Privilege level Property # * # * Description: The recommended privilege level for # * SW_TOPROTN-MGC is service affecting (SA). Property # * swToProtnMgcPrivLevel allows the privilege level # * to be raised to software (SW). The SW_TOPROTN-MGC # * command is used to force a MGC failover from the # * working MGC to the protection MGC. # * # * Rules: N/A # * # * swToProtnMgcPrivLevel – set the operator privilege level # * to SA or SW. # * Type: string # * Range: {SA,SW} # * Default: “SA” # */ #swToProtnMgcPrivLevel=SA





# /** # * SW_TOPROTN-SG Operator Privilege level Property # * # * Description: The recommended privilege level for # * SW_TOPROTN-SG is service affecting (SA). Property # * swToProtnSgPrivLevel allows the privilege level # * to be raised to software (SW). The SW_TOPROTN-SG # * command is used to force a SG failover from the # * working SG to the protection SG. # * # * Rules: N/A # * # * swToProtnSgPrivLevel – set the operator privilege level # * to SA or SW. # * Type: string # * Range: {SA,SW} # * Default: “SA” # */ #swToProtnSgPrivLevel=SA # /** # * Default ISUP Variant property. # * # * Description: This property is used to set the ISUP Variant to # * the variant of the end user. This prevents error messages # * from being generated when the ADD MGC Point Code (ENT-MGC-PC) # * and the ADD ISUP Trunk Group (ENT-TRKGRP) dialogs are displayed. # * # * Rules: Must be a valid ISUP variant enumeration. # * # * isupVariantDefault – set the default ISUP Variant to a valid # * ISUP Variant enumeration. Check the TL1 documentation # * for the valid string. The following is a list of known # * enumerations: ISUPANSI1992, ISUPITUQ767, ISUPITU, # * ISUPETSI, ISUPMEXICO, ISUPTELSTRA, ISUPG500, ISUPANSIATT, # * ISUPITUQ767ATT, ISUPBR, ISUPIN, ISUPG500V2000, # * ISUPG500V2002, ISUPDE, ISUPVE, ISUPPL, ISUPAR, ISUPCN, # * ISUPCR, ISUPVEMOVILNET. Is wise to check the current # * documentation for TL1 commands ENT-MGC-PC and ENT-TRKGRP # * since the above list may be out of date. # * # * Type: string # * Range: {see the TL1 documentation for valid enumerations} # * Default: “ISUPANSI1992” # */ #isupVariantDefault= # /** # * Multiple Navigator Trees # * # * Description: This property is used to alter the default (1) number of # * Navigators allowed to be opened when selecting a Switch or Network Element # * from the Switch Status Panel(s). # * # * Limitation to the amount of memory installed on the client platform. Setting





# * the parameter higher than the default (1) may have an adverse affect on the client # * desktop performance. # */ # # navigatorCount=2

2.3.2 New plexcore.properties template properties No properties in this file are new for this release.

2.4 NAL (Node Access List) changes A Node Access List (NAL) provides fine-grained access control allowing the OMC-P system administrator to limit individual operator account provisioning capabilities to a specific functional area. A NAL list requires the system administrator to assign a privilege level (RW or RO) for each node in the navigator tree and to save the NAL list to the database. The NAL(s) can then be assigned to any operator level account. The operator account’s NAL list determines the node-by-node provisioning capabilities granted to the account.

NAL security is only supported on Lucent Gateway Platform switches.

Because new software releases introduce new navigator nodes, the system administrator must review and modify the NALs each time an OMC-P software upgrade is performed. New nodes in the NAL default to RO, so operators cannot provision new nodes after an upgrade, even if the node is within their functional provisioning area. Modifications to the NALs required for each upgrade depend on the previous version of OMC-P software, the new version of software, and the versions of switch software being managed.

The list below summarizes the navigator node changes that have occurred between the 9.11.0.0 release and this 10.0 release and are applicable to the management of 6.x.x.x and 5.x.x.x LGP network elements.

LGP switch new NALs

New NALs are listed for every new command in the column titled Equivalent EMS Screen Location in the table titled, TL1 command to OMC-P screen matrix in this document. These new commands have equivalent NALs that must be updated for switches that use those commands.





3 ADVANCED REPORTING SOFTWARE RELEASE

3.1 Advanced Reporting System with or without Advanced Traffic Collection

The Advanced Reporting System is optional software. If you do not have the Advanced Reporting System, skip to section 4.

This software release notice section covers both the optional Advanced Reporting System and the optional Advanced Reporting System with the Advanced Traffic Collector.

The advanced reporting system provides a reporting environment that enables you to generate, schedule, and control access to predefined customizable reports. The advanced reporting system provides access to Inventory (for both the EMS and switches), Performance Monitoring, Traffic Statistics, and Order Entry data. The platform uses an architecture consisting of distributed databases and the report engine from Business Objects.

This software release notice (SRN) contains important release-specific information that is not available elsewhere.

3.2 License keys The OMC-P Element Management System License Readme contains information on Advanced Reporting license keys. Please allow two business days for Advance Reporting System keys to be generated and sent to you.

3.3 Advanced Reporting System requirements The minimum recommended system requirements for this version of the Advanced Reporting System are provided in the following sections. For situations where hardware resources will be shared by applications or the architecture of the ARS could change over time, contact Lucent Worldwide Service for further information on recommended hardware.

3.3.1 EMS Server with Advanced Reporting workstation requirements The standard server sizing for the OMC-P workstation applies when using Advanced Reporting.

3.3.2 Advanced Traffic Collector workstation requirements The optional advanced traffic collection workstation will contain the StatsCollector application. This hardware requirement section is valid regardless of the architecture of the TSAA/StatsCollector relationship. The traffic collector workstation has the following minimum hardware requirements:

• 550 Mhz Processor

• 1GB RAM

• Hard drive options are listed in the next section.





3.3.2.1 Advanced Traffic Collector hard drive configuration options:

The standard ATC configuration uses two 36GB (minimum) hard drives. All system and application software is installed on the first disk. The Oracle database is installed on the second disk.

The recommended disk partitions and sizes are as follows:

Disk 1:

• /4 GB

• swap 2 GB

• /usr 4 GB

• /opt All remaining space – all software is installed in this partition

Disk 2:

The second disk is configured as a single partition. The /opt/PlexView/Oracle/ora02 mount point is on the second disk:

/opt/PlexView/Oracle/ora02 – 36GB partition. The Oracle database is installed here.

Note: When using this configuration, periodic backups, if required, must be performed manually.

3.3.2.2 Mirrored configuration option

To back up ATC data and software, an alternative configuration using two 36G hard drive with one drive acting as a mirror can be used. The operating system (OS), application software and Oracle database reside on the same physical disk. This configuration may result in lower performance than the standard configuration.

The recommended disk partitions and sizes are as follows:

Disk 1:

• 4 GB

• Swap 2 GB

• /usr 4 GB

• /opt All remaining space – all software is installed in this partition

• /opt/PlexView/Oracle/ora02 – this directory resides in the /opt partition. The Oracle database is installed here

Disk 2:

In this configuration, Disk 2 serves as a mirrored backup of Disk 1.

Note: The same configuration applies whether mirroring is performed by Sun Solstice or by Veritas Volume Manager.

3.3.2.3 The commands to check your setup are:

swap-l





df-k

3.3.3 Business Objects PC requirements The Business Objects PC must be a new PC and must be dedicated to the Advanced Reporting System. You can use this PC for the Business Objects client.

Note: This PC must never have had an instance of Oracle on it. If an instance of Oracle has ever been on the PC, do not use it.

The PC that will run the Business Objects software must meet the minimum specifications as stated by Business Objects. This software can be installed on computers running:

• Windows NT with Service Pack 6a

• Windows 2000

• Windows XP

3.3.3.1 Oracle database requirements

The PlexView Server employs an Oracle database for persistent storage of selected configuration information as well as user account information.

Oracle 8i Standard Edition Release 3 (8.1.7.4) is bundled into this release of ARS software.

3.3.3.2 Optimizing Oracle physical database layout

The physical database layout can be optimized on the Advanced Traffic Collector workstation. Overall system performance improves when you add additional physical disk drives and map them to Oracle data directories. Lucent recommends that each directory map to a separate disk.

Instructions are included in the Advanced Reporting System installation procedures.

3.4 Validated supported switch releases This release adds Advanced Reporting System support for the new features in the switch releases supported by this release of OMC-P software. For a list of supported switch software releases, see the section titled 1.4 Manageable switches and applications in this document.

3.5 WebIntelligence patch The WebIntelligence patch introduced into the 255-400-201R9.11.0.0 Lucent Gateway Platform Advanced Reporting System Installation and Setup Guide is no longer required. That patch is now automatically installed when you install ARS 10.0 software and the webi patch installation procedure is not required.

3.6 Advanced Reporting System fixed and known anomalies Advanced Reporting System fixed and known anomalies are listed in section 4 of this document.





4 EXCEPTIONS AND WORKAROUNDS

4.1 Exceptions The following lists include the fixed exceptions (anomalies) in this software release.

4.1.1 OMC-P managing Lucent Gateway Platform switches fixed anomalies

ID Number

Customer Reported Incident #

Priority Summary of Fixed Anomaly

46607 Manual refresh is still required after taking IOM-8-ENET-2 out of service. Works with 6.2.0.1 or 6.2.0.2 switches. See section 4.2.1 for further details.

46647 Broadcast agent does not restart after EMS failover

46711 Unable to delete route digits in bulk from EMS

42776 P2 TRC-CALL-EQPT on an AU3-E1 fails

43063 P2 STM1 ports are not updated real time in the navigator

43956 P1 EMS support for rtrv-status-tdmtermid and rtrv-pm-voipckt

44734 P2 ISDN wizard T0 ports preview fails on STM1

45523 P2 SS7 links on TUG-E1 do not display properly

46285 P2 Geographic redundant protection status does not display properly

46375 P2 “-“ and ”.” are not allowed in FQDN for primary key PNAME

46840 P2 5.1.0 to 5.1.2 hot upgrade reorders TIMESTEN SUBCL4 table elements

46953 49239

1-1431178 P2 There is no count down timer that we can see from PlexView after account has been created.

46971 1-1417796 P2 BTS Heartbeat alarms occurring frequently

47146 1-1438191 P2 4 digit country code needs to be supported

47149 P3 OK action should be de-activated on successful country code search





ID Number



47164 P3 Log search should not display a message that must be dismissed if no entries are found

47284 P4 Misspelling on switch log dialogue

47310 P2 SG-PROTN attr name change: MASTERMGCLU -> MASTERMGCAS

47734 P2 RTRV-PM-CC should not be allowed for MG or SG chassis types

47739 P3 EMS synch

47812 P2 No information in EMS for STM1

47813 P2 OMC-P missing �ignalling link information

47904 P3 Add/Modify Audio announcements should allow 0 for repetition counter

47905 P2 Error when viewing VSM AAL VCC for VSM2

47918 P2 Last valid login date time should be displayed on login security message

47919 P2 Unsuccessful login attempts should be displayed on login security message

48021 P2 SG-SLK Performance statistics should be available

48178 P2 FS5K Digit Tables should be sorted in numerical order

48224 P1 MG status retrieval fails

48314 46324 P2 Unable to sync NC on EMS after upgrading NC to 5.1.2.3 – MkRouteList java null pointer exception.

48393 P2 Cannot provision a PRI and SS7 link on a 414 card

48488 P2 TL1 synchronization report does not contain ENT-ROUTE

48532 1-1466935 P2 SNMP Proxy sending V1 traps when configured for V2

48577 P2 Add a property for default TG variant

48733 P2 Add a property for default MGC point code variant

48768 1-1474069 P2 BTS OIDS have an extra .0 postfix

48788 P2 Could not add or modify Trunk Groups (both ISUP and SIP)

48790 P2 Invalid Point code display





ID Number



48791 P2 Chassis-2 failed to sync with EM

48852 P2 Allow underscores in BILLSYS system name

48889 46056

1-1416176 P2 Webi Patch required to fix file opening issues after web server and VERITAS contention issues

48909 P2 BTS entries should be allowed in fault filters

48914 P1 ITU Point Codes display improperly

48915 P1 EMS synch error

48944 P1 Cannot create ISUPIN trunk groups

48946 P1 Link set add fails

48947 P2 TERMIDS are incorrect for STM1 E1

48949 P2 Error in �ignalling capture

48979 P1 Cannot sync the SCLAUSSG to OMC-P R10CI2

48980 P2 SG-SLK State cannot be modified

48985 P2 ENETSP Statistics display improperly

49009 49368 49483 49484

P1 OMC-P does not allow you to view new value in digitmod-PARAM

49039 46614 P2 WIN_PHASE needs to be GMSC-WINSY on hot upgrade

49059 P2 IP Routes display improperly

49064 ESC8122 P2 Synchronization failure with a large number of AIN trigger lists

49066 P2 Cannot set state of SG-SLK through EMS

49069 P2 History is missing for some VSM DSP counters

49073 P1 STM1 trunks are not displayed properly

49088 1-1480553 P2 Unable to add service access point profile

49114 P3 Add/Modify SDP profile should allow a Fax Action of T38STRICT without a PCMA or PCMU

49169 P1 Geographic redundancy should not replicate state changes

49182 P2 TRKGRP.SDPPRFL default value change





ID Number



49188 P2 Sync TL1 report does not Add LNP SLHRID to service access code

49190 1-1483349 P2 Multiple LCP entries in Node Access List

49204 P2 OMC-P does not replicate dlt-trkgrp from working MGC to standby

49212 P2 Delete all trunks fails when trunk count is greater than 3000

49223 P2 OPR-CQM results are truncated

49224 P2 Capture components are not displaying

49333 P1 E1 Facility alarm not displayed in EMS GUI

49343 P1 Timing reference is not displayed properly for E1 BITS

49345 P2 TMGREF in EMS always shows TMG-T1 even if set to TMG-E1

49382 P2 Performance statistics cannot be viewed for an E1 that is OOS

49427 P2 Packet error on alarm refresh

49455 P2 Cannot select autocommit field for calendar order entry

49475 P2 OMC-P only allows Digitmod-DN to be selected on Treatments

49476 48883

P2 OMC-P does not replicate dlt-trkgrp from working MGC to standby

49477 48883

P1 OMC-P replicates ED-EQPT Commands executed in Working System to Standby System

49517 P2 EMS does not parse an alarm properly

49519 P2 Modify SIP system fails

49531 P2 Cannot configure VSM3 card

49539 P1 java.lang.OutOfMemoryError: Java heap space

49558 P2 STM1 status not updated for error on EMS

49559 P2 Enet status not updated for error on EMS





ID Number



49925 P2 Failed login attempts on security message is prefaced with a “-“

49997 P2 OMC-P User’s Failed Login Attempt not working

50033 P1 Standby ENET endpoints displays are not updated properly

51802 1-1535548 P2 OMC-P is reporting GR STATUS for MGC incorrectly and allows translations to be added via standby MGC without warnings

52355 1-1546368 P2 Incorrect GR Peer shown in Switch Status Pane

4.1.2 OMC-P Advanced Reporting System fixed anomalies

ID Number



41550 P1 WebIntelligence is not restarting after an EMS reboot

45300 P2 invalid column name when generating Lcmauthenticationservicerpt

45328 P2 Invalid column name when generating report of Lcmlogginservicerpt

46056 P3 Error: This file could not be opened" when trying to open a report. Webi patch bundled into install for ARS 10.0

47178 P3 Add Traffic Utils Relative Dates : support for last 3, 7, 10, 30, 60, 90 days

48533 48536

P2 Add Card SerialNumber and HardwareVersion to CardRpt

48889 P2 Scheduler restart issues on HA failover

49232 P2 OMC-P Universe: Gap for SS7 route report





4.1.3 OMC-P managing Feature Server 5000 and Lucent Communication Manager fixed anomalies

ID Number



IMR 846782

Support "-" in the add switch screen for switch name

IMR 833088

ParyID should be unique across the network

IMR 844809

Decouple Remote User from DN Ext

IMR 847117

BGCF profile does not support "-" or "_"

IMR 847117

BGCF URI Q priority does not support "-" or "_"

IMR 847678

The digit table pull down menu must be ordered by table number

49608 P2 EMS needs to restart WebAPI automatically

4.2 Workarounds The following known anomalies are listed in these tables.

4.2.1 OMC-P managing Lucent Gateway Platform switches known anomalies

ID Number


Priority Summary of Known Anomaly

46607 Manual refresh is still required after taking IOM-8-ENET-2 out of service. Works with 6.2.0.1 or 6.2.0.2 switches but not for 5.1.2.3 switches





ID Number



48764 46653 EMS does not synch with switch database after deletion of 14000 Route Digits via Tl1

49770 P2 Web API - missing xxxx-list-tollfree - documented but not implemented

49967 P2 STM1 state change on stand by E1 port not reflected

49986 P2 OMC-P View Switch Alarms for LCM times out after 300 seconds

4.2.2 OMC-P Advanced Reporting System known anomalies

ID Number

TIL/ Incident Number


50208 P2 During Webi Startup, Apache may sometimes die causing Veritas to initiate a failover. Workaround: Make the web server a non critcal resource in the Veritas main.cf configuration file.

4.2.3 OMC-P managing Feature Server 5000 and Lucent Communication Manager known anomalies

ID Number



IMR 844317

When 100 subscribers are displayed, in range new subscriber not displayed

IMR 844318

Feature window shows web portal assigned by LCM Switch pulldown is blank

IMR 844807

Description missed for SeqRing If you drag the display district, it can be displayed.

IMR 847418

Modification failed after deleting secondary PUIDs on Compact FS (has an HSS)





ID Number



1-1499055 In R1.0 switches, the Digit Table Number type of International Operator Assist is incorrectly displayed as IDDD Prefix.

Documents

OMC-P Software Release Notice Release 10.0.0 · OMC-P Software Release Notice Release 10.0.0.1 ... 1.5.3 Oracle database requirements ... OMC-P RELEASE 10.0.0.1 4