OST: Using opduptranslate to Translate IP Addresses |
Quantum Q-Cloud is a subscription service for customers who do not want to purchase a second DXi system and would rather replicate data to a target DXi system in the Q-Cloud. Customers can use Namespace replication, File/Cartridge based replication, or OpenStorage (OST) Optimized Duplication to replicate to a DXi system in the Q-Cloud. Of these replication options, only OST Optimized Duplication uses the opduptranslate command.
SR Information: No specific SR information is available
Product / Software Version: DXi7500, DXi8500, and DXi670x systems with 1.x software. In addition, DXi systems with 2.1, 2.2, and 2.2.1.
Problem Description: If Optimized Duplication is configured on both a “local” source DXi system and a “Q-Cloud” target DXi system, the data in the Q-Cloud target DXi cannot be sent back to the local source DXi system until the opduptranslate command is run on the target DXi system.
|
When configuring Optimized Duplication on both a “local” source DXi system and a “Q-Cloud” target DXi system, the opduptranslate command needs to be executed once on the Q-Cloud target DXi system. The command updates a configuration file on the target DXi system by translating the IP address of the source DXi system to its NAT server address. This update is needed because the target DXi system is only aware of the source DXi system’s NAT server address and NOT its IP addresses. Once the command is executed, the data in the Q-Cloud target DXi can then be pushed back to the local source DXi system, when needed.
The syscli opduptranslate command is run from the /opt/DXi directory.
On the target DXi system in the cloud, opduptranslate modifies the “Configured_Targets” section of config file: /data/hurricane/conf/NewReplication.conf
The opduptranslate command syntax can differ depending on the firmware revision. A syscli opduptranslate help command should be run on the Q-Cloud target DXi for confirmation.
DXi4500 with FW 2.2.1: syscli opduptranslate Help
Valid syntax:
Allows to map OST target ip address to a replication ip address.
Allows to delete the mapping of OST target ip address for a replication ip address.
Gets the replication ip address for a translated OST target ip address.
Allows to edit the existing map of OST target ip address to a replication ip address.
Lists all mappings of OST target ip address to a replication ip address.
DXi6702 running FW 2.1.1: syscli opduptranslate Help
Valid syntax:
Allows to map OST target ip address to a replication ip address.
Allows to delete the mapping of OST target ip address for a replication ip address.
Gets the replication ip address for a translated OST target ip address.
Example #1: DXi4500 with 2.2.1 Software
By default, the /data/hurricane/conf/NewReplication.conf does not exist on the cloud target DXi system. The add opduptranslate command creates the file and adds the configuration information.
[root@asps-l-DXi4500 DXi]# syscli --add opduptranslate --replicationip 13.40.6.54 --dataip 10.70.208.127
Command completed successfully.
[root@asps-l-DXi4500 DXi]#
In the example above, “replicationip” is the NAT address of the DXi at the at the local customer site. Also in the example above, “dataip” is the actual IP address of the source DXi system at the local customer site.
Contents of /data/hurricane/conf/NewReplication.conf below:
<?xml version="1.0"?>
<root>
<Configured_Targets>
<Targets>
<Target>
<Name>13.40.6.54</Name>
<ReplicationIP>13.40.6.54</ReplicationIP>
<DataIPs>
<DataIP>10.70.208.127</DataIP>
</DataIPs>
</Target>
</Targets>
</Configured_Targets>
</root>
NewReplication.conf (END)
When the delete opduptranslate command is executed, the /data/hurricane/conf/NewReplication.conf file will remain on the target DXi system in the cloud, but it will contain no IP data:
<?xml version="1.0"?>
<root>
<Configured_Targets>
<Targets></Targets>
</Configured_Targets>
</root>
NewReplication.conf (END)
Example #2: DXi6702 with 2.1.1 Software
The NewReplication.conf gets added as described previously in Example #1. However, when the delete command is executed, the NewReplication.conf remains and holds the NAT address. In this example, only the data IP is removed.
<?xml version="1.0"?>
<root>
<Configured_Targets>
<Targets>
<Target>
<Name>13.40.6.54</Name>
<ReplicationIP>13.40.6.54</ReplicationIP>
<DataIPs></DataIPs>
</Target>
</Targets>
</Configured_Targets>
</root>
This page was generated by the BrainKeeper Enterprise Wiki, © 2018 |