11-11-2020 08:13 AM
Using RSPAN feature on EXOS HW there are situations where the recieved data on the remote RSPAN device is not complete. This occurs when the RSPAN process (RSPAN sender) on EXOS HW should transport a 1500 byte packet via GRE-Tunneling to the RSPAN receiver and the encapsulated packet (1500 byte + GRE header) is too big for the available MTU between RSPAN sender and receiver.
In this case you will see at the RSPAN receiver only packets matching the connection MTU. There is no note/description or error mesage available about this silent drop because of HW limitations. We figured that out by comparing local mirroring data with remote mirroring (RSPAN) data.
Another solution is to configure Jumbo frames in the complete communication path betwee RSPAN senden and receiver. This is sometimes possible in local connections but not in big LANs and via WAN.
For that we need
Br
Volker
04-21-2021 04:07 PM
We now have another customer who needs it, thus it qualifies for FR.
Feature Request 02334617 Ability to set an IP MTU and MSS value on GRE tunnels
12-04-2020 06:28 PM
Can’t agree more.
What if we use Fabric as a transport ? Will it save your world ? 🙂
(truncated frames need CPU processing if you do it on switch, I am afraid)
12-04-2020 05:12 PM
Did you install IAH? I`m running FGT and other stuff on it. This is not usable in the field and much too expensive for a part time usage. And what´s about VSPs without IAH?
RSPAN to a remote PC with wireshark is absolutely needed. With truncation and/or jumbo frames - does not matter at all. Best with fragmentation in next HW versions.
Managing worldwide networks you will need RSPAN anytime anywhere…
Volker
12-04-2020 04:55 PM
Sounds like a kludge for RSPAN.. And what if we rather use IAH VM to do fragmentation/defragmentation ?
Or simply use remote pcap on IAH VM ?