|
|
The primary focus of this release is to make Web NMS more developer-friendly. With this Service Pack, Web NMS is empowered with self monitoring and management capabilities by the usage of J2SE5.0 Management APIs. The following features can be enabled by running Web NMS with JRE 1.5 :
Memory and Thread Monitoring of the Web NMS Server and Application Clients - Existing Data Collection framework will be used to collect the Web NMS JVM resource statistics.
Memory Notification System - Automatic email notification will be sent to the administrator and information of the threads will be dumped when the server memory usage exceeds the configured threshold value.
P6Spy, an open-source framework for applications that intercept database statements/operations, has been integrated in to the Web NMS platform. As a result, all the database queries between the Web NMS server and the database server can be logged to a flat file. Also, long-running database queries can be identified by enabling P6Spy logging. A new page has been provided in the Web Client to configure the P6Spy properties at runtime.
Apart from the default Web NMS Logging Framework, Web NMS provides support for industry standard Apache's Log4j framework. A default implementation for Rolling File Appender and a sample configuration entry for SMTP Appender is made available in Web NMS.
Server
Log and P6Spy Log Viewers
- This release provides new web-based UIs for viewing Web NMS, P6Spy,
Apache, and Tomcat logs.
Refer to the Web NMS JVM Monitoring section of
the Developer Guide for more information on the above features.
Support tab is added to the Web Client. This page enables users to create a bug report by means of a support information file which contains logs, and configuration files. The file can then be uploaded to AdventNet or can be mailed to nms-support@adventnet.com along with the support query. This tab also provides access to the Web NMS online public forums, Technical Documentation and Knowledge Base.
Debugging features have been included in the Java client. All client operations will be logged in the client logs by enabling the 'Debug Mode' option. The details in the client cache can be logged by enabling the 'Client Details' option. Refer to the User Guide topic for more information.
Support for RedHat Linux ES 4.0 and AS 4.0 is provided in addition to the already supported operating systems. Refer to the Installation Guide to get to know the procedure to start the Web NMS server in Linux ES/AS 4.0 operating systems.
Support for MySQL 5.0.21 is provided in addition to the already supported databases. Refer to the Installation Guide for details on the driver version to be used for this database.
Transaction support has been provided for Firebird database.
New methods added in NmsUtil, GenericFEAPI, and NmsClientUtil to expose details about Web NMS server and clients connected. The new list of methods include getClientDetailsOfType, getIpConfigInformation, getJVMSystemProperties, getLicenseInformation, getNmsVersion, getServerIPAndHostName, getServerStartTime, getServerUpTime. Refer to the Javadocs section for the API documentation.
Support for JFreeChart
1.0.0 has been provided
|
|
Note : On upgrading to Service Pack 3 any user customization done to the performance graphs generated by Web NMS will need to be redone to be compatible with the JFreeChart version 1.0.0. The earlier customizations done using JFreeChart 0.9.15 will not be compatible with JFreeChart 1.0.0. Please contact nms-support@adventnet.com for further information. |
Enhancements
The Studio Packager now packages the mibsToBeLoaded.conf and the nmsInterfaces.conf files in the NAR along with the other files.
Bug Fixes
In NAR packaging, classpath update was not happening in the launcher_conf.txt file when the StartNmsJdbc class was replaced with another main class. This issue is fixed.
The usability issue in setting the minimum and maximum value in the NumericSpinControl component is fixed.
In the Security Administration tool present inside Studio, there was an issue in the generation of the securitydbData.xml file when performing Add/Delete Operation. This is fixed.
The Web NMS Client could not be connected with server if the Operation/User settings is manipulated using the Security Administration tool of the studio and the NAR is installed in Web NMS. This issue is fixed.
The 'Class Not Found' error thrown while compiling the Security Administration project in Bean Builder is fixed.
The issue of user-written code missing in the RelationalManagedObject class during regeneration or modification in Studio has been fixed.
'Update Object' functionality was not working in the Deep Discovery Filter generated using studio. This issue is fixed.
Enhancements
The init() method of the CommonRelationalObject class has been made public. As a result, users extending CommonRelationalObject to persist their object using UserStorageAPI, can now have their relational class in any package name.
Bug Fixes
When SSL is enabled, invoking the getClientAddress() method of MainSocketSessionFE results in ClassCastException. This issue is fixed.
The following
archives that were not present in the CLASSPATH variable of the java_service.ini file (present in the
<Web NMS Home>/lib directory)
have been added :
AdventNetCLIClient.jar, AdventNetSnmpDistributedAPI.jar, JimiProClasses.zip,
jfreechart.jar, ftp.jar, jcommon.jar
If you are already running Web NMS as a service, you need to add
these jars in the CLASSPATH variable of java_service.ini
and restart the server.
A minor enhancement has been done in the backup process so as to reduce the CPU cycles.
The time stamp at the Web NMS server startup is logged in the server console.
When running Web NMS in SSL mode, the Truststore password is stored in plain text in the transportprovider.conf present in the <Web NMS Home>/conf directory. Now, an option is provided to configure the encrypted Truststore and Keystore passwords. The passwords should be encrypted using the EncryptPassword.bat/sh script present under <Web NMS Home>/bin/admintools and could be specified using the parameters ENCRYPTED_TRUST_STORE_PASSWORD and ENCRYPTED_KEY_STORE_PASSWORD. Refer to the Developer Guide for more information.
When starting the FE server with the nms.server.host system parameter (parameter used to start Web NMS in a specific IP in a dual NIC machine) , the FE server was not able to connect with the BE server. This has been fixed and it is now possible to start the FE server for a specific NIC in a dual NIC machine.
In a multiple interface system, even if the Apache server is started on a particular interface, the Web NMS server checked for the availability of Apache server only at the localhost IP Address instead of the actual interface. Since Apache was not bound to that interface, the Web NMS server was shutdown gracefully. Now, the Web NMS server will check the availability of the Apache server at the interface specified in the nms.server.host system property.
In the Web NMS default backup implementation, support has been provided for files backup at the sub-directory level.
In the Web NMS license registration screen, the file chooser dialog invoked for browsing the license file had the AdventNet string reference as a hardcoded one, preventing complete re-branding of the EMS. Now, the AdventNet string reference is removed from the License Registration Screen.
If Apache is started on port number 80, during server shutdown in TCP/RMI mode, the server was getting shutdown even if improper port values were provided. This critical security issue is fixed.
During startup, the server will wait for some particular time for proper startup of the Tomcat server. Now, this time out value is made configurable and can be configured using the TOMCAT_TIMEOUT_VALUE parameter (in milliseconds) in the serverparameters.conf file present in the <Web NMS Home>/conf directory.
Web NMS has an option to start the server by attaching it to a standalone Apache server i.e., running as a separate VM. In this scenario, calling the Web NMS shutdown process stopped the standalone Apache server also. Now, this issue has been fixed such that if the Apache server is not started by the Web NMS JVM, the shutdown process will not stop it.
The Web NMS server could not be started in SSL mode from the Web NMS Launcher as well as Windows Service. Now, this issue has been fixed. Refer to the Developer Guide to know more about enabling SSL mode in Launcher and Windows Service.
Previously, the maximum length of the NAME column in the AlertPolicyObject table was 15 characters in the DatabaseSchema.conf file. Due to this, policy names exceeding 15 characters got truncated. Now, the field length has been increased to 100, to fix this issue.
Renaming the *.data
file obtained by running the BackupDB.bat/sh
script and restoring the same file using the RestoreDB.bat/sh
script caused java.io.IOException to be thrown. This issue is fixed.
New Features
Web NMS now supports MySQL 5.0.X. As some of the column names used in the Web NMS database schema conflict with the key words of MySQL 5, you need to backquote ( ` ) these column names in the DatabaseSchema.conf file. The column names are LOCALTIME of USMTABLE and CONDITION of the PollingAttributes table. Change these column names to `LOCALTIME` and `CONDITION` respectively.
Bug Fixes
Data Truncation error occurred when inserting rows in to the REPORTS_HOURLY table in MySQL database versions 4 and 5. This issue is fixed.
VACMCONTEXTTABLE was not getting created in Firebird database. This issue is fixed.
During data collection, if any of the system resources returns Float type values, Parsing Exception occurred. This issue is fixed and the float values are properly stored in database.
In some racing conditions, if a thread tries to execute a database query even after the transaction is timed out for that particular thread, deadlock occurred and Web NMS stopped responding. Now, this issue has been fixed by avoiding the database query execution from a timed out thread.
In MySQL 4.x InnoDB, when tree nodes were added from multiple threads using NmsTreeAPI.insertNode(), an error message stating com.adventnet.nms.store.NmsStorageException: General error, message from server: "Deadlock found when trying to get lock; Try restarting transaction is thrown. This issue is fixed.
In some rare conditions, ArrayIndexOutOfBounds Exception was thrown when trying to access a PreparedStatement from the connection pool. This issue is fixed.
Tree nodes that are added within a database transaction context using NmsTreeAPI, were not notified to the client in the proper order of the transaction operation. This issue is fixed.
If the database column name of a table contained the keyword PRIMARY, update of the corresponding object did not happen properly. This issue is fixed.
When the backup of a database table is configured in MySQL 4.x version with the LIMIT parameter specified in the BackUp.conf file, database rows were backed up only till the highest multiple of LIMIT parameter (within the number of rows available) and the rest of the rows were not backed up. This issue is fixed.
Bug Fixes
The Change Password operation failed to work in the client when custom authentication is enabled in Web NMS. This issue is fixed.
The option for re-configuring the user password on first time login and Password Expiry was not persisted properly in the database and hence the new password was not accepted in Web NMS. This issue is fixed.
When an Authorized Scope is defined on a group and the operation associated with that scope is modified after the scope creation, that particular Scope was not deleted even after deleting the group. This issue is fixed and all the authorized scopes specific to that group are deleted.
New Features
There is now provision to collapse or expand the left navigation pane by clicking on the respective arrow present on the divider that separates the navigation tree in the left and the internal frame in the right side of the client.
The toolbar button size can now be customized using the TOOLBAR_DIMENSION parameter in the clientparameters.conf file.
Support to display the extended properties of the managed object in the Topology Add/Modify Custom View dialogs is given. This feature can be enabled by configuring the CVFORM_ALLPROPS parameter in clientparameters.conf to true.
The custom view UI has been enhanced with provision to change the color and font of the custom view table header by setting the desired value for the TABLE_HEADER_FONT and TABLE_HEADER_COLOR parameters respectively in clientparameters.conf
Auto-scroll feature is provided in custom view table to enhance usability while dragging the table header to the corner of the internal frame.
Enhancements
The setUITimeZone() and getUITimeZone() methods are now available in the NmsClientUtil class. Using these methods you can set and get the UI time zones dynamically from the client.
The Discover Parent Net check box of the RTA is disabled when a node is already configured for Discovery with parentNet set to true.
There is now provision to specify the columns to be displayed in the policy panel by specifying column names in the TABLE-COLUMNS entry for the Policy module in the Tree.xml file.
Bug Fixes
There was issue in using the "&&" (AND condition) in the match criteria when creating or modifying custom views. The data that is present in the database at the time of creation or modification of the custom view was displayed in the new/modified custom view. But the incoming data after the custom view creation/modification was not getting updated in the view. This issue is fixed.
When the image filename/path has space in-between, the map image was not getting loaded in remote clients. This issue is fixed.
When deleting threshold objects, a confirmation message was not displayed. This issue is fixed.
When multiple threshold objects were selected and deleted, only the first selected object was getting deleted. This issue is fixed.
When a User whose password has expired tries to login into the client, the Re-Configure Password dialog was displayed even if the user does not have permission to change the password. This has been fixed to show the dialog only for users with permission to change the password. For other users an error message is displayed.
Clear Severity is removed from the Severity list of Long and Percentage threshold configurations as they are irrelevant.
If all the menu items are hidden in a menu using the ACTION-ON-NO-PRIVILEGE attribute, and if the menu is invoked by right clicking on the tree node, a small square was displayed without any menu items. This issue is fixed.
When the Java Applet Window statement is displayed in the status bar of the Client Lockout dialog, the text and the text boxes in the dialog was shrunk and not displayed clearly. This issue is fixed by increasing the height of the dialog.
When incorrect details was provided in the authentication dialog that is invoked on running the ShutDown.sh/bat script, an Authentication Failure dialog will be displayed. The improper text alignment in this dialog is fixed.
Selection of rows in the Network Database panels using Ctrl + A and Shift + Arrow key was lost when entries are added or updated in the panel. This issue has been fixed.
When there is no entry in the listIcon.data file for a particular type of Managed Object and if the row of that type is double clicked in the Network Database panel, the UI would hang displaying the wait cursor. This issue is fixed.
The TAB command completion feature and automatic focus in the Telnet window does not work when the Web NMS client is started in JDK1.5 or higher versions. This issue is fixed.
In the Policies window of the Web NMS client, if a policy is selected and the right click menu item Update Policy is clicked, a error message "User does not have the permission to do the requested operation" is thrown. This issue is fixed.
Whenever a node is moved under the same parent, there was a mis-configuration in the index numbering and the node was not getting moved to the correct location. This issue has been fixed.
When the Truststore file is not available in the browser JRE's lib/security directory, the client will not be able to connect to the server in SSL mode. In this case, no error message was displayed to notify the exact problem. Now appropriate error message will be displayed.
On setting the value of USE_INTERNALFRAME to false and detaching a panel, the Detach menu item was getting added to the Window menu the number of times the detach menu is clicked. This issue is fixed so that only one detach menu item will be added to the Window menu irrespective of the number of times the detach is clicked.
The Password Expiry dialog was not internationalized. This issue is fixed.
Enabling the SHOW_FIRST_PAGE mode in the client by setting this parameter to 'true' in the clientparameters.conf file did not show the first page for newly created custom views. This issue is fixed.
Clicking on the Alarms summary view after traversing an Alarm custom view with a specific criteria, resulted in the custom view criteria not being applied properly, when clicking on the same custom view again. This issue in temporary custom view is fixed.
The issue in connecting the client to the Web NMS server running in NAT IP has been fixed.
An additional separator was present in the object menu of map module, whereas it was not present in the Network database list view menus. This inconsistency has been corrected.
The image in the map module image panel gets adjusted depending upon the size of the internal frame. When the frame size is reduced/increased the size of the image will be shrunk/expanded. This functionality has been included in the image panels of other modules such as Fault management, Performance etc.
The horizontal scroll bar of the Event Parser dialog was not visible until the dialog was resized. This issue is fixed.
The frame icon images of the Event Filter and Alert Filter dialogs were hard-coded to display the adventneticon.jpg image. This issue has been fixed such that the frame icon shows the image configured for the FRAME_ICON parameter of clientparameters.conf.
New Features
SNMP V3 security parameters configuration/query support is provided in the SNMP Tools page. This is similar to the SNMP Settings dialog of the Java client which takes V3 related information.
Enhancements
Reports module in Web Client is supported with Firebird database.
Multiple row selection and de-selection can be easily performed in all the list views using the Shift key.
The Add Node page is enhanced to accept the DNS Name as input. Previously, only the IP Address of the Node could be specified here.
The Refresh Node page is provided with an option to refresh a node for SNMP V3 discovery.
The Audited Object column will be populated with the object name, if any operation is performed on the managed object from the Web Client. Prior to this release, the object name was not audited.
The $message token is included in the list of property tokens for the mail subject and body options of the Send Email Notification.
The Web Client now supports reading the additional properties such as ORDERBYCOLUMN, ISASCENDING, VIEWLENGTH from the Tree.xml file and applying them in the list views.
Bug Fixes
When a non-English category is clicked in the Alarm Summary panel, a 'No data available' page was shown. This issue has been fixed.
When user invokes Add Group or Operation Configuration page, script error was thrown. This issue has been fixed.
".0" was not appended to the scalar OIDs when selected from the OID Selector of the Web Client. This issue is fixed.
StringIndexOutOfBounds Exception was thrown while viewing reports for polled data using protocol other than SNMP. This issue has been fixed.
ArrayIndexOutOfBounds Exception was thrown when trying to view the Performance page of the web client when there are no polled data in the database. This issue is fixed.
SNMP V3 protocol was not supported when querying device tables such as in Interfaces, Routers, UDP table, and TCP table, in the Managed Object Properties page of the Web Client. This issue is fixed.
When the menu items in the Network Maps tab are enabled and if the user clicks on the Symbol Properties page, exception will be thrown if the symbol name and the object name are different. This issue is fixed.
No error message was shown when an invalid MIB is loaded in the OID selector of the Add Polling Object page. This issue is fixed.
When the user configures any of the available notifications from the Event Filter or Alert filter pages of the Web Client, all the notifications of that type will get selected and the list of notifications will get distorted. This issue is fixed.
Multiple thresholds could not be associated from the Add/Modify Polling object pages. This issue is fixed.
After traversing the polling objects in the Modify Polling Object page, polling objects through which the user traversed, will not get applied for the managed objects added thereafter. This issue is fixed.
When the Configured Collection page is visited for the first time, the number of managed objects shown and the count displayed were not equal. This issue is fixed.
When a user performs a custom view related operation on the page loaded by clicking on any device type from the Inventory Snapshot of the home page or the Search Result page, the same will affect the Complete View in the Network Database tab. This issue is fixed by showing only the Print Version option in such scenario.
No error message was shown when trying to add a Topology custom view with a duplicate name. This issue is fixed.
All the custom views under Network Database tab could be deleted including the Complete View, which removed the Network Database tab subsequently. This issue is fixed.
Interface type was not available in the 'Type' parameter list of the Polling Object page. This issue is fixed.
MIBs with dependencies could not be loaded from the SNMP Tools page and OID selector of the Performance tab. This issue is fixed.
Trap parsers defined with duplicate match criteria in the trap.parsers file could not be modified from the Trap Parser page. This issue is fixed by showing an appropriate error message and providing an option to delete the duplicate parser.
Interface index of 'node' and 'multiple' polled data could not be clearly distinguished in the information displayed in the Reports page. This issue is fixed.
When a map containing match criteria with wild card characters (like "!" for status) is modified, NumberFormat Exception was thrown. This issue is fixed.
When performing the NE Re-sync operation, if the <Web NMS Home>/state/traps directory is unavailable, Null Pointer Exception was thrown. This issue is fixed.
Devices discovered as SNMP V3 were queried with SNMP V2 queries to construct the Memory utilization and CPU utilization charts in the Managed Object Properties page of the Web Client. This issue is fixed.
In the Add Multiple Users page, the users could be created without associating it to any group. This issue is fixed.
In the Group Administration page, if a group is deleted and added immediately, the group could not be added. This issue is fixed.
In the Audit Trails page, if the user varies the page length and traverses to some other page, the page length shown and the number of audit trails displayed in the page were out of sync when re-visiting the Audit Trails page. This issue is fixed.
If an incorrect current password is provided while changing the password of the currently logged in user using the Change Password dialog, the exception trace was displayed as error message. This issue has been fixed by showing proper message.
No error message was shown while creating a new group with an existing group name. This issue has been fixed.
In the operation tree, if the privileges are removed for a parent operation and the change is applied, the third level children and later will get privileged. This issue has been fixed.
In the Add Group page, initially the hint message will be shown related to Add Group operation. However, if any node in the operation tree is clicked, the hint message shown was pertaining to user-based operation. This issue has been fixed.
When a user is not authorized for either Assign User To Group or Remove User From Group, the user will not be able to perform both the operations. This issue has been fixed.
A privileged user could not delete the audit trails of other user. This issue has been fixed.
In the Scope Settings page, the enrolled scopes were listed in the available scopes also and if the user removes all the enrolled scopes, inappropriate error message was displayed. Both these issues are fixed.
When a user moves to the Admin tab after visiting the Audit Trails page, the left tree related to the Admin tab was not displayed. This issue is fixed.
The Set User Permission operation was wrongly audited while adding a new group. This issue has been fixed to audit the appropriate Set Group Permission operation.
Remove Operation was wrongly audited while adding multiple users through the Add Users page. This issue is fixed.
Topology Custom Views defined with match criteria containing not equals or not contains could not be modified. This issue is fixed.
Script errors and scrolling issues were observed in the pop up dialog shown when invoking the Add Group button in the Internet Explorer 6 browser. This issue is fixed.
Wild Characters were getting appended to the operand in the Edit Topology View Criteria page when the criteria included 'not equals' or 'does not contain'. This issue is fixed.
The details logged in the Audit trails could not be internationalized. This issue is fixed.
User passwords were logged in plain text in the log files in DEBUG log level. This issue is fixed.
Incorrect error message was displayed when deleting the currently logged-in user. This issue is fixed.
When the Logs Configurator form is submitted, the Log Levels of nmsout and nmserr are set to 0 for all users. This issue is fixed.
Bug Fixes
While polling a SNMP Agent with set of OIDs containing some erroneous OIDs using Management Server in SNMP v1 mode, the responses for the valid OIDs were not obtained. This issue is fixed.
When establishSession() and terminateSession() methods of the ManagementServer class were called repeatedly, it led to a racing condition resulting in 100% CPU utilization. This issue is fixed.
New Features
A utility class PopulateUserTable has been provided to add and delete entries of SNMP V3 devices in the USERTABLE Table of the database.
Enhancements
Netmask of the node will be passed to the user discovery implementation class. Refer to the Developer Guide for the code snippet to be used to retrieve the netmask.
Cascade deletion of Managed Objects is now supported in MySQL 4.x and 5.x.
If the CONTEXT_NAME field is not given while configuring the discovery of a V3 device, the value specified for the common parameter SNMPV3_CONTEXTNAME will be taken as context name and the SNMP Agent will be queried with this context name.
Bug Fixes
While performing network discovery using TopoAPI's setAddressRangeToDiscover() method, the discovery status of the network object was not set to 'In progress' which lead to issues across the discovery thread during the database update of the same network object. This issue is fixed by setting the network discovery status appropriately.
During node rediscovery, if one of the previously discovered interfaces does not physically exist, the non-existent interfaces were not deleted from the Web NMS database. This issue has been fixed.
SnmpV3 EngineID is not updated when IP Address changed in the case of SNMP V3 DHCP nodes. This issue is fixed.
NodeList of a Network is not updated when a node is added to the network using TopoAPI's addObject method. This issue is fixed.
TopoAPI's addNodeToTopoDB() method discovers the SNMP nodes with the community hard coded as 'public'. This is fixed to read the community as per the seed.file configurations.
The Add Node dialog returns success even if a discovery filter drops the object. This is fixed so as to returns an appropriate error message to the client.
Discovering a multiple interface device was based on the ifIndex value only but in case of devices such as Multi-Home VLANs, the interfaces are such that uniqueness is not based on ifIndex alone but on the combination of IP Address and ifIndex. Hence the multiple interface discovery mechanism is modified to discover based on ipaddress+ifindex in order to identify all its interfaces.
In case of SNMP V3 discovery, a SNMP V2c request was sent to the device to check if it a router. This issue is fixed to send appropriate SNMP V3 request during the router check.
SNMP request with default community 'public' was sent to the local agent even if the DISCOVER_LOCALNET parameter is set to false. This issue has been fixed.
When status poll of a managed object is scheduled in short intervals and if it is deleted and added immediately, the status polling happens for the previously scheduled time also. This issue which was happening in certain racing conditions, has been fixed.
Bug Fixes
Link Symbols that represent the Interface objects are not getting added in Custom Maps. This issue is fixed.
The zoom slider position moved to the default starting point (0), even though the map symbols were still in the zoomed state, when any of the map property was modified and saved to the server. This issue is fixed.
The alignment of map symbols was not proper when changing the map panel's window size after performing 'zoom in' and 'zoom out' operations with the auto-placement functionality disabled. This issue is fixed.
On the Ipnet map panel, the right click menu for a network displays the Stop Discovery menu item even though discovery has been completed for that network. This issue is fixed to display the Start Discovery menu item when discovery is completed for the network.
Bug Fixes
The unnecessary string '-->' was appended to the collected values of String type polled data, by default. This issue is fixed.
In case of data collection in Bulk Insert mode, some of the collected data were not getting stored in the database occasionally. This issue is fixed.
Querying a columnar OID with table values in the agent being empty using the FrameExample class present under <Web NMS Home>/default_impl/client_server_communication resulted in exceptions. This issue is fixed.
During data collection in SNMPv2c mode, if there are some invalid OIDs in the OID list, then the collected values were correlated to the invalid OIDs instead of the valid OIDs. This issue is fixed.
Enhancements
Maximum value of Y-axis of the ACC Panel's Bar graph can be customized by adding the SET_YAXIS_LIMIT parameter in clientparameters.conf.
Bug Fixes
An error message stating No traps defined in MIB occurred when trying to load a MIB with multiple modules in the Trap Parser and the MIB did not get loaded. This issue has been fixed.
Modifying a V2 'Send Trap' action to V1 in Event and Alert Filters resulted in V2 trap still being sent. This issue has been fixed.
Configuring Run Command action on Event/Alert Filters with the Append error with message and Append output with message options disabled resulted in Event/Alert message fields getting appended with the command output errors, if the command was not executed within the specified time out value. This issue has been fixed such that the command output is not appended if the Append options are disabled.
'Save to File' menu item of the Java Client did not save the event and alert information when the directory specified in the SAVE_DIR parameter (argument of the EventMgr process in NmsProcessesBE.conf) did not exist. This issue fixed such that if the SAVE_DIR directory is not present, it is created and then the Event/Alert information are saved in the configured directory.
Bug Fixes
When CLEAN_AUDIT_INTERVAL was configured with a high value, audit cleanup was happening much before due to incorrect clean up interval calculation. This issue is fixed.
When a non-existent TFTP Root directory is specified, the NmsTftpServer process defaults to system root as the TFTP root directory, thus providing access to the entire system. This issue has been fixed such that the NmsTftpServer process would fail to come up in this scenario.
Enhancement
Prior to this Service Pack, the provisioning results shown in the Activity List Panel would be available only to the user who executed the template. Now if a custom view scope is defined for a group, then the provisioning results will be displayed to all the users of that group provided the template is executed by a member of that group.
Bug Fixes
Data type of AlertDescription and AlertTimeStamp have been changed to DisplayString and TimeTicks respectively in AdventNet-WebNMS-MIB.
When a SNMP GET-NEXT request was invoked on the varbindLogTable of AdventNet-WebNMS-MIB in Web NMS JMX agent, an infinite loop was triggered. This issue is fixed.
In the traps that are sent by the JMX agent, the sequenceNum value in the trap varbind was not getting incremented for each trap. This issue has been fixed such that the sequenceNum value is incremented. Also if the sequenceNum value exceeds the maximum value of INTEGER data type, it is reset to zero.
Bug Fixes
Line Graph was not getting plotted when invoked from the SnmpTablePanel of the MIB Browser. This issue is fixed.
Exception was thrown when closing the Mib Node Descriptor dialog of MIB Browser, using the 'X' button. This issue is fixed.
When commands are sent to a remote host running SSH2 server after establishing a CLI Session, NullPointer Exception is thrown. This issue is fixed.
ArrayIndexOutOfBounds Exception is thrown when establishing a SSH connection with some proprietary devices supporting SSH1 protocol. This issue is fixed.
Sometimes, a NegativeArraySize Exception is thrown when commands are sent to a Solaris box supporting SSH1 protocol, after successfully logging into the device. This issue is fixed.
When a non-dedicated CLI Session times out, all the threads used by the session were not getting cleaned up. This issue is fixed.
If a CLI Session fails to open due to incorrect login name or password when connecting to a device supporting SSH2 protocol, all the threads were not getting cleaned up. This issue is fixed.
While data collection takes place using the SSH protocol, if the SSH daemon in the remote host is down, a memory leak arises. This issue has been fixed. It is now possible to stop the SSH daemon during data collection for a period of time and start it again to proceed further so that there is no unnecessary wait and hence no issues of memory leak.
Enhancements
Provision
to perform 'Event To Alert Correlation' at DMS :
When forwarding the events without correlating in to meaningful
alerts, it creates high network traffic from DMS to Central Server and
results in high load on the Central Server. As Fault Management is a major
workload of the Central Server, correlating the events to alerts in the
DMS level and forwarding the Alert-causing Events alone to the Central
Server, becomes crucial for efficient performance of the Central Server.
This feature can be enabled by configuring ENABLE_ALERTFILTER
parameter to true for the RemoteProbe process defined in the
NmsProcessesBE.conf file of the
DMS.
Runtime
Event Filter Configuration of DMS from Central Server's Java Client :
The Java Client of the Central Server is provided with a new option
to configure Event Filters for the DMS.
This option is available in the Runtime
Administration dialog. Users need to copy the event.filters
file to the defaultToNewProbes/conf
directory to enable this feature in the Central Server.
Runtime
Threshold Configuration of DMS from
Central Server's Java Client :
The Java Client of the Central Server is provided with a new option
to configure Thresholds for the DMS.
This option is available in the Runtime
Administration dialog. Users need to copy the Threshold.conf
file to the defaultToNewProbes/conf
directory to enable this feature in the Central Server.
Bug Fixes
Scalability issues in Central Server and DMS have been fixed.
During DMS Failover, the DMS was not sending the updates to the Central Server in two way communication. This issue is fixed.
In some rare scenarios, the Socket Output stream was blocked when the data was transferred from DMS to CS. This issue is fixed.
A buffering issue was identified during a 'Patch Version' Check triggered from the Central Server to the DMS in two way communication. An indefinite while loop check was done for validating the patch version in DMS which lead to thread deadlock in DMS in some rare situations thereby preventing the DMS from reading any data from the Central Server. The issue is fixed.
Configuration Updation issue in distributing the Professional Edition Nar using the DistributedNarPackager tool has been fixed. Contact nms-support@adventnet.com if you plan to upgrade to Service Pack 3 using the DistributedNarPackager tool.
When modifying the polled data in the Central Server (CS), CS sends the modified polled data to the DMS with SSAVE property set to 'false' (as defined in the CS database), which gets updated in the DMS. This resulted in SSAVE property getting modified incorrectly true to false in DMS. This issue is fixed such that if the polled data is modified at the CS, the SSAVE property in DMS will not be updated to false and setting SSAVE property on the DMS is correctly set from the properties defined in Polling.conf.
|
|
