Home > Storage > PowerMax and VMAX > Data Protection > Dell PowerMax and VMAX All Flash: SRDF/Metro Overview and Best Practices > Configuring Path Priority RHEL 8.0 and Higher
With RHEL 8.0 and Higher Multipath settings can also be configured to prioritize different IO paths, to ensure those with lowest latency always take priority.
This is typically done for performance reasons. When one array is reporting better response times than the other. Unisphere for PowerMax performance charts can help identify which array should have the highest priority. Refer to KB article 225178 Imbalanced IO response times in SRDF Metro Cross-connect configuration | Dell US.
In the case where prioritizing the paths is needed, follow the following five step process.
1. Determine which paths are associated with each array.
This can be done by using the syminq and syminq -native commands. If you don’t have solutions enabler installed on your hosts you can install the standalone inq utility from Dell available here which provides the same functionality for device and path validation.
In the example below, running syminq or inq without any options will show the devices as if they appear from a single array due to the matching external WWN identifier presented by the SRDF METRO configuration. All devices appear to be device with serial number “6900644000”. The number 69 at the start of the serial signifies that the device is from array serial ending 69 and the 644 indicated the PowerMax device ID.
Conversely when the same command is run with the -native switch the syminq/inq command will read the native WWN showing that some devices have serial number “18001F5000” while others remain “6900644000”, this shows which devices are from the target array serial number ending in 18.
For the example we are following, we will assign a higher priority to paths to array serial number ending in 18 boxed in yellow.
Paths to array serial number ending in 69 boxed in red are the paths to be given lower priority.
2. Determine the World Wide Node Name associated with each of the paths
In order to identify the WWN of both paths to the arrays, we can issue the following command searching for devices from each array, in this case sdao and sdak.
multipathd show paths format "%N:%R:%n:%r” | grep -E -w "sdao" "sdak" command output is shown below.
The above output shows the World Wide Node Name of the array ports associated with each device path.
World Wide Node Name of array ports for serial number ending in 18 is the first device, and the other for array serial ending 69.
3. On the application server, edit the multipath.conf file to include the devices definition as outlined below.
This will result in paths to array serial number ending in 18 boxed in yellow to be set at priority value 20 and paths to array serial number ending in 69 boxed in red to be set at priority value 15.
4. On the application server, run the multipathd reconfigure command.
This action tells the multipath daemon to rediscover the device paths and create the required device path IO Groups.
5. On the application server, run the multipath -ll command.
The result is the creation of two path groups.
Multipathing will send all application IO to the paths of the group with the higher prio value when available. In the above example, the path group with a prio=20 value.
The paths in the group with a prio=15 value will only be used when all paths in the higher priority group are unavailable.
This process can be repeated on the hosts’ remote site by adjusting the multipathing values so that the local array has higher priority, and the remote array has lower priority accounting for higher latency due to distance.