Cisco Cisco Packet Data Gateway (PDG)
GGSN Changes in Release 16
▀ GGSN Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
160
With this requirement, bulkstat for GGSN are proposed in system schema
ggsn-activedata: defines the current number of GGSN sessions actively transmitting and receiving data packets.
This statistic is updated once an hour and is defined as having sent and/or received at least one data packet
within the last 60 seconds of the update time
within the last 60 seconds of the update time
CSCug70293 - PCO for UE Notification - GGSN Support
Feature Changes
PCO for UE Notification
The CLI for this feature already exists in support for P-GW and now the same is supported for GGSN as well.
Previous Behavior: Earlier no custom PCO values were configurable under the APN configuration for GGSN.
New Behavior: Custom PCO values can now be configured for the UE notifications to be sent for GGSN, too.
Customer Impact: Customized PCO option for UE notification can be sent for GGSN product as well with the
existing CLI options under the APN configuration.
existing CLI options under the APN configuration.
CSCuh28410 - GTP-U UDP Bundle
Feature Changes
GTP-U UDP Bundle
Currently, for forwarding GTP-U data packets, standard UDP port (2152) as source and destination port are used for
outgoing GTP-U packet. This creates hardship to balance traffic properly over the LAG interfaces between the different
L2/L3 elements in the network. Some routers use source UDP port to do load balancing of packets towards destination.
outgoing GTP-U packet. This creates hardship to balance traffic properly over the LAG interfaces between the different
L2/L3 elements in the network. Some routers use source UDP port to do load balancing of packets towards destination.
As part of this feature, behavior is changed so that source port outgoing GTP-U packet is different for each SESSMGR.
The destination port should remain as 2152, as per protocol.
The destination port should remain as 2152, as per protocol.
The usage of non-standard source port number is permitted, as per section 4.4.2 of 3GPP TS 29.281. This feature does
not require deviation from any GTP-U protocol aspects as defined in 3GPP TS 29.281.
not require deviation from any GTP-U protocol aspects as defined in 3GPP TS 29.281.
A new CLI is added in GTP-U Service configuration to enable this behavior. By default, standard port 2152 is used as
source port.
source port.
Customer Impact: Helps in doing effective load balancing of data traffic over LAG interfaces on some routers.
Command Changes
source-port
This new command configures GTP-U data packet source port related parameters.
configure
context context_name