Important Notice: Our web hosting provider recently started charging us for additional visits, which was unexpected. In response, we're seeking donations. Depending on the situation, we may explore different monetization options for our Community and Expert Contributors. It's crucial to provide more returns for their expertise and offer more Expert Validated Answers or AI Validated Answers. Learn more about our hosting issue here.

Does Software Management support software upgrades on dual RSP-based systems?

April 26, 2017dual Management Software support SYSTEMS upgrades

0

Posted

Does Software Management support software upgrades on dual RSP-based systems?

2 Answers

0

Posted

A. Software Management updates the software on the master RSP processor by copying the software image file to the master RSP Flash card (bootflash: slot0: slot1:) and updating the config file on the master RSP. Software Management cannot do a complete job of upgrading the software on the slave RSP processor. Software Management can only copy the software image file to the slave RSP processor, but it cannot update the config file on that processor. Users will have to run a separate Distribute Images job to copy the software image file to the slave RSP processor. Because Software Management cannot update the config file on the slave RSP processor, users must select “Don’t touch config file” and select the “no reboot” option in the job created for upgrading software on the slave RSP processor.

0

Posted

A. Software Management updates the software on the master RSP processor by copying the software image file to the master RSP Flash card (bootflash: slot0: slot1:) and updating the config file on the master RSP. Software Management cannot do a complete job of upgrading the software on the slave RSP processor. Software Management can only copy the software image file to the slave RSP processor, but it cannot update the config file on that processor. Users will have to run a separate Distribute Images job to copy the software image file to the slave RSP processor. Since Software Management cannot update the config file on the slave RSP processor, users must select Don’t touch config file and select the No Reboot option in the job created for upgrading software on the slave RSP processor.