Cisco Cisco Mobility Unified Reporting Release Note

New Feature Summary

Generally Available 04-30-2013

1-90

GTP-U Data Forwarding Changes for IPSec

Sessmgrs are now informed of IPSec tunnels to peers.

GTP-U IPSec Peer Updates to sessmgr

gtpumgr now receives IPSec tunnel notifications from IPSec. gtpumgr now updates all
sessmgrs with NPU flow information for the tunnel that is received from IPSec.

gtpumgr also notifies all sessmgrs of peer info. so that when any bearer setups for that peer,
corresponding IPSec tunnel info. is used for data forwarding.

GTP-U IPSec Tunnel Create and Status Handling

If IPSec is enabled and a new peer is detected, a new IPSec tunnel is now initiated.

GTP-U Echoes Sent through IPSec Tunnel for a Peer Once the IPSec
Tunnel to the Peer is Set Up

This functionality has been implemented.

Gtpumgr Restart Handling

With IPSec tunnels, if gtpumgr restarts, the IPSec tunnel info is now synced up with the
IPSec subsystem and sessmgr.

Gy: Added CHANGE_IN_SERVING_NODE Trigger Type

CHANGE_IN_SERVING_NODE trigger is an extension to the CHANGE_IN_SGSN
trigger. However, for the purpose of backward compatibility, both triggers are retained. The
P-GW sends them in the following manner.

●

If OCS does not provide any trigger:

●

SERVING_NODE AND SGSN is configured on the CLI, system sends
SERVING_NODE_CHANGE.

●

If one of them is configured, that one will be sent.

●

If OCS provides SERVING_NODE and SGSN, then CHANGE_IN_SERVING_NODE
would be sent.

●

If OCS provides:

●

SGSN alone (older OCS), then the current behavior of sending
CHANGE_IN_SGSN_IP_ADDRESS trigger is retained.

●

SERVING_NODE alone (newer OCS), then the new trigger
CHANGE_IN_SERVING_NODE would be sent.

Gy: [GTP] Support for Generating SERVING_ NODE_CHANGE Trigger

This functionality has been implemented.