Cisco Cisco Packet Data Gateway (PDG) Nota Di Rilascio
System Changes in Release 15.0
System and Platform Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
603
By default, the system is configured to prompt all administrative users with a confirmation prior to executing certain
commands. This functionality serves two purposes:
commands. This functionality serves two purposes:
Helps ensure that you do not execute an unwanted configuration change.
Indicates potential misspellings of names during configuration. The first time you configure an element name
(context, subscribers, services, etc.), the prompt is displayed. The prompt is not displayed for subsequent
entries of the name. Therefore, if you see the confirmation prompt after entering the name of a previously
configured element, it is likely that you misspelled the name.
entries of the name. Therefore, if you see the confirmation prompt after entering the name of a previously
configured element, it is likely that you misspelled the name.
You can control CLI autoconfirmation at the following levels:
Specific administrative user sessions: To enable or disable autoconfirmation, use the [no] autoconfirm
commands while in the Exec Mode.
All Future Sessions: To disable or re-enable autoconfirmation for all future sessions, use the
[no]autoconfirm
commands while in the Global Configuration Mode.
For specific commands: Disable autoconfirmation for various commands that support the
-noconfirm
keyword, such as the save configuration or card reboot commands.
Configurable Subscriber State Management Audit Process (ICSR)
A new audit command and keywords in Context Configuration mode allow an operator to specify the start time and
periodicity for generating Interchassis Session Recovery (ICSR) Service Redundancy Protocol (SRP) audit statistics.
This audit ensures that two ICSR peers are in synch and identifies any discrepancies prior to scheduled or unscheduled
switchover events.
periodicity for generating Interchassis Session Recovery (ICSR) Service Redundancy Protocol (SRP) audit statistics.
This audit ensures that two ICSR peers are in synch and identifies any discrepancies prior to scheduled or unscheduled
switchover events.
Demux Functionality on MIO/UMIO (ASR 5500)
This feature allows an MIO/UMIO card to host all the demux tasks on StarOS. Previously one DPC in the system could
be reserved as a demux card where none of the session components directly related to subscribers are running. This
feature frees session subsystem resources to increase system performance and throughput.
be reserved as a demux card where none of the session components directly related to subscribers are running. This
feature frees session subsystem resources to increase system performance and throughput.
This feature is disabled by default and can be enabled via the Global Configuration mode require demux card
command which has been modified for this purpose.
command which has been modified for this purpose.
The following restrictions apply when enabling an MIO/UMIO as a demux card:
The require demux management-card command must be configured before any service or contexts have been
created on the system. The command will not execute after a mode of operation has been selected for the
chassis.
chassis.
Only the following services currently support the designation of an MIO/UMIO card for demux functions:
GGSN, SGW, PGW, HA and SAE-GW.
Ex-GW, L2TP, MME, NEMO and SGSN are not supported.
After the ASR 5500 has booted with demux functions running on an MIO/UMIO, you cannot configure non-
supported services. A maximum of eight Demux Managers are supported. Any attempt to add more than eight
Demux Managers will be blocked.
Demux Managers will be blocked.
Service/products requiring a large number of VPN Managers, VRFs and/or Demux Managers must not enable
demux functions on an MIO.
With demux functions running on an MIO, the ASR 5500 supports a maximum of 10 contexts, 15 interfaces per
context, with a maximum of 64 interfaces and 250 VRFs per system.
To support this feature session recovery must also be enabled via the Global Configuration mode require session
recovery command.
recovery command.