8. Traffic
Monitoring
MN700004 Rev 01
69
Supported Standards, MIBs and RFCs
Standards
No standards are supported by this feature.
MIBs
No MIBs are supported by this feature.
RFCs
No RFCs are supported by this feature.
Prerequisites
You cannot define different monitoring directions (transmit, receive) for both a VLAN list
and an interface list concurrently (such as the transmit source defined to be a VLAN list and
the receive source defined to be an interface list in the same monitoring session).
Up to of eight ports can be monitored on the transmitted traffic. If a VLAN list is monitored,
only the first eight ports will be monitored.
The monitored VLANs must be defined before adding them to the monitor session.
The monitor session will start to function only when the analyzer port (destination) is set by
the
monitor session destination
command in Global Configuration mode.
When activating a monitor session on a port list, the analyzer port (destination) is
automatically removed from all the VLANs in which it was a member and automatically
added as an untagged member to all the VLANs in which the monitored ports are members.
When activating monitor session on VLAN list, the analyzer port (destination) is
automatically removed from all the VLANs it was member in, and automatically as untagged
member added to all the monitored VLANs.
When the monitor session is disabled, the destination port is automatically removed from all
the VLANs and added as an untagged member to the default VLAN (VLAN ID 1).
Do not add the analyzer port to VLANs. It can affect the monitor session operation.
Default Traffic Monitoring Configuration
Table 8-1 shows the default traffic monitoring configuration.