cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
777
Views
5
Helpful
8
Replies

Same device type add in dcr fail

ebezombes
Level 1
Level 1

Hi,

Customer has LMS 2.6 on solaris 9. Since he has upgraded LMS to CS 3.0.6, Campus 4.0.10, RME 4.0.6 and dfm 2.0.10.

In dcr he has added devices which are not reconized, it appears like "?" icon. Device with same type were added without issue before upgrading.

He has verified credentials, no failure credentials are good.

Any idea ?

Many thanks,

Elisabeth

8 Replies 8

Joe Clarke
Cisco Employee
Cisco Employee

If the device appears as unknown with a ? icon in the device selector, it is most likely because no application has tried to manage it yet, or the SNMP credentials are incorrect in DCR. How were the SNMP credentials verified? also, check that the device has been added to one of RME, Campus, or DFM.

Hi,

SNMP credentials are correct in DCR. Customer has test with RME->DeviceManagement->DeviceCredentialVerificationJobs (snmp read, write, telnet, enable).

Customer has export credential to csv file. We can see all informations.

In RME, devices are in pending state.

We try to see if devices are in Campus, but Device Discovery-All Devices Report was too long to generate.

Right now, customer is doing a stop/restart dmgtd process.

Elisabeth

What type of device is this? If RME is able to verify credentials, the device should already be supported in the MDF, so the icon in the device selector should not be a ?.

The same type of device are already correctly discovered by LMS, but it was before the upgrade.

After the upgrade, newone are discovered with ?

Do you think that can be an issue with database ?

Elisabeth

I doubt it, but so far I've had to guess as to what you are seeing. A clear screenshot would be useful as would knowing the exact type of devices affected.

Here you can find snmp request on sysoid for one device correctly discover and one device with ? There are the same.

Yes, the Cat4503 is supported in RME. However, you have not provided a screenshot showing the exact problem.

Customer has reboot server, issue doesn't exist anymore ... Sometimes rebooting server does help :)

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco