# sf-r630

SureFire-client physical server at the Anaheim colo — Dell PowerEdge
R630. **PFI-managed** under the hosting agreement (hardware + OS ops).

**This directory documents the hardware / iDRAC side only.** The OS
running on this box is tracked separately as
[`servers/sfsrv-ana/`](../sfsrv-ana/README.md) — Proxmox VE at
`10.250.250.115`. Refer to that for OS-level snapshots, SSH access,
and backup coverage.

## Client context

- **Client:** SureFire
- **PFI role:** full-service managed host (iDRAC + Proxmox)

## Network

- **iDRAC BMC:** `10.250.250.110` (dedicated OOB management NIC)
  - Web UI: <https://10.250.250.110/> (currently 404s; use the
    vSphere-style Redfish API or racadm from iDRAC shell for
    out-of-band ops)
  - Homepage monitors this via ICMP ping rather than HTTP
- **OS-side (Proxmox VE):** see `servers/sfsrv-ana/` — `10.250.250.115`

## Hardware

- **Type:** Physical Dell PowerEdge R630, 2U
- **Site:** Anaheim (PFI colo)
- Detailed hardware / CPU / RAM / disk data comes from `sfsrv-ana`'s
  `system-details.txt` (the OS can read all of this via `dmidecode`,
  `lscpu`, etc. — no need to duplicate here).

## Why this dir exists separately from sfsrv-ana

- The iDRAC is a distinct management surface with its own credentials,
  protocol stack, and firmware lifecycle. Power events, BIOS updates,
  and console access live here.
- Inventory audits that track *hardware* (for hosting-agreement
  billing, depreciation, etc.) should see the physical box as its own
  entry independent of whatever OS happens to be running on it.

## Refresh state

**No `ssh-target` and no `system-details.txt`** — iDRAC doesn't expose
a useful sshd for our inspect scripts. Host metadata comes from
`sfsrv-ana`'s snapshot instead.

## Discovered via

`scripts/discover-fortigate.sh 10.250.250.1` on 2026-04-21 — iDRAC's
DHCP lease on the management interface (MAC `74:e6:e2:fe:2c:7c`,
VCI `iDRAC`). Matched to sfsrv-ana via iDRAC Service Tag / physical
co-location on 2026-04-23.