From 8d6a4e78e36535ebcaba44af719ec4ce0a0d5f95 Mon Sep 17 00:00:00 2001 From: niusmallnan Date: Sat, 29 Sep 2018 14:45:12 +0800 Subject: [PATCH] Prompt the impact of DHCP on NIC bonding --- .../os/v1.x/en/installation/networking/interfaces/_index.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/content/os/v1.x/en/installation/networking/interfaces/_index.md b/content/os/v1.x/en/installation/networking/interfaces/_index.md index fa65cafe865..7e4035fb339 100644 --- a/content/os/v1.x/en/installation/networking/interfaces/_index.md +++ b/content/os/v1.x/en/installation/networking/interfaces/_index.md @@ -78,6 +78,10 @@ rancher: In this example two physical NICs (with MACs `0c:c4:d7:b2:14:d2` and `0c:c4:d7:b2:14:d3`) are aggregated into a virtual one `bond0`. +During the bootup process, ROS needs to run cloud-init. It automatically detects the data sources of cloud-init, but some data sources require a network connection. +So in cloud-init, we open `rancher.network.interfaces.eth*.dhcp=true` by default, this may affect the bonding NIC. +There is a way to avoid this problem is to use `rancher.network.interfaces.eth*.dhcp=false` in the kernel cmdline to disable DHCP for all NICs. + ### VLANS In this example, you can create an interface `eth0.100` which is tied to VLAN 100 and an interface `foobar` that will be tied to VLAN 200.