public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-17 02:23:19 +00:00
Code Issues Packages Projects Releases Wiki Activity

Prompt the impact of DHCP on NIC bonding

Browse Source
This commit is contained in:
niusmallnan
2018-09-29 14:45:12 +08:00
parent f6120181c3
commit 8d6a4e78e3
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/os/v1.x/en/installation/networking/interfaces/_index.md
+4
View File
@@ -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.