---
oid: "1.3.6.1.4.1.2699.1.3.1.5.1.1.6"
asn1-notation: "{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2699 mibs(1) imagingCounterMIB(3) icMIBObjects(1) icTime(5) icTimeTable(1) icTimeEntry(1) icTimeProcessingSeconds(6)}"
description: "icTimeProcessingSeconds OBJECT-TYPE"
classification: "MIB object for network management"
last-modified: "2018-01-04"
---

## OID : `1.3.6.1.4.1.2699.1.3.1.5.1.1.6`

```asn1
{iso(1) identified-organization(3) dod(6) internet(1) private(4) enterprise(1) 2699 mibs(1) imagingCounterMIB(3) icMIBObjects(1) icTime(5) icTimeTable(1) icTimeEntry(1) icTimeProcessingSeconds(6)}
```

### Description

```asn1
icTimeProcessingSeconds OBJECT-TYPE
SYNTAX IcCounter32
UNITS "seconds"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Time in seconds that this managed service or managed subunit
has spent processing jobs in user mode since it was installed.
Usage: Processing may be mapped from hrDeviceStatus of 'running'
or 'warning' and either hrPrinterStatus of 'printing' or
hrSWRunStatus of 'running' (vs 'runnable' or 'notRunnable')
and snapshots of hrSystemUptime in Host Resources MIB (RFC2790)
or sysUpTime in MIB-II (RFC 1213), but these 32-bit tick
(1/100th second) counters can roll over in 15 months, so an
agent MUST account for roll over.
If implemented, hrSystemUptime (main system running time) SHOULD
be used instead of sysUpTime (SNMP Agent running time), to avoid
undetected roll over or restart discontinuities.
Note: Time in seconds is also available in printer-up-time in
IPP/1.1 Model (RFC 2911)."
REFERENCE
"hrDeviceStatus of 'running' or 'warning' and
hrPrinterStatus or hrSWRunStatus in Host Resources MIB
(RFC 1514/2790);
sysUpTime in MIB-II (RFC 1213);
printer-up-time in IPP/1.1 Model (RFC 2911)."
DEFVAL { 0 } -- no processing time
```

**Classification**: MIB object for network management

### Child OIDs

No child OID

### Terms of Use
[Terms of use](https://oid-base.com/disclaimer.htm.md)
