Users Guide

Configure source and destination port, and traffic direction
OS10(conf-mon-local-1)# source interface Eth1/1/1 rx
OS10(conf-mon-local-1)# destination interface Eth1/1/2
OS10(conf-mon-local-1)# no shut
View configured monitoring sessions
In the State field, true indicates that the port is enabled. In the Reason field, Is UP indicates that hardware resources are
allocated.
OS10# show monitor session all
S.Id Source Destination Dir SrcIP DstIP DSCP TTL State Reason
----------------------------------------------------------------------
1 ethernet1/1/7 ethernet1/1/1 rx N/A N/A N/A N/A true Is UP
Remote port monitoring
Remote port monitoring monitors ingress traffic, egress traffic, or both, on multiple source ports of multiple devices.
It forwards the monitored traffic to multiple destination ports on different remote devices. Remote port monitoring helps
network administrators monitor and analyze traffic to troubleshoot network problems.
In a remote port monitoring session, monitored traffic is tagged with a VLAN ID and switched on a user-defined, nonroutable
L2 VLAN. The VLAN is reserved to carry only monitored traffic, which is forwarded on all egress ports of the VLAN. You must
configure each intermediate switch that participates in transporting the monitored traffic with the reserved L2 VLAN.
In the following diagram, the source port (Eth 1/1/26:1) is on one switch, and destination port (Eth 1/1/26:1) is on the other
switch. The source port forwards the packet copy to the destination port through the uplink connection. This enables data
monitoring and analysis across devices.
Session and VLAN requirements
Remote port monitoring requires configuring source and destinations sessions, and also a tagged VLAN for transporting
monitored traffic.
RPM requires the following:
● Source session, such as monitored ports on different source devices.
● Reserved tagged VLAN for transporting monitored traffic configured on source, intermediate, and destination devices.
698
Layer 2