rp_rcm_startup

Starts an RCM using the specified path and configuration file.

rp_rcm_startup [rcm_path, rcm_cfg, rcm_log, rcm_retries, rcm_redundant]

rcm_path: Path to the RCM binary.

If not provided (NULL), the RCM binary is executed using the value of the RCM_PATH parameter set in the OpenSwitch configuration file. If RCM_PATH is not set, the RCM binary is executed from $OPENSWITCH/bin/rcm on UNIX and from %OPENSWITCH%\bin\rcm on Windows.

When you provide rcm_path, the RCM executable is invoked from the specified location. You must have execution permission on the RCM binary.

rcm_cfg: Absolute path to the RCM configuration file. If not provided, the value specified by the RCM_CFG_FILE parameter in the OpenSwitch configuration file is used. You must have read access on this file.

rcm_log: Absolute path to the RCM log. If not provided, the value specified by the RCM_LOG_FILE parameter in the OpenSwitch configuration file is used.

rcm_retries: An integer value to specify the number of times OpenSwitch restarts the RCM if it fails. If NULL, the value specified by RCM_RETRIES parameter in the OpenSwitch configuration file is used.

rcm_redundant: An Boolean value (1 is “true” and zero (0) is “false”) to specify whether or not the RCM being started is a redundant RCM. If 1, the RCM binary is executed with the “-R” option. If zero (0), the RCM binary is not executed with the “-R” option.

Starts the RCM with the default RCM binary, trying twice, with no redundancy.

1> rp_rcm_startup NULL, /scratch/15.0_bld2/OpenSwitch-15_1/config/rcm.cfg,
   /scratch/15.0_bld2/OpenSwitch-15_1/logs/rcm.log, 2, 0
2> go

Returns:

Msg 20107, Level 16, State 0:
Server 'monsoon_OSW':rp_rcm_startup: 
The RCM has been started.
(return status = 0)

RCM_AUTOSTART must be set to 1 in the OpenSwitch configuration file to run this command. Use rp_set to dynamically configure RCM_AUTOSTART.
Verify that RCM_CFG_FILE and RCM_LOG_FILE are pointing to valid locations and that the files to which these parameters point have the proper access permissions before executing rp_rcm_startup.
Always check the OpenSwitch error log after you run rp_rcm_startup to verify that the RCM has started; the command can sometimes return a success before the RCM has completely started. When rp_rcm_startup is successful, you see this message in the OpenSwitch error log:
```
INFO: spid 19: rp_rcm_startup: The RCM has been started.
INFO: spid 22: rcm__thread: Service thread spawned.
```
After you start the RCM, use rp_rcm_list to verify that the RCM has started.