XEROX-GENERAL-MIB: View SNMP OID List / Download MIB

Version: 5.402.pub Xerox General MIB See section 9 'Supplement' of XCMI General TC for implementation and conformance guidance for this MIB module. Copyright (C) 1995-2005 Xerox Corporation. All Rights Reserved.

A table of general counters and capabilities for ease of use of the XCMI General MIB on this host system. Usage: The ONLY valid row in the 'xcmGenBaseTable' SHALL have an 'xcmGenBaseIndex' of one ('1').

An entry of general counters and capabilities for ease of use of the XCMI General MIB on this host system. Usage: The ONLY valid row in the 'xcmGenBaseTable' SHALL have an 'xcmGenBaseIndex' of one ('1').

A unique value used by this host system to identify this conceptual row in the 'xcmGenBaseTable'. Usage: The ONLY valid row in the 'xcmGenBaseTable' SHALL have an 'xcmGenBaseIndex' of one ('1').

This object is used to display status of the ONLY valid conceptual row in the 'xcmGenBaseTable'. Usage: 'xcmGenBaseRowStatus' is 'read-only' because the ONLY valid conceptual row SHALL NOT be deleted.

The value of 'hrDeviceIndex' corresponding to the platform associated conceptual row in the 'hrDeviceTable' representing the CPU device (of type 'hrDeviceProcessor'), which currently supports the executing process/thread of this management agent.

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional XCMI General MIB object groups which are 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 the XCMI General MIB object groups.

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional XCMI General MIB object groups which are 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 the XCMI General MIB object groups.

The terse conformance statement of ALL mandatory, conditionally mandatory, and optional XCMI General MIB object groups which are 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 the XCMI General MIB object groups.

The maximum 'xcmGenClientDataLength' supported for ANY conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming implementations NEED NOT support maximum 'xcmGenClientDataLength' greater than 1 octet.

The 'xcmGenOptionValueSyntax' values supported for ANY conceptual row in the 'xcmGenOptionTable'. Usage: Conforming management agents SHALL report their supported values as a 'bit-mask' formed via the bit-wise OR of '2**(n)', where (n) is each supported enumerated value in the in the 'XcmGenOptionValueSyntax' textual convention.

The 'xcmGenReconfOptionState' values supported for ANY conceptual row in the 'xcmGenReconfTable'. Usage: Conforming management agents SHALL report their supported values as a 'bit-mask' formed via the bit-wise OR of '2**(n)', where (n) is each supported enumerated value in the in the 'XcmGenReconfOptionState' textual convention.

This object is used to specify ALL transport domains (address and name spaces) which are supported by this management agent for SNMP protocol traffic (SNMP responses, SNMP traps, etc), in ALL versions specified by 'xcmGenBaseSNMPVersionSupport'. This object is also used to allow the 'xcmGenTrapClientTable' to be used with any URI scheme (e.g., 'mailto:') for notifications, by specifying 'uriNotifyDomain'. Usage: Conforming management agents SHALL report their supported values as a 'bit-mask' formed via the bit-wise OR of '2**(n)', where (n) is each supported enumerated value in the in the 'XcmGenSNMPDomain' textual convention.

This object SHALL be 'true' if this management agent supports SNMP traps (in any SNMP domain and SNMP version) and MAY support the 'xcmGenTrapClientTable'. This object SHALL be 'false' if this management agent does NOT support SNMP traps (in any SNMP domain and SNMP version) and does NOT support the 'xcmGenTrapClientTable'.

This object is used to specify ALL SNMP versions (RFC 1157, RFC 1905, etc) which are supported by this management agent for SNMP protocol traffic (SNMP responses, SNMP traps, etc), in ALL domains specified by 'xcmGenBaseSNMPDomainSupport'. Usage: Conforming management agents SHALL report their supported values as a 'bit-mask' formed via the bit-wise OR of '2**(n)', where (n) is each supported enumerated value in the in the 'XcmGenSNMPVersion' textual convention.

This object is used to specify a 'read community name' valid for use in SNMPv1c and SNMPv2c 'Get|GetNext|GetBulk' PDUs received (SNMP requests) and generated (SNMP responses) by this management agent. Usage: Note that the object 'xcmGenBaseSNMPWriteCommunity' SHALL ALSO be used to specify a 'read community name' valid for use in SNMPv1c and SNMPv2c 'Get|GetNext|GetBulk' PDUs received (SNMP requests) and generated (SNMP responses) by this management agent. Note however that the object 'xcmGenBaseSNMPTrapCommunity' SHALL NOT be used to specify a 'read community name' valid in SNMP 'Get|GetNext|GetBulk'. Note: XCMI-defined community name objects support 64 octets maximum length and configurable charsets, for consistency with the 'snmpCommunityName' object defined in the SNMP Community MIB defined in RFC 2576 (March 2000). Note: Products MAY ship with a market-specific factory default locale with a charset other than 'utf-8', eg, in Japan a product might factory default to 'shift-jis(17)' or 'iso-2022-jp(39)'. Such products MUST implement the 'xcmGenFixedLocalizationTable', to prevent ambiguity about the factory default charset. Usage: For best interworking with the ('utf-8' charset ONLY) closely related 'snmpCommunitySecurityName' object in RFC 2576, conforming management stations and management agents SHOULD NOT configure community names longer than 32 octets. Usage: For best interworking with third-party applications, conforming management stations and management agents SHOULD NOT configure empty (zero-length or all spaces) community names. Usage: All XCMI conforming management agents SHALL treat a valid 'write community name' as a valid 'read community name' and SHALL NOT increment 'snmpInBadCommunityNames' (unknown name) or 'snmpInBadCommunityUses' (wrong community name for operation) counters in the SNMPv2 Agent MIB (RFC 1907). Usage: All XCMI conforming management agents are STRONGLY RECOMMENDED to support an authenticated SNMP SetRequest to this object, changing the system 'read community name' (for best interworking with third-party management stations). Usage: All XCMI conforming management agents: a) SHALL return a zero length string in response to an SNMP GetRequest of this object; b) are STRONGLY RECOMMENDED to default this object to the string 'public' (in the static charset); and c) MAY support multiple valid 'read community names' (by using 'xcmGenBaseReadCommunity' as a 'window' to a community list via 'device[Set|List]' device operations in the Device Mgmt group of the XCMI Host Resources Ext MIB). Usage: This object is of type 'XcmFixedLocaleDisplayString', with an (opaque) locale and an explicit charset which is specified in the 'xcmGenLocalizationCharSet' object indexed by 'hrDeviceIndex' per 'xcmGenBaseSystemHrDeviceIndex' and 'xcmGenLocalizationIndex' per 'xcmGenFixedLocalizationIndex'. If 'xcmGenLocalizationTable' or 'xcmGenFixedLocalizationTable' are not implemented on this host system, then the charset SHALL be 'utf-8(106)', ISO 10646-1 in 'UTF-8' stream encoding. Usage: All XCMI conforming management agents SHALL allow any defined character in the configured charset of this object. All XCMI conforming management stations SHOULD NOT write control characters or other non-display characters into this object. WARNING: Changing the only valid 'read community name' of an SNMP management agent will cause a COMPLETE loss of communications unless all associated SNMP management stations (clients) ALSO change over to the new 'read community name'!!!

This object is used to specify a 'write community name' valid for use in SNMPv1c and SNMPv2c 'Set' PDUs received (SNMP requests) and generated (SNMP responses) by this management agent. Usage: Note that the object 'xcmGenBaseSNMPWriteCommunity' SHALL ALSO be used to specify a 'read community name' valid for use in SNMPv1c and SNMPv2c 'Get|GetNext|GetBulk' PDUs received (SNMP requests) and generated (SNMP responses) by this management agent. Note however that the object 'xcmGenBaseSNMPTrapCommunity' SHALL NOT be used to specify a 'read community name' valid in SNMP 'Get|GetNext|GetBulk'. Usage: All XCMI conforming management agents SHALL treat a valid 'write community name' as a valid 'read community name' and SHALL NOT increment 'snmpInBadCommunityNames' (unknown name) or 'snmpInBadCommunityUses' (wrong community name for operation) counters in the SNMPv2 Agent MIB (RFC 1907). Note: XCMI-defined community name objects support 64 octets maximum length and configurable charsets, for consistency with the 'snmpCommunityName' object defined in the SNMP Community MIB defined in RFC 2576 (March 2000). Note: Products MAY ship with a market-specific factory default locale with a charset other than 'utf-8', eg, in Japan a product might factory default to 'shift-jis(17)' or 'iso-2022-jp(39)'. Such products MUST implement the 'xcmGenFixedLocalizationTable', to prevent ambiguity about the factory default charset. Usage: For best interworking with the ('utf-8' charset ONLY) closely related 'snmpCommunitySecurityName' object in RFC 2576, conforming management stations and management agents SHOULD NOT configure community names longer than 32 octets. Usage: For best interworking with third-party applications, conforming management stations and management agents SHOULD NOT configure empty (zero-length or all spaces) community names. Usage: All XCMI conforming management agents are STRONGLY RECOMMENDED to support an authenticated SNMP SetRequest to this object, changing the system 'write community name' (for best interworking with third-party management stations). Usage: All XCMI conforming management agents: a) SHALL return a zero length string in response to an SNMP GetRequest of this object; b) are STRONGLY RECOMMENDED to default this object to the string 'public' (in the static charset); and c) MAY support multiple valid 'write community names' (by using 'xcmGenBaseWriteCommunity' as a 'window' to a community list via 'device[Set|List]' device operations in the Device Mgmt group of the XCMI Host Resources Ext MIB). Usage: This object is of type 'XcmFixedLocaleDisplayString' (see DESCRIPTION of 'xcmGenBaseSNMPReadCommunity' above). If 'xcmGenLocalizationTable' or 'xcmGenFixedLocalizationTable' are not implemented on this host system, then the charset SHALL be 'utf-8(106)', ISO 10646-1 in 'UTF-8' stream encoding. Usage: All XCMI conforming management agents SHALL allow any defined character in the configured charset of this object. All XCMI conforming management stations SHOULD NOT write control characters or other non-display characters into this object. Usage: When an SNMP management stations CHANGES the value of this 'write community name', an XCMI conforming management agent SHALL use the old (previous) 'write community name' when generating the SNMP response to the 'Set' PDU, for consistency. WARNING: Changing the only valid 'write community name' of an SNMP management agent will cause a COMPLETE loss of communications unless all associated SNMP management stations (clients) ALSO change over to the new 'write community name'!!!

This object is used to specify a 'trap community name' valid for use in SNMPv1c and SNMPv2c 'Inform|Trap' PDUs received (SNMP requests) and generated (SNMP traps) by this management agent. Usage: Note that the object 'xcmGenBaseSNMPWriteCommunity' SHALL ALSO be used to specify a 'read community name' valid for use in SNMPv1c and SNMPv2c 'Get|GetNext|GetBulk' PDUs received (SNMP requests) and generated (SNMP responses) by this management agent. Note however that the object 'xcmGenBaseSNMPTrapCommunity' SHALL NOT be used to specify a 'read community name' valid in SNMP 'Get|GetNext|GetBulk'. Note: XCMI-defined community name objects support 64 octets maximum length and configurable charsets, for consistency with the 'snmpCommunityName' object defined in the SNMP Community MIB defined in RFC 2576 (March 2000). Note: Products MAY ship with a market-specific factory default locale with a charset other than 'utf-8', eg, in Japan a product might factory default to 'shift-jis(17)' or 'iso-2022-jp(39)'. Such products MUST implement the 'xcmGenFixedLocalizationTable', to prevent ambiguity about the factory default charset. Usage: For best interworking with the ('utf-8' charset ONLY) closely related 'snmpCommunitySecurityName' object in RFC 2576, conforming management stations and management agents SHOULD NOT configure community names longer than 32 octets. Usage: For best interworking with third-party applications, conforming management stations and management agents SHOULD NOT configure empty (zero-length or all spaces) community names. Usage: All XCMI conforming management agents are STRONGLY RECOMMENDED to support an authenticated SNMP SetRequest to this object, changing the system 'trap community name' (for best interworking with third-party management stations). Usage: All XCMI conforming management agents: a) SHALL return a zero length string in response to an SNMP GetRequest of this object; b) are STRONGLY RECOMMENDED to default this object to the string 'public' (in the static charset); and c) MAY support multiple valid 'trap community names' (by using 'xcmGenBaseTrapCommunity' as a 'window' to a community list via 'device[Set|List]' device operations in the Device Mgmt group of the XCMI Host Resources Ext MIB). Usage: This object is of type 'XcmFixedLocaleDisplayString' (see DESCRIPTION of 'xcmGenBaseSNMPReadCommunity' above). If 'xcmGenLocalizationTable' or 'xcmGenFixedLocalizationTable' are not implemented on this host system, then the charset SHALL be 'utf-8(106)', ISO 10646-1 in 'UTF-8' stream encoding. Usage: All XCMI conforming management agents SHALL allow any defined character in the configured charset of this object. All XCMI conforming management stations SHOULD NOT write control characters or other non-display characters into this object. WARNING: Changing the only valid 'trap community name' of an SNMP management agent will cause a COMPLETE loss of communications unless all associated SNMP management stations (clients) ALSO change over to the new 'trap community name'!!!

The terse control/report vector of ALL mandatory, conditionally mandatory, and optional XCMI General MIB object groups which are hidden from MIB walks (via SNMP GetNext or GetBulk PDUs) by this management agent implementation (ie, version) on this host system, specified in a bit-mask. Usage: When an object group is currently 'hidden' via 'xcmGenBaseGroupWalkHidden', XCMI conforming management agents SHALL skip over that object group to the next lexicographically higher object for GetNext or GetBulk requests. Usage: Conforming management agents SHOULD hide the Message Map Message Text object groups from MIB walks (as they MAY contain thousands of conceptual rows in typical implementations). Usage: Conforming management agents SHALL accurately report their hidden MIB walk XCMI General MIB object groups.

The terse conformance statement of ALL notification URI schemes which are 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 notification URI schemes.

The terse conformance statement of ALL notification severity filters supported by this management agent implementation (ie, version) on this host system, specified in a bit-mask. Usage: Individual trap definitions MAY further constrain which notifications are 'in scope'. Usage: Conforming management agents SHALL accurately report their support for notification severity filters.

The terse conformance statement of ALL notification training filters supported by this management agent implementation (ie, version) on this host system, specified in a bit-mask. Usage: Individual trap definitions MAY further constrain which notifications are 'in scope'. Usage: Conforming management agents SHALL accurately report their support for notification training filters.

The value of this variable MUST exactly match the IEEE 1284-2000 Device ID string, except the length field MUST NOT be specified. The value is assigned by the Printer vendor and MUST NOT be localized by the agent. The IEEE 1284-2000 Device ID is a length field followed by a case-sensitive string of ASCII characters defining peripheral characteristics and/or capabilities. For the purposes of this specification, the length bytes MUST NOT be included. The Device ID sequence is composed of a series of keys and values of the form: key: value {,value} repeated for each key As indicated, each key will have one value, and MAY have more than one value. The minimum necessary keys (case-sensitive) are MANUFACTURER, COMMAND SET, and MODEL. (These keys MAY be abbreviated as MFG, CMD, and MDL respectively.) Each implementation MUST supply these three keys and possibly additional ones as well. Each key (and each value) is a string of characters. Any characters except colon (:), comma (,), and semi-colon (;) MAY be included as part of the key (or value) string. Any leading or trailing white space in the string is ignored by the parsing program (but is still counted as part of the overall length of the sequence). An example ID String, showing optional comment and active command set keys and their associated values (the text is actually all on one line): MFG:Xerox; CMD:PCL,POSTSCRIPT,PJL; MDL:WorkCentre Pro 32C; CLS:PRINTER; DES: Xerox WorkCentre Pro 32C

This object SHALL be 'true' if this management agent supports sending SNMP warning traps. This object SHALL be 'false'if this management agent does NOT support sending SNMP warning traps. This does not change the behavior of support for sending 'Error Cleared' traps such sending a trap when an alertRemovalOfBinaryChangeEntry is added to the Alert Table.

General Base Group (XCMI General MIB capabilities)

Current Localization Group (dynamic locales)

General Localization Group (supported dynamic/static locales)

Code Indexed String Group (charset conversions)

Coded Character Set Group (supported IANA-registered charsets)

Fixed Localization Group (static locales)

General Lock Group (advisory contention locks) Implementation of this group is STRONGLY RECOMMENDED.

General Reconf Group (reconfiguration requests)

General Option Group (reconfiguration options)

Client Data Group (network device installs/upgrades)

Trap Client Group (trap destination domains/addresses)

Trap View Group (trap requested object subtrees)

Message Map Group (message labels for client localization)

Message Text Group (message lookups for agent localization)

Notify Rule Group (notification client URI and event names)

Notify Detail Group (notification additional details)

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

A table of general localization information per device. It is put in a table so it can be per device using the hrDeviceIndex.

Contains the scalar objects that we want to be per device.

The value of the 'xcmGenLocalizationIndex' corresponding to the current language, country, and character set which SHALL be used for all objects of type 'InternationalDisplayString' in all legacy MIBs. Note the Printer MIB has a similar mechanism which controls only objects (of type OCTET STRING) which are in the Printer MIB.

This object manages the row status of this conceptual row in the 'xcmGenCurrentLocalizationTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenCurrLocalizationRowStatus' row status object; and SHALL clear the 'xcmGenCurrentLocalizationGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenCurrLocalizationRowStatus' row status object; and SHALL set the 'xcmGenCurrentLocalizationGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations NEED NOT support dynamic row creation (via 'createAndGo(4)') nor dynamic row deletion (via 'destroy(6)'). Usage: Conforming implementations MAY support a single, static conceptual row, but SHALL allocate that row with an 'hrDeviceIndex' value of one ('1'). Usage: This row status SHALL be set, to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), in the same PDU which sets the current locale in 'xcmGenCurrentLocalizationIndex' (thus activating/allocating this conceptual row). Usage: To explicitly release this conceptual row, a management station SHALL set 'xcmGenCurrLocalizationRowStatus' to 'notInService(2)' (for static rows) or 'destroy(6)' (for dynamic rows). Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

The available localizations in this device.

An entry exists in this table for each Localization, i.e. for each combination of Language, Country (or Territory) and Coded Character Set, that is supported in some objects of type 'InternationalDisplayString', 'XcmFixedLocaleDisplayString', 'XcmFixedLocaleUtf8String', or 'XcmNamedLocaleUtf8String' for each device on this managed system.

A unique value used by the device to identify this localization entry.

This object manages the row status of this conceptual row in the 'xcmGenLocalizationTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenLocalizationRowStatus' row status object; and SHALL clear the 'xcmGenLocalizationGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenLocalizationRowStatus' row status object; and SHALL set the 'xcmGenLocalizationGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

The unlocalized human readable name in NVT ASCII of the localization with the language, followed by the country (or territory), followed by the character set. Example: English US ASCII

The localized human readable name of the localization with the language, followed by the country (or territory), followed by the character set. Example: Japanese Japan Kanji (Represented with Kanji chars.)

A two character language abreviation from ISO 639:1988 - Codes For the Representation of Names of Languages. Examples EN, GB, CA, FR, DE.

A two character country or territory abbreviation from ISO 3166:1993 - Codes for the Representation of Names of Countries. Examples: US, FR, DE, ...

The charset used for this localization. The value is the enum for the charset registered with IANA. See the 'IANACharset' textual-convention in the Printer MIB (RFC 1759).

The current charset-indexed strings for this device.

An entry exists in this table containing a charset-indexed string in a particular charset. There are separate sets of charset-indexed strings for each device. If an agent supports multiple charset representations of a charset-indexed string, including code conversion between, there will be a separate entry for each such charset representation. Usage: 'xcmGenCodeIndexedStringCharSet' selects which charset representation is to be returned. The value of 'xcmGenCodeIndexedStringCharSet' is the charset enum registered with IANA. See the 'IANACharset' textual-convention in the Printer MIB (RFC 1759). Usage: Conforming management agents SHALL NOT 'reuse' values of 'xcmGenCodeIndexedStringIndex' until its' 32-bit value wraps. This prevents access to 'xcmGenCodeIndexedStringData' contents via 'stale' pointers (previously cached from XCMI Job Monitoring MIB or XCMI Resources MIB). Note: Conforming management stations SHOULD interwork with earlier (pre-XCMI 3.1) management agents which MAY 'reuse' values of 'xcmGenCodeIndexedStringIndex'. By first reading the pointer object in XCMI Job Monitoring MIB or XCMI Resources MIB, the manager will avoid 'stale' pointer processing errors.

A unique value used by the device, along with the following 'xcmGenCodeIndexedStringCharSet', to identify this charset-indexed string entry. Usage: Conforming management agents SHALL NOT 'reuse' values of 'xcmGenCodeIndexedStringIndex' until its' 32-bit value wraps. This prevents access to 'xcmGenCodeIndexedStringData' contents via 'stale' pointers (previously cached from XCMI Job Monitoring MIB or XCMI Resources MIB). Note: Conforming management stations SHOULD interwork with earlier (pre-XCMI 3.1) management agents which MAY 'reuse' values of 'xcmGenCodeIndexedStringIndex'. By first reading the pointer object in XCMI Job Monitoring MIB or XCMI Resources MIB, the manager will avoid 'stale' pointer processing errors.

The charset used for this charset-indexed string entry. Usage: The value is the enum for the charset registered with IANA. See the 'IANACharset' textual-convention in the Printer MIB (RFC 1759).

This object manages the row status of this conceptual row in the 'xcmGenCodeIndexedStringTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenCodeIndexedStringRowStat' row status object; and SHALL clear the 'xcmGenCodeIndexedStringGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenCodeIndexedStringRowStat' row status object; and SHALL set the 'xcmGenCodeIndexedStringGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

This is the actual charset-indexed string data, in the charset identified by 'xcmGenCodeIndexedStringCharSet'.

The supported charsets for this device.

An entry exists in this table for each charset supported in some objects of 'CodeIndexedStringIndex' type for each device.

The supported charset enum identifier, used an index for this table. The value is the enum for the charset registered with IANA.

This object manages the row status of this conceptual row in the 'xcmGenCodedCharSetTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenCodedCharSetRowStatus' row status object; and SHALL clear the 'xcmGenCodedCharSetGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenCodedCharSetRowStatus' row status object; and SHALL set the 'xcmGenCodedCharSetGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations NEED NOT support dynamic row creation (via 'createAndGo(4)') nor dynamic row deletion (via 'destroy(6)'). Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

The unlocalized human readable name in ASCII of the charset. Example: 'ASCII'

A table of fixed localization information per device. It is put in a table so it can be per device using the hrDeviceIndex.

An entry of fixed localization information per device.

The value of the 'xcmGenLocalizationIndex' corresponding to the current language, country, and character set which SHALL be used for all objects of type 'XcmFixedLocaleDisplayString' in all current and future MIBs. Also, the value of the 'xcmGenLocalizationIndex' corresponding to the language and country (but FIXED UTF-8) which SHALL be used for all objects of type 'XcmFixedLocaleUtf8String' in all current and future MIBs.

This object manages the row status of this conceptual row in the 'xcmGenFixedLocalizationTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenFixedLocalizationRowStat' row status object; and SHALL clear the 'xcmGenFixedLocalizationGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenFixedLocalizationRowStat' row status object; and SHALL set the 'xcmGenFixedLocalizationGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations NEED NOT support dynamic row creation (via 'createAndGo(4)') nor dynamic row deletion (via 'destroy(6)'). Usage: Conforming implementations MAY support a single, static conceptual row, but SHALL allocate that row with an 'hrDeviceIndex' value of one ('1'). Usage: This row status SHALL be set, to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), in the same PDU which sets the fixed locale in 'xcmGenFixedLocalizationIndex' (thus activating/allocating this conceptual row). Usage: To explicitly release this conceptual row, a management station SHALL set 'xcmGenFixedLocalizationRowStat' to 'notInService(2)' (for static rows) or 'destroy(6)' (for dynamic rows). Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

This subtree is current. Subordinate objects are leaf objects.

The advisory lock supported max owner timer (in seconds) for use for ANY advisory lock in the 'xcmGenLockTable'. Usage: The value zero ('0') represents 'no limit'. Usage: This supported max timer represents an XCMI enhancement to the traditional advisory lock mechanism used in existing IETF MIB modules (eg, RFC 1573). It provides reliable information to a management station contending for advisory locks, about the MAXIMUM time supported (ie, permitted) for ANY advisory lock by the management agent on this host system.

The advisory lock current max owner timer (in seconds) in use for ANY advisory lock in the 'xcmGenLockTable'. Usage: This current max timer represents an XCMI enhancement to the traditional advisory lock mechanism used in existing IETF MIB modules (eg, RFC 1573). It provides reliable information to a management station contending for advisory locks, about the current MAXIMUM time until expiration for ALL advisory locks for the management agent on this host system. Note: To acquire an advisory lock on an ENTIRE host system, a conforming management station (or management agent) SHALL examine 'xcmGenLockCurrentMaxTimer', add an appropriate delta for eventual processing, and lock the 'xcmGenLockTable' itself. When 'xcmGenLockCurrentLockCount' subsequently becomes one (1), the requesting management station (or management agent) has acquired a lock on the ENTIRE host system (since no OTHER entity MAY acquire any further lock, because 'xcmGenLockTable' has become 'read-only' to all other entities), and MAY proceed accordingly.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenLockTable'. Usage: This current lock count represents an XCMI enhancement to the traditional advisory lock mechanism used in existing IETF MIB modules (eg, RFC 1573).

The highest advisory lock index which has been active in the 'xcmGenLockTable'. Usage: This highest lock index represents an XCMI enhancement to the traditional advisory lock mechanism used in existing IETF MIB modules (eg, RFC 1573).

The maximum number of simultaneous entries (rows) supported for the 'xcmGenLockTable'. Usage: The value zero ('0') represents 'no limit'.

A table containing 'advisory contention lock' objects for various subtrees of MIB objects from the complete set of IETF and XCMI MIB modules implemented by this host system. Note: To acquire an advisory lock on an ENTIRE host system, a conforming management station (or management agent) SHALL examine 'xcmGenLockCurrentMaxTimer', add an appropriate delta for eventual processing, and lock the 'xcmGenLockTable' itself. When 'xcmGenLockCurrentLockCount' subsequently becomes one (1), the requesting management station (or management agent) has acquired a lock on the ENTIRE host system (since no OTHER entity MAY acquire any further lock, because 'xcmGenLockTable' has become 'read-only' to all other entities), and MAY proceed accordingly.

An entry containing 'advisory contention lock' objects for one specific subtree of MIB objects from the complete set of IETF and XCMI MIB modules implemented by this host system.

A unique value used by this host system to identify this conceptual row in the 'xcmGenLockTable' - each conceptual row in the 'xcmGenLockTable' represents an 'advisory contention lock' on a specific subtree of MIB objects from the complete set of IETF and XCMI MIB modules implemented by this host system.

This object manages the row status of this conceptual row in the 'xcmGenLockTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenLockRowStatus' row status object; and SHALL clear the 'xcmGenLockGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenLockRowStatus' row status object; and SHALL set the 'xcmGenLockGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations NEED NOT support dynamic row creation (via 'createAndGo(4)') nor dynamic row deletion (via 'destroy(6)'). Usage: Conforming implementations MAY support a single, static conceptual row, but SHALL allocate that row with an 'xcmGenLockIndex' value of one ('1'). Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenLockRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenLockOwnerString' (if an owner string is available), 'xcmGenLockOwnerSubtree' (if not 'zeroDotZero'), and 'xcmGenLockOwnerTimer' (to a suitable value) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenLockOwnerString', or 'xcmGenLockOwnerSubtree' AFTER row creation (these objects are 'write-once'). Usage: To explicitly release this advisory lock, the current lock owner (management station or management agent) SHALL set 'xcmGenLockRowStatus' in this row to 'notInService(2)' (for static rows) or 'destroy(6)' (for dynamic rows). Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

The advisory lock owner string corresponding to the current 'owner' of this advisory lock. Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenLockRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenLockOwnerString' (if an owner string is available), 'xcmGenLockOwnerSubtree' (if not 'zeroDotZero'), and 'xcmGenLockOwnerTimer' (to a suitable value) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenLockOwnerString', or 'xcmGenLockOwnerSubtree' AFTER row creation (these objects are 'write-once'). Usage: This owner string SHALL contain one or more of the following: a) Textual form of the management station's transport address; b) Management station name (eg, domain name); and/or c) Network management person's name, location, or phone. In the instance that the management agent itself is the 'owner', this object SHALL be set to a string beginning with 'agent' (in English). Usage: This object is of type 'XcmFixedLocaleDisplayString'.

The advisory lock owner subtree (ie, scope) for the current 'owner' of this advisory lock. Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenLockRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenLockOwnerString' (if an owner string is available), 'xcmGenLockOwnerSubtree' (if not 'zeroDotZero'), and 'xcmGenLockOwnerTimer' (to a suitable value) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenLockOwnerString', or 'xcmGenLockOwnerSubtree' AFTER row creation (these objects are 'write-once'). Usage: This owner subtree represents an XCMI enhancement to the traditional advisory lock mechanism used in existing IETF MIB modules (eg, RFC 1573).

The advisory lock owner lock time remaining for the current 'owner' of this advisory lock (in seconds). Usage: A conforming management agent MAY choose to reduce the 'credit' granted as a result of a set to this owner lock timer, at its sole discretion (see 'xcmGenLockSupportMaxTimer' object). Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenLockRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenLockOwnerString' (if an owner string is available), 'xcmGenLockOwnerSubtree' (if not 'zeroDotZero'), and 'xcmGenLockOwnerTimer' (to a suitable value) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenLockOwnerString', or 'xcmGenLockOwnerSubtree' AFTER row creation (these objects are 'write-once'). Usage: A conforming management station MAY choose to increase or reduce the value of this owner lock timer, subsequent to initial row creation, for example to 'refresh' the timer for an additional time interval. Usage: A conforming management station SHALL NOT reduce the value of this owner lock timer to zero (as an indirect 'destroy' operation). A conforming management agent SHALL reject any such set to zero of this owner lock timer. Usage: This owner lock timer represents an XCMI enhancement to the traditional advisory lock mechanism used in existing IETF MIB modules (eg, RFC 1573). It provides reliable information to a management station (or management agent) contending for this advisory lock, about the MAXIMUM time until this advisory lock lock will be released (either by explicit action of the owner of the advisory lock or by 'timeout' handling of the management agent itself).

This subtree is current. Subordinate objects are leaf objects.

The count of SUCCESSFUL 'activations' of reconfiguration for this host system: invoked by SUCCESSFUL writes to the 'xcmGenReconfOptionState' reconfiguration invocation object of 'activateFor[ImmediateChange|RebootChange|ImmediateReboot]'; and followed by SUCCESSFUL completions of 'activation' (without errors reports in 'xcmGenReconfError[Index|Status]'). 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.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenReconfTable'.

The maximum number of simultaneous entries (rows) supported for the 'xcmGenReconfTable'. Usage: The value zero ('0') represents 'no limit'.

A table containing information on a 'reconfiguration request', for use in atomic reconfiguration of this host system. Usage: A conforming management station (or management agent) SHALL lock 'xcmGenReconfTable' and 'xcmGenOptionTable' before attempting to perform any 'reconfiguration request' on a host system (via the 'xcmGenLockTable').

An entry containing information on a 'reconfiguration request', for use in atomic reconfiguration of this host system. Usage: The ONLY valid row in the 'xcmGenReconfTable' for each supported device ('hrDeviceIndex') SHALL have an 'xcmGenReconfIndex' of one ('1').

A unique value used by this host system to identify this conceptual row in the 'xcmGenReconfTable'. Usage: The ONLY valid row in the 'xcmGenReconfTable' for each supported device ('hrDeviceIndex') SHALL have an 'xcmGenReconfIndex' of one ('1').

This object manages the row status of this conceptual row in the 'xcmGenReconfTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenReconfRowStatus' row status object; and SHALL clear the 'xcmGenReconfGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenReconfRowStatus' row status object; and SHALL set the 'xcmGenReconfGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming management agents SHALL support 'active(1)' and SHOULD support 'notInService(2)' or 'destroy(6)' (to 'release' the 'reconfiguration request'). Usage: Conforming management agents NEED NOT support 'createAndGo(4)', and SHOULD NOT support 'notReady(3)' or 'createAndWait(5)'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

The value of 'xcmGenOptionIndex' corresponding to the first pending reconfiguration option (in 'xcmGenOptionTable'), or zero if there are no pending reconfiguration options for this host system. Usage: This 'chain' represents pending reconfiguration options of this host system.

The processing state of ALL pending reconfiguration options of this host system. A write to this object by an (authorized) management station invokes a request for validation (or activation) of ALL pending reconfiguration options of this host system. A read of this object returns 'idle', 'validateInProgress', or 'activateInProgress' to report the processing state of the last 'validate...' or 'activate...' request. It is mandatory that a conforming management agent ensure that, at system initialization, this object SHALL be set to a value of 'idle'. Usage: Conforming management agents SHALL 'reject' any SNMP Set-Request to 'xcmGenReconfOptionState' while another management operation is already in progress (ie, while 'xcmGenReconfOptionState' is NOT equal to 'idle') with 'badValue' (SNMPv1) or 'inconsistentValue' (SNMPv2/v3). Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this option state object.

The value of 'xcmGenOptionIndex' corresponding to the first pending reconfiguration option (in 'xcmGenOptionTable') which was found to be 'in error' (during 'validate' or 'activate' reconfiguration processing for this host system), or zero if no error was found (eg, consistency, range, etc).

The reconfiguration error status corresponding to the first pending reconfiguration option (in 'xcmGenOptionTable') which was found to be 'in error' (during 'validate' or 'activate' reconfiguration processing for this host system), or 'noError' if no error was found (eg, consistency, range, etc).

This subtree is current. Subordinate objects are leaf objects.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenOptionTable'.

The maximum number of simultaneous entries (rows) supported for the 'xcmGenOptionTable'. Usage: The value zero ('0') represents 'no limit'.

A table containing information on reconfiguration options, for use in atomic reconfiguration of this host system. Usage: A conforming management station (or management agent) SHALL lock 'xcmGenReconfTable' and 'xcmGenOptionTable' before attempting to perform any 'reconfiguration request' on a host system (via the 'xcmGenLockTable'). Note: The 'xcmGenOptionTable' is indexed by 'hrDeviceIndex', so the 'hrDeviceIndex' element of a columnar object instance ID (ie, fully specified object identifier) NEED NOT be specified in 'xcmGenOptionTypeOID'. To reconfigure objects indexed by several devices in 'hrDeviceTable' of the IETF Host Resources MIB (RFC 2790), a conforming management station SHALL use several rows in 'xcmGenReconfTable' and several trees of objects in 'xcmGenOptionTable' with appropriate 'hrDeviceIndex' values. To reconfigure objects which are actually NOT indexed by 'hrDeviceIndex', it is RECOMMENDED that rows be used in 'xcmGenOptionTable' which are indexed by 'hrDeviceIndex' for an 'hrDeviceType' of 'hrDeviceUnknown'.

An entry containing information on a reconfiguration option, for use in atomic reconfiguration of this host system.

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

This object manages the row status of this conceptual row in the 'xcmGenOptionTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenOptionRowStatus' row status object; and SHALL clear the 'xcmGenOptionGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenOptionRowStatus' row status object; and SHALL set the 'xcmGenOptionGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming management agents SHALL support 'active(1)' and SHOULD support 'notInService(2)' or 'destroy(6)' (to 'release' the 'reconfiguration option'). Usage: Conforming management agents NEED NOT support 'createAndGo(4)', and SHOULD NOT support 'notReady(3)' or 'createAndWait(5)'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

An unambiguous reconfiguration option type, used by system administrators and end users to identify this reconfiguration option. Usage: Since this reconfiguration option 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'.

A reconfiguration option value syntax, used by system administrators and end users to specify the correct value syntax for this reconfiguration option. Usage: This reconfiguration option value syntax is used to select which of the following three objects SHALL be used to contain the value of this reconfiguration option.

A reconfiguration option value integer, used by system administrators and end users to specify the current value for a reconfiguration option with a base value syntax of 'INTEGER'. Note: This object has the type 'Integer32', rather than 'INTEGER'. This a work-around to compiler warnings which occur when 'INTEGER' is used without a range specification. And if we had range qualified, it would have been identical to the SNMP 'Integer32' type. In SNMPv2, only the 'Counter64 is an integer type wider 32 bits, and for backward compatibility we depricated the use of Counter64.

A reconfiguration option value OID (object identifier), used by system administrators and end users to specify the current value for a reconfiguration option with a base value syntax of 'OBJECT IDENTIFIER'.

A reconfiguration option value string, used by system administrators and end users to specify the current value for a reconfiguration option with a base value syntax of 'OCTET STRING'. Usage: This object is of type 'XcmFixedLocaleDisplayString' (if 'xcmGenOptionValueLocalization' is zero) or 'XcmNamedLocaleUtf8String' (if 'xcmGenOptionValueLocalization' is non-zero).

A reconfiguration option value localization, used by system administrators and end users to specify the ALTERNATE localization for a reconfiguration option (different from 'xcmGenFixedLocalizationIndex'), so that 'xcmGenOptionValueString' becomes 'XcmNamedLocaleUtf8String'. Usage: For a reconfiguration option string to which POSIX-style localization (territory, language, character set) is applicable (non-keyword) this object MAY contain a suitable index value for 'xcmGenLocalizationIndex' from the XCMI General MIB, or zero to indicate 'none'.

A reconfiguration option value character set, used by system administrators and end users to specify the ALTERNATE character set for a reconfiguration option (different from 'xcmGenFixedLocalizationIndex'), so that 'xcmGenOptionValueString' is unambiguous. Usage: XCMI conforming management agents SHALL ONLY allow Sets of this object to 'other' (none) or 'utf-8' (Unicode/ ISO-10646 in the UTF-8 encoding, a proper superset of US-ASCII), for consistency with the Xerox Unicode Coherence Standard.

The value of 'xcmGenOptionIndex' corresponding to the next 'chained' conceptual row in the 'xcmGenOptionTable', or zero if this is the last associated conceptual row in a particular vertical 'chain' within a given set. Usage: Generally, reconfiguration options (of similar or unlike type) are 'chained' vertically via '...[Next|Previous]Index'. But, in the case where particular communications options MUST be 'tightly coupled', they SHOULD be 'shelved' horizontally via '...[Family|Previous]Index' (eg, an IP address and an IP subnet mask).

The value of 'xcmGenOptionIndex' corresponding to a previous associated conceptual row in the 'xcmGenOptionTable', or zero if this is the first associated conceptual row in a given set. Usage: This object provides common 'backward' linkage for BOTH the 'xcmGenOptionNextIndex' and 'xcmGenOptionFamilyIndex' linkage objects. A previous conceptual row MAY 'forward' reference this conceptual row via either '...NextIndex' or '...FamilyIndex' - ie, a given conceptual row MAY 'forward' reference EXACTLY zero, one, or two 'later' conceptual rows.

The value of 'xcmGenOptionIndex' corresponding to a next 'family' conceptual row in the 'xcmGenOptionTable', or zero if this conceptual row has no associated 'family' members. Usage: Generally, reconfiguration options (of similar or unlike type) are 'chained' vertically via '...[Next|Previous]Index'. But, in the case where particular reconfiguration options MUST be 'tightly coupled', they SHOULD be 'shelved' horizontally via '...FamilyIndex' (eg, an IP address and an IP subnet mask).

This subtree is current. Subordinate objects are leaf objects.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenClientDataTable'.

The last entry index (regardless of its current state) in the 'xcmGenClientDataTable' of this General MIB, on this host system. Usage: This last entry index explicitly bounds the valid range of 'xcmGenClientDataIndex'.

The maximum number of simultaneous entries (rows) supported for the 'xcmGenClientDataTable'. Usage: The value zero ('0') represents 'no limit'.

A table containing 'client data' objects for use by conforming management stations/agents, particularly during installation of this host system. Usage: For managed systems which support static rows (ie, 'read-write'), a management station (or management agent) SHALL search 'xcmGenClientDataRowStatus', to determine the appropriate value of 'xcmGenClientDataIndex' to use when allocating an existing row in the 'xcmGenClientDataTable'. Usage: For managed systems which support dynamic rows (ie, 'read-create'), a management station (or management agent) SHALL examine 'xcmGenClientDataLastIndex', to determine the appropriate value of 'xcmGenClientDataIndex' to use when creating a new row in the 'xcmGenClientDataTable'. Usage: Throughout this specification, the term 'stable storage' refers to storage which is reliable over long durations (years) and is NOT destroyed by host system reboot (eg, battery-backed DRAM is 'stable storage' - while simple DRAM is NOT 'stable storage'). Examples of valid 'stable storage' include: NVRAM, hard disk, EEPROM, etc. Usage: Conforming implementations SHALL preserve active 'client data' objects across management agent power cycles, and SHALL implement one of the following two methods: 1) The agent SHALL store 'client data' objects directly in 'stable storage'; or 2) The agent SHALL automatically checkpoint all active 'client data' objects to 'stable storage' with reasonable frequency (either due to a write to some 'client data' object, or upon expiration of a product-specific timeout). Usage: Conforming implementations MAY (optionally) support one of the following two 'checkpoint protocols': 1) A client sends a 'Set' of 'xcmGenClientDataRowStatus' to 'active(1)', to request that a 'checkpoint' be performed; 2a) An agent which supports 'rapid checkpoint', completes the checkpoint to 'stable storage', and sends a 'SetResponse' with 'noError(0)'; 2b) An agent which supports 'delayed checkpoint', changes 'xcmGenClientDataRowStatus' to 'notInService(2)', sends a 'SetResponse' with 'noError(0)', completes the checkpoint to 'stable storage', and later changes 'xcmGenClientDataRowStatus' back to 'active(1)'.

An entry containing 'client data' objects for use by conforming management stations/agents, particularly during installation of this host system.

A unique value used by this host system to identify this conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming implementations which only support a single, statically allocated row, SHALL allocate that row with an 'xcmGenClientDataIndex' value of one (1).

This object manages the row status of this conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming implementations which support static rows SHALL support 'active' and 'notInService' writes to this 'xcmGenClientDataRowStatus' row status object; and SHALL clear the 'xcmGenClientDataGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenClientDataRowStatus' row status object; and SHALL set the 'xcmGenClientDataGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming implementations NEED NOT support dynamic row creation (via 'createAndGo(4)') nor dynamic row deletion (via 'destroy(6)'). Usage: Conforming implementations MAY support a single, static conceptual row, but SHALL allocate that row with an 'xcmGenClientDataIndex' value of one ('1'). Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenClientDataRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenClientDataRequestID' (to a suitable client global ID), 'xcmGenClientDataProductID' (to a suitable client product ID), 'xcmGenClientDataLength' (to a suitable client data length) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenClientDataRequestID', 'xcmGenClientDataProductID', or 'xcmGenClientDataLength' AFTER row creation (these objects are 'write-once'). Usage: To explicitly release this conceptual row, the client data owner SHALL set 'xcmGenClientDataRowStatus' to 'notInService(2)' (for static rows) or 'destroy(6)' (for dynamic rows). Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

The client data request date which uniquely timestamps the creation of this conceptual row in the 'xcmGenClientDataTable'. Usage: This request date SHALL be set (to a suitable value) by conforming management agents during creation of each conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming implementations which have a source of time, SHALL set a meaningful value in this object. ONLY those implementations which do NOT have a source of time, SHALL return the following DEFVAL.

The client data owner request ID which uniquely identifies the creation of this conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenClientDataRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenClientDataRequestID' (to a suitable client global ID), 'xcmGenClientDataProductID' (to a suitable client product ID), 'xcmGenClientDataLength' (to a suitable client data length) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenClientDataRequestID', 'xcmGenClientDataProductID', or 'xcmGenClientDataLength' AFTER row creation (these objects are 'write-once').

The client data owner product ID corresponding to the current 'owner' of this client data. Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenClientDataRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenClientDataRequestID' (to a suitable client global ID), 'xcmGenClientDataProductID' (to a suitable client product ID), 'xcmGenClientDataLength' (to a suitable client data length) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenClientDataRequestID', 'xcmGenClientDataProductID', or 'xcmGenClientDataLength' AFTER row creation (these objects are 'write-once').

The client data length requested/granted for this conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming implementations NEED NOT support maximum client data length greater than 1 octet. Usage: Conforming management stations, when they first create or activate rows in this table, SHALL set 'xcmGenClientDataRowStatus' to 'active(1)' (for static rows) or 'createAndGo(4)' (for dynamic rows), 'xcmGenClientDataRequestID' (to a suitable client global ID), 'xcmGenClientDataProductID' (to a suitable client product ID), 'xcmGenClientDataLength' (to a suitable client data length) SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenClientDataRequestID', 'xcmGenClientDataProductID', or 'xcmGenClientDataLength' AFTER row creation (these objects are 'write-once').

The client data string currently set into this conceptual row in the 'xcmGenClientDataTable'. Usage: Conforming implementations NEED NOT support maximum client data length greater than 1 octet. Usage: This data string NEED NOT be set (to a suitable value) by the client data owner, in the same PDU which creates each conceptual row in the 'xcmGenClientDataTable'.

This subtree is current. Subordinate objects are leaf objects.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenTrapClientTable'.

The maximum number of simultaneous entries (rows) supported for the 'xcmGenTrapClientTable'. Usage: The value zero ('0') represents 'no limit'.

A table of SNMP trap clients (management stations or proxies) registered for trap delivery from this host system. Usage: SNMP version/transport independent trap registration. Usage: Conforming management stations SHALL create at least one subordinate row in the 'xcmGenTrapViewTable' for each trap client that they register in the 'xcmGenTrapClientTable'. Conforming management agents SHOULD interpret a dangling row in the 'xcmGenTrapClientTable' (no children) as 'NO traps in view' (existing implementations of both clients and devices are known to consider dangling rows invalid). To register for all device traps, use a single view of 'iso(1).org(3).dod(6).internet(1)'. Usage: Conforming management agents SHALL delete any rows in the 'xcmGenTrapViewTable' which were subordinate to a deleted row in the 'xcmGenTrapClientTable'.

An entry for an SNMP trap client (management station or proxy) registered for trap delivery from this host system.

This object is used to specify the transport domain (address and name space) which SHALL be used by this management agent for SNMP protocol traffic (transmission of SNMP traps), in the version specified by 'xcmGenTrapClientSNMPVersion', to the trap client (management station or proxy). This object is also used to allow the 'xcmGenTrapClientTable' to be used with any URI scheme (e.g., 'mailto:') for notifications, by specifying 'uriNotifyDomain'.

This object is used to specify the transport address (below SNMP) which SHALL be used by this management agent to deliver SNMP traps to the trap client (management station or proxy). Usage: This transport address usually consists of an underlying network layer address with a suffixed transport selector. Usage: This object is of type 'XcmFixedLocaleDisplayString'.

This object manages the row status of this conceptual row in the 'xcmGenTrapClientTable'. Usage: It is conformant to implement this object as read-only, however, conforming management agents are STRONGLY RECOMMENDED to support at least read-write access to this object. Usage: Conforming management stations, when they first create new rows in this table, SHALL set 'xcmGenTrapClientRowStatus' (to 'createAndGo'), 'xcmGenTrapClientRowPersistence' (if not 'volatile'), 'xcmGenTrapClientSNMPVersion' (if not 'snmpV1Community'), and 'xcmGenTrapClientSNMPCommunity' (if not the current managed system default in 'xcmGenBaseSNMPTrapCommunity') SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenTrapClientRowPersistence', 'xcmGenTrapClientSNMPVersion', or 'xcmGenTrapClientSNMPCommunity' AFTER row creation (these objects are 'write-once'). Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenTrapClientRowStatus' row status object; and SHALL set the 'xcmGenTrapClientGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming management agents SHOULD NOT support 'notInService(2)', 'notReady(3)', or 'createAndWait(5)'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

A unique value ASSIGNED by this host system to identify this conceptual row in the 'xcmGenTrapClientTable'. This object is used to specify the unique client index which was chosen FOR the trap client registered in this conceptual row (management station or proxy) at row creation and which SHALL be used by the trap client to create any associated conceptual rows in the 'xcmGenTrapViewTable'. Usage: Conforming management agents NEED NOT preserve the value of this object across power cycles for 'nonvolatile' rows in the 'xcmGenTrapClientTable', but SHALL preserve the configured associations with (any) subordinate rows in the 'xcmGenTrapViewTable'.

This object is used to specify the persistence of this conceptual row in the 'xcmGenTrapClientTable' (and associated conceptual rows in the 'xcmGenTrapViewTable'). Usage: It is conformant to implement this object as read-only, however, conforming management agents are STRONGLY RECOMMENDED to support at least read-write access to this object. Usage: Conforming management stations, when they first create new rows in this table, SHALL set 'xcmGenTrapClientRowStatus' (to 'createAndGo'), 'xcmGenTrapClientRowPersistence' (if not 'volatile'), 'xcmGenTrapClientSNMPVersion' (if not 'snmpV1Community'), and 'xcmGenTrapClientSNMPCommunity' (if not the current managed system default in 'xcmGenBaseSNMPTrapCommunity') SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenTrapClientRowPersistence', 'xcmGenTrapClientSNMPVersion', or 'xcmGenTrapClientSNMPCommunity' AFTER row creation (these objects are 'write-once'). Usage: Dynamically created rows SHALL be given 'volatile' or 'nonvolatile' persistence. Usage: Conforming management agents SHALL support 'volatile' (lost across power cycles). Usage: Conforming management agents are STRONGLY RECOMMENDED to support 'nonvolatile' (preserved across power cycles), but NEED NOT support any other levels of persistence.

This object is used to specify the SNMP version (RFC 1157, RFC 1905, etc) which SHALL be used by this management agent for SNMP protocol traffic (transmission of SNMP traps), in the domain specified by 'xcmGenTrapClientSNMPDomain', to the trap client (management station or proxy). Usage: Conforming management stations, when they first create new rows in this table, SHALL set 'xcmGenTrapClientRowStatus' (to 'createAndGo'), 'xcmGenTrapClientRowPersistence' (if not 'volatile'), 'xcmGenTrapClientSNMPVersion' (if not 'snmpV1Community'), and 'xcmGenTrapClientSNMPCommunity' (if not the current managed system default in 'xcmGenBaseSNMPTrapCommunity') SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenTrapClientRowPersistence', 'xcmGenTrapClientSNMPVersion', or 'xcmGenTrapClientSNMPCommunity' AFTER row creation (these objects are 'write-once').

This object is used to specify the 'trap community name' used in all SNMPv1c and SNMPv2c 'Inform|Trap' PDUs which SHALL be generated by this SNMP management agent, in the domain specified by 'xcmGenTrapClientSNMPDomain', to the trap client (management station or proxy). Note: XCMI-defined community name objects support 64 octets maximum length and configurable charsets, for consistency with the 'snmpCommunityName' object defined in the SNMP Community MIB defined in RFC 2576 (March 2000). Note: Products MAY ship with a market-specific factory default locale with a charset other than 'utf-8', eg, in Japan a product might factory default to 'shift-jis(17)' or 'iso-2022-jp(39)'. Such products MUST implement the 'xcmGenFixedLocalizationTable', to prevent ambiguity about the factory default charset. Usage: For best interworking with the ('utf-8' charset ONLY) closely related 'snmpCommunitySecurityName' object in RFC 2576, conforming management stations and management agents SHOULD NOT configure community names longer than 32 octets. Usage: For best interworking with third-party applications, conforming management stations and management agents SHOULD NOT configure empty (zero-length or all spaces) community names. Usage: Conforming management stations, when they first create new rows in this table, SHALL set 'xcmGenTrapClientRowStatus' (to 'createAndGo'), 'xcmGenTrapClientRowPersistence' (if not 'volatile'), 'xcmGenTrapClientSNMPVersion' (if not 'snmpV1Community'), and 'xcmGenTrapClientSNMPCommunity' (if not the current managed system default in 'xcmGenBaseSNMPTrapCommunity') SIMULTANEOUSLY (in the same SNMP Set-Request PDU). Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenTrapClientRowPersistence', 'xcmGenTrapClientSNMPVersion', or 'xcmGenTrapClientSNMPCommunity' AFTER row creation (these objects are 'write-once'). Usage: This object SHALL be set by all XCMI conforming SNMP trap generators (managed host systems) to the default value of 'xcmGenBaseSNMPTrapCommunity', when NOT supplied by the requesting SNMP trap client (management station or proxy) at the time of row creation. Usage: This object is of type 'XcmFixedLocaleDisplayString' (see DESCRIPTION of 'xcmGenBaseSNMPReadCommunity' above). If 'xcmGenLocalizationTable' or 'xcmGenFixedLocalizationTable' are not implemented on this host system, then the charset SHALL be 'utf-8(106)', ISO 10646-1 in 'UTF-8' stream encoding. Usage: All XCMI conforming management agents SHALL allow any defined character in the configured charset of this object. All XCMI conforming management stations SHOULD NOT write control characters or other non-display characters into this object. WARNING: Changing the configured 'trap community name' of an SNMP trap client registration will cause a COMPLETE loss of communications unless the associated SNMP management station (client) ALSO changes over to the new 'trap community name'!!!

This subtree is current. Subordinate objects are leaf objects.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenTrapViewTable'.

The maximum number of simultaneous entries (rows) supported for the 'xcmGenTrapViewTable'. Usage: The value zero ('0') represents 'no limit'.

A table of SNMP trap object subtrees (ie, trap scopes) registered for trap delivery from this host system to the associated trap client (management station or proxy). Usage: SNMP version/transport independent trap registration. Usage: Conforming management stations SHALL create at least one subordinate row in the 'xcmGenTrapViewTable' for each trap client that they register in the 'xcmGenTrapClientTable'. Conforming management agents SHOULD interpret a dangling row in the 'xcmGenTrapClientTable' (no children) as 'NO traps in view' (existing implementations of both clients and devices are known to consider dangling rows invalid). To register for all device traps, use a single view of 'iso(1).org(3).dod(6).internet(1)'. Usage: Conforming management agents SHALL delete any rows in the 'xcmGenTrapViewTable' which were subordinate to a deleted row in the 'xcmGenTrapClientTable'.

An entry for an SNMP trap object subtree (ie, trap scope) registered for trap delivery from this host system to the associated trap client (management station or proxy).

This object is used to specify the object subtree (within MIBs) which is 'in scope' for this trap view.

This object manages the row status of this conceptual row in the 'xcmGenTrapViewTable'. Usage: Conforming implementations which support dynamic rows SHALL support 'createAndGo' and 'destroy' writes to this 'xcmGenTrapViewRowStatus' row status object; and SHALL set the 'xcmGenTrapViewGroup' bit in 'xcmGenBaseGroupCreateSupport' in the 'xcmGenBaseTable'. Usage: Conforming management agents SHOULD NOT support 'notInService(2)', 'notReady(3)', or 'createAndWait(5)'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

This object is used to specify the notification severity filter used to 'screen' notifications 'in scope' for this trap view. Usage: Individual trap definitions MAY further constrain which notifications are 'in scope'.

This object is used to specify the notification training filter used to 'screen' notifications 'in scope' for this trap view. Usage: Individual trap definitions MAY further constrain which notifications are 'in scope'.

A table of message string labels for the current contents of static (agent-generated) message string objects, in all MIBs implemented by this host system. Usage: Exposes the server's message catalog for indirect search via source message object OIDs, yielding message string labels. Usage: Supports reliable translation by clients (managers) of static (agent-generated) message strings, INDEPENDENT of the current language/country/charset of the message strings on the managed host system in the conventional MIB objects. Conformance: XCMI conforming management agents SHALL support SNMP Get requests to the 'xcmGenMessageMapTable' (ie, agents must respond to valid explicit EXACT requests). When 'xcmGenMessageMapTable' is currently 'hidden' via 'xcmGenBaseGroupWalkHidden', XCMI conforming management agents SHALL skip over 'xcmGenMessageMapTable' to the next lexicographically higher object for GetNext or GetBulk requests - 'xcmGenMessageMapTable' SHOULD be invisible to MIB walks, to avoid undesirable performance degradation with third-party network management stations and other monitoring tools.

A entry for a message string label for the current contents of a static (agent-generated) message string object, in some MIB implemented by this host system. Conformance: XCMI conforming management agents SHALL support SNMP Get requests to the 'xcmGenMessageMapTable' (ie, agents must respond to valid explicit EXACT requests). When 'xcmGenMessageMapTable' is currently 'hidden' via 'xcmGenBaseGroupWalkHidden', XCMI conforming management agents SHALL skip over 'xcmGenMessageMapTable' to the next lexicographically higher object for GetNext or GetBulk requests - 'xcmGenMessageMapTable' SHOULD be invisible to MIB walks, to avoid undesirable performance degradation with third-party network management stations and other monitoring tools.

This object is used to specify the fully qualified object identifer (w/ instance suffix) of a message string object, which contains a Xerox registered standard or experimental message string value associated with the current message string label specified in 'xcmGenMessageMapStringLabel'.

This object is used to specify a Xerox standard or experiemental message string label associated with the current value of the message string pointed to by 'xcmGenMessageMapStringIndexOID'. Usage: Experimental message string labels SHOULD NOT be used in shipping versions of Xerox-branded products or services. They exist solely to facilitate rapid product development cycles. Usage: All Xerox message string label values SHALL be specified using display (NOT space) characters from the IANA registered charset 'utf-8' (ie, the UTF-8 octet-stream encoding of ISO-10646 UCS-4, described in RFC 2279). Usage: All Xerox message string label values SHALL contain no more than 64 UTF-8 display characters AND no more than 128 total octets (in some scripts, less than 64 characters in UTF-8 octet-stream encoding). Note: New or refined message label syntaxes MAY be defined in future versions of the XCMI General TC.

A table of message string translations for all target locales of static (agent-generated) message string objects, in various known (agent-supported) source message locales. Usage: Exposes the server's message catalog for indirect search via source message object OIDs, yielding target string values. Usage: Supports reliable translation by servers (agents) of static (agent-generated) message strings, INDEPENDENT of the current language/country/charset of the message strings on the managed host system in the conventional MIB objects. Conformance: XCMI conforming management agents SHALL support SNMP Get requests to the 'xcmGenMessageTextTable' (ie, agents must respond to valid explicit EXACT requests). When 'xcmGenMessageTextTable' is currently 'hidden' via 'xcmGenBaseGroupWalkHidden', XCMI conforming management agents SHALL skip over 'xcmGenMessageTextTable' to the next lexicographically higher object for GetNext or GetBulk requests - 'xcmGenMessageTextTable' SHOULD be invisible to MIB walks, to avoid undesirable performance degradation with third-party network management stations and other monitoring tools.

An entry for a message string translation for one target locale of a static (agent-generated) message string object, in some MIB implemented by this host system. Conformance: XCMI conforming management agents SHALL support SNMP Get requests to the 'xcmGenMessageTextTable' (ie, agents must respond to valid explicit EXACT requests). When 'xcmGenMessageTextTable' is currently 'hidden' via 'xcmGenBaseGroupWalkHidden', XCMI conforming management agents SHALL skip over 'xcmGenMessageTextTable' to the next lexicographically higher object for GetNext or GetBulk requests - 'xcmGenMessageTextTable' SHOULD be invisible to MIB walks, to avoid undesirable performance degradation with third-party network management stations and other monitoring tools.

This object is used to specify the fully qualified object identifer (w/ instance suffix) of a message string object, which contains a Xerox registered standard or experimental message string value equivalent to the target message string translation specified in 'xcmGenMessageTextTargetString'. The locale of this source message string is immaterial.

This object is used to specify the locale (language/country), as a value of 'xcmGenLocalizationIndex', of the message string translation in 'xcmGenMessageTextTargetString'.

This object is used to specify a translated Xerox registered message string value associated with the current value of the message string pointed to by 'xcmGenMessageMapStringIndexOID', in the locale specified by 'xcmGenMessageTextTargetLocale'. Usage: All Xerox registered message string values SHALL contain no more than 128 UTF-8 display characters AND no more than 255 total octets (in some scripts, less than 128 characters in UTF-8 octet-stream encoding).

This subtree is current. Subordinate objects are leaf objects.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenNotifyRuleTable'.

The maximum number of simultaneous entries (rows) supported for the 'xcmGenNotifyRuleTable'. Usage: The value zero ('0') represents 'no limit'.

A table of notification rules (recipient/event lists) registered for event delivery from this host system. Note: In this MIB, the term 'notification rule' is equivalent to the term 'Subscription object' in IPP Notifications. Usage: Conforming management agents SHALL NOT accept sets to any other columnar object in 'xcmGenNotifyRuleTable' when 'xcmGenNotifyRuleRowStatus' is 'active'. Dynamic rows must be deleted (with 'destroy') and then recreated (with 'createAndGo') with new columnar values. Static rows must be released (with 'notInService') and then then reallocated (with 'active') with new columnar values. Thus only a row status transition to 'active' indicates a new notification registration by a conforming management station. Usage: Conforming management agents SHALL delete any rows in the 'xcmGenNotifyDetailTable' which were subordinate to a deleted row in the 'xcmGenNotifyRuleTable'.

An entry for a notification rule (recipient/event list) registered for event delivery from this host system.

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

This object is used to display the status of this conceptual row in the 'xcmGenNotifyRuleTable'. Usage: This object MAY be used to create ('createAndGo') and delete ('destroy') dynamic rows in the 'xcmGenNotifyRuleTable'. Also used to enable ('active') and disable ('notInService') static rows in the 'xcmGenNotifyRuleTable'. Usage: Conforming management agents SHOULD NOT support the intermediate values 'notReady(3)' or 'createAndWait(5)'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

This object is used to specify the persistence of this conceptual row in the 'xcmGenNotifyRuleTable' (and associated conceptual rows in the 'xcmGenNotifyRuleDetailTable'). Usage: Dynamically created rows SHALL be given 'volatile' or 'nonvolatile' persistence. Usage: Conforming management agents SHALL NOT accept sets to 'xcmGenNotifyRuleRowPersistence' AFTER row creation (this object is 'write-once'). Usage: Conforming management agents SHALL support 'volatile' (lost across power cycles), but NEED NOT support any other levels of persistence.

This object is used to specify a single recipient URI (Uniform Resource Identifier, per Generic URI Syntax, RFC 2396) for event delivery for this notification rule (list of events), eg, - 'mailto:joe@sample.com' (Email) - 'mailto:VOICE=+3940226338@samplevoice.com' (Voice Mail) - 'mailto:FAX=+1.800.5553000/T33S=6377@sampleserv.com' (IFax) - 'ftp://machine.sample.com/pub/event_logs' (FTP logging) Usage: 'ftp:' and 'http:' URLs specify paths for event logs. Usage: MAY include parameters for SNMP and other URL schemes (eg, 'snmp://machine.sample.com;version=2c;community=public' for SNMPv2c delivery with community-name of 'public'). Usage: For additional recipients, use 'notifyRecipientURI' notify details in the 'xcmGenNotifyRuleDetailTable'.

This object is used to specify the subscribed events for this notification rule, as a comma-delimited list of (standard) keywords or (vendor or site-specific) names. Usage: Keywords of IPP 'notify-events' and SNMP traps and and SNMP state/alert enumeration keywords are interoperable (eg, 'lowPaper,jammed' from IETF HR MIB, RFC 2790). ` Usage: Standard keywords MAY be scoped with their source, eg, 'notify-events.job-stopped,hrPrinterDetectedErrorState.jammed', for clarity. Usage: Conforming management stations and management agents SHALL prefix non-standard names with 'x-' for compatibility.

This object is used to specify a delay timer in seconds for event delivery that rate-limits (buffers) frequent events. This timer is the minimum number of seconds between events delivered for this notification rule ('xcmGenNotifyRuleIndex'). Usage: Conforming management agents (network devices) SHOULD support server-side buffering of events for interoperability (and improved performance) via 'xcmGenNotifyRuleEventDelay'. Usage: Conforming management stations (recipients) SHOULD support client-side buffering of events for interoperability (and not depend on this 'xcmGenNotifyRuleEventDelay' object).

This object is used to specify the notification severity filter used to 'screen' notifications for event delivery. Usage: Notification details MAY further constrain which notifications are 'in scope'.

This object is used to specify the notification training filter used to 'screen' notifications for event delivery. Usage: Notification details MAY further constrain which notifications are 'in scope'.

This object is used to specify the notification charset used for notification text in event messages, specified as an IANA registered charset identifier, eg, 'MIBenum' value (per RFC 2978). Usage: If 'xcmGenNotifyRuleCharset' is 'other(1)', then the value of 'xcmGenFixedLocalizationIndex' SHALL be used for a notification rule locale specifier for charset.

This object is used to specify the notification natural language used for notification text in event messages, specified as an IETF 'language tag' (per RFC 3066). Usage: If 'xcmGenNotifyRuleNaturalLanguage' is empty, then the value of 'xcmGenFixedLocalizationIndex' SHALL be used for a notification rule locale specifier for natural language.

This object is used to specify the notification sequence number last used for event delivery for this notification rule. Usage: Conforming management agents SHOULD include the value of 'xcmGenNotifyRuleSequenceNumber' in all event messages.

This subtree is current. Subordinate objects are leaf objects.

The count of entries (rows) which are currently in the 'active' state in 'xcmGenNotifyDetailTable'.

The maximum number of simultaneous entries (rows) supported for the 'xcmGenNotifyDetailTable'. Usage: The value zero ('0') represents 'no limit'.

A 'sparse' table of notification detail information for notification rules configured on this host system, augmenting the basic entries in the 'xcmGenNotifyTable'. Usage: UNLIKE the 'xcmGenOptionTable' in the XCMI General MIB (which is a unique exception), this table of 'dictionary-based' notify details is used with DIRECT create/update operations.

An entry of notification detail information for one of the notification rules configured on this host system, augmenting the basic entry in the 'xcmGenNotifyTable'.

The type of notify detail stored in this conceptual row in 'xcmGenNotifyDetailTable'. Usage: Conforming XCMI management stations and agents SHALL encode notify details as UTF-8 strings (like SLPv2, RFC 2608). - Integers SHALL be encoded as (signed) decimal strings. - Booleans SHALL be encoded as 'true' or 'false' strings. - Strings SHALL be encoded as UTF-8 character strings. - Binary data (e.g., 'userCertificate') SHALL be stored in SLPv2 opaque encoding (leading '\FF' and escaped octets). Usage: Conformant implementations MUST encrypt passwords, keys, and other security information in 'xcmGenNotifyDetailString'.

A unique value used by this host system to identify this conceptual row in the 'xcmGenNotifyDetailTable', OR a common value shared across a set of related conceptual rows (with different values of 'xcmGenNotifyDetailType'.

This object is used to display the status of this conceptual row in the 'xcmGenNotifyDetailTable'. Usage: This object MAY be used to create ('createAndGo') and delete ('destroy') dynamic rows in 'xcmGenNotifyDetailTable'. Also used to enable ('active') and disable ('notInService') static rows in the 'xcmGenNotifyTable'. Usage: Conforming management agents SHOULD NOT support the intermediate values 'notReady(3)' or 'createAndWait(5)'. Usage: See section 3.4 'Secure Modes of Operation' and section 3.5 'Secure SNMP Get/Set Requests' in XCMI Security TC, for details of secure modes of access to this row status object.

The string notify detail value stored in this conceptual row in 'xcmGenNotifyDetailTable'. Usage: Conforming XCMI management stations and agents SHALL encode notify details as UTF-8 strings (like SLPv2, RFC 2608). - Integers SHALL be encoded as (signed) decimal strings. - Booleans SHALL be encoded as 'true' or 'false' strings. - Strings SHALL be encoded as UTF-8 character strings. - Binary data (e.g., 'userCertificate') SHALL be stored in SLPv2 opaque encoding (leading '\FF' and escaped octets). Usage: Conformant implementations MUST encrypt passwords, keys, and other security information in 'xcmGenNotifyDetailString'.