Cisco Cisco Packet Data Gateway (PDG)
Performance Indicator Changes
show apn
<apn_name>
| all
This command has been modified to display the following fields:
ppp keep alive period: 32 ppp mtu: 1500
ppp auth without pco for l2tp: Enabled
ppp auth without pco for l2tp: Disabled
ppp auth without pco for l2tp: Enabled
ppp auth without pco for l2tp: Disabled
show config verbose output
If the CLI command ppp l2tp allow-auth-without-pco is configured, the output of this command is modified
to display the following:
to display the following:
• ppp l2tp allow-auth-without-pco
If no ppp l2tp allow-auth-without-pco or default ppp l2tp allow-auth-without-pco or no configuration
is done, there is no change in the output of this show command.
is done, there is no change in the output of this show command.
show apn <apn_name>
This command displays the virtual-apn configuration based on pdp-type and pdp-type along with roaming-mode.
The output of this command has been modified to display the following fields:
The output of this command has been modified to display the following fields:
Virtual APN Configuration:
Preference Rule-Definition
Preference Rule-Definition
Selected-APN
1
PDP Type = ipv4 telenor.ipv4v6
2
PDP Type = ipv6 telenor.nat64
3
PDP Type = ipv4v6
Roaming mode = roaming telenor.nat64
Retaining Old IMEI Values
CSCuz67967 - Logging when GTPC TEID reuse with different IMEI in MBR
Applicable Products: P-GW, SAEGW
Feature Changes
For a PDN session, P-GW receives MBReq with IMEI value which is different from old IMEI value.
Old behavior: On receiving MBReq with different IMEI value, P-GW replaces old IMEI information with
the new IMEI value and start using the new IMEI information on all interfaces. This impacts the P-GW CDRs
generated for that PDN session. P-GW CDRs generated before the MBReq uses the old IMEI value and P-GW
CDRs generated after the MBReq uses the new IMEI value, which is wrong and has impact on billing and
revenue loss for the customer.
the new IMEI value and start using the new IMEI information on all interfaces. This impacts the P-GW CDRs
generated for that PDN session. P-GW CDRs generated before the MBReq uses the old IMEI value and P-GW
CDRs generated after the MBReq uses the new IMEI value, which is wrong and has impact on billing and
revenue loss for the customer.
New behavior: If, P-GW receives MBReq with IMEI value which is different from old IMEI value, P-GW
ignores the new IMEI value received as part of MBReq and retains the old IMEI information. Hence,
PGW-CDRs generated before or after MBReq now use the old IMEI value. As a result, there is no impact on
billing.
ignores the new IMEI value received as part of MBReq and retains the old IMEI information. Hence,
PGW-CDRs generated before or after MBReq now use the old IMEI value. As a result, there is no impact on
billing.
Release Change Reference, StarOS Release 19
261
P-GW Changes in Release 19
Retaining Old IMEI Values