rtpSessionNewIndex
RTP-MIB ·
.1.3.6.1.2.1.87.1.1
Object
This object is used to assign values to rtpSessionIndex as described in 'Textual Conventions for SMIv2'. For an RTP system that supports the creation of rows, the network manager would read the object, and then write the value back in the Set that creates a new instance of rtpSessionEntry. If the Set fails with the code 'inconsistentValue,' then the process must be repeated; If the Set succeeds, then the object is incremented, and the new instance is created according to the manager's directions. However, if the RTP agent is not acting as a monitor, only the RTP agent may create conceptual rows in the RTP session table.
Context
- MIB
- RTP-MIB
- OID
.1.3.6.1.2.1.87.1.1- Type
- scalar
- Access
- readwrite
- Status
- current
- Parent
- rtpMIBObjects
- Groups
- 1
Net-SNMP examples
How SNMP and these commands workScalars have one instance, identified by the .0 suffix.
Read the scalar instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'RTP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'RTP-MIB::rtpSessionNewIndex.0'
More examples
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'RTP-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'RTP-MIB::rtpSessionNewIndex'
Syntax
- Source
- SNMPv2-TCTestAndIncr
- Base type
Integer32
Type Description
Represents integer-valued information used for atomic
operations. When the management protocol is used to specify
that an object instance having this syntax is to be
modified, the new value supplied via the management protocol
must precisely match the value presently held by the
instance. If not, the management protocol set operation
fails with an error of `inconsistentValue'. Otherwise, if
the current value is the maximum value of 2^31-1 (2147483647
decimal), then the value held by the instance is wrapped to
zero; otherwise, the value held by the instance is
incremented by one. (Note that regardless of whether the
management protocol set operation succeeds, the variable-
binding in the request and response PDUs are identical.)
The value of the ACCESS clause for objects having this
syntax is either `read-write' or `read-create'. When an
instance of a columnar object having this syntax is created,
any value may be supplied via the management protocol.
When the network management portion of the system is re-
initialized, the value of every object instance having this
syntax must either be incremented from its value prior to
the re-initialization, or (if the value prior to the re-
initialization is unknown) be set to a pseudo-randomly
generated value.
Values & Constraints
Type Constraints
range: 0..2147483647
Conformance
Member of
Compliance refinements
rtpHostCompliance
noaccess
RTP system implementations support of
row creation and deletion is OPTIONAL so
implementation of this object is OPTIONAL.
row creation and deletion is OPTIONAL so
implementation of this object is OPTIONAL.