Fabric OS 6.2 administrator guide 465
The following example shows the
portShow fcipTunnel
command used to display IPsec
information for tunnel 3:
switch:admin>
portshow fciptunnel 8/ge0 3 -ipsec
Port: ge0
-------------------------------------------
Tunnel ID 3
Remote IP Addr 192.175.5.200
Local IP Addr 192.175.5.100
Remote WWN Not Configured
Local WWN 10:00:00:05:1e:37:00:20
Compression off
Fastwrite on
Tape Pipelining on
Uncommitted bandwidth, minimum of 1000 Kbps (0.001000 Gbps)
SACK on
Min Retransmit Time 100
Keepalive Timeout 80
Max Retransmissions 9
Status : Active
Connected Count: 1
Uptime 1 hour, 16 minutes, 4 seconds
IKE Policy 7
-----------------------------------------
Authentication Algorithm: MD5
Encryption: 3DES
Perfect Forward Secrecy: off
Diffie-Hellman Group: 1
SA Life (seconds): 200000
IPSec Policy 7
-----------------------------------------
Authentication Algorithm: AES-XCBC
Encryption: 3DES
SA Life (seconds): 1500000
Pre-Shared Key 1234567890123456
Virtual Fabrics and FCIP
Any GigE_Port and all of its associated FCIP tunnels on a chassis can be assigned to any Logical Switch.
As with the current Fabric OS, the port types supported by FCIP are either VE_ or VEX_Port. When a GigE
port is moved to a Logical Switch, all eight VE_ and VEX_Ports are automatically moved. There is no
interaction required to assign or move them.
The following constraints on VE_ and VEX_Ports apply:
•
All VEX_Ports will be persistently disabled when Virtual Fabric mode is enabled. You need to create a
Logical Switch with the base switch attribute turned on and move the ports to the new base switch.
•
The ports must be offline before they are moved from one Logical Switch to another.
•
A Logical Switch is independent of the base switch. Therefore all GigE_Port based protocol addresses,
such as IP addresses, must be unique within a Logical Switch.
•
FCIP tunnels working as an extended ISL can carry traffic for multiple fabrics. Therefore a GigE_Port
used as an extended ISL must be assigned to the base switch.
TCP Byte Streaming
TCP Byte Streaming allows an HP StorageWorks 400 Multi-Protocol Router or a B-Series Multi-Protocol
Router Blade to communicate with supported third party WAN optimization hardware connected on the
GigE ports configured for FCIP. This feature is enabled when configuring the FCIP tunnel.
Содержание A7533A - Brocade 4Gb SAN Switch Base
Страница 1: ...HP StorageWorks Fabric OS 6 2 administrator guide Part number 5697 0016 Edition May 2009 ...
Страница 24: ...24 ...
Страница 99: ...Fabric OS 6 2 administrator guide 99 ...
Страница 100: ...100 Managing user accounts ...
Страница 118: ...116 Configuring standard security features ...
Страница 164: ...162 Configuring advanced security features ...
Страница 234: ...232 Installing and maintaining firmware ...
Страница 268: ...266 Administering advanced zoning ...
Страница 284: ...282 Configuring Enterprise class platforms ...
Страница 292: ...290 Routing traffic ...
Страница 294: ...292 Interoperability for merged SANs ...
Страница 302: ...300 Configuring the Distributed Management Server ...
Страница 334: ...332 iSCSI gateway service ...
Страница 340: ...338 Administering NPIV ...
Страница 407: ...Fabric OS 6 2 administrator guide 405 ...
Страница 408: ...406 Using the FC FC routing service ...
Страница 438: ...434 Administering extended fabrics ...
Страница 460: ...456 Administering ISL trunking ...
Страница 498: ...494 Configuring and monitoring FCIP extension services 556200 Bps 30s avg 491394 Bps lifetime avg ...
Страница 516: ...512 FICON fabrics ...
Страница 526: ...522 Configuring and monitoring FICON Extension Services ...
Страница 540: ...536 Configuring the PID format ...
Страница 544: ...540 Understanding legacy password behavior ...
Страница 546: ...542 Mixed fabric configurations for non merge SANs ...
Страница 550: ...546 Migrating from an MP Router to a 400 MP Router ...
Страница 558: ...554 Inband Management ...
Страница 572: ...568 ...