How to use HiveOS for multi-rig management? (Platform Tutorial)

Dashboard Navigation and Farm Setup

1. After logging into hiveon.com, users land on the dashboard displaying real-time metrics across all registered rigs.

2. A new farm must be created before adding any rig—this is done by clicking “Add Farm” and assigning a descriptive name such as “AMD-Rig-Cluster” or “NVIDIA-Ethash-Farm”.

3. Each farm supports custom tags, location labels, and alert thresholds for temperature, fan speed, and hash rate deviation.

4. The dashboard auto-refreshes every 15 seconds; manual refresh is available via the circular arrow icon in the top-right corner.

5. Rig status indicators use color coding: green for normal operation, yellow for warning (e.g., GPU temp >78°C), and red for offline or critical failure.

Rig Registration and Firmware Synchronization

1. To register a rig, users generate a unique activation code from the farm page and input it during HiveOS boot via console or IPMI interface.

2. HiveOS automatically detects GPU models, VRAM capacity, and PCIe lane configuration upon first boot and reports them to the dashboard.

3. Firmware updates are pushed centrally—selecting multiple rigs and clicking “Update Firmware” triggers simultaneous OTA deployment without manual SSH access.

4. Custom BIOS profiles stored on the HiveOS server can be applied in bulk, including memory timings, power limits, and voltage offsets tailored per GPU generation.

5. Failed firmware deployments are logged with timestamps and error codes, enabling rapid root-cause analysis using the built-in diagnostic viewer.

Algorithm Switching and Pool Failover Configuration

1. Users define primary and fallback mining algorithms per rig group—for example, switching from ETHASH to ETCHASH when Ethereum PoW difficulty spikes above threshold.

2. Pool failover logic is configured through JSON-based rules: if connection latency exceeds 500ms for 3 consecutive checks, HiveOS redirects all shares to the secondary pool instantly.

3. Each pool entry includes authentication tokens, worker naming templates, and share submission retry counts before triggering the next fallback level.

4. Algorithm benchmarks run automatically during idle periods, comparing hashrate stability and power efficiency across ETHASH, KAWPOW, AUTOLYKOS, and GRIN-C31.

5. Benchmark results are retained for 90 days and accessible via time-range filters, supporting historical comparison of driver versions and overclock profiles.

Remote Console and Diagnostic Tools

1. The web-based terminal provides full bash access to each rig’s underlying Linux environment, with command history persistence across sessions.

2. Real-time sensor monitoring displays per-GPU core clocks, memory bandwidth utilization, junction temperature, and PCIe RX/TX throughput in graph format.

3. Log streaming includes kernel messages, miner process output, watchdog alerts, and hardware error reports—all searchable by keyword, severity, or timestamp range.

4. Hardware stress tests can be launched remotely: MemTest for VRAM, FurMark for GPU load, and Prime95 for CPU validation—all with configurable duration and intensity.

5. Crash dumps are captured automatically on kernel panic or miner segmentation fault and uploaded to encrypted storage linked to the rig ID.

Frequently Asked Questions

Q1: Can HiveOS manage rigs with mixed GPU vendors in one farm?Yes. HiveOS natively supports concurrent NVIDIA, AMD, and Intel Arc GPUs within the same farm, applying vendor-specific drivers and tuning parameters automatically.

Q2: Is there a limit to the number of rigs managed under a single HiveOS account?No rigid cap exists—enterprise accounts have successfully managed over 2,400 rigs. Performance remains stable as long as network bandwidth supports telemetry packet volume.

Q3: Does HiveOS require outbound internet access from each rig?Each rig must maintain HTTPS connectivity to hiveon.com endpoints for configuration sync, firmware delivery, and metric reporting. Local-only mode disables remote management features.

Q4: How does HiveOS handle dual-mining configurations like ETH+CKB or TON+ETH?Dual-mining is supported via pre-integrated miner wrappers. Users select dual-mode from the algorithm dropdown and configure secondary coin wallet and pool separately in the advanced settings panel.