cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
3466
Views
0
Helpful
2
Replies

Partial Collection Failure (Unknown Error)

g.raymakers
Level 1
Level 1

 

Hi,  I've been trying for several days to discover a 9800-80 running 16.12.2s code on a DNA-C running 1.3.0.6 code. The software version should be OK according to the compatibility matrix. netconf is enabled on the device, the ports match between device and DNA-C (netconf is enabled on the discovery profile as well).  Credentials are OK and the needed aaa commands for local autentication and authorization are also there. The status in the inventory is always " Partial Collection Failure (Unknown Error)". Has anyone run into the same or similar problem? 

Thx,

Guy

2 Replies 2

Dan Rowe
Cisco Employee
Cisco Employee
Partial Collection Failures could occur for multiple reasons. Unfortunately for Partial Collection Failure - Unknown error, the symptom is much less obvious and will require some digging to determine the root cause. I would attempt the following to rule out a possibility that it could be a DB issue with this specific device:

1. Delete it from the DNA center inventory
2. Log into the DNA CLI and run the following command while logging the console output:
-- magctl service logs -rf inventory-manager | lql
** If you receive an error that multiple inventory-manager services exist, open up another CLI session window, copy the exact name for each inventory-manager service and run the command above on each CLI session **
3. While the output is collected from the CLI sessions, please re-discover the 9800 from the DNA center appliance
4. Once successfully discovered, let the console sessions continue to collect the output from the inventory service logs until the device either goes into a Managed state or fails back into partial collection failure.

If the device goes back into partial collection failure, please upload the console output files to this discussion thread for further analysis.

LeroyW
Level 1
Level 1

At least for the 9800CL, we've found that it needs the

shell:priv-lvl=15

for the user that will connect. Have you tried setting that?

Review Cisco Networking for a $25 gift card