для Cisco Cisco Packet Data Gateway (PDG)
StarOS Management Operations
Upgrading StarOS ▀
VPC-VSM System Administration Guide, StarOS Release 19 ▄
105
[local]host_name# show version /flash/image_filename.bin
Saving a Copy of the Current Configuration File
Prior to upgrading to a new StarOS release, you should copy and rename the current configuration file to the /flash
device and to an off-chassis location (external memory device or network URL). This renamed copy assures that you
will have a fallback, loadable configuration file should a problem be encountered during the upgrade.
device and to an off-chassis location (external memory device or network URL). This renamed copy assures that you
will have a fallback, loadable configuration file should a problem be encountered during the upgrade.
Off-line Software Upgrade
An off-line software upgrade can be performed for any VPC, upgrading from any version of StarOS to any other
version, regardless of version number. This process is considered off-line because while many of the steps can be
performed while the VPC is currently supporting sessions, the last step of this process requires a reload to actually apply
the StarOS upgrade.
version, regardless of version number. This process is considered off-line because while many of the steps can be
performed while the VPC is currently supporting sessions, the last step of this process requires a reload to actually apply
the StarOS upgrade.
This procedure assumes that you have a CLI session established and are placing the new StarOS .bin image file onto the
local file system. To begin, make sure you are at the Exec mode prompt.
local file system. To begin, make sure you are at the Exec mode prompt.
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 StarOS 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 StarOS 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
VPC, you can configure multiple newcall policies.
The general syntax for newcall policies is described below:
[local]host_name# newcall policy service_type { all | name service_name } reject
Keyword availability varies by service_type. For a complete description of the newcall policy command with all its
associated keywords, see the Exec Mode Commands chapter of the Command Line Interface Reference.
associated keywords, see the Exec Mode Commands chapter of the Command Line Interface Reference.
Configure a Message of the Day Banner
Optional: Configure a “Message of the Day” banner informing other management users that the system will be rebooted
by entering the following command from the Global Configuration mode prompt.
by entering the following command from the Global Configuration mode prompt.
[local]host_name(config)# banner motd “banner_text”
banner_text is the message that you would like to be displayed and can be up to 2048 alphanumeric characters. Note
that banner_text must begin with and end in double quotation marks (“ “). For more information in entering CLI banner
information, see the CLI Reference. The banner is displayed when an administrative user logs onto the CLI.
that banner_text must begin with and end in double quotation marks (“ “). For more information in entering CLI banner
information, see the CLI Reference. The banner is displayed when an administrative user logs onto the CLI.
Back up the Current CLI Configuration File
Back up the current CLI configuration file by entering the following command: