Cisco Cisco Gigabit Ethernet Switch Module (CGESM) for HP Release Notes

An egress SPAN copy of routed unicast traffic might show an incorrect destination MAC address on 
both local and remote SPAN sessions. This limitation does not apply to bridged packets. The 
workaround for local SPAN is to use the replicate option. For a remote SPAN session, there is no 
workaround. 

This is a hardware limitation: (CSCdy72835)

Egress SPAN routed packets (both unicast and multicast) show the incorrect source MAC address. 
For remote SPAN packets, the source MAC address should be the MAC address of the egress VLAN, 
but instead the packet shows the MAC address of the RSPAN VLAN. For local SPAN packets with 
native encapsulation on the destination port, the packet shows the MAC address of VLAN 1. This 
problem does not appear with local SPAN when the encapsulation replicate option is used. This 
limitation does not apply to bridged packets. The workaround is to use the encapsulate replicate 
keywords in the monitor session global configuration command. Otherwise, there is no 
workaround. 

This is a hardware limitation: (CSCdy81521)

During periods of very high traffic, when two RSPAN source sessions are configured, the VLAN ID 
of packets in one RSPAN session might overwrite the VLAN ID of the other RSPAN session. If this 
occurs, packets intended for one RSPAN VLAN are incorrectly sent to the other RSPAN VLAN. 
This problem does not affect RSPAN destination sessions. The workaround is to configure only one 
RSPAN source session. 

This is a hardware limitation: (CSCed24036)

Cisco Discovery Protocol (CDP), VLAN Trunking Protocol (VTP), and Port Aggregation Protocol 
(PAgP) packets received from a SPAN source are not sent to the destination interfaces of a local 
SPAN session. The workaround is to use the monitor session session_number destination 
{interface interface-id encapsulation replicate} global configuration command for local SPAN. 

The switch treats frames received with mixed encapsulation (802.1Q and Inter-Switch Link [ISL]) 
as frames with FCS errors, increments the error counters, and causes the LED to blink amber. This 
happens when an ISL-unaware device receives an ISL-encapsulated packet and forwards the frame 
to an 802.1Q trunk interface. There is no workaround. (CSCdz33708)

IP traffic with IP options set is sometimes leaked on a trunk port. For example, a trunk port is a 
member of an IP multicast group in VLAN X but is not a member in VLAN Y. If VLAN Y is the 
output interface for the multicast route entry assigned to the multicast group and an interface in 
VLAN Y belongs to the same multicast group, the IP-option traffic received on an input VLAN 
interface other than one in VLAN Y is sent on the trunk port in VLAN Y because the trunk port is 
forwarding in VLAN Y, even though the port has no group membership in VLAN Y. There is no 
workaround. (CSCdz42909)

For trunk ports or access ports configured with 802.1Q tagging, inconsistent statistics might appear 
in the show interfaces counters privileged EXEC command output. Valid 802.1Q frames of 64 to 
66 bytes are correctly forwarded even though the port LED blinks amber, and the frames are not 
counted on the interface statistics. There is no workaround. (CSCec35100)