Skip to main content
NetApp Console setup and administration

Choose a Console agent deployment method

Contributors netapp-tonias
PDFs

Deploy a Console agent using the NetApp Console, your cloud provider's marketplace, or by manually installing software on a Linux host. Your deployment method determines how you maintain the agent host and differs depending on which NetApp Console deployment mode you are using.

For cloud deployments, you can deploy an agent in Amazon Web Services (AWS), Microsoft Azure, or Google Cloud.

Deploy from the NetApp Console

NetApp recommends deploying from the NetApp Console when you use standard mode. The NetApp Console guides you through networking and permissions setup, then automatically launches the VM or instance in your cloud provider. The Console guides you through networking and permissions setup, then launches the VM or instance in your cloud provider automatically.

Choose this method when:

  • You are deploying in a standard cloud environment with outbound internet access.

  • You want the fastest path to a running agent with the least manual setup.

Advantages Disadvantages

  • Guided setup — the Console handles VM creation, software installation, and initial registration in a single workflow

  • Automatically applies the correct VM image and configuration

  • Fewest manual steps of any cloud deployment method

  • Not available for on-premises, restricted mode or air-gapped environments

Deploy a Console agent in AWS from the Console
Deploy a Console agent in Azure from the Console
Deploy a Console agent in Google Cloud from the Console

Deploy from a cloud provider marketplace

Deploying from the AWS Marketplace or Azure Marketplace initiates the agent installation directly from the marketplace, not from the NetApp Console.

Note A marketplace-equivalent option is available in Google Cloud using Google Cloud tools (gcloud CLI or Google Cloud console) rather than a traditional marketplace listing.

Choose this method when:

  • Your organization requires all cloud software to be procured through the marketplace.

  • You prefer to initiate deployments from your cloud provider's interface rather than the NetApp Console.

Advantages Disadvantages

  • Familiar deployment interface for teams already working in the cloud provider's console

  • Deployment is initiated outside the NetApp Console, so the guided workflow is not available

Deploy a Console agent in AWS from the marketplace
Deploy a Console agent in Azure from the marketplace
Deploy a Console agent in Google Cloud using Google Cloud tools

Manually install on a Linux host in the cloud

Manual installation lets you install the Console agent software directly on a Linux host that you provide and manage in AWS, Azure, Google Cloud or on-premises.

Choose this method when:

  • You need to deploy in a restricted mode or private mode environment without outbound internet access.

  • Your organization requires all software to be installed on pre-approved, internally managed hosts.

Advantages Disadvantages

  • Supports environments with limited outbound internet access (restricted mode or private mode)

  • Upgrades are automatically handled when the Console agent has internet access

  • Most steps of any deployment method. You must prepare the host, install Podman or Docker, configure networking, install the software, and provide permissions manually

  • * Deployment is initiated outside the NetApp Console, so the guided workflow is not available

Manually install a Console agent in AWS
Manually install a Console agent in Azure
Manually install a Console agent in Google Cloud

Manually install on-premises using VCenter (OVA)

If you use VMware VCenter, you can deploy the Console agent by importing an OVA (Open Virtual Appliance) file. The OVA is a pre-configured VM image you deploy with the vSphere client, without installing Linux or configuring a container runtime.

Choose this method when:

  • You are deploying on-premises in a VMware environment.

  • You want a simpler on-premises installation that requires less maintenance and Linux setup.

Note You cannot manage Google Cloud resources from an on-premises Console agent. To manage Google Cloud resources, install the agent in Google Cloud.
Advantages Disadvantages

  • Simpler on-premises installation with no Linux or container runtime setup required

  • On-premises only; not available for cloud deployments

  • Includes a menu-driven maintenance console for agent maintenance tasks

  • Familiar deployment workflow for VMware administrators

  • * Pre-configured VM image helps prevent mistakes and makes maintenance easier

  • Requires VCenter; cannot be installed directly on a bare ESXi host

Deploy on-premises using VCenter

Manually install on-premises (without VCenter)

You can manually install the Console agent on any on-premises Linux host. You must set up the Linux host and container runtime (Docker or Podman), then install the Console agent.

Choose this method when:

  • You are deploying on-premises and do not have a VMware VCenter environment.

  • You are comfortable with Linux administration and want to manage the underlying host yourself.

  • You want to control when the Console agent is upgraded.

Advantages Disadvantages

  • Works on any Linux-compatible on-premises hardware or VM platform — no VMware required

  • Supports private mode (air-gapped) deployments with no outbound internet access

  • You need to know how to use Linux and set up Docker or Podman yourself

  • You are responsible for manually applying upgrades to the Console agent when new versions are released

Manually install on-premises