Booting Linux from an iSCSI Target Ethernet
Contents
1. 10 Appendix A Sanity 12 CHECK eie Ee ooo 12 A 2 DHCP Configuration for PXELINUX with 13 Pot Jpxelinibcrg delQulbzs stereo eR it ads te haustus ee Od atas edu de desta Danus ug Rode 14 A 4 DHCP Configuration for iSCSI Boot with FlexBoot PXE SAN 14 Appendix B SAN Booting with FlexBoot in CHAP Environment 15 Mellanox Technologies Confidential Rev 1 0 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target Preface About this Manual This User Guide provides guidance for booting diskless PXE clients to RHEL6 4 from remote storage over iSCSI using Mellanox Network technology card and boot agent FlexBoot over Ethernet Network The setting up and configuration of the iSCSI target and PXE server as described within this document are merely recommendations and provided as 1 and may be applied according to requirements of the environment in which the actual work takes place The actions described in this paper are focused on Mellanox Network technology solution Document Conventions The following lists conventions used in this document NOTE Identifies important information that contains helpful suggestions X CAUTION Alerts you to the risk of personal injury system2. list eO chcp oamemerermeoueeudumst du meros cur oo eee ceris option domain nane operon doman Ser c oi default lease time 86400 1 day max lease time 86400 serv od c Ll 8 2 Mellanox Technologies Confidential Rev 1 0 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target A 3 A 4 E fixed address 12 7 6 70 7 hardware ethernet 00 02 9 32 8 80 nexbt server 12 7 6 30 if option client system architecture 00 00 filename pxelinux 0 pxelinux cfg default cabe var LABEL rh6 4x64 instl manual MENU LABEL Manual Installation RHEL6 4 KERNEL RHEL6 4 x86 64 DVDl images pxeboot vmlinuz APPEND initrd RHEL6 4 x86 64 DVDl images pxeboot initrd img DHCP Configuration for iSCSI Boot with FlexBoot PXE SAN Boot Modify the following host declaration in your DHCP configuration file to allow PXE SAN Boot kost OO d hardware ethernet 00 02 9 32 8 80 14 Mellanox Technologies Confidential Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target User Manual Rev 1 0 Appendix B SAN Booting with FlexBoot in CHAP Environment For Successful SAN Booting with FlexBoot in CHAP environment the FlexBoot in use
3. usc deer Disk dev sda 500 1 GB 500107862016 bytes 255 heads 63 sectors track 60801 cylinders 15065 5 2 619222 90 Sector size 512 bytes 512 bytes size 9512 byten 512 2 Device Boot Start End Blocks Id System dev sdal 1 1048576 mnc dev sda2 20681 20480000 So dev sda3 25 oul 2086 2048000 82 Linux swap polaris Disk dev sdb 21 5 GB 21478670336 bytes 64 heads 32 sectors track 20483 cylinders Units cylinders of 2048 512 1048576 bytes Sector suze logical physica S12 S02 bytes I O size minimum optimal 512 bytes 512 bytes Dio lt M eee m 100 00 TORNO A 2 DHCP Configuration for PXELINUX with FlexBoot The following DHCP configuration is presented as is and may not work in all environments authoritative ddns update style none ddns updartes oni allow Seonp always reply rfc1048 off Poot unknown clients On option client system architecture code 93 unsigned integer 16 Opt ron vendor cmt qe cade dA option vendor class identifier code 60 string Glass PX T eng Mareen ik mine WOM Eoin ODE OI Vendor v Po Gale ems y opteron wendor cncapsulaked oprrons 00 91 08 option
4. Fresh Installation b Choose this option to install a fresh copy of Red Hat Enterprise Linux on your system Existing software and data may be overwritten depending your configuration choices Upgrade an Existing Installation P m Choose this option if you would like to upgrade your existing Red Hat Enterprise Linux system This d option will preserve the existing data on your storage device s EN J Mellanox Technologies Confidential Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target User Manual Rev 1 0 13 Select the Use All Space option Which Ne of installation would you like Use All Space Removes of partibons on the selected Gevicets This inches partitions created by other operating sy Sterns Tig This ogton will remove data from the selected deveeis sure you have backups Replace Existing Linux System s Removes Linus parutions Created trem previous Linus instaltanee Ths Goes not remove other partitions you have on your storage deviens such as or FAT 32 Tig Thus will remove data from the selected aevceis sure you heve Shrink Current System Shrink exiting parties to create free space for the defaut layout Use Free Space Retains your Current data and partitions and uses only the onpartitioned space on the selected device 4 you hare enough free space avadabic Create Custom Layout Manualy cr
5. discovery authentication do you wish to perform CHAP pair CHAP Usemame CHAP Password Cancel start Discovery iSCSI Discovered Nodes Check the nodes you wish to log into O Node Name Interface 1qn 2013 10 qalab com sqaQ030 prt9 p2pl Cancel Lagin 15051 Nodes Login What kind of iSCSI login authentication do you wish to perform CHAP pair 2 CHAP Userna meljoe CHAPPasswoi ee eee Cancel Login iSCSI Login Results successfully lagged in and attached the following nodes iqn 2013 10 qalab com 5qa030 prt9 via p2p1 _ WV Mellanox Technologies Confidential
6. Active network interfaces Configure Network gt Add drive 7 Enter the IP address of iSCSI target Optionally you may choose to enter a customized Initiator Name and select the necessary CHAP authentication of choice Refer to SAN Booting with FlexBoot in CHAP Environment In the example below iSCSI Initiator Name is left with the default value given by the installer and iSCSI discovery authentication is left with No authentication iSCSI Discovery Details To use iSCSI disks you must provide the address of your iSCSI target and the iSCSI initiator name you ve configured for your host Target IP Address 12 7 6 30 iSCSI Initiator 23 ee ee What kind of SCS discovery authentication do you wish to perform c No authentication Cancel Start Discovery 8 Check the relevant Node Name to log in If as a result of the discovery multiple Node Names are found select the one that is relevant to you iSCSI Discovered Nodes Check the nodes you wish to log into Node Name Interface vi 19 n 2013 10 qalab com sqa030 prt9 etho iqn 2013 10 qgalab com sqa030 prtg etho iqn 2013 10 galab com 5qa030 prt9 iqn 2013 10 galab com sqa030 prt9 etho iqgn 2013 10 qaiab com sqa030 prtg etho 7 Mellanox Technologies Confidential Rev 1 0 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target 9 Click Login A successful login is mandatory to proceed A failure at this stage 1s probab
7. H DAMAGE Mellanox TECHNOLOGIES Mellanox Technologies Mellanox Technologies Ltd 350 Oakmead Parkway Suite 100 Beit Mellanox Sunnyvale CA 94085 PO Box 586 Yokneam 20692 U S A Israel www mellanox com www mellanox com Tel 408 970 3400 Tel 972 0 74 723 7200 Fax 408 970 3403 Fax 972 0 4 959 3245 Copyright 2013 Mellanox Technologies All Rights Reserved Mellanox Mellanox logo BridgeX ConnectX CORE Direct InfiniBridge InfiniHost InfiniScale MLNX OS PhyX SwitchX UFM Virtual Protocol Interconnect and Voltaire are registered trademarks of Mellanox Technologies Ltd Connect IB ExtendX FabricIT Mellanox Open Ethernet Mellanox Virtual Modular Switch MetroXTM MetroDX ScalableHPC Unbreakable Link are trademarks of Mellanox Technologies Ltd All other trademarks are property of their respective owners 2 Document Number MLNX 15 1 544 Mellanox Technologies Confidential Contents Rev 1 0 Contents xir RC 4 1 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target 5 1 1 Configuring the iSCSI Target 5 1 2 Installing RHEL6 4 on a Remote Storage over 5 6 1 3 SAN Booting the Diskless Client with
8. Mellanox TECHNOLOGIES Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target User Manual Rev 1 0 www mellanox com Mellanox Technologies Confidential NOTE THIS HARDWARE SOFTWARE OR TEST SUITE PRODUCT PRODUCT S AND ITS RELATED DOCUMENTATION ARE PROVIDED BY MELLANOX TECHNOLOGIES AS IS WITH ALL FAULTS OF ANY KIND AND SOLELY FOR THE PURPOSE OF AIDING THE CUSTOMER IN TESTING APPLICATIONS THAT USE THE PRODUCTS IN DESIGNATED SOLUTIONS THE CUSTOMER S MANUFACTURING TEST ENVIRONMENT HAS NOT MET THE STANDARDS SET BY MELLANOX TECHNOLOGIES TO FULLY QUALIFY THE PRODUCTO S AND OR THE SYSTEM USING IT THEREFORE MELLANOX TECHNOLOGIES CANNOT AND DOES NOT GUARANTEE OR WARRANT THAT THE PRODUCTS WILL OPERATE WITH THE HIGHEST QUALITY ANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANTABILITY FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT ARE DISCLAIMED IN NO EVENT SHALL MELLANOX BE LIABLE TO CUSTOMER OR ANY THIRD PARTIES FOR ANY DIRECT INDIRECT SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES OF ANY KIND INCLUDING BUT NOT LIMITED TO PAYMENT FOR PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY FROM THE USE OF THE PRODUCT S AND RELATED DOCUMENTATION EVEN IF ADVISED OF THE POSSIBILITY OF SUC
9. P TFTP and NFS server for PXE clients e Both servers have a Mellanox ConnectX 3 based IOGE NIC equipped with PXE boot capabilities via Expansion ROM called FlexBoot of version 3 4 149 1 1 Configuring the iSCSI Target Machine gt To configure the iSCSI target 1 Download the IET target software from http sourceforge net projects iscsitarget files iscsitarget 1 4 20 2 2 Install iSCSI target and additional required software on target server root sqa030 yum install kernel devel openssl devel gcc rpm build root sga030 cd tmp tmp Car cu cec c APP secu ser idee eoot sqa0s0 EIDOMCedewsesibarget Tod 720927 root sqa030 iscsitarget 1 4 20 2 make amp amp make install 3 Create the IQN in the ietd configuration file root sqa030 vi etc iet ietd conf Optional for CHAP authentication uncomment the following lines IncomingUser joe secret fOutgoingUser jack 12charsecret Target ES ais com Lun Path dev cciss c0d0p9 Type fileio IOMode wb ImmediateData Yes MaxConmnectsons Torna MTS Mellanox Technologies Confidential Rev 1 0 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target The local Hard Disk partition assigned to the LUN dev cciss cOdOp9 in the example Ah above must not contain any valuble data as this data will be destroyed by the installation process taking place later in this procedure 4 Edit the etc sysconfig iscsi target fil
10. Performance Tools Perl Support Printing client Ruby Support GE Scientific support 8 Security Tools 8 Smart card support pols iSCSI Storage Client Software designed for supporting clustering and grid connectivity using RDMA based InfiniBand and iWARP fabrics Optional packages selected 12 of 20 Optional packages 19 Click Next Allow the installation to reach completion 1 3 SAN Booting the Diskless Client with FlexBoot When the installation process is completed the client will ask to reboot At that point the DHCP server configuration for that client needs to be changed so that when it PXE boots again it will get the root path IQN and LUN information from the DHCP server For further information please refer to section DHCP Configuration for iSCSI Boot with FlexBoot PXE SAN Boot NOTE Restart your DHCP service after changing the dhcp configuration file e Reboot the system Congratulations your Red Hat Enterprise Linux installation is complete Please reboot to use the installed system Note that updates may be available to ensure the proper functioning of your system and installation of these updates is recommended after the reboot ip Reboot om 7 Mellanox Technologies Confidential Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target User Manual Rev 1 0 The expected result now is that the diskless PXE client will boot the newly installed 6 4 from the i
11. SCSI storage and become an operational environment accessible from any remote PC via ssh over LOGbE IP network 11 Mellanox Technologies Confidential Rev 1 0 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target Appendix A Sanity Checks A 1 Sanity Check iSCSI Login From a remote PC called sga070 below with 10GE network connection to the iSCSI target configure an 1SCSI Initiator service and verify the correct target configuration by logging into the target For CHAP configuration refer to SAN Booting with FlexBoot in CHAP Environment Install the initiator gt does db 2 Configure the Initiator root sqa070 vim etc iscsi iscsid conf NOde MIN RIOT eae Optional for CHAP authentication uncomment the following lines discovery sendtargets auth authmethod CHAP discovery sendtargets auth username joe discovery sendtargets auth password secret node sessilon auth authmethod CHAP node session auth username jack node session auth password 12charsecret cu E NI imos comin Cl c hogan 15 aeos sexo Cl seins Loco cec TS MOGs Son LO rs eram c MOC uae MOC Cl Se MSO be Je Bresse 15 MOC MOC Sones I S GUUS node session iscsi InitialR2T No node session iscsi ImmediateData Yes node session iscsi FirstBurstLen
12. damage or loss of data WARNING Warns you that failure to take or avoid a specific action might result in personal injury or a malfunction of the hardware or software Be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents before you work on any equipment n C Mellanox Technologies Confidential Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target User Manual Rev 1 0 1 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target Below are instructions on how to provision a diskless system the client with a fresh RHEL 6 4 installation to a remote storage IE a LUN partition on an iSCSI target and then SAN Booting GSCSI boot the client using Mellanox PXE boot agent FlexBoot The iSCSI configuration in this document is very basic no CHAP authentication no multipath I O and demonstrates basic PXE SAN Boot capability In this document IET is used as the iSCSI Target In the example below e sqaQ30 a Linux host performs the role of the PXE server and an iSCSI target and e Sqa070 a host performs the role of the PXE client and a sanity check environment e sqa030 The OS is configured with IP 12 7 6 30 and the DHCP IP configuration for the diskless client is 12 7 6 70 e Sqa030 has a 21 5GB disk partition on its local HDD called dev cciss c0dOp9 which will be used as the storage volume to host the client s OS It also serves as DHC
13. e as follow OPTIONS coni adle 5 Start the iSCSI target service root8sqa030 etc init d iscsi target start Perform a sanity check by connecting to the iSCSI target from a remote PC on LOGE network link For further information please refer to section Sanity Checks 1 2 Installing RHEL6 4 on a Remote Storage over iSCSI 1 Reboot the diskless client and perform a PXE boot with FlexBoot This is not an iSCSI boot rather a regular PXE initiated network deployment of RHELO 4 In the DHCP server configuration the PXELINUX pxelinux 0 and a RHEL 6 4 distribution media will be provided for network installation For further information please refer to sections A 2DHCP Configuration for PXELINUX with FlexBoot and pxelinux cfg default The clients HDD was removed beforehand therefore the RHEL installer A K A Anaconda will ask to locate a HDD The Anacaonda s built in iSCSI discovery will be used to connect to the iSCSI target LUN partition For further information please refer to https access redhat com site documentation en US Red Hat Enterprise Linux 6 html si ngle Installation_Guide index html ISCSI_ disks 2 Select the Network Interface for the installation process once prompted after the installer is loaded and starts running on the client Select the same interface which was used by FlexBoot during PXE boot stage 3 Select the type of Installation Media access In th
14. e the undionly kpxe module Refer to http www ipxe org howto chainloading root sqa030 src 4 make bin undionly kpxe EMBED sanbootnchap ipxe 5 Copy the bin undionly kpxe to your TFTP root directory E G var lib tftpboot 6 Edit the client s host declaration in the DHCP configuration file for chain loading undionly kpxe The outcome of this procedure is to have FlexBoot download undionly kpxe to the client s RAM and then have undionly kpxe authenticate iSCSI and login with the iSCSI target host See NEXT Sery r l2 7726 30 if option client system architecture 00 00 filename undionly kpxe fixed address 27747605 v0 hardware ethernet 00 02 c9 32 e68 80 Jeu User Class root pach aee O tome Onl eere S e filename Mellanox Technologies Confidential Rev 1 0 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target For CHAP users the CHAP authentication lines mentioned as comments in the 1SCSI target and initiator configuration examples in sections Configuring the iSCSI Target Machine and Sanity Check 1SCSI Login must be uncommented beforehand and during RHEL installation follow these steps iSCS Discovery Details To use iSCSI disks you must provide the address of your iSCSI target and the iSCSI initiator name you ve configured for your host Target IP Address 12 7 6 30 iSCSI Initiator Name What kind of iSCSI
15. eme your own Custom lwyout oe the setected dgevscets using our partibonig toot Encrypt system Reyiew and modify partitioning layout Back Next 14 Click Next and proceed with the Installation 15 Select the Basic Server option This 15 only one of the options that can be chosen not the mandatory one The default installation of Red Hat Enterprise Linux is a basic server install You can optionally select a different set of software now Basic Server Database Server Web Server Identity Management Server Virtualization Host Desktop Software Development Workstation Minimal Please select any additional repositories that you want to use for software installation X Red Hat Enterprise Linux Jo Add additional software repositories 7 Modify repository You can further customize the software selection now or after install via the software management applicatiog Customize later Back up Next 16 Check the Customize Now checkbox 17 Click Next Mellanox Technologies Confidential Rev 1 0 Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target 18 Select Infiniband Support and iSCSI Storage Client k FCoE Storage Client Servers owe Web Services Databases ave System Management Large Systems Performance Virtualization Legacy UNIX compatibility Desktops Mainframe Access Applications Network file system client Development sf Networking Tools Languages 4
16. gth 262144 node session iscsi MaxBurstLength 16776192 nodeoconmllveusesrT Maxhecewvbatasegmernthength discovery sendtargets iscsi MaxRecvDataSegmentLength 32768 node session iscsi FastAbort No 3 Start the iSCSI Initiator service rootCsga070 iscsi Stare 4 Discover the iSCSI target host In the example below the IP address 12 7 6 30 is the iSCSI target root sga070 iscsid start so oder m discovery 0 Starting SC sns Achieving a successful target discovery at this stage 15 mandatory for proceeding with the process of iSCSI boot A failure at this stage 1s probably a result of an erroneous target or network configuration and troubleshooting that 1s out of the scope of this document 5 Log into the target coe e sra 70 o 125395990 abeo login Logging to raeed der aula S Por eos SO 7 Mellanox Technologies Confidential Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target User Manual Rev 1 0 LOGEC abate deen ki LZ ye ceu sono Mee oes Tb A successful LUN login at this stage is mandatory for proceeding with the process of iSCSI boot A failure at this stage is probably a result of an erroneous target or network configuration and troubleshooting that 1s out of the scope of this document 6 Verify the remote partition appears to the initiator as a local HDD
17. is example we use NFS which also requires us to enter the NFS server name and the directory path to the installation media on the NFS 4 Select Specialized Storage Devices What type of devices wh your installation involve Basic Storage Devices installs or upgrades to typical types of storage devices 17 you re not sure which option is right for you this probably it Specialized Storage Devices instalis or upgrades to enterprise devices such as Storage Area Networks SANs This option will allow you to add FCoE SCSI zFCP disks and to filter out devices the installer should ignore 5 Click on the Add Advanced Target button Device Options Add Advanced Target 0 device s 0 MB selected out of 0 device s 0 MB total Tip Selecting a drive on this screen does not necessarily mean it will be wiped by the installation process Also note that post installation you may mount drives you did not select here by modifying your etc fstab file Back Next VEN 117 111 Mellanox Technologies Confidential Using FlexBoot for Booting RHEL 6 4 from an iSCSI Target User Manual Rev 1 0 6 In the Advanced Storage Options window perform the following a Select the Add iSCSI target option b Check the Bind targets to network interfaces checkbox c Click Add drive button Advanced Storage Options How would you like ify your drive configuration Add iSCSI target Bind targets to network interfaces
18. ly a result of a target or network configuration error and recovery troubleshooting that is out of the scope of this document iSCSI Login Resuits Successfully logged in and attached the following nodes 13n 2013 10 galab com 5q3030 prt9 via 10 Make sure a new storage LUN appears in the Other AN Devices tab A successful LUN discovery is mandatory to proceed A failure at this stage 15 probably a result of a target or network configuration error and recovery troubleshooting that is out of the scope of this document Please select the drives you d like to install the operating system on as well as any drives you d like to automatically mount to your system below Basic Devices Firmware RAID Multipath Devices Other SAN Devices Search Filter By Show Only Devices Using Identifier Capacity MB Vendor interconnect T 2 0512 76 30 3260 2013 10 300030 prti un 11 Click Next Device Options Add Advanced Target 1 device s 20483 MB selected out of 1 device s 20483 MB total Tip Selecting 4 drive on this screen does not necessarily mean it will be wiped by the installation process Also note that post installation you may mount drives you did not select here by modifying your etc fstab fite Back Next 12 Select Fresh Installation and proceed with the Installation At least one existing installation has been detected on your system What would you like to do
19. must support passing CHAP credentials Please note that FlexBoot v3 4 149 does not support such operation Hence use FlexBoot to chain load an UNDI software which supports passing CHAP credentials This can be achieved by using the UNDI software module from 1PXE org called undionly kpxe A Linux host 15 required to create undionly kpxe 1 Install the below prerequisite software to support necessary UNDI s compilation eoo assa Tes eM Sere eomm etes make perl 2 Download the UNDI sources from iPXE org For More info visit http www ipxe org download ee oot aegra s git clone 3 Edit a command file named sanbootnchap ipxe the name is given as an example whereas the ipxe file extension is mandatory with the following lines Make sure to enter your own values for username and password per your CHAP configuration For reasons of simplicity and coherence with this document examples we gave our CHAP the username joe and the password secret Note that these CHAP settings are going to be hardcoded into this module and any modification done to them will require you to recompile the module after changing sanbootnchap ipxe root8sqa030 cd ipxe src sexos vim Sanboornenae ipe ipxe dhep dhcp 2 set username joe set password secret Selo I roor ar JI assu 286 echo Booting from sanboot i Mo decer be coor earn 4 Compil
Download Pdf Manuals
Related Search