bonding and vlans. Bonding a vlan interface vs applying vlans to a bond interface
My soul purpose here is to have flexibility to change the physical media around with out changing the interface name.
I'd to bring up the vlan interfaces on the Ethernet devices, then enslave them into bonds. I would like to have bond0 bond1 and bond2 inteface names to stay consistent (Oracle RAC annoyance)
ETH0 --> eth0.122
ETH1 --> eht1.122
ifenslave bond1 eth0.122 eth1.122
I see no documentation showing this approach. I see plenty of howto's where you bond up eth0 and eth1 into bond0, then apply vlans to bond0 as bond0.122
Trying to maximize the 10G pipe and get rid of copper and save on fiber port costs. If I can manage to pull a node down and move a vlan to another switch or cable and change it's underlining Ethernet interface, that would be cool.
If we use the bond0.122 method, and have to make a change, it would require a re-configuration of clusterware and a complete cluster outage to make things work on bond1.122