An extended device status, used by system administrators
and end users of this device (here, read 'state' for 'status').
Usage: Conforming implementations shall NOT 'bubble up' status
from 'physical' devices to associated 'logical' devices. All
devices shall ALWAYS report their own status ONLY.
Usage: Exactly one enumeration of extended device status
shall be defined, with ranges for each basic device type (eg,
'hrDevicePrinter'). The legal range for extended device status
for a given device type (either defined by RFC 1514 or by this
MIB) is found by multiplying the final arc of the the device
type OID by 100 - the result is the device specific range base -
the end of the device specific range is 99 larger. These device
specific extended device status values shall be reissued
periodically in the 'XcmHrDevInfoXStatus' textual convention.
Parsed from file XEROX-HOST-RESOURCES-EXT-MIB.mib.txt
Company: None
Module: XEROX-HOST-RESOURCES-EXT-MIB
An extended device status, used by system administrators
and end users of this device (here, read 'state' for 'status').
Usage: Conforming implementations shall NOT 'bubble up' status
from 'physical' devices to associated 'logical' devices. All
devices shall ALWAYS report their own status ONLY.
Usage: Exactly one enumeration of extended device status
shall be defined, with ranges for each basic device type (eg,
'hrDevicePrinter'). The legal range for extended device status
for a given device type (either defined by RFC 1514 or by this
MIB) is found by multiplying the final arc of the the device
type OID by 100 - the result is the device specific range base -
the end of the device specific range is 99 larger. These device
specific extended device status values shall be reissued
periodically in the 'XcmHrDevInfoXStatus' textual convention.
Parsed from file XEROX-HOST-RESOURCES-EXT-MIB.mib
Module: XEROX-HOST-RESOURCES-EXT-MIB
Vendor: Xerox
Module: XEROX-HOST-RESOURCES-EXT-MIB
[Automatically extracted from oidview.com]
xcmHrDevInfoXStatus OBJECT-TYPE SYNTAX XcmHrDevInfoXStatus MAX-ACCESS read-only STATUS current DESCRIPTION "An extended device status, used by system administrators and end users of this device (here, read 'state' for 'status'). Usage: Conforming implementations shall NOT 'bubble up' status from 'physical' devices to associated 'logical' devices. All devices shall ALWAYS report their own status ONLY. Usage: Exactly one enumeration of extended device status shall be defined, with ranges for each basic device type (eg, 'hrDevicePrinter'). The legal range for extended device status for a given device type (either defined by RFC 1514 or by this MIB) is found by multiplying the final arc of the the device type OID by 100 - the result is the device specific range base - the end of the device specific range is 99 larger. These device specific extended device status values shall be reissued periodically in the 'XcmHrDevInfoXStatus' textual convention." REFERENCE "See: Section 9.4.9 'Printer-state' (page 185) of DPA (Document Printing Application) ISO/IEC 10175 (Final Text, March 1996) for a discussion of the printer states used here. Note that the DPA state 'connecting-to-printer' has no meaning in the context of a 'physical' printer device, but only in the context of an intermediate DP-Server presenting a 'logical' printer device. See: 'hrPrinterStatus' and 'hrPrinterDetectedErrorState' in IETF Host Resources MIB (RFC 1514). See: 'hrDeviceStatus' in the Device group of the IETF Host Resources MIB (RFC 1514). See: 'xcmHrDevInfoConditions' and 'xcmHrDevInfoXConditions' in the Host Resources Extensions MIB." DEFVAL { commonNone } ::= { xcmHrDevInfoEntry 5 }
xcmHrDevInfoXStatus OBJECT-TYPE SYNTAX XcmHrDevInfoXStatus MAX-ACCESS read-only STATUS current DESCRIPTION "An extended device status, used by system administrators and end users of this device (here, read 'state' for 'status'). Usage: Conforming implementations shall NOT 'bubble up' status from 'physical' devices to associated 'logical' devices. All devices shall ALWAYS report their own status ONLY. Usage: Exactly one enumeration of extended device status shall be defined, with ranges for each basic device type (eg, 'hrDevicePrinter'). The legal range for extended device status for a given device type (either defined by RFC 1514 or by this MIB) is found by multiplying the final arc of the the device type OID by 100 - the result is the device specific range base - the end of the device specific range is 99 larger. These device specific extended device status values shall be reissued periodically in the 'XcmHrDevInfoXStatus' textual convention." REFERENCE "See: Section 9.4.9 'Printer-state' (page 185) of DPA (Document Printing Application) ISO/IEC 10175 (Final Text, March 1996) for a discussion of the printer states used here. Note that the DPA state 'connecting-to-printer' has no meaning in the context of a 'physical' printer device, but only in the context of an intermediate DP-Server presenting a 'logical' printer device. See: 'hrPrinterStatus' and 'hrPrinterDetectedErrorState' in IETF Host Resources MIB (RFC 1514). See: 'hrDeviceStatus' in the Device group of the IETF Host Resources MIB (RFC 1514). See: 'xcmHrDevInfoConditions' and 'xcmHrDevInfoXConditions' in the Host Resources Extensions MIB." DEFVAL { commonNone } ::= { xcmHrDevInfoEntry 5 }
| OID | Name | Sub children | Sub Nodes Total | Description |
|---|---|---|---|---|
| 1.3.6.1.4.1.253.8.53.3.2.1.1 | xcmHrDevInfoRowStatus | 0 | 0 | This object manages the SMIv2 row status of this conceptual row in the 'xcmHrDevInfoTable' and ALSO manages the row status of the… |
| 1.3.6.1.4.1.253.8.53.3.2.1.2 | xcmHrDevInfoName | 0 | 0 | Human-readable device name, used by system administrators and end users to identify this device for systems management. Usage: T… |
| 1.3.6.1.4.1.253.8.53.3.2.1.3 | xcmHrDevInfoSerialNumber | 0 | 0 | Human-readable serial number, used by system administrators and end users to identify this device for systems management. |
| 1.3.6.1.4.1.253.8.53.3.2.1.4 | xcmHrDevInfoRealization | 0 | 0 | An extended device type (or device 'realization'), used by system administrators and end users of this device. |
| 1.3.6.1.4.1.253.8.53.3.2.1.6 | xcmHrDevInfoConditions | 0 | 0 | A relatively generic description of the current 'conditions' of this device. Usage: It is desirable that the implementor report … |
| 1.3.6.1.4.1.253.8.53.3.2.1.7 | xcmHrDevInfoXConditions | 0 | 0 | A device specific description of the extended 'conditions' of this device. Usage: For FUTURE expansion. Usage: Exactly one bit m… |
| 1.3.6.1.4.1.253.8.53.3.2.1.8 | xcmHrDevInfoInstallDate | 0 | 0 | The date of the most recent install or upgrade of the device represented by this conceptual row in the 'hrDeviceTable'. |
| 1.3.6.1.4.1.253.8.53.3.2.1.9 | xcmHrDevInfoResetDate | 0 | 0 | The date of the most recent auto or managed reset of the device represented by this conceptual row in the 'hrDeviceTable'. |
| 1.3.6.1.4.1.253.8.53.3.2.1.10 | xcmHrDevInfoNextDeviceIndex | 0 | 0 | The value of 'hrDeviceIndex' corresponding to: a) the next associated row in the 'hrDeviceTable'; or b) zero if this is the last … |
| 1.3.6.1.4.1.253.8.53.3.2.1.11 | xcmHrDevInfoPreviousDeviceIndex | 0 | 0 | The value of 'hrDeviceIndex' corresponding to: a) the previous associated row in the 'hrDeviceTable'; or b) zero if this is the f… |
| 1.3.6.1.4.1.253.8.53.3.2.1.12 | xcmHrDevInfoPhysicalDeviceIndex | 0 | 0 | The value of 'hrDeviceIndex' corresponding to the directly associated conceptual row in the 'hrDeviceTable' representing: a) the … |