SNI-SERVER-CONTROL-MIB: View SNMP OID List / Download MIB

Agent identification string

Agent's company name

Agent's version string . (i.e. 1.05)

Compilation time and date of agent program

Agent's major version (numerical)

Agent's minor version (numerical)

Defines whether writable objects can be written (except shutdown/power-off operations) Enumeration: 'unknown': 1, 'write-not-allowed': 2, 'write-allowed': 3.

Defines whether shutdown/power-off objects can be written Enumeration: 'unknown': 1, 'shutdown-not-allowed': 2, 'shutdown-allowed': 3.

Table with data of all configured temperature sensors

ID of the cabinet the temperature sensor is in (index, 0 based)

Number of the sensor in this cabinet (index, 0 based)

Status of this temperature sensor (OK, critical or shutdown temperature reached...). The cold and the damage temperature status levels are no longer supported (values 6, 8, 9, 10). Status not-available(99) can be a sensor of a cpu that is not installed. Status sensor-disabled(2) is currently not used. Enumeration: 'sensor-fail': 4, 'not-available': 99, 'critical-temp-warm': 7, 'ok': 3, 'warning-temp-cold': 6, 'unknown': 1, 'sensor-disabled': 2, 'damage-temp-cold': 10, 'warning-temp-warm': 5, 'damage-temp-warm': 9, 'critical-temp-cold': 8.

Purpose of this temperature sensor (CPU, ambient, housing...). Purposes disable(2) and not-available(6) are no longer used. Enumeration: 'not-available': 6, 'unknown': 1, 'housing': 5, 'io-board': 7, 'cp': 3, 'disable': 2, 'ambient': 4, 'power-backplane': 8.

Object made obsolete - no longer supported

System sends a temperature warning when temperature rises ABOVE this level (degrees Celsius)

Object made obsolete - no longer supported

System becomes critical when temperature rises ABOVE this level (degrees Celsius). A system shutdown is performed if object tempCriticalReaction is set to shutdown-and-poweroff.

Object made obsolete - no longer supported

Object made obsolete - no longer supported

Current temperature value (degrees Celsius; -1: unknown temperature, problem with sensor, see tempSensorStatus)

Reaction when a temperature gets critical (shutdown and power-off, continue...). The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'shutdown-and-poweroff': 3, 'unknown': 1, 'continue': 2.

String describing the purpose of each temperature sensor in a housing (e.g. CPU, ambient,...). This object will substitute the tempSensorPurpose object.

Table with data of all configured cooling devices (fans)

ID of the cabinet the cooling device (fan) is in (index, 0 based)

Number of the fan in this cabinet (index, 0 based)

Status of this fan (OK, failed...). Status disabled(2) is no longer used. Status prefailure-predicted(5) means the fan will fail in near future. Status redundant-fan-failed(6) means a redundant fan has failed, the system is not yet critical. Status not-manageable(7) is a fan that is available but has no management facilities. Status not-present(8) can be a hot-plug fan that is currently removed. Enumeration: 'not-manageable': 7, 'ok': 3, 'prefailure-predicted': 5, 'unknown': 1, 'disabled': 2, 'redundant-fan-failed': 6, 'not-present': 8, 'fail': 4.

Purpose of this fan (housing, component, CPU on-chip, power supply...). Purpose disabled(2) is currently not used. Enumeration: 'not-available': 7, 'unknown': 1, 'housing': 5, 'component': 4, 'disable': 2, 'cpu-onchip': 3, 'power-supply': 6.

Fax X position - obsolete; for fan indentifying use fanIdentification object

Fax Y position - obsolete; for fan indentifying use fanIdentification object

Fax Z position - obsolete; for fan indentifying use fanIdentification object

Current speed of the fan (in revolutions per minute, -1 = unknown)

Nominal speed of the fan (in revolutions per minute) on maximum power; the speed is measured the first time the agent is installed and than compared daily to the current speed on maximum power to detect a fan prefailure (-1 = unknown).

Current speed of the fan (in revolutions per minute) on maximum power (-1 = unknown).

Obsolete - no longer supported.

Obsolete - no longer supported.

Reaction when a fan has failed (shutdown and power-off, continue...). The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'shutdown-and-poweroff': 3, 'unknown': 1, 'continue': 2.

Delay time (in seconds) when shutdown should commit on fan fail (if shutdown-and-off is configured, 0 = immediately, -1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

String describing the purpose of each fan in a housing (e.g. CPU, Power Supply,...). This object will substitute the fanPurpose object.

String identifying each fan in a housing (e.g. CPU0, CPU1, PS0...)

Daily time when to automatically test fan speeds (in minutes since midnight; -1 = unknown, automatic fan test not supported). The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

Start test of all fans to get the speed at maximum power (this test is normally started automatically once a day). Reading this object just returns the value 0. Enumeration: 'start-test': 1.

Table with event log entries (can also contain critical errors when an ErrorLog for critical errors is not available)

Entry number in eventLogTable (index, 0 based)

Non-critical message log entry as described above

Number of EventLog entries (can be used to directly get all table entries with one varbind list)

Table with major and critial error log entries (can be missing on some hardware platforms)

Entry number in critical errorLogTable (index, 0 based)

Major/critical message log entry as described above

Number of ErrorLog entries (can be used to directly get all table entries with one varbind list)

Status of the hardware watchdog (periodically restarted by the server management BIOS). The hardware watchdog is only supported on SMI based management hardware, not for micro controller hardware. Enumeration: 'not-available': 4, 'unknown': 1, 'enable': 3, 'disable': 2.

Timeout time of the hardware watchdog (in seconds, -1 = unknown)

Enable/disable the hardware watchdog. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'enable': 3, 'disable': 2.

Status of the software watchdog (periodically restarted by the server management agent) Enumeration: 'not-available': 4, 'unknown': 1, 'enable': 3, 'disable': 2.

Timeout time of the software watchdog (in minutes, -1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

Enable/disable the software watchdog. The value unknown(-1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'enable': 3, 'disable': 2.

Behavior when the software watchdog timeout occurs (reboot, continue...). This value is only used if the watchdog is enabled. If set to continue and the watchdog has timeout, it will only be logged and no reset happens. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'continue': 2, 'power-cycle': 5, 'nmi': 4, 'reboot': 3.

Status of the boot watchdog (started at system boot, reset by the server management agent). If the SC agent is not started within the specified time, the management controller assumes the system did not boot correctly and executes system reboot. Enumeration: 'not-available': 4, 'unknown': 1, 'enable': 3, 'disable': 2.

Timeout time of the boot watchdog (in minutes, -1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

Enable/disable the boot watchdog. The value unknown(-1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'enable': 3, 'disable': 2.

Behavior when the boot watchdog timeout occurs (reboot, continue...). This value is only used if the watchdog is enabled. If set to continue and the watchdog has timeout, it will only be logged and no reset happens. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'continue': 2, 'power-cycle': 5, 'nmi': 4, 'reboot': 3.

Table with CPU information

Number of the CPU in the CpuTable (index, 0 based)

Type of the CPU (486, Pentium, R2000...) Enumeration: 'r4000': 104, 'r5000': 105, 'unknown-mips': 101, 'unknown': 1, 'r12000': 112, 'i486': 4, 'r10000': 110, 'r3000': 103, 'pentium-pro': 6, 'pentium': 5, 'r2000': 102, 'i386': 3.

Frequency of the CPU (in MHz, -1 = unknown)

Step (version) of the CPU (-1 = unknown)

Status of a CPU: unknown(1) : CPU status could not be evaluated disabled(2) : CPU was manually disabled in BIOS setup ok(3) : CPU is available and operating properly not-present(4) : CPU is not available, empty socket error(5) : CPU has encountered errors but is still in use fail(6) : CPU has failed and is disabled missing-termination(7): CPU socket needs a terminator module when not populated but the terminator is missing prefailure-warning(8) : CPU has too many correctable errors within a certain time period Enumeration: 'ok': 3, 'prefailure-warning': 8, 'unknown': 1, 'disabled': 2, 'not-present': 4, 'error': 5, 'fail': 6, 'missing-termination': 7.

Model of the CPU (-1 = unknown)

Name of the CPU (e.g. 'Pentium', 'Pentium Pro' ...) as text string

String containing the socket designation of a CPU. This is the same text that is written on the system board.

String containing the CPU manufacturer.

Number of logical CPUs within one physical CPU (for hyper-threading and multi-core CPUs). This is the sum of all cores and all logical CPUs of a hyper-threading CPU.

Level 1 cache size (kByte) of a physical CPU (0 if unknown or not available).

Level 2 cache size (kByte) of a physical CPU (0 if unknown or not available).

Level 3 cache size (kByte) of a physical CPU (0 if unknown or not available).

Number of cores within one physical CPU (for multi-core CPUs).

Size of the second level cache (in kBytes, 0 if not available or disabled, -1 = unknown). Object will be made obsolete in next releases; use cpuCacheL2Size instead!

Write policy of the second level cache (write-back, write-through). Object will be made obsolete in next releases (no longer required). Enumeration: 'write-through': 3, 'unknown': 1, 'write-back': 2.

Size of the whole physical memory on the system board (in MBytes, -1 = unknown)

Size of the base memory (below 1 MB) on the system board (in kBytes, -1 = unknown)

Size of the extended memory (above 1 MB) on the system board (in MBytes, -1 = unknown)

Method to get utilization values: take-snapshot-now: get all values and store them to have all values at one certain time (set this object each time you want to get new values) get-current-values (default): get the values directly without buffering. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'take-snapshot-now': 2, 'unknown': 1, 'get-current-values': 3.

Load on the PCI bus (in percent; -1 if unknown); do no longer use this object for new implementations; object replaced by pciUtilizationTable.

Load on the EISA bus (in percent; -1 if unknown)

Table with memory module descripitions

Module number (index, 0 based)

Bank number the module belongs to (-1 = unknown).

Status of the memory module socket (OK, fail, disabled...). unknown(1) : module status could not be evaluated error(2) : module has encountered errors but is still in use ok(3) : module is available and operating properly not-available(4) : empty socket, module is not available fail(5) : module has failed and is disabled prefailure-warning(6) : module has too many correctable errors within a certain time period hot-space(7) : module is a hot-spare (standby) module, which can be used as a run-time-replacement for failed modules mirror(8) : module is part of a mirror disabled(9) : module was manually disabled in BIOS setup raid(10) : module is part of a memory module RAID system Enumeration: 'not-available': 4, 'ok': 3, 'prefailure-warning': 6, 'unknown': 1, 'error': 2, 'disabled': 9, 'mirror': 8, 'fail': 5, 'raid': 10, 'hot-spare': 7.

Number of (parity) errors in this module since last error count reset (-1 = unknown)

Start address of the bank this memory belongs to (-1 = unknown). This object is obsolete when the main memory size exceeds 4 GByte. Use new object memModuleStartAddressMB instead.

Size of this memory module (in bytes, -1 = unknown). This object is obsolete when the module's size exceeds 4 GByte. Use new object memModuleSizeMB instead.

Type of memory module (Parity, NoParity, ECD, EDO...). Will be made obsolete in next agent releases!!! Use memModuleType2 for newer implementations! Enumeration: 'edc': 6, 'no-parity': 3, 'parity-or-edc': 5, 'unknown': 1, 'edo': 7, 'synchrone-edo': 8, 'other': 2, 'parity': 4.

Information about the type of a memory module (Parity, ECC, EDO, SIMM, DIMM...). The type is a combination of one or more bits. Bit field: Bit 0 - Other Bit 1 - Unknown Bit 2 - Standard Bit 3 - Fast page mode Bit 4 - EDO Bit 5 - Parity Bit 6 - ECC Bit 7 - SIMM Bit 8 - DIMM Bit 9 - RIMM Unused bits are set to zero.

String containing the socket designation of a memory module. This is the same text that is written on the system board.

Number of correctable errors in this module since last error count reset (-1 = unknown)

Information whether the memory module has been approved by the system vendor. unknown(1) is given when a module is not available or module cannot be accessed; no(2) when no approval information is found; yes(3) when a valid approval information is found in the module. Enumeration: 'unknown': 1, 'yes': 3, 'no': 2.

Start address (in MBytes) of the bank this memory belongs to (-1 = unknown). This object makes the object memModuleStartAddress obsolete (4 GByte limit).

Size (in MBytes) of this memory module (-1 = unknown). This object makes the object memModuleSize obsolete (4 GByte limit).

Reset the memory module error counters (and set a new start time), reading this object just returns the value 0. Enumeration: 'reset': 1.

Time when memory module error counters were started (seconds since 1/1/1970, -1 = unknown)

Table with PCI bus utilization data; independent of utilizationMethod object, update method for this table is always get-current-values. The number of entries in this table can be read from MIB object sniScNumberPciBusses.

PCI bus number (index, 1..n)

PCI bus load (in percent, 0xffffffff if unknown)

PCI bus data transfer rate (in MBytes/second, 0xffffffff if unknown)

PCI bus efficiency, ratio of data transfer rate through bus load (in percent); avarage value over all devices on this PCI bus; optimum value is 100 percent (0xffffffff if unknown).

String containing complete BIOS version, e.g. V4.05 R1.03.887

Number of CPU sockets available on the system board. This is not the number of currently installed CPUs! This object also describes the number of entries in the 'cpuTable' (-1 = unknown).

Number of memory module sockets available on the system board (or memory extension board). This is not the number of currently installed memory modules! This object also describes the number of entries in the 'memoryModulesTable' (-1 = unknown).

Number of PCI busses available in the system (-1 = unknown).

Total system memory usage (virtual and physical, in KBytes, -1 = unknown)

Total system memory usage (virtual and physical, in percent, -1 = unknown)

Physical system memory usage (in KBytes, -1 = unknown)

Physical system memory usage (in percent, -1 = unknown)

Total system memory available (virtual and physical, in KBytes, -1 = unknown)

Physical system memory available (in KBytes, -1 = unknown)

Total size of the whole physical memory available to the operating system; this value is similar to 'physicalMemorySize', but may be less if the system has mirror or hot spare memory modules (in MBytes, -1 = unknown)

Table with info of the users that should be paged

Index into pager user table (0 based)

Type of the installed pager (signal, numeric, alfa-numeric). The value unknown(1) and not-available(2) cannot be set, a SET will deliver 'badValue'. Enumeration: 'not-available': 2, 'unknown': 1, 'signal': 3, 'alfa-numeric': 5, 'numeric': 4.

Name of the pager user

Description (function, optional) of the pager user

Describes whether this pager is active and should be called. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'not-active': 2, 'unknown': 1, 'active': 3.

User ID number of the user's pager

Telephone dial number of the pager service provider (can also contain additional modem dial characters)

Prompt string that should be received before pager number can be sent

Encoded string containing a pager time model (when should which user be paged); this value is currently not used.

Init string that will be sent to the pager modem before the dialing begins

Number of this server. It is sent together with the error number as a message to the user's pager (-1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

COM port number (1...4) the pager modem is connected to. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'com1': 2, 'unknown': 1, 'com3': 4, 'com2': 3, 'com4': 5.

Baud rate of the pager COM port. Following values are supported: 1200, 2400, 4800, 9600, 19200 (-1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

Parity check configuration for the pager COM port. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'even': 2, 'none': 4, 'space': 6, 'unknown': 1, 'mark': 5, 'odd': 3.

Number of bits per byte on the pager COM port (7, 8, -1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

Flow control method of the pager COM port (Hardware, XON/XOFF...). The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'hardware': 3, 'unknown': 1, 'none': 2, 'xon-xoff': 4.

Optional modem name or type; can be used just as info to be displayed.

Tells whether a password is configured for the standard BIOS (read-only) Enumeration: 'unknown': 1, 'enable': 3, 'disable': 2.

Source medium to boot from: Normal system or diagnostic system standard(2): standard boot diag-system(4): boot from alternate diagnostic system The source the diagnostic system is booted from is selected in object 'srvSetupRebootFailAction'. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'diag-system': 4, 'standard': 2.

Describes what to do when a POST error has occured (halt on any error, no halt on any error...). The values unknown(1) and other(9) cannot be set, a SET will deliver 'badValue'. Enumeration: 'halt-on-any-error': 2, 'unknown': 1, 'other': 9, 'no-halt-on-any-error': 3.

The COM port which the on-board serial interface 1 is mapped to (1...4). The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'com-4': 6, 'com-1': 3, 'com-3': 5, 'com-2': 4, 'unknown': 1, 'disable': 2, 'auto': 9.

The COM port which the on-board serial interface 2 is mapped to (1...4). The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'com-4': 6, 'com-1': 3, 'com-3': 5, 'com-2': 4, 'unknown': 1, 'disable': 2, 'auto': 9.

The LPT port which the on-board parallel interface is mapped to (1...3). The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'lpt-2': 4, 'unknown': 1, 'lpt-1': 3, 'lpt-3': 5, 'disable': 2, 'auto': 9.

Describes whether the floppy controller is enabled. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'enable': 3, 'disable': 2.

Describes whether the IDE harddisk controller is enabled. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'disable': 2, 'primary': 3, 'primary-and-secondary': 4.

Describes whether the mouse port controller is enabled. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'enable': 3, 'disable': 2.

Cabinet ID number of this server (-1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'. Use this number as cabinetId for all tables containing a cabinet index. If unknown is delivered, 0 should be used as cabinet index.

Slot number (in a rack) this server is in (only for rack servers; -1 = unknown). The value unknown(-1) cannot be set, a SET will deliver 'badValue'. This object is currently not used.

deleted

deleted

deleted

deleted

deleted

deleted

Describes whether remote-on via RI modem line is enabled or not available. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'not-available': 4, 'unknown': 1, 'enable': 3, 'disable': 2.

Maximum number of retries to reboot/restart the server when a shutdown (and power-off) had occured. After this number of retries the action defined in 'srvSetupRebootFailAction' will be executed (-1 = unknown, no retries). The value unknown(1) cannot be set, a SET will deliver 'badValue'.

Describes the action on a specified number of failed reboot retries (srvSetupMaxRestartRetries=0): unknown(1) - diagnostic system cannot be determined (cannot be SET) switch-off(2) - no diag system, final power-off ide-diag-disk(3) - boot diag system from IDE disk no-diag-system(4) - no diag system available remote-image-disk(5) - boot from remote image (over LAN) pxe(6) - boot from PXE (Preboot eXecution Environment) rsb-usb(7) - boot from RSB remote source (via USB interface) bmc-remote(8) - boot from BMC from remote storage This value is also the source to be booted from when object 'stdSetupBootSource' is set to 'diag-system'. Enumeration: 'bmc-remote': 8, 'unknown': 1, 'ide-diag-disk': 3, 'rsb-usb': 7, 'remote-image-disk': 5, 'no-diag-system': 4, 'switch-off': 2, 'pxe': 6.

Describes whether the pager should be activated when reboot after error shutdown had occured. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'pager-disabled': 2, 'unknown': 1, 'page-on-every-error-reboot': 3.

Group number for storage extension communication bus. Legal values are 0..9, -1 = unknown. The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

Default number of retries to reboot/restart the server when a shutdown (and power-off) had occured. This value will be copied to object srvSetupMaxRestartRetries by the user to reset the counter to its original (default) value (-1 = unknown, no retries). The value unknown(1) cannot be set, a SET will deliver 'badValue'.

Table with system power on/off times; power-on will be performed by the real-time clock, power-off (with shutdown) by the operating system (system control service); table must be enabled before using

Day of the week the times should act upon (index, 1 based); 1 = Sunday, 2 = Monday...

Time the system should be switched on (by the real-time clock; in minutes since midnight; -1 = disabled, no on time). Only values -1 and 0..1439 are allowed.

Time the system should be switched off (by the operating system; in minutes since midnight; -1 = disabled, no off time). Only values -1 and 0..1439 are allowed.

The delay time (in minutes) the agent should wait before executing a shutdown (with doShutdown); 0 = default = shutdown immediately; -1 = unknown. The value unknown(-1) cannot be set, a SET will deliver 'badValue'.

Execute a shutdown; argument tells what kind of shutdown: shutdown: wait for user to switch off or reboot shutdown-and-off: switch off after shutdown shutdown-and-reboot: reboot after shutdown abort-pending-shutdown: abort a delayed shutdown immediately (if not already initiated) Reading this object just returns the value 0. Enumeration: 'shutdown-and-off': 2, 'abort-pending-shutdown': 4, 'shutdown': 1, 'shutdown-and-reboot': 3.

Tells how often the server was switched on in its life (-1 = unknown)

Tells how long the system was switched on in its life (in hours; -1 = unknown)

Tells how long the system was switched off in its life (in hours; -1 = unknown)

Delay (in minutes) when the system should be automatically switched on again (by real-time clock) after an error power-off (-1 = no switch-on function). The value unknown(-1) cannot be set, a SET will deliver 'badValue'. On some platforms only the values 1, 2, 3, 5, 7, 10, 15 and 20 can be set. Values between these numbers will be rounded.

Describes whether the last (current) POST (power on self test) was errornous. Object is now obsolete - use object systemBootStatus instead! Enumeration: 'unknown': 1, 'errors': 3, 'ok': 2.

Reason why the system was switched off last time Enumeration: 'MMB-continuous-operation': 36, 'remote-off': 11, 'fan-fail': 6, 'power-limiting': 35, 'watchdog-power-cycle': 37, 'temperature-damage': 8, 'keyboard': 29, 'watchdog': 10, 'power-supply-failure': 9, 'hardware-reset': 23, 'ac-fail': 4, 'clock': 5, 'unknown': 1, 'temperature-critical': 7, 'software-command': 2, 'reset-button': 25, 'peripheral-bus-error': 13, 'firmware-restart': 242, 'cpu-error': 14, 'remote-manager-reset': 32, 'power-button': 3, 'nmi': 20, 'warmstart': 24, 'remote-manager': 31, 'hardware-fail': 12, 'ac-fail-reboot': 26, 'housing-opened': 243.

Source the system was switched on from Enumeration: 'warmstart': 24, 'keyboard': 29, 'temperature-damage': 8, 'chipcard-reader': 30, 'watchdog': 10, 'power-supply-failure': 9, 'hardware-reset': 23, 'ac-fail': 4, 'clock': 5, 'unknown': 1, 'mgmt-processor-fail': 27, 'temperature-critical': 7, 'software-command': 2, 'power-cycle': 33, 'reset-button': 25, 'peripheral-bus-error': 13, 'pci-pme': 28, 'firmware-restart': 242, 'remote-on': 11, 'cpu-error': 14, 'remote-manager-reset': 32, 'power-button': 3, 'nmi': 20, 'fan-fail': 6, 'remote-manager': 31, 'housing-closed': 243, 'hardware-fail': 12, 'ac-fail-reboot': 26.

Time and Date the system was booted (seconds since 1/1/1970; -1 = unknown)

Switch the server on or off; argument tells what kind of action: on: switch power on off: switch power off power-cycle: switch power off and switch power on again reset: perform a server reset nmi: perform a non-maskable interrupt (NMI, mainly for debugging purpose) Enumeration: 'reset': 4, 'on': 1, 'off': 2, 'power-cycle': 3, 'nmi': 5.

Result of the last server boot. Enumeration: 'no-boot-cp': 4, 'diagnostic-boot-failed': 7, 'os-boot-successful': 2, 'unknown': 1, 'diagnostic-boot-successful': 3, 'hardware-failure': 8, 'no-bootable-media': 5, 'os-failed-to-load': 6.

Status of the current boot process. Enumeration: 'no-boot-cp': 3, 'reset': 12, 'os-shutdown': 10, 'off': 2, 'unknown': 1, 'setup': 5, 'diagnostic-shutdown': 11, 'os-boot': 6, 'self-test': 4, 'diagnostic-boot': 7, 'os-running': 8, 'diagnostic-running': 9.

Number of configured cabinets (server and storage extensions, at least 1: the server itself)

Number of detected cabinets (server and storage extensions, at least 1: the server itself). This is also the number of entries in cabinetInfosTable.

Table with data of all configured cabinets

Cabinet ID number, index into the cabinet table

The place where the cabinet is located (user can store any string here to identify the cabinet location)

System ident number (serial number) - will be a number like 'XYZZ 12345678'. XYZZ is the cabinet identifier and is mandatory. It will be used to identify the cabinet model name (i.e. PCD-5S). 12345678 is the cabinet serial number and is optional. Cabinet identifier and serial number are separated by a blank character!

System name string (i.e. PCD-5S, Primergy 150...)

The number of configured cooling devices (fans) in this cabinet (-1 = unknown)

The number of configured temperature sensors in this cabinet (-1 = unknown)

The number of available power supplies in this cabinet (-1 = unknown)

The number of power supply slots in this cabinet (is the maximum number of installable power supplies; 0 if no hot-plug slots available; -1 = unknown)

Uninterruptable power supply for this cabinet available: 0: No UPS 1..n: Index in UPS table -1: unknown

Serial number of the cabinet's system board

Revision (GS) of the cabinet's system board (-1 = unknown). Value obsolete, use sieScCabinetBoardRevisionString instead!

Identifier string of the cabinet's system board

Type of the cabinet's system management controller (i.e. SNI System Control Board)

Firmware version (major number) of the cabinet's system management controller (-1 = unknown). This object will be replaced by sieScCabinetControllerFirmware in future versions.

Firmware version (minor number) of the cabinet's system management controller (-1 = unknown). This object will be replaced by sieScCabinetControllerFirmware in future versions.

Attribute of a cabinet (Primary/secondary server, storage extension...) Enumeration: 'standalone-server': 2, 'other': 1, 'primary-server': 3, 'storage-extension': 5, 'secondary-server': 4.

Power-on state of the cabinet Enumeration: 'unknown': 1, 'off': 2, 'disconnected': 4, 'on': 3.

Describes the status of a cabinet (OK, degraded, error...) Enumeration: 'fail': 4, 'degraded': 2, 'ok': 1, 'error': 3.

The source from which the cabinet was powered off last time Enumeration: 'power-supply-failure': 9, 'software-off': 2, 'fan-failure': 6, 'clock': 5, 'remote-off': 11, 'unknown': 1, 'critical-temperature': 7, 'power-switch': 3, 'damage-temperature': 8, 'power-fail': 4.

Action on AC power resume after AC has failed. not-available(2) : function not available, behavior is hardware-defined. as-before(3) : server gets the same power state as before the AC fail. remain-off(4) : server remains off on power resume. switch-on(5) : server is always switched on on power resume. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'not-available': 2, 'unknown': 1, 'remain-off': 4, 'switch-on': 5, 'as-before': 3.

Battery buffering unit for this cabinet available. The value unknown(1) cannot be set, a SET will deliver 'badValue'. Enumeration: 'unknown': 1, 'false': 2, 'true': 3.

Value is obsolete. This value should no longer be used for cabinet identification. Use cabinetHousingType to identify the housing type and cabinetSystemName for the type of the cabinet!

More detailed status information from this cabinet. The StatusDetail object is set to reflect the new status. ok: (status ok) no failures detected. selftestWarning: (status degraded) the SCB firmware issued a warning condition. selftestFailure: (status error) the SCB firmware detected a failure that prevents it from functioning. powerFailure: (status degraded) the AC input at the power supply or the AC input at the UPS failed. fanFailure: (status error) A fan in this cabinet failed. The system is going to shut down. temperatureFailure: (status error) A sensor in this cabinet detected an over temperature. The system is going to shut down. communicationFailure: (status error) The SCB in the CPU cabinet has lost communication with the SCB in this cabinet. The system is going to shut down. powerOff: (status degraded) The cabinet is switched off. Enumeration: 'powerFailure': 8, 'ok': 1, 'communicationFailure': 64, 'selftestFailure': 4, 'temperatureFailure': 32, 'temperatureWarning': 256, 'fanFailure': 16, 'powerOff': 128, 'bbuError': 512, 'selftestWarning': 2.

Type string for cabinet housing type (i.e. 'P300' for all PRIMERGY 3xx housings); this object should be used to identify the cabinet instead of using object cabinetSystemType (i.e. for painting pictures in management applications)

Status of the cabinet's front door Enumeration: 'unknown': 1, 'open': 2, 'closed': 3.

Status describing whether the housing is open or closed Enumeration: 'unknown': 1, 'open': 2, 'closed': 3.

Number of entries in power supply voltage table

The cabinet's system management controller firmware version (i.e. '1.1.4.88'). This object will replace the previous objects cabinetControllerFirmwareMinor and cabinetControllerFirmwareMajor.

Revision string (GS, WGS...) of the cabinet's system board. This object replaces the previous object cabinetBoardRevision.

Provides a URL that may be used by a front-end to start a web browser and connect it directly to the cabinet's administrative web server (e.g. https://10.0.0.2:443/foobar.html).

REMCS system identification string (binary data): Format of Fujitsu REMCS ID (40byte) Format = TTMMMMMMMMMMMMmmmmmmmmmmmmCCnnnnnnnnnnnn TT : 2byte : Type ID for Company Name MM...M : 12byte : Model Name mm...m : 12byte : Device Name CC : 2byte : Checksum nn...n : 12byte : Serial number

Value is obsolete Enumeration: 'fail': 4, 'degraded': 2, 'ok': 1, 'error': 3.

Value is obsolete. This value should no longer be used for server identification. Use serverHousingType to identify the housing type and cabinetSystemName for the type of the server!

Type string for cabinet housing type (i.e. 'P300' for all PRIMERGY 3xx housings); this object should be used to identify the cabinet instead of using object serverType (i.e. for painting pictures in management applications). This is the same value as from object cabinetHousingType for the server cabinet.

Universal Unique ID (UUID) number - this is a world wide unique ID number of the server. Can be used for identifying a server. The UUID string format is like this: 157E465A-A4AC-D711-A847-DD85CECD12EC

Table with power supply groups in the cabinets

Cabinet ID, index into the power supply table (0 based)

Status of the cabinet's power supply group; ok: all units OK, number >= minimum degraded: one or more units failed, number OK >= minimum critical: number OK < minimum. Enumeration: 'unknown': 1, 'degraded': 3, 'critical': 4, 'ok': 2.

Number of available redundant power supply units (i.e. 2 units minimum, 3 available -> redundancy is 1, -1 = unknown)

Table with info about the configured power supply units

Cabinet ID, index into the power supply unit table (0 based)

Power supply unit number, index into power supply unit table (0 based)

Status of the power supply unit (OK, failed, not present...) Enumeration: 'not-manageable': 8, 'ok': 3, 'fan-failure': 10, 'ac-fail': 5, 'unknown': 1, 'critical-temperature': 7, 'failed': 4, 'not-present': 2, 'dc-fail': 6, 'fan-failure-predicted': 9.

Power supply unit designation. This string specifies a name/designation for the power supply unit. The designation string may not be available on some platforms.

Table with power supply voltage information

Cabinet number, index into the power supply voltage table (0 based)

Power supply voltage number, index into power supply voltage table (0 based)

Status of the power supply voltage; 'not-available' maybe the voltage of an empty CPU socket; 'out-of-range' comes when the voltage is out of range; 'prefailure' is used for battery voltages and informs that the battery is predicted to fail in near future. Enumeration: 'not-available': 2, 'ok': 3, 'unknown': 1, 'out-of-range': 6, 'too-low': 4, 'battery-prefailure': 7, 'too-high': 5.

Power supply voltage designation. This string specifies the voltage by clear text (e.g. 5V, 12V, 3.3V...)

Power supply voltage minimum level (1/100th Volts; -1 = unknown)

Power supply voltage maximum level (1/100th Volts; -1 = unknown)

Power supply voltage current level, negative voltages are reported as negative values (1/100th Volts, e.g. 330 means 3.30 Volts; -177 (0xFFFFFF4F) means -1.77 Volts; 0xFFFFFFFF = unknown)

Power supply voltage nominal level (1/100th Volts; -1 = unknown)

Power supply output load in percent of maximum load; 0xFFFFFFFF = unknown

Number of uninterruptable power supplies (UPS) in this system (-1 = unknown)

Table with uninterruptable power supplies used in this system. The index is the UPS number used in the system. One or more server or storage-extension objects can reference to a UPS entry in this table.

Number of the UPS in this table (index, 1 based)

Tells whether the UPS was detected Enumeration: 'unknown': 1, 'false': 2, 'true': 3.

Maximum time this UPS will be discharged, after that a shutdown will be performed (seconds; -1 = unknown)

Vendor name of the UPS

Type of the UPS; can be used to identify an OEM UPS with an OEM agent

Object identifier of an OEM UPS MIB; no agent if empty OID

IP address of an OEM UPS SNMP agent; no agent if empty

Time (in seconds) the UPS is running on battery since power fail (will be cleared on power recovery)

Status of the service processor's backup battery (not present, OK, recharging) Enumeration: 'discharging': 7, 'ok': 3, 'unknown': 1, 'recharging': 5, 'failed': 6, 'not-present': 2, 'on-battery': 4.

Maximum time this backup battery will be discharged, after that a shutdown will be performed (seconds; -1 = unknown)

Time (in seconds) the backup battery is running on battery since power fail (will be cleared on power recovery)

Perform a discharge/charge cycle on the backup battery. Reading this object just returns the value 0. Enumeration: 'recharge': 1.

Reads the current charge level of the rechargeable battery (in percent of the maximum capacity).

Send a trap to the manager application(s) to test connection and trap configuration; trap cannot be disabled. Reading this object just returns the value 0. Enumeration: 'send-trap': 1.

Table with the interface parameters of all management channels, which are controlled by this server.

The interface parameters of the designated management channel interface.

CabinetId of the cabinet where the management channel interface resides.

Index number of the channel management interface (index, 0 based).

The interface type of the interface. Enumeration: 'lan': 2, 'other': 1, 'dial-up': 3.

The IP v4 address of the interface.

The IP v4 subnet mask of the interface.

The interface address of the physical layer of the interface (MAC address).

The telephone dial number of this interface. Only useful if the interfaceType is of type dial-up(3).

The managegement channel type of the interface: primary: local operating system interface secondary: local management controller LAN interface management-blade: management blade interface (in a blade server chassis) secondary-remote: remote management controller (in an RSB concentrator environment) secondary-remote-backup: backup remote management controller baseboard-controller: baseboard management controller Enumeration: 'unknown': 1, 'secondary-remote-backup': 6, 'primary': 2, 'management-blade': 4, 'secondary-remote': 5, 'baseboard-controller': 7, 'secondary': 3.

Defines if the ip address should be requested by a dhcp service. Enumeration: 'unknown': 1, 'configured': 2, 'not-configured': 3.

The type of the remote or baseboard management controller (for identification), like 'RSB', 'RSB S2', 'RSB S2 LP'... These names will not be changed if defined once.

The model name of the remote management controller (for displaying), like 'Remote Service Board', 'RemoteView Service Board S2'... This name should not be used for identification, only for displaying (can be changed in different firmware versions)!

The FW version of the remote or baseboard management controller as string;

Table with the components attached to the service processor

The components attached to the service processor

Id of the service processor this component is attached to (index, 0 based)

Index number of the service component (index, 0 based)

The name of the component in human readable form

The type of the componen we are dealing with. Enumeration: 'accumulator': 4, 'lan': 2, 'other': 1, 'dial-up': 3.

Describes the status of the component managed by the service processor. Degraded means that some problems have occurred. Error that the component has reported an error that prevents the component form working. Failed means that the component is no longer reacting to the agents requests. Enumeration: 'failed': 4, 'degraded': 2, 'ok': 1, 'error': 3.

The managegement channel type of the currently used management channel. Enumeration: 'unknown': 1, 'primary': 2, 'secondary': 3.

Name of server the trap occured

Time the trap occured (in seconds since 01/01/1970 00:00h)

Number of the cabinet where the trap was generated

Number of the object that generated the trap (fan, temperature sensor...)

Additional string to be displayed in the trap text

The estimated remaining BBU/UPS capacity in minutes. In the current implementation this is the time remaining until the system will shut down.

See scbUPSSecondsOnBattery/scbBBUSecondsOnBattery.

The value of trapMinutesRemaining at which a shut down is initiated. In the current implementation this is always 0.

Additional numeric value to be displayed in the trap text

The number of the management channel interface.

Test trap to verify trap connection.

The indicated fan failed.

The temperature of the indicated sensor has decreased to the normal level.

The temperature of the indicated sensor has reached the warning level.

The temperature of the indicated sensor is out of tolerance range. The system will shut down and power off if shutdown is enabled.

The UPS is operating on battery power or the power supply is drawing current from the backup battery unit (BBU). This status is persistent and is resent at one minute intervals until the mains returns or the system is switched off.

The mains voltage returned after a power failure.

Currently the only possible warning is: SCB battery (nearly) empty.

The Server Management controller failed.

Communication with the Server Management controller lost.

A UPS has been detected, but no UPS is configured. This trap will be repeated every 60 minutes until the condition is removed.

A UPS is configured, but no UPS has been detected. This trap will be repeated every 60 minutes until the condition is removed.

A BBU has been detected, but no BBU is configured. This trap will be repeated every 60 minutes until the condition is removed.

A BBU is configured, but no BBU has been detected. This trap will be repeated every 60 minutes until the condition is removed.

One or more storage extensions missing.

The actual number of storage extensions is higher than the configured number.

The cabinet has been switched off.

The cabinet has been switched on.

The agent has detected an internal error.

The server is being shut down.

The indicated fan became critical.

The agent has detected a mismatch in the configuration of the server.

One hot-replace power supply was removed.

One hot-replace power supply was added.

One hot-replace power supply failed.

Power supply is working again.

Power supply status has become critical.

The indicated fan is OK again.

The indicated temperature sensor is broken.

The server management BIOS is disabled.

Mains failed in the specified cabinet. This can only happen in storage extension cabinets without UPS or BBU. A server will not have time to send this event.

Two ore more cabinets (server or storage extension) have the same ID number. The system will not run properly.

An error message was written into the systemboard's event/error log. This could have happened when an error occured before the agent was running or any error without a specific event message. See server management event/error log for detailed error description.

The indicated broken temperature sensor is OK again.

Communication with the Server Management controller established again.

A correctable memory error at specified address was detected.

An uncorrectable memory error at specified address was detected.

A correctable memory error at specified bank was detected.

An uncorrectable memory error at specified bank was detected.

A correctable memory error at specified module was detected.

An uncorrectable memory error at specified module was detected.

A correctable memory error at unknown address was detected.

An uncorrectable memory error at unknown address was detected.

The power-off time is reached! System will shutdown in after delay.

The front door status has changed.

The housing open status has changed

The indicated redundant fan failed.

One redundant hot-replace power supply failed.

Power supply voltage is within normal range again.

Power supply voltage is too low.

Power supply voltage is too high.

The indicated hot-plug fan was inserted.

The indicated hot-plug fan was removed.

This event will be sent if a pending server shutdown has been cancelled by the user.

The CPU clock frequency has been reduced because of a temperature problem.

The server has been powered on.

The system boot failed because no valid boot CPU has been found.

This trap will be sent when the system boot fails, because the power on selftest (POST) has reported an error.

This trap will be sent when the bios setup has been entered.

This trap will be sent when no bootable operating system can be found.

This trap will be sent when the boot watchdog expires.

This trap will be sent when the software watchdog expires.

This trap will be sent when an user authentication failure is detected via PPP, FTP, HTTP or telnet fails.

This trap will be sent when a server is reset and diagnostic boot is enabled. The value in trapString specifies the primary channel i.e. the server name (from which the primary IP address may be derived).

This trap will be sent when a boot retry counter gets zero on power up

The System Event Log is full. No more messages can be logged. This trap will not occur on wrap-around log types.

A memory module is predicted to fail (prefailure).

A memory module is failing.

A memory module had failed and was replaced by a hot-spare module.

Power supply redundancy no longer available.

The warning threshold for the number of System Event Log entries has been exceeded.

A CPU is predicted to fail (prefailure).

DC power failed in the specified cabinet. This is the result of the system's power-good sensor monitoring. The system may stop when this condition occurs.

A critical error happend while BIOS selftest. This error needs to be acknowledged to clear the error condition.

This trap will be sent when the BIOS selftest watchdog expires. This watchdog expires when the BIOS selftest cannot be finished in a certain time period.

Power supply voltage is out of range.

Battery is predicted to fail.

The system was restarted after a severe problem. See server management message log (recovery log) for detailed information.