"telnet window" feature in client, using RMI communication mode will
not work, in the case of firewall NAT environment. Due to this reason,
TCP communication mode can be enabled for "telnet
window" feature in client,
but with the following limitations. Automatic
login and SSH will not
work in "telnet window" in TCP communication mode. Currently, the
"telnet window" feature is available only for clients connected to
BE-FE combo and not available for stand-alone FEs.
V3 Parameters configuration GUI is not available in web client MIB
multiple interface machine, the "Terminate Client" option will be
enabled if the server is connected in the one IP address and the web
connected to the other IP address.
the web client "JVM Management" page, the "Select Period"
combo box will retain the value previously selected until it is changed
again even, if the tabs are traversed.
V3 parameteres cannot be configured
from Web Client.
"ZoomWindow" is not supported.
Restoration of data backed up in Oracle in
SYBASE database will fail. Similarly restoration of data backed up in
Sybase / MSSQL fails in MYSQL.
StatusPolling.conf file, the list of ManagedObject properties that are
to be fetched during status polling can be specified. These properties
will be fetched and provided to the UserTeser if user defined status
polling is enabled for that ManagedObject. In these property list, topo
user properties cannot be specified. The specified topo user properties
will be ignored while providing the property list to the UserTester. To
overcome this issue, instead of using topo user properties, it is
highly recommended to use dynamic schema extension to include those
additional properties. When dynamic schema extension properties are
specified in StatusPolling.conf, it would work as expected.
a group object is one of the object to be deleted in a cascade
operation (delete with level), then the groupNames property of its
group members will not be updated with null value.
columns to view passed for getSqlString method should always contain
name. So that the returned query when executed will contain object name.
deleteObjects and deleteObjectAndSubElements(String, int), if any of
the object to be deleted is an interfaces(IpAddress and its extended
objects) then query and keys passed in the notification will not have
their children keys if any.
The getAlerts(Alert) method returns null if
the Alert passed as argument is null or if an Alert with no property is
passed as an argument.
Load Filters option, loads the filters from
alert.filters or event.filters files only. If these configuration files
are renamed, filters will not be loaded.
RMI shutdown will not happen when server is running in RMI secure mode.
At present, the Web NMS standby BE server
cannot be gracefully shut down using the shutdown scripts
(ShutDown.sh/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 the server is by using the Ctrl + C interrupt.
The exception "org.hibernate.ObjectNotFoundException: No
row with the given identifier exists" is displayed in the logs
when loading an object in hibernate. This occurs when one thread is
loading the object while another thread may have deleted the same
object, thereby invalidating the entry in the cache.
This harmless hibernate log print is disabled by default in WebNMS.
However, if the messages appear in the logs, please check that the
following entry is present in <WebNMS
reinitializing the Web NMS server without any log files under the <Web NMS Home>/logs
directory, a fresh list of
empty log files will be generated.
The PREPAREDSTATEMENT returned from
getPreparedStatement() and fetchPreparedStatement() of ConnectionPool
API will not timeout based on PREPAREDSTATEMENT_TIMEOUT.
Chassis Wizard can be run in JDK1.6 along with the endorsed mechanism
implementation. Please check the installation guide for more details on
endorsed mechanism in Studio Tools.
(No such file or directory) is displayed when running a screen created
with build type Applet.
is issue when using columnar variables from multiple tables in a group.
Internal Error :There is no such variable name in this MIB.Property :
running a configuration screen in the configuration wizard, if a new
index that is not present in the table is given, the following error is
thrown. Internal Error :There is no such variable name in this
MIB.Property : ifAdminStatusInstance_prop1
client is terminated from the Web Client UI, the notification from LILO
states as CLIENT_COMMUNICATION_FAILURE. It should have been like
the value for any of the not-null column is null, then search or fetch
for (!)NOT condition based on such columns will not return rows with
getObjects() method in CommonAPI, the properties in the User Properties
table such as TOPOUSERPROPS, MAPUSERPROPS, ALERTUSERPROPS etc, cannot
be used as criteria. Also the fetched object will not have these
installing the product in Windows Vista in Program Files folder, there
will be issues when any user other than the "Administrator" user uses
the product. This is because of the Security Checks in Windows Vista.
To overcome the issue, the product must be installed in a folder
structure other than "Program Files".
Utilization for the BE/FE server in JVM details will be fetched only if
the BE/FE machine is a SNMP Node.