# Asama AI Deployment Guide

Version: v1.4 - Last updated October 2026

From install to insights in under 30 minutes:

- *Provision and configure the Collector VM(s).*
- *Roll out the Host Agents across all your devices.*
- *Start seeing insights in your account.*

## Before you start

- Console credentials received (login for console.asama.cloud, sent to you by the Asama team)
- Collector VM provisioned to spec (minimum 2 cores, 8 GB RAM, 50 GB SSD per VM)
- Firewall rules opened (every flow in the network access table)
- Credentials store ready (a secrets manager such as HashiCorp Vault; not required for POC/LAB)

## Deployment architecture

- Collector VM(s) run in the customer environment.
- Collector -> console.asama.cloud (Asama Console): TCP 443 (HTTPS)
- Collector -> Server BMCs: TCP 443 (Redfish)
- Collector -> Switch/PDU management IPs: UDP 161 (SNMP)
- Collector -> secrets manager (e.g. HashiCorp Vault): TCP 8200
- Host Agents (running on each monitored server) -> Collector: TCP 2379 (etcd) and TCP 4317 (OTLP)

## 1. Deployment requirements

### Collector VM(s)

- Single collector (1 VM): one VM or server with minimum 2 cores, 8 GB RAM, 50 GB SSD.
- High availability (3 VMs): for high availability, three VMs with the same minimum spec on each VM are recommended.
- SSH access for Asama AI engineers to this VM is recommended, at least for the initial deployment.

### BMC credentials store

- Production: Industry best practices recommend storing BMC credentials in a centralized secrets manager (e.g., HashiCorp Vault) to ensure encryption at rest and strict access control.
- POC/LAB setup: for a POC/LAB setup, the collector may read credentials from a config file instead of a secrets manager to make the setup faster.

### Network access required

Access from Collector VM to:

| Destination | Port | Protocol |
|---|---|---|
| console.asama.cloud | 443 | TCP/HTTPS |
| Server BMC IPs | 443 | TCP/Redfish |
| Switch/PDU Mgmt IP | 161 | UDP/SNMP |
| Secrets manager (e.g. HashiCorp Vault) | 8200 | TCP |

Access from Host Agents to:

| Destination | Port | Protocol |
|---|---|---|
| Collector VM | 2379 and 4317 | TCP/etcd and TCP/OTLP |

## 2. Installation steps

Prerequisite (requires help from the Asama team): get the credentials to access console.asama.cloud for initial setup and thereafter. It will be sent to you by Asama's team.

### Step 1: Set up the Collector VM(s)

Run on the collector VM:

```bash
bash <(curl -sSL https://console.asama.cloud/public/collector-setup.sh)
```

Enter the username and secret provided by the Asama team when prompted.

### Step 2: Deploy Host Agents on all servers to be monitored

Run on each server:

```bash
bash <(curl -sSL https://console.asama.cloud/public/host-agent-install.sh)
```

Enter the username and secret provided by the Asama team when prompted. Enter the collector VM details when prompted.

### Reviewing the scripts before running them

Prefer to review scripts before running them? Download with `curl -sSLO <url>`, inspect, then run locally with `bash <file>`.

## Deployment FAQ

### How do I get console credentials?

Console credentials are sent to you by the Asama team.

### Where credentials are stored after install?

BMC Credentials and other secrets are stored in a secret management store like HashiCorp Vault in your infrastructure. Any other standard secrets management tool you use internally can also be used.

### What data is sent to console.asama.cloud?

Telemetry (metrics and logs) from the BMC, hardware components like CPU, GPU, DIMM etc., the operating system and the kernel is sent to the Asama console.

### How is my data secured?

All traffic is encrypted in transit, both from the Host Agents to the Collector and from the Collector to console.asama.cloud. The Collector only makes outbound connections, so no inbound access to your network is needed. Asama collects hardware and system telemetry only, and no personal data is collected. For details, visit the [Asama Trust Center](https://trust.asama.ai/).

### How much time does it take to complete the process?

For 1,000-1,500 devices, it takes less than 30 minutes to provision and configure the Collector VM(s), roll out the Host Agents across all your devices, and start seeing insights in your account.

### Is high availability setup needed?

Yes. For uninterrupted reliability of your infrastructure, it's advisable to have a high-availability setup for Asama.

## Need help?

Contact the Asama team at contactus@asama.ai.