Connectivity Guide
View monitoring session
OS10(conf-mon-rpm-source-10)# do show monitor session all
S.Id Source Destination Dir SrcIP DstIP DSCP TTL State Reason
---------------------------------------------------------------
1 vlan10 vlan 100 rx N/A N/A N/A N/A true Is UP
Encapsulated remote port monitoring
You can also have the monitored trac transmitted over an L3 network to a remote analyzer. The encapsulated remote port monitoring
(ERPM) session mirrors 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.
Consider the following when conguring an ERPM session:
• OS10 supports only the ERPM source session. The encapsulated packets terminate at the destination IP address, the remote analyzer.
• The source IP address must be a valid local IP address for the session.
• The destination IP address must be on a remote L3 node that supports standard GRE decapsulation.
• If the destination IP address is not reachable, the session goes down.
• OS10 does not support an ERPM destination session and decapsulation of ERPM packets at the destination switch.
• You can congure a maximum of four ERPM sessions with a maximum of 128 source ports in each session. You can congure these
four ERPM sessions in one of the following methods:
– Single directional with either four ingress or four egress sessions.
– Bidirectional with two ingress and two egress sessions.
• You can monitor a source VLAN only through ow-based monitoring. Only ingress is supported in 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 a GRE tunnel as a source interface.
• ERPM supports only GRE-over-IPv4 tunneling.
• ERPM does not support Equal cost multi-path (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 time-to-live (TTL) and dierentiated services code point (DSCP) values.
1 Create monitoring session in CONFIGURATION mode.
monitor session session-id type erpm-source
2 Congure source port in MONITOR-SESSION mode.
source interface interface-type {both | rx | tx}
3 Congure source and destination IP addresses, and protocol type in MONITOR-SESSION mode.
source-ip source ip-address destination-ip destination ip-address [gre-protocol protocol-
value
]
4 Congure TTL and DSCP values in MONITOR-SESSION mode.
ip {ttl ttl-number | dscp dscp-number}
5 Enable the monitoring interface in MONITOR-SESSION mode.
no shut
Layer 2
377