Oracle Cloud Infrastructure Documentation

Network Resource Planning

Plan ahead for the installation of your Roving Edge device and ensure that the necessary network resources have been reserved in advance at the installation site. Work with your data center administrator to set up all required resources and the optional resources your installation needs.

The table describes all network resources that can be part of the network configuration for a Roving Edge device installation. Some are mandatory minimum requirements and are marked as such. In addition, ensure that any optional resources you plan to use for your specific installation are available.

Network Resource

Required

Description

Device uplink IP

uplinkIntfIpCidr

Yes

A reserved IP address in the network to which the device is directly connected. The IP must be entered in CIDR notation. The prefix must match the directly connected subnet. Public network access is required.

A good practice is to use the bootstrap interface IP address, which is already reserved for self-provisioning the physical device, as the uplink interface IP.

Management node virtual IP

mgmtVip

Yes

The IP address to be assigned to the virtual management node and used to access the Service Enclave. The easiest solution is to reserve another IP in the network to which the device is directly connected.

If an IP is reserved from another on-premises network, that IP must be routable from the directly connected network. For routing to the target network, use the uplinkGateway parameter in the system network configuration part of the Edge Platform setup.

DNS server IP

dnsIp1

Yes

The IP address of a DNS server that can be reached from the on-premises network.

At least one DNS IP is required, and must be set as dnsIp1. Up to three DNS IPs can be configured as part of the Edge Platform setup.

NTP server IP

ntpIps

Yes

The IP address of an NTP server that can be reached from the on-premises network. Multiple IPs must be entered as a comma-separated list.

At least one NTP server is required. It's good practice to configure multiple time synchronization sources for redundancy.

Management host name

mgmt01Hostname

Yes

The host name for the device, assigned to the virtual management node. This name will be part of the system FQDN.

Uplink gateway IP

uplinkGateway

No

The IP address of the gateway in the network to which the device is directly connected. The gateway is used to provide device access from on-premises networks beyond the directly connected network.

The uplink gateway is optional. It's not needed if the device is only accessed from the network it's directly connected to. This configuration works if a bastion host is used for access.

Object storage IP

objectStorageIp

(Yes)

The IP address to be used to access object storage on the device. The easiest solution is to reserve another IP in the network to which the device is directly connected.

If an IP is reserved from another on-premises network, that IP must be routable from the directly connected network. For routing to the target network, use the uplinkGateway parameter in the system network configuration part of the Edge Platform setup.

This is a required network resource when using Windows compute instances that connect to network drives (file systems) using the SMB protocol.

Public IPs

publicIps

No

A set or range of IP addresses that can be assigned as public IPs to compute instances. External connectivity in public subnets requires an internet gateway (IGW); for private subnets a NAT gateway must be used.

The easiest solution is to reserve IPs in the network to which the device is directly connected. If these IPs are reserved from another on-premises network, they must be routable from the directly connected network. For routing to the target network, use the uplinkGateway parameter in the system network configuration part of the Edge Platform setup.

Additional DNS server IPs

dnsIp2, dnsIp3

No

The IP addresses of additional DNS servers that can be reached from the on-premises network. One DNS IP is mandatory, but up to three can optionally be configured as part of the Edge Platform setup.

If more than one DNS server is available in the on-premises network, it's good practice to configure multiple DNS sources for redundancy.

Device MTU

deviceMtu

No

The default maximum transfer unit (MTU) is 1500 bytes. You can specify a custom packet size in the range of 1500 to 9000 bytes.

Configure a value higher than the default only if that MTU is supported on the network to which the device is directly connected. Changing the MTU on a running devices requires a reboot.