Cisco SFS Boot over InfiniBand
User Guide for Linux
Release 3.2.0
June 2007
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
Text Part Number: OL-12368-01
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL
STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT
WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT
SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE
OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH
ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT
LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF
DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING,
WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO
OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
CCVP, the Cisco logo, and the Cisco Square Bridge logo are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn is a service mark of Cisco Systems,
Inc.; and Access Registrar, Aironet, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, CCSP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press,
Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, Follow Me Browsing,
FormShare, GigaDrive, HomeLink, Internet Quotient, IOS, iPhone, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, iQuick Study, LightStream, Linksys,
MeetingPlace, MGX, Networking Academy, Network Registrar, Packet, PIX, ProConnect, ScriptShare, SMARTnet, StackWise, The Fastest Way to Increase Your Internet
Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0705R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the
document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
Cisco SFS Boot over InfiniBand
User Guide for Linux
© 2007 Cisco Systems, Inc. All rights reserved.
CONTENTS
Preface
v
Audience
v
Organization
vi
Conventions
vi
Related Documentation
vii
Obtaining Documentation, Obtaining Support, and Security Guidelines
CHAPTER
1
Boot over IB Overview
1-1
How Boot over IB Works
Boot over IB Features
Supported Platforms
CHAPTER
2
1-1
1-2
1-2
Booting from a Fibre Channel SAN
Overview
vii
2-1
2-1
Setting Up Hardware 2-2
Installing Hardware 2-2
Checking the HCA Firmware Version
2-3
Configuring a Fibre Channel Connection 2-3
Using Element Manager and a Host with a Remote Boot HCA
Using the CLI and a Host with a Remote Boot HCA 2-5
2-3
Installing an Image on Fibre Channel Storage 2-10
Installing and Booting RHEL3 or RHEL4 2-10
Installing and Booting SLES9 Service Pack 3 2-18
Booting an Image 2-34
Booting the Installation Host 2-34
Booting a New, Diskless Host with a New HCA
Using the CLI 2-35
Using Element Manager 2-38
CHAPTER
3
Booting from PXE
2-35
3-1
About Booting from PXE 3-1
Hardware Setup for PXE Boot Process
3-1
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
iii
Contents
Overview of the PXE Boot Process
3-1
Configuring Boot over PXE 3-2
Verifying Prerequisites 3-2
Performing Hardware Setup 3-3
Checking the HCA Firmware Version 3-4
Configuring the Booting Host 3-5
Configuring the DHCP Server 3-6
Configuring the TFTP Server 3-7
Configuring the Boot Loader 3-7
Configuring the Ethernet Gateway 3-8
APPENDIX
A
Acronyms and Abbreviations
A-1
INDEX
Cisco SFS Boot over InfiniBand User Guide for Linux
iv
OL-12368-01
Preface
This preface describes who should read the Cisco SFS Boot over InfiniBand User Guide for Linux, how
it is organized, and its document conventions and includes the following sections:
•
Audience, page v
•
Organization, page vi
•
Conventions, page vi
•
Related Documentation, page vii
•
Obtaining Documentation, Obtaining Support, and Security Guidelines, page vii
Audience
The intended audience is the administrator responsible for configuring and managing host drivers and
host card adapters that boot over IB. This administrator should have experience administering similar
networking or storage equipment.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
v
Preface
Organization
Organization
This publication is organized as follows:
Chapter
Title
Description
Chapter 1
Boot over IB Overview
This chapter describes how boot over IB
works, the value of boot over IB, and some
requirements to enable boot over IB.
Chapter 2
Booting from a Fibre Channel
SAN
This chapter describes how to boot from a
Fibre Channel Storage Area Network
(SAN).
Chapter 3
Booting from PXE
This chapter describes how to boot over IB
using the Pre-boot Execution Environment
(PXE).
Appendix A
Acronyms and Abbreviations
This appendix defines the acronyms and
abbreviations that are used in this
publication.
Conventions
This document uses the following conventions:
Convention
Description
boldface font
Commands, command options, and keywords are in
boldface. Bold text indicates Chassis Manager elements or
text that you must enter as-is.
italic font
Arguments in commands for which you supply values are in
italics. Italics not used in commands indicate emphasis.
Menu1 > Menu2 >
Item…
Series indicate a pop-up menu sequence to open a form or
execute a desired function.
[ ]
Elements in square brackets are optional.
{x|y|z}
Alternative keywords are grouped in braces and separated by
vertical bars. Braces can also be used to group keywords
and/or arguments; for example, {interface interface type}.
[x|y|z]
Optional alternative keywords are grouped in brackets and
separated by vertical bars.
string
A nonquoted set of characters. Do not use quotation marks
around the string or the string will include the quotation
marks.
screen
font
Terminal sessions and information the system displays are in
font.
screen
boldface screen
Information you must enter is in boldface screen font.
font
Cisco SFS Boot over InfiniBand User Guide for Linux
vi
OL-12368-01
Preface
Related Documentation
Convention
Description
italic screen font
Arguments for which you supply values are in italic
screen font.
^
The symbol ^ represents the key labeled Control—for
example, the key combination ^D in a screen display means
hold down the Control key while you press the D key.
< >
Nonprinting characters, such as passwords are in angle
brackets.
!, #
An exclamation point (!) or a pound sign (#) at the beginning
of a line of code indicates a comment line.
Notes use the following convention:
Note
Means reader take note. Notes contain helpful suggestions or references to material not covered in the
manual.
Cautions use the following convention:
Caution
Means reader be careful. In this situation, you might do something that could result in equipment
damage or loss of data.
Related Documentation
For additional information related to Cisco SFS Boot over IB, see the following documents:
•
Release Notes for Linux Boot over InfiniBand, Release 3.2.0
•
Release Notes for TopspinOS Release 2.9.0
•
Release Notes for Linux Host Drivers Release 3.2.0
•
Cisco Product Family Chassis Manager User Guide
•
Cisco Product Family Element Manager User Guide
•
Cisco Product Family Command Reference Guide
•
Host Channel Adapter Hardware Guide
Obtaining Documentation, Obtaining Support, and Security
Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback,
security guidelines, and also recommended aliases and general Cisco documents, see the monthly
What’s New in Cisco Product Documentation, which also lists all new and revised Cisco technical
documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
vii
Preface
Obtaining Documentation, Obtaining Support, and Security Guidelines
Cisco SFS Boot over InfiniBand User Guide for Linux
viii
OL-12368-01
C H A P T E R
1
Boot over IB Overview
With your software and IB device, you can centrally locate host images and configure your hosts to boot
these images over your IB network. This chapter explains the Boot over IB (BoIB) feature and discusses
the value that this feature adds to your network.
This chapter includes the following sections:
Note
•
How Boot over IB Works, page 1-1
•
Boot over IB Features, page 1-2
•
Supported Platforms, page 1-2
For expansions of acronyms and abbreviations used in this publication, see Appendix A, “Acronyms and
Abbreviations.”
How Boot over IB Works
When hosts boot over an IB fabric, they boot an image that resides on a remote storage device. Hosts
with HCAs that use BoIB firmware can boot an image using one of the following methods:
•
Using a Fibre Channel SAN through the Fibre Channel gateway
•
Using PXE with Ethernet gateway
When the IB host boots, it initializes the HCA and executes the HCA BoIB firmware image. The HCA
firmware communicates with the connected server switch to determine which boot LUN to request. Once
this information is received, the HCA acts like a standard SCSI interface and reads the boot sector from
the remote Fibre Channel storage. The rest of the OS loads as though the storage were locally attached
storage.
Alternatively, you can boot with PXE over an IB fabric using Ethernet services or from an IB server. To
boot over PXE, connect the boot server either to IB or to an Ethernet network, but use the same IP subnet
as the boot host. If an Ethernet-based boot server is used, an Ethernet gateway is used to bridge the IP
subnet.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
1-1
Chapter 1
Boot over IB Overview
Boot over IB Features
Boot over IB Features
The BoIB feature serves as a manageability tool to help you more easily and centrally administer your
network. With this feature, you can perform the following tasks:
•
Quickly and easily change the image that hosts run
•
Centrally localize images
•
Easily reallocate hosts based on your immediate needs
•
Eliminate any need for local storage, eliminating a common source of failure
•
Reduce the amount of power that your servers consume
•
Increase the mean time between failure of your servers
•
Replace old hardware with new hardware and boot the existing image and configuration
With the Boot over IB feature, you can change storage mappings during production, then reboot servers
from a different storage to change the functions of the servers.
Supported Platforms
For a list of supported platforms, see the Release Notes for Linux Boot over InfiniBand, Release 3.2.0.
Cisco SFS Boot over InfiniBand User Guide for Linux
1-2
OL-12368-01
C H A P T E R
2
Booting from a Fibre Channel SAN
This chapter describes the boot from a Fibre Channel SAN process and includes the following sections:
•
Overview, page 2-1
•
Setting Up Hardware, page 2-2
•
Checking the HCA Firmware Version, page 2-3
•
Configuring a Fibre Channel Connection, page 2-3
•
Installing an Image on Fibre Channel Storage, page 2-10
•
Booting an Image, page 2-34
Overview
This section describes how to perform a SAN boot with SRP and includes the following high-level steps:
Step 1
Install and connect all required hardware.
For more information, see the “Installing Hardware” section on page 2-2.
Step 2
Load the correct firmware onto the HCA.
You can upgrade standard and low-profile HCAs to run BoIB-capable firmware. To upgrade the firmware
on your HCA, see the Cisco SFS InfiniBand Host Drivers User Guide for Linux.
Note
Step 3
Skip this step if your HCA already runs BoIB firmware. To determine if your HCA already runs
the appropriate software, see the “Checking the HCA Firmware Version” section on page 2-3.
Configure an ITL group to connect your host to the Fibre Channel storage.
For details, see the “Installing an Image on Fibre Channel Storage” section on page 2-10.
Note
Skip this step if your environment runs VFrame software. VFrame Director, along with a server
switch and gateways, creates a programmable switching fabric for mapping servers to storage
and networking resources. For more information, see the Cisco VFrame InfiniBand Director
User Guide.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-1
Chapter 2
Booting from a Fibre Channel SAN
Setting Up Hardware
Step 4
Load an image onto a Fibre Channel storage device.
For details, see the “Configuring a Fibre Channel Connection” section on page 2-3.
Note
Step 5
Skip this step if an image already resides on your storage.
Boot the remote image.
For details, see the “Booting an Image” section on page 2-34.
Setting Up Hardware
A SAN boot with the BoIB feature uses the following hardware:
•
A host with an HCA
•
A server switch with a Fibre Channel gateway
•
A Fibre Channel storage device (connected, optionally, through a SAN switch or switch fabric)
•
(Optional) A portable CD ROM drive for servers without a local drive
•
(Optional) A KVM device, recommended to view the installation process
Installing Hardware
To create the physical environment for your SAN boot, perform the following high-level steps:
Step 1
Install the HCA into your host.
For details, see the Cisco SFS InfiniBand Host Drivers User Guide for Linux.
Step 2
Connect the HCA to an IB port on your server switch.
Step 3
Install the Fibre Channel gateway into your server switch.
For details, see the Cisco SFS InfiniBand Fibre Channel Gateway User Guide.
Step 4
Note
Connect the Fibre Channel gateway to a Fibre Channel storage device or to a SAN fabric with a Fibre
Channel storage device.
If you upgrade your Linux kernel after installing these host drivers, you need to reinstall the host drivers.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-2
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Checking the HCA Firmware Version
Checking the HCA Firmware Version
This section describes how to check the HCA firmware version. To verify that your HCA provides the
BoIB feature, enter the /usr/local/topspin/sbin/tvflash -i command from the host CLI. If .Boot appears
in the description of your HCA, the HCA includes the BoIB feature.
If your HCA does not run BoIB firmware, update the HCA. For instructions, see the Cisco SFS
InfiniBand Host Drivers User Guide for Linux.
The following example shows how to check the HCA firmware version:
host1# /usr/local/topspin/sbin/tvflash -i
HCA #0: MT23108, Cougar Cub, revision A1
Primary image is v3.5.000 build 3.2.0.118, with label 'HCA.CougarCub.A1.Boot'
Secondary image is v3.5.000 build 3.2.0.106, with label 'HCA.CougarCub.A1.Boot'
Vital Product Data
Product Name: Cougar cub
P/N: MHXL-CF128-T
E/C: C-00
S/N: MT0420F00221
Freq/Power: N/A
Checksum: Ok
Date Code: N/A
Note
The firmware is available on the BoIB ISO image. For instructions on how to upgrade your firmware,
see the Cisco SFS InfiniBand Host Drivers User Guide for Linux.
Configuring a Fibre Channel Connection
This section describes how to configure a Fibre Channel connection and includes the following topics:
•
Using Element Manager and a Host with a Remote Boot HCA, page 2-3
•
Using the CLI and a Host with a Remote Boot HCA, page 2-5
Using Element Manager and a Host with a Remote Boot HCA
This section describes how to use the Element Manager and a host with a remote boot HCA. These
procedures are based on the following requirements:
•
The HCA in your host runs BoIB feature firmware.
•
You have installed all hardware components successfully.
•
Only one HCA resides in your host.
To install an image onto storage, perform the following steps:
Step 1
(Recommended) Restrict global access.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-3
Chapter 2
Booting from a Fibre Channel SAN
Configuring a Fibre Channel Connection
Note
If you do not restrict access, only the first seven LUNs that your host can access will appear in
the boot menu.
After you install an image, you must deny your host access to all LUNs that contain bootable
images (except the LUN that stores the image that you want to boot). Hosts might not boot
successfully when they can access multiple LUNs that store bootable images. After you install
the image, if you grant your host access to additional LUNs that do not contain bootable images,
your host continues to boot successfully.
Step 2
a.
Launch Element Manager and open your server switch.
b.
From the FibreChannel menu, select Storage Manager. The Storage Manager window opens.
c.
Click the Storage folder at the top of the left-hand navigation tree.
d.
In the Gateway Port Access field, check the Restricted check box.
e.
In the LUN Access field, check the Restricted check box.
f.
Click the Apply button.
Configure an ITL.
Note
If you are using a VFrame environment, do not configure ITLs manually. VFrame configures
ITLs for you.
a.
Boot your host and press the x key when the Type ‘x’ to configure boot options prompt appears
during the boot process. The GUID of the host appears in the host display. Record the GUID and
leave the host at this screen. You will refresh the screen later in this process.
b.
Return to the Storage Manager window of Element Manager and click the SRP Hosts folder in the
navigation tree.
c.
Click the Define New button. The Define New SRP Host window opens.
d.
Enter the GUID of your host (from Step a) in the Host GUID field, or select it from the drop-down
menu (if available).
e.
(Optional) Enter a text description for the host in the Description field.
f.
Click the Next > button.
g.
Click the Finish button. The new initiator appears under the SRP Hosts folder.
h.
Click the new initiator under the SRP Hosts folder, and then click the Targets tab.
i.
Verify that the WWPN of the target onto which you want to install the image appears in the list.
j.
Double-click in the list the WWPN (from Step i) in the list of the target onto which you want to
install the image. The IT Properties window opens.
k.
Click the ... button next to the Port Mask field. The Select Ports window opens.
l.
Click the button of the port that connects the host to the storage, and then click OK.
m.
Click the Apply button in the IT Properties window, and then close the window.
n.
Click the LUN Access tab, and then click the Discover LUNs button. The targets that your server
switch sees appear in the Available LUNs column.
o.
Click the target (from Step i) onto which you want to install an image, and then click the Add >
button.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-4
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Configuring a Fibre Channel Connection
p.
Click the Apply button.
q.
(Optional) If you plan to install the bootable image to an LU of a RAID device, perform the
following steps to define the bootable LU as LUN 0:
– In the Accessible LUNs field, double-click the LU to which you want to install the image. The
ITL Properties window opens.
– In the SRP LUN ID field, enter 00:00:00:00:00:00:00:00.
– Click the Apply button, and then close the window.
r.
Return to your host and press the r key to refresh your view. The WWPN of the target (from Step i)
appears in the display, beneath the GUID.
s.
(Optional but recommended) Configure the WKSN.
– Return to the Storage Manager window of Element Manager, click your SRP host, and then click
the General tab.
– From the Boot Target WWPN field, select the boot target from the drop-down menu or manually
enter it.
– From the Boot FC LUN field, select the boot LUN from the drop-down menu or manually enter
it.
– Click the Apply button.
Using the CLI and a Host with a Remote Boot HCA
This section describes how to use the CLI and a host with a remote boot HCA. These procedures are
based on the following requirements:
•
The HCA in your host runs BoIB feature firmware.
•
You have installed all hardware components successfully.
•
Only one HCA resides in your host.
To install an image onto storage, perform the following steps:
Step 1
(Recommended) Restrict global access.
Note
If you do not restrict access, only the first seven LUNs that your host can access will appear in
the boot menu.
After you install an image, you must deny your host access to all LUNs that contain bootable
images (except the LUN that stores the image that you want to boot). Hosts do not boot
successfully when they can access multiple LUNs that store bootable images. If, after you install
the image, you grant your host access to additional LUNs that do not contain bootable images,
your host continues to boot successfully.
Step 2
Log into your server switch.
Login: super
Password: xxxxx
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-5
Chapter 2
Booting from a Fibre Channel SAN
Configuring a Fibre Channel Connection
Step 3
Enter privileged EXEC mode by entering the enable command.
SFS-3012R> enable
SFS3012R#
Step 4
Enter global configuration mode by entering the configure terminal command.
SFS-3012R# configure terminal
SFS-3012R(config)#
Step 5
Restrict LUN access to initiators for all new ITs and ITLs.
Enter the fc srp-global command with the following items:
•
lun-policy keyword
•
restricted keyword
SFS-3012R(config)# fc srp-global lun-policy restricted
Step 6
Restrict portmask access to initiators for all new ITs and ITLs.
Enter the fc srp-global command with the following items:
•
gateway-portmask-policy keyword
•
restricted keyword
SFS-3012R(config)# fc srp-global gateway-portmask-policy restricted
Step 7
Configure an ITL.
Note
To install an image with VFrame, do not configure ITLs manually.
Step 8
Boot your host and press the x key when the Type ‘x’ to configure boot options prompt appears during
the boot process. The GUID of the host appears in the host display. Record the GUID and leave the host
at this screen. You refresh the screen later in this process.
Step 9
Add your host to the configuration file and create WWPNs on the Fibre Channel gateway that point to
the host.
Return to your server switch CLI and enter the fc srp initiator command with the following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
•
auto-bind keyword
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
auto-bind
Step 10
Assign an easily recognizable identifier to the initiator.
(Optional) Enter the fc srp initiator command with the following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
•
description keyword
•
Text description, enclosed in quotation marks
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
description "test-initiator"
Cisco SFS Boot over InfiniBand User Guide for Linux
2-6
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Configuring a Fibre Channel Connection
Step 11
Enter the exit command to return to privileged EXEC mode.
SFS-3012R(config)# exit
SFS-3012R#
Step 12
View the WWPNs of the host.
Enter the show fc srp initiator command with the following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
SFS-3012R# show fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
================================================================================
SRP Initiators
================================================================================
guid: 00:05:ad:00:00:00:17:3c
extension: 00:00:00:00:00:00:00:00
description: test-initiator
wwnn: 20:02:00:05:ad:00:00:00
credit: 0
active-ports: none
pkeys:
bootup-target: 00:00:00:00:00:00:00:00
bootup-lu: 00:00:00:00:00:00:00:00
action: auto-bind
result: success
wwpns: port
wwpn
fc-addr
2/1
20:02:00:05:ad:20:00:00 00:00:00
2/2
20:02:00:05:ad:24:00:00 00:00:00
3/1
20:02:00:05:ad:30:00:00 00:00:00
3/2
20:02:00:05:ad:34:00:00 00:00:00
4/1
20:02:00:05:ad:40:00:00 00:00:00
4/2
20:02:00:05:ad:44:00:00 00:00:00
5/1
20:02:00:05:ad:50:00:00 00:00:00
5/2
20:02:00:05:ad:54:00:00 00:00:00
6/1
20:02:00:05:ad:60:00:00 00:00:1d
6/2
20:02:00:05:ad:64:00:00 00:00:1d
7/1
20:02:00:05:ad:70:00:00 00:00:00
7/2
20:02:00:05:ad:74:00:00 00:00:00
8/1
20:02:00:05:ad:80:00:00 00:00:00
8/2
20:02:00:05:ad:84:00:00 00:00:00
9/1
20:02:00:05:ad:90:00:00 00:00:00
9/2
20:02:00:05:ad:94:00:00 00:00:00
10/1
20:02:00:05:ad:a0:00:00 00:00:00
10/2
20:02:00:05:ad:a4:00:00 00:00:00
11/1
20:02:00:05:ad:b0:00:00 00:00:00
11/2
20:02:00:05:ad:b4:00:00 00:00:00
12/1
20:02:00:05:ad:c0:00:00 00:00:00
12/2
20:02:00:05:ad:c4:00:00 00:00:00
13/1
20:02:00:05:ad:d0:00:00 00:00:00
13/2
20:02:00:05:ad:d4:00:00 00:00:00
Step 13
Record the WWPN of the port that connects the host to the storage.
Step 14
Verify that the host can see the target. If the WWPN of the target does not appear in the command output,
give the gateway some time to configure the ITs and retry the command.
Enter the show fc srp initiator-wwpn-view command with the following items:
•
WWPN of the port (from Step 13)
•
target keyword
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-7
Chapter 2
Booting from a Fibre Channel SAN
Configuring a Fibre Channel Connection
SFS-3012R# show fc srp initiator-wwpn-view 20:02:00:05:ad:60:00:00 target
================================================================================
SRP Targets Accessible to Initiator Via Port WWN 20:02:00:05:ad:60:00:00
================================================================================
wwpn: 21:00:00:04:cf:f6:c2:ab
wwnn: 20:00:00:04:cf:f6:c2:ab
description: SRP.T10:21000004CFF6C2AB
ioc-guid: 00:05:ad:00:00:00:15:1a
service-name: SRP.T10:21000004CFF6C2AB
protocol-ids: 04:00:00:00:00:00:00:00:00:00
fc-address: 00:00:23
mtu: 0
connection-type: nl-port
physical-access: 6/1
Step 15
Return to global configuration mode by entering the configure terminal command.
SFS-3012R# configure terminal
SFS-3012R(config)#
Step 16
Grant the host access to one target. This is the target from which your host will boot through the port.
Enter the no fc srp it command with the following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
•
WWPN of the target to which you want to install the image
•
gateway-portmask-policy keyword
•
restricted keyword
•
Fibre Channel gateway port that connects the host to the storage (in slot#/port# format)
SFS-3012R(config)# no fc srp it 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
21:00:00:04:cf:f6:c2:ab gateway-portmask-policy restricted 6/1
Step 17
Configure ITLs to which the host belongs. The ITLs inherit the portmask policy of the IT (from Step 7).
Enter the fc srp initiator command with the following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
•
discover-itl keyword
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
discover-itl
Cisco SFS Boot over InfiniBand User Guide for Linux
2-8
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Configuring a Fibre Channel Connection
Step 18
Grant the host access to one LUN. This is the LUN from which your host boots.
Enter the no fc srp itl command with the following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
•
WWPN of the target onto which you want to install the image
•
LUN ID of the LUN onto which you want to install the image
•
lun-policy keyword
•
restricted keyword
SFS-3012R(config)# no fc srp itl 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
21:00:00:04:cf:f6:c2:ab 00:00:00:00:00:00:00:00 lun-policy restricted
Step 19
(Optional) Install the bootable image to an LU of a RAID device. Enter the fc srp itl command with the
following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
•
WWPN of the target onto which you want to install the image
•
Fibre Channel LUN ID of the LUN to which you wish to install the image
•
srp-lunid keyword
•
SRP LUN ID that you want to assign to the LU (for the installation, you must enter
00:00:00:00:00:00:00:00)
•
logical-id keyword
•
logical ID of the LU, without colons (:)
SFS-3012R(config)# fc srp itl 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
21:00:00:04:cf:f6:c2:ab 00:00:00:00:00:00:00:01 srp-lunid 00:00:00:00:00:00:00:00
logical-id
0103000820000004cff6c2ab000000000000000000000000000000000000000000000000000000000000000000
00000000000000000000000000000000000000
Step 20
Return to your host and press the r key to refresh your view.
The WWPN of the target appears in the display under the GUID.
Step 21
Configure the LUN as the WKSN of your host.
Return to your server switch and enter the fc srp initiator command with the following items:
•
GUID of the host (from Step 8)
•
GUID extension of the host (always 00:00:00:00:00:00:00:00)
•
bootup keyword
•
target keyword
•
WWPN of the target onto which you want to install the image
•
lu keyword
•
LUN ID of the LUN onto which you want to install the image
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00 bootup
target 21:00:00:04:cf:f6:c2:ab lu 00:00:00:00:00:00:00:00
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-9
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Installing an Image on Fibre Channel Storage
This section describes how to install a bootable image on Fibre Channel storage with the following
resources:
Note
•
Installing and Booting RHEL3 or RHEL4, page 2-10
•
Installing and Booting SLES9 Service Pack 3, page 2-18
To ensure a successful boot, install with a separate /boot partition during the standard Linux setup.
Installing and Booting RHEL3 or RHEL4
This section describes how to install and boot the RHEL3 or the RHEL4. Use a Kickstart configuration
file that contains the driverdisk parameter to access the BoIB CD over the network.
driverdisk --source=nfs:10.0.0.35:/qadata/home/releng/builds/Linux-3.2.0/
build118/image/topspin-boib-3.2.0-118.iso
Note
Although there is a long delay while the ISO image is mounted and accessed, you must use an ISO
image, not a directory.
On RHEL3 and RHEL4, if you install over NFS, you need to use Kickstart with driverdisk, or place your
ISO image in the same directory as the Red Hat ISO images.
The following procedure begins the installation from a CD, but completes the installation over NFS:
Step 1
Place the first installation CD in your host and boot the server from the CD.
Step 2
(RedHat only) At your host CLI, exit interactive mode.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-10
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 3
(RedHat only) At the boot prompt, enter the linux dd or linux dd askmethod command to prompt the
installer to run the driver CD (Figure 2-1).
To complete the installation over NFS, enter the linux dd askmethod command.
Figure 2-1
Begin the Linux and Red Hat Installation
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-11
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
The installation begins loading (Figure 2-2).
Figure 2-2
Step 4
Installation Process
(RedHat only) At the Do you have a driver disk? prompt, click Yes (Figure 2-3).
Figure 2-3
Driver Disk Screen
Cisco SFS Boot over InfiniBand User Guide for Linux
2-12
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 5
(RedHat only) On the Driver Disk Source screen, select your CD ROM, and then select OK.
The Insert Driver Disk screen appears (Figure 2-4).
Figure 2-4
Step 6
Insert Driver Disk Screen
(RedHat only) Remove the Linux installation CD and place the driver CD in the drive, and then click
OK (Figure 2-4).
The ts_srp_host driver loads (Figure 2-5 and Figure 2-6).
Figure 2-5
Driver Disk Loading
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-13
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Figure 2-6
Step 7
SRP Host Driver Loading
(RedHat only) At the Do you wish to load any more driver disks? screen, click No.
The Installation Method screen (Figure 2-7) appears if you previously appended the askmethod option
to the linux dd command (see Step 3). If you do not use the askmethod option, this screen does not
appear. Continue to install from the CDs.
Figure 2-7
Select Installation Method
(In this example, the user has selected installation over NFS).
Cisco SFS Boot over InfiniBand User Guide for Linux
2-14
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 8
Select the network interface on which you want to install the image and click OK (Figure 2-8).
Figure 2-8
Select Networking Device
The Configure TCP/IP screen appears (Figure 2-9).
Figure 2-9
Enter Network IP Configuration Information
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-15
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 9
Enter the appropriate IP network information for the remote device from where you want to install the
packages, and click the OK button.
The NFS Setup screen appears (Figure 2-10).
Figure 2-10
Step 10
NFS Setup Screen
Enter the NFS server name and the path to the Red Hat directory and click the OK button.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-16
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 11
Caution
(RedHat only) Complete the installation as you normally would (Figure 2-11).
Install and verify that the host installs the boot loader to the SRP drive. If you have a local ATA drive,
by default the host is configured to install the boot loader on the ATA drive. Make sure that you avoid
installing the boot loader on the ATA drive.
Figure 2-11
Install Red Hat Packages
Step 12
(RedHat only) After the installation is complete, remove the driver CD and reboot the host.
Step 13
Change the default boot order to well known so that SRP Boot is selected first. You can change the order
using the boot ROM menu (Figure 2-12) or the Linux command line.
From the boot ROM menu, select the number corresponding to the WKBS. Save the configuration by
typing s. Type x to exit boot ROM. The system boots the SRP target now and on subsequent reboots.
Note
The IB switch configuration must be saved after installing over SRP in order for the WKBS to work.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-17
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Figure 2-12
Select WKBS from the Boot ROM Menu
To change the default boot option without using the boot ROM itself, use the tvflash -o
boot_type=well_known command.
Setting the value to well_ known requires the use of a boot ROM that is SRP-capable.
host1# /usr/local/topspin/sbin/tvflash -o boot_type=well_known
Writing [============================================================]
host1# /usr/local/topspin/sbin/tvflash -o
auto_upgrade=yes
boot_enable_port_1=yes
boot_enable_port_2=yes
boot_wait_on_error=no
boot_try_forever=no
boot_type=well_known
boot_saved_port=0
boot_saved_ioc_num=0
boot_saved_dgid=0000:0000:0000:0000:0000:0000:0000:0000
boot_saved_service_name=0000:0000:0000:0000
boot_pxe_secs=0
Note
If you do not install over NFS, you are prompted to reinsert the CD at the end of the process.
Installing and Booting SLES9 Service Pack 3
This section describes how to install and boot SLES9 Service Pack 3.
Note
This distribution can be installed directly from the BoIB CD. Older supported SLES9 Service Packs are
available, but as a smaller ISO image that is included on our BoIB CD. You have to burn the smaller ISO
image to a CD yourself.
To install SLES9, Service Pack 3 on a remote SRP disk, perform the following steps:
Step 1
Insert the Service Pack 3 CD 1 in your host.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-18
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 2
Boot your host. When the initial GUI screen appears, press the F6 key when the screen in Figure 2-13
appears.
Figure 2-13
Initial GUI Screen
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-19
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 3
Select the Installation in the screen (Figure 2-14).
Figure 2-14
Select Installation on GUI Screen
Cisco SFS Boot over InfiniBand User Guide for Linux
2-20
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 4
Press the F2 key and select 1024 x 768 to configure the screen resolution (Figure 2-15).
Figure 2-15
Configure Screen Resolution
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-21
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 5
Press the Enter key to continue the installation. A screen similar to the one shown in Figure 2-16
appears.
Figure 2-16
Disk-Change Prompt
Step 6
Place the driver CD in your host (Figure 2-16).
Step 7
Press the Enter key to continue.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-22
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 8
Select CD-ROM (Figure 2-17).
Figure 2-17
Step 9
Click OK and press the Enter key.
Note
Step 10
Select Driver Update Medium
To view installation details, press and hold Ctrl-Alt-F3 to view the output or press and hold
Ctrl-Alt-F4 to view the console. See your SLES distribution documentation for details. Press
and hold Ctrl-Alt-F1 to return to the primary display.
Click OK and press the Enter key.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-23
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 11
Insert the service pack CD 1 back into your host. The Drivers Updates added dialog box appears
(Figure 2-18).
Figure 2-18
Driver Updates Added Screen
Cisco SFS Boot over InfiniBand User Guide for Linux
2-24
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 12
Click OK and press the Enter key. The Driver Update medium dialog box appears (Figure 2-19).
Figure 2-19
Driver Update Medium
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-25
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 13
Click OK and press the Enter key. The Driver Updates added dialog box appears (Figure 2-20).
Figure 2-20
Driver Updates Added Screen
Cisco SFS Boot over InfiniBand User Guide for Linux
2-26
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 14
Click Back and press the Enter key. The choose the Driver Update medium dialog box appears
(Figure 2-21).
Figure 2-21
Driver Update Medium
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-27
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 15
When prompted, place the SLES 9 CD 1 in your host (Figure 2-22).
Step 16
Click OK and press the Enter key after ensuring the required CD is in the drive (Figure 2-22).
Figure 2-22
Note
Ensure Required CD is in the Drive
To ensure a successful boot, install with a separate /boot partition during the standard Linux
installation steps.
The following steps are for uniprocessor hosts.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-28
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 17
Continue the normal SLES installation until you reach the Installation Settings screen (Figure 2-23).
Figure 2-23
Step 18
Installation Settings Screen
Click the Software link (Figure 2-24). The Software Selection screen appears (Figure 2-25).
Figure 2-24
Click the Software Link
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-29
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 19
Click the Detailed Selection ... button (see button in Figure 2-25). The detailed selection screen appears
(Figure 2-26).
Figure 2-25
Click the Detailed Selection Button
Cisco SFS Boot over InfiniBand User Guide for Linux
2-30
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 20
From the Filter drop-down menu, select Search. A Search text field appears in the left pane
(Figure 2-27).
Figure 2-26
Search Text Field in Filter Drop-down Menu
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-31
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 21
Enter kernel in the Search field and click the Search button. The list of software appears in the right
pane (Figure 2-28).
Figure 2-27
Step 22
Enter Selection in the Search Field
Uncheck the kernel-default check box (Figure 2-28). Click OK if a dialog box pops up.
Figure 2-28
Uncheck the kernel-default Check Box
Cisco SFS Boot over InfiniBand User Guide for Linux
2-32
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Installing an Image on Fibre Channel Storage
Step 23
Check the kernel-smp check box (Figure 2-29). Click OK if a dialog box pops up.
Figure 2-29
Step 24
Check the kernel-smp Check Box
Click the Accept button (Figure 2-30).
Figure 2-30
Click the Accept Button
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-33
Chapter 2
Booting from a Fibre Channel SAN
Booting an Image
Step 25
Click Continue to resolve interdependencies (Figure 2-31).
Figure 2-31
Step 26
Click Continue to Resolve Interdependencies
Continue your standard SLES installation steps.
Booting an Image
This section describes how to boot an image. After you install an image onto Fibre Channel storage with
a host, you may continue to boot that host from the storage, or you may replace that host with a new,
identical host.
Booting the Installation Host
To boot the remote image with your installation host, reload the host. If the boot fails, verify that you
have taken the following steps:
•
Reconfigured the boot order of the host to put SRP boot first.
•
Reconfigured the boot service to use WKSN first and configured the WKSN on your server switch
(see Step 20 of Using the CLI and a Host with a Remote Boot HCA, page 2-5).
Cisco SFS Boot over InfiniBand User Guide for Linux
2-34
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Booting an Image
Booting a New, Diskless Host with a New HCA
This section provides procedures that are based on the following requirements:
•
Your host includes an HCA that runs BoIB firmware.
•
You have configured the Fibre Channel gateway on your server switch to deny port and LUN access
to all new initiators.
Using the CLI
This section describes how to use the CLI. To boot an image that exists using a new host and HCA,
perform the following steps:
Step 1
Remove or reconfigure any host that runs the existing image. Only one host on your network may boot
a given image.
Step 2
Physically connect your new host to your server switch.
Step 3
Configure an ITL.
Note
To install an image with VFrame, do not configure ITLs manually.
a.
Open your host and record the GUID from the label on your HCA. Alternatively, you can boot your
host and press the x key when the Type ‘x’ to configure boot options prompt appears during the boot
process. The GUID of the host appears in the host display. Record the GUID and leave the host at
this screen. You may refresh the screen later in this process.
b.
Log into your server switch.
c.
Enter privileged EXEC mode by typing the enable command.
SFS-3012R> enable
SFS-3012R#
d.
Enter global configuration mode by typing the configure terminal command.
SFS-3012R# configure terminal
SFS-3012R(config)#
e.
Add your host to the configuration file and create WWPNs, on the Fibre Channel gateway, that point
to the host.
Enter the fc srp initiator command with the following items:
– GUID of the host (from Step a)
– GUID extension of the host (always 00:00:00:00:00:00:00:00)
– auto-bind keyword
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
auto-bind
f.
(Optional) Assign an easily-recognizable identifier to the initiator.
Enter the fc srp initiator command with the following items:
– GUID of the host (from Step a)
– GUID extension of the host (always 00:00:00:00:00:00:00:00)
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-35
Chapter 2
Booting from a Fibre Channel SAN
Booting an Image
– description keyword
– Text description, enclosed in quotation marks
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
description "test-initiator"
g.
Return to privileged EXEC mode by entering the exit command.
SFS-3012R(config)# exit
SFS-3012R#
h.
Display the WWPNs of the Fibre Channel gateway ports that point to the host.
Enter the show fc srp initiator command with the following items:
– GUID of the host (from Step a)
– GUID extension of the host (always 00:00:00:00:00:00:00:00)
SFS-3012R# show fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
================================================================================
SRP Initiators
================================================================================
guid: 00:05:ad:00:00:00:17:3c
extension: 00:00:00:00:00:00:00:00
description: test-initiator
wwnn: 20:02:00:05:ad:00:00:00
credit: 0
active-ports: none
pkeys:
bootup-target: 00:00:00:00:00:00:00:00
bootup-lu: 00:00:00:00:00:00:00:00
action: auto-bind
result: success
wwpns: port
wwpn
fc-addr
2/1
20:02:00:05:ad:20:00:00 00:00:00
2/2
20:02:00:05:ad:24:00:00 00:00:00
3/1
20:02:00:05:ad:30:00:00 00:00:00
3/2
20:02:00:05:ad:34:00:00 00:00:00
4/1
20:02:00:05:ad:40:00:00 00:00:00
4/2
20:02:00:05:ad:44:00:00 00:00:00
5/1
20:02:00:05:ad:50:00:00 00:00:00
5/2
20:02:00:05:ad:54:00:00 00:00:00
6/1
20:02:00:05:ad:60:00:00 00:00:1d
6/2
20:02:00:05:ad:64:00:00 00:00:1d
7/1
20:02:00:05:ad:70:00:00 00:00:00
7/2
20:02:00:05:ad:74:00:00 00:00:00
8/1
20:02:00:05:ad:80:00:00 00:00:00
8/2
20:02:00:05:ad:84:00:00 00:00:00
9/1
20:02:00:05:ad:90:00:00 00:00:00
9/2
20:02:00:05:ad:94:00:00 00:00:00
10/1
20:02:00:05:ad:a0:00:00 00:00:00
10/2
20:02:00:05:ad:a4:00:00 00:00:00
11/1
20:02:00:05:ad:b0:00:00 00:00:00
11/2
20:02:00:05:ad:b4:00:00 00:00:00
12/1
20:02:00:05:ad:c0:00:00 00:00:00
12/2
20:02:00:05:ad:c4:00:00 00:00:00
13/1
20:02:00:05:ad:d0:00:00 00:00:00
13/2
20:02:00:05:ad:d4:00:00 00:00:00
i.
Record the WWPN of the Fibre Channel gateway port that connects the host to the storage.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-36
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Booting an Image
j.
Verify that the host can see the target that contains the bootable image. If the WWPN of the boot
target does not appear in the command output, give the gateway some time to configure the ITs and
retry the command.
Enter the show fc srp initiator-wwpn-view command with the following items:
– WWPN of the port (from Step i)
– target keyword
SFS-3012R# show fc srp initiator-wwpn-view 20:02:00:05:ad:60:00:00 target
================================================================================
SRP Targets Accessible to Initiator Via Port WWN 20:02:00:05:ad:60:00:00
================================================================================
wwpn: 21:00:00:04:cf:f6:c2:ab
wwnn: 20:00:00:04:cf:f6:c2:ab
description: SRP.T10:21000004CFF6C2AB
ioc-guid: 00:05:ad:00:00:00:15:1a
service-name: SRP.T10:21000004CFF6C2AB
protocol-ids: 04:00:00:00:00:00:00:00:00:00
fc-address: 00:00:23
mtu: 0
connection-type: nl-port
physical-access: 6/1
k.
Return to global configuration mode by entering the configure terminal command.
SFS-3012R# configure terminal
SFS-3012R(config)#
l.
Grant the host access to the target from which your host will boot (through the port).
Enter the no fc srp it command with the following items:
– GUID of the host (from Step a)
– GUID extension of the host (always 00:00:00:00:00:00:00:00)
– WWPN of the target that stores the bootable image
– gateway-portmask-policy keyword
– restricted keyword
– Fibre Channel gateway port that connects the host to the storage (in slot#/port# format)
SFS-3012R(config)# no fc srp it 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
21:00:00:04:cf:f6:c2:ab gateway-portmask-policy restricted 6/1
m.
Configure ITLs to which the host belongs. The ITLs inherit the portmask policy of the IT.
Enter the fc srp initiator command with the following items:
– GUID of the host (from Step a)
– GUID extension of the host (always 00:00:00:00:00:00:00:00)
– discover-itl keyword
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
discover-itl
n.
Grant the host access to the LUN from which your host boots.
Enter the no fc srp itl command with the following items:
– GUID of the host (from Step a)
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-37
Chapter 2
Booting from a Fibre Channel SAN
Booting an Image
– GUID extension of the host (always 00:00:00:00:00:00:00:00)
– WWPN of the target that stores the bootable image
– LUN ID of the LUN that stores the bootable image
– lun-policy keyword
– restricted keyword
SFS-3012R(config)# no fc srp itl 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
21:00:00:04:cf:f6:c2:ab 00:00:00:00:00:00:00:00 lun-policy restricted
o.
Configure the LUN as the WKSN of your host.
Enter the fc srp initiator command with the following items:
– GUID of the host (from Step a)
– GUID extension of the host (always 00:00:00:00:00:00:00:00)
– bootup keyword
– target keyword
– WWPN of the target that stores the boot image.
– lu keyword
– LUN ID of the LUN that stores the boot image
SFS-3012R(config)# fc srp initiator 00:05:ad:00:00:00:17:3c 00:00:00:00:00:00:00:00
bootup target 21:00:00:04:cf:f6:c2:ab lu 00:00:00:00:00:00:00:00
Step 4
Boot your host.
Note
If the host does not boot successfully, reboot the host and enter interactive mode, then configure
the boot order to begin with SRP boot or WKSN.
Using Element Manager
To use Element Manager, perform the following steps:
Step 1
Remove or reconfigure any host that runs the existing image. Only one host on your network can boot a
specific image.
Step 2
Physically connect your new host to your server switch.
Step 3
Configure an ITL.
Note
To install an image with VFrame, do not configure ITLs manually.
a.
Open your host and record the GUID from the label on your HCA. Alternatively, you can boot your
host and press the x key when the Type ‘x’ to configure boot options prompt appears during the boot
process. The GUID of the host appears in the host display. Record the GUID and leave the host at
this screen. You may refresh the screen later in this process.
b.
Launch Element Manager and open your server switch.
Cisco SFS Boot over InfiniBand User Guide for Linux
2-38
OL-12368-01
Chapter 2
Booting from a Fibre Channel SAN
Booting an Image
c.
From the FibreChannel menu, select Storage Manager. The Storage Manager window opens.
d.
Click the SRP Hosts folder in the navigation tree.
e.
Click the Define New button. The Define New SRP Host window opens.
f.
Enter the GUID of your host (from Step a) in the Host GUID field.
g.
(Optional) Enter a text description for the host in the Description field.
h.
Click the Next > button.
i.
Click the Finish button. The new initiator appears under the SRP Hosts folder.
j.
Click the new initiator under the SRP Hosts folder, and then click the Targets tab.
k.
Verify that the target that stores the image that you want to boot appears in the list.
l.
Double-click the target in the list where you want to install the image. The IT Properties window
opens.
m.
Click the ... button next to the Port Mask field. The Select Ports window opens.
n.
Click the button of the port that connects the host to the storage, and then click OK.
o.
Click the Apply button in the IT Properties window, and then close the window.
p.
Click the LUN Access tab, and then click the Discover LUNs button. The targets that your server
switch sees appear in the Available LUNs column.
q.
Click the target that stores the image that you want to boot, and then click the Add > button.
r.
Click the Apply button.
s.
(Optional but recommended) Configure the WKSN.
– Return to the Storage Manager window of Element Manager and click the General tab.
– From the Boot Target WWPN field, select the boot target from the drop-down menu or manually
enter it.
– From the Boot FC LUN field, select the boot LUN from the drop-down menu or manually enter
it.
– Click the Apply button.
Step 4
Boot your host.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
2-39
Chapter 2
Booting from a Fibre Channel SAN
Booting an Image
Cisco SFS Boot over InfiniBand User Guide for Linux
2-40
OL-12368-01
C H A P T E R
3
Booting from PXE
This chapter includes the following sections:
•
About Booting from PXE, page 3-1
•
Configuring Boot over PXE, page 3-2
About Booting from PXE
This section describes the Cisco BoIB using PXE and includes a high-level overview of the boot process
followed by a detailed step-by-step configuration procedure.
This section includes the following topics:
•
Hardware Setup for PXE Boot Process
•
Overview of the PXE Boot Process
Hardware Setup for PXE Boot Process
The hardware setup used for the following example consists of one IB host booting RHEL3 and one
server running RHEL3 providing DHCP, TFTP, and NFS services.
These services could be provided by a single RHEL3 node or separate network nodes connected either
to the IB or Ethernet network. This document describes both cases. If some of the services are provided
by Ethernet node, an Ethernet gateway is required. The Ethernet gateway configuration is described in
the “Configuring the Ethernet Gateway” section on page 3-8.
Overview of the PXE Boot Process
This section contains an overview of the PXE boot process. See Figure 3-1 for a sample hardware setup.
The system follows the following procedure to boot over PXE:
1.
The host BIOS reads the configuration from nonvolatile memory to determine the boot device order.
In order to boot over IB using PXE, the first entry for the boot order should be PXE by default. Use
the tvflash -o command to set the boot order without entering the BIOS, as described in Configuring
the Booting Host, page 3-5.
2.
The host BIOS sends a DHCP request to a PXE-enabled DHCP server to obtain initial configuration
and boot parameters, IP address, and boot loader filename.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
3-1
Chapter 3
Booting from PXE
Configuring Boot over PXE
3.
The host BIOS loads the boot loader from TFTP server and starts it.
4.
Boot loader reads its configuration file from TFTP server and parses it to get boot options, Linux
kernel, and initrd filenames.
5.
The boot loader loads the Linux kernel and executes it, passing some options from the configuration
file.
6.
The Linux kernel performs the initialization procedures and loads the initrd image from the TFTP
server as a temporary root file system before mounting the root file system.
7.
The initrd image startup script starts and loads the IB stack and IPoIB driver. This process changes
the root file system to an NFS volume.
8.
The Linux initialization continues with the NFS root file system, using the IPoIB interface until it
is up and running.
Configuring Boot over PXE
This section describes how to perform PXE boot with the BoIB feature.
To perform a PXE boot with the BoIB feature (BoIB-PXE), you must perform the steps described in the
following sections:
•
Verifying Prerequisites, page 3-2
•
Performing Hardware Setup, page 3-3
•
Checking the HCA Firmware Version, page 3-4
•
Configuring the Booting Host, page 3-5
•
Configuring the DHCP Server, page 3-6
•
Configuring the TFTP Server, page 3-7
•
Configuring the Boot Loader, page 3-7
•
Configuring the Ethernet Gateway, page 3-8
Verifying Prerequisites
The following requirements must be met to perform a boot over PXE:
•
A host with a Cisco HCA.
•
A server with a PXE-enabled Cisco HCA. The boot server provides DHCP, TFTP, and NFS services.
These services could be provided by a single node or separate network nodes connected either to the
IB or Ethernet network. This document describes both cases. If some of the services are provided
by an Ethernet node, an Ethernet gateway is required.
•
A server switch, such as an SFS 3001 Server Switch or an SFS 3012R Server Switch, with an
optional Ethernet gateway.
Cisco SFS Boot over InfiniBand User Guide for Linux
3-2
OL-12368-01
Chapter 3
Booting from PXE
Configuring Boot over PXE
Performing Hardware Setup
To perform the hardware setup, perform the following steps:
Step 1
Install the HCAs into your host and server.
For details, see the Cisco SFS InfiniBand Host Drivers User Guide for Linux.
Note
The HCAs listed in Table 3-1 support the BoIB feature. To verify that your HCA supports BoIB,
enter the tvflash -i command and verify that the word Cougarcub or Lioncub appears in the
output.
Table 3-1
HCAs and their HCA Codenames in Output
Cisco Product ID
HCA Codename in Output
SFS-HCA-X2T7-A1
Cougarcub
SFS-HCA-X2T7R-A1
Cougarcub - RemoteBoot
SFS-HCA-X2S7-A1
Cougarcub
SFS-HCA-X2S7R-A1
Cougarcub - RemoteBoot
SFS-HCA-E2T7-A1
Lioncub
SFS-HCA-E2T7R-A1
Lioncub - RemoteBoot
SFS-HCA-E2S7-A1
Lioncub
SFS-HCA-E2S7R-A1
Lioncub - RemoteBoot
Step 2
Install and connect all required hardware.
Step 3
Connect the HCA to an IB port on your server switch.
Figure 3-1 shows a sample hardware setup for the boot process.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
3-3
Chapter 3
Booting from PXE
Configuring Boot over PXE
Figure 3-1
Sample Boot over PXE Hardware Setup
Boot Server
PXE-enabled
firmware
on HCA
RHEL3
Connect the boot server either
directly to InfiniBand or to an
Ethernet network, but use the
same IP subnet as the boot host.
In case of an Ethernet-based boot
server, an Ethernet gateway is
used to bridge the IP subnet.
Services
Optional
Ethernet
router
DHCP,
TFTP, and
NFS services
Use an Ethernet
gateway to bridge
the IP subnet
Connect optional
Ethernet gateway
directly to Ethernet
host or to optional
Ethernet router
SFS 3012R Switch
Boot Host
The first port
of the HCA is
connected to
the InfiniBand
switch
* These services could be
provided by a single node
or separate network nodes
connected either to the
InfiniBand or Ethernet
network.
- If some of the services
are provided by an Ethernet
node, an Ethernet gateway
is required.
RHEL3
181862
Diskless station
with InfiniBand HCA
Checking the HCA Firmware Version
To verify that your HCA provides the BoIB feature, enter the /usr/local/topspin/sbin/tvflash -i
command from the host CLI. If .Boot appears in the description of your HCA, the HCA includes the
BoIB feature.
If your HCA does not run BoIB firmware, update the HCA. For instructions, see the Cisco SFS
InfiniBand Host Drivers User Guide for Linux.
The following example shows how to check the HCA firmware version:
host1# /usr/local/topspin/sbin/tvflash -i
HCA #0: MT23108, Cougar Cub, revision A1
Primary image is v3.5.000 build 3.2.0.118, with label 'HCA.CougarCub.A1.Boot'
Secondary image is v3.5.000 build 3.2.0.106, with label 'HCA.CougarCub.A1.Boot'
Vital Product Data
Cisco SFS Boot over InfiniBand User Guide for Linux
3-4
OL-12368-01
Chapter 3
Booting from PXE
Configuring Boot over PXE
Product Name: Cougar cub
P/N: MHXL-CF128-T
E/C: C-00
S/N: MT0420F00221
Freq/Power: N/A
Checksum: Ok
Date Code: N/A
Note
The firmware is available on the BoIB ISO image. For instructions on how to upgrade your firmware,
see the Cisco SFS InfiniBand Host Drivers User Guide for Linux.
Configuring the Booting Host
The host drivers provide a feature, tvflash -o, that allows you to change the default boot option without
using the boot ROM itself. If you decide to set the default option without using the automatic tvflash -o
option, you can do this manually. The procedure is BIOS-dependent. Set the boot device order so that
the BIOS selects boot over PXE to boot. This step requires you to enter the motherboard setup program,
find the menu item specifying the boot order, and change it accordingly, as required.
To configure the booting host, perform the following steps:
Step 1
Display the current default boot option by entering the tvflash -o command.
host1# /usr/local/topspin/sbin/tvflash -o
auto_upgrade=yes
boot_enable_port_1=yes
boot_enable_port_2=yes
boot_service_scan=yes
boot_type=well_known
boot_saved_port=0
boot_saved_ioc_num=0
boot_saved_dgid=0000:0000:0000:0000:0000:0000:0000:0000
boot_saved_service_name=0000:0000:0000:0000
Step 2
Locate the boot_type field. In this example, the boot_type is set to well_known, so the boot hosts try the
WKSN option by default.
Step 3
Change the default boot option to PXE, if the default boot_type is not PXE, by entering the tvflash -o
boot_type=pxe command.
Set the value to pxe. You need to use a boot ROM that is PXE-capable.
host1# /usr/local/topspin/sbin/tvflash -o boot_type=pxe
Writing [============================================================]
host1# /usr/local/topspin/sbin/tvflash -o
auto_upgrade=yes
boot_enable_port_1=yes
boot_enable_port_2=yes
boot_service_scan=yes
boot_type=pxe
boot_saved_port=0
boot_saved_ioc_num=0
boot_saved_dgid=0000:0000:0000:0000:0000:0000:0000:0000
boot_saved_service_name=0000:0000:0000:0000
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
3-5
Chapter 3
Booting from PXE
Configuring Boot over PXE
Configuring the DHCP Server
To configure the DHCP server, perform the following steps:
Step 1
Verify that the DHCP server supports PXE extensions.
The following example shows how to configure a Linux DHCP server.
Include a section describing the IP subnet of the booting host in the DHCP server configuration
/etc/dhcpd.conf file. The minimum required information is as follows:
ddns-update-style none;
subnet 40.0.0.0 netmask 255.255.0.0 {
next-server 40.0.0.101;
filename "/pxelinux.0";
range dynamic-bootp 40.0.0.50 40.0.0.100;
always-broadcast on;
}
The important options are next-server, filename, and always-broadcast.
Step 2
•
The next-server and filename options specify the TFTP server and filename of the initial boot loader.
•
The always-broadcast option must be turned on. As part of the DHCP over IB specification, and as
a requirement for the IB DHCP client to acquire the IP address, turning on the always-broadcast
option causes the DHCP server to broadcast the DHCP OFFER reply, instead of unicast. IP
addresses and ranges can be changed to match the target setup.
Note
The broadcast option must be specified even if the DHCP server is on the Ethernet network.
(Optional) Limit the DHCP server to specific IP interfaces by including the following statement in the
/etc/sysconfig/dhcpd file:
DHCPDARGS=interface
In this example, the DHCP server is active only on the ib0 interface.
host1# /etc/sysconfig/dhcpd DHCPDARGS="ib0 lo0"
Step 3
Activate the DHCP server after the configuration files are prepared. To start the server, use the service
dhcpd start command as root.
host1# # service dhcpd start
Starting dhcpd:
[ OK ]
Step 4
Make the DHCP configuration persistent across reboots by using the chkconfig command.
host1# chkconfig --list dhcpd
dhcpd
0:off
1:off
Step 5
2:on
3:on
4:on
5:on
6:off
Verify that the DHCP server is running.
host1# ps -ef | grep dhcp
root
4069
1 0 12:06 ?
00:00:00 /usr/sbin/dhcpd ib0 lo0
Cisco SFS Boot over InfiniBand User Guide for Linux
3-6
OL-12368-01
Chapter 3
Booting from PXE
Configuring Boot over PXE
Configuring the TFTP Server
This section describes how to configure the TFTP server.
Note
The steps in this section assume you are using the Linux tftp-server package as a TFTP server.
In this procedure, the setup tftp service is handled by the xinetd daemon. The corresponding xinetd
configuration file must be edited in order to enable the service. The steps that follow show a sample of
the /etc/xinetd.d/tftp file:
Step 1
Enable TFTP service. Edit the xinetd.d file to enable TFTP service with root directory /tftpboot. All file
paths must be relative to this directory.
service tftp
{
socket_type
protocol
wait
user
server
server_args
disable
per_source
cps
flags
}
Step 2
=
=
=
=
=
=
=
=
=
=
dgram
udp
yes
root
/usr/sbin/in.tftpd
-s /tftpboot
no
11
100 2
IPv4
Activate the configuration by restarting the inetd daemon.
# service xinetd restart
Stopping xinetd:
Starting xinetd:
[
[
OK
OK
]
]
The TFTP service is now active and the initial boot loader, Linux kernel, and initrd image can be placed
under the TFTP root directory.
Configuring the Boot Loader
This section describes how to configure the boot loader. Only the PXE boot loader is used. The filename
is pxelinux.0.
Note
The boot loader used in this example is from syslinux distribution http://syslinux.zytor.com.
To configure the boot loader, perform the following steps:
Step 1
Copy the boot loader file to the tftpboot directory stated in the DHCP configuration file.
The boot loader expects to find its configuration file on the TFTP server under the pxelinux.cfg directory.
Step 2
Create /tftpboot/pxelinux.cfg directory and create a configuration file.
The boot loader configuration could be for a specific host, for a group of hosts, or for all hosts.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
3-7
Chapter 3
Booting from PXE
Configuring Boot over PXE
To create individual configuration files, the filename must match the corresponding host IP address as a
32-bit hex number. For example, for a host with IP address 40.0.0.99, the filename would have to be
28000063.
To create a single configuration file for use by all hosts (as in the example below), the filename must be
default.
The following example shows how to configure the boot loader to load the Linux kernel with the
filename linux and initrd image filename initrd from the /tftpboot directory on the TFTP server. The
example also shows how some kernel parameters are passed to the Linux kernel.
serial 0 38400
default rhel3
prompt 1
timeout 100
label rhel3
kernel linux
append root=/dev/cciss/c0d0p3 initrd=initrd console=ttyS0,38400
Configuring the Ethernet Gateway
This section illustrates how to configure the Ethernet gateway. If you have configured your services so
that DHCP, TFTP, or NFS servers are on the Ethernet network, an Ethernet gateway must be configured
to bridge the IP subnet.
The following sample configuration is for an Ethernet gateway located in an SFS 3012R Server Switch:
•
The Ethernet gateway is installed in slot 6.
•
One bridging group is configured between Ethernet port 5 on the gateway and the second IB port,
which is internal.
•
No VLAN tagging is configured and the default partition key (P_KEY) is used on the IB side.
•
The broadcast forwarding must be enabled in order for the DHCP server to work across the gateway.
SFS-3012R# configure
SFS-3012R(config)# bridge-group 2 subnet-prefix 40.0.0.0 16
SFS-3012R(config)# bridge-group 2 broadcast-forwarding
SFS-3012R(config)# interface ethernet 6/5
SFS-3012R(config)# bridge-group 2
SFS-3012R(config)# interface gateway 6/2
SFS-3012R(config-if-gw-2/2)#)# bridge-group 2
SFS-3012R(config-if-gw-2/2)#)# exit
Cisco SFS Boot over InfiniBand User Guide for Linux
3-8
OL-12368-01
A P P E N D I X
A
Acronyms and Abbreviations
Table A-1 defines the acronyms and abbreviations that are used in this guide.
Table A-1
List of Acronyms and Abbreviations
Acronym
Expansion
API
Application Program Interface
BIOS
Basic Input/Output System
BoIB
Boot over InfiniBand
DHCP
Dynamic Host Configuration Protocol
GUID
globally unique identifier
HCA
host channel adapter
IB
InfiniBand
IPoIB
IP over InfiniBand
IT
Initiator/Target
ITL
Initiator/Target/LUN
LU
logical unit
LUN
logical unit number
NFS
Network File System
PXE
Pre-boot Execution Environment
RAID
Redundant Array of Independent Disks
RDMA
Remote Direct Memory Access
RHEL3
Red Hat Enterprise Linux 3
RHEL4
Red Hat Enterprise Linux 4
ROM
read-only memory
SAN
storage area network
SCSI
Small Computer System Interface
SLES
SUSE Linux Enterprise Server by Novell
SRP
SCSI RDMA Protocol
TFTP
Trivial File Transfer Protocol
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
A-1
Appendix A
Table A-1
Acronyms and Abbreviations
List of Acronyms and Abbreviations (continued)
Acronym
Expansion
VLAN
virtual local area network
WKBS
Well Known Boot Service
WKSN
Well Known Service Name
WWPN
worldwide port name
Cisco SFS Boot over InfiniBand User Guide for Linux
A-2
OL-12368-01
INDEX
DHCP
A
3-1
DHCP OFFER reply
accessible LUNs
2-5
always-broadcast option
ATA drive
audience
diskless host
3-6
2-35
document
2-17
audience
v
v
conventions
vi
organization
vi
related
B
3-6
vii
driverdisk parameter
BIOS
2-10
Driver Disk Source
3-1
2-13
BoIB
description
firmware
1-1
E
2-3, 3-4
ISO image
methods
2-3
Element Manager
1-1
boot, FC LUN
launch
2-5, 2-39
bootable image
2-4
window
2-4
Ethernet
bootloader
3-2
network
boot menu
2-4
node
Boot ROM menu
2-4
2-18
3-2
3-1, 3-2
extensions, PXE
3-6
Boot Target
WWPN
2-5, 2-39
F
Fibre Channel
C
gateway
CD ROM
Cisco HCA
2-2
storage
3-2
1-1
1-1, 2-2, 2-8, 2-37
2-1, 2-34
storage device
conventions, document
vi
firmware
version
2-2
1-1
2-3
D
daemon, inetd
daemon, xinetd
3-7
3-7
G
Gateway Port Access
2-4
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
IN-1
Index
global access, restrict
global configuration mode
enter
new
2-6, 2-8
2-1, 2-37
2-6
2-35
globally unique identifier. See GUID.
GUID
extension
host
configure
2-3, 2-5
2-9
Keyboard, Video, Mouse device. See KVM device.
2-37
Kickstart
host display
record
K
2-4, 2-6
2-35
2-10
Kickstart configuration file
KVM device
H
2-10
2-2
L
HCA
1-1
Linux
BoIB firmware
2-35
kernel
check firmware
2-3
kernel upgrade
host
2-2
3-2
logical unit. See LU.
remote boot
2-3, 2-5
logical unit number. See LUN.
verification
3-4
LU
Host Channel Adapter. See HCA.
bootable image
Host GUID
logical ID
2-4
LUN
ID
IB
2-9
2-4
2-9
install image
description
fabric
M
3-2
InfiniBand. See IB.
mode
Initiator/Target. See IT.
global configuration
Initiator/Target/LUN. See ITL.
enter
initrd image
return
3-2
Insert Driver Disk
IP subnet
2-9
1-1
1-1
network
2-5
1-1
access
I
ISO
2-2
2-13
2-35
2-6
2-8
privileged EXEC, enter
2-6, 2-35
3-6
2-10
N
IT
configure
new
2-37
2-6
ITL
Network File System. See NFS.
network interface
2-15
NFS
Cisco SFS Boot over InfiniBand User Guide for Linux
IN-2
OL-12368-01
Index
install
services
setup
fabric
2-10, 2-14, 2-18
2-2
switch
3-1
SCSI
2-16
2-2
1-1
SCSI RDMA Protocol. See SRP.
server switch
O
2-4
SLES
organization, document
installation
vi
SLES9
2-29, 2-34
2-18
Small Computer System Interface. See SCSI.
P
SRP
platform prerequisites
boot
1-2
2-34
Port Mask, field
2-4, 2-39
drive
2-17
portmask policy
2-8
hosts
2-4, 2-39
Pre-boot eXecution Environment. See PXE.
startup script
privileged EXEC mode
storage area network. See SAN.
enter
2-6, 2-35
programmable switching fabric
2-1
3-2
Storage Manager
2-4
storage mapping
1-2
syslinux distribution
PXE
extensions
using
3-6
3-1
T
Targets
R
TFTP
RAID
3-7
2-4
3-1
2-5
read-only memory. See ROM.
U
Red Hat Enterprise Linux 3. See RHEL3.
Red Hat Enterprise Linux 4. See RHEL 4.
unicast
3-6
Redundant Array of Independent Disks. See RAID.
related documentation
remote boot, HCA
vii
2-3
restrict, global access
2-5
V
VFrame
2-6
RHEL3
2-10
software
RHEL4
2-10
VFrame Director
ROM
2-18
S
VLAN
2-1
2-1
3-8
W
SAN
1-1
Well Known Boot Service. See WKBS.
Cisco SFS Boot over InfiniBand User Guide for Linux
OL-12368-01
IN-3
Index
Well Known Service Name. See WKSN.
WKBS
2-17
WKSN
configure
2-38
configure boot order
default
2-38
3-5
host
2-9
use
2-34
worldwide port name. See WWPN.
WWPN
boot target
host
2-7
port
2-7
record
target
2-5
2-36
2-4, 2-9, 2-37
Cisco SFS Boot over InfiniBand User Guide for Linux
IN-4
OL-12368-01