In the HUM Poller Creation , we have an option to “poll all instances”. I am checking it because I want to poll all available instances on the device so that complete information about all devices is available for device statistics like Top N/Bottom N Utilization/Errors etc. .. on the HUM portal..
In the Poller Status, I see some errors and the failure status is “Permanent” and the reason is “NoSuch Instance - The specified instance is not available”. I don’t see any reason why this is happening, because HUM itself is polling the devices and fetching the instances available & it is throwing an error saying instance is not available. As per my understanding (Please correct me if I am wrong !), It makes sense if the failure status is “Transient” which would mean that device is down/SNMP credentials are incorrect/SNMP request time out . However I see the Failure status is “Permanent”.
Could any of you please tell me why this is happening ?
Also please let me know how do we avoid “Permanent” Poller failures ?
These are usually sub-interfaces or those not supported by HUM (can also be due to bugs). You should go ahread and remove polling from the error prone interfaces after confirming that they actually exist on the device.
The 'all instances' option is not suitable for most environments. You must chose the interfaces manually to perform adequate polling.
Thanks for your reply.Manually choosing the interfaces is a good option. But, it becomes very tedious and time consuming when the number of devices and their assosiated interfaces becomes very large. I was wondering is there's a way to automate this ., as in HUM should poll only those interfaces which are operationally up.
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationConfigure one of the connectivity options to access the Cisco IMC from the n...
Firepower Threat Defense (NGFWv) on UCS E-series - Transparent Mode in HA
DocumentationCode download linksGoalRequirementLimitationsSupported ISR and UCS-E ModelSupported ISRG2 and UCS-E Blades:Supported ISR4K and UCS-E Blades:Step by Step ConfigurationCo...
I am currently unable to specify "crypto keyring" command when configuring VPN connection on my cisco 2901 router.
The following licenses have been activated on my router :