Cisco Cisco Packet Data Gateway (PDG)
![Cisco](https://files.manualsbrain.com/attachments/7380d0050044647c30f5c24bbbf5d0c0b6d9bb84/common/fit/150/50/faa183d287233c52228cfea3dbc2a127fe780f60564fcb0955d9c3d1cd23/brand_logo.png)
Software Management Operations
Upgrading the Operating System Software ▀
ASR 5000 System Administration Guide, StarOS Release 18 ▄
151
Aborting an On-line Software Upgrade
Abort the on-line software upgrade process by entering the following command:
[local]host_name# abort upgrade [-noconfirm]
Important:
The abort upgrade command can only be used during Stage 1 (busy-out) of an on-line software
upgrade.
Restoring the Previous (Pre-online Upgrade) Software Image
If for some reason you need to restore the system to the software image that was running before the online upgrade
process, perform the On-Line Software Upgrade again and specify the locations of the original software image and
configuration files.
process, perform the On-Line Software Upgrade again and specify the locations of the original software image and
configuration files.
Off-line Software Upgrade
An off-line software upgrade can be performed for any system, upgrading from any version of operating system
software to any version, regardless of version number. This process is considered off-line because while many of the
steps can be performed while the system is currently supporting sessions, the last step of this process requires a reboot to
actually apply the software upgrade.
software to any version, regardless of version number. This process is considered off-line because while many of the
steps can be performed while the system is currently supporting sessions, the last step of this process requires a reboot to
actually apply the software upgrade.
This procedure assumes that you have a CLI session established and are placing the new operating system image file
onto the local file system. To begin, make sure you are at the Exec mode prompt:
onto the local file system. To begin, make sure you are at the Exec mode prompt:
[local]host_name#
Configure a Newcall Policy
Configure a newcall policy from the Exec mode to meet your service requirements. When enabled the policy redirects
or rejects new calls in anticipation of the chassis reload that completes the upgrade process. This reduces the amount of
service disruption to subscribers caused by the system reload that completes the upgrade.
or rejects new calls in anticipation of the chassis reload that completes the upgrade process. This reduces the amount of
service disruption to subscribers caused by the system reload that completes the upgrade.
Important:
Newcall policies are created on a per-service basis. If you have multiple services running on the
chassis, you can configure multiple newcall policies.
The syntax for newcall policies is described below:
[local]host_name# newcall policy { asngw-service | asnpc-service | sgsn-service }
{ all | name service_name } reject
{ all | name service_name } reject
[local]host_name# newcall policy cscf-service { all | name service_name }
{ redirect target_ip_address [ weight weight_num ] [ target_ipaddress2
[ weight weight_num ] ... target_ip_address16 [ weight weight_num ] | reject }
{ redirect target_ip_address [ weight weight_num ] [ target_ipaddress2
[ weight weight_num ] ... target_ip_address16 [ weight weight_num ] | reject }
[local]host_name# newcall policy { fa-service | lns-service | mipv6ha-service }
{ all | name service_name } reject
{ all | name service_name } reject