General

• If a Solaris OS user switches between JDK versions say 1.3 and 1.4, he may get a message dialog stating "Inconsistent date setting", resulting in the product not getting started.
• If you start tnameserv in a remote host which has "-" in its name (like linux-server), then you cannot bind the CORBA APIs of Web NMS in that remote Naming Server. This is due to a limitation of Java IDL Naming Service.
• When Web NMS is started as a Service, Apache gets killed when the user logs off from Windows.
• J2SE 1.4 does not support IPv6 on Microsoft Windows. In Web NMS, IPV6 support is available only for Linux and Solaris.
<>When upgrading from Web NMS 4 + SP2 + WEBCLIENT.ppm,  JDK1.4.2 and above should be used to compile the JSP files. If the JSP files are compiled using any lower version of JDK in this setup, the server crashes when you connect the webclient.

Studio

Services

• When a Custom Discovery Filter is deleted in Windows with JDK1.4.X series, its corresponding files will not get deleted. 
  Workaround : Delete the files manually from the project and proceed with creation of new discovery filter with the same name as the deleted discovery filter.

CVS Client

• All projects can be stored only under the Repository root directory. CVS Client does not support remote target directory.
• The CVS Update functionality in CVS Client does not work.
  Workaround : Check in the Project and then do a Project checkout.

General

• In the Tutorial projects bundled in Studio, a duplicate entry error will be thrown if clientparameters.conf, WebNMS.jnlp and launcher_conf.txt are found in the "Other Resources" screen of Packager Wizard. This is because the above files are now being packaged by default by the Studio Packager.
  Workaround: While packaging remove the above three file entries from the "Other Resources" screen of the Packager Wizard.
• In Studio if selective packaging is done, the .properties files present under the html directory, will not get bundled, hence use Complete Packaging option if Rebranding Tool is used.
• When using JDK1.5 with Studio, the xalan.jar entry must be removed in <Web NMS Home>/StudioTools/Studio/setEnv.bat/sh file. Else the exception "IOException occurred when trying to write to file" with Type "javax.xml.transform.TransformerException" error message will be displayed on creating the Studio project.
  Also when deploying the nar using the Deployment Wizard, if you are using JDK1.5, ensure that the xalan.jar entry is removed in the XML_CLASSPATH in setEnv.bat file / folder.
  If you are using Window XP, then you may face additional errors. In that case, please refer to the Notes in the Installation Guide for resolving the issue.

Client Builder

• Multiple SNMP and TL1 Agents can not be started from Non UI Agent Tool.
• Two tier Applet option in Client Builder will not work for TL1 applications.
• If JRE1.4.2 is used, Configuration screens with 3 Tier Protocol Neutral Option cannot be invoked in Applets. This happens because when the JRE1.4.2 tries to read the XMLEntities.res file java.lang.ExceptionInInitializerError is thrown. This is an issue with Xalan-Java bundled with JRE1.4.2. Refer the Changes for Xalan-Java 2.5.0 : Committed by mkwan@apache.org on 2002/09/06  
  Workaround : Add the following entry  in the java policy file of the JRE plug-in that is used by the Applet.
  permission java.io.FilePermission "<JRE Home>\\lib\\rt.jar", "read";
• In Chassis Wizard and Configuration Wizard (on Web NMS standard edition), it is not recommended to use TL1-related menus although they are enabled. Invocation of those menus might result in undesired behavior.

• In Linux-MySQL database, tables that are created dynamically have to be named with all upper case letters. If these tables are named with letters of mixed or smaller cases, they will not be dropped when the Web NMS database is reinitialized, as Linux-MySQL is case sensitive.
• While running Web NMS with Solid database, when two or more transactions try to update the same row, the first transaction which holds the row will succeed and other transaction(s) will fail with the exception "SOLID Database Error 10006: Concurrency conflict, two transactions updated or deleted the same row". The following is an example scenario where this exception would occur : During bulk delete operation, when the bulk delete is in progress, if status polling triggers update on the same row, the second transaction - updating the row - will fail with the concurrence conflict exception. The first transaction - bulk delete - will succeed.
• Enhanced SNMP V3 does not work in Web NMS with TimesTen database.
  
• AuditException would be thrown in the logs when starting the server with Firebird database. The following entries must be added in the DatabaseAliases.conf file present under <Web NMS Home>/conf to resolve this issue :
  

  #In Table AuthAuditExt
  authAuditId AUTHAUDITID
  module MODULE
  auditTime AUDITTIME
  auditedObj AUDITEDOBJ
  operation OPERATION

• JVM Monitoring Details will be stored in the database in NMS_STATUS_MONITOR% tables. These tables will not get restored properly if we restore the backed up file across databases. For example, if we restore a database backup file taken in Oracle into MySQL database, then the NMS_STATUS_MONITOR table related entries will not be created properly.
• When a database backup is done in Mysql 4 or earlier versions and restored in Mysql 5, exceptions will happen and will not be restored properly.Customers to contact nms-support@adventnet.com to fix this.
  

• Wild card pattern "?" will not work in the search criteria for the TopoAPI.getObjectNamesWithProps method.
• For DHCP nodes, when the physical address is not obtained, the DNS name is assigned for the managed object. And the ManagedObject is added to the database as unmanaged, that is the "managed" property set to 'false'.
• For non SNMP DHCP nodes as physical address of such devices across routers cannot be obtained, the DHCP nodes will have incorrect physical address as names. The physical address of such a node will be the router's physical address.
• When a Container object is deleted using the TopoAPI.deleteObjects() api, the "parentKey" property of the children objects will not be updated in the database. Hence, the childrenkeys in the database will still contain the reference to the deleted parent.  Similarly when a Network object is deleted using the TopoAPI.deleteObjects(), the parentNet property of the interfaces will not be updated in the database.  In general, the method TopoAPI.deleteObjects() updates only the cache and does not take care of updating the database tables.
• ENABLE_STATUS_POLL_BATCH parameter will not work with MSSQL database in the default Web NMS setup. This is because MSSQL does not support GROUP BY on IMAGE, TEXT & NTEXT data types, unlike ORACLE. To workaround this problem, refer to the article id 113081 at http://kbase.adventnet.com/webnms/search.jsp

• When ALERT_LOCK is disabled (set to 'false') and when different threads try to update the same Alert, Alert Count will be erratic.
• The value for the attribute "groupName" will not get updated on Alert update.
• "No Detail" category column in Alert Count Panel is supposed to display the Alerts whose category is "null" as well as "No Detail". But when clicked, it will display only those Alerts whose category is set as "No Detail".
• When a user transaction involving update over Alerts is rolled back, the count in Alert Count Panel will not roll back.

• When client explicitly specifies the ConfigServer to retain the sessions established between ConfigServer and devices, for further reuse, these sessions will not be closed when the client gets killed abruptly.
• When DEBUG mode is enabled and the DEBUG_LEVEL is 2, the SNMP packet dumps will not be printed.
• The ConfigServer is compatible with JAXP1.1. Earlier versions of XML parsers may have some problems.
• The result of configuring a TELNET/CLI task will always be "success" except in case of incorrect login parameters.
• There are a few XML parser-related compatibility issues when running BE and FE servers in same JVM (Single Server Deployment) in WebLogic environment.
• When providers returns result containing control characters, the XML parsers will give parse Exceptions.
• Password attributes are not encrypted.

• In Solid database, bulk delete and PollingObject deletion and modification will work inconsistently.

• A user can not be created with the name of an existing group and vice versa. This is because, when a group is assigned directly to an operation, an AuthorizedView is internally created with the name "default<groupname>View", and the permission is assigned through that AuthorizedView. The same thing happens when a user is directly assigned to an operation.  Thus, when a user is created with the name of an existing group and directly assigned to an operation, it will result in the user getting the existing permissions of "default<groupname>view" also.
• While creating the user without giving password, the same user name will be considered as the password. In that case, if the user name is more than eight characters in length, then due to the limitation in the product, the password can not be stored in the security database, resulting in the user add operation to fail.
• If a user belongs to multiple groups and if those groups have contradictory permissions for the same operation, then the user will be given the permission for that operation. But, the Security Administration UI may still display that the user does not have the permission for that operation. This is because the Security Administration UI does not resolve such  contradictions while rendering, unlike the authorization engine in the BE server.
• User defined properties (user properties and extended event/alarm properties) are not supported as criteria for the operations of Authorized Scope and for the Authorized Scopes of Custom View Scope (CVS).

• AdventNet Provisioning Framework provides the support for stateless and messaging based server using JMS (J2EE or TIBCO). The following issues are related to J2ee Server.
  • When you try to connect the Applet Client through the J2EE Server, AccessControlException will be thrown.
  • In linux, when you execute a template via the J2EE Sever using the OpenTemplate.sh. file, Segmentation Fault Exception is thrown. This happens occasionally and the workaround for the same is given below.

Workaround: Set the Stack size, using the following command
         ulimit -s 2000
         Here 2000 is the value in kbytes.

• When you invoke any of the provisioning templates which has more than one stage, using the TemplateTesterApplet.html or using the OpenTemplate.bat/.sh files and close the template window before performing the provisioning operation, the column header Status in the ActivityList panel displays the status as In Progress.

• The startIndex and endIndex may be inconsistent with the actual order when delete updates occur for custom views.

• Java Client Framework
  
• The DataFormCustomizer API customizability mechanism is not supported for Alarm Details, Event Parser configuration, and Trap Parser configuration forms.
• Occasionally, some set of NullPointerExceptions may appear due to Java Swing issues.
• When you use special characters in naming a Theme file in the Theme Manager, it throws some exceptions.
• Comment nodes in Themes.conf file are not preserved when the file is recreated (i.e., when a new theme is added).
• In JDK1.4, the browser (Applet) client does not support Internationalization of the date string ( AM, PM, Jan, Feb, etc.,) that appears in the Date Time component (displayed in the Property forms, Search dialog etc.).
• In JDK 1.4, and above versions, when an Internal Frame is detached and subsequently the frame icon associated with it is modified, the change will not be reflected in the detached frame.
• Escape key sequence associated with the "Cancel" action of  the various dialogs in the client will not work in JDK 1.4.
• The Java Web Start client can be launched from the Netscape 6.0 (and above version), Opera, Mozilla, and Konqueror browsers only when a workaround which involves modifying the Login.jsp and WebStart.jsp files located in <Web NMS Home>/jsp directory is performed. More details on this is available in the chapter named QB-Application, Applet and Web Start clients.
• The usage of special characters such as "semi colon" in the text fields of the Custom View Properties form is not accepted.
• In a Linux OS with JDK 1.3, when you provide the user name and a wrong password in the logging-in authentication dialog, a warning message pops up  stating that it is an invalid authentication. When you click OK, the authentication dialog is in a collapsed state.
  
• In Web NMS 4.7 SP2, when the Add Node dialog is internationalized, the Add Node button does not function properly. Please get in touch with us at nms-support@adventnet.com to get a patch that fixes the problem.

 
• Web Client Framework 

• Apache returns garbled response in Opera 7.21 in Solaris platform, when pages with large content is requested. 
• Struts validator dumps java script for all the validation rules (Java Scripts) defined in the validation-rules.xml , to the html page, even though the input form present in the html page uses only selective rules for validation.
  
• When you start Web NMS Server, after reverting SP1 from 4.0.0+SP2+Web Client PPM+SP1 setup, the server is shut down gracefully (after the processes are initialized). Workaround: Perform the steps given below to fix this problem.
  1. Edit web-header.xml file located in the <Web NMS Home>/WEB-INF directory and remove the following entries.
     <servlet>
     <servlet-name>jsp.index</servlet-name>
     <servlet-class>jsp.index</servlet-class>
     </servlet>
     
     <servlet>
     <servlet-name>jsp.WebStart</servlet-name>
     <servlet-class>jsp.WebStart</servlet-class>
     </servlet>
  2. Edit web-footer.xml file located in the <Web NMS Home>/WEB-INF directory and remove the following entries.
     <servlet-mapping>
     <servlet-name>jsp.index</servlet-name>
     <url-pattern>/jsp/index.jsp</url-pattern>
     </servlet-mapping>
     
     <servlet-mapping>
     <servlet-name>jsp.WebStart</servlet-name>
     <url-pattern>/jsp/WebStart.jsp</url-pattern>
     </servlet-mapping>
  3. Execute compileJSP.bat/sh file located in the <Web NMS Home>/bin directory.
  
  
• The Polled Data listed below needs to be commented to prevent the DataTruncation error in FireBird Database.

RouterMemoryUtilization
RouterSmallBuffHits
RouterMedBuffHits
RouterBigBuffHits
RouterLarBuffHits
RouterHugeBuffHits
CiscoSwitchMemoryUtilization

AdventNet Web NMS Agent

• When the number of events exceed the specified limit i.e. above 10000, the values are not displayed in the Event Table of Web NMS Agent.
• In the HTML Agent, all tables have the Add, Modify and Delete buttons by default. This is present even for tables in which any property cannot be set, modified or deleted. Thus for these types of tables, when you try to set, modify or delete some property, exceptions are thrown.

• The Rebranding Tool does not rebrand the new Web Client.
• Conf updation in provider.xml will not be done during deployment of Web NMS using the Deployment Wizard.
• In NmsProcessesBE.conf and NmsProcessesFE.conf, comments for each process is mandatory. If a process exists without comment, conf updation will not be done for that process, which might introduce problems during NMS Server startup after Deployment using the Deployment Wizard.

• At present, the Web NMS standby BE server can not be gracefully shut down using the shutdown scripts (ShutDown.sh or ShutDown.bat). This is because the standby BE server will always be in a state where it only keeps monitoring the health of the primary BE server and behaves as a totally closed application. The only way to shut it down is to kill the process forcefully.
• The JVM Monitoring Details will not get collected for the client that is connected to the primary server after failover.
  

• If a data fetching operation is performed for a custom view while the updates come at a fast rate (at about 20 traps/sec or more), the from index, end index, and total may have incorrect values. This is because when the BE server processes an event, it updates the database and puts the event in a queue for the FE server to process it and also updates the clients. If the events come at a fast rate, it becomes too heavy for the FE to process that the queue size becomes large.  In such a situation, if we start traversing between views, the FE fetches the data from the DB which will have the actual data, but the queue will have older data. So, when the FE processes the data from the queue based on the new set of data fetched from the database, the indices go wrong and as a result the from index, end index, and total will have incorrect values. The actual values can be obtained by manually refreshing the view.
• Custom View related operations will work only in the databases which are supported, by default, by Web NMS. This is because the custom view framework employs database-specific things (for example joins in sql queries) which may not be supported by other databases.
• In MySQL Client/Server protocol, all the data transfer between the client and server takes place in the form of packets. A communication packet is a single SQL statement sent to the MySQL server or a single row that is sent to the client. In such a case, when a query length exceeds certain limit, MySQL client or the MySQL server gets a packet bigger than the max_allowed_ packet bytes (which is a configurable parameter in MySQL). In this situation, MySQL issues a "Packet too large" error and closes the connection. This max_allowed_packet size varies in different versions of MySQL. For example, in MySQL 3.23, the biggest possible packet size is 16M. So, whenever the particular packet size exceeds this limit, "Packet too large error" comes. This can be avoided by increasing the max_allowed_packet size. Information on how to change this is available in the following url : http://www.mysql.com/doc/P/a/Packet_too_large.html.

• When the standalone FE server is started in the mode where the configuration files are not downloaded from the BE server, and if the FE server is configured to connect to a different RDBMS than that of the BE server, it results in the FE sever starting up and connecting to the BE server, but both of them working with different RDBMSs.
• Boolean performOR set as true in CustomSessionRemote.getData() method may not return proper results, if the criteria contains user properties.

• In UNIX, if the system date is changed when NMS Server is running, green thread continues sleeping. This problem is due to some limitations in Java.
• If Web NMS is installed in a directory with the directory name containing a space (for example /home/Program Files/AdventNet/ WebNMS), the Web NMS server will not start in linux. This is because, the start and stop script files of Web NMS do not support directory names containing spaces.

• The reinitialize script (reinitialize_nms.sh or reinitialize_nms.bat) does not allow the Web NMS database to be reinitialized when the Web NMS BE server is running. But if the reinitialize script is invoked before the BE server gets fully initialized, it drops all the database tables created so far. This is because the BE server behaves as a fully closed application till it gets initialized completely, and thus the reinitialize script can not know about the existence of the BE server and it allows the database to be reinitialized.

• While running the toolkit using JDK 1.4, the Cut, Copy, and Select All operations are not supported in the frame where the log messages are displayed.

• In the XML tutorial, connection will not be established between the XML Agent and Web NMS server during warm start.
• For working with TL1 tutorial (in Web NMS 4 SP2 only), download the same from site  and make the following change.
  • Open the clientparameters.conf file present in TL1 tutorial Studio project and remove jfreechart.jar and jcommon.jar from ARCHIVE list.
• The HTML Client cannot be invoked from the EMS tutorial.
• When GES tutorial is compiled with JDK1.4, the following error is thrown. As a workaround, use JDK1.3 while compiling GES tutorial.

error: The method org.jgraph.plaf.basic.TransferHandler getTransferHandler() declared in nested class org.jgraph.plaf.basic.TransferHandler. JAdapterComponent cannot override the method of the same signature declared in class javax.swing.JComponent. They must have the same return type. 

• On clicking 'browse' button to load Command Set / Data Set into CLI Browser, files present in <Web NMS Home>/conf directory are listed by default instead of <Web NMS Home>/ccs directory. Please change directory to <Web NMS Home>/ccs to list command / data sets packaged with Web NMS.
• On clicking browse button to load script files to run from the CLI Browser, files present in <Web NMS Home>/examples directory are listed by default instead of <Web NMS Home>/examples/script directory. Please change directory to <Web NMS Home>/examples/script to list script files packaged with Web NMS.