XEROX-COMMS-ENGINE-MIB

MIB Reference — IPNetwork Monitor · Updated September 09, 2026

All MIBsXEROX-COMMS-ENGINE-MIB

Organization: Xerox Corporation - XCMI Working Group

Last Updated: 2002-09-17

Category: Xerox Printer Management

Description: Monitors Xerox XCMI communications engine operation, job routing, and protocol processing status.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is XEROX-COMMS-ENGINE-MIB?

The XEROX-COMMS-ENGINE-MIB (version 5.11) is Xerox's companion XCMI MIB for detailed protocol stack graphing and active runtime management of the 'communications engine' driving protocol stacks on Xerox network-attached devices, giving a more granular live view than the config MIB. It exposes engine-level tables tracking the actual running composition, addressing, and management layering of each communications engine instance. Its monitoring emphasis is on software/protocol runtime status: revealing the current layered composition of a running protocol engine to confirm it is actively serving the expected stack, and detecting stalled or misconfigured engines. It relies on RFC 2790's Host Resources MIB (hrDeviceProcessor) for host CPU indexing, matching the config MIB, and the two modules are closely complementary. It was deployed on Xerox network-attached printers and hosts where administrators need live visibility into active protocol engine state beyond static configuration. Engineers can download the XEROX-COMMS-ENGINE-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in XEROX-COMMS-ENGINE-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Xerox network printer/host with XCMI support

Monitoring Examples

xcmCommsEngineTable/xcmCommsEngineEntry objects such as xcmCommsEngineName, xcmCommsEngineStackLast, and xcmCommsEngineMuxLast let an admin see the actual running composition of a protocol stack engine on a Xerox device, versus its configured intent in the companion config MIB. An engine whose xcmCommsEngineRowStatus is inconsistent with the expected active state, or whose xcmCommsEngineAddressLast doesn't match the expected network address, would flag a protocol engine that failed to start correctly.

What Can Be Monitored

  • active protocol stack engine composition
  • engine row status
  • last-known stack/mux/address/management layer
  • engine create/update support flags
Imported Objects

From HOST-RESOURCES-MIB

ProductID
hrDeviceIndexOBJECT-TYPE

From SNMPv2-CONF

MODULE-COMPLIANCE
OBJECT-GROUP

From SNMPv2-SMI

Counter32
Gauge32
Integer32
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DateAndTime
RowStatus
TruthValue

From XEROX-COMMON-MIB

xeroxCommonMIBOBJECT-IDENTITY

From XEROX-COMMS-ENGINE-TC

XcmCommsAddressExtFanout
XcmCommsAddressExtForm
XcmCommsAddressExtScope
XcmCommsEngineGroupSupport
XcmCommsMgmtCommandData
XcmCommsMgmtCommandRequest
XcmCommsMgmtConditions
XcmCommsMgmtState
XcmCommsStackExtLayer
XcmCommsStackExtProtocol
XcmCommsStackExtPurpose
XcmCommsStackExtRole
XcmCommsStackExtSuite
XcmCommsStackExtSuiteVersion
XcmCommsStackPosition

From XEROX-GENERAL-TC

Cardinal32
Ordinal32
XcmFixedLocaleDisplayString
XcmGenSNMPv2ErrorStatus
zeroDotZeroOBJECT-IDENTITY

From XEROX-HOST-RESOURCES-EXT-TC

XcmHrDevTrafficUnit

How to Use in IPNetwork Monitor

Example using xcmCommsTrafficInputCount OID:

Select a Xerox network printer/host with XCMI support (live comms-engine protocol-stack runtime status) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type xcmCommsTrafficInputCount into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. It reports a layer input traffic count, used by system administrators and end users of this layer. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs

RFC description

Xerox vendor-specific MIB for managing communications protocol stacks and network-accessible devices; used for Xerox printer and device management.

Start monitoring Xerox network printer/host with XCMI support (live comms-engine protocol-stack runtime status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download XEROX-COMMS-ENGINE-MIB