HP SureStore 7400 HP StorageWorks Multi-protocol Router XPath OS 7.4.1f releas - Page 7

Important notes Table 5 through Table 10 list issues to consider when using XPath OS 7.4.1f and the HP StorageWorks MP Router. Table 5 Fibre Channel routing services Issue Description Unexpected LSAN Zone Update messages or unexpected physical device offline messages These messages can occur during normal operation. However, if the MP Router reports numerous occurrences that cannot be correlated to actual initiated events, such as planned device reconfigurations or reboots, examine low-level port error counts using the portstatsshow command. Faulty cables and SFPs that cause interruptions in EX_Port connectivity might also cause unexpected fabric reconfigurations. In the event of unexpected fabric reconfigurations, ensure that there are no low-level errors occurring on ports and focus diagnostic efforts on cables and SFPs. Zoning restrictions for LSAN zones and local fabric zones Remote WWNs cannot be in both a Logical Storage Area Network (LSAN) zone and a local fabric zone of fabrics that they do not physically reside in. Putting them in both locations may result in excessive boot times for host or servers in fabrics connected to the MP Router. If a remote node WWN is in an LSAN zone, it cannot also be in a local non-LSAN zone in a fabric that it does not physically reside in. For example, if you have a host or storage device defined in a remote fabric zone and want to add either of these devices to an LSAN zone, you must ensure that these devices are not listed in any local zones other than the physical fabric they reside in. Local WWNs are allowed in both an LSAN zone and the local zones of the fabric where they are physically located. Fabric ID oversubscribed message If you configure multiple EX-port connections to the same fabric using different Fabric IDs, the port error Fabric ID oversubscribed displays. While the Fabric ID used for each fabric connected to the MP Router is unique, all EX-ports connected to the same fabric from the MP Router must use the same Fabric ID. HBA configuration In certain large routed fabrics with large numbers of EX_Ports (for example, 8 or fewer) connected to each fabric (usually done for bandwidth for large numbers of shared initiators and targets across fabrics) and a large number of shared devices (for example, 800 or fewer), set the PLOGI timeout value for 1 Gbps JNI FC HBAs to 3000 ms. This will allow time for the routed fabric to answer PLOGI requests. Meta-SAN traffic In a non-routed SAN, if there are multiple E_Port links between two switches and fabric reconfigurations occur due to the loss of a single E_Port link, traffic around the fabric is generally not interrupted. If interruptions occur, they are brief (less than one second). Due to a design decision in this release of the router, traffic disruption for routed traffic always occurs for a short period (less than one second), even if EX_Port links remain available. The manager of a non-routed SAN will not expect this performance characteristic. During testing, applications have been shown to tolerate the traffic disruption in the routed fabric and to recover based on an application-specific recovery timeline, which is typically longer than when the fabric allows traffic to flow again. However, the commonly used I/O test tool, Iometer, is known to panic or crash under certain circumstances of traffic disruption; this has occurred in large routed fabric configurations. Multi-protocol Router XPath OS 7.4.1f 7