XEROX-COMMS-ENGINE-MIB: View SNMP OID List / Download MIB

Version: 5.11.pub The MIB module for detailed protocol stack graphing, and active management of communications protocol stacks, communications end system applications, communications intermediate systems, and communications gateways for network accessible host systems. Usage: Note that throughout this MIB module, the INDEX clauses referring to 'hrDeviceIndex' for the 'hrDeviceTable' (Devices Group) of the Host Resources MIB (RFC 2790) SHALL specify host system CPUs (ie, 'hrDeviceProcessor') and SHALL NOT specify ANY other 'hrDeviceType'. Usage: The object 'xcmCommsStackXrefHrCommDevIndex' in the Comms Stack Xref Group of this MIB MAY be used to specify (for 'bottom' protocol stack layers) the corresponding value of 'hrDeviceIndex' for network, modem, serial port, and parallel port devices. And the object 'xcmCommsStackXrefIfIndex' MAY be used to specify the value of 'ifIndex' for the corresponding entry in the MIB-II 'ifTable' (ie, 'network interfaces'). Copyright (C) 1995-2002 Xerox Corporation. All Rights Reserved.

Comms Engine Group (Comms Engines).

Comms Engine Ext Group (Comms Engines).

Comms Stack Group (Stack Layers).

Comms Stack Ext Group (Stack Layers).

Comms Stack Xref Group (Stack Layers).

Comms Mux Group (Multiplexors).

Comms Mux Ext Group (Multiplexors).

Comms Address Group (Directories).

Comms Address Ext Group (Directories).

Comms Traffic Group (Stack Layer Traffic Counters).

Comms Access Group (Stack Layer Access Counters).

Comms Mgmt Group (State Management).

The compliance statements for SNMP management agents that implement the Comms Engine MIB.

The compliance statements for SNMP management agents that implement a subset of the Comms Engine MIB, for the sole purpose of supporting extended 'contact' information per device, via the Device Help group of the XCMI Ext to Host Resources MIB. Usage: See 'Usage' paragraphs in the DESCRIPTION sub-clauses of the following OBJECT clauses for additional usage details.

A table of the communications engines installed and (possibly) running on platforms (ie, CPUs) on this host system.

An entry for a communications engine installed and (possibly) running on a platform (ie, CPU) on this host system. Usage: Note that values of 'hrDeviceIndex' used to reference entries in the 'xcmCommsEngineTable' SHALL reference entries in the 'hrDeviceTable' with 'hrDeviceType' equal to 'hrDeviceProcessor' (representing host system CPUs and therefore also having corresponding entries in the 'hrProcessorTable').

This object is used to create and delete individual conceptual rows in the 'xcmCommsEngineTable'.

Human-readable name, used by system administrators and end users to identify this communications engine for systems management. Usage: This name SHOULD be the one normally used in a command shell for control of this communications engine.

The last entry index (regardless of its current state) in the 'xcmCommsStackTable' of this communications engine, on this host system. Usage: The last entry index explicitly bounds the valid range of 'xcmCommsStackIndex'.

The last entry index (regardless of its current state) in the 'xcmCommsMuxTable' of this communications engine, on this host system. Usage: The last entry index explicitly bounds the valid range of 'xcmCommsMuxIndex'.

The last entry index (regardless of its current state) in the 'xcmCommsAddressTable' of this communications engine, on this host system. Usage: The last entry index explicitly bounds the valid range of 'xcmCommsAddressIndex'.

The last entry index (regardless of its current state) in the 'xcmCommsMgmtTable' of this communications engine, on this host system. Usage: The last entry index explicitly bounds the valid range of 'xcmCommsMgmtIndex'.

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional XCMI Comms Engine MIB object groups supported by this management agent implementation (ie, version) on this host system, specified in a bit-mask. Usage: Conforming management agents SHALL accurately report their support for XCMI Comms Engine MIB object groups.

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional XCMI Comms Engine MIB object groups supported for dynamic row creation (via '...RowStatus') by this management agent implementation (ie, version) on this host system, specified in a bit-mask. Usage: Conforming management agents SHALL accurately report their support for XCMI Comms Engine MIB object groups.

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional XCMI Comms Engine MIB object groups supported for existing row update (via SNMP Set-Request PDUs) by this management agent implementation (ie, version) on this host system, specified in a bit-mask. Usage: Conforming management agents SHALL accurately report their support for XCMI Comms Engine MIB object groups.

A 'sparse' table which augments 'xcmCommsEngineTable' with additional useful information.

A 'sparse' entry which augments 'xcmCommsEngineEntry' with additional useful information.

This object is used to create and delete individual conceptual rows in the 'xcmCommsEngineExtTable'.

A relatively generic description of the current state of this communications entity.

A relatively generic description of the current conditions of this communications entity.

The software product ID of the SNMP sub-agent which implements the XCMI Comms Engine MIB on this host system. Usage: This object SHALL specify the software product ID of an SNMP sub-agent (possibly also found in a conceptual row in the 'hrSWRunTable' and/or 'hrSWInstalledTable' in the IETF HR MIB). This object SHALL NOT specify a particular release of the XCMI Comms Engine MIB, or the whole host system product. Note: Contrast with 'sysObjectID' for the whole SNMP agent in the IETF MIB-II (RFC 1213) and 'hrDeviceID' for the whole device (or whole product, in the case of 'xcmHrDevice...') in the IETF Host Resources MIB (RFC 2790).

The software build date of the SNMP sub-agent which implements the XCMI Comms Engine MIB on this host system. Usage: This object SHALL specify the BUILD date of the SNMP sub-agent software (not available elsewhere in IETF/XCMI MIBs). This object SHALL NOT specify the INSTALL date of the SNMP sub-agent software on this host system, nor the RESET date. Note: Contrast with 'hrSWInstalledDate' in the Software Installed group of the IETF Host Resources MIB (RFC 2790), and 'xcmHrDevInfoResetDate' in the Device Info group of the XCMI Host Resources Extensions MIB.

The value of 'xcmCommsMgmtIndex' corresponding to a directly associated conceptual row in the 'xcmCommsMgmtTable', or zero if this 'managed entity' does NOT require such information.

The OID (object identifier) of the conceptual row or simple object which represents some 'owner entity' associated with this entry in the 'xcmCommsEngineExtTable'.

A table containing information on the relationships between the multiple stack layers or sublayers (ie, protocol entities) comprising the (possibly) running 'protocol stacks' on this host system. In particular, it contains information about which stack layer runs 'above' and 'below' which other stack layer.

An entry for a stack layer in a protocol stack installed and (possibly) running on this host system.

A unique value used by this host system to identify this conceptual row in the 'xcmCommsStackTable'.

This object is used to create and delete individual conceptual rows in the 'xcmCommsStackTable'.

An unambiguous stack layer type, used by system administrators and end users to identify the type of this stack layer. Usage: Since this unambiguous stack layer type is specified as an object identifier, it MAY be taken from any IETF, Xerox, third- party, or product-specific MIB, or it MAY simply be any IETF SMIv2-style 'autonomous type'. Usage: Suitable values for this unambiguous stack layer type are specified in the companion XCMI Comms Config TC (eg, 'xcmCONetwareIPX').

Human-readable name, used by system administrators and end users to identify this stack layer for systems management. Usage: This name SHOULD be the one normally used in a command shell for control of this stack layer.

A relatively generic description of the current position of this protocol entity (ie, this layer) in this protocol stack. Usage: A conceptual row in 'xcmCommsStackTable', which occupies a 'bottom' position in a protocol stack AND has a corresponding row in the 'xcmCommsStackXrefTable', SHOULD have valid references in 'xcmCommsStackXrefIfIndex' (to IETF MIB-II) and 'xcmCommsStackXrefHrCommDevIndex' (to IETF Host Resources MIB). Usage: A conceptual row in 'xcmCommsStackTable' which occupies a 'lowerMux' and/or an 'upperMux' position in a protocol stack SHALL have one (or two) valid corresponding conceptual rows in the 'xcmCommsMuxTable', as the conventionally used 'xcmCommsStack[Lower|Upper]StackIndex' objects take on zero values for multiplexors (thus breaking the graph of the stack layers, without the use of the 'xcmCommsMuxTable').

The value of 'xcmCommsStackIndex' corresponding to a next lower associated conceptual row in the 'xcmCommsStackTable', or zero if this stack layer's position is either 'bottom' or 'lowerMux'.

The value of 'xcmCommsStackIndex' corresponding to a next higher associated conceptual row in the 'xcmCommsStackTable', or zero if this stack layer's position is either 'upperMux' or sometimes 'top' (see usage note below). Usage: Only for protocol entities whose current purpose is either 'layerInterWorkingUnit' (ie, relays or gateways) or 'systemInterWorkingUnit' (ie, application gateways), it is permitted that the stack layer whose current position is 'top' have an upper layer index pointing to the peer entity (also in a 'top' position) which comprises the 'other half' of a relay or gateway between two different address domains (ie, an active protocol conversion relay) - that is the graphed protocol stack is an inverted 'U'.

The value of 'xcmCommsAddressIndex' corresponding to the first associated conceptual row in the 'xcmCommsAddressTable', or zero if this 'owner entity' does NOT require such information.

The value of 'xcmCommsOptionIndex' corresponding to the first associated conceptual row in the 'xcmCommsOptionTable', or zero if this stack layer does NOT require such information.

The value of 'xcmCommsMuxIndex' corresponding to the first associated conceptual row in the 'xcmCommsMuxTable', or zero if this stack layer's position is NOT 'lowerMux'.

The value of 'xcmCommsMuxIndex' corresponding to the first associated conceptual row in the 'xcmCommsMuxTable', or zero if this stack layer's position is NOT 'upperMux'.

A 'sparse' table which augments 'xcmCommsStackTable' with additional useful information.

A 'sparse' entry which augments 'xcmCommsStackEntry' with additional useful information.

This object is used to create and delete individual conceptual rows in the 'xcmCommsStackExtTable'.

A relatively generic description of the current state of this communications entity.

A relatively generic description of the current conditions of this communications entity.

A relatively generic description of the current purpose of this stack layer during normal operation.

A relatively generic description of the current role of this stack layer during normal operation.

The current protocol suite of this protocol entity (stack layer or sublayer).

The current protocol suite version of this protocol entity (stack layer or sublayer).

The closest approximate layer in the OSI Reference Model (CCITT X.200 | ISO 7498) to the current behavior of this stack layer or sublayer.

The specific protocol (within a given protocol suite) currently configured for this stack layer or sublayer.

The value of 'xcmCommsMgmtIndex' corresponding to the directly associated conceptual row in the 'xcmCommsMgmtTable', or zero if this 'managed entity' does NOT require such information.

The OID (object identifier) of the conceptual row or simple object which represents some 'owner entity' associated with this entry in the 'xcmCommsStackExtTable'. Usage: A Printer Channel, for example, might choose to specify the OID of some conceptual row in the 'prtChannelTable'.

A table containing optional cross reference information for the multiple stack layers or sublayers (ie, protocol entities) comprising the (possibly) running 'protocol stacks' on this host system.

An entry for a stack layer in a protocol stack installed and (possibly) running on this host system.

This object is used to create and delete individual conceptual rows in the 'xcmCommsStackXrefTable'.

The value of 'xcmCommsStackIndex' corresponding to the one-to-one associated conceptual row in the 'xcmCommsStackTable' which has 'xcmCommsStackExtPurpose' of 'layerManagement', or zero if this this stack layer has no associated layer management entity.

The value of 'xcmCommsStackIndex' corresponding to the one-to-one associated conceptual row in the 'xcmCommsStackTable' which has 'xcmCommsStackExtPurpose' of 'layerSecurity', or zero if this this stack layer has no associated layer security entity.

The value of 'xcmCommsStackIndex' corresponding to the one-to-one associated conceptual row in the 'xcmCommsStackTable' which has 'xcmCommsStackExtPurpose' of 'layerInterWorkingUnit', or zero if this this stack layer has no associated layer relay entity.

The value of 'hrSWRunIndex' corresponding to the directly associated conceptual row in the 'hrSWRunTable' of the Host Resources MIB (RFC 2790), or zero if 'hrSWRunTable' is NOT implemented.

The value of 'hrSWInstalledIndex' corresponding to the directly associated conceptual row in the 'hrSWInstalledTable' of the Host Resources MIB (RFC 2790), or zero if 'hrSWInstalledTable' is NOT implemented.

The value of 'ifIndex' corresponding to the directly associated conceptual row in the 'ifTable' (Interfaces Group) of the MIB-II (RFC 1213), or zero if the position of this stack layer is NOT 'bottom' (ie, this stack layer does NOT represent a physical 'network interface'). Usage: This is partially a convenience object, since given the value of 'hrDeviceIndex' for an 'hrDeviceNetwork' type device, the corresponding 'ifIndex' is found in the mandatory entry in the 'hrNetworkTable'. However, note that for 'hrDeviceModem', 'hrDeviceSerialPort', and 'hrDeviceParallelPort' devices, the 'xcmCommsStackXrefIfIndex' object is a NECESSITY for support of this communications engine MIB.

The value of 'hrDeviceIndex' corresponding to the directly associated conceptual rows in the 'hrDeviceTable' and (possibly) 'hrNetworkTable' of the Host Resources MIB (RFC 2790), or zero if the position of this stack layer is NOT 'bottom' (ie, this stack layer does NOT represent a physical 'network interface'). Usage: Note that for 'hrDeviceModem', 'hrDeviceSerialPort', and 'hrDeviceParallelPort' devices, there is NO corresponding entry in the 'hrNetworkTable', a subtle difference between MIB-II (RFC 1213) and the Host Resources MIB (RFC 2790).

A table containing information on the relationships between the multiple stack layers or sublayers (ie, protocol entities) participating in a 'upper' or 'lower' multiplexor (ie, the simultaneous adjacency of two or more 'upper' or 'lower' stack layers with a single instance of a 'base' stack layer), eg, IP (a 'base' stack layer) operating below both TCP and UDP (the 'adjacent' stack layers).

An entry for a 'base' stack layer participating in an 'upper' or 'lower' multiplexor.

A unique value used by this host system to identify this conceptual row in the 'xcmCommsMuxTable'.

This object is used to create and delete individual conceptual rows in the 'xcmCommsMuxTable'.

The value of 'xcmCommsMuxIndex' corresponding to a next associated conceptual row in the 'xcmCommsMuxTable', or zero if this is the last associated conceptual row in a given set.

The value of 'xcmCommsMuxIndex' corresponding to a previous associated conceptual row in the 'xcmCommsMuxTable', or zero if this is the first associated conceptual row in a given set.

The value of 'xcmCommsOptionIndex' corresponding to the first associated conceptual row in the 'xcmCommsOptionTable', or zero if this multiplexor entry does NOT require such information.

The value of 'xcmCommsStackIndex' corresponding to the base associated conceptual row in the 'xcmCommsStackTable'.

The value of 'xcmCommsStackIndex' corresponding to the adjacent associated conceptual row in the 'xcmCommsStackTable'.

A 'sparse' table which augments 'xcmCommsMuxTable' with additional useful information.

A 'sparse' entry which augments 'xcmCommsMuxEntry' with additional useful information.

This object is used to create and delete individual conceptual rows in the 'xcmCommsMuxExtTable'.

A relatively generic description of the current state of this communications entity.

A relatively generic description of the current conditions of this communications entity.

The value of 'xcmCommsMgmtIndex' corresponding to the directly associated conceptual row in the 'xcmCommsMgmtTable', or zero if this 'managed entity' does NOT require such information.

The value of 'xcmCommsAddressIndex' corresponding to the first associated conceptual row in the 'xcmCommsAddressTable', or zero if this 'owner entity' does NOT require such information.

The OID (object identifier) of the conceptual row or simple object which represents some 'owner entity' associated with this entry in the 'xcmCommsMuxExtTable'.

A table containing information on unicast, multicast, and broadcast addresses (remote/local) known to this host system.

An entry containing information on one unicast, multicast, or broadcast address (remote/local) known to this host system.

A unique value used by this host system to identify this conceptual row in the 'xcmCommsAddressTable'.

This object is used to create and delete individual conceptual rows in the 'xcmCommsAddressTable'.

An unambiguous address type, used by system administrators and end users to identify the type of this address. Usage: Since this unambiguous address type is specified as an object identifier, it MAY be taken from any IETF, Xerox, third- party, or product-specific MIB, or it MAY simply be any IETF SMIv2-style 'autonomous type'. Usage: Suitable values for this unambiguous address type are specified in the companion XCMI Comms Config TC (eg, 'xcmCONetwareIPX').

An unambiguous address user role, used by system administrators and end users to identify the user role of this address. Usage: This unambiguous address user role is specified by a value defined in the textual convention 'XcmSecUserRole' in the XCMI Security/AAA TC. Usage: This unambiguous address user role is weakly typed here to avoid cyclic compilation dependencies between XCMI MIBs. Usage: A chain of 'xcmCommsAddressEntry' objects MAY be pointed to by 'xcmDevHelpCommsAddressIndex' in the Device Help group of the XCMI Ext to IETF Host Resources MIB. In this case, the 'xcmCommsAddressTypeOID' object MAY contain values such as 'xcmCOOsiwanPSTNAddress' (analog phone number), 'xcmCOOsiwanFaxAddress' (fax phone number), etc, taken from the XCMI Comms Config TC. In this case, the 'xcmCommsAddressUserRole' object MAY be used to specify the role of the system admin, system operator, etc (whose name is specified by 'xcmCommsAddressName', address format is specified by 'xcmCommsAddressTypeOID', and actual address is specified by 'xcmCommsAddressCanonical').

Human-readable name, used by system administrators and end users to identify this protocol entity. Usage: This name SHOULD be the one normally used in a command shell for control of this protocol entity. Usage: When a chain of 'xcmCommsAddressEntry' objects is pointed to by 'xcmHrDevHelpCommsAddressIndex' in the Device Help group of the XCMI Ext to IETF Host Resources MIB (see the 'xcmCommsAddressUserRole' object above) special semantics apply. In this case, the 'xcmCommsAddressName' object MAY be used to specify the name of the system admin, system operator, etc (whose role is specified by 'xcmCommsAddressUserRole', address format is specified by 'xcmCommsAddressTypeOID', and actual address is specified by 'xcmCommsAddressCanonical').

The current canonical address of this protocol entity.

The value of 'xcmCommsAddressIndex' corresponding to a next associated conceptual row in the 'xcmCommsAddressTable', or zero if this is the last associated conceptual row in a given set. Usage: A locally administered 'directory' MAY be searched and/or managed via use of the 'xcmCommsAddressNextIndex' and the 'xcmCommsAddressPreviousIndex' objects referenced from each base protocol entity (ie, stack layer).

The value of 'xcmCommsAddressIndex' corresponding to a previous associated conceptual row in the 'xcmCommsAddressTable', or zero if this is the first associated conceptual row in a given set.

The value of 'xcmCommsOptionIndex' corresponding to the first associated conceptual row in the 'xcmCommsOptionTable', or zero if this address entry does NOT require such information.

A 'sparse' table which augments 'xcmCommsAddressTable' with additional useful information.

A 'sparse' entry which augments 'xcmCommsAddressEntry' with additional useful information.

This object is used to create and delete individual conceptual rows in the 'xcmCommsAddressExtTable'.

A relatively generic description of the current state of this communications entity.

A relatively generic description of the current conditions of this communications entity.

The current address form of this protocol entity.

The current address scope of this protocol entity.

The current address fan out of this protocol entity.

The value of 'xcmCommsMgmtIndex' corresponding to the directly associated conceptual row in the 'xcmCommsMgmtTable', or zero if this 'managed entity' does NOT require such information.

The OID (object identifier) of the conceptual row or simple object which represents some 'owner entity' associated with this entry in the 'xcmCommsAddressExtTable'.

A table containing input and output traffic counters for stack layers.

An entry containing input and output traffic counters for this stack layer.

This object is used to create and delete individual conceptual rows in the 'xcmCommsTrafficTable'.

A layer input unit, used by system administrators and end users of this layer for traffic counters.

A layer output unit, used by system administrators and end users of this layer for traffic counters.

A layer input traffic count, used by system administrators and end users of this layer. Usage: Although no default value ('DEFVAL' clause) is permitted (by IETF SMIv2) for this counter, conforming host systems SHALL zero this counter upon conceptual row creation.

A layer output traffic count, used by system administrators and end users of this layer. Usage: Although no default value ('DEFVAL' clause) is permitted (by IETF SMIv2) for this counter, conforming host systems SHALL zero this counter upon conceptual row creation.

A layer input errors count, used by system administrators and end users of this layer. Usage: Although no default value ('DEFVAL' clause) is permitted (by IETF SMIv2) for this counter, conforming host systems SHALL zero this counter upon conceptual row creation.

A layer output errors count, used by system administrators and end users of this layer. Usage: Although no default value ('DEFVAL' clause) is permitted (by IETF SMIv2) for this counter, conforming host systems SHALL zero this counter upon conceptual row creation.

A table containing current, high-water mark, and maximum permitted values for both connection (or association) and message (or datagram) ports at the upper sides (ie, service provider interfaces) of stack layers.

A table containing current, high-water mark, and maximum permitted values for both connection (or association) and message (or datagram) ports at the upper side (ie, service provider interface) of this stack layer.

This object is used to create and delete individual conceptual rows in the 'xcmCommsAccessTable'.

The current number of connection (or association) ports open at the upper side (ie, service provider interface) of this layer.

The highest number of connection (or association) ports open at the upper side (ie, service provider interface) of this layer.

The maximum number of connection (or association) ports permitted at the upper side (ie, service provider interface) of this layer.

The current number of message (or datagram) ports open at the upper side (ie, service provider interface) of this layer.

The highest number of message (or datagram) ports open at the upper side (ie, service provider interface) of this layer.

The maximum number of message (or datagram) ports permitted at the upper side (ie, service provider interface) of this layer.

A table containing additional management control objects for installed and (possibly) active entities on this host system and supporting detailed and extensible 'states' and 'conditions'.

An entry containing additional management control objects for installed and (possibly) active entity on this host system and supporting detailed and extensible 'states' and 'conditions'.

A unique value used by this host system to identify this conceptual row in the 'xcmCommsMgmtTable'.

This object is used to create and delete individual conceptual rows in the 'xcmCommsMgmtTable'.

The most recent comms management command request specified for this conceptual row in the 'xcmCommsMgmtTable'. Usage: Conforming management agents SHALL 'reject' any SNMP Set-Request to 'xcmCommsMgmtCommand[Request|Data]' while another management operation is already in progress (ie, while 'xcmCommsMgmtCommandInProgress' is 'true'), with 'badValue' (SNMPv1) or 'inconsistentValue' (SNMPv2/v3). Usage: Conforming management stations SHALL set 'xcmCommsMgmtCommandRequest' (mgmt operation) and 'xcmCommsMgmtCommandData' (mgmt arguments) SIMULTANEOUSLY (in the same SNMP Set-Request PDU).

The most recent comms management command data (if any) specified for this conceptual row in the 'xcmCommsMgmtTable'. Usage: Conforming management agents SHALL 'reject' any SNMP Set-Request to 'xcmCommsMgmtCommand[Request|Data]' while another management operation is already in progress (ie, while 'xcmCommsMgmtCommandInProgress' is 'true'), with 'badValue' (SNMPv1) or 'inconsistentValue' (SNMPv2/v3). Usage: Conforming management stations SHALL set 'xcmCommsMgmtCommandRequest' (mgmt operation) and 'xcmCommsMgmtCommandData' (mgmt arguments) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conformant implementations MUST encrypt passwords, keys, and other security information stored in this string object.

The simple comms management error status associated with this conceptual row in 'xcmCommsMgmtTable'. Usage: Conforming management agents SHALL set this object to the value returned in an SNMP Set-Response PDU when a simple comms management operation is 'accepted', ie, when 'xcmCommsMgmtCommandInProgress' goes from 'false' to 'true'. Usage: Conforming management agents SHALL set this object to the value of the completion status of the (possibly deferred) simple comms management operation, when 'xcmCommsMgmtCommandInProgress' goes from 'true' to 'false'.

The comms management in progress status associated with this conceptual row in 'xcmCommsMgmtTable'. Usage: Conforming management agents SHALL 'reject' any SNMP Set-Request to 'xcmCommsMgmtCommand[Request|Data]' while another management operation is already in progress (ie, while 'xcmCommsMgmtCommandInProgress' is 'true'), with 'badValue' (SNMPv1) or 'inconsistentValue' (SNMPv2/v3).