Cisco Cisco Packet Data Gateway (PDG)

 

▄  VPC-VSM System Administration Guide, StarOS Release 19 

Assign the next highest priority to this entry, by using the <N-1> method, wherein you assign a priority number that is 
one number less than your current highest priority. 

If priority 1 is in use, you must renumber the existing entries to ensure that at least that priority is available.  

The maximum number of boot stack entries that can be contained in the boot.sys file is 10. If there are already 10 entries 
in the boot stack, you must delete at least one of these entries (typically, the lowest priority) and, if necessary, renumber 
some or all of the other entries before proceeding. Use the no boot system priority command to delete a book stack 
entry. 

For information on using the boot system priority command, refer to the Adding a New Boot Stack Entry section of the 
StarOS Management Operations chapter. 

Reboot StarOS by entering the following command: 

[local]host_name# reload [-noconfirm] 

As StarOS reboots, it loads the new .bin software image and its corresponding CLI configuration file using the new boot 
stack entry configured earlier.  

After the system reboots, establish a StarOS CLI session and enter the show version command to verify that the active 
software version is correct. 

Features in the new operating system may require changes tot he configuration file. These changes can be done 
manually or facilitated by custom scripts prepared by Cisco TAC. Make whatever changes are necessary prior to saving 
the updated configuration file. 

After StarOS has successfully booted, verify that the new StarOS version is running by executing the Exec mode show 
version command.  

Use the Exec mode save configuration command to save the currently running configuration to the /flash device and to 
an off-chassis location (network URL). The off-chassis copy assures that you will have a fallback, loadable 
configuration file should a problem be encountered. 

Repeat the following tasks to complete the upgrade process on the standby secondary instance: 



 

  

