HP 4400 HP B-series Fabric OS 7.0.0a Release Notes (5697-0881, June 2011) - Page 32

APIs for Array Integration) hardware acceleration in vSphere 4.1. This results in non-VAAI methods of data transfer for the underlying arrays, and may affect the performance of VM related operations. FCIP (HP DC SAN Director Multiprotocol Extension Blade, HP 1606 SAN Extension Switch and HP StorageWorks B-series Multi-protocol Router Blade) • HP DC SAN Director Multiprotocol Extension Blade and HP StorageWorks B-series Multi-protocol Router Blade blades cannot coexist in an HP StorageWorks DC SAN Backbone Director Switch or an HP StorageWorks DC04 SAN Director Switch chassis. • IPSec is supported on VE group 12 - 21 and not supported on VE group 22 - 31. • IPSec is supported on FCIP tunnels that use only IPv4 connections. • To enable IPSec, both ends of the tunnel must be running Fabric OS 7.0.0a. • FICON networks with FCIP tunnels do not support DPS (aptpolicy 3) configurations. This applies to both emulating and non-emulating FCIP tunnels. • Both ends of FICON emulating tunnels must run Fabric OS 7.0.0a. • The maximum supported MTU size for the Brocade HP 1606 SAN Extension Switch/HP DC SAN Director Multiprotocol Extension Blade is 1500. • FCIP connections are supported only between the HP 1606 SAN Extension Switch/HP DC SAN Director Multiprotocol Extension Blade and another HP 1606 SAN Extension Switch/HP DC SAN Director Multiprotocol Extension Blade. FCIP tunnels are not supported between the HP 1606 SAN Extension Switch/HP DC SAN Director Multiprotocol Extension Blade and the previous generation HP StorageWorks 400 Multi-protocol Router /HP StorageWorks B-Series Multi-protocol Router Blade platforms. • When multiple FCIP tunnels are present on a switch and additional circuits (and the network bandwidth provided by those circuits) are added to an already active tunnel, there may be a short time where some frame loss can occur due to the process to re-fresh the internal FC frame routing tables in the switch. Therefore, additional circuits should be added only during low I/O periods utilizing the FCIP Tunnel being modified. In addition, if the circuit operation (addition/deletion) to the tunnel increases/decreases the total tunnel bandwidth, an FCIP Tunnel (VE port) disable/enable sequence should be performed after the addition/deletion of the circuit. This allows the switch to adjust the internal routes to utilize the new bandwidth fully. • Switching modes between 10 Gbps and 1 Gbps is disruptive for FCIP traffic. • The FCIP Circuit Keep alive timeout has a Fabric OS default value of 10000 ms (10 seconds). If FICON is configured, the recommended value is 1000 ms (1 second). The Keep Alive value needs to be set based on the application needs. If the local and remote circuit configurations' Keep Alive Timeout values do not match, the tunnel uses the lower of the two configured values. • The configured FCIP Circuit Keep Alive Timeout should be set to the same value on both ends of the FCIP connections. • To perform the following operations, delete the FCIP configuration on the affected ports first: • Switching modes between 1 Gbps/10 Gbps/Dual • Moving VE/GE port between logical switches • Cleaning up the configuration before removing the blade • Inband Management on the HP 1606 SAN Extension Switch or HP DC SAN Director Multiprotocol Extension Blade has the following restrictions: • Firmwaredownload over the Inband interface is not supported. • IPv6 addressing is not supported. • Fabric OS 7.0.0a supports up to six 1Gbps circuits on HP 1606 SAN Extension Switch and up to ten 1 Gbps circuits on HP DC SAN Director Multiprotocol Extension Blade per VE/FCIP Tunnel on 1 GbE interfaces. As a best practice, the FC-traffic through VE tunnel should not exceed recom- 32