HP StorageWorks 2/140 FW 07.01.02/HAFM SW 08.06.00 HP StorageWorks HA-Fabric M - Page 26

Changing or removing the principal switch of a persisted fabric causes two fabrics to be displayed Fabrics are identified by the WWN of the principal switch. If a new principal switch is selected (either manually, or because the current principal switch is removed from the fabric), the fabric is reidentified by the WWN of the new principal switch. If the principal switch of a persisted fabric is changed or removed, two fabrics are displayed with identical switches, with the two fabrics identified by the former and the new principal switch WWN. The persisted fabric indicates all switches have been removed from fabric (red circle with minus sign) and all switch connections disabled (yellow dashed lines). The new fabric is not persisted. Similarly, if the principal switch of a persisted fabric is removed from the fabric (ISLs removed or blocked) but still powered up and managed by HAFM, two fabrics are displayed with identical switches, with the two fabrics identified by the former and the new principal switch WWN. The persisted fabric indicates all switches except the former principal switch have been removed from fabric (red circle with minus sign) and all switch connections disabled (yellow dashed lines). The new fabric is not persisted. Workaround Unpersist the former fabric, and persist the new fabric. Removing a Port Fencing Threshold Policy may not occur as expected under specific conditions Under specific conditions, a Port Fencing Threshold Policy may remain active even if the user has removed it. This occurs when you are in the same Port Fencing configuration session: 1. A particular Port Fencing Threshold Policy is not currently applied to any switch. 2. The same Port Fencing Threshold Policy is applied to switch port(s). 3. The same Port Fencing Threshold Policy is selected in the ISL Threshold table (left panel), and Remove is clicked in order to remove this policy. 4. The Port Fencing configuration session is completed (by clicking OK). Under these conditions, the Port Fencing Threshold Policy is not successfully removed and is active on the switch ports where the policy was applied. Workaround This can be corrected by repeating the selection of the Port Fencing Threshold Policy in the ISL Threshold table (left panel), by clicking Remove, and then clicking OK. The Port Fencing Threshold Policy will then be removed correctly. This can be avoided by also selecting the Port Fencing Threshold Policy on the switch ports where it was applied (right panel), and removing the policy from the switch port(s), before completing the session (step 4 above). 24