Cisco Cisco Packet Data Gateway (PDG) Nota De Lançamento
eWAG Changes in Release 15.0
eWAG Feature Changes as of September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
187
eWAG Feature Changes as of September 30, 2013
This section provides information on eWAG feature changes in release 15.0.
Important:
For more information regarding features in this section, refer to the eWAG Administration Guide for
this release.
New eWAG Features
This section identifies new eWAG features available in release 15.0.
R-eWAG Support for GGSN-initiated UPC
R-eWAG now supports processing GGSN-initiated UPC requests. GGSN-initiated UPC requests will be accepted only
for QoS Update case. In GGSN-initiated UPC request for QoS update, QoS is updated for the R-eWAG session and
accept status is sent in UPC response. UPC requests with EUA update, PCO update, APN restriction update, TFT
update, and direct tunnel update will be rejected by the R-eWAG.
for QoS Update case. In GGSN-initiated UPC request for QoS update, QoS is updated for the R-eWAG session and
accept status is sent in UPC response. UPC requests with EUA update, PCO update, APN restriction update, TFT
update, and direct tunnel update will be rejected by the R-eWAG.
R-eWAG Support for Local Configuration of GGSN IP Addresses
R-eWAG now has the ability to locally select a GGSN. This would be used in case a DNS server is unavailable or
unreachable. A new CLI command is now available to locally configure GGSN IP address under the R-eWAG service.
unreachable. A new CLI command is now available to locally configure GGSN IP address under the R-eWAG service.
Previous Behavior: Hidden test mode CLI command
[ no ] ggsn-ip-address <ipv4_address>
was available
for this purpose.
New Behavior: Now new CLI command
[ no ] gtp peer-ip-address <ipv4_address>
can be used to locally
configure GGSN IP address under the R-eWAG service. This CLI command is available only for the eWAG mode. The
old CLI command
old CLI command
[ no ] ggsn-ip-address <ipv4_address>
is now removed for the eWAG mode.
R-eWAG Support for Alternate GGSN in Case Primary GGSN Rejects CPC
In case the DNS server returns more than one GGSN address for the given APN, and if CPC request to GGSN fails due
to GGSN being unreachable, then next GGSN address from the list of addresses will be tried. Note that next GGSN
addresses will also be tried in case GGSN rejects the CPC request due to one of the following reasons:
to GGSN being unreachable, then next GGSN address from the list of addresses will be tried. Note that next GGSN
addresses will also be tried in case GGSN rejects the CPC request due to one of the following reasons:
No resources available
All dynamic PDP addresses are occupied
No memory is available
Missing or unknown APN
System failure
Unknown PDP address or PDP type
All decode errors at peer like “Mandatory IE incorrect”, “Mandatory IE missing”, “Optional IE incorrect”, and
“Invalid message format”.