All MIBs › XEROX-SERVICE-MONITORING-MIB
Organization: Xerox Corporation - XCMI Working Group
Last Updated: 2006-03-17
Category: Xerox Printer Management
Description: Monitors Xerox XCMI device services including print, copy, scan, and fax operational status.
Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.
What Is XEROX-SERVICE-MONITORING-MIB?
The XEROX-SERVICE-MONITORING-MIB is a Xerox Corporation proprietary MIB (part of XCMI) for monitoring the application-level services running on network-accessible Xerox devices, such as print, copy, scan, and fax. It exposes a general service table describing each supported service's version and capability information, along with a queue table tracking service-specific job or request queues. Its monitoring focus is on software/service status: it lets an operator determine whether the print, copy, scan, or fax service on a device is active and functioning, and inspect queue depth to detect a stuck or backed-up service (e.g., a fax queue that isn't draining) before it becomes a user-visible outage. It explicitly builds on the IETF Network Services Monitoring MIB (RFC 1565) and IETF Host Resources MIB (RFC 2790) conventions cited in its module description. It is deployed on Xerox network printers and multifunction devices offering multiple document services in enterprise environments, consistent with the XEROX-SERVICE-MONITORING-MIB MIB definition built on those RFC conventions.
IPNetwork Monitor allows you to monitor SNMP objects defined in XEROX-SERVICE-MONITORING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.
Supported Devices
- Xerox network printer
- Xerox multifunction device (MFD)
Monitoring Examples
An administrator polls xcmSvcMonGeneralTable/xcmSvcMonGeneralEntry to see each service's xcmSvcMonGeneralVersionID and confirm which document services (print, copy, scan, fax) are present and enabled on the device, then checks xcmSvcMonQueueTable/xcmSvcMonQueueEntry for the depth of each service's job queue. A fax or print queue whose xcmSvcMonQueueIndex count keeps growing without draining indicates that specific service has stalled even though the device overall reports as reachable.
What Can Be Monitored
- supported service list (print/copy/scan/fax)
- service version information
- job queue depth per service
- service enable/active status
This MIB depends on
Related MIBs
Imported Objects
From HOST-RESOURCES-MIB
| ProductID | |
| hrDeviceIndex | OBJECT-TYPE |
From SNMPv2-CONF
| MODULE-COMPLIANCE | |
| OBJECT-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-IDENTITY | |
| OBJECT-TYPE |
From SNMPv2-TC
| DateAndTime | |
| RowStatus | |
| TruthValue |
From XEROX-COMMON-MIB
| xeroxCommonMIB | OBJECT-IDENTITY |
| XcmCommsMgmtConditions | |
| XcmCommsMgmtState | |
| XcmCommsStackExtProtocol |
From XEROX-GENERAL-TC
| Cardinal32 | |
| Ordinal32 | |
| XcmFixedLocaleDisplayString | |
| XcmGenSNMPv2ErrorStatus | |
| zeroDotZero | OBJECT-IDENTITY |
From XEROX-HOST-RESOURCES-EXT-TC
| XcmHrDevDetailUnitClass | |
| XcmHrDpaAvailability | |
| XcmHrDpaConditions | |
| XcmHrDpaState |
From XEROX-SERVICE-MONITORING-TC
| XcmSvcMonGroupSupport | |
| XcmSvcMonServiceDetailClass | |
| XcmSvcMonServiceDetailType | |
| XcmSvcMonServiceMgmtData | |
| XcmSvcMonServiceMgmtOperation | |
| XcmSvcMonServiceType |
How to Use in IPNetwork Monitor
Example using xcmSvcMonQueueFaultCount OID:
Select a Xerox network printers and multifunction device as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type xcmSvcMonQueueFaultCount into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The 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. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline, since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.
OIDs
| OID symbolic | OID numeric | Type | Access | Description |
|---|---|---|---|---|
| xcmSvcMonGeneral | 1.3.6.1.4.1.253.8.74.1 | |||
| XCM xcmSvcMonGeneralCreateSupport | 1.3.6.1.4.1.253.8.74.1.2.1.6 | XcmSvcMonGroupSupport | read-only | The 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. |
| xcmSvcMonGeneralEntry | 1.3.6.1.4.1.253.8.74.1.2.1 | not-accessible | An 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'). | |
| xcmSvcMonGeneralGroup | 1.3.6.1.4.1.253.8.74.2.2.1 | The Service Monitoring General Group. | ||
| XCM xcmSvcMonGeneralGroupSupport | 1.3.6.1.4.1.253.8.74.1.2.1.5 | XcmSvcMonGroupSupport | read-only | The 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. |
| ORD xcmSvcMonGeneralIndex | 1.3.6.1.4.1.253.8.74.1.2.1.1 | Ordinal32 | not-accessible | A 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. |
| ROW xcmSvcMonGeneralRowStatus | 1.3.6.1.4.1.253.8.74.1.2.1.2 | RowStatus | read-only | This 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. |
| xcmSvcMonGeneralTable | 1.3.6.1.4.1.253.8.74.1.2 | not-accessible | A 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'). | |
| XCM xcmSvcMonGeneralUpdateSupport | 1.3.6.1.4.1.253.8.74.1.2.1.7 | XcmSvcMonGroupSupport | read-only | The 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. |
| DAT xcmSvcMonGeneralVersionDate | 1.3.6.1.4.1.253.8.74.1.2.1.4 | DateAndTime | read-only | The 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. |
| PRO xcmSvcMonGeneralVersionID | 1.3.6.1.4.1.253.8.74.1.2.1.3 | ProductID | read-only | The 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). |
| xcmSvcMonMIB | 1.3.6.1.4.1.253.8.74 | 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. | ||
| xcmSvcMonMIBCompliance | 1.3.6.1.4.1.253.8.74.2.3 | The compliance statements for SNMP management agents that implement the Service Monitoring MIB. | ||
| xcmSvcMonMIBConformance | 1.3.6.1.4.1.253.8.74.2 | |||
| xcmSvcMonMIBGroups | 1.3.6.1.4.1.253.8.74.2.2 | |||
| xcmSvcMonQueue | 1.3.6.1.4.1.253.8.74.3 | |||
| XCM xcmSvcMonQueueConditions | 1.3.6.1.4.1.253.8.74.4.2.1.3 | XcmCommsMgmtConditions | read-only | The 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. |
| XCM xcmSvcMonQueueDomain | 1.3.6.1.4.1.253.8.74.3.2.1.3 | XcmCommsStackExtProtocol | read-create | The 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). |
| xcmSvcMonQueueEntry | 1.3.6.1.4.1.253.8.74.3.2.1 | not-accessible | An 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). | |
| xcmSvcMonQueueExt | 1.3.6.1.4.1.253.8.74.4 | |||
| xcmSvcMonQueueExtEntry | 1.3.6.1.4.1.253.8.74.4.2.1 | not-accessible | An entry which augments 'xcmSvcMonQueueTable', with dynamic queue routing (forwarding), state, conditions, and fault info. | |
| xcmSvcMonQueueExtGroup | 1.3.6.1.4.1.253.8.74.2.2.4 | The Service Monitoring Associated Queue Ext Group. | ||
| xcmSvcMonQueueExtTable | 1.3.6.1.4.1.253.8.74.4.2 | not-accessible | A 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). | |
| xcmSvcMonQueueExtV1EventOID | 1.3.6.1.4.1.253.8.74.4.1 | The 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'. | ||
| NTF xcmSvcMonQueueExtV2Event | 1.3.6.1.4.1.253.8.74.4.1.0.1 | This 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. | ||
| xcmSvcMonQueueExtV2EventPrefix | 1.3.6.1.4.1.253.8.74.4.1.0 | |||
| I32 xcmSvcMonQueueFaultCode | 1.3.6.1.4.1.253.8.74.4.2.1.5 | Integer32 | read-only | Encoded 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. |
| C32 xcmSvcMonQueueFaultCountEx | 1.3.6.1.4.1.253.8.74.4.2.1.4 | Counter32 | read-only | The 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. |
| STR xcmSvcMonQueueFaultString | 1.3.6.1.4.1.253.8.74.4.2.1.6 | XcmFixedLocaleDisplayString | read-only | Human-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. |
| xcmSvcMonQueueGroup | 1.3.6.1.4.1.253.8.74.2.2.3 | The Service Monitoring Associated Queue Group. | ||
| ORD xcmSvcMonQueueIndex | 1.3.6.1.4.1.253.8.74.3.2.1.1 | Ordinal32 | read-only | A 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). |
| DAT xcmSvcMonQueueLastConnectDate | 1.3.6.1.4.1.253.8.74.4.2.1.9 | DateAndTime | read-only | The date and time of last connect (and/or login) to this remote or local external job queue. |
| C32 xcmSvcMonQueueLastConnectJobs | 1.3.6.1.4.1.253.8.74.4.2.1.10 | Counter32 | read-only | The 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. |
| STR xcmSvcMonQueueName | 1.3.6.1.4.1.253.8.74.3.2.1.5 | XcmFixedLocaleDisplayString | read-create | Human-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. |
| T/F xcmSvcMonQueueOnSystem | 1.3.6.1.4.1.253.8.74.3.2.1.6 | TruthValue | read-create | Specifies whether this queue is present on this host system (local) or is on another network system (remote). |
| STR xcmSvcMonQueuePath | 1.3.6.1.4.1.253.8.74.3.2.1.4 | XcmFixedLocaleDisplayString | read-create | Human-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. |
| CAR xcmSvcMonQueueRoutingIndex | 1.3.6.1.4.1.253.8.74.4.2.1.1 | Cardinal32 | read-create | The (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. |
| DAT xcmSvcMonQueueRowCreateDate | 1.3.6.1.4.1.253.8.74.4.2.1.7 | DateAndTime | read-only | The date and time of creation of this conceptual row in the 'xcmSvcMonQueueTable' (and 'xcmSvcMonQueueExtTable'). |
| ROW xcmSvcMonQueueRowStatus | 1.3.6.1.4.1.253.8.74.3.2.1.2 | RowStatus | read-create | This 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. |
| C32 xcmSvcMonQueueRowTotalJobs | 1.3.6.1.4.1.253.8.74.4.2.1.8 | Counter32 | read-only | The 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. |
| XCM xcmSvcMonQueueState | 1.3.6.1.4.1.253.8.74.4.2.1.2 | XcmCommsMgmtState | read-only | The 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. |
| xcmSvcMonQueueTable | 1.3.6.1.4.1.253.8.74.3.2 | not-accessible | A 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)'; 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)'. | |
| xcmSvcMonService | 1.3.6.1.4.1.253.8.74.5 | |||
| XCM xcmSvcMonServiceAvailability | 1.3.6.1.4.1.253.8.74.5.2.1.7 | XcmHrDpaAvailability | read-only | The availability of this system and/or end-user service. |
| XCM xcmSvcMonServiceConditions | 1.3.6.1.4.1.253.8.74.5.2.1.6 | XcmHrDpaConditions | read-only | The current conditions (ie, state reasons) of this system and/or end-user service. |
| XCM xcmSvcMonServiceCurrentState | 1.3.6.1.4.1.253.8.74.5.2.1.4 | XcmHrDpaState | read-only | The current state of this system and/or end-user service. Usage: The current DPA object generic state of a service. |
| xcmSvcMonServiceDetail | 1.3.6.1.4.1.253.8.74.6 | |||
| XCM xcmSvcMonServiceDetailClass | 1.3.6.1.4.1.253.8.74.6.2.1.1 | XcmSvcMonServiceDetailClass | not-accessible | A service detail class, used by system administrators and end users to specify the correct class for this service detail. |
| xcmSvcMonServiceDetailEntry | 1.3.6.1.4.1.253.8.74.6.2.1 | not-accessible | A '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. | |
| xcmSvcMonServiceDetailGroup | 1.3.6.1.4.1.253.8.74.2.2.6 | The Service Monitoring Service Detail Group. | ||
| ORD xcmSvcMonServiceDetailIndex | 1.3.6.1.4.1.253.8.74.6.2.1.3 | Ordinal32 | not-accessible | A 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. |
| I32 xcmSvcMonServiceDetailInteger | 1.3.6.1.4.1.253.8.74.6.2.1.7 | Integer32 | read-create | A 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'. |
| OID xcmSvcMonServiceDetailOID | 1.3.6.1.4.1.253.8.74.6.2.1.8 | OBJECT IDENTIFIER | read-create | A 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'. |
| ROW xcmSvcMonServiceDetailRowStatus | 1.3.6.1.4.1.253.8.74.6.2.1.4 | RowStatus | read-create | This 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. |
| OCT xcmSvcMonServiceDetailString | 1.3.6.1.4.1.253.8.74.6.2.1.9 | OCTET STRING | read-create | A 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. |
| xcmSvcMonServiceDetailTable | 1.3.6.1.4.1.253.8.74.6.2 | not-accessible | A '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. | |
| XCM xcmSvcMonServiceDetailType | 1.3.6.1.4.1.253.8.74.6.2.1.2 | XcmSvcMonServiceDetailType | not-accessible | A service detail type, used by system administrators and end users to specify the correct type for this service detail. |
| CAR xcmSvcMonServiceDetailUnit | 1.3.6.1.4.1.253.8.74.6.2.1.6 | Cardinal32 | read-create | The 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. |
| XCM xcmSvcMonServiceDetailUnitClass | 1.3.6.1.4.1.253.8.74.6.2.1.5 | XcmHrDevDetailUnitClass | read-create | The 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. |
| xcmSvcMonServiceEntry | 1.3.6.1.4.1.253.8.74.5.2.1 | not-accessible | An 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. | |
| CAR xcmSvcMonServiceExternalDevice | 1.3.6.1.4.1.253.8.74.5.2.1.10 | Cardinal32 | read-create | The 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. |
| xcmSvcMonServiceGroup | 1.3.6.1.4.1.253.8.74.2.2.5 | The Service Monitoring Service Group. | ||
| ORD xcmSvcMonServiceIndex | 1.3.6.1.4.1.253.8.74.5.2.1.1 | Ordinal32 | read-only | A 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). |
| CAR xcmSvcMonServiceLogicalDevice | 1.3.6.1.4.1.253.8.74.5.2.1.9 | Cardinal32 | read-create | The 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'. |
| xcmSvcMonServiceMgmt | 1.3.6.1.4.1.253.8.74.7 | |||
| OCT xcmSvcMonServiceMgmtAdminPassword | 1.3.6.1.4.1.253.8.74.7.2.1.8 | OCTET STRING | read-create | A 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. |
| XCM xcmSvcMonServiceMgmtData | 1.3.6.1.4.1.253.8.74.7.2.1.2 | XcmSvcMonServiceMgmtData | read-create | The 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'. |
| xcmSvcMonServiceMgmtEntry | 1.3.6.1.4.1.253.8.74.7.2.1 | not-accessible | An entry containing a service management request for control of a system and/or end-user service on this host system. | |
| xcmSvcMonServiceMgmtGroup | 1.3.6.1.4.1.253.8.74.2.2.7 | The Service Monitoring Service Mgmt Group. | ||
| T/F xcmSvcMonServiceMgmtInProgress | 1.3.6.1.4.1.253.8.74.7.2.1.4 | TruthValue | read-only | The 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). |
| XCM xcmSvcMonServiceMgmtOperation | 1.3.6.1.4.1.253.8.74.7.2.1.1 | XcmSvcMonServiceMgmtOperation | read-create | The 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). |
| OCT xcmSvcMonServiceMgmtOperatorPassword | 1.3.6.1.4.1.253.8.74.7.2.1.7 | OCTET STRING | read-create | A 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. |
| ROW xcmSvcMonServiceMgmtRowStatus | 1.3.6.1.4.1.253.8.74.7.2.1.5 | RowStatus | read-create | This 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. |
| XCM xcmSvcMonServiceMgmtStatus | 1.3.6.1.4.1.253.8.74.7.2.1.3 | XcmGenSNMPv2ErrorStatus | read-only | The 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'. |
| xcmSvcMonServiceMgmtTable | 1.3.6.1.4.1.253.8.74.7.2 | not-accessible | A table containing service management requests for control of system and/or end-user services on this host system. | |
| OCT xcmSvcMonServiceMgmtUserPassword | 1.3.6.1.4.1.253.8.74.7.2.1.6 | OCTET STRING | read-create | A 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. |
| xcmSvcMonServiceMgmtV1EventOID | 1.3.6.1.4.1.253.8.74.7.1 | The value of the enterprise-specific OID in an SNMPv1 trap sent whenever an 'xcmSvcMonServiceMgmtOperation' completes. See SNMPv2 trap definition 'xcmSvcMonServiceMgmtV2Event' below for 'special semantics'. | ||
| NTF xcmSvcMonServiceMgmtV2Event | 1.3.6.1.4.1.253.8.74.7.1.0.1 | This 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. | ||
| xcmSvcMonServiceMgmtV2EventPrefix | 1.3.6.1.4.1.253.8.74.7.1.0 | |||
| STR xcmSvcMonServiceName | 1.3.6.1.4.1.253.8.74.5.2.1.3 | XcmFixedLocaleDisplayString | read-create | A 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). |
| CAR xcmSvcMonServicePhysicalDevice | 1.3.6.1.4.1.253.8.74.5.2.1.8 | Cardinal32 | read-create | The 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'. |
| XCM xcmSvcMonServicePreviousState | 1.3.6.1.4.1.253.8.74.5.2.1.5 | XcmHrDpaState | read-only | The previous state of this system and/or end-user service. Usage: The previous DPA object generic state of a service. |
| INT xcmSvcMonServicePriority | 1.3.6.1.4.1.253.8.74.5.2.1.14 | INTEGER | read-create | The 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. |
| ROW xcmSvcMonServiceRowStatus | 1.3.6.1.4.1.253.8.74.5.2.1.2 | RowStatus | read-create | This 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. |
| OCT xcmSvcMonServiceStateDetail | 1.3.6.1.4.1.253.8.74.5.2.1.16 | OCTET STRING | read-only | This 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. |
| CAR xcmSvcMonServiceStorage | 1.3.6.1.4.1.253.8.74.5.2.1.13 | Cardinal32 | read-create | The 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. |
| CAR xcmSvcMonServiceSWInstalled | 1.3.6.1.4.1.253.8.74.5.2.1.12 | Cardinal32 | read-create | The 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. |
| CAR xcmSvcMonServiceSWRun | 1.3.6.1.4.1.253.8.74.5.2.1.11 | Cardinal32 | read-create | The 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. |
| xcmSvcMonServiceTable | 1.3.6.1.4.1.253.8.74.5.2 | not-accessible | A 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. | |
| XCM xcmSvcMonServiceType | 1.3.6.1.4.1.253.8.74.5.2.1.15 | XcmSvcMonServiceType | read-create | The explicit type of this system and/or end-user service. |
| xcmSvcMonServiceV1EventOID | 1.3.6.1.4.1.253.8.74.5.1 | The 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'. | ||
| NTF xcmSvcMonServiceV2Event | 1.3.6.1.4.1.253.8.74.5.1.0.1 | This 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. | ||
| xcmSvcMonServiceV2EventPrefix | 1.3.6.1.4.1.253.8.74.5.1.0 | |||
| xcmSvcMonZeroDummy | 0.0.74 |
RFC description
Monitors application services and device health for network-accessible Xerox systems and host devices.
Start monitoring Xerox network printers and multifunction devices with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.