sipServerRegStatsDisconTime
SIP-SERVER-MIB ·
.1.3.6.1.2.1.151.1.6.1.1.3
Context
- MIB
- SIP-SERVER-MIB
- OID
.1.3.6.1.2.1.151.1.6.1.1.3- Type
- column
- Access
- readonly
- Status
- current
- Parent
- sipServerRegStatsEntry
- 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 'SIP-SERVER-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SIP-SERVER-MIB::sipServerRegStatsDisconTime'
More examples
Read one indexed instance
/usr/bin/snmpget -v2c -c '<community>' -Pud -Ir -OQUv -m 'SIP-SERVER-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'SIP-SERVER-MIB::sipServerRegStatsDisconTime.<applIndex>'
Translate to a numeric OID
/usr/bin/snmptranslate -Pud -Ir -On -m 'SIP-SERVER-MIB' -M '/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'SIP-SERVER-MIB::sipServerRegStatsDisconTime'
Syntax
- Source
- SNMPv2-TCTimeStamp
- Base type
Unsigned32- Based on
- SNMPv2-SMITimeTicks
Type Description
The value of the sysUpTime object at which a specific
occurrence happened. The specific occurrence must be
defined in the description of any object defined using this
type.
If sysUpTime is reset to zero as a result of a re-
initialization of the network management (sub)system, then
the values of all TimeStamp objects are also reset.
However, after approximately 497 days without a re-
initialization, the sysUpTime object will reach 2^^32-1 and
then increment around to zero; in this case, existing values
of TimeStamp objects do not change. This can lead to
ambiguities in the value of TimeStamp objects.
Values & Constraints
No enumerated values or constraints recorded.
Conformance
Member of