Lucent Control and Gateway Platform Element Management System (PlexView EMS) Software Release Notice for All Supported Platforms

Transcription

1 Lucent Control and Gateway Platform Element Management System (PlexView EMS) Software Release Notice for All Supported Platforms Part Number R Issue 1 March 17, 2006 Software Version Copyright 2006 Lucent Technologies All Rights Reserved

2 Copyright 2006 by Lucent Technologies. 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 Lucent Technologies), except in accordance with applicable agreements, contracts or licensing, without the express written consent of Lucent Technologies and the business management owner of the material. For permission to reproduce or distribute, please contact the following: Product Development Manager LTINFO6 (domestic) (international) Notice Every effort has been made to ensure that the information in this document was complete and accurate at the time of printing. However, information is subject to change. Mandatory customer information Safety Always observe the Safety Instructions when operating the system. Trademarks All trademarks and service marks specified herein are owned by their respective companies. Ordering information The order number of this document is R Support Technical support Please contact your Lucent Technologies Local Customer Support Team (LCS) for technical questions about the information in this document Lucent8 Information product support To comment on this information product online, go to or your comments to comments@lucent.com.

3 PlexView Element Management System Software Release Notice 1. Software Release Notice Table of Contents Release Release Abstract Software System Requirements... 7 PlexView Server Requirements... 7 Solaris Version/Patch Requirements... 7 Oracle Database Requirements... 8 Java JDK Requirements... 8 PlexView Client Requirements Lucent Control and Gateway Platform (PlexView) Element Management System Reference Documentation New Features TAOS MG Support Feature Server 5000 Support Lucent Communication Manager Support Application and Status Pane Tab Additions Support for Lucent Gateway Platform Switch Release Support for Lucent Gateway Platform Switch Release Support for Lucent Gateway Platform Switch Release Support for Lucent Gateway Platform Switch Release Support for Lucent Gateway Platform Switch Release Billing Records Expanded with Biller ID and Service Category Fields Features Previously Introduced in EMS 9.7 and Distributed Switches Are Now Supported Distributed Lucent Network Gateways Display Virtual Inventories Available Switch Nodes Vary By Chassis Type and Switch Software Release SS7 Point Codes and Proxy Provisioning is Updated New ISUP Profiles support International Switch Use MEGACO Defines Distributed Connectivity and Topology IUA Carries Communication Between Signaling Gateway and Network Controller.. 15 The MG CAS Profile is Under System Services Number Administration Supports International Numbering Plans Performance Monitoring adds View Performance Feature for Global PM Graphical Representation of Performance Monitoring is Available GPP Performance Monitoring Support EMS Related Traps now include Alarm Ids Configurable Properties Customizable Server Properties New Properties for EMS Northbound SNMP Trap Properties New Properties for EMS VPS Status Poll Property The ISUP CIC Range is a Configurable Property INIT-SYS Permission Level is a Property Lucent Technologies, Inc. 3 of 36

4 Software Release Notice PlexView Element Management System Password Complexity Property Receiving SNMP Traps Property Feature Server 5000 Status Polling Interval Property New Properties for EMS 9.7 and SNMP Traps can be Forwarded to Multiple SNMP Managers SSL Data Encryption Between Client and Server Forwarding Alarms and Events as SNMP Traps Restrictions and Special Considerations SSH encryption Re-establishment after Switch Software Upgrades Init-Sys Switch Erroneous Message Synchronize Switches after Upgrading Switch Software Connecting PlexView Clients and the Server through Firewalls and with NATs Unmanaging and Remanaging a Switch Deleting Switches Also Deletes All Related Database Entries NAL (Node Access List) Changes During Upgrades Installation Update Known and Fixed Anomalies Technical Support of 36 Lucent Technologies, Inc.

5 PlexView Element Management System Software Release Notice 2. Release Abstract This Software Release Notice (SRN) for version of 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 Lucent Control and Gateway Platform (PlexView) 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 applications are documented in the Lucent Control and Gateway Platform (PlexView) Element Management Systems 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 OMC-P manager of the Feature Server 5000 and Lucent Communication Manager is now retitled as the Lucent Control and Gateway Platform (PlexView) Element Management System. This software release notice introduces management of the Feature Server 5000, the Lucent Communication Manager and the TAOS MG. Consult the Reference Documentation section in this document for further details on the Feature Server 5000 and the Lucent Communication Manager s EMS interface. TAOS MG management is in a chapter included in the Lucent Control and Gateway Platform (PlexView) Element Management System User Guide. The terms OMC-P, EMS, and PlexView are used interchangeably throughout this document and all references refer to the Lucent Control and Gateway Platform (PlexView) Element Management System. The EMS 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 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. Lucent Technologies, Inc. 5 of 36

6 Software Release Notice PlexView Element Management System 3. Software This release of the PlexView EMS software consists of the following software: PlexView Client Release, Version PlexView Server Release, Version This release contains a version of the PlexView Client installation program that enables you to install PlexView Client software on multiple Sun Solaris or Windows platforms. Releases of switch software that this release of EMS software supports are listed in the section titled, Restrictions and Special Considerations. 6 of 36 Lucent Technologies, Inc.

7 PlexView Element Management System Software Release Notice 4. System Requirements 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. Lucent Gateway Platform switches that can be managed by this software release include: Lucent Compact Switch Lucent Signaling Gateway (SG) Lucent Network Controller (MGC) Lucent Network Gateway (MG) Lucent Control Platform network element applications working on the LCP and clcp hardware platforms that can be managed by this software release include: Lucent Feature Server 5000 The Lucent Communication Manager runs on a Sun Fire workstation. The TAOS MG is a Lucent Media Gateway that is not part of the Lucent Gateway Platform family. The minimum recommended system requirements for this version of PlexView software are provided in the following sections. PlexView Server Requirements PlexView Server software runs on a Sun Solaris platform. The minimum recommended hardware configuration for PlexView is: A Sun Solaris platform with a 550 MHz CPU 1 Gbyte of memory minimum 36 Gbytes of hard disk space minimum A 100MB Ethernet connection This release does not support the configuration of more than a single PlexView Server instance. Solaris Version/Patch Requirements PlexView EMS software (client or server) requires Solaris 9 or 8 with the corresponding Solaris patches and packages. The required patches and packages are listed in the Installation procedure. Lucent Technologies, Inc. 7 of 36

8 Software Release Notice PlexView Element Management System 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 ( ) and the Oracle patch set are bundled into this release of PlexView EMS software. Use of the provided instance of Oracle is required. Using a different instance of Oracle will void your Lucent Technologies, Inc. support agreement. Java JDK Requirements The Java JDK version bundled in with the EMS software is jdk1.5.0_02. This is the only supported version of Java for this software and there is no need for a different version. Using a different instance of Java will void your Lucent Technologies, Inc. support agreement. PlexView Client Requirements The PlexView 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 of 128 Mbytes of memory (256 Mbytes recommended) A minimum of 100 Mbytes 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: An Ultra 10 or greater system is recommended A minimum of 256 Mbytes of memory is recommended The Common Desktop Environment (CDE) must be used when running the client in the Sun environment. Lucent recommends that only one client run on each platform. Lucent does not recommend using a configuration where a single server runs multiple clients or the client applications are x-termed to user displays. 8 of 36 Lucent Technologies, Inc.

9 PlexView Element Management System Software Release Notice 5. Lucent Control and Gateway Platform (PlexView) Element Management System Reference Documentation This software release notice for this revision of EMS software has an accompanying Installation Guide and multiple User Guides, depending on the application you want to manage. The listed guides are current for EMS software. The supporting guides to use are: Installation: Lucent Control and Gateway Platform Element Management System (PlexView EMS) Installation Guide for the Lucent Gateway Platform Part Number R See the Installation Update section in this Software Release Notice for any additional instructions. If there is no section heading with that title, then there are no additional instructions beyond what s in the Installation Guide. User Guides: Lucent Control and Gateway Platform Element Management System (PlexView) User Guide for the Lucent Gateway Platform Part Number R Lucent Control and Gateway Platform Element Management System (PlexView) User Guide for the Lucent Feature Server 5000 Part Number R Lucent Control and Gateway Platform Element Management System (PlexView) User Guide for the Lucent Communication Manager Part Number R Advanced Reporting Documentation: Lucent Gateway Platform Advanced Traffic Collection for the Advanced Reporting System User Guide Part Number R Lucent Gateway Platform Advanced Reporting System Installation & Setup Guide Part Number R Lucent Gateway Platform Advanced Traffic Collection for the Advanced Reporting System Installation & Setup Guide Part Number R Lucent Gateway Platform PlexView Advanced Reporting System and Advanced Reporting System with Advanced Traffic Collection Software Release Notice Part Number R Lucent Gateway Platform Advanced Reporting System Master Checklist Part Number Lucent Technologies, Inc. 9 of 36

10 Software Release Notice PlexView Element Management System 6. New Features This section summarizes the new features provided in this release of PlexView EMS software. New Devices Managed Starting with EMS New EMS Traps EMS supports the generation and northbound forwarding of three new EMS only traps. These traps are: 1. An EMS up trap that is sent northbound whenever the EMS server has initialized and is ready to receive client request. The generation of this trap cannot be disabled. 2. An EMS down trap that is sent northbound whenever the EMS server has been shut down. The generation of this trap cannot be disabled. 3. An EMS keep alive trap that is sent northbound at a configurable rate to alert the northbound OSS that the EMS server is operational. The generation of this trap can be disabled. See the section titled, Configurable Properties in this document for more information on configuring these traps. TAOS MG Support The TAOS MG is a non-lucent Gateway Platform Lucent switch that acts as a Media Gateway controlled by a Lucent Network Controller. Management features include: Initiating Telnet Sessions from an EMS Client to the TAOS MG SNMP Traps issued from a TAOS MG can be processed as events by the EMS Supported trunk types can be provisioned individually or as ranged trunks Feature Server 5000 Support EMS supports the simultaneous management of FS 5000 platforms using either Release 1.1 or Release 2.0 versions of FS 5000 software. The Feature Server 5000 is an application that runs on the LCP (Lucent Control Platform) and clcp (Compact Lucent Control Platform) chassis when either of those chassis is configured with the appropriate hardware and software to run the FS 5000 application. The Lucent Feature Server 5000 provides SIP call terminations when used in conjunction with Lucent Gateway Platform switches also managed by the EMS. The Lucent Gateway Platform switch provides class 4 SIP trunking and SIP call control. The Feature Server 5000 provides subscriber information and SIP call termination. A high-level description of the Feature Server 5000 and how to provision subscribers on that application using the EMS are provided in the Feature Server 5000 User Guide. Lucent Communication Manager Support EMS supports the simultaneous management of LCM platforms using either the 6.0 or 6.2 versions of the LCM software Beta software is also manageable. 10 of 36 Lucent Technologies, Inc.

11 PlexView Element Management System Software Release Notice The Lucent Communication Manager (Lucent CM) is an application that runs on a Sun Microsystems Sun Fire workstation. Lucent Communication Manager provides a web portal that subscribers can use to access and personalize their communications applications from a wireline or wireless device, when the communications application is provided by a Lucent Feature Server Feature and session control are available to a subscriber from any connectable endpoint. The underlying infrastructure of application servers between the subscriber s endpoint and the Feature Server 5000 that handles the subscriber s calls is transparent to the subscriber. The Lucent CM connects to the Lucent Feature Server 5000 by an Ethernet link and both applications are managed from the Element Management System (EMS). The calling features are actually provided by the Lucent Feature Server 5000, even though subscribers use the Lucent Communication Manager s subscriber portal to access their features. To use the Lucent CM s portal, the subscriber purchases web portal services from their service provider. The service provider then uses the EMS to provision the Lucent CM with a set of privileges and defaults for that subscriber s application. After the Lucent CM is provisioned for that subscriber, that subscriber can use a web launchable client from their PC or a mobile device to access services and applications and customize their personal communications setup. Using the Lucent CM web portal, a subscriber can: Establish calls (or sessions) Search and define contacts Invoke and manage their services Define their preferences Application and Status Pane Tab Additions With the introduction of new managed devices in this release other than Lucent Gateway Platform switches, the user interface was changed to allow access to these new managed devices. The Status pane has been enhanced with a second row. The new row at the bottom of the status pane is called the Application and Status Pane. This application and status pane includes manageable device types that are not shown by default in the status pane. Newly supported applications include: Plexus 9000 this is the default. LCP this is the Lucent Feature Server 5000 LCM this is the Lucent Communication Manager TAOS MG This is a Lucent Media Gateway that is not part of the Lucent Gateway Platform family Fault Status this status tab mixes device faults from all managed device types New supported features for managed Lucent Gateway Platform Switches Lucent Technologies, Inc. 11 of 36

12 Software Release Notice PlexView Element Management System Support for Lucent Gateway Platform Switch Release Lucent Network Gateway switches running switch release software have all features supported in the EMS management interface. Refer to the switch software release documentation for a list of new features. Support for Lucent Gateway Platform Switch Release Lucent Gateway Platform switches running switch release software have all features supported in the EMS management interface. Refer to the switch software release documentation for a list of new features. Lucent Gateway Platform switches now act as SIP trunking tandems that support Feature Server 5000 with enhanced SIP functionality. Refer to the switch Software Release Notes for further details. The STM 1 card is not supported for this release. Support for Lucent Gateway Platform Switch Release Lucent Gateway Platform switches running switch release software have all features supported in the EMS management interface. Refer to the switch software release documentation for a list of new features. The STM 1 card is not supported for this release. Support for Lucent Gateway Platform Switch Release Lucent Gateway Platform switches running switch release software have all features supported in the EMS management interface. Refer to the switch software release documentation for a list of new features. Support for Lucent Gateway Platform Switch Release Lucent Gateway Platform switches running switch release software have all features supported in the EMS management interface. Refer to the switch software release documentation for a list of new features. Billing Records Expanded with Biller ID and Service Category Fields Two new billing fields have been added to switch release , the Biller ID and the Service Category. These fields can be provisioned against incoming trunk groups or ISDN or CAS interfaces, or Subscriber Class 4 ANIs. As calls are delivered over these incoming trunk groups or interfaces or from a Subscriber Class 4, the new fields will be captured in the Call Detail Record. The order of precedence for capturing this data is trunk group or incoming interface and then Class 4 Subscriber. This feature allows the Service Provider to create customized billing assignments per trunk group, interface, or Class 4 Subscriber. Features Previously Introduced in EMS 9.7 and 9.8 Distributed Switches Are Now Supported Starting with EMS release , you can manage Lucent Gateway Platform switches set up in a distributed environment as follows: 12 of 36 Lucent Technologies, Inc.

13 PlexView Element Management System Software Release Notice The Lucent Compact Switch with software at release <5.x.x.x is still an integrated switch characterized in the EMS GUI s status pane with a chassis type of BOTH. Signaling Gateway, Media Gateway Controller and Media Gateway functionality still resides within this single switch and the switch still has Class 4 and Class 5 functionality. The Lucent Compact Switch with software at release >5.x.x.x is still an integrated switch characterized in the EMS GUI s status pane with a chassis type of SG_MGC_MG. Signaling Gateway, Media Gateway Controller, and Media Gateway functionality still resides within this single switch and the switch has Class 4 functionality. The Lucent Signaling Gateway with software at release >5.x.x.x is a signaling gateway in a distributed switching network and is characterized in the EMS GUI s status pane with a chassis type of SG. Signaling gateway functionality and communications links to supported downstream Lucent Network Controllers reside in this switch. The Lucent Network Controller with software at release >5.x.x.x is a media gateway controller in a distributed switching network and is characterized in the EMS GUI s status pane with a chassis type of MGC. Network Controller functionality and communications links to supported upstream Lucent Signaling Gateway and the supported downstream Lucent Network Gateways reside in this switch. The Lucent Network Gateway with software at release >5.x.x.x is a media gateway in a distributed switching network and is characterized in the EMS GUI s status pane with a chassis type of MG. Media Gateway functionality and communications links to the single upstream Lucent Network Gateway that supports it reside in this switch. Distributed Lucent Network Gateways Display Virtual Inventories In distributed systems, trunk groups and some other functions that are executed on Lucent Network Gateways (MGs) get provisioned on the Lucent Network Controller (MGC). The EMS client, though, displays these interfaces on their respective Lucent Network Gateway (MGC), presenting views of Lucent Network Gateways (MGs) with virtual inventories that actually reside on the Lucent Network Controller (MGC). TAOS MGs do not display virtual inventories on the Lucent Network Controller. Having virtual inventories keeps distributed system inventories consistent in appearance with integrated Lucent Compact Switch inventories. Available Switch Nodes Vary By Chassis Type and Switch Software Release Prior to Release 9.7 of EMS software, when you highlighted a switch in the status pane, the set of nodes and corresponding configurable objects depended on the switch s software release. Starting with Release 9.9 of the EMS, this section applies when you have selected the Plexus 9000 tab, the default, from the Application and Status Pane. Starting with Release 9.7, there is an additional factor that determines the nodes you will see and the available provisioning screens. That factor is the Chassis Type as displayed in the status pane. In the Lucent pane, you will only see and be able to configure nodes for that chassis type at that software release. When you highlight a switch with BOTH listed in the chassis field of the status pane, you will see all available nodes for that release of switch software for a Lucent Technologies, Inc. 13 of 36

14 Software Release Notice PlexView Element Management System switch configured as a Lucent Compact Switch running <switch release 5 software. When you highlight a switch with SG_MGC_MG listed in the chassis field of the status pane, you will see all available nodes for that release of switch software for a switch configured as a Lucent Compact Switch running >switch release 5 software. When you highlight a switch with SG listed in the chassis field of the status pane, you will see all available nodes for that release of switch software for a switch configured as a Lucent Signaling Gateway. When you highlight a switch with MGC listed in the chassis field of the status pane, you will see all available nodes for that release of switch software for a switch configured as a Lucent Network Controller. When you highlight a switch with MG listed in the chassis field of the status pane, you will see all available nodes for that release of switch software for a switch configured as a Lucent Network Gateway. SS7 Point Codes and Proxy Provisioning is Updated The SG and MGC functionality will not be in the same switch in a distributed environment, so point code information under the SS7 node is now broken out into SG Own Point Codes and SG Point Codes and MGC Own Point Codes and MGC Point Codes. SG ISUP Proxy provisioning has also been added. New ISUP Profiles support International Switch Use Under the IMT Node, new ISUP profiles have been added to support international variants of ISUP and replace the CIC profile from previous releases. For this release of software the following international variants have been added. MGC CAS Profiles ISUP ANSI Profiles ISUP ITU Profiles ISUP ITU Q767 Profiles ISUP Mexico Profiles ISUP VE (Venezuela) Profiles ISUP PL (Poland) Profiles MEGACO Defines Distributed Connectivity and Topology MEGACO can be set up fully using the system and association nodes under the MEGACO node. MEGACO, also known as H.248, sets up relationships between one or many MGs (Lucent Network Gateways) and a single MGC (Lucent Network Controller). The relationship set up by MEGACO provisioning enables the MGC (Lucent NC), which is aware of local and remote MGs (Lucent NGs), to select a path for traffic and to determine the service type for that traffic. 14 of 36 Lucent Technologies, Inc.

15 PlexView Element Management System Software Release Notice The EMS allows you to select the physical facility and then calculates the MEGACO Termination Id sent to the switch. You must provision the topology between MEGACO devices. IUA Carries Communication Between Signaling Gateway and Network Controller IUA system, endpoints, ASP (Application Service Process) and links are provisioned between switches in a distributed network under the IUA node. IUA stands for ISDN Q.921-User Adaptation. IUA is a protocol for backhauling ISDN Q.921 user messages over IP using the Stream Control Transmission Protocol (SCTP). IUA is used between a Signaling Gateway (SG) and Media Gateway Controller (MGC). The SG receives ISDN signaling over a standard ISDN interface. The MG CAS Profile is Under System Services Provisioning the MG CAS Profile establishes a Channel Associated Signaling (CAS) profile only on the Lucent Network Gateway, which works as the MG in this application. Number Administration Supports International Numbering Plans The Number Administration facility has been expanded to support numbers that are not part of NANP (the North American Numbering Plan) for area codes. Performance Monitoring adds View Performance Feature for Global PM Performance monitoring is greatly expanded for this release. When you right-click a switch, a new menu item titled View Performance displays along with the other switch related menu items. If you select view performance, you can select a switch-wide, or global, function that you want to view performance on, plus you can initialize the registers to start with clean memory. Performance monitoring of functions that are not global, or are unique to an IOM, a trunk group, a trunk, an interface or other non-global object that can be monitored for performance are still available from their respective interface. Graphical Representation of Performance Monitoring is Available Call statistics, switch resources and trunk group PM (Performance Monitoring) information can be graphed using a new tool for historical PM data. The data that can be graphed shows on an X/Y coordinates graph with a selectable vertical resolution and selectable sampling frequencies. 3GPP Performance Monitoring Support The Lucent Gateway Platform Element Management System (EMS) provides performance measurement reports in 3GPP XML format for five (5) performance measurement parameters. The following table provides the list of performance monitoring commands associated with 3GPP performance measurements and identifies the Lucent Gateway Platform switch types the commands apply to. Lucent Technologies, Inc. 15 of 36

16 Software Release Notice PlexView Element Management System Performance Monitoring (PM) Commands Table 1. 3GPP Performance Measurement Reports Lucent Signaling Gateway Lucent Network Controller PLATFORM RESOURCES Lucent Network Gateway Lucent Compact Switch EMS Value- Add Compute Module or System Processor CPU Performance Monitoring (Resource RSRC) Y (SP) Y (SP+CM) Y (SP) Y (SP) 3GPP CALL STATISTICS Call Control (CC) Performance Monitoring N Y N Y 3GPP Release Cause (RC) Performance Monitoring Y Y N Y 3GPP GMSC Performance Monitoring N Y N Y 3GPP MEGACO (H.248) MEGACO Message Retrieval (from MGC) N Y N Y 3GPP The EMS collects the 3GPP performance measurements every five minutes. At every thirty-minute interval, the EMS aggregates the data and generates XML reports. EMS Related Traps now include Alarm Ids The EMS now has its own MIB and supports specific alarms ids is the range reserved for the EMS. Of this range: are for EM related alarms reserved for BTS alarms When forward as SNMP traps, you can now filter on the number range to see only traps specific to the EMS or BTS. 16 of 36 Lucent Technologies, Inc.

17 PlexView Element Management System Software Release Notice 7. Configurable Properties Customizable Server Properties PlexView provides two editable properties files to customize PlexView s appearance and operation. Both files are located in the 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 PlexView server for the changes to take effect. Each new version of PlexView 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. New Properties for EMS The following new properties apply for this release. Northbound SNMP Trap Properties These properties control the periodicity of the EMS Keep Alive trap and the format of traps forwarded northbound from EMS. #Specify the interval at which the EM Keep alive trap is sent. A value of 0 turns the heartbeat trap off #emkeepaliveinterval=30 #EMS/Plexus alarms/events con be configured to be forwarded as SNMPv1 or SNMPv2 traps #traptype=2 New Properties for EMS The relevance of these properties depends on the release of switch software being managed. VPS Status Poll Property When this property in the plexcore.properties file uncommented, enabling it, the EMS will issue the RTRV-STATUS-VPS command to poll the switch for the VPS card status. If the retrieved VOIP Network Connection is OOS, an EMS alarm (trouble Id 9015) is raised and a trap will be issued. The alarm will be cleared when the Network Connection state changes to IS. To enable the VPS status poll property, uncomment and modify the following lines in the plexcore.properties file: Lucent Technologies, Inc. 17 of 36

18 Software Release Notice PlexView Element Management System # * Rules: # * This poll is issued every poll_interval seconds # * # * poll_vps_status # * Type: boolean # * Range: true/false # * Default: true # * # */ #poll_vps_status=true The ISUP CIC Range is a Configurable Property Starting for switch release , the default ISUP ANSI CIC range is The default ISUP ITU CIC range is To change the ranges, or change the minimum CIC value to 0, uncomment and modify the following lines in the plexview.properties file: #isupmincicval=1 #isupmaxcicval=16382 #isupitumaxval=4095 These are the default values, even though the lines are commented out in the script. To change the default, uncomment the line and change the Val number. INIT-SYS Permission Level is a Property By default, operator privilege levels of SW and SA can run an INIT-SYS command to reboot a switch. The recommended security level is SA only. To change the property to the recommended level, uncomment the following line in the plexview.properties file: #initsysprivlevel=sa Password Complexity Property The standard password complexity algorithm is the EMS is configurable if you can write java programs. Java Program Instructions: 1. Modify provided class template to have required complexity check. vi PasswordVerifyFunction.java 2. Compile modified class. javac PasswordVerifyFunction.java 3. Unit test compiled class. 18 of 36 Lucent Technologies, Inc.

19 PlexView Element Management System Software Release Notice /opt/plexview/server/currrel/lumos/jre/bin/java -classpath. PasswordVerifyFunction arg_1_uname arg_2_newpasswd arg_3_oldpasswd 4. Place compiled class in class-path of EMS Server. cp PasswordVerifyFunction.class /opt/plexview/server/currrel/lumos 5. Set the property to use custom password complexity check. cd /opt/plexview/server/properties vi plexview.properties ispasswordcomplexityrulesenabled=true 6. Restart EMS Server. cd /opt/plexview/server/currrel./server.sh stop./server.sh start To activate the class file, uncomment the following lines in plexview.properties: The header to find the lines reads # Properties for DTAG support user admin enhancements # req-id 5130 & 5131 The lines to uncomment are: #ischangeinitialpasswordenabled=false #ispasswordcomplexityrulesenabled=false The first line, if uncommented and changed to true, requires the initial password to be changed. The second line, if uncommented and changed to true, tells the EMS to look for the previously provisioned class template on password complexity. If you do write a java program and follow these instructions and your program does not work, the failure is logged and the EMS defaults to the standard password algorithm. Receiving SNMP Traps Property The EMS can receive SNMP traps from many devices that report trap information to the EMS. All traps from all devices are received port on the EMS. In the plexcore.properties file, uncomment the SnmpTrapRcvrOn=true lines relevant to the device you want to receive traps from. # The common port on which EM will receive traps for all BTS/NGFS/LCM/AC/TAOS #snmptraprcvrport=14002 Lucent Technologies, Inc. 19 of 36

20 Software Release Notice PlexView Element Management System # To enable EM receive traps from BillingServer( BTS) #btssnmptraprcvron=true # Specify the BTS instance's IPAddresses that EM will monitor as a comma separated list #btssnmptraprcvragentlist=<ip address list in xxx.xxx.xxx.xxx format> # Specify the btsheartbeatlosstimeout in seconds #btsheartbeatlosstimeout=60 # To enable EM receive traps from AudioCodes (IPM2K) #acsnmptraprcvron=true # Specify the AC instance's IPAddresses that EM will monitor as a comma separated list #acsnmptraprcvragentlist=<ip address list in xxx.xxx.xxx.xxx format> # To enable EM receive traps from LCM #lcmsnmptraprcvron=true # To enable EM receive traps from TAOS #taossnmptraprcvron=true # To enable EM receive traps from the Feature Server #ngfssnmptraprcvron=true Feature Server 5000 Status Polling Interval Property The Feature Server 5000 (NGFS) has a default status poll cycle of 60 seconds, or one minute. A status poll gets the status of the NGFS services. Uncomment and change the numeric value in seconds to change the periodicity of this status poll. #ngfs_poll_interval=60 New Properties for EMS 9.7 and 9.8 SNMP Traps can be Forwarded to Multiple SNMP Managers The plexcore.properties template has been updated to support sending SNMP Valueadded traps to multiple SNMP managers. In the plexcore.properties.template, near the bottom, there is a new property called trapdestinationlist. 20 of 36 Lucent Technologies, Inc.

21 PlexView Element Management System Software Release Notice The format of the entities to be filled in is t takes values in this format <host1:port1:community1,host2:port2:community2 An example of trap destination list line sent to two managers is: trapdestinationlist=spyglass:162:public,juniper:162:public. SSL Data Encryption Between Client and Server SSL Encryption of data between client and server is now available with PlexView. By default, encryption is disabled. To enable encryption, create or edit the file using the following path: /opt/plexview/server/currrel/lumos/ext/auto-service.cfg Edit it to add: sslcommunicationon=true The data encryption level is preset and cannot be adjusted. On servers or clients residing on older computers, performance may be slower than before you enabled encryption. Forwarding Alarms and Events as SNMP Traps Alarms and events can be forwarded to northbound SNMP management systems as SNMP traps. Alarms and events are converted to traps and forwarded by PlexView. For switches running <3.8 software, only generic traps can be sent. For switches running >3.8 software, generic or specific traps can be sent. Perform the following steps to enable trap forwarding. 1. Go to the server from a UNIX command line and change to the following directory: cd /opt/plexview/server/currrel/lumos/ext 2. Auto-snmptraps.jar is a hidden file. Copy it and change its attributes by the copy so the file is not hidden as follows: cp.auto-snmptraps.jar auto-snmptraps.jar 3. Change your directory to: /opt/plexview/server/properties 4. Open plexcore.properties and uncomment the following properties or copy the following lines to append the file: enabletrapforward=true trapdestinationhost=plexview1 trapdestinationport=162 trapcommunitystring=public Lucent Technologies, Inc. 21 of 36

22 Software Release Notice PlexView Element Management System By default, the SNMP proxy sends generic traps when you enable forwarding. To send specific SNMP traps from switches running >3.8 software, set the following property by adding this line to the file: trapmode=specific You can filter traps that will get forwarded. The trapfilteraccountname parameter is only valid starting with EMS 9.6. It uses the user account s fault session filter and event notification filter and forwards faults and events accordingly. Add the following property to enable this feature: trapfilteraccountname=(the user account name) 5. Save the file. 6. Shut down and restart the server. Northbound SNMP managers should now see traps forwarded by the proxy agent. 22 of 36 Lucent Technologies, Inc.

23 PlexView Element Management System Software Release Notice 8. Restrictions and Special Considerations This version of EMS software has been validated against and only supports Lucent Gateway Platform Switches running switch releases: 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. This version of EMS software has been validated against and only supports Lucent Control Platform applications running the following software versions: Feature Server 5000 Release 1.1 This version of EMS software has been validated against and only supports Lucent Communication Manager running the following software versions: Lucent Communications Manager Release This version of EMS software does not support running multiple instances of the PlexView Server. Only one instance of the Server should be running was the last EMS software release to be regression tested against switches running software at a release lower than release To migrate to later versions of EMS, you must have prior Lucent Technologies, Inc. engineering approval. SSH encryption Re-establishment after Switch Software Upgrades The SSH encryption link between the EMS and a managed switch will not operate after the switch software has been upgraded. To re-establish an SSH connection, the entries in the known_hosts file must be reestablished. Reference the section titled SSH Data Encryption Re-establishment After a Switch Software Upgrade in the chapter titled, Server Administration and Maintenance for the procedure on how to update the known_hosts file. Init-Sys Switch Erroneous Message A race condition exists when EMS performs INIT-SYS, where the command sometimes causes a "WRITE FAILED" error message to appear at the client. This race is caused by the switch closing down the management socket unexpectedly in response to the INIT- SYS command. In this particular case, the error can be ignored. In other cases, the error may be an important indication of a problem with the connectivity between the EMS and switch. Lucent Technologies, Inc. 23 of 36

24 Software Release Notice PlexView Element Management System Synchronize Switches after Upgrading Switch Software Always synchronize a switch after the switch has undergone a software upgrade, whether in a standard or a high-availability (VERITAS) environment. Perform this step regardless of whether the EMS informs you that the switch is unsynchronized. Connecting PlexView Clients and the Server through Firewalls and with NATs The EMS uses Java Remote Method Invocation (RMI) to establish communications paths between the EMS clients and the EMS server. To configure RMI to work with all clients, including clients outside a firewall, you must use the hostname of the EMS server and not localhost or the IP address in the Server Name field of the install/upgrade setup dialog, update the DNS to resolve the hostname, and use the EMS server s hostname in client setups. This is fully documented in the Lucent Control and Gateway Platform (PlexView) EMS Server Software Installation Guide. Unmanaging and Remanaging a Switch To unmanage or manage a switch, right click the switch and select Modify. In the Modify Switch window, select the drop down window next to the Managed parameter and select YES to manage or NO to unmanage. Click the Ok button at the bottom of the screen. When you unmanage a switch, the EMS drops its switch connection. The switch will queue all TL1 changes that are made via the craft while the switch is unmanaged from the EMS. When you manage the switch, the queue will automatically be forwarded to the EMS making synchronization unnecessary unless the EMS fails to keep up with the playback (i.e., a queue overrun occurs). A queue overrun should only occur if a large volume of changes have been made via the craft while the EMS was disconnected. If the queue is overrun, the EMS will display SYNC REQUIRED in the EM Status field of the Status panel. Synchronizing the switch is only required if the EMS tells you SYNC REQUIRED in the EM Status field in the status pane. To synchronize the switch, right click the switch and select Synchronize EM. At the end of the synchronization, the switch will again be managed. Always synchronize a switch after the switch has undergone a software upgrade, whether in a standard or a high-availability (VERITAS) environment. Perform this step regardless of whether the EMS informs you that the switch is unsynchronized. Deleting Switches Also Deletes All Related Database Entries Deleting a switch requires enough time for the EMS to eliminate every trace of the deleted switch from its databases. To delete a switch, unmanage it, and then delete it. Lucent recommends that you delete a switch from the navigator s Lucent pane and not from the status pane. The Lucent pane is the bottom window in the navigator that shows the configurable nodes. Right-click on the switch name and select Delete. When you use the Lucent pane, the delete monitor displays deletion progress. After you initiate a switch delete, allow the EMS enough time to complete deletion before performing any other operations. Check the status bar at the bottom of the delete monitor for completion. 24 of 36 Lucent Technologies, Inc.

25 PlexView Element Management System Software Release Notice Note: Deleting a switch does not delete alarm, event or log histories of that switch or remove persistent PM data that has been collected for that switch. NAL (Node Access List) Changes During Upgrades A Node Access List (NAL) provides fine-grained access control allowing the PlexView 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 PlexView navigator tree and to save the NAL list to the PlexView 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 LGP switches. Because new releases of PlexView introduce new navigator nodes, the system administrator must review and modify the NALs each time a PlexView 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 PlexView software, the new version of PlexView software, and the versions of switch software being managed. The list below summarizes the navigator node changes that have occurred between the release of PlexView and this version and are applicable to the management of 6.x.x.x, 5.x.x.x, and 3.11.x.x LGP network elements. There are some new NALs added for >9.9 EMS software managing 5.1.x.x switches There are no new NALs for 3.11.x.x switches. For 5.x and 6.x switches: SIP>SIP Route SIP>TgMapAddr SIP>DNS System SS7>Intelligent Network Services>Service Access Point Profile IMT>ISUP VE Profiles IMT>ISUP PL Profiles IMT>SIP Profiles IMT>Protocol Release Profiles VOIP>VOP System VOIP>CODEC Profile Mobile Systems>CAMEL Network for GMSC Lucent Technologies, Inc. 25 of 36

26 Software Release Notice PlexView Element Management System Mobile Systems>VMS Prefixes System Services>IP Filter Rules System Services>PFP Profiles 26 of 36 Lucent Technologies, Inc.

27 PlexView Element Management System Software Release Notice 9. Installation Update The Lucent Control and Gateway Platform Element Management System (PlexView EMS) Installation Guide for the Lucent Gateway Platform Part Number R has been updated to add an appendix for server upgrades, downgrades, and restoral. Lucent Technologies, Inc. 27 of 36

28 Software Release Notice PlexView Element Management System 10. Known and Fixed Anomalies The following table provides a list of known anomalies within the PlexView EMS software managing Lucent Gateway Platform switches. ID Number TIL (if applies) Priority Summary of Known Anomalies P2 Retrieving B Channels of a fully loaded ISDN NFAS or NFAS Backups may time out. Workaround: Retry Retrieval P2 SG_MGC_MG. Add SS7 Link. Port chooser shows ports with IUA links as available. Workaround: Expand IUA Links prior to provisioning SS7 Links and ensure that there are no conflicts P2 Ranged Edits of SS7 Trunks may time out: Workaround: Retry edit P1 EMS error resetting 8064 SS7 CICs. Workaround: Retry. Keepalive (heartbeat) issue P2 After re-initialization of EMS all elements show as disconnected. Workaround: Cannot reproduce P1 Unable to access the EMS. Workaround: Cannot reproduce P3 Resource Monitoring. Where applicable options are CPU A,B,C and D the Histories or More Histories tab will not allow selection of C and D. Workaround: Select C or D in Data tab and then select either History tab P2 TL1 ED-GMSC-GSMSYS changes are not reflected in the EMS. Workaround: Use EMS to update GMSC-GSMSYS P2 When adding MG CAS Profiles the EMS defaults vary from the TL1 defaults. Workaround: Edit the Tone Duration, Pause Duration and Outpulse Delay to reflect desired values. TL1 Defaults: Tone Duration=65 Pause Duration=65 Outpulse Delay= of 36 Lucent Technologies, Inc.

29 PlexView Element Management System Software Release Notice ID Number TIL (if applies) Priority Summary of Known Anomalies P2 Modify/View MGC Point Codes show invalid Point Code Format in Select Point Code Format field. Workaround: This display is the default Format used when adding MGC Point Codes. It is used to return only desired variants for selection. It is only applicable to the Add dialogue and can be ignored on the Modify/View dialogue P2 Occasionally when performing and INIT-SYS from the EMS a write failed error will be thrown. Workaround: The error message is invalid. Wait for the EM server to reconnect to the switch P2 EMS backout procedure required. Workaround: None P2 EMS Add User allows special characters for username and password. Oracle will reject them but the EMS user will be created and there is no way to delete it. Workaround: When adding users only use alphanumeric characters or the _ for Username and Password P1 Unable to place ENET Port IS using EMS. Workaround When a switch undergoes a software upgrade, always synchronize it from the EMS, regardless of whether the Synch Required flag is set or not P3 After upgrade elements show as disconnected. Workaround: None. Lucent Technologies, Inc. 29 of 36