VLAN1 and IP on Bonded Interfaces

[Vladimir]

When creating bonded interfaces and VLAN subinterfaces, the first VLAN ID we can define is 2.

Does it mean that the bond itself should be assigned the IP in the network residing in VLAN 1 ?

[Maarten_Sjouw]

Always keep in mind that VLAN 1 has a special function in a switch.

Only when VLAN 1 has been assigned to the port as the native VLAN you will be able to assign an IP in that VLAN on the interface itself.

Do keep in mind it is NOT good practice to use the native VLAN in a trunk port, nor to assign an IP to the port that has subinterfaces (VLAN's assigned to it)

[Vladimir]

Thank you Maarten Sjouw‌, it figures that this is not a best practice and that's why I did not run into it before.

This time around though, I am working with the client where this may very well be the case on the switch side and thus, I'll have to deal with this situation.

Anything in particular you can share that makes the assignment of the IP to the Bond interface with subinterfaces cause negative effects?

[Maarten_Sjouw]

Vladimir Yakovlev, it is not a point of not working, it's just a thing that you should not do. Recently I had to do the same, luckily  I was able to get the VLAN moved from VLAN 1 to VLAN 10 by using a switch to switch VLAN translation. By setting the 1 switch trunk port to native VLAN 1 and the other switch trunk port to native VLAN 10 we could move the traffic from VLAN 1 to VLAN 10. Ohh and do not forget to disable CDP on those ports!

[JozkoMrkvicka]

"Invalid number: 1. Not in range 2..4094" error when configuring VLAN in Gaia Clish 

[AlekseiShelepov]

As I understand, you are in situation, where you need to have bond0.1 interface together with multiple other VLANs. I had similar situations in previous implementations.

I cannot find the confirmation in documents or in SKs for now. I remember that Timothy Hall wrote about this on CheckMates and most probably in his book, but didn't find it quickly. 

But in general, if an interface is configured as interface with multiple vlans ("trunk"), then IP address shoudn't be assigned to the main interface itself. For example, you shouldn't configure:

eth1 = 192.168.1.1

eth1.2 = 192.168.2.1

eth1.3 = 192.168.3.1

One of possibilities - use separate physical interface for VLAN 1. The easiest way usually if nobody wants to change settings on switches. Best practice is to change default/native vlan on switches, as was mentioned previously.

Another possibility was described by Maarten Sjouw‌ here, change settings of native vlan on the closest switch to Check Point gateway. I did it in the same way also when there was a very simple switch, which couldn't be configured.

[Vladimir]

Thank you guys. I have found the thread you were referring to:

Combine VLAN and physical interface, which already has an assigned IP 

As well as pertinent SKs:  sk110096 and sk88700