Understanding the owner name used by the Analyzer detail view

Ops Center Analyzer Detail View User Guide

Version

11.0.x

Audience

anonymous

Part Number

MK-99ANA007-06

ft:lastEdition

2026-03-16

On the Analyzer detail view, the owner represents the hosts where LDEVs are mapped to the host group. When a group of LDEVs that are using a common set of WWNs are mapped to multiple host groups, then the owner name is created by combining the name of these host groups. Therefore, an owner is not the same as the host group.

The Analyzer detail view creates the owner only for the Hitachi Enterprise Storage probe by applying the following rules:

Rule 1: The unique name is discovered from the list of host groups and sorted in case-insensitive alphabetical order.

Rule 2: Length of the common string is checked. If the common string is the name of the host group, then the last character is skipped from the common string.

Rule 3: If the common string of the host group is less than three characters, then the owner name consists of the host groups separated by an underscore (_).

Rule 4: If the common string of the host group name is three characters or greater, then the owner name consists of the common sub-string appended by a hyphen (-) and the remaining part of the host group name is separated by an underscore (_).

Rule 5: If the resulting owner name is greater than 50 characters, it is truncated as follows.

a. If the owner name has a hyphen, the name is truncated at the hyphen.

b. If the owner name does not have the hyphen (-), then the first 50 characters become the owner name.

Rule 6: If non-unique owner names are obtained after applying the rules, then the owner name is appended with (0), (1), and so on.

The owner name depends on the configuration data collection. If there is any change in the components that are used to create the owner name, the owner name is changed after the latest configuration data is collected.

Example 1:

The group of LDEVs 00:01:01 and 00:01:02 having a common set of WWNs are mapped to the following host groups:

ESXI_COMTest
DC1_ESXI_COMTest_NEW
DC1_ESXI_COMTest_NEW_M4
ESXI_COMTest
COMP_test

After applying rule 1 on the above host groups, the following output is created:
```
COMP_test
DC1_ESXI_COMTest_NEW
DC1_ESXI_COMTest_NEW_M4
ESXI_COMTest
```
According to rule 2, the common string is searched and starts matching with the first character. Because there is no common string in these host groups name, the length of the common string is considered zero (0) and rule 3 is applied so that the owner name contains all the host group names separated by an underscore (_) and the owner name becomes:
```
COMP_test_DC1_ESXI_COMTest_NEW_DC1_ESXI_COMTest_NEW_M4_ESXI_COMTest
```
As the length of this owner name exceeds 50 characters and it does not have a hyphen, the length restriction rule 5b applies and the following owner name is created:
```
COMP_test_DC1_ESXI_COMTest_NEW_DC1_ESXI_COMTest_NE
```

Example 2:

The group of LDEVs 00:01:03 and 00:01:04 are mapped to following host groups:

COMP_test
COMP_test22

After applying rule 1, the following output is created:
```
COMP_test
COMP_test22
```
The common string is COMP_test. According to rule 2, if the common string is the name of the host group, then the last character is skipped:
```
COMP_tes
```
The length of the common string is eight characters in this case (greater than three characters). Therefore, rule 4 is applied and the owner name contains the common sub-string appended by a hyphen and the remaining part of the host group name is separated by an underscore. The resulting owner name is: (rule 5 does not apply because the name is less than 50 characters.)
```
COMP_tes-t_t22
```