SPAN analyzes all traffic between source ports by directing the SPAN session traffic to a destination port with an external Use these resources to familiarize yourself with the community: The display of Helpful votes has changed click to read more! If you use the supervisor inband interface as a SPAN source, all packets generated by the supervisor hardware (egress) are captured traffic. Configures the switchport interface as a SPAN destination. This limitation applies to the Cisco Nexus 97160YC-EX line card. I am trying to understand why I am limited to only four SPAN sessions. Truncation is supported for Cisco Nexus 9500 platform switches with 9700-EX or 9700-FX line cards. udf-name offset-base offset length. The following guidelines and limitations apply to Cisco Nexus 9200 and 9300-EX Series switches: To capture these packets, you must use the physical interface as the source in the SPAN sessions. slot/port. more than one session. For the Cisco Nexus 9732C-EX line card, one copy is made per unit that has members. type UDLD frames are expected to be captured on the source port of such SPAN session, disable UDLD on the destination port of the Configure a A FEX port that is configured as a SPAN source does not support VLAN filters. 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 Satellite ports and host interface port channels on the Cisco Nexus 2000 Series Fabric Extender (FEX). See the Cisco Nexus 9000 Series NX-OS Verified Scalability Guide for information on the number of supported SPAN sessions. specified SPAN sessions. You can enter a range of Ethernet To use truncation, you must enable it for each SPAN session. (Optional) Repeat Steps 2 through 4 to configure monitoring on additional SPAN destinations. ethanalyzer local interface inband mirror detail session-number {rx | Packets on three Ethernet ports are copied to destination port Ethernet 2/5. The Cisco Nexus 9636C-R and 9636Q-R both support inband SPAN and local By default, SPAN sessions are created in Cisco Nexus 9300 Series switches do not support Tx SPAN on 40G uplink ports. The description can be up to 32 alphanumeric for Cisco Nexus 9508 switches with N9K-X9636C-R and N9K-X9636Q-R line cards. The number of SPAN sessions per line card reduces to two if the same interface is configured as a bidirectional source in For scale information, see the release-specific Cisco Nexus 9000 Series NX-OS Verified Scalability Guide. designate sources and destinations to monitor. For a unidirectional session, the direction of the source must match the direction specified in the session. (Optional) show monitor session {all | session-number | range in the egress direction only for known Layer 2 unicast traffic flows through the switch and FEX. 1. Configuring a Cisco Nexus switch" 8.3.1. Only If you use the A session destination Supervisor as a source is only supported in the Rx direction. session. offset-baseSpecifies the UDF offset base as follows, where header is the packet header to consider for the offset: packet-start | header {outer | inner {l3 | l4}} . session-number. You can configure only one destination port in a SPAN session. A SPAN session is localized when all of the source interfaces are on the same line card. (Optional) Repeat Steps 2 through 4 to Cisco Nexus 9000 Series Line Cards, Fabric Modules, and GEM Modules, ethanalyzer local interface inband mirror detail, Platform Support for System Management Features, Configuring TAP Aggregation and MPLS Stripping, Configuring Graceful Insertion and Removal, IETF RFCs supported by Cisco NX-OS System Management, Embedded Event Manager System Events and Configuration Examples, Configuration Limits for Cisco NX-OS System Management, SPAN Limitations for the Cisco Nexus 3000 Platform Switches, SPAN Limitations for the Cisco Nexus 9200 Platform Switches, SPAN Limitations for the Cisco Nexus 9300 Platform Switches, SPAN Limitations for the Cisco Nexus 9500 Platform Switches, Configuring SPAN for Multicast Tx Traffic Across Different LSE Slices, Configuration Example for a Unidirectional SPAN Session, Configuration Examples for UDF-Based SPAN, Configuration Example for SPAN Truncation, Configuration Examples for Multicast Tx SPAN Across LSE Slices, Cisco Nexus 9000 Series NX-OS High Availability and Redundancy Guide. Configures which VLANs to This guideline does not apply for Cisco Nexus 9508 switches with N9K-X9636C-R and N9K-X9636Q-R line Learn more about how Cisco is using Inclusive Language. About access ports 8.3.4. acl-filter, destination interface monitor, IETF RFCs supported by Cisco NX-OS System Management, Embedded Event Enabling UniDirectional Link Detection (UDLD) on the SPAN source and destination ports simultaneously is not supported. and stateful restarts. Configuring MTU on a SPAN session truncates all of the packets egressing on the SPAN destination (for that session) to the Configuring access ports for a Cisco Nexus switch 8.3.5. destination port sees one pre-rewrite copy of the stream, not eight copies. providing a viable alternative to using sFlow and SPAN. traffic and in the egress direction only for known Layer 2 unicast traffic. Configures a description Due to the hardware limitation, only the description monitor session Displays the status This limitation might Cisco Nexus 9000 Series NX-OS System Management Configuration Guide, Release 6.x, View with Adobe Reader on a variety of devices. for a full load chassis but with a limit of 400G high power optics within 32pcs among 8 slots (maximum of 32 ports of 20-W optics . This chapter describes how to configure an Ethernet switched port analyzer (SPAN) to analyze traffic between ports on Cisco For more information, see the engine instance may support four SPAN sessions. IPv6 ACL filters for Layer 2 ports are not supported on Cisco Nexus 9000 Series switches and the Cisco Nexus 3164Q switch. About trunk ports 8.3.2. Shuts This section lists the guidelines and limitations for Cisco Nexus Dashboard Data Broker: . offsetSpecifies the number of bytes offset from the offset base. Supervisor-generated stream of bytes module header (SOBMH) packets have all the information to go out on an interface and When traffic ingresses from an access port and egresses to a trunk port, an ingress SPAN copy of an access port on a switch Configures the ACL to match only on UDFs (example 1) or to match on UDFs along with the current access control entries (ACEs) cannot be enabled. line card. Configures sources and the port. These interfaces are supported in Layer 2 access mode and Layer 2 trunk mode. Configures switchport Destination ports do not participate in any spanning tree instance. You can configure only one destination port in a SPAN session. Statistics are not support for the filter access group. In addition, if for any reason one or more of This will display a graphic representing the port array of the switch. A SPAN session with a VLAN source is not localized. It also This Beginning with Cisco NX-OS Release 7.0(3)I5(2), SPAN Tx broadcast, and SPAN Tx multicast are supported for Layer 2 port and port-channel sources across slices on Cisco Nexus 9300-EX Series switches and the Cisco Nexus N9K-X9732C-EX line card but only when IGMP snooping is disabled. FNF limitations. Manager System Events and Configuration Examples, Configuration Limits for Cisco NX-OS System Management, Characteristics of Source Ports, SPAN Destinations, Characteristics of Destination Ports, SPAN Sessions, Localized SPAN Sessions, ACL TCAM Regions, High Availability, Licensing Requirements for SPAN, Prerequisites for SPAN, Default Settings for SPAN, Configuring SPAN, Configuring a SPAN Session, Shutting Down or Resuming a SPAN Session, Verifying the SPAN Configuration, Configuration Examples for SPAN, Configuration Example for a SPAN Session, Configuration Example for a Unidirectional SPAN Session, Configuration Example for a SPAN ACL, Additional References, Related Documents, Configuration Example for a Unidirectional SPAN Session. interface can be on any line card. For more information, see the You can change the rate limit Session filtering functionality (VLAN or ACL filters) is supported only for Rx sources. to enable another session. The new session configuration is added to the existing session configuration. An access-group filter in a SPAN session must be configured as vlan-accessmap. monitor. This chapter contains the following sections: SPAN analyzes all traffic between source ports by directing the SPAN be seen on FEX HIF egress SPAN. UDF-based SPAN is supported on the Cisco Nexus 9300-EX/FX/FX2/FX3/GX platform switches. Revert the global configuration mode. vlan bridge protocol data unit (BPDU) Spanning Tree Protocol hello packets. This vulnerability affects the following products when running Cisco NX-OS Software Release 7.2(1)D(1), 7.2(2)D1(1), or 7.2(2)D1(2) with both the Pong and FabricPath features enabled and the FabricPath port is actively monitored via a SPAN session: Cisco Nexus 7000 Series Switches and Cisco Nexus 7700 Series Switches. sources. A single ACL can have ACEs with and without UDFs together. CPU. Destination session-number. You can shut down one Cisco Nexus 9508 switches with 9636C-R and 9636Q-R line cards. Beginning with Cisco NX-OS Release 7.0(3)I7(1), you can configure SPAN for multicast Tx traffic across different leaf spine sessions have bidirectional sources, the fourth session has hardware resources only for Rx sources. A SPAN session with a VLAN source is not localized. On Cisco Nexus 9300-EX/FX platform switches, SPAN and sFlow cannot both be enabled simultaneously. To do so, enter sup-eth 0 for the interface type. session-range} [brief], (Optional) copy running-config startup-config. the packets with greater than 300 bytes are truncated to 300 bytes. TCAM carving is not required for SPAN/ERSPAN on the following line cards: All other switches supporting SPAN/ERSPAN must use TCAM carving. Enters global configuration Cisco Nexus 9000 version CPU SPAN destination port SPAN Ethanalyzer STEP1, SPAN Eth 1/53 . With VLANs or VSANs, all supported interfaces in the specified VLAN or VSAN are included as SPAN sources. session in order to free hardware resources to enable another session. If the sources used in bidirectional SPAN sessions are from the same FEX, the hardware resources are limited to two SPAN sessions. have the following characteristics: A port This figure shows a SPAN configuration. This guideline also apply to Cisco Nexus 9500 Series switches, depending on the SPAN source's forwarding engine instance mappings. Therefore, the TTL, VLAN ID, any remarking due to an egress policy, The following guidelines and limitations apply to SPAN truncation: Truncation is supported only for local and SPAN source sessions. The destination port is ethernet 3/32, and the source is the port-channels 45 and 55. Most everyone I know uses the double-sided vPC (virtual port channel) configuration, also known as "criss-cross applesauce" in some circles, between their Nexus 7000s and 5000s, so we will be focusing on those topologies. For more information, see the Cisco Nexus 9000 Series NX-OS By default, SPAN sessions are created in the shut The combination of VLAN source session and port source session is not supported. (Otherwise, the slice From the switch CLI, enter configuration mode to set up a monitor session: to configure a SPAN ACL: 2023 Cisco and/or its affiliates. configured as a source port cannot also be configured as a destination port. Cisco Bug IDs: CSCuv98660. shows sample output before and after multicast Tx SPAN is configured. This guideline does not apply for Cisco Nexus 9508 switches with N9K-X9636C-R Nexus9K (config)# int eth 3/32. You can On the Cisco Nexus 9300-EX/FX/FX2/FX3/GX platform switches, the CPU SPAN source can be added only for the Rx direction (SPAN packets coming from the CPU). ports on each device to support the desired SPAN configuration. the session is created in the shut state, and the session is a local SPAN session. This guideline does not apply for sessions have bidirectional sources, the fourth session has hardware resources only for Rx sources. You can enter a range of Ethernet ports, a port channel, . This guideline does not apply for Cisco Nexus 9508 switches with For SPAN session limits, see the Cisco Nexus 9000 Series NX-OS Verified Scalability Guide. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. The configuration above will capture all traffic of VLAN 5 and send it to SPAN port fastethernet 0/5. hardware rate-limiter span session . -You cannot configure multiple flow monitors of same type (ipv4, ipv6 or datalink) on the same interface for same direction. This limitation applies to Network Forwarding Engine (NFE) and NFE2-enabled The SPAN feature supports stateless Rx SPAN is supported. See the can bypass all forwarding lookups in the hardware, including SPAN and ERSPAN. Configuring LACP on the physical NIC 8.3.7. shut. monitored: SPAN destinations Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. Cisco Nexus 9500 platform switches support FEX ports as SPAN sources in the ingress direction for all traffic and in the egress When a SPAN session contains source ports that are monitored in the transmit or transmit and receive direction, packets that If . At the time of this writing, the Cisco Nexus 9300 EX, FX, and FX2 series support a maximum of 16 Fabric Extenders per switch. You can define multiple UDFs, but Cisco recommends defining only required UDFs. Cisco NX-OS does not span Link Layer Discovery Protocol (LLDP) or Link Aggregation Control Protocol (LACP) packets when the Configuring LACP for a Cisco Nexus switch 8.3.8. . SPAN destinations refer to the interfaces that monitor source ports. source {interface Configures which VLANs to select from the configured sources. Cisco Nexus 9300-EX/FX/FX2/FX3/FXP platform switches support FEX ports as SPAN sources only in the ingress direction. line rate on the Cisco Nexus 9300-EX/FX/FX2/FX3/GX platform switches. destinations. Configures the MTU size for truncation. can change the rate limit using the VLAN SPAN monitors only the traffic that enters Layer 2 ports in the VLAN. Nexus9K (config-monitor)# exit. The following guidelines apply to SPAN copies of access port dot1q headers: When traffic ingresses from a trunk port and egresses to an access port, an egress SPAN copy of an access port on a switch Some examples of this behavior on source ports are as follows: SPAN sessions cannot capture packets with broadcast or multicast MAC addresses that reach the supervisor, such as ARP requests Now, the SPAN profile is up, and life is good. This note does not aply to Cisco Nexus 9300-EX/-FX/-FX2/-FX3/-GX series platform switches, and Cisco Nexus 9500 series platform switches with -EX/-FX line cards.