HP StorageWorks Fabric OS 5.1.1b Release Notes (AA-RWEEG-TE, April 2007)

If a port is configured as an EX_Port:
• Frame-based trunking, which is typically enabled automatically or configured
manually using the portCfgTrunkPort command,isnotsupported.
• However, Dynamic Path Select (DPS), or exchange-based load-balancing, is
supported on equal cost links whether they are E_Ports, EX_Ports, VE_Ports, or
VEX_Ports.(NotethatyoucandisableDPSusingtheaptPolicy command.)
NOTE:
You cannot connect the E_Port of a switch running Fabric OS 2.x to an EX_Port on an
HP StorageWorks 400 MP Router or B-Series MP Router blade.
GbE_ports
Several new commands have been added to support GbE_Ports and several existing
commands will not work with the GbE_Ports (see “Unsupported Commands”).
Frame-based trunking is not supported over G bE_Ports, but DPS (exchange-based
loadbalancing) is supported and is always on. GbE_Por ts or tunnels are as long as
the cost paths are the same. (Note that you can disable DPS using the aptPolicy
command.)
GbE_Port features include:
• The GbE_Ports are set to 1-Gbit/sec speed and duplex settings cannot be
changed.
• Neither Fabric Watch nor Advanced Performance Monitoring is supported on
GbE_Ports, nor are they suppor ted on the virtual tunnel VE_Ports and VEX_Ports.
• For each FC-IP tunnel, two TCP connections are established between the end
points. The first, running at TCP port, 3225 carries all Fibre Channel Class F
(control) traffic. The second, running on TCP por t 3226, ca rries all Fi bre Channel
Class 2 and 3 (data) traffic.
VE_Por ts and VEX_Ports (over GbE)
VE_Ports and VEX_Ports are virtual ports (that represent each FC -IP tunnel, up to eight per
GbE_Port) over the physical GbE link. VE_Ports are essentially tunneled E_Por ts over an
IP network via FC-IP. VEX_Ports are routed VE_P orts, just as EX_Ports are routed E_P orts.
VE_Ports and VEX_Ports have the same behavior and functionality.
NOTE:
At this time, you cannot connect both a VEX_Port and an EX_Port to the sam e edge
fabric.
12