Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

OpenNMS not using HighSpeed counters when collecting interface data on Cisco ASA Security Contexts

Description

When importing an ASA Security Contexts node into OpenNMS and SNMP is enabled OpenNMS do not use the ifHCSpeed counters. It uses the regular ifSpeed counters instead, even though ifHC counters are available, which breaks correct bits in/out graphing of these devices. SNMP v2c is configured to be used by OpenNMS.

Is this a bug or is there some way I could force OpenNMS to use highspeed counters?

A snmpwalk on the ASA Security Context is attached asa text-file.

perhaps I've added the wrong component? Should 'Component/s' be changed to collectd?

Acceptance / Success Criteria

None

Attachments

1
  • 04 Nov 2015, 08:00 AM

Lucidchart Diagrams

Activity

Show:

Kalle Carlbark November 4, 2015 at 10:42 AM

Hi Jeff,

This is a Cisco ASA Security Context (Virtual FW) on a physical ASA 5585-X SSP10.

It has .1.3.6.1.4.1.9.1.1198 as sysObjectID.

I added .1.3.6.1.4.1.9.1.1198 as a systemDef in cisco.xml and included mib2-X-interfaces I edited cisco.xml via the webapp, deleted and re-provisioned the node but it still collects non-highspeed counters. At least I don't see any ifHCInOctets.jrb under rrd/snmp/<nodeid>/<interface>/ directory. But I do see ifInOctets.jrb.

Thanks

Jeff Gehlbach November 4, 2015 at 9:56 AM

what's the sysObjectID of the ASAs you're using? We can support these models out of the box in future releases by adding, for each one, a systemDef that includes the mib2-X-interfaces group.

We try to collect high-speed counters by default from all the kinds of devices that are known to have good support for them.

Details

Assignee

Reporter

Labels

Components

Affects versions

Priority

PagerDuty

Created November 4, 2015 at 8:00 AM
Updated September 21, 2021 at 6:24 PM

Flag notifications