diffServActionInterface
DIFFSERV-MIB ·
.1.3.6.1.2.1.97.1.5.2.1.2
Object
The interface index (value of ifIndex) that this action occurs
on. This may be derived from the diffServDataPathStartEntry's
index by extension through the various RowPointers. However, as
this may be difficult for a network management station, it is
placed here as well. If this is indeterminate, the value is
zero.
This is of especial relevance when reporting the counters which
may apply to traffic crossing an interface:
diffServCountActOctets,
diffServCountActPkts,
diffServAlgDropOctets,
diffServAlgDropPkts,
diffServAlgRandomDropOctets, and
diffServAlgRandomDropPkts.
It is also especially relevant to the queue and scheduler which
may be subsequently applied.
Context
- MIB
- DIFFSERV-MIB
- OID
.1.3.6.1.2.1.97.1.5.2.1.2- Type
- column
- Access
- readwrite
- Status
- current
- Parent
- diffServActionEntry
- 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 'DIFFSERV-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DIFFSERV-MIB::diffServActionInterface'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'DIFFSERV-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'DIFFSERV-MIB::diffServActionInterface.<diffServActionId>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'DIFFSERV-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'DIFFSERV-MIB::diffServActionInterface'
Syntax
- Source
- IF-MIBInterfaceIndexOrZero
- Base type
Integer32- Display format
d
Type Description
This textual convention is an extension of the InterfaceIndex convention. The latter defines a greater than zero value used to identify an interface or interface sub-layer in the managed system. This extension permits the additional value of zero. the value zero is object-specific and must therefore be defined as part of the description of any object which uses this syntax. Examples of the usage of zero might include situations where interface was unknown, or when none or all interfaces need to be referenced.
Values & Constraints
Type Constraints
range: 0..2147483647
Conformance
Member of
Compliance refinements
diffServMIBReadOnlyCompliance
readonly
Write access is not required.