Cisco Cisco Packet Data Gateway (PDG)
SAEGW Changes in Release 16
▀ SAEGW Enhancements for 16.1
▄ Release Change Reference, StarOS Release 16
400
The output of this command has been enhanced to display the total number of subscribers in the assumed positive state.
Session Stats:
S6b Assume Positive:
show subscribers sagew-only summary
The output of this command has been enhanced to display the total number of subscribers in the assumed positive state.
Total S6b Assume Positive:
show saegw-service statistics all
The output of this command has been enhanced to display the total number of subscribers in the assumed positive state.
Subscriber Total
Total S6b Assume Positive:
CSCun86828 - CBR - MBR collision causing MME to delete dedicated bearer
Feature Changes
CBR and MBR Collision Detection for Dedicated Bearers
The software has been enhanced to avoid aborting the existing Create Bearer Request. The Create Bearer Request
procedure is buffered until the time Modify Bearer Request procedure is over. The Create Bearer Response received
will be handled only after the Modify Bearer Request procedure is over.
procedure is buffered until the time Modify Bearer Request procedure is over. The Create Bearer Response received
will be handled only after the Modify Bearer Request procedure is over.
Previous Behavior: On ASR 5000 P-GW/SAEGW nodes, when the S5/S8 interface detected a collision between an
already initiated Create Bearer Request and a new incoming Modify Bearer Request, the Create Bearer Request was
aborted at the P-GW. This resulted in any later Create Bearer Response received from the MME/S-GW to be rejected.
As a result, the SAEGW/P-GW had one bearer less than the peer.
already initiated Create Bearer Request and a new incoming Modify Bearer Request, the Create Bearer Request was
aborted at the P-GW. This resulted in any later Create Bearer Response received from the MME/S-GW to be rejected.
As a result, the SAEGW/P-GW had one bearer less than the peer.
New Behavior: On ASR5000 P-GW/SAEGW nodes, when the S5/S8 interface detects a collision between an already
initiated Create Bearer Request and a new incoming Modify Bearer Request, the Create Bearer Request is not aborted at
P-GW. The Create Bearer Request procedure is buffered until the time Modify Bearer Request procedure is over. Create
Bearer Response received will be handled only after the Modify Bearer Request procedure is over. Normal T3/N3
Timer expiry behavior will continue for Create Bearer Request.
initiated Create Bearer Request and a new incoming Modify Bearer Request, the Create Bearer Request is not aborted at
P-GW. The Create Bearer Request procedure is buffered until the time Modify Bearer Request procedure is over. Create
Bearer Response received will be handled only after the Modify Bearer Request procedure is over. Normal T3/N3
Timer expiry behavior will continue for Create Bearer Request.