webnms framework :: release notes · webnms framework 5.2 :: release notes 2 zoho corp. release...

WebNMS Framework 5.2 :: Release Notes

1

Zoho Corp.

Table of Contents

RELEASE NOTES - INTRODUCTION ...................................................................... 2

WEBNMS FRAMEWORK 5.2 .................................................................................... 3

Release Notes for WebNMS Framework 5.2 ..................................................................... 3

Service Packs .................................................................................................................... 4

WebNMS Framework 5.2 - Service Pack 1 ..................................................................................... 4

WEBNMS FRAMEWORK 5.0 .................................................................................... 7

Release Notes for WebNMS Framework 5.0 ..................................................................... 7

Service Packs .................................................................................................................. 16

WebNMS Framework 5.0 - Service Pack 1 ................................................................................... 16


2

Zoho Corp.

Release Notes - Introduction This document is prepared to help the reader who looks for the specific information such as the New features in the current release, and the enhancements done over earlier releases.

• WebNMS Framework 5.2 Release Notes : It explains the new feature of release WebNMS Framework 5.2

• Service Pack 1 Release Notes : It explains the new features and enhancements made in SP1.

• WebNMS Framework 5.0 Release Notes : It explains the new features and enhancements of release WebNMS Framework 5.0

• Service Pack 1 Release Notes : It explains the new features, changes and bug fixes made in SP1.


3

Zoho Corp.

WebNMS Framework 5.2

Release Notes for WebNMS Framework 5.2

In WebNMS Framework 5.2, PostgreSQL has been bundled as the default database. The database version supported in WebNMS Framework 5.2 is PostgreSQL 9.0.1. The release comprises of the following:

• The new features and enhancements of release WebNMS Framework 5.0. Refer the WebNMS Framework 5.0 Release Notes for more details.

• The new features, changes and bug fixes made in WebNMS 5.0 SP1. Refer the Service Pack 1 Release Notes for more details.


4

Zoho Corp.

Service Packs

WebNMS Framework 5.2 - Service Pack 1

• Release Highlights

1. Framework Services

2. Java Client Framework

3. HTML Client Framework

4. Maps

5. Fault Management

6. Performance Management

7. Configuration Management

8. Eclipse

Release Highlights Enhancements

• The web client user interface has been completely redesigned with new aesthetics and layout with focus on usability.

• Attractive and intuitive map interface introduced in web client with new layouts and easy-to-use map toolbar.

• NETCONF protocol support added for configuration management.

• KPI reporting tool introduced with comprehensive reports.

• JDK support provided for JDK 1.7, and OpenJDK 6 versions.

• Browsers support provided for IE 9x and Firefox 17x and higher versions.

• Chrome browser is now officially supported.

Framework

Enhancement

• WebNMS can now be started in a floating Virtual IP in the failover setup.

Java Client Framework

Enhancements

• 3Dimensional and Force directed map layouts introduced in maps. Default implementation available at <WebNMS Home>/default_impl/map_layouts/ folder.


5

Zoho Corp.

• Easy-to-use filter functionality added to the map panel to facilitate map search.

• Highly intuitive and user-friendly configuration user interface provided for adding/modifying/deleting polling objects, polled data, and thresholds.

• Enhanced escalation policy interface provided for adding policies with complete details along with action items.

Top

Web Client Framework

Enhancements

• Web client now supports real-time updates for all managed device information, events, and alarms.

• Support provided for audio notification with facility to play MP3 / WAV file on receiving an alarm in the fault console.

• Trouble shooting alarms is made easier with actions such as Ping / TraceRoute the device which is the alarm source.

• Telnet or SSH directly to the device from the web client to trouble shoot any problems on the device.

• Tree nodes can now be associated to dashboard for easy viewing of module-wise metrics at a glance.

• New themes Gainsboro with white/gray combination, and NOC with black background introduced for more attractive user interfaces.

• Performance graphs and widgets made more attractive with enhanced graphs.

• Powerful map functionality introduced to perform all map operations from the web client interface. Functions such as re-arranging symbols, grouping, adding symbols and links, etc., can be performed with ease using the web client map toolbar.

Maps

Enhancements

• 3Dimensional and Force directed map layouts introduced in Java client maps. Refer to <WebNMS Home>/default_impl/map_layouts/help/MapLayouts.html for complete details.

• Maps can now be searched easily with the filter functionality in Java clients.

• Powerful interactive map interface introduced in web client with new layouts and easy-to-use map toolbar.


6

Zoho Corp.

Fault Management

Enhancements

• Send SMS action introduced in fault monitoring, with customization options in the Events Filters and Alert Filters UI.

• MP3 / WAV files support provided for audio alarm notification.

• Support introduced for Ping / TraceRoute the device, and Telnet / SSH directly to the device from the web client for effective troubleshooting of alarm source and devices respectively.

Performance

Enhancements

• KPI Reporting Tool introduced, with highly sophisticated KPI graphs and reports.

• Support provided for storing collected performance values of polleddatas in decimal format.

• Performance graphs viewing enhanced with attractive graphs.

Configuration

Enhancement

• NETCONF protocol support introduced for configuration management in Java and Web client.

Eclipse Plugin

Enhancements

• Eclipse plugin version 1.3.0 with enhancements and bug fixes has been bundled with this release.

• Support provided for upgrading the eclipse project created in WebNMS 5.2 to WebNMS 5.2 + SP1.


7

Zoho Corp.

WebNMS Framework 5.0

Release Notes for WebNMS Framework 5.0


1. Framework Services 1.1 Database 1.2 Security Service



4. Management Protocol Services

5. Discovery & Topology

6. Maps

7. Fault Management

8. General

9. WebNMS Framework Eclipse Plugin for Application Development Environment

9.1 General Features 9.2 Services

Release Highlights

• Hibernate version 3.2.6.ga integrated in Web NMS as persistence framework. Object modelling, connection pool, transaction service, caching etc., are based on Hibernate framework. With Hibernate integration, WebNMS Framework now offers enhanced object modelling, database constraints like foreign key, surrogate key etc., Core WebNMS Framework modules like Topology, Fault Management, Map, Performance Management, and StorageServer use Hibernate persistence.

• WebNMS Framework uses Tomcat version 5.5.20 as web server instead of Apache. It is used as web container as well as web server, thereby reducing the security vulnerabilities, maintenance effort and product size. In the previous versions of WebNMS Framework, Apache was used as web server and Tomcat was used as web container involving two applications for two services.

• WebNMS Framework Studio enhanced with support for Eclipse IDE. WebNMS Framework provides a plug-in for Eclipse version 3.3.x, which has WebNMS Framework Studio tools and features integrated.

• WebNMS Framework monitors the JVM parameters like CPU Utilization, Memory Usage and Thread Counts and Web NMS server parameters like Status Polling rate, Data Collection rate, Trap, Event, Alert Processing Rates. For managing the JVM issues, if the JVM parameters cross the threshold, it is reported to Administrator by mail or other actions. For quick issue resolution WebNMS Framework provides server and database logs in a sleek format.

• WebNMS Framework introduces Distributed Multi-tier Architecture in Polling Engine to provide scalability and reliability in monitoring Network Elements. This architecture reduces


8

Zoho Corp.

the load on the Poll Engine in WebNMS Framework Server and enhances the performance by faster data collection.

• WebNMS Framework supports complete deployment of WebNMS Framework BE & FE servers in JBoss.

• Status Polling performance enhanced by fetching only the required managed object properties for status polling instead of fetching the entire managed object. This reduces the fetching time and improves the status polling performance.

• A new Notification Mechanism provided to notify WebNMS Framework client activities like login, logout, and login failure. Applications can register to initiate actions like Email, Alert etc.

• Map Tree Nodes can be associated with a managed object and the status of the managed object will be propagated to the corresponding Tree Node. The Tree Node icon color will represent the status of the managed object. This feature is applicable for Java client.

• Maps can integrate Alert, Event and any Custom panel into them as separate tabs. The Alerts, Events and Custom panels are displayed at the bottom of the Map as tabs. The panels present a quick snapshot view of events/alerts related to the corresponding managed objects contained in the map.

• WebNMS Framework has integrated Log4J as default logging service framework. With Log4j, the logs are presented in sleek format to give a clutter free look.

• Support included for the following:

o OS versions, such as, Windows Server 2008, Windows Vista, Fedora Core 9, RedHat Linux 9.0, RedHat Enterprise Linux 5.0, AS 4.0, and Solaris 10.

o Database MySQL version 5.0.44

o Java Development Environment JDK 1.6

o Web browsers IE 7.0, and Firefox 3.0

• WebNMS Framework supports JMX Agent version 6.0. This version supports enhanced North bound communication.

1. Framework Services

New Features

• User login and logout activity has been made observable in WebNMS Framework. An interface has been provided at the framework level for the customers to implement their own notification mechanism. This interface shall also provide user credentials such as user name, type of activity being done (login, logout, login failure), time of activity, number of failure count (in case of login failure) etc., so as to provide a greater control over security in EMS.


9

Zoho Corp.

• Hibernate based StorageServer framework enables the user defined object to be stored into database using StorageAPI. The framework supports the custom object with complete ORM support (for Create, Retrieve, Update, and Delete tasks), bulk operations addition and deletion, notification framework, object locking and complete custom view support. The StorageAPI interface replaces the already available UserStorageAPI.

• A new API, NmsManagementAPI has been provided to dynamically obtain the different performance rates such as Status Polling, Data Collection, Alert Processing rate of WebNMS Framework server.

• WebNMS Framework has integrated Log4J as default logging service framework.

• A new interface PreStartUpValidator has been introduced to implement pre-startup check for WebNMS Framework server. This interface gets called before WebNMS Framework server startup and checks like the availability of disk size, ports, database etc., can be done either to proceed or abort server startup.

Changes

• Apart from using Tomcat as web container, WebNMS Framework uses Tomcat also as web server instead of Apache. By default, Tomcat version 5.5.20 is bundled with WebNMS Framework. Apache Web server was used in earlier WebNMS Framework versions.

• The dependency of xalan, crimson, and jaxp jars, has been removed in Web NMS server and client framework.

• As of the J2SE 5.0 release stub classes are no longer needed to access the remote objects, the codebase entry can be removed in startnms.bat/sh file.

Enhancements

• WebNMS Framework can be installed in OS versions such as Windows Server 2008, Windows Vista, Fedora Core 9, RedHat Linux 9.0, ES 5.0, AS 4.0, and Solaris 10.

• WebNMS Framework supports Java version 1.6 (Sun Java 6.0 version). JRE version 1.6 is bundled with WebNMS.

• WebNMS Framework adopts Java Service Wrapper for installing WebNMS Framework as Service. The Wrapper makes it possible to install Web NMS as a Windows NT Service. The scripts provided with the Wrapper also make it very easy to install WebNMS Framework as daemon processes on UNIX systems. The Wrapper correctly handles user log outs under Windows, service dependencies, and the ability to run services which interact with the desktop. Using Wrapper, WebNMS Framework can be started with multiple dependent services.

• A particular scheduler can be made to run even when Scheduler.suspendAll() is called by setting the boolean suspendable (in the Scheduler class) value to false. The property is set to false using the setSuspendable method.


10

Zoho Corp.

1.1 Database

• WebNMS Framework supports the following databases with integration of Hibernate:

o MySQL (default) o Oracle o Sybase o PostgreSQL o MSSQL

• Core WebNMS Framework modules like Topology, Fault Management, Map, and Performance Management use Hibernate persistence.

New Features

• WebNMS Framework is integrated with Hibernate version 3.2.6.ga, as persistence framework. Hibernate is high performance object/relational persistence for Java environments and query service. This framework makes object modeling as simple as writing an XML file.

• With Hibernate, WebNMS Framework uses C3P0 for database resource pooling like Connection and Prepared Statements.

• WebNMS Framework uses ehcache as its object caching strategy. Hibernate uses this second-level caching to enhance performance.

• WebNMS Framework supports PostgreSQL database version 8.2.4.

Enhancements

• Default database MySQL (bundled with WebNMS Framework) upgraded to version 5.0.44. By default, InnoDB engine is enabled.

• Hereafter, error code would be returned in case of database restore failure to easily identify the root cause of the issue.

1.2 Security Service

New Features

• In Java client, you can configure minimum and maximum length of the password.

• WebNMS Framework provides new interface ValidateCredentials to perform custom validation (like validating against password history, password format etc.,) of the Password field at server side.

• Banner dialogs can be displayed starting the client by setting appropriate parameter values. The messages to be displayed in the banner can be customized as per the requirement.


11

Zoho Corp.

Enhancements

• It is now possible to have special characters in the password.

• The Authorization Audit details can now be stored in CSV format.

• When there are conflicting permission between a child operation and parent operation in various groups then the parent operation will take precedence over child operation for a user.

• In addition to the user name, the descriptive name of the WebNMS Framework User(s) account can also be provided when creating an user.


New Features

• Tree node icons can now reflect the status of the managed object associated with it. This feature provides the status of the managed objects in the tree itself. Any status change is easily noticeable by the user.

• Whenever an user account is created, by default, user directories of the same name are created under <Web NMS Home>/users folder to store user specific menus. If common menus are to be used by all user accounts, the directory creation can be omitted by configuring CREATE_USERDIR value to false.

Enhancements

• Support provided for playing Audio files upon reception of alarms on client side. Severity based audio files can be configured by the user.

• Option to enable "Telnet to a device" using TCP communication has been given for environments like NAT firewall where there are issues in RMI communication.

• The maximum size of the tree icon can be set by configuring the TREE-ICON-MAXIMUM-DIMENSION parameter in the <Web NMS Home>/conf/clientparameters.conf file.

• In the list view, the object specific menu can be hidden on multiple selection in the list view.


12

Zoho Corp.


New Features

• A new page JVM Management is added for WebNMS Framework Administrator and the page displays the graphs of the monitored data of all the JVMs (BE, FEs and Clients).

o You can view the CPU usage, Memory usage and Thread count of all the JVMs and the different metrics such as Status Polling rate, Data Collection rate, Alert Processing Rate etc., of the WebNMS Framework server.

o Additional features available are: Client termination, getting the JVMs details and the thread dump, and Reporting issues.

Enhancements

• The reuse password option (which appears on configuring change_password_for_firsttime_login as true is now turned off by default. However the same can be activated by setting ALLOW_PASSWORD_REUSE as true in <Web NMS Home>/conf/serverparameters.conf.

4. Management Protocol Services

New Features

SNMP

• WebNMS Framework listens for SNMP V3 informs and processes the informs following the same flow of traps like transformation into Event, Alert correlation and also passes through all available parsers and filters.

Enhancements

• During discovery of CLASS B network with SNMP V3 enabled, one row of MO will be added instead of 65000 rows to prevent OutOfmemory error when reading all the entries from the USERTABLE.


13

Zoho Corp.


New Features

• During Status Polling, instead of fetching the entire managed object, only the properties specified in the configuration file (StatusPolling.conf) would be fetched. The fetched properties would be passed to UserTester interface, if user defined status polling is enabled for that managed object.

• SNMP V3 support has been provided for status polling of DHCP devices.

Enhancements

• During status polling, IpAddress of a device is moved to 0.0.0.0 only when the old IpAddress does not correspond to the DNSName and the new IpAddress does not have the same PhyAddress of the device. In cases when the device is not reachable during StatusPolling the device is moved to major status.

6. Maps

New Features

• Map Symbol LED Flash feature is introduced to notify the status changes of MO. You can enable/disable this visual notification per map basis and per symbol basis. Time duration of blink and also number of blinks are configurable. WebNMS Framework provides facility to suppress the blink notification (like acknowledging the status change notification).

• Events/Alerts custom views are available as tabs by default and user defined panels can be added as tabs with the maps. These custom views present a quick view of events/alerts related to the corresponding map and its objects.

Enhancements

• Map Zoom quality has been enhanced to avoid map from pixelating. While zooming in and out avoids continuous changing of position of anchored symbols. Zoom mode selection of symbols and zooming made effective, i.e., the selected area is fully contained in the view window after zooming. Zoom slider precision and look and feel improved.

• Previously whenever a map was reduced to a smaller size and saved, the position and size of the map symbols will be saved in the database. When the map was resized and refreshed again, the map symbol size was same as that saved in the database. Now it has been fixed to adjust to the size of the map on refresh.


14

Zoho Corp.

• During map repaint process on the client, multiple links displayed between MapSymbols led to performance degradation. To overcome this, the display of multiple links between map symbols has been disabled. However, the option can be enabled by setting the ENABLE_MULTIPLE_MAPLINKS="true" in <Web NMS Home>/conf/clientparameters.conf file.

7. Fault Management

New Features

• Fault module uses a dedicated thread instead of the main thread for enhanced trap processing and related operations.

• Secure mailing (in SSL mode) enabled in the "Send Email" action in event and alerts filters.

8. General

New Feature JMX Agent

• The JMX agent bundled in WebNMS Framework has been migrated to NMS JMX Agent release 6.0 release. Previously it was using JMX Agent 5.1 release.

9. WebNMS Framework Eclipse Plugin for Application Development Environment

9.1 General Features

• Complete life cycle support from Resource Modeling to Deployment.

• Segregated Development and Deployment environments.

• Service-level segregation of information to enable distributed development.

• Option to completely package the User's changes.

• Single NAR (Nms ARchive) to install Client and Server customization in WebNMS Framework.

• Scripts to start Chassis Wizard and Configuration Wizard from Eclipse


15

Zoho Corp.

• Launchers included for starting and shutting down NMS server and client and also reinitializing the NMS database.

• Hassle free integration of customized applications into WebNMS Framework.

9.2 Services

Resource Modeling

• Modeling of Managed Resources in four simple steps.

• Can also be used for creating Extended Alert and Extended Event.

• Provision for generating the pojo class from Hibernate Mapping file.

• MIB support for adding attributes to Managed Resources.

• Automated entry in the Hibernate configuration file (hibernate.cfg.xml) for Managed Resources created via Object Modelling tool.

Discovery

• Shallow and Custom Discovery Filter Wizards for defining discovery filters based on requirements.

• Automated source code generation for creating Shallow Discovery filter.

• Automated entry in discovery.filters for filters created via plugin.

Map

• Wizard to define Map Filter for displaying network elements (Managed Resources) on the GUI.

• Provision to add Maps, Map symbols, links, and containers to the database through the Map Filter.

Fault

• Trap Filter Wizard to define Trap Filter based on the extended events.

• Provision to define Status Poller to periodically check status of device components.

Go through the WebNMS Framework Eclipse Plugin documentation for complete explanation.

NOTE: To view the documents referenced through links, please download the complete package help zip file and extract it under <Web NMS Home>. This Release Notes has links to Developer Guide, User Guide, Administrator Guide, Installation Guide, and Eclipse Guide.


16

Zoho Corp.

Service Packs

WebNMS Framework 5.0 - Service Pack 1


1. Framework Services 1.1 Database 1.2 Security Service




5. Maps

6. Fault Management

7. Performance Management

8. Configuration Management

9. Snmp

10. General

11. Studio Tools

11.1 General Features 11.2 Eclipse

Release Highlights Enhancements

• The Web Client home page construction made easy with widgets and dashboards. Desired widgets can be arranged in rows and columns to form a dashboard and set as the new home page.

• Multiple dashboards can be grouped to form a CCTV to display a slide-show of dashboards.

• The Managed Object details page in Web Client is made more user friendly with additional graphs to view the inventory details.

• Google maps integration facility provided in Web Client.

• Configuration Management feature included in Web Client.

• The generation of event reports made possible from Web Client.

• Filter Notification Actions can now be invoked in separate threads for events and alerts.

• Fault management enhanced with provision to process events and alerts in multiple threads.

• Windows 7 OS support provided. Refer to the software requirements page for more details.

• Windows XP SP3 support provided.


17

Zoho Corp.

Framework

Enhancement

• AES-128 protocol support in Mib browser, and SNMP V3 Security tool provided.

• AES-128 protocol support provided in all the modules except the Configuration module.

• <Web NMS Home>/reports.conf has been deprecated. Henceforth all reporting details are configured in <Web NMS Home>/conf/ReportsManagement.xml.

• StorageAPI can now handle integer datatypes in addition to string.

Bug Fix

• WebNMS server was not getting started when MSSQL Server 2005 was started with non-admin user. This is fixed.

• NullPointerException was thrown when WebNMS licensing framework was disabled. This is fixed.

• SSL related issue while transferring hourly reports in poller is fixed.

• The localhost address was returned on calling the NmsUtil.getListOfFEServers() during shutdown instead of returning the list of stand alone FE Servers that are connected to the BE server. This issue is fixed.

• Taking backup when WebNMS is running suspended all the schedulers including the HeartBeat-updating-Scheduler. This resulted in an unintentional failover when a STANDBY server is started (since the LASTCOUNT of BEFailOver table is the same till the backup gets finished). This is fixed by setting the boolean value setSuspendable as FALSE when the HeartBeat Scheduler is started.

• OutOfMemory issues due to scanning open TCP ports in WebNMS machine are fixed.

• Shutting down of STANDBY server with HOT_STANDBY_MODULES running did not stop the RMIRegistry process. This issue is fixed.

• The ClassCastException issue in getObjectPropsWithProps(className,fetchProperties,criteriaProps,returnAsProps,performOr) of TopoAPI is fixed.


18

Zoho Corp.

Database

Enhancement

• Provision included to backup and restore binary files (.zip / .tar etc). Similarly, particular type of files (*.txt /*.conf) can be excluded to be backed up / restored. The FILES_TO_BACKUP and FILES_TO_EXCLUDE parameter in <Web NMS Home>/conf/BackUp.conf can be used to achieve this requirement.

• Tables can be excluded on restoration using the EXCLUDED_TABLES option in <Web NMS Home>/bin/backup/TablesToRestore.conf file.

• MySQL server can now be started and stopped in any port. Previously only the MySQL started in the default 3306 port was properly stopped by WebNMS.

• During restoration of database, the details such as Restoration startup time, Table names with their row counts will be displayed instead of the busy cursor.

Bug Fix

• MySQL dependencies while starting the WebNMS Server with other databases is removed.

• The ZipException that occurred when restoring huge amount (5 GB) of data is fixed.

• The duplicate key violates (JDBC Exception) exception that occurred when deleting container objects with TOPOUSERPOPRS table is fixed.

• Issues in cross DB restoration due to varying syntax of user dynamic tables in different databases is fixed.

• Dynamic tables were not created in Postgre SQL when there exists custom tables without '%' sign. This is fixed.

• With oracle database, the ORA-00933 error was thrown when the column header is clicked to sort the extended event column in the Network Event panel. This is fixed.

Security

Enhancement

• There is restriction in having the same user name as the group name in the application client. The same check is included when adding users in the Web Client also.

• Admin users need not provide the previous password of a user (any other user) to change that user's password.


19

Zoho Corp.

• Previously, a single 'Change Password' operation controlled the operations of changing both the self password, and changing the password of any other user. Now this is split as two separate operations.

Bug Fix

• When the permission to 'Get Users List' is enabled for a particular user, the list does not get displayed for that particular user in the Application client. This is fixed.

• Fix included to display proper message on changing the password for a user from the Password Configurator dialog.

• Issue in creating a group with its name ending with the word Group is fixed.

Java Client Framework

Enhancement

• In the Network Database views, it is now possible to align text as desired by setting the proper value for the TABLE_TEXT_ALIGN parameter in <Web NMS Home>/conf/NmsPanels.conf file.

• When multiple panels are provided for the 'INIT_PANEL' parameter in <Web NMS Home>/conf/clientparameters.conf, all the panels are displayed in TILE HORIZONTAL layout on client startup.

• Filter action UI in the Java client is enhanced for better usability with provision to configure separate threads for filter actions.

• The Total, From, and To text fields in page navigator in the Application client is made non-editable, and the length of the text boxes will be automatically modified to display the number. The non-editable textbox can be customized as editable fields by overwriting the setProperties() method.

Bug Fix

• The connection lost message displayed in the status bar of the Application Client "javaui.errmessage.connectionLost" was not internationalised. This is fixed.

• Fix included for handling invalid severity in custom view scope.

• In Network Database views of the Application Client, when Alt + D is pressed to view the MO details without selecting any MO, the message "Unable to fetch the details of the selected Object(s). The server may be busy, try later" was displayed. This is fixed to display proper error message.

• Duplicate queries were sent to the server for the custom views on selection of tree nodes whose corresponding panel is already open. This is fixed.


20

Zoho Corp.

• In the map search dialog, the issue in using 'Match Whole Word' and 'Ignore Case' conditions is fixed.

• The text truncation issue (e.g "Alarm Messag...") in the header field combo box of the search dialog is fixed.

• In rare occasions, when the client is unable to communicate with the server, TransportException was thrown and the exception trace was printed in the client logs. Now the trace is printed in an error dialog when client debug is enabled instead of printing in the logs.

• With the append_object_menu parameter set to false in the object-specific menu file, client hangs on invoking the right-click menu items in the list view. This issue is fixed.

• If a modal dialog was open when unlocking the client after lockout session, a duplicate modal dialog was displayed. This is fixed.

• The issue of busy cursor not getting changed to normal cursor when the Detach option is selected by right clicking on the map tree node is fixed.

• During multiple selection of rows in the list view, unnecessary looping was happening resulting in the increase of CPU usage. This issue is fixed.

• The Show All button was not displayed in the AuthAuditBrowser when the search criteria was applied. This issue is fixed.

• When nodes were moved under the same parent, the nodes were not getting persisted. This issue is fixed.

• When the Save To File menu option is selected in the Alarm panel and an existing filename given, the file gets overwritten. This issue is fixed such that we show a confirmation dialog before overwriting the existing file.

• Hereafter, when the client is restarted, the menu details will be fetched from the cache instead of the server.

• The table columns were not getting reordered when changed using the NmsUiAPI.addTemporaryCustomView() method. This issue is fixed.

• Busy cursor was not shown in the EventBrowser panel when the Event data was being fetched from the server. This issue is fixed.

• When the addTemporaryCustomView method of the NmsUIAPI is invoked the first time, all the columns selected to be displayed were not displayed. Only the default columns were displayed. This issue is fixed.

• When search is performed on date condition with 'equal to' parameter, the milliseconds were ignored and as a result data was not fetched. This issue is fixed.

• The order of the Maps was not retained on client restart after the tree nodes were reordered using the Move Node operation from the client. This issue is fixed.


21

Zoho Corp.

• When the sort is set using the parameters ORDERBYCOLUMN and ISASCENDING, the client displayed the data and the sort icon correctly. But if the sort criteria is changed in the client view, the data gets sorted correctly but the icon is shown wrongly on switching to some other view and returning back to this view. This issue is fixed.

• The Export Data operation was not working in case of multiple instances of panels. This issue is fixed.

• Synchronous requests from Java client to the server resulted in missing responses. This is fixed.

• The NullPointerException that occurred on closing the Run Time Administration window is fixed.

• The sort indicator and scroll bar issue in ProListView bean is fixed.

Web Client Framework

Enhancement

• The Web Client home page is enhanced with facility to design the layout using widgets and dashboards. Custom dashboard can be created and set as the home page.

• Dashboards can be integrated in a CCTV to view a slide-show of dashboards at a specific time interval.

• The Managed Object details page in Web Client is made more user friendly with a new layout with more inventory and performance graphs.

• Google maps integration provision included in Web Client maps.

• Configuration Management feature included in Web Client.

• The generation of event reports made possible from Web Client.

Bug Fix

• Fix included to avoid exception traces in the Web Client when the modified value of the parameter 'selectedTab' does not match any of the tab belonging to a particular user.

• The issue in selecting threshold list for Polled Data in Web Client is fixed.

• The Performance graph was not getting created in Web Client connected through FE server. This issue is fixed.

• The NullPointerException that occurred on clicking NE Re-sync in Web Client is fixed.


22

Zoho Corp.

• In Create Multiple Users page in the Web Client, when User Name field is left empty in between users, the users were created after displaying a error message. This is fixed.

• The unnecessary check boxes for each device in the search results page is removed.

• The 'View Details' option for List of Groups, SubNetworks properties was not working in the MO details page of the Web Client. This is fixed.

• Fix included to display error message when sort in performed for a column which is present in two tables instead of displaying the "Service not available" page.

• While trying to view the performance graph for a custom period, if the end data is before the start date, then an error message was shown and only few polled data was shown in the Reports drop-down. This issue is fixed to pop-up an alert in such scenario.

• In the search screen, the default search option is set as 'starts with'.

Discovery and Topology

Enhancement

• The timeout parameter is included for system ping.

Bug Fix

• The nodes were not getting discovered when many nodes of the same network were added from multiple threads using TopoAPI.addNode() method. This is fixed.

• When adding a node without its interface, the client displays an error message even after the node is added successfully. This is fixed.

• The getObjectPropsWithProps() method call was throwing UserTransactionException if invoked before the DB connections for module queries (such as custom view queries) got initialized. This is fixed.

• Storage Exception was thrown in the logs when deleting a network using "Delete Object and Traces" menu item. This is fixed.

• When Managed Objects were added and deleted in succession, status polling for some of the devices were stopped randomly. This is fixed.

• The issue in constructing the Ping Command string in execPing6 method is fixed.

• Using the getObjectNamesWithProps() method with the values true / false provided in the property was replaced with 1/ 0 before fetching from the database even for String data type. This issue is fixed.

• When searching with empty string in any of the value for matching criteria, all objects were returned instead of the object satisfying the search criteria. This is fixed.


23

Zoho Corp.

• Previously a node with a (wrong) network's IPAddress can be added. This lead to ClassCast exception at the time of status polling. Now such a node cannot be added at all.

Maps

Bug Fix

• When updating any map group property using the symbol property dialog, a new map symbol was added in the map view with the group name and the map group was ungrouped and displayed. This is fixed.

• The status message of the previous search was retained even when the map search dialog was closed and invoked again. This is fixed.

• When using the method mapApi.getAllSymbolProperties(viewId), the property 'type' was missing in the result. This is fixed.

• After opening more than 20 maps in the client, when open submap option is used, NullPointerException was thrown continuously in client log. This is fixed.

• ClassCastException was thrown with the deleteContainer() method when the server is warm started in JRE 1.5. This is fixed.

• The NullPointerException that occurred on using SnmpMapFilter.java example file is fixed.

• When a link is made between MapContainer object, the link gets broken when moving that component in the map screen. This issue is fixed.

• The StackOverFlow error when using the MapAPI.deleteContainer() method is fixed.

Fault Management

Enhancement

• A new parameter MAX_EVENT_SIZE_IN_DB is introduced in the EventMgr process in <Web NMS Home>/conf/NmsProcessesBE.conf file to specify the maximum number of events to be stored in the database. If the event size increases beyond the configured value, the oldest events will be removed from the database.

• Provision to invoke Filter Notification Actions in separate threads for events and alerts.

• Fault management enhanced with provision to process events and alerts in multiple threads.


24

Zoho Corp.

Bug Fix

• When two thresholds for a single PD (one is to raise Critical event, another one is to raise Major event) is set, these two events were continuously generated during the alternative data collection irrespective of the values collected. This issue is fixed.

• For every data collection, the event is generated with alternative severity from threshold irrespective of the value specified for the threshold. This happens when the data collected exceeds the threshold value. This if fixed.

• When multiple events/alerts is selected and mouse clicked holding the CTRL key to deselect all the rows, and now clicking on ALT + D to view the event/alert details displayed the last selected event/alert details instead of 'No row selected' message. This is fixed.

• When more than one event is selected and ALT + D is selected to view the event details, the last selected event details is displayed instead of displaying proper message 'More than one row selected'. This is fixed.

Performance

Bug Fix

• NullPointerException that occurred on adding a polling object through the UI is fixed.

• Fix provided for persisting empty values in custom STATS tables.

• Fix included to prevent the setting of timeval field of polledData if it is set by the poll filter.

• The calendar component in Collected graphs was not getting invoked. This is fixed.

• The issue in generating clear event when the collected value decreases the rearm value and ResourceMonitoring is returning null is fixed.

• Status poll was called twice in an interval after updating the interval. This issue is fixed.

• The disable status changed to active status on modifying the poll interval as the rearm event was not generated from the Poller as the poller modified properties were overwritten from the BE while modifying. This is fixed.

• When the Table button in the collected graph viewer is clicked for an interval in which data is not available, the table with previously selected data was getting displayed. This is fixed.

• The date and time values in the performance graphs were displayed as long values. Now these have been changed to simple date format.

• There was exception while searching with no input in the search dialog. This is fixed.


25

Zoho Corp.

• If there are tables in the database with name starting with STATSDATA such as STATSDATAxxx along with STATSDATA% tables, there was issue in cleaning the STATSDATA% tables. This issue is fixed.

• MAX_OIDS_IN_ONE_POLL was not taking effect in multiple type PolledData. This is fixed.

• The date range error involving 12.00 noon ( eg. when selecting 12.00 noon to 3.00 pm) in Collected Statistics is fixed.

• There was an issue in creating the prepared statements for custom tables ending with %. This issue is fixed.

• The issue in setting the primary key constraints in custom stats table is fixed.

Configuration

Bug Fix

• In the Batch Configuration dialog, NullPointerException was thrown on clicking on the column though the data was sorted properly. This is fixed.

Snmp

Enhancement

• Snmp Ipv6Address support is included.

• InetAddress datatype support in SNMP PDU level is added.

• During discovery, if EngineEntry is already present in the EngineTable without EngineID, re-discovery will be performed.

Bug Fixes

• After failover, SNMP operations in the MibBrowser of the Java Client was not working. This is fixed.

• Fix in SASClient : NullPointerException that occurred while re-establishing the TCP connection for continuous GET Request for the graph plot in Web NMS is fixed.

• If a new file is added to SasFileDialog, it will maintain the directory path of the new file created as well as the file name.

• The issue of SNMP v3 requests being sent with empty engineID (bad discovery) is fixed. When an engine entry with empty string is added to engine table, then engineID is taken as zero length (not null) and requests are sent with zero length engineID. This issue is fixed.


26

Zoho Corp.

• ArrayIndexOutOfBoundsException occurred when there was mismatch in the length of varlist and oidlist variables using SnmpTarget.snmpGetVariableBindings() method. This issue is fixed.

• When the database connection object was idle for a long time, there was an issue in getting response from the agent. This is fixed.

• The NullPointerException that occurred due to customer-specific implementation methods in this branch is fixed.

• In case of SNMPv3, setting broadCast flag to true is disallowed if the remoteHost address ends with either ".255" or ".0".

• Error propagation of TooBig PDU for a Snmp Get request using highlevel API is fixed.

• The NullPointerException that occurred when invoking LogManager.addLogClient(LogInterface client) method in multiple threads is fixed.

• Debug log message was not printed properly in a multi-threaded environment. This is fixed.

• Fixed the IllegalThreadStateException that would happen if SnmpPoller is instantiated in different threads simultaneously.

• NullPointerException occurred after SASession could not construct an SNMP message from the received malformed packet. This is fixed.

• Fix for the issue of EngineID becoming empty in the ENGINETABLE of database when processing the get request and response.

• Handled the SQLException in SNMP API that may be thrown while closing a Statement object if its Connection object is already closed.

• When snmpv3 agent is running, if an attempt is made to modify/update snmpv3 user credentials from the remote machine using snmpUSMRemoteConfigure application, the passwords and keys was not updated properly in the agent end. This is fixed.

• The issue of database connection timing out is fixed by doing a dummy query for every 1 hour to keep the DB connection alive.

• When tried to access the SasFileDialog.applet from any application it throws IllegalAccessError. This issue is fixed.

• If the SnmpEngineBoots of a SNMPv3 device gets changed due to device reboot, the Web NMS will again initiate SNMPv3 discovery to get the latest SnmpEngineBoots and SnmpEngineID. While doing this, a NullPointerException was got in SnmpSession class. This is fixed.


27

Zoho Corp.

General

Enhancement

• The support mail ID was hard coded in the log message. Now there is provision to provide the desired support ID using the I18 tool in the <Web NMS Home>/html/EnglishToNative.properties file.

• Common configuration of mail accounts is introduced in <Web NMS Home>/conf/MailServer.conf. This would be used for both JVM monitoring notifications and Send Email Filter actions in Java and Web Clients. In addition, Web Client enhanced to support multiple mail server settings, and send email notification modified to fetch the server details from MailServer.conf.

• Fix included in the Rebranding tool to make the version change effective in the About Dialog along with the other changes.

StudioTools General Features

• There was an issue in using the Versioning -> CVS Server option in the Configuration Wizard due to the absense of versioningClasses.conf file in <Web NMS Home>ClientBuilder/conf/versioningClasses.conf. This file is now included to fix the issue.

• JDK 1.5.0 source compilation support provided in Studio tools.

Eclipse Plugin

Enhancement

• There is provision to generate source file on completing the MO modelling. The destination folder for the source file can be provided in the MO modeling wizard. This option is enabled by default.

• The composite and non-composite controls present in the primary key page of the MO Modelling tool has been moved to the property display page. While adding each property, the primary key can be set by selecting the check box that is present at the start of the added property.

• The composite and non-composite control is enabled in the property display page only when the user-storage option is selected. Also the check box will present in the row only when user-storage option is selected.

• The Modify XML option is provided to enable editing the *.hbm.xml file.


28

Zoho Corp.

• The jar and type details of the source folder can be provided in the project properties dialog. This information is used while packaging the project.

• Eclipse project created in WebNMS 5 can be upgraded to a Service Pack 1 compatible project.

• Security administration tool can now be invoked from within Eclipse.

Bug Fix

• In the taskStatusID section of the Create Hibernate Mapping File wizard, on selecting any IdentifierGenerator value in the drop down list, the generator class value in the generated hibernate file was always native. This is fixed.

• There was an issue when modeling the managed object with upper case characters in the package name. There is now restriction in the wizard to provide the package name only in lower case characters.

• The entry "output folder= <projectname>/clientclasses" in projectdetails.xml file was causing issues while packaging in eclipse. This is fixed by modifying it as outputfolder="clientClasses".

• While creating trap filters, when v1 is selected in the beginning and Enterprise OID is entered, the Finish button got disabled. The button was not enabled on selecting a different version v2. This issue is fixed.

• When MO or filters are deleted, the corresponding entries do not get deleted from the nms-common.properties file present under the eclipse project folder. This is fixed.

• In trap filter creation wizard, the GT and ST fields are accepting string values. This is fixed.

• Invalid character check included in the wizards such as MO modeling wizard, filter wizards etc.

• When a project is packaged after importing a conf file, the error message -1 was displayed. This is fixed.

• There was provision to add additional properties to a table, but there was no provision to remove the added properties. This is fixed.

• When an additional property is added as column to the table, the field becomes mandatory. Now this check is removed.

• For attribute selection from MIB, only the attribute name was taken from MIB, the datatype of DB field was not taken. This is fixed and the datatype is also got from the selected MIB itself.

• The MIB loaded for attribute selection was not remembered in the MO modeling wizard. This is fixed so that the MIB need not be reloaded for that session of Eclipse.


29

Zoho Corp.

• The Finish button will be enabled only after the values are specified for the mandatory fields such as Property Name, Type, Column, and Length.

• The Add and Delete buttons were missing in the Attribute selection UI. This is fixed.

• The issue when composite ID is used along with mapped=true property is fixed.

• When trying to delete MO by right clicking SERVER node > Modelling > Delete Managed Object, the "The chosen operation is not currently available." error gets thrown and not able to delete any MOs. This is fixed.

• Sometimes, when source files are imported into EMS projects, the value which is set for resource copy exclusion filter is null and this causes NullPointerException while packaging. Hence, a null check is added and a default value assigned to the same to fix the issue.

webnms framework :: release notes · webnms framework 5.2 :: release notes 2 zoho corp. release...

Documents