Endpoint Switches And Intermediate Devices; Updating From A Legacy Mirroring Configuration - ProCurve 6200yl Management And Configuration Manual

Monitoring and Analyzing Switch Operation
Traffic Mirroring
N o t e s
N o t e s
B-30

Endpoint Switches and Intermediate Devices

The endpoint switches used for remote mirroring source and remote mirroring
exit functions must be ProCurve switches that support the mirroring functions
described in this chapter. However, because remote mirroring on your
ProCurve switch uses IPv4 encapsulation of mirrored traffic to remote desti-
nation switches, the intermediate switches and routers in a layer 2/3 domain
can be from any vendor supporting IPv4.
The exit interface for a mirroring destination must be an individual port.
The switch mirrors traffic on static trunks, but not on dynamic LACP trunks.
The switch mirrors traffic at line rate. When mirroring multiple interfaces in
networks with high traffic levels, it is possible to copy more traffic to a
mirroring destination than the link supports. In this case, some mirrored
traffic may not reach the destination. If you are mirroring a high traffic volume,
distribute the load to multiple exit ports if possible.

Updating from a Legacy Mirroring Configuration

On a switch running a software version earlier than K.12.xx and also config-
ured for mirroring, downloading and booting from software release K.12.xx
or greater produces the following mirroring configuration:
The legacy port or VLAN mirroring configuration maps to session 1.
■
Selection criteria for session 1 is set to both (that is, mirroring traffic
■
entering and leaving the switch on the configured interface).
■ The local exit port in the legacy configuration is applied to session 1.
Booting from Software Versions Earlier than K.12.xx: If it is necessary
to boot the switch from a legacy (pre-K.12.xx) software version after using
version K.12.xx or greater to configure mirroring, remove mirroring from the
configuration before booting with the earlier software.
Maximum Supported Frame Size: The IPv4 encapsulation of mirrored
traffic adds a 54-byte header to each mirrored frame. If a resulting frame
exceeds the MTU (Maximum Transmission Unit) allowed in the path from the
mirroring source to the mirroring destination, the frame is dropped. For more
information, refer to "Maximum Supported Frame Size" on page B-69.
No Frame Truncation: Mirroring does not truncate frames, and oversized
mirroring frames will be dropped. Also, remote mirroring does not allow
downstream devices in a mirroring path to fragment mirrored frames.