# Cluster Status Check: sankofa-sfv-01

**Date**: 2024-12-19  
**Cluster Name**: sankofa-sfv-01

## API Check Results

### Status
⚠️ **API-based cluster checks are limited due to permission constraints**

The current API tokens do not have `Sys.Audit` permission, which is required to access cluster status endpoints.

### What We Can Verify

✅ **Both instances are accessible**:
- ML110-01 (192.168.11.10): ✅ API accessible
- R630-01 (192.168.11.11): ✅ API accessible

✅ **Both instances are online**:
- Both nodes respond to API requests
- Version information retrievable

### What We Cannot Verify via API

❌ **Cluster membership** (requires Sys.Audit permission)
❌ **Cluster configuration** (requires Sys.Audit permission)
❌ **Cluster node list** (requires Sys.Audit permission)

## Alternative Methods to Check Cluster

### Method 1: Proxmox Web UI (Recommended)

1. **Log in to ML110-01**: https://ml110-01.sankofa.nexus:8006
2. Go to: **Datacenter** → **Cluster**
3. Check if cluster name "sankofa-sfv-01" is displayed
4. Verify both nodes (ML110-01 and R630-01) are listed

5. **Log in to R630-01**: https://r630-01.sankofa.nexus:8006
6. Go to: **Datacenter** → **Cluster**
7. Verify same cluster name and both nodes visible

### Method 2: SSH Commands

If SSH access is available:

```bash
# On ML110-01
ssh root@192.168.11.10
pvecm status
pvecm nodes

# On R630-01
ssh root@192.168.11.11
pvecm status
pvecm nodes
```

Expected output if cluster exists:
```
Cluster information
-------------------
Cluster name: sankofa-sfv-01
Cluster version: 2
Nodes: 2
```

### Method 3: Check Corosync Configuration

```bash
# On either node
cat /etc/pve/corosync.conf
```

Look for:
- Cluster name matching "sankofa-sfv-01"
- Both node IPs listed
- Node IDs assigned

## Expected Cluster Configuration

If cluster "sankofa-sfv-01" exists:

- **Cluster Name**: sankofa-sfv-01
- **Node 1**: ML110-01 (192.168.11.10)
- **Node 2**: R630-01 (192.168.11.11)
- **Quorum**: Should be configured for 2-node cluster

## Next Steps

1. **Verify via Web UI** (easiest method)
2. **If cluster exists**: Update documentation and task list
3. **If cluster doesn't exist**: Follow cluster creation guide in `CLUSTER_SETUP.md`

## Related Documentation

- [Cluster Setup Guide](./CLUSTER_SETUP.md)
- [Task List](./TASK_LIST.md)
- [Connection Status Report](./CONNECTION_STATUS_REPORT.md)

