Prime "Partial Collection Failure" since estate upgrade

[lowfell]

Prime "Partial Collection Failure" since estate upgrade 93/9500 switches to 17.12.4 only affecting a  one site but not all devices.

We reead somewhere that  if config identical, removing the devices from prime's inventory, then verifying credentials before putting them back in may assist with this. if config identical, removing the devices from prime's inventory, then verifying credentials before putting them back in may assist with this. This is the post

https://community.cisco.com/t5/network-management/cisco-prime-partial-collection-failure/td-p/4483422 
If we were to go down this route can someone walk us through the process as we are unfamiliar with how to remove then readd devices?


Current version of Prime is 3.9.0 & we could patch/upgrade to 3.10 however customer is loathe to do this as Prime is no longer supported, is that correct? can a TAC case no longer be raised?

This is the snmp config on the switches
#sh run | section snmp-server
snmp-server group readonly v3 auth read readview access 15
snmp-server group PRIME-GROUP v3 priv read PRIME-VIEW access 15
snmp-server view readview internet included
snmp-server view PRIME-VIEW iso included

[marce1000 · Accepted solution]

   - @lowfell   Ref : https://www.cisco.com/c/en/us/products/collateral/cloud-systems-management/prime-infrastructure/prime-infrast-gen-appliance-lic-eol.html

                     Says :  Last Date of Support:  HW,OS SW  September 30, 2028

                    Actually because Prime is EOL ; the customer should use 3.10 with latest(last) patch.
                    3.10  is the only version which remains under support,

 M

[lowfell]

Thanks for your help. I'll advise customer to upgrade whilst they still can under support.