Cisco Cisco ASR 5000
SGSN Pooling
▀ Configuring the SGSN Pooling feature
▄ SGSN Administration Guide, StarOS Release 18
exit
SGSN Service Configuration
config
context <context_name>
sgsn-service <service_name>
nri length nri_length [ nri-value nri_value | null-nri-value null_nri_value non-
broadcast mcc mcc mnc mnc lac lac_id rac rac_id nri-value value ] default nrino nri
broadcast mcc mcc mnc mnc lac lac_id rac rac_id nri-value value ] default nrino nri
exit
To Configure a Default SGSN
This procedure is common to both 2G and 3G SGSN pooling configurations. The SGSN can be configured as a “default
SGSN” in the pool under the SGTP service in the Gn context. This configuration is to be performed only once to render
a SGSN as a “default SGSN".
SGSN” in the pool under the SGTP service in the Gn context. This configuration is to be performed only once to render
a SGSN as a “default SGSN".
config
context <context_name>
sgtp-service <service_name>
pool {default-sgsn | hop-counter count}
exit
Procedure to Configure a Default SGSN (S16/S3 interface)
The following CLI command under the eGTP Service Configuration mode is used to configure the default SGSN:
config
context <context_name>
egtp-service <service_name>
pool {default-sgsn | hop-counter count}
exit
The default SGSN receives inbound SGSN context request messages and forwards it to the correct SGSN in the pool
based on the NRI bits of the P-TMSI. If the incoming message EGTP_CONTEXT_REQ/ IDENTIFICATION_REQ has
the hop count IE, the default SGSN decrements the count by one and forwards it to the Old-SGSN. The hop count is not
over written even if it is configured. If the hop count IE is missing with incoming message then the then hop count
configured gets populated. If no value is configured the default value is chosen. The hop Counter prevents endless
relaying of context/identification request. Each relaying SGSN keeps decrementing the hop-counter value if received
from the peer-sgsn, otherwise the SGSN includes hop-counter IE. If default-sgsn receives request having hop counter
“0”, it does not relay the request.
based on the NRI bits of the P-TMSI. If the incoming message EGTP_CONTEXT_REQ/ IDENTIFICATION_REQ has
the hop count IE, the default SGSN decrements the count by one and forwards it to the Old-SGSN. The hop count is not
over written even if it is configured. If the hop count IE is missing with incoming message then the then hop count
configured gets populated. If no value is configured the default value is chosen. The hop Counter prevents endless
relaying of context/identification request. Each relaying SGSN keeps decrementing the hop-counter value if received
from the peer-sgsn, otherwise the SGSN includes hop-counter IE. If default-sgsn receives request having hop counter
“0”, it does not relay the request.
Procedure to Configure an Operator Policy
Step 1: