X-Git-Url: https://git.proxmox.com/?p=pve-docs.git;a=blobdiff_plain;f=pve-network.adoc;h=e6deb43dc7ab1e6254e1d9327ceafa0cc87ffc7c;hp=8146a3b16ea4f8f10b15fa7f9f2540f7b45558c2;hb=63a0180693d69c0875c388e6ca7df46bca64efca;hpb=cd1de2c286d63fb59a857cd82b411d66d2339a80

diff --git a/pve-network.adoc b/pve-network.adoc
index 8146a3b..e6deb43 100644
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -1,6 +1,10 @@
+[[sysadmin_network_configuration]]
 Network Configuration
 ---------------------
 include::attributes.txt[]
+ifdef::wiki[]
+:pve-toplevel:
+endif::wiki[]
 
 {pve} uses a bridged networking model. Each host can have up to 4094
 bridges. Bridges are like physical network switches implemented in
@@ -154,10 +158,22 @@ iface vmbr0 inet static
 Linux Bond
 ~~~~~~~~~~
 
-Bonding is a technique for binding multiple NIC's to a single network
-device.  It is possible to achieve different goals, like make the
-network fault-tolerant, increase the performance or both
-together.
+Bonding (also called NIC teaming or Link Aggregation) is a technique
+for binding multiple NIC's to a single network device.  It is possible
+to achieve different goals, like make the network fault-tolerant,
+increase the performance or both together.
+
+High-speed hardware like Fibre Channel and the associated switching
+hardware can be quite expensive. By doing link aggregation, two NICs
+can appear as one logical interface, resulting in double speed. This
+is a native Linux kernel feature that is supported by most
+switches. If your nodes have multiple Ethernet ports, you can
+distribute your points of failure by running network cables to
+different switches and the bonded connection will failover to one
+cable or the other in case of network trouble.
+
+Aggregated links can improve live-migration delays and improve the
+speed of replication of data between Proxmox VE Cluster nodes.
 
 There are 7 modes for bonding: