Thursday, March 30, 2017

WFA Workflow to check iSCSI setup

For a customer I had to create this workflow to check/create the iSCSI setup between a host and a vserver.  This workflow does some excessive testing on both the host & vserver side and will re-mediate if needed.

Download the dar




Steps :

1 : Ask for vserver & windows host
2 : Check/Install snapdrive on the host (upgrade will follow)
3 : Check/Start the msiscsi windows service (set to automatic)
4 : Check/Install the multipath-IO feature
5 : Check/Alarm if the windows host has (enough) iscsi ip addresses
6 : Check if the vserver runs iscsi and has (enough) iscsi lifs
7 : Check/Create new mutual chap passwords and store in KeePass database
8 : Check/Create iscsi connections

Input

1 : Cluster
2 : Vserver
3 : Computer (must be netbios)

Constants

Note : backslashes need to be doubled (escaped)
Note2 : change to match your environment
Note3 : the computer name must be netbios, as I'll add the domain name in the workflow.  To install snapdrive, it was absolutely necessary to have the FQDN name, or it would keep nagging about multiple connection to the remote computer with the same username.  I need to map the remote computers c$ share to push the install files.  The commands used in this workflow are also separate blogposts, look 'em up to learn more.
1 : SNAPDRIVE_INSTALLPATH (\\server\c$\soft\snapdrive.exe)
2 : CREDENTIAL_REMOTE (name of wfa-stored credentials to remotely access the computer)
3 : CREDENTIAL_SNAPDRIVE (name of wfa-stored credentials used to run snapdrive)
4 : ISCSI_SERVICE (msiscsi)
5 : NETWORK_ISCSI (Network address of iscsi)
6 : NETMASK_ISCSI (Netmask address of iscsi)
7 : COMPUTER_IQN ("iqn.1991-05.com.microsoft:" + COMPUTER_FQDN)
8 : DOMAIN_NAME (your domain name)
9 : KEEPASS_DB (c:\path_of_keepass_db)
10 : KEEPASS_GROUP (DOMAIN_NAME + "/iscsi_chap/" + $Computer)
11 : ISCSI_IN_NAME (iSCSIin => chap username)
12 : ISCSI_OUT_NAME (iSCSIout => chap username)
13 : COMPUTER_FQDN ($Computer + "." + DOMAIN_NAME)
14 : MPIO_FEATURE (Multipath-IO)

No comments :

Post a Comment