ProCurve 3500yl Series, Руководство по управлению и настройке

Страница: 562 / 732

B-32
Monitoring and Analyzing Switch Operation
Traffic Mirroring
N o t e
Using the CLI, you can access all mirroring capabilities on the switch. Using
the Menu or Web interfaces, you can configure and display only session 1 and
only as a local mirroring session for traffic in both directions on the specified
interface. If session 1 has been configured in the CLI for local mirroring for
inbound-only or outbound-only traffic, then using the Menu or Web interface
to change the session 1 configuration
automatically reconfigures the session
to monitor both inbound and outbound traffic on the interface. (If session 1
has been configured in the CLI with an ACL or as a remote mirroring session,
then the Menu and Web interfaces cannot be used to configure a mirroring
session.) The CLI can configure sessions 1 - 4 for local or remote mirroring in
any combination, and can be used to override a Menu or Web interface
configuration of session 1. Using SNMP allows the same capability and effect
as the CLI
except that SNMP cannot be used to configure any ACL mirroring.
(SNMP can overwrite an existing configuration for any session.)
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.
N o t e s
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.
3500-5400-6200-8200-MCG-Jan08-K_13_01.book Page 32 Monday, January 28, 2008 10:04 AM