HP QR516B manual SATP rule changes cannot be affected through vSphere GUI

Models: QR516B

1 89
Download 89 pages 22 Kb
Page 41
Image 41
•SATP rule changes cannot be affected through vSphere GUI.

NOTE:

SATP rule changes cannot be affected through vSphere GUI.

SATP rule changes through esxcli commands populate the esx.conf file.

A custom SATP rule is an added SATP rule that modifies or redefines parameters of an existing SATP default rule, defines the targeted devices to be affected, and is given a unique custom rule name.

A custom SATP rule cannot be changed/edited. A custom SATP rule must be removed and then a new one created with the desired changes added to affect a change in the parameters of the custom rule.

SATP and PSP creation, changes, additions, or removals will take effect for any new devices presented afterward without the need for server reboot.

The host must be rebooted for SATP rule creation, changes, additions, or removals to take effect on existing, previously presented devices.

Path policy changes done on an individual device basis, either done via vCenter or esxcli command, supersede the PSP path policy defined in a SATP rule, and such path policy changes to individual devices are maintained through host reboots.

Valid PSP for SATP VMW_SATP_DEFAULT_AA rules are:

VMW_PSP_RR

VMW_PSP_FIXED

VMW_PSP_MRU

VMW_PSP_RR is preferred.

Valid PSP for SATP VMW_SATP_ALUA rules are:

VMW_PSP_RR

VMW_PSP_MRU

VMW_PSP_FIXED is not a valid PSP to be defined within an ALUA SATP rule. VMW_PSP_RR is preferred.

Changing from HP 3PAR host persona 6/Generic-legacyto host persona 11/VMware or vice versa:

A change from persona 6 to 11, or from 11 to 6, requires that the array ports affected be taken offline, or that the host for which the persona is being changed is not connected (not logged in). This is an HP 3PAR OS requirement.

For existing devices targeted in a custom SATP rule to be claimed by the rule, the host must be rebooted. This is an ESX/ESXi OS requirement.

Because of the items required for this persona change listed above, the following procedure is recommended for changing from persona 6 to 11, or from 11 to 6:

1.Stop all host I/O and apply the necessary SATP changes (create custom SATP rule and/or modify default SATP rule PSP defaults) to the ESX/ESXi host.

2.Shut down the host.

3.Change the host persona on the array.

4.Boot the host.

5.Verify that the target devices have been claimed properly by the SATP rule as desired.

Multipath Failover Considerations and I/O Load Balancing 41

Page 41
Image 41
HP QR516B manual SATP rule changes cannot be affected through vSphere GUI