cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4192
Views
5
Helpful
11
Replies
Highlighted
Beginner

Device collection failure on Cisco Prime version 3.4

  1. Cisco Prime is running on VM (standalone)
  2. CPI running on 3.4 Update 02 and Device Pack 9
  3. Showing collection failure for couple of devices models, Not with particular model.
  4. Issue is seen since last 6 months
  5. Deleting and re-adding the device is fixing the issue temporarily but again all these devices go into collection failure state.
  6. Seeing below error on collection failure bar

 

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

 

 

  1. Issue seen for below devices for now. This might change and we see issue for couple of other devices.
  2. Device model 3850  software version 03.06.08E
  3. Device model 3850  software version 03.06.08E
  4. Device model 3750  software version c3750e-universalk9-mz.150-2.SE11.bin
  5. Device model 4331 Software version isr4300-universalk9.16.03.06.SPA.bin
  6. Device model 4321 Software version isr4300-universalk9.16.03.06.SPA.bin

Any solution would be appreciated.

 

Regards

Binny

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Hi Galleon,

 

Cisco has done this and fixed the issue.

 

We have changed the SNMP timeout to the default value and apply this workaround from Prime CLI:

 

 

Ø  Stopped the PI server "ncs stop"

 

Ø  Issued:

cd /opt/CSCOlumos/xmp_inventory/xde-home/inventoryDefaults/

 

Ø  edited the file:

vi XdeIOSExt.def

 

 

Ø  added the below line into XdeIOSExt.def file before </inventoryDefaults> line

 

<default attribute="SNMP_FORCE_GET_NEXT">true</default>

<default attribute="SNMP_MAX_OIDS_PER_PDU">30</default>

 

 

Ø  Then saved the changes and restart the server using 'ncs start"

 

Regards

Binny

View solution in original post

11 REPLIES 11
Highlighted
Hall of Fame Master

Binny,
I have only seen this when there was an issue with the login. For example, what I have seen on Cisco controllers was that when I initiated an SSH session, I had to hit a key to get to the login prompt and that caused an issue. I had to reboot the controller to fix the issue. I have not had any issues with switches or routers.
Might be good to also open a Tac case.
-Scott
*** Please rate helpful posts ***
Highlighted

Hi Scott,

 

Thanks for your response.

Let me try with anyone else has seen this issue and if I can find a solution.

 

For me it looks  like a buggy behavior.

 

Regards

Binny

Highlighted

Prime gets buggy especially if you upgrade from train to train. A fresh install has always worked better and is preferred. So for example, if you were on 3.2 and then upgraded to 3.4 where you are at now, you could run into some stale entries or behaviors that the dev team would need to fix.
I think if you remove the device and it’s the same device that fails, look at the device. However, if once you remove it and that solves the issue, then you would have to remove the others and add it back. From what you posted, it seems like it’s the same devices that have issues.
-Scott
*** Please rate helpful posts ***
Highlighted

Hi Scott,



Yeah that's right it has many buggy behavior as you said and even I suspect this might be the issue (stale entries on the DB even after the upgrade), But not sure what is causing the issue.



It's not with particular device model, It varies from device to device.



When I try to resync the devices which are having issue I get 1 or 2 more new devices with collection failure issue.



Looks very strange.



Regards

Binny


Highlighted

What happens if you delete a device, wait 15 minutes and then add it again? Will the collection for this device work again?
Highlighted

Hi ,

 

Deleting a device and re-adding after 15minutes fixes the issue. But as I told it is temporary.

 

Binny

 

 

 

Highlighted

I understand, maybe someone else here can help you. My suggestion is to open a Tac case and have then review the logs as you would get the answer quicker for something like this.
-Scott
*** Please rate helpful posts ***
Highlighted
Beginner

Hi ,

Were you able to find a solution for this issue. We are seeing this issue with Prime 3.3 and 7510 WLC running 8.5.131.0 code.

 

Thanks,

Manish

 

Highlighted

Hi Manish,

 

I have logged a TAC case and its with BU team. Still finding an resolution for this.

 

I would suggest you to try the below and see if it helps.

1. Delete the device from prime and re-add.

2. update the PI with latest device pack (Device-Pack-10-PI3.4-09.ubf)

3. update with all latest MR release (PI_3_4_1-1.0.27.ubf and PI_3_4_1_Update_02-1.0.9.ubf)

4. If none of these work, try reaching TAC.

 

Let me know how it goes.

 

Regards

Binny

Highlighted
Beginner

Hi Binny,

I am having the same issue, however mine seems to be with the Cisco Catalyst 3850 24P switched only.

If you have resolved this issue please share, also if there is anyone else with a resolution.

Thanks

Galleon

Highlighted

Hi Galleon,

 

Cisco has done this and fixed the issue.

 

We have changed the SNMP timeout to the default value and apply this workaround from Prime CLI:

 

 

Ø  Stopped the PI server "ncs stop"

 

Ø  Issued:

cd /opt/CSCOlumos/xmp_inventory/xde-home/inventoryDefaults/

 

Ø  edited the file:

vi XdeIOSExt.def

 

 

Ø  added the below line into XdeIOSExt.def file before </inventoryDefaults> line

 

<default attribute="SNMP_FORCE_GET_NEXT">true</default>

<default attribute="SNMP_MAX_OIDS_PER_PDU">30</default>

 

 

Ø  Then saved the changes and restart the server using 'ncs start"

 

Regards

Binny

View solution in original post

Content for Community-Ad