Open Manage Network Manager – Release Notes
12
account of this limitation. Workaround: Rename the interface with a telnet
session. (32594)
File Management
• You may experience difficulties when using 3CServer as your FTP server.
Workaround: Use 3CDaemon (8525)
• If you cancel changes while creating a new filter within the file server man-
ager, you must exit the filter editor then recreate a new filter before you can
save the filter. (11206)
• A “%1 in event message” error appears if you backup a device without a con-
figured file server.
• In some cases, “NetConfig” appears instead of “File Management” in
messages—for example in Audit Trail queries for type of audited messagess.
Event Management
• OpenManage Network Manager supports multiple IP addresses per resource.
During event processing, filters that include IP address criteria may behave
incorrectly when OpenManage Network Manager evaluates the filter.
Workaround: Best practice is using resource name(s) instead of IP addresses.
(PV-12532)
• The default polling interval is 5 minutes, but if you reduce the polling inter-
val, polling cycles maybe skipped depending on hardware resources, number
of devices being polled and network latency. (11959)
• Events with no corresponding definition appear as alarms of indeterminate
severity. The only way to change behavior of an unknown event in this ver-
sion would be to locate the missing MIB and load it into the system. This cre-
ates the missing event definition(s) needed to specify explicit behaviors.
• Northbound action can now send as proxy. With this option set, there are no
issues with XP’s security patch, Vista or Server 2008. The application attempts
to spoof sourceIP on packet only when the proxy option is not selected.
(1737)
• In Linux, the Event definition manager panel cannot resize when the cursor
changes to a horizontal bi-directional arrow sign. It can only be resized when
the cursor is showing as a arrow sign. (37741)
• Trap listener, Inform listener and all outbound SNMP requests must bind to a
specific interface in a multi-homed environment. This interface is considered
appropriate to use for all network-facing SNMP activity. By default, this is
localhost, interpreted as the application's local IP value (the NIC selected at
installation time). The following text in
installed.properties
(in \oware-
apps\installprops\lib) provides a specific IP address to control outbound
SNMP interface binding on the local machine (22258):
#
# specific interface used for all NMS initated
# communications to the network
com.dorado.mediation.outbound.address=localhost
(62 pages)
(190 pages)
(320 pages)
Manymanuals.com
Manymanuals.de
Manymanuals.fr
Manymanuals.it
Manymanuals.pl
Manymanuals.cz
Manymanuals.es
Manymanuals-pt.com
Comments to this Manuals