Cisco Explorer 1540 Specifications Page 841

  • Download
  • Add to my manuals
  • Print
  • Page
    / 924
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 840
8-83
Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)
OL-20105-01
Chapter 8 Industry-Standard Management Information Base
HOST-RESOURCES-MIB
hrDeviceID OBJECT-TYPE
SYNTAX ProductID
MAX-ACCESS read-only
STATUS current
DESCRIPTION
The product ID for this device.
::= { hrDeviceEntry 4 }
hrDeviceStatus OBJECT-TYPE
SYNTAX INTEGER { unknown(1), running(2), warning(3), testing(4), down(5) }
MAX-ACCESS read-only
STATUS current
DESCRIPTION
The current operational state of the device described by this row of the table. A value unknown(1)
indicates that the current state of the device is unknown. running(2) indicates that the device is up
and running and that no unusual error conditions are known. The warning(3) state indicates that
agent has been informed of an unusual error condition by the operational software (e.g., a disk
device driver) but that the device is still 'operational'. An example would be a high number of soft
errors on a disk. A value of testing(4), indicates that the device is not available for use because it
is in the testing state. The state of down(5) is used only when the agent has been informed that the
device is not available for any use.
::= { hrDeviceEntry 5 }
hrDeviceErrors OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only
STATUS current
DESCRIPTION
The number of errors detected on this device. It should be noted that as this object has a SYNTAX
of Counter32, that it does not have a defined initial value. However, it is recommended that this
object be initialized to zero, even though management stations must not depend on such an
initialization.
::= { hrDeviceEntry 6 }
hrProcessorTable OBJECT-TYPE
SYNTAX Sequence of hrProcessorEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
The (conceptual) table of processors contained by the host. Note that this table is potentially sparse:
a (conceptual) entry exists only if the correspondent value of the hrDeviceType object is
hrDeviceProcessor.
::= { hrDevice 3 }
hrProcessorEntry OBJECT-TYPE
Page view 840
1 ... 840 841 842 ... 924

Comments to this Manuals

No comments