Creating a Local Endpoint

Traffic between peered Private Cloud Appliance systems flows through tunnels between endpoints. A rack must have a local endpoint configured before it can participate in a peer connection.

Assuming the network configuration remains the same, a local endpoint is set up once. It remains configured if a peer connection is deleted, so it can be reused for any new connection. These parameters are required to create the local endpoint:

an IP address for each spine switch
the IP addresses of the data center gateways to which the spines are connected
IP address of the capacity ZFS pool and, if present, the high-performance ZFS pool
the ASN ID of your network environment, if applicable

Network Configuration Guidelines

A local endpoint requires a /29 address block, which has 6 usable IP addresses. Within that /29 range, the spine switch pair is assigned 3 IPs (one is shared). Each ZFS pool is assigned 1 IP outside the spine switch subnet. To allow for additional future peer connections, it is recommended to reserve a data center IP range of at least /25 in size, which corresponds with 16 address blocks of /29 size.

When setting up the local endpoint, you must provide the netmask with the peering network IPs, but not with IPs that have already been configured, such as the data center addresses. The gateway IPs must be provided by the network administrator, and assigned to the data center switches to which the spine switches are connected. Note that spine 1 corresponds with gateway 1, and spine 2 with gateway 2.

First Generation DR Migration

Caution

If your systems are set up with a first-generation disaster recovery configuration, and you are migrating to the native disaster recovery service, perform these steps:

Gather the existing disaster recovery configuration details on both appliances, using the drShowService command.

PCA-ADMIN> drShowService
Data:
  Local Ip = 10.100.3.83/28
  Local Ip Perf = 10.100.3.84/28
  Remote Host = sn01-dr1.exmaple.com
  Remote Host Perf = sn02-dr1.exmaple.com
  Replication = ENABLED
  Replication High = ENABLED
  Message = Successfully retrieved site configuration
  maxConfig = 12
  gateway IP = 10.100.3.81
  gateway IP Perf = 10.100.3.81
  Job Retention Hours = 48

Remove the ZFS pool replication IPs from the existing network configuration.

PCA-ADMIN> edit networkConfig ZFSCapacityPoolReplicationEndpoint=""
PCA-ADMIN> edit networkConfig ZFSPerfPoolReplicationEndpoint=""

Use the storage IP addresses (and subnet mask) already assigned to theZFS Storage Appliance Controllers for replication between the storage pools.

Creating the Local Endpoint

When you have obtained all required IP addresses, create the appliance local endpoint using either the Service CLI or Service Web UI.

Service CLI:

Enter the following command on a single line, replacing the sample IPs with the ones you obtained:

PCA-ADMIN> create LocalEndpoint \
spine1Ip=<10.212.128.3/29> datacenterGateway1Ip=<10.212.128.1> \
spine2Ip=<10.212.128.4/29> datacenterGateway2Ip=<10.212.128.2> \
zfsCapacityPoolEndpointIp=<10.212.128.129/29> zfsPerformancePoolEndpointIp=<10.212.128.130/29> \
localAsn=<136025>

Check the local endpoint configuration with the command: getLocalEndpoint.

Service Web UI:

Under Disaster Recovery Service, open the Local Endpoint page. In the top-right corner, click Create.

In the pop-up window, enter the IP addresses in the respective fields. Click Create Local Endpoint to apply the settings.

In the Local Endpoint page, the Information tab indicates the endpoint is configured. Click the Configuration tab to display the details.

Deleting the Local Endpoint

The local endpoint cannot be deleted if it is part of an existing peer configuration. Delete the peer connection first.

To delete the local endpoint:

Service CLI:

Enter the command: deleteLocalEndpoint.
Service Web UI:

Under Disaster Recovery Service, open the Local Endpoint page. In the top-right corner, click Delete.

Oracle Cloud Infrastructure Documentation

Creating a Local Endpoint