MTU Settings on a VLAN Interface still not possible

Hi LuCar

Yes, this is possible on a physical interface. But when i create a link aggregation with all Subnets as VLAN Interfaces on this LAG i don't have the option. When i now need an MTU of 1460 on a VLAN Interface i have to contact the technical support. The edit a startupfile to do that. When you do this only in the console, the setting is lost after next reboot.

Because of this it's not usable for us to call every time to the support. We would do this by our self.

Best Regards,

Rene

Thats the missing point, you are using LAG and tagging a PPPOE on this VLAN? 

Or why do you use MTU1460 on a Interface? 

Thats the missing point, you are using LAG and tagging a PPPOE on this VLAN? 

Or why do you use MTU1460 on a Interface? 

Yes, we have a xDSL Modem on a Switch (VLAN 1000) and also the VLAN1000 on the LAG. But the VLAN Interface is not PPPoE it is static. and on this i have to change the MTU to 1460. It works fine with the correction in the startup file. 

Hi Lucar,

He said why they use 1460, it's required for the xDSL connection. MTU of 1460 is not uncommon for any PPP connections, especially in the UK.

LAG-ing a bunch of ports and tying everything through a highly resilient switch configuration is also not unusual.

Emile

Just wanted to make sure, we are not talking about simple VDSL.

I am not quite sure, if this is covered by EAP3, because there are some changes to VLAN etc. 

PMParth Could give some insight?