DFM is the one application in LMS that does not and will not respect DCR display names. This is due to the way the EMC/Smarts engine manages the devices. You can adjust the way DFM resolves device names by changing DisplayNameFormat to MIBIISYSNAME in NMSROOT/objects/smarts/conf/discovery/discovery.conf, then re-adding your devices to DFM.
Of course, the other way to fix this is make sure that the IP address of the device resolves back to a hostname using the system resolver (i.e. test with the NMSROOT/bin/resolver.pl tool).
As for DFM duplicating devices, you may see instances where devices such as MSFCs get duplicated in DCR. This behavior can be turned off by editing NMSROOT/objects/vhm/config/inventorycollector/InventoryConfig.conf, and changing EnableContainedDevDisc to false, then restart dmgtd.
DFM uses the IP address of the device if the IP address cannot resolve to a host name(As configured in DNS). DFM does not consider the display name that you provide while adding to DCR(Common Service DCR display name).
In short, DFM will use the host name if it can resolve the IP address(during the discovery) else displays the device as IP address.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...