# Global Configuration Mode Commands (threshold ppp - url-blacklisting)

This section includes the commands threshold ppp-setup-fail-rate through url-blacklisting database.

The Global Configuration Mode is used to configure basic system-wide parameters.

IMPORTANT:

The commands or keywords/variables that are available are dependent on platform type, product version, and installed license(s).
threshold ppp-setup-fail-rate

Configures alarm or alert thresholds for the percentage of point-to-point protocol (PPP) setup failures.
Platform:

ASR 5000

ASR 5500
Product:

PDSN, GGSN
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for PPP setup failure rates based on the following rules:

- 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.
Example:
The following command configures a PPP setup failure rate high percentage threshold of 50 percent and a clear threshold of 45 percent:

    threshold ppp-setup-fail-rate
    50 clear 45

threshold route-service bgp-routes

Configures alarm or alert thresholds for the percentage of route services to BGP routes.
Platform:

ASR 5000

ASR 5500
Product:

PDSN
Privilege:

Security Administrator, Administrator
Syntax

    threshold route-service
    bgp-routes high_thresh [ clear low_thresh ]

high_thresh

Default: 0

Specifies the high threshold rate percentage for BGP routes on 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 BGP routes on 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.

IMPORTANT:

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:

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 (including all VRFs) 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 (including all VRFs) goes below low_thresh. The maximum number of BGP routes is also sent by BGP task when getting the statistics
Alerts or alarms are triggered for BGP routes based on the following rules:

- Enter condition: Actual number of call setup failures is greater than 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.
Example:
The following command configures system for high threshold of 50 percent and a clear threshold of 45 percent:

    threshold route-service
    bgp-routes 50 clear 45

threshold rp-setup-fail-rate

Configures alarm or alert thresholds for the percentage of RAN PDSN (RP) setup failures.
Platform:

ASR 5000

ASR 5500
Product:

PDSN
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for RP setup failure rates based on the following rules:

- 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.
Example:
The following command configures a RP setup failure rate high threshold of 50 percent and a clear threshold of 45 percent:

    threshold rp-setup-fail-rate
    50 clear 45

threshold spc-cpu-memory-usage

This command has been renamed to threshold mgmt-cpu-memory-usage. Please refer to that command for details. Note that for backwards compatibility, the system accepts this command as valid.

IMPORTANT:

This command is not supported on all platforms.
threshold spc-cpu-utilization

This command has been renamed to threshold mgmt-cpu-utilization. Please refer to that command for details. Note that for backwards compatibility, the system accepts this command as valid.
threshold storage-utilization

Configures alarm or alert thresholds for the percentage of management card flash memory utilization.
Platform:

ASR 5000

ASR 5500
Product:

All
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

Flash memory utilization thresholds generate alerts or alarms based on the utilization percentage of storage available to the system.
Alerts or alarms are triggered for storage utilization based on the following rules:

- 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.
Example:
The following command configures a high threshold for storage utilization percentage of 85 for a system using the Alert thresholding model:

    threshold storage-utilization 85

threshold subscriber active

Configures alarm or alert thresholds for the number of active subscribers in the system.
Platform:

ASR 5000

ASR 5500
Product:

PDSN, GGSN, SGSN, HA
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for active subscriber totals based on the following rules:

- 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.
Example:
The following command configures an active subscriber high threshold count of 150000 and a low threshold of 100000 for a system using the Alarm thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

PDSN, GGSN, HA
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for subscriber totals based on the following rules:

- 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.
Example:
The following command configures an active subscriber high threshold count of 450000 and a low threshold of 250000 for a system using the Alarm thresholding model:

    threshold subscriber
    total 450000 clear 250000

threshold system-capacity

Configures alarm or alert thresholds based on the percentage of current system capacity.
Platform:

ASR 5000

ASR 5500
Product:

All
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

Flash memory utilization thresholds generate alerts or alarms based on the system utilization.
Alerts or alarms are triggered for system capacity based on the following rules:

- 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.
Example:
The following command configures a high threshold for system capacity percentage of 95 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

ANS-GW
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of ASN-GW sessions based on the following rules:

- 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.
Example:
The following command configures a total ASN-GW session high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

GGSN
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of GGSN sessions based on the following rules:

- 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.
Example:
The following command configures a total GGSN session high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000
Product:

SGSN
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for GPRS sessions based on the following rules:

- 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.
Example:
The following command configures a total number of PDP contexts per GPRS session high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000
Product:

SGSN
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for GPRS sessions based on the following rules:

- 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.
Example:
The following command configures a total number of GPRS sessions high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

HA
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for HA sessions based on the following rules:

- 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.
Example:
The following command configures a total number of HA sessions high threshold count of 10000 for a system using the Alert thresholding model:

    threshold total-ha-sessions 10000

threshold total-hnbgw-hnb-sessions

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.
Platform:

ASR 5000
Product:

HNB-GW
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of HNB-HNB-GW sessions on IuH interface based on the following rules:

- 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.

IMPORTANT:

To enable an SNMP trap for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWHnbSess command in this mode.
Example:
The following command configures the total number of HNB-GW-HNB sessions on IuH interfaces to a high threshold count of 10000 for a system using the Alert thresholding model:

    threshold total-hnbgw-hnb-sessions 10000

threshold total-hnbgw-iu-sessions

Configures alarm or alert thresholds for the total number of subscriber sessions towards the Core Networks (CN) across all HNB-GW services over Iu interfaces (Iu-CS/Iu-PS interface) on a system.
Platform:

ASR 5000
Product:

HNB-GW
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of subscriber sessions towards CN across all HNB-GW service on a system based on the following rules:

- 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.

IMPORTANT:

To enable an SNMP trap for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWIuSess command in this mode.
Example:
The following command configures the total number of subscriber sessions towards CN across all HNB-GW services to a high threshold count of 30000 for a system using the Alert thresholding model:

    threshold total-hnbgw-iu-sessions 30000

threshold total-hnbgw-ue-sessions

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.
Platform:

ASR 5000
Product:

HNB-GW
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of UEs connected across all HNB-GW service on a system based on the following rules:

- 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.

IMPORTANT:

To enable an SNMP trap for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWUeSess command in this mode.
Example:
The following command configures the total number of UEs connected to HNB-GW service across all HNB-GW services to a high threshold count of 40000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000
Product:

HSGW
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for HSGW sessions based on the following rules:

- 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.
Example:
The following command configures a total number of HSGW sessions high threshold count of 500000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

P-GW, SAEGW
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for LMA sessions based on the following rules:

- 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.
Example:
The following command configures a total number of LMA sessions high threshold count of 500000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

PDSN, GGSN, HA
Privilege:

Security Administrator, Administrator
Syntax

    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 value 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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of LNS sessions based on the following rules:

- 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.
Example:
The following command configures a total LNS session high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000
Product:

MME
Privilege:

Security Administrator, Administrator
Syntax

    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 value 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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of MME sessions based on the following rules:

- 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.
Example:
The following command configures a total MME session high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

PDSN
Privilege:

Security Administrator, Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for the total number of PDSN sessions based on the following rules:

- 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.
Example:
The following command configures a total PDSN session high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

P-GW, SAEGW
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for P-GW sessions based on the following rules:

- 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.
Example:
The following command configures a total number of P-GW sessions high threshold count of 500000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

SAEGW
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for SAEGW sessions based on the following rules:

- 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.
Example:
The following command configures a total number of SAEGW sessions high threshold count of 500000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000
Product:

SGSN
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for SGSN sessions based on the following rules:

- 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.
Example:
The following command configures a total number of PDP contexts per SGSN session high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000
Product:

SGSN
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for SGSN sessions based on the following rules:

- 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.
Example:
The following command configures a total number of SGSN sessions high threshold count of 10000 for a system using the Alert thresholding model:

    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.
Platform:

ASR 5000

ASR 5500
Product:

S-GW
Privilege:

Administrator
Syntax

    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.

IMPORTANT:

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:

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.
Alerts or alarms are triggered for S-GW sessions based on the following rules:

- 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.
Example:
The following command configures a total number of S-GW sessions high threshold count of 500000 for a system using the Alert thresholding model:

    threshold total-sgw-sessions 500000

threshold tpo-dns-failure

Configures alarm or alert thresholds for monitoring Traffic Performance Optimization (TPO) DNS resolution failures.
Platform:

ASR 5000
Product:

TPO
Privilege:

Security Administrator, Administrator
Syntax

    threshold tpo-dns-failure high_thresh [ clear low_thresh ]default threshold tpo-dns-failure

default

Configures this command with the default threshold setting.

Default: 0—disabled
high_thresh

Specifies that if in a polling interval the number of TPO DNS failures experienced by the system meets or exceeds high_thresh an alert or alarm should be generated.

high_thresh is an integer from 0 through 10000.

Default: 0
clear low_thresh

Specifies that if, within the polling interval, the number of TPO DNS failures experienced by the system falls below low_thresh a clear alarm should be generated.

low_thresh is an integer from 0 through 10000.

Default: 0
Usage:

Use this command to configure thresholds for monitoring TPO DNS resolution failures.
threshold tpo-low-compression-gain

Configures alarm or alert thresholds for monitoring TPO low compression gain comparison results.
Platform:

ASR 5000
Product:

TPO
Privilege:

Security Administrator, Administrator
Syntax

    threshold tpo-low-compression-gain high_thresh [ clear low_thresh ]default threshold tpo-low-compression-gain

default

Configures this command with the default threshold setting.

Default: 0—disabled
high_thresh

Specifies that if in a polling interval the number of TPO low-compression-gain comparison results experienced by the system meets or exceeds high_thresh an alert or alarm is generated.

high_thresh is an integer from 0 through 100000.

Default: 0
clear low_thresh

Specifies that if, within the polling interval, the number of TPO low-compression-gain comparison results experienced by the system falls below low_thresh a clear alarm is generated.

low_thresh is an integer from 0 through 100000.

Default: 0
Usage:

Use this command to configure thresholds for monitoring TPO low compression gain results.
threshold tpo-rto-timeout

Configures alarm or alert thresholds for monitoring TPO retransmission timeouts (RTOs).
Platform:

ASR 5000
Product:

TPO
Privilege:

Security Administrator, Administrator
Syntax

    threshold tpo-rto-timeout high_thresh [ clear low_thresh ]default threshold tpo-rto-timeout

default

Configures this command with the default threshold setting.

Default: 0—disabled
high_thresh

Specifies that if in a polling interval the number of TPO RTOs experienced by the system meets or exceeds high_thresh an alert or alarm should be generated.

high_thresh is an integer from 0 through 5000000.

Default: 0
clear low_thresh

Specifies that if, within the polling interval, the number of TPO RTOs experienced by the system falls below low_thresh a clear alarm should be generated.

low_thresh is an integer from 0 through 5000000.

Default: 0
Usage:

Use this command to configure thresholds for monitoring TPO DNS resolution failures.
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.
Platform:

ASR 5000

ASR 5500
Product:

All
Privilege:

Security Administrator, Administrator
Syntax

    timestampsno timestamps

no

Disables generation of timestamps for each command entered. When omitted, the output of a timestamp for each entered command is enabled.
Usage:

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.
Example:

    timestamps

    no timestamps

upgrade limit

Configures upgrade session limits that trigger when the system may execute the software upgrade.
Platform:

ASR 5000

ASR 5500
Product:

All
Privilege:

Security Administrator, Administrator
Syntax

    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:

Use this command to configure upgrade session limits that trigger the system to begin executing the software upgrade.

IMPORTANT:

This command is not supported on all platforms.

IMPORTANT:

Software Patch Upgrades are not supported in this release.
Example:
The following command sets the number of minutes a session can exist to 200, and the minimum number of sessions that may exist before terminating them to 50:

    upgrade limit time 200
    usage 50

url-blacklisting database

This command configures URL Blacklisting database directory parameters.
Platform:

ASR 5000
Product:

CF
Privilege:

Security Administrator, Administrator
Syntax

    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:

Use this command to configure URL Blacklisting database directory parameters.
Example:
The following command configures the maximum number of URL Blacklisting database versions to be maintained to 3:

    url-blacklisting database
    max-versions 3