starlingx/docs
Code Issues Proposed changes

Converted table formatting to list-table

Browse Source 
This is in support of pre-processing files without introducing table alignment errors.

Signed-off-by: Stone <ronald.stone@windriver.com>
Change-Id: I78ec8e90c37c0bc4821c5328a6206968cea4e709
This commit is contained in:
Stone 2021-03-03 13:48:44 -05:00
parent b60579b001
commit 788367fa67
1 changed files with 65 additions and 32 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

97
doc/source/node_management/kubernetes/node_interfaces/link-aggregation-settings.rst
View File

@ -55,42 +55,75 @@ controller connects to the primary interface within the |LAG| with the lowest
.. _link-aggregation-settings-table-kb5-rwb-ln:
.. table:: Table 1. Supported Link Aggregation Operational Modes
.. list-table:: Table 1. Supported Link Aggregation Operational Modes
:widths: 100, 300, 200
:header-rows: 1
+-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+
| Mode | Description | Supported Interface Types |
+===================+==============================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+====================================================+
| Active-backup | Provides fault tolerance. Only one slave interface at a time is available. The backup slave interface becomes active only when the active slave interface fails. | Management, OAM, cluster-host, and data interfaces |
| | | |
| \(default value\) | For platform interfaces \(such as, OAM, cluster-host, and management interfaces\), the system will select the interface with the lowest MAC address as the primary interface when all slave interfaces are enabled. | |
+-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+
| Balanced XOR | Provides aggregated bandwidth and fault tolerance. The same slave interface is used for each destination MAC address. | OAM, cluster-host, and data interfaces |
| | | |
| | This mode uses the default transmit policy, where the target slave interface is determined by calculating the source MAC address XOR'd with the destination MAC address, modulo 2. | |
| | | |
| | You can modify the transmit policy using the xmit-hash-policy option. For details, see :ref:`Table 2 <link-aggregation-settings-xmit-hash-policy>`. | |
+-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+
| 802.3ad | Provides aggregated bandwidth and fault tolerance. Implements dynamic link aggregation as per the IEEE 802.3ad \(LACP\) specification. | Management, OAM, cluster-host, and data interfaces |
| | | |
| | You can modify the transmit policy using the xmit-hash-policy option. For details, see :ref:`Table 2 <link-aggregation-settings-xmit-hash-policy>`. | |
| | | |
| | In order to support PXE booting over an aggregated management interface, the far-end switch ports must be configured in passive LACP mode. This is required because the BIOS on the host does not support LACP and cannot establish a LAG, and therefore can use only one of the aggregated interfaces during PXE boot. If the far-end switch is configured to use active LACP, it can establish a |LAG| and use either interface, potentially resulting in a communication failure during the boot process. | |
+-------------------+------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+----------------------------------------------------+
* - Mode
- Description
- Supported Interface Types
* - Active-backup
\(default value\)
- Provides fault tolerance. Only one slave interface at a time is
available. The backup slave interface becomes active only when the
active slave interface fails.
For platform interfaces \(such as, |OAM|, cluster-host, and management
interfaces\), the system will select the interface with the lowest
|MAC| address as the primary interface when all slave interfaces are
enabled.
- Management, |OAM|, cluster-host, and data interface
* - Balanced XOR
- Provides aggregated bandwidth and fault tolerance. The same
slave interface is used for each destination |MAC| address.
This mode uses the default transmit policy, where the target slave
interface is determined by calculating the source |MAC| address XOR'd
with the destination |MAC| address, modulo 2.
You can modify the transmit policy using the xmit-hash-policy option.
For details, see :ref:`Table 2
<link-aggregation-settings-xmit-hash-policy>`.
- |OAM|, cluster-host, and data interfaces
* - 802.3ad
- Provides aggregated bandwidth and fault tolerance. Implements dynamic
link aggregation as per the IEEE 802.3ad |LACP| specification.
You can modify the transmit policy using the xmit-hash-policy option.
For details, see :ref:`Table 2
<link-aggregation-settings-xmit-hash-policy>`.
In order to support |PXE| booting over an aggregated management
interface, the far-end switch ports must be configured in passive
|LACP| mode. This is required because the BIOS on the host does not
support |LACP| and cannot establish a |LAG|, and therefore can use only
one of the aggregated interfaces during |PXE| boot. If the far-end
switch is configured to use active |LACP|, it can establish a |LAG| and
use either interface, potentially resulting in a communication failure
during the boot process.
- Management, |OAM|, cluster-host, and data interface
.. _link-aggregation-settings-xmit-hash-policy:
.. table:: Table 2. xmit-hash-policy Options
.. list-table:: Table 2. xmit-hash-policy Options
:widths: auto
:header-rows: 1
+-------------------+---------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+
| Option | Description | Supported Interface Types |
+===================+=============================================================================================+==============================================================================+
| Layer 2 | Hashes on source and destination MAC addresses. | OAM, internal management, cluster-host, and data interfaces \(worker nodes\) |
| | | |
| \(default value\) | | |
+-------------------+---------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+
| Layer 2 + 3 | Hashes on source and destination MAC addresses, and on source and destination IP addresses. | OAM, internal management, and cluster-host |
+-------------------+---------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+
| Layer 3 + 4 | Hashes on source and destination IP addresses, and on source and destination ports. | OAM, internal management, and cluster-host |
+-------------------+---------------------------------------------------------------------------------------------+------------------------------------------------------------------------------+
* - Options
- Description
- Supported Interface Types
* - Layer 2
\(default value\)
- Hashes on source and destination |MAC| addresses.
- |OAM|, internal management, cluster-host, and data interfaces \(worker
nodes\).
* - Layer 2 + 3
- Hashes on source and destination |MAC| addresses, and on source and
destination IP addresses.
- |OAM|, internal management, and cluster-host
* - Layer 3 + 4
- Hashes on source and destination IP addresses, and on source and
destination ports.
- |OAM|, internal management, and cluster-host