Create a CIRA Config
Client Initiated Remote Access (CIRA) enables a CIRA-capable edge device to initiate and establish a persistent connection to the MPS. As long as the managed device is connected to the network and to a power source, it can maintain a persistent connection.
Note - Wireless Activations
This express setup assumes the managed device (i.e. AMT device) is on a wired connection for quickest setup. To learn more about a Wireless Setup, see the Wireless Activation Tutorial.
To create a CIRA Config:
-
Select the CIRA Configs tab from the left-hand menu.
-
In the top-right corner, click Add New.
Figure 1: Create a new CIRA Config -
Specify a Config Name of your choice.
-
Select IPv4.
-
For MPS Address, provide your development system's IP Address.
-
Cert Common Name (CN=) should auto-populate. If not, provide your development system's IP Address.
-
Leave Port as the default, 4433.
-
Leave the Username as admin or choose your own.
-
Leave the slider set on Auto-load.
-
Click Save.
Example CIRA Config
Figure 2: Example CIRA Config
Next up¶
Profiles provide configuration information to the AMT Firmware during the activation process with the Remote Provisioning Client (RPC). Profiles also distinguish between activating in:
Client Control Mode (CCM): This mode offers all manageability features including, but not limited to, power control, audit logs, and hardware info. Redirection features, such as KVM or SOL, require user consent. The managed device will display a 6-digit code that must be entered by the remote admin to access the remote device via redirection.
Admin Control Mode (ACM): ACM mode supports all manageability features without requiring user consent. This means it is not necessary to have a person on-site to remote in and manage an edge device. In most IoT use cases, edge devices such as digital signage or kiosks may not be easily accessible or have available employees nearby. ACM mode proves immensely helpful in these scenarios.