HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2.0g release notes (5697-0035 - Page 24

Port Mirroring, 10G interoperability, Port Fencing, Extended Fabrics and R_RDY flow control - 24 san switch console

Get HP StorageWorks 8/80 - SAN Switch PDF manuals and user guides View all HP StorageWorks 8/80 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 24 highlights

that are still established to the CUP. This results in mainframe console messages indicating that this type of recovery has occurred. Port Mirroring • On the 8/80 SAN Switch, the Port Mirroring feature has a limitation where all port mirror resources must remain in the same ASIC port group. The resources are the configure mirror port, Source Device, and Destination Device or ISL, if the Destination Device is located on another switch. The ASIC port groups are 0-15, 16-31, 32-47, 48-63, and 64-79. The routes will be broken if the port mirror resources are spread across multiple port groups. • Port Mirroring is not supported on a switch with the VF feature enabled. 10G interoperability 10G interop between HP StorageWorks SAN Director 6 Port 10Gb FC blade and McDATA blades is not supported due to a hardware limitation. However, the SAN Director 6 Port 10Gb FC blade is supported in a chassis running in interopmode 2 or 3 (SAN Director 6 Port 10Gb FC blade to SAN Director 6 Port 10Gb FC blade connections only). A SAN Director 6 Port 10Gb FC blade will not synchronize with a McDATA 10G blade, but will not negatively impact the system. Port Fencing • When the Port Fencing feature is enabled for ITW or CRC errors, the first set of errors detected on an active link that meet the custom high threshold level set by the user (or the default threshold level) is always ignored to account for expected link transition errors. The port is disabled only upon detection of a second set of 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 checkbox 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. 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. 24

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
that are still established to the CUP. This results in mainframe console messages indicating that
this type of recovery has occurred.
Port Mirroring
•
On the 8/80 SAN Switch, the Port Mirroring feature has a limitation where all port mirror resources
must remain in the same ASIC port group. The resources are the configure mirror port, Source
Device, and Destination Device or ISL, if the Destination Device is located on another switch. The
ASIC port groups are 0-15, 16-31, 32-47, 48-63, and 64-79. The routes will be broken if the
port mirror resources are spread across multiple port groups.
•
Port Mirroring is not supported on a switch with the VF feature enabled.
10G interoperability
10G interop between HP StorageWorks SAN Director 6 Port 10Gb FC blade and McDATA blades
is not supported due to a hardware limitation. However, the SAN Director 6 Port 10Gb FC blade is
supported in a chassis running in interopmode 2 or 3 (SAN Director 6 Port 10Gb FC blade to SAN
Director 6 Port 10Gb FC blade connections only). A SAN Director 6 Port 10Gb FC blade will not
synchronize with a McDATA 10G blade, but will not negatively impact the system.
Port Fencing
•
When the Port Fencing feature is enabled for ITW or CRC errors, the first set of errors detected
on an active link that meet the custom high threshold level set by the user (or the default threshold
level) is always ignored to account for expected link transition errors. The port is disabled only
upon detection of a second set of 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
checkbox 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.
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.
24