Cisco Prime version 3.0.4 Partial collection failure. Nexus and ios device synchronization is not happening. Any Idea

[sarwar1986]

collection failure with nexus and ios device

[m.holfeld]

I have this problem to.

version 3.1

Collection Status Details Help Pin Close

Collection Status : An unexpected error has occurred:
# Check the device is in supported device list in deployment guide.
# Check there is connectivity between the device and Prime Infrastructure
# Check the device credentials provided are valid
# Finally if the problem still persists then contact Cisco System's technical assistance center

[Hilario Martin]

Hi,

same problem with Nexus 5672 & NX 7.0(7)N1(1) and CPI 3.0.

Upgrade to CPI 3.1 with no improvement :-(

It looks like this these bugs are related to this issue:

CSCuy06078

CSCuv16175

CSCur02752 

CSCux91416

Any plans from Cisco to apply a new upgrade,  patche or device packet to resolve it?

Regards,

[Sebastian Helmer]

I have the same with 3.1 Device Pack 1 and WLC with SSO enabled 8.0.120.0 via SNMPv3 connected

[Martin Gramlick]

We were having this problem too with our Nexus and some IOS devices.  TAC walked us through increasing the timeout values for SNMP and SSH.  If you have a Credential Profile linked to your devices you can update just the Credential Profile and it will update all the devices.  That is what we did.  Or you can manually edit just the devices you are having problems with but that will break any link to a centralized Credential Profile.

SNMP Timeout = 100 seconds

SSH Timeout = 120 seconds

[christian.filips]

Troubleshooting by Cisco TAC that helped me:

1)The PI version used is 3.1

2)You had Collection failure of Nexus devices on PI

3)Found it to be the bug CSCuz50083

4)Applied the workaround in the bug.

- Replaced etherchannel_nexus-3.70.77.xar in

- /opt/CSCOlumos/xmp_inventory/xde-home/packages/standard/

 - /opt/CSCOlumos/xmp_inventory/dar/com/cisco/ifm/config/xde/etherchannel_nexus/3.70.77/

- checked by checksum that these are the same!

5)Deleted and re-added the devices, The devices were managed successfully.

Issue was resolved.