# VMID 2400-2402 Status

**Date**: 2026-01-05  
**Status**: VMIDs Not Found on r630-01

---

## Current Situation

VMIDs 2400-2402 are not found on Proxmox node `r630-01`. The configuration files don't exist:
- `nodes/r630-01/qemu-server/2400.conf` - Not found
- `nodes/r630-01/qemu-server/2401.conf` - Not found  
- `nodes/r630-01/qemu-server/2402.conf` - Not found

---

## Possible Scenarios

### Scenario 1: VMs Exist on Different Node
The VMIDs may exist on a different Proxmox node. Check:
```bash
# Check all nodes
ssh root@192.168.11.11 "pvesh get /nodes"
```

### Scenario 2: VMs Need to be Created
The VMIDs may need to be provisioned first. They should be:
- **Type**: QEMU/KVM VMs (based on IP allocation)
- **IPs**: 192.168.11.240, 192.168.11.241, 192.168.11.242
- **Purpose**: RPC Translator instances

### Scenario 3: VMs Exist but Not Registered
The VMs may exist but aren't properly registered in Proxmox.

---

## Network Connectivity

The IPs are allocated:
- 192.168.11.240 (VMID 2400)
- 192.168.11.241 (VMID 2401)
- 192.168.11.242 (VMID 2402)

Check if these IPs are reachable:
```bash
ping -c 1 192.168.11.240
ping -c 1 192.168.11.241
ping -c 1 192.168.11.242
```

---

## Next Steps

1. **Verify VM existence**: Check all Proxmox nodes
2. **If VMs don't exist**: Create them according to the deployment plan
3. **If VMs exist elsewhere**: Update deployment scripts with correct node
4. **If IPs are reachable**: VMs may exist but not be registered in Proxmox

---

## Password Setup (Once VMs are Located)

Password has been generated: `feeO4j9QwpuMgb6dMHi4T2etn`

Once VMs are accessible:
1. Set root password on each VM
2. Configure SSH keys
3. Proceed with deployment
