CISCO-PIM-MIB

        This MIB module defines the cisco specific variables
for Protocol Independent Multicast (PIM) management. 
These definitions are an extension of those defined in
the IETF PIM MIB (RFC 2934).
    
Source file
CISCO-PIM-MIB
Last revised
Identity
ciscoPimMIB
Base OID
1.3.6.1.4.1.9.9.184
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
PIM-MIB pimInterfaceStatus pimRPSetHoldTime
SNMPv2-CONF MODULE-COMPLIANCE (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page)
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-PIM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-PIM-MIB::ciscoPimMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-PIM-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-PIM-MIB::ciscoPimMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (19)
.1.3.6.1.4.1.9.9.184
.1.3.6.1.4.1.9.9.184.1
.1.3.6.1.4.1.9.9.184.1.1
.1.3.6.1.4.1.9.9.184.1.1.1
.1.3.6.1.4.1.9.9.184.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.184.1.1.3
.1.3.6.1.4.1.9.9.184.1.1.4
.1.3.6.1.4.1.9.9.184.1.1.5
.1.3.6.1.4.1.9.9.184.1.1.6
.1.3.6.1.4.1.9.9.184.1.1.7
.1.3.6.1.4.1.9.9.184.1.1.8
.1.3.6.1.4.1.9.9.184.1.1.9
.1.3.6.1.4.1.9.9.184.2
.1.3.6.1.4.1.9.9.184.2.0
.1.3.6.1.4.1.9.9.184.2.1
Enumeration
.1.3.6.1.4.1.9.9.184.2.1.1
.1.3.6.1.4.1.9.9.184.3
.1.3.6.1.4.1.9.9.184.3.1
.1.3.6.1.4.1.9.9.184.3.2
Dependencies (12) 5 direct · 7 transitive Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Conformance Groups (2)
A collection of objects to support management of PIM
Sparse mode on Cisco devices.
.1.3.6.1.4.1.9.9.184.3.2.1
A collection of objects that are supported only for
notification purpose.
.1.3.6.1.4.1.9.9.184.3.2.2
Compliance Statements (1)

OID .1.3.6.1.4.1.9.9.184.3.1.1
The compliance statement for devices running PIM Sparse
Mode and implementing the CISCO PIM MIB.
Required groups
Notifications / Traps (5)
NameOIDDescription
.1.3.6.1.4.1.9.9.184.2.0.1
A ciscoPimInterfaceUp notification signifies the
restoration of a PIM interface. This notification
should be generated whenever pimInterfaceStatus
transitions into the 'active' state.
pimInterfaceStatus identifies the interface which
was involved in the generation of this notification.
.1.3.6.1.4.1.9.9.184.2.0.2
A ciscoPimInterfaceDown notification signifies the loss
of a PIM interface. This notification should be generated
whenever an entry is about to be deleted from the
PimInterfaceTable.
pimInterfaceStatus identifies the interface which
was involved in the generation of this notification.
.1.3.6.1.4.1.9.9.184.2.0.3
A ciscoPimRPMappingChange notification signifies a change
in the RP Mapping on the device in question. A change in RP
Mapping could be because of addition of new entries to the
RP Mapping cache, deletion of existing entries, or a
modification to an existing mapping. The type of change is
indicated by cpimRPMappingChangeType. pimRPSetHoldTime
is used to identify the row in the pimRPSetTable that is
responsible for the generation of this notification.

In case of modification to existing entries, a
notification should be generated once before the
modification (with cpimRPMappingChangeType set to
modifiedOldMapping) and once after modification (with
cpimRPMappingChangeType set to modifiedNewMapping).

NOTE: A high frequency of RP Mapping change could result
in a large number of ciscoPimRPMappingChange notifications
being generated. Hence, in environments where the
possibility of a high frequency of RP Mapping change
exists, enable this notification with utmost care.
.1.3.6.1.4.1.9.9.184.2.0.4
A ciscoPimInvalidRegister notification signifies that
an invalid Register message was received by this device.

This notification is generated whenever the
cpimInvalidRegisterMsgsRcvd counter is incremented.
cpimLastErrorOrigin, cpimLastErrorGroup, and
cpimLastErrorRP should signify the source address, group
address and the RP address in the invalid register
packet.
.1.3.6.1.4.1.9.9.184.2.0.5
A ciscoPimInvalidJoinPrune notification signifies the
receipt of an invalid join/prune message.

This notification is generated whenever the
cpimInvalidJoinPruneMsgsRcvd counter is incremented.
cpimLastErrorOrigin, cpimLastErrorGroup, and
cpimLastErrorRP should signify the source address, group
address and the RP address in the invalid join/prune
packet.