Cisco Cisco Packet Data Gateway (PDG) Veröffentlichungshinweis
System Changes in Release 15.0
▀ System and Platform Enhancements for September 30, 2013
▄ Cisco ASR 5x00 Release Change Reference
604
Important:
After enabling demux card and session recovery, you must save the configuration and reboot the
ASR 5500 to enable this feature.
Implementation of this feature assumes that CEPS (Call Events Per Second) and the number of subscribers will remain
constant, but the data rate will increase. This ensures that the CPU demand will not increase on the MIO.
constant, but the data rate will increase. This ensures that the CPU demand will not increase on the MIO.
Caution:
Enabling the Demux on MIO/UMIO feature changes resource allocations within the system. This
directly impacts an upgrade or downgrade between StarOS versions in ICSR configurations. Contact Cisco TAC for
procedural assistance prior to upgrading or downgrading your ICSR deployment.
procedural assistance prior to upgrading or downgrading your ICSR deployment.
Important:
Contact Cisco TAC for additional assistance when assessing the impact to system configurations
when enabling the Demux on MIO/UMIO feature.
Enabling Password Access to cli-test commands
A Security Administrator can set a plain-text or encrypted password for access to CLI test commands. The password
value is stored in /flash along with the boot configuration information. The show configuration and save configuration
commands will never output this value.
value is stored in /flash along with the boot configuration information. The show configuration and save configuration
commands will never output this value.
The Global Configuration mode command tech-support test-commands [encrypted] password <password> sets an
encrypted or plain-text password for access to CLI test-commands.
encrypted or plain-text password for access to CLI test-commands.
When a test-commands password is enabled, the Global Configuration mode command cli test-commands [encrypted]
password <password> requires the entry of the password keyword. If the encrypted keyword is specified, the
<password> argument is interpreted as an encrypted string containing the password value. If the encrypted keyword is
not specified, the <password> argument is interpreted as the actual plain text value
password <password> requires the entry of the password keyword. If the encrypted keyword is specified, the
<password> argument is interpreted as an encrypted string containing the password value. If the encrypted keyword is
not specified, the <password> argument is interpreted as the actual plain text value
Important:
If tech-support test-commands password is never configured, cli-test commands will
always fail. If the password keyword is not entered for cli test-commands, the user is prompted (no-echo) to
enter the password. Also, cli hidden must be enabled by a Security Administrator to access the CLI test-
commands.
enter the password. Also, cli hidden must be enabled by a Security Administrator to access the CLI test-
commands.
New Chassis ID Encryption Method
Beginning with this release, the chassis ID will be generated from an input chassis key using the SHA2-256 algorithm
followed by base36 encoding. The resulting 44-character chassis ID will be stored in the same chassisid file in flash.
followed by base36 encoding. The resulting 44-character chassis ID will be stored in the same chassisid file in flash.
Release 14 and Release 15 chassis IDs will be in different encryption formats. Release 15 will recognize a Release 14
chassis ID and consider it as valid. Upgrading from 14.x to 15.0 will not require changing the chassis ID or
configuration file
chassis ID and consider it as valid. Upgrading from 14.x to 15.0 will not require changing the chassis ID or
configuration file
However, if the chassis key is reset in Release 15 through the setup wizard or chassis-key CLI command, a new chassis
ID will be generated in Release 15 format (44 instead of 16 characters). Release14 builds will not recognize the 44-
character chassis ID. If the chassis is subsequently downgraded to Release 14, a new 16-character chassis ID will be
generated. To accommodate the old key format, you must save the configuration file in pre-v12.2 format before the
downgrade. If you attempt to load a v15 configuration file on the downgraded chassis, StarOS will not be able to
decrypt the password/secrets stored in the configuration file.
ID will be generated in Release 15 format (44 instead of 16 characters). Release14 builds will not recognize the 44-
character chassis ID. If the chassis is subsequently downgraded to Release 14, a new 16-character chassis ID will be
generated. To accommodate the old key format, you must save the configuration file in pre-v12.2 format before the
downgrade. If you attempt to load a v15 configuration file on the downgraded chassis, StarOS will not be able to
decrypt the password/secrets stored in the configuration file.
For additional information, refer to the System Administration Guide.
Selectable Password/Secrets Encryption Algorithm