Application Node Setup: Virtual Power Controllers
Intended for use with Cassatt Active Response V5.0.
Application nodes are servers that Cassatt Active Response deploys into tiers to run your business applications. This article describes how set up and configure application nodes (SPARC or Intel) without power controller. Tasks include:
- Cable hardware
- Configure application nodes
- Create and discover virtual power controller
- Add and discover application nodes
Prerequisites
Before starting tasks in this document, review the requirements for completing the tasks:
Step 1: Cable hardware
Using one of the following cabling diagrams (dual or a single control node configuration) cable application nodes to the network switches.
If the first NIC in the application node is not going to be managed by Cassatt Active Response, make sure it is unplugged or plugged into its appropriate network.
top
Step 2: Configure application nodes
Using the Intel or SPARC instructions in this section, configure application nodes to boot from the network and enable DHCP.
Intel
Follow these steps to configure boot order and enable PXE booting (which enables DHCP) for Intel-based application nodes. Steps and settings will vary according to the BIOS and network configuration utilities on your application node hardware.
- Verify that application nodes are plugged in, but powered off.
- Connect a console, keyboard, and mouse to the application node.
- Power on the application node.
- Access the BIOS setup program and configure as follows.
For this BIOS setting... |
Set as follows... |
Ethernet interfaces |
Enabled. |
PXE |
Enable ethernet interfaces to PXE boot (which enables DHCP). |
Boot order |
Set network to be first in the boot order.
WARNING: “Network” must come before the “Hard drive” option in the boot order or the node will not boot. If you place “Network” first in the boot order, you gain a small optimization in speed for node discovery and in moving nodes to the free pool. If you are operating in a test environment or you expect to need frequent administrative access to the application nodes, you can set the order to Floppy, CD-ROM, Network. |
Other |
Set other BIOS settings as required by your site, making sure they do not conflict with Cassatt Active Response settings. |
SPARC
Follow these steps to configure SPARC application 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.
- Power on the application node.
- Access the application node via the serial console.
To display all supported OpenBoot parameters, use the printenv command.
- Access the OpenBoot “ok” prompt.
For conserver terminal emulator program: Control-e cl1 (c, el, one).
For a Sun keyboard: Stop-A
- Use the devalias command to view devices:
ok devalias
- Set the following OpenBoot parameters.
For this OpenBoot setting... |
Set as follows... |
boot-device to use DHCP |
ok setenv boot-device net1:dhcp
boot-device = net1:dhcp |
boot-command |
ok setenv boot-command boot -r
boot-command = boot -r |
auto-boot? |
ok setenv auto-boot? true
auto-boot? = true |
auto-boot-on-error
(if available) |
ok setenv auto-boot-on-error? true
auto-boot? = true |
local-mac-address
(if available) |
ok setenv local-mac-address? true
local-mac-address? = true |
network-boot-arguments
(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 instructions, see: http://www.sun.com/products-n-solutions/hardware/docs/pdf/819-1771-21.pdf.
top
Step 3: Create and discover virtual power controllers
Follow these steps to create the virtual power controllers in the Controller.
Prerequisites:
- A MAC address for virtual power controller
- Name of network where the virtual power controller resides
- If you are adding a number of virtual power controllers, you can save time by importing them in a comma-separated file. For details, see Configuration files.
- Log into the Controller.
- Go to: Discovered Pool > Power Controllers > New Power Controller.
- In the wizard, specify "Virtual" for Type.
- On the Power Controller page, verify that Cassatt Active Response has finished discovering the virtual power controller.
top
Step 4: Add and discover application nodes
Follow these steps to add application nodes to an associated the virtual power controller.
Prerequisites:
- Virtual power controller name
- MAC address of the application node
- Go to: Discovered Pool > Power Controllers.
- Click the appropriate virtual power controller link.
- Select Nodes > Associated Nodes > Add Nodes and complete the page.
- On the Nodes list, verify that nodes are discovered.
During booting, some Sun systems with gigabit cards may display the following alert. This is normal; booting will eventually start.
Boot device: /pci@1f,700000/network@2:dhcp File and args: -r 1000 Mbps FDX Link up Timed out waiting for BOOTP/DHCP reply Timed out waiting for BOOT/DHCP reply Timed out waiting for BOOT/DHCP reply 1000 Mbps FDX Link up.
To troubleshoot discovery and inventory, see Alternatives to Power Controllers: Virtual Power Controllers.
top
Was this article useful? Tell us what you think.
Email infocentral@cassatt.com.
. |
