EMS Software Release Notice - Nokia Networks Development Manager 1 888-LTINFO6 (domestic)...

PlexView Element Management System (EMS) Software Release Notice

Part Number 255-400-402R9.7.0.0 Issue 1, July 26, 2005

Software Version 9.7.0.0

Copyright 2005 Lucent Technologies All Rights Reserved

Copyright 2005 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 1 888-LTINFO6 (domestic) 1-317-322-6848 (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 255-400-004R9.7.0.0 Support Technical support Please contact your Lucent Technologies Local Customer Support Team (LCS) for technical questions about the information in this document. Information product support To comment on this information product online, go to http://www.lucent-info.com/comments or email your comments to [email protected].

PlexView Element Management System Software Release Notice

1. Software Release Notice Table of Contents Release 9.7.0.0

1. Software Release Notice Table of Contents ............................................................... 3 2. Release Abstract.......................................................................................................... 6

Software .......................................................................................................................... 6 3. System Requirements.................................................................................................. 7

PlexView Client Requirements....................................................................................... 7 PlexView Server Requirements ...................................................................................... 7 Oracle Database Requirements..................................................................................... 8 Solaris Version/Patch Requirements............................................................................... 8

4. New Features .............................................................................................................. 9 Distributed Switches Are Now Supported...................................................................... 9 Available Switch Nodes Vary By Chassis Type and Switch Software Release............. 9 SS7 Point Codes and Proxy Provisioning is Updated................................................... 10 New ISUP Profiles support International Switch Use .................................................. 10 MEGACO Defines Distributed Connectivity and Topology........................................ 10 IUA Carries Communication Between Signaling Gateway and Network Controller .. 10 The MG CAS Profile is Under System Services .......................................................... 11 Number Administration Supports International Numbering Plans............................... 11 Performance Monitoring adds View Performance Feature for Global PM .................. 11 Graphical Representation of Performance Monitoring is Available............................. 11 3GPP Performance Monitoring Support....................................................................... 11 Trunk Group Provisioning and Trunk Monitoring are Expanded ................................ 12 ISUP Point Codes are Variant Sensitive....................................................................... 12 Distributed Lucent Network Gateways Display Virtual Inventories............................ 12 New Features for Switch Release 3.11 Only ................................................................ 12 B911 Ring Back............................................................................................................ 12 Hot Line ........................................................................................................................ 13 Warm Line .................................................................................................................... 13 Home Intercom ............................................................................................................. 13 Busy Line Verification and Interruption....................................................................... 13 SIP Refer to Flash Hook ............................................................................................... 13 Service Access Codes Updated..................................................................................... 13 Canadian Call Name Delivery Added........................................................................... 14

5. Configurable Properties ............................................................................................ 15 SNMP Traps can be Forwarded to Multiple SNMP Managers .................................... 15 EMS Related Traps now include Alarm Ids ................................................................. 15 Customizable Server Properties.................................................................................... 15 SSL Data Encryption Between Client and Server ........................................................ 15 BTS SNMP Traps Display on PlexView...................................................................... 16

Forwarding Alarms and Events as SNMP Traps ...................................................... 16 6. Restrictions and Special Considerations................................................................... 18

Connecting PlexView Clients and the Server through Firewalls and with NATs........ 18 Deleting Switches Also Deletes All Related Database Entries .................................... 18 NAL (Node Access List) Changes During Upgrades ................................................... 19

7. Known and Fixed Anomalies.................................................................................... 21

Lucent Technologies, Inc. 3 of 24

211918181816161515151515141313131313131212121212111111111110101010

99988777663

Software Release Notice PlexView Element Management System

8. Technical Support ..................................................................................................... 24

4 of 24 Lucent Technologies, Inc.

24


2. Release Abstract This Software Release Notice (SRN) for version 9.7.0.0 of the PlexView® Element Management System (EMS) software describes the system architecture and features provided by this product. The PlexView EMS software allows you to perform element and network management functions on your Lucent Gateway Platform Switches. It provides the functionality to configure, monitor, and manage faults on multiple switches simultaneously.

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

Software This release of the PlexView EMS software consists of the following software:

PlexView Client Release, Version 9.7.0.0 PlexView Server Release, Version 9.7.0.0 PlexView TL1 Gateway Release, Version 9.7.0.0

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 Section 6, Restrictions and Special Considerations.



3. System Requirements This version of PlexView software can manage a network of many Lucent Gateway Platform Switches with many simultaneously connected clients. The switches and clients are both connected to a single PlexView 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)

The minimum recommended system requirements for this version of PlexView software are provided in the following sections.

PlexView Client Requirements The PlexView Client software is written in Java and runs on Sun/Solaris, Windowsxp, Windows NT or Windows 2000 platforms.

The minimum recommended configuration for a Windows-based PlexView 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 PlexView Client software 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 PlexView 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.

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.

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.0) and the Oracle 8.1.7.4 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.

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.



4. New Features This section summarizes the new features provided in this release of PlexView EMS software.

The following new features are for switch release 5.1 only.

Distributed Switches Are Now Supported Starting with EMS release 9.7.0.0, you can manage Lucent Gateway Platform switches set up in a distributed environment as follows:

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.

Available Switch Nodes Vary By Chassis Type and Switch Software Release Prior to Release 9.7 of EMS software, when you highlight 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.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 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

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.

The EMS allows you to select the physical facility and then calculates the MEGACO Termination Id sent to the switch.

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



Table 1. 3GPP Performance Measurement Reports

Performance Monitoring (PM) Commands

Lucent Signaling Gateway

Lucent Network Controller

Lucent Network Gateway

Lucent Compact Switch

EMS Value-Add

PLATFORM RESOURCES

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.

Trunk Group Provisioning and Trunk Monitoring are Expanded A trunk group summary dialog will show statistics on up to 100 trunks at a time.

Trunk group filtering is enhanced to allow sorting by trunk state.

Trunk Groups can now be provisioned at up to 672 trunks (a full DS3) at a time by modifying the properties file. Additionally, you can provision up to 93 trunks simultaneously on an E1 and up to 24 on a T1 simultaneously.

ISUP Point Codes are Variant Sensitive When provisioning trunk groups, the business logic for OPC (Originating Point Code) – DPC (Destination Point Code) formats vary based on the trunk group variant.

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

Having virtual inventories keeps distributed system inventories consistent in appearance with integrated Lucent Compact Switch inventories.

New Features for Switch Release 3.11 Only

B911 Ring Back 911 service now supports 911 ring back for CAS calls. When a 911 call is placed and then disconnected, a PSAP (Public Service Answering Point) attendant can call the



subscriber back. The Lucent Compact Switch in this application serves as an EO (End Office) or local tandem for 9-1-1- calls and callbacks. A new variable in IMT>CAS Profiles under the Calling Model titled B911_TRUNK replaces 911_Trunk. When B911_TRUNK is selected another field titled Originator On-hook Signal can be set.

Hot Line Hot line is a new per-subscriber feature that dedicates a line between two phones. This PLAR (Private Line Automated Ringdown) service directly connects two phones with an off-hook signal. If the far-end is busy, the caller gets a busy signal. Hot Line is under Subscriber Database>Subscriber>Services, and there’s more under the Subscriber>Hot/Warm Line tab.

Warm Line Warm line is a new per-subscriber feature that dedicates a line between two phones after a provisionable warm line timer expires. If the subscriber starts dialing digits prior to warm line timer expiration, then the call terminates normally. Warm Line is under Subscriber Database>Subscriber>Services, and there’s more under the Subscriber>Hot/Warm Line tab.

Home Intercom Home Intercom (HI), is a new feature that allows a subscriber to use any extension in their home or business to call the other extensions that are connected to the same line. The subscriber dials his/her own Directory Number (DN) and upon receiving a busy tone hangs up. The Lucent CS rings the subscriber back and they pick up. When one of the other extensions connected to the same line picks up, the two extensions are connected. The call terminates when both of the parties go back on-hook. Home Intercom is under the Subscriber Database>Subscriber>Services tab.

Busy Line Verification and Interruption The Busy Line Verification (BLV) feature allows an operator to determine if a specific subscriber number is off hook and whether voice conversation is actually taking place. The Busy Line Interrupt (BLI) feature provides the additional capability of interrupting the voice conversation to relay a message to the subscriber. BLV can be denied under Subscriber Database>Subscriber.

SIP Refer to Flash Hook This feature supports DTMF Release Link Trunking by sending a “Flash Hook” (wink) down the originating MF or DTMF CAS trunk, accompanied by the destination number signaled using DTMF. Upon receiving a SIP REFER, the call transfer is invoked via a Flash-Hook followed by DTMF digits. Provision this parameter per trunk group under IMT>SIP (or SIP-T) Trunk Groups>Session Info>Refer Replace Handling.

Service Access Codes Updated New service access codes support hot line, warm line, home intercom and BLV. Service access codes are under System Services>Service Access Codes.



Canadian Call Name Delivery Added For SS7 calls, Canadian CNAM no provides calling name delivery information in the SS7 IAM messages on outgoing trunks. The feature is now available under the IMT>ISUP Trunk Groups>Session Info tab. You can select whether the calling name should be part of the Generic Name (GN) parameter or part of the Party Information (PI) in the IAM message.



5. Configurable Properties

SNMP Traps can be Forwarded to Multiple SNMP Managers The plexcore.properties template has been updated to support sending SNMP Value-added traps to multiple SNMP managers. In the plexcore.properties.template, near the bottom, there is a new property called trapDestinationList.

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.

EMS Related Traps now include Alarm Ids The EMS now has its own MIB and supports specific alarms ids.

9000 - 10000 is the range reserved for the EMS.

Of this range:

• 9000 - 9800 are for EM related alarms • 9800 - 10000 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.

Customizable Server Properties PlexView provides two editable properties files to customize PlexView’s appearance and operation. Both files are located in the

{ROOT}/opt/PlexView/Server/Properties

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

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.

BTS SNMP Traps Display on PlexView The SNMP agent in PlexView accepts, receives and displays/logs SNMPv1 traps from the Billing and Traffic Server. SNMP traps retrieved from the BTS are converted to TL1 alarms and displayed by PlexView.

To enable the receipt and recognition of SNMPv1 traps from the BTS, edit the file using the following path. /opt/PlexView/Server/CurrRel/lumos/ext/auto-service.cfg

Edit it to add three lines as shown in the following example: btsSnmpTrapRcvrOn=true

btsSnmpTrapRcvrPort=14002

btsSnmpTrapRcvrAgentList=10.2.2.18,10.2.2.13,10.2.2.15 (three example IP addresses)

For the btsSnmpTrapRcvrAgentList, use the list of unique IP addresses with comma delimiters that work for your network. Once the trap receiver is on, the port is set, and the agent list is created, you should be able to receive and forward SNMP traps from the Billing and Traffic Server. Configure the SNMP agent in the BTS to send traps to the EMS’s btsSnmpTrapRcvrAgentList.

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’s built-in SNMP proxy agent. 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

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.



6. Restrictions and Special Considerations This version of PlexView software has been validated against and only supports Lucent Gateway Platform Switches running switch releases:

5.1.0.1 3.11.0.1 3.10.1.7 3.10.1.6 3.10.1.5 3.10.1.4 3.10.1.3 3.10.1.2 3.10.1.1 3.10.1.0

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 PlexView software does not support running multiple instances of the PlexView Server. Only one instance of the PlexView Server should be running.

9.6.3.1 was the last EMS software release to be regression tested against switches running software at a release lower than release 3.10. To migrate to later versions of EMS (10.0.0.0 or later), you must have prior Lucent Technologies, Inc. engineering approval.

Connecting PlexView Clients and the Server through Firewalls and with NATs The PlexView 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 PlexView EMS Server Software Installation Guide.

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.



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.

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 PlexView navigator node changes that have occurred between the release of PlexView 9.6.3.3 and this version and are applicable to the management of 3.11.x.x and 3.10.x.x software.

There are many new NALs added for >9.7 EMS software managing 5.1.x.x switches There are no new NALs for 3.11.x.x switches.

For 5.x switches:

• SIP>SIP System (v5.0) • SS7>SG Own Point Codes • SS7>SG Point Codes • SS7>SG ISUP Proxy • SS7>MGC Own Point Codes • SS7>MGC Point Codes • IMT>MGC CAS Profiles • IMT>ISUP ANSI Profiles • IMT>ISUP ITU Profiles • IMT>ISUP ITU Q767 Profiles • IMT>ISUP MEXICO Profiles • MEGACO-Everything under MEGACO is new • MEGACO Associations>SG System • MEGACO Associations>MGC System • MEGACO Associations>SG • MEGACO Associations>MG System



• MEGACO Associations>>SG MGC Association • MEGACO Associations>MGC SG Association • MEGACO Associations>MGC MG Association • MEGACO Associations>MG MGC Association • MEGACO>System • MEGACO>MGC Profile • • IUA – Everything under IUA is new • IUA>System • IUA>MGC MG • IUA>ASP Endpoint • IUA>ASP • IUA>AS • IUA>Link • System Services>MG CAS Profile • Number Administration>Area Code



7. Known and Fixed Anomalies The following table provides a list of known anomalies within the PlexView EMS software.

ID Number

Priority Summary

You must refresh the screen for rolled back ports or any object that changes state to display its updated state. Workaround: None.

Do not update or delete trunks if you have sorted them.

If you alter the sort order of trunks in the Configure Trunking dialogues and then send down a ranged update/delete, you may see undesirable results.

As an example, If you have trunk 1 and trunk 10 IS and trunk 2-9 OOS, you sort by status, and then do a ranged update while highlighting 1 and 10, you actually send a ranged update command to the switch for 1 through 10, regardless of the sort order. So 2-9 also get updated. Workaround: Only delete unsorted multiple trunks.

Roll Back of ISUP trunks

If you range delete ISUP trunks in an ISUP trunk group in Order Entry mode, then commit the order, and then attempt to roll back the committed order, PlexView will not be able to restore the committed order to its previous state for the range deleted ISUP trunks. All range deleted trunks will have the same configuration instead of the unique configurations they had prior to being range deleted. Workaround: None.

26378 P2 The EMS search tool needs to allow multi-key searches.

30561 P2 Backups of large switch databases will occasionally time out. Workaround: Modify BackupRestoreTimeOut= in plexcore.properties and reboot the EMS server

36791 P2 Area codes automatically added by adding a National NPA will not display in the navigator. Workaround: Resynchronize switch after adding National NPA.

37203 P2 SNMP User Passwords are not being populated properly after a resynchronization. Workaround: None

37311 P2 Retrieving B Channels of a fully loaded ISDN NFAS or NFAS Backups may time out. Workaround: Retry Retrieval.



ID Number

Priority Summary

37674 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 insure that there are no conflicts.

38345 P2 Ranged Edits of SS7 Trunks may time out: Workaround: Retry edit.

38485 P2 Modifications of pending orders never complete. Workaround: Delete and Reenter the order

38663 P3 Next/Previous filtering. When you reach the end of list using Next, Previous doesn't work. Workaround: Refresh

39427 P2 View/Modify SG Point Codes -> PM Stats shows incorrect data. Workaround: Retrieve using TL1.

39439 P2 SG ISUP Proxy added via TL1 does not display in the navigator. Workaround: Add by the EM or resynchronize switch after adding using TL1

39685 P2 Resource Monitoring continues polling after you close the dialogue. Workaround: reset the polling rate to 0 before closing the dialogue.



The following table provides a list of fixed anomalies within the PlexView EMS software.

ID Number

Priority Summary




8. Technical Support Lucent Worldwide Service Is available to assist you with any problems that you encounter with this release of PlexView software. To contact Lucent Worldwide Service, please call 866-582-3688 and select option 5.

EMS Software Release Notice - Nokia Networks Development Manager 1 888-LTINFO6 (domestic)...

Documents

Transcript of EMS Software Release Notice - Nokia Networks Development Manager 1 888-LTINFO6 (domestic)...