Advanced RCCMD Settings for VMware

Use Advanced Settings for additional settings to configure RCCMD.

Event Logfile

In general, any RCCMD Signal affecting the client will be logged. Due to the fact that server systems may provide limited memory resources for log files, it may be necessary to limit the size of the log file to the maximum size to be consumed. In case the maximum file size is reached, the oldest entry is replaced by a new entry.

RCCMD Bindings

RCCMD Bindings is a sophisticated tool that helps you to limit traffic. Since this setting deeply affects your network setting, it should be used with caution. The bindings allow forcing RCCMD to listen on a specific network card. In case multihoming is in use, the listener can be configured to a specific IP address within one network card.  As an example, this will be used if there is a necessity to divide the network logically into a production network and an infrastructure network via VLAN:

In this example scenario, two or more network adapters can be installed. Binding RCCMD to one specific network card will prevent users to access the RCCMD client and accidentally shut down a server - this is only possible via devices that are located in VLAN 3 or have been properly enabled via a router.

Another scenario is the so-called multihoming:

It is not absolutely necessary for modern network devices that an IP address is firmly linked to one network interface. In fact, multiple IP addresses can be connected via a network interface - they share hardware, but otherwise form self-contained instances. As an example, this could be a web server that manages different websites with a unique IP address: the server is connected by a router that distinguishes between incoming signals and signals provided by local network. Bindings will instruct RCCMD to listen for incoming RCCMD signals only at a specific IP address that is assigned to the local network only.

Note

These configurations are used in special scenarios. Normally you can leave the setting 127.0.0.1 / local host, port 6003. In that case, RCCMD will listen on all available IP addresses for a valid incoming signal. Since you have defined the valid sender address in the menu Connections, RCCMD will notice the signal but deny execution and log this fact as an invalid RCCMD command.

Change and Update License Data

Under certain conditions, it may be necessary to modify or change an RCCMD license key for example, when switching to a Corporate Key or if a license key has been assigned twice.

In that case, click on Update License Key and enter the new key directly.

Afterwards, simply stop and restart RCCMD under Status. The new license key will be applied and becomes active immediately.

Change RCCMD Target

The RCCMD appliance is more than just a small tool to handle just VMware hosts. By unchecking the checkbox and pressing Save changes, RCCMD changes to the local mode:

All VMware menus will be disabled and the Shutdown settings will switch to local options:

Due to the fact, RCCMD cannot just receive, but also send RCCMD shutdown signals, it is possible to use an RCCMD appliance as a central RCCMD relay that runs with completely customized additional scripting.

When local mode is active, RCCMD provides the following command sequences:

Shut down system

RCCMD will shut down the server it runs on.

RCCMD shut down relay

With this option, RCCMD will forward a valid RCCMD shutdown to

• Single IP addresses
• An IP address range

With this option, it is possible to get advanced redundancy options - as an example, you may combine a CS141 and a second RCCMD client – if both advise a shutdown, the target RCCMD system will execute the command.

Wait some seconds

RCCMD will wait a customizable time window until the next command in the list will be executed.

System restart

RCCMD will restart the complete RCCMD server that runs within a virtual machine

Custom command

Start programs, run kill commands, run your own scripts; just enter the command and mandatory extensions, and RCCMD will do the rest.