rbSuUnitControl

If reset (2) is selected, the SU should perform reset
and resume running from the current version.
Reset is applicable only for a connected SU, and it does not affect the database
(Get will return the previously selected option).
putToShadow (3), resetAndRunFromShadow (4) and makeRunningVersionOperational (5)
are applicable also for SUs that are not connected: they define the action
that should take place upon network entry of the SU.
If putToShadow (3) is selected, the file specified in rbSuUpgradeSwFileName
will be loaded as the Shadow file (unless it already exists in the SU). 
If resetAndRunFromShadow (4) is selected, the file specified in rbSuUpgradeSwFileName
will be loaded as the Shadow file (unless it already exists as the Shadow),
the SU should perform reset and boot from the Shadow software.
If the specified file already exists as the Main version, no action will take place.
If makeRunningVersionOperational (5) is selected, the file specified in
rbSuUpgradeSwFileName will be loaded as the Shadow file, the SU should perform reset
and boot from the Shadow software, and then swap the Main and Shadow SW Version,
so that the running version (which was previously the Shadow version)
will become the Main version, to be used after next reset.
If no file is specified, the SU should perform the described operations
using the current Shadow file.

MIB

RAINBOW-MIB

OID

.1.3.6.1.4.1.12394.1.2.5.1.1.17

Type

column

Access

readwrite

Status

current

Parent

rbRegisteredSuEntry