Configuring The Encapsulated Remote Port Mirroring; Configuration Steps For Erpm - Dell Z9000 Configuration Manual

Configuring the Encapsulated Remote Port Mirroring

The ERPM session copies traffic from the source ports/lags or source VLANs and forwards the traffic
using routable GRE-encapsulated packets to the destination ip address specified 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 configured ip route (static or dynamic)
• The system MTU should be configured 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 defined in the box but it should be unique
and should not be assigned to any other system in the network.
• The keyword 'flow-based enable' should have been specified in case of source as vlan or where
monitoring on a per flow basis is desired.
• The keyword monitor should have been specified in the access list rules for which we need to
mirror.
• The maximum number of source ports that can be defined in a session is 128.
• The system allows to configure upto 4 ERPM sessions.
• ERPM sessions do not copy locally sourced Remote-VLAN traffic from source trunk ports that
carry RPM VLANs. ERPM sessions do not copy locally sourced ERPM GRE-encapsulated traffic
from source ports.
• Source Vlan monitoring can be done only for ingress packets and is not supported for egress
direction.

Configuration steps for ERPM

ERPM sample steps for configuring the Source sessions
Step Command
1 configure terminal
2
monitor session <id> type erpm
3 source Interface | Range
4
direction
5
erpm source-ip <id> dest-ip <id>
620
Purpose
Enter global configuration mode.
The <id> needs to be unique and not
already defined in the box specifying type
as 'erpm' defines a RPM session.
Specify the port or list of ports that needs
to be monitored
Specify rx, tx or both in case to monitor
ingress/egress or both ingress and egress
packets on the specified port..
Specify the source ip address and the
destination ip where the packet needs to
be sent.
Port Monitoring