Users Guide
Discovering Resources | Getting Started
100 OMNM 6.5.3 User Guide
LLDP Warnings
Warning messages sometimes appear in the Discovery Audit Trail about LLDP. This occurs when
the device's LLDP information indicates that a component exists with LLDP enabled at a certain
IfIndex, but that IfIndex doesn't actually exist in the IfTable.
In other words, the information in the two SNMP tables does not match perfectly, OpenManage
Network Manager warns about the IfIndexes that are missing. This incongruity in the tables is
rather common and is not normally a problem, but OpenManage Network Manager still displays
the warning.
The only time it would be of concern is if the warning claimed that it could not match IfIndex
numbers that do exist in the IfTable, otherwise it's just a harmless warning that the LLDP table has
some bad data in it.
Incomplete Discovery
If the device is detected and responds to ping, but does not respond to actions (for example:
Resync or Adaptive CLI), you may have only partially discovered it. Right-click the device in the
Managed Resources portlet and select
Direct Access > Telnet
. If that menu option does not exist,
the device is typically partially discovered with SNMP only. Right-click to edit the device, and add a
both Telnet Management Interface and Authentication in those two tabs of the editor.
Configuring Resync
Resync now can retrieve, and if it is obsolete, update, the information gathered on initial discovery.
Fields retrieved/updated include SysDescription, Contact, and Location.
OpenManage Network Manager can also retrieve the device’s SysName to update the device's
Name
field on resync, depending on a system property. By default this is false, so no name retrieval
occurs on resync.
The property determining this behavior is in
owareapps\ddbase\lib\
ddbase.properties
. Here is how that property looks in
ddbase.properties
:
##Update Device Name on resync - 'false' turns this behavior off.
##Other options: sysname_ip , hostname_ip, sysname, hostname, and ip
##For example, to set this to use sysname + IP naming format, use
##com.dorado.devicedriver.base.updateName=sysname_ip
com.dorado.devicedriver.base.updateName=false
Best practice is to override the default in
owareappse\installprops\lib\installed.properties
.
CAUTION:
This property overrides the discovery profile’s Device Naming Format convention selected. This can be
useful if you want to force discovery to use a particular naming convention regardless of how others may
have configured the Discovery Profile that initially retrieves information about the device discovered. It
may be less-than-useful if a Resync action that follows or is part of the discovery process provides
naming you do not want.
If you elect the default, resync still updates SysDescription, Contact and Location, but does
not
update SysName (
Name
).