Document Information
Using This Documentation
Related Documentation
Documentation Feedback
Product Downloads
Download Product Software and Firmware
Oracle ILOM 3.1 Firmware Version Numbering Scheme
Support and Accessibility
Quick Start
Oracle ILOM 3.1 – Quick Start
Factory Default Settings
Mandatory Setup Tasks
Optional Setup Tasks
Daily Management Tasks
Routine Maintenance Tasks
Initial Setup FAQs
Configuration and Maintenance
Setting Up a Management Connection to Oracle ILOM and Logging In
Establishing a Management Connection to Oracle ILOM
Logging In to Oracle ILOM Server SP or CMM
Configuring Oracle ILOM for Maximum Security
Setting Up and Maintaining User Accounts
Managing User Credentials
Configuring Local User Accounts
Configuring Active Directory
Configuring LDAP/SSL
Configuring LDAP
Configuring RADIUS
Modifying Default Settings for Network Deployment and Administration
Network Deployment Principles and Considerations
Modifying Default Management Access Configuration Properties
Modifying Default Connectivity Configuration Properties
Example Setup of Dynamic DNS
Assigning System Identification Information
Setting Properties for SP or CMM Clock
Suggested Resolutions for Network Connectivity Issues
Using Remote KVMS Consoles for Host Server Redirection
First-Time Setup for Oracle ILOM Remote Console
Launching and Using the Oracle ILOM Remote Console
First Time Setup for Oracle ILOM Storage Redirection CLI
Launching and Using the Oracle ILOM Storage Redirection CLI
Starting and Stopping a Host Serial Redirection Session
Host Serial Console Log Properties
Configuring Host Server Management Actions
Controlling Host Power to Server or Blade System Chassis
Setting Host Diagnostic Tests to Run
Setting Next Boot Device on x86 Host Server
Setting Boot Behavior on SPARC Host Server
Overriding SPARC Host Boot Mode
Managing SPARC Host Domains
Setting SPARC Host KeySwitch State
Setting SPARC Host TPM State
Setting Up Alert Notifications and Syslog Server for Event Logging
Configuring Alert Notifications
Configuring Syslog for Event Logging
Setting System Management Power Source Policies
Power-On and Cooling-Down Policies Configurable From the Server SP
System Management Power Supply Policies Configurable From CMM
Setting Power Alert Notifications and Managing System Power Usage
Setting Power Consumption Alert Notifications
Setting CMM Power Grant and SP Power Limit Properties
Setting SP Advanced Power Capping Policy to Enforce Power Limit
Setting SP Power Management Settings for Power Policy (SPARC)
Setting the CMM Power Supply Redundancy Policy
Performing Oracle ILOM Maintenance and Configuration Management Tasks
Performing Firmware Updates
Reset Power to Service Processor or Chassis Monitoring Module
Backing Up, Restoring, or Resetting the Oracle ILOM Configuration
Maintaining x86 BIOS Configuration Parameters
BIOS Configuration Management
Performing BIOS Configuration Tasks From Oracle ILOM
SAS Zoning Chassis Blade Storage Resources
Zone Management for Chassis-Level SAS-2 Capable Resources
Manageable SAS-2 Zoning-Capable Devices
Sun Blade Zone Manager Properties
Important SAS Zoning Allocations Considerations
Enabling Zoning and Creating SAS-2 Zoning Assignments
Managing Existing SAS-2 Storage Resource Allocations
Resetting Sun Blade Zone Manager Allocations to Factory Defaults
Resetting the Zoning Password to Factory Default for Third-Party In-Band Management
User's Guide
Oracle ILOM Overview
About Oracle ILOM
Oracle ILOM Features and Functionality
Supported Management Interfaces
Supported Operating System Web Browsers
Integration With Other Management Tools
Getting Started With Oracle ILOM 3.1
Logging In to Oracle ILOM
Navigating the Redesigned 3.1 Web Interface
Navigating the Command-Line Interface (CLI) Namespace Targets
Collecting System Information, Monitoring Health Status, and Initiating Host Management
Collecting Information, Status, and Initiating Common Actions
Administering Open Problems
Administering Service Actions: Oracle Blade Chassis NEMs
Managing Oracle ILOM Log Entries
Performing Commonly Used Host Management Actions (Web)
Applying Host and System Management Actions
Administering Host Management Configuration Actions
Administering System Management Configuration Actions
Troubleshooting Oracle ILOM Managed Devices
Network Connection Issues: Oracle ILOM Interfaces
Tools for Observing and Debugging System Behavior
Enabling and Running Oracle ILOM Diagnostic Tools
Real-Time Power Monitoring Through Oracle ILOM Interfaces
Monitoring Power Consumption
Monitoring Power Allocations
Analyzing Power Usage Statistics
Comparing Power History Performance
Managing Oracle Hardware Faults Through the Oracle ILOM Fault Management Shell
Protecting Against Hardware Faults: Oracle ILOM Fault Manager
Oracle ILOM Fault Management Shell
Using fmadm to Administer Active Oracle Hardware Faults
Using fmdump to View Historical Fault Management Logs
Using fmstat to View the Fault Management Statistics Report
Using the Command-Line Interface
About the Command-Line Interface (CLI)
CLI Reference For Supported DMTF Syntax, Command Verbs, Options
CLI Reference For Executing Commands to Change Properties
CLI Reference For Mapping Management Tasks to CLI Targets
CLI Reference
Basic CLI Command Reference for Oracle ILOM 3.1
System Information and Management
Host and System Control
Oracle ILOM Initial Setup
System Monitoring and Status
System Inventory
Oracle ILOM Maintenance
Oracle ILOM Configuration Management
Oracle ILOM Help
SNMP, IPMI, CIM, WS-MAN Protocol Management
SNMP Overview
About Simple Network Management Protocol
SNMP Components
Oracle ILOM SNMP MIBs
SNMP Command-Line Syntax Examples
Configuring SNMP Settings in Oracle ILOM
Managing SNMP Read and Write Access, User Accounts, and SNMP Trap Alerts (CLI)
Managing SNMP Read and Write Access, User Accounts, and SNMP Trap Alerts (Web)
Downloading SNMP MIBs Using Oracle ILOM
Manage User Accounts Using SNMP
Before You Begin – User Accounts (SNMP)
Configuring Oracle ILOM User Accounts (SNMP)
Configuring Oracle ILOM for Active Directory (SNMP)
Manage DNS Name Server Settings (SNMP)
Configuring Oracle ILOM for LDAP (SNMP)
Configuring Oracle ILOM for LDAP/SSL (SNMP)
Configuring Oracle ILOM for RADIUS (SNMP)
Manage Component Information and Email Alerts (SNMP)
Before You Begin – Component Information (SNMP)
Viewing Component Information (SNMP)
Managing Clock Settings, Event Log, Syslog Receiver, and Alert Rules (SNMP)
Configuring SMTP Client for Email Alert Notifications (SNMP)
Configuring Email Alert Settings (SNMP)
Monitor and Manage System Power (SNMP)
Before You Begin – Power Management (SNMP)
Monitoring the Power Consumption Interfaces (SNMP)
Maintaining System Power Policy (SNMP)
Managing System Power Properties (SNMP)
Manage Oracle ILOM Firmware Updates (SNMP)
Update Oracle ILOM Firmware (SNMP)
Manage Oracle ILOM Backup and Restore Configurations (SNMP)
View and Configure Backup and Restore Properties (SNMP)
Manage SPARC Diagnostics, POST, and Boot Mode Operations (SNMP)
Before You Begin – Manage SPARC Hosts (SNMP)
Managing SPARC Diagnostic, POST, and Boot Mode Properties (SNMP)
Server Managment Using IPMI
Intelligent Platform Management Interface (IPMI)
Configuring the IPMI Service
Using IPMItool to Run ILOM CLI Commands
Performing System Management Tasks (IPMItool)
IPMItool Utility and Command Summary
Server Management Using WS-Management and CIM
WS-Management and CIM Overview
Configuring Support for WS-Management in Oracle ILOM
Supported DMTF SMASH Profiles, CIM Classes and CIM Indications
Oracle's Sun-Supported CIM Classes
Document Conventions for Oracle's Sun-Supported CIM Classes
Oracle_AssociatedIndicatorLED
Oracle_AssociatedSensor
Oracle_Chassis
Oracle_ComputerSystem
Oracle_ComputerSystemPackage
Oracle_Container
Oracle_ElementCapabilities
Oracle_ElementConformsToProfile
Oracle_EnabledLogicalElementCapabilities
Oracle_HWCompErrorOkIndication
Oracle_IndicatorLED
Oracle_InstCreation
Oracle_InstDeletion
Oracle_LogEntry
Oracle_LogManagesRecord
Oracle_Memory
Oracle_NumericSensor
Oracle_PhysicalAssetCapabilities
Oracle_PhysicalElementCapabilities
Oracle_PhysicalMemory
Oracle_PhysicalPackage
Oracle_Processor
Oracle_ProcessorChip
Oracle_Realizes
Oracle_RegisteredProfile
Oracle_RecordLog
Oracle_ReferencedProfile
Oracle_Sensor
Oracle_SpSystemComponent
Oracle_SystemDevice
Oracle_ThresholdIndication
Oracle_UseOfLog
SNMP Command Examples
snmpget Command
snmpwalk Command
snmpbulkwalk Command
snmptable Command
snmpset Command
snmptrapd Command
Feature Updates and Release Notes
Feature Enhancements as of Oracle ILOM 3.1
Feature Enhancements Summary
Updates to Oracle ILOM 3.1.x Firmware
Initial 3.1 Point Releases for Servers and Sun Blade 6000 CMM
Deprecation Notice for WS-Man as of Oracle ILOM 3.2.1
Oracle ILOM 3.1 Known Issues
Documentation Titles in Translated Documents
Glossary
Index
Oracle_PhysicalComponent
Description: |
The PhysicalComponent class represents any low-level or basic component within a
package. A component object either can not or does not need to be
decomposed into its constituent parts. |
Inheritance: |
CIM_PhysicalComponent |
Properties: |
For a description of the supported properties for the Oracle_PhysicalComponent
class, see the following table.
|
Profile: |
Physical Asset |
|
Table 130 Properties for Oracle_PhysicalComponent
|
|
|
|
CreationClassName |
string |
The CreationClassName property is a mandatory key property. CreationClassName indicates the name
of the class or the subclass used in the creation of an instance.
When used with the other key properties of this class, this property allows
all instances of this class and its subclasses to be uniquely identified. |
Set to
Oracle_PhysicalComponent. |
Tag |
string |
The Tag property is a mandatory key property. An arbitrary string that uniquely identifies
the physical element and serves as the key of the element. The Tag
property can contain information such as asset tag or serial number data. The key
for the physical element is placed very high in the object hierarchy to
independently identify the hardware or entity, regardless of physical placement in or on
cabinets, adapters, and so on. For example, a hot-swappable or removable component can
be taken from its containing (scoping) package and be temporarily unused. The object continues
to exist and can even be inserted into a different scoping container. Therefore,
the key for physical element is an arbitrary string and is defined independently
of any placement or location-oriented hierarchy. |
Set to component NAC name. |
-CanBeFRUed |
boolean |
A boolean that indicates
whether this physical element can be a FRU (TRUE) or not (FALSE). |
Set to
TRUE or FALSE depending on whether the component is considered to be a
FRU by the platform. |
Description |
string |
The Description property provides a textual description of the object. |
Appropriate
value. |
ElementName |
string |
User-friendly name. This property allows each instance to define a user-friendly name in
addition to its key properties, identity data, and description information.
Note - The Name property
of ManagedSystemElement is also defined as a user-friendly name. But, it is often
subclassed to be a key. It is not reasonable that the same property
can convey both identity and a user-friendly name, without inconsistencies. Where Name exists and
is not a key (such as for instances of LogicalDevice), the same information
can be present in both the Name and ElementName properties.
|
Set to component
NAC name. |
HealthState |
uint16 |
Indicates the current health of the element. This attribute expresses the health
of this element but not necessarily that of its subcomponents. The possible values
are 0 to 30, where 5 means the element is entirely healthy and
30 means the element is completely nonfunctional. The following continuum is defined:
30 (Non-Recoverable Error) - The element has completely failed, and recovery is not possible. All functionality provided by this element has been lost.
25 (Critical Failure) - The element is nonfunctional, and recovery might not be possible.
20 (Major Failure) - The element is failing. It is possible that some or all of the functionality of this component is degraded or not working.
15 (Minor Failure) - All functionality is available but some might be degraded.
10 (Degraded/Warning) - The element is in working order and all functionality is provided. However, the element is not working to the best of its abilities. For example, the element might not be operating at optimal performance or it might be reporting recoverable errors.
5 (OK) - The element is fully functional and is operating within normal operational parameters and without error.
|
Appropriate value
depending on whether the component is in error state or not. |
|
|
- 0 (Unknown) - The implementation cannot report on HealthState at this time. DMTF has reserved the unused portion of the continuum for additional health states in the future.
Possible values are: {0,
5, 10, 15, 20, 25, 30, ..} Definitions for these values are: {Unknown, OK,
Degraded/Warning, Minor failure, Major failure, Critical failure, Non-recoverable error, DMTF Reserved} |
|
Manufacturer |
string |
The name of
the organization responsible for producing the PhysicalElement. This organization might be the entity from
whom the element is purchased, but this is not necessarily true. The latter
information is contained in the Vendor property of CIM_Product. |
Appropriate value if the component
is considered as a FRU by the platform. |
Model |
string |
The name by which the PhysicalElement
is generally known. |
Appropriate value if the component is considered a FRU by the platform. |
OperationalStatus |
Uint16
[] |
Indicates the current statuses of the element. Various operational statuses are defined. Many
of the enumeration's values are self-explanatory. However, a few are not and are
described here in more detail.
Stressed - indicates that the element is functioning, but needs attention. Examples of stressed states are overload, overheated, and so on.
Predictive Failure - indicates that an element is functioning nominally but predicting a failure in the near future.
In Service - describes an element being configured, maintained, cleaned, or otherwise administered.
No Contact - indicates that the monitoring system has knowledge of this element, but has never been able to establish communications with it.
Lost Communication - indicates that the ManagedSystemElement is known to exist and has been contacted successfully in the past, but is currently unreachable.
Stopped and Aborted - are similar, although the former implies a clean and orderly stop, while the latter implies an abrupt stop where the state and configuration of the element might need to be updated.
Dormant - indicates that the element is inactive or quiesced.
Supporting Entity in Error - indicates that this element might be OK but that another element, on which it is dependent, is in error. An example is a network service or endpoint that cannot function due to lower-layer networking problems.
|
OperationalStatus[0] will have appropriate value depending on whether the component
is in error state or not. |
|
|
OperationalStatus replaces the Status property on ManagedSystemElement to
provide a consistent approach to enumerations, to address implementation needs for an array property,
and to provide a migration path from today's environment to the future. This
change was not made earlier because it required the deprecated qualifier. Due to
the widespread use of the existing Status property in management applications, providers or
instrumentation should provide both the Status and OperationalStatus properties. Further, the first value of
OperationalStatus should contain the primary status for the element. When instrumented, Status (because it is
single-valued) should also provide the primary status of the element. Possible values are: {0, 1,
2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13,
14, 15, 16, 17, 18, .., 0x8000..} Definitions of these values are: {Unknown, Other, OK,
Degraded, Stressed, Predictive Failure, Error, Non- Recoverable Error, Starting, Stopping, Stopped, In Service,
No Contact, Lost Communication, Aborted, Dormant, Supporting Entity in Error, Completed, Power Mode, DMTF
Reserved, Vendor Reserved} |
|
PartNumber |
string |
The part number assigned by the organization that is responsible for
producing or manufacturing the PhysicalElement. |
Appropriate value if the component is considered a FRU
by the platform. |
SKU |
string |
The stock-keeping unit number for this PhysicalElement. |
Will have the appropriate
value if the component is considered a FRU by the platform. |
SerialNumber |
string |
A manufacturer-allocated number
used to identify the PhysicalElement. |
Will have the appropriate value if the component is considered
a FRU by the platform. |
StatusDescriptions |
string[] |
Strings describing the various OperationalStatus array values. For example,
if Stopping is the value assigned to OperationalStatus, then this property can contain an
explanation as to why an object is being stopped.
Note - Entries in this array
are correlated with those at the same array index in OperationalStatus.
|
StatusDescriptions[0] will have appropriate
description on the reason for the value of OperationalStatus[0]. |
|