Cisco Cisco IOS Software Release 12.2(8)YW
8
Release Notes for Cisco 7000 Series Routers for Cisco IOS Release 12.2 YW
OL-1620-04
Important Notes
Important Notes
The following sections contain important notes about Cisco IOS Release 12.2 YW that can apply to the
Cisco 7000 family.
Cisco 7000 family.
New Implementations and Behavior Changes in Cisco IOS Release 12.2(8)YW1
The following sections describe new implementations and behavior changes since the last release of the
Cisco IOS GGSN software.
Cisco IOS GGSN software.
GTP Related Changes
The following new GTP related changes have been added to this release:
•
GGSN allows GTP v0 PDP context create requests over an existing GTP v1 PDP context and
vice-versa.
vice-versa.
•
GGSN drops update requests with a different version than the SGSN that currently owns the PDP
context.
context.
PPP Related Changes
The following PPP related changes have been added to this release:
•
In this release, GGSN supports the LCP ACFC option for GTP PPP, in which the header (0xFF03)
will be always stripped off for downlink PPP TPDUs. However, if the GGSN receives the first PPP
TPDU with 0xFF03 from the SGSN, it will not strip off 0xFF03 for downlink PPP TPDU.
will be always stripped off for downlink PPP TPDUs. However, if the GGSN receives the first PPP
TPDU with 0xFF03 from the SGSN, it will not strip off 0xFF03 for downlink PPP TPDU.
•
In previous releases, the Reordering IE was always not set or set to ‘0’ in the Create PDP Context
Response returned by a Cisco GGSN. With this release, in case of PPP PDP, it is always set. In case
of IP PDP, it depends on the QoS profile.
Response returned by a Cisco GGSN. With this release, in case of PPP PDP, it is always set. In case
of IP PDP, it depends on the QoS profile.
•
With this implementation on the GGSN, uplink TPDUs arriving at the GGSN that are in-sequence
are processed and routed. Out-of-sequence TPDUs are dropped. No packet buffering and reordering
will actually be done. Such sequencing is always performed on PPP PDP contexts or IP PDP
contexts that have the delivery order set in the R99 QoS profiles.
are processed and routed. Out-of-sequence TPDUs are dropped. No packet buffering and reordering
will actually be done. Such sequencing is always performed on PPP PDP contexts or IP PDP
contexts that have the delivery order set in the R99 QoS profiles.
•
Previously, when PPP-regeneration was used, a user might be connected to a different domain other
than the APN the user was connecting to. This is because when the protocol configuration option
(PCO) IE of a create PDP context request contained a composite username (for example,
user@domain), the GGSN would create a L2TP tunnel to this user to the domain specified in PCO
IE. The GGSN did not validate this domain against the APN sent out by the user. The GGSN also
selected an L2TP tunnel either using an APN name or the user-supplied domain name, and would
always prioritize the user-supplied domain-name over the APN name. Therefore, regardless of the
APN the user is connecting to, the GGSN would connect the user to the requested domain-name,
using the L2TP tunnel for that domain.
than the APN the user was connecting to. This is because when the protocol configuration option
(PCO) IE of a create PDP context request contained a composite username (for example,
user@domain), the GGSN would create a L2TP tunnel to this user to the domain specified in PCO
IE. The GGSN did not validate this domain against the APN sent out by the user. The GGSN also
selected an L2TP tunnel either using an APN name or the user-supplied domain name, and would
always prioritize the user-supplied domain-name over the APN name. Therefore, regardless of the
APN the user is connecting to, the GGSN would connect the user to the requested domain-name,
using the L2TP tunnel for that domain.