Cisco Cisco Packet Data Gateway (PDG) Nota De Lançamento
P-GW Changes in Release 15.0
P-GW Enhancements for September 30, 2013 ▀
Cisco ASR 5x00 Release Change Reference ▄
433
show session trace subscriber
The following field has been added to display subscriber session trace functionality type:
Trace Type
show subscribers full
Corrected Content: This section includes corrections to previously published content. The previous content stated that,
“Overcharging Protection functionality has been implemented as lab quality”, which is incorrect. Overcharging
Protection functionality has been implemented as deploy quality.
“Overcharging Protection functionality has been implemented as lab quality”, which is incorrect. Overcharging
Protection functionality has been implemented as deploy quality.
The following counters have been added to display overcharging protection for all subscribers:
in packet dropped overcharge protection
in bytes dropped overcharge protection
out packet dropped overcharge protection
out bytes dropped overcharge protection
Important:
When a session is in overcharge protection state, not all the downlink packets will be dropped;
however, downlink packets will be rate limited. Current configuration allows one downlink packet per minute towards
S-GW without charging it, if any downlink packets come to P-GW. P-GW will not generate any packets of its own.;
separate debug stats have been added for P-GW.
S-GW without charging it, if any downlink packets come to P-GW. P-GW will not generate any packets of its own.;
separate debug stats have been added for P-GW.
show subscribers pgw-only full all
The following field has been added to display the peer profile for this subscriber:
Network Peer Profile
The following field and counters have been added to display S-GW restoration:
Bearer State
in packet dropped sgw restoration state
in bytes dropped sgw restoration state
out packet dropped sgw restoration state
out bytes dropped sgw restoration state
Corrected Content: This section includes corrections to previously published content. The previous content stated that,
“Overcharging Protection functionality has been implemented as lab quality”, which is incorrect. Overcharging
Protection functionality has been implemented as deploy quality.
“Overcharging Protection functionality has been implemented as lab quality”, which is incorrect. Overcharging
Protection functionality has been implemented as deploy quality.
The following field and counters have been added to display overcharging protection:
Bearer State
in packet dropped overcharge protection
in bytes dropped overcharge protection
out packet dropped overcharge protection
out bytes dropped overcharge protection
The following fields and counters have been added to display PCRF authorized QoS: