Skip to content

Diagnostics Toolkit

VergeOS embeds diagnostic tools directly into every major subsystem. Rather than SSH-ing into individual nodes or installing third-party utilities, administrators run diagnostics from the VergeOS UI — each scoped to the component being investigated.

Every diagnostic interface follows the same pattern:

  1. Navigate to the component (network, node, NAS, or vSAN)
  2. Click Diagnostics in the left menu
  3. Select a command from the Query dropdown
  4. Configure parameters on the right
  5. Click Send → to execute

Access: Networks → [Select Network] → Diagnostics

Network diagnostics run per-network — you select the specific network you want to troubleshoot, and all commands execute within that network’s context. This is critical because VergeOS networks are isolated by design.

CommandCLI EquivalentPurpose
Pingping -c [COUNT] [DEST]Basic ICMP connectivity test
Trace Routetraceroute / mtrMap the network path to a destination
ARP Scannmap -sn [RANGE]Discover active devices on the network
ARP Tablearp -aView current IP-to-MAC mappings
TCP Connection Testtelnet / nc -zv [HOST] [PORT]Verify a specific TCP port is reachable
What’s My IPcurl ifconfig.meCheck the network’s external IP (NAT verification)
CommandCLI EquivalentPurpose
DNS Lookupnslookup / dig [HOST] [TYPE]Query A, AAAA, MX, NS, PTR records
CommandCLI EquivalentPurpose
Show Firewall Rulesnft list rulesetDisplay the full nftables ruleset
Trace/Debug Firewall Rulesnft add rule ... logEnable per-rule logging for debugging
NMAPnmap [OPTIONS] [TARGET]Port scanning and service discovery
CommandCLI EquivalentPurpose
TCP Dumptcpdump -i [IFACE] [FILTER]Packet capture with BPF filtering
Top Network Usageiftop / nethogsReal-time bandwidth consumers
Top CPU Usagetop -o %CPUProcesses consuming the most CPU
CommandCLI EquivalentPurpose
DHCP Release/Renewdhclient -r && dhclientForce DHCP lease refresh (DHCP client networks)
IPsecipsec [COMMAND]Monitor and control IPsec VPN tunnels
FRRouting BGP/OSPFvtysh -c "show ip bgp"Dynamic routing protocol status
Logsjournalctl -u [SERVICE]Network container system logs

Access: Infrastructure → Nodes → [Select Node] → Diagnostics

Node diagnostics provide hardware-level visibility into individual physical servers. These tools interact directly with the server’s BMC, drives, and physical network interfaces.

These commands use ipmitool to communicate with the server’s Baseboard Management Controller — the out-of-band management interface (iDRAC on Dell, iLO on HPE, etc.).

CommandCLI EquivalentPurpose
IPMI BMC Infoipmitool bmc infoBMC firmware and configuration
IPMI Chassis Statusipmitool chassis statusPower state, intrusion detection
IPMI FRU Infoipmitool fru printField Replaceable Unit identification
IPMI LAN Infoipmitool lan printBMC network configuration
IPMI MC Resetipmitool mc reset coldReset a non-responsive BMC
IPMI Sensorsipmitool sensor listTemperature, voltage, fan readings
IPMI Sensor Data Repositoryipmitool sdr listFull sensor data repository
IPMI System Event Logsipmitool sel listHardware event history (SEL)
CommandCLI EquivalentPurpose
S.M.A.R.T. Informationsmartctl -a [DRIVE]Drive health attributes, wear, temperature
S.M.A.R.T. Diagnostic Testsmartctl -t [TYPE] [DRIVE]Run short, long, or conveyance tests
Show Block Deviceslsblk / fdisk -lList all block devices on the node
LED Control (Drive)ledctl locate=[DRIVE]Blink a drive LED for physical identification
RAS Queryras-mc-ctl --summaryMemory ECC error reporting
CommandCLI EquivalentPurpose
Ethernet Toolethtool [IFACE]Link speed, duplex, driver info
Fabric Configurationverge fabric showCore fabric status for this node
Network Bondingcat /proc/net/bonding/[BOND]Bond interface health and active slave
Bridge Addressesbrctl showmacs [BRIDGE]Virtual switch MAC address table
ARP Scan / ARP Tablenmap -sn / arp -aNode-level network discovery
Ping / Trace Routeping / tracerouteBasic connectivity from node context
CommandCLI EquivalentPurpose
DMI TabledmidecodeFull hardware inventory (CPU, RAM, serial numbers)
Logsjournalctl -n 100 / dmesgSystem and kernel logs
OpenSSL Speedopenssl speedCPU crypto performance benchmark
Clear Persistent Storagesync && echo 3 > /proc/sys/vm/drop_cachesClear filesystem caches (support use only)

Access: System → vSAN Diagnostics

vSAN diagnostics operate at the system level using vcmd — the VergeOS vSAN command-line interface. These commands provide deep visibility into the distributed storage engine.

CommandCLI EquivalentPurpose
Get Tier Statusvcmd tier statusHealth, redundancy, and capacity per tier
Get Cluster Ratesvcmd cluster ratesRead/write throughput across the cluster
Get Cluster Usagevcmd cluster usageOverall storage utilization statistics
Get Device Listvcmd devices listAll storage devices in the vSAN pool
Get Device Statusvcmd device status [ID]Individual device health and error counts
Get Device Usagevcmd device usage [ID]Per-device capacity and I/O metrics
Get Repair Statusvcmd repair statusActive rebuild/repair progress
Get Journal Statusvcmd journal statusWrite-ahead journal health
Get Integ Check Statusvcmd integcheck statusData integrity verification progress
Get Cache Infovcmd cache infoCache hit/miss ratios and memory usage
Get File Statusvcmd file status [PATH]Replication and integrity for a specific file
Get Top Usage Ratesvcmd usage top-ratesIdentify top storage consumers
Get Running Confvcmd config showCurrent vSAN configuration parameters
Get Sync Listvcmd sync listActive synchronization operations
Get Node Listvcmd nodes listAll nodes participating in the vSAN
Integ Checkvcmd integcheck startInitiate a full integrity check
Summarize Disk Usagevcmd usage summarizeCluster-wide disk usage summary

A structured approach to investigating storage issues:

  • working = false on any tier → Critical — tier is not operational
  • redundant = false → Degraded state, no fault tolerance
  • bad_drives > 0 → Drive failure detected, auto-repair in progress
  • Repair status all zeros → No active repairs (healthy state)
  • Write throttle active → Storage capacity approaching limits (>91% triggers throttling)
UtilizationBehavior
< 91%Normal operation, no throttling
91–95%Low-space throttling begins (10ms latency added)
96%+Critical throttling (50ms latency added)
> 96%Severe performance degradation

Access: NAS → [Select NAS Service] → Diagnostics

NAS diagnostics are per-NAS-service — each NAS instance has its own diagnostic interface. These tools focus on file-sharing protocols (SMB/CIFS, NFS) and authentication.

CommandCLI EquivalentPurpose
SambasmbstatusActive SMB connections and locked files
testparmValidate Samba configuration syntax
smbclient -L localhostList available SMB shares
CommandCLI EquivalentPurpose
NFSexportfs -vCurrent NFS export configuration
rpcinfo -pRPC service registration status
showmount -eExported filesystems visible to clients
CommandCLI EquivalentPurpose
Winbindwbinfo -tTest domain trust relationship
wbinfo -uList domain users
wbinfo -gList domain groups

NAS diagnostics also include the standard connectivity tools: Ping, Trace Route, ARP Scan/Table, TCP Dump, TCP Connection Test, DNS Lookup, NTP Query, Top CPU Usage, Top Network Usage, and Logs.

CommandCLI EquivalentPurpose
Usersgetent passwd / whoSystem user accounts
Groupsgetent groupSystem groups and membership
Date/Timedate / timedatectlTime sync (critical for Kerberos/AD)
Servicessystemctl list-units --type=serviceAll running services

When investigating an issue, follow a structured escalation path from component-specific diagnostics to system-wide analysis:

  1. Start simple — Ping before packet capture. Check tier status before integrity checks.
  2. Scope correctly — Select the right network, node, or NAS service before running diagnostics. Running commands in the wrong context produces misleading results.
  3. Document as you go — Use “Show Command” to capture exact commands. Copy output before moving to the next test.
  4. Consider performance impact — TCP Dump, NMAP scans, and integrity checks can affect production performance. Schedule intensive diagnostics during maintenance windows.
  5. Check logs last — Logs provide context but can be overwhelming. Use targeted diagnostics first, then correlate with log entries.

For issues that span multiple components or require support escalation, VergeOS can generate a comprehensive diagnostic bundle:

  • Access: System → System Diagnostics
  • Output: [SYSTEMNAME]_diags_[YYYYMMDD]_[HHMMSS].tar.gz
  • Contents: vSAN status files, SMART reports, network configuration, IPMI data, system logs, and kernel logs — organized per-node
  • Retention: System logs are retained for 45 days before automatic deletion

Network Diagnostics

Use when: VM can’t reach the internet, DNS not resolving, firewall blocking traffic, DHCP not assigning IPs, VPN tunnel down

Access: Networks → [Network] → Diagnostics

Node Diagnostics

Use when: Hardware alerts, drive failures, temperature warnings, NIC link issues, IPMI unresponsive, fabric connectivity problems

Access: Infrastructure → Nodes → [Node] → Diagnostics

vSAN Diagnostics

Use when: Storage performance degraded, tier unhealthy, capacity warnings, repair stuck, data integrity concerns

Access: System → vSAN Diagnostics

NAS Diagnostics

Use when: SMB shares inaccessible, NFS mount failures, AD authentication broken, file permission denied, slow CIFS performance

Access: NAS → [NAS Service] → Diagnostics