The sysobjectid in DCR is different form the correct one in RME
We have LMS 3.2 CS3.3 RME 4.3.1 Solaris 9
The sysobjectid in DCR is different form the correct one in RME for some devices and although update them by web database access and it was not reflected in the Ciscoworks portal also that device not appeared in Conflicting Device Types in RME. also I run job to update invotary and it's succeed but no change in Device Type.
I deleted one of them and added manually and its device type is correct type, May I delete all of them, and re-add again?
Re: The sysobjectid in DCR is different form the correct one in
Yes, this is clearly wrong. It looks as though when these devices were added to DCR, someone manually specified the sysObjectID (which is the wrong thing to do). At this point, RME should show them as conflicting devices. You should either correct the type in DCR, or simply remove the devices from DCR, and add them back. If you do add them back, leave the device type as UNKNOWN. This way, RME will update DCR with the correct sysObjectID and MDF type.
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 ...