Skip to main content
Sign Out

Welcome to Dell

My Account
  • Place orders quickly and easily
  • View orders and track your shipping status
  • Create and access a list of your products
  • Manage your Dell EMC sites, products, and product-level contacts using Company Administration.
Sign In Create an Account Premier Sign In Partner Program Sign In
Contact Us

Your Dell.com Carts

Dell EMC SmartFabric OS10 User Guide Release 10.5.0

PDF

Session and VLAN requirements

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.
  • 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.

Consider the following when configuring an RPM session:

  • A remote port monitoring session mirrors monitored traffic by prefixing 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 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.

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 traffic, if the device has an L3 VLAN configured, packets that have the same destination MAC address as an intermediate or destination device in the path the reserved VLAN uses to transport the mirrored traffic are dropped by the device that receives the traffic .

Source session

  • 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 configure the VLAN traffic to be monitored 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.

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.

Rate this content

Accurate
Useful
Easy to understand
Was this article helpful?
0/3000 characters
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please provide ratings (1-5 stars).
  Please select whether the article was helpful or not.
  Comments cannot contain these special characters: <>()\