Receiving below alert from the interface traffic probe: The max interface speed (ifSpeed) of Loopback on X.X.X.X could not be determined! Traffic alarms in percent of max speed cannot be issued. Please override interface speed or set alarm options on ac

book

Article ID: 7321

calendar_today

Updated On:

Products

DX Infrastructure Management NIMSOFT PROBES

Issue/Introduction

Interface_traffic probe generating the below alert:

 

The max interface speed (ifSpeed) of Loopback on X.X.X.X could not be determined! Traffic alarms in percent of max speed cannot be issued. Please override interface speed or set alarm options on ac 

Cause

The alert that you are questioning: 

"The max interface speed (ifSpeed) of Loopback on X.X.X.X could not be determined! Traffic alarms in percent of max speed cannot be issued. Please override interface speed or set alarm options on actual values." 

The above alert is coming from the interface_traffic probe. This probe will generate an alarm when the bandwidth (in %) alarms are enabled but it cannot get a speed from the device. To stop this alarm, either configure a speed manually under the Advanced tab in the interface_traffic probe or fix the issue if it is a problem with the device. You can verify this by right mouse click on Monitor on the interface and see if the Speed field is filled. We have seen this issue with certain Cisco devices, e.g., when speed auto-negotiation fails. 

Environment

UIM - 8.5

Resolution

-> Configure the speed using "Manual override" (Advanced Options) on those interfaces where you are getting the alarm(s). 

 

Optionally, this can be adjusted in your bulk configuration for this probe, by filtering on the agents then editing the "Modify Interface Values: Configure interface settings" dialog. 

 

In this dialog, under "Enable Monitoring" you will see two options: 

 

- using percentage (%), 

- using values (e.g. Mb/s) 

 

Change your monitoring to the "using values" section and you will no longer see the problem with the ifSpeed counter not being present on the device(s) you are monitoring. You will need to set a low/high threshold based on the amount of traffic you wish to alarm on. 

 

Alternatively, you can filter these alarms at the alarm server (nas) level by adding an auto-operator profile or pre-processing rule to acknowledge or ignore these alarms when they are processed by the nas. 

 

Additional Information

Interface_traffic  - This probe is no longer supported as of October 1, 2017. This probe is replaced by the snmpcollector probe.

https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/interface-traffic-interface-traffic-monitoring-no-longer-supported.html

Snmpcollector documentation:
https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/it-operations-management/ca-unified-infrastructure-management-probes/GA/alphabetical-probe-articles/snmpcollector-snmp-data-monitoring.html