HP StorageWorks Multi-protocol Router XPath OS 7.4.1c Release Notes (AV-RW5LL-TE, December 2006)

Table 6 Fibre Channel routing services
Issue
Description
Unexpected LSA
N Zone Update
messages or une
xpected physical
device offline messages
These messages can occur during normal operation. However, if the MP Router
reports numerous occurrences that cannot b e 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 unexpec
ted fabric reconfigurations. In the event of unexpected fabric
reconfigurations, ensure that there are no low-level errors occurring on ports and
focus diagno
stic efforts on cables and SF Ps.
Zoning restrictions for LSA N zones
and local fabric zones
Remote W WNs 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 loca tions, 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, then it cannot also be in a local
non-LSAN zone in a fabric that it does not physically reside in. For example, if
youhaveahostorstoragedevicedefined i n a remote fabric zone and you wish
to add either of these devices to an LSAN zone, you need to ensure that these
devices are not listed in any local zones other than the physical fabric they reside
in. Local WWNs are allowed in b oth an LSAN zone and the local zones of the
fabric where they are physically located.
Fabric ID oversubscribed message
The port error Fabric ID oversubscribed displays if you configure multiple
EX-port connections to the same fabric using different Fabric IDs. 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 con
figuration
In cert
ain large routed fabrics with large numbers of EX_Ports (for example,
≥ 8)
connected to each fabric (usually done for ba ndwidth for large numbers of shared
initi
ators and targets across fabrics) and a large number of shared devices (for
example, ≥ 800), 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, then traffic
around the fabric is generally not interrupted (or is interrupted for a very short
time: for example, less than one second).
Due to a design decision in this release of the Router, trafficdisruptionforrouted
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 trafficdisruptioninthe
routed fabric and to recover based on an application specific recovery timeline,
which is typically longer than when the fabric again permits traffictoflow . However,
thecommonlyusedI/Otesttool,Iometer,isknowntopanicorcrashundercertain
circumstances of traffic d isruption; this has been witnessed to occur in large routed
fabric configurations.
Multi-protocol Router XPath OS 7.4.1c
7