AdventNet Web NMS 5的更新说明

Welcome to AdventNet Web NMS

AdventNet Web NMS is a highly customizable, Java based network management platform, which can be used to build sophisticated network and element management solutions. This README file provides information on the release features, pointers to documentation, support, license, and copyright details.

About the Release

Web NMS 5 is a major release after 4.7.0. This release claims support for some of the new operating systems, databases, and third-party software packages. This release aims at enhancing the customizability of Web NMS to suit your needs.

The major features of this release are listed below:

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, Web NMS now offers enhanced object modelling, database constraints like foreign key, surrogate key etc., Core Web NMS modules like Topology, Fault Management, Map, Performance Management, and StorageServer use Hibernate persistence.

·         Web NMS 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 Web NMS, Apache was used as web server and Tomcat was used as web container involving two applications for two services.

·         Web NMS Studio enhanced with support for Eclipse IDE. Web NMS provides a plug-in for Eclipse version 3.3.x, which has Web NMS Studio tools and features integrated.

·         Web NMS 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 Web NMS provides server and database logs in a sleek format.

·         Web NMS introduces Distributed Multi-tier Architecture in Polling Engine to provide scalability and reliability in monitoring Network Elements. This architecture reduces the load on the Poll Engine in Web NMS Server and enhances the performance by faster data collection.

·         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 Web NMS 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.

·         Web NMS 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:

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

·         Database MySQL version 5.0.44

·         Java Development Environment JDK 1.6

·         Web browsers IE 7.0 and Firefox 3.0

·         Web NMS supports JMX Agent version 6.0. This version supports enhanced North bound communication.

1. Framework Services
 

New Features

o        User login and logout activity has been made observable in Web NMS. 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.

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

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

o        Web NMS has integrated Log4J as default logging service framework.

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

Changes

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

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

o        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

o        Web NMS 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.

o        Web NMS supports Java version 1.6 (Sun Java 6.0 version). JRE version 1.6 is bundled with Web NMS.

o        Web NMS adopts Java Service Wrapper for installing Web NMS 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 Web NMS 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, Web NMS can be started with multiple dependent services.

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

 

    1.1 Database

o        Web NMS supports the following databases with integration of Hibernate:

1.  
   •  
     • MySQL (default)
     • Oracle
     • Sybase
     • PostgreSQL
     • MSSQL

o        Core Web NMS modules like Topology, Fault Management, Map, and Performance Management use Hibernate persistence.

    New Features

o        Web NMS 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.

o        With Hibernate, Web NMS uses C3P0 for database resource pooling like Connection and Prepared Statements.

o        Web NMS uses Ehcache as its object caching strategy. Hibernate uses this second-level caching to enhance performance.

o        Web NMS supports PostgreSQL database version 8.2.4.

    Enhancements

o        Default database MySQL (bundled with Web NMS) upgraded to version 5.0.44. By default, InnoDB engine is enabled.

o        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

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

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

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

Enhancements

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

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

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

o        In addition to the user name, the descriptive name of the Web NMS User(s) account can also be provided when creating an user.

 

2. Java Client Framework

          New Features

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

o        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

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

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

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

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

 

3. HTML Client Framework

New Features

o        A new page JVM Management is added for Web NMS 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 Web NMS server.

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

Enhancements

o        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

          SNMP

o        Web NMS 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

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

 

5. Discovery & Topology

 

New Features

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

o        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

o        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. Web NMS provides facility to suppress the blink notification (like acknowledging the status change notification).

o        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

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

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

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

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

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

8. General

 New Feature 

 

JMX Agent

o        The JMX agent bundled in Web NMS has been migrated to AdventNet JMX Agent release 6.0 release. Previously it was using JMX Agent 5.1 release.

 

9. Web NMS Eclipse Plugin for Application Development Environment

 9.1 General Features

o        Complete life cycle support from Resource Modeling to Deployment.

o        Segregated Development and Deployment environments.  

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

o        Option to completely package the User's changes.

o        Single NAR (Nms ARchive) to install Client and Server customization in Web NMS.  

o        Scripts to start Chassis Wizard and Configuration Wizard from Eclipse

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

o        Hassle free integration of customized applications into Web NMS.

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.

For a detailed list of features and enhancements with links to Web NMS documentation, refer to Release notes.