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).
|
ciscoPimMIB1.3.6.1.4.1.9.9.184 |
| ciscoMgmt | CISCO-SMI |
| InetAddressType, InetAddress | INET-ADDRESS-MIB |
| pimInterfaceStatus, pimRPSetHoldTime | PIM-MIB |
| MODULE-COMPLIANCE, OBJECT-GROUP | SNMPv2-CONF |
| MODULE-IDENTITY, OBJECT-TYPE, Counter32, NOTIFICATION-TYPE | SNMPv2-SMI |
![]() | .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 | |
![]() | .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 | |
![]() | .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 |
| Name | OID | Description |
|---|---|---|
| .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. |