Replication IPs
Replication IPs
A replication IP is an address StorONE uses only for replication traffic between two systems —— it's kept separate from the floating IPs your hosts and clients connect to, so replication traffic has its own dedicated path and doesn't compete with or get exposed alongside client-facing services. You need at least one replication IP configured on each of the two systems before you can start replicating; the --sourceIp and --targetIp options on the replication start commands point at these (see Starting and stopping replication).
On an HA (two-node) system, a replication IP actually needs one address per node —— one owned by each node —— so replication traffic keeps flowing if the appliance fails over from one node to the other. On a single-node system, you only supply one address.
Direct vs. VPN
A replication IP connects to its remote counterpart one of two ways:
- Direct (the default)
—— the two systems are reachable on the same routed subnet, so you assign each system's replication IP an address directly on that subnet, along with a mask and (optionally) a gateway. - VPN client
—— the two systems aren't on the same network, for example when replicating over the internet between two sites. One system acts as the VPN server—— its replication IP has a public address the other side can reach—— and the other acts as the VPN client, connecting out to it. When you create a VPN-client replication IP, StorONE automatically creates and configures the matching server-side replication IP on the remote system for you at the same time—— you don't need to separately configure the server side.
Creating a replication IP
Using the web interface
- Open Application Volumes > Replication, then go to the Replication IPs tab.
- Click Create.
- Under Name, enter the replication IP's Name.
- Under Connection Type, choose Direct or VPN Client.
- For a direct connection:
- Under IP Addresses, select the Node(s)
—— one for a single-node system, two for an HA pair—— and, for each node, its Interface and Address. - Under Subnet Mask and Gateway, enter the Mask and, optionally, the Gateway.
- Under IP Addresses, select the Node(s)
- For a VPN client connection, under VPN, enter the VPN Server IP Address (the public address of the remote system) and select the VPN Server System.
- Confirm to create the replication IP.
Using the CLI
replication ips create <name> [--direct|--vpnClient] --nodes=<name...> --interfaces=<name...> --addresses=<ip...> --mask=<subnet> [--gateway=<ip>] [--vpnServerIpAddress=<ip>] [--vpnServerSystem=<name>] [--force]
| Option | Description |
|---|---|
<name> |
Name of the replication IP. |
--direct |
Network connection is direct |
--vpnClient |
Network connection uses VPN; this system acts as a client and connects to another system. |
--nodes=<name...> |
Select one node for a single-node system or two for an HA pair. |
--interfaces=<name...> |
The interface name of the corresponding node. Set an interface for each node. |
--addresses=<ip...> |
The IP addresses of the replication IP. Set an IP for each node. |
--mask=<subnet> |
The subnet mask of the replication IP. |
--gateway=<ip> |
The gateway of the replication IP. |
--vpnServerIpAddress=<ip> |
Public IP address the VPN connects to. |
--vpnServerSystem=<name> |
Server system this VPN connects to. |
--force |
Skip the confirmation prompt. |
Examples
Create a direct replication IP on a single-node system:
replication ips create repl-1 --nodes node1 --interfaces eth3 --addresses 10.10.20.11 --mask 255.255.255.0
Create a direct replication IP on an HA pair, one address per node:
replication ips create repl-1 --nodes node1 node2 --interfaces eth3 eth3 --addresses 10.10.20.11 10.10.20.12 --mask 255.255.255.0 --gateway 10.10.20.1
Create a VPN-client replication IP that connects out to a remote system's public address (this also provisions the matching server-side replication IP on dr-site automatically):
replication ips create repl-to-dr --vpnClient --vpnServerIpAddress 203.0.113.10 --vpnServerSystem dr-site
Editing a replication IP
Using the web interface
- Open Application Volumes > Replication, then go to the Replication IPs tab.
- Select the replication IP and click Edit.
- Under Name, update the Name if needed.
- For a direct replication IP, update the IP Addresses, Subnet Mask and Gateway fields as needed.
- For a VPN replication IP, update the VPN IP Address.
- Confirm the change.
Using the CLI
replication ips edit <name> [--newname=<name>] [(--nodes=<name...> --interfaces=<name...> --addresses=<ip...> --mask=<subnet> [--gateway=<ip>])] [--vpnIpAddress=<ip>] [--force]
| Option | Description |
|---|---|
<name> |
The replication IP to edit. |
--newname=<name> |
New name for the replication IP. |
--nodes=<name...> |
Select one node for a single-node system or two for an HA pair. |
--interfaces=<name...> |
The interface name of the corresponding node. Set an interface for each node. |
--addresses=<ip...> |
The IP addresses of the replication IP. Set an IP for each node. |
--mask=<subnet> |
The subnet mask of the replication IP. |
--gateway=<ip> |
The gateway of the replication IP. |
--vpnIpAddress=<ip> |
Public IP address the VPN connects to. |
--force |
Skip the confirmation prompt for subnet validation warnings. |
Examples
Rename repl-1 to repl-primary:
replication ips edit repl-1 --newname repl-primary
Change the address owned by node1 on a direct replication IP:
replication ips edit repl-1 --nodes node1 --interfaces eth3 --addresses 10.10.20.15 --mask 255.255.255.0
Listing replication IPs
Using the web interface
Open Application Volumes > Replication, then go to the Replication IPs tab. The list shows every replication IP configured on the system.
Using the CLI
replication ips list [<name>] [--ip=<ip>]
| Option | Description |
|---|---|
<name> |
Filter by name. |
--ip=<ip> |
Filter by IP address. |
Example
replication ips list
Deleting a replication IP
A replication IP that's still in use by an active pairing can't be deleted. Deleting a VPN-client replication IP also removes its paired server-side replication IP on the remote system automatically —— you don't need to delete both sides separately.
Using the web interface
- Open Application Volumes > Replication, then go to the Replication IPs tab.
- Select the replication IP and click Delete.
- Confirm the deletion.
Using the CLI
replication ips delete <name> [--force]
| Option | Description |
|---|---|
<name> |
The replication IP to delete. |
--force |
Skip the confirmation prompt. |
Example
replication ips delete repl-to-dr --force
Next: Starting and stopping replication
See also: Replication