Reserve the range
Keep miner addresses separate from DHCP pools, infrastructure, and unrelated office devices.
Document and assign miner IP addresses carefully so BTC Tools discovery remains predictable and duplicate addresses do not disrupt management.
Workflow
Static addressing can make miner operations predictable, but a bulk network change can also make an entire group unreachable. Build the IP plan outside the tool and test one segment at a time.
Keep miner addresses separate from DHCP pools, infrastructure, and unrelated office devices.
Assign ranges by room, rack, switch, or VLAN so an address carries operational context.
Use MAC-to-IP records to resolve conflicts and replaced devices.
Know how to reach, reset, or locally inspect a miner if a network change fails.
Checklist
A complete plan includes gateway, mask, DNS where required, and addresses reserved from other services.
Operations
Use a shared source of truth rather than reconstructing network ownership from scan results later.
| Area | What to check | BTC Tools workflow |
|---|---|---|
| Subnet | Network and prefix length | Defines the valid local address space. |
| Gateway | Router address for the management network | Required only where routing is intended. |
| DHCP range | Automatically assigned address pool | Must not overlap planned static addresses. |
| Static range | Reserved miner addresses | Assign by rack, room, switch, or asset plan. |
| MAC mapping | Device MAC to intended IP | Supports conflict and replacement diagnosis. |
| Rollback | Previous address or reset method | Needed when a changed miner becomes unreachable. |
Setup
Apply the address plan to a small group, verify each miner at its new IP, update inventory records, and confirm no conflict before moving to the next rack or subnet.
