HUM1.2 - Erratic Interface Utilisation Polling

[glenn.ong]

Hi experts,

Ever since our HUM was upgraded from 1.1 to 1.2..there is this strange behaviour where the Interface Utilisation template on an existing poller (which worked without a hitch in 1.1) would produce no data for 1-2 days, then working again for approx. the same number of days and then off again.

Restarting upm process doesn't seem to have any effect. upm_process.log and upmprocess.log shows nothing particularly interesting except this:

"

ERROR,[SNMPThrPool1057],com.cisco.nm.upm.pollingengine.UPMGenericResponseHandler,performComputations,680,EvaluationException occured for the device: <RouterIP> for poller:RouterPolling"

This only occurs for the Interface Utilisation template...all others (cpu utilisation, etc) works fine (continuous data across any period) so it's safe to rule out any polling/connectivity issue.

Would post the full log if required but has anyone come across this before?

Thanks in advance.

[Joe Clarke]

The expression engine used by HUM must not like one of the variables in the interface utilization calculation. The interface utilization template is unique when compared to some of the others as it needs to use a calculation to generate the utilization value.

More debugging would be required when the poller is not producing any data in order to determine why this is happening. I suggest you open a TAC service request so this analysis can be done.