Forum Discussion
Vipirion platform Jumbo Frames support
Hello , I have defined the vlan mtu size to be : 8000 (jumbo ) , testing the traffic through the device it seems that the packet isnt passing .
Might someone have any ideas for what might be the cause ?
10x
- What_Lies_Bene1Cirrostratus
Jumbo frame support is currently patchy. Where VIPRION is concerned a 9216 frame size is supported but only on B2100 and B4300 blades and TMOS v10.2.4 onwards. I'll check now to see if things have improved since I last noted this information and update this answer if they have.
Things have indeed changed, see here for all the details: http://support.f5.com/kb/en-us/solutions/public/6000/300/sol6399.html
- Valentin_Z_Nimbostratus
Thank you for the quick response , We are currently running version 11.4 build 2419.0 HF3 which is pretty much one of the latest versions . The blade we have is the B2100 so that's supposed to be supported . And yet it doesnt seem to work .
- What_Lies_Bene1Cirrostratus
Jumbo configuration seems to be tricky with most vendor's equipment. I'd suggest you try using the maximum MTU in the first instance (9198). Also, if the packets pass between VLANs, ensure you set the MTU on all of them.
If this doesn't fix the issue, I'd suggest contacting F5 support for further advice.
- Valentin_Z_Nimbostratus
Hi , After contacting the support , turns out there is a bug (ID 413261) which relates to pinging the self-ips of the device with big packetsize fails. That's because of dos.maxicmpframesize DB variable, introduced in v11.4.0 which is limitting ping framesize by default of 1500. If you really need to ping self ips with jumbo frames you can modify this DB variable.
- What_Lies_Bene1CirrostratusExcellent, great to know. Cheers
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com