Sun: Nodes with Integrated Power Controllers
Intended for use with Cassatt Active Response Premium Edition and Data Center Edition V5.1.
This article describes how to set up Sun application nodes that use SPARC ALOM, X86 ILOM, and SPARC RSC integrated power controllers. Complete this step before adding nodes to the Cassatt Active Response Controller.
Step 1: Configure power controllers for DHCP
Select a power controller type from the following list, and complete the instructions in that section to configure DHCP and authentication.
SPARC ALOM power controllers (T2000)
Follow these steps to configure the SPARC ALOM power controllers for DHCP and authentication. The instructions provide steps for a T2000 power controller.
- Access the ALOM using the serial interface.
- Create a new user for the power controller with the Admin permission.
usershow
useradd <username>
userperm <username> cuar
userpassword <username>
- Enable the ethernet port for the power controller.
showsc
setsc if_network true
- Make sure the port is open for telnet.
setsc if_connection telnet
- Set DHCP to true.
setsc netsc_dhcp true
- Apply all changes.
resetsc
Are you sure you want to reset the SC [y/n]? y
top
Follow these steps to configure the X86 ILOM Sun-style power controllers for DHCP and authentication. The instructions provide steps for x4100 power controllers.
- Access the ILOM using the serial interface.
- Create a new user for the power controller. The default username is root; the default password is changeme.
create /SP/users/<username> password=<password> role=Administrator
Cassatt has found that the password must be at least 8 characters long, with at least two alphabetic characters, and at least one digit. For example, the following default password is valid: pc0ntr01. Other power controller syntax rules may apply for your particular power controller; check additional rules before creating a password.
- Navigate to the network settings directory.
cd /SP/network
ls
Targets:
Properties:
commitpending = (Cannot show property)
ipaddress = 10.0.119.200
ipdiscovery = static
ipgateway = 10.0.116.1
ipnetmask = 255.255.252.0
macaddress = 00:14:4F:6B:7A:2F
pendingipaddress = 10.0.119.200
pendingipdiscovery = static
pendingipgateway = 10.0.116.1
pendingipnetmask = 255.255.252.0
- Set "pendingipdiscovery" to DHCP.
set pendingipdiscovery=dhcp
- Save the changes.
set commitpending=true
Follow these steps to configure the X86 ILOM OEM-style power controllers for DHCP and authentication. The instructions provide steps for V20z power controllers.
- ILOMs must have an IP address before you can configure it for Cassatt Active Response. If you do not have a valid IP address, create a temporary one as follows: on the front panel of the ILOM, assign a static IP address and reboot the power controller.
- Telnet to the ILOM power controller.
- Create a new user for the power controller with Admin permissions:
SUNSPV20Z-1 $ access add user -g admin -p PASSWORD -u USERNAME
Cassatt has found that the password must be at least 8 characters long, with at least two alphabetic characters, and at least one digit. For example, the following default password is valid: pc0ntr01. Other power controller syntax rules may apply for your particular power controller; check additional rules before creating a password.
- Enable the 'lan' IPMI interface using the "IPMI Server Management" section of the Sun Fire V20z and Sun Fire V40z Servers Server Management Guide.
SUNSPV20Z-1 $ ipmi enable channel lan
Password:
Confirm password:
- Configure the power controller for auto discovery.
SUNSPV20Z-1 $ sp set hostname SUNSPV20z-1
Where: hostname = SUNSP<unique name>
- Configure the power controller for DHCP.
SUNSPV20Z-1 $ sp set ip dhcp
- While the ILOM tries to get a new IP address, the ssh session will be halted; to gracefully exit ssh, do the following:
<Enter>
Shift+ ~.
<Enter>
top
Follow these steps to configure RSC power controllers for Cassatt Active Response management. The instructions provide steps for the RSC 280R.
- Ensure that a static IP address is reserved for the power controller in the Cassatt Active Response UI.
- Verify that the RSC firmware is version 2.2.3 or later.
To download firmware version 2.2.3, see: http://www.sun.com/servers/rsc.html.
To upgrade from firmware version 2.2.2, you must install the 2.2.3 SUNWrsc package (which includes the firmware). For instructions to install the package and update the firmware, see:
http://www.sun.com/servers/rsc_download_readme.html.
- Access the rscadm utility located in: /usr/platform/<servertype>/rsc/rsc-config.
bash-3.00# cd /usr/platform/`uname -i`/rsc
bash-3.00# ls
- Start the rsc-config script.
bash-3.00# ./rsc-config
- Configure the RSC power controller as follows:
Setting |
Enter |
| Set RSC date/time now (y|n|?) |
y |
| Server Hostname [host0029]: |
Accept default |
| Edit customer info field (y|n|?) |
n |
| Enable RSC Ethernet Interface (y|n|s|?) |
y |
| RSC IP Mode (config|dhcp|?) |
config |
RSC IP Address []: 10.0.123.100
|
<reserved_static_IP_address> |
RSC IP Netmask [255.255.255.0]: 255.255.252.0
|
<netmask> |
| RSC IP Gateway []: 10.0.120.1 |
<gateway> |
| Enable RSC Alerts (y|n|s|?) |
n |
| Enable RSC Modem Interface (y|n|s|?) |
n |
| Enable RSC Serial Port Interface (y|n|s|?) |
n |
| Setup RSC User Account (y|n|?) |
y |
| Username [cassatt]: |
<username> |
| User Permissions (c,u,a,r|none|?)[cuar] |
Accept the default (cuar) |
- Set the power controller password when prompted in the script, and verify successfully completion of RSC set up.
Cassatt has found that the password must be at least 8 characters long, with at least two alphabetic characters, and at least one digit. For example, the following default password is valid: pc0ntr01. Other power controller syntax rules may apply for your particular power controller; check additional rules before creating a password.
- Telnet to the power controller and validate that you can log in with the user name and password.
top
SPARC nodes must be configured to boot from the network and enable DHCP. Cassatt recommends selecting IPMP whenever you specify more than one NIC as a hardware requirement for a tier that uses SUN nodes.
Note the following before starting:
RARP bootparams cannot be configured for SPARC application nodes; DHCP must be configured for all nodes that are connected to the Cassatt Active Response network.
The devalias command is used to verify that aliases are working on systems; nvalias is used for creating new aliases on systems. Do not use devalias to create aliases for SPARC application nodes under Cassatt Active Response power management; if you do, aliases are lost after a system reset or power cycle. Create permanent aliases using the nvalias command. For more information, see Chapter 3, Setting Configuration Variables, of the OpenBoot 3.x Command Reference Manual.
- Verify that the system NIC (whose MAC address is reported by OpenBoot during booting) is plugged into the network.
- Make sure the application node is plugged into a power outlet.
- Access the power controller interface.
For ALOM, use the serial console.
For RSC, use telnet.
- Apply power from the power controller to the host system.
<prompt> poweron
- Access the OpenBoot “ok” prompt.
For conserver terminal emulator program:
<prompt> Control-e cl1 (c, el, one)
OR
<prompt> break
<prompt> console
For a Sun keyboard: Stop-A
- Set the following OpenBoot parameters.
To view devices, use: devalias
To display all supported OpenBoot parameters, use: printenv
Set as follows... |
Example |
boot-device = <device>:DHCP |
ok setenv boot-device net:dhcp
boot-device = net0:dhcp |
boot-command = boot -r
|
ok setenv boot-command boot -r
boot-command = boot -r
The '-r' tells Solaris to rediscover its hardware on boot. |
auto-boot? = true |
ok setenv auto-boot? true
auto-boot? = true |
auto-boot-on-error? = true
(if available) |
ok setenv auto-boot-on-error? true
auto-boot? = true |
local-mac-address? = true
(if available) |
ok setenv local-mac-address? true
local-mac-address? = true |
network-boot-arguments = dhcp
(if available) |
ok setenv network-boot-arguments dhcp
network-boot-arguments = dhcp |
- If application nodes are Sun Opteron servers, disable the High Precision Event Timer (HPET) or application nodes will fail discovery, inventory, and diagnostics. For help, see Sun documentation.
- Check the boot NIC MAC address format.
Cassatt requires the boot NIC MAC address have 2 digits for every field. Sun MAC addresses often do not have leading zeroes; ensure the format is correct or Cassatt cannot manage the application node.Example:
Invalid format: 0:3:ba:47:8c:9b
Valid format: 00:03:ba:47:8c:9b
top
Was this article useful? Tell us what you think.
Email infocentral@cassatt.com.
. |