Users Guide

Conguring the Encapsulated Remote Port Mirroring
The ERPM session copies trac from the source ports/lags or source VLANs and forwards the trac using routable GRE-
encapsulated packets to the destination ip address specied in the session.
Important:
The steps to be followed for the ERPM Encapsulation :
• Dell Networking OS supports ERPM Source session only. The Encapsulated packets terminate at the destination ip or at
the analyzer.
• Make sure that the destination ip is reachable via the congured ip route (static or dynamic)
• The system MTU should be congured properly to accommodate the increased size of the ERPM mirrored packet.
• 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.
• The source IP address can be any port's ip address dened in the box but it should be unique and should not be assigned to
any other system in the network.
• The keyword ‘ow-based enable’ should have been specied in case of source as vlan or where monitoring on a per ow
basis is desired.
• The keyword monitor should have been specied in the access list rules for which we need to mirror.
• The maximum number of source ports that can be dened in a session is 128.
• The system allows to congure upto 4 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.
• Source Vlan monitoring can be done only for ingress packets and is not supported for egress direction.
Changes to Default Behavior
• Rate-limiting ïs no longer done for ERSPAN trac.
• Same port can be congured as both source and destination in an ERSPAN session.
• TTL and ToS values can be congured in IP header of ERSPAN trac.
Conguration steps for ERPM
ERPM sample steps for conguring the Source sessions
Step
Command Purpose
1 congure terminal
Enter global conguration mode.
2
monitor session <id> type erpm The <id> needs to be unique and not already dened
in the box specifying type as 'erpm' denes a RPM
session.
3 source Interface | Range
Specify the port or list of ports that needs to be
monitored
4
direction Specify rx, tx or both in case to monitor ingress/
egress or both ingress and egress packets on the
specied port..
5
erpm source-ip <id> dest-ip <id> Specify the source ip address and the destination ip
where the packet needs to be sent.
6
<no> ow-based enable Specify ow-based enable for mirroring on a ow by
ow basis and also for vlan as source.
648
Port Monitoring