4. Create Source RPM session as follows (port-channel 1 and port-channel 2 are LACP).
Dell(conf)#monitor session 1 type rpm
Dell(conf-mon-sess-1)#source port-channel 1 destination remote-vlan 10
dir rx
Dell(conf-mon-sess-1)#no disable
5. Show the output for the LACP.
Dell#show interfaces port-channel brief
Codes: L - LACP Port-channel
O - OpenFlow Controller Port-channel
LAG Mode Status Uptime Ports
L1 L3 up 00:01:17 Te 1/4 (Up)
L2 L2 up 00:00:58 Te 1/5 (Up)
Dell#
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.
Changes to Default Behavior
• Rate-limiting ïs no longer done for ERSPAN traffic.
• Same port can be configured as both source and destination in an ERSPAN session.
• TTL and ToS values can be configured in IP header of ERSPAN traffic.
764
Port Monitoring
To Next Page
Loading...
Need help?
General