LTE Policy Configuration Mode Commands

The LTE Policy Configuration Mode is used to create and manage the LTE policies supporting ePDG, MME, S-GW, SAEGW, SGSN and HeNBGW configurations on the system.


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

IMPORTANT:

Available commands or keywords/variables vary based on platform type, product version, and installed license(s).

cause-code-group

Creates a new cause code group, or specifies an existing cause code group and enters the Cause Code Group Configuration Mode.

Product:

MME


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
cause-code-group group_name protocol s1ap
no cause-code-group group_name
no

Removes the specified cause code group with all related configuration from the LTE Policy.

group_name

Specify a name of a cause-code-group to create, modify, or remove. This name must be an alphanumeric string of 1 through 16 characters. Each new cause-code-group must have a unique name.

A maximum of 4 cause code groups can be defined across all services (MME+GPRS+SGSN).

protocol

Specifies the protocol for the cause code group being created/accessed. Options include:

  • S1-AP

Usage:

Use this command to create or modify a group of cause codes.

Entering this command results in a prompt, with the protocol ID included, similar to the following:

[context_name]hostname(s1ap-cause-code)#

Depending upon the protocol you have selected, the Cause Code Group configuration commands are defined in the

  • S1AP Cause Code Configuration Mode Commands chapter of this guide.

Example:

The following command creates an S1-AP cause code group named move-ue-to-idle.

cause-code-group move-ue-to-idle
protocol s1ap
congestion-action-profile

Creates an action profile for MME or ePDG critical, major and minor congestion thresholds. The profile defines the action to be taken when these thresholds are exceeded.

Product:

ePDG

HeNBGW

MME


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] congestion-action-profile profile_name
no

Removes the specified profile from the system.

profile_name

Specifies the name of the action profile. If the entered name does not refer to an existing profile, a new profile is created. profile_name is an alphanumeric string of 1 through 64 characters.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.


Usage:

Use this command to establish MME or ePDG action profiles to be associated with critical, major and minor congestion thresholds. This command is also used to remove an existing profile.

Note:

This command is part of a licensed feature and requires a proper license to function: MME Resiliency Bundle.

For information on setting the action to be taken within this profile, see the Congestion Action Profile Configuration Mode Commands chapter in this guide, and the Congestion Control chapter in the System Administration Guide.


Example:
The following command creates a major congestion action profile named mme_major_profile and moves to the Congestion Action Profile Configuration mode:
congestion-action-profile
mme_major_profile 
end

Exits the current configuration mode and returns to the Exec mode.

Product:

All


Privilege:

Security Administrator, Administrator


Syntax
end

Usage:

Use this command to return to the Exec mode.

exit

Exits the current mode and returns to the parent configuration mode.

Product:

All


Privilege:

Security Administrator, Administrator


Syntax
exit

Usage:

Use this command to return to the parent configuration mode.

foreign-plmn-guti-mgmt-db

Creates a new, or enters the existing Foreign PLMN GUTI management database.

Product:

MME


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
foreign-plmn-guti-mgmt-db db_name [ -noconfirm ]
no foreign-plmn-guti-mgmt-db db_name 
no

Remove the specified management database from the system.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.

db-name

Specifies the name of the management database. If the name does not refer to an existing database, a new database is created.

db_name is an alphanumeric string of 1 through 64 characters.


Usage:

Use this command to create a new, or enter the existing Foreign PLMN GUTI management database. This management database allows for the optional configuration of foreign PLMNs for which Attach Requests or TAU Requests containing a GUTI from such a PLMN can either be allowed or immediately rejected.

A maximum of four separate Foreign PLMN GUTI management databases can be configured.

Entering this command results in the following prompt:

[context_name]hostname(foreign-plmn-guti-mgmt-db)#

Global MME ID management database commands are defined in the LTE Foreign PLMN GUTI Management Database Configuration Mode Commands chapter.


Example:

The following command creates a Foreign PLMN GUTI management database named fguti-db1.

foreign-plmn-guti-mgmt-db fguti-db1 -noconfirm

henbgw mme-pool

Creates or configures a specified MME or MME pool to which the HeNB-GW is to communicate and enters the MME pool configuration mode.

Product:

HeNB-GW


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] henbgw
mme-pool pool_name [ -noconfirm ]
no

Removes an already configured MME or MME pool from the system.

pool_name

Specifies the name of the MME pool being created or accessed. If the pool name does not refer to an existing profile, a new pool is created. pool_name is an alphanumeric string of 1 through 63 characters.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.


Usage:

Use this command to enter the MME Pool Configuration Mode for an existing pool or for a newly defined MME pool. This command is also used to remove an existing MME pool.

IMPORTANT:

A maximum of eight MME pools are allowed per system.

Entering this command results in the following prompt:

[context_name]hostname(mme-pool)#

MME Pool Configuration Mode commands are defined in the MME Pool Configuration Mode Commands chapter.


Example:
The following command helps entering the MME Pool Configuration Mode for a new or existing profile named henb_mme_pool:
mme pool henb_mme_pool

henbgw overload-control

Configures HeNBGW overload control parameters.

Product:

HeNBGW


Privilege:

Administrator

Mode

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
henbgw  overload-control [ load-reduction-indicator
  percentage_value | ochl-guard-time minutes ]
default henbgw  overload-control [ load-reduction-indicator | ochl-guard-time ]  ]
default

Sets/Restores the default values assigned to HeNBGW overload control parameters. The default value of load Reduction indication is 99 percent.

load-reduction-indicator percentage_value

Designates the percentage of HeNBs to relay overload start message if traffic load Reduction indication IE is not present in the overload start message.

percentage_value is the percentage value, which is an integer between 1 and 99.

ochl-guard-time minutes

Designates the guard timeout value for sending overload stop messages if overload stop message is not received from MME to all the HeNBs in corresponding MME’s overload control HeNBs list.

minutes is the number of minutes, which is an integer between 0 and 2147483647.


Usage:

Use this command to configure HeNBGW overload control parameters.


Example:
The following command configures HeNBGW overload control parameter ochl-guard-time as 45 minutes:
henbgw overload-control
ochl-guard-time 45 
ho-restrict-list

Creates a handover (HO) restriction list or specifies an existing HO restriction list and enters the Handover Restriction List Configuration Mode.

Product:

MME

ePDG

SAEGW

S-GW


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] ho-restrict-list list_name [ -noconfirm ]
no

Removes the specified restriction list from the system.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.

list_name

Specifies the name of the HO restriction list. If the entered list name does not refer to an existing list, a new list is created. list_name is an alphanumeric string of 1 through 64 characters.


Usage:

Use this command to enter the Handover Restriction List Configuration Mode for an existing list or for a newly defined list. This command is also used to remove an existing list.

Entering this command results in the following prompt:

[context_name]hostname(ho-restrict-list)#

Handover Restriction List Configuration Mode commands are defined in the LTE Handover Restriction List Configuration Mode Commands chapter.


Example:
The following command enters the Handover Restriction List Configuration Mode for a new or existing list named ho_restricit_list1:
ho-restrict-list ho_restrict_list1
lte-emergency-profile

Creates an LTE emergency profile or specifies an existing emergency profile and enters the LTE Emergency Profile Configuration Mode.

Product:

MME

ePDG

SAEGW

S-GW


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] lte-emergency-profile profile_name [ -noconfirm ]
no

Removes an LTE emergency profile from the system.

profile_name

Specifies the name of the LTE emergency profile being created or accessed. If the profile name does not refer to an existing profile, a new profile is created. profile_name is an alphanumeric string of 1 through 64 characters.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.


Usage:

Use this command to enter the LTE Emergency Profile Configuration Mode for an existing profile or for a newly defined profile. This command is also used to remove an existing profile.

IMPORTANT:

A maximum of four LTE emergency profiles are allowed per system.

Entering this command results in the following prompt:

[context_name]hostname(lte-emergency-profile)#

LTE Emergency Profile Configuration Mode commands are defined in the LTE Emergency Profile Configuration Mode Commands chapter.


Example:
The following command enters the LTE Emergency Profile Configuration Mode for a new or existing profile named emergency_profile3:
lte-emergency-profile emergency_profile3
mme paging cache

Enable or disables caching of the MME’s paging and provides the operator configurable paging cache controls.

Product:

MME


Privilege:

Security Administrator, Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
mme paging cache { size cache_size | timeout time }
default mme paging cache { size | timeout }
default

Resets either the paging cache size or the paging cache timer to default settings.

size cache_size

cache_size: Enter an integer from 0 to 10000 to specify the maximum number of Tracking Area Code (TAC) entries to be cached.

Entering the ‘0’ value disables caching and should be followed by use of the mme paging cache clear command (in the Exec mode).

Default cache size = 5000 TAC entries per SessMgr.

timeout time

time: Enter an integer from 1 to 1440 to specify the number of minutes that each Tracking Area Code (TAC) entry remains valid.

A lower cache timeout helps to refresh the cache frequently and enables this functionality to quickly adapt to changes in the network. We recommend the timeout value be less than the expected eNodeB flap frequency; for example, if the eNodeBs connected to the MME are expected to disconnect and reconnect every 10 minutes (due to network issues), then the timeout configuration should be less than 10 minutes.

Default timeout = 5 minutes.


Usage:

Both size and timeout must be configured to enable paging cache optimization. The mme paging cache command must be entered twice, once for each parameter.


Example:
Set the paging cache timeout to match the eNodeB flap frequency of 10 minutes:
mme paging cache timeout 10
Set the paging cache size to disable caching:
mme paging cache size 0
end
mme paging cache clear { all | instance sessmgr_instance }
network-global-mme-id-mgmt-db

Creates a new, or enters the existing MME group ID management database.

Product:

MME

ePDG

SAEGW

S-GW

SGSN


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] network-global-mme-id-mgmt-db
no

Remove the global MME ID management database from the system.


Usage:

Use this command to create a new, or enter the existing MME group ID management database. The MME group ID management database is used to create associations between PLMN IDs and ranges of MME group IDs.

On the S4-SGSN, this command enables operators to create a MME group ID management database that can be associated with an SGSN service.

IMPORTANT:

Only one MME group ID management database can be created per system.

Entering this command results in the following prompt:

[context_name]hostname(network-global-mme-id-mgmt-db)#

Global MME ID management database commands are defined in the LTE Network Global MME ID Management Database Configuration Mode Commands chapter.

paging-map

Creates a paging map or specifies an existing paging map and enters the Paging Map Configuration Mode.

Product:

MME

ePDG


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] paging-map paging_map_name [ -noconfirm ]
no

Remove the paging map from the system.

paging_map_name

Specifies the name of the paging map being created or accessed. If the map name does not refer to an existing map, a new map is created. paging_map_name must be an alphanumeric string of 1 through 64 characters.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.


Usage:

Enter the Paging Map Configuration Mode for an existing or newly defined map. This command is also used to remove an existing map.

Entering this command results in the following prompt:

hostname(paging-map)#

Paging Map Configuration Mode commands are defined in the LTE Paging Map Configuration Mode Commands chapter.

Refer to the Heuristic and Intelligent Paging chapter in the MME Administration Guide for more information about Paging Maps.


Example:
The following command enters the existing Paging Map Configuration Mode (or creates it if it does not already exist) for the map named map1:
paging-map map1
paging-profile

Creates a paging profile or specifies an existing paging profile and enters the Paging Profile Configuration Mode.

Product:

MME

ePDG


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] paging-profile paging_profile_name [ -noconfirm ]
no

Remove the paging map from the system.

paging_profile_name

Specifies the name of the paging profile being created or accessed. If the profile name does not refer to an existing profile, a new profile is created. paging_profile_name must be an alphanumeric string of 1 through 64 characters.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.


Usage:

Enter the Paging Profile Configuration Mode for an existing or newly defined paging profile. This command is also used to remove an existing profile.

Entering this command results in the following prompt:

hostname(paging-profile)#

Paging Profile Configuration Mode commands are defined in the LTE Paging Profile Configuration Mode Commands chapter.

Refer to the Heuristic and Intelligent Paging chapter in the MME Administration Guide for more information about Paging Profiles.


Example:
The following command enters the existing Paging Profile Configuration Mode (or creates it if it does not already exist) for the profile named profile1:
paging-profile profile1
peer-map

Creates a peer map and enters the LTE Peer Map Configuration mode.

Product:

P-GW

SAEGW

S-GW


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
peer-map map_name [ -noconfirm ]no peer-map map_name
no

Removes the specified peer map from the LTE policy.

map_name

Specify a name of a peer map to create, modify, or remove. This name must be an alphanumeric string of 1 through 64 characters. Each new peer map must have a unique name.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.


Usage:

Use this command to create or modify a peer map.

Entering this command results in the following prompt:

[local]host_name(peer-map)#

LTE Peer Map Configuration Mode commands are defined in the LTE Peer Map Configuration Mode Commands chapter of this guide.


Example:
The following command creates a peer map named map5 and enters the LTE Peer Map Configuration mode:
peer-map map5
subscriber-map

Creates a subscriber map or specifies an existing subscriber map and enters the Subscriber Map Configuration Mode.

Product:

MME

ePDG

SAEGW

S-GW


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] subscriber-map map_name [ -noconfirm ]
no

Removes the specified subscriber map from the system.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.

map_name

Specifies the name of the subscriber map. If the map name does not refer to an existing map, a new map is created. map_name must be an alphanumeric string of 1 through 64 characters.


Usage:

Enter the Subscriber Map Configuration Mode for an existing or newly defined map. This command is also used to remove an existing map.

Entering this command results in the following prompt:

hostname(subscriber-map)#

Subscriber Map Configuration Mode commands are defined in the LTE Subscriber Map Configuration Mode Commands chapter.


Example:
The following command enters the existing Subscriber Map Configuration Mode (or creates it if it does not already exist) for the map named map1:
subscriber-map map1
tai-list-db

Creates or configures a list of Tracking Area Information (TAI). This list is called TAI List Database.

Product:

HeNB-GW


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] tai-list-db db_name [ -noconfirm ]
no

Removes the specified TAI list database from the system.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.

db_name

Specifies the name of the TAI list database. If the name does not refer to an existing database, a new database is created. db_name is an alphanumeric string of 1 through 64 characters.


Usage:

Enters the TAI List Database Configuration Mode for an existing or newly defined database. This command is also used to remove an existing database.

IMPORTANT:

Maximum of eight TAI List Database instances can be created in a system.

Entering this command results in the following prompt:

[context_name]hostname(tai-list-db)#

TAI List Database Configuration Mode commands are defined in the TAI List Database Configuration Mode Commands chapter.


Example:
The following command enters the existing TAI List Database configuration mode (or creates it if it does not already exist) for the database named tai_db1:
tai-list-db tai_db1
tai-mgmt-db

Creates a Tracking Area Identifier (TAI) Management Database or specifies an existing database and enters the TAI Management Database Configuration mode. On an S4-SGSN, this command is used as part of configuring S-GWs and their associated RAIs to bypass DNS resolution of RAI FQDN for obtaining the S-GW address.

Product:

MME

ePDG

SAEGW

S-GW

SGSN


Privilege:

Administrator


Mode:

Exec > Global Configuration > LTE Policy Configuration

configure > lte-policy

Entering the above command sequence results in the following prompt:

[local]host_name(lte-policy)#

Syntax
[ no ] tai-mgmt-db db_name [ -noconfirm ]
no

Removes the specified management database from the system.

-noconfirm

Executes the command without any additional prompt and confirmation from the user.

db_name

Specifies the name of the management database. If the name does not refer to an existing database, a new database is created. db_name is an alphanumeric string of 1 through 64 characters.


Usage:

Enter the TAI Management Database Configuration Mode for an existing or newly defined database. This command is also used to remove an existing database.

On the S4-SGSN, once you have created a new, or accessed an existing, TAI Management database, a TAI Management Object must be created or accessed and the S-GWs and their associated RAIs configured using the rai and sgw-address commands. Refer to the LTE TAI Object Configuration Mode chapter for details on these two commands.

Entering this command results in the following prompt:

[context_name]hostname(tai-mgmt-db)#

TAI Management Database Configuration Mode commands are defined in the TAI Management Database Configuration Mode Commands chapter.


Example:
The following command enters the existing TAI Management Database configuration mode (or creates it if it does not already exist) for the database named tai_db1:
tai-mgmt-db tai_db1