Issue

This article applies to the following issues:

• A SPAN destination is not available.
• The interface type or types prevent using a laptop as a SPAN destination.

Note: This data has to be processed by the control plane, which impacts the CPU of the destination switch.

Environment

• Cumulus Linux, all versions

Resolution

Normal ERSPAN setup rules apply; see the Network Troubleshooting chapter for details.

1. Create rules for SPAN source; for example:
   

   cumulus@switch:~$ cat /etc/cumulus/acl/policy.d/span.rules
   [iptables]
   -A FORWARD --in-interface swp50 -j ERSPAN --src-ip 192.168.0.1 --dst-ip 192.168.0.2
   -A FORWARD --out-interface swp50 -j ERSPAN --src-ip 192.168.0.1 --dst-ip 192.168.0.2

2. Install the rules:
   

   cumulus@switch:~$ sudo cl-acltool -i

3. Verify the SPAN rules were installed:
   

   cumulus@switch:~$ cl-acltool -L all | grep SPAN
   41229 4368K ERSPAN all -- swp50 any anywhere anywhere ERSPAN src-ip:192.168.0.1 dst-ip:192.168.0.2
   17540 1126K ERSPAN all -- any swp50 anywhere anywhere ERSPAN src-ip:192.168.0.1 dst-ip:192.168.0.2

Note: The destination switch does not expect the ERSPAN packets, so it generates ICMP destination unreachable packets as a result. These packets are included in any capture you take.

To remove these packets, add an ACL like the following to the destination switch:

cumulus@switch:~$ cat /etc/cumulus/acl/policy.d/span.rules
[iptables]
-A OUTPUT --out-interface swp3 -p icmp --icmp-type destination-unreachable -j DROP