XEROX-SERVICE-MONITORING-MIB
AI MIB Summary
The XEROX-SERVICE-MONITORING-MIB enables SNMP-based configuration and active monitoring of application service states, availability, and operational parameters on network-accessible Xerox host systems. This module facilitates the tracking of service instance health and resource utilization by leveraging standards defined in IETF RFC 1565 and RFC 2790 to align with the OSI Systems Management framework.
Version: 5.502.pub
The MIB module for basic configuration and active management of application services for network accessible host systems.
See: IETF Network Services Monitoring MIB
(IETF RFC 1565, January 1994).
See: IETF Host Resources MIB
(IETF RFC 2790, March 2000).
See: OSI Reference Model - Part 1: Basic Reference Model
(CCITT X.200:1992 | ISO 7498-1:1992).
See: OSI Reference Model - Part 4: Systems Management
(CCITT X.700:1992 | ISO 7498-4:1992).
Copyright (C) 1996-2006 Xerox Corporation. All Rights Reserved.
Main OID:
xcmSvcMonMIB.1.3.6.1.4.1.253.8.74
87
Objects
Active
Status
9
Dependencies
Imported Objects
Objects
87 total| Object Name |
|---|
xcmSvcMonMIBVersion: 5.502.pub
The MIB module for basic configuration and active management
of application services for network accessible host systems.
See: IETF Network Services Monitoring MIB
(IETF RFC 1565, January 1994).
See: IETF Host Resources MIB
(IETF RFC 2790, March 2000).
See: OSI Reference Model - Part 1: Basic Reference Model
(CCITT X.200:1992 | ISO 7498-1:1992).
See: OSI Reference Model - Part 4: Systems Management
(CCITT X.700:1992 | ISO 7498-4:1992).
Copyright (C) 1996-2006 Xerox Corporation. All Rights Reserved. MODULE-IDENTITY .1.3.6.1.4.1.253.8.74 |
xcmSvcMonGeneral OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.1 |
xcmSvcMonGeneralTableA table of general counters and capabilities for ease of use
of the XCMI Service Monitoring MIB on this host system.
Usage: The ONLY valid row in the 'xcmSvcMonGeneralTable'
SHALL have an 'xcmSvcMonGeneralIndex' of one ('1'). SEQUENCE OF XcmSvcMonGeneralEntry .1.3.6.1.4.1.253.8.74.1.2 |
xcmSvcMonGeneralEntryAn entry of general counters and capabilities for ease of use
of the XCMI Service Monitoring MIB on this host system.
Usage: The ONLY valid row in the 'xcmSvcMonGeneralTable'
SHALL have an 'xcmSvcMonGeneralIndex' of one ('1'). XcmSvcMonGeneralEntry .1.3.6.1.4.1.253.8.74.1.2.1 |
xcmSvcMonGeneralIndexA unique value used by this host system to identify this
conceptual row in the 'xcmSvcMonGeneralTable'.
Usage: The ONLY valid row in the 'xcmSvcMonGeneralTable'
SHALL have an 'xcmSvcMonGeneralIndex' of one ('1').
Usage: 'xcmSvcMonGeneralRowStatus' is 'read-only' because
the ONLY valid conceptual row SHALL NOT be deleted. Ordinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.1.2.1.1 |
xcmSvcMonGeneralRowStatusThis object is used to display status of the ONLY valid
conceptual row in the 'xcmSvcMonGeneralTable'.
Usage: 'xcmSvcMonGeneralRowStatus' is 'read-only' because
the ONLY valid conceptual row SHALL NOT be deleted.ro RowStatus (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.1.2.1.2 |
xcmSvcMonGeneralVersionIDThe software product ID of the SNMP sub-agent which implements
the XCMI Service Monitoring 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
Service Monitoring 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).ro ProductID (HOST-RESOURCES-MIB) .1.3.6.1.4.1.253.8.74.1.2.1.3 |
xcmSvcMonGeneralVersionDateThe software build date of the SNMP sub-agent which implements
the XCMI Service Monitoring 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.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.1.2.1.4 |
xcmSvcMonGeneralGroupSupportThe terse conformance statement of ALL mandatory, conditionally
mandatory, and optional XCMI Service Monitoring MIB 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 Service Monitoring MIB groups.ro XcmSvcMonGroupSupport (XEROX-SERVICE-MONITORING-TC) .1.3.6.1.4.1.253.8.74.1.2.1.5 |
xcmSvcMonGeneralCreateSupportThe terse conformance statement of ALL mandatory, conditionally
mandatory, and optional XCMI Service Monitoring MIB 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 Service Monitoring MIB groups.ro XcmSvcMonGroupSupport (XEROX-SERVICE-MONITORING-TC) .1.3.6.1.4.1.253.8.74.1.2.1.6 |
xcmSvcMonGeneralUpdateSupportThe terse conformance statement of ALL mandatory, conditionally
mandatory, and optional XCMI Service Monitoring MIB 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 Service Monitoring MIB groups.ro XcmSvcMonGroupSupport (XEROX-SERVICE-MONITORING-TC) .1.3.6.1.4.1.253.8.74.1.2.1.7 |
xcmSvcMonMIBConformance OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.2 |
xcmSvcMonMIBGroups OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.2.2 |
xcmSvcMonQueue OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.3 |
xcmSvcMonQueueTableA table of the external job queues supported and (possibly)
active, for some 'physical', 'logical', or 'logicalAndPhysical'
device on this host system.
Usage: These externally visible job queues MAY actually be
configured on external print/file servers (remote) or on the
managed system itself (local).
Usage: For example, a 'logical printer' might support one or
more external (network) job queues.
Note: The 'xcmJobGenBasicTable' in the XCMI Job Monitoring MIB
(indexed by 'hrDeviceIndex' from the IETF Host Resources MIB)
displays the unordered union of all jobs present in the (one or
more) 'local' queues supported by each 'physical', 'logical', or
'logicalAndPhysical' device on this host system.
Note: The XCMI Comms Engine MIB is indexed by devices of type
'CPU', while the 'xcmSvcMonQueueTable' is indexed by application
devices of type 'printer', 'fax', etc.
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
queue table objects across management agent power cycles,
and SHALL implement one of the following two methods:
1) The agent SHALL store queue table objects directly in
'stable storage'; or
2) The agent SHALL automatically checkpoint all active queue
table objects to 'stable storage' with reasonable frequency
(either due to a write to some queue table 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 'xcmSvcMonQueueRowStatus' 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)';
<or>
2b) An agent which supports 'delayed checkpoint',
changes 'xcmSvcMonQueueRowStatus' to 'notInService(2)',
sends a 'SetResponse' with 'noError(0)',
completes the checkpoint to 'stable storage', and
changes 'xcmSvcMonQueueRowStatus' back to 'active(1)'. SEQUENCE OF XcmSvcMonQueueEntry .1.3.6.1.4.1.253.8.74.3.2 |
xcmSvcMonQueueEntryAn entry for an external job queue supported and (possibly)
active, for some 'physical', 'logical', or 'logicalAndPhysical'
device on this host system.
Usage: This externally visible job queue MAY actually be
configured on an external print/file server (remote) or on the
managed system itself (local). XcmSvcMonQueueEntry .1.3.6.1.4.1.253.8.74.3.2.1 |
xcmSvcMonQueueIndexA unique value used by this host system to identify this
conceptual row in the 'xcmSvcMonQueueTable'.
Usage: This object SHALL be permanent (ie, preserved
across all hardware resets).ro Ordinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.3.2.1.1 |
xcmSvcMonQueueRowStatusThis object is used to create and delete individual conceptual
rows in the 'xcmSvcMonQueueTable' and (optionally) in the
'xcmSvcMonQueueExtTable' (if implementated on this system).
Usage: Conforming implementations which support static rows
SHALL support 'active' and 'notInService' writes to this
'xcmSvcMonQueueRowStatus' row status object; and
SHALL clear the 'svcMonQueueGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the 'xcmSvcMonGeneralTable'.
Usage: Conforming implementations which support dynamic rows
SHALL support 'createAndGo' and 'destroy' writes to this
'xcmSvcMonQueueRowStatus' row status object; and
SHALL set the 'svcMonQueueGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the 'xcmSvcMonGeneralTable'.
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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.3.2.1.2 |
xcmSvcMonQueueDomainThe queue namespace domain (directory protocol) for the queue
path and queue name (eg, 'internetDNS', 'netwareNDS').
Usage: This queue namespace domain SHALL be a valid
directory protocol enumeration from 'XcmCommsStackExtProtocol'
in the XCMI Comms Engine TC.
Usage: When a remote management station (client) creates a row
in 'xcmSvcMonQueueTable' (via 'xcmSvcMonQueueRowStatus'),
this queue namespace domain SHALL be specified.
Note: For implementation efficiency, this object uses the
integer 'XcmCommStackExtProtocol' values (from the XCMI Comms
Engine MIB) rather than the equivalent 'XcmCO...' OID values
(from the XCMI Comms Config MIB).rw XcmCommsStackExtProtocol (XEROX-COMMS-ENGINE-TC) .1.3.6.1.4.1.253.8.74.3.2.1.3 |
xcmSvcMonQueuePathHuman-readable queue path, used by system administrators
and end-users to specify the 'full network path' of a file
server (eg, Novell Bindery) or directory tree (eg, Novell NDS)
which, when prefixed to the following 'xcmSvcMonQueueName'
object, specifies a 'full network queue name' of this queue.
Usage: This queue path SHOULD be the one normally used in a
command shell for control of this queue.
Usage: When a remote management station (client) creates a row
in 'xcmSvcMonQueueTable' (via 'xcmSvcMonQueueRowStatus'),
this queue path SHALL be specified.rw XcmFixedLocaleDisplayString .1.3.6.1.4.1.253.8.74.3.2.1.4 |
xcmSvcMonQueueNameHuman-readable queue name, used by system administrators
and end-users to specify the 'simple name' of this queue (or in
the Novell NDS case, the context and simple name concatenated),
which, when suffixed to the preceding 'xcmSvcMonQueuePath'
object, specifies a 'full network queue name' of this queue.
Usage: This queue name SHOULD be the one normally used in a
command shell for control of this queue.
Usage: When a remote management station (client) creates a row
in 'xcmSvcMonQueueTable' (via 'xcmSvcMonQueueRowStatus'),
this queue name SHALL be specified.rw XcmFixedLocaleDisplayString .1.3.6.1.4.1.253.8.74.3.2.1.5 |
xcmSvcMonQueueOnSystemSpecifies whether this queue is present on this host system
(local) or is on another network system (remote).rw TruthValue (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.3.2.1.6 |
xcmSvcMonQueueExt OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.4 |
xcmSvcMonQueueExtV1EventOIDThe value of the enterprise-specific OID in an SNMPv1 trap sent
whenever 'xcmSvcMonQueue[State|Conditions|FaultCount]' changes.
See SNMPv2 trap definition 'xcmSvcMonQueueExtV2Event'
below for 'special semantics'. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.4.1 |
xcmSvcMonQueueExtV2EventPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.4.1.0 |
xcmSvcMonQueueExtV2EventThis is the definition of the SNMPv2 trap sent whenever
'xcmSvcMonQueue[State|Conditions|FaultCount]' changes.
Note: The variable-bindings of this trap have been chosen to
specify a complete associated queue status change while keeping
trap messages reasonably concise (generally a few hundred octets
at most).
This notification has the following special semantics:
o The queue's 'xcmSvcMonQueueIndex' field
value SHALL be appended to this trap object ID,
as a BER binary OID suffix.
This trap OID qualifier allows service management/monitoring
applications to limit the alerts they receive to ones generated
by associated queues of interest. NOTIFICATION-TYPE .1.3.6.1.4.1.253.8.74.4.1.0.1 |
xcmSvcMonQueueExtTableA table which augments 'xcmSvcMonQueueTable', with dynamic
queue routing (forwarding), state, conditions, fault info,
create date, lifetime jobs, and last connect date and jobs.
Usage: Conforming implementations SHALL preserve active
queue table objects across management agent power cycles,
and SHALL implement one of the following two methods:
1) The agent SHALL store queue table objects directly in
'stable storage'; or
2) The agent SHALL automatically checkpoint all active queue
table objects to 'stable storage' with reasonable frequency
(either due to a write to some queue table object, or upon
expiration of a product-specific timeout). SEQUENCE OF XcmSvcMonQueueExtEntry .1.3.6.1.4.1.253.8.74.4.2 |
xcmSvcMonQueueExtEntryAn entry which augments 'xcmSvcMonQueueTable', with dynamic
queue routing (forwarding), state, conditions, and fault info. XcmSvcMonQueueExtEntry .1.3.6.1.4.1.253.8.74.4.2.1 |
xcmSvcMonQueueRoutingIndexThe (optional) routing index of this queue.
Usage: This (optional) routing index, for queue indirection
mapping, specifies 'xcmSvcMonQueueIndex' for the NEXT queue
closer to (or on) this host system, or zero if none.
Usage: It is common for more than one off-system (remote) queue
to be forwarded to the same on-system (local) queue. Multiple
off-system (remote) entries in the 'xcmSvcMonQueueTable' (for a
given device) MAY forward to the same on-system (local) entry.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.4.2.1.1 |
xcmSvcMonQueueStateThe current state of this queue.
Usage: This queue state specifies the operational state
of the application service or the network communications path
to this queue.
Usage: This queue state need NOT be reported for a
'remote' queue (ie, 'xcmSvcMonQueueOnSystem' is 'false'),
although in some cases (eg, Novell PServer), the state of
(connectivity to) the 'remote' queue is known (and SHALL
be reported) on the managed system.
Usage: This queue state SHALL be as reported in
the XCMI Comms Config/Engine MIB objects for this queue.ro XcmCommsMgmtState (XEROX-COMMS-ENGINE-TC) .1.3.6.1.4.1.253.8.74.4.2.1.2 |
xcmSvcMonQueueConditionsThe current conditions (ie, state reasons) of this queue.
Usage: These queue conditions qualify the operational state
of the application service or the network communications path
to this queue.
Usage: These queue conditions need NOT be reported for a
'remote' queue (ie, 'xcmSvcMonQueueOnSystem' is 'false'),
although in some cases (eg, Novell PServer), the state of
(connectivity to) the 'remote' queue is known (and SHALL
be reported) on the managed system.
Usage: These queue conditions SHALL be as reported in
the XCMI Comms Config/Engine MIB objects for this queue.ro XcmCommsMgmtConditions (XEROX-COMMS-ENGINE-TC) .1.3.6.1.4.1.253.8.74.4.2.1.3 |
xcmSvcMonQueueFaultCountThe current fault count of this queue.
Usage: This queue fault count qualifies the operational state
of the application service or the network communications path
to this queue.
Usage: This queue fault count need NOT be reported for a
'remote' queue (ie, 'xcmSvcMonQueueOnSystem' is 'false'),
although in some cases (eg, Novell PServer), the state of
(connectivity to) the 'remote' queue is known (and SHALL
be reported) on the managed system.
Usage: This queue fault count SHALL be as reported in
any relevant device- or service-specific MIB for this queue.
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.ro Counter32 .1.3.6.1.4.1.253.8.74.4.2.1.4 |
xcmSvcMonQueueFaultCodeEncoded current fault code of this queue.
Usage: This queue fault code qualifies the operational state
of the application service or the network communications path
to this queue.
Usage: This queue fault code need NOT be reported for a
'remote' queue (ie, 'xcmSvcMonQueueOnSystem' is 'false'),
although in some cases (eg, Novell PServer), the state of
(connectivity to) the 'remote' queue is known (and SHALL
be reported) on the managed system.
Usage: This queue fault code SHALL be as reported in
any relevant device- or service-specific MIB for this queue.ro Integer32 .1.3.6.1.4.1.253.8.74.4.2.1.5 |
xcmSvcMonQueueFaultStringHuman-readable current fault string of this queue.
Usage: This queue fault string qualifies the operational state
of the application service or the network communications path
to this queue.
Usage: This queue fault string need NOT be reported for a
'remote' queue (ie, 'xcmSvcMonQueueOnSystem' is 'false'),
although in some cases (eg, Novell PServer), the state of
(connectivity to) the 'remote' queue is known (and SHALL
be reported) on the managed system.
Usage: This queue fault string SHALL be as reported in
any relevant device- or service-specific MIB for this queue.ro XcmFixedLocaleDisplayString .1.3.6.1.4.1.253.8.74.4.2.1.6 |
xcmSvcMonQueueRowCreateDateThe date and time of creation of this conceptual row in the
'xcmSvcMonQueueTable' (and 'xcmSvcMonQueueExtTable').ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.4.2.1.7 |
xcmSvcMonQueueRowTotalJobsThe total jobs completed for this remote/local external
job queue, since 'xcmSvcMonQueueRowCreateDate'.
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.ro Counter32 .1.3.6.1.4.1.253.8.74.4.2.1.8 |
xcmSvcMonQueueLastConnectDateThe date and time of last connect (and/or login) to this remote
or local external job queue.ro DateAndTime (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.4.2.1.9 |
xcmSvcMonQueueLastConnectJobsThe total jobs completed for this remote/local external
job queue, since 'xcmSvcMonQueueLastConnectDate'.
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.ro Counter32 .1.3.6.1.4.1.253.8.74.4.2.1.10 |
xcmSvcMonService OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.5 |
xcmSvcMonServiceV1EventOIDThe value of the enterprise-specific OID in an SNMPv1 trap sent
whenever a service status changes.
See SNMPv2 trap definition 'xcmSvcMonServiceV2Event'
below for 'special semantics'. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.5.1 |
xcmSvcMonServiceV2EventPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.5.1.0 |
xcmSvcMonServiceV2EventThis trap is sent whenever
'XcmSvcMonService[CurrentState|Conditions]' changes.
Note: The variable-bindings of this trap have been chosen to
specify a complete service status change while keeping
trap messages reasonably concise (generally a few hundred octets
at most).
This notification has the following special semantics:
o The service's 'xcmSvcMonServiceIndex' field
value SHALL be appended to this trap object ID,
as a BER binary OID suffix.
This trap OID qualifier allows service management/monitoring
applications to limit the alerts they receive to ones generated
by services of interest. NOTIFICATION-TYPE .1.3.6.1.4.1.253.8.74.5.1.0.1 |
xcmSvcMonServiceTableA table of the system and/or end-user services supported and
(possibly) ready on this host system, and (possibly) associated
with one or more 'physical', 'logical', or 'logicalAndPhysical'
devices on this host system presenting job services and one or
more external devices (for security, accounting, etc), attached
to this host system. SEQUENCE OF XcmSvcMonServiceEntry .1.3.6.1.4.1.253.8.74.5.2 |
xcmSvcMonServiceEntryAn entry for a system and/or end-user service supported and
(possibly) ready on this host system, and (possibly) associated
with one or more 'physical', 'logical', or 'logicalAndPhysical'
devices on this host system presenting job services and one or
more external devices (for security, accounting, etc), attached
to this host system. XcmSvcMonServiceEntry .1.3.6.1.4.1.253.8.74.5.2.1 |
xcmSvcMonServiceIndexA unique value used by this host system to identify this
conceptual row in the 'xcmSvcMonServiceTable'.
Usage: Conforming management stations and management agents
SHALL ensure that 'xcmSvcMonServiceIndex' is equal to
'xcmSecServiceIndex' for the same service (if the XCMI Security
MIB is also implemented).
Usage: This object SHALL be permanent (ie, preserved
across all hardware resets).ro Ordinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.5.2.1.1 |
xcmSvcMonServiceRowStatusThis object is used to create and delete individual conceptual
rows in the 'xcmSvcMonServiceTable' and (optionally) in the
'xcmSvcMonServiceMgmtTable' (if implemented on this system).
Usage: Conforming management stations and management agents
SHALL ensure that 'xcmSvcMonServiceIndex' is equal to
'xcmSecServiceIndex' for the same service (if the XCMI Security
MIB is also implemented).
Usage: Conforming implementations which support static rows
SHALL support 'active' and 'notInService' writes to this
'xcmSvcMonServiceRowStatus' row status object; and
SHALL clear the 'svcMonServiceGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the 'xcmSvcMonGeneralTable'.
Usage: Conforming implementations which support dynamic rows
SHALL support 'createAndGo' and 'destroy' writes to this
'xcmSvcMonServiceRowStatus' row status object; and
SHALL set the 'svcMonServiceGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the 'xcmSvcMonGeneralTable'.
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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.5.2.1.2 |
xcmSvcMonServiceNameA human-readable name, used by system administrators
and end-users to identify this service.
Usage: This name SHALL be either:
a) the name normally used in a command shell for control of
this service (eg, 'showstopper.sample.com/bin/scan2file'); or
b) the local user-friendly service name (eg, 'ScanToFile').
Usage: Conforming implementations need NOT ensure that each
'xcmSvcMonServiceEntry' has a non-empty (on the managed system)
'xcmSvcMonServiceName' (ie, names support is optional), but
a given 'xcmSvcMonServiceName' SHALL be found via the
same value of 'xcmSecServiceIndex' on the same managed system
(ie, service names SHALL be persistent).rw XcmFixedLocaleDisplayString .1.3.6.1.4.1.253.8.74.5.2.1.3 |
xcmSvcMonServiceCurrentStateThe current state of this system and/or end-user service.
Usage: The current DPA object generic state of a service.ro XcmHrDpaState (XEROX-HOST-RESOURCES-EXT-TC) .1.3.6.1.4.1.253.8.74.5.2.1.4 |
xcmSvcMonServicePreviousStateThe previous state of this system and/or end-user service.
Usage: The previous DPA object generic state of a service.ro XcmHrDpaState (XEROX-HOST-RESOURCES-EXT-TC) .1.3.6.1.4.1.253.8.74.5.2.1.5 |
xcmSvcMonServiceConditionsThe current conditions (ie, state reasons) of this system
and/or end-user service.ro XcmHrDpaConditions (XEROX-HOST-RESOURCES-EXT-TC) .1.3.6.1.4.1.253.8.74.5.2.1.6 |
xcmSvcMonServiceAvailabilityThe availability of this system and/or end-user service.ro XcmHrDpaAvailability (XEROX-HOST-RESOURCES-EXT-TC) .1.3.6.1.4.1.253.8.74.5.2.1.7 |
xcmSvcMonServicePhysicalDeviceThe value of 'hrDeviceIndex' corresponding to the first
associated physical device row in the 'hrDeviceTable' in the
Host Resources MIB (RFC 2790) and an (optional) associated row
in 'xcmHrDevInfoTable' of the XCMI Ext to Host Resources MIB,
or zero if none.
Usage: Conforming implementations SHALL ensure that
physical devices underlying services are 'visible'.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.5.2.1.8 |
xcmSvcMonServiceLogicalDeviceThe value of 'hrDeviceIndex' corresponding to the first
associated logical device row in the 'hrDeviceTable' in the
Host Resources MIB (RFC 2790) and an (optional) associated row
in 'xcmHrDevInfoTable' of the XCMI Ext to Host Resources MIB,
or zero if none.
Usage: Conforming implementations SHALL ensure that
logical devices presenting services are 'visible'.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.5.2.1.9 |
xcmSvcMonServiceExternalDeviceThe value of 'hrDeviceIndex' corresponding to the first
associated external device row in the 'hrDeviceTable' in the
Host Resources MIB (RFC 2790) and an (optional) associated row
in 'xcmHrDevInfoTable' of the XCMI Ext to Host Resources MIB,
or zero if none.
Usage: Such an external device is termed a 'foreign attachment'
and SHALL have 'xcmHrDevInfoRealization' of 'physical' in the
Device Info group of the XCMI Ext to Host Resources MIB - such
a device performs some security processing (any authentication,
authorization, or accounting), job processing, job finishing, or
other off-system activity, on behalf of this service.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.5.2.1.10 |
xcmSvcMonServiceSWRunThe value of 'hrSWRunIndex' corresponding to the first
associated conceptual row in the 'hrSWRunTable' of the
Host Resources MIB (RFC 2790) and an (optional) associated row
in 'xcmHrSWRunTable' of the XCMI Ext to Host Resources MIB,
or zero if none.
Usage: A 'chain' of one or more Software Running entries in
the Host Resources MIB MAY be associated with this service.
By convention, the FIRST of these entries SHALL represent
the security functional unit of this service.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.5.2.1.11 |
xcmSvcMonServiceSWInstalledThe value of 'hrSWInstalledIndex' corresponding to the first
associated conceptual row in the 'hrSWInstalledTable' of the
Host Resources MIB (RFC 2790) and an (optional) associated row
in 'xcmHrSWInstalledTable' in XCMI Ext to Host Resources MIB,
or zero if none.
Usage: A 'chain' of one or more Software Installed entries in
the Host Resources MIB MAY be associated with a service.
By convention, the FIRST of these entries SHALL represent
the security functional unit of a service.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.5.2.1.12 |
xcmSvcMonServiceStorageThe value of 'hrStorageIndex' corresponding to the first
associated conceptual row in the 'hrStorageTable' of the
Host Resources MIB (RFC 2790) and an (optional) associated row
in 'xcmHrStorageTable' of the XCMI Ext to Host Resources MIB,
or zero if none.
Usage: A 'chain' of one or more Storage entries in
the Host Resources MIB MAY be associated with a service.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.5.2.1.13 |
xcmSvcMonServicePriorityThe current priority of this system and/or end-user service.
Usage: The scheduling priority of this service, where '0'
is unspecified (default), '1' is lowest, and '100' is highest.rw INTEGER .1.3.6.1.4.1.253.8.74.5.2.1.14 |
xcmSvcMonServiceTypeThe explicit type of this system and/or end-user service.rw XcmSvcMonServiceType (XEROX-SERVICE-MONITORING-TC) .1.3.6.1.4.1.253.8.74.5.2.1.15 |
xcmSvcMonServiceStateDetailThis object represents additional status details to further
describe the current state of the service.
Usage: This bit-array is constructed from the set of
supported values from 'XcmSvcMonServiceStateDetail', used as
powers of 2 with big-endian rules - the high-order bit of the
first octet corresponds to a service state detail '0' (reserved)
- the low-order bit of the first octet corresponds to a
service state detail of '7'.
Similar to the BITS pseudotype defined in IETF SMIv2
(RFC 2578), which has the same bit ordering rules but
requires definitions for contiguous enumerated bits.ro OCTET STRING .1.3.6.1.4.1.253.8.74.5.2.1.16 |
xcmSvcMonServiceDetail OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.6 |
xcmSvcMonServiceDetailTableA 'sparse' table containing service detail information for
installed and (possibly) active services on this host system,
augmenting the basic entries in the 'xcmSvcMonServiceTable'
of the XCMI Service Monitoring MIB.
Usage: UNLIKE the 'xcmGenOptionTable' in the XCMI General MIB
(which is a unique exception), this table of 'dictionary-based'
service details is used with DIRECT create/update operations. SEQUENCE OF XcmSvcMonServiceDetailEntry .1.3.6.1.4.1.253.8.74.6.2 |
xcmSvcMonServiceDetailEntryA 'sparse' entry containing service detail information for
an installed and (possibly) active service on this host system,
augmenting a basic entry in the 'xcmSvcMonServiceTable'
of the XCMI Service Monitoring MIB. XcmSvcMonServiceDetailEntry .1.3.6.1.4.1.253.8.74.6.2.1 |
xcmSvcMonServiceDetailClassA service detail class,
used by system administrators and end users to specify
the correct class for this service detail. XcmSvcMonServiceDetailClass (XEROX-SERVICE-MONITORING-TC) .1.3.6.1.4.1.253.8.74.6.2.1.1 |
xcmSvcMonServiceDetailTypeA service detail type,
used by system administrators and end users to specify
the correct type for this service detail. XcmSvcMonServiceDetailType (XEROX-SERVICE-MONITORING-TC) .1.3.6.1.4.1.253.8.74.6.2.1.2 |
xcmSvcMonServiceDetailIndexA unique value used by this host system to identify this
conceptual row in the 'xcmSvcMonServiceDetailTable', OR a common
value shared across a set of related conceptual rows (with
different values of 'xcmSvcMonServiceDetailType'.
Usage: For service detail types which are single-valued, this
index SHALL be used to correlate related single-valued details.
Usage: For service detail types which are multi-valued, this
index SHALL be used to enumerate lists of multi-valued details. Ordinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.6.2.1.3 |
xcmSvcMonServiceDetailRowStatusThis object is used to create and delete individual conceptual
rows in the 'xcmSvcMonServiceDetailTable'.
Usage: Conforming implementations which support static rows
SHALL support 'active' and 'notInService' writes to this
'xcmSvcMonServiceDetailRowStatus' row status object; and
SHALL clear the 'svcMonServiceDetailGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the 'xcmSvcMonGeneralTable'.
Usage: Conforming implementations which support dynamic rows
SHALL support 'createAndGo' and 'destroy' writes to this
'xcmSvcMonServiceDetailRowStatus' row status object; and
SHALL set the 'svcMonServiceDetailGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the 'xcmSvcMonGeneralTable'.
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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.6.2.1.4 |
xcmSvcMonServiceDetailUnitClassThe value unit class of the detail information specified
in this conceptual row in the 'xcmSvcMonServiceDetailTable'.
Usage: Used to select a textual convention for specifying the
value unit of this service detail.
Usage: The 'xcmSvcMonServiceDetail[UnitClass|Class]' objects
are used to specify the value syntax AND the value unit of the
'xcmSvcMonServiceDetail[Integer|OID|String]' value objects.rw XcmHrDevDetailUnitClass (XEROX-HOST-RESOURCES-EXT-TC) .1.3.6.1.4.1.253.8.74.6.2.1.5 |
xcmSvcMonServiceDetailUnitThe value unit of the detail information specified
in this conceptual row in the 'xcmSvcMonServiceDetailTable'.
Usage: Used to select an enumerated choice from a textual
convention to specify the value unit of this service detail.
Usage: The 'xcmSvcMonServiceDetail[UnitClass|Class]' objects
are used to specify the value syntax AND the value unit of the
'xcmSvcMonServiceDetail[Integer|OID|String]' value objects.rw Cardinal32 (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.6.2.1.6 |
xcmSvcMonServiceDetailIntegerA service detail value integer,
used by system administrators and end users to specify
the current value for a service detail
with a base value syntax of 'INTEGER'.rw Integer32 .1.3.6.1.4.1.253.8.74.6.2.1.7 |
xcmSvcMonServiceDetailOIDA service detail value OID (object identifier),
used by system administrators and end users to specify
the current value for a service detail
with a base value syntax of 'OBJECT IDENTIFIER'.rw OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.6.2.1.8 |
xcmSvcMonServiceDetailStringA service detail value string,
used by system administrators and end users to specify
the current value for a service detail
with a base value syntax of 'OCTET STRING'.
Usage: This object is of type 'XcmFixedLocaleDisplayString'.
Usage: Conformant implementations MUST encrypt passwords, keys,
and other security information stored in this string object.rw XcmFixedLocaleDisplayString .1.3.6.1.4.1.253.8.74.6.2.1.9 |
xcmSvcMonServiceMgmt OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.7 |
xcmSvcMonServiceMgmtV1EventOIDThe value of the enterprise-specific OID in an SNMPv1 trap sent
whenever an 'xcmSvcMonServiceMgmtOperation' completes.
See SNMPv2 trap definition 'xcmSvcMonServiceMgmtV2Event'
below for 'special semantics'. OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.7.1 |
xcmSvcMonServiceMgmtV2EventPrefix OBJECT IDENTIFIER .1.3.6.1.4.1.253.8.74.7.1.0 |
xcmSvcMonServiceMgmtV2EventThis trap is sent whenever an 'XcmSvcMonServiceMgmtOperation'
completes, ie, when 'xcmSvcMonServiceMgmtStatus' becomes the
completed operation status and 'XcmSvcMonServiceMgmtInProgress'
goes from 'true' to 'false'.
Note: The variable-bindings of this trap have been chosen to
specify a complete management operation result while keeping
trap messages reasonably concise (generally a few hundred octets
at most).
This notification has the following special semantics:
o The service's 'xcmSvcMonServiceIndex' field
value SHALL be appended to this trap object ID,
as a BER binary OID suffix.
This trap OID qualifier allows service management/monitoring
applications to limit the alerts they receive to ones generated
by requests they have submitted. NOTIFICATION-TYPE .1.3.6.1.4.1.253.8.74.7.1.0.1 |
xcmSvcMonServiceMgmtTableA table containing service management requests for control
of system and/or end-user services on this host system. SEQUENCE OF XcmSvcMonServiceMgmtEntry .1.3.6.1.4.1.253.8.74.7.2 |
xcmSvcMonServiceMgmtEntryAn entry containing a service management request for control
of a system and/or end-user service on this host system. XcmSvcMonServiceMgmtEntry .1.3.6.1.4.1.253.8.74.7.2.1 |
xcmSvcMonServiceMgmtOperationThe most recent service management operation specified for
this conceptual row in the 'xcmSvcMonServiceMgmtTable'.
Usage: Conforming management agents SHALL 'reject' any
SNMP Set-Request to 'xcmSvcMonServiceMgmt[Operation|Data]'
while another management operation is already in progress
(ie, while 'xcmSvcMonServiceMgmtInProgress' is 'true'),
with 'badValue' (SNMPv1) or 'inconsistentValue' (SNMPv2/v3).
Usage: Conforming management stations SHALL set
'xcmSvcMonServiceMgmtOperation' (mgmt operation) and
'xcmSvcMonServiceMgmtData' (mgmt arguments)
SIMULTANEOUSLY (in the same SNMP Set-Request PDU).rw XcmSvcMonServiceMgmtOperation (XEROX-SERVICE-MONITORING-TC) .1.3.6.1.4.1.253.8.74.7.2.1.1 |
xcmSvcMonServiceMgmtDataThe most recent service management data specified for
this conceptual row in the 'xcmSvcMonServiceMgmtTable'.
Usage: Conforming management agents SHALL 'reject' any
SNMP Set-Request to 'xcmSvcMonServiceMgmt[Operation|Data]'
while another management operation is already in progress
(ie, while 'xcmSvcMonServiceMgmtInProgress' is 'true')
with 'badValue' (SNMPv1) or 'inconsistentValue' (SNMPv2/v3).
Usage: Conforming management stations SHALL set
'xcmSvcMonServiceMgmtOperation' (mgmt operation) and
'xcmSvcMonServiceMgmtData' (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.
Usage: Management strings will be formatted as specified
in the 'XcmHrDevMgmtCommandDataTag' textual convention. This
means that the 'TT=value:' string format will be used with all
management strings.
Usage: Strings that have been specified by XCMI are provided
in the 'XcmSvcMonServiceMgmtData'.rw XcmSvcMonServiceMgmtData .1.3.6.1.4.1.253.8.74.7.2.1.2 |
xcmSvcMonServiceMgmtStatusThe service management error status associated with
this conceptual row in 'xcmSvcMonServiceMgmtTable'.
Usage: Conforming management agents SHALL set this
object to the value returned in an SNMP Set-Response PDU when
a service management operation is 'accepted', ie, when
'xcmSvcMonServiceMgmtInProgress' goes from 'false' to 'true'.
Usage: Conforming management agents SHALL set this
object to the value of the completion status of the (possibly
deferred) service management operation, when
'xcmSvcMonServiceMgmtInProgress' goes from 'true' to 'false'.ro XcmGenSNMPv2ErrorStatus (XEROX-GENERAL-TC) .1.3.6.1.4.1.253.8.74.7.2.1.3 |
xcmSvcMonServiceMgmtInProgressThe service management in progress status associated with
this conceptual row in 'xcmSvcMonServiceMgmtTable'.
Usage: Conforming management agents SHALL 'reject' any
SNMP Set-Request to 'xcmSvcMonServiceMgmt[Operation|Data]'
while another management operation is already in progress
(ie, while 'xcmSvcMonServiceMgmtInProgress' is 'true'),
with 'badValue' (SNMPv1) or 'inconsistentValue' (SNMPv2/v3).ro TruthValue (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.7.2.1.4 |
xcmSvcMonServiceMgmtRowStatusThis object manages the row status of this conceptual row in
the 'xcmSvcMonServiceMgmtTable'.
Usage: Conforming implementations which support static rows
SHALL support 'active' and 'notInService' writes to this
'xcmSvcMonServiceMgmtRowStatus' row status object; and
SHALL clear the 'xcmSvcMonServiceMgmtGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the
'xcmSvcMonServiceGeneralTable'.
Usage: Conforming implementations which support dynamic rows
SHALL support 'createAndGo' and 'destroy' writes to this
'xcmSvcMonServiceMgmtRowStatus' row status object; and
SHALL set the 'xcmSvcMonServiceMgmtGroup' bit in
'xcmSvcMonGeneralCreateSupport' in the
'xcmSvcMonServiceGeneralTable'.
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.rw RowStatus (SNMPv2-TC) .1.3.6.1.4.1.253.8.74.7.2.1.5 |
xcmSvcMonServiceMgmtUserPasswordA protected end user password for this device.
Usage: Conformant implementations MUST encrypt passwords, keys,
and other security information stored in this string object.
Usage: When changing the [User|Operator|Admin] Password,
conformant implementations MUST encrypt the NEW password that is
submitted in 'xcmSvcMonServiceMgmtData'.
Usage: All XCMI conforming management agents: a) SHOULD always
return a zero length string in response to an SNMP GetRequest of
this object; b) SHALL NOT return the contents of this object in
cleartext (ie, unencrypted) in response to an SNMP GetRequest;
c) SHOULD support (ie, accept) an authenticated SNMP SetRequest
changing the system 'end user password' that is used in this
object.rw OCTET STRING .1.3.6.1.4.1.253.8.74.7.2.1.6 |
xcmSvcMonServiceMgmtOperatorPasswordA protected system operator password for this device.
Usage: Conformant implementations MUST encrypt passwords, keys,
and other security information stored in this string object.
Usage: When changing the [User|Operator|Admin] Password,
conformant implementations MUST encrypt the NEW password that is
submitted in 'xcmSvcMonServiceMgmtData'.
Usage: All XCMI conforming management agents: a) SHOULD always
return a zero length string in response to an SNMP GetRequest of
this object; b) SHALL NOT return the contents of this object in
cleartext (ie, unencrypted) in response to an SNMP GetRequest;
c) SHOULD support (ie, accept) an authenticated SNMP SetRequest
changing the system 'operator password' that is used in this
object.rw OCTET STRING .1.3.6.1.4.1.253.8.74.7.2.1.7 |
xcmSvcMonServiceMgmtAdminPasswordA protected system administrator password for this device.
Usage: Conformant implementations MUST encrypt passwords, keys,
and other security information stored in this string object.
Usage: When changing the [User|Operator|Admin] Password,
conformant implementations MUST encrypt the NEW password that is
submitted in 'xcmSvcMonServiceMgmtData'.
Usage: All XCMI conforming management agents: a) SHOULD always
return a zero length string in response to an SNMP GetRequest of
this object; b) SHALL NOT return the contents of this object in
cleartext (ie, unencrypted) in response to an SNMP GetRequest;
c) SHOULD support (ie, accept) an authenticated SNMP SetRequest
changing the system 'administrator password' that is used in
this object.rw OCTET STRING .1.3.6.1.4.1.253.8.74.7.2.1.8 |
xcmSvcMonZeroDummy OBJECT IDENTIFIER .zeroDotZero.74 |