Service Manual

Conguring Remote Port Mirroring
Remote port mirroring requires a source session (monitored ports on dierent source switches), a reserved tagged VLAN for
transporting mirrored trac (congured on source, intermediate, and destination switches), and a destination session (destination
ports connected to analyzers on destination switches).
Conguration Notes
When you congure remote port mirroring, the following conditions apply:
• You can congure any switch in the network with source ports and destination ports, and allow it to function in an intermediate
transport session for a reserved VLAN at the same time for multiple remote-port mirroring sessions. You can enable and disable
individual mirroring sessions.
• BPDU monitoring is not required to use remote port mirroring.
• A remote port mirroring session mirrors monitored trac by prexing the reserved VLAN tag to monitored packets so that they
are copied to the reserve VLAN.
• Mirrored trac is transported across the network using 802.1Q-in-802.1Q tunneling. The source address, destination address and
original VLAN ID of the mirrored packet are preserved with the tagged VLAN header. Untagged source packets are tagged with
the reserve VLAN ID.
• The RPM VLAN can’t be a Private VLAN.
• The RPM VLAN can be used as GVRP VLAN.
• The L3 interface conguration should be blocked for RPM VLAN.
• The member port of the reserved VLAN should have MTU and IPMTU value as MAX+4 (to hold the VLAN tag parameter).
• To associate with source session, the reserved VLAN can have at max of only 4 member ports.
• To associate with destination session, the reserved VLAN can have multiple member ports.
• Reserved Vlan cannot have untagged ports
In the reserved L2 VLAN used for remote port mirroring:
558
Port Monitoring