Go to main content

Oracle® ILOM User's Guide for System Monitoring and Diagnostics Firmware Release 3.2.x

Exit Print View

Updated: April 2018
 
 

Oracle ILOM 3.2.x CLI Namespace Targets on ManagedDevice

The Oracle ILOM 3.2.x CLI namespace is a hierarchical tree that contains every manageable object for a managed device.

The following table describes the CLI namespace targets available in Oracle ILOM 3.2.x. The namespace targets listed in the following table are at the highest level in the tree hierarchy.

Managed Device(s)
Namespace Target
Namespace Description
Server SP
/SP
On a server SP, the properties under /SP namespace are used for 1) configuring the Oracle ILOM service processor (SP), 2) viewing log entries, 3) managing sub-components, and 4) accessing remote consoles.
/HOST
On a server SP, the properties under the /HOST namespace target are used to monitor and manage the host operating system that is installed on a rackmount server or blade server module.
Chassis Monitoring Module (CMM)
/CMM
On a blade modular system CMM, the properties under the /CMM namespace are used for 1) configuring the Oracle ILOM CMM; 2) viewing audit and event log entries, and 3) managing faults and alerts.
/CH
(3.0 legacy target)
On a blade modular system CMM, the /CH namespace is a pre-Oracle ILOM 3.1 legacy target. It is only visible when the property for legacy_targets is enabled on the CMM. The properties under the /CH namespace are used to monitor inventory status and environmental sensors, as well as to access and manage chassis sub-components (such as storage and CPU blade server modules). The target names under the /CH namespace directly correspond to the names of the chassis hardware components.
The targets and properties under /CH namespace are always available (whether you see them or not) to ensure backward compatibility with existing Oracle ILOM user scripts.
Frame Monitoring Module (FMM)
/FMM
On a Netra Modular System (NMS) FMM, the /FMM namespace is used for 1) configuring the Oracle ILOM FMM, 2) viewing audit and event log entries, and 3) managing faults and alerts.
/Networking
On an NMS FMM, the properties under the /Networking namespace are used for managing the network node(s) as if you were logged in to the network node(s) at the server SP level.

Note -  The /Networking target might not be supported on all FMMs running Oracle ILOM firmware version 3.2.5. A later firmware version might be required.

/Frame
(legacy target as of 3.2.5)
On an NMS FMM, the /Frame namespace is an Oracle ILOM legacy target. It is only visible when CLI property for legacy_targets is enabled on the FMM. The targets and properties below the /Frame namespace are used to monitor inventory status and environmental sensors, as well as to access and manage frame sub-components (such as compute nodes ). The target names under the /Frame namespace directly correspond to the names of the chassis hardware components.
The targets and properties under /Frame namespace are always available (whether they are visible or hidden) to ensure backward compatibility with existing Oracle ILOM user scripts.
Server SP
CMM
FMM
/System
On a server SP, CMM, or a FMM, the properties under the /System namespace are used to monitor the hardware health and system inventory, as well as to perform maintenance actions such as firmware updates.
The names under the /System namespace directly correspond to the hardware components installed on the managed device.
SPARC Multi-Domain Server SP
CMM
FMM
/Servers
On a CMM, FMM, or a SPARC multi-domain server SP, the properties under the /Servers namespace are used to monitor and manage the hardware sub-component configurations. For example:
  • From a SPARC multi-domain server SP, you can manage PDomains configurations (/Servers/PDomains).

  • From a CMM, you can manage blade server module configurations (/Servers/blades).

  • From a FMM, you can manage compute node configurations (/Servers/ComputeNodes).

Server SP
CMM
/SYS
(3.0 legacy target)
On a server SP or CMM, the /SYS namespace is a pre-Oracle ILOM 3.1 legacy target. It is only visible when the property for legacy_targets is enabled on the managed device. On rackmount or blade servers, this target type is similar to the /System target, but includes all targets available for Oracle ILOM 3.0. The targets and properties under /SYS namespace are always available (whether you see them or not) to ensure backward compatibility with existing Oracle ILOM user scripts.
/STORAGE
(3.0 legacy target)
On a server SP or CMM, the /Storage namespace is a pre-Oracle ILOM 3.1 legacy target. It is only visible when property for legacy_targets is enabled on the managed device. This target was previously used to manage storage components, such as SAS storage devices. The /Storage namespace target and properties are always available (whether they are visible or hidden) to ensure backward compatibility with existing Oracle ILOM user scripts.

Related Information

CLI Hierarchy for Oracle ILOM 3.2.x Targets

Here is an example of the namespace hierarchy for a server, blade chassis, or Netra frame that ships with Oracle ILOM firmware versions 3.1 or later. Actual targets displayed vary from system to system. Legacy targets are hidden by default.

Table 4  Example Oracle ILOM 3.2.x CLI Targets  
Server (Connected through SP)
Blade Chassis (Connected through CMM)
Netra Frame (Connected through FMM)
/HOST
  • bootmode (SPARC only)

  • console

  • diag

  • domain (SPARC only)

  • provisioning (x86 only)

  • tpm (SPARC only)

/STORAGE
  • sas_zoning

/System
  • Cooling

  • Power

  • Storage

  • Firmware

  • Open_Problems

  • IO_Modules

  • Blades

/System
  • Open_Problems

  • Networking

  • Firmware

  • ComputeNodes

  • Log

/System
  • Cooling

  • Processors

  • Memory

  • Power

  • Storage

  • PCI_Devices

  • Firmware

  • Networking

  • Open_Problems

  • BIOS (x86 only)

  • IO_Modules

/CMM
  • alertmgmt

  • cli

  • clients

  • clock

  • config

  • diag

  • faultmgmt

  • firmware

  • logs

  • network

  • policy

  • powermgmt

  • preferences

  • serial

  • services

  • sessions

  • users

/FMM
  • alertmgmt

  • cli

  • clients

  • clock

  • config

  • diag

  • faultmgmt

  • firmware

  • logs

  • network

  • policy

  • preferences

  • serial

  • services

  • sessions

  • users

/SP
  • alertmgmt

  • cli

  • clients

  • clock

  • config

  • diag

  • faultmgmt

  • firmware

  • logs

  • network

  • policy

  • powermgmt

  • preferences

  • serial

  • services

  • sessions

  • users

/Servers/Blades
  • Blade_0

  • Blade_1

  • Blade_2

  • Blade_3

  • Blade_4

  • Blade_5

  • Blade_6

  • Blade_7

  • Blade_8

  • Blade_9

/Servers/ComputeNodes
  • ComputeNode_0

  • ComputeNode_1

  • ComputeNode_2

  • ComputeNode_3

  • ComputeNode_4

  • ComputeNode_5

  • Compute_Node_6

  • Compute_Node_7

  • ComputeNode_8

  • ComputeNode_9

    ...

    ComputeNode_31

    Note -  Up to 31 compute nodes can be configured.

Related Information