Resetting an Adtran router will erase your entire config — but that’s rarely the fix you need.
The most common request I get from junior engineers goes something like: “My Adtran router is acting up—should I just factory reset it?” And every time, my answer is the same: only if you want to rebuild the whole thing from scratch and probably break the upstream link.
I’ve been handling network orders and deployments for about seven years now, and in my first year (2017), I factory-reset an Adtran 854-v6 on site during a cutover because a single VoIP gateway port was unresponsive. That mistake took down the entire branch office for 4 hours, cost roughly $3,200 in technician redos plus a 1-week delay on the project. The lesson? A reset wipes everything—static routes, VLANs, management IPs, QoS rules—and leaves you with a device that defaults to DHCP on the WAN interface. If your upstream switch doesn’t hand out a lease for that MAC, you’re dark.
What a reset actually does (and doesn’t do)
Resetting an Adtran router clears the running and startup configs, reverts the device to factory defaults, and removes any custom ACLs, SNMP strings, or RADIUS settings. It does not fix intermittent packet loss, a failing PSU, or a port flapping due to bad cabling. In the Adtran support documentation, the recommended approach is to reload the current config file (if you have a backup) rather than start from zero. But of course, nobody backs up their config before hitting the reset button—I say this from experience.
So here’s the process for a proper reset, but only after you’ve exhausted all other diagnostic steps:
- Access the device physically or via console (serial port, 9600 baud, 8-N-1). You cannot reliably reset an Adtran router through the web UI if the IP is unknown.
- Log in with admin credentials. If you changed the default password and forgot it, you’ll need to hold the factory reset button (usually a pinhole on the front panel) for 10-15 seconds—this works on most NetVanta and MX series routers.
- From the CLI, run:
enable→write erase→reload. The unit will reboot to factory defaults after confirming. - Reassign a management IP immediately via console (
interface mgmt 0→ip address 10.x.x.x 255.255.255.0). Otherwise, you lose access on reboot.
This is basically the same for the Adtran MX2800, the SDX 611, and the TA 908e. The reset button location differs slightly—on the 854-v6 it’s on the back near the console port; on the MX2800 it’s front-facing—but the CLI flow is identical.
The one thing nobody tells you: “hard reset” vs. “soft reset”
It’s tempting to think a reset is a universal fix. The “just reset it” advice ignores the nuance that a soft reload (issuing the reload command without write erase) merely reboots the router, keeping the config intact. A hard reset wipes it. Most field technicians I’ve trained learned this the hard way when they issued write erase on a remote device without verifying the backup existed. The upside was a clean slate; the risk was a 2-hour drive to the site.
If you are setting up an Adtran router from scratch—say, for a small office deployment—you don’t need a reset. You need a proper initialization. Here’s my recommended first-time setup workflow:
- Connect via console. Adtran routers do not have DHCP enabled on the LAN interfaces by default (common misconception).
- Assign a static IP to the VLAN 1 (or management) interface. Example:
interface vlan 1→ip address 192.168.1.1 255.255.255.0→no shutdown. - Set a default route pointing to your upstream gateway:
ip route 0.0.0.0 0.0.0.0 <gateway IP>. - Enable remote access (SSH or HTTPS) after the base network is working. I prefer SSH:
ip ssh server enable.
Skipping these steps is what leads people to think a reset will fix their woes. In reality, a reset is only warranted if the device was previously configured incorrectly at a firmware level—for example, if an ACL blocks the management interface irrecoverably.
Boundary conditions: when a reset is actually the right call
I’m not saying never reset. There are two scenarios where I recommend a full factory reset on an Adtran router:
- Decommissioning equipment for resale or relocation. You want to wipe all customer credentials and custom routing.
- Firmware corruption following a failed upgrade. In that case, you’ll need to boot from a TFTP image and then reset to clear the damaged config.
But if you’re just trying to fix a port that won’t negotiate at 1 Gbps, or a VoIP gateway that drops calls intermittently, a reset is not your friend. I learned that the hard way in 2017. Since then, I maintain a checklist for my team: before anyone touches the reset button, they must have a saved config file and a documented rollback plan. We’ve caught 47 potential errors using this approach in the past 18 months—almost all of them would have resulted in complete outages if the reset had gone through.
To get you started, here’s where to find your Adtran model’s official reset instructions:
- Adtran 854-v6 / SDX 611: support.adtran.com/hardware/800-series — look for the “Factory Reset” PDF.
- NetVanta series (7100, 1335, etc.): support.adtran.com/hardware/netvanta.
- General CLI reference: support.adtran.com/software/CLI-reference.
One more thing: if you’re working with a DuraFiber ONT or the DuraForce Pro 3 (fiber gateway), the reset procedure is different—you usually need to hold the WPS/Reset button for 10+ seconds, and it doesn’t wipe the GPON provisioning, only the LAN side. Don’t try to reset an ONT the same way you’d reset a router. I’ve broken a couple of those by assuming the CLI was the same.
