HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2 administrator guide (5697-0 - Page 200

AD3 WWN = 10:00:00:00:c7:2b:fd:a3 WWN = 10:00:00:00:c2:37:2b:a3 Domain ID = 1 WWN = 10:00:00:05:1f:05:23:6f Domain ID = 2 WWN = 10:00:00:05:2e:06:34:6e AD4 WWN = 10:00:00:00:c8:3a:fe:a2 Figure 23 Fabric showing switch and device WWNs Figure 24 shows the filtered view of the fabric as seen from AD3 and AD4. The switch WWNs are converted to the NAA=5 syntax; the device WWNs and domain IDs remain the same. Fabric Visible to AD3 User WWN = 10:00:00:00:c7:2b:fd:a3 WWN = 10:00:00:00:c2:37:2b:a3 Domain ID = 1 WWN = 50:00:51:f0:52:36:f9:03 Domain ID = 2 WWN = 50:00:52:e0:63:46:e9:03 Fabric Visible to AD4 User Domain ID = 1 WWN = 50:00:51:f0:52:36:f9:04 WWN = 10:00:00:00:c2:37:2b:a3 Domain ID = 2 WWN = 50:00:52:e0:63:46:e9:04 WWN = 10:00:00:00:c8:3a:fe:a2 Figure 24 Filtered fabric views showing converted switch WWNs Admin Domain compatibility, availability, and merging Admin Domains maintain continuity of service for Fabric OS features, and operate in mixed-release Fabric OS environments. High availability is supported with some backward compatibility. When an E_Port comes online, the adjacent switches merge their AD databases. The receiving switch accepts an AD database from the neighboring switch only if the local AD database is empty or if the new AD database exactly matches both the defined and effective configurations of the local AD database. If the AD database merge fails, the E_Port is segmented with AD conflict error code. Admin Domains can be implemented in fabrics with a mix of AD-capable and non-AD-capable switches. The following considerations apply: 198 Managing administrative domains