C H A P T E R 3 |
Preparing the Sun Fire B10n Content Load Balancing Blade for Load Balancing |
To prepare the Sun Fire B10n content load balancing blade for load balancing, you must first configure the blade servers, then set up the content load balancing blade. This chapter describes the procedures for preparing the blade servers for load balancing.
This chapter includes the following sections:
The Sun Fire B10n software includes the following components:
See Software Architecture to understand the different software components.
The procedures for downloading both the blade server module software and the B10n application software as well as the firmware on the Sun Fire B10n content load balancing blade involve downloading the software to your TFTP server.
If you are updating the blade server module before downloading the software, check the blade server module software version.
1. At the sc prompt enter the following command:
sc> console Sn |
Where S indicates the slot and n is the number of the slot containing the blade you want to access. Valid slot numbers range from 0 to 15.
2. At the Solaris root prompt, check the module information:
# modinfo | grep clbmod |
The following example checks the blade server module software of the blade in slot 10:
sc> console s10 Connected with input enabled on fru S10 Escape Sequence is '#.'(#.) |
The ifnormation shows that software version 1.34 is currently installed.
# modinfo | grep clbmod 213 78160000 d18f 21 1 clbmod (Server CLB module v1.34) |
1. To down load the latest software, go to the following site and select Sun Fire B10n:
http://wwws.sun.com/software/download/network.html
# /usr/bin/unzip SunFire_B10n-1_0.zip |
3. Install the blade server module software packages:
# cd path_to_unzipped_file/Solaris_8/Packages # pkgadd -d . |
Step 3 shows an example of a Solaris blade server module.
You will see a message similar the following:
4. Press return to install all the packages.
5. Install the blade server module on each blade server.
The blade server module must be installed on each blade server individually. You can install the packages from the blade server to the TFTP server.
6. Configure the management IP address to the server interface:
# /usr/sbin/ifconfig ce0 plumb ip_address netmask netmask up |
7. To configure interfaces to remain across reboots, add the interfaces to /etc/opt/SUNWclb/clb.conf placing each interface on a separate line to be configured at start up. Or run the clbctl script after creating the file and adding the interfaces.
# /etc/init.d/clbctl start |
Following is a sample configuration file:
8. Configure the virtual IP addresses (VIPs) that this server supports:
# ifconfig virtual loopback interface plumb vip netmask netmask up |
You must configure the virtual IP address of the service being load balanced. If it is not configured, the stack will not recognize the destination address in the incoming IP packets and will reject packets received for that destination address. Configure the virtual IP address on the loop back interface as a logical IP address. Using the loop back interface prevents responses to incoming ARP request broadcasts for the virtual IP address. Use different loop back instances for different virtual IP addresses.
For example if the server supports VIP 192.50.50.1, you would type the following:
# ifconfig lo0:1 plumb 192.50.50.1 netmask 255.255.255.0 up |
To make the content load balancing blade functional, you must first set it up. Once you are at the B10n prompt, you can get help by doing either of the following:
At the B10n prompt, type the following command:
puma# help command_name |
At the B10n prompt, type a question mark:
puma# service ? |
1. Connect your telnet console with a Sun Fire B1600 blade system chassis serial port.
2. Telnet into the system controller (sc):
% telnet sc ip_addr |
Where ip_addr is the IP address of the system controller.
3. To poweron a single content load balancing blade, type the following:
sc> poweron Sn |
Where S indicates the slot and n is the number of the slot containing the blade you want to power on.
If you are powering on more than one blade, list the slot number for each blade you are powering on. See Powering On Content Load Balancing Blades.
4. Access the console for the blade:
sc> console Sn |
5. Login as admin to access the command line interface:
puma# Login:admin Password:admin puma{admin}# |
Note - The default login and password for the administrator is admin. To ensure the security of the configuration, change the default password before you continue. The new password must have at least six characters. See User Access for more information. |
6. Change the default password:
puma{admin}# password admin Enter new password: new admin secret password Confirm new password: new admin secret password |
puma{admin}# config puma(config){admin}# |
puma(config){admin}# ip interface 0 ip-addr mask net-mask |
This command sets up the iq0 on your content load balancing blade, that is the interface connected to switch SSC0 (in slot 0).
Note - The switch number, for example SSC0, corresponds to the slot where the blade server resides. |
The following example sets the IP address on interface 0 at 192.50.50.134:
puma(config){admin}# ip interface 0 192.50.50.134 mask 255.255.255.0 |
Each Sun Fire B10n content load balancing blade has two interfaces. Alternatively, you could configure the second interface as follows:
puma(config){admin}# ip interface 1 ip-addr mask net-mask |
This alternative configuration sets up the iq1 on your content load balancing blade, that is the interface connected to switch SSC1 (in slot 1).
The following example sets the IP address on interface 1 at 192.50.50.135:
puma(config){admin}# ip interface 1 192.50.50.135 mask 255.255.255.0 |
9. Verify that the interface is working:
puma(config){admin}# ping remote-ip-addr |
The following example pings the remote IP address at 192.50.50.200:
puma(config){admin}# ping 192.50.50.200 |
Note - Ensure that the remote-ip-addr is reachable from the Sun Fire B10n content load balancing blade before you complete the basic configuration. |
Before the Sun Fire B10n content load balancing blade can be configured to do basic load balancing, you must at minimum, configure a default gateway, and DNS server, a service, and a group.
As admin in config mode, set the default gateway:
puma(config){admin}# default gateway ip_addr |
The following example configures the default gateway as 192.50.50.200:
puma(config){admin}# default gateway 192.50.50.200 |
As admin in config mode, configure the primary DNS server:
puma(config){admin}# dns server 192.50.50.100 primary |
As admin in config mode, configure the DNS suffix:
puma(config){admin}# dns suffix mycompany.com |
As admin in config mode, commit the configuration you just set up:
puma(config){admin}# commit |
As admin, verify the configuration you just set up:
Note - The output from the show network command is only an example of the data provided. Your output will be different. |
Copyright © 2003, Sun Microsystems, Inc. All rights reserved.