Context Configuration
Mode Commands S-Z
This section
includes the commands s102-service through wsg-service service.
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
IMPORTANT:
The commands or keywords/variables
that are available are dependent on platform type, product version, and
installed license(s).
saegw-service
Creates a System Architecture
Evolution Gateway (SAEGW) service or specifies an existing SAEGW
service and enters the SAEGW Service Configuration Mode for the
current context.
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
saegw-service service_name [ -noconfirm ]no saegw-service service_name
no
Removes the specified
SAEGW service from the context.
service_name
Specifies the name of
the SAEGW service. If service_name does
not refer to an existing service, the new service is created if
resources allow. service_name is
an alphanumeric string of 1 through 63 characters.
IMPORTANT:
Service names must be unique across all
contexts within a chassis.
-noconfirm
Executes the command
without any additional prompt and confirmation from the user.
Usage:
Enter the SAEGW Service
Configuration Mode for an existing service or for a newly defined
service. This command is also used to remove an existing service.
IMPORTANT:
An S-GW and/or
P-GW created in the same context must be associated with this SAEGW service.
A maximum of 256 services
(regardless of type) can be configured per system.
CAUTION:
Large numbers of services
greatly increase the complexity of management and may impact overall
system performance (for example, resulting from such things as system
handoffs). Therefore, it is recommended that a large number of services
only be configured if your application absolutely requires it. Please
contact your local service representative for more information.
Entering this command
results in the following prompt:
[context_name]hostname(config-saegw-service)#
SAEGW Service Configuration
Mode commands are defined in the SAEGW Service Configuration
Mode Commands chapter.
Use this command when
configuring the following SAE components: SAEGW.
Example:
The following command
enters the existing SAEGW Service Configuration Mode (or creates
it if it does not already exist) for the service named
saegw-service1:
saegw-service saegw-service1
The following command
will remove
pgw-service1 from
the system:
no saegw-service saegw-service1
server
Configures remote server
access protocols for the current context. This command is used to
enter the specified protocols configuration mode.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
server { ftpd | named | sshd | telnetd | tftpd }no server { ftpd | named | sshd | telnetd | tftpd } [ kill ]
no
Disables the specified
service.
ftpd
Enters the FTP Server
Configuration Mode.
IMPORTANT:
The FTPD server can
only be configured in the local context.
named
Starts the named server.
sshd
Enters the SSH Server
Configuration Mode.
IMPORTANT:
The SSHD server allows
only three unsuccessful login attempts before closing a login session
attempt.
telnetd
Enters the Telnet Server
Configuration Mode.
IMPORTANT:
The TELNET server allows
only three unsuccessful login attempts before closing a login session
attempt.
tftpd
Enters the TFTP Server
Configuration Mode.
IMPORTANT:
The TFTPD server can
only be configured in the local context.
kill
Indicates all instances
of the server are to be stopped.
This option only works
with the ftpd, sshd, telnetd, and tftpd commands.
Usage:
Enter the Context Configuration
Mode for the appropriate, previously defined context, to set the
server option(s). Repeat the command as needed to enable/disable
more than one option server daemon.
Example:
server ftpd
server named
no server tftpd
server sshd
server telnetd
no server telnetd kill
service-redundancy-protocol
Configures Interchassis
Session Recovery (ICSR) services for the current context. This command
is used to enter the Service Redundancy Protocol Configuration Mode.
Product:
All products supporting
ICSR
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
service-redundancy-protocol
Usage:
Enter the Configuration
Mode to set the service redundancy protocol options.
Example:
The following command
enters Service Redundancy Protocol Configuration Mode.
service-redundancy-protocol
session-event-module
Enables the event
module, enters the Session Event Module Configuration Mode where the
sending of S-GW subscriber-specific
event files to an external server can be configured.
From release 15.0
onwards, the session-event module is used by SGSN for event logging.
By default, EDR files are generated at the location: /hd-raid/records/edr.
After upgrading to release R15.0, if this CLI is configured, the
path for EDR files changes to: /hd-raid/records/event.
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ no ] session-event-module
no
Disables the event module
configuration.
Usage:
Enter the Session Event
Module Configuration Mode where the sending of S-GW subscriber-specific event files to an external server
can be configured.
Entering this command
results in the following prompt:
[context_name]hostname(config-event)#
Session Event Module
Configuration Mode commands are defined in the Session Event Module
Configuration Mode Commands chapter.
sgsn-service
Creates an SGSN service
instance and enters the SGSN Service Configuration mode. This mode
configures or edits the configuration for an SGSN service which
controls the SGSN functionality.
An SGSN mediates access
to GPRS/UMTS network resources on behalf of user equipment
(UE) and implements the packet scheduling policy between different
QoS classes. It is responsible for establishing the packet data
protocol (PDP) context with the GGSN.
IMPORTANT:
For details about the
commands and parameters, check the SGSN Service Configuration
Mode chapter.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ no ] sgsn-service srvc_name
no
Remove the configuration
for the specified SGSN service from the configuration of the current context.
srvc_name
Specifies the name
of the SGSN service as a unique alphanumeric string of 1 through
63 characters.
IMPORTANT:
Service names must
be unique across all contexts within a chassis.
Usage:
Use this command to
create, edit, or remove an SGSN service.
Example:
The following command
creates an SGSN service named
sgsn1 in the
current context:
sgsn-service sgsn1
The following command
removes the sgsn service named
sgsn1 from
the configuration for the current context:
no sgsn-service sgsn1
sgs-service
Creates an SGs service
instance and enters the SGS Service Configuration mode.
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ no ] sgs-service name
no
Remove the configuration
for the specified SGs service from the configuration of the current context.
name
Specifies a name for
an SGs service as a unique alphanumeric string of 1 through 63 characters.
IMPORTANT:
Service names must be unique across all
contexts within a chassis.
-noconfirm
Executes the command
without any additional prompt and confirmation from the user.
Usage:
Enter the SGS Service
Configuration Mode for an existing service or for a newly defined service.
This command is also used to remove an existing service.
A maximum of 256 services
(regardless of type) can be configured per system.
CAUTION:
Large numbers of services
greatly increase the complexity of management and may impact overall
system performance (for example, resulting from such things as system
handoffs). Therefore, it is recommended that a large number of services
only be configured if your application absolutely requires it. Please
contact your local service representative for more information.
Entering this command
results in the following CLI prompt:
[context_name]hostname(config-sgs-service)#
SGS Service Configuration
Mode commands are defined in the MME SGS Service Configuration
Mode Commands chapter.
Example:
The following command
creates an SGS service named
sgs1 in the
current context:
sgs-service sgs1
The following command
removes the SGS service named
sgs1 from
the configuration for the current context:
no sgs-service sgs1
sgtp-service
Creates an SGTP service
instance and enters the SGTP Service Configuration mode. This mode
configures the GPRS Tunneling Protocol (GTP) related settings required
by the SGSN
and eWAG to support
GTP-C (control plane) messaging and GTP-U (user data plane) messaging.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ no ] sgtp-service sgtp_service_name
no
If previously configured,
removes the specified SGTP service configuration in the current context.
sgtp_service_name
Specifies name of the
SGTP service.
sgtp_service_name must
be an alphanumeric string of 1 through 63 characters.
IMPORTANT:
Service names must be unique across all
contexts within a chassis.
Usage:
Use this command to
create, edit, or remove an SGTP service.
On entering this command,
the CLI prompt changes to:
[context_name]hostname(config-sgtp-service)#
Example:
The following command
creates an SGTP service named
sgtp1 in
the current context:
sgtp-service sgtp1
The following command
removes, if previously configured, the SGTP service named
sgtp1 from
the current context:
no sgtp-service sgtp1
sgw-service
Creates an S-GW service
or specifies an existing S-GW service and enters the S-GW Service
Configuration Mode for the current context.
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
sgw-service service_name [ -noconfirm ]no sgw-service service_name
service_name
Specifies the name
of the S-GW service. If service_name does
not refer to an existing service, the new service is created if
resources allow. service_name is
an alphanumeric string of 1 through 63 characters.
IMPORTANT:
Service names must be unique across all
contexts within a chassis.
-noconfirm
Executes the command
without any additional prompt and confirmation from the user.
no sgw-service service_name
Removes the specified
S-GW service from the context.
Usage:
Enter the S-GW Service
Configuration Mode for an existing service or for a newly defined service.
This command is also used to remove an existing service.
A maximum of 256 services
(regardless of type) can be configured per system.
CAUTION:
Large numbers of services
greatly increase the complexity of management and may impact overall
system performance (for example, resulting from such things as system
handoffs). Therefore, it is recommended that a large number of services
only be configured if your application absolutely requires it. Please
contact your local service representative for more information.
Entering this command
results in the following prompt:
[context_name]hostname(config-sgw-service)#
S-GW Service Configuration
Mode commands are defined in the S-GW Service Configuration
Mode Commands chapter.
Use this command when
configuring the following SAE components: S-GW.
Example:
The following command
enters the existing S-GW Service Configuration Mode (or creates
it if it does not already exist) for the service named
sgw-service1:
sgw-service sgw-service1
The following command
will remove
spgw-service1 from
the system:
no sgw-service sgw-service1
ssh
Generates public and
private keys for use with the configured Secure Shell (SSH) server
for the current context and sets the public/private key
pair to specified values.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
ssh { generate
key | key data length octets } [ type { v1-rsa | v2-rsa | v2-dsa } ]no ssh key [ type { v1-rsa | v2-rsa | v2-dsa } ]
no ssh key [ type { v1-rsa | v2-rsa | v2-dsa } ]
This command clears
configured SSH keys. If type is not specified, all SSH keys are cleared.
generate key
Generates a public/private
key pair which is to be used by the SSH server. The generated key pair
is in use until the command is issued again.
key data length octets
Sets the public/private
key pair to be used by the system where data is the
encrypted key and length is the
length of the encrypted key in octets. data must
be an alphanumeric string of 1 through 1023 characters and octets must be
a value in the range of 0 through 65535.
[ type { v1-rsa | v2-rsa | v2-dsa } ]
Specifies the type
of SSH key to generate. If type is not specified, all three key
types are generated.
-
v1-rsa: SSHv1
RSA host key only
-
v2-rsa: SSHv2
DSA host key only
-
v2-dsa: SSHv2
RSA host key only
IMPORTANT:
For maximum security,
it is recommended that only SSH v2 be used. v2-rsa is
the recommended key type.
Usage:
Generate secure shell
keys for use in public key authentication.
Example:
ssh generate key
ssh key g6j93fw59cx length 128
ssl
Creates a new Secure
Sockets Layer (SSL) template or specifies an existing one and enters
the SSL Template Configuration Mode.
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ no ] ssl
template name { ssl-subscriber }
no
Removes the specified
SSL template from the context.
template name
Specifies the name
of a new or existing SSL template as an alphanumeric string of 1
through 127 alphanumeric characters.
ssl-subscriber
Specifies that the
SSL template is an SSL subscriber template.
Usage:
Use this command to
create a new SSL template or modify an existing one.
Entering this command
results in the following prompt:
[context_name]hostname(cfg-ctx-ssl-subscriber-template)#
SSL Template Configuration
Mode commands are defined in the SSL Template Configuration
Mode Commands chapter.
Example:
The following command
specifies the SSL template
ssl_template_1 and
enters the SSL Template Configuration Mode:
ssl template ssl_template_1
ssl-subscriber
subscriber
Configures the specified
subscriber for the current context.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
subscriber { default | name user_name } asn-service-info mobility [ ipv4 | ipv6 | ipv6-ipv4 ]no subscriber { default | name user_name }
no
Indicates the subscriber
specified is to be removed from the list of allowed users for the current
context.
default | name user_name
default:
Enters the Subscriber Configuration Mode for the context’s
default subscriber settings.
name user_name:
Specifies the user which is to be allowed to use the services of
the current context. user_name must
be an alphanumeric string of 1 through 127 characters.
asn-service-info mobility:Indicates
the type of mobility supported and enabled in the Autonomous System
Number (ASN).
Usage:
Enter the Subscriber
Configuration Mode for actual users as well as for a default subscriber
for the current context.
Entering this command
results in the following prompt:
[context_name]hostname(config-subscriber)#
Subscriber Configuration
Mode commands are defined in the Subscriber Configuration
Mode Commands chapter.
NAS uses the specified
parameter for asn-service-info mobility to indicate and pack the mobility
support field for IPv4, IPv6, or both, in the Service-Info attribute
in the Access-request. RADIUS sends back this attribute in the Access-accept
message by indicating respective bits to authorize the service indicated
by NAS.
IMPORTANT:
A maximum of 128 subscribers
and/or administrative users may be locally configured per context.
Example:
Following command configures
the default subscriber in a context:
subscriber default
Following command removes
the default subscriber from a context:
no subscriber default
Following command configures
a subscriber named
user1 in
a context:
subscriber name user1
Following command removes
a subscriber named
user1 from
a context:
no subscriber name user1
threshold available-ip-pool-group
Configures context-level
thresholds for IP pool utilization for the system.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
threshold available-ip-pool-group low_thresh [ clear high_thresh ]default threshold available-ip-pool-group
default
Configures the default
setting.
low_thresh
The low threshold IP
pool utilization percentage that must be met or exceeded within
the polling interval to generate an alert or alarm. low_thresh can
be configured as an integer from 0 through 100. Default: 10
clear high_thresh
Specifies the high
threshold IP pool utilization percentage that maintains a previously generated
alarm condition. If the utilization percentage rises above the high
threshold within the polling interval, a clear alarm will be generated. high_thresh can
be configured as an integer from 0 through 100. Default: 10
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
When IP address pools
are configured on the system, they can be assigned to a group. IP address
pool utilization thresholds generate alerts or alarms based on the
utilization percentage of all IP address contained in the pool group
during the specified polling interval.
All configured public
IP address pools that were not assigned to a group are treated as belonging
to the same group. Individual configured static or private pools
are each treated as their own group.
Alerts or alarms are
triggered for IP address pool utilization based on the following rules:
-
Enter Condition:
Actual IP address utilization percentage per pool group
< Low Threshold
-
Clear Condition:
Actual IP address utilization percentage per pool group > High Threshold
If a trigger condition
occurs within the polling interval, the alert or alarm will not
be generated until the end of the polling interval.
The following table
describes the possible methods for configuring IP pool utilization thresholds:
Table 1. IP Pool Utilization
Thresholds - Configuration Methods
| Method |
Description |
|
Context-level
|
A single IP pool utilization
threshold can be configured for all IP pool groups within a given
system context. If a single threshold is configured for all pool
groups, separate alerts or alarms can be generated for each group.
This command configures
that threshold.
|
|
IP address pool-level
|
Each individual IP
address pool can be configured with its own threshold. Thresholds
configured for individual pools take precedence over the context-level threshold
that would otherwise be applied (if configured).
In the event that two
IP address pools belonging to the same pool group are configured
with different thresholds, the system uses the pool configuration
that has the greatest low threshold for that group.
|
Example:
The following command
configures a context-level IP pool utilization low threshold percentage
of
10 and
a high threshold of
35 for
an system using the Alarm thresholding model:
threshold available-ip-pool-group
10 clear 35
threshold ha-service
init-rrq-rcvd-rate
Sets an alarm or alert
based on the average number of calls setup per second for an HA
service.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
threshold ha-service
init-rrq-rcvd-rate high_thresh [ clear low_thresh ]no threshold ha-service
init-rrq-rcvd-rate
no
Deletes the alert or
alarm.
high_thresh
Sets the high threshold
average number of calls setup per second that must be met or exceeded
within the polling interval to generate an alert or alarm. It can
be configured as an integer from 0 through 1000000. Default: 0
clear low_thresh
Sets the low threshold
average number of calls setup per second that must be met or exceeded
within the polling interval to clear an alert or alarm. It can be
configured as an integer from 0 through 1000000. Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set an alert or an alarm when the average number of calls set upper second
is equal to or less than a specified number of calls per second.
Alerts or alarms are
triggered for the number of calls setup per second based on the following
rules:
-
Enter Condition:
Actual number of calls setup per second > High Threshold
-
Clear Condition:
Actual number of calls setup per second
< Low Threshold
Example:
The following command
configures a number of calls setup per second threshold of
1000 and a
low threshold of
500 for
a system using the Alarm thresholding model:
threshold ha-service
init-rrq-rcvd-rate 1000 clear 500
threshold ip-pool-free
Sets an alarm or alert
based on the percentage of IP addresses that are unassigned in an
IP pool. This command affects all IP pools in the current context.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
threshold ip-pool-free low_thresh [ clear high_thresh ]default threshold ip-pool-free
default
Configures the default
setting.
low_thresh
Sets the low threshold
percentage of addresses available in an IP pool that must be met
or exceeded within the polling interval to generate an alert or
alarm. It can be configured as an integer between 0 and 100. Default:0
clear high_thresh
Sets the high threshold
percentage of addresses available in an IP pool that maintains a previously
generated alarm condition. If the utilization percentage rises above
the high threshold within the polling interval, a clear alarm will
be generated. It may be configured as an integer between 0 and 100.
Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
Use this command to
set an alert or an alarm when the number of unassigned IP addresses in
any pool is equal to or less than a specified percentage of the
total number of addresses in the pool.
Alerts or alarms are
triggered for percentage of IP address pool free based on the following rules:
-
Enter Condition:
Actual percentage of IP addresses free per pool
< Low Threshold
-
Clear Condition:
Actual percentage of IP addresses free per pool > High Threshold
IMPORTANT:
This command is overridden
by the settings of the alert-threshold keyword
of the ip pool command.
Example:
The following command
configures a context-level IP pool percentage of IP addresses that are
unused low threshold percentage of
10 and a high
threshold of
35 for
an system using the Alarm thresholding model:
threshold ip-pool-free
10 clear 35
threshold ip-pool-hold
Sets an alert based
on the percentage of IP addresses from an IP pool that are on hold.
This command affects all IP pools in the current context.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
threshold ip-pool-hold high_thresh [ clear low_thresh ]default threshold ip-pool-hold
default
Configures the default
setting.
high_thresh
Sets the high threshold
percentage of addresses on hold in an IP pool that must be met or exceeded
within the polling interval to generate an alert or alarm. It can
be configured as an integer from 0 through 100. Default: 0
clear low_thresh
Sets the low threshold
percentage of addresses on hold in an IP pool that maintains a previously
generated alarm condition. If the utilization percentage rises below
the low threshold within the polling interval, a clear alarm will
be generated. It may be configured as an integer from 0 through
100. Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set an alert or an alarm when the percentage of IP addresses on
hold in any pool is equal to or greater than a specified percentage
of the total number of addresses in the pool.
Alerts or alarms are
triggered for percentage of IP address pool addresses on hold based
on the following rules:
-
Enter Condition:
Actual percentage of IP addresses on hold per pool > High Threshold
-
Clear Condition:
Actual percentage of IP addresses on hold per pool
< Low Threshold
IMPORTANT:
This command is overridden
by the settings of the alert-threshold keyword
of the ip pool command.
Example:
The following command
configures a context-level IP pool percentage of IP addresses that are
on high threshold percentage of
35 and a low
threshold of
10 for
an system using the Alarm thresholding model:
threshold ip-pool-hold
35 clear 10
threshold ip-pool-release
Sets an alert based
on the percentage of IP addresses from an IP pool that are in the
release state. This command affects all IP pools in the current
context.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
threshold ip-pool-release high_thresh [ clear low_thresh ]default threshold ip-pool-release
default
Configures the default
setting.
high_thresh
Sets the high threshold
percentage of addresses in the release state in an IP pool that
must be met or exceeded within the polling interval to generate
an alert or alarm. It can be configured as an integer from 0 through
100. Default: 0
clear low_thresh
Sets the low threshold
percentage of addresses in the release state in an IP pool that maintains
a previously generated alarm condition. If the utilization percentage
rises below the low threshold within the polling interval, a clear
alarm will be generated. It may be configured as an integer from
0 through 100. Default:0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
Use this command to
set an alert or an alarm when the number of IP addresses the release state
in any pool is equal to or greater than a specified percentage of
the total number of addresses in the pool.
Alerts or alarms are
triggered for percentage of IP address pool addresses in the release state
based on the following rules:
-
Enter Condition:
Actual percentage of IP addresses in the release state per pool>
High Threshold
-
Clear Condition:
Actual percentage of IP addresses in the release state per pool
< Low Threshold
IMPORTANT:
This command is overridden
by the settings of the alert-threshold keyword
of the ip pool command.
Example:
The following command
configures a context-level IP pool percentage of IP addresses that are
in the release state high threshold percentage of
35 and a low threshold
of
10 for
an system using the Alarm thresholding model:
threshold ip-pool-release
35 clear 10
threshold ip-pool-used
Sets an alert based
on the percentage of IP addresses that have been assigned from an
IP pool. This command affects all IP pools in the current context.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
threshold ip-pool-used high_thresh [ clear low_thresh ]default threshold ip-pool-used
default
Configures the default
setting.
high_thresh
Sets the high threshold
percentage of addresses assigned from an IP pool that must be met
or exceeded within the polling interval to generate an alert or
alarm. It can be configured as an integer from 0 through 100. Default:0
clear low_thresh
Sets the low threshold
percentage of addresses assigned from an IP pool that maintains
a previously generated alarm condition. If the utilization percentage
rises above the high threshold within the polling interval, a clear
alarm will be generated. It may be configured to any integer between0
and 100. Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the low
threshold.
Usage:
Use this command to
set an alert or an alarm when the number of IP addresses assigned from
any pool is equal to or greater than a specified percentage of the
total number of addresses in the pool.
Alerts or alarms are
triggered for percentage of IP address pool addresses used based
on the following rules:
-
Enter Condition:
Actual percentage of IP addresses used per pool > High Threshold
-
Clear Condition:
Actual percentage of IP addresses used per pool
< Low Threshold
IMPORTANT:
This command is overridden
by the settings of the alert-threshold keyword
of the ip pool command.
Example:
The following command
configures a context-level IP pool percentage of IP addresses that are
used high threshold percentage of
35 and a low
threshold of
10 for
an system using the Alarm thresholding model:
threshold ip-pool-used
35 clear 10
threshold monitoring
Enables or disables
thresholds alerting for a group of thresholds.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ default | no ] threshold
monitoring available-ip-pool-group
default
Configures the default
setting.
no
Disables threshold
monitoring for the specified value.
available-ip-pool-group
Enables threshold monitoring
for IP pool thresholds at the context level and the IP address pool-level.
Refer to the threshold
available-ip-pool-group command, the threshold ip-pool-x commands
and the alert-threshold keyword
of the ip pool command
for additional information on these values.
Usage:
Thresholding on the
system is used to monitor the system for conditions that could potentially
cause errors or outage. Typically, these conditions are temporary
(i.e high CPU utilization, or packet collisions on a network) and
are quickly resolved. However, continuous or large numbers of these
error conditions within a specific time interval may be indicative
of larger, more severe issues. The purpose of thresholding is to
help identify potentially severe conditions so that immediate action
can be taken to minimize and/or avoid system downtime.
Thresholding reports
conditions using one of the following mechanisms:
-
SNMP traps: SNMP
traps have been created that indicate the condition (high threshold
crossing and/or clear) of each of the monitored values.
Complete descriptions and other information pertaining to these
traps is located in the
starentMIB(8164).starentTraps(2)section
of the SNMPMIB Reference.
The generation of specific
traps can be enabled or disabled on the system allowing you to view
only those traps that are most important to you.
-
Logs: The system
provides a facility called threshold for which active and event
logs can be generated. As with other system facilities, logs are
generated Log messages pertaining to the condition of a monitored
value are generated with a severity level of WARNING.
-
Alarm System: High
threshold alarms generated within the specified polling interval
are considered “outstanding” until a the condition
no longer exists and/or a condition clear alarm is generated.
“Outstanding” alarms
are reported to through the system’s alarm subsystem and
are viewable through the CLI.
The following table
indicates the reporting mechanisms supported by each of the above models.
Table 2. Thresholding Reporting
Mechanisms by Model
| Model |
SNMP
Traps |
Logs |
Alarm
System |
|
Alert
|
X
|
X
|
|
|
Alarm
|
X
|
X
|
X
|
Refer to the threshold
poll command in Global Configuration Mode Commands for
information on configuring the polling interval over which IP address
pool utilization is monitored.
Example:
the following command
enables threshold monitoring for IP pool thresholds at the context level
and the IP address pool-level:
threshold monitoring
available-ip-pool-group
threshold pdsn-service
init-rrq-rcvd-rate
Sets an alarm or alert
based on the average number of calls setup per second for a PDSN
service.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
threshold pdsn-service
init-rrq-rcvd-rate high_thresh [ clear low_thresh ]no threshold pdsn-service
init-rrq-rcvd-rate
no
Deletes the alert or
alarm.
high_thresh
Sets the high threshold
average number of calls setup per second that must be met or exceeded
within the polling interval to generate an alert or alarm. It can
be configured as an integer between 0 and 1000000. Default: 0
clear low_thresh
Sets the low threshold
average number of calls setup per second that must be met or exceeded
within the polling interval to clear an alert or alarm. It can be
configured as an integer between 0 and 1000000. Default: 0
IMPORTANT:
This value is ignored
for the Alert model. In addition, if this value is not configured
for the Alarm model, the system assumes it is identical to the high
threshold.
Usage:
Use this command to
set an alert or an alarm when the average number of calls set upper second
is equal to or less than a specified number of calls per second.
Alerts or alarms are
triggered for the number of calls setup per second based on the following
rules:
-
Enter Condition:
Actual number of calls setup per second > High Threshold
-
Clear Condition:
Actual number of calls setup per second
< Low Threshold
Example:
The following command
configures a number of calls setup per second threshold of
1000 and a
low threshold of
500 for
a system using the Alarm thresholding model:
threshold pdsn-service
init-rrq-rcvd-rate 1000 clear 500
udr-module active-charging-service
Enables creation, configuration
and deletion of the User Data Record (UDR) module for the context.
Privilege:
Security Administrator,
Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
[ no ] udr-module
active-charging-service
no
Deletes the UDR module
configuration for the current context.
Usage:
Use this command to
create the UDR module for the context, and configure the UDR module
for active charging service records. You must be in a non-local
context when specifying this command, and you must use the same
context when specifying the EDR module command.
On entering this command,
the CLI prompt changes to:
[context_name]hostname(config-udr)#
Example:
The following command
creates the UDR module for the context, and enters the UDR Module
Configuration Mode:
udr-module active-charging-service
wsg-service
Enables or disables
Wireless Security Gateway (WSG) service. When
enabled you are in WSG Service Configuration mode. (VPC
only)
Privilege:
Security Administrator
Mode:
Exec > Global Configuration
> Context Configuration
configure > context context_name
Entering the above
command sequence results in the following prompt:
[context_name]host_name(config-ctx)#
Syntax
wsg-service service_name
no wsg-service service_name
no
Disables the specified
WSG service.
service_name
Specifies the name of
the WSG service as an alphanumeric string of 1 through 63 characters.
IMPORTANT:
Service names must be
unique across all contexts within a chassis.
Usage:
Use this command to
enter the WSG Service Configuration Mode. For additional information, see
the WSG Service Configuration
Mode Commands chapter.
Example:
The following command
enters the WSG Service Configuration Mode:
wsg-service wsg01