Hi Aaron You can't upgrade directly from release 4 to 6. First upgrade to 5.3.4 before upgrading to release 6.
It's recommended to remove fpd auto-upgrade in the admin config (if configure) when upgrading between major releases. RP/0/RSP0/CPU0:hostname(admin)#sh run | i auto Thu Oct 24 10:12:41.175 SAST Building configuration... *fpd auto-upgrade* Install the post-expiry SMU and root cert, else you won't be able to add install add any new software. This document is for 5.1.3 - you'll need the 4.3.4 SMU https://www.cisco.com/c/en/us/td/docs/routers/technotes/MOP-CSS-to-Abraxas.html Once complete, you would be able to add the 5.3.4 PIE files. install add ... install active disk0:*5.3.4* asynchronous install commit - after the reload. Run a FPD upgrade. RP/0/RSP0/CPU0:hostname(admin)#upgrade hw-module fpd all location all Once the FPD upgrade is complete - remove the 4.3.4 inactive files to ensure you have enough space on the router. RP/0/RSP0/CPU0:hostname(admin)#install remove inactive asynchronous Now you are ready to add the 6.5.2 PIE files and relevant SMU's. install add install active install commit -Werner On Thu, Oct 24, 2019 at 4:32 AM Aaron Gould <aar...@gvtc.com> wrote: > It got jumbled ... I'll try again... > > > admin install add disk1:asr9k-mgbl-px.pie-4.3.4 > disk1:asr9k-mpls-px.pie-4.3.4 disk1:asr9k-mini-px.pie-4.3.4 > disk1:asr9k-fpd-px.pie-4.3.4 synchronous > > admin install activate disk0:asr9k-mgbl-px-4.3.4 disk0:asr9k-mpls-px-4.3.4 > disk0:asr9k-mini-px-4.3.4 disk0:asr9k-fpd-px-4.3.4 synchronous > > (after reboot occurs) > > admin install commit > > > > _______________________________________________ > cisco-nsp mailing list cisco-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ > _______________________________________________ cisco-nsp mailing list cisco-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/