Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

fixing import issues

Hi,

after importing several devices to DCR some of them are UNKNOWN due to issues on the device side (wrong community, ACL, unreachable etc.)

When those are fixed, which is the best way to make DCR query again the devices for their type ?

Thanks in advance,

Alex

Everyone's tags (1)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

Re: fixing import issues

Correct.  RME is most likely the app which populates device type and MDF data into DCR.  DCR will not query the sysObjectID itself.

Yes, in a multi-server setup, the slaves will sync all DCR data from the master.  They will get the same updates that the master gets.

3 REPLIES
Cisco Employee

Re: fixing import issues

DCR does not communicate with devices itself.  It uses the other LMS applications to figure out the device type.  Therefore, simply resubmit the device for inventory collection in RME, or perform a new Campus Data Collection, or submit the device for management into DFM.

Community Member

Re: fixing import issues

So when I add one or more devices to DCR and in a few minutes I see that the device type has been updated, this is from the initial RME inventory collection? I thought that just adding devices makes DCR query the sysObjectID.

A related question: In a multi-server setup this sysObjectID update is propagated to the slave DCRs ?

Cisco Employee

Re: fixing import issues

Correct.  RME is most likely the app which populates device type and MDF data into DCR.  DCR will not query the sysObjectID itself.

Yes, in a multi-server setup, the slaves will sync all DCR data from the master.  They will get the same updates that the master gets.

297
Views
0
Helpful
3
Replies
CreatePlease to create content