Cisco Cisco Packet Data Gateway (PDG)
SGSN Changes in Release 16
▀ SGSN Enhancements for 16.0
▄ Release Change Reference, StarOS Release 16
522
no equipment-identity-register { isdn E.164_num | point codept_code }]
[include-imsi | map-include-imsi]
[include-imsi | map-include-imsi]
end
Where:
include-imsi
keyword enables the inclusion of IMSI checking during the IMEI check procedure. By default
this function is not included.
map-include-imsi
keyword enables the inclusion of IMSI parameter in the CHECK_IMEI Request. By
default, IMSI is not included in the CHECK_IMEI Request.
no
included in the command phrase, disables the specified operation.
Performance Indicator Changes
show map-service
A new field has been added to the
show map-service
output to indicate if sending the IMSI in the
MAP_CHECK_IMEI message has been enabled in the SGSN configuration:
MAP CHECK IMEI MAP Include IMSI :
CSCug97812 - Lock Peer-Server Point/Process (PSP)
Feature Changes
SGSN Support for Peer-Server Blocking
The validity of SCTP redundancy has to be tested by simulating fail overs when new RNCs/STPs have to be
commissioned. Peer-Server Blocking support has been added to prevent any issues during commissioning of new
RNCs/STPs
commissioned. Peer-Server Blocking support has been added to prevent any issues during commissioning of new
RNCs/STPs
The Peer Server Blocking feature provides the following functionalities:
1. The SCTP association can be either brought up or down in order to test the redundancy of the same.
2. The PSPs can be brought down without removing the configuration.
3. The SGSN supports a new configuration command under the psp-instance to block/unblock peer endpoint and
2. The PSPs can be brought down without removing the configuration.
3. The SGSN supports a new configuration command under the psp-instance to block/unblock peer endpoint and
this configuration is pushed to the Link Manager to achieve peer-server blocking.
4. The SGSN sends a SCTP Shutdown to the remote endpoint and marks the endpoint as LOCKED when the PSP
is configured as blocked and if the PSP is in ESTABLISHED state.
5. The SGSN initiates a SCTP INIT when a blocked PSP is un-blocked and if the SGSN is a client and is asp-
associated.
6. The SGSN replies with an ABORT when the peer sends INIT in LOCKED state.
7. The SGSN marks the remote endpoint as LOCKED when the PSP is configured as blocked and if the PSP is in a
7. The SGSN marks the remote endpoint as LOCKED when the PSP is configured as blocked and if the PSP is in a
CLOSED state.
8. The PSP state is recovered in case of Link Manager death and no messages are initiated after recovery if the PSP
is in locked state.
Previous Behavior: Control for locking PSP was not supported.
New Behavior: The SGSN now supports control for bringing down and locking PSPs. A new CLI has been added for
supporting Peer-Server blocking.
supporting Peer-Server blocking.