- GGSN Service Configuration Mode Commands
- Global Configuration Mode Commands (A-K)
- Global Configuration Mode Commands (L-S)
- Global Configuration Mode Commands (T-threshold phspc)
- Global Configuration Mode Commands (threshold poll commands A - N)
- Global Configuration Mode Commands (threshold poll commands O - Z)
- Global Configuration Mode Commands (threshold ppp - url-blacklisting)
- GPRS Service Configuration Mode Commands
- GRE Tunnel Interface Configuration Mode Commands
- Gs Service Configuration Mode Commands
- GT-Format1 Configuration Mode Commands
- GT-Format2 Configuration Mode Commands
- GT-Format3 Configuration Mode Commands
- GT-Format4 Configuration Mode Commands
- GTPC Load Control Profile Configuration Mode Commands
- GTPC Overload Control Profile Configuration Mode Commands
- GTPP Server Group Configuration Mode Commands
- GTP-U Service Configuration Mode Commands
- HA Proxy DNS Configuration Mode Commands
- HA Service Configuration Mode Commands
- HD Storage Policy Configuration Mode Commands
- HeNB-GW Access Service Configuration Mode Commands
- HeNBGW Qci Dscp Mapping Table Configuration Mode Commands
- HeNB-GW Network Service Configuration Mode Commands
- HLR Configuration Mode Commands
- HNB-GW Global Configuration Mode Commands
- HNB-GW Service Configuration Mode Commands
- HNB-CS Network Configuration Mode Commands
- HNB-PS Network Configuration Mode Commands
- HNB-RN PLMN Configuration Mode Commands
- HSGW Service Configuration Mode Commands
- HSGW Service RoHC Configuration Mode Commands
- HSS Peer Service Configuration Mode Commands
- Index
Command Line Interface Reference, Modes G - H, StarOS Release 21
Bias-Free Language
The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
- Updated:
- October 27, 2016
Chapter: Global Configuration Mode Commands (threshold ppp - url-blacklisting)
- threshold ppp-setup-fail-rate
- threshold route-service bgp-routes
- threshold route-service vrf-framed-routes
- threshold route-service vrf-total-routes
- threshold rp-setup-fail-rate
- threshold sess-flow-count
- threshold storage-utilization
- threshold subscriber active
- threshold subscriber total
- threshold system-capacity
- threshold total-asngw-sessions
- threshold total-ggsn-sessions
- threshold total-gprs-pdp-sessions
- threshold total-gprs-sessions
- threshold total-ha-sessions
- threshold total-hnbgw-hnb-sessions
- threshold total-hnbgw-iu-sessions
- threshold total-hnbgw-ue-sessions
- threshold total-hsgw-sessions
- threshold total-lma-sessions
- threshold total-lns-sessions
- threshold total-mme-sessions
- threshold total-pdsn-sessions
- threshold total-pgw-sessions
- threshold total-saegw-sessions
- threshold total-sgsn-pdp-sessions
- threshold total-sgsn-sessions
- threshold total-sgw-sessions
- throttling-override-policy
- timestamps
- traffic shape
- transaction-rate bucket-interval
- transaction-rate nw-initiated-setup-teardown-events qci
- unexpected-scenario session drop-call
- upgrade limit
- url-blacklisting database
- wsg-lookup
Global Configuration
Mode Commands (threshold ppp - url-blacklisting)
The Global Configuration Mode is used to configure basic system-wide parameters.
Mode
This section includes the commands threshold ppp-setup-fail-rate through url-blacklisting database.
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
- threshold ppp-setup-fail-rate
- threshold route-service bgp-routes
- threshold route-service vrf-framed-routes
- threshold route-service vrf-total-routes
- threshold rp-setup-fail-rate
- threshold sess-flow-count
- threshold storage-utilization
- threshold subscriber active
- threshold subscriber total
- threshold system-capacity
- threshold total-asngw-sessions
- threshold total-ggsn-sessions
- threshold total-gprs-pdp-sessions
- threshold total-gprs-sessions
- threshold total-ha-sessions
- threshold total-hnbgw-hnb-sessions
- threshold total-hnbgw-iu-sessions
- threshold total-hnbgw-ue-sessions
- threshold total-hsgw-sessions
- threshold total-lma-sessions
- threshold total-lns-sessions
- threshold total-mme-sessions
- threshold total-pdsn-sessions
- threshold total-pgw-sessions
- threshold total-saegw-sessions
- threshold total-sgsn-pdp-sessions
- threshold total-sgsn-sessions
- threshold total-sgw-sessions
- throttling-override-policy
- timestamps
- traffic shape
- transaction-rate bucket-interval
- transaction-rate nw-initiated-setup-teardown-events qci
- unexpected-scenario session drop-call
- upgrade limit
- url-blacklisting database
- wsg-lookup
threshold ppp-setup-fail-rate
Configures alarm or alert thresholds for the percentage of point-to-point protocol (PPP) setup failures.
Product
PDSN
GGSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold ppp-setup-fail-rate high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold rate percentage for PPP setup failures experienced by the system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold rate percentage for PPP setup failures experienced by the system that maintains a previously generated alarm condition. If the number of setup failures falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
PPP setup failure rate thresholds generate alerts or alarms based on the rate of call setup failures experienced by the system during the specified polling interval. The failure rate is the percentage of failures as determined by number of PPP setup failures divided by the total number of PPP sessions initiated.
-
Enter condition: Actual number of call setup failures is greater than or equal to the high threshold.
-
Clear condition: Actual number of call setup failures is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold ppp-setup-fail-rate 50 clear 45
threshold route-service bgp-routes
Configures alarm or alert thresholds for the percentage of BGP routes.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold route-service bgp-routes high_thresh [ clear low_thresh ]
bgp-routes
Specifies the threshold for percentage of maximum bgp routes per context. It is an integer from 0 through 100.
- high_thresh
Specifies the high threshold rate percentage for maximum BGP routes per context that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 through 100. A value of 0 disables the threshold. The default value is 0.
- clear low_thresh
Specifies the low threshold rate percentage for BGP routes per context that maintains a previously generated alarm condition. If the number of BPG routes falls beneath the low threshold within the polling interval, a clear alarm will be generated. low_thresh is an integer from 0 through 100. A value of 0 disables the threshold. The default value is 0.
For more information on the maximum route value per context, refer to Engineering Rules in the System Administration Guide.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Use this command to configure a threshold in percentage of maximum BGP routes allowed. If the percentage of the number of BGP routes in a context reaches high_thresh, a notification is generated. Optionally, if the threshold subsystem is configured in 'alarm' mode, a Threshold_Clear notification is generated when the percentage of the number of BGP routes in a context goes below low_thresh. The maximum number of BGP routes is also sent by BGP task when getting the statistics.
-
Enter condition: Actual number of BGP routes is greater than the high threshold.
-
Clear condition: Actual number BGP routes is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold route-service bgp-routes 50 clear 45
threshold route-service vrf-framed-routes
Configures alarm or alert thresholds for the percentage of VRF framed routes.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold route-service vrf-framed-routes high_thresh [ clear low_thresh ] [ context context_name vrf vrf_name ]
vrf-framed-routes
Specifies the threshold for percentage of VRF framed routes per VRF. It is an integer from 0 through 100.
- high_thresh
Specifies the high threshold rate percentage for VRF framed routes per VRF that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 through 100. A value of 0 disables the threshold. The default value is 0.
- clear
low_thresh
Configures the alarm clear threshold. It is an integer from 0 through 100. The default value is 0.
- context
context_name
Configures the context to apply vrf-framed-routes threshold.
- vrf vrf_name
Configures the VRF to apply vrf-framed-routes threshold.
For more information on the maximum route value per context, refer to Engineering Rules in the System Administration Guide.
When the root level version of the threshold route-service command is issued without context and vrf information, the framed routes threshold value is configured for every VRF in the system. When the vrf-framed-routes command is issued for a specific context and VRF name, then the threshold value is configured only for that context and VRF. Any previously configured root level or VRF specific threshold value will be overwritten. The threshold values are set as a percentage of the ip maximum routes for the VRF. If ip maximum routes for a VRF is not configured, the default value is the maximum routes per context. If the threshold values in the above CLI command is set to 0, then the respective threshold configuration is removed.
Usage Guidelines
Use this command to configure a threshold in percentage of the maximum VRF framed routes. If the percentage of the number VRF framed routes reaches high_thresh, a notification is generated. Optionally, if the threshold subsystem is configured in 'alarm' mode, a Threshold_Clear notification is generated when the percentage of the number of VRF framed routes s in a context goes below low_thresh.
-
Enter condition: Actual number of VRF framed routes is greater than the high threshold.
-
Clear condition: Actual number of VRF framed routes is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold route-service vrf-framed-routes 70 clear 40
threshold route-service vrf-framed-routes 30 clear 20 context egress1 vrf vrf1
threshold route-service vrf-total-routes
Configures alarm or alert thresholds for the count of VRF total routes.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold route-service vrf-total-routes high_thresh [ clear low_thresh ] [ context context_name vrf vrf_name ]
vrf-total-routes
Specifies the number of VRF total routes threshold value per VRF. It is an integer from 0 through 65536.
- high_thresh
Specifies the high threshold count of total routes per VRF that must be met or exceeded within the polling interval to generate an alert or alarm. high_thresh is an integer from 0 through 65536. A value of 0 disables the threshold. The default value is 0.
- clear
low_thresh
Configures the alarms clear threshold. It is an integer from 0 through 65536. The default is 0.
- context
context_name
Configures the context to apply vrf-total-routes threshold.
- vrf vrf_name
Configures the VRF to apply vrf-total-routes threshold.
For more information on the maximum route value per context, refer to Engineering Rules in the System Administration Guide.
When the root level version of the threshold-route-service command is issued without context and vrf information, the total routes threshold value is configured for every VRF in the system. When the vrf-total-routes command is issued for a specific context and VRF name, the threshold value is configured only for that context and VRF. Any previously configured root level or VRF specific threshold value will be overwritten. The threshold values are set as the total count of the routes in the VRF which includes pool routes, interface routes, static routes, dynamic routes and framed routes. If the threshold values in the above CLI command is set to 0, then the respective threshold configuration is removed.
Usage Guidelines
Use this command to configure a threshold in number of the VRF total routes. If the count of VRF total routes in a context reaches high_thresh, a notification is generated. Optionally, if the threshold subsystem is configured in 'alarm' mode, a Threshold_Clear notification is generated when count of VRF total routes in a context goes below low_thresh.
-
Enter condition: Actual number of VRF total routes is greater than the high threshold.
-
Clear condition: Actual number of VRF total routes is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold route-service vrf-total-routes 3000 clear 2800
threshold route-service vrf-total-routes 1500 clear 800 context egress1 vrf vrf1
threshold rp-setup-fail-rate
Configures alarm or alert thresholds for the percentage of RAN PDSN (RP) setup failures.
Product
PDSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold rp-setup-fail-rate high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold rate percentage for RP setup failures experienced by the system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold rate percentage for RP setup failures experienced by the system that maintains a previously generated alarm condition. If the number of setup failures falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
RP setup failure rate thresholds generate alerts or alarms based on the rate of call setup failures experienced by the system during the specified polling interval. The failure rate is the percentage of failures as determined by number of Registration Request Messages rejected divided by the total number of Registration Request Messages received.
-
Enter condition: Actual number of call setup failures is greater than or equal to the high threshold.
-
Clear condition: Actual number of call setup failures is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold rp-setup-fail-rate 50 clear 45
threshold sess-flow-count
Configures alarm or alert thresholds for the percentage of session manager flow count.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold sess-flow-count flow_count_thresh [ clear clear_thresh ]
flow_count_percent
Default: 90
Specifies the high threshold rate percentage for session manager flow count to generate an alert or alarm.
flow_count_thresh is an integer from 1 through 100.
clear clear_thresh
Specifies the low threshold rate percentage for session manager flow count. If the number of session manager flow count falls beneath the low threshold, a clear alarm will be generated.
clear_thresh is an integer from 1 through 100. The value chosen for the clear_thresh must always be lesser than the flow_count_thresh.
Usage Guidelines
Use this command to configure thresholds for monitoring the session flow count.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold sess-flow-count 50 clear 45
threshold storage-utilization
Configures alarm or alert thresholds for the percentage of management card flash memory utilization.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold storage-utilization high_thresh [ clear low_thresh ]
high_thresh
Default: 90
Specifies the high threshold storage utilization percentage that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 90
Specifies the low threshold storage utilization percentage that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Flash memory utilization thresholds generate alerts or alarms based on the utilization percentage of storage available to the system.
-
Enter condition: Actual percentage storage utilization is greater than or equal to the high threshold.
-
Clear condition: Actual percentage storage utilization is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold storage-utilization 85
threshold subscriber active
Configures alarm or alert thresholds for the number of active subscribers in the system.
Product
PDSN
GGSN
SGSN
HA
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold subscriber active high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of active subscriber sessions facilitated by the system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of active subscriber sessions facilitated by the system that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Active subscriber thresholds generate alerts or alarms based on the total number of active subscriber sessions facilitated by the system during the specified polling interval.
-
Enter condition: Actual total number of active subscriber sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of active subscriber sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold subscriber active 150000 clear 100000
threshold subscriber total
Configures alarm or alert thresholds for the total number of active and inactive subscribers in the system.
Product
PDSN
GGSN
HA
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold subscriber total high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of subscriber sessions (active and dormant) facilitated by the system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of subscriber sessions (active and dormant) facilitated by the system that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Total subscriber thresholds generate alerts or alarms based on the total number of subscriber sessions (active and dormant) facilitated by the system during the specified polling interval.
-
Enter condition: Actual total number of subscriber sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of subscriber sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold subscriber total 450000 clear 250000
threshold system-capacity
Configures alarm or alert thresholds based on the percentage of current system capacity.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold system high_thresh [ clear low_thresh ]
high_thresh
Default: 90
Specifies the high threshold system capacity percentage that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 90
Specifies the low threshold system capacity percentage that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 100. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Flash memory utilization thresholds generate alerts or alarms based on the system utilization.
-
Enter condition: Actual percentage of system capacity is greater than or equal to the high threshold.
-
Clear condition: Actual percentage of system capacity is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold system-capacity 95
threshold total-asngw-sessions
Configures alarm or alert thresholds for the total number of ASN-GW sessions across all the services in the system.
Product
ANS-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-asngw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold number of total ASN-GW sessions across all the sessions in the system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold number of total ASN-GW sessions that maintains a previously generated alarm condition. If the number of ASN-GW sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of ASN-GW sessions across all the services in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of ASN-GW sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of ASN-GW sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-asngw-sessions 10000
threshold total-ggsn-sessions
Configures alarm or alert thresholds for the total number of GGSN sessions across all the services in the system.
Product
GGSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-ggsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold number of total GGSN sessions across all the sessions in the system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold number of total GGSN sessions that maintains a previously generated alarm condition. If the number of GGSN sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of GGSN sessions across all the services in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of GGSN sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of GGSN sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-ggsn-sessions 10000
threshold total-gprs-pdp-sessions
Configures alarm or alert thresholds for the total number of PDP contexts per GPRS sessions in the system.
Product
SGSN
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-gprs-pdp-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of total PDP contexts per GPRS session for all GPRS services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of total PDP contexts per GPRS session for all GPRS services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 2000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of GPRS sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of PDP Contexts is greater than or equal to the high threshold.
-
Clear condition: Actual total number of PDP contexts is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-gprs-pdp-sessions 10000
threshold total-gprs-sessions
Configures alarm or alert thresholds for the total number of GPRS sessions in the system.
Product
SGSN
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-gprs-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of total GPRS sessions for all GPRS services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of total GPRS sessions for all GPRS services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 2000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of GPRS sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of GPRS sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of GPRS sessions is less than the low threshol.d
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-gprs-sessions 10000
threshold total-ha-sessions
Configures alarm or alert thresholds for the total number of Home Agent (HA) sessions across all services in the system.
Product
HA
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-ha-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of HA sessions for all HA services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of HA sessions for all HA services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of HA sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of HA sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of HA sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-ha-sessions 10000
threshold total-hnbgw-hnb-sessions
In Release 20 and later, HNBGW is not supported. This command must not be used for HNBGW in Release 20 and later. For more information, contact your Cisco account representative.
Configures alarm or alert thresholds for the total number of Home NodeB (HNB) sessions across all the HNB Gateway (HNB-GW) services in the system.
Product
HNBGW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-hnbgw-hnb-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold for the total number of HNB-HNB-GW sessions on IuH interfaces across all HNB-GW services on a system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold for the total number of HNB-HNB-GW sessions on IuH interfaces across all services on a system that maintains a previously generated alarm condition. If the number of HNB-HNB-GW sessions in a system falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 1000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Use this command to monitor and set alarms or alerts when the total number of HNB-HNB-GW sessions on IuH interface across all HNB-GW services in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of HNB-HNB-GW sessions on IuH interface is greater than the high threshold.
-
Clear condition: Actual total number of HNB-HNB-GW sessions on IuH interfaces is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll total-hnbgw-hnb-sessions command to configure the polling interval and the threshold monitoring hnbgw-service command to enable thresholding for this value.
To enable an SNMP trap for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWHnbSess command in this mode.
Examples
threshold total-hnbgw-hnb-sessions 10000
threshold total-hnbgw-iu-sessions
In Release 20 and later, HNBGW is not supported. This command must not be used for HNBGW in Release 20 and later. For more information, contact your Cisco account representative.
Configures alarm or alert thresholds for the total number of subscriber sessions towards the Core Networks (CN) across all HNBGW services over Iu interfaces (Iu-CS/Iu-PS interface) on a system.
Product
HNBGW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-hnbgw-iu-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold for the total number of subscriber sessions towards CN across all HNB-GW services on a system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 3000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold for the total number of subscriber sessions towards CN across all services on a system that maintains a previously generated alarm condition. If the number of subscriber sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 3000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Use this command to monitor and set alarms or alerts when the total number of subscriber sessions towards CN across all HNB-GW services in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of subscriber sessions across all HNB-GW service on a system is greater than the high threshold.
-
Clear condition: Actual total number of subscriber sessions across all HNB-GW service on a system is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll total-hnbgw-iu-sessions command to configure the polling interval and the threshold monitoring hnbgw-service command to enable thresholding for this value.
To enable an SNMP trap for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWIuSess command in this mode.
Examples
threshold total-hnbgw-iu-sessions 30000
threshold total-hnbgw-ue-sessions
In Release 20 and later, HNBGW is not supported. This command must not be used for HNBGW in Release 20 and later. For more information, contact your Cisco account representative.
Configures alarm or alert thresholds for the total number of UEs connected to an HNB-GW service across all the HNB-GW services in the system.
Product
HNBGW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-hnbgw-ue-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold for the total number of UEs connected across all HNB-GW services on a system that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold for the total number of UEs connected to HNB-GW service across all HNB-GW services that maintains a previously generated alarm condition. If the number of UE sessions across all the services in a system, falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Use this command to monitor and set alarms or alerts when the total number of UEs connected to HNB-GW service across all HNB-GW services in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of UEs connected to HNB-GW service across all HNB-GW services on a system is greater than the high threshold.
-
Clear condition: Actual total number of UEs connected to HNB-GW service across all HNB-GW services on a system is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll total-hnbgw-ue-sessions command to configure the polling interval and the threshold monitoring hnbgw-service command to enable thresholding for this value.
To enable an SNMP trap for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWUeSess command in this mode.
Examples
threshold total-hnbgw-ue-sessions 40000
threshold total-hsgw-sessions
Configures alarm or alert thresholds for the total number of HRPD Serving Gateway (HSGW) sessions across all services in the system.
Product
HSGW
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-hsgw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold for the number of HSGW sessions for all HSGW services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold for the number of HSGW sessions for all HSGW services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 2500000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of HSGW sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of HSGW sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of HSGW sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-hsgw-sessions 500000
threshold total-lma-sessions
Configures alarm or alert thresholds for the total number of Local Mobility Anchor (LMA) sessions across all services in the system.
Product
P-GW
SAEGW
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-lma-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of LMA sessions for all LMA services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 1500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of LMA sessions for all LMA services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 1500000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of LMA sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of LMA sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of LMA sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-lma-sessions 500000
threshold total-lns-sessions
Configures alarm or alert thresholds for the total number of L2TP Network Server (LNS) sessions in the system.
Product
PDSN
GGSN
HA
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-lns-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of total LNS sessions that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of total LNS sessions that maintains a previously generated alarm condition. If the number of LNS sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of LNS sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of LNS sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of LNS sessions is less than the low threshold
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-lns-sessions 10000
threshold total-mme-sessions
Configures alarm or alert thresholds for the total number of Mobility Management Entity (MME) sessions across all the MME services in the system.
Product
MME
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-mme-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold number of total MME sessions that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold number of total MME sessions that maintains a previously generated alarm condition. If the number of MME sessions, across all the services in a system, falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 2500000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Use this command to monitor and set alarms or alerts when the total number of MME sessions across all the MME services in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of MME sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of MME sessions is less than the low threshold
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll total-mme-sessions command to configure the polling interval and the threshold monitoring mme-service command to enable thresholding for this value.
Examples
threshold total-mme-sessions 10000
threshold total-pdsn-sessions
Configures alarm or alert thresholds for the total number of Packet Data Serving Node (PDSN) sessions in the system.
Product
PDSN
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-pdsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of total PDSN sessions that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 0 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of total PDSN sessions that maintains a previously generated alarm condition. If the number of PDSN sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 and 2500000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of PDSN sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of PDSN sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of PDSN sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-pdsn-sessions 10000
threshold total-pgw-sessions
Configures alarm or alert thresholds for the total number of Packet Data Network Gateway (P-GW) sessions across all services in the system.
Product
P-GW
SAEGW
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-pgw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of P-GW sessions for all P-GW services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 3000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of P-GW sessions for all P-GW services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 3000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of P-GW sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of P-GW sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of P-GW sessions is less than the low threshold
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-pgw-sessions 500000
threshold total-saegw-sessions
Configures alarm or alert thresholds for the total number of System Architecture Evolution Gateway (SAEGW) sessions across all services in the system.
Product
SAEGW
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-saegw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of SAEGW sessions for all SAEGW services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 3000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of SAEGW sessions for all SAEGW services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 3000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of SAEGW sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of SAEGW sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of SAEGW sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-saegw-sessions 500000
threshold total-sgsn-pdp-sessions
Configures alarm or alert thresholds for the total number of PDP contexts for all Serving GPRS Support Node (SGSN) sessions in the system.
Product
SGSN
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-sgsn-pdp-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of total PDP contexts per SGSN session for all SGSN services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of total PDP contexts per SGSN session for all SGSN services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 4000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of SGSN sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of PDP contexts is greater than or equal to the high threshold.
-
Clear condition: Actual total number of PDP contexts is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-sgsn-pdp-sessions 10000
threshold total-sgsn-sessions
Configures alarm or alert thresholds for the total number of SGSN sessions in the system.
Product
SGSN
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-sgsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of total SGSN sessions for all SGSN services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of total SGSN sessions for all SGSN services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 2000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of SGSN sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of SGSN sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of SGSN sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-sgsn-sessions 10000
threshold total-sgw-sessions
Configures alarm or alert thresholds for the total number of Serving Gateway (S-GW) sessions across all services in the system.
Product
S-GW
Privilege
Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
threshold total-sgw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold number of S-GW sessions for all S-GW services that must be met or exceeded within the polling interval to generate an alert or alarm.
high_thresh is an integer from 1 through 3000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold number of S-GW sessions for all S-GW services that maintains a previously generated alarm condition. If the number of sessions falls beneath the low threshold within the polling interval, a clear alarm will be generated.
low_thresh is an integer from 0 through 3000000. A value of 0 disables the threshold.
This value is ignored for the Alert model. In addition, if this value is not configured for the Alarm model, the system assumes it is identical to the high threshold.
Usage Guidelines
Monitor and set alarms or alerts when the total number of S-GW sessions in the system is equal to or greater than the set limit.
-
Enter condition: Actual total number of S-GW sessions is greater than or equal to the high threshold.
-
Clear condition: Actual total number of S-GW sessions is less than the low threshold.
If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll command to configure the polling interval and the threshold monitoring command to enable thresholding for this value.
Examples
threshold total-sgw-sessions 500000
throttling-override-policy
Creates a GTP-C Throttling Override Policy. Entering this command creates a Throttling Override Policy mode. Use this mode to configure the Throttling Override Policy that can be used at the GGSN/P-GW nodes to selectively bypass throttling for a configured message type or for the configured APN.
Product
GGSN
P-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
throttling-override-policy throttling-override-policy_name
throttling-override-policy
Creates a GTP-C throttling overrride policy.
throttling-override-policy_name is a throttling overrride policy name for the policy that can be used at the GGSN/P-GW nodes.
Usage Guidelines
Enter this command mode to configure the Throttling Override Policy that can be used at the GGSN/P-GW nodes to selectively bypass throttling for a configured message type or for the configured APN.
Examples
throttling-override-policy throttling-override-policy_name
timestamps
Enables or disables the generation of a timestamp in response to each commands entered. The timestamp does not appear in any logs as it is a CLI output only. This command affects all future CLI sessions. Use the timestamps command in the Exec Mode to change the behavior for the current CLI session only.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
timestamps no timestamps
no
Disables generation of timestamps for each command entered. When omitted, the output of a timestamp for each entered command is enabled.
Usage Guidelines
Enable the timestamps when logging a CLI session on a remote terminal such that each command will have a line of text indicating the time when the command was entered.
Examples
timestamps
no timestamps
traffic shape
Configures the maximum buffer limit for sessmgr and subscribers for use during traffic shaping.
Product
GGSN
P-GW
SAEGW
Traffic Shaping is a license-controlled feature. Contact your Cisco account or support representative for detailed licensing information.
Privilege
Administrator, Security Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
traffic shape max-buffer-size sessmgr MBs subscriber MBs default traffic shape max-buffer-size
default
Returns sessmgr and subscriber settings to their default values.
Default setting for the sessmgr is 10MB. Default setting for the subscriber is 1MB.
traffic
Allows configuration for data traffic.
shape
Allows configuration for traffic shaping.
max-buffer-size
Allows configuration of the maximum buffer size for the session manager and subscriber.
sessmgr
Specifies the maximum buffer limit for the session manager for use during traffic shaping.
Valid entries are from 1 to 100 MB.
The default is 10 MB.
The sessmgr value should be greater than the subscriber value.
 Caution | Standard size buffers (500, 2k, and 10k bytes) are used for buffering packets to avoid memory fragmentation. As a result, there may be additional memory overhead in the memory used for buffering. The buffer limit in the above configuration refers to actual effective bytes used to store packets. Use caution to use appropriate buffer limits, so that the system does not significantly affect the overall Session Manager memory requirement for sessions. |
subscriber
Specifies the maximum buffer limit for subscriber use during traffic shaping.
Valid entries are from 1 to 100 MB.
The default is 1 MB.
The subscriber value should be less than the sessmgr value.
 Note |
|
Usage Guidelines
Use this command to set the maximum memory buffer limit for session manager and subscriber use during traffic shaping.
Traffic shaping and policing must first be configured in APN Configuration Mode using the apn-ambr command before the traffic shape command can be used.
Examples
traffic shape max-buffer-size sessmgr 20 subscriber 2
transaction-rate bucket-interval
Enables operators to set the time interval used for gathering transaction rate Session Events per Second and N/w Initiated Setup/Teardown Events per Second key performance indicator (KPI) information.
Product
ePDG
P-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
transaction-rate bucket-intervaltime-interval
default transaction-rate bucket-interval
transaction-rate bucket-interval time_interval
Where bucket-interval is the time interval, in minutes, used for gathering transaction rate statistics. This setting must be an integer from 1 to 20 minutes. The default value is 2 minutes. If no entry is made for the bucket-interval, then the default value of 2 minutes is used.
default
Returns the bucket-interval setting to the default value of 2 minutes.
Usage Guidelines
Session Events Per Second (SEPS) KPIs measure the signaling load on the P-GW/ePDG. Network initiated setup/tear down KPIs are available to measure the event rate for VoLTE call setup and tear down. Together, these measurements assist operators in performing network dimensioning/planning for the P-GW/ePDG node.
The P-GW/ePDG contains 8 buckets for transaction rate statistics collection for both session events per second KPIs and N/w Initiated Setup/Tear down Events per Second KPIs. The buckets are based on a configurable bucket interval that is from 1 to 20 minutes in length. During the configured time interval, an average is computed and stored for the entire bucket interval.
After the first 8 bucket intervals have elapsed and statistics collected, the P-GW continues sequentially through the 8 bucket intervals and eventually overwrites the original 8 bucket-intervals with more recent data. In short, the 8 bucket intervals provide a running average for the last eight bucket-intervals for which KPIs have been computed. While the bucket-interval statistics are eventually overwritten with new values, all statistic totals are added to the historical statistics, which are not overwritten.
-
Configure the bucket-interval so that the bulk statistic sampling interval is an integer (from 1 to 8) multiple of the configured bucket-interval. This new integer multiple reflects the number of buckets with new information in a given sampling interval. For example:
-
If the bulk statistic sampling interval is 15, then the configured bucket interval should be 3 so that the bucket interval is an integer multiple (3*5=15) of the sampling interval. In this case, 5 indicates the number of buckets with new information in a given sampling interval.
-
Similarly, when the bulk statistic sampling interval is 16, then the bucket interval could be 2 (so that 2*8=16). In this example 8 is the number of buckets with new information in a given sampling interval.
-
-
The transaction rates statistics are lost if the sessmgr/demuxmgr restarts. Also the cumulative statistics accumulated to that point are also lost.
-
If the sessmgr/demuxmgr restarts in the middle of a bucket interval, the transaction rates stats collected to that point are lost.
To view transaction rate KPI information, use the show transaction-rate pgw-service command in Exec Mode.
Examples
transaction-rate bucket-interval 3
transaction-rate nw-initiated-setup-teardown-events qci
Enables operators to set the Quality of Class Identifier (QCI) value for use in tracking Network Initiated Setup/Tear down Events per Second key performance indicator (KPI) information.
Product
ePDG
P-GW
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
transaction-rate nw-initiated-setup-teardown-events qci qci_value default transaction-rate nw-initiated-setup-teardown-events qci no transaction-rate nw-initiated-setup-teardown-events qci qci_value
transaction-rate nw-initiated-setup-teardown-events qci qci_value
Specifies the Quality of Service Class Identifier (QCI) value for which nw-initiated-setup-teardown-events will be tracked. QCI values of 1-9, 65, 66, 69, 70, and 128 - 254 are supported. A maximum of 4 unique QCI settings can be configured. The default is for network-initiated setup/teardown events to be supported for all supported QCI values.
QCI values 65 and 66 are available for guaranteed bit rate (GBR) network initiated QCI values only.
QCI values 69 and 70 are available for non-GBR network initiated QCI values only.
default
Returns the setting to its default value. The default is for network-initiated setup/teardown events to be tracked for all supported QCI values.
no
Disables the collection of network-initiated setup/teardown events for the specified QCI value.
Usage Guidelines
Network initiated setup/tear down KPIs are available to measure the event rate for VoLTE call setup and tear down. These KPIs assist operators in performing network dimensioning/planning for the P-GW/ePDG node.
The P-GW/ePDG contains 8 buckets for transaction rate statistics collection for N/w Initiated Setup/Tear down Events per Second KPIs. The buckets are based on a configurable bucket interval that is from 1 to 20 minutes in length. During the configured time interval, an average is computed and stored for the entire bucket interval. Refer to the description of the transaction-rate bucket-interval command in Global Configuration Mode Commands chapter for details on configuring the bucket interval.
The transaction rates statistics are lost when the sessmgr/demux restarts.
Existing transaction-rate configuration settings can be viewed by using the show configuration command in Exec Mode.
To view network-initiated setup/tear down event statistics, use the show transaction-rate pgw-service command in Exec Mode.
To clear the transaction-rate statistics, use the clear transaction-rate pgw-service command in Exec Mode.
Examples
transaction-rate nw-initiated-setup-teardown-events qci 3
unexpected-scenario session drop-call
Configures behavior when an unexpected call processing scenario is encountered. Enabling this command sets call clearing logic that replaces the automatic generation of asserts and core dumps for an initial assert.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
unexpected-scenario session drop-call [ disable-core ]
default unexpected-scenario session drop-call
default
Disables call clearing logic for a graceful assert. This results in automatic core dump generation for unexpected scenarios resulting in control and data outage for the task instance until the core is fully generated.
[ disable-core ]
This option disables the automatic generation of core dumps when a call is dropped for a specific session.
Usage Guidelines
Use this command to enable call clearing logic that will minimize the automatic generation of asserts and core dumps during a specific call processing session that may lead to data outage and session manager recovery.
The call clearing logic is only applied to the first assert generated during a call processing session. When that assert occurs, a zero-second timer lets the current stack unwind to avoid reentrancy issues. The call is then dropped from all interfaces. This is considered to be a graceful assert.
A core dump is generated along with any application supplied debug info. The line number and file index of the ASSERT appears in the call-line; the current call-line is marked as being in "assert_hit" scenario.
With the disable-core option set, a core dump is not generated following a graceful assert.
An assert generated after a graceful assert for the same unexpected scenario will cause the call to be dropped and trigger an automatic core dump. Depending on the length of time required to generate the associated core dump, a session manager recovery may be initiated. This is a highly unlikely possibility.
The graceful assert call clearing logic can only be applied to call processing events, such as VoLTE. It cannot be used for ICSR-SRP scenarios.
Examples
The following command enables call clearing logic for graceful asserts of initial call processing failures:
unexpected-scenario session drop-call disable-core
upgrade limit
Configures upgrade session limits that trigger when the system may execute the software upgrade.
Product
All
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
upgrade limit [ time session_life ] [ usage session_num ]
upgrade limit
This command issued with no keywords sets all parameters to their defaults.
time session_life
Default: 120
Defines the maximum number of minutes that a session may exist on the system undergoing a software upgrade, before it is terminated by the system. As individual user sessions reach this lifetime limit, the system terminates the individual session(s). session_life must be an integer ranging from 1 through 1440.
usage session_num
Default: 100
This keyword defines a low threshold limit of sessions running either on a packet processing card or system-wide. When a software upgrade is invoked, this parameter applies to the entire system.
When the threshold is crossed (when the number of sessions on the packet processing card or system is less than this value), the remaining sessions on the card or system are terminated allowing the upgrade to begin. The remaining sessions on the packet processing card or system are terminated regardless of their session life. session_num must be an integer from 0 through 6000.
Usage Guidelines
Use this command to configure upgrade session limits that trigger the system to begin executing the software upgrade.
This command is not supported on all platforms.
Software Patch Upgrades are not supported in this release.
Examples
upgrade limit time 200 usage 50
url-blacklisting database
This command configures URL Blacklisting database directory parameters.
Product
CF
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
url-blacklisting database { directory path path | max-versions max_versions | override file file_name }
default url-blacklisting database { directory path | max-versions | override file }
default
Configures this command with the default settings.
directory path path
Specifies the path to the directory to be used for storing URL Blacklisting databases.
path must be an alphanumeric string of 1 through 255 characters.
Default: /flash/bl
max-versions max_versions
Specifies the maximum number of URL Blacklisting database versions to be maintained in the URL Blacklisting database directory path with the base file name specified by the URL Blacklisting database override file.
max_versions must be an integer from 0 through 3.
Default: 0
override file file_name
Specifies the URL Blacklisting database override file name.
file_name must be in name.extension format. For example, abc.bin. And, must be an alphanumeric string of 1 through 10 characters.
Default: optblk.bin
Usage Guidelines
Use this command to configure URL Blacklisting database directory parameters.
Examples
url-blacklisting database max-versions 3
wsg-lookup
Enters the WSG lookup priority list configuration mode for site-to-site tunnels.
Product
WSG
Privilege
Security Administrator, Administrator
Mode
Exec > Global Configuration
configure
Entering the above command sequence results in the following prompt:
[local]host_name(config)#
Syntax
Syntax Description
wsg-lookup
Usage Guidelines
Use this command to enter the WSG lookup priority list configuration mode for site-to-site tunnels.
Examples
wsg-lookup
Feedback