Factory bare-metal: unpack and go
For factory-shipped AdWAN appliances (for example Dell VEP1425), you no longer need to whitelist the serial in the portal before rack and power-on. The unit leaves manufacturing with a factory identity; you claim it into your organization, assign a site, cable per the SKU card, and power on.
The whitelist wizard and bulk CSV import remain supported for pilots, RMA replacements, lab units, and any device that was not factory-enrolled. Factory ZTP is the default path for volume shipments.
When to use this path
| Situation | Path |
|---|---|
| New factory-shipped VEP1425 (or other factory-enrolled SKU) | This guide — claim → assign site → cable → power on |
| Pilot, lab, RMA, or pre-factory inventory | Managing device whitelists |
| Cloud VM (AWS / Azure / GCP) | Registering a device (bootstrap token) |
| On-prem VM | On-prem VM |
Overview
Claim code (QR on box) → Redeem in portal → Assign site → Cable → Power on
After claim and site assignment, the platform creates a whitelist entry with SKU default port mappings. The appliance registers automatically on first boot — no serial typing in the whitelist wizard.
Step 1 — Claim the appliance
- Log in to the customer portal.
- Open Devices → Unassigned Appliances (
/devices/unassigned). - In Claim with code, paste the code from the appliance label or QR (format
usdn-claim:<code>or the code alone). - Optionally pick a site and environment now, or assign the site later from the table below.
- Click Redeem code.
If your USDN sales engineer already claimed the serial to your org, skip redeem and go to Step 2.
Step 2 — Assign a site
If the appliance appears under Unassigned appliances (claimed but no site):
- Click Assign site on the row.
- Choose the target site and environment.
- Confirm Assign site.
The platform applies the SKU interface mapping template (for VEP1425, see cable map below). You do not need the whitelist wizard for standard wiring.
Step 3 — Cable (VEP1425-V210)
Standard unpack-and-go wiring for branch CPE:
| Port | Role | Connect to |
|---|---|---|
| GE1 | Primary WAN | Customer ISP / handoff (DHCP) |
| GE2 | Secondary WAN | Optional second uplink (DHCP) |
| GE3 | Management | Optional; legacy mgmt port (prefer out-of-band when possible) |
| GE5 | LAN | Switch or downstream LAN |
| Power | — | 12V DC per faceplate |
SFP+ and unused GE ports can stay disconnected; the agent can discover alternate WAN paths if your cabling differs.
Step 4 — Power on
- Ensure GE1 has a route to the internet (for platform registration and controller reachability).
- Power on the appliance.
- First boot uses the factory identity burned at manufacture — the device calls the existing registration API (
POST /v1/devices/add/) once the whitelist exists. - Within roughly 15–30 minutes (depending on WAN DHCP), the device should appear under Devices for the assigned site.
Verify
- Devices list shows the serial at the assigned site.
- No manual whitelist entry was required before power-on.
- If registration fails, confirm claim + site assignment completed before first boot, and that GE1 is cabled to a working WAN.
Troubleshooting
| Symptom | Check |
|---|---|
| Redeem fails (expired / invalid code) | Contact USDN support or your SE for a new claim code |
| Serial not in unassigned list | Confirm the unit was factory-enrolled; use manual whitelist if it is a pilot/lab box |
| Device does not appear after power-on | Whitelist + site must exist before first boot; verify GE1 WAN DHCP |
| Wrong ports after boot | Non-standard cabling — SE can adjust mappings via the whitelist wizard |
Related guides
- Unassigned Appliances (SE / admin) — internal runbook for claim codes and SE assign
- Managing device whitelists — manual path for pilots and RMA
- Registering a device — cloud and general device registration