Upgrade an Airgap Server Using a New Airgap Deployment

You can upgrade an existing airgap server by deploying a new airgap server in an internet-accessible environment and then replacing the existing airgap server with the new airgap server. You can use this procedure to upgrade the airgap server from Telco Cloud Automation 2.1 to 2.3 and from 2.2 to 2.3.

Prerequisites

Back up the certificates from the existing airgap server to your desktop or jump box.

Procedure

Deploy and configure a new Photon OS VM as the new Airgap server in an internet-accessible environment. For instructions, see Configuring an Airgap Repository.
Download the Telco Cloud Automation 2.3 airgap tar file from the VMware Downloads page.

VMware-Telco-Cloud-Automation-airgap-files- 2.3.0-[build_number].tar.gz

Extract the downloaded tar file to the /root/ directory.

root@photon-machine [ ~/root ]# tar -xvf VMware-Telco-Cloud-Automation-airgap-files-2.3.0-[build_number].tar.gz

Copy the setup-user-inputs.yml file as user-inputs.yml file.

#cd /root/airgap/scripts/vars/
#cp setup-user-inputs.yml user-inputs.yml

Modify the product and other parameters such as FQDN and certs in the user-inputs.yml file. For more information about modifying other parameters, see Set Up an Airgap Server.
- If you are upgrading the airgap server from Telco Cloud Automation 2.2 to 2.3, use the following parameter values.
- ```
products:
  - name: "tca"
    versions: "2.2.0-"
server_fqdn: <PhotonOS VM FQDN>
```
- If you are upgrading the airgap server from Telco Cloud Automation 2.1 to 2.3, use the following parameter values.
- ```
products:
  - name: "tca"
    versions: "2.1.0-"
server_fqdn: <PhotonOS VM FQDN>
```

Set up the new airgap server.

root@photon-machine [ ~/airgap ]# scripts/bin/run.sh setup

Export the new airgap server as an OVF from the internet-accessible environment and deploy the new airgap server as a VM in the air-gapped environment. For more information, see Export and Transfer Airgap Server OVA to Internet-Restricted Environment.
Copy the certificates that you backed up from the existing airgap server to the /root/certs/ directory on the new airgap server.

Copy the deploy-user-inputs.yml file as user-inputs.yml file.

#cd /root/airgap/scripts/vars/
#cp deploy-user-inputs.yml user-inputs.yml

Modify the FQDN, IPs, and certificate paths in the user-inputs.yml file.

Caution:
Use the same FQDN, IPs, and certificates that you used in the existing airgap server.
Power OFF the existing airgap server.
Configure the new airgap server.
```
./run.sh deploy
```

What to do next

Validate the Airgap Server setup.