Reconfiguring the Roving Edge Operating Environment

The operating environment is configured during the initial setup of Roving Edge. An administrator can update this configuration, for example when the device is moved to a new location. Careful planning is advised, because device networking changes could disrupt active workloads.

The base configuration of the Roving Edge device is applied during this procedure: Completing the Edge Platform Software Initial Setup and Configuration. Most of these parameters can be changed on an operational device without requiring a full reset.

Updating the System Operating Mode

The device registration with OCI can be updated.

Using the Service Web UI

Initial configuration steps are described in Setting the System Operating Mode.

In the navigation menu, select Appliance.
In the top-right corner of the Appliance Details page, select Controls, then Edit, to display the System Details window.
Clear the checkbox under Link to OCI. The controls to link the system to OCI are displayed.
1. To clear the existing link, select Unlink from OCI.
2. To relink the device, enter all required OCI tenancy and infrastructure parameters.
  
  Pay special attention to these settings:
  - Connected Mode: select True
  - IAM Data Source: select Local
3. Select Link to OCI to confirm the settings.
  
  At this point you can unlink and relink to update the link settings. When you select Save Changes in the next step, all one time setup parameters are locked in and can no longer be changed.
Select the checkbox under Link to OCI to hide the OCI link controls, and display the system parameters.
- If necessary, change the rack name and description.
- The system name and domain cannot be modified.
Select Save Changes to apply the updated settings. You're returned to the Appliance Details page.

Using the Service CLI

Initial configuration steps are described in Setting the System Operating Mode.

To clear the existing link, use the command unlinkFromOCI with no additional parameters.

To relink the device, use the linkToOci command.

RED2-ADMIN> linkToOci \
ociTenancyId=ocid1.tenancy.oc1...<unique_id> 
ociInfrastructureId=ocid1.cccinfrastructure.oc1...<unique_id> \ 
region=us-ashburn-1 regionKey=IAD realmDomainComponent=testrealm.com

Confirm the system is linked.

RED2-ADMIN> show pcaSystem
Data:
  Id = 5709f72b-c439-4c3a-8959-758df94eff25
  Type = PcaSystem
  Product Type = RED2
  System Mode = Linked
  Connected State = true
  System Config State = Config System Params
[...]

Updating the System Network

The network configuration parameters can be updated to keep the device operational when its environment changes.

Note

If the device MTU is changed, the node must be rebooted. See Rebooting a Roving Edge Device.

Note

You can check the NTP connection status of a running system at any time. In the Service Web UI, it's displayed in the NTP tab of the Network Environment Information page. In the Service CLI you can run this command:

PCA-ADMIN> checkNtpServers
Data:
  id              Accessible
  --              ----------
  10.64.0.252     true
  192.0.2.2       true

Using the Service Web UI

Initial configuration steps are described in Configuring the System Network.

In the navigation menu, click Network Environment. The current configuration is displayed in multiple tabs.
In the top-right corner of the Network Environment Information page, click Edit. The Configure Network Params wizard is displayed.
Use Next and Previous to navigate between the wizard pages. Make the required changes to the configuration parameters.
Select Save Changes to apply the updated configuration.

Using the Service CLI

Initial configuration steps are described in Configuring the System Network.

Display the current network configuration information using the show networkConfig command.

RED2-ADMIN> show networkConfig
Data:
  Advance Network Mode = false
  NTP Server(s) = 10.25.68.1,10.25.0.4,10.211.17.1
  Public Ip range/list = 10.25.125.129/27,10.25.125.162/32,10.25.125.163/32
  DNS Address1 = 206.223.27.1
  DNS Address2 = 206.223.27.2
  Management Node1 Hostname = red01
  Management VIP = 10.25.125.101
  Object Storage Ip = 10.25.125.164
  Uplink Static Routing = true
  Uplink Gateway = 10.25.125.1
  Uplink Intf Ip Cidr = 10.25.125.161/24
  Network Config Lifecycle State = ACTIVE
  Enable Admin Network = false
  Free Public Ips = 10.25.125.129/27,10.25.125.162/32,10.25.125.163/32
  Provisioned Public Ip Count = 32

Use the setSimpleNetworkConfig command to change any of these parameters:

RED2-ADMIN> setSimpleNetworkConfig ?
                                   activeConfiguration
                                   uplinkGateway
                                   uplinkIntfIpCidr
                                   mgmtVip
                                   mgmt01Hostname
                                   publicIps
                                   ntpIps
                                   dnsIp1
                                   dnsIp2
                                   dnsIp3
                                   objectStorageIp
                                   deviceMtu

The configuration is overwritten with the new parameters you provide.

Example:

RED2-ADMIN> setSimpleNetworkConfig activeConfiguration=True \
uplinkGateway=10.80.16.1 uplinkIntfIpCidr=10.80.16.65/24 \
mgmtVip=10.80.16.66 mgmt01Hostname=red01 \
ntpIps=10.80.16.1,10.0.0.4,10.211.17.1 \
dnsIp1=206.223.27.1 dnsIp2=206.223.27.2 \
publicIps=10.80.16.128/26,10.80.16.67/32,10.80.16.68/32
objectStorageIp=10.80.16.69

Status: Running
JobId: aafb988c-9bad-4b28-a7ba-7c6a77f55dde
Data: Created a job for setSimpleNetworkConfig

Confirm that network configuration has completed successfully, where System Config State = Complete.

RED2-ADMIN> show pcaSystem
Data:
  Id = 5709f72b-c439-4c3a-8959-758df94eff25
  Type = PcaSystem
  Product Type = RED2
  System Mode = Linked
  Connected State = true
  System Config State = Complete
[...]

Configuring Appliance Proxy Settings

The initial Edge Platform setup procedure, as described in Completing the Edge Platform Software Initial Setup and Configuration, provides no option to add a system-wide proxy configuration. However, some of the platform and infrastructure services require connectivity to endpoints outside the appliance environment. For example, for federation with an identity provider (IDP), the IAM and Admin services must acquire metadata from that external server (for users of the Compute Enclave and Service Enclave respectively.) If network traffic passes through a proxy server in the data center, requests between the appliance and the external server cannot be completed successfully.

To enable external network communication through a data center proxy server, add the proxy configuration to the appliance network setup.

Caution

Ensure that the Edge Platform setup procedure has been completed first.

Using the Service Web UI

In the PCA Config navigation menu, click Appliance Details.

The Appliance Details page contains system properties such as realm, region and domain.
To configure a proxy at the system level, select Controls in the top-right corner, then select Set Rack-Wide Proxy.

A proxy configuration window appears.
Fill out the proxy configuration parameters:
- Proxy Name: Enter the fully qualified domain name of the proxy server.
- Proxy Host: Enter the proxy server IP address.
- Proxy Port: Enter the port number the proxy server uses for routing requests.
- Proxy User Name: If required, enter a user name for authentication with the proxy server.
- Proxy Password: If required, enter the password for the proxy user name.
- Proxy Confirm Password: If required, enter the proxy password again for confirmation.
The user name and password parameters are optional, in case the proxy server requires authentication. The details are stored in the Secret Service (Vault), where services can retrieve them securely to establish their external connection.
Select Set Rack-Wide Proxy to save the proxy configuration.

The proxy configuration is displayed in a separate tab on Appliance Details page.
To delete the proxy configuration from the appliance, go to the Appliance Details page. Select Controls in the top-right corner, then select Clear Rack-Wide Proxy.
If you need to modify the stored proxy configuration, delete it and fill out the proxy configuration window again with the correct parameters.

Using the Service CLI

Add the proxy configuration details using the setProxy command.

Syntax (entered on a single line):

RED2-ADMIN> setProxy
proxyName=<proxy_fqdn>
proxyHost=<proxy_ip>
proxyPort=<proxy_port>
proxyUsername=<proxy_user>
proxyPassword=<proxy_password>
proxyConfirmPassword=<proxy_password>

Example:

RED2-ADMIN> setProxy proxyName=myproxy.example.com
proxyHost=172.16.0.100
proxyPort=8080
proxyUsername=proxyuser
proxyPassword=********
proxyConfirmPassword=********

The user name and password parameters are optional, in case the proxy server requires authentication. The details are stored in the Secret Service (Vault), where services can retrieve them securely to establish their external connection.

To delete the proxy configuration from the appliance, enter the clearProxy command. No command parameters are required.
If you need to modify the stored proxy configuration, run the setProxy command again with the correct parameters.

If you set the proxy before completing the Edge Platform setup

Run the setProxy command using a different port. This temporary setting is incorrect, but enables you to correct it later.
```
RED2-ADMIN> setProxy proxyName=myproxy.example.com
proxyHost=172.16.0.100
proxyPort=8800
```
Wait five minutes to let the update take effect.
Run the setProxy command again using the correct settings. Because the parameters are different, this command overwrites the existing entries.
```
RED2-ADMIN> setProxy proxyName=myproxy.example.com
proxyHost=172.16.0.100
proxyPort=8080
```

Oracle Cloud Infrastructure Documentation

Reconfiguring the Roving Edge Operating Environment

Updating the System Operating Mode

Updating the System Network

Configuring Appliance Proxy Settings