HP 4400 HP StorageWorks Fabric OS 6.2.2e Release Notes (5697-0809, February 20 - Page 25
Extended Fabrics and R_RDY flow control, Implementation, 8-Gb Link Init and fill words
View all HP 4400 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 25 highlights
errors; that is, the next time the user-set threshold level (or default threshold level) is reached. This prevents a port from being disabled due to normal link transition behaviors. • When using the Port Fencing feature, you must first run the fwalarmsfilterset command. This command enables the port and allows you to receive Port Fencing messages. • Port Fencing can be inadvertently disabled from Web Tools. This occurs when you first open the Fabric Watch configuration window and then select the SNMP Trap check box in the Above row. Making this change in Web Tools disables Port Fencing. If this happens, you must re-enable the Port Fencing bit from the CLI. The Port Fencing feature is not supported for Loss of Sync (LOS) and Link Failure (LF) areas of Port/F-port/E-port classes. Extended Fabrics and R_RDY flow control • Starting with Fabric OS 5.1, the Extended Fabrics feature is supported with R_RDY flow control (R_RDY flow control mode can be enabled using the portCfgISLMode command). R_RDY flow control mode that uses IDLE primitives does not support frame-based trunking for devices such as Time Division Multiplexor (TDM). To overcome this limitation and provide support for frame-based trunking with Extended Fabrics, Fabric OS 6.2.x has been enhanced to support interoperability with these distance extension devices. Fabric OS 6.2.x allows Extended Fabrics E_Ports to operate in VC_RDY mode using either ARB or IDLE primitives as fill words. This allows frame-based trunking to be supported on Extended Fabrics E_Ports even when IDLE primitives are configured for these ports when operating in native VC_RDY mode. Prior to this change, frame-based trunking was supported only when ARB primitives were used in VC_RDY mode. With Fabric OS 6.2.x, frame-based Trunking is supported on Extended Fabrics E_Ports even if IDLE or ARB primitives are used when operating in native VC_RDY mode. Implementation The portcfglongdistance CLI parameter VC Translation Link Init is now overloaded to specify whether the long distance link should use IDLE or ARB primitives. By default vc_init is enabled. When vc_init is enabled, the long distance link uses ARB primitives. When vc_init is disabled, the link uses IDLE primitives. The buffer-to-buffer credit recovery feature is not supported on Extended Fabrics E_Port when it is configured to use IDLE primitives. The user must disable buffer-to-buffer credit recovery feature using the command portcfgcreditrecovery and specifying the disable option; otherwise, the link will continuously reset. The Adaptive Networking SID/DID Traffic Prioritization QoS feature is not supported on Extended Fabrics E_Ports when IDLE primitives are configured on these ports. In this mode only data virtual channels are available when QoS related virtual channels are not available. When connecting to an extension device that does not support ARB primitives (such as some TDM products), the following configuration must be used: • portcfgqos -disable • portcfgcreditrecovery -disable • portcfglongdistance 0 The fabric parameter fabric.ops.mode.longdistance is now deprecated and should not be used. 8-Gb Link Init and fill words This section describes the portCfgfillWord command. Other important notes and recommendations 25