Avaya Integrated Management Release 4.0 Fault and Performance Manager Service Pack 8

Transcription

1 Avaya Integrated Management Release 4.0 Fault and Performance Manager Service Pack 8 Service Pack Date: April 2009 Files: mfpm-4.0-sp bin; Self-extract file; Size: Purpose of the Service Pack The Avaya Integrated Management Release 4.0 Fault and Performance Manager (FPM) service packs are cumulative and include the fixes in the current service pack and any previous service pack to the current release. The fixes for this service pack are listed below. Avaya Fault and Performance Manager 4.0 Service Pack 8 The Exception report, after a scheduled alarm collection, no longer displays an acknowledged Restart alarm that occurred owing to Daylight Saving rules. FPM now alters trap parameters according to filter settings so that traps are forwarded to third party NMSs with modified severity levels. The Refresh Alarm procedure no longer takes excessive time for completion. FPM displays active alarms, even unacknowledged ones, properly in the alarm list. FPM displays the configured number of records in a report, even when the number exceeds FPM users can now attach GIF files to reports sent through s. Attendant Group reports in FPM now display peak information for the attendant position. Avaya Fault and Performance Manager 4.0 Service Pack 7 Launching GUI multiple times will not hang LvlUtil. Route-pattern and sig-group data gets collected without exceptions on primary and secondary. Alarm counter gets updated as soon as fpm receive trap. Trunk group report always shows the updated GOS value. Acknowledged warning alarms do not show up in the exception report. Modifications to IP Trunk Map displays that make them more readable. The clarity in the display becomes apparent only after the users run config collections on the CMs. Users can do this manually or can wait for the scheduled config collection to run and complete itself. New feature provided which will show administrator defined default filters when custom value radio button selected instead showing fpm default filters. Collection of Ip address is successful for G3V9 voice system. Avaya Fault and Performance Manager 4.0 Service Pack 6 Log messages are enhanced to indicate the failures in sending s from FPM server Logs of only two service pack installs are maintained rather than maintaining large log for all the service packs, older one by name mfpm-patch-rpm.log.old. The error message popup for failed connections to voice systems while applying alarm filters is modified to indicate the name of the voice system as well The severity is set to None, while creating a new filter of type Error A new script by name BackupRestoreFPM is available in /opt/avaya/mfpm/bin which can be scheduled to run at fixed intervals using Linux s crontab utility. This is supposed to cleanup the database and reduce the size of the database. E.g to schedule it at 2 am everyday, open Linux terminal and type the following: crontab e 00 2 * * * * /opt/avaya/mfpm/bin/backuprestorefpm >>/var/avaya/mfpm/dbbkup/bkprestorelog 2>&1

2 Then save the changes. SSG traps are forwarded as SNMP V2 traps to other NMS The error message popup is modified to display the proper cause of failure in case of wrong SSH Key used for authenticating with CM If secondary server is not running or unreachable then, proper error message is popped rather than giving a fatal error message View as HTML button is removed from Exceptions window Performance of Trap forwarding services are enhanced by modifying the query for fetching PIDs FPM blocks the user after specified number of failed logins in IMD. A new tool for checking connection to administered Voice Systems has been added to /opt/avaya/mfpm/bin directory by name CheckConn Refresh TCP Connection feature is working. Earlier it used to show no data available for all the Voice Systems. FPM gui launches from server side after installing the service pack The properties for trkex can be set to any desired value in PMProps file Collection doesnot fail for correct alternate IP address when the original IP address is wrong Collection of Definity restarts is populating the FPM database correctly The default value of ossi read timeout has been increased to 5 minutes such that collections for TgData, Isdn-Tg Data on large switch doesnot fail The trap OIDs for Voice adjuncts are correctly forwarded The retry information is removed from the Connection failure information from CM GetCount tool shows proper exception/error type name instead of some arbitrary numver when executed Avaya Fault and Performance Manager 4.0 Service Pack 5 Performance: Proccesor Occupancy report doesnot show futuristic dates Audit Switch process timesout properly if there is ssh problem with the voice system FPM features trap reception from ASG Defender FPM features trap reception from SEAR Mediagateway collection is sped up due to enhanced snmp timeout during the collection Java console doesnot show irrelevant log messages during login process DIG-IP-ST alarms are properly processed by FPM and shown as DIG-IP-S alarms with troubleshooter light bulb against the record in exceptions table Reports scheduled from secondary FPM servers are properly mailed with attachments A new property 'MFPM.systemGrpView' can be added to PMProps file to configure the number of voice elements and adjuncts to be shown in the graphical view. If this number exceeds in reality, then user will be presented with a message in the graphical view. The figures 49 and 50 are available in DIG-LINE helper Two new tools GetPerfCounts and FpmAckAll available for Tech Support No bash errors are displayed while running mfpmconfig script Trap service binds properly with collector service after collector service is restarted Collection task handles date type returns and hence no wrong data type error is popped up in the GUI. Running mfpmconfig script doesnot change the values for following properties: SNMPRetries, snmptimeout, MFPM.dbTransaction, MFPM.defaultPageWidth, MFPM.defaultPageHeight, MFPM.ConnTimeoutSeconds, MFPM.connectionStatusTimeout, MFPM.dataGetterGeneralTimeout, MFPM.systemStatusTimeout, MFPM.DefSharedMsgLogVersionLimit. Snapshot and Restore snapshot does validations for availability of snapshot files etc. And if there are any discrepancies then the Snapshot and Restore snapshot processes are exited without changing the system or database status. Nightly collections are made faster by enhancing the removal of old performance data process

3 Null pointer exceptions are handeled for Alarm collection on voice systems with large number of media gateways Parse errors observed while collecting restarts are handeled and restarts get collected properly ESS icons are shown properly in ESS Cluster view Performance Announcement reports can be created in a newly installed FPM server Test traps from SEAR are processed Expired logins are blocked by FPM and a new button for Change Password is available in the login screen. Running `mfpmconfig show` on secondary server shows the information for secondary properly Correct icon for Conversant is shown in the gui Refresh Alarms/Errors doesnot fill MsgLogs with irrelevant messages like "resource type<mo-name>" Avaya Fault and Performance Manager 4.0 Service Pack 4 Multiple traps are not sent if there are multiple filters set for the same MFPMgui command displays FPM gui on those hardware platforms where it was not working earlier Mod Msg Traps from MAS are not being ignored anymore Assist capability for Traps has been provided TG GOS change shows up in TG Reports CollectMediaGateways doesnpt try GETS of Tool available to allow for removal of types of perf data Warning trap can be added to system wide defaults for filters Scheduled reports are no more showing up empty FPM Service Pack install error is removed CollectCpServers will not go to wrong IP for collection Custom TG GOS field edit is visible Incoming TG shows default value as 0% for outgoing calls blocked Service State/Available show correct value in LSP clusters Restart collection doesnot fail with parse error CollWorkAll doesnot truncate the log files FixCounts -a wipes out EWatch.log and recreate them at the end Change to TimeScale on one report will not change timescale of all reports in the UI RemoveOldExceptions runs faster than before and will not block collection Traps from FPM to NMS are formatted properly Avaya Fault and Performance Manager 4.0 Service Pack 3 Supports enhanced filtering based on description. Changes default from Hourly Collection to Daily Collection for CAC/BL status, Clan Ethernet, and Clan PPP. Resolves the issue where the wrong report was being deleted from the report manager after the list of reports had been sorted. Resolves the problem where old exceptions were not being cleaned up properly by the nightly audits. Removes old exceptions successfully. Allows user to acknowledge exceptions occurring due to failed ing of reports. Resolves the issue of Alarm collection failing after LSP/ESS failover. Increased the default timeout to 30 seconds to allow FPM to successfully log into Voice Systems where network delays are encountered. Resolves the issue of IE hanging when closing the FPM applet. Allows the cleared alarms to be visible in FPM. Resolves the issue of missing entries in the DCS group list.

4 Resolves the issue of reports getting proper failure exception. If the fails from both the primary and secondary server configured in IMD, the exception is logged as minor. If fails with primary, but if it is successful with secondary, the exception is logged as a warning with proper description. Supports MAS/MSS on Modular Messaging Helper documentation links for exceptions. Resolves the issue of scheduled entry getting deleted when the "X" button is selected on the Yes/No dialog (confirmation dialog for deletion). New option to MFPMdb: MFPMdb GetDefties lastcoll bash command shows the last collection time for each Voice System. Improved the speed of FixCounts cleanlob. Allows the user to view details for Boards from graphical view and does not throw the number format exception. Avaya Fault and Performance Manager 4.0 Update 2 The Voice system details screen now shows a new node called Server for server status information. Provides successful login through SSH. Introduces SNMP Trap Generation test tool for Tier III/Cust use. MGStacks now show G700 Media Gateways only. The new Media Gateways node introduced in the voice system details screen show non-g700 media gateways. Resolves the Out of Memory errors when running Trunk Group report. MG Stacks correctly show stack number instead of blank / IP address. IPT groups show near-end and far-end link information for S8300, which is IP based. output from performance threshold violation shows proper description. Default Systems are not added in the systems groups if there is no node below it. G250/G450 gateways show appropriate values for suffix/vintage/stack information. Allows FPM users to create new reports from the Report Manager. Correctly shows Static Occupancy on the detailed screen. Resolves the issue of FixCounts taking a long time and restoring alarm filters. Supports creating Alarm Filters for H323-SGR, H323-SGRP, PRI-CDR, and SEC-CDR mo types. Supports FPM launching with 1.5 family of JREs. Avaya Fault and Performance Manager 4.0 Update 1 Resolves the issue of old alarms returning after they were acknowledged in Fault and Performance Manager. Resolves the issue of incomplete trunk information from the table view, including: trunk group numbers, far-end node names, near-end node names, far-end defty names, and signaling groups. Resolves the issue relating to no graphic view and graphic view not coming when selecting the Graphic View button for an S8720XL server. Resolves the issue relating to Defties showing inactive during collection when moving managed node to any custom created systems group. Resolves the issue with exception counts and adjuncts. Resolves the MFPM.showAllExceptions issue with Assist and Troubleshooter. When the showallexceptions is set to true, the list of inactive alarms are not displayed. When the showallexceptions is set to false, the active alarms and exceptions are displayed properly. Correctly displays the media gateway model number. Also renamed the HWTYPE column to MODEL. Resolves the issue with CollWork and running collections. Resolves the formatting issues by displaying the operator and value fields separately and removing the oids from the Description. Changed the error level to trace level to provide meaningful message logs. Resolves the Close the browser issue when closing the FPM GUI and the browser windows.

5 Service Pack Procedure Please read the procedure below before you download the service pack. During the installation, the script checks the product version and service packs that are currently installed. The script prompts you to apply the service pack. At the end of the installation, the last question gives you the option to remove the service pack you just installed. Installing mfpm-4.0-sp bin 1. Save the FPM update file to your computer. Follow the directions to save the update file to a directory. Make a note of the location. 2. Optional. If you saved the update file on your Windows computer, then FTP the update file (in binary mode) to the Linux server where the product resides. 3. Log in as root on the Linux server. 4. Open a terminal window. Enter the cd command to go to the directory where you saved the update file. 5. At the command prompt, start the install script. Type./mfpm-4.0-SP bin and press Enter. Then answer the question prompts to install the service pack. The last question gives you the option to remove the service pack you just installed. 6. At the end of the installation, you may need to press Ctrl-C or Delete to return to the command line.