The SNMP Collection agents package consists of an SNMP Collection profile, an SNMP OID profile, and two SNMP real-time agents.
- The SNMP Collection profile is used to define the set of MIB files for the network element(s) you want to use. Usually, the set of MIB files is provided by equipment vendor.
- The SNMP Request agent is used for polling management data from network elements and converting it to UDRs. A network element is often a router or a switch, but it can be anything that is SNMP-enabled.
- The SNMP OID profile is used for configuring UDR types and fields to poll, as an alternative to configuring this in the SNMP Request agent itself, making the configuration available for multiple agents.
- The SNMP Trap agent is used to receive SNMP notifications, that is, traps and informs, and convert them to UDRs.
Features Overview
- SNMPv1, v2c, and v3 are supported.
- The SNMP Request agent maps all SNMP ASN.1 types to corresponding UDR attribute types including:
- INTEGER (including integer enumerations defined in MIB files)
- COUNTER
- COUNTER64
- GAUGE
- OCTET STRING (including BIT STRING)
- OPAQUE
- IPADDRESS
- OBJECT IDENTIFIER
- TIMETICKS
- IPv4 and IPv6 protocols are supported.
- The SNMP Trap agent supports all types of SNMP notifications: Traps (TRAPv1 and TRAPv2 PDU types) and informs.
- The SNMP Trap agent also supports enterprise specific traps and generic traps:
- Cold Start
- Warm Start
- Link Up/Down
- Authentication Failure
- EGP Neighborless
Network Elements
The SNMP Request agent uses a CSV file as the input source. This file holds the list of network elements to poll.
Extended MIB support
If the target MIBs have any dependent MIBs, ensure that all the dependent MIBs are also loaded to avoid errors.