Service Manual
Conguring the Encapsulated Remote Port Mirroring
The ERPM session copies trac from the source ports/lags or source VLANs and forwards the trac using routable GRE-
encapsulated packets to the destination ip address specied 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 congured ip route (static or dynamic)
• The system MTU should be congured 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 dened 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 specied in case of source as vlan or where monitoring on a per ow
basis is desired.
• The keyword monitor should have been specied in the access list rules for which we need to mirror.
• The maximum number of source ports that can be dened in a session is 128.
• The system allows to congure upto 4 ERPM sessions.
• ERPM sessions do not copy locally sourced Remote-VLAN trac from source trunk ports that carry RPM VLANs. ERPM
sessions do not copy locally sourced ERPM GRE-encapsulated trac 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 trac.
• Same port can be congured as both source and destination in an ERSPAN session.
• TTL and ToS values can be congured in IP header of ERSPAN trac.
Conguration steps for ERPM
ERPM sample steps for conguring the Source sessions
Step
Command Purpose
1 congure terminal
Enter global conguration mode.
2
monitor session <id> type erpm The <id> needs to be unique and not already dened
in the box specifying type as 'erpm' denes 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
specied 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.
Port Monitoring
599










