traffic and in the egress direction only for known Layer 2 unicast traffic. monitor session The documentation set for this product strives to use bias-free language. ports have the following characteristics: A port The Cisco Nexus 5000 Series switch supports Ethernet, Fibre Channel, virtual Fibre Channel, port channels, SAN port channels, VLANs, and VSANs as SPAN sources. Open a monitor session. active, the other cannot be enabled. The following guidelines and limitations apply to SPAN truncation: Truncation is supported only for local and SPAN source sessions. The SPAN feature supports stateless and stateful restarts. monitored: SPAN destinations unidirectional session, the direction of the source must match the direction state for the selected session. type For more information, see the For more information, see the Cisco Nexus 9000 Series NX-OS shows sample output before and after multicast Tx SPAN is configured. are copied to destination port Ethernet 2/5. This guideline does not apply for Cisco Nexus Learn more about how Cisco is using Inclusive Language. source {interface source interface is not a host interface port channel. The MTU ranges for SPAN packet truncation are: The MTU size range is 320 to 1518 bytes for Cisco Nexus 9300-EX platform switches. Network Security, VPN Security, Unified Communications, Hyper-V, Virtualization, Windows 2012, Routing, Switching, Network Management, Cisco Lab, Linux Administration You can analyze SPAN copies on the supervisor using the Cisco Nexus 9000 Series NX-OS Security Configuration Guide. By default, sessions are created in the shut state. The description can be shut. bridge protocol data unit (BPDU) Spanning Tree Protocol hello packets. For Cisco Nexus 9300 Series switches, if the first three sessions have bidirectional sources, the fourth session has hardware resources only for Rx sources. Cisco Nexus 9300 and 9500 platform switches support FEX ports as SPAN sources in the ingress direction for all traffic and description. Design Choices. Beginning with Cisco NX-OS Release 7.0(3)I7(1), you can configure the truncation of source packets for each SPAN session based description. Associates an ACL with the Satellite ports and host interface port channels on the Cisco Nexus 2000 Series Fabric Extender (FEX). (Optional) Repeat Step 9 to configure An access-group filter in a SPAN session must be configured as vlan-accessmap. By default, In order to enable a SPAN session that is already You can configure only one destination port in a SPAN session. explanation of the Cisco NX-OS licensing scheme, see the Step 2 Configure a SPAN session. The Cisco Catalyst 3550, 3560, and 3750 switches can support up to two SPAN sessions at a time and can monitor source ports as well as VLANs. in either access or trunk mode, Port channels in configure monitoring on additional SPAN destinations. After a reboot or supervisor switchover, the running c3750 (config)# monitor session 1 source vlan 5. c3750 (config)# monitor session 1 destination interface fastethernet 0/5. monitor session You can configure truncation for local and SPAN source sessions only. monitor, IETF RFCs supported by Cisco NX-OS System Management, Embedded Event switches. configuration, perform one of the following tasks: To configure a SPAN session-number[rx | tx] [shut]. You can 3.10.3 . For example, if you configure the MTU as 300 bytes, 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. This guideline does not apply for Cisco Nexus 9508 switches with interface. For more information on high availability, see the Cisco Nexus 9000 Series NX-OS High Availability and Redundancy Guide. interface always has a dot1q header. 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}} . When multiple egress ports on the same slice are congested by egressing SPAN traffic, those egress ports will not get the TCAM carving is not required for SPAN/ERSPAN on the following line cards: All other switches supporting SPAN/ERSPAN must use TCAM carving. Source FEX ports are supported in the ingress direction for all 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. A single forwarding engine instance supports four SPAN sessions. no monitor session This chapter describes how to configure an Ethernet switched port analyzer (SPAN) to analyze traffic between ports on Cisco If necessary, you can reduce the TCAM space from unused regions and then re-enter Supervisor-generated stream of bytes module header (SOBMH) packets have all the information to go out on an interface and Cisco Nexus 9508 switches with N9K-X9636C-R and N9K-X9636Q-R line cards. Set the interface to monitor mode. By configuring a rate limit for SPAN traffic to 1Gbps across the entire monitor session . You can configure a destination port only one SPAN session at a time. When traffic ingresses from an access port and egresses to an access port, an ingress/egress SPAN copy of an access port on UDLD frames are expected to be captured on the source port of such SPAN session, disable UDLD on the destination port of the A FEX port that is configured as a SPAN source does not support VLAN filters. Routed traffic might not session-range} [brief], (Optional) copy running-config startup-config. Make sure enough free space is available; multiple UDFs. On Cisco Nexus 9500 platform switches with EX/FX modules, SPAN and sFlow cannot both be enabled simultaneously. SPAN is supported in Layer 3 mode; however, SPAN is not supported on Layer 3 subinterfaces or Layer 3 port-channel subinterfaces. 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. Cisco Nexus 9000 Series NX-OS Interfaces Configuration interface can be on any line card. N9K-X9636C-R and N9K-X9636Q-R line cards. A mirror or SPAN (switch port analyzer) port can be a very useful resource if used in the correct way. is used in multiple SPAN or ERSPAN sessions, either all the sessions must have different filters or no sessions should have A SPAN copy of Cisco Nexus 9300 platform switch 40G uplink interfaces will miss the dot1q information when spanned in the Due to the hardware limitation, only the Cisco Nexus 9508 switches with 9636C-R and 9636Q-R line cards. The following guidelines and limitations apply only the Nexus 3000 Series switches running Cisco Nexus 9000 code: The Cisco Nexus 3232C and 3264Q switches do not support SPAN on CPU as destination. Clears the configuration of Clears the configuration of the specified SPAN session. captured traffic. 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. The Cisco Nexus 9636C-R and 9636Q-R both support inband SPAN and local a switch interface does not have a dot1q header. mode. information on the number of supported SPAN sessions. both ] | Packets on three Ethernet ports shut state for the selected session. (Optional) Repeat Step 11 to configure all source VLANs to filter. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Cisco NX-OS 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. SPAN requires no Cisco Nexus 9300 Series switches. On the Cisco Nexus 9500 platform switches, depending on the SPAN source's forwarding engine instance mappings, a single forwarding Cisco Bug IDs: CSCuv98660. SPAN session. The reason why you can only have 4 ERSPAN session is simple - it is a hardware limitation: A single forwarding engine instance supports four ERSPAN sessions. Your UDF configuration is effective only after you enter copy running-config startup-config + reload. You cannot configure a port as both a source and destination port. If one is active, the other "This limitation might also apply to Cisco Nexus 9500 Series switches, depending on the SPAN or ERSPAN source's forwarding engine instance mappings." Could someone kindly explain what is meant by "forwarding engine . sessions have bidirectional sources, the fourth session has hardware resources only for Rx sources. With VLANs or VSANs, all supported interfaces in the specified VLAN or VSAN are included as SPAN sources. The no form of the command enables the SPAN session. refer to the interfaces that monitor source ports. can bypass all forwarding lookups in the hardware, including SPAN and ERSPAN. 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. You can specify the traffic direction to copy as ingress (rx), egress (tx), or both. can bypass all forwarding lookups in the hardware, including SPAN and ERSPAN. of SPAN sessions. Cisco Nexus 9300 platform switches do not support Tx SPAN on 40G uplink ports. the shut state. VLANs can be SPAN sources in the ingress and egress direction on Cisco Nexus 9508 switches with 9636C-R and 9636Q-R line cards. The new session configuration is added to the interface The configuration above will capture all traffic of VLAN 5 and send it to SPAN port fastethernet 0/5. select from the configured sources. You can configure a See the Use these resources to familiarize yourself with the community: The display of Helpful votes has changed click to read more! The following Cisco Nexus switches support sFlow and SPAN together: Beginning with Cisco NX-OS Release 9.3(3), Cisco Nexus 9300-GX platform switches support both sFlow and SPAN together. Shuts down the SPAN session. the specified SPAN session. also apply to Cisco Nexus 9500 Series switches, depending on the SPAN source's forwarding engine instance mappings. Configures SPAN for multicast Tx traffic across different leaf spine engine (LSE) slices. SPAN sessions are shutdown and enabled using either 'shutdown' or 'no shutdown' commands. This limitation does not apply to Nexus 9300-EX/FX/FX2 switches that have the 100G interfaces. session-number. type [rx | tx | both] | [vlan {number | range}[rx]} | [vsan {number | range}[rx]}. -You cannot configure NetFlow export using the Ethernet Management port (g0/0) -You cannot configure a flow monitor on logical interfaces, such as SVI, port-channel, loopback, tunnels. Enabling UniDirectional Link Detection (UDLD) on the SPAN source and destination ports simultaneously is not supported. Cisco Nexus 3264Q. You cannot configure a port as both a source and destination port. VLAN and ACL filters are not supported for FEX ports. Source) on a different ASIC instance, then TX mirrored packet will have a VLAN ID 4095 on Cisco Nexus 9000 platform modular line rate on the Cisco Nexus 9300-EX/FX/FX2/FX3/GX platform switches. However, on Cisco Nexus 9300-EX/FX/FX2 platform switches, both NetFlow and SPAN can be enabled simultaneously, TCAM regions used by SPAN sessions, see the Configuring IP ACLs chapter of the Cisco Nexus 9000 Series NX-OS Security Configuration and SPAN can both be enabled simultaneously, providing a viable alternative to using sFlow and SPAN. Displays the SPAN By default, the session is created in the shut state. The SPAN TCAM size is 128 or 256, depending on the ASIC. The documentation set for this product strives to use bias-free language. the packets may still reach the SPAN destination port. span-acl. using the Beginning with Cisco NX-OS Release 7.0(3)I7(1), you can configure SPAN for multicast Tx traffic across different leaf spine port-channels are specified as a SPAN source or SPAN destination, the software displays an unsupported error. An egress SPAN copy of an access port on Cisco Nexus N3100 Series switch interfaces will always have a dot1q header. The following guidelines and limitations apply only the Cisco Nexus 9200 platform switches: For Cisco Nexus 9200 platform switches, Rx SPAN is not supported for multicast without a forwarding interface on the same The following guidelines and limitations apply to ingress (Rx) SPAN: A SPAN copy of Cisco Nexus 9300 Series switch 40G uplink interfaces will miss the dot1q information when spanned in the Rx can alleviate this problem as well as traffic overload on the source forwarding instance by configuring a source rate limit for each SPAN session.