# sfsrv-ana

SureFire-client Proxmox hypervisor at the Anaheim colo. Client-owned
equipment but **PFI-managed** under the hosting agreement — we have SSH
and are responsible for operations.

## Client context

- **Client:** SureFire (SF prefix is SF-client hosts)
- **PFI role:** full-service managed host (rack, power, network, OS
  ops, backups)

## Network

- **LAN IP:** 10.250.250.115
- **FQDN:** not yet in DNS / `/etc/hosts` — add a line to the
  workstation's hosts file to make short-name resolution work:
  ```
  10.250.250.115  sfsrv-ana
  ```
- **Web UI:** https://10.250.250.115:8006 (Proxmox VE)
- **SSH:** `root@10.250.250.115` (key auth — same pattern as other PVE nodes)

## Infrastructure

- **Type:** Proxmox VE hypervisor (bare metal)
- **Site:** Anaheim (PFI colo)

Hosts SureFire's VMs, including:
- `sf-ana-container` (10.250.150.100) on the dedicated SF container subnet

## Backup coverage

- **VM-image:** status unknown — probe with
  `scripts/refresh-proxmox-info.sh sfsrv-ana` once SSH is verified.
  If no vzdump jobs are configured, set them up the same as pfi-pve
  (daily 01:00 into a network target).
- **File-level restic:** not yet configured.

This is on the open work list — once we've validated SSH + refreshed
the Proxmox snapshot, add a `configs/restic/sfsrv-ana/` profile if
it's running hosted workloads whose state we care about beyond the
VM-image layer.

## Refresh state

```bash
scripts/refresh-proxmox-info.sh sfsrv-ana
```

## Discovered via

`scripts/discover-fortigate.sh 10.250.250.1` on 2026-04-21 (MAC
`44:a8:42:33:d9:c3`).