|
Measures reported by NAUSDInitiatorTest
Initiator groups (igroups) are tables of host identifiers (FCP WWPNs or iSCSI node names) that are used to control hosts’ access to LUNs.
igroups specify which initiators have access to which LUNs. igroups can be created either before or after LUNs are created, but they must be created before a LUN is mapped to an igroup. Initiator groups can have multiple initiators, and multiple igroups can have the same initiator. However, a LUN can not be mapped to multiple igroups that have the same initiator.
An initiator cannot be a member of igroups of differing ostypes.
Using this test, you can analyze the initiators of each igroup and determine the following:
- The number of initiators with ALUA setting mismatch
- The number of initiators with the OS type mismatch
- How many initiators are actually differing from the actual VSA setting? and
- Which are the initiators that are mapped to the LUNs with non unique ids?
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Alua_Setting |
Indicates the number of initiators in this igroup with an ALUA setting mismatch. |
Number |
If the ALUA setting does not match between the local and partner systems, it would affect the host multi-path software's ability to distingush primary and secondary paths. This could lead to incorrect system behaviour. The containing igroups could be within the local system or between local and partner systems. The Detailed diagnosis of this measure reveals the name of the initiator, the initiator group to which the initiator belongs and the ALUA settings of the affected initiators. |
| OS_type |
Indicates the number of initiators in an initiator group with an operating system mismatch. |
Number |
An initiator cannot be a member of initiator groups of differing OS types i.e., the initiator can be a member of igroups that are of the same OS type. The Detailed diagnosis of this measure reveals the name of the initiator, the containing igroup of the initiator and the OS type of the affected inititator. |
| VSA_settings |
Indicates the number of initiators in an initiator group with a differing VSA setting. |
Number |
In order to avoid unexpected performance related issues in the storage system, an initiator can be a member of initiator groups with the same VSA setting only.
The detailed diagnosis of this measure reveals the name of the initiator, the initiator group to which the initiator belongs and the VSA setting of the affected initiator. |
| Partner_os |
Indicates the number of initiators in an initiator group with an operating system mismatch between the local and partner systems. |
Number |
In order to avoid unexpected performance related issues in the storage system, an initiator can be of the same OS type in both the local and partner systems of the initiator groups.
The detailed diagnosis of this measure reveals the name of the initiator, the OS type of the initiator belonging to the initiator group in both local and partner systems. |
| Lun_mapping |
Indicates the number of initiators that are mapped to the LUNs with non-unique LUN ids. |
Number |
Only one lun in the cluster can be mapped to an initiator at a given lun-id. Certain conflicts may arise if a lun on each filer is mapped to the same initiator at the same lun-id. These conflicts need to be resolved before a filer can be upgraded to run in the ‘single_image’ fcp cfmode. The conflicts can be resolved by unmapping one lun and remapping it to an unused lun-id.
The Detailed diagnosis of this measure reveals the name of the initiator and the lun id of the mapped lun for the affected initiators. |
|