HP StorageWorks 1606 HP StorageWorks Fabric OS 6.3.0a release notes (5697-0359 - Page 27

On the DC SAN Director Multi-protocol Extension Blade, GigE ports 0-9 or 10-GbE port 1

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 27 highlights

• Software compression (available on the 1606 Extension SAN Switch) modes 2 and 3 are not supported in FICON environments; they are supported only in Open Systems environments. • Software compression (modes 2 and 3) generally gives a better compression ratio, but not the throughput or bandwidth across all six GE ports. HP recommends software compression for lowthroughput links and supports throughput up to 2 Gb/s across all 6 GE ports. • To perform the following operations you must delete the FCIP configuration on the affected ports first: • Switching modes between 1G/10G/Dual • Moving VE/GE port between logical switches • The DC SAN Director Multi-protocol Extension Blade supports three operating modes: • Mode 1: 10 1-GbE ports mode (default) • Mode 2: 10 1-GbE ports and 1 10-GbE port • Mode 3: 2 10-GbE ports Modes 2 and 3 require the slot-based 10-GbE FCIP license. • ARL is not supported on 10-Gb tunnels. • IPv6, IPsec, DiffServ VLAN tagging, and In-band Management are not supported on the 1606 Extension SAN Switch or DC SAN Director Multi-protocol Extension Blade. • Fabric OS 6.3 supports only up to four 1-Gb circuits per VE/FCIP tunnel for the 1-Gb interfaces. A VE/FCIP tunnel created over 10-Gb interfaces will be limited to 10 circuits created using IPIFs on the same 10-GbE port (and no more than 1 Gb per circuit). • As a recommended best practice, the VE tunnel should not be oversubscribed (for example, 8-Gb FC traffic over 500 Mb/s tunnel). General guidelines are 2:1 subscription without compression and 4:1 with compression. • Nondisruptive firmware activation on Fabric OS 6.3 will disrupt I/O traffic on FCIP links. • FCR (VEX) is not supported on the DC SAN Director Multi-protocol Extension Blade but is supported on the 1606 Extension SAN Switch. • Differences between the 1606 Extension SAN Switch/DC SAN Director Multi-protocol Extension Blade platforms and previous-generation 7500/FR4-18i platforms include: • On the 1606 Extension SAN Switch, the GigE port does not directly correlate to a VE_Port. • On the DC SAN Director Multi-protocol Extension Blade, GigE ports 0-9 or 10-GbE port 1 (xge1) correspond to VE_Ports 12-21, and 10-GbE port 0 (xge0) corresponds to VE_Ports 2231. • The CLI syntax for the 1606 Extension SAN Switch/DC SAN Director Multi-protocol Extension Blade varies from the 7500/FR4-18i. See the Brocade Fabric OS Command Reference document for Fabric OS 6.3 for details. • Both ends of a tunnel must be identically configured for the Compression, FastWrite, and Tape Pipeline options. If a mismatch exists, the tunnel will not be established and the TCP virtual connections will be removed. • Under traffic isolation (TI) zone configurations with failover enabled, non-TI zone traffic will use the dedicated path if no other E or VE paths through the fabric exist, or if the nondedicated paths are not the shortest paths. (A higher bandwidth tunnel with multiple circuits will become the shortest path compared to a single tunnel.) • A VE/VEX tunnel and E/EX FC port cannot connect to the same domain at the same time. • The recommended Keep Alive Timeout must be the same on the tunnel and circuits on the switches on both sides of a link. • The 1606 Extension SAN Switch and DC SAN Director Multi-protocol Extension Blade cannot receive a ping from an external device (for example, a Windows PC). • Latency measurements supported on FCIP tunnels (tested limit under Fabric OS 6.3.0): HP StorageWorks Fabric OS 6.3.0a release notes 27

  • 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
•
Software compression (available on the 1606 Extension SAN Switch) modes 2 and 3 are not
supported in FICON environments; they are supported only in Open Systems environments.
•
Software compression (modes 2 and 3) generally gives a better compression ratio, but not the
throughput or bandwidth across all six GE ports. HP recommends software compression for low-
throughput links and supports throughput up to 2 Gb/s across all 6 GE ports.
•
To perform the following operations you must delete the FCIP configuration on the affected ports
first:
•
Switching modes between 1G/10G/Dual
•
Moving VE/GE port between logical switches
•
The DC SAN Director Multi-protocol Extension Blade supports three operating modes:
•
Mode 1: 10 1-GbE ports mode (default)
•
Mode 2: 10 1-GbE ports and 1 10-GbE port
•
Mode 3: 2 10-GbE ports
Modes 2 and 3 require the slot-based 10-GbE FCIP license.
•
ARL is not supported on 10-Gb tunnels.
•
IPv6, IPsec, DiffServ VLAN tagging, and In-band Management are not supported on the 1606
Extension SAN Switch or DC SAN Director Multi-protocol Extension Blade.
•
Fabric OS 6.3 supports only up to four 1-Gb circuits per VE/FCIP tunnel for the 1-Gb interfaces.
A VE/FCIP tunnel created over 10-Gb interfaces will be limited to 10 circuits created using IPIFs
on the same 10-GbE port (and no more than 1 Gb per circuit).
•
As a recommended best practice, the VE tunnel should not be oversubscribed (for example, 8-Gb
FC traffic over 500 Mb/s tunnel). General guidelines are 2:1 subscription without compression
and 4:1 with compression.
•
Nondisruptive firmware activation on Fabric OS 6.3 will disrupt I/O traffic on FCIP links.
•
FCR (VEX) is not supported on the DC SAN Director Multi-protocol Extension Blade but is supported
on the 1606 Extension SAN Switch.
•
Differences between the 1606 Extension SAN Switch/DC SAN Director Multi-protocol Extension
Blade platforms and previous-generation 7500/FR4-18i platforms include:
•
On the 1606 Extension SAN Switch, the GigE port does not directly correlate to a VE_Port.
•
On the DC SAN Director Multi-protocol Extension Blade, GigE ports 0-9 or 10-GbE port 1
(xge1) correspond to VE_Ports 12-21, and 10-GbE port 0 (xge0) corresponds to VE_Ports 22-
31.
•
The CLI syntax for the 1606 Extension SAN Switch/DC SAN Director Multi-protocol Extension
Blade varies from the 7500/FR4-18i. See the
Brocade Fabric OS Command Reference document
for Fabric OS 6.3 for details.
•
Both ends of a tunnel must be identically configured for the Compression, FastWrite, and Tape
Pipeline options. If a mismatch exists, the tunnel will not be established and the TCP virtual connec-
tions will be removed.
•
Under traffic isolation (TI) zone configurations with failover enabled, non-TI zone traffic will use
the dedicated path if no other E or VE paths through the fabric exist, or if the nondedicated paths
are not the shortest paths. (A higher bandwidth tunnel with multiple circuits will become the shortest
path compared to a single tunnel.)
•
A VE/VEX tunnel and E/EX FC port cannot connect to the same domain at the same time.
•
The recommended Keep Alive Timeout must be the same on the tunnel and circuits on the switches
on both sides of a link.
•
The 1606 Extension SAN Switch and DC SAN Director Multi-protocol Extension Blade cannot
receive a ping from an external device (for example, a Windows PC).
•
Latency measurements supported on FCIP tunnels (tested limit under Fabric OS 6.3.0):
HP StorageWorks Fabric OS 6.3.0a release notes
27