Filter
Top Products
Monitoring and Analyzing Switch Operation
Traffic Mirroring
Viewing the Mirroring Configurations in the Running
Configuration File
Using the show run command, you can view the current mirroring configura-
tions on the switch. In the show run command output, information about
mirroring sources in configured sessions begins with the mirror keyword;
monitored source interfaces are listed per-interface. For example:
ProCurve(config)# show run
Running configuration:
; J8697A Configuration Editor; Created on release #K.12.XX
max-vlans 300
ip access-list extended "100"
10 permit icmp 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255 0
exit
no ip address
exit
. . .
mirror 1 port B3
mirror 2 name "test-10" remote ip 10.10.10.1 8010 10.10.30.2
Mirroring sessions with exit ports configured
on the switch: B3 is an exit port for a local
session; session 2 has a remote destination
and exit port.
. . .
interface B1
monitor all Both mirror 2
exit
. . .
monitor ip access-group "100" In mirror 1
Selection criteria used to monitor traffic
on port B1 for mirroring sessions 1 (ACL-
based) and 2 (direction -based)
Figure B-46. Displaying Mirroring Sources and Sessions in the Running Configurations
Information about remote endpoints configured for remote sessions on the
switch begin with the mirror endpoint keywords. In the following example, two
remote sessions use the same exit port:
ProCurve(config)# show run
Running configuration:
; J8693A Configuration Editor; Created on release #K.12.XX
module 3 type J8694A
Remote endpoints configured on the switch, including source IP address,
UDP port number, destination IP address, and remote exit port. Each
remote session is identified by a unique UDP port number.
. . .
mirror endpoint ip 10.10.20.1 8010 10.10.30.2 port 4
mirror endpoint ip 10.10.51.10 7955 10.10.30.2 port 4
. . .
Figure B-47. Displaying Remote Mirroring Endpoints in the Running Configuration
B-86