Reference Guide
• OS10 does not support ERPM destination session and decapsulation of ERPM packets at the destination switch.
• You can congure a maximum of 4 ERPM sessions with a maximum of 128 source ports in each session. You can congure these 4
ERPM sessions in one of the following methods:
– Single directional with either 4 ingress or 4 egress sessions.
– Bidirectional with 2 ingress and 2 egress sessions.
• You can monitor a source VLAN only through ow-based monitoring. Only ingress is supported in a ow-based source VLAN
monitoring.
• You cannot congure an interface with ERPM trac as a source for an ERPM session.
• You cannot monitor an RPM VLAN as a source.
• You cannot congure the same destination IP address for two sessions.
• You cannot congure an interface that serves as egress for GRE tunnel as a source interface.
• ERPM supports only GRE over IPv4 tunneling.
• ERPM does not support ECMP.
• You can use third party devices as only tunnel-transit devices.
• OS10 does not support monitoring VLAN sub-interfaces and CPU generated packets.
Congure encapsulated remote port monitoring
Encapsulated remote port monitoring requires valid source and destination IP addresses. Ensure that the source IP address is local and
destination IP address is remote. You can also congure the TTL and DSCP values.
Create monitoring session
OS10(config)# monitor session 10 type erpm-source
S10(conf-mon-erpm-source-10)#
Congure source port, source and destination IP addresses, and protocol type
OS10(conf-mon-erpm-source-10)# source interface ethernet 1/1/2
OS10(conf-mon-erpm-source-10)# source-ip 1.1.1.1 destination-ip 3.3.3.3 gre-protocol 35006
OS10(conf-mon-erpm-source-10)# ip ttl 16
OS10(conf-mon-erpm-source-10)# ip dscp 63
OS10(conf-mon-erpm-source-10)# no shut
View congured ERPM session
OS10(conf-mon-erpm-source-6)# do show monitor session all
S.Id Source Destination Dir Mode Source IP Dest IP DSCP TTL Gre-
Protocol State Reason
------------------------------------------------------------------------------------------------
-----------------------------
6 ethernet1/1/2 remote-ip both port 1.1.1.1 3.3.3.3 63 16
35006 true Is UP
View running conguration of monitor session
OS10# show running-configuration monitor
!
monitor session 10 type erpm-source
source-ip 1.1.1.1 destination-ip 3.3.3.3
source interface ethernet1/1/2
no shut
Flow-based monitoring
Flow-based monitoring conserves bandwidth by inspecting only specied trac instead of all interface trac. Using ow-based monitoring,
you can monitor only trac received by the source port that matches criteria in ingress access-lists.
1 Enable ow-based monitoring for a monitoring session in MONITOR-SESSION mode.
flow-based enable
Layer 2
259