mirror of
https://github.com/vyos/vyos-documentation.git
synced 2025-12-16 10:32:02 +01:00
bonding: correct spelling and grammar
(cherry picked from commit 54bd1933f98708cce7a196f236609143767cb4d3)
This commit is contained in:
parent
f4ed696a46
commit
1b15e4578a
@ -1,3 +1,5 @@
|
||||
:lastproofread: 2021-06-30
|
||||
|
||||
.. _bond-interface:
|
||||
|
||||
#######################
|
||||
@ -47,7 +49,7 @@ Bond options
|
||||
the :cfgcmd:`hash-policy` option, documented below.
|
||||
|
||||
.. note:: Not all transmit policies may be 802.3ad compliant, particularly
|
||||
in regards to the packet mis-ordering requirements of section 43.2.4
|
||||
in regards to the packet misordering requirements of section 43.2.4
|
||||
of the 802.3ad standard.
|
||||
|
||||
* ``active-backup`` - Active-backup policy: Only one slave in the bond is
|
||||
@ -133,9 +135,9 @@ Bond options
|
||||
|
||||
This option only affects 802.3ad mode.
|
||||
|
||||
The default value is 0. This will cause carrier to be asserted (for 802.3ad
|
||||
mode) whenever there is an active aggregator, regardless of the number of
|
||||
available links in that aggregator.
|
||||
The default value is 0. This will cause the carrier to be asserted
|
||||
(for 802.3ad mode) whenever there is an active aggregator,
|
||||
regardless of the number of available links in that aggregator.
|
||||
|
||||
.. note:: Because an aggregator cannot be active without at least one
|
||||
available link, setting this option to 0 or to 1 has the exact same
|
||||
@ -222,7 +224,7 @@ Bond options
|
||||
This algorithm is not fully 802.3ad compliant. A single TCP or UDP
|
||||
conversation containing both fragmented and unfragmented packets will see
|
||||
packets striped across two interfaces. This may result in out of order
|
||||
delivery. Most traffic types will not meet this criteria, as TCP rarely
|
||||
delivery. Most traffic types will not meet these criteria, as TCP rarely
|
||||
fragments traffic, and most UDP traffic is not involved in extended
|
||||
conversations. Other implementations of 802.3ad may or may not tolerate
|
||||
this noncompliance.
|
||||
@ -267,7 +269,7 @@ Bond options
|
||||
be given for ARP monitoring to function.
|
||||
|
||||
The maximum number of targets that can be specified is 16. The default value
|
||||
is no IP addresses.
|
||||
is no IP address.
|
||||
|
||||
Offloading
|
||||
----------
|
||||
@ -498,9 +500,9 @@ Lets assume the following topology:
|
||||
!
|
||||
|
||||
.. note:: When using EVE-NG to lab this environment ensure you are using e1000
|
||||
as the desired driver for your VyOS network interfaces. When using the regular
|
||||
virtio network driver no LACP PDUs will be sent by VyOS thus the port-channel
|
||||
will never become active!
|
||||
as the desired driver for your VyOS network interfaces. When using the
|
||||
regular virtio network driver no LACP PDUs will be sent by VyOS thus the
|
||||
port-channel will never become active!
|
||||
|
||||
*********
|
||||
Operation
|
||||
|
||||
Loading…
x
Reference in New Issue
Block a user