You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a VLAN interface has two physical ports on different switches configured, the v4/provisioner/layer2interfaces/switch-name/$switch.json API returns an incorrect port name for the second switch port.
STEPS TO REPRODUCE
My procedure to migrate a member to a different switch is:
add the new physical port to the existing VLAN interface
ignore the warning saying that this is not supported because the ports are in different switches
generate the configuration for the new switch using data from the L2 provisioner API
move the fiber
remove the old physical port
At step 3 both the old and the new interface are configured in IXP manager.
EXPECTED RESULTS
The API should return the correct port for the switch.
ACTUAL RESULTS
The API returns the name of the first port also for the second switch.
IMPORTANCE
Not being able to automatically generate the configuration for a new switch port significantly increases the risk of configuration mistakes.
The text was updated successfully, but these errors were encountered:
Yes, the ultimate goal is migrating the port.
Just editing the port is sub optimal because it needs to be coordinated tightly with the data center activity (and causes loss of statistics?).
Regarding the process, I can only speak to how we typically do these. For us, we'd never have two ports enabled for a member during a migration for fear of l2 loops / etc. You never know what's on the member end of the link. So we always co-ordinate on time and the process for us is:
member drains traffic on old port
member disables old port [i.e. onus is on the member to take their port down]
we see port down / member tells us and then we disable the old port on our end.
swap switch/switchport on physical interface
new port already enabled in quarantine lan usually, member configures new port and we test pings and follow quarantine
deploy new config to push to production
member up on new port
Statistics wise - adding two physical interfaces won't solve that as the mrtg config stores the data in dedicated physical interface files. I.e. old port data in old phys int file and new port data in new phys int file. The only time their combined is if the port is a lag.
ISSUE TYPE
Bug Report
OS
Ubuntu 24.04 LTS
VERSION
SUMMARY
When a VLAN interface has two physical ports on different switches configured, the
v4/provisioner/layer2interfaces/switch-name/$switch.json
API returns an incorrect port name for the second switch port.STEPS TO REPRODUCE
My procedure to migrate a member to a different switch is:
At step 3 both the old and the new interface are configured in IXP manager.
EXPECTED RESULTS
The API should return the correct port for the switch.
ACTUAL RESULTS
The API returns the name of the first port also for the second switch.
IMPORTANCE
Not being able to automatically generate the configuration for a new switch port significantly increases the risk of configuration mistakes.
The text was updated successfully, but these errors were encountered: