Users Guide

• Use the default VLAN and native VLANs as a source VLAN.
• You cannot congure the dedicated VLAN used to transport mirrored trac as a source VLAN.
Restrictions
• When you use a source VLAN, enable ow-based monitoring using the flow-based enable command.
• In a source VLAN, only received (rx) trac is monitored.
• You cannot congure a source port-channel or source VLAN in a source session if the port-channel or VLAN has a member port
congured as a destination port in a remote port monitoring session.
• You cannot use a destination port for remote port monitoring as a source port, including the session the port functions as the
destination port.
• The reserved VLAN used to transport mirrored trac must be a L2 VLAN.; L3 VLANs are not supported.
Congure remote port monitoring
Remote port monitoring requires a source interface, monitored ports on dierent source network devices, and a reserved tagged VLAN for
transporting mirrored trac congured on the source, intermediate, and destination devices.
1 Create a remote monitoring session in CONFIGURATION mode.
monitor session session-id type rpm-source
2 Enter the source to monitor trac in MONITOR-SESSION mode.
source interface interface-range direction
3 Enter the destination to send the trac to in MONITOR-SESSION mode.
destination remote-vlan vlan-id
4 Enable the monitoring interface in MONITOR-SESSION mode.
no shut
Create remote monitoring session
OS10(config)# monitor session 10 type rpm-source
OS10(conf-mon-rpm-source-10)#
Congure source and destination port, and trac direction
OS10(conf-mon-rpm-source-10)# source interface vlan 10 rx
OS10(conf-mon-rpm-source-10)# destination remote-vlan 100
OS10(conf-mon-rpm-source-10)# no shut
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 trac transmitted over an L3 network to a remote analyzer. The encapsulated remote port monitoring
(ERPM) session mirrors trac from the source ports, LAGs or source VLANs and forwards the trac using routable GRE-encapsulated
packets to the destination IP address specied in the session.
Consider the following when conguring 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.
444
Layer 2