pimTmEntScheduleLimit
DC-PIM-MIB ·
.1.2.826.42.1.1578918.5.71.1.1.1.18.1.43
Object
The maximum number of objects that can be processed in a
single schedule.
When subcomponents are scheduled by receipt of an IPS or a
timer pop, that IPS can cause more work than can be
performed in a reasonable time without blocking the
N-BASE. Subcomponents handle this by breaking off
processing when they hit a processing limit.
Higher values increase the processing efficiency of DC-PIM
instances, but can cause the scheduler to be blocked for
excessive periods, causing timers to pop late. Lower
values have the reverse effects.
Context
- MIB
- DC-PIM-MIB
- OID
.1.2.826.42.1.1578918.5.71.1.1.1.18.1.43- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- pimTmEntEntry
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workWalk 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 'DC-PIM-MIB' -M '/opt/observium/mibs/versa:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DC-PIM-MIB::pimTmEntScheduleLimit'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'DC-PIM-MIB' -M '/opt/observium/mibs/versa:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DC-PIM-MIB::pimTmEntScheduleLimit.<pimTmEntIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'DC-PIM-MIB' -M '/opt/observium/mibs/versa:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DC-PIM-MIB::pimTmEntScheduleLimit'
Syntax
- Source
- SNMPv2-SMIUnsigned32
- Base type
Unsigned32
Values & Constraints
Type Constraints
range: 0..4294967295
Conformance
Member of