Home

Boot for NIC, iSCSI, and FCoE Protocols User Manual

image

Contents

1. 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 56782 nlockmgr 100021 3 udp 56782 nlockmgr 100021 4 udp 56782 nlockmgr 100021 1 tcp 44855 nlockmgr 100021 3 tcp 44855 nlockmgr 100021 4 tcp 44855 nlockmgr 100024 1 udp 766 status 100024 1 tcp 769 status 100011 1 udp 815 rquotad 100011 2 udp 815 rquotad 100011 1 tcp 818 rquotad 100011 2 tcp 818 rquotad 100003 2 udp 2049 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 828 mountd Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX DHCP Server Configuration 100005 1 tcp 831 mountd 100005 2 udp 828 mountd 100005 2 tcp 831 mountd 100005 3 udp 828 mountd Appendix C Example for Configuring and Booting UEFI NIC 198 UEFI NIC Server Configuration Script for SLES11 SPx root orleansrhel5564 cat etc dhcpd conf 1 Install the following RPMs in the server if not installed root bglinux156 rpm qa grep dhcp dhepv6 client 1 0 10 18 e15 dhep devel 3 0 5 23 e15 dhep 3 0 5 23 e15 2 Make the following entry in etc dhcpd conf file DHCP Server Configuration file see usr share doc dhcp dhcpd conf sample ddns update style interim ignore client updates subnet 192 168 47 0 netmask 255 255 255 0 range 192 168 47 50 192 168 47 100 default lease time 3600 max lease time 4800 option subnet mask 255 255 25
2. ccc ce ceee eee eee eee eee ed 120 Configuring the LPVID se sscttenccks occ theacs antiwieer kaoi ien ERa AE EENE NEDER aad 121 Saving the Current Configuration ccccecceee cece ee eeee esate EEEE 122 Configuring Multichannel for IBM Adapters ccccccceseceeeeeee esate reeeeeeaneeeaes 122 Multichannel Mod Sii ccedcenciers tease dicridananasiauseddanedaee ar tasanawemieaeindanbaeieeners 123 Multichannel Configuration cccccccccecceceee eee eeaeeeeeeeeeeeeeeeeteetesaeeeneeenegaes 123 Port Management evens tuaricsseiendeeevideectee iuebssesburercaatawcuercebeiercerctaswanelaa 127 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DE EMULEX Table of Contents 7 Feature on Demand sssssssrrsssaasntnttt ant tt ttrt tt rtnn rnn rnnnnnna aR nna annaa nanne 128 Identifying a Port 22224 tests s ores anc eth anciaeta cen anarecenaececnen eae uuu rn rr rrr rrene 129 Erasing Ports and Controller Configuration ccccccceceeeeeeeeeeeeeeeeeeeeenenennanes 129 UEFI NIC DiaQnOSCSycicscceveivicrebicadentamorixtiweroora cen eoa a Ra T vaa 131 EFI _DRIVER_DIAGNOSTICS_PROTOCOL sssssessesssessussnesnenronrrrnrrrrrrrrrorrrrrrne 131 11 Configuring UEFI for iSCSI ssssssnnnnnnnnnssnunnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnn 133 OVGIVIGW siascadsacicancinadeivarssiaatinanstennedieaciadesiaancesdatndeasseenseaciaredaeneeieeie 133 Navigating the Emulex iSCSI Configuration Utility ccccseccssceesscee
3. O M8 Estersiore Path tito fe lor of rf a DHCP server sed options inchide 5 and DNS Figure 9 14 DHCP Server Scope Options 3 In the String Value box add the location of the iSCSI target you want to use for iSCSI boot Enter the string in the following format iscsi lt ipaddress gt lt protocol gt lt iscsi port number gt lt luns gt lt target name gt For example iscsi 010 010 010 001 0 3260 0 ign 1992 08 com netap sn 15729740 4 Click Apply The DHCP server screen is ready to discover boot targets Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 101 gt G EMULEX Enabling DHCP Discovery Through the iSCSISelect Utility Enabling DHCP Discovery Through the iSCSiSelect Utility If your DHCP server supports DHCP discovery and you added the root path to the DHCP server you can enable Discover Boot Target via DHCP using the iSCSISelect utility By enabling Discover Boot Target via DHCP you can use DHCP discovery to provide the boot path from the DHCP server Note If you leave Discover Boot Target via DHCP disabled default you must manually configure iSCSI boot To enable DHCP discovery through iSCS Select 1 After configuring the iSCSI Initiator Name select Controller Properties from the Controller Configuration screen and press lt Enter gt 2 From the Controller Properties screen select Discover Boot T
4. View Configuration Function 0 NIC Permanent MAC 00 00 C9 BC CE 40 Current MAC 00 00 C9 BC CE 40 Logical Link Status Link Up SRIOU Disabled Function 2 iSCSI Permanent MAC 00 00 C9 BC CE 41 Current MAC 00 00 C9 BC CE 41 Logical Link Status Link Up SRIOU Disabled Figure 10 11 View Configuration Screen From the View Configuration screen you can view information for that specific function including the permanent and current MAC addresses the logical link status and the SR IOV status for NIC functions 2 When you are finished viewing the configurations press lt Esc gt to return to the Controller Configuration screen Configuring SR IOV If your system BIOS supports SR IOV you can enable it SR IOV support can only be enabled when multichannel is disabled or it is not supported Note SR IOV is only available for NIC functions and not for storage iSCSI or FCoE functions For more information on SR IOV configuration see the appropriate Emulex driver manual Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 114 gt lt EMULEX Using the Emulex NIC Configuration Utility To configure SR IOV 1 On the Controller Configuration screen select Configure SRIOV and press lt Enter gt The Configure SRIOV screen appears Configure SRIOU Function 0 lt Disable gt Enable Disable SRIOU lt Disable gt Support Figure 10 12 Config
5. Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 138 gt EMULEX Configuring the Network Configuring the Network Automatically Assigning an IP Address through a DHCP Server To enable DHCP for automatic assignment of the IP address through a DHCP server 1 Onthe Controller Configuration menu Figure 11 2 select Network Configuration and press lt Enter gt The Network Configuration screen is displayed Network Configuration 00 00 C9 BC CE 41 MAC Address Port Speed 10 Gbps Link Status Link Up Initiator IP via DHCP lt Disable gt Configure VLAN ID Priority Save DHCP Settings Configure Static IP Address Ping Tl Move Highlight Figure 11 5 Network Configuration Screen 2 Initiator IP via DHCP must be set to lt Enable gt If you change this setting from lt Disable gt to lt Enable gt select Save DHCP Settings and press lt Enter gt Manually Assigning an IP Address To manually assign an IP address 1 Onthe Controller Configuration menu Figure 11 2 select Network Configuration and press lt Enter gt The Network Configuration screen is displayed see Figure 11 5 2 DHCP must be set to lt Disable gt If you change this setting from lt Enable gt to lt Disable gt select Save DHCP Settings and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 139 gt lt EMU
6. Targets gt Figure 12 19 Configure HBA Parameters Maximum LUNs Target Field 4 Type a decimal value between 1 and 4096 and press lt Enter gt The screen is refreshed with the modified value Note The default and typical maximum number of LUNs in a target device is 256 A higher number of maximum LUNs causes the discovery to take more time 5 Select Commit Changes and press lt Enter gt The Emulex Adapter Configuration Main Menu is displayed Changing Boot Target Scan Method This option is only available if none of the eight boot entries is configured to boot from the DID or WWPN The Emulex Adapter Configuration Main Menu is used to configure up to eight boot entries With boot scan enabled the first device issues a Name Server Inquiry The boot scan options are e Boot Path from NVRAM Targets Boot scan discovers only LUNs that are saved to the adapter s NVRAM Select up to eight attached devices to use as potential boot devices Limiting discovery to a set of eight selected targets can greatly reduce the time it takes for the EFIBoot driver to complete discovery e Boot Path from Discovered Targets Boot scan discovers all devices that are attached to the FC port Discovery can take a long time on large SANs if this option is used e Do not create boot path Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 173 gt lt EMULEX Configuring Adapter Parame
7. Troubleshooting for the NIC Protocol Error Codes ARP TFTP Error Codes Possible Reason Comment Solution PXE E11 ARP timeout An ARP request is tried four times and the client did not receive an ARP reply Check the DHCP server settings If you are connected through a switch also check the switch settings PXE E32 TFTP Open timeout A DHCP address and boot file name has been obtained and attempts to download the file name from a remote server Check that the TFTP is configured properly Check that the filename is properly placed in the tftpboot directory e Check that the PXE server is configured for TFTP not MTFTP PXE E35 TFTP read timeout A TFTP server is not able to receive the next packet Check that the hardware and TFTP server are functioning properly PXE E36 Error received from TFTP server A TFTP server sends an error packet Check the TFTP server settings and boot file settings PXE E38 TFTP cannot open connection ATFTP client is not able to opena TFTP connection with the TFTP server Check that the correct boot file is copied into the default TFTP boot path PXE E3B TFTP error File not found A requested boot file is not found on TFTP server Check that the correct boot file is copied into the default TFTP boot path PXE E3C TFTP error Access violation The TFTP server does not have enough access rights to open or read the fi
8. service tftp socket_type dgram protocol udp wait yes user root server usr sbin in tftpd server_args s tftpboot linux install This line specifies path where the pxe boot searches for the images disable no convert this line from yes to no per source 11 cps 100 2 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 189 o Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot 190 gt EMULEX Linux and Citrix PXE Server Remote Installation Procedure flags IPv4 root bglinux156 sbin chkconfig level 345 xinetd on root bglinux156 sbin chkconfig level 345 tftp on root bglinux156 service xinetd restart DHCP Server Configuration 1 Install the following RPMs in the server if not installed root bglinux156 rpm qa grep dhcp dhepv6 client 1 0 10 18 e15 dhecp devel 3 0 5 23 e15 dhcp 3 0 5 23 e15 2 Make the following entry in etc dhcpd conf file DHCP Server Configuration file see usr share doc dhcp dhcpd conf sample ddns update style interim subnet 192 168 1 0 netmask 255 255 255 0 range 192 168 1 50 192 168 1 90 default lease time 3600 max lease time 4800 option subnet mask 255 255 255 0 option domain name pxe_ text option time offset 8 host bglinux45 next server 192 168 1 1 hardware ethernet 00 00 C9 5B 75 A8 fixed address 192 168 1 60 option ho
9. 01 0Ce10100 Bust 02 Devt 00 Funct 02 Mem Base CE2C0000 Firmware Version 2 702 485 1 BIOS Enabledt Port Name 10000000C9587791 Node Name 20000000C95B7791 Ulan ID 0001 DCBX mode CEE mode DID 0203E4 WWPN 22000004 CF9Z26A79 LUN 00 Boot this device via WWPN Boot this device via DID lt ESC gt to Previous Menu lt T l gt to Highlight lt Enter gt to Select Figure 5 9 Boot Devices Menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 62 gt EMULEX Configuring DCBX Mode 6 Use the up and down arrows to select the boot method If you select to boot the device by WWPN the WWPN of the earlier selected entry is saved in the flash memory However during the initial BIOS scan the utility issues a Name Server Inquiry GID_PN Get Port Identifier Then based on this DID it continues with the remainder of the scanning If you select to boot this device by DID the earlier selected entry is saved in the flash memory 01 0Ce10100 Bus 02 Devt 00 Func 02 Mem Base CEZ2C0000 Firmware Version 2 702 485 1 BIOS Enabled Port Name 10000000C95B7791 Node Name Z0000000C9587791 Vlan ID 0001 DCBX mode CEE mode List of Saved Boot Devices Unused 7900000 WWPN 80000000 00000000 00 Primary Used 0203E4 WWPN 00000000 00000000 00 Unused 000000 NWPN 00000000 00000000 00 Unused 000000 YWPN 60000000 00000000 00 Unused
10. FoD Status The FoD Status field indicates whether a license key has been applied properly or not e When the FoD status field is set to Enabled it indicates that the FoD license key has been successfully applied and FoD is enabled When FoD is enabled you will see all of the storage personalities under the Personality menu option including NIC iSCSI and FCOE e Inall other cases the FoD Status field indicates that a failure has occurred or that an FoD license has not been applied Identifying a Port To physically identify a port on the Emulex NIC Selection screen select Port Identification and press lt Enter gt The LEDs on your controller start blinking indicating the selected port Note Not all controllers have LEDs that are visible externally If you are using an add in card in a blade server environment the port identification or beaconing capability does not work Note If port identification is not supported on your system you will receive a message stating that it is not supported Erasing Ports and Controller Configuration Note When selecting this setting all previous configuration settings are returned to their factory default settings except for the current personality selection Emulex recommends performing this action to provide a clean environment for new configuration settings to take effect To erase ports and the controller configuration 1 On the Emulex NIC Selection Screen select Erase Confi
11. Login Redirect Figure 11 14 Advanced iSCSI Target Information Screen Boot for NIC iSCSI and FCoE Protocols User Manual 8192 65536 1 65536 Yes No First Burst Length P009697 01A Rev A 147 11 Configuring UEFI for iSCSI 148 gt lt EMULEX Adding and Configuring Targets Logging In or Logging Out of a Target To log in or out of a target 1 On the Edit Ping Target screen select more to display additional configuration options Edit Ping Target TCP Port Number 3260 Logout BladeEngine Port Number 1 Boot Target lt Yes gt ISID Qualifier FA Header Digest lt No gt Data Digest lt No gt Authentication Method lt None gt Ping Save Login Advanced Properties Login Logout Delete Target LUN Configuration Figure 11 15 Edit Ping Target Screen with Login and Logout Options 2 To explicitly log in or log out of a target select Login or Logout and press lt Enter gt Deleting a Target A target can be deleted only if it is not a boot target If a target is set as a boot target 1 On the Edit Ping Target screen select Boot Target and press lt Enter gt 2 From the drop down menu select No and press lt Enter gt 3 Select Save Login and press lt Enter gt To delete the target 1 On the Edit Ping Target screen select more to display additional configuration options 2 Select Delete Target and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697
12. ccceeeeee tenet nena 73 Reset Adapter Configuration to Defaults SCre n cece eeee cece eee eee ee ene ees 75 10 gt EMULEX Figure 7 1 Figure 7 2 Figure 7 3 Figure 8 1 Figure 8 2 Figure 8 3 Figure 8 4 Figure 8 5 Figure 8 6 Figure 8 7 Figure 8 8 Figure 8 9 Figure 9 1 Figure 9 2 Figure 9 3 Figure 9 4 Figure 9 5 Figure 9 6 Figure 9 7 Figure 9 8 Figure 9 9 Figure 9 10 Figure 9 11 Figure 9 12 Figure 9 13 Figure 9 14 Figure 10 1 Figure 10 2 Figure 10 3 Figure 10 4 Figure 10 5 Figure 10 6 Figure 10 7 Figure 10 8 Figure 10 9 Figure 10 10 Figure 10 11 Figure 10 12 Figure 10 13 Figure 10 14 Figure 10 15 Figure 10 16 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A List of Figures iSCSI Initiator Configuration MENU sieeve ccdvnotivietamedevisieivioiienbesmedatebeda 78 Controller Selection Menu cis scuteetacsicitcavacepchtietasepeitenscmapcleicpsceadeiadeces 78 Controller Configuration M nu cccccc ccc e cece ener esate eeaeeeeaeeeeneeeenan ees 78 iSCSI Initiator Configuration Screen caveicas vies vevawSviede stave vewesgeass ence eiaws ies 80 Controller Selection Menu scce 81 Controller Configuration M nu cccccccce eee e eee ee eeeeeeaeeeeaeeeeneeeenat nes 81 Network Configuration Dialog BOX ic ccicccdprtconcedinre cppendancd ckeentaetaencantna ces 82 DHCP IP Address Dialog BOX iscisccicscocevetetvarsivideens bssatentG ociaseneienaasenns 83 Static IP Address Dialog BOX
13. or prompt information PXE tags were detected but the boot menu and or boot prompt were not found or were invalid Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX Table 13 1 PXE Error Codes Continued 13 Troubleshooting 181 Troubleshooting for the iSCSI Protocol Error Codes PXE E77 Bad or missing discovery server list Possible Reason There are two possible reasons One is that Multicast and Broadcast discovery are both disabled The other is that Multicast and Broadcast are enabled but the server list tag is not found or is invalid Comment Solution PXE E78 Could not locate boot server PXE E79 NBP is too big to fit in free base memory The NBP file size is larger than the free base memory Check the NBP file size Miscellaneous Error Codes PXE EAO Network boot cancelled by keystroke Pressing lt Ctrl gt and lt C gt during DHCP discovery Troubleshooting for the iSCSI Protocol The following section includes troubleshooting information for the iSCSISelect utility Ensure that you also lookup the readme txt file located on CD1 for the most current troubleshooting issues Table 13 2 Troubleshooting the iSCSISelect Utility Issue Answer Solution iSCSI BIOS banner is not displayed e Check the motherboard BIOS configuration and make sure that during system post Boot for NIC iSCSI and FCoE Protoco
14. 008000 WWPN 60000800 000090000 00 Unused 7000000 WWPN 80000000 00000000 HO Unused 000000 BWPN 00000000 00000000 700 Unused 000000_UUPN 00000000 00000000 00 Figure 5 10 Primary Boot Device Set Up Screen SON OUR ON Re 7 Press lt Enter gt to select the change 8 Press lt Esc gt to return to the main configuration menu 9 Reboot the system for the new boot path to take effect Configuring DCBX Mode To configure DCBX mode for FCoE initialization protocol 1 On the main configuration menu Figure 5 2 select Configure DCBX mode and press lt Enter gt The DCBX menu is displayed 01 0Ce10100 Bust 02 Devt 00 Funct 02 Mem Base CE2C0000 Firmware Version 2 702 435 1 BIOS Enabledt Port Name 10000000C95B7595 Node Name 20000000C9587595 Ulan ID 0001 DCBX mode CEE mode DCBX mode is CEE mode CEE mode CIN mode Figure 5 11 DCBX Menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 63 gt C EMULEX Configuring DCBX Mode 2 Use the arrow keys to select CEE if the attached switch is CEE compatible or select CIN if the attached switch is CIN compatible For more information see the FCoE switch documentation for your particular switch 3 Press lt Enter gt to select the mode Configuring CEE Parameters To configure CEE parameters 1 If multiple VLANs or FCoE switches are set up and you want to select
15. Displaying Adapter Information Displaying Adapter Information The Adapter Information screen shows the following information about the selected adapter Adapter status Network boot status Link speed Topology Firmware version refer to this firmware version if reporting a problem to Emulex Technical Support Universal boot version EFI Boot version To display adapter information 1 From the Device Manager screen Figure 12 2 select the adapter whose information you want to view and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Display Adapter Info and press lt Enter gt Information about the selected adapter is displayed 002 OCei0102 FM PCie2 5Gb s x8 Go to Configuration Go eg 00 Bus 04 Dev 00 Func 02 VlanID 0002 Main Menu co Configuration Main Menu A Status Ready Boor from SAN Enabled 2 702 425 0 5 00A10 NA Auto Loop First Figure 12 23 Controller Information Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 13 Troubleshooting 178 Troubleshooting for the NIC Protocol gt EMULEX 13 Troubleshooting Troubleshooting for the NIC Protocol Issues During the PXE Boot Process Situation If any of the following occur during the boot process e The PXE boot ROM sends a DHCP request extended with PXE specific options but the request is not received e The DHCP responses do not contain the DHCP options D
16. OK root bglinux156 etc re d init d nfs restart Shutting down NFS mountd OK Shutting down NFS daemon OK Shutting down NFS quotas OK Shutting down NFS services OK Starting NFS services OK Starting NFS quotas OK Starting NFS daemon OK Starting NFS mountd OK 2 Check if the NFS services are running root bglinux156 rpcinfo p program vers proto port Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A vim etc exports Add work rw sync reflect changes in NFS Server 188 gt G EMULEX Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper L00021 1 udp 56782 nlockmgr 00021 3 udp 56782 nlockmgr 100021 4 udp 56782 nlockmgr 00021 1 tcp 44855 nlockmgr 100021 3 tcp 44855 nlockmgr L00021 4 tcp 44855 nlockmgr 100024 1 udp 766 status 100024 1 tcp 769 status 00011 1 udp 815 rquotad 100011 2 udp 815 rquotad 00011 1 tcp 818 rquotad 100011 2 tcp 818 rquotad 100003 2 udp 2049 nfs 00003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 00003 4 tcp 2049 nfs 100005 1 udp 828 mountd 100005 1 tcp 831 mountd 00005 2 udp 828 mountd 100005 2 tcp 831 mountd 100005 3 udp 828 mountd TFTP Server Setup root bglinux156 vi etc xinetd d tftp
17. To do this select Add Selected iSCSI Targets and press lt Enter gt Figure 9 3 If you enabled CHAP Authentication you are prompted to enter CHAP configuration for each target one at a time For more information see Enabling CHAP Authentication on page 92 Below are the targets discovered via SendTargets Select the targets to add then highlight Add Selected iSCSI Targets and press Enter Add Selected iSCSI Targets 001 iqn 1984 05 emule gt IPv4 172 40 46 150 002 iqn 1984 05 emule gt IPv4 1 E e TRE the ia By EHEHE Pran Figure 9 3 Targets Discovered via SendTargets Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 89 gt EMULEX Adding iSCSI Targets 16 After you have added your targets from the Controller Configuration menu select iSCSI Target Configuration and press lt Enter gt to view the added target information Add New iSCSI Target 001 iqn 1984 gt IPv4 172 40 46 150 3260 1 No Connected Figure 9 4 iSCSI Target Configuration Screen Note If you set the Boot Target option in step 5 before adding the target the Boot Target displays No on this menu To enable Boot Target go to step 17 17 To enable Boot Target or make any other changes to your target or targets select the target and press lt Enter gt The Edit Ping iSCSI Target menu is displayed From this menu you can edit your target
18. and Enabling Boot Code on page 76 for more information Enable the adapter to boot from SAN See Enabling an Adapter to Boot from SAN on page 58 for more information Configure boot devices See Configuring Boot Devices on page 59 for more information If desired configure the boot options on the adapter See Configuring Advanced Adapter Parameters on page 66 for more information Install the operating system on an FC boot disk For additional information see Installing Windows Server 2008 or 2012 on an FC Boot Disk x86 x64 and UEFI on page 40 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 38 gt G EMULEX Windows Server 2008 and Windows Server 2012 Configuring Boot from SAN on Windows UEFI To configure boot from SAN 1 If necessary install or update the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information If necessary enable the boot code on the adapter See Enabling an Adapter to Boot from SAN on page 58 for more information Configure boot devices See Configuring Boot Devices on page 59 for more information If desired configure the boot options on the adapter See Configuring Advanced Adapter Parameters on page 66 for more information Install the operating system on an FC boot disk e For Windows Server 2008 or
19. lt Enter gt A dialog box prompts you to enter the directory path of the server Enter the directory on the server works lesiisp164 Figure C 15 Server Directory Dialog Box 18 Enter the directory path and press lt Enter gt Information similar to the following is displayed starting syslogd Clogging to dev tty4 ok starting klogd ok starting yast Figure C 16 Starting Script SUSE Linux Enterprise Server 11 Installation there are shells running on consoles Z 5 6 9 use extend to load extensions renove with extend r extensions are o bind gdb sax2 network setup run e g dhcped eth0 sshd run resshd start don t forget to set a password with passud mnodinfo beZnet filenane supported license author description version srcversion alias alias alias alias depends supported vernag ic parn parn parn parn 2 4 libsmodules72 6 32 12 6 defaults initrdbe2net ko external GPL ServerEngines Corporation ServerEngines BladeEngine 18Gbps NIC Driver 2 103 358 8 2 103 358 8 73B2DCFE6EFASCh10009192 pci YOBHG19AZdHG0087 10s u sd bewsc i pei vBBHG1IAZdHOBBO7BBsuKsdxbewsc ix pci VBBHB1IAZAHGOHH2Z21isuKsd bc sc i pei VBBOG19SAZdOBOBNZ Llisuxsd bcewscri yes 2 6 32 12 8 7 default SMP nod_unload nodversions rx_frag_size Size of receive fragnent buffer 2048 default 4096 or 819 nun_
20. lt Enter gt The adapter configuration menu is displayed Figure 5 18 2 Select Enable or Disable Auto Boot Sector and press lt Enter gt The Auto Boot Sector configuration screen is displayed 01 0Ce10100 Bus 02 Devitt 00 Funct 02 Mem Base CE2ZCO0000 Firmware Version 2 703 269 2 BIOS Enabledt Port Name 10000000C95B7595 Node Name 20000000C95B7595 Ulan ID 0001 DCBX mode CEE mode Enable Figure 5 26 Enable or Disable Auto Boot Sector Format Screen Select whether to enable or disable the auto boot sector Press lt Enter gt to accept the new value Press lt Esc gt to return to the advanced adapter configuration menu GN OT ee p3 For changes to take effect reboot the system Using Multi Path Boot from SAN Multi boot BIOS is in compliance with BBS The system must have a Multi boot system BIOS in order to take advantage of this option The Multi boot BIOS allows you to select any boot disk in the system BIOS setup menu The boot disk can be an FC drive a SCSI drive an IDE drive a USB device or a floppy drive The Emulex BIOS supplies the first eight drives to the system BIOS menu The Multi boot BIOS can override the FC drive that is selected in the BIOS utility For example the system has eight FC disks only The boot disk has AL_PA 02 However you can select AL_PA 23 in the system BIOS setup menu The boot device is the FC disk with AL_PA 23 instead of AL_PA 02 as is set in the BIOS utility If your s
21. page 96 9 To save your changes select Save Login and press lt Enter gt The iSCSI Target Configuration appears with the revised information Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 92 gt EMULEX Managing an iSCSI Target Setting an ISID Value The ISID qualifier is a unique ISID value to specify if you are connecting dual sessions to the same target portal group This value ensures that you do not log into the same session twice A combination of the initiator name ISID qualifier target name and target portal group defines an iSCSI session For the ISID qualifier you can enter a number up to 65535 To set the ISID Qualifier 1 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted 2 Select Controller Configuration and press lt Enter gt A list of controllers is displayed 3 Select a controller and press lt Enter gt The Controller Configuration menu is displayed 4 From the Controller Configuration menu select iSCSI Target Configuration and press lt Enter gt 5 Select Add New iSCSI Target and press lt Enter gt 6 From the Add Ping iSCSI Target dialog box select ISID Qualifier and type ina numeric value 7 To save your changes select Save Login and press lt Enter gt The iSCSI Target Configuration appears with the revised information For more information on when an ISID val
22. see the appropriate Emulex driver manual 1 On the configuration screen use the lt Tab gt key to select the SR IOV setting and a drop down menu appears 2 From the drop down menu select Enabled or Disabled and press lt Enter gt 3 Select Save and press lt Enter gt Configuring the PXE VLAN ID and Priority To configure a PXE VLAN ID and set the priority level 1 On the configuration screen select Configure PXE VLAN ID Priority and press lt Enter gt The Configure PXE VLAN ID Priority menu is displayed PXE VLAN Support PXE ULAN ID Enabled PXE VLAN Priority Disabled Figure 2 8 Configure PXE VLAN ID Priority Menu 2 Use the lt Tab gt key to select the PXE VLAN Support setting and a drop down menu appears a For PXE VLAN Support from the drop down menu select Enabled and press lt Enter gt b For the PXE VLAN ID enter a number from 0 4094 and press lt Enter gt c For the PXE VLAN Priority level enter a number from 0 7 and press lt Enter gt This unique value assigns a priority to outbound packets containing a specified VLAN ID Valid values range from 0 7 with 0 the highest priority level 3 Select Save and press lt Enter gt After you exit the PXESelect utility the system will reboot for the configuration to take effect Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 30 gt C EMULEX Using the PXESelect Util
23. task is completed the corresponding check box is automatically selected After all tasks are completed a confirmation window is displayed 5 Clear the Run AutoPilot Installer check box and click Finish to close the distribution executable file 6 In Windows Explorer navigate to the folder you specified in step 3 7 Inthe AutoPilot Installer Drivers drivername folder open the folder that corresponds to your computer type such as x86 drivername is the type of driver you downloaded for example Storport Miniport 8 Copy all the files in this folder onto a formatted floppy disk or a USB device 9 Boot the target system with the Windows Server 2008 or 2012 setup media The Install Windows splash screen is displayed 10 Verify and if necessary change the language time and date and keyboard values Click Next Another splash screen is displayed 11 Click Install Now The Where do you want to install Windows screen is displayed 12 Click Load Driver Browse to the floppy disk or USB device specified in step 8 where the driver is located to load the Storport Miniport driver for the appropriate operating system Once selected the correct driver location and driver are displayed under the Select driver to be installed screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX 3 Configuring Boot from SAN for the FCoE Protocol 41 Linux Citrix and VMware 13 Select Next After the driver is loa
24. work rhel6364 images root orleans images mount o loop efiboot img root test1 HHHHHH Extract efiboot img to get bootx64 efi and BOOTX64 conf files root orleans images cd root test1 root orleans test1 cd efi boot root orleans boot cp r tftpboot linux install HHEHHH Copy bootx64 efi and BOOTX64 conf to TFTP root directory HHHH Editing efidefault to the following content root orleans boot cat tftpboot linux install efideault default 0 timeout 10 splashimage nd splash xpm gz title RHEL6364 root nd splashimage splash xpm gz kernel vmlinuz keymap us lang en_US method nfs 192 168 1 1 RHEL6364 ip dhcp noipv6 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX initrd initrd im Configuring DHCP root orleans cat DHCP Server Configuration file etc dhepd conf Appendix C Example for Configuring and Booting UEFI NIC 202 UEFI NIC Server Configuration Script for RHEL 6 x see usr share doc dhcp dhcpd conf sample ddns update style interim ignore client updates allow booting allow bootp subnet 192 168 1 0 netmask 255 255 255 range 192 168 1 50 192 168 1 90 default lease time 3600 max lease time 4800 option subnet mask 255 255 255 0 option router 192 168 1 1 option domain name pxe_ text option name server 192 168 1 20 option time offset 8 host bglinux45 next server 192 168 1 1 back to back to
25. 01A Rev A 11 Configuring UEFI for iSCSI 149 gt lt EMULEX Adding and Configuring Targets Configuring LUNs To configure LUNs 1 On the Edit Ping Target screen select more to display additional configuration options 2 Select LUN Configuration and press lt Enter gt The LUN Configuration screen is displayed LUN Configuration IET 0 Save the Configuration Changes Save Changes Figure 11 16 LUN Configuration Screen 3 Ifthe target is a boot target select any single LUN as a boot LUN using the lt Space gt bar Note If the target is not a boot target you cannot select any LUNs 4 Select Save Changes and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 150 DG EMULEX Adding and Configuring Targets iSNS Configuration Note This functionality is only available on UEFI capable HP adapters The Internet Storage Name Service iSNS Protocol allows automated discovery management and configuration of iSCSI and FC devices using iFCP gateways ona TCP IP network To view the iSNS Configuration screen 1 On the Controller Configuration menu Figure 11 2 select iSCSI Target Configuration and press lt Enter gt iSCSI Target Configuration Add Target gt iSNS Configuration Discovered Targets Figure 11 17 iSCSI Target Configuration Screen 2 On the iSCSI Target Configuration screen select iSNS Configuration and
26. 0x9F 0x43 0xA5 0xA6 OxA7 OxA9 OxAA OxAB OxAC OxAD OxAE OxB1 OxB2 0xB3 0xB4 0xB5 0xB6 0xB9 OxBA OxBC OxC3 OxC5 0xC6 0xC7 0xC9 OxCA OxCB OxCC 0xCD OxCE OxD1 OxD2 0xD3 0xD4 0xD5 0xD6 0xD9 0xDA 0xDC OxE0 OxE1 OxE2 OxE4 OxE8 OxEF Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 67 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 68 gt lt EMULEX Configuring Advanced Adapter Parameters Changing the PLOGI Retry Timer This option is especially useful for Tachyon based RAID arrays Rarely a Tachyon based RAID array resets itself and the port goes offline temporarily When the port returns to operation the PLOGI retry interval scans the loop to discover this device The PLOGI retry interval is the time it takes for one PLOGI to scan the whole loop You can choose e No PLOGI Retry 0 msec default e 50 msec takes 5 to 6 seconds per device if 126 AL_PAs are on the loop e 100 msec takes 12 seconds per device if 126 AL_PAs are on the loop e 200 msec takes 22 seconds per device if 126 AL_PAs are on the loop To set the interval for the PLOGI retry timer 1 On the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed Figure 5 18 2 Select Change PLOGI Retry Timer and press lt Enter gt Information similar to Figure 5 20 is displayed 01 0Ce10100 Bus 02 Deut 00 Func 02 Mem Base CE
27. 11 12 13 14 7 Configuring iSCSI Boot Support with the iSCSISelect Utility 78 Setting Up a Basic iSCSI Boot Configuration Select Save and press lt Enter gt to save your initiator name iSCSI Initiator Name gt iqn 1998 8 com emilex 0 Figure 7 1 iSCSI Initiator Configuration Menu Select Controller Configuration and press lt Enter gt If you are running a single controller the Controller Configuration menu is displayed Figure 7 3 If you are running multiple controllers the Controller Selection menu is displayed Figure 7 2 Controller Port 0 Bus 09 Dev 00 Controller Port 1 Bus 09 Dev 00 Controller Port 0 Bus 01 Dev 00 Control ler Port 1 Bus 01 Dev 00 Figure 7 2 Controller Selection Menu From the Controller Selection menu select your controller and port then press lt Enter gt For more information see Selecting a Controller on page 81 After you have selected your controller the Controller Configuration menu appears ontroller Propert ies etwork Configuration SCSI Target Configuration ort Identification rase Configuration Figure 7 3 Controller Configuration Menu From this menu select Controller Properties and press lt Enter gt Ensure Boot Support is set to Enabled Select Save and press lt Enter gt From the Controller Configuration menu select Network Configuration and press lt Enter gt Configure a network IP address From the Network Configuration menu d
28. 4 Selecta LUN from the list and press lt Enter gt The target list is displayed OCe10102 FM Node Name SEAGATE WWN 21000020 37E16C1E ST318451FC F26D Return to Previous Page LUN 0000 Mode Peripheral dev Figure 12 10 LUN Listing Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Deleting Boot Devices SXC EMULEX 12 Configuring UEFI for FCoE 166 5 Select Commit Changes and press lt Enter gt The Emulex Adapter Configuration Main Menu is displayed UN 0000 Mode Peripheral dev Commit Changes and Go OCe10102 FM Node Name 20000000C9587857 to the Previous Page Commit Changes Discard Changes Figure 12 11 Commit Discard Change Deleting Boot Devices To delete boot devices 1 From the Device Manager screen Figure 12 2 select the adapter from which you want to delete a boot device and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Delete Boot Device and press lt Enter gt A list of eight boot devices is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 167 gt EMULEX Changing Boot Device Order 3 Select the device and press the spacebar to mark it The device is displayed with an X beside it Delete Boot Device Name 20000000C9587857 Note that selecting Commit will reconnect the controller and return you to the Adapter Selection Menu WWN 22000020 S7Ei1
29. 92 Select Yes from the Header Digest drop down menu if you want to enable header digest When set to Yes and the iSCSI initiator is set accordingly the integrity of an iSCSI PDU s header segment is protected by CRC32C checksum The default setting is No Select Yes from the Data Digest drop down menu if you want to enable Data Digest When set to Yes and the iSCSI initiator is set accordingly the integrity of an iSCSI PDU s data segment is protected by CRC32C checksum The default setting is No Select an authentication method optional If you are enabling an authentication method you are prompted to enter CHAP configuration For more information see Enabling CHAP Authentication on page 92 Select Save Login A message reminds you that you have left the iSCSI Target name blank and that the SendTargets mechanism will be used If you want to continue press lt Y gt If the firmware successfully logs into the target the Targets Discovered Via SendTargets screen appears An unsuccessful login produces a failure message After you send your SendTargets request to the target the Targets Discovered Via SendTargets screen appears with a list of targets From this list of targets specify which targets to add To do this select the target or targets you want to add from the menu and press lt F3 gt After you have selected your targets you can add these targets to the list of iSCSI targets available for the initiator to login
30. Fabric Mode 1 On the Emulex NIC Selection screen select Controller Configuration and press lt Enter gt A list of available options is displayed Controller Configuration View Configuration View Current Configurations Configure SRIOU Configure LPUID Save Current Configurations Figure 10 20 IBM Virtual Fabric Mode Controller Configuration Screen 2 From the Controller Configuration screen you can perform the following tasks View the current configuration of each function see Viewing the Configuration on page 118 Configure SR IOV see Viewing the Current SR IOV Configuration on page 119 Note SR IOV cannot be configured with multichannel enabled The Configure SRIOV option only displays the current SR IOV status which is disabled Configure the LPVID per function see Configuring the LPVID on page 121 Save the current configuration see Saving the Current Configuration on page 122 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 125 gt lt EMULEX Using the Emulex NIC Configuration Utility IBM Unified Fabric Protocol Mode Multichannel Configuration To configure the multichannel configuration when the Multichannel Mode is set to IBM Unified Fabric Protocol Mode 1 On the Emulex NIC Selection screen select Controller Configuration and press lt Enter gt A list of available options is displayed Controller Confi
31. Fabric enabled switch provides the ability to configure an LPVID for a virtual channel or I O channel on a OneConnect port If multichannel is supported on your system you can select one of the following modes e IBM Virtual Fabric Mode select this mode when a OneConnect controller is attached to an IBM Virtual Fabric enabled switch e IBM Unified Fabric Protocol Mode select this mode when a OneConnect controller is attached to an IBM UFP enabled switch Note Some IBM switches support both UFP and IBM Virtual Fabric Mode e Switch Independent Mode select this mode if you are using a switch other than an IBM Virtual Fabric or UFP enabled switch Note Multichannel functionality is only supported on OneConnect controllers running in 10 Gb mode The 1 Gb mode does not support multichannel Note An LPVID is optional for IBM Virtual Fabric Mode but it is required for every function when using Switch Independent Mode Multichannel Configuration The available options for configuring multichannel are dependent on the selected multichannel mode Refer to the appropriate section below based on the mode you have selected Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 124 gt lt EMULEX Using the Emulex NIC Configuration Utility IBM Virtual Fabric Mode Multichannel Configuration To configure the multichannel configuration when the Multichannel Mode is set to IBM Virtual
32. HS22 Blade with e Raptor MEZZ 2 Select Boot Manager and press lt Enter gt The Boot Manager screen is displayed Boot Manager Boot system from a Add Boot Option file or device Delete Boot Option Change Boot Order Add WOL Boot Option Delete WOL Boot Option Change WOL Boot Order Boot From File Select Next One Time Boot Reset System Figure C 2 Boot Manager Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 205 gt EMULEX Configuring the IBM HS22 Blade with e Raptor MEZZ 3 Select Boot from File and press lt Enter gt The File Explorer screen is displayed File Explorer EMULEX Pc iRoot 0x0 Pci 0x10 0x7 USB 0x2 0x0 USB 0x0 0x0 USB 0x1 0x0 USB 0x1 0x0 HD 1 HBR 0x067F479 F 0x3F 0x3BAFB1 J Load File PciRoot 0x0 Pci 0x3 0x0 Pci 0x0 0x1 MAC 0000C 95BAS2A 0x0 Load File Pc iRoot 0x0 Pci 0x3 0x0 Pc i 0x0 0x4 ZMAC 0000C 95BA528 0x0 Load File more l Tl Move Highlight lt Enter gt Select Entry Esc Exit I Informational Event s Detected Check POST Event Viewer Figure C 3 File Explorer Screen 4 Select the card from which the UEFI NIC boot is to be performed Press lt Enter gt A message similar to the following is displayed ELILOD boot Loading kernel linux done buffer too small need netbuf_size 23999623 Loading file initrd _ Figure C 4
33. Information sssssssssrsrrerrerssrrrrrrrrerrrrtrrrrrrrrrrrrerrrrrrrrr 177 Network Installation and Diskless Environment WindOW ccceeeeeee neues 191 Configure Network Installations WINdOW ccceceseceeeeeeeeeeeeeeeeeee nena es 192 Network Installation Dialog WINdOW cccceceee cece ee eeeeeteeeeeeeeeneneeeenes 192 Network Installation and Diskless Environment Window with IP Address 193 Edit Dialog BOX sirscidcceantitee ds entered ces citabd tas ianiih eo ia asicaaete ih raiaeeeeaes 193 Enabling Network BOO vcnncsscvcustracSceadnciecsebednsdecsaccatancasaeadiaenadaenatans 195 System Configuration and Boot Management SCreen ccceceeeeeeeeeeeeeees 203 Boot Manager Screen ssiseancshotiedecassaaiereckesbaserenasseutersasurasauntnesasarands 204 File Explorer Screen rasssrrorierii meri reni een paina a a a aaa 205 ELILO Boot Message sssssssrrrrsrrrerrnrnrrnrnrrrruranrnrnrnrruerranarnrrrrerenre 205 Language Selection Menu ccecce 206 Maln Men rirci erona nanna e EAE ENEA EA TEREA aai 206 Expert MeN isrisisrsi roians irnsi tiak reonda E REE TOOR EEE Tanti 207 Kernel Modules Hardware Drivers Menu s sssssssssssrrrrrerrererrsrrrrrreree 207 Driver Update Medium Selection LiSting s sssssssssssrrrrrrrrrrerrrrrrrrrerere 208 Driver Update List Dialog BOX cccceccecccee eens e eee e seats eeaeeeeaneeennenenes 208 Source Medium Selection Menu sc csisiwtaciciiiiisisiesdi icaediacanawiss 208 Network Pro
34. Manually Adding an iSCSI Target Use this method if an iSCSI node has a small number of targets or you want to restrict the targets that an initiator can access To manually configure a target you must provide the iSCSI target name To configure an iSCSI target manually 1 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted 2 Select Controller Configuration and press lt Enter gt A list of controllers is displayed 3 Select a controller and press lt Enter gt The Controller Configuration menu is displayed 4 From the Controller Configuration menu select iSCSI Target Configuration and press lt Enter gt 5 Select Add New iSCSI Target and press lt Enter gt The Add Ping iSCSI Target dialog box is displayed Figure 9 2 Enter the iSCSI target name Enter the iSCSI target IP address Enter the TCP port number the default target port number is 3260 If you want to enable the target as a boot target select Yes w p NO 10 Enter an ISID Qualifier if needed A unique ISID value is needed if you are connecting dual sessions to the same target portal group You can enter a number up to 65535 For more information see Setting an ISID Value on page 63 11 Select Yes from the Header Digest drop down menu if you want to enable Header Digest When set to Yes and the iSCSI initiator is set accordingly the integrity of an iSCSI PDU s header segment is protected by CRC32C checksum The default sett
35. Mode lt Disable gt Controller Configuration Emulex Flash Update Utility Port Identification Erase Configuration Tl Move Highlight Figure 10 2 Emulex NIC Selection Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX 3 10 Configuring UEFI for Ethernet 105 Using the Emulex NIC Configuration Utility The Emulex NIC Selection screen shows the following device information for the selected adapter e Firmware Version the current firmware version installed on the adapter The firmware version is the same as the boot version e Bus Device Function the PCI bus device and function for the adapter This information describes the location of the adapter in the PCI configuration space e Link Speed the current maximum port speed on the adapter This screen also has a link to the Emulex Flash Update Utility which you can use to download firmware and boot code Press lt Esc gt until you exit the utility Downloading Firmware and Boot Code To download firmware and boot code 1 In an open UEFI shell copy the firmware and boot code file into a directory on the EFI partition media Directory of fs0 Firmware 08723711 11 04p 16 777 392 o0c11 4 0 360 1 ufi 1 File s 16 777 392 bytes 0 Dir fs Figure 10 3 EFI Shell with Firmware and Boot Code File Exit the UEFI shell and launch the Emulex NIC configuration utility From the Network device list select the NI
36. Port Converged Network Adapter iSCSI Target Configuration iSNS Configuration iSNS Discovery Mode Disable iSNS Server Discovery via DHCP Disable gt iSNS Server IP 172 40 46 1 iSNS TCP Port 3205 Save Changes Available Servers Figure 11 21 iSNS Server IP Screen 2 Enter the iSNS server s IP address and press lt Enter gt 3 Select iSNS TCP Port and press lt Enter gt The default iSNS Port is 3205 The valid range is 1024 65535 4 Select Save Changes and press lt Enter gt to save the current settings The added server is displayed under the Available Servers list Porti HP CN1100E Dual Port Converged Network Adapter iSCSI Target Configuration iSNS Configuration gt iSNS Discovery Mode Disable iSNS Server Discovery via DHCP Disable iSNS Server IP w iSNS TCP Port 3205 Save Changes Available Servers 172 40 46 1 Figure 11 22 Available Servers Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 154 gt lt EMULEX Adding and Configuring Targets Discovering Targets Using the iSNS Server To configure targets using the iSNS server from the iSNS Configuration screen Figure 11 17 select the iSNS server under the Available Servers list and press lt Enter gt iSNS Server IP 172 40 46 1 iSNS TCP Port 3205 Ping Server Remove Server Figure 11 23 iSNS Server Options Screen The iSNS server IP and TCP port info
37. Process 6 i iisscridscivecriieess eves decrieeerieesieeeetieearee s 178 PXE Error CGGG 2 sivccuoteesuavtdabes sotwe tatni D aE REER i aE EDE ENEE 178 Troubleshooting for the iSCSI Protocol ssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 181 Troubleshooting for the FCOE Protocol ssssssssssnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 184 Appendix A Configuring iSCSI through a DHCP Server using Vendor Specific Option 43 ssssssssnnsnnsnnnssunnnnnnnnnnnnnnnnnunnnnnn 185 OVEFV EW ascsnssmsemiscmascaasonaneteanasmapationenscncasanesanpeateimedanesenamiennsseneanennesenans 185 Format of Vendor Specific Option 43 sssssssssunsssunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 185 Description of ParameterS sssssssssrrerrrtstrrrrrrrrrtt tnter rrrrrrr ttrt rrn rrrrrrerere 185 EMTS erorar na ti orin ar a a AEA E AEE r SENEE EEEE a e aaga 186 Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI BOOt sssssssnnnnnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 187 Linux and Citrix PXE Server Remote Installation Procedure ssssssssnnnnnnnnnnnnnns 187 PAE SEYVET ievucecscnce oxdebsaeivensedete iu rA EEN a TE EEN E AET A IEE A TE A AGE 188 NFS Server Configuration Script ccccccccceeeeeeeeeeeeeeeeeeeceeeeetegueesereeneeenteas 188 TFTP Serer SECU een ecomuGlontens REEE EEE E E IEEE EAR 189 DHCP Server Configuration cccecceccee cee verii aena EE 190 PXE Boot Server Configuration ccccccccceee
38. See Configuring Boot Devices on page 59 for more information If desired configure the boot options on the adapter See Configuring Advanced Adapter Parameters on page 66 for more information Boot the Solaris installation CD and follow the prompts Note If you need help determining the LUNs to select for boot from SAN see Determining LUNs to Select for Boot from SAN on page 42 Determining LUNs to Select for Boot from SAN To determine which LUNs to select 1 2 5 Open a terminal window and leave it open In the terminal window select the LUN you are going to use as the SAN boot disk not the local drive using the luxadm probe command This shows all the available LUNs Record this LUN information which is used throughout this procedure LUN 0 is used in the example luxadm probe Found Fibre Channel device s Node WWN 50060e8003823800 Device Type Disk device Logical Path dev rdsk c5t226000COFF9833AFd6s2 Node WWN 50060 8003823800 Device Type Disk device Logical Path dev rdsk c5t226000COFF9833AFd6s2 Node WWN 50060e8003823800 Device Type Disk device Copy the dev rdsk nnn part of the path statement for a drive In the terminal window use the luxadm display command to show the WWPN or the LUN for which you selected the path in the prior step luxadm display lt dev rdsk nnn gt Record this LUN or WWPN information for use in the procedure Boot for NIC iSCSI and FCoE Protocols User Manual P009
39. Select protocol for installation i Kickstart Software Server IP Address 192 168 1 1 Location work rhel5564 User Password Figure B 3 Network Installation Dialog Window e Enter the operating system identifier and description e Select pxe as the protocol for installation e Enter the IP address of the TFTP server as set up in the DHCP server configuration in the server IP address field e Enter a directory location for the server Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A xs Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot 193 gt lt EMULEX Linux and Citrix PXE Server Remote Installation Procedure The Network Installation and Diskless Environment window shows the IP address of the TFTP server wa Network Installation and Diskless Environment a 5 xj File Configure Help g New Properties Delete Hostname Operating System IP Address E ce 192 168 1 60 rhel5464 192 168 1 60 Figure B 4 Network Installation and Diskless Environment Window with IP Address Configuring the Host To configure the host 1 Double click on the IP address row in the Network Installation and Diskless Environment window Figure B 4 An edit dialog box is displayed BS Edit 192 168 1 60 loj xj Hostname or IP Address Subnet 1 Operating System rhel5464 gt O Enable NISDOMAIN lt SNISDOMAIN O
40. Select the Boot Target option and press lt Enter gt Select Yes from the drop down menu and press lt Enter gt Select Save Login and press lt Enter gt P009697 01A Rev A 11 Configuring UEFI for iSCSI 144 gt lt EMULEX Adding and Configuring Targets Pinging a Target Note If you want to verify that you can connect to a target before you log in you must ping the target before you configure the target on the Edit Ping Target screen To ping a target 1 Onthe iSCSI Target Configuration screen select the target name and press lt Enter gt The Edit Ping Target screen is displayed Edit Ping Target iSCSI Target Name ign 1984 05 emulex tgtO Discover Targets in IP Version IPV4 the given Portal iSCSI Target IP Address 172 40 46 150 TCP Port Number 3260 BladeEngine Port Number 1 Boot Target lt Yes gt ISID Qualifier 2 Header Digest lt No gt Data Digest lt No gt Authentication Method lt None gt Ping Save Login Advanced Properties Login Figure 11 11 Edit Ping Target Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 145 gt lt EMULEX Adding and Configuring Targets 2 From the Add Ping iSCSI Target screen or the Edit Ping Target screen select Ping and press lt Enter gt If the ping is successful a screen similar to the following is displayed Edit Ping Target iSCSI Target Name ign 1984 05 emulex tgt0 Ping IP Version IP
41. Support Setting HIGNMOMECO aris vetagenassventashetvenaes sueceviensscettuaeee haem usercisestencacesesitacs 136 Controller Properties Screen cece cccee cee erect e eee sents en ates nae e ates 137 Network Configuration Screen sssssssssrsrrrererrsresrrrrrrrrertrrsrrrrrrerere 138 Configure Static IP Address Screen oicicscsccccseecstiicesvesvebsceeewesstxeseexcseais 139 Configure VLAN ID Priority Dialog BOX ssssssssrrrueeersrsrrrrrrererrrrrrrrer 140 iSCSI Target Configuration Screen ssssissrsereesssssrrrrrrrrrrerrrrrrrrrerere 141 Add Ping iSCSI Target Screen sssssssssrrrrrerrsrrrrsrrrrrrerrrerrrrrrrererer re 142 Boot Target Option on the Edit Ping Target Screen cc eeeeeee eee 143 Edit Ping Target SCreeMssrctisvsdesce2tavcenaseevivavesrdgeriessissesiresaesehaniemearss 144 Successful Target Ping ssssssssssssssssssrrrrrrrrrrrrrrrrrrrrnnnrrnnannrannnrernre 145 Edit Ping Target Screen with Additional Configuration Options 146 Advanced iSCSI Target Information Screen ssssssssssrrrrreerererrrrrrerrerere 147 Edit Ping Target Screen with Login and Logout Options sscccccccccccccccs 148 LUN Configuration Screen lt ivcxcisit cev cocwks veer iececehcesemnelaheeccanasenseseanetane 149 iSCSI Target Configuration Screen ccccece eect eee e eee eee eee teat teen eaaee 150 ISNS Configuration Screen ccecce 150 ISNS Discovery Mode Screen ee 151 ISNS Server Discovery via DHCP
42. a diagnostic tool but it is also a validation that your network is set up properly prior to target login To verify that a target is accessible and that you are connected to the network 1 From the Network Configuration menu select Ping and press lt Enter gt 2 Inthe Ping Target dialog box enter the IP address of the iSCSI device you want to ping You are notified that the ping is successful If the ping is unsuccessful you receive a failed message For more information see Troubleshooting for the iSCSI Protocol on page 181 Figure 8 9 is an example of a successful ping Figure 8 9 Successful Ping Screen Note The Ping works for any IP address that supports ICMP Echo If you cannot verify the network interface there may be a number of reasons why For more information see Troubleshooting for the iSCSI Protocol on page 181 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 86 gt EMULEX Adding iSCSI Targets 9 Configuring and Managing iSCSI Targets with the iSCSiSelect Utility An iSCSI target is any device that receives iSCSI commands The device can be an end node such as a storage device or it can be an intermediate device such as a bridge between IP and FC devices Each iSCSI target is identified by a unique IQN and each port on the controller or on a bridge is identified by one or more IP addresses As
43. boot from the first target found in the NameServer data To enable or disable the spinup delay 1 Sy gie w On the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed Figure 5 18 Select Enable or Disable Spinup Delay and press lt Enter gt Information similar to Figure 5 21 is displayed 01 0Ce10100 Bust 02 Devitt 00 Func 02 Mem Base CE2C0000 Firmware Version 2 703 269 2 BIOS Enabled Port Name 10000000C9587595 Node Name 20000000C95B7595 Ulan ID 0001 DCBX mode CEE mode Enable Figure 5 21 Enable or Disable Spinup Delay Screen Select whether to enable or disable spinup delay Press lt Enter gt to accept the new value Press lt Esc gt to return to the advanced adapter configuration menu For changes to take effect reboot the system Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 70 DG EMULEX Configuring Advanced Adapter Parameters Setting Auto Scan This option allows you to set auto scan and enable the first device in the boot entry list to issue a Name Server Inquiry Auto scan is available only if none of the eight boot entries is configured to boot from DID or WWPN The factory default is disabled If there is more than one adapter with the same PCI Bus number in the system and each has a boot drive attac
44. d 100 d 10 set boot id Example 2 wwpn 50000034987AFE lun af hexadecimal and target id 10 decimal wwpn 50000034987AFE af d 10 set boot id Example 3 did 6312200 lun 25 hexadecimal and target id f hexadecimal did 6312200 25 f set boot id Boot to the original local disk to set up the FC disk that you just defined Type boot local disk where local_disk is the complete path or the alias of the original boot disk Run the format utility format Select the target disk to become the new boot disk for example c1t1d0 Select the partition option and partition the disk as desired Select the label option and write a volume label to the target disk For help with the format utility see the man page man format Install the boot on partition 0 of the target disk Type this command as one line installboot usr platform uname i lib fs ufs bootblk dev rdsk clt1d0so Create a filesystem for each partition that contains a mounted filesystem newfs v dev rdsk clt1d0s0 becomes root newfs v dev rdsk cltid0s6 becomes usr newfs v dev rdsk clt1id0s7 becomes export home Create temporary mount points for the new partitions mkdir root2 mkdir usr2 mkdir export2 Mount copy then unmount the usr2 file system mount dev dsk cltid0s6 usr2 cOt0d0s6 ufsdump Of dev rdsk cotod0s6 cd usr2 ufsrestore rE umount usr2 Copy the export home file system Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01
45. d tmp c Modify the elxfc conf file to use persistent binding For more information see the Emulex Driver for Solaris User Manual 5 Copy the DVD image in the drive to the install server s hard disk setup_install_server install dir path install_dir_path specifies the directory where the DVD image is to be copied Note The setup_install_server command indicates whether you have enough disk space available for the Solaris Software disc images To determine available disk space use the df k1 command 6 Decide whether you need to make the installation server available for mounting If the installation server is on the same subnet as the system to be installed or you are using DHCP you do not need to create a boot server Proceed to step 7 If the install server is not on the same subnet as the system to be installed and you are not using DHCP complete the following steps a Verify that the path to the install server s image is shared appropriately share grep install_dir_path install_dir_path specifies the path to the installation image where the DVD image was copied e If the path to the install server s directory is displayed and anon 0 is displayed in the options proceed to step 7 e If the path to the install server s directory is not displayed or you do not have anon 0 in the options continue and make the install server available to the boot server Using the share command add this entry to the etc dfs dfs
46. for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 209 gt EMULEX Configuring the IBM HS22 Blade with e Raptor MEZZ 14 The Network Protocol Selection menu is displayed Select NFS and click OK Choose the network protocol FTP HTTP NFS SMB CIFS Windows Share TFTP mmj e Figure C 12 Network Protocol Selection Menu 15 The Network Device Selection listing is displayed Select the device and click OK Choose the network device ethi ServerEngines Emulex OneConnect 18Gb NIC eth2 ServerEngines Emulex OneConnect 18Gb NIC eth3 ServerEngines Emulex OneConnect 10Gb NIC eth4 ServerEngines Emulex OneConnect 10Gb NIC ethS ServerEngines Emulex OneConnect 18Gb NIC eth6 ServerEngines Emulex OneConnect 18Gb NIC eth Broadcom NetXtreme II BCNS 769S Gigabit Eth eth Broadcom NetXtreme II BCMS709S Gigabit Eth usb IBM RNDIS CDC ETHER Figure C 13 Network Device Selection Listing 16 The DHCP request is sent A dialog box prompts you to enter the IP address of the NFS server Enter the IP address of the NFS server 192 168 147 1 Figure C 14 NFS Server IP Address Dialog Box Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX Appendix C Example for Configuring and Booting UEFI NIC 210 Configuring the IBM HS22 Blade with e Raptor MEZZ 17 Enter the IP address and press
47. from a target e Its IP address e Its unique node name e The boot iSCSI target s IP address e The boot target s name If not available this may be discovered using the iSCSI discovery protocol e The target s non default TCP port number if applicable e Header and data digest settings to be used with the target e Authentication parameters if applicable If your boot BIOS allows it you can configure all of the above parameters from a centrally configured DHCP server using vendor specific option 43 This appendix documents this method of configuration For this method the initiator must be configured using non DHCP means with the appropriate DHCP vendor ID The method and format for specifying the vendor ID is outside the scope of this document The initiator offers this Vendor ID to the DHCP server to retrieve data in the format described in the following sections Two other methods for configuration are not documented in this appendix e Manual configuration using iSCSISelect or SMCLP MILI e Pre boot configuration using CLP BIOS 3 0 Format of Vendor Specific Option 43 The format for vendor specific option 43 is as follows iscsi lt ipaddress gt lt protocol gt lt iscsi port number gt lt lun gt lt target name gt Fields enclosed in angular brackets including the angular brackets should be replaced with their corresponding values All fields are case insensitive See the example at the end of this document De
48. gt G EMULEX Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Emulex Connects Servers Storage and People gt EMULEX EMULEX CONFIDENTIAL Copyright 2003 2013 Emulex All rights reserved worldwide No part of this document may be reproduced by any means or translated to any electronic medium without the prior written consent of Emulex Information furnished by Emulex is believed to be accurate and reliable However no responsibility is assumed by Emulex for its use or for any infringements of patents or other rights of third parties which may result from its use No license is granted by implication or otherwise under any patent copyright or related rights of Emulex Emulex the Emulex logo AutoPilot Installer AutoPilot Manager BlockGuard Connectivity Continuum Convergenomics Emulex Connect Emulex Secure EZPilot FibreSpy HBAnyware InSpeed LightPulse MultiPulse OneCommand OneConnect One Network One Company SBOD SLI and VEngine are trademarks of Emulex All other brand or product names referenced herein are trademarks or registered trademarks of their respective companies or organizations Emulex provides this manual as is without any warranty of any kind either expressed or implied including but not limited to the implied warranties of merchantability or fitness for a particular purpose Emulex may make improvements and changes to the product described in this manual at any time and withou
49. iSCSI Target 87 Manually Adding an iSCSI Target sxc ceices esc ccave takes swietsbudicnsell eavaceweiamectawnpraines 89 Managing an iSCSI Target cscccciiessataseasastsnesetcasestaniecsstetwssscssnsieniecoceeeetvenate 90 Viewing Target Information cccccccce cece eee eee e eee eee e ee eae teense eeaateeaae enna 90 Editing a Target ConmquratiGn cicccsis cide canted a honsanenesbtedauteteteedanvedsheedeeeatsnes 91 Setting an SID Value rei pouecewsads E OKA ARAA cones bys EREE ETENI AEAEE 92 Enabling CHAP AUthentiCatiOnienaiinciageer ities daanudabied an ea dda AAE i 92 Pinging a Target ssc cncass ccs aecan seaein han a EE E EE EEES 95 Viewing Advanced Target Properties viccccienluitcetvue ce tas aceencveseddheedebeederwedsedads 96 Configuring LUN Settings ssssssssrsrrrrrerrrrrrrrrrrrrrrrrrtrrnrrrrrrrrtrrrrerrrrrrert 96 Removing and Logging Out and In of a Configured Target cccccceeeeeneeeenee eens 97 Booting the System 25 sisiwsserceesrwatncn titawieervedienct eritanieiorenkesieredeieieventes 97 Erasing the COnMQUPAUON tevsinvescaxi di aev eerie otertcawreeeebiia ve rekebesawedenesoue teres 98 Discovering Targets through DHCP for iSCSI ssssssnssnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 99 Enabling DHCP Discovery Through the iSCSISelect Utility cccccceeeceeeeneeeeseeees 101 10 Configuring UEFI for Ethernet ssssssssnnnnnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn LOZ OVEI VIEW sinuiessciadcncsnksdancessnesiastnannssens
50. is displayed Target CHAP Name Target Secret Initiator CHAP Name Initiator Secret Figure 9 8 Mutual CHAP Configuration Dialog Box 7 Enter the target CHAP name target secret initiator CHAP name and initiator secret Select OK and press lt Enter gt The target initiator CHAP names can be any name or sequence of numbers over 12 and less than 16 characters However the name and secret on the target side must match the name and target on the initiator side The target initiator secret can be in string for example abcdefg23456 or hexadecimal for example 0x01234567890123456789A BCD format e Ifusing a string format the secret can be any name or sequence of numbers over 12 and less than 16 bytes long where each character equals one byte e If using a hexadecimal format the secret must be at least 12 and less than 16 bytes long where two characters equal one byte Hexadecimal formatting restrictions o The Ox representation requires an even number of hexadecimal values excluding the Ox 0 9 A F For example the secret 0x1234567890123456789ABCD is not allowed because the character length is odd with 23 hexadecimal values excluding the 0x The secret 0x01234567890123456789ABCD is allowed with 24 hexadecimal values excluding the Ox o The hexadecimal representation of CHAP secrets must only contain hexadecimal values The 0x representation must only have the following characters 0 1 2 3 4 5 6 7 8 9 a b
51. is CEE compatible or select CIN if the attached switch is CIN compatible For more information see the switch documentation Press lt Enter gt The selection is changed to NVRAM and the current setting is displayed 001 OCei0102 EM PCie2 5Gb s x8 This setting will eg 00 Bus 04 Dev 00 Func 02 VlanID 0002 Configure DCBX OCei0102 FM Node Name 20000000C9587857 CEE CIN Mode NOTE Defauit is CIN Back to Display Adapters and RECONNECT DEVICE Mode Your selection Set Boot from SAN will be AUTO saved to onfigure DCBX Mode NVRAM System Reset Required Oonfigure CIN FCF Parameters eosece can for Fibre Devices Add Boot Device Delete Boot Device ange Boot Device Order onfigure HBA and Boot Parameters Set Emulex Adapter to Default Settings Figure 12 5 Emulex Adapter Configuration Main Menu DCBX Menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 161 gt EMULEX Configuring CEE FCF Parameters Configuring CEE FCF Parameters To configure CEE FCF parameters 1 From the Device Manager screen Figure 12 2 select the adapter to configure and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Configure CEE FCF Parameters and press lt Enter gt A listing of current CEE FCF record information is displayed wish to modify in Flash UNSD Name VLANID 000 S
52. loaded in an EFI Shell type drivers and press lt Enter gt to see if the driver is loaded Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 103 SG EMULEX Using the Emulex NIC Configuration Utility Using the Emulex NIC Configuration Utility Navigating the Utility Use the following methods to navigate the Emulex NIC configuration utility Press the up down arrows on your keyboard to move through menu options or fields When multiple adapters are listed use the up down arrows to scroll to the additional adapters Press the lt gt lt gt or lt Enter gt keys to change numeric values Press lt Enter gt to select a menu option to select a row in a configuration screen or to change a configuration default Use the navigation entries on the page to move about the utility Press lt Esc gt to exit the current screen and show the previous screen Downloading the Latest Firmware and Boot Code A single firmware image contains the latest version of the firmware and boot code Depending on the OEM UFFI configuration the Emulex NIC configuration utility may appear under different setup menus in OEM system firmware or BIOS such as System Settings gt Network Device List Firmware Components The ELX UNDI driver implements the PXE UNDI API services used by the SNP driver during PXE boot and while executing an NBP The boot hardware abstraction layer HAL prov
53. personality implies that all the enabled functions provide NIC TOE functionality iSCSI and FCoE personalities are enabled on one function per OneConnect port and include NIC functionality on the other enabled functions Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 111 gt lt EMULEX Using the Emulex NIC Configuration Utility To view the personalities supported on the adapter select Personality on the Emulex NIC Selection Screen and then press lt Enter gt The Personality dialog box appears with a list of available personalities Emulex NIC Selection Emulex OneConnect 0Ce11102 IM 2 port PCIe 10GbE Change Personality CNA This Setting gets affected for the other Firmware Version 4 6 152 0 Port SYSTEM RESET Bus Device Function 15 0 0 REQUIRED Link Speed 10 Gbps Advanced Mode lt Enab iSCSI Personality lt iSCS Multichannel Mode lt Disa Controller Configuration Emulex Flash Update Utility Port Identification Erase Configuration Figure 10 9 Personality Dialog Box To change the personality of the adapter 1 Onthe Emulex NIC Selection Screen select Personality and press lt Enter gt The Personality dialog box appears 2 Select the desired personality from the drop down menu and press lt Enter gt Note Additional configuration changes may be made after changing the Personality setting however a reboot is required before the new P
54. pessemsdes bee ecbarasemrantonscres 100 Emulex NIC Configuration Utility Network Screen ccceeeeeee eee eeeeeeeeenes 104 Emulex NIC Selection Screen 104 EFI Shell with Firmware and Boot Code File cceceeeene snes tees rears 105 Emulex Flash Update Utility cccccccecceee cece reese rset eeeeteneetenenneneaes 106 Emulex Flash Update Utility with Directory Name Dialog Box 106 Emulex Flash Update Utility with Flash File Name Dialog Box 000 107 Emulex Flash Update Utility Flash Updating ccccccceeeceee esate seen eeenes 108 Advanced Mode Dialog BOX co cc tacauedeudvacisemiidirrecadaiacaverendederesadedteas 110 Personality Dialog BOK scc2xcavccivetniadcaci stants cccdatenitcsad actdcadamaadciaenaa 111 Controller Configuration Screen cris ctvissureccave awd etveaeessstnestebeen sean oe 112 View Configuration SCreen ssssssssssssrrrrrrrrrrtrtrrrrrrrrrerrrtrrrrrrrrr 113 Configure SRIOV Screen ssssssssrsrrrrrerssrsrrrrrrrrrrrrrtrrrrrrrrrrrtrrsrrrrr 114 Multichannel Modes 2 420 sen erotietaceaaivareeecentetesmaraiuraueeeraeraeeanites 116 Controller Configuration Screen ccccccccee cee e este erate eset esate enee een ae es 117 Multichannel Configuration for Function 0 SCre n cccceeeeeeeeeeeeeeeeeenes 118 Configure SRIOV Screen sus tense Oe oecceru tpaenadandde nds deste me saserhcpadecmanet ees 119 11 gt G EMULEX Figure 10 17 Figure 10 18 Figur
55. select Configure VLAN ID Priority and press lt Enter gt The Configure VLAN ID Priority dialog box appears Configure VLAN ID Priority ULAN Support lt Enable gt Save the Configuratio ULAN ID 45 Changes ULAN Priority 2 Save Changes Figure 11 7 Configure VLAN ID Priority Dialog Box 2 To enable VLAN support a Select VLAN Support and press lt Enter gt b From the VLAN Support drop down menu select Enable and press lt Enter gt 3 To assign a VLAN ID number a Select VLAN ID and press lt Enter gt This is a unique value you assign to each VLAN ona single device There are a maximum of 4093 possible values ranging from 2 4094 b Enter a VLAN ID value and press lt Enter gt 4 Toseta VLAN priority if necessary a Select VLAN PRIORITY and press lt Enter gt This unique value assigns a priority to outbound packets containing a specified VLAN ID Valid values range from 0 7 with 0 the highest priority level b Enter a VLAN priority value and press lt Enter gt 5 Select Save Changes and press lt Enter gt 6 Press lt Esc gt to return to the Network Configuration menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt lt EMULEX 11 Configuring UEFI for iSCSI 141 Updating Firmware Updating Firmware To update firmware you must use the NIC firmware update utility which revises the iSCSI function with a single firmware download image For more information on downloa
56. standard for linking data storage devices over a network and transferring data by carrying SCSI commands over IP networks An iSCSI network consists of one or more iSCSI storage units targets connected through a copper or optical networking cable to 10Gb Ethernet network switches and or IP routers One or more servers are connected to this network which are responsible for transferring data to or from the storage units When an operating system receives a request it generates the SCSI command and then sends an IP packet over an Ethernet connection At the receiving end the SCSI commands are separated from the request and the SCSI commands and data are sent to the SCSI controller and then to the SCSI storage device iSCSI also returns a response to the request using the same protocol Constructing a Basic iSCSI SAN There are three main components that make up an iSCSI SAN e iSCSI Initiator s The initiator allows a given machine access to the storage available in the iSCSI SAN It requests all SCSI operations like read or write An initiator is usually located on the host server side either as hardware iSCSI adapter or software iSCSI software initiator To transport block SCSI commands over the IP network an iSCSI driver must be installed on the iSCSI host An iSCSI driver is included with the OneConnect adapter For more information on iSCSI initiators see chapter 8 Configuring and Managing the iSCSI Initiator with the iSCSI
57. svc iisecrsscsstodierieeniv eraser rievseeieeierneieress 83 Configure VLAN ID Priority Dialog BOX cccceeceeeeeee eect eeeneeeeneeeenaeeeas 84 Port Identification SCIEN i cccccuaresiccctecscssaserasadvadadstandiiandsaacestaadchends 85 SUCCESS Ul PING SCVEEN wciccixciicewniesedesiuseenbotase tener AKADTAK EENE EN 85 Controller Configuration M nu ccccccccee cece ee eee e esas eeeaeeeeaeeeeneeeenaeeeas 87 Add Ping iSCSI Target dialog DOX lcc 87 Targets Discovered via SendTargets ScCreen 2 ccceceeeee eee e eee eeeeeeeeeaes 88 iSCSI Target Configuration Screen ccc sieccicic cis noe biy ctweck ia aienesttat cetsecdsawens 89 iSCSI Target Configuration Information ssssssesssssrerrrerrresrrrrrrerererre 90 Edit Ping iSCSI Target Dialog BOX ssssssssrsrrruserssrrrrrrrrerrrrrrrsrrrerrrrere 91 One way Chap Configuration Dialog BOX sssccccccccccccccccrccccccccccn 93 Mutual CHAP Configuration Dialog BOX ssssssssessssssrrrrrererrrrrrrrrrrrrrrre 94 Ping Target Dialog BOX siicisssctsrthsiscedeuteetvewesstedsacvssasasssawieadaieaseaseseen 95 Successful Ping Screen sssssssssesrsrerrrrrrrrrrrntrrrnanarranarraanarunnarrrrrrrn 95 Advanced Target Properties Screen cccceceeeee eee etna eens eee eeeeeneeaaes 96 LUN Configuration Menu vcccstisestecentaciseecesecieateentoetenteseteidensiannerenees 96 DHCP Ser Ver SC EEN isione erie a EE o a e beds 99 DHCP Server Scope OC ONS xc wcsze san vances tee wnandvs
58. the integrity of an P009697 01A Rev A DG EMULEX 11 Configuring UEFI for iSCSI Adding and Configuring Targets 143 iSCSI PDU s header segment is protected by the CRC32C checksum The default setting is No 9 Select Yes from the Data Digest drop down menu if you want to enable Data Digest When set to Yes and the iSCSI initiator is set accordingly the integrity of an iSCSI PDU s data segment is protected by the CRC32C checksum The default setting is No 10 Select an authentication method optional If you are enabling an Authentication method you are prompted to enter CHAP configuration 11 Select Save Login and press lt Enter gt to discover targets Setting a Boot Target The discovered target must be set as a boot target to enable iSCSI boot To set a boot target 1 Onthe iSCSI Target Configuration screen select the target name and press lt Enter gt The Edit Ping Target screen is displayed iSCSI Target Name IP Version iSCSI Target IP Address TCP Port Number BladeEngine Port Number Boot Target ISID Qualifier Header Digest Data Digest Authentication Method Ping Save Login Advanced Properties Login Edit Ping Target iqn 1984 05 emulex tgt0 IPV4 172 40 46 150 3260 1 lt No gt 2 lt No gt lt No gt lt None gt Boot From This Target Boot for NIC iSCSI and FCoE Protocols User Manual Figure 11 10 Boot Target Option on the Edit Ping Target Screen
59. to scroll to the additional adapters e Press lt Tab gt to move to the next field and lt Shift gt lt Tab gt to move to the previous field e Press lt Enter gt to accept a selection select a menu option to select a row ina configuration screen or to change a configuration default e Press lt Esc gt to return to the previous menu or page cancel a selection or dialog box or exit the utility Setting Up a Basic iSCSI Boot Configuration By setting up a basic iSCSI boot configuration you can configure your initiator contact network devices and set up an iSCSI boot target With iSCSI boot capability the iSCSI Select utility can quickly and easily provide the target LUN disk to the operating system through the BIOS After setting up a basic iSCSI boot configuration you can continue to use the iSCSISelect utility to manage your OneConnect Server iSCSI SAN environment When setting up a basic iSCSI boot configuration you must do the following e Configure the iSCSI initiator name and enable boot support e Configure the network properties e Add an iSCSI target and enable it as a boot target e Set your boot LUN e Reboot your system To set up a basic iSCSI Boot configuration 1 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted 2 From the iSCSI Initiator Configuration menu set the initiator name Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX 3 10
60. utility is configured properly a message during boot time indicates that the iSCSI disk was successfully connected Install a Linux operating system over the iSCSI LUN For more information refer to the Emulex Driver for Linux User Manual ESXi Server To install and configure boot from SAN on ESXi Server 1 2 Log into the iSCSISelect utility pressing lt Ctrl S gt when prompted Use the iSCSISelect utility to log into a target from one adapter and configure it for boot For more information see chapter 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility on page 80 and chapter 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility on page 86 If the iSCSISelect utility is configured properly a message during boot time indicates that the iSCSI disk was successfully connected Install an ESXi Server operating system over the iSCSI LUN For more information refer to the Emulex Driver for VMware User Manual Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 4 Configuring x86 x64 Platforms for the iSCSI Protocol 53 gt C EMULEX Configuring for the iSCSI Protocol Booting from SAN for iSCSI MPIO MPIO support allows the initiator to log in dual sessions to the same target In this way I O can be sent over either TCP IP connection to the target If one session fails another session can continue processing I O without interruption to the application In
61. value may be different To change the delay device discovery value 1 From the Device Manager screen Figure 12 2 select the adapter whose device discovery delay settings you want to change and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Configure HBA Parameters and press lt Enter gt The Configure HBA Parameters is displayed 3 From the Configure HBA Parameters menu select Delay Device Discovery and press lt Enter gt Delay Device Discovery Discard Changes commit Changes Opoicgy Selection lt AUIO Loop First defauit gt PLOGI Retry Timer lt Disable Defauit gt Force Link Speed lt Auto negotiate Default gt onfigure Boot Parameters aximum Luns Target 256 Boot Target Scan Method lt Boot Path Discovered Targets gt Delay Device Discovery 0 Figure 12 21 Configure HBA Parameters Delay Device Discovery Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX 12 Configuring UEFI for FCoE 175 Resetting Emulex Adapters to Default Values 4 Use the keys to change the delay device discovery value in increments of 10 seconds and press lt Enter gt The screen is refreshed with the modified value 5 Select Commit Changes and press lt Enter gt The Emulex Adapter Configuration Main Menu is displayed Resetting Emulex Adapters to Default Values The EFI utility enables you to clear the NVRAM target
62. 0 00000000 gt lt 05 WWN 00000000 00000000 gt Figure 12 13 Change Boot Device Order Screen 4 Select a device from the list of eight boot devices and press lt Enter gt Boot Device Order Change Boot Device Order lt 05 WWN 00000000 Figure 12 14 Boot Device Order Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A sc 12 Configuring UEFI for FCoE 169 gt EMULEX Changing Boot Device Order 5 Use the lt gt or lt gt keys to change the order of the selected device on the dialog box and press lt Enter gt A screen shows the new boot device order Boot Device Order ot E H eooo D oo o Figure 12 15 Change Boot Device Order Screen 6 Verify that the boot device list order is correct Press lt Enter gt Boot Device Order 3 5 221 Change Boot Device Order WWN 00000000 Figure 12 16 Change Boot Device Order Screen with Revised Boot Order Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 170 gt lt EMULEX Configuring Adapter Parameters 7 Select Commit Changes and press lt Enter gt The revised order is saved to the NVRAM The Emulex Adapter Configuration Main Menu is displayed Figure 12 17 Change Boot Device Order 8 From the Emulex Adapter Configuration Main Menu select Back to Display Adapters and RECONNECT DEVICES to complete configuration or select another configura
63. 0 Successful Ping Screen If the ping is unsuccessful you receive a failed message There are several reasons for an unsuccessful ping For more information see Troubleshooting for the iSCSI Protocol on page 181 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A xs 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility Q6 gt C EMULEX Managing an iSCSI Target Viewing Advanced Target Properties After you have logged into a target you can view more information about that target To view more information about the target from the Edit Ping iSCSI Target dialog box select the Advanced option and press lt Enter gt Advanced information is displayed Target 001 iSCSI Initiator Name FirstBurstLength Kbytes MaxBurstLength Kbytes InitialR2T ImmediateData MaxRecvDataSegmentLength Kbytes Login Redirect Figure 9 11 Advanced Target Properties Screen Configuring LUN Settings A LUN represents an individually addressable logical device that is part of a target An initiator negotiates with a target to establish connectivity to a LUN To configure a LUN 1 From the iSCSI Target Configuration screen press lt F7 gt to display the LUNs associated with the iSCSI node LUN Configuration Vendor Information Block Size Bytes Bootable Size MB 002 IET 512 No 003 IET 512 No 004 LET Tie No 005 IET nae No 006 TET 512 No 007 IET Tia No 008 IET nae No 009 IE
64. 0000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00004000 00020000 00020000 00040000 pciex19a2 700 pciexclass 020000 pciexclass 0200 000005ee 00000030 ethernet 10000 null1 full Copyright c 2009 2011 Emulex All rights oce network Emulex 00016e00 00000001 00000010 00020000 0000e602 000010df 00000002 00000700 000019a2 3 Add the MAC address from step 2 as an installation client to the Install Boot server Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 49 C EMULEX E Power on the client machine and wait for the ok prompt 5 Set the net device alias for the device selected in step 2 e If the net device alias is already set to the network device to be used for the net boot skip this step e If the net device alias is not set set the net device alias to the network device that to be used for the net boot Type 0 ok devalias net lt device path gt 6 Boot from the network e If using the DHCP boot strategy type 0 ok boot net dhep e If using the RARP boot strategy type 0 ok boot net rarp Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 4 Configuring x86 x64 Platforms for the iSCSI Protocol 50 gt lt EMULEX iSCSI Overview 4 Configuring x86 x64 Platforms for the iSCSI Protocol iSCSI Overview iSCSI is an IP based
65. 001 EE E E E EEEE E E 147 00000019 No ee ee eee O a pd j pd d N Figure E 1 Driver Listing 2 Write down the Emulex NIC FCoE or iSCSI driver handles For the above case the PCI Bus Driver SCSI Bus Driver Scsi Disk Driver Vitesse VSC452 SIO Driver Simple Network Protocol Driver UEFI PXE Base Code Driver PXE DHCPv4 Driver gt MNP Network Service Driver IP4 Network Service Driver DHCP Protocol Driver IP4 CONFIG Network Service Driver Tcp Network Service Driver 0 UDP Network Service Driver ARP Network Service Driver MTFTP4 Network Service UEFI PXE Configuration Driver Broadcom Gigabit Ethernet Driver Broadcom Gigabit Ethernet Driver 2 Emulex 106 NIC Emulex iSCSI Boot Driver LSI Logic Fusion MPT SAS Driver G200eV Matrox Graphics UEFI Driver 3 Partition Driver MBR GPT E Torito FuFile 43B93232 AF FuF i le 93B80004 9F FuF i le 016 7CCC4 D0 FuF i le OAB6E322 37 FuF i le BBA81468 FF FuF i le A2F436EA AL FuF i le SB1IDEABS C FuF i le A46C3330 BE FuF i le O25BBFC E6 FuF i le SFB1A1F3 3B FuF i le 94734718 0B FuF i le 26841 BDE 92 FuF i le 6D6963AB 90 FuF i le 6D6963AB 90 FuF i le 629D3F93 E8 FuF i le DC3641B8 2F FuF i le OCOB6DB5 AA Offset 12000 231FF Offset 12000 231FF Offset 8000 169FF Offset 10000 1ASFF Offset B200 247FF Offset 6000 D1FF Emulex NIC driver handle is 122 and the Emulex iSCSI driver handle is 126 3 To unload t
66. 2012 see Installing Windows Server 2008 or 2012 on an FC Boot Disk x86 x64 and UEFI on page 40 e For anew installation of Windows 2008 UEFI Aware operating system on a UEFI based x64 Server see Installing a New Windows Server 2008 or 2012 UEFI Aware Operating System on a UEFI based x64 Server on page 38 Installing a New Windows Server 2008 or 2012 UEFI Aware Operating System on a UEFI based x64 Server This installation procedure assumes LUNs are created in the SAN storage device and zoned appropriately to the host adapter s WWN To install a new Windows Server UEFI aware operating system 1 From the server system UFFI setup ensure that CD DVD is the first device in the Boot Order list Enable the adapter BIOS setting to allow SAN boot in the Emulex UEFI configuration utility Configure the boot target and LUN in Emulex UEFI configuration utility to select the desired target Boot the host server with the Windows Server 2008 or 2012 DVD inserted Follow the on screen prompts to install the appropriate version of Windows Server 2008 or 2012 The Windows installation exposes all available visible LUNs as disks and partitions numbered 0 to N where N is the highest number available These numbers typically are the LUN numbers assigned by the array Select the disk on which you want to install the operating system Follow system prompts in the Windows installation Note The operating system image is installed w
67. 2C0000 Firmware Version 2 703 269 2 BIOS Enabled Port Name 10000000C95B7595 Node Name 20000000C95B7595 Ulan ID 0001 DCBX mode CEE mode No PLOGI Retry 0 msec Default Figure 5 20 Change the PLOGI Retry Timer Screen Select the retry timer interval Press lt Enter gt to accept the new interval Press lt Esc gt to return to the advanced adapter configuration menu For changes to take effect reboot the system Doe w amp Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 69 SG EMULEX Configuring Advanced Adapter Parameters Enabling or Disabling the Spinup Delay This option allows you to enable or disable the disk spinup delay The factory default setting is disabled If at least one boot device has been defined and the spinup delay is enabled the boot BIOS searches for the first available boot device e Ifa boot device is present the boot BIOS boots from it immediately e Ifa boot device is not ready the boot BIOS waits for the spinup delay and for up to three additional minutes continues the boot scanning algorithm to find another multi boot device If boot devices have not been defined and auto scan is enabled then the boot BIOS waits for five minutes before scanning for devices e Ina private loop the boot BIOS attempts to boot from the lowest target AL_PA it finds e Inanattached fabric the boot BIOS attempts to
68. 4 drwxr xr x 3 root root 16384 Jan 1 1970 root orleansrhel5564 ls lar test2 efi boot bootx64 efi elilo conf initrd linux root orleansrhel5564 ls lar test2 efi boot total 26838 rwxr xr x root root 3231872 May 20 2010 linux root root 23999623 May 20 2010 initrd root root 512 May 20 2010 elilo conf root root 241318 May 20 2010 bootx64 efi drwxr xr x root root 2048 May 20 2010 drwxr xr x 2 root root 2048 May 20 2010 root orleansrhel5564 cp test2 boot efi tftpboot linux install Ywxr Xr xX Ywxr Xr xX Ywxr Xr xX Wr PP Pp Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFINIC 197 gt EMULEX UEFI NIC Server Configuration Script for SLES11 SPx NFS Server Configuration Script root bglinux156 etc re d init d portmap restart Stopping portmap OK Starting portmap OK root bglinux156 etc re d init d nfslock restart Stopping NFS locking OK Stopping NFS statd OK Starting NFS statd OK root bglinux156 etc re d init d nfs restart Shutting down NFS mountd OK Shutting down NFS daemon OK Shutting down NFS quotas OK Shutting down NFS services OK Starting NFS services OK Starting NFS quotas OK Starting NFS daemon OK Starting NFS mountd OK Check if the NFS services are running root bglinux156 rpcinfo p program vers proto port
69. 49 nfs 100003 3 udp 2049 nfs 100003 4 udp 2049 nfs 100003 2 tcp 2049 nfs 100003 3 tcp 2049 nfs 100003 4 tcp 2049 nfs 100005 1 udp 828 mountd 100005 1 tcp 831 mountd 100005 2 udp 828 mountd 100005 2 tcp 831 mountd 100005 3 udp 828 mountd TFTP Configuration root orleans vi etc xinted d tftp default off description The tftp server serves files using the trivial file transfer protocol The tftp protocol is often used to boot diskless workstations download configuration files to network aware printers and to start the installation process for some operating systems service tftp disable no socket _type dgram protocol udp wait yes user root Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 201 gt G EMULEX UEFI NIC Server Configuration Script for RHEL 6 x server usr sbin in tftpd server_args s tftpboot linux install per_source 11 cps 100 2 flags IPv4 H H HH Restart TFTP service root orleans service xinetd restart Stopping xinetd OK Starting xinetd OK root orleans chkconfig tftp on PXE Configuration root orleans cd work rhel6364 root orleans RHEL6364 cd images pxeboot root orleans pxeboot cp r tftpboot linux install HHHH Copy vmlinuz and initrd to TFTP root directory root orleans pxeboot mkdir p root test1l root orleans images cd
70. 5 0 option domain name pxe_ test option time offset 8 Eastern Standard Time we want the nameserver to appear at a fixed address host orleansrhel5564 next server 192 168 47 1 IP of the NFS Server hardware ethernet 00 00 c9 5b a5 26 mac address of the client machine fixed address 192 168 47 60 IP assigned to the client machine option host name linux test filename bootx64 efi Used for UEFI boot This sets up a DNS server that will assign IP Address 192 168 47 60 to the client machine that has MAC Address 00 00 c9 5b a5 26 assigned to a PXE UEFI capable NIC The only thing that needs to be changed in the above is the MAC Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFINIC 199 gt EMULEX UEFI NIC Server Configuration Script for RHEL 6 x Address to match that of the NIC in the client box The IP address that follows the next server option should be the IP address of the tftp server root bglinux156 service dhcpd restart Shutting down dhcpd OK Starting dhcpd OK TFTP Server Setup root orleansrhel5564 cat etc xinetd d tftp service tftp disable no socket_type dgram protocol udp wait yes user root server usr sbin in tftpd server args s tftpboot linux install per_source 11 cps 100 2 flags IPv4 UEFI NIC Server Configuration Script
71. 697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 43 gt G EMULEX Solaris Configuring Boot from SAN on Solaris SFS SPARC To configure boot from SAN 1 9 If necessary install or update the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information If necessary enable the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information Type the following at the OBP prompt show devs The ID information for each found adapter is displayed such as pci 22 600000 pci 0 pci 9 pci 0 pci 9 emlx 0 Enable boot from SAN on each Emulex adapter in the system by typing the following set of commands replacing adapter_id with the ID information such as shown above for each Emulex adapter in turn There is a space between the first quotation mark and the first character of the adapter ID adapter_id select dev for example pci 22 600000 pci 0 pci 9 pci 0 pci 9 emlx 0 select dev set sfs boot unselect dev After all Emulex adapters have been enabled to boot from SAN reset the system with the following command reset all After the system resets boot the Solaris installation CD and follow the prompts After the installation completes successfully you will be prompted to reboot or exit the system Press lt gt and then press the lt Enter gt key to go to the Unix prom
72. 6CiE WWN 00000000 00000000 WWN 00000000 00000000 WWN 000060000 00000000 WWN 00000000 00000000 WWN 00000000 00000000 WWN 00000000 00000000 WWN 00000000 00000000 Discard Changes Commit Changes gt Ce e a a aa a a a Figure 12 12 Delete Boot Device Screen 4 Select Commit Changes and press lt Enter gt The Emulex Adapter Configuration Main Menu is displayed Changing Boot Device Order Note The boot device order has no relationship to the system BIOS boot device order Changing the boot device order with this procedure will only change the order that the devices are discovered by UEFIBoot To change boot device order 1 From the Device Manager screen Figure 12 2 select the adapter whose boot device order you want to change and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Change Boot Device Order and press lt Enter gt The Change Boot Device Order screen is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A sc 12 Configuring UEFI for FCoE 168 gt EMULEX Changing Boot Device Order 3 Select Boot Device Order and press lt Enter gt OCe10102 FM Node Name 20000000C95387557 Discard Changes and Go ere are the discovered targets to the Previous Page Discard Changes commit Changes Boor Device Order lt 01 WWN 21000020 37E16C1E gt lt 02 WWN 21000020 37E19C64 gt lt 03 WWN 00000000 00000000 gt lt 04 WWN 0000000
73. A Rev A 2 Configuring PXE Boot for the NIC Protocol 34 gt EMULEX Using the PXESelect Utility 3 Select Save and press lt Enter gt 4 To proceed select Continue and press lt Enter gt With the Multichannel Mode selected you can now configure multichannel support See Multichannel Configuration for more information Multichannel Modes Note The following modes are only available on IBM adapters and systems that support IBM Virtual Fabric and Unified Fabric Protocol modes An IBM Virtual Fabric enabled switch provides the ability to configure an LPVID for a virtual channel or I O channel on a OneConnect port If multichannel is supported on your system the PXESelect utility enables you to select one of the following modes e IBM Virtual Fabric Mode select this mode when a OneConnect controller is attached to an IBM Virtual Fabric enabled switch e IBM Unified Fabric Protocol Mode select this mode when a OneConnect controller is attached to an IBM UFP enabled switch Note Some IBM switches support both UFP and IBM Virtual Fabric Mode e Switch Independent Mode select this mode if you are using a switch other than an IBM Virtual Fabric or UFP enabled switch When this mode is enabled refer to Configuring Universal Multichannel on page 31 for information on configuring multichannel Note Multichannel functionality is only supported on OneConnect controllers running in 10 Gb mode The 1 Gb mode does no
74. A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 47 gt EMULEX Ea mount dev dsk clt1d0s7 export2 ufsdump 0f dev rdsk cOt0d0s7 cd export2 ufsrestore rf umount export2 15 Perform copy mount dev dsk cltid0s0O root2 ufsdump 0f dev rdsk cotodoso cd root2 ufsrestore rf 16 Edit root2 etc vfstab changing the controller number target number and LUN number to point to the new FC boot disk For example if the FC boot disk is c1t1d0 replace all local disk entries of cOt0d0 with c1t1d0 Currently file shows dev dsk cOt0d0s1 swap dev dsk cOt0d0sO and dev rdsk c0Ot0d0s0O root dev dsk coOt0d0s6 and dev rdsk cOt0d0s 6 usr dev dsk cOt0d0s7 and dev rdsk cOt0d0s7 export Edit file to show dev dsk cltidisl1 swap dev dsk clt1d0soO and dev rdsk cl1t1d0s1 root dev dsk clt1id0s6 and dev rdsk clt1d0s6 usr dev dsk clt1d0s7 and dev rdsk clt1id0s7 export 17 Reboot the system sync halt reset all 18 Boot to disk boot disk The system should boot to the FC disk 19 View the current dump device setting dumpadm 20 Change the dump device to the swap area of the FC drive dumpadm d dev dsk cliti1d0s1 where dev dsk c1t1d0s1 is a sample path to the swap area of the FC drive Booting Solaris 10 from the Network on SPARC Machines To boot from the network 1 Set up the install server and the boot server if required See the topic for Network Based Instal
75. Boot Support iSCSI Initiator Name ign 1990 07 com emulex 00 00 c9 be ce 41 Boot Support lt Enable gt Save Changes Controller Properties Network Configuration iSCSI Target Configuration Erase Configuration Figure 11 3 Controller Configuration Menu Screen with Boot Support Setting Highlighted 2 Select Boot Support and press lt Enter gt 3 From the Boot Support drop down menu select Enable or Disable and press lt Enter gt 4 To save your changes select Save Changes and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX 11 Configuring UEFI for iSCSI Configuring the Controller 137 Configuring the Controller To configure the controller 1 From the Storage screen Figure 11 1 select the Emulex iSCSI Utility for a particular function and press lt Enter gt The Controller Configuration Menu is displayed Figure 11 2 2 From the Controller Configuration Menu screen select Controller Properties and press lt Enter gt The Controller Properties screen is displayed Controller Model Number Controller Description BIOS Version Firmware Version Discover Boot Target via DHCP Save Changes Controller Properties Emulex OneConnect Controller Model Number 0Ce11102 IM 2 port PCIe 10GbE CNA Emulex OneConnect 0Ce11102 IM 2 port PCIe 10GbE CNA v46 00a0 4 6 152 0 lt Disable gt Figure 11 4 Controller Properties Screen
76. C adapter you want to modify and press lt Enter gt The Emulex NIC Selection screen Figure 10 2 shows information for the selected adapter Select Emulex Flash Update Utility and press lt Enter gt The Emulex Flash Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 106 gt EMULEX Using the Emulex NIC Configuration Utility Update Utility screen is displayed This utility displays all available media and installs the flash file on the adapter Emulex Flash Update Utility Tl Move Highlight lt Enter gt Select Entry Esc Ex it Figure 10 4 Emulex Flash Update Utility 5 Press lt Enter gt to select the media containing the flash file Emulex Flash Update Utility Firmware RECYCLER UEFI Tl Move Highlight lt Enter gt Select Entry Figure 10 5 Emulex Flash Update Utility with Directory Name Dialog Box Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 107 gt lt EMULEX Using the Emulex NIC Configuration Utility 6 Navigate to the directory containing the flash file and press lt Enter gt Emulex Flash Update Utility be3flash_103_397_38 uf i oc11 4 0 200 10 ufi be3f lash_103_397_3806 uf i oc11 4 0 265 2 ufi be3f lash_104_335_0 ufi oc11 4 0 290 0 ufi oc11 4 0 291 0 ufi oc11 4 0 301 0 ufi oc11 4 0 304 0 ufi oc11 4 0 333 0 ufi oc11 4 0 1001 0 ufi oc11 4 0 1019 0 ufi oc11 4 0 265 2 ufi o0
77. Dev 00 Controller 1 Bus 06 Dev 00 Controller 2 Bus 09 Dev 00 Figure 2 2 Controller Selection Menu Note The Controller Selection Menu only appears if there are two or more adapters connected The Controller Configuration menu appears MultiChannel Mode Advanced Mode Support Enabled Personality Disabled Figure 2 3 Controller Configuration Menu Depending on the adapter one or more of the following options will be displayed e MultiChannel Mode when multichannel is enabled you can access up to eight virtual network interfaces e For additional information on Multichannel Mode see Configuring Universal Multichannel on page 31 Note If you are using an IBM adapter see Configuring Multichannel for IBM Adapters on page 33 for additional information on Multichannel Mode Note A reboot will occur when you exit the PXESelect utility if the Multichannel Mode has changed since the last boot e Advanced Mode Support Advanced Mode support is enabled by default on OCe11100 series 2 port and 4 port controllers Advanced Mode support enables you to run Advanced Mode aware drivers that provide advanced capabilities For additional information on configuring Advanced Mode see Advanced Mode Support on page 26 e Personality This option specifies a list of available protocols that can be configured on an adapter For additional information on adapter personality see Personality Option on pag
78. EE Parameters Configure FCF CIN Parameters Configure Advanced Adapter Parameters Enter lt Esc gt to Previous Menu lt tvl gt to Highlight lt Enter gt to Select Figure 5 2 Main Configuration Menu Under normal circumstances you would first configure boot devices using the BIOS Utility However if the adapter is not enabled to boot from SAN you must first enable the adapter to do so Enabling an Adapter to Boot from SAN To enable an adapter to boot from SAN from the Main configuration menu select Enable Disable Boot from SAN and press lt Enter gt Note Adapters are disabled by default At least one adapter must be enabled to boot from SAN in order to use remote boot functionality Once you enable an adapter the status of the boot BIOS changes as shown in Figure 5 3 01 OCe10100 Bus 02 Devt 00 Funct 02 Mem Base CE2C0000 Firmuare Version 2 702 485 1 BIOS Enabledt Port Name 10000000C935B 7791 Node Name 20000000C95B7791 Ulan ID 0001 DCBX mode CEE mode Boot BIOS is Enabled Enable Disable Figure 5 3 BIOS Status Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 59 gt lt EMULEX Scanning for Target Devices Scanning for Target Devices To scan for target devices 1 From the Main configuration menu select Scan for Target Devices This option only displays a list of discovered target devices It
79. ELILO Boot Message Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SG EMULEX Appendix C Example for Configuring and Booting UEFI NIC 206 Configuring the IBM HS22 Blade with e Raptor MEZZ 5 The Language Selection menu is displayed Select a language and click OK Afrikaans BnarapcKu Catala CeStina Dansk Deutsch Espa ol Fran ais E Amy K Italiano Japanese Magyar Neder lands Norsk Polski Portugu s Portugu s Brasileiro Pyccxua Simplified Chinese Select the language Back Figure C 5 Language Selection Menu 6 The Main menu is displayed Select Expert and click OK Start Installation Settings Exit or Reboot Figure C 6 Main Menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 207 gt lt EMULEX Configuring the IBM HS22 Blade with e Raptor MEZZ 7 The Expert menu is displayed Select Kernel Modules Hardware Drivers and click OK Expert Time 68 10 System Information Kernel Modules CHarduare Drivers Verify Installation CD ROM DUD Eject CD Show config Change conf ig Start shell Figure C 7 Expert Menu 8 The Kernel Modules Hardware Drivers menu is displayed Select Add Driver Update and click OK Kernel Modules Hardware Drivers Load IDE RAID SCSI Modules Load Network Card Modules Load PCMCIA Modules Load WULAN Modules Load USB M
80. Enter gt Figure 12 2 Device Manager Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SXC EMULEX 12 Configuring UEFI for FCoE 158 Updating Firmware and Boot Code The Emulex Adapter Configuration Main Menu is displayed 001 OCe10102 FM PCIe2 5Gb s x8 Back to Display eg 00 Bus 04 Dev 00 Func 02 VlanID 0002 Adapters and RECONNECT OCe10102 FM Node Name 20000000C9587857 DEVICES ECT DEVICES lt CEE gt onfigure CEE FCF Parameters Onfigure CIN FCF Parameters Scan for Fibre Devices Add Boot Device Delete Boot Device Change Boot Device Order onfigure HBA and Boot Parameters Set Emulex Adapter to Default Settings Figure 12 3 Emulex Adapter Configuration Main Menu Updating Firmware and Boot Code To update the firmware and boot code to the latest versions you must use the NIC firmware update utility which revises the FCoE function with a single firmware and boot code image For more information on revising firmware versions see chapter 10 Configuring UEFI for Ethernet on page 102 Enabling an Adapter to Boot from SAN To enable an adapter to boot from SAN 1 From the Device Manager screen Figure 12 2 select the adapter whose network boot setting you want to change and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Set Boot from SAN The current setting is displayed A Disable Enable menu is displayed Pres
81. FC fabric s WWN to which to connect This must be an 8 digit hexadecimal number e Fabric Name Hi Enter the high bits of the FC fabric s WWN to which to connect This must be an 8 digit hexadecimal number 5 Do one of the following e To save your changes select Commit Changes and press lt Enter gt The changed CEE FCF record information is displayed e To discard all changes select Discard Changes and press lt Enter gt The CEE record selection list is displayed Figure 12 6 e To discard your changes and use the CEE parameters from the FCF table select Select From FCF Table and press lt Enter gt The FCF table parameters are displayed 6 Press lt Enter gt The Emulex Adapter Configuration Main Menu is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 163 gt lt EMULEX Configuring CIN FCF Parameters Configuring CIN FCF Parameters To configure CIN FCF parameters 1 From the Device Manager screen Figure 12 2 select the adapter to configure and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Configure CIN FCF Parameters and press lt Enter gt A listing of current CIN FCF record information is displayed 3 Select the CIN FCF record to modify and press lt Enter gt Current record information is displayed onfigure CIN FCF Parameters Active shows the ctive VLAN ID 0000 FC_ MAP OEFCOO ex
82. Figure C 13 Figure C 14 Figure C 15 Figure C 16 Figure C 17 Figure D 1 Figure D 2 Figure E 1 Boot for NIC iSCSI and FCoE Protocols User Manual List of Figures CIN FCF Record Information wisciess scree cer tihunntcees copied eveoisreiiaimeieeets 163 SAN Discovery Targets St c idarcctadeitawscacteid aceaadnidaniaaceeidanteanieetant 165 LUN MIS IG d aiaeatenade nies sruadereessyseatecnsersasaratassecas nira i 165 Commit Discard Change wicca ve scveseei seem ce i pa wlar este aia iawvel 166 Delete Boot Device Screen i sie sses stash wasaeeesstmsnesagardeteaanaihastersy iotiereeses 167 Change Boot Device Order SCreen c ccceeee cnet eee e nett eee test eae nnne 168 Boot Device Order Screen cicxcaddscccspectinrdaancedcanearmemad poekaeen ieee ban 168 Change Boot Device Order SCree n ccecceeee cece eee e eee eee tee eeaeeneeeaes 169 Change Boot Device Order Screen with Revised Boot Order eesse 169 Change Boot Device Orders ccascscacuccnvacitcarences sheadensst ites cmssaceesseaneishe 170 PROG Retry TIMer ccscnceonassteeatenacvonsitedatacsatudnctiaccetiendisandibenaiseatutes 171 Configure HBA Parameters Maximum LUNs Target Field 068 172 Configure HBA Parameters Boot Target Scan Method Menu 655 173 Configure HBA Parameters Delay Device DiSCOVEry cece eee eee eee 174 Set Adapter Defaults xccccscenewcvsapenaancun emeemseeaseenepnen acecepnendecenennence 176 Controller
83. HCPOFFERs that include the NBP filename and boot server lists e The PXE client attempts to download the specified NBP over TFTP from one of the specified boot servers but fails e The PXE client does not execute the downloaded NBP Outcome If any of these issues occur the boot process continues using the next available device in the boot sequence PXE Error Codes Table 13 1 PXE Error Codes Error Codes Possible Reason Comment Solution Init Error Codes PXE EO1 PCI Vendor and Device The PCI BIOS passes This message should never be seen IDs do not match Bus Device Function numbers in in the production level BIOS AX register when it initializes the OptionROM If the vendor ID amp device ID did not match the vendor ID and the device ID in the device s PCI configuration space with the UNDI device PCI structure defined in UNDI driver initialization code this error is displayed PXE E04 Error reading PCI Any of the PCI BIOS INT 1Ah calls This should not happen with any Configuration space to read the PCI configuration production level motherboard space failed BIOS PXE E07 PXE BIOS calls not The PCI system BIOS does not This should not happen with any supported support INT 1Ah services PCI BIOS as all PCI BIOS must support these services Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX Table 13 1 PXE Error Codes Continued 13 Troubleshooting 179
84. I The Spanning Tree Protocol is used to calculate the best path between switches where there are multiple switches and multiple paths through the network 3 Install a Windows Server operating system over the iSCSI LUN 4 Once Windows Server is installed install the MPIO software such as Microsoft iSCSI Initiator and reboot the system 5 After rebooting ensure that the boot LUN is detected by the MPIO driver This can be done by either of the following two methods e For Windows Server 2008 Windows Server 2008 R2 and Windows Server 2012 o Look at the driver name for the disk device from Device Manager Or Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 4 Configuring x86 x64 Platforms for the iSCSI Protocol 54 gt EMULEX Configuring for the iSCSI Protocol 6 7 o Use the MPIO GUI to check for device ID MS FT2005iSCSIBusType_0x9 under the MPIO Devices tab The Disk Manager does not show duplicate disks Reboot your system and log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted You can now add an additional boot path with the iSCSISelect utility To add an additional boot path to the same iSCSI LUN a Follow the steps for the Windows Server on page 52 to set up the second path b At the Add Ping iSCSI Target menu make sure you set a valid ISID Qualifier before adding your target For more information on the ISID Qualifier see Setting an ISID Value
85. Introduction 18 Abbreviations OneCommand Manager original equipment manufacturer operating system Peripheral Component Interconnect Peripheral Component Interconnect Express protocol data unit physical function port login power on self test Preboot eXecution Environment redundant array of independent disks Red Hat Enterprise Linux Remote Installation Services read only memory resource package manager receive side scaling storage area network Small Computer System Interface SUSE Linux Enterprise Server Service Level Interface Simple Network Protocol single root I O virtualization service VLAN ID terabyte transmission control protocol Trivial File Transfer Protocol Universal Configuration Manager universal converged network adapter User Datagram Protocol Unified Fabric Protocol Unified Extensible Firmware Interface universal multichannel Universal Network Device Interface Universal Serial Bus virtual function virtual local area network virtual machine Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 1 Introduction gt G EMULEX Abbreviations 13 VMQ virtual machine queue vNIC virtual NIC WDS Windows Deployment Services WWN world wide name WWNN world wide node name WWPN world wide port name xX Used to designate a variable For example SPx includes SP1 SP2 etc ZB zettabyte Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configur
86. LEX Configuring the Network 3 Select Configure Static IP Address and press lt Enter gt The Configure Static IP Address screen appears Configure Static IP Address IP Address 172 40 46 100 Save the Configuratio Subnet Mask 255 255 255 0 Changes Default Gateway 0 0 0 0 Save Changes Figure 11 6 Configure Static IP Address Screen 4 Enter the IP address subnet mask and default gateway in the corresponding fields 5 Select Save Changes and press lt Enter gt Configuring VLAN ID Priority A VLAN is a way of partitioning the network If the LAN is made up of all devices within a broadcast domain a VLAN is a broadcast domain made up of switches You first create a VLAN and then assign ports to a VLAN All ports in a single VLAN are in a single broadcast domain You do not have to configure VLANs unless your network is already using them Some reasons why VLANs are used include e ALAN increases in size with numerous devices e ALAN has extensive broadcast traffic on it e Groups of users on a LAN need more security A VLAN ID like an IP address or initiator name is assigned a value to uniquely identify it on a network A VLAN priority is set to determine what packet gets priority order within a VLAN Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 140 gt lt EMULEX Configuring the Network To configure a VLAN ID priority 1 On the Network Configuration menu
87. LEX Starting the Emulex iSCSI Configuration Utility The Controller Configuration Menu screen is displayed Controller Configuration Menu Enter Initiator IQN Name iSCSI Initiator Name ign 1990 07 com emulex 00 00 c9 be ce 41 Boot Support lt Enable gt Save Changes Controller Properties Network Configuration iSCSI Target Configuration Erase Configuration Figure 11 2 Controller Configuration Menu Screen 2 Highlight iSCSI Initiator Name and press lt Enter gt to edit the initiator name This is a global setting The initiator name configured on one adapter is reflected on all adapters in the system Note HP systems are an exception to the previous statement Each port on an HP system can be configured with a unique initiator name 3 To save changes select Save Changes and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 136 gt lt EMULEX Configuring Boot Support Configuring Boot Support Boot support is provided for each port or function If boot support is enabled you can boot from the specified function If boot support is disabled you will not be able to boot from the function To configure boot support 1 From the Storage screen Figure 11 1 select the Emulex iSCSI Utility for a particular function and press lt Enter gt The Controller Configuration Menu is displayed Controller Configuration Menu Enable Disable
88. MONU ciideciicitieccasunsesedsadaneienicagexekscRentaxseoassiaxesdvdabdons 61 Primary Boot Device Set Up Screen 0 cceeceece enter teeta etna teen teenies 62 DCBX Men 4 witihig toeneiehrtneenctuaieaniiecties ein TENER EEEE AEAEE ee 62 PCP LISINO cciias 63 Save Edited Boot Record Dialog BOX ssssssssiirrsssrrnnrrrrnnnnrrrnnrrrrrrrererrre 63 CIN Configuration Menu s sssssssssssrrrrrerrrrtstrrrrrrrr trta rrr rrrrrrrrrrarrrrrr 64 FCF CIN VLAN Dreesmann na a a aa A E a a A 64 Enable or Disable VLAN ID Screen cece ccc c ene e cette sents renee renee nents nente es 65 Set FCF Wrap Byte Screen itssccsassdrsr esata ridin nies eniid reds ohessreaiadnaideniiaenks 65 Advanced Adapter Configuration Menu cece eeeeee eect cnet eee etna enna 66 Change Default ALPA Screen cccccccececce cent renee renee sense sean eeeneenenae nes 67 Change the PLOGI Retry Timer SCr e n cccceceeceeeeeeeeeeeeeeneeeeneenenee nes 68 Enable or Disable Spinup Delay Screen 2 c ecceeee eee e eee eeee eee eeeeeeaes 69 Set Auto S an MENU ss p25 seers ccteanntsbasthelateucincasdinscestatdbin daanin aai 70 Enable or Disable EDD 3 0 Screen ssssssssrsrirereerrrerrrrrrerrrrrrrrrrrrrrrerre 71 Enable or Disable Start Unit Command Screen ccceeeeeee cess teat ene 72 Enable or Disable Environment Variable SCre n cccceceeeeeee sent ee eeeeeene ees 72 Enable or Disable Auto Boot Sector Format Screen
89. OA8 toCload pxelinux cfg COA to load pxelinux cfq co to load pxelinux cfg c Figure B 6 Enabling Network Boot Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 196 gt EMULEX UEFI NIC Server Configuration Script for SLES11 SPx Appendix C Example for Configuring and Booting UEFI NIC UEFI NIC Server Configuration Script for SLES11 SPx root orleansrhel5564 ls root slesllisp164 SLES 11 SP1 DVD x86 64 GM DVD1 iso root orleansrhel5564 mkdir testl root orleansrhel5564 mkdir test2 root orleansrhel5564 mount o loop slesllsp164 SLES 11 SP1 DVD x86_64 GM DVD1 iso testl root orleansrhel5564 1s test1 ARCHIVES gz COPYING degpg pubkey 3d25d3d9 36e12d04 asc media 1 boot COPYRIGHT gpg pubkey 7e2e3b05 4be037ca asc NEWS ChangeLog COPYRIGHT degpg pubkey 9c800aca 4be01999 asc pubring gpg content directory yast gpg pubkey a1912208 446a0899 asc README content ascdocu gpg pubkey b37b98a9 4be0lala asc suse content keygpg pubkey 0df b3188 41ed929b ascINDEX gz control xmgpg pubkey 1d061a62 4bd70bfa asclicense tar gz COPYING gpg pubkey 307e3d54 4be01a65 ascls 1R gz root orleansrhel5564 mount o loop test1 boot x86 64 efi test2 root orleansrhel5564 ls lar test2 total 28 rwxr xr x 1 root root 48 May 20 2010 packages boot efi drwxr xr x 3 root root 2048 May 20 2010 efi drwxr x 20 root root 4096 Jan 5 14 0
90. PXE VLAN is used However once the NIC driver is operational the LPVID is used Note If no PXE VLAN is configured the LPVID is used For example PXE Install OS PXE Server configured with VLAN 5 PXE VLAN 5 LPVID for function 0 5 To configure LPVID 1 On the configuration screen use the lt Tab gt key to select LPVID and a dialog box appears 2 Enter a value and press lt Enter gt The LPVID range is 2 4094 A value of 0 disables the LPVID 3 Select Save and press lt Enter gt Configuring Multichannel for IBM Adapters Note This section only pertains to certain Emulex OneConnect UCNAs that support IBM Virtual Fabric multichannel or Unified Fabric Protocol When you want to enable multichannel on IBM adapters you must select a Multichannel Mode To select the Multichannel Mode 1 From the Controller Configuration menu use the lt Tab gt key to select the Multichannel Mode setting and a drop down menu appears MultiChannel Mode Personality Switch Independent Mode IBM Virtual Fabric Mode IBM Unified Fabric Protocol Mode Disabled Figure 2 11 Controller Configuration Screen IBM Adapters 2 Select one of the following settings and press lt Enter gt e Switch Independent Mode e IBM Virtual Fabric Mode e IBM Unified Fabric Protocol Mode e Disabled Note For more information on the available Multichannel Modes see Multichannel Modes Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01
91. PXE client interface hardware ethernet 00 00 C9 BB C7 8F fixed address 192 168 1 60 interface option host name linux test filename bootx64 efi HHHH Restart DHCP service root orleans service dhcpd restart Shutting down dhcpd Starting dhcpd 0 IP address of PXE server interface connected HHHH MAC address of PXE client interface IP address to be assigned to PXE client OK OK Note Reboot your system under test and boot from the PXE client interface Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 203 gt lt EMULEX Configuring the IBM HS22 Blade with e Raptor MEZZ Configuring the IBM HS22 Blade with e Raptor MEZZ To install and update the driver follow these steps 1 Press lt F1 gt during the system boot and log into the System Configuration and Boot Management screen System Configuration and Boot Management System information This selection Systen Settings displays the basic Date and Time details of the Systen Start Options Boot Hanager Systea Event Logs User Security Save Settings Restore Settings Load Default Settings Exit Setup Figure C 1 System Configuration and Boot Management Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 204 gt lt EMULEX Configuring the IBM
92. Screen ssssssssssrsrrrererrsrsrrrrrrerrrrsrr 152 ISNS Server IP Screen essissssssssrrrrrrrnrrrrrrerrrrranetttrrnnntrrrnnrtnrrrnrent 153 Available Servers SCNCSMiscases savesiacvenacvecedeseasepiausieeudteasniwen diizaninssives 153 ISNS Server Options Screen ccecce 154 Erase Configuration Screen i 2 cepcartoactnasnecpen E 155 Exiting the EFI Shell scectscsxtieeddscevavncdeveieesecatsiacigecdeasteispeetacereecdeshs 157 Device Manager Screen 157 Emulex Adapter Configuration Main Menu cccccccseeeeeeeeaeeeeaeeeeneeens 158 Emulex Adapter Configuration Main Menu Network Boot Options MENU ciiicesteeesStecaeaedtecesteenedatemsaciedareenmackt pen eeeeeanannsmensiaecennroelies 159 Emulex Adapter Configuration Main Menu DCBX Menu cceseeeee eee e ees 160 CEE Record Selection LS wxciuses cycteencnaartiabescasyekcisesn habia tenensoleeaey 161 CEE FCF Record Information cciseeaiced cc tccsee ceased cee eceieeseesiented eens 162 and FCoE Protocols User Manual P009697 01A Rev A 12 gt G EMULEX Figure 12 8 Figure 12 9 Figure 12 10 Figure 12 11 Figure 12 12 Figure 12 13 Figure 12 14 Figure 12 15 Figure 12 16 Figure 12 17 Figure 12 18 Figure 12 19 Figure 12 20 Figure 12 21 Figure 12 22 Figure 12 23 Figure B 1 Figure B 2 Figure B 3 Figure B 4 Figure B 5 Figure B 6 Figure C 1 Figure C 2 Figure C 3 Figure C 4 Figure C 5 Figure C 6 Figure C 7 Figure C 8 Figure C 9 Figure C 10 Figure C 11 Figure C 12
93. Select Utility on page 80 e iSCSI Target s An iSCSI SAN has one or more iSCSI targets which house and make available the storage used within the SAN The iSCSI target is the storage device itself or an appliance that controls and serves volumes or virtual volumes The target is the device that performs the SCSI command or bridges it to an attached storage device iSCSI targets can be disks RAID arrays or even FC fabrics For additional information on iSCSI targets see chapter 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility on page 86 e Networking infrastructure The networking infrastructure in an iSCSI SAN uses Ethernet transport The configuration and complexity of the storage network depends on its intended function and the required capabilities Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 4 Configuring x86 x64 Platforms for the iSCSI Protocol 5 gt EMULEX Managing an iSCSI Session Managing an iSCSI Session To transmit information from an iSCSI initiator to an iSCSI target the initiator must first establish a session with the target through an iSCSI login process The login process e Starts a TCP IP connection e Verifies that the iSCSI initiator has access to the iSCSI target authentication e Allows negotiation of various parameters Logging into an iSCSI Session An iSCSI session has two phases e Login Phase iSCSI parameters are negotiated using log
94. Serial Console Edit Extra Kernel Boot aj Diskless OS Network OS Install Snapshot name Generate Kickstart File Ethernet lt Remote Logging Enable Host x Cancel Figure B 5 Edit Dialog Box 2 Inthe Hostname or IP Address Subnet field enter the IP address fully qualified hostname or a subnet of systems that should be allowed to connect to the PXE server for installations In Figure B 5 the Hostname IP Address is the IP address of the client machine 3 In the case of a multi boot environment select an operating system preference Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A o Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot 194 gt EMULEX Linux and Citrix PXE Server Remote Installation Procedure 4 Select the operating system identifier to install on this client The list is populated from the network install instances created from the Network Installation dialog box 5 Ifyou use a serial console check the Serial Console check box 6 Specify the location of a kickstart file such as http server example com kickstart ks cfg This file can be created with the Kickstart Configuration Note Ignore the Snapshot name and Ethernet options They are only used for diskless environments 7 Click OK This closes the dialog box and creates configuration files within tfitpboot linux install and tftpboot linux install pxelinu
95. T 512 No IET 512 No IET Fiz No 012 IET 512 No 013 IET Tia No 014 IET 512 No 015 IET 512 No 016 IET 512 No 017 IET 512 No 018 IET 512 No 019 IET 512 No DONT A UN e Figure 9 12 LUN Configuration Menu 2 Press lt F3 gt to set the boot LUN if the target is a boot target By setting the LUN to bootable you can confirm that you have the boot target configured properly and see the LUN from which you are booting By looking at the LUN size you can also determine which target is which along with the LUN order Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 97 gt EMULEX Managing an iSCSI Target Note The LUN order is determined by the target and is in the order listed If there are no LUNs available the following message is displayed No LUN available please check your configuration on the Target For more information see Troubleshooting for the iSCSI Protocol on page 181 Removing and Logging Out and In of a Configured Target If you remove or delete a target you log out of the target and remove it from the list of targets To remove a target from the iSCSI Target Configuration screen select the target and press the lt Delete gt key If you log out of a target you log out of the target but the target is listed in the target list with the connection status of disconnected With a logout you ar
96. V4 iSCSI Target IP Address 172 40 46 150 TCP Port Number 3260 BladeEngine Port Number 1 Boot Target lt Yes gt ISID Qualifier Header Digest Data Digest Authentication Method lt None gt Ping Save Login Advanced Properties Login Figure 11 12 Successful Target Ping If the ping is not successful a failure message is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 146 gt lt EMULEX Adding and Configuring Targets Viewing Advanced Properties To view advanced properties 1 On the Edit Ping Target screen select more to display additional configuration options Edit Ping Target TCP Port Number 3260 iSCSI Advanced Target BladeEngine Port Number 1 Information Boot Target lt Yes gt ISID Qualifier 2 Header Digest lt No gt Data Digest lt No gt Authentication Method lt None gt Ping Save Login Advanced Properties Login Logout Delete Target LUN Configuration Figure 11 13 Edit Ping Target Screen with Additional Configuration Options Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DG EMULEX 11 Configuring UEFI for iSCSI Adding and Configuring Targets 2 Select Advanced Properties and press lt Enter gt The Advanced iSCSI Target Information screen is displayed Advanced iSCSI Target Information First Burst Length Max Burst Initial R2T Max Recu Data Segment Immediate Data
97. Windows Server 2008 and Windows Server 2012 3 Configuring Boot from SAN for the FCoE Protocol When booting from SAN the storage device is typically identified by its WWPN and a LUN By extending the server system BIOS boot from SAN capability is provided by the boot BIOS contained on an Emulex adapter in the server When properly configured the adapter then permanently directs the server to boot from a logical unit disk on the SAN as if it were a local disk Note Not all procedures are required Emulex adapters usually ship from the factory with the latest version of boot code installed and enabled so you do not need to install or enable boot code in those cases However if boot code is not installed you must install it and if it is not enabled you must enable it You may want to update the boot code if a more current version is available on the Emulex website at http www emulex com This section describes how to set up a system to boot from SAN This specific procedure to follow is determined by the system architecture and the operating system Windows Server 2008 and Windows Server 2012 Configuring Boot from SAN on Windows x86 and x64 To configure boot from SAN 1 If necessary install or update the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information If necessary enable the boot code on the adapter See chapter 6 Installing Updating
98. X MTU NBP NIC NIS NIS NIV NLB NPIV NVRAM 1 Introduction 17 Abbreviations File Transfer Protocol FoD Unique Identifier gigabits per second GUID partition table graphic user interface Globally Unique Identifier host bus adapter Human Interface Infrastructure Hypertext Transfer Protocol Institute of Electrical and Electronics Engineers PCIe legacy interrupts where x is variable input output input output control internet protocol iSCSI qualified name Internet Small Computer System Interface just a bunch of disks 1024 bytes Kilobyte or Kibibyte Link Aggregation Control Protocol Lightweight Directory Access Protocol light emitting diode LAN on motherboard logical port VLAN ID logical unit number media access control master boot record multipath I O message signaled interrupts message signaled interrupts extended maximum transmission unit network bootstrap program network interface card or controller Network Information Service Network Information Service Plus Network Interface Virtualization network loopback N_Port ID virtualization non volatile random access memory Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX OCM OEM OS PCI PCle PDU PF PLOGI POST PXE RAID RHEL RIS ROM RPM RSS SAN SCSI SLES SLI SNP SR IOV SVID TB TCP Scaacgcqaaay ag Oo 4 2 53 ZER MC Z HH es VLAN VM 1
99. a OE eaat 202 Configuring the IBM HS22 Blade with e Raptor MEZZ sssssssnnsnssnunnnnnnnnnnnnnnns 203 Appendix D Example for Installing and Booting UEFI FCOE sssssssssssssnnnnsnnns 211 Appendix E Loading and Unloading UEFIBoot from the UEFI Shell 005 213 Loading UEFIBoot from the UEFI Shell sssssssnssnsunnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 213 Unloading UEFIBoot from the UEFI Shell ssssssssusnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 213 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SXG EMULEX List of Figures List of Figures Figure 2 1 Figure 2 2 Figure 2 3 Figure 2 4 Figure 2 5 Figure 2 6 Figure 2 7 Figure 2 8 Figure 2 9 Figure 2 10 Figure 2 11 Figure 2 12 Figure 5 1 Figure 5 2 Figure 5 3 Figure 5 4 Figure 5 5 Figure 5 6 Figure 5 7 Figure 5 8 Figure 5 9 Figure 5 10 Figure 5 11 Figure 5 12 Figure 5 13 Figure 5 14 Figure 5 15 Figure 5 16 Figure 5 17 Figure 5 18 Figure 5 19 Figure 5 20 Figure 5 21 Figure 5 22 Figure 5 23 Figure 5 24 Figure 5 25 Figure 5 26 Figure 5 27 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A PXE BOOU PROCESS peiin iriri TEET EEEE EENET EAEE AERE AAA EAEE EEAS 21 Controller Selection Menu tcccscccisstciscccky iedesccderaidascstayscias caves aatascdiagias 24 Controller Configuration MeN xcs ecivevecivies woe eesvevorecedsiiweeriaesecrebesaasen 24 Port Selection Menu cave iccceseiciwerelanedereeenstbaivienentec
100. a particular VLAN to boot from every time select Configure FCF CEE Parameters from the main configuration menu Figure 5 2 and press lt Enter gt A list of discovered FCF is displayed Adapter Boot Configuration Record i VLAN ID Anyx Sw Name Match Anyx x LZA e Del lt Pg Dn FCF Sel Select the discovered FCF you wish to write into this Adapter Record Di Maa SW Mame j Figure 5 12 FCF Listing 2 Select the FCF you want to boot from every time and save this to the adapter record by pressing lt Enter gt The following message is displayed Adapter Boot Configuration Record D ULAN ID fny Sw Name Match A Del lt Pg Dn gt FCF Sel Figure 5 13 Save Edited Boot Record Dialog Box 3 Type lt Y gt to save the boot record The main configuration menu is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 64 gt EMULEX Configuring DCBX Mode Configuring CIN Parameters To configure CIN parameters on the main configuration menu Figure 5 2 select Configure FCF CIN Parameters and press lt Enter gt The CIN configuration menu is displayed 01 0Ce101900 Bus 02 Devt 00 Funct 02 Mem Base CEZCO000 Firmware Version 2 703 269 2 BIOS Enabled Port Name 10000000C95B7595 Node Name 20000000C95B7595 Vlan ID 0001 DCBX mode CEE mode Set the VLAN ID value Enable Disable VLAN ID set the FC
101. ables storage functions on Emulex adapters This feature requires a unique license key to be applied from IBM s IMM For additional information on obtaining a license key contact your IBM representative The FoD Type and FUI fields are required by IBM to generate a unique license key for the specific adapter for which you have requested a license Each controller in the system should obtain its own license key To view Feature on Demand information from the Emulex NIC Selection screen select Feature On Demand and press lt Enter gt The Feature On Demand screen appears Feature On Demand FoD Type 8005 Feature Descriptor Type FUI FXAXPSPUURNXSKSZLNY 6GHBSHBSMZ2Z52Z FoD Status No valid FoD license key found Figure 10 24 Feature On Demand Screen From the Feature On Demand screen you can view information on the feature type the FoD Unique Identifier and its current status FoD Type The FoD Type field is unique for each platform Different products have different FoD types For example LOM products have a different FoD type than mezzanine cards FUI The FUI field is internally generated by the Emulex firmware using the FoD type and the adapter s serial number The FUI is unique to each adapter because each card will have its own unique serial number Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A sc 10 Configuring UEFI for Ethernet 129 gt C EMULEX Using the Emulex NIC Configuration Utility
102. ace Disabling these ports also lowers the power consumption of the adapter Enabling any of the ports restores the previously removed PCI functions and restores the power consumption back to its normal state Note Enabling and disabling ports is applicable in both multichannel and non multichannel configurations If multichannel is enabled all virtual functions associated with the disabled port will also be disabled To configure port management 1 On the Controller Configuration screen select Port Management and press lt Enter gt The Port Management screen appears Port Management Port 0 lt Enable gt Enable Disable Port Port 1 lt Enable gt Port 2 lt Enable gt Port 3 lt Enable gt Save Port States Figure 10 23 Port Management Screen 2 Select the current setting for a particular port and a drop down menu appears 3 From the drop down menu select Enable or Disable and press lt Enter gt When you are finished select Save Port States to save the current settings Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 128 gt lt EMULEX Using the Emulex NIC Configuration Utility 5 Press lt Esc gt to return to the Controller Configuration screen Note A reboot is required for this setting to take effect Feature on Demand Note The Feature on Demand functionality is only available on some IBM adapters FoD is an IBM proprietary protocol that en
103. ake effect reboot the system Enabling or Disabling the Start Unit Command You must know the specific LUN to issue the SCSI start unit command The default setting is disabled To enable or disable the start unit command 1 From the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed Figure 5 18 2 Select Enable or Disable Start Unit Command and press lt Enter gt The Start Unit Command configuration screen is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A e 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 72 gt lt EMULEX Configuring Advanced Adapter Parameters 01 0Ce10100 Bus 02 Devitt 00 Funct 02 Hem Base CE2C0000 Firmware Version 2 703 269 2 BIOS Enabled Port Name 10000000C95B7595 Node Name 20000000C9587595 Vlan ID 0001 DCBX mode CEE mode Enable Figure 5 24 Enable or Disable Start Unit Command Screen Select whether to enable or disable the start unit command Press lt Enter gt to select the change Press lt Esc gt to return to the advanced adapter configuration menu For changes to take effect reboot the system OV Gh Enabling or Disabling the Environment Variable Sets the boot controller order if the system supports the environment variable The default setting is disabled To enable or disable the environment variable 1 F
104. allows you to quickly verify zoning and SAN connectivity while providing a mechanism to log in ports for zoning 01 0Ce10100 Bus OZ Dev 00 Func 02 Mem Base CEZC0000 Firmware Version 2 702 485 1 BIOS Enabled Port Name 10000000C95B7791 Node Name 20000000C95B7791 Vlan ID 0001 DCBX mode CEE mode Figure 5 4 Devices Present on the Adapter 2 Press lt Esc gt to return to the Main configuration menu Configuring Boot Devices Note The FC protocol supports FC AL public and private loop and fabric point to point When operating in loop FC AL topology the system automatically determines whether it is configured for a public or private loop The BIOS looks for a fabric loop FL_Port first If a fabric loop is not detected the BIOS looks for a private loop The FCoE protocol does not support FC AL To configure boot devices 1 On the main configuration menu Figure 5 2 select Configure Boot Devices and press lt Enter gt A list of eight boot devices is shown Figure 5 5 Emulex recommends that you configure only the bootable devices The primary boot device is the first entry shown It is the first bootable device If the first boot entry fails due to a hardware error the system boots from the second bootable entry If the second boot entry fails the system boots from the third bootable entry and so on Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS U
105. arget via DHCP and press lt Enter gt Enable the function by selecting Enabled from the drop down menu and press lt Enter gt 3 Select Save and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 1Q2 gt lt EMULEX Overview 10 Configuring UEFI for Ethernet Overview UEFIBoot supports uEFI version uEFI 2 3 1 compatible drivers backward compatible with 2 1 EDK version EDK2 compatible drivers Supported EFI protocols NII protocol Configuration Access protocol Component Namez2 protocol Driver Diagnostics protocol Platform to Driver Configuration protocol and Firmware Management Protocol Operating systems Windows Server 2008 R2 Windows Server 2012 Red Hat Linux 6 and SLES 11 SP2 Multi mode Switch personalities from the HII menus Multichannel Enable or disable multichannel and configure multichannel parameters from HII Blade Open Firmware Management Protocol and Universal Configuration Manager Note Only applies to IBM products Maximum controllers and ports support for up to 96 physical controllers or 192 ports Single driver Single latest driver version supports all controllers in the system This version of UEFIboot is loaded from flash into system memory For more information on loading and unloading UEFIBoot see appendix E Loading and Unloading UEFIBoot from the UFFI Shell on page 213 When UEFIBoot is
106. ation Personality Option The personality reflects the protocol or protocols of the adapter This option specifies a list of available protocols that can be configured on an adapter Depending on the personalities for which the adapter is licensed one of the following selections appears e NIC e iSCSI e FCoE The menu only displays the available personalities including both free and licensed personalities The NIC personality implies that all the enabled functions provide NIC TOE functionality iSCSI and FCoE personalities are enabled on one function per OneConnect port and include NIC functionality on the other enabled functions Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 26 gt EMULEX Using the PXESelect Utility To select the personality of the adapter 1 From the Controller Configuration menu use the lt Tab gt key to select Personality and a drop down menu appears MultiChannel Mode Advanced Mode Support Personality NIC iSCSI FCoE Figure 2 5 Controller Configuration Menu Personality Selection 2 From the drop down menu select NIC iSCSI or FCoE and press lt Enter gt 3 Select Save and press lt Enter gt Note Changing the Personality setting requires a reboot before the change will take effect A reboot will occur when you exit the PXESelect utility if the Personality setting has changed since the last boot A
107. avigating the iSCSISelect Utility sssssssssnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 77 Setting Up a Basic iSCSI Boot Configuration sssssssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnn 77 Booting the System iissirriricissisrinrrirnisrinisidtennnnarni nitri krni nanE ranni nrar EENAA 79 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Vi ee eer reer eer reer ree reer rr rer eco rT eee ee erry 80 Configuring the iSCSI Initiator Name ssssssssssnnnnnnnnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 80 Selecting a Controller sisicacsicscctisicdsscviscscsstectintcocssensscdisestnsesessesassaneseesnsde 81 Configuring Network PropertieS ssssssssssnsnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 82 Enabling DACP oerion nna arniarna e a aa E e a stat 82 Configuring a Static IP Address usssssssnnnnnnnnnnnnnnnnnnnnunnnnnnuunnnnnnnnnnnnnnnnnnnna 83 Configuring VLAN ID and VLAN Priority sssssssssnnnnnsnsnnunnnnnnnnnnnannnnnnnnnnnnnnnnnn 84 Identifying a POrtssnoseinsi terinin nnna NEn N E 84 Confirming Network SettingS sssssssnnnssssnunnnnnnnnnnnnnnnnnnnnnnnnnanunnnnnnnnnnnunnnn 85 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 86 Adding iSCSI Targets ssssssssnsunnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn nnna 86 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DE EMULEX Table of Contents 6 Using SendTargets Discovery to Add an
108. before configuring a boot target 2 Complete the normal operating system installation Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 4 Configuring x86 x64 Platforms for the iSCSI Protocol 52 SG EMULEX Configuring for the iSCSI Protocol Windows Server To set up boot from SAN for iSCSI on Windows Server 1 2 3 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted Use the iSCSISelect utility to log into a target from one adapter and configure it for boot For more information see chapter 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility on page 80 and chapter 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility on page 86 If the iSCSISelect utility is configured properly a message during boot time indicates that the iSCSI disk was successfully connected Install a Windows Server operating system over the iSCSI LUN Linux and Citrix Servers To set up boot from SAN for iSCSI on Linux or Citrix 1 2 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted Use the iSCSISelect utility to log into a target from one adapter and configure it for boot For more information see chapter 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility on page 80 and chapter 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility on page 86 If the iSCSISelect
109. boot scan option and press lt Enter gt The screen is refreshed with the modified value Note If you havea large SAN and set the boot path to Boot Path Discovered Targets discovery takes a long time Press lt Esc gt to return to the EFI utility menu 5 Select Commit Changes and press lt Enter gt The Emulex Adapter Configuration Main Menu is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 174 gt lt EMULEX Configuring Adapter Parameters Changing Device Discovery Delay This parameter sets a delay to occur after an loop initialization and before a scan is initiated to discover the target The default is off or 0 seconds Change the default if you have an HP MSA1000 or HP MSA1500 RAID array and if both of the following conditions exist e The MSA array is direct connected or part of an arbitrated loop for example daisy chained with a JBOD e The boot LUN is not reliably discovered In this case a delay may be necessary to allow the array to complete a reset Caution Do not change the delay device discovery time if your MSA array is connected to a fabric switch Setting it to any other time guarantees that the maximum delay time is seen on every loop initialization If both of the above conditions exist typically set this parameter to 20 seconds However the delay should be only long enough for the array to be reliably discovered after a reset Your
110. both the link and the activity LEDS of that port LEDs blink on the back of the server so that there is no confusion as to which physical port you are configuring with the iSCSISelect utility Port identification allows you to correlate the iSCSI software configuration with the hardware port Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A e 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility 85 DG EMULEX Confirming Network Settings Note Not all controllers have LEDs that are externally visible If you are using an add in card in a blade server environment the port identification or beaconing capability does not work To identify a port from the Controller Configuration menu select Port Identification and press lt Enter gt The LED status indicators for the selected port blink on the controller until you select Done and press lt Enter gt on the Port Identification screen The link and activity LEDs on Controller 0 Port 0 are blinking in unison Upon exit from this screen the LEDs will return to normal operation Done Figure 8 8 Port Identification Screen Confirming Network Settings After you configure the iSCSI initiator confirm your network settings by pinging the network The ping option checks whether the IP address is on the network If there is another IP entity on that network when you ping you receive a ping reply back to confirm the network settings Ping can be
111. c d e f A B C D E and F Any other characters are not allowed When you have successfully enabled the CHAP authentication the Add Ping iSCSI Target dialog box appears Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 95 SG EMULEX Managing an iSCSI Target Pinging a Target There are different ways to ping a target For instance you can ping a target from the Network Configuration menu or you can ping a target from the Controller Configuration menu From the Network Configuration Menu 1 2 3 From the Network Configuration menu select Ping and press lt Enter gt The Ping Target dialog box opens Enter IP Address Figure 9 9 Ping Target Dialog Box Enter the IP address of the target you want to ping Select Ping and press lt Enter gt From the Controller Configuration Menu 1 2 From the Controller Configuration menu select iSCSI Target Configuration and press lt Enter gt Select Add Ping iSCSI Target or Edit Ping iSCSI Target and press lt Enter gt The iSCSI Target IP Address is the address that will be pinged From the Add Ping iSCSI Target dialog box Figure 9 2 or the Edit Ping iSCSI Target dialog box Figure 9 6 select Ping and press lt Enter gt If the ping is successful you are notified that the ping is successful Figure 9 10 is an example of a successful ping Figure 9 1
112. c11 4 0 360 1 ufi Figure 10 6 Emulex Flash Update Utility with Flash File Name Dialog Box Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 108 gt EMULEX Using the Emulex NIC Configuration Utility 7 Use the arrow keys to select the flash file and press lt Enter gt to begin the update process It takes about two minutes to complete be3flash_103_397_38 ufi oc11 4 0 200 10 ufi be3flash_103_397_3806 uf i oc11 4 0 265 2 ufi be3f lash_104_335_0 ufi oc11 4 0 290 0 ufi o0c11 4 0 291 0 ufi oc11 4 0 301 0 ufi o0c11 4 0 304 0 ufi o0c11 4 0 333 0 ufi oc11 4 0 1001 0 ufi oc11 4 0 1019 0 ufi oc11 4 0 265 2 ufi tl Move Highlight lt Enter gt Select Entry Flash Update Completed Restart the Systen Figure 10 7 Emulex Flash Update Utility Flash Updating Note This firmware flash procedure only flashes the physical interface which was selected in the HII menu All Emulex adapters must contain the same firmware version to function properly The above procedure should be repeated for each physical interface installed in the system before proceeding to the next step 8 Reset the system The latest version information for the adapter is displayed in the Emulex NIC Selection screen Figure 10 2 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX Advanced Mode Support 10 Configuring UEFI for Ethernet 109 Using the Emulex NIC C
113. configuration default e Press lt Esc gt to go back to the previous menu Starting the FCoE BIOS Utility Note Links must be established before entering the FCoE BIOS utility otherwise you will receive an error message To start the FCoE BIOS utility 1 Turn on the computer and press and hold down lt Alt gt or lt Ctrl gt and press lt E gt immediately within five seconds when the Emulex bootup message to start the FCoE BIOS utility is displayed An adapter listing is displayed Figure 5 1 Note If the bootup message does not appear you must enable x86 BootBIOS For more information see Installing Updating and Enabling Boot Code on page 76 Emulex Adapters in the System 2 0Ce10100 Bus 02 Dev 00 Func 03 NWPN 10000000C95B7793 Figure 5 1 Emulex Adapter Listing Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 58 gt G EMULEX Enabling an Adapter to Boot from SAN 2 Select the adapter to configure and press lt Enter gt The main configuration menu is displayed Figure 5 2 02 0Ce10100 Bust OZ Devt OO Func 03 Mem Base CE400000 Firmware Version 2 702 485 1 BIOS Enabled Port Name 10000000C95B7793 Node Name 20000000C95B7793 Ulan ID 0000 DCBX mode CEE mode Enable Disable Boot from SAN Scan for Target Devices Reset Adapter Defaults Configure Boot Devices Configure DCBX mode Configure FCF C
114. d Fabric Protocol Mode is enabled you must configure the minimum and maximum bandwidth settings on the switch Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX 2 Configuring PXE Boot for the NIC Protocol PXE Boot Parameters Default Values 36 PXE Boot Parameters Default Values The default settings for the PXE Boot parameters are listed in the following table Table 2 2 PXE Boot Parameter Default Values Parameter Default Value Valid Values Advanced Mode Enabled OCe11100 series 2 port and Enabled 4 port controllers Disabled Disabled OCe10100 series controllers PXE Boot Support The default for this parameter varies Enabled depending on the vendor Disabled configuration SR IOV Disabled Enabled Disabled VLAN Support Disabled Enabled Disabled VLAN ID 0 0 4094 VLAN Priority 0 0 7 Multichannel Mode The default for this parameter varies For Emulex adapters depending on the vendor Enabled configuration Disabled For IBM adapters e IBM Virtual Fabric Mode IBM Unified Fabric Protocol Mode e Switch Independent Mode Disabled Minimum Bandwidth 0 Must have a total of 100 across all ports Maximum Bandwidth 0 From the minimum bandwidth value up to 100 inclusive LPVID 0 2 4094 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 37 gt G EMULEX
115. ded the Where do you want to install Windows screen is displayed 14 Select the same drive you configured as the boot device For x86 and x64 systems see Configuring Boot Devices on page 59 For UEFI systems see Adding Boot Devices on page 164 Linux Citrix and VMware Configuring Boot from SAN on Linux Citrix or VMware x86 and x64 To configure boot from SAN 1 If necessary install or update the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information If necessary enable the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information Enable the adapter to boot from SAN See Enabling an Adapter to Boot from SAN on page 58 for more information If necessary enable spinup delay See Enabling or Disabling the Spinup Delay on page 69 for more information Configure boot devices See Configuring Boot Devices on page 59 for more information If desired configure the boot options on the adapter See Configuring Advanced Adapter Parameters on page 66 for more information Use the driver on the operating system distribution disk to boot the system If necessary you can update the driver to the latest version Configuring Boot from SAN on Linux UEFI To configure boot from SAN 1 If necessary install or update the latest boot code on the adapte
116. ded in an EFI Shell type drivers and press lt Enter gt to see if the driver is loaded Navigating the Emulex iSCSI Configuration Utility The Emulex iSCSI configuration utility has menus and configuration screens Use the following methods to navigate them e Press the up down arrows on your keyboard to navigate menu options or configuration fields When multiple adapters are listed use the up down arrows to scroll to the additional adapters e Press the lt gt lt gt or lt Enter gt keys to change numeric values e Press lt Enter gt to select an option e Press lt Esc gt to exit the current screen and show the previous screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A sc 11 Configuring UEFI for iSCSI 134 gt lt EMULEX Starting the Emulex iSCSI Configuration Utility Starting the Emulex iSCSI Configuration Utility Depending on the OEM UEFI configuration the Emulex iSCSI configuration utility may appear under different setup menus in the OEM system firmware or BIOS such as Storage To start the Emulex iSCSI configuration utility 1 Select the Emulex iSCSI Utility for a particular function and press lt Enter gt Storage Emulex iSCSI Utility 21 0 2 Port 0 Emulex iSCSI Utility 21 0 3 Bus 21 Devicet 0 Funct 2 Figure 11 1 Storage Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 135 gt lt EMU
117. ding firmware see Using the Emulex NIC Configuration Utility on page 103 Adding and Configuring Targets Discovering and Adding Boot Targets through DHCP To automatically discover and add boot targets through DHCP 1 9 On the Controller Properties screen Figure 11 4 set Discover Boot Target via DHCP to lt Enable gt and press lt Enter gt Select Save Changes and press lt Enter gt Reboot the system On the Controller Configuration menu Figure 11 2 select iSCSI Target Configuration and press lt Enter gt The iSCSI Target Configuration screen shows the discovered targets Note For more information on configuring a DHCP boot target refer to Discovering Targets through DHCP for iSCSI on page 99 iSCSI Target Configuration Select the Target to Add Target Edit the Configuration IP Address ign 1984 05 emulex tgt0 172 40 46 150 IP Version IPV4 TCP Port 3260 Boot Target No Connection Status Yes Figure 11 8 iSCSI Target Configuration Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX 11 Configuring UEFI for iSCSI Adding and Configuring Targets 142 Manually Adding Discovering and Managing Boot Targets To manually add and discover boot targets 1 On the Controller Properties screen Figure 11 4 set Discover Boot Target via DHCP to lt Disable gt and press lt Enter gt 2 Select Save Changes and press lt Enter gt 3 Reboot
118. dvanced Mode Support Advanced Mode is a driver compatibility option With Advanced Mode enabled you can run Advanced Mode aware drivers that provide advanced capabilities as listed in Table 2 1 With Advanced mode disabled you can run older legacy inbox drivers that are not Advanced Mode aware with the latest firmware versions Note Advanced Mode support is enabled by default on OCe11100 series 2 port and 4 port controllers On 4 port controllers the Advanced Mode setting is not provided in the PXESelect HII utilities The Advanced Mode setting on these platforms is implicitly enabled and Advanced Mode aware drivers must be installed Compatibility with legacy drivers requires that Advanced Mode support be disabled on 2 port controllers Note The Advanced Mode capability is not supported on OCe10100 series controllers Table 2 1 Advanced Mode Capabilities by Operating System Advanced Mode Disabled Operating System Advanced Mode Enabled Legacy Mode Windows 16 RSS queues 4 RSS Queues Note Only supported on Windows Server 2008 R2 and 2012 Remains four queues for earlier Windows versions VMQ lookahead split Lookahead split is silently ignored There may be a small performance Note VMQs are only supported on penalty for VMQS Windows 2008 R2 and later versions Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX 2 Configuring PXE Boot for the NIC Protocol 27 Using t
119. e Using SendTargets Discovery to Add an iSCSI Target on page 87 e iSCSI target IP address The IP address of the target into which you are logging e TCP port number The TCP port number of the target portal Typically this is 3260 which is the well known port number defined for use by iSCSI Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 87 SG EMULEX Adding iSCSI Targets Using SendTargets Discovery to Add an iSCSI Target SendTargets discovery asks an iSCSI target to provide the list of target names that can be logged into by the initiator The iSCSI initiator then uses the SendTargets Discovery option to perform the device discovery Use this method if an iSCSI node has a large number of targets When adding an iSCSI target leave the iSCSI target name option blank you can use the iSCSI SendTargets mechanism to add a target To configure an iSCSI target using the SendTargets discovery i 2s Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted Select Controller Configuration and press lt Enter gt A list of controllers is displayed Select a controller and press lt Enter gt The Controller Configuration menu is displayed ontroller Properties etwork Configuration SCSI Target Configuration ort Identification rase Configuration Figure 9 1 Controller Configuration Menu From the Controller Con
120. e specified boot servers steps 6 and 7 4 The PXE client executes the downloaded NBP steps 8 and 9 Note If any of these steps fail the boot process typically continues using the next available device in the boot sequence depending on the system configuration and boot order Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 22 gt lt EMULEX Remotely Installing with PXE for Windows Server 2008 2008 R2 and 2012 Remotely Installing with PXE for Windows Server 2008 2008 R2 and 2012 For remote installation with PXE a network driver for the Emulex adapter must be part of the client s installation image on the server The current versions of Windows Server 2008 and Windows Server 2008 R2 do not include network drivers for the Emulex adapter however Windows Server 2012 does include the network driver for the Emulex adapter To add the image and installation using the driver with the Remote Installation Service Setup select Start Menu gt Programs gt Administrative Tools Remote Installation Services Setup For more information refer to Microsoft Article ID Q246184 How to Add Third Party OEM Network Adapters to RIS Installations In addition to the network driver for the Emulex UCNA you must configure the following services to use PXE for remote installations e DHCP server e Remote Installation Services e Windows Deployment Services Microsof
121. e 10 19 Figure 10 20 Figure 10 21 Figure 10 22 Figure 10 23 Figure 10 24 Figure 10 25 Figure 11 1 Figure 11 2 Figure 11 3 Figure 11 4 Figure 11 5 Figure 11 6 Figure 11 7 Figure 11 8 Figure 11 9 Figure 11 10 Figure 11 11 Figure 11 12 Figure 11 13 Figure 11 14 Figure 11 15 Figure 11 16 Figure 11 17 Figure 11 18 Figure 11 19 Figure 11 20 Figure 11 21 Figure 11 22 Figure 11 23 Figure 11 24 Figure 12 1 Figure 12 2 Figure 12 3 Figure 12 4 Figure 12 5 Figure 12 6 Figure 12 7 Boot for NIC iSCSI List of Figures Configure Bandwidth Screen sciccss scree cas tiivensiees awieriecveveossvesesmerenes 120 Configure LPVID Screen ssssssssrsrrrerersssrrrrrrrerrrrrrrrrrrrrrrrrsrrsrrrrr 121 Multichannel Mode Dialog BOX n ss ssssuessssssrsrrrerrresrerrrrrrrrrrrerrsrrrrrrerere 122 IBM Virtual Fabric Mode Controller Configuration Screen ccecce 124 IBM Unified Fabric Protocol Mode Controller Configuration Screen 125 Switch Independent Mode Controller Configuration Screen eee eee 126 Port Management Screen ices ceistaceesnceddetbespecdtanaesaenelaciaemsedietemenacsens 127 Feature On Demand Screen ciciivsccasanstarenstedcivracassbiaiesuciasiueccasasieras 128 Erase Configuration SCreen acceca 130 St rage Serec siaopinie AEE EEEE EEA PEE EENE AEREA EEEE ATEEN IARA 134 Controller Configuration Menu Screen sssssssssresesesrrrrrrerrrrrrrrrrrrrrr 135 Controller Configuration Menu Screen with Boot
122. e 25 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 25 gt EMULEX Using the PXESelect Utility Note Changing the Personality setting requires a reboot before the change will take effect A reboot will occur when you exit the PXESelect utility if the Personality setting has changed since the last boot 2 Once you have set the options in the Controller Configuration menu select Save and press lt Enter gt 3 To proceed select Continue and press lt Enter gt The Port Selection Menu appears 4 Select the port you want to configure and press lt Enter gt Controller 0 Port 0 Bus 15 Dev 00 Controller 0 Port 1 Bus 15 Dev 00 Figure 2 4 Port Selection Menu Note The Port Selection Menu only appears if there are two or more ports connected Depending on your installed adapter and if Multichannel Mode is enabled proceed to the following sections e If Multichannel Mode is disabled or it is not supported refer to Configuring Ports When Multichannel is Disabled or Not Supported on page 28 for additional configuration information e If Multichannel Mode is enabled refer to Configuring Universal Multichannel on page 31 for additional configuration information e If Multichannel Mode is enabled and you are using IBM adapters refer to Configuring Multichannel for IBM Adapters on page 33 for additional configuration inform
123. e Emulex Redboot Initialization online or offline utilities If the error s persist contact Technical failed Support Firmware Load failed DDR config failed DDR callibrate failed DDR test failed SEEPROM checksum failed Secondary firmware image loaded You receive this POST error The firmware loaded on this UCNA is not supported Load the message appropriate firmware for the controller Firmware halted This firmware does not support this controller Troubleshooting for the FcoE Protocol Table 13 3 Troubleshooting the FCoE Protocol Issue Answer Solution Cisco Nexus switch configuration Ensure that the FCoE switch ports are configured correctly for the situations UCNA FCoE settings e Windows creates the NTFS partition properly but then reports that The hard disk containing the partition or free space you chose has a LUN greater than 0 Setup cannot continue Dell 1850 server Windows reboots successfully but then gets stuck during the GUI portion of the installation right from the beginning HP DL385G2 server Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix A Configuring iSCSI through a DHCP Server using Vendor Specific Option 43 gt lt EMULEX pp guring g g p ramets 185 Appendix A Configuring iSCSI through a DHCP Server using Vendor Specific Option 43 Overview An iSCSI initiator requires the following parameters to boot
124. e Maximum Bandwidth value is the greatest amount of bandwidth that the function can provide It is represented as a percentage 2 Enter the value for the specified option and press lt Enter gt 3 Select Save and press lt Enter gt Note To disable a function set the Minimum Bandwidth value to 0 Configuring LPVID The LPVID is used to enforce a VLAN ID on all traffic originating from an IP address channel or PCI function If the operating system for that PCI function has set up a VLAN ID then the operating system configured VLAN ID takes precedence over the LPVID for transmit packets while the operating system configured VLAN ID and LPVID tagged packets will both be received If the operating system has not set up any VLAN IDs then the LPVID is used for tagging Note LPVID and user configured VLAN IDs from the operating system must be different Note LPVIDs also need to be configured on the switch port Each LPVID must be unique and is relevant for NIC traffic only The LPVID is not supported for storage functions For iSCSI storage functions you must configure a Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 33 gt EMULEX Using the PXESelect Utility VLAN ID through iSCSISelect or through the host For additional information see Configuring VLAN ID and VLAN Priority on page 84 During PXE boot when the UNDI Driver BIOS is functional the
125. e iSCSI Initiator Name on all the controllers match If there were pre existing sessions before the iSCSI Initiator Name change the pre existing sessions use the original name that was used to login the very first time The new name is used for any sessions added after the name change 3 Select Save and press lt Enter gt to save the iSCSI initiator name If you select Controller Configuration without saving the changes a warning message will appear stating that your settings will be lost and asking whether you want to cancel or not Press lt Y gt and you will lose your changes Press lt N gt and you will return to the iSCSI Initiator Configuration screen Selecting a Controller After you configure an ISCSI initiator name select a controller to configure the iSCSI target If you are running the iSCSISelect utility with multiple controllers all the controllers are listed in the Controller Selection menu The OneConnect is a dual port chip therefore the Controller Selection menu always shows two controllers dual ports for each physical controller Figure 8 2 is an example of the Controller Selection menu showing two physical controllers with two controllers dual port each Controller Port 0 Bus 09 Dev 00 Controller Port 1 Bus 09 Dev 00 Controller Port 0 Bus 01 Dev 00 Controller Port 1 Bus 01 Dev 00 Figure 8 2 Controller Selection Menu After you select the controller the Controller Configuration menu appears From t
126. e only deleting the target session If you have logged out of a target you can perform a login To log out of a target from the iSCSI Target Configuration screen select the target and press lt F6 gt To log into a target from the iSCSI Target Configuration screen select the target and the disconnected target and then press lt F5 gt to establish the target session Booting the System After you have configured the iSCSI initiator and target you must reboot the system for the configurations to take effect When you exit the iSCSISelect utility the system automatically reboots and during system startup the OneConnect BIOS is displayed For example Controller 0 Port 0 Base OxFCE60000 at Bus 01 Dev 00 Fun 02 Controller 0 Port 1l Base OxFCEA0O000 at Bus 01 Dev 00 Fun 03 lt lt lt Press lt Ctrl gt lt S gt for iSCSISelect TM Utility gt gt gt Initiator iSCSI Name iqn 2004 05 com emulex Initiator IP Address 172 40 1 41 Initiator IP Address 172 40 1 62 BIOS Not Installed Note The iSCSI BIOS logs into the configured iSCSI boot target and shows its target LUN information in the BIOS sign on banner only if you have configured an iSCSI boot target For more information see Setting Up a Basic iSCSI Boot Configuration on page 77 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 98 gt EMULEX Managing an iSCSI Tar
127. ecesiec amddin ninkin Cenni ELaNA R ITAAS 34 PXE Boot Parameters Default ValueS ssssssssssnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnn 36 3 Configuring Boot from SAN for the FCoE Protocol cccccssccececcseeeeeeseeeenaeer 37 Windows Server 2008 and Windows Server 2012 ssssssssnssnssnnnnnnnnnnnnnnnnnnnnnnn 37 Configuring Boot from SAN on Windows x86 and X64 cccccee cece ee eeeeeeaeeeenees 37 Configuring Boot from SAN on Windows UEFI cccceecceeeceeeeeeeeeaeeesaeeeenaes 38 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DE EMULEX Table of Contents 4 Installing a New Windows Server 2008 or 2012 UEFI Aware Operating System on a UEFEDased x64 Server ic dincistxdiinnti cox cdilnteapenidaw secs cacaeracaeandancns 38 Directing a UEFl based Server to a Windows Server 2008 or 2012 Operating System Image Installed as UEFl Aware Already Installed on the SAN Goensuchaaeveascetsasseancaeaevesss ihsdemaccesessuteeastasseeencatatceoenseseaaetesseiesctvean 39 GUID Partition Table ssccccocvivsseariwrematierenterteaeinieerr aoa a r paia 39 Installing Windows Server 2008 or 2012 on an FC Boot Disk x86 x64 and VER iesca AEE EEEE Ana 40 Linux Citrix and VMware s ssassssssssnsnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 41 Configuring Boot from SAN on Linux Citrix or VMware x86 and x64 n e 41 Configuring Boot from SAN on Linux UEFI cccceeeeeeeceeeeeeee esate eeaneeeaneee
128. ed To start the Network Booting Tool from the desktop do one of the following e Go to the Main Menu Button on the Panel and select System Settings gt Server Settings gt Network Booting Service Or e Type the command system config netboot at a shell prompt For example in an XTerm or a GNOME terminal Note If you are starting the Network Booting Tool for the first time select Network Install from the First Time Druid Copy the files necessary to start the installation to the TFTP server 1 Select Configure gt Network Installation from the pull down menu wa Network Installation and Diskless Environment Bie Help Network Installation 6 Diskless elete Hostname Operating System IP Address Figure B 1 Network Installation and Diskless Environment Window Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DG EMULEX Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot 192 Linux and Citrix PXE Server Remote Installation Procedure 2 The Configure Network Installations window is displayed Click Add 3 Ei Configure Network Installations Emo x J Properties oD Q pelete OS Name Description i dp Add Ly i Figure B 2 Configure Network Installations Window The Network Installation Dialog window is displayed Network Installation Dialog of x Operating system identifier rhel5564 Description
129. eee e eee 109 Table 12 1 Adapter Default Vale vcs cscs casexccnes neds charesnbea shard tbackssanssladespmadedes 175 Table 13 1 PXE Error CodeS vcscerreccstigassepineciageetistasescetddamedetassiagisenadacacededasals 178 Table 13 2 Troubleshooting the iSCSISelect Utility eee eee eens 181 Table 13 3 Troubleshooting the FCoE Protocol eccceee eee eee cess teat eae eeee eae 184 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A XC EMULEX 1 Introduction 15 Overview 1 Introduction Overview This manual describes installing enabling and configuring boot code for Emulex network interface card NIC Internet Small Computer System Interface iSCSI and Fibre Channel over Ethernet FCoE universal converged network adapters UCNAs This manual also describes the Emulex boot from SAN implementation and its operation with distinct hardware and operating system requirements Boot from SAN is the process of booting a server directly from a disk operating system image located on a storage area network SAN by way of Emulex adapters using Emulex boot code When booting from SAN the storage device is typically identified by its world wide port name WWPN and a logical unit number LUN By extending the server system boot basic input output system BIOS boot from SAN functionality is provided by the boot BIOS contained on an Emulex adapter in the server When properly configured the adapter then permane
130. eeeeeeeeeeeeeeeeeeeeeeateeeteceteeeeennenaes 191 Copying Files to the TFTP Server with the Graphical Version of the Network Booting Tool viccosscciveccevernter veers tunestatastcuedecs toners seareenigsiarieuaiees 191 Configuring the HOSt cece eee teeter tee tee 193 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DE EMULEX Table of Contents Q Enabling the PXE Client with a PXE enabled Adapter c ccc eee eee e teeter eee es 195 Appendix C Example for Configuring and Booting UEFI NIC ccesceeeeeeeeeaas 196 UEFI NIC Server Configuration Script for SLES11 SPX cccscescseeeseeeeseeeeseeeesaeeees 196 NES Server Configuration Script ciisiscstertisevcrvedesnes eigciiesveretiressotasisanderes 197 DHCP Server Configuration iacrenneicsatacnnitecntetenicitescad inate cdeaduxisecaiadiaaedieka 198 TETP Server Set p cxictarencctect perc adeaed E E AA A E OAE 199 UEFI NIC Server Configuration Script for RHEL 6 X ssssssssunnnnnnnnnnnnnnannnnnnnnnan 199 Setup Information cicceunigi dat cixedddecisercndaaebaenspacaiiienantedi ates cbscaiasanuacadssas 199 NFS Configuratio s t2crstasntectettiennier ys ter iee o E AEO EEEE 199 TFTP Configuration 271 22 2e8 ower cicieisWascieenievexGicrd seve eid inure djeseesssasdoresieeess 200 PXE Configuration 222 c2nadyedatuaxtiscasiiuress cisiantegcatadurivecdsassntcscatneuriegadase 201 Configuring DHCP cave viavmdiinrbiammoeciestanveding aoar ia ai a
131. elect Utility ssssssssssrsrrrrrrrrrresrrrrrrererrrrrrrrrrrrerere 23 Running the PXESelect Utility 02 x atittaricancnedaskenteeiinceuenemed sea recanaaveseeundareds 23 Setting Up a PXE Bootable Network cccceecce cece e eee sent essen ee neeeenennenenn es 24 Personality OPN cessi iesit iraro nimitin e etree bier sere teaerernteaateres 25 Advanced Mode Support 2c ccccladocsxtecsain beedidentaesades SeleehageddwietaedelSeledeeeiavics 26 Configuring Ports When Multichannel is Disabled or Not Supported 0 05 28 Configuring PXE Boot Support 0 ccc een nee 28 Contouring SR IOV kerena enuiar a E EE ETETE IE E alo EEEE 29 Configuring the PXE VLAN ID and Priority ccccccc c 29 Physically Identifying the POrt cccccecce cece cnet eats eee eeee esse eset eeateseteeeeeenenae ens 30 Erasing Ports and Controller Configuration cccecceeceeceeeeeeeeeeeateseeeeeeeeene sates 30 Configuring Universal Multichannel cccccccee ects cece eee eeeeeeeeeeeeeeesanteeaneennaes 31 Configuring Minimum and Maximum Bandwidth cccseceeeeeeeeeeeeeeeeeeeeeeneesaes 32 Configuring LPVID vs accgsPeetescetsraet tenes aad Pd aed eal Senda ds R NEIRE EnEn daca peseabeia kaa de 32 Configuring Multichannel for IBM Adapters ccceccceeeeeeeeeeeeeeeeeeaeeeeaneennaes 33 Multichannel Modes nieren iinn nna oen seas dead Enr aes aE AEAEE e ai 34 Multichannel Contiguration iacesss tessa cma ane
132. ell gt driverdiag Drv 122 Ctr1 121 Drv 122 Ctr1 123 To run the standard diagnostic tests on function 0 Shell gt drvdiag s 122 121 To run the standard diagnostic tests on all NIC functions Shell gt drvdiag s 122 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 133 gt G EMULEX Overview 11 Configuring UEFI for iSCSI Note For systems with multiple adapters the UEFI system firmware or boot code uses the highest version driver installed on any of the adapters Adapters with older versions of EFIBoot are managed by the more recent version but only as long as the adapter with the most recent version is in the system The latest firmware and boot code must be installed on each adapter in the system to ensure that each adapter runs the latest firmware and boot code Overview UEFIBoot supports e EFI protocols Configuration and component name are supported e Operating systems Windows Server 2008 R2 Windows Server 2012 Red Hat Linux 6 and SLES 11 SP2 e Multi Device path SCSI device path is selectable through the driver configuration protocol e Multi initiators Up to 96 adapters in a system e Multi target 256 targets are selectable through the driver configuration protocol e Multi LUNs Up to 256 LUNs are supported e Multi utility Setup is supported This version of UEFIboot is loaded from flash into system memory When UEFIBoot is loa
133. ersonality setting will take effect Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 112 gt EMULEX Using the Emulex NIC Configuration Utility Configuring the Controller When Multichannel is Disabled or Not Supported Note If your adapter has Multichannel Mode enabled refer to Configuring Universal Multichannel on page 115 If you are using an IBM adapter refer to Configuring Multichannel for IBM Adapters on page 122 When Multichannel Mode is disabled or it is not supported the following Controller Configuration screen appears when you select Controller Configuration on the Emulex NIC Selection Screen Controller Configuration View Configuration View Current Configurations Configure SRIOU Save Current Configurations Tl Move Highlight lt Enter gt Select Entry Esc Exit Figure 10 10 Controller Configuration Screen The Controller Configuration screen enables you to perform the following tasks e View the current configuration e Configure SR IOV e Save the current configuration Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 113 gt lt EMULEX Using the Emulex NIC Configuration Utility Viewing the Configuration To view the current configuration 1 On the Controller Configuration screen select View Configuration and press lt Enter gt The View Configuration screen appears
134. eseeeeseeesaeeeas 133 Starting the Emulex iSCSI Configuration Utility ccccccsceessceeeseeeesceeesueeesaeeeas 134 Configuring Boot SUpport s ssssssssssnnnnnnnnunnnnnununnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 136 Configuring the Controller sssssssansnnnnnsnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 137 Config ring the NEIWOM Kissin sdiscesnasdadsseinancesssmnatqonasninarencsmmaneeneenneanetennnne 138 Automatically Assigning an IP Address through a DHCP Server sceeeeeeneeeees 138 Manually Assigning an IP Address ccvsecesevssvedactuecevsedwersntesdeceteaendduavecaeces 138 Configuring VLAN ID PIMOQICy cstcicxecstsscisaraciacedisbadinandGneastiacdsasantassadioadates 139 Updating Firmware sicssscccsstscsstsccscssestasestssestssesnssavaeccserseterestsisasscrseassacenes 141 Adding and Configuring Targets wsiivcicatacvenidcntncsnnicantdesmiidantecmnienntneceecaendanens 141 Discovering and Adding Boot Targets through DHCP s ssssssssisrrereersrrsrrrrrrere 141 Manually Adding Discovering and Managing Boot Targets eeeeeee eee 142 Setting a BOOE Target sxiccuntciewtaciacualetiatetiadwtesensedewieus neceleecesteetetauesaciend 143 Pinging a TAQCC er wevresk trans daursccnwetvaetineedvninstaawiveaiotecivelaiciecisres ioieedsecs 144 Viewing Advanced Properti S cccccccce cece cece eee e seen este eens eeeneteenetennaneeas 146 Logging In or Logging Out of a Target ccccscecteareichenctetercacateicuns meadtacan
135. etQueues PFs in non VFA 4 NetQueues PFs in VFA Boot for NIC iSCSI and FCoE Protocols User Manual 1500 MTU 8 NetQueues PFs in non VFA and 4 NetQueues PFs in VFA 9000 MTU 4 NetQueues PFs in both VFA and non VFA P009697 01A Rev A 10 Configuring UEFI for Ethernet 110 gt lt EMULEX Using the Emulex NIC Configuration Utility To enable Advanced Mode support 1 Onthe Emulex NIC Selection Screen select Advanced Mode and press lt Enter gt The Advanced Mode dialog box appears Emulex NIC Selection Emulex OneConnect 0Ce11102 IM 2 port PCIe 10GbE Enable Disable CNA Advanced Mode This Setting gets affected Firmware Version 4 6 152 0 for the other Port Bus Device Function 15 0 0 SYSTEM RESET REQUIRED Link Speed 10 Gbps Advanced Mode lt Enable gt Personality lt iSCSI gt Multichannel Mode lt Disable gt Controller Configuration Emulex Flash Update Utility Port Identification Erase Configuration Figure 10 8 Advanced Mode Dialog Box 2 Select Enable and press lt Enter gt 3 Reboot the system Note Changing the Advanced Mode setting requires a reboot Configuring Personality The personality reflects the protocol or protocols of the adapter This option specifies a list of available protocols that can be configured on an adapter Depending on the personalities for which the adapter is licensed one of the following selections appears e NIC e iSCSI e FCoE The NIC
136. etting the VLAN ID Value ccccce cece eee e eee eeeeeeee sees eeeeeeeeeaee sees satteneeeeneeneraaes 64 Enabling or Disabling VLAN ID ssssssssssssssssssrrrrrrrrrrt ttrt ttti ttr trr EE E EEEE EEEE EEEE 65 Setting the FC Map Bytes ccc cee een 65 Configuring Advanced Adapter ParameterS s ssssssssnussununnnnnnnnnnnnnnnnnnnnnnnnnnnnn 66 Changing the Default AL PA csvs2nesecathjacssecdssebeetcaanelxiiacaelzsantareastaixepsaaiseens 66 Changing the PLOGI Retry Timer sschisvstincsivdessouswecasiviavereineivetoonesdiasnietapenin 68 Enabling or Disabling the Spinup Delay 2 2csce scscsceeeesstenseeesetseetauersaeess 69 Setting UEC Sca yeas oe debe eonia S E A a EE EERS 70 Enabling or Disabling EDD 3 0yossisenscteieetwieieveiwedcitehatwencep teint cneseatwevadieess 71 Enabling or Disabling the Start Unit Command sssssssssssrsrrrereerrrrrrrrrrerrrre 71 Enabling or Disabling the Environment Variable sssssssssssrrrreereresrrrrrrerrrrere 72 Enabling or Disabling Auto Boot Sector sssssssrseereersrsrrrrrrerrererrrrrrrrerrere 73 Using Multi Path Boot from SAN ssssssssnnnnnnsnsnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 73 Resetting to Default Values sssssssssnnnnnnnnnnssnnnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 74 6 Installing Updating and Enabling Boot Code sssssssnnssnssunnnunnnnnnnnnnnnnn 76 7 Configuring iSCSI Boot Support with the iSCSISelect Utility ccecssseeeeeeeees 77 N
137. ettings are firmware UCNA parameters and are not altered when setting the BIOS boot parameters to their defaults Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 75 DG EMULEX Resetting to Default Values To reset parameters to their factory default settings 1 On the main configuration menu Figure 5 2 select Reset Adapter Defaults and press lt Enter gt A screen is displayed that asks if you want to reset to the defaults Bust 02 Deut 00 Func 03 Firmuare Version 2 702 485 1 BIOS Enabled Node Name 20000000C958 793 Figure 5 27 Reset Adapter Configuration to Defaults Screen 2 Press lt Y gt All settings revert to their factory default values 3 Press lt Esc gt to go to the previous menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX 6 Installing Updating and Enabling Boot Code 76 6 Installing Updating and Enabling Boot Code Emulex provides utilities to install update and enable boot code The utility that you use depends on the operating system and in some cases the driver type or system architecture Table 6 1 indicates the utilities that are currently available for each operating system Table 6 1 Utilities that Install Update and Enable Boot Code OneCommand Manager Operating System Application HBAcmd Utility Offline Utilities Windows v v Vv Li
138. figuration menu select iSCSI Target Configuration and press lt Enter gt Select Add New iSCSI Target and press lt Enter gt In the Add Ping iSCSI Target dialog box leave the iSCSI Target Name blank for a SendTargets response Note Only the first 64 sessions are returned during a single discovery session iSCSI Target Name IP Version IPv4 iSCSI Target IP Address TCP Port Number OneConnect Port 0 Boot Target ISID Qualifier Header Digest Data Digest Authentication Method Save Login Figure 9 2 Add Ping iSCSI Target dialog box Enter the iSCSI target IP address Change the TCP port number value if necessary The default target port number is 3260 For a boot target accept the default No even if you want to enable the target as a boot target For more information about the boot target see Setting Up a Basic iSCSI Boot Configuration on page 77 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 88 gt G EMULEX Adding iSCSI Targets 10 11 12 13 14 15 Note You must enable the Boot Target option after you add the target via SendTargets see step 16 Change the ISID qualifier value if necessary A unique ISID value is necessary if you connect dual sessions to the same target portal group Enter a number up to 65535 For more information see Setting an ISID Value on page
139. for RHEL 6 x Setup Information PXE client server Dell R710 with Emulex OneConnect UCNA or Intel X520 card Test System to do UEFI PXE boot PXE server HP running RHEL 5 5 64 bit NFS Configuration root orleans mkdir work mount 10 192 194 110 work mnt Mounting network drive root orleans cd mnt cp r rhel6364 work Copying rhel6 1 64 bit os to PXE root orleans root orleans server mechine root orleans vim etc exports HHHH Add work rw sync root orleans exportfs a HEH reflect changes in NFS Server HHH Restart NFS services root orleans etc rce d init d portmap restart root orleans etc re d init d nfslock restart root orleans etc rce d init d nfs restart Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 200 gt EMULEX UEFI NIC Server Configuration Script for RHEL 6 x Check if NFS is running fine root orleans rpcinfo p program vers proto port 100000 2 tcp 111 portmapper 100000 2 udp 111 portmapper 100021 1 udp 56782 nlockmgr 100021 3 udp 56782 nlockmgr 100021 4 udp 56782 nlockmgr 100021 alt tcp 44855 nlockmgr 100021 3 tcp 44855 nilockmgr 100021 4 tcp 44855 nlockmgr 100024 1 udp 766 status 100024 alt tcp 769 status 100011 1 udp 815 rquotad 100011 2 udp 815 rquotad 100011 1 tcp 818 rquotad 100011 2 tcp 818 rquotad 100003 2 udp 20
140. from SAN for the FCoE Protocol 40 gt lt EMULEX Installing Windows Server 2008 or 2012 on an FC Boot Disk x86 x64 and UEFI Note By default Microsoft Windows Server 2008 and 2012 installs with a GPT formatted disk on an UEFI Aware server For more information on the GUID partition table see the Microsoft website and search for the terms Windows and GPT FAQ Installing Windows Server 2008 or 2012 on an FC Boot Disk x86 x64 and UEFI This procedure installs Windows Server 2008 or 2012 onto an unformatted FC disk drive and configures the system to boot from the SAN disk drive Note The computer s system BIOS may require that another controller take precedence over the Emulex adapter during boot If this occurs you must disconnect or disable the other adapter This allows you to configure and build your operating system on the drive connected to the Emulex adapter To install Windows Server on an FC boot disk 1 From http www emulex com download the distribution executable file for the latest version of the Emulex driver to your local drive The file you download is an executable exe file 2 In Windows Explorer double click the distribution executable file Driver version information is displayed 3 Click Next to access the Location window The default installation location is displayed If desired browse to a different location 4 Click Install to continue the installation A progress window is displayed As each
141. g at the OBP prompt show devs The ID information for each found adapter is displayed such as pci 5d 700000 em1x 1 2 Select the Emulex adapter on which you want to enable boot from SAN by entering the path to the adapter for example pci 5d 700000 em1x 1 select dev 3 To view the current boot device ID type show devs pci 5d 700000 em1x 1 select dev to select emlx 1 for example boot id Make a note of the WWPN DID or AL_PA returned from the probe and write down the corresponding boot entry 4 To enable boot from SAN set the boot device ID to the SAN device from which you want to boot For example pci 5d 700000 em1x 1 select dev wwon did alpa lun target_id set boot id unselect dev where Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 46 gt G EMULEX Solaris 10 11 12 13 14 e wwpn did alpa is the device WWPN DID or AL_PA of the storage device e lunisthe LUN number in hexadecimal To enter it in decimal enter d lun e target_id is the target ID in hexadecimal To enter it in decimal enter d target_id Note Emulex recommends using the WWPN in most cases The DID and AL_PA may change between boots causing the SAN boot to fail unless the DID and AL_PA are specifically configured to not change between boots Example 1 alpa e1 lun 100 decimal and target id 10 decimal alpa el
142. gdeashisentveentiasaiiaanke 25 Controller Configuration Menu Personality Selection cceceeeee eee 26 Controller Configuration Menu Advanced Mode Support Selection 27 Port Configuration Screen sivivsivereeved icesdedveesvereskteeceudeiieessadaieieeteaanins 28 Configure PXE VLAN ID Priority MenU ssssssssisrrrereeerresrrrrrrrrrerrrrrrrrrne 29 Port Identification Screen 12 2 5 Aran chacoectnwckedncel enrecapaeamenee eceeteraaeeacnbenes 30 MultiChannel Configuration SCre n cccccecceceeee eee e settee eens neene nents renee es 31 Controller Configuration Screen IBM AdapterS c ceeeeee tenet ee eee ees 33 IBM Virtual Fabric Mode Configuration SCreen cccceee cece teen e ee ee teen eae 35 Emulex Adapter LISting i5cc5 lt sacsteaikeradddpacienecctwaitdeaded peddieanctenieisaaens eds 57 Main Configuration MENU cc i ncetacrcienaeatecns beewedantensettesteseematasiaapsoednies 58 BIOS StaCUGccisiteates hess tacens ceseisandscesetecaeexeiendecas A E DEESA 58 Devices Present on the Adapter cc cece cece e cece teat eee eeee tees eneenes 59 List of Saved Boot Devices SCree N ciicctsevitserd cnecetaevtiarsdcnantsaedetserscennes 60 Device Selection List Example Array Screen 0 ceeceeee cece eect eee teeta 60 LUN Listing SCEN antianedstuntcnnicimoruiisodecine aaa EEEa E E 61 Boot Device Selected asssscccatisceresasansiatesvarngiesecustaqiaremuelasiavedsssasierters 61 Boot Devices
143. get Erasing the Configuration Erase Configuration erases the configuration of a single controller Configuration data is erased for both ports on the selected controller The initiator name is global for all OneConnect controllers in the system If you have more than one controller and you erase the configuration on the first controller the Erase Configuration option resets the initiator name back to their default values If you erase the configuration on the second controller the default values are only reset for the second controller and are not reset globally on both controllers Note You must select Erase Configuration to clear out existing IQN data if you purchase a different or subsequent license for the adapter To erase a controller configuration 1 From the Controller Configuration menu select Erase Configuration and press lt Enter gt 2 A message appears asking if you want to erase the current configuration Type lt Y gt 3 You are cautioned that the operation removes any existing configuration permanently Type lt Y gt When the controller configuration is erased the Controller Configuration menu is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 99 gt lt EMULEX Discovering Targets through DHCP for iSCSI Discovering Targets through DHCP for iSCSI For your target to be discovered by the initiator t
144. get as a boot target select Boot Target and select Yes in the Boot Target drop down menu 3 You can set the ISID Qualifier on the Edit Ping iSCSI Target dialog box by selecting ISID Qualifier and typing a number value up to 65535 A unique ISID value is required if you are connecting dual sessions to the same target portal group For additional information see Setting an ISID Value on page 92 4 To enable the Header Digest select Yes in the Header Digest drop down menu When set to Yes and the iSCSI initiator is set accordingly the integrity of an iSCSI PDU s header segment is protected by CRC32C checksum The default setting is No 5 To enable the Data Digest select Yes in the Data Digest drop down menu When set to Yes and the iSCSI initiator is set accordingly the integrity of an isCSI PDU s data segment is protected by CRC32C checksum The default setting is No 6 To select an authentication method to use when logging into the target select an authentication method from the Authentication Method drop down menu For more information about authentication methods see Enabling CHAP Authentication on page 92 7 To verify your target connection select Ping and press lt Enter gt For more information about ping see Adding iSCSI Targets on page 86 8 To view more target properties select Advanced and press lt Enter gt For more information on these properties see Viewing Advanced Target Properties on
145. guration View Configuration View Current Configurations Configure SRIOU Figure 10 21 IBM Unified Fabric Protocol Mode Controller Configuration Screen 2 From the Controller Configuration screen you can perform the following tasks e View the current configuration of each function see Viewing the Configuration on page 118 for more information e Configure SR IOV see Viewing the Current SR IOV Configuration on page 119 Note SR IOV cannot be configured with multichannel enabled The Configure SRIOV option only displays the current SR IOV status which is disabled Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 126 DG EMULEX Using the Emulex NIC Configuration Utility Switch Independent Mode Multichannel Configuration To configure the multichannel configuration when the Multichannel Mode is set to Switch Independent Mode 1 On the Emulex NIC Selection screen select Controller Configuration and press lt Enter gt A list of available options is displayed Controller Configuration View Configuration View Current Configurations Configure SRIOU Configure Bandwidth Configure LPUID Save Current Configurations Figure 10 22 Switch Independent Mode Controller Configuration Screen 2 From the Controller Configuration screen you can perform the following tasks View the current configuration of each function see Viewing the Configurat
146. guration and press lt Enter gt A warning appears asking if you want to erase the configurations for both ports of the controller Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 130 gt lt EMULEX Using the Emulex NIC Configuration Utility Emulex NIC Selection Emulex OneConnect 0Ce11102 IM 2 port PCIe 10GbE Enter to Erase CNA Configuration Firmware Version 4 6 152 0 Bus Device Function 15 0 0 Link Speed 10 Gbps Advan Perso Multi Contr Emulex Flash Update Utility Port Identification Erase Configuration Figure 10 25 Erase Configuration Screen 2 Press lt Enter gt to delete the controller configuration or press lt Esc gt to abort the operation Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 13 SG EMULEX Using the Emulex NIC Configuration Utility UEFI NIC Diagnostics The UEFI NIC driver diagnostics protocol can be used to run diagnostic tests on each NIC function of the card This protocol is used by a platform management utility to allow you to run driver specific diagnostics on a controller EFI_DRIVER_DIAGNOSTICS_PROTOCOL Syntax drvdiag c 1 XXX s e m driverhandle devicehandle childhandle Description The UEFI NIC driver diagnostics protocol can be used to run diagnostic tests on each NIC function of the card Diagnostics can be run in standard m
147. he Emulex NIC driver in the previous example type unload 122 and press lt Enter gt 4 To unload the Emulex iSCSI driver in the previous example type unload 126 and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 213 xs Appendix E Loading and Unloading UEFIBoot from the UEFI Shell 214 gt EMULEX Unloading UEFIBoot from the UEFI Shell Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A
148. he PXESelect Utility Table 2 1 Advanced Mode Capabilities by Operating System Continued Operating System Linux and Citrix Advanced Mode Enabled 16 RSS Queues Advanced Mode Disabled Legacy Mode 4 RSS Queues VFs PFs can be increased up to 30 VMware ESXi For both 1500 and 9000 MTU 16 NetQueues PFs in non VFA 4 NetQueues PFs in VFA To configure Advanced Mode support 1500 MTU 8 NetQueues PFs in non VFA and 4 NetQueues PFs in VFA 9000 MTU 4 NetQueues PFs in both VFA and non VFA 1 From the Controller Configuration menu use the lt Tab gt key to select Advanced Mode Support and a drop down menu appears Mu 1ltiChannel Mode Advanced Mode Support Personality Enabled Disabled Figure 2 6 Controller Configuration Menu Advanced Mode Support Selection 2 Select Enabled or Disabled and press lt Enter gt 3 Select Save and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 28 DG EMULEX Using the PXESelect Utility Configuring Ports When Multichannel is Disabled or Not Supported Note If your adapter has multichannel enabled refer to Configuring Universal Multichannel on page 31 If you are using an IBM adapter refer to Configuring Multichannel for IBM Adapters on page 33 When Multichannel Mode is disabled or it is not supported the Port Configuration screen a
149. hed the first PCI scanned adapter is the boot adapter The first adapter is usually in the lowest PCI slot in the system Use the Boot Devices menu Figure 5 9 to configure up to eight boot entries for fabric point to point public loop or private loop configurations The first adapter is usually in the lowest PCI slot in the system This device is the only boot device and it is the only device exported to the multi boot menu Auto scan options e Autoscan disabled default e Any first device The first adapter issues a Name Server Inquiry and the first D_ID from the inquiry becomes the boot device The adapter attempts to log in to a public loop first If it fails it logs in to a private loop The first successfully scanned device becomes the boot device This device only is exported to the multi boot menu e First LUN 0 device e First NOT LUN 0 device a device other than LUN 0 To set auto scan 1 From the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed Figure 5 18 2 Select Auto Scan Setting and press lt Enter gt Figure 5 22 is displayed 01 0Ce10100 Bust 02 Deut 00 Func 02 Mem Base CE2C00090 Firmware Version 2 703 269 2 BIOS Enabled Port Name 10000000C9587595 Node Name 20000000C95B7595 Vlan ID 0001 DCBX mode CEE mode Autoscan disabled Default Figure 5 22 Set Auto Scan Menu Select the appropr
150. his menu you can configure and manage the iSCSI initiator and target s ontrol ler Propert ies etwork Configuration SCSI Target Configuration ort Identification rase Configuration Figure 8 3 Controller Configuration Menu If you are not sure that you are configuring the correct port you can check by either e Performing port identification For additional information see Identifying a Port on page 84 e Checking the link status in the Network Configuration menu Connect the controller port to a 10 Gb s switch port and check the link status in the Network Configuration menu If the status is Link Up it is the correct controller port Note Make sure you back out of the Network Configuration menu to the Controller Configuration menu before checking the Network Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility 82 Configuring Network Properties gt G EMULEX Configuration menu This allows the Link Status field to refresh when you insert or remove the cable from the controller Configuring Network Properties Use the Network Configuration menu to configure a network IP address for the controller The IP address is a logical address for the controller and uniquely identifies the system on a TCP IP network The IP address can be determined statically manually assigned or dynamically with the DHCP server to obtain an IP add
151. hrough DHCP you must add the root path to the DHCP server 1 From the DHCP server screen select Scope Options then right click and select Configure Options Bk actin wow Hep e am Bh ele DHE fa rx300 3 127 0 0 1 5 3 Scope 1 0 0 0 FSC DHCP i iE address Pool i QB Adcress Leases E E Reservations Scape Options 1 scope options VY Scopa optians are addtional canfigquration parameters that a DHCP sarvar tong to OHCP dierts For example some cammonty used optians inchide Corfioure Op c For defauk gateways routers WINS servers and DNS G8 Server Opicr new b gt bre override server options Refresh ns scape optiars onthe Action menu cick Configure Options oF Mare wFormetion about scope optiors see onine Help Corfiguee scope options Figure 9 13 DHCP Server Screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 100 DG EMULEX Discovering Targets through DHCP for iSCSI 2 From the General tab scroll down the list of available options and select 017 Root Path ieou I xix Fie Action W Gerea Advanced e Gi Avalable Options DHCP fh 3006301 E 29 Scop E Ad ad ft Gig Ae i tg Se PE ain Dato erty Sing vaus iecat010 010 010 001 0 2280 Rkion com ss tgtl O CISDNS Domain Name DNS Doma y O ME Swap Server Addiesz o c
152. iSCSI target configuration you have the option of setting dual network paths to a single boot LUN Note Although MPIO boot support allows the initiator to log into multiple sessions the iSCSI BIOS currently limits the number of sessions to two iSCSI sessions for a single boot LUN You must follow these steps in this order to configure MPIO boot support for each operating system 1 Use the iSCSISelect utility to configure the first path to a boot target 2 Complete normal operating system installation 3 Install third party MPIO software for your operating system 4 Configure the second path to a single boot LUN through the iSCSISelect utility Windows Server To install and configure MPIO on Windows Server 1 Log into the iSCSISelect utility by pressing lt Ctrl1 S gt when prompted 2 Use the iSCSISelect utility to log into a target from one adapter and configure it for boot by following the steps in Setting Up a Basic iSCSI Boot Configuration on page 77 If the iSCSISelect utility is configured properly a message during boot time indicates that the iSCSI disk was successfully connected Note Only one instance of the boot LUN must be visible to the server during the installation The installation might fail if multiple instances of the boot LUN are available to the server Emulex recommends that the Spanning Tree Protocol be disabled on any ports that are connected to Windows Server 2008 or 2012 hosts booting via iSCS
153. iate auto scan option Press lt Enter gt to accept the new scan option Press lt Esc gt to return to the advanced adapter configuration menu For changes to take effect reboot the system Sy OV ye Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 71 SG EMULEX Configuring Advanced Adapter Parameters Enabling or Disabling EDD 3 0 EDD 3 0 provides additional data to the operating system boot loader during an INT 13h function 48h call get device parameters This information includes the path to the boot device and the disk size The default setting for EDD 3 0 is disabled EDD 2 1 To enable or disable EDD 3 0 1 Oy gi gt From the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed Figure 5 18 Select Enable or Disable EDD 3 0 and press lt Enter gt The EDD 3 0 configuration screen is displayed 01 O0Ce10100 Bus 02 Devt 00 Funct 02 Mem Base CE2C0000 Firmware Version 2 703 269 2 BIOS Enabledt Port Name 10000000C95B7595 Node Name 20000000C9587595 Ulan ID 0001 DCBX mode CEE mode Enable Figure 5 23 Enable or Disable EDD 3 0 Screen Select whether to enable or disable EDD 3 0 Press lt Enter gt to accept the change Press lt Esc gt to return to the advanced adapter configuration menu For changes to t
154. ides the OneConnect IOCTL interface API for the UNDI driver The firmware and UEFI NIC iSCSI and FCoE drivers are contained in one image file with the UFI extension This file must be flashed through the NIC interface exposed by HII Viewing the Adapter s Firmware and Boot Code Version To view the adapter s firmware and boot code version 1 Start the Emulex NIC configuration utility via the HII Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 104 gt EMULEX Using the Emulex NIC Configuration Utility The Network screen shows a list of the adapters in the system Your list may vary depending on the installed adapters Network Global Network Settings Configure the network boot parameters iSCSI Configuration Network Device List MAC E4 1F 13 66 88 64 Onboard PFA 1 MAC E4 1F 13 66 88 66 Onboard PFA 1 MAC 00 00 C9 BC CE 40 Slot 1 PFA 21 0 0 MAC 00 00 C9 BC CE 44 Slot 1 PFA 21 0 1 1 0 1 0 0 1 Tl Move Highlight lt Enter gt Select Entry Esc Exit Figure 10 1 Emulex NIC Configuration Utility Network Screen 2 Locate the adapter Use the up down arrows on your keyboard to select it and press lt Enter gt The Emulex NIC Selection Screen appears Emulex NIC Selection Emulex NIC Model Number Firmware Version 4 6 152 0 Bus Device Function 15 0 0 Link Speed 10 Gbps Advanced Mode lt Enable gt Personality lt iSCSD Multichannel
155. ill receive another warning asking you to confirm the permanent removal of the controller configuration 3 Press lt Y gt to delete the configuration To exit the PXESelect utility after erasing the ports and controller configuration 1 Follow the instructions on the bottom of the individual menu screens until you are prompted to exit 2 Press lt Y gt to exit Depending on what settings were changed a reboot may be necessary Note For older systems depending on the memory allocation method supported the PXESelect utility automatically reboots even when there are no changes made to the system Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DG EMULEX Configuring Universal Multichannel 2 Configuring PXE Boot for the NIC Protocol 31 Using the PXESelect Utility Note Universal multichannel support is only available on Emulex OneConnect OCe11100 series UCNAs Note If your adapter has multichannel enabled and also supports IBM Virtual Fabric Mode or IBM Unified Fabric Protocol Mode refer to Configuring Multichannel for IBM Adapters on page 33 for additional information If multichannel is disabled or not supported on the adapter refer to Configuring Ports When Multichannel is Disabled or Not Supported on page 28 UMC provides the ability to configure multiple PCI functions or I O channels for each physical OneConnect port For additional information on UMC support see the Emulex Un
156. in requests and responses e Full Featured Phase Once security authentication has occurred and operational parameters have been set the initiator begins to perform SCSI I Os Security Because the iSCSI protocol operates in the Internet environment security is critical The iSCSI SAN uses the CHAP security method CHAP Authentication CHAP is used to periodically verify the identity of the initiator by the target using a challenge response mechanism The challenge response is established on the initial link and may repeated at any time afterward For CHAP to work the target must know the initiator s secret key and the initiator must correctly respond to the challenge Although the authentication is only one way you can negotiate CHAP in both directions for mutual authentication with the help of the same secret set Configuring for the iSCSI Protocol This section provides instructions for configuring boot from SAN for iSCSI on various operating systems using the iSCSISelect utility It also provides information on how to use the iSCS Select utility to perform an MPIO boot configuration Setting Up Boot from SAN for iSCSI In iSCSI target configuration you have the option of setting dual network paths to a single boot LUN You must follow these steps in this order to configure boot support successfully for each operating system 1 Use the iSCSISelect utility to configure a boot target Note iSCSI must be enabled for the port
157. in the network This address is required for communication to the iSCSI SAN For an initiator with its own network interface you must assign an IP address in the same range as the iSCSI SAN Enter the subnet mask The subnet mask provides a way to segment networks All hosts iSCSI initiators or targets on the same physical network usually have the same subnet mask For example Figure 8 6 shows the initiator in the subnet 255 255 xxx xxx All the hosts initiators or targets in a sub network will have the same subnet mask Enter the default gateway information if necessary A gateway is a router on a computer network that serves as an access point to another network and that an initiator uses by default Any data to addresses not on the initiator s subnet are sent through the default gateway Select Save and press lt Enter gt to save the settings Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 8 Configuring and Managing the iSCSI Initiator with the iSCS Select Utility 84 gt G EMULEX Configuring VLAN ID and VLAN Priority 6 You are prompted to save the changes type lt Y gt 7 Press lt Esc gt to return to the Network Configuration menu Configuring VLAN ID and VLAN Priority A Virtual Local Area Network VLAN is a way of partitioning the network If the LAN is made up of all devices within a broadcast domain a VLAN is a broadcast domain made up of switches You first create a VLAN and then assign po
158. ing is No 12 Select Yes from the Data Digest drop down menu if you want to enable Data Digest When set to Yes and the iSCSI initiator is set accordingly the integrity of an Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility Q0 gt EMULEX Managing an iSCSI Target iSCSI PDU s data segment is protected by CRC32C checksum The default setting is No 13 Select the Authentication Method For more information see Enabling CHAP Authentication on page 92 14 Select Save Login and press lt Enter gt If the firmware logs into the target successfully you receive a successful login message Press lt Esc gt to go to the iSCSI Target Configuration menu where you can view information about the added target 15 To enable Boot Target or make any other changes to your target or targets select the target and press lt Esc gt Managing an iSCSI Target With the iSCSISelect utility you can manage a target by viewing target details or by editing the target configuration Viewing Target Information After you have successfully logged into the target you can view the details of the newly added target or manage the target From the Controller Configuration menu select iSCSI Target Configuration and press lt Enter gt to view the target information Note The iSCSISelect utility only shows LUN information for the first 128 LUNs The f
159. ing PXE Boot for the NIC Protocol 20 E EMULEX ae 2 Configuring PXE Boot for the NIC Protocol This section describes using and configuring PXE to boot computers using a network interface independent of available data storage devices such as hard disks or installed operating systems The PXE protocol is a combination of DHCP and TFTP with subtle modifications to both DHCP locates the appropriate boot server or servers and TFTP downloads the initial bootstrap program and additional files Network booting enables you to perform the following tasks e Boot diskless systems such as thin clients and dedicated systems e Deploy software and operating systems for your systems e Automate system maintenance such as backups e Automate system checking such as virus scanning e Ensure a system is secure Pre OS PXE can be used in a pre OS environment Pre OS is the process of loading a small operating environment to perform a client management task before loading the final operating system from the local hard drive For example with a pre OS you can scan the hard drive for viruses This guarantees that the client is not infected before it starts The WDS uses this to install operating systems on local disks or BFS disks PXE Boot Process Once PXE Boot is enabled in the system UEFI BIOS the PXE client can boot up and start up the PXE boot ROM This is the boot code physically located on the NIC adapter Note To enable or disab
160. ink Down Disabled Figure 2 12 IBM Virtual Fabric Mode Configuration Screen Notes Logical Link Status is displayed as N A for storage functions SR IOV support can only be enabled if multichannel support is disabled If your system does not support some of the multichannel options those unavailable options show as N A on the MultiChannel Configuration screen The SVID or Outer VLAN ID is displayed in IBM Virtual Fabric Mode and IBM Unified Fabric Protocol Mode This value is provided by the IBM switch and will display when the protocol modes are configured on the switch and the adapter If the protocol modes are not configured a value of N A is displayed 2 From the configuration screen you can perform the following tasks Note Configure PXE boot support see Configuring PXE Boot Support on page 28 for instructions Configure PXE VLAN ID Priority see Configuring the PXE VLAN ID and Priority on page 29 for instructions Identify ports see Physically Identifying the Port on page 30 for instructions Erase the port and adapter configuration see Erasing Ports and Controller Configuration on page 30 for instructions Configure the LPVID for each channel see Configuring LPVID on page 32 for instructions Note An LPVID is optional for IBM Virtual Fabric Mode but it is required for every function when using Switch Independent Mode When IBM Virtual Fabric Mode or Unifie
161. ion on page 118 Configure SR IOV see Viewing the Current SR IOV Configuration on page 119 Note SR IOV cannot be configured with multichannel enabled The Configure SRIOV option only displays the current SR IOV status which is disabled Configure the minimum and maximum bandwidth percentage see Configuring Minimum and Maximum Bandwidth on page 120 Configure the LPVID per function see Configuring the LPVID on page 121 Note An LPVID is required for every function when using Switch Independent Mode but it is optional for IBM Virtual Fabric Mode and IBM Unified Fabric Protocol Mode Save the current configuration see Saving the Current Configuration on page 122 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 127 gt lt EMULEX Using the Emulex NIC Configuration Utility Port Management Note The Port Management functionality is only available on IBM NIC adapters and the configuration menu is only available on port 0 The Port Management option is used to enable or disable the physical ports When port 0 is disabled it brings down the physical link for port 0 and the power consumption of the adapter is lowered however the PCI functions associated with that port must remain enabled When any other port is disabled all of the corresponding functions associated with that port are disabled and removed from the PCI configuration sp
162. ion with adjacent switches To enable multichannel support 1 On the Emulex NIC Selection screen select Multichannel Mode and press lt Enter gt The Multichannel Mode dialog box appears Emulex NIC Selection Emulex OneComect 0Ce11100 Multichannel Configuration Use of Firmware Version 4 6 145 0 IBM Virtual Fabric Bus Device Function 16 0 0 Mode or IBM Unified Link Speed ic Protocol Mode Personality de ode ires the switch to Multichannel Mode support the Controller Configura tionality Port Management Disable EM RESET REQUIRED Feature On Demand Emulex Flash Update Utility Port Identification Erase Configuration Figure 10 19 Multichannel Mode Dialog Box 2 Select one of the following settings and press lt Enter gt e Switch Independent Mode e IBM Virtual Fabric Mode e IBM Unified Fabric Protocol Mode Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 123 gt EMULEX Using the Emulex NIC Configuration Utility e Disabled Note For more information on the available Multichannel Modes see Multichannel Modes With the Multichannel Mode selected you can now configure multichannel support See Multichannel Configuration on page 123 for more information Multichannel Modes Note The following modes are only available on certain adapters and systems that support IBM Virtual Fabric and Unified Fabric Protocol modes An IBM Virtual
163. isable VLAN ID Screen 2 Use the up and down arrows to highlight an option then press lt Enter gt to select it 3 Press lt Esc gt to return to the CIN configuration menu Setting the FC Map Bytes To set the FC map bytes 1 Select Set the FC Map Bytes from the CIN configuration menu and press lt Enter gt The following screen is displayed 01 0Ce10100 Bus 02 Devit 00 Func 02 Mem Base CE2C0000 Firmware Version 2 703 269 2 BIOS Enabledt Port Name 10000000C95B7595 Node Name 20000000C9587595 Ulan ID 0001 DCBX mode CEE mode Edit The FCF Map Byte Values only byte 2 is user editable FCF Map Bytes OE 1 FC 2 30 Figure 5 17 Set FCF Wrap Byte Screen 2 Enter the bit value that completes the fabric provided MAC address Use the up and down arrow keys to change the value at the cursor and the left and right arrow keys to move the cursor 3 Press lt Enter gt to save and return to the CIN configuration menu 4 Press lt Esc gt to exit this screen without saving Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 66 DG EMULEX Configuring Advanced Adapter Parameters Configuring Advanced Adapter Parameters The BIOS utility has numerous options that can be modified to provide different behavior Use the BIOS utility to perform the following tasks e Change the default AL_PA of the adapter e Change the PLOGI
164. isting Logged in Values Enter VLAN ID 2 Commit changes and Enter FC BYTE 2 Value 0 Reboot to make changes set VLAN Valid lt TRUE gt Effective on Next Boor Discard Changes ommit Changes Figure 12 8 CIN FCF Record Information 4 Change the record information as needed e VLAN ID Enter the VLAN on which the adapter FCoE services are available This must be a 3 digit hexadecimal number e FC Byte 2 Enter the bit value that completes the fabric provided MAC ADDRESS Value can be incremented or decremented with the lt gt and lt gt keys FC BYTE 0 and 1 are predefined unchangeable to OE FC and only the second byte is selectable e Set VLAN Valid Select TRUE to enable VLAN or FALSE to disable it 5 Select Commit Changes and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 164 gt EMULEX Scanning for Fibre Devices Scanning for Fibre Devices When LUNs are set up on the SAN before POST has completed that is before the boot driver has been started you can select Scan for Fibre Devices or Add Boot Device to discover all available LUNs Although this procedure does not perform a complete HBA initialization it executes faster than selecting Reconnect Devices Note If you dynamically add LUNs after POST has completed and the driver has been started you must select Reconnect Devices to perform a complete HBA initia
165. ith the GPT disk partition See GUID Partition Table on page 39 for a brief description of GPT disk partitions After the installation is complete a boot option variable called Windows Boot Manager is populated with a media device path pointing to the Windows boot Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 39 gt G EMULEX Windows Server 2008 and Windows Server 2012 loader utility Windows Boot Manager can be found in the Start Options menu of the Host Server UEFI The Windows Boot Manager option is inserted as the first boot option in the boot order list of the Host Server UEFI The CD DVD boot is the second device in the boot order list 10 Upon reboot the system boots from the LUN set up on the SAN Directing a UEFl based Server to a Windows Server 2008 or 2012 Operating System Image Installed as UEFI Aware Already Installed on the SAN This installation procedure assumes a LUN exists in the SAN storage device is zoned appropriately to the host adapter s WWN and a UEFI aware operating system resides on the target LUN To direct a UEFI based server to a Windows Server operating system image 1 2 Enable network boot in the Emulex UEFI configuration utility Configure the boot target and LUN in the Emulex UEFI configuration utility to point to your desired target Select Boot Manager from the System UEFI configuration manager Se
166. ity Physically Identifying the Port To physically determine which port you are configuring by blinking the link and activity LEDs of that port 1 On the configuration screen select Port Identification and press lt Enter gt The Port Identification screen appears The link and activity LEDs on Controller 0 Port 0 are blinking in unison Upon exit from this screen the LEDs will return to normal operation Done Figure 2 9 Port Identification Screen 2 The LEDs on your controller begin blinking The selected port s LED status indicators blink on your controller until you select Done on this screen and press lt Enter gt Note Not all controllers have LEDs that are visible externally If you are using an add in card in a blade server environment the port identification or beaconing capability does not work Erasing Ports and Controller Configuration Note When selecting this setting all previous configuration settings are returned to their factory default settings except for the current personality selection Emulex recommends performing this action to provide a clean environment for new configuration settings to take effect To erase the ports and controller configuration 1 On the configuration screen select Erase Configuration and press lt Enter gt A warning appears asking if you want to erase the current configuration for all ports of the controller 2 Press lt Y gt to delete the configuration You w
167. iversal Multichannel Reference Guide Note When UMC is enabled you must configure the multichannel settings minimum and maximum bandwidths for iSCSI and FCoE storage functions in the NIC BIOS before they can be configured further from their respective utilities iSCSI or FCoE BIOS Otherwise the Logical Link for that function will still show as down and you will not be able to log into targets or find LUNs behind those targets Note Multichannel functionality is only supported on OneConnect controllers running in 10 Gb mode The 1 Gb mode does not support UMC To view the MultiChannel Configuration screen 1 From Port Selection Menu Figure 2 4 select the port you want to configure and press lt Enter gt The MultiChannel Configuration screen appears Controller 0 Port 0 Bus 15 Dev 00 Firmware Version v4 6 145 0 Port Speed 10 Gbps Physical Link Status Link Up PXE Boot Support Enabled Type Bandwidth LPVID MA Disabled 1 1007 2 4094 Addr Min Max NIC z 00 00 c9 bc ce 40 iSCSI N ZA 00 00 c9 bc ce 41 NIC 1007 00 00 c9 bc ce 42 NIC 00 00 c9 bc ce 43 Figure 2 10 MultiChannel Configuration Screen Notes ogical Link Status Link Up N A Link Up Link Up SR IOU Disabled Disabled Disabled Disabled e Logical Link Status is displayed as N A for storage functions e SR IOV support can only be enabled if UMC support is disabled Boot for NIC iSCSI and FCoE Protocols User Man
168. lations in the Solaris 10 10 09 Installation Guide 2 Obtain the MAC address of the OCE port used for the net boot a Get the device path of the port from the show devs command Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX 0 ok show devs 3 Configuring Boot from SAN for the FCoE Protocol Solaris 48 pci 0 pci 0 pci 8 pci 0 pci 1 em1x 0 3 pci 0 pci 0 pci s pci 0 pci 1 em1x 0 2 pci 0 pci 0 pci 8s8 pci 0 pci 1 oce 0 1 pci 0 pci 0 pci s pci 0 pci 1 oce 0 pci 0 pci 0 pci s pci 0 pci 1 em1x 0 3 fpe 0 0 b Select the OCE device to boot 0 ok pci 0 pci 0 pci 8 pci 0 pci l1 oce 0 1 select dev c Get the MAC address of the selected device from its properties 0 ok properties status assigned addresses model fcode version reg compatible max frame size address bits supported network types copyright reserved name device type manufacturer fcode rom offset interrupts cache line size class code subsystem id subsystem vendor id revision id device id vendor id okay 82020014 82020018 82020020 82020030 O0Ce10102 4 0 0 0 00020000 02020014 03020018 03020020 00000000 00000000 02020030 00000000 00000000 pciex19a2 700 10df e602 2 pciex19a2 700 10df e602 pciex19a2 700 2 00000000 00000000 00000000 00000000 00100000 00120000 00140000 00180000 00000000 00000000 00000000 00000000 00004000 00020000 00020000 00080000 00000000 0000
169. le Check the TFTP server s file permissions PXE E3F TFTP packet size is invalid TFTP packet received is larger than 1456 bytes Check the MTU on the Server side NIC interface Boot DHCP Error Codes PXE E51 No DHCP or Proxy DHCP offers were received The client did not receive any valid DHCP BOOTP or Proxy DHCP offers Check that the bootfile name is configured correctly for PXE Clients in the DHCP setup PXE E52 Proxy DHCP offers were received No DHCP offers were received The client did receive at least one valid proxyDHCP offer but did not receive any valid DHCP or BOOTP offers Check that the DHCP server and PXE server are configured properly PXE E53 No boot filename received The client did receive a valid BOOTP DHCP offer but does not have a boot file name to download in the DHCP offer Boot for NIC iSCSI and FCoE Protocols User Manual Check that the bootfile name is configured correctly for PXEClients in the DHCP setup P009697 01A Rev A gt EMULEX Table 13 1 PXE Error Codes Continued 13 Troubleshooting 180 Troubleshooting for the NIC Protocol Error Codes PXE E55 Proxy DHCP service did not reply to request on port 4011 Possible Reason The client issued a proxyDHCP request to the DHCP server on port 4011 but did not receive a reply Comment Solution Check that the DHCP server and TFTP server are properly configu
170. le PXE Boot it must be enabled or disabled in the system UEFI BIOS see the documentation that accompanied the server for more information Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 21 DG EMULEX PXE Boot Process DHCP Discover to Port 67 P Contains PXEClient extension tags Extended DHCP Offer to port 68 contains PXE server extension tags Other DHCP option tags Step2 __ Client IP addr bees DHCP Request to Installation Server port 67 Contains PXEClient extension tags Other DHCP option tags DHCP Ack reply to Port 68 Boot Service Discover to port 67 or 4011 Contains PXEClient extension tags Other DHCP optio T9 Step6 a Boot Service Ack reply to client source port Step7 Contains PXE Server extension tags contains Network Bootstrap Pr Network Bootstrap Program download request to TFTP port 69 from Boot Service Ack Client execu tesi NEP Network Bootstrap Program Download to Client s port Figure 2 1 PXE Boot Process Figure 2 1 shows the boot process 1 The PXE boot ROM sends a DHCP request extended with PXE specific options step 1 in the figure 2 The DHCP responses contain the DHCP options DHCPOFFERs that include the NBP filename and boot server lists steps 2 through 5 3 The PXE client attempts to download the specified NBP over TFTP from one of th
171. le gt Controller Configuration Emulex Flash Update Utility Port Identification Erase Configuration Figure 10 13 Multichannel Mode 2 Select Enable to activate multichannel support and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 117 gt lt EMULEX Using the Emulex NIC Configuration Utility To configure the multichannel configuration 1 On the Emulex NIC Selection screen select Controller Configuration and press lt Enter gt A list of available options is displayed Controller Configuration View Configuration View Current Configurations Configure SRIOU Configure Bandwidth Configure LPVID Save Current Configurations Figure 10 14 Controller Configuration Screen From the Controller Configuration screen you can view the current configuration of each function configure SR IOV configure the minimum and maximum bandwidth percentage configure the LPVID per function and save the current configuration Note SR IOV cannot be configured with multichannel enabled The Configure SRIOV option only displays the current SR IOV status which is disabled Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 118 gt lt EMULEX Using the Emulex NIC Configuration Utility Viewing the Configuration To view the current multichannel configuration 1 On the Controller Configurati
172. lect Add Boot Option Identify the desired target in the list and continue down the explorer path until you locate the bootmgfw efi file This file is the boot loader utility for your Windows 2008 or 2012 UEFI aware operating system installation Input a boot device description for example Win2K8_UEFI_SAN and optional data if desired for this device and select Commit Changes From the Windows Boot Manager select Change Boot Order Move your previous input description name Win2K8_UEFI_SAN to the desired position in the boot order Select Commit Changes The Start Options list now reflects the boot order changes Upon reboot the server is able to boot from this target LUN on the SAN GUID Partition Table The GPT was introduced as part of the EFI initiative GPT provides a more flexible mechanism for partitioning disks than the older MBR partitioning scheme that has been common to PCs MBR supports four primary partitions per hard drive and a maximum partition size of 2 TB If the disk is larger than 2 TB the maximum partition size in a legacy MBR the size of this partition is marked as 2 TB and the rest of the disk is ignored The GPT disk itself can support a volume up to 264 blocks in length for 512 byte blocks this is 9 44 ZB A zettabyte is 1 billion terabytes The GPT disk can also theoretically support unlimited partitions Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot
173. list and set all boot device WWNNs back to 0 along with setting the adapter back to the default values These default values are listed in Table 12 1 Table 12 1 Adapter Default Values Parameter Default Value Enable Disable BIOS Disabled Valid Values Enabled Disabled PLOGI Retry Timer Disabled Disabled 50 msec 100 msec 200 msec Boot Target Scan Boot path from NVRAM targets Boot path from NVRAM targets Boot path discovered targets Do not create boot path Maximum LUNs Setting 0256 0 4096 Delay Device Discovery 0000 0000 0255 Advanced Mode Enabled 0Ce11100 series 4 port Enabled controllers Disabled Disabled 0Ce11100 series 2 port and 0Ce10100 series controllers PXE Boot Support The default for this parameter varies Enabled depending on the vendor Disabled configuration SR IOV Disabled Enabled Disabled VLAN Support Disabled Enabled Disabled VLAN ID 0 0 4094 VLAN Priority 0 0 7 Multichannel Support The default for this parameter varies Enabled depending on the vendor Disabled configuration Function En Dis Disabled Enabled Disabled Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX 12 Configuring UEFI for FCoE 176 Resetting Emulex Adapters to Default Values Table 12 1 Adapter Default Values Continued Parameter Default Value Valid Values Bandwidth 0 Must have a total of 100 acros
174. lization and discovery If this step is not performed all LUNs may not be properly discovered You should also select Reconnect Devices after adding any discovered LUNs to the NVRAM list To scan for Fibre devices 1 From the Device Manager screen Figure 12 2 select the adapter that you want to scan for Fibre devices and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu select Scan for Fibre Devices and press lt Enter gt A list of discovered targets is displayed This is only a list of discovered target devices to quickly determine SAN connectivity and provide you with a mechanism to have the port logged in for zoning Adding Boot Devices To add a boot device 1 From the Device Manager screen Figure 12 2 select the adapter to which you want to add a boot device and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A sc 12 Configuring UEFI for FCoE 165 gt G EMULEX Adding Boot Devices 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Add Boot Device and press lt Enter gt Discovered targets are displayed 0Ce10102 FM Node Name 20000000C95387857 WWN 21000020 37E16C1E ere are the discovered targets Port ID 0100DC Configuration Main Menu SEAGATE ST3184S1FC SEAGATE ST318451FC SEAGATE ST318451FC SEAGATE ST318451FC SEAGATE ST318451FC Figure 12 9 SAN Discovery Targets List 3 Select a target and press lt Enter gt
175. ls User Manual the Option ROM is enabled and is set for the PCle slot into which the OneConnect adapter is inserted e If the Option ROM is enabled and is set for the PCle slot into which the OneConnect adapter is inserted and the issue persists erase the Controller Configuration For more information see Erasing the Configuration on page 98 P009697 01A Rev A o 13 Troubleshooting 182 gt EMULEX Troubleshooting for the iSCSI Protocol Table 13 2 Troubleshooting the iSCSISelect Utility Continued Issue Answer Solution Unable to ping iSCSI target IP e Check cable connections and make sure they are securely address connected at both ends Make sure the link light is ON at both ends of the cable e Verify that you have assigned a valid IP address with the correct subnet mask to the interface s that are connected to the network Check for duplicate IP addresses e Make sure you are connected to the correct port e If the IP address is coming from DHCP check that the DHCP server is up and available e lIsthe target ona different subnet Check the default gateway and make sure that the IP addresses of both the default gateway and the remote host are correct e Check link status under Network Configuration If you try changing the initiator link status you can back out one screen then go back to Network Configuration to see a view of your current link status Login to iSCSI target fails or login e Check initiat
176. m BIOS setting e Check the system BIOS for boot device priority order Make sure that the boot device is at the top If using DHCP lf Boot Support is not enabled enable it on the iSCSI Initiator menu For more information see chapter 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility on page 80 If DHCP boot support is enabled check the DHCP setup and also verify that you have added the root path to the DHCP server For more information see Setting Up a Basic iSCSI Boot Configuration on page 77 e If this checklist confirms that the initiator and target are configured correctly and the issue persists erase the Controller Configuration For more information see Erasing the Configuration on page 98 BIOS post shows BIOS Not Installed If you have not configured an iSCSI boot target this is proper message normal behavior e If you have configured an iSCSI boot target and the BIOS cannot find a bootable LUN then refer to the solutions provided in the issue Unable to boot from the iSCSI target If solutions for issues 1 3 and 5 6 all Use the iSCSISelect utility to erase the controller configuration fail To clear controller configuration 1 From the Controller Configuration menu select Erase Configuration and press lt Enter gt 2 A message appears asking if you want to erase the current configuration Press lt Y gt 3 You are cautioned that the operatio
177. map bytes Figure 5 14 CIN Configuration Menu Setting the VLAN ID Value To set the VLAN ID value 1 Select Set the VLAN ID from the CIN configuration menu and press lt Enter gt The following screen is displayed 01 0Ce10100 Bust 02 Devitt 00 Funct 02 Mem Base CEZC0000 Firmware Version 2 703 269 2 BIOS Enabled Port Name 10000000C95B7595 Node Name 20000000C95B7595 Vlan ID 0001 DCBX mode CEE mode The current VLAN ID is 0001 Input new VLAN ID 0 4095 3001 Figure 5 15 FCF CIN VLAN ID 2 Enter the VLAN on which the adapter FCoE services are available Use the up and down arrow keys to change the value at the cursor and the left and right arrow keys to move the cursor 3 Press lt Enter gt to save and return to the CIN configuration menu Press lt Esc gt to exit this screen without saving Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 65 gt C EMULEX Configuring DCBX Mode Enabling or Disabling VLAN ID To enable or disable VLAN ID 1 Select Enable Disable VLAN ID from the CIN configuration menu The following screen is displayed 01 0Ce10100 Bus 02 Devt 00 Func 02 Hem Base CE2C0000 Firmware Version 2 703 269 2 BIOS Enabledt Port Name 10000000C9587595 Node Name 20000000C9587595 Ulan ID 0001 DCBX mode CEE mode The current VLAN ID is Enabled Enable Disable Figure 5 16 Enable or D
178. metry 105 3FFF BIOS Installed Successfully Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility 80 gt EMULEX Configuring the iSCSI Initiator Name 8 Configuring and Managing the iSCSI Initiator with the 1SCSIiSelect Utility The iSCSI initiator or host also known as the iSCSI client is a system such as a server which attaches to an IP network and initiates requests and receives responses from an iSCSI target Each iSCSI host is identified by a unique ION Once you have an initiator host system running you must configure the initiator to allow access to the iSCSI SAN To do this you must 1 Configure the iSCSI initiator name 2 Select a controller For additional information see Selecting a Controller on page 81 3 Configure network properties For additional information see Configuring Network Properties on page 82 4 Verify network settings For additional information see Confirming Network Settings on page 85 Configuring the iSCSI Initiator Name The iSCSI initiator name is a unique identifier for the initiator on the network and configures target access It must be unique to that system on the network and is identified by an ION The iSCSI initiator name is global to the entire system The iSCSI initiator name must also match the target s ACL After you log into the iSCSISelect utility you can config
179. n A A EEE EE EENET RR qian 52 Linuxand Citrix SQrvenS vscdsecatancwionveseaaleaniaeestdetraraaieda nian adied aaah i 52 ESXi SORVGER rrea ane ais aun A EAE danee winnaar ESAERA 52 Booting from SAN for iSCSI MPIO icciccsecsnsttecevedearicceetseslaadavarwiteccasicasateanss 53 Windows Server sisiiseriisinecn siaa Sakanan niena Ee EEEa EEE EANET sends EARE 53 LINUX and Citrix Server Sisirain aion ena ae EE ERTE AEAEE KEEA 54 ESXi 5 0 0r 5 1 Sener urinmani r E E AE A NTA 55 5 Using the FCoE Boot BIOS Utility for x86 and x64 ArchitectureS ssssssssssssa 57 Navigating the FCoE BIOS Utility ccccccccccceeccceeesceeeseeeesueeesueeesueeeaueeeaueeeagee 57 Starting the FCoE BIOS Ute y sccinsiindsninseninsenrmgenaventminddataarenamiateaieaninenianaaat 57 Enabling an Adapter to Boot from SAN sssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 58 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DE EMULEX Table of Contents 5 Scanning for Target Devices 1ccccsccsdccesccscssrcenssdessanesaacceacscasasersacensseseerasenaei 59 Configuring Boot DEVICES ssssssssnsnnnnnnnnnnnnnnnnnuunnnnnuunnnnnnnnnnnnnnnnnnnnnnnnnnnna 59 Configuring DCBX Mode iisisiisirssrisrisarrsririsrironrorni tirrr nids Annn Earr SA Er reini in enia 62 Configuring CEE Parameters sssssssrsrrerrerestsrrrrrrrrrrtnrt rrr rrrrrrrrtrrrrrrrrrrrnt 63 Configuring CIN Parameters vcr veaswdrecidiaws beeviieads Maviveaate eens yinairoeeunandeeds 64 S
180. n iSCSI Target 5 Select Add New iSCSI Target and press lt Enter gt 6 Follow steps 5 11 in the procedure Using SendTargets Discovery to Add an iSCSI Target on page 87 7 Inthe Add Ping iSCSI Target dialog box select Authentication Method select One Way Chap and press lt Enter gt Target CHAP Name Target Secret Figure 9 7 One way Chap Configuration Dialog Box 8 Enter the target CHAP name and target secret then select OK and press lt Enter gt The target CHAP name can be any name or sequence of numbers over 12 and less than 16 characters However the name and secret on the target side must match the name and target on the initiator side The target secret can be in string for example abcdefg23456 or hexadecimal for example 0x01234567890123456789A BCD format e Ifusing a string format the secret can be any name or sequence of numbers over 12 and less than 16 bytes long where each character equals one byte e If using a hexadecimal format the secret must be at least 12 and less than 16 bytes long where two characters equal one byte Hexadecimal formatting restrictions o The Ox representation requires an even number of hexadecimal values excluding the Ox 0 9 A F For example the secret 0x1234567890123456789ABCD is not allowed because the character length is odd with 23 hexadecimal values excluding the 0x The secret 0x01234567890123456789ABCD is allowed with 24 hexadecimal values excluding the Ox
181. n is refreshed with the modified value Note Press lt Esc gt to return to the EFI utility menu Select Commit Changes and press lt Enter gt The Emulex Adapter Configuration Main Menu is displayed Changing the Maximum LUNs per Target The maximum number of LUNs represents the maximum number of LUNs that are polled during device discovery The minimum value is 1 the maximum value is 4096 The default is 256 To change the maximum number of LUNs 1 2 Boot for NIC iSCSI and FCoE Protocols User Manual From the Device Manager screen Figure 12 2 select the adapter whose LUNs per target information you want to change and press lt Enter gt From the Emulex Adapter Configuration Main Menu Figure 12 3 select Configure HBA Parameters and press lt Enter gt The Configure HBA Parameters screen is displayed 12 Configuring UEFI for FCoE 171 P009697 01A Rev A 12 Configuring UEFI for FCoE 172 gt lt EMULEX Configuring Adapter Parameters 3 From the Configure HBA Parameters screen select Maximum LUNs Target and press lt Enter gt 0Ce10102 FM Node Name 20000000C95587557 Maximum Luns Target onfigure HBA Parameters Discard Changes ommit Changes opology Selection lt AUTO Loop First default gt PLOGI Retry Timer lt Disable Default gt Force Link Speed lt Auto negotiate Defauit gt onfigure Boot Parameters aximum Luns Target 256 Boot Target Scan Method lt Boot Path Discovered
182. n removes any existing configuration permanently Press lt Y gt Note If you have multiple controllers you must erase the configuration of each controller separately For more information see Erasing the Configuration on page 98 After you erase the controller configuration reboot the system and then reconfigure the OneConnect adapter You receive this POST error In the iSCSI BIOS the iSCSI initiator name may be different if message there is more than one OneConnect controller in the system If Initiator iSCSI Name the iSCSI initiator name is different on multiple controllers you mismatch Please use receive a POST error message indicating an iSCSI name mismatch iscsISelect to set a single You must enter the iSCSISelect utility and save a new initiator Hane tor All controllers name on the first iSCSISelect utility menu screen so that the iSCSI initiator name on all controllers match All logins from the Press lt Ctrl gt lt S gt to enter multiple controllers use the new name iSCSISelect Reboot required Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SG EMULEX 13 Troubleshooting 184 Troubleshooting for the FcoE Protocol Table 13 2 Troubleshooting the iSCSISelect Utility Continued Issue Answer Solution You receive any of the following These POST messages indicate that you must reload the UCNA POST error messages or warnings firmware using OneCommand Manager or one of th
183. n screen or to change a configuration default Use the navigation entries on the page to move about the utility Press lt Esc gt to exit the current screen and show the previous screen Select Commit to save changes Select Discard to not save changes Select Back to Display Adapters and RECONNECT DEVICES from the Emulex Adapter Configuration Main Menu when you are finished to ensure the Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 157 DG EMULEX Starting the Emulex FCoE Configuration Utility changes are made active otherwise a system restart is required to make your changes active You are then returned to the adapter list Starting the Emulex FCoE Configuration Utility Depending on the OEM UFFI configuration the Emulex FCoE configuration utility may appear under different setup menus in the OEM system firmware or BIOS such as System Settings gt Storage This description applies to systems where the Emulex utility is found in the Device Manager To start the Emulex FCoE configuration utility using HII 1 Exit the EFI shell Figure 12 1 Exiting the EFI Shell 2 A front page is displayed Launch the Device Manager 3 On the Device Manager screen a list of all the adapters in the system is displayed Your list may vary depending on the installed adapters Locate the adapter you want to configure Use the up down arrows on your keyboard to select it and press lt
184. n the bottom of the menu screens until you are prompted to exit g Save your changes before you exit h Press lt Y gt to exit the iSCSISelect utility 6 After the ESXi Server boots up the MPIO installs drivers on the second path and prompts for a reboot Reboot the server Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 57 SC EMULEX Navigating the FCoE BIOS Utility 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Before using the FCoE BIOS utility ensure that the boot code is loaded and enabled on the adapter as described in Installing Updating and Enabling Boot Code on page 76 Note This section reflects the most recent release of the FCoE BIOS utility Some selections may not be available if you are using an older version of the utility Navigating the FCoE BIOS Utility The FCoE BIOS utility has menus and configuration screens Use the following methods to navigate them e Press the up down arrows on your keyboard to move through and select menu options or configuration fields When multiple adapters are listed use the up down arrows to scroll to the additional adapters e Press lt PageUp gt to scroll to the previous page e Press lt PageDn gt to scroll to the next page e Press lt Enter gt to select a menu option to select a changed value to select a row in a configuration screen or to change a
185. nabled functions on that port must be equal to 100 e The Maximum Bandwidth value is the greatest amount of bandwidth that the function can provide It is represented as a percentage 3 Enter the value for the specified function and press lt Enter gt When you are finished configuring bandwidths press lt Esc gt to return to the Controller Configuration screen Note To disable a function set the Minimum Bandwidth value to 0 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 121 gt lt EMULEX Using the Emulex NIC Configuration Utility Configuring the LPVID The LPVID is used to enforce a VLAN ID on all traffic originating from an IP address channel or PCI function If the operating system for that PCI function has set up a VLAN ID then the operating system configured VLAN ID takes precedence over the LPVID for transmit packets while the operating system configured VLAN ID and LPVID tagged packets will both be received If the operating system has not set up any VLAN IDs then the LPVID is used for tagging Note LPVID and user configured VLAN IDs from the operating system must be different Note LPVIDs also need to be configured on the switch port Each LPVID must be unique and is relevant for NIC traffic only The LPVID is not supported for storage functions For iSCSI storage functions you must configure a VLAN ID through iSCSISelect or through the host For additio
186. naes 41 SOL ANS sic tacwiicedareasascndiscavanadiabasaradnseauaseitarennasneicatenass buses yanseeraaien nse eniese 42 Configuring Boot from SAN on Solaris SFS x86 and X64 cccee eee e cece ee eee ee enes 42 Determining LUNs to Select for Boot from SAN cccececceceeeeeeeeeeeeeeeeaeeeeaanenas 42 Configuring Boot from SAN on Solaris SFS SPARC ccceeeceeeeeeeeesaeeeeaeeeeaaes 43 Installing Solaris from a Network IMage 0ccsseceeseeeeseeeeseeeeseeeesnenesnenags 43 Installing Solaris by Migrating an Image from a Local SCSI Disk ccceee eee e eee 45 Booting Solaris 10 from the Network on SPARC Machines s 47 4 Configuring x86 x64 Platforms for the iSCSI Protocol s ccccecssceeeesseeeeenas 50 ISCS OVEIVIGW ssc cccsccsetaccsectsenseneecanesscctsccseaentetasentsinatasestestodeneseendatnssanens 50 Constructing a Basic iSCSI SAN sssssssssnnnnnnnnnnnuunnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnna 50 Managing an iSCSI SeSSiO iiisssirsssrsiisinnnrindinirnnai rinrin ianiai NaN NSAN 51 Logging into an iSCSI SESSION vsicesiwitineedasveersestuswvessendunbecteeneeitesseertasytegseeies 51 SA T E AT E E A T 51 CHAP AUth NntiGation cc rereana ae a K ET ia E EE ee Pi EDANE oe 51 Configuring for the iSCSI Protocol ssssssssssunnnnnnnnnnnnnnnnnnnnnnnnnannnnnnnnnnnnnnnnnn 51 Setting Up Boot from SAN for iSCSI sssssnsnnuunnrsssrsrrrrrernrrsrrrrrrerrrrrrerrrrrn 51 Windows Server iiss itd cia cide sanbolai dagen
187. nal information see Configuring VLAN ID and VLAN Priority on page 84 To configure an LPVID 1 On the Controller Configuration screen select Configure LPVID and press lt Enter gt The Configure LPVID screen appears Configure LPVID Function 0 Configure Logical Port C ULAN ID Function 4 Function 6 Figure 10 18 Configure LPVID Screen 2 Select the LPVID value for a specific function and press lt Enter gt 3 Enter a value and press lt Enter gt The LPVID range is 2 4094 A value of 0 disables the LPVID Note LPVID values 1 and 4095 are currently reserved and cannot be used or configured Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 122 gt lt EMULEX Using the Emulex NIC Configuration Utility 4 When you are finished configuring LPVIDs press lt Esc gt to return to the Controller Configuration screen Saving the Current Configuration To save the configuration changes on the Controller Configuration screen select Save Current Configurations and press lt Enter gt Configuring Multichannel for IBM Adapters Note This section only pertains to certain Emulex OneConnect UCNAs that support IBM Virtual Fabric multichannel or Unified Fabric Protocol Multichannel provides the ability to configure multiple PCI functions or I O channels for each OneConnect port Note Setting up IBM Virtual Fabric or UFP multichannel depends on cooperat
188. nd FCoE storage functions in the NIC BIOS before they can be configured further from their respective utilities iSCSI or FCoE BIOS Otherwise the Logical Link for that function will still show as down and you will not be able to log into targets or find LUNs behind those targets Note Multichannel functionality is only supported on OneConnect controllers running in 10 Gb mode The 1 Gb mode does not support UMC If multichannel functionality is supported on your system the Emulex UEFI NIC utility enables you to perform the following tasks e Enable or disable multichannel functionality Multichannel Mode e View the current controller configuration e Configure the minimum and maximum bandwidth for each channel e Configure the LPVID for each channel Note Your system may not support all multichannel options Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 116 gt lt EMULEX Using the Emulex NIC Configuration Utility To enable multichannel support 1 On the Emulex NIC Selection screen select Multichannel Mode and press lt Enter gt The Multichannel Mode dialog box appears Emulex NIC Selection Emulex OneConnect 0Ce11102 IM 2 port PCIe 10GbE Configure Multichannel CNA Mode SYSTEM RESET REQUIRED Firmware Version 4 6 152 0 Bus Device Function 15 0 0 Link Speed 10 Gbps Advanced Mode lt Enable gt Personality lt iSCSI gt Multichannel Mode lt Disab
189. nd advanced adapter parameters e iSCSISelect Utility o Setting up a basic configuration o Configuring and managing iSCSI initiators and targets The boot code is distributed in the same image used to flash the firmware Several methods are available for flashing the firmware and boot code image See the documentation accompanying each utility for additional information on the flash procedure Abbreviations ACL Access Control List AL PA Arbitrated Loop Physical Address API application programming interface ARP Address Resolution Protocol BBS BIOS Boot Specification BFS byte file system BIOS basic input output system BOFM Blade Open Firmware Management Protocol CEE Converged Enhanced Ethernet CHAP Challenge Handshake Authentication Protocol CIN Cisco Intel Nuova CLI command line interface DCB Data Center Bridging DCBX Data Center Bridging Exchange Protocol DHCP Dynamic Host Configuration Protocol DID device ID DMA direct memory access DNS Domain Name System EDD Enhanced Disk Device EFI Extensible Firmware Interface FC Fibre Channel FC AL Fibre Channel Arbitrated Loop FCF FC Forwarder FCoE Fibre Channel over Ethernet FL_Port fabric loop port FMP Firmware Management Protocol FoD Feature on Demand Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX FTP FUI Gb s GPT GUI GUID HBA HI HTTP TEEE INTx I O IOCTL IP IQN iSCSI JBOD KB LACP LDAP LED LOM LPVID LUN MAC MBR MPIO MSI MSI
190. nnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 160 Configuring CEE FCF ParameterS ssssssssssssnnnnnnnnnnnsnunnnnnnnnnnnnnnannnnnnnnnnnan 161 Configuring CIN FCF Parameters ssssssssnssnssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 163 SCANNING for Fibr DEVICES was sssanssgusesswnadeanrssinaescrenseisesclreaenirnmecemneoeTmeneE 164 Adding Boot DeVICES iciiscstsctscssestsscssasesscsassacassenestanestanassaneststestanectanassacases 164 Deleting BOOt Devices scrire ERa 166 Changing Boot Device Order sssssssssnnnnssnsnnunnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnn 167 Configuring Adapter ParameterS sssssssssssusnnnnnnnnnnnnnunnnnnnnnnnnnnnunnnnnnnnnnnnn 170 Changing the PLOGI Retry Timer vccviestivesews visoravevtivbinarsonedoobveiarsiearereneahe 170 Changing the Maximum LUNS per Target cecceseeeeeeeee sents eeanereneeneaneneaes 171 Changing Boot Target Scan Method cccccccseeeeeeeeeeeeeeeeeeeeeeeeteeeneeeennenenes 172 Changing Device Discovery Delay vei ivcssiversissonverieesteivenwiebssareiarsteereiwarnns 174 Resetting Emulex Adapters to Default ValueS sssssssnnssrssnunnnnnnnnnnnnnnnnnnnnnnn 175 Displaying Adapter Information sssasssssnnrnnnsnunnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 177 13 Troubleshooting sssssssssssssnnnunnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnn 178 Troubleshooting for the NIC Protocol ssssssssssssnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 178 Issues During the PXE Boot
191. nsennssuesaieenasbanarmitantiadanmaetennenneaseneas 102 Using the Emulex NIC Configuration Utility cccccccsceecsceecsceeesceeeseeesueeesuneeas 103 Navigating the WEIN Yc lt lt cacuvisticeusedaseuapupieseersmnseadseesempesbnansenpanceensennesiees 103 Downloading the Latest Firmware and Boot Code cccccccseeeeeeeeeeeeeeeeeenenes 103 Firmware Components caereaiedidsaeredaneeadadoer nate Madvartwetela nig dew end EE ven Dataianad 103 Viewing the Adapter s Firmware and Boot Code VerSion cceeeeee eee eee eee eee 103 Downloading Firmware and Boot Code ccccccceeeeeceeeceeeeeeeeeeeeuteseeeeeeeeneeaes 105 Advanced Mode Support ss svsc vetacaveasusiasyesinyeeed ieeaey scasuUdeueeeebveunts peae Bian ye 109 Configuring Personality 2ccaccicceravestvsenmelacedreswsenshdracearecisrtesbensdene setadeceabes 110 Configuring the Controller When Multichannel is Disabled or Not Supported 112 Viewing the Configuration ccccccccccecceeeeeeeeee sees cee EEEE sees see EEEE EEEE 113 Configuring SR lOViicccised thi chisaiddasdaaadas Sas bekiwa dada aiai 113 Saving the Current Configuration occ cece eee eee eee tented 114 Configuring Universal Multichannel sci 2c esecctaeckaceeedandd lasdatae sd baecud dade iapgandes 115 Viewing the Contiqurationcsiisciscctaiiaatalcndaetieitid atidsaeia dade ldacaviaeaeaiiads 118 Viewing the Current SR IOV Configuration 119 Configuring Minimum and Maximum Bandwidth
192. ntly directs the server to boot from a logical unit disk on the SAN as if it were a local disk Emulex provides the following types of boot code e Preboot eXecution Environment PXE boot for NIC adapters in x86 and x64 systems e x86 BootBIOS for FCoE adapters in x86 and x64 systems e iSCSI boot for iSCSI adapters in x86 and x64 systems e UEFIBoot for NIC iSCSI and FCoE adapters in x64 systems This provides system boot capability through the use of the UEFI Unified Extensible Firmware Interface Shell It also functions on UEFI 2 x based platforms through the HII Human Interface Infrastructure interface e OpenBoot for FCoE adapters in Sun SPARC systems OpenBoot is also called FCode Note Emulex drivers support multipath boot configurations See your storage vendor s documentation for information on configuring multipath booting The Emulex boot code and the following utilities provide a variety of capabilities e Boot from SAN across the different networking protocols and operating systems e UEFI configuration using the Emulex NIC FCoE and iSCSI Configuration Utilities e PXESelect Utility o Configuring the port and controller o Configuring multichannel support personality options and advanced mode support e FCoE Boot BIOS Utility o Scanning for target devices Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 1 Introduction gt G EMULEX Abbreviations 19 o Configuring boot devices DCBX mode a
193. nual P009697 01A Rev A DG EMULEX 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures Configuring Advanced Adapter Parameters 2 Select Change Default ALPA of this adapter and press lt Enter gt Information similar to Figure 5 19 is displayed 01 0Ce10100 Mem Base CE2C0000 Port Nane 10000000C35B7791 Ulan ID 0001 DCBX mode CEE Figure 5 19 Change Default ALPA Screen Firmuare Version node Bust 02 Devitt 00 Funct 02 2 702 485 1 Node Name 20000000C9587791 BIOS Enabledt 3 Change the default AL_PA use the up and down arrow keys to scroll through the valid AL_PAs Table 5 1 lists the valid AL_PA values Press lt Enter gt to accept the new value 5 Press lt Esc gt to return to the advanced adapter configuration menu 6 For changes to take effect reboot the system Note If the adapter s AL_PA is changed it does not show on the NVRAM AL_PA until the system has been reset Table 5 1 Valid AL_PA Values 0x00 0x01 0x02 0x04 0x08 OxOF 0x10 0x17 0x18 0x1B 0x1D 0x1E Ox1F 0x23 0x25 0x26 0x27 0x29 0x2A 0x2B 0x2C 0x2D 0x2E 0x31 0x32 0x33 0x34 0x35 0x36 0x39 0x3A 0x3C 0x43 0x45 0x46 0x47 0x49 0x4A 0x4B 0x4C 0x4D 0x4E 0x51 0x52 0x53 0x54 0x55 0x56 0x59 0x5A 0x5C 0x63 0x65 0x66 0x67 0x69 0x6A 0x6B 0x6C 0x6D 0x6E 0x71 0x72 0x73 0x74 0x75 0x76 0x79 0x7A 0x7C 0x80 0x81 0x82 0x84 0x88 0x8F 0x90 0x97 0x98 0x9B 0x9D 0x9E
194. nux v v A Citrix v v A VMware v v v Note For the Citrix and VMware operating systems the OneCommand Manager application GUI is not supported locally but can be managed through the GUI from a remote system After you decide which utility to use see the appropriate documentation for the proper procedures e OneCommand Manager application see the OneCommand Manager Application User Manual e HBAcmd utility see the OneCommand Manager Application CLI User Manual e Offline utility see the Offline Utilities User Manual Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A sc 7 Configuring iSCSI Boot Support with the iSCS Select Utility 77 gt C EMULEX Navigating the iSCSISelect Utility 7 Configuring iSCSI Boot Support with the iSCSISelect Utility This section provides quick installation instructions for setting up a basic boot configuration For more information on setting up an iSCSI initiator and adding an iSCSI target see chapter 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility on page 80 and chapter 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility on page 86 Navigating the iSCSISelect Utility Use the following methods to navigate the iSCSISelect utility e Press the up down arrows on your keyboard to move through and select menu options or configuration fields When multiple adapters are listed use the up down arrows
195. o The hexadecimal representation of CHAP secrets must only contain hexadecimal values The 0x representation must only have the following characters 0 1 2 3 4 5 6 7 8 9 a b c d e f A B C D E and F Any other characters are not allowed When you have successfully enabled the CHAP authentication the Add Ping iSCSI Target dialog box appears For more information see Pinging a Target on page 95 Authenticating Mutual CHAP With mutual CHAP authentication the target authenticates the initiator and the initiator authenticates the target Use mutual CHAP authentication for a two way challenge response security method To enable mutual CHAP authentication 1 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 94 gt G EMULEX Managing an iSCSI Target 2 Select Controller Configuration and press lt Enter gt A list of controllers is displayed 3 Select a controller and press lt Enter gt The Controller Configuration menu is displayed 4 From the Controller Configuration menu select iSCSI Target Configuration and press lt Enter gt 5 Select Add New iSCSI Target and press lt Enter gt 6 From the Add Ping iSCSI Target dialog box select Authentication Method and select Mutual Chap and press lt Enter gt The CHAP Configuration dialog box
196. o one of the following e Enable DHCP For more information see Enabling DHCP on page 82 e Set up a static IP address For more information see Configuring a Static IP Address on page 83 If desired configure a VLAN ID For more information see Configuring VLAN ID and VLAN Priority on page 84 Add a SCSI target From the Controller Configuration menu select iSCSI Target Configuration then select Add a New iSCSI Target For more information see Adding iSCSI Targets on page 86 After you have successfully configured the iSCSI initiator and target reboot the system Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A aw 7 Configuring iSCSI Boot Support with the iSCSISelect Utility 79 gt G EMULEX Booting the System Booting the System After you have successfully set up your basic boot configuration exit the iSCSISelect utility and the system automatically reboots During the next boot up the iSCSI BIOS logs into the configured iSCSI boot target and display its target LUN information in the BIOS sign on banner For example Controller 0 Port 0 Base OxFCE60000 at Bus 01 Dev 00 Fun 02 Controller 0 Port 1 Base OxFCEA0000 at Bus 01 Dev 00 Fun 03 lt lt lt Press lt Ctrl gt lt S gt for iSCSISelect TM Utility gt gt gt Initiator iSCSI Name iqn 2004 05 com emulex Initiator IP Address 172 40 1 41 Initiator IP Address 172 40 1 62 Drive 0 NETAPP LUN 0 2048 MB Drive Geo
197. oE functions To view the current SR IOV configuration 1 On the Controller Configuration screen select Configure SRIOV and press lt Enter gt The Configure SRIOV screen appears Configure SRIOU lt Disable gt Enable Disable SRIOU lt Disable gt Support lt Disable gt Figure 10 16 Configure SRIOV Screen 2 When you are finished press lt Esc gt to return to the Controller Configuration screen For more information on SR IOV configuration see the appropriate Emulex driver manual Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 120 gt lt EMULEX Using the Emulex NIC Configuration Utility Configuring Minimum and Maximum Bandwidth To configure bandwidth 1 On the Controller Configuration screen select Configure Bandwidth and press lt Enter gt The Configure Bandwidth screen appears Configure Bandwidth Configure Minimum Bandwidth Percentage Function Function Function Function Function Function Function Function Figure 10 17 Configure Bandwidth Screen 2 Select a specific function under Configure Minimum Bandwidth or Configure Maximum Bandwidth and press lt Enter gt e The Minimum Bandwidth value is the least amount of bandwidth that the function can provide It is represented as a percentage The Minimum Bandwidth value must be less than or equal to the Maximum Bandwidth value The total of the Minimum Bandwidth values for all e
198. ode extended mode and manufacturing mode Parameters c Diagnose all child devices 1 XXX Diagnose using the ISO 639 2 language specified by XXX s Run diagnostics in standard mode Diagnostics in standard mode run the LED test Link test Get MAC test and the DMA test Read Write and Read and Write e Run diagnostics in extended mode Diagnostics in extended mode run the ARM Timer test the MAC Loopback test and the Physical Loopback test m Run diagnostics in manufacturing mode Diagnostics in manufacturing mode run the Network Loopback test for the OneConnect OCe10100 series adapter and the Low level Subsystem NLB test for the OneConnect OCE11100 series adapter driverhandle Handle of the driver being configured devicehandle Handle of a device that the driverhandle is managing childhandle Handle of a device that is a child of the devicehandle Examples The following examples show you a way of using the EFI_DRIVER_DIAGNOSTICS_PROTOCOL The driver command identifies the handle of the driver Shells drivers 122 Emulex 10G NIC Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 132 gt EMULEX Using the Emulex NIC Configuration Utility The drvdiag command list all the devices available for diagnostics Each Ctrl XXX corresponds to a NIC function which may be physical or virtual The command returns handles for NIC functions on both ports Sh
199. odules Load FireWire Modules Load File System Modules Load Unknown Modules Show Loaded Modules Unload Modules Add Driver Update Show Driver Updates Back Figure C 8 Kernel Modules Hardware Drivers Menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix C Example for Configuring and Booting UEFI NIC 208 gt EMULEX Configuring the IBM HS22 Blade with e Raptor MEZZ 9 The Driver Update Medium Selection listing is displayed Select a medium and click OK Kernel Modules Hardware Drivers Please choose the Driver Update nediun sr USB CD ROM MATSHITA DUD RAM UJE7OBJ J USB Partition Kingston DataTraveler G2 sdbi Partition IBM ESXS 51914685235 sdb2 Partition IBM ESXS 51914685235 sdb3 Partition IBM ESXS 51914685235 sdb4 Partition IBM ESXS 51914685235 other device mex M N Figure C 9 Driver Update Medium Selection Listing 10 The Driver Update List confirmation dialog box is displayed Click OK Driver Update list Driver Update for be2net OK Figure C 10 Driver Update List Dialog Box 11 The Expert menu Figure C 7 is displayed Click Back 12 The Main menu Figure C 6 is displayed Select Start Installation and click OK 13 The Source Medium Selection menu is displayed Select Network and click OK Choose the source medium DUD CD ROM Network Hard Disk E Back Figure C 11 Source Medium Selection Menu Boot
200. ollowing is an example of a target detail Add New iSCSI Target 001 iqn 1984 gt IPv4 172 40 46 150 3260 0 Yes Connected Figure 9 5 iSCSI Target Configuration Information In the iSCSI Target Configuration menu the functions keys located at the bottom of the menu help you manage your target configuration e Press lt Enter gt to select the target configuration e Press lt Del gt to delete the target e Press lt F5 gt to log in to the target e Press lt F6 gt to log out of the target e Press lt F7 gt to configure the LUN e Press lt Esc gt to return to the previous menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A xs 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility Q1 gt C EMULEX Managing an iSCSI Target Editing a Target Configuration Once you have added a target you can edit your iSCSI target configuration or apply other management options to the target To edit a target configuration 1 From the iSCSI Target Configuration dialog box select the target and press lt Enter gt The Edit Ping iSCSI Target dialog box is displayed iSCSI Target Name gt iqn 1984 05 emulex IP Version IPv4 iSCSI Target IP Address 172 40 46 150 TCP Port Number 3260 OneConnect Port 0 Boot Target ISID Qualifier fae E Header Digest Data Digest Authentication Method Figure 9 6 Edit Ping iSCSI Target Dialog Box 2 If you want to enable the tar
201. ology type sbin multipath 1 Reboot your system and log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 4 Configuring x86 x64 Platforms for the iSCSI Protocol SG EMULEX Configuring for the iSCSI Protocol 8 Use the iSCSISelect utility to add an additional boot path to the same iSCSI LUN To do this follow these steps a Follow the steps for the Linux and Citrix Servers on page 52 to set up the second path b When you get to the Add Ping iSCSI Target menu make sure you set a valid ISID Qualifier before adding your target For more information on the ISID Qualifier see Setting an ISID Value on page 92 c After you have logged into the target from the iSCSI Target Configuration menu set the Boot Target option for the second target to Yes d Press lt F7 gt to display the LUNs behind the target Select the same LUN you chose for your initial boot LUN then press lt F3 gt to set it to bootable f Follow the instructions on the bottom of the menu screens until you are prompted to exit g Save your changes before you exit h Press lt Y gt to exit the iSCSISelect utility After Linux boots up the MPIO installs drivers on the second path and prompts you to reboot Reboot the server ESXi 5 0 or 5 1 Server To install and configure MPIO on ESXi Server 1 2 Boot for NIC iSCSI and FCoE Protocols Use
202. on page 92 c After you have logged into the target from the iSCSI Target Configuration menu set the Boot Target option for the second target to Yes d Press lt F7 gt to display the LUNs behind the target Select the same LUN you chose for your initial boot LUN then press lt F3 gt to set it to bootable After Windows Server boots up the MPIO installs drivers on the second path and prompts for reboot Reboot the server Linux and Citrix Servers To install and configure MPIO on Linux or Citrix 1 2 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted Use the iSCSISelect utility to log into a target from one adapter and configure it for boot by following the steps for the Linux and Citrix Servers on page 52 If the iSCSISelect utility is configured properly a message during boot time indicates that the iSCSI disk was successfully connected Install a Linux operating system over the iSCSI LUN For more information refer to the Emulex Driver for Linux User Manual Once Linux is installed install the MPIO software and reboot the system After rebooting ensure that the boot LUN is detected by the MPIO driver Perform either of the following steps e To see if the multipath is running type sbin multipath or e To see if the multipath daemon is running type ps aelf grep multipathd If multipath is running you can view the current multipath topology To view the current multipath top
203. on screen select View Configuration and press lt Enter gt The View Configuration screen appears View Configuration Function 0 NIC Permanent MAC 00 00 C9 BC CE 40 Current MAC 00 00 C9 BC CE 40 Logical Link Status Link Up SRIOU Disabled Bandwidth 25 1004 LPVID er i Function 2 iSCSI Permanent MAC 00 00 C9 BC CE 41 Current MAC 00 00 C9 BC CE 41 Logical Link Status Link Down SRIOU Disabled Bandwidth 254 904 Figure 10 15 Multichannel Configuration for Function 0 Screen From the View Configuration screen you can view information for that specific function including the permanent and current MAC addresses the logical link status the current SR IOV setting the minimum and maximum bandwidth settings and LPVID of all of the NIC functions Note Logical Link Status and LPVID for storage functions iSCSI and FCoE display as N A 2 When you are finished viewing the configurations press lt Esc gt to return to the Controller Configuration screen Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 119 gt lt EMULEX Using the Emulex NIC Configuration Utility Viewing the Current SR IOV Configuration Note SR IOV cannot be configured with multichannel enabled The Configure SRIOV option only displays the current SR IOV status which is disabled Note SR IOV is only available for NIC functions and not for storage iSCSI or FC
204. onfiguration Utility Advanced Mode is a driver compatibility option With Advanced Mode enabled you can run Advanced Mode aware drivers that provide advanced capabilities as listed in Table 10 1 With Advanced mode disabled you can run older legacy inbox drivers that are not Advanced Mode aware with the latest firmware versions Note Advanced Mode support is enabled by default on OCe11100 series 2 port and 4 port controllers On 4 port controllers the Advanced Mode setting is not provided in the PXESelect HII utilities The Advanced Mode setting on these platforms is implicitly enabled and Advanced Mode aware drivers must be installed Compatibility with legacy drivers requires that Advanced Mode support be disabled on 2 port controllers Note The Advanced Mode capability is not supported on OCe10100 series controllers Table 10 1 Advanced Mode Capabilities by Operating System Operating System Advanced Mode Enabled Windows 16 RSS queues Note Only supported on Windows 2008 R2 and Windows Server 2012 Remains four queues for earlier Windows versions Advanced Mode Disabled Legacy Mode 4 RSS Queues VMQ lookahead split Note VMQs are only supported on Windows 2008 R2 and later Lookahead split is silently ignored There may be a small performance penalty for VMQs Linux and Citrix 16 RSS Queues 4 RSS Queues VFs PFs can be increased up to 30 VMware ESXi For both 1500 and 9000 MTU 16 N
205. or IQN name and target IQN name Verify that succeeds but no LUNs are available they are properly specified e Check target s ACL settings if any to verify that the initiator s IQN name is listed and can be recognized e Make sure that the target login parameters are compatible with the initiator s e If this checklist confirms that initiator and target are configured correctly and the issue persists erase the Controller Configuration For more information see Erasing the Configuration on page 98 Login to iSCSI target is successful Check the jumbo frame settings on the iSCSI target If enabled but iSCSI I O causes the system to change the frame size to 1514 and retry This isolates any issues hang or freeze in the network related to jumbo frames J umbo frames when supported by the entire network provide increased performance Note OneConnect adapters support jumbo frames Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SG EMULEX 13 Troubleshooting 183 Troubleshooting for the iSCSI Protocol Table 13 2 Troubleshooting the iSCSISelect Utility Continued Issue Answer Solution Unable to boot from the iSCSI e Check the target setup Check the target ACL to verify that target the initiator s iSCSI name is listed and can be recognized e Check the initiator name and make sure it is correct e If applicable verify that you have selected the iSCSI LUN as the boot LUN in your syste
206. piring To enable DHCP 1 From the Controller Configuration menu select Network Configuration and press lt Enter gt Figure 8 4 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 8 Configuring and Managing the iSCSI Initiator with the iSCSISelect Utility 83 SG EMULEX Configuring a Static IP Address 2 Select Enabled from the DHCP drop down menu and press lt Enter gt 3 Select Save DHCP Settings and press lt Enter gt The DHCP IP Address dialog box appears For example IP Address 172 40 8 13 Subnet Mask 200 2 eae i Default Gateway 172 40 B 1 Figure 8 5 DHCP IP Address Dialog Box Note If you have set a static IP address a message warns that the static IP address will be lost Press lt Y gt to continue with enabling DHCP Configuring a Static IP Address If a DHCP server is not available you must manually configure a static IP address To configure a static IP address 1 From the Network Configuration menu select Configure Static IP Address and press lt Enter gt Note If you have DHCP enabled a message warns that the DHCP IP Address will be lost Press lt Y gt to continue to configure a static IP address The Static IP Address dialog box is displayed IP Address Subnet Mask Default Gateway Figure 8 6 Static IP Address Dialog Box Enter the IP address This is a unique 32 bit address that specifies the location of each device or workstation
207. ple Array Screen Note To minimize the amount of time needed to locate the boot device Emulex recommends that you select the drive with the lowest AL_PA as the boot device 3 Select lt 00 gt and press lt Enter gt to clear the selected boot entry or select a device to configure booting by WWPN or DID and press lt Enter gt 4 Ifyou select a device you are asked for the starting LUN Use the up and down arrows to enter the starting LUN in hexadecimal format and press lt Enter gt Figure 5 7 The starting LUN can be any number from 0 to 255 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 61 gt EMULEX Configuring Boot Devices 01 O0Ce10100 Bust 02 Devitt 00 Funct 02 Nem Base CE2C0000 Firmuare Version 2 702 485 1 BIOS Enabledt Port Name 10000000C95B7731 Node Name 20000000C95587791 Ulan ID 0001 DCBX mode CEE mode 1A14BC WWPN 21000011 C68O0A5D LUN 00 SEAGATE ST373554FC Figure 5 7 LUN Listing Screen 5 A screen similar to Figure 5 8 is displayed Press lt Enter gt 01 0Ce10100 Bus 02 Dev 00 Func 02 Mem Base CEZCO000 Firmware Version 2 702 435 1 BIOS Enabled Port Name 10000000C95B87595 Node Name 20000000C95B87595 Vlan ID 0001 DCBX mode CEE mode DID 0203E4 WWPN 22000004 CF926A79 01 LUN 00 SEAGATE 51T318452FC 0004 Figure 5 8 Boot Device Selected The Boot Devices menu is displayed
208. ppears after you select a port in the Port Selection Menu Controller 0 Port 0 Bus 15 Dev 00 Firmware Version v4 6 139 0 Port Speed 10 Gbps Physical Link Status Link Up PXE Boot Support Enabled PF Type MAC Address Disabled Status SR IOV Func 0 NIC 00 00 c9 bc ce 40 Func 2 iSCSI 00 00 c9 bc ce 41 N A Disabled Figure 2 7 Port Configuration Screen Note Logical Link Status is displayed as N A for storage functions The Port Configuration screen enables you to perform the following tasks e Configure PXE boot support e Configure SR IOV e Configure PXE VLAN ID and Priority e Identify ports e Erase the port and adapter configuration Configuring PXE Boot Support To configure PXE boot support 1 On the configuration screen use the lt Tab gt key to select the PXE Boot Support setting and a drop down menu appears 2 From the drop down menu select Enabled or Disabled and press lt Enter gt 3 Select Save and press lt Enter gt Note During system startup PXE contacts the DHCP server for an IP address to boot from the network Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 29 gt EMULEX Using the PXESelect Utility Configuring SR IOV If your system BIOS supports SR IOV you can enable it SR IOV support can only be enabled when multichannel is disabled or it is not supported For more information on SR IOV configuration
209. ppendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot C EMULEX pp p a ou 187 Linux and Citrix PXE Server Remote Installation Procedure Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure PXE configuration requires a PXE server and the PXE client Setting up a PXE server requires the following configurations e NFS server e TFTP server e DHCP server e PXE boot server The pxelinux functionality occurs in this order 1 2 The client machine boots to PXE which requests a DHCP address The DHCP server responds with an IP address for the client machine along with the address of a TFTP server and a filename to load pxelinux 0 from that server The client downloads pxelinux 0 from the specified TFTP server and executes it The pxelinux 0 file searches the pxelinux cfg directory on the server for a configuration file that matches the IP address of the machine If no matches are found it attempts to load a file called default The configuration file loaded by pxelinux 0 has instructions on what to do next Some of the choices include boot to local hard drive boot to an image file floppy image or load vmlinuz and initrd img The client searches for a configuration file with the IP address converted to hexadecimal for example 192 168 1 60 becomes C0A8013C or the MAC address of yo
210. press lt Enter gt The iSNS Configuration screen is displayed Porti HP CN1100E Dual Port Converged Network Adapter iSCSI Target Configuration iSNS Configuration gt iSNS Discovery Mode Disable iSNS Server Discovery via DHCP Disable iSNS Server IP iSNS TCP Port 3205 Save Changes Available Servers Figure 11 18 iSNS Configuration Screen The iSNS Configuration screen enables you to perform the following tasks Enable or disable iSNS discovery mode Enable or disable iSNS server discovery via DHCP Configure the iSNS server IP address and TCP port number manually Save any changes made to the iSNS configuration View a list of available iSNS servers Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 11 Configuring UEFI for iSCSI 151 gt lt EMULEX Adding and Configuring Targets Enabling iSNS Discovery This option enables or disables iSNS discovery iSNS targets are only discovered when this option is enabled To enable or disable iSNS discovery 1 From the iSNS Configuration screen select iSNS Discovery Mode and press lt Enter gt iSNS Server Discovery via DHCP Disable iSNS Server IP 9 iSNS TCP Port 3205 Save Changes Available Servers Figure 11 19 iSNS Discovery Mode Screen 2 Select either Enable or Disable and press lt Enter gt 3 Select Save Changes and press lt Enter gt to save the current settings Enabling iSNS Server Discovery via DHCP Thi
211. pt Once the Unix prompt appears append the following line to the system file at a etc system set pcie pcie max_mps 0 Save and reboot server Installing Solaris from a Network Image The system must have a DVD drive and must be part of the site s network and naming service If you use a naming service the system must already be in a service such as NIS NIS DNS or LDAP If you do not use a naming service you must distribute information about this system by following your site s policies Note This procedure assumes that the system is running the Volume Manager If you are not using the Volume Manager to manage media refer to the Sun Microsystems System Administration Guide Devices and File Systems To install from a network image 1 2 Log on as a superuser or equivalent Insert the Solaris DVD in the system s drive Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 44 Solaris gt EMULEX 3 Create a directory to contain the DVD image mkdir p install dir path Install_dir_path specifies the directory where the DVD image is to be copied 4 Change to the Tools directory on the mounted disc cd cdrom cdrom0 Solaris 10 Tools Note For Solaris 10 only a Remove the SUNWemlxu and SUNWemlxs from install_dir_path Solaris Tools Boot b Unzip the elxfc driver to a temporary directory pkgadd R install_dir path Solaris Tools Boot
212. r See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information If necessary enable the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information Configure boot devices See Enabling an Adapter to Boot from SAN on page 58 for more information If desired configure the boot options on the adapter See Configuring Advanced Adapter Parameters on page 66 for more information Use the driver on the operating system distribution disk to boot the system If necessary you can update the driver to the latest version Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX Solaris 3 Configuring Boot from SAN for the FCoE Protocol 42 Solaris Configuring Boot from SAN on Solaris SFS x86 and x64 To configure boot from SAN 1 If necessary install or update the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information If necessary enable the boot code on the adapter See chapter 6 Installing Updating and Enabling Boot Code on page 76 for more information Enable the adapter to boot from SAN See Enabling an Adapter to Boot from SAN on page 58 for more information If necessary enable spinup delay See Enabling or Disabling the Spinup Delay on page 69 for more information Configure boot devices
213. r Manual P009697 01A Rev A Log into the iSCSISelect utility pressing lt Ctrl S gt when prompted Use the iSCSISelect utility to log into a target from one adapter and configure it for boot by following the steps for the ESXi Server on page 52 If the iSCSISelect utility is configured properly a message during boot time indicates that the iSCSI disk was successfully connected Install an ESXi server operating system over the iSCSI LUN For more information refer to the Emulex Driver for VMware User Manual Once the ESXi server is installed install the MPIO software and reboot the system The ESXi Server is MPIO by default Use the iSCSISelect utility to add an additional boot path to the same iSCSI LUN To do this follow these steps a Follow the steps for the ESXi Server on page 52 to set up your second path b When you access the Add Ping iSCSI Target menu set a valid ISID Qualifier before adding your target For more information see Setting an ISID Value on page 92 c After you have logged into the target from the iSCSI Target Configuration menu set the Boot Target option for the second target to Yes d Press lt F7 gt to display the LUNs behind the target e Select the same LUN you chose for your initial boot LUN then press lt F3 gt to set it to bootable 55 4 Configuring x86 x64 Platforms for the iSCSI Protocol 56 SG EMULEX Configuring for the iSCSI Protocol f Follow the instructions o
214. red on different servers This issue may happen only when both are configured on separate servers UNDI Error Codes PXE E60 Invalid UNDI API function number The underlying UNDI drivers do not support the UNDI API sent from BaseCode NBP Check with the hardware vendor PXE E61 Media test failed check cable There is no physical link on the PXE client port on which the boot is attempted Check the cables on the NIC interface PXE E63 Error while initializing the NIC There is an issue in initializing the hardware as part of the UNDI_Initialize API Check with the hardware vendor BaseCode UNDI Loader Error Codes PXE EC1 BaseCode ROM ID structure was not found The UNDI boot module can not find the BaseCode ROM ID structure This may be caused by a corrupted BaseCode ROM image PXE EC3 BaseCode ROM ID structure is invalid The BaseCode ROM ID structure is invalid This may be caused by a corrupted BaseCode image in ROM PXE EC4 UNDI ROM ID structure was not found The BaseCode loader module could not locate the UNDI ROM ID structure The UNDI ROM image is probably corrupted PXE EC5 UNDI ROM ID structure is invalid The UNDI ROM image is probably corrupted PXE EC8 PXE structure was not found in UNDI driver code segment The UNDI ROM image is probably corrupted Bootstrap and Discovery Error Codes PXE E74 Bad or missing PXE menu and
215. ress The method that you choose depends on your network configuration If your network uses a DHCP configuration then you can enable DHCP and obtain an IP address from the DHCP server If a DHCP server is not available you must configure a static IP address You can also set a VLAN ID and or priority from the Network Configuration dialog box Note For all Linux based operating systems Emulex recommends that you enable DHCP when attempting to assign an IP address to an iSCSI port This should be done as the iSCSI firmware will not detect it as a duplicate IP address if one already exists on a Linux server Otherwise you must manually ensure there are no duplicate IP addresses before assigning an IP address Note If you are using target discovery through DHCP you must add the root path to the DHCP server and enable DHCP discovery through the iSCSISelect utility MAC Address 00 16 88 05 e4 c2 Port Speed 10 Gbps Link Status Link Up DHCP Figure 8 4 Network Configuration Dialog Box Enabling DHCP Enabling DHCP provides the initiator with an IP address Note If you are using the DHCP server to obtain an IP address for your iSCSI initiator set up a reservation A reservation assigns a specific IP address based on the MAC address of your iSCSI function If you do not reserve an IP address through DHCP then you must set the lease length for the iSCSI initiator IP address to unlimited This prevents the IP address lease from ex
216. retry timer e Enable or disable spinup delay e Set autoscan e Enable or disable EDD 3 0 e Enable or disable the start unit command e Enable or disable the environment variable e Enable or disable the auto boot sector To access the adapter configuration menu from the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed 01 OCe10100 Bust 02 Devt 00 Funct 02 Mem Base CE2C0000 Firmware Version 2 703 269 2 BIOS Enabledt Port Name 10000000C95B7595 Node Name 20000000C95B7595 Ulan ID 0001 DCBX mode CEE mode Change Default ALPA of this Adapter Figure 5 18 Advanced Adapter Configuration Menu Default settings are acceptable for most installations To reset all values to their defaults from the main configuration menu Figure 5 2 select Reset Adapter Defaults and press lt Enter gt Changing the Default AL_ PA The default value of the AL_PA for the adapter BIOS is 00 hex All adapters or boot drives can be configured to other AL_PAs rather than their default values Note This option applies only to arbitrated loop FC AL The FCoE protocol does not support FC AL To change the default AL_PA 1 On the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed Figure 5 18 Boot for NIC iSCSI and FCoE Protocols User Ma
217. rmation is displayed The following iSNS server options are available on this screen e Ping Server select this option to check connectivity to the server e Discover Targets select this option to display a list of targets available on the iSNS server One or more targets can be added by logging into the targets individually All added targets are listed under Discovered Targets on the iSCSI Target Configuration screen Figure 11 17 e Remove Server select this option to remove the server from the Available Servers list Note This only removes the server and not the targets added by this server To remove the targets select the target from the Discovered Targets list under the iSCSI Target Configuration screen Figure 11 17 select Delete Target and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SC EMULEX 11 Configuring UEFI for iSCSI 155 Erasing the Configuration Erasing the Configuration Erase Configuration erases the configuration of a single controller Configuration data is erased for both ports on the selected controller Erase configuration restores the default settings only for that particular controller When an initiator name is global for all adapters the IQN configured on the first adapter is reflected on all controllers Note For HP systems the initiator name on all ports of the selected controller are reset to their respective default values Note You mus
218. rom the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press lt Enter gt The adapter configuration menu is displayed Figure 5 18 2 Select Enable or Disable Environment Variable and press lt Enter gt The Environment Variable configuration screen is displayed 01 OCe10100 Bus 02 Devitt 00 Funct 02 Mem Base CEZC0000 Firmware Version 2 703 269 2 BIOS Enabled Port Name 10000000C95B7595 Node Name 20000000C95B7595 Vlan ID 0001 DCBX mode CEE mode Enab le Figure 5 25 Enable or Disable Environment Variable Screen Select whether to enable or disable the environment variable Press lt Enter gt to select the change Press lt Esc gt to return to the advanced adapter configuration menu Oy OT epa For changes to take effect reboot the system Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 73 DG EMULEX Using Multi Path Boot from SAN Enabling or Disabling Auto Boot Sector This option automatically defines the boot sector of the target disk for the migration boot process which applies only to HP MSA1000 arrays If there is no partition on the target the default boot sector format is 63 sectors The default setting is disabled To enable or disable the auto boot sector format 1 From the main configuration menu Figure 5 2 select Configure Advanced Adapter Parameters and press
219. rts to a VLAN All ports in a single VLAN are in a single broadcast domain You do not have to configure VLANs unless your network is already using them Some reasons why VLANs are used include e ALAN increases in size with several devices e ALAN has increased broadcast traffic on it e Groups of users ona LAN need more security A VLAN ID like an IP address or initiator name is assigned a value to uniquely identify it on a network A VLAN priority is set to determine what packet gets priority order within a VLAN To configure a VLAN ID and VLAN priority 1 On the Network Configuration menu select Configure VLAN ID Priority and press lt Enter gt The Configure VLAN ID Priority dialog box appears ULAN Support ULAN ID ULAN Priority Save Figure 8 7 Configure VLAN ID Priority Dialog Box 2 Select the VLAN Support drop down menu and select Enabled 3 Seta VLAN ID number This is a unique value you assign to each VLAN ona single device There are a maximum of 4095 possible values ranging from 0 4094 4 Seta VLAN Priority if necessary This unique value assigns a priority to outbound packets containing a specified VLAN ID Valid values range from 0 7 with 0 the highest priority level 5 Select Save and press lt Enter gt 6 Press lt Esc gt to return to the Network Configuration menu Identifying a Port Port identification or beaconing helps you physically determine which port you are configuring by blinking
220. s lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 159 gt C EMULEX Enabling an Adapter to Boot from SAN 3 Select Enable and press lt Enter gt The selection is changed to NVRAM and the current setting is displayed Emulex Adapter Configuration Main Menu 001 OCei0102 FM PCie2 5Gb s x8 Back to Display eg 00 Bus 04 Dev 00 Func 02 VlanID 0002 Adapters and RECONNECT OCe10102 FM Node Name 20000000C9557857 DEVICES Back to Display Adapters and RECONNECT DEVICES Set Boot from SAN lt Enable gt onfigure DCBX Mode lt CEE gt Onfigure CEE FCF Parameters Onfigure CIN FCF Parameters can for Fibre Devices Add Boot Device Delete Boor Device Change Boot Device Order onfigure HBA and Boot Parameters Ser Emulex Adapter to Default Settings Figure 12 4 Emulex Adapter Configuration Main Menu Network Boot Options Menu Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 160 gt C EMULEX Configuring DCBX Mode Configuring DCBX Mode To configure DCBX mode for the FCoE initialization protocol 1 From the Device Manager screen Figure 12 2 select the adapter to configure and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Configure DCBX Mode and press lt Enter gt The current setting is displayed 3 Select CEE if the attached switch
221. s all ports LPVID 0 2 4094 Switch Option IBM IBM Virtual Fabric Mode IBM Virtual Fabric Mode bi ge IBM Unified Fabric Protocol Mode configuration i available Switch Independent Mode Note The following example sets the default values for FC and FCoE adapters only To set other adapters to their default settings you must use the utility for that specific protocol To set Emulex adapters to their default settings 1 2 From the Device Manager screen Figure 12 2 select the adapter whose default settings you want to change and press lt Enter gt From the Emulex Adapter Configuration Main Menu Figure 12 3 select Set Emulex Adapter to Default Settings and press lt Enter gt Set Emulex Adapter to Default Settings 0Ce10202 FM Node Name 20000000C95875857 Set Adapter Defauits eg 00 Bus 04 Dev 00 Func 02 VlanID 0002 Set Adapter Defaults ancel Set Defauits Figure 12 22 Set Adapter Defaults Note This will set the adapter to the FCoE driver default settings only Select Set Adapter Defaults and press lt Enter gt to set the adapter back to its default values The Emulex Adapter Configuration Main Menu is displayed From the Emulex Adapter Configuration Main Menu select Back to Display Adapters and RECONNECT DEVICES to complete configuration or select another configuration option Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SXC EMULEX 12 Configuring UEFI for FCoE 177
222. s option discovers iSNS servers configured on the network using DHCP Note If you leave iSNS Server Discovery via DHCP disabled default you must manually configure the iSNS server To enable or disable iSNS server discovery using DHCP 1 From the iSNS Configuration screen Figure 11 20 select iSNS Server Discovery via DHCP and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A xs 11 Configuring UEFI for iSCSI 152 gt lt EMULEX Adding and Configuring Targets iSNS Discovery Mode Disable iSNS Server IP 2 iSNS TCP Port 3205 Save Changes Available Servers Figure 11 20 iSNS Server Discovery via DHCP Screen 2 Select either Enable or Disable and press lt Enter gt 3 Select Save Changes and press lt Enter gt to save the current settings Configuring the iSNS Server IP Address and TCP Port Number Manually An iSNS server can also be configured manually by entering the server IP address and the TCP port Only one iSNS server can be configured at present Note This option is only available when the iSNS Server Discovery via DHCP option is disabled To add an iSNS server manually 1 From the iSNS Configuration screen Figure 11 21 select iSNS Server IP and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A c 11 Configuring UEFI for iSCSI 153 gt lt EMULEX Adding and Configuring Targets Port1 HP CN1100E Dual
223. scription of Parameters lt ipaddress gt Replace this parameter with a valid Pv4 address in dotted decimal notation This is a mandatory field Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX lt protocol gt Appendix A Configuring iSCSI through a DHCP Server using Vendor Specific Option 43 186 Format of Vendor Specific Option 43 Replace this parameter with a decimal number indicating the TCP port The default TCP port is 3260 lt iscsi port number gt Replace this parameter with a decimal number ranging from 1 to 65535 inclusive It is an optional field lt lun gt This parameter is a hexadecimal representation of logical unit number of the boot device It is an optional field If not provided LUN 0 is assumed to be the boot LUN It is an 8 byte number which must be specified as a hexadecimal number consisting of 16 digits with an appropriate number of 0 s padded to the left if required lt target name gt Replace this parameter with a valid iSCSI target ign name of up to 223 characters This is a mandatory field Example iscsi 010 010 010 001 0 3260 0 iqn 1992 08 com netap sn 151729740 The above example specifies the following Target IP address 010 010 010 001 Target protocol 0 Target TCP port 3260 Target boot LUN 0 Target iqn name iqn 1992 08 com netap sn 151729740 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A A
224. snnedtan 148 Deleting a Target se accagicsaeccndahinasectsgnactuatewiatiteantselsterccsatanieeuuedsateenesads 148 Configuring LUNS ccccvreceevianveraterecnvenseestaadens a i a a a a enaa 149 ISNS Configuratio N secreten nurini R EE en EED AREE E EPEE AAEE AEREE A ETETEN 150 Enabling ISNS DISCOVETY i enirar aandcmeler east anew tdea dined a n hera iaido raai 151 Enabling ISNS Server Discovery via DHCP ssssssesssssesssrererrrrrrerrrerrrrrerrerrreree 151 Configuring the iSNS Server IP Address and TCP Port Number Manually 68 152 Discovering Targets Using the ISNS Server ccc cece enn teed 154 Erasing the Configuration ssssssssssnunnnnnnnnnsnannunnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 155 12 Configuring UEFI for FCOE ssssssssnnnnnnnnnssnunnnnnnnnnnnnnnnununnnnnnnnnnnnnnnnn 156 OVE IWIEW ohcicacteneracatdamesaaneecnineicebccicesacceswemeanamunscteteauman times EAEE 156 Navigating the Emulex FCoE Configuration Utility ccccccccseeecceeeccceeceeensaeenes 156 Starting the Emulex FCoE Configuration Utility ccccccseeesseeeesceeeseeeesueeesaeeeas 157 Updating Firmware and Boot Code ssssssssssssussnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnnn 158 Enabling an Adapter to Boot from SAN sssssssssusnnnnnnnnnnnnnunnnnnnnnnnnnnnnnnnnnnnn 158 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DE EMULEX Table of Contents Configuring DCBX Mode sssssssssssnnnnnnnnnnnnunnnnnnn
225. st name linux test filename pxelinux 0 This sets up a DNS server that will assign IP Address 192 168 1 60 to the client machine that has MAC Address 00 00 C9 5B 75 A8 assigned to a PXE capable NIC The only thing that needs to be changed in the above is the MAC Address to match that of the NIC in the client box The IP address that follows the next server option should be the IP address of the tftp server root bglinux156 service dhcpd restart Shutting down dhcpd OK Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A o Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot 191 gt EMULEX Linux and Citrix PXE Server Remote Installation Procedure Starting dhcpd OK PXE Boot Server Configuration root bglinux156 rpm qa grep system config netboot system config netboot cmd 0 1 45 1 1 e15 system config netboot 0 1 45 1 1 e15 Copying Files to the TFTP Server with the Graphical Version of the Network Booting Tool Copy the files necessary to start the installation to the TFTP server to enable them to be found when the client requests them Run the Network Booting Tool on the NFS FTP or HTTP server A separate PXE server is not necessary To use the graphical version of the Network Booting Tool you must be running the X Window System have root privileges and have the redhat config netboot RPM package install
226. t any notice Emulex assumes no responsibility for its use nor for any infringements of patents or other rights of third parties that may result Periodic changes are made to information contained herein although these changes will be incorporated into new editions of this manual Emulex disclaims any undertaking to give notice of such changes Emulex 3333 Susan Street Costa Mesa CA 92626 Note References to OCe11100 series products also apply to OCe11100R series products Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX Table of Contents Table of Contents 3 List of FIQUEGS aspirasina rnanis aa a i a kaia aiia 10 List OF Tabl e S sinisiin annaa EN EENE ai aki 14 1 INCFODUCHON viiscicctecsinctntndsstsntecderasinadsstgenieeaseseeennenisisetaeneeenseRERnaN Ra 15 OVEIVICW cinsore nnana En AE NDEN ana 15 AbDbDreviatiONn siiscisccssscscscctccstsctscsssstesrssssstessnesassesasessasenaieensssansasassanansas 16 2 Configuring PXE Boot for the NIC Protocol sssssssnsssnnnnnnnnnnnnnnnnnnnnnnnnnnn 20 gigi rere a a Te eer rr re rrr 20 PXE Boot PrOCesS siiissscccssctsessciiscsseasadssieisrasesiasiecinedendsadsiancssectinnenaeacens 20 Remotely Installing with PXE for Windows Server 2008 2008 R2 and 2012 somna a E ERER 22 Remotely Installing with PXE for Linux and Citrix Servers s sssssssssssnnnnnnnnnnnnnnn 22 Using the PXESSISCE Utility orrrsornisinan nassaan aaa 23 Navigating the PXES
227. t provides extensive documentation on deploying its operating systems for remote installations and different setups may be required depending on your individual implementation Microsoft provides step by step guides for its Windows Deployment Services for configuring your server adding images and installing an operating system It also includes instructions for more advanced tasks like creating multicast transmissions creating custom images and performing an unattended installation For detailed information on deploying and managing remote installations on Windows Server 2008 Windows Server 2008 R2 and Windows Server 2012 see the Microsoft website and visit Microsoft TechNet Search on the bulleted terms above to access Microsoft s wide ranging documentation on these subjects Remotely Installing with PXE for Linux and Citrix Servers Linux allows for PXE installation over a network using the NFS TFTP or HTTP protocols If the system to be installed contains an Emulex NIC or UCNA with PXE Boot support it can be configured to boot from files on another networked system rather than local media The Linux distributions provide extensive documentation on deploying and managing remote installations of the Linux operating system via PXE See your appropriate distribution s documentation for instructions on how to deploy a PXE installation over your network Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Config
228. t select Erase Configuration to clear out existing IQN data if you purchase a different or subsequent license for the adapter To erase a controller configuration 1 From the Controller Configuration menu select Erase Configuration and press lt Enter gt Controller Configuration Menu Emulex OneConnect 0Ce11102 IM 2 port PCIe 10GbE Erase the Current CNA Configuration and Restore the Default iSCSI Initiator Name iqn 1990 0 com emulex Configuration 00 00 c9 be ce 41 Boot Support lt Enable gt Existing Configuration will be overwritten by Default Values for both ports Press ENTER to Continue ESC to Abort iSCSI Target Configuration Tl Move Highlight lt Enter gt Select Entry Figure 11 24 Erase Configuration Screen A warning message appears asking for confirmation 2 Press lt Enter gt to erase the configuration or press lt Esc gt to abort the operation When the controller configuration is erased the Controller Configuration menu is displayed Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX 12 Configuring UEFI for FCoE 156 Overview 12 Configuring UEFI for FCoE Note If you have several adapters in your system the UEFI system firmware or boot code uses the highest version driver installed on any of the adapters Adapters with older versions of EFIBoot are managed by the more recent version but only as long as the adapter with the most recent version is in the s
229. t support multichannel Multichannel Configuration Multichannel provides the ability to configure multiple PCI functions or I O channels for each physical OneConnect port Note Setting up IBM Virtual Fabric or UFP multichannel depends on cooperation with adjacent switches Note Refer to Configuring Universal Multichannel on page 31 for information on configuring multichannel when Switch Independent mode is enabled To view the configuration screen 1 From Port Selection Menu Figure 2 4 select the port you want to configure and press lt Enter gt The configuration screen appears When configuring multichannel on adapters that support IBM Virtual Fabric and UFP modes the configuration screen will be dependent on which Multichannel Mode has been selected Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol SG EMULEX Using the PXESelect Utility Note For illustration purposes the screen displays in this section are for a system with IBM Virtual Fabric Mode enabled Controller 0 Port 0 Bus 16 Dev 00 Firmware Version v4 6 145 0 Port Speed 10 Gbps Physical Link Status Link Up PXE Boot Support Enabled Type Bandwidth SUID LPVID Disabled Logical SR IOV 1 100 2 4094 2 4094 Link Min Max Status NIC NVA z N A 5c f3 fc 5e 05 50 Link Up Disabled iSCSI N A z N A N A 5c f3 fc Se 05 51 N A Disabled NIC NYA z NVA 5c f3 fc S5e 05 53 L
230. tab file all on one line share F nfs o ro anon 0 d install server directory install dir path b Verify that the nfsd daemon is running or start the nfsd daemon e If the install server is running the current Solaris release or compatible version type the following command sves l svc network nfs server default o If the nfsd daemon is online continue to step c Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 3 Configuring Boot from SAN for the FCoE Protocol 45 SC EMULEX Ea o If the nfsd daemon is not online start it Type the following command svcadm enable svc network nfs server e If the install server is running the Solaris 9 operating system or compatible version type the following command ps ef grep nfsd o If the nfsd daemon is running continue to step c o If the nfsd daemon is not running start it etc init d nfs server start c Share the install server shareall 7 Change directories to root cd 8 Eject the Solaris DVD 9 Optional Patch the files that are located in the miniroot on the net install image that was created by setup_install_server Patching a file might be necessary if a boot image has problems For more information see the Sun Microsystems Solaris 10 10 08 Installation Guide Installing Solaris by Migrating an Image from a Local SCSI Disk To install Solaris by migrating an image from a local SCSI disk 1 Type the followin
231. ters e EFIFCScanLevel NVRAM Targets Boot scan sets the EFIFCScanLevel environment variable to inform the driver to configure only targets in the NVRAM boot table e EFIFCScanLevel Discovered Targets Boot scan sets the EFIScanLevel environment variable to inform the driver to configure all available targets on the SAN To change the boot target scan method 1 From the Device Manager screen Figure 12 2 select the adapter whose boot target scan method you want to change and press lt Enter gt 2 From the Emulex Adapter Configuration Main Menu Figure 12 3 select Configure HBA Parameters and press lt Enter gt The Configure HBA Parameters is displayed 3 From the Configure HBA Parameters menu select Boot Target Scan Method and press lt Enter gt The Boot Target Scan Method menu is displayed gure HBA Parameters OCel0i02 FM Node Name 20000000C95875857 Selects the method to onfigure HBA Parameters use to scan for Boot Targets Discard Changes NVRAM Targets ommit Changes hotatetebatatatatetatadatatebatabahetebenateteiadetetatatateteteheiebenenatanel Hers only LUNS opology Selection F izre saved to the iz Non Volatile j Access Memory PLOGI Retry Timer Force Link Speed a NE ee ee eS a fers all devices aximum Luns Target oot Target Scan Method the FC port Discovery can take a long time on Figure 12 20 Configure HBA Parameters Boot Target Scan Method Menu 4 Select a
232. the client system the initiator initiates disk I O It communicates with the target and the target serves the initiator by providing resources to the initiator Once you configure your iSCSI initiator and verified that your network interface is working you can log into your target to establish your connection To do this you must e Perform a login to the target adding a target e Ping a target and verify that you can connect to it e Reboot the system Adding iSCSI Targets Once the initiator has been configured you need a process that shows you how to make an iSCSI target available to that initiator host The discovery process presents an initiator with a list of available targets The discovery methods used for discovering targets are e SendTargets discovery e Manually configuring targets With the iSCSISelect utility you can easily configure an iSCSI target by selecting and enabling values on the Add Ping iSCSI Target menu From this menu you can configure the target and perform a login to the target to establish an iSCSI network connection Before you begin the login session gather the following information e iSCSI target name only for manual configuration The target name that you are adding The iSCSI target name is not required if you are using SendTargets discovery It is required only for manually configured targets This name should be known to you based on how you configured your iSCSI target For more information se
233. the system On the iSCSI Target Configuration screen select Add Targets and press lt Enter gt The Add Ping iSCSI Target screen is displayed iSCSI Target Name IP Version iSCSI Target IP Address TCP Port Number BladeEngine Port Number Boot Target ISID Qualifier Header Digest Data Digest Authentication Method Edit Ping Target ign 1984 05 emulex tgtO IPV4 172 40 46 150 3260 1 lt No gt FA lt No gt lt No gt lt None gt Login Ping Save Login Advanced Properties tl Move Highlight lt Enter gt Select Entry Esc Exit Figure 11 9 Add Ping iSCSI Target Screen Enter the target IP address and TCP port number the default target port number is For a boot target use the default setting No even if you want to enable the target as a boot target For more information about the boot target see Setting Up a Basic Note You must enable the Boot Target option after you add the target via Change the ISID qualifier value if necessary A unique ISID value is necessary if you connect dual sessions to the same target portal group Enter a number up to 65535 For more information see Setting an ISID Value on page 92 5 3260 6 iSCSI Boot Configuration on page 77 SendTargets 7 8 Boot for NIC iSCSI and FCoE Protocols User Manual Select Yes from the Header Digest drop down menu if you want to enable header digest When set to Yes and the iSCSI initiator is set accordingly
234. the system boots SUSE Linux Enterprise Server 11 SP1 now shows in the system Start Options screen Start Options SUSE Linux Enterprise Server 11 SPI Device Path CD DUD Ron HD 1 GPT ES24A62A 2A4A 4 Hard Disk 8 69E 83D9 ESCC34B93F 15 Ox Hard Disk 1 22 0x620B8 ef i SuSE el Hard Disk 3 ilo efi Hard Disk 2 Hard Disk 4 Floppy Disk USB Storage Legacy Only PXE Network Vindows Boot Manager full shell iSCSI Figure D 2 UEFI FCoE Start Options Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A Appendix D Example for Installing and Booting UEFI FCoE 212 gt G EMULEX Appendix E Loading and Unloading UEFIBoot from the UEFI Shell Loading UEFIBoot from the UEFI Shell Appendix E Loading and Unloading UEFIBoot from the UEFI Shell Loading UEFIBoot from the UEFI Shell The UEFI boot code is distributed with the firmware in a UFI file This file may be downloaded to a NIC iSCSI or FCoE adapter through the HII interface in the NIC UFFI code Unloading UEFIBoot from the UEFI Shell To unload UEFIBoot 1 View Emulex driver handle information by typing drivers and pressing lt Enter gt at the shell prompt A list of drivers is displayed 00000000A 00000000A 00000000A 00000000A 00000001 00000000A 00000000A 00000000A 0000000A 00000000A 00000000A 00000000A 00000000A 00000000A 00000000A 00000000A 0000000A 7 11C 00050212 11E 00050212 122 000221A5 126 000100AF 143 030A0
235. tility for x86 and x64 Architectures 60 gt G EMULEX Configuring Boot Devices Bust OZ Devt 00 Funct 02 Firmuare Version 2 702 485 1 BIOS Enabled 10000000C95B87791 Node Name 20000000C95B 7791 Ulan ID 0001 DCBX mode CEE node List of Saved Boot Devices Unused 7000000 WWPN 0090000090 90000000 700 Primary Unused 000000 WWPN 00000000 90000000 700 Unused 000000 WWPN 00000000 90000000 700 Unused 7080000 WWPN 00906000 90000000 00 Unused 7080090 WWPN 00908000 90000000 700 Unused 7080000 WUUPN 00000000 00000000 00 Unused 000000 WWPN 00000000 90000000 700 Unused 7000000 WWPN 00000000 90000000 700 Figure 5 5 List of Saved Boot Devices Screen ONO Uh ON a 2 Select a boot entry and press lt Enter gt A screen similar to Figure 5 6 is displayed 01 0Ce10100 Bust 02 Devitt 00 Funct 02 Mem Base CE2C0000 Firmware Version 2 702 485 1 BIOS Enabledt Port Name 10000000C95B7791 Node Name Z20000000C95B7791 Ulan ID 0001 DCBX made CEE mode Clear selected boot entry DID 0203E4 WWPN 22000004 CF926A793 SEAGATE 51T318452FC DID 0OZO3EF WWPN Z2000004 CF9Z6A8Z SEAGATE 1T318452FC DID 1A14BS WWPN 21000011 C6800B4A 3 SEAGATE ST373554FC DID 1A14B6 WWPN 21000011 C6800B3F SEAGATE ST373554FC DID 1A14B9 WWPN 21000011 C68009A8 SEAGATE T373554FC DID 1A14BA WWPN 21000011 C6800A69 s SEAGATE 51373554FC DID 1A14BC WWPN 21000011 C6800A5D SEAGATE T373554FC Figure 5 6 Device Selection List Exam
236. tion option Configuring Adapter Parameters Changing the PLOGI Retry Timer This option allows you to set the interval for the PLOGI retry timer This option is especially useful for Tachyon based RAID arrays Under very rare occasions a Tachyon based RAID array resets itself and the port goes offline temporarily in the loop When the port comes to life the PLOGI retry interval scans the loop to discover this device You can choose e Disable Default e 50 Msec e 100 Msec e 200 Msec To change timer values 1 From the Device Manager screen Figure 12 2 select the adapter to configure and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt G EMULEX Configuring Adapter Parameters From the Emulex Adapter Configuration Main Menu Figure 12 3 select Configure HBA Parameters and press lt Enter gt The Configure HBA Parameters screen is displayed From the Configure HBA Parameters screen select PLOGI Retry Timer and press lt Enter gt The PLOGI Retry Timer menu is displayed OCe10102 FM Node Name onfigure HBA Parameters 20000000C9587557 PLOGI Retry Timer Discard Changes ommit Changes opology Selection PLOGI Retry Timer Force Link Speed onfigure Boot Parameters aximum Luns Targec 256 oot Target Scan Method lt Boot Path Discovered Targets gt Figure 12 18 PLOGI Retry Timer Select a retry timer option and press lt Enter gt The scree
237. tocol Selection Menu jcc ccieceourkdtecad aie cacdivaerd dxedad zane idenniaes 209 Network Device Selection LISting ccccccccecsee esses eeaeeesaeteseetenentenenes 209 NFS Server IP Address Dialog BOX wicewieneeceeviwvineseisssseraweivsneerineaases 209 Server Directory Dialog BOX cccccccee cece cee e este e rene eae ee saeteeneneenaneas 210 Starting Script csscccnrecissattenceteyaidegastiahnlescencaeenenaetiabssiaaqeeessbarsenciien 210 Driver Update Confirmation ssssssssssrrrrrerrrerrrrrrrrrrrrrrtrrrrrrrrrerere 210 PSNCEENOM Gil diane eous bicare ne niceteweeneasotere hers giere cues stevesacelelaseanesnaceees 211 UEFI PEGE Start Opt ONG teccic cacy nrcrscecmericesscatsencrevecibiaewsoaipenenweane 212 Driver LISt N esos reriirrrisserirssiien iire iren E EEE EEOSE REEERE REEERE EAEE a eamenees 213 P009697 01A Rev A 13 gt G EMULEX List of Tables 14 List of Tables Table 2 1 Advanced Mode Capabilities by Operating System cece cece e eee eae 26 Table 2 2 PXE Boot Parameter Default ValU S cccceceee eects eee ee eae ee eaeeeean en enn ees 36 Table 5 1 Valid AL PA ValuGG sciceciuceeeiiectirardaesimeniiaesiieweed EEEE EA 67 Table 5 2 Default Adapter Boot Parameter ValUGS ccecccee sees es eeeereeee nents renee ns 74 Table 6 1 Utilities that Install Update and Enable Boot Code cceeeeeeee eee eee 76 Table 10 1 Advanced Mode Capabilities by Operating System cceeeee
238. ual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 32 gt EMULEX Using the PXESelect Utility e If your system does not support some of the multichannel options those unavailable options show as N A on the MultiChannel Configuration screen 2 From the MultiChannel Configuration screen you can perform the following tasks e Configure PXE boot support see Configuring PXE Boot Support on page 28 for instructions e Configure PXE VLAN ID Priority see Configuring the PXE VLAN ID and Priority on page 29 for instructions e Identify ports see Physically Identifying the Port on page 30 for instructions e Erase the port and adapter configuration see Erasing Ports and Controller Configuration on page 30 for instructions e Configure the minimum and maximum bandwidth for each channel e Configure the LPVID for each channel Note Your adapter or system may not support all multichannel options Configuring Minimum and Maximum Bandwidth To configure bandwidth 1 On the configuration screen use the lt Tab gt key to select Minimum Bandwidth or Maximum Bandwidth e The Minimum Bandwidth value is the least amount of bandwidth that the function can provide It is represented as a percentage The Minimum Bandwidth value must be less than or equal to the Maximum Bandwidth value The total of the Minimum Bandwidth values for all enabled functions on that port must be equal to 100 e Th
239. ue must be changed see Booting from SAN for iSCSI MPIO on page 53 Enabling CHAP Authentication The iSCS Select utility uses CHAP to authenticate initiators and targets for added network security By using a challenge response security mechanism CHAP periodically verifies the initiator s identity This authentication method depends on a secret known only to the initiator and the target Although the authentication can be one way you can negotiate CHAP in both directions with the help of the same secret set for mutual authentication You must make sure however that what you configure on the target side matches the initiator side The iSCSISelect utility supports both one way and mutual authentication Authenticating One Way CHAP With one way CHAP authentication the target authenticates the initiator Use one way CHAP authentication for a one way challenge response security method To enable one way CHAP authentication 1 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted 2 Select Controller Configuration A list of controllers is displayed 3 Select a controller and press lt Enter gt The Controller Configuration menu is displayed 4 From the Controller Configuration menu select iSCSI Target Configuration and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 9 Configuring and Managing iSCSI Targets with the iSCSISelect Utility 903 SG EMULEX Managing a
240. ufs Nunber of PCI UFs to initialize max 16 uint msix Enable and disable the MSIx By default HSIx is enabled Cuint multi_rxq Multi Rx Queue support Enabled by default uint Figure C 17 Driver Update Confirmation Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A SXC EMULEX Appendix D Example for Installing and Booting UEFI FCoE 211 Appendix D Example for Installing and Booting UEFI FCoE The following steps use the Linux SLES operating system as an example 1 Boot to UEFI linux from DVD 2 Select UEFI boot from the BIOS boot manager or boot to shell and execute efi boot elilo efi from removable media Follow normal boot instructions from YaST me oO During the Installation Settings select Partitioning then select Custom partitioning for experts In SystemViews select a hard disk Select the Partitions tab Delete any old partitions on the disk To create a GPT disklabel UEFI does not support booting from disks with an MS DOS partition table click Expert above the Accept button 9 Create a partition table and check GPT required for UEFI boot Sm SG Expert Partitioner p 4 r System View Hard Disk dev sdd 2 krux Qvermew Parttons Used Devices eS Hard Desks MEPE Sge F En type FS Type Label Mourt Poirt x 1956 11 M6 F WingS FAT32 LBA FAT boot efi J RAID 4 0068 F Linux swap Swap swap chime Manage 29 9868 F Linux native Ext3 1 EJ Crypt Files i De
241. ur PXE boot client s Ethernet card with a prefix of 01 The MAC address should be separated with dashes instead of colons In this example the client looks for the following configuration file names and uses the first one it finds 01 00 00 C9 5B 75 A8 COA8013C COA8013 COA801 COA80 COA8 COA Co Cc default Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A gt EMULEX Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot Linux and Citrix PXE Server Remote Installation Procedure 7 The default file s contents should look similar to the following prompt 1 default linux timeout 100 label linux kernel vmlinuz append initrd initrd img ramdisk_size 9216 noapic acpi off PXE Server NFS Server Configuration Script root bglinux156 root bglinux156 root bglinux156 root bglinux156 directory to root bglinux156 root bglinux156 root bglinux156 root bglinux156 1 Restart NFS Services root bglinux156 Stopping portmap Starting portmap wo mkdir work mount 10 192 194 110 work mnt cd mnt cp r rhel5564 work copy the entire rk cd work rhel5564 cp r images tftpboot linux install exportfs a etc re d init d portmap restart OK OK root bglinux156 etc rc d init d nfslock restart Stopping NFS locking OK Stopping NFS statd OK Starting NFS statd
242. ur controllers are displayed when you start the utility For example Press lt Ctrl gt lt P gt for PXESelect TM Utility Controller 0 Port 0 Base OxFCE60000 at Bus 05 Dev 00 Fun 00 Controller 0 Port 1 Base OxFCEAO000 at Bus 05 Dev 00 Fun 01 Controller 1 Port 0 Base OxFC920000 at Bus 01 Dev 00 Fun 00 Controller 1 Port 1 Base OxFC960000 at Bus 01 Dev 00 Fun 01 Initializing Done The PXE Configuration menu appears after the boot BIOS initializes to begin your PXE configuration Note A UEFI capable system typically does not display the prompt for running the PXESelect utility unless it is configured for legacy booting See your system configuration manual for information on performing a legacy boot All configuration that can be performed in the PXESelect utility can instead be performed in the UEFI configuration utility See chapter 10 Configuring UEFI for Ethernet on page 102 for more information Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 2 Configuring PXE Boot for the NIC Protocol 24 gt C EMULEX Using the PXESelect Utility Setting Up a PXE Bootable Network After the PXE boot BIOS initializes you can use the PXESelect utility to set up a PXE bootable network by configuring your controllers To configure controllers for PXE boot 1 At the Controller Selection Menu use the lt Tab gt key to select the controller you want to configure and press lt Enter gt Controller 0 Bus 02
243. ure SRIOV Screen 1 Select the current setting for a particular NIC function and a drop down menu appears 2 From the drop down menu select Enable or Disable and press lt Enter gt 3 When you are finished press lt Esc gt to return to the Controller Configuration screen Saving the Current Configuration To save the configuration changes on the Controller Configuration screen select Save Current Configurations and press lt Enter gt Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 10 Configuring UEFI for Ethernet 115 gt C EMULEX Using the Emulex NIC Configuration Utility Configuring Universal Multichannel Note Universal multichannel is only available on Emulex OneConnect OCe11100 series UCNAs Note If your adapter has Multichannel Mode enabled and also supports IBM Virtual Fabric Mode or IBM Unified Fabric Protocol Mode refer to Configuring Multichannel for IBM Adapters on page 122 for additional information If Multichannel Mode is disabled or not supported on the adapter refer to Configuring the Controller When Multichannel is Disabled or Not Supported on page 112 UMC provides the ability to configure multiple PCI functions or I O channels for each OneConnect port For additional information on UMC support see the Emulex Universal Multichannel Reference Guide Note When UMC is enabled you must configure the multichannel settings minimum and maximum bandwidths for iSCSI a
244. ure the iSCSI initiator name from the iSCSI Initiator Configuration screen Note When installing Microsoft software iSCSI initiator service the iSCSI initiator name for OneConnect will change and any IQN name previously configured through the iSCSISelect utility will be overridden Though this will not affect existing boot sessions and persistent sessions new target logins may fail because the new IQN name may not match the incoming initiator IQN names configured on the target To avoid this situation after installing Microsoft software you must rename the IQN name to the previous IQN name you had configured To configure the iSCSI initiator name 1 Log into the iSCSISelect utility by pressing lt Ctrl S gt when prompted After the BIOS initializes the iSCSI Initiator Configuration screen appears 2 Set or change the iSCSI initiator name from this screen iSCSI Initiator Name ign 2001 05 com serveren Save Controller Configuration Figure 8 1 iSCSI Initiator Configuration Screen Note If there are multiple controllers in your system your iSCSI Initiator name may be different for each controller If this happens an error message Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A aw 8 Configuring and Managing the iSCSI Initiator with the iSCS Select Utility 81 gt G EMULEX Selecting a Controller indicates an Initiator iSCSI Name mismatch You must save a new initiator name on this menu so that th
245. uring PXE Boot for the NIC Protocol 23 gt C EMULEX Using the PXESelect Utility For remote installation with PXE a network driver for the Emulex UCNA must be part of the client s installation image on the server Your current Linux distribution may or may not include network drivers for Emulex UCNAs If they do the driver may need to be added to your operating system s installation image or added during installation See your appropriate distribution s documentation for instructions on how to add drivers during installation Using the PXESelect Utility Navigating the PXESelect Utility Use the following methods to navigate the PXESelect utility e Press the up down arrows on your keyboard to move through and select menu options or configuration fields When multiple adapters are listed use the up down arrows to scroll to the additional adapters e Press lt Tab gt to move to the next field or to select a row in a configuration screen Use lt Shift gt lt Tab gt to move to the previous field e Press lt Enter gt to accept a selection select a menu option or to change a configuration default e Press lt Esc gt to return to the previous menu or page cancel a selection or dialog box or exit the utility Running the PXESelect Utility To run the PXESelect utility start or restart your computer When prompted hold down lt Ctrl gt and press lt P gt If you are running the PXESelect utility with multiple controllers all yo
246. vice Mapper a NFS 7 E Unused Device t Settings eA ace M a tn ries met Figure D 1 Partitions Tab Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A DG EMULEX 10 To add an UEFI system partition VFAT or FAT click Add 11 Select a custom size 100 400MB depending on what EFI driver and utilities you want to store on the UEFI system partition In general using 200 MB is sufficient if the plug in card detail for UEFI system partition is unknown 12 In the Formatting options dialog box select Format Partition gt File system gt FAT 13 Under Mounting options select boot efi and click Finish The boot drive now has a GPT disk label that contains a FAT EFI boot partition 14 Perform the remainder of the partitioning as with any Linux installation The remainder of the installation is not unique to UEFI for example add a swap partition and an EXT3 partition for root 15 Once the installation is completed view the partitions using the parted 1 command Information similar to the following is displayed parted 1 Model SEAGATE ST336754FC scsi Disk dev sdd 36 7GB Sector size logical physical 512B 512B Partition Table gpt Number Start End Size File system Name Flags 1 17 4kB 206MB 206MB fatl16 PEIMALY qo r or r r po ee He eoi nsftres 2 206MB 4499MB 4294MB linux swap primary 5557 4 1 3 4499MB 31 36GB 26 8GB ext3 primary gz pps HH OR a i 16 When
247. w Name 00000000 00000000 VLANID 000 Sw Name 00000000 00000000 00000000 00000000 VLANID 000 Sw Name 00000000 00000000 00000000 00000000 VLANID 000 Sw Name 00000000 00000000 00000000 00000000 VLANID 000 Sw Name 00000000 00000000 00000000 00000000 UNSD VLANID 000 Sw Name 00000000 00000000 00000000 00000000 00000000 00000000 Figure 12 6 CEE Record Selection List Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 12 Configuring UEFI for FCoE 162 gt EMULEX Configuring CEE FCF Parameters 3 Select the CEE FCF record to modify and press lt Enter gt The current record information is displayed onfigure CEE FCF Parameters Set Record State et Record State lt UNUSED gt nrer VLAN ID 0 Enter Switch Name Low 00000000 Enter Switch Name Hi 00000000 Enter Fabric Name Low 00000000 Enter Fabric Name Hi 00000000 Discard Changes ommit Changes elect From FCF Table Figure 12 7 CEE FCF Record Information 4 Change the record information as needed e Set Record State can be set to unused active or boot e VLAN ID must be a three digit hexadecimal number e Switch Name Low Enter the low bits of the FC switch s WWN to which to connect This must be an 8 digit hexadecimal number e Switch Name Hi Enter the high bits of the FC switch s WWN to which to connect This must be an 8 digit hexadecimal number e Fabric Name Low Enter the low bits of the
248. x cfg 8 Go to tftpboot pxelinux cfg and open the file COA8013C The C0A8013C file is created when you assign the client IP using system config netboot This is the hexadecimal address of the IP assigned to the client NIC It is 192 168 1 60 in the example in Figure B 4 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A o Appendix B Example for Installing and Configuring Linux or Citrix for PXE Boot and UEFI Boot 195 gt EMULEX Linux and Citrix PXE Server Remote Installation Procedure Enabling the PXE Client with a PXE enabled Adapter The PXE client must have a PXE enabled adapter 1 Power on the PXE client 2 Press lt F12 gt to enable network boot Pressing lt F12 gt accesses the DHCP server IP and the Boot Linux image LIENT MAC ADDR 00 00 CS 5B 37 6C GUID 44454C4C 4D00 104C 804C B9C04F313253 LIENT IP 192 168 65 200 MASK 255 255 255 0 DHCP IP 192 168 65 100 PXELINUX 3 10 2005 08 24 Copyright C 1994 2005 H Peter Anvin UNDI data segment at 00098D10 UNDI data segment size 2430 UNDI code segment at 0009B140 UNDI code segment size 2990 PXE entry point found we hope at 9B14 0109 My IP addresswseems to be COA841C8 192 168 65 200 ip 192 168 65 200 192 168 65 100 0 0 0 0 255 255 255 0 TETP prefix to load pxelinux cfg 01 00 00 c9 5b 37 6c to load pxelinux cfg COAs41C8 to load pxelinux cfg CoAs4ic to load pxelinux cfg COA841 to load pxelinux cfg COAs4 to load pxelinux cfg C
249. ystem The latest firmware and boot code must be installed on each adapter in the system to ensure that each adapter runs the latest firmware and boot code Overview UEFIBoot supports Single topology Only Fabric point to point is supported EFI protocols All applicable UEFI 2 3 driver protocols are supported Operating systems All UEFI aware operating systems are supported Multi Device path Fibre SCSI device path is selectable through the driver configuration application Multi initiators Up to 256 ports are supported Multi boot Eight targets are selectable through the driver configuration application Multi LUNs Up to 4096 LUNs are supported Multi utility Setup and firmware updates are supported The Emulex FCoE UEFIboot is loaded from flash into system memory To verify that the Emulex UEFIBoot driver is loaded enter the EFI Shell type drivers and then press lt Enter gt Navigating the Emulex FCoE Configuration Utility The Emulex FCoE configuration utility has menus and configuration screens Use the following methods to navigate them Press the up down arrows on your keyboard to move through and select menu options or configuration fields When multiple adapters are listed use the up down arrows to scroll to the additional adapters Press the lt gt lt gt or lt Enter gt keys to change numeric values Press lt Enter gt to select a menu option to select a row in a configuratio
250. ystem supports Multi boot BBS the local boot disk drive C is the first entry in Multi boot on the system BIOS setup menu The list of entries is determined by the list of configured boot entries in the BIOS utility For example Adapter 1 boot_entry0 boot_entryl Adapter 2 boot_entry2 boot_entry3 Boot for NIC iSCSI and FCoE Protocols User Manual P009697 01A Rev A 5 Using the FCoE Boot BIOS Utility for x86 and x64 Architectures 74 gt G EMULEX Resetting to Default Values The order of boot entries exported to Multi boot BBS is boot_entry0 boot_entryl boot_entry2 and boot_entry3 However Multi boot allows changing the boot order in the server BIOS which allows any disk to become the C drive Resetting to Default Values The BIOS utility enables you to reset BIOS boot parameters to their factory default settings These defaults are listed in Table 5 2 Table 5 2 Default Adapter Boot Parameter Values Parameter Default Value Valid Values Boot from SAN Disabled Enabled Disabled AL_PA Value 0x00 Fibre See Table 5 1 Valid AL_PA Values EDD 3 0 Disabled EDD 2 1 Enabled EDD 3 0 Disabled EDD 2 1 PLOGI Retry Timer Disabled Disabled 50 msec 100 msec 200 msec Spinup Delay Disabled Enabled Disabled Auto Scan Disabled Enabled Disabled Start Unit Disabled Enabled Disabled Environmental Variable Disabled Enabled Disabled Auto Boot Sector Disabled Enabled Disabled Note DCBX mode s

Download Pdf Manuals

image

Related Search

Related Contents

1 - 株式会社キューヘン  Eldningsinstruktion och bruksanvisning Cronspisen 100, 200, 500  Monitoring du carnet d`ordres : Mode d`emploi  Linux® Troubleshooting Bible  lucRezia - lp14 - lp20 - lp30  to User Manual  Samsung Galaxy Tab E Felhasználói kézikönyv  Alaris® GH Syringe Pump  GUÍA DEL USUARIO    

Copyright © All rights reserved.
Failed to retrieve file