Users Guide

● Destination session, where destination ports connect to analyzers on destination devices.
Configure any network device with source and destination ports. Enable the network device to function in an intermediate
transport session for a reserved VLAN for multiple remote port monitoring sessions. You can enable and disable individual
monitoring sessions.
VLAN requirements when configuring an RPM session:
● A remote port monitoring session mirrors the monitored traffic by prefixing the reserved VLAN tag to the monitored packets
to transmit using the reserved VLAN.
● The source address, destination address, and original VLAN ID of the mirrored packet are prefixed with the tagged VLAN
header. Untagged source packets are tagged with the reserved VLAN ID.
● The member port of the reserved VLAN must have the MTU and IPMTU value as MAX+4 to hold the VLAN tag parameter.
● To associate with the source session, the reserved VLAN can have up to four member ports.
● To associate with the destination session, the reserved VLAN can have multiple member ports.
● The reserved VLAN cannot have untagged ports.
Restrictions
When you configure an RPM session, VLAN has certain restrictions.
● When you use a source VLAN, enable flow-based monitoring using the flow-based enable command.
● In a source VLAN, only received (rx) traffic is monitored.
● If the port channel or VLAN has a member port configured as a destination port in a remote port monitoring session, you
cannot configure a source port channel or source VLAN in a source 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 traffic must be an L2 VLAN. L3 VLANs are not supported.
Reserved L2 VLAN
In an RPM session, the reserved VLAN is automatically disabled and the default VLAN ID is not supported.
● MAC address learning in the reserved VLAN is automatically disabled.
● There is no restriction on the VLAN IDs used for the reserved remote monitoring VLAN. Valid VLAN IDs are from 2 to 4093.
The default VLAN ID is not supported.
● When the traffic is monitored in a device where L3 VLAN is configured, the packets, which has the same MAC address as
that of an intermediate or destination device in the path that the VLAN uses to transport, the mirrored traffic is dropped by
the device that receives the traffic
Source session
In an RPM session, you can configure sources and use the different VLANs available as the source VLAN.
● Configure physical ports and port channels as sources in remote port monitoring and use them in the same source session.
You can use both L2, configured with the switchport command, and L3 ports as source ports. Optionally, to monitor the
configured VLAN traffic on source ports, configure one or more source VLANs.
● Use the default VLAN and native VLANs as a source VLAN.
● You cannot configure the dedicated VLAN used to transport mirrored traffic as a source VLAN.
Configure remote port monitoring
Remote port monitoring requires the following for transporting mirrored traffic configured on the source, intermediate, and
destination devices:
● A source interface
● Monitored ports on different source network devices
● A reserved tagged VLAN
1. Create a remote monitoring session in CONFIGURATION mode.
monitor session session-id type rpm-source
Layer 2
699