Level: Introductory Hans-Dieter Wehle, e-business Architect, IBM Developer Relations
04 Aug 2004 This article describes the steps of a basic installation of Linux on an IBM eServer BladeCenter JS20 blade server, starting with the BladeCenter Management Module and ending with the installation of SUSE Linux Enterprise Server 8.
The first major step is to install a JS20 blade server in a BladeCenter chassis and prepare the BladeCenter Management Module for the new JS20 blade server. The second major step is to install Linux on the blade server via a SUSE Linux Enterprise Server 8 (SLES 8) distribution on CD-ROM. In general, you will be accepting SUSE's recommended defaults.
BladeCenter Management Module and Serial Over LAN
Setting up the BladeCenter Management Module
Before beginning the installation, you should be familiar with BladeCenter Management Module configuration. (See Resources for a link to more information on the BladeCenter Management Module, if you are not already familiar with it).
First, you'll need to cable the BladeCenter Management Module into your existing environment. Either use a cross-over cable between your workstation and the BladeCenter, or connect the BladeCenter Management Module via an external Ethernet switch. If you opt for the latter, you will also have to connect your local workstation to the external Ethernet switch.
Figure 1. IBM eServer Blade Center JS20 blade server
Configuring BladeCenter Management Module
You will need to set up the TCP/IP configuration on your local workstation. Use the default IP address (normally http://192.168.70.125) for the BladeCenter Management Module as input. Please check the label on the BladeCenter Management Module for the IP address and the default userid/password.
Next, disable the proxy configuration for your Web browser.
Now, start the browser on your workstation and access the Web front-end of the BladeCenter Management Module using the default IP address (or use the IP address that you have assigned to it).
When the logon screen appears, enter the user ID USERID. The password is PASSW0RD (where 0 = a zero).
Once you have successfully logged on, a Welcome screen appears. You need to click the Continue button in order to access a screen with the system status summary.
 |
BladeCenter JS20 hints and tips:
-
Integrated Ethernet Port 0 will only be used for the Serial over LAN (SOL) connection to the system.
-
Integrated Ethernet Port 1 will be used for network traffic and network installs.
|
|
Do not forget to check the firmware level, and make sure you use the latest firmware level when you select MM Control/Firmware Update on the left side of the screen. If you need to update the firmware, use the download site listed in Resources, or use the firmware on the IBM-supplied CD-ROM.
Configuring and setting up a Serial Over LAN session
Serial Over LAN provides users with the ability to view the JS20 boot and progress codes. Set it up by following these steps:
- From the side panel, select Blade Tasks/Serial Over LAN.
- Click on the Serial over LAN Configuration link.
You need to enable SOL on the BladeCenter before you enable SOL on the JS20 blade server.
To do this from the SOL console, select enable at the top of the screen and verify that the SOL VLAN ID is set to 4095.
If the SOL VLAN ID is not set, complete the following steps:
- Go to the debug Web page <http://192.168.70.125/private/debug.ssi> (or replace this IP address with the one assigned for your BladeCenter Management Module).
- In the command field, type
sol -v 4095, then click the Submit button.
- Hit the Exit Debugger button to go back to the main Web page.
SOL should now work. (It is not necessary to reboot the BladeCenter Management Module.)
You will need to input these values:
-
BSMP IP address range set to 10.10.10.80
-
Accumulate timeout set to 250
-
Send threshold set to 1
-
Retry count set to 2
-
Retry interval value must be set to 80
If you change anything on the screen -- for instance, the enable, disable, or transport parameters -- make sure you save the changes by selecting the Save button.
At this point, you should restart the BladeCenter Management Module.
Now you are ready to enable SOL for your JS20 blade server. Click on the check box in the first column, then click on the Enable SOL link (below the Serial Over LAN Status screen) to enable SOL on the selected JS20 blade server.
If the SOL status does not change to Ready or Enabled within two minutes (this should appear on the left side under MM Control status), select Restart MM. Note that if other JS20 blades are currently running SOL sessions, restarting the BladeCenter Management Module will cause all sessions to be lost, and they will all have to be re-established. Therefore, you should choose the Restart MM option only when it is truly necessary.
To restart the BladeCenter Management Module in a way that is less detrimental to other SOL sessions, use the Restart Blade System Mgmt Processor link on the Power/Restart Tab, which is the last link on the Web interface. (Click OK on both pop-up windows.)
Once you have enabled Serial Over LAN, you can begin to customize your new JS20 blade server.
Customization and configuration
The first thing you will want to do is change the boot sequence of the JS20 blade server from Hard disk to CD-ROM.
The left navigation section shows the topic Blade Tasks; choose it, then click on Configuration. The Blade Server Configuration screen appears. You will change the boot sequence for the new JS20 blade server from this screen.
Click on Boot Sequence to access a screen with a Boot Sequence section; from here, go to the bay where the new JS20 blade server is located.
Click on the name shown for the new JS20 blade server. This displays the Blade Boot Sequence screen.
Define the first boot device as CD-ROM and the second boot device as Hard drive 0. (If you will need this option later, define the third boot device as Network BOOTP).
Don't forget to click Save.
Now it is time to assign the IBM BladeCenter's CD-ROM to the new JS20 blade server. Press the CD button of the JS20 blade server -- it should start flashing green.
From the left navigation section of the displayed screen, go to Blade Tasks and select Power/Restart. From here, you can stop and start the JS20 blade server with the Power On Blade and Power Off Blade options.
The JS20 blade server must have a power status of Off in order to install from CD-ROM. If this is not the case, click on the name of the new server and select Power Off Blade. Then use your browser's reload/refresh option to refresh the displayed information.
Now it is time to connect the JS20 blade server via SOL, which we have already enabled on the BladeCenter Management Module. Establish the connection by choosing Blade Tasks and then Serial Over LAN.
Installing SUSE Linux Enterprise Server 8
Insert the first SUSE SLES 8 SP 3 CD (CD 1) into the BladeCenter's CD-ROM reader. From a command-line window, enter the PuTTY command to connect to the BladeCenter Management Module (you may have to use telnet).
putty 192.168.70.125 (USERID/PASSW0RD)
Start an SOL connection like so (x is the bay number of the new blade server):
console -T system:blade[x]
If you receive an error message saying that SOL is not ready, please check the SOL state. (You can do this at the command line with the command SOL -T blade[x].)
Otherwise, the system should boot and start the Linux installation. A SUSE Welcome menu will come up. If you see either E1AD or Elapsed time since - on the screen, the installation is running. This step takes a few minutes.
In the menu, type install.
This installation step takes a few minutes. The CD-ROM drive indicator blinks, and the terminal (or command prompt) window displays the message, Please wait, loading kernel.
When you are prompted to change the CD-ROM, replace CD 1 of SP3 with the first CD-ROM of the SUSE SLES 8 package. Then press OK.
The next screen asks you to select a terminal type. Use option 3 (VT220) for Windows and option 4 (xterm) for UNIX or Linux.
Now the text-based Linux install begins. If you are not already familiar with this process, see the article "Install Linux on pSeries," which is listed in the Resources section, for more information.
After the Linux installation is finished, you can use ssh to reach the JS20 blade server.
Congratulations!
At this point, you should be ready to go. If you are not, check some of the troubleshooting guides listed in the Resources section below.
Resources
- Before beginning the installation, you should be familiar with BladeCenter Systems Management configuration.
- If you need to update your firmware, use the IBM-supplied CD-ROM or check the Management Module Firmware updates download site.
- For more information about Linux installation, please have a look at the article "Install Linux on pSeries" (developerWorks, July 2003).
- Learn more about installing Linux and troubleshooting from the Linux Installation and Getting Started guide.
- You will find information, articles, and downloads at the IBM BladeCenter blade servers home page and the What are blade servers? page.
- Find great resources at the Linux on POWER page.
- For Linux developers looking to get started on Power Architecture, you'll find a collection of articles and resources on the Linux on Power Architecture Developer's corner.
- Find more resources for Linux developers in the developerWorks Linux zone.
-
Browse for books on these and other technical topics.
- Develop and test your Linux applications using the latest IBM tools and middleware with a developerWorks Subscription: you get IBM software from WebSphere, DB2, Lotus, Rational, and Tivoli, and a license to use the software for 12 months, all for less money than you might think.
About the author | 
| | Hans-Dieter is an e-business architect for IBM's Developer Relations group. He is a member of the IBM EMEA Technical Marketing Competence Center and Linux Center of Competence in Boeblingen, Germany. Hans-Dieter has more than 15 years of experience in the computer industry, ranging from field support to software development and consulting. You can contact Hans-Dieter at hdwehle@de.ibm.com. |
Rate this page
| 
