myPimComponentIndex

MY-PIM-MIB · .1.3.6.1.4.1.4881.1.1.10.2.27.1.1.7.1.1
Commands MIB view Table view

Object

column Integer32 
A number uniquely identifying the component.  Each protocol
instance connected to a separate domain should have a
different index value.  Routers that only support membership
in a single PIM-SM domain should use a pimComponentIndex
value of 1.

Context

MIB
MY-PIM-MIB
OID
.1.3.6.1.4.1.4881.1.1.10.2.27.1.1.7.1.1
Type
column
Access
noaccess
Status
current
Parent
myPimComponentEntry

Net-SNMP examples

How SNMP and these commands work

Walk the column to discover its indexed instances, or supply every index to read one instance.

Walk the column
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'MY-PIM-MIB' -M '/opt/observium/mibs/ruijie:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MY-PIM-MIB::myPimComponentIndex'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'MY-PIM-MIB' -M '/opt/observium/mibs/ruijie:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'MY-PIM-MIB::myPimComponentIndex.<myPimComponentIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'MY-PIM-MIB' -M '/opt/observium/mibs/ruijie:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'MY-PIM-MIB::myPimComponentIndex'

Syntax

Integer32

Values & Constraints

Object Constraints
range: 1-255