Configure
storage data client to use authentication
Perform this procedure to configure the
storage data clients for authentication.
About this task
For each
storage data client, populate the generated CHAP password. On a VMware ESXi host, this requires setting a new
scini parameter through the esxcli tool. Use the procedure to perform this configuration change. For Windows and Linux SDC hosts, the included
drv_cfg utility is used to update the driver and configuration file in real time.
NOTE:Reboot the VMware ESXi hosts for the new parameter to take effect.
Prerequisites
Generate the pre-shared passwords for all the
storage data clients to be configured.
Ensure that you have the following information:
Primary and
secondary MDM IP addresses or names
Credentials to access all VMware ESXi hosts running
storage data clients
Steps
Using SSH log in to the VMware ESXi host using the provided credentials.
Type
esxcli system module parameters list -m scini | grep Ioctl to list the hosts current
scini parameters:
IoctlIniGuidStr string d30ff770-b64c-40b5-a341-58d18927e523 Ini Guid, for example: 12345678-90AB-CDEF-1234-567890ABCDEF
IoctlMdmIPStr string 192.168.151.20,192.168.152.20,192.168.153.20,192.168.154.20 Mdms IPs, IPs for MDM in same cluster should be comma separated. To configure more than one cluster use '+' to separate between IPs.For Example: 10.20.30.40,50.60.70.80+11.22.33.44. Max 1024 characters
IoctlMdmPasswordStr string Mdms passwords. Each value is <ip>-<password>, Multiple passwords separated by ';' signFor example: 10.20.30.40-AQAAAAAAAACS1pIywyOoC5t;11.22.33.44-tppW0eap4cSjsKIcMax 1024 characters
NOTE:The third parameter
IoctlMdmPasswordStr is empty.
Using ESXCLI, configure the driver with the existing and new parameters. To specify multiple IP addresses, use a semicolon (;) between the entries, as shown in the following example. Additional data IP addresses, data3, and data4 can be used, if required.
esxcli system module parameters set -m scini -p "IoctlIniGuidStr=10cb8ba6-5107-47bc-8373-5bb1dbe6efa3 IoctlMdmIPStr=192.168.151.20,192.168.152.20 IoctlMdmPasswordStr=192.168.151.20- AQAAAAAAAAA8UKVYp0LHCFD59BrnExNPvKSlGfLrwAk;192.168.152.20-AQAAAAAAAAA8UKVYp0LHCFD59BrnExNPvKSlGfLrwAk bBlkDevIsPdlActive=1 blkDevPdlTimeoutMillis=60000"
NOTE:There are spaces between
Ioctl parameter fields and the opening quotes. The example is entered on a single line.
Reboot the VMware ESXi nodes.
The SDC configuration is applied.
If the SDC is a
PowerFlex hyperconverged node, go to the next step. For other nodes, continue to step 8.
For
PowerFlex hyperconverged nodes, use the scli tool to place the corresponding SDS into maintenance mode.
If the SDS is also the cluster
primary MDM, switch cluster ownership to a
secondary MDM and verify cluster state before proceeding, type
scli --switch_mdm_ownership --mdm_name <secondary MDM name>.
Power off the SVM once the cluster ownership is switched (if needed) and the SDS is in maintenance mode.
Manually migrate the workloads to the other hosts if required, and place the VMware ESXi host in maintenance mode.
Reboot the VMware ESXi host.
Once the host has completed rebooting, remove it from maintenance mode and power on the SVM (if present).
Take the SDS out of the maintenance mode (if present).
Repeat this procedure for each VMware ESXi SDC host.
Examples - Windows and Linux SDC nodes
Windows and Linux hosts have access to the
drv_cfg utility, which allows driver modification and configuration in real time.
The --file option allows for persistent configuration to be written to the driver's configuration file (so that the SDC remains configured after a reload or reboot).
NOTE:Only one IP address is needed for the command to identify the MDM to modify.
Windows (from within a PowerShell prompt):
C:\Program Files\EMC\scaleio\sdc\bin\drv_cfg --set_mdm_password --ip <MDM IP> --port 6611 --password <secret>