HP StorageWorks 1606 HP StorageWorks FOS 6.3.0b Release Notes (5697-0360, Apri - Page 33

Port Mirroring, 10G interoperability, Port Fencing, ICLs, Extended Fabrics and R_RDY flow control

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

Page 33 highlights

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 over multiple port groups. • Port Mirroring is not supported on the 1606 Extension SAN Switch. 10G interoperability 10G interoperability between the 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 10Gb blade, but this will not negatively impact the system. Port Fencing • For Port Fencing, once the trigger threshold is exceeded (for example, for ITWs, CRCs, or LRs), Fabric Watch waits for approximately six seconds to see if the port is going offline. If it is still online at the next poll cycle, Fabric Watch fences the port. Extensive testing has shown that ports in the process of going offline may exhibit bursts of errors. Waiting the additional six seconds to check the port status helps prevent false positives and unnecessarily fencing a port (for example, during a server reboot). • When using Port Fencing, you must first run the fwalarmsfilterset command. This command enables the port and allows you to receive Port Fencing messages. • The state-changes counter used by Fabric Watch in FOS 6.3 has been updated to ignore any toggling of F_Ports due to planned internal mechanisms, such as throttling and trunking. There are some FOS CLI commands, such as portcfgspeed and portCfgTrunkPort, that implicitly disable/enable ports after configuration. • Fabric Watch monitors state change for LISL ports, even though it is not displayed in Fabric Watch CLI commands. • The Port Fencing feature is not supported for Loss of Sync (LOS) and Link Failure (LF) areas of Port/F-Port/E-Port classes. State change area can be used in place of LOS/LF areas for Port Fencing. ICLs • If a DC SAN Director with an 8-link ICL license is connected to a DC SAN Director with a 16-link license, the DC SAN Director with the 16-link license will report enc_out errors. The errors are harmless, but will continue to increment. These errors will not be reported if a DC SAN Director with a 16-link license is connected to a DC04 SAN Director with only 8-link ICL ports. • If ICL ports are disabled on only one side of an ICL link, the enabled side may see enc_out errors. Extended Fabrics and R_RDY flow control • Starting with FOS 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 HP StorageWorks FOS 6.3.0b Release Notes 33

  • 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
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
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 over multiple port groups.
•
Port Mirroring is not supported on the 1606 Extension SAN Switch.
10G interoperability
10G interoperability between the 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 10Gb blade, but this will not negatively impact the system.
Port Fencing
•
For Port Fencing, once the trigger threshold is exceeded (for example, for ITWs, CRCs, or LRs),
Fabric Watch waits for approximately six seconds to see if the port is going offline. If it is still
online at the next poll cycle, Fabric Watch fences the port. Extensive testing has shown that ports
in the process of going offline may exhibit bursts of errors. Waiting the additional six seconds to
check the port status helps prevent false positives and unnecessarily fencing a port (for example,
during a server reboot).
•
When using Port Fencing, you must first run the
fwalarmsfilterset
command. This command
enables the port and allows you to receive Port Fencing messages.
•
The state-changes counter used by Fabric Watch in FOS 6.3 has been updated to ignore any
toggling of F_Ports due to planned internal mechanisms, such as throttling and trunking. There are
some FOS CLI commands, such as
portcfgspeed
and
portCfgTrunkPort
, that implicitly
disable/enable ports after configuration.
•
Fabric Watch monitors state change for LISL ports, even though it is not displayed in Fabric Watch
CLI commands.
•
The Port Fencing feature is not supported for Loss of Sync (LOS) and Link Failure (LF) areas of
Port/F-Port/E-Port classes. State change area can be used in place of LOS/LF areas for Port Fencing.
ICLs
•
If a DC SAN Director with an 8-link ICL license is connected to a DC SAN Director with a 16-link
license, the DC SAN Director with the 16-link license will report
enc_out
errors. The errors are
harmless, but will continue to increment. These errors will not be reported if a DC SAN Director
with a 16-link license is connected to a DC04 SAN Director with only 8-link ICL ports.
•
If ICL ports are disabled on only one side of an ICL link, the enabled side may see
enc_out
errors.
Extended Fabrics and R_RDY flow control
•
Starting with FOS 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
HP StorageWorks FOS 6.3.0b Release Notes
33