Configuring ILOM Communication Settings
|
Topics
|
Description
|
Links
|
Configure network settings
|
|
Configure Secure Shell settings
|
|
Configure the Local Interconnect Interface
|
|
Related Topics
|
For ILOM
|
Chapter or Section
|
Guide
|
|
- ILOM Network Configurations
|
Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide (820-6410)
|
|
- Connecting Your System to ILOM
|
Oracle Integrated Lights Out Manager (ILOM) 3.0 Getting Started Guide (820-5523)
|
|
- Configuring ILOM Communication Settings
|
Oracle Integrated Lights Out Manager (ILOM) 3.0 Web Interface Procedures Guide (820-6411)
|
|
- Configuring ILOM Communication Settings
|
Oracle Integrated Lights Out Manager (ILOM) 3.0 Management Protocols Reference Guide (820-6413)
|
The ILOM 3.0 Documentation Collection is available at: http://docs.sun.com/app/docs/prod/int.lights.mgr30#hic.
|
Configuring Network Settings
Topics
|
Description
|
Links
|
Platform Feature Support
|
Review the prerequisites
|
|
- x86 system server SP
- SPARC system server SP
- CMM
|
View and configure IPv4 network settings
|
|
Edit existing IPv4 addresses
|
|
View and configure dual-stack IPv4 and IPv4 network settings
|
|
Test IPv4 or IPv6 network configuration
|
|
Assign a host name and system identifier
|
|
- x86 system server SP
- SPARC system server SP
- CMM
|
View and configure DNS settings
|
|
View and configure serial port settings
|
|
Enable HTTP or HTTPS web access
|
|
Switch serial port output between the SP console and the host console
|
|
|
Before You Begin
Review the following information before you view or configure ILOM network settings.
Network Environment
|
Before You Begin
|
IPv4-only
|
- To configure network settings, you need the Admin (a) role enabled.
- Prior to configuring ILOM communication settings, ensure that the same IP address is always assigned to ILOM by either assigning a static IP address to ILOM after initial setup, or by configuring your DHCP server to always assign the same IP address to ILOM. This enables ILOM to be easily located on the network. By default, ILOM will attempt to obtain network settings using DHCP.
|
Dual-stack IPv4 and IPv6
|
- To configure or test network settings, you need the Admin (a) role enabled.
- Verify that your server or CMM has ILOM firmware 3.0.12 or later installed.
- Verify that support for the IPv6 configuration options in either your platform ILOM Supplement guide or platform Administration guide.
- Review the IPv6 enhancements identified in Chapter 2 of the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide (820-6410).
|
|
- ILOM supports a dual-mode TCP/IP stack and is shipped from the factory with both the IPv4 and IPv6 states enabled by default. If necessary, you can optionally disable the IPv6 network state. However, the IPv4 network state must always be enabled in order for ILOM to operate in an IPv4 network environment or in a dual-stack IPv4 and IPv6 network environment.
- ILOM supports static and DHCP network settings for both IPv4 and IPv6 network environments.
- For IPv6 Stateless auto-configurations, ILOM (3.0.12 or later) requires a network router to be configured for IPv6.
- For DHCPv6 auto-configuration options, ILOM (3.0.14 or later) requires a network DHCPv6 server to provide the IPv6 address(es) and DNS information for the device.
Note - DHCP and DHCPv6 are separate protocols. In a dual-stack network environment, DHCP and DHCPv6 operate as follows: (1) the DHCPv6 server can provide IPv6 addresses to a network node and the network node always uses the IPv6 protocol to communicate with a DHCPv6 server; and (2) the DHCP server can provide IPv4 addresses to a network node and the network node will always use the IPv4 protocol to communicate with a DHCP server
- For DHCP and DHCPv6 auto-configurations, you should choose to receive the DNS information from either an IPv6 DHCP server or from an IPv4 DHCP server, but not from both.
You can manually configure the settings for the DNS Name Server in ILOM under the Network DNS target. For instructions on specifying DNS information, see View and Configure DNS Settings.
|
Other network settings described in this section
|
- You need to have the Admin (a) role enabled to modify any server SP or CMM network properties or options.
|
View and Configure IPv4 Network Settings
|
Note - This procedure provides instructions for configuring ILOM to operate in an IPv4-only network environment, as is supported in ILOM 3.0.10 and earlier versions of ILOM. If you are configuring ILOM to operate in an dual-stack IPv4 and IPv6 network environment, see View and Configure Dual-Stack IPv4 and IPv6 Network Settings.
|
1. Log in to the ILOM SP CLI or the CMM CLI.
2. At the command prompt, type:
--> show /SP/network
3. Use the set command and type all of the settings that you wish to change.
You can execute these commands within a combined command. See Execute Combined Commands.
Note - Change a complete set of properties and commit to true only when the pending values are all typed into the command.
|
Note - Settings take effect as soon you set commitpending=true. Configuring network settings might disconnect your active session if you are connected to ILOM over a network. Configure all your systems before you commit the changes. After you commit the changes you will have to reconnect to ILOM.
|
Example
To change multiple network settings from DHCP to static assigned settings, type:
-> set /SP/network pendingipdiscovery=static pendingipaddress=nnn.nn.nn.nn pendingipgateway=nnn.nn.nn.nn pendingipnetmask=nnn.nn.nn.nn commitpending=true
Targets, Properties, and Values
The following target, properties, and values are valid for ILOM network settings.
TABLE 3-1 ILOM Target, Properties, and Values for Network Settings
Target
|
Property
|
Value
|
Default
|
/SP/network
|
ipaddress
ipdiscovery
ipgateway
ipnetmask
|
Read-only; values are updated by the system
|
|
|
macaddress
|
MAC address of ILOM
|
|
|
commitpending
pendingipaddress
pendingipdiscovery
pendingipgateway
pendingipnetmask
|
true|none
<ipaddress|none>
dhcp|static
<ipaddress|none>
<ipdotteddecimal>
|
none
none
dhcp
none
255.255.255.0
|
|
dhcp_server_ip
|
Read-only; value is updated when the SP receives a DHCP address
|
|
|
state
|
enabled|disabled
|
none
|
Edit Existing IPv4 Addresses in ILOM
|
1. Log in to the ILOM SP CLI or the CMM CLI.
2. Type one of the following commands to set the SP working directory:
- For a rackmount standalone server: cd /SP/network
- For a chassis server blade server module: cd /SP/network
- For a chassis CMM: cd /CMM/network
3. Type the show command to view the IP address assigned.
4. Type the following commands to change the existing settings.
Command
|
Description and Example
|
set pendingipaddress=<ipaddress>
|
Type this command followed by the static IP address that you want to assign to the server SP or CMM.
|
set pendingipnetmask=<ipnetmask>
|
Type this command followed by the static Netmask address that you want to assign to the server SP or CMM.
|
set pendingipgateway=<ipgateway>
|
Type this command followed by the static Gateway address that you want to assign to the server SP or CMM.
|
set pendingipdiscovery=<ipdiscovery>
|
Type this command to set a static IP address on the server SP or CMM.
|
set commitpending=true
|
Type this command to assign the network settings specified.
For example:
set pendingipaddress=129.144.82.26
set pendingipnetmask=255.255.255.0
set pendingipgateway=129.144.82.254
set pendingipdiscovery=static
set commitpending=true
|
Note - If you connected to ILOM through a remote SSH connection, the connection made to ILOM using the former IP address will timeout. Use the newly assigned settings to connect to ILOM.
|
View and Configure Dual-Stack IPv4 and IPv6 Network Settings
|
Note - This procedure provides instructions for configuring ILOM to operate in a dual-stack IPv4 and IPv6 network environment. If you are configuring ILOM to operate in an IPv4-only network environment, as is supported in ILOM 3.0.10 and earlier versions of ILOM, see View and Configure IPv4 Network Settings.
|
1. Log in to the ILOM SP CLI or the CMM CLI.
Establish a local serial console connection or SSH connection to the server SP or CMM.
2. Perform the network configuration instructions that apply to your network environment:
- To configure IPv4 network settings, perform Step 3 to Step 5 in this procedure.
- To configure IPv6 network settings, perform Step 6 to Step 10 in this procedure.
3. For IPv4 network configurations, use the cd command to navigate to the /x/network working directory for the device.
For example:
- For a rackmount server SP type: cd /SP/network
- For a chassis CMM type: cd /CMM/network
- For a chassis blade server SP type: cd /CH/BLn/network
- For a chassis blade server with multiple SP nodes type:
cd /CH/BLn/Noden/network
4. Type the show command to view the configured IPv4 network settings configured on the device.
5. To set IPv4 network settings for DHCP or static, perform one of the following:
- To configure DHCP IPv4 network settings, set values for the following properties:
Property
|
Set Property Value
|
Description
|
state
|
set state=enabled
|
The network state is enabled by default for IPv4.
Note - To enable the DHCP network option for IPv4 the state must be set to enabled.
|
pendingipdiscovery
|
set pendingipdiscovery=dhcp
|
The property value for ipdiscovery is set to dhcp by default for IPv4.
Note - If the dhcp default property value was changed to static, you will need to set the property value to dhcp.
|
commitpending=
|
set commitpending=true
|
Type set commitpending=true to commit the changes made to the state and ipdiscovery property values.
|
- To configure static IPv4 network settings, set values for the following properties:
Property
|
Set Property Value
|
Description
|
state
|
set state=enabled
|
The network state is enabled by default for IPv4.
Note - To enable the static IPv4 network option the state must be set to enabled.
|
pendingipdiscovery
|
set pendingipdiscovery=static
|
To enable a static IPv4 network configuration, you need to set the pendingipdiscovery property value to static.
Note - The property value for ipdiscovery is set to dhcp by default for IPv4.
|
pendingipaddress
pendingipnetmask
pendingipgateway
|
set pendingipaddress=<ip_address> pendingipnetmask=<netmask> pendingipgateway=<gateway>
|
To assign multiple static network settings, type the set command followed by the pending command for the each property value (IP address, netmask, and gateway), then type the static value that you want to assign.
|
commitpending=
|
set commitpending=true
|
Type set commitpending=true to commit the changes madeto the IPv4 network properties.
|
6. For IPv6 network configurations, use the cd command to navigate to the /x/network/ipv6 working directory for the device.
For example:
- For a rackmount server SP type: cd /SP/network/ipv6
- For a chassis CMM type: cd /CMM/network/ipv6
- For a chassis blade server SP type: cd /CH/BLn/network/ipv6
- For a chassis blade server with multiple SP nodes type:
cd /CH/BLn/Noden/network/ipv6
7. Type the show command to view the configured IPv6 network settings configured on the device.
For example, see the following sample output values for the IPv6 properties on a server SP device.
-> show
/SP/network/ipv6
Targets:
Properties:
state = enabled
autoconfig = stateless
dhcpv6_server_duid = (none)
link_local_ipaddress = fe80::214:4fff:feca:5f7e/64
static_ipaddress = ::/128
ipgateway = fe80::211:5dff:febe:5000/128
pending_static_ipaddress = ::/128
dynamic_ipaddress_1 = fec0:a:8:b7:214:4fff:feca:5f7e/64
Commands:
cd
show
|
Note - When the autoconfig= property is set to dhcpv6_stateful or dhcpv6_stateless, the read-only property for dhcpv6_server_duid will identify the DHCP Unique ID of the DHCPv6 server that was last used by ILOM to retrieve the DHCP information.
|
Note - The default IPv6 autoconfig property value provided in ILOM 3.0.14 (and later) is autoconfig=stateless. However, if you have ILOM 3.0.12 installed on your CMM or server, the default property value for autoconfig appears as autoconfig=stateless_only.
|
8. To configure an IPv6 auto-configuration option, use the set command to specify the following auto-configuration property values.
Property
|
Set Property Value
|
Description
|
state
|
set state=enabled
|
The IPv6 network state is enabled by default. To enable an IPv6 auto-configuration option this state must be set to enabled.
|
autoconfig
|
set autoconfig=<value>
|
Specify this command followed by the autoconf value you want to set.
Options include:
- stateless (default setting provided in ILOM 3.0.14 or later)
or
stateless_only (default setting provided in ILOM 3.0.12)
Automatically assigns IP address learned from the IPv6 network router.
- dhcpv6_stateless
Automatically assigns DNS information learned from the DHCP server.
The dhcpv6_stateless property value is available in ILOM as of 3.0.14.
- dhcpv6_stateful
Automatically assigns the IPv6 address learned from the DHCPv6 server.
The dhcpv6_stateful property value is available in ILOM as of 3.0.14.
- disable
Disables all auto-configuration property values and sets the read-only property value for link local address.
|
Note - The IPv6 configuration options take affect after they are set. You do not need to commit these changes under the /network target.
|
Note - IPv6 auto-configuration addresses learned for the device will not affect any of the active ILOM sessions to the device. You can verify the newly learned auto-configured addresses under the /network/ipv6 target.
|
Note - As of ILOM 3.0.14 or later, you can enable the stateless auto-configuration option to run at the same time as when the option for dhcpv6_stateless is enabled or as when the option for dhcpv6_stateful is enabled. However, the auto-configuration options for dhcpv6_stateless and dhcpv6_stateful should not be enabled to run at the same time.
|
9. Perform the following steps to set a static IPv6 address:
a. To set a pending static IPv6 address, specify the following property values:
Property
|
Set Property Value
|
Description
|
state
|
set state=enabled
|
The IPv6 network state is enabled by default. To enable a static IP address this state must be set to enabled.
|
pendingipaddress
|
set pending_static_ipaddress=<ip6_address>/<subnet mask length in bits>
|
Type this command followed by the property value for the static IPv6 address and net mask that you want to assign to the device.
IPv6 address example:
fec0:a:8:b7:214:4fff:feca:5f7e/64
|
b. To commit (save) the pending IPv6 static network parameters, perform the steps in the following table:
Step
|
Description
|
1
|
Use the cd command to change the directory to the device network target.
For example:
- For rackmount server type: cd /SP/network
- For chassis CMM type: cd /CMM/network
- For chassis blade server SP type: cd /CH/BLn/network
- For chassis blade server SP with multiple nodes type:
cd /CH/BLn/Noden/network
|
2
|
Type the following command to commit the changed property values for IPv6:
set commitpending=true
|
Note - Assigning a new static IP address to the device (SP or CMM) will end all active ILOM sessions to the device. To log back in to ILOM, you will need to create a new browser session using the newly assigned IP address.
|
10. To test the IPv4 or IPv6 network configuration from ILOM use the Network Test Tools (Ping and Ping6). For details, see Test IPv4 or IPv6 Network Configuration.
Test IPv4 or IPv6 Network Configuration
|
1. Log in to the ILOM SP CLI or the CMM CLI.
Establish a local serial console connection or SSH connection to the server SP or CMM
2. Use the cd command to navigate to the /x/network/test working directory for the device, for example:
- For a rackmount server SP type: cd /SP/network/test
- For a chassis CMM type: cd /CMM/network/test
- For a chassis blade server SP type: cd /CH/BLn/network/test
- For a chassis blade server with multiple SP nodes type:
cd /CH/BLn/Noden/network/test
3. Type the show command to view the network test targets and properties.
For example, see the following output the shows the test target properties on a CMM device.
-> show
/CMM/network/test
Targets:
Properties:
ping = (Cannot show property)
ping6 = (Cannot show property)
Commands:
cd
set
show
|
4. Use the set ping or set ping6 command to send a network test from the device to a specified network destination.
Property
|
Set Property Value
|
Description
|
ping
|
set ping=<IPv4_address>
|
Type the set ping= command at the command prompt followed by the IPv4 test destination address.
For example:
-> set ping=10.8.183.106
Ping of 10.8.183.106 succeeded
|
ping6
|
set ping6=<IPv6_address>
|
Type the set ping6= command followed by the IPv6 test destination address.
For example:
-> set ping6=fe80::211:5dff:febe:5000
Ping of fe80::211:5dff:febe:5000 succeeded
|
Assign Host Name and System Identifier
|
1. Log in to the ILOM SP CLI or the CMM CLI.
2. To set the SP host name and system identifier text, at the command prompt, type:
-> set /SP hostname=text_string
-> set /SP system_identifier=text_string
Where:
- The host name can consist of alphanumeric characters and can include hyphens. Host names can contain up to 60 characters.
- The system identifier can consist of a text string using any standard keyboard keys except quotation marks.
For example:
-> set /SP hostname=Lab2-System1
-> set /SP system_identifier=DocSystemforTesting
With these settings, the show command produces the following output:
-> show /SP
/SP
Targets:
alertmgmt
.
.
.
users
Properties:
check_physical_presence = false
hostname = Lab2-System1
system_contact = (none)
system_description = SUN BLADE X8400 SERVER MODULE, ILOM v3.0.0.0, r31470
system_identifier = DocSystemforTesting
system_location = (none)
Commands:
cd
reset
set
show
version
|
View and Configure DNS Settings
|
1. Log in to the ILOM SP CLI or the CMM CLI.
2. At the command prompt type the following command to display settings for the external serial port:
-> cd /SP/clients/dns
3. Use the set command to change properties and values for DNS settings. At the command prompt type:
-> set /SP/clients/dns [propertyname=value]
For example:
-> set /SP/clients/dns searchpath=abcdefg.com
Targets, Properties, and Values
The following targets, properties, and values are valid for DNS settings.
TABLE 3-2 Valid Targets, Properties, and Values for DNS Settings
Target
|
Property
|
Value
|
Default
|
/SP/clients/dns
|
auto_dns
nameserver
retries
searchpath
timeout
|
enabled|disabled
ip_address
Integer between 0 and 4
Integer between 1 and 10
Up to six comma-separated search suffixes
|
disabled
|
View and Configure Serial Port Settings
|
1. Log in to the ILOM SP CLI or the CMM CLI.
2. At the command prompt:
- Type the following command to display settings for the external serial port:
-> show /SP/serial/external
- Type the following command to display settings for the host serial port:
-> show /SP/serial/host
3. Use the set command to change properties and values for serial port settings. Port settings have two sets of properties: pending and active. At the command prompt type:
-> set target [propertyname=value] commitpending=true
Example
To change the speed (baud rate) for the host serial port from 9600 to 57600, type the following:
-> set /SP/serial/host pendingspeed=57600 commitpending=true
-> set /SP/serial/external pendingspeed=57600 commitpending=true
Note - On x86-based systems, the speed of the host serial port must match the speed setting for serial port 0, COM1, or /dev/ttys0 on the host operating system for ILOM to communicate properly with the host.
|
Targets, Properties, and Values
The following targets, properties, and values are valid for ILOM serial port settings.
TABLE 3-3 Valid Targets, Properties, and Values for ILOM Serial Port Settings
Target
|
Property
|
Value
|
Default
|
/SP/serial/external
|
commitpending
flowcontrol
pendingspeed
|
true|(none)
software
<integer>
|
(none)
software
9600
|
|
speed
|
Read-only value; configured via the pendingspeed property
|
|
/SP/serial/host
|
commitpending
pendingspeed
|
true|(none)
<integer>
|
(none)
(none)
|
|
speed
|
Read-only value; configured via the pendingspeed property
|
|
Enable HTTP or HTTPS Web Access
|
1. Log in to the ILOM SP CLI or the CMM CLI.
2. At the command prompt, type:
-> set /SP/services/http [propertyname=value]
The properties are located in /SP/services/http and /SP/services/https.
Targets, Properties, and Values
TABLE 3-4 shows the valid targets, properties, and values for HTTP and HTTPS connections.
TABLE 3-4 Valid Targets, Properties, and Values for HTTP and HTTPS Connections
Target
|
Property
|
Value
|
Default
|
/SP/services/http
|
secureredirect
|
enabled|
disabled
|
enabled
|
|
servicestate
|
enabled|
disabled
|
disabled
|
|
port
|
<portnum>
|
80
|
/SP/services/https
|
servicestate
|
enabled|
disabled
|
enabled
|
|
port
|
<portnum>
|
443
|
TABLE 3-5 lists the possible settings for HTTP, HTTPS, and automatic redirect.
TABLE 3-5 Possible Settings for HTTP, HTTPS, and Automatic Redirect
Desired State
|
Target
|
Property
|
Value
|
Enable HTTP only
|
/SP/services/http
|
secureredirect
|
disabled
|
|
/SP/services/http
|
servicestate
|
enabled
|
|
/SP/services/https
|
servicestate
|
disabled
|
Enable HTTP and HTTPS
|
/SP/services/http
|
secureredirect
|
disabled
|
|
/SP/services/http
|
servicestate
|
enabled
|
|
/SP/services/https
|
servicestate
|
enabled
|
Enable HTTPS only
|
/SP/services/http
|
secureredirect
|
disabled
|
|
/SP/services/http
|
servicestate
|
disabled
|
|
/SP/services/https
|
servicestate
|
enabled
|
Automatically redirect HTTP to HTTPS
|
/SP/services/http
/SP/services/http
/SP/services/https
|
secureredirect
servicestate
servicestate
|
enabled
disabled
enabled
|
Switch Serial Port Output
|
Note - To determine whether serial port sharing is supported for your server, refer to the platform ILOM Supplement guide or platform Administration guide provided for your server.
|
|
Caution - You should set up the network on the SP before attempting to switch the serial port owner to the host server. If a network is not set up, and you switch the serial port owner to the host server, you will be unable to connect using the CLI or web interface to change the serial port owner back to the SP. To return the serial port owner setting to the SP, you will need to restore access to the serial port on the server.For more details about restoring access to the server port on your server, see the platform documentation supplied with your server.
|
1. Log in to the ILOM SP CLI.
2. To set the serial port owner, type:
-> set /SP/serial/portsharing /owner=host
Note - The serial port sharing value by default is owner=SP.
|
3. Use a dongle or multi-port cable to connect a serial host to the server.
For details on how to use aattach devices to the server, see the platform installation documentation supplied with your server.
Configuring Secure Shell Settings
Topics
|
Description
|
Links
|
Platform Feature Support
|
Configure Secure Shell settings
|
|
- x86 system server SP
- SPARC system server SP
- CMM
|
Before You Begin
- To configure Secure Shell (SSH) settings, you need the Admin (a) role enabled.
Establish a Secure Remote SSH Connection
|
You will need to establish a secure connection from a remote SSH client to the server SP. To establish a secure connection, type the following:
$ ssh -l username server_ipaddress
Password: ********
The default CLI prompt appears and the system is ready for you to run the CLI commands to establish network settings.
Enable or Disable SSH
|
Note - SSH is enabled by default in ILOM.
|
Follow these steps to enable or disable SSH:
1. Log in to the ILOM SP CLI or the CMM CLI.
2. If you do not want to provide access over the network, or if you do not want to use SSH, type the following:
-> set /SP/services/ssh state=enabled | disabled
View the Current Key
|
Note - All of the properties below /SP/services/ssh/keys/rsa|dsa are read only. To view the key, you need the Read Only (o) role enabled.
|
Follow one of these steps to view the current key:
To view the RSA key, type:
-> show /SP/services/ssh/keys/rsa
For example:
/SP/services/ssh/keys/rsa
Targets:
Properties:
fingerprint = ca:c0:05:ff:b7:75:15:a0:30:df:1b:a1:76:bd:fe:e5
length = 1024
publickey
AAAAB3NzaC1yc2EAAAABIwAAAIEAthvlqgXbPIxN4OEvkukKupdFPr8GDaOsKGg
BESVlnny4nX8yd8JC/hrw3qDHmXIZ8JAFwoLQgjtZCbEsgpn9nNIMb6nSfu6Y1t
TtUZXSGFBZ48ROmU0SqqfR3i3bgDUR0siphlpgV6Yu0Zd1h3549wQ+RWk3vxqHQ
Ffzhv9c=
Commands:
cd
show
|
To view the DSA key, type:
-> show /SP/services/ssh/keys/dsa
For example:
/SP/services/ssh/keys/dsa
Targets:
Properties:
fingerprint = 6a:90:c7:37:89:e6:73:23:45:ff:d6:8e:e7:57:2a:60
length = 1024
publickey =
AAAAB3NzaC1kc3MAAACBAInrYecNH86imBbUqE+3FoUfm/fei2ZZtQzqrMx5zBm
bHFIaFdRQKeoQ7gqjc9jQbO7ajLxwk2vZzkg3ntnmqHz/hwHvdho2KaolBtAFGc
fLIdzGVxi4I3phVb6anmTlbqI2AILAa7JvQ8dEGbyATYR9A/pf5VTac/TQ70O/J
AAAAFQCIUavkex7wtEhC0CH3s25ON0I3CwAAAIBNfHUop6ZN7i46ZuQOKhD7Mkj
gdHy+8MTBkupVfXqfRE9Zw9yrBZCNsoD8XEeIeyP+puO5k5dJvkzqSqrTVoAXyY
qewyZMFE7stutugw/XEmyjq+XqBWaiOAQskdiMVnHa3MSg8PKJyWP8eIMxD3rIu
PTzkV632uBxzwSwfAQAAAIAtA8/3odDJUprnxLgHTowc8ksGBj/wJDgPfpGGJHB
B1FDBMhSsRbwh6Z+s/gAf1f+S67HJBTUPsVSMz+czmamc1oZeOazT4+zeNG6uCl
u/5/JmJSdkguc1FcoxtBFqfO/fKjyR0ecWaU7L4kjvWoSsydHJ0pMHasEecEBEr
lg==
Commands:
cd
show
|
Generate a New SSH Key
|
Follow these steps to generate a new SSH key:
1. Log in to the ILOM SP CLI or the CMM CLI.
2. Set the key type by typing the following:
-> set /SP/services/ssh generate_new_key_type=dsa|rsa
3. Set the action to true.
-> set /SP/services/ssh generate_new_key_action=true
The fingerprint and key will look different. The new key will take effect immediately for new connections.
Restart the SSH Server
|
Note - Restarting the SSH server will end any existing SSH connections.
|
Follow these steps to restart the SSH server:
1. Log in to the ILOM SP CLI or the CMM CLI.
2. To restart the SSH server, type the following:
-> set /SP/services/ssh restart_sshd_action=true
Configuring the Local Interconnect Interface
Topics
|
Description
|
Links
|
Platform Feature Support
|
Review the prerequisites
|
|
- x86 system server SP
- SPARC system server SP
|
Configure the Local Interconnect Interface
|
|
Before You Begin
The following requirements must be met before performing the procedures described in this section for configuring the Local Interconnect Interface in ILOM.
- Review the concepts describing the use of a Local Interconnect Interface between the ILOM SP and the host OS. For details, see “Local Interconnect Interface: Local Connection to ILOM From Host Operating System” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- Review the ILOM descriptions for the Local Host Interconnect configuration settings. For details, see “Local Host Interconnect Configuration Settings in ILOM” in the Oracle Integrated Lights Out Manager (ILOM) 3.0 Concepts Guide.
- Verify that your server is running ILOM 3.0.12 or a later version of ILOM.
- Verify that your platform supports the Local Interconnect Interface. Refer to your platform server ILOM Supplement guide or Administration guide.
Note - The settings in ILOM for the Local Interconnect Interface are not supported on the CMM.
|
- Automatic configuration of the Local Interconnect Interface requires the Host Managed (hostmanaged) setting in ILOM to be enabled (set to True), as well as the installation of the Oracle Hardware Management Pack 2.1.0 or later software on the server. For more information about installing the Oracle Hardware Management Pack 2.1.0 software, see the Oracle Server Hardware Management Pack User’s Guide (821-1609).
- Manual configuration of the Local Interconnect Interface between the ILOM SP and the host operating system requires the Host Managed (hostmanaged) setting in ILOM to be disabled (set to False), as well as other configuration settings to be set on the host operating system.
For guidelines for configuring the host OS connection point on the Local Interconnect Interface, see Manual Host OS Configuration Guidelines for Local Interconnect Interface.
- The host operating system must support the internal USB Ethernet device that is presented from the ILOM SP. Therefore, prior to configuring the Local Interconnect Interface in ILOM, you should verify that an internal USB Ethernet device driver was included in the operating system distribution and installed on your server. If an internal USB Ethernet device driver was not installed by the operating system distribution, you can obtain the device driver for your operating system from the Oracle Hardware Management Pack 2.1.0 software. For more details, see the Oracle Server Hardware Management Pack User’s Guide (821-1609).
- Network parameter changes to the settings in ILOM for the Local Interconnect Interface are considered pending until you commit the changes in the ILOM. For example, in the ILOM CLI, you must issue the commitpending=true command to save the pendingipaddress and the pendingipnetmask under the network/interconnect target. In the ILOM web interface, network parameter changes entered on the Configure USB Ethernet Parameters dialog are committed after clicking Save.
- An ILOM user account with Administrator (a) role privileges is required in order to change any of the settings in ILOM for the Local Interconnect Interface.
- To determine the operating systems supported on your server, refer to the platform server installation guide or operating system guide(s).
Configure the Local Interconnect Interface
|
1. Log in to the ILOM SP CLI.
Establish a local serial console connection or SSH connection to the server SP or CMM
2. Use the cd command to navigate to the /x/network/interconnect working directory for the server.
For example:
- For a rackmount server SP type: cd /SP/network/interconnect
- For a chassis blade server SP type: cd /CH/BLn/network/interconnect
3. Type the show command to view the network interconnect targets and properties.
Example outputs:
- hostmanaged property under the network/interconnect property is set to true. In this configuration example, the host managed state is enabled for auto-configuration by the Oracle Hardware Management Pack 2.1.0 or later software.
-> show
/SP/network/interconnect
Targets:
Properties:
hostmanaged = true
type = USB Ethernet
ipaddress = 169.254.182.76
ipnetmask = 255.255.255.0
spmacaddress = 02:21:28:57:47:16
hostmacaddress = 02:21:28:57:47:17
Commands:
cd
set
show
|
- hostmanaged property under the network/interconnect property is set to false. In this configuration example, the host managed state is disabled allowing you to manually configure the ILOM SP and host OS connection points on the Local Interconnect Interface.
-> show
/SP/network/interconnect
Targets:
Properties:
hostmanaged = false
state = enabled
type = USB Ethernet
ipaddress = 169.254.182.76
ipnetmask = 255.255.255.0
spmacaddress = 02:21:28:57:47:16
hostmacaddress = 02:21:28:57:47:17
pendingipaddress = 169.254.182.76
pendingipnetmask = 255.255.255.0
commitpending = (Cannot show property)
Commands:
cd
set
show
|
4. To configure the assignment of the non-routable IPv4 addresses to the connection points on the Local Interconnect Interface, you can choose to:
- Automatically assign non-routable IPv4 addresses to each connection point on the Local Interconnect Interface by setting the hostmanaged property to true.
-> set hostmanaged=true
When you set the hostmanaged property to true, you must also install the Oracle Hardware Management Pack 2.1.0 (or later) software on your server and accept the installation default for enabling Local ILOM Interconnect. For more information, see the section about configuring the Local ILOM Interconnect in the Oracle Server Hardware Management Pack User’s Guide (821-1609).
- or-
- Manually assign non-routable IPv4 addresses to each connection point on the Local Interconnect Interface by setting the hostmanaged property to false.
-> set hostmanaged=false
When you set the hostmanaged property to false, you must also manually set the values for the following /network/interconnect properties.
Property
|
Set Property Value
|
Description
|
state
|
set state=enabled
|
Type set state=enabled to manually enable the Local Interconnect Interface between the ILOM SP and host OS.
The state property under the interconnect target is disabled by default.
|
pendingipaddress
|
set pendingipaddress=169.254.182.76
|
ILOM, by default, provides a non-routable IPv4 address for the ILOM SP connection point on the Local Interconnect Interface.
This default IPv4 address (169.254.182.76) should not be changed unless a conflict exists on the host OS with this IPv4 address.
To change the default IPv4 address, type the set pendingipaddress= command followed by the internal IPv4 address that you want to assign to the ILOM SP connection point on the Local Interconnect Interface.
|
pendingipnetmask
|
set pendingipnetmask=255.255.255.0
|
ILOM, by default, provides an IPv4 Netmask address for the ILOM SP connection point on the Local Interconnect Interface.
This default IPv4 Netmask (255.255.255.0) address should not be changed unless a conflict exists in your network environment with this address.
To change the default Netmask address, type the set pendingipnetmask= command follow by the internal IPv4 Netmask that you want to assign to the ILOM SP connection point on the Local Interconnect Interface.
|
commitpending
|
set commitpending=<value>
|
Changes under the network/interconnect target for both pendingipaddress and pendingipnetmask are considered pending until they are committed.
To commit the changes, type:
set commitpending=true
To cancel the changes, type:
set commitpending=false
|
For additional information about the values required for the manual local host interconnect configuration properties, type help. For example:
-> help hostmanaged
-> help state
-> help pendingipaddresss
->help pendingipnetmask
->help commitpending
For additional information about the read-only properties, type:
-> help type
-> help ipaddress
-> help ipnetmask
-> help spmacaddress
-> help hostmacaddress
If you chose to manually configure the Local Interconnect Interface in ILOM without the use of the Oracle Hardware Management Pack 2.1.0 software, you will need to perform some additional configuration on the host operating system. For general details about these additional host OS configuration settings, see Manual Host OS Configuration Guidelines for Local Interconnect Interface.
Note - To prevent the Oracle Hardware Management Pack software from auto-configuring the connection points on the Local Interconnect Interface, the hostmanaged property value must be set to False. To prevent the use of Local Interconnect Interface between the ILOM SP and the host OS, the state property value must be set to disabled and the hostmanaged property value must be set to False.
|
Oracle Integrated Lights Out Manager (ILOM) 3.0 CLI Procedures Guide
|
820-6412-12
|
|
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.