Cisco Cisco Packet Data Gateway (PDG)
• One PD prefix per PDN is supported; multiple PD-prefixes per PDN are not supported.
• P-GW and GGSN do not support local-based and RADIUS-based allocation of both DHCPv6 prefix
delegation and framed prefix delegation from the same pool. Hence the allocation is done from separate
pools. Framed prefix received in the access-accept message is not part of the delegated prefix range.
pools. Framed prefix received in the access-accept message is not part of the delegated prefix range.
Correction to GTPV2 Cause Source Being Incorrectly Set as S-GW
CSCux82063 - GTPv2 Cause Source incorrectly set as SGW of CC 64 in CSResp message
Applicable Products: SAEGW
Feature Changes
Consider the following scenario:
1
An SAEGW service is configured on the StarOS.
2
The S-GW ingress interface receives a Create Session Request with the Handover Indication Flag set.
3
The S-GW, being associated with the SAEGW service, checks with the SAEGW session manager for the
presence or absence of a session on the P-GW without forwarding the PDU to the P-GW.
presence or absence of a session on the P-GW without forwarding the PDU to the P-GW.
4
The session is not found and a Create Session Response is sent out with Cause Code 'Context Not Found'.
Even though the reject message is sent out by the S-GW, the message is logically rejected by the P-GW. Since
there is a configured SAEGW service, the StarOS does not need to originate the message from the P-GW to
save resources. External to the StarOS, the expectation is that the Cause Source IE (OI Flag) would indicate
the presence or absence of the session at the P-GW.
there is a configured SAEGW service, the StarOS does not need to originate the message from the P-GW to
save resources. External to the StarOS, the expectation is that the Cause Source IE (OI Flag) would indicate
the presence or absence of the session at the P-GW.
Previous Behavior: The Cause Source IE (OI Flag) was not set, and therefore indicated that the reject originated
from the S-GW.
from the S-GW.
New Behavior: The Cause Source IE is set and correctly indicates that the reject originates from the P-GW.
Customer Impact: This change was requested by a specific operator since their MME is expecting a set flag
if a session is absent at the P-GW. If other operators' MMEs expect different behavior, then the issue is with
the MME, according to the standards.
if a session is absent at the P-GW. If other operators' MMEs expect different behavior, then the issue is with
the MME, according to the standards.
ECS Rules Written for IP Protocol
CSCuy14480 - ECS rules written for IP protocol 132 are not hit
Applicable Products: GGSN, P-GW, SAE-GW
Feature Changes
Previous Behavior: Earlier, SCTP downlink traffic passed through the default bearer instead of dedicated
bearer, when the received packet was matched with the packet filter, which was configured in either of the
following ways:
bearer, when the received packet was matched with the packet filter, which was configured in either of the
following ways:
• Only source port or destination port was configured
• IP Address and port was configured
Release Change Reference, StarOS Release 19
324
SAEGW Changes in Release 19
Correction to GTPV2 Cause Source Being Incorrectly Set as S-GW