Wolfspyre
Cadet
- Joined
- Jun 17, 2021
- Messages
- 8
Howdy all!
I’m wondering if anyone else is running into some odd behaviors wrt the network configuration tooling
ive got a dell r720, with a quad 10g nic, exposed to truenas as 8x ‘eno’ interfaces (eno1-eno8 mtu9216)
these are configured as two bonds
bond0 (eno1-4)
bond1 (eno5-8)
(load balance layer 3+4 mtu9216)
bond0 is the parent for several vlan interfaces
vlan1
vlan2
vlan3
vlan10
vlan12
vlan36
vlan40
mtu 9216
bond1 is the parent for several other vlans
vlan198
vlan199
vlan200
mtu 9216
each vlan is the parent of a br# interface
vlan1 -> br1
vlan2 -> br2
mtu 9000
…
the bridge interfaces have static ip’s assigned on different subnets
i have one node already configured like this, working fine.
i am trying to reconfigure my secondary node, and running into some weirdness:
when trying to get this configuration plumbed in the gui or the console, i will frequently get an error
‘keyError’ ‘vlan_parent_interface’
sometimes it’s when trying to create a bond,
sometimes it’s when trying to create a vlan,
sometimes when trying to create a bridge.
regardless, once this occurs, any subsequent attempts to configure anything are pointless, as configuration is impossible.
i’ve tried restoring the default vanilla configuration db and starting from scratch, to no avail.
I SUSPECT there’s some logic bugs in the network validation tooling, and am posting here to see if anyone else is experiencing similar issues.
i’ve searched the forums
i’ve posted on discord in the truenas scale install and general help channels
anyone have a clue-by-four they can hit me over the head with real quick? :)
I’m wondering if anyone else is running into some odd behaviors wrt the network configuration tooling
ive got a dell r720, with a quad 10g nic, exposed to truenas as 8x ‘eno’ interfaces (eno1-eno8 mtu9216)
these are configured as two bonds
bond0 (eno1-4)
bond1 (eno5-8)
(load balance layer 3+4 mtu9216)
bond0 is the parent for several vlan interfaces
vlan1
vlan2
vlan3
vlan10
vlan12
vlan36
vlan40
mtu 9216
bond1 is the parent for several other vlans
vlan198
vlan199
vlan200
mtu 9216
each vlan is the parent of a br# interface
vlan1 -> br1
vlan2 -> br2
mtu 9000
…
the bridge interfaces have static ip’s assigned on different subnets
i have one node already configured like this, working fine.
i am trying to reconfigure my secondary node, and running into some weirdness:
when trying to get this configuration plumbed in the gui or the console, i will frequently get an error
‘keyError’ ‘vlan_parent_interface’
sometimes it’s when trying to create a bond,
sometimes it’s when trying to create a vlan,
sometimes when trying to create a bridge.
regardless, once this occurs, any subsequent attempts to configure anything are pointless, as configuration is impossible.
i’ve tried restoring the default vanilla configuration db and starting from scratch, to no avail.
I SUSPECT there’s some logic bugs in the network validation tooling, and am posting here to see if anyone else is experiencing similar issues.
i’ve searched the forums
i’ve posted on discord in the truenas scale install and general help channels
anyone have a clue-by-four they can hit me over the head with real quick? :)
