Define the target
Use private management subnets, VLANs, or explicit ranges that belong to the mining operation.
Scan the intended private subnet, confirm discovered ASIC miners and diagnose missing devices without exposing management interfaces publicly.
Workflow
BTC Tools imports or accepts IP ranges for local miner discovery. A useful scan begins with an accurate network plan and ends with reconciliation against physical or DHCP records.
Use private management subnets, VLANs, or explicit ranges that belong to the mining operation.
Large environments are easier to troubleshoot when ranges map to racks, switches, or rooms.
Compare IP, MAC, model, and physical labels where those records are available.
A missing miner may reflect power, cable, switch, VLAN, DHCP, firewall, or firmware conditions.
Checklist
Avoid broad scans that mix miner networks with office, guest, or public infrastructure.
Operations
Treat scan output as an observation that still needs network and inventory context.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Miner found | IP, model, and rack record agree | Add it to the reviewed working group. |
| Expected miner missing | Power, link, VLAN, DHCP, or wrong range | Check the physical and network path first. |
| Unexpected device | Unknown IP or model | Exclude it until ownership and identity are confirmed. |
| Duplicate IP symptom | Intermittent reachability or changing identity | Reconcile MAC, DHCP reservation, and static settings. |
| Many devices missing | Shared switch, uplink, VLAN, or range issue | Investigate the segment instead of individual miners. |
Setup
Label reviewed miners by rack, switch, subnet, or maintenance group so later configuration actions operate on known devices rather than a raw list of IP addresses.
