Studio

Map Filter Wizard

• The generated source of the Map Filter Wizard does not check if a map of the same name already exist in the database.

General

• While compiling Projects from Studio, the classes are placed in the respective <ProjectName>/classes/server and <ProjectName>/classes/client directories as part of client-customization support. Hence, while writing automated Build script for Command line Studio Packaging, ensure two directories "client" and "server" are created under <Studio Project>/classes directory. Compile the server and client-side java files and place them under the respective directories.

Client Builder

• While creating VirtualTableModel beans, if 'not accessible column' is added to the selected nodes list, during runtime it may give some errors. This happens for certain Device Information Bases. Workaround: If index column is of 'not accessible' type , first add an 'accessible' node and then add 'not accessible' nodes.

• When the IF-Mib is loaded, there will be two entries for IF-Index in the IF-Table.

• Issues in Linux platform:

  • With JDK1.3.1, run time screen is not displayed properly when the screen contains Virtual Bean.

  • Sometimes the run time screen does not appear, when the screen with beans components (that has protocol intelligence) are arranged in GridBag Layout.

• Issues with Save Project As option.

  • If the project is saved in a folder having name space such as "Program Files", using 'Save Project As' option, it will have issues with compilation since the URL prefix is not set properly in Project Properties.

  • The project saved in a different drive using 'Save Project As' project option should be updated for the URL prefix in the Project Properties dialog for change in drive letter.

• Images used for the Projects should be present under the /images directory only.

• Mibs used for the Project should present under the /mibs directory only.

Discovery and Topology

 

Object Locking

• From the 2.3 release, the Web NMS internally locks all the ManagedObjects before doing any database update/delete operation. Thus, it is recommended that the users use only the appropriate API methods, which obey the object locking rules. Still, there are methods in TopoAPI (to ensure backward compatibility) which do not obey locks, all of which have been deprecated. Users are advised not to use those methods, as it might cause database inconsistencies.

Topo Notification Filter

• Currently, there is no flow control mechanism in the NotificationFilter to handle the condition where the notification rate from the topology module is much higher than what the NotificationFilter can handle. So, the user's implementation of the NotificationHandler has to be efficient, otherwise there will be a negative impact in the performance of the NotificationFilter.

Client Framework

• Authentication and Authorization is not possible while using RMIClientAPI.

• For delete type updates , no add update is sent resulting in a view with lesser number of objects than the viewLength.

• If you use the DBXmlTool to update the Tree.xml from the database, the comments will not be preserved.

Java Client Framework

• Client does not support the existence of multiple instances for the Network Database and Performance panels. Currently it is supported for Maps, Events, Alarms, and user-defined panels.

• Currently, the default NMS Panels shown in the Client, namely Events, Alarms, Network Database, and Performance, are not extendable for user customization. Limited flexibility is provided in extending the Map Applet in Web NMS 2.3 Release. This limitation will be addressed completely in the future release, where the client will be moving toward a much more component based UI model.

• Disposing of the default NMS Panels, namely Events, Alarms, Network Database, and Performance, (excluding Maps) from the memory based on the parameter setting DEFAULT-CLOSE-OPERATION is not supported as of this release.

• Sorting will not work for a column which is present in more than one database table. (For example, hostNetmask column is present in SnmpNode and SnmpInterface tables).

• The Failover feature is not supported for Browser Client. The other probable situations where the failover mechanism do not get applied are as follows:

• There can be a case where client applications that use RMI APIs detect the Failover earlier than the Client Framework. In this case, at the time of failure identification, the application may not have the information about the new FE to do subsequent lookups, they may require to wait till the Client Framework notifies them. The probability of this occurrence is very remote (Worst case scenario).

• Let us say, some requests have been sent properly and the response does not come at all to the request, if failover occurs in between. So, sessions must have some timeout mechanism and if the response does not come at that time then resend the request.

• When the number of Ethernet and Serial connections are more for a router, in the Routers map, the rendering may not be proper and few map symbols may go out of the boundary of the router base image.

Web Client Framework

• Configuration Management module is not available in the Web Client.

• Custom Views based on user properties cannot be created.

• When the Server is started in non-X window mode in Linux, the Web Client cannot be invoked. Workaround before starting the Server:

  • Edit the startnms.sh file located in the <Web NMS Home>/bin directory and set -Djava.awt.headless=true

  • Compile all the JSP files with JDK1.4 using compileJSP.sh located in the <Web NMS Home>/bin directory.

• When you add a custom map symbol (other than what is provided by default), you need ensure that the menu link (for the map symbol) is provided at the same location as provided in the default map symbol (bottom right corner). If not, usability issues while invoking the symbol menus could arise.

• Map-related operations, such as moving and grouping map symbols and zooming maps are not possible in Web Client.

• Reports will not be available in Timesten and Informix databases.
• New Home Page and Reports module will not be available in DMS.

Fault Management

• SNMP v3 Inform requests will not be handled.

• If database does not allow batch processing even though you set MAX_ALERTS_PER_BATCH as >0, separate queries will be used for each Alert manipulation.

• When Events are deleted based on CLEAN_EVENT_INTERVAL parameter or by invoking EventAPI.purgeEventDB() method, the registered Event observers will not be notified.

Configuration Management

• As there are no proxy servers for configuration module in FE, ConfigClients using a separate TCP connection can connect to ConfigServer on BE only.

• Group-based task configuration is not supported.

• The templates and nonpersistent pending tasks are not stored in the database. Hence, configuration of devices is not done based on these during the next startup.

• Only "get" and "put" commands can be used in the FTP task.

Performance Management

• User properties can also be set to the PolledData using Polling.conf itself, but these user properties will not be received in the PolledData given for providers. They have to be obtained by the user, explicitly in the provider class.

• Performance module Custom Views are not available in the Web Client.

• Current Statistics cannot be plotted for Expression OIDs.

Security Services

• The maximum number of characters allowed in the password is not configurable, and is hardcoded to eight. This is done to restrict the encrypted password length to less than fifty characters as specified in the security database schema.

• Changes made to the security database, either from the UI or through the API,  are not dynamically notified to the Security Administration UI. The UI has to be manually refreshed to reflect those changes.

Tools

• Using the Deployment tool, if the HTML UI component is unplugged, the login page still displays the HTML UI option.

• Conf updation in DatabaseSchema.xml will not be done during Deployment of Web NMS. Due to this, tables for unplugged components will be created in the Database which is harmless.

Management Server

• If screens using Management Client (for example screens built using Chassis Wizard and Configuration Wizard of Client Builder) are invoked from Applets over JDK 1.4 plug-in, Security exception related to XML writer will be thrown. To overcome this limitation, the following entry has to be added in java.policy file present in <Java Home>/lib/security directory.

permission java.util.PropertyPermission "user.dir", "read";

EMS - Tutorial

• When the user wishes to increase the number of Ports, Slots, etc., in the Chassis View he has to modify the bundled Chassis project to achieve the same.