MONIT CONFIGURATION EXAMPLES SERIES
MONIT CONFIGURATION EXAMPLES MAC

The new session configuration is added to the existing session configuration.Įnters the monitor configuration mode. (Optional) Repeat Steps 2 and 3 to configure monitoring on additional SPAN destinations.Ĭlears the configuration of the specified SPAN session.

MONIT CONFIGURATION EXAMPLES MAC

Switchport mode Ĭonfigures the switchport mode for the selected slot and port or range of ports.Ĭonfigures the switchport interface as a SPAN destination:Īllows the SPAN destination port to inject packets that disrupt a certain TCP packet stream, for example, in networks with IDS.Īllows the SPAN destination port to inject packets, and allows the learning of MAC addresses, for example, the IDS MAC address. However, they cannot be configured as SPAN destinations.Įnters interface configuration mode on the selected slot and port or range of ports.Ĭonfigures switchport parameters for the selected slot and port or range of ports.

MONIT CONFIGURATION EXAMPLES SERIES

Beginning with Cisco NX-OS Release 5.2, the Cisco Nexus 2000 Series Fabric Extender interfaces and the fabric port channels connected to the Cisco Nexus 2000 Series Fabric Extender can be configured as SPAN sources.If you span a core interface when inter-VLAN routing is enabled across L2MP, it is not possible to capture the traffic egressing out of the core interface.If the SPAN source traffic exceeds the capacity of the SPAN destination, packet drops might occur on the SPAN source interfaces. When using SPAN sessions on F1 Series modules, ensure that the total amount of source traffic in a given session is less than or equal to the capacity of the SPAN destination interface or port channel for that session.An F1 Series module interface cannot be configured as Layer 3, but it can receive Layer 3 traffic in a SPAN destination mode. Packets from Layer 3 sources can be spanned and directed to an F1 Series module SPAN destination. F1 Series modules are Layer 2 domain line cards.However, a FabricPath core port can be configured as a SPAN source interface. A FabricPath core port is not supported as a SPAN destination when an F1 Series module is present in a VDC.A maximum of two bidirectional sessions are supported when an F1 Series module is present in a VDC.If multiple SPAN destinations are configured in a SPAN session, the session is disabled until the F1 Series module is powered down or moved to another VDC or the multiple SPAN destinations are reduced to a single destination. Multiple SPAN destinations are not supported when an F1 Series module is present in a VDC.You can configure a SPAN session on the local device only.You can configure an RSPAN VLAN for use only as a SPAN session source.Inband traffic from all VDCs is monitored. You can monitor the inband interface only from the default VDC.VLAN SPAN monitors only the traffic that leaves or enters Layer 2 ports in the VLAN.For VLAN SPAN sessions with both ingress and egress configured, two packets (one from ingress and one from egress) are forwarded from the destination port if the packets get switched on the same VLAN.Some examples of this behavior on source ports include: When a SPAN session contains source ports that are monitored in the transmit or transmit and receive direction, packets that these ports receive may be replicated to the SPAN destination port even though the packets are not actually transmitted on the source ports.SPAN output includes Bridge Protocol Data Unit (BPDU) Spanning-Tree Protocol hello packets.

Destination ports do not participate in any spanning tree instance.

– The inband interface to the control plane CPU – VLANs, which can be assigned to port channel subinterfaces

A single SPAN session can include mixed sources in any combination of the following:.

You cannot configure a port as both a source and destination port.

A destination port can only be configured in one SPAN session at a time.

All SPAN replication is performed in the hardware.

SPAN is not supported for management ports.

SPAN has the following configuration guidelines and limitations:Ĭisco Nexus 7000 Series NX-OS Verified Scalability Guide

Monit configuration examples