Re: Starting a JS12 Blade with i5/OS

Steve,

You said: "The Natchev document has it all, step by step.The important milestones are configing the AMM so your browser can get to the BCS."

What is the "Natchev document" and where would I find it? I am looking for a step by step and the AMM config seems to be the issue.

Thanks

Pete

Steve Richter wrote:

On Sun, Oct 5, 2008 at 2:59 PM, Pete Helgren <Pete@xxxxxxxxxx> wrote:

Thanks. Right now I am working through an error that says:

"SOL is not ready", which despite the ominous acronym, has to do with
the Serial Over Lan status. It IS enabled, but doesn't seem to be
entering the "ready" state. Still searching for an answer to that issue.

I would avoid the PuTTY connect to the BCS. It is easy to connect a
monitor and keyboard to the BCS and the press the switch on the blade
to acquire the KVM. The Natchev document has it all, step by step.
The important milestones are configing the AMM so your browser can get
to the BCS. Then run mktcpip from the system console to config the IP
address of VIOS on the JS12. That gives you IVM browser access to
VIOS. Then the IBM i lan console.

here are notes I took during my install. not complete, but they might help:

--------------------------------------

Client Access
Client Access provides the Lan Console needed to install IBM i.

Install from the disk labeled "IBM System i Access for Windows"

After the install, install the system i access service pack
browse to the "System i Access" home page, click Windows tab, Service packs, etc

Connect PC monitor, keyboard and mouse to the respective ports of the
AMM ( advanced mgmt module )
keyboard, etc are shared between blades. Press the monitor button on
the blade for the blade to acquire the kbd/mouse/monitor.
as the blade boots, status messages are displayed on the monitor

FTP - send file to VIOS using FTP
FTP from Windows XP works better than from Vista

suggested location to place files: /home/padmin

ftp 192.168.1.24
bin
put c:\bladecenter\steve.img
Hardware - BC-S and JS12
300GB SAS drives - part no 43X0802 - $365
4GB memory ( 2 x 2GB ) DDR2 667MHz DIMMs - 7998-8229 - $459
IBM i - install
using the IVM browser, configure the IBM i partition

insert the LIC install DVD

before activating the partition, click on the partition name link to
display its properties
on the general tab, IPL source D, keylock position manual
ethernet tab - a virtual ethernet adapter is configured
storage tab - physical volumes are selected. IBM recommends that the
drives internal to the blade are reserved for VIOS.
optical devices tab - the physical optical device is selected

Lan connect the AMM to the router
the default config of the AMM is to use DHCP to connect to the
network. The DHCP server will then assign an IP address to the AMM. If
you dont want this to happen
use LAN cable to direct connect a PC to the AMM
set the PC to IP address 192.168.70.101

Lan connect the Ethernet IO module to the router
the Ethernet IO module is the L2/L3 Nortel switch
connect from port1 to the router
can connect as many LAN cables to the router as there are ports on the
Nortel switch

LAN console
LAN console is part of System i client access
updates the HOSTS table of the PC with the IP address of the host name entered
C:\WINDOWS\system32\drivers\etc\hosts

start the blade by connecting it to a power source
best to supply power to both power supplies. When both power supplies
are used the system is more quiet and consumes the same amount of
power as when a single power supply is used.
this does not power up the blades. Power up the blades from the AMM
browser connection or by pressing the white button on the front of the
blade

Test the browser and PuTTY connect to the AMM
run PUTTY on the configing PC. Enter the IP address of the AMM.
browse to the IP address of the AMM
in both cases, the default login name is USERID and the password is
PASSW0RD ( digit zero instead of letter O )

PuTTY basics
type help for a list of commands
exit to quit the connection

PuTTY - Download and Install
install on the configing PC
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

PuTTY - open a console for VIOS
make sure the VIOS console is changed to /dev/vty0
make sure SOL is enabled for the blade
start PuTTY connection to the AMM
login with same user profile as for the browser interface ( shipped
value is : USERID, PASSW0RD )
env -T blade[x]
console
VIOS will display some sort of system log
to log in, press enter. User id is padmin

Power off a blade
AMM
blade tasks - power/restart
select the blade, click the desired power option

Firmware - download
browse to bladecenter S - software and device drivers
http://www-304.ibm.com/systems/support/supportsite.wss/supportresources?categoryind=5035127&familyind=5356544&brandind=5000020&osind=0&typeind=0&modelind=0&matrix=Y&taskind=2&selectedButton.x=15&selectedButton.y=11
ethernet I/O module firware

Firmware - Nortel L2/L3 switch
multiple step process - be prepared

Follow the link at the IBM site. Will be taken to Alteon - Nortel site
have to register and login at the Nortel site. Switch serial number
will be needed.

Download the firmware files to your PC.

Can use TFTP to install. Did not work for me.


Assign ethernet addresses to modules in the BCS
AMM
IO Module tasks - configuration
ip addr - 192.168.1.20
gateway - 192.168.1.1
click save


Assign disks to blades

USB - using a USB attached DVD drive from JS12 blade
plug USB cable of DVD drive to either back or front of the BCS chassis

the chassis may be plug and play, but VIOS is not. Have to reboot the
blade for the USB device to be recognized.

to see that the USB device is available to VIOS:
lsdev | grep cd

To use USB DVD device in IBM i
IVM connect to the IBM i partition
from IBM i partition properties, click optical devices tab
USB device should be listed. Select to use in IBM i.

VIOS - install or reinstall - from AMM browser
click REMOTE CONTROL under Blade Tasks
click Start Remote Control

VIOS - Install
overview

to install VIOS, boot the blade, at the console wait for the SMS menu
to display, take option 1, then use 5=boot options to config the blade
to be booted from the VIOS install DVD.

the SMS menu steps
1-sms menu
5-boot options
1-select install boot device
3-cd/dvd
6-usb
1-choose the usb cd rom
2-normal mode boot
1-yes, exit sms

steps to run after the install:
signon as padmin and set the password
accept the license agreement. run the "license -accept" command or
reply with "a" at the license prompt
use lsdev command to find name of "HEA" ( host ethernet adapter ) to use:
lsdev | grep hea
where "entx" is displayed, the interface to use is "enx"
use mktcpip command to config the ip address and host name of the VIOS
mktcpip -hostname js12vios -inetaddr 192.168.1.24 -interface en4
-gateway 192.168.1.1 -start


Configure networking in VIOS
login to VIOS using the padmin user profile
use lsdev command to get name of first HEA ( host ethernet adapter )
on the blade
lsdev | grep hea
interface name to use for ent0 is en0
mktcpip -hostname vjs12 -inetaddr 192.168.1.22 -interface en0 -gateway
192.168.1.1 -start
specify the DNS server name and ip address if you have them
run "lstcpip -stored" to display the current VIOS network config

Display current microcode level of the CFFv SAS expansion adapter on
the JS12 blade
start telnet session to VIOS
lsfware -dev mptsas0
sample results : 00105000 1004712303

troubleshooting - device resource OPT01 not found
look in IVM - view/modify virtual storage - optical devices tab
should be an optical device under "physical optical devices"
at the VIOS command prompt, list the cd devices:
lsdev grep | cd0
lsmap -all : list the physical devices vios is expecting to find
reseat the AMM module, then power cycle the chassis


VIOS - upgrading
download the upgrade package from IBM.

follow instructions to download the ISO image files.
for each file, use a product like "express burn" from NCH software to
burn the ISO images to DVD or CD.

boot VIOS on the blade. Login as "padmin"

get name of cd drive:
lsdev | grep cd

place CD in the CD drive

run updateios command:
updateios -accept -install -dev /dev/cdX

answer multiple prompts to mount the next disk

once complete, verify the software level
ioslevel