Deployment Guide

Scenario RPM Restriction Recommended Solution
Mirroring member port of ICL LAG to
Orphan Port of peer vlt device— In this
scenario, a member port of the ICL LAG or a
member port of the VLT LAG is mirrored to
an orphan port on the peer VLT device. The
packet analyzer is connected to the peer
VLT device.
The bandwidth of the VLTi link is
unnecessarily used by mirrored trac if max
rate limit value is congured in the RPM
mirror session.
None.
Mirroring member port of ICL LAG to VLT
LAG — In this scenario, a member port of
the ICL LAG is mirrored to the VLT LAG on
the same VLT device. The packet analyzer is
connected to the TOR switch.
No restrictions apply. The bandwidth of the
VLTi link is unnecessarily used by mirrored
trac if max rate limit value is congured in
the RPM mirror session.
If you want to mirror trac in the TOR
locally, use local Port mirroring session
instead of RPM.
Mirroring with a VLAN as source and
destination — If the members of the source
and destination VLANs are same in a single
monitoring session.
No restrictions apply. None.
Mirroring with an interface or LAG as source
and destination --- If the source and
destination interface or LAG of a monitor
session are same.
No restrictions apply. None.
Encapsulated Remote Port Monitoring
Encapsulated Remote Port Monitoring (ERPM) copies trac from source ports/port-channels or source VLANs and forwards the trac
using routable GRE-encapsulated packets to the destination IP address specied in the session.
NOTE
:
When conguring ERPM, follow these guidelines
• The Dell Networking OS supports ERPM source session only. Encapsulated packets terminate at the destination IP address or at
the analyzer.
• You can congure up to four ERPM source sessions on switch.
• Congure the system MTU to accommodate the increased size of the ERPM mirrored packet.
• The maximum number of source ports you can dene in a session is 128.
• The system encapsulates the complete ingress or egress data under GRE header, IP header, and outer MAC header and sends it
out at the next hop interface as pointed by the routing table.
• Specify flow-based enable in case of source as VLAN or where you need monitoring on a per-ow basis.
• Specify the monitor keyword in the access list rules for which you want to mirror.
• The system allows you to congure up to four ERPM sessions.
• ERPM sessions do not copy locally sourced remote VLAN trac from source trunk ports that carry RPM VLANs. ERPM sessions
do not copy locally sourced ERPM GRE-encapsulated trac from source ports.
• Flow-based mirroring is supported only for source VLAN ingress trac.
Changes to Default Behavior
• Rate-limiting is supported for the ERSPAN trac.
• You can congure the same port as both source and destination in an ERSPAN session.
• You can congure TTL and TOS values in the IP header of the ERSPAN trac.
Conguration steps for ERPM
616
Port Monitoring