host007
host007 is a Proxmox VE hypervisor in the klynge001 cluster. This page is an emergency access runbook, not the inventory source of truth. Keep inventory-style details in NetBox.
Emergency access
SSH: root@host007.hackeriet.no
-
Connectivity: use the Hackeriet internal network or VPN before assuming the host is down.
Credentials: check the Hackeriet password store for host007 entries. Do not copy secrets into the wiki.
If SSH does not answer, use NetBox to find the physical location and switch port before changing anything on guests.
Orientation
NetBox device: host007
Role: Hypervisor
Cluster: klynge001
OS observed: Debian GNU/Linux 12 (bookworm)
Kernel observed: 6.8.12-9-pve
Proxmox VE observed: pve-manager/8.3.5
Hardware observed: ASUS MINIPC PN62
Serial observed: L3MRAC001971H8A
Cluster status observed while documenting:
Network
Management IPv4: 10.10.50.27/24
Management bridge observed: vmbr50
Physical uplink observed: eno1
Physical MAC observed: a8:5e:45:bc:6a:ee
Physical link observed: 1 Gbps, MTU 1500
NetBox cable: host007
LAN to hackeriet-sw GigabitEthernet0/41
Guests
Guests observed on host007 while documenting:
100 jakkn2
102 fr30n
105 blade
107 bergh
117 haus-forum
119 haus
120 hyperboria
121 nux
123 chat
601 idp1
Do not touch guest VMs unless the incident requires it. This page is for host access and orientation only.
Storage and backups
Storage looked healthy when documented:
Root filesystem: about 94G total, about 74G free.
/var/lib/vz/dump: separate filesystem, about 503G total, about 331G free.
Proxmox storage observed: local about 17% used, local-lvm about 27% used.
Host-level backup jobs are managed from Proxmox/cluster configuration. Do not confuse guest backup placement with unrelated service backups.
Known issues
Useful checks
Run these on host007 when investigating host-level incidents:
hostname -f
pveversion
pvecm status
systemctl –failed
ip -br addr
df -h
pvesm status
qm list