Cisco Cisco ASR 5000
Global Configuration Mode Commands (T-threshold phspc)
task facility imsimgr ▀
Command Line Interface Reference, StarOS Release 18 ▄
5577
Important:
max
is a boot-time configuration setting. It should be added in the configuration file before any
SGSN/MME related configuration is created or any IMSI Manager is started. Run-time (dynamic) configuration of this
parameter is stored but not effective until after the next reboot. Any attempt at dynamic configuration of this parameter
results in a display of the following error message:
parameter is stored but not effective until after the next reboot. Any attempt at dynamic configuration of this parameter
results in a display of the following error message:
IMSImgrs already started. So modify the config file and reboot the system with
updated config.
updated config.
required-sessmgr
SGSN only.
This keyword configures the required number of Session Manager instances at the IMSI Manager. By default,
this parameter is disabled to ensure backward compatibility.
This keyword configures the required number of Session Manager instances at the IMSI Manager. By default,
this parameter is disabled to ensure backward compatibility.
no_sess_mgrs
: The number of required Session Managers can be an integer value from “1” through “384”.
sessmgr-sessions-threshold
This option is used to configure the threshold high and low watermarks, in terms of percentage, for the
sessions per Session Manager. The actual session limits are derived based on the card type.
sessions per Session Manager. The actual session limits are derived based on the card type.
high-watermark high_value
: The high-watermark value can be a percentage value from “70” through
“100”. The default percentage value is “100”.
low-watermark low_value
: The low-watermark value can be a percentage value from “50” through
“100”. The default percentage value is “100”.
Usage
For the MME:
Typically, the
Typically, the
avoid-sessmgr-broadcast
and
sessmgr-sessions-threshold
keywords are available
for configuration but not used.
For the SGSN:
This command configures the number of Session Manager instances required at the IMSI Manager before
forwarding any calls from the Gb Manager or Link Manager, as well, it configures the high watermark and
low watermark threshold levels per Session Manager.
If the required number of Session Managers are configured through this command, once the Link Manager or
Gb Manager comes up, it sends a query to the IMSI Manager to verify if the IMSI Manager has learnt the
configured number of Session Manager instances. IMSI Manager readiness status is determined based on the
number of Session Manager instances present in the list maintained. Once the IMSI Manager has completed
learning about all the required number Session Manager instances, it informs the Link Manager and Gb
Manager. Runtime enabling and modification of Session Manager instance is disabled except disabling this
configuration. Disabling of this configuration does not affect the call forwarding to the IMSI Manager as the
default behavior is to always forward the calls to the IMSI Manager. This configuration is used to avoid the
session imbalance across Session Manager instances due to call forwarding to the same Session Manager
instance during or after re-load, if the IMSI Manager has learnt only few Session Manager instances. By
default, this feature is disabled and Gb Manager or Link Manager start forwarding calls immediately during
or after re-load to the IMSI Manager which in turn forwards the request to the available Session Manager
instances. It is recommended to have this configuration before re-load. This option is available only under a
SGSN license.
The high and low watermark limits allow the IMSI Manager to decide and select the Session Manager for
processing new calls and eliminate the chances of it receiving a “call reject” in instances where the Session
Manager has reached its maximum allowed session limits and the IMSI Manager is not aware of the same.
The IMSI Manager converts the high and low watermark percentage to the maximum session allowed for the
configured percentage based on the card type. It uses the calculated session values for both high and low
For the SGSN:
This command configures the number of Session Manager instances required at the IMSI Manager before
forwarding any calls from the Gb Manager or Link Manager, as well, it configures the high watermark and
low watermark threshold levels per Session Manager.
If the required number of Session Managers are configured through this command, once the Link Manager or
Gb Manager comes up, it sends a query to the IMSI Manager to verify if the IMSI Manager has learnt the
configured number of Session Manager instances. IMSI Manager readiness status is determined based on the
number of Session Manager instances present in the list maintained. Once the IMSI Manager has completed
learning about all the required number Session Manager instances, it informs the Link Manager and Gb
Manager. Runtime enabling and modification of Session Manager instance is disabled except disabling this
configuration. Disabling of this configuration does not affect the call forwarding to the IMSI Manager as the
default behavior is to always forward the calls to the IMSI Manager. This configuration is used to avoid the
session imbalance across Session Manager instances due to call forwarding to the same Session Manager
instance during or after re-load, if the IMSI Manager has learnt only few Session Manager instances. By
default, this feature is disabled and Gb Manager or Link Manager start forwarding calls immediately during
or after re-load to the IMSI Manager which in turn forwards the request to the available Session Manager
instances. It is recommended to have this configuration before re-load. This option is available only under a
SGSN license.
The high and low watermark limits allow the IMSI Manager to decide and select the Session Manager for
processing new calls and eliminate the chances of it receiving a “call reject” in instances where the Session
Manager has reached its maximum allowed session limits and the IMSI Manager is not aware of the same.
The IMSI Manager converts the high and low watermark percentage to the maximum session allowed for the
configured percentage based on the card type. It uses the calculated session values for both high and low