Global Configuration
Mode Commands
The Global Configuration
Mode is used to configure basic system-wide parameters.
IMPORTANT:
The commands or keywords/variables
that are available are dependent on platform type, product version,
and installed license(s).
aaa accounting-overload-protection
This command configures
Overload Protection Policy for accounting requests.
Privilege:
Security Administrator,
Administrator
Syntax
aaa accounting-overload-protection
prioritize-gtpp
{ default | no } aaa
accounting-overload-protection
default
Configures the default
setting.
Default: no priority
assigned
no
Disables the Overload
Protection configuration.
prioritize-gtpp
Gives higher priority
to GTPP requests among the other outstanding requests. So while purging
the lower priority requests will be selected first.
Usage:
Use this command to
configure Overload Protection Policy for accounting requests.
Example:
The following command
prioritizes GTPP requests among the other outstanding requests:
aaa accounting-overload-protection
prioritize-gtpp
aaa default-domain
Configure global accounting
and authentication default domain for subscriber and context-level
administrative user sessions.
Privilege:
Security Administrator,
Administrator
Syntax
aaa default-domain { administrator | subscriber } domain_name
no aaa default-domain { administrator | subscriber }
no
Removes all or only
the specified configured domain.
administrator | subscriber
administrator:
Configures the default domain for context-level administrative users.
subscriber:
Configures the default domain for subscribers.
domain_name
Sets the default context.
domain_name must
be an alphanumeric string of 1 through 79 characters.
Usage:
This command configures
the default domain which is used when accounting and authentication
services are required for context-level administrative user and
subscriber sessions whose user name does not include a domain.
Example:
The following commands
configure the default domains for context-level administrative users
and subscribers, respectively:
aaa default-domain
administrator sampleAdministratorDomain
aaa default-domain
subscriber sampleSubscriberDomain
aaa domain-matching
ignore-case
This command disables
case sensitivity when performing domain matching. When this command
is enabled, the system disregard case when matching domains.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] aaa
domain-matching ignore-case
default aaa domain-matching
default
Configures ignore-case
as the domain matching method.
no
Specifies that the
system consider case when domain matching.
Usage:
Use this command to
configure the system to ignore case when matching domains.
Example:
The following command
configures the system to ignore case when matching domains:
aaa domain-matching
ignore-case
aaa domain-matching
imsi-prefix
Enables domain lookup
for session based on the International Mobile Subscriber Identity
(IMSI) prefix length. Default: Disabled
IMPORTANT:
This command is only
available in 8.3 and later releases.
Privilege:
Security Administrator,
Administrator
Syntax
aaa domain-matching
imsi-prefix prefix-length prefix_length
no aaa domain-matching
imsi-prefix
default aaa domain-matching
no
Specifies the system
must not consider imsi-prefix domain matching method.
prefix-length
Specifies the IMSI
length to be matched with the domain.
prefix_length must
be an integer from 1 through 15.
Usage:
Use this command to
configure the IMSI-prefix method of domain matching. This command
enables domain lookup for the session based on the IMSI prefix length.
If there is a domain configured with the matching IMSI prefix, the
associated configuration is used.
This feature does
not support partial matches.
Example:
The following command
configures the IMSI prefix method for domain matching setting the prefix
length to
10.
aaa domain-matching
imsi-prefix prefix-length 10
aaa large-configuration
This command enables
or disables the system to accept a large number of RADIUS configurations
to be defined and stored.
IMPORTANT:
For this command to
take affect, after entering the command the configuration must be
saved and reloaded.
When aaa large-configuration
is disabled, the following restrictions are in place:
- Only one (1) NAS IP
address can be defined per context with the radius attribute command.
- The RADIUS attribute nas-ip-address can
only be configured if the RADIUS group is default.
- Only 320 RADIUS servers
can be configured system-wide.
- Only 64 RADIUS groups
can be configured system-wide.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] aaa
large-configuration
no
Disables AAA large
configuration support.
Usage:
When aaa large-configuration
is enabled, the system provides the ability to configure multiple
NAS IP addresses in a single context to used with different radius
groups. As well, the command allows support for up to 1,600 RADIUS
server configurations and
for
a PDSN a maximum of 400 or
for a GGSN a maximum of 800 RADIUS server group configurations
system-wide.
Example:
To enable the definition
of a large number of RADIUS configurations, enter the following commands
in the following order:
In APN Configuration
mode, enter:
default aaa group
In Global Configuration
mode, enter:
aaa large-configuration
In Exec mode, use
the save configuration command
and then the reload command.
aaa last-resort
Configure global accounting
and authentication last resort domain for subscriber and context-level
administrative user sessions.
Privilege:
Security Administrator,
Administrator
Syntax
aaa last-resort context { administrator | subscriber context_name }
no aaa last-resort
context { administrator | subscriber }
no
Removes all or only
the specified previously configured authentication last resort domain name.
administrator | subscriber
administrator:
Configures the last resort domain for context-level administrative.
subscriber:
Configures the last resort domain for the subscribers.
context_name
Specifies the context
which is to be set as the last resort. context_name must
be an alphanumeric string of 1 to 79 characters.
Usage:
Set the last resort
context which is used when there is no applicable default domain (context)
and there is no domain provided with the subscriber’s or
context-level administrative user’s name for use in the
AAA functions.
Example:
The following commands
configure the last resort domains for context-level administrative user
and subscribers, respectively:
aaa last-resort administrator sampleAdministratorDomain
aaa last-resort subscriber sampleSubscriberDomain
The following command
removes the previously configured domain called
sampleAdministratorDomain:
no aaa last-resort
administrator sampleAdministratorDomain
aaa tacacs+
This command enables
or disables system-wide TACACS+ AAA (authentication, authorization
and accounting) services for administrative users. This command
is valid only if TACACS+ servers and related services have
been configured in TACACS Configuration Mode.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] aaa
tacacs+
Usage:
Enables or disables
the use of TACACS+ AAA services for administrative users.
Example:
aaa tacacs+
no aaa tacacs+
aaa username-format
Configure global accounting
and authentication user name formats for AAA (authentication, authorization
and accounting) functions. Up to six formats may be configured.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] aaa
username-format { domain | username } separator
default aaa username-format
no
Removes the specified
user name format from the configuration.
domain | username
Default: username @
domain:
indicates the left side of the string from the separator character
is a domain name and the right side is the user name.
username:
indicates the left side of the string from the separator character
is a user name and the right side is the domain name.
IMPORTANT:
The user name string
is always searched from right to left for the first occurrence of
the separator character.
separator
Specifies the character
to use to delimit the domain from the user name for global AAA functions.Permitted
characters include: @, %, -, \, #,
or /. To specify a back slash (’\’)
as the separator, you must enter a double back slash (‘\\’)
on the command line.
Usage:
Define the formats
for user name delimiting if certain domains or groups of users are
to be authenticated based upon their user name versus domain name.
Example:
aaa username-format
domain @
aaa username-format
username %
no aaa username-format
username %
active-charging
service
This command allows
you to create/configure/delete the Active Charging
Service (ACS)/Enhanced Charging Service (ECS).
Privilege:
Security Administrator,
Administrator
Syntax
active-charging service acs_service_name [ -noconfirm ]
no active-charging
service acs_service_name
no
Deletes the specified
Active Charging Service.
acs_service_name
Specifies name of
the Active Charging Service.
acs_service_name must
be the name of an Active Charging Service, and must be an alphanumeric
string of 1 through 15 characters.
If the named Active
Charging Service does not exist, it is created, and the CLI mode
changes to the ACS Configuration Mode wherein the service can be
configured. If the named Active Charging Service already exists,
the CLI mode changes to the ACS Configuration Mode.
-noconfirm
Specifies that the
command must execute without any additional prompt and confirmation from
the user.
Usage:
Use this command to
create/configure/delete an Active Charging Service
in the system. Note that, in this release, only one Active Charging
Service can be created in the system.
Use this command after
enabling ACS using the require active-charging command.
This command allows administrative users to configure the ACS functionality.
On entering this command,
the CLI prompt changes to:
[context_name]hostname(config-acs)#
Example:
The following command
creates an ACS service named
test:
active-charging service test
alarm
Enables or disables
alarming options for the SPIO card or the SSC internal alarms and
the central-office external alarms. To verify the state of the alarms,
refer to the show
alarm command.
Privilege:
Security Administrator,
Administrator
Syntax
alarm { audible | central-office }
no alarm { audible | central-office }
no
Disables the option
specified.
audible | central-office
audible:
indicates the internal audible alarm on the SPIO cards or SSCs are
to be enabled.
central-office:
indicates the central office alarms are to be enabled.
Usage:
Disable CO and audible
alarms when an existing device provides such capability.
Example:
The following commands
enable the SPIO card or SSC internal alarms and disable the central
office alarms, respectively.
alarm audible
no alarm central-office
apn-profile
Creates an instance
of an Access Point Name (APN) profile.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] apn-profile apn_profile_name
no
Deletes the APN profile
instance from the configuration.
apn_profile_name
Specifies the name
of the APN profile. Enter an alphanumeric string of 1 through 64 characters.
Usage:
Use this command to
create an instance of an APN profile and to enter the APN profile configuration
mode. An APN profile is a template which groups a set of APN-specific commands
that may be applicable to one or more APNs. See the APN Profile Configuration Mode
Commands chapter for information regarding the definition of
the rules contained within the profile and the use of the profile.
IMPORTANT:
An APN profile is a
key element of the Operator Policy feature and is only valid when associated
with at least one operator policy.
To see what APN profiles
have already been created, return to the Exec mode and enter the show apn-profile all command.
Example:
The following command
creates a configuration instance of an APN profile:
apn-profile apnprof27
apn-remap-table
Creates an instance
of an Access Point Name (APN) remap table.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] apn-remap-table apn_remap_table_name
no
Deletes the APN remap
table instance from the configuration.
apn_remap_table_name
Specifies the name
of the APN remap table. Enter an alphanumeric string of 1 through
65 characters.
Usage:
Use this command to
create an instance of an APN remap table and to enter the APN remap
table configuration mode. An APN remap table includes entries that
define how an incoming APN, or the lack on one, will be handled.
See the APN Remap Table Configuration
Mode Commands chapter for information regarding the definition
of the entries contained within the table and the use of the table.
IMPORTANT:
An APN remap table
is a key element of the Operator Policy feature and is only valid
when associated with at least one operator policy.
To see what APN remap
tables have already been created, return to the Exec mode and enter
the show apn-remap-table
all command.
Example:
The following command
creates a configuration instance of an APN remap table:
apn-remap-table pnremap-USorigins-table1
arp
Configures a system-wide
time interval for performing Address Resolution Protocol (ARP) refresh.
Privilege:
Security Administrator,
Administrator
Syntax
arp base-reachable-time time
default arp base-reachable-time
default
Restores the parameter
to its default setting.
time
Default: 30
Specifies the ARP
refresh interval (in seconds) as an integer from 30 through 86400.
Usage:
Use this command to
configure a system-wide ARP refresh interval. Once a neighbor is found,
the entry is considered valid for at least a random value between
the time/2
and the time*1.5.
Example:
The following command
configures an ARP refresh interval of 1 hour:
arp base-reachable-time 3600
autoconfirm
This command disables
or enables confirmation for certain commands. This command affects
all future CLI sessions.
IMPORTANT:
To change the behavior
for the current CLI session only, use the autoconfirm command
in the Exec Mode.
Privilege:
Security Administrator,
Administrator, Operator
Syntax
autoconfirm
no autoconfirm
Usage:
When autoconfirm is
enabled, certain commands ask you to answer yes or no to confirm that
you want to execute the command. When autoconfirm is disabled the
confirmation questions never appear. Disabling autoconfirm disables
command confirmation for all future CLI sessions.
By default autoconfirm is
enabled.
Example:
The following command
enables command confirmation for all future CLI sessions;
autoconfirm
The following command
disables command confirmation for all future CLI sessions;
no autoconfirm
autoless
This command is obsolete.
It is included in the CLI for backward compatibility with older
configuration files. When executed, this command issues a warning
and performs no function.
banner
Configures the CLI
banner which is displayed upon the start of a CLI session.
Privilege:
Security Administrator,
Administrator
Syntax
banner { charging-service | lawful-intercept | motd | pre-login } string
no banner { charging-service | lawful-intercept | motd | pre-login }
no
Removes the banner
message by setting it to be a string of zero length.
charging-service
Specifies the Active
Charging Service banner message. The banner is displayed upon initialization
of an SSH CLI session with ACS-admin privileges (whenever anyone
with the CLI privilege bit for ACS logs on).
lawful-intercept
Refer to the Lawful Intercept Configuration
Guide for a description of this parameter.
motd
Configures the CLI
banner message of the day which is displayed upon the initialization
of any CLI session.
pre-login
Configures the CLI
banner displayed before a CLI user logs in.
IMPORTANT:
This banner is displayed
only for serial port and telnet log ins. It is not supported in
ssh and, therefore, will not be displayed before ssh log ins.
string
Specifies the banner
or message to be displayed at session initialization. string may
be an alphanumeric string of 0 through 2048 characters. The string
must be enclosed in double quotation marks if the banner or message
is to include spaces.
Usage:
Set the message of
the day banner when an important system wide message is needed.
For example, in preparation for removing a chassis from service,
set the banner 1 or more days in advance to notify administrative
users of the pending maintenance.
Example:
banner motd “Have
a nice day.”
banner motd No_News_Today
no banner motd
boot delay
Configures the delay
period, in seconds, before attempting to boot the system from a
software image file residing on an external network server.
Privilege:
Security Administrator,
Administrator
Syntax
boot delay time
no boot delay
no
Deletes the setting
for the boot delay. The boot process executes immediately.
time
Specifies the amount
of time (in seconds) to delay prior to requesting the software image from
the external network server as an integer from 1 through 300.
Usage:
Useful when booting
from the network when connection delays may cause timeouts. Such as
when the Spanning Tree Protocol is used on network equipment.
IMPORTANT:
The settings for this
command are stored immediately in the boot.sys file. No changes
are made to the system configuration file.
Example:
The following sets
the boot delay to
10 seconds:
boot delay 10
boot interface
Configures Ethernet
network interfaces for obtaining a system software image during
the system boot process.
Privilege:
Security Administrator,
Administrator
Syntax
Releases prior to 12.2:
boot interface { spio-eth1 | spio-eth2 } [ medium { auto | speed medium_speed duplex medium_duplex } [ media medium_media ] ]
no boot interface
Releases after 12.2:
boot interface { local-eth1 | local-eth2 } [ medium { auto | speed medium_speed duplex medium_duplex } [ media medium_media ] ]
no boot interface
no
Removes the boot interface
configuration from the boot.sys file. Only files from the local file
system can be loaded.
spio-eth1 | spio-eth2
Specifies the network
interface to be configured where spio-eth1 is
the primary interface on the SPIO (slot 24 interface 1 or slot 25
interface 1) and spio-eth2 is
the secondary interface on the SPIO (slot 24 interface 2 or slot
25 interface 2). The interfaces are either RJ-45 ifor speeds of
10, 100, or 1000 megabits per second (Mbps), or SFP for the optical
Gigabit (1000 Mbps).
local-eth1 | local-eth2
Specifies the network
interface to be configured where local-eth1 is
the primary ethernet interface and local-eth2 is
the secondary ethernet interface.
For the ASR 5000,
the primary is interface 1 on the SPIO and the secondary is interface
2 on the SPIO. The interfaces are either RJ-45 ifor speeds of 10,
100, or 1000 megabits per second (Mbps), or SFP for optical Gigabit
(1000 Mbps).
For the ASR 5500,
the primary is port 1 (1000Base-T) on the MIO and the secondary interface
is port 2 (1000Base-T) on the MIO.
medium { auto | speed medium_speed duplex medium_duplex }
Default: auto
auto: configures
the interface to auto-negotiate the interface speed. and duplex.
speed medium_speed duplex medium_duplex:
specifies the speed to use at all times where
medium_speed must
be one of:
The keyword
duplex is
used to set the communication mode of the interface where
medium_duplex must
be one of:
media medium_media
Default: rj45
Optionally sets the
physical interface where medium_media must
be either rj45 or sfp.
Usage:
Modify the boot interface
settings to ensure the system is able to obtain a software image from
an external network server.
IMPORTANT:
The settings for this
command are stored immediately in the boot.sys file. No changes
are made to the system configuration file.
Example:
The following configures
the primary interface to auto-negotiate the speed.
boot interface spio-eth1
medium auto
boot interface local-eth1
medium auto
The following command
configures the secondary interface to a fixed gigabit speed at full duplex
using RJ45 connectors for the physical interface.
boot interface spio-eth2
medium speed 1000 duplex full media rj45
boot interface local-eth2
medium speed 1000 duplex full media rj45
The following restores
the defaults for the boot interface.
no boot interface
boot nameserver
Configures the IP
address of the DNS (Domain Name Service) server to use when looking
up hostnames in URLs for network booting.
Privilege:
Security Administrator,
Administrator
Syntax
boot nameserver ip_address
no boot nameserver
no
Removes the network
boot nameserver information from the boot.sys file.
ip_address
IPv4 dotted-decimal
address of the DNS server the system uses to lookup hostnames in URLs
for a software image from the network during the system boot process.
Usage:
Use this command to
identify the DNS server to use to lookup hostnames in a software image
URL.
IMPORTANT:
The settings for this
command are stored immediately in the boot.sys file. No changes
are made to the system configuration file.
Example:
The following configures
the system to communicate with a DNS nameserver with the IP address
of 10.2.3.4:
boot nameserver 10.2.3.4
boot networkconfig
Configures the networking
parameters for the Switch Processor I/O card network interfaces
to use when obtaining a software image from an external network
server during the system boot process.
Privilege:
Security Administrator,
Administrator
Syntax
boot networkconfig { dhcp | { { dhcp-static-fallback | static } ip
address spio24 ip_address [ spio25 ip_address ] netmask ip_mask [ gateway gw_address ] } }
no boot networkconfig
no
Removes the network
configuration information from the boot.sys file.
dhcp
Indicates that a Dynamic
Host Control Protocol (DHCP) server is used for communicating with
the external network server.
dhcp-static-fallback | static
dhcp-static-fallback:
provides static IP address fallback network option when a DHCP server
is unavailable.
static:
specifies a fixed network IP address for the external network server
that hosts the software image.
spio24 ip_address [ spio25 ip_address ] netmask ip_mask [ gateway gw_address ]
spio24 ip_address [ spio25 ip_address ]:
the IP address to use for the SPIO in slot 24 and optionally the
SPIO in slot 25 for network booting. ip_address must
be specified using IPv4 dotted-decimal notation.
netmask ip_mask:
the network mask to use in conjunction with the IP address(es) specified
for network booting. ip_mask must
be specified using IPv4 dotted-decimal notation.
gateway gw_address:
the IP address of a network gateway to use in conjunction with the
IP address(es) specified for network booting. gw_address must
be entered using IPv4 dotted-decimal notation.
IMPORTANT:
If gw_address is
not specified, the network server must be on the same LAN as the
system. Since both SPIOs must be in the same network, the netmask
and gateway settings are shared.
Usage:
Configure the network
parameters for the ports on the SPIO cards to use to communicate with
an external network server that hosts software images.
IMPORTANT:
The settings for this
command are stored immediately in the boot.sys file. No changes
are made to the system configuration file.
IMPORTANT:
When configuring static
addresses both SPIOs must have different IP addresses. Neither address
can be the same as the local context IP address.
Example:
The following configures
the system to communicate with the external network server via DHCP
with a fallback to IP address
192.168.100.10,
respectively.
boot networkconfig
dhcp-static-fallback ip address spio24 192.168.100.10 netmask 255.255.255.0
The following command
configures the system to communicate with an external network server
using the fixed (static) IP address
192.168.100.10 with
a network mask of
255.255.255.0.
boot networkconfig
static ip address spio24 192.168.100.10 netmask 255.255.255.0
The following restores
the system default for the network boot configuration options.
no boot networkconfig
boot system priority
Specifies the priority
of a boot stack entry to use when the system first initializes or
restarts. Up to 10 boot system priorities (entries in the boot.sys
file located in the /flash device in the SPC, SMC or MIO)
can be configured.
Privilege:
Security Administrator,
Administrator
Syntax
boot system priority number image image_url config config_path
no boot system priority number
no
Remove a boot stack
entry at the priority specified from the boot stack when it is no
longer used.
priority number
Specifies the priority
for the file group (consisting of an image (.bin) and its corresponding configuration
(.cfg) file) specified in the boot stack. The value must be in the
range from 1 through 100 where a priority of 1 is the highest. Up
to 10 boot system priorities (boot stack entries) can be configured.
IMPORTANT:
When performing a
software upgrade it is important that the new file group have the
highest priority (lowest value) configured.
IMPORTANT:
To ensure that higher
priority numbers remain open, use an “N-1” priority
numbering methodology, where “N” is the first
priority in the current boot stack.
image image_url
Specifies the location
of a image file to use for system startup. The URL may refer to
a local or a remote file. The URL must be formatted according to
the following format:
For the ASR 5000:
- [ file: ]{ /flash | /pcmcia1 | /hd }[ /directory ]/filename
- [ http: | tftp: ]//host[ :port ][ /directory ]/filename
IMPORTANT:
Use of the SMC hard
drive is not supported in this release.
IMPORTANT:
Do not use the following
characters when entering a string for the field names below: “/” (forward
slash), “:” (colon) or “@” (at
sign).
directory is
the directory name.
filename is
the actual file of interest.
host is
the IP address or host name of the server.
port# is
the logical port number that the communication protocol is to use.
IMPORTANT:
A file intended for
use on an ASR 5000 uses the convention xxxxx.asr5000.bin, where xxxxx
is the software build number.
IMPORTANT:
When using the TFTP,
it is advisable to use a server that supports large blocks, per
RFC 2348. This can be implemented by using the “block size
option” to ensure that the TFTP service does not restrict
the file size of the transfer to 32MB.
config config_path
Specifies the location
of a configuration file to use for system startup. This must be formatted
according to the following format:
For the ASR 5000:
- [ file: ]{ /flash | /pcmcia1 | /hd }[ /path ]/filename
IMPORTANT:
Use of the SMC hard
drive is not supported in this release.
Where path is
the directory structure to the file of interest, and filename is
the name of the configuration file. This file typically has a .cfg extension.
Usage:
This command is useful
in prioritizing boot stack entries in the boot.sys file, typically located
on the /flash device of the Active SPC, SMC, or MIO, for
automatic recovery in case of a failure of a primary boot file group.
IMPORTANT:
The configuration
file must reside on the SPC’s, SMC’s, or MIO’s
local filesystem, stored on one of its local devices (/flash,
or /pcmcia1, or /hd-raid/pcmcia1, or /pcmcia2,
or /usb1, or /hd-raid). Attempts to load the configuration
file from an external network server will result in a failure to
load that image and configuration file group, causing the system
to load the image and configuration file group with the next highest
priority in the boot stack.
IMPORTANT:
Configuration changes
do not take effect until the system is reloaded.
IMPORTANT:
The settings for this
command are stored immediately in the boot.sys file. No changes
are made to the system configuration file.
Example:
The following commands
set up two locations to obtain a boot file group from.
boot system priority
1 image tftp: //remoteABC/pub/2012jan.bin
config /flash/pub/data/2012feb.cfg
boot system priority
2 image /flash /pub/data/2002jun.bin
config /pcmcia1/pub/data/2012feb.cfg
The following removes
the current priority
1 boot
entry from the boot.sys file.
no boot system priority 1
bulkstats
Enables the collection
of bulk statistics by the system and/or enters the bulk statistic
configuration mode.
Privilege:
Security Administrator,
Administrator
Syntax
bulkstats { collection | historical | mode }
no bulkstats collection
collection
Enables the statistics
collection process. Collects a period snapshot of data, such as “here
is what the value is right now”.
historical collection
Enables the system
to collect historical bulk statistics.
If enabled, the system
keeps track of some things which require the storing of more data, such
as “the highest value that’s been seen over the
last 24 hours”.
mode
Enters the bulk statistics
configuration mode. The resulting command-line prompt will look similar
to:
[<context-name>]asr5000(config-bulkstats)#
no
Disables the collection
of bulk statistics.
Usage:
The Bulk Statistics
Configuration Code consists of commands for configuring bulk statistic
properties, such as the period of collection. Bulk Statistics
configuration mode commands are defined in the Bulk Statistics Configuration
Mode Commands chapter.
The system can be
configured to collect bulk statistics and send them to a collection
server (called a receiver). Bulk statistics are statistics that
are collected in a group or schema, for example, system statistics,
port statistics, radius statistics.
Once bulk statistics
receiver, schema, and collection properties are configured, this bulkstats command
is used to enable or disable the collection of the data.
To collect a sample
that will provide an average, for example, an average of CPU counters, the “historical” features
must be enabled with the bulkstats historical collection command.
Since bulk statistics
are collected at regular, user-defined intervals, the bulkstats force command
in the Exec Mode can be used to manually initiate the collection
of statistics at any time.
Example:
bulkstats collection
bulkstats mode
no bulkstats collection
ca-certificate
Configures and selects
an X.509 CA root certificate to enable a security gateway or SCM
to perform certificate-based peer (client) authentication. The system
supports a maximum of 16 certificates and 16 CA root certificates.
A maximum of four CA root certificates can be bound to a crypto
or ssl template.
Product:
FNG, SCM (P-CSCF,
A-BG)
Privilege:
Administrator, Security
Administrator, Operator
Syntax
ca-certificate name name pem { data pemdata | url url }
no ca-certificate
name name
name name
Names the CA certificate. name must
be an alphanumeric string of 1 through 128 characters.
pem
Specifies that the
Privacy-enhanced Electronic Mail (PEM) format is to be used.
data pemdata
CA certificate data
in PEM format. pemdata must
be an alphanumeric string of 1 through 4095 characters.
url url
URL of the file containing
CA certificate in PEM.
url must
be an existing URL expressed in one of the following formats:
- [file:]{/flash | /pcmcia1 | /hd-raid}[/directory]/<filename
- tftp://<host>[:<port>][/<directory>]/<filename
- ftp://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
- sftp://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
- http://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
When read via a file,
note that show
configuration will not contain the URL reference, but
will instead output the data via data pemdata,
such that the configuration file is self-contained.
no
Removes the named
CA certificate.
Usage:
In addition to the
X.509 certificate-based gateway authentication method and the PSK (Pre-Shared
Key) and EAP-AKA (Extensible Authentication Protocol - Authentication
and Key Agreement) peer (client) authentication methods, the FNG
and SCM support X.509 certificate-based peer authentication.
The FNG checks the
network policy on whether a FAP is authorized to provide service.
If the network policy states that all FAPs that pass device authentication
are authorized to provide service, no further authorization check
may be required. If the network policy requires that each FAP be
individually authorized for service (in the case where the FEID
is associated with a valid subscription), the FNG sends a RADIUS
Access-Request message to the AAA server. If the AAA server sends
a RADIUS Access-Accept message, the FNG proceeds with device authentication.
Otherwise, the FNG terminates the IPSec tunnel setup by sending
an IKEv2 Notification message indicating authentication failure.
The operator/administrator
is responsible for configuring the certificates through the CLI. The
system will generate an SNMP notification when the certificate is
within 30 days of expiration, and then once a day.
Example:
Use the following
command to remove a certificate named
fap1:
no ca-certificate
data fap1
ca-crl
Configures the name
and URL path of a Certificate Authority-Certificate Revocation List
(CA-CRL).
Product:
S-GW
PDG/TTG
PDIF
FNG
HNB-GW
SCM (P-CSCF, A-BG)
Syntax
ca-crl name name { der | pem } { url url }
no ca-crl name name
no
Removes the named
CA-CRL.
name
Provides a name of
the CA-CRL. name must
be an alphanumeric string of 1 through 128 characters.
der
Specifies that the
Distinguished Encoding Rules (DER) format is to be used for the
source format.
pem
Specifies that the
Privacy-enhanced Electronic Mail (PEM) format is to be used for
the source format.
url url
Specifies the URL
where the CA-CRL is to be fetched.
url must be
an existing URL expressed in one of the following formats:
- [file:]{/flash | /pcmcia1 | /hd-raid}[/directory]/<filename
- tftp://<host>[:<port>][/<directory>]/<filename
- ftp://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
- sftp://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
- http://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
Usage:
Use this command to
name and fetch a CA-CRL from a specified location.
Without additional
information from the CA, an issued certificate remains valid to
any verifier until it expires. To revoke certificates, the CA publishes
a CRL periodically to provide an updated list of certificates revoked,
but not yet expired. Like a certificate, a CRL is a digital document
signed by the CA. In addition to a list of serial numbers of revoked
certificates, the CRL includes attributes such as issuer name (same
as the issuer name in the certificate), signature (signed by the
issuer using the same key that signs certificates), last update
(the time this CRL was issued), and next update (the time next CRL
will be available).
Example:
The following command
fetches a CA-CRL named
list1.pem from
a
host.com/CRLs location
and names the list
CRL5:
ca-crl name CRL5 pem
url http://host.com/CRLs/list1.pem
card
Enters the card configuration
mode for the card specified.
Privilege:
Security Administrator,
Administrator
number
Specifies the number
of the card for which the card configuration mode is to be entered. number must
be an integer from 1 through 48 (on the ASR 5000) or 1 through 20
(on the ASR 5500).
Usage:
Enter the configuration
mode for a specific card when changes a required.
IMPORTANT:
This command is not
supported on all platforms.
card-standby-priority
Configures the redundancy
priorities for packet processing cards by specifying the slot number
search order for a standby card when needed.
Privilege:
Security Administrator,
Administrator
Syntax
card-standby-priority slot_num [ slot_num ] [ slot_num ] ...
slot_num
Specifies the slot
of the card for the order of the standby cards. slot_num must
be in the range from 1 through 16 excluding slots 8 and 9 (on the
ASR 5000) or 1 through 10 excluding slots 5 and 6 (on the ASR 5500). slot_num may
be repeated as many times as necessary to indicate the complete
search order.
Usage:
Set the standby order
of the redundant cards when multiple standby cards are available.
Questionable hardware
should be placed lower in the priority list.
IMPORTANT:
This command replaces
the pac-standby-priority command.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
configures the redundancy priority to use the standby cards in slots 16,
14, and 12 in that order:
card-standby-priority
16 14 12
call-control-profile
Creates an instance
of a call-control profile.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] call-control-profile cc_profile_name
no
Deletes the Call-Control
Profile instance from the configuration.
cc_profile_name
Specifies the name
of the call-control profile. Enter an alphanumeric string of 1 through
64 characters.
Usage:
Use this command to
create an instance of a call-control profile and to enter the call-control
profile configuration mode. A call-control profile is a template
which groups a set of call-handling instructions that may be applicable
to one or more incoming calls. See the Call-Control Profile
Configuration Mode Commands chapter for information regarding
the definition of the rules contained within the profile and the
use of the profile.
IMPORTANT:
A call-control profile
is a key element of the Operator Policy feature and is only valid
when associated with at least one operator policy.
To see what call-control
profiles have already been created, return to the Exec mode and enter
the show call-control-profile
all command.
Example:
The following command
creates a configuration instance of an call-control profile:
call-control-profile ccprof1
cdr-multi-mode
This command enables
multiple instances of CDRMOD, one per packet processing card.
Privilege:
Security Administrator,
Administrator
Syntax
[ default ] cdr-multi-mode
default
Configures this command
with its default setting.
Default: Single-CDRMOD
mode
Usage:
Use this command to enable
the multi-CDRMOD mode, wherein there will be one instance of CDRMOD
per packet processing card. All the SessMgr instances that are running
on a packet processing card will send the records to the CDRMOD
instance running on that card.
By default, CDRMOD runs
in single mode, wherein there will be only one instance of CDRMOD
running for the entire chassis. All the SessMgr instances that are
running on a packet processing card will send the records to the
CDRMOD instance.
IMPORTANT:
For changes to this command
to take effect, save the configuration and reboot the system.
IMPORTANT:
In multi-CDRMOD mode,
you should enable hard-disk usage.
certificate
Configures and selects
an X.509 Trusted Author certificate.
Product:
ACS
FNG
PDG/TTG
PDIF
SCM (P-CSCF, A-BG)
Privilege:
Administrator, Security
Administrator, Operator
Syntax
certificate name name pem { data pemdata | url url } private-key
pem { [ encrypted ] data pemdata | url url }
no certificate name name
name name
Names the certificate. name must
be from 1 to 128 alphanumeric characters.
pem
Specifies that the
Privacy-enhanced Electronic Mail (PEM) format is to be used.
data pemdata
Certificate/private
key data in PEM format. pemdata must
be an alphanumeric string of 1 through 4095 (certificate) or 1 through
8191 (private key) characters.
url url
URL of the file containing
certificate/private key in PEM.
url must
be an existing URL expressed in one of the following formats:
- [file:]{/flash | /pcmcia1 | /hd-raid}[/directory]/<filename
- tftp://<host>[:<port>][/<directory>]/<filename
- ftp://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
- sftp://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
- http://[<username>[:<password>]@]<host>[:<port>][/<directory>]/<filename
When read via a file, show configuration will not contain the
URL reference, but instead outputs the data via data pemdata,
such that the configuration file is self-contained.
private-key
Private key data.
encrypted
Encrypted private
key data.
no
Removes the named
certificate.
Usage:
A certificate authority
or certification authority (CA) is an entity which issues digital certificates
for use by other parties. It is an example of a trusted third party.
CAs are characteristic of many public key infrastructure (PKI) schemes.
If CERT information
is configured, the system will include the CERT payload in the first IKE_AUTH
Response during the first authentication. The system stores its
own certificate for use in the first AUTH calculation. MS will not
have its own certificate from CA. Still, it will be capable of accepting
a certificate from the system and verify AUTH.
The operator/administrator
is responsible for configuring the certificates through the CLI. The
system will generate an SNMP notification when the certificate is
within 30 days of expiration, and then once a day.
Example:
Use the following
command to remove a certificate named
box1:
no certificate data box1
cli
Configures global
Command Line Interface (CLI) parameters.
Privilege:
Security Administrator,
Administrator
Syntax
cli { access { monitor-protocol | monitor-subscriber | show-configuration } { administrator | operator } } | configuration-monitor | login-failure-delay
number | max-sessions number | operator clear-subscriber-one-only | trap config-mode }
no cli { configuration-monitor | hidden | login-failure-delay
number | max-sessions | operator clear-subscriber-one-only | trap
config-mode }
default cli { access { monitor-protocol | monitor-subscriber | show-configuration } | configuration-monitor | login-failure-delay | max-sessions | operator
clear-subscriber-one-only | trap config-mode }
no
Removes the specified
option.
default
Resets the keywords
to their default values.
access { monitor-protocol | monitor-subscriber | show-configuration } { operator | administrator }
Sets access privileges
on the monitor
protocol and monitor subscriber commands:
monitor-protocol:
Selects privileges for the monitor protocol command.
monitor-subscriber:
Selects privileges for the monitor subscriber command.
show-configuration:
Selects privileges for the show-configurationcommand.
However the default access level for this command is the user with
operator privileges.
operator:
Sets the privileges for the selected command to allow use by users
with operator privileges.
administrator:
Restricts use of the selected command to administrators only.
login-failure-delay number
Specifies the time
to wait before a login failure is returned and another login may
be attempted. Default is five seconds.
max-sessions number
Sets the number of
allowed simultaneous CLI sessions on the system. If this value is
set to a number below the current number of open CLI sessions, the
open sessions will continue until closed. number must
be an integer from 2 through 100.
CAUTION:
Use caution when setting
this command. Limiting simultaneous CLI sessions prevents authorized
users from accessing the system if the maximum number allowed has
been reached. The system already limits CLI sessions based on available
resources. Additional limitation could have adverse effects.
operator clear-subscriber-one-only
Restricts Operator
to clearing only one subscriber session at a time.
trap config-mode
Enables sending an
SNMP notification (trap) when a CLI user enters the configuration mode.
Usage:
This command sets
access parameters and enables several operational parameters for
the system’s command line interface.
Example:
The following command
sets the number of allowed simultaneous CLI sessions to
5.
cli max-sessions 5
The following command
sets the command
monitor protocol to
administrator-only
cli access monitor-protocol administrator
clock
Configures system
clock timezone and what local time zone to use.
Privilege:
Security Administrator,
Administrator
Syntax
clock timezone tz [ local ]
no clock timezone
no
Resets the system
timezone to the system default UTC.
tz
Specifies the system
time zone to use as one of:
- america-buenos-aires
(GMT-3:00; Buenos Aires)
- america-caracas (GMT-4:00)
Caracas
- america-guatemala
(GMT-6:00; Guatemala, Guatemala)
- america-la_paz
(GMT-4:00; La Paz)
- america-lima (GMT-5:00;
Lima, Peru)
- america-puerto-rico
(GMT-4:00; Puerto Rico)
- america-sao-paulo
(GMT -3:00; Brazil)
- america-tijuana (GMT-8:00;
Tijuana)
- asia-baghdad (GMT+3:00;
Baghdad, Russia Zone 2, Kuwait, Nairobi, Riyadh, Moscow, Tehran)
- asia-bangkok (GMT+7:00;
Bangkok)
- asia-calcutta (GMT+5:30;
Calcutta, Mumbai, New Delhi)
- asia-dhaka (GMT+6:00;
Dhaka)
- asia-hong-kong (GMT+8:00;
Hong_Kong)
- asia-irkutsk (GMT+9:30;
Irkutsk)
- asia-kabul (GMT+4:30;
Kabul)
- asia-karachi (GMT+5:00;
Karachi)
- asia-katmandu (GMT+5:45;
Kathmandu)
- asia-magadan (GMT+11:00;
Magadan)
- asia-muscat (GMT+4:00;
Abu Dhabi, UAE, Muscat, Tblisi, Volgograd, Kabul)
- asia-rangoon (GMT+6:30;
Rangoon)
- asia-seoul (GMT+9:00)
Seoul
- asia-tehran (GMT+3:30;
Tehran)
- asia-tokyo (GMT+9:00;
Tokyo, Russia Zone 8)
- atlantic-azores (GMT-2:00;
Azores)
- atlantic-cape-verde
(GMT-1:00; Cape Verde Islands)
- australia-perth (GMT+8:00)
Perth
- australia-darwin (GMT+9:30)
Northern Territory - Alice Springs, Darwin, Uluru
- australia-adelaide
(GMT+9:30) Southern Territory - Adelaide
- australia-melbourne
(GMT+10:00) Victoria - Ballarat, Melbourne
- australia-sydney (GMT+10:00)
New South Wales - Newcastle, Sydney, Wollongong
- australia-hobart (GMT+10:00)
Tasmania - Hobart, Launceston
- australia-brisbane
(GMT+10:00) Queensland - Brisbane, Cairns, Toowoomba, Townsville
- australia-lordhowe
(GMT+10:30) Lord Howe Island
- canada-newfoundland
(GMT-3:30; Newfoundland)
- canada-saskatchewan
(GMT-6:00; Saskatchewan)
- europe-central (GMT+1:00;
Paris, Berlin, Amsterdam, Brussels, Vienna, Madrid, Rome, Bern,
Stockholm, Oslo)
- europe-dublin (GMT+0:00)
Dublin, Ireland
- europe-eastern (GMT+2:00;
Russia Zone 1, Athens, Helsinki, Istanbul, Jerusalem, Harare)
- newzealand-auckland
(GMT +12:00; Auckland, Willington)
- newzealand-chatham
(GMT +12:45; Chatham)
- nuku (GMT-13:00; Nuku'alofa)
- pacific-fiji (GMT+12:00;
Wellington, Fiji, Marshall Islands)
- pacific-guam (GMT+10:00;
Brisbane, Cairns, Sydney, Guam)
- pacific-kwajalein
(GMT-12:00; Kwajalein)
- pacific-norfolk -
(GMT+11:30) Norfolk Island
- pacific-samoa (GMT-11:00;
Samoa)
- us-alaska (GMT-9:00;
Alaska)
- us-arizona (GMT-7:00;
Arizona)
- us-central (GMT-6:00;
Chicago, Mexico City, Saint Louis)
- us-eastern (GMT-5:00;
Bogota, Lima, New York City)
- us-hawaii (GMT-10:00;
Hawaii)
- us-indiana (GMT-6:00;
Indiana)
- us-mountain (GMT-7:00;
Cheyenne, Denver, Las Vegas)
- us-pacific (GMT-8:00)
San Francisco, LA, Seattle
- utc (GMT; Universal
Time Coordinated: London, Dublin, Edinburgh, Lisbon, Reykjavik,
Casablanca)
local
Indicates the timezone
specified by tz is
to be considered the local time zone for local time display and
conversion.
Usage:
Clock and timezone
management is necessary for proper accounting records. The chassis may
be set to display a different local time than that of the system
clock which allows accounting records to use the system time but
to display the proper local time for users.
Example:
clock timezone utc
clock timezone us-indiana local
no clock timezone
congestion-control
Enables or disables
support for congestion control on the system.
Privilege:
Security Administrator,
Administrator
Syntax
congestion-control
policy
[ default | no ]
congestion-control
default
Sets the congestion
control to its default value.
no
Disables congestion
control functionality. This is the default setting.
Usage:
Congestion control
on the system is used to monitor the system for conditions that
could potentially degrade performance when the system is under heavy
load. Typically, these conditions are temporary (i.e high CPU or
memory utilization) and are quickly resolved. However, continuous
or large numbers of these conditions within a specific time interval
may impact the system’s ability to service subscriber sessions.
The purpose of congestion control is to aid in the identification
of such conditions and invoke policies for addressing the situation.
Congestion control
operation is based on the configuration of the following:
- Congestion condition
thresholds: Thresholds dictate the conditions for which congestion
control is to be enabled and establish limits for defining the state
of the system (congested or clear). These thresholds function in
a similar fashion to the operation thresholds that can be configured
for the system (as described in later in this chapter). The primary
difference is that when these thresholds are reached, not only is
an SNMP trap generated (starCongestion), but a service congestion
policy is invoked as well.
A threshold tolerance
is configured to dictate the percentage under the configured threshold
that must be reached in order for the condition to be considered “cleared”.
An SNMP trap (starCongestionClear)
is then triggered.
- Service congestion
policies: Congestion policies are configurable for each service
(PDSN, GGSN, or HA).
These policies dictate how services respond should the system detect
that a congestion condition threshold has been crossed.
Because congestion
control functionality on the system is disabled by default, this command
should be executed once congestion-control thresholds and policies
have been configured. (Refer to the congestion-control
policy and congestion-control
threshold commands for more information.)
congestion-control
overload-disconnect
This command enables
and disables the policy for disconnecting passive calls (chassis-wide)
during an overload situation. It also configures and fine-tunes
the overload-disconnect congestion control policy for an entire
chassis.
Privilege:
Security Administrator,
Administrator
Syntax
congestion-control
overload-disconnect [ iterations-per-stage integer | percent percentage_value | threshold { license-utilization percentage_value | max-sessions-per-service-utilization percentage_value | tolerance number } ]
default congestion-control
overload-disconnect [ iterations-per-stage | percent | threshold { license-utilization | max-sessions-per-service-utilization | tolerance } ]
no congestion-control
overload-disconnect
default
When “default” and
one of the keywords is added to the command, the policy remains
in its current state and the value for the specified keyword is
reset to its default value.
When “default” and
the command are entered without keywords, the overload-disconnect policy
for congestion control is disabled.
no
Disables the overload-disconnect
policy for congestion control.
iterations-per-stage integer
Specifies the number
of calls to be disconnected during the defined number of seconds. integer is
a value from 2 through 8. The default value is 8.
percent percentage_value
Specifies the percentage
of calls to be disconnected, in stages, during an overload situation. percentage_value is
an integer from 1 through 100. The default value is 5.
threshold
license-utilization: Specifies
the license-utilization percentage threshold for overload situations.
If candidates are available, passive calls are disconnected when
this threshold is exceeded. percentage_value is
an integer from 1 through 100. The default value is 80.
max-sessions-per-service-utilization: Specifies
a percentage of the maximum sessions per service. If candidates
are available, passive calls are disconnected when this threshold
is exceeded. percentage_value is
an integer from 1 through 100. The default value is 80.
tolerance:Specifies
the percentage of calls the system disconnects below the values
set for the other two thresholds.
In
either case, a Clear Traps message is sent after the number of calls
goes below the corresponding threshold value. number is
an integer from 1 through 25. The default value is 10.
Usage:
Use this command to
set the policy for call disconnects when the chassis experiences
call overload.
To verify the congestion-control
configuration use show
congestion-control configuration from the Exec mode.
To set overload-disconnect
policies for individual subscribers., see overload-disconnect in
Subscriber Configuration Mode Commands.
Example:
The following command
sets an overload-disconnect policy for the chassis in which 5 calls would
be disconnected very 5 seconds during an overload situation.
congestion-control
overload-disconnect interations-per-stage 5
Both of the following
commands disable the overload-disconnect policy without changing the
policy configuration.
default congestion-control
overload-disconnect
or
no congestion-control
overload-disconnect
To instruct the system
to stop call disconnects when the number of calls goes down 85% of the
total allowed calls for that service, enter both of the following
commands to set the max-sessions-per-service-utilization value to
90% and the tolerance value to 5%:
congestion-control overload-disconnect threshold
max-sessions-per-service-utilization 90
congestion-control overload-disconnect threshold
tolerance 5
congestion-control
policy
Configures congestion
control policies.
Privilege:
Security Administrator,
Administrator
Syntax
congestion-control policy { asngw-service | asnpc-service |
cscf-service | fng-service | ggsn-service | ha-service | hnbgw-service | hsgw-service | lma-service | lns-service | mipv6ha-service | pdg-service| pdif-service | pdsn-service | pdsnclosedrp-service | pgw-service | phsgw-service | phspc-service | sgsn-service | sgw-service } action { drop | none | redirect | reject }
congestion-control policy
mme-service action { drop | none | reject | report-overload { permit-emergency-sessions | reject-new-sessions | reject-non-emergency-sessions } enodeb-percentage percentage }
default congestion-control
policy { asngw-service | asnpc-service | cscf-service | fng-service | ggsn-service | ha-service | hnbgw-service | hsgw-service | lma-service | lns-service | mipv6ha-service | mme-service | pdg-service | pdif-service | pdsn-service | pdsnclosedrp-service | pgw-service | phsgw-service | phspc-service | sgsn-service | sgw-service }
default congestion-control
policy service
Sets the congestion
policy action for the selected service to its default value.
asngw-service
Sets the congestion
policy action for the ASN-GW service.
asnpc-service
Sets the congestion
policy action for the ASN PC-LR service.
cscf-service
Sets
the congestion policy action for the CSCF service.
fng-service
Sets the congestion
policy action for the FNG service.
ggsn-service
Sets the congestion
policy action for the GGSN service.
ha-service
Sets the congestion
policy action for the HA service.
hnbgw-service
Sets the congestion
policy action for the HNB-GW service.
Supported policy actions
are:
- drop: Specifies
that the system is to drop incoming packets containing new session
requests.
- none: Specifies
that the system is take no action.
- reject:
Specifies that the system processes new session request messages
and responds with a reject message.
lma-service
Sets the congestion
control policy action for the LMA service
lns-service
Sets the congestion
policy action for the LNS service.
mipv6ha-service
Sets the congestion
policy action for the MIPv6-HA service.
mme-service
Sets the congestion
control policy for action to take when subscriber sessions exceeds
the defined threshold limit.
For
MME type of session/calls redirect action
is not supported.
pdg-service
Sets the congestion
policy action for the PDG service.
pdif-service
Sets the congestion
policy action for the PDIF service.
pdsn-service
Sets the congestion
policy action for the PDSN service.
sgsn-service
Sets the congestion
policy action for the SGSN service.
action { drop | none | redirect | reject }
Defines what policy
action is taken:
report-overload { permit-emergency-sessions | reject-new-sessions | reject-non-emergency-sessions } enodeb-percentage percentage
IMPORTANT:
This set of keywords
is supported only by the MME.
Enables the MME to report
overload conditions to eNodeBs and take additional action to alleviate
congestion situations.
permit-emergency-sessions:
Specifies that only emergency sessions are allowed to access the
MME during the overload period.
reject-new-sessions:
Specifies that all new sessions destined for the MME will be rejected
during the overload period.
reject-non-emergency-sessions:
Specifies that all non-emergency sessions will be rejected during
the overload period.
enodeb-percentage percentage:
Configures the percentage of known eNodeBs that will receive the overload
report. percentage must
be an integer from 1 to 100.
Usage:
Congestion policies
can be configured for each service. When congestion control functionality
is enabled, these policies dictate how services respond should the
system detect that a congestion condition threshold has been crossed.
Example:
The following command
configures a congestion control policy of reject for PDSN services:
congestion-control
policy pdsn-service action reject
The following command
configures a congestion control policy of reject for MME services:
congestion-control
policy mme-service action reject
congestion-control
threshold
Configures the congestion
control threshold values that are to be monitored.
Privilege:
Security Administrator,
Administrator
Syntax
congestion-control
threshold { license-utilization percent | max-sessions-per-service-utilization percent | message-queue-utilization percent | message-queue-wait-time time | port-rx-utilization percent | port-specific { slot/port | all } [ tx-utilization percent ] [ rx-utilization percent ] | port-tx-utilization percent | service-control-cpu-utilization percent | system-cpu-utilization percent | system-memory-utilization percent | tolerance percent }
default congestion-control
threshold { license-utilization | max-sessions-per-service-utilization | message-queue-utilization | message-queue-wait-time | port-rx-utilization | port-specific | tx-utilization | rx-utilization | port-tx-utilization | service-control-cpu-utilization | system-cpu-utilization | system-memory-utilization | tolerance }
no congestion-control
threshold port-specific { slot/port | all }
no congestion-control
threshold port-specific { slot/port | all } [ rx-utilization percent ] [ tx-utilization percent ]
no congestion-control
threshold { message-queue-utilization | message-queue-wait-time | port-rx-utilization percent | port-tx-utilization
percent | service-control-cpu-utilization | system-cpu-utilization | system-memory-utilization }
default congestion-control
threshold keyword
Sets the threshold
keyword to its default value.
no congestion-control
threshold port-specific { slot/port | all }
This command disables
port specific threshold monitoring on the specified port or on all ports.
slot/port:
Specifies the port for which port specific threshold monitoring
is being configured. The slot and port must refer to an installed
card and port.
all: Set
port specific threshold monitoring for all ports on all cards.
license-utilization percent
Default: 100
The percent utilization
of licensed session capacity as measured in 10 second intervals.
percent can
be configured to any integer value from 0 to 100.
max-sessions-per-service-utilization percent
Default: 80
The percent utilization
of the maximum sessions allowed per service as measured in real-time.
This threshold is based on the maximum number of sessions or PDP
contexts configured for the a particular service. (Refer to the
bind command
for the PDSN
, GGSN,
SGSN, or HA services.)
percent can
be an integer from 0 through 100.
message-queue-utilization percent
Default: 80
The percent utilization
of the Demux Manager software task’s message queue as measured in
10 second intervals. The queue is capable of storing a maximum of
10000 messages.
percent can
be an integer from 0 through 100.
message-queue-wait-time time
Default: 5
The maximum time (in
seconds) messages can be held in queue as measured by packet time stamps.
time is measured
in seconds and can be an integer from 1 through 30.
IMPORTANT:
In the event that this
threshold is crossed, an SNMP trap is not triggered. The service
congestion policy invocation resulting from the crossing of this
threshold is enforced only for the packet that triggered the action.
[ no ] port-rx-utilization percent
Default: 80
The average percent
utilization of port resources for all ports by received data as
measured in 5 minute intervals.
percent can
be an integer from 0 through 100.
[ no ] port-specific { slot/port | all } [ rx-utilization percent ] [ tx-utilization percent]
Default: Disabled
Sets port-specific
thresholds. If you set port-specific thresholds, when any individual
port-specific threshold is reached, congestion control is applied
system-wide.
slot/port:
Specifies the port for which port-specific threshold monitoring
is being configured. The slot and port must refer to an installed
card and port.
all: Set
port specific threshold monitoring for all ports on all cards.
rx-utilization percent: Default
80%. The average percent utilization of port resources
for the specified port by received data as measured in 5 minute
intervals. percent must
an integer from 0 through 100.
tx-utilization percent: Default
80%. The average percent utilization of port resources
for the specified port by transmitted data as measured in 5-minute
intervals. percent must
be an integer from 0 through 100.
[ no ] port-tx-utilization percent
Default: 80
The average percent
utilization of port resources for all ports by transmitted data
as measured in 5-minute intervals.
percent can
be an integer from 0 through 100.
service-control-cpu-utilization percent
Default: 80
The average percent
utilization of CPUs on which a Demux Manager software task instance is
running as measured in 10-second intervals.
percent can
be an integer from 0 through 100.
system-cpu-utilization percent
Default: 80
The average percent
utilization for all PSC/PSC2
CPUs available to the system as measured in 10-second intervals.
percent can
be an integer from 0 through 100.
This threshold setting
can be disabled with no
congestion-control threshold system-cpu-utilization command.
In case later you want to enable the same threshold setting congestion-control
threshold system-cpu-utilization command will enable the
CPU utilization threshold to preconfigured level.
system-memory-utilization percent
Default: 80
The average percent
utilization of all CPU memory available to the system as measured
in 10-second intervals.
percent can
be an integer from 0 through 100.
tolerance percent
Default: 10
The percentage under
a configured threshold that dictates the point at which the condition
is cleared.
percent can
be an integer from 0 through 100.
Usage:
Thresholds dictate
the conditions for which congestion control is to be enabled and establish
limits for defining the state of the system (congested or clear).
These thresholds function in a similar fashion to the operation
thresholds that can be configured for the system (as described in
later in this chapter). The primary difference is that when these
thresholds are reached, not only is an SNMP trap generated (starCongestion),
but a service congestion policy is invoked as well.
The tolerance parameter
establishes the threshold at which the condition is cleared. An SNMP
trap (starCongestionClear) is generated for the clear condition,
as well.
IMPORTANT:
The MME (version 14.0
and higher) supports three levels of thresholds – critical,
major and minor – for each condition. Refer to the congestion-control threshold commands
immediately following this command for information specific to the
MME.
Example:
The following command
configures a system CPU utilization threshold of 75%.
congestion-control threshold
system-cpu-utilization 75
This setting will
remain in configuration unless you specify another threshold value
in place of 75. This threshold setting can be disabled with no congestion-control threshold
system-cpu-utilization command but cannot be removed from configuration.
Later if you want to enable the previously configured threshold
value of 75 percent,
you only need to enter the congestion-control
threshold system-cpu-utilization command without specifying
any threshold value. It will enable the CPU utilization threshold
to preconfigured level of 75 percent.
For example, no congestion-control
threshold system-cpu-utilization disables the configured
threshold setting and congestion-control
threshold system-cpu-utilization again enables the threshold
setting of 75%.
The following command
configures a threshold tolerance of 5%:
congestion-control threshold
license-utilization tolerance 5
In the above examples,
the starCongestion trap gets triggered if the license utilization
goes above 25% and the starCongestionClear trap gets triggered
if it reaches or goes below 70%.
content-filtering
category database directory
This command configures
the base directory to be used for storing all content-rating databases
that are required for Category-based Content Filtering application.
Privilege:
Security Administrator,
Administrator
Syntax
content-filtering
category database directory path directory_path
default content-filtering
category database directory path
default
Specifies the default
base directory and directory path for Category-based Content Filtering application.
directory_path
Default: /pcmcia1/cf
Specifies the base
directory and its path to store all of the full or incremental content
rating databases for the Category-based Content Filtering application.
directory_path must
be an alphanumeric string of 1 through 255 characters.
Usage:
Use this command to
specify the directory and its path to download all full or incremental category-rating
databases to be used for the Category-based Content Filtering application.
Merging of incremental
database can be done as part of the database upgrade process preformed
with upgrade
content-filtering category database command in the Executive
Mode.
Example:
The following command
configures the
/flash/cf_temp/DB as
the base directory to download all full and incremental content-rating
databases for content filtering application.
content-filtering
category database directory path /flash/cf_temp/DB
content-filtering
category database max-versions
This command configures
the number of full content-rating databases to maintain/archive
in the base directory for category-based content filtering application.
Privilege:
Security Administrator,
Administrator
Syntax
content-filtering
category database max-versions num_archive
default content-filtering
category database max-versions
default
Sets the default number
of full databases for specified directory path/location.
num_archive
Default: 2
Specifies the maximum
number of database to be archived or maintained in the specific location.
num_archive must
be an integer from 1 through 3.
Usage:
Use this command to
set the number of full content-rating database to be maintained
in the specified directory path with the base file name specified
using the content-filtering
database override file command. The specified directory path
is the location specified using the content-filtering
category database directory path command.
Example:
The following command
configures the system to maintain
3 full content-rating
databases for category-based content filtering application.
content-filtering
category database max-versions 3
content-filtering
category database override
This command specifies
the name of a file to be used by the category-rating database load
process for category-based content filtering application.
Privilege:
Security Administrator,
Administrator
Syntax
content-filtering
category database override file file_name.extension
default content-filtering
category database override file
default
Sets the default content
rating database file name; for example, optcmd.bin.
file file_name.extension
Specifies the header
of the file in the database directory path location to determine
the newest full database.
file_name must
be an alphanumeric string of up to 10 characters with an extension
of 3 characters after a period (.) as extension.
Usage:
Use this command to
configure the category-rating database file name to determine the newest
version of full database. A process called “LOAD_DATABASE” invokes
during the system startup or the database upgrade process by upgrade content-filtering
category database command in Executive Mode. This process
examines the header of each of the files in the database folder
specified by content-filtering category
directory path command in this mode.
Note that by default
system examines the header of those files only which begins with
the string “OPTCMDB” and having extension “.bin”.
Example:
The following command
configures the system to examine the header of files that begins with
CF_sta.DB only
for content filtering application.
content-filtering category
database override file CF_sta.DB
context
Enters the Context
Configuration mode or is used to add or remove a specified context.
Privilege:
Security Administrator,
Administrator
Syntax
context name [ -noconfirm ]
no context name
no
Removes the specified
context from the configuration.
name
Specifies the name
of a context to enter, add, or remove. When creating a new context,
the context name must be unique.
IMPORTANT:
When creating a new
context, the context
name specified must not conflict with the name of any
existing context or domain names.
-noconfirm
Indicates that the
command is to execute without any additional prompt and confirmation from
the user.
Usage:
Configure contexts
or remove obsolete contexts.
IMPORTANT:
A maximum of 64 contexts
may be created.
crash enable
Enables or disables
the copying of crash data to a specified location.
Privilege:
Security Administrator,
Administrator
Syntax
crash enable [ encrypted ] url crash_url [ filename-pattern pattern ] [ restrict mbyte ]
no crash enable
no
Removes the specified
context from the configuration.
IMPORTANT:
System crash information
is generated and stored in the crash list even when the no keyword
is specified. The information maintained in the crash lists is minimal
crash information when the no keyword
has been specified.
encrypted
Indicates that the
URL encrypted for security reasons.
filename-pattern pattern
The
filename-pattern is
a an alphanumeric string containing any or all of the following
variables:
- %hostname% -
The system hostname.
- %ip% -
A SPIO IP address
- %cpu% -
CPU number
- %card% -
Card number
- %time% -
POSIX timestamp in hexadecimal notation
- %filename% -
Alias for crash-%card%-%cpu%-%time-core%
- %% -
A single % sign
If no pattern is specified,
the result is the same as the pattern filename.
Use '/' characters
in the filename pattern part to store crashes in per-system subdirectories.
url crash_url
Specifies the location
to store crash files. crash_url may
refer to a local or a remote file. crash_url must
be entered using the following format:
For the ASR 5000:
- [ file: ]{/flash|/pcmcia1|/hd}[/directory]/
- tftp://{host[:port#]}[/directory]/
- [ ftp: | sftp: ]//[username[:password]@] {host}[:port#][/directory]/
IMPORTANT:
Use of the SMC hard
drive is not supported in this release.
IMPORTANT:
Do not use the following
characters when entering a string for the field names below: “/” (forward
slash), “:” (colon) or “@” (at
sign).
directory is
the directory name.
filename is
the actual file of interest.
username is
the user to be authenticated.
password is
the password to use for authentication.
host is
the IP address or host name of the server.
port# is
the logical port number that the communication protocol is to use.
restrict mbyte
Specifies a maximum
amount of memory (in megabytes) to use for storing crash files as
an integer from 1 through 128. Default: 128
The restrict keyword
is only applicable to local URLs.
Usage:
Enable crashes if
there are systems that are not stable and the crash information
will be useful for trouble shooting. The remote storage of the crash
file reduces the memory utilized on the chassis.
Example:
crash enable ftp://remoteABC/pub/crash.dmp
crash enable /flash/pub/data/crash.dmp
restrict 64
no crash enable
cs-network
This command creates/removes
an HNB-CS network configuration instance for Femto UMTS access over
Iu-CS/Iu-Flex interface between Home NodeB Gateway (HNB-GW) service
and CS networks elements; i.e. MSC/VLR. This command also
configures an existing HNB-CS network instance and enters the HNB-CS
Network Configuration mode on a system.
Syntax
cs-network cs_instance [ -noconfirm ]
no cs-network cs_instance
no
Removes the specified
HNB-CS network instance from the system.
CAUTION:
Removing the HNB-CS
network instance is a disruptive operation and it will affect all
UEs accessing MSC(s) configured in specific CS core network through
the HNB-GW service.
CAUTION:
If any HNB-CS Network
instance is removed from system all parameters configured in that mode
will be deleted and Iu-CS/Iu-Flex interface will be disabled.
cs_instance
Specifies the name of
the Circuit Switched Core Networks instance which needs to be associated
with the HNB Radio Network PLMN via the HNB RN-PLMN Configuration
mode. If cs_instance does
not refer to an existing HNB-PS network instance, the new HNB-CS
network instance is created.
cs_instance must
be an alphanumeric string of 1 through 63 characters.
-noconfirm
Indicates that the command
is to execute without any additional prompt and confirmation from
the user.
Usage:
Use this command to
enter the HNB-CS Network Configuration mode for an existing CS network
instance or for a newly defined HNB-CS network instance. This command
is also used to remove an existing HNB-CS network instance.
This configuration enables/disables
the Iu-CS/Iu-Flex interface on HNB-GW service with CS core
network elements; i.e. MSC/VLR.
A maximum of one HNB-CS
network instance per HNB-GW service instance which is further limited
to a maximum of 256 services (regardless of type) can be configured
per system.
CAUTION:
This is a critical configuration.
The HNBs cannot access MSC(s) in CS core network without this configuration.
Any change to this configuration would lead to disruption in HNB
access to CS core network.
Entering this command
results in the following prompt:
[context_name]hostname(config-cs-network)#
The various parameters
available for configuration of an HNB-CS network instance are defined
in the HNB-CS Network
Configuration Mode Commands chapter.
Example:
The following command
enters the existing HNB-CS Network configuration mode (or creates
it if it does not already exist) for the instance named
hnb-cs1:
cs-network hnb-cs1
The following command
will remove HNB-CS network instance
hnb-cs1 from
the system without any warning to operator:
no cs-network hnb-cs1
css acsmgr-selection-attempts
This is a restricted
command.
In 9.0 and later
releases this command is obsolete.
css delivery-sequence
This is a restricted
command.
In 9.0 and later
releases this command is obsolete.
css service
This is a restricted
command.
In 9.0 and later
releases this command is obsolete.
default
Restores the system
default values for the specified parameters.
Privilege:
Security Administrator,
Administrator
Syntax
default { autoconfirm | banner [ lawful-intercept | motd | pre-login ] | boot [ delay | interface | nameserver | networkconfig ] | card-standby-priority | cli
max-sessions | congestion-control | logging { display | filter
runtime } | operational-mode | pac-standby-priority | qos
npu inter-subscriber traffic { bandwidth | priority [ assigned-to
dscp { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef } ] } | require
session recovery | snmp { engine-id | notif-threshold } | system
hostname | task { facility sessmgr start | resource
cpu-memory-low } | threshold { value } | timestamps | upgrade
limit [ time ] [ usage] }
autoconfirm
Restores the autoconfirm
behavior to its default of disabled.
banner
lawful-intercept -
Restores the system default message of the day for SSH CLI sessions.
motd - Restores
the system default message of the day banner.
pre-login - Restores
the CLI log in banner to the system default.
boot [ delay | interface | nameserver | networkconfig ]
interface | networkconfig -
Restores the default boot interface and network configuration options.
The keywords interface and networkconfig are
used to restore the default option settings for the interface and
network configuration options, respectively.
Defaulting the network
configuration boot option removes the network boot option from the boot.sys
file. It does not remove the network config options from the configuration
file which is managed separately from the boot.sys file.
delay - Removes
the boot delay setting (if any). The default for boot delay is “no
boot delay”.
nameserver -
Removes the nameserver IP address.
card-standby-priority
Resets the standby
priority of the Packet Services Cards.
cli max-sessions
Restores the default
value of this command to no cli max-sessions which
removes the limit on the number of allowed simultaneous CLI sessions
on the system.
congestion-control
Restores the system’s
congestion-control functionality to its default setting of disabled.
logging {display | filter
runtime}
display:
sets the default level of detail to display for trace log information
to the system default.
filter runtime:
resets the filtering of logged information to log in real time.
operational-mode
Sets the operational
mode of the chassis to the system default.
pac-standby-priority
This parameter has
been replaced by the card-standby-priority keyword.
qos npu inter-subscriber
traffic {bandwidth | priority [ assigned-to
dscp { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef } ] }
Restores the following
NPU QoS parameters to their default values:
- gold: 10%
- silver: 20%
- bronze: 30%
- best-effort: 40%
- priority:
All DSCP values are mapped to the best-effort priority queue but
are not configured.
require session recovery
Resets the session
recovery feature to its default setting of disabled.
snmp { engine-id | notif-threshold | system hostname | timestamps }
engine-id:
restores the SNMP engine ID to the system default.
notif-threshold:
restores the SNMP notification threshold to the system default.
task { facility
sessmgr start | resource cpu-memory-low }
facility sessmgr start:
Restores the default session manager start policy.
resource cpu-memory-low:
Resets the system so that when a CPU runs very low on memory (below
12MB) the most over limit task is killed.
system hostname
Sets the system host
name for SNMP use to the system default value.
timestamps
Resets the inclusion
of timestamps in command.
upgrade limit [ time ] [ usage ]
Sets upgrade limit
values to the defaults. If the optional keywords are not specified
all values are reset to their defaults.
time: Resets
the maximum time a session may exist during a software upgrade to
the default of 120.
usage: Resets
the minimum number of sessions before closing the sessions during
a software upgrade to the system default of 100.
Usage:
Restore system defaults
to aid in trouble shooting or just prior to modifying additional configuration
options.
Example:
default banner motd
default boot
default logging display
default system hostname
default upgrade limit time
diameter-proxy
ram-disk
This command configures
the amount of extra RAM disk space in MB to be allocated to Diamproxy
task when local storage (hard disk) is enabled.
Product:
S-GW,
P-GW, HSGW
Privilege:
Security
Administrator, Administrator
Syntax
diameter-proxy ram-disk
mb space_mb
default diameter-proxy
ram-disk mb
default
Configures
the default setting.
Default:
32 MB
mb space_mb
Specifies
the storage space in MB.
space_mb must
be an integer from 10 through 256.
Usage:
Specifies
the additional storage space to be allocated to Diamproxy for file
write, in MB. The specified memory in MB is added to the existing
memory allocated to Diamproxy only if HDD storage is enabled. By
default, 32 MB is additionally allocated.
Example:
The
following command specifies that
100 MB of
additional storage space be allocated to the Diamproxy task:
diameter-proxy ram-disk
mb 100
end
Exits the current
configuration mode and returns to the Exec mode.
Privilege:
Security Administrator,
Administrator
Usage:
Use this command to
return to the Exec mode.
enforce imsi-min
equivalence
Enables the PDSN/HA
to treat IMSI and MIN as the same for identifying the PDSN/HA
session.
Privilege:
Security Administrator,
Administrator
Syntax
[ no | default ] enforce
imsi-min equivalence
default
Returns the command
to its default setting of disabled.
no
Disables the PDSN/HA
from treating IMSI and MIN as the same for identifying the PDSN/HA
session.
Usage:
Generally on an HA,
the IMSI and MIN are treated as different and hence the RRQs with 1x
and DO PDSNs are processed as different sessions. You can use this
feature to treat the IMSI and MIN with the matching lower 10-digit
as the same for identifying a session. The 10-digit MIN and the
15-digit IMSI are treated as equivalent for the purpose of matching
sessions if the lower 10 digits are the same. Any handoff from 1x
to DO or vice-versa is treated as the same session if the NAI and
HoA also match. If the NAI and/or HoA do not match, then
the duplicate IMSI session detect and terminate feature is applicable.
Generally on a PDSN,
the IMSI and MIN are treated as different and hence RP messages from
1x and DO PDSNs are processed as different sessions. You can use
this feature to treat the IMSI and MIN with the matching lower 10-digit
as the same for identifying a session. The 10-digit MIN and the
15-digit IMSI are treated as equivalent for the purpose of matching
PDSN sessions if the lower 10 digits are the same. Any handoff from
1x to DO or vice-versa is treated as the same session.
Example:
To monitor or clear
subscriber session information filtered by on IMSI/MIN
refer to the show
subscribers msid command.
IMPORTANT:
This command must
be executed at startup only and will not take effect when reconfigured
without rebooting.
Example:
The following command
enables the treatment of the IMSI and MIN as the same for identifying
the session:
enforce imsi-min equivalence
Either of the following
commands disables the treatment of the IMSI and MIN as the same for
identifying sessions:
no enforce imsi-min equivalence
default enforce imsi-min equivalence
exit
Exits the current
mode and returns to the parent configuration mode.
Privilege:
Security Administrator,
Administrator
Usage:
Use this command to
return to the parent configuration mode.
fa-spi-list
Replaces a duplicate
Foreign Agent- Security Parameter Index (FA-SPI) remote address
list applied to multiple FA services with a list name.
Privilege:
Security Administrator,
Administrator
Syntax
fa-spi-list fa_spi_list
fa_spi_list
Remote address list
name expressed as an alphanumeric string of 1 through 64 characters.
Usage:
Use this command to
Replace duplicate FA-SPI remote address list applied to multiple
FA or HA services with a list name.
Example:
The following command
configures the list FA SPI list to
fa-list2:
fa-spi-list fa-list2
global-title-translation
address-map
Creates an instance
of a Global Title Translation (GTT) address-map, a database, for
global titles (ISDN-type address) used for SCCP routing. Upon creating
the instance, the system enters global title translation address-map
configuration mode. For the commands to configure the database,
go to the Global Title
Translation Address-Map Configuration Mode Commands chapter.
Privilege:
Security Administrator,
Administrator
Syntax
global-title-translation
address-map instance instance
no global-title-translation
address-map instance instance
no
Removes the specified
GTT address-map database from the SCCP portion of the configuration.
instance
This value uniquely
identifies a specific instance of a GTT address-map.
instance must
be an integer from 1 through 4096.
Usage:
Create a GTT address-map
with a unique identifier and enter the GTT address-map configuration
mode.
Example:
global-title-translation
address-map instance 324
global-title-translation
association
Creates an instance
of a Global Title Translation (GTT) association which defines the
rules for handling global title translation. Upon creating the instance,
the system enters global title translation association configuration
mode. For the commands to configure the rules, go to the Global Title Translation
Association Configuration Mode Commands chapter.
Privilege:
Security Administrator,
Administrator
Syntax
global-title-translation
association instance instance
no global-title-translation
association instance instance
no
Removes the specified
instance of a GTT association from the SCCP portion of the configuration.
instance
This value uniquely
identifies a specific instance of a GTT association.
instance must
be an integer from 1 through 16.
Usage:
Create a GTT association
with a unique identifier and enter the GTT association configuration
mode.
Example:
global-title-translation
association instance 2
gtpp compression-process
This command configures
the maximum number of child compression processes that AAA proxy
can have.
Privilege:
Security Administrator,
Administrator
Syntax
gtpp compression-process max_number
default gtpp compression-process
default
Restores the system
to the default settings for the number of child compression processes allowed.
max_number
Specifies the maximum
number of child processes. The default is 1
max_number: must
be an integer from 1 through 4.
Usage:
This command configures
the maximum number of child compression processes that AAA proxy
can have only if hard disk storage is enabled.
Example:
gtpp compression-process 3
gtpp ram-disk-limit
This command configures
additional storage space to be allocated for writing files.
Privilege:
Security Administrator,
Administrator
Syntax
gtpp ram-disk-limit
mb mega_bytes
default gtpp ram-disk-limit
default
Restores the system
to the default settings of 32 MB of storage.
mb mega_bytes
Specifies the number
of megabytes of storage allocated for files.
mega_bytes: must
be an integer from 10 through 256. The default is 32 MB.
Usage:
The memory specified
with this command would be added to the existing memory allocated
to the AAA proxy only if hard disk storage is enabled.
Example:
gtpp ram-disk-limit
mb 256
gtpp single-source
Configures the system
to reserve a CPU for performing a proxy function for accounting.
Privilege:
Security Administrator,
Administrator
Syntax
gtpp single-source [ centralized-lrsn-creation | private-extensions ]
no gtpp single-source
centralized-lrsn-creation
Defines Log Record
Sequence Number (LRSN) generation at proxy. The AAA proxy will generate
the LRSN for all CDR types generated by either the GGSN or the SGSN.
Default: disabled
private-extensions
This optional keyword
enables the proprietary use of customer-specific GTPP extensions.
If private-extensions is
not configured, all customer specific private extensions related
to GTPP message transfer with CGF and recovery through GSS are disabled.
IMPORTANT:
In order for the customer-specific
extensions to work properly, the gtpp max-pdu-size command
in the Context Configuration Mode should be set to 65400 and the gtpp server command’s max value
should be set to “1”.
no
Disables GTPP single-sourcing.
This is the default setting.
CAUTION:
Entering this command
while PDP contexts are in process could cause the loss of pending CDRs.
The configuration must be saved and the chassis reloaded for this
option to take effect.
Usage:
When GTPP single-sourcing
is enabled, the system’s AAA proxy function generates requests
to the accounting server using a single UDP source port number,
instead of having each AAA Manager generate independent requests
with unique UDP source port numbers. This is accomplished by the
AAA Managers forwarding their GTPP PDUs to the AAA Proxy function that
runs on a reserved packet processing card CPU. Since a packet processing
card CPU is being reserved, fewer Session Managers and AAA Managers
will be started on that card.
CAUTION:
This command must
be entered prior to the configuration of other services. Specifying
it later may return an error due to a lack of CPU availability.
Example:
The following command
enables GTPP single-sourcing with the use of private GTPP extensions:
gtpp single-source
private-extensions
The following command
disables GTPP single-sourcing:
no gtpp single-source
ha-spi-list
Replaces a duplicate
Home Agent-Security Parameters Index (HA-SPI) remote address list
applied to multiple HA services with a list name.
Privilege:
Security Administrator,
Administrator
Syntax
ha-spi-list ha_spi_list
ha_spi_list
Remote address list
name expressed as an alphanumeric string of 1 through 64 characters.
Usage:
Use this command to
Replace duplicate HA-SPI remote address list applied to multiple HA
services with a list name.
Example:
The following command
configures the list HA SPI list to
ha-list2:
ha-spi-list ha-list2
hd raid
Provides access to
a local RAID hard drive configuration mode in order to manage parameters
supporting local storage of records.
Privilege:
Security Administrator,
Administrator
raid
Provides access to
the HD RAID configuration mode in order to manage the RAID on the ASR 5000
SMC hard drive or ASR 5500.
Usage:
Enters the HD RAID
configuration mode.
Entering this command
results in the following prompt:
[context_name]hostname(config-hd-raid)#
HD RAID Configuration
Mode commands are defined in the HD RAID Configuration Mode Commands
chapter.
Example:
The following command
opens the hd-raid mode:
hd raid
hd storage-policy
Provides access to
the local hard drive configuration mode in order to manage parameters
supporting local storage of records.
Product:
GGSN, SGSN, HSGW, P-GW, S-GW
Syntax
[ no ] hd
storage-policy name
no
Removes a configured
HD storage policy from the system.
storage-policy name
Specifies a name for
an HD storage policy and then enters the HD Storage Policy Configuration
Mode. name must
be an alphanumeric string of 1 through 63 characters.
Usage:
Creates a new policy
or specifies an existing policy and enters the HD Storage Policy Configuration
Mode.
Entering this command
results in the following prompt:
[context_name]hostname(config-hd-storage-policy)#
HD Storage Policy
Configuration Mode commands are defined in the HD Storage Policy Configuration
Mode Commands chapter.
Example:
The following command
creates an HD storage policy named
policy3 and
enters the HD Storage Policy Configuration Mode:
hd storage-policy policy3
high-availability
Configures the speed
for detection of packet processing card task failures.
Privilege:
Security Administrator,
Administrator
Syntax
high-availability fault-detection
speed { aggressive | normal }
default high-availability
fault-detection speed
{ aggressive | normal }
Default:
normal
- aggressive:
Initiates packet processing card failover without performing additional
checks.
- normal:
Initiates packet processing card failover after additional checks
are performed.
Usage:
Use this command to
increase the fault detection speed for faster switchovers after
a packet processing card task failure.
Setting fault detection
speed to aggressive will trigger packet processing card failover
as soon as possible if a potential failure is detected. Aggressive
mode will reduce the duration of subscriber outages caused by a
failed packet processing card if session recovery is enabled.
Aggressive mode also
bypasses most information gathering steps and logs that can be used to
determine the root cause of the failure.
In normal mode, additional
checks are performed before triggering a packet processing card
failover to ensure that the card has actually failed. In aggressive
mode these checks are bypassed so that session recovery can start
as soon as possible. These additional checks reduce the likelihood
of a false positive failure.
Example:
The following command
sets the fault detection speed for packet processing card tasks
to
aggressive:
high-availability
fault-detection speed aggressive
hybrid-mode
Enables an ASR 5000
chassis to run a mix of Packet Services Cards (PSCs) and PSC Type
A (PSCAs). When enabled, PSCAs will boot and be compatible with
the PSCs as long as encryption services are disabled. The default
is to run the chassis in non-hybrid mode; PSCAs will not boot when
inserted in the chassis.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] hybrid-mode [force]
no
Returns the chassis
to non-hybrid mode. PSCAs will not boot.
force
Always updates the
configuration, even if the encryption services could not be disabled. However,
the PSC and PSCA cards will continue to be incompatible until encryption
services are manually disabled.
Usage:
To allow a chassis
to run in PSC/PSCA hybrid-mode with encryption services
disabled you must configure hybrid-mode
force once.
To go from hybrid mode
to non-hybrid mode, you must enter the no hybrid-mode force command.
Non-hybrid chassis mode allows encryption services to be started
through the appropriate CLI commands. However, all PSCAs in the
chassis will be disabled.
For additional information,
see the ASR 5000
Installation Guide.
Example:
The following command
enables the chassis to run a mix of PSCs and PSCAs without encryption
services:
hydrid-mode force
imei-profile
Creates an instance
of an International Mobile Equipment Identity (IMEI) profile.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] imei-profile imei_profile_name
no
Deletes the IMEI profile
instance from the configuration.
imei_profile_name
Specifies the name
of the IMEI profile as an alphanumeric string of 1 through 64 characters.
Usage:
Use this command to
create an instance of an IMEI profile and to enter the IMEI Profile Configuration
mode. An IMEI profile is a template which groups a set of device
instructions, such as blacklisting, that may be applicable to one
or more calling devices. See the IMEI Profile Configuration
Mode Commands chapter for information regarding the definition
of the rules contained within the profile and the use of the profile.
IMPORTANT:
An IMEI profile is
a key element of the Operator Policy feature and is only valid when associated
with at least one operator policy.
To see what IMEI profiles
have already been created, return to the Exec mode and enter the show imei-profile all command.
Example:
The following command
creates a configuration instance of an IMEI profile:
imei-profile imeiprof1
license
Configures the session
license key.
Privilege:
Security Administrator,
Administrator
Syntax
license key key_value [ -force ] session-limit
no license key key_value [ -force ] session-limit
no
Removes the license
key(s) installed.
key key_value
Installs the license
key specified by key_value. key_value is
provided by Cisco operations staff.
session-limit
Use this keyword to
suppress fail-over calls from being rejected if the licensed threshold
is crossed.
IMPORTANT:
This is a customer-specific
command that is available for HA, PDSN, EHA, and PDIF. Please contact
your local Cisco sales representative for more information.
-force
Sets the license key
even if resources are not available. The system supports the dynamic resizing
of demultiplexor software tasks based on the licensed session capacity
and feature type. When installing a license, the system automatically
attempts to resize currently functioning tasks. Warning messages
are displayed if there is an issue. Though its use is not recommended,
the -force keyword
can be used to suppress these warning messages.
CAUTION:
Use of this option
is not recommended.
Usage:
Install or update
system session keys when necessary due to expiration and/or
capacity needs.
Example:
license key sampleKeyValue
no license key
line
Enters the terminal
display line configuration mode.
Privilege:
Security Administrator,
Administrator
Usage:
Change the terminal
display configuration based upon the users own terminal characteristics.
link-aggregation
Configures the Link
Aggregation system priority. This parameter is usually changed to
match the feature requirements of the remote switch.
Product:
WiMAX, PDSN, HA, FA,
GGSN, SGSN
Privilege:
Security Administrator,
Administrator
Syntax
link-aggregation { system-mac [ MAC | auto ] | system-priority priority } [-noconfirm ]
{ default | no } link-aggregation { system-mac | system-priority
} [-noconfirm ]
default
Resets the configuration
to the default.
link-aggregation system-mac { MAC | auto } priority
Sets the system MAC
address used along with the system priority to form the system ID.
MAC is a manually
entered MAC address (six groups of two hexadecimal digits separated by
hyphens).
Auto is the default
and is the LAG master port’s MAC address.
link-aggregation system-priority priority
This command sets
the system priority used by LACP to form the system ID.
priority is
a hexadecimal value from 0x0000 through 0xFFFF.
Default system priority
value is 0x8000 (32768).
-noconfirm
Instructs the system
to execute the command without additional prompting for command confirmation.
Usage:
The system MAC address
(6 bytes) and system priority (2 bytes) combine to form the system
ID. A system consists of a packet processing card and its associated
QGLC(s) or XGLCs, or MIO traffic ports. The highest system ID priority
(the lowest number) handles dynamic changes.
For additional usage
and configuration information for the link aggregation feature,
go to Configuring Link Aggregation in the System Administration
Guide.
IMPORTANT:
Not supported on all
platforms
Example:
The following command
configures the link aggregation system-priority to 10640 (
0x2990):
link-aggregation system-priority 0x2990
local-policy-service
This command enables
creating, configuring, or deleting a local QoS policy.
Privilege:
Security Administrator,
Administrator
Syntax
local-policy-service name [ -noconfirm ]
no local-policy-service name
no
Deletes the specified
local QoS policy service from the system.
name
Specifies name of
the local QoS policy service as an alphanumeric string of 1 through
63 characters.
IMPORTANT:
The name must
be unique across all contexts.
If the named local
QoS policy service does not exist, it is created, and the CLI mode
changes to the Local Policy Service Configuration Mode wherein the
local QoS policy service can be configured.
If the named local
QoS policy service already exists, the CLI mode changes to the Local Policy
Service Configuration Mode for that local QoS policy service.
-noconfirm
Specifies that the
command must execute without prompting for confirmation.
Usage:
Use this command to
specify a local QoS policy service name to allow configuration of
a local QoS policy service.
IMPORTANT:
This feature is license
dependent. Please contact your local sales representative for more information.
A local QoS policy
service can be used to control different aspects of a session, such
as QoS, data usage, subscription profiles, or server usage, by means
of locally defined policies.
Local QoS policies
are triggered when certain events occur and the associated conditions are
satisfied. For example, when a new call is initiated, the QoS to
be applied for the call could be decided based on the IMSI, MSISDN,
and APN.
IMPORTANT:
A maximum of 16 local
QoS policy services are supported.
Entering this command
results in the following prompt:
[context_name]hostname(config-local-policy-service)#
Local Policy Service
Configuration Mode commands are defined in the Local Policy Service
Configuration Mode Commands chapter.
Example:
The following command
creates a local QoS policy service named
lctest and
enters the Local Policy Service Configuration Mode:
local-policy-service lctest
local-user allow-aaa-authentication
Enables or disables
the use of administrative accounts other than local-user administrative
accounts.
Privilege:
Security Administrator,
Administrator
Syntax
[ default | no ] local-user
allow-aaa-authentication
default
Returns this parameter
to its default setting of enabled.
no
Disables administrative
user accounts other than local-user accounts.
Usage:
Local-user administrative
accounts are separate from other administrative user accounts configured
at the context level (Security Administrator, Administrator, Operator,
and Inspector).
Context-level administrative
users rely on the system’s AAA subsystems for validating user
names and passwords during login. This is true for both administrative
user accounts configured locally through a configuration file or
on an external RADIUS server.
Since the T1.276-2003
password security mechanisms are supported only for local-user administrative
accounts and not for the AAA-based administrative accounts, this
command provides a mechanism for disabling AAA-based administrative
accounts.
By default, AAA-based
administrative accounts are allowed.
Example:
The following command
forces the system to authenticate local-user accounts based only
on the information in the security account file on its CompactFlash:
no local-user allow-aaa-authentication
local-user lockout-time
Configures the lockout
period for local-user administrative accounts.
Privilege:
Security Administrator,
Administrator
Syntax
local-user lockout-time time
default local-user
lockout-time
default
Restores the parameter
to its default setting.
time
Default: 60
Specifies the amount
of time (in minutes) that must elapse before a previously locked-out local-user
account can attempt to login again. time is
an integer from 1 through 10080.
Usage:
Local-user administrative
accounts can become locked for reasons such as exceeding the configured
maximum number of login failures.
Once an account is
locked, this parameter specifies the lockout duration. Once the
amount of time configured by this parameter has elapsed, the local-user
can once again attempt to login.
Example:
The following command
configures a lockout time of
120 minutes
(2 hours):
local-user lockout-time 120
local-user max-failed-logins
Configures the maximum
number of failed login attempts a local-user can have before their
account is locked out.
Privilege:
Security Administrator,
Administrator
Syntax
local-user max-failed-logins number
[ default | no ] local-user
max-failed-logins
no
Disables this functionality.
default
Restores this parameter
to its default setting.
number
Default: 5
Specifies the maximum
number of times a local-user could experience a login failure before their
account is locked out. number is
an integer from 2 through 100.
Usage:
This command configures
the maximum number of failed login attempts a local-user can have
before their account is locked out. For example if, this parameter
is configured to “3” then after the third failed
login attempt, the account would be locked.
IMPORTANT:
Local-user accounts
can be configured to either enforce or reject a lockout due to the maximum
number of failed login being reached. Refer to the local-user username command
for more information.
Refer to the local-user lockout-time command
for more information.
Example:
The following command
configures a maximum of three login attempts:
local-user max-failed-logins 3
local-user password
Configures local-user
administrative account password properties.
Privilege:
Security Administrator,
Administrator
Syntax
local-user password { [ complexity { ansi-t1.276-2003 |
none } ] [ history length number [ duration days ] ] [ max-age days ] [ min-change-char number ] [ min-change-interval days ] [ min-length number ] }
no local-user password { [ history ] [ max-age ] [ min-change-interval ] }
default local-user
password { [ complexity ] [ history ] [ max-age ] [ min-change-char ] [ min-change-interval ] [ min-length ] }
no
Disables the specified
parameter.
default
Restores the specified
parameter to its default setting.
[ complexity { ansi-t1.276-2003 | none } ]
Default: ansi-t1.276-2003
Specifies the password
strength as one of the following:
- ansi-t1.276-2003: If this option
is selected, the following rules are enforced:
- Passwords may not
contain the username or the reverse of the username
- Passwords may contain
no more than three of the same characters used consecutively
- Passwords must contain
at least three of the following:
uppercase alpha character
lowercase alpha character
numeric character
special character
- none: No additional
password checks are performed.
[ history length number [ duration days ] ]
Default: length is
5
Specifies the number
of previous password entries kept in the history list maintained
by the system. A password cannot be reused if it is one of the entries
kept in the history list unless the time it was last used was more
than the number of days specified by the duration keyword.
If the duration keyword
is not used, the only check performed by the system is that it is
not in the history list.
number is
the number of entries for each account stored in the history list
entered as an integer from 1 through 100. days is
the number of days during which a password can not be reused entered
an integer from 1 through 365.
[ max-age days ]
Default: 90
Specifies the maximum
age for a password. Users logging in with a password older than
the specified limit are locked out. Once the lockout period expires,
at their next login attempt, they are prompted to change their password
before accessing the CLI.
IMPORTANT:
Local-user accounts
can be configured to either enforce or reject a lockout due to a password’s
maximum age being reached. Refer to the local-user username command
for more information.
days is
the number of days that passwords remain valid entered as an integer
from 1 through 365.
[ min-change-char number ]
Default: 2
Specifies the minimum
number of characters that must be changed (in comparison to the current
password) when a user changes their password.
IMPORTANT:
Changes in password
length are counted as “character” changes. For
example: changing a password from “password” to “passwo” is
a 2-character change, changing a password from “password” to “password2” is
a 1-character change, and changing a password from “password” to “apassword” is
a 9-character change.
number is
the number of characters entered as an integer from 0 through 16.
[ min-change-interval days ]
Default: 1
Specifies the frequency
that passwords can be changed (other than first login).
days is
the minimum number of days that must pass before a user can change
their password. It is an integer from 1 through 365.
IMPORTANT:
If the no local-user password
min-change-interval command is used, users may change
their password as often as desired which could allow them to circumvent
the password history function.
[ min-length number ]
Default: 8
Specifies the minimum
length allowed for user-defined password.
number is
the minimum number of alphanumeric characters that the password
must contain, entered as an integer from 3 through 32.
Usage:
This command is used
to set the property requirements for user-defined passwords and system
behavior in relation to those passwords.
Information pertaining
to user passwords, login failures, and password history are stored on
the packet processing cards and in the software’s Shared
Configuration Task (SCT).
The system uses the
information in the SCT for runtime operations such as determining password
ages and determining if new passwords meet the criteria specified
by this command.
Example:
The following command
configures a minimum password length requirement of
6 characters:
local-user password
min-length 6
The following command
configures the system to store the
4 most recently
used passwords per user-account in the history list:
local-user password
history length 4
local-user username
Adds or removes local-user
administrative accounts.
Privilege:
Security Administrator,
Administrator
Syntax
local-user username name [ authorization-level
{ administrator | inspector | operator | security-admin } ] [ ecs | noecs ] [ ftp | noftp ] [ timeout-min-absolute time ] [ timeoute-min-idle time ] [ no-lockout-login-failure ] [ no-lockout-password-aging ] password password
no local-user username name
no
Removes a previously
configured user.
name
Specifies the name
of the user as an alphanumeric string of 3 through 16 characters
that is case sensitive.
[ authorization-level { administrator | inspector | operator | security-admin } ]
Default: Operator
Configures the authorization
level for the user as one of the following:
- administrator:
Administrator users have read-write privileges and can execute any
command throughout the CLI except for a few security functions allowed
only in the administrator mode. Administrators can configure or
modify the system and are able to execute all system commands, including
those available to the operator and inspector user. This level corresponds
to the both the System Administrator and Application Administrator
levels in the T1.276-2003.
- inspector:
Inspector users are limited to a small number of read-only Exec
Modecommands.The bulk of these are “show” commands
giving the inspector the ability to view a variety of statistics
and conditions. The Inspector cannot execute show configuration
commands and do not have the privilege to enter the Config Mode.
- operator:
Operator users have read-only privileges to a larger subset of the
Exec Mode commands as depicted in the following figure. Operator
users can execute all commands that are part of the inspector mode,
plus some system monitoring, statistical, and fault management functions.
Operators do not have the ability to enter the Config Mode.
- security-admin:
Security Administrator users have read-write privileges and can
execute any command throughout the CLI. Security Administrators can
execute all system commands, including those available to the administrator,
operator, and inspector users. This level corresponds to both the
System Security Administrator and Application Security Administrator
levels in T1.276-2003.
[ ecs | noecs ]
Specifies whether
or not the user has access to Active Charging Service configuration parameters.
- ecs: The
user has access.
- noecs: The
user does not have access.
Default: ecs
[ ftp | noftp ]
Default: ftp
Specifies whether
or not the user is allowed to access the system via the File Transfer Protocol
(FTP) and/or the Secure File Transfer Protocol (SFTP).
- ftp: The
user has access.
- noftp: The
user does not have access.
[ timeout-min-absolute time ]
Default: 0
Specifics the maximum
session time (in minutes) for this user. time is
an integer from 0 through 525600. A value of “0” indicates
no limit.
IMPORTANT:
This limit applies
only to the user’s CLI sessions.
[ timeout-min-idle time ]
Default: 0
Specifics the maximum
idle time (in minutes) for this user. time is
an integer from 0 through 525600. A value of “0” indicates
no limit.
IMPORTANT:
This limit applies
only to the user’s CLI sessions.
[ no-lockout-login-failure ]
Default: Disabled
Specifies that this
user will never be locked out due to login attempt failures.
[ no-lockout-password-aging ]
Default: Disabled
Specifies that this
user will never be locked out due to the age of their password.
password password
Specifies the initial
password for this user. password must
an alphanumeric string of 6 through 32 characters that is case sensitive.
IMPORTANT:
The user is requested
to change their password upon their first login.
Usage:
The ability to configure
administrative local-users is provided in support of the login security
mechanisms specified in ANSI T1.276-2003.
Like administrative
users configured at the context level, local-users can be assigned
one of 4 security levels:
Local-User
Level User |
Context
Level User |
Security Administrator
|
Administrator
|
Administrator
|
Config-Administrator
|
Operator
|
Operator
|
Inspector
|
Inspector
|
Local-user configuration
support is handled differently from that provided for administrative
users configured at the context level.
Context-level administrative
users rely on the system’s AAA subsystems for validating user
names and passwords during login. This is true for both administrative
user accounts configured locally through a configuration file or
on an external RADIUS server. Passwords for these user types are
assigned once and are accessible in the configuration file.
Local-user account
information (passwords, password history, lockout states, etc.)
is maintained in non-volatile memory and in the software’s
Shared Configuration Task (SCT). This information is maintained
in a separate file – not in configuration files used by
the system. As such, the configured local-user accounts are not
visible with the rest of the system configuration.
Local-user and context-level
administrative accounts can be used in parallel.
Example:
The following command
configures a security-administrator level local-user administrative account
for a user named
User672 that
has FTP privileges, a temporary password of
abc123, and
that does not lockout due to either login attempt failures or password
aging:
local-user username
User672 authorization-level security-admin ftp no-lockout-login-failure
no-lockout-password-aging password abc123
The following command
deletes a previously configured local-user administrative account called
admin32:
no local-user username admin32
logging console
Enables the output
of logged events to be displayed on the console terminal.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] logging console
no
Disables the output
of events to the console port.
Usage:
Log console output
to allow for offline review during system monitoring and/or
trouble shooting.
logging disable
Enables/disables
the logging of the specified event ID or range of IDs.
Privilege:
Security Administrator,
Administrator
Syntax
logging disable eventid id [ to to_id ]
no logging disable
eventid id [ to to_id ]
no
Indicates the event
IDs specified are to be enabled for logging.
eventid id
Specifies the event
for which no logging is to occur. id must
be a integer from 1 through 100000.
to to_id
Specifies the end
ID of the events when a range of event ID is to be disabled from
being logged. to_id must
be an integer from 1 through 100000. The to_id must
be equal to or larger than the id specified.
Usage:
Disable common events
which may occur with a normal frequency are not of interest in monitoring
the system for troubles.
Example:
The following commands
disables the logging of event ID 4580 and the range of events from 4500
through 4599, respectively.
logging disable eventid
4580 4580
logging disable eventid
4500 to 4599
The following enables
the subset of disabled event IDs:
no logging disable
eventid 4500 to 4549
logging display
Configures the level
of detail for information to be logged.
Privilege:
Security Administrator,
Administrator
Syntax
logging display event-verbosity evt_level ] [ pdu-data format ] [ pdu-verbosity pdu_level ]
event-verbosity evt_level
Specifies the level
of verboseness to use in logging of events as one of:
pdu-data format
Specifies output
format for
packet data units when logged as one of:
- none: outputs in
raw format
- hex; displays out
in hexadecimal format
- hex-ascii; displays
output in hexadecimal and ASCII similar to a main-frame dump
pdu-verbosity pdu_level
Specifies the level
of verboseness to use in logging of packet data units as an integer
from 1 through 5, where 5 is the most detailed.
Usage:
Tune the level of
information to be logged so as to avoid flooding a log file with information
which is not useful or critical.
Example:
The following sets
the logging display for events to the maximum.
logging display event-verbosity
full
The following command
sets the logging display level of detail for packet data units to
level
3 and
sets the output format to the main-frame style
hex-ascii:
logging display pdu-data
hex-ascii pdu-verbosity 3
logging filter
Configures the logging
of events to be performed in real time for the specified facility.
Privilege:
Security Administrator,
Administrator
Syntax
logging filter runtime
facility facility level report_level [ critical-info | no-critical-info ]
facility facility
Specifies the facility
to modify the filtering of logged information. The following list displays
the valid facilities for this command:
level report_level [ critical-info | no-critical-info ]
level report_level:
specifies the level of information to be logged,
report_level,
as one of:
- critical
- debug
- error
- info
- trace
- unusual
- warning
critical-info | no-critical-info:
indicates if critical information is to be displayed or not. The
keyword critical-info specifies
that events with a category attribute of critical information are
to be displayed. Examples of these types of events can be seen at
bootup when system processes and tasks are being initiated. The no-critical-info keyword
specifies that events with a category attribute of critical information are
not to be displayed.
Usage:
This command is useful
when it is necessary to get real time output of events. Event output may
be cached otherwise which may make it difficult to trouble shoot
problems which do not allow the last cache of events to be output
prior to system problems.
CAUTION:
Issuing this command
could negatively impact system performance depending on system loading,
the log level, and/or the type of facility(ies) being logged.
Example:
Set real time output
for the point-to-point protocol facility and all facilities, respectively,
to avoid logging of excessive information.
logging filter runtime
facility ppp
logging filter runtime
facility all level warning
logging monitor
Enables or disables
the monitoring of a specified user.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] logging
monitor {ipaddr ip_address | msid ms_id | username user_name}
no
Disables the monitoring
of the user specified by the options given.
ipaddr ip_address
Specifies the IP address
of the user for which the monitoring filter is to be set. ip_address must
entered using IPv4 dotted-decimal notation.
msid ms_id
msid ms_id:
specifies the mobile subscriber ID for which the monitoring filter
is to be set. ms_id must be
from 7 to 16 digits.
This
keyword/option can be used to specify the Mobile Subscriber
ISDN (MSISDN) for GGSN calls which enables logging based on MSISDN.
username user_name
username user_name:
specifies a user for which the monitoring filter is to be set. user_name must refer
to a previously configured user.
Usage:
Monitor subscribers
which have complaints of service availability or to monitor a test
user for system verification.
CAUTION:
Issuing this command
could negatively impact system performance depending on the number
of subscribers for which monitoring is performed and/or
the amount of data they’re passing.
Example:
The following command
enables the monitoring of user
user1 and
mobile subscriber ID 4441235555, respectively.
logging monitor username user1
logging monitor msid 44441235555
The following disables
the monitoring of user
user1.
no logging monitor
username user1
logging runtime
Enables events to
be filtered and logged in real time.
Privilege:
Security Administrator,
Administrator
Syntax
logging runtime buffer
store { all-events | filtered-events-only }
buffer store { all-events | filtered-events-only }
Determines which logs
are stored in internal logging daemon runtime buffer.
- all-events:
Logging daemon runtime buffer stores all logs that come to it.
- filtered-events-only:
Logging daemon runtime buffer stores only logs that pass the runtime
filter.
Usage:
Sets the filtering
of logged information to log in real time.
Example:
The following command
enables storage of logs that pass the runtime filter:
logging runtime buffer
store filtered-events-only
lte-policy
This command enters
the LTE Policy Configuration Mode where LTE policy parameters can
be configured.
Usage:
Enters the LTE Policy
Configuration Mode.
Entering this command
results in the following prompt:
[
context_name]
hostname(lte-policy)#
LTE Policy Configuration
Mode commands are defined in the LTE Policy Configuration
Mode Commands chapter.
mediation-device
This command is obsolete.
Even though the CLI accepts the command no function is performed.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] mediation-device
mode { tcs }
network-overload-protection
This command configures
an attach rate throttle mechanism to control the number of new connections
(attaches or inter-SGSN RAUs), through the SGSN, on a per second basis.
Privilege:
Security Administrator,
Administrator
Syntax
network-overload-protection
sgsn-new-connections-per-second #_new_connections action { drop | reject
with cause { congestion | network failure } } [ queue-size
queue_size ] [ wait-time
wait_time ]
default network-overload-protection
sgsn-new-connections-per-second
default
Using default in
the command, disables this attach rate throttle feature that provides
network overload protection.
sgsn-new-connections-per-second #_new_connections
Define the number
of new connections to be accepted per second.
#_new_connections: Must
be an integer from 50 to 5000.
action
Specifies the action
to be taken by the SGSN when the attach rate exceeds the configured limit
on the number of attaches. Select one of the following actions:
- drop: Drop the new
connection request.
- reject-with-cause: Reject the new connection
request. Include one of the following as the cause in the reject message:
- congestion
- network failure
queue-size queue_size
Defines
the maximum size of the pacing queue used for buffering the packets.
If configured, the queue-size should be greater than or equal to
the #_new_connections value
and less than or equal to the optimal value (the wait_time * #_new_connections).
This validation is done in the CLI.
queue_size Must
be an integer from 250 to 25000.
Default: unconfigured.
The default value is the #_new_connections * wait-time.
This will be the optimal value.
wait-time wait_time
Defines
the maximum life-time (number of seconds) of the packets in the
queue beyond which the packets are considered to be “stale”.
wait_time Must
be an integer from 1 to 15
Default: 5
Usage:
Use this command to
configure the rate at which the SGSN must process new connection requests.
The rate is the number of new connections to be accepted per second.
With basic network
overload protection, the incoming new connection rate is higher
than this configured rate. When this occurs, all of the new connection
requests cannot be processed. This command can also be used to configure
the action to be taken when the rate limit is exceeded. The new
connection requests, which cannot be processed, can be either dropped
or rejected with a specific reject cause.
The SGSN’s optimized network
overload protection performs attach-rate throttling to avoid overloading
Gr, Gn and Gf interfaces. This is enabled with queue-size and wait-time keywords
so that the IMSIMgr throttles the attach rate to values configured
with these keywords.
If the SGSN receives
more than the configured number of attaches in a second, then the attaches
are buffered in the pacing queue and requests are only dropped when
the buffer overflows due to high incoming attach rate. Messages
in the queue are processed (FIFO) until they age-out when the queued
message's lifetime crosses the configured wait-time. The wait-time
and the attach rate decide the optimal size of the queue.
Counters for this
feature are available in the show gmm-sm statistics command
display in the Network Overload Protection portion of the table.
Example:
Configure the throttle
rate or limit to 2500 attaches per second and to drop all requests
if the limit is exceeded.
network-overload-protection
sgsn-new-connections-per-second 2500 action drop
Disables the network-overload
protection feature and set the default queue size to 1000 and the
wait time to 5 seconds:
default network-overload-protection
sgsn-new-connections-per-second
Set the attach rate
to 500 per second, the action to drop, the wait time to 5 seconds,
and the queue size to be calculated (as follows:
wait_time *
#_new_connections -
i.e., 2500)
network-overload-protection
sgsn-new-connections-per-second 500 action drop wait-time 5
network-service-entity
This command creates
a new instance of an SGSN network service entity (NSE) for either
the IP environment or the Frame Relay environment.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] network-service-entity
( ip-local | peer-nsei peer_nsei_number frame-relay )
no
Deletes the network
service entity definition from the system configuration.
ip-local
Configures the local
endpoint for NS/IP and enters the NSE-IP configuration
mode. The prompt will change to:
[local]<hostname>(nse-ip-local)#
peer-nsei peer_nsei_number frame-relay
Configures a peer
NSE with frame relay connectivity. This set of keywords also provides access
to the NSE-FR Configuration mode. The prompt will change to:
[local]<hostname>(nse-fr-peer-nsei-<peer_nsei_number>)#
Usage:
Use this command to
access the configuration modes for either the IP or Frame Relay network
service entities.
Example:
Enter the NSE for
a Frame Relay configuration instance identified as 4554:
network-service-entity
peer-nsei 4554 frame-relay
network-service-entity
ip
ntp
Enters the Network
Time Protocol (NTP) configuration mode or disables the use of NTP
on the system.
Privilege:
Security Administrator,
Administrator
no
Disables the use of
NTP for clock synchronization. When omitted, NTP client support
is enabled on the chassis. By default NTP synchronization to external
servers is disabled.
IMPORTANT:
If the use of NTP
is disabled the system clock may drift over a period of time. This
may require manual updates to the system clock to synchronize the
clock with other network elements.
Usage:
Used when it is necessary
to enable or configure NTP settings. For additional information refer
to the NTP Configuration
Mode Commands chapter and the System Administration
Guide.
Example:
The following command
enters the NTP configuration mode:
ntp
The following disables
the use of the network timing protocol for system clock synchronization.
no ntp
operator-policy
This command creates
an operator policy and enters the operator policy configuration
mode. Commands for configuration of the policies are available in
the Operator Policy
Configuration Mode Commands chapter.
Privilege:
Security Administrator,
Administrator
Syntax
operator-policy (
default | name policy_name } [ -noconfirm ]
no operator-policy
( default | name policy_name }
-noconfirm
Indicates that the
command is to execute without any additional prompt and confirmation from
the user.
no
Removes the specified
operator policy from the system configuration.
default
default, in
this case, is the name of
a specific operator policy. This default policy is used when no
other defined operator policy matches the incoming IMSI.
IMPORTANT:
You should configure
this default operator policy to be it available to handle IMSIs
that are not matched with other defined policies.
name policy_name
Specifies the unique
name of an operator policy. policy_name is
entered as an alphanumeric string of 1 through 64 characters.
Usage:
Use this command to
create an operator policy and to enter the operator policy configuration
mode to define or modify policies.
An operator policy
associates APNs, APN profiles, IMEI ranges, IMEI profiles, an APN remap
table and a call-control profile to ranges of IMSIs. These profiles
and tables are created and defined within their own configuration
modes to generate sets of rules and instructions that can be reused
and assigned to multiple policies. In this manner, an operator policy
manages the application of rules governing the services, facilities
and privileges available to subscribers. These policies can override
standard behaviors and provide mechanisms for an operator to get around
the limitations of other infrastructure elements such as DNS servers
and HLRs.
The system supports
up to 1,000 operator policies, including the default operator policy.
IMPORTANT:
An operator policy
is the key element
of the Operator Policy feature. After defining an instance of an
operator policy, you must go to the SGSN Global Configuration Mode (from
the Global Configuration mode) to define the IMSI range(s). This
requirement does not hold if you are using a default operator
policy.
To see what operator
policies have already been created, return to the Exec mode and
enter the show
operator-policy all command.
Example:
The following command
accesses the default operator policy and enters the operator policy configuration
mode to view or modify the specified policy:
operator-policy default
orbem
Enters the Object
Request Broker Element Manager (ORBEM) Configuration mode.
Privilege:
Security Administrator,
Administrator
Usage:
Set the configuration
mode to allow modification of the ORBEM configuration data.
pac-standby-priority
This command has been
renamed to card-standby-priority.
Please refer to that command for details. Note that for backwards
compatibility, the system accepts this command as valid.
port atm
Identifies a physical
port on a line card that supports ATM signaling and then enters
the configuration mode for the specific interface-type. For the
commands to configure the port interface, see the CLI chapter ATM
Port Configuration Mode.
Privilege:
Security Administrator,
Administrator
Syntax
port atm slot/port
atm
Indicates the port
identified is an ATM interface port.
slot/port
To determine valid
ATM slot and port numbers, use the Exec mode’s command
show port table
slot: Identifies
the chassis slot holding the line card that supplies ATM ports.
The slot ID number can be an integer from 17 through 48.
port: Identifies
the physical port that is to be configured to support ATM signaling.
The ID number can be an integer from 1 through 4.
Usage:
Change the current
configuration mode to Ethernet Port Configuration mode.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following enters
the ATM port configuration mode for ATM port 1 on the card in slot 19:
port atm 19/1
port bits
Enters the Building
Integrated Timing Supply (BITS) port configuration mode by identifying
the BITS port on the active or standby SPIO.
Privilege:
Security Administrator,
Administrator
Syntax
port bits slot/port
bits
Identifies the BITS
port.
slot/port
slot: Identifies
the chassis slot holding the SPIO. The slot ID can be either 24
(active SPIO) or 25 (standby SPIO).
port: Identifies
the BITS port on the SPIO. The port ID number must be 4.
Usage:
Change the current
configuration mode to BITS port configuration mode.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following enters
the BITS port configuration mode for the active SPIO:
port bits 24/4
port channelized
Identifies a physical
port on a Channelized Line Card (CLC) that supports Frame Relay
signaling and creates a Frame Relay interface. This command enters
the configuration mode for the commands that configure the Frame
Relay interface and the channelized port interface. For additional
information, see the Channelized
Port Configuration Mode Commands chapter.
Privilege:
Security Administrator,
Administrator
Syntax
port channelized slot/port
channelized
Selects the channelized
frame relay interface for the selected line card and port.
slot/port
To determine valid
slots and port numbers, use the Exec mode’s command show port table to
find the channelized line card.
slot: Identifies
the chassis slot holding the Channelized Line Card that sources
Frame Relay ports. The slot ID number can be an integer from 17
through 48.
port: Identifies
the physical port that is to be configured to support Frame Relay
signaling. The ID number can only be 1.
Usage:
Change the current
configuration mode to Channelized Port configuration mode.
Example:
The following enters
the Channelized port configuration mode for port 1 on the card in
slot 20:
port channelized 20/1
port ethernet
Enters the Ethernet
Port Configuration mode for the identified port.
Privilege:
Security Administrator,
Administrator
Syntax
port ethernet slot/port
ethernet
Indicates the port
identified is an Ethernet interface port.
slot/port
Specifies the port
for which Ethernet Port Configuration mode is being entered. The
slot and port must refer to an installed card and port.
Usage:
Change the current
configuration mode to Ethernet Port Configuration mode.
Example:
The following command
enters the Ethernet Port Configuration mode for ethernet port 1
in slot 17:
port ethernet 17/1
port mac-address
virtual-base-address
This command defines
a block of 256 consecutive media access control (MAC) addresses
and enables virtual MAC addressing for Ethernet line card ports.
Not available for the XT2 platform.
Privilege:
Security Administrator,
Administrator
Syntax
port mac-address virtual-base-address MAC_Address
no port mac-address
virtual-base-address
no
Disables virtual MAC
addressing for Ethernet
line
card ports. The block of virtual MAC addresses is not saved.
MAC_Address
Specifies the beginning
address of a block of 256 MAC addresses that are used for virtual MAC
addressing.
Usage:
Use this command to
disregard the MAC addresses assigned and stored in card firmware and
assign MAC addresses for all Ethernet ports from the specified block
of virtual MAC addresses. This command does not affect the MAC addresses
on SPIO cards.
There are 65536 MAC
addresses (00:05:47:FF:00:00 - 00:05:47:FF:FF:FF) reserved for use
by customers. This range allows for the creation of 256 address
blocks each containing 256 MAC addresses (for example, 00:05:47:FF:00:00,
00:05:47:FF:01:00, 00:05:47:FF:02:00, 00:05:47:FF:03:00, 00:05:47:FF:04:00,
etc.).
CAUTION:
This configuration
requires the configuration of a valid block of unique MAC addresses
that are not used anywhere else. Use of non-unique MAC addresses
can degrade and impair the operation of your network.
IMPORTANT:
This command is not
supported on all platforms.
Example:
To enable virtual
MAC addressing for Ethernet ports on all Ethernet line cards in
the system using a block of MAC addresses starting at
00:05:47:FF:00:00, enter
the following command:
port mac-address virtual-base-address 00:05:47:FF:00:00
port rs232
Enters the RS-232
Port Configuration mode for the RS-232 console port on the specified
SPIO card. Not available on the XT2 platform.
Privilege:
Security Administrator,
Administrator
rs232
Indicates the port
identified is an RS-232 port on a SPIO card.
slot 3
Specifies the slot
of the SPIO for which RS-232 Port Configuration mode is being entered. The
slot must refer to an installed SPIO card. The specified port must
always be 3 for an RS-232 port.
The value for slot must
be either 24 or 25.
Usage:
Change the current
configuration mode to RS-232 Port Configuration mode.
Example:
The following command
enters the RS-232 Port Configuration mode for the SPIO in slot 24;
port rs232 24 3
profile-id-qci-mapping
Creates a Qos Class-Identifier-Radio
Access Network (QCI-RAN) ID mapping table or specifies an existing
table and enters the QCI Mapping Configuration mode for the system.
Syntax
[ no ] profile-id-qci-mapping name [ -noconfrm ]
no
Removes the specified
mapping table from the system
name
Creates a new or enters
an existing mapping table configuration. name must
be an alphanumeric string of 1 through 63 alphanumeric.
-noconfirm
Indicates that the
command is to execute without any additional prompt and confirmation from
the user.
Usage:
Enters the QCI-RAN
ID mapping configuration mode for an existing table or for a newly defined
table. This command is also used to remove an existing table.
Entering this command
results in the following prompt:
[context_name]hostname(config-hsgw-association-table)#
QCI Mapping Configuration
Mode commands are defined in the QCI Mapping Configuration
Mode Commands chapter.
Use
this command when configuring the HSGW eHRPD component.
IMPORTANT:
This command creates
a mapping table available to any HSGW context configured on the system.
Example:
The following command
enters the existing QCI mapping configuration mode (or creates it if
it doesn’t already exist) for a mapping table named
qci_table1:
profile-id-qci-mapping qci_table1
The following command
will remove
qci_table1 from
the system:
no profile-id-qci-mapping qci_table1
ps-network
This command creates/removes
an HNB-PS network configuration instance for Femto UMTS access over
Iu-PS/Iu-Flex interface between Home NodeB Gateway (HNB-GW) service
and PS networks elements; i.e. SGSN. This command also configures
an existing HNB-CS network instance and enters the HNB-CS Network
Configuration mode on a system.
Syntax
[ no ] ps-network ps_instance [ -noconfirm ]
no ps-network ps_instance
no
Removes the specified
HNB-PS network instance from the system.
CAUTION:
Removing the HNB-PS
network instance is a disruptive operation and it will affect all
UEs accessing SGSN(s) in specific PS core network through the HNB-GW
service.
DANGER:
If any HNB-PS Network
instance is removed from system all parameters configured in that mode
will be deleted and Iu-PS/Iu-Flex interface will be disabled.
ps_instance
Specifies the name of
the Packet Switched Core Networks instance which needs to be associated
with HNB Radio Network PLMN in HNB RN-PLMN configuration mode. If ps_instance does
not refer to an existing HNB-PS instance, the new HNB-PS network
instance is created.
ps_instance must
be an alphanumeric string of 1 through 63 characters.
-noconfirm
Indicates that the command
is to execute without any additional prompt and confirmation from
the user.
Usage:
Use this command to
enter the HNB-PS Network Configuration mode for an existing PS network
instance or for a newly defined HNB-PS network instance. This command
is also used to remove an existing HNB-PS network instance.
This configuration enables
the Iu-PS/Iu-Flex interface on HNB-GW service with CS core network
elements; i.e. MSC/VLR.
A maximum of 1 HNB-PS
networks instance which is further limited to a maximum of 256 services
(regardless of type) can be configured per system.
CAUTION:
This is a critical configuration.
The HNBs can not access SGSNs in PS core network without this configuration.
Any change to this configuration would lead to disruption in HNB
access to PS core network.
Entering this command
results in the following prompt:
[context_name]hostname(config-ps-network)#
The various parameters
available for configuration of an HNB-PS network instance are defined
in the HNB-PS Network
Configuration Mode Commands chapter.
Example:
The following command
enters the existing HNB-PS Network configuration mode (or creates
it if it doesn’t already exist) for the instance named
hnb-ps1:
ps-network hnb-ps1
The following command
will remove HNB-PS network instance
hnb-ps1 from
the system without any prompt to user:
no ps-network hnb-ps1
qci-qos-mapping
Global QCI-QoS mapping
tables are used to map QoS Class Identifier (QCI) values to appropriate
Quality of Service (QoS) parameters.
Syntax
qci-qos-mapping name [ -noconfirm ]
no
Removes the specified
mapping configuration from the system
name
Creates a new or enters
an existing mapping configuration. name must
be an alphanumeric string of 1 through 63 characters.
-noconfirm
Indicates that the
command is to execute without any additional prompt and confirmation from
the user.
Usage:
Enter the QCI-QoS
mapping configuration mode for an existing table or for a newly defined
table. This command is also used to remove an existing table.
Entering this command
results in the following prompt:
[context_name]hostname(config-qci-qos-mapping)#
QCI - QoS Mapping
Configuration Mode commands are defined in the QCI - QoS Mapping Configuration
Mode Commands chapter.
Use this command when
configuring the following eHRPD component: HSGW, P-GW, S-GW.
IMPORTANT:
This command creates
a mapping configuration available to any HSGW, P-GW, S-GW context configured
on the system.
Example:
The following command
enters the existing QCI - QoS mapping configuration mode (or creates
it if it doesn’t already exist) for a mapping configuration
named
qci-qos3:
qci-qos-mapping qci-qos3
qos npu inter-subscriber
traffic bandwidth
Configures NPU QoS
bandwidth allocations for the system.
Privilege:
Security Administrator,
Administrator
Syntax
qos npu inter-subscriber
traffic bandwidth
gold percent silver percent bronze percent best-effort percent
no qos npu inter-subscriber
traffic bandwidth
no
Removes a previous
bandwidth allocation.
gold percent
Default: 10%
Specifies the maximum
percentage of bandwidth to be allocated to the gold queue priority.
percent can
be configured to an integer from 0 through 100.
silver percent
Default: 20%
Specifies the maximum
percentage of bandwidth to be allocated to the silver queue priority.
percent can
be configured to an integer from 0 through 100.
bronze percent
Default: 30%
Specifies the maximum
percentage of bandwidth to be allocated to the bronze queue priority.
percent can
be configured to an integer from 0 through 100.
best-effort percent
Default: 40%
Specifies the maximum
percentage of bandwidth to be allocated to the best-effort queue priority.
percent can
be configured to an integer from 0 through 100.
Usage:
The bandwidth of a
subscriber queue is maintained by rate limiting functions which implement
packet-rate limiting at the first level and bit-rate limiting at
the next level.
The packet-rate limit
of a queue is defined by the number of packets-per-second (PPS) permitted
for queuing. Before queuing a packet on a subscriber queue, the
NPU ensures that the packet falls within the limit. If the packet
to be queued exceeds the packet rate limit, it is dropped.
Each subscriber queue
is configured with a bit rate limit, measured in megabits-per-second (Mbps),
referred to as CP-BPS (bit-per-second to CP). The CP-BPS is available
as the total bandwidth for the subscriber traffic that a CP can
sustain. Each subscriber queue receives an allocation of a certain
percentage of the CP-BPS. The following maximum CP-BPS values are supported:
- Lead CP (CP0) = 128
Mbps
- Remaining CPs (CP1,
CP2, CP3) = 256 Mbps
For additional information
on the NPU QoS functionality, refer to the System Administration
and Configuration Guide.
IMPORTANT:
This functionality
is not supported for use with the PDSN at this time.
Example:
The following command
configures bandwidth allocations of 20, 30, 40, and 50% for
the gold, silver, bronze, and best-effort queues respectively:
qos npu inter-subscriber
traffic bandwidth gold 20 silver 30 bronze 40 best-effort 50
Upon executing this
command, the priority queues will have the following packet processing card
CP bandwidth allocations based on the maximum CP bandwidth specifications:
Priority |
Lead
CP (CP 0) Bandwidth (Mbps) |
CP
1 through CP 3 Bandwidth (Mbps) |
Gold
|
25.6
|
51.2
|
Silver
|
38.4
|
76.8
|
Bronze
|
51.2
|
102.4
|
Best-effort
|
64
|
128
|
qos npu inter-subscriber
traffic bandwidth-sharing
Configures NPU QoS
bandwidth sharing properties for the system.
Syntax
qos npu inter-subscriber
traffic bandwidth-sharing { { enable | disable } { all | slot slot_num cpu cpu_num } }
enable
Enables bandwidth
sharing for the specified criteria.
disable
Disables bandwidth
sharing for the specified criteria.
all
Specifies that the
bandwidth action is to be applied to all packet processing cards
and every CPU on each packet processing card.
slot slot_num
Specifies that the
bandwidth action is to be applied to a packet processing card in
a specific chassis slot number.
slot_num is
the slot in which a packet processing card is installed. These cards
can be installed in slots 1 through 8 and 10 through 16 on the
ASR 5000, or 1 through 4 and 7 through 10 on the ASR 5500.
cpu cpu_num
Specifies a specific
control processor (CP) on a packet processing card for which to
perform the bandwidth action.
cpu_num is
an integer value from 0 to 3. 0 represents the lead CP.
Usage:
The available bandwidth
of a subscriber queue can be shared equally among the other subscriber
queues. Any unutilized bandwidth of a queue can be shared with the
other queues equally. For example, if only one DSCP is configured
and it is mapped to best-effort, that DSCP would get the bandwidth
allocated to the best-effort in addition to the rest of the bandwidth allocated
to the gold, silver, and bronze.
By default, the system
enables sharing for all packet processing cards and their CPs.
For additional information
on the NPU QoS functionality, refer to the System Administration
Guide.
IMPORTANT:
This functionality
is not supported for use with the PDSN at this time.
Example:
The following command
disables bandwidth sharing for the fourth CP (CP 3) on a packet processing
card installed in chassis slot 3:
qos npu inter-subscriber
traffic bandwidth-sharing disable slot 4 cpu 3
qos npu inter-subscriber
traffic priority
Configures the DSCP-to-Priority
assignments for the system.
Privilege:
Security Administrator,
Administrator
Syntax
qos npu inter-subscriber
traffic priority { best-effort | bronze | gold | silver } assigned-to
dscp { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef | dscp_num } }
no qos npu inter-subscriber
traffic priority [ assigned-to dscp { af11 | af12 | af13 | af21 | af22 | af23 | af31 | af32 | af33 | af41 | af42 | af43 | be | ef } ]
best-effort
Specifies the best-effort
queue priority.
bronze
Specifies the bronze
queue priority.
gold
Specifies the gold
queue priority.
silver
Specifies the silver
queue priority.
afXX
Assigns the Assured
Forwarding XX PHB
(per-hop behavior) DSCP.
Each Assured Forwarding
PHB has a corresponding DSCP value as follows:
- af11 through af13:
DSCP values 5 through 7 respectively
- af21 through af23:
DSCP values 9 through 11 respectively
- af31 through af33:
DSCP values 13 through 15 respectively
- af41 through af43:
DSCP values 17 through 19 respectively
be
Assigns the Best Effort
forwarding PHB which has a corresponding DSCP value of 0.
ef
Assigns the Expedited
Forwarding PHB which has a corresponding DSCP value of 23.
dscp_num
Specifies a specific
DSCP value as an integer from 0 through 31.
Usage:
The differentiated
services (DS) field of a packet contains six bits (0-5) that represent
the differentiated service code point (DSCP) value.
Five of the bits (1-5)
represent the DSCP. Therefore, up to 32 (25) DSCPs can be assigned to
the various priorities. By default, they're all assigned to the
lowest priority (best-effort).
For additional information
on the NPU QoS functionality, refer to the System Administration
Guide.
IMPORTANT:
This functionality
is not supported for use with the PDSN at this time.
Example:
The following command
maps the ef DSCP to the gold priority queue:
qos npu inter-subscriber
traffic priority gold assigned-to dscp ef
ran-peer-map
Creates a Radio Access
Network (RAN) Peer Map and enters the RAN Peer Map Configuration
Mode.
Syntax
[ no ] ran-peer-map name [ -noconfirm ]
no
Removes the RAN Peer
Map from the system.
name
Specifies the name
of the RAN Peer Map. name must
be an alphanumeric string of 1 through 31 characters.
Usage:
Use this command to
create a new RAN Peer Map or edit an existing one. RAN peer maps reconcile
base station MAC addresses received in R6 protocol messages to the
base station’s IP address.
Entering this command
results in the following prompt:
[context_name]hostname(config-ran-peer-map)#
RAN Peer Map Configuration
Mode commands are defined in the ASN RAN Peer Map Configuration
Mode Commands chapter in this guide.
Example:
The following command
creates a RAN peer map named
ran12:
ran-peer-map ran12
require active-charging
This command enables/disables
Active Charging Service (ACS)
with
or without the Category-based Content Filtering application.
Privilege:
Security Administrator,
Administrator
Syntax
require active-charging [ isolated-mode ] [ content-filtering
category [ static-and-dynamic ] ] [ optimized-mode ]
no require active-charging
no
Disables ACS on the
system.
isolated-mode
Enables ACS and separates
ACS-related resources from other sub-system resource sharing.
IMPORTANT:
In 8.1 and later releases,
this keyword is not supported.
optimized-mode
Enables ACS in Optimized
mode, wherein ACS functionality is managed by SessMgrs.
IMPORTANT:
In 8.0 and earlier
releases
and in 9.0 and later
releases, this keyword is not supported.
IMPORTANT:
In Release 8.1, ACS
must be configured in the Optimized mode.
IMPORTANT:
In Release 8.1, if
the active-charging mode is changed from the default (non-optimized) mode
to the Optimized mode, or vice-versa, the system must be rebooted
for the change to take effect.
IMPORTANT:
In Release 8.3, this
keyword is obsolete. With or without this keyword ACS is always enabled
in the Optimized mode.
Use the require active-charging command
to enable ACS in the non-optimized mode. Wherein, ACS Managers will
spawn to support ACS.
Use the require active-charging
optimized-mode command to enable ACS in the Optimized
mode. Wherein, ACS is enabled as part of Session Managers.
content-filtering category [ static-and-dynamic ]
Enables the Category-based
Content Filtering application with ACS support and creates the necessary
Static Rating Database (SRDB) tasks to utilize the internal database
of static/dynamic URLs.
For Dynamic Content
Filtering support, the static-and-dynamic keyword
must be configured to specify that the Dynamic Rater Package (model
and feature files) must be distributed to rating modules on startup,
recovery, etc. If not configured, by default, the static-only mode
is enabled.
Usage:
Use this command to
enable/disable ACS
with
or without Category-based Content Filtering application on
the chassis.
IMPORTANT:
This command triggers
the resource subsystem to switch to ACS-enabled mode and start ACS-related
tasks. This CLI command must be configured before any services are
configured, so that the resource subsystem can appropriately reserve
adequate memory for the ACS-related tasks. After configuring this
command, the configuration must be saved and the system rebooted
in order to allocate the resources for ACS upon system startup.
In 8.0 and 8.1 releases,
this command must be configured before configuring any services. This
is to ensure that the resource subsystem can appropriately reserve
adequate memory for ACS Manager tasks. If this command is configured
after all the Session Manager tasks are already active, the ACS
Manager tasks will not be started even if additional cards are added
to the chassis—instead, the chassis must be rebooted.
Example:
In Release 8.0, the
following command enables resource subsystem to configure ACS in isolated
mode:
require active-charging
isoated-mode
In Release 8.1, the
following command enables ACS in Optimized mode:
require active-charging
optimized-mode
In Release 8.3, the
following command enables ACS in Optimized mode:
require active-charging
require cipher
ssl resource-percentage
Assigns the 8 processing
cores on the PSC2 card and splits the hardware acceleration resources
between SSL protocol and IPSec protocol processing.
Product:
SCM (P-CSCF, A-BG)
Privilege:
Security Administrator,
Administrator
Syntax
require cipher ssl
resource-percentage percentage_value
default require cipher
ssl resource-percentage
percentage_value
The system converts
the specified resource percentage value to the nearest number of processing
cores assigned to SSL processing. The system assigns the remaining
processing cores to IPSec processing. This value can be within the
range of 0 to 100.
For example, if 20% of
the hardware acceleration resources are assigned to SSL processing, the
system translates this value to INT((20*8+50)/100) = 2
processing cores assigned to SSL processing, and (8-2) = 6
processing cores assigned to IPSec processing.
default
Sets the default percentage
value to 0%, assigning all 8 processing cores to IPSec processing.
Usage:
Use this command to
split the 8 processing cores on the PSC2 card between SSL protocol and
IPSec protocol processing.
Example:
The following command
assigns 20% of the hardware acceleration resources on the
PSC2 card (2 processing cores) to SSL processing, and 80% of
the hardware acceleration resources (6 processing cores) to IPSec
processing:
require cipher ssl
resource-percentage 20
require demux card
This command enables
or disables the demux capabilities.
Privilege:
Security Administrator,
Administrator
Syntax
[ default | no ] require
demux card
default
Disables the demux
capabilities on the card.
no
Disables the demux
capabilities on the card.
Usage:
Use this command configure
the system to allow session recovery task placement scheme when
session recovery is off.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
enables demux capabilities:
require demux card
require detailed-rohc-stats
Enables or disables
context-specific Robust Header Compression (RoHC) statistics.
Syntax
[ no ] require
detailed-rohc-stats
no
Disables statistics
for RoHC calls. This is the default condition.
Usage:
Enables context-specific
statistics for RoHC calls.
Example:
Enter the following
command to enable context specific statistics for RoHC calls:
require detailed-rohc-stats
require diameter-proxy
This command enables
or disables Diameter Proxy mode.
Privilege:
Security Administrator,
Administrator
Syntax
require diameter-proxy { master-slave | multiple | single }
no require diameter-proxy
no
Disables Diameter
Proxy mode.
Default: no require
diameter-proxy
master-slave
Sets the Diameter-Proxy
to Master-Slave mode.
In Master-slave mode,
multiple Diameter proxies run on system, one on each packet processing
card where one of them acts as Master and other Diameter proxies
act as Slave.
In such mode the Master
relays the traffic from an incoming connection to a specific Slave Diameter
proxy.
multiple
To configure one Diameter
proxy for each active packet processing card.
single
To configure one Diameter
proxy for the entire chassis.
Usage:
When the Diameter
Proxy mode is enabled, each proxy process is a Diameter host, instead of
requiring every Diameter application user (such as, every ACSMgr
and/or every SessMgr, depending on the application) to
be a host.
In Master-slave mode,
multiple Diameter proxies runs on system, one on each packet processing
card where one of them acts as Master and other Diameter proxies
act as Slave.
In such mode Master
relays the traffic from an incoming connection to a specific Slave Diameter
proxy.
Example:
To configure a Diameter
proxy for each active packet processing card, enter the following command:
require diameter-proxy multiple
To configure a single
Diameter proxy for the entire chassis, enter the following command:
require diameter-proxy single
require ecs credit-control
subscriber-mode
This command configures
the Diameter Credit-Control Application (DCCA) to work in per subscriber-PDN
level Gy mode.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] require
ecs credit-control subscriber-mode
no
Creates DCCA/Gy
sessions per bearer/PDP-context.
Usage:
This command is applicable
to all products using the Gy interface. Use this command to configure
DCCA/Gy to work in per subscriber-PDN level Gy mode, wherein
one Diameter session is created per subscriber PDN rather than per
bearer, and only one DCCA/Gy session is created for multi-bearer
PDNs.
If this command is
not configured, or the no
require ecs credit-control subscriber-mode command is
configured, DCCA/Gy sessions are created per bearer/PDP-context,
and as a result when there are multiple PDP contexts or multiple
bearers in a PDN as many DCCA/Gy sessions are created.
IMPORTANT:
This command will take
effect only when the system is booted/rebooted. When configured after
the system comes up, the command will be accepted but will not be
applied until after the system is rebooted with the saved configuration.
IMPORTANT:
This command is independent
of the require
active-charging command. The ecs keyword
in this command is license dependent.
require session
recovery
Enables session recovery
when hardware or software fault occurs within system.
Product:
PDSN,
GGSN, SGSN, HA, LNS
, ASN-GW,
PDIF,
PDG/TTG,
MME
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] require
session recovery
no
Disables session recovery
feature after configuration file is saved and system is restarted.
Usage:
When this feature
is enabled, the system attempts to recover any home agent-based
Mobile IP sessions that would normally be lost due to a hardware
or software fault within the system.
This functionality
is available for the following call types:
-
ASN-GW services supporting
simple IP, Mobile IP, and Proxy Mobile IP
- PDSN services supporting
simple IP, Mobile IP, and Proxy Mobile IP
- HA services supporting
Mobile IP and/or Proxy Mobile IP session types with or without
per-user Layer 3 tunnels
-
GGSN services for
IPv4 and PPP PDP contexts
-
SGSN services for
all attached and/or activated subscribers
- LNS session types
-
PDIF services supporting
Simple-IP, Mobile-IP and Proxy Mobile-P
-
MME services
The default setting
for this command is disabled.
The no option
of this command disables this feature.
This command only works when
the Session Recovery feature is enabled through a valid Session
and Feature Use License Key.
IMPORTANT:
After entering this
command, you must restart the system for the command takes effect. Remember
to save the configuration file before issuing the reload command.
reveal disabled
commands
Enables the input
of commands for features that do not have license keys installed.
The output of the command show cli indicates
when this is enabled. This command effects all future CLI sessions.
This is disabled by default.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] reveal
disabled commands
no
Do not show disabled
commands.
Usage:
When this is enabled
and a disabled command is entered, a message is displayed that informs
you that the required feature is not enabled and also lists the
name of the feature that you need to support the command.
When this is disabled
and a disabled command is entered, the CLI does not acknowledge the
existence of the command and displays a message that the keyword
is unrecognized.
Example:
Set the CLI to accept
disabled commands and display the required feature for all future
CLI sessions with the following command:
reveal disabled commands
Set the CLI to reject
disabled commands and return an error message for all future CLI sessions:
no reveal disabled commands
rohc-profile
This command allows
you to create an RoHC (Robust Header Compression) profile and enter
the RoHC Profile Configuration Mode. This mode is used to configure
RoHC Compressor and Decompressor parameters. RoHC profiles can then
be assigned to specific subscriber sessions when RoHC header compression
is configured.
Privilege:
Security Administrator,
Administrator
Syntax
rohc-profile profile-name name [ -noconfirm ] [ common-options | compression-options | decompression-options ]
no rohc-profile profile-name name
common-options
Configures common
parameters for compressor and decompressor.
compression-options
Configures ROHC compression
options.
decompression-options
Configures ROHC decompression
options.
no
Remove the specified
RoHC profile.
name
The name of the RoHC
profile to create or remove. name must be
an alphanumeric string of 1 through 63 characters.
-noconfirm
Do not prompt for
additional verification when executing this command.
Usage:
Use this command to
enter the RoHC Profile Configuration mode.
Entering this command
results in the following prompt:
[context_name]host(config-rohcprofile-<profile_name>)#
RoHC Profile Configuration
Mode commands are defined in the RoHC Profile Configuration
Mode Commands chapter.
Example:
Enter the following
command to create an RoHC profile named
HomeUsers and
enter the RoHC Configuration mode without prompting for verification:
rohc-profile profile-name HomeUsers
The following command
removes the RoHC profile named
HomeUsers:
no rohc-profile profile-name HomeUsers
sccp-network
This command creates
or removes a Signaling Connection Control Part (SCCP) network instance
which is used to define the SS7 end-to-end routing in a UMTS network.
As well, this command enters the SCCP network configuration mode.
The SGSN supports up to 12 SCCP network instances at one time.
Privilege:
Security Administrator,
Administrator
Syntax
sccp-network sccp_net_id [ -noconfirm ]
no sccp-network sccp_net_id
no
Remove the SCCP network
configuration with the specified index number from the system configuration.
sccp_net_id
This number identifies
a specific SCCP network configuration.
sccp_net_id: must
be an integer from 1 through 12.
-noconfirm
Indicates that the
command is to execute without any additional prompt and confirmation from
the user.
Usage:
Use this command to
create or modify an SCCP network and enter the SCCP network configuration
mode.
The SCCP network is
not a standard SS7 or UMTS concept - this concept is specific to
this platform.
For
details about the commands and parameters needed to create and edit
the SCCP Network configuration, check the SCCP Network Configuration
Mode chapter.
Example:
The following command
creates an SCCP network with the index number of
1:
sccp-network 1
The
following command creates an SCCP network with the index number
of
2 to
associate with HNB-GW service for HNB access network users without
any prompt.:
sccp-network 2 -noconfirm
sctp-parameter-template
This command
allows you to create an SCTP parameter template and enter the SCTP
Parameter Template Configuration Mode. This mode is used to configure
parameters for SCTP associations.
Syntax
[ no ] sctp-param-template name
no
Removes the specified
SCTP parameter template from the system.
name
Specifies the name
of the SCTP parameter template being created or accessed. name must
be an alphanumeric string of 1 through 63 characters.
Usage:
Use
this command to enter the SCTP Parameter Template Configuration
mode.
Entering
this command results in the following prompt:
[context_name]host(sctp-param-template)#
SCTP
Parameter Template Configuration Mode commands are defined in the SCTP Parameter Template
Configuration Mode Commands chapter.
Example:
The following command
creates a new SCTP parameter template or enters an existing template
named
sctp-tmpl2:
sctp-param-template
sctp-tmpl2
session trace
This command configures
the type of network elements, file transfer protocol, and Trace
collection entity mode to be used for the transportation of trace
files collected for the subscriber session tracing on the UMTS/EPC
network element(s) along with network connection parameters and
timers.
Product:
GGSN, MME, P-GW, S-GW
Syntax
session trace network-element { all | mme | pgw | sgw | ggsn } [ collection-timer sec ] [ tce-mode { none | push transport
sftp path string username name { encrypted
password enc_pw | password password } } ]
no session trace network-element { all | mme | pgw | sgw | ggsn }
no
Removes the entire
session trace configuration from the system or a specific network element
trace configuration.
network-element { all | mme | pgw | sgw | ggsn }
Identifies the type
of service to the session trace application in order to determine
the applicable interfaces.
all: Specifies
that all network elements and their associated interfaces are to
be made available to the session trace application.
ggsn: Specifies
that the GGSN as network element and its associated interfaces is
to be made available to the session trace application.
mme: Specifies
that the MME as network element and its associated interfaces is
to be made available to the session trace application.
pgw: Specifies
that the P-GW as network element and its associated interfaces is
to be made available to the session trace application.
sgw: Specifies
that the S-GW as network element and its associated interfaces is
to be made available to the session trace application.
collection-timer sec
Specifies the amount
of time (in seconds) to wait from initial activation/data
collection before data is reported to the Trace Collection Entity
(TCE). sec must be
an integer from 0 through 255.
tce-mode none
Specifies that session
trace files are to be stored locally and must be pulled by the TCE.
tce-mode push transport
sftp path string username name { encrypted
password enc_pw | password password }
Specifies that session
trace files are to be pushed to the Trace Collection Entity (TCE).
sftp: Specifies
that Secure FTP is used to push session trace files to the TCE.
path string:
Specifies the directory path on the TCE where files will be placed.
username name: Specifies
the username to be used when pushing files to the TCE.
encrypted password enc_pw: Specifies
the encrypted password to be used when pushing files to the TCE.
password password:
Specifies the password to be used when pushing files to the TCE.
Usage:
Use this command to
configure the file transfer methods and modes for subscriber session trace
functionality and to how and where session trace files are sent
after collection.
This
configuration contains collection timer, UMTS/EPC network
element, type of file transfer, and user credentials setting to
send the collected trace files to the TCE.
Example:
The following command
configures the collection time for session traces to
30 seconds,
identifies the network element as all elements (GGSN, MME, S-GW,
and P-GW), and pushes session trace files to a TCE via SFTP into
a directory named
/trace/agw using
a username
admin and
a password of
pw123:
session trace network-element
all collection-timer 30 tce-mode push transport sftp path /trace/agw
username admin password pw123
The following command
configures the collection time for session traces to
30 seconds,
identifies the network element as an MME, and pushes session trace
files to a TCE via SFTP into a directory named
/trace/sgw using
a username
admin and
a password of
pw123:
session trace network-element
mme collection-timer 30 tce-mode push transport sftp path /trace/mme
username admin password pw123
The
following command configures the collection time for session traces
to
30 seconds,
identifies the network element as GGSN, and pushes session trace
files to a TCE via SFTP into a directory named
/trace/ggsn using
a username
admin and
a password of
pw123:
session trace network-element
ggsn collection-timer 30 tce-mode push transport sftp path /trace/ggsn
username admin password pw123
sgsn-global
This command gives
access to the SGSN Global configuration mode to set parameters relevant
to the SGSN and HNB-GW as a whole.
Privilege:
Security Administrator,
Administrator
Usage:
Using this command
moves into SGSN Global Configuration mode. In this mode, you can set
system-wide parameters on SGSN and HNB-GW to perform the following
tasks:
On
SGSN:
- monitoring and managing
TLLIs in the BSSGP layer.
- defining IMSI ranges
used as filters in the operator policy selection process.
Example:
Enter the SGSN Global
configuration mode with the following:
sgsn-global
snmp authentication-failure-trap
Enables or disables
the SNMP traps for authentication failures.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] snmp
authentication-failure-trap
no
Disables SNMP traps
for authentication failures. When omitted, SNMP traps for authentication
failures will be generated.
Usage:
Disables authentication
failure traps if they are not of interest. At this time the option
may be changed to support trouble shooting.
By default SNMP authentication
failure traps are disabled.
snmp community
Configures the SNMP
v1 and v2 community strings.
Privilege:
Security Administrator,
Administrator
Syntax
In StarOS 12.1 and
earlier releases:
snmp community string ] [ read-only | read-write ]
no snmp community string
no
The specified community
string is removed from the configuration.
name string
Specifies a community
string whose options are to be modified. An unencrytpted string
must be an alphanumeric string of 1 through 31 characters. An encrypted
string is an alphanumeric string of 1 through 80 characters.
context context_name
Default: community
string applies to all contexts.
Specifies a the context
to which the community string shall be applied. context_name must
be an alphanumeric string of 1 through 31 characters.
read-only | read-write
Default: read-only
Specifies if access
rights for the community string.
read-only:
the configuration may only be viewed.
read-write:
the configuration may be viewed and edited.
view view_name
Default: community
string applies to all views.
Specifies the view
to which the community string shall be applied. view_name must
be an alphanumeric string of 1 through 31 characters.
Usage:
The community strings
define the privileges of SNMP users. It may be desirable to give read-only
access to front line operators.
Example:
snmp community name plain_text_string
snmp community encrypted
name encrypted_string
snmp community name
plain_text_string context sampleContext
snmp community name
plain_text_string context sampleContext view sampleView
snmp community name
plain_text_string read-write view sampleView
no snmp community plain_text_string
snmp engine-id
Configures the SNMP
engine to use for SNMP requests when SNMPv3 agents are utilized.
Privilege:
Security Administrator,
Administrator
Syntax
snmp engine-id local id
id
Specifies the SNMPv3
engine to employ. id must
be an alphanumeric string of 1 through 31 characters.
Usage:
When SNMPv3 is used
for SNMP access to the chassis the engine ID can be used to quickly
change which schema is used for SNMP access.
IMPORTANT:
The system can send
either SNMPv1, SNMPv2c, or SNMPv3 traps to numerous target devices.
However, the Web Element Manager can only process SNMP version 1
(SNMPv1) and SNMP version 2c (SNMPv2c) traps. If the SNMP target
being configured is Web Element Manager application, then you must
not configure this command to use.
snmp heartbeat
Enables the sending
of periodic “heartbeat” notifications (traps).
Syntax
snmp heartbeat { interval [ minutes ] | second-interval [ seconds ] }
[ deafult | no ] snmp heartbeat
default
Returns the command
to its default setting of disabled.
interval [ minutes ]
Default: 60
Specifies the interval
time (in minutes) between notifications. minutes must
be an integer from 1 through 1440.
second-interval [ seconds ]
Default: 30
Specifies the secondary
interval time, in seconds, between notifications. seconds must
be an integer from 10 through 50.
Usage:
Use this command to
enable the sending of a heartbeat notification periodically to confirm a
system is up and communicating.
Example:
The following command
sets the SNMP heartbeat notification interval to 2 hours, 15 minutes
and 30 seconds:
snmp heartbeat interval
135 second-interval 30
snmp history heartbeat
Enables the recording
of heartbeat notifications in SNMP history.
Syntax
[ default | no ] snmp
history heartbeat
default
Returns the command
to the default setting of enabled.
no
Disables the history
recording feature.
Usage:
Use this command to
enable the recording of SNMP heartbeat notifications in SNMP history
files.
snmp notif-threshold
Configures the number
of SNMP notification that need to be generated for a given event
before it is propagated to the SNMP users.
Privilege:
Security Administrator,
Administrator
Syntax
snmp notif-threshold count [ low low_count ] [ period seconds ]
no snmp notif-threshold
no
Removes all SNMP notification
thresholds. All notifications will be broadcast to SNMP users.
count
Default: 100
Specifies the number
of notifications that must be generated before the next notification
is broadcast to SNMP users. count must
be an integer from 1 through 10000.
low low_count
Default: 20
Specifies the number
of notifications within the monitoring period before which any subsequent
notification for each specific event. low_count must
be an integer from 1 through 10000.
period seconds
Default: 300
Specifies the number
of seconds of the monitoring window size before any subsequent notification
may be broadcast to users. seconds must
be an integer from 10 through 3600.
Usage:
Set the notification
threshold to avoid a flood of events which may be the result of
a single failure or maintenance activity.
Example:
snmp notif-threshold 100
snmp notif-threshold
100 period 30
snmp server
Enables the SNMP server
as well the configuration of the SNMP server port.
Privilege:
Security Administrator,
Administrator
Syntax
snmp server [ port number ]
no snmp server
no
Restores the default
SNMP port assignment.
port number
Default: 161
Specifies the port
number to use for SNMP communications. number must
be an integer from 1 to 65535.
Usage:
Set the SNMP port
for communications when SNMP is enabled.
IMPORTANT:
This will result in
restarting the SNMP agent when the no keyword
is omitted. SNMP queries as well as notifications/traps
will be blocked until the agent has restarted.
Example:
snmp server port 100
no snmp server
snmp target
Configures remote
receivers for SNMP notifications.
Privilege:
Security Administrator,
Administrator
Syntax
snmp target name ip_address [ port number ] [ non-default ] [ security-name string ] [ version { 1 | 2c | 3 | view ] [ security-level { noauth | { auth | priv-auth
privacy [ encrypted ] des privpassword } authentication [ encrypted ] { md5 | sha } authpassword } } [ informs | traps ]
no snmp target name
no
Removes the specified
target as a receiver of unsolicited SNMP messages (traps).
authentication { md5 | sha } authpassword
Reads the authentication
type and password if the security level of the SNMP messages is set
to
auth or
priv-auth. Authentication
types are:
- md5: Configures
the hash-algorithm to implement MD5 per RFC 1321.
- sha: Specifies
that the hash protocol is Secure Hash Algorithm.
security-level { noauth | { auth | priv-auth
privacy [ encrypted ] des privpassword }
Sets the security
level of the SNMPv3 messages, as follows:
- noauth: No
authentication and encryption is used.
- auth: Only
authentication will be used.
- priv-auth:
Both authentication and encryption will be used.
- privacy des privpassword:
Reads the privacy type and password.
name
Specifies a logical
name to use to refer to the remote receiver. name must
be an alphanumeric string of 1 through 31 characters.
ip_address
Specifies the IP address
of the receiver. ip_address must
be specified using IPv4 dotted-decimal notation.
non-default
Specifies that this
destination is only used for SNMP traps which have been specifically identified.
port number
Default: 162
Specifies the port
which is to be used in communicating with the remote receivers. number must
be an integer from 0 through 65535.
security-name string
Default: no community
string included
Specifies the community
string to use in the unsolicited messages. string must
be an alphanumeric string of 1 through 31 characters.
version { 1 | 2c | 3 } | view
Default: 1
Specifies the SNMP
version the target supports and consequently the version of the
SNMP protocol to use for communications.
IMPORTANT:
The system can send
either SNMPv1, SNMPv2c, or SNMPv3 traps to numerous target devices.However,
the Web Element Manager can only process SNMP version 1 (SNMPv1)
and SNMP version 2c (SNMPv2c) traps. If the SNMP target being configured
is Web Element Manager application, then you must configure this
command to use version 1 or version 2c.
informs | traps
Default: traps
Specifies the type
of SNMP event to use to send notifications to SNPM targets. traps are
unacknowledged (fire and forget) whereas informs require
a response from the SNMP target.
If the notification
type is set to informs,
the notification is resent if no response is received within 5 seconds.
The notification is resent at most two times.
Usage:
The target manages
the list of remote receivers to which unsolicited messages are sent.
Use this command to add /remove a monitoring system to/from
a network.
Example:
snmp target sampleReceiver
1.2.3.4 security-name sampleComm
snmp target sampleReceiver
1.2.5.6 port 100
snmp target sampleReceiver
1.2.7.8 version 2c traps
no snmp target sampleReceiver
snmp trap
This command enables
or disables generation of specific or all SNMP traps.
Privilege:
Security Administrator,
Administrator
Syntax
snmp trap { enable | suppress } [ trap_name1
trap_name2 ... trap_nameN | all ]
enable
Enables or allows
the generation of one or more SNMP traps by the system.
suppress
Disables the generation
of one or more SNMP traps by the system.
trap_name1 trap_name2 ... trap_nameN
The name of the specific
SNMP trap to enable or disable. Multiple traps can be listed for
a single instance of this command.
IMPORTANT:
The system disregards
character case (case insensitive) when entering trap names.
all
Default: Enable All
Specifies that all
SNMP traps will be affected by the specified operation (enable or suppress).
Usage:
SNMP traps are used
by the system to indicate that certain events have occurred. A complete
listing of the traps supported by the system and their descriptions
can be found in the SNMP
MIB Reference. Additionally, a trap listing can be viewed using
the following command:
snmp trap { enable | suppress } ?
By default, the system
enables the generation of all traps. However, individual traps can
be disabled allowing only traps of a certain type or alarm level
to be generated. This command can be used to disable un-desired
traps and/or re-enable previously suppressed traps.
Example:
The following command
suppresses the LogMessage trap:
snmp trap suppress logmessage
The following command
suppresses the
CLISessEnd and
CLISessStart:
snmp trap suppress
clisessend clisessstart
snmp trap-timestamps
Adds an additional
system-time varbind to generated traps.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] snmp
trap-timestamps
no
Disables the adding
of timestamps to generated traps.
Usage:
The timestamp added
to the generated trap reflects the current system time. The timestamp is
proprietary. This functionality is disabled by default.
IMPORTANT:
If the Web Element
Manager application is used as your alarm server, the application
relies on the timestamp provided by enabling this command to identify
duplicate traps. As a result, it is recommended that this parameter
be enabled for this case.
Example:
The following command
enables the inclusion of a timestamp with each generated trap:
snmp trap-timestamps
snmp user
Configures an SNMPv3
user for SNMP access.
Privilege:
Security Administrator,
Administrator
Syntax
snmp user user_name [ [ encrypted ] password password | engine id | group grp_name | security-model model auth [ [ encrypted ] password password ] ]
no snmp user user_name
no
Removes the specified
user from the list of valid SNMPv3 users.
user_name
Specifies the user
which is to use SNMPv3 interfaces to the system. user_name must
be an alphanumeric string of 1 through 31 characters.
engine id
The SNMP engine ID. id must
be an alphanumeric string of 1 through 31characters.
group grp_name
Default: undefined
(not a member of any group)
Specifies the user
SNMPv3 group the into which user will be added. grp_name must
be an alphanumeric string of 1 to 1023 characters.
security-model model auth
Default: USM
Specifies the security
model used to authenticate the user.
model must
be configured to the following:
[ encrypted ] password password
Default: undefined
Specifies the password
for authenticating the user when the security model is set to User-based
Security Model (USM).
The encrypted keyword
indicates the password will be received in an encrypted form. password must
be an alphanumeric string of 8 through 31 characters.
The encrypted keyword
is intended only for use by the chassis while saving configuration
scripts. The system displays the encrypted keyword
in the configuration file as a flag that the variable following
the password keyword
is the encrypted version of the plain text password. Only the encrypted
password is saved as part of the configuration file.
Usage:
Add and remove SNMPv3
users as operations staff or automated systems are updated. The security
model will be user dependant based upon the support the users system
provides.
IMPORTANT:
The system can send
either SNMPv1, SNMPv2c, or SNMPv3 traps to numerous target devices.
However, the Web Element Manager can only process SNMP version 1
(SNMPv1) and SNMP version 2c (SNMPv2c) traps. If the SNMP target
being configured is Web Element Manager application, then you must
not configure this command to use.
Example:
snmp user user1
snmp user user1 security-model
2c auth
snmp user user1 group
user1 group sampleGroup security-model usm auth
no snmp user user1
ss7-routing-domain
This command creates
an SS7 routing domain instance and enters the SS7 Routing Domain
Configuration mode.
Privilege:
Security Administrator,
Administrator
Syntax
ss7-routing-domain rd_id variant v_type [ -noconfirm ]
no ss7-routing-domain rd_id
no
Removes the specified
SS7 routing domain from the system configuration.
rd_id
Identifies a specific
SS7 routing domain. Once it has been created, it can be accessed
for further configuration and modification by entering the rd_id without entering
the variant.
rd_id must
be an integer from 1 through 12.
variant v_type
Identifies the national
standard to be used for call setup, routing and control, signaling. Select
one of the following:
- ansi: American
National Standards Institute (U.S.A.)
- bici: Broadband
Intercarrier Interface standard
- china: Chinese
standard
- itu: International
Telecommunication Union (ITU-T) Telecommunication Standardization
Sector
- ntt: Japanese
standard
- ttc: Japanese
standard
-noconfirm
Indicates that the
command is to execute without any additional prompt and confirmation from
the user.
Usage:
Use this command to
create an SS7 routing domain configuration instance or to enter
the SS7 routing domain configuration mode to edit the configuration.
A routing domain groups
configuration items to facilitate the management of the SS7 connection
resources for an SGSN service. An Access Gateway supports up to
12 configured SS7 routing domains at one time.
After entering this command,
the prompt appears as:
[context_name]<hostname>(config-ss7-routing-domain-routing_domain_id)#
For details about
the commands and parameters used to define or edit an SS7 routing domain,
refer SS7 Routing Domain
Configuration Mode chapter.
Example:
The following creates
an SS7 routing domain with an index of
1 and the
variant selection of Broadcast Intercarrier Interface (
bici):
ss7-routing-domain
1 variant bici
The
following command creates an SS7 routing domain instance with an
index of
2 and
the variant selection of Broadcast Intercarrier Interface (
bici) to be
associated with HNB RN-PLMN in an HNB access network:
ss7-routing-domain
1 variant bici
suspend local-user
Suspends a local-user
administrative account.
Syntax
[ no ] suspend
local-user name
no
Removes the suspended
status for the specified local-user account.
name
The name of the local-user
account expressed as an alphanumeric string of 3 through 16 characters
that is case sensitive.
Usage:
This command allows
a security administrator to suspend local-user administrative accounts.
A “suspended” user
cannot login to the system. The user’s account information (passwords,
password history, etc.), however, is preserved.
Example:
The following command
suspends a local-user account called
Inspector1:
suspend local-user Inspector1
The following command
removes the suspension from a local-user account called
Admin300:
no suspend local-user Admin300
system
Configures system
information which is accessible via SNMP.
Privilege:
Security Administrator,
Administrator
Syntax
system { carrier-id
mcc mcc_id mnc mnc_id | contact who | description string | hostname host_name | location text| sysdesc-sysoid-style
[ default | new ] }
default system { contact | location }
default
Removes the configured system contact and system location form
the system.
carrier-id mcc mcc_id mnc mnc_id
IMPORTANT:
This carrier ID is
not used by the GGSN.
Specifies a carrier-id
that is a unique identifier for the carrier that has installed the
system. When the carrier ID values are set, the carrier-id and gmt_offset
attributes are included in access-request and accounting packets
when using the following RADIUS dictionaries:
- 3gpp2
- 3gpp2-835
- starent
- starent-835
- starent-vsa1
- starent-vsa1-835
- custom9
mcc mcc_id:
The mobile country code. This must be specified as a 3-digit string
from 001 through 999.
mnc mnc_id:
The mobile network code. This must be specified as a 2- or 3-digit
string from 01 through 999.
contact who
Default: No contact
specified.
contact who: specifies
the contact information for the chassis. who must
be an alphanumeric string of 0 through 255 characters. The string
must be embedded in double quotes (“) if spaces and special
punctuation is to be used.
description string
Allows a user to describe
the system for identification purposes. The system description can be
comprised of a mix of alphanumeric characters, as follows:
- %version% -
software version.
- %build% -
software build number
- %chassis% -
chassis type (ST16, ASR 5000, or ASR 5500)
- %staros% -
OS type
- %hostname% -
system name
- %release% -
release number
- %kerver% -
kernel version
- %machine% -
machine hardware name
- string - an
alphanumeric string of 1 through 255 characters.
hostname host_name
hostname host_name: configures
the chassis host name where host_name must
be an alphanumeric string of 1 through 63 characters.
IMPORTANT:
Please note that changing
the chassis host name results in the command prompt changing as well
to reflect the new name. This may affect any previously scripted
interfaces from an OSS or maintenance facility.
location text
Default: No location
specified.
location text: specifies
the system location expressed as an alphanumeric string of 0 through
255 characters. The text specified must be embedded in double quotes
(“) if spaces are to be used.
sysdesc-sysoid-style [ default | new ]
Allows the user to select
the SNMP return for the objects sysDescr and sysOId.
- default -
SNMP returns old style system description and old style system OID
string.
- new - SNMP
returns Cisco style system description and Cisco style OID string.
Usage:
Specify system basic
information which is useful back at a network operations center which
uses the SNMP interfaces for management.
Example:
The following commands
configure the contact information, system host name, and location text,
or remove configured location and system respectively.
system contact user1@company.com
system hostname system16
system location “Clark
Street Closet\nBasement Rack 4”
The following commands
remove the configured contact and location from system respectively
default system contact
default system location
tacacs mode
Enters the TACACS+ (Terminal
Access Controller Access Control System+) configuration
mode. Use this mode to configure up to three TACACS+ servers
for use in authenticating administrative users via the TACACS+ protocol.
Privilege:
Security Administrator,
Administrator
Usage:
Enter TACACS Configuration
Mode to configure up to three TACACS+ servers for use in authenticating
administrative users via the TACACS+ protocol. For additional
information, see the TACACS+ Configuration
Mode Commands chapter.
Example:
Use the following
command to enter TACACS mode:
tacacs mode
task facility ipsecmgr
Configures IPSec manager
settings.
Privilege:
Security Administrator,
Administrator
Syntax
task facility ipsecmgr { ikev1 { task-count { increased | normal } } | task-count { increased | normal } }
ikev1 { task-count { increased | normal } }
Default: normal
Adjusts the IPSec
manager task count to support EHA for IKEv1. See task-count below.
task-count { increased | normal }
Default: normal
Adjusts the IPSec
manager task count to support EHA.
increased:
Starts additional IPSec manager tasks operating on the packet processing
cards. In increased mode, they run on all but demux packet processing cards.
Also, all the IPSec managers start at the same time when an active
non-demux card is detected and IPSec is configured.
normal:
Uses the standard algorithm for allocating memory for IPSec manager
tasks. In normal mode, IPSec managers do not run on session packet processing
cards.
CAUTION:
If task-count is
set to normal and
session recovery is enabled, IPSec manager tasks are not allowed
to start on most packet processing cards. Because the resources
are not reserved, IPSec managers in normal mode only run on demux
packet processing cards.
Usage:
Sets IPSec manager
parameters for all IPSec managers in the system.
Example:
Use the following
command to set the IPSec manager task count to
increased mode:
task facility ipsecmgr
task-count increased
task facility sessmgr
Configures system
information which is accessible via SNMP.
Privilege:
Security Administrator,
Administrator
Syntax
task { facility
sessmgr start { aggressive | normal } | resource
cpu-memory-low { kill | warn } }
facility sessmgr start { aggressive | normal }
Default: Normal
Specifies the facility
options for the session manager.
aggressive:
specifies the maximum number of session manager processes are started
immediately.
CAUTION:
The task facility sessmgr
start aggressive command should only be used if the system
will reach capacity (for the existing configuration) during the first
few minutes of service.
CAUTION:
This command must
only be executed last during configuration (or appended to the end
of the configuration file) to ensure the availability of memory
resources to contexts and services.
normal:
indicates the session manager processes are started as needed.
resource cpu-memory-low { kill | warn }
Default: kill
Sets the action for
the Resource Manager to take when the amount of free memory on a
CPU falls below 12MB. An SNMP TRAP and CORBA notification are generated
and the event is logged.
Once the free memory
threshold is crossed, The Resource Manager examines all tasks on that
cpu and finds the most over limit task and kills it. If there are
no over limit tasks nothing happens. Resource Manager takes preference
on killing a non-sessmgr task over a sessmgr task.
kill: The
task most over memory limit (if any) is killed and recovered.
warn: The
event is logged and no tasks are killed.
Usage:
Set the session manager
start policy to aggressive on heavily utilized systems to avoid undue
delays in processing subscriber sessions.
Set the CPU memory
low action to only log CPU low memory events.
Example:
task facility sessmgr
start aggressive
task facility sessmgr
start normal
task resource cpu-memory-low warn
task facility acsmgr
This command configures
ACSMgr task settings.
Privilege:
Security Administrator,
Administrator
Syntax
task facility acsmgr
start [ aggressive | normal ]
no task facility acsmgr start
no
Disables the configured
ACSMgr setting.
aggressive
Specifies to start
the maximum possible ACSMgr tasks.
normal
Configures the resource
subsystem to start/stop ACSMgr tasks on an as-needed basis.
Usage:
This command provides
option for the resource subsystem to start maximum possible ACSMgr
tasks based on the license configured and the available system configuration.
Example:
The following command
starts the maximum possible ACSMgr tasks:
task facility acsmgr
start aggressive
terminal
Configures the console
port on the SPIO.
Privilege:
Security Administrator,
Administrator
Syntax
terminal [ carrierdetect { off | on } | databits { 7 | 8 } | flowcontrol { hardware { off | on } | none } | parity { even | none | odd } | speed { 115200 | 19200 | 38400 | 57600 | 9600 } | stopbits { 1 | 2 } ]
carrierdetect { off | on }
Specifies whether
or not the console port is to use Data Carrier Detect (DCD) when connecting
to a terminal.
Default: off
off: Do
not use DCD.
on: Use
DCD.
databits { 7 | 8 }
Specifies the number
of data bits used to transmit and receive characters.
Default: 8
7: Use 7
databits to transmit and receive characters.
8: Use 8
databits to transmit and receive characters.
flowcontrol { hardware { off | on } | none }
Specifies how the
flow of data is controlled between the SPIO and a terminal.
Default: none
hardware:
Enables or disables the use of hardware-based flow control
off: Disables
the use of Ready to Send (RTS) and Clear to Send (CTS).
on: Enables
the use of Ready to Send (RTS) and Clear to Send (CTS).
none: Disables
the use of DCD, RTS and CTS.
parity { even | none | odd }
Specifies the type
of error checking used on the port.
Default: none
even - Enables
error checking by setting the parity bit to 1 (if needed) making
the number of 1s in the data bits even.
none - Disables
error checking.
odd - Enables
error checking by setting the parity bit to 1 (if needed) making
the number of 1s in the data bits odd.
speed { 115200 | 19200 | 38400 | 57600 | 9600 }
Specifies the flow
of data in bits per second between the console port and terminal.
Default: 9600
stopbits { 1 | 2 }
Specifies the number
of stop bits between each transmitted character.
Default: 1
1: Use one
stop bit between each transmitted character.
2: Use two
stop bits between each transmitted character.
Usage:
Sets the SPIO’s
console port parameters for communication with the terminal device.
Example:
The following command
sets the SPIO’s console port. The terminal must support
these values.
terminal carrierdetect
off databits 7 flowcontrol hardware on parity even speed 115200
stopbits 1
threshold 10sec-cpu-utilization
Configures alarm or
alert thresholds that measure a 10-second average of CPU utilization.
Its polling interval can be set down to 30 seconds.
Privilege:
Security Administrator,
Administrator
Syntax
threshold 10sec-cpu-utilization percent [ clear percent ]
percent
Default: 0
Configures Specifies
the high threshold for 10-second average cpu-utilization. If the monitored
CPU utilization is greater than or equal to the specified percentage
an alert is sent. Regardless of the length of the polling interval,
only one sample at the end of the polling interval is tested.
clear percent
Default: 0:
This is a low watermark
value that sets the alarm clearing threshold value. If not specified
it is taken from the first value.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set a threshold that sends an alert when CPU utilization over a
10-second average exceeds the limit set.
Alerts or alarms are
triggered for 10-second sample of CPU utilization based on the following
rules:
- Enter condition: 10-second
average percentage of CPU utilization is greater than or equal to
the high threshold.
- Clear condition: 10-second
average percentage of CPU utilization is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
generates an alert when the 10-second average CPU utilization reaches
45 percent:
threshold 10sec-cpu-utilization 45
threshold aaa-acct-archive-size
Configures accounting
message archive size, alarm or alert thresholds.
Privilege:
Security Administrator,
Administrator
Syntax
threshold aaa-acct-archive-size high_thresh [ clear low_thresh ]
default threshold
aaa-acct-archive-size
high_thresh
Default: 1
Specifies the high
threshold number of archived accounting messages that must be met
or exceeded within the polling interval to generate an alert or
alarm. high_thresh is
an integer from 0 through 1044000.
clear low_thresh
Default: 1
Specifies the low
threshold number of archived accounting messages that maintains
a previously generated alarm condition. If the number of failures
falls beneath the low threshold within the polling interval, a clear
alarm will be generated. low_thresh is
an integer from 0 through 1044000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
In the event that
the system cannot communicate with configured AAA accounting servers (RADIUS
or CGFs), 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 accounting messages buffered in the archive during the specified
polling interval. Accounting requests are counted for all AAA accounting
servers 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 archived messages that is greater than or equal to the
high threshold.
- Clear condition: Actual
number of archived messages that is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
250 AAA accounting
archived messages and low threshold of
100 for a
system using the Alarm thresholding model:
threshold aaa-acct-archive-size
250 clear 100
threshold aaa-acct-failure
Configures accounting
failure, alarm or alert thresholds for the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold aaa-acct-failure high_thresh [ clear low_thresh ]
default threshold
aaa-acct-failure
high_thresh
Default: 0
Specifies the high
threshold number of accounting failures that must be met or exceeded within
the polling interval to generate an alert or alarm. high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of accounting failures that maintains a previously generated
alarm condition. If the number of failures falls beneath the low
threshold within the polling interval, a clear alarm will be generated. low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Accounting failure
thresholds generate alerts or alarms based on the number of failed AAA
accounting message requests that occur during the specified polling
interval. Accounting requests are counted for all AAA accounting
servers 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 is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 AAA accounting
failures and low threshold of
25 for a system
using the Alarm thresholding model:
threshold aaa-acct-failure
100 clear 25
threshold aaa-acct-failure-rate
Configures accounting
failure rate, alarm or alert thresholds for the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold aaa-acct-failure-rate high_thresh [ clear low_thresh ]
default threshold
aaa-acct-failure-rate
high_thresh
Default: 1
Specifies the high
threshold percent of accounting failures that must be met or exceeded within
the polling interval to generate an alert or alarm. high_thresh is
an integer from 0 and 100.
clear low_thresh
Default: 1
Specifies the low
threshold percent of accounting failures that maintains a previously generated
alarm condition. If the percentage of failures falls beneath the
low threshold within the polling interval, a clear alarm will be
generated. low_thresh is
an integer from 0 through 100.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Accounting failure
rate thresholds generate alerts or alarms based on the percentage
of AAA accounting message requests that failed during the specified
polling interval. Accounting requests are counted for all AAA accounting
servers that the system is configured to communicate with.
Alerts or alarms are
triggered for accounting failure rates based on the following rules:
- Enter condition: Actual
failure percentage is greater than or equal to the high threshold.
- Clear condition: Actual
failure percentage is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a AAA accounting failure rate high threshold percentage
of
30 and
a low threshold percentage of
10 for a system
using the Alarm thresholding model:
threshold aaa-acct-failure-rate
30 clear 10
threshold aaa-auth-failure
Configures authentication
failure, alarm or alert thresholds for the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold aaa-auth-failure high_thresh [ clear low_thresh ]
default threshold
aaa-auth-failure
high_thresh
Default: 0
Specifies the high
threshold number of authentication failures that must be met or
exceeded within the polling interval to generate an alert or alarm.high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of authentication failures that maintains a previously generated
alarm condition. If the number of failures falls beneath the low
threshold within the polling interval, a clear alarm will be generated. low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Authentication failure
thresholds generate alerts or alarms based on the number of failed AAA
authentication message requests that occur during the specified
polling interval. Authentication requests are counted for all AAA
authentication servers that the system is configured to communicate
with.
Alerts or alarms are
triggered for authentication failures based on the following rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 AAA authentication
failures for a system using the Alert thresholding model:
threshold aaa-auth-failure 100
threshold aaa-auth-failure-rate
Configures authentication
failure rate, alarm or alert thresholds for the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold aaa-auth-failure-rate high_thresh [ clear low_thresh ]
default threshold
aaa-auth-failure-rate
high_thresh
Default: 5
Specifies the high
threshold percent of authentication failures that must be met or
exceeded within the polling interval to generate an alert or alarm. high_thresh is
an integer from 0 through 100.
clear
Allows the configuration
of Specifies the low threshold.
low_thresh
Default: 5
Specifies the low
threshold percent of authentication failures that maintains a previously generated
alarm condition. If the percentage of failures falls beneath the
low threshold within the polling interval, a clear alarm will be
generated. low_thresh is
an integer from 0 through 100.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Authentication failure
rate thresholds generate alerts or alarms based on the percentage
of AAA authentication message requests that failed during the specified
polling interval. Authentication requests are counted for all AAA
authentication servers that the system is configured to communicate
with.
Alerts or alarms are
triggered for authentication failures based on the following rules:
- Enter condition: Actual
failure percentage is greater than or equal to the high threshold.
- Clear condition: Actual
failure percentage is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a AAA authentication failure rate high threshold percentage
of
30 for
a system using the Alert thresholding model:
threshold aaa-auth-failure-rate 30
threshold aaa-retry-rate
Configures AAA retry
rate, alarm or alert thresholds for the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold aaa-retry-rate high_thresh [ clear low_thresh ]
default threshold
aaa-retry-rate
high_thresh
Default: 5
Specifies the high
threshold percent of AAA request message retries that must be met
or exceeded within the polling interval to generate an alert or
alarm. high_thresh is
an integer from 0 through 100.
clear low_thresh
Default: 5
Specifies the low
threshold percent of AAA request message retries that maintains
a previously generated alarm condition. If the percentage of retries
falls beneath the low threshold within the polling interval, a clear
alarm will be generated. low_thresh is
an integer from 0 through 100.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
AAA request message
retry rate thresholds generate alerts or alarms based on the percentage
of request messages (both authentication and accounting) that were
retried during the specified polling interval. The percentage is
based on a message count taken for all AAA authentication and accounting
servers that the system is configured to communicate with.
Alerts or alarms are
triggered for request message retries based on the following rules:
- Enter condition: Actual
retry percentage is greater than or equal to the high threshold.
- Clear condition: Actual
retry percentage is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a AAA message retry rate high threshold percentage of
25 and a low
threshold percentage of
10 for
a system using the Alarm thresholding model:
threshold aaa-retry-rate
25 clear 10
threshold aaamgr-request-queue
Configures the AAA
Manager internal request queue, alarm or alert thresholds.
Privilege:
Security Administrator,
Administrator
Syntax
threshold aaamgr-request-queue high_thresh [ clear low_thresh ]
default threshold
aaamgr-request-queue
high_thresh
Default: 0
Specifies the high
threshold number of AAA Manager Requests that must be met or exceeded
within the polling interval to generate an alert or alarm. high_thresh is
an integer from 1 through 100.
clear
Allows the configuration
of Specifies the low threshold.
low_thresh
Default: 5
Specifies the low
threshold number of AAA Manager Requests that maintains a previously generated
alarm condition. If the percentage of failures falls beneath the
low threshold within the polling interval, a clear alarm is generated. low_thresh is
an integer from 0 through 100.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
AAA Manager Request
thresholds generate alerts or alarms based on the number of AAA Manager
Requests for an AAA manager process during the specified polling
interval.
Alerts or alarms are
triggered for AAA Manager Requests based on the following rules:
- Enter condition: Actual
number of AAA Manager Requests per AAA manager is greater than or
equal to the high threshold.
- Clear condition: Actual
number of AAA Manager Requests per AAA manager process is less than
the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm is not generated until
the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a AAA authentication failure rate high threshold percentage
of
30 for
a system using the Alert thresholding model:
threshold aaamgr-request-queue 30
threshold asngw-auth-failure
Configures authentication
failure, alarm or alert thresholds for the ASN-GW system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asngw-auth-failure high_thresh [ clear low_thresh ]
default threshold
asngw-auth-failure
high_thresh
Default: 0
Specifies the high
threshold number of authentication failures that must be met or
exceeded within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of authentication failures that maintains a previously generated
alarm condition. If the number of failures falls beneath the low
threshold within the polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
configure threshold limits to generate alerts or alarms based on
the number of failed ASN-GW authentication message requests that
occur during the specified polling interval. Authentication requests
are counted for all ASN Gateway authentication servers with which
that the system is configured to communicate.
Alerts or alarms are
triggered for authentication failures based on the following rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 authentication
failures for an ASN-GW using the Alert thresholding model:
threshold asngw-auth-failure 100
threshold asngw-handoff-denial
Configures alarm or
alert thresholds for hand-off denials within the ASN-GW service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asngw-handoff-denial high_thresh [ clear low_thresh ]
default threshold
asngw-handoff-denial
high_thresh
Default: 0
Specifies the high
threshold number of hand-off denials that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of hand-off denials that maintains a previously
generated alarm condition. If the number of hand-off denials falls
beneath the low threshold within the polling interval, a clear alarm
will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set threshold limits to generate alerts or alarms based on the number of
denied hand-off that occurred during the specified polling interval.
Hand-off denial messages are counted for all ASN Gateways that the
system is configured to communicate with.
Alerts or alarms are
triggered for hand-off denials based on the following rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 hand-off
denials using the Alert thresholding model:
threshold asngw-handoff-denial 100
threshold asngw-max-eap-retry
Configures alarm or
alert thresholds for maximum retries for Extensible Authentication
Protocol (EAP) authentication within an ASN-GW service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asngw-max-eap-retry high_thresh [ clear low_thresh ]
default threshold asngw-max-eap-retry
high_thresh
Default: 0
Specifies the high
threshold number of retries for EAP authentication that must be
met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of retries for EAP authentication that maintains
a previously generated alarm condition. If the number of retries
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set threshold limits to generate alerts or alarms based on the number of
retries for EAP authentication that occur during the specified polling
interval.
Alerts or alarms are
triggered for maximum number of retries for EAP authentication based
on the following rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 alerts
or alarms generated on maximum number of retries for EAP authentication
for an ASN Gateway using the Alert thresholding model:
threshold asngw-max-eap-retry 100
threshold asngw-network-entry-denial
Configures alarm or
alert thresholds for denials of network entry to an MS within the
ASN-GW service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asngw-network-entry-denial high_thresh [ clear low_thresh ]
default threshold asngw-network-entry-denial
high_thresh
Default: 0
Specifies the high
threshold number of denial of network entry to an MS that must be
met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of denial of network entry to an MS that maintains
a previously generated alarm condition. If the number of denials
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set threshold limits to generate alerts or alarms based on the number of
network entry denials that occurred during the specified polling
interval. Network denial messages are counted for an MS with which
the system is configured to communicate.
Alerts or alarms are
triggered for network entry denials based on the following rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 network
entry denials for an MS using the Alert thresholding model:
threshold asngw-network-entry-denial 100
threshold asngw-session-setup-timeout
Configures alarm or
alert thresholds for session setup timeouts in an ASN-GW service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asngw-session-setup-timeout high_thresh [ clear low_thresh ]
default threshold
asngw-session-setup-timeout
high_thresh
Default: 0
Specifies the high
threshold number of timeouts during session setup that must be met
or exceeded within the polling interval to generate an alert or
alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of timeouts during session setup that maintains
a previously generated alarm condition. If the number of denials
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set threshold limits to generate alerts or alarms based on the number of
timeouts during session setup that occurred during the specified
polling interval.
Alerts
or alarms are triggered for session setup timeouts based on the
following rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 timeouts
during session setup using the Alert thresholding model:
threshold asngw-session-setup-timeout 100
threshold asngw-session-timeout
Configures alarm or
alert thresholds for session timeouts in an ASN-GW service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asngw-session-timeout high_thresh [ clear low_thresh ]
default threshold
asngw-session-timeout
high_thresh
Default: 0
Specifies the high
threshold number of timeouts during session that must be met or
exceeded within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of timeouts during session that maintains a previously generated
alarm condition. If the number of session timeouts falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set threshold limits to generate alerts or alarms based on the number of
timeouts during a session that occurred during the specified polling
interval.
Alerts or alarms are
triggered for session timeouts based on the following rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 timeouts
during a session using the Alert thresholding model:
threshold asngw-session-timeout 100
threshold asnpc-idle-mode-timeout
Configures alarm or
alert thresholds for ASNPC Instant Messenger idle mode timeouts.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asnpc-idle-mode-timeout high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of ASNPC idle mode timeouts that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of ASNPC idle mode timeouts during session
that maintains a previously generated alarm condition. If the number
of session timeouts falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set the maximum number
of idle mode timeouts allowed in the ASNPC service.
Alerts
or alarms are triggered for session timeouts based on the following
rules:
- Enter condition: Actual
number of timeouts is greater than or equal to the high threshold.
- Clear condition: Actual
number of timeouts is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures the high threshold for ASNPC idle mode timeouts at
10000:
threshold asnpc-idle-mode-timeout 10000
threshold asnpc-im-entry-denial
Configures the ASNPC
Instant Messenger (IM) entry denial, alarm or alert thresholds.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asnpc-im-entry-denial high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of IM entry denials during session that
must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of IM entry denials during session that
maintains a previously generated alarm condition. If the number
of session timeouts falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set the maximum number
of IM session denials allowed in the ASNPC service.
Alerts
or alarms are triggered for session timeouts based on the following
rules:
- Enter condition: Actual
number of failures is greater than or equal to the high threshold.
- Clear condition: Actual
number of failures is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures the high threshold for IM session counts at
10000:
threshold asnpc-im-entry-denial 10000
threshold asnpc-lu-denial
Configures the alarm
or alert thresholds for Location Update (LU) denials.
Privilege:
Security Administrator,
Administrator
Syntax
threshold asnpc-lu-denial high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of LU denials during session that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of LU denials during session that maintains
a previously generated alarm condition. If the number of session
timeouts falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 10000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set the maximum number
of Location Update denials allowed in the ASNPC service.
Example:
The following command
configures high threshold of
10000 LU denials:
threshold asnpc-lu-denial 10000
threshold asnpc-session-setup-timeout
Configures alarm or
alert thresholds for ASNPC session setup timeouts in an ASN-GW service.
Privilege:
Security
Administrator, Administrator
Syntax
threshold asnpc-session-setup-timeout value
default threshold
asnpc-session-setup-timeout
value
value is
an integer from 1 through 1000000.
Usage:
Use
this command to set threshold limits to generate alerts or alarms
based on the number of timeouts during session setup that occurred
during the specified polling interval.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a high threshold count of
100 timeouts
during session setup using the Alert thresholding model:
threshold asnpc-session-setup-timeout 100
threshold call-reject-no-resource
Configures alarm or
alert thresholds on the system for calls rejected due to insufficient
resources.
Privilege:
Security Administrator,
Administrator
Syntax
threshold call-reject-no-resource high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of no-resource call rejects issued by the system
that must be met or exceeded within the polling interval to generate
an alert or alarm.
The number is an integer
from 0 through 100000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of no-resource call rejects issued by the system
that maintains a previously generated alarm condition. If the number
of rejections falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
The number is an integer
from 0 through 100000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
No resource call reject
thresholds generate alerts or alarms based on the total number of calls
that were rejected by the system due to insufficient or no resources
(memory and/or session licenses) 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 is greater than or
equal to the high threshold.
- Clear condition: Actual
number of calls rejected due to no resources is less than the low
threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count for the number of calls rejected by
the system due to insufficient or no resources to
100 and allow threshold
of
40 for
a system using the Alarm thresholding model:
threshold call-reject-no-resource
100 clear 40
threshold call-setup
Configures call setup,
alarm or alert thresholds for the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold call-setup high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of calls setup by the system that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 100000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of calls setup by the system that maintains a previously generated
alarm condition. If the number of setups falls beneath the low threshold
within the polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Call setup thresholds
generate alerts or alarms based on the total number of calls setup
by the system during the specified polling interval.
Alerts or alarms are
triggered for call setups based on the following rules:
- Enter condition: Actual
number of call setups is greater than or equal to the high threshold.
- Clear condition: Actual
number of call setups is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 calls
setup for a system using the Alert thresholding model:
threshold call-setup
100
threshold call-setup-failure
Configures call setup
failure, alarm or alert thresholds for the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold call-setup-failure high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of call setup failures experienced by the system
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 100000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold number of call setup failures experienced by the system
that maintains a previously generated alarm condition. If the number
of setup failures falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Call setup failure
thresholds generate alerts or alarms based on the total number of
call setup failures experienced by 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 is greater than or equal to the high
threshold.
- Clear condition: Actual
number of call setup failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
100 call setup
failures and a low threshold of
80 for a system
using the Alarm thresholding model:
threshold call-setup-failure
100 clear 80
threshold card-temperature-near-power-off-limit
Configures alarm or
alert thresholds for triggering and clearing high card temperature
alarms.
Privilege:
Security Administrator,
Administrator
Syntax
threshold card-temperature-near-power-off-limithigh_temp [ clear low_temp ]
high_thresh
Default: 0
Specifies the high
card temperature (in degrees Celsius) that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
card temperature (in degrees Celsius) before a high temperature
alarm is cleared.
low_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set the high and low
temperatures in degrees Celsius that generate and clear alarms.
Example:
The following command
configures sets the high and low temperatures to
40 and
35 degrees:
threshold card-temperature-near-power-off-limit 40
clear 35
threshold cdr-file-space
Configures, alarm
or alert thresholds for monitoring the percentage of total file space
allocated for Charging Data Records (CDRs) used during the polling interval.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cdr-file-space high_thresh [ clear low_thresh ]
default threshold
cdr-file-space
default
Configures this command
with the default threshold settings.
high_thresh
Specifies the high
threshold for percentage of total allocated CDR file space used
that must be met or exceeded at the end of the polling interval
to generate an alert or alarm.
high_thresh is
measured in percentage of total allocated CDR file space used and
is an integer from 0 through 100. A value of 0 disables the threshold.
Default: 90
clear low_thresh
Specifies the low
threshold for percentage of total allocated CDR file space used
that maintains a previously generated alarm condition. If the space
usage falls below Specifies the low threshold within the polling
interval, a clear alarm is generated.
low_thresh is
measured in percentage of total allocated CDR file space used and
is an integer from 0 through 100. A value of 0 disables the threshold.
Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to Specifies
the low threshold.
Usage:
CDR file space usage
generate alerts or alarms based on the percentage of total allocated CDR
file space used during the polling interval.
Alerts or alarms are
triggered for CDR file space usage session based on the following rules:
- Enter condition: Actual
percentage of allocated CDR file space usage is greater than or
equal to the specified percentage of total CDR file space.
- Clear condition: Actual
CDR file space used is less than the specified clear percentage
of total allocated CDR file space usage.
If a trigger condition
exists at the end of the polling interval, the alert or alarm will
not be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a threshold of
65 percent
of total allocated CDR file space usage and a clear threshold of
35 percent:
threshold cdr-file-space
65 clear 35
threshold contfilt-block
Configures, alarm
or alert thresholds for Content Filtering rating operations blocked
during a polling interval at which the threshold are raised or cleared.
Privilege:
Security Administrator,
Administrator
Syntax
threshold contfilt-block high_thresh_value [ clear low_thresh_value ]
default threshold
contfilt-block
default
Configures this command
with the default threshold settings.
high_thresh
Specifies
the high threshold for number of rating operations blocked for content
filtering service that must be met or exceeded at the end of the
polling interval to generate an alert or alarm.
high_thresh is
measured in numbers of total rating operations blocked and is an
integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Specifies the low
threshold for the total number of rating operations blocked for
a content filtering service that maintains a previously generated
alarm condition. If the threshold falls below Specifies the low
threshold within the polling interval, a clear alarm is generated.
low_thresh is
measured in numbers of total rating operations blocked and is an
integer from 0 through 1000000. A value of 0 disables the threshold.
Default: 0
Usage:
Use this command to
configure the threshold for a content filtering service to generates alerts
or alarms based on the number of rating operations blocked for a
content filtering service during the polling interval.
If a trigger condition
exists at the end of the polling interval, the alert or alarm will
not be generated until the end of the polling interval.
Refer to the threshold poll contfilt-block command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a threshold of
65000 rating operations
blocked and a clear threshold of
35000 operations:
threshold contfilt-block
65000 clear 35000
threshold contfilt-rating
Configures, alarm
or alert thresholds for Content Filtering rating operations performed
during a polling interval at which the threshold are raised or cleared.
Privilege:
Security Administrator,
Administrator
Syntax
threshold contfilt-rating high_thresh_value [ clear low_thresh_value ]
default threshold
contfilt-rating
default
Configures
this command with the default threshold settings.
high_thresh
Specifies the high
threshold for number of rating operations performed for content
filtering service that must be met or exceeded at the end of the
polling interval to generate an alert or alarm.
high_thresh is
measured in numbers of total rating operations performed and is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Specifies the low
threshold for the total number of rating operations performed for
a content filtering service that maintains a previously generated
alarm condition. If the threshold falls below Specifies the low
threshold within the polling interval, a clear alarm is generated.
low_thresh is
measured in umber of total rating operations performed and is an
integer from 0 through 1000000. A value of 0 disables the threshold.
Default: 0
Usage:
Use this command to
configure the threshold for a content filtering service to generates alerts
or alarms based on the number of rating operations performed for
a content filtering service during the polling interval.
If a trigger condition
exists at the end of the polling interval, the alert or alarm will
not be generated until the end of the polling interval.
Refer to the threshold poll contfilt-rating command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a threshold of
65000 percent
of total rating operations performed and a clear threshold of
35000 percent:
threshold contfilt-rating
65000 clear 35000
threshold cpu-available-memory
Configures alarm or
alert thresholds for available CPU memory in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cpu-available-memory low_thresh [ clear high_thresh ]
low_thresh
Default: 32
Specifies the low
threshold amount of CPU memory that must be met or exceeded at the polling
time to generate an alert or alarm.
low_thresh is
measured in megabytes (MB) and is an integer from 0 through 2048.
clear high_thresh
Default: 32
Specifies the high
threshold amount of CPU memory that maintains a previously generated alarm
condition. If the memory amount rises above the high threshold within
the polling interval, a clear alarm will be generated.
high_thresh is
measured in megabytes (MB) and is an integer from 0 through 2048.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
CPU available memory
thresholds generate alerts or alarms based on the amount of available
memory for each packet processing card CPU at the polling time.
Although, a single threshold is configured for all CPUs, separate
alerts or alarms can be generated for each CPU.
Alerts or alarms are
triggered for available CPU memory based on the following rules:
- Enter condition: Average
measured amount of memory/CPU for the last 5 minutes is
less than or equal to the low threshold.
- Clear condition: Average
measured amount of memory/CPU for the last 5 minutes is
greater than the high threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
configures a low threshold count of
50 MB CPU
memory available and a high threshold of
112 MB for
a system using the Alarm thresholding model:
threshold cpu-available-memory
50 clear 112
threshold cpu-load
Configures alarm or
alert thresholds for monitoring packet processing card CPU loads
using a 5-minute average measurement. The threshold is enabled by
enabling CPU resource monitoring.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cpu-load high_thresh [ clear low_thresh ]
high_thresh
Default: 0
If the monitored CPU
load is greater than or equal to the specified number an alert is
sent. high_thresh must
be an integer from 0 through 15.
clear low_thresh
Default: 0
This is a low watermark
value that sets the alarm clearing threshold value. If not present
it is taken from the first value. low_thresh must
be an integer from 0 through 15.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to Specifies
the low threshold.
Usage:
Use this command to
set an alert when the card’s CPU load is equal to or greater
than the number specified.
Alerts or alarms are
triggered for CPU load based on the following rules:
- Enter condition: Actual
CPU load is greater than or equal to the high threshold.
- Clear condition: Actual
CPU load is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
IMPORTANT:
This command is not
supported on all platforms.
Example:
To set an alert when
the packet processing card CPU load is over
10 and set
an alert clear when the CPU load drops down equal or less than
7, enter the
following command;
threshold cpu-load
10 clear 7
threshold cpu-memory-usage
Configures, alarm
or alert thresholds for monitoring the percentage of total CPU memory
used during the polling interval.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cpu-memory-usage high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold for percentage of total memory used that must be met or exceeded
at the end of the polling interval to generate an alert or alarm.
high_thresh is
measured as a percentage of total CPU memory used and is an integer
from 0 and 100. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold for percentage of total CPU memory used that maintains
a previously generated alarm condition. If the memory usage falls
below the low threshold within the polling interval, a clear alarm
is generated.
low_thresh is
measured as a percentage of total CPU memory used and is an integer
from 0 and 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to Specifies
the low threshold.
Usage:
CPU memory usage generate
alerts or alarms based on the percentage of total CPU memory used
during the polling interval.
Alerts or alarms are
triggered for CPU memory usage session based on the following rules:
- Enter condition: Actual
percentage of CPU memory usage is greater than or equal to the specified
percentage of total CPU memory.
- Clear condition: Actual
CPU memory usage is less than the specified clear percentage of
total CPU memory usage.
If a trigger condition
exists at the end of the polling interval, the alert or alarm will
not be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a threshold of
65 percent
of total packet processing card CPU memory usage and a clear threshold
of
35 percent:
threshold cpu-memory-usage
65 clear 35
threshold cpu-orbs-crit
Configures thresholds
for generating critical-level alerts or alarms based on the percentage
of CPU utilization by the Object Request Broker System (ORBS) software task.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cpu-orbs-crit high_thresh [ clear low_thresh ]
[ default ] threshold
cpu-orbs-crit
default
Restores this parameter
to its default setting.
high_thresh
Default: 60
Specifies the high
threshold percent of CPU utilization by the ORB software task that
must be exceeded as measured at the time of polling to generate
a critical-level alert or alarm.
high_thresh is
measured in percentage of total CPU utilization and is an integer
from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 60
Specifies the low
threshold percent of CPU utilization by the ORB software task that maintains
a previously generated alarm condition. If the percentage is measured
as less than or equal to Specifies the low threshold at the time
of polling, a clear alarm will be generated.
low_thresh is
measured in percentage of total CPU utilization and is an integer
from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to Specifies
the low threshold.
Usage:
Object Request Broker
(ORB) software task CPU utilization thresholds generate critical-level
alerts or alarms based on the percentage of packet processing 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 following rules:
- Enter condition: Actual
CPU usage percentage is greater than the high threshold.
- Clear condition: Actual
CPU usage percentage is less than or equal to the low threshold.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a critical-level alarm threshold of
35 percent
of CPU utilization by the ORBS task and a clear threshold of
30 percent:
threshold cpu-orbs-crit
35 clear 30
threshold cpu-orbs-warn
Configures thresholds
for generating warning-level alerts or alarms based on the percentage
of CPU utilization by the Object Request Broker System (ORBS) software task.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cpu-orbs-warn high_thresh [ clear low_thresh ]
[ default ] threshold
cpu-orbs-warn
default
Restores this parameter
to its default setting.
high_thresh
Default: 50
Specifies the high
threshold percent of CPU utilization by the ORBS software task that
must be exceeded as measured at the time of polling to generate
a warning-level alert or alarm.
high_thresh is
measured in percentage of total CPU utilization and is an integer
from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 50
Specifies the low
threshold percent of CPU utilization by the ORBS software task that maintains
a previously generated alarm condition. If the percentage is measured
as less than or equal to Specifies the low threshold at the time
of polling, a clear alarm will be generated.
low_thresh is
measured in percentage of total CPU utilization and is an integer
from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to Specifies
the low threshold.
Usage:
Object Request Broker
(ORB) software task CPU utilization thresholds generate warning-level
alerts or alarms based on the percentage of packet processing 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 following rules:
- Enter condition: Actual
CPU usage percentage is greater than the high threshold.
- Clear condition: Actual
CPU usage percentage is less than or equal to the low threshold.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a warning-level alarm threshold of
25 percent
of CPU utilization by the ORBS task and a clear threshold of
20 percent:
threshold cpu-orbs-warn
25 clear 20
threshold cpu-session-throughput
Configures alarm or
alert thresholds for CPU session throughput within the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cpu-session-throughput high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold session throughput that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh is
measured in kilobytes per second (Kbps) and is an integer from 0
through 1000000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low
threshold session thereabout that maintains a previously generated
alarm condition. If the throughput falls below Specifies the low
threshold within the polling interval, a clear alarm will be generated.
low_thresh is
measured in kilobytes per second (Kbps) and is an integer from 0
through 1000000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
CPU session throughput
thresholds generate alerts or alarms based on total throughput for all
Session Manager tasks running on each packet processing card CPU
during the polling interval. Although, a single threshold is configured
for all CPUs, separate alerts or alarms can be generated for each
CPU.
Alerts or alarms are
triggered for CPU session throughput based on the following rules:
- Enter condition: Actual
CPU session throughput is greater than or equal to the high threshold.
- Clear condition: Actual
CPU session throughput is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
configures a high threshold count of
900 Kbps session
throughput and a low threshold of
500 KBps for
a system using the Alarm thresholding model:
threshold cpu-session-throughput
900 clear 500
threshold cpu-utilization
Configures alarm or
alert thresholds for CPU utilization within the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold cpu-utilization high_thresh [ clear low_thresh ]
high_thresh
Default: 85
Specifies the high
threshold CPU utilization percentage that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 100.
clear low_thresh
Default: 85
Specifies the low
threshold CPU utilization percentage that maintains a previously
generated alarm condition. If the utilization percentage falls below
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 100.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
CPU utilization thresholds
generate alerts or alarms based on the utilization percentage of each
packet processing card CPU during the specified polling interval.
Although, a single threshold is configured for all CPUs, separate
alerts or alarms can be generated for each CPU.
Alerts or alarms are
triggered for CPU utilization based on the following rules:
- Enter condition: Average
measured CPU utilization for the last 5 minutes
- Clear condition: Average
measured CPU utilization for the last 5 minutes is less than the
low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
configures a high threshold CPU utilization percentage of
90 for a system
using the Alert thresholding model:
threshold cpu-utilization 90
threshold dcca-bad-answers
Configures alarm or
alert thresholds for invalid or bad responses to the system from
Diameter servers.
Privilege:
Security Administrator,
Administrator
Syntax
threshold dcca-bad-answers high_thresh [ clear low_thresh ]
default threshold
dcca-bad-answers
default
Disables the threshold
for configured alarm and sets the high_thresh and low_thresh values
to 0.
high_thresh
Default: 0
Specifies the high
threshold number of invalid messages or responses that must be met
or exceeded within the polling interval to generate an alert or
alarm.
high_thresh is
an integer from 0 through 1000000.
clear low_thresh
Default: 0
Specifies the low
threshold number of invalid messages/responses that maintains
a previously generated alarm condition. If the number of failures
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 1000000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
In the event that
the system receives invalid message or response from Diameter server dcca-bad-answers is
generated.
DCCA bad answer messages
size threshold generates alerts or alarms based on the number of
invalid response or messages received during the specified polling
interval.
Alerts or alarms are
triggered for DCCA bad answers based on the following rules:
- Enter condition: Actual
number of DCCA bad answer messages is greater than or equal to the
high threshold.
- Clear condition: Actual
number of DCCA bad answer messages is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
The following command
configures a high threshold count of
250 DCCA
bad answer messages and low threshold of
100 for
a system using the Alarm thresholding model:
threshold dcca-bad-answers
250 clear 100
threshold dcca-protocol-error
Configures alarm or
alert thresholds for Diameter Credit Control Application (DCCA)
protocol errors from the Diameter server.
Privilege:
Security Administrator,
Administrator
Syntax
threshold dcca-protocol-error high_thresh [ clear low_thresh ]
default threshold
dcca-protocol-error
default
Disables the threshold
for configured alarm and sets the high_thresh and low_thresh values
to 0.
high_thresh
Default: 0
Specifies the high
threshold number of protocol error received from Diameter server
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 1000000.
clear low_thresh
Default: 0
Specifies the low
threshold number of protocol error received from Diameter server
that maintains a previously generated alarm condition. If the number
of errors falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
In the event that
the system receives the protocol errors from Diameter server, dcca-protocol-error is
generated.
DCCA protocol error
threshold generates alerts or alarms based on the number of protocol error
messages received from Diameter server during the specified polling
interval.
Alerts or alarms are
triggered for DCCA protocol error based on the following rules:
- Enter condition: Actual
number of DCCA protocol error is greater than or equal to the high
threshold.
- Clear condition: Actual
number of DCCA protocol errors is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
The following command
configures a high threshold count of
250 protocol
errors and low threshold of
100 for
a system using the Alarm thresholding model:
threshold dcca-protocol-error
250 clear 100
threshold dcca-rating-failed
Configures Diameter
Credit Control Application (DCCA) Rating Group (content-id) request
reject, alarm or alert thresholds.
Privilege:
Security Administrator,
Administrator
Syntax
threshold dcca-rating-failed high_thresh [ clear low_thresh ]
default threshold
dcca-rating-failed
default
Disables the threshold
for configured alarm and sets the high_thresh and low_thresh values
to 0.
high_thresh
Default: 0
Specifies the high
threshold number of requests for a block of credits due to invalid
Rating Group (content-id), rejected from the Diameter server that
must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 1000000.
clear low_thresh
Default: 0
Specifies the low
threshold number of requests for a block of credits due to invalid
Rating Group (content-id), rejected from the Diameter server that
maintains a previously generated alarm condition. If the number
of errors falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
In the event that
the Diameter server rejects the system request for a block of credits
due to invalid Rating Group, defined as content-id, dcca-rating-failed message
is generated.
Rating Group failed
threshold generates alerts or alarms based on the number of requests rejected
from Diameter server during the specified polling interval.
Alerts or alarms are
triggered for Rating Group failed based on the following rules:
- Enter condition: Actual
number of DCCA Rating Group failed is greater than or equal to the
high threshold.
- Clear condition: Actual
number of DCCA Rating Group failed is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
The following command
configures a high threshold count of
250 requests
rejected and low threshold of
100 for
a system using the Alarm thresholding model:
threshold dcca-rating-failed
250 clear 100
threshold dcca-unknown-rating-group
Configures alarm or
alert thresholds for the unknown Diameter Credit Control Application
(DCCA) Rating Group (content-id) messages returned by Diameter servers.
Privilege:
Security Administrator,
Administrator
Syntax
threshold dcca-unknown-rating-group high_thresh [ clear low_thresh ]
default threshold
dcca-unknown-rating-group
default
Disables the threshold
for configured alarm and sets the high_thresh and low_thresh values
to 0.
high_thresh
Default: 0
Specifies the high
threshold number of unknown Rating Group (content-id) messages sent by
the Diameter server that must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000.
clear low_thresh
Default: 0
Specifies the low
threshold number of unknown Rating Group (content-id) sent by Diameter server
and received by system that maintains a previously generated alarm
condition. If the number of errors falls beneath the low threshold
within the polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
In the event that
the Diameter server sends invalid Rating Groups, content-ids to
the system, dcca-unk-rating-group message
is generated.
Unknown Rating Group
threshold generates alerts or alarms based on the number of unknown
Rating Groups received by the system from Diameter server during
the specified polling interval.
Alerts or alarms are
triggered for unknown rating groups based on the following rules:
- Enter condition: Actual
number of unknown rating groups is greater than or equal to the
high threshold.
- Clear condition: Actual
number of unknown rating groups is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
The following command
configures a high threshold count of
250 unknown
rating groups and low threshold of
100 for
a system using the Alarm thresholding model:
threshold dcca-unknown-rating-group
250 clear 100
threshold diameter
diameter-retry-rate
Configures Diameter
Retry Rate, alarm or alert thresholds based on the percentage of
Diameter requests that were retried during the polling interval.
Privilege:
Security Administrator,
Administrator
Syntax
threshold diameter
diameter-retry-rate high_thresh [ clear low_thresh ]
default threshold
diameter diameter-retry-rate
default
Configures this command
with the default threshold settings.
Default: 0—disabled
high_thresh
Specifies the high
threshold. If, within the polling interval, the percentage of Diameter requests
retried equals or exceeds high_thresh an
alert or alarm is generated.
high_thresh is
an integer from 0 through 100.
Default: 0
clear low_thresh
Specifies the low
threshold. If, within the polling interval, the percentage of Diameter requests
retried falls below low_thresh,
a clear alarm is generated.
low_thresh is
an integer from 0 through 100.
Default: 0
IMPORTANT:
This value is applicable
for the Alarm mode, and ignored for the Alert mode. In addition,
if this value is not configured for the Alarm mode, the system assumes
it is identical to the high threshold.
Usage:
Diameter Retry Rate
threshold generates alerts or alarms based on the percentage of Diameter
requests that were retried during the specified polling interval.
Alerts or alarms are
triggered based on the following rules:
- Enter condition: Percentage
of Diameter requests retried is greater than or equal to the high
threshold.
- Clear condition: Percentage
of Diameter requests retried is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
The following command
configures a high threshold of
75 percent,
and a low threshold of
50 percent
for a system using the Alarm thresholding model:
threshold diameter
diameter-retry-rate 75 clear 50
threshold edr-udr-dropped
flow control
Configures alarm or
alert thresholds to monitor the total number of Event Data Records
(EDRs) and Usage Data Records (UDRs) discarded due to flow control.
Privilege:
Security Administrator,
Administrator
Syntax
threshold edr-udr-dropped-flow-control high_thresh [ clear low_thresh ]
default threshold edr-udr-dropped-flow-control
default
Configures this command
with the default threshold settings.
Default: High threshold:
90; Low threshold: 10
high_thresh
Specifies the high
threshold for total number of EDRs + UDRs dropped due to
flow control, which must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh must
be an integer from 0 through 100000.
A value of 0 disables
the threshold.
Default: 90
clear low_thresh
Specifies the low threshold
for total number of EDRs + UDRs dropped that maintains
a previously generated alarm condition. If the total number of EDRs + UDRs
dropped falls below Specifies the low threshold within the polling
interval, a clear alarm is generated.
low_thresh must
be an integer from 0 through 100000 that must be lower than high_thresh.
A value of 0 disables
the threshold.
Default: 10
Usage:
Use this command to
configure thresholds to monitor the total number of EDRs + UDRs discarded
due to flow control. Alerts or alarms are generated based on the
total number of EDRs + UDRs dropped during polling interval.
Alerts or alarms are
triggered for EDR file space usage session based on the following rules:
- Enter condition: Actual
number of EDRs + UDRs dropped greater than or equal to
the specified number of EDRs + UDRs dropped.
- Clear condition: Actual
number of EDR + UDRs dropped is less than the specified
clear number of EDRs + UDRs dropped.
If a trigger condition
exists at the end of the polling interval, the alert or alarm will
not be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold of
90 and a clear
threshold of
45 to
monitor EDRs + UDRs dropped due to flow control:
threshold edr-udr-dropped-flow-control
90 clear 45
threshold epdg-current-sessions
Configures alarm or
alert thresholds for the number of subscribers currently in Evolved
Packet Date Gateway (ePDG) sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold epdg-current-sessions
default threshold epdg-current-sessions
default
Disables the threshold
for configured alarm and sets the high_thresh and low_thresh values
to 0.
high_thresh
Default: 0
Specifies the high
threshold number of the total number of ePDG subscriber sessions
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 1000000.
clear low_thresh
Default: 0
Specifies the low
threshold number of the total number of ePDG subscriber sessions
that maintains a previously generated alarm condition. If the number
of errors falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Sets the upper and
power thresholds for the total number of ePDG subscriber sessions
that will generate and clear alerts or alarms.
Alerts or alarms are
triggered based on the following rules:
- Enter condition: Actual
number of ePDG subscriber sessions is greater than or equal to the
high threshold.
- Clear condition: Actual
number of ePDG subscriber sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
The following command
configures sets the upper threshold of ePDG subscriber sessions
at
100000 and
the lower threshold at
90000:
threshold epdg-current-sessions
100000 clear 90000
threshold fng-current-active-sessions
Configures alarm or
alert thresholds for the number of subscribers currently active
Femto Network Gateway (FNG) sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold fng-current-active-sessions
default threshold fng-current-actice-sessions
default
Disables the threshold
for configured alarm and sets the high_thresh and low_thresh values
to 0.
high_thresh
Default: 0
Specifies the high
threshold number of the total number of active FNG subscriber sessions that
must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 1000000.
clear low_thresh
Default: 0
Specifies the low
threshold number of the total number of active FNG subscriber sessions that
maintains a previously generated alarm condition. If the number
of errors falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Sets the upper and
power thresholds for the total number of active FNG subscriber sessions
that will generate and clear alerts or alarms.
Alerts or alarms are
triggered based on the following rules:
- Enter condition: Actual
number of active FNG subscriber sessions is greater than or equal
to the high threshold.
- Clear condition: Actual
number of active FNG subscriber sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
The following command
configures sets the upper threshold of active FNG subscriber sessions
at
100000 and
the lower threshold at
90000:
threshold fng-current-active-sessions
100000 clear 90000
threshold fng-current-sessions
Configures alarm or
alert thresholds for the number of subscribers currently in Femto
Network Gateway (FNG) sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold fng-current-sessions
default threshold fng-current-sessions
default
Configures this command
with the default threshold settings.
Default: High threshold:
90; Low threshold: 10
high_thresh
Default: 0
Specifies the high
threshold number of the total number of FNG subscriber sessions
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 1000000.
clear low_thresh
Default: 0
Specifies the low
threshold number of the total number of FNG subscriber sessions
that maintains a previously generated alarm condition. If the number
of errors falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Sets the upper and
power thresholds for the total number of FNG subscriber sessions
that will generate and clear alerts or alarms.
Alerts or alarms are
triggered based on the following rules:
- Enter condition: Actual
number of FNG subscriber sessions is greater than or equal to the
high threshold.
- Clear condition: Actual
number of FNG subscriber sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Example:
200000190000
threshold fng-current-sessions
200000 clear 190000
threshold fw-deny-rule
Configures alarm or
alert thresholds for the Stateful Firewall Deny Rule.
Privilege:
Security Administrator,
Administrator
Syntax
threshold fw-deny-rule high_thresh [ clear low_thresh ]
default threshold fw-deny-rule
default
Configures this command
with the default threshold settings.
Default:
0—disabled
high_thresh
Specifies the Stateful
Firewall Deny-Rule threshold value, which if met or exceeded generates
an alert or alarm.
high_thresh must
be an integer from 0 through 1000000.
Default: 0
clear low_thresh
Specifies the Stateful
Firewall Deny-Rule alarm clear threshold value. If, in the same
polling interval, the threshold falls below low_thresh a
clear alarm is generated.
low_thresh must
be an integer from 0 through 1000000.
Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
When the number of
Deny-Rule instances exceeds a given value, a n alarm or alert is raised;
it is cleared when the number of Deny-Rule instances falls below
a value within the polling interval.
Refer to the threshold poll command
to configure the polling interval, and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a Stateful Firewall Deny Rule high threshold of
1000 and
a low threshold of
900 for
a system using the Alarm Thresholding model:
threshold fw-deny-rule
1000 clear 900
threshold fw-dos-attack
Configures alarm or
alert thresholds for Stateful Firewall Denial-of-Service (DoS) attacks.
Privilege:
Security Administrator,
Administrator
Syntax
threshold fw-dos-attack high_thresh [ clear low_thresh ]
default threshold fw-dos-attack
default
Configures
this command with the default threshold settings.
Default: 0—disabled
high_thresh
Specifies the Stateful
Firewall DoS attacks threshold value, which if met or exceeded generates
an alert or alarm.
high_thresh must
be an integer from 0 through 1000000.
Default:
0
clear low_thresh
Specifies the Stateful
Firewall DoS attacks clear threshold value. If, in the same polling interval,
the threshold falls below low_thresh a
clear alarm is generated.
low_thresh must
be an integer from 0 through 1000000.
Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
When the number of
DoS attacks exceed a given value, a threshold is raised and it is cleared
when the number of DoS attacks fall below a value within the polling
interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a Stateful Firewall DoS attacks high threshold of
1000 and
a low threshold of
100 for
a system using the Alarm Thresholding model:
threshold fw-dos-attack
1000 clear 100
threshold fw-drop-packet
Configures alarm or
alert thresholds for Stateful Firewall dropped packets.
Privilege:
Security Administrator,
Administrator
Syntax
threshold fw-drop-packet high_thresh [ clear low_thresh ]
default threshold fw-drop-packet
default
Configures
this command with the default threshold settings.
Default:
0—disabled
high_thresh
Specifies the Stateful
Firewall dropped packets threshold value, which if met or exceeded generates
an alert or alarm.
high_thresh must
be an integer from 0 through 1000000.
Default: 0
clear low_thresh
Specifies the Stateful
Firewall dropped packets clear threshold value. If, in the same
polling interval, the threshold falls below low_thresh a
clear alarm is generated.
low_thresh must
be an integer from 0 through 1000000.
Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
When the number of
dropped packets exceed a given value, a threshold is raised and
it is cleared when the number of dropped packets fall below a value
within the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a Stateful Firewall dropped packets high threshold of
1000 and
a low threshold of
900 for
a system using the Alarm thresholding model:
threshold fw-drop-packet
1000 clear 900
threshold fw-no-rule
Configures alarm or
alert thresholds for Stateful Firewall no rule occurrences.
Privilege:
Security Administrator,
Administrator
Syntax
threshold fw-no-rule high_thresh [ clear low_thresh ]
default threshold fw-no-rule
default
Configures
this command with the default threshold settings.
Default:
0—disabled
high_thresh
Specifies the Stateful
Firewall no rules threshold value, which if met or exceeded generates an
alert or alarm.
high_thresh must
be an integer from 0 through 1000000.
Default: 0
clear low_thresh
Specifies the Stateful
Firewall no rules clear threshold value. If, in the same polling
interval, the threshold falls below low_thresh a
clear alarm is generated.
low_thresh must
be an integer from 0 through 1000000.
Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
When the number of
no rule occurrences exceeds a given value, a threshold is raised
and it is cleared when the number of no rules fall below a value
within the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a Stateful Firewall no rule high threshold of
1000 and
a low threshold of
900 for
a system using the Alarm Thresholding model:
threshold fw-no-rule
1000 clear 900
threshold license
remaining-sessions
Configures alarm or
alert thresholds for the percentage of session license utilization
by the system.
Privilege:
Security Administrator,
Administrator
Syntax
[ no ] threshold
license remaining-sessions low_thresh clear high_thresh
no low_thresh
Disables threshold
session license utilization alerts or alarms.
remaining-sessions low_thresh
Default: 10
Specifies the low
threshold session license utilization percentage that must be met
or exceeded within the polling interval to generate an alert or
alarm.
low_thresh is
an integer from 0 through 100.
clear high_thresh
Default: 10
Specifies the high
threshold session license utilization percentage that maintains
a previously generated alarm condition. If the utilization percentage
rises above the high threshold within the polling interval, a clear
alarm will be generated.
high_thresh is
an integer from 0 through 100.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to Specifies
the low threshold.
Usage:
Session license utilization
thresholds generate alerts or alarms based on the utilization percentage
of all session capacity licenses during the specified polling interval.
The system uses session
capacity license to dictate the maximum number of simultaneous sessions
that can be supported. There are multiple session types that require
licenses. Although, a single threshold is configured for all session
types, alerts or alarms can be generated for each type.
Alerts or alarms are
triggered for session license utilization based on the following
rules:
- Enter condition: Actual
session license utilization percentage per session type is greater
than or equal to the low threshold.
- Clear condition: Actual
session license utilization percentage per session type is greater
than the high threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a session license low threshold percentage of
10 and a high
threshold of
35 for
a system using the Alarm thresholding model:
threshold license
remaining-sessions 10 clear 35
threshold mgmt-cpu-memory-usage
Configures alarm or
alert thresholds for the percentage of CPU memory usage on management
cards.
Privilege:
Security Administrator,
Administrator
Syntax
threshold mgmt-cpu-memory-usage high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold percent of CPU memory usage that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh is
measured in percentage of total memory used and can be configured
to an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Specifies the low
threshold percent of CPU memory usage that maintains a previously generated
alarm condition. If the percentage falls beneath the low threshold
within the polling interval, a clear alarm will be generated.
low_thresh is
measured in percentage of total memory used and can be configured
to an integer from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
CPU memory usage thresholds
generate alerts or alarms based on memory usage for the SPC, SMC,
or MIO CPU during the polling interval. A single threshold enables
CPU monitoring for both the active and standby SPCs, SMCs, or MIOs
allowing for alerts or alarms to be generated for each CPU.
Alerts or alarms are
triggered for SPC, SMC, or MIO CPU memory usage based on the following
rules:
- Enter condition: Actual
CPU memory usage is greater than or equal to the high threshold
- Clear condition: Actual
CPU memory usage is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
configures a threshold of
65 percent
of total SPC, SMC, or MIO CPU memory usage and a clear threshold
of
35 percent:
threshold mgmt-cpu-memory-usage
65 clear 35
threshold mgmt-cpu-utilization
Configures alarm or
alert thresholds for the percentage of CPU utilization on management
cards.
Privilege:
Security Administrator,
Administrator
Syntax
threshold mgmt-cpu-utilization high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold CPU utilization percentage that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 100.
clear low_thresh
Specifies the low
threshold CPU utilization percentage that maintains a previously
generated alarm condition. If the utilization percentage falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 100.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
CPU utilization thresholds
generate alerts or alarms based on the utilization percentage of each
SPC, SMC, or MIOCPU during the specified polling interval. Although,
a single threshold is configured for both SPC, SMC, or MIO CPUs,
separate alerts or alarms can be generated for each CPU.
Alerts or alarms are
triggered for SPC, SMC, or MIO CPU utilization based on the following
rules:
- Enter condition: Average
measured CPU utilization for the last 5 minutes is greater than
or equal to the high threshold.
- Clear condition: Average
measured CPU utilization for the last 5 minutes is less than the
low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
IMPORTANT:
This command is not
supported on all platforms.
Example:
The following command
configures a high threshold SPC, SMC, or MIO CPU utilization percentage
of
90 for
a system using the Alert thresholding model:
threshold mgmt-cpu-utilization 90
threshold mme-attach-failure
Configures alarm or
alert thresholds for the total number of MME Attach Failure messages
across all the MME services in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold total-mme-attach-failure high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high
threshold number of total MME Attach Failure messages across all services
on a system that must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh can
be configured to an integer from 0 through 100000. A value
of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low
threshold number of total MME Attach Failure messages across all services
on a system that maintains a previously generated alarm condition.
If the number of MME Attach Failure messages across all the services
in a system, falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
monitor and set alarms or alerts when the total number of MME Attach
Failure message across all the MME services in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for the total number of MME Attach Failure message based on
the following rules:
- Enter condition: Actual
total number of MME Attach Failure messages is greater than or equal
to the high threshold.
- Clear condition: Actual
total number of MME Attach Failure messages is less than the low
threshold
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer to the threshold poll mme-attach-failure command
to configure the polling interval and the threshold monitoring mme-service command
to enable thresholding for this value.
Example:
The following command
configures the limit of MME Attach Failure high threshold count of
10000 for
a system using the Alert thresholding model:
threshold mme-attach-failure 10000
threshold mme-auth-failure
Configures alarm or
alert thresholds for the total number of MME Auth Failure messages
across all the MME services.
Privilege:
Security Administrator,
Administrator
Syntax
threshold total-mme-auth-failure high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high
threshold number of total MME Auth Failure messages across all MMM services
on a system that must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh can
be configured to an integer from 0 through 100000. A value
of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low
threshold number of total MME Auth Failure messages across all services on
a system that maintains a previously generated alarm condition.
If the number of MME Attach Failure messages across all the services
in a system, falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
monitor and set alarms or alerts when the total number of MME Auth Failure
message across all the MME services in the system is equal to or
greater than the set limit.
Alerts
or alarms are triggered for the total number of MME Auth Failure
message based on the following rules:
- Enter condition: Actual
total number of MME Auth Failure messages is greater than or equal
to the high threshold.
- Clear condition: Actual
total number of MME Auth Failure messages is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll mme-auth-failure command
to configure the polling interval and the threshold monitoring mme-service command
to enable thresholding for this value.
Example:
The following command
configures a total MME Auth Failure high threshold count of
10000 for
a system using the Alert thresholding model:
threshold mme-auth-failure 10000
threshold model
Configures the thresholding
model, alarm or alert, for the system to use.
Privilege:
Security Administrator,
Administrator
Syntax
threshold model { alarm | alert }
alarm
Selects the alarm
thresholding model as described in the Usage section for
this command.
alert
Selects the alert
thresholding model as described in the Usage section for
this command.
Usage:
The system supports
the following thresholding models:
- Alert: A value
is monitored and an alert condition occurs when the value reaches
or exceeds the configured high threshold within the specified polling
interval. The alert is generated then generated and/or
sent at 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 the point where the count exceeded the high threshold.
- Alarm: Both high
and low threshold are defined for a value. An alarm condition occurs
when the value reaches or exceeds the configured high threshold
within the specified polling interval. The alert is generated then
generated 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.
In the example shown
in the figure below, this model generates an alarm during period
2 when the count exceeds the high threshold. A second alarm is generated
in period 6 when the count falls beneath low threshold. The second
alarm indicates a “clear” condition.
Figure 1. Thresholding Model
Example
IMPORTANT:
For certain values
the alert or alarm serves to warn of low quantities (such as, memory, session
licenses, etc.). In these cases, the low threshold is the condition
that must be met or exceeded within the polling interval to generate
the alert or alarm. When the high threshold is exceeded during an interval,
the low quantity condition is cleared.
Refer to the threshold monitoring command
for additional information on thresholding.
Example:
The following command
configures the system to support the Alarm thresholding model:
threshold model alarm
threshold monitoring
Enables threshold
monitoring for the selected value.
Syntax
[ no | default ] threshold
monitoring { aaa-acct-archive-size | aaa-acct-failure | aaa-auth-failure | aaa-retry-rate | aaamgr-request-queue | asngw | call-setup | content-filtering | cpu-resource | cpu-session-throughput | diameter | ecs | fa-service | firewall | ha-service | hnbgw-service | hsgw-service | ipsec | license | lma-service | mme-service | packets-filtered-dropped | packets-forwarded-to-cpu | pdsn-service | pdg-service | pdif-service | pgw-service | route-service | sgw-service | subscriber | system | tpo }
no
Disables threshold
monitoring for the specified value.
default
Sets or restores the
default value assigned to the specified parameter.
aaa-acct-archive-size
Enables threshold
monitoring for the size of the AAA accounting record archive.
aaa-acct-failure
Enables threshold
monitoring for AAA accounting failures and AAA accounting failure
rate values.
Refer to the threshold aaa-acct-failure and threshold aaa-acct-failure-rate commands
for additional information on these values.
aaa-auth-failure
Enables threshold
monitoring for AAA authentication failures and AAA authentication failure
rate values.
Refer to the threshold aaa-auth-failure and threshold aaa-auth-failure-rate commands
for additional information on these values.
aaa-retry-rate
Enables threshold
monitoring for the AAA retry rate value.
Refer to the threshold aaa-retry-rate command
for additional information on this value.
aaamgr-request-queue
Enables threshold
monitoring for AAA Manager Requests for each AAA manager process. Refer
to the threshold
aaamgr-request-queue command for additional information
on these values.
asngw
Enables the threshold
monitoring for ASN-GW services.
call-setup
Enables threshold
monitoring for the call setup, call setup failures, and no-resource
rejected call values.
Refer to the threshold call-setup,
threshold call-setup-failure, threshold ppp-setup-fail-rate, threshold
rp-setup-fail-rate, and threshold call-reject-no-resource commands
for additional information on these values.
cpu-resource
Enables threshold
monitoring for CPU thresholds.
Refer to the threshold 10sec-cpu-utilization,
threshold cpu-available-memory, threshold cpu-load, threshold cpu-memory-usage, threshold
cpu-orbs-crit, threshold cpu-orbs-warn, threshold cpu-session-throughput,
threshold cpu-utilization, threshold mgmt-cpu-memory-usage, and threshold mgmt-cpu-utilization commands
for additional information on these values.
cpu-session-throughput
Enables threshold
monitoring for the CPU session throughput value.
Refer to the threshold cpu-session-throughput command
for additional information on this value.
content-filtering
Enables threshold
monitoring for the Content Filtering in-line service.
diameter
Enables threshold
monitoring for Diameter.
ecs
Enables threshold
monitoring for the Active Charging Service (ACS)/Enhanced
Charging Service (ECS).
fa-service
Enables threshold
monitoring for Registration Reply errors for each FA service.
Refer to the threshold reg-reply-error FA
Service Configuration Mode command for additional information on
this value.
firewall
Enables threshold
monitoring for the Stateful Firewall in-line service.
Default: Disabled
Refer to the threshold fw-deny-rule,
threshold fw-dos-attack, threshold fw-drop-packet, and threshold fw-no-rule commands
for additional information on this value.
IMPORTANT:
Stateful Firewall
thresholds can only be enabled if the Stateful Firewall license
is present.
ha-service
Enables threshold
monitoring for Registration Reply errors, re-registration reply
errors, deregistration reply errors, and average calls setup per
second for each HA service and average calls setup per second at
the context level.
Refer to the threshold init-rrq-rcvd-rate,
threshold reg-reply-error, threshold rereg-reply-error, and threshold dereg-reply-error HA
Service Configuration Mode commands and the threshold ha-service
init-rrq-rcvd-rate Context Configuration mode command
for additional information on this value.
hnbgw-service
Enables threshold
monitoring for HNB-GW sessions including Iu-CS and Iu-PS sessions
for HNB-GW services on a system at the system level.
IMPORTANT:
This keyword is required
to activate the threshold alarm/alert for HNB-GW service
to use threshold
total-hnbgw-hnb-sessions, thresshold total-hnbgw-iu-sessions,
and thresshold
total-hnbgw-ue-sessions command for threshold values.
hsgw-service
Enables threshold
monitoring for HSGW services.
Refer
to the threshold total-hsgw-sessions for more information on HSGW thresholds.
ipsec
Enables monitoring
of IPSec thresholds.
refer to the HA-Service
Configuration Mode chapter of the Command Line Interface Reference
for information on the IPSec thresholds.
license
Enables threshold
monitoring for the session license value.
Refer to the threshold license command
for additional information on this value.
lma-service
Enables threshold
monitoring for LMA services.
Refer
to the threshold total-lma-sessions for more information on LMA thresholds.
mme-service
Default: Disabled.
Enables threshold
monitoring for the MME services.
Refer to the threshold total-mme-sessions commands for
additional information on this value.
packets-filtered-dropped
Enables threshold
monitoring for the filtered/dropped packet value.
Refer to the threshold packets-filtered-dropped command
for additional information on this value.
packets-forwarded-to-cpu
Enables threshold
monitoring for the forwarded packet value.
Refer to the threshold packets-forwarded-to-cpu command
for additional information on this value.
pdg-service
Enables threshold
monitoring for PDG service.
Threshold monitoring
for PDG service is disabled by default.
pdif-service
Enables threshold
monitoring for PDIF service.
pdsn-service
Enables threshold
monitoring for average calls setup per second for contexts and for
PDSN services, A11 Request.
Refer to the threshold packets-forwarded-to-cpu command
for additional information on this value.
pgw-service
Enables threshold
monitoring for P-GW services.
Refer
to the threshold total-pgw-sessions for more information on P-GW thresholds.
route-service
Enables threshold
monitoring for BGP/VRF route services.
Refer to the ip maximum-routes command
in Context configuration mode and threshold route-service
bgp-routes in this mode for more information on route
thresholds.
sgw-service
Enables
threshold monitoring for S-GW services.
Refer
to the threshold total-sgw-sessions for more information on S-GW thresholds.
subscriber
Enables threshold
monitoring for the subscriber and session values.
Refer to the
threshold subscriber
active,
threshold
subscriber total, threshold total-ggsn-sessions,
threshold total-gprs-sessions, threshold
total-gprs-pdp-sessions, threshold total-ha-sessions,
threshold total-lns-sessions, threshold total-pdsn-sessions, threshold total-sgsn-sessions,
threshold total-sgsn-pdp-sessions,
threshold per-service-ggsn-sessions,
threshold per-service-ha-sessions, t
hreshold per-service-lns-sessions,
and
threshold
per-service-pdsn-sessions commands for additional information
on these values.
system
Enables system (chassis)
thresholds monitoring.
tpo
Enables thresholds
monitoring for Traffic Performance Optimization (TPO) in-line service.
Usage:
Thresholding on the
system is used to monitor the system for conditions that could potentially
cause errors or outage. Typically, these conditions are temporary
(i.e high CPU utilization, or packet collisions on a network) and
are quickly resolved. However, continuous or large numbers of these
error conditions within a specific time interval may be indicative
of larger, more severe issues. The purpose of thresholding is to
help identify potentially severe conditions so that immediate action
can be taken to minimize and/or avoid system downtime.
Thresholding reports
conditions using one of the following mechanisms:
- SNMP traps: SNMP
traps have been created that indicate the condition (high threshold
crossing and/or clear) of each of the monitored values.
Complete descriptions and other information pertaining to these
traps 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
only those 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 Log messages pertaining to the condition of a monitored
value are generated with a severity level of WARNING.
- 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 through the CLI.
The following table
indicates the reporting mechanisms supported by each of the above models.
Table 1. ASR 5000
Thresholding Reporting Mechanisms by Model
Model |
SNMP
Traps |
Logs |
Alarm
System |
Alert
|
X
|
X
|
|
Alarm
|
X
|
X
|
X
|
In addition to the
values that can be enabled by this command, the system supports
the enabling of threshold monitoring for IP pool address availability
(refer to the ip pool and
threshold commands in this reference) and port utilization (refer
to the threshold commands in this chapter).
Example:
The following command
enables thresholding for subscriber totals:
threshold monitoring subscriber
threshold nat-port-chunks-usage
Configures alarm or
alert thresholds for the percentage of Network Address Translation
(NAT) port chunk utilization.
IMPORTANT:
This command is only
available in 8.3 and later releases.
Privilege:
Security Administrator,
Administrator
Syntax
threshold nat-port-chunks-usage high_thresh [ clear low_thresh ]
default threshold nat-port-chunks-usage
default
Configures
this command with the default threshold settings.
Default:
0—disabled
high_thresh
Specifies the high
NAT-port-chunks-usage percentage threshold that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh must
be an integer from 0 through 100. A value of 0 disables the threshold.
Default: 0
clear low_thresh
Specifies the low
nat-port-chunks-usage percentage threshold that must be met within
the polling interval for a clear alarm to be generated.
low_thresh must
be an integer from 0 through 100. A value of 0 disables the threshold.
If not set, the high_thresh will
be the high and low threshold setting.
Default: 0
Usage:
Use this command to
configure the NAT port chunk utilization threshold settings.
Example:
The following command
sets the NAT port chunk utilization threshold settings to a high
of
75% and
a low of
15%:
threshold nat-port-chunks-usage
75 clear 15
threshold npu-utilization
Configures alarm or
alert thresholds for the percentage of network processing unit (NPU)
utilization.
Privilege:
Security Administrator,
Administrator
Syntax
threshold npu-utilization
default
Configures
this command with the default threshold settings.
Default:
0—disabled
high_thresh
Specifies the high
percentage threshold for NPU utilization that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh must
be an integer from 0 through 100. A value of 0 disables the threshold.
Default: 0
clear low_thresh
Specifies the low
percentage threshold for NPU utilization that must be met within
the polling interval for a clear alarm to be generated.
low_thresh must
be an integer from 0 through 100. A value of 0 disables the threshold.
If not set, the high_thresh will
be the high and low threshold setting.
Default: 0
Usage:
Use this command to
configure the NPU utilization threshold settings.
Example:
The following command
sets the NPU utilization threshold settings to a high of
90% and
a low of
75%:
threshold npu-utilization
90 clear 75
threshold packets-filtered-dropped
Configures alarm or
alert thresholds for filtered or dropped packets within the system.
Product:
PDSN
, GGSN, HA
, SGSN, ASN GW
Privilege:
Security Administrator,
Administrator
Syntax
threshold packets-filtered-dropped high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of filtered/dropped packets experienced
by the system resulting from access control list (ACL) rules that
must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 1000000000. A value of 0 disables the
threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of filtered/dropped packets experienced by the system resulting
from ACL rules that maintains a previously generated alarm condition.
If the number of packets falls beneath the low threshold within
the polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000000. A value of 0 disables the
threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Filtered/dropped
packet thresholds generate alerts or alarms based on the total number
of packets that were filtered 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 is greater than or equal
to the high threshold.
- Clear condition: Actual
number of filtered/dropped packets is less than the low
threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value. In addition, refer to information
on ACLs in this reference.
Example:
The following command
configures a filtered/dropped packet high threshold count
of
150000 for
a system using the Alert thresholding model:
threshold packets-filtered-dropped 150000
threshold packets-forwarded-to-cpu
Configures alarm or
alert thresholds for packets forwarded to active system CPUs in
the system.
Product:
PDSN
, GGSN, HA
, SGSN, ASN GW
Privilege:
Security Administrator,
Administrator
Syntax
threshold packets-forwarded-to-cpu high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of packets forwarded to CPUs that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000000. A value of 0 disables the
threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of packets forwarded to CPUs that maintains a previously
generated alarm condition. If the number of packets falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 1000000000. A value of 0 disables the
threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Forwarded packet thresholds
generate alerts or alarms based on the total number of packets that
were forwarded to active system CPU(s) during the specified polling
interval. Packets are forwarded to active system CPUs when the NPUs
do not have adequate information to properly route them.
IMPORTANT:
Ping and/or
traceroute packets are intentionally forwarded to system CPUs for
processing. These packet types are included in the packet count
for this threshold.
Alerts or alarms are
triggered for forwarded packets based on the following rules:
- Enter condition: Actual
number of forwarded packets is greater than or equal to the high
threshold
- Clear condition: Actual
number of forwarded packets is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a forwarded packet high threshold count of
100000 for
a system using the Alert thresholding model:
threshold packets-forwarded-to-cpu 100000
threshold pdg-current-active-sessions
Configures alarm or
alert thresholds for monitoring the total number of currently active
Packet Data Gateway/Tunnel Termination Gateway (PDG/TTG)
sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold pdg-current-active-sessions high_thresh [ clear low_thresh ]
high_thresh
Configures the total
number of active PDG sessions to be monitored on a chassis. high_thresh is
an integer from 0 through 1000000.
There is no default,
but 0 means that there is no threshold monitoring.
clear low_thresh
Clears the number of
sessions being monitored using the high_thresh variable
defined above.
low_thresh is
an integer from 0 through 1000000.
Usage:
Thresholds are provided
for monitoring the overall PDG usage on a chassis. This command
is used to monitor the total number of active PDG sessions for an
entire chassis.
Example:
The following command
configures a monitoring threshold of
300000 and
a clearing threshold of 100000 active PDG sessions on a chassis:
threshold pdg-current-active-sessions
300000 clear 100000
threshold pdg-current-sessions
Configures alarm or
alert thresholds for monitoring the total number of current Packet
Data Gateway/Tunnel Termination Gateway (PDG/TTG)
sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold pdg-current-sessions high_thresh [ clear low_thresh ]
high_thresh
Configures the total
number of PDG sessions on a chassis, both active and inactive. high_thresh is
any integer from 0 through 1000000.
There is no default,
but 0 means that there is no threshold monitoring.
clear low_thresh
Clears any number of
sessions being monitored using the high_thresh variable
defined above.
low_thresh is
any integer from 0 through 1000000.
Usage:
Thresholds are provided
for monitoring the overall PDG usage on a chassis. This command
is used to monitor the total number of PDG sessions, both active
and inactive, for an entire chassis.
Example:
The following command
configures a monitoring threshold of
300000 and
a clearing threshold of
100000 active
and inactive PDG sessions on a chassis:
threshold pdg-current-sessions
300000 clear 100000
threshold pdif-current-active-sessions
Configures alarm or
alert thresholds for monitoring the total number of currently active
Packet Data Interworking Function (PDIF) sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold pdif-current-active
sessions high_thresh [ clear low_thresh ]
high_thresh
Configures the total
number of active PDIF sessions to be monitored on a chassis. high_thresh is
any integer from 0 through 1000000.
There is no default,
but 0 means that there is no threshold monitoring.
clear low_thresh
Clears the specified
number of sessions being monitored using the high_thresh variable
defined above. low_thresh is
any integer from 0 through 1000000.
Usage:
Thresholds are provided
for monitoring the overall PDIF usage on a chassis. This command
is used to monitor the total number of active PDIF sessions for
an entire chassis.
Example:
The following command
configures a monitoring threshold of
300000 and
a clearing threshold of
100000 active
PDIF sessions on a chassis:
threshold pdif-current-active-sessions
300000 clear 100000
threshold pdif-current-sessions
Configures alarm or
alert thresholds for monitoring the total number of current Packet
Data Interworking Function (PDIF) sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold pdif-current-sessions high_thresh [ clear low_thresh ]
high_thresh
Configures the total
number of PDIF sessions on a chassis, both active and inactive. high_thresh is
an integer from 0 through 1000000.
There is no default,
but 0 means that there is no threshold monitoring.
clear low_thresh
Clears the specified
number of sessions being monitored using the high_thresh variable
defined above. low_thresh is
an integer from 0 through 1000000.
Usage:
Thresholds are provided
for monitoring the overall PDIF usage on a chassis. This command
is used to monitor the total number of PDIF sessions, both active
and inactive, for an entire chassis.
Example:
The following command
configures a monitoring threshold of
300000 and
a clearing threshold of
100000 active
and inactive PDIF sessions on a chassis:
threshold pdif-current-sessions
300000 clear 100000
threshold per-service-asngw-sessions
Configures alarm or
alert thresholds for the number of sessions per ASN-GW service in
the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-asngw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of PDP contexts for any one ASN-GW service that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of PDP contexts for any one ASN-GW service that maintains
a previously generated alarm condition. If the number of sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 2500000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of PDP contexts for any ASN-GW service
in the system is equal to or greater than the set limit.
Alerts or alarms are
triggered for PDP contexts based on the following rules:
- Enter condition: Actual
number of PDP contexts for any ASN-GW service is greater than or
equal to the high threshold
- Clear condition: Actual
number of PDP contexts is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
10000 subscriber
attaches per GGSN service for the Alert thresholding model:
threshold per-service-asngw-sessions 10000
threshold per-service-ggsn-sessions
Configures alarm or
alert thresholds for the number of PDP contexts per GGSN service
in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold per-service-ggsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of PDP contexts for any one GGSN service
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of PDP contexts for any one GGSN service
that maintains a previously generated alarm condition. If the number
of sessions falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor
and set alarms or alerts when the number of PDP contexts for any
GGSN service in the system is equal to or greater than the set limit.
Alerts
or alarms are triggered for PDP contexts based on the following
rules:
- Enter condition: Actual
number of PDP contexts for any GGSN service is greater than or equal
to the high threshold
- Clear condition: Actual
number of PDP contexts is less than the low threshold
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
10000 subscriber
attaches per GGSN service for the Alert thresholding model:
threshold per-service-ggsn-sessions 10000
threshold per-service-gprs-pdp-sessions
Configures alarm or
alert thresholds for the number of 2G-activated PDP contexts per
GPRS service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-gprs-pdp-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of 2G-activated PDP contexts for any one GPRS service.
This number must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of 2G-activated PDP contexts for any one GPRS service. This
number or higher maintains a previously generated alarm condition.
If the number of sessions falls beneath the low threshold within
the polling interval, then a clear alarm will be generated.
low_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of 2G-activated PDP contexts for any GPRS
service in the system is equal to or greater than the set limit.
Alerts or alarms are
triggered for PDP contexts based on the following rules:
- Enter condition: Actual
number of PDP contexts for any GPRS service is greater than or equal
to the high threshold.
- Clear condition: Actual
number of PDP contexts is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
10000 2G-activated
PDP contexts per GPRS service for the Alert thresholding model:
threshold per-service-gprs-sessions 10000
threshold per-service-gprs-sessions
Configures alarm or
alert thresholds for the number of 2G-attached subscribers per GPRS
service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-gprs-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of 2G-attached subscribers for any one GPRS service. This
threshold number must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of 2G-attached subscribers for any one GPRS service. The
number of subscribers must remain above this threshold in order
to maintain a previously generated alarm condition. If the number
of 2G subscribers falls beneath the low threshold within the polling
interval, then a clear alarm will be generated.
low_thresh is
an integer from 0 through 2000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of 2G-attached subscribers for any GPRS
service in the system is equal to or greater than the set limit.
Alerts or alarms are
triggered for PDP contexts based on the following rules:
- Enter condition: Actual
number of 2G-attached subscribers for any GPRS service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of 2G-attached subscribers is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
10000 2G-attaches
per GPRS service for the Alert thresholding model:
threshold per-service-gprs-sessions 10000
threshold per-service-ha-sessions
Configures alarm or
alert thresholds for the number of HA sessions per Home Agent (HA)
service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-ha-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of HA sessions for any one HA service that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of HA sessions for any one HA service that maintains a previously
generated alarm condition. If the number of sessions falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of HA sessions for any HA service in the
system is equal to or greater than the set limit.
Alerts or alarms are
triggered for HA sessions based on the following rules:
- Enter condition: Actual
number of HA sessions for any HA service is greater than or equal
to the high threshold.
- Clear condition: Actual
number of HA sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a HA session per service high threshold count of
10000 for
a system using the Alert thresholding model:
threshold per-service-ha-sessions 10000
threshold per-service-lns-sessions
Configures alarm or
alert thresholds for the number of L2TP Network Server (LNS) sessions
per LNS service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-lns-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of LNS sessions for any one LNS service that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of LNS sessions for any one LNS service that maintains a
previously generated alarm condition. If the number of LNS sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 2500000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of LNS sessions for any LNS service in the
system is equal to or greater than the set limit.
Alerts or alarms are
triggered for LNS sessions based on the following rules:
- Enter condition: Actual
number of LNS sessions for any LNS service is greater than or equal
to the high threshold.
- Clear condition: Actual
number of LNS sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a LNS session per service high threshold count of
10000 for
a system using the Alert thresholding model:
threshold per-service-lns-sessions 10000
threshold per-service-pdg-sessions
Configures alarm or
alert thresholds for the number of Packet Data Gateway (PDG) sessions
per PDG/TTG service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-pdg-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of PDG sessions for any one PDG service that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of PDG sessions for any one PDG service that maintains a
previously generated alarm condition. If the number of PDG sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of PDG sessions for any PDG service in the
system is equal to or greater than the set limit.
Alerts or alarms are
triggered for PDSN sessions based on the following rules:
- Enter condition: Actual
number of PDG sessions for any PDG service is greater than or equal
to the high threshold.
- Clear condition: Actual
number of PDSN sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a PDG session per service high threshold count of
10000 for
a system using the Alert thresholding model:
threshold per-service-pdg-sessions 10000
threshold per-service-pdsn-sessions
Configures alarm or
alert thresholds for the number of Packet Data Serving Node (PDSN)
sessions per PDSN service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-pdsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of PDSN sessions for any one PDSN service that
must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of PDSN sessions for any one PDSN service that maintains
a previously generated alarm condition. If the number of PDSN sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 2500000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of PDSN sessions for any PDSN service in
the system is equal to or greater than the set limit.
Alerts or alarms are
triggered for PDSN sessions based on the following rules:
- Enter condition: Actual
number of PDSN sessions for any PDSN service is greater than or
equal to the high threshold.
- Clear condition: Actual
number of PDSN sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a PDSN session per service high threshold count of
10000 for
a system using the Alert thresholding model:
threshold per-service-pdsn-sessions 10000
threshold per-service-sgsn-pdp-sessions
Configures alarm or
alert thresholds for the number of 3G-activated PDP contexts per
SGSN service on the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-sgsn-pdp-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of 3G-activated PDP contexts for any one SGSN service.
This number must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of 3G-activated PDP contexts for any one SGSN service. This
number or higher maintains a previously generated alarm condition.
If the number of 3G-activated PDP contexts falls beneath the low
threshold within the polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 2400000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of 3G-activated PDP contexts for any SGSN
service in the system is equal to or greater than the set limit.
Alerts or alarms are
triggered for PDP contexts based on the following rules:
- Enter condition: Actual
number of 3G-activated PDP contexts for any SGSN service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of 3G-activated PDP contexts is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
10000 3G-activated
PDP contexts per SGSN service for the system’s Alert thresholding
model:
threshold per-service-sgsn-sessions 10000
threshold per-service-sgsn-sessions
Configures alarm or
alert thresholds for the number of 3G-attached subscribers per SGSN
service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold per-service-sgsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of 3G-attached subscribers for any one SGSN service. This
number must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of 3G-attached subscribers for any one SGSN service. This
number must be met or exceeded to maintain a previously generated
alarm condition. If the number of subscribers falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 through 2000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the number of 3G-attached subscribers for any one SGSN
service in the system is equal to or greater than the set limit.
Alerts or alarms are
triggered for PDP contexts based on the following rules:
- Enter condition: Actual
number of 3G-attached subscribers for any single SGSN service is
greater than or equal to the high threshold.
- Clear condition: Actual
number of 3G-attached subscribers for any single SGSN service is
less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold count of
10000 3G-attached
subscribers per SGSN service for a system using the Alert thresholding
model:
threshold per-service-sgsn-sessions 10000
threshold phsgw-auth-failure
Configures alarm or
alert thresholds for the number of authentication failures in Personal
Handyphone Service Gateway (PHSGW) service.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgw-auth-failure high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number for PHSGW authentication failures in any
one PHSGW service. This number must be met or exceeded within the
polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of PHSGW authentication failures in any
one PHSGW service. This number must be met or exceeded to maintain
a previously generated alarm condition. If the number of subscribers
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW authentication
failures.
Alerts
or alarms are triggered for authentication failures based on the
following rules:
- Enter condition: Actual
number of PHSGW authentication failures in any one PHSGW service
is greater than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW authentication failures in any one PHSGW service
is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW au the tic a it on failures:
threshold phsgw-auth-failure
100000 clear 50000
threshold phsgw-eapol-auth-failure
Configures alarm or
alert thresholds for authentication failures for a PHSGW service
using Extensible Authentication Protocol Over LAN (EAPOL).
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgw-eapol-auth-failure high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number for PHSGW EAPOL failures in any one PHSGW service.
This number must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of PHSGW EAPOL failures in any one PHSGW
service. This number must be met or exceeded to maintain a previously
generated alarm condition. If the number of subscribers falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW EAPOL failures.
Alerts
or alarms are triggered for EAPOL failures based on the following
rules:
- Enter condition: Actual
number of PHSGW EAPOL failures in any one PHSGW service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW EAPOL failures in any one PHSGW service is less
than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW EAPOL failures:
threshold phsgw-eapol-auth-failure
100000 clear 50000
threshold phsgw-handoff-denial
Configures alarm or
alert thresholds for handoff denials in PHSGW.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgw-handoff-denial high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of handoff denials for any one PHSGW service.
This number must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of handoff denials for any one PHSGW service.
This number must be met or exceeded to maintain a previously generated
alarm condition. If the number of subscribers falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW handoff denials.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSGW handoff denials in any one PHSGW service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW handoff denials in any one PHSGW service is less
than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW handoff denials:
threshold phsgw-handoff-denial
100000 clear 50000
threshold phsgw-max-eap-retry
Configures alarm or
alert thresholds for the maximum number of Extensible Authentication
Protocol (EAP) retries in PHSGW.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgww-max-eap-retry high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of EAP retries for any one PHSGW service.
This number must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of EAP retries for any one PHSGW service.
This number must be met or exceeded to maintain a previously generated
alarm condition. If the number of subscribers falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW EAP retries.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSGW EAP retries in any one PHSGW service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW EAP retries in any one PHSGW service is less than
the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW EAP retries:
threshold phsgw-max-eap-retry
100000 clear 50000
threshold phsgw-max-eapol-retry
Configures alarm or
alert thresholds for the maximum number of Extensible Authentication
Protocol over LAN (EAPOL) retries in PHSGW.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgww-max-eapol-retry high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of EAPOL retries for any one PHSGW service.
This number must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of EAPOL retries for any one PHSGW service.
This number must be met or exceeded to maintain a previously generated
alarm condition. If the number of subscribers falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW EAPOL retries.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSGW EAPOL retries in any one PHSGW service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW EAPOL retries in any one PHSGW service is less than
the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW EAPOL retries:
threshold phsgw-max-eapol-retry
100000 clear 50000
threshold phsgw-network-entry-denial
Configures, alarm or
alert thresholds for the number of network entry denials in PHSGW.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgww-max-network-entry-denial high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of network entry denials for any one PHSGW
service. This number must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of network entry denials for any one PHSGW
service. This number must be met or exceeded to maintain a previously
generated alarm condition. If the number of subscribers falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW network entry denials.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSGW network entry denials in any one PHSGW service is
greater than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW network entry denials in any one PHSGW service is
less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW network entry denials:
threshold phsgw-network-entry-denial
100000 clear 50000
threshold phsgw-session-setup-timeout
Configures alarm or
alert thresholds for the number of PHSGW sessions that timed out
during setup.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgww-session-setup-timeout high_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of session setup timeouts for any one
PHSGW service. This number must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of session setup timeouts for any one PHSGW
service. This number must be met or exceeded to maintain a previously
generated alarm condition. If the number of subscribers falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW session setup timeouts.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSGW session setup timeouts in any one PHSGW service
is greater than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW session setup timeouts in any one PHSGW service
is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW session setup timeouts:
threshold phsgw-session-setup-timeout
100000 clear 50000
threshold phsgw-session-timeout
Configures alarm or
alert thresholds for the number of PHSGW sessions that timed out.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phsgww-session-timeouthigh_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of session timeouts for any one PHSGW
service. This number must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of session timeouts for any one PHSGW service.
This number must be met or exceeded to maintain a previously generated
alarm condition. If the number of subscribers falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSGW session timeouts.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSGW session timeouts in any one PHSGW service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of PHSGW session timeouts in any one PHSGW service is less
than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSGW session timeouts:
threshold phsgw-session-timeout
100000 clear 50000
threshold phspc-session-setup-timeout
Configures alarm or
alert thresholds for the number of Personal Handyphone System -
Personal Computer (PHSPC) sessions that timed out during setup.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phspc-session-setup-timeouthigh_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of session setup timeouts for any one
PHSPC service. This number must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of session setup timeouts for any one PHSPC
service. This number must be met or exceeded to maintain a previously
generated alarm condition. If the number of subscribers falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSPC session setup timeouts.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSPC session setup timeouts in any one PHSGW service
is greater than or equal to the high threshold.
- Clear condition: Actual
number of PHSPC session setup timeouts in any one PHSGW service
is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSPC session setup timeouts:
threshold phspc-session-setup-timeout
100000 clear 50000
threshold phspc-sleep-mode-timeout
Configures alarm or
alert thresholds for the number of PHSPC sessions that timed out
when the personal computer went into sleep mode.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phspc-sleep-mode-timeouthigh_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of sleep mode timeouts for any one PHSPC
service. This number must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of sleep mode timeouts for any one PHSPC
service. This number must be met or exceeded to maintain a previously
generated alarm condition. If the number of subscribers falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSPC sleep mode timeouts.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSPC sleep mode timeouts in any one PHSGW service is
greater than or equal to the high threshold.
- Clear condition: Actual
number of PHSPC sleep mode timeouts in any one PHSGW service is
less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSPC sleep mode timeouts:
threshold phspc-sleep-mode-timeout
100000 clear 50000
threshold phspc-sm-entry-denial
Configures alarm or
alert thresholds for the number of denied PHSPC short message (SM)
sessions.
Privilege:
Security
Administrator, Administrator
Syntax
threshold phspc-sm-entry-denialhigh_thresh [ clear low_thresh ]
high_thresh
Default:
0
Specifies
the high threshold number of SM entry denials for any one PHSPC
service. This number must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0
Specifies
the low threshold number of SM entry denials for any one PHSPC service.
This number must be met or exceeded to maintain a previously generated
alarm condition. If the number of subscribers falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Set
the monitoring and clearing thresholds for PHSPC SM entry denials.
Alerts
or alarms are triggered for handoff denials based on the following
rules:
- Enter condition: Actual
number of PHSPC SM entry denials in any one PHSPC service is greater
than or equal to the high threshold.
- Clear condition: Actual
number of PHSPC SM entry denials in any one PHSPC service is less
than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The
following command configures a monitoring threshold of
100000 and
a clearing threshold of
50000 for
PHSPC SM entry denials:
threshold phsgw-sm-entry-denial
100000 clear 50000
threshold poll
10sec-cpu-utilization interval
Configures the polling
interval over which to measure a 10-second average of CPU utilization.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll 10sec-cpu-utilization duration
default threshold
poll 10sec-cpu-utilization
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCPUUtilization10Sec command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the 10-second CPU utilization threshold:
threshold poll 10sec-cpu-utilization 600
threshold poll
a11-ppp-send-discard interval
Configures the polling
interval for PDSN service over which to count the number of packets
that the PPP protocol processing layer internally discarded on transmit
for any reason.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll a11-ppp-send-discard intervalduration
default threshold poll
a11-ppp-send-discard interval
default
Restores
the specified parameter to its default value 0 seconds.
interval duration
Default:
0 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 900 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDSNSvcA11PPPSendDiscard command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the A11 PPP send discard threshold:
threshold poll a11-ppp-send-discard
interval 600
threshold poll
a11-rac-msg-discard interval
Configures the polling
interval for PDSN service over which to count the number of Discarded
A11 Registration Acknowledgements.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll a11-rac-msg-discard intervalduration
default threshold poll
a11-rac-msg-discard interval
default
Restores
the specified parameter to its default value 0 seconds.
interval duration
Default:
0 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 900 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDSNSvcA11RACMsgDiscard command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the A11 RAC message discard threshold:
threshold poll a11-rac-msg-discard
interval 600
threshold poll
aa11-rrp-failure interval
Configures the polling
interval for PDSN service over which to count A11 Registration Response
failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll a11-rrp-failure
interval duration
default threshold poll
a11-rrp-failure interval
default
Restores
the specified parameter to its default value 0 seconds.
interval duration
Default:
0 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 900 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDSNSvcA11RRPFailure command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the A11 RRP failure threshold:
threshold poll a11-rrp-failure
interval 600
threshold poll
a11-rrq-msg-discard interval
Configures the polling
interval for PDSN service over which to count how many A11 Registration
Request messages are discarded.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll a11-rrq-msg-discard intervalduration
default threshold poll
a11-rrq-msg-discard interval
default
Restores
the specified parameter to its default value 0 seconds.
interval duration
Default:
0 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 900 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDSNSvcA11RRQMsgDiscard command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the A11 RRQ message discard threshold:
threshold poll a11-rrq-msg-discard
interval 600
threshold poll
aaa-acct-archive-size interval
Configures the polling
interval over which to count archived AAA accounting messages.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll aaa-acct-archive-size
interval duration
default threshold
poll aaa-acct-archive-size interval
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
Example:
The
following command configures the polling interval to
600 seconds
for the AAA accounting archive size threshold:
threshold poll aaa-acct-archive-size
interval 600
threshold poll
aaa-acct-failure interval
Configures the polling
interval over which to count failed AAA accounting requests.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll aaa-acct-failure
interval duration
default threshold
poll aaa-acct-failure interval
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshAAAAcctFail command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the AAA accounting failure threshold:
threshold poll aaa-acct-failure
interval 600
threshold poll
aaa-acct-failure-rate interval
Configures the polling
interval over which to measure the percentage of AAA accounting
failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll aaa-acct-failure-rate
interval duration
default threshold
poll aaa-acct-failure-rate interval
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshAAAAcctFailRate command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the AAA accounting failure rate threshold:
threshold poll aaa-acct-failure-rate
interval 600
threshold poll
aaa-auth-failure interval
Configures the polling
interval over which to count failed authentication requests.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll aaa-auth-failure
interval duration
default threshold
poll aaa-auth-failure interval
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshAAAAuthFail command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the AAA authentication failure threshold:
threshold poll aaa-auth-failure
interval 600
threshold poll
aaa-auth-failure-rate interval
Configures the polling
interval over which to measure the percentage of AAA authentication
failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll aaa-auth-failure-rate
interval duration
default threshold
poll aaa-auth-failure-rate interval
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshAAAAuthFailRate command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the AAA authentication failure rate threshold:
threshold poll aaa-auth-failure-rate
interval 600
threshold poll
aaa-retry-rate interval
Configures the polling
interval over which to measure the percent of AAA request message
retries.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll aaa-retry-rate
interval duration
default threshold
poll aaa-retry-rate interval
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshAAARetryRate command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the AAA retry rate threshold:
threshold poll aaa-retry-rate
interval 600
threshold poll
aaamgr-request-queue interval
Configures the polling
interval over which to count the number of AAA Manager Requests
for each AAA manager process.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll aaamgr-request-queue
interval duration
default threshold
poll aaamgr-request-queue interval
default
Restores
the specified parameter to its default value 0 seconds.
interval duration
Default:
0 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshAAAMgrQueue command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the AAA manager request queue threshold:
threshold poll aaamgr-request-queue
interval 600
threshold poll
active-subscriber interval
Configures the polling
interval over which to count the total number of active subscriber
sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll active-subscriber intervalduration
default threshold
poll active-subscriber interval
default
Restores
the specified parameter to its default value 300 seconds.
interval duration
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration is
an integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshSubscriberActive command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the active subscriber threshold:
threshold poll active-subscriber
interval 600
threshold poll asngw-auth-failure
interval
Configures the polling
interval over which to count or measure the thresholding value for
ASN Gateway authentication failure.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll asngw-auth-failure
interval dur
default threshold poll
asngw-auth-failure interval
default
Restores
the specified parameter to its default value 300 seconds.
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNGWAuthFail command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the ASN Gateway authentication failure threshold:
threshold poll asngw-auth-failure
interval 600
threshold poll asngw-handoff-denial interval
Configures the polling
interval over which to count or measure the thresholding value for
ASN Gateway hand-off denial.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll asngw-handoff-denial
interval dur
default threshold poll
asngw-handoff-denial interval
default
Restores the specified
parameter to its default value 300 seconds.
interval dur
Default: 300 seconds.
Specifies the polling
interval time in seconds.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNGWHandoffDenial command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the hand-off denial threshold:
threshold poll asngw-handoff-denial
interval 600
threshold poll asngw-max-eap-retry interval
Configures the polling
interval over which to count or measure the thresholding value for
maximum Extensible Authentication Protocol (EAP) authentication retries.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll asngw-max-eap-retry
interval dur
default threshold poll
asngw-max-eap-retry interval
default
Restores the specified
parameter to its default value 300 seconds.
interval dur
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNGWMaxEAPRetry command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the maximum EAP authentication retry threshold:
threshold poll asngw-max-eap-retry
interval 600
threshold poll asngw-network-entry-denial interval
Configures the polling
interval over which to count or measure the thresholding value for
network entry denial to an MS.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll asngw-network-entry-denial interval dur
default threshold poll
asngw-network-entry-denial interval
default
Restores the specified
parameter to its default value 300 seconds.
interval dur
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNGWNWEntryDenial command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the network entry denial threshold:
threshold poll asngw-network-entry-denial interval
600
threshold poll asngw-session-setup-timeout interval
Configures the polling
interval over which to count or measure the thresholding value for
session setup timeout.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll asngw-session-setup-timeout interval dur
default threshold poll
asngw-session-setup-timeout interval
default
Restores the specified
parameter to its default value 300 seconds.
interval dur
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNGWSessSetupTimeout command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the session setup timeout threshold:
threshold poll asngw-session-setup-timeout interval
600
threshold poll asngw-session-timeout interval
Configures the polling
interval over which to count or measure the thresholding value for
session timeout.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll asngw-session-timeout
interval dur
default threshold poll
asngw-session-timeout interval
default
Restores the specified
parameter to its default value (300 seconds).
interval dur
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNGWSessTimeout command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the session timeout threshold:
threshold poll asngw-session-timeout
interval 600
threshold poll asnpc-idle-mode-timeout interval
Configures the polling
interval over which to count the number of ASNPC Instant Messenger
idle mode timeouts.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll asnpc-idle-mode-timeout
interval dur
default threshold poll
asnpc-idle-mode-timeout interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNPCIdleModeTimeout command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the idle mode timeout threshold:
threshold poll asnpc-idle-mode-timeout
interval 600
threshold poll asnpc-im-entry-denial interval
Configures the polling
interval over which to count the number of ASNPC Instant Messenger
entry denials.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll asnpc-im-entry-denial
interval dur
default threshold poll
asnpc-im-entry-denial interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNPCImEntryDenial command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the IM entry denial threshold:
threshold poll asnpc-im-entry-denial
interval 600
threshold poll asnpc-lu-denial
interval
Configures the polling
interval over which to count the number of ASNPC Location Update
(LU) denials.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll asnpc-lu-denial
interval dur
default threshold poll
asnpc-lu-denial interval interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNPCLuDenial command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the LU denial threshold:
threshold poll asnpc-lu-denial
interval 600
threshold poll asnpc-session-setup-timeout interval
Configures the polling
interval over which to count the number of times an ASNPC session
timed out before setup completion.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll asnpc-session-setup-timeout intervaldur
default threshold poll
asnpc-session-setup-timeout interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNPCSessSetupTimeout command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the session setup timeout threshold:
threshold poll asnpc-session-setup-timeout interval
600
threshold poll available-ip-pool-group interval
Configures the polling
interval over which to measure IP pool utilization.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll available-ip-pool-group
interval dur
default threshold poll
available-ip-pool-group interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPPoolAvail command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for available IP pool threshold:
threshold poll available-ip-pool-group
interval 600
threshold poll call-reject-no-resource interval
Configures the polling
interval over which to measure IP pool utilization.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll call-reject-no-resource intervaldur
default threshold poll
call-reject-no-resource interval
default
Restores
the specified parameter to its default value (900 seconds).
interval dur
Default:
900 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCallRejectNoResource command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for call reject no-resource threshold:
threshold poll call-reject-no-resource
interval 600
threshold poll call-setup
interval
Configures the polling
interval over which to count the number of calls that were setup.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll call-setup intervaldur
default threshold poll
call-setup interval
default
Restores
the specified parameter to its default value (900 seconds).
interval dur
Default:
900 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCallSetup command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the call setup threshold:
threshold poll call-setup
interval 600
threshold poll call-setup-failure
interval
Configures the polling
interval over which to count the number of calls that failed to
setup.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll call-setup-failure intervaldur
default threshold poll
call-setup-failure interval
default
Restores
the specified parameter to its default value (900 seconds).
interval dur
Default:
900 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 30 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCallSetupFailure command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for call setup failure threshold:
threshold poll call-setup-failure
interval 600
threshold poll call-setup-failures
interval
Configures the polling
interval over which to count the number of CSCF call setup failures.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll call-setup-failures intervaldur
default threshold poll
call-setup-failures interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcTotalCallFailure command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for CSCF session timeout threshold:
threshold poll call-setup-failures
interval 600
threshold poll call-total-active
interval
Configures the polling
interval over which to count the total number of CSCF active calls.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll call-total-active intervaldur
default threshold poll
call-total-active interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcTotalActiveCalls command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for session timeout threshold:
threshold poll call-total-active
interval 600
threshold poll card-temperature-near-power-off-limit
interval
Configures the polling
interval over which to count the number of times card temperatures
reached the power-off limit.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll card-temperature-near-power-off-limit
intervaldur
default threshold poll
card-temperature-near-power-off-limit interval
default
Restores
the specified parameter to its default value (300 seconds).
interval dur
Default:
300 seconds.
Specifies
the amount of time (in seconds) that comprises the polling interval.
dur is an
integer from 60 through 60000 in multiples of 30.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCardTemperatureNearPowerOffLimit command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for session timeout threshold:
threshold poll card-temperature-near-power-off-limit
interval 600
threshold poll cdr-file-space
interval
Configures the polling
interval for Charging Data Record (CDR) File Space Usage threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll cdr-file-space
interval duration
default threshold poll
cdr-file-space interval
default
Uses
the default polling interval.
Default: 300 seconds
interval duration
Specifies the polling
interval (in seconds) for the CDR File Space Usage threshold.
duration must
be an integer from 60 through 60000.
Usage:
This command configures
the polling interval for CDR File Space Usage threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCDRFileSpace command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the CDR file space usage threshold:
threshold poll cdr-file-space
interval 600
threshold poll contfilt-block
interval
Configures the polling
interval Content Filtering Block threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll contfilt-block
interval duration
default threshold poll
contfilt-block interval
default
Uses
the default threshold polling interval.
Default: 300 seconds
interval duration
Specifies the polling
interval (in seconds) for the Content Filtering Block threshold.
duration must
be an integer from 60 through 60000.
Usage:
This command configures
the polling interval Content Filtering Block threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshContFiltBlock command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the content filtering blocking threshold:
threshold poll contfilt-block
interval 600
threshold poll contfilt-rating
interval
Configures the polling
interval for the Content Filtering Rating threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll contfilt-rating
interval duration
default threshold poll
contfilt-rating interval
default
Uses the default threshold
polling interval.
Default:
300 seconds
interval dur
Specifies the polling
interval (in seconds) for the Content Filtering Rating threshold.
duration must
be an integer from 60 through 60000.
Usage:
This command configures
the polling interval for the Content Filtering Rating threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshContFiltRating command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the content filtering rating processing threshold:
threshold poll contfilt-rating
interval 600
threshold poll cpu-available-memory interval
Configures the polling
interval over which to measure the percentage of total packet processing
card CPU memory used.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cpu-available-memory intervalduration
default threshold poll
cpu-available-memory interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCPUMemory command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CPU available memory threshold:
threshold poll cpu-available-memory
interval 600
threshold poll cpu-load
interval
Configures the polling
interval over which to monitor packet processing card CPU loads
using a 5-minute average measurement.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cpu-load intervalduration
default threshold poll
cpu-load interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCPULoad command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CPU load threshold:
threshold poll cpu-load
interval 600
threshold poll cpu-memory-usage
interval
Configures the polling
interval over which to measure the percentage of total packet processing
card CPU memory used.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cpu-memory-usage
interval duration
default threshold poll
cpu-memory-usage interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCPUMemUsage command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CPU memory usage threshold:
threshold poll cpu-memory-usage
interval 600
threshold poll cpu-orbs-crit
interval
Configures the polling
interval over which to measure the percentage of CPU utilization
by the ORBS software task for critical-level alerts.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cpu-orbs-crit
interval duration
default threshold poll
cpu-orbs-crit interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCPUOrbsCritical command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CPU ORBS critical threshold:
threshold poll cpu-orbs-crit
interval 600
threshold poll cpu-orbs-warn
interval
Configures the polling
interval over which to measure the percentage of CPU utilization
by the ORBS software task for warning-level alerts.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cpu-orbs-warn
interval duration
default threshold poll
cpu-orbs-warn interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCPUOrbsWarn command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CPU ORBS warning threshold:
threshold poll cpu-orbs-warn
interval 600
threshold poll cpu-session-throughput interval
Configures the polling
interval over which to measure total throughput for all Session
Manager tasks running on each packet processing card CPU.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cpu-session-throughput
interval duration
default threshold poll
cpu-session-throughput interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshSessCPUThroughput command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CPU session throughput threshold:
threshold poll cpu-session-throughput
interval 600
threshold poll cpu-utilization
interval
Configures the polling
interval over which to measure the percentage of CPU utilization.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cpu-utilization
interval duration
default threshold poll
cpu-utilization interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCPUUtilization command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CPU utilization threshold:
threshold poll cpu-utilization
interval 600
threshold poll cscf-invite-rcvd
interval
Configures the polling
interval in seconds over which to count the invitations received
for Call State Control Function (CSCF) calls.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cscf-invite-rcvd
interval duration
default threshold poll
cscf-invite-rcvd interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcCallsPerInterval command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CSCF call invite threshold:
threshold poll cscf-invite-rcvd
interval 600
threshold poll cscf-reg-rcvd
interval
Configures the polling
interval in seconds over which to count the registrations received
for Call State Control Function (CSCF) calls.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cscf-reg-rcvd
interval duration
default threshold poll
cscf-reg-rcvd interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcRegPerInterval command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CSCF call registrations threshold:
threshold poll cscf-reg-rcvd
interval 600
threshold poll cscf-service-route-failures interval
Configures the polling
interval in seconds over which to count the CSCF service route failures.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll cscf-service-route-failures interval duration
default threshold poll
cscf-service-route-failures interval
default
Uses
the default threshold polling interval.
Default:
300 seconds
interval dur
Specifies
the amount of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
monitoring and other threshold commands for additional
information on the system’s support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcRouteFailures command
in this mode.
Example:
The
following command configures the polling interval to
600 seconds
for the CSCF service route failures threshold:
threshold poll cscf-service-route-failures interval
600
threshold poll dcca-bad-answers
interval
Configures the polling
interval for DCCA Bad Answers threshold—invalid or bad
response to the system from the Diameter server.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll dcca-bad-answers
interval duration
default threshold poll
dcca-bad-answers interval
default
Uses the default threshold
polling interval.
Default: 900 seconds
interval duration
Specifies the polling
interval (in seconds) for the DCCA Bad Answers threshold.
duration must
be an integer from 60 through 60000.
Usage:
This command configures
the poling interval for DCCA Bad Answers threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholding in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshDCCABadAnswers command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for invalid or bad response threshold to the system from Diameter
server:
threshold poll dcca-rating-failed
interval 600
threshold poll dcca-protocol-error
interval
Configures the polling
interval for Diameter Credit-Control Application (DCCA) Protocol
Error threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll dcca-protocol-error
interval duration
default threshold poll
dcca-protocol-error interval
default
Uses the default threshold
polling interval.
Default: 900 seconds
interval duration
Specifies the polling
interval (in seconds) for the DCCA Protocol Error threshold.
duration must
be an integer from 60 through 60000.
Usage:
Use this the polling
interval for DCCA Protocol Error threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholding in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshDCCAProtocolError command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the DCCA protocol error threshold:
threshold poll dcca-protocol-error
interval 600
threshold poll dcca-rating-failed
interval
Configures the polling
interval for Diameter Credit-Control Application (DCCA) Rating Failed
threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll dcca-rating-failed
interval duration
default threshold poll
dcca-rating-failed interval
default
Uses the default polling
interval.
Default: 900 seconds
interval duration
Specifies the polling
interval (in seconds) for the DCCA Rating Failed threshold.
duration must
be an integer from 60 through 60000.
Usage:
This command configures
the polling interval for DCCA Rating Failed threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholding in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshDCCARatingFailed command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the Diameter Credit Control Application (DCCA) Rating Group
(content-id) request reject thresholds:
threshold poll dcca-rating-failed
interval 600
threshold poll dcca-unknown-rating-group interval
Configures the polling
interval for Diameter Credit-Control Application (DCCA) Unknown
Rating Group threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll dcca-unknown-rating-group interval duration
default threshold poll
dcca-unknown-rating-group interval
default
Uses the default polling
interval.
Default: 900 seconds
interval duration
Specifies the polling
interval (in seconds) for the DCCA Unknown Rating Group threshold.
duration must
be an integer from 60 through 60000.
Usage:
This command configures
the polling interval for DCCA Unknown Rating Group threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholding in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshDCCAUnknownRatingGroup command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
to threshold for the unknown DCCA Rating Group (content-id) returned
by Diameter to system:
threshold poll dcca-unknown-rating-group interval
600
threshold poll dereg-reply-error
interval
Configures the polling
interval to count the number of de-registration reply errors per
HA service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll dereg-reply-error
interval duration
default threshold poll
dereg-reply-error interval
default
Uses the default polling
interval.
Default: 300 seconds
interval duration
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000. The input will be rounded up
to the closest multiple of 30.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands in this chapter for additional information
on the system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshHASvcDeregReplyError command
in this mode.
Example:
The following command
configures the HA de-registration reply error threshold polling interval
to
600 seconds:
threshold poll dereg-reply-error
interval 600
threshold poll diameter-retry-rate
interval
Configures the polling
interval for the Diameter Credit-Control Application (DCCA) Diameter
Retry Rate threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll diameter-retry-rate
interval duration
default threshold poll
diameter-retry-rate interval
default
Uses the default polling
interval.
Default: 300 seconds
interval duration
Specifies the polling
interval (in seconds) for the Diameter Retry Rate threshold.
duration must
be an integer from 60 through 60000. The input will be rounded up
to the closest multiple of 30.
Usage:
This command specifies
the polling interval for Diameter Retry Rate threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands in this chapter for additional information
on the system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshDiameterRetryRate command
in this mode.
Example:
The following command
configures the Diameter Retry Rate threshold polling interval to
600 seconds:
threshold poll diameter-retry-rate
interval 600
threshold poll edr-file-space
interval
Command configures
the polling interval for Event Data Record (EDR) File Space Usage
threshold.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll edr-file-space
interval duration
interval duration
Default: 300 seconds.
Specifies the polling
interval (in seconds) for the EDR File Space Usage threshold.
duration must
be an integer from 60 through 60000.
Usage:
This command configures
the polling interval for EDR File Space Usage threshold.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshEDRFileSpace command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the EDR file space usage threshold:
threshold poll edr-file-space
interval 600
threshold poll edr-udr-dropped-flow-control interval
Configures the polling
interval to count the total number of Event Data Records (EDRs)
and Usage Data Records (UDRs) discarded due to ACSMGR flow control.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll edr-udr-dropped-flow-control interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
Example:
The following command
configures the polling interval to
600 seconds
for the EDR/UDR drops due to flow control threshold:
threshold poll edr-udr-dropped-flow-control interval
600
threshold poll epdg-current-sessions interval
Configures the polling
interval to count the total number of subscribers currently in Evolved
Packet Date Gateway (ePDG) sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll epdg-current-sessions
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshEPDGCurrSess command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the ePDG sessions threshold:
threshold poll epdg-current-sessions
interval 600
threshold poll error-no-resource
interval
Configures the polling
interval in seconds over which to count CSCF No Resource Errors.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll error-no-resource
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcErrorNoResource command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the CSCF No Resource Errors threshold:
threshold poll error-no-resource
interval 600
threshold poll error-presence
interval
Configures the polling
interval in seconds over which to count CSCF Presence Errors.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll error-presence
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcErrorPresence command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the CSCF Presence Errors threshold:
threshold poll error-presence
interval 600
threshold poll error-reg-auth
interval
Configures the polling
interval in seconds over which to count CSCF Reg-Auth Errors.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll error-reg-auth
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcErrorRegAuth command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the CSCF Reg-Auth Errors threshold:
threshold poll error-reg-auth
interval 600
threshold poll error-tcp
interval
Configures the polling
interval in seconds over which to count CSCF TCP Errors.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll error-tcp
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcErrorTcp command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the CSCF TCP Errors threshold:
threshold poll error-tcp
interval 600
threshold poll fa-reg-reply-error
interval
Configures the polling
interval over which to measure the number of registration reply
errors for Foreign Agent (FA) services.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll fa-reg-reply-error
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshFASvcRegReplyError command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the FA registration reply errors threshold:
threshold poll fa-reg-reply-error
interval 600
threshold poll fng-current-active-sessions interval
Configures the polling
interval in seconds over which to count Femto Network Gateway (FNG)
current active sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll fng-current-active-sessions interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshFNGCurrActSess command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the FNG current active sessions threshold:
threshold poll fng-current-active-sessions interval
600
threshold poll fng-current-sessions interval
Configures the polling
interval in seconds over which to count Femto Network Gateway (FNG)
current sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll fng-current-sessions
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshFNGCurrSess command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the FNG current sessions threshold:
threshold poll fng-current-sessions
interval 600
threshold poll fw-deny-rule
interval
Configures the Stateful
Firewall Deny Rule threshold polling interval.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll fw-deny-rule
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 900.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshFWDenyRule command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the Stateful Firewall Deny Rule threshold:
threshold poll fw-deny-rule
interval 600
threshold poll fw-dos-attack
interval
Configures the Stateful
Firewall Denial of Service (DoS) Attacks threshold polling interval.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll fw-dos-attack
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 900.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshFWDosAttack command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the Stateful Firewall DoS Attacks threshold:
threshold poll fw-dos-attack
interval 600
threshold poll fw-drop-packet
interval
Configures the Stateful
Firewall Drop-Packet threshold polling interval.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll fw-drop-packet
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 900.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshFWDropPacket command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the Stateful Firewall Drop-Packet threshold:
threshold poll fw-drop-packet
interval 600
threshold poll fw-no-rule
interval
Configures the Stateful
Firewall No-Rule threshold polling interval.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll fw-no-rule
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 900.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshFWNoRule command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the Stateful Firewall No-Rule threshold:
threshold poll fw-no-rule
interval 600
threshold poll ha-init-rrq-rcvd-rate
interval
Configures the polling
interval for Home Agent (HA) service over which to measure the average
number of calls setup per minute.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ha-init-rrq-rcvd-rate
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 900.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshHACallSetupRate command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of HA calls setup per minute:
threshold poll ha-init-rrq-rcvd-rate
interval 600
threshold poll ha-svc-init-rrq-rcvd-rate interval
Configures the polling
interval over which to measure the average number of calls setup
per minute for HA services.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ha-svc-init-rrq-rcvd-rate interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 900.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshHASvcCallSetupRate command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of calls setup per minute for HA services:
threshold poll ha-svc-init-rrq-rcvd-rate interval
600
threshold poll ip-pool-free
interval
Configures the polling
interval over which to measure the percentage of the IP pool addresses
that are in the Free state.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ip-pool-free
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPPoolFree command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of Free IP pools:
threshold poll ip-pool-free
interval interval 600
threshold poll ip-pool-hold
interval
Configures the polling
interval over which to measure the percentage of the IP pool addresses
that are in the Hold state.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ip-pool-hold
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPPoolHold command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of IP pool addresses in Hold state:
threshold poll ip-pool-hold
interval 600
threshold poll ip-pool-release
interval
Configures the polling
interval over which to measure the percentage of IP pool addresses
that are in the Release state.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ip-pool-release
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPPoolRelease command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of IP pool addresses in Release state:
threshold poll ip-pool-release
interval 600
threshold poll ip-pool-used
interval
Configures the polling
interval over which to measure the percentage of the IP pool addresses
that are used.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ip-pool-used
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPPoolUsed command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of used IP pool addresses:
threshold poll ip-pool-used
interval 600
threshold poll ipsec-call-req-rej
interval
Configures the polling
interval over which to count the IPSec call requests that are rejected.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ipsec-call-req-rej
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPSECCallReqRej command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of rejected IPSec IKE calls:
threshold poll ipsec-call-req-rej
interval 600
threshold poll ipsec-ike-failrate
interval
Configures the polling
interval over which to count the IPSec IKE failure rate.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ipsec-ike-failrate
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPSECIKEFailRate command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average rate for IPSec IKE failures:
threshold poll ipsec-ike-failrate
interval 600
threshold poll ipsec-ike-failures
interval
Configures the polling
interval over which to count the number of IPSec IKE failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ipsec-ike-failures
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPSECIKEFailures command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of IPSec IKE failures:
threshold poll ipsec-ike-failures
interval 600
threshold poll ipsec-ike-requests
interval
Configures the polling
interval over which to count the number of IPSec IKE requests.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ipsec-ike-requests
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPSECIKERequests command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the average number of IPSec call requests:
threshold poll ipsec-ike-requests
interval 600
threshold poll ipsec-tunnels-established interval
Configures the polling
interval over which to count the number of IPSec tunnels that have
been established.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ipsec-tunnels-established interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPSECTunEstabl command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the number of established IPSec tunnels:
threshold poll ipsec-tunnels-established interval
600
threshold poll ipsec-tunnels-setup
interval
Configures the polling
interval over which to count the number of IPSec tunnels that have
been setup.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ipsec-tunnels-setup
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshIPSECTunSetup command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the number of IPSec tunnels that have been setup:
threshold poll ipsec-tunnels-setup
interval 600
threshold poll license-remaining-session interval
Configures the polling
interval over which to measure session license utilization.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll license-remaining-session interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshLicense command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for the utilization of session licenses:
threshold poll license-remaining-session interval
600
threshold poll mgmt-cpu-memory-usage interval
Configures the polling
interval over which to measure management card CPU memory usage.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll mgmt-cpu-memory-usage
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
Example:
The following command
configures the polling interval to
600 seconds
for management card CPU memory usage:
threshold poll mgmt-cpu-memory-usage
interval 600
threshold poll mgmt-cpu-utilization interval
Configures the polling
interval over which to measure management card CPU utilization.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll mgmt-cpu-utilization
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
Example:
The following command
configures the polling interval to
600 seconds
for management card CPU memory usage:
threshold poll mgmt-cpu-utilization
interval 600
threshold poll mme-attach-failure
interval
Configures the polling
interval to count the MME Attach Failure messages across all MME
services in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll mme-attach-failure
interval dur
default threshold poll
mme-attach-failure interval
default
Restores the polling
interval value to its default value of 900 seconds.
interval dur
Default: 900 seconds.
Specifies the polling
interval (in seconds) for counting MME Attach Failure messages across
all MME services in the system.
dur must
be an integer from 30 through 60000 in multiples of 30.
Usage:
Use this command to
configure the polling interval to count the MME Attach Failure messages
across all MME services in the system to generate threshold value.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring
mme-service and other threshold commands for additional
information on the system’s support for thresholds in this
chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshMMEAttachFail command
in this mode.
Example:
The following command
configures the polling interval of
600 seconds
to count the MME Attach Failure messages for threshold limit:
threshold poll mme-attach-failure
interval 600
threshold poll mme-auth-failure
interval
Configures the polling
interval to count the MME Authentication Failure messages across
all MME services in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll mme-auth-failure
interval dur
default threshold poll
mme-auth-failure interval
default
Restores the specified
poll interval value to its default value of 900 seconds.
interval dur
Default: 900 seconds.
Specifies the polling
interval (in seconds) for counting MME Authentication Failure messages
across all MME services in the system.
dur must
be an integer from 30 through 60000 in multiples of 30.
Usage:
Use this command to
configure the polling interval to count the MME Auth Failure messages
across all MME services in the system to generate threshold value.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring
mme-service and other threshold commands for additional
information on the system’s support for thresholds in this
chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshMMEAuthFail command
in this mode.
Example:
The following command
configures the polling interval of
600 seconds
to count the MME Auth Failure messages for threshold limit:
threshold poll mme-auth-failure
interval 600
threshold poll nat-port-chunks-usage interval
Configures the polling
interval over which to measure the percentage of Network Address
Translation (NAT) port chunk utilization.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll nat-port-chunks-usage
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshNATPortChunksUsage command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for (NAT) port chunk utilization:
threshold poll nat-port-chunks-usage
interval 600
threshold poll npu-utilization
interval
Configures the polling
interval over which to measure the percentage of network processing
unit (NPU) utilization.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll npu-utilization
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshNPUUtilization command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for NPU utilization:
threshold poll npu-utilization
interval 600
threshold poll packets-filtered-dropped interval
Configures the polling
interval over which to count the filtered/dropped packets.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll packets-filtered-dropped interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPacketsFilteredDropped command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for filtered/dropped packets:
threshold poll packets-filtered-dropped interval
600
threshold poll packets-forwarded-to-cpu interval
Configures the polling
interval over which to count packets forwarded to active system
CPUs in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll packets-forwarded-to-cpu interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPacketsForwarded command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for packets forwarded to active system CPUs in the system:
threshold poll packets-forwarded-to-cpu interval
600
threshold poll pdg-current-active-sessions interval
Configures the polling
interval over which to count the total number of currently active
Packet Data Gateway/Tunnel Termination Gateway (PDG/TTG)
sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll pdg-current-active-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDGCurrActSess command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDG/TTG sessions:
threshold poll pdg-current-active-sessions interval
600
threshold poll pdg-current-sessions interval
Configures the polling
interval over which to count the total number of current Packet
Data Gateway/Tunnel Termination Gateway (PDG/TTG)
sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll pdg-current-sessions
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDGCurrSess command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDG/TTG sessions:
threshold poll pdg-current-sessions
interval 600
threshold poll pdif-current-active-sessions interval
Configures the polling
interval over which to count the total number of currently active
Packet Data Interworking Function (PDIF) sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll pdif-current-active-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDIFCurrActSess command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDIF sessions:
threshold poll pdif-current-active-sessions interval
600
threshold poll pdif-current-sessions interval
Configures the polling
interval over which to count the total number of current Packet
Data Interworking Function (PDIF) sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll pdif-current-sessions
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDIFCurrSess command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDIF sessions:
threshold poll pdif-current-sessions
interval 600
threshold poll pdsn-init-rrq-rcvd-rate interval
Configures the polling
interval over which to count the total number of current Packet
Data Serving Node (PDSN) sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll pdsn-init-rrq-rcvd-rate
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 60 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDSNCallSetupRate command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDSN sessions:
threshold poll pdsn-init-rrq-rcvd-rate
interval 600
threshold poll pdsn-svc-init-rrq-rcvd-rate interval
Configures the polling
interval over which to count the total number of current Packet
Data Serving Node (PDSN) sessions, including inactive sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll pdsn-svc-init-rrq-rcvd-rate interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDSNSvcCallSetupRate command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDSN sessions:
threshold poll pdsn-svc-init-rrq-rcvd-rate interval
600
threshold poll per-service-asngw-sessions interval
Configures the polling
interval in seconds over which to count the number of PDP contexts
per ASN-GW service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-asngw-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceASNGWSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for ASN-GW sessions:
threshold poll per-service-asngw-sessions interval
600
threshold poll per-service-ggsn-sessions interval
Configures the polling
interval in seconds over which to count the number of PDP contexts
per GGSN service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-ggsn-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceGGSNSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for GGSN sessions:
threshold poll per-service-ggsn-sessions interval
600
threshold poll per-service-gprs-pdp-sessions interval
Configures the polling
interval in seconds over which to count the number of 2G-activated
PDP contexts per GPRS service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-gprs-pdp-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceGPRSPDPSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for 2G PDP contexts:
threshold poll per-service-gprs-pdp-sessions interval
600
threshold poll per-service-gprs-sessions interval
Configures the polling
interval in seconds over which to count the number of 2G-attached
subscribers per GPRS service.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-gprs-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceGPRSSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for 2G GPRS sessions:
threshold poll per-service-gprs-sessions interval
600
threshold poll per-service-ha-sessions interval
Configures the polling
interval in seconds over which to count the number of HA sessions
per Home Agent (HA) service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-ha-sessions
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceHASessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for HA sessions:
threshold poll per-service-ha-sessions
interval 600
threshold poll per-service-lns-sessions interval
Configures the polling
interval in seconds over which to count the number of L2TP Network
Server (LNS) sessions per LNS service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-lns-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceLNSSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for LNS sessions:
threshold poll per-service-lns-sessions interval
600
threshold poll per-service-pdg-sessions interval
Configures the polling
interval in seconds over which to count the number of Packet Data
Gateway (PDG) sessions per PDG/TTG service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-pdg-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServicePDGSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDG/TTG sessions:
threshold poll per-service-pdg-sessions interval
600
threshold poll per-service-pdsn-sessions interval
Configures the polling
interval in seconds over which to count the number of Packet Data
Serving Node (PDSN) sessions per PDSN service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-pdsn-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServicePDSNSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PDSN sessions:
threshold poll per-service-pdsn-sessions interval
600
threshold poll per-service-sgsn-pdp-sessions interval
Configures the polling
interval in seconds over which to count the number of 3G-activated
PDP contexts per SGSN service on the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-sgsn-pdp-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceSGSNPDPSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for 3G PDP contexts:
threshold poll per-service-sgsn-pdp-sessions interval
600
threshold poll per-service-sgsn-sessions interval
Configures the polling
interval in seconds over which to count the number of 3G-attached
subscribers per SGSN service in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll per-service-sgsn-sessions interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPerServiceSGSNSessions command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for SGSN sessions:
threshold poll per-service-sgsn-sessions interval
600
threshold poll phsgw-auth-failure
interval
Configures the polling
interval in seconds over which to count the number of Personal Handyphone
System Gateway (PHSGW) authentication failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-auth-failure
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWAuthFail command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW authentication failures:
threshold poll phsgw-auth-failure
interval 600
threshold poll phsgw-eapol-auth-failure interval
Configures the polling
interval in seconds over which to count the number of authentication
failures for a PHSGW service using Extensible Authentication Protocol
Over LAN (EAPOL).
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-eapol-auth-failure interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWEAPOLAuthFailure command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW EAPOL failures:
threshold poll phsgw-eapol-auth-failure interval
600
threshold poll phsgw-handoff-denial interval
Configures the polling
interval in seconds over which to count the number of handoff denials
in PHSGW.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-handoff-denial
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWMaxEAPOLRetry command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW handoff denials:
threshold poll phsgw-handoff-denial
interval 600
threshold poll phsgw-max-eap-retry interval
Configures the polling
interval in seconds over which to count the maximum number of Extensible
Authentication Protocol (EAP) retries in PHSGW.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-max-eap-retry
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWMaxEAPRetry command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW EAP retries:
threshold poll phsgw-max-eap-retry
interval 600
threshold poll phsgw-max-eapol-retry interval
Configures the polling
interval in seconds over which to count the maximum number of Extensible
Authentication Protocol Over LAN (EAPOL) retries in PHSGW.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-max-eapol-retry
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWMaxEAPOLRetry command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW EAPOL retries:
threshold poll phsgw-max-eapol-retry
interval 600
threshold poll phsgw-network-entry-denial interval
Configures the polling
interval in seconds over which to count the number of network entry
denials in PHSGW.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-network-entry-denial interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWNWEntryDenial command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW network entry denials:
threshold poll phsgw-network-entry-denial interval
600
threshold poll phsgw-session-setup-timeout interval
Configures the polling
interval in seconds over which to count the number of PHSGW sessions
that timed out during setup.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-session-setup-timeout interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWSessSetupTimeout command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW session setup timeouts:
threshold poll phsgw-session-setup-timeout interval
600
threshold poll phsgw-session-timeout interval
Configures the polling
interval in seconds over which to count the number of PHSGW sessions
that timed out.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phsgw-session-timeout
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSGWSessTimeout command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSGW session timeouts:
threshold poll phsgw-session-timeout
interval 600
threshold poll phspc-session-setup-timeout interval
Configures the polling
interval in seconds over which to count the number of Personal Handyphone
System - Personal Computer (PHSPC) sessions that timed out during setup.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phspc-session-setup-timeout interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSPCSessSetupTimeout command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSPC session setup timeouts:
threshold poll phspc-session-setup-timeout interval
600
threshold poll phspc-sleep-mode-timeout interval
Configures the polling
interval in seconds over which to count the number of PHSPC sessions
that timed out when the personal computer went into sleep mode.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phspc-sleep-mode-timeout interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSPCSleepModeTimeout command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSPC sleep mode timeouts:
threshold poll phspc-sleep-mode-timeout interval
600
threshold poll phspc-sm-entry-denial interval
Configures the polling
interval in seconds over which to count the number of denied PHSPC
short message (SM) sessions.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll phspc-sm-entry-denial
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPHSPCSmEntryDenial command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PHSPC SM session denials:
threshold poll phspc-sm-entry-denial
interval 600
threshold poll port-high-activity
interval
Configures the polling
interval in seconds over which to measure the overall percentage
of port utilization.
Privilege:
Administrator Security
Administrator
Syntax
threshold poll port-high-activity
interval seconds
interval seconds
Configures the threshold
polling interval in multiples of 30 seconds. seconds is
an integer from 30 through 60000. Default is 300 seconds.
Usage:
High port activity
thresholds generate alerts or alarms based on the peak utilization percentage
of each configured 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 is greater than or equal to the high
threshold.
Clear condition: Actual
percent peak utilization of a port is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.This threshold
is configured on a per-port basis configured using the port port-type slot#/port# command
syntax.
IMPORTANT:
This command is not
available on all platforms
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPortHighActivity command
in this mode.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPortHighActivity command
in this mode.
Example:
Use the following example
to configure the polling interval over which to measure for high port
activity to
300 seconds:
threshold poll port-high-activity
interval 300
threshold poll port-rx-utilization
interval
Configures the polling
interval in seconds over which to measure the overall percentage
of incoming traffic received over system ports.
Privilege:
Administrator Security
Administrator
Syntax
threshold poll port-rx-utilization
interval seconds
interval seconds
Configures the threshold
polling interval in multiples of 30 seconds. seconds is
an integer from 30 to 60000. Default is 300 seconds.
Usage:
Receive port utilization
thresholds generate alerts or alarms based on the utilization percentage
of each configured port in relation to data received during the
specified polling interval. This threshold is configured on a per-port
basis configured using the port port-type slot#/port# command syntax.
IMPORTANT:
This command is not
available on all platforms
IMPORTANT:
Ports configured for
half-duplex do not differentiate between data received and data transmitted.
(The transmitted and received percentages are combined.) Therefore,
to avoid redundant alarms, it is recommended that only the receive or transmit utilization
threshold be configured.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPortRxUtil command
in this mode.
Example:
Use the following example
to configure a threshold poll interval of
300 seconds
(5 minutes)
threshold poll port-rx-utilization
interval 300
threshold poll port-tx-utilization
Configures the polling
interval in seconds over which to measure the overall percentage
of outgoing traffic sent over system ports.
Privilege:
Administrator Security
Administrator
Syntax
threshold poll port-tx-utilization
interval seconds
interval seconds
Configures the threshold
polling interval in multiples of 30 seconds. seconds is
an integer from 30 through 60000. Default is 300 seconds.
Usage:
Transmit port utilization
thresholds generate alerts or alarms based on the utilization percentage
of each configured port in relation to data transmitted during the
specified polling interval. This threshold is configured on a per-port
basis configured using the port port-type slot#/port# command syntax.
IMPORTANT:
This command is not
available on all platforms
IMPORTANT:
Ports configured for
half-duplex do not differentiate between data received and data transmitted.
(The transmitted and received percentages are combined.) Therefore,
to avoid redundant alarms, it is recommended that only the receive or transmit utilization
threshold be configured.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPortTxUtil command
in this mode.
Example:
Use the following example
to configure a threshold poll interval of
300 seconds
(5 minutes)
threshold poll port-tx-utilization
interval 300
threshold poll ppp-setup-fail-rate
interval
Configures the polling
interval in seconds over which to measure for the percentage of
point-to-point protocol (PPP) setup failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll ppp-setup-fail-rate
interval duration
interval duration
Default: 900 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPPPSetupFailRate command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for PPP setup failures:
threshold poll ppp-setup-fail-rate
interval 600
threshold poll reg-reply-error
interval
Configures the polling
interval over which to measure number of registration reply errors
for Home Agent (HA) services.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll reg-reply-error
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshHASvcRegReplyError command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for HA registration errors:
threshold poll reg-reply-error
interval 600
threshold poll reg-total-active
interval
Configures the polling
interval over which to measure CSCF Total Active Registrations.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll reg-total-active
interval duration
interval duration
Default: 300 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshCSCFSvcTotalActiveReg command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for CSCF active registrations:
threshold poll reg-total-active
interval 600
threshold poll rereg-reply-error
interval
Configures the polling
interval over which to measure number of re-registration reply errors
for HA services.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll rereg-reply-error
interval duration
interval duration
Default: 0 seconds.
Specifies the amount
of time (in seconds) that comprises the polling interval.
duration must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold monitoring and
other threshold commands for additional information on the system’s
support for thresholds in this chapter.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshHASvcReregReplyError command
in this mode.
Example:
The following command
configures the polling interval to
600 seconds
for HA re-registration reply errors:
threshold poll rereg-reply-error
interval 600
threshold poll route-service
interval
Configures the polling
interval over which to count or measure the thresholding value for
BGP route services on the system.
Privilege:
Administrator Security
Administrator
Syntax
threshold poll route-service
interval dur
default threshold poll
route-service interval
default
Restores the threshold
poll interval value to its default value of 900 seconds.
interval time
Default: 900 seconds
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is any
integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold model and threshold monitoring commands
for additional information on the system’s support for
thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshBGPRoutes command
in this mode.
Example:
The following command
configures the polling interval for the total BGP routes threshold polling
duration value to
600 seconds
(10 minutes):
hreshold poll route-service
interval 600
threshold poll rp-setup-fail-rate
interval
Configures the polling
interval over which to measure the percentage of RAN PDSN (RP) setup
failures.
Privilege:
Administrator Security
Administrator
Syntax
threshold poll rp-setup-fail-rate
interval dur
default threshold poll
route-service interval
default
Restores the threshold
poll interval value to its default value of 900 seconds.
interval time
Default: 900 seconds
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is any
integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold model and threshold monitoring commands
for additional information on the system’s support for
thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshRPSetupFailRate command
in this mode.
Example:
The following command
configures the polling interval for the RP setup fail rate polling duration
value to
600 seconds
(10 minutes):
hreshold poll rp-setup-fail-rate
interval 600
threshold poll storage-utilization
interval
Configures the polling
interval over which to measure the percentage of management card
flash memory utilization.
Privilege:
Administrator Security
Administrator
Syntax
threshold poll storage-utilization
interval dur
default threshold poll
route-service interval
default
Restores the threshold
poll interval value to its default value of 900 seconds.
interval time
Default: 900 seconds
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is any
integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold model and threshold monitoring commands
for additional information on the system’s support for
thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshStorageUtilization command
in this mode.
Example:
The following command
configures the polling interval for flash memory utilization polling duration
value to
600 seconds
(10 minutes):
threshold poll storage-utilization
interval 600
threshold poll system-capacity
interval
Configures the polling
interval over which to measure the percentage of current system
capacity.
Privilege:
Administrator Security
Administrator
Syntax
threshold poll system-capacity
interval dur
default threshold poll
route-service interval
default
Restores the threshold
poll interval value to its default value of 900 seconds.
interval time
Default: 900 seconds
Specifies the amount
of time (in seconds) that comprises the polling interval.
dur is any
integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold model and threshold monitoring commands
for additional information on the system’s support for
thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshSystemCapacity command
in this mode.
Example:
The following command
configures the polling interval for flash memory utilization polling duration
value to
600 seconds
(10 minutes):
hreshold poll system-capacity
interval 600
threshold poll total-asngw-sessions interval
Configures the polling
interval over which to count or measure the thresholding value for
the total number of sessions across all the ASN-GW services on a
system to trigger an alert or alarm.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll total-asngw-sessions
interval time
default threshold poll
total-asngw-sessions interval
default
Restores the threshold
polling interval value to its default value of 300 seconds.
interval time
Default: 300 seconds
Specifies the amount
of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This command sets the
time period over which to monitor the specified value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer to the threshold model and threshold monitoring commands
for additional information on the system’s support for
thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshASNGWSessions command
in this mode.
Example:
The following command
configures the polling interval for counting the total number of ASN-GW
sessions across all the ASN-GW services on a system, to
600 seconds
(10 minutes):
threshold poll total-asngw-sessions
interval 600
threshold poll total-ggsn-sessions
interval
Configures the polling
interval over which to count or measure the thresholding value for
the total number of sessions across all the GGSN services on a system
to trigger an alert or alarm.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-ggsn-sessions
interval time
default threshold poll
total-ggsn-sessions interval
default
Restores
the threshold polling interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshGGSNSessions command
in this mode.
Example:
The
following command configures the polling interval for counting the
total number of GGSN sessions across all the GGSN services on a
system, to
600 seconds
(10 minutes):
threshold poll total-ggsn-sessions
interval 600
threshold poll total-gprs-pdp-sessions interval
Configures the polling
interval over which to count the total number of 2G-activated PDP
contexts per GPRS sessions on the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-gprs-pdp-sessions
interval time
default threshold poll
total-gprs-pdp-sessions interval
default
Restores
the threshold polling interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshGPRSPDPSessions command
in this mode.
Example:
The
following command configures the polling interval for counting the
total number of 2G-activated PDP contexts per GPRS sessions, to
600 seconds
(10 minutes):
threshold poll total-gprs-pdp-sessions
interval 600
threshold poll total-gprs-sessions
interval
Configures the polling
interval over which to count the total number of 2G-attached subscribers
on the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-gprs-sessions
interval time
default threshold poll
total-gprs-sessions interval
default
Restores
the threshold polling interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshGPRSSessions command
in this mode.
Example:
The
following command configures the polling interval for counting the
total number of 2G-attached subscribers, to
600 seconds
(10 minutes):
threshold poll total-gprs-sessions
interval 600
threshold poll total-ha-sessions
interval
Configures the polling
interval over which to count the total number of Home Agent (HA)
sessions on the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-ha-sessions
interval time
default threshold poll
total-ha-sessions interval
default
Restores
the threshold polling interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshHASessions command
in this mode.
Example:
The
following command configures the polling interval for counting the
total number of HA sessions on the system, to
600 seconds
(10 minutes):
threshold poll total-ha-sessions
interval 600
threshold poll total-hnbgw-hnb-sessions
Configures the polling
interval over which to count or measure the thresholding value for
the total number of IuH sessions between the HNB and HNB-GW to count
across all the HNB-GW services on a system to trigger an alert or
alarm.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-hnbgw-hnb-sessions interval time
default threshold poll
total-hnbgw-hnb-sessions interval
default
Restores
the threshold polling interval value to its default value of 900 seconds.
interval time
Default:
900 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable SNMP trap
for threshold monitoring of this threshold use snmp trap enable ThreshTotalHNBGWHnbSess command
in this mode.
Example:
The
following command configures the polling interval for counting the
total number of HNB sessions between HNB and HNB-GW across all the
HNB-GW services on a system, to
600 seconds
(10 minutes):
threshold poll total-hnbgw-hnb-sessions interval
600
threshold poll total-hnbgw-iu-sessions
Configures the polling
interval over which to count or measure the thresholding value for
the total number of subscriber sessions on HNB-GW service (over
Iu-CS/Iu-PS interface) to count across all the HNB-GW services
on a system to trigger alert or alarm.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-hnbgw-iu-sessions
interval time
default threshold poll
total-hnbgw-iu-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an value from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWIuSess command
in this mode.
Example:
The
following command configures the polling interval for counting the
total number of subscriber sessions across all the HNB-GW services
on a system, to
600 seconds
(10 minutes):
threshold poll total-hnbgw-iu-sessions
interval 600
threshold poll total-hnbgw-ue-sessions
Configures the polling
interval over which to count or measure the thresholding value for
the total number of UEs connected to HNB-GW service to count across
all the HNB-GW services on a system to trigger alert or alarm.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-hnbgw-ue-sessions
interval time
default threshold poll
total-hnbgw-ue-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWUeSess command
in this mode.
Example:
The
following command configures the polling interval for the total
number of UEs connected to an HNB-GW service across all the HNB-GW
services on a system, to
600 seconds
(10 minutes):
threshold poll total-hnbgw-ue-sessions
interval 600
threshold poll total-hsgw-sessions interval
Configures the polling
interval over which to count the total number of HRPD Serving Gateway
(HSGW) sessions across all services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-hsgw-sessions
interval time
default threshold poll
total-hsgw-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshHSGWSessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of HSGW sessions across all the HSGW services on a system,
to
600 seconds (10
minutes):
threshold poll total-hsgw-sessions
interval 600
threshold poll total-lma-sessions
interval
Configures the polling
interval over which to count the total number of Local Mobility
Anchor (LMA) sessions across all services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-lma-sessions
interval time
default threshold poll
total-lma-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshLMASessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of LMA sessions across all the LMA sessions on a system,
to
600 seconds
(10 minutes):
threshold poll total-lma-sessions
interval 600
threshold poll total-lns-sessions
interval
Configures the polling
interval over which to count the total number of L2TP Network Server
(LNS) sessions in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-lns-sessions
interval time
default threshold poll
total-lns-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshLNSSessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of LNS sessions across all the LNS sessions on a system,
to
600 seconds
(10 minutes):
threshold poll total-lns-sessions
interval 600
threshold poll total-mme-sessions
Configures the polling
interval over which to count or measure the thresholding value for
MME sessions on the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-mme-sessions
interval time
default threshold poll
total-mme-sessions interval
default
Restores
the threshold poll interval value to its default value of 900 seconds.
interval time
Default:
900 seconds
Specifies
the polling interval (in seconds) for counting the total number
of MME sessions on the system.
time must
be an ny integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshMMESessions command
in this mode.
Example:
The following command
configures the polling interval for the total MME session threshold polling
duration value to
600 seconds
(10 minutes):
threshold poll total-mme-sessions
interval 600
threshold poll total-pdsn-sessions
interval
Configures the polling
interval over which to count the total number of Packet Data Serving
Node (PDSN) sessions in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-pdsn-sessions
interval time
default threshold poll
total-pdsn-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPDSNSessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of PDSN sessions across all the PDSN sessions on a system,
to
600 seconds
(10 minutes):
threshold poll total-pdsn-sessions
interval 600
threshold poll total-pgw-sessions
interval
Configures the polling
interval over which to count the total number of Packet Data Network
Gateway (P-GW) sessions across all services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-pgw-sessions
interval time
default threshold poll
total-pgw-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshPGWSessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of P-GW sessions across all the P-GW sessions on a system,
to
600 seconds
(10 minutes):
threshold poll total-pgw-sessions
interval 600
threshold poll total-sgsn-pdp-sessions interval
Configures the polling
interval over which to count the total number of PDP contexts for
all Serving GPRS Support Node (SGSN) sessions in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-sgsn-pdp-sessions
interval time
default threshold poll
total-sgsn-pdp-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshSGSNPDPSessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of PDP contexts across all the SGSN sessions on a system,
to
600 seconds
(10 minutes):
threshold poll total-sgsn-pdp-sessions
interval 600
threshold poll total-sgsn-sessions
interval
Configures the polling
interval over which to count the total number of SGSN sessions in
the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-sgsn-sessions
interval time
default threshold poll
total-sgsn-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshSGSNSessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of SGSN sessions on a system, to
600 seconds
(10 minutes):
threshold poll total-sgsn-sessions
interval 600
threshold poll total-sgw-sessions
interval
Configures the polling
interval over which to count the total number of Serving Gateway
(S-GW) sessions across all services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-sgw-sessions
interval time
default threshold poll
total-sgw-sessions interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshSGWSessions command
in this mode.
Example:
The
following command configures the polling interval for the total
number of S-GW sessions on a system, to
600 seconds
(10 minutes):
threshold poll total-sgw-sessions
interval 600
threshold poll total-subscriber
interval
Configures the polling
interval over which to count the total number of subscriber sessions
across all services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold poll total-subscriber
interval time
default threshold poll
total-subscriber interval
default
Restores
the threshold poll interval value to its default value of 300 seconds.
interval time
Default:
300 seconds
Specifies
the amount of time (in seconds) that comprises the polling interval.
time must
be an integer from 30 through 60000.
Usage:
This
command sets the time period over which to monitor the specified
value for threshold crossing.
IMPORTANT:
All configured polling
intervals are rounded up to the closest multiple of 30. For example,
if a polling interval is configured for 130 seconds, the system
uses a polling interval of 150 seconds.
Refer
to the threshold
model and threshold
monitoring commands for additional information on the
system’s support for thresholding.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshSubscriberTotalcommand
in this mode.
Example:
The
following command configures the polling interval for the total
number of subscribers on a system, to
600 seconds
(10 minutes):
threshold poll total-subscriber
interval 600
threshold poll tpo-dns-failure
Configures the threshold
polling interval for monitoring Traffic Performance Optimization
(TPO) DNS resolution failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll tpo-dns-failure
interval interval
default threshold
poll tpo-dns-failure interval
default
Configures this command
with the default polling interval.
Default: 900 seconds
interval
Specifies the polling
interval (in seconds) for monitoring TPO DNS resolution failures.
interval must
be an integer from 30 through 60000. The system rounds up the value
to the closest multiple of 30.
Usage:
Use this command to
configure the threshold polling interval for monitoring TPO DNS resolution
failures.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTpoDnsFailure command
in this mode.
Example:
The following command
configures the polling interval for TPO DNS resolution failures threshold
to
600 seconds:
threshold poll tpo-dns-failure
interval 600
threshold poll tpo-low-compression-gain
Configures the threshold
polling interval for monitoring TPO low-compression-gain results.
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll tpo-low-compression-gain interval interval
default threshold
poll tpo-low-compression-gain interval
default
Configures this command
with the default polling interval.
Default: 900 seconds
interval
Specifies the polling
interval (in seconds) for monitoring TPO low-compression-gain results.
interval must
be an integer from 30 through 60000. The system rounds up the value
to the closest multiple of 30.
Usage:
Use this command to
configure the threshold polling interval for monitoring TPO low-compression-gain
results.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTpoLowCompressionGain command
in this mode.
Example:
The following command
configures the polling interval for TPO low-compression-gain results
threshold to
600 seconds:
threshold poll tpo-low-compression-gain interval
600
threshold poll tpo-rto-timeout
Configures the threshold
polling interval for monitoring TPO retransmission timeouts (RTOs).
Privilege:
Security Administrator,
Administrator
Syntax
threshold poll tpo-rto-timeout
interval interval
default threshold
poll tpo-rto-timeout interval
default
Configures this command
with the default polling interval.
Default: 900 seconds
interval
Specifies the polling
interval (in seconds) for monitoring TPO retransmission timeouts.
interval must
be an integer from 30 through 60000. The system rounds up the value
to the closest multiple of 30.
Usage:
Use this command to
configure the threshold polling interval for monitoring TPO retransmission
timeouts.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTpoRtoTimeout command
in this mode.
Example:
The following command
configures the polling interval for TPO retransmission timeouts threshold
to
600 seconds:
threshold poll tpo-rto-timeout
interval 600
threshold ppp-setup-fail-rate
Configures alarm or
alert thresholds for the percentage of point-to-point protocol (PPP)
setup failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold ppp-setup-fail-rate high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold rate percentage for PPP setup failures experienced by
the system that must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
rate percentage for PPP setup failures experienced by the system that
maintains a previously generated alarm condition. If the number
of setup failures falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
PPP setup failure rate
thresholds generate alerts or alarms based on the rate of call setup failures
experienced by the system during the specified polling interval.
The failure rate is the percentage of failures as determined by
number of PPP setup failures divided by the total number of PPP
sessions initiated.
Alerts or alarms are
triggered for PPP setup failure rates based on the following rules:
- Enter condition: Actual
number of call setup failures is greater than or equal to the high
threshold.
- Clear condition: Actual
number of call setup failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a PPP setup failure rate high percentage threshold of
50 percent
and a clear threshold of
45 percent:
threshold ppp-setup-fail-rate
50 clear 45
threshold route-service
bgp-routes
Configures alarm or
alert thresholds for the percentage of route services to BGP routes.
Privilege:
Security Administrator,
Administrator
Syntax
threshold route-service
bgp-routes high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold rate percentage for BGP routes on the system that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
rate percentage for BGP routes on the system that maintains a previously
generated alarm condition. If the number of setup failures falls
beneath the low threshold within the polling interval, a clear alarm
will be generated.
low_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
configure a threshold in percentage of maximum BGP routes allowed.
If the percentage of the number of BGP routes in a context (including
all VRFs) reaches high_thresh,
a notification is generated. Optionally, if the threshold subsystem
is configured in ‘alarm’ mode, a Threshold_Clear notification is
generated when the percentage of the number of BGP routes in a context
(including all VRFs) goes below low_thresh.
The maximum number of BGP routes is also sent by BGP task when getting
the statistics
Alerts or alarms are
triggered for BGP routes based on the following rules:
- Enter condition: Actual
number of call setup failures is greater than the high threshold.
- Clear condition: Actual
number of call setup failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures system for high threshold of
50 percent
and a clear threshold of
45 percent:
threshold route-service
bgp-routes 50 clear 45
threshold rp-setup-fail-rate
Configures alarm or
alert thresholds for the percentage of RAN PDSN (RP) setup failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold rp-setup-fail-rate high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold rate percentage for RP setup failures experienced by the
system that must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
rate percentage for RP setup failures experienced by the system that
maintains a previously generated alarm condition. If the number
of setup failures falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
RP setup failure rate
thresholds generate alerts or alarms based on the rate of call setup failures
experienced by the system during the specified polling interval.
The failure rate is the percentage of failures as determined by
number of Registration Request Messages rejected divided by the
total number of Registration Request Messages received.
Alerts or alarms are
triggered for RP setup failure rates based on the following rules:
- Enter condition: Actual
number of call setup failures is greater than or equal to the high
threshold.
- Clear condition: Actual
number of call setup failures is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a RP setup failure rate high threshold of
50 percent
and a clear threshold of
45 percent:
threshold rp-setup-fail-rate
50 clear 45
threshold spc-cpu-memory-usage
This command has been
renamed to threshold
mgmt-cpu-memory-usage. Please refer to that command for
details. Note that for backwards compatibility, the system accepts
this command as valid.
IMPORTANT:
This command is not
supported on all platforms.
threshold spc-cpu-utilization
This command has been
renamed to threshold mgmt-cpu-utilization.
Please refer to that command for details. Note that for backwards
compatibility, the system accepts this command as valid.
threshold storage-utilization
Configures alarm or
alert thresholds for the percentage of management card flash memory
utilization.
Privilege:
Security Administrator,
Administrator
Syntax
threshold storage-utilization high_thresh [ clear low_thresh ]
high_thresh
Default: 90
Specifies the high
threshold storage utilization percentage that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 90
Specifies the low threshold
storage utilization percentage that maintains a previously generated
alarm condition. If the number of sessions falls beneath the low
threshold within the polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Flash memory utilization
thresholds generate alerts or alarms based on the utilization percentage
of storage available to the system.
Alerts or alarms are
triggered for storage utilization based on the following rules:
- Enter condition: Actual
percentage storage utilization is greater than or equal to the high
threshold.
- Clear condition: Actual
percentage storage utilization is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold for storage utilization percentage of
85 for a system
using the Alert thresholding model:
threshold storage-utilization 85
threshold subscriber
active
Configures alarm or
alert thresholds for the number of active subscribers in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold subscriber
active high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high
threshold number of active subscriber sessions facilitated by the
system that must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of active subscriber sessions facilitated by the system that
maintains a previously generated alarm condition. If the number
of sessions falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 and 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Active subscriber thresholds
generate alerts or alarms based on the total number of active subscriber
sessions facilitated by the system during the specified polling
interval.
Alerts or alarms are
triggered for active subscriber totals based on the following rules:
- Enter condition: Actual
total number of active subscriber sessions is greater than or equal
to the high threshold.
- Clear condition: Actual
total number of active subscriber sessions is less than the low
threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures an active subscriber high threshold count of
150000 and
a low threshold of
100000 for
a system using the Alarm thresholding model:
threshold subscriber
active 150000 clear 100000
threshold subscriber
total
Configures alarm or
alert thresholds for the total number of active and inactive subscribers
in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold subscriber
total high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of subscriber sessions (active and dormant) facilitated by
the system that must be met or exceeded within the polling interval
to generate an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of subscriber sessions (active and dormant) facilitated by the
system that maintains a previously generated alarm condition. If
the number of sessions falls beneath the low threshold within the
polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 and 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Total subscriber thresholds
generate alerts or alarms based on the total number of subscriber
sessions (active and dormant) facilitated by the system during the
specified polling interval.
Alerts or alarms are
triggered for subscriber totals based on the following rules:
- Enter condition: Actual
total number of subscriber sessions is greater than or equal to
the high threshold.
- Clear condition: Actual
total number of subscriber sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures an active subscriber high threshold count of
450000 and
a low threshold of
250000 for
a system using the Alarm thresholding model:
threshold subscriber
total 450000 clear 250000
threshold system-capacity
Configures alarm or
alert thresholds based on the percentage of current system capacity.
Privilege:
Security Administrator,
Administrator
Syntax
threshold system high_thresh [ clear low_thresh ]
high_thresh
Default: 90
Specifies the high
threshold system capacity percentage that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
clear low_thresh
Default: 90
Specifies the low threshold
system capacity percentage that maintains a previously generated
alarm condition. If the number of sessions falls beneath the low
threshold within the polling interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 100. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Flash memory utilization
thresholds generate alerts or alarms based on the system utilization.
Alerts or alarms are
triggered for system capacity based on the following rules:
- Enter condition: Actual
percentage of system capacity is greater than or equal to the high
threshold.
- Clear condition: Actual
percentage of system capacity is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a high threshold for system capacity percentage of
95 for a system
using the Alert thresholding model:
threshold system-capacity 95
threshold total-asngw-sessions
Configures alarm or
alert thresholds for the total number of ASN-GW sessions across
all the services in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold total-asngw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold
number of total ASN-GW sessions across all the sessions in the system
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold
number of total ASN-GW sessions that maintains a previously generated
alarm condition. If the number of ASN-GW sessions falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 and 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of ASN-GW sessions across all the services
in the system is equal to or greater than the set limit.
Alerts or alarms are
triggered for the total number of ASN-GW sessions based on the following
rules:
- Enter condition: Actual
total number of ASN-GW sessions is greater than or equal to the
high threshold.
- Clear condition: Actual
total number of ASN-GW sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total ASN-GW session high threshold count of
10000 for
a system using the Alert thresholding model:
threshold total-asngw-sessions 10000
threshold total-ggsn-sessions
Configures alarm or
alert thresholds for the total number of GGSN sessions across all
the services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold total-ggsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default:
0 (Disabled)
Specifies
the high threshold number of total GGSN sessions across all the
sessions in the system that must be met or exceeded within the polling
interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0 (Disabled)
Specifies
the low threshold number of total GGSN sessions that maintains a
previously generated alarm condition. If the number of GGSN sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 and 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor
and set alarms or alerts when the total number of GGSN sessions
across all the services in the system is equal to or greater than
the set limit.
Alerts
or alarms are triggered for the total number of GGSN sessions based
on the following rules:
- Enter condition: Actual
total number of GGSN sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of GGSN sessions is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll command to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total GGSN session high threshold count of
10000 for
a system using the Alert thresholding model:
threshold total-ggsn-sessions 10000
threshold total-gprs-pdp-sessions
Configures alarm or alert
thresholds for the total number of PDP contexts per GPRS sessions
in the system.
Syntax
threshold total-gprs-pdp-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of total PDP contexts per GPRS session for all GPRS services
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of total PDP contexts per GPRS session for all GPRS services
that maintains a previously generated alarm condition. If the number
of sessions falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 and 2000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of GPRS sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for GPRS sessions based on the following rules:
- Enter condition: Actual
total number of PDP Contexts is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of PDP contexts is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of PDP contexts per GPRS session high threshold
count of
10000 for
a system using the Alert thresholding model:
threshold total-gprs-pdp-sessions 10000
threshold total-gprs-sessions
Configures alarm or
alert thresholds for the total number of GPRS sessions in the system.
Syntax
threshold total-gprs-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of total GPRS sessions for all GPRS services that must be
met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of total GPRS sessions for all GPRS services that maintains
a previously generated alarm condition. If the number of sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 and 2000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of GPRS sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for GPRS sessions based on the following rules:
- Enter condition: Actual
total number of GPRS sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of GPRS sessions is less than the low threshol.d
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of GPRS sessions high threshold count of
10000 for a
system using the Alert thresholding model:
threshold total-gprs-sessions 10000
threshold total-ha-sessions
Configures alarm or alert
thresholds for the total number of Home Agent (HA) sessions across
all services in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold total-ha-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of HA sessions for all HA services that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of HA sessions for all HA services that maintains a previously
generated alarm condition. If the number of sessions falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 and 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of HA sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for HA sessions based on the following rules:
- Enter condition: Actual
total number of HA sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of HA sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of HA sessions high threshold count of
10000 for a
system using the Alert thresholding model:
threshold total-ha-sessions 10000
threshold total-hnbgw-hnb-sessions
Configures alarm or
alert thresholds for the total number of Home NodeB (HNB) sessions
across all the HNB Gateway (HNB-GW) services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold total-hnbgw-hnb-sessions high_thresh [ clear low_thresh ]
high_thresh
Default:
0 (Disabled)
Specifies
the high threshold for the total number of HNB-HNB-GW sessions on
IuH interfaces across all HNB-GW services on a system that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0 (Disabled)
Specifies
the low threshold for the total number of HNB-HNB-GW sessions on
IuH interfaces across all services on a system that maintains a
previously generated alarm condition. If the number of HNB-HNB-GW
sessions in a system falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 through 1000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use
this command to monitor and set alarms or alerts when the total
number of HNB-HNB-GW sessions on IuH interface across all HNB-GW
services in the system is equal to or greater than the set limit.
Alerts
or alarms are triggered for the total number of HNB-HNB-GW sessions
on IuH interface based on the following rules:
- Enter condition: Actual
total number of HNB-HNB-GW sessions on IuH interface is greater
than the high threshold.
- Clear condition: Actual
total number of HNB-HNB-GW sessions on IuH interfaces is less than
the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll total-hnbgw-hnb-sessions command to configure the
polling interval and the threshold monitoring
hnbgw-service command to enable thresholding for this
value.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWHnbSess command
in this mode.
Example:
The
following command configures the total number of HNB-GW-HNB sessions
on IuH interfaces to a high threshold count of
10000 for
a system using the Alert thresholding model:
threshold total-hnbgw-hnb-sessions 10000
threshold total-hnbgw-iu-sessions
Configures alarm or
alert thresholds for the total number of subscriber sessions towards
the Core Networks (CN) across all HNB-GW services over Iu interfaces
(Iu-CS/Iu-PS interface) on a system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold total-hnbgw-iu-sessions high_thresh [ clear low_thresh ]
high_thresh
Default:
0 (Disabled)
Specifies
the high threshold for the total number of subscriber sessions towards
CN across all HNB-GW services on a system that must be met or exceeded
within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 3000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0 (Disabled)
Specifies
the low threshold for the total number of subscriber sessions towards
CN across all services on a system that maintains a previously generated
alarm condition. If the number of subscriber sessions falls beneath
the low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 through 3000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use
this command to monitor and set alarms or alerts when the total
number of subscriber sessions towards CN across all HNB-GW services
in the system is equal to or greater than the set limit.
Alerts
or alarms are triggered for the total number of subscriber sessions
towards CN across all HNB-GW service on a system based on the following
rules:
- Enter condition: Actual
total number of subscriber sessions across all HNB-GW service on
a system is greater than the high threshold.
- Clear condition: Actual
total number of subscriber sessions across all HNB-GW service on
a system is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll total-hnbgw-iu-sessions command to configure the
polling interval and the threshold monitoring
hnbgw-service command to enable thresholding for this
value.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWIuSess command
in this mode.
Example:
The
following command configures the total number of subscriber sessions
towards CN across all HNB-GW services to a high threshold count
of
30000 for
a system using the Alert thresholding model:
threshold total-hnbgw-iu-sessions 30000
threshold total-hnbgw-ue-sessions
Configures alarm or
alert thresholds for the total number of UEs connected to an HNB-GW
service across all the HNB-GW services in the system.
Privilege:
Security
Administrator, Administrator
Syntax
threshold total-hnbgw-ue-sessions high_thresh [ clear low_thresh ]
high_thresh
Default:
0 (Disabled)
Specifies
the high threshold for the total number of UEs connected across
all HNB-GW services on a system that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default:
0 (Disabled)
Specifies
the low threshold for the total number of UEs connected to HNB-GW
service across all HNB-GW services that maintains a previously generated
alarm condition. If the number of UE sessions across all the services
in a system, falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 and 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use
this command to monitor and set alarms or alerts when the total
number of UEs connected to HNB-GW service across all HNB-GW services
in the system is equal to or greater than the set limit.
Alerts
or alarms are triggered for the total number of UEs connected across
all HNB-GW service on a system based on the following rules:
- Enter condition: Actual
total number of UEs connected to HNB-GW service across all HNB-GW
services on a system is greater than the high threshold.
- Clear condition: Actual
total number of UEs connected to HNB-GW service across all HNB-GW
services on a system is less than the low threshold.
If
a trigger condition occurs within the polling interval, the alert
or alarm will not be generated until the end of the polling interval.
Refer
to the threshold
poll total-hnbgw-ue-sessions command to configure the
polling interval and the threshold monitoring
hnbgw-service command to enable thresholding for this
value.
IMPORTANT:
To enable an SNMP trap
for monitoring this threshold use the snmp trap enable ThreshTotalHNBGWUeSess command
in this mode.
Example:
The
following command configures the total number of UEs connected to
HNB-GW service across all HNB-GW services to a high threshold count
of
40000 for
a system using the Alert thresholding model:
threshold total-hnbgw-ue-sessions 40000
threshold total-hsgw-sessions
Configures alarm or alert
thresholds for the total number of HRPD Serving Gateway (HSGW) sessions
across all services in the system.
Syntax
threshold total-hsgw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
for the number of HSGW sessions for all HSGW services that must
be met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 1 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
for the number of HSGW sessions for all HSGW services that maintains
a previously generated alarm condition. If the number of sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 and 2500000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of HSGW sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for HSGW sessions based on the following rules:
- Enter condition: Actual
total number of HSGW sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of HSGW sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of HSGW sessions high threshold count of
500000 for
a system using the Alert thresholding model:
threshold total-hsgw-sessions 500000
threshold total-lma-sessions
Configures alarm or
alert thresholds for the total number of Local Mobility Anchor (LMA)
sessions across all services in the system.
Syntax
threshold total-lma-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of LMA sessions for all LMA services that must be met or
exceeded within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 1 through 1500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of LMA sessions for all LMA services that maintains a previously
generated alarm condition. If the number of sessions falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 1500000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of LMA sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for LMA sessions based on the following rules:
- Enter condition: Actual
total number of LMA sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of LMA sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of LMA sessions high threshold count of
500000 for
a system using the Alert thresholding model:
threshold total-lma-sessions 500000
threshold total-lns-sessions
Configures alarm or
alert thresholds for the total number of L2TP Network Server (LNS)
sessions in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold total-lns-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of total LNS sessions that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh is
an integer value from 0 through 4000000. A value of 0 disables the
threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of total LNS sessions that maintains a previously generated
alarm condition. If the number of LNS sessions falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 and 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of LNS sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for the total number of LNS sessions based on the following rules:
- Enter condition: Actual
total number of LNS sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of LNS sessions is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total LNS session high threshold count of
10000 for
a system using the Alert thresholding model:
threshold total-lns-sessions 10000
threshold total-mme-sessions
Configures alarm or
alert thresholds for the total number of Mobility Management Entity
(MME) sessions across all the MME services in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold total-mme-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0 (Disabled)
Specifies the high threshold
number of total MME sessions that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh is
an integer value from 0 through 2500000. A value of 0 disables the
threshold.
clear low_thresh
Default: 0 (Disabled)
Specifies the low threshold
number of total MME sessions that maintains a previously generated
alarm condition. If the number of MME sessions, across all the services
in a system, falls beneath the low threshold within the polling
interval, a clear alarm will be generated.
low_thresh is
an integer from 0 and 2500000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
monitor and set alarms or alerts when the total number of MME sessions
across all the MME services in the system is equal to or greater
than the set limit.
Alerts
or alarms are triggered for the total number of MME sessions based
on the following rules:
- Enter condition: Actual
total number of MME sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of MME sessions is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll total-mme-sessions command
to configure the polling interval and the threshold monitoring mme-service command
to enable thresholding for this value.
Example:
The following command
configures a total MME session high threshold count of
10000 for
a system using the Alert thresholding model:
threshold total-mme-sessions 10000
threshold total-pdsn-sessions
Configures alarm or
alert thresholds for the total number of Packet Data Serving Node
(PDSN) sessions in the system.
Privilege:
Security Administrator,
Administrator
Syntax
threshold total-pdsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of total PDSN sessions that must be met or exceeded within
the polling interval to generate an alert or alarm.
high_thresh is
an integer from 0 through 2500000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of total PDSN sessions that maintains a previously generated
alarm condition. If the number of PDSN sessions falls beneath the
low threshold within the polling interval, a clear alarm will be
generated.
low_thresh is
an integer from 0 and 2500000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of PDSN sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for the total number of PDSN sessions based on the following
rules:
- Enter condition: Actual
total number of PDSN sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of PDSN sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total PDSN session high threshold count of
10000 for
a system using the Alert thresholding model:
threshold total-pdsn-sessions 10000
threshold total-pgw-sessions
Configures alarm or
alert thresholds for the total number of Packet Data Network Gateway
(P-GW) sessions across all services in the system.
Syntax
threshold total-pgw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of P-GW sessions for all P-GW services that must be met or
exceeded within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 1 through 3000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of P-GW sessions for all P-GW services that maintains a previously
generated alarm condition. If the number of sessions falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 3000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of P-GW sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for P-GW sessions based on the following rules:
- Enter condition: Actual
total number of P-GW sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of P-GW sessions is less than the low threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of P-GW sessions high threshold count of
500000 for
a system using the Alert thresholding model:
threshold total-pgw-sessions 500000
threshold total-sgsn-pdp-sessions
Configures alarm or
alert thresholds for the total number of PDP contexts for all Serving
GPRS Support Node (SGSN) sessions in the system.
Syntax
threshold total-sgsn-pdp-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of total PDP contexts per SGSN session for all SGSN services
that must be met or exceeded within the polling interval to generate
an alert or alarm.
high_thresh is
an integer from 1 through 4000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of total PDP contexts per SGSN session for all SGSN services
that maintains a previously generated alarm condition. If the number
of sessions falls beneath the low threshold within the polling interval,
a clear alarm will be generated.
low_thresh is
an integer from 0 through 4000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of SGSN sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for SGSN sessions based on the following rules:
- Enter condition: Actual
total number of PDP contexts is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of PDP contexts is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of PDP contexts per SGSN session high threshold
count of
10000 for
a system using the Alert thresholding model:
threshold total-sgsn-pdp-sessions 10000
threshold total-sgsn-sessions
Configures alarm or
alert thresholds for the total number of SGSN sessions in the system.
Syntax
threshold total-sgsn-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of total SGSN sessions for all SGSN services that must be
met or exceeded within the polling interval to generate an alert
or alarm.
high_thresh is
an integer from 1 through 2000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of total SGSN sessions for all SGSN services that maintains
a previously generated alarm condition. If the number of sessions
falls beneath the low threshold within the polling interval, a clear
alarm will be generated.
low_thresh is
an integer from 0 through 2000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of SGSN sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for SGSN sessions based on the following rules:
- Enter condition: Actual
total number of SGSN sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of SGSN sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of SGSN sessions high threshold count of
10000 for
a system using the Alert thresholding model:
threshold total-sgsn-sessions 10000
threshold total-sgw-sessions
Configures alarm or
alert thresholds for the total number of Serving Gateway (S-GW)
sessions across all services in the system.
Syntax
threshold total-sgw-sessions high_thresh [ clear low_thresh ]
high_thresh
Default: 0
Specifies the high threshold
number of S-GW sessions for all S-GW services that must be met or
exceeded within the polling interval to generate an alert or alarm.
high_thresh is
an integer from 1 through 3000000. A value of 0 disables the threshold.
clear low_thresh
Default: 0
Specifies the low threshold
number of S-GW sessions for all S-GW services that maintains a previously
generated alarm condition. If the number of sessions falls beneath
the low threshold within the polling interval, a clear alarm will
be generated.
low_thresh is
an integer from 0 through 3000000. A value of 0 disables the threshold.
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Monitor and set alarms
or alerts when the total number of S-GW sessions in the system is equal
to or greater than the set limit.
Alerts or alarms are
triggered for S-GW sessions based on the following rules:
- Enter condition: Actual
total number of S-GW sessions is greater than or equal to the high
threshold.
- Clear condition: Actual
total number of S-GW sessions is less than the low threshold.
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
Refer to the threshold poll command
to configure the polling interval and the threshold monitoring command
to enable thresholding for this value.
Example:
The following command
configures a total number of S-GW sessions high threshold count of
500000 for
a system using the Alert thresholding model:
threshold total-sgw-sessions 500000
threshold tpo-dns-failure
Configures alarm or
alert thresholds for monitoring Traffic Performance Optimization
(TPO) DNS resolution failures.
Privilege:
Security Administrator,
Administrator
Syntax
threshold tpo-dns-failure high_thresh [ clear low_thresh ]
default threshold tpo-dns-failure
default
Configures this command
with the default threshold setting.
Default: 0—disabled
high_thresh
Specifies that if in
a polling interval the number of TPO DNS failures experienced by
the system meets or exceeds high_thresh an
alert or alarm should be generated.
high_thresh is
an integer from 0 through 10000.
Default: 0
clear low_thresh
Specifies that if,
within the polling interval, the number of TPO DNS failures experienced by
the system falls below low_thresh a
clear alarm should be generated.
low_thresh is
an integer from 0 through 10000.
Default: 0
Usage:
Use this command to
configure thresholds for monitoring TPO DNS resolution failures.
threshold tpo-low-compression-gain
Configures alarm or
alert thresholds for monitoring TPO low compression gain comparison
results.
Privilege:
Security Administrator,
Administrator
Syntax
threshold tpo-low-compression-gain high_thresh [ clear low_thresh ]
default threshold tpo-low-compression-gain
default
Configures this command
with the default threshold setting.
Default: 0—disabled
high_thresh
Specifies that if in
a polling interval the number of TPO low-compression-gain comparison results
experienced by the system meets or exceeds high_thresh an alert
or alarm is generated.
high_thresh is
an integer from 0 through 100000.
Default: 0
clear low_thresh
Specifies that if,
within the polling interval, the number of TPO low-compression-gain comparison
results experienced by the system falls below low_thresh a
clear alarm is generated.
low_thresh is
an integer from 0 through 100000.
Default: 0
Usage:
Use this command to
configure thresholds for monitoring TPO low compression gain results.
threshold tpo-rto-timeout
Configures alarm or
alert thresholds for monitoring TPO retransmission timeouts (RTOs).
Privilege:
Security Administrator,
Administrator
Syntax
threshold tpo-rto-timeout high_thresh [ clear low_thresh ]
default threshold tpo-rto-timeout
default
Configures this command
with the default threshold setting.
Default: 0—disabled
high_thresh
Specifies that if in
a polling interval the number of TPO RTOs experienced by the system meets
or exceeds high_thresh an
alert or alarm should be generated.
high_thresh is
an integer from 0 through 5000000.
Default: 0
clear low_thresh
Specifies that if,
within the polling interval, the number of TPO RTOs experienced
by the system falls below low_thresh a
clear alarm should be generated.
low_thresh is
an integer from 0 through 5000000.
Default: 0
Usage:
Use this command to
configure thresholds for monitoring TPO DNS resolution failures.
timestamps
Enables or disables
the generation of a timestamp in response to each commands entered.
The timestamp does not appear in any logs as it is a CLI output
only. This command affects all future CLI sessions. Use the timestamps command
in the Exec Mode to change the behavior for the current CLI session
only.
Privilege:
Security Administrator,
Administrator
Syntax
timestamps
no timestamps
no
Disables generation
of timestamps for each command entered. When omitted, the output
of a timestamp for each entered command is enabled.
Usage:
Enable the timestamps
when logging a CLI session on a remote terminal such that each command
will have a line of text indicating the time when the command was entered.
upgrade limit
Configures upgrade session
limits that trigger when the system may execute the software upgrade.
Privilege:
Security Administrator,
Administrator
Syntax
upgrade limit [ time session_life ] [ usage session_num ]
upgrade limit
This command issued
with no keywords sets all parameters to their defaults.
time session_life
Default: 120
Defines the maximum
number of minutes that a session may exist on the system undergoing a
software upgrade, before it is terminated by the system. As individual
user sessions reach this lifetime limit, the system terminates the
individual session(s). session_life must
be an integer ranging from 1 through 1440.
usage session_num
Default: 100
This keyword defines
a low threshold limit of sessions running either on a packet processing card
or system-wide. When a software upgrade is invoked, this parameter
applies to the entire system.
When the threshold is
crossed (when the number of sessions on the packet processing card or
system is less than this value), the remaining sessions on the card
or system are terminated allowing the upgrade to begin. The remaining
sessions on the packet processing card or system are terminated
regardless of their session life. session_num must
be an integer from 0 through 6000.
Usage:
Use this command to
configure upgrade session limits that trigger the system to begin executing
the software upgrade.
IMPORTANT:
This command is not
supported on all platforms.
IMPORTANT:
Software Patch Upgrades
are not supported in this release.
Example:
The following command
sets the number of minutes a session can exist to
200, and the
minimum number of sessions that may exist before terminating them
to
50:
upgrade limit time 200
usage 50
url-blacklisting
database
This command configures
URL Blacklisting database directory parameters.
Privilege:
Security Administrator,
Administrator
Syntax
url-blacklisting database { directory
path path | max-versions max_versions | override
file file_name }
default url-blacklisting
database { directory path | max-versions | override
file }
default
Configures this command
with the default settings.
directory path path
Specifies the path to
the directory to be used for storing URL Blacklisting databases.
path must
be an alphanumeric string of 1 through 255 characters.
Default: /flash/bl
max-versions max_versions
Specifies the maximum
number of URL Blacklisting database versions to be maintained in the
URL Blacklisting database directory path with the base file name
specified by the URL Blacklisting database override file.
max_versions must
be an integer from 0 through 3.
Default:
0
override file file_name
Specifies the URL Blacklisting
database override file name.
file_name must
be in name.extension format.
For example, abc.bin.
And, must be an alphanumeric string of 1 through 10 characters.
Default: optblk.bin
Usage:
Use this command to
configure URL Blacklisting database directory parameters.
Example:
The following command
configures the maximum number of URL Blacklisting database versions
to be maintained to
3:
url-blacklisting database
max-versions 3