Skip to main content
BlueXP setup and administration

Maintain the Connector VM and operating system

Contributors netapp-bcammett
PDFs

Maintaining the operating system on the Connector host is your responsibility. For example, you should apply security updates to the operating system on the Connector host by following your company's standard procedures for operating system distribution.

Tip If you have an existing Connector, you should be aware of changes to supported Linux operating systems.

Operating system patches and the Connector

You don't need to stop any services on the Connector host when applying OS security patches.

VM or instance type

If you created a Connector directly from BlueXP, BlueXP deployed a virtual machine instance in your cloud provider using a default configuration. After you create the Connector, you should not change to a smaller VM instance that has less CPU or RAM.

The CPU and RAM requirements are as follows:

CPU

8 cores or 8 vCPUs

RAM

32 GB

Learn about the default configuration for the Connector.

Stopping the starting the Connector VM

If you need to stop and then start the Connector VM, then you should do so from your cloud provider's console or by using the standard procedures for on-premises management.

Be aware that the Connector must be operational at all times.

Connect to the Linux VM

If you need to connect to the Linux VM that the Connector runs on, you can do so by using the connectivity options available from your cloud provider.

AWS

When you created the Connector instance in AWS, you provided an AWS access key and secret key. You can use this key pair to SSH to the instance. The user name for the EC2 Linux instance is ubuntu (for Connectors created prior to May 2023, the user name was ec2-user).

AWS Docs: Connect to your Linux instance

Azure

When you created the Connector VM in Azure, you specified a user name and chose to authenticate with a password or SSH public key. Use the authentication method that you chose to connect to the VM.

Azure Docs: SSH into your VM

Google Cloud

You can't specify an authentication method when you create a Connector in Google Cloud. However, you can connect to the Linux VM instance using the Google Cloud Console or Google Cloud CLI (gcloud).

Google Cloud Docs: Connect to Linux VMs

Change the IP address for a Connector

If it's required for your business, you can change the internal IP address and public IP address of the Connector instance that is automatically assigned by your cloud provider.

Steps

  1. Follow the instructions from your cloud provider to change the local IP address or public IP address (or both) for the Connector instance.

  2. If you changed the public IP address and you need to connect to the local user interface running on the Connector, restart the Connector instance to register the new IP address with BlueXP.

  3. If you changed the private IP address, update the backup location for Cloud Volumes ONTAP configuration files so that the backups are being sent to the new private IP address on the Connector.

    You'll need to update the backup location for each Cloud Volumes ONTAP system.

    1. From the Cloud Volumes ONTAP CLI, set the privilege level to advanced:

      set -privilege advanced

    2. Run the following command to display the current backup target:

      system configuration backup settings show

    3. Run the following command to update the IP address for the backup target:

      system configuration backup settings modify -destination <target-location>

Edit a Connector's URIs

Add and remove the Uniform Resource Identifier (URI) for a Connector.

Steps

  1. Select the Connector drop-down from the BlueXP header.

  2. Select Manage Connectors.

  3. Select the action menu for a Connector and select Edit URIs.

  4. Add and remove URIs and then select Apply.