CLI setup and SAN Boot
This appendix describes the setup of the command-line interface (CLI) and provides extra information about the SAN Boot function.
Specifically, this appendix provides information about the following topics:
Command-line interface
The IBM Storwize V5000 Gen2 system has a powerful CLI, which offers even more functions than the graphical user interface (GUI). This section is not intended to be a detailed guide to the CLI because that topic is beyond the scope of this book. The basic configuration of the IBM Storwize V5000 Gen2 CLI is covered. Example commands are described. However, the CLI commands are the same in the IBM SAN Volume Controller/Storwize family, and more commands are available to manage internal storage. If a task completes in the GUI, the CLI command is always displayed in the details, as shown throughout this book.
Detailed CLI information is available at the IBM Storwize V5000 Gen2 web page under the command-line section, which is at the following address:
Basic setup
In the IBM Storwize V5000 Gen2 GUI, authentication is performed by using a user name and password. The CLI uses a Secure Shell (SSH) to connect from the host to the IIBM Storwize V5000 Gen2 system. Either a private and a public key pair or user name and password combination is necessary. The following steps are required to enable CLI access with SSH keys:
•A public key and a private key are generated together as a pair.
•A public key is uploaded to the IBM Storwize V5000 Gen2 system through the GUI.
•A client SSH tool must be configured to authenticate with the private key.
•A secure connection can be established between the client and the IBM Storwize V5000 Gen2.
Secure Shell is the communication vehicle between the management workstation and the IBM Storwize V5000 Gen2 system. The SSH client provides a secure environment from which to connect to a remote machine. It uses the principles of public and private keys for authentication. The system supports up to 32 interactive SSH sessions on the management IP address simultaneously. After 1 hour, a fixed SSH interactive session times out, which means that the SSH session is automatically closed. This session timeout limit is not configurable.
SSH keys are generated by the SSH client software. The SSH keys include a public key, which is uploaded and maintained by the clustered system, and a private key, which is kept private on the workstation that is running the SSH client. These keys authorize specific users to access the administration and service functions on the system. Each key pair is associated with a user-defined ID string that consists of up to 30 characters. Up to 100 keys can be stored on the system. New IDs and keys can be added, and unwanted IDs and keys can be deleted. To use the CLI, an SSH client must be installed on that system, the SSH key pair must be generated on the client system, and the client’s SSH public key must be stored on the IBM Storwize V5000 Gen2.
The SSH client that is used in this book is PuTTY. Also, a PuTTY key generator can be used to generate the private and public key pair. The PuTTY client can be downloaded from the following address at no cost:
Download the following tools:
•PuTTY SSH client: putty.exe
•PuTTY key generator: puttygen.exe
Generating a public and private key pair
To generate a public and private key pair, complete the following steps:
1. Start the PuTTY key generator to generate the public and private key pair (Figure A-1).
Figure A-1 PuTTY key generator
Ensure that the following options are used:
 – SSH-2 RSA
 – Number of bits in a generated key: 1024
2. Click Generate and move the cursor over the blank area to generate keys (Figure A-2).
Figure A-2 Generate keys
 
To generate keys: The blank area that is indicated by the message is the large blank rectangle on the GUI inside the section of the GUI that is labeled Key. Continue to move the mouse pointer over the blank area until the progress bar reaches the far right. This action generates random characters to create a unique key pair.
3. After the keys are generated, save them for later use. Click Save public key (Figure A-3).
Figure A-3 Save public key
4. You are prompted for a name (for example, pubkey) and a location for the public key (for example, C:Support UtilsPuTTY). Click Save.
Ensure that you record the name and location because the name and location of this SSH public key must be specified later.
 
Public key extension: By default, the PuTTY key generator saves the public key with no extension. Use the string “pub” for naming the public key, for example, superuser.pub, to easily differentiate the SSH public key from the SSH private key.
5. Click Save private key (Figure A-4).
Figure A-4 Save private key
6. You are prompted with a warning message (Figure A-5). Click Yes to save the private key without a passphrase.
Figure A-5 Confirm the security warning
7. When you are prompted, enter a name (for example, icat), select a secure place as the location, and click Save.
 
Key generator: The PuTTY key generator saves the private key with the PPK extension.
8. Close the PuTTY key generator.
Uploading the SSH public key to the IBM Storwize V5000 Gen2
After you create your SSH key pair, upload your SSH public key onto the IBM V5000 Gen2 system. Complete the following steps:
1. On the System Overview, click the Access functional icon and select Users in the GUI menu (Figure A-6).
Figure A-6 Click Users on the Access menu
2. Under User Groups, select All Users. Right-click the user name for which you want to upload the key and click Properties (Figure A-7).
Figure A-7 Superuser properties
3. To upload the public key, click Browse, and select the folder where you stored the public SSH key (Figure A-8).
Figure A-8 Select public key
4. Select your public key, and click Open (Figure A-9).
Figure A-9 Selection of the public SSH key
5. Click OK, as shown in Figure A-10. The key is uploaded.
Figure A-10 Select the public key
6. Check in the GUI whether the SSH key was successfully imported. See Figure A-11.
Figure A-11 SSH key was successfully imported
Configuring the SSH client
Before you can use the CLI, you must configure the SSH client:
1. Start PuTTY. The PuTTY Configuration window opens (Figure A-12).
Figure A-12 PuTTY
In the right pane, select SSH as the connection type. Under the “Close window on exit” section, select Only on clean exit, which ensures that if any connection errors occur, they are displayed on the user’s window, see Figure A-13.
Figure A-13 Select SSH + Only on clean exit
2. In the Category pane, on the left side of the PuTTY Configuration window (Figure A-14), click Connection → SSH to open the PuTTY Configuration window Options controlling SSH connections view.
Figure A-14 SSH protocol version 2
Under Preferred SSH protocol version, select 2.
3. In the Category pane on the left, click Connection → SSH → Auth, as shown in Figure A-15. More options are displayed for controlling SSH authentication.
In the Private key file for authentication field, either browse to or type the fully qualified directory path and file name of the SSH client private key file, which was created previously (for example, C:Support Utilsputtyprivat.PPK).
Figure A-15 SSH authentication
4. In the Category pane, click Session to return to the PuTTY Configuration window Basic options for your PuTTY session view (Figure A-16).
5. Enter the following information in these fields in the right pane:
 – Host Name (or IP address): Specify the host name or system IP address of the IBM Storwize V5000 Gen2 clustered system.
 – Saved Sessions: Enter a session name.
Figure A-16 Enter the session information
6. Click Save to save the new session (Figure A-17).
Figure A-17 Save the new session
7. Figure A-18 shows the saved PUTTY session. Select the new session and click Open.
Figure A-18 Saved PUTTY session
8. If a PuTTY Security Alert window opens. Confirm it by clicking Yes (Figure A-19).
Figure A-19 Confirm the security alert
9. PuTTY now connects to the system and prompts you for a user name to log in as. Enter Superuser as the user name (Example A-1) and click Enter.
Example A-1 Enter user name
login as: Superuser
Authenticating with public key "putty public key"
IBM_2077:ITSO V5000Gen2:Superuser>
The tasks to configure the CLI for the IBM Storwize V5000 Gen2 administration are complete.
SAN Boot
The IBM Storwize V5000 Gen2 supports SAN Boot for Microsoft Windows, VMware, and many other operating systems. SAN Boot support can change, so regularly check the IBM Storwize V5000 Gen2 interoperability matrix at this address:
The IBM Knowledge Center for Storwize V5000 Gen2 contains information about SAN Boot in combination with various operating systems. For more information, go to this address:
More information about SAN Boot is also available in the IBM Multipath Subsystem Device Driver User’s Guide, which is available at the following address:
Enabling SAN Boot for Windows
Complete the following procedure if you want to install a Windows host by using SAN Boot:
1. Configure the IBM Storwize V5000 Gen2 system so that only the boot volume is mapped to the host.
2. Configure the Fibre Channel storage area network (SAN) so that the host sees only one IBM Storwize V5000 Gen2 system node port. Multiple paths during installation are not supported.
3. Configure and enable the host bus adapter (HBA) BIOS.
4. Install the operating system by using the normal procedure, selecting the volume as the partition on which to install.
 
HBAs: You might need to load an additional HBA device driver during installation, depending on your Windows version and the HBA type.
5. Install Subsystem Device Driver Device Specific Module (SDDDSM) after the installation completes.
6. Modify your SAN zoning to allow multiple paths.
7. Check your host to see whether all paths are available.
8. Set redundant boot devices in the HBA BIOS to enable the host to boot when its original path fails.
Enabling SAN Boot for VMware
Complete the following steps if you want to install a VMware ESX host by using SAN Boot:
1. Configure the IBM Storwize V5000 Gen2 system so that only the boot volume is mapped to the host.
2. Configure the Fibre Channel SAN so that the host sees only one IBM Storwize V5000 Gen2 system node port. Multiple paths during installation are not supported.
3. Configure and enable the HBA BIOS.
4. Install the operating system by using the normal procedure, selecting the volume as the partition on which to install.
 
HBAs: You might need to load an additional HBA device driver during installation, depending on your ESX level and the HBA type.
5. Modify your SAN zoning to allow multiple paths.
6. Check your host to see whether all paths are available and modify the multipath policy, if required.
Windows SAN Boot migration
If your host runs Windows Server 2008, Windows 2012 or Windows 2016 operating system and uses existing SAN Boot images that are controlled by storage controllers, you can migrate these images to image-mode volumes that are controlled by the IBM Storwize V5000 Gen2 system.
 
SAN Boot procedures: For SAN Boot procedures for other operating systems, check IBM Knowledge Center for the Storwize V5000:
Complete the following steps to migrate your existing SAN Boot images:
1. If the existing SAN Boot images are controlled by an IBM storage controller that uses the IBM Subsystem Device Driver (SDD) as the multipathing driver, you must use SDD V1.6 or later. Run the SDD datapath set bootdiskmigrate 2077 command to prepare the host for image migration. For more information, see the Multipath Subsystem Device Driver documentation.
2. Shut down the host.
3. Complete the following configuration changes on the storage controller:
a. Write down the Small Computer System Interface (SCSI) logical unit number (LUN) ID that each volume is using, for example, boot LUN SCSI ID 0, Swap LUN SCSI ID 1, and Database LUN SCSID 2.
b. Remove all of the image-to-host mappings from the storage controller.
c. Map the existing SAN Boot image and any other disks to the IBM Storwize V5000 Gen2 system.
4. Change the zoning so that the host can see the IBM Storwize V5000 Gen2 I/O group for the target image mode volume.
5. Complete the following configuration changes on the IBM Storwize V5000 Gen2 system:
a. Create an image mode volume for the managed disk (MDisk) that contains the SAN Boot image. Use the MDisk unique identifier to specify the correct MDisk.
b. Create a host object and assign the host HBA ports.
c. Map the image mode volume to the host by using the same SCSI ID as before. For example, you might map the boot disk to the host with SCSI LUN ID 0.
d. Map the swap disk to the host, if required. For example, you might map the swap disk to the host with SCSI LUN ID 1.
6. Change the boot address of the host by completing the following steps:
a. Restart the host and open the HBA BIOS utility of the host during the booting process.
b. Set the BIOS settings on the host to find the boot image at the worldwide port name (WWPN) of the node that is zoned to the HBA port.
7. If SDD V1.6 or later is installed and you run bootdiskmigrate in step 1, reboot your host, update SDDDSM to the current level, and go to step 14. If SDD V1.6 is not installed, go to step 8.
8. Modify the SAN zoning so that the host sees only one path to the IBM Storwize V5000 Gen2.
9. Boot the host in single-path mode.
10. Uninstall any multipathing driver that is not supported for the IBM Storwize V5000 Gen2 system hosts that run the applicable Windows Server operating system.
11. Install SDDDSM.
12. Restart the host in single-path mode. Ensure that SDDDSM was correctly installed.
13. Modify the SAN zoning to enable multipathing.
14. Rescan the drives on your host and check that all paths are available.
15. Reboot your host and enter the HBA BIOS.
16. Configure the HBA settings on the host. Ensure that all HBA ports are boot-enabled and that they can see both nodes in the I/O group that contains the SAN Boot image. Configure the HBA ports for redundant paths.
17. Exit the BIOS utility and finish starting the host.
Map any additional volumes to the host, as required.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.19.75.133