Users Guide

Session and VLAN requirements
Remote port monitoring requires a source session (monitored ports on dierent source devices), a reserved tagged VLAN for transporting
monitored trac (congured on source, intermediate, and destination devices), and a destination session (destination ports connected to
analyzers on destination devices).
• Congure any network device with source ports and destination ports and enable it to function in an intermediate transport session for
a reserved VLAN at the same time for multiple remote port monitoring sessions. Enable and disable individual monitoring sessions.
• A remote port monitoring session mirrors monitored trac by prexing the reserved VLAN tag to monitored packets to transmit using
the reserved VLAN.
• The source address, destination address, and original VLAN ID of the mirrored packet are prexed 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 source session, the reserved VLAN can have a maximum of four member ports.
• To associate with destination session, the reserved VLAN can have multiple member ports.
• The reserved VLAN cannot have untagged ports.
Reserved L2 VLAN
• 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.
• In monitored trac, packets that have the same destination MAC address as an intermediate or destination device in the path used by
the reserved VLAN to transport the mirrored trac are dropped by the device that receives the trac if the device has a L3 VLAN
congured.
Source session
• Congure physical ports and port-channels as sources in remote port monitoring and use them in the same source session. You can use
both L2 (congured with the switchport command) and L3 ports as source ports. Optionally congure one or more source VLANs
to congure the VLAN trac to be monitored on source ports.
• 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 (flow-based enable).
• In a source VLAN, only received (rx) trac is monitored.
• In S5148F-ON, 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 rspan-source
186
Layer 2