upgraded only the FPD for the cards that the Upg/Dng field marked "Yes"

upgraded all of the FPDs on all cards with an FPD regardless of the Upg/Dng field markings

upgraded only the FPD and ROMMON for the cards that the Upg/Dng field marked "Yes"

upgraded all of the FPDs and ROMMONs on all cards with an FPD or ROMMON regardless of the Upg/Dng field markings

install add tftp://172.20.165.36/hfr-mgbl-p.pie-4.0.1 activate

install activate tftp://172.20.165.36/hfr-mgbl-p.pie-4.0.1

install add disk0:hfr-mgbl-p-4.0.1 activate

install activate disk0:hfr-mgbl-p.pie-4.0.1

RP/0/RSP0/CPU0:P1 (admin)#install remove disk0:asr9k-mpls-p-4.1.0

RP/0/RSP0/CPU0:P1 (config)#install deactivate smu location disk0:

RP/0/RSP0/CPU0:P1 (admin-config)#deactivate disk0:asr9k-mpls-p-4.1.0

RP/0/RSP0/CPU0:P1 (admin)#install deactivate disk0:asr9k-mpls-p-4.1.0

RP/0/RSP0/CPU0:P1 #asr9k-mpls-p-4.1.0 disk0:deactivate sync

P images can only support legacy hardware, while px images can only support new CRS-3 hardware.

P images can use an SMU to operate as x86 images.

P images can only support Power PC hardware, while px images can support both Power PC and Intel hardware in the same chassis.

P and px images can both be installed on the same ROMMON version.

P and px images are roughly the same because they are built to operate on the same system.

(config)#load disk0:name.cfg

#copy disk0:name.cfg running-configuration

#copy tftp://255.255.255.255/name.cfg

#load commit changes <name>

(config)#load commit <name>