Thresholding Configuration Guide, StarOS Release 19€¦ · Thresholding Configuration Guide, StarOS Release 19 First Published: September30,2015 Americas Headquarters Cisco Systems,

Thresholding Configuration Guide, StarOS Release 19First Published: September 30, 2015

Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000 800 553-NETS (6387)Fax: 408 527-0883

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS,INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND,EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITEDWARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITHTHE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY,CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain versionof the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDINGANYOTHERWARRANTYHEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS"WITH ALL FAULTS.CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OFMERCHANTABILITY, FITNESS FORA PARTICULAR PURPOSEANDNONINFRINGEMENTORARISING FROMACOURSEOFDEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUTLIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERSHAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, networktopology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentionaland coincidental.

Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http://www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnershiprelationship between Cisco and any other company. (1110R)

© 2015 Cisco Systems, Inc. All rights reserved.

http://www.cisco.com/go/trademarks

http://www.cisco.com/go/trademarks

C O N T E N T S

P r e f a c e About this Guide xiii

About this Guide xiii

Conventions Used xiii

Supported Documents and Resources xiv

Related Common Documentation xiv

Related Product Documentation xv

Obtaining Documentation xv

Contacting Customer Support xvi

C H A P T E R 1 Thresholding Overview 1

Thresholding Overview 1

C H A P T E R 2 AAA Thresholds 7

AAA Thresholds 7

Saving Your Configuration 8

AAA Accounting Message Archive Size Thresholds 8

Configuring AAA Accounting Message Archive Size Threshold 8

AAA Accounting Message Archive Queue Size Thresholds 9

Configuring AAA Accounting Message Archive Queue Size Threshold 9

AAA Accounting Failure Thresholds 9

Configuring AAA Accounting Failure Threshold 10

AAA Accounting Failure Rate Thresholds 10

Configuring AAA Accounting Failure Rate Threshold 10

AAA Authentication Failure Thresholds 10

Configuring AAA Authentication Failure Threshold 11

AAA Authentication Failure Rate Thresholds 11

Configuring AAA Authentication Failure Rate Threshold 11

Thresholding Configuration Guide, StarOS Release 19 iii

AAA Request Message Retry Rate Thresholds 11

Configuring AAA Authentication Failure Rate Threshold 12

AAA Manager Request Queue Threshold 12

Configuring AAA Manager Request Queue Threshold 12

C H A P T E R 3 ASNGW Thresholds 13

ASN GW Service Thresholds 13


System-Level ASN GW Service Thresholds 14

Configuring System-level ASN GW Service Thresholds 14

C H A P T E R 4 Call Setup Thresholds 15

Call Setup Thresholds 15


Call Setup Thresholds 16

Configuring Call Setup Thresholds 16

Call Setup Failure Thresholds 16

Configuring Call Setup Failure Thresholds 17

RP Setup Failure Rate Thresholds 17

Configuring RP Setup Failure Rate Thresholds 17

PPP Setup Failure Rate Thresholds 17

Configuring PPP Setup Failure Rate Thresholds 18

No Resource Call Reject Thresholds 18

Configuring No Resource Call Reject Thresholds 18

C H A P T E R 5 Content Filtering Thresholds 19

Content Filtering Thresholds 19

Configuring Content Filtering Thresholds 19

Enabling Thresholds 19

Configuring Threshold Poll Interval 20

Configuring Threshold Limits 20


C H A P T E R 6 CPU Resource Thresholds 21

CPU Resource Thresholds 21

Thresholding Configuration Guide, StarOS Release 19iv

Contents


10-second Average of Total Processing Card CPU Utilization Thresholds 22

Configuring 10-second Average of Processing Card CPU Thresholds 23

Processing Card CPU Available Memory Thresholds 23

Configuring Processing Card CPU Available Memory Thresholds 23

Processing Card CPU Load Thresholds 23

Configuring Processing Card CPU Load Thresholds 24

Processing Card CPU Memory Usage Thresholds 24

Configuring Processing Card CPU Memory Usage Thresholds 24

Processing Card CPU Session Throughput Thresholds 24

Configuring Processing Card CPU Session Throughput Thresholds 25

Processing Card CPU Utilization Thresholds 25

Configuring Processing Card CPU Utilization Thresholds 25

System Management Card CPU Memory Usage Thresholds 25

Configuring System Management Card CPU Memory Usage Thresholds 26

System Management Card CPU Utilization Thresholds 26

Configuring System Management Card CPU Utilization Thresholds 26

ORBS Software Task CPU Usage Warning-Level Thresholds 26

Configuring ORBS Software Task CPU Usage Warning-Level Thresholds 27

ORBS Software Task CPU Usage Critical-Level Thresholds 27

Configuring ORBS Software Task CPU Usage Critical-Level Thresholds 27

C H A P T E R 7 CSCF Service Thresholds 29

CSCF Service Thresholds 29

Configuring CSCF Thresholds 29

Enabling CSCF Service Thresholds 29

Configuring CSCF Service Thresholds 30

Configuring Threshold Poll Intervals 30


C H A P T E R 8 Diameter Thresholds 33

Diameter Thresholds 33

Configuring Diameter Thresholds 33

DCCA Bad Answers Threshold 34

Configuring DCCA Bad Answers Threshold 34

Thresholding Configuration Guide, StarOS Release 19 v

Contents

DCCA Protocol Errors Threshold 34

Configuring DCCA Protocol Errors Threshold 34

DCCA Rating Failure Threshold 35

Configuring DCCA Rating Failure Threshold 35

DCCA Unknown Rating Group Threshold 35

Configuring DCCA Unknown Rating Group Threshold 35

Diameter Retry Rate Threshold 36

Configuring Diameter Retry Rate Threshold 36


C H A P T E R 9 ePDG Thresholds 37

EPDG Thresholds 37

Configuring ePDG Thresholds 37


C H A P T E R 1 0 FA Service Thresholds 39

FA Service Thresholds 39

Configuring FA Service Thresholds 39


C H A P T E R 1 1 FNG Service Thesholds 41

FNG Thresholds 41

Configuring FNG Thresholds 41


C H A P T E R 1 2 HA Service Thresholds 43

HA Service Thresholds 43


Context-Level HA Service Thresholds 44

Configuring Context-Level HA Service Thresholds 44

HA Service-Level HA Service Thresholds 44

Configuring HA Service-Level HA Service Thresholds 45

C H A P T E R 1 3 HeNBGW Thresholds 47

HeNB-GW Service Thresholds 47

Thresholding Configuration Guide, StarOS Release 19vi

Contents


System-Level HeNB-GW Service Thresholds 48

Configuring System-level HeNB-GW Service Thresholds 48

C H A P T E R 1 4 IP Pool Utilization Thresholds 49

IP Pool Utilization Thresholds 49


Context-Level IP Pool and Group Thresholds 50

Configuring Context-Level IP Pool and Group Thresholds 51

IP Address Pool-Level Thresholds 51

Configuring IP Address Pool-Level Thresholds 52

C H A P T E R 1 5 MME Service Thresholds 53

MME Service Thresholds 53


System-Level MME Service Thresholds 54

Configuring System-level MME Service Thresholds 54

C H A P T E R 1 6 Network Address Translation Thresholds 55

Network Address Translation Thresholds 55

Configuring NAT Thresholds 55


Configuring Threshold Poll Interval 56

Configuring Thresholds Limits 56


C H A P T E R 1 7 Packet Processing Thresholds 57

Packet Processing Thresholds 57


Filtered/Dropped Packet Thresholds 57

Configuring Filtered/Dropped Packet Thresholds 58

Forwarded Packet Thresholds 58

Configuring Forwarded Packet Thresholds 58

C H A P T E R 1 8 PDG/TTG Thresholds 59

Thresholding Configuration Guide, StarOS Release 19 vii

Contents

PDG/TTG Thresholds 59

Configuring PDG/TTG Thresholds 59


C H A P T E R 1 9 PDIF Thresholds 61

PDIF Thresholds 61

Configuring PDIF Thresholds 61


C H A P T E R 2 0 PDSN Service Thresholds 63

PDSN Service Thresholds 63


Context-Level PDSN Service Thresholds 64

Configuring Context-Level PDSN Service Thresholds 64

PDSN Service-Level PDSN Service Thresholds 64

Configuring PDSN Service-Level PDSN Service Thresholds 65

C H A P T E R 2 1 Per-service Session Thresholds 67

Per-service Session Thresholds 67


Per-PDSN Service Thresholds 68

Configuring Per-PDSN Service Thresholds 68

Per-HA Service Thresholds 68

Configuring Per-HA Service Thresholds 69

Per-GGSN Service Thresholds 69

Configuring Per-GGSN Service Thresholds 69

Per-LNS Service Thresholds 69

Configuring Per-LNS Service Thresholds 70

Per-GPRS Service Thresholds 70

Configuring Per-GPRS Service Thresholds 70

Per-GPRS Service PDP Contexts Thresholds 70

Configuring Per-GPRS Service PDP Contexts Thresholds 71

Per-SGSN Service Thresholds 71

Configuring Per-SGSN Service Thresholds 71

Per-SGSN Service PDP Contexts Thresholds 71

Thresholding Configuration Guide, StarOS Release 19viii

Contents

Configuring Per-SGSN Service PDP Contexts Thresholds 72

C H A P T E R 2 2 Port Utilization Thresholds 73

Port Utilization Thresholds 73


Receive Port Utilization Thresholds 74

Configuring Receive Port Utilization Thresholds 74

Transmit Port Utilization Thresholds 74

Configuring Transmit Port Utilization Thresholds 74

High Port Activity Thresholds 75

Configuring High Port Activity Thresholds 75

C H A P T E R 2 3 SaMOG Thresholds 77

SaMOG Thresholds 77

Configuring SaMOG Thresholds 77


C H A P T E R 2 4 Session License Utilization Thresholds 79

Session License Utilization Thresholds 79

Configuring Session License Utilization Thresholds 79


C H A P T E R 2 5 Stateful Firewall Thresholds 81

Stateful Firewall Thresholds 81

Configuring Stateful Firewall Thresholds 81


Configuring Threshold Polling Intervals 82

Configuring Thresholds Limits 82


C H A P T E R 2 6 Subscriber Thresholds 83

Subscriber Thresholds 83


Total Subscriber Thresholds 83

Configuring Total Subscriber Thresholds 84

Thresholding Configuration Guide, StarOS Release 19 ix

Contents

Active Subscriber Thresholds 84

Configuring Active Subscriber Thresholds 84

C H A P T E R 2 7 System Management Card CompactFlash Memory Thresholds 85

System Management Card CompactFlash Memory Thresholds 85


C H A P T E R 2 8 Total Session Thresholds 87

Total Session Thresholds 87


Total PDSN Session Thresholds 89

Configuring Total PDSN Session Thresholds 89

Total GGSN Session Thresholds 89

Configuring Total GGSN Session Thresholds 90

Total GPRS Session Thresholds 90

Configuring Total GPRS Session Thresholds 90

Total GPRS PDP Contexts Thresholds 90

Configuring Total GPRS PDP Context Thresholds 91

Total HA Session Thresholds 91

Configuring Total HA Session Thresholds 91

Total HeNB-GW Session Thresholds 91

Configuring Total HeNB Session Thresholds 92

Configuring Total UE Session Thresholds 92

Total HNB-GW Session Thresholds 92

Configuring Total HNB Session Thresholds 92

Configuring Total UE Session Thresholds 0 93

Configuring Total Iu Session Thresholds 93

Total HSGW Session Thresholds 93

Configuring Total HSGW Session Thresholds 93

Total LMA Session Thresholds 94

Configuring Total LMA Session Thresholds 94

Total LNS Session Thresholds 94

Configuring Total LNS Session Thresholds 94

Total MME Session Thresholds 95

Configuring Total MME Session Thresholds 95

Thresholding Configuration Guide, StarOS Release 19x

Contents

Total P-GW Session Thresholds 95

Configuring Total P-GW Session Thresholds 95

Total SAEGW Session Thresholds 96

Configuring Total SAEGW Session Thresholds 96

Total SGSN Session Thresholds 96

Configuring Total SGSN Session Thresholds 96

Total SGSN PDP Contexts Thresholds 97

Configuring Total SGSN PDP Context Thresholds 97

Total S-GW Session Thresholds 97

Configuring Total S-GW Session Thresholds 97

Thresholding Configuration Guide, StarOS Release 19 xi

Contents

Thresholding Configuration Guide, StarOS Release 19xii

Contents

About this Guide

• About this Guide, page xiii

• Conventions Used, page xiii

• Supported Documents and Resources, page xiv

• Contacting Customer Support , page xvi

About this GuideThis preface describes the Thresholding Configuration Guide and its document conventions.

This document provides descriptive information on StarOS thresholds and thresholding mechanism, used tomonitor all StarOS functions and services for conditions and events that could potentially cause errors oroutages.

Refer to the Thresholding Overview section for more information about the structure and content of thisreference.

Conventions UsedThe following tables describe the conventions used throughout this documentation.

DescriptionNotice Type

Provides information about important features or instructions.Information Note

Alerts you of potential damage to a program, device, or system.Caution

Alerts you of potential personal injury or fatality. May also alert youof potential electrical hazards.

Warning

Thresholding Configuration Guide, StarOS Release 19 xiii

DescriptionTypeface Conventions

This typeface represents displays that appear on your terminalscreen, for example:

Login:

Text represented as a screendisplay

This typeface represents commands that you enter, for example:

show ip access-list

This document always gives the full form of a command inlowercase letters. Commands are not case sensitive.

Text represented as commands

This typeface represents a variable that is part of a command, forexample:

show card slot_number

slot_number is a variable representing the desired chassis slotnumber.

Text represented as a command variable

This typeface represents menus and sub-menus that you accesswithin a software application, for example:

Click the File menu, then click New

Text represented as menu or sub-menunames

Supported Documents and Resources

Related Common DocumentationThe following common documents are available:

• AAA Interface Administration and Reference

• Command Line Interface Reference

• GTPP Interface Administration and Reference

• Installation Guide (platform dependant)

• Release Change Reference

• SNMP MIB Reference

• Statistics and Counters Reference

• System Administration Guide (platform dependant)

Thresholding Configuration Guide, StarOS Release 19xiv

About this GuideSupported Documents and Resources

Related Product DocumentationThe most up-to-date information for related products is available in the product Release Notes provided witheach product release.

The following related product documents are also available:

• ADC Administration Guide

• CF Administration Guide

• ECS Administration Guide

• ePDG Administration Guide

• eWAG Administration Guide

• GGSN Administration Guide

• HA Administration Guide

• HeNB-GW Administration Guide

• HNB-GW Administration Guide

• HSGW Administration Guide

• IPSec Reference

• IPSG Administration Guide

• MME Administration Guide

• MVG Administration Guide

• NAT Administration Guide

• PDSN Administration Guide

• PSF Administration Guide

• P-GW Administration Guide

• SAEGW Administration Guide

• SaMOG Administration Guide

• SecGW Administration Guide

• SGSN Administration Guide

• S-GW Administration Guide

Obtaining DocumentationThe most current Cisco documentation is available on the following website:

http://www.cisco.com/cisco/web/psa/default.html

Use the following path selections to access the documentation:

Products > Wireless > Mobile Internet> Platforms > Cisco ASR 5000 Series > Cisco ASR 5000

Thresholding Configuration Guide, StarOS Release 19 xv

About this GuideRelated Common Documentation

Contacting Customer SupportUse the information in this section to contact customer support.

Refer to the support area of http://www.cisco.com for up-to-date product documentation or to submit a servicerequest. A valid username and password are required to access this site. Please contact your Cisco sales orservice representative for additional information.

Thresholding Configuration Guide, StarOS Release 19xvi

About this GuideContacting Customer Support

C H A P T E R 1Thresholding Overview

• Thresholding Overview, page 1

Thresholding OverviewThresholding on the system is used to monitor the system for conditions that could potentially cause errorsor outage. Typically, these conditions are temporary (i.e. high CPU utilization, or packet collisions on anetwork) and are quickly resolved. However, continuous or large numbers of these error conditions within aspecific time interval may be indicative of larger, more severe issues. The purpose of thresholding is to helpidentify potentially severe conditions so that immediate action can be taken to minimize and/or avoid systemdowntime.

The following thresholding models are supported by the system:

• Alert: A value is monitored and an alert condition occurs when the value reaches or exceeds theconfigured high threshold within the specified polling interval. The alert is then generated and/or sentat the end of the polling interval.

In the example shown in the figure below, this model generates alerts during period 2, 3, and 5 at thepoint where the count exceeded HT.

• Alarm: Both high and low thresholds are defined for a value. An alarm condition occurs when the valuereaches or exceeds the configured high threshold within the specified polling interval. The alert is thengenerated and/or sent at the end of the polling interval.

The alarm is cleared at the end of the first interval where the measured value is below the low threshold.

Thresholding Configuration Guide, StarOS Release 19 1

In the example shown in in the figure below, this model generates an alarm during period 2 when thecount exceeds HT. A second alarm is generated in period 6 when the count falls beneath LT. The secondalarm indicates a "clear" condition.

Figure 1: Example of Thresholding Model

Note that for certain values, the alert or alarm serves to warn of low quantities (i.e. memory, sessionlicenses, etc.). In these cases, the low threshold is the condition that must be met or exceeded within thepolling interval to generate the alert or alarm. Once the high threshold is exceeded during an interval, thelow quantity condition is cleared.

Note

Thresholding functionality on the system can be configured to monitor the following values:

• AAA:

• Archive size

• Number of authentication failures

• Authentication failure rate

• Number of accounting failures

• Accounting failure rate

• Retry rate

• AAA Manager request queue usage

• ASN GW Service:

• Number of ASN GW Authentication failures

• Number of ASN GW hand-off denials

• Maximum number of EAP retries

Thresholding Configuration Guide, StarOS Release 192

Thresholding OverviewThresholding Overview

• Number of network entry denials

• Number of Network Access Identifier (NAI) in R6 message

• ASN GW timeout duration during session setup

• ASN GW session timeout duration

• FA Service registration reply errors

• HA Service:

• Call setup rate

• Registration Reply, Re-registration Reply, and De-registration Reply errors

• HNB-GW Service Sessions:

• Total HNB Sessions

• Total UE Sessions

• Total Iu Sessions

• PDSN Service:

• Call setup rate

• A11 Messages failed and discarded

• PPP send packets discarded

• Call setup:

• Number of calls setup

• Number of call setup failures

• RP setup failure rate

• PPP setup failure rate

• Number of calls rejected due to no processing resources being available

• MME Service

• Number of MME Authentication failures

• Number of MME Session Attachment failures

• Number of MME sessions

• PAC/PSC CPU resource availability:

• 10 second sample utilization

• Percent utilization

• Available memory

• Load



• Memory usage

• Session throughput

• SPC/SMC CPU resource availability:

• Memory usage

• Percent utilization

• ORBS software task utilization

• IP address pool utilization

• Licensed session utilization

• Packet processing:

• Number of packets filtered/dropped

• Number of packets forwarded to CPU

• Per-service session count

• Port utilization:

• High activity

• Transmit utilization

• Receive utilization

• Subscriber number:

• Total number

• Number active

• Total session count

• SPC/SMC CompactFlash memory utilization

Thresholding reports conditions using one of the following mechanisms:

• SNMP traps: SNMP traps have been created that indicate the condition (high threshold crossing and/orclear) of each of the monitored values. Complete descriptions and other information pertaining to thesetraps is located in the starentMIB(8164).starentTraps(2) section of the SNMP MIB Reference.

The generation of specific traps can be enabled or disabled on the system allowing you to view onlythose traps that are most important to you.

• Logs: The system provides a facility called threshold for which active and event logs can be generated.As with other system facilities, logs are generated Logmessages pertaining to the condition of a monitoredvalue are generated with a severity level of WARNING.

Refer to the System Administration Guide for additional information on system logging functionality.

• Alarm System: High threshold alarms generated within the specified polling interval are considered"outstanding" until a the condition no longer exists and/or a condition clear alarm is generated.



"Outstanding" alarms are reported to through the system\'s alarm subsystem and are viewable throughthe system\'s CLI.

The following table indicates the reporting mechanisms supported by each of the above models.

Table 1: Thresholding Reporting Mechanisms by Model

Alarm SystemLogsSNMP TrapsModel

XXAlert

XXXAlarm





C H A P T E R 2AAA Thresholds

• AAA Thresholds, page 7

• Saving Your Configuration, page 8

• AAA Accounting Message Archive Size Thresholds, page 8

• AAA Accounting Message Archive Queue Size Thresholds, page 9

• AAA Accounting Failure Thresholds, page 9

• AAA Accounting Failure Rate Thresholds, page 10

• AAA Authentication Failure Thresholds, page 10

• AAA Authentication Failure Rate Thresholds, page 11

• AAA Request Message Retry Rate Thresholds, page 11

• AAA Manager Request Queue Threshold, page 12

AAA ThresholdsThreshold monitoring can be enabled for the AAA-related values described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on the number of AAA(RADIUS and/or GTPP) accountingmessages archived during the pollinginterval.

Archive size

Enables the generation of alerts or alarms per Session Manager instancebased on the queue size for AAA (RADIUS and/or GTPP) accountingmessages being archived during the polling interval.

Archive Queue size

Enables the generation of alerts or alarms based on the number of failedAAA accounting requests that occur during the polling interval.

Accounting Failures

Enables the generation of alerts or alarms based on the percentage ofAAA accounting requests that failed during the polling interval.

Accounting Failure Rate


DescriptionValue

Enables the generation of alerts or alarms based on the number of failedAAA authentication requests that occur during the polling interval.

Authentication Failures

Enables the generation of alerts or alarms based on the percentage ofAAA authentication requests that failed during the polling interval.

Authentication Failure Rate

Enables the generation of alerts or alarms based on the percentage ofAAA requests (both accounting and authentication) that were re-triedduring the polling interval.

Retry Rate

Enables the generation of alarms or alerts when the AAAManager requestqueue usage reaches a specified percentage level.

AAA Manager Request QueueUsage

Saving Your ConfigurationWhen you configure thresholds they are not permanent unless you save the changes.When you have completedconfiguring thresholds, save your configuration to flash memory, an external memory device, and/or a networklocation using the Exec mode command save configuration. For additional information on how to verify andsave configuration files, refer to the System Administration Guide and theCommand Line Interface Reference.

AAA Accounting Message Archive Size ThresholdsIn the event that the system cannot communicate with configured AAA accounting servers (RADIUS orCGFs), either due to the server being busy or loss of network connectivity, the system buffers, or archives,the accounting messages.

Accounting message archive size thresholds generate alerts or alarms based on the number of AAA accountingmessages buffered in the archive during the specified polling interval. Accounting requests are counted forall AAA accounting servers that the system is configured to communicate with.

Alerts or alarms are triggered for accounting message archive size threshold based on the following rules:

• Enter condition: Actual number of archived messages > or = High Threshold

• Clear condition: Actual number of archived messages < Low Threshold

If a trigger condition occurs within the polling interval, the alert or alarm will not be generated until the endof the polling interval.

Configuring AAA Accounting Message Archive Size ThresholdUse the following example to configure the accounting message archive size threshold:

configurethreshold aaa-acct-archive-size <high_thresh> [ clear <low_thresh> ]threshold poll aaa-acct-archive-size interval <time>threshold monitoring aaa-acct-archive-sizeend


AAA ThresholdsSaving Your Configuration

AAA Accounting Message Archive Queue Size ThresholdsThe Session Manager can buffer around 26400 CDRs per Session Manager instance in ASR5K. Once theabove limit is breached the oldest CDRs will be purged to make room for the new CDRs. Since purging canhappen as soon as the Session Manager queue size reaches the maximum allowed limit, there is a need forthe alarms to be generated during this scenario.

Accounting message archive queue size thresholds generate alerts or alarms per Session Manager instancebased on the queue percentage of accounting messages archived in the buffer. The alarm will typically begenerated when the message archival begins, and as and when the buffer is filled up to say, 25, 50 and 90during the specified polling interval.

AcctArchiveStarted trap will be generated if the queue size exceeds 15 of the maximum number of sessionmanager items per instance. The queue size is indicative of the maximum of ACS manager queue sizeand session manager queue size.

Note

Alerts or alarms are triggered for accounting message archive queue size thresholds based on the followingrules:

• Enter condition: Actual queue percentage of archived messages > or = High Threshold

• Clear condition: Actual queue percentage of archived messages < Low Threshold


Configuring AAA Accounting Message Archive Queue Size ThresholdUse the following example to configure the accounting message archive queue size threshold:

configurethreshold aaa-acct-archive-queue-size1 <high_thresh> [ clear <low_thresh> ]threshold aaa-acct-archive-queue-size2 <high_thresh> [ clear <low_thresh> ]threshold aaa-acct-archive-queue-size3 <high_thresh> [ clear <low_thresh> ]threshold monitoring aaa-acct-archive-queuethreshold poll aaa-acct-archive-queue-size1 interval <time>threshold poll aaa-acct-archive-queue-size2 interval <time>threshold poll aaa-acct-archive-queue-size3 interval <time>end

AAA Accounting Failure ThresholdsAccounting failure thresholds generate alerts or alarms based on the number of failed AAA accountingmessagerequests that occur during the specified polling interval. Accounting requests are counted for all AAA accountingservers that the system is configured to communicate with.

Alerts or alarms are triggered for accounting failures based on the following rules:

• Enter condition: Actual number of failures > or = High Threshold


AAA ThresholdsAAA Accounting Message Archive Queue Size Thresholds

• Clear condition: Actual number of failures < Low Threshold


Configuring AAA Accounting Failure ThresholdUse the following example to configure AAA accounting failure threshold:

configurethreshold aaa-acct-failure <high_thresh> [ clear <low_thresh> ]threshold poll aaa-acct-failure interval <time>threshold monitoring aaa-acct-failureend

AAA Accounting Failure Rate ThresholdsAccounting failure rate thresholds generate alerts or alarms based on the percentage of AAA accountingmessage requests that failed during the specified polling interval. Accounting requests are counted for allAAA accounting servers that the system is configured to communicate with.

Alerts or alarms are triggered for accounting failure rates based on the following rules:




Configuring AAA Accounting Failure Rate ThresholdUse the following example to configure AAA accounting failure rate threshold:

configurethreshold aaa-acct-failure-rate <high_thresh>[ clear <low_thresh> ]threshold poll aaa-acct-failure-rate interval <time>threshold monitoring aaa-acct-failureend

AAA Authentication Failure ThresholdsAuthentication failure thresholds generate alerts or alarms based on the number of failed AAA authenticationmessage requests that occur during the specified polling interval. Authentication requests are counted for allAAA authentication servers that the system is configured to communicate with.

Alerts or alarms are triggered for authentication failures based on the following rules:




AAA ThresholdsConfiguring AAA Accounting Failure Threshold


Configuring AAA Authentication Failure ThresholdUse the following example to configure AAA authentication failure threshold:

configurethreshold aaa-auth-failure <high_thresh>[ clear <low_thresh> ]threshold poll aaa-auth-failure interval <time>threshold monitoring aaa-auth-failureend

AAA Authentication Failure Rate ThresholdsAuthentication failure rate thresholds generate alerts or alarms based on the percentage of AAA authenticationmessage requests that failed during the specified polling interval. Authentication requests are counted for allAAA authentication servers that the system is configured to communicate with.

Alerts or alarms are triggered for authentication failure rates based on the following rules:

• Enter condition: Actual failure percentage > or = High Threshold

• Clear condition: Actual failure percentage < Low Threshold


Configuring AAA Authentication Failure Rate ThresholdUse the following example for configuring AAA authentication failure rate threshold:

configurethreshold aaa-auth-failure-rate <high_thresh>[ clear <low_thresh> ]threshold poll aaa-auth-failure-rate interval <time>threshold monitoring aaa-auth-failureend

AAA Request Message Retry Rate ThresholdsAAA request message retry rate thresholds generate alerts or alarms based on the percentage of requestmessages (both authentication and accounting) that were retried during the specified polling interval. Thepercentage is based on a message count taken for all AAA authentication and accounting servers that thesystem is configured to communicate with.

Alerts or alarms are triggered for request message retries based on the following rules:

• Enter condition: Actual failure percentage > or = High Threshold

• Clear condition: Actual failure percentage < Low Threshold


AAA ThresholdsConfiguring AAA Authentication Failure Threshold


Configuring AAA Authentication Failure Rate ThresholdUse the following example for configuring AAA request message retry rate threshold:

configurethreshold aaa-retry-rate <high_thresh>[ clear <low_thresh> ]threshold poll aaa-retry-rate interval <time>threshold monitoring aaa-retry-rateend

AAA Manager Request Queue ThresholdThe AAA Manager request queue threshold generates an alert or alarm based on the usage percentage of theAAAManager request queue during the specified polling interval. The percentage is based on the total numberof pending requests for the AAA Manager and the total size allowed for the queue. This is polled for eachAAA Manager process.

Alerts or alarms are triggered for the AAA Manager request queue threshold based on the following rules:

• Enter condition: Actual AAA Manager request queue percentage used > or = High Threshold

• Clear condition: Actual AAA Manager request queue percentage used < Low Threshold

If a trigger condition occurs within the polling interval, the alert or alarm is not generated until the end of thepolling interval.

Configuring AAA Manager Request Queue ThresholdUse the following example for configuring AAA Manager request queue threshold.

configurethreshold aaamgr-request-queue <high_thresh>[ clear <low_thresh> ]threshold poll aaamgr-request-queue interval <time>threshold monitoring aaamgr-request-queueend


AAA ThresholdsConfiguring AAA Authentication Failure Rate Threshold

C H A P T E R 3ASNGW Thresholds

• ASN GW Service Thresholds, page 13


• System-Level ASN GW Service Thresholds, page 14

ASN GW Service ThresholdsASN GW Service thresholds generate alerts or alarms for the average number of calls setup. A threshold canbe configured to report this information on entire system for ASN GW service. Thresholds can also beconfigured for session registration response failures, discarded interface registration requests, discardednetwork entry registration acknowledgments for ASN GW services.

Alerts or alarms are triggered for these ASN GW thresholds based on the following rules:

• Enter condition:When the actual average of call setups or actual number of failures or discards passes,or is equal to, the configured Threshold value an alert or alarm is set.

• Clear condition:When the actual average of call setups or actual number of failures or discards passesbelow the Threshold value the alert or alarm is cleared.




System-Level ASN GW Service ThresholdsThe system-level thresholds for ASNGWService-Level can be configured to monitor thresholds for subscribernetwork entry, authentication, session registration response failures, discarded registration requests, sessiontimeout, and hand-off denials for individual ASN GW services.

Following thresholds can be configured for the ASN GW service-level:

• Number of ASN GW Authentication failures

• Number of ASN GW hand-off denials

• Maximum number of EAP retries

• Number of network entry denials

• Number of Network Access Identifier (NAI) in R6 message

• ASN GW timeout duration during session setup

• ASN GW session timeout duration

Configuring System-level ASN GW Service ThresholdsUse the following example to configure and enable these thresholds:configurationthreshold asngw-auth-failure <high_thresh> [clear <low_thresh>]threshold asngw-handoff-denial <high_thresh> [clear <low_thresh>]threshold asngw-max-eap-retry <high_thresh> [clear <low_thresh>]threshold asngw-network-entry-denial <high_thresh> [clear <low_thresh>]threshold asngw-r6-invalid-nai <high_thresh> [clear <low_thresh>]threshold asngw-session-setup-timeout <high_thresh> [clear <low_thresh>]threshold asngw-session-timeout <high_thresh> [clear <low_thresh>]threshold poll asngw-auth-failure interval <time>threshold poll asngw-handoff-denial interval <time>threshold poll asngw-max-eap-retry interval <time>threshold poll asngw-network-entry-denial interval <time>threshold poll asngw-r6-invalid-nai interval <time>threshold poll asngw-session-setup-timeout interval <time>threshold poll asngw-session-timeout interval <time> thresholdmonitoring asngw end


ASNGW ThresholdsSystem-Level ASN GW Service Thresholds

C H A P T E R 4Call Setup Thresholds

• Call Setup Thresholds, page 15


• Call Setup Thresholds, page 16

• Call Setup Failure Thresholds, page 16

• RP Setup Failure Rate Thresholds, page 17

• PPP Setup Failure Rate Thresholds, page 17

• No Resource Call Reject Thresholds, page 18

Call Setup ThresholdsThreshold monitoring can be enabled for the call setup values described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on the number of callssetup by the system during the polling interval.

Number of calls setup

Enables the generation of alerts or alarms based on the number of call setupfailures experienced by the system during the polling interval.

Number of call setup failures

Enables the generation of alerts or alarms based on the rate at which RPfailures are experienced by the system during the polling interval.

RP setup failure rate

Enables the generation of alerts or alarms based on the rate at which PPPfailures are experienced by the system during the polling interval.

PPP setup failure rate

Enables the generation of alerts or alarms based on the number of callsrejected by the system due to insufficient resources (memory and/or sessionlicenses) during the polling interval.

Number of calls rejected dueto no processing resourcesbeing available



Call Setup ThresholdsThreshold monitoring can be enabled for the call setup values described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on the number of callssetup by the system during the polling interval.

Number of calls setup

Enables the generation of alerts or alarms based on the number of call setupfailures experienced by the system during the polling interval.

Number of call setup failures

Enables the generation of alerts or alarms based on the rate at which RPfailures are experienced by the system during the polling interval.

RP setup failure rate

Enables the generation of alerts or alarms based on the rate at which PPPfailures are experienced by the system during the polling interval.

PPP setup failure rate

Enables the generation of alerts or alarms based on the number of callsrejected by the system due to insufficient resources (memory and/or sessionlicenses) during the polling interval.

Number of calls rejected dueto no processing resourcesbeing available

Configuring Call Setup ThresholdsUse the following example to configure call setup thresholds:configurethreshold call-setup <high_thresh> [ clear <low_thresh> ]threshold poll call-setup interval <time>threshold monitoring call-setupend

Call Setup Failure ThresholdsCall setup failure thresholds generate alerts or alarms based on the total number of call setup failures experiencedby the system during the specified polling interval.

Alerts or alarms are triggered for call setup failures based on the following rules:

• Enter condition: Actual number of call setup failures > or = High Threshold

• Clear condition: Actual number of call setup failures < Low Threshold


Call Setup ThresholdsSaving Your Configuration


Configuring Call Setup Failure ThresholdsUse the following example for configuring call setup failure thresholding:configurethreshold call-setup-failure <high_thresh> [ clear <low_thresh> ]threshold poll call-setup-failure interval <time>threshold monitoring call-setupend

RP Setup Failure Rate ThresholdsRP setup failure rate thresholds generate alerts or alarms based on the rate of call setup failures experiencedby the system during the specified polling interval. The failure rate is the percentage of failures as determinedby number of Registration Request Messages rejected divided by the total number of Registration RequestMessages received.

Alerts or alarms are triggered for RP setup failure rates based on the following rules:




Configuring RP Setup Failure Rate ThresholdsUse the following example for configuring RP setup failure rate thresholding:configurethreshold rp-setup-fail-rate <high_thresh> [ clear <low_thresh> ]threshold poll rp-setup-fail-rate interval <time>threshold monitoring call-setupend

PPP Setup Failure Rate ThresholdsPPP setup failure rate thresholds generate alerts or alarms based on the rate of call setup failures experiencedby the system during the specified polling interval. The failure rate is the percentage of failures as determinedby 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:




Call Setup ThresholdsConfiguring Call Setup Failure Thresholds


Configuring PPP Setup Failure Rate ThresholdsUse the following example for configuring PPP setup failure rate thresholding:configurethreshold ppp-setup-fail-rate <high_thresh> [ clear <low_thresh> ]threshold poll ppp-setup-fail-rate interval <time>threshold monitoring call-setupend

No Resource Call Reject ThresholdsNo resource call reject thresholds generate alerts or alarms based on the total number of calls that were rejectedby the system due to insufficient or no resources (CPU, memory, etc.) during the specified polling interval.

Alerts or alarms are triggered for no-resource-rejected calls based on the following rules:

• Enter condition: Actual number of calls rejected due to no resources > or = High Threshold

• Clear condition: Actual number of calls rejected due to no resources < Low Threshold


Configuring No Resource Call Reject ThresholdsUse the following example for configuring no resource call reject thresholding:configurethreshold call-reject-no-resource <high_thresh> [ clear <low_thresh> ]threshold poll call-reject-no-resource interval <time>threshold monitoring call-setupend


Call Setup ThresholdsConfiguring PPP Setup Failure Rate Thresholds

C H A P T E R 5Content Filtering Thresholds

• Content Filtering Thresholds, page 19

• Configuring Content Filtering Thresholds, page 19


Content Filtering ThresholdsThresholds generate alerts or alarms based on either the total number of Content Filtering calls setup by thesystem during the specified polling interval, or on the number of currently active calls only.

Alerts or alarms are triggered for call setups based on the following rules:

• Enter condition: Actual number of call setups > or = High Threshold

• Clear condition: Actual number of call setups < Low Threshold


Default value is 0, which means there will be no monitoring.

The polling interval is in seconds and it is an integer between 30 and 60000. Entries will be rounded up to thenearest 30 seconds.

Configuring Content Filtering ThresholdsThis section describes how to enable and configure Content Filtering thresholds.

Enabling ThresholdsTo enable thresholds use the following configuration:

configurethreshold monitoring content-filteringend


Configuring Threshold Poll IntervalTo configure threshold poll interval use the following configuration:

configurethreshold poll contfilt-block interval <interval>threshold poll contfilt-rating interval <interval>end

Configuring Threshold LimitsTo configure threshold limits use the following configuration:

configurethreshold contfilt-block <high_thresh> [ clear <low_thresh> ]threshold contfilt-rating <high_thresh> [ clear <low_thresh> ]end



Content Filtering ThresholdsConfiguring Threshold Poll Interval

C H A P T E R 6CPU Resource Thresholds

• CPU Resource Thresholds, page 21


• 10-second Average of Total Processing Card CPU Utilization Thresholds, page 22

• Processing Card CPU Available Memory Thresholds, page 23

• Processing Card CPU Load Thresholds, page 23

• Processing Card CPU Memory Usage Thresholds, page 24

• Processing Card CPU Session Throughput Thresholds, page 24

• Processing Card CPU Utilization Thresholds, page 25

• System Management Card CPU Memory Usage Thresholds, page 25

• System Management Card CPU Utilization Thresholds, page 26

• ORBS Software Task CPU Usage Warning-Level Thresholds, page 26

• ORBS Software Task CPU Usage Critical-Level Thresholds, page 27

CPU Resource ThresholdsThreshold monitoring can be enabled for the CPU resource values described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on a 10 second average ofprocessing card CPU utilization.

10 second average of totalprocessing card CPU utilization

Enables the generation of alerts or alarms based on the amount of availablememory for each processing card CPU during the polling interval.

Processing card CPU availablememory

Enables the generation of alerts or alarms based on processing card CPUload using a 5 minute average measurement.

Processing card CPU load

Enables the generation of alerts or alarms based on the percentage of totalprocessing card CPU memory used during the polling interval.

Processing card CPU memoryusage


DescriptionValue

Enables the generation of alerts or alarms based on the total throughput forall Session Manager tasks running on each processing card CPU duringthe polling interval.

Processing card CPU sessionthroughput

Enables the generation of alerts or alarms based on the utilization percentagefor each processing card CPU during the polling interval.

Processing card CPU utilization

Enables the generation of alerts or alarms based on the percentage of totalsystem management card CPU memory used during the polling interval.

System management card CPUmemory usage

Enables the generation of alerts or alarms based on the utilization percentagefor each active system management card CPU during the polling interval.

System management card CPUutilization

Enables the generation of warning-level alerts or alarms based on thepercentage CPU resources utilized by the Object Request Broker (ORB)software task.

ORBS task CPU utilizationwarning

Enables the generation of critical-level alerts or alarms based on thepercentage CPU resources utilized by the Object Request Broker (ORB)software task.

ORBS task CPU utilizationcritical


10-second Average of Total Processing Card CPU UtilizationThresholds

10-second average of total CPU utilization thresholds generate alerts or alarms based on a 10 second averageof cpu utilization for all processing card CPUs during the specified polling interval.

Alerts or alarms are triggered for 10-second average of total CPU utilization based on the following rules:

• Enter condition:Average measured amount of total CPU utilization for the last 10 seconds > or = HighThreshold

• Clear condition: Average measured amount of total CPU utilization for the last 10 seconds < LowThreshold



CPU Resource ThresholdsSaving Your Configuration

Configuring 10-second Average of Processing Card CPU ThresholdsUse the following example for configuring 10-second average of total CPU utilization thresholding.configurethreshold 10sec-cpu-utilization <high_thresh> [ clear <low_thresh> ]threshold poll 10sec-cpu-utilization interval <time>threshold monitoring cpu-resourceend

Processing Card CPU Available Memory ThresholdsCPU available memory thresholds generate alerts or alarms based on the amount of available memory foreach processing card CPU during the specified polling interval. Although, a single threshold is configuredfor all processing card CPUs, separate alerts or alarms can be generated for each CPU. Both active and standbyprocessing card CPUs are monitored.

Alerts or alarms are triggered for available processing card CPU memory based on the following rules:

• Enter condition: Average measured amount of memory/CPU for last 5 minutes = or < Low Threshold

• Clear condition: Average measured amount of memory/CPU for last 5 minutes > High Threshold


Configuring Processing Card CPU Available Memory ThresholdsUse the following example for configuring processing card CPU available memory thresholding.configurethreshold cpu-available-memory <low_thresh> [ clear <high_thresh> ]threshold poll cpu-available-memory interval <time>threshold monitoring cpu-resourceend

Processing Card CPU Load ThresholdsCPU load thresholds generate alerts or alarms based on a five-minute average of processing card CPU loadduring the polling interval. Although, a single threshold is configured for all processing card CPUs, separatealerts or alarms can be generated for each CPU.

Alerts or alarms are triggered for CPU load based on the following rules:

• Enter condition: 5 minute average CPU load > or = High Threshold

• Clear condition: 5 minute average CPU load < Low Threshold



CPU Resource ThresholdsConfiguring 10-second Average of Processing Card CPU Thresholds

Configuring Processing Card CPU Load ThresholdsUse the following example for configuring processing card CPU load thresholding.configurethreshold cpu-load <high_thresh> [ clear <low_thresh> ]threshold poll cpu-load interval <time>threshold monitoring cpu-resourceend

Processing Card CPU Memory Usage ThresholdsCPU memory usage thresholds generate alerts or alarms based on memory usage for each processing cardCPU during the polling interval. Although, a single threshold is configured for all processing card CPUs,separate alerts or alarms can be generated for each CPU.

Alerts or alarms are triggered for CPU memory usage based on the following rules:

• Enter condition: Actual CPU memory usage > or = High Threshold

• Clear condition: Actual CPU memory usage < Low Threshold


Configuring Processing Card CPU Memory Usage ThresholdsUse the following example for configuring processing card CPU memory usage thresholding.configurethreshold cpu-memory-usage <high_thresh> [ clear <low_thresh> ]threshold poll cpu-memory-usage interval <time>threshold monitoring cpu-resourceend

Processing Card CPU Session Throughput ThresholdsCPU session throughput thresholds generate alerts or alarms based on total throughput for all SessionManagertasks running on each processing card CPU during the polling interval. Although, a single threshold isconfigured for all processing card CPUs, separate alerts or alarms can be generated for each CPU.

Alerts or alarms are triggered for processing card CPU session throughput based on the following rules:

• Enter condition: Actual CPU session throughput > or = High Threshold

• Clear condition: Actual CPU session throughput < Low Threshold



CPU Resource ThresholdsConfiguring Processing Card CPU Load Thresholds

Configuring Processing Card CPU Session Throughput ThresholdsUse the following example for configuring processing card CPU session throughput thresholding.configurethreshold cpu-session-throughput <high_thresh> [ clear <low_thresh> ]threshold poll cpu-session-throughput interval <time>threshold monitoring cpu-session-throughputend

Processing Card CPU Utilization ThresholdsCPU utilization thresholds generate alerts or alarms based on the utilization percentage of each processingcard CPU during the specified polling interval. Although, a single threshold is configured for all processingcard CPUs, separate alerts or alarms can be generated for each CPU.

Alerts or alarms are triggered for processing card CPU utilization based on the following rules:

• Enter condition: Average measured CPU utilization for last 5 minutes > or = High Threshold

• Clear condition: Average measured CPU utilization for last 5 minutes < Low Threshold


Configuring Processing Card CPU Utilization ThresholdsUse the following example for configuring processing card CPU utilization thresholding.configurethreshold cpu-utilization <high_thresh> [ clear <low_thresh> ]threshold poll cpu-utilization interval <time>threshold monitoring cpu-resourceend

System Management Card CPU Memory Usage ThresholdsCPU memory usage thresholds generate alerts or alarms based on memory usage for the system managementcard CPU during the polling interval. A single threshold enables CPU monitoring for both the active andstandby system management cards allowing for alerts or alarms to be generated for each CPU.

Alerts or alarms are triggered for system management card CPU memory usage based on the following rules:

• Enter condition: Actual CPU memory usage > or = High Threshold

• Clear condition: Actual CPU memory usage < Low Threshold



CPU Resource ThresholdsConfiguring Processing Card CPU Session Throughput Thresholds

Configuring System Management Card CPU Memory Usage ThresholdsUse the following example for configuring system management card CPU memory usage thresholding.configurethreshold mgmt-cpu-memory-usage <high_thresh> [ clear <low_thresh> ]threshold poll mgmt-cpu-memory-usage interval <time>threshold monitoring cpu-resourceend

System Management Card CPU Utilization ThresholdsCPU utilization thresholds generate alerts or alarms based on the utilization percentage of each systemmanagement card CPU during the specified polling interval. Although, a single threshold is configured forboth system management card CPUs, separate alerts or alarms can be generated for each CPU.

Alerts or alarms are triggered for system management card CPU utilization based on the following rules:

• Enter condition: Average measured CPU utilization for last 5 minutes > or = High Threshold

• Clear condition: Average measured CPU utilization for last 5 minutes < Low Threshold


Configuring System Management Card CPU Utilization ThresholdsUse the following example for configuring system management card CPU utilization thresholding.configurethreshold mgmt-cpu-utilization <high_thresh> [ clear <low_thresh> ]threshold poll mgmt-cpu-utilization interval <time>threshold monitoring cpu-resourceend

ORBS Software Task CPU Usage Warning-Level ThresholdsObject Request Broker (ORB) software task CPU utilization thresholds generate warning-level alerts or alarmsbased on the percentage of system management card CPU resources it is consuming at the time of polling.

Warning-level alerts or alarms are triggered for CPU usage by the ORBs software task based on the followingrules:

• Enter condition: Actual CPU usage percentage > High Threshold

• Clear condition: Actual CPU usage percentage = or < Low Threshold


CPU Resource ThresholdsConfiguring System Management Card CPU Memory Usage Thresholds

Configuring ORBS Software Task CPU Usage Warning-Level ThresholdsUse the following example for configuring warning-level ORB software task CPU usage thresholding.configurethreshold cpu-orbs-warn <high_thresh> [ clear <low_thresh> ]threshold poll cpu-orbs-warn interval <time>threshold monitoring cpu-resourceend

ORBS Software Task CPU Usage Critical-Level ThresholdsObject Request Broker (ORB) software task CPU utilization thresholds generate critical-level alerts or alarmsbased on the percentage of system management card CPU resources it is consuming at the time of polling.

Critical-level alerts or alarms are triggered for CPU usage by the ORBs software task based on the followingrules:

• Enter condition: Actual CPU usage percentage > High Threshold

• Clear condition: Actual CPU usage percentage = or < Low Threshold

Configuring ORBS Software Task CPU Usage Critical-Level ThresholdsUse the following example for configuring critical-level ORB software task CPU usage thresholding.configurethreshold cpu-orbs-crit <high_thresh> [ clear <low_thresh> ]threshold poll cpu-orbs-crit interval <time>threshold monitoring cpu-resourceend


CPU Resource ThresholdsConfiguring ORBS Software Task CPU Usage Warning-Level Thresholds


CPU Resource ThresholdsConfiguring ORBS Software Task CPU Usage Critical-Level Thresholds

C H A P T E R 7CSCF Service Thresholds

• CSCF Service Thresholds, page 29

• Configuring CSCF Thresholds, page 29


CSCF Service ThresholdsCSCF Service thresholds generate alerts or alarms for the average number of calls setup. A threshold can beconfigured to report this information for an individual CSCF service. Thresholds can also be configured forseveral other conditions for individual CSCF services.

Alerts or alarms are triggered for these CSCF thresholds based on the following rules:

• Enter condition: Actual average of call setups or actual number of errors > or = High Threshold

• Clear condition: Actual average of call setups or actual number of errors < Low Threshold

If a trigger condition occurs within the polling interval, the alert or alarm is not generated until the end of thepolling interval. Polling intervals are set on a system level.

Configuring CSCF ThresholdsThis section describes how to enable and configure CSCF Service thresholds.

Enabling CSCF Service ThresholdsTo enable threshold monitoring for a CSCF service, use the following configuration:configurecontext <context_name>cscf-service <name>threshold monitoringend


Configuring CSCF Service ThresholdsThe following thresholds can be configured for a CSCF Service:

• Number of CSCF call setup failures

• Number of total active CSCF calls

• Number of CSCF call setup failures due to no-resource

• Number of CSCF Presence errors

• Number of CSCF Registration Authentication failures

• Number of CSCF call setup failures due to TCP error

• Number of CSCF calls per polling interval

• Number of CSCF registrations per polling interval

• Number of total CSCF active registrations

• Maximum number of route-failures, after which the alarm/alert will be raised

Use the following example to configure these thresholds:configurationcontext <context_name>cscf-service <name>threshold call-setup-failures <high_thresh> [ clear <low_thresh>]threshold call-total-active <high_thresh> [ clear <low_thresh> ]threshold error-no-resource <high_thresh> [ clear <low_thresh>]threshold error-presence <high_thresh> [ clear <low_thresh>]threshold error-reg-auth <high_thresh> [ clear <low_thresh>]threshold error-tcp <high_thresh> [ clear <low_thresh>]threshold invite-rcvd-rate <high_thresh> [ clear <low_thresh>]threshold reg-rcvd-rate <high_thresh> [ clear <low_thresh>]threshold reg-total-active <high_thresh> [ clear <low_thresh>]threshold route-failures <high_thresh> [ clear <low_thresh>]end

Configuring Threshold Poll IntervalsThe following threshold poll intervals can be configured for the CSCF Service:

• CSCF call setup failures

• CSCF total active calls

• CSCF calls

• CSCF registrations

• CSCF service route failures

• CSCF no resource errors

• CSCF presence errors


CSCF Service ThresholdsConfiguring CSCF Service Thresholds

• CSCF Reg-Auth errors

• CSCF TCP errors

• CSCF total active registrations

Use the following example to configure these threshold poll intervals:configurationthreshold poll call-setup-failures interval <dur>threshold poll call-total-active interval <dur>threshold poll cscf-invite-rcvd interval <dur>threshold poll cscf-reg-rcvd interval <dur>threshold poll cscf-service-route-failures interval <dur>threshold poll error-no-resource interval <dur>threshold poll error-presence interval <dur>threshold poll error-reg-auth interval <dur>threshold poll error-tcp interval <dur>threshold poll reg-total-active interval <dur>end



CSCF Service ThresholdsSaving Your Configuration


CSCF Service ThresholdsSaving Your Configuration

C H A P T E R 8Diameter Thresholds

• Diameter Thresholds, page 33

• Configuring Diameter Thresholds, page 33


Diameter ThresholdsThreshold monitoring can be enabled for the Diameter-related values described in the following table.

DescriptionThreshold

Enables generation of alerts or alarms based on the number of timesDIAMETER-BAD-ANSWER code is sent to the Diameter server during apolling interval.

DCCA Bad Answers

Enables generation of alerts or alarms based on the number protocol errormessages received from the Diameter server during a polling interval.

DCCA Protocol Errors

Enables generation of alerts or alarms based on the number of times theDiameter server rejected requests for a block of credits, due to the RatingGroup (content-id) being invalid during a polling interval.

DCCA Rating Failure

Enables generation of alerts or alarms based on the number of times the blockof credits returned by the Diameter server is rejected due to the Rating Groupbeing unknown during a polling interval.

DCCA Unknown RatingGroup

Enables generation of alerts or alarms based on the percentage of Diameterrequests that were re-tried during a polling interval.

Diameter Retry Rate

Configuring Diameter ThresholdsThis section describes how to enable and configure Diameter thresholds.


DCCA Bad Answers ThresholdDCCA Bad Answers threshold generates alerts or alarms based on the number of timesDIAMETER-BAD-ANSWER code is sent to the Diameter server during the polling interval.

Alerts or alarms are triggered based on the following rules:

• Enter condition : Actual number of timesDIAMETER-BAD-ANSWERcode sent > or =High Threshold

• Clear condition : Actual number of times DIAMETER-BAD-ANSWER code sent < Low Threshold


Configuring DCCA Bad Answers ThresholdTo configure the DCCA Bad Answers threshold use the following configuration:

configurethreshold dcca-bad-answers <high_thresh> [ clear <low_thresh> ]threshold poll dcca-bad-answers interval <seconds>threshold monitoring ecsend

DCCA Protocol Errors ThresholdDCCA Protocol Errors threshold generates alerts or alarms based on the number protocol error messagesreceived from the Diameter server during the polling interval.


• Enter condition : Actual number of protocol error messages received > or = High Threshold

• Clear condition : Actual number of protocol error messages received < Low Threshold


Configuring DCCA Protocol Errors ThresholdTo configure the DCCA Protocol Errors threshold use the following configuration:

configurethreshold dcca-protocol-error <high_thresh> [ clear <low_thresh> ]threshold poll dcca-protocol-error interval <seconds>threshold monitoring ecsend


Diameter ThresholdsDCCA Bad Answers Threshold

DCCA Rating Failure ThresholdDCCA Rating Failure threshold generates alerts or alarms based on the number of times the Diameter serverrejected requests for a block of credits, due to the Rating Group (content-id) being invalid during the pollinginterval.


• Enter condition : Actual number of rating failures > or = High Threshold

• Clear condition : Actual number of rating failures < Low Threshold


Configuring DCCA Rating Failure ThresholdTo configure the DCCA Rating Failure threshold use the following configuration:

configurethreshold dcca-rating-failed <high_thresh> [ clear <low_thresh> ]threshold poll dcca-rating-failed interval <seconds>threshold monitoring ecsend

DCCA Unknown Rating Group ThresholdDCCA Unknown Rating Group threshold generates alerts or alarms based on the number of times the blockof credits returned by the Diameter server is rejected due to the Rating Group being unknown during thepolling interval.


• Enter condition : Actual number of "unknown rating group" failures > or = High Threshold

• Clear condition : Actual number of "unknown rating group" < Low Threshold


Configuring DCCA Unknown Rating Group ThresholdTo configure the DCCA Unknown Rating Group threshold use the following configuration:

configurethreshold dcca-unknown-rating-group <high_thresh> [ clear <low_thresh> ]threshold poll dcca-unknown-rating-group interval <seconds>threshold monitoring ecsend


Diameter ThresholdsDCCA Rating Failure Threshold

Diameter Retry Rate ThresholdDiameter Retry Rate threshold generates alerts or alarms based on the percentage of Diameter requests thatwere re-tried during the polling interval.


• Enter condition: Percentage of Diameter requests retried > or = High Threshold

• Clear condition: Percentage of Diameter requests retried < Low Threshold


Configuring Diameter Retry Rate ThresholdTo configure the Diameter Retry Rate threshold use the following configuration:

configurethreshold diameter diameter-retry-rate <high_thresh> [ clear <low_thresh> ]threshold poll diameter-retry-rate interval <seconds>threshold monitoring diameterend



Diameter ThresholdsDiameter Retry Rate Threshold

C H A P T E R 9ePDG Thresholds

• EPDG Thresholds, page 37

• Configuring ePDG Thresholds, page 37


EPDG ThresholdsThresholds generate alerts or alarms based on either the total number of ePDG calls setup by the system duringthe specified polling interval, or on the number of currently active calls only.





Default ePDG threshold polling interval value is 5 Min.


Configuring ePDG ThresholdsUse the following configuration example to enable, disable and configure ePDG threshold monitoring.

configure[ no ] threshold monitoring epdg-service

threshold epdg-current-sessions current_epdg_sessions_threshold clear alarm_clear_thresholddefault threshold epdg-current-sessionsthreshold poll epdg-current-sessions interval threshold_polling_intervaldefault threshold poll epdg-current-sessions intervalend




ePDG ThresholdsSaving Your Configuration

C H A P T E R 10FA Service Thresholds

• FA Service Thresholds, page 39

• Configuring FA Service Thresholds, page 39


FA Service ThresholdsAn FA Service threshold generates alerts or alarms for registration reply errors for individual FA services.

Alerts or alarms are triggered for the FA threshold based on the following rules:

• Enter condition: Actual number of errors > High Thresholds

• Clear condition: Actual number of errors < Low Threshold


Configuring FA Service ThresholdsUse the following example to configure the threshold, set the polling interval for the threshold and enablemonitoring of the threshold.

configurecontext <context_name>fa-service <name>threshold reg-reply-error <high_thresh> [ clear <low_thresh> ]exitexitthreshold poll fa-reg-reply-error interval <time>threshold monitoring fa-serviceend




FA Service ThresholdsSaving Your Configuration

C H A P T E R 11FNG Service Thesholds

• FNG Thresholds, page 41

• Configuring FNG Thresholds, page 41


FNG ThresholdsThresholds generate alerts or alarms based on either the total number of FNG calls set up by the system duringthe specified polling interval, or on the number of currently active calls only.


• Enter condition: Actual number of call setups > High Threshold



The default value is 0, which means there will be no monitoring.


Configuring FNG ThresholdsUse the following configuration example to configure FNG threshold monitoring:

configure[ no | default ] threshold monitoring fng-service[ default ] threshold fng-current-sessions <high_thresh> [ clear <low_thresh> ][ default ] threshold poll fng-current-sessions interval <time>

endUsage thresholds are provided for monitoring the overall FNG usage on anASR 5000 chassis. These commandsare used to monitor the total number of FNG sessions, both active and inactive, over an entire chassis.


In the commands above,<high_thresh> configures the total number of FNG sessions on an ASR 5000 chassis,both active and inactive. <high_thresh> is any integer from 0 to 300000. There is no default, but 0 meansthat there is no threshold monitoring.

The clear <low_thresh> command clears any percentage of the number of sessions being monitored usingthe <high_thresh> variable defined above. <low_thresh> is any integer from 0 to 300000.

The following example configures a monitoring threshold of 300000 active and inactive FNG sessions on anASR 5000 chassis:

threshold fng-current-sessions 300000

This turns out to be too many, so the following command clears 100000:

threshold fng-current-sessions 300000 clear 100000



FNG Service ThesholdsSaving Your Configuration

C H A P T E R 12HA Service Thresholds

• HA Service Thresholds, page 43


• Context-Level HA Service Thresholds, page 44

• HA Service-Level HA Service Thresholds, page 44

HA Service ThresholdsHA Service thresholds generate alerts or alarms for the average number of calls setup. A threshold can beconfigured to report this information for an entire context or for an individual HA service. Thresholds canalso be configured for registration reply, re-registration reply and de-registration reply errors for individualHA services.

Alerts or alarms are triggered for these HA thresholds based on the following rules:

• Enter condition: Actual average of call setups or actual number of errors > or = High Threshold

• Clear condition: Actual average of call setups or actual number of errors < Low Threshold


The following table describes the possible methods for configuring HA Service thresholds:

DescriptionMethod

This threshold keeps track of the average number of call setups for all HAservices in a context. When the actual average of call setups per polling periodmeets or exceeds the set high threshold an alert or alarm is set.

Context-Level

HA services send and receive registration messages. The thresholds in the HAService-Level can be configured to monitor thresholds for registration reply,re-registration reply, and de-registration reply errors.

HA Service-Level



Context-Level HA Service ThresholdsThere is only one HA service threshold that can be configured, the average number of call setups for all HAservices in a context.

Configuring Context-Level HA Service ThresholdsUse the following example to configure the threshold, set the polling interval for the threshold and enablemonitoring of the threshold:configurationcontext <context_name>threshold ha-service-init-rrq-rcvd-rate <high_thresh> [ clear <low_thresh> ]exitthreshold poll <threshold_name> interval <time>threshold monitoring ha-servicethreshold monitoring ip-secend

HA Service-Level HA Service ThresholdsThere are 10 thresholds that can be configured for the HA service-level:

• Total De-registration Reply Errors

• Average Calls Setup Per Second

• Total IPSec Call Requests Rejected

• Percentage of IPSec IKE Failures

• Total IPSec IKE Failures

• Total IPSec IKE Requests

• Total IPSec Tunnels Established

• Total IPSec tunnels Setup

• Total Registration Reply Errors

• Total Re-registration Reply Errors


HA Service ThresholdsSaving Your Configuration

Configuring HA Service-Level HA Service ThresholdsUse the following example to configure the HA service-level thresholds:

configurecontext <context_name>ha-service <name>threshold { dereg-reply-error | init-rrq-rcvd-rate | ipsec-call-req-rej | ipsec-ike-failrate |ipsec-ike-failures | ipsec-ike-requests | ipsec-tunnels-established | ipsec-tunnels-setup |reg-reply-error | rereg-reply-error }exitexitthreshold poll ha-init-rrq-rcvd-rate interval <time>threshold poll reg-reply-error interval <time>threshold poll rereg-reply-error interval <time>threshold poll dereg-reply-error interval <time>threshold monitoring ha-serviceend


HA Service ThresholdsConfiguring HA Service-Level HA Service Thresholds


HA Service ThresholdsConfiguring HA Service-Level HA Service Thresholds

C H A P T E R 13HeNBGW Thresholds

• HeNB-GW Service Thresholds, page 47


• System-Level HeNB-GW Service Thresholds, page 48

HeNB-GW Service ThresholdsHeNB-GW Service thresholds generate alerts or alarms for the average number of calls setup. A thresholdcan be configured to report this information on entire system for HeNB-GW service. Thresholds can also beconfigured for session registration response failures, discarded interface registration requests, discardednetwork entry registration acknowledgments for HeNB-GW services.

Threshold counter limits are configured for HeNB-GW HeNB SCTP association, HeNB-GW UE sessions,and HeNB-GW Paging messages with poll interval value.

On reaching the threshold limits in the configured interval, if thresholdmonitoring is enabled for the HeNB-GWservice(s), threshold notifications get generated as SNMP traps. If threshold monitoring is disabled for theHeNB-GW service(s), even on reaching the threshold limits, no notification gets generated.

Alerts or alarms are triggered for these HeNB-GW thresholds based on the following rules:






System-Level HeNB-GW Service ThresholdsThe system-level thresholds for HeNB-GW Service-Level can be configured to monitor thresholds forHeNB-GW Paging messages.

Following thresholds can be configured for the HeNB-GW service-level:

• Number of HeNB-GW Paging Messages

• Total number of subscribers threshold for HeNB-GW HeNB sessions

• Total number of subscribers threshold for HeNB-GW UE sessions

Configuring System-level HeNB-GW Service ThresholdsUse the following example to configure and enable these thresholds:configurationthreshold henbgw-paging-messages <high_thresh> [ clear <low_thresh>]threshold total-henbgw-henb-sessions <high_thresh> [ clear <low_thresh>]threshold total-henbgw-ue-sessions <high_thresh> [ clear <low_thresh>]threshold poll henbgw-paging-messages interval <dur>threshold poll total-henbgw-henb-sessions interval <dur>threshold poll total-henbgw-ue-sessions interval <dur>threshold monitoring henbgw-serviceend


HeNBGW ThresholdsSystem-Level HeNB-GW Service Thresholds

C H A P T E R 14IP Pool Utilization Thresholds

• IP Pool Utilization Thresholds, page 49


• Context-Level IP Pool and Group Thresholds, page 50

• IP Address Pool-Level Thresholds, page 51

IP Pool Utilization ThresholdsWhen IP address pools are configured on the system, they can be assigned to a group. All configured publicIP address pools that were not assigned to a group are treated as belonging to the same group (automaticallynamed "Public IP Pools"). Individually configured static or private pools are each treated as their own group.

IP address pool thresholds can be configured for all IP pools or pool groups configured within a system contextor for individual pools or groups. These thresholds generate alerts or alarms based on calculations pertainingto percent-available for pool groups and percent-free, percent-on-hold, percent-released, and percent-used forindividual pools.

Alerts or alarms are triggered for IP address pool utilization based on the following rules:

• Enter condition: When the actual IP address utilization percentage passes, or is equal to, the configuredThreshold value an alert or alarm is set.

• Clear condition: When the actual IP address utilization percentage passes the Threshold value the alertor alarm is cleared.


The following table describes the possible methods for configuring IP pool utilization thresholds:


DescriptionMethod

IP Pool Group: A single percent available threshold can be configured for allIP pool groups within a given context. The threshold is based on an aggregatemeasurement of available IP addresses for all IP pools within each group.NOTE: Separate alerts or alarms are generated for each group that experiencesan event.

Context-level

IP Pool: The following thresholds can be configured for all IP address poolsconfigured within a given system context:

• Percent-free;

• Percent-hold;

• Percent-release;

• Percent-used.

NOTE: Separate alerts or alarms are generated for each pool that experiencesan event.

The following thresholds can be configured for each IP address pool:

• Percent-available for the group that the IP pool belongs to;

• Percent-free;

• Percent-hold;

• Percent-release; and

• Percent-used.

Thresholds configured for individual pools take precedence over thecontext-level threshold that would otherwise be applied (if configured). In theevent that two IP address pools belonging to the same pool group are configuredwith different group-available thresholds, the system uses the poolconfiguration that has the Enter condition that would be encountered first forthe entire group.

IP address pool-level


Context-Level IP Pool and Group ThresholdsThis section provides instructions for configuring a single IP address pool utilization threshold for all poolswithin the context. These become the default settings for all pool existing or created in this context. See forsetting thresholds for individual IP pools.


IP Pool Utilization ThresholdsSaving Your Configuration

These instructions assume that IP address pools have been previously configured.Note

Configuring Context-Level IP Pool and Group ThresholdsUse the following example to configure the context-level IP Pool and group thresholds:

configurethreshold poll { available-ip-pool-group | ip-pool-free | ip-pool-hold | ip-pool-release | ip-pool-used} interval <time>context <context_name>threshold available-ip-pool-group <low_thresh> [ clear <high_thresh> ]threshold ip-pool-free <low_thresh> [ clear <high_thresh> ]threshold ip-pool-hold <high_thresh> [ clear <low_thresh> ]threshold ip-pool-release <high_thresh> [ clear <low_thresh> ]threshold ip-pool-used <high_thresh> [ clear <low_thresh> ]threshold monitoring available-ip-pool-group

end

IP Address Pool-Level ThresholdsThis section provides instructions for configuring a single IP address pool utilization threshold for all poolgroups within the context.

The IP pool-level threshold settings configured with the ip pool pool_name alert-threshold commandtake precedence over the context level IP pool threshold configuration commands.

Note

These instructions also assume that IP address pools have been previously configured.Note

If the group-available threshold is set for individual IP pools that are a part of an IP pool group, the IP poolwith the threshold that is encountered first sets the threshold for the entire group.

For example; assume there is a group named IPGroup1, and there are three IP pools in that group; PoolA,PoolB, and PoolC. Also assume that, at the IP address-pool level, the three pools have the group-availablethreshold set as follows:

• PoolA:

• Enter condition (low threshold) set to 40 percent

• Clear condition (high threshold) set to 60 percent

• PoolB:




IP Pool Utilization ThresholdsConfiguring Context-Level IP Pool and Group Thresholds

• PoolC:



In this case, the Enter condition for the percentage of IP pool addresses available from the group that isencountered first is the low threshold setting for PoolA. So both the low and high threshold settings for PoolAare used for the whole group.

Configuring IP Address Pool-Level Thresholdsconfigurethreshold poll { available-ip-pool-group | ip-pool-free | ip-pool-hold | ip-pool-release | ip-pool-used} interval <time>context <context_name>ip pool name alert-threshold group-available <low_thresh> [ clear <high_thresh> ]ip pool name alert-threshold pool-free <low_thresh> [ clear <high_thresh> ]ip pool name alert-threshold pool-hold <high_thresh> [ clear <low_thresh> ]ip pool name alert-threshold pool-release <high_thresh> [ clear <low_thresh>]ip pool name alert-threshold pool-used <high_thresh> [ clear <low_thresh> ]exitthreshold monitoring available-ip-pool-groupend


IP Pool Utilization ThresholdsConfiguring IP Address Pool-Level Thresholds

C H A P T E R 15MME Service Thresholds

• MME Service Thresholds, page 53


• System-Level MME Service Thresholds, page 54

MME Service ThresholdsMME Service thresholds generate alerts or alarms for the average number of calls setup. A threshold can beconfigured to report this information on entire system for MME service. Thresholds can also be configuredfor session registration response failures, discarded interface registration requests, discarded network entryregistration acknowledgments for MME services.

Alerts or alarms are triggered for these MME thresholds based on the following rules:






System-Level MME Service ThresholdsThe system-level thresholds for MME Service-Level can be configured to monitor thresholds for MMEauthentication, session registration response failures, discarded registration requests for individual or all MMEservices.

Following thresholds can be configured for the MME service-level:

• Number of MME authentication failures

• Number of MME session registration failures

Configuring System-level MME Service ThresholdsUse the following example to configure and enable these thresholds:configurationthreshold mme-auth-failure <high_thresh> [ clear <low_thresh>]threshold mme-attach-failure <high_thresh> [ clear <low_thresh> ]threshold total-mme-sessions <high_thresh> [ clear <low_thresh>]threshold poll mme-auth-failure interval <dur>threshold poll mme-attach-failure interval <dur>threshold poll total-mme-session interval <dur>threshold monitoring mme-serviceend


MME Service ThresholdsSystem-Level MME Service Thresholds

C H A P T E R 16Network Address Translation Thresholds

• Network Address Translation Thresholds, page 55

• Configuring NAT Thresholds, page 55


Network Address Translation ThresholdsThresholds generate alerts or alarms based on either the total number of Network Address Translation (NAT)calls setup by the system during the specified polling interval, or on the number of currently active calls only.



• Clear condition: Actual number of call setups < Low Threshold.




Configuring NAT ThresholdsThis section describes how to enable and configure NAT thresholds.


configurethreshold monitoring firewallcontext <context_name>


threshold monitoring available-ip-pool-groupend

Notes:

The thresholdmonitoring available-ip-pool-group command is required only if you are configuring IP poolthresholds. It is not required if you are only configuring NAT port-chunks usage threshold or many-to-oneNAT.

Configuring Threshold Poll IntervalTo configure threshold poll interval use the following configuration:

configurethreshold poll ip-pool-used interval <interval>threshold poll nat-pkt-drop interval <interval>threshold poll nat-port-chunks-usage interval <interval>end

Notes:

The threshold poll nat-port-chunks-usage interval command is only applicable to many-to-one NAT.

Configuring Thresholds LimitsTo configure threshold limits use the following configuration:

configurecontext <context_name>

threshold ip-pool-free <high_thresh> [ clear <low_thresh> ]ip-pool-hold <high_thresh> [ clear <low_thresh> ]ip-pool-release <high_thresh> [ clear <low_thresh> ]ip-pool-used <high_thresh> [ clear <low_thresh> ]exit

threshold nat-pkt-drop <high_thresh> [ clear <low_thresh> ]threshold nat-port-chunks-usage <high_thresh> [ clear <low_thresh> ]end

Notes:

• Thresholds configured using the threshold ip-pool-* commands in the Context Configuration Modeapply to all IP pools in the context

• Thresholds configured using the alert-threshold keyword are specific to the pool that they are configuredin, and will take priority, i.e. will override the context-wide configuration mentioned above.



Network Address Translation ThresholdsConfiguring Threshold Poll Interval

C H A P T E R 17Packet Processing Thresholds

• Packet Processing Thresholds, page 57


• Filtered/Dropped Packet Thresholds, page 57

• Forwarded Packet Thresholds, page 58

Packet Processing ThresholdsThreshold monitoring can be enabled for the packet processing values described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on the total number of packetsthat were filtered or dropped based on ACL rules during the polling interval.

Packets filtered/dropped

Enables the generation of alerts or alarms based on the total number of packetsthat were forwarded to the CPU during the polling interval.

Packets forwarded


Filtered/Dropped Packet ThresholdsFiltered/dropped packet thresholds generate alerts or alarms based on the total number of packets that werefiltered or dropped by the system as a result of ACL rules during the specified polling interval.

Alerts or alarms are triggered for filtered/dropped packets based on the following rules:


• Enter condition: Actual number of filtered/dropped packets > or = High Threshold

• Clear condition: Actual number of filtered/dropped packets < Low Threshold


These instructions assume that ACLs have been previously configured.Note

Configuring Filtered/Dropped Packet ThresholdsUse the following example to configure the filtered/dropped packet thresholds:

configurethreshold packets-filtered-dropped <high_thresh> [ clear <low_thresh>]threshold poll packets-filtered-dropped interval <time>threshold monitoring packets-filtered-droppedend

Forwarded Packet ThresholdsForwarded packet thresholds generate alerts or alarms based on the total number of packets that were forwardedto active system CPU(s) during the specified polling interval. Packets are forwarded to active system CPUswhen the NPUs do not have adequate information to properly route them.

Ping and/or traceroute packets are intentionally forwarded to system CPUs for processing. These packettypes are included in the packet count for this threshold.

Note

Alerts or alarms are triggered for forwarded packets based on the following rules:

• Enter condition: Actual number of forwarded packets > or = High Threshold

• Clear condition: Actual number of forwarded packets < Low Threshold


Configuring Forwarded Packet ThresholdsUse the following example to configure the forwarded packet thresholds:

configurethreshold packets-forwarded-to-cpu <high_thresh> [ clear <low_thresh> ]threshold poll packets-forwarded-to-cpu interval <time>threshold monitoring packets-forwarded-to-cpuend


Packet Processing ThresholdsConfiguring Filtered/Dropped Packet Thresholds

C H A P T E R 18PDG/TTG Thresholds

• PDG/TTG Thresholds, page 59

• Configuring PDG/TTG Thresholds, page 59


PDG/TTG ThresholdsThresholds generate alerts or alarms based on either the total number of PDG/TTG calls set up by the systemduring the specified polling interval, or on the number of currently active calls only.


• Enter condition: Actual number of call setups > High Threshold





Configuring PDG/TTG ThresholdsUse the following configuration example to enable, disable and configure PDG/TTG threshold monitoring.

configure[ no | default ] threshold monitoring pdg-service[ default ] threshold pdg-current-sessions <high_thresh> [ clear <low_thresh> ][ default ] threshold poll pdg-current-sessions interval <time>[ default ] threshold pdg-current-active-sessions <high_thresh> [ clear <low_thresh> ][ default ] threshold poll pdg-current-active-sessions interval <time>

end




PDG/TTG ThresholdsSaving Your Configuration

C H A P T E R 19PDIF Thresholds

• PDIF Thresholds, page 61

• Configuring PDIF Thresholds, page 61


PDIF ThresholdsThresholds generate alerts or alarms based on either the total number of PDIF calls setup by the system duringthe specified polling interval, or on the number of currently active calls only.







Configuring PDIF ThresholdsUse the following configuration example to enable, disable and configure PDIF threshold monitoring.

configure[ no ] threshold monitoring pdif

threshold pdif-current-sessions high_thresh [ clear <low_thresh> ]threshold pdif-current-active-sessions [ <high_thresh> clear <low_thresh> ]default threshold { pdif-current-sessions | pdif-current-active-sessions }threshold poll { pdif-current-sessions | pdif-current-active-sessions } interval <time>default threshold poll { pdif-current-sessions | pdif-current-active-sessions }end




PDIF ThresholdsSaving Your Configuration

C H A P T E R 20PDSN Service Thresholds

• PDSN Service Thresholds, page 63


• Context-Level PDSN Service Thresholds, page 64

• PDSN Service-Level PDSN Service Thresholds, page 64

PDSN Service ThresholdsPDSN Service thresholds generate alerts or alarms for the average number of calls setup. A threshold can beconfigured to report this information for an entire context or for an individual PDSN service. Thresholds canalso be configured for A11 registration response failures, discarded A11 registration requests, discarded A11registration acknowledgments, and discarded PPP send packets for individual PDSN services.

Alerts or alarms are triggered for these PDSN thresholds based on the following rules:




The following table describes the possible methods for configuring PDSN Service thresholds:

DescriptionMethod

This threshold keeps track of the average number of call setups for all PDSNservices in a context. When the actual average of call setups per pollingperiod meets or exceeds the set high threshold an alert or alarm is set.

Context-Level

PDSN services send and receive A11 registrationmessages and PPP packets.The thresholds in the PDSN Service-Level can be configured to monitorthresholds for A11 registration response failures, discarded A11 registrationrequests, discarded A11 registration acknowledgments, and discarded PPPsend packets for individual PDSN services.

PDSN Service-Level



Context-Level PDSN Service ThresholdsThis threshold keeps track of the average number of call setups for all PDSN services in a context. When theactual average of call setups per polling period meets or exceeds the set high threshold an alert or alarm isset.

Configuring Context-Level PDSN Service ThresholdsUse the following example to configure the threshold for monitoring the average number of calls setup persecond for the context, set the polling interval for the threshold and enable monitoring of the threshold.configurecontext <context_name>threshold pdsn-service init-rrq-rcvd-rate <high_thresh> [ clear <low_thresh>]exitthreshold poll pdsn-init-rrq-rcvd-rate interval <time>threshold monitoring pdsn-serviceend

PDSN Service-Level PDSN Service ThresholdsPDSN services send and receive A11 registration messages and PPP packets. The thresholds in the PDSNService-Level can be configured to monitor thresholds for A11 registration response failures, discarded A11registration requests, discarded A11 registration acknowledgments, and discarded PPP send packets forindividual PDSN services.

There are five thresholds that can be configured for the PDSN service-level:

• Average Calls Setup Per Second

• Total A11 Registration Response Failures

• Total A11 Registration Request Messages Discarded

• Total A11 Registration Acknowledgement Messages Discarded

• Total Packets PPP Protocol Processing Layer Discarded on Transmit


PDSN Service ThresholdsSaving Your Configuration

Configuring PDSN Service-Level PDSN Service ThresholdsUse the following example to configure and enable these thresholds:configurationcontext <context_name>pdsn-service <name>threshold init-rrq-rcvd-rate <high_thresh> [ clear <low_thresh>]threshold a11-rrp-failure <high_thresh> [ clear <low_thresh>]threshold a11-rrq-msg-discard <high_thresh> [ clear <low_thresh>]threshold a11-rac-msg-discard <high_thresh> [ clear <low_thresh>]threshold all-ppp-send-discard <high_thresh> [ clear <low_thresh>]exitexitthreshold poll pdsn-init-rrq-rcvd-rate interval <time>threshold poll a11-rrp-failure interval <time>threshold poll a11-rrq-msg-discard interval <time>threshold poll a11-rac-msg-discard interval <time>threshold poll a11-ppp-send-discard interval <time>threshold monitoring pdsn-serviceend


PDSN Service ThresholdsConfiguring PDSN Service-Level PDSN Service Thresholds


PDSN Service ThresholdsConfiguring PDSN Service-Level PDSN Service Thresholds

C H A P T E R 21Per-service Session Thresholds

• Per-service Session Thresholds, page 67


• Per-PDSN Service Thresholds, page 68

• Per-HA Service Thresholds, page 68

• Per-GGSN Service Thresholds, page 69

• Per-LNS Service Thresholds, page 69

• Per-GPRS Service Thresholds, page 70

• Per-GPRS Service PDP Contexts Thresholds, page 70

• Per-SGSN Service Thresholds, page 71

• Per-SGSN Service PDP Contexts Thresholds, page 71

Per-service Session ThresholdsThreshold monitoring can be enabled for the per-service session counts described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on the number of sessions(active and dormant) facilitated by any PDSN service counted during thepolling interval.

PDSN Services

Enables the generation of alerts or alarms based on the number of sessions(active and dormant) facilitated by any HA service counted during the pollinginterval.

HA Services

Enables the generation of alerts or alarms based on the number of PDPcontexts (active and dormant) facilitated by anyGGSN service counted duringthe polling interval.

GGSN Services

Enables the generation of alerts or alarms based on the number of sessionsfacilitated by any LNS service counted during the polling interval.

LNS Services


DescriptionValue

Enables the generation of alerts or alarms based on the number of GPRSsessions or the number of r GPRS PDP contexts (active and dormant)facilitated by any GPRS service counted during the polling interval.

GPRS Services

Enables the generation of alerts or alarms based on the number of SGSNsessions or the number of SGSNPDP contexts (active and dormant) facilitatedby any SGSN service counted during the polling interval.

SGSN Services


Per-PDSN Service ThresholdsPer-PDSN service thresholds generate alerts or alarms based on the total number of sessions facilitated byany PDSN service configured on the system during the specified polling interval.

Alerts or alarms are triggered for sessions per-PDSN service based on the following rules:

• Enter condition: Actual total number of sessions > or = High Threshold

• Clear condition: Actual total number of sessions < Low Threshold


This section provides instructions for configuring per-PDSN service thresholding. These instructions assumethat you are at the prompt for the Global Configuration mode:

Configuring Per-PDSN Service ThresholdsUse the following example to configure the per-PDSN service thresholds:

configurethreshold per-service-pdsn-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-pdsn-sessions interval <time>threshold monitoring subscriberend

Per-HA Service ThresholdsPer-HA service thresholds generate alerts or alarms based on the total number of sessions facilitated by anyHA service configured on the system during the specified polling interval.


Per-service Session ThresholdsSaving Your Configuration

Alerts or alarms are triggered for sessions per-HA service based on the following rules:




Configuring Per-HA Service ThresholdsConfigure the per-HA service thresholds by entering the following command:

configurethreshold per-service-ha-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-ha-sessions interval <time>threshold monitoring subscriberend

Per-GGSN Service ThresholdsPer-GGSN service thresholds generate alerts or alarms based on the total number of PDP contexts facilitatedby any GGSN service configured on the system during the specified polling interval.

Alerts or alarms are triggered for sessions per-GGSN service based on the following rules:

• Enter condition: Actual total number of PDP contexts > or = High Threshold

• Clear condition: Actual total number of PDP contexts < Low Threshold


Configuring Per-GGSN Service ThresholdsUse the following example to configure the per-GGSN service thresholds:

configurethreshold per-service-ggsn-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-ggsn-sessions interval <time>threshold monitoring subscriberend

Per-LNS Service ThresholdsPer-LNS service thresholds generate alerts or alarms based on the total number of sessions facilitated by anyLNS service configured on the system during the specified polling interval.

Alerts or alarms are triggered for sessions per-LNS service based on the following rules:



Per-service Session ThresholdsConfiguring Per-HA Service Thresholds



Configuring Per-LNS Service ThresholdsUse the following example to configure the per-LNS service thresholds:

configurethreshold per-service-lns-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-lns-sessions interval <time>threshold monitoring subscriberend

Per-GPRS Service ThresholdsPer-GPRS service thresholds generate alerts or alarms based on the total number of attached subscribersfacilitated by any GPRS service configured on the system during the specified polling interval.

Alerts or alarms are triggered for sessions per-GPRS service based on the following rules:

• Enter condition: Actual total number of attached subscribers > or = High Threshold

• Clear condition: Actual total number of attached subscribers < Low Threshold


Configuring Per-GPRS Service ThresholdsUse the following example to configure the per-GGSN service thresholds:

configurethreshold per-service-gprs-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-gprs-sessions interval <time>threshold monitoring subscriberend

Per-GPRS Service PDP Contexts ThresholdsPer-GPRS service PDP context thresholds generate alerts or alarms based on the total number of PDP contextsfacilitated by any GPRS service session configured on the system during the specified polling interval.

Alerts or alarms are triggered for sessions per-GPRS service based on the following rules:




Per-service Session ThresholdsConfiguring Per-LNS Service Thresholds


Configuring Per-GPRS Service PDP Contexts ThresholdsUse the following example to configure the per-GPRS service PDP contexts thresholds:

configurethreshold per-service-gprs-pdp-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-gprs-pdp sessions interval <time>threshold monitoring subscriberend

Per-SGSN Service ThresholdsPer-SGSN service thresholds generate alerts or alarms based on the total number of attached subscribersfacilitated by any SGSN service configured on the system during the specified polling interval.

Alerts or alarms are triggered for sessions per-SGSN service based on the following rules:




Configuring Per-SGSN Service ThresholdsUse the following example to configure the per-SGSN service thresholds:

configurethreshold per-service-sgsn-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-sgsn-sessions interval <time>threshold monitoring subscriberend

Per-SGSN Service PDP Contexts ThresholdsPer-SGSN service PDP context thresholds generate alerts or alarms based on the total number of PDP contextsfacilitated by any SGSN service session configured on the system during the specified polling interval.

Alerts or alarms are triggered for sessions per-SGSN service based on the following rules:





Per-service Session ThresholdsConfiguring Per-GPRS Service PDP Contexts Thresholds

Configuring Per-SGSN Service PDP Contexts ThresholdsUse the following example to configure the per-SGSN service PDP contexts thresholds:

configurethreshold per-service-sgsn-pdp-sessions <high_thresh> [ clear<low_thresh> ]threshold poll per-service-sgsn-pdp sessions interval <time>threshold monitoring subscriberend


Per-service Session ThresholdsConfiguring Per-SGSN Service PDP Contexts Thresholds

C H A P T E R 22Port Utilization Thresholds

• Port Utilization Thresholds, page 73


• Receive Port Utilization Thresholds, page 74

• Transmit Port Utilization Thresholds, page 74

• High Port Activity Thresholds, page 75

Port Utilization ThresholdsThreshold monitoring can be enabled for the port utilization values described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on the port utilizationpercentage for data received during the polling interval.

Receive port utilization

Enables the generation of alerts or alarms based on the port utilizationpercentage for data transmitted during the polling interval.

Transmit port utilization

Enables the generation of alerts or alarms based on the overall portutilization percentage during the polling interval.

High port activity

Ports configured for half-duplex do not differentiate between data received and data transmitted. (Thetransmitted and received percentages are combined.) Therefore, to avoid redundant alarms, it isrecommended that only the receive or transmit utilization threshold be configured.

Note

Saving Your ConfigurationWhen you configure thresholds they are not permanent unless you save the changes.When you have completedconfiguring thresholds, save your configuration to flash memory, an external memory device, and/or a network


location using the Exec mode command save configuration. For additional information on how to verify andsave configuration files, refer to the System Administration Guide and theCommand Line Interface Reference.

Receive Port Utilization ThresholdsReceive port utilization thresholds generate alerts or alarms based on the utilization percentage of eachconfigured port in relation to data received during the specified polling interval. This threshold is configuredon a per-port basis.

Alerts or alarms are triggered for receive port utilization based on the following rules:

• Enter condition: Actual percent utilization of a port for received data > or = High Threshold

• Clear condition: Actual percent utilization of a port for received data < Low Threshold


Configuring Receive Port Utilization ThresholdsUse the following example to configure the polling interval over which to measure receive port utilization

configurethreshold poll port-rx-utilization interval <seconds>port <port-type> <slot/port>threshold rx-utilization <high_thresh_> [ clear <low_thresh_> ]threshold monitoring

end

Transmit Port Utilization ThresholdsTransmit port utilization thresholds generate alerts or alarms based on the utilization percentage of eachconfigured port in relation to data transmitted during the specified polling interval. This threshold is configuredon a per-port basis.

Alerts or alarms are triggered for transmit port utilization based on the following rules:

• Enter condition: Actual percent utilization of a port for transmit data > or = High Threshold

• Clear condition: Actual percent utilization of a port for transmit data < Low Threshold


Configuring Transmit Port Utilization ThresholdsUse the following example to configure the polling interval over which to measure transmit port utilization:

configurethreshold poll port-tx-utilization interval <seconds>port <port-type> <slot/port>threshold tx-utilization <high_thresh_> [ clear <low_thresh_> ]


Port Utilization ThresholdsReceive Port Utilization Thresholds

threshold monitoringend

High Port Activity ThresholdsHigh port activity thresholds generate alerts or alarms based on the peak utilization percentage of eachconfigured port during the specified polling interval. This threshold is configured on a per-port basis.

Alerts or alarms are triggered for high port activity based on the following rules:

• Enter condition: Actual percent peak utilization of a port > or = High Threshold

• Clear condition: Actual percent peak utilization of a port < Low Threshold


Configuring High Port Activity ThresholdsUse the following example to configure the polling interval over which to measure for high port activity:

configurethreshold poll port-high-activity interval <time>port <port-type> <slot/port>threshold high-activity <high_thresh_> [ clear <low_thresh_> ]threshold monitoring

end


Port Utilization ThresholdsHigh Port Activity Thresholds


Port Utilization ThresholdsConfiguring High Port Activity Thresholds

C H A P T E R 23SaMOG Thresholds

• SaMOG Thresholds, page 77

• Configuring SaMOG Thresholds, page 77


SaMOG ThresholdsPer-samog-service threshold generate alerts or alarms based on either the total number of SaMOG sessionsfacilitated by any samog-service configured on the system duringf the specified polling interval

Alerts or alarms are triggered for sessions per-samog-service based on the following rules:

• Enter Condition: Actual total number of SaMOG sessions > or = High Threshold

• Clear Condition: Actual total number of SaMOG sessions < Low Threshold

Configuring SaMOG ThresholdsUse the following configuration example for the samog-service session count threshold crossing alerts:

configurethreshold per-service-samog-sessions <high_thresh> [ clear <low_thresh> ]threshold poll per-service-samog-sessions interval <dur>threshold monitoring subscriberend

Saving Your ConfigurationWhen you configure thresholds they are not permanent unless you save the changes.When you have completedconfiguring thresholds, save your configuration to flash memory, an external memory device, and/or a networklocation using the Exec mode command save configuration For additional information on how to verify andsave configuration files, refer to the System Administration Guide and theCommand Line Interface Reference.



SaMOG ThresholdsSaving Your Configuration

C H A P T E R 24Session License Utilization Thresholds

• Session License Utilization Thresholds, page 79

• Configuring Session License Utilization Thresholds, page 79


Session License Utilization ThresholdsSession license utilization thresholds generate alerts or alarms based on the utilization percentage of all sessioncapacity licenses during the specified polling interval.

The system uses session capacity licenses to dictate the maximum number of simultaneous sessions that canbe supported. There are multiple session types that require licenses (i.e. Simple IP, Mobile IP, L2TP, etc.).Although, a single threshold is configured for all session types, alerts or alarms can be generated for eachtype.

Alerts or alarms are triggered for session license utilization based on the following rules:

• Enter condition: Actual session license utilization percentage per session type < Low Threshold

• Clear condition: Actual session license utilization percentage per session type > High Threshold


Configuring Session License Utilization ThresholdsUse the following example to configure the thresholds for session license utilization:configurethreshold license-remaining-sessions <low_thresh> [ clear <high_thresh> ]threshold poll license-remaining-sessions interval <time>threshold monitoring licenseend




Session License Utilization ThresholdsSaving Your Configuration

C H A P T E R 25Stateful Firewall Thresholds

• Stateful Firewall Thresholds, page 81

• Configuring Stateful Firewall Thresholds, page 81


Stateful Firewall ThresholdsThresholds generate alerts or alarms based on either the total number of Stateful Firewall calls setup by thesystem during the specified polling interval, or on the number of currently active calls only.



• Clear condition: Actual number of call setups < Low Threshold.




Configuring Stateful Firewall ThresholdsThis section describes how to enable and configure Stateful Firewall thresholds.


configurethreshold monitoring firewallend


Configuring Threshold Polling IntervalsTo configure threshold poll interval use the following configuration:

configurethreshold poll fw-deny-rule interval <interval>threshold poll fw-dos-attack interval <interval>threshold poll fw-drop-packet interval <interval>threshold poll fw-no-rule interval <interval>end

Configuring Thresholds LimitsTo configure threshold limits use the following configuration:

configurethreshold fw-deny-rule <high_thresh> [ clear <low_thresh> ]threshold fw-dos-attack <high_thresh> [ clear <low_thresh> ]threshold fw-drop-packet <high_thresh> [ clear <low_thresh> ]threshold fw-no-rule <high_thresh> [ clear <low_thresh> ]end



Stateful Firewall ThresholdsConfiguring Threshold Polling Intervals

C H A P T E R 26Subscriber Thresholds

• Subscriber Thresholds, page 83


• Total Subscriber Thresholds, page 83

• Active Subscriber Thresholds, page 84

Subscriber ThresholdsThreshold monitoring can be enabled for the subscriber values described in the following table.

DescriptionValue

Enables the generation of alerts or alarms based on the total number subscribersessions (active and dormant) counted during the polling interval.

Total subscribers

Enables the generation of alerts or alarms based on the total number ofsubscribers with active sessions counted during the polling interval.

Active subscribers


Total Subscriber ThresholdsTotal subscriber thresholds generate alerts or alarms based on the total number of subscriber sessions (activeand 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 > or = High Threshold

• Clear condition: Actual total number of subscriber sessions < Low Threshold


This section provides instructions for configuring total subscriber thresholding. These instructions assumethat you are at the prompt for the Global Configuration mode:

Configuring Total Subscriber ThresholdsUse the following example to configure the total subscriber thresholds:

configurethreshold subscriber total <high_thresh> [ clear <low_thresh> ]threshold poll total-subscriber interval <time>threshold monitoring subscriberend

Active Subscriber ThresholdsActive subscriber thresholds generate alerts or alarms based on the total number of active subscriber sessionsfacilitated 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 > or = High Threshold

• Clear condition: Actual total number of active subscriber sessions < Low Threshold


This section provides instructions for configuring active subscriber thresholding. These instructions assumethat you are at the prompt for the Global Configuration mode:

Configuring Active Subscriber ThresholdsUse the following example to configure the active subscriber thresholds:

configurethreshold subscriber active <high_thresh> [ clear <low_thresh> ]threshold poll active-subscriber interval <time>threshold monitoring subscriberend


Subscriber ThresholdsConfiguring Total Subscriber Thresholds

C H A P T E R 27System Management Card CompactFlash MemoryThresholds

• System Management Card CompactFlash Memory Thresholds, page 85


System Management Card CompactFlash Memory ThresholdsSystemmanagement card CompactFlash memory utilization thresholds generate alerts or alarms based on thepercentage of memory used for the CompactFlash during the polling interval. A single threshold enablesmemory utilization monitoring for both the active and standby system management cards allowing for alertsor alarms to be generated for each CompactFlash.

Alerts or alarms are triggered for CompactFlash memory utilization based on the following rules:

• Enter condition: Actual percentage memory utilization > or = High Threshold

• Clear condition: Actual percentage memory utilization < Low Threshold





System Management Card CompactFlash Memory ThresholdsSaving Your Configuration

C H A P T E R 28Total Session Thresholds

• Total Session Thresholds, page 87


• Total PDSN Session Thresholds, page 89

• Total GGSN Session Thresholds, page 89

• Total GPRS Session Thresholds, page 90

• Total GPRS PDP Contexts Thresholds, page 90

• Total HA Session Thresholds, page 91

• Total HeNB-GW Session Thresholds, page 91

• Total HNB-GW Session Thresholds, page 92

• Total HSGW Session Thresholds, page 93

• Total LMA Session Thresholds, page 94

• Total LNS Session Thresholds, page 94

• Total MME Session Thresholds, page 95

• Total P-GW Session Thresholds, page 95

• Total SAEGW Session Thresholds, page 96

• Total SGSN Session Thresholds, page 96

• Total SGSN PDP Contexts Thresholds, page 97

• Total S-GW Session Thresholds, page 97

Total Session ThresholdsThreshold monitoring can be enabled for the total session counts described in the following table.


DescriptionValue

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by all PDSN services counted during thepolling interval.

PDSN Services

Enables the generation of alerts or alarms based on the total number of PDPcontexts (active and dormant) facilitated by all GGSN services counted duringthe polling interval.

GGSN Services

Enables the generation of alerts or alarms based on the total number of GPRSsessions or the total number of PDP sessions facilitated by the GPRS servicescounted during the polling interval.

GPRS Services

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by all HA services counted during the pollinginterval.

HA Services

Enables the generation of alerts or alarms based on the total number of HeNBand UE sessions (active and dormant) facilitated by all HeNB-GW servicescounted during the polling interval.

HeNB-GW Services

Enables the generation of alerts or alarms based on the total number of HNB,UE, Iu sessions (active and dormant) facilitated by all HNB-GW servicescounted during the polling interval.

HNB-GW Services

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by all HSGW services counted during thepolling interval.

HSGW Service

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by all LMA services counted during the pollinginterval.

LMA Service

Enables the generation of alerts or alarms based on the total number of sessionsfacilitated by all LNS services counted during the polling interval.

LNS Services

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by allMME services counted during the pollinginterval.

MME Service

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by all P-GW services counted during thepolling interval.

P-GW Service

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by all SAEGW services counted during thepolling interval.

SAEGW Service


Total Session ThresholdsTotal Session Thresholds

DescriptionValue

Enables the generation of alerts or alarms based on the total number of SGSNsessions or the total number of PDP sessions facilitated by the SGSN servicescounted during the polling interval.

SGSN Services

Enables the generation of alerts or alarms based on the total number of sessions(active and dormant) facilitated by all S-GW services counted during thepolling interval.

S-GW Service


Total PDSN Session ThresholdsTotal PDSN session thresholds generate alerts or alarms based on the total number of sessions facilitated byany PDSN service configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all PDSN sessions based on the following rules:




Configuring Total PDSN Session ThresholdsUse the following example to configure the total PDSN session thresholds:

configurethreshold total-pdsn-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-pdsn-sessions interval <time>threshold monitoring subscriberend

Total GGSN Session ThresholdsTotal GGSN session thresholds generate alerts or alarms based on the total number of PDP contexts facilitatedby all GGSN services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all GGSN PDP contexts based on the following rules:


Total Session ThresholdsSaving Your Configuration




Configuring Total GGSN Session ThresholdsUse the following example to configure the per-GGSN service thresholds:

configurethreshold total-ggsn-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-ggsn-sessions interval <time>end

Total GPRS Session ThresholdsTotal GPRS session thresholds generate alerts or alarms based on the total number of attached subscribersfacilitated by all GPRS services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all subscribers attached to the GPRS based on the followingrules:




Configuring Total GPRS Session ThresholdsUse the following example to configure the per-SGSN service thresholds:

configurethreshold total-gprs-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-gprs-sessions interval <time>end

Total GPRS PDP Contexts ThresholdsTotal GPRS PDP contexts thresholds generate alerts or alarms based on the total number of PDP contextsfacilitated by all GPRS services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all GPRS PDP contexts based on the following rules:




Total Session ThresholdsConfiguring Total GGSN Session Thresholds


Configuring Total GPRS PDP Context ThresholdsUse the following example to configure the per-GPRS service thresholds:

configurethreshold total-gprs-pdp-sessions <high_thresh> [ clear <low_thresh>]threshold poll total-gprs-pdp-sessions interval <time>end

Total HA Session ThresholdsTotal HA session thresholds generate alerts or alarms based on the total number of sessions facilitated by allHA services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all HA sessions based on the following rules:




Configuring Total HA Session ThresholdsUse the following example to configure the total HA session thresholds:

configurethreshold total-ha-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-ha-sessions interval <time>threshold monitoring subscriberend

Total HeNB-GW Session ThresholdsTotal HeNB-GW service session thresholds generate alerts or alarms based on the total number of HeNB andUE sessions facilitated by all HeNB-GW services configured on the system during the specified pollinginterval.

Alerts or alarms are triggered for the total of all sessions based on the following rules:





Total Session ThresholdsConfiguring Total GPRS PDP Context Thresholds

Configuring Total HeNB Session ThresholdsUse the following example to configure the thresholds for total HNB sessions over IuH interface betweenHNB and HNB-GW service on HNB-GW node:

configurethreshold total-henbgw-henb-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-henbgw-henb-sessions interval <time>threshold monitoring henbgw-serviceend

Configuring Total UE Session ThresholdsUse the following example to configure the thresholds for total HeNB-GW UE sessions:

configurethreshold total-henbgw-ue-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-henbgw-ue-sessions interval <time>threshold monitoring henbgw-serviceend

Total HNB-GW Session ThresholdsTotal HNB-GW service session thresholds generate alerts or alarms based on the total number of IuH, IuCS,and IuPS sessions facilitated by all HNB-GW services configured on the system during the specified pollinginterval. Thresholds for IuH session is provided for HNB and UE seperately.

Alerts or alarms are triggered for the total of all IuH, IuCS, or IuPS sessions based on the following rules:




Configuring Total HNB Session ThresholdsUse the following example to configure the thresholds for total HNB sessions over IuH interface betweenHNB and HNB-GW service on HNB-GW node:

configurethreshold total-hnbgw-hnb-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-hnbgw-hnb-sessions interval <time>threshold monitoring hnbgw-serviceend


Total Session ThresholdsConfiguring Total HeNB Session Thresholds

Configuring Total UE Session Thresholds 0Use the following example to configure the thresholds for total UE sessions over IuH interface between HNBand HNB-GW service on HNB-GW node:

configurethreshold total-hnbgw-ue-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-hnbgw-ue-sessions interval <time>threshold monitoring hnbgw-serviceend

Configuring Total Iu Session ThresholdsUse the following example to configure the thresholds for total IuPS and/or IuCS sessions over Iu interfacebetween HNB-GW and CN node:

configurethreshold total-hnbgw-iu-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-hnbgw-iu-sessions interval <time>threshold monitoring hnbgw-serviceend

Total HSGW Session ThresholdsTotal HSGW session thresholds generate alerts or alarms based on the total number of sessions facilitated byall HSGW services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all HSGW sessions based on the following rules:




Configuring Total HSGW Session ThresholdsUse the following example to configure the total HSGW session thresholds:

configurethreshold total-hsgw-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-hsgw-sessions interval <time>threshold monitoring hsgw-serviceend


Total Session ThresholdsConfiguring Total UE Session Thresholds 0

Total LMA Session ThresholdsTotal LMA session thresholds generate alerts or alarms based on the total number of sessions facilitated byall HSGW services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all LMA sessions based on the following rules:




Configuring Total LMA Session ThresholdsUse the following example to configure the total LMA session thresholds:

configurethreshold total-lma-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-lma-sessions interval <time>threshold monitoring lma-serviceend

Total LNS Session ThresholdsTotal LNS session thresholds generate alerts or alarms based on the total number of sessions facilitated by allLNS services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all LNS sessions based on the following rules:




Configuring Total LNS Session ThresholdsUse the following example to configure the total LNS session thresholds:

configurethreshold total-lns-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-lns-sessions interval <time>threshold monitoring subscriberend


Total Session ThresholdsTotal LMA Session Thresholds

Total MME Session ThresholdsTotal MME session thresholds generate alerts or alarms based on the total number of sessions facilitated byall MME services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all MME sessions based on the following rules:




Configuring Total MME Session ThresholdsUse the following example to configure the total P-GW session thresholds:

configurethreshold total-mme-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-mme-sessions interval <time>threshold monitoring mme-serviceend

Total P-GW Session ThresholdsTotal P-GW session thresholds generate alerts or alarms based on the total number of sessions facilitated byall P-GW services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all P-GW sessions based on the following rules:




Configuring Total P-GW Session ThresholdsUse the following example to configure the total P-GW session thresholds:

configurethreshold total-pgw-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-pgw-sessions interval <time>threshold monitoring pgw-serviceend


Total Session ThresholdsTotal MME Session Thresholds

Total SAEGW Session ThresholdsTotal SAEGW session thresholds generate alerts or alarms based on the total number of sessions facilitatedby all SAEGW services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all SAEGW sessions based on the following rules:




Configuring Total SAEGW Session ThresholdsUse the following example to configure the total SAEGW session thresholds:

configurethreshold total-saegw-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-saegw-sessions interval <time>threshold monitoring saegw-serviceend

Total SGSN Session ThresholdsTotal SGSN session thresholds generate alerts or alarms based on the total number of attached subscribersfacilitated by all SGSN services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all subscribers attached to the SGSN based on the followingrules:




Configuring Total SGSN Session ThresholdsUse the following example to configure the per-SGSN service thresholds:

configurethreshold total-sgsn-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-sgsn-sessions interval <time>end


Total Session ThresholdsTotal SAEGW Session Thresholds

Total SGSN PDP Contexts ThresholdsTotal SGSN PDP contexts thresholds generate alerts or alarms based on the total number of PDP contextsfacilitated by all SGSN services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all SGSN PDP contexts based on the following rules:




Configuring Total SGSN PDP Context ThresholdsUse the following example to configure the per-SGSN service thresholds:

configurethreshold total-sgsn-pdp-sessions <high_thresh> [ clear <low_thresh>]threshold poll total-sgsn-pdp-sessions interval <time>end

Total S-GW Session ThresholdsTotal S-GW session thresholds generate alerts or alarms based on the total number of sessions facilitated byall S-GW services configured on the system during the specified polling interval.

Alerts or alarms are triggered for the total of all S-GW sessions based on the following rules:




Configuring Total S-GW Session ThresholdsUse the following example to configure the total S-GW session thresholds:

configurethreshold total-sgw-sessions <high_thresh> [ clear <low_thresh> ]threshold poll total-sgw-sessions interval <time>threshold monitoring sgw-serviceend


Total Session ThresholdsTotal SGSN PDP Contexts Thresholds


Total Session ThresholdsConfiguring Total S-GW Session Thresholds