Cisco Cisco Packet Data Gateway (PDG)

MME Changes in Release 17

▀ MME Enhancements for 17.0

▄ Release Change Reference, StarOS Release 17

306

Previous Behavior: The maximum number of retransmissions for Echo Requests was configured by

max-

retransmissions

configuration option.

New Behavior:

echo-max-retransmissions

is introduced explicitly for the configuration of echo max

retransmissions in both GTPC Service Configuration Mode.

Command Changes

gtpc echo-max-retransmissions

The

echo-max-retransmissions

keyword is now available in EGTP Service Configuration Mode. This keyword is

available to allow for the separate configuration of GTP echo retransmissions.

configure

context context_name

egtp-service egtp_service_name

gtpc echo-max-retransmissions number

default gtpc echo-max-retransmissions

end

Notes:

Important:

service_name

must be unique across all contexts.



echo-max-retransmissions

: Configures the maximum retries for GTP Echo requests. This option must be

an integer from 0 to 15. The default is 4. If

echo-max-retransmissions

configuration option is not

configured, then the

max-retransmissions

configuration will be used for maximum number of echo retries.

Performance Indicator Changes

show egtp-service [ all | name

service_name

]

The output of this command has been enhanced to show the configured number of GTPC echo max retransmissions.



GTPC Echo Max Retransmission

CSCum35622 - Ability to define same TAI in multiple TAI Lists

Feature Changes

Ability to define same TAI in multiple TAI Lists

Prior to 17.0, the MME could have a tracking area in only one tracking area list (TAI List). Consequently, the tracking
area list assigned to subscribers attaching from different TAIs will be same, even if the adjacency of these tracking areas
is not same. This results in MME getting TAUs even as subscribers moved to the adjacent area.