Replacing a faulty Cisco router is one of the most time-sensitive tasks a network engineer faces. Done correctly, it is a structured process: back up configuration and the IOS image from the old router, prepare the replacement unit, transfer the image, load the configuration, verify licenses, and restore connectivity. Done incorrectly, a router replacement can turn a hardware fault into an extended outage.
This guide covers the complete replacement procedure for Cisco ISR (Integrated Services Routers — 1900, 2900, 3900, 4000 series) and ASR (Aggregation Services Routers — 1000 series) platforms running IOS or IOS-XE. It includes a dedicated section on the often-overlooked requirement to specify a TFTP source interface when transferring files on routers.
The procedure in this guide applies to the following Cisco router families, with notes where behaviour differs:
Note: License handling differs significantly between platforms and is covered in its own section below.
A router replacement follows this high-level sequence:
If the faulty router is still partially accessible via console or SSH, extract as much information as possible before swapping hardware.
Document the exact IOS version, feature set, and hardware to ensure you source a matching or compatible image for the replacement:
show version show inventory show license show license udi
The show version output will tell you the exact image filename currently running, for example:
System image file is "flash:isr4400-universalk9.17.06.05.SPA.bin"
The show license udi output gives you the Unique Device Identifier (UDI) — you will need this to transfer licenses to the new unit.
Save to TFTP server:
copy running-config tftp://192.168.10.10/faulty-router-running-config.txt
Save to local flash as a fallback:
copy running-config flash:running-config-backup.txt
If the router is completely unresponsive, retrieve the startup configuration from flash using ROMMON (covered in the Troubleshooting section).
If the replacement unit needs the same IOS image and you have it on the faulty router's flash, copy it to the TFTP server now — while you still have access:
copy flash:isr4400-universalk9.17.06.05.SPA.bin tftp://192.168.10.10/
Note on TFTP Source Interface: If this copy fails, the router may not be able to route packets out the management interface using a default source. See Phase 3 for how to fix this.
Photograph or document the physical port connections on the faulty router. Interface naming (GigabitEthernet0/0, GigabitEthernet0/0/0, etc.) varies by platform — a replacement unit of a different sub-model may use different interface names, requiring a config adjustment.
show ip interface brief show interfaces description
reload
Power on the replacement router and connect via console. If this is a brand-new unit, it will boot the factory IOS image and may prompt you with the setup wizard. Answer no to the setup wizard:
--- System Configuration Dialog --- Would you like to enter the initial configuration dialog? [yes/no]: no
You will be dropped into the Router> prompt. Enter privileged mode:
enable
Before you can transfer any files, the replacement router needs a reachable IP address and — critically — the correct TFTP source interface configured.
Unlike switches, routers have multiple interfaces and use routing to determine the source IP of outbound packets. When you run a copy tftp flash: command, the router selects the source IP based on its routing table, which on a freshly booted router may point to the wrong interface or produce no route at all. The TFTP server will receive a connection from an unexpected source IP and may reject it, or the packets may simply not route correctly.
The solution is to explicitly tell the router which interface to use as the source for TFTP traffic using the ip tftp source-interface command. This ensures the TFTP session originates from the interface connected to your management network, where the TFTP server is reachable.
Enter global configuration mode and assign a temporary IP to the interface connected to your TFTP server network. On most ISR platforms this is GigabitEthernet0/0 or GigabitEthernet0/0/0:
For ISR G2 (1900/2900/3900) — interface naming:
configure terminal interface GigabitEthernet0/0 ip address 192.168.10.2 255.255.255.0 no shutdown exit
For ISR 4000 / ASR 1000 / ISR 1000 — interface naming:
configure terminal interface GigabitEthernet0/0/0 ip address 192.168.10.2 255.255.255.0 no shutdown exit
If using a dedicated Management port (ISR 4000, ASR 1000):
configure terminal interface GigabitEthernet0 vrf forwarding Mgmt-intf ip address 192.168.10.2 255.255.255.0 no shutdown exit
Note: ISR 4000 and ASR 1000 routers have a dedicated out-of-band management port (GigabitEthernet0) that operates in a separate VRF named Mgmt-intf. If you use this port, you must also specify the VRF in the TFTP source interface command (see Step 3.2).
This is the critical command that prevents TFTP transfer failures on routers.
If using a regular in-band interface (e.g., GigabitEthernet0/0 or GigabitEthernet0/0/0):
ip tftp source-interface GigabitEthernet0/0
or for ISR 4000:
ip tftp source-interface GigabitEthernet0/0/0
If using the dedicated management port with Mgmt-intf VRF (ISR 4000 / ASR 1000):
ip tftp source-interface GigabitEthernet0
And also specify the VRF when running the copy command (Step 4.1).
If the TFTP server is not on the same subnet as the management interface, add a temporary static default route:
ip route 0.0.0.0 0.0.0.0 192.168.10.1
Verify reachability to the TFTP server before proceeding:
ping 192.168.10.10
If you are using the Mgmt-intf VRF, use:
ping vrf Mgmt-intf 192.168.10.10
Before copying the image, confirm you have enough space:
ISR G2:
show flash: | include bytes
ISR 4000 / ASR 1000:
show bootflash: | include bytes dir bootflash:
Cisco ISR IOS images range from 100 MB to over 1 GB. Ensure there is adequate free space. If not, delete any existing large files you do not need:
delete bootflash:old-image.bin
For ISR G2 (copies to flash:):
copy tftp://192.168.10.10/isr-universalk9-mz.155-3.M9.bin flash:
For ISR 4000 / ISR 1000 (copies to bootflash:):
copy tftp://192.168.10.10/isr4400-universalk9.17.06.05.SPA.bin bootflash:
If using the Mgmt-intf VRF on ISR 4000 / ASR 1000:
copy tftp://192.168.10.10/isr4400-universalk9.17.06.05.SPA.bin bootflash: vrf Mgmt-intf
The transfer will begin and display progress. Depending on image size and network speed, this may take several minutes:
Destination filename [isr4400-universalk9.17.06.05.SPA.bin]? Accessing tftp://192.168.10.10/isr4400-universalk9.17.06.05.SPA.bin... Loading isr4400-universalk9.17.06.05.SPA.bin from 192.168.10.10: !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! [OK - 588251136 bytes]
Always verify the MD5 checksum after transfer. Compare the result against the value published on Cisco's software download page:
ISR G2:
verify /md5 flash:isr-universalk9-mz.155-3.M9.bin
ISR 4000 / ASR 1000:
verify /md5 bootflash:isr4400-universalk9.17.06.05.SPA.bin
If the checksum does not match, delete the file and re-copy it. Do not proceed with a mismatched image.
Remove any existing boot system entries and point the router to the new image.
ISR G2:
configure terminal no boot system flash:<old-image.bin> boot system flash:isr-universalk9-mz.155-3.M9.bin exit
ISR 4000 / ISR 1000:
configure terminal no boot system bootflash:<old-image.bin> boot system bootflash:isr4400-universalk9.17.06.05.SPA.bin exit
ISR 4000 using Install Mode (if applicable):
If your environment uses install mode on ISR 4000, use the install command instead of setting the boot variable manually:
install add file bootflash:isr4400-universalk9.17.06.05.SPA.bin activate commit
copy running-config startup-config show boot
Confirm the correct image filename is listed as the boot variable before reloading.
reload
After the router comes back up, verify the correct IOS version is running:
show version
After the reload, the router will have come back up with only its boot configuration. Before loading the full configuration from TFTP, re-apply the management IP and TFTP source interface commands so the router can reach your TFTP server:
configure terminal interface GigabitEthernet0/0/0 ip address 192.168.10.2 255.255.255.0 no shutdown exit ip tftp source-interface GigabitEthernet0/0/0 ip route 0.0.0.0 0.0.0.0 192.168.10.1 exit
Load the backed-up configuration directly into the startup configuration, then reload — this is the cleanest method and avoids partial configuration states:
copy tftp://192.168.10.10/faulty-router-running-config.txt startup-config
Alternatively, copy it into the running configuration for immediate application (may cause partial disruption if routing changes occur mid-copy):
copy tftp://192.168.10.10/faulty-router-running-config.txt running-config
If you loaded to startup-config in Step 6.2, reload to ensure a clean boot with the full configuration:
reload
show running-config show ip interface brief show ip route
At this point the router should have all its interfaces configured, routing protocols starting, and VPN or service configurations in place.
Cisco IOS licenses are tied to the hardware UDI (Unique Device Identifier) of each router. Moving a configuration to a new router does not automatically transfer the licenses. The procedure differs based on the licensing model in use.
show license show license udi show version | include License
ISR G2 routers use Product Activation Keys (PAKs) tied to the hardware. To relicense the replacement unit:
show license udicopy tftp://192.168.10.10/replacement-router.lic flash:
license install flash:replacement-router.lic
show license show license detail
ISR 4000 and ASR 1000 series running IOS-XE 16.x and later use Cisco Smart Licensing. Licenses are managed centrally via Cisco Smart Software Manager (CSSM) and are not locked to hardware UDI in the same way.
show license status show license summary
license smart register idtoken <your-token-from-CSSM>
show license status show license summary
Routers running IOS-XE 17.3 or later use Smart Licensing Using Policy (SLP), which allows devices to operate and report usage within a reporting period without immediate registration. The router will still need eventual CSSM reporting:
show license status show license tech support | include Policy
Tip: If you have an active Cisco TAC case for the RMA, Cisco can assist with license transfer directly through the case portal.
Once the IOS, configuration, and licenses are confirmed, physically connect the WAN and LAN production interfaces. Replace the management IP with the router's correct production IP as defined in the loaded configuration.
show ip route show ip bgp summary show ip ospf neighbor show ip eigrp neighbors
show interfaces show crypto isakmp sa show crypto ipsec sa show dmvpn
show ip nat translations show ip nat statistics show policy-map interface
show processes cpu | include five show memory statistics show logging | include ERROR|WARN
show clock show ntp status show ntp associations
This is almost always a source interface issue. Verify:
show ip tftp show running-config | include tftp
Ensure the ip tftp source-interface is set to the interface that can reach the TFTP server. Confirm the interface is up and has an IP:
show interfaces GigabitEthernet0/0/0 ping 192.168.10.10 source GigabitEthernet0/0/0
Also confirm the TFTP server is listening and the firewall allows UDP port 69 from the router's management IP.
Access ROMMON and manually boot the image to diagnose:
rommon 1 > dir flash: rommon 2 > boot flash:isr4400-universalk9.17.06.05.SPA.bin
If the image loads successfully from ROMMON, the boot variable was not set correctly. Fix it after booting:
configure terminal no boot system bootflash:<wrong-entry> boot system bootflash:isr4400-universalk9.17.06.05.SPA.bin exit copy running-config startup-config
If the replacement is a different sub-model, interface names may differ (e.g., the faulty router had GigabitEthernet0/0 but the replacement uses GigabitEthernet0/0/0). You will need to edit the configuration before or after loading it:
configure terminal interface GigabitEthernet0/0/0 ip address <address from old config> <mask> no shutdown exit
If the faulty router's IOS is corrupted but the flash is intact, boot into ROMMON and read the startup-config file:
rommon 1 > dir flash: rommon 2 > more flash:startup-config
Copy the output manually from the console to a text file on your workstation for later use.
For Classic PAK licensing, confirm the PAK has been reassigned to the new UDI at cisco.com/go/license. For Smart Licensing, verify the token is valid and the router can reach CSSM:
show license status ping vrf Mgmt-intf tools.cisco.com
Flash location : flash: Image type : .bin (monolithic IOS) Management interface: GigabitEthernet0/0 TFTP source command : ip tftp source-interface GigabitEthernet0/0 Boot variable : boot system flash:<image.bin> Licensing : Classic PAK (cisco.com/go/license)
Flash location : bootflash: Image type : .bin (bundle) or packages.conf (install mode) Management interface: GigabitEthernet0 (VRF: Mgmt-intf) TFTP source command : ip tftp source-interface GigabitEthernet0 TFTP copy with VRF : copy tftp://server/image.bin bootflash: vrf Mgmt-intf Boot variable : boot system bootflash:<image.bin> Licensing : Smart Licensing / SLP (IOS-XE 17.3+)
Flash location : bootflash: (per RP) Image type : .bin (bundle) or packages.conf Management interface: GigabitEthernet0 (VRF: Mgmt-intf) TFTP source command : ip tftp source-interface GigabitEthernet0 TFTP copy with VRF : copy tftp://server/image.bin bootflash: vrf Mgmt-intf Boot variable : boot system bootflash:<image.bin> Licensing : Smart Licensing / SLP
Flash location : bootflash: Image type : .bin (bundle) or packages.conf Management interface: GigabitEthernet0 (VRF: Mgmt-intf) or GigabitEthernet0/0/0 TFTP source command : ip tftp source-interface GigabitEthernet0/0/0 Boot variable : boot system bootflash:<image.bin> Licensing : Smart Licensing / SLP
ip tftp source-interface before attempting any TFTP transfer on a routerReplacing a faulty Cisco router is a structured process that, when followed in the correct sequence, can restore full network services with minimal downtime. The steps are consistent across the ISR and ASR families: prepare and back up, install the replacement, configure basic IP connectivity, set the TFTP source interface, transfer and verify the IOS image, load the configuration, and migrate licenses.
The ip tftp source-interface command is one of the most important — and most commonly forgotten — steps when working with Cisco routers. Unlike switches, routers do not automatically know which interface to use for management traffic, and a missing source interface setting is the single most common reason TFTP transfers fail during a router replacement.
Thorough pre-failure preparation — particularly maintaining current configuration backups and keeping IOS images on a TFTP server — is what separates a 30-minute router replacement from a multi-hour outage. Build these practices into your standard operations and every router replacement will be a manageable, predictable procedure.