Converting a Single Cluster Running GNS to be a GNS Client Cluster

Because it is necessary to stay connected to the current GNS during this conversion process, the procedure is more involved than that of converting a single cluster to a server cluster.

Run the following command as root in the server cluster to export the GNS client information to a file:
```
# srvctl export gns -clientdata path_to_client_data_file
```
You must specify the fully-qualified path to the file.
Stop GNS on the cluster you want to convert to a client cluster.
```
# srvctl stop gns
```
Note:

While the conversion is in progress, name resolution using GNS will be unavailable.
Run the following command as root in the server cluster to export the GNS instance:
```
# srvctl export gns -instance path_to_file
```
You must specify the fully-qualified path to the file.
Run the following command as root in the server cluster to import the GNS instance file:
```
# srvctl import gns -instance path_to_file
```
You must specify the fully-qualified path to the file.
Run the following command as root on the node where you imported the GNS instance file to start the GNS instance:
```
# srvctl start gns
```
By not specifying the name of the node on which you want to start the GNS instance, the instance will start on a random node.
Remove GNS from the GNS client cluster using the following command:
```
# srvctl remove gns
```
Make the former cluster a client cluster, as follows:
```
# srvctl add gns -clientdata path_to_client_data_file
```
Note:

You must copy the file containing the GNS data from the server cluster to a node in the cluster where you run this command.
Modify the SCAN in the GNS client cluster to use the GNS subdomain qualified with the client cluster name, as follows:
```
srvctl modify scan -scanname scan_name.gns_domain
```
In the preceding command, gns_domain is in the form client clustername.server GNS subdomain