The Administrators are allowed to execute the following management operations on the SAM subsystem per manageSAM.sh or manageFW.sh script:
|
Operation |
Command |
|
Start |
manageSAM [-v] start <instanceId> |
|
Stop |
manageSAM [-v] stop <instanceId> |
|
Check Code Integrity |
manageSAM [-v] integrity code <instanceId> |
|
Check Data Integrity |
manageSAM [-v] integrity data |
|
Initialize SAM Firmware |
manageFW [-v] init LogonPass=<user>,<credential> <MBK slot id> |
|
Set IdP Public Keys |
manageFW [-v] setidpkeys LogonPass<user>,<credential> <certfile> |
Table 51: SAM Maintenance Operations
The following figure shows an overview of the management operations carried out by the module SAM Management Module.
Figure 22: Overview of SAM Maintenance operations
The most common success and error scenarios for calling the management operations per manageSAM.sh and manageFW.sh script are listed below:
|
Operation |
Console Output (Exit Code) |
Action |
|
Start |
XYZ code integrity check … ok The subsystem “sam<instanceId>” has been started … ok (0) |
- |
|
Start |
The subsystem “sam<instanceId>” is already running … warning (0) |
- |
|
Start |
XYZ code integrity check … failed Starting the subsystem “sam<instanceId> has been abandoned ... failed (1) |
Check for modifications. |
|
Stop |
The subsystem “sam<instanceId>” has been stopped … ok (0) |
- |
|
Stop |
The subsystem “sam<instanceId>” is not running … warning (0) |
- |
|
Check Code Integrity |
XYZ code integrity check … ok (0) |
- |
|
Check Code Integrity |
XYZ code integrity check … failed. (1) |
Check deployment for modifications. |
|
Check Data Integrity |
Data integrity check … ok (0) |
- |
|
Check Data Integrity |
Data integrity check … failed (1) |
Investigate cause. Check database for modifications. |
|
Initialize SAM Firmware |
Initialization of SAM Firmware … ok (0) |
- |
|
Initialize SAM Firmware |
Initialization of SAM Firmware … failed (1) |
Investigate cause. |
|
Set IdP Public Keys |
Import of IdP Public Keys … ok (0) |
- |
|
Set IdP Public Keys |
Import of Public Keys … failed (1) |
Investigate cause. |
Table 52: Calling of management operations per manageSAM.sh and manageFW.sh