◦ The monitored interface (A1) and exit port (B7) are on different switches.
◦ Mirrored traffic can be bridged or routed from a source switch to a remote switch.
Figure 64: Local and remote sessions showing mirroring terms
Mirroring destinations
Traffic mirroring supports destination devices that are connected to the local switch or to a remote switch:
Traffic can be copied to a destination (host) device connected to the same switch as the mirroring source in a
local mirroring session. You can configure up to four exit ports to which destination devices are connected.
Mirroring sources and sessions
Traffic mirroring supports the configuration of port in up to
four
mirroring sessions on a switch. Each session can
have one or more sources (ports and/or static trunks) that monitor traffic entering and/or leaving the switch.
NOTE:
Using the CLI, you can make full use of the switch's local and remote mirroring capabilities.
Mirroring sessions
A mirroring session consists of a mirroring source and destination (endpoint.) Although a mirroring source can be
one of several interfaces, as mentioned above, for any session, the destination must be a single (exit) port. The
exit port cannot be a trunk.
You can map multiple mirroring sessions to the same exit port, which provides flexibility in distributing hosts, such
as traffic analyzers or an IDS. In a remote mirroring endpoint, the IP address of the exit port and the remote
destination switch.
426
Aruba 2930F / 2930M Management and Configuration Guide
for ArubaOS-Switch 16.08
