some small spelling/grammar fixes

[pve-docs.git] / pve-network.adoc

diff --git a/pve-network.adoc b/pve-network.adoc
index f14033cf12ded9ee724e48eae4b08531807fdb60..45f64249b687c52c6d52a3145aab8b602f3159a1 100644 (file)
--- a/pve-network.adoc
+++ b/pve-network.adoc
@@ -1,6 +1,9 @@
+[[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 +157,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:
 
@@ -193,8 +208,7 @@ designated slave network interface. If this receiving slave fails,
 another slave takes over the MAC address of the failed receiving
 slave.
 
-* *Adaptive load balancing (balanceIEEE 802.3ad Dynamic link
-aggregation (802.3ad)(LACP):-alb):* Includes balance-tlb plus receive
+* *Adaptive load balancing (balance-alb):* Includes balance-tlb plus receive
 load balancing (rlb) for IPV4 traffic, and does not require any
 special network switch support. The receive load balancing is achieved
 by ARP negotiation. The bonding driver intercepts the ARP Replies sent
@@ -207,6 +221,10 @@ traffic.
 For the most setups the active-backup are the best choice or if your
 switch support LACP "IEEE 802.3ad" this mode should be preferred.
 
+The following bond configuration can be used as distributed/shared
+storage network. The benefit would be that you get more speed and the
+network will be fault-tolerant.
+
 .Example: Use bond with fixed IP address
 ----
 auto lo
@@ -236,7 +254,11 @@ iface vmbr0 inet static
 
 ----
 
-.Example: Use a bond with a bridge
+
+Another possibility it to use the bond directly as bridge port.
+This can be used to make the guest network fault-tolerant.
+
+.Example: Use a bond as bridge port
 ----
 auto lo
 iface lo inet loopback