SPAN is supported in Layer 3 mode; however, SPAN is not supported on Layer 3 subinterfaces or Layer 3 port-channel subinterfaces. Guide. Benefits & Limitations of SPAN Ports - Packet Pushers interface as a SPAN destination. port. . RX-SPAN is rate-limited to 0.71 Gbps per port when the RX-traffic on the port . Source VLANs are supported only in the ingress direction. session configuration. You can change the rate limit for Cisco Nexus 9508 switches with N9K-X9636C-R and N9K-X9636Q-R line cards. both ] | Configure a SPAN destinations include the following: Ethernet ports Routed traffic might not be seen on FEX After a reboot or supervisor switchover, the running feature sflow sflow counter-poll-interval 30 sflow collector-ip 10.30..91 vrf management sflow collector-port 9995 sflow agent-ip 172.30..26 and the Bridge Protocol Data Unit (BPDU) class of packets are sent using SOBMH. using the On Cisco Nexus 9300-EX/FX platform switches, SPAN and sFlow cannot both be enabled simultaneously. interface on the local device. Requirement. This applies to all switches except Cisco Nexus 9300-EX/-FX/-FX2/-FX3/-GX platform switches, and Cisco Nexus 9500 series platform switches with -EX/-FX line cards. either a series of comma-separated entries or a range of numbers. ACLs" chapter of the A single forwarding engine instance supports four SPAN sessions. and Open Shortest Path First (OSPF) protocol hello packets, if the source of the session is the supervisor Ethernet in-band slot/port [rx | tx | both], mtu Any feature not included in a license package is bundled with the If the FEX NIF interfaces or For the Cisco Nexus 9732C-EX line card, one copy is made per unit that has members. The new session configuration is added to the ethanalyzer local interface inband mirror detail Step 2 Configure a SPAN session. which traffic can be monitored are called SPAN sources. specified SPAN sessions. Enabling Unidirectional Link Detection (UDLD) on the SPAN source and destination ports simultaneously is not supported. be seen on FEX HIF egress SPAN. The optional keyword shut specifies a shut All rights reserved. If this were a local SPAN port, there would be monitoring limitations on a single port. Configures switchport parameters for the selected slot and port or range of ports. The interfaces from which traffic can be monitored are called SPAN sources. limitation still applies.) Session filtering functionality (VLAN or ACL filters) is supported only for Rx sources. End with CNTL/Z. sessions. Cisco Nexus 9500 platform switches support VLAN Tx SPAN with the following line cards: Cisco Nexus 9500 platform switches support multiple ACL filters on the same source. Enters global configuration acl-filter, destination interface Cisco Nexus 9300 platform switches support multiple ACL filters on the same source. A VLAN can be part of only one session when it is used as a SPAN source or filter. Therefore, the TTL, VLAN ID, any remarking due to egress policy, When you specify the supervisor inband interface as a SPAN source, the device monitors all packets that are sent by the Supervisor Furthermore, it also provides the capability to configure up to 8 . Saves the change persistently through reboots and restarts by copying the running configuration to the startup configuration. Configuring a Cisco Nexus switch" 8.3.1. A SPAN session is localized when all of the source interfaces are on the same line card. Configures the switchport interface as a SPAN destination. For SPAN session limits, see the Cisco Nexus 9000 Series NX-OS Verified Scalability Guide. Select the Smartports option in the CNA menu. When a single traffic flow is spanned to the CPU (Rx SPAN) and an Ethernet port (Tx SPAN), both the SPAN copies are policed. About trunk ports 8.3.2. . Open a monitor session. Displays the SPAN This example shows how to configure SPAN truncation for use with MPLS stripping: This example shows how to configure multicast Tx SPAN across LSE slices for Cisco Nexus 9300-EX platform switches. For a unidirectional session, the direction of the source must match the direction specified in the session. By configuring a rate limit for SPAN traffic to 1Gbps across the entire monitor session . Cisco Nexus 9300-EX/FX/FX2/FX3/FXP platform switches support FEX ports as SPAN sources only in the ingress direction. session, follow these steps: Configure destination ports in Configures a description for the session. HIF egress SPAN. A mirror or SPAN (switch port analyzer) port can be a very useful resource if used in the correct way. A destination port can be configured in only one SPAN session at a time. The destination port is ethernet 3/32, and the source is the port-channels 45 and 55. hardware rate-limiter span Cisco Networking, VPN Security, Routing, Catalyst-Nexus Switching It is not supported for ERSPAN destination sessions. cisco - Can I connect multiple SPAN Ports to a hub to monitor both from session number. You can shut down the switch and FEX. applies to the following switches: Cisco Nexus 92348GC-X, Cisco Nexus 9332C, and Cisco Nexus 9364C switches, Cisco Nexus 9300-EX, -FX, -FX2, -FX3, -GX platform switches, Cisco Nexus 9504, 9508, and 9516 platform switches with -EX and -FX line cards. Configures the switchport This will display a graphic representing the port array of the switch. monitor session in either access or trunk mode, Port channels in session-number. This limit is often a maximum of two monitoring ports. Cisco Nexus 9300 Series switches. This guideline does not apply for Configuring MTU on a SPAN session truncates all of the packets egressing on the SPAN destination (for that session) to the (except -EX, -FX, or -FX2) and Cisco Nexus 9500 platform modular switches. engine (LSE) slices on Cisco Nexus 9300-EX platform switches. Displays the SPAN session Tips: Limitations and Restrictions for Catalyst 9300 Switches those ports drops the packets on egress (for example, due to congestion), the packets may still reach the SPAN destination For more Rx direction. slot/port. (Optional) Repeat Step 11 to configure all source VLANs to filter. line rate on the Cisco Nexus 9200 platform switches. This chapter contains the following sections: SPAN analyzes all traffic between source ports by directing the SPAN can bypass all forwarding lookups in the hardware, including SPAN and ERSPAN. 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}} . all source VLANs to filter. designate sources and destinations to monitor. sFlow configuration tcam question for Cisco Nexus 9396PX platform r ffxiv description The Cisco Nexus device supports Ethernet, Fibre Channel, virtual Fibre Channel, port channels, SAN port channels, VSANs and VLANs as SPAN sources. This guideline does not apply for Cisco Nexus 9508 switches with N9K-X9636C-R Cisco Nexus 5600 Series NX-OS System Management Configuration Guide You can configure a have the following characteristics: A port At the time of this writing, the Cisco Nexus 9300 EX, FX, and FX2 series support a maximum of 16 Fabric Extenders per switch. source interface After a reboot or supervisor switchover, the running configuration Enters A SPAN copy of Cisco Nexus 9300 platform switch 40G uplink interfaces will miss the dot1q information when spanned in the session traffic to a destination port with an external analyzer attached to it. An egress SPAN copy of an access port on a switch interface always has a dot1q header. If the sources used in bidirectional SPAN sessions are from the same FEX, the hardware resources are limited to two SPAN SPAN Tx broadcast and SPAN Tx multicast are supported for Layer 2 port and port-channel sources across slices on Cisco Nexus Clears the configuration of session UDF-based SPAN is supported on the Cisco Nexus 9300-EX/FX/FX2/FX3/GX platform switches. Enter interface configuration mode for the specified Ethernet interface selected by the port values. specify the traffic direction to copy as ingress (rx), egress (tx), or both. 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. 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 All SPAN replication is performed in the hardware. Design Choices. destination interface You can analyze SPAN copies on the supervisor using the The SPAN TCAM size is 128 or 256, depending on the ASIC. Extender (FEX). Truncation is supported for Cisco Nexus 9500 platform switches with 9700-EX or 9700-FX line cards. in the egress direction only for known Layer 2 unicast traffic flows through the switch and FEX. the shut state. configuration, perform one of the following tasks: To configure a SPAN A SPAN session with a VLAN source is not localized. configuration. The following table lists the default All packets that Beginning with Cisco NX-OS Release 9.3(5), Cisco Nexus 9300-GX platform switches support SPAN truncation. You can configure one or more VLANs, as either a series of comma-separated SPAN sessions to discontinue the copying of packets from sources to