40
o
Gateway IP Address:
The gateway IP for this VIOS partition.
o
Subnet Mask:
The correct subnet mask for the network segment of which VIOS
is going to be a part.
•
Once everything is filled in correctly, hit the ESC key to go back a page and select
3.Ping
Test
•
Select
1.Execute Ping Test
to test the connection. If the ping test was successful, hit
the
M key
to go back to the SMS Main Menu and continue the install. (If the ping test
was not successful, check the network settings on the BladeCenter)
•
At the SMS Main Menu, select the menu option
5.Select Boot Options
•
Select
1.Select Install/Boot Device
•
Select
6.Network
for the Device Type
•
Select
1.BOOTP
as the Network Service
•
Select the port you configured above (for most scenarios, port 1)
•
Select
2.Normal Mode Boot
•
Select
1.Yes
to start the install (this will exit the SMS menus and the install image will
start downloading from the NIM server)
5.2.7. Completing the install
This section applies to installing from DVD or NIM:
•
Once the first "Welcome to the Virtual I/O Server" screen has disappeared, enter
2
on the
following one to confirm this terminal as the console and press Enter (the number will not
appear on the screen)
•
Enter the correct number option for the language you want to use during install
•
On
the
Welcome to BOS
menu, choose
Change/Show Installation Settings and
Install
•
Choose
option 2
to verify the correct disk unit is selected for installation. The SAS drive
internal to the blade will be detected as hdisk0, whereas any LUNs attached to VIOS will
be detected as hdisk1, hdisk2 and so on
•
Choose
option 0
twice to start installing
•
After the install has completed and VIOS has rebooted, log in with the default
administrator user profile,
padmin.
A password is not required for this first login
•
When prompted, enter a password for
padmin
twice
•
Enter
license –accept
to accept the VIOS license agreement
5.2.8. Mirroring of VIOS
Because VIOS provides storage, optical and networking I/O resources to IBM i, any IBM i LPAR
on the blade depends on VIOS to be operational. Therefore, it is strongly recommended to
employ disk protection for the VIOS installation.
When IBM i is implemented on JS22, there is a single internal SAS drive on the blade itself that
can be used for the VIOS installation. With JS22 in a BladeCenter H, the VIOS installation can
then be mirrored to a LUN on the SAN. Alternatively, you can forgo the internal drive on the
blade, and install VIOS entirely on the SAN, leveraging its RAID disk protection. If VIOS is
installed entirely on the SAN, it is strongly recommended to use MPIO to access the LUNs, as
discussed in section 4.4. With JS22 in a BladeCenter S, VIOS can again be installed on the
internal drive on the blade and mirrored to a SAS drive in the chassis; or installed on a SAS drive
in one DSM and mirrored to a drive in the second DSM. In this case, it is recommended to install
VIOS on the drive on the blade and mirror to a drive in the chassis, in order to use as few drives
in the chassis as possible just for VIOS.
