Skip Navigation Links | |
Exit Print View | |
Oracle Integrated Lights Out Manager (ILOM) 3.1 Documentation Collection |
Download Product Software and Firmware
Oracle ILOM 3.1 Firmware Version Numbering Scheme
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
Configuring Local User Accounts
Modifying Default Settings for Network Deployment and Administration
Network Deployment Principles and Considerations
Management Access Deployment Options
Connectivity Deployment Options
Use of Web Server Certificates and SSH Server-Side Keys
Default Timeout for CLI and Web Sessions
Displaying Banner Messages at Log-In
Input Format for IPv4 and IPv6 Addresses
Default Network Ports Used by Oracle ILOM
Legacy Oracle Servers Not Supporting IPv6
Modifying Default Management Access Configuration Properties
Modifying Default Connectivity Configuration Properties
Assigning System Identification Information
Setting Properties for SP or CMM Clock
Suggested Resolutions for Network Connectivity Issues
Resolving Web Browser Security Settings
Modify Default Web Server Properties to Support Internet Explorer 6
Recommended Practice for Spanning Tree Configurations
Test IPv4 and IPv6 Connectivity
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
Setting SPARC Host KeySwitch 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
Reset Power to Service Processor or Chassis Monitoring Module
Backing Up, Restoring, or Resetting the Oracle ILOM Configuration
Maintaining x86 BIOS Configuration Parameters
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
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
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 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
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
Basic CLI Command Reference for Oracle ILOM 3.1
System Information and Management
Oracle ILOM Configuration Management
SNMP, IPMI, CIM, WS-MAN Protocol Management
About Simple Network Management Protocol
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)
Intelligent Platform Management Interface (IPMI)
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_ElementConformsToProfile
Oracle_EnabledLogicalElementCapabilities
Oracle_HWCompErrorOkIndication
Oracle_PhysicalAssetCapabilities
Oracle_PhysicalElementCapabilities
Feature Updates and Release Notes
Feature Enhancements as of Oracle ILOM 3.1
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
This example describes how to set up a typical DDNS configuration.
Assumptions:
The following assumptions apply to this DDNS configuration example:
There is a single server that handles both DNS and DHCP for the network on which the SP resides.
The SP network address is 192.168.1.0.
The DHCP/DNS server address is 192.168.1.2
The IP addresses from 192.168.1.100 to 192.168.1.199 are used as a pool to provide addresses to the SP and other clients.
The domain name is example.com.
There is no existing DNS or DHCP configuration in place. If there is, use the .conf files in this example as a guideline to update the existing configuration.
Note - How you set up DDNS depends on the infrastructure in use at your site. Oracle Solaris, Linux, and Microsoft Windows operating systems all support server solutions that offer DDNS functionality. This example configuration uses Debian r4.0 as the server operating system environment.
You can use the following steps and sample files provided here, with site-specific modifications, to set up your own DDNS configuration.
Installing the dnsutils package provides access to dig, nslookup, and other useful tools.
options { directory "/var/cache/bind"; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { any; }; }; // prime the server with knowledge of the root servers zone "." { type hint; file "/etc/bind/db.root"; }; // be authoritative for the localhost forward and reverse zones, // and for broadcast zones as per RFC 1912 zone "localhost" { type master; file "/etc/bind/db.local"; }; zone "127.in-addr.arpa" { type master; file "/etc/bind/db.127"; }; zone "0.in-addr.arpa" { type master; file "/etc/bind/db.0"; }; zone "255.in-addr.arpa" { type master; file "/etc/bind/db.255"; }; // additions to named.conf to support DDNS updates from dhcp server key server.example.com { algorithm HMAC-MD5; secret "your-key-from-step-2-here" }; zone "example.com" { type master; file "/etc/bind/db.example.com"; allow-update { key server.example.com; }; }; zone "1.168.192.in-addr.arpa" { type master; file "/etc/bind/db.example.rev"; allow-update { key server.example.com; }; };
Empty zone files should be named /etc/bind/db.example.com and /etc/bind/db.example.rev.
Copying the distribution supplied db.empty files is sufficient; they will be updated automatically by the DNS server.
ddns-update-style interim; ddns-updates on; server-identifier server; ddns-domainname "example.com."; ignore client-updates; key server.example.com { algorithm hmac-md5; secret your-key-from-step-2-here; } zone example.com. { primary 127.0.0.1; key server.example.com; } zone 1.168.192.in-addr.arpa. { primary 127.0.0.1; key server.example.com; } default-lease-time 600; max-lease-time 7200; authoritative; log-facility local7; subnet 192.168.1.0 netmask 255.255.255.0 { range 192.168.1.100 192.168.1.199; option domain-name-servers 192.168.1.2; }
Once the servers are running, any new Oracle ILOM SPs configured for DHCP will be automatically accessible using their host name when they are powered on. Use log files, dig, nslookup, and other utilities for debugging, if necessary.
For more information on the Linux DHCP and DNS servers used in this example, see the Internet Systems Consortium web site at: http://www.isc.org/