administrator: Configures the default domain for context-level administrative users.
subscriber: Configures the default domain for subscribers.
Specifies the context which is to be set as the default. domain_name must be from 1 to 79 alpha and/or numeric characters with no spaces.
Important: This command is only available in Release 8.3 and later.
prefix_length must be an integer from 1 through 15.
Important: For this command to take affect, after entering the command the configuration must be saved and reloaded.
In Exec mode, use the save configuration command and then the
reload command.
administrator: Configures the last resort domain for context-level administrative.
subscriber: Configures the last resort domain for the subscribers.
Specifies the context which is to be set as the last resort. context_name must be from 1 to 79 alpha and/or numeric characters with no spaces.
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.
ecs_service_name must be an alpha and/or numeric string of 1 through 15 characters in length.
Use this command after enabling Enhanced Charging Service using the require active-charging command. This command allows administrative users to configure the Enhanced Charging Service functionality.
audible: indicates the internal audible alarm on the switch processor cards are to be enabled.
central-office: indicates the central office alarms are to be enabled.
Important: To change the behavior for the current CLI session only, use the
autoconfirm command in the Exec Mode.
By default autoconfirm is enabled.
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.
Specifies the banner or message to be displayed at session initialization. string may be from 0 to 2048 characters and must be enclosed in double quotation marks if the banner or message is to include spaces.
Important: The settings for this command are stored immediately in the boot.sys file. No changes are made to the system configuration file.
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 refer to either the RJ-45 interfaces for speeds of 10, 100, or 1000 megabit per second (Mbps) or the SFP interface for the optical gigabit (1000 Mbps) interface.
medium { auto | speed medium_speed duplex medium_duplex }
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:
Important: The settings for this command are stored immediately in the boot.sys file. No changes are made to the system configuration file.
Important: The settings for this command are stored immediately in the boot.sys file. No changes are made to the system configuration file.
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 the standard 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 the standard 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 specified using the standard IPv4 dotted-decimal notation.
Important: If
gw_address is not specified, then 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.
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.
Important: When performing a software upgrade it is important that the new file group have the highest priority (lowest value) configured.
Important: It is suggested that an “N-1” priority numbering methodology, where “N” is the first priority in the current boot stack be employed to ensure that higher priority numbers remain open.
•
|
[ 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.
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 information.
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.
•
|
[ file: ]{ /flash | /pcmcia1 | /pcmcia2 }[ /path ] /filename
|
•
|
[ 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.
Important: The configuration file must reside on the SMC’s local filesystem, stored on one of its local devices (/flash, /pcmcia1, /pcmcia2, /hd). 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.
[<context-name>]asr5000(config-bulkstats)#
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.
The PEM-formatted data can be specified (data pemdata) or the information can be read from a file via url
url). 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.
Important: This command is not supported on all platforms.
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.
slot_num may be repeated as many times as necessary to indicate the complete search order.
Important: This command replaces the
pac-standby-priority command.
Important: This command is not supported on all platforms.
The PEM-formatted data can be specified (data pemdata) or the information can be read from a file via url
url). 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.
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.
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.
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.
Important: The maximum number of multiple CLI session support is based on the amount of available memory. The Resource Manager, however, reserves enough resources so that a minimum of 15 CLI sessions are assured for ASR 5000s. One of the CLI sessions is reserved for use exclusively by a CLI session on an SPIO console interface. Additional CLI sessions beyond the pre-reserved set are permitted if sufficient SMC resources are available. If the Resource Manager is unable to reserve resources for a CLI session beyond those that are pre-reserved, administrative users are prompted as to whether or not the system should attempt to create the new CLI session even without reserved resources.
The following command sets the command monitor protocol to administrator-only
Indicates the timezone specified by tz is to be considered the local time zone for local time display and conversion.
•
|
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.
|
•
|
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.
|
To verify the congestion-control configuration use show congestion-control configuration from the Exec mode.
license-utilization: An integer value between 1 and 100 that specifies the license-utilization percentage threshold for overload situations. If candidates are available, passive calls are disconnected when this threshold is exceeded. The default value is 80.
max-sessions-per-service-utilization: An integer value between 1 and 100 that specifies a percentage of the maximum sessions per service. If candidates are available, passive calls are disconnected when this threshold is exceeded. The default value is 80.
tolerance: An integer between 1 and 25 that 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. The tolerance default value is 10.
For MME type of session/calls redirect action is not supported.
•
|
drop: Specifies that the system is to drop incoming packets containing new session requests. (PDSN, GGSN, ASN GW, LMA, MME, and ASN PC and HA only)
|
•
|
none: Specifies that the system is take no action. This is the default for PDIF-service.
|
•
|
redirect: Specifies that the system is to redirect new session requests to an alternate device. (PDSN and HA only)
|
Important: If this option is used, the IP address of the alternate device must be configured using the
policy overload redirect command that is part of the service configuration. Note that this option can not be used in conjunction with GGSN and MME services.
•
|
reject: Specifies that the system processes new session request messages and responds with a reject message. (For PDSN and HA, the reply code is 130, “insufficient resources”. For the GGSN, the reply code is 199, “no resources available”.)
|
congestion-control threshold { license-utilizationpercent| max-sessions-per-service-utilization percent| message-queue-utilizationpercent| message-queue-wait-timetime| port-rx-utilizationpercent| port-specific {slot/port| all} [tx-utilizationpercent] [rx-utilizationpercent] | port-tx-utilizationpercent| service-control-cpu-utilizationpercent| system-cpu-utilizationpercent| system-memory-utilizationpercent| tolerancepercent }
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.
percent can be configured to any integer value from 0 to 100.
Important: In the event that this threshold is crossed, an SNMP trap is not triggered. In addition, the service congestion policy invocation resulting from the crossing of this threshold is enforced only for the packet that triggered the action.
[no] port-specific {slot/port | all} [rx-utilization percent] [tx-utilization percent]
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.
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.
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 can not be removed from configuration. Later if you want to enable the previously configured threshold value of
75 percent you only need to enter
congestion-control threshold system-cpu-utilization command without specifying any threshold value and it will enable the CPU utilization threshold to preconfigured level of
75 percent.
For example, no congestion-control threshold system-cpu-utilization will disable the configured threshold setting and
congestion-control threshold system-cpu-utilization will again enable the threshold setting of 75%.
directory_path must be an alpha and/or numeric string of 1 through 255 characters in length.
The following command configures the /flash/cf_temp/DB as base directory to download all full and incremental content-rating databases for content filtering application.
num_archive must be an integer between 1 and 3.
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. Note that the specified directory path is the location specified using the
content-filtering category database directory path command.
The following command configures the system to maintain 3 full content-rating databases for category-based content filtering application.
file_name must be an alpha and/or numeric string of up to 10 characters with an extension of 3 character after a period (.) as
extension.
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.
Important: When creating a new context, the context name specified must not conflict with the name of any existing context or domain names.
Important: A maximum of 64 contexts may be created.
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.
The filename-pattern is a string containing any or all of the following variables:
•
|
%time% - POSIX timestamp in hexadecimal notation
|
•
|
%filename% - Alias for crash- %card%- %cpu%- %time- core%
|
Specifies the location to store crash files. crash_url may refer to a local or a remote file.
crash_url must be entered using one of the following formats:
Important: Use of the SMC hard drive is not supported in this release.
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.
The restrict keyword is only applicable to local URLs.
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 must be from 1 to 63 alpha and/or numeric characters.
Caution: This is a critical configuration. The HNBs can not 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.
[context_name]
hostname(config-cs-network)#
The following command will remove HNB-CS network instance hnb-cs1 from the system without any warning to operator:
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.
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.
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.
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.
•
|
priority : All DSCP values are mapped to the best-effort priority queue but are not configured.
|
engine-id: restores the SNMP engine ID to the system default.
notif-threshold: restores the SNMP notification threshold to the system default.
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.
•
|
cpu-load: PSC/PSC2 CPU load using a 5 minute average measurement
|
•
|
license: Session license threshold settings
|
•
|
model: Thresholding model settings
|
•
|
monitoring: Threshold monitoring configuration settings
|
•
|
poll: Threshold polling interval configuration settings
|
•
|
total: Total subscriber threshold settings
|
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.
space_mb must be an integer from 10 through 256.
Important: This command must be executed at startup only and will not take effect when reconfigured without rebooting.
Return to the Exec mode. This command has the same effect as the end command as the global configuration mode’s parent mode is the Exec mode.
max_number: Must be an integer from 1 to 4.
mega_bytes: Must be an integer from 10 to 256. The default is 32 MB.
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”.
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.
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.
name: must be a string of 1 to 63 alphanumeric characters.
name: must be a string of 1 to 63 alphanumeric characters.
[context_name]
hostname(config-hd-raid)#
[context_name]
hostname(config-hd-storage-policy)#
The following command creates an HD storage policy named policy3 and enters the HD Storage Policy Configuration Mode:
•
|
aggressive: Initiates PSC failover without performing additional checks.
|
•
|
normal: Initiates PSC failover after additional checks are performed.
|
Installs the license key specified by key_value.
key_value is provided by Cisco Systems operations staff.
Important: This is a customer-specific command that is available for HA, PDSN, EHA, and PDIF. Please contact your local sales representative for more information.
Caution: Use of this option is not recommended.
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.
•
|
ansi-t1.276-2003: If this option is selected, then the following rules are enforced:
|
•
|
none: No additional password checks are performed.
|
[ history length number [ duration days ] ]
number is the number of entries for each account stored in the history list and can be configured to any integer value from 1 to 100.
days is the number of days during which a password can not be reused and can be configured to any integer value between 1 and 365.
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 and can be configured to any integer value from 1 to 365.
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 and can be configured to any integer value between 0 and 16.
days is the minimum number of days that must pass before a user can change their password. It can be configured to any integer value from 1 to 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.
number is the minimum number of alpha and/or numeric characters that the password must contain and can be configured to any integer value between 3 and 32.
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
•
|
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, statistic, 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: The user has access.
|
•
|
noecs: The user does not have access.
|
•
|
ftp: The user has access.
|
•
|
noftp: The user does not have access.
|
Specifics the maximum session time for this user. time is measured in minutes and can be configured to any integer value between 0 and 525600. A value of “0” indicates no limit.
Important: This limit applies only to the user’s CLI sessions.
Specifics the maximum idle time for this user. time is measured in minutes and can be configured to any integer value between 0 and 525600. A value of “0” indicates no limit.
Important: This limit applies only to the user’s CLI sessions.
Specifies the initial password for this user. password must from 6 to 32 alpha and or numeric characters in length in length and is case sensitive.
Important: The user is requested to change their password upon their first login.
Specifies the end ID of the events when a range of event ID is to be disabled from being logged. to_id must be a value in the range 1 through 100000. The
to_id must be equal to or larger than the
id specified.
•
|
a10: A10 interface facility
|
•
|
a11: A11 interface facility
|
•
|
aaamgr: AAA manager logging facility
|
•
|
acl-log: Access Control List logging facility
|
•
|
acsctrl: Active Charging Service (ACS) Controller facility
|
•
|
acsmgr: Active Charging Service (ACS) Manager facility
|
•
|
asf: Voice Application Server Framework logging facility
|
•
|
asfprt: ASF Protocol Task (SIP) logging facility
|
•
|
asnlrmgr: ASN Paging/Location-Registry Manager facility
|
•
|
bgp: Border Gateway Protocol (BGP) facility
|
•
|
bssap+: Base Station Sub-system Application Part+ logging facility
|
•
|
bssgp: Base Station Sub-system GPRS Protocol logging facility
|
•
|
cap: Camel Application Part logging facility
|
•
|
chatconf: Voice Chat/Conference logging facility
|
•
|
cli: CLI logging facility
|
•
|
csp: Card Slot Port controller facility
|
•
|
css: Content Service Selection (CSS) facility
|
•
|
css-sig: Content Service Selection (CSS) RADIUS Signaling facility
|
•
|
dcardctrl: IPSEC Daughter card Controller logging facility (not used at this time)
|
•
|
dcardmgr: IPSEC Daughter card Manager logging facility (Not used at this time)
|
•
|
dgmbmgr: Diameter Gmb Application Manager logging facility
|
•
|
dhcp: DHCP facility (GGSN product only)
|
•
|
dhost: Distributed Host logging facility
|
•
|
diameter: Diameter endpoint logging facility
|
•
|
dpath: IPSEC Data Path facility
|
•
|
ds3mgr: DS3 Manager logging facility
|
•
|
ecs-css: ACSMGR <-> Session Manager Signalling Interface Logging facility
|
•
|
famgr: Foreign Agent manager logging facility
|
•
|
firewall: Inline per-subscriber Stateful Firewall facility
|
•
|
gmm: GMM Protocol logging facility
|
•
|
gprs-ns: GPRS-NS Protocol logging facility
|
•
|
gss-gcdr: GTPP Storage Server GCDR facility
|
•
|
gtpc: GTP-C protocol logging facility (GGSN product only)
|
•
|
gtpcmgr: GTP-C protocol Manager logging facility (GGSN product only)
|
•
|
gtpp: GTP-PRIME protocol logging facility (GGSN product only)
|
•
|
gtpu: GTP-U protocol logging facility (GGSN product only)
|
•
|
h248prt: H.248 Protocol logging facility
|
•
|
hamgr: Home Agent manager logging facility
|
•
|
hat: High Availability Task (HAT) process facility
|
•
|
hdctrl: HD Controller logging facility
|
•
|
ip-arp: IP Address Resolution Protocol facility
|
•
|
ipsec: IP Security logging facility
|
•
|
ipsg: IP Service Gateway interface logging facility
|
•
|
ipsp: IP Pool Sharing Protocol logging facility
|
•
|
l2tpmgr: L2TP Manager logging facility
|
•
|
li: Lawful intercept facility (Logs are visible only to system accounts with li-administrator privileges.)
|
•
|
linkmgr: SGSN/SS7 Links Manager facility
|
•
|
llc: Logical Link Control (LLC) Protocol logging facility
|
•
|
m3ua: MTP3 User Adaptation (M3UA) Protocol logging facility
|
•
|
map: Mobile Application Part (MAP) Protocol logging facility
|
•
|
mmgr: Master Manager logging facility
|
•
|
mtp3: Message Transfer Part (MTP3) Protocol logging facility
|
•
|
npuctrl: Network Processor Unit Control facility
|
•
|
npumgr: Network Processor Unit Manager facility
|
•
|
nsctrl: Charging Service Controller facility (supported in conjunction with ECSv1)
|
•
|
nsmgr: Charging Service Manager facility
|
•
|
nsproc: Charging Service process facility
|
•
|
orbs: Object Request Broker System logging facility
|
•
|
ospf: OSPF logging facility
|
•
|
pdif: PDIF logging facility
|
•
|
pmm-app: PMM application logging facility
|
•
|
ppp: PPP link and packet facilities
|
•
|
ptt: Voice push-to-talk logging facility
|
•
|
push: VPNMGR CDR push logging facility
|
•
|
radius-coa: RADIUS change of authorization and radius disconnect
|
•
|
ranap: RANAP Protocol logging facility
|
•
|
rct: Recovery Control Task logging facility
|
•
|
rdt: Redirect Task logging facility
|
•
|
resmgr: Resource Manager logging facility
|
•
|
rip: RIP logging facility (RIP is not supported at this time.)
|
•
|
rohc: RObust Header Compression facility
|
•
|
rsvp: Reservation Protocol logging facility
|
•
|
sccp: SCCP Protocol logging facility
|
•
|
sct: Shared Configuration Task logging facility
|
•
|
sctp: SCTP Protocol logging facility
|
•
|
sessctrl: Session Controller logging facility
|
•
|
sessmgr: Session Manager logging facility
|
•
|
sft: Switch Fabric Task logging facility
|
•
|
sgsn-app: SGSN-APP interface logging facility
|
•
|
sgsn-gtpc: SGSNs GTP-C Protocol logging facility
|
•
|
sgsn-gtpu: SGSNs GTP-U Protocol logging facility
|
•
|
sgsn-misc: SGSN miscellaneous logging facility
|
•
|
sitmain: System Initialization Task main logging facility
|
•
|
sm-app: Session Management (SM) Protocol logging facility
|
•
|
sms: Short Message Service (SMS) logging facility
|
•
|
sndcp: Sub-Network Dependent Convergence (SNDCP) Protocol logging facility
|
•
|
snmp: SNMP logging facility
|
•
|
srdb: Static Rating Database
|
•
|
srp: Service Redundancy Protocol (SRP) logging facility
|
•
|
sscfnni: Service Specific Co-ordination Function for UNNI (SCFNNI) Protocol logging facility
|
•
|
sscop: Service Specific Connection Oriented Protocol (SSCOP) logging facility
|
•
|
stat: Statistics logging facility
|
•
|
taclcp: Type Allocation Code (TAC) Local Call Processing logging facility
|
•
|
tcap: Transaction Capabilities Application Part (TCAP) Protocol logging facility
|
•
|
ttg: TTG logging facility
|
•
|
tucl: TUCL logging facility
|
•
|
udr: User detail record facility (used with the Charging Service)
|
•
|
vim: Voice Instant Messaging logging facility
|
•
|
vinfo: Voice Information logging facility
|
•
|
vpn: Virtual Private Network logging facility
|
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-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.
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.
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.
username user_name: specifies a user for which the monitoring filter is to be set.
user_name must refer to a previously configured user.
Caution: Issuing this command could negatively impact system performance depending on the number of subscribers for which monitoring is performed and/or the amount amount of data they’re passing.
The following command enables the monitoring of user user1 and mobile subscriber ID 4441235555, respectively.
Using default in the command, disables this attach rate throttle feature.
#_new_connections: Must be an integer from 50 to 5000.
•
|
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:
|
Counters for this feature are available in the show gmm-sm statistics command display in the Network Overload Protection portion of the table.
peer-nsei peer_nsei_number frame-relay
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.
Important: This command is only required for code versions prior to 4.5.
Important: Executing this keyword increases the maximum number of PDP contexts supported per Session Manager from 2000 to 4000.
Caution: In order for this command to function properly, this command must be executed prior to configuring services on the system.
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.
slot: Identifies the chassis slot holding the line card that supplies ATM ports. The slot ID number can be any valid integer between 17 and 48.
port: Identifies the physical port that is to be configured to support ATM signaling. The ID number can be any valid integer between 1 and 4.
Important: This command is not supported on all platforms.
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.
Important: This command is not supported on all platforms.
slot: Identifies the chassis slot holding the Channelized line card that supplies Frame Relay ports. The slot ID number can be any valid integer between 17 and 48.
port: Identifies the physical port that is to be configured to support Frame Relay signaling. The ID number can only be 1.
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.
The value for slot must be either 24 or 25.
[context_name]
hostname(config-hsgw-association-table)#
Important: This command creates a mapping table available to any HSGW context configured on 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.
Warning: 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 must be from 1 to 63 alpha and/or numeric characters.
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.
[context_name]
hostname(config-ps-network)#
Creates a new or enters an existing mapping configuration. name must be from 1 to 63 alpha and/or numeric characters.
[context_name]
hostname(config-qci-qos-mapping)#
Important: This command creates a mapping configuration available to any HSGW, P-GW, S-GW context configured on the system.
percent can be configured to any integer value from 0 to 100.
percent can be configured to any integer value from 0 to 100.
percent can be configured to any integer value from 0 to 100.
percent can be configured to any integer value from 0 to 100.
Important: This functionality is not supported for use with the PDSN at this time.
slot_num is an integer from 1 to 48 that represents the slot in which a PSC/PSC2 is installed. These cards can be installed in slots 1 through 8, and/or 10 through 16.
cpu_num is an integer value from 0 to 3. 0 represents the lead CP.
Important: This functionality is not supported for use with the PDSN at this time.
Important: This functionality is not supported for use with the PDSN at this time.
Specifies the name of the RAN Peer Map. name must be from 1 to 31 alpha and/or numeric characters.
Important: In Release 8.1 and later, this keyword is not supported.
Important: In Release 8.0 and earlier and in Release 9.0 and later, 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 Optimized mode.
Use the require active-charging command to enable ACS in the non-optimized mode. Wherein, ACSMgrs 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 SessMgr.
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.
Important: This command is not supported on all platforms.
Important: Upon entering this command, the system must be restarted before the command takes effect. Remember to save the configuration file before issuing the reload command.
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.
The name of the RoHC profile to create or remove. name must be an alphanumeric string of from 1 through 63 characters in length.
[context_name]
host(config-rohcprofile-<
profile_name>)#
Enter the following command to create an RoHC profile named HomeUsers and enter the RoHC Configuration mode without prompting for verification:
sccp_net_id: must be an integer from 1 through 12.
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.:
session trace [ collection-timer sec ] [ network-element { all | mme | pgw | sgw } ] [ retry-timer
sec ] [ tce-mode { none | push transport { ftp | sftp } path
string username
name { encrypted password
enc_pw | password
password }}]
all: Specifies that all network elements and their associated interfaces are to be made available to the session trace application.
mme: Specifies that the MME network element and it’s associated interfaces is to be made available to the session trace application.
pgw: Specifies that the P-GW network element and it’s associated interfaces is to be made available to the session trace application.
sgw: Specifies that the P-GW network element and it’s associated interfaces is to be made available to the session trace application.
tce-mode push transport { ftp | sftp } path string username name { encrypted password enc_pw | password password }
{ ftp | sftp }: Specifies that FTP or 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.
The following command configures the collection time for session traces to 30 seconds, identifies the network element as all elements (MME, S-GW, and P-GW), sets the retry timer to
5 seconds, and pushes session trace files to a TCE via SFTP into a directory named
/trace/sgw using a username
admin and a pasword of
pw123:
The following command configures the collection time for session traces to 30 seconds, identifies the network element as an MME, sets the retry timer to
5 seconds, 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:
Important: We recommend that you configure this default operator policy so that is it available to handle IMSIs that are not matched with other defined policies.
Important: Once the instance of an operator policy is defined, to use the policy it is necessary to go into the SGSN Operator Policy Configuration Mode to define the IMSI range with the MCC command - this requirement does not hold if you are using a default operator policy.
snmp communitystring [ contextctx_name ] [ viewview_name ] [ read-only | read-write ]
Specifies a community string whose options are to be modified. string must be a from 1 to 31 alpha and/or numeric characters.
read-only: the configuration may only be viewed.
read-write: the configuration may be viewed and edited.
Specifies the SNMPv3 engine to employ. id must be from 1 to 31 alpha and/or numeric characters.
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.
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.
snmp targetname ip_address [ portnumber ] [ non-default ] [ security-namestring ] [ version { 1 | 2c | 3| view ] [security-level { noauth | { auth | priv-auth privacy [encrypted] des privpassword } authentication [encrypted] { md5 | sha } authpassword } }
[ informs | traps ]
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 }
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.
Specifies the IP address of the receiver. ip_address must be specified using the standard IPv4 dotted decimal notation.
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.
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.
snmp target sampleReceiver 1.2.3.4 security-name sampleComm
trap_name1 trap_name2 ... trap_nameN
Important: The system disregards character case when entering trap names.
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.
snmpuseruser_name [ [ encrypted ] passwordpassword | engineid | groupgrp_name | security-modelmodelauth [ [ encrypted ] passwordpassword ] ]
The SNMP engine ID. id must be a string of alpha and/or numeric characters from 1 to 31characters in length.
•
|
usm : User Security Model
|
The encrypted keyword indicates the password will be received in an encrypted form.
password must be from 8 to 31 alpha and/or numeric 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.
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 user user1 group sampleGroup security-model usm auth
rd_id must be an integer from 1 to 12.
•
|
ansi: American National Standards Institute (U.S.A.)
|
•
|
bici: Broadband Intercarrier Interface standard
|
•
|
itu: International Telecommunication Union (ITU-T) Telecommunication Standardization Sector
|
[context_name]<hostname>(config-ss7-routing-domain-
routing_domain_id)#
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:
no suspend local-user
name
no suspend local-user Admin300
This keyword removes the configured system contact and
system location on system.
carrier-id mcc mcc_id mnc mnc_id
Important: This carrier ID is not used by the GGSN
mcc mcc_id : The mobile country code. This must be specified as a string of integers from 001 through 999. Values must be expressed as three integers.
mnc mnc_id: The mobile network code. This must be specified as a string of integers from 01 through 999. Values must be expressed as a minimum of two integers and a maximum of three integers.
contact who: specifies the contact information for the chassis.
who must be a string of 0 to 255 characters. The string specified must be embedded in double quotes (“) if spaces and special punctuation is to be used.
hostname host_name: configures the chassis host name where
host_name must be from 1 to 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 scripted interfaces from OSS or maintenance facility.
location text: specifies the location text to use which may be a string of 0 to 255 characters. The text specified must be embedded in double quotes (“) if spaces are to be used.
max_num must be an integer from 1 through 150.
max_num must be an integer from 1 through 200.
num must be an integer from 1 to 128.
increased: Increases the number of IPSec manager tasks operating on the PSCs/PSC2s while reducing the number of session manager tasks.
normal: Uses the standard algorithm for allocationg memory for IPSec manager tasks.
Caution: If
task-count is set to
normal and session-recovery is enabled, IPSecMgr tasks are not allowed to start on most PSCs/PSC2s.
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.
kill: The task most over memory limit (if any) is killed and recovered.
warn: The event is logged and no tasks are killed.
7: Use 7 databits to transmit and receive characters.
8: Use 8 databits to transmit and receive characters.
hardware: Enable or disable the use of hardware-based flow control
off: Disable the use of Ready to Send (RTS) and Clear to Send (CTS).
on: Enable the use of Ready to Send (RTS) and Clear to Send (CTS).
none: Disable the use of DCD, RTS and CTS.
1: Use one stop bit between each transmitted character.
2: Use two stop bits between each transmitted character.
terminal carrierdetect off databits 7 flowcontrol hardware on parity even speed 115200 stopbits 1
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.
•
|
Enter condition: 10-second average percentage of CPU utilization ³ High Threshold
|
•
|
Clear condition: 10-second average percentage of CPU utilization < Low Threshold
|
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.
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
•
|
Enter condition: Actual number of AAA Manager Requests per AAA manager ³ High Threshold
|
•
|
Clear condition: Actual number of AAA Manager Requests per AAA manager process < Low Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
high_thresh can be configured to any integer value between 0 and 10000000. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 authentication failures for an ASN-GW using the Alert thresholding model:
high_thresh can be configured to any integer value between 0 and 10000000. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
high_thresh can be configured to any integer value between 0 and 10000000. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
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:
high_thresh can be configured to any integer value between 0 and 10000000. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 network entry denials for an MS using the Alert thresholding model:
high_thresh can be configured to any integer value between 0 and 10000000. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 invalid NAIs in R6 messages using the Alert thresholding model:
high_thresh can be configured to any integer value between 0 and 10000000. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 timeouts during session setup using the Alert thresholding model:
high_thresh can be configured to any integer value between 0 and 10000000. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 0 and 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 100 timeouts during a session using the Alert thresholding model:
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.
•
|
Enter condition: Actual number of calls rejected due to no resources ³ High Threshold
|
•
|
Clear condition: Actual number of calls rejected due to no resources < Low Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
low_thresh is measured in mega bytes (MB) and can be configured to any integer value between 0 and 2048.
high_thresh is measured in mega bytes (MB) and can be configured to any integer value between 0 and 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.
•
|
Enter condition: Average measured amount of memory/CPU for last 5 minutes £ Low Threshold
|
•
|
Clear condition: Average measured amount of memory/CPU for last 5 minutes > High Threshold
|
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.
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.
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.
high_thresh is measured in percentage of total CPU memory used and can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh is measured in percentage of total CPU memory used and can be configured to any integer value between 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 the low threshold.
•
|
Enter condition: Actual percentage of CPU memory usage ³ specified percentage of total CPU memory.
|
•
|
Clear condition: Actual CPU memory usage < specified clear percentage of total CPU memory usage.
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65 percent of total PSC/PSC2 CPU memory usage and a clear threshold of
35 percent:
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a critical-level alarm threshold of 35 percent of CPU utilization by the ORBS task and a clear threshold of
35 percent:
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a warning-level alarm threshold of 25 percent of CPU utilization by the ORBS task and a clear threshold of
25 percent:
high_thresh is measured in Kilobytes per second (Kbps) and can be configured to any integer value between 0 and 1000000000. A value of 0 disables the threshold.
low_thresh is measured in Kilobytes per second (Kbps) and can be configured to any integer value between 0 and 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.
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.
high_thresh is measured in percentage of total allocated CDR file space used and can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh is measured in percentage of total allocated CDR file space used and can be configured to any integer value between 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 the low threshold.
•
|
Enter condition: Actual percentage of allocated CDR file space usage ³ specified percentage of total CDR file space.
|
•
|
Clear condition: Actual CDR file space used < specified clear percentage of total allocated CDR file space usage.
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65 percent of total allocated CDR file space usage and a clear threshold of
35 percent:
high_thresh is measured in numbers of total rating operations blocked and can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh is measured in umber of total rating operations blocked and can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
Refer to the threshold poll contfilt-block command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65 percent of total rating operations blocked and a clear threshold of
35 percent:
high_thresh is measured in numbers of total rating operations performed and can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh is measured in umber of total rating operations performed and can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
Refer to the threshold poll contfilt-rating command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65 percent of total rating operations performed and a clear threshold of
35 percent:
high_thresh can be configured to any integer value between 0 and 100.
low_thresh can be configured to any integer value between 0 and 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.
•
|
Enter condition: Average measured CPU utilization for last 5 minutes ³ High Threshold
|
•
|
Clear condition: Average measured CPU utilization for last 5 minutes < Low Threshold
|
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.
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.
The following command configures a high threshold count of 250 DCCA bad answer messages and low threshold of
100 for an system using the Alarm thresholding model:
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.
The following command configures a high threshold count of 250 protocol errors and low threshold of
100 for an system using the Alarm thresholding model:
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.
The following command configures a high threshold count of 250 requests rejected and low threshold of
100 for an system using the Alarm thresholding model:
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.
In the event that the Diameter server sends invalid Rating Groups, content-ids to the system,
dcca-unk-rating-group message is generated.
The following command configures a high threshold count of 250 unknown rating groups and low threshold of
100 for an system using the Alarm thresholding model:
high_thresh must be an integer from 0 through 100.
low_thresh must be an integer from 0 through 100.
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.
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:
high_thresh is measured in percentage of total allocated EDR file space used and can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh is measured in percentage of total allocated EDR file space used and can be configured to any integer value between 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 the low threshold.
•
|
Enter condition: Actual percentage of allocated EDR file space usage ³ specified percentage of total EDR file space.
|
•
|
Clear condition: Actual EDR file space used < specified clear percentage of total allocated EDR file space usage.
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a threshold of 65 percent of total allocated EDR file space usage and a clear threshold of
35 percent:
high_thresh must be an integer from 0 through 100000.
low_thresh must be an integer from 0 through 100000, and must be lower than
high_thresh.
•
|
Enter condition: Actual number of EDRs + UDRs dropped >= specified number of EDRs + UDRs dropped.
|
•
|
Clear condition: Actual number of EDR + UDRs dropped < specified clear number of EDRs + UDRs dropped.
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold of 90 and a clear threshold of
45 to monitor EDRs + UDRs dropped due to flow control:
Disables the threshold and sets high_thresh and
low_thresh to the default values.
high_thresh must be an integer from 0 through 1000000.
low_thresh must be 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 low threshold.
Refer to the threshold poll command to configure the polling interval, and the
threshold monitoring command to enable thresholding for this value.
The following command configures a Stateful Firewall Deny Rule high threshold of 1000 and a low threshold of
100 for a system using the Alarm Thresholding model:
Disables the threshold and sets high_thresh and
low_thresh to the default values.
high_thresh must be an integer from 0 through 1000000.
low_thresh must be 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 low threshold.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
Disables the threshold and sets high_thresh and
low_thresh to the default values.
high_thresh must be an integer from 0 through 1000000.
low_thresh must be 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 low threshold.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
Disables the threshold and sets high_thresh and
low_thresh to the default values.
high_thresh must be an integer from 0 through 1000000.
low_thresh must be 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 low threshold.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a Stateful Firewall no rules high threshold of 1000 and a low threshold of
100 for a system using the Alarm Thresholding model:
low_thresh can be configured to any integer value between 0 and 100.
high_thresh can be configured to any integer value between 0 and 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 low threshold.
•
|
Enter condition: Actual session license utilization percentage per session type £ Low Threshold
|
•
|
Clear condition: Actual session license utilization percentage per session type > High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
high_thresh is measured in percentage of total memory used and can be configured to any integer value 0 through 100. A value of 0 disables the threshold.
low_thresh is measured in percentage of total memory used and can be configured to any integer value 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.
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.
The following command configures a threshold of 65 percent of total SMC CPU memory usage and a clear threshold of
35 percent:
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.
•
|
Enter condition: Average measured CPU utilization for last 5 minutes ³ High Threshold
|
•
|
Clear condition: Average measured CPU utilization for last 5 minutes < Low Threshold
|
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.
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.
•
|
Enter condition: Actual total number of MME Attach Failure messages ³ High Threshold
|
•
|
Clear condition: Actual total number of MME Attach Failure messages < Low Threshold
|
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.
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.
•
|
Enter condition: Actual total number of MME Auth Failure messages ³ High Threshold
|
•
|
Clear condition: Actual total number of MME Auth Failure messages < Low Threshold
|
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.
•
|
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.
|
•
|
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.
|
Important: Note that for certain values, the alert or alarm serves to warn of low quantities (i.e., 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. Once 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.
Refer to the threshold aaa-acct-failure and
threshold aaa-acct-failure-rate commands for additional information on these values.
Refer to the threshold aaa-auth-failure and
threshold aaa-auth-failure-rate commands for additional information on these values.
Refer to the threshold aaa-retry-rate command for additional information on this value.
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.
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.
Refer to the threshold cpu-session-throughput command for additional information on this value.
Refer to the threshold reg-reply-error FA Service Configuration Mode command for additional information on this value.
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.
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.
Refer to the threshold license command for additional information on this value.
Refer to the threshold total-mme-sessions commands for additional information on this value.
Refer to the threshold packets-filtered-dropped command for additional information on this value.
Refer to the threshold packets-forwarded-to-cpu command for additional information on this value.
Refer to the threshold packets-forwarded-to-cpu command for additional information on this value.
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.
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.
•
|
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.
|
•
|
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.
|
Important: This command is only available in Release 8.3 and later releases.
high_thresh must be an integer from 0 through 100. A value of 0 disables the threshold.
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 high and low threshold setting.
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.
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.
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.
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
low_thresh is any integer from 0 to 300000.
low_thresh is any integer from 0 to 300000.
Clears any percentage of the number of sessions being monitored using the high_thresh variable defined above.
low_thresh is any integer from 0 to 300000.
Clears any percentage of the number of sessions being monitored using the high_thresh variable defined above.
low_thresh is any integer from 0 to 300000.
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.
•
|
Enter condition: Actual number of PDP contexts for any GGSN service ³ High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 subscriber attaches per GGSN service for the Alert thresholding model:
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.
•
|
Enter condition: Actual number of PDP contexts for any GPRS service ³ High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 2G-activated PDP contexts per GPRS service for the Alert thresholding model:
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.
•
|
Enter condition: Actual number of 2G-attached subscribers for any GPRS service ³ High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 2G-attaches per GPRS service for the Alert thresholding model:
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.
•
|
Enter condition: Actual number of HA sessions for any HA service ³ High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
•
|
Enter condition: Actual number of LNS sessions for any LNS service ³ High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
•
|
Enter condition: Actual number of PDSN sessions for any PDSN service ³ High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
•
|
Enter condition: Actual number of 3G-activated PDP contexts for any SGSN service ³ High Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 3G-activated PDP contexts per SGSN service for the system’s Alert thresholding model:
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.
•
|
Enter condition: Actual number of 3G-attached subscribers for any single SGSN service ³ High Threshold
|
•
|
Clear condition: Actual number of 3G-attached subscribers for any single SGSN service < Low Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures a high threshold count of 10000 3G-attached subscribers per SGSN service for a system using the Alert thresholding model:
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: This command is not supported on all platforms
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms.
Important: This keyword is only available in Release 8.3 and later.
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: This command is not supported on all platforms
Important: This command is not supported on all platforms
Important: This command is not supported on all platforms
time must an integer value from 60 to 60000 and expressed in multiples of 30. The system will round up all other configured values to a multiple of 30.
Important: 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
Important: 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.
Important: This command is not supported on all platforms
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
Important: When specifying
interval time for this threshold, the range is from 30 through 60000 seconds. If the value entered is not a multiple of 30, the value is automatically rounded up to the next highest multiple of 30. (If you enter 35, the value is rounded to 60.)
time is measured in seconds and can be configured to any integer value from 60 to 60000 unless otherwise noted in keyword descriptions.
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.
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
The following command configures the polling interval to 600 seconds for the ASN Gateway authentication failure threshold:
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
The following command configures the polling interval to 600 seconds for maximum EAP authentication retry threshold:
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
duration must be an integer value from 60 through 60000.
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.
duration must be an integer value from 60 through 60000.
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.
The following command configures the polling interval to 600 seconds for the content filtering blocking threshold:
duration must be an integer value from 60 through 60000.
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.
The following command configures the polling interval to 600 seconds for the content filtering rating processing threshold:
duration must be an integer value from 60 through 60000.
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.
duration must be an integer value from 60 through 60000.
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.
duration must be an integer value from 60 through 60000.
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.
duration must be an integer value from 60 through 60000.
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.
duration must be an integer from 60 through 60000. The input will be rounded up to the closest multiple of 30.
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.
duration must be an integer value from 60 through 60000.
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 ecs and other threshold commands for additional information on the system’s support for thresholds in this chapter.
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
The following command configures the polling interval of 600 seconds to count the MME Attach Failure messages for threshold limit:
dur is measured in seconds and can be configured to any integer value from 30 to 60000 in multiple of 30.
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.
The following command configures the polling interval of 600 seconds to count the MME Auth Failure messages for threshold limit:
time is measured in seconds and can be configured to any integer value from 30 to 60000.
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: 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: 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: This command is not available on all platforms
dur is measured in seconds and can be configured to any integer value from 30 to 60000.
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.
high_thresh can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 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 the high threshold.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
high_thresh can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 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 the high threshold.
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 stats
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
high_thresh can be configured to any integer value between 0 and 100. A value of 0 disables the threshold.
low_thresh can be configured to any integer value between 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 the high threshold.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
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.
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.
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
•
|
Enter condition: Actual total number of active subscriber sessions ³ High Threshold
|
•
|
Clear condition: Actual total number of active subscriber sessions < Low Threshold
|
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures an active subscriber high threshold count of 150000 and a low threshold of
1500 for an system using the Alarm thresholding model:
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this value.
The following command configures an active subscriber high threshold count of 450000 and a low threshold of
250000 for an system using the Alarm thresholding model:
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the command to configure the polling interval and the threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
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.
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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
Refer to the threshold poll command to configure the polling interval and the
threshold monitoring command to enable thresholding for this 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.
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.
Important: Software Patch Upgrades are not supported in this release.
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:
path must be a string of 1 through 255 characters in length.
max-versions max_versions
max_versions must be an integer from 0 through 3.
file_name must be in
name.extension format. For example,
abc.bin. And, must be a string of 1 through 10 characters in length.