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

Made changes based on review comments. Added links to advanced

Browse Source 
hardware control commands to point to the man page and reformatted
based on review comments
This commit is contained in:
Victor Hu 2017-05-10 15:51:32 -04:00
parent d8d18d844d
commit fe763d674a
7 changed files with 25 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/advanced/rflash.rst
View File

@ -1,15 +1,15 @@
``rflash`` - Remote Firmware Flashing
=====================================
For OpenPOWER machines, use the ``rflash`` command to update firmware.
See :doc:`rflash manpage </guides/admin-guides/references/man1/rflash.1>` for more information.
Check firmware version of the node and the HPM file: ::
The ``rflash`` command is provided to assist the system administrator in updating firmware.
rflash cn1 -c /firmware/8335_810.1543.20151021b_update.hpm
To check the current firmware version on the node's BMC and the HPM file: ::
Update node firmware to the version of the HPM file
rflash <noderange> -c /firmware/8335_810.1543.20151021b_update.hpm
::
To update the firmware on the node's BMC to version in the HPM file: ::
rflash cn1 /firmware/8335_810.1543.20151021b_update.hpm
rflash <noderange> /firmware/8335_810.1543.20151021b_update.hpm

8
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/advanced/rinv.rst
View File

@ -1,13 +1,15 @@
``rinv`` - Remote Hardware Inventory
====================================
When you have a lot of physical machines in one place, the most important thing is identify which is which. Mapping the model type and/or serial number of a machine with its host name. Command ``rinv`` is involved in such a situation. With this command, most of the important information to distinct one machine from all the others can be obtained remotely.
See :doc:`rinv manpage </guides/admin-guides/references/man1/rinv.1>` for more information.
To get all the hardware information, which including the model type, serial number, firmware version, detail configuration, et al. ::
Use ``rinv`` command to remotely obtain inventory information of a physical machine. This will help to distinguish one machine from another and aid in mapping the model type and/or serial number of a machine with its host name.
To get all the hardware information for node ``cn1``: ::
rinv cn1 all
As an example, in order to get only the information of firmware version, the following command can be used. ::
To get just the firmware information for ``cn1``: ::
rinv cn1 firm

6
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/advanced/rspconfig.rst
View File

@ -1,10 +1,10 @@
``rspconfig`` - Remote Configuration of Service Processors
==========================================================
Here comes the command, ``rspconfig``. It is used to configure the service processor of a physical machine. On a OpenPower system, the service processor is the BMC, Baseboard Management Controller. Various variables can be set through the command. Also notice, the actual configuration may change among different machine-model types.
See :doc:`rspconfig manpage </guides/admin-guides/references/man1/rspconfig.1>` for more information.
Examples
The ``rspconfig`` command can be used to configure the service processor, or Baseboard Management Controller (BMC), of a physical machine.
To turn on SNMP alerts for cn5: ::
For example, to turn on SNMP alerts for node ``cn5``: ::
rspconfig cn5 alert=on

12
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/advanced/rvitals.rst
View File

@ -1,13 +1,15 @@
``rvitals`` - Remote Hardware Vitals
====================================
Collect runtime information from running physical machine is also a big requirement for real life system administrators. This kind of information includes, temperature of CPU, internal voltage of particular socket, wattage with workload, speed of cooling fan, et al.
See :doc:`rvitals manpage </guides/admin-guides/references/man1/rvitals.1>` for more information.
In order to get such information, use ``rvitals`` command. This kind of information varies among different model types of the machine. Thus, check the actual output of the ``rvitals`` command against your machine, to verify which kinds of information can be extracted. The information may change after the firmware update of the machine. ::
Collecting runtime information from a running physical machine is an important part of system administration. Data can be obtained from the service processor including temperature, voltage, cooling fans, etc.
rvitals cn1 all
Use the ``rvitals`` command to obtain this information. ::
As an example, get only the temperature information of a particular machine. ::
rvitals <noderange> all
rvitals cn1 temp
To only get the temperature information of machines in a particular noderange: ::
rvitals <noderange> temp

7
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/basic/rbeacon.rst
View File

@ -4,11 +4,6 @@
See :doc:`rbeacon manpage </guides/admin-guides/references/man1/rbeacon.1>` for more information.
Most enterprise level servers have LEDs on their front and/or rear panels, one of which is a beacon light. If turned on, this light can help assist the system administrator locate one physical machine out of a large number of machines in a frame.
Most enterprise level servers have LEDs on their front and/or rear panels, one of which is a beacon light. If turned on, this light can assist the system administrator in locating one physical machine in the cluster.
Using xCAT, administrators can turn on and off the beacon light using: ``rbeacon <node> on|off``
There's currently no way to query whether the beacon light is on or off. To work around, first turn off all the lights and then turn on the beacon for the machine you wish to identify: ::
rbeacon <noderange> off
rbeacon <node> on

4
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/basic/rcons.rst
View File

@ -19,7 +19,7 @@ Open a console to ``compute1``: ::
rcons compute1
**Note:** The keystroke ``ctrl+E C .`` will disconnect you from the console.
**Note:** The keystroke ``ctrl+e c .`` will disconnect you from the console.
Troubleshooting
@ -45,7 +45,7 @@ The xCAT ``rcons`` command relies on conserver (http://www.conserver.com/). The
#. After this, try invoking the console again: ``rcons <node>``
OpenBMC Spcific
OpenBMC Specific
```````````````
#. For OpenBMC managed servers, the root user must be able to ssh passwordless to the BMC for the ``rcons`` function to work.

2
docs/source/guides/admin-guides/manage_clusters/ppc64le/management/basic/rpower.rst
View File

@ -3,7 +3,7 @@
See :doc:`rpower manpage </guides/admin-guides/references/man1/rpower.1>` for more information.
Use the ``rpower`` command to remotely power on and off a single server or a range of server. ::
Use the ``rpower`` command to remotely power on and off a single server or a range of servers. ::
rpower <noderange> on
rpower <noderange> off