Project

General

Profile

Actions
Copy link

Bug #10960

closed

Bring up VXLANs correctly at boot

Added by Steve Wheeler over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Viktor Gurov
Category:
Interfaces
Target version:
-
Start date:
10/06/2020
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
All

Description

With the patches from 10898 and 10899 VXLAN interfaces can be added and are created at boot. VXLANs on WAN are configured correctly but throw an error:

Oct 6 00:58:31     php     432     rc.bootup: The command '/sbin/ifconfig 'vxlan0' vxlanid '12345' vxlanremote '172.21.16.187' vxlanlocal '172.21.16.167' vxlanlearn ' returned exit code '1', the output was 'ifconfig: VXLAN_CMD_SET_VNI: Device busy'

This doesn't seem to affect the interface.

VXLANs on other parent interfaces try to come up before the parent resulting in:

Oct 6 00:58:31     php     432     rc.bootup: The command '/sbin/ifconfig 'vxlan3' description 'VXLAN4'' returned exit code '1', the output was 'ifconfig: interface vxlan3 does not exist'
Oct 6 00:58:31     php     432     rc.bootup: The command '/sbin/ifconfig 'vxlan3' -staticarp ' returned exit code '1', the output was 'ifconfig: interface vxlan3 does not exist'
Oct 6 00:58:31     php     432     rc.bootup: The command '/usr/sbin/arp -d -i 'vxlan3' -a > /dev/null 2>&1 ' returned exit code '1', the output was ''

And incomplete configuration. Missing the description and MTU values.

Files

Screenshot from 2020-12-06 23-16-04.png (89.1 KB) Screenshot from 2020-12-06 23-16-04.png Steve Wheeler, 12/06/2020 05:16 PM
Actions
Copy link

Also available in: Atom PDF