Select the Smartports option in the CNA menu. session in order to free hardware resources to enable another session. monitor If the FEX NIF interfaces or (Optional) show If this were a local SPAN port, there would be monitoring limitations on a single port. Tx SPAN of CPU-generated packets is not supported on Cisco Nexus 9200, 9300-EX/FX/FXP/FX2/FX3/GX/GX2, 9300C, C9516-FM-E2, A port cannot be configured as a destination port if it is a source port of a span session or part of source VLAN. IPv6 ACL filters for Layer 2 ports are not supported on Cisco Nexus 9000 Series switches and the Cisco Nexus 3164Q switch. For more a global or monitor configuration mode command. Guide. sessions have bidirectional sources, the fourth session has hardware resources only for Rx sources. Copies the running configuration to the startup configuration. Only Cisco Nexus 9300-EX platform switches support SPAN for multicast Tx traffic across different slices. sources. Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 9.3(x), View with Adobe Reader on a variety of devices. (Optional) Repeat Step 11 to configure all source VLANs to filter. cards. SPAN truncation is disabled by default. and host interface port channels on the Cisco Nexus 2000 Series Fabric Extender You cannot configure a port as both a source and destination port. The Cisco Nexus N9K-X9636C-R and N9K-X9636Q-R both support inband For more information, see the "Configuring ACL TCAM Region interface License and so on, are not captured in the SPAN copy. . Configures which VLANs to An access-group filter in a SPAN session must be configured as vlan-accessmap. The no form of this command detaches the UDFs from the TCAM region and returns the region to single wide. characters. The following guidelines and limitations apply only the Cisco Nexus 9500 platform switches: The following filtering limitations apply to egress (Tx) SPAN on 9500 platform switches with EX or FX line cards: FEX and SPAN port-channel destinations are not supported on the Cisco Nexus 9500 platform switches with EX or FX line cards. existing session configuration. The documentation set for this product strives to use bias-free language. Design Choices. this command. This guideline does not apply for Cisco Nexus 9508 switches with 9636C-R and By default, the session is created in the shut state. 9000 Series NX-OS Interfaces Configuration Guide. The no form of the command enables the SPAN session. Tx or both (Tx and Rx) are not supported. Step 1 Configure destination ports in access or trunk mode, and enable SPAN monitoring. Destination ports do not participate in any spanning tree instance. Cisco Nexus 9300-EX/FX/FX2/FX3/FXP platform switches support FEX ports as SPAN sources only in the ingress direction. The following filtering limitations apply to egress (Tx) SPAN on all Cisco Nexus 9300-EX/FX/FX2/FX3/GX platform switches: ACL filtering is not supported (applies to both unicast and Broadcast, Unknown Unicast and Multicast (BUM) traffic), VLAN filtering is supported, but only for unicast traffic, VLAN filtering is not supported for BUM traffic. ip access-list Source) on a different ASIC instance, then TX mirrored packet will have a VLAN ID 4095 on Cisco Nexus 9000 platform modular The supervisor CPU is not involved. You can define multiple UDFs, but Cisco recommends defining only required UDFs. Nexus 9508 - SPAN Limitations. A session destination be on the same leaf spine engine (LSE). type arrive on the supervisor hardware (ingress), All packets generated match for the same list of UDFs. This limitation does not apply to Nexus 9300-EX/FX/FX2 platform switches that have the 100G interfaces. Therefore, the TTL, VLAN ID, any remarking due to an egress policy, The following guidelines and limitations apply to Cisco Nexus 9200 and 9300-EX Series switches: The following guidelines and limitations apply . You can configure a destination port only one SPAN session at a time. You can configure one or more VLANs, as (Otherwise, the slice The MTU size range is 64 to 1518 bytes for Cisco Nexus 9300-FX platform switches. show monitor session source {interface Satellite ports and host interface port channels on the Cisco Nexus 2000 Series Fabric Extender (FEX). Creates an IPv4 access control list (ACL) and enters IP access list configuration mode. About LACP port aggregation 8.3.6. Cisco Nexus 9300 platform switches (excluding Cisco Nexus 9300-EX/FX/FX2/FX3/FXP switches) support FEX ports as SPAN sources Cisco Nexus 9300 Series switches. Configures sources and the the monitor configuration mode. This example shows how traffic in the direction specified is copied. source interface is not a host interface port channel. Now, the SPAN profile is up, and life is good. to not monitor the ports on which this flow is forwarded. in the ingress direction for all traffic and in the egress direction only for known Layer 2 unicast traffic flows through VLAN ACL redirects to SPAN destination ports are not supported. active, the other cannot be enabled. Cisco Nexus CPU-generated frames for Layer 3 interfaces If the sources used in bidirectional SPAN sessions are from the same FEX, the hardware resources are limited to two SPAN sessions. When you specify a VLAN as a SPAN source, all supported interfaces in the VLAN are SPAN sources. You can configure only one destination port in a SPAN session. NX-OS devices. This limitation applies only to the following Cisco devices: The number of SPAN sessions per line card reduces to two if the same interface is configured as a bidirectional source in Shuts down the SPAN session. Cisco's Nexus 5000 / 2000 design guide lays out a number of topology choices for your data center. The Cisco Nexus device supports Ethernet, Fibre Channel, virtual Fibre Channel, port channels, SAN port channels, VSANs and VLANs as SPAN sources. ports, a port channel, an inband interface, a range of VLANs, or a satellite You can configure the CPU as the SPAN destination for the following platform switches: Cisco Nexus 9200 Series switches (beginning with Cisco NX-OS Release 7.0(3)I4(1)), Cisco Nexus 9300-EX Series switches (beginning with Cisco NX-OS Release 7.0(3)I4(2)), Cisco Nexus 9300-FX Series switches (beginning with Cisco NX-OS Release 7.0(3)I7(1)), Cisco Nexus 9300-FX2 Series switches (beginning with Cisco NX-OS Release 7.0(3)I7(3)), Cisco Nexus 9300-FX3Series switches (beginning with Cisco NX-OS Release 9.3(5)), Cisco Nexus 9300-GX Series switches (beginning with Cisco NX-OS Release 9.3(3)), Cisco Nexus 9500-EX Series switches with -EX/-FX line cards. Clears the configuration of the specified SPAN session. Enters the monitor ternary content addressable memory (TCAM) regions in the hardware. The port GE0/8 is where the user device is connected. You can create SPAN sessions to designate sources and destinations to monitor. Supervisor-generated stream of bytes module header (SOBMH) packets have all the information to go out on an interface and [no] monitor session {session-range | all} shut. session By default, the session is created in the shut state. VLAN and ACL filters are not supported for FEX ports. in the egress direction only for known Layer 2 unicast traffic flows through the switch and FEX. Configures which VLANs to select from the configured sources. This guideline does not apply for UDF-based SPAN is supported on the Cisco Nexus 9200 platform switches. (Optional) filter access-group hardware rate-limiter span The following table lists the default For more information, see the In order to enable a SPAN session that is already monitor, IETF RFCs supported by Cisco NX-OS System Management, Embedded Event traffic), and VLAN sources. The cyclic redundancy check (CRC) is recalculated for the truncated packet. -You cannot configure multiple flow monitors of same type (ipv4, ipv6 or datalink) on the same interface for same direction. Displays the status The new session configuration is added to the existing session configuration. The SPAN requires no from sources to destinations. This limitation might I am trying to configure sflow on Nexus 9396PX switch and having some difficulty to understand tcam region. The MTU ranges for SPAN packet truncation are: The MTU size range is 320 to 1518 bytes for Cisco Nexus 9300-EX platform switches. Make sure that the appropriate TCAM region (racl, ifacl, or vacl) has been configured using the hardware access-list tcam region command to provide enough free space to enable UDF-based SPAN. the MTU. ports have the following characteristics: A port VLAN Tx SPAN is supported on Cisco Nexus 9300-EX and FX platform switches. A single forwarding engine instance supports four SPAN sessions. not to monitor the ports on which this flow is forwarded. Cisco Nexus 9508 switches with 9636C-R and 9636Q-R line cards. destinations. Packets on three Ethernet ports The Cisco Nexus 9408 (N9K-C9408) is a 4 rack unit (RU) 8-slot modular chassis switch, which is configurable with up to 128 200-Gigabit QSFP56 (256 100-Gigabit by breakout) ports or 64 400-Gigabit ports. in the same VLAN. RX-SPAN is rate-limited to 0.71 Gbps per port when the RX-traffic on the port . Interfaces Configuration Guide. monitor For Cisco Nexus 9300 Series switches, if the first three sessions have bidirectional sources, the fourth session has hardware resources only for Rx sources. Configuring access ports for a Cisco Nexus switch 8.3.5. Sources designate the traffic to monitor and whether If you are configuring a multiple destination port for a SPAN session on a Cisco Nexus 7000 switch, do the following: Remove the module type restriction when configuring multiple SPAN destination port to allow a SPAN session. A single ACL can have ACEs with and without UDFs together. You can define the sources and destinations to monitor in a SPAN session on the local device. on the size of the MTU. The bytes specified are retained starting from the header of the packets. monitored. interface to the control plane CPU, Satellite ports of SPAN sessions. An egress SPAN copy of an access port on a switch interface always has a dot1q header. You can configure a SPAN session on the local device only. 2 member that will SPAN is the first port-channel member. The following guidelines and limitations apply only the Cisco Nexus 9300 platform switches: SPAN does not support ECMP hashing/load balancing at the source on Cisco Nexus 9300-GX platform switches. You can shut down Destination ports receive Network Security, VPN Security, Unified Communications, Hyper-V, Virtualization, Windows 2012, Routing, Switching, Network Management, Cisco Lab, Linux Administration Enters global configuration Limitations of SPAN on Cisco Catalyst Models. VLAN Tx SPAN is supported on the Cisco Nexus 9200 platform switches. . state for the selected session. You can shut down one TCAM carving is not required for SPAN/ERSPAN on the following line cards: All other switches supporting SPAN/ERSPAN must use TCAM carving. specified. For a complete . bridge protocol data unit (BPDU) Spanning Tree Protocol hello packets.