There are a couple of options, depending on how much traffic you will receive:
- If you're going to receive a lot of traffic, should use gulp, which runs on linux; gulp requires the linux pf_ring kernel module.
- If the bandwidth requirements are reasonable, you could simply use your laptop with wireshark's ERSPAN decoder; wireshark can see the protocols inside ERSPAN v2 and v3 packets. Use
ip proto 0x2f
as your capture filter, if you want to only capture ERSPAN traffic. I use the wireshark to capture ERSPAN from Catalyst6500 user ports when I need to remotely sniff a port without walking up to the switch with a laptop. This works well for user ports and even some server ports (as long as they aren't sending tons of traffic)
Example Cat6500 ERSPAN config:
!
monitor session 2 type erspan-source
source interface GigabitEthernet7/22
destination
erspan-id 1
! This is the ip address of gulp, or the wireshark laptop
! If using wireshark, capture with "ip proto 0x2f"
ip address 10.1.1.5
! This is the IP address of the switch sourcing ERSPAN packets
origin ip address 10.21.4.12
no shutdown
Example Nexus9000 ERSPAN config:
monitor session 1 type erspan-source
erspan-id 1
! Specify the vrf that ERSPAN will use to route to the destination IP
! NOTE: I have not found a way to use "vrf management" on the 9000 series
vrf default
! This is the ip address of gulp, or the wireshark laptop
! If using wireshark, capture with "ip proto 0x2f"
destination ip 10.5.69.226
source interface port-channel1001 both
no shut
! This is the IP address of the switch sourcing ERSPAN packets
monitor erspan origin ip-address 172.16.12.80 global