xCAT/xcat-core
2
0
Fork 0
mirror of https://github.com/xcat2/xcat-core.git synced 2025-08-11 22:10:14 +00:00
Code Issues Releases Wiki Activity

Spelling fixes in advanced/networks docs

Browse Source
This commit is contained in:
besawn
2022-02-10 08:19:58 -05:00
parent dab905c853
commit 60af1ce6c0
10 changed files with 11 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/source/advanced/networks/ethernet_switches/ethernet_switches.rst
View File

@@ -62,7 +62,7 @@ Switch Management
When managing Ethernet switches, the admin often logs into the switches one by one using SSH or Telnet and runs the switch commands. However, it becomes time consuming when there are a lot of switches in a cluster. In a very large cluster, the switches are often identical and the configurations are identical. It helps to configure and monitor them in parallel from a single command.
For managing Mellanox IB switches and Qlogic IB switches, see :doc:`Mellanox IB switches and Qlogic IB switches </advanced/networks/infiniband/index>`
For managing Mellanox IB switches and Qlogic IB switches, see :doc:`Mellanox IB switches and Qlogic IB switches </advanced/networks/infiniband/index>`
xCAT will not do a lot of switch management functions. Instead, it will configure the switch so that the admin can run remote command such as ``xdsh`` for it. Thus, the admin can use the ``xdsh`` to run proprietary switch commands remotely from the xCAT mn to enable **VLAN**, **bonding**, **SNMP** and others.
@@ -77,7 +77,7 @@ Add the switch in xCAT DB. Refer to the "Discovering Switches" section if you wa
mkdef bntc125 groups=switch mgt=switch ip=10.4.25.1 nodetype=switch switchtype=BNT
Set the ssh or telnet username an d password. ::
Set the ssh or telnet username and password. ::
chdef bntc125 username=admin \
password=password \

2
docs/source/advanced/networks/infiniband/mlnxofed_ib_install_diskless.rst
View File

@@ -26,7 +26,7 @@ Diskless Installation
/install/postscripts/mlnxofed_ib_install \
-p /install/<path-to>/<MLNX_OFED_LINUX.iso> -i $1 -n genimage
.. note:: The ``$1`` is a argument that is passed to the the postinstall script at runtime.
.. note:: The ``$1`` is a argument that is passed to the postinstall script at runtime.
.. tip:: **Kernel Mismatch**

2
docs/source/advanced/networks/infiniband/mlnxofed_ib_install_preparation.rst
View File

@@ -36,7 +36,7 @@ The ``mlnxofed_ib_install`` is a sample script intended to assist with the insta
| | || of the string to mark the completion of the option list |
| | || option list. |
| | || |
| | || If nothing is specified, xCAT passes the the following |
| | || If nothing is specified, xCAT passes the following |
| | || ``--without-32bit --without-fw-update --force`` |
+---------+------------------+----------------------------------------------------------+
|``-i`` | For diskless || The image root path of the diskless image |

2
docs/source/advanced/networks/infiniband/ufm_configuration.rst
View File

@@ -55,7 +55,7 @@ The default port is 162. For example: ::
[Notifications]
snmp_listeners = 10.0.0.1
Where 10.0.0.1 is the the ip address of the management node.
Where 10.0.0.1 is the ip address of the management node.
3. On the UFM host, restart the ufmd ::

2
docs/source/advanced/networks/onie_switches/index.rst
View File

@@ -1,7 +1,7 @@
Open Network Install Environment Switches
=========================================
The Open Network Install Environment, or "ONIE" [1]_. is an open source project definining an **install environment** for bare metal switches. This environment allows choice for the end users when selecting a network operating system to install onto these bare metal switches.
The Open Network Install Environment, or "ONIE" [1]_. is an open source project defining an **install environment** for bare metal switches. This environment allows choice for the end users when selecting a network operating system to install onto these bare metal switches.
.. toctree::
:maxdepth: 2

2
docs/source/advanced/networks/onie_switches/os_cumulus/manage.rst
View File

@@ -24,7 +24,7 @@ Switch Port and VLAN Configuration
xCAT places the front-panel port configuration in ``/etc/network/interfaces.d/xCAT.intf``.
The ``configinterface`` postscript can be used to pull switch interface configuration from the xCAT Management Node (MN) to the switch. Place the switch specific confguration files in the following directory on the MN: ``/install/custom/sw_os/cumulus/interface/``.
The ``configinterface`` postscript can be used to pull switch interface configuration from the xCAT Management Node (MN) to the switch. Place the switch specific configuration files in the following directory on the MN: ``/install/custom/sw_os/cumulus/interface/``.
xCAT will look for files in the above directory in the following order:

2
docs/source/advanced/networks/onie_switches/os_cumulus/prepare.rst
View File

@@ -20,7 +20,7 @@ Prepare the Cumulus Linux files on the xCAT Management Node.
Cumulus osimage
---------------
xCAT can able to create a cumulus osimage defintion via ``copycds`` command. ``copycds`` will copy cumulus installer to a destination directory, and create several relevant osimage definitions. **cumulus<release>-<arch>** is the default osimage name. ::
xCAT can able to create a cumulus osimage definition via ``copycds`` command. ``copycds`` will copy cumulus installer to a destination directory, and create several relevant osimage definitions. **cumulus<release>-<arch>** is the default osimage name. ::
#run copycds command
# copycds cumulus-linux-3.5.2-bcm-armel.bin

2
docs/source/advanced/networks/onie_switches/os_cumulus/ztp.rst
View File

@@ -55,7 +55,7 @@ Leveraging the ZTP mechanism, xCAT provides the capability to setup ONIE switche
5. Plug the ONIE switches into the cluster according to the network plan and power on them.
For the white-box ONIE switches, the Cumulus OS will be installed, then the switches will be discovered and configured automaticaly, the whole process will take about 1 hour.
For the white-box ONIE switches, the Cumulus OS will be installed, then the switches will be discovered and configured automatically, the whole process will take about 1 hour.
For the ONIE switches already with Cumulus OS installed, please make sure the ZTP have been enabled and none of the following manual configuration have been made:

2
docs/source/advanced/networks/switchdiscover/switch_based_switch_discovery.rst
View File

@@ -55,7 +55,7 @@ In order to do switch-based switch discovery, the admin
"192_168_0_0-255_255_0_0","192.168.0.0","255.255.0.0","enP4p1s0f2","<xcatmaster>",,"192.168.3.29",,,,"192.168.5.150-192.168.5.170",,,,,,,,,
dhcp should be restarted after seting up dynamic IP range.
dhcp should be restarted after setting up dynamic IP range.
Discover Switches

2
docs/source/advanced/networks/switchdiscover/switches_discovery.rst
View File

@@ -37,5 +37,5 @@ The discovery process works with the following four kind of switches: ::
BNT
Juniper
The ``switchdiscover`` command can display the output in xml format, stanza forma and normal list format. See the man pages for this command for details.
The ``switchdiscover`` command can display the output in xml format, stanza format and normal list format. See the man pages for this command for details.