ANDROID
Find the Right Device in a Data Center Rack Using a Phone
Find the correct NetBox device in a physical rack using Android. Check site, U position, rack face, serial and asset tag before field maintenance.
There are 40 devices in the cabinet, several share the same model, and the work order names a switch that is no longer labeled clearly. Before touching a cable or power supply, you need to identify one physical chassis, find its existing NetBox record, and verify that the rack, location and physical identifiers agree. A successful search result is only a candidate until you make that comparison.
This guide uses an authorized Android phone and the read-only Field Companion for NetBox to complete that field check. You can search existing Devices and Racks, open their details, and inspect the available Site, Location, Rack, Position, serial and asset-tag fields. You do not need a QR label for every device. The app does not discover live equipment, render a complete rack elevation, or change NetBox records; the full NetBox web interface remains the source of truth.
First decide what you are trying to identify
Three jobs are often mixed together at a rack. Keep them separate to avoid looking up the wrong object.
| Your field question | Start with | Confirm before acting |
|---|---|---|
| Which cabinet am I standing at? | A Rack search using a documented rack name, then its NetBox record. | Site, Location, Rack name and (where available) the facility-assigned Rack ID. |
| Which device is this chassis? | A Device search using a known hostname or other tested lookup term. | Site, Rack, Position, device type, physical serial or asset tag. |
| I know an IP address, not the hostname. | The IP Address search result, then the assigned object and related device as applicable. | Address context, VRF/assignment and the physical device identity in NetBox. |
Suppose your ticket says Site DC-East, Rack R14, switch edge-sw-03. These are illustrative identifiers only. If the rack door says R14 but NetBox calls it R14-A, confirm whether you are seeing an internal rack name, a facility ID or an outdated label. A co-location facility may identify a cabinet by its own Facility ID while the NetBox team uses a shorter Rack name. NetBox’s Rack model supports both identifiers, but a facility ID being present in NetBox does not mean the Android search bar will search that field directly.
Step 1. Confirm the NetBox instance, account and physical rack
- Open Field Companion on the Android phone and confirm it is connected to the correct organization’s HTTPS NetBox installation. A numeric device ID or familiar hostname can identify different objects across independent instances.
- Use a dedicated read-only API token with permission to view the relevant Devices, Racks and related objects. If the phone cannot connect or an expected permitted object is denied, follow the first-connection guide before looking for the rack.
- Use the app’s search interface to find the Rack by a known, searchable name. Open the Rack result. Check the displayed Site, Location, Status, Facility ID and Height when present in the record.
- Compare the Rack identity against the actual cabinet and the approved work order. If the rack’s NetBox location does not match the building, cage or row, stop; do not let a matching short name override a site mismatch.
Current Field Companion source retrieves Rack details from the authorized NetBox API and can display Rack Site, Location, Status, Role, Facility ID, Height, Serial and Asset tag when those fields contain values. It does not render the native NetBox rack elevation diagram or automatically enumerate every device mounted in that rack. If you need the full front/rear layout or an exhaustive cabinet inventory, use the authenticated NetBox Rack view in the normal web interface.
Step 2. Search for the device, then inspect the candidate record
From Search in Field Companion, enter a known device name or other identifier that your NetBox installation actually indexes. The current app submits the same text to three read-only API collections: Devices, Racks and IP Addresses, requesting up to eight results per object type. The on-screen category chips filter already returned results; they are not a claim that a complete rack or every matching device has been loaded.
- Start with the exact hostname from the change ticket when it is trustworthy, such as
edge-sw-03. A partial search can help, but may produce many candidate objects. - Choose a Device result, not a similarly named Rack or IP Address entry. On the result list, the app can show a Device name and brief Site/Role/Device type context.
- Open the Device detail. Check Site, Location, Rack, Position (U and face, if provided), device type, Serial and Asset tag. Compare at least one hardware identifier physically visible on the equipment with the existing NetBox record.
- If no result appears, or you suspect the phone displayed only a subset, refine the term or use the full NetBox browser search and object filters. Do not interpret an empty mobile result as proof that the physical device is absent.
Search caveat: although the app’s search placeholder mentions hostnames, IPs, asset tags and serial numbers, its implementation sends a general q query to the configured NetBox API. The fields matched by that query can vary by object type, NetBox version and server customizations. A typed serial or asset tag is not a guaranteed exact-field lookup. The mobile application does not provide a rack-scoped advanced search or automatically cross-check the chassis against live network telemetry.
Step 3. Interpret rack U position, height and front/rear correctly
NetBox’s Device model documentation defines a Device’s rack Position as its lowest-numbered occupied rack unit. Thus a synthetic 3U device occupying U8–U10 is recorded at Position U8, not U10, even if the rack’s numbering runs in descending physical order. The recorded Rack Face indicates front or rear where assigned.
| NetBox field result | Correct field interpretation | Potential mismatch |
|---|---|---|
| Position: 8 U · Front | Look for equipment whose occupied range starts at numbered U8 on the front side. | Do not assume this is the eighth slot counting down from the top of every cabinet. |
| Device type: 3U chassis | The recorded base U is U8 for equipment spanning U8–U10. | Confusing U10 with the recorded device position. |
| Rack: R14; Position absent | Inspect alternate identifiers and the official rack record; position may be unassigned. | Assuming a blank position means the device does not exist. |
| 0U equipment such as a vertical PDU | May be assigned to a rack without consuming a numbered rack unit. | Trying to infer a physical U slot that NetBox does not record. |
| Rack has descending units | Use the rack’s actual visible numbering direction and NetBox’s configured rack unit scheme. | Counting U units in the opposite direction. |
Position and face are location clues, not independent proof of hardware identity. A device might be moved without an immediate inventory update; a 0U component may occupy a side rail; a replacement chassis may keep the old hostname. Confirm the actual physical serial, asset tag or explicitly maintained service label as well.
Step 4. Resolve ambiguous or conflicting identifiers
The safest lookup is not always the shortest one. Use the identifier that survives renames and can be physically verified, rather than a plausible-looking title alone.
| Situation in front of you | Check next | When to stop |
|---|---|---|
| Two devices have similar hostnames | Compare Site, Rack, Position, device type, physical serial and asset tag. | You cannot tie one unique NetBox record to the chassis. |
| Rack label differs from NetBox | Check Location and the Rack’s separately recorded Facility ID with the site owner. | Cabinet identity is still ambiguous across rooms, sites or cages. |
| Serial or asset-tag search yields nothing | Use a known device name or the authorized full NetBox UI; inspect the record’s explicit serial/asset field. | The actual chassis identifier conflicts with the candidate record. |
| Rack U position seems wrong | Check front/rear face, 0U/multi-U equipment and ascending/descending rack numbering. | You cannot confidently map the recorded position to physical equipment. |
| Search returns partial or no results | Use a narrower or different term, account View permissions, full NetBox filters and pagination. | Required record cannot be verified; a missing result does not authorize a guess. |
| Only an offline cached record appears | Restore a trusted network route and compare with current server data. | The task requires current state and no live confirmation is available. |
For already labeled equipment, the companion NetBox QR and barcode field guide explains device-URL scanning, text-search fallback and wrong-instance risks. Do not treat a printed QR’s device ID as unique across multiple NetBox installations: the current mobile app resolves it against the configured server. When the returned location differs from what you see physically, hand the discrepancy to the NetBox inventory owner through your existing change process; the Android app does not change rack assignments.
Step 5. Finish a read-only field acceptance check
In a safe pilot, choose one synthetic Device and one synthetic Rack with populated identity fields. For example, configure Site DC-East, Rack R14 with Facility ID FAC-014, and Device edge-sw-03 at 8 U · Front, with a known serial/asset tag. These are fabricated identifiers for an acceptance exercise—not a real inventory export.
- Search
R14; open the Rack result and compare its Site, Facility ID and Height to the expected reference. - Search
edge-sw-03; inspect the Device’s Site, Rack, Position/Face, device type, Serial and Asset tag, if present. - Intentionally test a different or wrong-name Rack on a synthetic fixture. The technician must recognize and reject the mismatch rather than proceeding.
- Attempt an overly broad search and note whether the mobile result cap hides a known object. Confirm the complete set in the authenticated NetBox web UI.
- With connectivity deliberately removed from the test setup, distinguish a previously cached record from a live response. Treat cached data as history, not authorization for a change.
To begin with the actual Android release, use the Field Companion product page and its Google Play listing. The product is an independent NetBox-compatible read-only client, not an official NetBox Labs offering. Its support page covers reporting sanitized device/version issues without disclosing API tokens or internal inventory. Avoid putting real credentials or serials into public bug reports or sample screenshots.
Which field check should you make next?
This local decision guide maps a real-world lookup result to the next safe action. It does not contact your instance, measure a rack, discover devices or change any record.
What do you know about the device in front of you?
Applies when: You have authorized read-only access to a known NetBox installation and want to verify a physical device inside a data center rack. This checklist does not query NetBox or make hardware changes.
Quick answer
Identify the correct rack and Site first. Find a candidate Device, inspect the available Rack, Position, serial and asset tag fields, then match an independently observed chassis identifier and approved work order. Stop when the evidence conflicts.
What to do
-
Use a known Rack name or other tested search term. Inspect the Rack's Site, Location and Facility ID when present; the cabinet's facility label may differ from its internal NetBox name.
-
Field Companion's ordinary search queries Device, Rack and IP Address collections with a bounded set of results. It does not enumerate all devices in a rack or guarantee exact serial/asset-tag matching.
-
Open the Device record and compare Site, Rack, Position/Face if set, device type, serial or asset tag to the actual chassis. Multi-U device position is the lowest numbered unit it occupies; 0U equipment may have no U position.
-
A live, consistent record supports physical identification, not authorization to perform work. If a record is absent, ambiguous, conflicting or cached offline, use the full NetBox interface or request owner review before touching hardware.
What is your current obstacle?
All paths are listed below. Select a symptom to focus on the most relevant path.
Establish the physical cabinet identity
Match Site and Location before choosing a familiar Rack name. Inspect NetBox Rack's optional Facility ID, serial or asset tag to reconcile a data-center operator's cabinet number. Stop if the building, cage or row remains uncertain.
Change the search evidence, not the device
Try a known device name or a more specific term. The app requests up to eight matches from each of three NetBox collections; absent results may reflect paging, search behavior or permissions. Use the authorized full NetBox web view for exhaustive filtering.
Check U numbering, device height and rack orientation
NetBox stores the lowest numbered occupied U as a multi-U device's Position; its rack can use ascending or descending numbering. The app shows Position and face if recorded, not a full elevation. A 0U vertical PDU may not have a numbered U slot.
Stop and request an authorized discrepancy review
Do not choose hardware solely by hostname, IP or U position. Compare the actual chassis serial or asset tag with the live record and work order. If they disagree, record a sanitized discrepancy through the inventory team's normal change process without modifying the physical device.
Reconnect for authoritative information
Previously viewed NetBox records may be cached. An offline result is historical and may describe moved or replaced equipment. Where a change requires current information, reconnect before acting.
Finish the approved work-order check
Confirm the right NetBox server, Rack, Site, physical chassis identifier and a live matching record. These support identification only; continue exclusively within your organization's separately approved physical change procedure.
Did this help?
Before touching a device: six confirmations
- Correct server: The Android client is connected to the intended NetBox instance using an authorized, read-only token.
- Correct cabinet: The Rack’s Site, Location and name/Facility ID are consistent with the physically labeled enclosure.
- Correct chassis: The Device’s physical serial/asset label or another independently observed identifier matches the live NetBox record and work order.
- Correct position: Rack U position, face and multi-U/0U conventions explain where the equipment is installed; missing position is not silently guessed.
- Current information: You have a live response where the task requires current inventory state; offline cache is not mistaken for live verification.
- Authorized action: Your team’s maintenance/change approval covers the specific chassis. Field Companion identifies records but does not edit them or grant physical authorization.
Keep the broader ModelGain Android tools directory available for supported releases. For exact Site, Rack, Position and physical inventory semantics, use the upstream NetBox Device and Rack references. When NetBox and the cabinet disagree, stop and reconcile the source-of-truth record before any physical change.