.. _list_of_unused_cluster_commands:

List of Unused Cluster Commands
-------------------------------

.. index:: cluster

.. _19.1|DOC-188:
.. _12.5(1)|DOC-188:

The following table shows **cluster** commands that 
should not used:


+-------------------------------------------------+
| command                                         |
+=================================================+
| **cluster run all system shutdown**             |
+-------------------------------------------------+
| **cluster run all system reboot**               |
+-------------------------------------------------+
| **cluster run <any> backup create XXX**         |
+-------------------------------------------------+
| **cluster run <any> cluster upgrade**           |
+-------------------------------------------------+
| **cluster run <any> cluster run XXX**           |
+-------------------------------------------------+
| **cluster run <any> cluster provision**         |
+-------------------------------------------------+
| **cluster run all cluster add <ip>**            |
+-------------------------------------------------+
| **cluster run all cluster del <ip>**            |
+-------------------------------------------------+
| **cluster run all cluster job kill <pid>**      |
+-------------------------------------------------+
| **cluster run all cluster job list**            |
+-------------------------------------------------+
| **cluster run all cluster job reconnect <pid>** |
+-------------------------------------------------+
| **cluster run all cluster list**                |
+-------------------------------------------------+
| **cluster run all cluster status**              |
+-------------------------------------------------+


Only one **cluster** command can be run on web proxy nodes.
A message is shown if running the other **cluster** commands, for example
running the **cluster list** and **cluster status** commands *on a web proxy node*:

::

   $ cluster list
   Invalid command syntax - refer to help descriptions

   USAGE:
   ------
   cluster prepnode  - Prepares the system so that it can be joined to a cluster 




   $ cluster status
   cluster status not available on webproxy nodes.



To exclude these **cluster** commands from running on web proxy nodes,
use the ``<where>`` parameter to specify the node types, for example, 
with the ``database`` node type as specified below:


::

   $ cluster run database cluster list
   You are about to a run a command across the cluster, which could affect service availability.
   Do you wish to continue? y
   
   
   ---------- VOSS-UN-1, ip=164.168.151.3, role=webproxy,application,database, loc=cpt
   
   
   Cluster has 8 nodes:
   
        application :  164.168.151.3, 164.168.151.5, 164.168.151.4, 164.168.151.7, 164.168.151.6, 164.168.151.8
           webproxy :  164.168.151.3, 164.168.151.5, 164.168.151.4, 164.168.151.7, 164.168.151.6, 164.168.151.9, 164.168.151.8, 164.168.151.10
           database :  164.168.151.3, 164.168.151.5, 164.168.151.4, 164.168.151.7, 164.168.151.6, 164.168.151.8
   
   
   
   
   ---------- VOSS-UN-3, ip=164.168.151.5, role=webproxy,application,database, loc=cpt

   [...]