Do Not Fragment bit in Fabric Engine 'Ping'

[tcsr121]

Hi
I want to test MTU between two Fabric Extend endpoints both running 9.0.4 that traverse a third party network where the third party does not always set the path MTU to allow FE (it's usually 1900 end to end).
I'm pinging from the tunnel interface on our core switch to a remote logical interface address that I know works as follows:

     ping 10.a.b.c datasize 1900 vrf fe-int source 10.x.y.x 

This works - but then so does 

     ping 10.a.b.c datasize 9000 vrf fe-int source 10.x.y.x 

as I know the intervening network has a limit of 1900 I'm guessing that packets are being fragmented which makes the test useless. There seems to be no 'do not fragment' option for ping (there is with Cisco). Is there an option I'm missing or a better test on Fabric Engine?? As MTU is limited to 1500 elsewhere I can only check directly between the two Extreme switches.

[SamPirok · Accepted solution]

Hey guys, just wanted to mention that opening a feature request with your local sales engineer would help raise this request to management's attention faster. If you're unsure who your local sales rep is, please let me know generally where you're located and I'll find a sales engineer to assist you. 

[tcsr121]

Thanks I've raised it with our Premier Support Delivery Manager
I have to say that "Accepted Solution" is stretching things a bit - currently there is no solution.

[Jave]

Hy @SamPirok 

I've done this several times for over two years now, but it is the same old story.

Regards.

[CordScott]

This really should be there considering the jumbo frame requirements in Extreme Fabric.